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.
Related
Hey guys, I think I might've bricked my Amaze
I was flashing a new ROM with CWM, used the superwipe script that X posted and formatted /cache, /data, /system. After the superwipe script, it reboots back into recovery, but when it tried to, it just gave me the green htc logo.
So I went into the bootloader and tried to get back into recovery through there, but it still just gave me the green htc logo. I then tried to install CWM again through the fastboot flash recovery method which was "successful" according to this:
c:\Android>fastboot flash recovery recovery-cwm-ruby-5.5.0.4.img
sending 'recovery' (5740 KB)...
OKAY [ 1.238s]
writing 'recovery'...
OKAY [ 8.469s]
finished. total time: 9.708s
However, everytime I try to get into recovery, it's the same green htc logo!
I formatted /system and /data, I don't think I have a ROM to normally boot to.
I tried to use every other method to reinstall CWM, but it just isn't getting past that htc logo screen.
I've tried using fastboot erase recovery to see if I could clean that partition, but it gave me this:
c:\Android>fastboot erase recovery
erasing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.003s
I've also tried relocking my bootloader and unlocking again, after re-unlocking, nothing changed
Lastly, I tried "fastboot boot recovery-cwm-ruby-5.5.0.4.img", which supposedly downloads the image file and boots right into it, but that also didn't work.
I'm pretty screwed if I can't get this device to work again since I'll be left with a $500+ brick and no phone to use, so if anyone can shed some light as to what I can try to get this thing working again, please do!
Edit: not sure if this will help, but this is my "fastboot getvar all":
c:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.90.0008
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.45.1500.2
(bootloader) serialno: (removed by me for privacy)
(bootloader) imei: (removed by me for privacy)
(bootloader) product: ruby
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH8511000
(bootloader) cidnum: GLOBA001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4145mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 2dad0f62
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Edit2: Phone came back to life, had to resort to relocking the boot loader and then reverting back to stock firmware.
Hate to suggest it but the same thing happened to me as well.
I didn't feel like messing around so I just used a PH85IMG.zip file and started over from scratch. I think it might be an issue with the wipe script but can't be sure.
Binary100100 said:
Hate to suggest it but the same thing happened to me as well.
I didn't feel like messing around so I just used a PH85IMG.zip file and started over from scratch. I think it might be an issue with the wipe script but can't be sure.
Click to expand...
Click to collapse
I'm downloading the Globalive RUU (since I'm with WIND) right now and it's going really slow... Hoping this will resurrect my Amaze
adslee said:
I'm downloading the Globalive RUU (since I'm with WIND) right now and it's going really slow... Hoping this will resurrect my Amaze
Click to expand...
Click to collapse
As long as you have access to fastboot you're phone isn't dead 99% of the time.
Binary100100 said:
As long as you have access to fastboot you're phone isn't dead 99% of the time.
Click to expand...
Click to collapse
And you're absolutely right!
I relocked my bootloader, finished downloading that stock firmware, and it booted back up to stock, phew!
Thanks a bunch for the suggestion there Binary, I was hoping for a more elegant solution than to revert back to stock, but I'm just thankful that I'm not sitting at home right now with a $500 brick
In case this happens to anyone else, I guess the surefire way to get things back up and running again is to relock the bootloader and go back to stock
adslee said:
And you're absolutely right!
I relocked my bootloader, finished downloading that stock firmware, and it booted back up to stock, phew!
Thanks a bunch for the suggestion there Binary, I was hoping for a more elegant solution than to revert back to stock, but I'm just thankful that I'm not sitting at home right now with a $500 brick
In case this happens to anyone else, I guess the surefire way to get things back up and running again is to relock the bootloader and go back to stock
Click to expand...
Click to collapse
Glad to help.
ALWAYS make backups. Preferably on your external storage space becomes sometimes those RUU files wipe your internal storage.
Seems like if two people have had this problem it might be safer to just use recovery to wipe the phone, then flash the Rom. That way there is no reboot and less of a chance of a soft brick.
Sent from my HTC_Amaze_4G using XDA App
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.
Ok, so somehow I've managed to screw this phone up royally. Any help would be greatly appreciated.
I just switched to Android from iPhone and I think I tried too much too fast.
I successfully followed the guide to convert my AT&T HTC One to a Google Play Edition. I got S-OFF and changed the CID to GOOGL001 and successfully got 4.4 up and running.
I'd been using that for a few months and decided I wanted to try the HTC Sense Stock Software 4.3 (being new to android I just kind of wanted to try it myself in addition to stock android) I've been through a ton of steps and attempts now that I won't bore you with, but here's where I'm at now:
I'm stuck in a bootloop. My phone will load to welcome and ask for a language and then reboots about 2 seconds later.
I can successfully get into fastboot and run commands against the device. If I flash a recovery, it seems to work for one or two boots and then it will crash and restart until I flash it again (tried with TWRP and CWM)
I am currently Tampered Unlocked but can perform fastboot oem lock and unlock. I have S-ON, HBOOT 1.54 and Radio 4T.
My goal is to go back to stock for this device with 4.3 and Sense, but since I stupidly did S-ON before I changed the CID I'm not able to run the RUU exe and since my phone is in a bootloop I don't know how to get root access to run rumrunner to S-OFF.
I've been researching and trying stuff for several days now with no luck and this forum seems to have the best advice of most that I've seen. Can anyone help? Thanks so much for your time!
I had a similar experience in which I completely removed android OS from the phone If u flash the HTC with TWRP and you are able to successfully enter the recovery... TWRP has under advance button and option called adb sideload.
basically download the Google edition that successfully ran your device and place it under the adb.exe folder.
Steps
On the phone
Access recoverty TWRP
go to advance
Click on adb sideload
Swipe to activate adb sideload
Connect phone to computer.
On computer
Go to run and enter cmd press enter
go to the folder where you have the adb.exe
and the command that you enter is adb sideload «filename.zip» press enter and let it work
Sent from my HTC One using xda app-developers app
TopoX84 said:
I had a similar experience in which I completely removed android OS from the phone If u flash the HTC with TWRP and you are able to successfully enter the recovery... TWRP has under advance button and option called adb sideload.
basically download the Google edition that successfully ran your device and place it under the adb.exe folder.
Steps
On the phone
Access recoverty TWRP
go to advance
Click on adb sideload
Swipe to activate adb sideload
Connect phone to computer.
On computer
Go to run and enter cmd press enter
go to the folder where you have the adb.exe
and the command that you enter is adb sideload «filename.zip» press enter and let it work
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply and info! Ok, took your advice and flashed TWRP 2.6.3.3 to recovery. (I can only boot to recovery when I'm unlocked, not sure if that matters or not)
I'm trying to send RUU-HTC_One_GE-4.4.2-3.62.1700.1.zip (Is that the correct file I should be using)
The sideload gets to 100% but then instantly fails when it tries to run on the device:
ADB Sideload Complete
Failed
Updating partition details...
E: Unable to mount '/cache
E: Unable to mount '/cache
E: Unable to mount '/cache
Starting ADB sideload feature...
Cancelling ADB sideload...
Starting ADB sideload feature
Installing '/data/media/0/sideload.zip...
Checking for MD5 file...
Skipping Md5 check: no MD5 file found.
I've tried a few different versions with similar results (same file pre rooted) and same thing happens.
Any thoughts on what I could be doing wrong (because I'm sure that it's me that's the problem here. )
Give this a try... At the bottom of the op thread it says if adb sideload fails....
http://forum.xda-developers.com/showthread.php?t=2318497
If the link above didn't work you might want to try pushing the Rom to the phone via adb push...
See link below.
http://forum.xda-developers.com/showpost.php?p=43674827&postcount=5
Sent from my HTC One using xda app-developers app
I'm able to push the zip file ok, but when I try to do "install zip" it fails again. I get error flashing zip Updating Partition Detials
Is there anyway for me to achieve s-off from where I am now? If I change my CID back to the AT&T HTC one and then relock and s-on I would be able to use the stock ruu exe, correct?
I would look for a stock Rom GPE since you changed the CID and your s-on
I would look for a 4.3 or 4.4 stock Rom... Make sure also that TWRP is the latest . And try again both steps above. if that doesn't work my inclination would be to flash the Rom via fastboot.
try using this ROM, when i had the issues with my HTC i used it to sideload or push and it worked flawlessly.
http://forum.xda-developers.com/showthread.php?t=2460035
CtrlAltDave said:
Is there anyway for me to achieve s-off from where I am now? If I change my CID back to the AT&T HTC one and then relock and s-on I would be able to use the stock ruu exe, correct?
Click to expand...
Click to collapse
You are correct to what you said unfortunately the only way for you to perform a s-off based on the information given is using rumrunner in which you need your device to boot completely to the OS
Sent from my HTC One using xda app-developers app
no reason to post one after other where i can edit using the computer
Thanks for all of your help and patience with me. I think this phone hates me. I get error flashing with every zip I throw at the phone. I get error flashing zip in TWRP and Installation aborted with CWM. Tried with 4.3 and 4.4 stock GPE rom. Same results if I sideload or push. I also get an error when i try to fastboot flash the same roms. 99 unknown fail when bootloader unlocked and 12 signature verify fail if bootloader locked. Both of these are using fastboot oem rebootRUU and then fastboot flash zip rom.zip.
I pasted my getvar all below thinking that might help. I noticed my version-main is blank as well. Could that be causing any problems?
C:\Users\dfarrar\Desktop>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s
I'm beyond frustrated at this point because I've spent so much time trying to get this working and I'm at a loss. That's what I get for messing around before I learned enough I guess. Thanks again for helping me out. I owe you!
here is mine...
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT*******
(bootloader) imei: *************
(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: 3756mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
the problem as i see it might be the cidnum and modelid, if you get a rom with both config it might be able to flash
CtrlAltDave said:
Thanks for all of your help and patience with me. I think this phone hates me. I get error flashing with every zip I throw at the phone. I get error flashing zip in TWRP and Installation aborted with CWM. Tried with 4.3 and 4.4 stock GPE rom. Same results if I sideload or push. I also get an error when i try to fastboot flash the same roms. 99 unknown fail when bootloader unlocked and 12 signature verify fail if bootloader locked. Both of these are using fastboot oem rebootRUU and then fastboot flash zip rom.zip.
I pasted my getvar all below thinking that might help. I noticed my version-main is blank as well. Could that be causing any problems?
C:\Users\dfarrar\Desktop>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s
I'm beyond frustrated at this point because I've spent so much time trying to get this working and I'm at a loss. That's what I get for messing around before I learned enough I guess. Thanks again for helping me out. I owe you!
Click to expand...
Click to collapse
try this rom out .... RUU-HTC_One_GE-2.14.1700.15
http://forum.xda-developers.com/showthread.php?t=2358781&page=112
http://forum.xda-developers.com/showthread.php?t=2570785&page=3
Same errors with that rom. Won't work through adb push with twrm or cwm. Won't work with sideload and won't work fastboot flash zip. Could I have permanently broken this thing?
CtrlAltDave said:
Same errors with that rom. Won't work through adb push with twrm or cwm. Won't work with sideload and won't work fastboot flash zip. Could I have permanently broken this thing?
Click to expand...
Click to collapse
no it's not broken ...
Flash this stock recovery and also change your CID back to AT&T
fastboot oem writecid CWS__001
then
http://d-h.st/2Lr
fastboot flash recovery recovery_signed.img
Next boot into stock recovery / factory reset
this is done from the bootloader using the volume up/down to navigate and Power button to select. After you choose recovery you have to push vol up and power to see the factory reset option.
When it's done reflash TWRP recovery and try and sideload a new Rom
I recommend >> Download - ARHD 31.6
Would he be able to change back to the AT&T cod having s-on??? As far as I know you can only change with s-on only when you have supercid in place
Sent from my HTC One using xda app-developers app
TopoX84 said:
Would he be able to change back to the AT&T cod having s-on??? As far as I know you can only change with s-on only when you have supercid in place
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
yeah your right he need to get back s-off also after he gets ARHD 31.6 running
ARHD did the trick! For some reason none of the stock GPE roms would load but this one worked flawlessly. I was able to sideload and install, get supersu and then use rumrunner to get back to s-off. Plus this rom gives me everything that I wanted. I can keep kitkat and still get sense and zoe and whatnot. Never mind going back to stock, I think I'll stick with this for a while and try it out. Thanks so much for your help everyone!
To be in the safe side you might want to consider changing the cid to supercid...
Sent from my HTC One using xda app-developers app
CtrlAltDave said:
ARHD did the trick! For some reason none of the stock GPE roms would load but this one worked flawlessly. I was able to sideload and install, get supersu and then use rumrunner to get back to s-off. Plus this rom gives me everything that I wanted. I can keep kitkat and still get sense and zoe and whatnot. Never mind going back to stock, I think I'll stick with this for a while and try it out. Thanks so much for your help everyone!
Click to expand...
Click to collapse
Good to here it all worked out for you
and remember STAY S-OFF
SuperCID and S-Off for life. Thanks again!
Thanks All
Don't know if any of you will check back on this ancient post, but I read around for a long time and this totally ended up working for me. So belated thanks.
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.
I'm trying to update my phone using RUU, but it seems to be stuck on 0/7 Sending. It's been there for over an hour now. "adb devices" doesn't return anything, but "fastboot devices" returns HTxxxxxxxxxx fastboot.
Would unplugging the phone at this stage cause any damage? Searching around I saw somebody mention USB 3.0 can have some issues with RUU. I'd like to try it in a 2.0 port, but I"m not sure if it's safe to unplug (doesn't look like its done anything to the phone yet, but I figured it would be safer to ask here first).
Any other suggestions are welcome as well. Not sure what to do here.
edit:
By the way, phone has a stock rom, stock recovery, and the bootloader is relocked
Arsencon said:
I'm trying to update my phone using RUU, but it seems to be stuck on 0/7 Sending. It's been there for over an hour now. "adb devices" doesn't return anything, but "fastboot devices" returns HTxxxxxxxxxx fastboot.
Would unplugging the phone at this stage cause any damage? Searching around I saw somebody mention USB 3.0 can have some issues with RUU. I'd like to try it in a 2.0 port, but I"m not sure if it's safe to unplug (doesn't look like its done anything to the phone yet, but I figured it would be safer to ask here first).
Any other suggestions are welcome as well. Not sure what to do here.
edit:
By the way, phone has a stock rom, stock recovery, and the bootloader is relocked
Click to expand...
Click to collapse
This has been happening to me for forever. I've unplugged my phone and restarted process with no problems, BUT DO THAT AT YOUR OWN RISK!
I'm sure you've probably already decided on one action or another by this point (as your post was from yesterday). But I agree with the above, its at your own risk; but if you ask me what I would do, I would just unplug it and start again (and think I've done so in the past).
Not sure if killing the RUU process on the PC, or restarting the computer is any better or not. I'd think that if it were actually sending or installing something to the phone (which it doesn't seem to be) it would be just as "bad" as unplugging the phone.
I had the same problem. I'm not suggesting you do this but this is what I did. When it got stuck on 0/7 I unplugged it. Restarted the phone. Backed up everything using twrp . Rebooted. Then I ran the ruu with the phone on and not fast through fastboot usb. If you have another emulator on your pc like bluestacks turn it off (bluestack for me is c:/programfiles/bluestacke/quit.exe to turn off). My boot loader is unlocked but I dont know if that matters.
Sent from my HTC One_M8 using XDA Free mobile app
HInstinct said:
My boot loader is unlocked but I dont know if that matters.
Click to expand...
Click to collapse
Bootloader unlocked is okay (RUU will run) if you have s-off.
If s-on, the bootloader needs to be RELOCKED or LOCKED.
Arsencon said:
I'm trying to update my phone using RUU, but it seems to be stuck on 0/7 Sending. It's been there for over an hour now. "adb devices" doesn't return anything, but "fastboot devices" returns HTxxxxxxxxxx fastboot.
Would unplugging the phone at this stage cause any damage? Searching around I saw somebody mention USB 3.0 can have some issues with RUU. I'd like to try it in a 2.0 port, but I"m not sure if it's safe to unplug (doesn't look like its done anything to the phone yet, but I figured it would be safer to ask here first).
Any other suggestions are welcome as well. Not sure what to do here.
edit:
By the way, phone has a stock rom, stock recovery, and the bootloader is relocked
Click to expand...
Click to collapse
Same issue i have faced while updating . Just I have killed the tasks of RUU in Task Manager , unplugged and plugged again and restarted RUU update. RUU update done smoothly there after..
i have the same problum but when i unplug the usb cable the device has restard itself but no any problum here usman engeneer
(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: 6.20.502.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT45SWM06618
(bootloader) imei: XXXXXXXXXXXXXXX ( Deleted)
(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: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.125s
Bootloader - Unlocked
Recovery - TWRP
Rooted - Yes
Custom ROM - Resurrection Remis 5.8.5 Final
if want to go back to stock what is procedure
i have below RUU
RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502. 5_combined.exe
can i run this exe after relock the bootloader?
safrassm said:
if want to go back to stock what is procedure
i have below RUU
RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502. 5_combined.exe
can i run this exe after relock the bootloader?
Click to expand...
Click to collapse
Not related to the topic of the thread.
I'll answer you somewhere else . . . in one of the 10 threads you spammed. And now you see why cross posting is against the rules.