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
Related
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.
Guys,
Usually I am pretty good at this stuff, but I am banging my head against the wall trying to figure out how to get an RUU to flash to get stock AT&T firmware back on this HTC One I have to send back for warranty exhange. Keep getting Error 155 on the RUU.
Thanks,
Y2J
y2jdmbfan said:
Guys,
Usually I am pretty good at this stuff, but I am banging my head against the wall trying to figure out how to get an RUU to flash to get stock AT&T firmware back on this HTC One I have to send back for warranty exhange. Keep getting Error 155 on the RUU.
Thanks,
Y2J
Click to expand...
Click to collapse
If it is an AT&T phone then just take it to an AT&T service center. They will exchange it even if it has been rooted, s-offed/on, different ROM, it does not matter. HTC will not touch it but AT&T has no issues. You do not need to go through all the trouble of changing it back. Read later post in this thread
http://forum.xda-developers.com/showthread.php?t=2333894
It confirms what i am saying...
Solarenemy68 said:
If it is an AT&T phone then just take it to an AT&T service center. They will exchange it even if it has been rooted, s-offed/on, different ROM, it does not matter. HTC will not touch it but AT&T has no issues. You do not need to go through all the trouble of changing it back. Read later post in this thread
http://forum.xda-developers.com/showthread.php?t=2333894
It confirms what i am saying...
Click to expand...
Click to collapse
Unfortunately I already have the replacement device from HTC...
Just flash an ATT stock rom, then restore the stock recovery. Done.
cschmitt said:
Just flash an ATT stock rom, then restore the stock recovery. Done.
Click to expand...
Click to collapse
Via RUU? I've tried a bunch of times with the RUU's that are out there and keep getting error 155.
y2jdmbfan said:
Via RUU? I've tried a bunch of times with the RUU's that are out there and keep getting error 155.
Click to expand...
Click to collapse
No, via CWM/TWRP like this rom. Then flash the stock recovery in fastboot pulled from the 4.18.502.7 firmware.zip from here.
cschmitt said:
No, via CWM/TWRP like this rom. Then flash the stock recovery in fastboot pulled from the 4.18.502.7 firmware.zip from here.
Click to expand...
Click to collapse
Where do I get the stock recovery? Not sure which file in the list of the link you provided has the recovery.img.
Thanks!
y2jdmbfan said:
Where do I get the stock recovery? Not sure which file in the list of the link you provided has the recovery.img.
Thanks!
Click to expand...
Click to collapse
Here's the signed firmware.zip from the OTA: firmware_4.18.502.7.zip
You can flash it in fastboot with
Code:
fastboot oem rebootRUU
fastboot flash zip firmware_4.18.502.7.zip
fastboot flash zip firmware_4.18.502.7.zip (yes, twice!)
fastboot erase cache
fastboot reboot
This will give you the stock recovery, radio, hboot, etc.
cschmitt said:
Here's the signed firmware.zip from the OTA: firmware_4.18.502.7.zip
You can flash it in fastboot with
Code:
fastboot oem rebootRUU
fastboot flash zip firmware_4.18.502.7.zip
fastboot flash zip firmware_4.18.502.7.zip (yes, twice!)
fastboot erase cache
fastboot reboot
This will give you the stock recovery, radio, hboot, etc.
Click to expand...
Click to collapse
Now I am getting this error...I am S-On BTW if that makes a difference...
C:\platform-tools>fastboot flash zip firmware_4.18.502.7.zip
target reported max download size of 1514139648 bytes
sending 'zip' (47880 KB)...
OKAY [ 3.170s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 3.415s
Post the output of fastboot getvar all minus IMEI and S/N.
cschmitt said:
Post the output of fastboot getvar all minus IMEI and S/N.
Click to expand...
Click to collapse
C:\platform-tools>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.8
(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: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4278mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.069s
I think the issue is that you can't downgrade firmware from 4.19 to 4.18 with s-on. Was the phone s-off at one time?
cschmitt said:
I think the issue is that you can't downgrade firmware from 4.19 to 4.18 with s-on. Was the phone s-off at one time?
Click to expand...
Click to collapse
Yes it was. I accidentally put back s-on before I flashed the RUU. The phone had s-off and a custom software when I purchased it. The phone was acting up so I called HTC and got an advanced replacement and already have the replacement. I wanted to flash back to a stock firmware and remove s-off and lock the bootloader before I send the old phone back to HTC.
Unless you are willing to s-off again you're stuck with that firmware. The stock recovery can be pulled from the zip and flashed separately with fastboot though.
cschmitt said:
Unless you are willing to s-off again you're stuck with that firmware. The stock recovery can be pulled from the zip and flashed separately with fastboot though.
Click to expand...
Click to collapse
Oh I would s-off again no problem, but I can't get rumrunner or firewater to work...Any hints would be great based on the getvar I posted above.
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
ld power for 60 seconds !!
=========================================================================
preparing, one moment
The first bottle is open
chugging..........
C:\platform-tools>
Anyone have any ideas to get firewater working?
I have flashed Android Revolution HD 52.0 and then tried to do firewater, but it kicks me back to the command prompt after the initial chugging...
Hey everyone! I'm having issues booting my phone up. It might be bricked because one night my phone was working and the next morning it wouldn't boot at all after having not made any changes. I've messed around with it a lot, installing and wiping things. Anyway, I'd just like to make sure I've exhausted all attempts at getting the thing to boot again.
I am S-On, and have tried to use rumrunner to get s-off but was getting an error saying no adb connection. I wasn't able to turn off fastboot as instructed since I can't boot, but I have been able to run some adb commands. I get error: device not found sometimes and error: closed others. I have been using the windroid toolkit. I have tried running the ruu exe (yes, I first relocked) but got an error 155 and my bootloader said "HBoot Version is older!" I have installed several OTA roms and they seem to install properly through the recovery (I have been using TWRP, CWM and amonRa) but then do not make it to home screen. I had some progress where I was initially getting stuck at the white HTC screen, after flashing a kernel, I think it was, I made it to the 4G LTE screen but then it hung up there.
Hmm, I've done a lot of searching and trying things, but hopefully yall can help! I appreciate your efforts either way
Here are my getvars from fastboot
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.28.0000
(bootloader) version-baseband: 2.23.10.0123r/2.23.10.0124r
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) product: vigor
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH9810000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4144mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: cecc19f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.498s
Thanks!
JMBush1007 said:
Hey everyone! I'm having issues booting my phone up. It might be bricked because one night my phone was working and the next morning it wouldn't boot at all after having not made any changes. I've messed around with it a lot, installing and wiping things. Anyway, I'd just like to make sure I've exhausted all attempts at getting the thing to boot again.
I am S-On, and have tried to use rumrunner to get s-off but was getting an error saying no adb connection. I wasn't able to turn off fastboot as instructed since I can't boot, but I have been able to run some adb commands. I get error: device not found sometimes and error: closed others. I have been using the windroid toolkit. I have tried running the ruu exe (yes, I first relocked) but got an error 155 and my bootloader said "HBoot Version is older!" I have installed several OTA roms and they seem to install properly through the recovery (I have been using TWRP, CWM and amonRa) but then do not make it to home screen. I had some progress where I was initially getting stuck at the white HTC screen, after flashing a kernel, I think it was, I made it to the 4G LTE screen but then it hung up there.
Hmm, I've done a lot of searching and trying things, but hopefully yall can help! I appreciate your efforts either way
Here are my getvars from fastboot
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.28.0000
(bootloader) version-baseband: 2.23.10.0123r/2.23.10.0124r
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) product: vigor
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH9810000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4144mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: cecc19f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.498s
Thanks!
Click to expand...
Click to collapse
You need to get it bootable before you can S-OFF with Rumrunner... Unlock the bootloader again, boot or flash your recovery of choice (TWRP/PhilZ/CWM), wipe EVERYTHING thoroughly, at least 3 times, then flash in Tachyon to get it up and working (if you flashed the recovery and started it from the phone, remember to manually push the boot.img with fastboot). Give it time to boot, the first boot can take 10+ minutes in some cases. Once it is booted and stable, then you can try to S-OFF again.
acejavelin said:
You need to get it bootable before you can S-OFF with Rumrunner... Unlock the bootloader again, boot or flash your recovery of choice (TWRP/PhilZ/CWM), wipe EVERYTHING thoroughly, at least 3 times, then flash in Tachyon to get it up and working (if you flashed the recovery and started it from the phone, remember to manually push the boot.img with fastboot). Give it time to boot, the first boot can take 10+ minutes in some cases. Once it is booted and stable, then you can try to S-OFF again.
Click to expand...
Click to collapse
Hi acejavelin, thanks for the reply!
So, I was finally able to get it to boot again.. I put evervolv on it and then ran rumrunner once I had it booted. After running and getting most of the way through rumrunner, I got stuck in another boot loop. It seemed like rumrunner corrupted it or something. I couldn't it to book back up at that point, but I am now showing s-off! Not sure if it's possible to be halfway s-off or showing s-off but not, but the rumrunner never finished it got to pouring (2)... so I don't know.
Right now, I have evervolv on again (after trying many others) and it seems to be somewhat stable. I'm thinking I have a hardware issue. Something seems to be faulty and only working half the time. I tried a few different RUUs, OTA global rooted roms, etc.. Tachyon, cleanrom 4.5 pro, plain andy, carbon, etc. I have also been using Cleanwipe 10x before flashing new roms. Everything is unstable, so unfortunately, like I said, it seems to be hardware.
I have another rezound that has a bad ESN because I thought it was stolen, til I found it months later. It looks difficult, but possible to change the ESN.. I was thinking I could just switch the ESN and MEIDs and use the other phone? Any other suggestions on how to isolate the issue or find some stability would be very much appreciated. Thanks for the help!
Glad you got your answer! Also, cloning your IMEI and ESN is illegal and a major criminal offense. I suggest you don't go down that route.
JMBush1007 said:
Hi acejavelin, thanks for the reply!
So, I was finally able to get it to boot again.. I put evervolv on it and then ran rumrunner once I had it booted. After running and getting most of the way through rumrunner, I got stuck in another boot loop. It seemed like rumrunner corrupted it or something. I couldn't it to book back up at that point, but I am now showing s-off! Not sure if it's possible to be halfway s-off or showing s-off but not, but the rumrunner never finished it got to pouring (2)... so I don't know.
Right now, I have evervolv on again (after trying many others) and it seems to be somewhat stable. I'm thinking I have a hardware issue. Something seems to be faulty and only working half the time. I tried a few different RUUs, OTA global rooted roms, etc.. Tachyon, cleanrom 4.5 pro, plain andy, carbon, etc. I have also been using Cleanwipe 10x before flashing new roms. Everything is unstable, so unfortunately, like I said, it seems to be hardware.
I have another rezound that has a bad ESN because I thought it was stolen, til I found it months later. It looks difficult, but possible to change the ESN.. I was thinking I could just switch the ESN and MEIDs and use the other phone? Any other suggestions on how to isolate the issue or find some stability would be very much appreciated. Thanks for the help!
Click to expand...
Click to collapse
The result you got with rumrunner is very common, not sure exactly what it corrupts (probably the boot partition) but it is common to for it to freeze/bootloop after going S-OFF, as long as it's S-OFF in the bootloader, it is S-OFF... there is no "kinda S-OFF". Just restore the backup you did before running rumrunner (you did a Nandroid first, right ) or reflash your ROM and Gapps, no worries, this is kinda normal.
As far as the "most stable" ROM, this seems to vary a lot on the person, configuration/apps, ROM, and hardware build, some ROMs are better than others under various conditions and trial and error is the only real way to find out. Some Rezounds just do not like KitKat, others don't like JellyBean, etc... so if are having lots of issues with one, try a different one. A few ROMs you didn't mention that I think are very good on the Rezound are EclipticRez Revamped v9 (this is the most stable non-stock ROM I tried) and Nils Business Sense that are both ICS based, Beanstalk and Talon are two really good under-rated JellyBean ROMs just remember that some JB ROMs can swap your internal and external storage around in mounts (they appear swapped when the phone is booted, this is not really a bug if you see it). But to be honest, if you are flashing http://forum.xda-developers.com/showthread.php?t=2260154 or gone through @REV3NT3CH's full downgrade/upgrade guide and are still having issues, it could very well be hardware issues.
And yes, @kcipopnevets is correct... ESN/MEID swapping is illegal, although I don't know how much of a "major criminal offense" it is. But generally it is considered fraudulent activity and a violation of your terms of service on your cellular plan as well.
Hello all,
I've been browsing the forums for a few days now trying to fix my issue, but nothing I have found seems to be of much help, so I have decided to register here myself and get some assistance directly.
So, I rooted my phone and flashed twrp and cyanogenmod. After several bugs and overall irritation, I have decided to just go back to stock recovery, ROM, etc. (After all, I am a mechanical engineer - software is not my forté.)
In attempting to unroot my device, however, it seems that I just messed things up even further.
Steps taken:
1) Rebooted device into fastboot
2) fastboot oem lock
3) Reboot into RUU mode (black screen w/ htc logo)
4) Ran RUU.exe
5) (bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 35.173s
At this point, I thought that maybe it was because I was still S-ON so I was going to place rumrunner on the virtual SD. Now my PC won't recognize my phone, so I don't know how to flash rumrunner to go to S-OFF or if that's even the correct next step. So basically, I have bootloader and twrp, and that's it.
>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35ZW915640
(bootloader) imei: 354439051027912
(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: 3658mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
Ok so I got into twrp to try and flash any ROM but data wouldn't mount.
I wiped data through twrp, which allowed me to mount data
From here I could have copied a ROM to my virtual SD and flashed through twrp, but decided to give the RUU a try again.
This time I got ERROR [155].
Checked to make sure I had the right RUU for my CID, which I do, but I'm going to try an older RUU instead.
Since RUU wasn't working, I decided just to place the CM ROM onto the virtual SD and flash it. Finally have a phone that boots up and is running CM. Better than a paper weight, but still not a stock HTC One...
MJGiuffre said:
Ok so I got into twrp to try and flash any ROM but data wouldn't mount.
I wiped data through twrp, which allowed me to mount data
From here I could have copied a ROM to my virtual SD and flashed through twrp, but decided to give the RUU a try again.
This time I got ERROR [155].
Checked to make sure I had the right RUU for my CID, which I do, but I'm going to try an older RUU instead.
Click to expand...
Click to collapse
wrong way
MJGiuffre said:
Since RUU wasn't working, I decided just to place the CM ROM onto the virtual SD and flash it. Finally have a phone that boots up and is running CM. Better than a paper weight, but still not a stock HTC One...
Click to expand...
Click to collapse
there is no ruu for your sofware, older one will not work its just how htc are made, try this ruu its the latest.( make sure you are not supercid before running it, it can mess up the phone) from your first post it looks like you are fine unless u changed it to supercid.
http://dl3.htc.com/application/RUU_...06_10.46.1718.01L_release_424933_signed_2.exe
it should work at least it worked on mine
---------- Post added at 03:07 PM ---------- Previous post was at 03:00 PM ----------
MJGiuffre said:
Since RUU wasn't working, I decided just to place the CM ROM onto the virtual SD and flash it. Finally have a phone that boots up and is running CM. Better than a paper weight, but still not a stock HTC One...
Click to expand...
Click to collapse
also u can try one of the guru resets that matches your software , or look for a stock unrooted nandroid for att htc one , u need the 5,12 sofware , older one may not work properly. also before runing a ruu make sure your bootloader is loked or relocked. good luck.
I was following this guide: http://forum.xda-developers.com/showthread.php?t=2497614
I did the first flash which is supposed to fail, when I did it the 2nd time it got stuck on the first step in the command window ((bootloader) [RUU]WP,rcdata,0). I waited a long time but had no choice but to close the command prompt. Now I'm stuck w/ a green progress bar and the silver htc logo. Am I bricked? fastboot recognizes the device as "???????"
Update: I got it to recognize the device again. I'm trying to flash RUU_M7_UL_K44_SENSE55_MR_BrightstarUS_WWE_4.19.1540.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_353887_signed_3, but it doesn't recognize my phone so I extracted rom.zip manually and am trying to flash it. I'm getting this error now when I try to flash the 2nd time:
Code:
"target reported max download size of 1528479744 bytes
sending 'zip' (206214 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.025s"
I'm currently stuck with the 4 triangles so until I manage to flash SOMETHING successfully I'm soft-bricked I guess.
Update 2: I extracted the zip again. It's a lot larger this time so I guess I got a bad zip last time. :-/ In any case the rom.zip is over 1.5 GB now and when I try to flash it I get this in the console and fastboot.exe stops responding:
Code:
target reported max download size of 1526722560 bytes
Invalid sparse file format at header magi
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: <snip>
(bootloader) imei: <snip>
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4074mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.115s
Perhaps someone can just point me in the right direction for a dev edition zip. Will this one work? http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb_50_brightstarus_wwe_1-29-1540-3-zip/
@clsA, You've helped me in the past. Perhaps you could point me in the right direction? I'm using the RUU executable you mentioned in my old thread, but since they weren't recognizing my phone I decided to extract the rom.zip. Unfortunately that doesn't appear to be working either as you can see above.
Dr3x1 said:
@clsA, You've helped me in the past. Perhaps you could point me in the right direction? I'm using the RUU executable you mentioned in my old thread, but since they weren't recognizing my phone I decided to extract the rom.zip. Unfortunately that doesn't appear to be working either as you can see above.
Click to expand...
Click to collapse
Are you looking to use the latest dev edition version or you abosulately want to flash this old one? You could update your firmware to 6.07.1540.2 (that will also get you out of RUU mode) and then flash the 7.17.1540.2 ruu and take the ota update to 7.17.1540.21.
alray said:
Are you looking to use the latest dev edition version or you abosulately want to flash this old one? You could update your firmware to 6.07.1540.2 (that will also get you out of RUU mode) and then flash the 7.17.1540.2 ruu and take the ota update to 7.17.1540.21.
Click to expand...
Click to collapse
o/ Thanks for the reply. I finally managed to get out of RUU mode, but not until I accidentally downgraded to Hboot 1.44 and could no longer communicate w/ the device ('cuz windows). After booting linux I managed to flash a Zip of M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.
I'm currently doing OTA updates. How far will I get with what I flashed? Can I get the latest? I won't be too upset if I can't, but it'd be nice.
Dr3x1 said:
o/ Thanks for the reply. I finally managed to get out of RUU mode, but not until I accidentally downgraded to Hboot 1.44 and could no longer communicate w/ the device ('cuz windows). After booting linux I managed to flash RUU Zip M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.
I'm currently doing OTA updates. How far will I get with what I flashed? Can I get the latest? I won't be too upset if I can't, but it'd be nice.
Click to expand...
Click to collapse
you will eventually get their with the OTA's but why not just jump to the 6.x RUU and update from their
@alray has all the files you need in his thread in his signature
clsA said:
you will eventually get their with the OTA's but why not just jump to the 6.x RUU and update from their
@alray has all the files you need in his thread in his signature
Click to expand...
Click to collapse
Thanks for the links. Hopefully it updates my firmware too so I can talk to my device w/ Windows again. If not I'll do it manually though. Appreciate the help again! ^_^
Doesn't look like the RUU.exe will work still. It recognizes my phone now but gets stuck on 0/5 sending... The ZIP is too large as well. Fastboot.exe crashes every time I try to flash it. Oh well. OTA updates it is I guess.
Dr3x1 said:
Doesn't look like the RUU.exe will work still. It recognizes my phone now but gets stuck on 0/5 sending... The ZIP is too large as well. Fastboot.exe crashes every time I try to flash it. Oh well. OTA updates it is I guess.
Click to expand...
Click to collapse
flash the firmware / then try the RUU