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.
Related
I'm looking to root and flash my Hero to DamageControl 2.0, but has anyone successfully restored the device back to factory defaults after flashing to DC2.0?
You have to use either Sprint 1.29 RUU or Fresh's 1.56 RUU. That will make it stock again.
jdgiotta said:
I'm looking to root and flash my Hero to DamageControl 2.0, but has anyone successfully restored the device back to factory defaults after flashing to DC2.0?
Click to expand...
Click to collapse
Yeah I believe I used the 1.29 RUU from the stock rom
jdgiotta said:
I'm looking to root and flash my Hero to DamageControl 2.0, but has anyone successfully restored the device back to factory defaults after flashing to DC2.0?
Click to expand...
Click to collapse
I used 1.56 RUU and went back to stock. Worked fine on mine w/ stock radio.
jdgiotta said:
I'm looking to root and flash my Hero to DamageControl 2.0, but has anyone successfully restored the device back to factory defaults after flashing to DC2.0?
Click to expand...
Click to collapse
Some people do, and some don't. There is a fix if you brick it while RUUing. However if you are wanted to go back to stock for the 2.1 "official" release you might not be able to root again. They seem to leave the door open on the first round of software, but then close the hole on the next round. Seems the case for every phone
So the ability to root maybe lost if I was to update to a "official" release. Hmm... okay, good to know. Thanks.
jdgiotta said:
So the ability to root maybe lost if I was to update to a "official" release. Hmm... okay, good to know. Thanks.
Click to expand...
Click to collapse
Yea give it like 24 hours after the release, someone will do a nand dump, root it and post it on here. One thing I would reccomend people stay away from would be a new version of an RUU based off of 2.1, as that would put you up a **** creek if a root isn't found. I hear lots of problems trying to .29 RUU after a .56 RUU, I'm sure the same will be said for whatever the next version is.
jdgiotta said:
So the ability to root maybe lost if I was to update to a "official" release. Hmm... okay, good to know. Thanks.
Click to expand...
Click to collapse
They may, or may not close the exploit that was found in 1.5 but if so it will only be a matter of time before some of these guys who are far more talented than I find a way to root 2.1, 1.5 was not rootable when it was released. Regardless the 2.1's you will see later today will be far superior to whatever sprint ends up releasing.
You should be able to RUU without any issues. However, you might still not be able to see protected apps in the market. I used the steps in this thread to fix that:
http://forum.xda-developers.com/showthread.php?t=605028
xanadu1979 said:
You should be able to RUU without any issues. However, you might still not be able to see protected apps in the market. I used the steps in this thread to fix that:
http://forum.xda-developers.com/showthread.php?t=605028
Click to expand...
Click to collapse
This fix didn't work for me, however I was able to RUU, update to DamageControl 1.0, download some protected apps, and then upgrade to DC2.0r2 (without wiping between DC1 and DC2). This opened up protected apps and solved the black on black contact problem for me.
-obviously do so at your own risk and all-
&RoidRage said:
Some people do, and some don't. There is a fix if you brick it while RUUing. However if you are wanted to go back to stock for the 2.1 "official" release you might not be able to root again. They seem to leave the door open on the first round of software, but then close the hole on the next round. Seems the case for every phone
Click to expand...
Click to collapse
Speaking of this, I am currently rooted, but running stock 1.5(don't ask)will I still be able to get the update or do I have to be completely unrooted to do so!
Also as far as the update is concerned, I know on the droid forums there were instructions on saving the update before installation so all could get it! What is the procedure for doing so!
It seems with the current state of affairs the update could come in a minute or a day or a month, basically no one know, so it could be anytime, so I just wanna be prepared for when it drop to hand it off to the real DEV.!
Roman
Eh, you could go ahead and flash a new ROM right now if you want. A fix was found for people getting bricked from the RUU, so you're safe to use the RUU now without fear of having a permanent brick on your hands.
Roman G said:
Speaking of this, I am currently rooted, but running stock 1.5(don't ask)will I still be able to get the update or do I have to be completely unrooted to do so!
Click to expand...
Click to collapse
Good question
This is not a 2.1 speculation thread, I just thought I'd ask it here with all that knowledge floating around.
WHEN (May 7th?) the 2.1 update is OFFICIALLY dropped, will rooted users be pushed the update? Or will it only go out to models registered as running 1.56.
ASSUMING one might want to upgrade and that push comes, you guys think updating might cause any harm to the phone? I'm thinking 1.56RUU..
I don't think I will partake in the official release, I can't imagine it being any better then what I have now, and what will come after that official release is dropped, however I have had this question for a while. So what do you guys think?
I don't think they can actually push a OTW update.....
barnacles10 said:
This is not a 2.1 speculation thread, I just thought I'd ask it here with all that knowledge floating around.
WHEN (May 7th?) the 2.1 update is OFFICIALLY dropped, will rooted users be pushed the update? Or will it only go out to models registered as running 1.56.
ASSUMING one might want to upgrade and that push comes, you guys think updating might cause any harm to the phone? I'm thinking 1.56RUU..
I don't think I will partake in the official release, I can't imagine it being any better then what I have now, and what will come after that official release is dropped, however I have had this question for a while. So what do you guys think?
Click to expand...
Click to collapse
It is not going to be OTA. It will not matter if you are running custom whatever or stock.
If you run the ruu.exe it will load the official 2.1 release on your phone. The only reason it may not work would be if you ran the 2.1 test ruu.exe and for some reason the official release's hboot is lower than 1.47.000 (the hboot that came with the test release).
Other potential nasty side effects you could get with your official release:
No root
Possibly never be able to root again, or at least stuck with no root until a new work around is found. This fully depends on whether old method is patched.
No custom recovery, no custom roms, no ability to flash .zips from recovery. This goes along with the lack of root.
Inability to run 1.56 ruu ever again due to updated hboot.
danknee said:
It is not going to be OTA. It will not matter if you are running custom whatever or stock.
If you run the ruu.exe it will load the official 2.1 release on your phone. The only reason it may not work would be if you ran the 2.1 test ruu.exe and for some reason the official release's hboot is lower than 1.47.000 (the hboot that came with the test release).
Other nasty side effects you could get with your official release:
No root
Possibly never be able to root again, or at least stuck with no root until a new work around is found.
No custom recovery, no custom roms, no ability to flash .zips from recovery. This goes along with the lack of root.
Inability to run 1.56 ruu ever again due to updated hboot.
Click to expand...
Click to collapse
Couldn't have said it better myself! I would just suggest waiting until the cook of your preference updates his to include items from the official release.
And the single most important reason: No nandroid. Having a point in time backup is insanely important to me. If I ever have to return my phone and get a refurb, it's nice to know I've got a nandroid that will get me right back to where I was before I turned in my phone.
It won't be OTA as I have read in more than one place that Sprint limits OTA updates to 9MB. Since this will be close to or over 100MB it's going to be OTW.
I for one will not be updating to it. My phone is working perfectly as is and this would give me no additional functionality so why bother?
As for the whole rooting issue, I wish folks wouldn't be so scared of the new hboot. I used the RUU and I have custom recovery and can flash any ROM I want. Yes, I know the leaked RUU had root already, but I rerooted it properly and installed busybox and all that so I could use the phone how I wanted.
Anyway, sorry to get sidetracked there, my comment about being so scared of the new hboot is simply this...There is no way the new version will not be rooted sooner or later. Obviously Sprint and HTC would like us to not be able to root any phones but someone always finds a way. There is no way that the new firmware will not be rooted sooner or later. Just like how the Evo will get rooted, as will any newer phone released after it. It is inevitable that someone will figure it out especially with all the talented and experienced folks here working on it as soon as it's released.
jlem26 said:
It won't be OTA as I have read in more than one place that Sprint limits OTA updates to 9MB. Since this will be close to or over 100MB it's going to be OTW.
I for one will not be updating to it. My phone is working perfectly as is and this would give me no additional functionality so why bother?
As for the whole rooting issue, I wish folks wouldn't be so scared of the new hboot. I used the RUU and I have custom recovery and can flash any ROM I want. Yes, I know the leaked RUU had root already, but I rerooted it properly and installed busybox and all that so I could use the phone how I wanted.
Anyway, sorry to get sidetracked there, my comment about being so scared of the new hboot is simply this...There is no way the new version will not be rooted sooner or later. Obviously Sprint and HTC would like us to not be able to root any phones but someone always finds a way. There is no way that the new firmware will not be rooted sooner or later. Just like how the Evo will get rooted, as will any newer phone released after it. It is inevitable that someone will figure it out especially with all the talented and experienced folks here working on it as soon as it's released.
Click to expand...
Click to collapse
One big disadvantage/advantage in our case, is that Linux is open source. Anyone who wants to find a root exploit, and is smart enough has the ability to find out where there is potential code to allow for one. So you are correct, my assumption is that we will find a root for it one day. BUT I do think that if the EVO drops soon after, all of the talent that can find one will be on it. Then again, some people are of the mind set "Leave no device un hacked" and it would bother people if they knew we didn't have root LOL
Correct me if I'm wrong, but won't we be able to simply use an older RUU (1.52, etc) to get the phone rootable again?
My intention was going to be to try out the new stock RUU for a bit, then re-flash with an older RUU, get root and RA recovery back on, then go back to Fresh Toast. Will this not be possible?
cicada said:
Correct me if I'm wrong, but won't we be able to simply use an older RUU (1.52, etc) to get the phone rootable again?
My intention was going to be to try out the new stock RUU for a bit, then re-flash with an older RUU, get root and RA recovery back on, then go back to Fresh Toast. Will this not be possible?
Click to expand...
Click to collapse
Not possible if the Hboot updates, which it probably will. Those here who tried the test leak 2.1 ruu.exe were unable to run the 1.56 ruu after.
There is an alternative to restore everything except the hboot from the 1.56 ruu here, but you cannot simply run the .exe. This method won't work if the official build has patched the ability to gain root (you won't be able to nandroid). In that case you will be stuck with official 2.1 only.
BTW, speaking from experience with the test build, ruu, hboot, etc.
Kcarpenter said:
One big disadvantage/advantage in our case, is that Linux is open source. Anyone who wants to find a root exploit, and is smart enough has the ability to find out where there is potential code to allow for one. So you are correct, my assumption is that we will find a root for it one day. BUT I do think that if the EVO drops soon after, all of the talent that can find one will be on it. Then again, some people are of the mind set "Leave no device un hacked" and it would bother people if they knew we didn't have root LOL
Click to expand...
Click to collapse
Open source is never a disadvantage. Ever.
Good to know, would've been awful to have to wait for new root hack just because I tried the new and shiny!
Guess I will sit back and wait for dev magic before I jump the gun.
Sawawa said:
Open source is never a disadvantage. Ever.
Click to expand...
Click to collapse
Mater of semantics, politics, and Ideaologies.
Google has a half belief here, they like open, but they protect that damn search algorithim like its a sacred scripture - Last count I think 8 people on earth knew exactly how it worked.
So the disadvantage to google would be ungodly competition if it was released. Proprietary stuff is a win if you look for profits. Again...depends on which side of the spectrum you are on. Points can be argued either way.
jlem26 said:
It won't be OTA as I have read in more than one place that Sprint limits OTA updates to 9MB. Since this will be close to or over 100MB it's going to be OTW.
Click to expand...
Click to collapse
I think the OP is asking about an OTA 'notification' that the official update is available. If so then yes, everyone with a Hero will get a text message regardless of what rom we have installed.
ramiss said:
I think the OP is asking about an OTA 'notification' that the official update is available. If so then yes, everyone with a Hero will get a text message regardless of what rom we have installed.
Click to expand...
Click to collapse
THAT BETTER NOT COUNT AGAINST MY TEXT LIMIT!!!!
Kcarpenter said:
THAT BETTER NOT COUNT AGAINST MY TEXT LIMIT!!!!
Click to expand...
Click to collapse
ROFL. . . you don't have unlimited text?
lol I would hope having a hero you would have unlimited data and texts
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
yeah, but I still keep track of them. Habitual addiction to knowing everything LOL.
yeah, but I still keep track of them. Habitual addiction to knowing everything LOL.
Click to expand...
Click to collapse
lol! that's great.. ever since sprint gave us that free mobile to mobile in any network I do not bother checking minutes or texts. unless my bill changes.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
One big disadvantage/advantage in our case, is that Linux is open source. Anyone who wants to find a root exploit, and is smart enough has the ability to find out where there is potential code to allow for one.
Click to expand...
Click to collapse
Why is it that people still think open source means insecure? I don't claim to know how previous rooting techniques exploit Android, but I do know that 2 Linux distros have a higher government security rating than any other operating system. I assume most weaknesses in android have to do with the recovery and/or update code, which has nothing to do with Linux.
Sawawa said:
Open source is never a disadvantage. Ever.
Click to expand...
Click to collapse
It IS when HTC bogards it from us and hordes it like cookie monster does cookies. I thought open source meant OPEN SOURCE. Ahh, who knows i probably misunderstood the whole concept
Is there anyway to revert gingerbread back to froyo until the devs can root it? There has got to be a way. Need my net back
Sent from my PG06100 using XDA App
As of right now there is no way to revert back to froyo. Take a look at this thread.
http://forum.xda-developers.com/showthread.php?t=1142115
Sent from my PG06100 using XDA App
That sucks..... I cant beleive how much i screwed myself
Sent from my PG06100 using XDA App
well you r not the only one, I hate my self because i clicked upgrade. I lost lost my net on metropcs flashed evo
Yeah i live in a tech dead zone. The only net available is through my phone...
Sent from my PG06100 using XDA App
honorlost84 said:
Is there anyway to revert gingerbread back to froyo until the devs can root it? There has got to be a way. Need my net back
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Yes, you can but it's a pain in the butt. Go to this thread and then download the original stock firmware. Make sure USB debugging is turned on also.
To install the file you need to have HTC Sync installed and running. Double-click the file and it should recognize the phone and start installing after some input from you.
If you get a USB error, try booting into the bootloader and installing the exe in the same manner.
I just did this last night because I was in the same situation. It works.
Now you can re-root.
bnampel said:
Yes, you can but it's a pain in the butt. Go to this thread and then download the original stock firmware. Make sure USB debugging is turned on also.
To install the file you need to have HTC Sync installed and running. Double-click the file and it should recognize the phone and start installing after some input from you.
If you get a USB error, try booting into the bootloader and installing the exe in the same manner.
I just did this last night because I was in the same situation. It works.
Now you can re-root.
Click to expand...
Click to collapse
You were able to downgrade to Froyo with this RUU? If so, that's great.. your the only person I've seen post successfully downgrading and being able to root.
bnampel said:
Yes, you can but it's a pain in the butt. Go to this thread and then download the original stock firmware. Make sure USB debugging is turned on also.
To install the file you need to have HTC Sync installed and running. Double-click the file and it should recognize the phone and start installing after some input from you.
If you get a USB error, try booting into the bootloader and installing the exe in the same manner.
I just did this last night because I was in the same situation. It works.
Now you can re-root.
Click to expand...
Click to collapse
I think everyone that ran the factory upgrade has tried this and you seem to be the only one that it has worked for. It goes through the motions then you get error 140 or 170 i think: Bootloader version error. Please get the correct rom update utility and try again
I have rooted my phone and installed the rockmod_devroms_2.3.4.1-speedy and broke my root istalling "extras" can I just try the rooting procesess again or have to revert bak to froyo?
Sent from my PG06100 using XDA App
jimbowski51 said:
I have rooted my phone and installed the rockmod_devroms_2.3.4.1-speedy and broke my root istalling "extras" can I just try the rooting procesess again or have to revert bak to froyo?
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
What do you mean you broke root? Do you still have s-off and access to recovery?
Lancerz said:
I think everyone that ran the factory upgrade has tried this and you seem to be the only one that it has worked for. It goes through the motions then you get error 140 or 170 i think: Bootloader version error. Please get the correct rom update utility and try again
Click to expand...
Click to collapse
I guess I feel pretty lucky then. I'm fairly certain I didn't miss any steps.
When I upgraded to the gingerbread stock ROM I used this link and chose the "no hboot included" option. Maybe that saved me.
bnampel said:
I guess I feel pretty lucky then. I'm fairly certain I didn't miss any steps.
When I upgraded to the gingerbread stock ROM I used this link and chose the "no hboot included" option. Maybe that saved me.
Click to expand...
Click to collapse
That's not the same as accepting the ota.
Sent from my Gingerbread Speedy 4G using Tapatalk
bnampel said:
I guess I feel pretty lucky then. I'm fairly certain I didn't miss any steps.
When I upgraded to the gingerbread stock ROM I used this link and chose the "no hboot included" option. Maybe that saved me.
Click to expand...
Click to collapse
Yeah, you didnt do the ota update then.
Lancerz said:
Yeah, you didnt do the ota update then.
Click to expand...
Click to collapse
It's still the same update. Whether I installed it through an OTA update or from the bootloader doesn't matter.
You guys can get into the bootloader right? Take one of those modified "official" updates, rename it to PG06IMG.zip and flash it from the bootloader. Then do my first post and flash to Froyo so you can root again. May be worth a shot.
bnampel said:
It's still the same update. Whether I installed it through an OTA update or from the bootloader doesn't matter.
You guys can get into the bootloader right? Take one of those modified "official" updates, rename it to PG06IMG.zip and flash it from the bootloader. Then do my first post and flash to Froyo so you can root again. May be worth a shot.
Click to expand...
Click to collapse
This has already been tried and covered in this thread here: http://forum.xda-developers.com/showthread.php?t=1142115&page=2
I posted the same link in the beginning of this thread.
Unless you have an engineering bootloader, like after you rooted, you can only flash an an un modified pg0610.zip from htc. So any one who took an over the air update is SOL on that front. Best hope now is that the evo 3d root can be applied here
Sent from my PG06100 using XDA App
Wow, I almost just majorly screwed myself (again). I have the shift and its just been sitting in my drawer, waiting to be activated after carefully reading thru the forums so i do not true brick it again.
Anyway, for some weird reason, pulled it out just to charge the battery, and it requested to do an update (since it was connected via wifi), it tried and got stuck (praise the Lord) and Im just now reading this realizing I almost just GOOFED UP BIG TIME. So, wanted to take the time to thank the OP for this post which made me aware of the fact that I would be SOL if I had've upgrade and to prevent me from upgrading. THANKS!!!
xPSYB0RGx said:
Wow, I almost just majorly screwed myself (again). I have the shift and its just been sitting in my drawer, waiting to be activated after carefully reading thru the forums so i do not true brick it again.
Anyway, for some weird reason, pulled it out just to charge the battery, and it requested to do an update (since it was connected via wifi), it tried and got stuck (praise the Lord) and Im just now reading this realizing I almost just GOOFED UP BIG TIME. So, wanted to take the time to thank the OP for this post which made me aware of the fact that I would be SOL if I had've upgrade and to prevent me from upgrading. THANKS!!!
Click to expand...
Click to collapse
sooo.... hit the thanks button then
They've recently rooted the Sensation and EVO 3D...hopefully it will trickle down to us Shift owners....
Stuke00 said:
sooo.... hit the thanks button then
Click to expand...
Click to collapse
I thanked the OP, and I thanked u for reminding me to be "thankful"!!
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
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