Hello all, just got the MT4GS I have latest boot loader and update previous owner did it right before I purchased.
I thought we should get together and see what works and what doesn't.
I have tried the temp root method and SuperOneClick and the official HTC unlocker to no avail.
I know on some phones its possible to downgrade using some sort of official package or signed update. Is there such thing for our phone?
Threads I used for reference:
[APP]SuperOneClick v2.3.2 - Better LG Phone Support!
permroot for S-off MyTouch 4G Slide
Anyone notice the MT4GS Bootloader Unlockable?
Poking at latest OTA update for fun and profit
[TOOL] PERMANENT-ROOT (NEW!) & Temp-Root (v2) for any MT4GS (Windows)
There has to be a way to get this done. I found a signed and stock firmware and instructions
Originally Posted by yogi2010 View Post
sure Blue, it is pretty much the usual...
To undo the update/restore the stock firmware that came with the phone:
(Note: this will only work if you are still S-OFF even tho you have the new HBOOT version. If you are S-ON with the new HBOOT, then at this time there is no known way to revert... hopefully we can get the devs. of Revolutionary, etc, to update the root methods. Also, if you want to update just to check it out, make sure to turn S-OFF first if you'd like to give yourself the option to revert later.)
1. Download the stock firmware package from here: http://forum.xda-developers.com/show....php?t=1178082
2. Rename it PG59IMG.zip and put it on the root of your sdcard.
3. Boot into the bootloader('adb reboot bootloader' or power down the phone then hold volume down + power), let it read the update package, and press 'volume up' to update when prompted.
4. At the end it will prompt you to press Power to reboot. It scared me because when i pressed Power, the screen went off and seemed to not come back on, so i pressed power once again, and it booted into the system.
That's it! Just remember that if you do this, it will of course erase all your data... your phone will be like it was out of the box.
Click to expand...
Click to collapse
It won't work because the version is too old obviously. These are specially crafted archives with data in the beginning of the archive. You can't modify the android-info.txt because it throws off both winrar and 7zip.
I tried changing the version number in a hex editor. This makes the crc fail. Is there a way to just alter the crc to the new CRC? This way when HBOOT checks for the checksum it will pass and downgrade. I know for Unreal Tournament based games hackers would use a method called bytehacking where they are able to change certain values without upsetting CRC checks. Would something like this be possible?
I found a tool that recovers it and fixes it I have to try flashing in HBOOT but I doubt it will work I'm afraid the important data in the beginning. Maybe if I sign it, it will work?
The latest idea I had was using the OTA update, it contains a firmware.zip what if we modify the contents of firmware.zip with the contents of the stock firmware? You can flash using fastboot (i hope) as it will be formatted as an update and will downgrade the hboot as well.
are you S-ON? i mentioned in that post that it will only work if you happened to have S-OFF from before, which i did. but so far no one has been able to do anything with S-ON and the newest update. have you tried Tacoroot?
The search button is your friend ._., there are 5+ threads that share information and methods none of which work but the people on said threads are putting information and ideas out there.
Sorry noob question, just got the Mt4gs and It's updated to newest, how do I check if I am s-off or s-on? Also in short what does s-off/on mean? Thanks in advance.
Doubleshot on XDA App
Power the phone off with fastboot turned off. Or pull the battery when you power on hold the lower volume key and power simultaneously to boot into hboot. It will tell you S-OFF /S-ON. If you have latest OTA you're most likely S-ON.
S-Off: This term is used when describing the security radio. With S-on only signed ROMs may be flashed, when S-off unsigned ROMs may be flashed IE custom ROMs.
Click to expand...
Click to collapse
Also check out this thread it will answer some of your questions.
Read this before posting. MT4G Slide Compendium
revo420 said:
HYUH at team revolutionary has discovered that the new bootloader from latest OTA has hboot protection similar to Evo 3D. HYUH has also written a version of misc_version that writes to the correct partition for our doubleshot. Link here. Downgrade still doesn't work because when it checks hboot version it realizes its older and will abort.
PLEASE DONATE TO TEAM REVOLUTIONARY TO MOTIVATE THEM TO RELEASE MORE GREAT TOOLS, EXPLOITS, AND MORE!
Click to expand...
Click to collapse
My hboot is 1.45:0013 so I'm guessing I can't root my phone
Sent from my myTouch_4G_Slide using XDA App
wellingtonarmelin said:
My hboot is 1.45:0013 so I'm guessing I can't root my phone
Sent from my myTouch_4G_Slide using XDA App
Click to expand...
Click to collapse
correct. the only possible way to root is if your HBOOT happens to be S-OFF, in which case you could downgrade and then root. there is some work being done, but i don't know that anything has quite worked yet.
How do I downgrade software
Sent from my myTouch_4G_Slide using XDA App
wellingtonarmelin said:
How do I downgrade software
Sent from my myTouch_4G_Slide using XDA App
Click to expand...
Click to collapse
Are you trying to root and if so just root the old way. I tried it and it works.
Yeah I'm trying to root but at the top of my hboot it says locked and I'm not on the h boot everyone else has
Sent from my myTouch_4G_Slide using XDA App
wellingtonarmelin said:
Yeah I'm trying to root but at the top of my hboot it says locked and I'm not on the h boot everyone else has
Sent from my myTouch_4G_Slide using XDA App
Click to expand...
Click to collapse
Does it day S-ON or S-OFF? If S-ON then you're stuck for now, until one of the tools comes thru.
Lol I'm stuck for now dang that sucks
Sent from my myTouch_4G_Slide using XDA App
wellingtonarmelin said:
Lol I'm stuck for now dang that sucks
Sent from my myTouch_4G_Slide using XDA App
Click to expand...
Click to collapse
lol, yeah it does. we're definitely bugging all the people we can to get something happening tho.
Lol please do I kind of regret sending my old my touch back it was rooted
Sent from my myTouch_4G_Slide using XDA App
There are extremely capable people working on it. Team revolutionary are aware of what's going on. Now its just a matter of being patient.
Sent from my myTouch_4G_Slide using XDA App
That's cool with me
Sent from my myTouch_4G_Slide using XDA App
I'm guessing its still not away to root your phone if you have the new hboot with s on?
Sent from my myTouch_4G_Slide using XDA App
Related
You Must Be Rooted With S-OFF To Do This!
Seeing how there is no way to root 4.24 yet, I thought I would throw a little something together in case anyone needs to unroot before taking their phone into Sprint. This will return your phone to stock with S-ON while leaving a backdoor to reroot with. I have tested this as best I can without actually upgrading my hBoot (I want to keep the eng hboot), but there are no guarantees you won't run into issues. You also must flash the modified PC36IMG before setting S-ON in order for this to work.
While it would be trivial to create a script to automate this process, I wanted to make sure you know exactly what this does so it is easier to re-root. Plus there's no fun in having a script do all the work.
I've included all the files needed to use ADB and Fastboot on Windows, Linux and Macs. They have been renamed to match the operating system (eg. ADB for Windows is adbw, fastboot for Linux is fastbootl) and you may need to set the correct permissions in order to use them.
You will need:
Unrevoked Forever - The latest version of Unrevoked's S-OFF and S-ON tools
E4GUnroot.zip - The modified 4.24.651.1 PC36IMG zip and an unpacked copy of Amon RA's 1.8 recovery
Basic knowledge about ADB and Fastboot
Plenty of Battery Life
A little common sense
Click to expand...
Click to collapse
How To Unroot:
Make a Nandroid with the Boot, System and Data partitions along with your .android folder.
Make sure you have Radio S-OFF and not S-OFF from the ENG hBoot. If your bootloader shows SHIP S-OFF you should be good, if it shows ENG S-OFF then you will want to run Unrevoked Forever to make sure S-OFF is set from the radio.
Use ADB to reboot into RUU mode.
Code:
adb reboot oem-78
Once in RUU mode flash the PC36IMG. Be very careful that you do not interrupt it, doing so can easily result in the permanent bricking of your phone.
Code:
fastboot flash zip PC36IMG_4.24.651.1_Rootable.zip
Watch the output and make sure it completes correctly. If you get an error saying something about "remote 90: hboot pre-update" flash it again.
When it's finished flashing reboot and make your way into the Recovery.
Code:
fastboot reboot
--or--
fastboot reboot-bootloader
The recovery may show a green arrow for a few moments, wait for it to turn into the Red Triangle with an Exclamation Mark inside of it. Then push Amon RA's recovery to the phone and bring up the UI.
Code:
adb push amon_ra_1.8-mod /
adb shell "busybox --install /sbin"
adb shell "nohup /sbin/recovery &"
Now that the Recovery is up, use it to flash Unrevoked's S-ON tool.
You are now fully unrooted with S-ON! After you remove your SD card there will be nothing on your phone to show it was rooted.
Click to expand...
Click to collapse
How To Root Again:
Reboot into the Recovery and bring up Amon RA's recovery.
Run Unrevoked's S-OFF tool to unlock the NAND.
Flash your Recovery of choice and use it to restore your Nandroid
And that's it! You should be good to go again.
Click to expand...
Click to collapse
As always, you and you alone are responsible for everything you do to your phone. This is for informational purposes only; neither XDA nor I can be held responsible for anything that happens as a result of doing this.
Click to expand...
Click to collapse
Reserved...
I won't have to use this method, being rooted already, but will definitely help a lot of people. Also VERY clear, do good job man.
Agreed, great and useful guide.
Sent from my PC36100 using XDA Premium App
Good job and very educated post.
Just figured it may come in handy to someone, I had to unroot mine a few times to take it in to Sprint and I always did something similar to this to make it easier to reroot. If you wanted too you could even restore your data partition from a nandroid and remove all the root apps, that way your phone is still how you like it just unrooted for the time being.
Thank you sir. Very informative and useful post..
I have a question about this since it seems what your describing may help me. Since I got my E3d I have been playing around with my e4g and I upgraded mt hboot not realizing it would turn s-on. I know I'm still rooted since i have flashed at least 3 custom roms since then. I am on cm7.3 currently. For my case would using the unrevoked s-on/s-off tool to turn s-off work?
Great job here, hope I never have to use this though but should help many that need to take in their phone for service.
XpAcErX said:
I have a question about this since it seems what your describing may help me. Since I got my E3d I have been playing around with my e4g and I upgraded mt hboot not realizing it would turn s-on. I know I'm still rooted since i have flashed at least 3 custom roms since then. I am on cm7.3 currently. For my case would using the unrevoked s-on/s-off tool to turn s-off work?
Click to expand...
Click to collapse
Try using unrevoked forever from the recovery. If your radio is updated it may not let you do it but it's worth a try
Sent from my PG86100 using XDA Premium App
xHausx said:
Try using unrevoked forever from the recovery. If your radio is updated it may not let you do it but it's worth a try
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
Thanks for the reply but i see from their site that 2.15.00.05.02 is not on the supported list.
XpAcErX said:
Thanks for the reply but i see from their site that 2.15.00.05.02 is not on the supported list.
Click to expand...
Click to collapse
Yeah, you'll most likely need to downgrade it first. I won't be getting home till late tonight or early in the morning but when I do I'll try to put some stuff together for you to downgrade with
Do you use a pc or linux?
Sent from my PG86100 using XDA Premium App
xHausx said:
Yeah, you'll most likely need to downgrade it first. I won't be getting home till late tonight or early in the morning but when I do I'll try to put some stuff together for you to downgrade with
Do you use a pc or linux?
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
Thanks for your help, I have a pc.
Okay Haus. Now root my evo. Lol.
You can do it
Ill give you a hug from far away.
Sent from my PC36100 using Tapatalk
XpAcErX said:
Thanks for your help, I have a pc.
Click to expand...
Click to collapse
Sent a pm
tommytomatoe said:
Okay Haus. Now root my evo. Lol.
You can do it
Ill give you a hug from far away.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
You mean you lost root too? I'm working it but unfortunately I haven't had that much free time to do it. I get the feeling it won't be too much longer now though.
xHausx said:
Sent a pm
Click to expand...
Click to collapse
Thanks, I'll dl and try it tonight.
hey xHausx
I've been with my Evo since the beginning so I have no issues, but a friend of mine just bought the Evo. Unfortunately, his came with gingerbread with 4.24.651. Since his is not rooted to begin with, we can't unroot and reroot, so is it safe to assume that this method will not work? If so, are there any known methods to root? thanks in advance....
heyman123 said:
so is it safe to assume that this method will not work? If so, are there any known methods to root? thanks in advance....
Click to expand...
Click to collapse
Correct assumption and nope. Join the masses over in Q&A and General posting about this daily.
github said:
Correct assumption and nope. Join the masses over in Q&A and General posting about this daily.
Click to expand...
Click to collapse
thanks for the response.
hmmm... well, all I can say is...... bummer! to my friend
aaaaaaand I'm back to s-off, thanks haus!
my h-boot version was 18 then when i flashed android revolution rom it went to a 17. (not exact numbers but thats not really the point) I was just wondering what the H-boot version really has to do with my device itself. Or would i need to be able to switch it back to original state at some point
rddocke said:
my h-boot version was 18 then when i flashed android revolution rom it went to a 17. (not exact numbers but thats not really the point) I was just wondering what the H-boot version really has to do with my device itself. Or would i need to be able to switch it back to original state at some point
Click to expand...
Click to collapse
Hboot is on a separate partition than rom. When you go from stock to rooted your hboot might change, depending on the root method.
Flashing a rom won't change it. Reverting to stock with an ruu will.
Sent from my HTC Glacier using xda premium
rddocke said:
my h-boot version was 18 then when i flashed android revolution rom it went to a 17. (not exact numbers but thats not really the point) I was just wondering what the H-boot version really has to do with my device itself. Or would i need to be able to switch it back to original state at some point
Click to expand...
Click to collapse
You're good to go, that's how's it suppose to be. Make sure you have supercid, and also if you have time search in devolpement section for Bin4ry and flash Eng Hboot to be safe.
epsix said:
You're good to go, that's how's it suppose to be. Make sure you have supercid, and also if you have time search in devolpement section for Bin4ry and flash Eng Hboot to be safe.
Click to expand...
Click to collapse
Thanks for4 the replies guys i havent messed with CID yet or Eng. currently running ARHD 3.6.0 i havent had any troubles rooting or flashing and speeds seem to be doing well.. i am still working on maximizing my battery life. its good i get about 15 hours when im not on wifi.
but how will Eng and CID help out?
Those are just gonna help you in the long run without bricking your phone if you do alot of flashing. Nothing to do with battery. Lol
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA Premium App
rddocke said:
Thanks for4 the replies guys i havent messed with CID yet or Eng. currently running ARHD 3.6.0 i havent had any troubles rooting or flashing and speeds seem to be doing well.. i am still working on maximizing my battery life. its good i get about 15 hours when im not on wifi.
but how will Eng and CID help out?
Click to expand...
Click to collapse
Engineering hboot allows you to flash recovery and radio at a more basic level and can help you recover from a ****ed up state in some cases. Good idea to have.
Super CID just allows you to flash an ruu from another carrier and is completely unnecessary if you're flashing custom roms.
Sent from my HTC Glacier using xda premium
epsix said:
Those are just gonna help you in the long run without bricking your phone if you do alot of flashing. Nothing to do with battery. Lol
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA Premium App
Click to expand...
Click to collapse
Hmm I'll look into it some more got any referrals for my research?
And ya I was just making a comment on my battery life I didn't think any of this would have an effect on battery life. Just pointing out successes. Fortunately haven't faced too difficult a situation with the sensation.
Now the galaxy s 2 on group via mini kies, bow that was a pain. Again thanks
Phateless said:
Engineering hboot allows you to flash recovery and radio at a more basic level and can help you recover from a ****ed up state in some cases. Good idea to have.
Super CID just allows you to flash an ruu from another carrier and is completely unnecessary if you're flashing custom roms.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I mean how much more basic could it get then flashing under CWM? If there's a simpler way I'm all for it lol.
But seriously ill look into it some more I just figured dont fix what ain't broken you know?
Flashing the radio/recovery isn't done via CWM - it's done using fastboot commands
EddyOS said:
Flashing the radio/recovery isn't done via CWM - it's done using fastboot commands
Click to expand...
Click to collapse
I was speaking of simplicity in general I'm just curiouse to what this more basic level would be. I did just fine with the flashing of o_10.58.9035.00U_10.15.9035.02_2 without adb
rddocke said:
I was speaking of simplicity in general I'm just curiouse to what this more basic level would be. I did just fine with the flashing of o_10.58.9035.00U_10.15.9035.02_2 without adb
Click to expand...
Click to collapse
It provides you some extra options if something goes wrong.
Phateless said:
It provides you some extra options if something goes wrong.
Click to expand...
Click to collapse
Ok cool thanks boss.
Is there anything to look for in a radio or zip before flashing that would tip me off to potential brickage or do you have to kinda just experience it?
rddocke said:
Ok cool thanks boss.
Is there anything to look for in a radio or zip before flashing that would tip me off to potential brickage or do you have to kinda just experience it?
Click to expand...
Click to collapse
Make SURE it's the right radio for your device and check md5sum. Do a google search, md5sum is easy.
Sent from my HTC Glacier using xda premium
Phateless said:
Make SURE it's the right radio for your device and check md5sum. Do a google search, md5sum is easy.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Gotcha thanks. Also I'm sure there is a difference between eng s-off and the s-off using revolutionary.io since your here and we talkin about it, you have a definition for me in basic terms? Perhaps a link to someplace? I been looking in google but they start talking about ship s-off and radio s-off, I'm not sure what s-off I've done. I just knew it was necessary before perm rooting.
rddocke said:
Gotcha thanks. Also I'm sure there is a difference between eng s-off and the s-off using revolutionary.io since your here and we talkin about it, you have a definition for me in basic terms? Perhaps a link to someplace? I been looking in google but they start talking about ship s-off and radio s-off, I'm not sure what s-off I've done. I just knew it was necessary before perm rooting.
Click to expand...
Click to collapse
Revolutionary does radio s-off which means the phone itself has security turned off and whatever hboot you have will display that. Eng s-off means the hboot is allowing the security bypass. Ship s-off just means it came that way from factory.
My understanding is somewhat rudimentary so I would appreciate one of the elders stepping in to clarify if I've missed anything.
We need s-off to give hboot permission to flash a custom recovery. Then we use the custom recovery because it permits us to make changes to the firmware, like the update that gave us root access.
The hierarchy goes radio, hboot, recovery, rom. Each is on a separate partition.
Sent from my HTC Glacier using xda premium
Phateless said:
Revolutionary does radio s-off which means the phone itself has security turned off and whatever hboot you have will display that. Eng s-off means the hboot is allowing the security bypass. Ship s-off just means it came that way from factory.
My understanding is somewhat rudimentary so I would appreciate one of the elders stepping in to clarify if I've missed anything.
We need s-off to give hboot permission to flash a custom recovery. Then we use the custom recovery because it permits us to make changes to the firmware, like the update that gave us root access.
The hierarchy goes radio, hboot, recovery, rom. Each is on a separate partition.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Wow ok that was very helpful. Looks like this is turning into quite a decent thread. I appreciate you for your knowledge spread.
I would like to see (as you put it) one of the elders step in here with their feedback as well.
I'm gonna go ahead and move to the next step (eng) and see where that will take me in my adventures of the sensation.
I am also interested to hear from other members about their achievements with their devices as far as CPU speeds and of the many tricks that can performed by the sensation. I find myself searching for that info all day.
has anybody tried downloading the stock rom from this thread:
http://forum.xda-developers.com/showthread.php?t=1178082
then renaming it to pg59img.zip, putting it onto the root of your sd card, turning off the phone and holding the power and vol dn buttons and letting it flash that way?
then, just follow normal procedure for s off and root that is also posted here in the forums.
i'm pretty sure the package overwrites the hboot, also, unless this is disabled with the new version.
would somebody try that and let me know?
S off is permanent l. Even if you flash a newest bootloader
What I meant was that there seems to be some people having trouble obtaining s off and maybe rooting with the latest hboot/update. If you were to simply roll it all back by flashing a pg59img file from that stock rom, it would put it back to a workable state. Correct? I don't have the latest update/hboot and I already have s off so I cannot test myself.
Sent from my myTouch_4G_Slide using XDA App
Pretty sure someone(s) reported it not working like that, because the version is too far out of date and fails the check.
I wish I had one S-ON so I could play too.
Blue6IX said:
Pretty sure someone(s) reported it not working like that, because the version is too far out of date and fails the check.
I wish I had one S-ON so I could play too.
Click to expand...
Click to collapse
yep, i remember people with S-ON not being able to downgrade with the RUU.
looking back thru the inital update thread, jonnycat26 threw out the suggestion of possibly using a goldcard to get past the S-ON..... any possibility of this at all? i don't know a whole lot about that process, but i did use it on my friend's dad's Inspire 4G. i'll do a little reading and see what exactly the idea behind it is.
Blue6IX said:
Pretty sure someone(s) reported it not working like that, because the version is too far out of date and fails the check.
I wish I had one S-ON so I could play too.
Click to expand...
Click to collapse
DRAT!!! I feared something like that. Well, it was worth a shot anyway. What about writing/pushing with adb?
Sent from my myTouch_4G_Slide using XDA App
i was wondering if there is a way to do this. ??
im tired of my MTS4G, i want to install a good rom!
Amen to that
Sent from my myTouch_4G_Slide using Tapatalk
As of right now no, were all basically stuck. Htc say they'll release a update at the end of the month to allow unlocking but that will void your warranty. Im just waiting for a crack for this version. Shouldn't Be too long i hope.
Sent from my myTouch_4G_Slide using Tapatalk
I did not realize that this phone still had an unlocked bootloader when I purchased it a few days ago. It's unfortunate how the HTC Unlocker was glitchy with the MT4GS; it might be why there's such a lack of development right now, haha.
ac3theone said:
As of right now no, were all basically stuck. Htc say they'll release a update at the end of the month to allow unlocking but that will void your warranty. Im just waiting for a crack for this version. Shouldn't Be too long i hope.
Sent from my myTouch_4G_Slide using Tapatalk
Click to expand...
Click to collapse
i hope!! i dont care about the warranty, i hate the stock the sence , is so slow and i hate the interface, im comming from a vibrant runing ics passion v12, you can only imagine my frustration .
Limewirelord said:
I did not realize that this phone still had an unlocked bootloader when I purchased it a few days ago. It's unfortunate how the HTC Unlocker was glitchy with the MT4GS; it might be why there's such a lack of development right now, haha.
Click to expand...
Click to collapse
I think we can start shelving the idea that there's a lack of dev for the device - some definite strides being made in that direction now.
We could always use more people helping make stuff, though.
----
I need a copy of an S-ON bootloader that has not been unlocked.
I need both S-ON 1.44.0007 and S-ON 1.45.0013 - if anyone can get either to me that would be great.
They are only 1MB in size and can be attached to a post in the forum.
If you can get it - attach it as a reply to this post:
http://forum.xda-developers.com/showthread.php?t=1254518
The terminal command to back up a copy of it is:
Code:
dd if=/dev/block/mmcblk0p12 of=/sdcard/hboot.img
That will place a copy of your hboot on your sdcard, called hboot.img, if run from a terminal.
Nlarge got his unlocked S-ON bootloader added to that thread, now we need some regular S-ON ones to compare them to. If anyone can figure out how to get one to us it would be helpful.
We are trying to work the S-ON issue, but it's not exactly an easy nut to crack and we've mostly just started.
Thanks for any help that can be provided. This may not be all we need, but it's a start.
Hasn't anyone been able to flash the original PG59IMG.zip via the OTAbootloader patch?
Delivered via candygram for Mr. Mongo.
Blue6IX said:
I need a copy of an S-ON bootloader that has not been unlocked.
I need both S-ON 1.44.0007 and S-ON 1.45.0013 - if anyone can get either to me that would be great.
They are only 1MB in size and can be attached to a post in the forum.
If you can get it - attach it as a reply to this post:
http://forum.xda-developers.com/showthread.php?t=1254518
The terminal command to back up a copy of it is:
Code:
dd if=/dev/block/mmcblk0p12 of=/sdcard/hboot.img
That will place a copy of your hboot on your sdcard, called hboot.img, if run from a terminal.
Click to expand...
Click to collapse
I'll see if I can figure out how to get that to you. If I can't code, at least I can help with other things.
Cool, we'll look it over and see what we come up with. No promises, just gonna look and see what we see and hope it leads to something.
The hboot may or (more likely) may not be the whole problem for s-off/s-on, but the more we have to play with the more we are learning.
Blue6IX said:
Cool, we'll look it over and see what we come up with. No promises, just gonna look and see what we see and hope it leads to something.
The hboot may or (more likely) may not be the whole problem for s-off/s-on, but the more we have to play with the more we are learning.
Click to expand...
Click to collapse
I tried to copy it with (adb shell <command>) but it says I have permission denied.
Limewirelord said:
I tried to copy it with (adb shell ) but it says I have permission denied.
Click to expand...
Click to collapse
Okay, we are working on that, etn4off is leading the charge on adb through stock recovery, so hold that thought.
Meantime, i've whipped up a new version of the stock restore .zip file, that should work on the new OTA.
( Make sure you have a full battery first!)
Edit - didn't work
What you have to do is rename the file to:
PG59IMG.zip
...then place on the main directory of your sdcard.
Make sure fastboot is turned off in settings on the phone, and then power off.
Hold Volume Down and press Power to turn it on, booting into hboot. The installer will take over from there and guide you through it.
It will load itself, then ask you to press Volume UP to install - then does it's thing and will tell you to press power to reboot when it is done.
This is basically the same restore file you get from here: Thread Link updated for the new OTA.
This should solve the version mismatch problem people were having, but won't know until someone tries to install it.
Afterwards you can run Revolutionary to S-OFF your 1.44.0007 hboot.
You will no longer be on the newest OTA, but then you can apply it if you want and go back - as long as you run the Revolutionary process on the 1.44.0007 hboot before you do.
I'm going to try this asap
Sent from my myTouch_4G_Slide using Tapatalk
Blue6IX said:
Okay, we are working on that, etn4off is leading the charge on adb through stock recovery, so hold that thought.
Meantime, i've whipped up a new version of the stock restore .zip file, that should work on the new OTA.
( Make sure you have a full battery first!)
Stock_Retail_OTA_1-55-531-3_downgrade_PG59IMG.zip
Download link
MD5: c7ea224be738b14824a003fd9c9b4b19
What you have to do is rename the file to:
PG59IMG.zip
...then place on the main directory of your sdcard.
Make sure fastboot is turned off in settings on the phone, and then power off.
Hold Volume Down and press Power to turn it on, booting into hboot. The installer will take over from there and guide you through it.
It will load itself, then ask you to press Volume UP to install - then does it's thing and will tell you to press power to reboot when it is done.
This is basically the same restore file you get from here: Thread Link updated for the new OTA.
This should solve the version mismatch problem people were having, but won't know until someone tries to install it.
Afterwards you can run Revolutionary to S-OFF your 1.44.0007 hboot.
You will no longer be on the newest OTA, but then you can apply it if you want and go back - as long as you run the Revolutionary process on the 1.44.0007 hboot before you do.
Click to expand...
Click to collapse
Has anyone tried this? Not that im saying its bad i just dont want to mess up my newest toy...lol
Sent from my myTouch_4G_Slide using Tapatalk
izzy001 said:
Has anyone tried this? Not that im saying its bad i just dont want to mess up my newest toy...lol
Sent from my myTouch_4G_Slide using Tapatalk
Click to expand...
Click to collapse
No. That's why I said we won't know until someone tries.
I've run the package on both of my devices, so can attest to it working - but they are both s-off.
I've run it from the device in the newest OTA form, and it brought me back, but the old package did too - seems no version check on my devices (probably any s-off devices)
I've run from all versions of the hboot - 1.44.0006, 1.44.0007, 1.44.1107, and 1.45.0013, but they were all s-off.
As for what happens with an s-on device... ...? I updated the version because in another thread that was pinpointed as the problem for it not installing on the newest OTA.
Blue6IX said:
No. That's why I said we won't know until someone tries.
I've run the package on both of my devices, so can attest to it working - but they are both s-off.
I've run it from the device in the newest OTA form, and it brought me back, but the old package did too - seems no version check on my devices (probably any s-off devices)
I've run from all versions of the hboot - 1.44.0006, 1.44.0007, 1.44.1107, and 1.45.0013, but they were all s-off.
As for what happens with an s-on device... ...? I updated the version because in another thread that was pinpointed as the problem for it not installing on the newest OTA.
Click to expand...
Click to collapse
Well i tried it... But it didnt even see it as an update... It just checked it and went straight to the hboot menu
Sent from my myTouch_4G_Slide using Tapatalk
izzy001 said:
Well i tried it... But it didnt even see it as an update... It just checked it and went straight to the hboot menu
Sent from my myTouch_4G_Slide using Tapatalk
Click to expand...
Click to collapse
Okay thanks, it was pretty much an 'it will do it or it won't' situation, so we'll have to try something else.
I wish I could get an s-on device in my hands that I could try stuff on - for now it's test and test and test on the s-off, then try on the s-on ...
Sorry it didn't work, we'll have to try another way.
I'll give this a try as well, even though it supposedly doesn't work. Better try than not.
Is what you're trying to do make the older ROM (with the 1.44.0007 HBOOT) appear as an update to the newer update so we can, in a way, downflash to the older HBOOT that's compatible with the Revolutionary tool?
I'm kind of new to the whole Android scene and am just curious as to how things work.
Limewirelord said:
I'll give this a try as well, even though it supposedly doesn't work. Better try than not.
Is what you're trying to do make the older ROM (with the 1.44.0007 HBOOT) appear as an update to the newer update so we can, in a way, downflash to the older HBOOT that's compatible with the Revolutionary tool?
I'm kind of new to the whole Android scene and am just curious as to how things work.
Click to expand...
Click to collapse
If this flashes it should revert the phone back to retail launch - but it's probably not going to. Finding a way to force it could have a less then desirable outcome.
If it doesn't take, don't try to force the issue with it unless you know what you're doing and why.
Well I tried it as well and it got a check, but it didn't install anything. I wish I had the know-how to mess around with this stuff.
Limewirelord said:
Well I tried it as well and it got a check, but it didn't install anything. I wish I had the know-how to mess around with this stuff.
Click to expand...
Click to collapse
When it checks and oks it go to recovery in hboot menu
Sent from my myTouch_4G_Slide using Tapatalk
A friend of mine asked if I could help him fix his phone. He is a noob and so am I but I have rooted several phones and flashed many ROMS on all sorts of phones with no issues. So I would a least say I am pretty tech savvy. Here is the dilemma- If I hold volume down and power I get a white screen with some options such as hboot, fastboot, recovery, factory reset, simlock & image crc. It also says S-On....which I believe is the problem. He says that he though he downgraded to 2.2 before rooting but couldn't be sure but says he was originally on 2.3.4. I can boot into recovery CWM, mount usb/SD and load roms but no matter what ROM I load it will never get passed the HTC screen. Can someone tell me or at least point me in the right direction as to how I can achieve S-Off? Also I must note that he made no backups prior to his rooting attempt (Ughhhh!). Is there an easy way to get S-Off when the phone seems to be unlocked, rooted & CMW installed? Thanks a bunch my fellow XDA Einsteins.
I didn't think you can have a recovery without s-off for the shift... You could run an RUU and use one of the root guides we have if someone with more experience can't cone up with an idea. Of he did downgrade to 2.2 he should of used the shiftrr.exe to root
Sent from my EVO using Tapatalk 2
YoungCorruptionV2.0 said:
I didn't think you can have a recovery without s-off for the shift... You could run an RUU and use one of the root guides we have if someone with more experience can't cone up with an idea. Of he did downgrade to 2.2 he should of used the shiftrr.exe to root
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
You can with an unlocked boot loader.
VICODAN said:
You can with an unlocked boot loader.
Click to expand...
Click to collapse
Oh really? I didn't know that
Sent from my EVO using Tapatalk 2
YoungCorruptionV2.0 said:
Oh really? I didn't know that
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
http://wiki.cyanogenmod.com/wiki/Fastboot
It's in my root thread.
VICODAN said:
http://wiki.cyanogenmod.com/wiki/Fastboot
It's in my root thread.
Click to expand...
Click to collapse
Ah good to know. I never read your thread no offense since I rooted on 2.2
Sent from my EVO using Tapatalk 2
YoungCorruptionV2.0 said:
Ah good to know. I never read your thread no offense since I rooted on 2.2
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
No worries, no need. Not offended.
Sounds like something got screwed up during the RUU process of downgrading. I've run into a similar issue when running the ROM Update Utility and it put me back to s-on but It kept my custom recovery. Same thing, no matter what I flashed I couldn't get it to boot. Your best bet is probably going to be run the the RUU. It will depend on which version of bootloader is on the device to which RUU will work. I can't remember the specific number but I believe the 2.2 bootloader is something like 93xxx something or another. If that's the case then you should be able to run the old RUU, putting your back on 2.2 and continue rooting. If your bootloader version is higher (98xxx or something) you'll have to run the newest RUU in order for it to work.
I may be completely wrong here but when all else fails... RUU!
Sent from my ELTE using Tapatalk 2
crump84 said:
Sounds like something got screwed up during the RUU process of downgrading. I've run into a similar issue when running the ROM Update Utility and it put me back to s-on but It kept my custom recovery. Same thing, no matter what I flashed I couldn't get it to boot. Your best bet is probably going to be run the the RUU. It will depend on which version of bootloader is on the device to which RUU will work. I can't remember the specific number but I believe the 2.2 bootloader is something like 93xxx something or another. If that's the case then you should be able to run the old RUU, putting your back on 2.2 and continue rooting. If your bootloader version is higher (98xxx or something) you'll have to run the newest RUU in order for it to work.
I may be completely wrong here but when all else fails... RUU!
Sent from my ELTE using Tapatalk 2
Click to expand...
Click to collapse
Yes, you know when I water damaged my phone I (stupidly) was trying to RUU it while trying to fix it and the RUU failed and I got to a point where RUU was telling me that a newer version is installed.
Well the way I fixed it was by running RUU 2.3.4. All worked good after that.
Please refer to my post about how to flash misc.img in recovery since you can't get past the htc screen and this will allow you to get downgraded. If I can the post it's around here somewhere and I'll post a link to it.
Edit: here it is
http://forum.xda-developers.com/showpost.php?p=27695411&postcount=254
Sent from my PG06100 using xda premium
sparksco said:
Please refer to my post about how to flash misc.img in recovery since you can't get past the htc screen and this will allow you to get downgraded. If I can the post it's around here somewhere and I'll post a link to it.
Edit: here it is
http://forum.xda-developers.com/showpost.php?p=27695411&postcount=254
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
I found the post it's on Vicodan's thread