Develop Bugs

Boot Loop After Rooting

Hey Everyone!
I've been trying to fix this problem for hours with no luck, and while I've found solutions that have worked for others I can't find one that is specific enough to my situation.
So I just got an HTC One X that is locked to Rogers today from Kijiji, and I love it - great phone. The thing I didn't like was the hoard of stock apps that took up about four pages on the app drawer, so I thought hey, I'll root it and delete them. I didn't have any intention of using any custom ROMs, just wanted superuser permission to delete stock apps. Unlocking went fine (finding the token and what not using the app I found on here), and the rooting seemed to go alright until it turned off and didn't start again. I pulled out the cable from the computer and now things are weird..
I can sometimes get into the hboot, but when I try to just start the phone normally it goes to the HTC splash screen and has red writing telling me "this build is for development purposes only", etc etc. I really wanted to get rid of those stock apps but at this point I just want my phone working again. Am I screwed?
Thanks in advance.

Re:
Little update: I just figured out how to re-lock it assuming that might make my factory reset work.. it didn't.
oot-n-aboot said:
Hey Everyone!
I've been trying to fix this problem for hours with no luck, and while I've found solutions that have worked for others I can't find one that is specific enough to my situation.
So I just got an HTC One X that is locked to Rogers today from Kijiji, and I love it - great phone. The thing I didn't like was the hoard of stock apps that took up about four pages on the app drawer, so I thought hey, I'll root it and delete them. I didn't have any intention of using any custom ROMs, just wanted superuser permission to delete stock apps. Unlocking went fine (finding the token and what not using the app I found on here), and the rooting seemed to go alright until it turned off and didn't start again. I pulled out the cable from the computer and now things are weird..
I can sometimes get into the hboot, but when I try to just start the phone normally it goes to the HTC splash screen and has red writing telling me "this build is for development purposes only", etc etc. I really wanted to get rid of those stock apps but at this point I just want my phone working again. Am I screwed?
Thanks in advance.
Click to expand...
Click to collapse

Try here.
You may be in the wrong forum, this is for Tegra3 One X. I'm not sure though so don't quote me on it.

Re:
Hmm I didn't see a Rogers specific one so I wasn't sure. As for the link you posted it might have worked but a don't have a TWRP backup? I didn't think it was necessary to make a backup as I wasn't even trying to flash a custom ROM, just get myself superuser permission.
lmt337 said:
Try here.
You may be in the wrong forum, this is for Tegra3 One X. I'm not sure though so don't quote me on it.
Click to expand...
Click to collapse

You haven't bricked your HOX yet. I would look into getting a recovery on to it, from there you'll be able to flash a RUU to get back to where you started. Make sure you get the right instructions for your phone though.
You might get some info here

Re:
Thanks! I'm trying to find the RUU for my phone. I've found the one for the AT&T version with LTE, but mine is the one without it. Will the same RUU work? Thanks

Don't flash anything from here!! You are in the wrong forum m8!
This is the correct forum for you : http://forum.xda-developers.com/forumdisplay.php?f=1538

AHH thanks! I just thought the XL one was for the LTE model?
vin4yak said:
Don't flash anything from here!! You are in the wrong forum m8!
This is the correct forum for you : http://forum.xda-developers.com/forumdisplay.php?f=1538
Click to expand...
Click to collapse

So I think my HTC One V is bricked, can someone help?

So, I previously had an optimus v, which is like the easiest phone to root and get roms for and what not. Well i was hoping that the One V would be the same, it was not.
So I tried to install some rom that i liked after going through the unlocking and rooting process,and it had a restarting problem where every 5-15 seconds after it would boot it would restart. I found a solution (kind of) to that but most of the links where dead so i had to find them on my own. It led me to putting a custom kernel on it and that did not fix it, so i saw something that getting the OTA update that came out a while ago could cause this, and the only way to return it was to use RUU (i still had a custom kernel at this point, i think) so i got the (hopefully) correct recovery.img from RUU and i flashed that and the next step is to relock the device, so i did via command prompt, and i started RUU up again and it was doing its thing and ended in an error 155. I have tried several times and it has still not worked. I found some stuff saying that the HBOOT i have which is 1.57 doesnt have a supported RUU or something to that effect ( i found lots of conflicting information).
So now i am stuck with a phone that only goes to the bootloader menu and because its relocked i cant flash anything to it.
I have tried fastboot oem unlock and that came up with a command error, and everything else i try to flash just fails.
Any help is welcome and a thank you in advance to anyone that helps.

matterlord1 said:
So, I previously had an optimus v, which is like the easiest phone to root and get roms for and what not. Well i was hoping that the One V would be the same, it was not.
So I tried to install some rom that i liked after going through the unlocking and rooting process,and it had a restarting problem where every 5-15 seconds after it would boot it would restart. I found a solution (kind of) to that but most of the links where dead so i had to find them on my own. It led me to putting a custom kernel on it and that did not fix it, so i saw something that getting the OTA update that came out a while ago could cause this, and the only way to return it was to use RUU (i still had a custom kernel at this point, i think) so i got the (hopefully) correct recovery.img from RUU and i flashed that and the next step is to relock the device, so i did via command prompt, and i started RUU up again and it was doing its thing and ended in an error 155. I have tried several times and it has still not worked. I found some stuff saying that the HBOOT i have which is 1.57 doesnt have a supported RUU or something to that effect ( i found lots of conflicting information).
So now i am stuck with a phone that only goes to the bootloader menu and because its relocked i cant flash anything to it.
I have tried fastboot oem unlock and that came up with a command error, and everything else i try to flash just fails.
Any help is welcome and a thank you in advance to anyone that helps.
Click to expand...
Click to collapse
You should be able to flash a stock RUU for your device while it's in the bootloader menu from here:
http://androidfiles.org/ruu/?developer=Primo
make sure to download the correct RUU for your carrier/radio band and if its GSM (PRIMOU) or CDMA (PRIMOC), or you can screw it up more.
What network carrier are you with?
EDIT:, Just re-read your post, sorry. I don't know if anyone has posted a RUU for the updated radio, that Virgin Mobile released, you may need to get ahold of Football on this forum and see if he's still helping find/sell RUU's that you need.
Back in the day I had to get ahold of him to get the RUU for my phone that wasn't listed on any RUU site.

FreakyFreakGA said:
You should be able to flash a stock RUU for your device while it's in the bootloader menu from here:
make sure to download the correct RUU for your carrier/radio band and if its GSM (PRIMOU) or CDMA (PRIMOC), or you can screw it up more.
What network carrier are you with?
EDIT:, Just re-read your post, sorry. I don't know if anyone has posted a RUU for the updated radio, that Virgin Mobile released, you may need to get ahold of Football on this forum and see if he's still helping find/sell RUU's that you need.
Back in the day I had to get ahold of him to get the RUU for my phone that wasn't listed on any RUU site.
Click to expand...
Click to collapse
I don't really know about buying RUU's, that's like blackberry with their pay to unlock the imei thing. although if it saves me from having to buy a new phone ill consider it.

matterlord1 said:
I don't really know about buying RUU's, that's like blackberry with their pay to unlock the imei thing. although if it saves me from having to buy a new phone ill consider it.
Click to expand...
Click to collapse
I paid like $13 for mine, but it gave me piece of mind should the phone ever soft brick or hard brick with boot, that I can recover it and not lose a phone. I don't know if he's even around anymore, but I posted a thread in general asking if he was. I am on Alltel, but one of my family members bought an HTC One V with the updated radio, so for her I couldn't do anything but root. I know there are a few new radio friendly ROM's in the CDMA section of this forum that would of boot with a custom rom and the kernel.

FreakyFreakGA said:
I paid like $13 for mine, but it gave me piece of mind should the phone ever soft brick or hard brick with boot, that I can recover it and not lose a phone. I don't know if he's even around anymore, but I posted a thread in general asking if he was. I am on Alltel, but one of my family members bought an HTC One V with the updated radio, so for her I couldn't do anything but root. I know there are a few new radio friendly ROM's in the CDMA section of this forum that would of boot with a custom rom and the kernel.
Click to expand...
Click to collapse
yeah i found some ROM's that will work only after this happened. In my research i found something about downgrading HBOOT i only saw it on other phones and it did not look like something i wanted to mess with. And my HTC One V is CDMA on Virgin Mobile.

matterlord1 said:
yeah i found some ROM's that will work only after this happened. In my research i found something about downgrading HBOOT i only saw it on other phones and it did not look like something i wanted to mess with. And my HTC One V is CDMA on Virgin Mobile.
Click to expand...
Click to collapse
UPDATE: So i figured it out, I went and i reflashed the Unlock_code.bin file and now its back to unlocked again. Thanks to FreakyFreakGA to doing his best to help me out.

Be sure to flash an OTA-compatible ROM. Try RhythmicROM or CyanPrimo, both of which I've used for a long time and can attest that they are better HTC One V ROMs.

matterlord1 said:
UPDATE: So i figured it out, I went and i reflashed the Unlock_code.bin file and now its back to unlocked again. Thanks to FreakyFreakGA to doing his best to help me out.
Click to expand...
Click to collapse
so matterlord what rom are you running right now? were you ever able to revert back to stock? I am having the same problem you did.

gotts101 said:
so matterlord what rom are you running right now? were you ever able to revert back to stock? I am having the same problem you did.
Click to expand...
Click to collapse
I never tried to go back to stock, I'm running rhythmic ROM, can't link right now but it seems to work pretty well, its slightly faster than stock when all my stuff is on there and the only problem so far is sometimes when you lock the device and then quickly unlock it then it will freeze and restart.

matterlord1 said:
I never tried to go back to stock, I'm running rhythmic ROM, can't link right now but it seems to work pretty well, its slightly faster than stock when all my stuff is on there and the only problem so far is sometimes when you lock the device and then quickly unlock it then it will freeze and restart.
Click to expand...
Click to collapse
Yeah I just flashed Rhythmic. Seems pretty nice by my wifi is having some weird authentication problem. It doesn't seem like there are very many ROMs out there that would work though.

gotts101 said:
Yeah I just flashed Rhythmic. Seems pretty nice by my wifi is having some weird authentication problem. It doesn't seem like there are very many ROMs out there that would work though.
Click to expand...
Click to collapse
Yeah, make sure you find the right version for your radio, virgin mobile made a terrible move by updating it so you cant do much with it.
Or kernel or something, anyways mine was v5.2 and it was a pain, i think there was a lot more kernels available for older versions.
Best of luck, and if you are having problems with authentication then try using WPS, in some cases it fixes those types of problems.

[Q] Help out a new guy?

Hi.
I am very new to the world of rooting and all that stuff, in fact, I have never even attempted to root any of my phones. I currently own HTC One X (International version) which is running the newest Sense 5 Android 4.2.2. update. I tried to follow some youtube videos on how to root my One X but they are all a year old at least and are demonstrated on the stock version of Sense that was on my One X when I got it.. Now I know I am a huge noob at this but I would just like to ask if somebody can guide me trough or at least give me a link to some kind of guide/tutorial which will work on the newest update for my One X. I am very cautious because I don't want to harm my phone by doing something stupid or wrong. Anyways, hope somebody can spare a minute and help me out. And also thanks for taking the time to read my post!

TwystedThrottle said:
Hi.
I am very new to the world of rooting and all that stuff, in fact, I have never even attempted to root any of my phones. I currently own HTC One X (International version) which is running the newest Sense 5 Android 4.2.2. update. I tried to follow some youtube videos on how to root my One X but they are all a year old at least and are demonstrated on the stock version of Sense that was on my One X when I got it.. Now I know I am a huge noob at this but I would just like to ask if somebody can guide me trough or at least give me a link to some kind of guide/tutorial which will work on the newest update for my One X. I am very cautious because I don't want to harm my phone by doing something stupid or wrong. Anyways, hope somebody can spare a minute and help me out. And also thanks for taking the time to read my post!
Click to expand...
Click to collapse
try this. this is the one i followed when i root my one x before. http://www.youtube.com/results?search_query=cursed4eva+root+htc+one+x&oq=cursed4eva+root+htc+one+x&gs_l=youtube.12...0.0.0.14440.0.0.0.0.0.0.0.0..0.0...0.0...1ac..11.youtube.

So this works for Sense 5 update? Does it even matter which version I am running on my phone for rooting?

TwystedThrottle said:
So this works for Sense 5 update? Does it even matter which version I am running on my phone for rooting?
Click to expand...
Click to collapse
yep. but i dont know if hassoons toolkit is still ok. but you can do it manually. just watch the video. or try this tool kit.havent used it but its the same as hassoons. http://forum.xda-developers.com/showthread.php?t=2437459

Things are starting to get a little bit more clear now. I managed to unlock the bootloader so far. Before I go any further, is there anything I should look out for, what could go wrong? I've read that if I mess something up I could brick my phone, how can I avoid that? Also, thanks a lot for helping me out!

TwystedThrottle said:
Things are starting to get a little bit more clear now. I managed to unlock the bootloader so far. Before I go any further, is there anything I should look out for, what could go wrong? I've read that if I mess something up I could brick my phone, how can I avoid that? Also, thanks a lot for helping me out!
Click to expand...
Click to collapse
after you unlocked the bootloader flash custom recovery. then do a nandroid backup. then flash supersu/superuser then do nandroid backup again. you now have 2 backups of stock rom and stock rom(rooted) and when you flash custom rom make a backup again. eat will eat up space in storage but its better be safe.

(HELP) TMO HTC One- keep wiping and still end up in bootloop

I got a new HTC One m8 from Tmobile a few weeks ago and instantly went to root and find out about S on and how I can get rid of it. I followed a rooting tutorial on unlockr diligently and unlocked bootloader and installed TWRP and SuperSU. I moved on to S-off the device and got to the last step of the tutorial where it starts to "chug" bottles(Firewater). After the first bottle, it tells me I'm out of luck and that my phone is patched. This confused me. Does this mean that my phone is forever stuck S-on? or does it mean that the developers of firewater haven't developed an S-off method for the newest version of HTC's software and that I simply have to wait.
This is just my first problem, even though I can't flash custom ROMs I was fine because I was willing to give the stock ROM a chance and just tweak it with root privileges, but no, the next time I had to restart for some various reason it starts bootlooping every few minutes. I swear I didn't do anything wrong when rooting. Is it just too new and the newest HTC software makes the rooting process obsolete making it impossible to root?
So I end up wiping the phone not being able to save all the pictures I took on my trip in the mountains. My phone is still rooted but the phone is wiped. I go about thinking the solution is fixed and when I decide to nandroid backup, I go into recovery, do a simple backup and when I restart it goes straight back to the infuriating bootloop. A simple nandroid backup shouldn't make it go into a bootloop.
So I decide to relock the bootloader, install the stock recovery and software again and start over. Maybe I really did mess up rooting. I go through the process again and low and behold my phone goes into a bootloop again.
I'm so sick and tired of this phone and I'm not sure why it always seems to happen to me. I follow the tutorials closely and it always ends up ****ting on me.
It recently went into a bootloop after a good 3 day run where I managed to keep the phone on the entire time. Had to restart because the wifi antenna wasn't working and another bootloop ensued. I decided to make this thread to see if any other new users are experiencing similar difficulties and seeing if anyone knows a cause or maybe a solution. Right now in the process of unrooting and going back to stock.
It would be a shame if there really is no way for me to unlock the full potential of my new phone. Almost wishing I had bought a nexus.
Thank you for anyone who was willing to read that and to anyone who takes the time to write a response. Thanks!

westonnate said:
I got a new HTC One m8 from Tmobile a few weeks ago and instantly went to root and find out about S on and how I can get rid of it. I followed a rooting tutorial on unlockr diligently and unlocked bootloader and installed TWRP and SuperSU. I moved on to S-off the device and got to the last step of the tutorial where it starts to "chug" bottles(Firewater). After the first bottle, it tells me I'm out of luck and that my phone is patched. This confused me. Does this mean that my phone is forever stuck S-on? or does it mean that the developers of firewater haven't developed an S-off method for the newest version of HTC's software and that I simply have to wait.
This is just my first problem, even though I can't flash custom ROMs I was fine because I was willing to give the stock ROM a chance and just tweak it with root privileges, but no, the next time I had to restart for some various reason it starts bootlooping every few minutes. I swear I didn't do anything wrong when rooting. Is it just too new and the newest HTC software makes the rooting process obsolete making it impossible to root?
So I end up wiping the phone not being able to save all the pictures I took on my trip in the mountains. My phone is still rooted but the phone is wiped. I go about thinking the solution is fixed and when I decide to nandroid backup, I go into recovery, do a simple backup and when I restart it goes straight back to the infuriating bootloop. A simple nandroid backup shouldn't make it go into a bootloop.
So I decide to relock the bootloader, install the stock recovery and software again and start over. Maybe I really did mess up rooting. I go through the process again and low and behold my phone goes into a bootloop again.
I'm so sick and tired of this phone and I'm not sure why it always seems to happen to me. I follow the tutorials closely and it always ends up ****ting on me.
It recently went into a bootloop after a good 3 day run where I managed to keep the phone on the entire time. Had to restart because the wifi antenna wasn't working and another bootloop ensued. I decided to make this thread to see if any other new users are experiencing similar difficulties and seeing if anyone knows a cause or maybe a solution. Right now in the process of unrooting and going back to stock.
It would be a shame if there really is no way for me to unlock the full potential of my new phone. Almost wishing I had bought a nexus.
Thank you for anyone who was willing to read that and to anyone who takes the time to write a response. Thanks!
Click to expand...
Click to collapse
If you wanna fix it quick then just do an RUU (t-mobile one) and after you've done that use Sunshine to root, unlock and S-OFF your phone. All though Sunshine costs $25 it is a sure fire to work.
You can find a tutorial for the RUU in the t-mobile forum I believe, not sure as im replying to this before I go to bed but it should have one. If by some chance "TMO" doesn't mean T-Mobile then my bad. Anyways if you get confused take your time and do your research or wait for someone else or me to assist you further.
Also if you used Xposed then that could be the problem, I've had it randomly bootloop me after days of use, just google the Xposed deactivate script zip or Uninstaller script and flash it to remove it. If you don't have it then don't do this part.
Lastly I doubt you'll regret buying an M8 after you get it setup properly, it's a great phone but of course that's just mine and a lot of people's opinion. Anyways good luck and hope one of my solutions fix it! If not then don't be afraid to ask more questions or request further assistance whether from me or someone else.

S1L3nTShaDoWz said:
If by some chance "TMO" doesn't mean T-Mobile then my bad.
Click to expand...
Click to collapse
It does, although T-Mobile is a huge carrier in Europe, and AFAIK only the US T-Mob variant has an RUU (and not immediately clear what version the OP has).

You can flash custom roms without s-off, and have you tried wiping cache and fixing permissions? Idk if that'd solve it or not but worth a try.

Updating question

Ok, I start this off with the fact that this is my first phone with the whole slot A&B thing. I've done a ton of reading but it's still very confusing to me. I'm very confused on what exactly to do when it comes to updates. I'm stock rooted with TWRP installed on slot A. I'm also on the December build. I would like to update but I don't know what the easiest way to go about it is to be honest. I feel like an idiot but I guess that's because I'm really old school when it comes to this stuff. My rooting/roming goes back to the Samsung Captivate and countless other phones up until it got to be too much of a hassle to get a phone from a carrier that could be messed with. Now that I have rambled on, I thought it would be different getting a Pixel but this whole slot thing has me all confused. I basically want to stay stock rooted for now and possibly try a kernel down the line but I'm very happy with stock for now. Any advice would be greatly appreciated.
Thanks

pside15 said:
Ok, I start this off with the fact that this is my first phone with the whole slot A&B thing. I've done a ton of reading but it's still very confusing to me. I'm very confused on what exactly to do when it comes to updates. I'm stock rooted with TWRP installed on slot A. I'm also on the December build. I would like to update but I don't know what the easiest way to go about it is to be honest. I feel like an idiot but I guess that's because I'm really old school when it comes to this stuff. My rooting/roming goes back to the Samsung Captivate and countless other phones up until it got to be too much of a hassle to get a phone from a carrier that could be messed with. Now that I have rambled on, I thought it would be different getting a Pixel but this whole slot thing has me all confused. I basically want to stay stock rooted for now and possibly try a kernel down the line but I'm very happy with stock for now. Any advice would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
@Homeboy76 will get you squared away :good:
https://forum.xda-developers.com/pi...-android-9-0-pie-unlock-t3857195/post77944292

Badger50 said:
@Homeboy76 will get you squared away :good:
https://forum.xda-developers.com/pi...-android-9-0-pie-unlock-t3857195/post77944292
Click to expand...
Click to collapse
Thanks for the reply. I've read throughout that thread numerous times and I still can't determine the easiest way to update my phone and the necessary steps to take to get there. I just want to be stock rooted like I am now but don't know what steps to take to get there. Like do I need to unroot first, relock bootloader? I'm sure all those answers are in that thread but I'm probably just too dense to see them. I haven't really had a solid rooted phone in like 3 years so I'm used to things being done way different. Some times I miss my old HTC Inspire/Desire HD. There was so much development for that phone and it was all very straightforward.

pside15 said:
Thanks for the reply. I've read throughout that thread numerous times and I still can't determine the easiest way to update my phone and the necessary steps to take to get there. I just want to be stock rooted like I am now but don't know what steps to take to get there. Like do I need to unroot first, relock bootloader? I'm sure all those answers are in that thread but I'm probably just too dense to see them. I haven't really had a solid rooted phone in like 3 years so I'm used to things being done way different. Some times I miss my old HTC Inspire/Desire HD. There was so much development for that phone and it was all very straightforward.
Click to expand...
Click to collapse
This guide is how I update the monthly security patches. It is predicated on the notion that you have the latest platform-tools (28.0.1) and that your computer and phone are communicating well. It doesn't not require you to switch slots, and it will not wipe your data, and, you do not have to unroot before you begin. Happy flashing, and good luck
And never ever ever relock the bootloader! :crying:

Badger50 said:
This guide is how I update the monthly security patches. It is predicated on the notion that you have the latest platform-tools (28.0.1) and that your computer and phone are communicating well. It doesn't not require you to switch slots, and it will not wipe your data, and, you do not have to unroot before you begin. Happy flashing, and good luck
And never ever ever relock the bootloader! :crying:
Click to expand...
Click to collapse
Awesome, thank you very much for that. Yeah, I figured that about the bootloader. Does it matter if I have TWRP installed? That's the one main confusing thing to me. How you can have TWRP installed or not installed. I'm used to absolutely having to have TWRP or some other kind of custom recovery installed. But like I said it's been quite a while since I was really able to root/ROM a phone. I was basically forced to move to AT&T and opted for the Active line of Galaxy phones since I have little kids plus even the phones that were rootable and such seemed like more of a hassle than it was worth. The last phone I had that had some good development was probably the LG G3 on T-MOBILE. For some reason the T-MOBILE version had an unlocked bootloader or could be unlocked, don't remember exactly. But then a coworker got a Pixel 2XL and I got the itch again, not knowing how much had really changed though. Ok, I think I've rambled on enough now. Thanks again for the help.

pside15 said:
Awesome, thank you very much for that. Yeah, I figured that about the bootloader. Does it matter if I have TWRP installed? That's the one main confusing thing to me. How you can have TWRP installed or not installed. I'm used to absolutely having to have TWRP or some other kind of custom recovery installed. But like I said it's been quite a while since I was really able to root/ROM a phone. I was basically forced to move to AT&T and opted for the Active line of Galaxy phones since I have little kids plus even the phones that were rootable and such seemed like more of a hassle than it was worth. The last phone I had that had some good development was probably the LG G3 on T-MOBILE. For some reason the T-MOBILE version had an unlocked bootloader or could be unlocked, don't remember exactly. But then a coworker got a Pixel 2XL and I got the itch again, not knowing how much had really changed though. Ok, I think I've rambled on enough now. Thanks again for the help.
Click to expand...
Click to collapse
Doesn't matter if you have twrp installed or not. When you fastboot the update, it'll wipe it out anyway :good: