Related
At the root file system on my Android phone, there's a file called default.prop. Right now that's a non-standard file because of CF-Auto-Root, but I want that file to be the stock version (1).
After what I have understood, /default.prop file is overwritten on every boot from a default.prop file within the boot partition.
My phone is rooted with CF-Auto-Root, but I've replaced the boot and bootloader partitions with factory image versions:
$ fastboot flash bootloader bootloader.img
$ fastboot flash boot boot.img
But still I get the non-stock default.prop file. What am I doing wrong?
(1) This is because I'm trying to upgrade to Android 5.1, and right now I'm getting an error because "this device has google/omni_hammerhead/hammerhead:4.4.4/KTU84P/eng.dees_troy.20150214.172938:eng/test-keys".
neu242 said:
(1) This is because I'm trying to upgrade to Android 5.1, and right now I'm getting an error because "this device has google/omni_hammerhead/hammerhead:4.4.4/KTU84P/eng.dees_troy.20150214.172938:eng/test-keys".
Click to expand...
Click to collapse
Don't bother messing with reverting everything just to update, it is extremely unlikely to work since as of Lollipop Google has changed the OTA method to check the sum of the entire partition rather than only what it cares about.
Download the 5.1 factory images, and flash system.img, boot.img, cache.img, radio.img and bootloader.img (don't flash userdata.img unless you want to wipe all your data), then boot into a custom recovery and flash the latest SuperSU (http://download.chainfire.eu/supersu).
Elluel said:
Download the 5.1 factory images, and flash system.img, boot.img, cache.img, radio.img and bootloader.img (don't flash userdata.img unless you want to wipe all your data), then boot into a custom recovery and flash the latest SuperSU (http://download.chainfire.eu/supersu).
Click to expand...
Click to collapse
Perfect, just what the doctor ordered. Thanks Elluel!
Many of you have trouble to install the last OTA-Update (SP 1.July) on their rooted devices.
Here is a quick guide to successfully install the OTA-Update without losing any of your data, only all changes you made to the system are restored to stock.
There is no need to relock your bootloader.
The reason the OTA-Update fails, is that one of the /boot, /system, /logo or /recovery partitions are changed.
For example the /recovery if you flashed it permanently or the /boot partition for rooting. Also the /system partition when you remove same build-in apps or install xposed and do not reverse the changes.
To restore the partitions you have to flash the stock ROM Images of the partitions.
That's all you have to do!
Most of you have the problem that they can't find the right stock ROM with the correct build-no. (or don't have access to the FileFactory folder).
In desperation you just download any stock ROM that contain "XT16xx" and flash it, without any idea what you are doing.
And that is the reason your phones lost the IMEI no.
There is also another problem with changing /system or /boot after the OTA-Update, because usually Motorola don't release a stock ROM image which include the OTA-Update when the next OTA-Update should be a major update to the next Android Version (6.0.1 -> 7.0). So when you make some changes to /system or /boot (rooting) after the OTA-Update you have no stock ROM image files of the current build-no and you have to flash the hole stock ROM image and erase all your data and take then two OTA-Updates (6.0 -> 6.0.1 -> 7.0) to get Android 7.0.
This is the reason you should make a TWRP backup of /system and /boot to restore it and then take the next OTA-Update, maybe to Android 7.0.
[GUIDE]
ONLY FOLLOW THIS GUIDE IF YOU HAVE THE CORRECT STOCK ROM IMAGE !!!
STOCK ROM IMAGE FILE NAME MUST CONTAIN YOUR CURRENT BUILD-NO AND SKU (e.g. XT162) OF THE PHONE !!!
I am not responsible for any damage or failure on your smartphone.
Requirements:
Correct Stock ROM Image for your phone -> FileFactory Moto G
Minimal ADB & Fastboot
Motorola Drivers
TWRP - Custom Recovery
1a. If you get the OTA-Update notification
If you are rooted and the OTA-Update notification pops up, download the update and hit the "later" button. Go with your fav. Filebrowser to:
Code:
/data/data/com.motorola.ccc.ota/app_download
and copy the OTA-Update "Blur_Version.2....." file to your SD-Card.
Go to 2. ↓
1b. If you don't get the OTA-Update notification because you already try to install it and get "error 7"
First option is to wait and drink some cups of tea till the notification popup again and try 1a. ↑
Second option is to go to 2. ↓, but then you have no root access till the notification popup up again.
2. Restore the stock ROM images
Extract only the boot.img, logo.bin, recovery.img, system.img_sparsechunk.0 to .7 files to the MADB&FB folder.
Connect your phone to your PC and open MADB&FB, check the connection with:
Code:
adb devices
return should include your "serial-no" and "device".
Reboot into bootloader with:
Code:
adb reboot-bootloader
and check again with:
Code:
fastboot devices
return should be "serial-no" and "fastboot".
Flash the partitions with:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
After every command should be a return with "OKAY".
Reboot your Phone with:
Code:
fastboot reboot
After reboot all your data is still there and you can sideload the OTA-Update, if the OTA-Update notification has not already appeared.
3. Sideload from SD-Card
Reboot into recovery:
Code:
adb reboot recovery
After few seconds the dead "Android" should appear with "No command."
HOLD "Power" and then HOLD "VOLUME UP" for 2-1 seconds and release. Now you are in "Android Recovery".
Select "Apply update from SD card" and choose your "Blur_Version.2..." file.
After 20-30 min you get "success" message and select "Reboot system now".
4. Make a backup of /system, /boot, /recovery and /logo
Before you can make some further changes on your /system, /boot, /recovery and /logo, you should backup these partitions for the next OTA-Update.
Follow all steps in the Guide to root systemless -> [ROOT][GUIDE] Systemless Rooting with SuperSU 2.78 , which include the TWRP backup (/system and /boot).
Then come back here and install on your rooted phone -> Partitions Backup & Restore.
Select "LOGO" and "RECOVERY" and change Settings to "Raw partitions image (img)" and save it on your SD-Card.
Now you have all partitions as a backup for the next OTA-Update. So when the next update is coming, you have to flash /logo and /recovery and then restore your TWRP backup and you are able to install the update without issues.
Have Fun and don't pay attention to my writing errors
Bender1987 said:
Many of you have trouble to install the last OTA-Update (SP 1.July) on their rooted devices.
Here is a quick guide to successfully install the OTA-Update without losing any of your data, only all changes you made to the system are restored to stock.
You can root your phone again with this GUIDE after the update -> http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
There is no need to relock your bootloader.
Click to expand...
Click to collapse
I used this procedure a couple of days ago and it worked flawlessly. When I rebooted after flashing all of the stock files, my OTA update notification was there waiting for me to select "Install". I did and it installed without issues.
What is surprising to me is how many people try it with the wrong firmware and then are surprised when they screw up their phones.
I was so close!!! lol, didn't realize they checked /logo for modifications. Was about to completely wipe everything to get the update to apply. Glad I checked xda before doing so as all I was missing was flashing stock logo.img (restoring system, recovery and boot I had already tried). Thanks Bender1987 for the easy guide.
I have the 64GIG 4G plus (XT-1644)
Hi @Bender1987,
Thank you for your guides, they are very helpful. I've already unlocked, rooted without flashing twrp, uninstalled some system apps and flashed xposed using Flashfire on my xt1642, and eveything is running fine so far. So, when an OTA update is available (hopefully nougat!) will I receive the notification? Or does the rooting stop even OTA notifications? Thanks!
@pblasi
You already received the OTA-Update with SP 1.July? If yes, i think the next OTA-Update should be Android 7.0.
Bender1987 said:
@pblasi
You already received the OTA-Update with SP 1.July? If yes, i think the next OTA-Update should be Android 7.0.
Click to expand...
Click to collapse
I just got my xt1642 a week ago. It already came with build number: MPJ24.139-48 which I think is the latest, so I haven't received any OTA update yet.
@pblasi
the current build-no is MPJ24.139-63 with Security Patch 1.July.
I add "TWRP backup" which is very important for the next OTA-Update, maybe Android 7.0.
Bender1987 said:
@pblasi
the current build-no is MPJ24.139-63 with Security Patch 1.July.
I add "TWRP backup" which is very important for the next OTA-Update, maybe Android 7.0.
Click to expand...
Click to collapse
Well, I spent 2 days without touching the phone before unlocking/rooting and didn't receive this ota-update. Maybe it is not available for my version (32gb, 3gb ram, xt1642)...
If I didn't flash twrp, I guess I won't need to restore it, right? Anyway, I made the full backup following your instructions. In which partition is stock twrp included? Boot? Thanks.
Backup with TWRP only cover system, boot, cache and data partition, that means I have to add some steps to get a backup from logo and recovery -_-
Maybe tomorrow.
Bender1987 said:
Backup with TWRP only cover system, boot, cache and data partition, that means I have to add some steps to get a backup from logo and recovery -_-
Maybe tomorrow.
Click to expand...
Click to collapse
Let me know if I understood it right. I made a TWRP backup of untouched boot, system and data, rooted and installed xposed without flashing TWRP and without changing logo.bin. Then I should be able to install next OTA update if I previously restore my copies of boot and system in TWRP. Right? No need to flash stock images in this case? Thanks!
@pblasi jep you are right
Xt1644 not play nice with adb nor does it go into recovery it just reboots when I hold the buttons...or it stays on no command
All devices have stock recovery on it. I tried it again, when you see the dead Android -> HOLD POWER and then HOLD VOLUME UP for 2-3 sec. -> release VOLUME UP and still HOLD POWER
https://www.youtube.com/watch?v=SuOrl7Q4JY8
at 1:58.
When I flash the files, for the boot and recovery I get a warning that the "image not signed or corrupt". Eventually it is written... but is that normal?
mfastboot flash recovery recovery.img
sending 'recovery' (16484 KB)...
OKAY [ 0.531s]
writing 'recovery'...
Image not signed or corrupt
OKAY [ 0.153s]
finished. total time: 0.684s
Click to expand...
Click to collapse
@SoNic67
Maybe it is not the correct stock rom?
Hmm, it was DL from the usual place, but true, I am not 100% sure about it. However, it "works" but I don't get the OTA.
I am DL now the newer full FW.
LE: That latest full FW worked. I had to reinstall all my apps from backup but...
Weird thing is that before my imei disappeared I was getting the ota updates
Sent from my 6045X using Tapatalk
@Bender1987 I have a TWRP backup of unmodified Stock ROM XT1643, so now to install OTA do I just have to flash the nandroid backup & then flash stock recovery to get ota updates? If so then how can I go about flashing stock recovery. Thanks in advance mate
@Amit_timA
TWRP only backup /system and /boot, to restore recovery you must flash it from a stock rom image. If all partitions are stock after restoring you can get the OTA-Update.
Bender1987 said:
@Amit_timA
TWRP only backup /system and /boot, to restore recovery you must flash it from a stock rom image. If all partitions are stock after restoring you can get the OTA-Update.
Click to expand...
Click to collapse
Will try
What's up all. So I have a Verizon pixel rooted on 7.1. I want to sideload 7.1.1 but don't want lose the ability to re root etc. Just wanna make sure I have he steps down.
-flash back to stock boot image
-sideload 7.1.1 ota
-flash twrp
-flash root
Am I missing anything??
You could also flash back to stock boot image, boot up and take the OTA actually over the air.
Also, don't flash TWRP initially, just boot TWRP, flash twrp from inside twrp, reboot into recovery, then finally flash root (make sure to read the twrp rc1 thread, post #2) reboot to let root finish, and done. (unless you want a custom Kernel, then do this very last.
After doing a twrp backup and backing up the entire device, I used this method to update with twrp and root installed. I did not lose data.
Afterwards you will need to install TWRP and root.
mruno said:
After doing a twrp backup and backing up the entire device, I used this method to update with twrp and root installed. I did not lose data.
Afterwards you will need to install TWRP and root.
Click to expand...
Click to collapse
Ok that looks easy enough. What is the command you typed to flash the file after its modified?
computercarl said:
You could also flash back to stock boot image, boot up and take the OTA actually over the air.
Also, don't flash TWRP initially, just boot TWRP, flash twrp from inside twrp, reboot into recovery, then finally flash root (make sure to read the twrp rc1 thread, post #2) reboot to let root finish, and done. (unless you want a custom Kernel, then do this very last.
Click to expand...
Click to collapse
This sounds like the easiest way. Where do i get the stock boot image from? Do i extract it from the factory image zip file? And then once I get it what is the command I'd use to flash it?
https://www.androidfilehost.com/?fid=529152257862669140 is nde63p's boot.img. If you are on something else, you can extract it's boot.img from the factory image, there's a boot file in there. Fastboot boot <img file name> will boot it, then you can take the ota, reboot because the ota needs to finish. copy twrp.zip on to sd card, (were going to need it in a minute!) then fastboot boot twrp3020rc1.img the same way. From twrp, flash the zip. tell twrp to reboot into recovery. it will reboot into twrp, from the recovery (Or dont flash the zip, you dont have to, some prefer to remain on stock recovery) and then flash SU SR5 (How to install SuperSU SR5 on TWRP RC1: Before flashing the zip, in TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it. ) then finally flash a kernel. If you are going to flash root, might as well flash ElementalX 1.01 kernel from twrp. Hope that is a bit more breakdown.
computercarl said:
https://www.androidfilehost.com/?fid=529152257862669140 is nde63p's boot.img. If you are on something else, you can extract it's boot.img from the factory image, there's a boot file in there. Fastboot boot <img file name> will boot it, then you can take the ota, reboot because the ota needs to finish. copy twrp.zip on to sd card, (were going to need it in a minute!) then fastboot boot twrp3020rc1.img the same way. From twrp, flash the zip. tell twrp to reboot into recovery. it will reboot into twrp, from the recovery (Or dont flash the zip, you dont have to, some prefer to remain on stock recovery) and then flash SU SR5 (How to install SuperSU SR5 on TWRP RC1: Before flashing the zip, in TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it. ) then finally flash a kernel. If you are going to flash root, might as well flash ElementalX 1.01 kernel from twrp. Hope that is a bit more breakdown.
Click to expand...
Click to collapse
I extracted the boot.img and put in in my fastboot folder, but when I go to flash it it's saying file not found?? I named it boot.img and am typing fastboot flash boot boot.img. I've also tried fastboot boot boot.img and get the same message.
What am i doing wrong? Could I have the wrong boot image??
mpetruzz said:
Ok that looks easy enough. What is the command you typed to flash the file after its modified?
Click to expand...
Click to collapse
just double click the .bat file and it will perform all of the commands. the first boot afterwards will take a few mins.
How to update your phone even after unlocking your phone without losing data in Lenovo K8 Plus?
There is a pretty simple trick for those who wanted to update to latest firmware & already unlocked their device.
First unroot & if you flashed xposed then xposed uninstaller too then use fastboot to flash stock recovery, boot & system & then do the OTA update & Voila your data will not loose and you just get update.
To do it download stock firmware click below
HTML:
https://drive.google.com/uc?id=1YexKxunNYF_RemzFmvHpoSgp8eELebqY&export=download
Password:-
[email protected] Developers
Extract this firmware.
Then you'll find several files there just copy system.img, boot.img, recovery.img to adb folder and then put your phone in fastboot mode and then type:-
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
After this power it up download the update and install it.
Note:- This trick is only tried on manning as of now. But I'm pretty sure that it'll work on marino too.
Credits:- Dhruv , Prem & Me?
Thanks man
Any guides available for this latest OTA security update to preserve or restore root after applying?
Haven't yet done this on a 4a. Last did something similar on a Pixel 3a, but don't want to risk assuming the steps are the same, or even similar.
Anyone succesfully applied the security update yet and been able to restore Magisk?
This is what i did:
1. download both the full OTA file and the factory image file.
2. extract the boot.img from the factory image
3. in magisk patch the extracted boot image, copy back to PC
4. apply update in recovery - adb sideload ota_file.zip
5. reboot to bootloader
6. flash your rooted boot image from step 3
7. reboot phone.
8. i failed safety net and had to install this module through magisk - https://github.com/kdrag0n/safetynet-fix
I downloaded and installed the Jan OTA before realizing the Magisk inactive slot trick was broken :-(
Instead of restarting (and losing root) I patched the latest booot.img, restarted to fastboot, flashed the patched boot... Now when I try to restart it's the black google screen for a while, then back to fastboot with "no valid slot to boot" massage. Any advice on how to fix this? Or if it can't be fixed, best way to start fresh with rooted factory rom? Thanks!
Just try to flash both slots:
fastboot flash boot_a boot.root.sunfish-rq1a.210105.002.img
fastboot flash boot_b boot.root.sunfish-rq1a.210105.002.img
mrpeters said:
Any guides available for this latest OTA security update to preserve or restore root after applying?
Haven't yet done this on a 4a. Last did something similar on a Pixel 3a, but don't want to risk assuming the steps are the same, or even similar.
Anyone succesfully applied the security update yet and been able to restore Magisk?
Click to expand...
Click to collapse
Yea its all basically the same procedure on all A/B devices today and Magisk!
Meth0d said:
Just try to flash both slots:
fastboot flash boot_a boot.root.sunfish-rq1a.210105.002.img
fastboot flash boot_b boot.root.sunfish-rq1a.210105.002.img
Click to expand...
Click to collapse
Thanks so much for the suggestion. Unfortunately that didn't work, still was getting to the black google screen for a couple min and then back to fastboot.
So I used google's flash link to install the newest version of stock ROM via chrome browser, and it worked, my data was preserved as well! Root was lost.
In case anyone else had this problem, when I went to re-root using fastboot flash boot (patched img) I was getting:
FAILED (remote: Failed to write to partition Not Found)
So I flashed as you described above to boot_a and boot_b and IT WORKED! THANK YOU!!