Related
Hi all, well i was playing with my Desire S trying to install the generic wwe rom on it since it is brands, and ended up messing up the phone real badly.
Well i used the good old way of creating a gold card and then flash the RUU. The first time went well, i flashed the generic 1.28.401.1 rom on it, retaining the 0002 boot it had.
Then i went to flash the 2.10 wwe RUU and this time things went bad. For some reason the gold card powers were not evoked and it gave me "CID error" but, the all mighty 2.00.0002 hboot was flashed on the phone before it gave the error. So i had to downgrade the bootloader and i used this great guide as a help but once again things went wrong.
I flashed a pre rooted RUU 2.10 rom using 4EXT recovery as the guide tells to do but, i have no wi-fi and usb connection on the rom. This means i got no way to connect the phone to a pc to change the misc_version file and don't even have wi-fi. So i end up asking for any help here as the phone is left in a very bad situation that i can't see the way out...
Try to reflash same ROM again.
Sent from my Desire S
I believe you should have named your thread "I really messed up my Desire S", as the current title is sort of misleading ;-).
In your place I'll try flashing an older ROM, even your initial one and start over. If you still have acces to 4EXT recovery you just have to take out your sdcard, put it on a pc and copy the rom that way (since USB not working). Or you can try to activate USB drive within 4EXT recovery, maybe it'll work.
If you don't have 4EXT recovery, you can try flashing recovery.img (from 4EXT zip file) or a rom by renaming them as PG88IMG.zip and place them on the card (via PC). If you boot to bootloader and try to flash them using the flash procedure for radio, it might work like this.
Sorry if I am saying a stupid thing but this is what I'll try if I had these issues.
Rapier said:
In your place I'll try flashing an older ROM, even your initial one and start over. If you still have acces to 4EXT recovery you just have to take out your sdcard, put it on a pc and copy the rom that way (since USB not working). Or you can try to activate USB drive within 4EXT recovery, maybe it'll work.
If you don't have 4EXT recovery, you can try flashing recovery.img (from 4EXT zip file) or a rom by renaming them as PG88IMG.zip and place them on the card (via PC). If you boot to bootloader and try to flash them using the flash procedure for radio, it might work like this.
Sorry if I am saying a stupid thing but this is what I'll try if I had these issues.
Click to expand...
Click to collapse
Well the initial ROM i had on the phone was a branded Vodafone PT and i can't find that ROM anywhere and for some reason goldcards are not working after the bootloader was flashed by the RUU.
I still have the 4EXT recovery and usb works in it. Flashing a ROM via the PG88IMG only works if the RUU has the right CID as the phone is branded, now i don't know if flashing a rooted ROM using that procedure will work. The other thing i may try is flashing an older rooted ROM, like the 1.28.401.1 and see if the wi-fi and usb works.
Well what i can say is that the phone is completely cursed and i can't find a way out of this.
I tried to flash an older rooted ROM, 1.48 and the same thing happened, no wi-fi and usb connection.
I tried to flash custom ROMs then. Even worse, the phone doesn't boot, gets stuck on the htc logo. I tried more ROMS and the same happens.
Flashing official RUU will not work due to the CID error. All i end up is that i can't put the phone to work, simple as that. The only chance i think is to send the phone to HTC and tell them that a screwed the system and want them to flash it all again. I don't know how much that will cost but it seems to be the only way out.
smash_07 said:
Well what i can say is that the phone is completely cursed and i can't find a way out of this.
I tried to flash an older rooted ROM, 1.48 and the same thing happened, no wi-fi and usb connection.
I tried to flash custom ROMs then. Even worse, the phone doesn't boot, gets stuck on the htc logo. I tried more ROMS and the same happens.
Flashing official RUU will not work due to the CID error. All i end up is that i can't put the phone to work, simple as that. The only chance i think is to send the phone to HTC and tell them that a screwed the system and want them to flash it all again. I don't know how much that will cost but it seems to be the only way out.
Click to expand...
Click to collapse
Return it if you still have warranty. If not, read on:
1. Check you HBOOT if it got updated to the new one.
2. If it is updated, I suggest to flash the pre-root 2.10.5 ROM. Then see if it is going to work.
3. If it does, downgrade from there if you still want to.
Skanob said:
Return it if you still have warranty. If not, read on:
1. Check you HBOOT if it got updated to the new one.
2. If it is updated, I suggest to flash the pre-root 2.10.5 ROM. Then see if it is going to work.
3. If it does, downgrade from there if you still want to.
Click to expand...
Click to collapse
Yes it has warranty but im sure it will not be covered since i was the one who messed up the phone system.
Another thing i can do, but this is not a certain option, is to wait and see if alpharev can find a way to S-OFF the new hboot with revolutionary and then open a way to flash the RUUs again and older bootloaders.
But i am more looking to sending it to HTC. Does anyone have an idea how much does it cost to reflash the system on the phone?
smash_07 said:
Yes it has warranty but im sure it will not be covered since i was the one who messed up the phone system.
Another thing i can do, but this is not a certain option, is to wait and see if alpharev can find a way to S-OFF the new hboot with revolutionary and then open a way to flash the RUUs again and older bootloaders.
But i am more looking to sending it to HTC. Does anyone have an idea how much does it cost to reflash the system on the phone?
Click to expand...
Click to collapse
It would really help if you have given your bootloader details.\
Things you still can do:
1. If hboot is updated to 2.00.0002, then you need to unlock it, flash custom recovery via fastboot, flash custom rom, usable phone.
2. If hboot is S-OFF, same as 1 but skip unlocking. Again, usable phone.
Also, there are a lot of ways for you to change your hboot once you are S-OFF. Use search.
You are able to install custom roms, but the phone doesn't boot? And the 1.47 pre rooted boots but no WiFi?
You unlocked the phone with HTC.dev.
Steps:
- pick a custom Rom, any Rom
- extract boot.img from that Rom
- flash the Rom in recovery
- do not reboot
- flash boot.img using fastboot command from your computer (search around for instructions)
- reboot and enjoy
The problem is your phone is still s-on, and blocking the kernel from being written during normal flash. You end up with old kernel and new un-matching modules and libs.
I could be wrong though...
Cheers
Sent from my HTC Desire S using xda premium
I my case, that was may of this year, I send my desire (not s) back because of bootproblems, and they reflashed it for free. This was in the Netherlands so don't know how easygoing they are in Portugal, but it's worth a shot I guess.
lowveld said:
You are able to install custom roms, but the phone doesn't boot? And the 1.47 pre rooted boots but no WiFi?
You unlocked the phone with HTC.dev.
Steps:
- pick a custom Rom, any Rom
- extract boot.img from that Rom
- flash the Rom in recovery
- do not reboot
- flash boot.img using fastboot command from your computer (search around for instructions)
- reboot and enjoy
The problem is your phone is still s-on, and blocking the kernel from being written during normal flash. You end up with old kernel and new un-matching modules and libs.
I could be wrong though...
Cheers
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Well i can say that this has worked. I flashed the boot.img form the CM7 rom and it worked perfectly, it booted CM7 rom and have wi-fi and usb connection. Now the only thing left is to be able to flash official RUUs passing tne CID error which for some reason the Goldcards are not bypassing.
But many thanks for your help
(ou como se poderia dizer, obrigado pela ajuda)
I've been reading a little on this S-off thing and was wondering what its purpose actually is and what the advantages are from doing it? I know I was able to flash my HTC Vivid without it so what is it really used for? Thank you in advance.
Answer...
phrotac said:
I've been reading a little on this S-off thing and was wondering what its purpose actually is and what the advantages are from doing it? I know I was able to flash my HTC Vivid without it so what is it really used for? Thank you in advance.
Click to expand...
Click to collapse
See: What Is S-OFF & How To Gain It On HTC Android Phones With unrevoked forever
In a nutshell, S-OFF means that the NAND portion of the device is unlocked and can be written to. The default setting for HTC’s devices is S-ON, which means that neither can you access certain areas of the system nor can you guarantee a permanent root. Furthermore, signature check for firmware images is also ensured by the S-ON flag.
Click to expand...
Click to collapse
---------- Post added at 11:01 PM ---------- Previous post was at 10:58 PM ----------
Basically, if you are going to be installing custom ROMs, you probably want to set s-off so you can flash unsigned ROMs.
Very interesting. Thank you for responding That gives me something to think about.
In short. S-OFF allows you to change pretty much everything. Your CID, firmware (radio, hboot etc) and most important thing probably, allows you to flash older RUUs
Sent from my HTC Sensation XE with Beats Audio using Tapatalk 2
If you are going to be changing roms, themes, etc, then leave it off. If not then turn in back on.
kdub83 said:
If you are going to be changing roms, themes, etc, then leave it off. If not then turn in back on.
Click to expand...
Click to collapse
I found the perfect ROM from WCX but I never had to use a wire on it though. Is HTCdev the reason why? I'm just trying to figure out this whole s-off thing because I saw a video where someone used a piece of insulated wire and was wondering why. I'm sorry if I wasn't clear enough with my questions earlier... My bad.
S-OFF
Hi - I've had HTC devices since the Eris way back in 2010 - currently running the Rezound. Hopefully I can shed some more light.
When I first got the Rezound I was coming over from an S-OFF Eris... if you wanted to flash something custom, you'd go to htcdev.com and use their "unlock bootloader" tool. Once you ran that and followed a few other steps, you are reverted to stock and your bootloader now has a little warning "unlocked" in the text at the top. This was in January 2012, and ROMs back then came with 2 things - the ROM and a Kernel. You had to flash the kernel separatley (and via the bootloader as opposed to a custom recovery), as S-ON (even unlocked) still won't let you write to certain places (in the case of the kernel, its the boot partition).
We got S-OFF several months later (the thing using the wire trick). In S-OFF - custom recovery can write to all areas of the device - no more need for any separate files, you just flash a ROM in custom recovery and everything is set up the way it should be. Added bonus - no need to unlock the bootloader from htcdev... so no "unlocked" warning message.
Here was my S-OFF process:
1. Run the official RUU exe to get your device back to stock with a Locked bootloader (backup any files on the SDCard first!).
2. Perform the wire trick
3. Flash a custom recovery and proceed with flashing ROMS
Let me know if I can clarify anything...
Basically allows you to flash RADIOS that have not been signed by HTC
Sent from my Galaxy Nexus using xda premium
Ryan Kasper said:
Hi - I've had HTC devices since the Eris way back in 2010 - currently running the Rezound. Hopefully I can shed some more light.
When I first got the Rezound I was coming over from an S-OFF Eris... if you wanted to flash something custom, you'd go to htcdev.com and use their "unlock bootloader" tool. Once you ran that and followed a few other steps, you are reverted to stock and your bootloader now has a little warning "unlocked" in the text at the top. This was in January 2012, and ROMs back then came with 2 things - the ROM and a Kernel. You had to flash the kernel separatley (and via the bootloader as opposed to a custom recovery), as S-ON (even unlocked) still won't let you write to certain places (in the case of the kernel, its the boot partition).
We got S-OFF several months later (the thing using the wire trick). In S-OFF - custom recovery can write to all areas of the device - no more need for any separate files, you just flash a ROM in custom recovery and everything is set up the way it should be. Added bonus - no need to unlock the bootloader from htcdev... so no "unlocked" warning message.
Click to expand...
Click to collapse
Thank you very much. That DOES explain it very well.
Ryan Kasper said:
Here was my S-OFF process:
1. Run the official RUU exe to get your device back to stock with a Locked bootloader (backup any files on the SDCard first!).
2. Perform the wire trick
3. Flash a custom recovery and proceed with flashing ROMS
Let me know if I can clarify anything...
Click to expand...
Click to collapse
Are you saying I can make my bootloader say LOCKED again? I thought I could only make it say UNLOCKED or RELOCKED now that I've unlocked it. That is so awesome. And then the s-off will give me permanent root?
Are you saying I can make my bootloader say LOCKED again? I thought I could only make it say UNLOCKED or RELOCKED now that I've unlocked it. That is so awesome. And then the s-off will give me permanent root?
Click to expand...
Click to collapse
Yup! Once you are S-OFF you will be back on the stock bootloader that reads "locked". There are a variety of HBOOTS (AKA Bootloaders) you can flash (well - there are for my device currently...). For the Rezound right now I have a variety of them with different verbages in the title (example - "locked S-ON", "Rezound") - or you can simply leave it at the stock HBOOT though you will not be able to flash, say a custom recovery, using fastboot in the bootloader via a terminal emulator (you have to use the PH98IMG.zip method in the bootloader)... Also the devs that made the wire trick available offer their own hboot "juopunutbear" - this one allows fastboot recovery flashing... - here for the vivid http://unlimited.io/jb_holiday.htm
Also - be VERY careful when updating the bootloader - it is a very common way to brick the device... I always check the MD5Sum before copying to SD and flashing.
And regarding permanent root - absolutely. Flash SuperSU from custom recovery (the zip version available here - http://forum.xda-developers.com/showthread.php?t=1538053
Ryan Kasper said:
Yup! Once you are S-OFF you will be back on the stock bootloader that reads "locked". There are a variety of HBOOTS (AKA Bootloaders) you can flash (well - there are for my device currently...). For the Rezound right now I have a variety of them with different verbages in the title (example - "locked S-ON", "Rezound") - or you can simply leave it at the stock HBOOT though you will not be able to flash, say a custom recovery, using fastboot in the bootloader via a terminal emulator (you have to use the PH98IMG.zip method in the bootloader)... Also the devs that made the wire trick available offer their own hboot "juopunutbear" - this one allows fastboot recovery flashing... - here for the vivid http://unlimited.io/jb_holiday.htm
Also - be VERY careful when updating the bootloader - it is a very common way to brick the device... I always check the MD5Sum before copying to SD and flashing.
And regarding permanent root - absolutely. Flash SuperSU from custom recovery (the zip version available here - http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
This information is golden. Thank you very much
tinky1 said:
In short. S-OFF allows you to change pretty much everything. Your CID, firmware (radio, hboot etc) and most important thing probably, allows you to flash older RUUs
Sent from my HTC Sensation XE with Beats Audio using Tapatalk 2
Click to expand...
Click to collapse
Awesome! I have a couple more questions still *scratches head in confusion*...
Once I S-Off, can I reverse it if needed?
and
<Ignore this part... I found the information LOL>
What is an RUU? I have googled it and I can't find anything about it (maybe I'm just too tired or something)
phrotac said:
Awesome! I have a couple more questions still *scratches head in confusion*...
Once I S-Off, can I reverse it if needed?
Click to expand...
Click to collapse
Yup - here is how I'd do it if I had to for my device - http://forum.xda-developers.com/showthread.php?t=1612937 - careful if you do and read any warnings (brick opportunities again)
Hi,
It is possible, if I install custom rom, some function will not work without S-OFF?
The phone was routed and unlokced but it was S-ON.
Hi everyone,
I feel kind of bad for asking such a generic question like this, and I assure you that I have read around and done my research, but before I do potentially dangerous, irreversible, things to my device, I just want to make sure that I will perform the necessary steps correctly.
Basically, I have owned my HOX since launch date, and it came with either 1.73 or 1.85 base. As such, I rooted and unlocked the bootloader as soon as the exploits were available, and have been comfortably flashing ROMs and kernels every since. However, I have been experiencing some issues with data connectivity and stuff, issues that remain with any ROM, kernel, or radio that I flash. The details aren't important...
Now, I want to basically "start over" with my HOX. As if it was a brand new, unmodified, fresh device. So basically, unroot, relock bootloader, RUU, etc... And then start all over, root, unlock bootloader, install recovery, etc.....
Basically, what exact steps do I need to take to accomplish the "starting over"? As in the methods to use, the RUU to use, etc... ?
An outline of the steps, basically. My biggest fear is restoring to the wrong thing and losing my old HBOOT.
Again, I know this question probably gets asked often, but please bear with me through this.
I ruu'd my wife a and it was about 3 weeks before att sent her the next update lol. As long as you don't accept it you'll be fine. I'm sure you'd prolly root as soon as its finished anyway..
But you got it right. No need to unroot, just fire up fastboot and enter "fastboot oem lock". (Without quotes)
Figure out which ruu you need, most likely 1.85. Make sure you have the right HTC drivers updated, and make sure HTC sync is working right. Download ruu, which is an executable application, and run it. It should factory restore your phone like the day you bought it.
As far as restoring to the "bad" hboot, it shouldn't let you complete an ruu that's for another firmware other than what you had on it when you got root... So you'll be safe. Good luck bro, come back and let us know how it went :thumbup:
Sent from my One X using Tapatalk 2
So basically relock the bootloader with "fastboot oem lock" , and then RUU, and I have a fresh new phone?
And for determining which RUU I need, either 1.73 or 1.85, if I try running the wrong one, it will stop me?
And since I'm still on the older HBOOT with the older initial base, root and unlock the same way I did originally?
And also, once I relock my boot loader, should I immediately RUU?
So a full outline would be:
Connect phone to computer ( with drivers and all)
Boot into fast boot
Relock bootloader with command
RUU
Let phone boot
Re-root
Re-unlock bootloader
Install recovery
Flash ROMS!
?
And just because it's been forever since I've done it, what are the steps again for RUUing? Do I need to boot the phone into any special mode? Or I just connect the phone to the PC and run the RUU?
And after I relock the bootloader, will the phone reboot out of fastboot or anything? Or should I go immediately from the relock phase to the RUU phase?
Thanks
So basically relock the bootloader with "fastboot oem lock" , and then RUU, and I have a fresh new phone? You got it.
And for determining which RUU I need, either 1.73 or 1.85, if I try running the wrong one, it will stop me? Yes, it'll throw an error when you try to go through the RUU install process.
And since I'm still on the older HBOOT with the older initial base, root and unlock the same way I did originally? Yes. This is a fresh phone install after you run the RUU (like the day you bought it).
And also, once I relock my boot loader, should I immediately RUU? Yes. There's not a lot else you really need to do (especially on bricked phones, not a lot you CAN do).
So a full outline would be:
Connect phone to computer ( with drivers and all)
Boot into fast boot
Relock bootloader with command
RUU
Let phone boot
Re-root
Re-unlock bootloader
Install recovery
Flash ROMS!
? - Yes, that's pretty much it.
And just because it's been forever since I've done it, what are the steps again for RUUing? Do I need to boot the phone into any special mode? Or I just connect the phone to the PC and run the RUU? - Connect to pc in fastboot usb and run it from there.
And after I relock the bootloader, will the phone reboot out of fastboot or anything? - Nope, it'll stay in fastboot unless you reboot it.
Or should I go immediately from the relock phase to the RUU phase? - That makes things a little faster
Yep.. Run it from anywhere, as long as your computer recognizes your device let us know how it goes
Sent from my One X using Tapatalk 2
Ok, thanks a lot.
I don't have a PC with me right now (mac user) but once I get the opportunity I will go through with this. Thanks again!
Im hoping this thread may help me to solve my problem (I'm a total noob too lol)
I rooted and flashed a Rom on my HTC One S, and I had the same issues as OP
Im with Fido, but I was told that both Fido and Rogers use the same RUU
Trying to go back to stock, I relocked the bootloader.
1. then I ran the RUU (found a tutorial online), but I got an error message (155: wrong RUU or file cant be larger or something like that)
2. then I tried an alternative method : extract 2 files from the RUU, move them to another folder and from there run a cmd; didnt work either
(By the way, in method number 1, I also had to flash a recovery file (stock recovery) during the bootloader unlock process)
Did I do it the right way?
Can some Senior member give me a detailed step by step method?
Why do you keep posting HTC ONE S questions in our HTC ONE X forum? What is wrong with using the correct forum?
954wrecker said:
Why do you keep posting HTC ONE S questions in our HTC ONE X forum? What is wrong with using the correct forum?
Click to expand...
Click to collapse
Yeah.
954wrecker said:
Why do you keep posting HTC ONE S questions in our HTC ONE X forum? What is wrong with using the correct forum?
Click to expand...
Click to collapse
I did ???
Hey what do you know :laugh:
I have tried to do this multiple times, but no matter how many times a run the 2.2 exploit, and flash the unlock code bootloader continues to say relocked? any ideas
Yes, you need to check your pm. You need to hard reset the device. Hold power until device reboots, capacitive keys will flash during the process. Then run the unlock and you're device will unlock. I spent a full day to figure this out... Lol
Sent from my HTC One XL using Tapatalk 2
anyone happen to have a link on how to reset your phone back to factory defaults? i've had too many issues with roms, and my wifi, and as i use it for work, i cant have this happening.
I didn't back up the factory ROM before i started flashing, does that mean im pretty much screwed?
I have Hboot 1.14
Behemyth said:
anyone happen to have a link on how to reset your phone back to factory defaults? i've had too many issues with roms, and my wifi, and as i use it for work, i cant have this happening.
I didn't back up the factory ROM before i started flashing, does that mean im pretty much screwed?
I have Hboot 1.14
Click to expand...
Click to collapse
If you want to reset to stock just run the ruu like the poster above is trying to do.
Sent from my HTC One XL
ECEXCURSION said:
If you want to reset to stock just run the ruu like the poster above is trying to do.
Sent from my HTC One XL
Click to expand...
Click to collapse
Nobody answered his question about if he needs to find a RUU specific to his device. I've been looking and can't find an RUU specific to 1.14, and I dont want to chance bricking my device.
Behemyth said:
Nobody answered his question about if he needs to find a RUU specific to his device. I've been looking and can't find an RUU specific to 1.14, and I dont want to chance bricking my device.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1671237
scroll down to the stock ruu section and look up the firmware 2.2 not the hboot 1.14
Well, I'm the OP, and I ended up figuring out what RUU to use, which was 1.73. Basically, I ran 'fastboot oem lock' , then ran the RUU right afterwards, then booted up and ran the root exploit, rooted, and then ran 'fastboot oem unlock' using my old Unlock.bin file that I had from the very first time I unlocked the bootloader. From there, I installed a custom recovery and was good to go.
Yah, if your using 2.20 firmware, run the below link, works like a charm. Must make sure you re-lock the bootloader before, or it will error out. Just hold down the power button until it turns off if this happens.
possible brick
Skeeterdrums said:
So basically relock the bootloader with "fastboot oem lock" , and then RUU, and I have a fresh new phone? You got it.
And for determining which RUU I need, either 1.73 or 1.85, if I try running the wrong one, it will stop me? Yes, it'll throw an error when you try to go through the RUU install process.
And since I'm still on the older HBOOT with the older initial base, root and unlock the same way I did originally? Yes. This is a fresh phone install after you run the RUU (like the day you bought it).
And also, once I relock my boot loader, should I immediately RUU? Yes. There's not a lot else you really need to do (especially on bricked phones, not a lot you CAN do).
So a full outline would be:
Connect phone to computer ( with drivers and all)
Boot into fast boot
Relock bootloader with command
RUU
Let phone boot
Re-root
Re-unlock bootloader
Install recovery
Flash ROMS!
? - Yes, that's pretty much it.
And just because it's been forever since I've done it, what are the steps again for RUUing? Do I need to boot the phone into any special mode? Or I just connect the phone to the PC and run the RUU? - Connect to pc in fastboot usb and run it from there.
And after I relock the bootloader, will the phone reboot out of fastboot or anything? - Nope, it'll stay in fastboot unless you reboot it.
Or should I go immediately from the relock phase to the RUU phase? - That makes things a little faster
Click to expand...
Click to collapse
I did this, but my phone never boots. It just stays at the bootloader after i run the RUU. Any ideas? :/
Also, i get the "this build is for development purposes only" message under the HTC logo before the phone enters the bootloader.
EDIT: managed to get the bootloadr unlocked again via HTCDev.com and flashed recovery and ROM. Guess Im not starting fresh after all lol
I've tried to flash both CM 10.1 and LiquidSmooth RC2 (and a few others). Both result in my phone getting stuck on the "htc quietly brilliant" screen. I can install CM 10 or any other non- 4.2 roms. I flashed the boot files before flashing the roms. What is it that I'm doing wrong?
Try flashing the CM10.1 boot.img after flashing the rom.
If that doesn't work, go s-off and come back (really, you should be s-off anyway).
iElvis said:
Try flashing the CM10.1 boot.img after flashing the rom.
If that doesn't work, go s-off and come back (really, you should be s-off anyway).
Click to expand...
Click to collapse
I like to take baby steps with my phone. But I'm not having luck, so I'll attempt to s-off and try again.
seaneschen said:
I like to take baby steps with my phone. But I'm not having luck, so I'll attempt to s-off and try again.
Click to expand...
Click to collapse
S-off will make your life a whole lot easier and a lot fewer headaches. And it is so incredibly simple
Will S-off fix the problem of the roms not working? If not, what should my next step be?
S-off removes the need to flash the boot.img separately in fastboot. You can flash whatever you want.
You need to have S-Off to downgrade your touchscreen firmware to use AOSP ROMs...so, you really need S-Off.
this is what I did, it worked well:
1. unlock up your bootloader
2. flash TWRP and then any Sense ROM that is rooted
3. lock up your bootloader again
4. manually gain SUperCID and unlock your bootloader at the same time: http://forum.xda-developers.com/showthread.php?t=1671396 (make sure when you are told to enter the new CID in the Hex editor that you change the CID to 22222222
3. Gain S-OFF: http://forum.xda-developers.com/showthread.php?t=2155071
4. downgrade your touchscreen firmware and HBOOT version: http://forum.xda-developers.com/showthread.php?t=2159863
5. flash any AOSP/AOKP ROM you want
if your computer is ready and you know basic fastboot and adb knowledge...this shouldn't take more than 5 minutes IF YOU UNDERSTAND THE PROCESS. So i suggest a once-over of the instructions in the threads linked and just go at it.
Deus_eps_machina said:
You need to have S-Off to downgrade your touchscreen firmware to use AOSP ROMs...so, you really need S-Off.
this is what I did, it worked well:
1. unlock up your bootloader
2. flash TWRP and then any Sense ROM that is rooted
3. lock up your bootloader again
4. manually gain SUperCID and unlock your bootloader at the same time: http://forum.xda-developers.com/showthread.php?t=1671396 (make sure when you are told to enter the new CID in the Hex editor that you change the CID to 22222222
3. Gain S-OFF: http://forum.xda-developers.com/showthread.php?t=2155071
4. downgrade your touchscreen firmware and HBOOT version: http://forum.xda-developers.com/showthread.php?t=2159863
5. flash any AOSP/AOKP ROM you want
if your computer is ready and you know basic fastboot and adb knowledge...this shouldn't take more than 5 minutes IF YOU UNDERSTAND THE PROCESS. So i suggest a once-over of the instructions in the threads linked and just go at it.
Click to expand...
Click to collapse
We can assume he has an att one x.. you're instuections are kind of worthless he probably already has supercid it doesn't need to be 22222222.... He just needs to flash to viper(for ease) and then s off
Help im new!
Soo i recently got my htc one x on android jelly bean 4.2.2 from at&t and is there a method or easy root method for this version? 4.2.2, with 5.18? I really want to try and root my phone but i know nothing about messing with all these types of files, and i dont want to risk destroying my phone.
Im not sure if there is already a post or something about this and if it is im sorry, these forums are a bit overwhelming and i am new.
I would very much appeircate any help or info on being able to easily root my htc one x 4.2.2, 5.18 at&t white.
The recent at&t update patched the last exploit for gaining SuperCID in order to unlock the bootloader. Long story short, there's no way for you to root your phone since you took the update. If you had done it before taking the update you'd be fine. You'll have to wait and see if a dev comes up with a new exploit for the new firmware.
Sent from my Evita
timmaaa said:
The recent at&t update patched the last exploit for gaining SuperCID in order to unlock the bootloader. Long story short, there's no way for you to root your phone since you took the update. If you had done it before taking the update you'd be fine. You'll have to wait and see if a dev comes up with a new exploit for the new firmware.
Sent from my Evita
Click to expand...
Click to collapse
Well that sucks because even when i was on 4.1.1 i could not root my stupid phone. There was no easy way to do it on 4.1.1 3.18, and now i cant do crap with this 4.2.2 on 5.18. why would i not be able to root it if other people can root their phones that are on 4.3 and higher like the Htc One.
There is a perfectly easy way to unlock your bootloader on the 3.18 software, it isn't a stupid phone, nor is the exploit hard to achieve, hundreds if not thousands of people have done it. It's as simple as entering a few adb/fastboot commands.
You can't root on 5.18 because the update patched the weakness that was exploited in the 3.18 software/firmware. It takes time for devs to crack these things and the update has only just been released. It's not even sure whether the devs will want to spend any time finding a crack for a phone that's relatively old now. This is why you never take an update without first unlocking/rooting, unless you're comfortable with the fact that you won't be able to (it is a well established fact that updates patch exploits).
Sent from my Evita
5.18!to 3.18 ruu
I also took the update unaware I would not be able to root again...
Would it be possible to run the stock 3.18 ruu and then root?
brenntard said:
I also took the update unaware I would not be able to root again...
Would it be possible to run the stock 3.18 ruu and then root?
Click to expand...
Click to collapse
Bootloader details please.
Sent from my Evita
timmaaa said:
Bootloader details please.
Sent from my Evita
Click to expand...
Click to collapse
Tampered
Relocked
Evita put ship s-on rl
Hboot-2.18.0000
Radio-1.35a.32.45.27
Opendsp-v33.1.0.45.1128
Emmc-boot
It's weird, I tried using the all in one toolkit and was able to unlock the boot loader, get twrp recovery working and flash supersu. The only problem I ran into was when I opened supersu it said the binaries need to update. The first time I updated them and it was fine then the phone shut off and supersu would always need updated when opened...I downloaded titanium backup and was able to get root access before my phone restarted and I had to update supersu again... It is now relocked, obviously, but easy enough to unlock again using the toolkit
You're in a different category because you had gotten SuperCID in the past I assume. That's the main determining factor in whether you can unlock the bootloader. You should be fine as long as you still have SuperCID.
Code:
fastboot oem readcid
Sent from my Evita
timmaaa said:
You're in a different category because you had gotten SuperCID in the past I assume. That's the main determining factor in whether you can unlock the bootloader. You should be fine as long as you still have SuperCID.
Code:
fastboot oem readcid
Sent from my Evita
Click to expand...
Click to collapse
Yes it says me CID is 11111111. Why would supersu be acting so funny and constantly telling me to update the binaries...supersu seems relatively useless at this point. do i need supersu to flash a custom ROM?
Forever95 said:
Well that sucks because even when i was on 4.1.1 i could not root my stupid phone. There was no easy way to do it on 4.1.1 3.18, and now i cant do crap with this 4.2.2 on 5.18. why would i not be able to root it if other people can root their phones that are on 4.3 and higher like the Htc One.
Click to expand...
Click to collapse
Lack of research. A working root method exists for 3.18, both a "manual" method and two "Toolkits" for those that can't handle the manual method.
Also, you should never never never install an OTA update unless you know what has been patched, changed, etc. Updates frequently will patch existing root exploits, and therefore leaving you in the spot you find yourself in.
Other devices (such as the One) can be rooted with later firmware, simply because that device has more developer interest. It requires the right talented developer(s) putting in the time and effort to find the exploit method. Its still possible on this device with 5.18. All it takes is the right guy and the proper amount of motivation. But as the device is getting older, and devs are moving to other phones, those chances do get more unlikely.
UPDATE!
timmaaa said:
You're in a different category because you had gotten SuperCID in the past I assume. That's the main determining factor in whether you can unlock the bootloader. You should be fine as long as you still have SuperCID.
Code:
fastboot oem readcid
Sent from my Evita
Click to expand...
Click to collapse
Thank you so much for the help. i know officially have an s-off device that is unlocked and rooted ready to run custom ROMS.
My next question would be how do i flash a kernel and why would i flash a kernel?
cant flash ROM
Please help,
SO i downloaded the CM10.2.1ROM for the evita along with the gapps package provided. after putting them onto my phone i went into twrp and tried flashing them it starts to flash but then comes up with an error
E:Error executing updater binary in zip '/sdcard/cm10.2.1/pa-gapps-full-
Error flashing zip '/sdcard/cm10.2.1/pa-gapps-full-4.3-20131102-signed.zip
updating partition details...
thast what my screen reads after trying to flash the zip. What can i do?
brenntard said:
Please help,
SO i downloaded the CM10.2.1ROM for the evita along with the gapps package provided. after putting them onto my phone i went into twrp and tried flashing them it starts to flash but then comes up with an error
E:Error executing updater binary in zip '/sdcard/cm10.2.1/pa-gapps-full-
Error flashing zip '/sdcard/cm10.2.1/pa-gapps-full-4.3-20131102-signed.zip
updating partition details...
thast what my screen reads after trying to flash the zip. What can i do?
Click to expand...
Click to collapse
It's most likely because your hboot is too new (2.18) and hasn't been included as a compatible hboot in the installer script. You can flash the 2.15 firmware from Turge's stock Sense 5 ROM thread to overcome this problem. But first you'l need s-ff to do that. So I'd suggest installing the Kickdroid ROM, then you can get s-off, then you can flash the firmware, then you can flash that ROM.
timmaaa said:
It's most likely because your hboot is too new (2.18) and hasn't been included as a compatible hboot in the installer script. You can flash the 2.15 firmware from Turge's stock Sense 5 ROM thread to overcome this problem. But first you'l need s-ff to do that. So I'd suggest installing the Kickdroid ROM, then you can get s-off, then you can flash the firmware, then you can flash that ROM.
Click to expand...
Click to collapse
That sounds easy enough.. I was able to gain s-off through the face palm method earlier today so now i just need to flash the 2.15 firmware. in the thread it says to "make sure you flash your current ROM's boot.img after" is this necessary if i am using the stock 4.2.2 sense 5 ROM already, does the download include the radio? do i need a different radio?
The firmware is taken from the update that included that stock ROM so you might not have to flash the boot.img afterwards, if your phone doesn't boot thought that's why. The firmware package does include the radio, and it isn't suggested your change the radio because that'll cause a mismatch resulting in signal loss and reboots.
Sent from my Evita
timmaaa said:
The firmware is taken from the update that included that stock ROM so you might not have to flash the boot.img afterwards, if your phone doesn't boot thought that's why. The firmware package does include the radio, and it isn't suggested your change the radio because that'll cause a mismatch resulting in signal loss and reboots.
Sent from my Evita
Click to expand...
Click to collapse
awesome! im gonna try that tonight.
Download the file from the thread and follow the instructions precisely. It isn't flashed through recovery like a ROM would be, it's flashed in rebootRUU mode using fastboot.
Sent from my Evita
timmaaa said:
Download the file from the thread and follow the instructions precisely. It isn't flashed through recovery like a ROM would be, it's flashed in rebootRUU mode using fastboot.
Sent from my Evita
Click to expand...
Click to collapse
Thank you so much for your help! i succesfully flashed the firmware and amnow running CM10.2.1. If i want to flash a 4.4 ROM do i need a different recovery? im currently using 2.5.0.0
Yes you do need a different recovery to flash KitKat ROMs, it's the unofficial modified TWRP 2.6.3.0 from our Original Android Development section that you want. Even if you don't want to flash a KitKat ROM you need to change your recovery, the one you're currently running is very buggy and will cause major issues when flashing anything.
Download either the modified version of TWRP 2.6.3.0 (for KitKat ROMs) from here, or TWRP 2.6 (for any other ROM) from here.
Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Sent from my Evita
timmaaa said:
Yes you do need a different recovery to flash KitKat ROMs, it's the unofficial modified TWRP 2.6.3.0 from our Original Android Development section that you want. Even if you don't want to flash a KitKat ROM you need to change your recovery, the one you're currently running is very buggy and will cause major issues when flashing anything.
Download either the modified version of TWRP 2.6.3.0 (for KitKat ROMs) from here, or TWRP 2.6 (for any other ROM) from here.
Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Sent from my Evita
Click to expand...
Click to collapse
I guess the all in one toolkit hasn't had an update in a while...
thanks again for all the help, really appreciated
i have been working to get a custom rom on my device for roughly a month now and today was the day it finally happened
glad to say i learned a lot thanks to help from people like you in this great forum