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
Please listen up!
When the 2.1 is released;
Do not update your phone with the RUU from htc website or OTA because it will most likely lock up your bootloader and make you unable to downgrade, root and it will replace/delete you custom recovery boot menu and therefore UNABLE TO ROOT,DOWNGRADE AND FLASH ANY CUSTOM ROM!
I recommend waiting for a 2.1 based villain version or MODACO 4
YOU'VE BEEN WARNED; YOUR PHONE MAY BE "WRECKED"
if you goto modaco htc hero forum you'll find a similar thread with more information.
OFFICIAL SOURCE
www.villainrom.co.uk/viewtopic.php?f=9&t=28
Thanks for the informations dude!
so when modaco 4 will release? waiting for.....
Thanks Yeah i planned on waiting for a rooted 2.1 update-hero-generic-x.xx.xxx.xx-release-rooted rom for flashing with recovery.
where is this discussed??
Link please
Dan330 said:
where is this discussed??
Link please
Click to expand...
Click to collapse
OFFICIAL SOURCE!
www.villainrom.co.uk/viewtopic.php?f=9&t=28
Thanks for pointing out my little 'article' over on VillainROM.co.uk
As we approach the end of the week, and the point where something interesting might appear at any time, please make sure everyone knows not to flash an RUU.
To re-iterate what I said over there, if you get access to the official RUU in your country or from your provider, please let one of the admins or moderators on VillainROM.co.uk know (you can identify us with the red and green nametags, or by clicking 'the team' at the bottom of the home page. We will then provide you with temporary login details to FTP the file to our server, and the update will be re-released within hours (probably within minutes of uploading)
Cheers, and don't go RUU-ing
Please make it a stickie.
Hertus said:
Thanks for the informations dude!
so when modaco 4 will release? waiting for.....
Click to expand...
Click to collapse
I assume modaco 4 will be released shortly after the official 2.1 RUU, but it will always be well.. alpha and betas before the "real" modaco 4 is finished and we also have to wait until Teknologist releases his tweaked kernel to get the real modaco as we know from 3.2
Thank you!.... I was planning on installing the official one as soon as it is available under the assumption I could just flash a custom over the top of it once they had been tweaked.
You've saved me some heartache.
Assumption is definitely the mother of all f'ups.
Thanx again.
ddotpatel said:
Thank you!.... I was planning on installing the official one as soon as it is available under the assumption I could just flash a custom over the top of it once they had been tweaked.
You've saved me some heartache.
Assumption is definitely the mother of all f'ups.
Thanx again.
Click to expand...
Click to collapse
Glad someone's been saved... Perhaps we should get a viral tweet going I'll start one tonight if I remember...
Pass the message on, folks...
Tweeted via. my user below. Feel free to add me and RT to android users etc. Spread the word, and hopefully we won't even need to find a way to root the new update
hehe before i look at this post i was thinking "the official 2.1 must be out any time soon,should i flash it or wait for the customs..?"....question solved
So.. Even other downgrading (like GoldCards) methods wont work..?
How
I can solve this problem
Because it happen yo my
I was rooed my hero
on day i run .exe file for htc ruu
it work at first but un the end it but me error
What i can do
sorry i but my broke English
harsha_aithal said:
So.. Even other downgrading (like GoldCards) methods wont work..?
Click to expand...
Click to collapse
think about this: you are htc. you don't want people to root their phones. you get a major upgrade out there, and you know about the methods how to crack the security of the phone. would you fix them or not?
If somebody have SPL 1.76.2007 installed and wish to try official 2.1 form HTC you can do it in the following way:
1. Get rom.zip from 2.1 RRU
2. Unpack it on you hard disk
3. Make new archive HEROIMG.zip with following files from rom.zip:
- android-info.txt
- splash1_Hero_320x480.nb0
- boot.img
- radio.img
- system.img
- userdata.img
DO NOT INCLUDE recovery file (recovery.img) and SPL file (with name like hboot_7200A_1.76.0007_090804.nb0) into HEROIMG.zip.
4. Flash HEROIMG.zip
In this case you will able to root, downgrade or install custom rom.
FYI:
VillainROM will really come into life when we have the official 2.1 update.
But on topic - he's right. Remember those that used the official update last time and had to use the goldcard method to flash recovery?
We don't want that all over again.
Agreed: Sticky.
Al936 said:
4. Flash HEROIMG.zip
Click to expand...
Click to collapse
flash through recovery image? would that work?
kendong2 said:
flash through recovery image? would that work?
Click to expand...
Click to collapse
well surely you would have to sign it?
Making a ROM out of an RUU is a piece of piss
As soon as we have it, it's a battle of the upload speeds.
There will be a lot of ROMs out there, all based on the same build; too similar to differentiate.
Lennyuk said:
well surely you would have to sign it?
Click to expand...
Click to collapse
yes, but it is still lacking an update-script, and contains only .img files. from what i know that is not suitable for the recovery... it might work with the unlocked bootloader, that is correct, but for that you need to flash every partition with the corresponding image...
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
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
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