Database Users

[HOWTO] Force US10.4.2.9 Jellybean Update on Any Variant - Locked/Unlocked

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have a Canadian ASUS TF300 purchased from Futureshop. It shipped with WW firmware, and I updated OTA to WW9.4.3.30 before starting this.
I have lost root in the process. But I wasn't keep on keeping it in the first place. I kept all my apps and am now on US10.4.2.9 Jellybean Android 4.1.1. Maybe someone can chip in on how to keep root.
My device is NOT unlocked. Following this procedure requires that you root your device temporarily.
You will end up with JB with one modified binary (su, but with safe system permissions as a result of the rooting process).
This method is very time consuming (1-2 hours), so I don't recommend it for everyone. You need knowledge of ADB to proceed with this.
How To Flash (Unlocked/locked Device)
1) Convert to US9.4.3.30 using the blob:
Download US9.4.3.30 from the ASUS download page here: http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+TF300T
Open the firmware download package with 7zip or similar, and extract 'blob'.
2) Copy blob into your internal memory (/sdcard/). I used adb push to do this
3) Continue following 'Method 2' from here: http://forum.xda-developers.com/showthread.php?t=1622628
(You probably want to clean up the symlink after you finish this method)
You are now on the stock US9.4.3.30 firmware
4) Perform the official upgrade to the US10.4.2.9 firmware manually
Download US10.4.2.9 from Asus: http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download
Remove any external storage media attached to the device before proceeding.
The downloaded file is to be placed in the root directory of the internal storage (/sdcard). Reboot to install if the prompt to install doesn't come up right away.
(instructions by Bolandk. not tested by me.)
FROM THIS POINT FORWARD, THE INSTRUCTIONS BELOW ARE OBSOLETE AND ARE KEPT HERE FOR FUTURE REFERENCE ONLY
4) Root the firmware using the DebugFS method: http://forum.xda-developers.com/showthread.php?t=1706588
IF YOU WANT TO KEEP ROOT, FOLLOW THIS: http://forum.xda-developers.com/showthread.php?t=1840504
5) Use this method to force the FOTA update (dlpkgfile)
Download dlpkgfile from this thread:
http://forum.xda-developers.com/showthread.php?t=1840397
Follow this: http://forum.xda-developers.com/showthread.php?t=1803090
The difference is that our device does not vibrate. You want to hit 'vol up' right when your device shows any text, and this is within 5 seconds of you pressing the voldown+power combination. If you miss this, you need to recopy 'command' back into /cache/recovery.
6) The update process will start automatically. This takes 20 minutes to complete.
Region conversion instructions
Since ASUS has posted the Jellybean updates for a while now, I thought I'd update this post with instructions to change to another region.
To region convert, you need to download the firmware for the target region. Ideally you want the version you are currently on. I think you may end up losing root in the process, but I don't know a way around that at the moment.
You do not have to be bootloader unlocked to do this.
Extract the xxxUpdateLauncher.zip into the root directory of a microSD card formatted to FAT/FAT32. Then rename the file as EP201_768_SDUPDATE.zip. Reboot into the bootloader (vol - and power), and select the first option (left most square) when the menu comes up. The firmware update will start automatically in this mode.
I converted back from a US to a WW build without wiping using this method.

xaueious said:
I have a Canadian ASUS TF300 purchased from Futureshop. It shipped with WW firmware, and I updated OTA to WW9.4.3.30 before starting this.
Good luck!
Click to expand...
Click to collapse
Do you know of a way to force downgrade from Jelly Bean to ICS 9.4.3.17? I don't have any root access and need to restore it.

This works good it took me a little over an hour
but you lose root and the ability to flash a custom recovery (CWM,TWRP)
Please correct me if I am wrong

I haven't tried it this way yet, but it seems a little easier if someone wanted to try it.
jvanassche said:
Alright, after some work, I finally got this to install on my unlocked device following these steps:
1) If not already on stock, wipe everything and reflash to stock .30 update and reinstall TWRP 2.2.1.3. Be sure to backup before wiping.
2) Download the zip from the OP, and extracted it to a folder on your hard drive.
3) Open META-INF\com\google\android\updater-script in Notepad.
4) Deleted line 3 and 4 of the file. The Line to be deleted should read assert(getprop("ro.product.device") == "EeePad" ||
getprop("ro.build.product") == "EeePad");
5) Create a new zip file containing all of the files you extracted in step 2, including the modified updater-script file, and copy to your device.
6) Reboot into TWRP
7) In TWRP, under mount section, ensure all four mount options are checked, and internal memory is checked at the bottom
8) Flash the zip file you copied in step 5.
9) Reboot, and enjoy your Jelly Beans.
Click to expand...
Click to collapse

Turbojugend said:
I haven't tried it this way yet, but it seems a little easier if someone wanted to try it.
Click to expand...
Click to collapse
Just attempted this but got "install fail"
Its my 1st time creating a zip file so maybe I goofed at it. Used 7zipper.
Sent from my Nexus S 4G using Tapatalk 2

I can confirm after slaving away at this method. It does work and I am now on Jelly Bean.

Zadeis said:
I can confirm after slaving away at this method. It does work and I am now on Jelly Bean.
Click to expand...
Click to collapse
You still have root or lost after flash the rom?

wonsanim said:
You still have root or lost after flash the rom?
Click to expand...
Click to collapse
You will lose root without a modified dlpkgfile update-script.

wonsanim said:
You still have root or lost after flash the rom?
Click to expand...
Click to collapse
Unfortunately, no. I used ota root keeper and everything only for it to not work in the end...

Zadeis said:
Unfortunately, no. I used ota root keeper and everything only for it to not work in the end...
Click to expand...
Click to collapse
I'm in the same boat. I backed up root with the OTA Rootkeeper, but after the upgrade, it it doesn't restore root.
I did read in another thread, that some people were successful in restoring root in JB with OTA Rootkeeper, but they had SuperSU installed. Of course, I came across that little tidbit right in the middle of the upgrade

Actually, i'll what I said back. I actually managed to restore my root. I'm not sure what I did differently, but I have thankfully have root again!

i was able to restore root too.

FYI, this worked for me with an unlocked bootloader.
Extremely happy right now. Thanks for this.

Works great with unlocked bootloader, thanks again.

Sorry but what is the point if you already unlocked bootloader/root/install custom recovery , and now you tried to flash back to stock to get OTA update ?
- You tried to root/ flash custom rom at first place, and now you back to stock to get OTA update and you can't root once you update to 4.1.1. More important, 3-4 peoples already get their tab bricked when they tried to flash CWM after Jelly bean update as they attempt to root their device again. And now they screw up cause they can get warranty from ASUS. Why don't you guys wait couple days when developers make a new custom roms based on official 4.1.1 updated so yous just easily flash through recovery. Just my 2 cents :highfive:

sorta works
It worked sort of.
My tf300 was already "unlocked"
But the instructions didnt work exactly.
Here is what I had to do:
1. Use TWRP recovery to install the ICS official rom from ASUS
2. Use the idcrysis method for rooting after initial setup (failed the first time but worked the second try after rebooting)
3. put the dlpk file on the root of the tablet from: http://forum.xda-developers.com/showthread.php?t=1840397
4. Root the firmware using the DebugFS method: http://forum.xda-developers.com/show....php?t=1706588
5. copy "dlpkgfile" into /cache/ directory
6. create the file called "command" under /cache/recovery/
7. write this statement in the file /cache/recovery/command (without qoutes) "--update_package=/cache/dlpkgfile"
Dunno why it didnt work for me the right way but this is how I got it to work. Not root doesnt work but I can live with that till I read about rooting Jelly Bean tomorrow when I wake up.
If anyone else has issues forcing the jelly bean update these steps I did worked. I am definetely NOT a programmer, just had to follow steps from multiple posts. I kind of wished I could relock the bootloader again. This was such a pain in the rear!

OTA and Fully Removied Moded Binary
xaueious said:
I have a Canadian ASUS TF300 purchased from Futureshop. It shipped with WW firmware, and I updated OTA to WW9.4.3.30 before starting this.
I have lost root in the process. But I wasn't keep on keeping it in the first place. I kept all my apps and am now on US10.4.2.9 Jellybean Android 4.1.1. Maybe someone can chip in on how to keep root.
My device is NOT unlocked. Following this procedure requires that you root your device temporarily.
You will end up with JB with one modified binary (su, but with safe system permissions as a result of the rooting process).
This method is very time consuming (1-2 hours), so I don't recommend it for everyone. You need knowledge of ADB to proceed with this.
How To Flash (Unlocked Device)
0) Download dlpkgfile from this thread:
http://forum.xda-developers.com/showthread.php?t=1840397
1) Convert to US9.4.3.30 using the blob:
Download US9.4.3.30 from the ASUS download page here: http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+TF300T
Open the firmware download package with 7zip or similar, and extract 'blob'.
2) Copy blob into your internal memory (/sdcard/). I used adb push to do this
3) Continue following 'Method 2' from here: http://forum.xda-developers.com/showthread.php?t=1622628
(You probably want to clean up the symlink after you finish this method)
You are now on the stock US9.4.3.30 firmware
4) Root the firmware using the DebugFS method: http://forum.xda-developers.com/showthread.php?t=1706588
IF YOU WANT TO KEEP ROOT, FOLLOW THIS: http://forum.xda-developers.com/showthread.php?t=1840504
5) Use this method to force the FOTA update (dlpkgfile)
Follow this: http://forum.xda-developers.com/showthread.php?t=1803090
The difference is that our device does not vibrate. You want to hit 'vol up' right when your device shows any text, and this is within 5 seconds of you pressing the voldown+power combination. If you miss this, you need to recopy 'command' back into /cache/recovery.
6) The update process will start automatically. This takes 20 minutes to complete.
Good luck!
Edit:
If you are unlocked, you might as well wait for a repacked ROM.
Click to expand...
Click to collapse
I was wondering if you do a full reset, is the device OTA Eligible for future updates and are you able to remove the moded binary by doing a full reset.

does this have any side effects, eg no more ota or is the us version crippled because of patents?

OK....can someone confirm this for me.
I am stock,locked and rooted...my OTA failed due to some frozen apps.
So I would take the dlpkgfile and place it in /cache
I would then place the "command"file from the link in #5 and place that in c/cache/recovery
Then reboot into recovery and it should install on it's own?
Can anyone confirm this for me? Anyone locked have success with this process?
Also anyone have the dlpkgfile they can mirror...the original one generated too much traffic and is no longer available.

turdbogls said:
OK....can someone confirm this for me.
I am stock,locked and rooted...my OTA failed due to some frozen apps.
So I would take the dlpkgfile and place it in /cache
I would then place the "command"file from the link in #5 and place that in c/cache/recovery
Then reboot into recovery and it should install on it's own?
Can anyone confirm this for me? Anyone locked have success with this process?
Also anyone have the dlpkgfile they can mirror...the original one generated too much traffic and is no longer available.
Click to expand...
Click to collapse
dlpkgfile

[Solved] [Q] [4.4] [Nexus 7 2012 3G] Rooting problem: ineffective flashing of superSU

Hello,
I just updated my Nexus 7 2012 3G from 4.2 (unlocked, rooted) to 4.3 manually (fastboot), then 4.4.2 via OTA.
Now I'm trying to root my device again, by flashing SuperSU-v1.80 through CWM interface (recovery-clockwork-6.0.1.9-grouper).
Problem is, even though the SuperSu app appears after flashing it, I get the message
HTML:
no su binary installed and supersu cannot install it
Updating it changes nothing.
I tried to flash again the same file, and now the app simply disappeared. Installing the Play Store app does nothing either. I'm stuck here.
Any idea ?
For reference, after I tried to flash a first time (and it didn't work) I noticed that an incorrect storage size was recognized. So I did a factory reset, got the correct storage size, then tried to flash SuperSu again to gain root, to no avail. So I tried more than twice, with a factory reset inbetween.
Solution
I was just using outdated tools : my version of CWM and SuperSU were both too old to work on 4.4.2
Always get the latest of those two on their respective websites.

OneXdude said:
Hello,
I just updated my Nexus 7 2012 3G from 4.2 (unlocked, rooted) to 4.3 manually (fastboot), then 4.4.2 via OTA.
Now I'm trying to root my device again, by flashing SuperSU-v1.80 through CWM interface (recovery-clockwork-6.0.1.9-grouper).
Problem is, even though the SuperSu app appears after flashing it, I get the message
HTML:
no su binary installed and supersu cannot install it
Updating it changes nothing.
I tried to flash again the same file, and now the app simply disappeared. Installing the Play Store app does nothing either. I'm stuck here.
Any idea ?
For reference, after I tried to flash a first time (and it didn't work) I noticed that an incorrect storage size was recognized. So I did a factory reset, got the correct storage size, then tried to flash SuperSu again to gain root, to no avail. So I tried more than twice, with a factory reset inbetween.
Click to expand...
Click to collapse
Hi, OneXdude...
Due to security changes in KitKat, Chainfire had to re-work the way root worked, so it's probable your rather old SuperSU-v1.80 (which worked with Jellybean) is the cause of the problem...
Try the latest version, SuperSU-v1.93...
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Rgrds,
Ged.

Thanks for the quick reply, GedBlake.
Though it still doesn't work.
Here is what I did :
- Boot into CWM
- Factory Reset
- adb sideload of SuperSU-v1.93
- reboot
- initial setup
- tap on superSU app : "no su binary installed and supersu cannot install it"

OneXdude said:
Thanks for the quick reply, GedBlake.
Though it still doesn't work.
Here is what I did :
- Boot into CWM
- Factory Reset
- adb sideload of SuperSU-v1.93
- reboot
- initial setup
- tap on superSU app : "no su binary installed and supersu cannot install it"
Click to expand...
Click to collapse
Hi, OneXdude...
Try it this way...
** Download SuperSU-v1.93 direct to your Nexus 7 using Chrome or other Android browser.
** Boot into CWM.
** In CWM, select the 'Install Zip' option, followed by 'Choose zip from /sdcard'...
**...and then navigate to the folder where the SuperSU .zip just downloaded to... usually the '/download' folder.
** Flash the SuperSU-v1.93 zip.
** Reboot... and you should be rooted
Rgrds,
Ged.

GedBlake said:
Hi, OneXdude...
Try it this way...
** Download SuperSU-v1.93 direct to your Nexus 7 using Chrome or other Android browser.
** Boot into CWM.
** In CWM, select the 'Install Zip' option, followed by 'Choose zip from /sdcard'...
**...and then navigate to the folder where the SuperSU .zip just downloaded to... usually the '/download' folder.
** Flash the SuperSU-v1.93 zip.
** Reboot... and you should be rooted
Rgrds,
Ged.
Click to expand...
Click to collapse
I followed this exact procedure, but sadly the problem remains.
I still get the error message.

OneXdude said:
I followed this exact procedure, but sadly the problem remains.
I still get the error message.
Click to expand...
Click to collapse
This is very puzzling...
Rooting the Nexus 7 should be a piece of cake... it certainly was for me.
I have to go out for an hour or so... but when I get back, I'll test flash SuperSU-v1.93 on my own Nexus 7 using ClockWorkMod recovery.
Normally, I use TWRP for such things... but I'll see how it goes with CWM and see if I can grab some screenshots and any error messages that may result.
--------------------------
Incidentally, I notice the version of CWM you have installed, is an older version - v6.0.1.9... the latest is v6.0.4.3, and is available from here...
https://www.clockworkmod.com/rommanager
Possibly fastboot flashing a more up to date version of CWM on your Nexus 7 may resolve your problem.
Rgrds,
Ged.

Hi again, OneXdude...
Further to my previous post...
As I've said, I normally use TWRP recovery (TeamWin Recovery Project) for rooting and flashing stuff like Custom ROMs and flashing 'mods' like Xposed framework...but I have used CWM (ClockWorkMod) recovery in the past... so my recollection of how CWM works, as it currently stands, is now a little hazy.
Hunting around on my laptop, I find the earliest version of a copy of CWM I have for the Nexus 7, is v6.0.2.3 with a date/time stamp of 3rd of January 2013!!
Which means your currently installed version of CWM v6.0.1.9 significantly pre-dates that...
...and is very, very out of date!!. Possibly dating it back to 2012.
So, I would strongly recommend you update your version of CWM to the latest version... which is v6.0.4.3.
I suspect, because you're using such an old version of CWM to root, is the probable cause of why your attempts to root have so far failed.
---------------------
Anyway...
I've just test flashed SuperSU-v1.93 on my own Nexus 7 (2012-WiFi ony) model... via CWM v6.0.4.3.
And it largely succeeded... the SU binary was successfully 'pushed' to /system/xbin... the only thing missing was the SuperSU app itself.
I've had this rather peculiar problem before... but it's easily resolved by just installing it from Google PlayStore.
Here is my CWM v6.0.4.3 output listing, when flashing SuperSU-v1.93... and is the sort of thing you should expect to see...
(Apologies for the poor quality of this screen shot... both TWRP and CWM recoveries lack the ability to directly take screenshots, so I had to photograph the screen using my Samsung Galaxy).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
--------------------------------------------------
So, in conclusion...
I would recommend you update your version of CWM to the latest version... and try flashing SuperSU v1.93 again.
Hope this helps... and good luck.
--------------------------------------------------
EDIT: Additional info...
Just spotted an incongruity/inconsistency in your first post... and which I have higlighted in red.
OneXdude said:
..
...I just updated my Nexus 7 2012 3G...
..
Click to expand...
Click to collapse
...and...
OneXdude said:
..
....by flashing SuperSU-v1.80 through CWM interface (recovery-clockwork-6.0.1.9-grouper).
..
Click to expand...
Click to collapse
-----------------------------------
If your Nexus 7 is 3G capable (and has a SIM card it in it), then you MUST ENSURE you have the correct Custom Recovery installed for your specific Nexus 7 type.
So... not only are you running a very old version of CWM, you're also running an incorrect version of CWM.
-----------------------------------
A 'grouper' Custom Recovery is intended for WiFi only Nexus 7's... like mine, for example.
However, your Nexus 7 is a 3G Nexus 7... and so you need a 'Tilapia' Custom Recovery installed.
For the latest version of CWM for your 3G/GSM device, that would be... recovery-clockwork-touch-6.0.4.3-tilapia.img.
And which you can find here...
https://www.clockworkmod.com/rommanager
...under the title of Google Nexus 7(GSM).
Download to your PC... and fastboot flash it.
Regrds,
Ged.

You were right, I was just using outdated tools to root my Nexus 7. I have it rooted now.
Thanks for your help and time, sorry that it was such an obvious answer.
Regards.

OneXdude said:
You were right, I was just using outdated tools to root my Nexus 7. I have it rooted now.
Thanks for your help and time, sorry that it was such an obvious answer.
Regards.
Click to expand...
Click to collapse
No apologies required... What is obvious to some, may be obscure to others.
You got there in there end... and that's what matters.
But make sure you have the right version of CWM installed (see the edit to to my previous post)... it will matter if you need to perform NANDROID backups.
Rgrds,
Ged.

[OTA] Stock XNPH25R OTA

Here's the new update that came out today - XNPH25R. This has the assert junk removed so you can flash it in TWRP.
NOTHING has been changed in this other than the ability to flash it in TWRP.
Reboot to recovery, flash .zip. Reboot to system. Nothing fancy required. *Flash SuperSU if you want root access.
https://www.4shared.com/download/4UoLVwKIce/cm-bacon-XNPH25R_fix.zip?lgfp=3000

I'm getting binary update script error by flashing with TWRP

I flashed the stock OTA in TWRP right from my phone. Go to Developer settings adn uncheck the update CM recovery setting and OTA will flash in TWRP. I kept root. I'm not sure if the 4.4 update will kill root, but I doubt it. Thanks for providing the zip!

With the option to update CM recovery via OTAs does that mean we can take OTAs with TWRP installed?

Hey Guys Can I flash this zip file through CWM ???? Please suggest...........
Update = flashed the official cm-11.0-XNPH22R-bacon-signed file & then received the OTA & it's installed successfully even with CWM install.

iamacronym said:
With the option to update CM recovery via OTAs does that mean we can take OTAs with TWRP installed?
Click to expand...
Click to collapse
I think you have to disable that option in developer settings menu, if you want to be able to flash the OTA with TWRP.
Works for me

Updated it using TWRP but once booted it tells me there's an udpate, over and over... update in TWRP seems to work (no fails, only message is "radio image updated")

I flashed the file and when I reboot i´m still on XNPH22R and it also does prompt for the update. I flashed it on twrp, everything seemed ok

Flashed the file with both TWRP and Philz, no error but the Rom version is still 22R !
Can someone post the stock recovery img please?

ToRvaLDs said:
Flashed the file with both TWRP and Philz, no error but the Rom version is still 22R !
Can someone post the stock recovery img please?
Click to expand...
Click to collapse
Yeah I get the same issue where it shows as the flashing being successful,but reboots back to 22R.

housry23 said:
I flashed the stock OTA in TWRP right from my phone. Go to Developer settings adn uncheck the update CM recovery setting and OTA will flash in TWRP. I kept root. I'm not sure if the 4.4 update will kill root, but I doubt it. Thanks for providing the zip!
Click to expand...
Click to collapse
Which folder was the OTA located in? Is it the cache one at root level?
Sent from N5 or OPO

truckroot said:
Which folder was the OTA located in? Is it the cache one?
Sent from N5 or OPO
Click to expand...
Click to collapse
I couldn't tell you. I got a notification that an update was available, tapped install and it booted into twrp and installed the update. I had to reinstall xposed but kept root and twrp.
Sent from my OnePlus One

housry23 said:
I couldn't tell you. I got a notification that an update was available, tapped install and it booted into twrp and installed the update. I had to reinstall xposed but kept root and twrp.
Sent from my OnePlus One
Click to expand...
Click to collapse
OK thx. Wasn't sure if u had to navigate to a certain folder when twrp booted up. Stock OTAs in a custom recovery is new territory for me.
Sent from N5 or OPO

truckroot said:
OK thx. Wasn't sure if u had to navigate to a certain folder when twrp booted up. Stock OTAs in a custom recovery is new territory for me.
Sent from N5 or OPO
Click to expand...
Click to collapse
I would say it's new territory for all of us. I do have the option to update cm recovery unchecked in developer settings.
Sent from my OnePlus One

housry23 said:
I would say it's new territory for all of us. I do have the option to update cm recovery unchecked in developer settings.
Sent from my OnePlus One
Click to expand...
Click to collapse
True. I have that unchecked and also had the system update apk frozen just out of habit.
Leave it to CM to allow OTAs to be installed thru twrp/cwm. Living this phone more and more each day.
Sent from N5 or OPO

Is it supposed to be about 23.55 mb only? Everytime i flash nothing changes...
Sent from my One using XDA Free mobile app

truckroot said:
Which folder was the OTA located in? Is it the cache one at root level?
Sent from N5 or OPO
Click to expand...
Click to collapse
The downloaded OTA is located in \cache and can be flashed trough TWPR. Unfortunately I get an error of missing apks in \system due to deleting some of them (CM File Manager, PrintSpooler, ...).
I'll try to throw them back to \system and retry flashing.
Nope nope nope, doesn't work. He says blabla build.prop because of changed DPI, but it gave me an error on executing the update binary anyway.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what happens when you try to flash the original OTA .zip in TWRP. When flashing the provided zip in OP I don't get an error but like everybody said it doesn't update to 25.

fiz:ik said:
Nope nope nope, doesn't work. He says blabla build.prop because of changed DPI, but it gave me an error on executing the update binary anyway.
Click to expand...
Click to collapse
Someone has the original build.prop? We can try to restore it and update.

ToRvaLDs said:
Someone has the original build.prop? We can try to restore it and update.
Click to expand...
Click to collapse
I've got it. Do you need? Texdroider DPI makes an backup of the original build.prop. I restored it and the issue is solved but nevertheless the update binary can't be executed.
Flashed CWM over TWRP: with CWM same problem. I restored original build.prop and it's still complaining about in the build prop.
Okay, seems that my backup of build.prop isn't the stock build.prop but an updated version with DPI of 380, damn. Can anyone upload the original one?

Can you upload the original build.prop please? Are you sure that the old file has the correct cm revision?
Inviato dal mio One utilizzando Tapatalk

[OTA] 4.4.4 -> 5.1 OTA Update for XT1045 PEREGRINE

I don't know if this is the appropriate place to post this, but I was looking all over for this OTA update and couldn't find it, finally was able to nab it off a friends XT1045 before he installed it, pulled it directly from the cache folder immediately after downloading the update. Hopefully this can help someone else...
File: Blur_Version.21.11.56.peregrine_retus.retus.en.US.zip
Download: https://goo.gl/VN3ObF
Size: 414.7 MB
MD5: 235297354b4f511ac2f4b469304f8b3f
SHA-1: d5ddf230cc98ab5935505f2b323e68e3a70b42d1
Guide coming shortly
Cheers

How is this installed?
Sent from my XT1045 using XDA Free mobile app

Travisholt92 said:
How is this installed?
Sent from my XT1045 using XDA Free mobile app
Click to expand...
Click to collapse
I'm not sure but i think that you need to go back to 4.4.4 Stock KK ROM from your device... Then flash the standard recovery (No TWRP or CWM) and on normal recovery you flash the zip

Go back to stock 4.4.4 and download this file. Reboot into recovery, select "install update.zip" choose the file, and install.

Checked today and my XT1045 had the 5.1 update available. The phone was recently flashed back to stock 4.4.4. Forgot I installed TWRP recovery and changed the boot logo. I started the update which then restarted the phone. TWRP started loading which got me a little worried but then saw it used an AOSP recovery script and TWRP handled it just fine. Once the phone finished loading I could see it was running Lollipop. However, I did get a Motorola message saying the update couldn't be applied or something and that no changes were made. It clearly did apply as checking the version info confirms it. The update did wipe the recovery and the boot logo I flashed. So got the bootloader unlock warning screen again. Though I only saw that after I tried going into recovery. The first few reboots didn't show it.

TadMSTR said:
Checked today and my XT1045 had the 5.1 update available. The phone was recently flashed back to stock 4.4.4. Forgot I installed TWRP recovery and changed the boot logo. I started the update which then restarted the phone. TWRP started loading which got me a little worried but then saw it used an AOSP recovery script and TWRP handled it just fine. Once the phone finished loading I could see it was running Lollipop. However, I did get a Motorola message saying the update couldn't be applied or something and that no changes were made. It clearly did apply as checking the version info confirms it. The update did wipe the recovery and the boot logo I flashed. So got the bootloader unlock warning screen again. Though I only saw that after I tried going into recovery. The first few reboots didn't show it.
Click to expand...
Click to collapse
Nice, i think still the safest mode is with stock recovery.
But TWRP FTW so i'm glad you found a way to install it without flash the stock recovery

I was running stock 4.4.4 firmware, but was unlocked, had twrp installed, and was rooted. It let me download the update fine, but upon clicking install, after the phone rebooted it would just get stuck in twrp. if i rebooted from there it would just say update failed. so then i went back and flashed stock recovery and tried again. now it would reboot into stock recovery, the install would get about half way then it would fail and boot back into the rom. the weird part is the phone would not stay powered on for more than 30 seconds before automatically powering itself down and trying to install the update again, so it was kind of stuck in a very long continuous boot loop if you will. i don't quite recall how i got it out of this continuous loop but eventually i did and booted up the stock recovery and attempted to flash the zip. failed again. got an error about install-recovery.sh having unexpected contents. so i went back and downloaded the full stock 4.4.4 rom, flashed recovery, boot, motoboot, logo, and the 3 system files via mfastboot (i did not have to erase userdata) and then booted into stock recovery and tried flashing the update again and it finally succeeded. i did not have to re-lock the phone at any point.
i will try to throw together a quick guide in a few outlining the above process for anyone who's trying to apply this update and having similar issues. here's what a successful update through stock recovery should look like:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Pupet_Master said:
Nice, i think still the safest mode is with stock recovery.
But TWRP FTW so i'm glad you found a way to install it without flash the stock recovery
Click to expand...
Click to collapse
If I was thinking I would have went back to stock recovery first by doing a full restore to 4.4.4. I did have to update TWRP to 2.8.7.0 as 2.8.3.0 is based on 4.4.4 and gave me the weird screen flicker now that the bootloader is on 5.1. Going to TWRP 2.8.7.0 fixed it.

Is there anywhere to download 4.4.4 firmware (ret.us) faster than 50 kbps?
Sent from my XT1045 using XDA Free mobile app

Travisholt92 said:
Is there anywhere to download 4.4.4 firmware (ret.us) faster than 50 kbps?
Sent from my XT1045 using XDA Free mobile app
Click to expand...
Click to collapse
I think some of them are uploaded to Mega, you would have to look for the links and check if it matchs your version. I don't remember who posted the mirrors..

Travisholt92 said:
Is there anywhere to download 4.4.4 firmware (ret.us) faster than 50 kbps?
Sent from my XT1045 using XDA Free mobile app
Click to expand...
Click to collapse
Would have done this sooner but misunderstood what you needed. Here it is on my Mega account.
RETUS_XT1045_4.4.4_KXB21.14-L1.56_cid9_CFC.xml
https://mega.nz/#!sVAVXZ5Q!tsWQDyW7GXsbFhqqQVWFz1BISNJMblOv_6cxElAPxP0

My moto g xt1045 is running on KK4.4.4 Stock ROM.
I get the notification for lolipop 5.1 updates (23.21.37.en.US) but the file downloaded to /cache directory is Blur_Version.21.11.56.peregrine_retus.retus.en.US.zip
But my current system version is 21.11.56.peregrine_retus.retus.en.US retus, running stock recovery but still gets error and no update done.
Any clue what can be the issue? Is it the wrong file downloaded for lolipop 5.1 updates (23.21.37.en.US)?

TadMSTR said:
Would have done this sooner but misunderstood what you needed. Here it is on my Mega account.
RETUS_XT1045_4.4.4_KXB21.14-L1.56_cid9_CFC.xml
https://mega.nz/#!sVAVXZ5Q!tsWQDyW7GXsbFhqqQVWFz1BISNJMblOv_6cxElAPxP0
Click to expand...
Click to collapse
Wow, Thank you!! I was able to run the OTA update after installing this as per the instructions in this thread:
http://forum.xda-developers.com/moto-g/general/guide-moto-g-4g-lte-xt1045-restore-to-t2826112

Hmmmm...Stock xt1045 4.4.4 > 5.1 install aborted?
Hi all - Have a totally stock xt1045 running 4.4.4 (21.12.63.peregrine_att.att.en.US att) and trying to install this 5.1 update via stock recovery ends in an install aborted multiple times. Have downloaded and bit checked the upgrade file multiple times. Am I missing something really dumb perhaps?
Any ideas appreciated.
Littlalex

can anyone please share the install-recovery.sh from unrooted XT1045 of KK4.4.4

Anyone have a custom recovery for XT1045 5.1?
Thank you!
---------- Post added at 06:41 PM ---------- Previous post was at 06:38 PM ----------
TadMSTR said:
Would have done this sooner but misunderstood what you needed. Here it is on my Mega account.
RETUS_XT1045_4.4.4_KXB21.14-L1.56_cid9_CFC.xml
https://mega.nz/#!sVAVXZ5Q!tsWQDyW7GXsbFhqqQVWFz1BISNJMblOv_6cxElAPxP0
Click to expand...
Click to collapse
littlalex said:
Hi all - Have a totally stock xt1045 running 4.4.4 (21.12.63.peregrine_att.att.en.US att) and trying to install this 5.1 update via stock recovery ends in an install aborted multiple times. Have downloaded and bit checked the upgrade file multiple times. Am I missing something really dumb perhaps?
Any ideas appreciated.
Littlalex
Click to expand...
Click to collapse
Try reinstalling 4.4.4 using the firmware and instructions in the posts above yours.

Thanks!
Thanks Tesla74...I plead old age senility!!
Littlalex

littlalex said:
Thanks Tesla74...I plead old age senility!!
Littlalex
Click to expand...
Click to collapse
Note that after you reinstall 4.4.4 that you'll have to update Motorola Update Services via Google Play before you'll be able to download the new update.

Failure with 4.4.4 stuff
Tesla74 - Followed the instructions but using the 4.4.4 file and from the first mfastboot command I got an error "(bootloader) Preflash validation failed/
FAILED (remote failure)." Got two more similar errors as I went on (huh - what a dope!) But phone is still booting normally w/4.4.4
Think I'll wait for the official OTA...I'm no stranger to this but am still a virgin with this phone
Thanks again
Littlalex

littlalex said:
Tesla74 - Followed the instructions but using the 4.4.4 file and from the first mfastboot command I got an error "(bootloader) Preflash validation failed/
FAILED (remote failure)." Got two more similar errors as I went on (huh - what a dope!) But phone is still booting normally w/4.4.4
Think I'll wait for the official OTA...I'm no stranger to this but am still a virgin with this phone
Thanks again
Littlalex
Click to expand...
Click to collapse
Sorry it didn't work for you. Make sure that Motorola Update Services from Google Play is up to date, otherwise you won't get the OTA update.

Repairing Nexus 6 Marshmallow 6.0 Failed Root

If your stupid like me :silly: and you blindly follow the [HOW-TO] The Nexus 6 All-In-One Beginner's Guide you may be trying to figure out how to fix your phone.
The beginner guide linked above is amazing to say the least but the OP has not updated it yet to reflect the 6.0 update. If your phone has Marshmallow 6.0 and you follow the instructions you will render your Nexus 6 unusable. Not bricked, just not functional. You will get an error that states Your device is corrupt. It can't be trusted and may not work properly. (seen below) Followed by a blank screen. But don't worry, its very easy to fix with just a few extra steps. :fingers-crossed:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are here, it is assumed that you have already done the following steps:
Step 0.1 Download and install the Android SDK tools (adb and fastboot), as well as the Google USB drivers. This is step 2 in the beginner guide and there is a great write up here on these tools. [noob-read] adb and fastboot. What is it? How can it help you?
Step 0.2 Unlocked the Bootloader.
Step 0.3 Ran the CF-Root tool. The file name is CF-Auto-Root-shamu-shamu-nexus6.zip
If you watched the CMD window closely this is where the problem happened. There will be a couple errors thrown. You will wait to see the big red Android on your phone but instead you will see the above warning message flash briefly followed by a black screen. If this is the case, proceed to step 1​
Please Note: Parts of these steps are copied and pasted from other instructions. Consider this a grouping of other instructions for the purpose of simplification.
Step 1 - Install a Custom Recovery (taken from the original guide)
Go HERE to download the latest TWRP recovery for the Nexus 6. At the time of this write-up, I used 2.8.5.0
Turn the phone off. Then boot it into the bootloader/fastboot mode by holding volume down + power.
Rename the recovery file that you downloaded above to recovery.img. *Make sure that you rename it to recovery.img NOT recovery.img.img
Move the recovery.img file to C:\Program Files (x86)\Android\android-sdk\platform-tools
Open command prompt and run the following commands:
Code:
cd C:\Program Files (x86)\Android\android-sdk\platform-tools
Code:
fastboot flash recovery recovery.img
On the phone, use the volume buttons to scroll onto "Restart Bootloader" and hit power to select it.
After the bootloader reloads, use the volume buttons to scroll onto "Recovery Mode" and power to select it. You should then be greeted with your newly installed custom recovery.
Power off the phone
Step 2 - Install the Modified boot.img (Original steps HERE)
Download the modified boot.img from http://downloadmirror.co/android/sx/shamu-mra58k-boot.zip
Unzip the file and move it to C:\Program Files (x86)\Android\android-sdk\platform-tools
Boot the phone back into bootload mode using Power + volume down.
Open a command prompt and enter the following commands:
Code:
cd C:\Program Files (x86)\Android\android-sdk\platform-tools
Code:
fastboot flash boot boot.img
Power off the phone
Step 3 - Flash the SuperSU zip via TWRP Recovery v2.56 beta (original steps HERE)
Downlaod SuperSU x2.56 from http://downloadmirror.co/android/u1/SuperSU-v2.56-20151030013730.zip
Boot your phone into the bootloader mode with Power + volume down
Enter recovery mode. This will open TWRP Recovery
After TWRP Recovery is open, connect your phone to your computer.
Open My Computer where youc an see the C: drive, and other connected drives. You should see your Nexus 6 listed. Open it.
Move the SuperSU zip onto your phone. I placed mine in the TWRP folder.
On your phone, select Install, then navigate to the folder that contains the SuperSU zip. Click on the zip file.
Swipe to Confirm Flash and begin the flash.
Once SuperSU is flashed, select the Reboot System option.
And that's it, your phone should now boot back up to your fresh rooted copy of Android Marshmallow 6.0. You can download a root verification app to confirm the root. :victory:

all i did was flash a twrp flashable stock marshmallow, then a custom kernel and supersu(in twrp). no odd message, everything booted fine

simms22 said:
all i did was flash a twrp flashable stock marshmallow, then a custom kernel and supersu(in twrp). no odd message, everything booted fine
Click to expand...
Click to collapse
You followed the correct instructions haha. That is basically what those 3 steps above entail, but broken down well enough they could be followed by someone who has not rooted a phone in the past. You also have to consider that if they followed that original beginner guide they can no longer boot into android, which kind of induces panic in most of us newbies and it makes it hard to search for and find the right answers. So basically this guide picks up right at the point where you realized "oh crap my phone didn't boot up like the instructions said it would, and now it won't turn on" :crying:
For those of us who have been down this road a time or two, this guide will not help them at all. Its really just directed to newbie's who are now stuck because of the beginner guide above.

K!ngpen said:
You followed the correct instructions haha. That is basically what those 3 steps above entail, but broken down well enough they could be followed by someone who has not rooted a phone in the past. You also have to consider that if they followed that original beginner guide they can no longer boot into android, which kind of induces panic in most of us newbies and it makes it hard to search for and find the right answers. So basically this guide picks up right at the point where you realized "oh crap my phone didn't boot up like the instructions said it would, and now it won't turn on" :crying:
Click to expand...
Click to collapse
key word, that gets very many in trouble afterwards.. "panic".
yea, i remember those days. but i was very lucky, as i never paniced. when i first rooted my g1(beginning of 2009), there were not very many people that knew about android, nor much info about it. so most of what we did back then was lots of trial and error :angel:

simms22 said:
key word, that gets very many in trouble afterwards.. "panic".
yea, i remember those days. but i was very lucky, as i never paniced. when i first rooted my g1(beginning of 2009), there were not very many people that knew about android, nor much info about it. so most of what we did back then was lots of trial and error :angel:
Click to expand...
Click to collapse
I'm right there with you. My first rooted device was a motorola xt720 sometime in 2010 I think. It was a company phone and like most very young IT folk I was curious lol. New versions of Android started rolling out but the phone wasn't going to get the update. So i was suck on Eclair. I stayed after work and tried the root, and it didn't work to say the least... I stayed at work until 2am trying to get that darn thing to work. 3 days later I got it to flash cyanogen. It was buggy as hell but i didn't care because I didnt have to explain to my boss that I broke my phone by trying to "hack" it lol. That was a win in my book. I later worked up the courage to get it back on a rooted version of Froyo. Pretty bumpy start to my rooting career to say the least. Now I'm a die hard Nexus follower just looking for an excuse to root the next device.

K!ngpen said:
You followed the correct instructions haha...
Click to expand...
Click to collapse
Everyone who is trying to help other users earns respect.

Thanks for this. it got me 98% there but SuperSU says i need to update the binary. Its gives me the option to update normally which fails or to update through twrp. Im not sure how to update through twrp. Any suggestions?

Noopguy said:
Thanks for this. it got me 98% there but SuperSU says i need to update the binary. Its gives me the option to update normally which fails or to update through twrp. Im not sure how to update through twrp. Any suggestions?
Click to expand...
Click to collapse
Just to confirm, your phone now boots back up correctly, but you get the popup stating that the binaries for SuperSU are missing?

K!ngpen said:
Just to confirm, your phone now boots back up correctly, but you get the popup stating that the binaries for SuperSU are missing?
Click to expand...
Click to collapse
Not missing but needs updating. My phone boots up and everything seems to fine otherwise. I tried updating with the normal option but it fails and going into twrp does nothing. I just cant figure out how to update the binaries with twrp. I tried to post a screen shot but XDA wont let me post a link since im a new user. imgur.com/a/Jgwpt

Noopguy said:
Not missing but needs updating. My phone boots up and everything seems to fine otherwise. I tried updating with the normal option but it fails and going into twrp does nothing. I just cant figure out how to update the binaries with twrp. I tried to post a screen shot but XDA wont let me post a link since im a new user. imgur.com/a/Jgwpt
Click to expand...
Click to collapse
And this was an unrooted nexus 6 with android 6.0 when you started? It wasn't already rooted on a lower version of android or anything like that?

K!ngpen said:
And this was an unrooted nexus 6 with android 6.0 when you started? It wasn't already rooted on a lower version of android or anything like that?
Click to expand...
Click to collapse
No i had it rooted on 5.1.1 this morning and updated to 6.0 with a factory image. I ran into problems rerooting after the update and I came here. I used your guide and everything works except i cant figure out how to update the binaries for SuperSU.

Noopguy said:
No i had it rooted on 5.1.1 this morning and updated to 6.0 with a factory image. I ran into problems rerooting after the update and I came here. I used your guide and everything works except i cant figure out how to update the binaries for SuperSU.
Click to expand...
Click to collapse
If you sideload this through TWRP you shouldn't need to update the binaries. It has the latest included.

Noopguy said:
I tried updating with the normal option but it fails and going into twrp does nothing. I just cant figure out how to update the binaries with twrp.
Click to expand...
Click to collapse
Flash SuperSU 2.52 Beta (not 2.56), then boot into Android and select "Update SuperSU Binaries" and select "TWRP/CWM" option rather than "Normal". Worked for me.
alryder said:
If you sideload this through TWRP you shouldn't need to update the binaries. It has the latest included.
Click to expand...
Click to collapse
I still needed to.
I'm on MRA58R, BTW (the third and latest factory image for Nexus 6).

sjgore said:
Flash SuperSU 2.52 Beta (not 2.56), then boot into Android and select "Update SuperSU Binaries" and select "TWRP/CWM" option rather than "Normal". Worked for me.
I still needed to.
I'm on MRA58R, BTW (the third and latest factory image for Nexus 6).
Click to expand...
Click to collapse
That's strange, I sideloaded that for MRA58K, MRA58N and MRA58R and I don't think I was ever prompted to update the binaries. I'm not sure you are being asked to.

alryder said:
If you sideload this through TWRP you shouldn't need to update the binaries. It has the latest included.
Click to expand...
Click to collapse
Thanks guys, this really helped. Flashing 2.52 did the trick and i didnt need to update the binaries after i flashed it. I am also on MRA58R

I was going to say as well, SuperSU v2.52 is what needs to be installed via TWRP, not v2.56. I believe v2.56 is for the new systemless root option but it sounds less stable and buggy.

Does this wipe any data? I have been looking to root and actually followed that guide myself, got the same issue and fixed by reflashing a factory image.
EDIT: I'm assuming I don't have to break my phone again to do this correct? Can I just pick up from step 1 to flash the recovery and go from there?

Something weird happened to me after flashing TWRP and I thought I'd share. So my N6 wasn't corrupted at all, but I decided to root my phone and I started by flashing TWRP. I went into boot loader and then recovery to make sure it worked and it did. When I went to reboot the system, I got the the "your device is corrupt screen." I pressed the power button and the screen turned black for a few seconds and then it rebooted normally. I went back into recovery to try and reproduce this and it happened again, Not sure why this happened but everything is functional.

New to rooting and I want to root my Nexus 6
I have a Verizon Nexus 6 with the build number "MRA58R." I haven't unlocked the bootloader or ran CF-Root tool like Steps 0.2 and 0.3 say. To root my phone, should I try and purposely break it by following the All-In-One Beginner's Guide and then follow the steps you put? Or is there another way I should go about rooting it? Thanks for your help

atvisic said:
I have a Verizon Nexus 6 with the build number "MRA58R." I haven't unlocked the bootloader or ran CF-Root tool like Steps 0.2 and 0.3 say. To root my phone, should I try and purposely break it by following the All-In-One Beginner's Guide and then follow the steps you put? Or is there another way I should go about rooting it? Thanks for your help
Click to expand...
Click to collapse
Lol why break it first. I didn't read through the op here but all you need to do is unlock the bootloader. Flash twrp with fastboot. Reboot to recovery without booting the phone, if you boot the phone before going into twrp it will get overwritten and you will need to reflash it. Flash a custome kernel in twrp, flash SuperSU 2.52 or higher in twrp.
The instructions in the op are more complete naturally. But when it has you flash the boot.img, you can use a custom kernel instead.