Is there any way to achive s-off with android 2.3.7 running on my mytouch 4g
Sent from my GT-N7000 using XDA App
I didn't even know the my touch received an android update that high. Thought it was just 2.3.4 update.
I'm guessing that's what he meant. If there is a way, its unknown to the XDA community. You will need to downgrade to 2.2.1
No, there isn't such way. As pointed out before me, you need to downgrade.
Jack_R1 said:
No, there isn't such way. As pointed out before me, you need to downgrade.
Click to expand...
Click to collapse
can not seem to downgrade from this its the miuicecreamed rom witch is a hybrid rom and all downgrade atemps have failed i have root and cwm boot unable to downgrade cant flash new rom because of s-on and when trying to use PD15IMG it just says currant version is newer update cancled
ttibbetts83 said:
can not seem to downgrade from this its the miuicecreamed rom witch is a hybrid rom and all downgrade atemps have failed i have root and cwm boot unable to downgrade cant flash new rom because of s-on and when trying to use PD15IMG it just says currant version is newer update cancled
Click to expand...
Click to collapse
Wait, what? So you're on a custom rom? How is it that you're on a custom rom but you're s-on? I see now why stated you're on 2.3.7. How did you flash the miui rom in the first place?
If you have CWM just flash a different rom, if that fails just download the gfree files and use them to turn S-OFF because MIUI has root privileges built in. There really isn't a reason why you should be downgrading in the first place.
coupetastic-droid said:
Wait, what? So you're on a custom rom? How is it that you're on a custom rom but you're s-on? I see now why stated you're on 2.3.7. How did you flash the miui rom in the first place?
Click to expand...
Click to collapse
i had s-off and some how got s-on back
Nicgraner said:
If you have CWM just flash a different rom, if that fails just download the gfree files and use them to turn S-OFF because MIUI has root privileges built in. There really isn't a reason why you should be downgrading in the first place.
Click to expand...
Click to collapse
What he said. If you're running a custom ROM - you can run gfree at any time and achieve S-OFF.
Nicgraner said:
If you have CWM just flash a different rom, if that fails just download the gfree files and use them to turn S-OFF because MIUI has root privileges built in. There really isn't a reason why you should be downgrading in the first place.
Click to expand...
Click to collapse
if i flash with cwm it just boot loops at splash screen and ive tried gfree, and everything works intell i run the scrip and it fails to reset emmc and when reset the phone it does not change anything i have tried all the ways in these fourms that i can find but none have worked and i think gfree is not working because u need 2.3.4 for it to work and was trying to downgrade to get simunlock with gfree
Ok, in this case use the downgrading guide, found in Glacier Wiki, under section "Root", subsection "Gingerbread". Link to Wiki in my signature.
Since you have root on MIUI, you can skip the first "achieving temp root" part, and go straight to writing misc_version and loading PD15IMG.
Jack_R1 said:
Ok, in this case use the downgrading guide, found in Glacier Wiki, under section "Root", subsection "Gingerbread". Link to Wiki in my signature.
Since you have root on MIUI, you can skip the first "achieving temp root" part, and go straight to writing misc_version and loading PD15IMG.
Click to expand...
Click to collapse
i have tried that when a run # ./misc_version -s 1.00.000.0 it says permission denied
How did you get s-on and keep your current rom with root privileges? did you flash a pd15img that didnt include the rom?
If it says "permission denied" - verify that the file is set to correct permissions (chmod 777 misc_version), and that you're in correct folder. You're failing to follow the guide correctly, but the guide WILL work once you do.
Jack_R1 said:
If it says "permission denied" - verify that the file is set to correct permissions (chmod 777 misc_version), and that you're in correct folder. You're failing to follow the guide correctly, but the guide WILL work once you do.
Click to expand...
Click to collapse
i will try again
Jack_R1 said:
If it says "permission denied" - verify that the file is set to correct permissions (chmod 777 misc_version), and that you're in correct folder. You're failing to follow the guide correctly, but the guide WILL work once you do.[/QUO
still no go ive tried gfree, root.sh and visanory none seem to do anything guess im stuck
Click to expand...
Click to collapse
ttibbetts83 said:
Jack_R1 said:
If it says "permission denied" - verify that the file is set to correct permissions (chmod 777 misc_version), and that you're in correct folder. You're failing to follow the guide correctly, but the guide WILL work once you do.[/QUO
still no go ive tried gfree, root.sh and visanory none seem to do anything guess im stuck
Click to expand...
Click to collapse
flash the stock 2.2.1 update through bootloader and reroot.
Click to expand...
Click to collapse
coupetastic-droid said:
ttibbetts83 said:
flash the stock 2.2.1 update through bootloader and reroot.
Click to expand...
Click to collapse
when i try to flash that it says main version older update failed unless there is a differant file i have not found that will override all that
Click to expand...
Click to collapse
Related
Paul released Visionary R14 "with r/w"
I used it on a fresh S-ON stock ROM and it roots OK, I tick "mount r/w" and seems OK
Then I boot to bootloader and I see "S-ON", BUT I CAN enter Clockwork and flash my nandroid back
Has somebody else tested it ??
With r/w achieved, seems S-OFF will not be necessary anymore ??
This will save many noobs from bricking their phones
OOpen for discussion
gtrab said:
Paul released Visionary R14 "with r/w"
I used it on a fresh S-ON stock ROM and it roots OK, I tick "mount r/w" and seems OK
Then I boot to bootloader and I see "S-ON", BUT I CAN enter Clockwork and flash my nandroid back
Has somebody else tested it ??
With r/w achieved, seems S-OFF will not be necessary anymore ??
This will save many noobs from bricking their phones
OOpen for discussion
Click to expand...
Click to collapse
Weird.
I'd prefer S-OFF though. Dunno why, just an engineering hboot seems better to me. Like the splash screens. And stuff.
so I can use visionary now instead of S-OFF and install roms and all is that the case?
Problem is you need S-OFF to flash clockwork,
so as long as the ROM you flash doesn't contain a recovery...
That's why this thread is up for discussion, I'd like to hear comments and experiences.
I'd stick to S-OFF in the mean time.
gtrab said:
Problem is you need S-OFF to flash clockwork,
Click to expand...
Click to collapse
...but when you first install the ENG HBOOT you flash it at this point (via dd) - so is the recovery partition not writable but the HBOOT is?
I just do not get the difference between temp root, and then enabling temproot on boot, and permanent root.
I mean if you temp root and then enable temproot on boot, the device will be root every time, so why should you perm root?
Can anyone answer me?
Thanks in advance
buzmay said:
I just do not get the difference between temp root, and then enabling temproot on boot, and permanent root.
I mean if you temp root and then enable temproot on boot, the device will be root every time, so why should you perm root?
Can anyone answer me?
Click to expand...
Click to collapse
I'm sure someone else will have a better answer, but from my own point of view, with the temp root, you haven't properly rooted it really. The phone effectively hasn't been rooted, but you're rooting it specifically every time you boot up, because any writes to the system aren't being saved in permanent storage, only in cache memory (lost when shut down). What if something goes wrong with that process ?
Seems to me it's much better to have the rooting actually written to the phone's permanent storage (NAND).
steviewevie said:
I'm sure someone else will have a better answer, but from my own point of view, with the temp root, you haven't properly rooted it really. The phone effectively hasn't been rooted, but you're rooting it specifically every time you boot up, because any writes to the system aren't being saved in permanent storage, only in cache memory (lost when shut down). What if something goes wrong with that process ?
Seems to me it's much better to have the rooting actually written to the phone's permanent storage (NAND).
Click to expand...
Click to collapse
Thanks for the answer, what if something goes wrong? isn't this method currently the safest?
I was just wonder, because I would like to root my desire z but seems to be quite unstable still with the methods availble, and until there is no ROM that supports A2SD then I do not see a reason for either perm root or S-Off.
So that is why I was wondering.
Gtrab, I've updated to version Visionary r14 and then enabled the new option for R/W, restarted and I still have S-OFF and the ClockWorkMod.
I use root explorer to make changes to the /system partition, it allows to mount it r/w so I think I'm going to disable this on boot option for security...
Have you flashed the stock hboot earlier or did some changes/testing prior the update of this program?
EDIT: here's the link of the Visionary app thread with the description, maybe it can answer some questions.
http://android.modaco.com/content/h...m/322658/19-nov-r14-visionary-one-click-root/
zuachs said:
Gtrab, I've updated to version Visionary r14 and then enabled the new option for R/W, restarted and I still have S-OFF and the ClockWorkMod.
I use root explorer to make changes to the /system partition, it allows to mount it r/w so I think I'm going to disable this on boot option for security...
Have you flashed the stock hboot earlier or did some changes/testing prior the update of this program?
EDIT: here's the link of the Visionary app thread with the description, maybe it can answer some questions.
http://android.modaco.com/content/h...m/322658/19-nov-r14-visionary-one-click-root/
Click to expand...
Click to collapse
I've tested tons of combinations, but yes I did as you say:
Flahsed a fresh untouched ROM from my version's RUU, this turned S-ON and lost root.
Then used Visionary 14 to temp root-> perm root with r/w ticked.
After reboot, I had root and was able to mount r/w on demand, but was unable to install ClockworkMod (CWM) from the ROM Manager app because I was S-ON (obviously because visionary r14 doesn't have engineering hboot).
I think CWM is priceless, so I installed the eng hboot again to go S-OFF.
If you check koush's (ROM Manager) thread, he states CWM requires S-OFF
http://forum.xda-developers.com/showthread.php?t=834731
gtrab said:
I've tested tons of combinations, but yes I did as you say:
Flahsed a fresh untouched ROM from my version's RUU, this turned S-ON and lost root.
Then used Visionary 14 to temp root-> perm root with r/w ticked.
After reboot, I had root and was able to mount r/w on demand, but was unable to install ClockworkMod (CWM) from the ROM Manager app because I was S-ON (obviously because visionary r14 doesn't have engineering hboot).
I think CWM is priceless, so I installed the eng hboot again to go S-OFF.
If you check koush's (ROM Manager) thread, he states CWM requires S-OFF
http://forum.xda-developers.com/showthread.php?t=834731
Click to expand...
Click to collapse
Yes it was the problem, I'm glad it's working for you! I agree with you regarding the CWM
gtrab said:
I've tested tons of combinations, but yes I did as you say:
Flahsed a fresh untouched ROM from my version's RUU, this turned S-ON and lost root.
Then used Visionary 14 to temp root-> perm root with r/w ticked.
After reboot, I had root and was able to mount r/w on demand, but was unable to install ClockworkMod (CWM) from the ROM Manager app because I was S-ON (obviously because visionary r14 doesn't have engineering hboot).
I think CWM is priceless, so I installed the eng hboot again to go S-OFF.
If you check koush's (ROM Manager) thread, he states CWM requires S-OFF
http://forum.xda-developers.com/showthread.php?t=834731
Click to expand...
Click to collapse
Since your guides are so amazing Do you think you can make a dummy one for how to loose root and S-Off, more specifically where to get the stock RUUs and how to flash them?
Do you get them from shipped-roms.com or where?
I just want to be sure in case of having to return back the device.
Thanks in advance
gtrab said:
If you check koush's (ROM Manager) thread, he states CWM requires S-OFF
http://forum.xda-developers.com/showthread.php?t=834731
Click to expand...
Click to collapse
I don't understand why though - if you can flash to the HBOOT partition why can't you flash to the recovery partition?
You can. You'd need to use the wpthis thing before using clockwork. Think I'd prefer S-OFF though.
Sent from a Pulse. Yes, a Pulse.
DanWilson said:
You can. You'd need to use the wpthis thing before using clockwork. Think I'd prefer S-OFF though.
Click to expand...
Click to collapse
OK so Visionary will temproot and then insmod wpthis... So theoretically you could then (without rebooting) run Rom Manager and it could flash ClockworkRecovery, which itself has been modified to include wpthis so you wouldn't need to flash HBOOT?
I know some would prefer to have S-OFF in the HBOOT, but if you're not fussed or don't want to take the risk then the above could be an option... if my understanding's right!?
DanWilson said:
You can. You'd need to use the wpthis thing before using clockwork. Think I'd prefer S-OFF though.
Sent from a Pulse. Yes, a Pulse.
Click to expand...
Click to collapse
What is wpthis??
buzmay said:
What is wpthis??
Click to expand...
Click to collapse
The module that turns off the write protection on the internal NAND storage. See the sticky threads on rooting for more details.
mamoulian666 said:
OK so Visionary will temproot and then insmod wpthis... So theoretically you could then (without rebooting) run Rom Manager and it could flash ClockworkRecovery, which itself has been modified to include wpthis so you wouldn't need to flash HBOOT?
I know some would prefer to have S-OFF in the HBOOT, but if you're not fussed or don't want to take the risk then the above could be an option... if my understanding's right!?
Click to expand...
Click to collapse
the wpthis ("write protect this") effect is temporary since a reboot will delete it and restore stock values
theoretically speaking, you could insmod wpthis and then tell ROM Manager to install CWM
buzmay said:
Since your guides are so amazing Do you think you can make a dummy one for how to loose root and S-Off, more specifically where to get the stock RUUs and how to flash them?
Do you get them from shipped-roms.com or where?
I just want to be sure in case of having to return back the device.
Thanks in advance
Click to expand...
Click to collapse
I've been updating the FAQs day after day,
I think all of your requirements are already there (flashing from RUU, getting the RUUs, how to go back from root and S-OFF, etc. It's all in the FAQ.
Where do I get 'em ?? The Desire Z Android Development forum has several RUUs listed, these are the only ones I am aware of.
A specific link to a specific RUU ?? Not a good idea:
I could link them on the tutorial, but newer ones will always pop up and links will get obsolete, people will get confused.
Thats why I btter state "check the forum for currnt / latest available RUUs".
gtrab said:
I've been updating the FAQs day after day,
I think all of your requirements are already there (flashing from RUU, getting the RUUs, how to go back from root and S-OFF, etc. It's all in the FAQ.
Where do I get 'em ?? The Desire Z Android Development forum has several RUUs listed, these are the only ones I am aware of.
A specific link to a specific RUU ?? Not a good idea:
I could link them on the tutorial, but newer ones will always pop up and links will get obsolete, people will get confused.
Thats why I btter state "check the forum for currnt / latest available RUUs".
Click to expand...
Click to collapse
Could you having s-off and of course perm root, to come back to stock rom could you copy the PC10img to the root of the sdcard and enter into bootloader? will that work?
Thanks a lot in advance
Please help, I'm trying to root so I can run netflix on mt4g, almost there (i think)
Tysvm2: the folks that wrote: the true root article @
http://forum.xda-developers.com/showthread.php?t=858996
I am trying to flash a custom recovery and rom (hoping to do: panache or CM7 and twrp recovery
(PG86IMG.zip) My end goal is to run netflix app on htc glacier)
I have succeeded in setting up ADB/SDK drivers, etc.
On hboot i see: S=off
I am having a PROBLEM with TRUE ROOT gfree method
At step 12. It says:
"If this is the first time you have rooted your device you will need to run visionary again (temproot w/set system r/w after root checked and then attempt permroot) to make root privileges permanent and then reboot again. Now "su" should work properly for you."
I've run into a problem :
I restarted in hboot and I see s=off but when I try to open terminal:
It reads:
$ export PATH=/data/local/bin:$PATH
$su
PERMISSION DENIED
I tried to run temproot and permroot on visionary + R14 to "seal the deal" & move onto install of the engineering bootloader
It appears I am stuck in between temproot and perm root won't stick for some reason ...
FYI: all sorts of apps force closed immediately after reboot after I ran the reboot it says s=off and has bootloader version 0.86.0000
I just did:
1. a factory reset from hboot
2. Reinstalled visionary + R14
3. And ... astro file manager, terminal emulator app and easy installer, etc
4. i have all the files that the TRUE ROOT thread reccomended but terminal emulator says permission denied when I type: su
PERMISSION DENIED
It looks to me like visionary Is not properly establishing temp root or perm root after s=off.
Suggestions please.
thank you,
CP
HTC GLACIER
s=off
bootloader version 0.86.0000
also: HTC DREAM aka Tmobile g1 rooted with cyanogen old school
Ps: I'm new to the forum culture and I want to be sure to be respectful and post properly; if this is not a proper place for this kind of question please redirect me patiently
Try the older verson of Visionary. R11 I believe. This has come up before and it has worked for other people.
If you have already received the OTA, use Gingerbreak or fre3vo method for temp root instead of Visionary.
I suggest to flash engineering bootloader ASAP, it'll save you the question next time, by allowing to flash custom recovery (thus enabling root by flashing any su.zip package) at any time, independent of the ROM.
I got a replacement phone, and this is what I had to do...
1. Install Visionary r14 and Terminal Emulator
2. Download gfree file and move to phone
3. Temproot (with r/w switched on), then su on TE, then run gfree*
4. Reboot and validate S=OFF
5. Temproot again (with r/w switched on), then click on Permroot
Hi Thank you for your reply, I tried visionary r11 but when I installed it would not run (perhaps i installed the wrong one) my easy install app read it as visionary 1.0 is that the same as R11?
Thank you for your reply but i tried this:
http://forum.xda-developers.com/showthread.php?t=1030119
from Shaddy-Z.(10th April 2011, 01:35 PM) <- thank you Shaddy
"
http://forum.xda-developers.com/show...&postcount=899
It's the last download link."
But my easy install app calls it visionary 1.0 (is that the same as R11?) And it did not work ... it won't even open up, can you tell me do you have any experience with:
Jack R_1's suggestion: "If you have already received the OTA, use Gingerbreak or fre3vo method for temp root instead of Visionary."
What are benefits of gingerbreak vs. fre3vo? I just want to be sure to be careful so as to not brick my baby.
If you already have Radio S-OFF, have you tried flashing custom recovery via fastboot flash recovery? Or does your bootloader version not allow that?
Also try this post:
http://forum.xda-developers.com/showpost.php?p=15943010&postcount=6
I only know about gingerbreak not the other one, it will use a new exploit to gain perm root under gingerbread. But if you have the new OTA that's gingerbread 2.3.4 I think it won't work. Others have upgraded to the new OTA and can't root again, why? Since a new Radio and I think SPL are in this new OTA. And HTC has used a new security method to prevent such things as rooting.
Check this thread
http://forum.xda-developers.com/showthread.php?t=1174344
Flash the .85 engineering bootloader with adb and then clockworkmod from fastboot. You then can use the rooted nandroid backup in rom Bible (if you want to stay stock). Once you do that happy flashing. If you need any help pm me
Sent from my Google Nexus 12! yup I'm from the future
mark manning said:
Flash the .85 engineering bootloader with adb and then clockworkmod from fastboot. You then can use the rooted nandroid backup in rom Bible (if you want to stay stock). Once you do that happy flashing. If you need any help pm me
Sent from my Google Nexus 12! yup I'm from the future
Click to expand...
Click to collapse
Are you sure this holds true for users with newest OTA?
Ace42 said:
Are you sure this holds true for users with newest OTA?
Click to expand...
Click to collapse
As long as he has s-off it will.
Sent from my Google Nexus 12! yup I'm from the future
Ace42 said:
Are you sure this holds true for users with newest OTA?
Click to expand...
Click to collapse
Wait, he can't gain even temp root huh. NM your sol until a dev figures out how to root the gingerbread rom.
Its kind of a long shot. Since you have s-off you can try using the PD15IMG.ZIP from hboot and root the froyo rom. Not sure if that will work or not
Sent from my Google Nexus 12! yup I'm from the future
mark manning said:
Wait, he can't gain even temp root huh. NM your sol until a dev figures out how to root the gingerbread rom.
Its kind of a long shot. Since you have s-off you can try using the PD15IMG.ZIP from hboot and root the froyo rom. Not sure if that will work or not
Sent from my Google Nexus 12! yup I'm from the future
Click to expand...
Click to collapse
I'm using MIUI, I was asking cause I have a friend who's stuck on the new OTA since they accidentally flashed the non-rooted version of the OTA, probably since all of them had the same title and he didn't read...
Okay let me ask this: What about packing an unsigned PD15IMG.zip with ENG HBOOT and/or ClockworkMod Recovery and nothing else inside it? If you have Radio S-OFF, this image should be accepted by the bootloader and give you a route back to root.
I don't know if such a .zip has been made yet for the MT4G but it's not impossible. It's been done for the S-OFF Sensation:
http://forum.xda-developers.com/showthread.php?t=1122053
See "ENG Hboot" - there is a PG58IMG.zip file there, and there is another under "Here is the download link to recovery".
Again this thread has nothing to do with the MT4G but it's the same principle.
So... if there is anyone out there who knows how to pack a PD15IMG.zip for a Radio S-OFF device, please speak up and help out the OP!
Interesting, I think all you need to do is replace the file inside of zip but not totally sure.
Sent from my Google Nexus 12! yup I'm from the future
What I don't know is if the zip has to be constructed in some particular way to be accepted as valid, even with S-OFF. But yeah, there should be a way to flash CWM to the S-OFF bootloader.
Sent from my Nexus One using Tapatalk
Thank you but I don't know what that is exactly.
Ru suggesting I restart holding down on volume and select recovery from hboot?
Sent from my HTC Glacier using XDA App
crouchingpossum said:
Thank you but I don't know what that is exactly.
Ru suggesting I restart holding down on volume and select recovery from hboot?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
No not yet, gonna try to figure something out for you tomorrow. Be patient please
Sent from my Google Nexus 12! yup I'm from the future
Are you on 2.2.1 or are you on 2.3.?
Okay I'm just poking around blindly in the dark here... I'm not a developer, just a script tinkerer... but if you're brave enough...
I grabbed one of the PD15IMG.zip radio files from the Dev section just to obtain the proper android-info.txt file. Then I created a new zip containing only:
- android-info.txt
- CWM version 3.0.2.4 for Glacier, in .img format, renamed to recovery.img
I've attached it here. Rename it to PD15IMG.zip, put it on the root of your SD, and try booting into HBOOT and see if it prompts you to install the zip. If so, does it succeed?
If yes, then try booting into recovery. Do you get Clockwork?
If it does not succeed, please report any error messages.
I highly doubt this can damage your phone because your ROM is still bootable and your bootloader still works, so the worst you could get is a bad recovery that you have to fix up. But I hold no liability for anything that gets borked
Hello all,
I just ran RUU 2.2 to my wildfire, and used some command prompt actions to flash a new 1.0.0001 hboot to regain S-on. (Used Instructions Here: http://forum.xda-developers.com/showthread.php?t=1160251 )
Then I tried to run revolutianary tool to regain root access, but I only gain S-on and after the tool goes not responding (although i choose yes when it asks me to download clockwordrecovery and install it)..... tried to run unrevoked after that (since i goot s-off but no root) but no luck,it gives the too new firmware error..
So, since I couldn't root, I reused the command prompt to regain S-On... I did all that from the very beginning just to get root access but on stock froyo, coz I didn't like CM...
Sent from my HTC Wildfire using XDA App
There is a lot of confusion in your post.
Alyzembawy said:
Tried to run revolutianary tool to regain root access, but I only gain S-on
Click to expand...
Click to collapse
Revolutionary doesnt give you S-ON. It gives S-OFF. It doesn't give you root access either. Superuser binary does, which has to be flashed after you get S-OFF and Clockworkmod
Alyzembawy said:
So, since I couldn't root, I reused the command prompt to regain S-On... I did all that from the very beginning just to get root access but on stock froyo, coz I didn't like CM...
Click to expand...
Click to collapse
You never got S-OFF as per your post. How did you S-ON a S-ON phone?
Anyway, from what I get, you have Stock Froyo, and you have S-ON, and you simply want root access? In that case, there are 2 ways
1) Gain S-OFF again using Revolutionary . Then install Custom Recovery (Seperately, if Revolutionary is not working / giving you an error), and simply flash the Superuser Binary in Clockworkmod
Or
2) Gain S-OFF using Revolutionary, then gain S-ON again using the same command prompt tools. But, instead of flashing HBoot 1.01.0001, flash HBoot 0.80.x. This will allow you to root using Unrevoked, as was the case earlier
3xeno said:
There is a lot of confusion in your post.
Revolutionary doesnt give you S-ON. It gives S-OFF. It doesn't give you root access either. Superuser binary does, which has to be flashed after you get S-OFF and Clockworkmod
You never got S-OFF as per your post. How did you S-ON a S-ON phone?
Click to expand...
Click to collapse
Yeah sorry i meant that i got s-off after running revolutionary tool
Alyzembawy said:
Yeah sorry i meant that i got s-off after running revolutionary tool
Click to expand...
Click to collapse
I checked your Edited post. Well, just follow one of the 2 methods I listed below, either of them will work.
3xeno said:
Anyway, from what I get, you have Stock Froyo, and you have S-ON, and you simply want root access? In that case, there are 2 ways
1) Gain S-OFF again using Revolutionary . Then install Custom Recovery (Seperately, if Revolutionary is not working / giving you an error), and simply flash the Superuser Binary in Clockworkmod
Or
2) Gain S-OFF using Revolutionary, then gain S-ON again using the same command prompt tools. But, instead of flashing HBoot 1.01.0001, flash HBoot 0.80.x. This will allow you to root using Unrevoked, as was the case earlier
Click to expand...
Click to collapse
Can you please link me instructions to do these two steps, and which do you think is safer and easier ?!
And thanks btw
Alyzembawy said:
Can you please link me instructions to do these two steps, and which do you think is safer and easier ?!
And thanks btw
Click to expand...
Click to collapse
Depends, but the first should be easier, since you have already performed it yourself. The procedure remains exactly the same, just that you do not flash the CM7 ROM File, but simply flash the Superuser Binary file to gain root.
- Run Revolutionary
- Gain S-OFF
- When it asks to install a Custom Recovery, Select Y, and if it installs, well and good.
- If it doesn't, follow this guide to install Clockworkmod - http://forum.xda-developers.com/showthread.php?t=1130044
- Once Clockworkmod is installed, download Superuser Binary here: http://bit.ly/su2361ef and place it on your SDCard
- Reboot into Clockworkmod Recovery and flash it. (Install Zip from SDCard > Select the zip file you just placed)
3xeno said:
Depends, but the first should be easier, since you have already performed it yourself. The procedure remains exactly the same, just that you do not flash the CM7 ROM File, but simply flash the Superuser Binary file to gain root.
- Run Revolutionary
- Gain S-OFF
- When it asks to install a Custom Recovery, Select Y, and if it installs, well and good.
- If it doesn't, follow this guide to install Clockworkmod - http://forum.xda-developers.com/showthread.php?t=1130044
- Once Clockworkmod is installed, download Superuser Binary here: http://bit.ly/su2361ef and place it on your SDCard
- Reboot into Clockworkmod Recovery and flash it. (Install Zip from SDCard > Select the zip file you just placed)
Click to expand...
Click to collapse
Well that's funny, this time revolutionary tool just worked, and it reported "SUCCESS" about flashing CWM... So now am I fully rooted, or I still have to flash the binary super user app ?!
Alyzembawy said:
Well that's funny, this time revolutionary tool just worked, and it reported "SUCCESS" about flashing CWM... So now am I fully rooted, or I still have to flash the binary super user app ?!
Click to expand...
Click to collapse
You'll still have to flash Superuser to gain root access. The correct terminology is that it is a ROM which is rooted. A phone is never rooted.
Also, since you are keeping S-OFF, don't forget the Sense Fix here:
http://forum.xda-developers.com/showthread.php?t=1156713
3xeno said:
You'll still have to flash Superuser to gain root access. The correct terminology is that it is a ROM which is rooted. A phone is never rooted.
Also, since you are keeping S-OFF, don't forget the Sense Fix here:
http://forum.xda-developers.com/showthread.php?t=1156713
Click to expand...
Click to collapse
Ok, so now I will flash superuser to gain root acces, then flash the Sense Fix... Do I have to hard reset after all this ?!
Alyzembawy said:
Ok, so now I will flash superuser to gain root acces, then flash the Sense Fix... Do I have to hard reset after all this ?!
Click to expand...
Click to collapse
Not necessary, (Flashing both, Superuser and the sense fix doesn't touch your data) but, remember to take a Nandroid Backup though, in Clockworkmod, just in case.
3xeno said:
Not necessary, (Flashing both, Superuser and the sense fix doesn't touch your data) but, remember to take a Nandroid Backup though, in Clockworkmod, just in case.
Click to expand...
Click to collapse
Uhm, When I go to CWM and select Installl ZIP from SD Card, it goes to a black screen with the logo "REVOLUTIONARY" on... and the nothing...
Edit. Ah sorry, I was using the power button to select
Nvm
Hello all.. I am tryin to install the engineering bootloader and the file I need from the wiki page is not there anymore. Does anyone know where I can obtain a true copy of it. I d/l one and its not right, the md5sum was incorrect. It should be md5sum: df4fd77f44993eb05a4732210d2eddc6. Thanks if you can help. Im just trying to be thorough as i am learning all this. I have it rooted with s=off but I want to install eng. bl ....Thanks
**It is for MyTouch 4g**
Use this. Its the eng h-boot and clockworkmod recovery.
https://rapidshare.com/#!download|...|3930|R~C053B71776B49869847E4E328CF8DEC4|0|0
I got it from one of the stickies in the dev section.
Also, I have 2 Mt4g. One of the has the bootloader unlocked via HTCdev. I keep trying to flash a Stock 2.2.1 rom to it so I can do the Perma Root method on it. I have a custom rom on it currently, but it has s=on. Now the other one was stock 2.3.4 and I just got finished rooting it, for practice. Now back to the one with the bootloader unlocked by HTC, will traditional methods still work on it? I cant seem to get the adb/fastboot method to install the 2.2.1 rom on it. what would you recommend I do to get s=off on it if Im bent on doing it?
jjbadd385 said:
Also, I have 2 Mt4g. One of the has the bootloader unlocked via HTCdev. I keep trying to flash a Stock 2.2.1 rom to it so I can do the Perma Root method on it. I have a custom rom on it currently, but it has s=on. Now the other one was stock 2.3.4 and I just got finished rooting it, for practice. Now back to the one with the bootloader unlocked by HTC, will traditional methods still work on it? I cant seem to get the adb/fastboot method to install the 2.2.1 rom on it. what would you recommend I do to get s=off on it if Im bent on doing it?
Click to expand...
Click to collapse
I know NOTHING about the unlocked bootloader, so forgive me. Will flashing the froyo PD15IMG.zip from bootloader not replace your bootloader with the stock S-On bootloader that the rooting w S-Off guides are written for? Or has HTC figured out some way to bone you on that?
PD15IMG method of downgrading should take you to the older OS.
It won't necessarily take you to the older bootloader.
Not sure that being on the older bootloader is required for gfree to work. The older OS is indeed required.
Ok I'll tell you what I did this morning. I read a bunch last night. I am trying desperately to grasp & understand things. Its just there are so many different ways to acheive what I want to accomplish. Im doing this in small goals. My goal at this point is to get this MT4G, that is bootloader unlocked by HTC, to flash the Stock 2.2.1 Rom.But for some reason, it wont. Ive tried using my PC ADB/fastboot method, with no success. This morning I tried Recovery Clockwork, which I did wipe/factory reset, wipe cache, wipe davli cache, and then I choose the write zip from sd card, PD15IMG, and it wont do that either. I know I could be more helpful if I gave the exact errors but I forgot what they are, and at this point I am beginning to think that because its HTCdev unlocked, its not going to let me flash the 2.2.1. It does everything fine, until I attempt to flash the 2.2.1. The md5sum is ok too. If it were you, and you were running a custom ROM (ProjectMIUI 2.2.17 [R6]- UPDATED 2/21/12), and your device was HTC unlocked, but you wanted to get s=off, with engineer boot, how would you begin, and what method would YOU use? Give me some of your excellent advice for my birthday, which is today.
pdimg.zip files are flashed through the bootloader, not recovery. To do this, put zip on root of SD card power off phone hold volume down and power until bootloader appears and follow onscreen prompts.
HTC-Dev-unlocked bootloader 100% allows downgrading, because someone already did it before you. If you fail achieving it - means you're doing something wrong again and again, not realizing it. If I were you, I would think - why is it that your attempts to flash PD15IMG fail - and correct what you're doing wrong. But obviously, this excellent advice was given to you some time before your birthday, and still didn't help.
So, here's another advice:
Go download a PRE-ROOTED 2.2.1-based ROM.
Assuming you find one: flash it in recovery and flash boot.img from it separately.
Reboot to ROM.
Run gfree.
Flash Eng HBOOT.
If you don't find any 2.2.1-based ROM available, then you're out of luck. Sit down and find out what you're doing wrong that doesn't let you downgrade with PD15IMG.
Or just keep your phone as it is, and flash kernels manually, until you understand more.
Ok,I understand what you are saying. But when I put it on the root of my SD card as I have done multiple times, I pwr up in hboot, I wait on the blue progress bar, then a gold progress bar, then I get an error, I think it was "older version" if I remember correctly. There's not much I can do wrong to mess up a simple hboot flash of PD15IMG,you boot your phone up and wait ...
Sent from my HTC Glacier using Tapatalk
To avoid this error, you need to flash the MISC partition to "fool" the phone into thinking it's older than it is.
Read the downgrading guide, and since you're rooted - execute the "misc_version" part only:
> adb push misc_version /data/local/tmp/misc_version
> adb shell chmod 777 /data/local/tmp/*
> adb shell
Click to expand...
Click to collapse
If you see "$", it means you're not running in root shell. Then execute "su" and verify that you get "#" to continue.
# cd /data/local/tmp
# ./misc_version -s 1.00.000.0
Click to expand...
Click to collapse
You should see:
--set_version set. VERSION will be changed to: 1.00.000.0
Patching and backing up partition 17...
Click to expand...
Click to collapse
Then attempt downgrading again.
Jack_R1 said:
To avoid this error, you need to flash the MISC partition to "fool" the phone into thinking it's older than it is.
Read the downgrading guide, and since you're rooted - execute the "misc_version" part only:
If you see "$", it means you're not running in root shell. Then execute "su" and verify that you get "#" to continue.
You should see:
Then attempt downgrading again.
Click to expand...
Click to collapse
Everything went well until I got to the flashing part again. I did it 2 times, one time with fastboot and i got this:
C:\adb>fastboot-windows oem rebootRUU
... OKAY
From my PC:
C:\adb>fastboot-windows flash zip StockRom.zip
sending 'zip' (319593 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 99 unknown fail)
From my phone:
The next time, I did it in hboot from the handset and it returned an error that said "wrong zip file"
**I think I am going to be content flashing roms and the boot.img seperately until I find someone with this problem that figures it out. Besides I have another mt4g that I perm rooted s=off, so I truly feel like I have followed instructions well, since my 2nd phone worked out. Its just this one with the HTC unlocked b/l giving me problems.
Thank You for your help...
You insist on NOT following the guide, so I won't help you anymore.
FOLLOW THE DAMN GUIDE UNTIL YOU UNDERSTAND WHAT YOU'RE DOING!
Because obviously, you're doing lots of basically wrong stuff, like trying to flash a PD15IMG.ZIP by fastboot, or using fastboot oem commands.
I understand u getting frustrated, but I have followed the guide. It don't work that way either. It tells me " wrong zip file" in hboot when I do, & I know its the right one because I checked the md5sum. If its lettin me flash any Rom in CWM recovery, why can't I flash a 2.2.1 Rom in recovery? But just to let u know, I have followed the guide to the t, more than once. Sorry if u r getting frustrated but I have tried everything u told me, & thanks for helping.
Sent from my HTC Glacier using Tapatalk
Ok it says
***UNLOCKED*** (by HTCdev)
GLACIER PVT SHIP S-ON
HBOOT-0.89.0007
MICROP-0429
RADIO-26. 13.04.19_M
eMMC-boot
Dec 13 2011 21:07:39
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMG CRC
I do have Visionary and a stock unrooted 2.2.1 (PD15IMG). I also have Recovery CWM 5.0.2.0 and 4ext, just to let u know what resources I have. I think I have d/l everything under the sun..lol
Sent from my HTC Glacier using Tapatalk
Anglgodes19 said:
Good, now that makes it easy as I deleted my modified stock rom last year which I made specially for rooting, so lets move on...
1) Gain TempROOT via VISIONary+
2) On terminal.
adb shell [enter]
su [enter]
dd if=/dev/block/mmcblk0p17 of=/sdcard/msicold.img [enter]
3) Access /sdcard/msicold.img and open it in hex editor.
4) Find MSIC value XXX.XXX.XXX.XXX (ex: 2.09.1800.1) and change it to OTA "1.17.531.2" and save the file as msicnew.img on SDCard.
5) Now back on adb terminal:
dd if=/sdcard/miscnew.img of=/dev/block/mmcblk0p17 [enter]
sync [enter]
6) Now reboot in to bootloader and flash PD15IMG.zip as you would normally do.
Report back if you have issues or problems or can't find it in that case I suggest you upload your msicold.img and ill edit for you so you can replace it.
Click to expand...
Click to collapse
Ok I did that and opened the msicold.img in hex editor, and honestly I dont have a clue as to what i was doing, but i think i located the value and because i followed the downgrade guide, i beleive its 1.00.000.0, but i dont know how to change it. Any way i can email it to u and have u change it? my email is [email protected] if you will send me a blank email, I'll reply back with the attatched file...Thank you..
jjbadd385 said:
Ok I did that and opened the msicold.img in hex editor, and honestly I dont have a clue as to what i was doing, but i think i located the value and because i followed the downgrade guide, i beleive its 1.00.000.0, but i dont know how to change it. Any way i can email it to u and have u change it? my email is ****** if you will send me a blank email, I'll reply back with the attatched file...Thank you..
Click to expand...
Click to collapse
You may want to edit this post. Ask anyone interested in helping to PM you. Posting your email address on an open forum isn't a good idea.
estallings15 said:
You may want to edit this post. Ask anyone interested in helping to PM you. Posting your email address on an open forum isn't a good idea.
Click to expand...
Click to collapse
Wonder what happened to Anglgodes19 and all his posts? He disappeared like a theif in the night!!
1.00.000 is the correct value.
If bootloader doesn't accept PD15IMG.ZIP - it either means you're doing something wrong even though you're 100% sure you're not, or that HTC-Dev-unlocked HBOOT doesn't accept the image for downgrading, which I highly doubt.
In any case, as I wrote you, you can download and flash any 2.2.1 pre-rooted ROM, if you find one with working link, and continue the guide from there.
I don't think I can help you with anything beyond this point.
Jack_R1 said:
1.00.000 is the correct value.
If bootloader doesn't accept PD15IMG.ZIP - it either means you're doing something wrong even though you're 100% sure you're not, or that HTC-Dev-unlocked HBOOT doesn't accept the image for downgrading, which I highly doubt.
In any case, as I wrote you, you can download and flash any 2.2.1 pre-rooted ROM, if you find one with working link, and continue the guide from there.
I don't think I can help you with anything beyond this point.
Click to expand...
Click to collapse
Ok then, one last question. If I cannot get my phone to flash via hboot, Is it possible to flash the 2.2.1 rom through CWM like I am flashing other roms? Or if I flash a rooted 2.2.1 rom could I the proceed in getting s-off/ eng hboot? Or does it have to be done through hboot only with a stock rom? Or possibly a modified 2.2.1 rom that has been made to flash in recovery?
'
i have S-off but i have no root or recovery! please someone help! i need to get this phone back to stock!
Run PD15IMG.zip. It will flash the stock recovery and set everything back to stock. You should be good to send your phone back after that.
When I had that problem flashing the pd15.img did not turn S-on.
If your still on 2.2.1 you need to temp root with visionary and run gfree to turn S back on.
If your on gingerbread (2.3) you'll have to downgrade back to 2.2.1 before you can run gfree.
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
SenorBlanco said:
When I had that problem flashing the pd15.img did not turn S-on.
If your still on 2.2.1 you need to temp root with visionary and run gfree to turn S back on.
If your on gingerbread (2.3) you'll have to downgrade back to 2.2.1 before you can run gfree.
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
Click to expand...
Click to collapse
He needs to use grankin01's guide to get S-ON once he get back to froyo and then reflash froyo PD15IMG to restore everything back to stock.
Because he used gfree to acquire S-OFF, just flashing the PD15IMG.zip won't turn the security flag on. It does for root.sh, but not gfree.
Sent from my Glacier using XDA
I thought I remembered that the guide said how you could use gfree to turn S-on as well.
Sent from my Glacier using XDA
the guide says it works for pre OTA update. does that mean i dont have to go back to 2.2.1?
gcashiel said:
the guide says it works for pre OTA update. does that mean i dont have to go back to 2.2.1?
Click to expand...
Click to collapse
Yes.
invasion2 said:
Yes.
Click to expand...
Click to collapse
okay so how do i put back the stock hboot and turn s-on and unroot my phone? the whole guide is very confusing to me
gcashiel said:
okay so how do i put back the stock hboot and turn s-on and unroot my phone? the whole guide is very confusing to me
Click to expand...
Click to collapse
Let's get things straight. You are on 2.3.4, Engineering hboot, S-OFF, no root, and no recovery?
yes i am on 2.3.4 and i now have root and cwm recovery. and i have s-off
gcashiel said:
yes i am on 2.3.4 and i now have root and cwm recovery. and i have s-off
Click to expand...
Click to collapse
LOLWUT. 2.3.4 stock? With S-OFF and root and CWM?
invasion2 said:
LOLWUT. 2.3.4 stock? With S-OFF and root and CWM?
Click to expand...
Click to collapse
yes. or what do you mean?
gcashiel said:
yes. or what do you mean?
Click to expand...
Click to collapse
I'm confused...gcashiel, you are rooted, CWM recovery, S-Off right? But all of this is on 2.3.4 STOCK T-mobile OTA ROM, correcT?
invasion2 said:
I'm confused...gcashiel, you are rooted, CWM recovery, S-Off right? But all of this is on 2.3.4 STOCK T-mobile OTA ROM, correcT?
Click to expand...
Click to collapse
yes correct. i have the stock rom with root privileges.
i am trying to get EVERYTHING back to stock, hboot ( i have the hboot 0.85.2007), Security back to on, and the original 2.3.4 rom
I'll "translate":
There is no T-Mobile "stock" 2.3.4 with root. It's a pre-rooted 2.3.4, that you flashed from CWM recovery. The stock is not rootable, and should have been downgraded at some point to achieve S-OFF.
In any case, if S-OFF was achieved through gfree, you need to rerun gfree to return to S-ON. Judging by this thread, it's going to be way over your head.
So, my suggestion:
1) Go to the downgrading thread (search, don't ask), run "misc_partition" command on your current ROM.
2) Copy PD15IMG.ZIP of 2.3.4 to SD card and proceed with returning to stock. You'll most likely stay S-OFF, but otherwise have a completely stock ROM.
If it sounds too complicated - wait for someone to explain it better, or start reading to understand, what to do. Everything you need is in the guides, you just need to understand what things do and how to use it for your case.
Jack_R1 said:
I'll "translate":
There is no T-Mobile "stock" 2.3.4 with root. It's a pre-rooted 2.3.4, that you flashed from CWM recovery. The stock is not rootable, and should have been downgraded at some point to achieve S-OFF.
In any case, if S-OFF was achieved through gfree, you need to rerun gfree to return to S-ON. Judging by this thread, it's going to be way over your head.
So, my suggestion:
1) Go to the downgrading thread (search, don't ask), run "misc_partition" command on your current ROM.
2) Copy PD15IMG.ZIP of 2.3.4 to SD card and proceed with returning to stock. You'll most likely stay S-OFF, but otherwise have a completely stock ROM.
If it sounds too complicated - wait for someone to explain it better, or start reading to understand, what to do. Everything you need is in the guides, you just need to understand what things do.
Click to expand...
Click to collapse
okay i think i understand but what if i do the PD15IMG with the stock rom to get it unrooted will that be enough to send it back?
People on the forum reported that it was enough. I have no first-hand experience.
okay then but will it work with the PD15IMG that has the GB update on it?
can you help with this step please?
5. Now run the "dd if=/where/your/part7backup-numbers.bin of=/dev/block/mmcblk0p7" and it should show the output:
xxxx bytes in
xxxxbytes out
xxxxxxxxxx copied in blah blah blah
gcashiel said:
can you help with this step please?
5. Now run the "dd if=/where/your/part7backup-numbers.bin of=/dev/block/mmcblk0p7" and it should show the output:
xxxx bytes in
xxxxbytes out
xxxxxxxxxx copied in blah blah blah
Click to expand...
Click to collapse
?????
What do you not get? Locate the part7backup files on your sd card and add the path to the command sample. If you don't have them, follow this guide.
http://forum.xda-developers.com/showthread.php?p=16189365