Hello all,
I am on the stock ROM and decided to update the phone with the OTA released today. I was rooted and unlocked with S-ON, reflashed stock recovery and the update kept failing. I read a post where clearing the cache and relocking the bootloader would work. Well I did that, and now the phone only boots to the bootloader/fastboot/hboot and nothing else. It wont go into the system, and if I try recovery it shows the phone with the red triangle and exclamation mark. What did I do wrong and how can I fix it short of unlocking the bootloader again. I have some very important files on my SD card that I need to somehow save before they are erased. I tried the RUU that just got released but it wont load on my computer (Windows 8 x64). I did a backup through TWRP before I flashed the stock recovery.
I've tried flashing another recovery and I've tried using the fastboot boot command as well. I get errors on pretty much anything I do, which I'm sure is because I relocked the bootloader.
Can anyone help me out here? I'd be willing to do almost anything to get these files back.
Download Minmal ADB and Fastboot (google it) and install.
Download TWRP .img file and place it in the ADB/Fasboot folder.
Open a command prompt from that folder (shift-right-click on the folder and select "open command window here")
plug the phone in and make sure it is in bootloader mode.
type "fastboot boot openrecovery-twrp-2.6.0.1-m7.img" without the quotes and it will boot the phone into TWRP.
Factory reset and try rebooting.
If the problem continues, try sideloading a ROM from the same recovery, using the steps above and the sideload instructions in (I believe they are in General).
Sent from my Nexus 10 using Tapatalk HD
PhoenixPath said:
Download Minmal ADB and Fastboot (google it) and install.
Download TWRP .img file and place it in the ADB/Fasboot folder.
Open a command prompt from that folder (shift-right-click on the folder and select "open command window here")
plug the phone in and make sure it is in bootloader mode.
type "fastboot boot openrecovery-twrp-2.6.0.1-m7.img" without the quotes and it will boot the phone into TWRP.
Factory reset and try rebooting.
If the problem continues, try sideloading a ROM from the same recovery, using the steps above and the sideload instructions in (I believe they are in General).
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
This is what I get anytime I try to use the boot command:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot openrecovery-twrp-
2.6.0.1-m7.img
downloading 'boot.img'...
OKAY [ 1.165s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.171s
C:\Program Files (x86)\Minimal ADB and Fastboot>
simpleagony said:
This is what I get anytime I try to use the boot command:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot openrecovery-twrp-
2.6.0.1-m7.img
downloading 'boot.img'...
OKAY [ 1.165s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.171s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
What do you get when you type
Code:
fastboot devices
It should list your device like:
Code:
HT34SW900239 fastboot
If it is not, your computer is not detecting your device in bootloader mode. Also, does your bootloader say "locked" at the top?
If you get a device list, run
Code:
fastboot getver all
and post the results...
PhoenixPath said:
What do you get when you type
Code:
fastboot devices
It should list your device like:
Code:
HT34SW900239 fastboot
If it is not, your computer is not detecting your device in bootloader mode. Also, does your bootloader say "locked" at the top?
If you get a device list, run
Code:
fastboot getver all
and post the results...
Click to expand...
Click to collapse
I relocked my bootloader so that today's update would finally work, but that's when the problem started. Here's the getvar command:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35NW902997
(bootloader) imei: 355972054669271
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4330mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.052s
simpleagony said:
I relocked my bootloader so that today's update would finally work, but that's when the problem started. Here's the getvar command:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35NW902997
(bootloader) imei: 355972054669271
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4330mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.052s
Click to expand...
Click to collapse
Unlock the bootloader and try the TWRP wipes again.
PhoenixPath said:
Unlock the bootloader and try the TWRP wipes again.
Click to expand...
Click to collapse
I'm willing to try that as a last resort, but I have some stuff I need to save on the SD Card. Is there anyway to save it, or rescue it (data recovery software)?
simpleagony said:
I'm willing to try that as a last resort, but I have some stuff I need to save on the SD Card. Is there anyway to save it, or rescue it?
Click to expand...
Click to collapse
Without being able to get into any alternate recovery or adb, I really don't see how...unless someone else has some other ideas.
PhoenixPath said:
Without being able to get into any alternate recovery or adb, I really don't see how...unless someone else has some other ideas.
Click to expand...
Click to collapse
I figured as much. Thanks for all your help PhoenixPath. :good:
Related
I'm trying to go through the official HTC bootloader unlock process for Thunderbolt and I'm running into a problem. This is a test phone for work and not for personal use, so I need to do this on the up and up (with the boss' permission). The phone has HBOOT 1.04.00 and the system version is 2.11.605.9 (Gingerbread 2.3.4). I think that's all the OTAs.
When I hook the phone to my PC (Windows 7 Pro) and Ubuntu Linux (10.10), they enumerate the phone correctly. On Windows, the drivers enumerate and on Linux, lsusb shows it. When booted normally, 'adb devices' shows it. When I boot the phone into fastboot mode and type 'fastboot devices', the device is listed. All good so far.
When I type 'fastboot oem get_identifier_token', I get an error message as follows:
C:\android-sdk-windows\tools>.\fastboot oem get_identifier_token
... INFO[ERR] Command error !!!
OKAY
On Linux, the error is identical. I have tried several versions of fastboot from several different SDK versions. I submitted a support ticket to HTC, but the reply was just to use the latest version of fastboot and that was all they said.
Doing a Google search shows this to be a common problem without a clear solution. Is the availability of the get_identifier_token command tied to the version of fastboot or is it in the bootloader of the device itself? If it's in the bootloader, do I need a newer version of HBOOT? I know a lot of versions of patched HBOOT are floating around, I need to stay on official versions for when we need to relock the device and hand it over to the next team.
Thanks for any advice
I'm having this same issue with my htc inspire. Everytime i try to complete the unlock It gives me that error. The phone is going to be used for traveling so I need to figure this out. Maybe this will help?
Code:
c:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.85.0024
(bootloader) version-baseband: 26.10.04.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0438
(bootloader) version-main: 2.47.502.7
(bootloader) serialno: HT18ST205380
(bootloader) imei: 358920041451896
(bootloader) product: ace
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PD9812000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3938mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: a3d4fa0f
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) region-id: 0
all: Done!
finished. total time: 0.011s
possible try the non official method and see if that works
Here's some phone history:
Factory S-Off
Flashed TWRP and permaroot here
Flashed ViperLTE 1.0.0
Ran that for a while, then the RUU came out.
Flashed the RUU.
Unlock comes along, so I unlocked it. Then I flashed ViperLTE 2.0.0, and had the sync and phone process issue so I relocked and changed the CID back.
Been running great up until today.
So I go to unlock my screen to reply to a text, and the LED isn't flashing and the touch seemed unresponsive. So I reboot to hboot, and it tells me "battery low replace battery" then "press power to continue" or something along those lines.
I went into recovery and nothing works, no touch, no LEDs, I just see the recovery.
At this point I got scared. Battery pull, reboot. Boots up into ROM, but no touch. I get texts, email updates, etc in the statusbar showing but when I tried calling the phone, the process stopped and everything looked frozen in the background.
Reboot into recovery, and while sitting there plugged in the battery DROPS
So I turned the phone completely off for an hour, still no charging.
Booted up into the ROM, and as I'm sitting here the battery is charging again.
Heres my post in the viper thread:
jtdogblue said:
It's been plugged in for a while now and no change in the indicated charge in recovery or once booted. Should I go ahead and try flashing the recovery?
EDIT: The phone's been off completely and wasn't charging, as it's sitting in recovery the battery level is.... dropping?
e:\android>fastboot flash recovery recovery.img
sending 'recovery' (9820 KB)...
OKAY [ 1.107s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.144s
e:\android>
e:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.15.0000
(bootloader) version-baseband: 1.53.06.0919
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT26JS309742
(bootloader) imei: 990000641796059
(bootloader) product: fireball
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ5310000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3690mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3321eb88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.082s
Edit: I booted up and the battery is charging again.
Click to expand...
Click to collapse
So, that's where I'm at. Just figured I'd start a new thread instead of spamming the viper one.
Out of curiosity, if you were already s-off, why did you run the Fake CID unlock? With s-off, you should be able to push whatever you want onto the phone, including recovery and ROMs.
You may need to re-lock the bootloader and use the RUU to restore your phone to "factory" (with s-off) and start over. However, I do not know if the latest RUU will affect your s-off status, though, so proceed with great caution. Maybe andybones can confirm if the latest RUU has any negative effect on s-off.
junkmail9 said:
Out of curiosity, if you were already s-off, why did you run the Fake CID unlock? With s-off, you should be able to push whatever you want onto the phone, including recovery and ROMs.
You may need to re-lock the bootloader and use the RUU to restore your phone to "factory" (with s-off) and start over. However, I do not know if the latest RUU will affect your s-off status, though, so proceed with great caution. Maybe andybones can confirm if the latest RUU has any negative effect on s-off.
Click to expand...
Click to collapse
I keep asking myself the same question. The ruu.exe isn't working, it does absolutely nothing for me, so I flashed the individual things through hboot the first time didnt effect soff
jtdogblue said:
I keep asking myself the same question. The ruu.exe isn't working, it does absolutely nothing for me, so I flashed the individual things through hboot the first time didnt effect soff
Click to expand...
Click to collapse
since you decided to do the htc dev-unlock (which idk why, since u were s-off)
in order for you to run an RUU in bootloader, you need to re-lock the bootloader..
here's mine
C:\apktool>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.02.1111
(bootloader) version-baseband: 1.53.06.0919
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: fireball
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ5310000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4293mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-75a5dc7e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.103s
C:\apktool>
---------- Post added at 05:22 PM ---------- Previous post was at 05:19 PM ----------
also you have to run a command to turn it back to S-ON, other than that it's perm.
andybones said:
since you decided to do the htc dev-unlock (which idk why, since u were s-off)
in order for you to run an RUU in bootloader, you need to re-lock the bootloader..
here's mine
C:\apktool>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.02.1111
(bootloader) version-baseband: 1.53.06.0919
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: fireball
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ5310000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4293mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-75a5dc7e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.103s
C:\apktool>
---------- Post added at 05:22 PM ---------- Previous post was at 05:19 PM ----------
also you have to run a command to turn it back to S-ON, other than that it's perm.
Click to expand...
Click to collapse
I left the bootloader relocked. The RUU isn't working. It gets all the way through loading the installshield wizzard then just quits.
I'm about to spike this phone into the ground. $250 out the freaking window
jtdogblue said:
I left the bootloader relocked. The RUU isn't working. It gets all the way through loading the installshield wizzard then just quits.
I'm about to spike this phone into the ground. $250 out the freaking window
Click to expand...
Click to collapse
sounds to me like the bootloader is unlocked man.
andybones said:
sounds to me like the bootloader is unlocked man.
Click to expand...
Click to collapse
It says *RELOCKED* at the top. Also, the ruu doesnt let me click anything, just loads up then quits
PLEASE stay with me. I'm about to die here pressing refresh every 5 seconds
jtdogblue said:
It says *RELOCKED* at the top. Also, the ruu doesnt let me click anything, just loads up then quits
PLEASE stay with me. I'm about to die here pressing refresh every 5 seconds
Click to expand...
Click to collapse
INSTRUCTIONS
1) Download this - MD5 = 55023CC10B59FDEC0AAA6695C4CF83FB
2) rename to PJ53IMG.zip (make sure it's not named PJ53IMG.zip.zip...)
3) put the PJ53IMG.zip on the root of your SD-Card. (not in any folders)
4) reboot to bootloader
5) let the phone do its magic
6) enjoy Sense 4.1
I am VERY appreciative of any help you provide, I didn't mean to come across as pushy in any way. Thank you again
jtdogblue said:
I am VERY appreciative of any help you provide, I didn't mean to come across as pushy in any way. Sorry
Click to expand...
Click to collapse
Thank you. I appreciate that.
Please try this
INSTRUCTIONS
1) Download this - MD5 = 55023CC10B59FDEC0AAA6695C4CF83FB
2) rename to PJ53IMG.zip (make sure it's not named PJ53IMG.zip.zip...)
3) put the PJ53IMG.zip on the root of your SD-Card. (not in any folders)
4) reboot to bootloader
5) let the phone do its magic
6) enjoy Sense 4.1
---------- Post added at 06:34 PM ---------- Previous post was at 06:14 PM ----------
Once you are S-OFF it is permanent. Only way to get back to S-ON is with a fastboot command.
andybones said:
Thank you. I appreciate that.
Please try this
INSTRUCTIONS
1) Download this - MD5 = 55023CC10B59FDEC0AAA6695C4CF83FB
2) rename to PJ53IMG.zip (make sure it's not named PJ53IMG.zip.zip...)
3) put the PJ53IMG.zip on the root of your SD-Card. (not in any folders)
4) reboot to bootloader
5) let the phone do its magic
6) enjoy Sense 4.1
---------- Post added at 06:34 PM ---------- Previous post was at 06:14 PM ----------
Once you are S-OFF it is permanent. Only way to get back to S-ON is with a fastboot command.
Click to expand...
Click to collapse
Didnt work
jtdogblue said:
Didnt work
Click to expand...
Click to collapse
wow really
I'm thinking by unlocking bootloader you may have messed something up?
have you tried setting the phone back to the original CID?
andybones said:
wow really
I'm thinking by unlocking bootloader you may have messed something up?
have you tried setting the phone back to the original CID?
Click to expand...
Click to collapse
Yes, I had to set it to the original CID to get it re locked.
e:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.15.0000
(bootloader) version-baseband: 1.53.06.0919
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.17.605.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT26JS309742
(bootloader) imei: 990000641796059
(bootloader) product: fireball
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ5310000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3639mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3321eb88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
e:\android>
jtdogblue said:
Yes, I had to set it to the original CID to get it re locked.
e:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.15.0000
(bootloader) version-baseband: 1.53.06.0919
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.17.605.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT26JS309742
(bootloader) imei: 990000641796059
(bootloader) product: fireball
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ5310000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3639mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3321eb88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
e:\android>
Click to expand...
Click to collapse
only other thing I can think of is to try installing RUU using fastboot command
fastboot oem rebootRUU
also just for the heck of it (yes i know you are locked) but just for ****s and gigs, do a relock again, make sure the phone reboots, then try fastboot oem rebootRUU
andybones said:
only other thing I can think of is to try installing RUU using fastboot command
fastboot oem rebootRUU
also just for the heck of it (yes i know you are locked) but just for ****s and gigs, do a relock again, make sure the phone reboots, then try fastboot oem rebootRUU
Click to expand...
Click to collapse
I ran the fastboot oem rebootRUU and now its stuck on the darker black and silver htc screen...
jtdogblue said:
I ran the fastboot oem rebootRUU and now its stuck on the darker black and silver htc screen...
Click to expand...
Click to collapse
I think that is good..
should mean it's installing RUU..
andybones said:
I think that is good..
should mean it's installing RUU..
Click to expand...
Click to collapse
Well the first time I did it, it showed everything being done in hboot. I'll let it sit an hour or so and report back.
ok with it in the black screen, put the PJ53IMG.zip in your sdk folder and then do this command
fastboot flash zip PJ53IMG.zip
*you should now see it flashing things. do not for any reason interupt it during this process. when its finished:
fastboot reboot-bootloader
---------- Post added at 07:30 PM ---------- Previous post was at 07:29 PM ----------
jtdogblue said:
Well the first time I did it, it showed everything being done in hboot. I'll let it sit an hour or so and report back.
Click to expand...
Click to collapse
no need for that..
if it's installing in hboot ur good to go.
andybones said:
ok with it in the black screen, put the PJ53IMG.zip in your sdk folder and then do this command
fastboot flash zip PJ53IMG.zip
*you should now see it flashing things. do not for any reason interupt it during this process. when its finished:
fastboot reboot-bootloader
---------- Post added at 07:30 PM ---------- Previous post was at 07:29 PM ----------
no need for that..
if it's installing in hboot ur good to go.
Click to expand...
Click to collapse
NOOOOOOOO!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
e:\android>fastboot flash zip PJ53IMG.zip
sending 'zip' (583416 KB)...
OKAY [ 19.895s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 23.620s
jtdogblue said:
NOOOOOOOO!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
e:\android>fastboot flash zip PJ53IMG.zip
sending 'zip' (583416 KB)...
OKAY [ 19.895s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 23.620s
Click to expand...
Click to collapse
whoa, you did this when in the rebootRUU mode right?
the black with silver
Hi:
I have a Amaze ans there is no way I can go into recovery or OS.
I already reflash all ICS original images and the same.
Did it unlocked and relocked asame result.
I can go into HBOOT but nothing else.
The USB debug is not activated so I have very few options.
this is what I see in HBOOT:
*** UNLOCKED *** or *** RELOCKED ***
RUBY PVT SHIP S-ON RL
HBOOT-1.93.0002
OpenADSP-v02.6.0.2226.00.0202
eMMC-boot
Mar 15 2012,21:46:51
I can go into fastboot and execute commands, I even try to reflash TWRP with Hasoon tool and by myself with no luck.
When I try to boot recovery the phone shows the white HTC screen and vibrate. then it make a few soft vibrations with some time between then like it was in a loop.
In Win 8.1 it does not mount correctly. I manage to access it in Win7. In Linux did not mount either.
Any help?
=> fastboot getvar all result:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.93.0002
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.531.1
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxx
(bootloader) product: ruby
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH8511000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3816mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6298f8f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.518s
ludohavil said:
Hi:
I have a Amaze ans there is no way I can go into recovery or OS.
I already reflash all ICS original images and the same.
Did it unlocked and relocked asame result.
I can go into HBOOT but nothing else.
The USB debug is not activated so I have very few options.
this is what I see in HBOOT:
*** UNLOCKED *** or *** RELOCKED ***
RUBY PVT SHIP S-ON RL
HBOOT-1.93.0002
OpenADSP-v02.6.0.2226.00.0202
eMMC-boot
Mar 15 2012,21:46:51
I can go into fastboot and execute commands, I even try to reflash TWRP with Hasoon tool and by myself with no luck.
When I try to boot recovery the phone shows the white HTC screen and vibrate. then it make a few soft vibrations with some time between then like it was in a loop.
In Win 8.1 it does not mount correctly. I manage to access it in Win7. In Linux did not mount either.
Any help?
=> fastboot getvar all result:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.93.0002
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.531.1
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxx
(bootloader) product: ruby
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH8511000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3816mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6298f8f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.518s
Click to expand...
Click to collapse
Try this fastboot command when flashing the recovery.
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Sent from my HTC One using xda app-developers app
king_david43 said:
Try this fastboot command when flashing the recovery.
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
If that doesn't work, download the latest available RUU from one of the threads here and flash it via fastboot:
Code:
fastboot oem rebootruu
fastboot flash zip rom.zip
fastboot reboot
When something like what happened to you happened to me, that helped me. Bear in mind these commands got me a working Amaze, but all personal data is gone. I don't remember if my internal SD was wiped, but it's possible it was.
Also, the "rom.zip" is relative to the path you're running the fastboot command from. So if you're running fastboot from C:\Android, easiest thing to do is put the zip file in the same folder.
As the title says, After I unlocked the bootloader, and flashed a 4.4 rom, My HTC will just do a boot loop on the HTC Logo, I can go into fastboot and recovery no problem but I can't send any file by USB.
Thanks on any help...
poorg said:
As the title says, After I unlocked the bootloader, and flashed a 4.4 rom, My HTC will just do a boot loop on the HTC Logo, I can go into fastboot and recovery no problem but I can't send any file by USB.
Thanks on any help...
Click to expand...
Click to collapse
You will need to post fastboot getvar all, current recovery version and which rom you are attempting to install.
poorg said:
As the title says, After I unlocked the bootloader, and flashed a 4.4 rom, My HTC will just do a boot loop on the HTC Logo, I can go into fastboot and recovery no problem but I can't send any file by USB.
Thanks on any help...
Click to expand...
Click to collapse
mb_guy said:
You will need to post fastboot getvar all, current recovery version and which rom you are attempting to install.
Click to expand...
Click to collapse
you need TWRP 2.6.3.3
here - http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then your rom will flash and boot up
Same Problem
I have the same problem, but i have instaled the TWRP Recovery and i can access in the bootloader recovery. i have the version "twrp-2.6.3.4"
what can do for recover the phone?
C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-a85199f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
the rom i try to install is this: m7_Stock_Rooted_4.18.502.7_Odex.zip
i think is not At&t
Please help!
Alfre Chataing said:
I have the same problem, but i have instaled the TWRP Recovery and i can access in the bootloader recovery. i have the version "twrp-2.6.3.4"
what can do for recover the phone?
C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-a85199f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
the rom i try to install is this: m7_Stock_Rooted_4.18.502.7_Odex.zip
i think is not At&t
Please help!
Click to expand...
Click to collapse
You could use this one then take the ota later.
http://forum.xda-developers.com/showthread.php?t=2476204
Just found this one
http://forum.xda-developers.com/showthread.php?t=2676986
Alfre Chataing said:
I have the same problem, but i have instaled the TWRP Recovery and i can access in the bootloader recovery. i have the version "twrp-2.6.3.4"
what can do for recover the phone?
C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-a85199f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
the rom i try to install is this: m7_Stock_Rooted_4.18.502.7_Odex.zip
i think is not At&t
Please help!
Click to expand...
Click to collapse
Yes that's my Rom ... you don't know how to flash it? or whats the problem ?
You have bootloop ? did you use all the commands when you flashed TWRP ?
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
and yes it's Pure AT&T from the 4.4.2 OTA update
---------- Post added at 04:22 PM ---------- Previous post was at 04:20 PM ----------
mb_guy said:
You could use this one then take the ota later.
http://forum.xda-developers.com/showthread.php?t=2476204
Just found this one
http://forum.xda-developers.com/showthread.php?t=2676986
Click to expand...
Click to collapse
he's already 3.17.502.3 ( I guess he never got the update )
and the second link is the same rom he already has why download it again ?
mb_guy said:
You could use this one then take the ota later.
http://forum.xda-developers.com/showthread.php?t=2476204
Just found this one
http://forum.xda-developers.com/showthread.php?t=2676986
Click to expand...
Click to collapse
Thanks, i used the second link with this instructions and works fine:
your going to reflash recovery then a rom
download twrp 2.6.3.3 here > http://techerrata.com/browse/twrp2/m7
then flash it in fastboot
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then download the rom post below and sideload it to your phone
boot to recovery then
TWRP / Advanced / Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
Alfre Chataing said:
Thanks, i used the second link with this instructions and works fine:
your going to reflash recovery then a rom
download twrp 2.6.3.3 here > http://techerrata.com/browse/twrp2/m7
then flash it in fastboot
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then download the rom post below and sideload it to your phone
boot to recovery then
TWRP / Advanced / Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
Click to expand...
Click to collapse
Good to here .. I've posted those instructions dozens of times, glad I could help
clsA said:
Good to here .. I've posted those instructions dozens of times, glad I could help
Click to expand...
Click to collapse
Yes, my friend thanks!
i cant write early and give the thanks because i'm new in XDA a cant write several times.
Best regards!
I have my htc one back to the stock room 4.1.2 sideload via adb. Thanks to the developers.
So last week I reverted back to stock recovery to get the OTA 4.4.4 update. That went fine, so last night I tried to install a custom recovery again... which I'm not sure was actually successful, but basically, the phone is now stuck in hboot/fastboot. Attempting to reboot into recovery just reboots the phone into fastboot.
I unlocked and did S-off last year. Had a recovery (not sure which, I think twrp) but was still on stock rom. Interestingly, the banner at the top used to say the software was modified, but ever since I got this problem it now reads "software status: official". Also, the value for both the "radio" and "OpenDSP" fields on the fastboot screen is "INVALID_VER_INFO", which I don't know is pertinent or not but I don't think it was like that before.
I did a ton of research and I found this unresolved thread which seems to have the exact same situation. To be specific, "adb devices" command doesn't show any devices, "fastboot devices" shows the device, multiple attempts at flashing different recoveries via fastboot fail, running an RUU exe from windows fails (error [170]: USB CONNECTION ERROR), running a bootable RUU from extSD card fails (after it asks me if I want to update, and I select yes, it then returns a "partition update failed" error).
I'm seriously stumped and I'm not sure what else I can do at this point. Any advice or help?
getvar all dump:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.42.502.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxx
(bootloader) imei: xxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 56f9ae32
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Wasted my time responding to your other post, asking for info posted here. DON'T MAKE MULTIPLE POSTS FOR THE SAME ISSUE/QUESTION.
Follow my advice given in the last part of my post here, than get back to me. Stick to this thread, not the other one that is several months old.
Bootloader currently UNLOCKED or RELOCKED?
redpoint73 said:
Wasted my time responding to your other post, asking for info posted here. DON'T MAKE MULTIPLE POSTS FOR THE SAME ISSUE/QUESTION.
Follow my advice given in the last part of my post here, than get back to me. Stick to this thread, not the other one that is several months old.
Bootloader currently UNLOCKED or RELOCKED?
Click to expand...
Click to collapse
Sorry, lesson learned. Bootloader currently unlocked. Followed your advice in linked post, tried uninstalling drivers, using generic mtp drivers on both my win7 and win8 machine; still getting the same results. Using the "minimal adb and fastboot" program that's been linked on various m8 forums, it shows the device with the "fastboot devices" command but any command like "fastboot erase cache" or "fastboot flash recovery recovery.img" returns an error. RUU also returns the same error as before.
isaac.jang216 said:
it shows the device with the "fastboot devices" command but any command like "fastboot erase cache" or "fastboot flash recovery recovery.img" returns an error.
Click to expand...
Click to collapse
Do you remember the specific errors?
redpoint73 said:
Do you remember the specific errors?
Click to expand...
Click to collapse
I ran the RUU twice and when it tries to verify the device is connected, it returned an ERROR [170] and an ERROR [171]. Both read "usb connection error".
The "fastboot erase cache" command returns: FAILED (remote: erasing error!)
The "fastboot flash recovery recovery.img" command returns: FAILED (remote: image update error)