Install the ICS leak without Cheesecake and retain root
NOTE: Attempt this at YOUR own RISK.
That said, I have just easily installed the ICS leak (it is sweet), and retained root.
We have also confirmed thru multiple staffers you can fastboot back to .173
NOTE: We have no way of knowing if this will throw you off the official upgrade path.
Assume it will, so be prepared to fastboot back to stock if you upgrade now
All credit for the install goes to Vicious over at droidrazr.com
1) Download this torrent (LInk blocked till i get 8 post in this thread)
2) Make sure you have ROM Manager, ES File Explorer (Make sure root access and system writable are enabled in the ES file explorer settings), and have root access to your system but are on an otherwise stock COMPLETELY UNMODIFIED installation of 173. In ROM Manager, DO NOT INSTALL CLOCKWORKMOD. Just have the ROM Manager app itself installed.
2a) If you plan to have root after the update, make sure you have voodoo OTA Rootkeeper protecting your root before proceeding. (Install it, free in the market, open it and select protect root.)
3) Copy the 2 files from that torrent into your /cache folder on the root of your system (see the picss below, just press the indicated buttons in es file)
4) When the copy operation is complete, tap the zip file and select ROM Manager when it asks you what to use to open the file.
5) ROM Manager will automatically open and prompt you that a reboot is necessary to complete the operation. Hit OK/Accept.
6) The system will reboot and install the ICS leak.
REMEMBER Voodo OTA Root Keeper!!!
I would post link to the download but i need *8 post first so please help yourselves
Look 14 posts down Same info with links
http://forum.xda-developers.com/showthread.php?t=1575065
Why are you calling it official when it's the leak?
Ectoplasmic said:
Why are you calling it official when it's the leak?
Click to expand...
Click to collapse
It's a official leak lol
Sent from my XT910 using Tapatalk 2
What is this shenanigans?!
You're about 11 days and a ICS wrapper late.
Sent from my DROID RAZR using xda premium
PLEASE
please post the link
---------- Post added at 03:48 AM ---------- Previous post was at 03:47 AM ----------
Heres post #8 ...were jonesing for ICS !!!!
Please Please.... give me some Ice Cream!!! =)
COLoREDbyCHAoS said:
Install the ICS leak without Cheesecake and retain root
NOTE: Attempt this at YOUR own RISK.
That said, I have just easily installed the ICS leak (it is sweet), and retained root.
We have also confirmed thru multiple staffers you can fastboot back to .173
NOTE: We have no way of knowing if this will throw you off the official upgrade path.
Assume it will, so be prepared to fastboot back to stock if you upgrade now
All credit for the install goes to Vicious over at droidrazr.com
1) Download this torrent (LInk blocked till i get 8 post in this thread)
2) Make sure you have ROM Manager, ES File Explorer (Make sure root access and system writable are enabled in the ES file explorer settings), and have root access to your system but are on an otherwise stock COMPLETELY UNMODIFIED installation of 173. In ROM Manager, DO NOT INSTALL CLOCKWORKMOD. Just have the ROM Manager app itself installed.
2a) If you plan to have root after the update, make sure you have voodoo OTA Rootkeeper protecting your root before proceeding. (Install it, free in the market, open it and select protect root.)
3) Copy the 2 files from that torrent into your /cache folder on the root of your system (see the picss below, just press the indicated buttons in es file)
4) When the copy operation is complete, tap the zip file and select ROM Manager when it asks you what to use to open the file.
5) ROM Manager will automatically open and prompt you that a reboot is necessary to complete the operation. Hit OK/Accept.
6) The system will reboot and install the ICS leak.
REMEMBER Voodo OTA Root Keeper!!!
I would post link to the download but i need *8 post first so please help yourselves
Click to expand...
Click to collapse
I posted the 8th post yesterday. Can you unlock the link now Please?
MischiefsMommy said:
I posted the 8th post yesterday. Can you unlock the link now Please?
Click to expand...
Click to collapse
http://www.droidrzr.com/index.php/topic/1562-ics-anyone-i-haz-it-4-yew/
Related
There seems to be some anxiety about whether a successful ota update can be accomplished by those who modded their build prop file previously.
Just fyi for those who did the build.prop mod and have their original build.prop backed up but were waiting to attempt update, I will confirm that if you delete the modded build.prop and then rename your backed up build.prop.bak back to build.prop before you reboot then you will be able to take the ota update.
Steps I took:
Way back when I had originally renamed my build.prop to build.prop.bak leaving it in the system folder. I had then copied the modified build.prop file into the system folder and fixed the permissions.
Now, to reverse I did this (not sure if need to do all, but these were my steps:
1. opened root explorer
2. navigated to system folder
3. mount r/w
4. delete build.prop (this was the modded one)
5. renamed build.prop.bak to build.prop
6. confirmed permissions remained as they should
7. confirmed, in file properties, that ownership and group remained as "root"
8. mount r/o
9. exit root explorer
10. reboot
11. reboot again
12. opened voodoo ota rootkeeper
13. delete su backup
14. protect root
15. temp un-root
16 close voodoo ota rootkeeper
17. reboot
18 allow ota .28 update
19. when update finished reboot
20 open voodoo ota rootkeeper
21 restore root
So I suppose if you instead had a build.prop that you knew was the original you could substitute that one for the bak one.
Good luck
Yea best to do like you did and leave original in there for these occasions. 10 through 17 kind of overkill though. Reboot would be needed if you were wanting to apply the build.prop but in this case, simply putting the correct file there satisfies the system integrity requirements. No need to unroot. Just verify su backup with voodoo.
It is still fail if you did modify something else in /system partition. Like me i have removed a few sys apps and failed to upgrade. I had to do it manually.
Fireplug said:
There seems to be some anxiety about whether a successful ota update can be accomplished by those who modded their build prop file previously.
Just fyi for those who did the build.prop mod and have their original build.prop backed up but were waiting to attempt update, I will confirm that if you delete the modded build.prop and then rename your backed up build.prop.bak back to build.prop before you reboot then you will be able to take the ota update.
Steps I took:
Way back when I had originally renamed my build.prop to build.prop.bak leaving it in the system folder. I had then copied the modified build.prop file into the system folder and fixed the permissions.
Now, to reverse I did this (not sure if need to do all, but these were my steps:
1. opened root explorer
2. navigated to system folder
3. mount r/w
4. delete build.prop (this was the modded one)
5. renamed build.prop.bak to build.prop
6. confirmed permissions remained as they should
7. confirmed, in file properties, that ownership and group remained as "root"
8. mount r/o
9. exit root explorer
10. reboot
11. reboot again
12. opened voodoo ota rootkeeper
13. delete su backup
14. protect root
15. temp un-root
16 close voodoo ota rootkeeper
17. reboot
18 allow ota .28 update
19. when update finished reboot
20 open voodoo ota rootkeeper
21 restore root
So I suppose if you instead had a build.prop that you knew was the original you could substitute that one for the bak one.
Good luck
Click to expand...
Click to collapse
PLEASE SOMEONE POST A COPY OF THE ORIGINAL US VERSION BUILD.PROP from the .21 firmware
[email protected] said:
It is still fail if you did modify something else in /system partition. Like me i have removed a few sys apps and failed to upgrade. I had to do it manually.
Click to expand...
Click to collapse
Yep. If you want to take OTA's then you shouldn't remove system apps. If you absolutely can't live with the few manufacturer bloat apps, then you can always freeze them instead of remove them. then you can unfreeze them for an OTA.
flak0 said:
PLEASE SOMEONE POST A COPY OF THE ORIGINAL US VERSION BUILD.PROP from the .21 firmware
Click to expand...
Click to collapse
I would post it up for you but I already updated. You can always pull it out of an official update.zip I would think.
---------- Post added at 07:18 AM ---------- Previous post was at 07:14 AM ----------
check here. You might be able to extract what you need from the system dump.
http://forum.xda-developers.com/showpost.php?p=21065580&postcount=2
b.huss2 said:
Yep. If you want to take OTA's then you shouldn't remove system apps. If you absolutely can't live with the few manufacturer bloat apps, then you can always freeze them instead of remove them. then you can unfreeze them for an OTA.
I would post it up for you but I already updated. You can always pull it out of an official update.zip I would think.
---------- Post added at 07:18 AM ---------- Previous post was at 07:14 AM ----------
check here. You might be able to extract what you need from the system dump.
http://forum.xda-developers.com/showpost.php?p=21065580&postcount=2
Click to expand...
Click to collapse
Thanks but those zips have blob files
Sent from my LG-P999 using xda premium
flak0 said:
Thanks but those zips have blob files
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Can you not extract from blob?
flak0 said:
PLEASE SOMEONE POST A COPY OF THE ORIGINAL US VERSION BUILD.PROP from the .21 firmware
Click to expand...
Click to collapse
Here is a copy of the original US. 21
http://db.tt/SOxNURWA
Sent from my SGH-I777 using xda premium
Just make sure to remove ".bak"
Sent from my SGH-I777 using xda premium
Please, i need the EU version .21 of build.prop.
Thank you.
I followed your instructions and update went smooth
Sent from my Transformer Prime TF201 using XDA
I didn't even have to go to all that trouble.
Browsed to /system and renamed build.prop to build.prop.mod
renamed build.mod.bak to build.mod
verified I had a su backup in Voodoo
installed update
restored root
profitted.
I'm expecting to see the OTA show up any time now and I want to be ready for it. I'm running stock .181 rooted with bootstrap recovery. I've seen lots of threads with instructions for sideloading the 211 ICS update, and all say to use Matt's utility to start with clean version of .181 with no bootstrap. I'm willing to wait a day or a week or whatever for the OTA and don't see a need to rush and sideload ICS, so do those instructions still apply? I"m sure it's cleaner if I wipe everything before applying the OTA update, but I'd rather not spend the hours it will take to restore and recover all my apps and data and such if I don't have to.
So, do I have to rsd back to clean 181 to get rid of bootstrap recovery? Can I just uninstall the Razr Bootstrapper app? Any recommendations or advice would be appreciated.
Thanks!
OK. Found a simpler option than RSDing to re-install 181. I followed instructions to remove CWM posted at http://theunlockr.com/2012/01/24/how-to-install-bootstrap-recovery-on-the-motorola-droid-razr/ . I also un-installed the RAZR Bootstrapper app just to be on the safe side. I plan to back up root with OTA rootkeeper before installing OTA which I am hoping is soon.
Astrobrewer said:
OK. Found a simpler option than RSDing to re-install 181. I followed instructions to remove CWM posted at http://theunlockr.com/2012/01/24/how-to-install-bootstrap-recovery-on-the-motorola-droid-razr/ . I also un-installed the RAZR Bootstrapper app just to be on the safe side. I plan to back up root with OTA rootkeeper before installing OTA which I am hoping is soon.
Click to expand...
Click to collapse
I can't delete the files, I keep getting "error deleting file". Also am attempting to get in to adb shell using the utility and keep getting "the system cannot find the path specified". I have debugging enabled. Really getting fed up with this. I tried to use the utility to revert to at least a clean install of 181 and the path specified is never available. Root is good. Constant error messages.
Try opening the su app, then hit menu, then update your su binaries, then do it again, then open rom manager, or what ever app you may have, or boot into cwm and run fix permissions, reboot and try again, though, even if you remove bootstrap, if you've frozen, removed any bloat, or you/an app you installed altered your build.prop at all any update from vzn/moto will fail. Also I don't think ota rootkeepr works for going to ics. When you have root, ti backup and a nandroid are amazing time saving tools to have.
Sent from my DROID RAZR using xda premium
To delete/rename files using ES file explorer I had to go to preferences and check the root explorer option and the mount /system read/write option. Then all was good.
Sent from my Kindle Fire running Glazed ICS ROM
Astrobrewer said:
OK. Found a simpler option than RSDing to re-install 181. I followed instructions to remove CWM posted at http://theunlockr.com/2012/01/24/how-to-install-bootstrap-recovery-on-the-motorola-droid-razr/ . I also un-installed the RAZR Bootstrapper app just to be on the safe side. I plan to back up root with OTA rootkeeper before installing OTA which I am hoping is soon.
Click to expand...
Click to collapse
Can anyone confirm this method works? I would like to avoid rsd if at all possible. Wanna keep all my files / settings intact for the update.
Sent from my DROID RAZR using Forum Runner
Computer doesn't see your phone for adb? And you have the motorola usb drivers installed on the pc?
UrbanDroid said:
Can anyone confirm this method works? I would like to avoid rsd if at all possible. Wanna keep all my files / settings intact for the update.
Sent from my DROID RAZR using Forum Runner
Click to expand...
Click to collapse
I can confirm you do need to remove bootstrap. However, that method did not work for me to remove it to install the soak test. I'm not sure the reasoning, but the following steps:
[Removing CWM on Boot]
1) Delete file /system/bin/mot_boot_mode
2) Rename file /system/bin/mot_boot_mode.bin to /system/bin/mot_boot_mode
My phone did not have a mot_boot_mode.bin. I found an alternate set of instructions that did work and allowed me to receive the OTA soak.
This thread has the instructions I followed (also pasted below):
droidforums.net/forum/droid-razr-hacks/188690-how-remove-razr-bootstrap-custom-recovery.html
"I found a thread on DroidXForums.com by Abe21599, which suggested the following for a Droid X:
1. Reroot (If not currently rooted)
2. Get root explorer in the market
3. Uninstall the bootstrap app
4. Go into root explorer to system/bin
5. In top right corner tap r/w
6. Delete the file called hijack
7. Delete logwrapper
8. Rename logwrapper.bin to just logwrapper
9. Reboot and it should be gone.
(thanks to Droidforums member Hostility6)"
You also need to unroot, which I did with the Razr Utility 1.6. After all of this, I was able to install the soak OTA without any further issues!
The theunlockr.com article with instructions that I used referred back to a 12/18/2011 post by J.Y Daddy on xda, http://forum.xda-developers.com/showpost.php?p=20447149&postcount=47 . The instructions are pretty much the same as what brgr had but also have you delete the /preinstall/recovery directory. That may be why it didn't work for brgr.
Here are the instructions given in the J.Y. Daddy post:
It's complicated to remove.
Because, it must also be removed CWM recovery.
Follow the below with very careful:
Please work with RootExplorer.
[Removing CWM on Boot]
1) Delete file /system/bin/mot_boot_mode
2) Rename file /system/bin/mot_boot_mode.bin to /system/bin/mot_boot_mode
[Removing CWM Recovery]
1) Delete file /system/bin/logwrapper
2) Delete file /system/bin/hijack
3) Rename file /system/bin/logwrapper.bin to /system/bin/logwrapper
4) Delete directory /preinstall/recovery
Click to expand...
Click to collapse
I'm optimistic that it will work, but until I get the OTA I won't know. If it doesn't work out then I'll start clean with the razr utility.
Astrobrewer said:
The theunlockr.com article with instructions that I used referred back to a 12/18/2011 post by J.Y Daddy on xda, http://forum.xda-developers.com/showpost.php?p=20447149&postcount=47 . The instructions are pretty much the same as what brgr had but also have you delete the /preinstall/recovery directory. That may be why it didn't work for brgr.
Here are the instructions given in the J.Y. Daddy post:
I'm optimistic that it will work, but until I get the OTA I won't know. If it doesn't work out then I'll start clean with the razr utility.
Click to expand...
Click to collapse
I don't have the mot_boot_mode.bin file. Only the one without the. bin extension.
Will that make a difference to remove Bootstrap / CWM?
Thanks
Florestan2 said:
I don't have the mot_boot_mode.bin file. Only the one without the. bin extension.
Will that make a difference to remove Bootstrap / CWM?
Click to expand...
Click to collapse
Sounds like you didn't set up CWM to automatically run at boot, so you just skip the two steps in that section. As I understand it the mot_boot_mode.bin file is just a back-up of the stock mot_boot_mode file that is replaced when you run the set up to have CWM always come up when you reboot. To get rid of CWM on boot is to delete/rename to get the original file back. The stock version boots to your normal system ROM, the other version for CWM at boot boots phone to CWM. If you don't have a mot_boot_mode.bin file then just leave the mot_boot_mode file as is -- you definitely don't want to delete it.
I didn't set up CWM to come up automatically at boot, so I didn't have the .bin file either. It shouldn't matter because the mot_boot_mode file is the stock version (wasn't replaced to make CWM run at boot). Still need to do the rest of the steps to remove CWM recovery.
Hope this helps.
Good to know, that's what I was hoping for. I boot normally, not going into recovery first, so it makes sense.
Thanks
Ill let you all know how the OTA goes if and when i receive it. Just a waiting game now.
Sent from my DROID RAZR using Forum Runner
Moved To Q&A
Please Post questions in the Q&A section
Finally got OTA. I temp un-rooted with Voodoo before installing. Went very smoothly with no issues. After update i restored root with Voodoo and I'm back in the game.
Removing CWM using the steps i followed and temp un-rooting allowed OTA to work and let me keep root. Done.
Thanks
Sent from my rooted DROID RAZR MAXX
running ICS using xda premium
So after trying multiple times to update my tablet an failing everytime. I checked the last_log file in /cache/recovery and found out that the reason the update was failing because I've deleted Netflix.apk from /system/app.
Since I did not backup the application I had no way to use the OTA, however after a few hours research I found out a method to completely restore the system to stock.
Part 1: Restoring Tablet to Stock
1. Download the system dump that matches your current software:
9.4.2.28
WW - http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF201/WW_epaduser9_4_2_28UpdateLauncher.zip - MD5 - 68D41197B399967B7F6789E47683A0D7
US - http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF201/US_epaduser9_4_2_28UpdateLauncher.zip - MD5 - DF17D3129378E9A7F81C58AF7BF5396B
TW - http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF201/TW_epaduser9_4_2_28UpdateLauncher.zip- MD5 - 3999B0E052211AA53ED1DB5D06A02AD3
2. Unzip the compressed firmware file to the root directory of a MicroSD card (external). Only extract this once so your sdcard should look something like this:
/MicroSD/US_epad-user-9.4.2.28.zip
3.With your Transformer turned on, insert the MicroSD into the MicroSD card slot.
4. An exclamation mark should appear in the notification area.
5. Tap the mark and proceed with the update.
6. Your tablet should now reboot and proceed to update the tablet, if you get an error try redownloading the update and trying again.
Part 2: Rooting your Tablet
Voodoo root keeper didn't save my root after part 1, so to root it I used Debugfs automated root:
http://forum.xda-developers.com/showthread.php?t=1706588
After your tablet is rooted you should use OTA root keeper to backup your root.
Part 3: Manual Update to Jellybean
1.Download the dlpkgfile for your system, I uploaded the US file: <--------------- US ONLY don't try if your tablet is not on US firmware, it might brick
http://www.mediafire.com/?ddcl3k233kxsvv8
WW version dlpkgfile <--------------- WW ONLY don't try if your tablet is not on WW firmware, it might brick
The WW update file (thanks for kikistans for uploading):
http://dropbox.com/s/uiui6ha6hrg2mg1/dlpkgfile
http://www.mediafire.com/download.php?kzr30e1vufbgee9
2. Place the dlpkgfile on your tablet's storage, MAKE SURE THE dlpkgfile does not have a .zip extension, the file has no extension!
3. Download ES File manager and go to settings>root settings and tick all the boxes.
4. Copy dlpkgfile to /cache
5. Go to /cache/recovery and create a new file named command
6. Open the file as a text and place the following code in it and save:
--update_package=/cache/dlpkgfile
7. Turn off the tablet
8. Press and hold volume down+power until the tablet vibrates then release power and keep holding volume down
9 When a text shows on the boot logo screen release volume down and click volume up
10. The tablet should now start updating, it'll take about 30 minutes and once the tablet boots you'll have jellybean
11. Restore root with root keeper
This method should work for everyone with a locked bootloader:good:
Edit:
Sorry I've been busy, it seems like some people are missing 3 files, follow this thread if you're missing those files:
http://forum.xda-developers.com/showthread.php?t=1909820
Also some people are reporting that their tablet is get bricked, MAKE SURE THAT YOU'RE USING THE RIGHT FIRMWARE UPGRADE
new-tilus has reported that this method worked for his stock unlocked tablet.
I used the last part more our less. Ota rootkeeper claims I have root. But I don't. Photocopier still keeps root access, but I cannot gain any new root access.
Sent from my SAMSUNG-SGH-I717 using xda premium
It doesnt work for me. Im on .28 stock WW version. It starts but then appears android with red trangle
lukcinek said:
It doesnt work for me. Im on .28 stock WW version. It starts but then appears android with red trangle
Click to expand...
Click to collapse
Same here, no success for me either...
Didn't work
Sent from my Transformer Prime TF201 using xda premium
Do we really need to go thru the hardship? Isn't ASUS going to fix it?
I think it must be noted that the OTA update for a WW variant will not work on a US variant, a DE will not work on TW and so on. The SKU for the OTA must match the SKU of the Prime in question.
It works. It doesnt befor becouse I didnt delete .bin from name of the file
Uh, fix what? ASUS is in the business of doing firmware updates for stock + unlocked devices.
Spidey01 said:
Uh, fix what? ASUS is in the business of doing firmware updates for stock + unlocked devices.
Click to expand...
Click to collapse
It seems to work here, I did exactly what "Protato" wrote and it's been loading the new JB for more than 10 minutes and no triangle yet
It worked I am on JB 4.1.1, forllow the instructions "literally" and it will work!
by far the simplest instructions to follow
i was having the same issue as most of you, i was (stock) rooted and applied the OTA update. i did have OTA root keeper, but my update failed and i lost root. i did a factory reset of 9.4.2.28 (US version) after a backup, then i rooted using DebugfsRoot_Generic. i more or less performed part 3 of this thread although i had to add three missing files to /system/xbin/ (maybe if i would have applied the stock 9.4.2.28 file i could have skipped this step). i forgot to restore my backup before i applied the update so i lost root. updating and keeping root may require SuperSU instead of SuperUser, from what i read last night. i hope this helps, thanx to all the people out there, especially @Wipeout and @Trekest from the post below, as well as @sparkym2 for Debugfs and @1wayjonny for Universal Naked Driver 0.7 and @Protato. good luck, i wish this thread was around yesterday evening, it would have saved me hours...
missing files from the below thread post #111
http://forum.xda-developers.com/showthread.php?t=1907804&page=12
Got red triangle, will try again.
work for me! thanks
Anybody remember how to have Flash working again.
For me it works on default browser, but it's not working anymore on Boat Browser.
I saw a thread this morning, but now I can't remember where it is.
Thanks if any link will be passed here.
1. Downloaded US version (mine is US build) - checked MD5 version to be the same.
2. Extracted once and copied the .zip to the root of external memory card.
3. Upgrade file detected - proceed with upgrade
4. Reboot. Then progress bar for upgrade.
5. Device started with a message that upgrade process completed. I am still seeing 4.0.3
Sorry posted too early.. still need to follow step 2 & 3.
-----------------------
*** PERFECT ***
All steps worked EXACTLY as explained in OP :good:. I am running JB now. Even I managed to restore root explained. Thanks you very much !!!
Thanks for this! I applied steps 1 through 3 and no problems updating to Jelly Bean! Although I protected root. I lost root after update:/ Oh well. small price to pay for Jelly Bean!
ES file explorer will not allow copy of needed file.
bimbobo said:
It seems to work here, I did exactly what "Protato" wrote and it's been loading the new JB for more than 10 minutes and no triangle yet
It worked I am on JB 4.1.1, forllow the instructions "literally" and it will work!
Click to expand...
Click to collapse
Can't get Es file ex. to allow me to copy the file to the cache folder, says copy failed? Any suggestions?
sly.cooper said:
1. Downloaded US version (mine is US build) - checked MD5 version to be the same.
2. Extracted once and copied the .zip to the root of external memory card.
3. Upgrade file detected - proceed with upgrade
4. Reboot. Then progress bar for upgrade.
5. Device started with a message that upgrade process completed. I am still seeing 4.0.3
Sorry posted too early.. still need to follow step 2 & 3.
Click to expand...
Click to collapse
Yeah, this happened to be too.
Battery is too drained now. Charging and will try again when I have enough juice.
StephanBotha said:
Yeah, this happened to be too.
Battery is too drained now. Charging and will try again when I have enough juice.
Click to expand...
Click to collapse
You still need steps 2 and 3
still got red andy. everything worked up until that.
Protato said:
So after trying multiple times to update my tablet an failing everytime. I checked the last_log file in /cache/recovery and found out that the reason the update was failing because I've deleted Netflix.apk from /system/app.
Since I did not backup the application I had no way to use the OTA, however after a few hours research I found out a method to completely restore the system to stock.
Part 1: Restoring Tablet to Stock
1. Download the system dump that matches your current software:
9.4.2.28
WW - http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF201/WW_epaduser9_4_2_28UpdateLauncher.zip - MD5 - 68D41197B399967B7F6789E47683A0D7
US - http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF201/US_epaduser9_4_2_28UpdateLauncher.zip - MD5 - DF17D3129378E9A7F81C58AF7BF5396B
TW - http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF201/TW_epaduser9_4_2_28UpdateLauncher.zip- MD5 - 3999B0E052211AA53ED1DB5D06A02AD3
2. Unzip the compressed firmware file to the root directory of a MicroSD card (external). Only extract this once so your sdcard should look something like this:
/MicroSD/US_epad-user-9.4.2.28.zip
3.With your Transformer turned on, insert the MicroSD into the MicroSD card slot.
4. An exclamation mark should appear in the notification area.
5. Tap the mark and proceed with the update.
6. Your tablet should now reboot and proceed to update the tablet, if you get an error try redownloading the update and trying again.
Part 2: Rooting your Tablet
Voodoo root keeper didn't save my root after part 1, so to root it I used Debugfs automated root:
http://forum.xda-developers.com/showthread.php?t=1706588
After your tablet is rooted you should use OTA root keeper to backup your root.
Part 3: Manual Update to Jellybean
1.Download the dlpkgfile for your system, I uploaded the US file:
http://www.mediafire.com/?ddcl3k233kxsvv8
2. Place the dlpkgfile on your tablet's storage.
3. Download ES File manager and go to settings>root settings and tick all the boxes.
4. Copy dlpkgfile to /cache
5. Go to /cache/recovery and create a new file named command
6. Open the file as a text and place the following code in it and save:
--update_package=/cache/dlpkgfile
7. Turn off the tablet
8. Press and hold volume down+power until the tablet vibrates then release power and keep holding volume down
9 When a text shows on the boot logo screen release volume down and click volume up
10. The tablet should now start updating, it'll take about 30 minutes and once the tablet boots you'll have jellybean
11. Restore root with root keeper
This method should work for everyone with a locked bootloader:good:
Click to expand...
Click to collapse
still got red andy, followed instructions to the tee!
In case you want to do the actually OTA with your phone, and got some errors (dead android), you might want to check:
+ if you are using "CWM Recovery" (then uninstall it as in http://forum.xda-developers.com/showthread.php?t=2095825)
+ if you are using "Remove QSlide Apps from NotificationBar" (http://forum.xda-developers.com/showthread.php?t=2194423)
But don't use the QSlide revert file from above thread, it doesn't restore the exact matched file for OTA to work with (you can try if you want). To save you some trouble, I have attach the original files (LGSystemUI.apk and its odex). Unzip and overwrite them in the folder /system/app (use ES Explorer to remount /system RW first).
+ still not found the problem, check the few last lines of this file: /system/cache/recovery/last_log
It should say which file mismatches the checksum, and in the case of mine, it is LGSystemUI.apk, which I cannot find anything related searching google. And that's why I make the thread so people can search google and found it here.
chicguy said:
In case you want to do the actually OTA with your phone, and got some errors (dead android), you might want to check:
+ if you are using "CWM Recovery" (then uninstall it as in http://forum.xda-developers.com/showthread.php?t=2095825)
+ if you are using "Remove QSlide Apps from NotificationBar" (http://forum.xda-developers.com/showthread.php?t=2194423)
But don't use the QSlide revert file from above thread, it doesn't restore the exact matched file for OTA to work with (you can try if you want). To save you some trouble, I have attach the original files (LGSystemUI.apk and its odex). Unzip and overwrite them in the folder /system/app (use ES Explorer to remount /system RW first).
+ still not found the problem, check the few last lines of this file: /system/cache/recovery/last_log
It should say which file mismatches the checksum, and in the case of mine, it is LGSystemUI.apk, which I cannot find anything related searching google. And that's why I make the thread so people can search google and found it here.
Click to expand...
Click to collapse
Removed CWM and still get dead android red triangle icon.
My log also shows LGSYSTEMUI.APK ERROR
eSZee said:
Removed CWM and still get dead android red triangle icon.
My log also shows LGSYSTEMUI.APK ERROR
Click to expand...
Click to collapse
If you are rooted then all you need to do is find a nandroid backup of previous jb and flash it. Then you use the trick to force the OTA. If you are not rooted then the only thing I can say is download the kdz, flash it, and wait for the OTA.
there are a few things that manipulate the system: link2sd, overclocking, busybox, custom recovery. . .My thing was the busybox. I totally forgot that I downloaded it and my update didn't work at first. Good Luck
eSZee said:
Removed CWM and still get dead android red triangle icon.
My log also shows LGSYSTEMUI.APK ERROR
Click to expand...
Click to collapse
Go go page 9 of the forum link below. There is a Dropbox link of a factory rooted version of V20f for the 769 US version to flash if you have access to CWM on your phone.
http://forum.xda-developers.com/showthread.php?t=2359044
Sent from my LG-P769 using Tapatalk 2
TheCoutures said:
Go go page 9 of the forum link below. There is a Dropbox link of a factory rooted version of V20f for the 769 US version to flash if you have access to CWM on your phone.
http://forum.xda-developers.com/showthread.php?t=2359044
Sent from my LG-P769 using Tapatalk 2
Click to expand...
Click to collapse
Downloaded several times to make sure it wasn't a bad download. Went to apply zip, as soon as I pressed YES, INSTALL ABORTED.
I have no mods or edited system files or anything like that. All I ever did was CWM and root. Had qslide removed but reverted.
Make sure MD5 sum is correct. The other stuff doesn't matter. You are flashing a full backup not an OTA which requires all stock apps.
Sent from my LG-P769(20F) using the xda-developers app. If I helped you please hit the thanks button.
eSZee said:
Downloaded several times to make sure it wasn't a bad download. Went to apply zip, as soon as I pressed YES, INSTALL ABORTED.
I have no mods or edited system files or anything like that. All I ever did was CWM and root. Had qslide removed but reverted.
Click to expand...
Click to collapse
Wait you tried to install it as a zip
You are supposed to extract it and put the nandroid in the CWM backup directory.
sent from my locked rooted P769 v20D
I'm on YouTube (BioDesigner48)
I'm having the same issue, I do not have CWM or QSlide Remove installed, I've uninstalled all Root related apps and still encountering the same issue....
eSZee said:
Downloaded several times to make sure it wasn't a bad download. Went to apply zip, as soon as I pressed YES, INSTALL ABORTED.
I have no mods or edited system files or anything like that. All I ever did was CWM and root. Had qslide removed but reverted.
Click to expand...
Click to collapse
In my OP, I said "don't use the QSlide revert file from above thread, it doesn't restore the exact matched file for OTA to work with".
In case you still have trouble with the OTA, try to follow what I wrote: "To save you some trouble, I have attach the original files (LGSystemUI.apk and its odex). Unzip and overwrite them in the folder /system/app (use ES Explorer to remount /system RW first)."
Hope that helps!
For other people with problems, I suggest to use the Recovery Flashable Zip mentioned in one of the reply.
Or, if you are as paranoid as I am (who knows what people might put in those zip file ) (and somewhat technically knowledgeable), "check the few last lines of this file: /system/cache/recovery/last_log" to see what file got error, and try to get the original file from 20D (which should have the matched SHA1 checksum) and replace them.
chicguy said:
In my OP, I said "don't use the QSlide revert file from above thread, it doesn't restore the exact matched file for OTA to work with".
In case you still have trouble with the OTA, try to follow what I wrote: "To save you some trouble, I have attach the original files (LGSystemUI.apk and its odex). Unzip and overwrite them in the folder /system/app (use ES Explorer to remount /system RW first)."
Hope that helps!
For other people with problems, I suggest to use the Recovery Flashable Zip mentioned in one of the reply.
Or, if you are as paranoid as I am (who knows what people might put in those zip file ) (and somewhat technically knowledgeable), "check the few last lines of this file: /system/cache/recovery/last_log" to see what file got error, and try to get the original file from 20D (which should have the matched SHA1 checksum) and replace them.
Click to expand...
Click to collapse
Get the full P769BKv20f kdz file download here. Please be advised that this is just stock and if you flash this ROM then you WILL LOSE ROOT! But you can download and create a bin file to do the Lelus root method.
YOU HOLD MYSELF AND XDA FREE FROM ANY LIABILITY. WE ARE NOT RESPONSIBLE FOR YOUR DEVICE. FLASH AT YOUR OWN RISK.
This will enable Native Tether for Build 23.3.24.
Prerequisites:
Droid Maxx/Ultra Rooted w/WP off
METHOD 1: TWRP INSTALL
1) Download the package below labeled "23.3.24tether_twrpinstall".
2) Reboot Into TWRP recovery and navigate to the file for flashing.
3) Reboot
4) Verify tether works
5) Profit.
METHOD 2: MANUAL INSTALL
1) Download the package below labeled "23.3.24tether".
2) Download root browser by Jrummy from the play store
3) Navigate to System/Priv-App and rename VZWEntitlementservice.apk to VzwEntitlementservice.apk.bak.
4) Navigate to System and rename the build.prop to build.prop.bak
5) Place the package on the root of your sd card and extract the build.prop file within the folder.
6) Navigate to system and Copy and paste the new file.
7) Set permissions for the file to
Owner: Read/Write
Group: Read
Others: Read
This should show (rw-r--r--)
8) Reboot. Verify tether works
9) Profit.
REVERTING
METHOD 1:
If installed in twrp, download the package below labeled 23.3.24tether_revert. Flash in Twrp, reboot, verify subscription check re-enabled.
METHOD 2:
If manually installed, simply delete the build.prop you installed, remove the .bak extension from the original build.prop, verify permissions, reboot.
Works great thanks. I like the flash method because you don't even have to root your phone to do it. That is really nice when you have a corporate email setup that restricts rooting of the phone. Another nice thing is that you can flash from a USB stick which is nice since my internal SD card is encrypted due to corporate email also.
nukeruss said:
Works great thanks. I like the flash method because you don't even have to root your phone to do it. That is really nice when you have a corporate email setup that restricts rooting of the phone. Another nice thing is that you can flash from a USB stick which is nice since my internal SD card is encrypted due to corporate email also.
Click to expand...
Click to collapse
How did you manage to flash it without root?
If you have an unlocked bootloader then you can just fastboot the recovery and flash the zip. No root app required.
Sent from my XT1080 using Tapatalk
nukeruss said:
If you have an unlocked bootloader then you can just fastboot the recovery and flash the zip. No root app required.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Gotcha. I suppose I should have looked at your signature. Ha
Will you have a version for 24.3.7 or will this one work?
TIA
Mike
It looks like he just added 3 lines in the build.prop. I'll try it tomorrow and if it works I'll post it.
Sent from my XT1080 using Tapatalk
I just updated the build.prop files for the latest build. Actually had to add three lines for it to work. I tried the flash method on my phone and it worked just fine. Topsnake no longer has a droid maxx and gave me permission to post these.
visual voicemail problem with this mod?
Have anyone had problems with visual voicemail asking you to setup every day after doing this mod?
Anybody getting prompted for the lollypop update? I'm running topsnakes 4.4.4 and the update is rolling out for the Moto X so... I'm sure it won't just update through ota but I'm wondering if anybody is working on the port for the maxx