Related
Fixed.
RusherDude said:
If I am on 4.4 stock rooted, with a custom recovery, and stuff modified on /system.. what I do when the update to 4.1.1 comes?
If I don't do nothing, the update will download automatically (which I don't want at all...), then try to patch and fail (I guess it won't even start since it detects that it's not stock system and recovery to flash the update) and it may even loop downloading and failing by what I readed being a bug on some 4.3 roms on the Nexus 4?
So how I should act in the following situations? First make a nandroid then..
a) I wanna flash it asap: I get the ota zip asap its posted and flash it on CWM and hope it goes ok. I may **** up stuff and have to revert to the nandroid, or 1it can go ok and just lose root and the system changes, right?
b) I wanna stay on 4.4 until all the stuff is ported to 4.1.1: It will at some point download the ota (****) by itself and spam me continuously to install it, right? If I wanna stay on 4.4 until all the stuff I use its compatible with 4.1.1, what I got to do to evade the auto-downloading of the ota and the spam about the update?
I don't know.. any way to stop the auto-update from working or so? That would be great!
Thanks in advance.
Click to expand...
Click to collapse
Here is what I just did, and it worked perfectly.
1. Take note of all the mods you installed so you can install them afterwards.
2. Put phone in bootloader mode / fastboot
3. Grab the 4.4 stock image from Google. Extract system.img file from it and flash that through fastboot (without the -w command) (fastboot flash system system.img). Don't worry you won't lose anything if you omit -w. Apps and data are preserved, it just set the \system area back to stock
4. Copy the OTA udpate zip to your phone, flash with TWRP. Since everything is 'back to stock' it should flash fine.
I had to re-root with TWRP after flashing before I rebooted. Everything was good to go. Then reflash your mods.
sonicdeth said:
Here is what I just did, and it worked perfectly.
1. Take note of all the mods you installed so you can install them afterwards.
2. Put phone in bootloader mode / fastboot
3. Grab the 4.4 stock image from Google. Extract system.img file from it and flash that through fastboot (without the -w command) (fastboot flash system system.img). Don't worry you won't lose anything if you omit -w. Apps and data are preserved, it just set the \system area back to stock
4. Copy the OTA udpate zip to your phone, flash with TWRP. Since everything is 'back to stock' it should flash fine.
I had to re-root with TWRP after flashing before I rebooted. Everything was good to go. Then reflash your mods.
Click to expand...
Click to collapse
Ok, that covers the a) situation where I want to flash it asap, thanks! (also note everyone, you got to disable xposed and all mods before flashing the ota)
PS: You can just flash the stock kernel and undo all the system changes, no need to flash the entire 4.4 stock zip.
What about the b) situation?
RusherDude said:
Ok, that covers the a) situation where I want to flash it asap, thanks! (also note everyone, you got to disable xposed and all mods before flashing the ota)
PS: You can just flash the stock kernel and undo all the system changes, no need to flash the entire 4.4 stock zip.
What about the b) situation?
Click to expand...
Click to collapse
Don't know why you'd want to go all the way back to 4.1.1. That's from July '12.
mattjorgs said:
Don't know why you'd want to go all the way back to 4.1.1. That's from July '12.
Click to expand...
Click to collapse
Wut? in the b) situation I just wanna STAY on 4.1 until all the stuff is ported to 4.1.1 (if something needs porting).
RusherDude said:
Wut? in the b) situation I just wanna STAY on 4.1 until all the stuff is ported to 4.1.1 (if something needs porting).
Click to expand...
Click to collapse
You mean 4.4? And 4.4.1? Lol
Sent from my Nexus 5 using Tapatalk
How to update to 4.4.1
I am rooted/bootloader unlocked with TWRP v2.6.3.1. When I try to flash in recovery manually with ota zip, I get a Failed error with error "E: error executing updater binary in zip"
What are step to update for a device like mine??
Cheeze[iT] said:
You mean 4.4? And 4.4.1? Lol
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Omg yea, 4.4 lol, fail haha
I tried to update to KitKat officially over the air but I get an error message , I had a custom recovery but flashed back to a version of the stock recovery,thing is I think its the recovery that's the problem,I don't know which version of the moto g its from (tesco,us,Brazil) I'm not sure so I'm on the unlocked UK ROM retail.gb.en.GB bought from phones 4u . am I right in thinking that the recovery is the problem and would anyone have a copy of the recovery I'm looking for??
kieranc88 said:
I tried to update to KitKat officially over the air but I get an error message , I had a custom recovery but flashed back to a version of the stock recovery,thing is I think its the recovery that's the problem,I don't know which version of the moto g its from (tesco,us,Brazil) I'm not sure so I'm on the unlocked UK ROM retail.gb.en.GB bought from phones 4u . am I right in thinking that the recovery is the problem and would anyone have a copy of the recovery I'm looking for??
Click to expand...
Click to collapse
Are you also rooted, if so that's more likely the error.
There should be links in the forums to UK retail images.
scott_doyland said:
Are you also rooted, if so that's more likely the error.
There should be links in the forums to UK retail images.
Click to expand...
Click to collapse
I'm rooted yes but I did the temporary unroot option that's found in super su but I suppose the files are in the system still,the progress bar moves about a third of the way through the update then fails.
kieranc88 said:
I'm rooted yes but I did the temporary unroot option that's found in super su but I suppose the files are in the system still,the progress bar moves about a third of the way through the update then fails.
Click to expand...
Click to collapse
I have read in other threads that the unroot option possibly still leaves some system files different from what they originally were.
If possible can you flash cwm or twrp and backup /system. Then unpack/untar the backup on your PC and look at file
/system/etc/install- recovery.sh
See if it mentions superSU in the comments. This file is altered by superSU and I've heard it may be this file that does not get set back to its default when you unroot.
I can send you original file but you'd have to find a way to copy it to /system - hard if unrooted!! Maybe copy it and then unroot as I *think* this may work. The file seems to just start root daemon on boot so should be able to overwrite while rooted and then unroot.
I'm rooted and my update failed third of way through as well. However I wanted it to so updated while rooted on purpose as I want to stay on 4.3 (updating and letting it fail stops the 'update reminder').
scott_doyland said:
I have read in other threads that the unroot option possibly still leaves some system files different from what they originally were.
If possible can you flash cwm or twrp and backup /system. Then unpack/untar the backup on your PC and look at file
/system/etc/install- recovery.sh
See if it mentions superSU in the comments. This file is altered by superSU and I've heard it may be this file that does not get set back to its default when you unroot.
I can send you original file but you'd have to find a way to copy it to /system - hard if unrooted!! Maybe copy it and then unroot as I *think* this may work. The file seems to just start root daemon on boot so should be able to overwrite while rooted and then unroot.
I'm rooted and my update failed third of way through as well. However I wanted it to so updated while rooted on purpose as I want to stay on 4.3 (updating and letting it fail stops the 'update reminder').
Click to expand...
Click to collapse
Yeah,send it,I'll try copying it,unrooting and then trying the update
kieranc88 said:
Yeah,send it,I'll try copying it,unrooting and then trying the update
Click to expand...
Click to collapse
And will it matter what version of the stick recovery I'm using( if there are different versions)
kieranc88 said:
I tried to update to KitKat officially over the air but I get an error message , I had a custom recovery but flashed back to a version of the stock recovery,thing is I think its the recovery that's the problem,I don't know which version of the moto g its from (tesco,us,Brazil) I'm not sure so I'm on the unlocked UK ROM retail.gb.en.GB bought from phones 4u . am I right in thinking that the recovery is the problem and would anyone have a copy of the recovery I'm looking for??
Click to expand...
Click to collapse
check out this thread: http://forum.xda-developers.com/showthread.php?t=2611544
my posts have links to guides/files that helped me fix the OTA update error, and the thread as a whole should help you out
xTx
tee_pot said:
check out this thread: http://forum.xda-developers.com/showthread.php?t=2611544
my posts have links to guides/files that helped me fix the OTA update error, and the thread as a whole should help you out
xTx
Click to expand...
Click to collapse
OK,well at the moment I'm trying out cm11 unofficial builds,I'll see how they go, I'll try the full unroot option when I restore my cwm backup and reflash stock recovery and see if that works ,as I only tried the temporary unroot option in supersu(which is probably leaving some root files behind so it can reinstall su ) if that don't work I'll flash back to stock and try again.
kieranc88 said:
Yeah,send it,I'll try copying it,unrooting and then trying the update
Click to expand...
Click to collapse
I will send file tomorrow when I'm at my PC.
kieranc88 said:
Yeah,send it,I'll try copying it,unrooting and then trying the update
Click to expand...
Click to collapse
I have attached the file /system/etc/install-recovery.sh file to this post (had to gzip it as couldnt upload when it was just called .sh)
Im not sure what the original persmissions of the file should be on your phone, but if you make it read/write/executable by everyone then should be OK I guess.
As I mentioned it'd be good if you unrooted and did a backup and extracted the file to see the contents (before copying over the file). That would first tell you for sure if the file does revert back to original or if it stays as a 'superSU' file when you unroot.
If its reverted back to original then my theory is wrong anyway so no need to copy over the file.
Re the stock recovery type/version being different from what is expected - I dont know if that makes a difference to the OTA working or not. Its an interesting question though so I may do some googling and find out.
I also have a UK retail stock recovery.img (taken with CWM) (my phone is 16GB from phones4u). So if you want that you can have it. Should rule out the recovery type as a problem.
FYI the install-recovery.sh original file actually flashes a new stock recovery when an OTA is performed. At least if you look in the comments of the file I attached above thats what it says.
I tried to install the new update but on the install screen it says failed to verify and asks if i want to install anyways.
I choose yes and it errors out saying the update is for device "roth" and i have device "thor"
Does ayone know a workaround for this?
Have you messed with any system files or changed out the recovery or anything like that? I assume the Shield is going to look to make sure the system is all intact before allowing the update. Though the fact it says Roth which is a spelling error of Thor seems weird. Mine updated fine...
If you can find the update using root explorer you could delete it and redownload it.
I unlocked bootloader, installed cwm, and rooted using Kwonggers toolkit.
Sent from my XT1053 using Tapatalk
csos95 said:
I unlocked bootloader, installed cwm, and rooted using Kwonggers toolkit.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
OTAs will commonly fail if you install custom recovery. You'll have to wait for someone to make it into a zip that you can run through CWM.
csos95 said:
I unlocked bootloader, installed cwm, and rooted using Kwonggers toolkit.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
You probably still have CWM installed, to install an OTA you must first go back to the stock recovery. You can download it from here: http://goo.im/devs/agrabren/shield/original_images/recovery.img
Put that file in your ADB folder
To flash it, connect to usb and enable ADB debugging.
on PC type:
adb reboot bootloader
-Wait to reboot-
fastboot flash recovery recovery.img
-Now you have stock recovery installed-
Reboot the shield normally and install the OTA update, it should work.
Your bootloader is still unlocked, but you don't have root.
To install CWM, just follow the same instructions but replace the stock image with the CWM recovery image. You can download that here: http://goo.im/devs/agrabren/shield/cwm/recovery.img
The shield will be unrooted when you update. To root, simply flash CWM and reboot. CWM will ask you if you want to disable Stock reflashing, and if you want to root.
You may also need to flash the real SU zip from here: http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip?retrieve_file=1
For me, I was not able to let the SU app install the binary's alone, (Normal, or CWM method) I had to flash the SU zip.
But the update is smooth, and everything is working. Just no SD write support obviously.
CDeviant said:
You probably still have CWM installed, to install an OTA you must first go back to the stock recovery. You can download it from here: http://goo.im/devs/agrabren/shield/original_images/recovery.img
Put that file in your ADB folder
To flash it, connect to usb and enable ADB debugging.
on PC type:
adb reboot bootloader
-Wait to reboot-
fastboot flash recovery recovery.img
-Now you have stock recovery installed-
Reboot the shield normally and install the OTA update, it should work.
Your bootloader is still unlocked, but you don't have root.
To install CWM, just follow the same instructions but replace the stock image with the CWM recovery image. You can download that here: http://goo.im/devs/agrabren/shield/cwm/recovery.img
The shield will be unrooted when you update. To root, simply flash CWM and reboot. CWM will ask you if you want to disable Stock reflashing, and if you want to root.
You may also need to flash the real SU zip from here: http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip?retrieve_file=1
For me, I was not able to let the SU app install the binary's alone, (Normal, or CWM method) I had to flash the SU zip.
But the update is smooth, and everything is working. Just no SD write support obviously.
Click to expand...
Click to collapse
I tried this but it wouldn't download the ota again an I couldn't find where it was. So, I tried going back to stock to update but now it is stuck on the boot screen. I tried downloading a newer factory image from the nvidia website but now all of the windows links are locked behind some developer program that I have to make an account, submit an application, and wait for approval. Do you have any links to a recent factory restore image?
EDIT: I ended up just downloading mint and the linux .sh file to get the factory images.
You can use the root toolbox on this forum to reflash stock and relock and fix it
eric4shay said:
You can use the root toolbox on this forum to reflash stock and relock and fix it
Click to expand...
Click to collapse
That's what I tried before but it didn't work
If some updates please capture the OTA zip that downloads and upload it for us to tear apart.
What steps are you doing on there also email me [email protected] I will be able to respond more quickly
you dont have to
you can just use kwonggers toolkit, and just revert to stock kernel, stock system image, and stock recovery, you don't need to relock bootloader, but you must download the ota's separately, if you don't automatically see them under about shield> updates, then go to application manager>all> and force stop google services framework, then check for the update(it should now show up and download). this is what I have been doing, everytime I want to revert to the stock, most up to date ota, after this, you can reflash cwm recovery, flash the super su.zip and root again!
The ota (for some back assward reason) downloads not to the ota folder but to the cache folder. Anyway uploading the full otq zip now will edit with link when its done
Sent from my SHIELD using Tapatalk
Mechcondrid said:
The ota (for some back assward reason) downloads not to the ota folder but to the cache folder. Anyway uploading the full otq zip now will edit with link when its done
Sent from my SHIELD using Tapatalk
Click to expand...
Click to collapse
That could be more than one reason. But off the top of my head, maybe it's because the OTA folder is userspace, and there might not be enough Storage left on the internal. Cache is a separate partition, Things can even be deleted while running. So basically it insures enough space to download, and the user would never need to delete his own data to make room.
It might be awkward when you're looking for the OTA, but I think it's designed that way with the user in mind. :good:
Well regardless here's the ota file https://drive.google.com/file/d/0B2khjpo7TDP0Y3c0SjNNRWNXT28/edit?usp=sharing
Sent from my SCH-I545 using Tapatalk
I am currently using a Verizon HTC M8, it's a long story but the store sent me a Verizon phone even though I ordered the factory unlocked version. My problem is that I am on a GSM network, and the Verizon version of the phone updates over the CDMA network. My phone is currently on the 1.12.605.11 software number and I heard that the software has been recently updated to 1.55.605.2
My question is that I would like to know if anyone has the update and a method to manually update? As I am not likely to be able to get the OTA update anytime soon.
Thank in advance!!!
thirtyseven10 said:
I am currently using a Verizon HTC M8, it's a long story but the store sent me a Verizon phone even though I ordered the factory unlocked version. My problem is that I am on a GSM network, and the Verizon version of the phone updates over the CDMA network. My phone is currently on the 1.12.605.11 software number and I heard that the software has been recently updated to 1.55.605.2
My question is that I would like to know if anyone has the update and a method to manually update? As I am not likely to be able to get the OTA update anytime soon.
Thank in advance!!!
Click to expand...
Click to collapse
im sure someone is working on a flashable just be patient
Karl said:
im sure someone is working on a flashable just be patient
Click to expand...
Click to collapse
Understood... patience is not a trait I am known for. Thanks!
Karl said:
im sure someone is working on a flashable just be patient
Click to expand...
Click to collapse
I've manually patched the OTAs before but I found it easier to let the htc recovery to just update me. (Assuming you haven't changed a lot of stuff on the /system partition, root and xposed were the only two i changed on it)
This is assuming you have a custom recovery and are s-off (here is the gist of what i did, sorry its not very detailed)
Download the OTAPkg.zip
adb shell
su
cp /cache/fumo/OTAPkg.zip /sdcard/
adb pull /sdcard/OTAPkg.zip
extract firmware.zip from OTAPkg.zip
extract recovery.img from firmware.zip
adb reboot bootloader
fastboot flash recovery.img
fastboot reboot
have the system do its OTA via settings menu
after its done all i had to do was re-flash TWRP, re-root, and install my xposed library again .. TADA!
oops_iv said:
I've manually patched the OTAs before but I found it easier to let the htc recovery to just update me. (Assuming you haven't changed a lot of stuff on the /system partition, root and xposed were the only two i changed on it)
This is assuming you have a custom recovery and are s-off (here is the gist of what i did, sorry its not very detailed)
Download the OTAPkg.zip
adb shell
su
cp /cache/fumo/OTAPkg.zip /sdcard/
adb pull /sdcard/OTAPkg.zip
extract firmware.zip from OTAPkg.zip
extract recovery.img from firmware.zip
adb reboot bootloader
fastboot flash recovery.img
fastboot reboot
have the system do its OTA via settings menu
after its done all i had to do was re-flash TWRP, re-root, and install my xposed library again .. TADA!
Click to expand...
Click to collapse
or that :good:
There is a flashable zip coming tonight from a dev we're all familiar with. Hopefully tonight. He's at work right now.
Sent from my HTC6525LVW
1ManWolfePack said:
There is a flashable zip coming tonight from a dev we're all familiar with. Hopefully tonight. He's at work right now.
Sent from my HTC6525LVW
Click to expand...
Click to collapse
who is this masked man? and i hope he is going to make us baseband/radio flashable to:laugh:
Tonight? Oh, well, if it's tonight I can wait that long...... I hope........
My name's Harold and I'm a flashaholic.........
Karl said:
who is this masked man? and i hope he is going to make us baseband/radio flashable to:laugh:
Click to expand...
Click to collapse
He's doing it all. He does it right. I'm not going to introduce him, I'll let him do that ?
Sent from my HTC6525LVW
1ManWolfePack said:
He's doing it all. He does it right. I'm not going to introduce him, I'll let him do that ?
Sent from my HTC6525LVW
Click to expand...
Click to collapse
what a tease
I can guess??
oops_iv said:
I've manually patched the OTAs before but I found it easier to let the htc recovery to just update me. (Assuming you haven't changed a lot of stuff on the /system partition, root and xposed were the only two i changed on it)
This is assuming you have a custom recovery and are s-off (here is the gist of what i did, sorry its not very detailed)
Download the OTAPkg.zip
adb shell
su
cp /cache/fumo/OTAPkg.zip /sdcard/
adb pull /sdcard/OTAPkg.zip
extract firmware.zip from OTAPkg.zip
extract recovery.img from firmware.zip
adb reboot bootloader
fastboot flash recovery.img
fastboot reboot
have the system do its OTA via settings menu
after its done all i had to do was re-flash TWRP, re-root, and install my xposed library again .. TADA!
Click to expand...
Click to collapse
I'm stupid and forgot I deleted a lot of the VZW bloat with Titanium Backup, which, of course, this OTA checks for said bloat before going on with the install. Guess I'll just learn to be patient, otherwise this would have worked easily.
:laugh:
What if i am not rooted? and i am not in the US? What should i do to get the update?
Shouldn't the command be fastboot flash recovery recovery.img ?
You should be able to flash the official OTA zip in the stock recovery. http://forum.xda-developers.com/showthread.php?t=2722817
hgoldner said:
Well, so there are already a few threads on this, if you just can't wait to toy with it, check this post out.
As for me, I figure there will be a flashable zip available within a few hours so I won't have to redo my xposed modules with all the reboots, regain extreme powersave (for which there is also arleady a fix); redo sweep to sleep, etc. etc. etc. On the other hand, knowing how impatient I can be, I know what I'll be doing tomorrow afternoon otherwise.
Click to expand...
Click to collapse
There are now. Flashable zips
http://forum.xda-developers.com/showthread.php?t=2723159
New firmware/radios/boot.img for s-off
Sent from my HTC6525LVW using XDA Premium 4 mobile app
must.sayim said:
What if i am not rooted? and i am not in the US? What should i do to get the update?
Click to expand...
Click to collapse
You need at least temp root be able to manually install the update, weaksauce works great for this. Once you have temp root you can download the OTA from here http://forum.xda-developers.com/show....php?t=2722817 and then unzip and place the OTA.zip in /cache/fumo on your phone (I changed the permissions of the OTA.zip to allow read/write/execute as well). If you don't have a fumo folder in your cache create one and set the permissions to read/write/execute, for moving files and changing permissions I use root explorer.
Once you have the file in the correct location, flash the OTA through the stock recovery. That should be all, it worked for me...
thirtyseven10 said:
You need at least temp root be able to manually install the update, weaksauce works great for this. Once you have temp root you can download the OTA from here http://forum.xda-developers.com/show....php?t=2722817 and then unzip and place the OTA.zip in /cache/fumo on your phone (I changed the permissions of the OTA.zip to allow read/write/execute as well). If you don't have a fumo folder in your cache create one and set the permissions to read/write/execute, for moving files and changing permissions I use root explorer.
Once you have the file in the correct location, flash the OTA through the stock recovery. That should be all, it worked for me...
Click to expand...
Click to collapse
Didn't work
Hello,
So I just discovered this while trying to flash the 5.0.1 OTA from 5.0. I'm rooted on LRX21O via the Nexus Root Toolkit 1.9.9 (which is what I've always used in the past with no issues).
1 Tried flashing the OTA via Google notification push. It reboot, and no changes occur.
2 Fine - I try to use the Root Toolkit again. Boots into bootloader, appears to flash the radio and other necessary components. Reboots - no changes occur.
3 I then tried to just download the 5.0.1 package and flash everything manually via adb. Everything appears to go smoothly, and upon bootup Android updates all of its apps - still nothing. I appear to be completely stuck on LRX21O without any way to reflash stock or OTA's.
Anyone have any clue why this is occurring or have heard of such an issue before?
Thanks all.
Just flash factory images. With fastboot/flash-all script.
https://developers.google.com/android/nexus/images
You flash these in fastboot not adb
Sent from my Nexus 5 using Tapatalk
Did you not understand? I did flash in boot loader USING adb on my computer. All that bat script does is just automate the flashing of each image for you (system, radio, etc) so this is not helpful. I know how to flash, but flashing seems to have no effect despite successfully flashing via manually installing or just using the script
Sane116 said:
Did you not understand? I did flash in boot loader USING adb on my computer.
Click to expand...
Click to collapse
You use fastboot in bootloader, not adb.
I'm not the one asking for help. Anyways, carry on.
Your device's /system partition is tampered (you say you rooted it) and thus the OTA fails. Flash the 5.0 factory image (LRX21O) WITHOUT rooting/flashing kernels/whatever and then use the OTA zip to do adb sideload in the stock recovery to update to 5.0.1 LRX22C.
Manually use fastboot commands to flash system.img and boot.img of the full 5.0.1 factory image (not script). post the output please
I'm not the one asking for help. Anyways, carry on.
Click to expand...
Click to collapse
Sorry about that - didn't mean to come across snippy
It worked this time with fastboot. For future reference can this be done the same way with the OTA update zip instead of reflashing the entire image?
Sane116 said:
Sorry about that - didn't mean to come across snippy
It worked this time with fastboot. For future reference can this be done the same way with the OTA update zip instead of reflashing the entire image?
Click to expand...
Click to collapse
No, but if your phone is setup correctly you can sideload the ota zip in the stock recovery
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
No, but if your phone is setup correctly you can sideload the ota zip in the stock recovery
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Would you mind explaining this? I've used sideload in cwm and twrp before but I'm unsure of how to operate anything within stock recovery. adb won't even connect while in recovery. I would like to just remain on unrooted stock until xposed eventually get's developed for ART and flash zips that way.
Sane116 said:
Would you mind explaining this? I've used sideload in cwm and twrp before but I'm unsure of how to operate anything within stock recovery. adb won't even connect while in recovery. I would like to just remain on unrooted stock until xposed eventually get's developed for ART and flash zips that way.
Click to expand...
Click to collapse
Sideloading in the stock recovery works much the same as in a custom recovery. Boot into the stock recovery and there is an option to sideload. Then on your pc in a command window you type adb sideload update.zip. or whatever the file name is that you're trying to sideload. Obviously, if you can't get adb to recognize your device that's a problem. But that's a separate driver issue.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Sideloading in the stock recovery works much the same as in a custom recovery. Boot into the stock recovery and there is an option to sideload. Then on your pc in a command window you type adb sideload update.zip. or whatever the file name is that you're trying to sideload. Obviously, if you can't get adb to recognize your device that's a problem. But that's a separate driver issue.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
How can this be possible though without a custom recovery with the sideload feature? Stock recovery is essentially unusable as it just displays a picture of a dead android on a black screen.
Perhaps we're on different pages, or am I just confused still?
sideloading an OTA update from stock recovery
Hello, to make it work you will need to use the Google USB drivers you downloaded when you go into stock recovery then press the power button and volume up once then you will see a menu option with the "install update from adb option select this and plug in your phone to the computer. After this is done you will need to go to device manager and install the USB drivers from the Google USB drivers you downloaded. at this point after that is done you then go into the folder that has ADB installed and use adb sideload filename.zip
at this point your phone will accept the ota update package and you wont lose any data, I hope this helps..
-cs
Sane116 said:
How can this be possible though without a custom recovery with the sideload feature? Stock recovery is essentially unusable as it just displays a picture of a dead android on a black screen.
Perhaps we're on different pages, or am I just confused still?
Click to expand...
Click to collapse
When you get the dead android you need to press vol up and then press and release power. That'll get you into the stock recovery. It's stupid and I don't know why they made it that way
Sent from my Nexus 9 using XDA Free mobile app
thanks all, can't believe i never knew that volumeup+power got me into stock recovery options.
new issue: sideload works all well and perfect, but how can I bypass the "signature verification failed" flag that kicks me from the zip install every time?
Sane116 said:
thanks all, can't believe i never knew that volumeup+power got me into stock recovery options.
new issue: sideload works all well and perfect, but how can I bypass the "signature verification failed" flag that kicks me from the zip install every time?
Click to expand...
Click to collapse
Well you can't. The limitation of the stock recovery is you can only flash files signed by Google. That's why you need a custom recovery to flash most files
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Well you can't. The limitation of the stock recovery is you can only flash files signed by Google. That's why you need a custom recovery to flash most files
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
So can I just flash twrp with fastboot and go about that method? I believe it can bypass the signature. I am unlocked without root currently.
Sane116 said:
So can I just flash twrp with fastboot and go about that method? I believe it can bypass the signature. I am unlocked without root currently.
Click to expand...
Click to collapse
If you're trying to flash the update.zip to 5.0.1 you need to do that in the stock recovery. It will not work in twrp or cwm. I'm not sure what you're trying to do right now
Sent from my Nexus 9 using XDA Free mobile app
my apologies.
so originally i wanted to just flash the OTA. ended up performing a fresh install and un-rooted. but there's a few unsigned zips i like to have installed.
So I think I'm going to re-root, flash twrp, install my zips, and leave it at that. i'll just flash stock recovery whenever I need the OTA which should be quick now that I know what to do.
hope that sounds correct. thanks for all the help!