Is it possible to lock SIM on the G2 after unlocking with gfree? It's been acting really crazy lately and I think I'd rather just go back to having it locked if possible.
My current system info:
HBOOT: 0.76.2000 (PC1010000)
RADIO: 26.02.01.15_M2
S-OFF
I was running CM7 but after sync, battery, signal issues I've had since installing it, I want to go back to stock and just do the OTA update to GB if possible. Any help? I'd really appreciate it.
Just as a note... When I reflashed back to my stock backup, I get a message now showing that I have a radio update to install, which fails because of a Signature Error, if Im not mistaken, this is because I did the SIM unlock, right?
stubby210 said:
Is it possible to lock SIM on the G2 after unlocking with gfree? It's been acting really crazy lately and I think I'd rather just go back to having it locked if possible.
My current system info:
HBOOT: 0.76.2000 (PC1010000)
RADIO: 26.02.01.15_M2
S-OFF
I was running CM7 but after sync, battery, signal issues I've had since installing it, I want to go back to stock and just do the OTA update to GB if possible. Any help? I'd really appreciate it.
Just as a note... When I reflashed back to my stock backup, I get a message now showing that I have a radio update to install, which fails because of a Signature Error, if Im not mistaken, this is because I did the SIM unlock, right?
Click to expand...
Click to collapse
You're wanting to go back to the way it was out of the box? There's a guide in the wiki to return to stock, it's towards the bottom of the page that had the root guide.
Sent from my HTC Vision using XDA App
Thanks. I'm going to try a different radio first. Hopefully it will fix some of the craziness I've been experiencing the past couple of days. If it doesnt work out I'll check out that thread. I appreciate your help.
Option 1: Revert to stock.
When you use gfree it also changes the CID to super CID aka 11111111. To find out the old CID you can do the following via adb shell (comp) or Terminal (your phone):
Code:
dd if=/dev/block/mmcblk0p17 bs=1 count=8 2>/dev/null; echo
Your next port of call is to use gfree to change everything back to the way it was at stock.
After reverting to stock ROM (flashing the stock backup), follow the guide to gain perm-root(temp-root doesn't work) but once you have perm-root, we do this:
Code:
/data/local/tmp/gfree -c <insertCID>
/data/local/tmp/gfree -S
/data/local/gfree -s on
sync
From there you just flash the stock PC10IMG.zip via the bootloader and the job is done, all evidence of having gained route is now no longer there.
Option 2: Try a different ROM and see if it has the same effect.
A friend of mine told me how he has loads of problems with CM7 on his Nexus One, so it may not be the phone but the ROM itself. Try out other ROMs to see if it has the same effect.
Option 3: Different radios.
May not always work.
I downloaded the stock ROM from a link I found in the wiki. Everything is back as it was. Thanks for your post though. Ill make sure to keep note of it for future reference.
Sent from my T-Mobile G2 using XDA App
Adding to Scythe01's post,
You can do all those commands in one, you don't have to do them one after another.
Also, you should have a part7backup-xxxxxxxxx.bin on your sdcard, which has your exact simlock, s-on and cid info as it was before rooting, so you could just do
./gfree -r part7backup-xxxxxxxx.bin
(swap out the x's for the numbers)
-Nipqer
Thanks.. I was able to get everything back to how it was by flashing the TMOUS stock ROM from a link I found in the wiki. So far everything is working as it should. Again, I cant thank y'all enough. You guys really know your stuff. Break-fix is the only way I'll really be able to learn more about modding androids... and you guys are a real help. Many thanks again.
Nipqer said:
Adding to Scythe01's post,
You can do all those commands in one, you don't have to do them one after another.
Also, you should have a part7backup-xxxxxxxxx.bin on your sdcard, which has your exact simlock, s-on and cid info as it was before rooting, so you could just do
./gfree -r part7backup-xxxxxxxx.bin
Click to expand...
Click to collapse
I only broke it up into three separate steps to avoid confusion, wish the switch for simlock were something else and not '-S' with secuflag being '-s on' or '-s off'. :/
Personally I don't like using the backed up partitions, and find it easier to just use gfree to reset everything.
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
Thank you for droping in cause I really need your help! I made a huge mistake on it when I tried to unlock the phone.
The gfree method told that it doesn't work with radio higher than 26.03.02.xx but mine is 26.04.xx.xx. So I just did a stupid thing to found an older (official?) RUU and flashed it....
the radio has been downgraded to 26.02.15.xx(almost it) but the ship became s-on!!!!
And I tried the gfree several times on work! The former S-off method is depend on the offical rom so I thought it should not work as well...
What surprise me most is that the rom still has ROOT!! I've used clockmodrecovery to backup several times before the accident. The recovery still works however the radio cannot be flashed now and there is just S-ON!
So many words but I cannot find the point please help me, thank you
Now here is the brief situation:
1. The phone are now with an old radio. s-on and clockworkmod recovery(funny- -)
2. PC10IMG.img to flash radio failed. But by cwm recovery I can flash any rom or backup and restore any roms.
3. Before the situation I've once flashed a 4.02.17(?) radio and seems all gone right. Then I flashed a former radio as mentioned above and it comes here.
Are you sure you still have root ? Was it an official RUU you flashed ? Because all official RUUs will not have root (though you may be able to re-root, depending on the exact version).
A stock RUU/ROM will install a new hboot, and if you only had S-OFF via the eng hboot, you will lose that. Which is why everyone with S-OFF should make sure they have it via gfree.
What version of ROM are you running right now ?
This shouldn't be a new thread though, should be in an existing thread or in the Q&A forum
Thank you for your words! I flashed the RUU and found my rom is kept, just the radio downgraded and s-on...
I'm using the Q'N'D-miui rom...
Now I've tried to install new rom and I managed to install the CM6.1.1 tough the S-ON is still there, doesn't it mean I got the root? I the os I can find the superuser work correctly.
Sorry that I cannot find any similar situation in the forum and I'm new here...So I thought it can be a new thread
you might beable to just flash the spl by completing the last couple of steps ion the original g2 root process. don't quote me on this though, cuz i really don't know what i'm saying.
5. Open up terminal, type in "su" then press enter. Then without exiting type in "insmod /sdcard/wpthis-[YOURVERSION].ko" and press enter. Make sure you use the proper version of wpthis that applies to you. If you got the proper message type in "dd if=/sdcard/hboot-eng.img of=/dev/block/mmcblk0p18". Do not exit terminal in this step at all.
6. Exit terminal and run visionary again to make sure you're rooted.
7. Go back into terminal and type "su" then press enter, then type "sync". Wait about 10 seconds then pull the battery out.
8. Boot into recovery by holding volume down + power off until it comes up.
If it says S-OFF, you're rooted! Good job!
I'm [email protected]@ cuz I'm now using the miui rom not the origin one, which version of wpthis.ko is suitable for me?? Seems that just a mistake on it can bring me a brick...
So [rom] [guide] [kernal] [patch]...not [q]
I'm kinda confused what state your phone is in. Because if you are S-ON you wouldn't be able to flash any custom ROMs at all.
Sent from my HTC Desire Z
actually you might be able to skip the first step and just flash the spl
type in "dd if=/sdcard/hboot-eng.img of=/dev/block/mmcblk0p18". Do not exit terminal in this step at all.
6. Exit terminal and run visionary again to make sure you're rooted.
7. Go back into terminal and type "su" then press enter, then type "sync". Wait about 10 seconds then pull the battery out.
8. Boot into recovery by holding volume down + power off until it comes up.
If it says S-OFF, you're rooted! Good job!
....... if you have access to clockwork, someone could compile an update.zip to replace the spl......
but I'm a noob don't go on my opinion alone...... ask someone responsible for g2root to compile an update.zip for the spl IF you have access to clockwork recovery...
Yes now its s-on and still can be flashed!!
I've never heard before...
to master.peterm:
Now my rom has root... and I've tried the similar way as you said, but when I do the step it seems ok however it doesnt work as I went back into hboot it is still s-on...
I'm very much confused at this point. I know on the mt3gs, they could flash roms with s-on (but, with an eng hboot with test keys and cwm), but doesn't our RUU's all come with official hboots?
I'm not sure if once you're in cwm if it can bypass sig verifications though.
to PanCubano:
That's why I thought I should start a new thread... So strange which conflicts with the conclusion before.
s-on means the system permit no third-party flash right?? As I saw it, it's not right on my phone....backups and new cm rom can be flashed normally but seems that radio cannot be flashed..
And which method of rooting did you use before? Im assuming the rage method with the hacked eng hboot?
the irony of your name and your problem is kinda funny
to thatruth132:
my flashermaster is not this flash but adobe flash...
to PanCubano:
http://forum.xda-developers.com/showthread.php?t=833965
just the usual root method...
First, confirm that you legitimately have root. Download terminal emulator off the market. Open it, type su and hit enter. Superuser should prompt you for permissions. Hit allow and you should see your symbol go from $ to #
If yes, start the rooting method you did from step 2. If that's not the case above, start from step 1.
Since you already were able to sucessfully root the first time around, I still "strongly" suggest you always re-read every step (especially when you get to the dd commands)
Once you finish and can sucessfully confirm S-OFF via rebooting into hboot, come back here and follow the gfree method.
Do not skip out on doing the gfree method. Just because you were able to get s-off again (if you could) it doesn't mean you're done.
Finally I use the unpermroot method to restore the phone into stock state and do the gfree instead to s-off and simunlock the phone...
Thank you all above!! Though there is still no actual explanation of this.
Hello everyone, I have searched all over to try and figure this out on my own but I guess I have failed....lol. I am looking for the stock Rom from HTC desire cellcom usa. Or a way I can remove a stock Rom from the phone its self. I have one rooted and one not rooted and for warranty reasons I need a way to recover it to a state they would not know it was tampered with in the future. I hope that day never comes but I like to be safe. Anyone know of a way I can rip the stock ruu from the unrooted? Or know of a place I can find cellcoms ruu? Any help would be awesome and is greatly appreciated. Thanks in advance.
Sent from my HTC Desire using XDA App
I may have posted that a little hard to understand. Is there a way to take a backup from nandroid and remove the superuser aspect of it and then flash so the phone is restored to stalk? If that was a possibility I would do it and then upload the recovery for other users if they need it for recovery reasons. Second part of my question my fiance has a non rooted desire is there a way I can rip the factory cellcom recovery off of it?
Sent from my HTC Desire using XDA app
You could try it using this method.
http://forum.xda-developers.com/showpost.php?p=6710113&postcount=5
But I have no idea how to remove the custom recovery from your device.
don't know if this will work, haven't tried it, let someone who knows what they're talking about to confirm this (it probably won't work, I made it) and fill in the gaps before you try anything.
The following will (*should*) take you through the process of dumping the stock rom and flashing it to a rooted phone, most of this is from memory from what I read elsewhere, THIS IS NOT A GUIDE - PERFORM AT OWN RISK - UNTESTED!!!
Dump (stock desire):
Find the radio that is installed and download it, look here, in ruu's and OTA's, put it on your pc and call it radio.img
Use visionary to get 'temp root' (don't do a permanent root (not that it will work anyway)).
From adb or terminal emulator run these commands.
Code:
dd if=/dev/mtd/mtd1 of=/sdcard/unroot/recovery.img bs=4096
dd if=/dev/mtd/mtd2 of=/sdcard/unroot/boot.img bs=4096
dd if=/dev/mtd/mtd3 of=/sdcard/unroot/system.img bs=4096
Reboot into fastboot (bootloader) and note what HBOOT it is. This bit I'm unclear on, you will either have to dump the HBOOT somehow or extract it from a RUU (zip), I haven't done either but one of them should be possible.
Put the HBOOT image on your pc and call it hboot.img.
Restore (rooted desire):
s-off the desire if this has not already been done.
boot to recovery and clear ALL userdata.
Over adb (from recovery still) run these commands
Code:
mount /sdcard
flash_image boot /sdcard/unroot/boot.img
flash_image system /sdcard/unroot/system.img
***reboot into android to check it works before flashing recovery***
flash_image recovery /sdcard/unroot/recovery.img
reboot bootloader
From fastboot run 'fastboot flash radio radio.img'
From fastboot run 'fastboot flash hboot hboot.img'
reboot and you should be done.
Notes:
I'm not sure if misc needs to be backed up...can someone clarify.
Wow thanks for such a detailed reply. I will wait until someone else can confirm it is a good plan before prpceeding. It sounds good on paper but I don't want to take any chances lol. I am use to messing with other hardware but phones is a new thing to me. Being region and carrier specific I really don't want to ruin the phone before I have a stable backup to factory and because there are no ruu's for my provider I have to make my own. Thanks again. Hope to get this working so I can post it for other desire owners with my carrier
Sent from my HTC Desire using XDA app
No problem, it's not an entirely selfless act, there is no ruu for my carrier either so I would be very interested to see if this works.
Yeah I hope with one rooted desire and one stock to find a way to get factory recovery working. If so would make things a lot easyer for a lot of people I think
Sent from my HTC Desire using XDA app
If you already have a rooted desire, you can try the steps that mercianary provided. I am not sure, but maybe you don't need s-off because you will flash an "official rom".
Try these two steps
dd if=/dev/mtd/mtd2 of=/sdcard/unroot/boot.img bs=4096
dd if=/dev/mtd/mtd3 of=/sdcard/unroot/system.img bs=4096
Click to expand...
Click to collapse
And then without s-off try to push them with fastboot, you will get an error if it doesn't work, but then it hasn't done anything, so you don't need to worry.
Do all this on your already rooted desire of course. No harm done if it does not work.
If that works, you can try a temproot on your non rooted desire. Then do the same things from adb, then do the steps from fastboot on your already rooted desire (but don't push the recovery yet).
So I dont wanna sound to stupid but phone tweaking is really new to me. Phone was rooted with unrevoked so did not take a lot of skill... If you don't mind could I ask for slightly clearer directions? Thank you so much for the reply and help so far it is greatly appreciated
Sent from my HTC Desire using XDA app
have you flashed any custom roms or did you just use unrevoked?
I only used unrevoked and updated the radio but I am not to worried about the radio part though I bet I could find the official one that it shipped with
Sent from my HTC Desire using XDA app
Hey was just thinking, would someone be able to piece together a stock setup? Say find a normal boot without costume recovery and replace it in a backup, and then remove super user as well? Then flash that and be back to normal?
did you ever get this to work? I'm on Cellcom too and looking to get back to stock. Do you have the software version of the stock Desire that you could share?
It won't work as the signature wouldn't match. Just gotta use a WWE RUU and hope they don't mind
EddyOS said:
It won't work as the signature wouldn't match. Just gotta use a WWE RUU and hope they don't mind
Click to expand...
Click to collapse
Where are those available?
I see on shippedroms.com there is an Alltell RUU. All that I can tell for sure that's the same is the radio. Would this possibly work?
It's the only CDMA RUU ever to leak I think so it should work...branding will be wrong, though
I actually gave up on it lol. But I had to send my phone in for service and just got it back today a month later and they never said a thing about it being rooted and have superuser privileges
Sent from my HTC Desire CDMA using XDA App
Hey,
I rooted my phone and installed Clockwork mod recovery earlier. I'd like to unroot it, and remove the files from the phone. May send it back due to hinge issue.
I'm not sure where to start. I used the rage/gfree/ADB method on the wiki. I'm on 1.34.
Thanks!
Just re-flash the stock 1.34 ROM/RUU, then get temp root and run gfree with the necessary options to go back to S-ON.
Sent from my HTC Desire Z
Kaph said:
Hey,
I rooted my phone and installed Clockwork mod recovery earlier. I'd like to unroot it, and remove the files from the phone. May send it back due to hinge issue.
I'm not sure where to start. I used the rage/gfree/ADB method on the wiki. I'm on 1.34.
Thanks!
Click to expand...
Click to collapse
You can follow the guide on the wiki http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Returning_to_Stock but you can skip the "Install the stock image" part because you still have the stock image.
So just start at "radio S-ON and original CID"
Have fun - Guhl
Like Kaph I'm also trying to return to stock, but when I follow the guide on the wiki I get an error.
After I type in gfree -r /sdcard/part7backup.bin and pressing enter I get the following message:
"Error reading input file."
I'd like to try the other method but I don't know my original CID, is there a way to find that out?
I need to return my phone for warranty so help is much appreciated.
Edit: I've already tried reflashing the ROM, I was always running the stock rom without ota and rooted with rage and gfree.
Yeah I've been trying and I keep getting invalid input file.
Also, is there anyway to revert to stock recovery from Clockwork? I think that's hindering things. Unless that's part of the whole process.
Well after some fun I'm back to S-ON with the stock recovery. I'll try applying the OTA now.
But just a massive thanks to djfoo000 and this thread: http://forum.xda-developers.com/showthread.php?t=909755 as I couldn't get the method on the Wiki to work, but doing it in terminal seems to have done the trick and recovery is now showing S-ON. I also used his recovery.img as the versions matched my phone.
On the bright side I'm now a lot more comfortable with adb/etc heh.
My only other question is will all the gfree files and the like stay on the memory, and if so should I use rm to get rid of them? Or do they get deleted upon reboot?
sorry for what may be a stupid comment but will using the ruu not restore to factory?
The reason i ask is that the wiki has the guide for the tmobile g2 and not desire z?!
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.