Related
Tried to update my wife's Nexus 10 tonight. It's unlocked and rooted, formerly on the stock version of Jelly Bean. I thought this would be an easy update since it was stock jellybean to kitkat with the official OTA file but I guess I was wrong. Got the OTA update notification so I allowed it to reboot and install. CWM Touch Recovery picked it up and I told it to install the unsigned zip. Got near the end and it had an error. Now it's stuck in boot (appears to be Kit Kat boot). Just sits on the 4 colored circles going in/out in the middle of the screen.
I need to fix this without wiping data. It's her only computer that she uses daily so she's got a million things on there she uses all the time. If I have to wipe data, she'll be pissed (and I'll lose my hard earned game saves).
Attached is a picture of the error. I've got WUG's toolkit if it's necessary to use to fix this. Any ideas what's going on and how to fix it? Thanks.
Stinger2300 said:
Tried to update my wife's Nexus 10 tonight. It's unlocked and rooted, formerly on the stock version of Jelly Bean. I thought this would be an easy update since it was stock jellybean to kitkat with the official OTA file but I guess I was wrong. Got the OTA update notification so I allowed it to reboot and install. CWM Touch Recovery picked it up and I told it to install the unsigned zip. Got near the end and it had an error. Now it's stuck in boot (appears to be Kit Kat boot). Just sits on the 4 colored circles going in/out in the middle of the screen.
I need to fix this without wiping data. It's her only computer that she uses daily so she's got a million things on there she uses all the time. If I have to wipe data, she'll be pissed (and I'll lose my hard earned game saves).
Attached is a picture of the error. I've got WUG's toolkit if it's necessary to use to fix this. Any ideas what's going on and how to fix it? Thanks.
Click to expand...
Click to collapse
I have a rooted/unlocked Nexus 10, I used wugfresh's kit also. I got the OTA update last night. it installed. CWM never came up or did anything. During one of the boots after the green droid bot was saying "installing" the boot finished, but my green bot is now on his side. stomach open and it says "Error" in red bold letter.
I had to go to work, so I couldnt trouble shoot, but power off/on and soft reset (power+volume up select reset) didnt help. always comes to that "error".
I have data that is also not currently backed up with TBpro. hindsight I should have made sure I turned the scheduler on.
So I'm stuck also. not sure how to proceed. Got one recommendation to flash stock back on. But I think that will for sure wipe all my data. And beyond that, I dont know how, unless WUGs kit will do that.
Your best bet it is to sideload. Grab the OTA and the FULL 4.4
Pull the recovery.img from the full 4.4 rar (its in the zip), fastboot flash it, reboot into bootloader, go to recovery and sideload the OTA and that should restore it just fine
EDIT: http://forum.xda-developers.com/showpost.php?p=47656450&postcount=8
my detailed instructions there for sideloading
planet_x69 said:
Your best bet it is to sideload. Grab the OTA and the FULL 4.4
Pull the recovery.img from the full 4.4 rar (its in the zip), fastboot flash it, reboot into bootloader, go to recovery and sideload the OTA and that should restore it just fine
EDIT: http://forum.xda-developers.com/showpost.php?p=47656450&postcount=8
my detailed instructions there for sideloading
Click to expand...
Click to collapse
I was about to say. whaaaaat? then saw the link with some details. Never done that stuff before, just used other tools kits, like wugs. But doesnt sound to bad. Will try when I get home. I presume when you say into a adb directory, its something on the desktop pc you are connected to. outside of perhaps some drivers, do I need other applications on the PC to facilitate the adb stuff you mention?
jetguat said:
I was about to say. whaaaaat? then saw the link with some details. Never done that stuff before, just used other tools kits, like wugs. But doesnt sound to bad. Will try when I get home. I presume when you say into a adb directory, its something on the desktop pc you are connected to. outside of perhaps some drivers, do I need other applications on the PC to facilitate the adb stuff you mention?
Click to expand...
Click to collapse
Well if you are unfamiliar with the process you will need to get the android SDK installed or find one of the pre-packaged current adb loads. It's very simple, get this package here: http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip# (yes its a crappy ad link but hey the guy packaged it all up so...).
If you are on a PC extract these to a folder of your choice.
Open file manager
Navigage to the folder you extracted the files to
on the left pan select the folder, press SHIFT and Right Click mouse, then select "Open command window here"
You can now follow my instructions from the other page - Do the following below FIRST
If you are prompted to accept security allowance on your device do so. you will likely only see this once you are back into the Android OS not in recovery.
This folder has all the basics you need to fastboot and run adb.
Connect your device to your pc and run >fastboot reboot-bootloader.
If your device restarts and goes into the bootloader you can relax and follow my instructions.
Hope this helps.
One other thing, that su zip is dated, you will need to flash the 1.51 version and you should be good to complete root process.
Wow, this seems about 3 miles over my head but I guess I'll dive in and try it. Thanks for the info. I'm sure I'll be back with problems/questions.
planet_x69 said:
Well if you are unfamiliar with the process you will need to get the android SDK installed or find one of the pre-packaged current adb loads. It's very simple, get this package here: http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip# (yes its a crappy ad link but hey the guy packaged it all up so...).
If you are on a PC extract these to a folder of your choice.
Open file manager
Navigage to the folder you extracted the files to
on the left pan select the folder, press SHIFT and Right Click mouse, then select "Open command window here"
You can now follow my instructions from the other page - Do the following below FIRST
If you are prompted to accept security allowance on your device do so. you will likely only see this once you are back into the Android OS not in recovery.
This folder has all the basics you need to fastboot and run adb.
Connect your device to your pc and run >fastboot reboot-bootloader.
If your device restarts and goes into the bootloader you can relax and follow my instructions.
Hope this helps.
One other thing, that su zip is dated, you will need to flash the 1.51 version and you should be good to complete root process.
Click to expand...
Click to collapse
OK, I downloaded the packaged linked above and extracted it to the desktop. Then I used file manager to "open command window here". Where do I get su zip 1.51? I tried to google a link but they all seemed newer (1.75 for example). Does it matter if it's 1.51 exactly or can it be any version 1.51 or newer? One last question regarding su zip, does that need to be updated after this whole process is complete and I'm up and running again, or does it need to be done before I move on to the instructions you linked to above? Thanks.
Stinger2300 said:
OK, I downloaded the packaged linked above and extracted it to the desktop. Then I used file manager to "open command window here". Where do I get su zip 1.51? I tried to google a link but they all seemed newer (1.75 for example). Does it matter if it's 1.51 exactly or can it be any version 1.51 or newer? One last question regarding su zip, does that need to be updated after this whole process is complete and I'm up and running again, or does it need to be done before I move on to the instructions you linked to above? Thanks.
Click to expand...
Click to collapse
You don't need to root at all but the updated supersu 1.75 will be just fine as its universal. You can get the official from here: http://download.chainfire.eu/368/SuperSU/UPDATE-SuperSU-v1.75.zip
You will install that ONLY after you have installed the OTA's and your custom recovery and only if you want root.
good luck!
planet_x69 said:
Your best bet it is to sideload. Grab the OTA and the FULL 4.4
Pull the recovery.img from the full 4.4 rar (its in the zip), fastboot flash it, reboot into bootloader, go to recovery and sideload the OTA and that should restore it just fine
EDIT: http://forum.xda-developers.com/showpost.php?p=47656450&postcount=8
my detailed instructions there for sideloading
Click to expand...
Click to collapse
In this link, you said to do the following:
Pull the full stock 4.4 image from here : https://developers.google.com/androi...mages#mantaray
open it and pull out from the zip in the rar the recovery.img, move a copy to your adb folder along with a copy of your custom recovery ( for discussion sake I'll use twrp.recovery.img)
Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip
I got the full stock 4.4 image downloaded, extracted it, extracted the zip file inside (image-mantaray-krt16s.zip) and that provided me with "recovery.img" you mentioned above.
Now I have 2 problems, where is this "adb folder" you say to put the recovery.img in, and where is the custom recovery? I assume it's on the N10 after I connect it to my laptop. Is there a preferred custom recovery I should use? I saw mention of TWRP not working with Kit Kat elsewhere. Not sure if that is dated info or not.
Lastly, just to confirm this is true, none of this whole process will wipe my data correct?
planet_x69 said:
You don't need to root at all but the updated supersu 1.75 will be just fine as its universal. You can get the official from here: http://download.chainfire.eu/368/SuperSU/UPDATE-SuperSU-v1.75.zip
You will install that ONLY after you have installed the OTA's and your custom recovery and only if you want root.
good luck!
Click to expand...
Click to collapse
OK, downloaded that and will hold it for later. Hopefully after the questions I just asked are answered, I'll have enough info to proceed. Thanks for the help so far.
Stinger2300 said:
In this link, you said to do the following:
Pull the full stock 4.4 image from here : https://developers.google.com/androi...mages#mantaray
open it and pull out from the zip in the rar the recovery.img, move a copy to your adb folder along with a copy of your custom recovery ( for discussion sake I'll use twrp.recovery.img)
Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip
I got the full stock 4.4 image downloaded, extracted it, extracted the zip file inside (image-mantaray-krt16s.zip) and that provided me with "recovery.img" you mentioned above.
Now I have 2 problems, where is this "adb folder" you say to put the recovery.img in, and where is the custom recovery? I assume it's on the N10 after I connect it to my laptop. Is there a preferred custom recovery I should use? I saw mention of TWRP not working with Kit Kat elsewhere. Not sure if that is dated info or not.
Lastly, just to confirm this is true, none of this whole process will wipe my data correct?
Click to expand...
Click to collapse
Correct - if you SIDELOAD the OTA it will UPGRADE and retain all data and application settings etc...
If you run the 4.4 update from the factory image it will WIPE ALL. So do not do that ....just pull the recover.img from it and get rid of the rest.
If you downloaded this: http://downloadandroidrom.com/file/N...10RootNew.zip#
and extracted it to a new folder - do this first!!!
then copy the recovery.img you just extracted from the factory 4.4 rar to the same folder as the adb and fastboot commands
copy the OTA file to same folder and rename it ota.zip to make your life easier
>fastboot reboot-bootloader to validate your computer can see the device and that the next steps will go as planned
If you are now back bootloader then:
>fastboot flash recovery recover.img
wait till its done..will take about 15 seconds tops
>fastboot reboot-bootloader again and go to recovery using the volume buttons
select and enter recovery mode
wait for dead droid to appear
press both Volume UP and Power at same time and you should get the load menu
select "apply updated from adb" and press power after selecting
orange colored type will now appear at the bottom of the screen
on your PC
>adb sideload ota.zip
wait till you see its completed successfully
then reboot
(you can also apply the smaller ota (1.7MB) this same way)
If all went well you have now booted up successfully and see that your ass has been saved from eternal hell from your wife's wrath...
reboot and fastboot flash your favorite custom recovery reboot again to recovery and apply the su update for root access
I hope this helps
You can also read this: http://www.androidpolice.com/2013/1...-download-and-install-android-4-4-now-krt16o/
You said: "just pull the recover.img from it and get rid of the rest."
So is your instruction from the original link to: "Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip" replaced by the OTA file I renamed to ota.zip in order to retain all data? For reference, krt16s.zip is 390mb, ota.zip is 225mb.
Stinger2300 said:
You said: "just pull the recover.img from it and get rid of the rest."
So is your instruction from the original link to: "Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip" replaced by the OTA file I renamed to ota.zip in order to retain all data? For reference, krt16s.zip is 390mb, ota.zip is 225mb.
Click to expand...
Click to collapse
not sure i follow you but from the 4.4 factory image you will need the recovery.img file thats it. You will also need the OTA upgrade that takes you from 4.3 to 4.4. You need the OTA so that you wont lose your wifes data and will upgrade only and not image the device.
I have to leave and wont be back on till later this weekend.
Going well so far...had an issue but figured it out.
Got to sideloading ota.zip, then after it got to 100% it started verifying the update package. Got an error:
'/system/app/BasicDreams.apk" has unexpected contents
E:Error in /tmp/update.zip
(status 7)
Installation aborted.
Now what?
I found this in the Nexus 7 section but not sure if it applies here or if there is a better way, if it's guaranteed to not wipe data, etc.: http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26
Did you try this solution? I'm stuck on the "Error in /tmp/update.zip" as well. Having the same issues, and I hope to update without loosing data.
No, I haven't tried it as I can't risk losing data by randomly trying stuff I don't understand. I need someone who knows what they are doing to confirm that the steps in this link http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26 won't wipe data or do anything that will require wiping data to finish this process.
have well
Stinger2300 said:
No, I haven't tried it as I can't risk losing data by randomly trying stuff I don't understand. I need someone who knows what they are doing to confirm that the steps in this link http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26 won't wipe data or do anything that will require wiping data to finish this process.
Click to expand...
Click to collapse
I just tried it. And it worked. Didn't loose any data.
Flashing the img files, and then proceeding to sideload the OTA zip. Booting didn't take too long, Android then started upgrading ("Optimizing app..."), and booted successfully. It took a while to open de app drawer though... But everything was still there.
Regaining root access is something I'll try later. I'm just happy to have my N7 booting again.
Just a small disclaimer. I don't really know what I'm doing (I kinda like messing around with my device, it's only way to learn something), so I cannot guarantee it will work for you.
Glad it worked for you, it didn't work for me. I got another error after doing the following commands:
Then, run the following commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img
then I rebooted back to bootloader, then "apply updated from adb" and then from the command line: >adb sideload ota.zip
It again loaded 100% and then started verifying the package. Then I got this error:
Package expects build fingerprint of google/mantaray/manta:4.3/JWR66Y/776638:user/release-keys or google/mantaray/manta:4.4/KRT160/907817:user/release-keys; this device has google/mantaray/manta:4.4/KRT16S/920375:user/release-keys.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
What a F***ing nightmare...
Why do I apparently have the wrong version?
Hmm, might be the wrong OTA zip idd...
I downloaded mine from here: http://www.droid-life.com/2013/11/2...ial-update-for-nexus-7-2012-and-nexus-7-2013/
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Same here on my Nex5.
It seems, that some custom zips changed my stock (rooted) rom in this way that I am not able to install the 4.4.2 update.
I got similar issue on my Nex4 in the past, I could help me out by flashing full rom (rooted) deodexed, but where can I find the full rom of 4.4.2 for my Nex5 now?
Anybody can give me a clue?
Thank u very much.
Greetz from Germany.. Fred
Lexus One said:
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Click to expand...
Click to collapse
amplifier1980 said:
Same here on my Nex5.
It seems, that some custom zips changed my stock (rooted) rom in this way that I am not able to install the 4.4.2 update.
I got similar issue on my Nex4 in the past, I could help me out by flashing full rom (rooted) deodexed, but where can I find the full rom of 4.4.2 for my Nex5 now?
Anybody can give me a clue?
Thank u very much.
Greetz from Germany.. Fred
Click to expand...
Click to collapse
Hi Fred, and greetz from Ohio. I'm not aware of anything in the 4.4.2 flavor right now for the Nex10. I'm not sure about the Nex5. I think we're just going to have to wait. But I'd like to have the same thing. A lean & clean deodexed stock rooted 4.4.2 rom with a few performance tweaks. Like the old "Cleanrom" by scrosler. As for right now, did you try an ADB Sideload update to 4.4.2 using Wug's Toolkit? http://www.wugfresh.com/faqs/how-to-update-ota-not-working/
Lexus One said:
Hi Fred, and greetz from Ohio. I'm not aware of anything in the 4.4.2 flavor right now for the Nex10. I'm not sure about the Nex5. I think we're just going to have to wait. But I'd like to have the same thing. A lean & clean deodexed stock rooted 4.4.2 rom with a few performance tweaks. Like the old "Cleanrom" by scrosler. As for right now, did you try an ADB Sideload update to 4.4.2 using Wug's Toolkit?
Click to expand...
Click to collapse
Hi. Meanwhile i found a thread in nexus5 Android development area which contains both deodexed and odexed stock rooted full rom . so i just flashed odexed Version over my 4.4... Now i am on 4.4.2 finally... And still rooted..
Thank u anyway..
Greetz, fred
Lexus One said:
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Click to expand...
Click to collapse
Hi,
You can try performing a full unroot in the SuperSU app if it still doesn't work... I had to adb sideload mine to work, don't know how it works with toolkit, but you have to first set your tablet to receive it. As you are on TWRP you simply go to advanced and select adb sideload, then try using the tool, or following the instructions on it to do so .
You cannot install a OTA zip like a Custom ROM zip, they are a little bit different hehe.
Hope this helps,
~Lord
PS.: This will work for N5 too.
I somehow got the idea that rooted Nexus devices with a custom recovery could handle OTA's without trashing the recovery. I guess I expected that I would lose root. I think I'm just going to wait for someone to put together a "CleanROM" based on 4.4.2 or newer. I've been waiting for a rom like this since I bought my Nex10 anyway. I don't think I'll suffer too much running on 4.4 until then.
Thanks to those who contributed, I'll remember your suggestions. Especially if I end up waiting a long time for a 4.4.2 based Cleanrom.
Update: Thanks to Wug's toolkit. I'm now running 4.4.2..
I should ask for a sticky for this but these instruction will work EVERY TIME if you are running either custom recovery or Root.
You will need the latest adb/fastboot from google, you can either install the SDK or download any of the many smaller adb/fastboot and libs for your os
You will need STOCK 4.4/4.3/4.2 recovery depending on what version of android you are currently on. Download the factory image from here. Open the zip within the package and pull out recovery.img and rename it stockrecovery.img
Copy your custom recovery to the adb folder name it twrp.zip or short name for whatever you are using I am using twrp.
You will need the correct OTA you are seeking to apply - rename it to something short simple and obvious - for this example I will use otaupdate.zip
If you wish to root get the latest patch (I believe its up to 1.75 now) and copy it to the adb/fastboot folder.
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
If you are already Rooted:
If you are using SuperSU - go to the application options and completely unroot and reboot if needed
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
If not rooted start here:
I am assuming most of you are Windows users. Open your file explorer and open the ADB folder.
On the left hand folder where ADB is located press shift and right click the ADB folder and select "Open command window from here". This will open a command prompt window for you to run all your adb/fastboot commands from. This is the same folder where you copied your recoveries and updates to.
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
Copy your custom recovery and stock recovery to your adb folder
Copy and rename the OTA to the adb folder
Copy your root.zip patch to the /sdcard downloads folder (if you wish root)
>adb reboot bootloader
>fastboot flash recovery stockrecovery.img
>fastboot reboot-bootloader
Go into recovery and wait till dead droid appears
Press power and Volume Up at same time to go into the stock recovery menu
Using the volume buttons move and down the blue list of options and select: Apply update from ADB
You will now have orange text at the bottom of the screen - follow the instructions to side load by typing >adb sideload otaupdate.zip in your command prompt window
Wait and watch the progress, at this point you should see the ota processing steps of which there a few and will vary depending on the package. When its complete there will be a "install complete" or similar message
Reboot and let the update complete the system optimizations and go in validate your device is working and the version is what you wanted
>adb reboot bootloader
>fastboot flash twrp.zip
>fastboot reboot-recovery
Using your newly installed custom recovery you can now apply zips/root etc
Reboot as needed and update root if using older .zip to current binaries and enjoy your updated device.
And yes you only need to backup once prior to starting but many people skip that step -DON'T BE ONE OF THOSE PEOPLE.
Hopefully I've not missed a bit.
You can also use these same instructions if you're stuck in boot loop or applied a patch without first replacing stock or unrooting - just boot to bootloader using fastboot and replace recovery and apply the patches. This will usually work just fine and prevent much heart ache on your part.
Update5: 4.5.5 is out, and there is no reason NOT to update to 4.5.5. Please use the newer 4.5.5 upgrade instructions in the link below :
http://forum.xda-developers.com/fire-hd/general/upgrade-to-4-5-5-root-t3174449
Another alternative is Lollipop:
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
And these are the earlier (original) 4.5.x upgrade instructions which require modifying the Amazon update file:
Update4: For users with low computer proficiency (a.k.a "newbies"), DoLooper has written a post trying to make the instructions most accessible :
http://forum.xda-developers.com/showpost.php?p=61832754&postcount=10
If you still have questions after that, post here!
Update3: I've uploaded the 4.5.4 update file to Dropbox, now everything is super simple and you can skip steps 1)-4):
https://www.dropbox.com/s/17ngnhmvnkh1cpx/twrp_ready_update-kindle-20.4.5.4_user_454006120.zip?dl=0
md5sum : ab9468126ee7d7ff0b1c38a96313ef20
Use at your own risk (it works for me!)
If the procedure works for you, don't forget to click "Thanks"
Update2: Thanks to DoLooper, this has been established as the simplest and quickest way to get full GAPPS working. The instructions are simplified further to incorporate suggestions.
Update: Looks like the procedure worked for several people, but there is a single pitfall which appears to be common. I added some additional instructions below in red.
### Original post
I am making a separate topic out of this. Tested this yesterday, going from 4.5.2 to 4.5.4
What you need to have before you proceed : unlocked bootloader (according to reports, not really needed, skip), TWRP and rooted FireOS (4.5.3 or below). Also, download jmz tool to somewhere (can skip this too), and SuperSu flashable zip.
Important: If you have anything other than 4.5.3 right now, I recommend that you flash the 4.5.3 bootloader separately first before doing any updating business. I've attached the flashable zip with 4.5.3 bootloader as well (uboot*zip). The other bootloaders are very risky !!! 4.5.1 and 4.5.2 will not let you into TWRP by the "power" and "vol+" button push if you screw up !!!
0) If you used JMZ tool for GAPPS install or did a manual update prevention, clean up GAPPS update blockers by deleting the following dirs in /data/app (this will make your life easier later on!):
com.android.vending-1.apk
com.android.vending-2.apk
com.google.android.gms-1.apk
com.google.android.gms-2.apk
1) Download the latest 20-4.5.4 update to a PC ( https://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.4_user_454006120.bin ), rename *bin to *zip, unpack, and replace the attached "updater-script" below in 20-4.5.4/META-INF/com/google/android/updater-script
2) Delete the following directories/files :
a) here you remove stuff you will not flash
20-4.5.4/recovery
20-4.5.4/images
b) here you will remove files to make room in /system to flash bigger GAPPS
20-4.5.4/system/priv-app/com.amazon.weather.apk
20-4.5.4/system/priv-app/moffice_6.0.1_default_en00105_multidex_195423.apk
20-4.5.4/system/priv-app/com.amazon.geo.client.maps.apk
(can delete more if you need space in /system and know what is useless, and a few things could just be moved to /data/app with no issues)
3)Rename (just in case, this will make OTA blocked):
20-4.5.4/system/priv-app/DeviceSoftwareOTA.apk to *apk_
4) Zip everything into update.zip. Make sure the paths in zip are the same as in the original 4.5.4 update from Amazon (QC this carefully!). Put the zip on a USB stick with FAT (if you have an OTG cable). Alternatively, upload it to the device somewhere to the Download folder
Possible pitfall: When you create your update.zip, look into it!!! It should have {system,boot.img,etc} right at the top level, just like the original Amazon update. If you have {yourpath/system, yourpath/boot.img,etc}, you need to re-zip and make sure that "yourpath" is removed.
5) Boot into TWRP, and flash the 4.5.3 bootloader. Reboot. Skip if you already have 4.5.3
6) Boot into TWRP, and flash update.zip from 4) . Then immediately after flash supersu.zip ( https://download.chainfire.eu/396/supersu/ ). Reboot to FireOS. If you choose not to flash supersu.zip here, before you reboot TWRP, it will ask you to root the device, say yes (leaving hooks for later root)
7) Re-boot to TWRP, flash a GAPPS package, such as Pico (Uni) GAPPS for KitKat ( http://www.androidrootz.com/2015/03/download-android-44x-kitkat-pa-gapps.html ). Wipe dalvik/cache and reboot to FireOS (Note: The free room in /system is still kind of limited, either remove more stuff in Step 2), or go with the smaller GAPPS. If you download my update package, you'll probably have about ~140 Mb of room in /system for GAPPS). Wipe dalvik/cache, reboot.
8) In FireOS, install jmz tool, and do small tweaks. Important, installing GAPPS via this tool is obsolete !!! Don't do it!!!. Alternatively, skip this tool, and just do it manually or via the scripts, as per here :
http://forum.xda-developers.com/fire-hd/general/fireos-4-5-x-root-quickly-switch-to-t3145613
The lockscreen ads can be reversibly blocked via this adb command :
adb shell su -c "pm disable com.amazon.kindle.kso/com.amazon.kindle.kso.lockscreen.LockscreenUpdateS ervice"
(as per DoLooper's suggestion)
P.S. 4.5.4 allows the latest GAPPS to work fine, so they will update themselves over time, let them. No need anymore to keep Google Play Services at 7.0.99
kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.4_user_454006120.bin
link to 4.5.4.
nevermind figured it out, was being dumb and right clicking send to zip on the folder instead of adding the files to a zip
bibikalka said:
4) Zip everything into update.zip, and put it on a USB stick with FAT. Make sure the paths in zip are the same as in the original 4.5.4 update from Amazon.
Click to expand...
Click to collapse
You must use USB stick? . . .
. . . so must connect USB stick with OTG cable for step 6?
6) Boot into TWRP, and flash update.zip from 4) . Say yes when it offers to root the device.
Click to expand...
Click to collapse
I'm on rooted 4.5.3 with unlocked bootloader. Will install TWRP.
Haven't done anything like this before. Why not put update.zip in /system and flash from there? Thanks.
DoLooper said:
You must use USB stick? . . .
. . . so must connect USB stick with OTG cable for step 6?
I'm on rooted 4.5.3 with unlocked bootloader. Will install TWRP.
Haven't done anything like this before. Why not put update.zip in /system and flash from there? Thanks.
Click to expand...
Click to collapse
Sorry, I was not clear enough. Indeed, you can put this zip into the internal memory, but not /system (it'll get formatted). Instead, place it into the "Download" folder or something.
Just got done. Everything worked great. I did have to sideload SuperSu and Busybox manually though, but everything is working fine. Thank you.
With an easy way to recover (just re-install 4.5.4), I've been playing with various Xposed modules.
So far has not seen anything very attractive, and most of the system tweaks via Xposed modules don't seem to work.
Easy update 4.5.3 to 4.5.4 -- and working Gapps!!!
Very slick--thanks a lot! Finally, all Gapps updated and working perfectly!
FWIW, I wasn't prompted to root, which i guess I wouldn't be...didn't you say somewhere that root is preserved during 4.5.3 to 4.5.4 update? (Yeah, I'm still properly rooted.)
Gapps: Since JMZ's tool creates the dummy dirs you mentioned, which prevent play services and store from updating, I installed this Gapps minimal edition instead. Just uninstalled play store first--kept G+, hangouts and Gmail (although it never worked before)--and let play services update. Now everything is running great. :laugh:
DoLooper said:
Very slick--thanks a lot! Finally, all Gapps updated and working perfectly!
FWIW, I wasn't prompted to root, which i guess I wouldn't be...didn't you say somewhere that root is preserved during 4.5.3 to 4.5.4 update? (Yeah, I'm still properly rooted.)
Click to expand...
Click to collapse
Good to hear that you finally did it!
The update formats /system, so nothing survives there. But you could have had supersu in /data/app before, and that survived. You probably did root when TWRP asked about it right after the update? I think SuperSu needs something installed in /system to work properly, and that's what TWRP does.
DoLooper said:
Gapps: Since JMZ's tool creates the dummy dirs you mentioned, which prevent play services and store from updating, I installed this Gapps minimal edition instead. Just uninstalled play store first--kept G+, hangouts and Gmail (although it never worked before)--and let play services update. Now everything is running great. :laugh:
Click to expand...
Click to collapse
So you did not use JMZ's tool to install GAPPS at all? Did you just flash the minimal edition you've linked to in TWRP, and it worked? That'd be really neat if GAPPS could be flashed via recovery, just like in any other Android version. Btw, the latest Play Services provide correct positioning to Google Maps, so now it finds me on the map.
bibikalka said:
The update formats /system, so nothing survives there . . . You probably did root when TWRP asked about it right after the update?
Click to expand...
Click to collapse
If it were the least bit possible that I didn't get the root prompt, I would swear I didn't get it. I think, however, I left the tablet briefly while update.zip finished flashing. Any chance TWRP only gives you a minute or two to respond to root prompt, then defaults to yes?
Notes I took during update:
"Modified 4.5.4 update.zip installed successfully but i wasn't prompted to root. (see in twrp: HOME, WIPE CACHE, REBOOT SYSTEM) Went back to twrp HOME and flashed SUPERSU.ZIP - got success.
REBOOT."
Click to expand...
Click to collapse
That "see in twrp" is what i saw on screen after "success" with update.zip install. If TWRP always prompts to root and doesn't default to yes when there's no response, I must have done this step and will call a neurologist tomorrow. )
bibikalka said:
So you did not use JMZ's tool to install GAPPS at all? Did you just flash the minimal edition you've linked to in TWRP, and it worked?"
Click to expand...
Click to collapse
Exactly!
Couple last things:
1. Unlocked bootloader: You say unlocked bootloader required (and mine is), but JMZ shut down his thread. I assumed that was because TWRP could be installed without unlocking. Is that correct? If so, is unlocked bootloader really required to do this or is it only necessary to have TWRP?
2. Gapps: Hope you will have users install that minimal gapps. If they use JMZ's tool, to get updated play services and store they have to undo his fixes that make old Gapps work. With minimal package the store just updates itself to current version and prompts to update play services. No fuss.
3. Step 7 says "reboot to TWRP." This implies tablet reboots (or user is suppose to reboot) after "saying yes to root." Perhaps the reboot should be added? (But FWIW: Because I didn't see root prompt I flashed supersu right after flashing update, then rebooted.)
DoLooper said:
Very slick--thanks a lot! Finally, all Gapps updated and working perfectly!
...... I installed this Gapps minimal edition instead. ......
Click to expand...
Click to collapse
Thank you a million times for this. I'm on 4.5.4 rooted, and was having a horrible time getting gmail to work. I finally uninstalled framework, services, and playstore from that JMZ tool thing and gave this a shot. Gmail works great now. Only having one issue so far. On Google Play Movies, the movies and shows won't stream. They only play if downloaded first.
DoLooper said:
Notes I took during update:
"Modified 4.5.4 update.zip installed successfully but i wasn't prompted to root. (see in twrp: HOME, WIPE CACHE, REBOOT SYSTEM) Went back to twrp HOME and flashed SUPERSU.ZIP - got success.
REBOOT."
Click to expand...
Click to collapse
OK, no mystery then! And a good catch! It looks like update.zip can be safely followed by Supersu.zip, without any reboots. Supersu.zip will flash everything that's needed to have root, so TWRP does not ask for anything when you reboot the device.
DoLooper said:
Couple last things:
1. Unlocked bootloader: You say unlocked bootloader required (and mine is), but JMZ shut down his thread. I assumed that was because TWRP could be installed without unlocking. Is that correct? If so, is unlocked bootloader really required to do this or is it only necessary to have TWRP?
Click to expand...
Click to collapse
I agree, perhaps TWRP can be flashed and will work without any unlock, but I am just too lazy to test this. Do we have a confirmation for this one? I would update instructions accordingly if this is true.
DoLooper said:
2. Gapps: Hope you will have users install that minimal gapps. If they use JMZ's tool, to get updated play services and store they have to undo his fixes that make old Gapps work. With minimal package the store just updates itself to current version and prompts to update play services. No fuss.
Click to expand...
Click to collapse
Another good catch! I was not thinking about this when I wrote the original post, but having GAPPS flash properly is a pretty big deal! I may re-apply update.zip, and try the GAPPS flash, to see if it is indeed so simple.
Did you boot to FireOS after update.zip/supersu.zip, and then rebooted to TWRP, and flashed GAPPS? Or did you go straight from update.zip to supersu.zip to gapps flash, without the FireOS boot ?
DoLooper said:
3. Step 7 says "reboot to TWRP." This implies tablet reboots (or user is suppose to reboot) after "saying yes to root." Perhaps the reboot should be added? (But FWIW: Because I didn't see root prompt I flashed supersu right after flashing update, then rebooted.)
Click to expand...
Click to collapse
As above, supersu.zip flash right away is a nice simplification!
Overall, great help! And the big deal is that GAPPS are easy to flash, work fully, and require no messing around with anything else. This makes flashing 4.5.4 with GAPPS into the fastest way to get fully working GAPPS on this device !!!
Will I have to do anything special to undo the changes I made that blocked play store and services updates?
Thanks for working on this, having fully working play store will be great.
TWRP flashed fine for me without an unlocked bootloader, I already used it to make a backup.
lynnux said:
Will I have to do anything special to undo the changes I made that blocked play store and services updates?
Thanks for working on this, having fully working play store will be great.
TWRP flashed fine for me without an unlocked bootloader, I already used it to make a backup.
Click to expand...
Click to collapse
Good question ... At most you'll have to delete a couple of dummy directories in /data/app, one for the play store, and the 2nd one for the play services which prevented the updates. But perhaps the GAPPS zip will remove those itself ... Why don't you try, and post ?
lynnux said:
Will I have to do anything special to undo the changes I made that blocked play store and services updates?
Click to expand...
Click to collapse
It depends on what changes you made. Before I flashed update.zip, I did what @bibikalka suggests and found and deleted the following dirs in \data\app :
com.android.vending-1.apk
com.android.vending-2.apk
com.google.android.gms-1.apk
com.google.android.gms-2.apk
After update and before installing Gapps I searched /system for anything "google." Only found "widevine" and left it.
If you installed Gapps per the original root post, you gave this command:
pm grant com.google.android.gms android.permission.INTERACT_ACROSS_USERS
I don't know what this does. Shell command effects seem to be preserved with update, though, so would be worth finding out.
---------- Post added at 12:44 PM ---------- Previous post was at 12:23 PM ----------
bibikalka said:
OK, no mystery then! And a good catch! It looks like update.zip can be safely followed by Supersu.zip, without any reboots. Supersu.zip will flash everything that's needed to have root, so TWRP does not ask for anything when you reboot the device.
Did you boot to FireOS after update.zip/supersu.zip, and then rebooted to TWRP, and flashed GAPPS? Or did you go straight from update.zip to supersu.zip to gapps flash, without the FireOS boot ?
Click to expand...
Click to collapse
Exact steps I did:
Flash update.zip, press TWRP "Home," flash Supersu zip, reboot to system.
Go back to TWRP and flash Gapps zip, wipe cache (per instructions at minimal Gapps page), reboot to system.
FWIW, when rebooted after wipe, I got "updating" message again and it took awhile but all was fine.
4.5.4 Update bin: https://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.4_user_454006120.bin (Fire HD 6 and 7 use identical files)
superSU zip: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Gapps minimal: http://forum.xda-developers.com/showthread.php?t=2779598
I know this is basic, but how exactly do I do step 1? In root explorer or es file manager I can't figure out how to 'replace' the original update script with the one you've attached. These obviously don't work like regular files.
lynnux said:
I know this is basic, but how exactly do I do step 1? In root explorer or es file manager I can't figure out how to 'replace' the original update script with the one you've attached. These obviously don't work like regular files.
Click to expand...
Click to collapse
Download the update in a .bin file and extract (I use 7zip). Once extracted it makes a ton more sense.
lynnux said:
I know this is basic, but how exactly do I do step 1? In root explorer or es file manager I can't figure out how to 'replace' the original update script with the one you've attached. These obviously don't work like regular files.
Click to expand...
Click to collapse
ugcbrian said:
Download the update in a .bin file and extract (I use 7zip). Once extracted it makes a ton more sense.
Click to expand...
Click to collapse
Right. You do steps 1-4 on the computer. See my post above for link to the update bin file.
DoLooper said:
Right. You do steps 1-4 on the computer. See my post above for link to the update bin file.
Click to expand...
Click to collapse
Thanks. I was renaming as a .zip, but trying to make the replacement on the tablet. Since I'm using a linux laptop, I suppose I'll have to rename it as a tar or gz file to work with it there, since linux doesn't do .zips.
lynnux said:
Thanks. I was renaming as a .zip, but trying to make the replacement on the tablet. Since I'm using a linux laptop, I suppose I'll have to rename it as a tar or gz file to work with it there, since linux doesn't do .zips.
Click to expand...
Click to collapse
Okay, if you have to rename the bin file in order to extract the contents, do that. (Maybe double-click will work.) You will see the files and dirs that bibikalka's instructions refer to (excluding the "20-4.5.4," which is just for reference). After doing changes per instructions, make a compressed file named "update" containing what's left (see below). Since the extension will be tar or gz, rename it to "zip" and copy or move it to the Fire's download folder, then do step 6 (assuming you're on 4.5.3).
Your compressed file should contain:
[dir] META-INF
[dir] system
[dir] tools
boot.img
file_contexts
ota.prop
Today, I installed TWRP and rooted my device. I tried to install Xposed but I couldn't get passed the logo screen after rebooting. To try and fix this I did an advanced wipe and got rid of everything...
I know this was very stupid! TWRP is telling me there is no OS if I try to reboot. Is there a ROM I can install to fix this? I was on the stock MM rom and have L31 version.
LeChuck85 said:
Today, I installed TWRP and rooted my device. I tried to install Xposed but I couldn't get passed the logo screen after rebooting. To try and fix this I did an advanced wipe and got rid of everything...
I know this was very stupid! TWRP is telling me there is no OS if I try to reboot. Is there a ROM I can install to fix this? I was on the stock MM rom and have L31 version.
Click to expand...
Click to collapse
I made the same mistake at some point, but managed to get it back up and running.
Download the correct version of "update.zip" for your phone.
In my case it is a L31C432 so I looked for a file called something like VNS-L31C432B160 (stock MM).
Download this (EU version) (if you have a L31C432)
Once the download is completed, rename the downloaded file to "update.zip".
While in Recovery on your phone, and it's connected to your pc, copy the "update.zip" to either the phone's internal memory or the sdcard (doesn't matter).
Grab your phone and go into "Install" in your recovery and find your "update.zip" file.
Slide and let it install it.
Once done, reboot.
Viola!
Remember the "Thanks" button if it helped :good:
SnowmanDK said:
I made the same mistake at some point, but managed to get it back up and running.
Download the correct version of "update.zip" for your phone.
In my case it is a L31C432 so I looked for a file called something like VNS-L31C432B160 (stock MM).
Download this (EU version) (if you have a L31C432)
Once the download is completed, rename the downloaded file to "update.zip".
While in Recovery on your phone, and it's connected to your pc, copy the "update.zip" to either the phone's internal memory or the sdcard (doesn't matter).
Grab your phone and go into "Install" in your recovery and find your "update.zip" file.
Slide and let it install it.
Once done, reboot.
Viola!
Remember the "Thanks" button if it helped :good:
Click to expand...
Click to collapse
Excellent, thank you! For some reason I had no way of signing into my Google account with that version, however I found a previous version in another thread on here and that works perfectly. Thanks.
how to open the recovery mode ????
Hi, why when I try to install the zip it says invalid zip format? I'm trying to install it from a TWRP
spyrkle said:
Hi, why when I try to install the zip it says invalid zip format? I'm trying to install it from a TWRP
Click to expand...
Click to collapse
It's meant to be unzipped and then flashed with the dload method. Hope that helps :good:
So, I just rooted my Huawei P Smart, the 136 update shows up, it does all the install steps, reboots and then says it failed. Do O need to do something on the twrp boot?
Download the full firmware, we lose the option to just update via normal update and we can update with a full system update
airb05 said:
Download the full firmware, we lose the option to just update via normal update and we can update with a full system update
Click to expand...
Click to collapse
Just did that, 2 GB download, tries to install, reboots, goes to twrp, then I reboot to normal system and still says update failed.
Pretty sure you'll need stock recovery to update the "normal" way.
callmeWhiskers said:
Pretty sure you'll need stock recovery to update the "normal" way.
Click to expand...
Click to collapse
So I'll need to unroot and root again ? Anyway to update without doing that? Cause Im pretty sure ill screw up if I try it, barely made the root LOL
siivet said:
So I'll need to unroot and root again ? Anyway to update without doing that? Cause Im pretty sure ill screw up if I try it, barely made the root LOL
Click to expand...
Click to collapse
I'm not an expert - I always use HuRUpdater to update. It just requires you to download the (exact) right files, renaming them correctly and (like rooting with Magisk) just simply flashing a single .zip in recovery. In case you try it out, remember rule#1: Always make sure you have a (nandroid)backup.
Here are the relevant lines from my "Huawei-related-findings" text file:
#update
"Depends on how you rooted.
For a successful OTA install your device probably must meet the following criteria
• HUAWEI stock recovery installed
• unaltered /system, /product and /vendor partitions
So if you rooted with a "systemless" method (e.g. Magisk, recent SuperSU) and haven't done other installs/modifications that typically change /system you could try it. And you have to flash stock recovery (i.e. get rid of TWRP temporarily for the OTA install)."
Click to expand...
Click to collapse
#source XDA
@st_voss (u=1065667)
https://forum.xda-developers.com/showpost.php?p=73011427&postcount=2
#update
“It's recommended to use a proper custom recovery (with running oeminfo_nvm_server service) like for example*my version of TWRP.
How to use:
Warning: Make sure you know what you are doing and do not flash firmware from other devices.
1. Download firmware files (for official firmware use Huawei Firmware Finder).
2. Put files you want to flash in a seperate folder on sdcard.
Supported zip files to flash are (name must match):
◦ update.zip (use FullOTA file)
◦ update_all_hw.zip
◦ update_data_public.zip
3. Optional: Put recovery.img in same folder if you want to keep custom recovery.
4. Put HuRUpdater zip in same folder.
5. Select*only HuRUpdater*to flash in custom recovery.
6. Follow instructions on screen. Flashing can take multiple minutes.
Problems:
• If firmware includes factory reset
◦ Factory reset is not supported by custom recovery. Therefore HuRUpdater will flash stock recovery before launching factory reset. After flashing firmware and doing factory reset, you need to flash recovery manually.”
Click to expand...
Click to collapse
#source XDA
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
#notes HuRUpdater_0.4.zip working
Thanks mate, the Huawei Firmware Finder seems like its not working for the moment, but as soon as it is ill follow your tip
siivet said:
Thanks mate, the Huawei Firmware Finder seems like its not working for the moment, but as soon as it is ill follow your tip
Click to expand...
Click to collapse
Yes, I'm im the same boat - I guess you also get the "can't have connection" error using the FF app. During the last weeks they had troubles with their service regarding hackers and moving to a new server (according to their telegram group), which have been fixed ("all services working normally now"), and many can use it again - for whatever reason some still can't connect. I tried reinstalling the app, using proxies from different countries - still doesn't let me connect.
But their web interface is working: https://pro-teammt.ru/firmware-database/ though you can't check iirc, if the firmware has been approved for your IMEI.
According to this post:
sun75 said:
It's online now! I suggest you to download the "2018.08.30" .158 "2379" release, if you have a FIG-LX1, L31 board phone.
Click to expand...
Click to collapse
You apparently can download this release (2379) if you own this device/board- though the last time I updated mine (.148) I used the 2079 (154226) one despite owning the exact same device. I'm slightly confused about this
I didn't try the above mentioned update myself.
siivet said:
Thanks mate, the Huawei Firmware Finder seems like its not working for the moment, but as soon as it is ill follow your tip
Click to expand...
Click to collapse
Try installing an older version of the Firmware Finder app - I switched from (current) v9.0 to v8.9 and it works now
https://apkpure.com/firmware-finder...efinder/download/86-APK?from=versions/version
..