i downgraded to 2.2.1 from 2.3.4 because htc sense was force closing.
i have tried rooting but to no avail. i do have a bad emic chip.
i now am either going to update back to 2.3.4 and htc dev unlock and get rid of bloatware or i simply try to keep rooting and flash and hope i dont brick my phone.
NEVER EVER EVER unlock with HTC DEV! And try using ./gfree for FroYo, supposing you haven't updated to 2.3.4.
why not use htcdev
i can try gfree but the bad emmc chip apprently bricks your phone or is timebomb
For the EMMc chip: it is not. My brother had a bad chip. He flashed like there was no tomorrow. The only reason why he doesn't have the phone right now is because he traded it for an iPhone...-__-
HTCDev: It makes it harder because then when you flash a ROM, you must manually flash the boot.img to flash the whole ROM. I don't know the details, but that is just what I heard.
invasion2 said:
For the EMMc chip: it is not. My brother had a bad chip. He flashed like there was no tomorrow. The only reason why he doesn't have the phone right now is because he traded it for an iPhone...-__-
HTCDev: It makes it harder because then when you flash a ROM, you must manually flash the boot.img to flash the whole ROM. I don't know the details, but that is just what I heard.
Click to expand...
Click to collapse
The adb part is true, the reasoning though is HTC dev unlock only unlocks part of the bootloader, I'm not sure about the specifics but I know it unlocks the recovery partition which allows you to flash cwm
Sent from my HTC Glacier using xda premium
Nicgraner said:
The adb part is true, the reasoning though is HTC dev unlock only unlocks part of the bootloader, I'm not sure about the specifics but I know it unlocks the recovery partition which allows you to flash cwm
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
HTCDev unlocks the boot partition (and possibly recovery partition too) for fastboot flashing ONLY. It doesn't unlock them for anything else. So even though it lets you install recovery, you can't flash kernels (boot.img) from it - you HAVE to do it from fastboot.
For non-frequent-flashers, that are familiar enough with their PC to set up fastboot environment, this solution might be good enough.
I don't like it, because I prefer to have the ability to do things fully from the phone.
Jack_R1 said:
HTCDev unlocks the boot partition (and possibly recovery partition too) for fastboot flashing ONLY. It doesn't unlock them for anything else. So even though it lets you install recovery, you can't flash kernels (boot.img) from it - you HAVE to do it from fastboot.
For non-frequent-flashers, that are familiar enough with their PC to set up fastboot environment, this solution might be good enough.
I don't like it, because I prefer to have the ability to do things fully from the phone.
Click to expand...
Click to collapse
Jack R1 is absolutely right...I made the mistake of doing it the HTC way, and I have to flash the boot.img with fastboot. But to add to that, I also have been trying to reverse what the HTC method has done, and alot of the methods are not working properly. So plz listen to them and DO NOT unlock via HTC. Its way to easy doing it xda way, something I learned after the fact...
Sent from my Black Ice'd Glacier using Tapatalk
Related
This may be old news, but i followed these directions and got bootloader unlocked... now i just need to figure out s-off
http://forum.xda-developers.com/showthread.php?t=1426179
Nice find...now you should be able to root with Mr root or revolutionary
Revolutionary says I'm not supported.... ;(
Sent from my myTouch_4G_Slide using XDA App
(I will try) and make a script that downgrades your boot loader for compaitability
xmc wildchild22 said:
Nice find...now you should be able to root with Mr root or revolutionary
Click to expand...
Click to collapse
I am going to see if mr. root can help. I haven't tried your tools yet... anything I need to know before i do?
Well mr root is highly based off revolutionary's code, just tweaked to my liking....so I I doubt it will say you compaitable.....however a try won't hurt. ..but if not ill start work on a downgrade tool
Just says my bootloader is not compatable... Downgrading would be great.... I tried flashing a recovery file to backdoor it but came back as " older than current" and stopped...
Sent from my myTouch_4G_Slide using XDA App
are you able to install cwm recovery through fastboot?
nlarge said:
Just says my bootloader is not compatable... Downgrading would be great.... I tried flashing a recovery file to backdoor it but came back as " older than current" and stopped...
Sent from my myTouch_4G_Slide using XDA App
Click to expand...
Click to collapse
not much helpful, but on htc g2 in a similar situation, when root was done, next step was to push some changes to the partition where the Version number was stored. After that downgrading was possible the way you tried, and after that the S-Off tool worked. But as of now, i think there's no information how to cheat the version in the partition which it contains, or even which that partition is. Or maybe someone already knows this?
Then maybe we try a dd if= command on the right partition to overwrite it?
I'm not sure how you got this to work, because nobody else with the OTA has...
However, if you've gotten it to work, you can root just by flashing a superuser image from: http://androidsu.com/superuser/
You won't have S-Off, but I'm not sure of the appeal of S-Off, to be honest. The only thing you can't do with the HTC tool is flash radio files and the like.
I only tried by placing the pdsumthin.zip on SD card and it wouldn't allow it...
Theoretically an unlocked bootloader should allow that... Even if s-on
nlarge said:
I only tried by placing the pdsumthin.zip on SD card and it wouldn't allow it...
Theoretically an unlocked bootloader should allow that... Even if s-on
Click to expand...
Click to collapse
Your bootloader is still locked.
EDIT: in the unlikely event it is unlocked, you'll need to flash a custom recovery before flashing root. There's a guide somewhere on xda that explains all this.
Bootlader even says unlocked at the top... So I am free there...
nlarge said:
Bootlader even says unlocked at the top... So I am free there...
Click to expand...
Click to collapse
You found nothing. We've known about this for a while now and is "officially" (HTC) sanctioned, hence it being THEIR WEBSITE AND INSTRUCTIONS.
Now find yourself a nice recovery image (CWM), boot phone into fastboot mode, "fastboot flash recovery recovery.img".
When this is done (don't ask how, the instructions on doing this are EVERYWHERE, including google's dev site -- you can figure it out yourself with google....), you will have a free and open recovery image, and can use that to write/install the su binary and apk (either with flashable zip or through adb shell, either will work).
There is NO NEED for any kind of downgrade.
Edit: And do change your avatar... this is a hacker site, not a sex dating site. Nobody here is interested in seeing that.
Well... No one has been able to unlock it as of when I posted... It was failing... I will try flashing with fastboot... As long as I can use titanium afterwards, s-off isn't that important
Why is the 4gs community so on edge? No one was ever this rude with 4G or any other HTC forum
nlarge said:
Well... No one has been able to unlock it as of when I posted... It was failing... I will try flashing with fastboot... As long as I can use titanium afterwards, s-off isn't that important
Click to expand...
Click to collapse
I don't believe that's correct. I believe the issue is that the official HTC Bootloader Unlock process will not work -- and here's the key factor -- on devices that have already used the Revolution S-OFF procedure. I'm absolutely certain that people before you (who had not used Revolutionary) have successfully unlocked their bootloader via HTC's walkthrough.
nlarge said:
Why is the 4gs community so on edge? No one was ever this rude with 4G or any other HTC forum
Click to expand...
Click to collapse
Maybe it's because...
You created two threads that have nothing to do with doubleshot development
You didn't even check the General forum to see if there was an active thread about this (there is)
You can't even follow the rooting instructions posted in a thread on this very subject
As dhkr234 points out, all you need to do is flash the recovery zip and then flash the superuser zip. Just please try that. And then change your avatar.
HebrewToYou: I don't believe that's correct. I believe the issue is that the official HTC Bootloader Unlock process will not work -- and here's the key factor -- on devices that have already used the Revolution S-OFF procedure.[
I have been reading that it just kept hanging for everyone even with s-on... that is why I posted that I unlocked... I dont believe flashing recovery will work(yes i know how and tried zip method first).
What is the problem with my avatar? In the year that I have been on the MT4G thread no one has ever once complained about it... why you?
I'm not trying to be rude, I really just want to know why after all this time is it a problem?
ok, unlocked, SU and clockwork recovery all on board.. just stuck at S-on... directories are still read only, and I really would like to be able to use titanium!! but I am closer!!
I had no idea but I was trying to flash leedroid and then I found out shortly after that leedroid is only available for the international version. I flashed the boot.img (and all went well), but then when I reboot I get the HTC logo and nothing more.
This is not good at all. I'm worried that it might have soft bricked it. But, is it just a matter of loaded up fastboot and flashing the correct at&t boot.img?? If so, do I do it in the same way that I flashed the wrong boot.img?? Also does the bootloader have to be re-locked? I assume so. Maybe not.
Thank you!
Shawn
shgadwa said:
I had no idea but I was trying to flash leedroid and then I found out shortly after that leedroid is only available for the international version. I flashed the boot.img (and all went well), but then when I reboot I get the HTC logo and nothing more.
This is not good at all. I'm worried that it might have soft bricked it. But, is it just a matter of loaded up fastboot and flashing the correct at&t boot.img?? If so, do I do it in the same way that I flashed the wrong boot.img?? Also does the bootloader have to be re-locked? I assume so. Maybe not.
Thank you!
Shawn
Click to expand...
Click to collapse
Just flash the correct one like you flashed the wrong one. The boot loader does not and should not be relocked, it should be unlocked.
shgadwa said:
I had no idea but I was trying to flash leedroid and then I found out shortly after that leedroid is only available for the international version. I flashed the boot.img (and all went well), but then when I reboot I get the HTC logo and nothing more.
This is not good at all. I'm worried that it might have soft bricked it. But, is it just a matter of loaded up fastboot and flashing the correct at&t boot.img?? If so, do I do it in the same way that I flashed the wrong boot.img?? Also does the bootloader have to be re-locked? I assume so. Maybe not.
Thank you!
Shawn
Click to expand...
Click to collapse
is all you flashed, the boot.img or did you flash leedroid too? If you flashed leedroid then do the following:
plug it in to USB while it bootloops type adb reboot recovery
from there you can access your nandroid backup assuming you made one.
if you didn't make a backup then yeah you'll have to flash the 1.85 RUU. To do this, relock the bootloader from adb fastboot oem lock
run the RUU unlock the bootloader then install your recovery and push root files via recovery.
Much easier than having to re-root 1.85 with the new exploit etc.
If he can get to recovery then he can try pushing a ROM to the SD and flashing it first instead of flashing the RUU and all that hassle.
mbh87 said:
If he can get to recovery then he can try pushing a ROM to the SD and flashing it first instead of flashing the RUU and all that hassle.
Click to expand...
Click to collapse
I keep forgetting we have adb through recovery now. Good call. But do we have USB?
Latest TWRP is suppose to have both ADB and USB
You should always back up
Sent from my HTC One XL using Tapatalk 2
kkoshko1 said:
You should always back up
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Amen.
nandroid is always my first step when flashing a ROM
I just flashed boot.img. I cannot get to recovery.
Also I've been reading about how to flash a rom via fastboot. At the time I thought that the reason it was not working was because I flashed boot.img fist when I should of flashed leedroid first. Then I found out (much, much to my disappointment) that leedroid was only for international phones (which as we all know, have a different cpu).
Anyways, I've read that you should relock the bootloader before proceeding and now I see clearly that I was wrong in doing so. Why oh why don't I wait for you guy's awesome help...?
Anyways, so now I'm relocked. I just need to flash the correct boot.img (as soon as I find it). But I don't think I can do that while I'm locked. Heh. I would think I could just run the one click superCID tool again but I can't do that because the tool tries to reboot the phone using adb shell and the phone isn't fully powered on. I think will have to do it from fastboot, but I am not sure how.
Thank you guys for your help.
mbh87 said:
Latest TWRP is suppose to have both ADB and USB
Click to expand...
Click to collapse
I didn't see any need in backing up because I assumed all would go well and also I don't have any data on here that I want. Lesson learned well though. I will always back up. Now I've gotta get it working...
shgadwa said:
I just flashed boot.img. I cannot get to recovery.
Also I've been reading about how to flash a rom via fastboot. At the time I thought that the reason it was not working was because I flashed boot.img fist when I should of flashed leedroid first. Then I found out (much, much to my disappointment) that leedroid was only for international phones (which as we all know, have a different cpu).
Anyways, I've read that you should relock the bootloader before proceeding and now I see clearly that I was wrong in doing so. Why oh why don't I wait for you guy's awesome help...?
Anyways, so now I'm relocked. I just need to flash the correct boot.img (as soon as I find it). But I don't think I can do that while I'm locked. Heh. I would think I could just run the one click superCID tool again but I can't do that because the tool tries to reboot the phone using adb shell and the phone isn't fully powered on. I think will have to do it from fastboot, but I am not sure how.
Thank you guys for your help.
Click to expand...
Click to collapse
You should only supercid once, doesn't need to be re done, no matter locked or unlocked. Can you get to fastboot, try to ruu back...I dunno if this helps but that's what I would try
Sent from my HTC One XL using Tapatalk 2
shgadwa said:
I just flashed boot.img. I cannot get to recovery.
Also I've been reading about how to flash a rom via fastboot. At the time I thought that the reason it was not working was because I flashed boot.img fist when I should of flashed leedroid first. Then I found out (much, much to my disappointment) that leedroid was only for international phones (which as we all know, have a different cpu).
Anyways, I've read that you should relock the bootloader before proceeding and now I see clearly that I was wrong in doing so. Why oh why don't I wait for you guy's awesome help...?
Anyways, so now I'm relocked. I just need to flash the correct boot.img (as soon as I find it). But I don't think I can do that while I'm locked. Heh. I would think I could just run the one click superCID tool again but I can't do that because the tool tries to reboot the phone using adb shell and the phone isn't fully powered on. I think will have to do it from fastboot, but I am not sure how.
Thank you guys for your help.
Click to expand...
Click to collapse
Download your previous Unlock_code.bin and flash the unlock token again. Your CID should still be SuperCID, installing Rooms or RUUs don't change the CID.
kkoshko1 said:
You should only supercid once, doesn't need to be re done, no matter locked or unlocked. Can you get to fastboot, try to ruu back...I dunno if this helps but that's what I would try
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Thats actually why I re-locked. I've read that before installing an ruu, you need to re-lock.
I can get to fastboot. I tried to unlock via fastboot but it quickly timesout. I'm currently downloading 1.85 .exe ruu. I will give that a try as soon as its done downloading unless you guys have a better idea.
rohan32 said:
Download your previous Unlock_code.bin and flash the unlock token again. Your CID should still be SuperCID, installing Rooms or RUUs don't change the CID.
Click to expand...
Click to collapse
Thats a great idea! How do I do that via fastboot? I would assume fastboot flash Unlock_code.bin, but that doesn't work. As far as I know you can only flash .img. Or update .zip. What am I doing wrong?
shgadwa said:
Thats a great idea! How do I do that via fastboot? I would assume fastboot flash Unlock_code.bin, but that doesn't work. As far as I know you can only flash .img. Or update .zip. What am I doing wrong?
Click to expand...
Click to collapse
fastboot flash unlocktoken Unlock_code.bin
gunnyman said:
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
Thanks! That worked perfectly. Now I just need to find a AT&T boot.img.
Man, this international version is really throwing me off. I wish it was called something entirely different. It'd make it a lot easier. Its technically not the same phone at all anyway. Must be a marketing thing.
Anyways, I need to find a AT&T boot.img. I could get it from here http://forum.xda-developers.com/showthread.php?t=1689824 but I'm not sure if thats AT&T. It does say 1.82 is AT&T but mentions nothing else of 1.85 and 1.88. I am downloading the ruu for 1.85 but thats taking forever.
If anyone has a working 1.85 AT&T boot.img or knows where I can get one (maybe the link I gave is correct?)... please let me know.
Again, thank you for your help!
shgadwa said:
Thanks! That worked perfectly. Now I just need to find a AT&T boot.img.
Man, this international version is really throwing me off. I wish it was called something entirely different. It'd make it a lot easier. Its technically not the same phone at all anyway. Must be a marketing thing.
Anyways, I need to find a AT&T boot.img. I could get it from here http://forum.xda-developers.com/showthread.php?t=1689824 but I'm not sure if thats AT&T. It does say 1.82 is AT&T but mentions nothing else of 1.85 and 1.88. I am downloading the ruu for 1.85 but thats taking forever.
If anyone has a working 1.85 AT&T boot.img or knows where I can get one (maybe the link I gave is correct?)... please let me know.
Again, thank you for your help!
Click to expand...
Click to collapse
Link is correct. Pay attention to the subforum. It specifically says AT&T One X, if that is the section you are in.
Just flash an att rom no need to flash boot.img seperately anymore it gets flashed in recovery. All you had to do to begin with is use fastboot to flash recovery then flash a new rom in recovery.
To stop the bootloop just hold the power button down til the buttons flash when the screen goes black hold the volume down button and it will boot into hboot. It's a safety feature htc built in because of no battery access, and it works no matter where you are at in the boot process.
You can use sick sense its an att build and flashes the boot.img while flashing the rom.
smokin1337 said:
Just flash an att rom no need to flash boot.img seperately anymore it gets flashed in recovery. All you had to do to begin with is use fastboot to flash recovery then flash a new rom in recovery.
To stop the bootloop just hold the power button down til the buttons flash when the screen goes black hold the volume down button and it will boot into hboot. It's a safety feature htc built in because of no battery access, and it works no matter where you are at in the boot process.
You can use sick sense its an att build and flashes the boot.img while flashing the rom.
Click to expand...
Click to collapse
Thank you. I do know how to get into hboot. I flashed boot.img and it is now working!
NVM saw your edit lol...
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 am finally going to take the plunge and root my sensation what i would like to know is can you essentially clone your phone/apps so you dont have to re-install every app when your done rooting?
Does z4root work on the sensation and would this be the best way to do it?
Thanks peeps
djp76 said:
Hi everyone
I am finally going to take the plunge and root my sensation what i would like to know is can you essentially clone your phone/apps so you dont have to re-install every app when your done rooting?
Does z4root work on the sensation and would this be the best way to do it?
Thanks peeps
Click to expand...
Click to collapse
Once you've unlocked the boot loader and installed a custom recovery such as Clockwork or 4ext, you can do what's called a nandroid backup which basically takes an image of your phone - software, apps, data, the lot - which means that if anything goes wrong you can just restore that and it'll be exactly how it was when you backed it up.
Rooting your phone in itself shouldn't mean that you have to re-install any apps. Rooting just means that you give yourself full access to your phone's system. However, if you decided to install a new ROM, you would then need to replace your apps and one of the most popular and best ways of doing this is with an app called Titanium Backup - there are others, but this is what I use and it's never failed me.
I have no knowledge of z4root. I used a guide on here somewhere to root my phone, via something called Revolutionary.
Hope that helps. :thumbup::thumbup:
MikeDVH said:
Once you've unlocked the boot loader and installed a custom recovery such as Clockwork or 4ext, you can do what's called a nandroid backup which basically takes an image of your phone - software, apps, data, the lot - which means that if anything goes wrong you can just restore that and it'll be exactly how it was when you backed it up.
Rooting your phone in itself shouldn't mean that you have to re-install any apps. Rooting just means that you give yourself full access to your phone's system. However, if you decided to install a new ROM, you would then need to replace your apps and one of the most popular and best ways of doing this is with an app called Titanium Backup - there are others, but this is what I use and it's never failed me.
I have no knowledge of z4root. I used a guide on here somewhere to root my phone, via something called Revolutionary.
Hope that helps. :thumbup::thumbup:
Click to expand...
Click to collapse
I thought that unlocking the boot loader wipe you phone :/
I just want root access, time to look into it
Thanks for the reply :good:
djp76 said:
I thought that unlocking the boot loader wipe you phone :/
I just want root access, time to look into it
Thanks for the reply :good:
Click to expand...
Click to collapse
ok forgive my stupidity does unlocking your boot oader give you root access?
If i use the official htc bootloader unlocker will it be the same as using one of the unlocking progs on here or do different versions have different benifits?
ok so unlocking the bootloader is the same as saying S-Off just different jargon yeah?
djp76 said:
ok so unlocking the bootloader is the same as saying S-Off just different jargon yeah?
Click to expand...
Click to collapse
no, unlocking bootloader doesnt unlock most partition (you cant flash firmware), S-OFF unlocks all partition (its like actually owning the phone)
so should i bother with the htc bootloader unlocker or just go straight to s-off?
djp76 said:
so should i bother with the htc bootloader unlocker or just go straight to s-off?
Click to expand...
Click to collapse
S-off directly. Don't bother unlocking bootloader. Avoid potential headaches
Sent from my HTC Sensation 4G using xda app-developers app
djp76 said:
so should i bother with the htc bootloader unlocker or just go straight to s-off?
Click to expand...
Click to collapse
I'd go straight to S-OFF because with the newer version of JuopunutBear S-OFF you dont need to have htcdev unlock
The JuopunutBear download is here and the guide you need to follow by ganeshp is here
Thankyou both very much,i shall continue my quest tomorrow as its a bit late to start all this now.
Here let me do some explaining for you. when you purchase your device it comes with the security on or what is referred to as S-ON. It also comes with a locked bootloader. Now what that means is that as long as you are S-ON you only have read permissions on the internal storage partitions of the device. The locked bootloader will not let you flash unsigned software to the device and it limits the fastboot and ADB commands you can use with the device. When you S-OFF your device you gain read and write permissions to all the partitions. But even after you S-OFF your device you still have to flash a unlocked bootloader or what is commonly called a eng Hboot to be fully unlocked as you can see by the above explanation.
Now to cover the difference between HTC Dev unlock and S-OFF via JuopunutBear. When you use HTC Dev unlock you gain write permissions to your system partition, recovery partition, and your boot partition. But unlike when you are full S-OFF and you just simply flash the ROM as one package via recovery. After using HTC Dev unlock you have to extract the boot.img and flash it via fastboot commands, or you can install 4EXT recovery and the 4EXT Recovery Updater app then enable Smart Flash to flash the boot.img. Now because you do not gain write permissions to all the partitions you can not flash splash screens, radios, or firmware packages when you use HTC Dev unlock.
Now to talk about root, when you root your device you essentially fully open up the line of communication between the OS and the Linux kernel. It allows the OS to have more access to hardware and to a certain extent software. This allows the user to get the full potential out of the device. Now to root the Sensation you just need to flash Superuser or SuperSU via recovery and then install BusyBox from the Google Play store. Now I had originally plained to go into further details and tell you what both are for but I will not right nowcause my stupid phone erased the original much longer post I had wrote when I went to another tab o my browser.
Go to Recognized Contributor malybru's stickie thread " A great starting point for all new Sensation owners" here in the Sensation General forum for links to everything you need to know.
djp76 said:
Thankyou both very much,i shall continue my quest tomorrow as its a bit late to start all this now.
Click to expand...
Click to collapse
Bugger! my HBOOT 1.27.0000 is not supported by revoloutionary what do i do now?
MikeDVH said:
Once you've unlocked the boot loader and installed a custom recovery such as Clockwork or 4ext, you can do what's called a nandroid backup which basically takes an image of your phone - software, apps, data, the lot - which means that if anything goes wrong you can just restore that and it'll be exactly how it was when you backed it up.
Rooting your phone in itself shouldn't mean that you have to re-install any apps. Rooting just means that you give yourself full access to your phone's system. However, if you decided to install a new ROM, you would then need to replace your apps and one of the most popular and best ways of doing this is with an app called Titanium Backup - there are others, but this is what I use and it's never failed me.
I have no knowledge of z4root. I used a guide on here somewhere to root my phone, via something called Revolutionary.
Hope that helps. :thumbup::thumbup:
Click to expand...
Click to collapse
On your details abouit your phone it states that you s-offed using rev but rev said that hboot 1.27.000 is not supported
Any ideas?
Can anyone please tell me what to do next?
djp76 said:
Can anyone please tell me what to do next?
Click to expand...
Click to collapse
Use soff by juopunutbear or do htc-Dev unlocked lock and flash roms while being SON.. For both there re guides in general section
Sent from my HTC Sensation 4G using xda premium
thanks ganeshp i just found the juopunutbear updated version,looks like im gonna have to htc devunlock first.
djp76 said:
thanks ganeshp i just found the juopunutbear updated version,looks like im gonna have to htc devunlock first.
Click to expand...
Click to collapse
no wait with ganeshp's guide you can achieve S-OFF without htc dev unlock
take a look first
rzr86 said:
no wait with ganeshp's guide you can achieve S-OFF without htc dev unlock
take a look first
Click to expand...
Click to collapse
Ah yes thanks, i shall do that and see what happens
Hello all. I got my One S from a guy that didn't want it anymore. It came rooted and flashed with CM10.1. I've gone into fastboot and it says I'm unlocked, s-off, and on hboot 1.14. My question is if this means that to change ROMs all I do is wipe/clear and flash. Or do I have to flash GUI or boot.img every time. I use to have a LG P509, but this seems to be much more complex than that device's flashing.
Thanks
Sent from my One S using xda app-developers app
kkevin94 said:
Hello all. I got my One S from a guy that didn't want it anymore. It came rooted and flashed with CM10.1. I've gone into fastboot and it says I'm unlocked, s-off, and on hboot 1.14. My question is if this means that to change ROMs all I do is wipe/clear and flash. Or do I have to flash GUI or boot.img every time. I use to have a LG P509, but this seems to be much more complex than that device's flashing.
Thanks
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Yeah all you have to do is wipe and then flash.
S-on means your security is on and HTC semi locks your boot loader so you need to flash the boot.IMG via fastboot or the GUI to bypass htcs stupid bootloader limitations, being as the ville/one s now has s-off (as your phone is) you don't need to flash the boot.IMG after flashing the rom. I hope this helps you understand a little more.
Sent from my One S using xda premium