Related
I rooted my TF101 model B80 using RazorClaw (nvflash is a no-go for this model). Installed CWM, all was well. I tried to install Prime ROM from CWM, and was unimpressed; tried to restore my Nandroid backup of original rooted OS. Now, Transformer will not boot into any recovery (neither CWM or original green android), and screen comes up garbled. Is there any way I can restore my original stock by merely putting a particular image on my external sd card?
Any other suggestions welcome, I just can't get to a screen (recovery or otherwise) where there is any readable text I can respond to. Nor can I turn the device off. It will continue to reboot in this fashion. When I get home today I'll be able to start from a dead battery.
Thanks
Did you wipe before restore?
davebugyi said:
Did you wipe before restore?
Click to expand...
Click to collapse
Yes, I did a full wipe including dalvik cache before all restores. At this point, though, my primary concern is just finding a path back to usability!
DIncLover said:
I rooted my TF101 model B80 using RazorClaw (nvflash is a no-go for this model). Installed CWM, all was well. I tried to install Prime ROM from CWM, and was unimpressed; tried to restore my Nandroid backup of original rooted OS. Now, Transformer will not boot into any recovery (neither CWM or original green android), and screen comes up garbled. Is there any way I can restore my original stock by merely putting a particular image on my external sd card?
Any other suggestions welcome, I just can't get to a screen (recovery or otherwise) where there is any readable text I can respond to. Nor can I turn the device off. It will continue to reboot in this fashion. When I get home today I'll be able to start from a dead battery.
Thanks
Click to expand...
Click to collapse
I had the same situation..I used the unbrick method:
http://forum.xda-developers.com/showthread.php?t=1123429
then you could try restore a backup ..
To turn off the device press the power button for 10-15 seconds..
bruuuno said:
I had the same situation..I used the unbrick method:
http://forum.xda-developers.com/showthread.php?t=1123429
then you could try restore a backup ..
To turn off the device press the power button for 10-15 seconds..
Click to expand...
Click to collapse
I can try this when I get home today.... I'm just concerned because the method involves nvflash .... which I thought didn't work from the newer TF models (I have a model B80). I needed to wait for the RazorClaw exploit because previous attempts at using nvflash failed....
Then NVFlash will fail still...
davebugyi said:
Then NVFlash will fail still...
Click to expand...
Click to collapse
So am I hopelessly hosed?
Sounds like this problem
http://forum.xda-developers.com/showthread.php?t=1321207&highlight=green+screen
Being you can't get back into CWM not sure how you'll flash the stock kernel.
HAve you tried Holding Vol Down button plus Power button till you get prompt to enter recovery at which time immediately push Vol up button withion 5 sec.
baseballfanz said:
Sounds like this problem
http://forum.xda-developers.com/showthread.php?t=1321207&highlight=green+screen
Being you can't get back into CWM not sure how you'll flash the stock kernel.
HAve you tried Holding Vol Down button plus Power button till you get prompt to enter recovery at which time immediately push Vol up button withion 5 sec.
Click to expand...
Click to collapse
OK .... my bad.... I guess I wasn't pressing the buttons in the right sequence/duration. I CAN get to CWM!
So, once again, I try to restore the Nandroid backup and after rebooting, end up with the screen situation as in the reference you provided.
So, I am assuming my Nandroid backup is not restoring the kernel that it needs. I was running a recent OTA update; I believe the version was 8.6.5.19.
Where can I get the appropriate kernel to install from CWM? Does it matter in what order I install the kernel and the Nandroid backup?
DIncLover said:
Where can I get the appropriate kernel to install from CWM? Does it matter in what order I install the kernel and the Nandroid backup?
Click to expand...
Click to collapse
Look here
http://www.gnufabio.com/revolver/dls/
Same issue, no recovery though
Hi,
I have the same issue as the original poster, B80 serial, RazorClaw root. However, when I boot to recovery I get the green android with yellow triangle and exclamation mark.
I need to restore a recovery on my device as I may need to unroot to send to Asus. I have an even deeper problem of having to have the device connected to power for it to turn on after shut down.
However my main question is for that serial number and root method, what is the best way to flash a recovery on my device (stock or CWM) if I can not get into recovery to begin with?
P.S. RecoveryInstaller will not work, after installing the apk, I click the flash recovery button, the system holds for a bit, then nothing happens.
I will continue to search the forms for some answers, any insights or direction will be appreciated.
I can get into apx mode.
Thank you community!
I think you can flash the recovery via the staging partition. Search around the TF section, it's in here somewhere. Although, I wonder why the 1 click recovery didn't work?
gee one said:
I think you can flash the recovery via the staging partition. Search around the TF section, it's in here somewhere. Although, I wonder why the 1 click recovery didn't work?
Click to expand...
Click to collapse
Everything I see in the forms requires one of several conditions which my TF doesn't currently meet.
1. Recovery. I can not go into any recovery, thus I can not perform any flashing of any other rom or recovery.
2. B70 or later. Because of the security in the boot for these new serials, I can not use the NVFlash tools to un-brick / flash.
I am already rooted, however I do not know the reason for lack of recovery on this device. I unfortunately bought it yesterday from Craigslist, so not sure what this guy did before I got it.
I searched for flashing recovery staging partition and did not find anything immediately relevant. Please advice is there is a different wording I should use in my search as I am now getting an immense download on all of this trying to figure out what to do. I am also fairly new to Android devices having 1 other phone that is rooted.
Thank you for all the support and quick response! wonderful community here.
Try searching for posts with /dev/block/mmcblk0p4
This is particularly dangerous because you don't have access to nvflash. If you get bootloops, it is bricked. You have to be sure that whatever you flash will be 100% compatible with what you have now.
Also, when you try to boot into recovery, what does the text at the top say? There should be a version number in there somewhere.
sent from my cyanogen(mod) vision
gee one said:
Try searching for posts with /dev/block/mmcblk0p4
This is particularly dangerous because you don't have access to nvflash. If you get bootloops, it is bricked. You have to be sure that whatever you flash will be 100% compatible with what you have now.
Also, when you try to boot into recovery, what does the text at the top say? There should be a version number in there somewhere.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
Thank you gee one. I have since been able to install clockworkmod. My issue with the power not turning on if not plugged in still persists, I have started a separate thread.
I found your post on the staging partition here:
http://forum.xda-developers.com/showthread.php?t=1309949&highlight=power
Do you recommend this for the issue still persisting?
If so, considering I am on 8.6.5.19 will I have to use the blob from that? It is not on Asus website as I got it from the firmware update option in the settings before loading up my new ROM.
Do you recommend this step as the only resolution or is there another way?
Ok let me get this straight:
You have clockworkmod installed. Can you boot into it and do the buttons work?
Are you getting a garbled screen when you boot into the rom? Or are you just trying to unroot?
The tricky part is to avoid the bootloops of death.
sent from my cyanogen(mod) vision
Honestly what i would do if i were you, assuming i understood correctly that you can get into clockworkmod, just reflash the prime rom you didnt like(after wiping everything, including cache and dalvik), and if it boots and everythings okay, at least you know nothings really wrong with ur tablet. As for the plug in situation, make sure your battery isnt simply dead. As far as i know, it wont charge from recovery, so if uve been stuck without a booting rom for a while, it being dead could definitely be possible. Once you are in a working rom and you sorted out the charging issue, then you should worry about getting back to stock.
Thank you camaros,
I am able to load stock ROM successfully.
Battery is not dead as it is fully charged, and will run un tethered after powerup. I will test resetting it although I doubt that is causing it.
What i would like to determine is, is this related to a hardware or software issue?
Also, is there a way to restore stock recovery from CWM?
So here's my story. I rooted my transformer (rooted with razorclaw and CWM recovery, had no problems) and I wanted to update the firmware, sooo. I followed some walk through on unrooting by downloading the stock recovery and stock rom to my sdcard then unzipping them and loading them with CWM recovery. I let it boot and rebooted to load in the stock rom. Then I rebooted and loaded the stock recovery and rebooted again. And now it wont start up past the "Asus Eee pad Transformer" screen and just stays on it. I can get into part of stock recovery and wipe data and cold boot linux. But when I try to get into the other half of recovery options it just does the little robot unpacking the stuff then I get a triangle with an exclamation mark saying it failed to load. I tried using NVflash with the prime v1.4 ROM and failed. The starting S/N is B90 so that's why I figured NVflash didn't work...Because I have V2 SBK not V1. I can go into APX mode but it's getting really frustrating, WHAT CAN I DO??
I don't think you were supposed to unzip those files. Those are CWM flashable zip files
baseballfanz said:
I don't think you were supposed to unzip those files. Those are CWM flashable zip files
Click to expand...
Click to collapse
I actually dont think I did unzip them so ignore that...I used this method at the unlockr
-theunlockr[dot]com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
Yeah cause i was thinking if you did unzip it wouldn't flash anyway.
How long does is sit at the asus screen?
Sent from my Transformer TF101 using Tapatalk
forever until it dies, I can only get partially into recovery like I mentioned. Also when it charges it just shows that screen too(had to charge it cuz I got so frustrated I just left it and it ended up dying).
Please someone help, I have no idea how to flash a rom to my Device without NVflash. Is there some other program I could try that would work? I basically just need to flash a rom onto my device then I can try installing stock recovery again
Long shot but maybe try this, it's what peoples are doing to downgrade. Hopefully the recovery might pick it up after you reboot into recovery.
http://forum.xda-developers.com/showthread.php?p=20799328
I'll try this, but the download is taking forever...I'll have to update tomorrow thanks for your help
I tried in both the LOST.DIR folder and the main directory...the device didn't recognize it. I don't know what to do
Is there any other way to flash a rom on my transformer besides NVflash? or any other method? I'm up for anything now...does anything think if I sent it in to company they could do a restore?
The company could do a restore, but they will probably charge you since you rooted. You could try, or you could lie, and say it goobered after installing the update.
Hello,
I have a rooted, locked TF300T. I tried to flash TWRP via ADB back in ICS with locked bootloader but that apparently just broke my recovery (does it check signature before launching it?). I then OTA upgraded to latest JB (10.4.2.18) but I still cannot enter recovery (red triangle). Even if of little use, how can I get the right blob to flash on /dev/block/mmcblk0p4 to restore it?
I'd like to stay locked for a while since I just got this pad, if everything's smooth I may then consider unlocking and wild-flashing averything.
Download stock ROM from ASUS webside and flash the huge blob file to staging partition.
Sent from my GALAXY Cooper
100% sure it will not mess with root, installed system and so on once I try to boot recovery?
Sent from my Galaxy Nexus
poochie2 said:
Hello,
I have a rooted, locked TF300T. I tried to flash TWRP via ADB back in ICS with locked bootloader but that apparently just broke my recovery (does it check signature before launching it?). I then OTA upgraded to latest JB (10.4.2.18) but I still cannot enter recovery (red triangle). Even if of little use, how can I get the right blob to flash on /dev/block/mmcblk0p4 to restore it?
I'd like to stay locked for a while since I just got this pad, if everything's smooth I may then consider unlocking and wild-flashing averything.
Click to expand...
Click to collapse
When you took the ota you had stock recovery. Stock recovery is what installs otas and also updates you place on your tab to encourage updates or downgrades. Stock recovery is what is giving you the red triangle. It is telling you there is no update seen on your tab. I have never seen any type of menu on stock recovery either the red triangle or the fact that is is updating.
You can't flash twrp or cwm while locked! If you could there would be no reason to unlock.
There is much confusion about stock recovery. I have even seen posts saying there is no stock recovery. I think this is because the stock recovery does not present you with a menu and if it does not find a stock file to flash it presents the red triangle.
I hope this helps!
Place Asus stock 10.4.2.18 on your sdcard reboot the same as when you see the red triangle and accept the update. If no help there reboot normally with stock update still on sdcard. You should get a triangle notification of an update, accept the update.
adb shell
su
dd if=/sdcard/stock-recovery.blob of=/dev/block/mmcblk0p4 Then reboot to complete installation.
adb reboot
Thanks for clearing this one out, I think I'm already good then!
Sent from my Galaxy Nexus
poochie2 said:
Thanks for clearing this one out, I think I'm already good then!
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
You're welcome!
I also think you are already good.
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!
Been working on updating to JB 4.2 and wound up in a boot loop . Did successfully flash -TF700_421_US_BootRec_Flasher_Signed.zip and was previously unlocked and rooted with 4.1.
The problem now is that TWRP 2.5 is in a resolution that only allows half of the
buttons and options and options to show on the screen. Also re-flashed with -
openrecovery-twrp-2.5.0.0-tf700t.blob and tried with a few 2.4 versions with
same results. This makes it impossible to install any ROM to get out of the boot loop.
Any suggestions?
dengom said:
Been working on updating to JB 4.2 and wound up in a boot loop . Did successfully flash -TF700_421_US_BootRec_Flasher_Signed.zip and was previously unlocked and rooted with 4.1.
The problem now is that TWRP 2.5 is in a resolution that only allows half of the
buttons and options and options to show on the screen. Also re-flashed with -
openrecovery-twrp-2.5.0.0-tf700t.blob and tried with a few 2.4 versions with
same results. This makes it impossible to install any ROM to get out of the boot loop.
Any suggestions?
Click to expand...
Click to collapse
How about try to reflash the 4.2.1 bootloader and twrp using one package zip file? http://forum.xda-developers.com/showthread.php?t=2223492
Thanks for the reply.
That is exactly what I did first with the results mentioned in OP. Will give it another try,
that's why it is a little baffling.
Ok. I've fastbooted the blob from http://forum.xda-developers.com/showthread.php?t=2223492
successfully and am back to TWRP 2.5.0.0 but the resolution problem remains. So I am still boot
looping directly into a recovery I cannot use.
Can I use fastboot to flash the blob from TF700T_US_epaduser_V1061144UpdateLauncher to at least
return to a functional state and try to fix my TWRP problem latter?
dengom said:
Ok. I've fastbooted the blob from http://forum.xda-developers.com/showthread.php?t=2223492
successfully and am back to TWRP 2.5.0.0 but the resolution problem remains. So I am still boot
looping directly into a recovery I cannot use.
Can I use fastboot to flash the blob from TF700T_US_epaduser_V1061144UpdateLauncher to at least
return to a functional state and try to fix my TWRP problem latter?
Click to expand...
Click to collapse
Yeah, it's a good idea, flash back stock firmware to get back stock recovery, root the device then download goomanager from the market then try to install twrp again. I think your recovery bootloader maybe messup(reflash recovery from stock rom should address this issue).
I appreciate your input. Being somewhat new to android need some additional guidance.
Would renaming the stock 4.2 zip file to update.zip and issuing the update command work or is it
more complex?
dengom said:
I appreciate your input. Being somewhat new to android need some additional guidance.
Would renaming the stock 4.2 zip file to update.zip and issuing the update command work or is it
more complex?
Click to expand...
Click to collapse
That's incremental update. You want a full upgrade.
Alright, what wood be the proper way to proceed?
Sorry I need some hand holding.
dengom said:
Alright, what wood be the proper way to proceed?
Sorry I need some hand holding.
Click to expand...
Click to collapse
Alternative Firmware update Method: download full firmware from Asus web site.
1. Unzip the downloaded file (it will be another .zip)
2. Rename it to EP201_768_SDUPDATE.zip
3. Format FAT32 the MicroSD card that you will be using for the update process
4. Copy the file to (the root directory of) your MicroSD
5. Insert it into the tablet
6. Shutdown (power off) the tablet
7. Power it on by pressing and holding VOLUME DOWN and POWER buttons simultaneously
8. When you see white text in the top left corner of the screen, release the buttons ^^ and press VOLUME UP button twice
9. Wait patiently for 10 minutes or so and Done.
Thanks, will give it a try after work.
Also, I should preview my posts b4 submitting for spelling.
Well I think I've found part of the problem. I had to flash a CWM recovery to install the
official 4.2 update successfully. Going into settings I found that my device model has somehow been
change to a TF 300t from the correct TF700t. I believe this may be the cause of my TWRP resolution
problems.
I have no clue how this occurred. But, I do need some suggestions on correcting this.
On a side note booting into recovery now results in a dead robot. I will tackle this once the model reporting is
corrected
dengom said:
Well I think I've found part of the problem. I had to flash a CWM recovery to install the
official 4.2 update successfully. Going into settings I found that my device model has somehow been
change to a TF 300t from the correct TF700t. I believe this may be the cause of my TWRP resolution
problems.
I have no clue how this occurred. But, I do need some suggestions on correcting this.
On a side note booting into recovery now results in a dead robot. I will tackle this once the model reporting is
corrected
Click to expand...
Click to collapse
I suggest you should reflash the full Asus firmware which included the rom and bootloader. Just make sure you download the right version for your tf700 and the correct SKU and you are sure that you have the tf700 right? not the tf300!!
Yes it is definitely a TF700. I will try the re-flash of official 4.2.