[Q] Turn signature check off via ADB?? (FULL STORY IN POST) - AT&T HTC One (M7)

I had already had my phone's bootloader unlocked and rooted and had a GPe ROM installed and worked perfectly. THEN I saw that you could literally make it a Google Play edition phone complete with OTA and worked on trying to achieve that. Getting my phone S-Off wasn't working because I believe of my HBOOT version (1.55) so I was told to download this stock ROM that would downgrade me to reach a version that I could then run revone to achieve S-OFF.
POST: http://forum.xda-developers.com/showpost.php?p=45487258&postcount=55
I ran a backup through TWRP first and then flahsed this ROM, which has kept my HTC One at the HTC One splash screen. I connected it to my computer/ADB and got it into the bootloader to go into custome recovery BUT the recovery takes me to a black screen with a phone and red triangle, so it's like my recovery isn't there anymore. Fine.
I download the latest TWRP for my phone(triple checked) and ran the fastboot flash recovery command through ADB but it says
"(bootloader) signature checking...FAILED (remote: signature verify fail)"
is there some sort of way to disable the signature check using ADB or am I actually going about this the wrong way?
I'll admit, I don't do this stuff oftem, so ask as many questions as needed as I probably left out details you may need

I may be wrong but you may have to re-lock the bootloader and run the ruu back to stock.
nandroid backup restore won't change the hboot so I don't think you'll have any luck there.
I'm running ARHD 40 just till we can find a way to run s-off on our AT&T devices.

noobsquared said:
I may be wrong but you may have to re-lock the bootloader and run the ruu back to stock.
nandroid backup restore won't change the hboot so I don't think you'll have any luck there.
I'm running ARHD 40 just till we can find a way to run s-off on our AT&T devices.
Click to expand...
Click to collapse
Not to sound n00b-ish, but what would be the best way of doing this?
EDIT: Actually it is relocked already! Duh! On the bootloader screen it says "TAMPERED" and then "RELOCKED" below that

That's alright, we were all noobs at some point in time.
Sounds like you re-locked the bootloader without stock recovery.
Here is the link:
http://forum.xda-developers.com/showthread.php?t=2158151
Download the cingular:
RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2.exe 1134.6MB 2013-10-07 16:47:53
Run the RUU from a windows based computer that has HTC drivers and it should restore it back to stock.

noobsquared said:
That's alright, we were all noobs at some point in time.
Sounds like you re-locked the bootloader without stock recovery.
Here is the link:
http://forum.xda-developers.com/showthread.php?t=2158151
Download the cingular:
RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2.exe 1134.6MB 2013-10-07 16:47:53
Run the RUU from a windows based computer that has HTC drivers and it should restore it back to stock.
Click to expand...
Click to collapse
I actually had that downloaded but I was just concerned if that was the right move since it wipes the phone.

noobsquared said:
That's alright, we were all noobs at some point in time.
Sounds like you re-locked the bootloader without stock recovery.
Here is the link:
http://forum.xda-developers.com/showthread.php?t=2158151
Download the cingular:
RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2.exe 1134.6MB 2013-10-07 16:47:53
Run the RUU from a windows based computer that has HTC drivers and it should restore it back to stock.
Click to expand...
Click to collapse
I hate to say this actually, but I can't find that .exe in the link. I don't know exactly what I'm looking for in it.

h_smith said:
I hate to say this actually, but I can't find that .exe in the link. I don't know exactly what I'm looking for in it.
Click to expand...
Click to collapse
Here you go:
http://www.androidruu.com/getdownlo...13_10.38j.1157.04_release_334235_signed_2.exe
You can always unlock the bootloader again, install twrp and try to boot and see if that works.
Install the nandroid backup matching your system and you can then get to your data.

noobsquared said:
You can always unlock the bootloader again, install twrp and try to boot and see if that works.
Install the nandroid backup matching your system and you can then get to your data.
Click to expand...
Click to collapse
But how would I do that if I can't even boot up the phone past the splash screen? I did all of the unlocking and TRWP installing via the phone
Downloading and installing the file right now. It's going slow as hell but I'll run when I get the chance
THANK YOU FOR STICKING WITH ME!

h_smith said:
But how would I do that if I can't even boot up the phone past the splash screen? I did all of the unlocking and TRWP installing via the phone
Downloading and installing the file right now. It's going slow as hell but I'll run when I get the chance
THANK YOU FOR STICKING WITH ME!
Click to expand...
Click to collapse
Sure thing man. It's stuck at that screen because when your phone is unlocked, it allows custom recovery but when it's locked, it won't boot unless it finds the stock recovery. I am not 100% sure but I've had that issue as well. I had to run the RUU to get back to stock since you can't lock the bootloader with custom recovery and expect it to boot. It may vary from device to device but I've always had to RUU back to stock or fastboot flash stock recovery to get past that screen before you lock the bootloader. You can try again, there is stock recovery posted by someone in forums. Download that, try to go in fastboot mode and try fastboot flash recovery recovery_name.img. I think once you've locked the bootloader it may not work but worth a shot.

noobsquared said:
Sure thing man. It's stuck at that screen because when your phone is unlocked, it allows custom recovery but when it's locked, it won't boot unless it finds the stock recovery. I am not 100% sure but I've had that issue as well. I had to run the RUU to get back to stock since you can't lock the bootloader with custom recovery and expect it to boot. It may vary from device to device but I've always had to RUU back to stock or fastboot flash stock recovery to get past that screen before you lock the bootloader. You can try again, there is stock recovery posted by someone in forums. Download that, try to go in fastboot mode and try fastboot flash recovery recovery_name.img. I think once you've locked the bootloader it may not work but worth a shot.
Click to expand...
Click to collapse
Thank you. I'm downloading the .exe and will post the results. But it looks like that might take a few hours :/

hey is there another link? that one is so slow and keeps timing out :/

You can either use download manager or chrome browser is pretty good at managing that.
Try this: http://d-h.st/VWf
---------- Post added at 06:31 PM ---------- Previous post was at 06:30 PM ----------
I just did a google search for the term RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_R and gave you the second result I got. Just search for the name of the file and you will find plenty of links.
Hope that helps.

This sounds like the exact same problem I had. The RUU and directions solved that one for me too...
Link to RUU: http://www.htc.com/us/support/news.aspx?p_id=628&p_name=htc-one-att
Other thread: http://forum.xda-developers.com/showthread.php?t=2492266

THANK YOU NOOB!!
I managed to get it fixed. Turns out HTC hosted that exact file so I downloaded it and it fixed my phone. Good times..

Related

[Q] Which Stock RUU/ROM

Hi folks,
I have a HTC Evo 3D from the UK bought sim free, rooted it with s-on and tried to install a rom with 4ext, got stuck in bootloop, tried clearing cache but it never worked, tried a few different roms (not the best idea) and failed loads, the back up I used successfully before stopped working and in a mad attempt to get anything working I managed to stop 4ext as the recovery and its now CWM Recovery v4.0.1.4. It doesnt boot loop it just stays on the HTC screen without doing anything else.
Is there anything I can do?
I have tried the shipped RRUs but run into an error each time, probably since I am just guessing at which I am supposed to be using, is there a way to figure it out? Or a rom/cwm way or a way of getting another backup/restore file?
Any help is very much appreciated, I shouldnt have been allowed the USB cable! lol
Thanks
Paul
ScottishPaul88 said:
Hi folks,
I have a HTC Evo 3D from the UK bought sim free, rooted it with s-on and tried to install a rom with 4ext, got stuck in bootloop, tried clearing cache but it never worked, tried a few different roms (not the best idea) and failed loads, the back up I used successfully before stopped working and in a mad attempt to get anything working I managed to stop 4ext as the recovery and its now CWM Recovery v4.0.1.4. It doesnt boot loop it just stays on the HTC screen without doing anything else.
Is there anything I can do?
I have tried the shipped RRUs but run into an error each time, probably since I am just guessing at which I am supposed to be using, is there a way to figure it out? Or a rom/cwm way or a way of getting another backup/restore file?
Any help is very much appreciated, I shouldnt have been allowed the USB cable! lol
4ext recovery is the choice for s-on users so using cwm is a bad idea. You maybe experiencing bootloops on 4ext because you may have not had smartflash enabled. S-on users cannot flash kernels through normal means through recovery like s-off users can. With smartflash this is possible. So my suggestion is to reflash 4ext through fastboot and enable it if you havn't done so and do a full wipe of your phone and reflash your rom and see if that work. As for the ruu's. You have to have your bootloader relocked to flash them. You can flash them through bootloader if they were signed by htc but if not, you will have to run the ruu exe on your pc which still ofcourse needs the bootloader to be relocked.
Click to expand...
Click to collapse
Thanks for the reply,
I'm trying to get 4ext running, I've tried fastboot flash recovery recovery.img and then boot recovery.img but all I get is the HTC screen with no recovery program now :S
Ta
Paul
Did you type the command with the exact name of your recovery file in your folder? Also do you have HTC sync installed? If so uninstall it. It will interfere with fastboot.
Jsparta26 said:
Did you type the command with the exact name of your recovery file in your folder? Also do you have HTC sync installed? If so uninstall it. It will interfere with fastboot.
Click to expand...
Click to collapse
Dont have HTC sync. I used the exact name, even using the TAB button to complete the filename
Thanks
Are you sure your bootloader is completely unlocked? Sometimes when you apply the unlock bin code the unlock screen doesn't show up with Ics. What kind of output do you get when you type the fastboot flash recovery command? There might be a clue. Well in any event I'm going to trouble shoot your problem. If you could copy and paste the input and output of your command that will help alot.
---------- Post added at 11:29 PM ---------- Previous post was at 11:15 PM ----------
Edit: let's try to get your phone back on stock and unlocking your bootloader instead. I read your post about how your having trouble flashing ruu. The first question is, is your phone branded or unbranded? Depending on either you will have to find an ruu exe file based on the region and carrier if branded. Just google it up. Next your phone will have to be in relocked state if your bootloader says unlocked. Type fastboot oem lock to relock it. Now you can run the file. Remember you must have the right on or it won't take. Remember after you unlock it again it will erase all your user data. Let me know if you succeed or not and then we can proceed from there. Oh yeah here's a link you might want to read up on about the whole ruu thing http://forum.xda-developers.com/showthread.php?t=1655832
Pretty sure its fully unlocked, I was able to run superSU, install 4ext and busybox etc.
I have got 4ext working again, the problem appears that the two recovery.img files I had tried were not the correct version for my phone, I've got the right one now and can boot into 4ext through the recovery option.
Okay, now try to flash a sense Rom like cool sense and let me know if it boots for you
Jsparta26 said:
Okay, now try to flash a sense Rom like cool sense and let me know if it boots for you
Click to expand...
Click to collapse
Yup its working I used KingCobra3D-ICS, such a great feeling to see it actually boot up for the first time in days! Thanks for all your help, not sure I will even attempt another rom, I think stick with this will be safe lol
Thanks
Paul

[Q] Unab;e to install ICS RUU before installing Nils' Business

Hey everyone,
So I have successfully HTC Unlocked my Rezound bootloader, installed Amon Ra, and then installed and booted the CM9 unofficial. Problem was that CM9 wasn't quite as cooperative as I'd hoped - it is unofficial, after all, and so I decided to abandon that in favor of Nils' Business ROM. Here's where I ran into issues.
I have tried everything in every order I can find online and think of, including Nils' writeup. So, for the life of me, I cannot get the leaked ICS RUU to boot (4.03.605.2 as listed in his instructions on XDA). Install runs fine every time I do it from the relocked (I checked) stock HBOOT, all steps included. Every time it reboots (and I've tried forcing it back into hboot to do the install a second time) it just goes to the white HTC screen and starts boot looping. Tried it a million ways, no go. Also worth noting - the stock recovery doesn't install properly, either. Some'fin is hinky, here.
So I've tried just "assuming" it went fine anyhow and then proceeding with the install for Nils' ROM and same deal, no go, although with one difference. With Nils' ROM, it does display the boot splash screen "Nils Business ROM" or what have you about 1 out of every 4 "boots" in the loop cycle, and then reboots again.
I think I am going to perform S-OFF tomorrow if I have the time, and then try it again using the S-OFF instructions, but I would sincerely appreciate any help from you all. Honestly, I'm at near wit's end with this device, and I don't want to be, I enjoy this chase too much, but I *really* want the reward at the end of it, lol.
Any help is deeply appreciated.
- Katie
Re: [Q]
I'm guessing because of the corrupted recovery, you have a bad download of the RUU. Try re downloading and check the md5 hash for a match. The ruu should reboot itself after the first pass and end up in bootloader again for the second pass.... If not then after the first pass just hold down power + vol down to get back to bootloader.
Hope this helps
Sent from my ADR6425LVW using xda app-developers app
Make sure that you have a booting ROM before you s-off. You will cause yourself all kinds of heartache if you don't.
Using an sd card reader on a pc, check md5 of your RUU zip file. If it checks out good, put the sd back in your rez and do an hboot power on and accept the update again. Report back with your findings. Also you will need to re-unlock your hboot after and install your recovery again.
Snuzzo said:
Using an sd card reader on a pc, check md5 of your RUU zip file. If it checks out good, put the sd back in your rez and do an hboot power on and accept the update again. Report back with your findings. Also you will need to re-unlock your hboot after and install your recovery again.
Click to expand...
Click to collapse
Hey, thanks. Yeah, the RUU does check out just fine against an MD5SUM.
nm.... just read your original post again and you say you did relock the phone. I was hoping it was something simple like that that was overlooked.
Carry on...
feralicious said:
Nothing to see here, folks, move along.
Click to expand...
Click to collapse
Right now, I cannot S-OFF because it requires a working stock image, and I'll be lucky to get anything more than CM9 unofficial working here.
You're too fast, now my bad post lives on...
So, when theh RUU failed, you unlocked again, flashed a custom recovery and tried to flash Nils' ROM?
Do you have a nandroid you can try to restore? Even if its the cm9 ROM at least to see if you can get it back to a working phone?
feralicious said:
You're too fast, now my bad post lives on...
So, when theh RUU failed, you unlocked again, flashed a custom recovery and tried to flash Nils' ROM?
Do you have a nandroid you can try to restore? Even if its the cm9 ROM at least to see if you can get it back to a working phone?
Click to expand...
Click to collapse
Well that's the trick. CM9 didn't work well enough to even be worth backing up. I'm trying to reinstall it again now just to see if I get there - and it looks like I will. Once I'm back up with that, I'm not sure where to go from there. The phone barely worked under CM9. Really hoping to get Nils' ROM on there, since it gives all the nice features of a stock device without the bloatware. Even if I never get S-OFF, I'll be perfectly happy with just Nils' software.
How about this... did you wipe everything before running the RUU? There's CleanWipe in the Development forum you can flash it from recovery and it will wipe everything 5 times!
This shouldn't make any difference, but there's also a different RUU, the OTA that's not global. You might try that one instead. I'm convinced that sometimes things are just voodoo even when they should be completely logical. That's definitely the case at work on the Avid systems I use.
Here's the link to it:
http://androidfiles.org/ruu/?dir=Vigor
feralicious said:
How about this... did you wipe everything before running the RUU? There's CleanWipe in the Development forum you can flash it from recovery and it will wipe everything 5 times!
This shouldn't make any difference, but there's also a different RUU, the OTA that's not global. You might try that one instead. I'm convinced that sometimes things are just voodoo even when they should be completely logical. That's definitely the case at work on the Avid systems I use.
Here's the link to it:
http://androidfiles.org/ruu/?dir=Vigor
Click to expand...
Click to collapse
I did try wiping everything first. No luck. I will try the CleanWipe tomorrow, because right now, whatever my issues are, I'm being prevented from solving them since I can't S-OFF and I can't even seem to get a working ROM to make the phone worth having! Ugh.
And you can try installing it under fastboot oem ruu instead of the ph.zip file
Sent from my HTC Rezound...
Flyhalf205 said:
And you can try installing it under fastboot oem ruu instead of the ph.zip file
Sent from my HTC Rezound...
Click to expand...
Click to collapse
Oh yeah! Try that. Someone else was having trouble and did it that way and it worked. Here's instructions, just make sure you use PH98IMG and not whatever is used in the instructions since it was written up for a different phone.
http://androidforums.com/incredible-all-things-root/487280-easier-way-flash-pb31img-files.html
Also, once you get your phone back to stock make a nandroid as soon as you flash the recovery again so you'll have that to go back to if you have any more issues.
Flyhalf205 said:
And you can try installing it under fastboot oem ruu instead of the ph.zip file
Sent from my HTC Rezound...
Click to expand...
Click to collapse
Thank you, your magnanimity! Seriously, lol, you're gracing my thread just by being here. :victory:
feralicious said:
Oh yeah! Try that. Someone else was having trouble and did it that way and it worked. Here's instructions, just make sure you use PH98IMG and not whatever is used in the instructions since it was written up for a different phone.
http://androidforums.com/incredible-all-things-root/487280-easier-way-flash-pb31img-files.html
Also, once you get your phone back to stock make a nandroid as soon as you flash the recovery again so you'll have that to go back to if you have any more issues.
Click to expand...
Click to collapse
Thanks for the clicky, Feralicious. Same results, unfortunately. I'm going to try doing the RUU flash of Nils' ROM instead. Do you guys know where I can get the ICS firmware by itself? I cannot be sure that it's actually flashed right, unfortunately.
Your HBOOT is 2.27 and it should say relocked????
It should since you flashed the 4.03.605.2 RUU. The only RUU you will be able to flash since your S-ON is the one found here http://www.androidfilehost.com/?fid=9390034591667978440
The other RUU will fail because you can't downgrade. So the link above(The Global RUU) will that fail or completely install 100%??
If it does install 100% and boot loops still. Take out the sdcard. Boot into the HBOOT and perform a factory reset inside of HBOOT/Fastboot(NOT IN RECOVERY)
Report your status
EDIT
The link listed above for the RUU. Other way of installing it which is a great way to look at the status of everything.
Boot into Fastboot
fastboot oem rebootRUU
fastboot oem lock
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
EDIT2:
If you can't get it installed or it did. Just go ahead and unlock again. Flash custom recovery. Install a rom. Flash the boot.img in fastboot. Factory reset. and then see if it boots. If still not working. hit me up on google chat [email protected]
Flyhalf205 said:
Your HBOOT is 2.27 and it should say relocked????
It should since you flashed the 4.03.605.2 RUU. The only RUU you will be able to flash since your S-ON is the one found here http://www.androidfilehost.com/?fid=9390034591667978440
The other RUU will fail because you can't downgrade. So the link above(The Global RUU) will that fail or completely install 100%??
If it does install 100% and boot loops still. Take out the sdcard. Boot into the HBOOT and perform a factory reset inside of HBOOT/Fastboot(NOT IN RECOVERY)
Report your status
EDIT
The link listed above for the RUU. Other way of installing it which is a great way to look at the status of everything.
Boot into Fastboot
fastboot oem rebootRUU
fastboot oem lock
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
EDIT2:
If you can't get it installed or it did. Just go ahead and unlock again. Flash custom recovery. Install a rom. Flash the boot.img in fastboot. Factory reset. and then see if it boots. If still not working. hit me up on google chat [email protected]
Click to expand...
Click to collapse
I'll do that stuff and let you know. Thank you!
Yes, I am on 2.27 HBOOT.
Point of interest, though possibly unsurprising. When I send the lock command, it locks and reboots, but says "Failed" in my command window screen. Sure this is probably normal since the phone might just reboot before responding to the computer, but possibly an issue.
I believe that is the image I tried before, but I'll do it again both ways to be certain and report back soon! :good:
ncc74656m said:
Yes, I am on 2.27 HBOOT.
Point of interest, though possibly unsurprising. When I send the lock command, it locks and reboots, but says "Failed" in my command window screen. Sure this is probably normal since the phone might just reboot before responding to the computer, but possibly an issue.
I believe that is the image I tried before, but I'll do it again both ways to be certain and report back soon! :good:
Click to expand...
Click to collapse
My DNA said something about failing when I locked it. But it locked just fine.
Since it is failing.
fastboot oem rebootRUU
fastboot oem lock ----if unlocked
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
Should work Maybe
Flyhalf205 said:
Your HBOOT is 2.27 and it should say relocked????
It should since you flashed the 4.03.605.2 RUU. The only RUU you will be able to flash since your S-ON is the one found here http://www.androidfilehost.com/?fid=9390034591667978440
The other RUU will fail because you can't downgrade. So the link above(The Global RUU) will that fail or completely install 100%??
If it does install 100% and boot loops still. Take out the sdcard. Boot into the HBOOT and perform a factory reset inside of HBOOT/Fastboot(NOT IN RECOVERY)
Report your status
Click to expand...
Click to collapse
Ok, so, this part including a factory reset got me to "HTC Quietly Brilliant" screen, but then it bootloops again. Tried factory resetting again to no avail. Trying the second part.
Flyhalf205 said:
EDIT
The link listed above for the RUU. Other way of installing it which is a great way to look at the status of everything.
Boot into Fastboot
fastboot oem rebootRUU
fastboot oem lock
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
Click to expand...
Click to collapse
Same thing as before unfortunately. :/ Performed a factory reset afterwards to be safe - no go. Everything shows OK though in both this and the above install. *shrug*
Flyhalf205 said:
EDIT2:
If you can't get it installed or it did. Just go ahead and unlock again. Flash custom recovery. Install a rom. Flash the boot.img in fastboot. Factory reset. and then see if it boots. If still not working. hit me up on google chat [email protected]
Click to expand...
Click to collapse
Proceeding with another attempt at installing CM9, I guess. Maybe the first one got hosed. If I get it booting in any form, I'll Nandroid it before trying anything else.
ncc74656m said:
Proceeding with another attempt at installing CM9, I guess. Maybe the first one got hosed. If I get it booting in any form, I'll Nandroid it before trying anything else.
Click to expand...
Click to collapse
I really wouldn't see why you would need a Sense rom to get s-off. I would imagine it would just need su and busybox installed. But nandroid then try a sense rom again. Make sure you flash the boot.img through fastboot

[Q] Flashed Stock Kernel, Now stuck in loop.

Hello,
My amaze 4g is currently running GB with the bullet proof custom rom i found here a couple years ago.
The boot loader is unlocked, and it is S-ON.
I wanted to try and update my phone to an ICS rom such as NRGZ28's energy Rom found here: http://forum.xda-developers.com/showthread.php?t=1362759.
First attempt, I factory reset the phone, cleared cache and cleared dalvik cache and flashed the rom. I chose the option to install it using the stock HTC kernel. The installation went smooth without errors until the final reboot to finalize the installation. The phone gets stuck in the white screen with the green htc logo on it. I recover using Clock Work Mod and everything is back to the old GB setting.
I assume it is because i have an outdated kernel so I go to NRGZ28's thread and download the stock kernel he has posted there. I flashed the kernel using Flash Image GUI apk. This is where the problem happens. After flashing the kernel, the phone is stuck on infinite loop at the above mentioned htc screen.
I flash the energy rom with the newly flashed stock kernel and the phone finally gets past the htc logo screen, but freezes shortly after during the blue animated splash screen and proceeds to repeat this. I can get into boot loader just fine, but am unable to get my phone working again even after a Clock work mod recovery.
please help!!
There is a special process you have to follow when going from GB to ICS, you can't just flash the latest kernel and expect it to work with ICS.
I would do a full wipe/factory reset, then follow the instructions here to upgrade to ICS stock, then you can install whatever ICS ROM you want:
http://forum.xda-developers.com/showpost.php?p=26865752&postcount=27
---------- Post added at 11:33 AM ---------- Previous post was at 11:27 AM ----------
Here is another, possibly more helpful link. It gives step by step instructions, make sure to follow the ones for S=On users (assuming you are S=On).
http://forum.xda-developers.com/showpost.php?p=25215207&postcount=2
I see. Thank you. I will try that right now. I will post an update soon.
o_jake said:
There is a special process you have to follow when going from GB to ICS, you can't just flash the latest kernel and expect it to work with ICS.
I would do a full wipe/factory reset, then follow the instructions here to upgrade to ICS stock, then you can install whatever ICS ROM you want:
http://forum.xda-developers.com/showpost.php?p=26865752&postcount=27
---------- Post added at 11:33 AM ---------- Previous post was at 11:27 AM ----------
Here is another, possibly more helpful link. It gives step by step instructions, make sure to follow the ones for S=On users (assuming you are S=On).
http://forum.xda-developers.com/showpost.php?p=25215207&postcount=2
Click to expand...
Click to collapse
Alright now I'm having a completely unrelated trouble trying to re-lock my bootloader. Yes, I am S-on. I've tried to factory reset but the phone still ends up looping on the htc logo screen. I type in "fastboot oem lock" on sdk but it just hangs at "waiting for device".
DougieJK said:
Alright now I'm having a completely unrelated trouble trying to re-lock my bootloader. Yes, I am S-on. I've tried to factory reset but the phone still ends up looping on the htc logo screen. I type in "fastboot oem lock" on sdk but it just hangs at "waiting for device".
Click to expand...
Click to collapse
Are you able to get into the bootloader, fastboot, or recovery? I'm unsure of which HTC screen you are talking about, if it is the one before trying to boot into Android then I would just ignore it for now. If you're having trouble relocking the bootloader, you might try this toolkit, which includes a tool to relock the bootloader: http://forum.xda-developers.com/showthread.php?t=1493905
All this stuff can probably be found in the HTC Amaze Bible, which you should probably familiarize yourself with before messing around and potentially bricking your phone. http://forum.xda-developers.com/showthread.php?t=1679486
o_jake said:
Are you able to get into the bootloader, fastboot, or recovery? I'm unsure of which HTC screen you are talking about, if it is the one before trying to boot into Android then I would just ignore it for now. If you're having trouble relocking the bootloader, you might try this toolkit, which includes a tool to relock the bootloader: http://forum.xda-developers.com/showthread.php?t=1493905
All this stuff can probably be found in the HTC Amaze Bible, which you should probably familiarize yourself with before messing around and potentially bricking your phone. http://forum.xda-developers.com/showthread.php?t=1679486
Click to expand...
Click to collapse
Yes, it is the screen right before it boots onto your phone's lock screen or main screen. Yes, I can get into the bootloader, fastboot, and the recovery without any problems.
DougieJK said:
Yes, it is the screen right before it boots onto your phone's lock screen or main screen. Yes, I can get into the bootloader, fastboot, and the recovery without any problems.
Click to expand...
Click to collapse
If you can get into the bootloader, fastboot, and recovery, then you should be able to continue the steps and get it working again. Try the Toolkit method of relocking bootloader and continue upgrade to ICS.
o_jake said:
If you can get into the bootloader, fastboot, and recovery, then you should be able to continue the steps and get it working again. Try the Toolkit method of relocking bootloader and continue upgrade to ICS.
Click to expand...
Click to collapse
The all-in-one toolkit is not recognizing my device. Not sure if it's a problem with windows or the toolkit.
Also, it seems the toolkit only works if you are able to actually get to your phone's home screen, which I am unable to do.
So frustrating.....
DougieJK said:
The all-in-one toolkit is not recognizing my device. Not sure if it's a problem with windows or the toolkit.
Also, it seems the toolkit only works if you are able to actually get to your phone's home screen, which I am unable to do.
So frustrating.....
Click to expand...
Click to collapse
Here are some more instructions: http://forum.xda-developers.com/showthread.php?t=1575550&highlight=relock+bootloader
It seems as though the problem is with ADB communicating with your phone. Type in "ADB devices" to see if it is detecting your phone.
Also make sure the file "fastboot.exe" is in the same folder as your ADB file that your command prompt is using.
---------- Post added at 03:12 PM ---------- Previous post was at 03:03 PM ----------
Also are you in bootloader or fastboot when you are trying to do this? I believe you should be in fastboot.
To enter fastboot: Boot into bootloader (hold power and volume down button), scroll down to fastboot, hit the power button.
Now try executing the fastboot command using adb. (remember to make sure fastboot.exe is in same folder as adb)
Alright, so I got it relocked by hooking it up to an old tower. It seems it was an issue with windows not recognizing my phone for some reason.
NOW, there's a new problem. On the bootloader menu, on the top it says "RELOCKED". I choose the recovery option, and it immediately takes me back to the bootloader menu displaying a "Security Warning" message under "RELOCKED".
I am going to cry.:crying:
DougieJK said:
Alright, so I got it relocked by hooking it up to an old tower. It seems it was an issue with windows not recognizing my phone for some reason.
NOW, there's a new problem. On the bootloader menu, on the top it says "RELOCKED". I choose the recovery option, and it immediately takes me back to the bootloader menu displaying a "Security Warning" message under "RELOCKED".
I am going to cry.:crying:
Click to expand...
Click to collapse
This is good... I think. You can now move on to the next step in these instructions: http://forum.xda-developers.com/showthread.php?t=1575550&highlight=relock+bootloader
You have to rename the RUU to what is says in that link, place it on an external SD card, then reboot into bootloader. Then it should automatically install the update (there might be a prompt, just hit yes).
o_jake said:
This is good... I think. You can now move on to the next step in these instructions: http://forum.xda-developers.com/showthread.php?t=1575550&highlight=relock+bootloader
You have to rename the RUU to what is says in that link, place it on an external SD card, then reboot into bootloader. Then it should automatically install the update (there might be a prompt, just hit yes).
Click to expand...
Click to collapse
Yes!!! I finally got it to work! Oh my god thank you so much. Thanks for being so patient with me. I dont know what more i can do do express my gratitude. It just felt amazing to see everything working and falling into place after hours and hours of hopelessness.
So from here on, I assume I just get back onto the boot loader menu, Unlock the boot loader again, then flash the rom I want.
Thank you again.
DougieJK said:
Yes!!! I finally got it to work! Oh my god thank you so much. Thanks for being so patient with me. I dont know what more i can do do express my gratitude. It just felt amazing to see everything working and falling into place after hours and hours of hopelessness.
So from here on, I assume I just get back onto the boot loader menu, Unlock the boot loader again, then flash the rom I want.
Thank you again.
Click to expand...
Click to collapse
You can flash any *ICS* ROM you want. There's another process if you want to go back to GB (though I'm not sure why you would want to).
You should be able to use the Toolkit to unlock the bootloader again, and I would recommend flashing the 4ext recovery while you're at it. From there you should be good!
o_jake said:
You can flash any *ICS* ROM you want. There's another process if you want to go back to GB (though I'm not sure why you would want to).
You should be able to use the Toolkit to unlock the bootloader again, and I would recommend flashing the 4ext recovery while you're at it. From there you should be good!
Click to expand...
Click to collapse
is the 4ext recovery preferred over Clockwork?
DougieJK said:
Alright, so I got it relocked by hooking it up to an old tower. It seems it was an issue with windows not recognizing my phone for some reason.
NOW, there's a new problem. On the bootloader menu, on the top it says "RELOCKED". I choose the recovery option, and it immediately takes me back to the bootloader menu displaying a "Security Warning" message under "RELOCKED".
I am going to cry.:crying:
Click to expand...
Click to collapse
Thats fine now since you are locked you can download the ruu file pertaining to your phone/carrier and put it in the root of your external sd card and boot into the bootloader and it will automatically detect the ruu and start updating. however you must rename the ruu appropriately (depending on which carrier your phone is) for T-Mobile you rename the ruu file ph85img and it detects it automatically. Good luck
Sent from my HTC_Amaze_4G using xda app-developers app
DougieJK said:
is the 4ext recovery preferred over Clockwork?
Click to expand...
Click to collapse
Yeah. You might like it better too.
hatlesssandman said:
Thats fine now since you are locked you can download the ruu file pertaining to your phone/carrier and put it in the root of your external sd card and boot into the bootloader and it will automatically detect the ruu and start updating. however you must rename the ruu appropriately (depending on which carrier your phone is) for T-Mobile you rename the ruu file ph85img and it detects it automatically. Good luck
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Yep I was just overreacting. After I renamed the ruu file, everything fell into place and my phone is now functioning with ICS.
So apparently, my phone isn't rooted anymore? is this normal?
Flashed 4ext using the all-in-one tool kit. Nothing happened. Can't run any apps that require root. I'm confused.
Yeah, that's totally normal after flashing an RUU and relocking the bootloader. Just re-root, here's a really easy tool for it: http://theunlockr.com/2012/05/01/how-to-root-htc-amaze-4g/
o_jake said:
Yeah, that's totally normal after flashing an RUU and relocking the bootloader. Just re-root, here's a really easy tool for it: http://theunlockr.com/2012/05/01/how-to-root-htc-amaze-4g/
Click to expand...
Click to collapse
That tool doesn't work for some reason, even though its the tool I used when I first rooted my phone. I just went and did the fastboot flash unlock_code.bin to unlock my phone again.
But for some reason, I can't get 4ext to flash... I went through the steps in the link you provided but my phone doesn't show the app nor am i able to access it through the recovery option from the boot loader menu.

Urgent!! Please help to restore phone

Hi,
I have a Sprint CDMA HTC EVO 3D. I tried root and get S-OFF for it. Unfortunately I failed and now the phone fail to boot.
Below is what I did from which you might be able to diagnose it and give me suggestions.
(1) The original status of mu phone is:
Stock rom, I never root it before.
HBOOT-1.58.0000
Android Version: 4.03
HTC Sense version: 3.6
Software version: 2.95.651.6.710RD
(2) My root procedures:
I followed this post: http://forum.xda-developers.com/showthread.php?t=1813818
I successfully unlocked phone with HTCDev, successfully Flashed 4EXT recovery, and successfully installed Superuser-3.1.3-arm-signed.zip. I also booted into sytem, everything worked well.
However I failed in next step of JuopunutBear's Wire Trick (S-OFF). When I ran ControlBear.exe, it finally hanged there.
Current status of my phone:
Unfortunately I did not make a backup to my original ROM, so there is no way to revert back by restoring backup.
Now the phone is in unlocked status, I was able to boot to HBOOT and also enter 4Ext recovery, however I am not able to boot into Android. If I try to boot into Android, it always hang at black screen.
I am able to boot to fastboot (USB) mode, I tried to flash some stock ROM (listed at http://forum.xda-developers.com/showpost.php?p=24268786&postcount=209), but I failed. For example, I ran a RUU of 2.89.exe, it detected my phone version is 2.95, and further update RUU failed.
Looks like my partition is ruined, but I might be wrong.
ANyone can help me to restore my phone to working status? At least I need the phone to be able to boo to Android.
Here are also some tries that I ever did:
(1) I ever put the PG86IMG.zip file (downloaded from http://forum.xda-developers.com/showpost.php?p=21593454&postcount=564) to my sdcard, still failed.
(2) I ever formatted all partition from 4EXT recovery
lsdyna said:
Here are also some tries that I ever did:
(1) I ever put the PG86IMG.zip file (downloaded from http://forum.xda-developers.com/showpost.php?p=21593454&postcount=564) to my sdcard, still failed.
(2) I ever formatted all partition from 4EXT recovery
Click to expand...
Click to collapse
EDIT:
Okay. I've got some questions.
1. You're stuck on some black screen as you said. It boots past the white HTC splash and then it's stuck on that black screen, right. Do you mean the juopunutbear "arrow screen" - juopunutbears boot.img?
2. I think if you had flashed the original boot img everything would have been fine.
3. The easiest way is to flash to stock, so lets try to figure out why it doesn't flash.
MrJyrks said:
Okay. So from what I understood, you are stuck on the black juopunutbear screen, right?
Click to expand...
Click to collapse
Yes, after I was stuck with black juopunutbear screen, I took battery out, reboot again, never was able to root to Android. I am only able to boot to HBoot.
lsdyna said:
Yes, after I was stuck with black juopunutbear screen, I took battery out, reboot again, never was able to root to Android. I am only able to boot to HBoot.
Click to expand...
Click to collapse
And you can boot to recovery, right?
EDIT:
One more thing. Which ruu were you trying to run
Edit2:
What's your CID? Use "fastboot getvar cid" or "fastboot oem readcid" (without quotes).
Edit3:
BTW, this was on the wire trick page... http://unlimited.io/jbtroubleshooting.htm - TROUBLESHOOTING There was everything you needed to know when you failed at something. Remember that page. You may need it the next time you try to do the wiretrick.
Q: Were you using a linux distro for the wire trick and did you use the appropriate files for wire trick since GB and ICS have separate tools?
If you want I may assist you in gaining s-off if we get this thing functional again.
Yes, I am able to boot to recovery.
I tried ROM's here
http://forum.xda-developers.com/showpost.php?p=24268786&postcount=209
and
http://forum.xda-developers.com/showthread.php?p=22519105#post22519105
I tried 2.17, 2.89, unfortunately none of them worked
My CID is SPCS_001
MrJyrks said:
And you can boot to recovery, right?
EDIT: One more thing. Which ruu were you trying to run
Edit2: What's your CID? Use "fastboot getvar cid" or "fastboot oem readcid" (without quotes).
Click to expand...
Click to collapse
lsdyna said:
Yes, I am able to boot to recovery.
I tried ROM's here
http://forum.xda-developers.com/showpost.php?p=24268786&postcount=209
and
http://forum.xda-developers.com/showthread.php?p=22519105#post22519105
I tried 2.17, 2.89, unfortunately none of them worked
My CID is SPCS_001
Click to expand...
Click to collapse
Aw man, I'm completely sorry I didn't see this: Software version: 2.95.651.6.710RD
That means, no RUU for you cause htc/sprint wasn't kind enough to provide the ruu. Also FYI you can't flash a ruu lower than your current one.
So your best bet is to flash the most stock 2.95 cdma rom you could find and right after, flash the stock cdma evo 3d kernel through fastboot or 4ext (I think 4ext smartflash does the same thing). Try to find something that's COMPLETELY STOCK - with no mods whatsoever or if you couldn't find any, try something that's almost* stock. That should get you booting and you can try s off again.
Edit: This shall work. http://www.negalite.com/index.php?topic=21.0 Try it and report back!!!
Now I only want to revert my phone to stock, not considering root at present time.
I searched 2.95 ROM, unfortunately the highest version that I can find is 2.89. Does this mean I have no way to revert my phone to live? Thanks a lot.
MrJyrks said:
Aw man, I'm completely sorry I didn't see this: Software version: 2.95.651.6.710RD
That means, no RUU for you cause htc/sprint wasn't kind enough to provide the ruu. Also FYI you can't flash a ruu lower than your current one.
So your best bet is to flash the most stock 2.95 cdma rom you could find and right after, flash the stock cdma evo 3d kernel through fastboot or 4ext (I think 4ext smartflash does the same thing). Try to find something that's COMPLETELY STOCK - with no mods whatsoever or if you couldn't find any, try something that's almost* stock. That should get you booting and you can try s off again.
Click to expand...
Click to collapse
I ever run a RUU 1.13...exe for mmy phone, it said my device is having 1.000, and it tried to update to 1.13. However, the update procedure always failed at some point, some at beginning, some failed at 'wring signature'...
MrJyrks said:
Aw man, I'm completely sorry I didn't see this: Software version: 2.95.651.6.710RD
That means, no RUU for you cause htc/sprint wasn't kind enough to provide the ruu. Also FYI you can't flash a ruu lower than your current one.
So your best bet is to flash the most stock 2.95 cdma rom you could find and right after, flash the stock cdma evo 3d kernel through fastboot or 4ext (I think 4ext smartflash does the same thing). Try to find something that's COMPLETELY STOCK - with no mods whatsoever or if you couldn't find any, try something that's almost* stock. That should get you booting and you can try s off again.
Click to expand...
Click to collapse
lsdyna said:
I ever run a RUU 1.13...exe for mmy phone, it said my device is having 1.000, and it tried to update to 1.13. However, the update procedure always failed at some point, some at beginning, some failed at 'wring signature'...
Click to expand...
Click to collapse
This shall work. http://www.negalite.com/index.php?topic=21.0 Try it and report back!!!
Flash like a normal rom and don't forget to flash the boot img because that's what's really causing you problems right now. I'd choose the deodexed one from there.
My HBoot screen shows below:
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.000
RADIO-1.09.00.0108
OpenADSP-v02.6.0.2226.00.0217
DO you think I still have chance to save my device? Thanks a lot.
lsdyna said:
I ever run a RUU 1.13...exe for mmy phone, it said my device is having 1.000, and it tried to update to 1.13. However, the update procedure always failed at some point, some at beginning, some failed at 'wring signature'...
Click to expand...
Click to collapse
lsdyna said:
My HBoot screen shows below:
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.000
RADIO-1.09.00.0108
OpenADSP-v02.6.0.2226.00.0217
DO you think I still have chance to save my device? Thanks a lot.
Click to expand...
Click to collapse
If you have access to the recovery, most likely, yes.
Hello MrJyrks,
Thank you so much for the link! I am eager to try that. Before I do that I think I shall ask two questions to avoid further mess up the device:
Question #1: To install the deodexed rom, which is the correct way:
(1) Rename the ZIP file to PG86IMG.ZIP, put to root of sdcard, then boot, letting the Bootloader to do the update.
(2) In 4EXT recovery, enable smartflash, enable script asserts, then install the zip from the root of sdcard.
Question #2: You said I shall flash boot image, can you tell me how to do this? I mean, where shall I get the boot image file? Flash it with 4EXT? SHall I do it before or after install ROM zip file?
Thank you very much for your helps!!!
MrJyrks said:
This shall work. http://www.negalite.com/index.php?topic=21.0 Try it and report back!!!
Flash like a normal rom and don't forget to flash the boot img because that's what's really causing you problems right now. I'd choose the deodexed one from there.
Click to expand...
Click to collapse
I tried install the stock ROM from your link (using 4EXT with smartflash enabled and script asserts enabled.) . Amazing that installation completed successfully (indeed this is the first ROM zip that I was able to install successfully since I mess up the device). When I exit After that, it did some further update which I guess is the boot.img that you mentioned.
4EXT it said 'a pending update for your boot partition is detected' and I think it was doing the boot image flash that you mentioned, right?
Unfortunately when I boo the device, I still got black screen.
Now I am unlocked and also rooted (since I successfully installed superuser in 4EXT). DO you think I shall lock the devioce before installing the stock ROM? If so, one possible issue is that if I relock the device, I found 4EXT is not available. In that case, how shall I install the ROM zip file?
Thanks.
MrJyrks said:
This shall work. http://www.negalite.com/index.php?topic=21.0 Try it and report back!!!
Flash like a normal rom and don't forget to flash the boot img because that's what's really causing you problems right now. I'd choose the deodexed one from there.
Click to expand...
Click to collapse
Further update:
I flashed boot image by: fastboot flash boot boot.img which is included in the stock ROM zip file.
The flash went successfully. However, I am still not able to boot to Android. WHat I have is the device hang there, alternatively displaying logo with white background, and black screen.
MrJyrks said:
This shall work. http://www.negalite.com/index.php?topic=21.0 Try it and report back!!!
Flash like a normal rom and don't forget to flash the boot img because that's what's really causing you problems right now. I'd choose the deodexed one from there.
Click to expand...
Click to collapse
I wiped cache and Dalvic, then re-flash the ROM, now I am able to boot as normal.
MrJyrks, you are my life save!!!
Your helps are sincerely appreciated !
lsdyna said:
I wiped cache and Dalvic, then re-flash the ROM, now I am able to boot as normal.
MrJyrks, you are my life save!!!
Your helps are sincerely appreciated !
Click to expand...
Click to collapse
You're welcome! I'm glad I could help!
---------- Post added at 12:02 PM ---------- Previous post was at 11:16 AM ----------
Oh, and if, in the future, you do try the wire trick and get stuck at some point you can revert the changes with ControlBear -r or ControlBear -f from command line. And you may also PM me if you need any help. Cheers!
MrJyrks, thank you so much!!!
MrJyrks said:
You're welcome! I'm glad I could help!
---------- Post added at 12:02 PM ---------- Previous post was at 11:16 AM ----------
Oh, and if, in the future, you do try the wire trick and get stuck at some point you can revert the changes with ControlBear -r or ControlBear -f from command line. And you may also PM me if you need any help. Cheers!
Click to expand...
Click to collapse
Similar problem, can't return to stock
I have a problem similar to lsdyna's, and am hoping that even though this post is old, MrJyrks or someone might be able to help me.
I am unsuccessfully trying to return my phone to stock. First a bit of history.
I had 2.95.651.6.710RD s-on hboot 1.58 Android Version: 4.03 HTC Sense version: 3.6 on my phone, and wanted root. I didn't need s-off, just wanted to root so could do some tweaking (stop some apps from autostarting, stop some form getting network access, etc.) so loaded 4EXT Recovery Touch, and got root (fastboot oem get_identifier_token method), got superuser in there, and happily began tweaking. Famous last words... I didn't make a backup right away (learned my lesson!) and suddenly found a 'overtweaked' sluggish phone on my hands.
Thought best thing would be to lose the root & return to stock & start over, carefully, making backups.
So I used Fastboot (fastboot oem lock) to lock it (worked) and proceeded to try to load RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe into it [via my computer], but didn't realize until reading MrJyrks post that a lower RUU couldn't be used.
I now am relocked (phone does boot up, but can tell the system tweaks are still slogging it), lost the recovery, and wondering what to do... do I try putting recovery back in & using the Negalite 2.95 stock deodex ROM MrJyrks mentioned? If so, how do I use that zip file method verses the exe one I tried thru my computer?
Thanks for the help
You had issues with the RUU because your main version is higher than that contained in the RUU.
Unlock, flash recovery again. Boot into recovery and flash this zip: https://copy.com/wlVvwssXXNN00Pe
That will lower your main version. Relock the bootloader, put the phone into fastboot USB mode, then run the RUU while in fastboot USB mode.
Should be back to stock after that.

Help phone has no OS!

long story short i have to send in my phone for repairs i was trying to get rid of my custom rom and install a stock rom but some how i wiped out the entire phone i do however managed to get twrp recovery but can't really do much in there as no files are in my phone and it wont let me side load the stock rom help please?
Ok now dont panic !
Does your phone still have eat least 70% of battery left ? if yes then reboot into the bootloader and relock it and then run the RUU file whitch will return your phone back to stock,and for more detailed info im sry beacuse im currenty on my phone
Sent from my HTC One X using xda premium
Lord_Xovon said:
long story short i have to send in my phone for repairs i was trying to get rid of my custom rom and install a stock rom but some how i wiped out the entire phone i do however managed to get twrp recovery but can't really do much in there as no files are in my phone and it wont let me side load the stock rom help please?
Click to expand...
Click to collapse
if your hboot is 1.40 - there is no stock ROM available.
You need to sideload some other custom ROM.
i face same problem
was trying to get rid of my custom rom and install a stock rom but some how i wiped out the entire phone i do however managed to get twrp recovery but can't really do much in there as no files are in my phone and it wont let me side load the stock rom help please?
now my fone stop on htc logo
plz help help
i try found same ruu file but not found plz help
ENRC2B_U pvt ship s-on rl
hboot_1.35.0000
cpld_none
microp_none
raido-3.1204.168.32
emmc-bootmode:disabled
cpu-bootmode:disabled
hw secure boot:disabled
modem path : off
nov 14 2012, 16:38:06
soy2 said:
i face same problem
was trying to get rid of my custom rom and install a stock rom but some how i wiped out the entire phone i do however managed to get twrp recovery but can't really do much in there as no files are in my phone and it wont let me side load the stock rom help please?
now my fone stop on htc logo
plz help help
i try found same ruu file but not found plz help
ENRC2B_U pvt ship s-on rl
hboot_1.35.0000
cpld_none
microp_none
raido-3.1204.168.32
emmc-bootmode:disabled
cpu-bootmode:disabled
hw secure boot:disabled
modem path : off
nov 14 2012, 16:38:06
Click to expand...
Click to collapse
Unlock bootloader
Install TWRP 2.6 etc...
use adb sideload <rom.zip> to sideload the custom ROM
try it a number of times as it takes time to get recognized...
flash the kernel
Addicted2xda said:
Unlock bootloader
Install TWRP 2.6 etc...
use adb sideload <rom.zip> to sideload the custom ROM
try it a number of times as it takes time to get recognized...
flash the kernel
Click to expand...
Click to collapse
I have the same issue i unlocked and rooted my phone and went to flash a custom ROM when something went wrong...long story short i ended up wiping my entire phone, i relocked the phone and tried to flash the factory RUU using the all in one toolkit but i couldnt find and RUU.zip file please help
Everything you need to fix your device is here
Read and search. This has been covered 1000000 times.
brenntard said:
I have the same issue i unlocked and rooted my phone and went to flash a custom ROM when something went wrong...long story short i ended up wiping my entire phone, i relocked the phone and tried to flash the factory RUU using the all in one toolkit but i couldnt find and RUU.zip file please help
Click to expand...
Click to collapse
What is your hboot version?
I hope you have Android SDK installed and running in your system?
I guess I have just run into the same issue. I wasn't able to find any help in the "Device Essentials" thread, unfortunately.
I have no rom. ADB doesnt work when phone is in bootloader or recovery (twrp 2.6.3.0) and I can't mount the usb storage to get the rom onto my phone. I miss the days of my samsung captivate....It was so easy!! Thanks for reading.
I guess the key point here is that I can't sideload anything because adb isnt working in recovery. My hboot is 1.40.
1 25664338
TheJokah said:
Everything you need to fix your device is here
Read and search. This has been covered 1000000 times.
Click to expand...
Click to collapse
Thank you but those links on that page do not work
brenntard said:
Thank you but those links on that page do not work
Click to expand...
Click to collapse
Which version do you have ATT-Telus or International?
Did you try one of the toolkits like Windroid or Hasoons Toolkit. I would use Hasoon2000's first to return device to stock condition, and then try Windroid if that does not work.
TheJokah said:
Which version do you have ATT-Telus or International?
Did you try one of the toolkits like Windroid or Hasoons Toolkit. I would use Hasoon2000's first to return device to stock condition, and then try Windroid if that does not work.
Click to expand...
Click to collapse
i have the AT&T version with hasoons att htc one x all in one toolkit downloaded. i tried returning it to stock from hasoons toolkit but to no evail... when i go to reboot and twrp and try to reboot the system it tells me i have no os installed and asks if i want to continue so i went ahead and rebooted anyway even though it said no os installed, it then came up with a message saying i am not rooted anymore and do i want to install supersu...i am very confused
brenntard said:
i have the AT&T version with hasoons att htc one x all in one toolkit downloaded. i tried returning it to stock from hasoons toolkit but to no evail... when i go to reboot and twrp and try to reboot the system it tells me i have no os installed and asks if i want to continue so i went ahead and rebooted anyway even though it said no os installed, it then came up with a message saying i am not rooted anymore and do i want to install supersu...i am very confused
Click to expand...
Click to collapse
did you try and install supersu just for the hell of it?? You may want to install stock recovery, then re-lock bootloader, and then use RUU. This almost always get your device back to stock.:good:
TheJokah said:
did you try and install supersu just for the hell of it?? You may want to install stock recovery, then re-lock bootloader, and then use RUU. This almost always get your device back to stock.:good:
Click to expand...
Click to collapse
Yes i tried to install it just to see what would happen...my hpone rebooted and got stuck at the HTC quietly brilliant screen. so i should relock the phone and run the RUU? even if i dont have an os installed this will bring me back to stock? meaning i can use my phone again?
brenntard said:
Yes i tried to install it just to see what would happen...my hpone rebooted and got stuck at the HTC quietly brilliant screen. so i should relock the phone and run the RUU? even if i dont have an os installed this will bring me back to stock? meaning i can use my phone again?
Click to expand...
Click to collapse
yes it will put one there for you then you can unlock, install twrp or CM, and then custom rom. Profit! :highfive:
See, my issue is that I cant go back to a stock rom because my hboot 1.40....
copying to TWRP
parkerdjohnson said:
See, my issue is that I cant go back to a stock rom because my hboot 1.40....
Click to expand...
Click to collapse
I can send you a link in pm to send your costom or stock rom to TWRP but it may still not work to install. ask how I know about that? Coz I totally have the same problem and cant get rid of it for days. my hboot is 1.32 and I have the all in one toolkit.
İF anyone can help me about finding the right RUU for my htc one x+ (cid: cws-001) and how to go back to stock recovery I would be greatful.
Thankss
parkerdjohnson said:
See, my issue is that I cant go back to a stock rom because my hboot 1.40....
Click to expand...
Click to collapse
Im also on HBOOT 1.4 I believe you need this RUU.
I am going to revert to stock to make sure you can use this. Please just make sure what cid # you have. It should be CWS_001 for ATT Branded.(like mine )
edit: RUU ran fine with HBOOT 1.40
---------- Post added at 05:25 PM ---------- Previous post was at 05:20 PM ----------
[/COLOR]
sahtaan_yusuf said:
I can send you a link in pm to send your costom or stock rom to TWRP but it may still not work to install. ask how I know about that? Coz I totally have the same problem and cant get rid of it for days. my hboot is 1.32 and I have the all in one toolkit.
İF anyone can help me about finding the right RUU for my htc one x+ (cid: cws-001) and how to go back to stock recovery I would be greatful.
Thankss
Click to expand...
Click to collapse
You need to have this stock recovery installed. then relock bootloader, and then run this RUU
this should fix it. if that RUU does not work, try the link to the RUU I gave for parkerdjohnson
Thanks
thanks so much for the links my brother, I am downloading the RUU links but the stock recovery link doesnt work. do you have another one? or I have the all in one tool kit, do I have the chance to go back to stock recovery by using this toolkit?
sahtaan_yusuf said:
thanks so much for the links my brother, I am downloading the RUU links but the stock recovery link doesnt work. do you have another one? or I have the all in one tool kit, do I have the chance to go back to stock recovery by using this toolkit?
Click to expand...
Click to collapse
i attached a .zip file with the recovery inside. THIS IS NOT FLASHABLE! You need to flash from fastboot or with an All in one.
edit:
I uploaded the wrong file :banghead: I will try to find the right one. Sorry
Edit 2:
found the file and uploaded.

Categories

Resources