Jump to content
Onda Forum
Gearbest 20$ OFF OVER 100$ GearBest CLEARANCE SALE promotion
20$ OFF OVER 100$ GearBest CLEARANCE SALE
SciBee

HowTo - Create a bootable SDCard for V975M

Recommended Posts

Hy!

 

I follow the instrucion, but the tab don't boot from the sd card. It uses the default recovery, not the twrp recovery. It is only a 2gb card, so the other boot version is not option for me. Any solution?

recovery.img (TWRP or original or Philz) has to be in the root of the SDCard!

Simultaneously press Power and Vol+ while the SDCard is in the socket.

A 2GB FAT32 formatted card is ok for all steps.

If the default/original recovery is booting that should be all you need to install a rozak or stock ROM.

Share this post


Link to post
Share on other sites

recovery.img (TWRP or original or Philz) has to be in the root of the SDCard!

Simultaneously press Power and Vol+ while the SDCard is in the socket.

A 2GB FAT32 formatted card is ok for all steps.

If the default/original recovery is booting that should be all you need to install a rozak or stock ROM.

 

Hy!

Thank you! So, i would jump straight to "Part2 - Install a different ROM",becouse i have an original ROM. Am I right? (sorry if, I am a bit irritating, but I woldn't like brick my tablet).

Share this post


Link to post
Share on other sites

Hy!

Thank you! So, i would jump straight to "Part2 - Install a different ROM",becouse i have an original ROM. Am I right? (sorry if, I am a bit irritating, but I woldn't like brick my tablet).

 

Ok. Then I tried the part 2 all files on the bootable SD card, but nothing special happens (obviously pressing Volume+ and power buttons): IMG_20150511_153756.jpg

Share this post


Link to post
Share on other sites

I think you perfectly misunderstand what booting off the SDCard means in the Android world.

This just means that the bootloader on the SDCard is started instead of the bootloader in your internal NAND. You need that in case your ROM is corrupted or your partitions on your NAND have been deleted and your internal bootloader is not working anymore.

The bootloader just grants some basic hardware support.

It's more or less like the Bios on a standard PC.

After the bootloader has started it boots either a recovery: internal or on the SDCard - or the ROM: ALWAYS on your NAND!

There are some devices/ROMs indeed booting off the SDCard - but not this device and none of the available ROMs.

So in fact you will always get a recovery - no matter if you boot the SDCard or the internal NAND by pressing Power-Vol+.

This recovery, which is some kind of independant OS is needed to install any ROM on your device.

It's like booting a PC using a Windows installation DVD.

Bios=bootloader

WinPE=recovery

WinPE then installs your e.g. Win8.1 (=ROM) on your harddisk.

 

Original ROM means stock ROM by onda.

It seems you started Philz recovery which is not suitable to install a stock or rozak ROM.

So first decide which ROM you want to install and then put the appropriate files on the SDCard or for stane1983 ROMs use the USB burning tool without a SDCard.

Installation guides are always in the opening posts (OP) of the corresponding threads.

Share this post


Link to post
Share on other sites

I think you perfectly misunderstand what booting off the SDCard means in the Android world.

This just means that the bootloader on the SDCard is started instead of the bootloader in your internal NAND. You need that in case your ROM is corrupted or your partitions on your NAND have been deleted and your internal bootloader is not working anymore.

The bootloader just grants some basic hardware support.

It's more or less like the Bios on a standard PC.

After the bootloader has started it boots either a recovery: internal or on the SDCard - or the ROM: ALWAYS on your NAND!

There are some devices/ROMs indeed booting off the SDCard - but not this device and none of the available ROMs.

So in fact you will always get a recovery - no matter if you boot the SDCard or the internal NAND by pressing Power-Vol+.

This recovery, which is some kind of independant OS is needed to install any ROM on your device.

It's like booting a PC using a Windows installation DVD.

Bios=bootloader

WinPE=recovery

WinPE then installs your e.g. Win8.1 (=ROM) on your harddisk.

 

Original ROM means stock ROM by onda.

It seems you started Philz recovery which is not suitable to install a stock or rozak ROM.

So first decide which ROM you want to install and then put the appropriate files on the SDCard or for stane1983 ROMs use the USB burning tool without a SDCard.

Installation guides are always in the opening posts (OP) of the corresponding threads.

Thank you for the anwer. But my situation: i tried first run the twrp recovery without install, becouse of testing the botable sd card. It doesnt work, i got only the factory version of recovery. I tried to install the most rated rozak ROM  (20140515) too. All nessesary files with corect name in the root of a bootsble sd card but i got only the factory recovery again (doesnt start the installation).

Share this post


Link to post
Share on other sites

To run TWRP the SDCard does not need to be bootable.

Just download the TWRP version mating your installed ROM. You need the mating version because of the partitioning scheme. Stock and rozak differ from stane1983.

Extract the *.img file from the installable zip.

Rename that file to "recovery.img" and copy it to the root of your SDCard.

That's all.

If the stock/integrated recovery is booted if you press Power-Vol+ instead of the one on your SDCard it seems that your SDCard is not readable by the bootloader.

Is it FAT32 formatted? A 2GB card can also be formatted as FAT16 and I don't know if that works too.

Is the card readable in the tab when your normal Android system is started?

Share this post


Link to post
Share on other sites

To run TWRP the SDCard does not need to be bootable.

Just download the TWRP version mating your installed ROM. You need the mating version because of the partitioning scheme. Stock and rozak differ from stane1983.

Extract the *.img file from the installable zip.

Rename that file to "recovery.img" and copy it to the root of your SDCard.

That's all.

If the stock/integrated recovery is booted if you press Power-Vol+ instead of the one on your SDCard it seems that your SDCard is not readable by the bootloader.

Is it FAT32 formatted? A 2GB card can also be formatted as FAT16 and I don't know if that works too.

Is the card readable in the tab when your normal Android system is started?

 

Yep. I think i tried all combinations :D . FAT32, and when I tried the rom, i used the ROM's "u-boot.bin" file for the process. When the card is in the tab, it can  be read and written. But the rovery don't see the files from sd card, only from the internal memory (it seems, it don't recognise absolutely the sd card). So it would bo good to flash the ROM without sd card.

Share this post


Link to post
Share on other sites

The procedure worked for many people - including me - so it's obvious that there is a problem with your SDCard.

Either you get a new SDCard or you try to install the ROM via OTG USB stick. Don't know if Philz supports that...

Boot the integrated recovery and install the ROM from the USB stick.

Please post the type of your SDCard. That would prevent other users from falling into the same trap.

Share this post


Link to post
Share on other sites

The procedure worked for many people - including me - so it's obvious that there is a problem with your SDCard.

Either you get a new SDCard or you try to install the ROM via OTG USB stick. Don't know if Philz supports that...

Boot the integrated recovery and install the ROM from the USB stick.

Please post the type of your SDCard. That would prevent other users from falling into the same trap.

 

 

It's a very basic sd card (San Disk with no other information on the surface, if my memories are right, becouse now I'm not at home). 

My recovery and all of software on the tab are fully original, factory version. 

Now i put a card from the phone to the tab, it recognise correctly, but in recovery it looks like, it wasn't instert. Same with a pendrive. So it looks like the best way is, that i avoid the sd card ROM installing. But i don't recognise other version of ROM installing. And after 2 week non stop thinkig, searching and testing, i would give up all, it looks like impossible. But the problem is that, in this condition the tab is almost useless becouse of the ridiculous cpu clock limit. It's freezing, lagging and somtimes just exit from an app.

Share this post


Link to post
Share on other sites

I suggest to install stane's KK ROM then.

You install it via USBBurning tool without the need for a SDCard.

But you have to use the USB version here:

Use the instructions in the second post.

But be warned - as this installation replaces your stock boot loader and writes a new partition layout to your NAND there is a noticeable risk for a brick.

Share this post


Link to post
Share on other sites

 

I have great news and good news. :D :cool: :D :P :D :cool:

Looks like I finally have my working tablet.

I have achieved this by following, one by one, all the unbrick procedures described in the post http://hispatablets.com/onda-v975m/onda-v975m-t585.html

Exatcly the one called "Desbirckeo para pantalla en negro - u-boot MOD Metodo de Rozak"

 

I created the 3 files described in the post,

erasebd.xml

    <?xml version="1.0" encoding="UTF-8"?>
    <progress_configs>
    <command sn="0">store init 3</command>
    <command sn="1">store erase boot</command>
    <command sn="2">store erase data</command>
    <command sn="3">reset</command>
    </progress_configs>

config_progress_erase_my.xml

    <?xml version="1.0" encoding="UTF-8"?>
    <progress_configs>
    <command sn="0">mmcinfo</command>
    <command sn="1">store init 3</command>
    <command sn="2">fatload mmc 0 0x10100 u-boot.bin</command>
    <command sn="3">store rom_write 0x10100 0 60000</command>
    <command sn="4">mw 0xc8100004 0x01010101</command>
    <command sn="5">reset</command>
    </progress_configs>

fullerase.xml

                    <?xml version="1.0" encoding="UTF-8"?>

    <progress_configs>
    <command sn="0">mmcinfo</command>
    <command sn="1">store init 3</command>
    <command sn="2">store erase boot</command>
    <command sn="3">store erase data</command>
    <command sn="4">fatload mmc 0 0x10100 u-boot.bin</command>
    <command sn="5">store rom_write 0x10100 0 60000</command>
    <command sn="6">mw 0xc8100004 0x01010101</command>
    <command sn="7">reset</command>
    </progress_configs>

I downloaded the Amlogic Image Burning Tool v.1.6.2.0128 http://www.v975m.com/downloads/upload/_USB-Burning-Tool%201.6.2.0128.7z or http://www.ondaforum.com/files/download/28-usb-burning-tool-v1621228rar/

 

I followed the steps described but I have the flash loop always.

 

I tried to re-flash the stane Rom using USB_Burning_tool and in this occasion the soft has been able to erase the bootloader and the flash operation is finished without problems.

 

Now I can restart, power off, install TWRP, start in recovery mode without problems.

 

Now I'll try a few days to verify that no other error exist.

 

I want to thank all of you for your invaluable help. Especially SciBee, Rozak for their unbrick methods (that are the ones used in hispatablets once translated) and Stane1983 for his rom.

 

 

Thanks, that hispatablet posting (together with Google Translate) revived my tablet today using "config_progress_erase_my.xml".

First I thought nothing worked... then I left the tablet alone for an hour... when I returned, it was in a bootloop with the Android robot with the spinning cube (?) !!

Then I was able to use the Amlogic Burning tool after all.

[all of this was started because I tried to go back from Stane1983 1.0.0 Beta back to 0.9.2...]

Share this post


Link to post
Share on other sites

I suggest to install stane's KK ROM then.

You install it via USBBurning tool without the need for a SDCard.

But you have to use the USB version here:

Use the instructions in the second post.

But be warned - as this installation replaces your stock boot loader and writes a new partition layout to your NAND there is a noticeable risk for a brick.

Thank you! It seems now, not the sd card makes the issue, becouse I can't reach "the small droid picture". I follow accurately the instructions (driver install too) but even after the 10th time i got the recovery menu (what i uploaded earlier). If I'm right i would get at the sd card version "the small droid" too, so i think it's something with the software (or i do a little mistake every time, but I think the chance of this is little, 'couse I do everything step by step following the instucions).

Share this post


Link to post
Share on other sites

Bootable image does not fit my 16GB Sdcard..  Is there anything Im doing wrong or i should know. I have my tablet Bricked ( my 975m ) and my laptop cannot recognize under windows xp.. Even when on my pc with windows 7 I get a low power error even after its been charged using USB burning tool. I ran the 3 .xml scripts already friom my pc.

 

Any help would be greatly appreciated as Im searching all over forum for solutions.

Thanks in advance..

 

Pete

Share this post


Link to post
Share on other sites

Thank you! It seems now, not the sd card makes the issue, becouse I can't reach "the small droid picture". I follow accurately the instructions (driver install too) but even after the 10th time i got the recovery menu (what i uploaded earlier). If I'm right i would get at the sd card version "the small droid" too, so i think it's something with the software (or i do a little mistake every time, but I think the chance of this is little, 'couse I do everything step by step following the instucions).

First you should tell us what you try to do.

Which ROM do you want to install? Which way?

If you use the method of this thread (part2) you should see the little droid.

Share this post


Link to post
Share on other sites

Bootable image does not fit my 16GB Sdcard..  Is there anything Im doing wrong or i should know. I have my tablet Bricked ( my 975m ) and my laptop cannot recognize under windows xp.. Even when on my pc with windows 7 I get a low power error even after its been charged using USB burning tool. I ran the 3 .xml scripts already friom my pc.

 

Any help would be greatly appreciated as Im searching all over forum for solutions.

Thanks in advance..

 

Pete

This thread is not for the hispatablets method. I did not try that - so I can't help here.

 

This thread will only work if you want to install rozak or stock ROM.

You do not need to use the bootable image. Use the "easy way" instead.

 

Next will only help if you want to install a stane1983 ROM:

Concerning the low power message: we also had that if people did not use the original cable (it uses thicker wires) or a USB3 port or USB ports behind a hub.

Open your device manager. Switch the view to devices by connection and locate the tab. Try different ports. The less hubs in between the better.

Share this post


Link to post
Share on other sites

Bootable image does not fit my 16GB Sdcard.

Exactly what image are you talking about? You mean the image of a bootable SD card? The ones from the hispatablets page are (e.g. SD_unbrick_V975M_V3_1-1-0_STOCK.rar) is only 2 GB...

Share this post


Link to post
Share on other sites

Exactly what image are you talking about? You mean the image of a bootable SD card? The ones from the hispatablets page are (e.g. SD_unbrick_V975M_V3_1-1-0_STOCK.rar) is only 2 GB...

Im using image unpacked as per SciBee's instructions..  Botable image is approx 16 GB...  

Where can I find download link to hispatablets page.. My spanish no good...

 

Also Links are dead, my 975m is V1

 

 

 

my error

[HUB7-1][0x00102002]UBOOT/Lowper/Send command/USB Control setup error

Share this post


Link to post
Share on other sites

First you should tell us what you try to do.

Which ROM do you want to install? Which way?

If you use the method of this thread (part2) you should see the little droid.

 

Basically I tried 2 versions of ROMs. Both are your offer. 1) Rozak's 20140415 version with SD installing 2) stane's version with burning tool. Both situation: i did everything following the instuctions. But both version ended with this problem: when i press, hold and realese volume+ and power buttons  (and the secound version connect the cable) the tablet runs only the recovery menu, no spinnig cube with little droid. My phone behaved so, when I used wrong key combinations, but in this case I press volume+ and power like in the desciptions.

Share this post


Link to post
Share on other sites

my error

[HUB7-1][0x00102002]UBOOT/Lowper/Send command/USB Control setup error

 

I've got this kind of error when I put my tablet into recovery mode Before I've started flashing.

 

So method is: power off tablet -> connect to pc/notebook USB port (any) -> Start USB Burning tool -> set language to English -> load image (for me stane1983 0.9.2 ROM worked) -> Click Start -> Push Volume+ and Power button on tab till PC/Notebook recognise (appear in device manager) -> driver installing automatically -> when USB Burn Tool recognise tablet, flashing start automatically. -> when finished, stop USB Burn tool -> press Power button till tablet turn off (dissapeare from device manager) -> unplug tablet from PC/Notebook -> Turn on tablet with pushing Power button.

 

If you had done everything right, it will start with flashed ROM

Share this post


Link to post
Share on other sites

Still getting same error.. Low Power.. Tablet has been charged and same..

 

I had similar errors. You might try to follow this tutorial:  , which is basically the same procedure as described in the hispatablet forum.

Using this method resolved my strange USB errors.

Some people advise to use a XP pc (instead of later versions) and no USB 3.0 port; I assume you have tried a different USB 2.0 already (?)

Share this post


Link to post
Share on other sites

I managed to hard brick my tablet. Trying to solve this by using scibees methods I noticed the aml-files can no longer be downloaded. Can anyone reupload them?

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 thedozyone
      Hi
      I wonder if there is a new firmware available for the Onda 20 Plus?
      I found this one Firmware update?
      But not sure how to patch it or if it's even legit
      I'm still trying to resolve my windows sd card issue
       
      Thanks
       
    • 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 erturk
      Hi,
      I was using my onda v80 plus without any issue however one days it suddenly powered of and it couldnt boot again. So, I tried to install windows and failed, also tried to install Android and failed too.
      (Windows couldn't format the drive and Android couldn't create partitions on device blocks)
      After searching for problem, I got a clue that targets eMMC. It seems eMMC device is corrupted. I tried to perform checking tools on eMMC but nothing could fix it. 
      Now, I changed my scope, because seems impossible to fix eMMC device, and decided to install windows on SDCARD device. But, windows installation unfortunately unable to recognize card reader and I need to find driver of sdcard reader.
      Is there any body to help me or assist me to solve this problem?
      Thnx,
×