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
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
Hey,
I've looked through the forum and I'm a bit puzzled how is it with the bootloader "lock" on newly purchased models as I was thinking a bit of buying A500.
I read that the bootloader only checks for checksums when booting kernel / recovery (unless set to generate them), so you can put there custom kernel (get rid of Java Android) when you root it, which I read is not a problem even with 3.2.1 .
The thing I'm puzzled about is that I read there was a BL update and some say the BL is locked since that update and others not - so if I decide to buy A500 and there will be 3.2 with the BL update on it, is it locked and requiring signed kernel image or is it still the checksum only thing?
Skrilax_CZ said:
Hey,
I've looked through the forum and I'm a bit puzzled how is it with the bootloader "lock" on newly purchased models as I was thinking a bit of buying A500.
I read that the bootloader only checks for checksums when booting kernel / recovery (unless set to generate them), so you can put there custom kernel (get rid of Java Android) when you root it, which I read is not a problem even with 3.2.1 .
The thing I'm puzzled about is that I read there was a BL update and some say the BL is locked since that update and others not - so if I decide to buy A500 and there will be 3.2 with the BL update on it, is it locked and requiring signed kernel image or is it still the checksum only thing?
Click to expand...
Click to collapse
No problem. I'll try to put it in "laymans" terms.
Manufacturers don't want you mucking with things. It causes more tech support for them, and also a bad image reputation when stupid people screw things up.
So what they do, is change bootloaders, the part that tells the tab, that the os they are loading, is 100% Acer. If it's not, it's just going to give you a silly face.
So we, here in the Acer community, try to find a way around the bootloader. And invent ways to install a operating system other than Acer.
It's an ongoing battle it seems. We find a way around it, Acer changes the rules, so we have to find another way.
The thing is, our dev's are smarter than their devs. Even HTC gave up, and just offer bootloader unlocks. Besides, they take our innovations, and incorporate them into their newer releases.
So the point is, if you buy a 500, or a 501, XDA community will give the means to unlock it. Root, so we say. And people will help you get it running right.
Here at XDA, we have many roms, from plain rooted stock roms, to cooked roms with OC kernels.
Ah, oops, placed the question incorrectly, I know how the things work around bootloaders and have designed some workarounds. I was rather asking whether new a model of A500 can run custom kernel (don't mean modifications with modules now) or not - but summarizing what you've said: every A500 can run custom kernel, right? Thanks for answering in any case.
Currently on a new A500 with root and kernel. Manufactured in December 11. whole process took an hour. Hope this helps.
Skrilax_CZ said:
Ah, oops, placed the question incorrectly, I know how the things work around bootloaders and have designed some workarounds. I was rather asking whether new a model of A500 can run custom kernel (don't mean modifications with modules now) or not - but summarizing what you've said: every A500 can run custom kernel, right? Thanks for answering in any case.
Click to expand...
Click to collapse
IIRC, only 3.2.1 locked the bootloader, so even if your a500 comes with 3.2 you're safe.
That said, even with 3.2.1 and a locked bootloader, there is a downgrade trick that allows you to go from 3.2.1 (or 3.2, or 3.1) to 3.0 and run an app called iconiaroot and acer recovery installer. Iconiaroot is like z4root, VISIONary, gingerbreak, etc and recovery installer installs CWM recovery from within android. After doing all this you can flash any rom or kernel you want.
Skrilax_CZ said:
Ah, oops, placed the question incorrectly, I know how the things work around bootloaders and have designed some workarounds. I was rather asking whether new a model of A500 can run custom kernel (don't mean modifications with modules now) or not - but summarizing what you've said: every A500 can run custom kernel, right? Thanks for answering in any case.
Click to expand...
Click to collapse
YES if your a500 has Stock android 3.2 or above.. you will have to fallow the downgrade rom flashing.Then you can flash any rom of your choice . there are several threads on this forum explaining how to do this..
Do a search for the thread by Timmy Dean.. his method i think has been called the easiest. It flashes your tablet to a rooted 3.21 stock rom thru adb . from your windows computer..
Acer has yet to plug this hole. So i would not take ANY OTA UPDATES. Im looking for ics if ever releases to plug such holes in the boot loader and stop its magic .
Happy Flashing just please understand everything before proceeding.. there are enough help i bricked my iconia threads.. Boohoo i hate to see anyone do that to such a expensive device..
Thanks. Ordered a piece
So basically I need to store UID, first x bytes in mmcblk0 (for the mmcblk0_start) from sc2k thread (http://forum.xda-developers.com/showthread.php?t=1129873) and I'm pretty much brick safe (should I screw both kernel & recovery).
Happy Flashing
That in theory will give you the resources to recover . BUT BY NO MEANS A Get of of trouble free pass..
do not flash nothing you don't trust and Fallow all instructions Carefully.. You sound well on your way to Making the best of your tablet...
Enjoy your time on xda Iconia forum. There are some awesome people on here. NO im not including myself in that .. Im just a bored thread reading chic. that repeats what i have read... nothing i know is my own work..
Happy Flashing..
erica_renee said:
Im just a bored thread reading chic. that repeats what i have read... nothing i know is my own work..
Happy Flashing..
Click to expand...
Click to collapse
Aren't we all..... Not necessarily a chic though...
Allright, all went smooth (was 3.2 preinstalled). Thanks all.
you are very welcome..
Its simple easy with just a bit of reading up front..
So I'm going to go out on a limb and say that there is no solution to root a TP that's already applied the 2.0 update?
I've tried the root methods already obtainable on here and they don't work. I'm guessing (more hoping) that someone is working on finding a solution.
Makes me sad. A co-worker updated it for me because "it said it needed to update it so I did it for you"... *sigh*
OTA2 removed the exploit unless you were already rooted and used Voodoo Rootkeeper to maintain root during the update. I haven't heard the outcome with regards to 2.5. I don't want to risk root so won't be updating unless it's safe.
2.5 is out ? which your version of tablet ?
16gb us. Was delivered last week.
Yeah, I didn't have it rooted before so yeah.
Either people like us find a way to downgrade or wait until a new exploit is found. The former seems easier but my knowledge of these things isn't very high...
Yeah, I'm not sure how to either. I'm good at following directions but when a "friend" upgrades your device for you...
As for downgrading, I don't think that'll be an option until someone finds a Lenovo rom flash utility.
byersbw said:
16gb us. Was delivered last week.
Yeah, I didn't have it rooted before so yeah.
Click to expand...
Click to collapse
2. 5 was not available to US last week. How did you get it? Supposedly it's still going through certification. 0086_US is 2.0. What version are you?
Oh hell.... I've been reading too many posts on the Lenovo forums. My apologies, I am running OTA 2.0 NOT 2.5. I will correct my first post and title.
I'm running ThinkPadTablet_A310_02_0039_0086_US.
Okay. Thanks. No worries, but was scratching my head, looking puzzled.
Haha! I can understand. I have that look a lot sadly. I appreciate you telling me as I had no clue as to what exactly I was saying.
Now, if anyone knows someone on the inside at Lenovo that could get the flash utility...
LOL If only.
And now we wait. Did NOT expect CM9 to come out so fast and be working so didn't care much for root otherwise. Oh well, that was my fault and I knew I'd lose root for the time being. Now I wait patiently, since the primary work of the developers now is making CM9 to work properly so w/e.
Why isn't there a way to downgrade the rom to 075? The tab has a recovery boot. If it could be downgraded, it could then be rooted , then updated.
No way to downgrade, unless you know something the rest of us are unaware of. There's a bunch of folks that either can't root at all, or took OTA2 before getting root/without preserving root. We've been told that there's nothing to be done for the time being.
I don't know how to do it, but I know that's how other tabs got around the problem. I only say it in case someone does.
AFAIK, the problem is the recovery's signature check.. if it recognizes that the update.zip to flash is older than the build actually installed, it won't install the new ROM.
Thanks. Noob enough that I couldn't explain it, just knew it doesn't work.
YassinTP said:
AFAIK, the problem is the recovery's signature check.. if it recognizes that the update.zip to flash is older than the build actually installed, it won't install the new ROM.
Click to expand...
Click to collapse
I wonder what it takes to defeat the check? There must be an update script that performs that check. Editing elements of the update script has been the key to other "can't be done" situations.
http://forum.xda-developers.com/showthread.php?p=22918839[WIP][4.0.3]ICS CM9 ThinkPad Tablet PORT
I'm going to keep putting forth suggestions instead of claiming something can't be done. Afterall, the point of this entire forum is to work togther to overcome obstacles.
While I don't know a lot about these things, if it could be done, it would have been. This forum is overflowing with posts from owners of all kinds devices asking how to downgrade their respective device so they can take root. It's not an uncommon request, and one that I have researched for another device, only to find the same answer. Hey if you find out how to do it, you'll make a fortune.
Two other tablets, the Flyer and the View downgrade to gingerbread, then unlock bootloader, then root, then update to honeycomb, then custom roms are applied. They got the idea from another tab, the Iconia, who got it from the Transformer . . .
I'm just trying to push good and bad ideas to someone with the skills. It's about not taking 'no' as an answer.
Here's the thread for Flyer/View:
http://forum.xda-developers.com/showthread.php?p=21028879[Procedure]No HTC unlock downgrade HC-GB for official OTA
I'm brand new to the Glacier, although I've rooted many other phones.
I looked at the guides I could find here, but I was wondering if there is an easier way to S-off + CWM than a bunch of ADB to downgrade to 2.2.1 etc... seems overly complicated atm, isn't there a way to root on GB stock ROM or an easier way in general?
I really have searched, but there is too much info and I feel like some of it may be old, like there's an easier way to root now?
Just wanna flash some custom ROMs basically.
exploit
downgrade
root/unlock hboot/install recov
i duno, it doesnt get much easier than that. its honestly very simple it just takes some time to do.
if you have the stock mytouch 4g you dont need to downgrade as far as i know..
just follow the steps, i just rooted a second one of these with stock 2.3.. took a bit longer but it worked out, the guides here are amazing
ok well I was basically wondering if there was an updated way to do it, but I guess I'll just do the downgrade and go from there.
Thx for the heads up.
orangekid said:
ok well I was basically wondering if there was an updated way to do it, but I guess I'll just do the downgrade and go from there.
Thx for the heads up.
Click to expand...
Click to collapse
Hate to be the bearer of bad new, but as of currently the only way to root the 2.3.x update is to downgrade to 2.2.x then root.
There are two different eMMC chips that you could have in your device. You might want to look at my Noob Thread. I know with a post count of over 3k your not a noob but it has all the links that you'll be interested in.
neidlinger said:
Hate to be the bearer of bad new, but as of currently the only way to root the 2.3.x update is to downgrade to 2.2.x then root.
There are two different eMMC chips that you could have in your device. You might want to look at my Noob Thread. I know with a post count of over 3k your not a noob but it has all the links that you'll be interested in.
Click to expand...
Click to collapse
yeah that part I learned about and was glad to see I have the "good" one
orangekid said:
yeah that part I learned about and was glad to see I have the "good" one
Click to expand...
Click to collapse
one of mine has the bad chip... well see how long it lasts..
once i root and flash, does it still affect the chip or is it only when flashing?
(sorry for thread hijack )
grimey01 said:
one of mine has the bad chip... well see how long it lasts..
once i root and flash, does it still affect the chip or is it only when flashing?
(sorry for thread hijack )
Click to expand...
Click to collapse
np I'm actually interested in the answer to this even though I have the good chip.
arg, keep getting stuck on INFOsignaturechecking when I try to fastboot flash the froyo stock ROM