[Q][SBK2]Can't access/flash recovery (+random reboots&freezes) - Eee Pad Transformer Q&A, Help & Troubleshooting

Hi everyone, I've got a BIG problem with my sbk2 TF101.
I don't know why but I cannot access the Recovery. I don't know if it is actually installed or not, but I cannot access it nor I can flash it with CWM Manager or Recovery Installer
-When I restart, it simply stucks at the EEE logo.
-I cannot boot in recovery with any of the apps made for this;
-Every time I want to start the tablet, I need to start it using cold-boot (first, vol- and power, and then vol+), because it seems to be always starting in recovery.
-Without recovery I cannot flash a new recovery or a new rom, and I'm stucked with an AOKP cooked in the firsts days of may (I don't remember the name)
-I've got random and frequent reboots, freezes, and can't do something for more than 5 min because the tablet freezes.
-Standard voltages.
-My tablet is not recognized when I plug it in Windows or Mac OSX, didn't try with Ubuntu.
Please help me!
Thank you very much in advance for your great help.

Don't do any wipes, as that may be unrecoverable. I don't see why recovery installer isn't working, you should have root. Sounds like some stuff is seriously messed up. You can try using flash_image to manually flash a recovery.img with ADB or with a virtual terminal, that's about all I can think of now. Find the boot.img, and flash_image files and put them on root of SD and run appropriate commands, more info should be in recovery dev sections.

Thing O Doom said:
Don't do any wipes, as that may be unrecoverable. I don't see why recovery installer isn't working, you should have root. Sounds like some stuff is seriously messed up. You can try using flash_image to manually flash a recovery.img with ADB or with a virtual terminal, that's about all I can think of now. Find the boot.img, and flash_image files and put them on root of SD and run appropriate commands, more info should be in recovery dev sections.
Click to expand...
Click to collapse
First of all, thanks a lot for trying helping me.
The problem is that I don't know how to use ADB or wich commands should I use or where I could find the boot.img. Using a virtual terminal means running a trminal on the tablet? Can I use the internal memory instead of an SD card? I can confirm I've still got root, by the way.

Please, could someone help me? I think I need to overwrite the recovery image manually, but I don't know how to.

wanzer said:
Please, could someone help me? I think I need to overwrite the recovery image manually, but I don't know how to.
Click to expand...
Click to collapse
Use PERI/my easyflasher tool to reflash recovery from nvflash.
Read more here:
http://forum.xda-developers.com/showthread.php?t=1688012

Hello guys, I have a problem with my tf101! is brick, and only goes with apx.provo easyflasher wheelie but returns error when it finishes loading bootloader towards the closed dell'applicazione!

sorry for the English, are Italian

I figured out that the OP had the ROM manager bootloop :/
Romyfra - is it a Tf101 Wifi-only or a Tf101G, if it's a Tf101 then you can use NvFlash to reflash it

I brick my wifi tf101 with serial bcoka ..., ICS v24ww 1.6e 4.0.3 I can not even come out with a wheelie! This is what I done, done correctly with the root easyflasher 0.4, after I stupidly installed netformer 1.6 (that idiot) and restart it disappeared with the cmw.ho riflashato easyflasher and end of proceedings, the tab will not light! is only apx, so no recovery! the problem is that when I start wheelie crash and does not pass to nvflash! is possible that the flash is corrupt?? as a last resort if you think I'll send you notice of changes in the RMA? ICS had no stock and cmw più.possono dump and see what happened or there is no trace?? thanks

Related

[Q] Problems with Clockwork Mod

Using a viewsonic G Tablet, I had initially loaded the clockwork mod. was working fine. Flashed a few ROMs over the last week. Currently running Cyanogen Mod7 Accidentally wanted to see what the ROM Manager app was about. Went and flashed the Clockword mod. Since then, I'm not able to go back into Clockwork mod. Everytime I try to reboot using the Power and Vol + button, it boots back into CyanogenMod ROM. Has a message related to MRC Erase after it says it detected REcovery Key pressed. I want to go back to using Clockworkmod so that I can flash another ROM. Now my computer doesn't even recognize the g tablet as an external storage so can't even access root. What do I need to do to get back my Clockworkmod to work again and how do I get back to my computer to recognize the g tablet. Appreciate the help. All feedback is welcome.
Sounds like you've reverted to stock recovery. Reinstall ClockworkMod. First part of this thread: http://forum.xda-developers.com/showthread.php?t=865245
Before you do, you might want to check the developers thread for your ROM to make sure there aren't any caveats.
K J Rad said:
Sounds like you've reverted to stock recovery. Reinstall ClockworkMod. First part of this thread: http://forum.xda-developers.com/showthread.php?t=865245
Before you do, you might want to check the developers thread for your ROM to make sure there aren't any caveats.
Click to expand...
Click to collapse
But to install Clockworkmod, I need my computer to recognize the g tab as a external storage device. Something it's not doing. So can't go back to it. CAn I download the clockworkmod on the external SD Card on the computer, put it back in the gtab and let it self recognize it and install clockworkmod? Will that work? And why isn't my computer recognizing my gtab as an external storage device. Is there a way I can mount USB storage without going into clockworkmod?
Have you tried using Rom Manager to flash clockworkmod again? Or used it to flash and older version of Clockworkmod?
If you read the thread it shows there is a method to load CWM from MicroSD card (external). Once you have CWM back on then you can mount internal through it.
I dont know why Your tablet isn't mounting. Mine mounts automatically but my configuration is very different from yours. Perhaps you could check the ROM developers thread for more information.
Double submission. Please ignore/delete.
tcrews said:
Have you tried using Rom Manager to flash clockworkmod again? Or used it to flash and older version of Clockworkmod?
Click to expand...
Click to collapse
I used the ROM Manger to flash clockworkmod. That's what messed up the clockworkmod in the first place. Trying to see how to fix that. May need to get rid of the ROM Manager.
Flash the alternate recovery in Rom Manager and then delete Rom Manager
thebadfrog said:
Flash the alternate recovery in Rom Manager and then delete Rom Manager
Click to expand...
Click to collapse
I can't even flash clockwork mod from the ROM manager. Keeps giving me a message "An Error occured while attempting to run privileged commands". Using clockworkmod was just so much easier. Just touching one button the ROM Manager has caused me headaches. I need some serious help.
Then run nvflash from the development froum
thebadfrog said:
Then run nvflash from the development froum
Click to expand...
Click to collapse
Tried to run NVFlash, but I get through ok till the point where I have to run the .bat script. What am I doing wrong? Where do I run it? Do I just double click? Because it reports an error when I do that. I"m using Windows 7 64 bit on a HP touchsmart. able to download the usb driver. recognizes the APX. but can't run the last command. Am I just supposed to get a black screen when I boot using Power and vol - button? Cos nothing else shows up on it. Appreciate the help.
I am also Unable to get into CWM after doing an update in Rom Manager. Have tried a bunch of things. still no luck. Power>Reboot>Recovery and RomManager just get me the Deterct Recovery Command - Erasing MCS then straight into CM7
Power/+ gets me Recovery Key Detected but then boots right into CM7.
Please let me know how you make out.
Childpsy said:
Tried to run NVFlash, but I get through ok till the point where I have to run the .bat script. What am I doing wrong? Where do I run it? Do I just double click? Because it reports an error when I do that. I"m using Windows 7 64 bit on a HP touchsmart. able to download the usb driver. recognizes the APX. but can't run the last command. Am I just supposed to get a black screen when I boot using Power and vol - button? Cos nothing else shows up on it. Appreciate the help.
Click to expand...
Click to collapse
When the tablet is put into APX mode the screen will go black. I don't use windows so I can't be much help with the rest but it would help if you told us what the error is when you try to start the file.
Thunter75 said:
I am also Unable to get into CWM after doing an update in Rom Manager. Have tried a bunch of things. still no luck. Power>Reboot>Recovery and RomManager just get me the Deterct Recovery Command - Erasing MCS then straight into CM7
Power/+ gets me Recovery Key Detected but then boots right into CM7.
Please let me know how you make out.
Click to expand...
Click to collapse
That's exactly what is happening. Was wanting to load the TNT lite or Vegan to try out a different rom and now I can't do it.
K J Rad said:
When the tablet is put into APX mode the screen will go black. I don't use windows so I can't be much help with the rest but it would help if you told us what the error is when you try to start the file.
Click to expand...
Click to collapse
I will post the error message once I try it again at home. I do get the black screen. Thanks for your help.
Error message when trying NVFlash
K J Rad said:
When the tablet is put into APX mode the screen will go black. I don't use windows so I can't be much help with the rest but it would help if you told us what the error is when you try to start the file.
Click to expand...
Click to collapse
The Message that shows up on the command window
"nvflash.exe" ---bct gtablet.bct ---setbct ---bl bootloader.bin ---configfile gtablet.cfg --create --go
NVFlash Started
NVFlash configuration file error: file not found
Please enter to continue
That's exactly what I see when I double click the nvflash_gtablet Windows batch file
Alright so I tried a few things and it seems like I needed to copy the files rather than the folder to the NVFlash folder. So I did that. NVFlash was successful but now it's stuck in boot loop. Now what do I do?
Ok... if you read any amount of the flashing process threads you would know using rom manager is a quote"****ing bad idea"end quote. Nvflash and a repartition using cwm is your only hope.
Flash cwm as an update.zip and repartition

[Q] Clockwork mod bootloops

Hello. Today i managed to install small update from this thread: http://forum.xda-developers.com/showthread.php?t=1563249
I sucessfully flashed it through cwm, and I also booted. But then i accidentaly pressed OTA asus update and im now stuck in Cwm Recovery v3.1.0.1 (solarnz-R-230511-1902). I cant access my nandroid backup since this recovery doesnt support internal storage and i when i press reboot system i get recovery loops (tablet restarts but android wont boot, im again in cwm). So i managed to flash some other versions of cwm, i flashed them, but again, after reboot im still in this recovery ... then i tried this guide http://www.transformerforums.com/fo...overy-bootloop-fix-tested-my-c10-windows.html but i havent set an adb to my device before so when im in command prompt it doesnt recognize my tablet so its pretty awkward (maybe because i havent usb debugging on - is there any way to turn it on??). So im an epic noob, can someone give me advice how to unbrick my lovely tablet? I´ll be very very greatful please help...
If you have an sbk v1 version you could use nvflash to unbrick. Check your serial #
Hmm, I already solved it Just did cold boot and wrote some things with terminal emulator...
Hi,
Am exactly in the same situation, have to cold boot to use the tablet.
Could tou please detail what you did to solv the problem once under android ?
Thanks in advance.
Check this http://forum.xda-developers.com/showthread.php?p=23339963 . You'll need to connect to a PC and us adb to connect (Google it if you are not sure what it is or how to use it).
Then reboot since you'll be right back in CWM, run the advanced script. I would replace that version as soon as possible with the working version of CWM.
Sent from my Transformer TF101 using xda premium

[Q] [solved] Won't boot - No ADB, no CWM/, no "wipe data", no nvflash (c20 serial)

[Q] [solved] Won't boot - No ADB, no CWM/, no "wipe data", no nvflash (c20 serial)
Thanks for reading.
I recently bought a refurbished Transformer with a serial starting with c20. I rooted with vipermod, installed recoveryinstaller and AOKP. After being unable to install CWM (I now know why) my device became unable to boot into recovery. Recoveryinstaller would not install either. When I attempted to normal boot, the device would just hang. My only option was to cold boot into linux, which worked.
I then attempted to "full wipe" in order to re-install recoveryinstaller for access to recovery. After doing so, my Transformer no longer boots. It sits at the "Android" splash screen, which I believe is AOKP still attempting to load. Recovery doesn't boot, full wipe only beings me back to the "Android" splash, and cold booting into linux also returns me to the "Android" splash.
After lots of searching and reading, I found a few help threads that offered suggestions for those unable to boot, but they all require adb. My understanding based on the adb tutorial is that it requries configuration within the Android OS, and for the device to be running, which mine does not. And from what I've read, the c20 serial number isn't compatible with nvflash.
Can someone point me in the right direction? I feel like I'm at a dead end here. Thanks a bunch.
-Chris
edit: to clarify, I never setup ADB, which makes me think that solutions like this won't work: http://forum.xda-developers.com/showthread.php?p=25636698#post25636698
Hello cfbauer,
Did you try this driver pack? after 1st remove all you transformer drivers?
http://forum.xda-developers.com/showthread.php?t=1514942
If you install this, then you can check with adb if there is communication possible with your transformer. if you connect it, is there any life on your pc when you start your TF?
or volume + and power to put tablet in apx mode and see if then the apx driver installs. If it does then try the brks rootkit v7.1 to see if you can install cwm with this tool....maybe your refurbished TF is an old B40 to 70).
unless this is what you already did......
dont forget to disable spashtop and asys sync on your pc.......
Well I managed to get ADB setup, I think. I'm new to this, but when I attempt to boot into recovery, and do "adb devices" I get "0123456789ABCDEF offline".
I'm a little hesitant to try nlheiz's suggestion of brks rootkit v7.1 as it says it's for a serial number that's older than my device is. nlheiz, can you confirm this is safe? Or can someone else suggest an alternate method of getting my 2 week old Transformer to a useful state? I definitely appreciate the help.
-Chris
edit: I just read this
The only thing that differs between SBK1 tablets and SBK2 tablets is the use of NVFlash. SBK2 cannot use NVFlash, so if you end up botching both your recovery and your ROM, and cannot boot into either, then you are SCREWED, so I would suggest reading everything before attempting to mod your device if you are an SBK2 owner.
Click to expand...
Click to collapse
There is no emoticon to convey how sad I am right now
edit2: I'm looking at trying this guide: http://www.transformerforums.com/fo...overy-bootloop-fix-tested-my-c10-windows.html since it appears to be able to fix the issue I'm having.
edit3:attempting the guide posted in edit2 is giving me a "error:device offline" on step 6 when I try the adb push command
edit4: I can't seem to download brk Universal Rootkit 7.1 as neither download link is working
Does anyone have a suggestion? I'd appreciate it. Or is my device totally dead and I'm just screwed?
Try NvFlash anyway, It can't hurt. Does ADB work at all?
Thing O Doom said:
Try NvFlash anyway, It can't hurt. Does ADB work at all?
Click to expand...
Click to collapse
Thanks for your response. I get "0123456789ABCDEF offline" when I type adb devices when I boot into recovery mode, which isn't actually recovery mode since the system it hangs when I try to boot into recovery mode.
cfbauer said:
Thanks for reading.
I recently bought a refurbished Transformer with a serial starting with c20. I rooted with vipermod, installed recoveryinstaller and AOKP. After being unable to install CWM (I now know why) my device became unable to boot into recovery. Recoveryinstaller would not install either. When I attempted to normal boot, the device would just hang. My only option was to cold boot into linux, which worked.
I then attempted to "full wipe" in order to re-install recoveryinstaller for access to recovery. After doing so, my Transformer no longer boots. It sits at the "Android" splash screen, which I believe is AOKP still attempting to load. Recovery doesn't boot, full wipe only beings me back to the "Android" splash, and cold booting into linux also returns me to the "Android" splash.
Can someone point me in the right direction? I feel like I'm at a dead end here. Thanks a bunch.
-Chris
Click to expand...
Click to collapse
How did you get AOKP ROM on the TF if you couldn't get CM to install?
Are you still on stock recovery? I know yo usay recoery doesn't boot but what does it do when trying to boot into recovery?
Doe sit hang or you get any message?
FOR ADB offline message, have you try a different USB port?
baseballfanz said:
How did you get AOKP ROM on the TF if you couldn't get CM to install?
Are you still on stock recovery? I know yo usay recoery doesn't boot but what does it do when trying to boot into recovery?
Doe sit hang or you get any message?
FOR ADB offline message, have you try a different USB port?
Click to expand...
Click to collapse
OMG it worked! I'm back baby! So exited. Thanks for your help! I suppose this means my Transformer is an SBK1. Nice.
To answer your questions if you're curious, I used RecoveryInstaller. It was CWM, but an older version, my mistake. I ran into the random reboots issue, but the version of CWM recoveryInstaller used wasn't compatible with Aroma, which was required to install a custom kernel.
I don't remember the exact text on screen when I try to load into recovery, but I believe it was something like "booting into recovery mode."
And yes, I did try a different usb port for adb, it didn't work. Thanks for the suggestion though!
Thing O Doom said:
Try NvFlash anyway, It can't hurt. Does ADB work at all?
Click to expand...
Click to collapse
Worked! Thanks for the heads up!
By the way, you don't need Aroma to install a custom kernel with AOKP. Since I utterly refuse to flash touch recovery (no ext-sd support) I can't use aroma. The classic way is to go grab the .zip of the kernel (I recommend Testymehics or Guevor's test kernels) out of development. Clear cache, then flash as if you were flashing a rom, no aroma required.

[A510][RECOVERY][2012-12-15] CWM-based Recovery 6.0.1.9 (JB compatible)

CWM-based recovery 6.0.1.9 for the Acer Iconia TAB A510​
Another recovery build? Yes... But I can say this recovery is pretty safe. Having said that, however:
*** I am not responsible for anything that happens to your device ***
There is still a risk in bricking your tablet​
I've been testing various different ways to get custom ROMs going on this tablet, for over 6 months now. Developing for this tablet seems kinda dangerous (compared to my private building on HTC devices), and I already had to send my device back to Acer because of a brick once. At this point, I guess this recovery seems pretty safe, and hence I'm willing to release it in public. This recovery is inspired by the CWM-based recovery 6.0.1.1 for the Icona TAB A700 by pawitp. So first of all, I want to say thanks for his work and the talks we had.
The recovery itself is built by me so all partitions on the A510 are propely initialized, sized, and mounted: Including access to both internal storage (the 'fake' sdcard) and external MicroSD cards, as well as the flexrom partition. As an additional (see below) precaution, i've supressed 'EMMC wipe' commands in the recovery.
The kernel for this recovery has been compiled by me, disabling all the MMC_CAP_ERASE functions to prevent the 'Samsung EMMC brick' from happening. This does not give you a 100% guarantee, but it comes pretty close.
As explained in this post, the new CWM recovery does not really format your /data partition. It simply removes all files with the 'rm' command, leaving your 'fake' sdcard intact. The recovery in this post does format your other partitions, but it should show this message: 'warning: wipe_block_device: Wipe via secure discard suppressed due to bug in EMMC firmware'. Don't worry, that's a good thing!
Things to note:
I have mounted every partition with this recovery without problems
I have formatted/wiped every partition with this recovery without problems
I have backed up and restored (nandroid) every partition with this recovery without problems
I have installed custom .ZIP files with this recovery without problems
I still won't give you any warranties - This recovery can brick your tablet
How to install:
Step 0:
Check this thread to see if you can help the community before you let us help you!
Step 1:
Copy the file attached to this post (remove_recovery_from_rom.zip, (MD5: 73aea1147f571a83caeb8743cd5972b4)) to your tablets internal memory or SD Card. Download the CWM-Based Recovery by NoThrills for A510 tablets and save it somewhere on your computer.
Step 2:
If your device is already bootloader unlocked, skip step 3. Your boot screen (the one with the Acer logo when you turn the device on) should read Bootloader Version x.xx.xx-ICS (Unlock Mode). If your device is not yet unlocked, continue to the next step:
Step 3:
Connect your tablet to your computer via USB. Make sure you have the Android SDK installed, and perform the following command:
adb reboot-bootloader
When the tablet reboots to the Acer logo, perform the next command:
fastboot oem unlock
Then, quickly press the Volume down (**) button on your tablet, followed by the Volume up (*) button to confirm the unlock. When done:
fastboot reboot
Step 4:
Connect your tablet to your computer via USB. Make sure you have the Android SDK installed, and perform the following command:
adb reboot-bootloader
When the tablet reboots to the Acer logo, perform the next command:
fastboot flash recovery recovery_nothrills.img
This assumes you have put the nothrills_recovery.img in the same folder as the ADB utility.
Step 5:
Reboot your tablet with the following command, but you have to keep the Volume down (**) button pressed when the tablet boots:
fastboot reboot
Step 6:
Install the remove_recovery_from_rom.zip file from the Recovery, then reboot your device.
Your tablet now has this new recovery installed. You can enter the recovery by typing the command adb reboot recovery, or by booting your tablet with the Volume down (**) button pressed.
​
Downloads:
CWM-Based Recovery 6.0.1.9 (mirror) (mirror)
(MD5 for .img: 950b877a8d10d7de80ec7055b6367893)
CWM-Based Recovery 6.0.1.4 (mirror) (mirror)
(MD5 for .img: b0f9d33342943b44b998bd8f127800a8)
CWM-Based Recovery 6.0.1.3 (mirror) (mirror)
(MD5 for .img: 6ea6e278ebe2e9f093bcdef5ea07a990)
Stock Acer 1.044.00 recovery (mirror) (mirror)(note: you only need this to return to a stock Acer recovery)
(MD5 for .img: 7b58b9b76c4e39cafa9d926b57fe08fd)
Anything else?
That's what this thread is for, so post away...
Reserved
Great news! I'll have a try after i get my tab back.
btw, is there any Custom Rom available for A510?
finally we have CWM! Can´t wait to get CM10 on my A510!
Seems to work quite well, so far no probs - thank you
Great news just wish I new how to use adb.I have read so many ways on how to use it but can never get it to work.Now we need to get roms built.Is there anyway to get it to work with the Acer toolbox.
Great, thanks !
Great piece of news!
jessejames44 said:
Great news just wish I new how to use adb.I have read so many ways on how to use it but can never get it to work.Now we need to get roms built.Is there anyway to get it to work with the Acer toolbox.
Click to expand...
Click to collapse
Make sure to have the required DLLs in the same directory you are executing adb from (or in a specified PATH).
Sent from my A510 using xda app-developers app
Well I flashed this and even though it says the recovery is successfully written, when I reboot into recovery all I get is the android with the red exclamation mark and it never boots into the recovery at all??? weird.
Notice that the recovery files has been mixed up, but when you download from the mirror link, the nothrills_recovery.img is in it.
Just redo the procedure with the right file, not the factory 1.0.044, and you will be good to go.
On a subsequent note to the dev:
This is ****ing brilliant!
It works, damn it! Thank you for the work, we've been waiting for this **** to come along for a looong time, and even thou you stand on shoulders from work done on the A700, be asured that a lot of us is clappin' our hands now, thanks to you
Sincerely Omnius
Sent from my A510 using xda app-developers dope
Omnius001 said:
Notice that the recovery files has been mixed up, but when you download from the mirror link, the nothrills_recovery.img is in it.
Just redo the procedure with the right file, not the factory 1.0.044, and you will be good to go.
On a subsequent note to the dev:
This is ****ing brilliant!
It works, damn it! Thank you for the work, we've been waiting for this **** to come along for a looong time, and even thou you stand on shoulders from work done on the A700, be asured that a lot of us is clappin' our hands now, thanks to you
Sincerely Omnius
Sent from my A510 using xda app-developers dope
Click to expand...
Click to collapse
I have tried both of the files from the regular and the mirror sites and it says it completed ok, but I still do not have the custom recovery. I have done this many times on different devices and this is the first time it does not work, I am following the instructions by the letter too. LOL!!!
Anyone with A511 tested it ?
Omnius001 said:
Notice that the recovery files has been mixed up, but when you download from the mirror link, the nothrills_recovery.img is in it.
Just redo the procedure with the right file, not the factory 1.0.044, and you will be good to go.
On a subsequent note to the dev:
This is ****ing brilliant!
It works, damn it! Thank you for the work, we've been waiting for this **** to come along for a looong time, and even thou you stand on shoulders from work done on the A700, be asured that a lot of us is clappin' our hands now, thanks to you
Sincerely Omnius
Sent from my A510 using xda app-developers dope
Click to expand...
Click to collapse
Does anyone know if this could be flashed using terminal emulator. Using ADB I get confirmation that it sent and wrote the files ok to the tablet, but I still just get the dead android with the red exclamation when I try booting into recovery, regardless of wheather I use adb or the button holding methods.
Jesse6749 said:
Does anyone know if this could be flashed using terminal emulator. Using ADB I get confirmation that it sent and wrote the files ok to the tablet, but I still just get the dead android with the red exclamation when I try booting into recovery, regardless of wheather I use adb or the button holding methods.
Click to expand...
Click to collapse
Have u checked the MD5? (MD5 for .img: 6ea6e278ebe2e9f093bcdef5ea07a990)
Maybe u should download the file again and make sure the MD5 correct.
jokerzlh said:
Have u checked the MD5? (MD5 for .img: 6ea6e278ebe2e9f093bcdef5ea07a990)
Maybe u should download the file again and make sure the MD5 correct.
Click to expand...
Click to collapse
I did check the MD5 and it matches the MD5 on the OP and on your post as well, so the file is good. I have re downloaded the file 4 times already too.
Did you really reboot directly into recovery after flashing? If you were a little too slow and gave the stock firmware a chance to boot it will first reflash the stock recovery. If you then boot again and go into recovery you will get the fallen droid with exclamation mark.
I had experienced the same problem. After flashing the recovery it will automatically reboot and give you an extremly short time frame to go into recovery.
Mechkilla said:
Did you really reboot directly into recovery after flashing? If you were a little too slow and gave the stock firmware a chance to boot it will first reflash the stock recovery. If you then boot again and go into recovery you will get the fallen droid with exclamation mark.
I had experienced the same problem. After flashing the recovery it will automatically reboot and give you an extremly short time frame to go into recovery.
Click to expand...
Click to collapse
This is what I'm thinking as well. I should probably edit the instructions on the first post, as I didn't think about the fact that people might not have the recovery_from_boot files removed.
Mechkilla said:
Did you really reboot directly into recovery after flashing? If you were a little too slow and gave the stock firmware a chance to boot it will first reflash the stock recovery. If you then boot again and go into recovery you will get the fallen droid with exclamation mark.
I had experienced the same problem. After flashing the recovery it will automatically reboot and give you an extremly short time frame to go into recovery.
Click to expand...
Click to collapse
I just followed the instructions and rebooted into ICS then ran the adb reboot recovery command. So you are saying to run the adb reboot recovery command immediately after it finishes flashing. I may just try this later today. I got it to boot into recovery once and then went back to the dead android, then I followed the updated instructions on the op and now it works every time and it boots into the CWM recovery every time.
Sent from my Transformer Prime TF201 xda premium
Jesse6749 said:
I just followed the instructions and rebooted into ICS then ran the adb reboot recovery command. So you are saying to run the adb reboot recovery command immediately after it finishes flashing. I may just try this later today.
Sent from my Transformer Prime TF201 xda premium
Click to expand...
Click to collapse
I've updated the first post with a 'remove recovery' .ZIP file. Follow the new instructions and you should be set.
Super cool to see the development for the A510 finally with some results!!!! I love tyo get some custom stuff for our A510's...is there anything I can help you with? If there's something I could do to speed up the custom ROM process, just ask

Device stuck in bootloop?

Hi guys,
So this is my first post but I've been on XDA for a long time. I've been looking for an answer to this problem, and I haven't been successful in finding a post that regards to my situation...
Ok so I just got my tablet today. I upgraded to JB and then I unlocked it using the asus unlocker. I attempted to install TWRP, but when I use .blob files and attempt to load into recovery it didn't work. Anyway, I looked around and I installed CWM recovery instead.
I installed v5.5.0.4 following this guide:
http://theunlockr.com/2012/05/25/how-to-install-clockworkmod-recovery-on-asus-transformer-tf300t/
Now, I notice it's written back in may of 2012 aka before jelly bean... anyway so I installed this using fast boot, and booted into recovery and it worked. I believe I installed the ICS version of CWM. I tried to install Clean Rom v3.3 and I just get bootloops. I can still boot into fastboot and clockwork mod fine.
I tried to install v6.0.1.4 via this thread http://forum.xda-developers.com/showthread.php?t=1846554
But once again if I boot into recovery it just does nothing and reboots after a few seconds.
I re-installed v5.5.0.4 and I can wipe data/install everything just as I normally would, and I still have access to Fastboot. Can I get some help on how I can 1 install the correct CWM and 2 install a working rom? I don't think I bricked my device just yet since I can still flash in fastboot etc.
Thanks guys!
You cant't wipe data from bootloader menu, If you do that, you will get unrecoverable brick.
Sorry I believe I mislead you -> I wiped data from within CWM.
Anyway, I used this thread:
http://forum.xda-developers.com/showthread.php?t=1757077
I went back to stock and I think i'll stay there for a little while longer, this process made me nervous (I've rooted my thunderbolt, droid DNA, galaxy tab 2 7" and my friends phones) so anyway I believe I installed the wrong CWM and that caused errors trying to install a JB rom on a ICS CWM... If you have any insight let me know...
undergfx said:
Hi guys,
So this is my first post but I've been on XDA for a long time. I've been looking for an answer to this problem, and I haven't been successful in finding a post that regards to my situation...
Ok so I just got my tablet today. I upgraded to JB and then I unlocked it using the asus unlocker. I attempted to install TWRP, but when I use .blob files and attempt to load into recovery it didn't work. Anyway, I looked around and I installed CWM recovery instead.
I installed v5.5.0.4 following this guide:
http://theunlockr.com/2012/05/25/how-to-install-clockworkmod-recovery-on-asus-transformer-tf300t/
Now, I notice it's written back in may of 2012 aka before jelly bean... anyway so I installed this using fast boot, and booted into recovery and it worked. I believe I installed the ICS version of CWM. I tried to install Clean Rom v3.3 and I just get bootloops. I can still boot into fastboot and clockwork mod fine.
I tried to install v6.0.1.4 via this thread http://forum.xda-developers.com/showthread.php?t=1846554
But once again if I boot into recovery it just does nothing and reboots after a few seconds.
I re-installed v5.5.0.4 and I can wipe data/install everything just as I normally would, and I still have access to Fastboot. Can I get some help on how I can 1 install the correct CWM and 2 install a working rom? I don't think I bricked my device just yet since I can still flash in fastboot etc.
Thanks guys!
Click to expand...
Click to collapse
My suggestion is to flash the latest stock JB blob.
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
Once you get it sorted then flash the latest twrp for jb.
Now, when I try flashing blobs and I go to boot into RCK (I believe that's the term...) it just reboots the tablet instead of booting into recovery.
Android software is out of my element, if this was some C (somewhat similar to C) or Matlab I would better understand (I'm a senior Mechanical Engineer in college)
Edit:
Ah didn't see your post. I did what you recommended, and actually, while my device said it was on 4.1.1 JB, when I hold pwr/vol down I see a completely different menu now than last time, so I wonder if perhaps my OTA didn't correctly load everything from the firmware update hmm...
undergfx said:
Now, when I try flashing blobs and I go to boot into RCK (I believe that's the term...) it just reboots the tablet instead of booting into recovery.
Android software is out of my element, if this was some C (somewhat similar to C) or Matlab I would better understand (I'm a senior Mechanical Engineer in college)
Click to expand...
Click to collapse
The same way you flashed cwm.
Windows? Start - in search type cmd - press enter
In the cmd window cd to the directory with fastboot.
Hook cable between tablet and usb port on computer.
On tablet hold power and volume down till you see the bootloader menu.
Down volume till you are at the usb symbol - then volume up.
This should put you into fastboot mode - use the commands above.
Wait till the first command completes before you give the second command.
[INDEX][04 Feb 2013]TF300T & TG-INDEX of Roms/Dev Guides/Kernels/Recoveries/etc. You will find the stock firmware here as well as most other needs.
You will have to unzip to get the blob which you should place in the directory with fastboot.
Thank you very much.
So after flashing the most resent blob, I successfully installed CWM recovery and successfully flashed a rom. I'm not sure what the issue was before. Thank you for the help! much appreciated.
undergfx said:
Thank you very much.
So after flashing the most resent blob, I successfully installed CWM recovery and successfully flashed a rom. I'm not sure what the issue was before. Thank you for the help! much appreciated.
Click to expand...
Click to collapse
You're welcome.
Good Luck!

Categories

Resources