I've been struggling with this for over a day now.
I unlocked and rooted my phone just fine (HTC One on Sprint, 4.3) - but when I flashed a ROM, I flashed Maximus HD, which was apparently an International version and not a Sprint one. I think that messed some things up. After trying a few different ROMs on top of that, nothing works.
Each ROM I flash will "install" correctly, but when it boots to the lock screen, upon unlocking it gives me the HTC splash screen.
I'm convinced that my accidental upgrade to hboot 1.55 is rendering it impossible for me to flash any working ROMs - be it stock or otherwise. I can enter Recovery mode, adb sideload, and flash ROMs, but none of them work.
I've tried Superwipe and then Bad Boyz, but it's the same thing. After installation, it sticks at the HTC splash screen.
So, my options are limited. I think I need to find a way to revert my hboot to 1.44 from 1.55 - that way at least the stock RUU is compatible. However, I can't find any way to do this; since I'm S-On, and I can't access any ROM to mess with settings, I have no idea how to do this, or how to flash a workable ROM in order to switch to S-Off.
Anyone have any ideas. I'm seriously distraught. I just bought this phone, and I love it. I'm so sad that I decided to try this rooting/unlocking/ROM flashing business because it's disrupted my sanity.
Any thoughts or ideas will help immensely. I will give more information if needed. Thanks!
WayneQuasar said:
I've been struggling with this for over a day now.
I unlocked and rooted my phone just fine (HTC One on Sprint, 4.3) - but when I flashed a ROM, I flashed Maximus HD, which was apparently an International version and not a Sprint one. I think that messed some things up. After trying a few different ROMs on top of that, nothing works.
Each ROM I flash will "install" correctly, but when it boots to the lock screen, upon unlocking it gives me the HTC splash screen.
I'm convinced that my accidental upgrade to hboot 1.55 is rendering it impossible for me to flash any working ROMs - be it stock or otherwise. I can enter Recovery mode, adb sideload, and flash ROMs, but none of them work.
I've tried Superwipe and then Bad Boyz, but it's the same thing. After installation, it sticks at the HTC splash screen.
So, my options are limited. I think I need to find a way to revert my hboot to 1.44 from 1.55 - that way at least the stock RUU is compatible. However, I can't find any way to do this; since I'm S-On, and I can't access any ROM to mess with settings, I have no idea how to do this, or how to flash a workable ROM in order to switch to S-Off.
Anyone have any ideas. I'm seriously distraught. I just bought this phone, and I love it. I'm so sad that I decided to try this rooting/unlocking/ROM flashing business because it's disrupted my sanity.
Any thoughts or ideas will help immensely. I will give more information if needed. Thanks!
Click to expand...
Click to collapse
Check PM
same problem like TS have
Having the same issues like TS..
Can somebody point me where to look for the answers,the difference is that im on .44 boot
Somebody please
MeiTeS said:
Having the same issues like TS..
Can somebody point me where to look for the answers,the difference is that im on .44 boot
Somebody please
Click to expand...
Click to collapse
Look HERE
I think this is going to need an experienced dev to answer. Its a small question and probably a small answer but I'm going to put all the information I can.
Ok, so my background is that I recently returned my phone stock, the steps I took were:
S-off, flash RUU, root, remove tampered and unlocked flags, unroot, flash stock recovery, lock the bootloader, s-on.
I then OTAed myself up to 4.3 sense 5.5.
My issue is that having returned to stock, my phone has some instabilities like:
1. it randomly restarted once,
2. I can't lock the device (but can power it off so its not the button broken),
3. and once I opened the camera and the camera bit only took a square of the screen, as in it didn't fill up the whole screen, and the camera menus were messed up (when I rotated, half of the menus were cropped out of the screen, but it went back to normal around 15 seconds later).
Anyway, reason I'm posting this is that I have a niggling feeling that, being originally a CID J15 and x.xx.415.x (middle east firmware which has no RUU available) firmware device, I flashed a 401.x (Europe I think) firmware RUU, this is giving my device some issues. Would that be possible? I got the RUU from htc1guru and it listed J15 as one of the suitable CIDs for the RUU. I also, after unrooting, relocking bootloader and s-on, flashed the RUU again, because as far as I know the RUU (something made by HTC officially) will not flash on a CID that it was not made for, and it worked just fine. So, thats not the issue then is it? I can't think of anything else, I didn't even install any apps yet, only whatsapp.
3alaawi said:
I think this is going to need an experienced dev to answer. Its a small question and probably a small answer but I'm going to put all the information I can.
Ok, so my background is that I recently returned my phone stock, the steps I took were:
S-off, flash RUU, root, remove tampered and unlocked flags, unroot, flash stock recovery, lock the bootloader, s-on.
I then OTAed myself up to 4.3 sense 5.5.
My issue is that having returned to stock, my phone has some instabilities like:
1. it randomly restarted once,
2. I can't lock the device (but can power it off so its not the button broken),
3. and once I opened the camera and the camera bit only took a square of the screen, as in it didn't fill up the whole screen, and the camera menus were messed up (when I rotated, half of the menus were cropped out of the screen, but it went back to normal around 15 seconds later).
Anyway, reason I'm posting this is that I have a niggling feeling that, being originally a CID J15 and x.xx.415.x (middle east firmware which has no RUU available) firmware device, I flashed a 401.x (Europe I think) firmware RUU, this is giving my device some issues. Would that be possible? I got the RUU from htc1guru and it listed J15 as one of the suitable CIDs for the RUU. I also, after unrooting, relocking bootloader and s-on, flashed the RUU again, because as far as I know the RUU (something made by HTC officially) will not flash on a CID that it was not made for, and it worked just fine. So, thats not the issue then is it? I can't think of anything else, I didn't even install any apps yet, only whatsapp.
Click to expand...
Click to collapse
Could you provide the following informations? Because then it's easier to determine the reason for the misbehaviour...
-Did you also have these issues with the firmware you got from the RUU, I mean did you also experience these issues without any OTAs?
-Could you post the link to the RUU you used? Because I also RUUed my phone a few days ago with the same procedure.. but actually, I am from Europe
-Did you flash the stock hboot 1.44 before flashing the RUU?
And as far my knowledge goes, the middle east HTC One doesn't have other hardware, it only has a bit different software, so this shouldn't be the cause for the issues..
Other than that:
Unlock your phone, use a custom recovery and flash a different ROM, and if it works in this case, you can exclude other firmware parts than the system...
And maybe you wanna try out one of these RUUs:
http://www.androidruu.com/index.php?developer=M7
Maybe there is one for you
LibertyMarine said:
Could you provide the following informations? Because then it's easier to determine the reason for the misbehaviour...
-Did you also have these issues with the firmware you got from the RUU, I mean did you also experience these issues without any OTAs?
-Could you post the link to the RUU you used? Because I also RUUed my phone a few days ago with the same procedure.. but actually, I am from Europe
-Did you flash the stock hboot 1.44 before flashing the RUU?
And as far my knowledge goes, the middle east HTC One doesn't have other hardware, it only has a bit different software, so this shouldn't be the cause for the issues..
Other than that:
Unlock your phone, use a custom recovery and flash a different ROM, and if it works in this case, you can exclude other firmware parts than the system...
And maybe you wanna try out one of these RUUs:
http://www.androidruu.com/index.php?developer=M7
Maybe there is one for you
Click to expand...
Click to collapse
Hello,
Here's the RUU I flashed:
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
It didn't flash first and it said on the link I just posted that I may need hboot 1.44 and so I downloaded and flashed that one and then it worked.
I couldn't tell you if I experienced this before the OTA or not because I OTAed one update after the other immediately. What I can say however is that the home and back button seemed less sensitive to touch in the initial builds, but one of the OTAs made it how it always is.
A for unlocking again and flashing a different rom, I guess I could flash a stock 401 4.3 rom and redo the unrooting process. I just found it really odd that I'm having these issues whilst being on full stock, I've only ever had these issues when flashing unreliable roms and kernels. You lost me at "excluding other firmware parts" though. My main concern is that I want zero chance for anyone to know that my devices was rooted once upon a time, so I wouldn't want to compromise that.
3alaawi said:
Hello,
Here's the RUU I flashed:
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
It didn't flash first and it said on the link I just posted that I may need hboot 1.44 and so I downloaded and flashed that one and then it worked.
I couldn't tell you if I experienced this before the OTA or not because I OTAed one update after the other immediately. What I can say however is that the home and back button seemed less sensitive to touch in the initial builds, but one of the OTAs made it how it always is.
A for unlocking again and flashing a different rom, I guess I could flash a stock 401 4.3 rom and redo the unrooting process. I just found it really odd that I'm having these issues whilst being on full stock, I've only ever had these issues when flashing unreliable roms and kernels. You lost me at "excluding other firmware parts" though. My main concern is that I want zero chance for anyone to know that my devices was rooted once upon a time, so I wouldn't want to compromise that.
Click to expand...
Click to collapse
Ok.. I flashed the zip.. but this really shouldn't be an issue
But with "excluding other firmware parts" I meant.. if you try another ROM and there it works, you should definitely know that the issue is caused by the system and not by hardware or bootloader etc...
Try another ROM and if it works fine, you can try another RUU.. maybe the zip.. and then you can re-unroot your HTC One and then they won't have any chance finding out what you'd done
3alaawi said:
Hello,
Here's the RUU I flashed:
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
It didn't flash first and it said on the link I just posted that I may need hboot 1.44 and so I downloaded and flashed that one and then it worked.
I couldn't tell you if I experienced this before the OTA or not because I OTAed one update after the other immediately. What I can say however is that the home and back button seemed less sensitive to touch in the initial builds, but one of the OTAs made it how it always is.
A for unlocking again and flashing a different rom, I guess I could flash a stock 401 4.3 rom and redo the unrooting process. I just found it really odd that I'm having these issues whilst being on full stock, I've only ever had these issues when flashing unreliable roms and kernels. You lost me at "excluding other firmware parts" though. My main concern is that I want zero chance for anyone to know that my devices was rooted once upon a time, so I wouldn't want to compromise that.
Click to expand...
Click to collapse
Did it work? Or can I provide more help?
LibertyMarine said:
Did it work? Or can I provide more help?
Click to expand...
Click to collapse
I actually just booted into the bootloader and turned the phone on again. Then I could lock my device again and it seemed stable though I didn't have much time to test it. I just sent it in for repairs earlier today (for another issue, I have the camera tint problem with my device).
I'm guessing the previous times I reset it, it had that option in the power menu on (fast boot or something like that) maybe thats why the problems didn't go away?
Anyway, thanks for your help
Dont't buy HTC. They Thef's .
This is Problem.... Producer send fake updates to destroy all firmware stock too. I Have Desire 626 from ORANGE PL and my phone get update with this same problems. One idea. Dont't buy HTC. They Thef's .
Hey guys,
Trying to figure out how to unbrick it before just calling the Carrier to sort things out there. Long story short, updated to 6.0 (stock firmware) and was working fine. But once I restarted the phone later in the day, it just got stuck on the boot screen. Really sucked...
Tried factory reset in the bootloader, no luck. Also tried to use the RUU for the latest firmware available currently, but for obvious reasons it doesn't work.
Therefore at the very least if someone could point towards the RUU version 5.11.631.8 Rogers, that would be a good start.
Free to any suggestions too! Used to flash roms and stuff when I had the Xperia X10 and the HTC Incredible so just need a brushing up on this stuff.
Also BTW, the Hboot is 1.57 but its also S-ON (never bothered to unlock it)
Hi there,
I am using the Htc One M7 for At&t. I decided to root it and everything went good. I unlocked the bootloader, flashed a custom recovery and had the Xsense module installed and I loved it. I decided to try out cyanongen and if I didn't like it I would go back to stock. That doesn't quite work that way, needless to say. I ended up without a Rom and stuck on the bootloader. After countless hours of troubleshooting I found a stock htc rom and stock recovery, however now my problem is I can't seem to update my OS to the latest version, 4.4.3, which is what I had before all this. I've read it is because of the phone being unlocked. So I lock it and it boots to bootloader saying tampered relocked and Security Warning. I do more countless hours of research and find a few programs to make my phone S-off. Revone does not work. Firewater does not work and Rumrunner fails. I believe it is because the h boot is 1.57. My question now is do I just go sit in a corner and start crying or is their something im missing or not doing right? My phone is rooted, I just want to go back to stock.
Hello,
I am new to xda forum and expecting a helping hand from fellow members, here's the scenario, I have a sprint htc one which was working fine a few days ago before i decided to act smart .
It was rooted when i purchased it so i thought of flashing a new custom rom into it.I tried flashing (HTC_One_-_MaximusHD_53.0.0) and this one (NuSenSeveN-LP-m7-Sprint_v4.02_050715) and ended up being stuck at green HTC logo, even though the physical buttons are performing their respective functions when pressed but the screen shows just the htc one logo and nothing else.
It is unlocked, tampered and s-on and i have twrp recovery on board, hboot 1.57.0000
WHAT I HAVE ALREADY TRIED AND FAILED:
1) tried rum runner to turn s-off because i though may b because of s-on the roms are not being flashed properly but it says adb device not found
2) tried flashing Bad_Boyz_Sprint_ONE_M7_Lollipop_v2.0 but stuck at handsfree activation, even though i deleted htcwizard.apk.
Now the bottom line is, I am unable to use my device and in desperate need of your help.
Please respond, awaiting to put my hand back on the device.
Thank You
Flashing MaximusHD_53.0.0 messed up your partitions (it's not Sprint compatible as far as I know) and NuSenSeveN you have to fastboot flash the kernel separately ( I had the same problem lol)
The easiest fix would be to run the latest RUU and start fresh, then only flash roms that are Sprint compatible.
Sloth said:
Flashing MaximusHD_53.0.0 messed up your partitions (it's not Sprint compatible as far as I know) and NuSenSeveN you have to fastboot flash the kernel separately ( I had the same problem lol)
The easiest fix would be to run the latest RUU and start fresh, then only flash roms that are Sprint compatible.
Click to expand...
Click to collapse
Hey thanks for the response, I am not tech geek so I have no idea how to flash the latest RUU can you please be more specific about how to perform the above mentioned process or can you have a chat on hangouts as I have altready added you on it.
Thanks alot
Try to flash ruu which could be found on other posts do u know how to boot into the bootloader?
problem solved
Update: thanks to @Sloth I have fixed the problem, if anyone out there who owns a sprint htc one and have messed up his phone by flashing an incompatible rom the way i did, first relock your bootloader if you are s-on and then simply download RUU file from htc official website, make sure its for sprint variant.
Once the bootloader is relocked simply run ruu.exe file that you have downloaded and you are done.
Note: if the ruu setup says that you phone is not connected or gets stuck, boot into recovery and perform factory, after that re-try running ruu.
Thanks Sloth, and thanks xda members