I used unrevoked forever and rooted 2.2
I have the .93 bootloader.
Can someone tell me how to mount nand and make it writeable with the ADB shell commands?
Or other advice?
i tried using the .76 bootloader then nand restore, but it won't restore 2.2. It gets stuck on the boot restore. It will restore everything else though. But then i get boot loops.
So I need to unlock nand with ADb commands.
sure, could you be a little bit more specific about how you were able to root with unrevoked forever though? If S-OFF you should just be able to use a modified PC3600.img
More details please!
kthejoker20 said:
I used unrevoked forever and rooted 2.2
I have the .93 bootloader.
Can someone tell me how to mount nand and make it writeable with the ADB shell commands?
Or other advice?
i tried using the .76 bootloader then nand restore, but it won't restore 2.2. It gets stuck on the boot restore. It will restore everything else though. But then i get boot loops.
So I need to unlock nand with ADb commands.
Click to expand...
Click to collapse
I just caught a Rainbow!
somehow, i just dont believe you. sorry
Wish I was a mod so I could delete these BS posts about people rooting 2.2 with methods that hundreds of people have already tried! Get a life! Nothing better to do than post bogus success stories!
i rooted 2.2 with a commodore 64 and unlocked my NAND with a paperclip and duct tape.
I was able to root it, because I had the eng boot before.
But after the upgrade, everything reverted back.
But I still have S-off.
So don't get your hopes up people, I was asking a question, not gloating.
Chuckle
t3project said:
i rooted 2.2 with a commodore 64 and unlocked my NAND with a paperclip and duct tape.
Click to expand...
Click to collapse
LMAO! Thanks for the chuckle...
feedDunk said:
LMAO! Thanks for the chuckle...
Click to expand...
Click to collapse
The funny thing is that would actually probably work.
Short out one of the leads with the paperclip and tape it in place, nand unlocked.
You cant root the stock build when you don't have everything stock on your phone. You are not eligible to try and root it considering you already have an unlocked hboot. If you used Unrevoked Forever on your previously rooted 2.1 EVO, s-off stays even when you RUU, and you could just flash anything from hboot. That's not an option for people who don't have an unlocked bootloader, aka everyone who bought the phone w/ 2.2 already.
EDIT: I must have missed your last post that you said you already had the eng bootloader and you said not to get your hopes up lol
regaw_leinad said:
You cant root the stock build when you don't have everything stock on your phone. You are not eligible to try and root it considering you already have an unlocked hboot. If you used Unrevoked Forever on your previously rooted 2.1 EVO, s-off stays even when you RUU, and you could just flash anything from hboot. That's not an option for people who don't have an unlocked bootloader, aka everyone who bought the phone w/ 2.2 already.
EDIT: I must have missed your last post that you said you already had the eng bootloader and you said not to get your hopes up lol
Click to expand...
Click to collapse
I am trying to tinker with nand. Seeing as I am one of the lucky ones.
kthejoker20 said:
I am trying to tinker with nand. Seeing as I am one of the lucky ones.
Click to expand...
Click to collapse
Your nand is unlocked though... Your hboot says s-off... right? Those are the same thing. I'm not trying to stop you from tinkering, I'm just saying that yours is already unlocked lol
regaw_leinad said:
Your nand is unlocked though... Your hboot says s-off... right? Those are the same thing. I'm not trying to stop you from tinkering, I'm just saying that yours is already unlocked lol
Click to expand...
Click to collapse
I think it is unlocked, i just think it is a matter of setting permissions now so /data is writable.
CHMOD 755 ? /mount
This really sux all i want is root man im tired of people gloating about their root
kthejoker20 said:
I think it is unlocked, i just think it is a matter of setting permissions now so /data is writable.
CHMOD 755 ? /mount
Click to expand...
Click to collapse
What exactly are you trying to do? You already have nand unlocked, are you trying to figure out a method that will work for everyone who just got their phone w/ stock 2.2 on it? What do you need to write to data?
regaw_leinad said:
What exactly are you trying to do? You already have nand unlocked, are you trying to figure out a method that will work for everyone who just got their phone w/ stock 2.2 on it? What do you need to write to data?
Click to expand...
Click to collapse
im not sure he quite knows what he's trying to do. but he most definitely doesnt qualify as rooting 2.2.
kthejoker20 said:
I was able to root it, because I had the eng boot before.
But after the upgrade, everything reverted back.
But I still have S-off.
So don't get your hopes up people, I was asking a question, not gloating.
Click to expand...
Click to collapse
why do you have a donate button?
kthejoker20 said:
The funny thing is that would actually probably work.
Short out one of the leads with the paperclip and tape it in place, nand unlocked.
Click to expand...
Click to collapse
i made my own breadboard that will unlock nand on any phone...
t3project said:
but he most definitely doesnt qualify as rooting 2.2.
Click to expand...
Click to collapse
Yeah, of course not.
Related
i have installed the gingerbread keyboard file on my sd card and have rooted my phone using the visonary method but now i cant seem to get into recovery mode. I have rom manager installed and have flashed clockwork recovery mode. it said that it had sucsessfully installed.
I then flashed it again as i read somewhere that i might need to do it twice as sometimes it dosent work.
when i now click on the recovery option in rom manager all i get is the red triange with the ! in the middle.
any ideas what im doing wrong?
Have tried reading the threads but with 30 plus pages i am now completley confused
Sounds like you don't have S-OFF. What does it say in HBOOT (e.g. hold down volume down and the power button with the phone powered off) ?
steviewevie said:
Sounds like you don't have S-OFF. What does it say in HBOOT (e.g. hold down volume down and the power button with the phone powered off) ?
Click to expand...
Click to collapse
thanks for the quick reply, i think from what i have read that this s-off thing maybe the problem.
can you tell me how do this please
simple steps please as i am struggling with this
just done the hboot hing and at the top of screen it says
vision pvt ship s-on
hpsauce37 said:
thanks for the quick reply, i think from what i have read that this s-off thing maybe the problem.
can you tell me how do this please
simple steps please as i am struggling with this
Click to expand...
Click to collapse
It's a bit confusing because there is more than one way to do this. But by far the safest way is to follow the guide at http://forum.xda-developers.com/showthread.php?t=857390
Have a good read, then if you're not sure, ask questions in that thread on the process.
steviewevie said:
Sounds like you don't have S-OFF. What does it say in HBOOT (e.g. hold down volume down and the power button with the phone powered off) ?
Click to expand...
Click to collapse
S-OFF is a completely different animal. Don't get it confused with being able to boot into recovery.
Sent from my EVO using Tapatalk Pro
rwcj63 said:
S-OFF is a completely different animal. Don't get it confused with being able to boot into recovery.
Click to expand...
Click to collapse
I didn't think you could flash recovery without S-OFF though ? Surely ROM Manager doesn't have the ability to write to the NAND, since the write protection will be on if you're at S-ON ?
steviewevie said:
I didn't think you could flash recovery without S-OFF though ? Surely ROM Manager doesn't have the ability to write to the NAND, since the write protection will be on if you're at S-ON ?
Click to expand...
Click to collapse
Again. S-OFF is a different issue altogether. Being able to write to NAND is a part of the rooting process. Setting security off is not a part of the rooting process. It's a totally different process for a totally different purpose. The caveat would be if unrevoked has been revised to full root and set S-OFF during the same process. I haven't used it in awhile so on that point, I'm not certain.
Sent from my EVO using Tapatalk Pro
rwcj63 said:
Again. S-OFF is a different issue altogether. Being able to write to NAND is a part of the rooting process. Setting security off is not a part of the rooting process. It's a totally different process for a totally different purpose. The caveat would be if unrevoked has been revised to full root and set S-OFF during the same process. I haven't used it in awhile so on that point, I'm not certain.
Click to expand...
Click to collapse
Sorry but that's not right for the DZ/G2. I wonder if you're thinking of how it works on a different Android phone ? The security has been increased on the DZ/G2/DHD compared to, say, the original Desire.
Writing to the system and recovery partitions isn't possible until you get S-OFF. This has nothing to do with rooting, it it because of the increased security on these phones where the NAND is in a hardware write-protect mode for those partitions by default. You can appear to write to the partitions, but it's actually going to cache and is lost when you reboot, until you get S-OFF.
steviewevie said:
Sorry but that's not right for the DZ/G2. I wonder if you're thinking of how it works on a different Android phone ? The security has been increased on the DZ/G2/DHD compared to, say, the original Desire.
Writing to the system and recovery partitions isn't possible until you get S-OFF. This has nothing to do with rooting, it it because of the increased security on these phones where the NAND is in a hardware write-protect mode for those partitions by default. You can appear to write to the partitions, but it's actually going to cache and is lost when you reboot, until you get S-OFF.
Click to expand...
Click to collapse
Actually yes. S-OFF on the EVO is to make sure no matter what, you're always rooted. It came about after the new stock flash would unroot the phone. With S-OFF active, you can flash any stock rom and not lose root. All you would need to do is reflash RA or Clockwork to get back to recovery and flash roms again. Unrevoked forever is the program we used to change the security setting.
So. That is only true for the EVO?
Sent from my EVO using Tapatalk Pro
rwcj63 said:
Actually yes. S-OFF on the EVO is to make sure no matter what, you're always rooted. It came about after the new stock flash would unroot the phone. With S-OFF active, you can flash any stock rom and not lose root. All you would need to do is reflash RA or Clockwork to get back to recovery and flash roms again. Unrevoked forever is the program we used to change the security setting.
So. That is only true for the EVO?
Sent from my EVO using Tapatalk Pro
Click to expand...
Click to collapse
yeah I think so.
The new HTC Desire Z and HD had "better" security from htc, basically you can't write anything to nand (/system) until you perma rooted, even then some things such as recovery needed s-off before we could write to that partition.
im going to have to give up on this
i have tried to follow the guide to get s-off but i find it too complicated. I have my phone rooted with visionary but i think thats as far as im going to get.
tried to install the adb thing and get that working but it never recognises the phone. when i remove the drivers and plug it back in then windows automatically installs the drivers again so i never have the option to manually instll them.
this is just becoming a nightmare
someone make it simple for me please....the thread is pages and pages long and even then it seems there are problems
hpsauce37 said:
im going to have to give up on this
i have tried to follow the guide to get s-off but i find it too complicated. I have my phone rooted with visionary but i think thats as far as im going to get.
tried to install the adb thing and get that working but it never recognises the phone. when i remove the drivers and plug it back in then windows automatically installs the drivers again so i never have the option to manually instll them.
this is just becoming a nightmare
someone make it simple for me please....the thread is pages and pages long and even then it seems there are problems
Click to expand...
Click to collapse
Have you tried my guide on adb ? http://forum.xda-developers.com/showthread.php?t=865685
OK, I can use some help too
I have a DZ with stock ROM, root and s-off and CWR.
In my enthusiasm that I knew how to flash rom updates with clockwork (I am running the Godspeed 1Ghz) I downloaded the Gingerbread keyboard rom update from the G2 forum. I think I jumped off a bit too fast...
And now I am stuck in an infinite boot loop. I can get into Clockwork recovery but it just loops the "HTC Quietly Brilliant" forever including the annoying boot sound...
I tried some suggestions to download and reflash a second time, no effect.
I tried to mount /system before flashing, no effect.
Am I forced to go back to factory now?
Also, I found 2 gingerbread keyboards, one in the G2 forum and one over here.
Anyone know what the difference is? They have a different filesize..
Any help is welcome...
*edit*
OK so now I read that it is only to be flashed on a non-stock ROM... so I am now flashing Cyanogen 6.1
try wiping all the caches...
Lennyuk said:
yeah I think so.
The new HTC Desire Z and HD had "better" security from htc, basically you can't write anything to nand (/system) until you perma rooted, even then some things such as recovery needed s-off before we could write to that partition.
Click to expand...
Click to collapse
Wow. I'm really sorry guys. I never knew that's how non evo worked. That totally sucks.
Sent from my EVO using Tapatalk Pro
rwcj63 said:
Wow. I'm really sorry guys. I never knew that's how non evo worked. That totally sucks.
Click to expand...
Click to collapse
S'alright.
HTC really ramped up the security on these new phones, as Lenny said, with this hardware write-protection on certain partitions. But even given that, I was amazed by just how quickly the guys on the #G2ROOT IRC channel, especially Scotty2, managed to crack it !
It also looks like they've opened the phone even wider than many others before, with the "true" radio S-OFF that they achieved.
You can read up all about it in the Wiki - http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision
Here's my question. My friend's brother attempted to root his stock Evo using simpleroot instructions I sent my friend 4-5 months ago (pre-2.2) without knowing that simpleroot isn't supported. His phone is now borked. When he tries to load into bootloader, he gets an error (not sure which one), but his phone will boot into android.
What I'm wondering is this: As of yesterday, his phone was updated and current as per sprint and the update commands in the system menus... Can he flash back to an older stock rom via RUU (such as this one) without causing other problems? If my understanding is correct, the latest sprint updates aren't yet rootable, right?
Any help on this issue?
Thanks
Is the phone s-off?
Sent from my PC36100 using XDA App
badutahboy said:
Here's my question. My friend's brother attempted to root his stock Evo using simpleroot instructions I sent my friend 4-5 months ago (pre-2.2) without knowing that simpleroot isn't supported. His phone is now borked. When he tries to load into bootloader, he gets an error (not sure which one), but his phone will boot into android.
What I'm wondering is this: As of yesterday, his phone was updated and current as per sprint and the update commands in the system menus... Can he flash back to an older stock rom via RUU (such as this one) without causing other problems? If my understanding is correct, the latest sprint updates aren't yet rootable, right?
Any help on this issue?
Thanks
Click to expand...
Click to collapse
No, you can not run an older ruu. If he updated to today or yesterdays update hes stuck. If he is on HBOOT 2.02 he can flash the 3.30.651.3 ruu or ths 3.70.651.1 but you can not ruu further back.
animal7296 said:
No, you can not run an older ruu. If he updated to today or yesterdays update hes stuck. If he is on HBOOT 2.02 he can flash the 3.30.651.3 ruu or ths 3.70.651.1 but you can not ruu further back.
Click to expand...
Click to collapse
Are either of these rootable yet?
and can someone explain what S-on and off means?
badutahboy said:
Are either of these rootable yet?
and can someone explain what S-on and off means?
Click to expand...
Click to collapse
Yes, they're both rootable.
S-ON vs S-OFF; is just basically a security parameter that's being locked/unlocked. This allows for PC36IMG's files to be flashed via the bootloader without having to use or have authenticated signature keys from Google.
Basically, if you ever accept an OTA and it flashes and removes your recovery (CWM or Amon_RA); then you have no way of flashing custom roms/mods, etc... however with S-OFF, you have the ability to get your recovery back and set yourself back to root if need be.
Essentially, S-OFF allows for another method of flashing stuff to the phone besides just using the CWM or Amon_RA recoveries.
Hboot versions however can affect S-OFF; so it's important that if there is a new OTA that you always hold off, until a developer can validate that the hboot can be exploited and that the OTA can be rooted.
badutahboy said:
Are either of these rootable yet?
and can someone explain what S-on and off means?
Click to expand...
Click to collapse
1. 2.02 is rootable 2.10 is not and is the newest one.
2.0 S-ON means you can not flash roms s-off means you can. It is the security of the phone kind of.
If you can not get into bootloader then you can try running the oldest ruu and then the next. It wont hurt the phone at all (I just did it today) it will just give you an error and reboot the phone.
pseudoremora said:
Yes, they're both rootable.
S-ON vs S-OFF; is just basically a security parameter that's being locked/unlocked. This allows for PC36IMG's files to be flashed via the bootloader without having to use or have authenticated signature keys from Google.
Basically, if you ever accept an OTA and it flashes and removes your recovery (CWM or Amon_RA); then you have no way of flashing custom roms/mods, etc... however with S-OFF, you have the ability to get your recovery back and set yourself back to root if need be.
Essentially, S-OFF allows for another method of flashing stuff to the phone besides just using the CWM or Amon_RA recoveries.
Hboot versions however can affect S-OFF; so it's important that if there is a new OTA that you always hold off, until a developer can validate that the hboot can be exploited and that the OTA can be rooted.
Click to expand...
Click to collapse
Thanks for the explanations and the help.
How do I find out if it's S-on or off, and is it possible to change?
pseudoremora said:
Yes, they're both rootable.
S-ON vs S-OFF; is just basically a security parameter that's being locked/unlocked. This allows for PC36IMG's files to be flashed via the bootloader without having to use or have authenticated signature keys from Google.
Basically, if you ever accept an OTA and it flashes and removes your recovery (CWM or Amon_RA); then you have no way of flashing custom roms/mods, etc... however with S-OFF, you have the ability to get your recovery back and set yourself back to root if need be.
Essentially, S-OFF allows for another method of flashing stuff to the phone besides just using the CWM or Amon_RA recoveries.
Hboot versions however can affect S-OFF; so it's important that if there is a new OTA that you always hold off, until a developer can validate that the hboot can be exploited and that the OTA can be rooted.
Click to expand...
Click to collapse
I have been trying to root 2.10 since yesterday and it has proven to not be possible as of yet. If you have a rooting method that works for me then would you share please?
animal7296 said:
I have been trying to root 2.10 since yesterday and it has proven to not be possible as of yet. If you have a rooting method that works for me then would you share please?
Click to expand...
Click to collapse
Im with u brotha im stuck on 2.10 from a mistake i made. Was originally on 0.76.2
Sux man
Sent from my PC36100 using Tapatalk
badutahboy said:
Thanks for the explanations and the help.
How do I find out if it's S-on or off, and is it possible to change?
Click to expand...
Click to collapse
To see if you're S-OFF or S-ON; you can boot your phone into bootloader mode.
To do this:
1. Power down the phone
2. Hold the Volume Down + Power button
3. You'll see a white screen with three little Androids
4. Read the very top of the screen; should tell you if you are S-ON or S-OFF.
You can reboot afterwards.
And yes, you can switch from the S-ON to S-OFF and vise versa, though I don't see why you would want to do the latter.
animal7296 said:
I have been trying to root 2.10 since yesterday and it has proven to not be possible as of yet. If you have a rooting method that works for me then would you share please?
Click to expand...
Click to collapse
luckylui said:
Im with u brotha im stuck on 2.10 from a mistake i made. Was originally on 0.76.2
Sux man
Click to expand...
Click to collapse
I apologize to the both of you guys; I was under the impression that 2.10 was S-OFF, apparently testing is still being done. For now, looks like you'll have to sit tight. Sorry guys.
pseudoremora said:
To see if you're S-OFF or S-ON; you can boot your phone into bootloader mode.
To do this:
1. Power down the phone
2. Hold the Volume Down + Power button
3. You'll see a white screen with three little Androids
4. Read the very top of the screen; should tell you if you are S-ON or S-OFF.
You can reboot afterwards.
And yes, you can switch from the S-ON to S-OFF and vise versa, though I don't see why you would want to do the latter.
I apologize to the both of you guys; I was under the impression that 2.10 was S-OFF, apparently testing is still being done. For now, looks like you'll have to sit tight. Sorry guys.
Click to expand...
Click to collapse
However it has been verified that if you were S-OFF on 2.02 you can install the OTA and you will end up with HBOOT 2.10 with S-OFF.
pseudoremora said:
To see if you're S-OFF or S-ON; you can boot your phone into bootloader mode.
To do this:
1. Power down the phone
2. Hold the Volume Down + Power button
3. You'll see a white screen with three little Androids
4. Read the very top of the screen; should tell you if you are S-ON or S-OFF.
You can reboot afterwards.
And yes, you can switch from the S-ON to S-OFF and vise versa, though I don't see why you would want to do the latter.
I apologize to the both of you guys; I was under the impression that 2.10 was S-OFF, apparently testing is still being done. For now, looks like you'll have to sit tight. Sorry guys.
Click to expand...
Click to collapse
No prob pimp
Ima call sprint n see if i can some how get me a phone w the 2.02 hboot and just pretty much get an upgrade from 0003 hardware to 0004 Lol
Im like jumpy rite now ahaha
Sent from my PC36100 using Tapatalk
tpbklake said:
However it has been verified that if you were S-OFF on 2.02 you can install the OTA and you will end up with HBOOT 2.10 with S-OFF.
Click to expand...
Click to collapse
True this, but when i did it i was at 0.76.2 and now screw at 2.10 cause it updated all the way n i didnt want to do that.. Got lost in the tangle haha
Sent from my PC36100 using Tapatalk
tpbklake said:
However it has been verified that if you were S-OFF on 2.02 you can install the OTA and you will end up with HBOOT 2.10 with S-OFF.
Click to expand...
Click to collapse
Yea, I heard about this in the IRC; too bad these guys can do that... unfortunate; but I'm sure the Unrevoked team will have a fix soon enough.
luckylui said:
No prob pimp
Ima call sprint n see if i can some how get me a phone w the 2.02 hboot and just pretty much get an upgrade from 0003 hardware to 0004 Lol
Im like jumpy rite now ahaha
Click to expand...
Click to collapse
Good luck with Sprint; I don't know how helpful they're going to be, but you never know...
@luckylui and animal7296, check out the 2.02/2.10 rooting thread again, it seems they got something working. Good luck.
badutahboy said:
Here's my question. My friend's brother attempted to root his stock Evo using simpleroot instructions I sent my friend 4-5 months ago (pre-2.2) without knowing that simpleroot isn't supported. His phone is now borked. When he tries to load into bootloader, he gets an error (not sure which one), but his phone will boot into android.
What I'm wondering is this: As of yesterday, his phone was updated and current as per sprint and the update commands in the system menus... Can he flash back to an older stock rom via RUU (such as this one) without causing other problems? If my understanding is correct, the latest sprint updates aren't yet rootable, right?
Any help on this issue?
Thanks
Click to expand...
Click to collapse
There actually is a way to downgrade without rooting, all you need to do is flash the mtd-eng.img file to your misc partition as explained in toast's rooting part 2 thread. After you do that it will let you flash any ruu that is compatible with your phone
Sent from my PC36100 using XDA App
Ok so i know that gingerbread doesnt have root yet, but i installed the mod for the sense launcher it didnt work but my s-on isnt on its off... i dont know if this means anything to anybody ill upload a pictureee. Does this mean we might be closer to root?
i think i uploaded the picture ?
Yup. U r a lucky Guy. Put a copy of amon RA onto the root of ur SD card. Boot onto the bootloader and when it asks if u want to update say yes. U will then be able to flash whatever u like
If you were s-off before, you should still be s-off after. I have two s-off EVOs that I was going to sell, so I restored them to latest OTA (yea I'm a jerk!) but they stayed s-off (lucky for those when I do decide to sell).
I don't get the point of this, unless you had an S-ON phone and somehow got it S-OFF after the 2.16 hboot and 2.3.3 android upgrade.
YES! thats the thing! I unrooted, got the gingerbread update, after installation and what not it said S-ON. now it says s-off and i have no idea what i did, i been doing so much crap to my phone i dotn even remember what i did. I wanted to try the sense launcher from tommytomatoe and it froze my phone and couldnt do nothing. So i pressed power volume down and it now said s-off.
scoot16 said:
YES! thats the thing! I unrooted, got the gingerbread update, after installation and what not it said S-ON. now it says s-off and i have no idea what i did, i been doing so much crap to my phone i dotn even remember what i did. I wanted to try the sense launcher from tommytomatoe and it froze my phone and couldnt do nothing. So i pressed power volume down and it now said s-off.
Click to expand...
Click to collapse
If what you say is true, you might be able to help the rooting effort by pulling some info off your phone that could be valuable to the devs. I would explain the situation to them, and offer whatever info they need from your phone.
They'll probably call shenanigans on you-- I know I would. But maybe-- just maybe, your Evo carries the mutant X gene that we need to crack this puzzle.
Nice man! maybe just maybe your phone is the "root" of all hahahahaha
BigMatza said:
If what you say is true, you might be able to help the rooting effort by pulling some info off your phone that could be valuable to the devs. I would explain the situation to them, and offer whatever info they need from your phone.
Click to expand...
Click to collapse
This!
10char
scoot16 said:
Ok so i know that gingerbread doesnt have root yet, but i installed the mod for the sense launcher it didnt work but my s-on isnt on its off... i dont know if this means anything to anybody ill upload a pictureee. Does this mean we might be closer to root?
Click to expand...
Click to collapse
Did you have root before at all? Did you use Unrevoked3 to root before? If you did, how did you unroot?
Yes i used unrevoke 3 to root but i installed a stock froyo ruu unrooted because after i tried to unroot with unrevoked it didnt work. After i installed the froyo ruu it said S-ON, i then went on to install gingerbread, went back to check the hboot to see if everything was right and it still said S-ON, then i went thru every process to root my phone just to see if i could try soemthing but failed of course. I then wanted to try tommytomatoe sense launcher for unrooted and after my phone froze alot i went to clear data by pressing power and volume down. That is when i saw it was S-OFF. do you want to know anythingg else?
Please unroot again and post pics , you are still trying to unroot are you not. Go go.
Im cant unroot, im not even rooted, im running stock gingerbread ota 4.24.651.1
Did you flash the s-on tool when you unrooted?
complex88 said:
Did you flash the s-on tool when you unrooted?
Click to expand...
Click to collapse
Yes sir. I did all that was needed to unroot my phone.
Don't think running a ruu will turn s-on. Once you are s-off, you are s-off until you run the s-on tool. Correct me if I am wrong.
Swyped from my Supersonic
i am so tempted to try this....
can you provide the link to this tommytomato mod , at this point, i dont care if i brick my evo ill just go harass sprint and get a refurb or something if i do
LCL22 said:
i am so tempted to try this....
can you provide the link to this tommytomato mod , at this point, i dont care if i brick my evo ill just go harass sprint and get a refurb or something if i do
Click to expand...
Click to collapse
This didnt do nothing it was because of the mess up on my end did i go and find the s-on.
You need to write down everything you did and the order you did it. Also please provide the links that you used.
Also, was it the 4.22 or the 4.24 that you updated to?
*Edit* Nevermind I just saw your earlier post
scoot16 said:
Yes i used unrevoke 3 to root but i installed a stock froyo ruu unrooted because after i tried to unroot with unrevoked it didnt work. After i installed the froyo ruu it said S-ON, i then went on to install gingerbread, went back to check the hboot to see if everything was right and it still said S-ON, then i went thru every process to root my phone just to see if i could try soemthing but failed of course. I then wanted to try tommytomatoe sense launcher for unrooted and after my phone froze alot i went to clear data by pressing power and volume down. That is when i saw it was S-OFF. do you want to know anythingg else?
Click to expand...
Click to collapse
I say somehow some way when u attempted to re-root it went thru cuz that's the only logical way s-off could've been attained. Clearing ur data won't and u were s-on before u took the OTA update so it wasn't present before hand. Have you tried flashing another rom from recovery just to see if it works? You my friend maybe the "MVD" lol!!!
So, did I screw up? I reflashed to stock 2.2 in order to fix a few issues. I got the OTA message to update and I did, so now I'm on 2.3.4 with no way to re-root because I can't turn s-off. Would it be safe to use the unrevoked s-off forever tool or should I go with the gingerbreak.apk method. I feel like an idiot for updating, so take it easy on me... LOL! Thanks in advance.
I used this guide to get my Incredible rooted.
http://forum.xda-developers.com/showthread.php?t=1306400
My first time ever rooting an andriod device. May work for you, may not. You didn't say which device you have. I ended up using the zergrush method to get mine rooted with s-off. Not sure I needed to use that method since I had screwed up and made myself think I had to try it that way.
Rooted DINC ADR6300 with CyanogenMod 7.2 S-OFF
Thanks, but it didn't work for me. Not sure if it's because I'm a Mac user or what, but it was definitely a no go. I don't want to be stuck un-rooted forever! LOL!
gotbst05 said:
Thanks, but it didn't work for me. Not sure if it's because I'm a Mac user or what, but it was definitely a no go. I don't want to be stuck un-rooted forever! LOL!
Click to expand...
Click to collapse
The method in the link above is the only way to root an incredible on android 2.3.4 that is s-on. Your best bet would be to find a friend with a pc and try it again.
cmlusco said:
The method in the link above is the only way to root an incredible on android 2.3.4 that is s-on. Your best bet would be to find a friend with a pc and try it again.
Click to expand...
Click to collapse
I'll give it a shot and see what happens. Thanks.
I've been trying for two days by doing the method mentioned and no luck. I am following it exactly, but I keep getting an error message stating that my firmware is too new.
BuffaloChips said:
I used this guide to get my Incredible rooted.
http://forum.xda-developers.com/showthread.php?t=1306400
My first time ever rooting an andriod device. May work for you, may not. You didn't say which device you have. I ended up using the zergrush method to get mine rooted with s-off. Not sure I needed to use that method since I had screwed up and made myself think I had to try it that way.
Rooted DINC ADR6300 with CyanogenMod 7.2 S-OFF
Click to expand...
Click to collapse
I also was successful in rooting my Inc using the older version of Unrevoked in this thread (version 3.22 I believe). I stopped before doing the full downgrade and S-OFF... I haven't decided if that is worth the hassle or not.
Previously rooted, here you go
http://www.youtube.com/watch?v=Y-wjmYmSeSQ
works on mac and pc, but only if your s-off
korydak1lla said:
http://www.youtube.com/watch?v=Y-wjmYmSeSQ
works on mac and pc, but only if your s-off
Click to expand...
Click to collapse
Kind of a pointless video. Of course you can root 2.3.4 if your already s-off. That is the whole point of being s-off, so if newer firmware comes out that isnt supported by unrevoked or other rooting programs, you can still easily get root by flashing a custom recovery thru hboot and the su binary thru recovery, and your fully rooted again.
So a friend just gave me his old incredible because he got a razor maxx. He never rooted it or anything. So it has the latest OTA and such on it. I'm trying to unlock the bootloader right now b. hTCs ruu keeps failing. What should I do?
platinumrims said:
So a friend just gave me his old incredible because he got a razor maxx. He never rooted it or anything. So it has the latest OTA and such on it. I'm trying to unlock the bootloader right now b. hTCs ruu keeps failing. What should I do?
Click to expand...
Click to collapse
Do you have the correct drivers installed on the pc? They are installed with htc sync. Or did the ruu give a soecific error.
I thought I had the drivers but I don't actually have sync installed. Should I do that? It gives me an unknown error and just stops.
platinumrims said:
I thought I had the drivers but I don't actually have sync installed. Should I do that? It gives me an unknown error and just stops.
Click to expand...
Click to collapse
Yes install htc sync and that will install the drivers you need. Hopefully it will work then. What hboot version are you on now?
1.07.0000
Edit- after doing the ruu its 1.02 now
platinumrims said:
1.07.0000
Edit- after doing the ruu its 1.02 now
Click to expand...
Click to collapse
Oh if you were on 1.07 you could have just skipped the ruu part of the htcdev instructions, as 1.07 is already able to be unlocked. However 1.02 is unlockable too.
ah, we now i'm unlocked... i've downloaded all this ****, recovery and unrevoked and oneclick cuz it worked on my desire... what works best? I think i S-OFF with unrevoked if i remember correctly. and root with one click if it works.
i have the Rezound, so i haven't used this stuff in quite some time
platinumrims said:
ah, we now i'm unlocked... i've downloaded all this ****, recovery and unrevoked and oneclick cuz it worked on my desire... what works best? I think i S-OFF with unrevoked if i remember correctly. and root with one click if it works.
i have the Rezound, so i haven't used this stuff in quite some time
Click to expand...
Click to collapse
Follow this guide http://forum.xda-developers.com/showthread.php?t=1506258 ignoring the first couple steps that you have already done. This is the only way to root 2.3.4 with a 1.** hboot.
>.> it's just saying FAILED and such when i push the unlock.bin .... -__-
platinumrims said:
>.> it's just saying FAILED and such when i push the unlock.bin .... -__-
Click to expand...
Click to collapse
Hmm not sure, never had any issues with unlocking. Mabey you didnt get all the characters when copying and pasting to the htcdev site.
i used it to unlock already... then realized i had to flash the froyo ruu, which i did
and that's where im at now... i can't re-push the unlock code for some reason...
edit: maybe it's because i deleted HTC sync... err.. lol lemme try that
platinumrims said:
i used it to unlock already... then realized i had to flash the froyo ruu, which i did
and that's where im at now... i can't re-push the unlock code for some reason...
Click to expand...
Click to collapse
So right now your on froyo and still s-on? If so skip that step and move on to using unrevoked to root and get s-off. Being unkocked really isnt needed once your s-off, just needed to get to froyo to get s-off.
so, it doesn't matter if my bootloader is locked? as long as i'm on 1.02 hboot and froyo?
edit: and yes, i'm on froyo, with a locked bootloader, and no root
platinumrims said:
so, it doesn't matter if my bootloader is locked? as long as i'm on 1.02 hboot and froyo?
edit: and yes, i'm on froyo, with a locked bootloader, and no root
Click to expand...
Click to collapse
As long as your on froyo you can use unrevoked to root and get s-off. Getting s-off gives you all the same things as being unlocked plus more. So as long as you get s-off there is no need to be unlocked.
cmlusco said:
As long as your on froyo you can use unrevoked to root and get s-off. Getting s-off gives you all the same things as being unlocked plus more. So as long as you get s-off there is no need to be unlocked.
Click to expand...
Click to collapse
i see, i was under the impression that i had to be unlocked to get unrevoked to work.
cmlusco said:
As long as your on froyo you can use unrevoked to root and get s-off. Getting s-off gives you all the same things as being unlocked plus more. So as long as you get s-off there is no need to be unlocked.
Click to expand...
Click to collapse
Do i need to get back to hboot 1.07 or 1.06? i saw in some CM7 thread where it was recommended that i use .92
can't i just pull the boot.img from my GB rom and update it? or is there a .zip floating around that will do that for me?
platinumrims said:
Do i need to get back to hboot 1.07 or 1.06? i saw in some CM7 thread where it was recommended that i use .92
can't i just pull the boot.img from my GB rom and update it? or is there a .zip floating around that will do that for me?
Click to expand...
Click to collapse
1.02 is fine. It dosent really matter what hboot version your on.
cmlusco said:
1.02 is fine. It dosent really matter what hboot version your on.
Click to expand...
Click to collapse
Lulz I'm on 92 now. Say could you recommend a good rom to basically use this thing as an mp3 player? I'm on CM7pons or something.. Are there any that have anything special in them for music? Thanks a bunch for all your help too and maybe a good combo for battery life too? I am familiar with chads kernels but I think his website is down or something
platinumrims said:
Lulz I'm on 92 now. Say could you recommend a good rom to basically use this thing as an mp3 player? I'm on CM7pons or something.. Are there any that have anything special in them for music? Thanks a bunch for all your help too and maybe a good combo for battery life too? I am familiar with chads kernels but I think his website is down or something
Click to expand...
Click to collapse
I cant recommend one right off hand, but it would probably be best to take a stock rom, and remove the apps you dont need and dissble the radio if your not using it for calls. Chad and tinys kernels are awesome in my opinion, stable and great on battery life with the right settings. The site is working for me http://www.incredikernel.com/?page_id=10
cmlusco said:
I cant recommend one right off hand, but it would probably be best to take a stock rom, and remove the apps you dont need and dissble the radio if your not using it for calls. Chad and tinys kernels are awesome in my opinion, stable and great on battery life with the right settings. The site is working for me http://www.incredikernel.com/?page_id=10
Click to expand...
Click to collapse
His site won't load on anything for me... It just times out. I managed to find a hwa ics lite kernel, would that work on gb?