Related
So, I am new to this site and to the android community. I apologize if I sound stupid to any of you but if you aren't going to help I'd appreciate it if you just ignored me.
Anyway, I got my Atrix a couple days ago on AT&T and started learning about rooting and such. Everything on it is still stock, last night I upgraded to Gingerbread from Froyo and I'd just like to know if there's any specific rooting program, method I can use right now for 4.5.91 Also, when I upgraded I lost my music player widget, is there I can get it back without going back to Froyo?
Follow the procedure in the second link in my signature. Since you had root before you updated go into settings manage applications clear app data for superuser.
Sent from my MB860 using XDA App
phobos512 said:
Follow the procedure in the second link in my signature. Since you had root before you updated go into settings manage applications clear app data for superuser.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
will there be any severe consequences if I screw up?
Use gingerbreak.
Sent from my MB860 using XDA App
TheToiletSpaula said:
Use gingerbreak.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I've read that gingerbreak doesn't work with this version. I'll look it up though.
phobos512 said:
follow the procedure in the second link in my signature. Since you had root before you updated go into settings manage applications clear app data for superuser.
Sent from my mb860 using xda app
Click to expand...
Click to collapse
^^^^^ only way to root gb and probably the best way if there are other methods
savier420 said:
^^^^^ only way to root gb and probably the best way if there are other methods
Click to expand...
Click to collapse
cool, just one question. Am I supposed to have the device connected to my computer the whole time? and if not between which steps should I connect/ disconnect it? also, when I put the root.img in the C: folder, do I put the zip file or just the .img inside of it?
phobos512 said:
Follow the procedure in the second link in my signature. Since you had root before you updated go into settings manage applications clear app data for superuser.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
If you are just trying to "root" your phone only, YES, this is the best method.
Thanks for posting this and providing the link in your signature. I was crapping myself reading the other post about how the new updates bricks your phone but no one said if you are just looking to root your stock OTA's you'll be fine. So, thanks again. They should sticky this under "If you are just running stock and want to root without unlocked BL/pudding use this"
PSY0NIC
PSY0NIC said:
If you are just trying to "root" your phone only, YES, this is the best method.
Thanks for posting this and providing the link in your signature. I was crapping myself reading the other post about how the new updates bricks your phone but no one said if you are just looking to root your stock OTA's you'll be fine. So, thanks again. They should sticky this under "If you are just running stock and want to root without unlocked BL/pudding use this"
PSY0NIC
Click to expand...
Click to collapse
Since this is the 1st time I've seen some one say it this way....
If you are just trying to "root" your phone only, YES, this is the best method.
Brand new phone, all stock... just want root.... use gingerbreak?
Sent from my MB860 using XDA Premium App
Hi all,
Renaissance613, can you post if you had success and if you ran into any problems? I have the same setup as you (2.3.4/4.5.91) and I'm nervous about rooting so soon after the update (I just installed it).
Also, I'm wondering if I will have to undo this root when another automatic update gets pushed down, or if it will just unroot like my gingerbreak root did. I don't have/intend to use any ROMs. I like stock phone with phone-pulled updates and rooted.
In any case, thanks for the link phobos512 - and thanks to this community of developers and users. You guys are awesome.
Hambone~
hambone123 said:
Hi all,
Renaissance613, can you post if you had success and if you ran into any problems? I have the same setup as you (2.3.4/4.5.91) and I'm nervous about rooting so soon after the update (I just installed it).
Also, I'm wondering if I will have to undo this root when another automatic update gets pushed down, or if it will just unroot like my gingerbreak root did. I don't have/intend to use any ROMs. I like stock phone with phone-pulled updates and rooted.
In any case, thanks for the link phobos512 - and thanks to this community of developers and users. You guys are awesome.
Hambone~
Click to expand...
Click to collapse
I'm about to try it but I'm still confused about a few things like when exactly to connect or disconnect my phone and what to do after I've entered all the commands on my computer, will it install by itself? This is my first time rooting a phone, and my first time even owning an android so I want to make sure I know exactly what I'm doing
I hear you man, it's nerve wracking to worry that you're going to brick your phone. I did the gingerbreak on the last release and it worked perfectly. I'm sure this method will work fine as well, as you said I just want to be sure I'm doing the right thing for my goal: stock phone/downloaded updates/rooted. Best of luck, and thanks to anyone who gives us noobs some more reassurance.
this is by far the best method to root on gingerbread, but i dont see any reason to root but to only flash custom roms, i only needed root pre-GB to allow non market apps, and the new GB OTA UPDATE allows non market apps, so im pretty happy with wat i got, before i updated to the OTA GB i had BL unlocked and rooted, just flashed back to 1.2.6 to be rid of root and unlocked BL, then just went throught the OTA updates to get to GB and im loving it, dont really care to flash any other custom roms, BUT BEWARE DOING THE OTA TO GB AND UNLOCKING THE BL THEN TRYIN TO FLASH BACK TO A STOCK ROM WILL HARD BRICK SO DO YOUR RESEARCH so if u dont want a hard bricked phone dont do the ota stick to custom roms and ignore all OTA'S
so I got through the fastboot reboot command, phone booted back up automatically, then put the phone into debug. Then typed in the adb shell code and said the specified path could not be found.
Now I was still in the command prompt that said the c:/root
What did I do wrong?
So, adb says it is a bad path?? Do this instead..it is easier and it works -- I did it this way last night!
After "moto-fastboot reboot", once your phone has completely rebooted, go to the Android Market and download and install "Terminal Emulator." Once it is instslled and you have opened it, enter the EXACT SAME commands that you were going to type into the Adb Shell..once again, type in the commands VERBATIM. After the last command, there should be a message saying (in terminal emulator) that it was successful! Congrats, you have achieved root access on the AT&T issued stock Gingerbread 2.3.4 build! I hope it works for you!
~Eric
savier420 said:
this is by far the best method to root on gingerbread, but i dont see any reason to root but to only flash custom roms, i only needed root pre-GB to allow non market apps, and the new GB OTA UPDATE allows non market apps, so im pretty happy with wat i got.
Click to expand...
Click to collapse
I'm very vanilla. I root pretty much entirely for free wireless tethering and being able to delete bloatware.
Hello everyone, I am still a little confused between what will or what will not brick my phone. I appreciate your responses.
I am still in froyo 2.2.2 (firmware 1.8.3), rooted using GladRoot method (rooted in previous firmware, then upgraded to 1.83 and used the AfterUpdate.bat.
I am afraid to do the updrade to GB because after reading a looot of threads here on this I am completely confused on what will brick my atrix and what not. If I upgrade to GB OTA, will that brick my phone? if it doesn't brick it, what does? if I upgrade to GB OTA will I able to root it? what method should I use?
thanks a lot
aroca1978 said:
Hello everyone, I am still a little confused between what will or what will not brick my phone. I appreciate your responses.
I am still in froyo 2.2.2 (firmware 1.8.3), rooted using GladRoot method (rooted in previous firmware, then upgraded to 1.83 and used the AfterUpdate.bat.
I am afraid to do the updrade to GB because after reading a looot of threads here on this I am completely confused on what will brick my atrix and what not. If I upgrade to GB OTA, will that brick my phone? if it doesn't brick it, what does? if I upgrade to GB OTA will I able to root it? what method should I use?
thanks a lot
Click to expand...
Click to collapse
Updating to GB won't brick your phone. After updating to GB you can't down grade to older OS (like the one your on right now) that would brick your phone. So as long as you don't plan on going back to a past OS version (and I don't know why anyone would) you'll have no problems at all. As for Rooting >follow this link< and follow the instructions there after you update to GB. It works perfectly, you don't have to unlock your BL or anything else like that to just have Root on GB. Hope this helps.
Thanks!!! That was the response I was looking for
Now, what method should I use if I were planning to unlock the bootloader?
Also, if something goes wrong and I need to reinstall the upgrade (or better, flash with GB again with a spf file) will that not brick by atrix either?
For Questions about BL Unlocking
aroca1978 said:
Thanks!!! That was the response I was looking for
Now, what method should I use if I were planning to unlock the bootloader?
Also, if something goes wrong and I need to reinstall the upgrade (or better, flash with GB again with a spf file) will that not brick by atrix either?
Click to expand...
Click to collapse
Click on the link below, that thread will give you the answers and files your looking for.
> Click Here <
Help.
I have a rooted Thunderbolt and I have been able to reject the update from Verizon until this afternoon when my phone started to update on its own. The update didn't go through and I got an error icon. Now my phone just goes through the same cycle of turning it self off and trying to update and crashing.
I am able to get to the Clockwork Mod recovery page but the only option that works is the 'reboot system now', which starts the phone and the whole cycle of trying to update is started.
Does anyone have an idea of how to get my phone working again?
Thanks in advance.
Mike
I'm really sorry to hear that happened, I'm not sure what you can do. Hopefully someone will be able to help you out. But at least I can tell you that you are not alone! I wasn't rooted, but my phone did autoupdate on its own at about 2:30pm today.
I posted about it here: http://forum.xda-developers.com/showthread.php?t=1234844
Pull your SDcard, wipe the pg05img.zip file, and try again. You might have to reflash clockwork.
This is the problem with running rooted stock ROMs. I know flashing a new ROM isn't what a noob wants to do, but it will avoid these very confusing headaches.
whats if you rooted using revolutionary? As far as i know there wont be that pg05img.zip file to delete.
Would you always be in danger is this if you are rooted and stay stock?
Why would someone want to root their phone and stay stock ??????
Sent from my Verizon LTE 4G Thunderbolt
loonatik78 said:
This is the problem with running rooted stock ROMs
Click to expand...
Click to collapse
Nope. One only has to keep up with the current releases, rooted versions of which come out within days of official release.
Are you sure it is the Verizon update?
I have the same behavior on my T-bolt since about 10 pst today. However, just before the phone shuts down to reboot, I see a note about a new version of Clockworkmod Recovery 4.0.1.5.
So I have been working on the assumption that it is CWM Recovery that is doing an automatic update.
I also am running rooted stock, and have not updated to latest release.
OK, it isn't the update to CWM Recovery that is the problem; it is the Verizon OTA update, which they have figured out how to force on us. I fixed my phone using the solution given by Mike later in this thread.
jbh00jh said:
Why would someone want to root their phone and stay stock ??????
Sent from my Verizon LTE 4G Thunderbolt
Click to expand...
Click to collapse
Debloating. Stock is pretty damn nice without all the extra crap.
*Madmoose* said:
Debloating. Stock is pretty damn nice without all the extra crap.
Click to expand...
Click to collapse
This, plus "root while you can" - there's no guarantee that rooting will be possible with each subsequent (unrooted) release, but you can root now and stay rooted to keep your options open. Also, getting full backups of everything is easier when rooted.
Did the fix work?
Mike, did you try what loonatik suggested? Did it work? Waiting breathlessly...
Unless I am misunderstanding the problem wiping cache from Clockwork recovery should clear out the update and it will quit trying to install it. For the future if you go to settings in the about phone or software update section (dont remeber which) there is an option to de-select scheduled update checks.
Sent from my HTC Thunderbolt
Wait.. what? Most ROMs I've seen are debloated.. At the very least they have VZW crap removed
Thanks guys for all your help and interest. I tried the solution offered by lunatic but it did not work. Thanks any way I was still looping through continuous on and off cycle. I did however did find a solution on another site. Here is the solution from Sele.
http://www.thunderboltforums.com/forum/htc-thundebolt-hacking-guides/2257-rs-guide-how-get-rid-ota-forced-reboots-rooted-phone.html
It was easier fix than I thought it would be. Step #1 worked.
I also did this to stop the update from happening again.
"If you are rooted use root explorer or super manager and set system to R/W. Then navigate to /system/etc/security. Find the file named otacerts.zip and rename it to otacerts.zip.bak and reboot. Should fix you up."
I'm sorry I can't remember who offered this solution to give credit to. I haven't had any updates yet but only time will tell.
Good Luck with your phone.
JBO1018 said:
Unless I am misunderstanding the problem wiping cache from Clockwork recovery should clear out the update and it will quit trying to install it. For the future if you go to settings in the about phone or software update section (dont remeber which) there is an option to de-select scheduled update checks.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
Yes you are correct wiping the cache fixed the problem.
mjkusa said:
Thanks guys for all your help and interest. I tried the solution offered by lunatic but it did not work. Thanks any way I was still looping through continuous on and off cycle. I did however did find a solution on another site. Here is the solution from Sele.
http://www.thunderboltforums.com/forum/htc-thundebolt-hacking-guides/2257-rs-guide-how-get-rid-ota-forced-reboots-rooted-phone.html
It was easier fix than I thought it would be. Step #1 worked.
I also did this to stop the update from happening again.
"If you are rooted use root explorer or super manager and set system to R/W. Then navigate to /system/etc/security. Find the file named otacerts.zip and rename it to otacerts.zip.bak and reboot. Should fix you up."
I'm sorry I can't remember who offered this solution to give credit to. I haven't had any updates yet but only time will tell.
Good Luck with your phone.
Click to expand...
Click to collapse
Definitely a handy resource.. Every time a new OTA comes out, this is a very frequently asked question.
I suppose you could always use an RUU too
mike.s said:
Nope. One only has to keep up with the current releases, rooted versions of which come out within days of official release.
Click to expand...
Click to collapse
Based on how many of these threads I see, that clearly isn't what's being done.
This has been brought up in:
http://forum.xda-developers.com/showthread.php?t=1486926
I figured it would be time to start a new thread on it to discuss work-arounds.
Is it possible to revert to .11? I assume we would need to re-root.
EDIT* Since I didn't mention it, I am unable to OTA on 11.1. I live in Colorado which people from the other thread have stated they are able to update from.
redpoint13 said:
This has been brought up in:
http://forum.xda-developers.com/showthread.php?t=1486926
I figured it would be time to start a new thread on it to discuss work-arounds.
Is it possible to revert to .11? I assume we would need to re-root.
EDIT* Since I didn't mention it, I am unable to OTA on 11.1. I live in Colorado which people from the other thread have stated they are able to update from.
Click to expand...
Click to collapse
No, you can't go back until we have working recoveries and proper backups can be made. Only choice is to wait for manual version of .13, install it (should be up in 1-3 days), and likely after that the Kernel numbers will be in the right line for OTA's again
*EDIT: I too am on 11.1, just have to wait either for ASUS to update the firmware downloads on their website or for one of our fellow xda'ers to capture the update and upload it for us
Don't you love those Asus emails telling you to flash things without any indication of consequences? That's why I didn't flash the one I was pmed.
yep this kinda blows. went 11.1 because I considered rooting, but didnt.
Just didnt see any benefit for me at this point since there were no ROMS, boot ubnlock etc.
Oh well, hopefully it will be up on Asus soon.
Also hopefully when we do manually update to .13 any future OTA's will be available to us?
Seems to be a firmware update today just got it
Commodore 64
buxtahuda said:
No, you can't go back until we have working recoveries and proper backups can be made. Only choice is to wait for manual version of .13, install it (should be up in 1-3 days), and likely after that the Kernel numbers will be in the right line for OTA's again
*EDIT: I too am on 11.1, just have to wait either for ASUS to update the firmware downloads on their website or for one of our fellow xda'ers to capture the update and upload it for us
Click to expand...
Click to collapse
So it sounds like we are guaranteed to lose root then?
GreginNH said:
yep this kinda blows. went 11.1 because I considered rooting, but didnt.
Just didnt see any benefit for me at this point since there were no ROMS, boot ubnlock etc.
Oh well, hopefully it will be up on Asus soon.
Also hopefully when we do manually update to .13 any future OTA's will be available to us?
Click to expand...
Click to collapse
The biggest thing for rooting to me was being able to install/use an ad-block program.
redpoint13 said:
So it sounds like we are guaranteed to lose root then?
Click to expand...
Click to collapse
Yeah but should be no issue for those who made sure to use voodoo OTA rootkeeeper. The update breaks root but I easily restored it. VOODOO OTA ROOTKEEPER IS A MUST HAVE NOW!
Been working great for me last few updates. Saves me Hassell of having to worry about manually rooting sgain
Does it not work downloading and flashing 9.4.2.11 from asus' site and aquiring the .13 OTA that way?
redpoint13 said:
So it sounds like we are guaranteed to lose root then?
Click to expand...
Click to collapse
Absolutely!
I don't know how OTA's work, but it seems that the 11.1 just isn't in their timeline and so the servers aren't pushing to those devices. If ASUS could rectify this and somehow make it available, your OTA Rootkeeper will work.
Most likely, will have to manually update to .13 and then re-root for (third for me) second time. Don't worry, Viper and everyone will update quickly I'm sure.
---------- Post added at 11:17 AM ---------- Previous post was at 11:15 AM ----------
demandarin said:
Yeah but should be no issue for those who made sure to use voodoo OTA rootkeeeper. The update breaks root but I easily restored it. VOODOO OTA ROOTKEEPER IS A MUST HAVE NOW!
Been working great for me last few updates. Saves me Hassell of having to worry about manually rooting sgain
Click to expand...
Click to collapse
No, 'darin. It's OTA Rootkeeper. Not just Rootkeeper.
Manual updates wipe out your /system/ and so your subackup folder and any others relating to Rootkeeper's backup get removed.
*EDIT: Also, sorry, didn't meant to sound like a d'bag lol just trying to make sure some poor soul doesn't do a manual update thinking rootkeeper will work for them
buxtahuda said:
Absolutely!
I don't know how OTA's work, but it seems that the 11.1 just isn't in their timeline and so the servers aren't pushing to those devices. If ASUS could rectify this and somehow make it available, your OTA Rootkeeper will work.
Most likely, will have to manually update to .13 and then re-root for (third for me) second time. Don't worry, Viper and everyone will update quickly I'm sure.
---------- Post added at 11:17 AM ---------- Previous post was at 11:15 AM ----------
No, 'darin. It's OTA Rootkeeper. Not just Rootkeeper.
Manual updates wipe out your /system/ and so your subackup folder and any others relating to Rootkeeper's backup get removed.
Click to expand...
Click to collapse
Good point..lmfao wasn't really thinkn of that. Exit stage right. Lol
demandarin said:
Yeah but should be no issue for those who made sure to use voodoo OTA rootkeeeper. The update breaks root but I easily restored it. VOODOO OTA ROOTKEEPER IS A MUST HAVE NOW!
Been working great for me last few updates. Saves me Hassell of having to worry about manually rooting sgain
Click to expand...
Click to collapse
AFAIK when you manually install "OTA" root keeper does not work, and seems like others are confirming this.
I just hope someone is able to quickly find another root exploit as fast as they did for .11.
Hopefully they'll rectify this in the next couple of days, don't want to be without root again .
On a different note, did anyone notice the screen would take longer to come on from standby after the 11.1 update? Mine takes about a second longer than I THINK it did before updating, but I'm not sure.
I noticed that as well. 1st few times I hit it twice due to the delay which would end up turning it on and then back to standby/sleep
Moothead2 said:
Hopefully they'll rectify this in the next couple of days, don't want to be without root again .
On a different note, did anyone notice the screen would take longer to come on from standby after the 11.1 update? Mine takes about a second longer than I THINK it did before updating, but I'm not sure.
Click to expand...
Click to collapse
Yes, also noticed it. We'll see if the .13 goes back to the quicker.
Duh!
Just tried something on my 11.1 that I manually updated. If you already have root, use a build.prop editor to change:
ro.build.display.id to IML74K.US_epad-9.4.2.11-20120117
ro.build.version.incremental to US_epad-9.4.2.11-20120117
Save, then reboot. Once it boots up, don't unlock the device. Turn the screen off until it connects to the network, then unlock. It may hot-reboot a couple of times, but just keep trying.
Once you've got it up, go check for a firmware update. You should be able to get it.
isantop said:
Just tried something on my 11.1 that I manually updated. If you already have root, use a build.prop editor to change:
ro.build.display.id to IML74K.US_epad-9.4.2.11-20120117
ro.build.version.incremental to US_epad-9.4.2.11-20120117
Save, then reboot. Once it boots up, don't unlock the device. Turn the screen off until it connects to the network, then unlock. It may hot-reboot a couple of times, but just keep trying.
Once you've got it up, go check for a firmware update. You should be able to get it.
Click to expand...
Click to collapse
What are the risks of this? I want to do this myself but I'm worried.
isantop said:
Just tried something on my 11.1 that I manually updated. If you already have root, use a build.prop editor to change:
ro.build.display.id to IML74K.US_epad-9.4.2.11-20120117
ro.build.version.incremental to US_epad-9.4.2.11-20120117
Save, then reboot. Once it boots up, don't unlock the device. Turn the screen off until it connects to the network, then unlock. It may hot-reboot a couple of times, but just keep trying.
Once you've got it up, go check for a firmware update. You should be able to get it.
Click to expand...
Click to collapse
Trying now.
*RETARDED found both
isantop said:
Just tried something on my 11.1 that I manually updated. If you already have root, use a build.prop editor to change:
ro.build.display.id to IML74K.US_epad-9.4.2.11-20120117
ro.build.version.incremental to US_epad-9.4.2.11-20120117
Save, then reboot. Once it boots up, don't unlock the device. Turn the screen off until it connects to the network, then unlock. It may hot-reboot a couple of times, but just keep trying.
Once you've got it up, go check for a firmware update. You should be able to get it.
Click to expand...
Click to collapse
Even if this seems to work, I would be very worried about messing up the system. The OTAs are basically a patch file, and they only contain the changed bits of system files, not the whole files. (It's using bsdiff, if anyone cares.)
What this means is, if it's patching the wrong file because you lied about your version, it will very likely mess up your system - maybe even make it unbootable until you fix it with a full update.
Now, it's possible this update doesn't touch any files which changed between .11 and. 11.1, so it would be safe. But I wouldn't assume that.
buxtahuda said:
Trying now.
Click to expand...
Click to collapse
Any news? I.e. does it work or not?
I have a Transformer Prime with an Unknown Serial Number. My tablet can NOT be pushed OTA Updates by ASUS. Do NOT suggest going to ASUS's website and downloading their update file, you can NOT keep Root using those files. OTA RootKeeper ONLY Works on OTA Updates PUSHED by ASUS to your tablet.
Do NOT suggest going to ASUS's website and downloading their update file. Do NOT suggest any blob file that has been linked to on these forums, UNLESS it is from someone who has actually COPIED the OTA Update from ASUS AS IT WAS BEING PUSHED to their tablet. These blob files are NOT OTA Updates.
Okay, so if you have an unknown serial on your Transformer or Transformer Prime you can't get OTA Updates. I am one of these people and it sucks because I actually like 9.4.2.21. I want root.
Now my question is, is it possible for someone with a TF101/TF201 to use some ADB or some other software to intercept the package that ASUS is pushing to the tablet and make it available to others?
I would try to figure out how to do it myself, but as I mentioned earlier. I don't have a tablet with a serial number, it shows unknown. So no OTA Updates for me.
slayvus said:
Okay, so if you have an unknown serial on your Transformer or Transformer Prime you can't get OTA Updates. I am one of these people and it sucks because I actually like 9.4.2.21.
Now my question is, is it possible for someone with a TF101/TF201 to use some ADB or some other software to intercept the package that ASUS is pushing to the tablet and make it available to others?
I would try to figure out how to do it myself, but as I mentioned earlier. I don't have a tablet with a serial number, it shows unknown. So no OTA Updates for me.
Click to expand...
Click to collapse
You can manually update it using wolf849 method, which is really used to downgrade but im more then certain it would work to manually upgrade.
Ill go step by step.
1. If you want root, and are on 9.4.2.15 now, root it now! then backup root with OTA ROOTKEEPER
2.Download latest .21 FW here http://support.asus.com/Download.aspx?SLanguage=en&p=20&s=16&m=Eee+Pad+Transformer+Prime+TF201&os=32 you likely want US build, not WW (check in settings under about this tablet)
3. Download my modded ViperMOD tool from here http://forum.xda-developers.com/showpost.php?p=25508554&postcount=52 this allows for one click downgrade.
4. Extract the .21 fw you download and find the file named "blob" and put blob on the root of you primes INTERNAL MEMORY
5. Make sure all prime drivers are installed (should install by themselves , mine did) then open my modded viperMOD (thanks viperboy) and connect transformer prime. Select option 1 in modded viperMOD tool to downgrade tablet (in your case upgrade, it just manually apply's the blob file (firmware) )
6. Should reboot to .21 then restore root with OTA Rootkeeper if wanted
Hope it works
You can't manually update or you'll lose root. Unless you have tested this yourself I'll stick with where I am. I was on 9.4.2.15, manually upgraded to .21 as I have Unknown Serial problems, LOST ROOT. Currently downgraded to 9.4.2.14.
Aka, downgrade to 9.4.2.XX. Root. Protect Root, Use the tool to upgrade to .21. Restore Root. If you can show me video evidence of this, I will do it. Otherwise, it would be a waste of my time as I would have to downgrade AGAIN and stay where I am.
slayvus said:
You can't manually update or you'll lose root. Unless you have tested this yourself I'll stick with where I am. I was on 9.4.2.15, manually upgraded to .21 as I have Unknown Serial problems, LOST ROOT. Currently downgraded to 9.4.2.14.
Aka, downgrade to 9.4.2.XX. Root. Protect Root, Use the tool to upgrade to .21. Restore Root. If you can show me video evidence of this, I will do it. Otherwise, it would be a waste of my time as I would have to downgrade AGAIN and stay where I am.
Click to expand...
Click to collapse
I was on .21 downgraded to .15, then rooted, then installed OTA rootkeeper to backup root, updated to .21 OTA then restored root with OTA rootkeeper, and im now on .21 rooted with out a unlocked prime. This has also been stated by many others.
The Blob files are NOT the OTAs as far as I can tell from what I have read.
I can NOT receive OTA Updates from ASUS while connected to the internet on my Tablet. I have an UNKNWON SERIAL NUMBER on my TF201.
An Unknown Serial Number prohibits me from being pushed OTAs by ASUS.
slayvus, im with you, im gonna get my prime replaced or rma'd on thursday if i cant find exactly what your looking for!.
slayvus said:
The Blob files are NOT the OTAs as far as I can tell from what I have read.
I can NOT receive OTA Updates from ASUS while connected to the internet on my Tablet. I have an UNKNWON SERIAL NUMBER on my TF201.
An Unknown Serial Number prohibits me from being pushed OTAs by ASUS.
Click to expand...
Click to collapse
doing the manual update is like doing the OTA updates
you keep all your information on your prime hence you can just use the root keeper to restore root
of course we're just trying to help you but if you refuse to listen to us and want us to spend time to prove to you that something works when you can always try your self, then never mind just stay on your firmware that you're on @[email protected];
This is getting tiresome of repeating this. So I let you hear it from someone who MADE Primetime, -viperboy-.
http://forum.xda-developers.com/showpost.php?p=25495366&postcount=1634
-viperboy- said:
Assdikes said:
How come I can't root or how come vipermod is not getting the job done anymore? Also I don't really know how to make real use of the OTA root keeper, because everytime I updated I made a SU backup, and then I think this is where I mess up, Then I would install the update manually from my sd card and everything is out of whack the root is messed up in a half root state sometimes, and my apps are gone, and blah blah blah...... someone help!?!?!?!?!?!?!?!?
Click to expand...
Click to collapse
Dear God, can you read?! DIRECTLY from the OP:
THIS WILL NOT ROOT .21 AT THIS TIME!!
Click to expand...
Click to collapse
There is no root method for .21, only a downgrade procedure. The reason why OTA Root Keeper didn't work is because...
maatsby said:
...it's called "OTA rootkeeper", not "manual update rootkeeper".
Click to expand...
Click to collapse
...when you update it from the sdcard, it's the full install, not the OTA that only makes certain changes. You are wiping out the OS and your su-backup.
Click to expand...
Click to collapse
Again, lets go over this ONE more time since people can not seem to read and think EVERYONE on the internet is wrong.
THE BLOB FILES ARE NOT OTA UPDATES! THEY ARE MANUAL UPDATES AND YOU CAN NOT KEEP ROOT IF YOU USE THEM!
If someone can show a know developer saying different, THAN I will believe you. Until than, I will go with the assumption that, again, BLOB files are manual updates. I do NOT want to waste time to have to do everything over again on my Prime and risk bricking it AGAIN. I already risked it once by downgrading.
bimbobo said:
It worked finally, but I wasted my time.
I installed WW15, rooted it, save the root with OTA RK, reinstalled 21WW but OTA RK did not restore the saved root. Either I cannot OTA RK correctly, or you cannot root 21 at all. I do not get that somebody reported they could restore 21 root, maybe they are unlocked.
I need to decide to stay with 15 or rest in peace with 21 not rooted.
Click to expand...
Click to collapse
bimbobo said:
I installed using the guide in the dev forum, sd card and blob.
Then I do not know.
I just clicked on "backup root", I have no idea where it's installed.
But you can eventually explain how to use it correctly.
Click to expand...
Click to collapse
b.huss2 said:
No, I'm asking how you went from 15 to 21. Did you let it update over the air or did you manually update via an SDcard update? Just wondering because Root Keeper only works for OTA updates from what I understand. For example, I was on version 15, rooted with this tool, installed Root Keeper, backed up root, and when the update came it installed automatically, and I just had to go back into Root Keeper and restore root.
EDIT: just noticed this
I think this is your problem. It's an OTA Root Keeper. You did not update OTA
Click to expand...
Click to collapse
Now PLEASE, stop suggesting that I install .21 using a BLOB file off my SDCard. It's making me feel bad having to prove you wrong. All I want to know is if it is possible to intercept ASUS' OTA Updates so that people like ME can make use of them.
Could be a way
slayvus,
This guy managed to intercept this us one, now it would be nice if they could do it for my ww version.
http://forum.xda-developers.com/showthread.php?t=1437274
im downloading this old firmware to comare it to the manual blob to see if its just a case of putting the blob in the cache folder :S
we would just need someone with a non .21 prime to download the ota for us
It looks promising, but it doesn't seem like anyone has contributed to that method in over a month.
without trying to get your hopes up im returning mine tomorrow if i dont find a solution tonight i did find this http://forum.xda-developers.com/showthread.php?p=22928122
a direct link to asus ota update for 8.6.5.21 -> 9.2.1.11 US
im going to check out whats in this zip, and see if i can find an ota link for ww, if i find one for .21 its worth you trying, you can allways downgrade again.
i went from .21 to .11 to .21 to 8.8.3.33 now im back at .15, lol
You can download FOTAKILL.apk and install it in /system/data and it will no longer OTA.
Did it for the Xoom on 4.0.3 Team EOS 1.0. Works perfect. Will work on the Lemon TF201 as well.
slayvus said:
Okay, so if you have an unknown serial on your Transformer or Transformer Prime you can't get OTA Updates. I am one of these people and it sucks because I actually like 9.4.2.21.
Now my question is, is it possible for someone with a TF101/TF201 to use some ADB or some other software to intercept the package that ASUS is pushing to the tablet and make it available to others?
I would try to figure out how to do it myself, but as I mentioned earlier. I don't have a tablet with a serial number, it shows unknown. So no OTA Updates for me.
Click to expand...
Click to collapse
You can go to Asus.com and download the .21 updated zip file. If you unzip it you will find the blob file there. You will have to manually update but you will lose root. OTA root keeper wont work for this method.
If you want to intercept, accept the OTA download but dont install it. Go to your cache folder (I forget the sub folder maybe someone can chime in) and there you will find the dlpkxxxxx file. I assume if you copy that file into another Prime in the same directory that the tab will assume you have just downloaded an update and will install it as if it were OTA. Then you may be able to use OTA rootkeeper to restore root afterwards. I haven't tried this myself so just a theory.
Sent from my Transformer Prime TF201 using Tapatalk 2
slayvus
im going to get mine rma'd or replaced this afternoon,
when i get a working one back ill get a copy of the OTA from my cache folder, i feel this may be a way for unknown serial number units to get .21 with root!
i may be getting mine fixed but i will still strive to get a fix for this situation.
Believe me ive upgraded and downgraded to and from .21 about 10 times sofar so its still worth trying.
Again, the updates from ASUS on their website, which are the blob files people are passing around for things like downgrades and such ARE NOT THE SAME THING AS AN OTA UPDATE.
An OTA Update is smaller than the blob files by a LOT. The OTAs are like less than 100 MB for the incremental updates. The updates on ASUS's website are over 300MB.
calm down, im sorry if i didnt say it right, im only human, i am going to get the ota update that downloads to the cache folder which as you say is smaller than the asus blob, i fully understand this, i spent all last night looking for the asus OTA 9.4.2.21 update, the best i could find is one to update to 9.4.2.11.
I repeat, I do not mean the one from asus.com, i am refering to the ones the units automaticly notifys you that they are availble and you then download direct to device, allowing you to use ota root keeper.
i upgraded to .21 using wolfs method last night and confirm that root is not kept if you do it that way.
when i get a working unit i will help intercept where the update downloads to and get a copy from my device, even if it means downgrading multiple times till we get it right!
I have no problem with what you said XN, the problem is with people like aznmode.
Who said
aznmode said:
You can go to Asus.com and download the .21 updated zip file.
Click to expand...
Click to collapse
slayvus said:
I have no problem with what you said XN, the problem is with people like aznmode.
Who said
Click to expand...
Click to collapse
Did you see my 2nd paragraph? Did that not answer your question? I try to help and you have a problem with it. Get that stick out of your ass dude.
Sent from my PG86100 using Tapatalk 2
Did you even read my OP before I updated it? I have no problem with reading.
I can NOT receive OTA Updates. My Prime has an Unknown Serial Number. ASUS refuses to push OTA Updates to Primes that have the Unknown Serial Number.
I understand you cant receive OTA and thats a known problem ever since the first ICS build came around and Asus is well aware of it and I've been in this ATP forums since this tablet was release so I am well aware of that issue as well. My 1st prime was in Dec of last year. Anyway I was generalizing when I said "you" and I didnt mean YOU cause obviously you cant get the OTA. My main point was how it can be done. I have intercepted an OTA before and I have some saved and I've done it with my Acer a100 as well. We're all here to help each other out so you should be thankful instead of being an ass about it. People will less likely to help you in the future. Not gonna waste anymore time..but good luck and hope you get your problem sorted out.
Sent from my Transformer Prime TF201 using Tapatalk 2
Simple question and hopefully different from all the other "It's here!", "Where are our ROM" threads..
I upgraded (if you can call it that) to the Galaxy Nexus literally like a week ago and deactivated my TB but it remains rooted.
Anyone know if there are dangers trying to activate it rooted with the intent to unroot, wait for the OTA, just in the hopes it will sell for more.
Or would you recommend unrooting then activating and then waiting for the OTA?
Hopefully you understand the question. I had the impression from a friend that if I tried to re-activate with root, it would red flag me for modified software. Thanks in advance.
DNak206 said:
Simple question and hopefully different from all the other "It's here!", "Where are our ROM" threads..
I upgraded (if you can call it that) to the Galaxy Nexus literally like a week ago and deactivated my TB but it remains rooted.
Anyone know if there are dangers trying to activate it rooted with the intent to unroot, wait for the OTA, just in the hopes it will sell for more.
Or would you recommend unrooting then activating and then waiting for the OTA?
Hopefully you understand the question. I had the impression from a friend that if I tried to re-activate with root, it would red flag me for modified software. Thanks in advance.
Click to expand...
Click to collapse
The stock rooted roms are posted on the Infected forums if you just want to flash the stock rooted ICS.
OR, you could unroot and flash the OTA, but doing so I believe will upgrade your hboot, so you'll have to wait a bit until get the s-off on the new hboot.
Either way, I'm sure it'll be all squared away in the next couple of weeks.
Personally, if it were me, I would unroot and go OTA. Fly around completely stock for a while on your phone. I did that when 605.19 came out and I was actually surprised how well it performed being completely stock (battery life aside). But that didn't last long for me--I rooted it pretty shortly after.
Also, I'm not sure if you'd be red-flagged for trying to update OTA from root. I mean the worst that could happen is the update won't go through, and more likely, the update will go through, but will completely remove root and s-off.
Don't take the OTA expecting to reroot!
wazup7 said:
The stock rooted roms are posted on the Infected forums if you just want to flash the stock rooted ICS.
OR, you could unroot and flash the OTA, but doing so I believe will upgrade your hboot, so you'll have to wait a bit until get the s-off on the new hboot.
Either way, I'm sure it'll be all squared away in the next couple of weeks.
Personally, if it were me, I would unroot and go OTA. Fly around completely stock for a while on your phone. I did that when 605.19 came out and I was actually surprised how well it performed being completely stock (battery life aside). But that didn't last long for me--I rooted it pretty shortly after.
Also, I'm not sure if you'd be red-flagged for trying to update OTA from root. I mean the worst that could happen is the update won't go through, and more likely, the update will go through, but will completely remove root and s-off.
Click to expand...
Click to collapse
There may not be a "re-root" after you take the new hboot!!!!
YOU HAVE BEEN WARNED!!!
I've been saying this and not enough people are listening and stuck not being able to root again.
I know one person even trying to work on the hboot right now and his device will no longer boot, so think again before taking the OTA.
It's up to you and doesn't effect me either way, just a few words of advice if you will.
Maybe this will change and another miracle as big as this release will happen and an exploit will be found on a 2 year old device with less then a handful of devs even looking at it.
This could change, but right now I would not count on it.
I took the update unrooted but still had revolutionary's hboot. I can confirm that the hboot was not overwritten by the new one.
Edit
Didn't realize there was a thread about this already lol. My bad.
Sent from my HTC6435LVW using xda app-developers app
Seems there is a LOT of revert to stock and unroot threads, is there a consolidated place or simple means of doing this? I think I'm going to undo everything I did and just her activate it stock. If she *****es down the road about not having root (unlikely), I'll worry about it then.
Thanks guys.