Hi,
I'm a noob, have tried looking online and in these forums for answers, but am getting lost and am finding myself in over my head. So please be patient with me.
I have an Onda v891w CH V1 tablet with a quad core Z8300 that runs an English Windows 10 and Android 5.1. In a bold attempt to root my Android install, I ended up bricking my device. It now gets stuck on the animated logo screen when booting and never boots either of the 2 operating systems.
I've been browsing online and found a few guides for Onda tablets, but most deal with different models or different versions of the v891w (like the V5, or the Z3735 processor). I believe I've managed to find an Android rom or firmware for my device here, but I'm unable to install it. I'm very likely doing something wrong, I just can't figure out what.
First of all, the thread talks about pressing ESC or F7. I've tried hooking the tablet up to a powered usb hub, along with a usb keyboard and the content of the V891W CH中性固件（适用于V1版本32GB）-20160701.zip file on a usb key. Unfortunately I'm not able to get into the BIOS. I suspect that the usb hub doesn't supply enough power for all the devices. It's an EasyAcc D70 7 port hub with a 5V input.
I noticed in the replies in the thread I mentioned above that people were flashing img files from fastboot, so I've tried booting my tablet in bootloader mode, unlocked the bootloader using the command flashboot oem unlock and tried flashing the boot.img and/or system.img files from the archive using the commands fastboot flash boot boot.img and fastboot flash system system.img. That results in the error FAILED (remote: Flash failure: Not Found). On the tablet it says Failed to get partition boot: Not Found
I'm not sure what to try at this point. If there's anyone who wants to take pity on a newbie and walk me through some step by step instructions on what to try, I would be very grateful.
Update: I've now also tried an Anker 60W 3 PowerIQ Hub to connect the keyboard with the tablet and the usb key, without success. Both the Anker and the EasyAcc USB hub are powered hubs. I could really use some advice on how to get this Onda tablet back operational.
Related
I have a Malata T2 with 3g and have been happily trying many of the excellent roms in development from here with no problemes. I thought i'd therefore try the new 1.2 Build T2 3g rom from the download section of the malata.com web-site but messed up and downloaded the T8 3g rom by mistake but didn't spot this until after I had run the NV Flash.
The T8 rom loaded so far but then bricks at the honeycomb screensaver (and the left half of the screen is poor resolution and the right side is a solid white block).
I have obviously tried re-connecting to my laptop so I can re-flash the Flashback rom I had been running but the tablet no longer goes into the recovery mode when starting up whilst holding down the + button; and no longer cannoect to the laptop properly if starting up whilst holding the '-' button.
If connecting to my laptop as I would to flash a rom, my windows 7 laptop makes the normal usb connection sound and recognises the tablet as the Nvida Harmony in my connected devices. However, the laptop now shows a problem with the tablet and when i check the properties it states that the 'WPD FileSystem Volume Driver' has an error code 10 and that the device cannot start. This is preventing me re-flashing an alternative ROM via NV FLASH and when i try to, the nv flash programme says that there is no tablet connected to the laptop.
Obviously, the biggest problem with the tablet is the nube idiot who mucked around and got out of his depth(... me!) but is there anyone on this forum who can help me out and tell me how to get the tablet back to the point where I can communicate with it from my laptop and nvflash a T2 rom again!
Any help would be greatfully appreciated.
Turbo_kf
Try doing the nvflash on Linux. Follow instructions in this post and run a live CD.
1. You will have to use a Linux version of the nvflash utility that you use on the T2. And, before you ask: I don't know if the Linux nvflash program for the gTab will work on the T2. It may; it may not.
2. After you've booted into the Linux desktop, download all the files needed somewhere. I recommend putting it all--both the extracted .img files and the nvflash program--into some directory in /tmp, say /tmp/nvflash-t2. Boot the T2 into APX mode, run the Terminal Emulator, then type:
Code:
$ [B]cd /tmp/[I]nvflash-t2[/I][/B] [I]Change to dir containing all files[/I]
$ [B]sudo ./nvflash [I]... [/I][/B][I]Run nvflash with superuser permissions[/I]
anyone else have a solution that doesn't involve running linux cd's
okay with windows, but not with linux
still stuck
I have taken the advice, run the linux cd and still cant rescue it. From shell, i can see it is there at ./dev/sdb and it sees the tablet when i type lsusb. But when i try and run the correct malata linux nvflash or other g-tab linux nvflashes, it starts up but then tells me that it is an 'unknown device' before terminating the nvflash.
Any suggestions... going of on holiday next week and woukd love to have it recovered by then
Turbo_kf said:
But when i try and run the correct malata linux nvflash or other g-tab linux nvflashes, it starts up but then tells me that it is an 'unknown device' before terminating the nvflash.
Click to expand...
Click to collapse
1. Most likely, you did not put the T2 into what's called APX mode--this is a common mistake. Please, read my original post more carefully.
Also see this post for more info (it's for the gTab, but, it may also apply to the T2).
2. Did you use the nvflash for the T2 (if one exists)? What were the exact commands you used?
still stuck... cant get apx mode
I can assure you that i have been trying to get APX mode from the moment it went wrong ...the inability to get APX mode no matter what i try is where the problem is.
i have run the adb.zip i read about on this forum and run dmesg on both the shell (dmesgshell.txt) and normal (dmesgnvid.txt) and have attached the two outputs.
There is clearly some software problem with having run the T8 rom that is preventing the T2 tablet form going into APX mode and a noobie like me just doesn't have the knowledge to work out what i do now...
any help in how to restore the APX mode so i can flash back the malata T2 stock base1.2 rom would be appreciated.
Thanks
Hi guys, I just got an used Kyros 7022 from eBay and while trying to install a custom firmware I unplugged the USB cable during the process by accident and now my tablet has a black screen, nothing shows up, when I plug it to the computer Windows will detect it as "Telechips TCC88xx VTC USB Driver" but I'm not able to flash it using the FWDN software because it throws an error message:
[ERROR] CFwdnDownload::Open_BOOT:No Boot File error!
[ERROR] CFwdnDownload:Load_UBS: Open BOOT Error!
I tried to restore to the stock rom but ADB.exe and FASTBOOT.exe will NOT detect the tablet even though Windows detects it and it is displayed under the device manager.
I would appreciate any help,
Thanks
I've done the same thing
I've managed to do the same thing on my Kogan Agora 8' (TC8803)
Have you had any luck fixing it?
My screen is black, cant get into fastboot/adb and FWDN fails aswell (FWDN tool V7 Open_BOOT: No Boot File error! Load_UBS: Open BOOT error! or if rom specified I get ERR_FWDN_UBS_ROM_LOAD_CRC_ERROR), even when shorting pins 7 & 8 (which did work previously until I put the wrong lk.rom on)
I have also looked through the Kogan Agora and TC8803 threads but no luck
Any suggestions welcome!
I accidentally flashed wrong recovery.img to my ATM7021 -based tablet. Now when the tablet is booted it does not boot into OS but into recovery. I cannot get the tablet to be recognized by the flashing program (Tablet Product Tool), before this I had to press power + vol down but now the tablet just boots.
Is the tablet totally bricked now or are there any suggestions?
The tablet can be recognized by ADB, it sees it when I type:
adb devices
and I can command "adb reboot booloader" but that just resets the device back to recovery.
If you can use adb in the recovery then make use of it!
Adb flash recovery recovery.img. Not sure how that works with mediatek devices, but I'd try to use adb to do something like that. For devices with fastboot it's just fastboot flash recovery recovery.img.
If the recovery works then flash recovery as a zip.
Google on how to use adb to flash recovery, hopefully you'll get it to work.
OK, I didn't know adb can be used to flash, I tried fastboot but apparently it does not work, it can't see the device.
I'll have to Google for instructions, but I do have all firmware files available and there is "apply update from sdcard" or something, can the firmware be just zipped and reflashed? The software I used (to flash and screw up) was Actions Pad Tool or similar which no longer recognizes the device.
Update to this, I tried to zip the recovery image to zip and place it in SD Card. When I power on the device it tried to update from the SD card but it resulted in error, ERR 2 I believe it said.
I do have all .img files which apparently are required for the firmware.
Well no progress so far. I cannot get the tablet to go into flash mode for Pad Product Tool.
However, I read somewhere that if you open the tablet and short two pins of the nand chip the tablet is then forced to go into AFDU mode and Pad Product Tool should then recognize it. Can anyone confirm that this is true and have you succesfully restored your tablet by using this method?
You should've replied with a quote like my signature says so I'd reply you quicker.
I've heard about this pins shorting, but make sure you short the right pins of your very own device as this stuff - when done wrong can kill your device.
Send me the updater-script from the zip that you have made, but first dig the Web for recovery flashable firmware of your tablet. You just might eventually find it.
olokos said:
You should've replied with a quote like my signature says so I'd reply you quicker.
I've heard about this pins shorting, but make sure you short the right pins of your very own device as this stuff - when done wrong can kill your device.
Send me the updater-script from the zip that you have made, but first dig the Web for recovery flashable firmware of your tablet. You just might eventually find it.
Click to expand...
Click to collapse
OK, at this point I must say I have some knowledge about computer but far less about Android firmwares. I only zipped those image files and then tried to install them via sdcard so clearly I did someting wrong then. The firmware files are from the Chinese seller and he keeps telling to flash them via Actions Pad Tool, fails to understand I cannot get the table to flash mode.
Okay, I opened the tablet and apparently the NAND chip is made by Micron?
The code is: 29F64G08CBABA
According to this thread Onda V811 uses same chip:
http://www.androidtablets.net/threads/locate-tf-boot-pins-for-29f64g08cbaba-nand-flash-memory.58072/
And the user in that thread apparently did find correct pins but unfortunately the attachment does not work.
EDIT: Here is more discussion about that:
http://www.androidtablets.net/threads/onda-v811-completely-dead.58060/
Now I have to figure which pins to short.
Weekay said:
Okay, I opened the tablet and apparently the NAND chip is made by Micron?
The code is: 29F64G08CBABA
According to this thread Onda V811 uses same chip:
http://www.androidtablets.net/threads/locate-tf-boot-pins-for-29f64g08cbaba-nand-flash-memory.58072/
And the user in that thread apparently did find correct pins but unfortunately the attachment does not work.
EDIT: Here is more discussion about that:
http://www.androidtablets.net/threads/onda-v811-completely-dead.58060/
Now I have to figure which pins to short.
Click to expand...
Click to collapse
Sorry about the delay. I recently back home and I got all of my stuff sorted just recently, including going through over 90 notifications on xda and that wasn't really encouraging to do, but I finally did that.
I found your SoC datasheet. It's here http://www.datasheet4u.com/share_search.php?sWord=29F64G08CBABA
Try to understand this, maybe it will help you.
Hello,
I've got Chuwi v99i (a nice intel baytrail based tablet with "retina" display). It was running fine until I wanted to root it and modified the ramdisk of boot.img to get rid of "ro.secure" etc.
Although I was sure the new boot.img was compressed and assembled correctly (I double checked all the figures in the bootloader header with a hex editor etc etc.), flashing the modified boot.img bricked the tablet.
I cannot even go into the full fastboot. When I power on the tablet normally it gets stuck on boot logo. When I power on the tablet with volume button pressed, it is still stuck on boot logo, but at least gets listed with "fastboot devices". Anyway, the only fastboot command it reacts on is "fastboot continue" (it reboots then). All others (flash, getvar etc.) end up in "remote failure".
Do you have any idea if it could be fixed? I heard about xfstk downloader tool for intel-based tablets, but one needs special dnx files, which I do not have. I don't even know if it would do the trick.
If there is nothing I can do by myself, being equipped only with a PC and an USB connection, does anybody know anybody who could fix the issue for me???
I would appreciate any hints :crying:
Cheers,
Maciej
Hi, Same problem, Have you find a solution?
I have same problem, did anybody find solution
Hey Everybody!
I am new to this forum, looking for a way to root my trekstor Surftab breeze 9.6 Quad. I already tried out the recommended tools, unfortunately none of them worked out. Is anyone of you aware of a method rooting the tab? Or did anyone already rooted it?
First ofall I am looking for a way to move files and apps to the external sd and delete pre-installed apps. Farther, if possible and available, a custom rom would be pretty amazing.
I'm only familiar to nexus root toolkit on my old nexus 4, otherwise I'm a newbie in rooting.
Maybe there's some of you able to help me. If necessary, I will look up more information on the tablet.
Lucas
Maybe as an Update:
Trying to build a working adb connection using the andorid sdk tools, the surftab is not listed as a device in "adb devices"
Anyone out there who can help me with the tablet?
Alright, new update for today.
I was able to get a driver running and the root-toolkits like KingoRoot, KingRoot, One Click root etc. noticed the device, I even was able to start the rooting, but all of those tools said "Root failed" or "Your device is soild to root".
Looks like those one click solution aren't able to root the surftab. I also tried towelroot and framaroot, both without any success.
I am still looking for help
If you are still interested, I successfully dumped whole eMMC memory from this tablet, so I can send you, for example, the boot partition. You can try patch it with Magisk
The magic
Yes, if it's not difficult for you, you can share the firmware. I will be grateful
Hi!
I attached xz-compressed stock boot.img for you!
Also, I have full eMMC dump, but:
recovery partition data are not usable (overwritten by uncompatible recovery image during mine tests)
no data partition
no platform bootloader partitions mmc0boot0 and mmc0boot1
Trekstor-Surftab-Breeze-9.6-ST96416-1-emmc-dump.dd.xz [1.12 GB]
Decompress and use kpartx tool (need force to ignore omitted data partition)
I have this tablet rooted now, so you can ask me for anything about it.
With love for all open source,
petabeda
Just one thing: fastboot boot is not supported here, so If you are afraid, flash modified boot.img to recovery partition with fastboot flash recovery boot.img for test (adb reboot and then adb reboot recovery
You will lost your recovery, but, at least, no bricked device in case of error (recovery is actually second boot partition)
petabeda said:
Just one thing: fastboot boot is not supported here, so If you are afraid, flash modified boot.img to recovery partition with fastboot flash recovery boot.img for test (adb reboot and then adb reboot recovery
You will lost your recovery, but, at least, no bricked device in case of error (recovery is actually second boot partition)
Click to expand...
Click to collapse
I have two surftab tablets. One version of the SIM card is fully functional. Another wifi version will not load. When loading, the orange logo at the moment of "collection" freezes. If there is, you can go into recovery even factory reset.
But nothing changes. I believe that the EMMC resource has been exhausted and therefore this behavior.
and to be honest, I don’t know how to write the partition. Since only the adb sideload command is available in recovery mode. Apparently, it is impossible to overwrite the firmware except through the programmer.
Until that time, I could not even pull out the firmware. Since there was no root access
Thank you for your help. As a thank you, I will give you a link to a tool to repair the Nexus 7 bootloader. Through a vulnerability in the tegra cpu. As I understand it, I use this method to hack the nintendo switch. I personally bought 4 nexus 2012 on the secondary market and one of them was able to restore in this way. They of them had a damaged eMMC other power controller. And even with a soldering station, I could not replace it because there is no suitable frame for the reball. In general, nexus are not bad, but there is very little disk space for installing google services and GAPPS are useless. And it is difficult to change partition. And it makes no sense because of the available firmware.
I see, you can''t unlock bootloader, because your device is not bootable at all. So, there is no way to get into fastboot mode?
We are anti e-waste fighters giving second chances!
The first photo is the available recovery menu. Where after choosing a factory reset, nothing changes. And through the adb update, only sideload mode is available.
The factory partition is not corrupted as the restore completes successfully. But the download fails. And not just does not occur, but freezes as in the screenshot above. Most likely a hardware problem eMMC.
Earlier, I saw something similar, for example, in Asus Zenpad, if turn off or connect the camera incorrectly, then the download stops. But here animation is stuck.
I don't know how to check eMMC exactly.
logs files is empty
And with recovery, no commands are available (like adb or fasboot)
There is a one way how to diagnose/repair/have fun with that Trekstor tablet - If you could and want to disassemble it:
have your tablet powered off
disassemble the tablet
carefully disconnect FFC cables (display and digitizer)
remove mainboard screws
at back side in the center of the board, there are three testpoints.......yes you are thinking right, these are actually 1.8V UART signals and GND
Connect these signals to your serial converter (in my case, Raspberry Pi), be careful and talk with the same loundnesses
Don''t power on the tablet, only plug usb cable, tablet will try boot and run healthd (charging mode with battery animation)
Your console will show you the magic (PBL/SBL) bootloader messages and Linux log and event, maybe, the console (though no root), lalalal (/dev/ttyFIQ0)
Wish you luck
After that, if everything goes well, you should be able to use reboot fastboot command to get fastboot mode !