OK so I was on "HairyBean v2.31" and decided to try "CROMBi-kk". So I first flashed "TWRP-TF300T-2_7_0_1.zip" as instructed in the "CROMBi-kk" instructions. Then I flashed "CROMBi-kk" everything seemed to go fine but after reboot I was stuck at the "CROMBi-kk" boot animation. So I wanted to go back to "HairyBean v2.31" so flashed "Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip". When I got back to HairyBean TWRP I first tryed to Format DATA, well this got stuck and had no choice but to hard reboot. Now when I go back into TWRP I get a screen that asks for a password. I can hit cancel and get passed it, but I can't mount any of the partitions. So this is where in stuck. I do have an NVflash backup. Can someone please help me get out of this mess.
shatterstar78 said:
OK so I was on "HairyBean v2.31" and decided to try "CROMBi-kk". So I first flashed "TWRP-TF300T-2_7_0_1.zip" as instructed in the "CROMBi-kk" instructions. Then I flashed "CROMBi-kk" everything seemed to go fine but after reboot I was stuck at the "CROMBi-kk" boot animation. So I wanted to go back to "HairyBean v2.31" so flashed "Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip". When I got back to HairyBean TWRP I first tryed to Format DATA, well this got stuck and had no choice but to hard reboot. Now when I go back into TWRP I get a screen that asks for a password. I can hit cancel and get passed it, but I can't mount any of the partitions. So this is where in stuck. I do have an NVflash backup. Can someone please help me get out of this mess.
Click to expand...
Click to collapse
Try this:
Possible Unbrick Solution for Unrecoverable Bootloader & Wrong TWRP Flashes
If that doesn't work you'll have to recover through NVFlash backups.
Restorer said:
Try this:
Possible Unbrick Solution for Unrecoverable Bootloader & Wrong TWRP Flashes
If that doesn't work you'll have to recover through NVFlash backups.
Click to expand...
Click to collapse
Thanks i'll give that a try, but if that fails is their a guide on how to use NVflash to restore my backup? All I can find is how to backup using NVflash but nothing on restoring it.
shatterstar78 said:
Thanks i'll give that a try, but if that fails is their a guide on how to use NVflash to restore my backup? All I can find is how to backup using NVflash but nothing on restoring it.
Click to expand...
Click to collapse
There's plenty in these threads but read them right through carefully first. I've never bricked mine so I have no idea what problems you might encounter. The last two are older guides written before Flatline for JB but info is still relevant. Ignore any stuff about CWM or ROM Manager.
http://forum.xda-developers.com/showthread.php?t=2538028
http://rootzwiki.com/topic/35086-gu...s-guide-unbrickrecoverdowngradeupgrade-tf201/
Same guide but with XDA experiences:
http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
Restorer said:
There's plenty in these threads but read them right through carefully first. I've never bricked mine so I have no idea what problems you might encounter. The last two are older guides written before Flatline for JB but info is still relevant. Ignore any stuff about CWM or ROM Manager.
http://forum.xda-developers.com/showthread.php?t=2538028
http://rootzwiki.com/topic/35086-gu...s-guide-unbrickrecoverdowngradeupgrade-tf201/
Same guide but with XDA experiences:
http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
Click to expand...
Click to collapse
I can't tank you enough for your help in pointing me in the right direction. I'm now back up and running:good: The first guide got me close, but did not fully unbrick, so I got creative. I will list the steps I took to maybe help others out.
1. First you need Fastboot get it here(http://matthill.eu/content/downloads/transformerprime-unlock/fastboot.zip)
1b. You will need the Universal_Naked_Driver found here (http://matthill.eu/content/downloads/transformerprime-unlock/Universal_Naked_Driver_0.72.zip)
1c. Unzip the drivers somewhere, if at any point during this guide Windows detects your tablet as an unknown device, point it to this location for the drivers.
2. Unzip fastboot.zip somewhere preferably in C:\ (I found that folder names with spaces can cause problems)
3. Download the official update for your device from Asus. Make sure you get the right one, US, EU, WW, etc.
4. Unzip the update twice so that way you have a blob file.
5. Place the blob file into your fastboot folder.
6. Open a command prompt and navigate to your fastboot folder and enter the fallowing commands.
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
This next command will take the longest. Also you will notice the green RCK icon will stop flashing and you will have a blue progress bar, This is normal. Do not run the last command(reboot) until the green RCK logo starts flashing again and the blue progress bar is full.
fastboot -i 0x0B05 flash system c:\fastboot\blob (your path may vary depending where you placed the fastboot folder)
Now that all is done run the last command.
fastboot -i 0x0B05 reboot
If you are back up and running congratulations you are unbricked, but if you are stuck at the white Asus logo follow the next additional steps. Only do this if you are not fully booting up after the first part of this guide.
1. You will need a microsd card(32G max) and has to be formatted to Fat32.
2. Next you are going to take the Asus update you downloaded above, and unzip it ONLY ONCE and rename it to EP201_SDUPDATE.zip
3. Place the newly renamed EP201_SDUPDATE.zip on your sdcard, make sure its on the root directory and not in a folder.
4. Now reboot to fastboot (Hold Power and Volume Down) Press Volume Up when the white text at the top appears.
5. When the fastboot menu comes up with RCK icon selected press Volume up.
6. Go have a beer, this will take some time. Do not touch anything, when it is done the Asus configuration wizard will be displayed.
7. Congratulations you are now hopefully fully unbricked.
Some Tips:
1. Make sure you have "Show File Extensions" enabled in Windows, if not then when you rename the update to "EP201_SDUPDATE.zip" it will actually be "EP201_SDUPDATE.zip.zip".
2. Use Windows 7 if possible, Windows 8 just causes problems.
3. Disable Windows UAC or run fastboot as administrator.
4. Use a stock OEM data cable.
5. Make sure you have a fully charged tablet, cant stress this enough if your battery dies during this process, then you are in some serious trouble.
Credit goes to Buster99 for discovering the first part of this guide.
Bricked my prime
Hello, I have a big problem. I am in the possession of a TF201 and wanted to install the slimkat-rom for the Tf201. I had the topical Bootloader with Harybean V2.31 installed.
Then I have the Recoery (form the Startpost of the rom) in my present Rocovery installed (Custom TWRP v2.7.1.0 JB/KK for TF300T [with device checking] | STABLE)
Afterwards I have restarted the device. Everything functioned perfectly... on it I have booted up in the Recovery. In it I made a Factory-Reset. This became not explained... the device approx. 1 hour got stuck.
On it there I have restarted the device by hand... now I have the problem that I do not come any more to the Recovery. The device hangs with the picture "Teamwin"... I can do nothing more....also i can not go into the fastboot mode!??? (with the volume down button)
I already tried the solution about abd...but in cmd (Windows) always comes the statement "waiting for device"
What have I wrong made... what I can make? Can somebody help me? Please....
sorry for my bad english, thanks
maze44 said:
Hello, I have a big problem. I am in the possession of a TF201 and wanted to install the slimkat-rom for the Tf201. I had the topical Bootloader with Harybean V2.31 installed.
Then I have the Recoery (form the Startpost of the rom) in my present Rocovery installed (Custom TWRP v2.7.1.0 JB/KK for TF300T [with device checking] | STABLE)
Afterwards I have restarted the device. Everything functioned perfectly... on it I have booted up in the Recovery. In it I made a Factory-Reset. This became not explained... the device approx. 1 hour got stuck.
On it there I have restarted the device by hand... now I have the problem that I do not come any more to the Recovery. The device hangs with the picture "Teamwin"... I can do nothing more....also i can not go into the fastboot mode!??? (with the volume down button)
I already tried the solution about abd...but in cmd (Windows) always comes the statement "waiting for device"
What have I wrong made... what I can make? Can somebody help me? Please....
sorry for my bad english, thanks
Click to expand...
Click to collapse
Did you do a NVflash backup before all of this happened? If you did you can follow this guide to unbrick http://forum.xda-developers.com/showthread.php?t=2538028
I think the problem is "TWRP v2.7.1.0". I'm going to look more into it to see if I can figure what the problem is.
Thank you so much for the instructions post above. If you figure out what went wrong with flashing that rom, I would like to know too.
dangoon said:
Thank you so much for the instructions post above. If you figure out what went wrong with flashing that rom, I would like to know too.
Click to expand...
Click to collapse
Well I made some progress, I figured out why I could not mount partitions. Turns out that when I hit "Format Data" and thought that it froze, well it did not freeze it just takes really long to finish(~30min). Now I can install it, but no matter what I try it all ways gets stuck at the 4 penguins on the latest version or the bootanimation on the older version. I have tried every combination of twrp recovery's, kernals and varies versions of the rom, but still no luck. I have tried probably every rom available for this tablet and this is the only rom that just refuses to install. From the sounds of some of the problems this rom has I really don't want to use it, but now im so pissed off that I have to figure out why the hell this thing is not working I just cant quit.
[UPDATE]
Ok got it all squared away. Everything all up and running. The second part of my problem (getting stuck at bootanimation) was caused by doing a factory reset before flashing. So the correct way to flash it is...
1. Make sure you are on the Hairy Bean Bootloader.
2. Make sure you are using a 2.7 TWRP.
3. First Format Data. (It will take long, about 30mins)
4. The go into Advanced Wipe and check everything except SDCard.
5. When it's finished reboot, If all went well you should only be at the bootanimation for about 5mins.
Also if you get the four penguins after reboot, then you did something wrong.
Perfect
Legthy, but OMG thank you very much,
thought I was screwed..
I had to do the second part as well, now I get the Asus Setup , to finalize .
Great work, Thanks again.
Madd Macc
Related
Problem: Was trying to install AOKP 4.0 onto my fully updated TF201.
Wiped data/cache/davlik
installed ROM
installed Google Apps
Device stuck on splash screen.
Figured out the problem was an older version on CWM. I believe it was 5.5.0.4.
Tried to go install latest version of CWM: 5.8.3.4 by using the Fastboot method.
Accidentally selected Wipe Data Option instead of USB.
Lost CWM, all data on internal memory and my entire OS.
Device cannot boot (stays on splash screen). I also try to get back into CWM and it fails. I get bounced back to the Fastboot screen.
What can I do to get this thing back up and running? I will even take stock at this moment just to get the ball rolling again.
Thanks!
kevinb77 said:
Problem: Was trying to install AOKP 4.0 onto my fully updated TF201.
Wiped data/cache/davlik
installed ROM
installed Google Apps
Device stuck on splash screen.
Figured out the problem was an older version on CWM. I believe it was 5.5.0.4.
Tried to go install latest version of CWM: 5.8.3.4 by using the Fastboot method.
Accidentally selected Wipe Data Option instead of USB.
Lost CWM, all data on internal memory and my entire OS.
Device cannot boot (stays on splash screen). I also try to get back into CWM and it fails. I get bounced back to the Fastboot screen.
What can I do to get this thing back up and running? I will even take stock at this moment just to get the ball rolling again.
Thanks!
Click to expand...
Click to collapse
Go here, http://forum.xda-developers.com/showthread.php?t=1615990 read the OP, then go here to download http://teamw.in/project/twrp2/93
Follow the instructions under
Download - Recovery Image / Fastboot Method:
You will back up and running in no time, unfortunately you will need to reinstall the rom....
PS you will need to adb push the rom after you reboot to recovery....
Gage_Hero said:
Go here, http://forum.xda-developers.com/showthread.php?t=1615990 read the OP, then go here to download http://teamw.in/project/twrp2/93
Follow the instructions under
Download - Recovery Image / Fastboot Method:
You will back up and running in no time, unfortunately you will need to reinstall the rom....
PS you will need to adb push the rom after you reboot to recovery....
Click to expand...
Click to collapse
Thanks for the quick response!
OK, I was able to get the stock TF201 drivers onto my Windows 7 PC (since an alternate method had me change them) I am following every step explained in the directions from TeamW.in and am getting this error: "The program can't start because AdbWinAPI.dll is missing from your computer. Try reinstalling the program to fix this problem"
(UPDATE) I was able to find a ADBWinAPI.dll file and I dropped it into the same folder as the twrp.blob and fastboot.exe files. I am not able to access the cmd line, but it does not start the flash, it only lists a bunch of optional cmds to pick from. None of which look useful.
kevinb77 said:
Thanks for the quick response!
OK, I was able to get the stock TF201 drivers onto my Windows 7 PC (since an alternate method had me change them) I am following every step explained in the directions from TeamW.in and am getting this error: "The program can't start because AdbWinAPI.dll is missing from your computer. Try reinstalling the program to fix this problem"
(UPDATE) I was able to find a ADBWinAPI.dll file and I dropped it into the same folder as the twrp.blob and fastboot.exe files. I am not able to access the cmd line, but it does not start the flash, it only lists a bunch of optional cmds to pick from. None of which look useful.
Click to expand...
Click to collapse
Did you ever have any luck with this? I had a JB ROM soft brick my 201 about a year ago. I lost TWRP recovery, OS, pretty much everything. It stays on the splash screen and allows me to get to the fastboot option. I can't get my computer(windows 8) to recognize it at all. Just states it can not recognize USB device. I installed the universal naked driver package along with trying the stock ASUS driver package with no luck.
I put the tablet down and purchased a 701 but now would like to fix the 201 and sell it. If you have any advice I would be very thankful
Yesterday, I unlocked and rooted my tf201, and proceeded to mess around with it. DL'd androwook, wiped everything and installed it. I think my mistake was choosing wipe internal SD when installing (it's where the installer was), and as a result, I was not able to get past the boot animation. I screwed around with it some more and eventually, after trying the Unbrick tool by MasterZen, was stuck at the splash screen with no recovery. Somehow, I had managed to screw up the boot and recovery. Oops.
However, I was able to fix it (boots normally, has recovery, etc..) with some knowledge of fastboot. This is what I did, as a complete amateur, so I probably can't answer specific questions and definitely cannot be held responsible for what you do to your tablet. Make sure you confirm files as non-corrupted with MD5s. This is basically a manual alternative to the Unbricker tool by MasterZen.
I used:
fastboot & adb
TWRP recovery twrp.blob
Ubuntu for Android boot image
[Optional] Stock .28 for unlocked (blob from inside the zip), which you will need to rename (system.blob)
Put these blobs in the folder with your fastboot.
1) get tf201 into fastboot (hold volume down + power on), connect to PC
2) command prompt, "cd [directory fastboot is in]"
3) "fastboot devices" & confirm your device is seen, otherwise go to devmgr and uninstall tf201 drivers and install the Universal Naked Drivers.
4) "fastboot -i 0x0b05 flash recovery twrp.blob" - flashes recovery so you have TWRP. You could try CWM if you'd like.
5) "fastboot -i 0x0b05 flash boot prime-sdlinux.blob" - flashes main kernel.
At this point you should be able to shut down, hold down volume down, and boot with the option of getting into recovery. In recovery, you could use ADB to push a specific rom you'd like and install zip from there. Alternatively, if you want to be able to boot into the system, and have downloaded the stock .28 for unlocked devices and placed the blob inside the folder with fastboot, you can type into command prompt:
6) "fastboot -i 0x0b05 flash system system.blob[or whatever you named it]"
And you should be able to boot up normally.
I've rooted and messed around with android phones before, but honestly I don't know enough about it to give 100% confident answers, and as such cannot be held accountable for what you do to your own device. I figured if someone also had this problem and wasn't able to get the Unbricker tool to work, they could benefit from what I learned. So good luck! Leave questions and feedback, and I'll do my best to answer.
Thanks to blade2k11, who in this post, made me realize that the main kernel was screwed, and that's why I couldn't access the recovery, and that I could fix it with the bootimage from the Ubuntu for Android post.
Thank you sooo much. This brought life back to my tablet!
jmonster141 said:
Thank you sooo much. This brought life back to my tablet!
Click to expand...
Click to collapse
I'm really glad to hear it! I almost thought I had posted this for nothing.
Yea man. I was set on me having a $500 paper weight. You're my tablet's savior. Thanks again
Sent from my myTouch 4g using xda app-developers app
thank you
i wanted to thank you so very much i was at my wits end stayed up for hours trying to fix a simple mistake and you saved the day with this if you where standing here i think i would prob kiss ya cause im that happy that i didn't mess up my only real toy i have
:good: I can't thank you enough, I've been working on mine for a few days now, bad rom download messed it up, then one click fix made things worse, was starting to think hardware issues when nothing was saving or taking, you just saved my tab and made my day than you
Happy to hear it. Have fun with custom roms! I'm on cm10 jellybro, I highly recommend it.
Sent from my Transformer Prime TF201 using xda app-developers app
i just went through the fire. did all this to the teee and still no os. was not able to push the rom i wanted even though my device is seen. the .blob file loaded in second,, yet im stuck on the splash screen with no OS installed. what do i need to do know?? i have got a paper wight on my deck and it was not bought to be so
jyarborough said:
i just went through the fire. did all this to the teee and still no os. was not able to push the rom i wanted even though my device is seen. the .blob file loaded in second,, yet im stuck on the splash screen with no OS installed. what do i need to do know?? i have got a paper wight on my deck and it was not bought to be so
Click to expand...
Click to collapse
Did you download the stock .28 rom and take out the system blob? Have you checked the MD5's to make sure they're downloaded without any corruptions?
jyarborough said:
i just went through the fire. did all this to the teee and still no os. was not able to push the rom i wanted even though my device is seen. the .blob file loaded in second,, yet im stuck on the splash screen with no OS installed. what do i need to do know?? i have got a paper wight on my deck and it was not bought to be so
Click to expand...
Click to collapse
Assuming you have access to adb, put the rom file in your adb folder you have been working from, in windows, right click the rom file, go to properieties, copy the name of the file.
In your adb command box you opened from within your adb folder (pressand hold shift while right clicking select command prompt here) type adb push then right click and paste the name of the rom you copied followed by .zip
This should take about 5 minutes to transfer, go get a coffee or something.
Once done, boot into recovery (twrp)
Under install you should see the rom, install, after the reboot you should be good....
i got stuck in a bootloop trying to unbrick, i can boot into recovery using this but when i try to transfer a rom with adb it gives an error that /sdcard is read-only so i cant put my rom on it. i tried using the stock .28 blob but im still in the same bootloop. not sure what else to
Deleted... whew!
Thanks guys for the help. I'm back up and running
Sent from my Transformer Prime TF201 using Tapatalk 2
Thank you soooo much. I have a working tablet again!
Worked!!
geo.z said:
Yesterday, I unlocked and rooted my tf201, and proceeded to mess around with it. DL'd androwook, wiped everything and installed it. I think my mistake was choosing wipe internal SD when installing (it's where the installer was), and as a result, I was not able to get past the boot animation. I screwed around with it some more and eventually, after trying the Unbrick tool by MasterZen, was stuck at the splash screen with no recovery. Somehow, I had managed to screw up the boot and recovery. Oops.
However, I was able to fix it (boots normally, has recovery, etc..) with some knowledge of fastboot. This is what I did, as a complete amateur, so I probably can't answer specific questions and definitely cannot be held responsible for what you do to your tablet. Make sure you confirm files as non-corrupted with MD5s. This is basically a manual alternative to the Unbricker tool by MasterZen.
I used:
fastboot & adb
TWRP recovery twrp.blob
Ubuntu for Android boot image
[Optional] Stock .28 for unlocked (blob from inside the zip), which you will need to rename (system.blob)
Put these blobs in the folder with your fastboot.
1) get tf201 into fastboot (hold volume down + power on), connect to PC
2) command prompt, "cd [directory fastboot is in]"
3) "fastboot devices" & confirm your device is seen, otherwise go to devmgr and uninstall tf201 drivers and install the Universal Naked Drivers.
4) "fastboot -i 0x0b05 flash recovery twrp.blob" - flashes recovery so you have TWRP. You could try CWM if you'd like.
5) "fastboot -i 0x0b05 flash boot prime-sdlinux.blob" - flashes main kernel.
At this point you should be able to shut down, hold down volume down, and boot with the option of getting into recovery. In recovery, you could use ADB to push a specific rom you'd like and install zip from there. Alternatively, if you want to be able to boot into the system, and have downloaded the stock .28 for unlocked devices and placed the blob inside the folder with fastboot, you can type into command prompt:
6) "fastboot -i 0x0b05 flash system system.blob[or whatever you named it]"
And you should be able to boot up normally.
I've rooted and messed around with android phones before, but honestly I don't know enough about it to give 100% confident answers, and as such cannot be held accountable for what you do to your own device. I figured if someone also had this problem and wasn't able to get the Unbricker tool to work, they could benefit from what I learned. So good luck! Leave questions and feedback, and I'll do my best to answer.
Thanks to blade2k11, who in this post, made me realize that the main kernel was screwed, and that's why I couldn't access the recovery, and that I could fix it with the bootimage from the Ubuntu for Android post.
Click to expand...
Click to collapse
:good::good: Thank you soooo much..My prime is alive !! very much appreciated!!!
Dead link
The link for the ubuntu for android kernel is dead...
Can someone post it back please ?
When I attempt to flash the blobs through fastboot it gives me FAILED unknown error. Anyone help me please? The recovery flashes fine but the boot image gives me the failed error. When i try to access recovery it gives me unrecoverable bootloader error
im trying to flash main kernel i get error that says fastboot.exe has stopped working. Any help?
C:\Users\John St\Desktop\android-sdk-windows\platform-tools>fastboot -i 0x0b05 f
lash recovery twrp.blob
sending 'recovery' (7462 KB)...
OKAY [ 2.037s]
writing 'recovery'...
OKAY [ 1.006s]
finished. total time: 3.045s
C:\Users\John St\Desktop\android-sdk-windows\platform-tools>fastboot -i 0x0b05 f
lash boot prime-sdlinux.blob
error: out of memory
Hello,
I decided tyo go ahead and try to flash CM10 on my phone and when I did it got stuck at the HTC boot screen upon reboot.
I followed all the detailed instructions and this still happened to me. I figured that I could go ahead and apply the stock rom back just like in other cases of a soft-brick. However, this time upon updating it gave me the "Main version is older! error Press Power to reboot" when installing the stock RUU. Seeing as hansoons tool has a fix for that I apply it and it gives me now "Hboot version is older Press Power to reboot." This is now where I am stuck at. My phone is S-ON and I cannot find a way to turn S-OFF without actually booting into the actual OS. Is there a way and a different route I could take to un-brick my phone? Thanks.
glyphs said:
Hello,
I decided tyo go ahead and try to flash CM10 on my phone and when I did it got stuck at the HTC boot screen upon reboot.
I followed all the detailed instructions and this still happened to me. I figured that I could go ahead and apply the stock rom back just like in other cases of a soft-brick. However, this time upon updating it gave me the "Main version is older! error Press Power to reboot" when installing the stock RUU. Seeing as hansoons tool has a fix for that I apply it and it gives me now "Hboot version is older Press Power to reboot." This is now where I am stuck at. My phone is S-ON and I cannot find a way to turn S-OFF without actually booting into the actual OS. Is there a way and a different route I could take to un-brick my phone? Thanks.
Click to expand...
Click to collapse
are you using 43xt recovery? if not you need to use it since your s=on
and to get it to boot, use his tool to put that recovery on. and then reflash the cm10 rom. then it should work.
i believe that when you flashed it the kernel didnt boot.
ziggy46 said:
are you using 43xt recovery? if not you need to use it since your s=on
and to get it to boot, use his tool to put that recovery on. and then reflash the cm10 rom. then it should work.
i believe that when you flashed it the kernel didnt boot.
Click to expand...
Click to collapse
Nice, got it working thanks for your help and speedy reply man I was stuck for a second.
cheers +1
glyphs said:
Nice, got it working thanks for your help and speedy reply man I was stuck for a second.
cheers +1
Click to expand...
Click to collapse
no problem
Use the thanks button
Sent From My Amaze.
glyphs said:
Hello,
I decided tyo go ahead and try to flash CM10 on my phone and when I did it got stuck at the HTC boot screen upon reboot.
I followed all the detailed instructions and this still happened to me. I figured that I could go ahead and apply the stock rom back just like in other cases of a soft-brick. However, this time upon updating it gave me the "Main version is older! error Press Power to reboot" when installing the stock RUU. Seeing as hansoons tool has a fix for that I apply it and it gives me now "Hboot version is older Press Power to reboot." This is now where I am stuck at. My phone is S-ON and I cannot find a way to turn S-OFF without actually booting into the actual OS. Is there a way and a different route I could take to un-brick my phone? Thanks.
Click to expand...
Click to collapse
I had this same problem yesterday and corrected it by doing the following you need to put the phone into fastboot mode hold down power + power down once bootloader comes up click power again plug your USB in go into CMD (If On windows) CD to C drive then cd to the folder you put the files in below and run fastboot flash boot boot.img. The boot.img is going to be the boot.img from the rom you are using. This worked for me yesterday. When installing a rom make sure you clear Dalvik Cache,Cache & Wipe Data Factory Reset as well as formating your SD Card. Then toggle USB and copy the ROM over I would use 4EXT it is the best recovery out there.
Code:
https://dl.dropbox.com/u/102426750/XDA%20Dev/HTC%20Amaze.zip
Put these files in a folder in the root of your C drive. Once you cd into that folder with these files run the commands above
jared407 said:
I had this same problem yesterday and corrected it by doing the following you need to put the phone into fastboot mode hold down power + power down once bootloader comes up click power again plug your USB in go into CMD (If On windows) CD to C drive then cd to the folder you put the files in below and run fastboot flash boot boot.img. The boot.img is going to be the boot.img from the rom you are using. This worked for me yesterday. When installing a rom make sure you clear Dalvik Cache,Cache & Wipe Data Factory Reset as well as formating your SD Card. Then toggle USB and copy the ROM over I would use 4EXT it is the best recovery out there.
Code:
https://dl.dropbox.com/u/102426750/XDA%20Dev/HTC%20Amaze.zip
Put these files in a folder in the root of your C drive. Once you cd into that folder with these files run the commands above
Click to expand...
Click to collapse
Thank you so much, i made an account just to personally thank you for this.
I was stuck on the Bootscreen for cm10 and couldn't figure out what was wrong, but i tried your reply And it worked for me.
Thank you so much sir.
Isn't 4EXT like... the *COUGH*BEST RECOVERY FOR HTC DEVICES*COUGH*
Hi All,
Long time lurker and I appreciate all the work everyone does here. It makes owning an android device a great amount of fun...but as you can see by the title of the thread, a great amount of stress as well :laugh:
My device is unlocked and I've used CWM and recenlty noticed that along one of my flashes TWRP 2.4 installed over CWM. All is well because I was meaning to switch over and try this recovery out. Smooth, fast, I like. But I recently installed CM 10.1 using the october version with the JB bootloader because I did not have it. Everything was nice, but I wanted to update CM 10.1 to a more recent UNOFFICIAL build so I flased the 3/20 version on my device. Everything was smooth but the WiFi dropped all the time so I decided to wait out a more stable "official" version of CM 10.1. Take note that I have(had) TWRP 2.4. Now I wanted to stick with JB 4.2.X so I decided to flash Energy's 3/21 build but this hung up on the ASUS screen... So I decided to reflash the rom but first installing the JB bootloader and partitions zip. Still no luck and while exiting TWRP, I noticed that it stated that my device isn't rooted and would I like to root? So I swiped and did it but it seems that the JB bootloader and partitions zip file erased everything on my device, Roms, GAPPS, SU, backups...gone.
The next thing I did was execute Urkels fresh root and fresh start and that seemed to go through all the steps with no issue. When I went back into recovery I noticed that I now have TWRP 2.2.2.1 with a JB bootloader... so what ever I did downgraded TWRP? Ok... Now I wanted to play it safe and stick to the October version of CM 10.1 with the JB bootloader but while flashing the rom (ext SDCARD) i receive an error. I decided to re-execute Urkels fresh root and fresh start and now all my device does is boot into TWRP 2.2.2.1. I can't use fastboot even with holding the power button and vol down.
At this point I feel lost and defeated, I can't use external SD anymore and I can only mount the system. So I decided to see if ADB works. ADB works great in recovery and am able to send files to the device. I sent a ROM to see if I can install but it fails because it can't mount the cache and this is where I am now. Lost... confused and desperate for help :crying: I'll make sure XDA gets a nice donation if anyone can help me out!
What works -
boot to TWRP 2.2.2.1 (thats all)
ADB in recovery
What doesn't-
No rom installed
No backup
No fastboot
My troubleshooting
Again ANY help is appreciated!
Mike
Would I be able to update TWRP within TWRP using a 2.4.4.0 zip file?
TheYoz said:
Would I be able to update TWRP within TWRP using a 2.4.4.0 zip file?
Click to expand...
Click to collapse
This is happening because you are now on 4.2.1 bootloader with an old TWRP which is not compatible with the new bootloader.
When you say you cannot access fast boot do you mean the usb icon is missing? If you do that is part of the new bootloader. As soon as you get to where the icons are you are automatically in fast boot unless you select one of the icons.
I'm out at the moment but if you reply letting me know that you can get to the icons I will post a file when I get back and some instructions to downgrade you to old bootloader and compatible TWRP.
flumpster said:
This is happening because you are now on 4.2.1 bootloader with an old TWRP which is not compatible with the new bootloader.
When you say you cannot access fast boot do you mean the usb icon is missing? If you do that is part of the new bootloader. As soon as you get to where the icons are you are automatically in fast boot unless you select one of the icons.
I'm out at the moment but if you reply letting me know that you can get to the icons I will post a file when I get back and some instructions to downgrade you to old bootloader and compatible TWRP.
Click to expand...
Click to collapse
I figured my TWRP version might have been the culprit...
When I restart and hold the vol down button it normally would activate fastboot, now it goes directly to TWRP, no icons whatso ever. Before I would get the recovery icon, a usb (I think) and an option to wipe data. I can't get to that screen anymore. Is there a command in adb that will allow me to restart to fastboot from recovery? I myself am at work too so I will test anything I can in 3 - 4 hours. Thanks for taking the time to respond! :good:
So basically I won't be able to put TWRP 2.4.4.0 within my current version of TWRP?
TheYoz said:
I figured my TWRP version might have been the culprit...
When I restart and hold the vol down button it normally would activate fastboot, now it goes directly to TWRP, no icons whatso ever. Before I would get the recovery icon, a usb (I think) and an option to wipe data. I can't get to that screen anymore. Is there a command in adb that will allow me to restart to fastboot from recovery? I myself am at work too so I will test anything I can in 3 - 4 hours. Thanks for taking the time to respond! :good:
So basically I won't be able to put TWRP 2.4.4.0 within my current version of TWRP?
Click to expand...
Click to collapse
The version of TWRP you have will not mount the partitions you need to flash anything. You either need to downgrade the bootloader so that version of TWRP will work or get the version of TWRP back on there that was edited to work with the new 4.2.1 bootloader.
When you installed that partition.zip from energy rom it installed the new bootloader and the compatible twrp the same time. To go back he also has a zip that will restore old bootloader and old twrp. This is what you should have done.
What I am worried about now is the fact that you cannot even get to fastboot from the buttons.
Try adb reboot bootloader.
If that lets you in then download this .. http://flumpster.lolcakes.com/android/blob and place it in your fastboot directory.
Now type.
fastboot -i 0x0B05 flash staging blob
wait for it to fully flash and then type
fastboot -i 0x0B05 reboot
Give it about 20 seconds, if it doesn't restart then you will have to hold the power button down for 10 seconds to force a restart.
When it restarts it should now start to fill the blue line on the Asus screen which will flash the old bootloader and compatible TWRP. If it does this then great, just wait until it has finished and it should put you back into twrp where you will be able to install a rom off your external SD.
If it does not do the blue line then we have bigger probs and I hope you have nvflash backup files.
flumpster said:
The version of TWRP you have will not mount the partitions you need to flash anything. You either need to downgrade the bootloader so that version of TWRP will work or get the version of TWRP back on there that was edited to work with the new 4.2.1 bootloader.
When you installed that partition.zip from energy rom it installed the new bootloader and the compatible twrp the same time. To go back he also has a zip that will restore old bootloader and old twrp. This is what you should have done.
What I am worried about now is the fact that you cannot even get to fastboot from the buttons.
Try adb reboot bootloader.
If that lets you in then download this .. http://flumpster.lolcakes.com/android/blob and place it in your fastboot directory.
Now type.
fastboot -i 0x0B05 flash staging blob
wait for it to fully flash and then type
fastboot -i 0x0B05 reboot
Give it about 20 seconds, if it doesn't restart then you will have to hold the power button down for 10 seconds to force a restart.
When it restarts it should now start to fill the blue line on the Asus screen which will flash the old bootloader and compatible TWRP. If it does this then great, just wait until it has finished and it should put you back into twrp where you will be able to install a rom off your external SD.
If it does not do the blue line then we have bigger probs and I hope you have nvflash backup files.
Click to expand...
Click to collapse
Crossing my fingers... I will try what you mentioned and no, I don't have NVFLASH. Something that I have been meaning to do for a few weeks now too. Thanks for the help I will update when I get a chance to try.
Mikw
TheYoz said:
Crossing my fingers... I will try what you mentioned and no, I don't have NVFLASH. Something that I have been meaning to do for a few weeks now too. Thanks for the help I will update when I get a chance to try.
Mikw
Click to expand...
Click to collapse
You cannot do the nvflash process now. You could only do it while on ICS and there is no way back to ICS without having nvflash backups.
flumpster said:
You cannot do the nvflash process now. You could only do it while on ICS and there is no way back to ICS without having nvflash backups.
Click to expand...
Click to collapse
I am able to adb reboot bootloader, and it brings me to fastboot!
I successfully executed the steps you gave me but I didn't get the android screen with the blue line... it went back to TWRP 2.2.2.1. Can I fastboot the new version of TWRP?
TheYoz said:
I am able to adb reboot bootloader, and it brings me to fastboot!
I successfully executed the steps you gave me but I didn't get the android screen with the blue line... it went back to TWRP 2.2.2.1. Can I fastboot the new version of TWRP?
Click to expand...
Click to collapse
Tried one more time with no success... Please let me know if I have any other options since I can get to fastboot via ADB.
I think the reason I am running into this mess is because I didn't download the JB update from ASUS and move the system.blob file according to Urkel fresh start
TheYoz said:
Tried one more time with no success... Please let me know if I have any other options since I can get to fastboot via ADB.
I think the reason I am running into this mess is because I didn't download the JB update from ASUS and move the system.blob file according to Urkel fresh start
Click to expand...
Click to collapse
I have even tried installing the TWRP.blob (newest JB version) file using this method but still reverts to version 2.2.2.1. I'm stumped
TheYoz said:
I have even tried installing the TWRP.blob (newest JB version) file using this method but still reverts to version 2.2.2.1. I'm stumped
Click to expand...
Click to collapse
I was worried about this. I have seen loads of people with the same problem you have over on the tf300 forums.
They can access fastboot thru adb reboot fastboot and it appears to send the file over ok but then it doesn't work.
When you mentioned you couldn't get to fastboot by holding button combo it looked like the same prob as them.
Have a look at this thread. http://forum.xda-developers.com/showthread.php?t=2179874
flumpster said:
I was worried about this. I have seen loads of people with the same problem you have over on the tf300 forums.
They can access fastboot thru adb reboot fastboot and it appears to send the file over ok but then it doesn't work.
When you mentioned you couldn't get to fastboot by holding button combo it looked like the same prob as them.
Have a look at this thread. http://forum.xda-developers.com/showthread.php?t=2179874
Click to expand...
Click to collapse
So I probably need to send it to ASUS or wait for a solution? That is for the TF300 would I be able to use any steps for that device with mine?
Also,
I purchased this in January 2012 from best buy, any possibility I can go through them to have this issue fixed?
TheYoz said:
I have even tried installing the TWRP.blob (newest JB version) file using this method but still reverts to version 2.2.2.1. I'm stumped
Click to expand...
Click to collapse
Flash the .img not the blob that should fix your issue.
Loco0729 said:
Flash the .img not the blob that should fix your issue.
Click to expand...
Click to collapse
I doubt it will but he can try.
No luck flashing the .img file instead. This is the worst
Flumpster thanks a bunch for all of your help. I ended up sending in the tablet, as expected they had to replace the motherboard.:
They quoted me this origionally:
Parts: $165
Labor: $65
Shipping $10
TOTAL $240!!!
I called and complained until my eyes popped out of my head and they ended up replacing the motherboad and shipped it back to me for $150. Now I think I'm going to sell this thing with the dock and buy a Nexus 10. Again, thanks for your help.
Another note... It will probably be a pain to unlock and root this thing again after the RMA im assuming. No more ASUS.
I'm hoping that some kind soul can help me. I'm about 10 hours into trying to update what was a stock TF201 to KitKat or possibly Lollipop.
First, I unlocked the TF201 using the official unlocking app supplied by ASUS. I didn't attempt to root as I figured I could flash a ROM that was already rooted. I then installed ADB and Fastboot on my Win7 PC. I had a bunch of trouble getting ADB and Fastboot to work reliably, but after trying a number of different things, I eventually got them both working reliably. I am currently using what I believe is the stock ASUS bootloader (<1.00 e> released by "WW_epad-10.4.2.15-20120917" A03). Next, I finally got CM Recovery 5.8.3.4 installed and working. I tried to flash a couple of different CM ROMs (cm-9.0.0-tf201.zip, cm-9.1.0-tf201.zip, and cm-11-20140926-UNOFFICIAL-tf201.zip), all with the same result. They appeared to install correctly, but upon reboot, they would all hang indefinitely at the initial ASUS splashscreen that says "The Device is UnLocked" in the upper left corner. I tried leaving the tablet alone for up to an hour in hopes that it would eventually start, but no luck. I have a feeling that the current bootloader I'm using is incompatible with the various OS images that I tried to install, but I could obviously be wrong. Can anyone tell me what I'm doing wrong or if there's a different bootloader I should be using?
Thanks in advance for your help!
Please ignore this last post. Somehow I got it working. I wish I could share, but I really don't know how or why it started working again.
I had the same problem after flashing cm 11 to my tf201.
(i followed the guide to make my tf201 "unbrikable" by backing up blobs via nvflash.)
i thried a lot of things to get cm running, but then i choosed "wipe data" in the bootloader menue. after that my tf201 doesn't start at all.
i can see the android robot and a blue status bar for 1 second, then screen turns black 1 second, then the android robot comes back and so on. i can't stop this loop. Pulling down the power button simply starts this process new. can't start bootloader o.e.
What have i dun?? -.-
negRomino said:
I had the same problem after flashing cm 11 to my tf201.
(i followed the guide to make my tf201 "unbrikable" by backing up blobs via nvflash.)
i thried a lot of things to get cm running, but then i choosed "wipe data" in the bootloader menue. after that my tf201 doesn't start at all.
i can see the android robot and a blue status bar for 1 second, then screen turns black 1 second, then the android robot comes back and so on. i can't stop this loop. Pulling down the power button simply starts this process new. can't start bootloader o.e.
What have i dun?? -.-
Click to expand...
Click to collapse
Just restore via nvflash ?
Thx Josh
lj50036 said:
Just restore via nvflash ?
Thx Josh
Click to expand...
Click to collapse
After a long time of hating myself for bricking the tf201 i am about to give a new try to reset via nvflash.
I read the tutorial (http://forum.xda-developers.com/showthread.php?t=1927818) but the attached files for unblobd stock ROMs or the semi-automated complete recovery are not online anymore. anyone who can help me out with the files?
edit: APX driver works.
negRomino said:
After a long time of hating myself for bricking the tf201 i am about to give a new try to reset via nvflash.
I read the tutorial (http://forum.xda-developers.com/showthread.php?t=1927818) but the attached files for unblobd stock ROMs or the semi-automated complete recovery are not online anymore. anyone who can help me out with the files?
edit: APX driver works.
Click to expand...
Click to collapse
If you dont have your blob.bin its pointless..
This file is from your device (needed backed up before a brick) and only for your device......
Thx Josh
do not use CM Recovery ......... USE TWRP
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
YOU HAVE TO FLASH BOOTLOADER ON THE LINK
https://www.androidfilehost.com/?fid=23060877490002899
Check MD5 FEEA44BC7370116E1807DC943E2700B5
unzipit and copy "blob" in adb/fastbooy folder
fastboot flash boot blob
than reboot
YOU HAVE TO FLASH RECOVERY ON THE LINK
https://www.androidfilehost.com/?fid=95916177934539154
Check MD5 118eb4f530c99922126d11f71c981429
unzipit and copy "boot.blob" in adb/fastbooy folder
fastboot erase recovery
fastboot flash recovery boot.blob
reboot
Go to twrp/wipe/format data then type yes
It takes about 70 minutes to format
Make sure that your battery is full
Do Not interrupt format(if you do, it will brick)
After it's done go to Wipe//Advanced Wipe//Select Data
Tap “Repair or Change File System”//”Change File System//F2FS
Swipe to Change
Wipe dalvik cache, system, cache, data, internal storage
Flash KatKiss-5.1.1_TF201_030.zip from microsd card
Flash Supersu.zip
Flash Gapps.zip
Reboot