CM10 bricked phone - HTC Amaze 4G

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*

Related

Cant open bootloader

When i open bootloader (Holding Power + Volume-down), it keeps pushing a 'update' whether i click yes or no, it still forces me to reboot which in the end leaves me stuck on the HTC white screen.
Any help would be welcomed
diddykonga said:
When i open bootloader (Holding Power + Volume-down), it keeps pushing a 'update' whether i click yes or no, it still forces me to reboot which in the end leaves me stuck on the HTC white screen.
Any help would be welcomed
Click to expand...
Click to collapse
1. Easiest is to plug your phone into a computer while its off and adb works when it's off. Deleted the update.zip or ph98img.zip on your sdcard.
option 2.
take out sdcard. boot into hboot. plug phone into a charger usb or wall. pull battery out and put in sdcard, put battery back in and enter recovery.
Thanks for that, ended up doing the second option
Now, was wandering if i could get some assistance with flashing to EclipticRez.
First, while in TWRP 2.3.3 i got to wipe, run Factory reset, then cache, then dalvik cache.
After having done that, i go to install and find a folder i created called Roms which holds the EclipticRez.zip, and choose it. I proceed through the options, choosing Lunar for the kernal, and choosing S-On for the safety mode. Let it run through a rather super quick installation then it asks me if i want to reboot i click yes, and am still presented with an every lasting HTC White Screen.
Would you happen to know what im doing wrong? Thanks
diddykonga said:
Thanks for that, ended up doing the second option
Now, was wandering if i could get some assistance with flashing to EclipticRez.
First, while in TWRP 2.3.3 i got to wipe, run Factory reset, then cache, then dalvik cache.
After having done that, i go to install and find a folder i created called Roms which holds the EclipticRez.zip, and choose it. I proceed through the options, choosing Lunar for the kernal, and choosing S-On for the safety mode. Let it run through a rather super quick installation then it asks me if i want to reboot i click yes, and am still presented with an every lasting HTC White Screen.
Would you happen to know what im doing wrong? Thanks
Click to expand...
Click to collapse
You need to flash the boot IMG if you are s on.
Sent from my ADR6425LVW using Tapatalk 2
Do i do that after i have installed/flashed the ROM?
and where do i need to be to do it? (Recovery, HBoot, etc..)
Thank you for your help
diddykonga said:
Do i do that after i have installed/flashed the ROM?
and where do i need to be to do it? (Recovery, HBoot, etc..)
Thank you for your help
Click to expand...
Click to collapse
Flashed in fastboot. "fastboot flash boot boot.img" You can flash the boot.img after or before you install the rom.
Well i tried using the hansoon tool, and just using the command prompt, but im still getting stuck on the white HTC screen
Any help?
Tried relocking my hboot, but now for some reason my adb wont ever detect my phone.
Can anyone help? like a link to the drivers or something?
I'm s-on and just flashed Ecliptic myself.
I selected Lunar kernel and my phone didn't do the kernel install itself but it put the PH98IMG file on my sd card. I can't remember if after the ROM flashing it left me at the bootloader or not, but you should be able to get to it.
Perhaps you thought that was the OTA and wanted to not take it? If it appeared immediately after flashing the ROM it's the kernel and you need to let it flash in order to be able to completely boot up the phone.
At this point you need to unlock the bootloader again. Then disconnect the phone from pc, power down, pull battery and boot into bootloader by holding vol down + power until the bootloader screen shows up. It should find the PH98IMG file and ask you if you want to update, say yes.
If you pulled the "stockboot.img" file from the ROM it may not be working since you selected the Lunar kernel during the ROM flash setup.
If you've already deleted the PH98IMG file then just pull the lunarboot.img and flash that in fastboot, it should work. You can just do it right after unlocking the phone while it's still connected to your pc.
fastboot flash boot lunarboot.img

[Q] Can't access recovery

I am running santod's rooted Stock ICS rom, which has been running excellent, love it very much. Today I went to do a backup in recovery and noticedit will not boot into recovery. I am running the 4EXT recovery as suggested in the rom forum post. Nothing I do seems to be able to boot the recovery. I can't reboot into recovery from the 4EXT app. I boot the phone with the volume down key, and try to enter recovery from there. Still nothing. I get my initial boot logo, then screen goes black, then boot logo again and it proceeds to boot up normally. I have tried re-flashing the recovery from the 4EXT app, I even tried rom manages and using the latest clockwork mod recovery. Nothing gets me into recovery. Also have noticed my phone will not stay powered off when on the charger. If I power off, plug the charger in, after a few seconds phone powers itself on. Could it be related?
I followed the rom installation instructions to the letter.
Installed the 4EXT recovery.
Flashed the ICS radios.
Wiped all my partitions except my SD card.
Flashed rom and have enjoyed for weeks now.
Only other info I know to provide is I installed the debloated/deodexed rom
Did not flash the kernel as I didn't experience boot loops.
Thanks in advance for any assistance folks!
JM1084 said:
I am running santod's rooted Stock ICS rom, which has been running excellent, love it very much. Today I went to do a backup in recovery and noticedit will not boot into recovery. I am running the 4EXT recovery as suggested in the rom forum post. Nothing I do seems to be able to boot the recovery. I can't reboot into recovery from the 4EXT app. I boot the phone with the volume down key, and try to enter recovery from there. Still nothing. I get my initial boot logo, then screen goes black, then boot logo again and it proceeds to boot up normally. I have tried re-flashing the recovery from the 4EXT app, I even tried rom manages and using the latest clockwork mod recovery. Nothing gets me into recovery. Also have noticed my phone will not stay powered off when on the charger. If I power off, plug the charger in, after a few seconds phone powers itself on. Could it be related?
I followed the rom installation instructions to the letter.
Installed the 4EXT recovery.
Flashed the ICS radios.
Wiped all my partitions except my SD card.
Flashed rom and have enjoyed for weeks now.
Only other info I know to provide is I installed the debloated/deodexed rom
Did not flash the kernel as I didn't experience boot loops.
Thanks in advance for any assistance folks!
Click to expand...
Click to collapse
Did you rename or remove the Radio file from the sd card as suggested in the OP of the rom thread?
It will not let you get into Recovery if there is a PG05IMG.zip present on the root of the sd card.
If that's not the case, reflash 4ext from within the Recovery control app.
Just installing the app doesn't install the Recovery.
You must also install the actual Recovery from within the app if you haven't.
santod040 said:
Did you rename or remove the Radio file from the sd card as suggested in the OP of the rom thread?
It will not let you get into Recovery if there is a PG05IMG.zip present on the root of the sd card.
If that's not the case, reflash 4ext from within the Recovery control app.
Just installing the app doesn't install the Recovery.
You must also install the actual Recovery from within the app if you haven't.
Click to expand...
Click to collapse
Yeah, there is no PG05IMG.zip in the sd card root. Also I have tried reinstalling the recovery from the 4EXT recovery control app.
Current verson of recovery installed is 4EXT Recovery Touch v1.0.0.5 RC8.
Tried reflashing that, and also the RC9 test build that is out right now.
Still no go on getting into the recovery.
Thanks.
When you do the volume down and power option with the device off, you need to first press the volume down and then while holding that, then press and also hold the power button, you should feel it vibrate, keeeeeep holding them down, do not let go.
Wait until you see what should be a white hboot screen with menu options, then you may let go.
If you hold power first or don't hold them both down long enough, it will just try to boot normally.
Not that that would explain why you can't get there from within Recovery Control app.
What is your hboot version and how did you root your device?
santod040 said:
When you do the volume down and power option with the device off, you need to first press the volume down and then while holding that, then press and also hold the power button, you should feel it vibrate, keeeeeep holding them down, do not let go.
Wait until you see what should be a white hboot screen with menu options, then you may let go.
If you hold power first or don't hold them both down long enough, it will just try to boot normally.
Not that that would explain why you can't get there from within Recovery Control app.
What is your hboot version and how did you root your device?
Click to expand...
Click to collapse
It was rooted using the Revolutionary method, did it a year or more ago.
Hboot version is 6.04.1002
When I try to go to recovery from the hboot screen it does the same, vibrate, white HTC screen, black screen, vibrate, white HTC screen, normal boot. No recovery.
Is there any other method of getting into recovery or re-flashing the recovery?
JM1084 said:
It was rooted using the Revolutionary method, did it a year or more ago.
Hboot version is 6.04.1002
When I try to go to recovery from the hboot screen it does the same, vibrate, white HTC screen, black screen, vibrate, white HTC screen, normal boot. No recovery.
Is there any other method of getting into recovery or re-flashing the recovery?
Click to expand...
Click to collapse
Yes, you can flash Recovery images from hboot, just like you flash a radio.
With it named PG05IMG.zip and placed on the root of the sd card.
HERE is one you can try.
If that doesn't work, I may have something you can try from fastboot to clear the Recovery cache, and maybe that will resolve the issue.
I have only seen one other user have this occur and his device simply ended up getting replaced because he wasn't able to mount to usb for doing fastboot commands either.
santod040 said:
Yes, you can flash Recovery images from hboot, just like you flash a radio.
With it named PG05IMG.zip and placed on the root of the sd card.
HERE is one you can try.
If that doesn't work, I may have something you can try from fastboot to clear the Recovery cache, and maybe that will resolve the issue.
I have only seen one other user have this occur and his device simply ended up getting replaced because he wasn't able to mount to usb for doing fastboot commands either.
Click to expand...
Click to collapse
Still no go flashing that recovery in hboot. What is the process of clearing recovery cache?
On a side note, in talking to my father, his bolt seems to have the same issue. We both were rooted with the same method, and I believe we have the same hboot version. Only difference is he flashed the rom using clockwork recovery.
Edit: I confirmed his hboot is 6.04.1002. same as mine
JM1084 said:
Still no go flashing that recovery in hboot. What is the process of clearing recovery cache?
On a side note, in talking to my father, his bolt seems to have the same issue. We both were rooted with the same method, and I believe we have the same hboot version. Only difference is he flashed the rom using clockwork recovery.
Click to expand...
Click to collapse
Well, I've got several Bolts here, and a couple of them have that same hboot and were used to test the stock roms with.
So I do not think it's a root or hboot issue, but I do not know what the issue would be other then corrupt Recovery cache.
To try and fix it by clearing the cache, do the following:
Download the erasecache.zip file from www.4ext.net/erasecache.zip
First boot your device into bootloader while connected via usb.
If it reads "fastboot usb" you are already in fastboot mode.
If it reads "hboot usb" then select "fastboot" in the bootloader menu.
Extract the file anywhere on your computer, and then start the file erase_cache.cmd with
elevated rights (right click erase_cache.cmd and select to run as administrator)
Watch for any error messages and tell me the results please.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If the above method fails, try this way:
This requires a little adb or command line knowledge(not much) and the appropriate files on your system.
Please boot into bootloader -> fastboot mode
and then issue the following fastboot command:
fastboot erase cache
afterwards boot recovery from the bootloader menu and enter the
wipe menu and format cache
santod040 said:
Well, I've got several Bolts here, and a couple of them have that same hboot and were used to test the stock roms with.
So I do not think it's a root or hboot issue, but I do not know what the issue would be other then corrupt Recovery cache.
To try and fix it by clearing the cache, do the following:
Download the erasecache.zip file from www.4ext.net/erasecache.zip
First boot your device into bootloader while connected via usb.
If it reads "fastboot usb" you are already in fastboot mode.
If it reads "hboot usb" then select "fastboot" in the bootloader menu.
Extract the file anywhere on your computer, and then start the file erase_cache.cmd with
elevated rights (right click erase_cache.cmd and select to run as administrator)
Watch for any error messages and tell me the results please.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If the above method fails, try this way:
This requires a little adb or command line knowledge(not much) and the appropriate files on your system.
Please boot into bootloader -> fastboot mode
and then issue the following fastboot command:
fastboot erase cache
afterwards boot recovery from the bootloader menu and enter the
wipe menu and format cache
Click to expand...
Click to collapse
Alrighty, I will give that a shot. I am at work right now and am about to head out of town so I will be unable to try it until sunday. I'll post the results here asap. Thanks again!
Same ROM, same problem,I even tried flashing a different recovery. Rooted using really old one click method a month after thunderbolt release.
Sent from my HTC Thunderbolt
zomgalama said:
Same ROM, same problem,I even tried flashing a different recovery. Rooted using really old one click method a month after thunderbolt release.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
What is your h boot version?
Sent from my ADR6400L using Tapatalk 2
santod040 said:
Well, I've got several Bolts here, and a couple of them have that same hboot and were used to test the stock roms with.
So I do not think it's a root or hboot issue, but I do not know what the issue would be other then corrupt Recovery cache.
To try and fix it by clearing the cache, do the following:
Download the erasecache.zip file from www.4ext.net/erasecache.zip
First boot your device into bootloader while connected via usb.
If it reads "fastboot usb" you are already in fastboot mode.
If it reads "hboot usb" then select "fastboot" in the bootloader menu.
Extract the file anywhere on your computer, and then start the file erase_cache.cmd with
elevated rights (right click erase_cache.cmd and select to run as administrator)
Watch for any error messages and tell me the results please.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If the above method fails, try this way:
This requires a little adb or command line knowledge(not much) and the appropriate files on your system.
Please boot into bootloader -> fastboot mode
and then issue the following fastboot command:
fastboot erase cache
afterwards boot recovery from the bootloader menu and enter the
wipe menu and format cache
Click to expand...
Click to collapse
No Go, my tbolt will not mount in Win7, it just says the device has malfunctioned. Rebooting into the bootloader with USB in will not show anything in Windows, even in fastboot. It makes the device connection sound but no devices show up. Running the CMD file in the zip you linked does nothing, I'm at 10 minutes now where it just says "Waiting for device". Is my device just done for?
JM1084 said:
It was rooted using the Revolutionary method, did it a year or more ago.
Hboot version is 6.04.1002
When I try to go to recovery from the hboot screen it does the same, vibrate, white HTC screen, black screen, vibrate, white HTC screen, normal boot. No recovery.
Is there any other method of getting into recovery or re-flashing the recovery?
Click to expand...
Click to collapse
I think I had a similar problem once. Boot back into your hboot screen. Then select "factory reset". If you have a 3rd party recovery installed, like it sound like you have (4ext, right?), it will boot you to recovery so you can administer the reset yourself (it doesn't actually wipe anything, just brings you to your recovery's home screen).
Let me know how it goes.
coltspackers said:
I think I had a similar problem once. Boot back into your hboot screen. Then select "factory reset". If you have a 3rd party recovery installed, like it sound like you have (4ext, right?), it will boot you to recovery so you can administer the reset yourself (it doesn't actually wipe anything, just brings you to your recovery's home screen).
Let me know how it goes.
Click to expand...
Click to collapse
Thanks for the info, but this didn't work either. I'm also on 6.04.1002 and rooted mine a week after the T-Bolt shipped manually via adb.
This happened about a month ago also, and I thought it was ext4 but managed to get an older TWRP recovery to work after working on it for about a day and a half without a working phone. At least I have a working phone at this point.
Same ROM, same recovery (4ext), same problem. Rooted by adb a month after launch, hboot 6.04.1002
allo_87 said:
Same ROM, same recovery (4ext), same problem. Rooted by adb a month after launch, hboot 6.04.1002
Click to expand...
Click to collapse
Might be wise to bring it to Max's attention.
He makes the Recovery that is disappearing and may have suggestions or ideas on how to prevent this in the future.
I have flashed every rom I have ever posted at least once.
Most of them, may times and have yet to run into this issue.
I have had Recovery become corrupted once or twice quite some time back and not be able to get into it.
But it was easily fixed by reinstalling/reflashing a recovery.
I guess what I'm saying, is if there is a common issue occuring on our device with some ICS users and his Recovery, he should know about it.
Here's how to contact him: LINK
Hopefully he can help or look into the root of the issue, since I know he has had a few users with this same issue in the past.
santod040 said:
Might be wise to bring it to Max's attention.
He makes the Recovery that is disappearing and may have suggestions or ideas on how to prevent this in the future.
I have flashed every rom I have ever posted at least once.
Most of them, may times and have yet to run into this issue.
I have had Recovery become corrupted once or twice quite some time back and not be able to get into it.
But it was easily fixed by reinstalling/reflashing a recovery.
I guess what I'm saying, is if there is a common issue occuring on our device with some ICS users and his Recovery, he should know about it.
Here's how to contact him: LINK
Hopefully he can help or look into the root of the issue, since I know he has had a few users with this same issue in the past.
Click to expand...
Click to collapse
Excellent advice, thanks man.
Sent from my ADR6400L using Tapatalk 2
My thunderbolt's recovery spin mysteriously started working again yesterday, not sure why.
Doesn't matter though since I switched carriers now:/
Sent from my Sprint LG Optimus G
Still nothing for me. Worse yet is the fact that I can't adb because my usb has not worked properly since "the soup incident"
Sent from my ADR6400L using Tapatalk 2
santod040 said:
Might be wise to bring it to Max's attention.
He makes the Recovery that is disappearing and may have suggestions or ideas on how to prevent this in the future.
I have flashed every rom I have ever posted at least once.
Most of them, may times and have yet to run into this issue.
I have had Recovery become corrupted once or twice quite some time back and not be able to get into it.
But it was easily fixed by reinstalling/reflashing a recovery.
I guess what I'm saying, is if there is a common issue occuring on our device with some ICS users and his Recovery, he should know about it.
Here's how to contact him: LINK
Hopefully he can help or look into the root of the issue, since I know he has had a few users with this same issue in the past.
Click to expand...
Click to collapse
After going over the issue with Max and trying several fixes he suggested (he even made me an app that would format my cache), it seems I either need to obtain an RUU and flash the stock software/recovery back on and re-root or try flashing an updated hboot that already has s-off. The thinking is that it is my hboot that is causing the issue. Does anyone know what files I need? I have a couple of things to try at home to see if I can get my usb working again, if not, anything I do will have to be a flashable zip from the bootloader. Thanks!

[Q] Possible bricked device... Any help greatly appreciated.

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.

[Q] Installing TWRP over CWM

Hello,
I 'm new to the android community and i'm so glad to be among you. So i rooted my HTC Desire X (with ICS) a couple of days ago using CWM recovery and now I want to install this DEODEXED stock ROM: http://forum.xda-developers.com/showthread.php?p=40682127
(Note: I have CID:T-MOB101 and HBOOT 1.24.0000).
While rooting the phone i installed CWM recovery while the guide on the link demands to install TWRP. How can i install TWRP over CWM? Because while doing the steps of the guide i got stuck in the 3rd step(Command Prompt says:sending "recovery" but the process never finishes)...
Forgive me if i have forgotten any info of my phone, just let me know!
Thanks in advance,
Tassos
Download this tool http://forum.xda-developers.com/showthread.php?t=1943822
Its much easier.
Important! make a nandroid backup first before flash anything,
ειναι σημαντικο να εχεις ενα!!
Tried with the way above, didn't worked...
I tried this and it didnt worked, i also tried manually through terminal with no luck. As i said above the process gets stuck when the terminal says "sending recovery" and the bar on the screen of my phone doesn't fill. I 've been reading that there are some other users of HTC DX that have the same problem with me, that is they can't flash TWRP and finally they install CWM. Has this something to do with the details of my phone(CID, hboot, etc.)?
So can anyone help me on how to flash TWRP on my phone with CWM on it.?
tassos_chry said:
How can i install TWRP over CWM?
Click to expand...
Click to collapse
Try Clearing the Dalvik Cache
Download this toolkit ,extract it on desktop
replace its recovery.img with this RECOVERY
boot into bootloader
Connect to PC
run 'Install Recovery.img.bat'
AND U"RE DONE :laugh:
if this does not work then try factory format
AND REMEMBER MAKE AN NAND :good: BEFORE DOING THIS
Thanks
Ok thanks, i'll try these methods and post feedback.
Thanks again
Update:
First method didn't work...
Just tried factory reset!
Update 2:
I factory resetted the phone through CWM and went to repeat the process. Still NO luck...
tassos_chry said:
Ok thanks, i'll try these methods and post feedback.
Thanks again
Update:
First method didn't work...
Just tried factory reset!
Update 2:
I factory resetted the phone through CWM and went to repeat the process. Still NO luck...
Click to expand...
Click to collapse
1. Start your PC
2. Go in folder containing fastboot.exe and related binaries.
3. Download the recovery.img for (ICS or JB) as required.
4. Type this command in cmd.exe
fastboot.exe flash recovery recovery.img
5. Press power button so that phone goes from fasboot to hboot mode. Then press VOLDOWN and then POWER to boot into recovery.
Its a simple enough process, just try to be calm and do it one step at a time.
Regards
Yasir
Sorry for not posting this earlier, but i just saw that when i boot into hboot the following message comes up:
"SD Checking
Loading PM66DIAG.zip
No Image
Loading PM66DIAG.nbh
No Image
Loading PM66IMG.zip
No Image
Loading PM66IMG.nbh
No Image or Wrong Image"
Then it disappears immediately and the normal screen of hboot comes up...
Maybe this has something to do, with me not being able to flash TWRP...
Any help?
tassos_chry said:
Sorry for not posting this earlier, but i just saw that when i boot into hboot the following message comes up:
"SD Checking
Loading PM66DIAG.zip
No Image
Loading PM66DIAG.nbh
No Image
Loading PM66IMG.zip
No Image
Loading PM66IMG.nbh
No Image or Wrong Image"
Then it disappears immediately and the normal screen of hboot comes up...
Maybe this has something to do, with me not being able to flash TWRP...
Any help?
Click to expand...
Click to collapse
I said to you thru PM... check whether you are at the correct fastboot usb screen. This SD checking and blablabla is hboot screen, fastboot flash won't work on hboot screen, only on fastboot/bootloader screen.
After this SD checking and blablabla screen, press power once to go to bootloader/fastbboot screen
ckpv5 said:
I said to you thru PM... check whether you are at the correct fastboot usb screen. This SD checking and blablabla is hboot screen, fastboot flash won't work on hboot screen, only on fastboot/bootloader screen.
After this SD checking and blablabla screen, press power once to go to bootloader/fastbboot screen
Click to expand...
Click to collapse
All the times I've tried to flash a recovery i 'm on the fastboot/bootloader screen, which says Fastboot USB. I tried with neXus PRIME's way too but it didn't work out. I think i'm not doing anything wrong and don't know why it doesn't work...
Check/change your cable and also change the usb port (use usb2.0 instead of usb3.0) or try on other PC
BTW.. you also can use CWM to flash ROM... the only reason to use TWRP is it has a reboot option in recovery where you can select reboot to bootloader. So using CWM, you must manually put your device to bootloader after installing ROM.
But I suggest, you stick with your current ROM. That JB ROM is only for people who want to test how the JB ROM is. Most of them revert back to ICS
ckpv5 said:
Check/change your cable and also change the usb port (use usb2.0 instead of usb3.0) or try on other PC
BTW.. you also can use CWM to flash ROM... the only reason to use TWRP is it has a reboot option in recovery where you can select reboot to bootloader. So using CWM, you must manually put your device to bootloader after installing ROM.
But I suggest, you stick with your current ROM. That JB ROM is only for people who want to test how the JB ROM is. Most of them revert back to ICS
Click to expand...
Click to collapse
FML. It was the USB port that caused the mess(I was using USB 3). Just flashed TWRP using USB 2
Thank you man. I was so dissapointed, thinking that something is wrong with my phone!!
Thank you very much!:laugh:
Update:Any info when the official update for JB from HTC comes out for all of us who don't have it yet?

Tried to root my phone, can't boot anymore, how do I get it stock?? [Very worried]

So I tried to flash a rom and hit some problems, now when I try to restart my phone it gets stuck on the "verizon 4g lte" screen and wont load past there. When I open bootloader there are 3 warnings at the very top:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
How can I get my phone back to stock? I need this IMMEDIATLY if possible!!
Also make it as simple as possible, I'm new to roms and roots and flashing.
BabyPenguin said:
So I tried to flash a rom and hit some problems, now when I try to restart my phone it gets stuck on the "verizon 4g lte" screen and wont load past there. When I open bootloader there are 3 warnings at the very top:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
How can I get my phone back to stock? I need this IMMEDIATLY if possible!!
Also make it as simple as possible, I'm new to roms and roots and flashing.
Click to expand...
Click to collapse
You need to unlock the boot loader again. Flash a recovery img again.
Sent from my Rezound using xda app-developers app
tburns said:
You need to unlock the boot loader again. Flash a recovery img again.
Sent from my Rezound using xda app-developers app
Click to expand...
Click to collapse
What is a recovery img?
BabyPenguin said:
What is a recovery img?
Click to expand...
Click to collapse
as it was stated, you need to unlock your bootloader again. A recovery image is a image that we use to flash and wipe roms and the phone. Amon RA, TWRP and CW are the ones we can use for our phone. I personally use TWRP and Amon RA depending on my mood. You can find them here
http://forum.xda-developers.com/showthread.php?t=1425091
Towards the bottom of the list you will see recovery. You will need to flash one of those in order to flash a custom rom.
Also make sure to read the tutorials towards the bottom. before you start messing with your phone you should be familiar with everything. If you do something wrong and brick your phone, its hard to recover from if at all and you would have an expensive paper weight
clmowers said:
as it was stated, you need to unlock your bootloader again. A recovery image is a image that we use to flash and wipe roms and the phone. Amon RA, TWRP and CW are the ones we can use for our phone. I personally use TWRP and Amon RA depending on my mood. You can find them here
http://forum.xda-developers.com/showthread.php?t=1425091
Towards the bottom of the list you will see recovery. You will need to flash one of those in order to flash a custom rom.
Also make sure to read the tutorials towards the bottom. before you start messing with your phone you should be familiar with everything. If you do something wrong and brick your phone, its hard to recover from if at all and you would have an expensive paper weight
Click to expand...
Click to collapse
Alright, so I downloaded both the files here: http://forum.xda-developers.com/showthread.php?t=1339679
Two problems. First, I have no way of accessing my sd card now because it wont let me through my computer
Second, I don't know how to use these files and after reading the thread it still didn't help.
EDIT: After unlocking the only two notices on my hboot is
TAMPERED
and
UNLOCKED
EDIT2: I found my SD card adapter.
BabyPenguin said:
Alright, so I downloaded both the files here: http://forum.xda-developers.com/showthread.php?t=1339679
Two problems. First, I have no way of accessing my sd card now because it wont let me through my computer
Second, I don't know how to use these files and after reading the thread it still didn't help.
EDIT: After unlocking the only two notices on my hboot is
TAMPERED
and
UNLOCKED
EDIT2: I found my SD card adapter.
Click to expand...
Click to collapse
1. you need to download fastboot if you have not already. You can find that in the android sdk
2.) once fastboot is downloaded boot your phone into bootloader and select the fastboot option and plug your phone into your computer
3.) place the recovery image in the same directory as fastboot and use the command prompt (windows key +r then type cmd and hit enter)
4.) change directory to where fastboot is and run this command
fastboot flash recovery recovery.img
where recovery.img is the name of the recovery file that you downloaded
clmowers said:
1. you need to download fastboot if you have not already. You can find that in the android sdk
2.) once fastboot is downloaded boot your phone into bootloader and select the fastboot option and plug your phone into your computer
3.) place the recovery image in the same directory as fastboot and use the command prompt (windows key +r then type cmd and hit enter)
4.) change directory to where fastboot is and run this command
fastboot flash recovery recovery.img
where recovery.img is the name of the recovery file that you downloaded
Click to expand...
Click to collapse
Done, now what? Thanks for the help by the way!
BabyPenguin said:
Done, now what? Thanks for the help by the way!
Click to expand...
Click to collapse
yeah no problem.
If you go back into the bootloader and select recovery, this will bring you into the Amon Ra.
Download a rom from the forums, I personally like Neo's Roms, Infection 2.8.1 is a good choice. But download any rom and put it on your SD card.
1.) select USB-MS toggle and then select on of the options
2.) copy downloaded rom to mounted sdcard
3.) once copied, hit the power button to unmount and then return to the main menu
4.)select wipe from the main menu and then do each one of these 3 times
Wipe All data/factory reset
Wipe /data
Wipe /cache
Wipe /Dalvik-cache
Wipe /system
then go back to main menu and then select Fash zip menu and select where you placed your rom and then flash...once its flash go back to main menu and select Developers menu and selet reboot bootloader
open the rom using a zip program and pull the boot.img from the rom and place it in your fastboot directory
once you are in the bootloader it should go to fastboot usb automatically and then run these commands
fastboot flash boot boot.img
fastboot reboot
it should reboot and load your rom
clmowers said:
yeah no problem.
If you go back into the bootloader and select recovery, this will bring you into the Amon Ra.
Download a rom from the forums, I personally like Neo's Roms, Infection 2.8.1 is a good choice. But download any rom and put it on your SD card.
1.) select USB-MS toggle and then select on of the options
2.) copy downloaded rom to mounted sdcard
3.) once copied, hit the power button to unmount and then return to the main menu
4.)select wipe from the main menu and then do each one of these 3 times
Wipe All data/factory reset
Wipe /data
Wipe /cache
Wipe /Dalvik-cache
Wipe /system
then go back to main menu and then select Fash zip menu and select where you placed your rom and then flash...once its flash go back to main menu and select Developers menu and selet reboot bootloader
open the rom using a zip program and pull the boot.img from the rom and place it in your fastboot directory
once you are in the bootloader it should go to fastboot usb automatically and then run these commands
fastboot flash boot boot.img
fastboot reboot
it should reboot and load your rom
Click to expand...
Click to collapse
I have no idea why this isn't working
http://gyazo.com/2627f9963c95e7dc9a03cb118f139aac.png
I did your steps in order, but my phone has been stuck on rebooting... for over 15 minutes as you can see from the CMD. On my phone I just see the booting logo spinning.
I used this rom because I want jellybean: http://forum.xda-developers.com/showthread.php?t=2113140
Any ideas?
Also, what do I do with the MD5? I didn't use it.
BabyPenguin said:
I have no idea why this isn't working
http://gyazo.com/2627f9963c95e7dc9a03cb118f139aac.png
I did your steps in order, but my phone has been stuck on rebooting... for over 15 minutes as you can see from the CMD. On my phone I just see the booting logo spinning.
I used this rom because I want jellybean: http://forum.xda-developers.com/showthread.php?t=2113140
Any ideas?
Click to expand...
Click to collapse
the reboot step isnt 100% needed, its more for ease of use...just pull the battery and power on
Also did you flash the boot.img file?
---------- Post added at 07:22 AM ---------- Previous post was at 07:18 AM ----------
BabyPenguin said:
I have no idea why this isn't working
http://gyazo.com/2627f9963c95e7dc9a03cb118f139aac.png
I did your steps in order, but my phone has been stuck on rebooting... for over 15 minutes as you can see from the CMD. On my phone I just see the booting logo spinning.
I used this rom because I want jellybean: http://forum.xda-developers.com/showthread.php?t=2113140
Any ideas?
Also, what do I do with the MD5? I didn't use it.
Click to expand...
Click to collapse
Dont worry to much about the MD5,I havent used one if forever. Its basically just a security check to make sure that the file you downloaded didnt get corrupt. But with modern technology and internet, its less likely to mess up while downloading. Still possible, but not likely
clmowers said:
the reboot step isnt 100% needed, its more for ease of use...just pull the battery and power on
Also did you flash the boot.img file?
Click to expand...
Click to collapse
It's still just sitting on the boot screen.
If you didn't see my edit, there is an md5 file I can download, but I didn't use it because I don't know what to do with it.
BabyPenguin said:
It's still just sitting on the boot screen.
If you didn't see my edit, there is an md5 file I can download, but I didn't use it because I don't know what to do with it.
Click to expand...
Click to collapse
Just sent you a PM buds
maybe you can help me out quick im stuck on the lte logo also my bootloader is unlocked but when i open it to try and fix my problem its says i need an update. so i select update, it finishes, and makes me reboot which gets me stuck again.
i cant pick anything in the bootloader menu until i select yes or no for this update but both options require me to reboot after choosing then im back to stuck.
xcapeartist said:
maybe you can help me out quick im stuck on the lte logo also my bootloader is unlocked but when i open it to try and fix my problem its says i need an update. so i select update, it finishes, and makes me reboot which gets me stuck again.
i cant pick anything in the bootloader menu until i select yes or no for this update but both options require me to reboot after choosing then im back to stuck.
Click to expand...
Click to collapse
It sounds like you have a ph98img file on your sdcard. Remove the sdcard and Mount it in a PC and remove it. Then remount in the phone. Should allow to get into recovery and fastboot then
Sent from my ANDROFLY REZOUND using xda app-developers app
clmowers said:
It sounds like you have a ph98img file on your sdcard. Remove the sdcard and Mount it in a PC and remove it. Then remount in the phone. Should allow to get into recovery and fastboot then
Sent from my ANDROFLY REZOUND using xda app-developers app
Click to expand...
Click to collapse
thanks for the help, before i got your message i got around the issue in a different way just trying a few things. I figured out the phone would boot into recovery with no sd card in it but i couldnt flash the rom again without it installed so i put the sd in partially and then held the battery against the contacts with out inserting it completely then booted into recovery, push the sd in the rest of the way and i was golden for there.
but i happy that someone knew wat it was on the sd card that was giving me the problem ive got that deleted now thanks for the help
xcapeartist said:
thanks for the help, before i got your message i got around the issue in a different way just trying a few things. I figured out the phone would boot into recovery with no sd card in it but i couldnt flash the rom again without it installed so i put the sd in partially and then held the battery against the contacts with out inserting it completely then booted into recovery, push the sd in the rest of the way and i was golden for there.
but i happy that someone knew wat it was on the sd card that was giving me the problem ive got that deleted now thanks for the help
Click to expand...
Click to collapse
That works too, probably not the best thing for the phone, but it works, glad i could point you in the right direction

Categories

Resources