so im having a issue with my phone where when i plug the phone in and not always but alot of time just shuts down and boot loops which is why i need to turn s back on so i can send it back into tmobile i tried the one from the true permaroot with the unroot zip and booted to hboot and it continues to say s off does any one know how to fix this?
dfitton said:
so im having a issue with my phone where when i plug the phone in and not always but alot of time just shuts down and boot loops which is why i need to turn s back on so i can send it back into tmobile i tried the one from the true permaroot with the unroot zip and booted to hboot and it continues to say s off does any one know how to fix this?
Click to expand...
Click to collapse
Did you root using the gfree method...?
-Team Inferno
"Quality, not speed"
If you rooted with gfree (and you are), look at the unrooting instructions in gfree thread ("Ultimate S-OFF" in Development section).
yea i used gfree ill look it up and see if it works ty
yea that was the same one i tried before it didnt work
Did you load the original 2.2.1 firmware on the phone, temp-rooted it, and executed gfree with the right flag to make it turn the S-ON back?
I guess you didn't, otherwise it would work.
Please do now.
Jack_R1 said:
Did you load the original 2.2.1 firmware on the phone, temp-rooted it, and executed gfree with the right flag to make it turn the S-ON back?
I guess you didn't, otherwise it would work.
Please do now.
Click to expand...
Click to collapse
How would you execute gfree with the right flag that would make it turn on?
Please read the thread I mentioned in the first of my posts above.
Related
How do I COMPLETELY unroot EVO to send back to Sprint
Like s-off s-on plz help
If you rooted using Unrevoked 3.21 there is a thread listed in Android Development explaining the process as well as the needed links to download the needed zip files to turn S-On and the zip file to restore back to Stock Froyo 2.2
SouthernEvo said:
If you rooted using Unrevoked 3.21 there is a thread listed in Android Development explaining the process as well as the needed links to download the needed zip files to turn S-On and the zip file to restore back to Stock Froyo 2.2
Click to expand...
Click to collapse
Tbd but I used toast.method to root that used a lot of adb
mccurt29 said:
Tbd but I used toast.method to root that used a lot of adb
Click to expand...
Click to collapse
Ok but there are still methods in the forum for unrooting just like how you rooted. I would just do a search for them and choose which one you feel is the easiest for you to understand. Also if you are getting another EVO unrevoked 3.21 is as many in here have said easy peasy for rooting.
Good luck
playya said:
Ok but there are still methods in the forum for unrooting just like how you rooted. I would just do a search for them and choose which one you feel is the easiest for you to understand. Also if you are getting another EVO unrevoked 3.21 is as many in here have said easy peasy for rooting.
Good luck
Click to expand...
Click to collapse
Thanks!......
You need to run the RUU.exe found in the Dev section. It will do the trick.
Sent from my PC36100 using XDA App
novanosis85 said:
You need to run the RUU.exe found in the Dev section. It will do the trick.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Precisely. It can be found here:
*OFFICIAL* RUU_SuperSonic_S_Sprint_WWE_3.29.651.5_Radio_2.15. 00.09.01_NV_1.77_CNV_rel.
One thing to check first: do you have S-OFF? This would be the case if you ever ran Unrevoked Forever or Unrevoked 3.21. If so, you'll need to flash the Unrevoked Forever S-ON tool from recovery before running the RUU.
Noxious Ninja said:
Precisely. It can be found here:
*OFFICIAL* RUU_SuperSonic_S_Sprint_WWE_3.29.651.5_Radio_2.15. 00.09.01_NV_1.77_CNV_rel.
One thing to check first: do you have S-OFF? This would be the case if you ever ran Unrevoked Forever or Unrevoked 3.21. If so, you'll need to flash the Unrevoked Forever S-ON tool from recovery before running the RUU.
Click to expand...
Click to collapse
Thx guys I never used unrevok just toast methods but how do u check the A-on thing & should it be on or off
Also this 1 guy on this forum said he used the ruu & had s-on/off but Sprint still found out he rooted so should I wipe that ex--- >#366# stuff too?
mccurt29 said:
Thx guys I never used unrevok just toast methods but how do u check the A-on thing & should it be on or off
Also this 1 guy on this forum said he used the ruu & had s-on/off but Sprint still found out he rooted so should I wipe that ex--- >#366# stuff too?
Click to expand...
Click to collapse
Reboot into the bootloader (turn phone off, then hold power+volume down until it comes on). Then look at the end of the first line.
If it says SHIP S-ON, you're good.
If it says SHIP S-OFF, you need to run the Unrevoked tool.
If it says ENG S-OFF (which should be the case if you used Toast's method), it is indeterminate.
However, if you never used Unrevoked at all, you shouldn't have to worry about it. You can check after you run the RUU, which will reset it to the SHIP bootloader.
I believe the 3.29 RUU resets everything, including the PRI. Toast's method downgraded the PRI, and it was difficult to get it back before the current update, so this used to be a sure-fire way of telling whether you had rooted. Unless you had a bad Wimax flash and broke your 4G, I *think* you should be OK. But I don't know for sure.
Noxious Ninja said:
Reboot into the bootloader (turn phone off, then hold power+volume down until it comes on). Then look at the end of the first line.
If it says SHIP S-ON, you're good.
If it says SHIP S-OFF, you need to run the Unrevoked tool.
If it says ENG S-OFF (which should be the case if you used Toast's method), it is indeterminate.
However, if you never used Unrevoked at all, you shouldn't have to worry about it. You can check after you run the RUU, which will reset it to the SHIP bootloader.
I believe the 3.29 RUU resets everything, including the PRI. Toast's method downgraded the PRI, and it was difficult to get it back before the current update, so this used to be a sure-fire way of telling whether you had rooted. Unless you had a bad Wimax flash and broke your 4G, I *think* you should be OK. But I don't know for sure.
Click to expand...
Click to collapse
thanx that did the trick now to the sprint store tomorrow wish me luck
If your still having trouble then try this:
http://forum.xda-developers.com/showthread.php?t=780141&highlight=unroot
I just unrooted mine last night and it only took me 5 mins, just flash the unrevoked and then do the update on the PC36IMG and thats it.
Today I accidently turned it on (the thing in the bootloader) and now I can't turn it off no matter what so I can do a revert to stock .img, I used the PDI15.img or w.e that would revert back to stock forgetting that I had the newest radio and now I can't revert to stock or turn S-OFF. Please help
Current Configurations:
GLACIER PVT SHIP S-ON
HBOOT - 0.86.0000
MICORP - 0429
RADIO - 26.09.04.26_M
eMMC - BOOT
More Info:
When I use a PDIMG or w/e file it errors out as being old
Can you still boot? Like into your rom? If so just try rooting using visionary and using a root explorer to push the gfree files to data/local/ then just follow the normal rooting procedure
Sent from my HTC Glacier using XDA Premium App
Nicgraner said:
Can you still boot? Like into your rom? If so just try rooting using visionary and using a root explorer to push the gfree files to data/local/ then just follow the normal rooting procedure
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Yeah I can still boot into my rom, bootloader, and recovery and okay will try that
EDIT: Okay I did, I tried turning S-OFF but it says something about eMMC power cycle failed
XxKOLOHExX said:
Yeah I can still boot into my rom, bootloader, and recovery and okay will try that
EDIT: Okay I did, I tried turning S-OFF but it says something about eMMC power cycle failed
Click to expand...
Click to collapse
dude! I noticed this also this morning. I am rooted(using setcpu and root explorer just fine) but in hboot it says s=on. I was also wanting to flash the stock .img and start fresh. thought I was the only one having this problem. tried everything you did and got the same results.
What ROM are you on? AFAIK, gfree, requires the stock kernel to do what it does. How on earth did you turn S-ON? That sort of thing shouldn't just happen out of nowhere.
How is the progress on fixing your phone?
jdkoren said:
What ROM are you on? AFAIK, gfree, requires the stock kernel to do what it does. How on earth did you turn S-ON? That sort of thing shouldn't just happen out of nowhere.
Click to expand...
Click to collapse
currently on Evil D mTGB v1.0, Faux 0.0.7 CFS lv leak kernel. everything works fine, no FC's or anything. just having the same issues as XxKOLOHExX. I really have no idea how it turned on by itself, I dont remember doing anything out of the ordinary
I was trying to get back to stock from the rom i was on. (MIUI) and when I used the stock .img though the bootloader it went all good till it rebooted, then it said failed because the file was old and now I am stuck with s-on and I don't know how to turn it off
How did you get to the stock bootloader? Did you have eng bootloader at one point? What meth of root did you use? Alot of info missing.
Now download the stock radio.img and push it via adb or just download the PD15IMG.zip (radio only not rom included). Once this is done you can revert back to stock rom/radio using standard PD15IMG.zip (radio+rom). Now depending on the type of root you used it would depend if you still have radio flag on/off even if your reverted back to stock bootloader.
PS: You can get PD15IMG.zip (stock radio) from master radio thread and PD15IMG.zip (stock radio/rom) by doing search.
PermROOT said:
How did you get to the stock bootloader? Did you have eng bootloader at one point? What meth of root did you use? Alot of info missing.
Now download the stock radio.img and push it via adb or just download the PD15IMG.zip (radio only not rom included). Once this is done you can revert back to stock rom/radio using standard PD15IMG.zip (radio+rom). Now depending on the type of root you used it would depend if you still have radio flag on/off even if your reverted back to stock bootloader.
PS: You can get PD15IMG.zip (stock radio) from master radio thread and PD15IMG.zip (stock radio/rom) by doing search.
Click to expand...
Click to collapse
It flashed the bootloader when I flashed the PD15IMG.zip, it just stop when I did the whole procedure. Nope never flashed an Engineer Bootloader. I used theunlockr.com sites method
I tried that, it uziped then tried to flash the radio then just went back to the original menu for the bootloader
If you used the VISIONary+ (TempROOT) and root.sh (PermROOT) meth then you already had engineering hboot (0.85.2007) pushed though terminal on "/dev/block/mmcblk0p18". Now you did something in between is what I would like to know.
As you flashed new radio (26.09.04.26_M) which I am clear. But what I like to know is how did you end up with default hboot (0.86.0000)? If you had S=OFF you didn't lose it via flashing new radio. Which PD15IMG.zip did you install? Now when you say PD15IMG.zip what do you mean? It can be anything as its default mt4g system based image. Stock PD15IMG.zip = (Sense 2.2.1 Rom/Radio 26.03.02.26_M). Did you install leaked PD15IMG.zip from Panache? or GB2.3.3S?
Are you not 1 of the Royal dev's? who try to take over Silence's IG if I recall. I am just assuming here but this is why you do "NOT" dump system image via hboot. What you should have done was do complete total system wipe (format /data; /system) and then flash new edify based CWMR flashable rom.
PermROOT said:
If you used the VISIONary+ (TempROOT) and root.sh (PermROOT) meth then you already had engineering hboot (0.85.2007) pushed though terminal on "/dev/block/mmcblk0p18". Now you did something in between is what I would like to know.
As you flashed new radio (26.09.04.26_M) which I am clear. But what I like to know is how did you end up with default hboot (0.86.0000)? If you had S=OFF you didn't lose it via flashing new radio. Which PD15IMG.zip did you install? Now when you say PD15IMG.zip what do you mean? It can be anything as its default mt4g system based image. Stock PD15IMG.zip = (Sense 2.2.1 Rom/Radio 26.03.02.26_M). Did you install leaked PD15IMG.zip from Panache? or GB2.3.3S?
Are you not 1 of the Royal dev's? who try to take over Silence's IG if I recall. I am just assuming here but this is why you do "NOT" dump system image via hboot. What you should have done was do complete total system wipe (format /data; /system) and then flash new edify based CWMR flashable rom.
Click to expand...
Click to collapse
Yeah I know that, I Was trying to go back to stock everything using the unrooting method(PD15IMG.zip). Using this file I was able to get through the first step and it rebooted, then it went back to bootloader and now it won't take the PD15IMG.zip saying that it is an older file. Yes I am one of the devs, That's why before posting I tried everything I could think of, gfree, old unrooting methods, etc. I didn't use a dump lol I'm not that noobish haha
Thats where you got owned as the PD15IMG.zip (stock rom/radio) just reverted back to hboot (0.86.0000) from eng hboot (0.85.2007). While you attempted to go further you couldn't do to security turning on (S=ON). Now this normally wouldn't be problem but since you had newer radio (26.09.04.26_M) it wouldn't replace it with old.
All you had to do was follow few simple meths which you should have learned it over the years. Go back same way you came by first reverting back to original radio image and then after doing complete system wipe you should have reverted back to original factory based via stock pd15img.
Ill post back with solution soon let me think this out. I don't want to brick your phone trying to manually push the radio.img nor the eng_hboot.img. As if you try to push radio now would fail on write and give you hard brick. Since S=ON and if you try to push eng_hboot.img who knows what will happen as no R/W access on mmcblk could could also fail thus giving bad flash which can also brick the device. Ill see what happens and post back at... you folks just made more extra work for me.
PermROOT said:
Thats where you got owned as the PD15IMG.zip (stock rom/radio) just reverted back to hboot (0.86.0000) from eng hboot (0.85.2007). While you attempted to go further you couldn't do to security turning on (S=ON). Now this normally wouldn't be problem but since you had newer radio (26.09.04.26_M) it wouldn't replace it with old.
All you had to do was follow few simple meths which you should have learned it over the years. Go back same way you came by first reverting back to original radio image and then after doing complete system wipe you should have reverted back to original factory based via stock pd15img.
Ill post back with solution soon let me think this out. I don't want to brick your phone trying to manually push the radio.img nor the eng_hboot.img. As if you try to push radio now would fail on write and give you hard brick. Since S=ON and if you try to push eng_hboot.img who knows what will happen as no R/W access on mmcblk could could also fail thus giving bad flash which can also brick the device. Ill see what happens and post back at... you folks just made more extra work for me.
Click to expand...
Click to collapse
Thank you so much for the help
PermROOT said:
Thats where you got owned as the PD15IMG.zip (stock rom/radio) just reverted back to hboot (0.86.0000) from eng hboot (0.85.2007). While you attempted to go further you couldn't do to security turning on (S=ON). Now this normally wouldn't be problem but since you had newer radio (26.09.04.26_M) it wouldn't replace it with old.
All you had to do was follow few simple meths which you should have learned it over the years. Go back same way you came by first reverting back to original radio image and then after doing complete system wipe you should have reverted back to original factory based via stock pd15img.
Ill post back with solution soon let me think this out. I don't want to brick your phone trying to manually push the radio.img nor the eng_hboot.img. As if you try to push radio now would fail on write and give you hard brick. Since S=ON and if you try to push eng_hboot.img who knows what will happen as no R/W access on mmcblk could could also fail thus giving bad flash which can also brick the device. Ill see what happens and post back at... you folks just made more extra work for me.
Click to expand...
Click to collapse
lol sorry for the extra work, just dont wanna have the chance of bricking my phone but like XxKOLOHExX I wanted to revert back to stock from mTGB using the stock PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60.140e_26.03.02.26_M_release_155771_signed. everything he described is happening to me also, step by step. I rooted with the visionary+ and permroot method(unlockr). I did download and flash the 26.08.04.30 radio. heres what I see in hboot
GLACIER PVT SHIP S-ON
HBOOT-0.86.0000
MICROP-0429
RADIO-26.08.04.30_M3
eMMC-boot
Sep 27 2010, 11:12:59
so what youre saying is that we should try flashing the stock radio first, wipe the whole phone(including sdcard?), then flash the stock PD15IMG? Ill give it a shot real quick, thanks
*edit* hboot wont even let me flash the stock radio, itll say checking but wont actually let me update it
Well clarknick27 the problem here is that root.sh to gain PermROOT via VISIONary+ just push the 0.85.2007 eng hboot and giving temporary S=OFF, the true security flag as we know it is controlled in the radio. So when you try to revert back using stock PD15IMG (rom/radio) it reverted back to the stock 0.86.0000 hboot thus turning on the security flag on.
What you all should have done is reverted back same way you installed it. Which would have been first use PD15IMG.zip (stock radio) and then use stock PD15IMG.zip (radio/rom). I still need some sleep lol I just wokeup after sleeping 2hours.
The MT4G I tested on I rooted it via VISIONary+ and then flashed GB Leak rom not the PD15IMG.zip (leak radio/rom) which contained the 0.89.0005 hboot. So after flashing stock radio PD15IMG.zip (radio 26.03.02.26_M) I was able to flash stock PD15IMG.zip (rom/radio) without problem. Which is same as I suspected even after S=ON due to same version radio no problem. If I had newer radio after that point it would be locked out. Let me go to sleep and wakeup and ill see what happens from there. As I have clean MT4G ill have to reroot it first.
BTW XxKOLOHExX and clarknick27 just in case my account gets disabled. Do the following and report it here and ill see from there.
1) Which working rom you currently have installed on the device?
I know trying to reroot using gfree may give you similar result as my test: http://forum.xda-developers.com/showthread.php?t=1066966 < not important but unable to root on newer rom.
2) What happens when you try to reroot it using VISIONary+ (TempROOT) and root.sh (PermROOT)?
Did you try it? If so what is the end result? so post back. Ill check and go from there.
PermROOT said:
BTW XxKOLOHExX and clarknick27 just in case my account gets disabled. Do the following and report it here and ill see from there.
1) Which working rom you currently have installed on the device?
I know trying to reroot using gfree may give you similar result as my test: http://forum.xda-developers.com/showthread.php?t=1066966 < not important but unable to root on newer rom.
2) What happens when you try to reroot it using VISIONary+ (TempROOT) and root.sh (PermROOT)?
Did you try it? If so what is the end result? so post back. Ill check and go from there.
Click to expand...
Click to collapse
1) currently running Evil D's mTGB v1.0 rom with Faux's 0.0.7 CFS LV leak kernel. tried rooting with visionary and terminal first, no success. I then tried out the gfree method, and got "Attempting to power cycle eMMC...failed. Module failed to load: No such file or directory."
2) I installed Visionary using Astro file manager, then run Visionary. I click on "temproot now" and it starts, but then the screen goes black and doesnt do anything. I have let it sit on the black screen for well over 15mins before with no luck. I can click on "attempt to permroot" and it will ask for permissions and reboot and everything. my s=on but I still have root access and 0.86.000 bootloader. this is what I see using terminal before rebooting to see if s=off
Did you do the Radio S=OFF using gfree? If so that would explain why you still have root as security is disabled on the device totally. If thats the case then just push the eng bootloader manually via adb or though terminal and reboot. For now XxKOLOHExX is locked lets see what I find ill post back for him.
PermROOT said:
Did you do the Radio S=OFF using gfree? If so that would explain why you still have root as security is disabled on the device totally. If thats the case then just push the eng bootloader manually via adb or though terminal and reboot. For now XxKOLOHExX is locked lets see what I find ill post back for him.
Click to expand...
Click to collapse
thanks for taking the time to help out, Ill give it a shot
*edit* just tried pushing the eng bootloader through adb and it didnt stick or flash, rebooted into hboot and it still says 0.86.0000, s=on, 26.08.04.30_M3 radio
Device doesn power on after pwr off. on power on vibrates 3 times & orange LED flash
ok. here goes.
On rebooting my phone last night it doesnt come back on. It vibrates 3 times and the LED flashes orange.
The only way it comes back on is if i take out the battery for a while and then power it on again.
here is a chronology of what happens.
reboot or power down
devices powers off but doesnt restart. vibrates 3 times and the LED flashes orange.
pull out the battery and SDCARD and wait a minute.
After this I can now boot into CM7
Reboot or power off to restart. same thing happens again
this happens everytime i power down the device
things i have noticed
on plugging it into my PC it recognises my device as a qualcomm_cdma_technologies msm desire and tries to install drivers for it.
this is the first time i have seen this. My device is GSM based and i am on tmobile UK.
Device can never power back on immediately from power off. just vibrates 3 times, LED flashes. Only comes back when i pull battery and SD and wait a few seconds before powering it back on
What i have tried but they all dont solve it
flashing a new cwm recovery. i am able to flash a new one from rom manager but doesnt solve the problem. currently on Rom manager 4.2.0.2 and CWM 3.0.2.6
formatting my SDCARD through ROM Manager.
doing a full wipe and reflashing stable CM7.
all of these completed successfully with no errors
What i can do successfully
i can boot into bootloader and recovery from commandprompt or using the power+volume down combination. doesnt always power on because of the no boot (start) problem .
i can do "adb devices" and successfully see my device as HT0****** in the list of devices
On the terminal app, on typing "su" it gains root permission successfully.
i can succesfully access my SDCARD using astro and also using mount usb storage in recovery.
device information
HTC DEsire hd.
CM7.0.3 stable, previously on nightly CM_ace_full 83
ROM manager version 4.2.0.2
CWM 3.0.2.6
Radio 26.09.04.11_M2
hdboot-0.85.2007 (PD9810000)
ACE PVT ENG S-OFF
USBdebugging always on
please let me know if any further information is needed and how to get it.
I really need some help. I have trawled the forums and i am starting to believe that i have a partially bricked device or a usb brick. I havent seen any real solutions or any post with a problem like mine so i want to be sure that that is the issue before trying the fixes there. Is there any thread for fixing a Desire HD USB brick, because all the ones i have seen do not have a definite fix.
Hi,
I think you maybe close to hardware failure. I would perform a full backup of apps & data and restore a HTC RUU (1.32.405.6). Then if your problem still persists send it away for repair.
andyharney said:
Hi,
I think you maybe close to hardware failure. I would perform a full backup of apps & data and restore a HTC RUU (1.32.405.6). Then if your problem still persists send it away for repair.
Click to expand...
Click to collapse
Thanks andy.
In flashing the HTC RUU. is that the process of removing root?. because i was thinking of removing root and then sending it back. but thought there might be a software fix for it i could try first.
Yes, flashing via RUU will remove root and ENG S-OFF. It will not restore Radio S-ON. It's probably advisable to use jkoljo's Radio S-OFF tool again to restore it and CID:HTC__001.
andyharney said:
Yes, flashing via RUU will remove root and ENG S-OFF. It will not restore Radio S-ON. It's probably advisable to use jkoljo's Radio S-OFF tool again to restore it and CID:HTC__001.
Click to expand...
Click to collapse
im vey sorry andy. im now so scared of making this worse.
i have found jkoljos post here http://forum.xda-developers.com/showthread.php?t=857537 and i am going to try the instructions there but i do not understand the CID part. because after flashing the ruu i am supposed to do a temp root. id i remember correctly temp rppt reverts back to stock after reboot. or do i have to flash the RUU again.
sorry for the questions. havent had any sleep all night because of this and i am quite scared i will make it worse. i am going to do it now and will let you know.
santet said:
im vey sorry andy. im now so scared of making this worse.
i have found jkoljos post here http://forum.xda-developers.com/showthread.php?t=857537 and i am going to try the instructions there but i do not understand the CID part. because after flashing the ruu i am supposed to do a temp root. id i remember correctly temp rppt reverts back to stock after reboot. or do i have to flash the RUU again.
sorry for the questions. havent had any sleep all night because of this and i am quite scared i will make it worse. i am going to do it now and will let you know.
Click to expand...
Click to collapse
I recently had to send mt phone back to HTC. What I did was flash the RUU, temproot and revert to stock CID (don't know why I didn't do this first) then flash the RUU again just to make absolutely sure that all was well.
Yeah I would use the tool to change Radio S-OFF to ON and restore the CID before you run the RUU. You will save yourself a lot of time and effort.
ok. on first try i already have a problem. i downloaded the easy radio tool.
connected my device with usb debugging on. run the application as administrator. clicked on Stock CID (my device is unbranded desire hd) started up, notified as pushing file to sd. reurned with unknown error, probably connection.
i tried the same with Radio S-On. same response.
i am doing this before flashing the new RUU i downloaded which is version RUU_Ace_HTC_WWE_1.32.405.3_Radio_12.28b.60.140e_26.03.02.15_M3_release_155032_signed.zip.
what have i done wrong?
Don't panic your ok,
It just means you will have to run the RUU first then run Visionary+(r14) to get temp root then run the Radio S-OFF tool.
I have gone through all the steps with no glitches. How do i verify that my device no more has radio S-On and is fully returned to stock enough so as not to voide warranty. I have the stock ROM installed.
I also want to try updating using the recent OTA update and use the device a while to see if the problem returns before returning it to HTC.
If you temp rooted, then ran the Radio S-OFF tool to go back to S-ON and CID: HTC__001 then you are good to go. You are completely stock, do some testing to see if your reboot problem persists.
andyharney said:
If you temp rooted, then ran the Radio S-OFF tool to go back to S-ON and CID: HTC__001 then you are good to go. You are completely stock, do some testing to see if your reboot problem persists.
Click to expand...
Click to collapse
Funny enough no more problem of being unable to reboot.
I have installed titanium.
i want to update to the latest OTA 2.3 update for the desirehd. do you know if the visioinary root and the the easy radio tool for s-off work after that update which i believe is the latest one.
I will use the device in its stock condition for two mpore days and if i do not have any more issues then im going to install a custon rom once again.
Thanks loads for all the help.
If you upgrade to 2.3 (2.36.405.x) then Visionary+ no longer works, you have to use GingerBreak instead. You can still downgrade to an earlier firmware.
I tried rooting again using visionary. got the same problem after applying permroot and then using the easy radio tool for S-OFF. After applying permroot it booted fine. But after applying S-OFF and SUperCID it goes back to same error and doesnt boot again. It seems then that it has something to do with the rooting process.
I will post a new thread asking if anyone has been unable to complete the S-OFF and SUPERCID process .
Why did you apply permroot? I said temproot, you don't want to make persistent changes. See if you can undo the permroot, there is a button to do it.
andyharney said:
Why did you apply permroot? I said temproot, you don't want to make persistent changes. See if you can undo the permroot, there is a button to do it.
Click to expand...
Click to collapse
I did exactly as you said using temproot so as to be able to turn apply S-OFF and the stock CID.
but after i did that and it worked i just tried rooting once again permanently and had the same issue. I have updated to the OTA update and i will use that for a while as when reading the gingerbreak threads people do not seem to trust that it works fine.
I just re-read my last post, sorry if I came across as a d*ck, that was not the intent.
I would remain stock for a few days to see if that has an affect. If rooting is the cause of your issue, I doubt HTC will repair it because it has booting problems once rooted.
I looked all over the place and cant find anything like my situation!
Ok so i called t-mobile and they are sending me a replacement because of the bad screen on my phone. All in all i used a method from CM7 to root my phone. I dont remember what method it was. I remember that i had to downgrade my phone and then root from there.
I am trying to get S-on because i already flashed the PD15IMG and it didnt give me the s-on. it just keeps saying s-off. do i have to have s-on for the excahnge? i already have the phone with the stock rom without root.
PLEASE HELP! thanks!!!!
If you used gfree you can run the script again restore S-ON if you still have the part7 backup files. If you don't have them, there is a thread around here somewhere that has the files with instructions to hex-edit your IMEI.
If you used root.sh, then you simply need to run unroot.sh
Edit: I came to the conclusion that if you looked and couldn't manage to find the gfree thread stickied at the top of the dev section that you would never find the thread about hex-editing part7backup. So here: http://forum.xda-developers.com/showthread.php?t=1195630
estallings15 said:
If you used gfree you can run the script again restore S-ON if you still have the part7 backup files. If you don't have them, there is a thread around here somewhere that has the files with instructions to hex-edit your IMEI.
If you used root.sh, then you simply need to run unroot.sh
Sent from my Glacier using XDA
Click to expand...
Click to collapse
I dont think i used gfree because i used adb and my computer to root it
http://wiki.cyanogenmod.com/wiki/HTC_Glacier:_Full_Update_Guide
THIS IS WHAT I USED!
:sigh: The last set of steps had you use ADB to push gfree to the phone. So yes, you used gfree.
Go to the dev section and look at the gfree guide stickied there. It has steps to unroot and 5000 people asking questions when they run into snags during the process. Read until your eyes bleed, then read some more.
estallings15 said:
:sigh: The last set of steps had you use ADB to push gfree to the phone. So yes, you used gfree.
Go to the dev section and look at the gfree guide stickied there. It has steps to unroot and 5000 people asking questions when they run into snags during the process. Read until your eyes bleed, then read some more.
Click to expand...
Click to collapse
thank you so much man !!!
i dont understand it! please help?
Please help
okay i have tried everything i could think of and i still cant figure this out!
the problem is that i flashed the PD15IMG via hboot and it put everything back to stock. now the problem is that S is still off and i need s-on to send it back for a replacement. i have tried re rooting the phone from the guide i posted above but i have had no success CAN ANYONE PLEASE HELP!?
i have the stock rom that is GB but without root or anything i cant even get temp root! please help me!
If your on gingerbread (2.3) you'll have to downgrade back to 2.2.1 before you can run gfree to turn
S-on.
After turning S-on reflash a stock pd15.img and you'll be back to stock.
For more info read the rooting guide in the sticky section. I think its the one by grankin01. Its the one that says check this out even if your rooted.
Sent from my Glacier using XDA
I have followed this guide http://forum.xda-developers.com/showthread.php?p=25372466&highlight=s-off+still#post25372466 to the roots of it and i still cant get s-on! Any one willing to help?! after i do the last step it still says s-off but this time with 85.000 hboot! do i have to flash the PD15IMG so i can have s-on after that last step?!
OKAY! i did the type ./gfee --secu_flag on" now if i redo the PD15IMG will i have s-on?!!?!?!
Did you restore the part7backup?
Sent from my HTC Glacier using XDA
Part7backup doesn't matter much. If gfree was run and pd15img will be flashed after it, S-ON will be restored.
Jack_R1 said:
Part7backup doesn't matter much. If gfree was run and pd15img will be flashed after it, S-ON will be restored.
Click to expand...
Click to collapse
So what's his problem then? I'm not being sarcastic. If he got S-OFF with gfree and used gfree to turn the security flag back on, then...?
With Eng HBOOT the security flag isn't being checked - so he sees S-OFF even though the flag itself might be ON. PD15IMG with stock bootloader will revert his HBOOT to stock, which will reflect the actual flag status.
You guys were great help but I tried everything on what you guys showed me. But nothing seemed to work.. I sent the phone back unrooted but the flag still said s-off even without the eng boatloader... They sent me a replacement mt4g and it had the same issue with the screen being washed off. I talked with them (someone hung up on me twice, pissed me off) and they decoded to send me the sensation 4g. I am now going to be here and there trying to port good roms for you guys to enjoy on the mt4g! By the way, sense 3.6 on HTC isn't that different. Don't get too excited about it folks... Well thanks a lot for you're help ladies and gentlemen! Gcashiel singing off.
Ps. Pm Me if you like any sensation roms for me to port over!