OTA for Asia Retail RAZR XT910 - Motorola Droid RAZR

I live in India & I got the 65.1.21.en.03 OTA (168.9 MB) this morning.
Mentioned changes included bug fixes, a newer baseband and kernel, and the Bejeweled 2 game... although it is still on Gingerbread 2.3.5.
Anyone know how and where I can extract the downloaded update from my phone? Device isn't rooted.

Downloading..
The path/filename is
/cache/Blur_Version.65.1.12.XT910.PSHAsiaRetail.en.03.zip
and it's crc is
# cat /cache/Blur_Version.65.1.12.XT910.PSHAsiaRetail.en.03.crc
2663201091

Does the OTA break root?

The update failed on my rooted xt910. Will investigates later.
Sent from my XT910 using XDA App

Got update today!
I also got update today(india).. Dont know what are the changes happened.. Did not root my phone..

we (at Indonesia) also got the update today.
Tried to update my rooted Razr but like bahathir mine is also failed.
Do we need to get un-rooted before we install this update?

Update work fine on my rooted phone. The update did break the root. Install OTA rootkeeper will help to restore the root.
Sent from my XT910 using XDA App

Updates:
Problems:
1) Update failed.
2) Don't know which file(s) was/were changed, or failed crc check
Investigations and Findings:
0) Put the update file into external microSD. or rename it as update.zip
1) Boot to stock recovery mode.
Power off -> Power + Vol Up + Vol Down for 5 secs or until boot menus appear.
Select Recovery; Wait untul the trianagle with ! mark appear.
Vol Up + Vol Down until the selections appear
Select apply from sdcard and select the update file
In my case, the installation stopped because /system/build.prop has been changed. The changes were done by Motomizer app.
Solution:
Get the proper build.prop file and put it back to /system
Repeat the recovery again... You also can use $ adb reboot recovery from your PC/laptop.
Luckily, I only had one file conflicted by the upgrade.
Important Note:
The update is immune to to zergRush exploit, and you cannot gain ROOT anymore for time being!
Thank you.

So update breaks root and phone cannot be rooted? My update is still downloading
---------- Post added at 08:18 PM ---------- Previous post was at 08:18 PM ----------
How to get the update.zip file? Its only OTA

polaris441 said:
Update work fine on my rooted phone. The update did break the root. Install OTA rootkeeper will help to restore the root.
Sent from my XT910 using XDA App
Click to expand...
Click to collapse
I wish I had seen your post this afternoon.

Updated. Did NOT break root.

bahathir,
can you tell me how to get the original build.prop? My failure was definitely caused by the motomizer also.
Thanks again.

Since I cannot find SEAOP stock ROM, I recreated the file based on one of the build.prop from a stock ROM I found in xda motorola dev forum. Luckily it works
Sent from my XT910 using XDA App

Most of the time, official update will changes file's permission to default. This mean, the suid permission of the /system/xbin/su wil be removed. Check your build version to make sure the update is successful.
Sent from my XT910 using XDA App

bahathir said:
Since I cannot find SEAOP stock ROM, I recreated the file based on one of the build.prop from a stock ROM I found in xda motorola dev forum. Luckily it works
Sent from my XT910 using XDA App
Click to expand...
Click to collapse
care to share the file(build.prop).

Does anyone get a /tmp/sideload/package.zip (status 7) error in the stock recovery?
I've tried everything I could've possibly done(restore, stock files etc) but I still get this error. I really dont care much about my root and losing it would make no difference to me. I use the camera extensively so this update is very important to me.
Please help guys!
Thanks!
EDIT:
This is the exact thing that I see every time I try to install the update
Finding update package......
Opening update package.....
Verifying update package......
Installing update......
assert failed: mount("ext3", "MTD", "system", "/system")
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation Aborted.

/edit Ignore this, it was me thinking Astro file browser should of been working, Root Explorer works fine.
Would there be any other cache location,
I don't appear to have it in /cache/Blur.... (I did the put the update off for an hour option) and searching for it's up to 30mins and still going which is making the phone a pretty good hand warmer.

Here is my SEAOP build.prop Enjoy.

You need root power to access /cache. You need to copy it out AFTER the downloading finished but BEFORE you start installing the updates.
From Connectbot terminal
Code:
$ su
# ls /cache
# cat /cache/Blur_....zip > /sdcard/Blur_....zip
1) Get the root power;
2) list /cache directory and look for update file, mine is Blur_Version.65.1.12.XT910.PSHAsiaRetail.en.03.zip
3) copy the file from the /cache to /sdcard. Then you can copy to microSD's SD-ext
Good luck.

cheekrox said:
Updated. Did NOT break root.
Click to expand...
Click to collapse
how come?? is there something special method to keep the device rooted?

Related

[Q] ICS leak install issues

Hey been on these forums forever since i was installing themes on my hp ipac or htc shadow. Not a noob by any meens. Been flashing android since my G1. Now that thats out of the way im trying to flash a ICS leak to mess with the webtop 3.0. I was coming from a stock/rooted .181...
1. I fastbooted to .181 using the droid razr 1.6 utility.
2. then i root using ICS installer Combo.
3. Next i use the ICS installer Combo to install the .79 leak.
4. allowed rom manager and su user permissions. i get an error that it can not mkdir to /sdcardEXT.. is this a normal error? Either way once the phone reboots it starts install but then gets the ! in the triangle and what i assume, fails and reverts back to .181.... What am i doing wrong iv been at it for like 3 hours and im pulling my hair out trying to figure out what im missing. My battery is at 40%, is that an issue? Assuming not since if i can fastboot to .181 i should be able to install .79
Hopefully this makes sense and thanks for taking a look
I had something similar to this happen to me when downgrading-rooting-upgrading my Transformer Prime. It failed the upgrade OTA part because I had modified the build.prop and that kept it from installing the upgrade and I got the ! triangle. Have you changed anything? Frozen any apps? Changed your build.prop from stock?
There is a directory you can look in for the log file of why it failed the upgrade. I think it is under /cache/recovery directory from root. (you have to be rooted to see it and use a root explorer). Open the log file and see why its failing.
Thanx for the quick reply. if memory serves me right i modified the build prop to mess with the s-voice app. so your saying fastbooting wouldnt restore this? if not i guess il have to figure out how i changed it and change it back before trying this install again
Well, I would have thought fastbooting would bring it to total stock, but I had made a change in my build.prop AFTER I had downgraded I believe. I think I would check that directory if you can /cache/recovery for the log file and see whats causing your failure specifically. Again, you'll need a good root explorer (like "Root Explorer") and make sure you have it do root so you can see the sub directories too. I was using ES Explorer and it was not seeing the /cache/recovery directory, just /cache and using Root Explorer showed me the sub folder.
PS> Changing your build.prop back to what it looked like before the change didn't work for me. I had to get a stock, unmodified build.prop form another user on here for it to work.
PPS> Why are you wanting to install the leak? Its pretty much been all but confirmed its happening OTA very soon.
Ok i checked out the build.prop alot of stuff in there but seems to all be correct.
I checked that log file and at the very bottom i get this.
Finding update package...
I:Update location: /cache//Blur_Version.6.12.181.XT912.Verizon.en.US.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
E:failed to open /cache//Blur_Version.6.12.181.XT912.Verizon.en.US.zip (No such file or directory)
I:verify_file returned 1
E:signature verification failed
Installation aborted.
Have no idea what that means tho... If anyone needs the whole log to help me out let me know
Well, thats a lot different than what mine said so your problem is different, but I'm sure someone can help with that info. Heres what mine said when it was the build.prop:
file "/system/build.prop" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/build.prop"
etc...
Shinare said:
Well, thats a lot different than what mine said so your problem is different, but I'm sure someone can help with that info. Heres what mine said when it was the build.prop:
file "/system/build.prop" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/build.prop"
etc...
Click to expand...
Click to collapse
Yeah hopefully someone can, i mean with the ota around the corner this is not too big of an issue as long as it doesn't effect the official ota. Thanks for taking the time tho.
Well, the only other thing I can think of thats happened in the past is the wrong "region" file for the phone you are trying to update.
Like you are on US_ENG on your phone and you are trying to flash a WW_ENG or something so its not matching up? *shrug* just a blind guess. Hope someone can help you out.
This may or may not help, but I got that error back in the day flashing a ROM on my D2. In clockwork there was a option to disable and enable signature verification.
Or maybe the zip is messed up?
See the thing is i did this all through the guide in the dev section. i would have posted it there but i didnt have enough posts to post there, im more of a reader than a preacher. i only downloaded the 2 files with the 2 different batch scripts. 1 to fastboot to .181 and 1 to install ICS. Il figure it out eventually, but thanks guys. hopefully someone gets me there sooner.
**fixed it, i ended up using the permissions option in rom manager and also made sure the phone was over 50% and it worked so hopefully this helps soeone eles if they stumble across it.

[Q] Remove Bootstrap Recovery before installing ICS OTA?

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

[How-To] Update to Jellybean if you're having problems with OTA

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!

New VZW update vrall4

Anyone install this update? Is this the exynos fix? Is it hurting your battery life? International versions are claiming they are having battery issues with the update version they have recieved.
Sent from my SCH-I605 using xda premium
Please get the update zip or a logcat for me:
Code:
adb shell logcat > logcat.txt
Post it here.
adrynalyne said:
Please get the update zip or a logcat for me:
Code:
adb shell logcat > logcat.txt
Post it here.
Click to expand...
Click to collapse
Is that from a computer? I'm at work now no computer to use, and i already updated does that matter? Can I get direct from phone for you? If so how?
Sent from my SCH-I605 using xda premium
OK so found out its a change to add a boundary check routine to only allow applications to access the phones memory in specific areas. What ever that means
Sent from my SCH-I605 using xda premium
dawiseguy77 said:
OK so found out its a change to add a boundary check routine to only allow applications to access the phones memory in specific areas. What ever that means
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
Could that be another defense against allowing access to google wallet?
---------- Post added at 07:33 PM ---------- Previous post was at 07:30 PM ----------
dawiseguy77 said:
Is that from a computer? I'm at work now no computer to use, and i already updated does that matter? Can I get direct from phone for you? If so how?
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
Were you rooted before you updated your device?
Not rooted yet
Sent from my SCH-I605 using xda premium
Update failed
I was rooted and the update failed. Unrooted (saved root with Voodoo), and the update failed again... gotta check and see what I'm missing before I go to any more trouble
crcpeach said:
I was rooted and the update failed. Unrooted (saved root with Voodoo), and the update failed again... gotta check and see what I'm missing before I go to any more trouble
Click to expand...
Click to collapse
I just tried it. here was the log when flashing the update
updating partition details...
E: Invalid command argument
Installing zip file '/cache/fota/update.zip
Installing '/cache/fota/update.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
assert failed: getprop("ro.product.device") == "
getprop(ro.build.product" == "t01tevzw"
E: Error in /cache/fota/update.zip
(Status 7)
E: Error installing zip file '/cache/fota/update.
as it reset my phone, it opened up my Team Win Recovery attempted to install what ever it was it wanted to update, finished doing what it did and i had to click reboot from TW. phone rebooted and it came back with an update failed message and wanted to do it again, so i clicked defer for 5 days. In the system up[date the only thing i see for it was an error 410 code...
name of update is: update_SCH-I605_LJB_to_LL4
Rootkeeper worked
Was rooted and but saved root through voodoo. This update installed fine for me, let's see what happens.

Error on update to V20F

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.

Categories

Resources