Full disclosure, this isn't my phone and I'm helping a coworker who did some things. The phone was originally purchased without service as she was switching from AT&T to T-mobile and didn't have it setup yet.
Incident: The phone was unlocked and rooted when last night she used a "toolkit" (I have no idea which one and she said she deleted the folder with everything), then locked it with the toolkit and used the fastboot oem unlock to get back in. When the stock rom was installed again the screen wouldn't work and I was able to navigate with a OTG mouse connected. All of the custom roms work fine as far as the screen goes but the stock one is like it's missing a driver. The other issue here is the SIM card doesn't pickup a network, I verified the Access Point is setup correctly and tried with both the LTE (fast) setup and regular. It's entirely possible that the radio was hosed to start with and we didn't find out until the sim card was purchased on Monday. At this point I'd just like to get it back to FULL stock and see if she can do anything with the Warranty (not sure if this is really possible yet). So, on to things I've tried.
1. Display Issue on Stock, I read this could be a kernel issue and attempted to flash several Stockish roms from here. Also the kernel from mugetsu666. That kernel a long with the other 3-4 stock roms from page 1. Nothing resolved.
2. No Signal. While going through the stock and custom roms all I really need is the signal to work. The PA install had the wrong APN settings and I updated them with the Defaults. No change, so I moved on to radios, maybe that's it. Flashed all the radios from here and a couple other random ones from the individual rom I was using. Nothing.
3. Ok, at this point I just want back to stock. This phone is toast and I'm tired of dealing with it for the day. Found the t-mobile ruu file here and attempted to run it as admin on a windows 7 and 8 machines. The bootloader was locked before attempting this and I tried in fastboot or just the phone being on. All I get is error 170 which is the usb connection issue. Fastboot does recognize my device so the RUU should pickup, now i'm really stuck.
Needless to say it's hasn't been a productive day at work. Any assistance is greatly appreciated. THANKS!!
I see you tired the T-Mobile ruu have your tried offival att ruu yet?
Sent from inside the T.A.R.D.I.S
joselv456 said:
I see you tired the T-Mobile ruu have your tried offival att ruu yet?
Sent from inside the T.A.R.D.I.S
Click to expand...
Click to collapse
You should run the revone s-off before you do anything after unlocking the bootloader. The first RUU should have been ATT since it is an ATT phone, like the last poster mentioned. After you unlock the bootloader, run revone to get s-off, then get superCID and run whatever RUU you like ATT,GPE, or T-Mo.
This one?. The link is dead. Can I use another supercid by at or M7?
Thanks for the help. I'm really a Samsung user so this is new
C Murder said:
You should run the revone s-off before you do anything after unlocking the bootloader. The first RUU should have been ATT since it is an ATT phone, like the last poster mentioned. After you unlock the bootloader, run revone to get s-off, then get superCID and run whatever RUU you like ATT,GPE, or T-Mo.
Click to expand...
Click to collapse
Bootloader unlocked
s-off complete
CID-11111111
I'm running the Signed2 from this list.
http://www.androidruu.com/index.php?developer=M7
Error 170, USB issue. Fastboot can see the device but the RUU can't, odd.
Edit: Running the RUU when the phone is booted to PA gets pasted the error 170. Now it's an error 155 and it's stuck on the HTC logo. Powering it off and it's still hosed.
Sooooo, I think there is more wrong here than a simple RUU update. I noticed under the *** UNLOCKED *** that the model is M7_UL, which i'm finding is a Europe model. I'm toast.. warm buttery toast i think.
Side note: Don't offer to help coworkers if you haven't worked on a phone like this before.
I have m7ul which was originally a t-mobile device when I got it used. I flashed the GE ruu no problem. You should be ok with that device.
Sent from my HTC One using Tapatalk 4
kronikwisdom said:
Bootloader unlocked
s-off complete
CID-11111111
I'm running the Signed2 from this list.
http://www.androidruu.com/index.php?developer=M7
Error 170, USB issue. Fastboot can see the device but the RUU can't, odd.
Edit: Running the RUU when the phone is booted to PA gets pasted the error 170. Now it's an error 155 and it's stuck on the HTC logo. Powering it off and it's still hosed.
Click to expand...
Click to collapse
Did you try running the tmobile RUU.exe from your pc. I know it's in the Tmobile HTC One forum. I'm sure it's here somewhere too. The kernels and recovery are there too, with guides to take you back to stock.
C Murder said:
Did you try running the tmobile RUU.exe from your pc. I know it's in the Tmobile HTC One forum. I'm sure it's here somewhere too. The kernels and recovery are there too, with guides to take you back to stock.
Click to expand...
Click to collapse
Yes, I've tried the tmobile RUU from these forums.
I've just made things worse now it seems because I updated the CID back to "T-MOB010" and now the recovery image won't stick. Seems like I'm missing something else from the boot.img but I've tried to flash the original firmware.zip on these forums. So tired of this thing.
Monday and I'm still at this. After relocking my boot loader per the request of the owner I'm unable to unlock it now. Requested a new code and that didn't change anything. The command to unlock from fastboot completes and writes successfully but the screen doesn't popup on my phone to accept the unlock.
Fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 kb)... <--- not sure if that's correct, the file is actually 256b but maybe it's under 1 so it doesn't show.
OKAY [ 0.150s ]
writing 'unlocktoken'...
OKAY [ 0.010s ]
finished. total time: 0.160s
this phone is going further down hill.
last ditch effort and I ran the RUU from Tmobile on an old XP machine, worked. back to stock.. not sure what to say but i'm tired of looking.. haha
I don't know why she needed to do all that soff in the first place ... This device doesn't require soff to flash roms or even soff to flash tmobile roms on the att m7 or vise versa
It's a lot like nexus model the boot.img flashes In roms soff is usually needed to do that on other htc devices not the One
Simple carrier unlock and Bootloader unlock with recovery is all you need to flash any Rom onto any m7 besides sprint and vzw
Soff and supercid doesnt seem like it was necessary in her case
HTC is touchy stuff takes reading 10 times over before attempting anything...
If we had a samsung Odin method we would be golden ..
Glad it's fixed
Sent from my HTC One using xda app-developers app
Related
Hi Guys,
I feel strange, in that I have been rooting phones since the g1 (and literally every other android device on tmobile & sprint since then) and I've never run into this:
I was running Eternity rom, but wanted to send the device in for a warranty repair, so I followed the available instructions to take my Evo3d back to stock. Everything seemed to go fine, except that now the phone will ONLY boot into the bootloader.
I did re-lock the bootloader as per the instructions here on xda, so now at the top of the screen i get:
Relocked
Security Warning!
and S-On ( i was never s-off)
Does anyone know of a way to get me back up and running? Btw, it was the PG86IMG.zip ruu 2.17 u flashed.
Im in a big jam here now...no phone for work purposes
wards.jfasa said:
Hi Guys,
I feel strange, in that I have been rooting phones since the g1 (and literally every other android device on tmobile & sprint since then) and I've never run into this:
I was running Eternity rom, but wanted to send the device in for a warranty repair, so I followed the available instructions to take my Evo3d back to stock. Everything seemed to go fine, except that now the phone will ONLY boot into the bootloader.
I did re-lock the bootloader as per the instructions here on xda, so now at the top of the screen i get:
Relocked
Security Warning!
and S-On ( i was never s-off)
Does anyone know of a way to get me back up and running? Btw, it was the PG86IMG.zip ruu 2.17 u flashed.
Im in a big jam here now...no phone for work purposes
Click to expand...
Click to collapse
im going to say a bad ruu re unlock and start over i dont know if its on xda too but on scotts roms site it has info to lock without the re locked showing good luck
I am having the same problem, but I found a way around it. If I boot the kernel through fastboot it will boot up. (You'd need to re unlock). My hboot doesn't really work anymore..
------
3(d)vo one s
Newts my hero.
evo bryan said:
im going to say a bad ruu re unlock and start over i dont know if its on xda too but on scotts roms site it has info to lock without the re locked showing good luck
Click to expand...
Click to collapse
Im not even sure at this point how to re-unlock it. i am wondering if i should have flashed to an older ruu though.
How do I extract the kernel from the ruu? or is there a download available? I have searched....just cannot find it.
wards.jfasa said:
How do I extract the kernel from the ruu? or is there a download available? I have searched....just cannot find it.
Click to expand...
Click to collapse
flashimage gui is able to do it inside android, im guessing it stores it in a tempory folder, let me see if i can find the temp folder where it stores before rebooting to flash it...........brb
did you check this post http://forum.xda-developers.com/showthread.php?t=1627897
This helped me out when I was Juopunutbear S-OFF'ing my phone. But I was at Hboot 1.50.
http://androidforums.com/evo-3d-all...mware-upgrade-ruu-flash-unbricking-guide.html
Pretty good guide.
wards.jfasa said:
Hi Guys,
I feel strange, in that I have been rooting phones since the g1 (and literally every other android device on tmobile & sprint since then) and I've never run into this:
I was running Eternity rom, but wanted to send the device in for a warranty repair, so I followed the available instructions to take my Evo3d back to stock. Everything seemed to go fine, except that now the phone will ONLY boot into the bootloader.
I did re-lock the bootloader as per the instructions here on xda, so now at the top of the screen i get:
Relocked
Security Warning!
and S-On ( i was never s-off)
Does anyone know of a way to get me back up and running? Btw, it was the PG86IMG.zip ruu 2.17 u flashed.
Im in a big jam here now...no phone for work purposes
Click to expand...
Click to collapse
The security warning is because you are using a custom rom so will not be able to use the RUU through the bootloader.
What you need to do is download the RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00. 1216_signed.exe from here
http://forum.xda-developers.com/showpost.php?p=24268786&postcount=209
If you then run that exe while your phone is in fastboot and connected to your pc it will factory reset your phone and put you back on stock rom and kernel.
Not my first time around the block I did this with hboot 1.5 the only thing i can think of is HTCDEV.com sent me a F**ked up file.
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.000s]
finished. total time: 0.156s
and WTF nothing happens no menu pops up to unlock or anything
I sent in the full and correct no space unlock code to htcdev.com
This is iratating
I had the same thing happen. No clue how to make it work. Earlier hboot maybe...
Sent from my PG86100 using xda premium
Did you take the OTA?
Even if you didn't, I had the same problem.
What I had to do to fix it is run the RUU.
http://forum.xda-developers.com/showpost.php?p=30106576&postcount=20
Then do the HTC unlock crap again. It will then work.
You'll know because your phone will display a pop-up asking you if you want to unlock or not.
Didn't take the ota..
Sent from my PG86100 using xda premium
I would try it anyways. Can't hurt.
Im having the same problem. I am trying to root my Wife Evo 3D Sprint and when I push the unlock tocken, I dont get the splash screen on the phone to perform the unlock. After I type the command, the phone just sits there.
She did take the OTA and is on HBoot 1.58.
I cant get any of the RUUs to work because the boatloader and all the software on the phone is newer and the RUUs just fail on start.
hypersonicx said:
Im having the same problem. I am trying to root my Wife Evo 3D Sprint and when I push the unlock tocken, I dont get the splash screen on the phone to perform the unlock. After I type the command, the phone just sits there.
She did take the OTA and is on HBoot 1.58.
I cant get any of the RUUs to work because the boatloader and all the software on the phone is newer and the RUUs just fail on start.
Click to expand...
Click to collapse
Have you tried the 2.89 RUU that was linked in post #3 above? I flashed it after using virus's firmware upgrade and taking the Sprint ICS OTA and it still ran fine for me. It should be the same as the OTA, but I have more confidence in the RUU.
ramjet73
halfaddict said:
Not my first time around the block I did this with hboot 1.5 the only thing i can think of is HTCDEV.com sent me a F**ked up file.
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.000s]
finished. total time: 0.156s
and WTF nothing happens no menu pops up to unlock or anything
I sent in the full and correct no space unlock code to htcdev.com
This is iratating
Click to expand...
Click to collapse
FOUND SOLUTION..............
You have to download the RUU that matches the HTC Software on your phone. Go to settings > about > scroll down to Software Version and google search the RUU that matches.
Enable USB Debugging and let phone sit at home screen.
Run the RUU exe from withing windows on your PC wait for it to finish and and it will wipe phone in the process.
After it is done, boot to fastboot and run the HTC Unlock Token command again and this time you will get the prompt on the cell phone screen.
I spent 6 hours plus trying to root my wife phone wile tetherd from my Epic Touch GS2.
Samsung side of the world is a WHOLE lot easier. Everything is done within Oden for Samsung devices.
Anyway, there you go guys!
hypersonicx said:
FOUND SOLUTION..............
Click to expand...
Click to collapse
That's what I was recommending, except you don't have to relock your bootloader before running the RUU and unlock it after if you are S-OFF. And here's the downloads for the current RUU so others don't have to Google it.
Glad it worked for you.
ramjet73
apperantely people didnt read the htcdev website while unlocking. it clearly states it doesnt work properly unless on a 2.17.651.5 rom
htcdev.com said:
HTC has identified a known issue that may be experienced by some users with a Sprint EVO 3D that shipped with version 2.08.651.2, even if it was updated to a newer software version via FOTA. When attempting to unlock, a blank screen appears on the device after step 12 in the instructions and the process does not complete. As a workaround for users who experience this issue, we suggest you upgrade the ROM to 2.17.651.5 first via OTA then download and install the RUU from the table below to fix the issue before attempting the unlock process. This issue will also be fixed in the ICS update scheduled for EVO 3D.
Click to expand...
Click to collapse
t3project said:
apperantely people didnt read the htcdev website while unlocking. it clearly states it doesnt work properly unless on a 2.17.651.5 rom
Click to expand...
Click to collapse
That's odd, because the OP of this thread stated that it failed with hboot 1.5, which would indicate that he was already on the 2.17.651.5 build.
In any case, it appears that HTC unlock wants a pure stock configuration, so running either the 2.17 or 2.89 RUU before flashing the token should work.
ramjet73
ramjet73 said:
That's odd, because the OP of this thread stated that it failed with hboot 1.5, which would indicate that he was already on the 2.17.651.5 build.
In any case, it appears that HTC unlock wants a pure stock configuration, so running either the 2.17 or 2.89 RUU before flashing the token should work.
ramjet73
Click to expand...
Click to collapse
no, he stated he could unlock with 1.5 but couldn't unlock with 1.58.
hypersonicx said:
Im having the same problem. I am trying to root my Wife Evo 3D Sprint and when I push the unlock tocken, I dont get the splash screen on the phone to perform the unlock. After I type the command, the phone just sits there.
She did take the OTA and is on HBoot 1.58.
Click to expand...
Click to collapse
t3project said:
no, he stated he could unlock with 1.5 but couldn't unlock with 1.58.
Click to expand...
Click to collapse
And 1.58 is the stock bootloader of the official Sprint ICS build, which is where HTC said it would be fixed. Of course it depends on how he got the 1.58 bootloader but the OTA should have been fine, and at least one person said they had problems unlocking after taking the OTA.
ramjet73
ramjet73 said:
And 1.58 is the stock bootloader of the official Sprint ICS build, which is where HTC said it would be fixed. Of course it depends on how he got the 1.58 bootloader but the OTA should have been fine, and at least one person said they had problems unlocking after taking the OTA.
ramjet73
Click to expand...
Click to collapse
yea, they said it should be but it isnt. i cannot unlock mine either on 1.58 after installing the firmware updates but im already s-off so i just went back to the eng 1.04hboot since my current rom doesnt depend on 1.58 atm.
t3project said:
yea, they said it should be but it isnt. i cannot unlock mine either on 1.58 after installing the firmware updates but im already s-off so i just went back to the eng 1.04hboot since my current rom doesnt depend on 1.58 atm.
Click to expand...
Click to collapse
The firmware updates don't update you 100% to the 2.89 build. You need to flash the 2.89 RUU to do that, as has already been pointed out in this thread, and for some reason the HTC unlock appears to work after that. I really don't know what the difference is between taking the OTA and flashing the RUU is, but they should be the same.
For someone like you that is already S-OFF, you could always flash the JuopunutBear 1.58.5858 bootloader if you need to run the 2.89 kernel and get most of the benefits of the ENG bootloader. However, that bootloader will not work properly with GB and AOSP ROM's.
ramjet73
i know this man!!! lol
t3project said:
i know this man!!! lol
Click to expand...
Click to collapse
t3project said:
apperantely people didnt read the htcdev website while unlocking. it clearly states it doesnt work properly unless on a 2.17.651.5 rom
Click to expand...
Click to collapse
That's good. Now you also know that flashing the 2.89.651.2 RUU.exe will let you do the HTC unlock with the 1.58 bootloader.
ramjet73
t3project said:
yea, they said it should be but it isnt. i cannot unlock mine either on 1.58 after installing the firmware updates but im already s-off so i just went back to the eng 1.04hboot since my current rom doesnt depend on 1.58 atm.
Click to expand...
Click to collapse
I concur. I'm not a novice when it comes to unlocking bootloaders & rooting phones. I've unlocked more bootloaders through htcdev.com than I can count & this gentleman is absolutely right! HTC really needs to get it together! Samsung devices are so much easier to work with. You don't run into these stupid little problems with Samsung phones. Usually, what goes for one Samsung device goes for all!
I digress, but anyhow, I'm well aware that reinstalling the operating system on an EVO 3D via an RUU will allow the token that you get from htcdev.com to work, and I have used this fix several times in the past on the last Gingerbread OS (Software version 2.17.651.5), but here's my issue. I have an EVO 3D with S-ON & a LOCKED bootloader that was updated over the air to ICS & when I go to unlock the bootloader via htcdev.com, nothing happens & HTC claimed that this issue would be fixed with the ICS update, but guess what? It wasn't!
Nonetheless, you would think that reinstalling the ICS operating system (Software version 2.89.651.2) on the phone via an RUU or a PG86IMG file would work. Neither one works for me! Every time I go to run the ICS RUU, it throws back a 170 USB connection error & this is crazy because the RUU that I have for the last Gingerbread OS (Software version 2.17.651.5) never throws back any type of errors! It has worked on every single EVO 3D that I have had to use the fix on! I have tried running the ICS RUU several times and have used several different USB cables & have had no success whatsoever.
So what I did from here is requested for someone from the XDA community to create a PG86IMG for me so that I could see about reinstalling the ICS OS on the phone through the bootloader (Shout outs to Karl! He came through on this right away. Karl you are the man!). Unfortunately, when I go to use the PG86IMG file, it does all of this loading & appears as if it's going to work but ultimately goes back to the HBOOT home screen & doesn't give me an option to install the f'n operating system! This sh*t blows & I am all out of ideas as to what to do from here. I am basically stuck.
On anther note, I tried to use the ICS RUU that I have on another EVO 3D with no success, but I was successfully able to reinstall the ICS operating system on this same EVO 3D via the PG86IMG file that Karl provided. What in the world is going on here?! If anyone can offer any helpful advice, I'd certainly appreciate it. Thanx in advance. (On a side note this other EVO 3D that I was able to reinstalled the ICS OS on via the PG86IMG file has an UNLOCKED bootloader & is S-OFF. I don't know if this makes any difference, but I thought I'd share this anyway.)
RioSoul said:
Nonetheless, you would think that reinstalling the ICS operating system (Software version 2.89.651.2) on the phone via an RUU or a PG86IMG file would work. Neither one works for me! Every time I go to run the ICS RUU, it throws back a 170 USB connection error & this is crazy because the RUU that I have for the last Gingerbread OS (Software version 2.17.651.5) never throws back any type of errors! It has worked on every single EVO 3D that I have had to use the fix on! I have tried running the ICS RUU several times and have used several different USB cables & have had no success whatsoever.
Click to expand...
Click to collapse
The 170 error means that the RUU.exe can't find your phone. Make sure the phone is in "fasboot USB" mode in the bootloader, then try running "fastboot devices" from the PC directory you used to root your phone. It should come back with a serial number that starts with "HT". If it doesn't, you may have a problem with the USB port on your phone, although it probably won't go into fastboot USB mode in the bootloader if that is the case. If you get the serial number, try running the RUU.exe again from there. If you get a 17x error with the RUU.exe, usually restarting it will get past that error as long as you have the proper connectivity to the phone.
ramjet73
achppr who
Confirmed, this worked for me. Thanks for your help! :good:
I used hasoon2000's tool to unlock the bootloader of my friend's AT&T One X+. I was able to successfully unlock the bootloader and flash a custom recovery. The recovery I chose was the one from this thread, for another carrier. I didn't carefully read the red text, I assumed it said don't flash if you don't have AT&T. So, I have apparently flashed the wrong recovery to the device. I get errors attempting to mount the storage when in this recovery. I have downloaded the correct AT&T version of the recovery and attempted to flash using fastboot, but I only get this error message via the command prompt: "command write failed (Unknown error)". Also, I get errors in recovery that tell me it cannot mount E:\ (which is the internal storage).
Is there anything I can do to get the correct copy of recovery on his device? Or is it just bricked?
Thanks for your help, dudes.
Code:
C:\One_X+_All-In-One_Kit_v1.1\data>fastboot flash recovery Recoveries/recovery.
mg
sending 'recovery' (7068 KB)... FAILED (command write failed (Unknown error))
finished. total time: 0.640s
C:\One_X+_All-In-One_Kit_v1.1\data>fastboot reboot
rebooting...
finished. total time: 0.170s
Also, I am still able to get into the bootloader and the non-working CWM recovery. The device sits at the HTC screen when attempting to boot.
edit: I was able to fix this by using the AT&T RUU linked below in fast boot. Then, I unlocked the boot loader (it must be locked for the RUU installer to work) using the toolkit again, then flashed TWRP and flashed supersu. All is well. Thanks for the assistance, men.
I'm waiting for my device to charge in the powered-down state, apparently it's not at 30% or more. Hopefully it's actually charging. My plan is to use an RUU from O2 to get into the OS. Once I've done that and I hopefully boot up normally, I'll use the TOOLKIT again to flash the proper recovery and then flash the stock AT&T ROM, since no AT&T RUU is available (or not one that I can find).
If anyone knows if flashing a different carrier's RUU will cause additional problems, please let me know.
ATT ruu is available. You wont be able to use a different carrier RUU unless you have super cid. Hasoon has a good mirror. http://d-h.st/y1Z I used this ruu to fix my bricked ATT hox+ couple days ago. just relock bootloader and you should be set!
C:\One_X+_All-In-One_Kit_v1.1\data>fastboot flash recovery Recoveries/recovery.
mg
heh what's missing? ;p little hint > i < from .img
Lloir said:
C:\One_X+_All-In-One_Kit_v1.1\data>fastboot flash recovery Recoveries/recovery.
mg
heh what's missing? ;p little hint > i < from .img
Click to expand...
Click to collapse
lol yeah typos make a difference. No spell checker there!
tallymatty said:
Also, I am still able to get into the bootloader and the non-working CWM recovery. The device sits at the HTC screen when attempting to boot.
Click to expand...
Click to collapse
why you on my crappy CWM still....there's mike's one or my TWRP
nugzo said:
ATT ruu is available. You wont be able to use a different carrier RUU unless you have super cid. Hasoon has a good mirror. http://d-h.st/y1Z I used this ruu to fix my bricked ATT hox+ couple days ago. just relock bootloader and you should be set!
Click to expand...
Click to collapse
Thanks, I've got this downloaded now. Why hasn't this link be published somewhere easily findable? I searched for this forever.
I don't think the phone is charging in the powered-down state though, I left it charging for a good 45 minutes and the RUU installer still tells me it's below 30%. Is there another screen in the bootloader/recovery that will allow the phone to charge? I'll let you know how it goes if I can get this thing to charge up.
Lloir said:
C:\One_X+_All-In-One_Kit_v1.1\data>fastboot flash recovery Recoveries/recovery.
mg
heh what's missing? ;p little hint > i < from .img
Click to expand...
Click to collapse
This was just a copy-paste from the toolkit command prompt window. I don't know what happened to that i. :silly:
Lloir said:
why you on my crappy CWM still....there's mike's one or my TWRP
Click to expand...
Click to collapse
Definitely made a mistake on this one, I'll admit it. And my friend (if I can still call him that) isn't too happy that he still hasn't gotten to use his new phone yet.
I'll definitely be re-unlocking the bootloader and flashing a new recovery that works, probably TWRP. TWRP seems to have some better features. Thanks for the recommendation.
This should really be listed under ATT One X+ RUU
I've been searching forever for the correct RUU for the ATT One X+ and then stumbled upon this. I couldn't find it on the htc site or anything.
Finally, I ran this RUU and everything seems fine again! I thought I had soft bricked my phone and needed to wait for the correct RUU to be posted.
Thank you for posting this!
Please i need a hand HTC One X+ almost dead!! (noob)
Hi all,
I'm recognized that i'm lost right now. I tried so many things to come back my HOX+ to live but really i haven't the knowledgement to do that.
I bought my HTC two days ago and try to root (i come from HTC Leo and it's so easy) and i forget copy a rom inside my phone and flashed the boot.img. Then i stuck in a loopboot.
This is the info that i have from my phone if somebody can help me (put my phone life in your hands):
HTC One X + (ATT)
cid: CWS__001
Software number: 1.15.502.9 710RD
TWRP 2.4.4.0 (i can in to phone bootloader but the pc don't recognized it as storage)
Thanks and i hope the miracle in this Holy week :crying:
Please i need a hand HTC One X+ almost dead!! (noob)
aslanjunior said:
Hi all,
I'm recognized that i'm lost right now. I tried so many things to come back my HOX+ to live but really i haven't the knowledgement to do that.
I bought my HTC two days ago and try to root (i come from HTC Leo and it's so easy) and i forget copy a rom inside my phone and flashed the boot.img. Then i stuck in a loopboot.
This is the info that i have from my phone if somebody can help me (put my phone life in your hands):
HTC One X + (ATT)
cid: CWS__001
Software number: 1.15.502.9 710RD
TWRP 2.4.4.0 (i can in to phone bootloader but the pc don't recognized it as storage)
Thanks and i hope the miracle in this Holy week :crying:
Click to expand...
Click to collapse
I solved this issue, please follow this link (http://forum.xda-developers.com/showthread.php?p=39637348#post39637348)
So I am trying to Un-Root my HTC DNA, and I was following these steps
http://forum.xda-developers.com/showthread.php?t=2017525
But when I'm running the RUU, i get an error 155: Unknown error.
Telling me to get the correct ROM Update Utility, but i can't find it anywhere but on that website.
Once the RUU Update has failed and I restart the phone,it goes straight into boot menu with ****TAMPERED*****. ******RELOCKED******, and *******Security Warning******* At the top and when I try to do a factory data reset on the phone, it goes into the fastboot menu, with the same notifications uptop.
Any idea what might be going on?
RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed
this is the name of the RUU u need. not sure about the errors. just google uroot and relock dna and it should be the top link. or just look in rootzwiki
it looks like you got the correct RUU, try a different usb port. How far does it go? does it even start. make sure your usb debugging and booted in fastboot.
cmay227 said:
RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed
this is the name of the RUU u need. not sure about the errors. just google uroot and relock dna and it should be the top link. or just look in rootzwiki
it looks like you got the correct RUU, try a different usb port. How far does it go? does it even start. make sure your usb debugging and booted in fastboot.
Click to expand...
Click to collapse
I have tired to do it in all three of my USB Ports.
All i can say is try starting the RUU.exe and have your phone booted normally. not in fastboot. it worked for me both ways. might be something to try. If it fails again try re-downloading the file, rinse and repeat.
cmay227 said:
RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed
this is the name of the RUU u need. not sure about the errors. just google uroot and relock dna and it should be the top link. or just look in rootzwiki
it looks like you got the correct RUU, try a different usb port. How far does it go? does it even start. make sure your usb debugging and booted in fastboot.
Click to expand...
Click to collapse
Pretty sure you can't relock unless you used htcdev.
As Adryn said if you used htcdev I'm pretty sure we can still "relock" but the exploit has permanatly changed the CID of all our phones. So fastboot oem lock still works and the ruu will revert the phone to its "stock" state as in factory shipped software and bloat but the bootloader will still reflect that it has been tampered with and the same token can be used to unlock again immediately afterward. So what I'm saying to all others is that the exploit is irreversible. There were a couple guys toying with it in the irc yesterday. But unless you absolutely have to do this theres really NO reason because you won't be able to cover the tracks of the hacking you've already done to your phone.
jonesin said:
As Adryn said if you used htcdev I'm pretty sure we can still "relock" but the exploit has permanatly changed the CID of all our phones. So fastboot oem lock still works and the ruu will revert the phone to its "stock" state as in factory shipped software and bloat but the bootloader will still reflect that it has been tampered with and the same token can be used to unlock again immediately afterward. So what I'm saying to all others is that the exploit is irreversible. There were a couple guys toying with it in the irc yesterday. But unless you absolutely have to do this theres really NO reason because you won't be able to cover the tracks of the hacking you've already done to your phone.
Click to expand...
Click to collapse
To me the main benefit of running the RUU was to get rid of the Tampered status in the boot loader screen. But your right it will say Relocked instead of locked. no way around that......so kinda pointless warranty wise.just removes root
Well I'm in the process of redownloading the RUU file.
I am still kind of curious, how come I can't reset to factory default through the boot loader or though the settings -> restore feature? Does it have to do with being rooted?
If you don't have a good reason to unroot, I would encourage you to wait. Those have have unrooted, and relocked, have had problems unlocking a second time.
I've locked and relocked many times and It was a pain in the ass to get unlocked status back. I would get the unlock prompt on the phone and choose yes but it ended up always still saying relocked. I finallly read to shut phone down completly before going into fasboot. I was just choosing restart. Have not had a issue unlocking since. Unlock code takes everytime.
Sent from my HTC6435LVW using xda app-developers app
OP, if you're attempting to get the 'locked' message on the bootloader back, you won't (as others have stated,) but if you're trying this to get your warranty back, the persons at Verizon won't look at this when you return the device. Neither will the people at the Verizon corporate office. All they will do is completely reflash the device including bootloader and that will be that.
Mazer
Sent from my rooted and debloated Droid DNA.
Mazer_R said:
OP, if you're attempting to get the 'locked' message on the bootloader back, you won't (as others have stated,) but if you're trying this to get your warranty back, the persons at Verizon won't look at this when you return the device. Neither will the people at the Verizon corporate office. All they will do is completely reflash the device including bootloader and that will be that.
Mazer
Sent from my rooted and debloated Droid DNA.
Click to expand...
Click to collapse
Thanks from the reply. I mainly wanted to un-root it to 1) Check for updates an 2) Restore to OEM to see if a problem I am/was having with my Aux jack could have been fixed that way.
I managed to get it to work...I think what the problem was, was that I had PDANET installed, so when the phone rebooted to flash the ruu, Pdanet started and caused the flash to fail. I disabled Pdanet and any other non-essential programs that were running in the background on my laptop, and the flashing worked.
I wasn't too worried about the root or the unlocked status because I'll be returning it under the 14 day guarantee.
Hey all,
So I'm sending my Rezound back to Verizon as a warranty replacement, and today I tried to revert it to stock. It was rooted, S-OFF, with Infected ROM installed (based off CM10.1.2). However, the re-lock process didn't work correctly. I received the below error in the command prompt when I tried to relock it with fastboot oem lock:
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = -131073 (0xFFFDFFFF)
FAILED (status read failed (Too many links))
The steps I took are as follows:
1) Re-installed RUU using this file: Rezound_Global_ICS_4.03.605.2_Full_RUU_PH98IMG (renamed to PH98IMG and done through bootloader)
2) Attempted fastboot oem lock (and got the above error)
This process worked on a different Rezound that I also received as a warranty replacement which itself was also defective, but in that case I locked the phone first and THEN flashed the RUU. In my haste today I accidentally flipped the order to what you see above.
Now, the phone will not go back to ***LOCKED*** up at the top. Instead, it says ***RELOCKED*** which is not what I want here. I am afraid to set the S-OFF flag back to ON while the phone is displaying "relocked". The RUU did work, as the phone has stock firmware on it once again and boots up fine. I attempted to relock it again and RUU it again with the same results, still got the above error and still showing ***RELOCKED***.
I did some research but couldn't find anything specific to the Rezound; the nearest thing I was able to find was some info about how CleanROM can cause this on a different device, and something about mainver, which I'm not familiar with. I did use CleanROM for nearly a year before going S-OFF and moving to CM10. If anyone has an idea on how to fix it I would be eternally grateful.
tigerxchaos said:
Hey all,
So I'm sending my Rezound back to Verizon as a warranty replacement, and today I tried to revert it to stock. It was rooted, S-OFF, with Infected ROM installed (based off CM10.1.2). However, the re-lock process didn't work correctly. I received the below error in the command prompt when I tried to relock it with fastboot oem lock:
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = -131073 (0xFFFDFFFF)
FAILED (status read failed (Too many links))
The steps I took are as follows:
1) Re-installed RUU using this file: Rezound_Global_ICS_4.03.605.2_Full_RUU_PH98IMG (renamed to PH98IMG and done through bootloader)
2) Attempted fastboot oem lock (and got the above error)
This process worked on a different Rezound that I also received as a warranty replacement which itself was also defective, but in that case I locked the phone first and THEN flashed the RUU. In my haste today I accidentally flipped the order to what you see above.
Now, the phone will not go back to ***LOCKED*** up at the top. Instead, it says ***RELOCKED*** which is not what I want here. I am afraid to set the S-OFF flag back to ON while the phone is displaying "relocked". The RUU did work, as the phone has stock firmware on it once again and boots up fine. I attempted to relock it again and RUU it again with the same results, still got the above error and still showing ***RELOCKED***.
I did some research but couldn't find anything specific to the Rezound; the nearest thing I was able to find was some info about how CleanROM can cause this on a different device, and something about mainver, which I'm not familiar with. I did use CleanROM for nearly a year before going S-OFF and moving to CM10. If anyone has an idea on how to fix it I would be eternally grateful.
Click to expand...
Click to collapse
You need to get ahold of either the ph98img.zip for 3.14.605.12 like HERE and put it on your sd card and run that at hboot after renaming it ph98img.zip or get a copy of the full RUU (RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe) for 3.14.605.12 at ONE OF THESE LINKS and run this on your pc with the phone connected by the USB cable. Make sure on the exe version that you have USB debugging enabled. The RUU you used is a leak and not an "official" full RUU. You need to run a full official RUU to accomplish what you want and the full RUU for 4.05.605.14 has not been released yet. If you use either of the ones I provided links for, the hboot will show "locked" but an earlier version. Then if you want it to show the latest version, leave your SIM card in the phone, let it bootup, when the setup starts, just press the home key and it will bypass setup. The get into settings and into the software update and run that. It will update to the next version. Let it reboot and again bypassing the setup. Then run software update one more time and you will have 4.05.605.14 which is the latest version and your hboot will now show locked. Now you can go ahead and re S-on the phone.
However, I have heard over and over that Verizon never checks the software on the phones and you could just send it back the way it is now. But I'm sure that you are paranoid about this like I am and want it fully stock again so there are no red flags...
mikeyk101 said:
You need to get ahold of either the ph98img.zip for 3.14.605.12 like HERE and put it on your sd card and run that at hboot after renaming it ph98img.zip or get a copy of the full RUU (RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe) for 3.14.605.12 at ONE OF THESE LINKS and run this on your pc with the phone connected by the USB cable. Make sure on the exe version that you have USB debugging enabled. The RUU you used is a leak and not an "official" full RUU. You need to run a full official RUU to accomplish what you want and the full RUU for 4.05.605.14 has not been released yet. If you use either of the ones I provided links for, the hboot will show "locked" but an earlier version. Then if you want it to show the latest version, leave your SIM card in the phone, let it bootup, when the setup starts, just press the home key and it will bypass setup. The get into settings and into the software update and run that. It will update to the next version. Let it reboot and again bypassing the setup. Then run software update one more time and you will have 4.05.605.14 which is the latest version and your hboot will now show locked. Now you can go ahead and re S-on the phone.
However, I have heard over and over that Verizon never checks the software on the phones and you could just send it back the way it is now. But I'm sure that you are paranoid about this like I am and want it fully stock again so there are no red flags...
Click to expand...
Click to collapse
Thanks very much for the suggestion. I'll give this a try shortly.
It's just weird that this RUU successfully took another phone back to fully stock. The only difference between the two is that the other phone never had CleanROM installed on it.
EDIT: Just realized one other thing, at one point I manually updated the radios on the first phone (the one that is now giving me trouble) but didn't do this on the one that went back to stock properly. I'm going to give the PC method a try since it mentions the radios in the file name.
Sent from my SCH-I535 using xda app-developers app
Went ahead and ran the full RUU from my PC as suggested above. Unfortunately it didn't accomplish the goal. The RUU completed successfully, but HBOOT still says ***RELOCKED***. I tried unlocking and then relocking again, and got the same error:
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = -131073 (0xFFFDFFFF)
FAILED (status read failed (Too many links))
finished. total time: 0.958s
Not sure where to go from here.
With S-off, the radios shouldnt matter. Seems to me when I s-offed this latest phone, it was on 4.05.605.14 and I had to unlock the bootloader to do the s-off. After I achieved s-off, I dont remember relocking, I just ran that ph98img from android police. The bootloader then displayed that it was locked. Maybe try to run either of those RUUs after unlocking the bootloader.
mikeyk101 said:
With S-off, the radios shouldnt matter. Seems to me when I s-offed this latest phone, it was on 4.05.605.14 and I had to unlock the bootloader to do the s-off. After I achieved s-off, I dont remember relocking, I just ran that ph98img from android police. The bootloader then displayed that it was locked. Maybe try to run either of those RUUs after unlocking the bootloader.
Click to expand...
Click to collapse
I think the key is this error I'm getting via the command line. I didn't get it with the other phone and on that one, after I relocked, it said **TAMPERED** across the top; after the RUU, it just said **LOCKED**. This one is saying **RELOCKED** instead of **TAMPERED** and it's the one that won't go back to locked after a RUU. If we can figure out what's causing this error, might be the key to solving the issue. However, that's where I'm falling short in my research.
tigerxchaos said:
I think the key is this error I'm getting via the command line. I didn't get it with the other phone and on that one, after I relocked, it said **TAMPERED** across the top; after the RUU, it just said **LOCKED**. This one is saying **RELOCKED** instead of **TAMPERED** and it's the one that won't go back to locked after a RUU. If we can figure out what's causing this error, might be the key to solving the issue. However, that's where I'm falling short in my research.
Click to expand...
Click to collapse
IIRC, when it says Tampered across the top of the bootloader, it just means that the bootloader is unlocked and that a other than factory recovery has been installed such as TWRP or AmonRa. Relocked means that the bootloader had originally been unlocked at some point and then locked again. If it were me, I would
1. Try to unlock the bootloader again,
2. Reinstall either AmonRa or TWRP if either is not there, then
3. Wipe everything such as cache, dalvik cache, wipe ALL data/factory reset, and possibly even wipe system.
(Normally you would not want to wipe system because pretty much everything is then gone but since you have the RUU.exe, you have the means to reinstall the original OS.)
4. After wiping everything above, reboot from recovery to bootloader and try running that RUU again.
You are right though and this is weird. Normally when you run a full factory RUU, it should reset EVERYTHING back to factory original condition.
BTW, I have just been trying to come up with a workable solution. I was kind of hoping that someone with more experience would pipe in. Unfortunately it looks like the Rezound and development is dying a slow but sure death and many have moved on...
Just trying to think of alternate solutions again, I know that it is possible to change just the hboots by using the proper ph98img.zip files. I remember using one awhile back when I was unlocked that changed the hboot from tampered to read locked. I cant find the thread but I think it came from Vinylfreak . I attached it in this post but it will read 2.27.0000 as the version. I have also included the factory 2.28.0000 in a separate ph98img file below. Maybe try one of these and it might take care of it. Put these on your sd card, change the name of the first one to ph98img.zip and get into the bootloader hboot and let it update. If that doesn't work, try the second one.
If needed, I could also probably make one for the 3.05.605.12 and upload that as well. I just need to check the hboot version it came with.
ETA, I think the first one came from THIS THREAD and it is just renamed by me so I could keep track of what it was...
mikeyk101 said:
Just trying to think of alternate solutions again, I know that it is possible to change just the hboots by using the proper ph98img.zip files. I remember using one awhile back when I was unlocked that changed the hboot from tampered to read locked. I cant find the thread but I think it came from Vinylfreak . I attached it in this post but it will read 2.27.0000 as the version. I have also included the factory 2.28.0000 in a separate ph98img file below. Maybe try one of these and it might take care of it. Put these on your sd card, change the name of the first one to ph98img.zip and get into the bootloader hboot and let it update. If that doesn't work, try the second one.
If needed, I could also probably make one for the 3.05.605.12 and upload that as well. I just need to check the hboot version it came with.
ETA, I think the first one came from THIS THREAD and it is just renamed by me so I could keep track of what it was...
Click to expand...
Click to collapse
Thanks again for all your suggestions, you've been REALLY helpful.
I'll try out the hboot method you listed above and see what I can come up with. My concern there is that I think vinylfreak's hboot was an engineering hboot, which will brick the phone if I try to go back to S-ON with it installed.
Rezound development is actually still alive and well, among several dedicated developers who are working on some great software for the phone. @Flyhalf205 has been releasing regular updates to his Rezound build of CyanogenMod 10.1 and as I understand it, is responsible for a ton of the recent progress made on bringing Jellybean to the Rezound. @IAmTheOneTheyCallNeo has a fantastic ROM based off of CM called Infection, and a variant of it based on PACMan called Tron. @iHateWebOS has a great kernel called HIRO, @Snuzzo has another one called Funky Kernel, and there are other devs that I'm less familiar with working on other projects. Check out their work, it breathed new life into my phone.
tigerxchaos said:
Thanks again for all your suggestions, you've been REALLY helpful.
I'll try out the hboot method you listed above and see what I can come up with. My concern there is that I think vinylfreak's hboot was an engineering hboot, which will brick the phone if I try to go back to S-ON with it installed.
Rezound development is actually still alive and well, among several dedicated developers who are working on some great software for the phone. @Flyhalf205 has been releasing regular updates to his Rezound build of CyanogenMod 10.1 and as I understand it, is responsible for a ton of the recent progress made on bringing Jellybean to the Rezound. @IAmTheOneTheyCallNeo has a fantastic ROM based off of CM called Infection, and a variant of it based on PACMan called Tron. @iHateWebOS has a great kernel called HIRO, @Snuzzo has another one called Funky Kernel, and there are other devs that I'm less familiar with working on other projects. Check out their work, it breathed new life into my phone.
Click to expand...
Click to collapse
I didn't quite elaborate on what I was thinking. But you are absolutely correct about doing S-on with an engineered hboot and that it would brick it. However, since it is going back as a warranty replacement, maybe bricking it might not be such a bad idea. LOL. I should have added that by using the fake locked hboot, it may trick the phone into thinking it really was locked. And then flash the second one and the banner just might stay showing locked. I have actually gone back and forth between the two but have always been locked so I am not sure how yours would work out. BTW, that second one is the original factory hboot extracted off the full OTApkg.zip for 4.05.605.14 and packaged in a ph98img file. I extracted it in the event that I might have to S-on again sometime in the future. I also extracted the original factory recovery and packaged that in a ph98img file as well in case I ever had to revert back to stock for the same reason. I just have to unroot (I am using supersu), reinstall the factory recovery, reinstall the factory hboot, do a factory wipe in recovery and finally do the write secure flag command and I am golden. I know that there are still many very cool roms out there. I used to be a big fan of CleanROM but that is no longer supported by the developer. Since then I have gotten kind of used to using a rooted stock rom. I know I may be missing some bells and whistles but I mostly rooted and S-offed just because I could and have a few more choices available to me. I hope you are able to find a solution.
I had this happen a wile ago what worked for me was that I ran the ruu to back to stock, then go through the unlock process, once unlocked s-off. Once s-off run ruu, then follow directions in this link http://forum.xda-developers.com/showthread.php?t=1612937
Sent from my Infected Rezound using xda app-developers app