(sorry for my bad english I'm french )
Hi everybody,
I have received a new Nexus 6 32GB... No, sorry, a 64GB model (thanks to my resailer.. he make a mistake in the command, so I have won 32GB more! ).
But, I have few software problems with it...
At each OTA update, I get an error (at the robot opened screen). With almost all versions. This error get me a bootloop after update...
So I must to flash the official Google Image manually, partition by partition (else with NRT, I get an error at system writing step... I don't know why).
When I have fixed Android, finally, I have only.... 23.03 GB... With all versions.
So I must resize it in TWRP at each update (OTA or not).
For the last update, my bootloader have displayed at boot "Your device is corrupted. Blah blah blah..."
I actually make a new OTA update (6.1 I think). But I have an error one more time...
But I have no bootloop this time. The system reboot perfectly but in the old version. And few minutes later, the OTA is notified... Etc etc.
But, if a new system update is available, do you think I will get the same problems?
My system seems to be clean now... But during my multiple trys, my system has been clean too...
Without that, all is good and functionnal. Android, Wifi, LTE, screen, sound..... All!
This is very mysterious... Mostly for a new phone, non-rooted.
I did not want to root it while Google support it, but without root, my phone would still be blocked. That's not normal.
Should I be worried about it?
Thanks everyone!
1. Learn how to use ADB and Fastboot. Toolkits may get the job done, but you learn nothing in using them.
2. If flashing individual images from the system image, NEVER flash userdata.img as it resets your storage to 32GB. Formatting your internal storage using ADB, Fastboot, or in TWRP will restore the missing storage.
3. The system corruption message likely will disappear after you format internal storage and flash the stock images from Google. It will return however if you modify /system by adding files. To permanently remove it requires a custom kernel.
4. This a developer phone. You should be able to root it without losing the warranty.
Strephon Alkhalikoi said:
1. Learn how to use ADB and Fastboot. Toolkits may get the job done, but you learn nothing in using them.
2. If flashing individual images from the system image, NEVER flash userdata.img as it resets your storage to 32GB. Formatting your internal storage using ADB, Fastboot, or in TWRP will restore the missing storage.
3. The system corruption message likely will disappear after you format internal storage and flash the stock images from Google. It will return however if you modify /system by adding files. To permanently remove it requires a custom kernel.
4. This a developer phone. You should be able to root it without losing the warranty.
Click to expand...
Click to collapse
First thanks for your answer!
Oh yes for the 1 and the 4, my precedent phone is a Nexus 4, I know these phones and the steps to root/unroot/flash custom rom/recovery etc.. ^^ (I have made that a looooooot of times on my N4 without any problem, with and without NRT)
And this is for that I am surprised by the bad reaction of my Nexus 6 to this simple actions I request to it. (flashing image files)
I don't make anything I don't know, I am scared to brick my phone because I have made something that I master.
Yes I have forgot this point about userdata.img... But this is not a problem, I have resized my partition after flashing my phone with TWRP =)
The point that are interesting for me is the third point. I want to flash a stock image from Google. It's my goal. (I will flash custom ROM when Google will have stopped the update support)
In fact, my principal big problem is why the OTAs have been failed whereas I just start my phone, out of the box, with no modification and no root.
I'm not a specialist but for me, this is not normal when the phone is out of factory.
I will retry to flash another factory image from Google. This time with the flash-all script.
Thanks =)
Kermi78 said:
(sorry for my bad english I'm french )
Hi everybody,
I have received a new Nexus 6 32GB... No, sorry, a 64GB model (thanks to my resailer.. he make a mistake in the command, so I have won 32GB more! ).
But, I have few software problems with it...
At each OTA update, I get an error (at the robot opened screen). With almost all versions. This error get me a bootloop after update...
So I must to flash the official Google Image manually, partition by partition (else with NRT, I get an error at system writing step... I don't know why).
When I have fixed Android, finally, I have only.... 23.03 GB... With all versions.
So I must resize it in TWRP at each update (OTA or not).
For the last update, my bootloader have displayed at boot "Your device is corrupted. Blah blah blah..."
I actually make a new OTA update (6.1 I think). But I have an error one more time...
But I have no bootloop this time. The system reboot perfectly but in the old version. And few minutes later, the OTA is notified... Etc etc.
But, if a new system update is available, do you think I will get the same problems?
My system seems to be clean now... But during my multiple trys, my system has been clean too...
Without that, all is good and functionnal. Android, Wifi, LTE, screen, sound..... All!
This is very mysterious... Mostly for a new phone, non-rooted.
I did not want to root it while Google support it, but without root, my phone would still be blocked. That's not normal.
Should I be worried about it?
Thanks everyone!
Click to expand...
Click to collapse
Next time you flash and go into twrp make sure to select the "leave system read-only" option. Otherwise twrp will patch /system to survive a reboot and any modification to /system will break the next ota.
Kermi78 said:
...
But, if a new system update is available, do you think I will get the same problems?
Click to expand...
Click to collapse
Flash the latest TWRP 3.0 and the lite stock ROM of @Danvdh. This ROM has all you need, including root and OTA.
StykerB said:
Next time you flash and go into twrp make sure to select the "leave system read-only" option. Otherwise twrp will patch /system to survive a reboot and any modification to /system will break the next ota.
Click to expand...
Click to collapse
I have tried this. Thank you for this tip. I did not know Bootloader and OTAs fail depends of /system state. (I have never modified official google image. If I modify a device, it's with a custom rom like CM for example. Without my problem at the first start I would not have modify anything on my phone)
First, I don't have the bootloader message, that's a half good news
I download actually the MRA58N OTA update. Crossing fingers! =)
NLBeev said:
Flash the latest TWRP 3.0 and the lite stock ROM of @Danvdh. This ROM has all you need, including root and OTA.
Click to expand...
Click to collapse
My goal is to use the official Google Nexus Factory Images with official bootloader, etc.... Exactly the state of a normal Nexus out of the box.
But thank you. In last resort I will think of your tip.
StykerB said:
Next time you flash and go into twrp make sure to select the "leave system read-only" option. Otherwise twrp will patch /system to survive a reboot and any modification to /system will break the next ota.
Click to expand...
Click to collapse
So after my last try of OTA, 2 times, the update has been succeded!
Just thanks a lot! :good:
I notify this thread resolved
Kermi78 said:
My goal is to use the official Google Nexus Factory Images with official bootloader, etc....
Click to expand...
Click to collapse
Than you can't use layers. You have to live with the white Google ui, battery drain and hurting eyes.
NLBeev said:
Than you can't use layers. You have to live with the white Google ui, battery drain and hurting eyes.
Click to expand...
Click to collapse
Oh no that's good for me, I love Android Stock and I hate layers
For the battery... You see, my last phone was a Nexus 4. So the battery life of Nexus 6 is so wonderful for me!
In all cases, my phone is now stock and functionnal. Just that I want for the moment... I will see later for install other roms on it
I want to be simple things.
Kermi78 said:
(sorry for my bad english I'm french )
Hi everybody,
I have received a new Nexus 6 32GB... No, sorry, a 64GB model (thanks to my resailer.. he make a mistake in the command, so I have won 32GB more! ).
But, I have few software problems with it...
At each OTA update, I get an error (at the robot opened screen). With almost all versions. This error get me a bootloop after update...
So I must to flash the official Google Image manually, partition by partition (else with NRT, I get an error at system writing step... I don't know why).
When I have fixed Android, finally, I have only.... 23.03 GB... With all versions.
So I must resize it in TWRP at each update (OTA or not).
Click to expand...
Click to collapse
DON'T INSTALL THE userdata.img file and this won't happen.
Related
So I received a notification to download the 5.1 update this morning on my rooted Nexus 6. I proceeded to click download and then install.
However, due to that I had TeamWin recovery installed the update failed on reboot. (didn't even try to install)
Now when I click on "Check for updates" in About in System Settings menu. It says that there are no new updates??? Even though it failed to install.
Does anyone know where the update is stored on the device before installation? Maybe i need to remove it before it will try and update again? (now that i have flashed stock recovery)
Any help would be very appreciated.
You need to unroot too.
Ota can be downloaded online.
d1wepn said:
So I received a notification to download the 5.1 update this morning on my rooted Nexus 6. I proceeded to click download and then install.
However, due to that I had TeamWin recovery installed the update failed on reboot. (didn't even try to install)
Now when I click on "Check for updates" in About in System Settings menu. It says that there are no new updates??? Even though it failed to install.
Does anyone know where the update is stored on the device before installation? Maybe i need to remove it before it will try and update again? (now that i have flashed stock recovery)
Any help would be very appreciated.
Click to expand...
Click to collapse
Once you remove root, try pulling your Sim and rebooting. Let the phone sit, without Sim, and see if update reappears.
rootSU said:
You need to unroot too.
Ota can be downloaded online.
Click to expand...
Click to collapse
I was hoping to use the factory OTA update method for a change. (Always manually update) But might just be easier.
Downloading OTA now. Thanks for the advice rootSU
Evolution_Freak said:
Once you remove root, try pulling your Sim and rebooting. Let the phone sit, without Sim, and see if update reappears.
Click to expand...
Click to collapse
Might give this a try first. Worth a shot. Cheers mate.
OTA update downloads to system/cache folder ... It may get deleted soon after you try installing and restart the phone. You need rooted phone and a file explorer like es file explorer for accessing system folder.
Sent from android one lollypop 5.1
---------- Post added at 12:47 AM ---------- Previous post was at 12:38 AM ----------
Check first whether you have it in your phone already. Rooted phone go to /cache folder you'll find something.Zip there.
Ok so i managed to get the phone to download the OTA again and attempted to install it again. This time with stock recovery.
Everything was looking good but it fails with "error" below the android logo.
Any ideas?
Sorry I can't help you. I don't want that AT&T 5.1 update. So I did what you did and hit install. It of course didn't. I use TWRP also. But the damn 5.1 update is back!
Tappin from my Nexus 6
Any reason you want the OTA? you can install the factory image from here and get the same result without mucking around...
https://developers.google.com/android/nexus/images
Gage_Hero said:
Any reason you want the OTA? you can install the factory image from here and get the same result without mucking around...
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
You only need to flash the system.img file within the Google image using fastboot.
After that, boot into TWRP and reflash SuperSU, XPosed, and anything else you've flashed that resides in /system.
Wipe caches and reboot. Easy, and no app or data loss.
Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
um.. you are quite a bit late. this is an old thread, look at the dates. you responded to a question thats 6 month old.
liquidzoo said:
You only need to flash the system.img file within the Google image using fastboot.
After that, boot into TWRP and reflash SuperSU, XPosed, and anything else you've flashed that resides in /system.
Wipe caches and reboot. Easy, and no app or data loss.
Click to expand...
Click to collapse
Except, to be more complete, it might be a good idea to flash everything except data and boot - that is, in case changes are made to radio or anything else, but if changes are done to boot and are required for system or kernel and you don't put stock boot, you're kinda screwed (you'd need a different version of twrp in this case and it probably won't be out).
My point, there really is no complete way to know if flashing just system is enough to get all the security updates unless you look at what the update replaces. That's why I'm looking for the ota.zip
Rocky1988 said:
Except, to be more complete, it might be a good idea to flash everything except data and boot - that is, in case changes are made to radio or anything else, but if changes are done to boot and are required for system or kernel and you don't put stock boot, you're kinda screwed (you'd need a different version of twrp in this case and it probably won't be out).
My point, there really is no complete way to know if flashing just system is enough to get all the security updates unless you look at what the update replaces. That's why I'm looking for the ota.zip
Click to expand...
Click to collapse
And thankfully Google put version numbers to the other files so takes about 15 seconds to realise you only need to flash system. If a change was made to radio you can still flash in exactly the same way as the system and not lose data...
Amos91 said:
And thankfully Google put version numbers to the other files so takes about 15 seconds to realise you only need to flash system. If a change was made to radio you can still flash in exactly the same way as the system and not lose data...
Click to expand...
Click to collapse
How do you check version numbers for the other files? This may be what I'm after!
Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
I'm unable to find the latest update in the /system folder (/system/cache doesn't exist on my device) or the /cache folder either.
/data/data/com.google.android.gms/app_download/update.zip
d1wepn said:
Ok so i managed to get the phone to download the OTA again and attempted to install it again. This time with stock recovery.
Everything was looking good but it fails with "error" below the android logo.
Any ideas?
Click to expand...
Click to collapse
Use Flashify to install OTA updates instead.
At last i found it
I have clock work recovery installed on my phone. It refuses to update my OTA factory software update, i searched for it and installed it manually. It was in /data/data/com.tinno.systemupdate/files/googleota/0/update.zip
I have a nexus 6. I have been using custom ROMs from the days of xperia mini pro. Never had a Nexus before. I want to have root in my nexus 6 for ad blocking cereberus and more. But this time I don't want custom ROMs. I just need the OTA's. I know OTA's dont happen automatically after root. So please tell me should I root and put a custom recovery, Or just root for manually updating the OTA's. Where can I get all the OTA's ?? I know it's a lot of questions.. Please.
Quick answer: Isn't going to happen.
Reason: Lollipop wont install OTA if you modify /system, because it is now written as a block, unlike previous versions of android.
IF you root, you have modified /system.
Consequence: you will not update by OTA while rooted. It will fail.
Possible workaround: You can however AFAIK, unroot and then take an OTA, but I'll let others confirm this, please don't take me saying it as factual.
Factory image flash: always works, but you have to await the release after the updates.
mad_rulzzz said:
I have a nexus 6. I have been using custom ROMs from the days of xperia mini pro. Never had a Nexus before. I want to have root in my nexus 6 for ad blocking cereberus and more. But this time I don't want custom ROMs. I just need the OTA's. I know OTA's dont happen automatically after root. So please tell me should I root and put a custom recovery, Or just root for manually updating the OTA's. Where can I get all the OTA's ?? I know it's a lot of questions.. Please.
Click to expand...
Click to collapse
FWIW: I would recommend that you:
1) Unlock bootloader
2) Decide if you want uncrypted kernel, or not (since it wipes data, just like unlocking bootloader).
3) Fastboot flash TWRP recovery.
4) Download SuperSU .zip and flash it in recovery.
5) Now, when a new OTA comes out, they usually show up here > http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493
6) You can download your current factory image here > https://developers.google.com/android/nexus/images
7) Unzip your current factory image. Fastboot flash the system.img and that will unroot and restore the stock recovery.
8) Fastboot flash the stock boot.img if you have a custom kernel (or an unencrypted stock kernel).
9) Relax and wait for the OTA.
RW-1 said:
Quick answer: Isn't going to happen.
Reason: Lollipop wont install OTA if you modify /system, because it is now written as a block, unlike previous versions of android.
IF you root, you have modified /system.
Consequence: you will not update by OTA while rooted. It will fail.
Possible workaround: You can however AFAIK, unroot and then take an OTA, but I'll let others confirm this, please don't take me saying it as factual.
Factory image flash: always works, but you have to await the release after the updates.
Click to expand...
Click to collapse
I knew about the OTA failing due to the system partition getting changed while rooting. I think what I was looking for what cam30era just explained!!!
mad_rulzzz said:
I have a nexus 6. I have been using custom ROMs from the days of xperia mini pro. Never had a Nexus before. I want to have root in my nexus 6 for ad blocking cereberus and more. But this time I don't want custom ROMs. I just need the OTA's. I know OTA's dont happen automatically after root. So please tell me should I root and put a custom recovery, Or just root for manually updating the OTA's. Where can I get all the OTA's ?? I know it's a lot of questions.. Please.
Click to expand...
Click to collapse
You can just update in fastboot without an OTA. Just flash the new bootloader, system and possibly the new boot.img in fastboot and reroot. Erase and flash cache.img afterwards. Thats how i do it at least.
mad_rulzzz said:
I knew about the OTA failing due to the system partition getting changed while rooting. I think what I was looking for what cam30era just explained!!!
Click to expand...
Click to collapse
What he just explained is what I said, unroot and take the OTA.... He listed how as well.
RW-1 said:
What he just explained is what I said, unroot and take the OTA.... He listed how as well.
Click to expand...
Click to collapse
Yup.
@rw_1 @cam30era thanks guys
I would do what gee2012 said.
From what I have seen the OTA and the images are released pretty close together.
Instead of flashing images to get back to stock and waiting for the OTA. and then re-rooting
Just download the image files from Google. Manually flash all the files EXCEPT user data if you want to keep your data.
Re-root.
You are now updated and don't have to wait for OTA.
Either way works so it depends on which you are happier with.
mad_rulzzz said:
@rw_1 @cam30era thanks guys
Click to expand...
Click to collapse
Welcome. And BTW: there's a button for that.
gee2012 said:
You can just update in fastboot without an OTA. Just flash the new bootloader, system and possibly the new boot.img in fastboot and reroot. Erase and flash cache.img afterwards. Thats how i do it at least.
Click to expand...
Click to collapse
Just to be sure I understood right:
If I don't care about app data or settings ( I have titanium backup),
1)I can just unlock the boot loader
2)Flash the latest factory image from [developers.google.com/android/nexus/images]
3)Root using chain fire's tool
And repeat the process when the factory image of the next version is uploaded by google.
one last thing... Does Google upload factory images after each OTA happens?
cam30era said:
Welcome. And BTW: there's a button for that.
Click to expand...
Click to collapse
My BAd!!
mad_rulzzz said:
If I don't care about app data or settings ( I have titanium backup),
1)Can I just unlock the boot loader
2)Flash the latest factory image from [developers.google.com/android/nexus/images]
3)Root using chain fire's tool
And repeat the process when the factory image of the next version is uploaded by google.
Does Google upload factory images after each OTA happens? i.e; If Nexus 6 receives an OTA to 5.2, will they upload the 5.2 factory image soon?
Click to expand...
Click to collapse
When you unlock the bootloader it will wipe the contents of your SD card. Make sure it is backed up on your PC.
Unfortunately, not every OTA gets published as a factory image. Most, but not all. Case in point: LMY47M.
cam30era said:
Unfortunately, not every OTA gets published as a factory image. Most, but not all. Case in point: LMY47M.
Click to expand...
Click to collapse
I noticed that.... But that build is only for T-Mobile users, I guess...
Minor Differences, for example; If you take the android builds for Indian phones they are required by law to display the SAR rating. So I wouldn't worry about LMY47M, unless they have changed something to fix the memory leaks.
mad_rulzzz said:
I noticed that.... But that build is only for T-Mobile users, I guess...
Minor Differences, for example; If you take the android builds for Indian phones they are required by law to display the SAR rating. So I wouldn't worry about LMY47M, unless they have changed something to fix the memory leaks.
Click to expand...
Click to collapse
Correct. M is intended for T-Mobile. My point, though, is that Google doesn't always, 100% of the time publish a factory image for every OTA.
Hello all,
i rooted my nexus 6 and now that android 6.0 has been release i can't install the upgrade. My phone shows there is a system upgrade available. I have clicked to download the upgrade. Now its showing that a system upgrade has been downloaded and verified. Once i click on install update, it reboots to the teamwin. And to be honest, i don't really know if its taking the updated or how i can upgrade if possible.
can someone help me please?!!!!
Same answer every time. You can't get the OTA if you're rooted.
Options are :
- flash factory image (see sticky roll-up in general)
- flash a pre-rooted zip from recovery.
if you dont want to lose your data. just flash system.img, boot.img and recovery.img of your current build.
you can extract the images from the factory image...
Not only that, but by attempting to apply the OTA on a rooted device you risk bootlooping it, as I did with my Nexus 10 a couple of years ago.
Your best bet is to use Wugfresh's Nexus Root Toolkit (NRT). Since this is a major upgrade you can't use the "no wipe" option, so you'll lose any data that you haven't backed up first - photos, etc. - so do that before you do anything. Also take a TWRP backup of your current ROM and copy it to your PC so that at least you can recover to where you are now. NRT also has a backup option.
If you tell NRT that your current ROM is MRA58K (Android 6.0) and then tell it to flash stock and unroot, it will pull down all the required files before applying them to your Nexus. You can then re-root if you want to. It's a beautifully-engineered program, pretty well foolproof if you follow the instructions and choose the right ROM for your device.
dahawthorne said:
Not only that, but by attempting to apply the OTA on a rooted device you risk bootlooping it
Click to expand...
Click to collapse
It cant get to that stage any more.
Thats good news. What changed? Ever since that experience I haven't even tried an OTA. I was abroad at the time and lost the use of my Nexus 10 for most of the holiday.
dahawthorne said:
Thats good news. What changed? Ever since that experience I haven't even tried an OTA. I was abroad at the time and lost the use of my Nexus 10 for most of the holiday.
Click to expand...
Click to collapse
OTA zips used to check individual files in system to ensure they matched before updating. It checks either md5 or sha hash. It didn't take account of every file or even files added by the users. so upgrading could cause issues.
Now, it checks the md5/hash of the entire system, which means all files are taken into account.. It will not flash of anything is changed.
Thanks - happy to roll you over to 19,400...
Hi,
I am very new to this android world so my queries might feel stupid. Actually i m here after 3 years and that is very long period in this world. I know about rooting(super Su), bootloader and recovery (stock,CM and TWRP) . Recently read about Magisk and got some queries. Hope you will help me out. These are not device specific but need to learn.
What i read/study i found these readings...
1. Magisk roots device systemlessly (does not touch system partition) so one can get OTA updates easily.
2.To install and run Magisk one needs to unlock the bootloader .
3.(Device Specific) My redmi MI Flash tool says,If you unlock the bootloader , you wont get OTA updates.
4.I have previously rooted my galaxy Y and uninstalled system apps. If i delete sys apps from magisk,still can we say that we are not touching system.
So all statements are true? or some? or none ?
Here my device is redmi 3s (6.0.1- MIUI 9.6.1.0 Global Stable).All these queries are just in relation to OTA system updates. Nothing related to warranty.
Thanking You
Yes.
Yes.
Don't know about Xiaomi, but I've never had issues with OTA on a device with an unlocked bootloader (I've mainly used different Google and Oneplus devices). Someone with a Xiaomi is gonna have to chime in on this one.
As long as you use Magisk's debloating feature of replacing files or directories with empty ones, you're good. The actual /system partition won't be touched. Use a module like the Debloater module by @veez21, or make a debloater module yourself.
Didgeridoohan said:
Don't know about Xiaomi, but I've never had issues with OTA on a device with an unlocked bootloader (I've mainly used different Google and Oneplus devices). Someone with a Xiaomi is gonna have to chime in on this one.
Click to expand...
Click to collapse
Ahh, Thank You.
You get OTA system updates for your STOCK ROM ?
inwell said:
Ahh, Thank You.
You get OTA system updates for your STOCK ROM ?
Click to expand...
Click to collapse
Yes. But, having both Magisk and a custom recovery (an OTA won't install with a modified boot image and a custom recovery installed) I always find it easier to download the update and flash it manually. But, like I said, I have no idea if this is true for Xiaomi.
1. Ok. i also heared that when you update your device,you lose root...not true ? Or you need to root again ?
2.In normal stock device,we get update notification and we downlaod then restart (as per convenience)device to update.
If i remove some system apps from my rooted device and unroot the device,manage to get stock recovery back ,will the OTA update system treat my device as Stock-untouched? And install updates just as stock device will do ?
3. Is boot.img and bootloader are same things? Coz i read that for re locking boot loader you need to flash boot.img from stock software. (But Some procedures just use fastboot and relock oem command-they wont use boot.img,dont know why )
I read that unrooting,restoring stock recovery and locking bootloader again is more difficult/complicated than the rooting procedure
Some one should come up with solution just like Windows Restore .If you want to go back to everything STOCK,just use that feature same as done to Restore Windows in its previous state.
Any update that also updates the boot image (which means pretty much all) will remove root. But, that's just a simple case of reflashing Magisk right after applying the update.
If you've touched /system in any way, removing system apps or even just mounting the /system partition read-write, an OTA will fail. To be able update with an OTA your /system and /vendor partitions need to be untouched and you need to have the stock boot image and stock recovery installed. If your device doesn't conform to this the OTA will fail.
Boot image and bootloader are not the same thing. That you can read up on all over the internet, so I won't go into details. If you have done any kind of modifications on your device, I suggest you leave your bootloader unlocked. It's to easy to mess things up otherwise.
Going back to full stock is usually just a matter of flashing a full factory image/firmware package/stock ROM. Quite easy... Of course, some manufacturers make it harder than others.
Didgeridoohan said:
Boot image and bootloader are not the same thing. That you can read up on all over the internet, so I won't go into details. If you have done any kind of modifications on your device, I suggest you leave your bootloader unlocked. It's to easy to mess things up otherwise.
Click to expand...
Click to collapse
Ok. As you say the two are different , but can you explain in simple words (terms) that how they both are related/linked/connected? Coz as i read some forums/posts i get to read
1. To relock/lock bootloader you need to flash boot.img which suggests these (terms) are linked/connected.
2. but same time some forums/post suggest no img file flashing but just a fastboot command(s) to relock bootloader. In this case it seems they are not linked/connected.
And if the above 2 statements are true and device specific then how the bootloader and boot image are linked and not linked in diff devices? what changes are made so that in some cases these are linked and in some not
Sorry for asking too much. But you were really very kind to help me out.Thank you once again
I'm not 100% accurate (and someone will hopefully come I'm and correct me if needed), but basically the bootloader checks that everything is alright and then starts up your device. After that the boot image (ramdisk and kernel) takes over. Ramdisk basically makes sure all the partitions are mounted, and the kernel is exactly what it sounds like. The core of the OS, making sure that everything is working as it should.
This is of course a huge over-simplification, so if you want more you'll have to search around (and there are tons of resources around the web).
The main reason I can think of right at the moment for wanting to flash a boot image before locking the bootloader is that it's generally a good idea to have your device fully stock and functional before doing so. After you've locked the bootloader there might not be any going back if things start acting up and you could end up with a nice paperweight.
Questions are good. That's how you learn. I do believe that you'd be much better of searching around the internet for your answers. They've been put out there many, many times.
Ok.Thank you very much.I will learn more ...
When booting TWRP using fastboot, without flashing it to the recovery partition, eg. "fastboot boot twrp-sanders-r20.img", only for the purpose of taking a partition backup, once done the device wont longer take OTA's!
That is IMHO a very unexpected behavior, as booting this way and keeping system read only should mean that nothing on the phone gets changed (well except the data partition if a backup is saved on these one).
One would expect this not to mess with the OTA process.
Now, this twrp at least: https://forum.xda-developers.com/moto-g5s-plus/development/recovery-twrp-3-1-1-r7-t3694910 does, after some investigation i found out that it is mounting the oem partition writable and modifying it adding a .twrp file to the root. Since the OTAs are checking and patching this partition of cause they will fail.
Luckily there is a way out, you can reflash the OEM partition for example from here: https://forum.xda-developers.com/moto-g5s-plus/how-to/tutorial-fhash-oreo-8-1-stock-global-t3852967
that is assuming that you are running the first Oreo 8.1 update, if you had an other version when the issue hit, you will need to find the right OEM partition image for you actual build.
IMHO this behavior of TWRP is unacceptable and should be fixed in a new release ASAP.
DavidXanatos said:
When booting TWRP using fastboot, without flashing it to the recovery partition, eg. "fastboot boot twrp-sanders-r20.img", only for the purpose of taking a partition backup, once done the device wont longer take OTA's!
That is IMHO a very unexpected behavior, as booting this way and keeping system read only should mean that nothing on the phone gets changed (well except the data partition if a backup is saved on these one).
One would expect this not to mess with the OTA process.
Now, this twrp at least: https://forum.xda-developers.com/moto-g5s-plus/development/recovery-twrp-3-1-1-r7-t3694910 does, after some investigation i found out that it is mounting the oem partition writable and modifying it adding a .twrp file to the root. Since the OTAs are checking and patching this partition of cause they will fail.
Luckily there is a way out, you can reflash the OEM partition for example from here: https://forum.xda-developers.com/moto-g5s-plus/how-to/tutorial-fhash-oreo-8-1-stock-global-t3852967
that is assuming that you are running the first Oreo 8.1 update, if you had an other version when the issue hit, you will need to find the right OEM partition image for you actual build.
IMHO this behavior of TWRP is unacceptable and should be fixed in a new release ASAP.
Click to expand...
Click to collapse
Agreed; received today a security update for my moto G5S plus (didn't root till i got the official 8.1 Oreo update) and every time i try to install takes me to TWRP and i keep it as READ ONLY (since TWRP itself says if u modify u won't b able to receive OTA updates) and... even without the modification i still can't get the update. this has to be fixed ASAP by TWRP
I did discover that if you keep the OTA files for older updates, you can re-run them to update the OEM partition. Unfortunately it only works one update generation.
I wonder if we just delete the .TWRP file if it can recover it. I'll test later this week. The OTA has a way to repair partitions
pizzaboy192 said:
I did discover that if you keep the OTA files for older updates, you can re-run them to update the OEM partition. Unfortunately it only works one update generation.
I wonder if we just delete the .TWRP file if it can recover it. I'll test later this week. The OTA has a way to repair partitions
Click to expand...
Click to collapse
keep us posted man
pizzaboy192 said:
I wonder if we just delete the .TWRP file if it can recover it. I'll test later this week. The OTA has a way to repair partitions
Click to expand...
Click to collapse
imho 99% sure, it still will fail, the partition does not just have to be semantically unchanged it must be 1:1 bit wise identical with what is expected.
I'll see what happens. I'm not a developer but I have pointed this out a few times to the developers of both TWRP threads, along with sharing these issues on the telegram group, but everyone else is focused on the latest custom ROM and doesn't care about stock, so the issues have fallen on deaf ears
in a nutshell how can i receive the last OTA security? do i revert to stock , install then root again? holy moly that's a lot of work
TheKicKer69 said:
in a nutshell how can i receive the last OTA security? do i revert to stock , install then root again? holy moly that's a lot of work
Click to expand...
Click to collapse
Unfortunately until they fix TWRP so it doesn't damage the OEM partition, you need a clean copy of the OEM partition to take the OTA.
However, there is a way you can prevent this, but it is a little hairy (you can't use any magisk modules). You can use the magisk app to patch the boot.img file that is from a slightly older Oreo firmware and flash that with fastboot, without using TWRP.
---------- Post added at 07:35 AM ---------- Previous post was at 07:30 AM ----------
DavidXanatos said:
imho 99% sure, it still will fail, the partition does not just have to be semantically unchanged it must be 1:1 bit wise identical with what is expected.
Click to expand...
Click to collapse
Yup. Just confirmed that deleting the .twrp file does not fix it.
I've reached out to Motorola to update their Lenovo Motorola Smart Assistant tool to support the official Oreo OTA which will allow us to download the latest full firmware file, which would give us the OEM partition to reflash before the next OTA.
I'll bother the TWRP devs again this week to get this unexpected behavior removed so we don't need to bother anyone in the future.
Update: none of the TWRP maintainers currently have replied to me about this issue.
@CheckYourScreen hasn't been active for a while but hasn't responded to a few different attempts to point this issue out (Been over a month since first notification with no acknowledgement)
@MasterAwesome has a custom TWRP that is latest, but they're still working on it. They're our best bet to possibly get it fixed since they're actively working on it. They've also been made aware, but no response yet (4 days since notifying and it was a weekend, so hopeful)
@GeneticEnginer was notified today. They developed the first unofficial TWRP (3.1.1) and might be able to help, but not holding my breath
I've also contacted a few people who do unofficial TWRP ports for some tips on unpacking one of our existing TWRP files and fixing it myself. It may be the way to go.
Hi guys. Final update. I've fixed TWRP temporarily. If we're not going to run custom ROMs, use this TWRP to backup. It does a bitwise backup of OEM and doesn't mount it as RW so it WILL work for restoring fully OTA capable stock ROM. It is NOT treble compatible as the treble compatible ones do weird things that I haven't documented.
https://forum.xda-developers.com/mo...-r20-stock-t3869192/post78205758#post78205758