Related
I recently unlocked my Nexus 5's bootloader and flashed Android L on it, which wiped all my data. I just downloaded the Google image for Android 5.0.1 for my device from the Android site, and need someone to point me in the right direction on how to apply the update without wiping my user data. I just checked on my phone for an OTA update and it didn't find one. I have AT&T, but bought the phone from Google Play Store.
Edit the flash-all.bat and remove the "-w" bit in the "fastboot -w update image-hammerhead-lrx22c.zip" line
Delete the userdata.img in the image-hammerhead-lrx22c.zip file (you can do this in 7zip or the built-in Windows zip tool)
Flash as normal using the flash-all.bat once your phone is in the bootloader.
Just done the above myself and it has upgraded fine without losing my data.
ianm said:
Edit the flash-all.bat and remove the "-w" bit in the "fastboot -w update image-hammerhead-lrx22c.zip" line
Delete the userdata.img in the image-hammerhead-lrx22c.zip file (you can do this in 7zip or the built-in Windows zip tool)
Flash as normal using the flash-all.bat once your phone is in the bootloader.
Click to expand...
Click to collapse
Thanks for the quick response! I'll try this.
Edit: It worked!
You also could have extracted the image files and done
Code:
fastboot flash system system.img
fastboot flash radio radio.img
fastboot flash boot boot.img
rootSU said:
You also could have extracted the image files and done
Code:
fastboot flash system system.img
fastboot flash radio radio.img
fastboot flash boot boot.img
Click to expand...
Click to collapse
Are these the only .img files you need to flash? Why not the others? I know flashing userdata.img will erase your data but the others? Is nothing else updated, e.g. recovery or bootloader?
The factory image is to return it all to stock so you can start again but you only really need those three if you want to keep your custom recovery. Personally, I flash everything and set my phone up fresh with every factory image but then again most of my data is in the cloud these days so I don't mind wiping data
EddyOS said:
The factory image is to return it all to stock so you can start again but you only really need those three if you want to keep your custom recovery. Personally, I flash everything and set my phone up fresh with every factory image but then again most of my data is in the cloud these days so I don't mind wiping data
Click to expand...
Click to collapse
It worked great. Used the same method on my Nexus 7 2013 the other day sans flashing radio. I have too many apps so I gladly avoid the hassle of re-installing everything and signing in on 20+ different apps. I know I can use titanium or other methods to backup all data etc, but I think the fastboot method is the most convenient if you don't have limited bandwidth.
If someone want's a guide on how to use the non OTA fastboot method without loosing data I made a separate one here: http://forum.xda-developers.com/google-nexus-5/help/guide-how-to-update-5-0-to-5-x-loosing-t2975174
update to 5.0.1
I'm on root, stock rom and custom recovery. I got the notification for 5.0.1 update and I'm not sure how to do the update. Can I flash the image from TWRP custom recovery?
g33kos said:
I'm on root, stock rom and custom recovery. I got the notification for 5.0.1 update and I'm not sure how to do the update. Can I flash the image from TWRP custom recovery?
Click to expand...
Click to collapse
no you can not. You have to sideload the ota in the stock recovery. This is different than before. You also have to be stock recovery, system, kernel and radio
Sent from my Nexus 5 using XDA Free mobile app
I've got a Nexus 5 with Android 5.0. I've had it rooted and unlocked using SkipSoft Unified Android Toolkit. I recently got a notification for an OTA update for 5.0.1. When I tried to install it, it downloaded ok but upon restarting it dropped me into teamwin recovery menu with options for: Install, Wipe, Backup, Restore, Mount, Settings, Advanced, Reboot. Not knowing what to do I clicked on Reboot -> System which booted back into the phone. Nothing changed or got installed.
Does anyone know how I can apply the latest OTA update? Do I have to unroot first, apply and then re-root? Does the Toolkit have support for 5.0.1 rooting yet?
TIA
You must be 100% stock to update so yes, you need to fully unroot.
Though you should just fastboot flash the system.img and boot.img
Don't use toolkits. Do things manually. You can either flash SuperSU from recovery or use cf-auto root from a computer.
Its very easy, there is flashable 5.0 stock ROM, I dirty flashed, or you can do it like rootSU said via fastboot, root has been lost, then I flashed stock recovery via fastboot, there is thread for recoveries, then I upgraded via ota and flashed twrp via fastboot and flashed SuperSU to gain root and custom kernel.
My way is much quicker though as you flash 5.0.1 system and boot straight away. Nothing else.
rootSU said:
My way is much quicker though as you flash 5.0.1 system and boot straight away. Nothing else.
Click to expand...
Click to collapse
We will never understand why people even bother with OTAs regardless what we ever tell them
rootSU said:
You must be 100% stock to update so yes, you need to fully unroot.
Though you should just fastboot flash the system.img and boot.img
Don't use toolkits. Do things manually. You can either flash SuperSU from recovery or use cf-auto root from a computer.
Click to expand...
Click to collapse
Ok, I'm not 100% sure I understood everything you said. I've downloaded the 5.0.1 update from here: https://developers.google.com/android/nexus/images. Using 7zip, I noticed the system.img and boot.img is contained in the tgz file (along with several other files). Do I just extract just those two files? And then what do I do in Teamwin?
Will all my apps and data persist?
TIA
Techno79 said:
Ok, I'm not 100% sure I understood everything you said. I've downloaded the 5.0.1 update from here: https://developers.google.com/android/nexus/images. Using 7zip, I noticed the system.img and boot.img is contained in the tgz file (along with several other files). Do I just extract just those two files? And then what do I do in Teamwin?
Will all my apps and data persist?
TIA
Click to expand...
Click to collapse
Boot into bootloader
fastboot flash system system.img
fastboot flash boot boot.img
Boot into Lollipop
You didn't touch userdata.img so it doesn't touch the data partition, although a wipe is usually recommended anyways because it's a new version of Android.
Lethargy said:
Boot into bootloader
fastboot flash system system.img
fastboot flash boot boot.img
Boot into Lollipop
You didn't touch userdata.img so it doesn't touch the data partition, although a wipe is usually recommended anyways because it's a new version of Android.
Click to expand...
Click to collapse
Sweet, that worked a great. Thank you.
Hello everyone, I have a Moto G (2013) aka first generation Moto G & I live in India. I had unlocked my bootloader. I even flashed cwm touch via fastboot but it doesn't go to recovery mode at all. I get a black screen. I tried flashing the official TWRP 2.8.4.0 today, but I get a message that reads, "Partition size mismatch" & I'm stuck. The phone is usable & it boots up normally & I use it daily. But it is the recovery that is messed up. I tried updating to lollipop by ota but the device got stuck on a black screen once the ota was downloaded. I tried downloading the KitKat factory image, but the link is dead. Please, somebody help!! Thanks in advance!
Sent from my XT1033 using xda premium
The partition size mismatch error can be ignored, You get that error because the TWRP 2.8.4.0 is for the XT1032 and not the XT1033. To flash the OTA, you have to use the stock recovery only. Your system should not be modified (eg. It shouldn't be rooted, and if it had been rooted previously, you will have to unroot it.) To flash the stock recovery again, download the Asian XT1033 4.4.4 firmware and just flash the "recovery.img" from it. The flash the OTA. The numerous guides regarding this in the general section should help you.
I have a similar question.
I have unlocked bootloader & rooted moto g.
I received official OTA update today but its not installing. Do I need to lock bootloader or do something else to install the official OTA update?
Facing a similar issue. Updated the moto g and was successful. It was used for a couple of days before the error cropped up.
Now, it boots up but goes to a black screen after the boot animation. However, it still connects to the computer and I'm able to see the phone and its files in explorer. Beyond that, I can't interact with the phone because the screen is totally black.
Additionally, I can access the bootloader, but selecting 'factory' or 'recovery' isn't doing anything - just black screens everywhere.
The phone was perfectly fine for a few days after the update. (The phone is unrooted and unmodded and was running stock at lolipop update.)
Another thread suggests that I should
Code:
fastboot erase cache
fastboot erase userdata
Is that a viable course of action? Has anybody been able to recover from this issue?
pr.itdude said:
I have a similar question.
I have unlocked bootloader & rooted moto g.
I received official OTA update today but its not installing. Do I need to lock bootloader or do something else to install the official OTA update?
Click to expand...
Click to collapse
No need to lock. Unroot, reflash stock signed recovery and you should be good to go. Also undo any modifications you made to the filesystem and wiping /cache should help prevent errors.
---------- Post added at 02:42 AM ---------- Previous post was at 02:40 AM ----------
SoberDogs said:
Facing a similar issue. Updated the moto g and was successful. It was used for a couple of days before the error cropped up.
Now, it boots up but goes to a black screen after the boot animation. However, it still connects to the computer and I'm able to see the phone and its files in explorer. Beyond that, I can't interact with the phone because the screen is totally black.
Additionally, I can access the bootloader, but selecting 'factory' or 'recovery' isn't doing anything - just black screens everywhere.
The phone was perfectly fine for a few days after the update. (The phone is unrooted and unmodded and was running stock at lolipop update.)
Another thread suggests that I should
Code:
fastboot erase cache
fastboot erase userdata
Is that a viable course of action? Has anybody been able to recover from this issue?
Click to expand...
Click to collapse
Try fastboot erase cache, it shouldn't delete any of your data and it might be enough to get the device working again. You might want to wipe the dalvik-cache as well. If all else fails, since you can access you filesystem, backup all important files and do a factory reset.
skyguy126 said:
No need to lock. Unroot, reflash stock signed recovery and you should be good to go. Also undo any modifications you made to the filesystem and wiping /cache should help prevent errors.
Click to expand...
Click to collapse
Ok. Few more Q pls:
1. Reflashing stock recovery wipes system data & apps? After this my phone will be rooted or not? Any links where i can read more about it?
2. I have stock ROM but yes I installed xposed framework & few modules. Is it a filesystem modification?
3. Any other alternative to this?
pr.itdude said:
Ok. Few more Q pls:
1. Reflashing stock recovery wipes system data & apps? After this my phone will be rooted or not? Any links where i can read more about it?
2. I have stock ROM but yes I installed xposed framework & few modules. Is it a filesystem modification?
3. Any other alternative to this?
Click to expand...
Click to collapse
1. No it should not. If you had root before you will still have it. Search in the forum for more info.
2. Yes but you can easily uninstall xposed with the click of a button.
3. This is by far the easiest and safest method. I know of one alternative is to flash the ota update zip through custom recovery but you are on your own there.
skyguy126 said:
1. No it should not. If you had root before you will still have it. Search in the forum for more info.
2. Yes but you can easily uninstall xposed with the click of a button.
3. This is by far the easiest and safest method. I know of one alternative is to flash the ota update zip through custom recovery but you are on your own there.
Click to expand...
Click to collapse
ok so Here what i am planning:
1. Uninstall all modules & xposed framework
2. Unroot using supersu
3. Restore/reflash stock recovery (just recovery not whole firmware as I already have stock rom)
4. Install the update either manually via recovery or using auto install.
Am i on right path? Pls help me on step 3, any link or step-t-step guide? I couldn't find one, every post is abt restoring whole firmware.
TIA. Cheers !!
pr.itdude said:
ok so Here what i am planning:
1. Uninstall all modules & xposed framework
2. Unroot using supersu
3. Restore/reflash stock recovery (just recovery not whole firmware as I already have stock rom)
4. Install the update either manually via recovery or using auto install.
Am i on right path? Pls help me on step 3, any link or step-t-step guide? I couldn't find one, every post is abt restoring whole firmware.
TIA. Cheers !!
Click to expand...
Click to collapse
Yep you should be good good luck!!!
DISCLAIMER: I AM NOT LIABLE TO ANY DAMAGE THAT HAPPENS TO YOUR DEVICE BECAUSE OF DOING ANYTHING WRONG.
MOTO G4 PLUS [XT1643]
This is for those who had flashed a custom kernel on their stock ROM and now want to revert to stock.
REQUIREMENTS:
1. TWRP 3.0.3-n2 by @Shreps .
https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
This one is more updated/maintained than the official 3.0.2 version.
2. 7Zip Compression Utility:
Download and install on your PC. I use this as it gives the maximum ultra level compression. See Downloads below.
PROCEDURE:
1. Download and extract the TWRP.7z using 7Zip.
2. Place the TWRP folder it in the root directory of your INTERNAL STORAGE.
2. Just reboot TWRP once and choose Restore and then choose this: athene_93-14_boot
3. Swipe to restore.
NOTE: As a general recommendation for all zip installations and backup/restore using twrp, Wipe Cache and ART Cache before you Reboot to System.
4. You're DONE
DOWNLOADS:
Google Drive Link for the file:
https://drive.google.com/open?id=0B25DpDahxm52MDlBRlVqNElkaUE
7-ZIP Download Link:
http://www.7-zip.org/download.html
IF YOU WANT ENTIRE STOCK ROM ( TWRP BACKUP) VISIT THIS THREAD BY @Greekgodmerwyn .
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-moto-g4-plus-npj25-93-14-t3544601
HIT LIKE IF I HELPED YOU! :fingers-crossed: :good:
Hey I need the file bit it is in bin so give a alternative link
Can i install this to xt1644 retus?
Dont know bro I just want the 1643 one
dedik46 said:
Can i install this to xt1644 retus?
Click to expand...
Click to collapse
Not tried. Make additional backups and try. :good:
https://drive.google.com/open?id=0B25DpDahxm52MDlBRlVqNElkaUE
Not Found
Error 404
Please re-upload.
nextheart said:
https://drive.google.com/open?id=0B25DpDahxm52MDlBRlVqNElkaUE
Not Found
Error 404
Please re-upload.
Click to expand...
Click to collapse
Oh wait. Try this, @nextheart
https://www.androidfilehost.com/?fid=745425885120722570
@tywinlannister7 Thanks for quick reply.
As far as I can understand, this file should be flashed (restored) after restoring my TWRP back up of nougat stock rom taken in January-2017. Currently I am on RR-MM.
Shall I able to take OTA then?
nextheart said:
@tywinlannister7 Thanks for quick reply.
As far as I can understand, this file should be flashed (restored) after restoring my TWRP back up of nougat stock rom taken in January-2017. Currently I am on RR-MM.
Shall I able to take OTA then?
Click to expand...
Click to collapse
For OTA updates to work, you'd need a stock recovery on your device too; TWRP is a no go. Once you've restored your TWRP backup of your Nougat stock ROM (which hopefully may have the stock boot still), you can flash the stock recovery linked here https://forum.xda-developers.com/moto-g4-plus/how-to/how-to-ota-rooting-nougat-npj-25-93-14-t3601747
I imagine the easiest option is to flash the recovery in fastboot (same as you did with TWRP) using 'fastboot flash recovery recovery.img', then rebooting into recovery.
I think, though I've not tried it with a stock recovery, that you should be able to flash the recovery image in TWRP:
tap Install in the TWRP menu
Select 'install image's
Find your stock recovery image and select
Choose recovery as the image type
Flash and reboot to recovery.
Then, provided your system has a stock kernel, no modifications to your system and a stock recovery (bootloader doesn't matter), you should be able to update via OTA.
@echo92 Thanks for detailed guide.
I had flashed SuperSU on Nougat stock ROM, so stock boot might be affected. Am I right?
In short, I want to sell the device, so I want to return to stock.
nextheart said:
@echo92 Thanks for detailed guide.
I had flashed SuperSU on Nougat stock ROM, so stock boot might be affected. Am I right?
In short, I want to sell the device, so I want to return to stock.
Click to expand...
Click to collapse
You could have directly flashed the latest March 1 Security firmware via fastboot and lock your bootloader too.
tywinlannister7 said:
You could have directly flashed the latest March 1 Security firmware via fastboot and lock your bootloader too.
Click to expand...
Click to collapse
Thank you for pointing out.
Will I lose my IMEI or WIFI MAK or any thing else by fastboot method? Because I have read that some users are losing such things by fastboot method.
nextheart said:
Thank you for pointing out.
Will I lose my IMEI or WIFI MAK or any thing else by fastboot method? Because I have read that some users are losing such things by fastboot method.
Click to expand...
Click to collapse
Shouldn't create any such issues. Anyways, you can make an entire backup of the fsg and other partitions in twrp.
Yes, your data will be wiped though.
complete unrooting procedure for Mi A1 [Android Oreo]
1) remove all magisk modules
I mean untick all magisk modules and click on delete icon beside them
After this reboot your device
2) then open magisk manager and uninstall using completely uninstall option
3) then power off your device
4) go to fastboot mode
( by pressing vol- + power buttons simultaneously)
5) then unlock OEM using command
fastboot oem unlock
6) then check for current slot by using below command
fastboot getvar current-slot
7) then we should flash stock boot image
Using this command
fastboot flash boot_a boot.img
( If a is current slot )
Or
fastboot flash boot_b boot.img
( if current slot is b )
Boot image file : https://drive.google.com/file/d/1EsuVTv5zIrfhDH7VG6uSyTXUWPS7Dvfl/view?usp=drivesdk
8) then lock your OEM using command
fastboot oem lock
9) then reboot using command
fastboot reboot
Congratulations your device is unrooted successfully !!
Suggested vedios for mi A1 users
Iam maintaing my channel for mi A1 related vedios and other technical stuff
Do subscribe for latest updates
Rooting using magisk :
Complete gcam setup :
#reserved
Or..
1. download fastboot ROM from Xiaomi, run flash_all_except_storage.bat (or flash it in MiFlash)
Congrats, you have stock device!
This way you are sure that you have correct boot.img corresponding to your ROM (otherwise OTA update will fail) and not some "random file from the Internet".
Thank you very much!!!! Was looking for this in a pretty long time!!!
Nope. This boot.img doesn't work for me. After completing the instructions I'm just getting the Mi logo and then restart and it goes on forever. Maybe my system.img is bad??? Can anybody give me a link to a perfect Oreo fastboot ROM, becuase I found two: the one is my current ROM and the other one's system.img "cannot be extracted".
nicolasmart said:
Nope. This boot.img doesn't work for me. After completing the instructions I'm just getting the Mi logo and then restart and it goes on forever. Maybe my system.img is bad??? Can anybody give me a link to a perfect Oreo fastboot ROM, becuase I found two: the one is my current ROM and the other one's system.img "cannot be extracted".
Click to expand...
Click to collapse
This one works for me https://forum.xda-developers.com/showpost.php?p=75027522&postcount=63
Currently I'm rooted, but I fully booted right after flashing it without any mods and ROM started fine.
It will show some sparse warning during flashing, but it will complete the process OK.
Really? Is that what you're using? That's the exact one with the system.img errors. Nah, maybe a bad download.
nicolasmart said:
Really? Is that what you're using? That's the exact one with the system.img errors. Nah, maybe a bad download.
Click to expand...
Click to collapse
Yep, working fine (well, except the video recording bug, but that is most probably Xiaomi's fault). I downloaded this file as well (https://forum.xda-developers.com/mi-a1/development/tool-aosp-8-0-ql1515-dec-8-2017-t3722184) and extracted and compared both system.img files and they are exactly the same except the very small difference - second one allows encryption as optional (modified) vs. forced (stock) in fstab. It might cause bootloop if you try to lock the bootloader with that system. Try to redownload files from Mega..
_mysiak_ said:
Yep, working fine (well, except the video recording bug, but that is most probably Xiaomi's fault). I downloaded this file as well (https://forum.xda-developers.com/mi-a1/development/tool-aosp-8-0-ql1515-dec-8-2017-t3722184) and extracted and compared both system.img files and they are exactly the same except the very small difference - second one allows encryption as optional (modified) vs. forced (stock) in fstab. It might cause bootloop if you try to lock the bootloader with that system. Try to redownload files from Mega..
Click to expand...
Click to collapse
Hmm... redownloaded from Mega, says
Code:
error: cannot load '.\system.img'
Yes, I'm sure the file is in the current folder.
I tried a different fastboot.exe and the error is more specific this time :
Code:
target reported max download size of 534773760 bytes
Invalid sparse file format at header magi
Edit: The weird thing is that all other images from this Fastboot ROM install and work just fine. I've even used the boot.img from it. It works without any problems. The system is problematic.
nicolasmart said:
Hmm... redownloaded from Mega, says
Code:
error: cannot load '.\system.img'
Yes, I'm sure the file is in the current folder.
I tried a different fastboot.exe and the error is more specific this time :
Code:
target reported max download size of 534773760 bytes
Invalid sparse file format at header magi
Edit: The weird thing is that all other images from this Fastboot ROM install and work just fine. I've even used the boot.img from it. It works without any problems. The system is problematic.
Click to expand...
Click to collapse
First fastboot.exe is probably old, second one seems to be fine. Just wait until it starts flashing system.img, it will take a minute or two and will look like frozen (fastboot has to split file into 6 smaller ones, probably has something to do with missing sparse format), be patient and don't interrupt the process.
_mysiak_ said:
First fastboot.exe is probably old, second one seems to be fine. Just wait until it starts flashing system.img, it will take a minute or two and will look like frozen (fastboot has to split file into 6 smaller ones, probably has something to do with missing sparse format), be patient and don't interrupt the process.
Click to expand...
Click to collapse
THANK YOU!!!! IT WORKED!!! I AM NOW WITH LOCKED BOOTLOADER AGAIN! :victory: :victory: :victory:
nicolasmart said:
THANK YOU!!!! IT WORKED!!! I AM NOW WITH LOCKED BOOTLOADER AGAIN! :victory: :victory: :victory:
Click to expand...
Click to collapse
You saved me too.
presented error in the "no command" and did not accept the January update
Thank it worked for me!
After this unroot method i could install the january ota.
Then I used this https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654 method to root again
_mysiak_ said:
Or..
1. download fastboot ROM from Xiaomi, run flash_all_except_storage.bat (or flash it in MiFlash)
Congrats, you have stock device!
This way you are sure that you have correct boot.img corresponding to your ROM (otherwise OTA update will fail) and not some "random file from the Internet".
Click to expand...
Click to collapse
No need to uninstall modules and magisk
Just download & flash stock rom is enough to return to stock unrooted rom.
Is this you saying?
rkview37 said:
No need to uninstall modules and magisk
Just download & flash stock rom is enough to return to stock unrooted rom.
Is this you saying?
Click to expand...
Click to collapse
If you want to return to stock ROM and never use Magisk again, then you might want to uninstall Magisk first. But if you are only unrooting to apply OTA for example, it is enough to flash stock ROM and then reinstall Magisk - all your modules and settings will be kept.
_mysiak_ said:
If you want to return to stock ROM and never use Magisk again, then you might want to uninstall Magisk first. But if you are only unrooting to apply OTA for example, it is enough to flash stock ROM and then reinstall Magisk - all your modules and settings will be kept.
Click to expand...
Click to collapse
Actually sir
I have flashed patched boot image not just just boot
is your method work then
&Of course I just unroot to apply ota
rkview37 said:
Actually sir
I have flashed patched boot image not just just boot
is your method work then
&Of course I just unroot to apply ota
Click to expand...
Click to collapse
For OTA update, just reflash the latest stock ROM (keep data), apply OTA and root with Magisk again.
camerlengo said:
Thank it worked for me!
After this unroot method i could install the january ota.
Then I used this https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654 method to root again
Click to expand...
Click to collapse
Ok bro
_mysiak_ said:
Or..
1. download fastboot ROM from Xiaomi, run flash_all_except_storage.bat (or flash it in MiFlash)
Congrats, you have stock device!
This way you are sure that you have correct boot.img corresponding to your ROM (otherwise OTA update will fail) and not some "random file from the Internet".
Click to expand...
Click to collapse
Can u link me to the latest fastboot rom? , The link in the thread on the mi forums is too old I guess
AlwaysWin said:
Can u link me to the latest fastboot rom? , The link in the thread on the mi forums is too old I guess
Click to expand...
Click to collapse
http://ru.miui.com/thread-1308-1-1.html
This website is in Russian but download from this site
Rom is Oreo Jan official rom flash it using mi flash tool