Related
I just booted into the bootloader just for curiosity and it says locked and tampered. However I have never unlocked my bootloader and have not tampered with it. I thought that it only says tampered if you unlock the bootloader. Anyone else noticed this?
Sent from my HTC VLE_U using XDA
so did I
where did you buy it
any chance of buying a returned one
I bought it at tmobile on launch day so I don't think it is returned.
Sent from my HTC VLE_U using XDA
Tampered means non-official software such as root. Unlocking the bootloader does not cause it to say tampered.
Sent from my HTC VLE_U using xda premium
I don't have root. This is how my phone came from tmobile. Can anyone else that has not unlocked there bootloader or rooted their phone check to see if your phone says tampered?
Sent from my HTC VLE_U using XDA
If a stock rom is flashed you won't have root but it will still say tampered on the hboot,
Sent from my HTC VLE_U using xda premium
Yes but I have not flashed anything. this is how it came from tmobile. Do you think my phone was messed with before I bought it?
Sent from my HTC VLE_U using XDA
If you havent touched it, Meaning you havent flashed a recovery nor a ROM or root.. and your phone is 100%stock...
I would send it back, and say wtf is this ? lol, Or if you are going to mod it eventually, leave it as it is.. root it and flash a custom ROM now
Yeah I do plan on rooting eventually but it makes me a little curious as to why the hell it says this when I have not messed with it at all. It makes me wonder who has? Now if I go to take it back tmobile will think I did it.
Sent from my HTC VLE_U using XDA
they could do, but its obvious you havent because the bootloader is locked, you cant flash stuff with a locked bootloader.. If they do ask questions, act dumb
'wtf is bootloader ?' 'wtf is htcdev?' you should be fine, You've only just got the phone..
Yeah that is true. I will probably exchange it tomorrow. There is probably nothing wrong with it but it kinda gives me a funny feeling because it already says tampered. Like I said I plan to root but it makes me wonder if anyone else bought a phone like this.
Sent from my HTC VLE_U using XDA
McQueefus said:
Yeah that is true. I will probably exchange it tomorrow. There is probably nothing wrong with it but it kinda gives me a funny feeling because it already says tampered. Like I said I plan to root but it makes me wonder if anyone else bought a phone like this.
Click to expand...
Click to collapse
The phone should not come like that!
It appears that you have been sold a refurbished phone as new. In the UK that is illegal! I don't know where you are, but would think that it would also be illegal wherever you live. I would certainly return it. Rather than plead ignorance, I would say that you googled the 'tampered' issue and know that it means the phone does not have stock software installed. Kick up a real stink and ask for compensation - get them to give you a free case or something for it.....?
McQueefus said:
I don't have root. This is how my phone came from tmobile. Can anyone else that has not unlocked there bootloader or rooted their phone check to see if your phone says tampered?
Sent from my HTC VLE_U using XDA
Click to expand...
Click to collapse
I will let you know tonite--get mine then--
But, as my first post here, I think it is used--hope not
joshnichols189 said:
Tampered means non-official software such as root. Unlocking the bootloader does not cause it to say tampered.
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
I agree that it should not cause it to say tampered, However I also attempted the unlock with the purpose to root and it came back with tampered. This caused the boot-loader to lock and now I have a soft-brick. Now I cant flash anything. Has anyone found a solution to this yet? I am able to re-lock it but still shows tampered and the boot-loader locked up.
If you flash something it will always say tampered even if you relock the bootloader.
Sent from my HTC VLE_U using xda premium
got mine tonite, no tampered, even after unlocking bootloader--
Are you sure? Got a screenshot of the bootloader?
Maybe you got delivered a ENG HBOOT device by some weird chance or something. That would help devs temendously.
Cause I have not yet heard of a properly unlocked device that does not say tampered. To the contrary, everyone left and right is trying hard to get rid of it...
not even sure how to do screenshot,
It may only say tampered when you relock it if I am not mistaken. I have a rezound that did not say tampered but just unlocked because I had yet to relock boot loader (I eventually switched to an eng boot loader). As for the op, I would return the phone because it is quite possible someone unlocked it to play around with it wherever you bought it from. What they did could cause problems down the line, not of your own doing.
Sent from my Galaxy Nexus using xda premium
rugmankc said:
not even sure how to do screenshot,
Click to expand...
Click to collapse
Pressing power and home button at the same time might do the trick
Edit: but of course that won't help if your in fast boot lol
Sent from my Galaxy Nexus using xda premium
I'm not sure how to get back to stock as I purchased my phone off craigslist and it has CM10 on it with a custom recovery (TWRP or something I believe). I would like to get back to completely stock as if I purchased the phone brand new from AT&T. I searched through the forums and found stock RUU's but I'm not sure which one to use or how to flash it.
I would appreciate any help at all. Thank you.
Give it time and your question will be answer in here
Sent from my HTC One X using xda premium
---------- Post added at 07:46 PM ---------- Previous post was at 07:41 PM ----------
Also this need to be posted in the question section to be answer.
Sent from my HTC One X using xda premium
Check your hboot version ...if 1.14 relock bootloader then run the 2.20 ruu...if your on 1.09 or 1.11 I guess if you wanna go back to stock and have no desire of rooting then just relock and run the 2.20 ruu
Not really sure why you would want to be back at bone stock seeing as the warranty is gone with no chance to reverse it. Even if you get the boot loader relocked it states Relocked on the bootloader screen. Just flash a stock rom... and keep super user so you can remove all AT&T's bloat. The phones memory is already small as it is, no reason to waste it on crap apps.
Mrkrackie said:
Not really sure why you would want to be back at bone stock seeing as the warranty is gone with no chance to reverse it. Even if you get the boot loader relocked it states Relocked on the bootloader screen. Just flash a stock rom... and keep super user so you can remove all AT&T's bloat. The phones memory is already small as it is, no reason to waste it on crap apps.
Click to expand...
Click to collapse
Selling it, buying nexus 4
brian85 said:
Selling it, buying nexus 4
Click to expand...
Click to collapse
Ah I gotcha, well seeing how you can't ever return to true stock (the day you first got it) I'd just flash a stock ROM and call it a day. Trying to relock the boot loader is a waste of time. Since it will make no difference.
Sent from my One X using xda app-developers app
Mrkrackie said:
Ah I gotcha, well seeing how you can't ever return to true stock (the day you first got it) I'd just flash a stock ROM and call it a day. Trying to relock the boot loader is a waste of time. Since it will make no difference.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Sure you can. Just change the cid hex in mmcblk0p4
Only difference is bootloader will say relocked and not locked
Sent from my One X using xda app-developers app
i wouldnt change cid back. id just ruu then give the guy your selling it to the unlock token incase the buyer wants to mod it. save the person some time. if you want to just run the 1.85 ruu you can still get it from htc http://dl3.htc.com/application/htc_onex_att_RUU_1.85.520.3_US.exe
absolutelygrim said:
Sure you can. Just change the cid hex in mmcblk0p4
Only difference is bootloader will say relocked and not locked
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Which is still not true stock. You cannot get the boot loader back to factory locked. The warranty is gone and cannot be recovered so these steps that are being taken are useless and make extra hurdles for the buyer if they plan to root. I'd recommend just selling it with a stock ROM on it with the boot loader left unlocked.
Sent from my HTC One XL using xda app-developers app
Songlambr37 said:
Who else in the world still use the manly Dell Venue?
who can help us upgrade it to 4.0?
Click to expand...
Click to collapse
Nice Grammar, wrong section all together.
http://forum.xda-developers.com/forumdisplay.php?f=1013
Is stock recovery required before flashing a RUU?
no, all you need to do is get into bootloader and "fastboot oem lock" then flash ruu.
mbh87 said:
Is stock recovery required before flashing a RUU?
Click to expand...
Click to collapse
i suppose you have twrp recovery right?
if you have, then just flash device with cleanrom. or stock.
i personally prefer cleanrom, cause its deoxed.
cleanrom is odexed
So, I've been trying to use this method to root by AT&T HTC One X
http://forum.xda-developers.com/showthread.php?t=1644167
Attached is the software information of my phone...
I run the .bat file and everything works and my phone reboots three times but then I try to load SuperSU but it says su binary code not installed which leads me to believe that the phone isn't rooted?
Any advice on how to get it to work?
Cheers,
What Hboot version do you have? Go into boot loader by turning the phone off, hold the volume down button and press the power button. Let us know what it says?
Sent from my One X using xda premium
subarudroid said:
what hboot version do you have? Go into boot loader by turning the phone off, hold the volume down button and press the power button. Let us know what it says?
Sent from my one x using xda premium
Click to expand...
Click to collapse
hboot-2.14.000
Did you buy that phone second hand? Is the bootloader locked? Unlocked? Relocked? Does it say s-on? Or S-off?
Sent from my One X using xda app-developers app
No, I bought it new. Its locked and s-on
akaeavaian said:
No, I bought it new. Its locked and s-on
Click to expand...
Click to collapse
Well that's odd since you're software says 1.73 but your hboot is of 3.18.
Sent from my One X using xda app-developers app
nah hboot is 2.14
Post a photo of your bootloader screen, because what you're describing is virtually impossible.
The only way you could be on hboot 2.14 and 1.73 software is if you got a refurb that was previously on 2.20 or earlier, was rooted, unlocked, s-off, had the 3.18 ruu run, then the 1.73 stock rom installed, then relocked and s-on, and no one at AT&T bothered to clean up the mess.
iElvis said:
Post a photo of your bootloader screen, because what you're describing is virtually impossible.
The only way you could be on hboot 2.14 and 1.73 software is if you got a refurb that was previously on 2.20 or earlier, was rooted, unlocked, s-off, had the 3.18 ruu run, then the 1.73 stock rom installed, then relocked and s-on, and no one at AT&T bothered to clean up the mess.
Click to expand...
Click to collapse
Lmao that's sounds exactly like what would happen.
Sent from my One X using xda premium
That sounds complicated
but here you go...
Looks like youre going to have to wait. no exploit for att on that version. Pisses me off that Rogers can still unlock and s-off. I want to say horrible things about att. Can we turn this into a AT&T bashing thread now?
Sent from my One X using xda premium
subarudroid said:
Looks like youre going to have to wait. no exploit for att on that version. Pisses me off that Rogers can still unlock and s-off. I want to say horrible things about att. Can we turn this into a AT&T bashing thread now?
Sent from my One X using xda premium
Click to expand...
Click to collapse
can telestra too? telus can aswell.
Again another reason to bash AT&T
Sent from my One X using xda premium
akaeavaian said:
That sounds complicated
but here you go...
Click to expand...
Click to collapse
I'm sorry, even seeing it, I don't believe it. I just don't see how this could be possible.
In any case, the 1.73 root method might work, but with that hboot, you can't change cid, and thus can't unlock or flash a custom recovery, which means you can't get permanent root. You're stuck where you are, wherever that is.
They don't send ota's for the hboot right? I was on 2.20 few and 1.14 hboot. And got it refurb back in December
Sent from my Carbon-ize Evita using xda-developers app
Ota does affect the hboot... Yes. But there's not an Ota that changes just the hboot. This must have been previously rooted. Most likely this phone was at some point unlocked and rooted, the person who returned it most likely updated to 3.18 after bootloader unlock/soff, had issues, Relocked and s-on, ruu to 1.73, returned to HTC where HTC fixed and repackaged without updating the software.
*edit* sorry that makes no sense.. Ruu would have downgraded the hboot too.. Just woke up -_-
We may never know what happened to thus phone lol.
Sent from my One X using xda app-developers app
exad said:
Ota does affect the hboot... Yes. But there's not an Ota that changes just the hboot. This must have been previously rooted. Most likely this phone was at some point unlocked and rooted, the person who returned it most likely updated to 3.18 after bootloader unlock/soff, had issues, Relocked and s-on, ruu to 1.73, returned to HTC where HTC fixed and repackaged without updating the software.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Aha! So it couldn't have been new. Unless he had warranty. something isn't right.
Sent from my Carbon-ize Evita using xda-developers app
Yup, he's got an ICS Rom with a locked 2.14 hboot. Now that's f'd up.
exad said:
We may never know what happened to thus phone lol.
Click to expand...
Click to collapse
I think it's possible to get that configuration:
-phone was originally on ICS
-root, unlock, and s-off
-apply 3.17 or 3.18 ruu to get 2.14 hboot. This would also remove the TAMPERED flag
-flash rooted stock 1.73 rom
-edit p3 or flash scotty's zips to relock and restore LOCKED text
-remove root
-restore s-on
-return phone to AT&T
I just don't see why anyone would do it or how it would survive the refurb process.
soo...err....is there anything I can do? I got it through Costco though...if that changes anything...
I currently have S-ON with SuperCID, and I'm trying to get S-OFF with stock AT&T CID. I've heard that it's a fairly simple process to change the CID ("fastboot oem writecid HTC_001"), but HTC_001 is for the unbranded international version, and I'm having a hard time finding the code for the AT&T version, which I suppose I failed to write down before overwriting with SuperCID. Hope someone can help? Also, should I be s-ON or S-OFF to write the CID?
bikeracer4487 said:
I currently have S-ON with SuperCID, and I'm trying to get S-OFF with stock AT&T CID. I've heard that it's a fairly simple process to change the CID ("fastboot oem writecid HTC_001"), but HTC_001 is for the unbranded international version, and I'm having a hard time finding the code for the AT&T version, which I suppose I failed to write down before overwriting with SuperCID. Hope someone can help? Also, should I be s-ON or S-OFF to write the CID?
Click to expand...
Click to collapse
You can only S-OFF with super CID 11111111
After S-OFF you can write it back to the default of CWS__001 for AT&T, but there is no advantage to doing so. You can do whatever you like regardless of what your CID is after S-OFF. I set mine to R00T_001 after for example. (must be 8 characters)
Just noticed your other thread and see why you want the default CID. If you're selling it, make sure your cid is currently 11111111 then S-OFF then you can use that command to change the cid to default. If you're going to sell it, after S-OFF, I'd just format the SD card and run the 3.18 RUU and then power it off after so the person you sell it to will have a fresh start.
exad said:
After S-OFF you can write it back to the default of CWS__001 for AT&T, but there is no advantage to doing so.
Click to expand...
Click to collapse
From what I understand, CID can be changed once from SuperCID to something else, without s-off.
The OP wants to sell his phone, per this thread: http://forum.xda-developers.com/showthread.php?t=2251955
I suggested either changing from SuperCID, or achieving S-off, so the next owner doesn't unintentionally brick the phone by trying to install the 3.18 OTA or RUU (since he is currently SuperCID and S-on).
Not sure why he started this thread, I would have just answered the AT&T CID question in the other thread.
redpoint73 said:
From what I understand, CID can be changed once from SuperCID to something else, without s-off.
The OP wants to sell his phone, per this thread: http://forum.xda-developers.com/showthread.php?t=2251955
I suggested either changing from SuperCID, or achieving S-off, so the next owner doesn't unintentionally brick the phone by trying to install the 3.18 OTA or RUU (since he is currently SuperCID and S-on).
Not sure why he started this thread, I would have just answered the AT&T CID question in the other thread.
Click to expand...
Click to collapse
Sorry, the other thread was started because I couldn't turn my phone on, and was becoming unrelated to original post, thought it would be prudent to create a new thread. Really appreciate your help though.
Just a heads up, I bricked my first TELUS HOXL eventhough I had changed my CID back to the default prior to RUUing. May have been a fluke but yeah do with this info what you will.
UGGGHHH, this is getting frustrating...had to root the phone to get to S-OFF, so I used the X-FACTOR exploit, but when I tried to get S-OFF (http://forum.xda-developers.com/showthread.php?t=2155071) I got the first 2 adb command off but the second one said it couldn't find 'su' so I assumed to root hadn't worked. So I decided it would just be easiest to go back to CyanogenMod and start the whole process over. Only when I tried to unlock the bootloader again, I found that it wouldn't stick. It would SAY it was successful and reboot the phone, but when I would reboot to bootloader it would say "relocked". SO decided to run an RUU, only now the hboot was up to 2.14 from the S-OFF flashing, so I decided to run the 3.15 RUU instead of the 2.20, and that SEEMED to work fine, except that now I'm right back to where I was with not being able to turn the phone on, and I tried my previous trick of the Vol Down + Power...
EDIT: Aaaand, no LED when charging...
bikeracer4487 said:
UGGGHHH, this is getting frustrating...had to root the phone to get to S-OFF, so I used the X-FACTOR exploit, but when I tried to get S-OFF (http://forum.xda-developers.com/showthread.php?t=2155071) I got the first 2 adb command off but the second one said it couldn't find 'su' so I assumed to root hadn't worked. So I decided it would just be easiest to go back to CyanogenMod and start the whole process over. Only when I tried to unlock the bootloader again, I found that it wouldn't stick. It would SAY it was successful and reboot the phone, but when I would reboot to bootloader it would say "relocked". SO decided to run an RUU, only now the hboot was up to 2.14 from the S-OFF flashing, so I decided to run the 3.15 RUU instead of the 2.20, and that SEEMED to work fine, except that now I'm right back to where I was with not being able to turn the phone on, and I tried my previous trick of the Vol Down + Power...
EDIT: Aaaand, no LED when charging...
Click to expand...
Click to collapse
That's a brick. Do you have a linux boot disk? if not, create a linux boot disk or usb and then try the unbrick evita thread. If you can get past step 3, you should be able to unbrick. if not, Sorry to hear.
exad said:
That's a brick. Do you have a linux boot disk? if not, create a linux boot disk or usb and then try the unbrick evita thread. If you can get past step 3, you should be able to unbrick. if not, Sorry to hear.
Click to expand...
Click to collapse
Hm, not having much luck so far, but I AM seeing QHSUSB_DLOAD in the device manager...
bikeracer4487 said:
Hm, not having much luck so far, but I AM seeing QHSUSB_DLOAD in the device manager...
Click to expand...
Click to collapse
Yeah that bid brick I believe. Get live USB stick running Linux. All you need is small USB stick like 2 or 4 GB. Then download pen drive USB image creator. And run Linux from that. Then exad mentioned a thread to look into. I recommend an Ubuntu based distro. I use Linux mint
Sent from my Carbon-ize Evita using xda-developers app
There's a guide to making a bootable Linux usb in q&a if you need it.
Sent from my One X using xda app-developers app
exad said:
There's a guide to making a bootable Linux usb in q&a if you need it.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Yeah, booting from Linux isn't a problem, but as I said, I was trying to put it to stock so I could sell it...but then I discovered it was still under warranty (with just a week left), so instead of messing around in Linux I took it to an AT&T warranty center on my way home and they just straight up replaced with a new One X... Everything turned out better than expected
bikeracer4487 said:
Yeah, booting from Linux isn't a problem, but as I said, I was trying to put it to stock so I could sell it...but then I discovered it was still under warranty (with just a week left), so instead of messing around in Linux I took it to an AT&T warranty center on my way home and they just straight up replaced with a new One X... Everything turned out better than expected
Click to expand...
Click to collapse
Great!! But is it on the new unrootable software?
ImagioX1 said:
Great!! But is it on the new unrootable software?
Click to expand...
Click to collapse
Yup :-/ Software version 3.18, 2.14 hboot, S-ON, and CID of CWS__001... But since I won't be keeping this phone, it'll be someone else's problem...
bikeracer4487 said:
Yup :-/ Software version 3.18, 2.14 hboot, S-ON, and CID of CWS__001... But since I won't be keeping this phone, it'll be someone else's problem...
Click to expand...
Click to collapse
LoL!!
Sent from Xparent Red using my Venomized Evita
It is technically better to have a brand new in box phone for selling. That's awesome! Congrats! I wish Canadian carriers warranted phones like they do in the US. You only get manufacturer warranty here.
Sent from my One X using xda app-developers app
exad said:
It is technically better to have a brand new in box phone for selling. That's awesome! Congrats! I wish Canadian carriers warranted phones like they do in the US. You only get manufacturer warranty here.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
You could pay the 7 bucks a month for device protection then drive over it with a car when you brick it
Sent from my VENOMized HoxL
area51avenger said:
You could pay the 7 bucks a month for device protection then drive over it with a car when you brick it
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
Or just keep it and say that you lost it. And of you are able to fix it, sell it and you still keep a new phone.
Sent from my Carbon-ize Evita using xda-developers app
Pft, that's an extra 252$ within my contract period. Forget that noise! I doubt I'll even have this phone in a year lol.
Sent from my One X using xda app-developers app
---------- Post added at 10:17 AM ---------- Previous post was at 10:06 AM ----------
Herc08 said:
Or just keep it and say that you lost it. And of you are able to fix it, sell it and you still keep a new phone.
Sent from my Carbon-ize Evita using xda-developers app
Click to expand...
Click to collapse
They don't warrant lost phones here.
Sent from my One X using xda app-developers app
exad said:
Pft, that's an extra 252$ within my contract period. Forget that noise! I doubt I'll even have this phone in a year lol.
Sent from my One X using xda app-developers app
---------- Post added at 10:17 AM ---------- Previous post was at 10:06 AM ----------
They don't warrant lost phones here.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Oh wow. Didn't know that
Sent from my Carbon-ize Evita using xda-developers app
exad said:
They don't warrant lost phones here.
Click to expand...
Click to collapse
They don't cover lost phones on warranty anywhere. He was talking about insurance, not a warranty.
I am currently stuck in the bootloader. To make matters worse, I relocked to RUU and am stuck at Sending with that. I am Super CID which I think is the problem. To make matters even worse, I no longer have my unlock_code.bin file.
Is there any hope for my phone? Also, the RUU process has completely wiped my phone. Thanks for any input in advance. I have searched and searched for an answer but haven't found anything useful.
Sent from my HTC One XL using XDA Premium 4 mobile app
You haven't given enough information, what are you trying to do? You could just unlock your bootloader again.
Sent from my Evita
timmaaa said:
You haven't given enough information, what are you trying to do? You could just unlock your bootloader again.
Sent from my Evita
Click to expand...
Click to collapse
How can I unlock my bootloader without the unlock_code.bin file? Update. I reverted back to original CID CWS__001 and am going to try and run the RUU again.
I tried to s-off my wife's phone and it screwed it up somehow (rather I screwed it up). I simply wanted to take it back to stock to start fresh and now I am stuck in the bootloader with no Rom and a locked phone.
Sent from my HTC One XL using XDA Premium 4 mobile app
//JavaJ said:
How can I unlock my bootloader without the unlock_code.bin file? Update. I reverted back to original CID CWS__001 and am going to try and run the RUU again.
I tried to s-off my wife's phone and it screwed it up somehow (rather I screwed it up). I simply wanted to take it back to stock to start fresh and now I am stuck in the bootloader with no Rom and a locked phone.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You would just go to htcdev like you did in the first place and go through the unlock process again. But, you can't do that now because you just changed the CID back to CWS__001 which is blocked by htcdev. And I'm guessing you didn't succeed in getting s-off? If so, you've just used the one and only time you can change the CID without s-off to change it to a CID which is blocked, which means you have no way to unlock the bootloader again, ever. I hope your original plan was to stay stock because that's your only option now. Maybe that's for the best though, you seem to be doing things without fully comprehending what you're doing or the potential catastrophic results.
Sent from my Evita
timmaaa said:
You would just go to htcdev like you did in the first place and go through the unlock process again. But, you can't do that now because you just changed the CID back to CWS__001 which is blocked by htcdev. And I'm guessing you didn't succeed in getting s-off? If so, you've just used the one and only time you can change the CID without s-off to change it to a CID which is blocked, which means you have no way to unlock the bootloader again, ever. I hope your original plan was to stay stock because that's your only option now. Maybe that's for the best though, you seem to be doing things without fully comprehending what you're doing or the potential catastrophic results.
Thanks for your input. I appreciate it. Can I at least ruu the 3.18 now and get back to stock... That's better than bootloader I suppose. By the way, how could I have unlocked in the state I was in?
Ruu is stuck at sending for some time now.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
//JavaJ said:
timmaaa said:
You would just go to htcdev like you did in the first place and go through the unlock process again. But, you can't do that now because you just changed the CID back to CWS__001 which is blocked by htcdev. And I'm guessing you didn't succeed in getting s-off? If so, you've just used the one and only time you can change the CID without s-off to change it to a CID which is blocked, which means you have no way to unlock the bootloader again, ever. I hope your original plan was to stay stock because that's your only option now. Maybe that's for the best though, you seem to be doing things without fully comprehending what you're doing or the potential catastrophic results.
Thanks for your input. I appreciate it. Can I at least ruu the 3.18 now and get back to stock... That's better than bootloader I suppose. By the way, how could I have unlocked in the state I was in?
Ruu is stuck at sending for some time now.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you have a locked bootloader and the correct CID there should be no harm in running the RUU. The unlock process (from memory, I could be wrong) doesn't require the phone to be booted into an os, it's all taken care of while the phone is in bootloader. That's kinda irrelevant now anyway as it isn't possible anymore.
Are you using the usb cable that came with the phone? You can try using a different usb port, usually the ones on the back of the pc tower are the best.
May I ask, how exactly do you think the s-off process screwed up the phone? It either succeeds or fails, and there should be no serious repercussions from either.
Sent from my Evita
Click to expand...
Click to collapse
Ever since I ran the s off process I couldn't copy anything to the sd card, I.e. to flash a new Rom. I feel like an idiot for changing the cid back now. I ran the zip for s off and I waited an hour or so and it never went throufh
Sent from my HTC One XL using XDA Premium 4 mobile app
//JavaJ said:
Ever since I ran the s off process I couldn't copy anything to the sd card, I.e. to flash a new Rom. I feel like an idiot for changing the cid back now. I ran the zip for s off and I waited an hour or so and it never went throufh
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It sounds to me like you might have actually done a factory reset from bootloader which corrupts the sd card. The s-off process has no ability to change the sd card. Did you have HTC drivers and adb/fastboot all installed when you tried the s-off process? That's probably why it didn't work.
The corrupted sd card might be why the RUU won't work, can you still get into TWRP recovery? If so, you can use the mount menu to mount it to your pc and format it. If not, you might seriously be in trouble. The combination of these things you've done have possibly rendered the device completely useless. If this if the case, I hope this has been a learning experience. It's really important to have a firm understanding of what you're doing (and the results and potential risks) when modifying your device. It looks like you've rushed into all this without understanding it all properly.
In any case, let me know about what I asked about above and I'll do my best to see if there's a way out of this.
Sent from my Evita
timmaaa said:
It sounds to me like you might have actually done a factory reset from bootloader which corrupts the sd card. The s-off process has no ability to change the sd card. Did you have HTC drivers and adb/fastboot all installed when you tried the s-off process? That's probably why it didn't work.
The corrupted sd card might be why the RUU won't work, can you still get into TWRP recovery? If so, you can use the mount menu to mount it to your pc and format it. If not, you might seriously be in trouble. The combination of these things you've done have possibly rendered the device completely useless. If this if the case, I hope this has been a learning experience. It's really important to have a firm understanding of what you're doing (and the results and potential risks) when modifying your device. It looks like you've rushed into all this without understanding it all properly.
In any case, let me know about what I asked about above and I'll do my best to see if there's a way out of this.
Sent from my Evita
Click to expand...
Click to collapse
Took your advice about the usb port. Switched it to the back and the ruu worked. Will I be able to run the root exploit again? Yes, this definitely has been a learning experience. Coupled with my lack of sleep and overall frustration I made some bad moves. Thanks for your patience and help though. Much appreciated.
And no, I could not get back into recovery after I relocked it. It would send me right back to the bootloader. Also, I did do a factory reset from the bootloader. Believe me, taking mental notes all the way here.
Sent from my HTC One XL using XDA Premium 4 mobile app
Now that you have a working os, you could be able to use the exploit again to unlock the bootloader etc. Just take it slowly though, do some reading so you gain a bit of knowledge. And if you have any questions, don't be afraid to ask.
Sent from my Evita
Unlocked and rooted. Again. Thanks for your help. Leary of trying to s off again though
Sent from my HTC One XL using XDA Premium 4 mobile app
Very glad to see you got it all working again. S-off might seem daunting now, but it's a pretty straight forward process as long as you follow the instructions exactly.
Sent from my Evita
timmaaa said:
Very glad to see you got it all working again. S-off might seem daunting now, but it's a pretty straight forward process as long as you follow the instructions exactly.
Sent from my Evita
Click to expand...
Click to collapse
Yes, I have done it before, on my One X. Not quite sure what went wrong. Maybe the issue with my wife's phone was preexisting and reared it's ugly head in the process. I have been rooting and nodding phones for years. I am not a complete noob. I am experienced in java programming and have created many interesting applications for my phone. Perhaps I should take my java knowledge and automate my s off experience.
Sent from my HTC One XL using XDA Premium 4 mobile app
If you're looking for an automated method, I saw this just before. It's brand new but it looks to have some great tools incorporated. I prefer the manual method myself but many people will love this.
Sent from my Evita
timmaaa said:
If you're looking for an automated method, I saw this just before. It's brand new but it looks to have some great tools incorporated. I prefer the manual method myself but many people will love this.
Sent from my Evita
Click to expand...
Click to collapse
Very nice found Tim.....:thumbup:
Swyped From BlueICESense_JBE
timmaaa said:
If you're looking for an automated method, I saw this just before. It's brand new but it looks to have some great tools incorporated. I prefer the manual method myself but many people will love this.
Sent from my Evita
Click to expand...
Click to collapse
Appreciate it. I don't mind working from the command line either. Could my trouble have had anything to do with being plugged into the front of the cpu, for s off that is? Was getting stuck at sending with the flash zip command.
Sent from my HTC One XL using XDA Premium 4 mobile app
//JavaJ said:
Appreciate it. I don't mind working from the command line either. Could my trouble have had anything to do with being plugged into the front of the cpu, for s off that is? Was getting stuck at sending with the flash zip command.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah that was probably it, try again using the rear port and it'll probably be fine.
Sent from my Evita
timmaaa said:
Yeah that was probably it, try again using the rear port and it'll probably be fine.
Sent from my Evita
Click to expand...
Click to collapse
Just wanted to let you know that I went through s off and all went well. Only thing I can think was the problem was that either there was a pre existing corruption on the phone, or the usb port I was using.
Sent from my HTC One XL using XDA Premium 4 mobile app
It could have been anything. It's becoming more and more apparent that different things halt the process for different users. It makes it really difficult to troubleshoot when helping someone through the process. In the end you got it though which is great.
Sent from my Evita