After a full nvflash, it booted in stock. However it just loops between g-tablet and Viewsonic screes. When I select a recovery mode, it enter recovery mode. Instead of recovery menu, it Shows the word "Andriod" and after a few seconds, it shows a traingle with exclamation sign without any message and reboot itself.
Any idea?
Thanks
My first suggestion is a user data wipe - it's a common problem and the first thing I'd try.
Problem is that bekit's 1105 nvflash has standard recovery, and standard recovery doesn't have the ability to do a data wipe.
Further suggestion: Grab bekit's .8 clockworkmod (see my TNT Lite post for a link to that), take the recovery.img and drop it in the same folder as your nvflash. Then, reboot the device back in APX mode and run this (assuming you are a Windows user):
Code:
nvflash.exe --bl bootloader.bin --download 9 recovery.img
What this does is overwrite partition 9 (which is the recovery partition) with the clockworkmod image.
Then reboot into recovery (you should have clockworkmod) and wipe data / factory reset and reboot again. Hopefully that will fix it.
Hi,
Thanks for your reply. I have downloaded recovery-clockwork-2.5.1.8-tattoo.zip and got the img file. I am using linux and ran ./nvflash --bl bootloader.bin --download 9 recovery.img. The process completed. When I go into recovery, it stops at booting recovery kernel image. I am wondering if I downloaded a wrong file. If that is the case can you, please send the right link. If it is the right file, what can I do next.
Thanks
This may/may not resolve your issue, but I also was stuck w/ a similar bootloop after nvflashing my G-Tab. In the end repartitioning my sdcard 2048/0 via cwm corrected the issue; You may also want to make sure you're using bekit's cwm bundle image.(see roebeet's post below for linkage)
---edit---
Here's my thread detailing my issue in case it helps.
Try this link for the .8 bekit version of cwm: http://www.mediafire.com/?dvleg4oatkfxm7w
Related
I was happily running CM7 7.0.2 when I decided to load up .3.
it bootlooped. I tried all kinds of stuff within bootloader...factory reset, cache wipe, delv cache wipe...nothing...then I repartitioned my card and I was screwed.
So I tried nvflash FULL restore, using bekit's original image
This seemed to run...but when the puffins came up...it still bootlooped.
and I lost recovery....it's now just a triangle with an exclamation point for 2 seconds then the puffin bootloop again.
i tried Flashing UPDATE.ZIP the old fashioned way
exclamation point for 2 seconds then the puffin bootloop
I am really at a loss here...not sure what I can do.
Any ideas?
Update....I used NVFlash CWM to get recovery back
when I tried to do a data/factory reset I get this:
e: Can't mount /dev/block/mmcblk3p2
(Invalid Argument)
Error mounting /data/
looks bad
Update2 : OK I tried to load an image.zip file from CWM....after three boot loops I'm stuck on the g-tablet tab.
tried to get back into recovery....didn't go...got some sort of cardboard box....now I'm stuck in g-tablet screen again.
Update 3 : the cardboard box was from "update the old fashion way"....so I followed the instructions and got the image.zip to load up again.....but I'm still stuck on g-tablet.
1) nvflash bekit's 1105 with CWM in place of part9.
2) Repartition 2048 and 0
3) Wipe everything
Then you should be ready to flash a new ROM.
First of all....thanks for your efforts.. however.....
No joy....I did just what you suggested....nvflash...part9
was able to get into CWR
wiped.
installed 3588...seemed to go ok, but now I'm just looking at a g-tablet logo for 10 minutes now....no bootloop at all...
When I tried to clear Delvic cache I got :
e: Can't mount /dev/block/mmcblk3p2
Invalid argument
I get the same error when I try to mount data....
Is my SD Card screwed up somehow? I repartitioned per your instructions.
Try it again but before doing step three nvflash back to bekit's 1105 and leave the stock recovery in then upgrade to 3588 (I prefer manually upgrading but OTA should work also).
K J Rad said:
Try it again but before doing step three nvflash back to bekit's 1105 and leave the stock recovery in then upgrade to 3588 (I prefer manually upgrading but OTA should work also).
Click to expand...
Click to collapse
I'll try it tonight. Thanks so much for your help...I'm getting a little worried.
sudermatt said:
I'll try it tonight. Thanks so much for your help...I'm getting a little worried.
Click to expand...
Click to collapse
Also try (Can't find the exact post) the utility that does a quick deletion/format for your GTAB. THEN try popping in a NVFLASH. Should shake out all the bad demons.
Have you re-downloaded the nvflash image in case the one you have is corrupted? Also another good starting point there.
UPDATE: Post for erasing/formatting your Gtab.
http://forum.xda-developers.com/showthread.php?t=974422
9020 – Eur model. Was 2.3.3, but upgraded to 2.3.4 after one day.
I followed the Unlockr guide, and followed the following, before deviating!!Can someone help me recover from this recover from this?
Bootloader successfully unlocked
Then it all went pear shaped!!
IV. Flash a Custom Recovery Image
1. Download the custom recovery image and save it to your computer: DONE
ClockworkMod Recovery for Nexus S
2. Copy the recovery.img file inside the tools folder of the sdk (so it is in the same folder as fastboot.exe) DONE
3. Then in the command prompt that should still be open, type the following with hitting enter at the end of
each line:
fastboot flash recovery recovery.img DONE
This is where for some insane reason (moment of madness) I deviated and don’t know how to get out of it. I rebooted and it went into clockwork mod. I couldn’t get out of it so I thought I would flash a backed up nanroid rom (2.3.1) which I down loaded. Big mistake, as it boots then freezes after 1minute.
I then booted into recovery (clockwork mod) and wiped cache, and pretty much everything else. Now the phone hangs on the google start page, recovery (clockwork mod) says there’s misc missing, cache missing etc....Cant flash any new rom. Can get to recovery but that’s about it.
I need some help to fix it!
mittu1 said:
9020 – Eur model. Was 2.3.3, but upgraded to 2.3.4 after one day.
I followed the Unlockr guide, and followed the following, before deviating!!Can someone help me recover from this recover from this?
Bootloader successfully unlocked
Then it all went pear shaped!!
IV. Flash a Custom Recovery Image
1. Download the custom recovery image and save it to your computer: DONE
ClockworkMod Recovery for Nexus S
2. Copy the recovery.img file inside the tools folder of the sdk (so it is in the same folder as fastboot.exe) DONE
3. Then in the command prompt that should still be open, type the following with hitting enter at the end of
each line:
fastboot flash recovery recovery.img DONE
This is where for some insane reason (moment of madness) I deviated and don’t know how to get out of it. I rebooted and it went into clockwork mod. I couldn’t get out of it so I thought I would flash a backed up nanroid rom (2.3.1) which I down loaded. Big mistake, as it boots then freezes after 1minute.
I then booted into recovery (clockwork mod) and wiped cache, and pretty much everything else. Now the phone hangs on the google start page, recovery (clockwork mod) says there’s misc missing, cache missing etc....Cant flash any new rom. Can get to recovery but that’s about it.
I need some help to fix it!
Click to expand...
Click to collapse
If you have recovery, then you are fine. Just flash a rom. Flash the stock rom if you want. Any rom. Then you should be fine.
Sorted!! The solution was found here:
http://forum.xda-developers.com/archive/index.php/t-992114.html
New ROM up and running, no issues so far.
Transformer only boots to recovery.
Tried to use the usual 'echo boot | dd of=/dev/block/mmcblk0p3' trick, but it seems something overwrites it whenever i reboot (it just goes back to the old content).
Can't flash blobs, dd works fine and writes the blob to mmcblk0p4, but it seems like the bootloader doesn't even try to flash it, no progress bar, nothing.
power+voldown does not even ask me if i want to go to recovery, it just says it's doing a cold boot and wiping data and then "booting recovery kernel"
I'm a B80 so I can't use nvflash.
any ideas?
Well the flag for the bootloops is "boot-recovery" so when you echo "boot" you are just adding "boot" over "boot-recovery".
Maybe something like "dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13"
sent while running with scissors
Considering even if i zero out 100 bytes it restores the previous contents of mmcblk0p3, that's not the issue.
EDIT: in fact, it seems like the first few bytes of mmcblk0p3 are zeroes, then the word 'recovery', then a bunch of more zero bytes, then --wipe-data.
kind of weird, isn't it?
It is very odd. Maybe you have some form of fake/temp root? What does "getprop ro.secure" show in terminal?
sent while running with scissors
~ # getprop ro.secure
getprop ro.secure
/sbin/sh: getprop: not found
I am stuck in cwm, so I don't think getprop should work?
EDIT:
~ # cat /default.prop
cat /default.prop
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
would that be it?
I think so- your system is secure so changes don't stick. I'm not too familiar with ro.secure=1, but I know it gets in the way of a lot of fun things.
You might try the dd trick from cwm via adb.
sent from my transformer
That really has nothing to do with the rom- it works because I put sumpthin' sumpthin' in the updater script to remove the bootloops. I'll see about making a stand alone fix in zip format since everyone and their brother seems to get the recovery bootloops. And I even told them that if they keep on rebooting like that, they'll go blind!
There is a trouble shooting thead in the dev section for cwm 5504. Essentially, some of the cwm 5504 and 3201 don't handle the "reboot to recovery" flag well, so if you use an app or menu to reboot to recovery (out of sheer laziness)? then you'll get stuck in recovery boot loops. These recoveries don't clear the reboot flag, so they keep on rebooting to recovery. If you are old school and use the hardware buttons, then it never happens. See the thread for all the gory details. EDIT: I think that some of the recoveries have been patched, but you can't flash a patched version until you get out of the loopy ones.
The fix is to overwrite the first 13 or 80 or 100 bytes of the misc partition to remove the reboot to recovery flag that is set with the app/menu/software (not hardware buttons).
So to translate, the sumpthin' sumpthin' is just a bit of code in the zip file that fixes the issue.
I made a flashable zip file that just has the reboot fix. If you are truly curious, you can unzip it and try to figure out how it works.
Flash at your own risk! and yes, the file is tiny 151K. BE CAREFUL, since this will fix the recovery and anything in the staging partition will flash when the tf reboots. The zip won't write over anything, but that leftover meatloaf that you flashed in the staging partition will.
http://www.mediafire.com/?5ih9s5i59xys9zd
MD5(cwm_bootloop_fix_tf101_d6695210ed.zip)= d6695210edbb755526e450ab8fe20180
Now, back on topic, the OP has a similar issue, but based on this posts, I can tell that he has tried the usual solutions on his own. In this case, it seems like something else is wrong.
Well, I do say flash at your own risk, so if you have to ask then the answer is no It's probably fine if you have a classic recovery bootloop. It doesn't overwrite any of the usual partitions, but watch out for the leftover meatloaf in the staging if you tried to flash something unsuccessfully. Google around for the staging partition to see how it works.
gee one said:
Well, I do say flash at your own risk, so if you have to ask then the answer is no It's probably fine if you have a classic recovery bootloop. It doesn't overwrite any of the usual partitions, but watch out for the leftover meatloaf in the staging if you tried to flash something unsuccessfully. Google around for the staging partition to see how it works.
Click to expand...
Click to collapse
Could you just format staging in the CWM advanced menu before flashing your zip? Wouldn't that eliminate the chances of any "leftover meatloaf" messing things up?
Not every version of cwm will let you format the staging partition. I don't think it's formatted to start with, so formatting might be overkill- it might be better to do one of the following- empty it, write something safe, remove any blobs, or overwrite the blob header.
Can I flash the zip file that you uploaded for my TF101 problem as well?
I was using 9.2.1.17, stock rom and stock kernel but with root, and then I did the update OTA by asus to 9.2.1.21
After the update, it went to CWM bootloop. I am running CWM Recovery v3.2.0.1 by roach2010
Can I flash this to fix the issue?
Thanks in advance
wzseow said:
Can I flash the zip file that you uploaded for my TF101 problem as well?
I was using 9.2.1.17, stock rom and stock kernel but with root, and then I did the update OTA by asus to 9.2.1.21
After the update, it went to CWM bootloop. I am running CWM Recovery v3.2.0.1 by roach2010
Can I flash this to fix the issue?
Thanks in advance
Click to expand...
Click to collapse
There's always a danger in flashing anything- it will fix "typical" recovery bootloops caused by the reboot to recovery apps, but be careful because it will unstuck anything that is stuck in the staging partition. So if you flashed some hanson mp3's to the staging partition, then they will try to flash at reboot mmmmbop!
As far as I know, the recovery bootloop is caused by using a software method to reboot to recovery- using a menu or app. Rebooting using the hardware buttons does not seem to have the same issue. I also don't use OTA rootkeeper, so I have no experience with that to know if there are any potentially bad interactions. It might be fine, but I can't say with any certainty. There are lots (too many) threads about recovery bootloops- perhaps someone in the exact same situation as you has posted something about what works and what doesn't.
You'll lose latest touch/whatever recovery, but the reboot to recovery works with Rouge Xm recovery, and it reads from both internal and external SD card. You can download a cwm flashable zip of that and flash it. I almost never use the reboot to recovery options though, I just use the buttons -shrugs-
As far as fixing issues, you can try flashing a stockrooted-no recovery full update, then wipe it and flash a Rom/new recovery too. It'd be like you rebaked an entirely new loaf of bread! (gee one.. you got me on food metaphors..) Do check to make sure there's no 'leftover meatloaf' as that would seriously screw you, so see his post.
I restored a Nandroid backup within TWRP and now the TF101 is in a TWRP recovery script bootloop.
When I start the I see after the standard ASUS screen the Teamwin screen and after that the text:
"Updating partition details...
Formating cache using make_ext4fs
Done.
Wiping data without wiping /data/media ...
Done."
And than it reboots instantly.
When hold volume down that I see before the Teamwin screen the text:
"Wiping user data and any indicator before cold booting Linux.
Please wait a few minutes ...
Booting recovery kernel image."
With volume up TF101 goes evently off.
When I connect the TF101 to my PC it is recognized, but connection is lost every time it boots.
How can I restore TWRP recovery image?
Possible that your Nandroid backup is corrupted, or maybe a problem with TWRP
Try flashing TWRP again with Easyflasher then try to restore your backup again
If it fails, try flashing a ROM and see if you can get it to boot, if you can, looks like a bad Nandroid backup
I tried both, and both failed. I need to know how to stop the TWRP script from running, because it is keeping wiping something.
If you have an SBK1 device (B6O or earlier, some B7O Serials) you could use a stock NVFlash ROM to wipe TWRP back to stock recovery, then use Easyflasher to get TWRP back again, then flash your backup again
Code:
http://www.xdafileserver.nl/Files/Asus/Asus%20Transformer%20(TF101)/STOCK%20ROMS/ICS%20.27/NVFLASH_ICS_9.2.1.27_US_NOROOT.7z
Extract > Put TF into APX Mode > Run Download.bat as Admin > Wait
*Detection* said:
If you have an SBK1 device (B6O or earlier, some B7O Serials) you could use a stock NVFlash ROM to wipe TWRP back to stock recovery, then use Easyflasher to get TWRP back again, then flash your backup again
Code:
http://www.xdafileserver.nl/Files/Asus/Asus%20Transformer%20(TF101)/STOCK%20ROMS/ICS%20.27/NVFLASH_ICS_9.2.1.27_US_NOROOT.7z
Extract > Put TF into APX Mode > Run Download.bat as Admin > Wait
Click to expand...
Click to collapse
It is a B70 SBK2.
Joh14vers6 said:
It is a B70 SBK2.
Click to expand...
Click to collapse
I was wrong.
First I was not putting the device really in APX-mode,. Another recent posting made me that clear. Seccond, although it a B70 it seems to be a SBK1.
Only problem now that is not loading the boatloader.bin completely. In succesive tries it random hangs at some point (6%, 27%, 48%, 90%). What can I do to solve this?
*Detection* said:
If you have an SBK1 device (B6O or earlier, some B7O Serials) you could use a stock NVFlash ROM to wipe TWRP back to stock recovery, then use Easyflasher to get TWRP back again, then flash your backup again
Code:
http://www.xdafileserver.nl/Files/Asus/Asus%20Transformer%20(TF101)/STOCK%20ROMS/ICS%20.27/NVFLASH_ICS_9.2.1.27_US_NOROOT.7z
Extract > Put TF into APX Mode > Run Download.bat as Admin > Wait
Click to expand...
Click to collapse
I changed to another computer and then the boatloader was loading, but flashing was afterwards still not succesfull. Then I tried to flash a stock ROM within Easyflasher (2x), but ended in a TF that always start in APX-mode.
Then I tried the link above, with the only diference that I changed US to WW and now my TF101 is revived.
Thank you very much!!!
Joh14vers6 said:
I changed to another computer and then the boatloader was loading, but flashing was afterwards still not succesfull. Then I tried to flash a stock ROM within Easyflasher (2x), but ended in a TF that always start in APX-mode.
Then I tried the link above, with the only diference that I changed US to WW and now my TF101 is revived.
Thank you very much!!!
Click to expand...
Click to collapse
Great!
I originally had Katkiss 4.3 v19 and it was working fine. I then wanted to update to the recent 4.3.1 v27 but when I tried to flash the new ROM, it says that it can't open the zip file and failed. I backed up beforehand, so I wiped the cache and dalvik. I then tried to flash the ROM again, but it still says failed. I went to restore the backup to go back and for some reason, it is also failing.
I have TWRP 2.6.0.0 and I am stuck in recovery where I can't flash anything. Not even when I wanted to flash to stock.
I have the Asus EEE transformer tf101 tablet.
How do I fix this?
Please Help.
Are you trying to flash from Micro SDCard ?
Maybe the card has corrupted - try formatting the card in a PC, then copy #27 back to it, and try flashing again
Or try another MicroSD Card
*Detection* said:
Are you trying to flash from Micro SDCard ?
Maybe the card has corrupted - try formatting the card in a PC, then copy #27 back to it, and try flashing again
Or try another MicroSD Card
Click to expand...
Click to collapse
I did this and it says successful but I don't think it's completely flashed because the last line says E:Unable to mount '/staging'. Plus when I reboot, it just goes back to recovery. I flashed SuperSU but it didn't change anything.
EDIT: Ok. So I tried flashing any rom and it says 'successful', yet it seemed like it flashed the rom too quickly. Afterwards, I'd reboot but it just goes from the Eee transformer logo to twrp recovery. This happens to all of the 'successful' flashes. When I tried to flash the stock rom, it would just say failed.
I really don't know what to do at this point. I tried formatting the SD card, changing the SD card, reinstalling twrp using the EasyRecovery app and I wiped my internal and external data (which I think is the problem and IDK how to recover them). I even tried flashing a new recovery (CWM) and, like the other 'successful' flashes, still goes back to TWRP.
gigases said:
I did this and it says successful but I don't think it's completely flashed because the last line says E:Unable to mount '/staging'. Plus when I reboot, it just goes back to recovery. I flashed SuperSU but it didn't change anything.
EDIT: Ok. So I tried flashing any rom and it says 'successful', yet it seemed like it flashed the rom too quickly. Afterwards, I'd reboot but it just goes from the Eee transformer logo to twrp recovery. This happens to all of the 'successful' flashes. When I tried to flash the stock rom, it would just say failed.
I really don't know what to do at this point. I tried formatting the SD card, changing the SD card, reinstalling twrp using the EasyRecovery app and I wiped my internal and external data (which I think is the problem and IDK how to recover them). I even tried flashing a new recovery (CWM) and, like the other 'successful' flashes, still goes back to TWRP.
Click to expand...
Click to collapse
The /staging/ error is normal, nothing to worry about.
Question, if you shut down the tablet from recovery. Then turn it on with a 3 second power button press, does it go directly to recovery?
If so, this is causing your tablet NOT to finish the flash when it reboots. It needs to reboot normally and you should see the Eee Pad logo with a progress indicator.
If you do have a recovery boot loop, try this. Boot to recovery and go to the Advanced section and open a terminal window.
Code:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Then reboot normally (not to recovery). Then after it tries to boot not into recovery, boot back to recovery and try restoring your 019 backup.
frederuco said:
The /staging/ error is normal, nothing to worry about.
Question, if you shut down the tablet from recovery. Then turn it on with a 3 second power button press, does it go directly to recovery?
If so, this is causing your tablet NOT to finish the flash when it reboots. It needs to reboot normally and you should see the Eee Pad logo with a progress indicator.
If you do have a recovery boot loop, try this. Boot to recovery and go to the Advanced section and open a terminal window.
Code:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Then reboot normally (not to recovery). Then after it tries to boot not into recovery, boot back to recovery and try restoring your 019 backup.
Click to expand...
Click to collapse
Yes. When I reboot/shutdown from recovery, it shows the eee pad and nvidia logo on the bottom and then goes to recovery. I did what you said with the terminal window. I also typed in the code. and it says:
5+0 records in
5+0 records out
5 bytes (5B) copied,
0.006015 seconds, 831B/s
Afterwards, I rebooted normally and it still goes back to recovery. It doesn't even go to the 'ASUS' logo where there is a wheel on the bottom.
gigases said:
Yes. When I reboot/shutdown from recovery, it shows the eee pad and nvidia logo on the bottom and then goes to recovery. I did what you said with the terminal window. I also typed in the code. and it says:
5+0 records in
5+0 records out
5 bytes (5B) copied,
0.006015 seconds, 831B/s
Afterwards, I rebooted normally and it still goes back to recovery. It doesn't even go to the 'ASUS' logo where there is a wheel on the bottom.
Click to expand...
Click to collapse
May need to do it from an ADB shell, but adb shell is blocked on TWRP 2.6.X.X for security reasons.
I would suggest flashing TWRP again using EasyFlasher. See my guide here: www.transformerforums.com/forum/asu...nt/31927-frederucos-guide-root-rom-tf101.html . Grab one of the repacked versions with TWRP 2.6 and you should be back in business in no time.
I did everything and it all seemed fine. Now I'm in a bootloop. I used the TWRP 2.6.3.0 EasyFlasher
Okay. I just tried other recoveries (CWM and Rogue) and they seemed to go well. I tried flashing, yet it still does the same thing as before where it goes to the logo and then to the recovery.
gigases said:
I did everything and it all seemed fine. Now I'm in a bootloop. I used the TWRP 2.6.3.0 EasyFlasher
Okay. I just tried other recoveries (CWM and Rogue) and they seemed to go well. I tried flashing, yet it still does the same thing as before where it goes to the logo and then to the recovery.
Click to expand...
Click to collapse
At this point, I would try restoring stock using EasyFlasher. Just download the asus firmware file and leave it as is (do not unzip) and put it in the asusupdate folder in EasyFlasher.
Once you flash back to stock and can boot, then flash TWRP with EasyFlasher and you should be good to go.
frederuco said:
At this point, I would try restoring stock using EasyFlasher. Just download the asus firmware file and leave it as is (do not unzip) and put it in the asusupdate folder in EasyFlasher.
Once you flash back to stock and can boot, then flash TWRP with EasyFlasher and you should be good to go.
Click to expand...
Click to collapse
That did it. I flashed back to stock and it can boot again. I'll flash TWRP again.:fingers-crossed: Thank You
Any time! I have a few EasyFlashers with newer versions of TWRP in the EasyFlasher thread. Start and the end and read backwards to find them.