I've got stock, odexed....am rooted. That's it. Got the update, trying to flash with TWRP and get "system/build.prop has unexpected contents" error. Can't install the update.
WHY????? It's killin' me!
Thanks.
velveteen71 said:
I've got stock, odexed....am rooted. That's it. Got the update, trying to flash with TWRP and get "system/build.prop has unexpected contents" error. Can't install the update.
WHY????? It's killin' me!
Thanks.
Click to expand...
Click to collapse
you apparently have a modified build.prop. You probably will have to re-flash system.img to apply the OTA.
or find what was changed in build.prop and revert the change.
If you installed ANY modifications (dalvik mod, camera mod, center clock, dpi changes, ANYTHING) than it will not flash.
Synyster06Gates said:
If you installed ANY modifications (dalvik mod, camera mod, center clock, dpi changes, ANYTHING) than it will not flash.
Click to expand...
Click to collapse
Hey guys, got (what I believe is) a similar issue.
the error message I'm getting when I try to flash the update (or sideload it) is "EMMC:/dev/block/platform/msm_sdcc.1/by-name/bootand a huge string of characters ending with the end quote that follows)" has unexpected contents.
I've flashed back to stock krt16m, bootloader is still unlocked with cwm recovery, and I still get this error. The only modifications I had made were flashing the bricked-kernel hammerhead and enabling doubletap to wake, also installed xposed framework with gravitybox and advanced power options.
I flashed the uninstall file for bricked-kernel hammerhead (which was a boot.img so assuming it was this and not xposed?) but I'm still unable to flash the update to 4.4.1
suggestions? is there a way to flash a new boot.img? I'm a relative beginner.. I'm unable to track down a link that has a stock boot.img, I'm not sure if this is part of the factory image but I'm assuming not if I'm still having this issue..
thank you for any input!
desucca said:
Hey guys, got (what I believe is) a similar issue.
the error message I'm getting when I try to flash the update (or sideload it) is "EMMC:/dev/block/platform/msm_sdcc.1/by-name/bootand a huge string of characters ending with the end quote that follows)" has unexpected contents.
I've flashed back to stock krt16m, bootloader is still unlocked with cwm recovery, and I still get this error. The only modifications I had made were flashing the bricked-kernel hammerhead and enabling doubletap to wake, also installed xposed framework with gravitybox and advanced power options.
I flashed the uninstall file for bricked-kernel hammerhead (which was a boot.img so assuming it was this and not xposed?) but I'm still unable to flash the update to 4.4.1
suggestions? is there a way to flash a new boot.img? I'm a relative beginner.. I'm unable to track down a link that has a stock boot.img, I'm not sure if this is part of the factory image but I'm assuming not if I'm still having this issue..
thank you for any input!
Click to expand...
Click to collapse
Is Bricked the only kernel you've used? Or did you try Franco as well? Francos modifies a few files that need to be fixed before you can flash the update - even if you flashed a stock boot.img.
If you haven't, try the stock boot.img from http://forum.xda-developers.com/showthread.php?t=2513701
Got the same message. Flash the stock 4.4 (not 4.4.1) boot.img from the factory zip.
Synyster06Gates said:
Is Bricked the only kernel you've used? Or did you try Franco as well? Francos modifies a few files that need to be fixed before you can flash the update - even if you flashed a stock boot.img.
If you haven't, try the stock boot.img from http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
yep, bricked was the only one I've tried so far. I'll try this and report back, thank you
*update* worked! thanks very much, it's updating right now.
desucca said:
yep, bricked was the only one I've tried so far. I'll try this and report back, thank you
Click to expand...
Click to collapse
I was the same as you. I had to flash stock boot.img and system.img for it to work. I only tried Bricked but went back to stock and at one point I tried Xposed. Guess one of them left a trace.
Sent from my Nexus 5 using xda app-developers app
david23c said:
you apparently have a modified build.prop. You probably will have to re-flash system.img to apply the OTA.
or find what was changed in build.prop and revert the change.
Click to expand...
Click to collapse
This. What did you modify in your build.prop? Revert to your backed up original build.prop (.bak), install a new stock build.prop, or flash system.img.
Nitemare3219 said:
Got the same message. Flash the stock 4.4 (not 4.4.1) boot.img from the factory zip.
Click to expand...
Click to collapse
you should flash boot.img and system.img to make sure you have a stock system partition.
david23c said:
you should flash boot.img and system.img to make sure you have a stock system partition.
Click to expand...
Click to collapse
i have the same problem, does flashing these files affect any of my data or configuration?
cannot update rooted nexus?
so in short can we say we just cannot update to 4.4.1 without reverting back to and losing all app data ?
Guys,
Please help me out here. I rooted my Nex5 because I could not stand the DPI (icons/text were ridiculously big)
Because an app I use a lot cannot function on a rooted phone, I unrooted my phone.
I guess this means the following: my bootloader is NOT stock (because I see the 'unlock' icon), I am NOT rooted and my OS is stock.
In the end I just want to get 4.4.1 the easiest way and of course still have my DPI still modified.
Thanks in advance!!!
gaurishmhatre said:
so in short can we say we just cannot update to 4.4.1 without reverting back to and losing all app data ?
Click to expand...
Click to collapse
Yes you can. I flashed the OTA in CWM after undoing the changes I'd made and it flashed fine without losing data
lowlow2 said:
Guys,
Please help me out here. I rooted my Nex5 because I could not stand the DPI (icons/text were ridiculously big)
Because an app I use a lot cannot function on a rooted phone, I unrooted my phone.
I guess this means the following: my bootloader is NOT stock (because I see the 'unlock' icon), I am NOT rooted and my OS is stock.
In the end I just want to get 4.4.1 the easiest way and of course still have my DPI still modified.
Thanks in advance!!!
Click to expand...
Click to collapse
You can't install the update. You need to revert all system settings to stock (including what ever changed your DPI) before you can update. After that, you can install it, re root and change your DPI;
---------- Post added at 06:10 AM ---------- Previous post was at 06:09 AM ----------
chucky8 said:
i have the same problem, does flashing these files affect any of my data or configuration?
Click to expand...
Click to collapse
No, your data and configuration will be fine.
Synyster06Gates said:
You can't install the update. You need to revert all system settings to stock (including what ever changed your DPI) before you can update. After that, you can install it, re root and change your DPI;
---------- Post added at 06:10 AM ---------- Previous post was at 06:09 AM ----------
No, your data and configuration will be fine.
Click to expand...
Click to collapse
Thank you, I encountered in fact the problem because I changed my build.prop.
I tried adb sideload, but it gave an error on build.prop.
I see what I need to do now, thank you!!
---------- Post added at 01:25 PM ---------- Previous post was at 01:19 PM ----------
lowlow2 said:
Thank you, I encountered in fact the problem because I changed my build.prop.
I tried adb sideload, but it gave an error on build.prop.
I see what I need to do now, thank you!!
Click to expand...
Click to collapse
One last question, can I just adjust (revert) the DPI setting ? Or will it detect I fuzzled with my build.prop and never work without replacing ? Thanks
lowlow2 said:
Thank you, I encountered in fact the problem because I changed my build.prop.
I tried adb sideload, but it gave an error on build.prop.
I see what I need to do now, thank you!!
---------- Post added at 01:25 PM ---------- Previous post was at 01:19 PM ----------
One last question, can I just adjust (revert) the DPI setting ? Or will it detect I fuzzled with my build.prop and never work without replacing ? Thanks
Click to expand...
Click to collapse
You should be able to just edit it back to original configuration.
Synyster06Gates said:
You should be able to just edit it back to original configuration.
Click to expand...
Click to collapse
Tried this but unfortunately not working. I have the original system.img (+-600MB)
Can you tell me how I flash this with ADB (weirdly couldn't find it on xda via search!)
Thanks!
lowlow2 said:
Tried this but unfortunately not working. I have the original system.img (+-600MB)
Can you tell me how I flash this with ADB (weirdly couldn't find it on xda via search!)
Thanks!
Click to expand...
Click to collapse
Here ya go. Make sure the drivers are installed correctly. This guide has it all. You will only be flashing system.img, not the entire bat
http://forum.xda-developers.com/showthread.php?t=2513701
Synyster06Gates said:
Here ya go. Make sure the drivers are installed correctly. This guide has it all. You will only be flashing system.img, not the entire bat
http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
thanks!!
Related
Trying to do the 4.4.2 update but its says unexpected item in build prop every time I try to flash in recovery all I ever touched was LCD density and I flashed return to stock on 4way reboot and ad blocking hosts so I'm thinking I need an untouched build prop of someone is willing to help
Sent from my Nexus 5 using Tapatalk
+1
I also would be grateful if someone would upload 4.4.1 (KOT49E) stock build.prop...
i need this too.
Just fastboot flash the system image. Problem solved!
jd1639 said:
Just fastboot flash the system image. Problem solved!
Click to expand...
Click to collapse
4.4.1 isn't on AOSP yet, is it safe to flash 4.4 system.img on 4.4.1? Will it just revert me back to 4.4?
akhan47 said:
4.4.1 isn't on AOSP yet, is it safe to flash 4.4 system.img on 4.4.1? Will it just revert me back to 4.4?
Click to expand...
Click to collapse
Yes it's safe. Then sideload the 4.4 to 4.4.2 update zip
jd1639 said:
Yes it's safe. Then sideload the 4.4 to 4.4.2 update zip
Click to expand...
Click to collapse
Thanks you, will do this later today.
akhan47 said:
+1
I also would be grateful if someone would upload 4.4.1 (KOT49E) stock build.prop...
Click to expand...
Click to collapse
4.4.1 build.prop.
Remember to change permissions to rw-r-r
https://www.dropbox.com/s/7vp174py4fmmfip/build.prop
Sent from my Nexus 5 using XDA Premium 4 mobile app
jbielman said:
Trying to do the 4.4.2 update but its says unexpected item in build prop every time I try to flash in recovery all I ever touched was LCD density and I flashed return to stock on 4way reboot and ad blocking hosts so I'm thinking I need an untouched build prop of someone is willing to help
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hi,
Same problem for me but I need the KRT16M stock 4.4 /system/build.prop file to be able to apply the OTA update... and I don't want to reflash the stock system.img because I have added some ogg files and renamed some others to add custom ring bells and remove camera sounds... so basically (even if that's not that a pain in the ass to do it again) I would be pleased not to have to do that again.
Anyone ? (I'm googling like hell... only build.prop I found was the one here, from 4.4.1 :/)
hehe2 said:
Hi,
Same problem for me but I need the KRT16M stock 4.4 /system/build.prop file to be able to apply the OTA update... and I don't want to reflash the stock system.img because I have added some ogg files and renamed some others to add custom ring bells and remove camera sounds... so basically (even if that's not that a pain in the ass to do it again) I would be pleased not to have to do that again.
Anyone ? (I'm googling like hell... only build.prop I found was the one here, from 4.4.1 :/)
Click to expand...
Click to collapse
It's not going to work
jd1639 said:
It's not going to work
Click to expand...
Click to collapse
Well, I ended up by flashing the system.img, then sideloading the OTA, then flashing latest TWRP then installing latest Super SU and cleared cache/dalvik "et voilà", now I only got to put my custom ogg ringtones/notifications files in place and I'm good
Couldn't find that crappy build.prop anyway... but I adb pulled it (after having flashed the system.img) just to make a diff with my previously modified one (that I backuped).
Well, running 4.4.2 fine now, with no app to re-install, kinda "OTA" like... with the added mess up, but kept my root so...
You can always just download the stock ROM and pull the build.prop from there.
The original update OTA can be obtained here: WWE_4.07.1700.4-3.62.1700.1_KTU84L.H4_release_377648
This cannot be flashed unless your device meets all requirements. Wait for a ROM otherwise.
Can someone with the latest version of the stock 4.4.2 GPE help me out! Need one file to update to 4.4.3!
http://forum.xda-developers.com/showthread.php?t=2772266
Thanks!
Orginator said:
Can someone with the latest version of the stock 4.4.2 GPE help me out! Need one file to update to 4.4.3!
http://forum.xda-developers.com/showthread.php?t=2772266
Thanks!
Click to expand...
Click to collapse
Googling for this MD5 first gives me your postings (scattered across XDA ) as well as this link: http://rghost.net/53665485
EDIT: file has been deleted.
sanderg said:
Googling for this MD5 first gives me your postings (scattered across XDA ) as well as this link: http://rghost.net/53665485
EDIT: file has been deleted.
Click to expand...
Click to collapse
Trust me, the first thing I do is google.. been there, done that! Yeah sadly deleted and I'm still stuck at 4.4.2, so many must have made a CWM backup before updating to 4.4.3, yet so hard to get that file :/
Orginator said:
Trust me, the first thing I do is google.. been there, done that! Yeah sadly deleted and I'm still stuck at 4.4.2, so many must have made a CWM backup before updating to 4.4.3, yet so hard to get that file :/
Click to expand...
Click to collapse
What if you manually edit updater-script to not patch Youtube?
I could do that, but then I'll have the same issue on next OTA! I'd rather have a 100% clean update, if you know what I mean!
Could you make a ROM GPE with Sense camera ?
Orginator said:
I could do that, but then I'll have the same issue on next OTA! I'd rather have a 100% clean update, if you know what I mean!
Click to expand...
Click to collapse
Mine fails as well - on basicDreams.apk. It doesn't look like it can be applied to every device, e.g. when integrating apps into the ROM using Titanium Backup it will most likely fail. Will be taken care of by the ROM devs though.
sanderg said:
Mine fails as well - on basicDreams.apk. It doesn't look like it can be applied to every device, e.g. when integrating apps into the ROM using Titanium Backup it will most likely fail. Will be taken care of by the ROM devs though.
Click to expand...
Click to collapse
I don't use Titanium Backup or anything alike.
Can we flash this OTA.zip from stock recovery after we returned back to Google Edition ?
HAAANG ON!! hang on......
this....is a 4.xx.xxxx.x update
previous was 3.62.xxxx.x
....I may assume that is like a....major release or something...?
I expect a good improvement, even in performance (that on sense roms is always 2 times better, dunno why)
Can we flash this?
Sent from my HTC One using Tapatalk
gaja22 said:
Could you make a ROM GPE with Sense camera ?
Click to expand...
Click to collapse
No
---------- Post added at 06:13 AM ---------- Previous post was at 06:12 AM ----------
throcker said:
HAAANG ON!! hang on......
this....is a 4.xx.xxxx.x update
previous was 3.62.xxxx.x
....I may assume that is like a....major release or something...?
I expect a good improvement, even in performance (that on sense roms is always 2 times better, dunno why)
Click to expand...
Click to collapse
Stick to your sense ROM then because performance hasn't changed much between 4.4.2 and 4.4.3
---------- Post added at 06:13 AM ---------- Previous post was at 06:13 AM ----------
mrgwap said:
Can we flash this?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Don't think so, it's an OTA file that needs to be installed by the stock recovery, not a custom recovery.
Nic2112 said:
No
---------- Post added at 06:13 AM ---------- Previous post was at 06:12 AM ----------
Stick to your sense ROM then because performance hasn't changed much between 4.4.2 and 4.4.3
---------- Post added at 06:13 AM ---------- Previous post was at 06:13 AM ----------
Don't think so, it's an OTA file that needs to be installed by the stock recovery, not a custom recovery.
Click to expand...
Click to collapse
About to RUU back to 4.4.2 with stock recovery.
What do I do afterwards. I have the file in the OP downloaded. Do I just place it in root storage and look for a update than root afterwards.
charlieb620 said:
About to RUU back to 4.4.2 with stock recovery.
What do I do afterwards. I have the file in the OP downloaded. Do I just place it in root storage and look for a update than root afterwards.
Click to expand...
Click to collapse
All I had to do was RUU to 4.4.0 because that's the one I had handy, let the phone OTA to 4.4.2, and when it booted all I had to do was hit the "check for update" button 2-3 times and then it prompted me to download the OTA and voila, 4.4.3
Nic2112 said:
All I had to do was RUU to 4.4.0 because that's the one I had handy, let the phone OTA to 4.4.2, and when it booted all I had to do was hit the "check for update" button 2-3 times and then it prompted me to download the OTA and voila, 4.4.3
Click to expand...
Click to collapse
Alright I will do the RUU and just check for Update.
charlieb620 said:
Alright I will do the RUU and just check for Update.
Click to expand...
Click to collapse
You would have to put the OTA at the right location and name it exactly what the recovery expects and I don't know how to do that.
Thing is with stock recovery, there are no options, it either updates or resets to factory default.
can someone make a flashable zip of the rom? Wouldn't really want to go thru all the trouble of converting back to stock recovery and rom to update since im on a custom rom now? A flashable zip would mean a lot!
ace-user said:
can someone make a flashable zip of the rom? Wouldn't really want to go thru all the trouble of converting back to stock recovery and rom to update since im on a custom rom now? A flashable zip would mean a lot!
Click to expand...
Click to collapse
Just wait a day or two.
I haven't really noticed a performance increase or decrease tbh after flashing the new firmware. It says "5.11.401.10" because I edited the android-info.txt file. But the date is 5/16/2014, to confirm that it is the newer v1.54 hboot. How would I go about making a deodex system dump into a flashable rom.zip? I have the system dump if someone can help me with the procedure.
Hello everyone.
Two hours ago I received the notification about the Android 5.0 update. I downloaded it and hit "Install". Then, "TeamWin" started, but not the update. I rebooted into System and tried to update again - but it tells me that 4.4.4 is the latest version I can get now. I'm on Build KTU84P now.
1) Do I need to remove TeamWin? If yes, with what?
2) How can I start the update again? I'm on a super slow connection and it would hurt to download the 500 MB again…
Thank you!
Fablus said:
Hello everyone.
Two hours ago I received the notification about the Android 5.0 update. I downloaded it and hit "Install". Then, "TeamWin" started, but not the update. I rebooted into System and tried to update again - but it tells me that 4.4.4 is the latest version I can get now. I'm on Build KTU84P now.
1) Do I need to remove TeamWin? If yes, with what?
2) How can I start the update again? I'm on a super slow connection and it would hurt to download the 500 MB again…
Thank you!
Click to expand...
Click to collapse
You need to remove TeamWin, and load up your stock recovery. I don't have the exact instructions for this unfortunately.
The OTA update will come back to your phone soon, usually. Did for me within the hour.
The issue I am having now, back with stock recovery, is during the install I am getting a dead Android error icon, and can't continue. Looking for any help I can, and hopefully it will help you too.
Mysticodex said:
You need to remove TeamWin, and load up your stock recovery. I don't have the exact instructions for this unfortunately.
The OTA update will come back to your phone soon, usually. Did for me within the hour.
The issue I am having now, back with stock recovery, is during the install I am getting a dead Android error icon, and can't continue. Looking for any help I can, and hopefully it will help you too.
Click to expand...
Click to collapse
Maybe we need http://forum.xda-developers.com/google-nexus-5/general/stock-checker-zip-prepare-ota-t2927865?
Gosh, this used to be so easy all the time.
if you are using twrp, why the heck are you trying to install the ota? why not download(from xda) and flash a recovery flashable stock or aosp build, and make life much easier for yourself? heck, i dirty flashed from 444 to 5.0 via an aosp flashable zip without any issues, and kept all my data.
simms22 said:
if you are using twrp, why the heck are you trying to install the ota? why not download(from xda) and flash a recovery flashable stock or aosp build, and make life much easier for yourself? heck, i dirty flashed from 444 to 5.0 via an aosp flashable zip without any issues, and kept all my data.
Click to expand...
Click to collapse
I've read http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523 and it clearly states
-Do a factory reset (maybe you can keep data coming from STOCK 4.4.4 - maybe)
Click to expand...
Click to collapse
And I didn't want to count on a maybe.
I'm using stock recovery, rooted as per normal, and a custom kernal. OTA is giving an Android dead error, with no text. Trying to figure out how to diagnose this.
Fablus said:
I've read http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523 and it clearly states
Click to expand...
Click to collapse
it clearly states what? to use recovery version 2.8+? i used an older version, twrp version 2.6.2.4. what else?
---------- Post added at 05:51 PM ---------- Previous post was at 05:48 PM ----------
Mysticodex said:
I'm using stock recovery, rooted as per normal, and a custom kernal. OTA is giving an Android dead error, with no text. Trying to figure out how to diagnose this.
Click to expand...
Click to collapse
it wont flash over a rooted rom anymore as of lollipop. you can flash the factory img via fastboot though, in your bootloader.
simms22 said:
it clearly states what? to use recovery version 2.8+? i used an older version, twrp version 2.6.2.4. what else?
---------- Post added at 05:51 PM ---------- Previous post was at 05:48 PM ----------
it wont flash over a rooted rom anymore as of lollipop. you can flash the factory img via fastboot though, in your bootloader.
Click to expand...
Click to collapse
Trying to remove the root right now via SuperSU. I am hopeful it will work better afterwards.
Edit: SuperSU unrooted it, rebooted, did OTA again, error again. Is there no way to find out what this error is?
Updating now! ????
Me too! Can't wait for P!
Essential updated both radio and kernel this time.
P is just around the corner... Can't wait!!!
Does this include the multi touch bug fix?
I've never had issues with multi touch.
Nickvanexel said:
Does this include the multi touch bug fix?
Click to expand...
Click to collapse
They do not provide info about this point, but in my experience with this build, multi touch bug is fixed. At least pinch zooming in Instagram is now stable.
Is it ok to sideload over custom kernel?
I couldn't complete the update. After download is completed I am getting error "installation problem couldn't update".
I tried 3 to 4 times I even tried restarting the phone even tried downloading from a different network but none of them helped.
I checked it in a Reddit thread that many others also facing the same error like mine.
Is anyone else facing the same issue like this
prasathvishnu said:
I couldn't complete the update. After download is completed I am getting error "installation problem couldn't update".
I tried 3 to 4 times I even tried restarting the phone even tried downloading from a different network but none of them helped.
I checked it in a Reddit thread that many others also facing the same error like mine.
Is anyone else facing the same issue like this
Click to expand...
Click to collapse
No issue here, but I'm not unlocked or rooted.
No issues installing on my bone stock unrooted device.
millicent said:
Is it ok to sideload over custom kernel?
Click to expand...
Click to collapse
Yes..
You can just flash full OTA zip via twrp.
No wipes needed.
If I have the bootloader unlocked and with root, can I install this update? Without losing my data or having to re-root the phone?
---------- Post added at 06:03 PM ---------- Previous post was at 06:00 PM ----------
indian84 said:
Yes..
You can just flash full OTA zip via twrp.
No wipes needed.
Click to expand...
Click to collapse
do you know where I can download the OTA zip?
prasathvishnu said:
I couldn't complete the update. After download is completed I am getting error "installation problem couldn't update".
I tried 3 to 4 times I even tried restarting the phone even tried downloading from a different network but none of them helped.
I checked it in a Reddit thread that many others also facing the same error like mine.
Is anyone else facing the same issue like this
Click to expand...
Click to collapse
Same here, no root
rockhevy1000 said:
If I have the bootloader unlocked and with root, can I install this update? Without losing my data or having to re-root the phone?
---------- Post added at 06:03 PM ---------- Previous post was at 06:00 PM ----------
do you know where I can download the OTA zip?
Click to expand...
Click to collapse
Download the full OTA zip from below.
https://storage.googleapis.com/essential-static/PH1-OTA-OPM1.180104.234.zip
Reboot in TWRP, flash the zip without wiping anything.
Once the zip flashing is complete, reboot to system.
Then you can root again.
PS - Do not forget to remove your secured lock screen (PIN, Password, Pattern etc.) before flashing TWRP.
indian84 said:
Download the full OTA zip from below.
https://storage.googleapis.com/essential-static/PH1-OTA-OPM1.180104.234.zip
Reboot in TWRP, flash the zip without wiping anything.
Once the zip flashing is complete, reboot to system.
Then you can root again.
PS - Do not forget to remove your secured lock screen (PIN, Password, Pattern etc.) before flashing TWRP.
Click to expand...
Click to collapse
Do I have to flash the boot image to?
Thanks for the reply!
rockhevy1000 said:
Do I have to flash the boot image to?
Thanks for the reply!
Click to expand...
Click to collapse
Yes.
Rooting will be similar to how you did before.
Is the battery getting better? My battery life got a lot worse since I installed the May update, literally could only last a few hours.
where did you get the image from?...I meant he modded image to get the root back.
ranjaheer said:
where did you get the image from?...I meant he modded image to get the root back.
Click to expand...
Click to collapse
Google.
i have been flashing stock OTAs as sideloaded in TWRP. BL unlocked and rooted.
Hi all,
Tried searching, got nowhere.
I've received the OTA 1.53.401.5.
I have S-ON, Magisk root, stock recovery, stock system, custom Kernel
What would happen if I attempt to install the OTA without returning boot.img to stock? (Apart from overwriting the kernel with stock kernel).
Has anyone attempted? - Magisk should be able to persist root on the B partition since v14.1
Last, but not least, if the OTA fails....will my device bootloop? Or will it abort the update before making any changes?
The idea here, is it safe to attempt despite not being near to a PC to recover the device? Or will I need to be prepared to RUU my device in case of failure?
Kyuubi10 said:
Hi all,
Tried searching, got nowhere.
I've received the OTA 1.53.401.5.
I have S-ON, Magisk root, stock recovery, stock system, custom Kernel
What would happen if I attempt to install the OTA without returning boot.img to stock? (Apart from overwriting the kernel with stock kernel).
Has anyone attempted? - Magisk should be able to persist root on the B partition since v14.1
Last, but not least, if the OTA fails....will my device bootloop? Or will it abort the update before making any changes?
The idea here, is it safe to attempt despite not being near to a PC to recover the device? Or will I need to be prepared to RUU my device in case of failure?
Click to expand...
Click to collapse
I think it will fail if it doesn't pass its checks before rebooting.
(mine did as I had booted to twrp, but then I am used to backing up my data and RUUing these days)
Electronic Punk said:
I think it will fail if it doesn't pass its checks before rebooting.
(mine did as I had booted to twrp, but then I am used to backing up my data and RUUing these days)
Click to expand...
Click to collapse
Yeah, due to some tests I've been doing with Dolby Atmos I've gotten used to RUUing too... But it still is such a pain in the ass.
So can you confirm if it is a bootloop when OTA fails?
Kyuubi10 said:
Yeah, due to some tests I've been doing with Dolby Atmos I've gotten used to RUUing too... But it still is such a pain in the ass.
So can you confirm if it is a bootloop when OTA fails?
Click to expand...
Click to collapse
I didn't get as far as rebooting. The OTA started then failed without making any changes.
Kyuubi10 said:
Yeah, due to some tests I've been doing with Dolby Atmos I've gotten used to RUUing too... But it still is such a pain in the ass.
So can you confirm if it is a bootloop when OTA fails?
Click to expand...
Click to collapse
hey mate!
it won't bootloop, because it won't reach that far xD it will just fail. you need stock boot, system and vendor. if you've messed with system/vendor it will fail anyway
In another thread @Freak07 responded me that it could work only if some file in boot or vendor image had a certain value. It hadn't for me but I am sorry I forgot what it was exactly.
I believe it was either on @Freak07 recovery thread or in his kernel thread.
---------- Post added at 09:36 PM ---------- Previous post was at 08:38 PM ----------
EMJI79 said:
I am proposed OTA by the system but I can't do it, right?
We always have to RUU-OTA-ROOT then install the kernel?
I thought I had read that somewhere but I can't find it, so if someone could confirm?
Click to expand...
Click to collapse
It depends. Check the lifetime_kb_writes file like it’s mentioned in the second post of the twrp thread. If it doesn’t show 0 for system or vendor OTA will fail and you have to RUU.
Hi,
It is imperative to be in stock and not root.Sans this office error and the OTA does not settle.Je got to have version 1.30.401.2 on the A and version 1.53.401.5 on the B.Version on the A custom and root, the version on the B just root.
But not easy to get there!
DeeZZ_NuuZZ said:
hey mate!
it won't bootloop, because it won't reach that far xD it will just fail. you need stock boot, system and vendor. if you've messed with system/vendor it will fail anyway
Click to expand...
Click to collapse
Hey DeeZZ! Long time! XD I keep saying I'll come back but I never do.
Good to know that it won't bootloop... What I want to try tbh is follow the steps by Magisk dev to take OTA.
In theory if I flash back a clean system.img and vendor.img I should successfully be able to uninstall magisk take OTA and root the new update through Magisk Manager.
EMJI79 said:
In another thread @Freak07 responded me that it could work only if some file in boot or vendor image had a certain value. It hadn't for me but I am sorry I forgot what it was exactly.
I believe it was either on @Freak07 recovery thread or in his kernel thread.
---------- Post added at 09:36 PM ---------- Previous post was at 08:38 PM ----------
It depends. Check the lifetime_kb_writes file like it’s mentioned in the second post of the twrp thread. If it doesn’t show 0 for system or vendor OTA will fail and you have to RUU.
Click to expand...
Click to collapse
Thanks for this link! It was very useful.
But I do have one complaint about it... Surely the file would not be 0 while Magisk mods are active.
I have no system mods, and all mods I have are Magisk systemless mods.
So for the file to have a value greater than 0 it must be because while Magisk is active the file "believes" there are system modifications, due to following the sym-links created by Magisk.
This being said I couldn't find the vendor "sda#" on my sys/fs.
Additionally could I possibly change the file to have a "0" value? Thus fooling the OTA mechanism?
So many theories! I hope one of them works... I'm tired of RUU and losing my data.
I don't think you can change it manually, it would be too easy.
EMJI79 said:
I don't think you can change it manually, it would be too easy.
Click to expand...
Click to collapse
Lol true