Related
I never thought it'd happen to me..
Anyways.
I'm on Virgin Mobile in Canada, just recently unlocked my bootloader and rooted.
The process was bumpy but ultimately successful..ish.
I couldn't actually flash any roms. Not sure if it was because of the bumpy root process,
but every rom would just bootloop and I'd have to restore and deal with HTC Sense.
Great.
I had downloaded a Liquid [somethingorother] ROM from my PC and flashed it, with blind hope.
It was looping, as I half-expected.
I had this crazy idea that my roms were looping because I had neglected to press the "Perm Root" button
on the AIO root tool I had used.
Ecstatic, I rushed up and pressed that button as soon as I could.
The process went off without a hitch, but the next time I tried to boot something odd happened.
Every time I boot the HTC splash screen stating "this is for development purposes only.. etc" pops up.
-the one that would pop up when entering the bootloader - EVERY TIME.
I tried to restore but this splash screen still shows up, then loops on the HTC ONE screen....
AAAAAND that's where I'm at now. I attempted to factory restore from the bootloader, which would
erase my backups and whatnot. I don't know how infamous this issue is but I am unable to mount my storage.
Plenty other people seem to have this issue.
So, is there anything I can do?
You should try to run an RUU, then report back.
Sent from my HTC One S using Xparent Blue Tapatalk 2
invasion2 said:
You should try to run an RUU, then report back.
Sent from my HTC One S using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
I'm actually trying to find one now. I haven't been able to find one for Bell/Virgin wild on the interwebs.
I'm trying to find the mysterious RUU section on the painfully slow HTCdev website..
anyone have a link or something?
http://forum.xda-developers.com/showthread.php?t=1543588
Sent from my HTC One S using Xparent Blue Tapatalk 2
The most common reason for ROMs hanging on boot splash or looping is that you failed to fastboot flash the boot image that comes with the ROM.
The good news is if you can detect the phone in your computer, your phone isn't bricked.
That message you mentioned is normal for all of us flashers
I bet you didn't notice the "tampered" flag or you would have freaked out even more
Sent from my HTC One S
I need help please. I flashed the rom following the instructions and my phone boots but the screen remains all black. I hear a sound when it boot and nothing else. I am trying to reach recovery but I haven't been able by holding volume down + power. Any help please?
---------- Post added at 11:08 AM ---------- Previous post was at 10:58 AM ----------
Never mind I got it fixed. It was all because the boot img wasn't in place yet.
Sorry to beat a dead horse but i think i bricked my phone ! I to have a virgin mobile canada HTC One S but i can't find the ruu for virging mobile I Tried bell and it didn't work thus screwing up my phone. please pleaase please i need help I just got this phone yesterday.
lilsammy11 said:
Sorry to beat a dead horse but i think i bricked my phone ! I to have a virgin mobile canada HTC One S but i can't find the ruu for virging mobile I Tried bell and it didn't work thus screwing up my phone. please pleaase please i need help I just got this phone yesterday.
Click to expand...
Click to collapse
your in the wrong section. If you have the one v from virgin mobile, which code name is primo not ville check here http://www.filefactory.com/f/0eafb9c43276c308/ for ruu and section go here for support http://forum.xda-developers.com/forumdisplay.php?f=1551
or here http://htcruu.com/?dir=Primo
puertoblack2003 said:
your in the wrong section. If you have the one v from virgin mobile, which code name is primo not ville check here http://www.filefactory.com/f/0eafb9c43276c308/ for ruu and section go here for support http://forum.xda-developers.com/forumdisplay.php?f=1551
or here http://htcruu.com/?dir=Primo
Click to expand...
Click to collapse
no please help me. I am positive it is a One S I bought it yesterday from Virgin mobile in Canada. It says one s on the box it doesn't have the hump the one v has on the bottom. I am totally lost and don't know what to do The Bell mobility ruu didn't work for it and it seems like a virgin mobile ruu is none existant
lilsammy11 said:
no please help me. I am positive it is a One S I bought it yesterday from Virgin mobile in Canada. It says one s on the box it doesn't have the hump the one v has on the bottom. I am totally lost and don't know what to do The Bell mobility ruu didn't work for it and it seems like a virgin mobile ruu is none existant
Click to expand...
Click to collapse
Does the your computer recognize the one s
Sent from my Galaxy Nexus using xda premium
lilsammy11 said:
no please help me. I am positive it is a One S I bought it yesterday from Virgin mobile in Canada. It says one s on the box it doesn't have the hump the one v has on the bottom. I am totally lost and don't know what to do The Bell mobility ruu didn't work for it and it seems like a virgin mobile ruu is none existant
Click to expand...
Click to collapse
don't know what to tell you if you got it from virgin mobile i just checked there site http://www.virginmobileusa.com/shop/cell-phones/android-phones/ and they selll the V series. did you buy it form there store/site ? or second hand?
soljafree said:
Does the your computer recognize the one s
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes I think It does because I've tried to use the bell ruu about 5 times and it'll start but then I'll get error 155 a little while into it
puertoblack2003 said:
don't know what to tell you if you got it from virgin mobile i just checked there site http://www.virginmobileusa.com/shop/cell-phones/android-phones/ and they selll the V series. did you buy it form there store/site ? or second hand?
Click to expand...
Click to collapse
Try virginmobile.ca . But yes I just wanted to say I really appreciate you guys's help
lilsammy11 said:
Yes I think It does because I've tried to use the bell ruu about 5 times and it'll start but then I'll get error 155 a little while into it
Try virginmobile.ca . But yes I just wanted to say I really appreciate you guys's help
Click to expand...
Click to collapse
ahhhh i see. ok man your DONE!! becasue that error 155 means that your bootloader is unlocked. and to flash the ruu you would have to relock. but you said you're brick nothing happens to your device?
puertoblack2003 said:
ahhhh i see. ok man your DONE!! becasue that error 155 means that your bootloader is unlocked. and to flash the ruu you would have to relock. but you said you're brick nothing happens to your device?
Click to expand...
Click to collapse
ohhhhh that makes sense, and I think I'm bricked. I'm pretty sure I can run adb commands though. maybe I should try oem lock again command again? this is exactly what the top says
***TAMPERED***
***RELOCKED***
*** Security Warning***
I should point out that when I start the ruu the screen actually goes to a black screen with "htc" on it and that's it. and I tried to lock it again via abd and it says its already locked
---------- Post added at 05:27 AM ---------- Previous post was at 05:15 AM ----------
Ok I should also say that when ever I restart phone it goes right into bootloader. I'm guessing because ruu erased everything ? should i maybe unlock boot loader, root, download stock rom and then try rue again?
lilsammy11 said:
ohhhhh that makes sense, and I think I'm bricked. I'm pretty sure I can run adb commands though. maybe I should try oem lock again command again? this is exactly what the top says
***TAMPERED***
***RELOCKED***
*** Security Warning***
I should point out that when I start the ruu the screen actually goes to a black screen with "htc" on it and that's it. and I tried to lock it again via abd and it says its already locked
---------- Post added at 05:27 AM ---------- Previous post was at 05:15 AM ----------
Ok I should also say that when ever I restart phone it goes right into bootloader. I'm guessing because ruu erased everything ? should i maybe unlock boot loader, root, download stock rom and then try rue again?
Click to expand...
Click to collapse
It it says relocked and its not OEM software on there that's y u keep rebooting into boot loader had that happen on a vivid I had. Try reflashing the ruu
Sent from my Galaxy Nexus using xda premium
Man, I never read anything good anywhere in these forums lol. This phone is so awesome as is, I really don't think it is worth the trouble unlocking and rooting and all. Maybe it is cause only the bad gets posted but there seems to be a lot of it. This phone is definitely meant for the normal person who cares nothing about flashing it seems. I would love to be able to just root it for root-required apps, themes and Volume wake and/or slide to wake but it seems to be more trouble than it's worth.
Cyanogenmod 10 makes this phone 10 times the awesome.
soljafree said:
It it says relocked and its not OEM software on there that's y u keep rebooting into boot loader had that happen on a vivid I had. Try reflashing the ruu
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Sorry I don't quite understand, should I try to getting stock back ? Or just continue to try and get the ruu to work ?
LibertyMonger said:
Man, I never read anything good anywhere in these forums lol. This phone is so awesome as is, I really don't think it is worth the trouble unlocking and rooting and all. Maybe it is cause only the bad gets posted but there seems to be a lot of it. This phone is definitely meant for the normal person who cares nothing about flashing it seems. I would love to be able to just root it for root-required apps, themes and Volume wake and/or slide to wake but it seems to be more trouble than it's worth.
Click to expand...
Click to collapse
Yea I found that out to late, I actually screwed up the phone and somehow saved myself by getting on CM10 then I realized how much I love stock and wanted to go back and now i'm here stuck on bootloader -.-
lilsammy11 said:
Sorry I don't quite understand, should I try to getting stock back ? Or just continue to try and get the ruu to work ?
Yea I found that out to late, I actually screwed up the phone and somehow saved myself by getting on CM10 then I realized how much I love stock and wanted to go back and now i'm here stuck on bootloader -.-
Click to expand...
Click to collapse
Unlock your phone again. Change your CID to HTC__001. Then run an unbranded RUU.
Sent from my locked, tampered ville
Just wondering if anyone has tried to FXZ back after accepting the Update?
Sent from my XT1080 using Tapatalk
Brenardo said:
Just wondering if anyone has tried to FXZ back after accepting the Update?
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Had to do this, but it wasn't intentional. I had to take out specific lines in the XML file to get it to work. The first few lines caused errors so I had to delete them and start at factory.img command to get it to work. I have the edited file if you'd like me to post it. I was messing around with my dev edition and something went wrong and likely I figured out how to restore to stock with the edited file.
What are the odds it will work with a consumer edition?
Sent from my XT1080 using Tapatalk
Brenardo said:
What are the odds it will work with a consumer edition?
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
My guess is it should work. The xml file is the stock img, recovery, data, boot, etc for both the dev and consumer editions. I must say that what I did wasn't intentional and wasn't something I wanted to happen. If you are on the update and want to go back to 12.7.7 you could try this, but if something would happen to go wrong you could potentially brick your phone. It seems unlikely though as I thought I bricked mine and editing the file did indeed return me to 12.7.7 and I flashed the update zip from stock recovery as I had before.
Well I would like to see the edited file if you dont mind
Sent from my XT1080 using Tapatalk
Brenardo said:
Well I would like to see the edited file if you dont mind
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
View attachment 2375754
I deleted everything down to the boot.img. The prior commands come up with an error that I believe is some sort of security or files out of place that doesn't allow you to drop down to a lower firmware. If you are going to try this my suggesting would be to try the full xml and see if you get errors. If you do then try the way I did.
I'll be curious to see how it works for you. This could come in handy to people if they accidentally cause a boot loop. Once the files for 12.15.15 are released they won't have to do this.
theycallmerayj said:
I'll be curious to see how it works for you. This could come in handy to people if they accidentally cause a boot loop. Once the files for 12.15.15 are released they won't have to do this.
Click to expand...
Click to collapse
I can confirm it doesn't work if the update actually completes. Once the system partition is updated, there's no going back.
Sent from my SCH-I605 using Tapatalk
I had the update completed and working and I went back to 12 7.7
Sent from my XT1080 using Tapatalk
theycallmerayj said:
I had the update completed and working and I went back to 12 7.7
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Please enlighten us on how you did it.
bigv5150 said:
Please enlighten us on how you did it.
Click to expand...
Click to collapse
This is what I'm talking about further up in the thread. I was messing around and honestly can't remember what I specifically did but basically I updated to 12.15.15, bricked my phone into a boot loop, and assumed I couldn't do anything until they release the xml file for the update. I tried to 12.7.7 xml file and at first it didn't work. The first few commands give you an error basically saying some sort of security or files won't allow you to drop down to the old firmware. Unfortunately I don't know the exact wording of it. But I edited the xml file to only run the commands from boot.img down which I posted in this thread. Now I do have a dev maxx. I mean I could try it again, but I'd rather not as I have my phone all set up after having to restore to stock.
---------- Post added at 09:48 PM ---------- Previous post was at 09:40 PM ----------
Sorry I can't give more specific details, as I said I didn't intend to do all this so it wasn't something I thought I'd need to remember. I don't post much on here to begin with but I thought what happened to me and how I fixed it could potentially help someone else.
theycallmerayj said:
This is what I'm talking about further up in the thread. I was messing around and honestly can't remember what I specifically did but basically I updated to 12.15.15, bricked my phone into a boot loop, and assumed I couldn't do anything until they release the xml file for the update. I tried to 12.7.7 xml file and at first it didn't work. The first few commands give you an error basically saying some sort of security or files won't allow you to drop down to the old firmware. Unfortunately I don't know the exact wording of it. But I edited the xml file to only run the commands from boot.img down which I posted in this thread. Now I do have a dev maxx. I mean I could try it again, but I'd rather not as I have my phone all set up after having to restore to stock.
---------- Post added at 09:48 PM ---------- Previous post was at 09:40 PM ----------
Sorry I can't give more specific details, as I said I didn't intend to do all this so it wasn't something I thought I'd need to remember. I don't post much on here to begin with but I thought what happened to me and how I fixed it could potentially help someone else.
Click to expand...
Click to collapse
That's cool I wouldn't expect you to try again I think you having a dev phone is what allowed you to do it anyway. I tried to fastboot the system image and it wouldnt take.
bigv5150 said:
That's cool I wouldn't expect you to try again I think you having a dev phone is what allowed you to do it anyway. I tried to fastboot the system image and it wouldnt take.
Click to expand...
Click to collapse
Okay, I thought maybe that had something to do with it. I wouldn't suggest trying it to people anyway cause I was really worried I did brick my phone.
theycallmerayj said:
Okay, I thought maybe that had something to do with it. I wouldn't suggest trying it to people anyway cause I was really worried I did brick my phone.
Click to expand...
Click to collapse
Were you actually running 12.15.15 for a period of time, or did the bootloop occur during the update?
If you were actually running it, then my only conclusion is that the dev edition ignores the partition version check.
I don't recommend anyone on a consumer version try this.
Sent from my SCH-I605 using Tapatalk
I was actually on the update running it.
Sent from my XT1080 using Tapatalk
theycallmerayj said:
I was actually on the update running it.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Must be a dev edition thing then. Mine fails on system version checks for boot, recovery, and system. 2 of those 3 are apparently important.
Sent from my SCH-I605 using Tapatalk
erishasnobattery said:
Must be a dev edition thing then. Mine fails on system version checks for boot, recovery, and system. 2 of those 3 are apparently important.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Yeah it must be. Once they release the xml for 12.15.15 I might be willing to try this again to record the errors to see why I was able to do it. I don't want to do it now because I don't want to take the risk that it won't work.
So i bought me a new used nexus 5 on craigslist from some old chinese guy. He said it wasn't connecting to a network no matter what or whose sim cards he used and how many times he rooted it. the phone is on stock unrooted 4.4.2. I got it on the cheap and was hoping ot fix it up and use it. Any idea what might be wrong with it?
butthurtlocker said:
So i bought me a new used nexus 5 on craigslist from some old chinese guy. He said it wasn't connecting to a network no matter what or whose sim cards he used and how many times he rooted it. the phone is on stock unrooted 4.4.2. I got it on the cheap and was hoping ot fix it up and use it. Any idea what might be wrong with it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2601997
Sounds like the old Chinese guy knew what he was doing.
You don't mention that YOU returned it to stock, you just said it was stock and unrooted. If it is exactly the way he gave it to you I would fastboot flash the stock 4.4.2 images from google and see what that does for you. You could simply have a corrupted file somewhere.
thionylx said:
You don't mention that YOU returned it to stock, you just said it was stock and unrooted. If it is exactly the way he gave it to you I would fastboot flash the stock 4.4.2 images from google and see what that does for you. You could simply have a corrupted file somewhere.
Click to expand...
Click to collapse
Yes when he sold it to me it was stock. I haven't returned it to stock, ive rooted it and tried diff rom/basebad combos and still nothing. Theres also a weird persistent notification that i cant swipe away that says Nework (ROGERS) Unvailable....even when i reset and try a Telus sim! Is there an easier way to flash stock besides fastboot? I am pretty new to this gig and am not too comfortable with fastboot
butthurtlocker said:
Yes when he sold it to me it was stock. I haven't returned it to stock, ive rooted it and tried diff rom/basebad combos and still nothing. Theres also a weird persistent notification that i cant swipe away that says Nework (ROGERS) Unvailable....even when i reset and try a Telus sim! Is there an easier way to flash stock besides fastboot? I am pretty new to this gig and am not too comfortable with fastboot
Click to expand...
Click to collapse
This being a Nexus you have little or no risk of doing damage by playing around. My original Droid X was always threatening to self destruct if you messed up the tiniest little step. Spending a couple hours learning about and installing Fastboot and ADB will be the best investment you can make. Once you learn to use them the fear of messing something up is gone. You can flash roms at will without worry as you can always return to stock and start over.
Flash a Google stock image
Sent from my Nexus 5 using Tapatalk
---------- Post added at 08:15 PM ---------- Previous post was at 08:14 PM ----------
All nexus 5 regardless of carrier should be unlocked
Sent from my Nexus 5 using Tapatalk
butthurtlocker said:
Yes when he sold it to me it was stock. I haven't returned it to stock, ive rooted it and tried diff rom/basebad combos and still nothing. Theres also a weird persistent notification that i cant swipe away that says Nework (ROGERS) Unvailable....even when i reset and try a Telus sim! Is there an easier way to flash stock besides fastboot? I am pretty new to this gig and am not too comfortable with fastboot
Click to expand...
Click to collapse
Just follow method one of this. It's easy http://forum.xda-developers.com/showthread.php?p=47156064
PS, why did you buy a device thinking you could fix it of you don't know fastboot commands
thionylx said:
This being a Nexus you have little or no risk of doing damage by playing around. My original Droid X was always threatening to self destruct if you messed up the tiniest little step. Spending a couple hours learning about and installing Fastboot and ADB will be the best investment you can make. Once you learn to use them the fear of messing something up is gone. You can flash roms at will without worry as you can always return to stock and start over.
Click to expand...
Click to collapse
Thanks man thats a good point!
jd1639 said:
Just follow method one of this. It's easy http://forum.xda-developers.com/showthread.php?p=47156064
PS, why did you buy a device thinking you could fix it of you don't know fastboot commands
Click to expand...
Click to collapse
Oh thats perfect bro thanks, nice and straightforward. Will see how this goes after school. I just htought it was maybe a radio issue or rom issue so i thought i could flash around and fix it. Also it was only 70 bucks and in mint condition aside from this problem so I didn't think it was a bad deal
Sounds like the ESN/IMEI is bad.
Hard to fix ATM.
Sent from my Nexus 5 using Tapatalk
Dragn4rce said:
Sounds like the ESN/IMEI is bad.
Hard to fix ATM.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Oh really?how does that happen!? The imei isn't blacklisted or anything and shows up as a registered imei. I tried flashing stock image and still no dice! Looks like I'm doomed. Any other suggestions?
That usually happens when the following steps occur.
The original owner unlocked bootloader.
They put twrp on it and did a full backup including ESN
The device developed a fault so they RMA'd it.
They restored the backup from the faulty device into the new one.
The ESN is device specific and by restoring it onto a different device you end up with not being able to connect to a network.
You can check by going into the about phone menu in the settings. If it displays your imei then I don't think this is your problem.
Have you tried popping the back cover off and checking the antennae contacts
Sent from my Nexus 4 using xda app-developers app
The good news is the parts are worth more than the $70 you paid for it. Find someone with a busted screen and sell it.
jd1639 said:
The good news is the parts are worth more than the $70 you paid for it. Find someone with a busted screen and sell it.
Click to expand...
Click to collapse
That's a good idea.
Thanks for the advice. Ended up selling it this morning as is to an eager repair junkie. Btw my imei was showing up and the antennas were all in place so still a mystery what was up with it!
Sent from my LG-G2 using xda app-developers app
This the only phone I've ever had a problem with, and I am asking for some help from the community.
I've got a Cricket HTC One SV. K2PLC_CL. Android 4.2.2, which should be Jellybean.
I just wanted to get root. I know there aren't any custom ROMs (what I wouldn't give to remove all the bloatware, though...)
I followed a few guides that I'm sure everyone's looked at. My bootloader IS unlocked. When I tried flashing a recovery (I have two or three to try, one's even labelled for Cricket. They're CWM, though), I was unable to boot into it to install Superuser. Since then, I've earned the "TAMPERED" flag.
Have I done something terribly wrong? Can someone please instruct me on how to get root, and to fix my recovery?
Since I somehow managed to fail, I would be extremely appreciative if someone would be so kind as to spell it out, or just give me step-by-step instructions.
Since booting into recovery, my phone freezes if I shut it down while it's plugged into the charger... Oddly enough.
It's not your fault, it's because the new hboot, which came with 422 update!
Follow the link in my singnature, you will find there a working recovery and a SuperSu.zip for 422.
old.splatterhand said:
It's not your fault, it's because the new hboot, which came with 422 update!
Follow the link in my singnature, you will find there a working recovery and a SuperSu.zip for 422.
Click to expand...
Click to collapse
Ahh, thank you so much.
I'm looking right now, and unfortunately, I noticed the TWRP recovery isn't for my SV. Is there a K2PLC_CL around, or am I able to use one of those?
AnalogConspiracy said:
Ahh, thank you so much.
I'm looking right now, and unfortunately, I noticed the TWRP recovery isn't for my SV. Is there a K2PLC_CL around, or am I able to use one of those?
Click to expand...
Click to collapse
it still works for your device, go ahead and use it
Sent from my C525c using Tapatalk
russellvone said:
it still works for your device, go ahead and use it
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Will do, thank you very much. I'll let you know how it goes!
And I can flash my superuser through their recovery, correct?
AnalogConspiracy said:
Will do, thank you very much. I'll let you know how it goes!
And I can flash my superuser through their recovery, correct?
Click to expand...
Click to collapse
use superSU.......but yes
Sent from my C525c using Tapatalk
russellvone said:
use superSU.......but yes
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Thanks everyone, my phone has now been rooted!
However, I'd like to use a couple of apps, and was promptly alerted that I need to obtain S-OFF. I've been looking at Rumrunner... Should I use it?
Plug phone in while it's charged on, USB debug is on, and let it do it's thing?
edit: I ran it, and it looked great... But at the end, it gave a line along the lines of.
[TTTTT*******] or something.
I booted into Hboot, it's still on.
AnalogConspiracy said:
Thanks everyone, my phone has now been rooted!
However, I'd like to use a couple of apps, and was promptly alerted that I need to obtain S-OFF. I've been looking at Rumrunner... Should I use it?
Plug phone in while it's charged on, USB debug is on, and let it do it's thing?
edit: I ran it, and it looked great... But at the end, it gave a line along the lines of.
[TTTTT*******] or something.
I booted into Hboot, it's still on.
Click to expand...
Click to collapse
Make sure its the universal one, and insure you do not have any password set on your phone. Any kind of lockscreen security needs to be disabled. Basically, you need to be able to access your phone without the hassle of something preventing it. This stuff will disrupt the process.
Sent from my C525c using Tapatalk
Modding.MyMind said:
Make sure its the universal one, and insure you do not have any password set on your phone. Any kind of lockscreen security needs to be disabled. Basically, you need to be able to access your phone without the hassle of something preventing it. This stuff will disrupt the process.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Also (I think) make sure the fast boot option in Settings > Power is unchecked
palmtree5 said:
Also (I think) make sure the fast boot option in Settings > Power is unchecked
Click to expand...
Click to collapse
Thank you for putting up with my ignorance thus far, guys.
However, I:
- Am running Universal Rumrunner.
- Have already un-checked the Fastboot option.
- Have no current lock on my phone. Security>Screen Lock>None
- Have USB debug enabled.
Edit: - Have HTC Sync removed.
- Have no firewall, granting access to sojo.
- Have granted superuser/root access to ADB.
In my previous post, I stated I ran Rumrunner. It was with the aforementioned settings.
I did make sure to do this before touching anything.
This is why I'm stumped.
Is there any information I can provide that might assist you guys?
AnalogConspiracy said:
Thank you for putting up with my ignorance thus far, guys.
However, I:
- Am running Universal Rumrunner.
- Have already un-checked the Fastboot option.
- Have no current lock on my phone. Security>Screen Lock>None
- Have USB debug enabled.
Edit: - Have HTC Sync removed.
- Have no firewall, granting access to sojo.
- Have granted superuser/root access to ADB.
In my previous post, I stated I ran Rumrunner. It was with the aforementioned settings.
I did make sure to do this before touching anything.
This is why I'm stumped.
Is there any information I can provide that might assist you guys?
Click to expand...
Click to collapse
use an unsecure kernel
Sent from my C525c using Tapatalk
russellvone said:
use an unsecure kernel
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
I'll have to look for one.
However, I managed to get Rumrunner working properly.
What did I do?
... I re-downloaded the same universal version that I have. Then, I ran it.
I don't know what wasn't making it function properly in the first place, but it has this time.
My HTC One SV from Cricket is officially S-OFF.
Thank you very much for your help, and contributing to the education of my phone.
Hi I'm new here to kind of been into rooting my phones since I heard if it I've always figured it out on my own but the HTC sv im stumped I'd like to root and unlock who knows what from there but I've had this phone for a while can anyone help?
Sent from my C525c using xda app-developers app
---------- Post added at 07:47 AM ---------- Previous post was at 07:43 AM ----------
And if anyone knows anything about LG optimous 9 I have one them never turned it on yet need a battery are they any better cause I like the HTC but I'd like to throw it as far as possible love the phone but needs to come unlocked
Sent from my C525c using xda app-developers app
wytaske34 said:
Hi I'm new here to kind of been into rooting my phones since I heard if it I've always figured it out on my own but the HTC sv im stumped I'd like to root and unlock who knows what from there but I've had this phone for a while can anyone help?
Sent from my C525c using xda app-developers app
---------- Post added at 07:47 AM ---------- Previous post was at 07:43 AM ----------
And if anyone knows anything about LG optimous 9 I have one them never turned it on yet need a battery are they any better cause I like the HTC but I'd like to throw it as far as possible love the phone but needs to come unlocked
Sent from my C525c using xda app-developers app
Click to expand...
Click to collapse
HTC One SV:
First off, make sure your bootloader is unlocked.
www.htcdev.com/bootloader/
You do have to make an account. Please do so, and follow their instructions to the letter.
Second. Flash TWRP recovery, as seen: http://forum.xda-developers.com/showthread.php?t=2292432 (This link is also in old.splatterhand's signature.)
Third, run Rumrunner Universal -- the latest version, and then you should be set.
As for the requirements -- you will see them as you seek these topics. Everything is literally on that XDA link I sent -- it's also in old.splatterhand's signature, again.
wytaske34 said:
Hi I'm new here to kind of been into rooting my phones since I heard if it I've always figured it out on my own but the HTC sv im stumped I'd like to root and unlock who knows what from there but I've had this phone for a while can anyone help?
Sent from my C525c using xda app-developers app
---------- Post added at 07:47 AM ---------- Previous post was at 07:43 AM ----------
And if anyone knows anything about LG optimous 9 I have one them never turned it on yet need a battery are they any better cause I like the HTC but I'd like to throw it as far as possible love the phone but needs to come unlocked
Sent from my C525c using xda app-developers app
Click to expand...
Click to collapse
You have a K2_CL. I see that in your comment signature. Make sure you DO NOT use anything that pertains to K2_PLC_CL, K2_UL, and/or K2_U! Their partitions are different and unless you know what you are doing you may bring about some serious issues down the road lol.
Ultimately, everything you need you can find in old.splatterhands index as already mentioned. The custom recovery must pertain to K2_CL or it will not work.
Step one: unlock bootloader
Step two: flash custom recovery
Step three: make a backup using custom recovery
Step four: flash a flashable.zip with supersu to gain root.
Step five: the rest is up to you based on your wants, needs, and desires.
If you are not sure of something, please ask!
Sent from my C525c using Tapatalk
i got this pm and i thot it was worth everyone to see. while i do not recomend turning any device s on,a verizon device that is not unlockable via htcdev is of much more importance,as the only thing that can rescue it is a new enough,signed RUU.
it really is not worth the risk,i promise.
nicholi2789 said:
scotty1223 said:
nicholi2789 said:
Hey there, Sorry to bother you with a PM like a noob, but I just have a quick question for you. I have just received a Certified like new replacement M8 from Verizon because my original one had a manufacturer defect. My original one was S-OFF, rooted, with custom recovery and the latest firmware (1.55.605.2) from Verizon. I'm trying to get it back to as close to stock as possible so Verizon doesn't try and say I modified it and mak me pay for it. I already un-rooted it, flashed stock recovery, and took the latest OTA so my radios match my software version. Then I followed this thread: http://forum.xda-developers.com/showthread.php?t=2708571
to re-lock the bootloader and set the lock status flag. It says locked again in fastboot.
The only thing I have left is the S-OFF that displays in fastboot. I'm trying to find a way to reset that, or at least modify it so it shows S-ON. That way if by some weird chance a Verizon employee boots it to fastboot it will show completely stock and S-ON.
Now i've found this thread: http://forum.xda-developers.com/showthread.php?t=2475216 for resetting the S-OFF flag. I posted in it and asked if it would work on the M8 and nobody could give me an answer. XDA member brymaster5000 told me to ask you and that you could provide an answer.
So finally, my question is, will this fastboot command "fastboot oem writesecureflag 3" work to set my M8 back to S-ON? I know it works on the M7 but nobody can tell me for sure on the M8.
Thanks alot for your time.
Nick
Click to expand...
Click to collapse
I would very strongly recommend that you do not turn s on. Phones came s off ,so leaving out that way is not an issue.
Turning s on may open a can of worms that you cannot recover from,and then you're paying for a phone for sure.
As long as your stock rom, recovery and locked you're good to go
Sent from my HTC One VX using Tapatalk
Click to expand...
Click to collapse
What do you mean phones came s-off? Verizon sent people m8s that already were s-off? It just seems like a super obvious indication that the device was modified. Your not the first person that has said that going back to s-on is a bad idea, so I will listen and not tempt fate. But iam curious, What can happen by doing that command that could cause such problems? And don't stock RUUs return you to s-on? Or do they just reset everything else but s-off?
Click to expand...
Click to collapse
before any phone is released,batches are sent off to testers and these devices are always s off. i have owned several factory s off devices,and there is no way of proving the phone you have did not come this way. further, large phone resellers are able to use factory htc diagnostic files to clear security data(sim lock,s off,cid/mid),wich again is a legitimate reason a phone is s off.finding s off in the bootloader is not by any means a "super obvious" indication of having been messed with.
turning the phone s on could cause the tampered flag to reset(we dont completely understand all the things that trip it) or you could end up locked into bootloader with a security warning if the boot,system or recovery are not stock enough. either of these things ARE super obvious indicators that you have messed with it,and tried to hide it.
in the case of the security warning,the only course of action is to:
1)run a signed ruu(wich must meet many criteria since youre now s on)
or
2)re-unlock the bootloader. as you know,using htcdev to unlock is not possible with vzw
an ruu does not change/update the partition where the secutity flag lives and thus will NOT turn you s on.
Thanks for the write up, this should help some users decide. Wish it was as easy as flashing a pit file in Odin . That's one of the main reasons I've yet to root/s-off. HTC devices still confuse me xD
Sent from my HTC6525LVW using Tapatalk
wtoj34 said:
Thanks for the write up, this should help some users decide. Wish it was as easy as flashing a pit file in Odin . That's one of the main reasons I've yet to root/s-off. HTC devices still confuse me xD
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Agreed great write up... in reference to rooting the m8 it is very easy with weak sauce app I also find the s-off to be easier as well compared to Sammy devices using Odin. with my s4 like with the m8 there was no need for a pc for root but weak sause app is easier then using commands in a terminal emulator. Just my two sense.
thunderbls said:
Agreed great write up... in reference to rooting the m8 it is very easy with weak sauce app I also find the s-off to be easier as well compared to Sammy devices using Odin. with my s4 like with the m8 there was no need for a pc for root but weak sause app is easier then using commands in a terminal emulator. Just my two sense.
Click to expand...
Click to collapse
You have missed the point... If you are locked into the bootloader with a security warning and s-on, you can not use weak sauce and firewater
Sent from my HTC One VX using Tapatalk
People need to realize that verizon reps and techs see hundreds of phones, they don't know the details of every device. The security and bootloader status is obvious to us because it's our device and we know everything about it. To a samsung person they won't know WTF your talking about.
Scotty, Would one be able to save their device if they had S-Off, modified the CID, then used HTCDev to get their unlock token before embarking on an endeavor to re-lock the phone? In theory would they be able to use the unlock token even after the CID was changed back and the security flags turned on?
l7777 said:
Scotty, Would one be able to save their device if they had S-Off, modified the CID, then used HTCDev to get their unlock token before embarking on an endeavor to re-lock the phone? In theory would they be able to use the unlock token even after the CID was changed back and the security flags turned on?
Click to expand...
Click to collapse
Not really... More later
Sent from my HTC One VX using Tapatalk
scotty1223 said:
Not really... More later
Sent from my HTC One VX using Tapatalk
Click to expand...
Click to collapse
Yes, I misinterpreted the comment as general ease of use which makes me look like an idiot given the reason for the response.... my apologies and note to self read xda after nap lol.
l7777 said:
Scotty, Would one be able to save their device if they had S-Off, modified the CID, then used HTCDev to get their unlock token before embarking on an endeavor to re-lock the phone? In theory would they be able to use the unlock token even after the CID was changed back and the security flags turned on?
Click to expand...
Click to collapse
Not really... More later
Sent from my HTC One VX using Tapatalk
Click to expand...
Click to collapse
the prollem is that the vzw cid/mid are blocked(by vzws request ) at htcdev. changing the cid and/or mid will let you get an unlock_code.bin that will officially unlock the bootloader,but this token is only good while the phone contains these same parameters. i.e., you cant get yourself a token,then change the cid and mid back to stock and have the "safety net" of a token in case of a catastrophic security warning. cid,mid,esn,etc must all stay same in order for the token to continue working.
Q:"well,what if i just leave the cid/mid at something different?"
A:that may work,but it may set the tampered flag if the phone realizes that those partitions no longer match. since the cid and mid live in write protected partitions,its also possible what once s is on and the phone starts checking things in its boot sequence,that the processor may freak out,and go into a "do not boot" mode when signitures do not match what they should. (read "do not boot" as: pretty affective hard brick only recoverable by jtag)
plus,even if the phone did boot,and did not set the tampered flag, the phone is not stock,and may fail OTAs or have other issues that may affect users the phone is sent back out to,or may give it away that you have modified it.
the fact is,that these phones are not checked very well,as was said above. the chance of it being noticed that the s off phone is even different than others is slim to none,and it is quite possible that the phone will make it back out into the wild as a refurb without any sort of refurbishing process. if you thot all phones were hooked to a master computer that completely reset things,checked hardware,flashed the newest firmware,and reset things like supercid,simlock and s off,youd be mistaken. due to this fact,it is my strong opinion that patched hboots(displaying incorrect info of locked and s on),or incorrect cid/mids are extremely unethical and should never be sent in to fraud htc or the carriers,espeically since it may affect other users. returning the phone to a stock,locked s-off state is honest,and will not affect a future users esperince. the device will OTA and funtion normally and the unsavy user will never even know they have a device that is special
hope that cleared it up some.
also,sorry if either of my replies earlier were rude,they were not intended to be,im only able to text to speech short replies while im at work.
scotty1223 said:
the prollem is that the vzw cid/mid are blocked(by vzws request ) at htcdev. changing the cid and/or mid will let you get an unlock_code.bin that will officially unlock the bootloader,but this token is only good while the phone contains these same parameters. i.e., you cant get yourself a token,then change the cid and mid back to stock and have the "safety net" of a token in case of a catastrophic security warning. cid,mid,esn,etc must all stay same in order for the token to continue working.
Q:"well,what if i just leave the cid/mid at something different?"
A:that may work,but it may set the tampered flag if the phone realizes that those partitions no longer match. since the cid and mid live in write protected partitions,its also possible what once s is on and the phone starts checking things in its boot sequence,that the processor may freak out,and go into a "do not boot" mode when signitures do not match what they should. (read "do not boot" as: pretty affective hard brick only recoverable by jtag)
plus,even if the phone did boot,and did not set the tampered flag, the phone is not stock,and may fail OTAs or have other issues that may affect users the phone is sent back out to,or may give it away that you have modified it.
the fact is,that these phones are not checked very well,as was said above. the chance of it being noticed that the s off phone is even different than others is slim to none,and it is quite possible that the phone will make it back out into the wild as a refurb without any sort of refurbishing process. if you thot all phones were hooked to a master computer that completely reset things,checked hardware,flashed the newest firmware,and reset things like supercid,simlock and s off,youd be mistaken. due to this fact,it is my strong opinion that patched hboots(displaying incorrect info of locked and s on),or incorrect cid/mids are extremely unethical and should never be sent in to fraud htc or the carriers,espeically since it may affect other users. returning the phone to a stock,locked s-off state is honest,and will not affect a future users esperince. the device will OTA and funtion normally and the unsavy user will never even know they have a device that is special
hope that cleared it up some.
also,sorry if either of my replies earlier were rude,they were not intended to be,im only able to text to speech short replies while im at work.
Click to expand...
Click to collapse
Excellent info, I wondered if the unlock token was tied to the cid/mid. My personal preference is once the phone is unlocked it stays that way. It's my device and I'll take the responsibility for whatever happens to it barring some kind of hardware defect.
l7777 said:
Excellent info, I wondered if the unlock token was tied to the cid/mid. My personal preference is once the phone is unlocked it stays that way. It's my device and I'll take the responsibility for whatever happens to it barring some kind of hardware defect.
Click to expand...
Click to collapse
I agree completely.
Sent from my HTC One using Tapatalk
scotty1223 said:
I agree completely.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Anyone at the point of "return" should at least trying running my RUUish zip from boot loader before even thinking about relocking or s-on.
?. Glad to see you throwing some support over here
Sent from my Nexus 7 using Tapatalk
dottat said:
Anyone at the point of "return" should at least trying running my RUUish zip from boot loader before even thinking about relocking or s-on.
?. Glad to see you throwing some support over here
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Lol I try and throw support wherever its needed
So far, no m8 ruus yet. Hopefully some start popping up.
As far as I'm concerned,back to stock sequence is this:
While still rooted:
-return cid/mid to.stock
-reset tampered
-lock bootloader
Then:
-run release keys ruu
-collect underpants
-???
-proffit!
When ruu is not available,restore stock boot,system and recovery from backups.
After that's done allow phone to ota to current
Not sure why folks try and make it more complex than that
Sent from my HTC PG09410 using Tapatalk 2
How do you reset tampered?
scotty1223 said:
Lol I try and throw support wherever its needed
So far, no m8 ruus yet. Hopefully some start popping up.
As far as I'm concerned,back to stock sequence is this:
While still rooted:
-return cid/mid to.stock
-reset tampered
-lock bootloader
Then:
-run release keys ruu
-collect underpants
-???
-proffit!
When ruu is not available,restore stock boot,system and recovery from backups.
After that's done allow phone to ota to current
Not sure why folks try and make it more complex than that
Sent from my HTC PG09410 using Tapatalk 2
Click to expand...
Click to collapse
Paulb787 said:
How do you reset tampered?
Click to expand...
Click to collapse
Search this forum for a thread. I'm at work, I can't link it at the moment
Sent from my HTC One VX using Tapatalk
scotty1223 said:
So far, no m8 ruus yet. Hopefully some start popping up.
Not sure why folks try and make it more complex than that
Sent from my HTC PG09410 using Tapatalk 2
Click to expand...
Click to collapse
sorta?
For those who stay s-off and have issues I put together an ruu of sorts that includes the ota firmware that will get users out of a sticky situation. ?
Between the two of us we can probably fix most software problems as long as users stay s-off once s-off!!!
Sent from my Nexus 7 using Tapatalk
Ha, it's funny that you posted our PM conversation. It's kinda embarrassing but at least I asked someone who knew before just doing it, messing it up, then screaming to the forums for help. And while i am by no means a beginner Android power user, HTC devices are just a little bit different than the Samsung devices I am used to. Though there is alot of good information in this PM conversation that alot more people should know. Glad it could be of use! And thanks for taking the time to reply to my PMs Scotty. I appreciate that.
nicholi2789 said:
Ha, it's funny that you posted our PM conversation. It's kinda embarrassing but at least I asked someone who knew before just doing it, messing it up, then screaming to the forums for help. And while i am by no means a beginner Android power user, HTC devices are just a little bit different than the Samsung devices I am used to. Though there is alot of good information in this PM conversation that alot more people should know. Glad it could be of use! And thanks for taking the time to reply to my PMs Scotty. I appreciate that.
Click to expand...
Click to collapse
I didn't mean to embarrass you. They were good questions I thot everyone should read. I should have asked you,and can edit them if you wish.
Sent from my HTC PG09410 using Tapatalk 2
scotty1223 said:
I agree completely.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Nah I wasn't really embarrassed. Haha. I just meant that it's slightly embarrassing that I knew so little about HTC devices, but not a big deal or anything. You were right to post it though, there is some good information there that will do lots of people good.
dottat said:
sorta?
For those who stay s-off and have issues I put together an ruu of sorts that includes the ota firmware that will get users out of a sticky situation. ?
Between the two of us we can probably fix most software problems as long as users stay s-off once s-off!!!
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Definately a great rescue resource. I just want to make sure that folks understand that since it is unsigned,it will do them no good if they are s on,and stuck in bootloader with a security warning.
As you said,they must stay s off to benefit.(further supporting the point of this thread- don't turn s on)
Sent from my HTC PG09410 using Tapatalk 2
I was going to relock/S-On my defective M8 before returning it. I didn't have time though, and ended up just sending back only wiped and un-rooted, although I don't think /system was 100% stock. VZW sent me a text:
VZW FREE MSG: Thank You! The defective device you recently returned has been received by Verizon Wireless.
Click to expand...
Click to collapse
That was several weeks ago, haven't heard a thing since. I'm assuming they didn't care it was unlocked, or they are very slow at processing the devices.