[WIP]Temp-root Gingerbread EVOs - EVO 4G General

my evo is rooted already and i havent paid much atention since i got my 3d but was there an HBOOT update in the GB OTA as compared to the last Froyo 3.70?
If there wasnt, anyone should be able to a simple downgrade with a previous RUU and then use any of the working root methods for froyo.
just a thought i had while being bored.

Nope, new bootloader is locked. Cant downgrade.

EVOlvedAndroid said:
Nope, new bootloader is locked. Cant downgrade.
Click to expand...
Click to collapse
so there was a bootloader update?

I really don't even know what to say anymore. I give up. Someone else can do it.

github said:
I really don't even know what to say anymore. I give up. Someone else can do it.
Click to expand...
Click to collapse
+1 thats all i have to say about that

what about replacing the system.img in in the latest pc36img with one from the last froyo? if the bootloader stays intact it should flash the froyo sys image and then you could at lease have temp root

t3project said:
what about replacing the system.img in in the latest pc36img with one from the last froyo? if the bootloader stays intact it should flash the froyo sys image and then you could at lease have temp root
Click to expand...
Click to collapse
The short version is there is no way around or tricking the bootloader. Pretty much every way imaginable to do this has been tried a bunch of times. We need to find a new exploit to get in. Several devs are working on it and itay happen soon. Seems to be more problematic than any one expected.

firket2000 said:
The short version is there is no way around or tricking the bootloader. Pretty much every way imaginable to do this has been tried a bunch of times. We need to find a new exploit to get in. Several devs are working on it and itay happen soon. Seems to be more problematic than any one expected.
Click to expand...
Click to collapse
yes, but you're not tricking the bootloader. the bootloader remains the same. the sys image is all you are changing and the signatures should remain intact if it is pulled out of a froyo ruu. for that matter even try placing a rooted OTA sys image in it. this would not gain s-off but you could run a shell root and su if it would work.

t3project said:
what about replacing the system.img in in the latest pc36img with one from the last froyo? if the bootloader stays intact it should flash the froyo sys image and then you could at lease have temp root
Click to expand...
Click to collapse
As far as I understand, the new bootloader won't allow for downgrading or flashing anything that doesn't match HTCs signature....so modifying files is out of the question....
Sent from my PC36100 using XDA App

t3project said:
what about replacing the system.img in in the latest pc36img with one from the last froyo? if the bootloader stays intact it should flash the froyo sys image and then you could at lease have temp root
Click to expand...
Click to collapse
Can't do that, it would break HTC's signature and the bootloader would not accept it

I need to save this response in a text file so I can just copy and paste it every day.
You can't modify the contents of a RUU provided by HTC on an S-ON HBOOT. The zip is signed by HTC with their private key. The HBOOT has the public key. Changing just 1 bit on the zip will invalidate the private key and HBOOT won't allow it to flash. This is the reason for wanting S-OFF, so you can flash anything via HBOOT (Recovery, for example) without any signature checks.
You also can't downgrade the HBOOT, as it will give you an error about an earlier version.
All the obvious ideas have been tried, over and over again over the past few months since the new update hit.
If you are still confused, please see this article on Wikipedia about Public Key Cryptography.

Don't forget to add that goldcards and battery pull microsd swaps do not work either.

Well, eff. I switched back to Sprint and back to the EVO today after a (very unpleasant) experience with T-MO and the G2X, only to find out my brand new EVO is already on Gingerbread and can't be rooted, ruling out the best part about owning an EVO... all the awesome custom ROMs. Lovely.

There's been all types of shenanigans occurring trying to root this thing. Including physically planting in the ground. No root from that either. Appreciate where you're coming from and trying to help and all though

jjones1983 said:
Well, eff. I switched back to Sprint and back to the EVO today after a (very unpleasant) experience with T-MO and the G2X, only to find out my brand new EVO is already on Gingerbread and can't be rooted, ruling out the best part about owning an EVO... all the awesome custom ROMs. Lovely.
Click to expand...
Click to collapse
Its being worked on right now so no worries
Sent from my PC36100 using XDA App

I'm rooted but jw is there any news on when that source will be out?
My stupid friends at work wouldn't let me root their froyo and now want to pay me to root their gb I don't even want $ .
Sent from my PC36100 using XDA App

Related

ATTN Rom Cooks

If anyone is interested in assisting me in making a new rom, for our NOW rooted phones. Please let me know.
Lucky you
binny1007 said:
Lucky you
Click to expand...
Click to collapse
lol I was just thinking the same thing...
working on it already jcase
zifnab06 said:
working on it already jcase
Click to expand...
Click to collapse
...............
im on it. i promised i would. so all we need now is a recovery
NO BUENO!
its our luck tho, a week after we get a leak of 2.1 .. tadaaaaa the device is rooted.
this make socal mad!
SoCalSpecialist said:
NO BUENO!
its our luck tho, a week after we get a leak of 2.1 .. tadaaaaa the device is rooted.
this make socal mad!
Click to expand...
Click to collapse
+1 im in the same boat. i upgraded my eris thinking root was going to take a while longer and didnt want to wait. my understanding also was that the devs gave up on 1.5 root and were instead working on 2.1 leaked root. oh well. i can either wait for 2.1 downgrade or another root for 2.1. or my more likely scenario is to go out and get the Nexus 1 on the 23rd when it is supposedly coming to verizon.
SoCalSpecialist said:
NO BUENO!
its our luck tho, a week after we get a leak of 2.1 .. tadaaaaa the device is rooted.
this make socal mad!
Click to expand...
Click to collapse
What would top off the cake is if HTC released the OTA right now.
If your a chef, and want, I have a list (and files) of what I want added, and the base image.
I want the bootloader from our ROOT rom, the contents of /system/xbin from the ROOT rom and everything else from the leak rom.
Correct me if I am wrong, but that should give us
the s = off boot loader, su and other programs from xbin, and finally a more stable system.
jcase
jcase said:
If your a chef, and want, I have a list (and files) of what I want added, and the base image.
I want the bootloader from our ROOT rom, the contents of /system/xbin from the ROOT rom and everything else from the leak rom.
Correct me if I am wrong, but that should give us
the s = off boot loader, su and other programs from xbin, and finally a more stable system.
jcase
Click to expand...
Click to collapse
That's not much to ask for. lol. Why the bootloader and xbin from the root rom though, why not just remove boot.img from the leaked rom and add SU to it and flash it?
Or better yet, build AOSP from source and add the 2.1 Eris drivers from the leaked ROM, and make a Nexus One replica ROM for the Eris?
ECLIPS3 said:
+1 im in the same boat. i upgraded my eris thinking root was going to take a while longer and didnt want to wait. my understanding also was that the devs gave up on 1.5 root and were instead working on 2.1 leaked root. oh well. i can either wait for 2.1 downgrade or another root for 2.1. or my more likely scenario is to go out and get the Nexus 1 on the 23rd when it is supposedly coming to verizon.
Click to expand...
Click to collapse
Actually.... they didnt root 1.5 supposedly based on the official root is here thread
caboos3 said:
As to how this was found / done, I quote myself from IRC:
"<caboose> Lets just say i happened to come buy this SIGNED pre-rooted ROM while strolling the dungeons of the HTC building in taiwan (its true, i had to slay a dragon too.)"
We will post the ROM in question soon, just making sure there aren't any fatal bugs etc.
Click to expand...
Click to collapse
somone came across a rooted version of the 2.1 ROM so we just have to wait for somone to figure out a way to get the 2.1 leak to "downgrade".
this is all because the rooted rom has a build of 2.19.605.1 Test Keys and the Leaked rom has a build number of 2.26.605.2 Release Keys which in turn makes it a down grade because the rooted ROM is 7 builds lower then the leaked ROM.
my thought would be can somone get into a hex editor and change the build number to a higher version without jacking the checksum and ruining the ROM. maybe that would allow a "downgrade".
but back on topic.... it appears that 1.5 was not rooted at all based on Caboos3's statement
on the subject of rom cooking, i have never done it but am interested and would be willing to do what i could to help out.
ive got a 2.1 rooted eris
iron changing it with the hex number will screw up the checks.
apreichner
the bootloader has secure off, thats what i want it
busybox is userful
xbin has su, scp and other things i want.
i knew it would... but i wonder if there is a way to do it and preserve checks.
im not sure how checksum algoritims work so i dont know if theres a way to offset the change.
the only hex editing ive ever done with files only required me to ensure the file read the same size so minor changes were possible and a single digit change would be a minor change.
jcase said:
iron changing it with the hex number will screw up the checks.
apreichner
the bootloader has secure off, thats what i want it
busybox is userful
xbin has su, scp and other things i want.
Click to expand...
Click to collapse
Oh I didn't realize the bootloader was like that on the rooted rom. I was thinking you could just push the image if you had SU, but since the bootloader is already unsecured, you could use that. Until you guys get a custom recovery of course.
The bootloader has S-OFF *AND* it is an Engineering SPL. Can we extract the SPL by chance? I have an idea.....but I wont' mention it if we can't
zifnab06 said:
The bootloader has S-OFF *AND* it is an Engineering SPL. Can we extract the SPL by chance? I have an idea.....but I wont' mention it if we can't
Click to expand...
Click to collapse
Engineering SPL huh... woot that means u boys have fastboot. hell yeah. but no ur best bet is the goldcard deal. at that rate u can flash the rooted leak and be scott free. since u have a build that will flash to ur device and give u root. then all u gotta do is figure out the goldcard and flash it. idk if u guys have a good reason why the goldcard wont work or not. im just sayin thats prolly the best bet
toastcfh said:
Engineering SPL huh... woot that means u boys have fastboot. hell yeah. but no ur best bet is the goldcard deal. at that rate u can flash the rooted leak and be scott free. since u have a build that will flash to ur device and give u root. then all u gotta do is figure out the goldcard and flash it. idk if u guys have a good reason why the goldcard wont work or not. im just sayin thats prolly the best bet
Click to expand...
Click to collapse
I thought using the Goldcard was not possible?
http://forum.xda-developers.com/showthread.php?t=646734

rooting with 2.3 gb

Hey guys I've rooted a few phones for my friends since I rooted mines but that's when we were all running 2.2 froyo now I have a friend who wants me to root his phone too but he had the update 2.3 gb so can I still use unrevoked, the same method as froyo or do I have to wait for a different method for gb
Flip35 said:
Hey guys I've rooted a few phones for my friends since I rooted mines but that's when we were all running 2.2 froyo now I have a friend who wants me to root his phone too but he had the update 2.3 gb so can I still use unrevoked, the same method as froyo or do I have to wait for a different method for gb
Click to expand...
Click to collapse
As far as I know, there is no method available for rooting stock 2.3.
Got to wait. It will come.
Daaam, ok thanx I guess my buddy has to wait then, I told him to do it a few weeks back n he didn't want me to do it so now he'll have to wait...he should of done it when he had the chance
i thought i read a thread on here recently that said you could root by downgrading and then doing it. look around a lil n u will prob find it if u wanna try it out
{ParanoiA} said:
i thought i read a thread on here recently that said you could root by downgrading and then doing it. look around a lil n u will prob find it if u wanna try it out
Click to expand...
Click to collapse
You can only downgrade to 2.2 if you have s-off. The new 2.16 bootloader will not accept any known RUU, downgrade, or any other root method currently. I even tried to do the "old" GoldCard method, and of course, that didn't work either.
Here is the write up if interested on how to downgrade with s-off.........
http://htcevohacks.com/htc-evo-hacks/how-to-root-htc-evo-4g-gingerbread-2-3/
Check out the 4th comment, by Julian. Pretty much sums it up.........
"This procedure WILL NOT work if you have unrooted your Evo and updated via OTA from sprint!! New bootloader interface is included with the new RUU (2.3.3) which prevents recovery mode launch, reverting back to a prior ROM, or rooting"
you can root it if your bootloader says s-off, just flash recovery in a pc36img file and flash superuser for 2.3
skyline247 said:
You can only downgrade to 2.2 if you have s-off. The new 2.16 bootloader will not accept any known RUU, downgrade, or any other root method currently. I even tried to do the "old" GoldCard method, and of course, that didn't work either.
Here is the write up if interested on how to downgrade with s-off.........
http://htcevohacks.com/htc-evo-hacks/how-to-root-htc-evo-4g-gingerbread-2-3/
Check out the 4th comment, by Julian. Pretty much sums it up.........
"This procedure WILL NOT work if you have unrooted your Evo and updated via OTA from sprint!! New bootloader interface is included with the new RUU (2.3.3) which prevents recovery mode launch, reverting back to a prior ROM, or rooting"
Click to expand...
Click to collapse
thanks for this!
Well my friends phone has never been rooted so he wants to rooted so can I still go back to 2.2 using the methods y'all posted here
The new bootloader does not prevent recovery from launching. You can either turn off fastboot on settings-applications or instead of power off, choose reboot and start holding down vol-down when the screen goes black
Sent from my PC36100 using XDA App
vandon1 said:
The new bootloader does not prevent recovery from launching. You can either turn off fastboot on settings-applications or instead of power off, choose reboot and start holding down vol-down when the screen goes black
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
So ur saying I NEED TO GET TO BOOTLOADER to b able to do it right???
Flip35 said:
So ur saying I NEED TO GET TO BOOTLOADER to b able to do it right???
Click to expand...
Click to collapse
If the phone has never been rooted before, then you are going to be S-on. Since you have the new bootloader, AND you have S-on, there is nothing you can do to root the phone at this time. You cannot downgrade to 2.2, you cannot downgrade the bootloader. The only thing you'll be able to do is wait until someone figures out how to get S off on the new bootloader, or if someone figures out a way to downgrade the bootloader. The only way you can downgrade back to 2.2, is if the bootloader is S off. Also, if the bootloader was S off, downgrading to froyo to 'reroot' is a complete waste of time. All you need to do is flash a PC36IMG of a recovery image, and then use that recovery to flash a new rom. That's it. Anything more than that is a total waste of time, and a bunch of steps that don't need to be taken.
So, unfortunately, all you can do is wait until someone figures out a way around the new bootloader.
bootloader!!
kingdazy said:
As far as I know, there is no method available for rooting stock 2.3.
Got to wait. It will come.
Click to expand...
Click to collapse
Only option that I have found is to take it back to 2.2 and flash gingerbread rom, I personally only use z4root so ill have to wait
Desdoulas said:
Only option that I have found is to take it back to 2.2 and flash gingerbread rom, I personally only use z4root so ill have to wait
Click to expand...
Click to collapse
AGAIN......for those who just don't get it......
"This procedure WILL NOT work if you have unrooted your Evo and updated via OTA from sprint!! New bootloader interface is included with the new RUU (2.3.3) which prevents recovery mode launch, reverting back to a prior ROM, or rooting"
Sent from my PC36100 using XDA Premium App
Wow, don't you just hate repeating yourself?
HipKat said:
Wow, don't you just hate repeating yourself?
Click to expand...
Click to collapse
I think it might sink in eventually. Probably the day after a root method is found for Gingerbread.
k2buckley said:
If the phone has never been rooted before, then you are going to be S-on. Since you have the new bootloader, AND you have S-on, there is nothing you can do to root the phone at this time. You cannot downgrade to 2.2, you cannot downgrade the bootloader. The only thing you'll be able to do is wait until someone figures out how to get S off on the new bootloader, or if someone figures out a way to downgrade the bootloader. The only way you can downgrade back to 2.2, is if the bootloader is S off. Also, if the bootloader was S off, downgrading to froyo to 'reroot' is a complete waste of time. All you need to do is flash a PC36IMG of a recovery image, and then use that recovery to flash a new rom. That's it. Anything more than that is a total waste of time, and a bunch of steps that don't need to be taken.
So, unfortunately, all you can do is wait until someone figures out a way around the new bootloader.
Click to expand...
Click to collapse
Yea man the phone has never been rooted, is for my buddy n I told him to come to my house to get it rooted before the update he was procrastinating n now he's stuck but thanx a lot for the info everybody
skyline247 said:
AGAIN......for those who just don't get it......
"This procedure WILL NOT work if you have unrooted your Evo and updated via OTA from sprint!! New bootloader interface is included with the new RUU (2.3.3) which prevents recovery mode launch, reverting back to a prior ROM, or rooting"
No need to be rude kid, I watched a buddy install a ruu that worked perfectly, took about 20 min he was back to 2.2, there is a few youtube vids on it, I didn't do the code for it but I did watch it work to my disbelief, I said the same thing you did that there was no way
Sent from HTC_SUPERSONIC EVO
Click to expand...
Click to collapse
Then link us to this magical youtube video.
Kid? I'm 41 years old. I wasn't being rude. The same question was asked several times, so I was just restating the obvious. My goal on here is not to be rude, unlike many others, but to actually help. And I am sorry if you perceived as such.
Also, sorry to burst your bubble, but there is NO way to root if you have 2.3 AND the new 2.16 bootloader. Either you have S=off and run an RUU to get back to Froyo, or you do not have the new 2.16 bootloader.
That is all.

Rooting With The 2.3 O.T.A. Update

For everyone who's been wondering and asking,
As of right now there is NO WAY to root your phone if you accepted the 2.3 Gingerbread OTA update and there is no way to revert back to 2.2.
For all the people who have accepted it, you are stuck with a non-rootable phone until a dev can produce a new root method.
With that being said, temp-root is also NOT available.
Also, flashing anything like a different ROM or a new kernel is NOT possible at this time.
If you accidentally updated or just got the phone from Sprint, you are out of luck for now.
thanks for the info. i have been waiting to update because i suspected as much. For all those that updated to 2.3, is it awesome????
Sent from my PG06100 using XDA App
How long did it take for 2.2 to be rooted? Hopefully 2.3 should take the same amount of time/less time.
-CM7 ADR6300
Caiaphas said:
there is no way to revert back to 2.2.
Click to expand...
Click to collapse
The old official RUUs don't work on the phone?
x99percent said:
The old official RUUs don't work on the phone?
Click to expand...
Click to collapse
Nope, they don't.
Lancerz said:
Nope, they don't.
Click to expand...
Click to collapse
Any more of an explanation than that? ...like the error message you get?
People had to RUU back to an older version of Froyo when the latest update plugged up what was the latest root exploit, and that old RUU always worked without a problem. It would be a shame if HTC/Sprint didn't "allow" people to revert back to the older OS.
I think the error code was error 170 when running the RUU, but I have tried all the ways just like everyone else and none of them work.
dpwhitty11 said:
How long did it take for 2.2 to be rooted? Hopefully 2.3 should take the same amount of time/less time.
-CM7 ADR6300
Click to expand...
Click to collapse
FOREVER!!!! At least it felt that way. More people should have the phone now so shouldn't be too long.
Lancerz said:
I think the error code was error 170 when running the RUU, but I have tried all the ways just like everyone else and none of them work.
Click to expand...
Click to collapse
I would guess that booting into the bootloader to load the old Froyo RUU would still work. I always thought the RUU was looking for the proper phone, regardless of its firmware/OS versions.
Nope, in order for a ruu to run, the phone has to have the same or older hboot
Sent from my PG06100 using XDA App
I wish it was that easy because I forgot how much the GPS sucks on sense roms. Got a trip out of town coming up this weekend also, grrrr.
Lancerz said:
I wish it was that easy because I forgot how much the GPS sucks on sense roms. Got a trip out of town coming up this weekend also, grrrr.
Click to expand...
Click to collapse
Really? I always thought Sense was great, but AOSP roms sucked at GPS.
Just used the gps in the 2.3 rom and it worked out great. It was a short distance though so might need more testing fyi
I think the GPS on sense (stock at least) tends to take a little longer to lock on, that's all.
Hopefully this gets rooted soon since I've got to send my current phone back in a couple of days, and it wouldn't surprise me if the new one has the update already
danaff37 said:
Nope, in order for a ruu to run, the phone has to have the same or older hboot
Click to expand...
Click to collapse
So is this "170" error seen in the RUU program or on the phone itself?
Forgive me if I'm way behind the ball on this: The Froyo RUU contains a "rom.zip" that looks like it could simply be renamed to PG06IMG.zip and flashed from the bootloader.
x99percent said:
So is this "170" error seen in the RUU program or on the phone itself?
Forgive me if I'm way behind the ball on this: The Froyo RUU contains a "rom.zip" that looks like it could simply be renamed to PG06IMG.zip and flashed from the bootloader.
Click to expand...
Click to collapse
I don't know bout that error but when I tried twice to ruu my wife's phoneI think the error was 104 bootloader not new enuff something like that.
Well when you run the RUU it goes through all the motions like its going to be successful. Then it reboots into the bootloader and you get the all black HTC screen on your phone while its updating. The RUU on your pc screen is at the part where it says updating your rom image may take 10 minutes etc. Then you get the error [140] Bootloader version error. "The rom update utility cannot update your Android phone, please get the correct ROM update utility and try again."The error [170] is when it doesnt find your phone connected to the usb.
This should be done uploading in about 3 minutes. Rename to PG06IMG.zip, place it in the root of your SD card, and boot up in the bootloader. If it doesn't work, I'll have another to try tomorrow.
BACK UP YOUR DATA/APPS/CONTACTS FIRST (I recommend using Titanium Backup, SMS Backup & Restore, and Call Logs Backup & Restore... and you should be syncing your contacts to a google account)
http://www.4shared.com/file/ADnrxUXB/Stock-Froyo-ROM-1176511.html
I'll give it a try now
Edit: Nope, that doesn't work.
great.
i guess i am stuck with this buggy 2.3 rom until a root solution is found and i can get this crappy rom off my phone. i am tired of the apps not working. locking up & same with the OS.
do the world a favor and steer clear of the RUU 2.3 rom. dont be stuck like the rest of us with a rom we cant do anything with.

[Q] Help with Mytouch 4G with Gingerbread 2.3.4

Hello everyone,
Any help you guys can give will be much appreciated.
I have a MyTouch 4G previously running Froyo, rooted and S=Off. Against better judgment, I decided to put this release of Gingerbread 2.3.4 on it:
PD15IMG_Glacier_Gingerbread_S_TMOUS_2.19.531.1_Radio_12.58.60.25_26.11.04.03_M_release_200756_signed.zip
Though everything seems to work fine, I lost root. Contrary to most other accounts from other people who flashed the same file, S=Off remained on my phone.
I would really like to get root back so I can use some of my apps again.
Visionary stops at a black screen.
Gingerbreak runs forever with no success.
What other means can I use to get root back or am I SOL for now until someone figures out how to root 2.3.4 on the MT4G?
Thanks again.
N
From what I could find in the forums, you are kinda stuck till someone comes up with another exploit in order to gain root and s-off
Sent from my HTC Glacier using XDA Premium App
I am stuck in the same situation, except that I updated first to the official gingerbread rom for mytouch 4g and then tried to root my phone, i.e. the phone was not rooted at all.
I'm quite confident an exploit will be (re)written - just a matter of time. It's just that I couldn't use some of my paid apps.
normandelli said:
I'm quite confident an exploit will be (re)written - just a matter of time. It's just that I couldn't use some of my paid apps.
Click to expand...
Click to collapse
Yeah, Im just itching to use bloat freezer. I'm doing a warrant exchange if nothing happens in a week or two. Got dust under the screen anyways.
Sent from my HTC Glacier using XDA Premium App
You can go back to 2.2.1 from 2.3.4
I had the same issue then i found this http://forum.xda-developers.com/showthread.php?t=1178912 follow the G2 method, when you get to the part where you put this in # /data/local/tmp/misc_version -s 1.19.531.1 make sure you put the version you want like 1.17.531.2 not 1.19.531.1 worked for me just did it about 1/2hr ago
If you still have S-off, why not just wipe and flash another ROM?
GazaIan said:
If you still have S-off, why not just wipe and flash another ROM?
Click to expand...
Click to collapse
The ota kills root and makes S= ON
Sent from my HTC Glacier using XDA Premium App
GazaIan said:
If you still have S-off, why not just wipe and flash another ROM?
Click to expand...
Click to collapse
I tried flashing a similar 2.3.4 release that is rooted. Renamed it to PD15IMG.zip and tried applying it - At "parsing", it stops and just goes back to the HBOOT menu.
normandelli said:
I tried flashing a similar 2.3.4 release that is rooted. Renamed it to PD15IMG.zip and tried applying it - At "parsing", it stops and just goes back to the HBOOT menu.
Click to expand...
Click to collapse
You are mixing up roms and official update zips. You can't just flash a rom thorough hboot. That's not how it works.
Sent from my HTC Glacier using XDA Premium App
I managed to flash 2.2.1 back on to it and re-rooted. Problem solved. Thanks!
normandelli said:
I managed to flash 2.2.1 back on to it and re-rooted. Problem solved. Thanks!
Click to expand...
Click to collapse
Can you tell me how you managed to do that please?
superNES64 said:
Can you tell me how you managed to do that please?
Click to expand...
Click to collapse
lOOK AT WOLF26915's post use the G2 instructions to temp root using the fre3vo exploit in adb then change your version number to 1.17.531.2, then your bootloader will allow you to use the 2.2.1 PD15IMG update to get back to stock and root.
normandelli said:
I tried flashing a similar 2.3.4 release that is rooted. Renamed it to PD15IMG.zip and tried applying it - At "parsing", it stops and just goes back to the HBOOT menu.
Click to expand...
Click to collapse
This is the problem with n00bs. You wanna jump head first into something you have absolutely no understanding of then beg for help over and over in here when you finally brick your phone.
Stupid. You FAIL!
So sick of new users of Android trying to jump before looking. You're the same kind of people who would jump off a cliff before checking to see how deep the water is. Then want help after you break your neck.
CBConsultation said:
This is the problem with n00bs. You wanna jump head first into something you have absolutely no understanding of then beg for help over and over in here when you finally brick your phone.
Stupid. You FAIL!
So sick of new users of Android trying to jump before looking. You're the same kind of people who would jump off a cliff before checking to see how deep the water is. Then want help after you break your neck.
Click to expand...
Click to collapse
Just remember you was new at this at one time to
WOLF26915 said:
Just remember you was new at this at one time to
Click to expand...
Click to collapse
That was 20 years ago. And yet, even then, when I wanted to know something; I searched and searched and searched, and searched again. Then I read and read and re-read over and over and over again. And after all that if I still didn't know then I would ask. But I would also ask in a proficient manner.
Too many young kids jumping in on the Android bandwagon and wanting to root and flash Rom's right out of the box without learning first.
I stand by my first statement.
If you had Radio S-OFF, you should be able to flash an unsigned PD15IMG.zip even though you lost root.
Sent from my Nexus One using Tapatalk
WOLF26915 said:
I had the same issue then i found this http://forum.xda-developers.com/showthread.php?t=1178912 follow the G2 method, when you get to the part where you put this in # /data/local/tmp/misc_version -s 1.19.531.1 make sure you put the version you want like 1.17.531.2 not 1.19.531.1 worked for me just did it about 1/2hr ago
Click to expand...
Click to collapse
thanks a lot dude for showing me to put that.. i can confirm it worked perfectly fine. i will hit the thanks button for sure. i was stuck on that damn gingerbread leak build lol
Interesting. msm_rotator is I believe the exploit used in Fre3vo.
I wonder if this would work to downgrade the HTC Panache from Mobilicity to an MT4G ROM?
I also downgraded back to 2.2.1 then updated to the rooted 2.3.4 and it works

How much do I need to reset to stock before taking it into the store?

My HTC Evo Shift's touch screen stopped working partially.
Above 70% of the screen won't work vertically anymore. (Horizontal is fine).
I am going to take it into the store.
Do I need to get rid of everything including root and recovery?
What will they check?
nullstring2 said:
My HTC Evo Shift's touch screen stopped working partially.
Above 70% of the screen won't work vertically anymore. (Horizontal is fine).
I am going to take it into the store.
Do I need to get rid of everything including root and recovery?
What will they check?
Click to expand...
Click to collapse
Never take a Device in for service while Rooted. Some Techs will check, others will not. But if they do find that it's Rooted they can flag your account. Not what you want . Also they may try and say that the issue is because you rooted your device. If you are going to RUU I would use the RUU HERE. That way it will be easier to re-root your device afterward. One question, did you Update your Radio's and Touchscreen Firmware yet?
Why will it be easier to root my device?
Do I need to flash stock recovery? Or will they not check for this?
It will be easier to Re-Root your device if you RUU to 2.2, as opposed to 2.3.4 . Mostly because there are less steps involved. Once you RUU it will take the device to Factory fresh out of the box. Stock everything.
You don't think they'll be suspicious that I am still running froyo?
I am thinking about just calling sprint instead and seeing if they'll agree to do a replacement ahead of time. In that case, I can just RUU to 2.3.4 and not care since I'm not getting it back.
It depends on the Tech. Some techs don't care, as long as the device is not Rooted. Some may ask, but you just tell them you've never taken an Update. Calling Sprint ahead of time will most likely not do anything. They're going to want to check the device anyway. You can RUU to 2.3.4 then re-root later. It will just take a few more steps.
TEAM MiK
MikROMs Since 3/13/11
nullstring2 said:
You don't think they'll be suspicious that I am still running froyo?
I am thinking about just calling sprint instead and seeing if they'll agree to do a replacement ahead of time. In that case, I can just RUU to 2.3.4 and not care since I'm not getting it back.
Click to expand...
Click to collapse
Yes, majority of the techs will be suspicious about you being on froyo... Android users are anal about their ota updates and very few users skip ota updates except rooted users... I state this from experience, as I brought in a shift unrooted on froyo a few months ago and than ended up at sprint for over an hour answering their questions... I got my replacement device but I will NEVER bring in a device not running the latest firmware...
Sent from my PG06100
In my experience it depends where you take it to have it serviced. If you go to a Corporate store, they check out stuff a lot more. But the up side is they are quicker to resolve an issue. The privately owned stores usually do not check the device out that in depth. If they can't fix the issue immediately, they usually just give you some options about getting another.
prboy1969 said:
In my experience it depends where you take it to have it serviced. If you go to a Corporate store, they check out stuff a lot more. But the up side is they are quicker to resolve an issue. The privately owned stores usually do not check the device out that in depth. If they can't fix the issue immediately, they usually just give you some options about getting another.
Click to expand...
Click to collapse
I agree... The stores around my area are all corporate...
Sent from my PG06100
So, where do I get the stock 2.3.3 (or 2.3.4) RUU or zip file?
I can only find the 2.2 version.
Just run the exe then do the software upgrade
Sent from my PG06100 using Tapatalk 2
Thats kind of a pain.
I used http://goo.im/stock/speedy/ruu/PG06..._1.88_0128_PRL60674_release_196686_signed.zip
However, after it updated to S-ON, it says "Main Version is older! Update fail"
Do I need to use the 2.2 RUU?
EDIT:fastboot getvar version-main
2.77.651.3
Hrm. Did I screw up here?
Can I still use the 2.2 RUU?
Do I need to use the downgrade techniques to get it to downgrade?
EDIT2: I flashed the misc.img in order to trick hboot into installing 2.3.4 stock.
I'm not sure if I was suppose to have to do that.. but whatever, it worked.
nullstring2 said:
Thats kind of a pain.
I used http://goo.im/stock/speedy/ruu/PG06..._1.88_0128_PRL60674_release_196686_signed.zip
However, after it updated to S-ON, it says "Main Version is older! Update fail"
Do I need to use the 2.2 RUU?
EDIT:fastboot getvar version-main
2.77.651.3
Hrm. Did I screw up here?
Can I still use the 2.2 RUU?
Do I need to use the downgrade techniques to get it to downgrade?
EDIT2: I flashed the misc.img in order to trick hboot into installing 2.3.4 stock.
I'm not sure if I was suppose to have to do that.. but whatever, it worked.
Click to expand...
Click to collapse
Wait . What are you trying to accomplish? I thought you wanted to take it in for service. If you still want to take it in just run the 2.3.4 .exe RUU I've attached below. It will Update your device to 2.3.4 ,and done . Then you can take it in for service.
2.3.4 SPEEDY GB .exe RUU
prboy1969 said:
Wait . What are you trying to accomplish? I thought you wanted to take it in for service. If you still want to take it in just run the 2.3.4 .exe RUU I've attached below. It will Update your device to 2.3.4 ,and done . Then you can take it in for service.
2.3.4 SPEEDY GB .exe RUU
Click to expand...
Click to collapse
I already got it flashed... so the issue is solved.
But, are you sure just using the RUU will work?
I was having issues because I was trying to install 2.76 "main-version" when the installed version was 2.77 or something, and it wouldn't let me downgrade.
As far as I understand both the file I linked and the one you posted validate against the version.
Therefore, I had to flash the misc.img for the TB (like you do to downgrade to 2.2), and then i was able to do it fine.
Glad you got it sorted. Yes, any of the Speedy RUU's should work. So long as you are Fully Rooted ( S-OFF ). If not then you can only Upgrade RUU.
TEAM MiK
MikROMs Since 3/13/11
prboy1969 said:
Glad you got it sorted. Yes, any of the Speedy RUU's should work. So long as you are Fully Rooted ( S-OFF ). If not then you can only Upgrade RUU.
Click to expand...
Click to collapse
I see. The issue with the PG06IMG is that the first thing it does is flash the bootlooder to S-ON, and then you can only upgrade.
Thank goodness for that TB misc.img exploit!
Could have really screwed myself over there. I'll have to be more careful in the future.
Always here to help
Where's the RUU for 2.2? Prboy, the link you posted was for 2.3 if its possible, can some post a link for 2.2? I tried searching but didn't find it. I'm on mobile so that's why
Shifted from my EVO
Enraged21 said:
Where's the RUU for 2.2? Prboy, the link you posted was for 2.3 if its possible, can some post a link for 2.2? I tried searching but didn't find it. I'm on mobile so that's why
Shifted from my EVO
Click to expand...
Click to collapse
No worries . What your looking for is HERE.
prboy1969 said:
No worries . What your looking for is HERE.
Click to expand...
Click to collapse
You're the man... Appreciate it
Shifted from my EVO

Categories

Resources