Related
I have a new Sprint HTC Hero and was wondering what I would benefit from rooting my new phone.
everything
pretty much anything you would like.
one of my favorite functions is WIFI tether for my laptop and iTouch.
another cool feature is the latest "Fresh" rom. which is currently 1.1
its much faster than the stock sprint rom. plus its pretty!
P.S. and if you ever want to go back to stock you can do that as well!
if nothing else
I rooted my phone for this one reason. I wanted to be able to do back ups of my entire system that way if anything happened, then I didnt have to spend hours redoing everything. eventually though I have become a flash addict. I run fresh 1.1 for my daily rom and I play with AOSP 1.6 and flipzmod and companys 2.1 beta at night. all 3 are great but fresh 1.1 is the most stable
wtphoto said:
I rooted my phone for this one reason. I wanted to be able to do back ups of my entire system that way if anything happened, then I didnt have to spend hours redoing everything. eventually though I have become a flash addict. I run fresh 1.1 for my daily rom and I play with AOSP 1.6 and flipzmod and companys 2.1 beta at night. all 3 are great but fresh 1.1 is the most stable
Click to expand...
Click to collapse
very well put, i forgot about mr nandroid!
Thanks for the info. I have just one more question. If I root my phone can I just update it to software version 2.1 when Sprint releases it in the very near future, or will I need to wait for some kind of release from this site?
Thanks.
you'll most likely need to update using a rom from this site. The good thing is, that there will be a release here of it within 24-48 hours.
obelisk79 said:
you'll most likely need to update using a rom from this site. The good thing is, that there will be a release here of it within 24-48 hours.
Click to expand...
Click to collapse
Why is that? Why can't he flash to an official rom then update?
Well actually you can go ahead and get the 2.1 update from sprint when it's released, that will undo root though, and since no one has seen it re-obtaining root would take a while for someone to figure out again. That and the 2.1 will probably be available here in leaked form before sprint releases it anyway at least all my windows mobile phones saw leaks on XDA before the carrier. Root is good and should be worth it if you are the kind of guy that likes playing with their tech instead of just using it, otherwise you may be getting yourself into more than you're willing to put up with longterm.
If he flashes the official 2.1 rom when it is released, it is very likely that will invalidate current methods to root the cdma hero. Then you'll have to wait for a new root method to be found. It is also very possible/likely that upgrading to 2.1 via the official RUU once released will make it impossible to flash the 1.5 based RUU's to regain root.
So effectively he could update but would lose the capability to root the device and all of the resulting benefits it offers until a new root method is discovered.
Edit: thezero4 beat me to it, and is also very correct.
my bad wrong thread
Thanks for all of your input and information. It was very helpful and my phone is now rooted and running the fresh rom. Awesome.
I'm still new to this.
How do you backup your phone.
How would you put everything back to stock if needed.
Thanks so much for any help.
schultzy001 said:
Thanks for all of your input and information. It was very helpful and my phone is now rooted and running the fresh rom. Awesome.
I'm still new to this.
How do you backup your phone.
How would you put everything back to stock if needed.
Thanks so much for any help.
Click to expand...
Click to collapse
to perform a nandroid backup there are 2 options. you can either use the fresh pre-kitchen and perform your backups and restores from you comp or you can boot into recovery and go to backup/restore and then go to nandroid backup (this is also how you would restore any of your back ups).
as far as returning to stock. If you didn't make a backup before you flashed fresh then you need to download the stock RUU file here.
BTW help support flipz and what he does for us, visit his site and click on the adds.
Since the 2.1 new update was released, I figured it would be a higher version number than our leaked 2.1. That means we could hboot it to our phones to update.
But wait, could some developer root this update (maybe in a similar to the way they rooted 1.5 to 2.1 root) so the leaked 2.1 people could hboot to this new update for 2.1 except it would be rooted.
Sorry if that was confusing.
Here's where the update was found:
androidforums.com/htc-droid-eris/55898-you-dont-need-root-new-leak.html
As far as I understand it, the reason that 2.1 OTA can be installed for users running leaked 2.1 is because it has a higher subversion number and it is SIGNED. That is the tricky part. Because your SPL / HBoot is S-ON, meaning that it will only install signed zips, you are still unable to install a rooted 2.1. The reason that the exploit worked on 1.5 is because the PB00IMG.zip IS a signed package, but the versioning only puts it ahead of 1.5, not Leaked 2.1 or OTA 2.1. Once the PB00IMG.zip is installed, it turns S-OFF so that unsigned (e.g. rooted) packages. From what I have read in other posts, devs are moving toward trying to find exploits in the new 2.1 OTA for users who have already upgraded without root. I would personally recommend doing the 2.1 OTA and hanging tight for the next exploit.
Thank you man. So, would it not be possible to turn S-OFF in this new update? I understand that would require going in and tampering with the files, which could break the signature on the package, possibly?
Precisely, if you change one bit of a signed file, the signature changes completely. As I understand it, the PB00IMG.zip file that is used to root 1.5 phones was "stumbled upon" already signed by HTC. For any future rooting for people with 2.1, this file is unusable because the versioning of this convenient package is older than what leakers and official 2.1 adopters have. It is impossible to modify the 2.1 update without breaking the sig. We now have to hope that devs can find an exploit or broken code in the new 2.1 update that allows for rooting by another means.
If you are desperate, feel free to try to socially engineer Verizon. That has met with considerable success from some other early adopters. If not, play the waiting game. In the mean time, feel free to upgrade to the OTA 2.1 leak. It fixes some things like Google relogin.
shickfaced said:
Precisely, if you change one bit of a signed file, the signature changes completely. As I understand it, the PB00IMG.zip file that is used to root 1.5 phones was "stumbled upon" already signed by HTC. For any future rooting for people with 2.1, this file is unusable because the versioning of this convenient package is older than what leakers and official 2.1 adopters have. It is impossible to modify the 2.1 update without breaking the sig. We now have to hope that devs can find an exploit or broken code in the new 2.1 update that allows for rooting by another means.
If you are desperate, feel free to try to socially engineer Verizon. That has met with considerable success from some other early adopters. If not, play the waiting game. In the mean time, feel free to upgrade to the OTA 2.1 leak. It fixes some things like Google relogin.
Click to expand...
Click to collapse
So, I installed the first 2.1 leak. Can I install this new one that just came out in the last couple days? Sorry, guess I'm not seeing the answer here
If we were able to find a way to modify the update to include root with a valid signature, we would also be able to modify the version number to a higher number than the current 2.1 leak. I'm pretty sure upgrading to the "official" 2.1 won't hurt our chances of finding root, it'll just make the wait less buggy
jearl75:
Yeah, you can install the new leak over the old one, no worries.
so should us people on the first 2.1 leak upgrade to the newest one or stay on the first one??
theboo7 said:
so should us people on the first 2.1 leak upgrade to the newest one or stay on the first one??
Click to expand...
Click to collapse
I reckon that depends on if you're experiencing the Google login bug or not. My wife's Eris with the first leaked 2.1 is not. And if you are experiencing that bug, which is more hassle...logging into Google repeatedly, or rebuilding your phone (apps, contacts, etc) from scratch??
Dangerous Dave said:
I reckon that depends on if you're experiencing the Google login bug or not. My wife's Eris with the first leaked 2.1 is not. And if you are experiencing that bug, which is more hassle...logging into Google repeatedly, or rebuilding your phone (apps, contacts, etc) from scratch??
Click to expand...
Click to collapse
its not that bad since i rarely restart my phone, i guess my real question would be would it make it longer until i get root? or are devs trying to root the NEW 2.1 instead of the old 2.1
I apologize if this gets old, but I am trying to be cautious so I don't brick my phone...
I downloaded the following leaked 2.1 version a few weeks ago, and have this installed:
Baseband version: 2.40.00.01.22
Kernel version: 2.6.29-5898f66b / [email protected] #1
Build number: 2.19.605.1 CL12345 test-keys
Software number: 2.19.605.1
I have a problem installing the new version of Google Maps. Phone dial can be sluggish and/or unresponsive at times, but it is manageable. Overall, the installation of the leaked ROM went fine, and I feel like I am pushing my luck if I try to download the latest ROM. Does anyone know if the latest release addresses the issues above? I am not experiencing any of the login issues to Gmail that others are experiencing.
My question is this: Should I just leave well enough alone and wait for the OTA at this point?
Thanks for any suggestions.
mdeavers said:
I apologize if this gets old, but I am trying to be cautious so I don't brick my phone...
I downloaded the following leaked 2.1 version a few weeks ago, and have this installed:
Baseband version: 2.40.00.01.22
Kernel version: 2.6.29-5898f66b / [email protected] #1
Build number: 2.19.605.1 CL12345 test-keys
Software number: 2.19.605.1
I have a problem installing the new version of Google Maps. Phone dial can be sluggish and/or unresponsive at times, but it is manageable. Overall, the installation of the leaked ROM went fine, and I feel like I am pushing my luck if I try to download the latest ROM. Does anyone know if the latest release addresses the issues above? I am not experiencing any of the login issues to Gmail that others are experiencing.
My question is this: Should I just leave well enough alone and wait for the OTA at this point?
Thanks for any suggestions.
Click to expand...
Click to collapse
I Know that when I installed the new Leak, the dialer lag was MUCH improved, as was the phone signal and general stability, Gmail doesn't make you log back in every reboot, and on my phone my "get more HTC widgets" link is fixed. But I heard on others phones it wasnt. It Does wipe all your apps even though its 2.1 -> 2.1. But Just like last time the SD card is untouched.
The installation process is exactly the same. I recommend it.
EDIT- Actually I just noticed the build you have installed is test keys signed and to my knowledge only the root rom was test key signed. This being the case if you want to keep root I would flash a custom cooked ROM... Since your lucky enough to have the chance to do so... Sigh..
Wait, test keys signed means what exactly? My Eris reads that but I only installed the two leaks AFAIK?
Does it just mean signed by HTC?
thawkth said:
Wait, test keys signed means what exactly? My Eris reads that but I only installed the two leaks AFAIK?
Does it just mean signed by HTC?
Click to expand...
Click to collapse
So you only installed the 2.1 non-root Leaks??? I may be mistaken, but both times I flashed the leaks, 2.1a +2.1b, both had builds signed with release keys... I was under the impression that only the 2.1 leak+root was signed with test keys.
Shed some light developers?
Whitepaint said:
So you only installed the 2.1 non-root Leaks??? I may be mistaken, but both times I flashed the leaks, 2.1a +2.1b, both had builds signed with release keys... I was under the impression that only the 2.1 leak+root was signed with test keys.
Shed some light developers?
Click to expand...
Click to collapse
You are exactly correct: Both of the leaked 2.1 roms have release keys, while the 1.5->2.1 root rom (and any rom based on that upgrade) will have test keys.
my girl has a rooted 2.1 with release keys. download Grdlocks ota rom
ahjee said:
my girl has a rooted 2.1 with release keys. download Grdlocks ota rom
Click to expand...
Click to collapse
Interesting...can you post the software version/info from your phone settings?
ahjee said:
my girl has a rooted 2.1 with release keys. download Grdlocks ota rom
Click to expand...
Click to collapse
Thats most probably because Grdlocks ota rom is based on just that, the 2.1 ota leak, not the 2.1+root rom. The Beauty of custom roms...
Sorry no one has been clean on this before:
The 2.1 leak was leaked from HTC by riverrunner. We actually don't care about the hboot version, radio version is the main thing updaters look at (we've found that out since root).
The 2.1 update that had root built in was also an HTC leak. It contained SU. That was the difference. We didn't do ANYTHING to get root. ABSOLUTELY NOTHING. It was leaked by someone at HTC. Simple enough. So, we CANNOT redo this, becuas we did NOTHING.
Hope this clears it up. Thanks!
zifnab06 said:
Sorry no one has been clean on this before:
The 2.1 leak was leaked from HTC by riverrunner. We actually don't care about the hboot version, radio version is the main thing updaters look at (we've found that out since root).
The 2.1 update that had root built in was also an HTC leak. It contained SU. That was the difference. We didn't do ANYTHING to get root. ABSOLUTELY NOTHING. It was leaked by someone at HTC. Simple enough. So, we CANNOT redo this, becuas we did NOTHING.
Hope this clears it up. Thanks!
Click to expand...
Click to collapse
I'm glad this was finally publicly admitted. I got kind of tired of the devs going around pretending they actually did something besides getting lucky with a leak.
12134567890
For those who didn't dare to try... I got Froyo running on an AT&T version. All you need is to follow this guide: http://www.androidspin.com/2010/05/...-nexus-one-its-like-it-never-happened-almost/
Flash the ERD79 Release, update to EFE27. Then run the Froyo update through Stock recovery. 3G works fine, radio updated (I think?) and everything is fast.
thanks for your post. but the issue that most ATT N1 users are facing is updating to 2.2/Froyo from their non-rooted, bootloader-locked. devices.
vexingv said:
thanks for your post. but the issue that most ATT N1 users are facing is updating to 2.2/Froyo from their non-rooted, bootloader-locked. devices.
Click to expand...
Click to collapse
I think that rooting and unlocking the bootloader it's the way to go now, since like everybody has done it.
poorg said:
I think that rooting and unlocking the bootloader it's the way to go now, since like everybody has done it.
Click to expand...
Click to collapse
Translation:
"Everybody's doing it, come on. What are you, chicken?"
/peerpressure
I'm one that hasn't rooted, yet. Party due to my phone is less than two weeks old and I don't want to void the warranty just yet.
I just went from KangoRama to full wipe to Froyo...
Having owned several HTC phones, there's no way I'm voiding my warranty
Lot of trouble for nothing, if you are already rooted and have Amon's recovery. Just install Paul's Rooted Froyo and you've got the same thing, except with root.
rooting doesnt void hardware warranty
Experienced it
Froyo using AmonRa recovery - WORKS!
Followed some success off CM's forums in getting Froyo up and running on an AT&T N1. In fact it's been pretty error free (short of a couple apps not behaving with 2.2) and to top it off, no wipe needed.
Paul over on Modaco's site managed to pop up an image that is rooted and works with AmonRa's recovery. All I did was copy the zip to the SD card, ran recovery, flashed from SD, and voila! Froyo without having to painstakingly reinstall all my apps. No issues with 3G so far, but like all stock roms, there's no indication of running HSDPA unless you go into the about phone option in settings.
So far cooling off the hot day with some Froyo here.
Paul's Original Post on Modaco
Edit: And yes, if you didn't boot unlock your phone and want 2.2, then your only choice is waiting for the OTA to eventually hit you... when it goes public instead of press-only.
Are you able to view large images on your browser?
I know I'm not :S
http://forum.xda-developers.com/showthread.php?t=687256
update
I followed the guide and went from erd79 to ere27 but when trying to update to froyo my N1 would not boot completely. Ran adb logcat and watched the log and it looped running the same stuff over and over again.
x986123 said:
For those who didn't dare to try... I got Froyo running on an AT&T version. All you need is to follow this guide: http://www.androidspin.com/2010/05/...-nexus-one-its-like-it-never-happened-almost/
Flash the ERD79 Release, update to EFE27. Then run the Froyo update through Stock recovery. 3G works fine, radio updated (I think?) and everything is fast.
Click to expand...
Click to collapse
Yep, flashed the rooted version of FroYo, works great. Love it!!
----------------------------------------------------
Original Text:
----------------------------------------------------
Firstly, I tried to search but if this ends up simply rehashing another thread, mods please direct me to proper thread and delete this.
Now to my question. I am still running the base HBoot of my phone from the 1.56 RUU (I bought phone in December 2009). I'm rooted right now with that and using custom ROM/radio.
Now that the infamous 2.1 official RUU is out, would it be safe to up my phone to the root-included TEST RUU, RUU_Hero_C_Sprint_2.20.651.1_signed_test, and re-push flash_image or does it even really matter which hboot I'm running on (figure hboot is the only thing permanently stuck on phone from RUU)?
Or to put another way, do I gain anything from a higher-version hboot from the Test RUU other than it looking more like the official release so root isn't as obvious?
Any thoughts welcome
-----------------------------------------
This is sorta deprecated now that we have Root on the Release RUU, so repurposing the thread.
My new question: Now that i've rooted the Official Release version, can I restore my old nandroid backup without breaking my phone?
I did a nandroid backup of my fully-set-up Fresh 2.1.2 Install before I ran the Official RUU to 2.27.651.5 and now I'm wondering if it will break anything to "restore" that backup.
Again, any thoughts are welcome.
diaknia said:
Firstly, I tried to search but if this ends up simply rehashing another thread, mods please direct me to proper thread and delete this.
Now to my question. I am still running the base HBoot of my phone from the 1.56 RUU (I bought phone in December 2009). I'm rooted right now with that and using custom ROM/radio.
Now that the infamous 2.1 official RUU is out, would it be safe to up my phone to the root-included TEST RUU and re-push flash_image or does it even really matter which hboot I'm running on?
Or to put another way, do I gain anything from a higher-version hboot from the Test RUU other than it looking more like the official release so root isn't as obvious?
Click to expand...
Click to collapse
to my knowledge if your hboot changes from 1.56 to the one from the official you will lose root as of now, the test RUU still has root but its super buggy, why would you want to flash the official or the test anyways, theres roms here that blow the stock ones out the water, but once again to my knowledge you WILL lose root. And the test ruu with root has mad issues you should do a search bro as far as upgrading to the newer hboot well im not sure if it has features but the devs are still trying to break root in the new hboot.
check this out bro just in case you already flashed it http://forum.xda-developers.com/showthread.php?t=693449&highlight=hboot
I have not yet flashed the Test RUU.
From what I understand the Test RUU still has su built in, so all I need to do is re-push flash_image to get a custom recovery back on it and I'm golden from there.
I don't plan on using the stock ROM that comes with the RUU more than I have to, just curious about installing custom ROMs from that base versus the 1.56 base.
I still plan on uploading flash_image and doing the custom ROMs and Radio like now.
diaknia said:
I have not yet flashed the Test RUU.
I don't plan on using the stock ROM that comes with the RUU more than I have to, just curious about installing custom ROMs from that base versus the 1.56 base.
I still plan on uploading flash_image and doing the custom ROMs and Radio like now.
Click to expand...
Click to collapse
well from what i heard recently that base doesnt have audio issues that some people deal with on certain roms like the drivers are better, but my old hero i always had audios issues not with this refurb i dont get um anymore. but that 1.56 base is solid theres so much **** to work outta 2.1, until then im rocking darchdroid2.63 the only asop rom out there for our phones!
Im running Godspeed recovery, darchdroid2.63 and the latest 2.1 sprint radio and i cant complain
good to know
dirkydirk23 said:
well from what i heard recently that base doesnt have audio issues that some people deal with on certain roms like the drivers are better, but my old hero i always had audios issues not with this refurb i dont get um anymore. but that 1.56 base is solid theres so much **** to work outta 2.1, until then im rocking darchdroid2.63 the only asop rom out there for our phones!
Im running Godspeed recovery, darchdroid2.63 and the latest 2.1 sprint radio and i cant complain
Click to expand...
Click to collapse
I've already had audio issues installing custom ROMs based on 2.20.651.1 Test while using the 1.56 base, yet Fresh 2.1.2 based on 2.27.651.5 has yet to glitch on me for audio *crosses fingers*.
I'd still prefer to run a 2.27.651.5-based ROM like Fresh 2.1.2 even after upgrading my HBoot to the one from the 2.20.651.1 Test RUU, if I do so.
Original point of my question was if there was anything buggy in the HBoot itself moving from 1.56 to 2.20 RUU. Correct me if I'm wrong but HBoot is really the only thing that can't be easily flashed. You can flash both ROMs and Radio.
Far as AOSP, it's cool and all, but call me crazy: I actually like Sense.
diaknia said:
I've already had audio issues installing custom ROMs based on 2.20.651.1 Test while using the 1.56 base, yet Fresh 2.1.2 based on 2.27.651.5 has yet to glitch on me for audio *crosses fingers*.
I'd still prefer to run a 2.27.651.5-based ROM like Fresh 2.1.2 even after upgrading my HBoot to the one from the 2.20.651.1 Test RUU, if I do so.
Original point of my question was if there was anything buggy in the HBoot itself moving from 1.56 to 2.20 RUU. Correct me if I'm wrong but HBoot is really the only thing that can't be easily flashed. You can flash both ROMs and Radio.
Far as AOSP, it's cool and all, but call me crazy: I actually like Sense.
Click to expand...
Click to collapse
There is nothing wrong w/ the hboot. and the hboot isn't even the thing blocking root. The audio issue seems to differ from phone to phone, I have never had audio issues on my phone.
Thanks for the responses, regaw and dirky.
It looks like doesn't matter one way or another which base (rooted 1.56 or rooted 2.20) I use. I should have same functionality either way. I'm just gonna stick with 1.56. Really comes down to "if it ain't broke..."
On a side note.... i'm an eager follower of the official RUU ROOT thread on the dev sub-forum, Regaw, keep up the good work. Still feel bad for you that you've been stuck without root so long...
When you crack the thing, and I maintain hope you will, that's when I'll probly go and upgrade to the Release RUU.
diaknia said:
It looks like doesn't matter one way or another which base (rooted 1.56 or rooted 2.20) I use. I should have same functionality either way. I'm just gonna stick with 1.56. Really comes down to "if it ain't broke..."
Click to expand...
Click to collapse
Basically this.
abcdfv said:
Basically this.
Click to expand...
Click to collapse
yeah ive yet to run into it but i hear hboots are *****es to downgrade, but yeah i guess you and i both learned something dude, im rollin with your last post, if it aint broke dont fix it lol
dirkydirk23 said:
yeah ive yet to run into it but i hear hboots are *****es to downgrade, but yeah i guess you and i both learned something dude, im rollin with your last post, if it aint broke dont fix it lol
Click to expand...
Click to collapse
If you had run the test ruu and already pushed flash_image and custom recovery back to the phone then you can restore the original hboot in about 10 seconds if you want.
From recovery flash the .zip attached here and the hboot will revert to 1.41 instead of 1.47.
Cool, moot point now, though.
Now that the release version is rooted, I upgraded to the release RUU and re-rooted. Got Toast's OC recovery kernel rocking already.
Sorta off-topic, but I do have one small question:
I made a nandroid of my install of Fresh 2.1.2 before I upgraded. Would it be safe to restore that nandroid back now that i'm on the 2.27.651.5 RUU?
diaknia said:
Cool, moot point now, though.
Now that the release version is rooted, I upgraded to the release RUU and re-rooted. Got Toast's OC recovery kernel rocking already.
Sorta off-topic, but I do have one small question:
I made a nandroid of my install of Fresh 2.1.2 before I upgraded. Would it be safe to restore that nandroid back now that i'm on the 2.27.651.5 RUU?
Click to expand...
Click to collapse
I am curious about this also. Currently running fresh 2.1.1 previously from a 1.5 root and was thinking about updating to the .5 ruu and doing the root and than restoring a nandroid
OK a nice simple one,
had my dhd a few weeks now very pleased with it. Am a massive fan of cyanogenmod roms, previously had a magic 32b and his roms were the best thing to happen to the phone, so am holding out for a cyanogenmod dhd rom - fingers crossed!
So if I install OTA updates will it stop me from getting root with S-OFF in the future. Golden rule of flashing anything (apart from backing up first!!) is not to update to the latest system software. Well this has always been the case with anyhing I have flashed in the past (psp, ps3, magic 32b, ipod, iphones etc...) is that also the case with the DHD?????
DHD on T-Mobile UK.
nop, its not like "apple" devices, you can install otas from htc and hack your device, the ota include some software issue that fix (bugs and so).
btw: if you have root and recovery - you will not get any OTA, the recovery blocks it,
but you will get it from your costom rom vision.
As I thought, same deal as my old magic 32b then. Still think i'm going to sit on the fence for a while an watch what roms get developed or ported over.
I just miss a few of the mods in CM roms, silly thing like being able to enter a custom field in the add contact menu. Im sure i'll get over it. Although I believe that was a wysie mod to the phone book.
Thanks for the quick response.
Just gotta say how nice this phone is after my magic 32b, its like upgarading the ram and processor on your PC, it flies!!
An afterthought,
it seems it would be sensible to install the first few OTA updates before rooting so any stock software bugs are fixed before you loose the ability to update OTA.
Unless of course you are flashing a custom ROM which I assume the devs would include the bugfixes within their ROMS.
Why dont you try the CM rom now and if you dont want to keep it unroot the phone ?
Its brilliant by the way
I didnt realise there was a CM rom for the DHD, i couldnt see a category on his site for the DHD
But I do see it on the first page here in the dev section. Very pleased CM for the DHD and the phone has only been out a short while!
http://forum.xda-developers.com/showthread.php?t=844703
liorra3 said:
nop, its not like "apple" devices, you can install otas from htc and hack your device, the ota include some software issue that fix (bugs and so)...
Click to expand...
Click to collapse
Untrue: OTAs can and surely will fix the exploit used to root our DHD. Once rooted, never install an OTA and wait for a custom rom with the fix(es).
f.
Sent from The Galactic Empire using the Dark Side of The Force
forelli said:
Untrue: OTAs can and surely will fix the exploit used to root our DHD. Once rooted, never install an OTA and wait for a custom rom with the fix(es).
f.
Sent from The Galactic Empire using the Dark Side of The Force
Click to expand...
Click to collapse
Although if they do screw us over it is still possible to restore an older ruu image and re-root. I have archived myself a copy of the original WWE just in case.
dr.m0x said:
Although if they do screw us over it is still possible to restore an older ruu image and re-root. I have archived myself a copy of the original WWE just in case.
Click to expand...
Click to collapse
No, because they usually update the hboot, and when they do that, you're properly f#@&!d because Devs have to find a new exploit.
f.
Sent from The Galactic Empire using the Dark Side of The Force
forelli said:
No, because they usually update the hboot, and when they do that, you're properly f#@&!d because Devs have to find a new exploit.
f.
Sent from The Galactic Empire using the Dark Side of The Force
Click to expand...
Click to collapse
Couldn't you make a goldcard with sdk and a HxD hex editor??...then flash the ruu and you should be able to OTA..
Not as I see a need to do this as the Devs will always make new custom roms with the updated offical roms anyway..