Hello guys , so I am using a rooted nexus 6p , with the stock rom, custom kernel.
I received an OTA update ( noguat ) , but when I tried to install it through my phone it just went straight to the TWRP recovery.
I read that I can't install OTA updates with a custom recovery , I was wondering if I can manually download the OTA update from the official google site and install it that way?
edit: help, i think I just ****ed my phone, I tried to flash the OTA using this guide: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
but when I did what I did the phone showed me a " your phone is corrupted message " and now is stuck on the google logo, recovery is dead it just says no command and I see a red dead android.
What should I do?
Flash the factory image with flashall from google.
Sent from my Nexus 5X using Tapatalk
You didn't kill anything. Go to @Heisenberg thread in q&a and follow those instructions to flash factory images back to stock. Takes about five minutes and you'll be Booting back up.
Related
i have a rooted nexus 10 , not unlocked no custom recovery , rooted it via tool kit , 4.22 update was available via ota so tablet notified me and when i intalled the update it stoped in the mid and saying error , and now when i restart my tablet after google logo android appears and under it "no command" , how should i fix it.
I got the similar issue.. i can't find out another solutions.. i have to reflash the factory image to 4.2 and OTA 4.2.1 and 4.2.2
then use toolkit again to root it.
since Factory image 4.2.2 has released. just flash to it , will be much easier.
Try to search it.. i saw the other one have the same issue..
A friend of me got the same problem and all he did was go into recovery mode and wipe cache. He got this problem because he updated via ota and he had the aosp browser without the original files on /system/app.
What you have to do is power off your nexus 10 and then press power-vol+ and vol- buttons together. When you get to the dead droid recovery menu, press all 3 buttons. You will get into the recovery options.
thank you guys n another thing... to recieve and install the ota updates succesfully do i have to unroot my tablet?
harrisfayyaz said:
thank you guys n another thing... to recieve and install the ota updates succesfully do i have to unroot my tablet?
Click to expand...
Click to collapse
No; keep in mind that if you mod anything system related (apps, framework, build.prop), you'll need to restore it the way it was before actually running the install process.
Sent from my Nexus
Hi all,
I searched this forum and didn't see any solution so posting for help!
my Nexus 4 - which came with stock 4.3 (build - JWR66Y).
I rooted it loaded TWRP...
it worked fine for all these days.
I just upgraded to Kitkat 4.4 and that screwed up everything....I upgraded.. and off course rebooted and the phone is stuck on Google logo..
nothing happens..
Anyone who tried different options to get this to work...please help....
appreciate your response.
Same here. Had to flash stock 4.4 image to get my device alive again.
Enviado de meu Nexus 4 usando Tapatalk
Can you please let me know how you flashed stock 4.4 image?
I mean the steps you followed please...
Also did you just install the zip file once you extracted from google's .tgz file or did you have to even wipe out TWRP?
thanks
Fusquinha77 said:
Same here. Had to flash stock 4.4 image to get my device alive again.
Enviado de meu Nexus 4 usando Tapatalk
Click to expand...
Click to collapse
greenzellybean said:
Can you please let me know how you flashed stock 4.4 image?
I mean the steps you followed please...
Also did you just install the zip file once you extracted from google's .tgz file or did you have to even wipe out TWRP?
thanks
Click to expand...
Click to collapse
Factory images cannot be flashed using recovery. You have to use ADB for that. Here is a guide of the whole process.
This happened to me too, and I thought going back to 4.3 was the answer so I flashed stock 4.3 and now its the same. Im downloading 4.4 stock now. Im worry that it wont work. Any ideas?
jpborjav said:
This happened to me too, and I thought going back to 4.3 was the answer so I flashed stock 4.3 and now its the same. Im downloading 4.4 stock now. Im worry that it wont work. Any ideas?
Click to expand...
Click to collapse
Thanks arffrhn...I was able to get back to 4.3 stock and was able to gradually upgrade from there to 4.4.1
Here are the steps I followed.
when I was stuck at Google logo...I was still able to get into fastboot and TWRP etc..
I downloaded 4.3 and 4.4 builds from Google Developer site ( Link)
I unzipped them including zips with the main tar file...
followed instructions in the guide linked by arffrhn below (section D from the guide)
when I got to flashing boot loader it FAILED.....
error: not the same image...etc...
note when you go into fastboot using vol+power button check out your Product name, bootloader version and baseband version.....
mine was MAKOZ20i version # 2.0.1700.84, so I had to use the mirror site linked on the guide (section D again) to download an older stock build (which referenced my build number)....extracted files from this build
followed the steps again as mentioned on the guide.....
I was able to get back to stock 4.3
from there Google updates you to next version of 4.3 ..after reboot it will start upgrading you to 4.4.1
you may have some hassle with SuperSU....you are better off with downloading the zip file from the guide and installing it through TWRP.
note: I was not able t get TWRP working after upgrading to 4.4.1.....it gives me "No command" error ...I tried to fastboot TWRP multipl times but that didnt help.....
greenzellybean said:
Thanks arffrhn...I was able to get back to 4.3 stock and was able to gradually upgrade from there to 4.4.1
Here are the steps I followed.
when I was stuck at Google logo...I was still able to get into fastboot and TWRP etc..
I downloaded 4.3 and 4.4 builds from Google Developer site ( Link)
I unzipped them including zips with the main tar file...
followed instructions in the guide linked by arffrhn below (section D from the guide)
when I got to flashing boot loader it FAILED.....
error: not the same image...etc...
note when you go into fastboot using vol+power button check out your Product name, bootloader version and baseband version.....
mine was MAKOZ20i version # 2.0.1700.84, so I had to use the mirror site linked on the guide (section D again) to download an older stock build (which referenced my build number)....extracted files from this build
followed the steps again as mentioned on the guide.....
I was able to get back to stock 4.3
from there Google updates you to next version of 4.3 ..after reboot it will start upgrading you to 4.4.1
you may have some hassle with SuperSU....you are better off with downloading the zip file from the guide and installing it through TWRP.
note: I was not able t get TWRP working after upgrading to 4.4.1.....it gives me "No command" error ...I tried to fastboot TWRP multipl times but that didnt help.....
Click to expand...
Click to collapse
Well mine is MAKOZ30d and M9615A-CEFWMAZM-2.0.1700.97 that correspond to the KRT16S build. I already did the whole process in the guid and even did went to recovery after flashing and wipe the phone to factory like in the note says. Still no luck.
I tried flashing JWR66V to get MAKOZ20i version # 2.0.1700.84 but in fastboot still says MAKOZ30d and M9615A-CEFWMAZM-2.0.1700.97.
Is anyone reading this thread or should I make a new one! Im stuck! I got the phone to JWR66Y and the bootloader is MAKOZ20i with radio # 2.0.1700.84.
I cleared the cache, reset to factory after flashing and nothing! Still on the X Logo! Yesterday i left it like 30mins on the logo and nothing.
jpborjav said:
Is anyone reading this thread or should I make a new one! Im stuck! I got the phone to JWR66Y and the bootloader is MAKOZ20i with radio # 2.0.1700.84.
I cleared the cache, reset to factory after flashing and nothing! Still on the X Logo! Yesterday i left it like 30mins on the logo and nothing.
Click to expand...
Click to collapse
How did you update to jwr66y? Have you tried flashing factory images after you got stuck?
Sent from my Nexus 4 using xda premium
Factory images always help...especially when you don't know what you do.
https://developers.google.com/android/nexus/images#occam
Sent from my Nexus 4 using xda app-developers app
Hi,
I have a rooted Nexus 4 with android 5.0 lollipop build LRX21T.
I have TWRP recovery installed version : v2.8.0.1
The device id rooted via placing the zip file in the device and flashng it via TWRP recovery.
But i am not able to update to android 5.0.1 via google OTA update.
Everytime i try to install the 5.0.1 OTA it goes to TWRP recovery.
I found that the downloaded OTA update file is placed in /cache folder , so i try to update it manually but failed as it shows some update partition error.
"E: error executing updater binary in zip '/cache/e93b********************.signed-occam-LRX22c-from-LRX21T.e93b****.zip"
update partition details.....
I think i am getting this error because the device is rooted.
Can someone guide me how to update my device..and if this because of the rooted device how to unroot without going back to stock.
Thanks in advance....
You can't flash the ota in twrp. You have to be 100% stock recovery, system, kernel, and radio. Flash the stock recovery with fastboot then try the ota.
Sent from my Nexus 9 using XDA Free mobile app
I flashed the stock recovery the OTA update continued in the stock recovery , then it showed a error....and i had to restart the phone ...now the ota update has disappeared with the phone still in android 5.0 ...Can you tell me how to get the OTA update back...?
1)Does the error came because the phone is still rooted ?
2) If so how do i remove the root with returning stock .?
3) also if i root and return to stock will it wipe my phone apps and their data...
Now i got the OTA update downloaded manually on my laptop and and booted into stock recovery to try to sideload the zip it gave me the error
"package expects build fingerprint of google /occam/mako:5.0/LRX21T or google /occam/mako:5.0/LRX22C user release keys; this device has google/occam/mako:4.4/KRT160 user release keys .....
This is weird as i am running android android lollipop 5.0 LRX21T and not android kitkat....
Did you flash mods while rooted?
Sent from my Nexus 4
arkangel72 said:
Did you flash mods while rooted?
Sent from my Nexus 4
Click to expand...
Click to collapse
Tried both...with and without Root....same error....
Try flashing factory image.
The OTA will flash only on the stock recovery it won't work in any modified/custom recovery. So flash stock recovery first then you are good to go.
Edit: You may also try flashing the factory image, u may lose your data while doing that
Head to https://developers.google.com/android/nexus/images and download the latest image, flashing procedure is explained there too.Its not compulsory to lock bootloader afterwards BTW, its personal preference.
sachin.parmar100 said:
The OTA will flash only on the stock recovery it won't work in any modified/custom recovery. So flash stock recovery first then you are good to go.
Edit: You may also try flashing the factory image, u may lose your data while doing that
Head to https://developers.google.com/android/nexus/images and download the latest image, flashing procedure is explained there too.Its not compulsory to lock bootloader afterwards BTW, its personal preference.
Click to expand...
Click to collapse
Actually i dont want to flash stock as i will lose all the data in the process....
Any other way....?
If there is no other way could you please suggest any tool kit which will backup all data including sms ,contact, call logs and all app data and /data/media folder. in one go ...?
use advanced backup from twrp backup menu and select data only to create a nandroid backup of data only
you can also use titanium backup to backup to choose what to backup and restore it afterwards but it will need root again.
sync your contacts with google server
Flah rom in fastboot
Download factory image, flash system, bootloader and recovery manually. You won't lose your data.
You need stock recovery to proceed flashing the OTA, custom recovery won't flash the OTA, i don't think being rooted is the issue Just flash the stock recovery to solve the problem.
sachin.parmar100 said:
You need stock recovery to proceed flashing the OTA, custom recovery won't flash the OTA, i don't think being rooted is the issue Just flash the stock recovery to solve the problem.
Click to expand...
Click to collapse
Rooted IS an issue. You can't be rooted and apply the OTA file, it will fail every time. As a previous poster has said, the phone MUST have stock bootloader, recovery and be not rooted for the stock OTA's to apply. If they see any modification during the process, they abort. It's been discussed many times.
Yaz75 said:
Rooted IS an issue. You can't be rooted and apply the OTA file, it will fail every time. As a previous poster has said, the phone MUST have stock bootloader, recovery and be not rooted for the stock OTA's to apply. If they see any modification during the process, they abort. It's been discussed many times.
Click to expand...
Click to collapse
thanks for pointing out i was so wrong
After attempt at installing software update to Nexus 10 tablet will not boot. Have wiped Cache and even then did a factory reset. Nothing. Google appears and then twirling colorful dots and nothing. For hours just twirling dots., Samsung and Google and Best Buy geeks says nothing they can do. No longer under warranty but very upset since tablet was working great until update. I am not very tech savvy but can anyone help or do I just have a new paperweight? Thanks for any advice.
I have not made any modifications to the tablet.
Just flash the newest factory image. Get it and the instructions to flash it from here:
https://developers.google.com/android/nexus/images
yes flash the newest image
After getting a notification of the latest update I went and rebooted for the update to install but it went to the twrp recovery and nothing happens, is there a way to install the update?
VivaErBetis said:
Just flash the newest factory image. Get it and the instructions to flash it from here:
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Gibbothegreat said:
After getting a notification of the latest update I went and rebooted for the update to install but it went to the twrp recovery and nothing happens, is there a way to install the update?
Click to expand...
Click to collapse
Still having proble? what is your recovery ? stock? did you update the bootloader? depending on your answer I should be able to help you out, thx
Khaon said:
Still having proble? what is your recovery ? stock? did you update the bootloader? depending on your answer I should be able to help you out, thx
Click to expand...
Click to collapse
Hi Khaon, I have stock lollipop version 5.1.1 . (LMY47V) and latest twrp version. When upgrading it restarts and goes to recoverys main screen.
BTW how can I check which version my bootloader is?
same problem
VivaErBetis said:
Just flash the newest factory image. Get it and the instructions to flash it from here:
as a newbie .I'm not allowed to reference your link !!
I rooted my nexus 10 using xda instructions., installed CWM. All good. I tried backup and recovery and screwed something up in recovery. Got stuck in recovery mode reboot loop. Many gyrations, no fix, so I tried factory reset. Still no fix.
I decided to install a new version of the OS using the Mantaray tar you reference above. UBS connecting and fastboot. All messages look good. Now I have the problem reported in this thread. Stuck with flying balls and no boot. Very interested in any suggestions you may have.
Click to expand...
Click to collapse
Gibbothegreat said:
Hi Khaon, I have stock lollipop version 5.1.1 . (LMY47V) and latest twrp version. When upgrading it restarts and goes to recoverys main screen.
BTW how can I check which version my bootloader is?
Click to expand...
Click to collapse
So you keep just boot looping into twrp, right ?
Did you try installing a custom ROM through adb or just connecting your device?
If it keeps boot looping you gotta to wipe the full storage.
Khaon said:
So you keep just boot looping into twrp, right ?
Did you try installing a custom ROM through adb or just connecting your device?
If it keeps boot looping you gotta to wipe the full storage.
Click to expand...
Click to collapse
No, on a normal reboot or a shutdown/restart it's fine no problems there but when I try to install the update via system update it reboots into twrp. I attach a pic of my system.
Gibbothegreat said:
No, on a normal reboot or a shutdown/restart it's fine no problems there but when I try to install the update via system update it reboots into twrp. I attach a pic of my system.
Click to expand...
Click to collapse
Oh I see, well, you should just flash a custom ROM or if you want to stay with official factory images, you should just follow instruction there:
https://developers.google.com/android/nexus/images
What you do need is just have fastboot executable once you are into the bootloader.
You can easily access the bootloader from twrp : shutdown > reboot into booatloader
Cool thx for your continued help :good:
The problem is due to your attempting an OTA update with a custom recovery (TWRP). You can only do OTA with stock recovery. Once you are in this situation, your easiest way out of it is to simply apply the latest factory image using "fastboot", but this will also wipe your user data so backup any photos, music, etc. before you start. You will also have to reload programs from Playstore once the new image is installed.
Guys, I have a ZenFone 5. I have recently updated it to Lolllipop version 3.24.40.87. This Morning, I rooted it and changed its stock recovery to TWRP . After that when I tried to install Xposed using an installer provided by someone on this same site, but in second step of installing the framework, ZenFone did not boot. Then the phone was stuck on ASUS logo . After that I took backup through TWRP and did these various things to make it work.
1. Cleared the cache (didn't work)
2. Cleared the whole partition by selecting system,cache,internal sd,data in TWRP (also didn't work)
3. Downloaded the very same firmware previously installed and tried to install it from an OTG but failed with error 255
4. Restored the backup as after doing the above steps, it was not even booting from the very first large logo of ASUS
5. Tried to return to same stock recovery by uninstalling TWRP by the same installer provided to insall it to flash official firmware through stock recovery. Completed successfully but did not work.
6. Then I extracted the stock recovery from the firmware's zip and flashed it through fastboot. Stock recovery was then successfully installed.
7. Then I tried to install the official firmware by sideloading through ADB in stock recovery. Got same error two times as the phone was restarted automatically on 54% and the error was "*Failed to read command:".
8. Wiped the data using stock recovery.
Now It is booting up directly to the recovery where the red traingle is appearing . Does Anyone have a working method. If do, please share . It would be a great help for me.
bludyvenom said:
Guys, I have a ZenFone 5. I have recently updated it to Lolllipop version 3.24.40.87. This Morning, I rooted it and changed its stock recovery to TWRP . After that when I tried to install Xposed using an installer provided by someone on this same site, but in second step of installing the framework, ZenFone did not boot. Then the phone was stuck on ASUS logo . After that I took backup through TWRP and did these various things to make it work.
1. Cleared the cache (didn't work)
2. Cleared the whole partition by selecting system,cache,internal sd,data in TWRP (also didn't work)
3. Downloaded the very same firmware previously installed and tried to install it from an OTG but failed with error 255
4. Restored the backup as after doing the above steps, it was not even booting from the very first large logo of ASUS
5. Tried to return to same stock recovery by uninstalling TWRP by the same installer provided to insall it to flash official firmware through stock recovery. Completed successfully but did not work.
6. Then I extracted the stock recovery from the firmware's zip and flashed it through fastboot. Stock recovery was then successfully installed.
7. Then I tried to install the official firmware by sideloading through ADB in stock recovery. Got same error two times as the phone was restarted automatically on 54% and the error was "*Failed to read command:".
8. Wiped the data using stock recovery.
Now It is booting up directly to the recovery where the red traingle is appearing . Does Anyone have a working method. If do, please share . It would be a great help for me.
Click to expand...
Click to collapse
1. what firmware.zip version you flash on step 6?
2. what firmware version you try to sideload on step 7?
Sent from my ASUS_T00F using XDA-Developers mobile app
paktepu said:
1. what firmware.zip version you flash on step 6?
2. what firmware version you try to sideload on step 7?
Click to expand...
Click to collapse
It was the same lollipop firmware by which I had updated my phone. It was UL-ASUS_T00F-WW-3.24.40.87-user.zip and in both the steps 6 & 7 this was used. BTW thanks for the reply :good:
bludyvenom said:
It was the same lollipop firmware by which I had updated my phone. It was UL-ASUS_T00F-WW-3.24.40.87-user.zip and in both the steps 6 & 7 this was used. BTW thanks for the reply :good:
Click to expand...
Click to collapse
You cant sideload 87.zip when youre on 87.
you need to downgrade to kk first and upgrade back to 87.
Flash boot, recovery and fastboot from 54.zip and from recovery sideload 54.zip and 540.zip
Now you can upgrade back to 87 .
Or you can directly upgrade via FOTA.
Sent from my ASUS_T00F using XDA-Developers mobile app
paktepu said:
You cant sideload 87.zip when youre on 87.
you need to downgrade to kk first and upgrade back to 87.
Flash boot, recovery and fastboot from 54.zip and from recovery sideload 54.zip and 540.zip
Now you can upgrade back to 87 .
Or you can directly upgrade via FOTA.
Click to expand...
Click to collapse
Thanks for the Reply. I did not know about it so thank you for your help. Trying this method if works, I will tell u for sure :good: .
Problem Solved
Thanks for your valuable reply as It is finally working now after trying these various methods. Now, flashing Lollipop again. Thank you :good: :good: :good:
bludyvenom said:
Thanks for your valuable reply as It is finally working now after trying these various methods. Now, flashing Lollipop again. Thank you :good: :good: :good:
Click to expand...
Click to collapse
you welcome
Sent from my ASUS_T00F using XDA-Developers mobile app