I just got a new nexus 5
It had a 4.4.4 update immediately available. I updated
Now I'm not seeing a 5.0 update.
Can I speed up it finding the update somehow?
I am too scared to do the manual update. I might do something horribly wrong...
You have to wait till google pushes you update via OTA
lpganesh said:
You have to wait till google pushes you update via OTA
Click to expand...
Click to collapse
How frequently is google pushing the OTA when they have the 5.0.2?
I can't wait...
tonkku107 said:
How frequently is google pushing the OTA when they have the 5.0.2?
I can't wait...
Click to expand...
Click to collapse
All the time, in batches. If you can't wait, side load the ota or flash a factory image.
tonkku107 said:
How frequently is google pushing the OTA when they have the 5.0.2?
I can't wait...
Click to expand...
Click to collapse
You're on XDA, you don't have to wait. Just flash the factory image, you shouldn't even be taking an OTA anyway.
_MetalHead_ said:
You're on XDA, you don't have to wait. Just flash the factory image, you shouldn't even be taking an OTA anyway.
Click to expand...
Click to collapse
Why? I don't think I want the factory image. I would need to wipe everything. I have already stuff on this device.
Hiw much will the android SDK with the adb stuff take space from my computer then?
tonkku107 said:
Why? I don't think I want the factory image. I would need to wipe everything. I have already stuff on this device.
Hiw much will the android SDK with the adb stuff take space from my computer then?
Click to expand...
Click to collapse
If you're 100% stock then sideload the OTA, more info here: http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
If you're not 100% stock, sideloading won't work, but if your bootloader is unlocked you can:
fastboot flash system system.img
fastboot flash boot boot.img
Also flash the radio and bootloader if you want to. This won't wipe since you're not flashing userdata.img nor using -w.
And by 100% stock, I mean exactly one hundred percent.
I don't understand why an OTA is so special when you can get the update right away yourself, and often with much less trouble.
Lethargy said:
If you're 100% stock then sideload the OTA, more info here: http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
If you're not 100% stock, sideloading won't work, but if your bootloader is unlocked you can:
fastboot flash system system.img
fastboot flash boot boot.img
Also flash the radio and bootloader if you want to. This won't wipe since you're not flashing userdata.img nor using -w.
And by 100% stock, I mean exactly one hundred percent.
I don't understand why an OTA is so special when you can get the update right away yourself, and often with much less trouble.
Click to expand...
Click to collapse
Going to 5.x from 4.x without flashing userdata isn't a good idea.
You've been warned, OP.
beekay201 said:
Going to 5.x from 4.x without flashing userdata isn't a good idea.
You've been warned, OP.
Click to expand...
Click to collapse
Not really, if the usual internal storage derp happens then running one of the restorecon commands will usually fix it, but yeah, if you flash userdata then no chance of it happening.
Lethargy said:
Not really, if the usual internal storage derp happens then running one of the restorecon commands will usually fix it, but yeah, if you flash userdata then no chance of it happening.
Click to expand...
Click to collapse
Yeah, you're right: I forgot about the restorecon cmds.
:good:
They're best to avoid though. For some TWRP users, the restorecon needs to be repeated regularly. Not sure if the 2.8.3.0 has this issue though, I assume not.
Personally, I think its better to go full factory image from 4.4.x to 5. It takes longer but its a much better bet for compatibility issues.
Uhh...
I'm completely stock, so what are you talking about TWRP?
If there's a 'derp' I guess I better not flash it...
I don't get the restorecon stuff... Explain me what ot does
tonkku107 said:
Uhh...
I'm completely stock, so what are you talking about TWRP?
If there's a 'derp' I guess I better not flash it...
I don't get the restorecon stuff... Explain me what ot does
Click to expand...
Click to collapse
Nothing, I wasn't talking to you about TWRP
Restorecon fixes the sdcard issues that you'll probably have if you upgrade to lollipop badly.
I think if you're not confident, wait.
rootSU said:
Nothing, I wasn't talking to you about TWRP
Restorecon fixes the sdcard issues that you'll probably have if you upgrade to lollipop badly.
I think if you're not confident, wait.
Click to expand...
Click to collapse
Could you tell me more about the 'derp'?
I heard that google has stopped pushing the 5.0 because of it's issues.
There are no otas (atleast in the thread) from 4.4.4 to 5.0.1.
tonkku107 said:
Could you tell me more about the 'derp'?
I heard that google has stopped pushing the 5.0 because of it's issues.
There are no otas (atleast in the thread) from 4.4.4 to 5.0.1.
Click to expand...
Click to collapse
Not sure what derp you're talking about. You cannot ota from 4.4.4 to 5.0.1.
I don't think Google stopped pushing ota for 5.
rootSU said:
Not sure what derp you're talking about. You cannot ota from 4.4.4 to 5.0.1.
I don't think Google stopped pushing ota for 5.
Click to expand...
Click to collapse
It's possible with manta though.
Code:
I/SystemUpdateService( 759): processDownloadedFile /cache/930525cd9d47bae895e0c632c5f91c89af259c94.signed-mantaray-LRX22C-from-KTU84P.930525cd.zip
beekay201 said:
It's possible with manta though.
Code:
I/SystemUpdateService( 759): processDownloadedFile /cache/930525cd9d47bae895e0c632c5f91c89af259c94.signed-mantaray-LRX22C-from-KTU84P.930525cd.zip
Click to expand...
Click to collapse
Thats interesting.
rootSU said:
Not sure what derp you're talking about. You cannot ota from 4.4.4 to 5.0.1.
I don't think Google stopped pushing ota for 5.
Click to expand...
Click to collapse
This:
Lethargy said:
Not really, if the usual internal storage derp happens then running one of the restorecon commands will usually fix it, but yeah, if you flash userdata then no chance of it happening.
Click to expand...
Click to collapse
tonkku107 said:
This:
Click to expand...
Click to collapse
/sdcard doesn't exist. it's just a link to /data/media/0. Sometimes when not upgrading to 5.0 officially, that link breaks, so /sdcard looks empty. The command fixes it.
rootSU said:
/sdcard doesn't exist. it's just a link to /data/media/0. Sometimes when not upgrading to 5.0 officially, that link breaks, so /sdcard looks empty. The command fixes it.
Click to expand...
Click to collapse
So, basicly, it's nothing that I should even worry about, right?
Related
I'm on TWRP but I'd like to just adb push stock recovery. Is this possible just like I did to push TWRP?
waiting4mynexus said:
I'm on TWRP but I'd like to just adb push stock recovery. Is this possible just like I did to push TWRP?
Click to expand...
Click to collapse
Yep. Unzip a stock ROM. Find the recovery.img and fastboot it.
Why though?
theesotericone said:
Yep. Unzip a stock ROM. Find the recovery.img and fastboot it.
Why though?
Click to expand...
Click to collapse
Just so I can update when the OTAs come out. I'd rather not have to wipe and factory reset just to get the small updates they sent.
waiting4mynexus said:
Just so I can update when the OTAs come out. I'd rather not have to wipe and factory reset just to get the small updates they sent.
Click to expand...
Click to collapse
You can flash recoveries all day and not have to wipe anything. Unless your bootloader is still locked. Have you spent some time reading up on the device at all?
theesotericone said:
You can flash recoveries all day and not have to wipe anything. Unless your bootloader is still locked. Have you spent some time reading up on the device at all?
Click to expand...
Click to collapse
What reading do you suggest, this is my first nexus. Just came from an S3. I'm one for just making a couple mods as I need. I rooted so I could install navbar.
waiting4mynexus said:
What reading do you suggest, this is my first nexus. Just came from an S3. I'm one for just making a couple mods as I need. I rooted so I could install navbar.
Click to expand...
Click to collapse
Every sticky you find. I'm from Samsung devices as well. It took me less than 2 minutes to figure out a google device.
theesotericone said:
Every sticky you find. I'm from Samsung devices as well. It took me less than 2 minutes to figure out a google device.
Click to expand...
Click to collapse
I'm very satisfied with the nexus... No more constant modding or flashing this ROM and that to just avoid touchwiz and stay up-to-date.
waiting4mynexus said:
I'm very satisfied with the nexus... No more constant modding or flashing this ROM and that to just avoid touchwiz and stay up-to-date.
Click to expand...
Click to collapse
You can flash the OTAs through custom recoveries.
ihoneL some
Aerowinder said:
You can flash the OTAs through custom recoveries.
Click to expand...
Click to collapse
I think I understand... would I just need to download the OTA manually and flash it like any other zip?
Aerowinder said:
You can flash the OTAs through custom recoveries.
Click to expand...
Click to collapse
I was wondering the same thing. Do you have to wipe each update or just apply it and done?
Sent from my Nexus 5 using xda app-developers app
Badd_blood said:
I was wondering the same thing. Do you have to wipe each update or just apply it and done?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Don't wipe just apply it. The updates have been patched, not the whole rom. If you wipe you could be in trouble.
waiting4mynexus said:
I think I understand... would I just need to download the OTA manually and flash it like any other zip?
Click to expand...
Click to collapse
Badd_blood said:
I was wondering the same thing. Do you have to wipe each update or just apply it and done?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Disclaimer: These steps are assuming you are running Stock OS! No roms, no camera, sound, etc mods. If you're running a mod, then flash those back to stock to avoid issues.
Download the OTA, as well as the newest version of SuperSU (Version 1.8)
Transfer both files to the nexus via Android Transfer but dont put it in a folder, just so its at the bottom of the list
Boot to recovery
Flash OTA
Immediately Flash SuperSU after
Reebot
Done
I came from an S3 too, welcome to the Nexus fam
AceKingNYC said:
Disclaimer: These steps are assuming you are running Stock OS! No roms, no camera, sound, etc mods. If you're running a mod, then flash those back to stock to avoid issues.
Download the OTA, as well as the newest version of SuperSU (Version 1.8)
Transfer both files to the nexus via Android Transfer but dont put it in a folder, just so its at the bottom of the list
Boot to recovery
Flash OTA
Immediately Flash SuperSU after
Reebot
Done
I came from an S3 too, welcome to the Nexus fam
Click to expand...
Click to collapse
Would the xposed framework count as a mod? If you do have a mod then how do you go about updating on stock?
Badd_blood said:
Would the xposed framework count as a mod? If you do have a mod then how do you go about updating on stock?
Click to expand...
Click to collapse
I can't confidently say this because I have never used Xposed. But other folks have mentioned disabling it or uninstalling it i think?
As far as mods, if you have the camera mod etc, then just flash the stock APK for that mod so that its back as it was in it's original system state
Badd_blood said:
Would the xposed framework count as a mod? If you do have a mod then how do you go about updating on stock?
Click to expand...
Click to collapse
Anything that is different in /system or kernel may prevent ota. Xposed can be uninstalled via its gui
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
I'm new to rooting and android in general. I'm currently running 4.4 rooted with stock I believe. Says ponury kernal in my settings.
I'm trying to flash the update for 4.4.2 via the TWRP install. I get a failed error: error executing updater binary in zip.
I've made sure my zip is the 4.4 to 4.4.2 but still no luck. Any ideas what I can do? Do I need to wipe something before I can put it on there?
On a first thought, you need to get back to the original kernel.
Update from 4.4.1 to .4.4.2. has no problems with different kernels installed, however this won't work from 4.4. to 4.4.2.
The exact error message would be also helpful
tom1807 said:
On a first thought, you need to get back to the original kernel.
Update from 4.4.1 to .4.4.2. has no problems with different kernels installed, however this won't work from 4.4. to 4.4.2.
The exact error message would be also helpful
Click to expand...
Click to collapse
The error was : error executing updater binary in zip. I will look into getting back to stock.
matthewordie said:
The error was : error executing updater binary in zip. I will look into getting back to stock.
Click to expand...
Click to collapse
You need to fastboot flash the system and boot image from 4.4 if you have a custom kernel. Then flash the update
jd1639 said:
You need to fastboot flash the system and boot image from 4.4 if you have a custom kernel. Then flash the update
Click to expand...
Click to collapse
How do I fastboot flash the system and boot image? Can I do that from TWRP or do I need to use the command line with the fastboot? I have fastboot installed on my mac already. I was playing with that as well.
matthewordie said:
How do I fastboot flash the system and boot image? Can I do that from TWRP or do I need to use the command line with the fastboot? I have fastboot installed on my mac already. I was playing with that as well.
Click to expand...
Click to collapse
You'll need to get the factory image and extract the files. Inside there is another zip file which you'll need to extract. That's where you'll find the images. Use fastboot flash system system.img The Mac command is slightly different, I don't remember exactly what it is. To fastboot boot its the similar format
jd1639 said:
You'll need to get the factory image and extract the files. Inside there is another zip file which you'll need to extract. That's where you'll find the images. Use fastboot flash system system.img The Mac command is slightly different, I don't remember exactly what it is. To fastboot boot its the similar format
Click to expand...
Click to collapse
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.
matthewordie said:
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.
Click to expand...
Click to collapse
then stop modding your phone if you want OTAs.
its really that simple.
just flash the 4.4.2 factory images.
matthewordie said:
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.
Click to expand...
Click to collapse
Flashing the system image won't wipe anything
http://forum.xda-developers.com/showthread.php?p=14
Sent from my Nexus 5 using Tapatalk
Zepius said:
then stop modding your phone if you want OTAs.
its really that simple.
just flash the 4.4.2 factory images.
Click to expand...
Click to collapse
Well I really don't know the exact steps involved in "flashing the image". That's what I'm asking.
jd1639 said:
Flashing the system image won't wipe anything
Click to expand...
Click to collapse
Then I guess I had the wrong impression of what flashing the image is. Is there a guide available?
matthewordie said:
Then I guess I had the wrong impression of what flashing the image is. Is there a guide available?
Click to expand...
Click to collapse
Follow method#2. But only flash the system.img and boot.img. http://forum.xda-developers.com/showthread.php?p=47156064
Edit, your bootloader is unlocked, right? If not then you will lose all you data unlocking it
jd1639 said:
Follow method#2. But only flash the system.img and boot.img. http://forum.xda-developers.com/showthread.php?p=47156064
Edit, your bootloader is unlocked, right? If not then you will lose all you data unlocking it
Click to expand...
Click to collapse
Ah, I was close I actually did method 1. Yeah I did leave it unlocked since i'm going to root again right away. Thanks
Did anyone try out last night's software update? Any noticeable changes?
Initial observations: Up-gradation and initial boot up takes quite some time. What is more noticeable is the phone heating up during this process.
Found the OTA: (OTA_HIA_AERO_UL_M60_SENSE7GP_ATT_NA_Gen_Unlock_1.12.617.6-1.11.617.5_release_458832.zip) however TWRP nor stock recovery + stock boot will install it.
rlvl said:
Did anyone try out last night's software update? Any noticeable changes?
Initial observations: Up-gradation and initial boot up takes quite some time. What is more noticeable is the phone heating up during this process.
Click to expand...
Click to collapse
Any comment over the improvement in camera and performance?
Cashreedhar said:
Any comment over the improvement in camera and performance?
Click to expand...
Click to collapse
It's tough to see any changes considering it was all buttery smooth before as well
Wish HTC would post a changelog ...
That said.. The november update is supposed to fix the stagefright exploit.. So this update is critical.
What if your rooted can you still get the OTA update?
jbea007 said:
What if your rooted can you still get the OTA update?
Click to expand...
Click to collapse
I might be wrong, but I don't think anyone has successfully done this yet.
jbea007 said:
What if your rooted can you still get the OTA update?
Click to expand...
Click to collapse
ota upgrade rooted then this is possible because I have personally tried. focus is on twrp recovery restore or install will need to be system partition read only.At that time I was using [Root] HTC A9 thread completed. The other two threads I have not tried.
@jollywhitefoot: seen this?
edit: nevermind. You originated the thread and download links, lol.
http://www.htc.com/us/support/htc-one-a9/news/
Looks like the unlocked USA RUU: RUU_HIA_AERO_UL_M60_SENSE7GP_ATT_NA_Gen_Unlock_1.12.617.6.exe
Can't you flash just any ruu when s-off?
jaypeg123 said:
Can't you flash just any ruu when s-off?
Click to expand...
Click to collapse
You can flash it S-On or S-Off. If S-ON you MIGHT need to relock bootloader, but I'm not positive about that
This one: http://forum.xda-developers.com/attachment.php?attachmentid=3541020&d=1447433290
I just downloaded the RUU from the htc website
Won't I be able to push su.img back on and reinstall supersu.apk? Noticed that the first reboot when trying the OTA just boots it into TWRP. I'm going to try the RUU and see what happens. currently s-on bootloader unlocked with twrp. factory carrier unlocked
Did you see any changes after updating software guys ?
Will972 said:
Did you see any changes after updating software guys ?
Click to expand...
Click to collapse
Noticed that the storage menu in settings has a new set of options to format the sd card or use it as internal storage. Before it was only a button to unmount. if I remember correctly. Oh and I can't get root. I'm flashing back until I can find a modified boot.img that works
gunnarrrrr said:
Noticed that the storage menu in settings has a new set of options to format the sd card or use it as internal storage. Before it was only a button to unmount. if I remember correctly.
Click to expand...
Click to collapse
That was always there, but i don't think it shows up until you enable security
gunnarrrrr said:
Oh and I can't get root. I'm flashing back until I can find a modified boot.img that works
Click to expand...
Click to collapse
what problem are you having with root? I didn't have any issue re-rooting after the update
jollywhitefoot said:
That was always there, but i don't think it shows up until you enable security
what problem are you having with root? I didn't have any issue re-rooting after the update
Click to expand...
Click to collapse
That makes sense. and just booting after flashing the boot img. have one you want to share?
gunnarrrrr said:
That makes sense. and just booting after flashing the boot img. have one you want to share?
Click to expand...
Click to collapse
I just used the modified boot.img from the OP in jcase's root thread.
jollywhitefoot said:
I just used the modified boot.img from the OP in jcase's root thread.
Click to expand...
Click to collapse
I've been trying that one too but then after I reboot it just hangs at the HTC logo with the red text for about 20 minutes then I just end up giving up and reflashing
gunnarrrrr said:
I've been trying that one too but then after I reboot it just hangs at the HTC logo with the red text for about 20 minutes then I just end up giving up and reflashing
Click to expand...
Click to collapse
Are you formatting data in TWRP after flashing modified boot?
jollywhitefoot said:
Are you formatting data in TWRP after flashing modified boot?
Click to expand...
Click to collapse
*currently feeling like the dumbest person alive* thank you.
I didn't get the system update notification..
I'm rooted on unlock version ..
I've read that some people get the notification.. how is it possible
So I'm on a VP and am BL unlocked, twrp'd and rooted on 7.1 and want to update to 7.1.1. I want to flash the stock boot.img so I can take the OTA and update. Problem is I keep trying to extra the boot.img but can't get it to flash.
Not sure if I'm doing it wrong or have the wrong img but it's driving me nuts.
I've read through the forums and I know I'll get flamed for asking but I just need a bit of help with this.
Thx
mpetruzz said:
So I'm on a VP and am BL unlocked, twrp'd and rooted on 7.1 and want to update to 7.1.1. I want to flash the stock boot.img so I can take the OTA and update. Problem is I keep trying to extra the boot.img but can't get it to flash.
Not sure if I'm doing it wrong or have the wrong img but it's driving me nuts.
I've read through the forums and I know I'll get flamed for asking but I just need a bit of help with this.
Thx
Click to expand...
Click to collapse
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
Or, just flash the whole image with flash-all command. 7.1.1 (NMF26O, Dec 2016) is the one you want and its found here https://developers.google.com/android/images. You can edit the script and remove the -w and it'll keep the user data in tact. For me, it was better to start from scratch.
Droid1019 said:
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
Click to expand...
Click to collapse
Ok thanks! I had a few people give me the wrong command line that's prolly why it wasn't working. I'll give this a shot later!!
Droid1019 said:
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
Or, just flash the whole image with flash-all command. 7.1.1 (NMF26O, Dec 2016) is the one you want and its found here https://developers.google.com/android/images. You can edit the script and remove the -w and it'll keep the user data in tact. For me, it was better to start from scratch.
Click to expand...
Click to collapse
OK, so now I'm using those commands and still am getting the error message cannot load path/to/boot.img.
I can give the flash all a try, how to I edit the script to remove the -w??
mpetruzz said:
OK, so now I'm using those commands and still am getting the error message cannot load path/to/boot.img.
I can give the flash all a try, how to I edit the script to remove the -w??
Click to expand...
Click to collapse
If you get that error message it sounds like you don't have the right path for it to find that file. With the phone in bootloader mode I type in the command then drag the bit image into the terminal window and execute. I use a Mac so I don't know if you can drag the file in on a Windows machine. You'll have the same issue with the flash all if you don't have the right path.
mpetruzz said:
So I'm on a VP and am BL unlocked, twrp'd and rooted on 7.1 and want to update to 7.1.1. I want to flash the stock boot.img so I can take the OTA and update. Problem is I keep trying to extra the boot.img but can't get it to flash.
Not sure if I'm doing it wrong or have the wrong img but it's driving me nuts.
I've read through the forums and I know I'll get flamed for asking but I just need a bit of help with this.
Thx
Click to expand...
Click to collapse
Can't you just flash stock recovery and sideload the OTA? Seems a lot easier and safer.
bobby janow said:
Can't you just flash stock recovery and sideload the OTA? Seems a lot easier and safer.[/QUOTE
Yeah that does sound better!!. Honestly I might just leave it on 7.1 til some Roms come out.
Click to expand...
Click to collapse
mpetruzz said:
bobby janow said:
Can't you just flash stock recovery and sideload the OTA? Seems a lot easier and safer.[/QUOTE
Yeah that does sound better!!. Honestly I might just leave it on 7.1 til some Roms come out.
Click to expand...
Click to collapse
7.1.1 is worth it. Not sure when roms are coming out but with the OTA it's about a 10 minute install and reboot. You'll need to just fastboot flash recovery recovery.img for the stock, go directly into recovery with the vol keys / power key and then adb sideload the ota file after entering the recovery menu.
Did you flash another kernel? Is that why you want to replace the boot.img? If so you can probably just flash the OTA without changing anything other than recovery since it will overwrite the boot.img anyway.
Click to expand...
Click to collapse
bobby janow said:
mpetruzz said:
7.1.1 is worth it. Not sure when roms are coming out but with the OTA it's about a 10 minute install and reboot. You'll need to just fastboot flash recovery recovery.img for the stock, go directly into recovery with the vol keys / power key and then adb sideload the ota file after entering the recovery menu.
Did you flash another kernel? Is that why you want to replace the boot.img? If so you can probably just flash the OTA without changing anything other than recovery since it will overwrite the boot.img anyway.
Click to expand...
Click to collapse
Right now I'm only BL unlocked, twrp'd and rooted. No kernel modifications.
Where do I get the recovery.img from?
I was told by others here I need to flash the stock boot image in order to take the OTA. Jeez I'm getting so confused cause I keep getting different info
Click to expand...
Click to collapse
mpetruzz said:
bobby janow said:
Right now I'm only BL unlocked, twrp'd and rooted. No kernel modifications.
Where do I get the recovery.img from?
I was told by others here I need to flash the stock boot image in order to take the OTA. Jeez I'm getting so confused cause I keep getting different info
Click to expand...
Click to collapse
Stock recovery is in the image file from Google. Download it and extract it and flash it in bl. You might need things to "take" the OTA but I don't believe you need anything to flash the OTA (adb sideload) That will overwrite any kernel (boot.img) changes you made. But you said you made no kernel changes so why would you need to flash a boot.img?
Click to expand...
Click to collapse
bobby janow said:
mpetruzz said:
Stock recovery is in the image file from Google. Download it and extract it and flash it in bl. You might need things to "take" the OTA but I don't believe you need anything to flash the OTA (adb sideload) That will overwrite any kernel (boot.img) changes you made. But you said you made no kernel changes so why would you need to flash a boot.img?
Click to expand...
Click to collapse
OK so i'm in the system image file for 7.1 and am not seeing the recovery.img. Must be doing something wrong, but it's def not there. Anywhere else I can grab it from?
Also once I get it what would the adb command line be to flash it?
Click to expand...
Click to collapse
bobby janow said:
mpetruzz said:
Stock recovery is in the image file from Google. Download it and extract it and flash it in bl. You might need things to "take" the OTA but I don't believe you need anything to flash the OTA (adb sideload) That will overwrite any kernel (boot.img) changes you made. But you said you made no kernel changes so why would you need to flash a boot.img?
Click to expand...
Click to collapse
I got it and am all set!! Used the skipsoft tool to flash the stock recovery, then sideloaded the OTA!!
Thanks brother for all the help!!!!
Click to expand...
Click to collapse
Hey I'm pretty new to this but is there a way I can update without a computer, I dont mind losing root as long as I'm still unlocked... I'm using a Verizon phone on at&t if that matters... If not I can always to it tomorrow when I can get to a computer..
bobby janow said:
mpetruzz said:
7.1.1 is worth it. Not sure when roms are coming out but with the OTA it's about a 10 minute install and reboot. You'll need to just fastboot flash recovery recovery.img for the stock, go directly into recovery with the vol keys / power key and then adb sideload the ota file after entering the recovery menu.
Did you flash another kernel? Is that why you want to replace the boot.img? If so you can probably just flash the OTA without changing anything other than recovery since it will overwrite the boot.img anyway.
Click to expand...
Click to collapse
OK maybe i spoke too soon. I sideloaded the OTA and was able to install TWRP, but now when I flash the su zip I don't have the SuperSu app and can't get root. I've tried it twice and it looks like it's flashed but then when I reboot it's not there.
What am I not doing to get this too work??
Click to expand...
Click to collapse
mpetruzz said:
bobby janow said:
OK maybe i spoke too soon. I sideloaded the OTA and was able to install TWRP, but now when I flash the su zip I don't have the SuperSu app and can't get root. I've tried it twice and it looks like it's flashed but then when I reboot it's not there.
What am I not doing to get this too work??
Click to expand...
Click to collapse
http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156
This is where you'll need to go at this point. Lots to read but you have to do it in order to get it working correctly. Good luck, you'll get it.
Click to expand...
Click to collapse
bobby janow said:
mpetruzz said:
http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156
This is where you'll need to go at this point. Lots to read but you have to do it in order to get it working correctly. Good luck, you'll get it.
Click to expand...
Click to collapse
Got it, man this pixel is crazy different than what I'm used too. Thanks all for the help!
Click to expand...
Click to collapse
Hi, just tried to do this by flashing the old zip trough TWRP, but i always end to boot in recovery, maybe i'm doing something wrong...?
I tried this today and happened the same, i guess you have to clean flash to downgrade.
Also a tip, if you got stuck in recovery and yet cannot decrypt (doesn't ask for password/pin in TWRP), boot to fastboot mode, use the command "fastboot boot <the img file name for twrp>" so that you can boot directly to the img file from your PC. This way it will ask for your password.
Killua96 said:
Hi, just tried to do this by flashing the old zip trough TWRP, but i always end to boot in recovery, maybe i'm doing something wrong...?
Click to expand...
Click to collapse
You might try flashing again when you get booted back to TWRP. That way, you can get 9.01 flashed to both slots if it's not already. No guarantees, but it's worth a try.
maigre said:
You might try flashing again when you get booted back to TWRP. That way, you can get 9.01 flashed to both slots if it's not already. No guarantees, but it's worth a try.
Click to expand...
Click to collapse
I tried this way too but keep getting booted back to TWRP. Even did a wipe of the caches, system and data (not internal storage).
Is there anything I can still try?
jiatern said:
I tried this way too but keep getting booted back to TWRP. Even did a wipe of the caches, system and data (not internal storage).
Is there anything I can still try?
Click to expand...
Click to collapse
Flash Magisk again.
maigre said:
Flash Magisk again.
Click to expand...
Click to collapse
I did as well but it didn't help. Still the same.
jiatern said:
I did as well but it didn't help. Still the same.
Click to expand...
Click to collapse
Backup all your data outside the phone and flash a fastboot rom, it worked with me stuck in fastboot and I got back from that horrible 9.0.2
Killua96 said:
Backup all your data outside the phone and flash a fastboot rom, it worked with me stuck in fastboot and I got back from that horrible 9.0.2
Click to expand...
Click to collapse
Why horrible?
PuCiNhOOO said:
Why horrible?
Click to expand...
Click to collapse
Keyboard continuously crash 'cause the new gesture system, that have longer animations and the recent app one loses the vibration feedback and it' s also a lot confusing.
Anyway you can read the same things in the ota's thread, unfortunately are widespread problems
Killua96 said:
Keyboard continuously crash 'cause the new gesture system, that have longer animations and the recent app one loses the vibration feedback and it' s also a lot confusing.
Anyway you can read the same things in the ota's thread, unfortunately are widespread problems
Click to expand...
Click to collapse
I think they pushed the update too fast from beta to stable... But yes, agree with the gestures bug... Its a fact, but the other stuff is good
Killua96 said:
Backup all your data outside the phone and flash a fastboot rom, it worked with me stuck in fastboot and I got back from that horrible 9.0.2
Click to expand...
Click to collapse
Can you link me to the exact fastboot rom you flashed? Some said I have to use the downgrade zip from OnePlus to Oreo 5.1.1 then only upgrade to 9.0.1. The OP of the fastboot rom said the rom is not for downgrading.
Did you downgrade to Oreo first or directly flash the 9.0.1 fastboot rom?
jiatern said:
Can you link me to the exact fastboot rom you flashed? Some said I have to use the downgrade zip from OnePlus to Oreo 5.1.1 then only upgrade to 9.0.1. The OP of the fastboot rom said the rom is not for downgrading.
Did you downgrade to Oreo first or directly flash the 9.0.1 fastboot rom?
Click to expand...
Click to collapse
I've wiped everything, then downgraded to Pie directly, but I was in a slightly different situation (only fastboot available).
Just to be sure flash the Oreo one and then upgrade to Pie.
With the whole A/B partition layout it should be easier to downgrade too right?