Database Develop

Android 4.4 KitKat installation failed on nexus 7 (2012)

Hello,
I had a problem with my nexus 7 today, hope someone will help me.
Today i got a notification that says, new android system has been downloaded.. touch to install..
So i tapped the notification, and if anyone who has nexus 7 and got an updated before.. he will know exactly mo problem.
So i clicked the button "reboot and install".. my device has been rebooted .. and there was that screen like cmd in Windows.. i remember some messages from it "MD5 not found" then the the deviced booted and didn't get Android kitkat update.
Information about my nexus 7 device:
1) It's rooted.
2) I've Android 4.3.
My Questions are:
1) How can i get that notification another time to try install it again?
2) When i go to Recovery.. Install.. I see the ZIP file for Android 4.4, it's name was "kataski" i think, my question if i flashed that ZIP file.. means i've installed kitkat manually, then i'll lose my auto updates?
Waiting for the reply.
Thanks

Mob_Dev said:
Hello,
I had a problem with my nexus 7 today, hope someone will help me.
Today i got a notification that says, new android system has been downloaded.. touch to install..
So i tapped the notification, and if anyone who has nexus 7 and got an updated before.. he will know exactly mo problem.
So i clicked the button "reboot and install".. my device has been rebooted .. and there was that screen like cmd in Windows.. i remember some messages from it "MD5 not found" then the the deviced booted and didn't get Android kitkat update.
Information about my nexus 7 device:
1) It's rooted.
2) I've Android 4.3.
My Questions are:
1) How can i get that notification another time to try install it again?
2) When i go to Recovery.. Install.. I see the ZIP file for Android 4.4, it's name was "kataski" i think, my question if i flashed that ZIP file.. means i've installed kitkat manually, then i'll lose my auto updates?
Waiting for the reply.
Thanks
Click to expand...
Click to collapse
Hi,
As per: http://forum.xda-developers.com/showpost.php?p=47648484&postcount=2342
OTAs will never work on a system which is modified in some way, because they contain only bytes which were changed between two Android versions. If files on the device are changed (custom ROM, different kernel, MultiROM-injected init, sometimes even root), OTA simply can't be applied. Everyone who roots his device should be aware of that.
Wait for the flashable ZIPs,
Click to expand...
Click to collapse
So, instead of OTA (over-the-air), you can simply download the image files directly from Google Android's site: https://developers.google.com/android/nexus/images#nakasi

topet2k12001 said:
Hi,
As per: http://forum.xda-developers.com/showpost.php?p=47648484&postcount=2342
So, instead of OTA (over-the-air), you can simply download the image files directly from Google Android's site: https://developers.google.com/android/nexus/images#nakasi
Click to expand...
Click to collapse
Aha, i see. So maybe because i've rooted my nexus 7, and i've also got a different kernel for MultiRom( I've installed ubunto touch on my device). ... Those the reasons that leads the installation to be failed?
Anyway, my system auto downloaded the update, it name was "nakasi".
I tried to go to Recover mode, and tried to flash the nakasi ZIP file and flash it,,, but the operation was failed!
What should i do?
How i get auto update installation for kitkat on my nexus 7?
Another question, if i downloaded the Factory image from the link you gave me: https://developers.google.com/android/nexus/images#nakasi and flash it in Recovery Mode... Let say it will success? then i''ll lose auto system update on my nexus in future - because it will be installed manually.
=========
Please Copy the questions in your reply, and post the reply below each one.
Thanks

You modified your rom, therefore, you cannot ota. Use the full images or restore the rom to normal (kernel and whatever else you did).

topet2k12001 said:
Hi,
As per: http://forum.xda-developers.com/showpost.php?p=47648484&postcount=2342
So, instead of OTA (over-the-air), you can simply download the image files directly from Google Android's site: https://developers.google.com/android/nexus/images#nakasi
Click to expand...
Click to collapse
That quote isn't exactly correct. My N7 (tilapia) is rooted, unlocked & twrp recovery. The OTA worked fine. I had to reroot (which us normal), but its clear evidence that's contrary to "OTA's will never work on a system that has been modified in some way". In fact, wug's toolkit thread has multiple comments where people go it the OTA after rooting, unlocking & installing a different recovery. That said, mods MAY result in OTA's failing.
Sent from my Nexus 7 using XDA Premium 4 mobile app

khaytsus said:
You modified your rom, therefore, you cannot ota. Use the full images or restore the rom to normal (kernel and whatever else you did).
Click to expand...
Click to collapse
Can you guide me how to install kitkat on my nexus 2012 - rooted and modified ROM.
What do I need?

Another 4.4 Upgrade failure
I am having problems with the OTA upgrade too. However I am running a unmodified/rooted version of 4.3. I have also tried sideloading the factory zip and doing OTA and sideload from a factory reset.
I get the dead android and red triangle error and if I go to the restore menu then this is the error report I get each time
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
/system/apps/hangouts.apk produces some type of verfication error.
I can then reboot and I am back to 4.3
Any thoughts on solutions are gratefully recieved

Mob_Dev said:
Can you guide me how to install kitkat on my nexus 2012 - rooted and modified ROM.
What do I need?
Click to expand...
Click to collapse
You can use this ZIP( http://forum.xda-developers.com/showthread.php?t=2528090) file flash using recovery. You can use cyanogenmod window installer to give nexus new life and then revert to kitkat. Using that zip. This zip can update via ota. Just help
Sent from my Nexus 7 using XDA Premium 4 mobile app
PS: cyanogenmod window installer auto root your rom

dbgeek said:
That quote isn't exactly correct. My N7 (tilapia) is rooted, unlocked & twrp recovery. The OTA worked fine. I had to reroot (which us normal), but its clear evidence that's contrary to "OTA's will never work on a system that has been modified in some way". In fact, wug's toolkit thread has multiple comments where people go it the OTA after rooting, unlocking & installing a different recovery. That said, mods MAY result in OTA's failing.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
We are probably agreeing to refer to the same thing; maybe it was just a little miscommunication.
If we take only the first sentence of the quoted post "as-is", then it may contextually be construed as an over-generalization (to which, I agree that it is not exactly correct). However if we read the entirety of the quoted post, it was explained further that if a user has a "different kernel and multiROM-injected init), then OTA cannot be applied.
...to which, this thread's OP eventually mentioned that he has "a different kernel for MultiROM" installed.
But as far as being able to receive the OTA, yes I did receive it (rooted and running MultiROM); I just couldn't apply the OTA update. To solve, I performaed a "fresh install", i.e. download and install factory image method.

yusopa said:
You can use this ZIP( http://forum.xda-developers.com/showthread.php?t=2528090) file flash using recovery. You can use cyanogenmod window installer to give nexus new life and then revert to kitkat. Using that zip. This zip can update via ota. Just help
Sent from my Nexus 7 using XDA Premium 4 mobile app
PS: cyanogenmod window installer auto root your rom
Click to expand...
Click to collapse
I am following this guide to install Android kitkat on my nexus 2012 (Wifi only): http://www.droidviews.com/install-kitkat-factory-image-on-nexus/
But if you can see the last step satisfy that i need to flash the 4.4 Factory Image, type, using the following command:
fastboot -w update image-nakasi-krt16s.zip
Click to expand...
Click to collapse
The problem is that, the nakasi file i downloaded from here: https://developers.google.com/android/nexus/images
is not a ZIP file!. It's (.tar) file. And i can't process that command!!
Let me know what is the problem.
Thanks in advance

topet2k12001 said:
We are probably agreeing to refer to the same thing; maybe it was just a little miscommunication.
If we take only the first sentence of the quoted post "as-is", then it may contextually be construed as an over-generalization (to which, I agree that it is not exactly correct). However if we read the entirety of the quoted post, it was explained further that if a user has a "different kernel and multiROM-injected init), then OTA cannot be applied.
...to which, this thread's OP eventually mentioned that he has "a different kernel for MultiROM" installed.
But as far as being able to receive the OTA, yes I did receive it (rooted and running MultiROM); I just couldn't apply the OTA update. To solve, I performaed a "fresh install", i.e. download and install factory image method.
Click to expand...
Click to collapse
My bad. I read the "different kernel..." as an example of mods that might be made, that could cause failure, not a specific listing of mods that would cause a failure (implying that if the mod's not on the list then it wouldn't be a problem).

So i have the same problem, but aditionally my Windows 8 is unable to recognize my Nexus 7 while in recovery mode and i can't mount the sdcard to install a new rom. Only recognizes it as "grouper". Any advice?

I think Wug Fresh for nexus toolkit can help you guy to bring back your nexus to life. I use from the start.
Sent from my Nexus 7 using XDA Premium 4 mobile app

[Info] Rooted user? Learn to update properly

*The below post covers up to 4.4.4 only. for 5.0, read this thread: http://forum.xda-developers.com/goo...asic-overview-root-options-lollipop-t2947144*
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I see a lot of threads asking about updating to Lollipop and about returning to stock to receive OTA updates.. from rooted users.
I have created this thread as I have strong feelings about rooted users and OTA's in general, so I wanted to collect my thoughts together in a single thread to hopefully persuade rooted users to avoid OTA updates. Of course, you're free to choose to ignore this.
OTA's are simple for unrooted, noob users. They are minimal effort, quick and require no knowledge. However they have a propensity to go wrong - often resulting in a user having to factory reset to get things working.
OTA's are designed to be small to save on data usage. This is achieved by not supplying the entire ROM, kernel or app, but instead, including patches. These patch files (*.p) will unpack the recovery.img, bootloader.img, boot.img or *.apk and insert the new code into it. This means the OTA expects an exact version to install. You cannot skip an OTA and expect to apply a later one because the code in the patch might not "fit". Also, this is why modified users cannot apply an OTA. There are ways for rooted, stock kernel, no modification users to apply OTA updates but it is not recommended
Please note, rooted users will still receive the OTA notification. You do not need to apply it though. Some Custom ROMS even receive it.
Well if you are modified, you have to first return completely to stock to apply an OTA. This is a relatively long process compared to other options available to you. If you are simply rooted with stock kernel and no modifications, you can simply re-apply root after accepting the OTA, but it's a bit messy and still - it's an OTA that can go wrong. I think part of OTA's appeal is you can do it anywhere - but this is also it's biggest problem. rooted users need resources to be available to them so they can remedy whatever needs remedying after application.
In short, it's just not the best option, Why would anyone ever choose "not the best"?
It all depends what you want to keep going forward.
I don't want root or custom recovery
If you no longer want root, simply return to stock using google's factory images. The factory image package contains all the files needed to return to stock:
- boot.img
- recovery.img
- bootloader.img
- system.img
- cache.img
- userdata.img
- radio.img
It also includes a windows batch file (.bat) and a Linux shell script (.sh) that will automate the above. This will wipe your data.
If you don't want to lose your sdcard data, if you have a custom recovery, you can factory reset, fastboot flash individually the recovery.img, system.img and boot.img as this will keep /data partition in tact, which is where your /sdcard is located
I want to keep root
You have a couple options here.
You could like above, fastboot flash individually the system.img and boot.img (not recovery.img) then reflash supersu from your custom recovery. Please note, with lollipop as of now, you need as special modified boot.img, not the stock one - so this still is not the quickest method.
Alternatively, you can flash a pre-rooted zip*. Within a couple of hours of the factory image becoming available, guys from XDA will release pre-rooted zips that you simply flash from a custom recovery. This will be a quick process. Put the zip on your /sdcard, boot into recovery and flash it.
With both these options, you very well may need to factory reset after flashing roms, especially if it's a version jump - just as you may need to do with an OTA update. The benefit of being rooted however, is that you can use titanium backup to backup your apps and take a Nandroid backup too, rooted users upgrading should keep these available on the sdcard before updating.
*Please note with Android 5.0 Lollipop, you need to flash a ROM.zip, Permissive kernel and SuperSU all at once. You have to download all 3 files and flash them one after the other in that order. You can flash some custom kernels, such as elementalx straight over permissive kernel. Also, you can ONLY flash elementalX as it allows root to run at boot (without permissive kernel) however, some apps NEED permissive to run anyway
OTA is designed for noobs. Granted, those root users asking how to return to stock or thinking OTA is the only update method available - are also noobs... If you're going to be rooted, you should understand what you have and what it means to be rooted. Familiarise yourselves with fastboot. Familiarise yourself with your recovery. Learn how to take backups and you will get much more out of your phone that constantly wasting time returning to stock, applying OTA's then re-rooting. You're wasting time doing this - it's a fools errand. I hope this thread helps to open your eyes and your minds.
If you still want to (return to stock in order to) accept OTA updates, even after reading this thread (perhaps because doing things properly mean more work for you) then perhaps you shouldn't be rooted. Having, maintaining and understanding root takes effort and if you're not willing to put the time in, you will become a danger to your phone and possibly a drain on this forum too We write lots of guides and info threads for your benefit. If you have questions, please just ask.
adb and fastboot. What is it? How can it help you? - basic information about adb and fastboot (by @rootSU)
All you need to know about Android | Read this before you post/root ! - Understand the basics before you root (by @abaaaabbbb63 )
How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5 - Understand how to undo whatever you do before you root (by @abaaaabbbb63 )
OTA Help-Desk - Understand how OTA's work and what this means if you are rooted (by @Sandman-007)

Always informative Mr. RootSU

stankyou said:
Always informative Mr. RootSU
Click to expand...
Click to collapse
Thanks. I try

Thanks for this - I am rooted and have a basic knowledge of fastboot from unlocking and rooting the N5 last year and the N4 before that.. however, as I've not touched it for about that long it's probably about time I start the reading process again to get ready for some Lollipop action!
I had been planning on getting the factory images from Google and using fastboot to fresh flash it - looks like that's not really necessary tho?
Thanks
...sent from the Nexus 5000

I still remember rocking your dGB ROM during the Desire days. LOL

but my rooted and modified nexus 5 did receive an ota.. can i or should i apply it? or my rooted and unmodified nexus 5 did receive an ota.. can you decribe to me what would happen if i do apply it?

Thanks for this, really informative.

simms22 said:
but my rooted and modified nexus 5 did receive an ota.. can i or should i apply it? or my rooted and unmodified nexus 5 did receive an ota.. can you decribe to me what would happen if i do apply it?
Click to expand...
Click to collapse
Ooh good point. I'll mention that.

androidsnax said:
Thanks for this - I am rooted and have a basic knowledge of fastboot from unlocking and rooting the N5 last year and the N4 before that.. however, as I've not touched it for about that long it's probably about time I start the reading process again to get ready for some Lollipop action!
I had been planning on getting the factory images from Google and using fastboot to fresh flash it - looks like that's not really necessary tho?
Thanks
...sent from the Nexus 5000
Click to expand...
Click to collapse
If you want to keep root, The best thing to do would be to wait for a pre-rooted rom.zip - which should also contain the custom boot.img needed to give root permissions...
Just make sure you do all your backups first if you want to keep stuff.

Oh and if anyone has any suggestions for things I should include in the OP, please let me know.

rootSU said:
I see a lot of threads asking about updating to Lollipop and about returning to stock to receive OTA updates.. from rooted users.
I have created this thread as I have strong feelings about rooted users and OTA's in general, so I wanted to collect my thoughts together in a single thread to hopefully persuade rooted users to avoid OTA updates. Of course, you're free to choose to ignore this.
OTA background
OTA's are simple for unrooted, noob users. They are minimal effort, quick and require no knowledge. However they have a propensity to go wrong - often resulting in a user having to factory reset to get things working.
OTA's are designed to be small to save on data usage. This is achieved by not supplying the entire ROM, kernel or app, but instead, including patches. These patch files (*.p) will unpack the recovery.img, bootloader.img, boot.img or *.apk and insert the new code into it. This means the OTA expects an exact version to install. You cannot skip an OTA and expect to apply a later one because the code in the patch might not "fit". Also, this is why modified users cannot apply an OTA. There are ways for rooted, stock kernel, no modification users to apply OTA updates but it is not recommended
Why shouldn't rooted users apply OTA's if they can?
Well if you are modified, you have to first return completely to stock to apply an OTA. This is a relatively long process compared to other options available to you. If you are simply rooted with stock kernel and no modifications, you can simply re-apply root after accepting the OTA, but it's a bit messy and still - it's an OTA that can go wrong. I think part of OTA's appeal is you can do it anywhere - but this is also it's biggest problem. rooted users need resources to be available to them so they can remedy whatever needs remedying after application.
In short, it's just not the best option, Why would anyone ever choose "not the best"?
So what are the actual options?
It all depends what you want to keep going forward.
I don't want root or custom recovery
If you no longer want root, simply return to stock using google's factory images. The factory image package contains all the files needed to return to stock:
- boot.img
- recovery.img
- bootloader.img
- system.img
- cache.img
- userdata.img
- radio.img
It also includes a windows batch file (.bat) and a Linux shell script (.sh) that will automate the above. This will wipe your data.
If you don't want to lose your sdcard data, if you have a custom recovery, you can factory reset, fastboot flash individually the recovery.img, system.img and boot.img as this will keep /data partition in tact, which is where your /sdcard is located
I want to keep root
You have a couple options here.
You could like above, fastboot flash individually the system.img and boot.img (not recovery.img) then reflash supersu from your custom recovery. Please note, with lollipop as of now, you need as special modified boot.img, not the stock one - so this still is not the quickest method.
Alternatively, you can flash a pre-rooted zip. Within a couple of hours of the factory image becoming available, guys from XDA will release pre-rooted zips that you simply flash from a custom recovery. This will be a quick process. Put the zip on your /sdcard, boot into recovery and flash it.
With both these options, you very well may need to factory reset after flashing roms, especially if it's a version jump - just as you may need to do with an OTA update. The benefit of being rooted however, is that you can use titanium backup to backup your apps and take a Nandroid backup too, rooted users upgrading should keep these available on the sdcard before updating.
Conclusion
OTA is designed for noobs. Granted, those root users asking how to return to stock or thinking OTA is the only update method available - are also noobs... If you're going to be rooted, you should understand what you have and what it means to be rooted. Familiarise yourselves with fastboot. Familiarise yourself with your recovery. Learn how to take backups and you will get much more out of your phone that constantly wasting time returning to stock, applying OTA's then re-rooting. You're wasting time doing this - it's a fools errand. I hope this thread helps to open your eyes and your minds.
useful links
adb and fastboot. What is it? How can it help you? - basic information about adb and fastboot (by @rootSU)
All you need to know about Android | Read this before you post/root ! - Understand the basics before you root (by @abaaaabbbb63 )
How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5 - Understand how to undo whatever you do before you root (by @abaaaabbbb63 )
OTA Help-Desk - Understand how OTA's work and what this means if you are rooted (by @Sandman-007)
Click to expand...
Click to collapse
Seems like we've gone with what I previously said about people who want OTAs while rooted
You should also add that if one STILL wants to take OTAs for some silly reason, even after reading this thread, he/she should stay away from root access completely and use their phone like any other unknowledgable/ignorant person would, like someone that OTAs were meant for. :angel:

Lethargy said:
Seems like we've gone with what I previously said about people who want OTAs while rooted
You should also add that if one STILL wants to take OTAs for some silly reason, even after reading this thread, he/she should stay away from root access completely and use their phone like any other unknowledgable/ignorant person would, like someone that OTAs were meant for. :angel:
Click to expand...
Click to collapse
Yep

Well said, sir. Nice work.

stankyou said:
I still remember rocking your dGB ROM during the Desire days. LOL
Click to expand...
Click to collapse
Ha. Oh wow.

Thank you so much.

Nice information thx

rootSU said:
Oh and if anyone has any suggestions for things I should include in the OP, please let me know.
Click to expand...
Click to collapse
Probably goes without saying but a link to a pre-rooted ROM where you mention this option would be great. When available of course.
Only because finding a stock pre-rooted ROM at times like these can be a task even for vets. Having it right there would be very useful for those peaking in on this already informative thread.
Thanks

tgrgrd00 said:
Probably goes without saying but a link to a pre-rooted ROM where you mention this option would be great. When available of course.
Only because finding a stock pre-rooted ROM at times like these can be a task even for vets. Having it right there would be very useful for those peaking in on this already informative thread.
Thanks
Click to expand...
Click to collapse
na, very easy. basic aosp/stock rooted roms(these are what you want) will be in the android development section of the nexus 5. always. in the original development section, there will be original roms only.

rootSU said:
If you no longer want root, simply return to stock using google's factory images. The factory image package contains all the files needed to return to stock:
- boot.img
- recovery.img
- bootloader.img
- system.img
- cache.img
- userdata.img
- radio.img
It also includes a windows batch file (.bat) and a Linux shell script (.sh) that will automate the above. This will wipe your data.
If you don't want to lose your sdcard data, if you have a custom recovery, you can factory reset, fastboot flash individually the recovery.img, system.img and boot.img as this will keep /data partition in tact, which is where your /sdcard is located @Sandman-007)
Click to expand...
Click to collapse
Also, you can edit flash-all.bat and find entry:
Code:
nulfastboot -w update image-hammerhead-ktu84p.zip
and remove "-w" and save it. Then just execute flash-all.bat and the script will flash all the images without wiping data. I always do that way and never had data wiped.

Nice advices once again and I totally agree with OTA subject.
I used Lollipop a few days then I went back to KK and I do not plan to update soon. Since I didn't follow recent discussions about Lollipop I have a question: flashing a rooted flashable zip won't be a mess? e.g unavailable /sdcard, a 32Gb storage that becomes 16Gb (actually that's what I had - clean flash of course)... Lollipop is really different compared to KK so would it not be more appropriate to flash the factory imgs (without restoring user data from KK) before enjoying Lollipop's stuff?

Warning about Lollipop AOSP (and factory) ROMs. - broken recovery

All,
Please be aware of this. Flashing a compiled lollipop AOSP ROM may break your recovery. Actually, although I expect it - maybe you wont - but also factory images do this)
Zips may contain the following files:
/system/recovery.init.boot.p
/system/bin/install-recovery.sh
One is a recovery patch and the other is a script to run on boot and patch your recovery. If you flash a lollipop AOSP ROM and boot immediately, if these exist, your recovery will break.
Flashing superSU immediately after the ROM should
prevent the issue as that replaces /system/bin/install-recovery.sh with its own /system/etc/install-recovery.sh used to call root.
It may just be better for everyone to remove those from the zips before flashing (or uploading) though. If your bootloader is unlocked, you're OK, you can just fastboot flash your recovery back. However if its locked, you'll waste hours backing up your sdcard, preparing to unlock your bootloader and wipe the device, so beware and be careful
Dan

Thanks for heads up

Lukijs said:
Thanks for heads up
Click to expand...
Click to collapse
No probs.

Thanks bro ?
Gesendet von meinem Nexus 5

Do you mean flashing the ones built as zips or any?
Sent from my Android 5.0 Nexus 5

Ben36 said:
Do you mean flashing the ones built as zips or any?
Sent from my Android 5.0 Nexus 5
Click to expand...
Click to collapse
Anything not a dev preview. Just check the zip before flashing. If its a zip that contains .DAT archives, you can check from TWRP file manager after flash.
Although official may also have this one released. Not sure. Maybe just the OTA as some of the compiled ROMs seem to be using the OTA method instead of user debug or user method.

You mean something like this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

AA1973 said:
You mean something like this?
Click to expand...
Click to collapse
Yep. Unless whomever compiled that changed the make to exclude those files, they'll be there. It shouldn't be a problem for most who will immediately flash superSU. Its just for anyone who attempts to boot before flashing superSU as the scripts run at boot then delete themselves.
Anyone not wanting root but wanting to keep recovery, you can check and delete the files using the recovery file manager (philz or TWRP) once flashed. Just don't boot until you do. The problem with the OTA zip is the .DAT files are harder to analyse unlike a normal zip.

Multi Rom decided to intervene by cancelling the boot up process, although I had flashed SuperSU.

Can we replace the stock recovery by TWRP.img and then flashall.bat ?
Envoyé de mon Nexus 5 en utilisant Tapatalk

Thanks
Oh - I'm so happy that I flashed SU right after the ROM... ;p
Ah well, unlocked bootloader anyways, but still good to know.
---------- Post added at 10:03 AM ---------- Previous post was at 09:59 AM ----------
vercety974 said:
Can we replace the stock recovery by TWRP.img and then flashall.bat ?
Envoyé de mon Nexus 5 en utilisant Tapatalk
Click to expand...
Click to collapse
Does the flashall.bat include a line : fastboot flash recovery recovery.img?
You can check by opening the bat file in notepad..
If it has, then no. Well yes, but it will overwrite your current recovery again.

vercety974 said:
Can we replace the stock recovery by TWRP.img and then flashall.bat ?
Envoyé de mon Nexus 5 en utilisant Tapatalk
Click to expand...
Click to collapse
You could if their flash all includes a recovery. I'm not sure about AOSP ROMs generated as full images. The patch I have seen comes from building AOSP from source and distributing the resultant ota package (which is a full rom)

Stock ROMs have this feature, it's nothing new.

Rusty! said:
Stock ROMs have this feature, it's nothing new.
Click to expand...
Click to collapse
Stock OTA zips have this feature. Factory images do not, yet that is irrelevant. The point here is that compiled AOSP ROMs should not be distributed as OTA packages, yet here we are, with rushed, ill-conceived builds causing this issue. This is new for AOSP flashable zips. I've been flashing AOSP since cupcake and its definitely new to me and since others have fallen in to this trap, let's assume its new to them too.

Yes, factory images do have this.

Rusty! said:
Yes, factory images do have this.
Click to expand...
Click to collapse
No, They have then shell script. Not the patch file.
..and from the thread title. Again - I remind you that it is irrelevant

I found this line(/system/bin/install-recovery.sh) in file_contexts, is it where i need to delete it?

jonathanxx1 said:
I found this line(/system/bin/install-recovery.sh) in file_contexts, is it where i need to delete it?
Click to expand...
Click to collapse
If you have file_contexts then you are flashing a .DAT OTA. You can't get to the files until you flash the ROM. Flashing the ROM unpacks the .DAT archives into /system at which point, you could use a recovery based file manager or adb to delete the 2 files mentioned in post 1. This is assuming you're not going to root it. If you root it, you *should* be OK but sometimes its best to be safe than sorry.

rootSU said:
Stock OTA zips have this feature. Factory images do not, yet that is irrelevant. The point here is that compiled AOSP ROMs should not be distributed as OTA packages, yet here we are, with rushed, ill-conceived builds causing this issue. This is new for AOSP flashable zips. I've been flashing AOSP since cupcake and its definitely new to me and since others have fallen in to this trap, let's assume its new to them too.
Click to expand...
Click to collapse
I just extracted the factory system.img of the 3rd revision of the L Preview, and it has both files mentioned in the OP.
Also, saying that compiled AOSP ROMs should not be distributed as OTA packages is not true. This has been done since this feature has been available.
I just finished building Lollipop for the first time. The files mentioned in the OP are not present in the out/target/product/hammerhead/system folder, or any other folder that I can find. Can't confirm if they are in the system.new.dat file, or after flashing since I haven't flashed it yet (maybe tomorrow). Hopefully there is an option to build a folder-based zip instead of these .dat files.
Scripts that install recovery have never been an issue unless a recovery.img is present in the zip, or there is a backup cached in a partition. Maybe that has changed. This will be figured out soon enough.
Still good advice to flash supersu before booting until this is understood.

upndwn4par said:
I just extracted the factory system.img of the 3rd revision of the L Preview, and it has both files mentioned in the OP.
Also, saying that compiled AOSP ROMs should not be distributed as OTA packages is not true. This has been done since this feature has been available.
I just finished building Lollipop for the first time. The files mentioned in the OP are not present in the out/target/product/hammerhead/system folder, or any other folder that I can find. Can't confirm if they are in the system.new.dat file, or after flashing since I haven't flashed it yet (maybe tomorrow). Hopefully there is an option to build a folder-based zip instead of these .dat files.
Scripts that install recovery have never been an issue unless a recovery.img is present in the zip, or there is a backup cached in a partition. Maybe that has changed. This will be figured out soon enough.
Still good advice to flash supersu before booting until this is understood.
Click to expand...
Click to collapse
When I talk about irrelevant factory images, I'm not talking about unofficial previews. ...and yes it has changed. It doesn't need a recovery.img because it has a .p which is a patch file. The patch file upgrades an existing recovery by patching new code into it. Obviously if the recovery is not stock, that code kills recovery. There's not really much to understand. If the files are there, take them out.

Stock Nexus 6 (Verizon) will not update!

Hi guys,
As I wrote in the title, my Verizon Nexus 6 will not update. When I get a notification for the software update, I see that it downloads and is ready to restart the phone so it will install the update...
but when I do, it will display the android icon with the word "error" above it. No error number or details about why it did not work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Things I tried already are:
formatting the phone (both through the settings menu as well as the stock bootloader)
deleting data and cache in Google Services Framework (via settings/apps/all apps)
I have more than enough space in my storage; more than 2/3rds of my storage is free space, so I really am having trouble wrapping my head around why this software update is failing to install. And since all the threads and help things I find are for rooted phones, I am having trouble finding something that would offer an answer. I was hoping to keep this phone stock as long as possible, which is an oddity for me because I usually want to root my phone immediately. I guess I just really like this phone as stock. And other than this update that fails to load, the phone has no other issues, other than a few emojis that fail to show, but I feel like that's from the software not being able to update for the 6 months that I've been trying to update it.
Any help with this would be greatly appreciated! Thank you!!

Is your device unlocked? Have you tried to sideload the update?
If your device is unlocked you can use NRT to update without loosing any data.

PickelledEggs said:
Hi guys,
As I wrote in the title, my Verizon Nexus 6 will not update. When I get a notification for the software update, I see that it downloads and is ready to restart the phone so it will install the update...
but when I do, it will display the android icon with the word "error" above it. No error number or details about why it did not work.
Things I tried already are:
formatting the phone (both through the settings menu as well as the stock bootloader)
deleting data and cache in Google Services Framework (via settings/apps/all apps)
I have more than enough space in my storage; more than 2/3rds of my storage is free space, so I really am having trouble wrapping my head around why this software update is failing to install. And since all the threads and help things I find are for rooted phones, I am having trouble finding something that would offer an answer. I was hoping to keep this phone stock as long as possible, which is an oddity for me because I usually want to root my phone immediately. I guess I just really like this phone as stock. And other than this update that fails to load, the phone has no other issues, other than a few emojis that fail to show, but I feel like that's from the software not being able to update for the 6 months that I've been trying to update it.
Any help with this would be greatly appreciated! Thank you!!
Click to expand...
Click to collapse
You might try clearing the cache partition in recovery and reboot. Maybe the next OTA will be install without issues.

lol!
if you made any kind of changes, chances are that any ota will not work. but that's alright, all you have to do is flash the factory image. it would've been updated already if you did that instead of writing out your post. you can grab it here https://developers.google.com/android/nexus/images

simms22 said:
lol!
if you made any kind of changes, chances are that any ota will not work. but that's alright, all you have to do is flash the factory image. it would've been updated already if you did that instead of writing out your post. you can grab it here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
I don't think you read my post at all... I didn't make any changes. My phone is fully stock. No root at all. No unlock. No modifications whatsoever The ota Software update just will not work.
gee2012 said:
You might try clearing the cache partition in recovery and reboot. Maybe the next OTA will be install without issues.
Click to expand...
Click to collapse
I tried going in to recovery mode, but when I do, it gives me the same android error icon, but instead of "error" it says "no command"

Timza said:
Is your device unlocked? Have you tried to sideload the update?
If your device is unlocked you can use NRT to update without loosing any data.
Click to expand...
Click to collapse
Nope. Not unlocked. No modification whatsoever

PickelledEggs said:
Nope. Not unlocked. No modification whatsoever
Click to expand...
Click to collapse
If you nothing else works, I would try to sideload the update by downloading the image from Google's Factory Images for Nexus Devices page.

PickelledEggs said:
Nope. Not unlocked. No modification whatsoever
Click to expand...
Click to collapse
Best is to enable OEM UNLOCKING and usb debugging in developer options, reboot into fastboot and unlock the bootloader and after the reboot flash the latest MMB29S firmware as @simms22 allready stated. Flash the img`s seperately in fastboot, all i would flash personaly is the system and boot img.

Timza said:
If you nothing else works, I would try to sideload the update by downloading the image from Google's Factory Images for Nexus Devices page.
Click to expand...
Click to collapse
gee2012 said:
Best is to enable OEM UNLOCKING and usb debugging in developer options, reboot into recovery and unlock the bootloader and after the reboot flash the latest MMB29S firmware as @simms22 allready stated. Flash the img`s seperately in fastboot, all i would flash personaly is the system and boot img.
Click to expand...
Click to collapse
Oh ok, I must have misinterpereted what SImmz was saying, then. I got in to recovery mode and wiped cache finally, so I will see if that works, otherwise I'll try your guys' other suggestions

PickelledEggs said:
Oh ok, I must have misinterpereted what SImmz was saying, then. I got in to recovery mode and wiped cache finally, so I will see if that works, otherwise I'll try your guys' other suggestions
Click to expand...
Click to collapse
I had this issue with my Nexus 7 (stock) - wiped the cache partition in recovery, and waited for OTA to appear again - and it worked.

BTW, you don't need root to make certain changes(I don't know what changes, but I know many don't get ota because of). or google just made it to sensitive.

Timza said:
If you nothing else works, I would try to sideload the update by downloading the image from Google's Factory Images for Nexus Devices page.
Click to expand...
Click to collapse
You can only sideload OTA`s in stock recovery afaik, not complete images.

gee2012 said:
You can only sideload OTA`s in stock recovery afaik, not complete images.
Click to expand...
Click to collapse
Ah, my mistake. I (wrongly) assumed OTAs were included on that download page.

is using nexus root tool kit let you flash with su 2.5.2 or it using the lastest 2.66? or that makes no difference when flashing stock image?

MikePancake6 said:
is using nexus root tool kit let you flash with su 2.5.2 or it using the lastest 2.66? or that makes no difference when flashing stock image?
Click to expand...
Click to collapse
The latest version of NRT (v2.1.4) uses SuperSU 2.6.6.

Timza said:
The latest version of NRT (v2.1.4) uses SuperSU 2.6.6.
Click to expand...
Click to collapse
is there any way to use 2.5.2, or flashing a custom rom will system root or will it be systemless root anyhow?

MikePancake6 said:
is there any way to use 2.5.2, or flashing a custom rom will system root or will it be systemless root anyhow?
Click to expand...
Click to collapse
After you flash with TWRP (a step with NRT). When you opt to reboot system, you will get a message asking if you would like to install SuperSU. If you swipe to install you will have a "system root". If you opt to not install, you will have a systemless root.
Personally, I have a "system root", and it seems to be working fine, whereas before, I was having an issue with the systemless root.

Timza said:
After you flash with TWRP (a step with NRT). When you opt to reboot system, you will get a message asking if you would like to install SuperSU. If you swipe to install you will have a "system root". If you opt to not install, you will have a systemless root.
Personally, I have a "system root", and it seems to be working fine, whereas before, I was having an issue with the systemless root.
Click to expand...
Click to collapse
ok, thank you for all the help. i already unlocked the bootloader using the tool kit.
tonight i will root it and try a custom rom. maybe chrome or pure nexus project, those seem to be stock with extra options and rro customize.

Thanks guys. I just got around to sideloading the update last night and it's working like a dream.
I'll probably root it soon now. I've been feeling the itch recently... Lol
This (so far) is probably my favorite stock phone though. I might keep it stock for a bit longer
Sent from my Nexus 6 using Tapatalk

EMUI 9 root updates

I just looked up a few threads about rooting EMUI 9.
The one and only who kinda managed to do it is the developer of Magisk John Wu.
If you wanna stay updated about rooting EMUI 9 on Huawei P20pro, you should follow this guy:
EMUI9 root
still NO EMUI 9 kernel sources released

Rooting / Magisk is one thing. I think in addition to that we also need a working twrp or some recovery for Emui 9 to be able to flash stuff with relative ease. On top of that the OEM unlock option is greyed out which is problematical itself. So, this is all gonna be a bit complicated.

Well, there is a modded versions of TWRP Mate Rs Porsche with working decryption and for most people including me, oem-unlock is not greyed out when you have unlocked frp and unlocked bootloader.
I'm on the final of EMUI 9. So the last important thing would be a rooted EMUI 9 to get some important things working.
mrabcx said:
Rooting / Magisk is one thing. I think in addition to that we also need a working twrp or some recovery for Emui 9 to be able to flash stuff with relative ease. On top of that the OEM unlock option is greyed out which is problematical itself. So, this is all gonna be a bit complicated.
Click to expand...
Click to collapse

ArtaxXP said:
and for most people including me, oem-unlock is not greyed out when you have unlocked frp and unlocked bootloader.
Click to expand...
Click to collapse
Unlocked frp = oem unlock enabled in dev options
Unlock bootloader and frp itself doesn't cause "enable oem unlock" being greyed out. It's not getting greyed out just by upgrading to pie either. Upgrade to pie and factory reset does!
Good to know about twrp working on p20 pro

Hello, i changed my system font by using huawei themes.
Now it's not possible anymore, to edit photos and use different fonts for editing.
Does anybody have an idea, what i can do?i want to keep the new system font.
I hope to get a usefull help, i really would be grateful.
Sorry for this comment, i doesn't belong at this page

there is already something new on this topic?

not much but some
Heinzx3 said:
there is already something new on this topic?
Click to expand...
Click to collapse

some good news
good news

Rooted on 9.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my CLT-L04 using Tapatalk

Dene_Bluesman said:
Rooted on 9.0 View attachment 4673784
Sent from my CLT-L04 using Tapatalk
Click to expand...
Click to collapse
Yeah awesome! Well done!
John Wu just released some info in a post: EMUI9 root

Dene_Bluesman said:
Rooted on 9.0 View attachment 4673784
Sent from my CLT-L04 using Tapatalk
Click to expand...
Click to collapse
Link pls

mr.mgmg said:
Link pls
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Sent from my CLT-L04 using Tapatalk

Dene_Bluesman said:
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Sent from my CLT-L04 using Tapatalk
Click to expand...
Click to collapse
There are alot files
https://github.com/topjohnwu/magisk_files/tree/master/canary_builds
Any file i must download and flash

mr.mgmg said:
There are alot files
https://github.com/topjohnwu/magisk_files/tree/master/canary_builds
Any file i must download and flash
Click to expand...
Click to collapse
Would like someone to drop round and flash it for you too? Do some reading, or don't flash.

purple patch said:
Would like someone to drop round and flash it for you too? Do some reading, or don't flash.
Click to expand...
Click to collapse
I think the Q not for you, just keep silent

mr.mgmg said:
I think the Q not for you, just keep silent
Click to expand...
Click to collapse
his point is, even you got the question wrong,
no files from that list will root your emui 9 simply by flashing any of it,
you gonna need a copy of RECOVERY_RAMDIS.img pulled from update.app of latest emui 9.0 firmware,
copy it to device with latest canary magisk & magisk manager installed,
patching the .img using that canary manager, and you will get patched_boot.img stored in download folder in that device,
copy it to your pc and flash it to recovery_ramdisk partition using fastboot,
or if you really are that lazy, simply download the prepatched one here : https://drive.google.com/file/d/1rhl405-ALbYrtGHilrNUR5Fuq4yATvTH/view?usp=drivesdk
and flash it from fastboot to your recovery_ramdisk partition
boot by holding vol up button

otonieru said:
his point is, even you got the question wrong,
no files from that list will root your emui 9 simply by flashing any of it,
you gonna need a copy of RECOVERY_RAMDIS.img pulled from update.app of latest emui 9.0 firmware,
copy it to device with latest canary magisk & magisk manager installed,
patching the .img using that canary manager, and you will get patched_boot.img stored in download folder in that device,
copy it to your pc and flash it to recovery_ramdisk partition using fastboot,
or if you really are that lazy, simply download the prepatched one here : https://drive.google.com/file/d/1rhl405-ALbYrtGHilrNUR5Fuq4yATvTH/view?usp=drivesdk
and flash it from fastboot to your recovery_ramdisk partition
boot by holding vol up button
Click to expand...
Click to collapse
Thanks for help

It will seem dumb for some of you but important to me and others (i Hope there are some lol)..... so just to be clear :
1- do we have to follow these steps AFTER installing emui 9 ? coming from emui 8.1 161 with evira kernel and using mods i wanna start 100% fresh because first time i installed emui 9 163 i came back a week later because of battery consuption that was way worse and real bad SOT so it's major to me to proceed the best way - i have to go first to twrp and wipe all, data+system+caches before flashing emui 9 ?
2- any reason not to use the easiest way ? why to prefer the complicated one : pulling the file from update.app and copy and etc....?
3- magisk modules will be usable ?
Thanks to those of you who will bring light or give me confident in re-installing pie.
And of course merry Christmas everyone

deltaman83 said:
It will seem dumb for some of you but important to me and others (i Hope there are some lol)..... so just to be clear :
1- do we have to follow these steps AFTER installing emui 9 ? coming from emui 8.1 161 with evira kernel and using mods i wanna start 100% fresh because first time i installed emui 9 163 i came back a week later because of battery consuption that was way worse and real bad SOT
2- any reason not to use the easiest way ? why to prefer the complicated one : pulling the file from update.app and copy and etc....?
3- magisk modules will be usable ?
Thanks to those of you who will bring light or give me confident in re-installing pie.
And of course merry Christmas everyone
Click to expand...
Click to collapse
1. Steps is for rooting, if you wanna start fresh, you can consider wiping /data after update. So none of your previous mods data no cache will tag along to your EMUI 9
2. Reason is, the difference of firmware versioning betweem region. You told me you updated to .163. My prepatched ramdisk is from C636 .168, although most of the time it can work universally across region and version (just like how custom recovery work in a universal way), there's no telling what huawei actually did between version update. So its always best to use and patch your own file. Since it will give you confidence, its your own doing after all.
3. I use youtubevanced, LKT, systemless host, swap torpedo, busybox and detach magisk modules, all work just fine on EMUI 9. You only need to redownload and reinstall all the modules (if you didnt wipe data, like me), because installation from oreo version wont work straight away on EMUI 9.
for extra information, SafetyNet and MagiskHide all working as well. I can use my banking app just fine.
as for precaution info,
i suggest you to use the flashy tools to install EMUI 9 from PC instead of using HuRU,
i did the HuRU way, and ends up with a messed up software serial number and broken recovery partition, meaning i can't flash TWRP, stock recovery nor a patched recovery ramdisk to acquired root. It will all fall to an error screen, telling me no recovery image available inside the system, and ask me to update system again. Fortunately the phone still boot just fine to system.
scratched my heads for hours until i manage to resolved it by flashing Recovery META and Recovery Vendor image through fastboot. After that i can reflash stock recovery, and the patched one (after i confirm stock one work fine)

Thanks a lot for your answers.
---------- Post added at 06:42 PM ---------- Previous post was at 06:24 PM ----------
otonieru said:
1. Steps is for rooting, if you wanna start fresh, you can consider wiping /data after update. So none of your previous mods data no cache will tag along to your EMUI 9
Click to expand...
Click to collapse
One thing no clear to me is what i do of the magisk canary Zip file...?.... ? As twrp not working on emui 9...