Wrong recovery flashed, now can't get recognized by flashing program - Android Q&A, Help & Troubleshooting

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.

Related

[Q] Huawei U8520 Dual Sim problem with bootloop and no recovery menu

Hi all
first of all I apologize if this is not the right place to put my inquiry in, but I could not find the specific forum for this device.
I have serious problem with this android mobile phone. it is pretty good phone very useful with dual sim function one of them is 3G with WiFi Hotspot but the problem that I have rooted the phone with superoneclick and I have installed a lot of apps in it modifying some language files then when I restart the phone to let the changes take effect then the mobile keep restarting for infinite. Tried to get in to the recovery mode by using Call Button+Volume up+Power but the screen became blank. I spent the whole day searching the the internet to find the solution but with no clue. the problem the device is new and not supported that much in the public forums. could not find Stock Rom. Huawei website and bulletin was not useful.
is there any way to do it through USB or sdcard and How?
thanks in Advance
I am still trying to find a solution...
if you need it, I attached the original recovery dump to this post.
then you just need to get "fastboot" and then (after preparing your device for fastboot):
"fastboot flash recovery recovery.img" (on a command line opened on the same folder where "fastboot" is)
or you can probably do it too on Linux if you prefer. if it is possible, you'll find the way for it on Google.
also, to access fastboot mode is POWER+VOL_DOWN (not volume up or a 3 key combination) and recovery is POWER+HOME (which you probably already know).
the system dump I can't send because I never made a dump.img of it and I am currently having a bootloop problem (I'll probably have to flash the original rom from a friend).
bl88drg said:
if you need it, I attached the original recovery dump to this post.
then you just need to get "fastboot" and then (after preparing your device for fastboot):
"fastboot flash recovery recovery.img" (on a command line opened on the same folder where "fastboot" is)
or you can probably do it too on Linux if you prefer. if it is possible, you'll find the way for it on Google.
also, to access fastboot mode is POWER+VOL_DOWN (not volume up or a 3 key combination) and recovery is POWER+HOME (which you probably already know).
the system dump I can't send because I never made a dump.img of it and I am currently having a bootloop problem (I'll probably have to flash the original rom from a friend).
Click to expand...
Click to collapse
Hi, Can you help me and upload the boot img. I accidentally erase the boot partition.
Many Thanks.

Lessons learned from bricking (er, shot put-ing?) my Q

So yes, I tried to flash a different system.img, and am currently bricked, but would like to share some helpful info:
Google's Nexus telephone support will not supply factory image locations
They will also not comment on whether some sort of "internet recovery" (using Ethernet) exists such.
Fastboot can be manually entered by powering up with a palm ove the device, waiting for the red flashing to begin, and once it does, immediately removing your palm. I struggled with this for a little while (as I couldn't connect over adb/fastboot) and am at least in a state now where I could restore the device.
I hope this info's helpful... and if it is, please help me out with some factory image sources over in my "Factory Images?" thread!
Oh, and it'll run ICS
...or at least boot it! (can't yet post links)
youtube.com/watch?v=dUmuQULyrAk
You can Fastboot the device and only botched the system image correct? Well, in theory all you need to do is boot ClockworkMod Recovery through Fastboot and restore a dump someone has already done. I think their is one in the Dev Forum already.
ThisIsDave said:
So yes, I tried to flash a different system.img, and am currently bricked, but would like to share some helpful info:
Google's Nexus telephone support will not supply factory image locations
They will also not comment on whether some sort of "internet recovery" (using Ethernet) exists such.
Fastboot can be manually entered by powering up with a palm ove the device, waiting for the red flashing to begin, and once it does, immediately removing your palm. I struggled with this for a little while (as I couldn't connect over adb/fastboot) and am at least in a state now where I could restore the device.
I hope this info's helpful... and if it is, please help me out with some factory image sources over in my "Factory Images?" thread!
Click to expand...
Click to collapse
Thanks for the info, saved me at least 3 or 4 times after soft bricking my Q. One thing that I found to help is while the device is bricked type in command prompt: adb reboot-bootloader ... this will generate a waiting for device tag then once you see that unplug the Nexus Q and plug it in, within one second as soon as you see a hint of blue on the mute button put your palm over it and it typically boots right into fastboot mode. If not just unplug and repete until it goes.
FYI: Also if you try to launch clockwork from an apk and instal a rom you will almost most definitely soft brick it (tried to sideload AOSP JB ROM and some others with no luck).

[Q] Possibly Bricked - Completely Lost

Hello everyone, been a lurker for some time, but have never needed to post before until today. I'm accustomed to rooting and installing custom roms but I've never had anywhere close to as much difficulty as Im having with this tf201. Heres the situation:
Not sure if you'd call this bricked, as I have total access to fastboot, adb, and CWM Recovery (version 5.8.3.4 touch btw). However my most recent attempt ended with totally wiping from the volume down+power menu (whatever its called). I can not turn the tablet off, as it automatically boots to the asus splash screen (and goes no further, naturally). It is unlocked, and my drivers do work (both fastboot and adb recognize the device), but I can not flash or push anything to the sdcard (with adb its a protocol failure, with fastboot I get "sending zip....OKAY writing zip....FAILED [remote : [FileOperationFailed]]) Don't know if it needs to be said, but I also can't simply drop the file on the sd card as if it were a media storage device as "my computer" does not recognize that it is connected (Oh I am using the naked universal drivers from http://forum.xda-developers.com/showthread.php?t=1998650 )
So yeah, Im at a loss as it seems like no one has had this particular problem before (also my connector cable works fine, so its not that). Any help would, of course, be greatly appreciated.
EDIT: On the tablet after trying to flash with fastboot it returns "Failed to process command flash:zip error (0x30003)"
Really? Not a single person has any idea? Could really use some help here...
GrimAgent said:
Really? Not a single person has any idea? Could really use some help here...
Click to expand...
Click to collapse
You do not flash zips with fastboot.
First of all tell me where your "NVIDIA" logo is when you first power on, bottom center or bottom right?
The nvidia logo is in the bottom center of the "EEE PC Splash"
This is going to sound stupid, but did you verify the MD5 before you tried to flash it?
GrimAgent said:
The nvidia logo is in the bottom center of the "EEE PC Splash"
Click to expand...
Click to collapse
You are still on the ICS bootloader if NVIDIA is bottom center.
Go here http://www.teamw.in/project/twrp2/93 and follow the instructions for "Download - Recovery Image / Fastboot Method (using ICS or JB Asus bootloader)"
You will need to get the ICS blob file. Never flash the wrong recovery for what bootloader you are on or you can brick your device.
If you get it working and you want to upgrade to Jellybean bootloader there is instructions in post 2 of the Hairybean Rom thread. "Upgrade instructions for ICS"
edit.. to make it a bit easier for you.
Get this file http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.4.4.0-tf201-ICS.blob
Rename it to twrp.blob
Place the twrp.blob in the same folder as your fastboot exe
Go into fastboot and type
fastboot -i 0x0b05 flash recovery twrp.blob
Wait for it to finish and then type
fastboot -i 0x0B05 reboot
see if that works.
Damn, I had a feeling it was the bootloader issue that I messed up. I went searching all over for how to find out which one I had once I realized my potential mistake. Gonna give these steps a try
I just tried all your steps, twrp is on there and I was able to push both cm10 and gapps onto the tablet, but now the zips I pushed to the sd card arent showing up in TWRP...
GrimAgent said:
I just tried all your steps, twrp is on there and I was able to push both cm10 and gapps onto the tablet, but now the zips I pushed to the sd card arent showing up in TWRP...
Click to expand...
Click to collapse
If you now have twrp on there you dont need to push a file. Place the file on an external SD card on the root and plug it in before starting prime.
When going into TWRP go into install and select external SD. Pick your rom and then flash it.
Thanks a lot flumpster, everything's good now and Ive got cyanogen up and running smoothly. You've brought my tablet back to life and Ive learned a valuable lesson

[Q] Save my tablet please! HELP

sorry for my english guys,
i have asus ME301T tablet, but now i can't start, only asus logo shown, then everything stop
i can't get recovery with START+VOL DOWN too
any solutions for dumb newcomer?
petr.mostyn said:
sorry for my english guys,
i have asus ME301T tablet, but now i can't start, only asus logo shown, then everything stop
i can't get recovery with START+VOL DOWN too
any solutions for dumb newcomer?
Click to expand...
Click to collapse
You're not dumb. I don't know anything about this tablet but check to see if you find solutions here.
vanessaem said:
You're not dumb. I don't know anything about this tablet but check to see if you find solutions here.
Click to expand...
Click to collapse
I agree with vanessaem.... You are not dumb at all, just a newbie. We all started out as a newbie ourselves
I just read on the forums for your device that there is a physical "Reset" button near the SD Card slot. Can you please try to stick a paperclip or pin into that hole and hold it down until the tablet reboots? I also read that these instructions may be in the manual as well.
If all else fails you can restore the tablet to defaults. I also did a quick search and came upwith the easy steps to restore it. These steps are from another forum so I will quote them since this is not my work.
I've only had this tablet a few hours, but managed to get to a point where it wouldn't boot pretty soon after rooting it. So after trying everything to get it up and running I finally managed it with ADB and fastboot, also it took from Android 4.1.1 to 4.2.1 - so here is what I did after reading various forums of problems with other Asus devices and soft-bricking other Android devices in the past - hopefully it might help someone one day.
You will need to install the Asus ADB drivers before following the steps below, if you haven't installed them you can get them here
1. Download and install Lightweight ADB and fastboot installer here from XDA
2. Create a folder called 'Fastboot' on your C: drive (it can actually be called anything but the prompts below refer to a folder with this name)
3. Download the CarePackage.zip file here and unzip the contents to C:\Fastboot, there are 4 files
4. Download your chosen firmware from the Asus web site - extract the zip file to reveal another zip, extract the second zip file, copy the 'blob' file to the Fastboot folder, there will now be 5 files in your fastboot folder
5. Reboot tablet, holding volume down, select the USB option (3rd icon) using volume down to cycle through icons and volume up to select and connect it to your PC using the USB cable
5. Run the Lightweight ADB and fastboot installer which will open the command line, enter the following commands;
c:\Fastboot
fastboot devices
fastboot -i 0x0B05 flash system blob
6. The following will now be displayed in the command line screen;
sending 'system' <1062567 KB> (the actual size will vary depending on the firmware selected) Also a blue bar will appear on your tablet screen showing the progress. It takes around 3-4 minutes to send the system files.
writing 'system' will then be displayed, this will take a further 3-4 minutes.
Once the files have have been sent and written the command screen will display something similar to;
finished. total time: 444.226s
7. Unplug the tablet and reboot it using the power button, you'll have a fresh install, all data, root etc will be lost.
For anyone who is struggling to recover their tablet or just actually update it I hope this helps
Click to expand...
Click to collapse
timmytim said:
I agree with vanessaem.... You are not dumb at all, just a newbie. We all started out as a newbie ourselves
I just read on the forums for your device that there is a physical "Reset" button near the SD Card slot. Can you please try to stick a paperclip or pin into that hole and hold it down until the tablet reboots? I also read that these instructions may be in the manual as well.
If all else fails you can restore the tablet to defaults. I also did a quick search and came upwith the easy steps to restore it. These steps are from another forum so I will quote them since this is not my work.
Click to expand...
Click to collapse
thanks for all advices, but i think this is a SERIOUS problem ..
i can't do fastboot, can't connect PC-ANDROID or vice versa
my android device has now only two modes / off or stoned when asus logo appears
RECOVERY twrp non reachable!

Trekstor Surftab breeze 9.6 quad root

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 !

Categories

Resources