Related
will there be a simple root for 2.2? i hear unrevoked isnt trusted t be a full root
In due time
Sent from my PC36100 using XDA App
Rocklee99 said:
will there be a simple root for 2.2? i hear unrevoked isnt trusted t be a full root
Click to expand...
Click to collapse
Unrevoked 3 isn't a "full root", but it is when combined with Unrevoked Forever.
Sent from my HummerPhone using the XDA App
A fulll root and s-off is being worked on for 2.2 OTA.
Noxious Ninja said:
Unrevoked 3 isn't a "full root", but it is when combined with Unrevoked Forever.
Sent from my HummerPhone using the XDA App
Click to expand...
Click to collapse
You are correct.
Sent from my PC36100 using XDA App
Unrevoked isn't exactly needed to root 2.2. Once you've returned to stock 2.1, you can use whatever 2.1 root method you want - I used SimpleRoot.
Beknatok said:
Unrevoked isn't exactly needed to root 2.2. Once you've returned to stock 2.1, you can use whatever 2.1 root method you want - I used SimpleRoot.
Click to expand...
Click to collapse
Once again: The term full root is completely meaningless. You either have root, in which case you can run code as the root user, or you do not. There is no "full root" and there is no "partial root."
There is, in addition to the normal linux access control model, a NAND lock, implemented in hardware, on these phones. This means that without a particular exploit or an ENG bootloader, there is no way to reflash a partition. Luckily, an ENG bootloader was "obtained" "in some way" from HTC. I am not sure of the legal standing of said code, but "it's worked so far."
Now, the ENG bootloader is a signed update. This means that you have to flash the whole thing: you lose all your data, and you lose your 1.40PRI. Also, since the phone is not well and truly S-OFF, if you accept an OTA, you lose your unlocked NAND.
On the other hand, unrevoked forever ALSO unlocks NAND, and it does so at a level below the radio. This means that the update is permanent. If you accept an OTA, S-OFF remains. If you RUU, S-OFF remains. You can flash our s-on.zip update to revert it. Furthermore, every line of code in Unrevoked Forever was developed by us. HTC has no legal standing to tell us to remove it.
rpearl said:
Once again: The term full root is completely meaningless. You either have root, in which case you can run code as the root user, or you do not. There is no "full root" and there is no "partial root."
There is, in addition to the normal linux access control model, a NAND lock, implemented in hardware, on these phones. This means that without a particular exploit or an ENG bootloader, there is no way to reflash a partition. Luckily, an ENG bootloader was "obtained" "in some way" from HTC. I am not sure of the legal standing of said code, but "it's worked so far."
Now, the ENG bootloader is a signed update. This means that you have to flash the whole thing: you lose all your data, and you lose your 1.40PRI. Also, since the phone is not well and truly S-OFF, if you accept an OTA, you lose your unlocked NAND.
On the other hand, unrevoked forever ALSO unlocks NAND, and it does so at a level below the radio. This means that the update is permanent. If you accept an OTA, S-OFF remains. If you RUU, S-OFF remains. You can flash our s-on.zip update to revert it. Furthermore, every line of code in Unrevoked Forever was developed by us. HTC has no legal standing to tell us to remove it.
Click to expand...
Click to collapse
so even if i am already rooted, and did so by simple root, is my nand unlocked? i would think it is right? and even if it is can i still use unrevoked forever?
rpearl said:
Once again: The term full root is completely meaningless. You either have root, in which case you can run code as the root user, or you do not. There is no "full root" and there is no "partial root."
There is, in addition to the normal linux access control model, a NAND lock, implemented in hardware, on these phones. This means that without a particular exploit or an ENG bootloader, there is no way to reflash a partition. Luckily, an ENG bootloader was "obtained" "in some way" from HTC. I am not sure of the legal standing of said code, but "it's worked so far."
Now, the ENG bootloader is a signed update. This means that you have to flash the whole thing: you lose all your data, and you lose your 1.40PRI. Also, since the phone is not well and truly S-OFF, if you accept an OTA, you lose your unlocked NAND.
On the other hand, unrevoked forever ALSO unlocks NAND, and it does so at a level below the radio. This means that the update is permanent. If you accept an OTA, S-OFF remains. If you RUU, S-OFF remains. You can flash our s-on.zip update to revert it. Furthermore, every line of code in Unrevoked Forever was developed by us. HTC has no legal standing to tell us to remove it.
Click to expand...
Click to collapse
Currently. A future update is easily capable of overriding forever.
Sent from my PC36100 using XDA App
Rocklee99 said:
so even if i am already rooted, and did so by simple root, is my nand unlocked? i would think it is right? and even if it is can i still use unrevoked forever?
Click to expand...
Click to collapse
Yes all around.
Sent from my PC36100 using XDA App
Rocklee99 said:
so even if i am already rooted, and did so by simple root, is my nand unlocked? i would think it is right? and even if it is can i still use unrevoked forever?
Click to expand...
Click to collapse
You wouldn't be nand unlocked if u used simple root. After you use that do toasts part two for nand unlock.
Sent from my Evo 4G using Tapatalk
I rooted my phone according the following link http://forum.ppcgeeks.com/showthread.php?t=123714 . I did this after getting the ota. I followed the instructions in the ROOTING AFTER OTA 1.47.651.1 (Full Root). Am running Baked Snack, kernel #5 and riptide's theme. It shows up as android 2.2 but on boot it show in the boot up screens as 2.1. If I did forever can I take the ota and retain root and nand? Is there any benefit to it other then getting PRI 1.4.003? I don't have any problems now, can't check 4G because it's not here in Crystal River,Florida. Thanks for your help in advance
islandreamer said:
I rooted my phone according the following link http://forum.ppcgeeks.com/showthread.php?t=123714 . I did this after getting the ota. I followed the instructions in the ROOTING AFTER OTA 1.47.651.1 (Full Root). Am running Baked Snack, kernel #5 and riptide's theme. It shows up as android 2.2 but on boot it show in the boot up screens as 2.1. If I did forever can I take the ota and retain root and nand? Is there any benefit to it other then getting PRI 1.4.003? I don't have any problems now, can't check 4G because it's not here in Crystal River,Florida. Thanks for your help in advance
Click to expand...
Click to collapse
The reason you are seeing 2.1 on the boot screens is because those boot screens are static png files, not the system actually booting. If you are good with graphics manipulation you can make it say 3.0 (Gingerbread).
kf2mq said:
The reason you are seeing 2.1 on the boot screens is because those boot screens are static png files, not the system actually booting. If you are good with graphics manipulation you can make it say 3.0 (Gingerbread).
Click to expand...
Click to collapse
Thanks for the response! I should have been more specific, the 2.1 I see is really not the boot screen that are rom gods put on their roms but the system checks the phone goes through during boot up. It shows root access and success, initialization , type of processor, memory check and activating android 2.1 setup. Don't know if this means I have 2.1 or not. Under software it shows as android 2.2 just assume that is from hero's rom (Baked Snack).
islandreamer said:
Thanks for the response! I should have been more specific, the 2.1 I see is really not the boot screen that are rom gods put on their roms but the system checks the phone goes through during boot up. It shows root access and success, initialization , type of processor, memory check and activating android 2.1 setup. Don't know if this means I have 2.1 or not. Under software it shows as android 2.2 just assume that is from hero's rom (Baked Snack).
Click to expand...
Click to collapse
kf2mq is right. Android doesn't show any system checks when booting up. Everything you see after the white screen that says htc EVO 4G is all a series of image files carefully placed together as a gif to give you something pleasant to look at. In your case it just so happens that your boot animation mimics a system start-up like you would see on a computer. Mine even has an Energy Star certification in the top, right corner.
If you'd like to change the animation to say 2.2 check this thread out.
http://forum.xda-developers.com/showthread.php?t=754679
SharkUW said:
Currently. A future update is easily capable of overriding forever.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Well, not so easily. But it's certainly possible. I would still wait before applying any new OTAs just in case they've figured out the magic way to undo UF without killing all legit dev phones.
Sent from my HummerPhone using the XDA App
onewaycourt said:
kf2mq is right. Android doesn't show any system checks when booting up. Everything you see after the white screen that says htc EVO 4G is all a series of image files carefully placed together as a gif to give you something pleasant to look at. In your case it just so happens that your boot animation mimics a system start-up like you would see on a computer. Mine even has an Energy Star certification in the top, right corner.
If you'd like to change the animation to say 2.2 check this thread out.
http://forum.xda-developers.com/showthread.php?t=754679
Click to expand...
Click to collapse
I will check that out. We must have the same one because the energy star is also on mine. Thank you for the enlightenment everyday I find more I need to learn. Some day I will be able to answer a question instead of ask.
SharkUW said:
Currently. A future update is easily capable of overriding forever.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Well... such an update would be very interesting. Since the same exploit is used on the radio code to allow us to set S-ON as to set S-OFF, they would be revealing how to do it.
And quite likely, we'd be able to exploit or use that too.
Furthermore, there's no magic that wouldn't kill all existent testing phones too. There's no way to tell between an unrevoked forever phone and a test phone.
Don't worry... we'll still go through and confirm updates. But the process should be much easier ("hey, you can accept the OTA straight up when you get it") rather than "here is a rooted rom, you lose all your data, but it's basically the same as the update."
rpearl said:
Well... such an update would be very interesting. Since the same exploit is used on the radio code to allow us to set S-ON as to set S-OFF, they would be revealing how to do it.
And quite likely, we'd be able to exploit or use that too.
Click to expand...
Click to collapse
Awesome.
rpearl said:
Furthermore, there's no magic that wouldn't kill all existent testing phones too. There's no way to tell between an unrevoked forever phone and a test phone.
Click to expand...
Click to collapse
Could they keep a list of the MEIDs of all dev phones and selectively push updates based on that?
It's simple if you carefully follow the instructions...
http://forum.xda-developers.com/showthread.php?t=765496
In General terms, this method sets you back to 2.1 and uses Unrevoked Forever to root Stock 2.2 in the end.
What does this do and where do I get this?
Google it
Sent from my netarchy_toast, froyo beast of a machine evo!
I dont know the answer, but evohack99's answer was really not helpful. This is the right section for the question...
Why when I can ask you??? Isn't this what this forum is for????
i still dont know what s-off is. I agree this is the right section which is why i dont understand your getting a sarcastic answer from evohack.
RichTJ99 said:
i still dont know what s-off is. I agree this is the right section which is why i dont understand your getting a sarcastic answer from evohack.
Click to expand...
Click to collapse
Ok, I found something...
The security level is a flag stored on the radio; when the flag is S-OFF, the bootloader (HBOOT) will no longer check the signatures of firmware images before flashing them. This allows custom firmware images to be uploaded, including unsigned boot, recovery, splash1, and hboot images (as well as official images that have been modified). When the system is S-OFF, the NAND flash memory protection is also reduced; this allows all partitions (including /system) to be written to while the operating system is booted.
I guess this process is a part of the Unrevoked 3.21...
fechina said:
Ok, I found something...
The security level is a flag stored on the radio; when the flag is S-OFF, the bootloader (HBOOT) will no longer check the signatures of firmware images before flashing them. This allows custom firmware images to be uploaded, including unsigned boot, recovery, splash1, and hboot images (as well as official images that have been modified). When the system is S-OFF, the NAND flash memory protection is also reduced; this allows all partitions (including /system) to be written to while the operating system is booted.
I guess this process is a part of the Unrevoked 3.21...
Click to expand...
Click to collapse
No. It is an ADDITIONAL process. While not required, it is often recommended.
See Unrevoked's website for the definitive answer.
HTH
--Chris
Sorry, that is just a common question in which can be found all over the forum or on google, sorry I was being an ass,
Sent from my netarchy_toast, froyo beast of a machine evo!
fechina said:
Ok, I found something...
The security level is a flag stored on the radio; when the flag is S-OFF, the bootloader (HBOOT) will no longer check the signatures of firmware images before flashing them. This allows custom firmware images to be uploaded, including unsigned boot, recovery, splash1, and hboot images (as well as official images that have been modified). When the system is S-OFF, the NAND flash memory protection is also reduced; this allows all partitions (including /system) to be written to while the operating system is booted.
I guess this process is a part of the Unrevoked 3.21...
Click to expand...
Click to collapse
fechina , I think it is an ADDITIONAL step using unrevoked forever, been a while since I did this and the code has changed, review the "more" option after selecting unrevoked forever at there website and it will fill in the blanks. Your definition/understanding is right on. The point, I think you need to flash unrevoked forever to have nand-off, but verify and understand the process before you do it.
debugguy said:
fechina , I think it is an ADDITIONAL step using unrevoked forever, been a while since I did this and the code has changed, review the "more" option after selecting unrevoked forever at there website and it will fill in the blanks. Your definition/understanding is right on. The point, I think you need to flash unrevoked forever to have nand-off, but verify and understand the process before you do it.
Click to expand...
Click to collapse
Correct debugguy, it IS an ADDITIONAL process. In fact, this was the route I took
to root my supersonic; Unrevoked 3.21 > Unrevoked forever.
I can state that after recently rooting my phone via Unrevoked 3.21, the
process went as intended & w/o error. But when completed && rebooted to the
newly rooted phone, S-OFF was not implemented. So I downloaded & installed
Unrevoked forever. Now S-OFF is implemented.
--Chris
From what I read before I rooted.
S-Off prevents the rom from reverting back to the original data every time you reboot.
It also lets you flash custom roms.
UnrEVOked 3.21 sets it to S-Off, but unrEVOked forever will make S-Off permanent.
Permanent... as in safe to update using OTA's.
If you aren't unrEVOked forever an OTA can actually remove the S-Off flag and prevent you from re-rooting.
xNotta said:
From what I read before I rooted.
S-Off prevents the rom from reverting back to the original data every time you reboot.
It also lets you flash custom roms.
UnrEVOked 3.21 sets it to S-Off, but unrEVOked forever will make S-Off permanent.
Permanent... as in safe to update using OTA's.
If you aren't unrEVOked forever an OTA can actually remove the S-Off flag and prevent you from re-rooting.
Click to expand...
Click to collapse
Yes.
Unrevoked 3.21 = S-OFF && r/w long enough to rewrite your ROM with the one provided in Unrevoked 3.21
Unrevoked forever = S-OFF forever
It's all at their website and in numerous threads in these forums.
--Chris
Thanks.....
WOW, thanks...
xNotta said:
.....
If you aren't unrEVOked forever an OTA can actually remove the S-Off flag and prevent you from re-rooting.
Click to expand...
Click to collapse
This is the line I don't understand. If you don't run Forever and an OTA removes the S-OFF flag, why couldn't you just re-run Unrevoked again to gain root access?
Is it because a new OTA could block Unrevoked?
Thanks!
daystrom said:
This is the line I don't understand. If you don't run Forever and an OTA removes the S-OFF flag, why couldn't you just re-run Unrevoked again to gain root access?
Is it because a new OTA could block Unrevoked?
Thanks!
Click to expand...
Click to collapse
Unrevoked exploits a vulnerability to "root" the phone.
So, an OTA could patch that vulnerability and you would have to wait for another exploit to be found in order to regain S-Off and root again.
Ex. When OTA froyo came out unrevoked would not work since htc fixed the vulnerability used in rooting 2.1.
Sent from my Evo using XDA App.
Cool, thanks for that good info.
One more question -
Many are saying that you have to run Forever AFTER you have installed 3.21.
HOWEVER when you run 3.21 and click File, there is an option that is checked that says "Disable security on Phone".
When you select this a prompt comes up saying "unrEVOked Forever will not be installed".
When you select it again to enable it a prompt comes up saying "unrEVOked Forever will be installed to disable device security.".
To me this sounds like Forever IS installed with 3.21.
No?
daystrom said:
One more question -
Many are saying that you have to run Forever AFTER you have installed 3.21.
HOWEVER when you run 3.21 and click File, there is an option that is checked that says "Disable security on Phone".
When you select this a prompt comes up saying "unrEVOked Forever will not be installed".
When you select it again to enable it a prompt comes up saying "unrEVOked Forever will be installed to disable device security.".
To me this sounds like Forever IS installed with 3.21.
No?
Click to expand...
Click to collapse
I've actually wondered the same thing, since after rooting with 3.21 it is set to S-Off.
I wanted to be safe so I still flashed unrevoked forever.
It's a flashable zip so it's not hard to do and it take only a few seconds.
Better safe then without root, imo.
Sent from my Evo using XDA App.
Quick question. I had to use simple root method because of issues with unrevoked 3.21. Can I still run unrevoked forever?
It's called supersonic for a reason.
Hi guys,
I've been reading through the forums over the past two days but I have to admit it's hard to find what I am looking for now that the G2 forum and the DZ forum are merged, and the search isn't getting me anywhere for this one.
I have Bell Canada Desire Z permarooted and S-OFF'd, with CWMod. I did this before the newer gfree method and from what I can gather this can lead me to some kind of endless loop if I try to flash back to the a Bell RUU or other RUUs for that matter. It also worries me that I can't try new radios, etc.
I am getting very poor battery life compared to others so I want to have my phone replaced. I have an extended warranty from FutureShop so I probably don't even need to reset the phone to stock again (they swap on the spot) but I would like to anyway. It will also allow me to test the battery again with the stock ROM.
So, how do I go about flashing back to the Bell ROM and turning S-ON, and unrooting? Keeping in mind that I used the pre-gfree method. I believe it was Visionary R12 and gtab's guide.
Also as the title implies, I was wondering if it's possible to use the new (better) S-OFF even if I am already S-OFF'd the old way?
Any help is appreciated!
You can use gfree and achieve "real" S-OFF without having to unroot.
Just run it. Worst that'll happen is it fails if you happen to be on a kernel it doesn't like. If this happens, no harm is done, just a reboot.
Just run gfree from where you are, as the previous poster said.
That will put you in a much safer position, where you can get stuck in that boot loop that you can if you've only got the eng hboot.
Then you can flash whichever ROM you want. Then you can undo gfree if you want via its new options (see the Wiki).
Regarding your point about the merger, IMHO this issue isn't anything to do with the DZ specifically, and lots of users are posting about similar stuff with their G2s. It's all the same
Thanks guys,
I've done gfree (which is MUCH easier than the thread and wiki make it look - they need to simplify the text, it's overwhelming to look at given how simple the procedure is) and flashed the Bell RUU.
Now I am just about to root, and use gfree to undo the S-OFF I guess?
Will let you know how that turns out. Thanks again!
Ok,there is a new gfree method to get root and S-Off.
And gfree can now also be used to set radio S-ON.
But what about the backup "part7backup-1291675121.bin"
which gfree created at my sdcard?
No longer needed?
And with the new root and S-Off method,is it now possible to
to flash stock RUU 1.34.405.5 to get all original?
Because with old UBERROOT method this doesn`t work!
Ganii said:
Ok,there is a new gfree method to get root and S-Off.
And gfree can now also be used to set radio S-ON.
But what about the backup "part7backup-1291675121.bin"
which gfree created at my sdcard?
No longer needed?
And with the new root and S-Off method,is it now possible to
to flash stock RUU 1.34.405.5 to get all original?
Because with old UBERROOT method this doesn`t work!
Click to expand...
Click to collapse
I'd keep that backup file as it is a dump of your original partition 7 before gfree mods it. You can dd i back and put everything back to how it was, if you ever need to. Do you need to keep it on the phone? No.. store it somewhere on your PC.
With the old "fake" S-OFF you would get stuck if you flashed a stock rom because it would overwrite the engineering HBOOT which was the only thing making your phone think it had S-OFF. With gfree method, you have real S-OFF, so this should be fine.
See http://forum.xda-developers.com/showthread.php?t=838484 for details.
tl;dr You should be fine.
Hm,little bit confused!
The backup I need to get original original partition 7
but not to get S-On.
To get S-On I can use the new gfree method,it`s now
possible with this!
I did the old UBERROOT method with real S-Off!
P.S.I read here about this:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
Not 100% sure I understand the question...but:
You don't need that backup file. If you delete it nothing bad will happen. Paranoid people (like me) would copy it to a safe place, but there's no real need.
You can flash whatever roms you like, including stock ones, as long as you have real, radio (gfree) S-OFF.
Hi guys, thanks for the help! I got it all settled, it was easy.
As I mentioned above, I used gfree to do a true S-OFF, which was easy.
Then I ran Bell's RUU and it worked without any issues. I assume the RUU install also flashes the HTC recovery back to the phone, I didn't check but it must..
A little summary for anyone who needs help in the future..
If you rooted/S-OFF'd using a method older than the current rage/gfree method (the one in the wiki) then you need to redo the S-OFF using gfree.
Steps:
Use gfree -f to S-OFF again
Run the stock RUU file on your pc (you need HTC sync installed for this)
Temproot (first part of the wiki guide) the stock ROM
Use gfree -s on to S-ON your phone
Reboot, and everything should appear like stock (aside from still being sim-unlocked).
Were u sucessful in returning your phone to htc after u did the above?
I didn't have to return it to htc, just to future shop, and it was fine.
Sent from my GT-I9000 using XDA App
What's up! I'm wondering if someone can help me unroot and put back to 100% stock...
I used the rage/gfree method.
Sent from my HTC Vision using XDA App
http://forum.xda-developers.com/showthread.php?t=835971
That should do the trick.
He doesn't give instructions for gfree, so I'm not sure if this is the correct method.
Sent from my HTC Vision using XDA App
Ah - apologies.
No worries bro, hopefully someone else can help answer this question for me.
Sent from my HTC Vision using XDA App
I typed in unroot G2 in bing search and the unlockr site was second one down, this method worked great for me.
I looked it and read it all.
Since I used gfree to obtain s off and super cid/sim unlock, will it work?
Sent from my T-Mobile G2 using XDA App
mftek said:
I looked it and read it all.
Since I used gfree to obtain s off and super cid/sim unlock, will it work?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
I'm not 100% positive on that. I also have a Behold 2 and, it was rooted when I got it.
I had no idea how it was rooted. I used the unlockr site for it too and, it work for it.
To me, the way the instructions are wrote, it sounds like it will work to un-root all methods of the G2 root process.
Hopefully a more experienced person will chime in shortly.
tooter1 said:
I'm not 100% positive on that. I also have a Behold 2 and, it was rooted when I got it.
I had no idea how it was rooted. I used the unlockr site for it too and, it work for it.
To me, the way the instructions are wrote, it sounds like it will work to un-root all methods of the G2 root process.
Hopefully a more experienced person will chime in shortly.
Click to expand...
Click to collapse
No, those guides will technically remove root since they restore the shipping ROM but will leave you with S-OFF (since you used gfree---if you had only used the engineering HBOOT to obtain S-OFF, the guides would have been fine). Did you take a look at the actual Wiki: http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Returning_to_Stock?
ianmcquinn said:
No, those guides will technically remove root since they restore the shipping ROM but will leave you with S-OFF (since you used gfree---if you had only used the engineering HBOOT to obtain S-OFF, the guides would have been fine). Did you take a look at the actual Wiki: http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Returning_to_Stock?
Click to expand...
Click to collapse
When I used the unlockr method, my s-off went s-on.
tooter1 said:
When I used the unlockr method, my s-off went s-on.
Click to expand...
Click to collapse
Did you use gfree to to obtain S-OFF though? If you used the engineering HBOOT to do it, as I said in my post, those guides would work fine as is. Flashing the shipping ROM with the PC10IMG file will replace the engineering HBOOT with the shipping one (which is S-ON). If you use gfree though, you get true radio S-OFF (the engineering HBOOT is a fake one that tricks the phone into thinking you have S-OFF, thus allowing write access to the system). This is done by modifying partition 7 on the phone. Since this partition contains information specific to your phone, it is normally left untouched by a PC10IMG or RUU. This is why if S-OFF is obtained through gfree, simply replacing the HBOOT with a PC10IMG file won't revert you to S-ON.
ianmcquinn said:
Did you use gfree to to obtain S-OFF though? If you used the engineering HBOOT to do it, as I said in my post, those guides would work fine as is. Flashing the shipping ROM with the PC10IMG file will replace the engineering HBOOT with the shipping one (which is S-ON). If you use gfree though, you get true radio S-OFF (the engineering HBOOT is a fake one that tricks the phone into thinking you have S-OFF, thus allowing write access to the system). This is done by modifying partition 7 on the phone. Since this partition contains information specific to your phone, it is normally left untouched by a PC10IMG or RUU. This is why if S-OFF is obtained through gfree, simply replacing the HBOOT with a PC10IMG file won't revert you to S-ON.
Click to expand...
Click to collapse
Worked perfectly for me. I flashed stock rom, installed PC10IMG.zip and then used gfree to turn s-on and remove sim unlock.
Sent from my T-Mobile G2 using XDA App
ianmcquinn said:
Did you use gfree to to obtain S-OFF though? If you used the engineering HBOOT to do it, as I said in my post, those guides would work fine as is. Flashing the shipping ROM with the PC10IMG file will replace the engineering HBOOT with the shipping one (which is S-ON). If you use gfree though, you get true radio S-OFF (the engineering HBOOT is a fake one that tricks the phone into thinking you have S-OFF, thus allowing write access to the system). This is done by modifying partition 7 on the phone. Since this partition contains information specific to your phone, it is normally left untouched by a PC10IMG or RUU. This is why if S-OFF is obtained through gfree, simply replacing the HBOOT with a PC10IMG file won't revert you to S-ON.
Click to expand...
Click to collapse
What should I do first if I used gfree to return to stock on my T-Mobile US G2? I also flashed the eng-hboot.
I used this guide http://forum.cyanogenmod.com/topic/14344-how-to-root-a-new-g2/, and I flashed the "PC10IMG-altered.zip" right after I used gfree to get radio s-off.
Edit: I just followed the xda wiki and I didn't run into any problems.
Hi,
I've got my DZ a couple of days ago. It's a secondhand DZ. Previously i've used HTC Touch, Touch Dual, TP2, so this is my first Android experience. I did lots of ROM playing on previous winmo phones, but after reading for these couple of days of Android modding, i learn that flashing another Android ROM is not so simple as winmo ROM.
This is my DZ info:
Android version 2.2.1
Baseband version 12.28e.60.140fU_26.04.02.17_M2
Kernel version 2.6.32.21-g6e170e7
Build number 1.82.707.1 CL317545 release-keys
Software number 1.82.707.1
VISION PVT SHIP S-OFF
HBOOT - 0.85.0009
MICROP - 0425
RADIO - 26.04.02.17_M2
eMMC - boot
Dec 13 2010
I've check with root checker and Titanium Backup, it says NO root access.
I've learned that with 1.82, i will have to downgrade first to 1.34.
In the steps for downgrading, i found that i will have to flash signed PC10IMG. But i also found in the sticky thread there's a warning, not to flash signed PC10IMG if i have S-OFF. So before i can downgrade, i have to get the S-ON.
I've read in a thread :
If for some reason (sending phone for warranty or repair, etc) you want to go back to S-ON:
- If you got S-OFF by flashing an Engineering hBoot, download the official HTC RUU for your phone version and flash the stock firmware back again. S-ON will be restored. This forum contains many threads with official RUUs.
- If you got S-OFF with gfree, it saved a backup copy to your SD card called "part7backup-xxxxxxxxxx.bin". It can be flashed back from a terminal emulator or from an ADB shell:
"dd if=/wherever/your/part7backup-xxxxxxx.bin of=/dev/block/mmcblk0p7
The problem is, i got a secondhand unit without microSD card. How can I get S-ON? I don't know how (what method) my DZ got S-OFF at the first place.
Any help is much appreciated.
prazzo said:
Hi,
I've got my DZ a couple of days ago. It's a secondhand DZ. Previously i've used HTC Touch, Touch Dual, TP2, so this is my first Android experience. I did lots of ROM playing on previous winmo phones, but after reading for these couple of days of Android modding, i learn that flashing another Android ROM is not so simple as winmo ROM.
This is my DZ info:
Android version 2.2.1
Baseband version 12.28e.60.140fU_26.04.02.17_M2
Kernel version 2.6.32.21-g6e170e7
Build number 1.82.707.1 CL317545 release-keys
Software number 1.82.707.1
VISION PVT SHIP S-OFF
HBOOT - 0.85.0009
MICROP - 0425
RADIO - 26.04.02.17_M2
eMMC - boot
Dec 13 2010
I've check with root checker and Titanium Backup, it says NO root access.
I've learned that with 1.82, i will have to downgrade first to 1.34.
In the steps for downgrading, i found that i will have to flash signed PC10IMG. But i also found in the sticky thread there's a warning, not to flash signed PC10IMG if i have S-OFF. So before i can downgrade, i have to get the S-ON.
I've read in a thread :
If for some reason (sending phone for warranty or repair, etc) you want to go back to S-ON:
- If you got S-OFF by flashing an Engineering hBoot, download the official HTC RUU for your phone version and flash the stock firmware back again. S-ON will be restored. This forum contains many threads with official RUUs.
- If you got S-OFF with gfree, it saved a backup copy to your SD card called "part7backup-xxxxxxxxxx.bin". It can be flashed back from a terminal emulator or from an ADB shell:
"dd if=/wherever/your/part7backup-xxxxxxx.bin of=/dev/block/mmcblk0p7
The problem is, i got a secondhand unit without microSD card. How can I get S-ON? I don't know how (what method) my DZ got S-OFF at the first place.
Any help is much appreciated.
Click to expand...
Click to collapse
You are already S-OFF? I'd find it strange that you'd be S-OFF and not be rooted.
install rom manager and check if there has been a recovery already flashed. Might answer your question
Why do you want s-on? S-off is a good thing
Sent from my T-Mobile G2 using XDA Premium App
You can check if you got S-OFF or S-ON
by entering bootloader
Power off your phone, then, hold the volume down key and the power key.
You might need to disable fastboot
Spastic909 said:
install rom manager and check if there has been a recovery already flashed. Might answer your question
Why do you want s-on? S-off is a good thing
Sent from my T-Mobile G2 using XDA Premium App
Click to expand...
Click to collapse
I've already installed Rom manager and there's no clockwork recvery installed.
I want to flash custom rom. I need a root to do that. To get a root, i need to downgrade. To downgrade, i need to flash signed pc10img. And there's a warning here that said DONT flash pc10img with S-OFF. That's the problem.
Shinfang said:
You can check if you got S-OFF or S-ON
by entering bootloader
Power off your phone, then, hold the volume down key and the power key.
You might need to disable fastboot
Click to expand...
Click to collapse
I already did that. Bootloader says VISION PVT SHIP S-OFF. So that means i definitely have S-OFF.
I've learned some more from the post here and there. I think i figured out what happen with my DZ. I think the previous owner rooted and S-OFF the phone in the old firmware 1.34 then got an OTA update to 1.84. That update destroyed the root but somehow still S-OFF.
If I follow the direction in this thread, i assume that i can downgrade and root again. I will not need a goldcard to downgrade because currently i have S-OFF.
http://forum.xda-developers.com/showthread.php?t=905261
Am i right?
prazzo said:
I've learned some more from the post here and there. I think i figured out what happen with my DZ. I think the previous owner rooted and S-OFF the phone in the old firmware 1.34 then got an OTA update to 1.84. That update destroyed the root but somehow still S-OFF.
If I follow the direction in this thread, i assume that i can downgrade and root again. I will not need a goldcard to downgrade because currently i have S-OFF.
http://forum.xda-developers.com/showthread.php?t=905261
Am i right?
Click to expand...
Click to collapse
I am not sure whether it will work. But I am curious too.
I once upgrade via OTA and then I downgrade it following the instruction as per your link reference too. I rooted succesfully.
But, my DZ was S-ON.
Now you are in a different situation. You want to downgrade and root it but you already S-OFF.
Do you want to try it?
Cheers
silverwind said:
I am not sure whether it will work. But I am curious too.
I once upgrade via OTA and then I downgrade it following the instruction as per your link reference too. I rooted succesfully.
But, my DZ was S-ON.
Now you are in a different situation. You want to downgrade and root it but you already S-OFF.
Do you want to try it?
Cheers
Click to expand...
Click to collapse
I guess i have to try it.. will report after trying. Thnks all for the help..
Your theory on the previous owner having used the over the air update after rooting seems right to me. I've read more than a few times it will still show S-OFF but not be true S-OFF. Because you can't get S-OFF without root (well surely not on the newer 1.82's)
I'm not familiar with the 1.82 issues (why normal root methods fail on 1.82) but I wonder if temp root works, if you have radio S-OFF and temp root works it might be as simple as:
1. Obtain Temp Root (even Visionary could work)
2. Flash CWM Recovery (I'd use the flash_image method and not ROM Manager)
3. Reboot into CWM recovery
4. ...
5. Profit (Install a new pre-rooted ROM)
Of course this all depends on if temp root works with 1.82 and if your S-OFF is really S-OFF but it seems like a quick & easy thing to try.
I did it guys. It went smooth. Still needs goldcard though due to unmatched CID.
I'm on 1.34, rooted and S-OFF. Next find out ROM that i like most. Any recommendation? it has to be cool and fast..
So i figured that the warning "do not flash signed PC10IMG if you have S-OFF" is before we have the misc_version method. With misc_version "main is older" problem will never occur, provided misc_version done correctly.
Thank you all guys for your help and time especially for those guides starter. You guys are the ones who make this forum SO GREAT!
prazzo said:
I did it guys. It went smooth. Still needs goldcard though due to unmatched CID.
I'm on 1.34, rooted and S-OFF. Next find out ROM that i like most. Any recommendation? it has to be cool and fast..
So i figured that the warning "do not flash signed PC10IMG if you have S-OFF" is before we have the misc_version method. With misc_version "main is older" problem will never occur, provided misc_version done correctly.
Thank you all guys for your help and time especially for those guides starter. You guys are the ones who make this forum SO GREAT!
Click to expand...
Click to collapse
Congrats .
The first time I did after rooting was install ROM MANAGER premium version.
There a lot of rom to try with the easiest way..
Good luck