V3 is OTA, only file OTA has that V3 does not have is \System\App\UpgradeSetup.apk
V3 obviosuly has files that OTA does not because OTA is not a full upgrade, it is the only difference. So, Enjoy. Even the radio, recovery, and boot are the same as V3.
FireSokar said:
V3 is OTA, only file OTA has that V3 does not have is \System\App\UpgradeSetup.apk
V3 obviosuly has files that OTA does not because OTA is not a full upgrade, it is the only difference. So, Enjoy. Even the radio, recovery, and boot are the same as V3.
Click to expand...
Click to collapse
Okay, See if they can install that .apk if not... then ohh well, not a big deal.
That upgradesetup.apk is used by the device after the upgrade only to Upgrade the device... in otherwords not needed at all
What happend to friendstream???
edgeupgx said:
What happend to friendstream???
Click to expand...
Click to collapse
I'm pretty sure friendstream is an Sprint rom application that was ported over to the Eris.
Friendstream was never supposed to be on the Eris 2.1
Well its not it was in the update notes it really isnt even something I care about but its not there. Another thing there is talk that people that went from 1.5 to 2.1 ota are still able to root so there have to be some pretty big differences between the two.
You are mis-reading it. The only reason people would be able to is if bootloader doesnt get updated. This is allready updated past the s-OFF on a leaked non rooted 2.1 - The only hope is if what Zifnab is working on is completed.
andrew8806 said:
Friendstream was never supposed to be on the Eris 2.1
Click to expand...
Click to collapse
Gah must have been one of those stupid blogs I read that said it was getting it I know I had saw it somewhere that it would be included.
edgeupgx said:
Gah must have been one of those stupid blogs I read that said it was getting it I know I had saw it somewhere that it would be included.
Click to expand...
Click to collapse
But if you were root you could get it on just about any Sense rom... ie:EvilEris 2.0.1, HDLegend, etc.
V3 is very different from OTA.........mainly the fact that OTA does not change HBOOT and you can still ROOT once you have done OTA. Check the thread over at androifforums. I cannot post links as this is my first post.
I am the one that verified this and will fully root my phone tonight.....99% positive it will work.
ssgtob1 said:
V3 is very different from OTA.........mainly the fact that OTA does not change HBOOT and you can still ROOT once you have done OTA. Check the thread over at androifforums. I cannot post links as this is my first post.
I am the one that verified this and will fully root my phone tonight.....99% positive it will work.
Click to expand...
Click to collapse
Umm... im pretty sure you can't root the OTA just yet.... I don't care what AF says... lol... effin n00bz
Unless... one of our fine devs have already gotten it... but i dont think so yet!!!!!
FireSokar said:
You are mis-reading it. The only reason people would be able to is if bootloader doesnt get updated. This is allready updated past the s-OFF on a leaked non rooted 2.1 - The only hope is if what Zifnab is working on is completed.
Click to expand...
Click to collapse
He said 1.5 -> OTA 2.1, not leaker... so, their bootloader has not gone past the S-OFF version, if as you suggest the bootloader stays untouched.
Have a peek at ./META-INF/com/google/android/update-script (look for write_raw_image); it sort of looks like the kernel image (boot.img) and recovery partition are written, but a cursory inspection shows nothing similar for the bootloader, nor any files in the .zip which are exactly 512 kB.
As far as doing a file comparison between a post-install OTA phone and the leak-V3 code, it seems like a dev would actually have to compare post-patched code from the phone, something like this: (?)
1) Restore 1.5 but leave S-OFF in place (folks who did the Toastcfh "battery pull" can do this).
2) Run the update.zip (and pray that the bootloader is untouched).
3) Use fastboot+S-OFF to re-installl Amon_RA's recovery
4) Boot to recovery, and use adb to pull everything from /system, /data partitions back to the dev's PC
5) Restore whatever ROM you please
6) On the PC, compare phone files to leak V3 files (compare checksums or run binary diffs).
An even safer way would be to run the update in an emulator instance, but I'm not exactly sure how to set that up. (The SDK emulator is based off of QEMU - you can run arbitrary ARM code in it, but the update obviously needs to start with the Eris 1.5 code in the emulator).
On other matters, I note that there are some assertions at the beginning of the patch run:
Code:
assert file_contains("SYSTEM:build.prop", "ro.build.fingerprint=verizon/htc_desirec/desire
c/desirec:1.5/CUPCAKE/104882:user/release-keys") == "true" || file_contains("SYSTEM:build.
prop", "ro.build.fingerprint=verizon/htc_desirec/desirec/desirec:2.1/ERD79/165907:user/rel
ease-keys") == "true"
Anybody know which HTC leak matches the "2.1/ERD79" fingerprint?
Also, call me paranoid, but methinks HTC or Verizon are dicking with us - look at the ridiculous timestamps in the .zip file. Nobody is that sloppy.
bftb0
ssgtob1 said:
I am the one that verified this and will fully root my phone tonight.....99% positive it will work.
Click to expand...
Click to collapse
I hope it works out...
Manually updating with the OTA file definitely does not change HBOOT at all. I had 1.47 before and I still have 1.47......leakers all have 1.49....if you need a video I can make that happen......and andrew no need to call anyone an effin noob, I have probably done more with software in the last 24 hours than you have in your lifetime.....all I am saying is that if you install the OTA you still have the option of rooting. I took the roo pb00img.zip after I did the OTA and HBOOT recognised it as valid and would allow me to upgrade.
andrew8806 said:
How are you gonna root on 2.1 OTA? lmao... seriously dude... nevermind... I give up...
1 post on xda and now he thinks he can root 2.1 OTA.... when our devs have been hard at work trying to find an exploit... lol
Click to expand...
Click to collapse
He's right. If you go from 1.5 to 2.1 OTA you can still root.
ssgtob1 said:
Manually updating with the OTA file definitely does not change HBOOT at all. I had 1.47 before and I still have 1.47......leakers all have 1.49....if you need a video I can make that happen......and andrew no need to call anyone an effin noob, I have probably done more with software in the last 24 hours than you have in your lifetime.....all I am saying is that if you install the OTA you still have the option of rooting. I took the roo pb00img.zip after I did the OTA and HBOOT recognised it as valid and would allow me to upgrade.
Click to expand...
Click to collapse
#1 i wasn't calling you a n00b... I meant half the people in AF... so its whatever man... hope it works out for you.. No harm no foul...
#2 I hope it works out for you really do....
#3 if it does, I will apologize and welcome to root... If it doesn't then ohhh well...
andrew8806 said:
How are you gonna root on 2.1 OTA? lmao... seriously dude... nevermind... I give up...
1 post on xda and now he thinks he can root 2.1 OTA.... when our devs have been hard at work trying to find an exploit... lol
Click to expand...
Click to collapse
Whatever.....just trying to help......but I get flamed by some asshole instead
I guess the real question is... why did the leaks change the bootloader? that seems odd to me.
bftb0 said:
Anybody know which HTC leak matches the "2.1/ERD79" fingerprint?
Click to expand...
Click to collapse
The latest one (called leak 3, actually the 4th leak ) is the same: ro.build.fingerprint=verizon/htc_desirec/desirec/desirec:2.1/ERD79/165907:user/release-keys
Related
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
Ok...so I did the 2.1OTA manually off of my sd card and noticed that HBOOT did not change so I flashed with pb00img.zip(root) and pulled the battery when it re-booted. I then used fastboot to load the RA-eris-v1.6.2 recovery image. I now have a backup from nandroid of my 2.1OTA if any of you would think that this is helpful.
64 views....no reply??
reply for what, you rooted the ota from 1.5, they knew that already.
jearl75 said:
reply for what, you rooted the ota from 1.5, they knew that already.
Click to expand...
Click to collapse
No I rooted from 2.1OTA
ssgtob1 said:
... so I flashed with pb00img.zip(root) and pulled the battery when it re-booted. I then used fastboot to load the RA-eris-v1.6.2 recovery image...
Click to expand...
Click to collapse
Sounds scary on paper, but no big deal once you've done it, eh?
Enjoy your freedom; plenty of ROMs to try... and they keep getting better every day.
bftb0
ssgtob1 said:
No I rooted from 2.1OTA
Click to expand...
Click to collapse
Yea, they already know about it. The OTA is more of a patch update so it doesn't update hboot. Right now you probably have an hboot version of 1.46 or 1.47 and leakers have 1.49. The rooted 2.1 rom has a lower version number than the leak (v1,v2, and v3) version number. That's one reason we can't downgrade. You're able to because yours didn't change. If we could get a rooted rom with a higher hboot or make the eris not verify the sigs on the updates/recovery images then we could have root in a snap. Unfortunately, that's not the case...
you backup will contain the 2.1 root image.
Thanks for the info. This is now more or less confirmed in my mind.
2.1 ota DOES NOT contain a bootloader in it, meaning the phone keeps the original bootloader. AKA rootable.
jcase said:
you backup will contain the 2.1 root image.
Thanks for the info. This is now more or less confirmed in my mind.
2.1 ota DOES NOT contain a bootloader in it, meaning the phone keeps the original bootloader. AKA rootable.
Click to expand...
Click to collapse
so we can do the update and still be able to have recovery and rooting from what i'm reading off of this.... sweet!!!
PM sent to the OP requesting a copy of the system image, if at all possible. Sorry for cross-posting.
I'll retreat back to the GSM forum
anon2122 said:
PM sent to the OP requesting a copy of the system image, if at all possible. Sorry for cross-posting.
I'll retreat back to the GSM forum
Click to expand...
Click to collapse
Grab it off eris leak 3, same image but full. the OTA is a patch.
jcase said:
Grab it off eris leak 3, same image but full. the OTA is a patch.
Click to expand...
Click to collapse
Excellent. Thanks mate. Got it downloaded.
Cheers,
P
Sounds cool :]
So is it safe to give someone my system.img?
Download ROM HERE
It seems to be a Verizon Droid Eris 2.1 Official ROM.
RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed_with_driver.exe
Anyone test this on their Eris yet?
Its an ruu, I suspect of the OTA maybe. Don't flash if you are root or 1.5
what about leaked v3 ok to flash?
I'm testing it right now. I was running leak v1. Will post results when it's complete.
tereg said:
I'm testing it right now. I was running leak v1. Will post results when it's complete.
Click to expand...
Click to collapse
Ok Thanks buddy
Tried it on leak v3. I still have hboot 1.49 so no change there. Other than that, the only thing that changed was the build number. It now has release-keys instead of test-keys after it. It is the OTA, just doesn't really do much for those running leak v3 and looking to root.
Flash successful HBOOT v 1.49.0000 S-ON
Radio 2.42.00.04.12
Conflipper, I cross-posted this on android forums .com and I gave you credit for posting it. Thank you! This will help all of the folks who are stuck on earlier non-root leaks and just want to get up to the current version (but are having trouble flashing the "leak v3" zip manually).
I've verified that the rom.zip within this RUU is identical (based on checksums) to the non-root PB00IMG.ZIP known as "leak v3" (the fourth leak).
thenestor said:
Conflipper, I cross-posted this on android forums .com and I gave you credit for posting it. Thank you! This will help all of the folks who are stuck on earlier non-root leaks and just want to get up to the current version (but are having trouble flashing the "leak v3" zip manually).
I've verified that the rom.zip within this RUU is identical (based on checksums) to the non-root PB00IMG.ZIP known as "leak v3" (the fourth leak).
Click to expand...
Click to collapse
but this may give us the ablitly to regain further updates, instead of verizon not giving us leakers no mo updates
feel free to spread the word, and get this out there. Spread the word, I am sure people will want the "Official" file.
i keep on getting error about connectiviy to the phone which i have it connected and idk,
also ever other time i try it gives me your battery is less than 30% which its at 68% so idk about that either.
i couldnt get it to work. im gonna give it another redownload and see
mattv3090 said:
Tried it on leak v3. I still have hboot 1.49 so no change there. Other than that, the only thing that changed was the build number. It now has release-keys instead of test-keys after it. It is the OTA, just doesn't really do much for those running leak v3 and looking to root.
Click to expand...
Click to collapse
Your rom had "test-keys" after it before you flashed this? That means you were rooted? If so you just lost root
jearl75 said:
Your rom had "test-keys" after it before you flashed this? That means you were rooted? If so you just lost root
Click to expand...
Click to collapse
i think he meant he was already running leak 3... and not rooted.
Does this bring all the 2.1 Sense UI features to the Eris like friendstream etc?
jearl75 said:
Your rom had "test-keys" after it before you flashed this? That means you were rooted? If so you just lost root
Click to expand...
Click to collapse
LOL
Perhaps folks should try re-reading what thenestor reported up above in this very thread:
[SIZE=+1]The ROM that is bundled inside this RUU IS IDENTICAL TO LEAK-V3[/SIZE].
Don't get your hopes up if you are a leaker; this is only useful for folks who mysteriously were able to manage Leak-V1 (the first leak) or Leak-V2 (the third leak), but are somehow now unable to repeat exactly the same procedure with the Leak-V3 (fourth leak) PB00IMG.ZIP.
bftb0
tenzomonk said:
i think he meant he was already running leak 3... and not rooted.
Click to expand...
Click to collapse
All the leaks (excepting the 2nd chronological leak, the "root-ROM") were shipped with release-keys.
The root-ROM was the only one that reported "test-keys".
bftb0
bftb0 said:
LOL
Perhaps folks should try re-reading what thenestor reported up above in this very thread:
[SIZE=+1]The ROM that is bundled inside this RUU IS IDENTICAL TO LEAK-V3[/SIZE].
Don't get your hopes up if you are a leaker; this is only useful for folks who mysteriously were able to manage Leak-V1 (the first leak) or Leak-V2 (the third leak), but are somehow now unable to repeat exactly the same procedure with the Leak-V3 (fourth leak) PB00IMG.ZIP.
bftb0
Click to expand...
Click to collapse
Right! If people are on the leak and are not holding out for the slim chance of root, they should flash this. Atleast they will have an "official" release
jearl75 said:
Right! If people are on the leak and are not holding out for the slim chance of root, they should flash this. Atleast they will have an "official" release
Click to expand...
Click to collapse
What?
If it is IDENTICAL to Leak-V3; as far as the phone is concerned, how would it be any more or any less official?
I'm wondering, what do people think "Identical" means?
Coinflipper needs to "get the word out" that there is a new copy of Leak-V3 floating around; his OP reads as if this is something new, when it is not.
Wow, great news! It will encourage folks like the poster up above to rush out and unroot their phone.
Oh well, more power to them... or less, as the case may be.
bftb0
bftb0 said:
What?
If it is IDENTICAL to Leak-V3; as far as the phone is concerned, how would it be any more or any less official?
I'm wondering, what do people think "Identical" means?
Coinflipper needs to "get the word out" that there is a new copy of Leak-V3 floating around; his OP reads as if this is something new, when it is not.
Wow, great news! It will encourage folks like the poster up above to rush out and unroot their phone.
Oh well, more power to them... or less, as the case may be.
bftb0
Click to expand...
Click to collapse
First of all I said "those on a leak", didn't say leak v3. Just to bring you up to speed there are 2 leak versions before v3, hence the v3. It would be more official because this one WAS released by Verizon, whereas the leaks were not, which is why they were leaks. It is identical yes, but the build number is different, which would differentiate between leak v3 and this OFFICIAL release should you need to return your phone. Just because the support people might not be able to tell, someone can believe me. I know people who have returned there leak and been charged for a new phone because they had unofficial software on there phone, never even mentioning it. This was a month or more later, just showed up right there on there bill.
So, people who feel better having an official release (whether your on leak v1, v2, or v3) can flash this, it's official. If someone who has root can't read where it says this is for people on the leaks, if you have or ever want root don't update. Then that's their problem, not much you can do about that....
I have rooted and upgraded my Wildfire to 2.2.1 from 2.1, worked fine and still does, but i have lost root.
I have read that i cant use the "unrevoked method" yet to get root back as it wont work with Froyo. Is this true or is it safe to do so.
If I cant use that method then can anyone suggest another way.
Thanks and be gentle as i am new to android.
magpie22 said:
I have rooted and upgraded my Wildfire to 2.2.1 from 2.1, worked fine and still does, but i have lost root.
I have read that i cant use the "unrevoked method" yet to get root back as it wont work with Froyo. Is this true or is it safe to do so.
If I cant use that method then can anyone suggest another way.
Thanks and be gentle as i am new to android.
Click to expand...
Click to collapse
Hi, if you updated with OTA update (official) or with RUU, you can't root. We have to wait until some depeloper find out the way to root the new HBOOT.
I updated with a file called signed_121810_120233.zip if that helps.
Anyone know about that file, if its official or RUU
magpie22 said:
I updated with a file called signed_121810_120233.zip if that helps.
Anyone know about that file, if its official or RUU
Click to expand...
Click to collapse
I'm downloading it to see if it has the new HBOOT. Give me a minute
EDIT: It doesn't contain the new HBOOT, so you should be able to root. Trying Unrevoked is safe. If you had the new HBOOT, it would hang, but you wouldn't have any problem.
For what I read, you haven't run Unrevoked yet. Do it.
Thank you for your time and effort, i will try it later tonight when i get back home.
Will post and tell you the outcome.
Thanks
magpie22 said:
Thank you for your time and effort, i will try it later tonight when i get back home.
Will post and tell you the outcome.
Thanks
Click to expand...
Click to collapse
Great
Ok that did not work, it went through the process but said failed to get root, and asked if firmware was to new?
magpie22 said:
Ok that did not work, it went through the process but said failed to get root, and asked if firmware was to new?
Click to expand...
Click to collapse
You have done this in the same computer you did the time it worked, right? For the HBOOT drivers in windows and all these things.
Looking at the zip you sent me, you should be able to root, but I guess that if you lost root, there is something that made you lose it. :S
If you want to try to get root anyway, try Unrevoked in Ubuntu. If not, Superoneclick, or Z4root.
But doesn't look good to root by now... :S
Yeah the exact same pc that i first used to go from 2.1 to 2.2.
Is Z4 safe to use
magpie22 said:
Yeah the exact same pc that i first used to go from 2.1 to 2.2.
Is Z4 safe to use
Click to expand...
Click to collapse
Yes, the worst thing that can happen is that the phone is slow until you reboot, if it can't get root. But htese methods are Temp root. It would be just to see if you can get root access, which I doubt at the moment.
Thanks for your help, i think i will just wait until unrevoked gets updated.
magpie22 said:
Thanks for your help, i think i will just wait until unrevoked gets updated.
Click to expand...
Click to collapse
That's what I have to do, I'm in a similar situation for stupidly installing Froyo RUU...
If you notice an update to unrevoked can you PM me and let me know?
magpie22 said:
If you notice an update to unrevoked can you PM me and let me know?
Click to expand...
Click to collapse
Of course. I just tried with v3.31, which must be the version you tried. I got your same error.
I will let you know. It must be near, because in v3.3 changelog they say "No update for Wildfire yet, sorry", so they are working on it.
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