Related
Hi there,
I've been searching around to find a specific firmware zip for my new tablet, the SKU: WW, Version: 10.26.1.7.
It appears that asus has pulled this file and was wondering if anyone still has this file available somehow.
I soft-bricked my tablet and am not capable of flashing any other (earlier) firmware zip.
Any help would be greatly appreciated.
Yours sincerely,
Rens "Ikkerens" Rikkerink
Ikkerens said:
Hi there,
I've been searching around to find a specific firmware zip for my new tablet, the SKU: WW, Version: 10.26.1.7.
It appears that asus has pulled this file and was wondering if anyone still has this file available somehow.
I soft-bricked my tablet and am not capable of flashing any other (earlier) firmware zip.
Any help would be greatly appreciated.
Yours sincerely,
Rens "Ikkerens" Rikkerink
Click to expand...
Click to collapse
Why can't you download an earlier firmware?
schmeggy929 said:
Why can't you download an earlier firmware?
Click to expand...
Click to collapse
I can, but it always ends up with some kind of error.
I basically tried following the steps you did:
schmeggy929 said:
i downloaded the asus firmware for 10.14.1.47. extract zip and you get a user.zip. extracted the boot.img. I fastboot erase boot, system, format system, data and cache(as you did)
fastboot -i 0x0B05 flash boot boot.img then
fastboot -i 0x0B05 flash system blob then
fastboot -i 0x0B05 flash system UL-K00C-US-10.14.1.47-user.zip
rebooted back into fastboot and bootloader showed 10.14.1.47 version.
Click to expand...
Click to collapse
But on when trying to flash the ***-user.zip, I get this error message:
Code:
$ fastboot -i 0x0B05 flash system UL-K00C-WW-10.14.1.47-user.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
Edit: My bootloader version shows: WW_epad-10.26.1.7-20131108
Ikkerens said:
I can, but it always ends up with some kind of error.
I basically tried following the steps you did:
But on when trying to flash the ***-user.zip, I get this error message:
Code:
$ fastboot -i 0x0B05 flash system UL-K00C-WW-10.14.1.47-user.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
Edit: My bootloader version shows: WW_epad-10.26.1.7-20131108
Click to expand...
Click to collapse
you are going to get that along with a few more errors. Wait until it is done. It will take like 10 mins and finish.
when it is done reboot in bootloader and you should see the version change.
schmeggy929 said:
you are going to get that along with a few more errors. Wait until it is done. I will take like 10 mins and finish.
Click to expand...
Click to collapse
You're getting this wrong, it does not do anything. The process immediately quits.
Ikkerens said:
You're getting this wrong, it does not do anything. The process immediately quits.
Click to expand...
Click to collapse
Ok when you get that message do you get a blinking curser?
Ikkerens said:
Hi there,
I've been searching around to find a specific firmware zip for my new tablet, the SKU: WW, Version: 10.26.1.7.
It appears that asus has pulled this file and was wondering if anyone still has this file available somehow.
I soft-bricked my tablet and am not capable of flashing any other (earlier) firmware zip.
Any help would be greatly appreciated.
Yours sincerely,
Rens "Ikkerens" Rikkerink
Click to expand...
Click to collapse
did you make any backup with cwm recovery?
try this:
unpack blob from 47 update
Code:
fastboot flash staging blob
fastboot flash recovery recovery.img
fastboot reboot-bootloader
load recovery, restore your backup
if you have not made any backup with cwm recovery, tell me.
btw fastboot flash system... is not needed here
lpdunwell said:
did you make any backup with cwm recovery?
try this:
unpack blob from 47 update
Code:
fastboot flash staging blob
fastboot flash recovery recovery.img
fastboot reboot-bootloader
load recovery, restore your backup
if you have not made any backup with cwm recovery, tell me.
btw fastboot flash system... is not needed here
Click to expand...
Click to collapse
I have not made a backup using cwm because there was no CWM available for my version.
My tablet was already updated to 4.3 and I (apparently) could not boot the cwm in the development section.
If I would be able to flash a usable recovery, I wouldn't be in this situation anyway as the asus update (.47) is flashable (found an updater-script in the zip).
Ikkerens said:
I have not made a backup using cwm because there was no CWM available for my version.
My tablet was already updated to 4.3 and I (apparently) could not boot the cwm in the development section.
If I would be able to flash a usable recovery, I wouldn't be in this situation anyway as the asus update (.47) is flashable (found an updater-script in the zip).
Click to expand...
Click to collapse
forget what I wrote here. I opened a thread with unbricking instructions. Good luck
lpdunwell said:
forget what I wrote here. I opened a thread with unbricking instructions. Good luck
Click to expand...
Click to collapse
Won't do me any good at the moment, I already managed to brick it even further (couldn't even get into fastboot mode anymore), so I RMA'd it.
Ikkerens said:
Won't do me any good at the moment, I already managed to brick it even further (couldn't even get into fastboot mode anymore), so I RMA'd it.
Click to expand...
Click to collapse
oh crap. sorry about that. I know there's the nvflash, too, but I have no idea how to use that so far...
would you mind telling what exactly happened?
lpdunwell said:
oh crap. sorry about that. I know there's the nvflash, too, but I have no idea how to use that so far...
would you mind telling what exactly happened?
Click to expand...
Click to collapse
Nvflash is inaccessible at the moment, it requires some preparation (you have to prepare it BEFORE you brick it)
Anyway, basically, I bought the tablet a few hours earlier.
Wanted to root it to remove some bloatware and restore some titanium backup thingies.
So I unlocked, rooted, basic stuff.
Went into TB, removed bloatware such as Amazon Kindle and some other irrelevant titles.
That action however, somehow caused it to be unbootable.
So I went into some basic repair stuff, as usual.
Tried to flash a recovery, only to find out, there is no working recovery. Only CWM, which required an earlier version of my bootloader.
So, what next. Restore stock? Downloaded the firmware, found out it was the earlier version of my device, because Asus removed the 4.3-EU version from their website.
So, I downloaded the .47-EU version, opened it. Saw there were no images, merely plain files meant for /system and an updater-script.
I ended up attempting to package my own system.img after that. Created an ext4 image on my computer, moved the files there. Followed the instructions in updater-script, which were mostly symlinks and stuff.
In the end of the updater-script they flashed blob to /staging and boot.img to /boot.
So, I flashed my custom system.img to /system.
Flashed boot
Flashed the blob
And beyond that point, I ended up in a bootloop of my bootloader. I could not hold down volume to enter fastboot or anything. All I could do was watch the asus logo as it constantly rebooted. (And ofcourse, no way to turn it off other than waiting for the battery to die)
Ikkerens said:
Nvflash is inaccessible at the moment, it requires some preparation (you have to prepare it BEFORE you brick it)
Anyway, basically, I bought the tablet a few hours earlier.
Wanted to root it to remove some bloatware and restore some titanium backup thingies.
So I unlocked, rooted, basic stuff.
Went into TB, removed bloatware such as Amazon Kindle and some other irrelevant titles.
That action however, somehow caused it to be unbootable.
So I went into some basic repair stuff, as usual.
Tried to flash a recovery, only to find out, there is no working recovery. Only CWM, which required an earlier version of my bootloader.
So, what next. Restore stock? Downloaded the firmware, found out it was the earlier version of my device, because Asus removed the 4.3-EU version from their website.
So, I downloaded the .47-EU version, opened it. Saw there were no images, merely plain files meant for /system and an updater-script.
I ended up attempting to package my own system.img after that. Created an ext4 image on my computer, moved the files there. Followed the instructions in updater-script, which were mostly symlinks and stuff.
In the end of the updater-script they flashed blob to /staging and boot.img to /boot.
So, I flashed my custom system.img to /system.
Flashed boot
Flashed the blob
And beyond that point, I ended up in a bootloop of my bootloader. I could not hold down volume to enter fastboot or anything. All I could do was watch the asus logo as it constantly rebooted. (And ofcourse, no way to turn it off other than waiting for the battery to die)
Click to expand...
Click to collapse
Since you are unlocked, you can try to flash the recovery (extract it first) of the US version 1.7, should be the same as wwe. Or just even try to flash the whole us update manually. And later change back to the wwe version when it comes available. The 47 update was only a minor ota for 4.2 so no image of recovery or bootloader there.
Sad story. What would have been the safe thing to do, if others wish to root their devices?
Snah001 said:
Since you are unlocked, you can try to flash the recovery (extract it first) of the US version 1.7, should be the same as wwe. Or just even try to flash the whole us update manually. And later change back to the wwe version when it comes available. The 47 update was only a minor ota for 4.2 so no image of recovery or bootloader there.
Click to expand...
Click to collapse
I still had the original recovery flashed, I never overwrote it actually. I needed a custom recovery (such as CWM, TWRP).
Flashing an US update is not possible alltogether, there are some minor differences with hardware compitability and such.
Problem is, I could've downloaded the .47 update, but I had already updated to 4.3 (BL 10.26.1.7)
Ikkerens said:
I still had the original recovery flashed, I never overwrote it actually. I needed a custom recovery (such as CWM, TWRP).
Flashing an US update is not possible alltogether, there are some minor differences with hardware compitability and such.
Problem is, I could've downloaded the .47 update, but I had already updated to 4.3 (BL 10.26.1.7)
Click to expand...
Click to collapse
I don't know if it isn't possible. On the TF700 it was only a line in the build.prop file that made the difference.
I would try it because now you have nothing and when it works you have the us version yes, but at least it works.
pelago said:
Sad story. What would have been the safe thing to do, if others wish to root their devices?
Click to expand...
Click to collapse
This guide worked fine for me; http://forum.xda-developers.com/showthread.php?t=2516215
It's only about what you do with the root ^^
Snah001 said:
I don't know if it isn't possible. On the TF700 it was only a line in the build.prop file that made the difference.
I would try it because now you have nothing and when it works you have the us version yes, but at least it works.
Click to expand...
Click to collapse
Already too late, it has been RMA'd, and then, I had nothing to flash it with.
Ikkerens said:
This guide worked fine for me; http://forum.xda-developers.com/showthread.php?t=2516215
It's only about what you do with the root ^^
Click to expand...
Click to collapse
Well I meant, what should a root user do to try and protect themselves against bricking their device like you did? Is it a matter of making sure that CWM or TWRP is on the device as a recovery partition? And are those available on TF701T yet?
Oh dear. That's a lot gone wrong.
Cwm is available and that works.
It's made by drgravy. I use it in my unbrick tut.
All i can say is, root --> cwm --> backup.
Sent from my GT-I9505 using xda app-developers app
That CWM wouldn't boot for me :/
Have at it boys!
http://dl.google.com/dl/android/aosp/nakasi-lrx21p-factory-93daa4d3.tgz
MD5: e68948c23c918436680bd28fc6aaf983)
http://goo.gl/aYbCwf
IM guessing we can flash only system and boot...since the bootloader is the same. Plus, we don't wanna reflash the factory recovery.
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
ADB and Fastboot files attached below, if needed.
Mikey said:
IM guessing we can flash only system and userdata....since the bootloader is the same. Plus, we don't wanna reflash the factory recovery.
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
ADB and Fastboot files attached below, if needed.
Click to expand...
Click to collapse
Don't think that radio needs to be flashed on the N7
Cheers
Tom
I wouldn't flash the recovery partition, either.
The recovery-from-boot.p is in /system. I renamed it before the first boot using TWRP's file manager. I also flashed supersu. It's booting now...need to get to bed, though. Will report tomorrow.
Edit: Boot is successful. L.
Edit: This is my first go around with L. The checking for updates thing at sign on is interesting.
Flashed via fastboot and setting up now. I will report back with initial results and fire away any question you may want specifically answered.
FYI, first boot took about 6 minutes...
tom1807 said:
Don't think that radio needs to be flashed on the N7
Cheers
Tom
Click to expand...
Click to collapse
there is no radio in this....its wifi only....... the commands are generic
Hmmm...I am not getting supersu to work. Flashing the 2.16 zip in TWRP. The app says the binary is not installed.
brizey said:
Hmmm...I am not getting supersu to work. Flashing the 2.16 zip in TWRP. The app says the binary is not installed.
Click to expand...
Click to collapse
Probably needs a patch like for the N9.
Cheers
Tom
tom1807 said:
Probably needs a patch like for the N9.
Cheers
Tom
Click to expand...
Click to collapse
brizey said:
Hmmm...I am not getting supersu to work. Flashing the 2.16 zip in TWRP. The app says the binary is not installed.
Click to expand...
Click to collapse
http://www.ibtimes.co.uk/chainfire-releases-quick-root-fix-android-5-0-lollipop-preview-builds-how-install-1470680
https://plus.google.com/+Chainfire/posts/ZzXaU1W7Uzm
Mikey said:
http://www.ibtimes.co.uk/chainfire-releases-quick-root-fix-android-5-0-lollipop-preview-builds-how-install-1470680
https://plus.google.com/+Chainfire/posts/ZzXaU1W7Uzm
Click to expand...
Click to collapse
Yep...thanks.
Hmmm...this is not all that useful without Titanium. Will go back to KK in the AM and wait for a patched kernel.
Mikey said:
http://www.ibtimes.co.uk/chainfire-releases-quick-root-fix-android-5-0-lollipop-preview-builds-how-install-1470680
https://plus.google.com/+Chainfire/posts/ZzXaU1W7Uzm
Click to expand...
Click to collapse
Have to try probably, not sure whether this will run on a newer build of Lollipop
Cheers
Tom
Kernel version?
Any major differences than the couple of versions built from source?
Fyi, you will probably need SuperSU beta 2.19 and modified boot image for root. There is a titanium backup that works with l (beta). There may be a command that reflashes stock recovery on reboot (it's in /system /bin).
Tibu:
https://docs.google.com/file/d/0Bwj2Hf45t6uMSElfSXR6YXdVdVU/edit?usp=docslist_api
SuperSU:
http://forum.xda-developers.com/showthread.php?t=2868133
Nexus 7 5.0
Mikey said:
http://www.ibtimes.co.uk/chainfire-releases-quick-root-fix-android-5-0-lollipop-preview-builds-how-install-1470680
https://plus.google.com/+Chainfire/posts/ZzXaU1W7Uzm
Click to expand...
Click to collapse
tom1807 said:
Have to try probably, not sure whether this will run on a newer build of Lollipop
Cheers
Tom
Click to expand...
Click to collapse
Not good, the Boot.img is for Nexus 7 (2013)
Hangs at the Google logo.
Back to original Boot.img
Cheers
Tom
Mikey said:
IM guessing we can flash only system and boot...since the bootloader is the same. Plus, we don't wanna reflash the factory recovery.
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
Click to expand...
Click to collapse
Can I use these steps to clean flash the factory image?
I want to wipe everything and start from a fresh and clean flash.
I haven't flashed a factory image for a long time so I'm out of shape ?
Could someone make a flashable zip for multirom or normal flashing. ?
Nexus Root Toolkit
has anyone tried flashing this via nexus root toolkit? that software recently goot updated to 1.9.3 and has the abiloity to flash the Lollipop factory preview on those devices that got it.
That is exactly way I did. Started fresh and running smooth so far!
I used the toolkit to flash latest TWRP but that was all.
qualitymove13 said:
Flashed via fastboot and setting up now. I will report back with initial results and fire away any question you may want specifically answered.
FYI, first boot took about 6 minutes...
Click to expand...
Click to collapse
I was just going to ask about the boot time lol taking forever
My stock T-Mobile, unlocked bootloader N6 says that the 5.1.1. update is ready to install and then when I try to install it, it gets about 1/4 done and gives an error. I can reboot the phone at that point but the update never installs. Any suggestions? I've tried the factory reset and I get the same thing.
I downloaded the factory image and fastboot flashed the files.
Sent from my Nexus 6 using Tapatalk
Shift2win said:
My stock T-Mobile, unlocked bootloader N6 says that the 5.1.1. update is ready to install and then when I try to install it, it gets about 1/4 done and gives an error. I can reboot the phone at that point but the update never installs. Any suggestions? I've tried the factory reset and I get the same thing.
Click to expand...
Click to collapse
What error? Also, have you unencrypted?
Evolution_Tech said:
What error? Also, have you unencrypted?
Click to expand...
Click to collapse
Haven't unencrypted at all. The only "mod" has been the unlocking of the bootloader. Everything else is bone stock. And it just shows a picture of the Android robot laying down and it just says error underneath it.
Shift2win said:
Haven't unencrypted at all. The only "mod" has been the unlocking of the bootloader. Everything else is bone stock. And it just shows a picture of the Android robot laying down and it just says error underneath it.
Click to expand...
Click to collapse
Then as stated before, I recommend downloading the factory image, unzipping and flashing everything separately except userdata. Then you won't lose your data.
Shift2win said:
My stock T-Mobile, unlocked bootloader N6 says that the 5.1.1. update is ready to install and then when I try to install it, it gets about 1/4 done and gives an error. I can reboot the phone at that point but the update never installs. Any suggestions? I've tried the factory reset and I get the same thing.
Click to expand...
Click to collapse
Mine is doing the exact same, I'm also stock and on T-Mobile.
^same here...rooted and T-Mobile.
skipm said:
Mine is doing the exact same, I'm also stock and on T-Mobile.
Click to expand...
Click to collapse
n7plus1 said:
^same here...rooted and T-Mobile.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=61119896
Evolution_Tech said:
Then as stated before, I recommend downloading the factory image, unzipping and flashing everything separately except userdata. Then you won't lose your data.
Click to expand...
Click to collapse
I am rooted with stock recovery. Can I do this via ADB or do i need to install TWRP?
neudof said:
I am rooted with stock recovery. Can I do this via ADB or do i need to install TWRP?
Click to expand...
Click to collapse
Fastboot. You need an unlocked bootloader.
I have the same problem. I'm completely stock. Never done anything. I think it's a problem with the update. I've completely factory reset and wiped everything. I can't even get into the recovery mode. Just gives "no command" when I try.
robert_shipley said:
I have the same problem. I'm completely stock. Never done anything. I think it's a problem with the update. I've completely factory reset and wiped everything. I can't even get into the recovery mode. Just gives "no command" when I try.
Click to expand...
Click to collapse
That's exactly my problem, I'm completely stock and have to remain that way since I use my phone at work and they require the AirWatch MDM agent to be installed. I even tried deactivating AirWatch and uninstalling it and I still couldn't get the update to install. I hope there is some way they can either erase and download the update again or just overwrite the current one because this one definitely has problems.
Error you get if you look at recovery messages is
"Verifying current system...
System Partition has unexpected contents
E:Error in /cache/update.zip
(Status 7)
read elsewhere that something has modified a system file so OTA won't work and you'll need to flash full image (erasing everything in process) - which is my next step unless I want to wait for OTA to address the issue in the install procedure. No one has figured out what that item is that caused the change in system - some uninstalled Amazon appstore without success.
bchildress said:
Error you get if you look at recovery messages is
"Verifying current system...
System Partition has unexpected contents
E:Error in /cache/update.zip
(Status 7)
read elsewhere that something has modified a system file so OTA won't work and you'll need to flash full image (erasing everything in process) - which is my next step unless I want to wait for OTA to address the issue in the install procedure. No one has figured out what that item is that caused the change in system - some uninstalled Amazon appstore without success.
Click to expand...
Click to collapse
Just flash the system image. No need to flash everything. If you've unencrypted, then flash boot image too.
I have the same problem totaly stock, not rooted, untouched! I have the same error. I have 64 gb nexus 6 build number LMY47D.
Ok Guys,
Here is the solution,
1. Download stock image from google developer page, https://developers.google.com/android/nexus/images
2. Flash with long way;' DONT USE FLASH-ALL SCRIPT' (I tried, update fails again)
fastboot flash bootloader C:/image-shamu-XXXXXX/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/image-shamu-XXXXXX/radio.img
fastboot reboot-bootloader
fastboot flash system C:/image-shamu-XXXXXX/system.img
fastboot flash userdata C:/image-shamu-XXXXXX/userdata.img
(Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:/image-shamu-XXXXXX/boot.img
fastboot flash recovery C:/image-shamu-XXXXXX/recovery.img
fastboot erase cache
fastboot flash cache C:/image-shamu-XXXXXX/cache.img
(FOR FURTHER INFO PLS SEE THE PAGE; http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008)
3. Just turn on your N6 and it will find update and will be succesfull this time
Why do all that then OTA? Why not just flash everything but userdata from the LMY28E image? Boom your updated and you didn't lose data.
Evolution_Tech said:
Why do all that then OTA? Why not just flash everything but userdata from the LMY28E image? Boom your updated and you didn't lose data.
Click to expand...
Click to collapse
Hey,
I am Rooted with TWRP Recovery and Elemental X custom kernel, still encrypted with unlocked bootloader. I got the OTA (LMY47Z) notification and I have got the Factory Image as well as the OTA Zip. Can you guide me as to how can I update my Nexus (currently LMY47I) to 5.1.1 without losing any data?
Thanks.
The thing is which factory image for me?. Thats the reason i decided to do it via OTa. As u will see on developers page there are several versions,
5.1.0 (For T-Mobile ONLY) (LMY47M) Link 0469ca2018c923498cc603baae4fd648 5228e84a8a03609ead6b55df569057d5a4e28e0a
5.1.1 (For Sprint, USC ONLY) (LMY47Z) Link c8fe950ad9e861120a1074825b92cfba 33951732896055848d17b3876d8a39b79fb95301
5.1.1 (For T-Mobile ONLY) (LYZ28E) Link 9ea32a7ff1751afa2a16214ac23ef000 b542b88a0ad478110f9f111dd32b62a1cb65b9d5
So better to do it with the OTA.
peerpower said:
The thing is which factory image for me?. Thats the reason i decided to do it via OTa. As u will see on developers page there are several versions,
5.1.0 (For T-Mobile ONLY) (LMY47M) Link 0469ca2018c923498cc603baae4fd648 5228e84a8a03609ead6b55df569057d5a4e28e0a
5.1.1 (For Sprint, USC ONLY) (LMY47Z) Link c8fe950ad9e861120a1074825b92cfba 33951732896055848d17b3876d8a39b79fb95301
5.1.1 (For T-Mobile ONLY) (LYZ28E) Link 9ea32a7ff1751afa2a16214ac23ef000 b542b88a0ad478110f9f111dd32b62a1cb65b9d5
So better to do it with the OTA.
Click to expand...
Click to collapse
Download the OTA Zip, Extract it and check the "\META-INF\com\android\otacert" file to find the version number for your phone.
Hey guys
My N6 received the OTA update 2 days ago, I live in Australia and my device is rooted. I have downloaded the update then tried to restart and install for the first attempt, and off course it fails because am rooted. I have flashed the stock recovery.img and redownloaded it again, another failure. I have downloaded the OTA for the 3rd time and went to cache folder and took the "update.zip", then tried to flash it using TWRP and it failed. I have also tried the adb sideload and also failed. Below there is the pictures for the sideload procedure. What is puzzling me is that my phone build is "LMY47I" and what I receive is "LMY47Z" , so how can I apply this "update.zip" without wiping my system, I am already running on the stock image but it's rooted. I hope someone can help me out here, thanks everyone.:good::good:
I'm not sure you can be rooted on lollipop to take updates. That could be the problem. Try unrooting.
flash your current versions stock system.img. Lollipop updates don't patch files like the older updates, it does block level patching of the /system so you can't have any changes or the update will fail. On previous versions you could add files to /system and an update would patch the stock /system files and not care you had added other files. Now they patch at the block level so you can't add/delete files, you have to have a 100% untouched /system to take an update.
Download the factory image of what your phone is currently running. Fastboot flash the system.img and then take the OTA. You can then root after updated.
You could also just download the LMY47Z factory image and flash the bootloader, boot.img and system.img and be good to go (root again after). As long as you don't flash the userdata.img or wipe data you retain all your settings/apps/files.
vampire_8_7 said:
Hey guys
My N6 received the OTA update 2 days ago, I live in Australia and my device is rooted. I have downloaded the update then tried to restart and install for the first attempt, and off course it fails because am rooted. I have flashed the stock recovery.img and redownloaded it again, another failure. I have downloaded the OTA for the 3rd time and went to cache folder and took the "update.zip", then tried to flash it using TWRP and it failed. I have also tried the adb sideload and also failed. Below there is the pictures for the sideload procedure. What is puzzling me is that my phone build is "LMY47I" and what I receive is "LMY47Z" , so how can I apply this "update.zip" without wiping my system, I am already running on the stock image but it's rooted. I hope someone can help me out here, thanks everyone.:good::good:
Click to expand...
Click to collapse
You don't.
YOU obtain the full factory system image from https://developers.google.com/android/nexus/images
doitright said:
You don't.
YOU obtain the full factory system image from https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
tcrews said:
flash your current versions stock system.img. Lollipop updates don't patch files like the older updates, it does block level patching of the /system so you can't have any changes or the update will fail. On previous versions you could add files to /system and an update would patch the stock /system files and not care you had added other files. Now they patch at the block level so you can't add/delete files, you have to have a 100% untouched /system to take an update.
Download the factory image of what your phone is currently running. Fastboot flash the system.img and then take the OTA. You can then root after updated.
You could also just download the LMY47Z factory image and flash the bootloader, boot.img and system.img and be good to go (root again after). As long as you don't flash the userdata.img or wipe data you retain all your settings/apps/files.
Click to expand...
Click to collapse
Thanks tcrews
I still have the stock image for the 5.1 om my PC so if I used fastboot to flash the system and radio and bootloader, this won't delete any of my apps or my system??
vampire_8_7 said:
Thanks tcrews
I still have the stock image for the 5.1 om my PC so if I used fastboot to flash the system and radio and bootloader, this won't delete any of my apps or my system??
Click to expand...
Click to collapse
Hey doitright
So I can download the 5.1.1 (For Sprint, USC ONLY) (LMY47Z) even tho its saying US Only, and this was the one I received on the system update!!!
vampire_8_7 said:
Thanks tcrews
I still have the stock image for the 5.1 om my PC so if I used fastboot to flash the system and radio and bootloader, this won't delete any of my apps or my system??
Click to expand...
Click to collapse
To "restore" your system to stock, you just need to flash the system.img and recovery.img to take the OTA. To "update" your system to the next version with factory images you would flash bootloader, restart the bootloader, flash the radio, restart the bootloader then flash boot.img and system.img and then reboot the phone. Re-root after.
All Done
Thanks to everyone, all done now, and special thanks to "tcrews" all sorted out now mate, I used fastboot to flash 5.1 (recovery, bootloader, boot and system) then did the same thing for the 5.1.1. I didn't lose any data or apps all working perfectly fine. I had to "Root" the device after, then flashed the "Xposed Firmware". :good: :good:
Yes, thanks as well! I had this issue when the OTA showed up on my Nexus 6 yesterday. Did what vampire_8_7 indicated above, and everything is working with no loss of data or apps. Thanks everyone!
Hi Guys,
very sorry to bump this thread, but i've been trying for 2 days now to follow your instructions to update to 5.1.1 and its failing.
i have a rooted 5.1 using TeamWin software and custom ROM (LMY47D)
can i get a step by step on how to flash the 5.1.1 OTA ?
i tried to reflash 5.1 stock and it failed as well, no idea if i'm doing something wrong.
thanks in advance.
mar1nasr said:
Hi Guys,
very sorry to bump this thread, but i've been trying for 2 days now to follow your instructions to update to 5.1.1 and its failing.
i have a rooted 5.1 using TeamWin software and custom ROM (LMY47D)
can i get a step by step on how to flash the 5.1.1 OTA ?
i tried to reflash 5.1 stock and it failed as well, no idea if i'm doing something wrong.
thanks in advance.
Click to expand...
Click to collapse
You cannot flash the OTA. You can only flash stock. I also have no idea if you're doing something wrong. Probably though, that is usually the case.
vampire_8_7 said:
Hey guys
My N6 received the OTA update 2 days ago, I live in Australia and my device is rooted. I have downloaded the update then tried to restart and install for the first attempt, and off course it fails because am rooted. I have flashed the stock recovery.img and redownloaded it again, another failure. I have downloaded the OTA for the 3rd time and went to cache folder and took the "update.zip", then tried to flash it using TWRP and it failed. I have also tried the adb sideload and also failed. Below there is the pictures for the sideload procedure. What is puzzling me is that my phone build is "LMY47I" and what I receive is "LMY47Z" , so how can I apply this "update.zip" without wiping my system, I am already running on the stock image but it's rooted. I hope someone can help me out here, thanks everyone.:good::good:
Click to expand...
Click to collapse
- Fastboot erase system
- Fastboot flash system system.img
- Fastboot flash boot boot.img if you have a custom kernel
- Fastboot flash recovery recovery.img if you have a custom recovery
- Fastboot erase cache and then fastboot flash cache cache.img.
Reboot and sideload the OTA and that should do it because you still have have modified system files on your phone.
mar1nasr said:
Hi Guys,
very sorry to bump this thread, but i've been trying for 2 days now to follow your instructions to update to 5.1.1 and its failing.
i have a rooted 5.1 using TeamWin software and custom ROM (LMY47D)
can i get a step by step on how to flash the 5.1.1 OTA ?
i tried to reflash 5.1 stock and it failed as well, no idea if i'm doing something wrong.
thanks in advance.
Click to expand...
Click to collapse
Hey mate
The idea is to go complete stock before you flash any OTA, and this can be achieved by just flashing the "System.img" and the "bootloader.img" file to you device.
DON'T FORGET TO TAKE A FULL BACKUP Note: This warning above is more precaution thing, and this method never wiped any data but its good to have the backup always.
You need to download the official stock image for your device, if you have that's fine keep reading through.
Factory Images
You have to extract the image and get the "system.img" and "bootloader.img"
Copy and Paste the "System.img" and "bootloader.img" files in the fastboot folder.
Open the cmd as admin navigate to the directory where the fastboot resides, then start typing these commands.
fastboot flash bootloader bootloader-XXXX.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
fastboot flash system system.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
Now you have to copy (Boot.img , bootloader.img, system.img and the radio.img) from the OTA image you have and paste it in the fastboot folder, then you will run the previous 2 commands in addition to these 2 commands below.
fastboot flash radio radio-XXX-XXX.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
After performing this you should have 5.1.1 on your device without wiping any of your personal data or apps.
vampire_8_7 said:
...
Click to expand...
Click to collapse
Thanks a million for the step by step. i think my stock 5.1 is the issue. i'll download the factory image and try again now.
cheers,
EDIT: just finished, and it seems my old 5.1 image was crap. i downloaded a new factory image and did what you mentioned above. now running 5.1.1 and all my old data is there. thanks again, appreciate your time.
mar1nasr said:
Thanks a million for the step by step. i think my stock 5.1 is the issue. i'll download the factory image and try again now.
cheers,
EDIT: just finished, and it seems my old 5.1 image was crap. i downloaded a new factory image and did what you mentioned above. now running 5.1.1 and all my old data is there. thanks again, appreciate your time.
Click to expand...
Click to collapse
No Problems bro. Happy to hear that it worked. XDA is always the place where you can get help
another update for those using TWRP.
TWRP recovery 2.8.7.0 cannot decrypt data for recovery mode, and the 5.1.1 udpate comes encrypted. only way to decrypt is to factory wipe if your device is encrypted and the patternlock/pin doesnt work.
TWRP released 2.8.7.1 yesterday that fixes this issue. this saved me from factory wipe and starting from scratch. also no data needed to be wiped.
^^ just in case anyone is running into the same issue.
cheers,
mar1nasr said:
another update for those using TWRP.
TWRP recovery 2.8.7.0 cannot decrypt data for recovery mode, and the 5.1.1 udpate comes encrypted. only way to decrypt is to factory wipe if your device is encrypted and the patternlock/pin doesnt work.
TWRP released 2.8.7.1 yesterday that fixes this issue. this saved me from factory wipe and starting from scratch. also no data needed to be wiped.
^^ just in case anyone is running into the same issue.
cheers,
Click to expand...
Click to collapse
All official updates encrypt.
tcrews said:
To "restore" your system to stock, you just need to flash the system.img and recovery.img to take the OTA. .
Click to expand...
Click to collapse
Hi,
Can I ask for more details how to flash the system.img and recovery.img ? From where to download it and how to flash?
I have rooted Nexus 6 5.1 Verizon
Thanks
ikirilenko said:
Hi,
Can I ask for more details how to flash the system.img and recovery.img ? From where to download it and how to flash?
I have rooted Nexus 6 5.1 Verizon
Thanks
Click to expand...
Click to collapse
I always place these img`s in the /android/sdk/platform-tools/ folder, or extract them and right-click/shift copy to path. Then with cmd in fastboot erase system then flash system system.img and fastboot flash recovery recovery.img. Dowloadlink below in my signature Phantasmagoria and extract the downloaded file until you see the img`s.
gee2012 said:
Then with cmd in fastboot erase system then flash system system.img
Click to expand...
Click to collapse
Out of curiosity, why do you erase system first?
6.0.0 (MRA58N) for the Nexus 5 @ https://developers.google.com/android/nexus/images?hl=en
Reddit: https://www.reddit.com/r/Android/comments/3r95t2/android_60_november_security_update_images_are_out/
EDIT: Details at https://groups.google.com/forum/#!topic/android-security-updates/n1aw2MGce4E
So OTA usually comes out days after??
Sent from my Nexus 5 using XDA Free mobile app
I know this is just a security update, but can anyone confirm that the file transfer via USB MTP is working flawlessly?
Unlike this? ---> http://forum.xda-developers.com/google-nexus-5/help/considering-android-6-0-mtp-desktop-pc-t3218687
sutobe said:
I know this is just a security update, but can anyone confirm that the file transfer via USB MTP is working flawlessly?
Unlike this? ---> http://forum.xda-developers.com/google-nexus-5/help/considering-android-6-0-mtp-desktop-pc-t3218687
Click to expand...
Click to collapse
I've personally had no issues with the first 6.0 build on Windows 10 Pro x64, although only ever tried small files (<300MB)
Ok I made a Nandroid and installed 6.0 afterwards. File transfer worked for me now (don't know why it was so faulty before).....but there is still the thing with TWRP and TItanium Backup folders not showing up in Windows Explorer.
If I have a TWRP and / or Titanium Backup folder saved on my desktop's harddrive and want to move it to the phone's SD card the process fails while telling me that the folder already excists....but I can only see them via the phone's file explorer.
That means it is not impossible to move your backed up files to the SD card, it is just terribly awful. Always switch to MTP everytime you reconnect the phone with USB, then rename and move the backup-folders to the SD card and move their content to the proper backup folders (which you can't see in Windows) via a phone explorer.........who at Google had that great idea?
Any success rooting it? I tried the CF-Autoroot beta and last version of Chainfire's modified kernel, but got "no sim" errors.
FreemanAMG said:
Any success rooting it? I tried the CF-Autoroot beta and last version of Chainfire's modified kernel, but got "no sim" errors.
Click to expand...
Click to collapse
Yes. Modified boot.img attached in SuperSU beta thread... No problems.
GROGG88 said:
Yes. Modified boot.img attached in SuperSU beta thread... No problems.
Click to expand...
Click to collapse
Do you have a link? I do have the files from the first marshmallow release, But I'm not sure if you are talking about the latest SuperSU "systemless" beta
FreemanAMG said:
Do you have a link? I do have the files from the first marshmallow release, But I'm not sure if you are talking about the latest SuperSU "systemless" beta
Click to expand...
Click to collapse
I attached it in one of the last couple pages.
OTA failed for me. Using TWRP
fakitol said:
OTA failed for me. Using TWRP
Click to expand...
Click to collapse
Why do we keep having to repeat this?
You CAN NOT apply an OTA if you have modified the system in any way and/or you're using a different recovery. You can be unlocked. You can not be rooted. You can not apply an OTA via TWRP.
Yaz75 said:
Why do we keep having to repeat this?
You CAN NOT apply an OTA if you have modified the system in any way and/or you're using a different recovery. You can be unlocked. You can not be rooted. You can not apply an OTA via TWRP.
Click to expand...
Click to collapse
Because people are lazy and stupid at the same time often.
Sent from my Nexus 5 using Tapatalk
I got the security notification update but I have TWRP installed. I used NRT to Flash stock and unroot so am now down to a standard Nexus 5 with unlocked bootloader. I entered receovery mode and wiped cache for just in case then I tried the OTA install again but get no further than the message rebooting now. After a while it goes back to the restart and install message. Checked system and it shows October update. Any ideas what I can do. Trying to avoid wiping the phone, locking bootloader etc.
KC57 said:
I got the security notification update but I have TWRP installed. I used NRT to Flash stock and unroot so am now down to a standard Nexus 5 with unlocked bootloader. I entered receovery mode and wiped cache for just in case then I tried the OTA install again but get no further than the message rebooting now. After a while it goes back to the restart and install message. Checked system and it shows October update. Any ideas what I can do. Trying to avoid wiping the phone, locking bootloader etc.
Click to expand...
Click to collapse
Just flash the factory image but leave out the userdata.img file
EddyOS said:
Just flash the factory image but leave out the userdata.img file
Click to expand...
Click to collapse
Going to show my Noob quals here, which factory image, the security update? if so where would I find that and can I flash using NRT. Not a technology thicko but have only flashed images with NRT to now, did manage TWRP using ADB but that was a trial.
KC57 said:
Going to show my Noob quals here, which factory image, the security update? if so where would I find that and can I flash using NRT. Not a technology thicko but have only flashed images with NRT to now, did manage TWRP using ADB but that was a trial.
Click to expand...
Click to collapse
Easiest one is to use the latest MRA58N and then you've got the latest version but if you wanna use the previous one and then apply the OTA (to make sure it works) then you can do that as well. As for flashing it, just manually flash each image in fastboot but leave the userdata.img (as that will wipe your files). I do it in this order...
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase cache
fastboot format cache
fastboot reboot
That should do the job
Yaz75 said:
Why do we keep having to repeat this?
You CAN NOT apply an OTA if you have modified the system in any way and/or you're using a different recovery. You can be unlocked. You can not be rooted. You can not apply an OTA via TWRP.
Click to expand...
Click to collapse
Apologies for what is probably a dumb question but is there an easy repo of the contents of the OTA updates in flashable zip format?
EddyOS said:
Easiest one is to use the latest MRA58N and then you've got the latest version but if you wanna use the previous one and then apply the OTA (to make sure it works) then you can do that as well. As for flashing it, just manually flash each image in fastboot but leave the userdata.img (as that will wipe your files). I do it in this order...
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase cache
fastboot format cache
fastboot reboot
That should do the job
Click to expand...
Click to collapse
So does doing this equate almost to a "dirty flash" - i.e. I'm getting all the updates but not wiping any of my data/apps etc off the phone?
anyone a mirror for the 2,5 MB OTA file?
landwomble said:
So does doing this equate almost to a "dirty flash" - i.e. I'm getting all the updates but not wiping any of my data/apps etc off the phone?
Click to expand...
Click to collapse
Yes, but with official system files so you should be OK. Worst case scenario, backup data before doing anything in case you have to do a factory reset (e.g. if it shows 16GB on a 32GB device)
---------- Post added at 08:49 PM ---------- Previous post was at 08:49 PM ----------
hanschke said:
anyone a mirror for the 2,5 MB OTA file?
Click to expand...
Click to collapse
Don't need a mirror with the official Google server links - https://android.googleapis.com/pack...74e.signed-hammerhead-MRA58N-from-MRA58K1.zip