Jump to content
Onda Forum
Gearbest Get Xiaomi Mi Band 3 for Free on Xiaomi Great Sale @GearBest promotion
Get Xiaomi Mi Band 3 for Free on Xiaomi Great Sale @GearBest
stane1983

Onda V975m ROM by Stane1983

Recommended Posts

Hi,

Preparing factory rom for firmware installation is not possible for me. Why:

- .img file contains raw partitions for system, data... (that can be done from stock install file)

- u-boot files are missing (.img file does not have only u-boot.bin but contains these files: ddr_init.bin, u-boot.bin and u-boot-comp.bin)

It may be way for me to create new u-boot based on old layout and prepare update for it, but I really don't want to brick more devices.

Reverting to old bootloader and stock rom is possible but with uart connection.

Steps for that would be:

- boot device and interrupt booting

- read stock u-boot.bin from sdcard and flash it to write-protected NAND area

- reset device and interrupt bootloader again

- issue command store init 3 (this will recreate all partitions that matches old nand layout but will erase whole nand with bootloader included)

- read back stock u-boot.bin from sdcard and flash it to nand

- restart device with stock recovery.img and update.zip placed on sdcard.

- flash firmware from recovery (tablet will be auto booted in recovery because nand is empty) and do factory reset (from recovery menu) to format data and cache partitions and wipe media partition (to format internal sdcard partition)

these steps for installing stock and rozak roms or stock roms only

Share this post


Link to post
Share on other sites

Yeh got it working!

The following steps i did to get it working

Poweroff tablet

Connect usb cable with computer

Hold volume up

Connect usb

Power on tablet.

Thanx stane, this is for sure better than rozaks!

 

Why are you quoting a message that refers to flashing away from stane's into stock ROM to refer to you flashing successfully Stane's custom ROM?

It does not make sense and it just takes up space.

Share this post


Link to post
Share on other sites

Hi,

 

Preparing factory rom for firmware installation is not possible for me. Why:

 

- .img file contains raw partitions for system, data... (that can be done from stock install file)

- u-boot files are missing (.img file does not have only u-boot.bin but contains these files: ddr_init.bin, u-boot.bin and u-boot-comp.bin)

 

It may be way for me to create new u-boot based on old layout and prepare update for it, but I really don't want to brick more devices.

 

Reverting to old bootloader and stock rom is possible but with uart connection.

 

Steps for that would be:

- boot device and interrupt booting

- read stock u-boot.bin from sdcard and flash it to write-protected NAND area

- reset device and interrupt bootloader again

- issue command store init 3 (this will recreate all partitions that matches old nand layout but will erase whole nand with bootloader included)

- read back stock u-boot.bin from sdcard and flash it to nand

- restart device with stock recovery.img and update.zip placed on sdcard.

- flash firmware from recovery (tablet will be auto booted in recovery because nand is empty) and do factory reset (from recovery menu) to format data and cache partitions and wipe media partition (to format internal sdcard partition)

 

Hey Stane...before I jump up and down and high-five my dog, a little clarification. There are acouple of us who have bricks which occurred by tressing the twrp app of 0.9.1 but with an sdcard in slot with rom on it. As I read what you wrote it sounds like there might be a solution. I can boot into a stock recovery...sure you've read the posts...we only get an instwall\delete loop.

 

Not sure what uart means...need to read. But can we be saved?

Share this post


Link to post
Share on other sites

UART (Universal Asynchronous Receiver Transmitter) is a serial communication interface. You may know it as RS232 port or COM1, COM2 ports.

What stane means is that you have to use a serial debug interface like the USB debugging interface PL2303HX for ~$2.43 or ~€2.85 (easy to be found @Amazon).

This is a TTL level to USB interface. You must not connect a standard RS232 port to your tab because the tab uses TTL level (0V/5V) output and the COM port of your PC uses RS232 levels (-10V/+10V).

You have to solder it to the internal GND, Tx and Rx pins of the debug port inside the V975m.

Then you have to open a terminal program like Hyperterm or Realterm and configure the port to communicate @ 115200,8,N,1 and no hardware handshake.

If you turn the tab on you will see the startup messages.

Here is a VERY short excerpt of stanes bootloader startup:

System Started


U-boot-00000-ga234870-dirty(m8_k12_MA975M8_v1@20140823) (Sep 17 2014 - 22:42:57)

clr h-ram
DRAM:  2 GiB
relocation Offset is: 6fec0000
show partition table: 
part: 0, name :       logo, size : 2000000
part: 1, name :   recovery, size : 2000000
part: 2, name :       misc, size : 2000000
part: 3, name :       boot, size : 2000000
part: 4, name :     system, size : 40000000
part: 5, name :      cache, size : 10000000
part: 6, name :       data, size : end 
aml_card_type=0x0
MMC:   [mmc_register] add mmc dev_num=0, port=1, if_type=6
[mmc_register] add mmc dev_num=1, port=2, if_type=6

The communication runs in both ways and as you use a terminal program you can also send characters/commands to the tab.

But you first need to interrupt the boot process or the bootloader will not accept any commands from your side.

This interrruption is done by sending the "interrupt hotkey" to the tab during startup. Commonly used hotkeys are space, escape or enter.

I tried all of them and none seems work. Unfortunately there is no standard for the hotkey and even not implemeting this interruption at all is possible too.

The hotkey is defined in the sources of the bootloader - and as only stane has the sources he is the only person who could tell us this secret hotkey...

  • Upvote 1

Share this post


Link to post
Share on other sites

The problem is... It was only discovered that having the sd card in seemed to cause the bricks after it caused them... Also.. I had my sd card in and mine never bricked so it's also not that simple as just that issue causing

Sent from my Android L Nexus 5 via Tapatalk

Share this post


Link to post
Share on other sites

@stane

 

What I can deduce from what you said is that for most home users it is practically impossible to do that, it takes a lot of programming and testing on your side and technical expertise on our side (uart connection, soldering etc), if I understood correctly.

 

1) On the one side there are people here with bricked tablets which they may not even be returnable for service (free of extra charge)...

...it is important here to stop the flow of people with bricked tablets by providing very explicit information that

i) there is no going back to stock once you flash this ROM

ii) warn with bold red letters about all the perils and pitfalls of installing this ROM and TWRP the wrong way

 

It needs to get very hard for someone to get into the process without familiarizing himself with the relative information even if one is not being attentive, e.g. write with big letters on top, before any steps for flashing what one should not do and make sure one does.

 

2) On the other side there are people who see minor and major bugs with the given ROM. These people may have knowingly or not taken the plung into a ROM from which there is no way of going back on the short/mid-term. Some may be quite happy, others so and so.

 

The question for all users now is "where do we go from here?"

a. Should they be pressing for a stock ROM reflashing script

or

b. Should they be asking for new features, for fixes and improvements?

 

 

Although it may be very frustrating for those who got their tabs bricked one way or another, what I gather from what you're saying is that writing such a script can take a long while, with testing etc....

At the same time development on the token ROM can get pretty much frozen.

 

So how should you take advantage of your time and where should you spend your efforts? It's not like we are writing you a pay-cheque so there is limited time available for development.

 

I would support the 2nd option...

- FIRST focus on the glitches people are getting with their current ROM (wifi speed, bluetooth headset, support for ART etc) so they can work with it happily while putting aside the fact that they may now be in a one-lane road with regard to options

- THEN it would be awesome to see if there will be a way to move back between ROMs...it's not comforting to think that if the tablet needs service, one is gonna have to pay for it although covered by warranty period.

 

Lets make sure

- no more people flash this ROM without knowing they cant get back

- about what people need to do and don't do while flashing (write the guides as if all people are stupid and and are going to get it wrong and only read the guide fully after completing each step not knowing what comes next) in way that would be impossible to escape their attention.

 

And then move one to paths a. or b.

 

Problematic areas in your initial message in this thread (apart from the lack of mention to the one-way ticket to this ROM)

 

"Installing TWRP recovery:

Under apps there is TWRP Installer. Launch it and install TWRP. App will be uninstalled after procedure."

 

No mention there about the risk when you have an sdcard inserted...we need to avoid sending incomplete signals...better to say nothing but only link to the relevant thread while warning about what one should avoid, before one even follows the link to the thread concerning the isntallation of TWRP

 

Greetings from the Brickyard! Keep hope alive! Fortunately I live in Germany where Scibee is located and he doesn't even know it yet but he is going to help me unbrick this thing using the UART method.

 

But what I really want to say here...and after incredible frustration...we are all responsible for the learning curve here. Stane has since installed an interrupt so that the sd card gets pulled before twrp install. I have owned many china tablets and phones...and I experiment recklessly with all sorts of ROMs. All projects of this type come with an explicit or implicit warning...proceed at your own risk. I pushed the button, it's as simple as that. I am glad for the others who have come after me that they have now been protected from this error. But folks like Stane need the freedom to develop without guilt. All errors are part of the bumpy road. I don't see myself as a victim. We all need to use skippie as an example...thousands of frustrated posts, acceptance of his fate, and purchase of a new tablet.

 

But if you are still reading, skippie...looks like there may be life in this sucker after all!!!

  • Upvote 1

Share this post


Link to post
Share on other sites

I'm entirely agreed with all last posts. Maybe it's better to focus on bugs -like the WiFi problem- once you have installed the ROM, as it is in my case. Maybe, in a near future, I could be able to run muy WiFi speed...someday.

I'm still eternally grateful to Stane and everybody here for making this tablet better.

Share this post


Link to post
Share on other sites

Greetings from the Brickyard! Keep hope alive! Fortunately I live in Germany where Scibee is located and he doesn't even know it yet but he is going to help me unbrick this thing using the UART method.

 

But what I really want to say here...and after incredible frustration...we are all responsible for the learning curve here. Stane has since installed an interrupt so that the sd card gets pulled before twrp install. I have owned many china tablets and phones...and I experiment recklessly with all sorts of ROMs. All projects of this type come with an explicit or implicit warning...proceed at your own risk. I pushed the button, it's as simple as that. I am glad for the others who have come after me that they have now been protected from this error. But folks like Stane need the freedom to develop without guilt. All errors are part of the bumpy road. I don't see myself as a victim. We all need to use skippie as an example...thousands of frustrated posts, acceptance of his fate, and purchase of a new tablet.

 

But if you are still reading, skippie...looks like there may be life in this sucker after all!!!

 

Developling without guilt? Absolutely...

 

To avoid it however it's not enough to say "use it at your own risk"...you have to provide all the necessary info in a very hard to miss it fashion.

 

- There still isnt the slightest warning here, i.e. the start of the thread, that once you flash the ROM, there is no way back.

- More can be done to tell people what they must avoid doing BEFORE getting into the process, make sure it can't be missed.

 

Yes everyone took a chance flashing a test-Custom rom, BUT

- for one I wouldn't have if I knew there was no way back and I read the threads here and still didn't know it until recently. It needs to say it win big block letters

- tell people what they must not do before getting into the process, because lots of people get into the steps and then realize they have done something wrong.

 

To develop without guilt you have to take measures and provide all info, then leave it for people to decide what to do.

  • Upvote 2

Share this post


Link to post
Share on other sites

Developling without guilt? Absolutely...

To avoid it however it's not enough to say "use it at your own risk"...you have to provide all the necessary info in a very hard to miss it fashion.

- There still isnt the slightest warning here, i.e. the start of the thread, that once you flash the ROM, there is no way back.

- More can be done to tell people what they must avoid doing BEFORE getting into the process, make sure it can't be missed.

Yes everyone took a chance flashing a test-Custom rom, BUT

- for one I wouldn't have if I knew there was no way back and I read the threads here and still didn't know it until recently. It needs to say it win big block letters

- tell people what they must not do before getting into the process, because lots of people get into the steps and then realize they have done something wrong.

To develop without guilt you have to take measures and provide all info, then leave it for people to decide what to do.

Couldn't agree more.

+1

Unleashed by my Nexus 4

  • Upvote 1

Share this post


Link to post
Share on other sites

Hi all,for me, I is not had a problem to go way back.
I have setup several times, the ROM de Stan1983 and now I'm with the ROM Rosak 1.1.0.
--------------------------------------------------------------------------------------------------------------
!!! ( the version kitkat is not good for the onda  V975M V3 ) !!!

!!! ( the version kitkat is good for the onda V975M V1 ) !!!

kitkat android 4.4  version (2.0.1) is a beta version for onda V975M V3

android 4.3  version (1.1.0) is a official version for onda V975M V3
--------------------------------------------------------------------------------------------------------------
it's For this reason, I asked to Stan1983, if it was possible to make a ROM Stan1983,
for the onda V975M V3 with the ROM 1.1.0 official.


for réinstall others ROM, use Case B - Clean install :

Link :

Share this post


Link to post
Share on other sites

I guess you're right to some extent definito...the signs on this highway sometimes don't lead to the desired destination. Although there is a lack of clear RED PRINT warnings on the first page, I hope newcomers will read the entire thread before proceeding...the warnings are all there...sadly from some of us "early adopters".

 

As for me...I'm hoping for the uart solution to at least get some life...then final rom flash and leave well enough alone. Then maybe a Cube X9 for Christmas!!!

Share this post


Link to post
Share on other sites

There currently is no way to fix this problem. These are modified drivers for another chipset made to work with the AMLogic SoC. Hopefully Stane can find or build a better driver in the future.

So, if I'm correct...there's no way to find or get this WiFi card drivers...

Share this post


Link to post
Share on other sites

Tried again once more, loop install, then i take out the sd card, boots into stock recovery.

Then i put sd card back, try to install through recovery : error : 

 

script aborted (no error message)E:Error in /tmp/sideload/package.zip (status 7)

Installation aborted.

  1. E:failed to mount /cache (Block device required)

E:Can't mount /cache/recovery/log

E:Can't open /cache/recovery/log

E:failed to mount /cache (Block device required)

E:Can't mount /cache/recovery/last log

etc .....

Share this post


Link to post
Share on other sites

Does anyone find a way to boost the sound volume?

Viper4android app, but it's not available from Play Store, you have to Google it.

  • Upvote 1

Share this post


Link to post
Share on other sites

Can you tell me what to do after install it?

Thank you.

It's not that technical, I set mine up using phone speaker, enable equalizer and select small speakers, enable speaker optimization and extra loud and extreme effect strength.  If you want to get real technical open settings and select moderate or expert. Hope this helps.

  • Upvote 1

Share this post


Link to post
Share on other sites

UART (Universal Asynchronous Receiver Transmitter) is a serial communication interface. You may know it as RS232 port or COM1, COM2 ports.

What stane means is that you have to use a serial debug interface like the USB debugging interface PL2303HX for ~$2.43 or ~€2.85 (easy to be found @Amazon).

This is a TTL level to USB interface. You must not connect a standard RS232 port to your tab because the tab uses TTL level (0V/5V) output and the COM port of your PC uses RS232 levels (-10V/+10V).

You have to solder it to the internal GND, Tx and Rx pins of the debug port inside the V975m.

Then you have to open a terminal program like Hyperterm or Realterm and configure the port to communicate @ 115200,8,N,1 and no hardware handshake.

If you turn the tab on you will see the startup messages.

Here is a VERY short excerpt of stanes bootloader startup:

System Started


U-boot-00000-ga234870-dirty(m8_k12_MA975M8_v1@20140823) (Sep 17 2014 - 22:42:57)

clr h-ram
DRAM:  2 GiB
relocation Offset is: 6fec0000
show partition table: 
part: 0, name :       logo, size : 2000000
part: 1, name :   recovery, size : 2000000
part: 2, name :       misc, size : 2000000
part: 3, name :       boot, size : 2000000
part: 4, name :     system, size : 40000000
part: 5, name :      cache, size : 10000000
part: 6, name :       data, size : end 
aml_card_type=0x0
MMC:   [mmc_register] add mmc dev_num=0, port=1, if_type=6
[mmc_register] add mmc dev_num=1, port=2, if_type=6

The communication runs in both ways and as you use a terminal program you can also send characters/commands to the tab.

But you first need to interrupt the boot process or the bootloader will not accept any commands from your side.

This interrruption is done by sending the "interrupt hotkey" to the tab during startup. Commonly used hotkeys are space, escape or enter.

I tried all of them and none seems work. Unfortunately there is no standard for the hotkey and even not implemeting this interruption at all is possible too.

The hotkey is defined in the sources of the bootloader - and as only stane has the sources he is the only person who could tell us this secret hotkey...

 

Hi,

 

there is no secret hotkey. Pressing enter is enough. If that does not work, either you're not fast enough or TX line does not work. I did not solder anything to my tablet or opened it... I do have Amlogic debug card which connects to device via sdcard slot. That connected to PC via USB cable allows me to access UART console.

  • Upvote 1

Share this post


Link to post
Share on other sites

It's not that technical, I set mine up using phone speaker, enable equalizer and select small speakers, enable speaker optimization and extra loud and extreme effect strength.  If you want to get real technical open settings and select moderate or expert. Hope this helps.

Yes. It helps a lot. Thank you :)

Share this post


Link to post
Share on other sites

It's not that technical, I set mine up using phone speaker, enable equalizer and select small speakers, enable speaker optimization and extra loud and extreme effect strength. If you want to get real technical open settings and select moderate or expert. Hope this helps.

i set up it with no effect on songs or videos volume i use mx enable sw only help with mx only
  • Downvote 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By Lukypie
      Hi, I'm back again with another particular guide, this time just for android, which will show how to root every V80 Plus rom, this time for real. You probably know that the other guides are not working anymore due to newer roms adding a new layer of protection against modifications. SuperSU zips can't detect this on Android 5.1 since this is something that is used in Nougat or Marshmellow 

      Also, I will also explain how to use newer roms updates (Like the Android V7 version) and make it work on V3 (My tablet) since there are minor hardware changes like the Wi-Fi chip and the touchscreen vendor, I will show how to port the V3 drivers on the V7 ROM which is more stable, and smoother.

      Prerequisites:
      Unix environment (Linux, MacOS, Cygwin/MinGW on Windows) I recommend Manjaro Linux, the AUR has all the programs we need here. ADB and Fastboot https://github.com/xpirt/img2sdat https://github.com/ggrandou/abootimg Unlocking bootloader Decent knowledge of ROM tweaking or at least in theory Basic Unix-like systems knowledge A BACKUP,  you will lost all data on your device By following this guide I take no responsibility on device bricks or data loss
       
      Common steps for both ROM tweaking and Rooting
      The first thing you have to do is to unlock the bootloader, reboot your tablet from Android and press the down button to access the fastboot mode, then connect via USB the tablet to a PC, you have to enter this command in order to unlock the bootloader (You can also use this tool) also if you want to install TWRP follow his guide. ' fastboot oem unlock '
      You will lose all data after oem bootloader unlocking
      Now you have to extract your ROM boot.img by downloading the correct ROM image (http://onda.cn/search.aspx?keyword=v80%20plus) and using abootimg in Linux/MacOS/Cygwin/MinGW, I won't explain how to compile it.

      What we have to do is basically extract the initrd and changing ro.secure=0 o ro.secure=1, which will allow for supersu to install without bootlooping and mounting system as rw, using modified system.img's and disable the protection which will put the device into a bootloop state
        Type the following command to extract the boot.img (You must be on the same folder where you downloaded the boot.img)
        ' abootimg -x boot.img '
      Now several files are created, we need to extract the initrd, put ' abootimg-unpack-initrd initrd.img '
      Go into the ramdisk folder and look for default.prop, open it with a text editor

      change ' ro.secure=1 ' to ' ro.secure=0 '  in the previous folder, type ' abootimg-pack-initrd initrd.modified.img '
      This will create initrd.modified.img which includes your modifications, now you have to create a new boot.img with the modifications you made, with this command ' abootimg --create boot.edited.img -r initrd.modified.img -k zImage -f bootimg.cfg -c "bootsize=xxxxxx" '

      Please note that in xxxx you have to put the new boot.img size, you can get the exact string by omitting the -c "bootsize=xxxxx" argument, which will give an error that will tell on the left the size you need to put, in my case it was 

      ' abootimg --create boot.edited.img -r initrd.modified.img -k zImage -f bootimg.cfg -c "bootsize=11868160" '
      for the V5 Kernel
       
      If you have done everything correctly, we got a working boot.edited.img, to flash that into your device you need to go back to the bootloader like when we oem unlocked the device. Put this command from a PC ' fastboot flash boot boot.edited.img ' 

      Rooting
      If everything went good, you just need to try to install supersu by flashing it with twrp or trying to mount as r/w the /system partition and see if it bootloops, if the rom does not even boot at all even if you just flashed the boot.img you did something wrong.
       
      ROM Tweaking and porting Vy android firmware version to Vx tablet

      Since I got really mad and frustrated by ONDA not releasing firmware also for older hardware revisions (Other may work for your older device, other may not) I decided to extract the drivers and firmware and put them to a newer rom, and it is worth the score. New firmwares are more smooth and stable.
      As you know, some newer VX firmware ROM may not be compatible with your VY hardware revision device, in my example I had the V3 and I managed to use the V5 drivers (The V5 version works good with the V3 tablet hardware rev) to use the V7 firmware. 
      This may probably work also with a V5 tablet.
      Don't know if this works with V1

      Extracting drivers and files needed
      Boot.img patching: In order to get drivers working, make sure you followed the steps for creating the modified boot.img kernel which works on your device, cause it is mandatory or you will get a bootloop.

      Q: Can older boot.img/kernels work with newer/older firmwares?
      A: Yes, they seems to be pretty similiar so in my example I used V5 boot.img in order to get drivers working for the V7 ROM which has a slightly different hardware
       
      Without extracting the following files and firmware you will just have the touchscreen working, but not the wifi or the bluetooth, they require firmwares located into system files! And Without the boot.img you can't do anything with the new rom!
       
      Once you downloaded every ROM you need, in my example I had the V3 Hardware revision, I will put V5 drivers which works too on V3 into the V7 ROM, this time we need to find and extract the system.img using simg2img by using this command, easier than saying it. ' simg2img system.img system.img.raw ' 
      Now mount it as read-write with, ' mount -o rw system.img.raw /mnt '

        Firmware extracting
       
      I needed to extract the following files in order to have everything, copy them on the desktop, if unsure you could copy everything like /etc /lib/ /vendor / because I can't know if you are trying another ROM revisions, because they may require different files, find yours by yourself!
      (This may be a lot of trial-and-error but the files should be the same, you could try that also with V1 to V5/v7,  tell me if it works! Idk about other hardware revisions!)
      --------------------------------- V5 ROM ----------------------------------------
        /mnt/vendor - Other blobs needed  /mnt/bin/wpa_supplicant - Needed for the wifi correctly working /mnt/etc/firmware - Proprietary blobs dirvers needed for Wifi, bluetooth and other things to work. /mnt/etc/sensor_hal_config_default.xml - Needed in order to the accelerometer to work. /mnt/build.prop - Needed if you have problems with some apps like Facebook. /mnt/lib/hw/bluetooth.so - In order to make bluetooth working

      ------------------------------------------------------------------------------------ System.img patching
      Once you got those files, do the same simg2img command with the system.img ROM you want to put the drivers on, in my case the V7. Mount it with read-write on /mnt or everywhere you like, then patch all the files by copy-pasting the one you extracted before and replacing them on the new ROM using a file manager with root permissions like thunar, nautilus or pcmanfm  
      tl;dr, what I did? 
      Extracted the two system.img's of two different roms Copy-pasted and replaced the files I told you before from the working V5 ROM (Even owning the V3 one but that has the same hardware of V5 I suppose) to the newer V7 rom I want to use is that hard?

      System.img repacking and flashing
      Make sure you unmounted the system.img.raw by ' umount /mnt ' put this command  ' img2simg system.img.raw system.edited.img ' 
      Now you just need to flash it like the boot.img before, so ' fastboot flash system system.edited.img ' ' fastboot reboot system ' 

      If everything went good , you will reboot into your fresh-new system! Stable if you compare the first sh*tty firmwares they made, there are less slowdowns and bugs like the strecthed windows in the multitasking area.


      Downloads:
      Modified V5 boot.img: https://mega.nz/#!OlgygJjK!wTv2L9yfCGsqkV7ShGX4Cub-EGdvh3ROtuZxvMzVGoM
      Modified V7 system.img to make it work with V3 using V5 firmware: Soon...

      If you made your own working, please tell me, I will put the links, just specify the ROM and the source drivers you used! 
       
      Useful commands:
      From Fastboot: 
      fastboot format system - Formats the android systems Warning: it does not reset the phone, if you reboot you won't have any android system fastboot format data - Formats the /data folders (Program files like apps data) -  It does a factory reset, but the ROM will still be the same. fastboot format userdata - Formats the /sdcard folder fastboot reboot system - Reboots into Android fastboot reboot recovery - reboots into recovery From android:
      ' adb reboot recovery '  Reboots into TWRP ' adb reboot system ' Reboots normally  'adb reboot bootloader ' - Reboots into fastboot
       
    • By diegogyn
      First the Original ROM can be found at: http://www.onda.cn/Tablet_Supports.aspx?id=344 To download use JDownloader 2, copy the link and past on it that will work  
      There are 3 ROMs But attention the first one just works on the ONDA 80 SE V1 (You can check at the back bottom of the tablet)  
      What I've discovered so far is this tablet has a kind of UEFI BIOS, that means for you can enter on configuration to reset you will need an OTG Cable and conecta a keyboard on it. So I´m trying to discovery more about how to put another room on it, there is some tips on the files at the site but i´m not very sure how to do it. I just trying to do this because my battery status is really messy, I try to use root but to fix but it did not worked.  
      If anyone knows anything please let me know, I will continue researching and updating this topic.
    • By nicolaslienart
      Hi everyone,
       
      I have Onda V919 air Dual OS but it's stuck in bootloop. I've tried to fix it by flashing the firmware but I'm unable to do so.
      Maybe I don't have the correct firmware, I took it from XDA because I can't find it in download section of this forum.
      Check attached files to see a picture of the back of my tablet and the error I'm getting when flashing.
      Thank you for your help,
       
      Nicolas
       
       
       


    • By jambbo
      Hi,
      Is there any Onda air v989 v5 firmware to download? I didn' find any.;(
    • By Eardstapa
      Hi everyone - does anyone know if there's a custom recovery available for the OBook 10 SE? Anything like TWRP or CWM? If not, is there any other way to backup my tablet before trying to re-flash Remix OS 2.0 from Jide?
×