Hello everyone!
I have an AT&T HTC One that is S-Off, relocked, SuperCID, black HBoot 1.54, currently on ViperOne 2.7 with stock kernel. I've been trying for the past day and a half to get the 3.22.1540.1 Brightstar WWE to run so I could have it back to stock with the most current OS. I also want to fully convert it to a Developer's Edition phone as well. I thought that with SuperCID you could run any RUU but so far every single time it ends in an error. I also tried changing the CID to the Developer's Edition CID (BS_US001) and still came back with the same error. So here I am on the greatest place in the world for Android phone assistance and advice asking for help in getting my phone converted to a Developer's Edition and/or on the 3.22 RUU. Thanks in advance for any help.
P.S. I already did try to search like crazy for the answers to my questions.!
Well you may need a stock recovery to run an ruu.exe. And I'd recommend going back to super-cid and then running the ruu as well. Be sure you back up all your information that you do then wish to lose, as the ruu will format the entire phone.
Sent from my HTC One using Tapatalk 4
Willieumm said:
Hello everyone!
I have an AT&T HTC One that is S-Off, relocked, SuperCID, black HBoot 1.54, currently on ViperOne 2.7 with stock kernel. I've been trying for the past day and a half to get the 3.22.1540.1 Brightstar WWE to run so I could have it back to stock with the most current OS. I also want to fully convert it to a Developer's Edition phone as well. I thought that with SuperCID you could run any RUU but so far every single time it ends in an error. I also tried changing the CID to the Developer's Edition CID (BS_US001) and still came back with the same error. So here I am on the greatest place in the world for Android phone assistance and advice asking for help in getting my phone converted to a Developer's Edition and/or on the 3.22 RUU. Thanks in advance for any help.
P.S. I already did try to search like crazy for the answers to my questions.!
Click to expand...
Click to collapse
No need to relock boot loader because the developer edition comes by default unlocked. Unlock it to continue. You need to change your CID to 11111111 (super CID) and you need to flash the 1.44 hboot (I believe) the black hboot may be causing the problem.
Downgrade to the lowest firmware you can find for the Developers edition.
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
(Yes, twice.)
Check to be sure everything was successful.
fastboot reboot-bootloader
Make sure the bootloader is locked.
Run the ruu.
Let it do its thing.
Boot the phone and set it up.
Go to settings - about phone - software information - system update.
Allow it to download and update.
Repeatedly check for update until you reach 4.3
Sent from my HTC One using XDA Premium 4 mobile app
Hi there,
Did you get it work 3.22.1540.1 dev edition on your phone?, im still stuck in the same problem, got an HTC One AT&T, i got working the RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16.exe (dev edition), when i check for updates, there's an update of 17mb, after updating that one, i check again and found the 3.22.1540.1 OTA (around 550mb), i downloaded and agree to install it, but when reboot the phone, it got stuck in the HTC logo screen, did not go further, even trying to get into recovery, same thing, got stuck in HTC logo screen.
Another test i did, was installing RUU_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.exe and even the zip version, both of them install correctly but same problem, got stuck in HTC Logo screen, right now my phone is Unlocked bootloader, S-off with supercid (also tried the BS_US001 CID, same problem), hboot 1.55, is there any chance someone can help me with it? thanks a lot
leca27 said:
Hi there,
Did you get it work 3.22.1540.1 dev edition on your phone?, im still stuck in the same problem, got an HTC One AT&T, i got working the RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16.exe (dev edition), when i check for updates, there's an update of 17mb, after updating that one, i check again and found the 3.22.1540.1 OTA (around 550mb), i downloaded and agree to install it, but when reboot the phone, it got stuck in the HTC logo screen, did not go further, even trying to get into recovery, same thing, got stuck in HTC logo screen.
Another test i did, was installing RUU_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.exe and even the zip version, both of them install correctly but same problem, got stuck in HTC Logo screen, right now my phone is Unlocked bootloader, S-off with supercid (also tried the BS_US001 CID, same problem), hboot 1.55, is there any chance someone can help me with it? thanks a lot
Click to expand...
Click to collapse
go into stock recovery and do a factory reset ..it should boot then
I am running Stock 4.3, rooted and S-OFF. When I flash a 1.44 modified bootloader for the purpose of removing red text the phone starts differently than it does when on the 1.55 signed bootloader. With 1.44 modified hboot when it first starts up you see the htc splash screen disappear for a split second, kinda like a flicker. It also does it going into recovery. When I use the stock 1.55 hboot it starts normal, no flicker. I have tried 1.44 from this source http://forum.xda-developers.com/showthread.php?t=2314921 and have also used one from RegawMod customizer and they both do the same thing. I tried finding 1.44 hboot from moonshine but no luck. Is this normal behavior with the modified 1.44 hboots as far as the flickering goes? Is this because 1.44 are un-signed vs. the signed 1.55?
-Apollo- said:
I am running Stock 4.3, rooted and S-OFF. When I flash a 1.44 modified bootloader for the purpose of removing red text the phone starts differently than it does when on the 1.55 signed bootloader. With 1.44 modified hboot when it first starts up you see the htc splash screen disappear for a split second, kinda like a flicker. It also does it going into recovery. When I use the stock 1.55 hboot it starts normal, no flicker. I have tried 1.44 from this source http://forum.xda-developers.com/showthread.php?t=2314921 and have also used one from RegawMod customizer and they both do the same thing. I tried finding 1.44 hboot from moonshine but no luck. Is this normal behavior with the modified 1.44 hboots as far as the flickering goes? Is this because 1.44 are un-signed vs. the signed 1.55?
Click to expand...
Click to collapse
I think I flashed the same hboot from http://forum.xda-developers.com/showthread.php?t=2314921 but I dont recall seeing what you're describing....I can tell u though, on moonshines hboot, I see the HTC quietly brilliant screen for 5 secs or so
O.M.J said:
I think I flashed the same hboot from http://forum.xda-developers.com/showthread.php?t=2314921 but I dont recall seeing what you're describing....I can tell u though, on moonshines hboot, I see the HTC quietly brilliant screen for 5 secs or so
Click to expand...
Click to collapse
Probably something on my end then. It's no big deal, phone runs fine, I was just curious if anyone else saw this behavior.
Hello,
About a month back I destroyed my old HTC One. I unlocked the phone and flashed a new rom for the International version instead of the Sprint version. Ever since, no matter what rom I use, the phone is stuck in a boot loop. I cannot set it back to factory with the RUU because my version is more recent and I do not have S-OFF. I've since bought a new phone, but I'm looking to attempt to get the old one working. This has been a learning experience.
M7_WLS PVT SHIP S-ON RH
HBOOT - 1.55.0000
OpenDSP-v31.120.274.0617
OS-3.04.651.2
eMMC-boot 2048MB
Sep 18 2013,15:46:04.0
Any insight on what I can do to fix this would be greatly appreciated.
Thanks,
SJJ
sjjonesjr1 said:
Hello,
About a month back I destroyed my old HTC One. I unlocked the phone and flashed a new rom for the International version instead of the Sprint version. Ever since, no matter what rom I use, the phone is stuck in a boot loop. I cannot set it back to factory with the RUU because my version is more recent and I do not have S-OFF. I've since bought a new phone, but I'm looking to attempt to get the old one working. This has been a learning experience.
M7_WLS PVT SHIP S-ON RH
HBOOT - 1.55.0000
OpenDSP-v31.120.274.0617
OS-3.04.651.2
eMMC-boot 2048MB
Sep 18 2013,15:46:04.0
Any insight on what I can do to fix this would be greatly appreciated.
Thanks,
SJJ
Click to expand...
Click to collapse
Did you read this: http://forum.xda-developers.com/showthread.php?t=2503646 ?
I downgraded firmware and everything works
tdhite said:
Did you read this: http://forum.xda-developers.com/showthread.php?t=2503646 ?
Click to expand...
Click to collapse
I had the same problem before. I can't even restore ruu rom .. but as soon as I downgrade the firmware from 3.05.651.6 to 3.04.651.2 . everything works without a bootloop. been working on this problem for two days .. hope this will help others.
sprint htc one
hboot 155
Hello I have a problem,
I have htc one m7 locked for sprint (hboot 1.57.000, android 4.4 ) I already root it then i tried to turn s-off with rumrunner it was not possible cuz my kernel was stock ( I think...) so i tried to install custom kernel (Bulletproof-m7wl-1.2.zip) i then i stuck in bootloop ( htc logo). Now I can enter in recovery (teamwin) but i don't know what to do next.
diin1993 said:
Hello I have a problem,
I have htc one m7 locked for sprint (hboot 1.57.000, android 4.4 ) I already root it then i tried to turn s-off with rumrunner it was not possible cuz my kernel was stock ( I think...) so i tried to install custom kernel (Bulletproof-m7wl-1.2.zip) i then i stuck in bootloop ( htc logo). Now I can enter in recovery (teamwin) but i don't know what to do next.
Click to expand...
Click to collapse
You bootlooped because you loaded an incompatible kernel. Use *only* m7spr/m7wls kernels.
With that said -- just download a ROM you want (again -- stock with M7SPR or M7WLS (they're the same thing, just different ROMs call them by various names -- not going to explain that here).
Then, load your recovery (hopefully my TWRP 2.8.0.3 because it will work for you); "adb push" the rom file to /sdcard (i.e.: adb push <path_to_the_zip>.zip /sdcard) -- yes, that will work in recoveries.
Then install the ROM in your recovery. You should be fine with the caveat that if the kernel you loaded messed up your partitions (by writing it to the entirely incorrect disk partition), you'll have to RUU back to stock.
Hi
Back in december I converted my HTC One M7 to the GPE. I remember I had to unlock both with HTC and with another program, and also that I had to modify the CID etc. My device now looks like this:
CID-GOOGL001
HBOOT 1.54
RADIO-4T.21.3218.21
OpenDSP-v32.120.274.0909
Dec 9 2013 00:38:19
Now I saw HTC just released a new update for the HTC One including Sense 6. I'm wondering how I should approach the update. Should I try to revert everything back and install the original operating system (from when I made the switch to GPE) and then let HTC do an OTA to get to the new version? Will I need to modify CID etc? Will I lose S-OFF in the process? Or can I - now that I'm S-OFF - just format the phone and install the latest software from HTC? Will I need to update anything that has been modified in the time I as away from HTC (Radio firmware, HBOOT)?
Thanks!
Hi, I have an HTC One M7 for Sprint. It is running software version 5.03.651.3 according to settings.
The hboot is version 1.57
Currently the phone is locked and s-on but there is no recovery mode installed on the phone at all. When I try to update the phone it reboots to bootloader because there is no recovery partition on the device.
I can not run a RUU because every time I do I get an error 155. I am assuming that is because the hboot is newer than the one in the RUU.
I have tried changing the mainver to the one in both RUUs that I tried but it did not work.
I am stuck and would appreciate any help if anyone has any suggestions.