Related
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
I was following instructions on verifying if my HTC Desire Z has been rooted using this guide
I was expecting to see the result as the same subject as above but got this instead
===================
$ su
su
# cd /data/local
cd /data/local
# chmod 777 gfree_verify
chmod 777 gfree_verify
# stop ril-daemon
stop ril-daemon
# ./gfree_verify
./gfree_verify
gfree verify_cid returned:
@CID: HTC__044
OK
gfree verify_secu_flag returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@SIMLOCK= 00
OK
===================
What does HTC__044 mean?
it means that you do not have supercid
tazz9690 said:
it means that you do not have supercid
Click to expand...
Click to collapse
Despite that, did I do a successful root?
From the information you posted, you are S-Off (@secu_flag:0) and your sim is unlocked (@SIMLOCK=00), so you should have successfully rooted.
Just to verify, do you have superuser privileges? If you do, then you should be set.
If you want the supercid privileges, I cannot help you there. I did not have that problem when I used gfree, nor have I seen anyone else with this problem.
Quick question though. Since you have everything but supercid, did you run:
# ./gfree -f
# sync
Or did you run another line besides "-f".
That is the only thing that I can see as to why you do not have it, but then again, my knowledge is limited when it comes to gfree.
tazz9690 said:
From the information you posted, you are S-Off (@secu_flag:0) and your sim is unlocked (@SIMLOCK=00), so you should have successfully rooted.
Just to verify, do you have superuser privileges? If you do, then you should be set.
If you want the supercid privileges, I cannot help you there. I did not have that problem when I used gfree, nor have I seen anyone else with this problem.
Quick question though. Since you have everything but supercid, did you run:
# ./gfree -f
# sync
Or did you run another line besides "-f".
That is the only thing that I can see as to why you do not have it, but then again, my knowledge is limited when it comes to gfree.
Click to expand...
Click to collapse
I did run -f and sync. The Superuser app is on the applications menu. I just wanted to make sure I was properly rooted. I was also able to make a backup of the ROM (I already had S-Off before from a previous attempt). I tried following the procedure to set S-Off back to S-On using #./grfree -s on but I got permission denied. I am not sure if I was doing it right.
My HTC Desire Z was bought in Singapore last December and this is the current About Phone information I have:
=========
Android version 2.2
Baseband version 12.28b.60.140eU_26.03.02.26_M
Kernel version 2.6.32.21-gd2764ed [email protected] #1 Tue Oct 26 16:04:03 CST 2010
Build number 1.34.707.5 CL273326 release-keys
Software Number 1.34.707.5
Browser version
Webkit 3.1
==========
I am not even sure if this already has the 1.72 update everyone has been talking about. How do I find that out?
Your software number tells you what version you are running.
You have 1.34, not the 1.72 update.
If you had the 1.72 update, you would not have been able to use the wiki, you would have had to use the new method (psneuter) to obtain temp root and then downgrade to an older version to then be able to use gfree.
tazz9690 said:
Your software number tells you what version you are running.
You have 1.34, not the 1.72 update.
If you had the 1.72 update, you would not have been able to use the wiki, you would have had to use the new method (psneuter) to obtain temp root and then downgrade to an older version to then be able to use gfree.
Click to expand...
Click to collapse
Thanks! I was able to flash to Cyanogen 6.1.1 but the onscreen buttons are just making haptic feedback but no response. I'll see what I can find to get this one working and will try other ROMs as well. I am currently downloading MIUI. What other ROMS can I try?
iamthechickengod said:
Thanks! I was able to flash to Cyanogen 6.1.1 but the onscreen buttons are just making haptic feedback but no response. I'll see what I can find to get this one working and will try other ROMs as well. I am currently downloading MIUI. What other ROMS can I try?
Click to expand...
Click to collapse
Cynogen Mod and MIUI are like the only ones ;p
you could try GingerVillan 1.4 but that requires Clock works recovery 3.0
You can also try a rooted sense rom as well, if you so please.
Also, the CM7 nightlies are on the Cyanogenmod website if you so please to run that, but that requires clockworkmod recovery 3.x.x.x
Stuck with HTC__044
I did the gfree per rooting process with -s off only. I have even installed cm7 with no problem. Now i need totryied change my CID to 11111111 to update more things. I tried running gfree again with -cid 11111111 but no success. How do i change it? Im stuck.
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
Hi guys and gals, today we're going to talk about getting a Desire Z to S-On, but first here is a bit of background...
I rooted my phone using rage/gfree v1 or v2 in december 2010. That produced a partition 7 backup which I still have.
I also made a nandroid backup after rooting and installing CWR which I still have.
I have succefully removed Superuser.apk, un-rooted, put back original h-boot and orignal rom 1.34.666.5.
I cannot complete the final step; getting back to S-On. Here is what I have tried:
1) Get temp root with psneuter then use gfree v6 or v7 to reload my partition 7 backup. Did not turn s-on
2) Get temp root with psneuter then use Gfree to turn s-on. Did not turn s-on
3) Other threads about getting S-on talk only about the t-mobile G2, Not the DZ for example...
The part of the wiki that discusses returning to S-On is only applicable to T-mobile G2s. Not the Desire Z (http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Unrooting_and_Returning_to_Stock)
A few other guides talk about the T-mobile G2 but not the DZ (http://forum.xda-developers.com/showthread.php?t=835971&highlight=unroot)
Other guides deal with cases where you rooted using visionary which I didn't (http://theunlockr.com/2010/12/01/how...g2-htc-vision/)
Potential hints:
-I do not know which radio I had back then
-I am trying to get S-on after removing eng-hboot
What do you suggest I try?
Restoring your part7backup with gfree should work, you need to be on a 1.34 rom, and have a radio version at 26.03.xx.xx or lower.
Those guides for the G2 should work with the DZ also, seeing as they are identical devices (only difference is the hboot)
-Nipqer
is it safe to just run the RUU files instead to go back to stock form?
Running a stock RUU will return you to full stock (hboot, recovery, system)
BUT you will still be S-ON if you used gfree.
-Nipqer
Flash05 said:
is it safe to just run the RUU files instead to go back to stock form?
Click to expand...
Click to collapse
its safe and it's the fastest way!
but you will return to stock 2.3.3
I had a similar issue months ago (partition restore didn't work), in the end I went the whole way and got PERM-root.
In Terminal Emulator I typed the following:
Code:
/data/local/tmp/gfree -s on
sync
After that I rebooted into the bootloader to check if it'd worked and if it did I flashed the PC10IMG.zip I used in the rooting process to reset it.
d_gkal said:
its safe and it's the fastest way!
but you will return to stock 2.3.3
Click to expand...
Click to collapse
It depends on which RUU you run actually...
If you get the latest, then yeah you'll be on 2.3.3, but you can easily find froyo ones to use.
-Nipqer
Nipqer said:
It depends on which RUU you run actually...
If you get the latest, then yeah you'll be on 2.3.3, but you can easily find froyo ones to use.
-Nipqer
Click to expand...
Click to collapse
im on 2.3.3 GB OTA. can i run RUU with 2.2 so that i dont go thru the hassle of downgrading, running these and those... then from here root then custom ROM?
No, you need to modify the misc partition, which is where the version information is stored to allow a downgrade.
Even RUU's check if its newer or older before flashing.
-Nipqer
If you use the ruu, won't your telephone brick?
Sent from my HTC Vision using XDA App
double post
I'll try Scythes method tonight and report my results. I was gone this weekend so I couldn't play with it.
Scythe01 said:
I had a similar issue months ago (partition restore didn't work), in the end I went the whole way and got PERM-root.
In Terminal Emulator I typed the following:
Code:
/data/local/tmp/gfree -s on
sync
After that I rebooted into the bootloader to check if it'd worked and if it did I flashed the PC10IMG.zip I used in the rooting process to reset it.
Click to expand...
Click to collapse
Thanks
Should probably reset your cid as well...
you can find it by doing
Code:
dd if=/dev/block/mmcblk0p17 bs=1 count=8 2>/dev/null; echo
in adb shell, or terminal emulator.
then set your cid with
Code:
./gfree -c <cid here>
Note: CID is an 8 character string.
-Nipqer
Koopabro said:
If you use the ruu, won't your telephone brick?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
why?
10 chars
ok i have the same problem with an AZERTY Desire Z.
Now i don't have the original ruu, however I made a backup using dd to copy all the images to the sdcard. I don't have a backup of partition 7 though.
Here's the deal:
Went from a stock rooted gingerbread rom to stock 1.82.1100.7 rom (froyo). Stock recovery and radio restored. Everything is stock except, you guessed it, hboot. Can't get S-ON back. I tried the method in the wiki and it still wouldn't turn S-ON. I also have SuperCID eventhough i tried the gfree method to get CID back to stock (HTC__E41).
I tried upgrading to the latest stock 2.3.3 rom, but the hboot still stayed S-OFF. Which is a good thing since I am able to get CWM back and return to the froyo 1.82 rom. Once I was back, I also tried restoring a stock hboot but that didn't change anything.
So any suggestions? How can I get this device back to S-ON?
yozgatg said:
I tried upgrading to the latest stock 2.3.3 rom, but the hboot still stayed S-OFF.
So any suggestions? How can I get this device back to S-ON?
Click to expand...
Click to collapse
And i also have cid 11111111
I have to send the phone back cause of continue freezes but i think sending it with s-off and supercid won't help me to get it changed by guarantee
me too failed to get the S -on back again...
i am still figuring on how to do that for 2 weeks already...
basically read everything, tried what i am allowed. but to no avail...
i heard that people do send the phone with s -off for guarantee repair..
my ear speaker is not working anymore while in the guarantee period.
sad...
sevensaints said:
i heard that people do send the phone with s -off for guarantee repair..
my ear speaker is not working anymore while in the guarantee period.
sad...
Click to expand...
Click to collapse
I've sent mine with supercid and S-OFF and they repaired it with guarantee without any problem !!
The ear speaker was not broken by the rooting process, am i right ??
I couldn't get s-on or CID back to the bell CID.
I sent it in for repair for the second time. I'll keep you guys updated...
I sent my phone for repair of the BSOD (black screen of death) a second time. It was S-Off and superCID since I was incapable of returning them to stock. Nevertheless, they replaced the motherboard of my phone and it was covered by the guarantee (confirmed by the new serial number). Unfortunately, the issue is still occurring.