Hi,
I have been searching for clue how to fix my HTC EVO 3D GSM. It has stucked at the HTC logo during boot up. I have searched everywhere for how to resolve the problem. I have seen a lot where it says you can flash the recovery etc. However, my phone is on S-ON and LOCKED. I have never flash the ROM. It has always been using the Stock HTC ROM Jellybean.
Here's the detail on Volume Down + Power
SHOOTER_U PVT SHIP S_ON RL
HBOOT-1.53.0007
eMMC-boot
May 22 2012, 01.06:07
I have tried these
- put the recovery PG86IMG.zip in the root of sdcard
- unlock, all worked including getting the unlock code, which was successful, but the reboot stops at HTC, after the same Volume Down + Power, still Locked.
- can't do the wiretrick since it is GSM or HBOOT 1.53, and can't downgrade, because it is Locked
- can't flash the boot img because it is still locked
- RUU from HTC, but it complained no phone is connected
I'm out of options. Is there any other way I can recover this phone?
hudhood said:
Hi,
I have been searching for clue how to fix my HTC EVO 3D GSM. It has stucked at the HTC logo during boot up. I have searched everywhere for how to resolve the problem. I have seen a lot where it says you can flash the recovery etc. However, my phone is on S-ON and LOCKED. I have never flash the ROM. It has always been using the Stock HTC ROM Jellybean.
Here's the detail on Volume Down + Power
SHOOTER_U PVT SHIP S_ON RL
HBOOT-1.53.0007
eMMC-boot
May 22 2012, 01.06:07
I have tried these
- put the recovery PG86IMG.zip in the root of sdcard
- unlock, all worked including getting the unlock code, which was successful, but the reboot stops at HTC, after the same Volume Down + Power, still Locked.
- can't do the wiretrick since it is GSM or HBOOT 1.53, and can't downgrade, because it is Locked
- can't flash the boot img because it is still locked
- RUU from HTC, but it complained no phone is connected
I'm out of options. Is there any other way I can recover this phone?
Click to expand...
Click to collapse
Put into fastboot mode to use ruu. Which version of windows are you using? I know anything newer then XP has driver issues.
Can flash ruu manually, run ruu it will extract rom.zip to a temp folder. Copy rom.zip.
Run these commands from directory with fastboot.exe and rom.zip in it.
fastboot oem rebootRUU
fastboot flash zip rom.zip
I am running it from Windows XP. Yeah, connection is not an issue. After struggling with Windows 10.
I tried the command suggested, fastboot oem rebootRUU and got these messages
C:\Android\ADB>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) [SD/EMMC]Error status=0x400008
(bootloader) DATA_TIMEOUT
(bootloader) SD: write failed in CMD25.
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 3
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) emmc_erase(1852): sd_write_sector failed!
OKAY [ 1.313s]
finished. total time: 1.328s
Looks like hardware failure to me. Is there anyway I can save the phone?
hudhood said:
I am running it from Windows XP. Yeah, connection is not an issue. After struggling with Windows 10.
I tried the command suggested, fastboot oem rebootRUU and got these messages
C:\Android\ADB>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) [SD/EMMC]Error status=0x400008
(bootloader) DATA_TIMEOUT
(bootloader) SD: write failed in CMD25.
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 3
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) emmc_erase(1852): sd_write_sector failed!
OKAY [ 1.313s]
finished. total time: 1.328s
Looks like hardware failure to me. Is there anyway I can save the phone?
Click to expand...
Click to collapse
I think I've got an idea how to do the wiretrick but lets try the other way. You can unlock your device (the htc dev way), flash a recovery and wipe+install.
Sent from my Evo 3D GSM using Tapatalk
mhnx said:
I think I've got an idea how to do the wiretrick but lets try the other way. You can unlock your device (the htc dev way), flash a recovery and wipe+install.
Sent from my Evo 3D GSM using Tapatalk
Click to expand...
Click to collapse
I have tried unlocking the device the htc dev way, even though the unlocking code was successful, the phone still says it's locked. I have two phones of the same kind, the other one was unlocked without any problem. But this one, still remains locked.
Did it reboot into ruu mode? Also sounds like a bad sdcard. Try a different one or remove altogether.
jcfunk said:
Did it reboot into ruu mode? Also sounds like a bad sdcard. Try a different one or remove altogether.
Click to expand...
Click to collapse
It reboots and got stucked at the HTC logo. I had to remove the battery and volume down + power boot again. As for the sd card, I tried another sd card, and gave me the same error. Both sd card worked fine on another phone HTC EVO 3D.
hudhood said:
It reboots and got stucked at the HTC logo. I had to remove the battery and volume down + power boot again. As for the sd card, I tried another sd card, and gave me the same error. Both sd card worked fine on another phone HTC EVO 3D.
Click to expand...
Click to collapse
Is it a black HTC screen?
jcfunk said:
Is it a black HTC screen?
Click to expand...
Click to collapse
No. It's the white HTC logo, before displaying the quietly brilliant message.
Related
I have problem. A seriously problem.
Hboot 1.53.0007 S-ON
My Evo have restarts after showing HTC screen when I try to boot into recovery or normal boot.
After flashing RUU got the same problem.
I can:
get to fastboot but not every command correctly work, when changing CID have errors.
When I try to have LOCK Bootloader(not "relock") for warranty purposes with this command:
" fastboot oem writesecureflag 3 " is response with that error:
C:\fastboot>fastboot oem writesecureflag 3
< waiting for device >
...
(bootloader) vreg_set: request is duplicated id 14
(bootloader) shooter_u_init_sd, SD card power on ok
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
(bootloader) writesecureflag: Permission denied, value 1
OKAY [ 1.085s]
finished. total time: 1.085s
Click to expand...
Click to collapse
I think is the linux problem.
Is any method to repair that?
For help I send a Paypal Gift beacouse it's better than buying a new phone.
Seriously please help me and forgive my bad english
mvha said:
I have problem. A seriously problem.
Hboot 1.53.0007 S-ON
My Evo have restarts after showing HTC screen when I try to boot into recovery or normal boot.
After flashing RUU got the same problem.
I can:
get to fastboot but not every command correctly work, when changing CID have errors.
When I try to have LOCK Bootloader(not "relock") for warranty purposes with this command:
" fastboot oem writesecureflag 3 " is response with that error:
I think is the linux problem.
Is any method to repair that?
For help I send a Paypal Gift beacouse it's better than buying a new phone.
Seriously please help me and forgive my bad english
Click to expand...
Click to collapse
"fastboot oem writesecureflag 3" is command for s-off device to gain status s-on, u already have status s-on, right?
"fastboot oem lock" is command to lock bootloader, did u try this ?
Just simply relock your bootloader with "fastboot oem lock" download and run official RUU ICS rom, from here http://www.androidfiles.org/ruu/?dir=Shooter.
After flashing RUU got the same problem.
Click to expand...
Click to collapse
So I already do this steps and it doesn't work
Only flashing boot from CM9 nightly have difference because it restarts later(on HTC Quietly Brilliant screen).
But why I cant access any recovery after reflashed it using "fastboot flash recovery ....img" command.
Flashing always completed successfully.
Only Bootloader repair with JTAG helped. Now I have s-off and hboot 1.49.007.
Sent from my Evo 3D GSM using xda premium
Rezound FAILED (remote: not allowed)
I received this phone and it would boot to just the HTC screen. It will boot to the bootloader screen and I can access it with fastboot.
The filesystem seems to be locked down and I don't know how to unlock it. ADB won't work since it won't boot the OS. It also wouldn't boot into the stock recovery. When I try to boot into Amon Ra recovery, it shows the progress bar on the upper right side of the screen but then goes on into a boot loop. So parts of Amon Ra are being installed and working but not much.
At first it would boot to the HTC screen and sit there. I installed 605.2 via the PH98IMG.zip on SD method and it went along fine.
Now it just gets to the HTC screen and reboots like it has no or the wrong kernel. I unlocked the bootloader, flashed amon ra and it won't boot into recovery either. I tried to erase several things, it will only let me erase "cache" not "boot", "recovery" or "system. So I'm stuck until I find out how to allow writing to these areas of the system. It also doesn't read the files in light green in boot loader mode like it should.
I think if I can get s-off I can write over what I want, but I don't know how to downgrade or where to find the files. I tried RUU_Vigor_3.14.605.10_PH98IMG but that didn't help, it just gave me an error for trying to downgrade.
I am sure if I can get access to the complete file system I can get this thing going.
C:\ADB>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.27.0000
(bootloader) version-baseband: 2.22.10.0801r/2.22.10.0803r
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.03.605.2
(bootloader) serialno: FA28YS208261
(bootloader) imei: 990000652356066
(bootloader) product: vigor
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH9810000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3861mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ad3368f2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I received this phone and it would boot to just the HTC screen. It will boot to the bootloader screen and I can access it with fastboot.
The filesystem seems to be locked down and I don't know how to unlock it. ADB won't work since it won't boot the OS. It also wouldn't boot into the stock recovery. When I try to boot into Amon Ra recovery, it shows the progress bar on the upper right side of the screen but then goes on into a boot loop. So parts of Amon Ra are being installed and working but not much.
At first it would boot to the HTC screen and sit there. I installed 605.2 via the PH98IMG.zip on SD method and it went along fine.
Now it just gets to the HTC screen and reboots like it has no or the wrong kernel. I unlocked the bootloader, flashed amon ra and it won't boot into recovery either. I tried to erase several things, it will only let me erase "cache" not "boot", "recovery" or "system. So I'm stuck until I find out how to allow writing to these areas of the system. It also doesn't read the files in light green in boot loader mode like it should.
I think if I can get s-off I can write over what I want, but I don't know how to downgrade or where to find the files. I tried RUU_Vigor_3.14.605.10_PH98IMG but that didn't help, it just gave me an error for trying to downgrade.
I am sure if I can get access to the complete file system I can get this thing going.
C:\ADB>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.27.0000
(bootloader) version-baseband: 2.22.10.0801r/2.22.10.0803r
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.03.605.2
(bootloader) serialno: FA28YS208261
(bootloader) imei: 990000652356066
(bootloader) product: vigor
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH9810000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3861mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ad3368f2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
So what exactly happens when you try to run the 4.03.605.2 RUU again? Make sure your locked if your s-on trying to run the RUU. When you tried running it the first time. Did you let it run twice?
Relocked and re-RUU
Flyhalf205 said:
So what exactly happens when you try to run the 4.03.605.2 RUU again? Make sure your locked if your s-on trying to run the RUU.
Click to expand...
Click to collapse
First when relocking I get:
C:\ADB>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 134086008 (0x7FDFD78)
FAILED (status read failed (Too many links))
finished. total time: 0.936s
I boot to bootloader and get "TAMPERED" "RELOCKED". So according to the boot loader I am unlocking and relocking successfuly and it thinks that Amon RA is installed. Amon RA does not get written by the RUU it seems. If the stock recovery was written it would not say "TAMPERED".
I can access the device with fastboot but "boot", "system", "recovery are locked". I tried the wire trick for s-off, but the program fails at "testing "ADB" because the phone never gets that far, booting into OS.
I just tried rerunning the 605.2 RUU and it went through all of the steps. I may have attempted a downgrade and it seems to downgrade some things then when i go back to 605.2 it does the whole upgrade again. I'll try the 605.2 RUU upgrade twice to see if it makes any difference. This is my 5th Rezound I've tried to upgrade to 605.2 so I know to wait for it to do all of its thing. Maybe someone earlier aborted an upgrade and hosed it. Is the area with the boot, system, recovery removeable. If so, I'd replace the internal SD. For a while I was also getting a "security warning" just below "RELOCKED".
On the initial update phase it checks the image, then reboots and gives me a list of 18 things to upgrade and the option to proceed. I click vol up and it proceeds through the list "unzipping", "updating", "OK". No errors. It takes a while to update "system" which tells me it is doing something. Ends with "Update Complete". I also tried flashing the zip from a pc with fastboot. The screen on the phone thurned black with a HTC on it and the flash seemed to run a while but no good.I also tried flashing boot.img and Amon Ra. When trying to boot into recovery from the bootloader menu the progress bar on the right side moves up as normal with Amon RA but when it reboots it just does a boot loop like it does when trying to boot the OS. On the second and subsequent boots while holding vol down and power, it re-upgrades. So it seems that the system can't write to those areas and therefore keeps trying on subsequent tries. I don't understand why it says OK after each item updated if the updates are failing.
jcampolo said:
First when relocking I get:
C:\ADB>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 134086008 (0x7FDFD78)
FAILED (status read failed (Too many links))
finished. total time: 0.936s
I boot to bootloader and get "TAMPERED" "RELOCKED". So according to the boot loader I am unlocking and relocking successfuly and it thinks that Amon RA is installed. Amon RA does not get written by the RUU it seems. If the stock recovery was written it would not say "TAMPERED".
I can access the device with fastboot but "boot", "system", "recovery are locked". I tried the wire trick for s-off, but the program fails at "testing "ADB" because the phone never gets that far, booting into OS.
I just tried rerunning the 605.2 RUU and it went through all of the steps. I may have attempted a downgrade and it seems to downgrade some things then when i go back to 605.2 it does the whole upgrade again. I'll try the 605.2 RUU upgrade twice to see if it makes any difference. This is my 5th Rezound I've tried to upgrade to 605.2 so I know to wait for it to do all of its thing. Maybe someone earlier aborted an upgrade and hosed it. Is the area with the boot, system, recovery removeable. If so, I'd replace the internal SD. For a while I was also getting a "security warning" just below "RELOCKED".
On the initial update phase it checks the image, then reboots and gives me a list of 18 things to upgrade and the option to proceed. I click vol up and it proceeds through the list "unzipping", "updating", "OK". No errors. It takes a while to update "system" which tells me it is doing something. Ends with "Update Complete". I also tried flashing the zip from a pc with fastboot. The screen on the phone thurned black with a HTC on it and the flash seemed to run a while but no good.I also tried flashing boot.img and Amon Ra. When trying to boot into recovery from the bootloader menu the progress bar on the right side moves up as normal with Amon RA but when it reboots it just does a boot loop like it does when trying to boot the OS. On the second and subsequent boots while holding vol down and power, it re-upgrades. So it seems that the system can't write to those areas and therefore keeps trying on subsequent tries. I don't understand why it says OK after each item updated if the updates are failing.
Click to expand...
Click to collapse
I had a similar issue with mine last week. Woke up to a phone that booted to the white screen, and that's all. I tried pushing a new kernel, new recovery, nothing. I relocked and got the same error code, but regardless it DID relock the bootloader. I ran the RUU for the Global (which I was on) and that fixed the phone to a working stock again (stock to the Global Rom, which never went official). I had to flash it twice as a Ph98IMG. After the second flashing, I pulled the SD card and rebooted. It's been working fine since. I have yet to unlock again. Maybe tonight if I have time. I am missing my wireless tether.
318sugarhill said:
I had a similar issue with mine last week. Woke up to a phone that booted to the white screen, and that's all. I tried pushing a new kernel, new recovery, nothing. I relocked and got the same error code, but regardless it DID relock the bootloader. I ran the RUU for the Global (which I was on) and that fixed the phone to a working stock again (stock to the Global Rom, which never went official). I had to flash it twice as a Ph98IMG. After the second flashing, I pulled the SD card and rebooted. It's been working fine since. I have yet to unlock again. Maybe tonight if I have time. I am missing my wireless tether.
Click to expand...
Click to collapse
I tried it twice in a row as PH98IMG.zip with no luck. I've probably tried is a dozen or so times with "relocked" just as I have done four others. This is the only one that has this issue. How can you get s-off with no boot, fastboot is fine from the device or pc, I also cant boot to recovery. booting to recovery just puts in another loop. Is there a way to read the name of the recovery or address that partition?
As a side note: I also noted that anytime I plug the pc usb into the phone it powers up into bootloader. This happens anytime, even after a battery pull and reinsert. It's like the phone wants me to do something but I dont know what.
jcampolo said:
I tried it twice in a row as PH98IMG.zip with no luck. I've probably tried is a dozen or so times with "relocked" just as I have done four others. This is the only one that has this issue. How can you get s-off with no boot, fastboot is fine from the device or pc, I also cant boot to recovery. booting to recovery just puts in another loop. Is there a way to read the name of the recovery or address that partition?
As a side note: I also noted that anytime I plug the pc usb into the phone it powers up into bootloader. This happens anytime, even after a battery pull and reinsert. It's like the phone wants me to do something but I dont know what.
Click to expand...
Click to collapse
So you've been trying with the global RUU? What were you on before? Just curious.
Reply
318sugarhill said:
So you've been trying with the global RUU? What were you on before? Just curious.
Click to expand...
Click to collapse
I don't know what it was on before. When I got it it would only boot to the HTC screen that just has "HTC" on a white background.
So I took the battery to see if I could get to the bootloader screen. That worked so I figured the rest was simple, flash a RUU.
I should have checked the current version but just learned to do that while working on this thing.
I unlocked it, flashed Amon RA, relocked it and I flashed the 4.03.605.2 zip RUU and all looked good. OK, OK, OK, etc. Rebooted to a boot loop.
Tried to go to recovery, another boot loop.
It can't write to the boot, system or recovery, access is denied.
Thats where i am. Tried a ton of stuff, a million threads, no luck.
Now I'm trying to get it back to any stock rom that I can get to work and I know how to proceed from there.
tried RUU_Vigor_VERIZON_WWE_1.00.605.3 exe and RUU_Vigor_VERIZON_WWE_2.01.605.11 the installer goes through all of the steps and fails stating that the current rom is newer than the upgrade and stops. Maybe, just maybe if there was a version newer than 4.03.605.2 it would take. I'd like to just downgrade somehow and start from there. Or maybe an RUU exe for 4.03.605.2 would work if I could find one. The earlier exes work up to the point of quiting when the RUU is older than the installed version.
I have an HTC One X+ (AT&T) that i rooted and unlocked using the All-in-One toolkit version 2.4.
A day or so ago i believe i am having some partition corruption that makes my phone reboot any time you try to access things on the phone.
What it will do.
Boot normal and sit there as long as you let it sit.
boot to bootloader (Unlocked)
boot to TWRP
can see with adb and with fastboot
Things I can't do.
Copy anything to the phone through windows explorer
download anything to the phone
install any programs to the phone
push via adb to anywhere on the phone
mount usb in TWRP
sideload anything
wont reflash recovery...says it works and then reboot back to same recovery
cannot relock bootloader
due to unlock cannot RUU
cannot format/erase due to S-ON (which i believe is not changable on this model)
Not sure where to go from here. Any thoughts?
taenkarth said:
I have an HTC One X+ (AT&T) that i rooted and unlocked using the All-in-One toolkit version 2.4.
...
Not sure where to go from here. Any thoughts?
Click to expand...
Click to collapse
What ROM you are using? You forgot the most vital information...
Addicted2xda said:
What ROM you are using? You forgot the most vital information...
Click to expand...
Click to collapse
Stock. I did the latest OTA update to my phone before I rooted, unlocked. I have not installed any custom roms yet.
taenkarth said:
Stock. I did the latest OTA update to my phone before I rooted, unlocked. I have not installed any custom roms yet.
Click to expand...
Click to collapse
Have you tried factory reset?
Yes. Sorry I forgot to mention that.
I have also tried to do the factory wipe from settings while the phone was booted.
taenkarth said:
Yes. Sorry I forgot to mention that.
I have also tried to do the factory wipe from settings while the phone was booted.
Click to expand...
Click to collapse
If you are TWRP - erase data... first if that does not solve
Lock the bootloader and then re unlock it... I think it will solve your problem...
Things I can't do.
Copy anything to the phone through windows explorer
download anything to the phone
install any programs to the phone
push via adb to anywhere on the phone
mount usb in TWRP
sideload anything
wont reflash recovery...says it works and then reboot back to same recovery
cannot relock bootloader
due to unlock cannot RUU
cannot format/erase due to S-ON (which i believe is not changable on this model)
Click to expand...
Click to collapse
As you can see above I cannot lock the bootloader.
When I try to erase data from TWRP it fails stating that it cannot wipe /data. Unable to format to remove encryption.
Other thoughts?
Also when run getvar alll in fastboot i get this
C:\data>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.40.0000
(bootloader) version-baseband: SSD:2.14.55.01
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.19.502.1
(bootloader) serialno: HT2BCW301690
(bootloader) imei: 353429050343486
(bootloader) product: evitare_ul
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PM6310000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3778mV
(bootloader) devpower: 41
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.452s
taenkarth said:
As you can see above I cannot lock the bootloader.
When I try to erase data from TWRP it fails stating that it cannot wipe /data. Unable to format to remove encryption.
Other thoughts?
Click to expand...
Click to collapse
What problem are your facing / error message you are getting when trying to relock the bootloader?
Sometimes I get a failed with too many links.
Sometimes I get successful.
Either response I get doesn't change what the top of my boot loader says which is "unlocked" in pink.
I just guessing, maybe your internal Sdcard has been bad sector, did u check that?
Sent from my HTC One X+ using xda premium
I was thinking the same but don't know how to check. What do I do to check/repair that kind of issue on an internal card?
stop stop STOP!
when you relock the device, it will ALWAYS, say failed, but it does actually relock.
I have heard that. However, no matter what message I get when I boot into the boot loader afterwards it still says unlocked in pink at the top .
taenkarth said:
I have heard that. However, no matter what message I get when I boot into the boot loader afterwards it still says unlocked in pink at the top .
Click to expand...
Click to collapse
Are you using hasoon's toolkit?
If yes - put the unlock_code.bin in root of the toolkit folder and try a few times ... it should work.
Also, make sure you can see your device in adb...
Ok I just did this.
Put unlock_code.bin in the root of the AIO folder and ran the command three times. I also ran fastboot oem lock with the same results.
"fastboot devices" shows the device as connected in fastboot.
Here are the responses I get.
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.136s
...
(bootloader) Lock successfully...
OKAY [ 0.128s]
finished. total time: 0.129s
Both times I boot back into the bootloader and the top still says UNLOCKED in pink letters.
I can adb to it fine from within TWRP recovery or when the phone is standard booted.
Any new ideas?
I ran fdisk from recovery and the partition for data says that it doesn't contain a valid partition table.
Same with cache. Does that mean anything?
I have also found that every single time it reboots, it reverts everything back to the 23 of June. To the same exact instance in time. Any ideas?
Thanks!
Did I see somewhere that you had your phone encrypted? Try rebooting back into the ROM and going to Settings > Storage and uncheck Phone Storage Encryption.
No clue if that's the case or if it'll help, but it's one less thing it could be, ya know?
No encryption turned on in the Rom pin storage tab of settings. Thanks for the reply though.
What you saw on encryption was the message I get when I try to format data from within twrp recovery.
Stuck on white background with htc logo, stock rom from RUU, relocked bootloader. am able to get into bootloader, Not sure where to go from here without screwing it more, any suggestions would be greatly appreciated.
Please provide some more information .. Like your phone build, also let us know of what were you trying to achieve and the things that you have done with the phone.
same problem
ethanon said:
Please provide some more information .. Like your phone build, also let us know of what were you trying to achieve and the things that you have done with the phone.
Click to expand...
Click to collapse
i have the same problem, stuck in here for .. 2 mabey 3 months...
here is some info:
hboot:1.40.0000(*** unlocked ***)
cid:htc_e11
s-on
enrc2b_u
i have installed twrp and that's pretty mutch everything what is on my phone..
i wiped my phone before installing the new rom.. and now i'm not able to get past my bootscreen please could anyone help me?
im sure there are a couple more phones like this ohh btw i have a "HTC One X +".
:angel:
If your bootloader says relocked, you won't be able to not a custom kernel. What are you trying to do specifically?
Sent from my HTC One X+ using xda app-developers app
santinobonotaa said:
i have the same problem, stuck in here for .. 2 mabey 3 months...
here is some info:
hboot:1.40.0000(*** unlocked ***)
cid:htc_e11
s-on
enrc2b_u
i have installed twrp and that's pretty mutch everything what is on my phone..
i wiped my phone before installing the new rom.. and now i'm not able to get past my bootscreen please could anyone help me?
im sure there are a couple more phones like this ohh btw i have a "HTC One X +".
:angel:
Click to expand...
Click to collapse
Did you install the boot.img that came within the rom ? to help you we need more exact steps .
No guys I just used the RUU to return it to stock, relocked the bootloader and have used the phone for 3 months as is without any problems and for some godforsaken reason its now stuck in a bootloop and all i want to do is use my phone like normal again.
Hboot 1.35
radio 3.1204.168.32
additional help required
ethanon said:
Did you install the boot.img that came within the rom ? to help you we need more exact steps .
Click to expand...
Click to collapse
heey,
i used the next steps but all failed
cmd.exe -> adb toolkit
fastboot(usb)(on phone)
(on computer)
fastboot flash cm10.0 (sorry i was desperate, but it failed)
adb sideload cm10.0 (also failed)(error code: E:Error executiong updater binary in zip '/data/media/sideload.zip')
im using team win recovery project v2.6.3.0
phone is always above 60%
any questions?
just ask
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
also is it possible to use an OTG cable to access a usb stick? that would be a very nice solution for phones that cannot change theyre sd card or there battery.
similar issue, yet to find a solution
Hi all,
I'm having a very similar issue to the one here. I have the HTC One X+ on AT&T. I had never rooted this phone. I got the OTA update in January, which seemed to go pretty smoothly. The phone was slow for a few days until I got all the apps updated and then was starting to be normal again. Every now and then it would hang and then I'd force restart and it would stick on the bootscreen until I restarted again. One day, however, it did this and then never exited the bootscreen. Got into the bootloader menu and did factory reset in hboot mode, which did nothing. Then I find out it wouldn't do anything because the settings of the phone were set to Fastboot and that needs to be unchecked for factory reset to work. But I can't get into the phone to change that, so I started looking through many many forums here at XDA and trying solutions to problems that were as close to mine as I could find. ...most people have this problem when first attempting the update or when putting on a custom rom, or using a different HTC phone.
So, I've learned quite a bit about flashing roms and the architecture of my phone, but not enough to fix this or to know where I may have may things worse. Here is a summary of what I attempted (all with battery >50% and HTC Sync has been installed on my computer--although the computer never recognizes the device and says driver install failed every phone reboot):
First was to get adb and fastboot and clear the cache
Then I ran the RUU: RUU_EVITARE_UL_JB_50_S_Cingular_US_2.15.502.1_Radio_2.21.5517.15_18.27.11.35L_release_341689_signed_0220
It claimed it updated my phone from 2.15.502 to 2.15.502 and then hung on the bootscreen. (it did CHANGE the bootscreen logo to a simple HTC)
Older RUUs return an error that they are not the right RUU for my phone.
Next, I attempted to directly flash the recovery_signed and boot.img from the zipped roms that were in the TEMP folder after initializing the RUU (according to one forum thread), but this method required a system.img to exist and it does not.
I flashed TWRP recovery (v2.6.3.0) and can access that just fine. The entire phone is wiped. There is no OS. I cannot mount the SD card.
Most recently, I attempted to sideload the zipped ROM from the RUU (http://forum.xda-developers.com/showthread.php?t=2317986). It failed (unable to find partition size..unable to mount anything), so I used adb push to put the rom onto the SD card. Install from TWRP also failed. Unable to find/mount anything. That's where I am now.
*** UNLOCKED ***
EVITARE_UL PVT SHIP S-ON RL
HBOOT-1.73.0000
CPLD-None
MICROP-None
RADIO-SSD:2.21.5517.15
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM TYPE : MDM9215M
Sep 30 2013, 17:16:15
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.73.0000
(bootloader) version-baseband: SSD:2.21.5517.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.15.502.1
(bootloader) serialno: ***********
(bootloader) imei: ***************
(bootloader) product: evitare_ul
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PM6310000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4160mV
(bootloader) devpower: 93
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
Thanks.
mabey case closed?!
heeyy,, i fixed my HOX+ (HTC ONE+) with the next steps:
download this rom, boot.img , recovery and gapps. ---> dropboxbox /sh/kzgnoqmfstuc53z/IEof1v7nL3
make sure you have the latest sdk tools
open the SDK Manager.exe only install: platform tools
once installed open it.. search cmd.exe on your computer. (easiest is windows-key -> type: cmd.exe -> right click -> copy) and paste it in the platform tools folder.
open cmd.exe in the platform tools folder, from here we go to the phone
now connect your phone and computer by cable.
now start your HOX+ in fastboot mode, press power button with volume-down button at the same time (make sure you unlocked your HOX+ on the htcdev website.)
now make sure the red text on your phone is: fastboot usb
and we go back to our laptop.
go to the cmd program, type the following: fastboot flash recovery [recovery.img*]
* drag the recovery of the downloaded recovery.img to the cmd
now when you flashed the recovery.. now lets flash the boot...
type the following: fastboot flash boot [boot.img**]
** drag the boot of the downloaded boot.img to the cmd
now reboot the phone in recovery mode.
go back to your cmd.
and type again the following:adb devices <-- and make sure your device is in there otherwise ther's a problem
and than:adb push [cm10.zip***]
*** drag the cm10 for the downloaded cm10 to the cmd
and wait.....
and wait more...
and when it's completed..
go to your phone and install zip from sdcard.
search: cm10 blablabla and install .. and now reboot ^^
im not a professional.. i just shared my solution with you and i hope it helped your bootlooped phone too!!
and if someone could help me with upgrading cm10 to a custom rom 4.4 (kitkat) with a detailed description would it encourage me to help other people and it would even encourage me to study for application devellopment <3
---------- Post added at 06:24 PM ---------- Previous post was at 06:09 PM ----------
sorry for dropbox link .. :$
santinobonotaa said:
heeyy,, i fixed my HOX+ (HTC ONE+) with the next steps:
download this rom, boot.img , recovery and gapps. ---> dropboxbox /sh/kzgnoqmfstuc53z/IEof1v7nL3
make sure you have the latest sdk tools
open the SDK Manager.exe only install: platform tools
once installed open it.. search cmd.exe on your computer. (easiest is windows-key -> type: cmd.exe -> right click -> copy) and paste it in the platform tools folder.
open cmd.exe in the platform tools folder, from here we go to the phone
now connect your phone and computer by cable.
now start your HOX+ in fastboot mode, press power button with volume-down button at the same time (make sure you unlocked your HOX+ on the htcdev website.)
now make sure the red text on your phone is: fastboot usb
and we go back to our laptop.
go to the cmd program, type the following: fastboot flash recovery [recovery.img*]
* drag the recovery of the downloaded recovery.img to the cmd
now when you flashed the recovery.. now lets flash the boot...
type the following: fastboot flash boot [boot.img**]
** drag the boot of the downloaded boot.img to the cmd
now reboot the phone in recovery mode.
go back to your cmd.
and type again the following:adb devices <-- and make sure your device is in there otherwise ther's a problem
and than:adb push [cm10.zip***]
*** drag the cm10 for the downloaded cm10 to the cmd
and wait.....
and wait more...
and when it's completed..
go to your phone and install zip from sdcard.
search: cm10 blablabla and install .. and now reboot ^^
im not a professional.. i just shared my solution with you and i hope it helped your bootlooped phone too!!
and if someone could help me with upgrading cm10 to a custom rom 4.4 (kitkat) with a detailed description would it encourage me to help other people and it would even encourage me to study for application devellopment <3
Click to expand...
Click to collapse
Still stuck
TWRP wouldn't let me sideload and returned many "unable to mount" errors.
I put CWM on (the one rated for my phone) and it also gives the "can't mount" errors (/system, /data, /cache, etc.)
But I was able to sideload the Elegancia 6.2 rom onto the phone. It immediately started the install after that, but hangs at some early % (9.07 one time, now 13.07%).
These are subsequent attempts. The first time I wasn't staring at the phone and it appeared to have installed, but rebooted into HTC screen and stayed there. I had already flashed the kernel, but did so again with no luck.
CWM still says it can't mount /cache/recovery, etc.
Again, at a loss.
mrg209 said:
Hi all,
I'm having a very similar issue to the one here. I have the HTC One X+ on AT&T. I had never rooted this phone. I got the OTA update in January, which seemed to go pretty smoothly. The phone was slow for a few days until I got all the apps updated and then was starting to be normal again. Every now and then it would hang and then I'd force restart and it would stick on the bootscreen until I restarted again. One day, however, it did this and then never exited the bootscreen. Got into the bootloader menu and did factory reset in hboot mode, which did nothing. Then I find out it wouldn't do anything because the settings of the phone were set to Fastboot and that needs to be unchecked for factory reset to work. But I can't get into the phone to change that, so I started looking through many many forums here at XDA and trying solutions to problems that were as close to mine as I could find. ...most people have this problem when first attempting the update or when putting on a custom rom, or using a different HTC phone.
So, I've learned quite a bit about flashing roms and the architecture of my phone, but not enough to fix this or to know where I may have may things worse. Here is a summary of what I attempted (all with battery >50% and HTC Sync has been installed on my computer--although the computer never recognizes the device and says driver install failed every phone reboot):
First was to get adb and fastboot and clear the cache
Then I ran the RUU: RUU_EVITARE_UL_JB_50_S_Cingular_US_2.15.502.1_Radio_2.21.5517.15_18.27.11.35L_release_341689_signed_0220
It claimed it updated my phone from 2.15.502 to 2.15.502 and then hung on the bootscreen. (it did CHANGE the bootscreen logo to a simple HTC)
Older RUUs return an error that they are not the right RUU for my phone.
Next, I attempted to directly flash the recovery_signed and boot.img from the zipped roms that were in the TEMP folder after initializing the RUU (according to one forum thread), but this method required a system.img to exist and it does not.
I flashed TWRP recovery (v2.6.3.0) and can access that just fine. The entire phone is wiped. There is no OS. I cannot mount the SD card.
Most recently, I attempted to sideload the zipped ROM from the RUU (http://forum.xda-developers.com/showthread.php?t=2317986). It failed (unable to find partition size..unable to mount anything), so I used adb push to put the rom onto the SD card. Install from TWRP also failed. Unable to find/mount anything. That's where I am now.
*** UNLOCKED ***
EVITARE_UL PVT SHIP S-ON RL
HBOOT-1.73.0000
CPLD-None
MICROP-None
RADIO-SSD:2.21.5517.15
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM TYPE : MDM9215M
Sep 30 2013, 17:16:15
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.73.0000
(bootloader) version-baseband: SSD:2.21.5517.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.15.502.1
(bootloader) serialno: ***********
(bootloader) imei: ***************
(bootloader) product: evitare_ul
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PM6310000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4160mV
(bootloader) devpower: 93
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
Thanks.
Click to expand...
Click to collapse
have you solved the problem ?
Unsolved
mobileplazza said:
have you solved the problem ?
Click to expand...
Click to collapse
No, I didn't solve it. I ran out of time (had a child) and got the Galaxy S5. But I still have the HTC and want to fix it when I have time to work on it again.
Hello friends, recently got an M8 Att, its already S-Off, BL Unlocked, Tried CIDs BS_US001, BS_US002 and Super CID 11111111 tried to install UL/DEV Ruu from HTC dev site but alwasys got error 155.
Any suggestion or what am i doing wrong? Thanks in advance.
My getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.28.502.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT4xxxxxxxxxxx
(bootloader) imei: 35xxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(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: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Which RUU are you trying to flash? If it's the Sense 7/ Marshmallow RUU then you need to first flash 6.x firmware. I found the same exact version as in the name of the RUU and flashed that first then the RUU flashed without a problem.
Sent from my Nexus 5 using Tapatalk
Hey thanks for your reply, yep I'm trying to flash marshmallow ruu because is the only one I found, where can I found such 6.X firmware? Or how can get it?
firultd said:
Hey thanks for your reply, yep I'm trying to flash marshmallow ruu because is the only one I found, where can I found such 6.X firmware? Or how can get it?
Click to expand...
Click to collapse
Search Google for 6.12.1540.4 firmware. I used the one in the first result uploaded by Einwod.
Flash that via fastboot oem rebootRUU.
Twice. It will fail the first time, wait about a minute for the bootloader to reload and flash it again. Don't unplug your phone at all. Once you successfully flash the firmware, do fastboot reboot-bootloader to get back into fastboot, then you should be able to flash the RUU
Sent from my Nexus 5 using Tapatalk
What happens in case of any ruu installation error? phone won't boot right? Can flash att stock run to recover device? Don't wanna end with a brick
Which error? Are you familiar with fastboot at all? And HTC oem commands? I take no responsibility for your flashing but what I posted worked fine for me.
Sent from my Nexus 5 using Tapatalk
firultd said:
What happens in case of any ruu installation error? phone won't boot right? Can flash att stock run to recover device? Don't wanna end with a brick
Click to expand...
Click to collapse
Depends on the error. If the RUU errors out before it actually installs anything, your phone will probably boot normally. But if it partially installs, then an error, it may be a no-boot situation.
Yes, in most cases if your phone won't boot after an RUU error, going back to the AT&T RUU should get your phone working again. But if you actually were successful in updating (even partially) to MM firmware, you may need to flash LP firmware before the LP RUU will work.
Not sure why, but it seems to be a glitch with the MM RUU. To go from LP>MM you need to flash the MM firmware, then RUU. And MM>LP the vice versa is also true, you may need to flash LP firmware in order for the LP RUU to work properly.
Yes i personally do boot loader unlock s -off and all that stuff. Don't worry I know that all responsibility is mine. I mean if after flashing firmware ruu still give an error obviously device will not but isn't it? In that case I still can flash att 5.0 stock ruu?
redpoint73 said:
Depends on the error. If the RUU errors out before it actually installs anything, your phone will probably boot normally. But if it partially installs, then an error, it may be a no-boot situation.
Yes, in most cases if your phone won't boot after an RUU error, going back to the AT&T RUU should get your phone working again. But if you actually were successful in updating (even partially) to MM firmware, you may need to flash LP firmware before the LP RUU will work.
Not sure why, but it seems to be a glitch with the MM RUU. To go from LP>MM you need to flash the MM firmware, then RUU. And MM>LP the vice versa is also true, you may need to flash LP firmware in order for the LP RUU to work properly.
Click to expand...
Click to collapse
OK. Very clear explanation that's give me a better look of the situation. Will keep in mind and try. Thank s a lot.
So now that i have a real keyboard in front of me....
I had very similar issue as you just two days ago where I have an AT&T Branded M8 that is S-Off and had an unlocked bootloader and superCID and I was not able to flash any RUU besides the AT&T one. Although I didn't investigate a lot into why the other Dev RUUs (earlier versions) didn't flash, I was beating my head against the wall trying to get the newest Marshmallow Dev RUU to flash.
Since you are trying to flash an HTC rom, which is signed by HTC the zip in the RUU has to be decrypted with the correct key from HTC. I believe (I'm not an expert on this) the key is embedded into HBOOT. HTC changed the encryption key sometime ago so when you use a firmware that preceeds the key change, the HBOOT will not be able to decrypt the rom.zip file and it fails.
By flashing the firmware I mentioned earlier, it has the correct key to decrypt the zip in the RUU and flash it.
The steps that I followed to get my phone converted are below. The only assumption I am making is that you are able to get into fastboot mode and you have a working knowledge of fastboot commands on a Windows PC.
1. Boot phone into fastboot mode
2. PC command: fastboot oem rebootRUU (Puts the phone into HTC RUU mode)
3. PC command: fastboot flash zip firmware-6.12.1540.4.zip (Flashes the firmware onto the phone)
4. The above command will fail with: FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Wait about a minute then...
5. PC command: fastboot flash zip firmware-6.12.1540.4.zip (Flashes the firmware onto the phone again)
6. PC command: fastboot reboot-bootloader (Restarts the bootloader)
7. At this point your phone should be ready to accept the Dev RUU RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe
8. Launch the RUU on the PC and follow the steps in the RUU Instructions to flash the phone.
9. After it successfully flashes the RUU it will reboot the phone and start optimizing the apps...and then it should drop you into the Welcome screen.
Now, the bricking your phone bit....You can read this thread about the errors you can get and how dangerous they are.
psychephylax said:
So now that i have a real keyboard in front of me....
I had very similar issue as you just two days ago where I have an AT&T Branded M8 that is S-Off and had an unlocked bootloader and superCID and I was not able to flash any RUU besides the AT&T one. Although I didn't investigate a lot into why the other Dev RUUs (earlier versions) didn't flash, I was beating my head against the wall trying to get the newest Marshmallow Dev RUU to flash.
Since you are trying to flash an HTC rom, which is signed by HTC the zip in the RUU has to be decrypted with the correct key from HTC. I believe (I'm not an expert on this) the key is embedded into HBOOT. HTC changed the encryption key sometime ago so when you use a firmware that preceeds the key change, the HBOOT will not be able to decrypt the rom.zip file and it fails.
By flashing the firmware I mentioned earlier, it has the correct key to decrypt the zip in the RUU and flash it.
The steps that I followed to get my phone converted are below. The only assumption I am making is that you are able to get into fastboot mode and you have a working knowledge of fastboot commands on a Windows PC.
1. Boot phone into fastboot mode
2. PC command: fastboot oem rebootRUU (Puts the phone into HTC RUU mode)
3. PC command: fastboot flash zip firmware-6.12.1540.4.zip (Flashes the firmware onto the phone)
4. The above command will fail with: FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Wait about a minute then...
5. PC command: fastboot flash zip firmware-6.12.1540.4.zip (Flashes the firmware onto the phone again)
6. PC command: fastboot reboot-bootloader (Restarts the bootloader)
7. At this point your phone should be ready to accept the Dev RUU RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe
8. Launch the RUU on the PC and follow the steps in the RUU Instructions to flash the phone.
9. After it successfully flashes the RUU it will reboot the phone and start optimizing the apps...and then it should drop you into the Welcome screen.
Now, the bricking your phone bit....You can read this thread about the errors you can get and how dangerous they are.
Click to expand...
Click to collapse
Well, lets do it, just give me some hours to backup and will try and post results, again thanks for your time.
A tiny question before proceed, firmware zip file is 30.88 MB size? Its the right one? feel like its too small
firultd said:
A tiny question before proceed, firmware zip file is 30.88 MB size? Its the right one? feel like its too small
Click to expand...
Click to collapse
Yeah, it's about 30mb (31626 KB)
Here's the md5 sum from my file: b5add816536334711fb2baa6e8a4d134
HAve no words to describe the happines to see my phone just like a real dev edition, many thanks to all of you for your time. Whole process was right and phone is working awesome.
Glad you got it working.
Sent from my Redmi Note 2 using Tapatalk
firultd said:
A tiny question before proceed, firmware zip file is 30.88 MB size? Its the right one? feel like its too small
Click to expand...
Click to collapse
Note that firmware.zip only contains a subset of partitions including hboot, radio, kernel, recovery, WiFi, Bluetooth, Audio and a few others. It doesn't contain the ROM, which is a much larger file (1.5 GB or so); nor is it a full RUU or ROM.zip, etc.
Firmware is important, but not a large file.
Any harm in flashing the 6.12.1540.4 but staying on Lollipop?
I don't know, but why would you want to stay on lollipop?
Sent from my Redmi Note 2 using Tapatalk