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
Related
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
Tried to boot in to recovery to flash a root zip..
When i volume up to enter recovery, screen goes black. I hit power button and TWRP opens but its unusable and dual screen..top and bottom. Slide to unlock is on the screen but nothing works. Only way out is to hold down power and reset.
Help!
Motochopper not working. I run SuperUS app and get "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
I agree!
DatacomGuy said:
Motochopper not working. I run SuperUS app and get "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
I agree!
Click to expand...
Click to collapse
What bootloader are you on (its in settings app)
cmendonc2 said:
what bootloader are you on (its in settings app)
Click to expand...
Click to collapse
10.6.1.8-20130225
DatacomGuy said:
10.6.1.8-20130225
Click to expand...
Click to collapse
10.6.1.8 is compatible with very few recoveries. Upgrade it to 10.6.1.27 to flash recoveries for KitKat ROMs.
cmendonc2 said:
10.6.1.8 is compatible with very few recoveries. Upgrade it to 10.6.1.27 to flash recoveries for KitKat ROMs.
Click to expand...
Click to collapse
Asus has 10.6.1.27.5 posted. This one safe?
How do i manually update this?
DatacomGuy said:
Asus has 10.6.1.27.5 posted. This one safe?
How do i manually update this?
Click to expand...
Click to collapse
I know you can use that firmware to install KitKat ROMs as shown here (http://forum.xda-developers.com/showthread.php?p=49028315).
Use the 10.6.1.27.5 firmware with this:
Tylorw1 said:
1. Download the latest version of Android for your tablet. Make sure you download the correct SKU version.
A. To find the SKU, go into settings, About tablet, and look for your Build Number, There are two letters (such as US,WW, TW, etc.) that is your SKU. When downloading the zip from ASUS', you must download the correct SKU zip.
2. Decompress downloaded .zip file (it will be another .zip)
3. Rename it to:
A. For the TF700 and TF300: EP201_768_SDUPDATE.zip
4. Make sure your MicroSD card is formatted Fat32. It must be Fat32 Format or it will not work.
5. Copy the file to (the root directory of) your MicroSD
6. Insert the MicroSD into the tablet
7. Shutdown (power off) the tablet
8. Power it on by pressing and holding VOLUME DOWN and POWER buttons simultaneously
9. When you see white text in the top left corner of the screen, release the buttons ^^ and press VOLUME UP button (on RCK, this is your recovery which should already be selected) until you see Android logo and process bar
10. Give the update process 5-10 minutes. It should not take longer than that. If it happens to run for more than 45 minutes to an hour, force shut down the tablet and see if it boots. If it does not, try rerunning steps 7-9.
Click to expand...
Click to collapse
Only issue is that it's flashed in recovery, which isn't functioning for me.. Or usable.
Can I flash cwm again, flash this firmware, then try twrp again?
DatacomGuy said:
Only issue is that it's flashed in recovery, which isn't functioning for me.. Or usable.
Can I flash cwm again, flash this firmware, then try twrp again?
Click to expand...
Click to collapse
You can also use fastboot to flash the ROM from your computer
Sent from my TF300T using xda app-developers app
cmendonc2 said:
You can also use fastboot to flash the ROM from your computer
Sent from my TF300T using xda app-developers app
Click to expand...
Click to collapse
Alright..
fastboot -i 0x0B05 flash recovery firmwarefile.zip
Click to expand...
Click to collapse
Is that the right syntax?
DatacomGuy said:
Alright..
Is that the right syntax?
Click to expand...
Click to collapse
Remove the "recovery", that means you are flashing to the recovery partition. So
Code:
fastboot -i 0x0B05 flash firmwarefile.zip
for the stock Rom.
cmendonc2 said:
Remove the "recovery", that means you are flashing to the recovery partition. So
Code:
fastboot -i 0x0B05 flash firmwarefile.zip
for the stock Rom.
Click to expand...
Click to collapse
I'm trying to flash "US_epad-user-10.6.1.27.5.zip" by doing:
fastboot -i 0x0b05 flash US_epad-user-10.6.1.27.5.zip"
Click to expand...
Click to collapse
and i get:
Unknown partition 'US_epad-user-10.6.1.27.5.zip'
error: cannot determine image filename for 'US_epad-user-10.6.1.27.5.zip'
Click to expand...
Click to collapse
What might i be doing wrong? I tried with the zip and without.
I checked the contents of the zip, and i have folder named "META-INF" with a bunch of content, and also a blob file, about 820mb.
Grr.
DatacomGuy said:
I'm trying to flash "US_epad-user-10.6.1.27.5.zip" by doing:
and i get:
What might i be doing wrong? I tried with the zip and without.
I checked the contents of the zip, and i have folder named "META-INF" with a bunch of content, and also a blob file, about 820mb.
Grr.
Click to expand...
Click to collapse
Extract the blob from the stock zip file. It should be a large file. Put that blob in your fastboot folder.
Code:
fastboot -i 0x0B05 flash system blob
cmendonc2 said:
Extract the blob from the stock zip file. It should be a large file. Put that blob in your fastboot folder.
Code:
fastboot -i 0x0B05 flash system blob
Click to expand...
Click to collapse
There we go.. Thank you very much for all your help.
Got it all flashed, all running well.
I tried to boot in to recovery, and got a "system error". I'm assuming i need to reflash the correct TWRP, and then try motochopper again? Or is there a better way to root..
EDIT: Currently running stock 4.2.1...
EDIT2: Is this the right one?
openrecovery-twrp-2.6.3.0-tf300t-JB.blob
DatacomGuy said:
There we go.. Thank you very much for all your help.
Got it all flashed, all running well.
I tried to boot in to recovery, and got a "system error". I'm assuming i need to reflash the correct TWRP, and then try motochopper again? Or is there a better way to root..
EDIT: Currently running stock 4.2.1...
Click to expand...
Click to collapse
Flashing the stock wipes the recovery, so you will need to flash the correct version of TWRP this time . I dont think you need TWRP for motochopper. Since you are unlocked, you can just flash the SU binaries directly from TWRP.
cmendonc2 said:
Flashing the stock wipes the recovery, so you will need to flash the correct version of TWRP this time . I dont think you need TWRP for motochopper. Since you are unlocked, you can just flash the SU binaries directly from TWRP.
Click to expand...
Click to collapse
Makes sense.. openrecovery-twrp-2.6.3.0-tf300t-JB.blob the right version?
You lost me on your last part.. where do i find the SU binaries?
DatacomGuy said:
Makes sense.. openrecovery-twrp-2.6.3.0-tf300t-JB.blob the right version?
You lost me on your last part.. where do i find the SU binaries?
Click to expand...
Click to collapse
Wait! Flashing that will brick it again!!! Dont flash that, use the -42 TWRP since you are on Android 4.2 now.
cmendonc2 said:
Wait! Flashing that will brick it again!!! Dont flash that, use the -42 TWRP since you are on Android 4.2 now.
Click to expand...
Click to collapse
LOL!
openrecovery-twrp-2.6.3.0-tf300t-4.2.blob
Got it.
What about root? After i flash, where do i find the SU binaries?
DatacomGuy said:
LOL!
openrecovery-twrp-2.6.3.0-tf300t-4.2.blob
Got it.
What about root? After i flash, where do i find the SU binaries?
Click to expand...
Click to collapse
TWRP should have the SU binaries built into it. If TWRP doesn't detect root when it is run from the bootloader, it asks you if you want to flash them. Are you trying to flash a KitKat ROM or a Jelly Bean ROM. KitKat needs TWRP -2.6.3.1
cmendonc2 said:
TWRP should have the SU binaries built into it. If TWRP doesn't detect root when it is run from the bootloader, it asks you if you want to flash them. Are you trying to flash a KitKat ROM or a Jelly Bean ROM. KitKat needs TWRP -2.6.3.1
Click to expand...
Click to collapse
i dont want to flash any rom right now, i just want to stick with stock 4.2.1...
Last time i flashed TWRP.. albeit incorrectly.. it didnt ask anything when i rebooted into recovery. I'm assuming thats when it asks....
Hi guys,
I run rooted unlocked Nexus 5 with CM11. I wanted to update the ROM but it failed - I read a bit and found out that it is due to old bootloader version. I would like to update it but I'm not a friend with ADB and stuff.... It would be great to use the most easiest way. I got OTA update notification but have no idea what it does - will it unroot the phone? will I lose CM11 ROM? Just trying to figure out what backups and steps shall I do to update my ROM. How shall I continue from here?
Thanks a bunch!
devcager said:
Hi guys,
I run rooted unlocked Nexus 5 with CM11. I wanted to update the ROM but it failed - I read a bit and found out that it is due to old bootloader version. I would like to update it but I'm not a friend with ADB and stuff.... It would be great to use the most easiest way. I got OTA update notification but have no idea what it does - will it unroot the phone? will I lose CM11 ROM? Just trying to figure out what backups and steps shall I do to update my ROM. How shall I continue from here?
Thanks a bunch!
Click to expand...
Click to collapse
Attempting to take the OTA will fail.
Download the factory image and extract bootloader-hammerhead-hhz11k.img
Boot your device into bootloader:
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
You have a custom recovery installed, right? Flash the bootloader zip via recovery. However, you need to get familiar with adb/fastboot as you're gonna need them if you ever find yourself in a tight situation to fix your device.
Open the "must read" thread linked in my signature and find the thread which has all the info about adb and fastboot.
vin4yak said:
You have a custom recovery installed, right? Flash the bootloader zip via recovery. However, you need to get familiar with adb/fastboot as you're gonna need them if you ever find yourself in a tight situation to fix your device.
Open the "must read" thread linked in my signature and find the thread which has all the info about adb and fastboot.
Click to expand...
Click to collapse
Thank you! I get it about ADB, I had to solve one my problem in the past via ADB. Anyway, I just need to find the 4.4.4 bootloader in ZIP (or probalby .img will work too?) and flash it? That's it? Does it wipe my phone or something?
You just need to flash the IMG via fastboot, no wiping required!
EddyOS said:
You just need to flash the IMG via fastboot, no wiping required!
Click to expand...
Click to collapse
Alright. One more thing. Is it possible to convert the IMG file I have into zip to be able to flash it in TWRP?
EDIT: I found that Nexus Toolbox for my 5 has the option to flash the bootloader image so I will try this variant.
devcager said:
Alright. One more thing. Is it possible to convert the IMG file I have into zip to be able to flash it in TWRP?
EDIT: I found that Nexus Toolbox for my 5 has the option to flash the bootloader image so I will try this variant.
Click to expand...
Click to collapse
You don't need to. Just boot into fastboot, connect to PC, fastboot flash bootloader name_of_file.img, reboot, done
it's easy you must become familiar with fastboot and add the second you aren't it will come back to haunt you
Sent from my Nexus 5 using Tapatalk
devcager said:
Alright. One more thing. Is it possible to convert the IMG file I have into zip to be able to flash it in TWRP?
EDIT: I found that Nexus Toolbox for my 5 has the option to flash the bootloader image so I will try this variant.
Click to expand...
Click to collapse
so you learned nothing. awesome.
Zepius said:
so you learned nothing. awesome.
Click to expand...
Click to collapse
Brick waiting to happen.
Add to ignore list
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
rootSU said:
Brick waiting to happen.
Add to ignore list
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
Click to expand...
Click to collapse
I'm still waiting for someone to make a thread saying their device is "bricked because flashed fastboot to adb using bootloader while in recovery with x toolkit"
Oneplus updated the OnePlus 6's Bootloader and you may ask yourself 'Can i still root?'
The answer is yes. It is easy.
1. At first, your bootloader has to be unlocked
2. Just download the Twrp.img and the Twrp installer from twrp.me, then the latest magisk installer
3. Put the magisk.zip and twrp installer zip into the root of your device and boot into bootloader
4. Now you have to open a new shell or cmd window in your adb folder, then type "Fastboot devices" there
5. If your phone is recognized, then do this command: " fastboot boot .\twrp-3.2.1-0-enchilada.img"
6. The op6 should boot into the TWRP, there type in your pincode, pattern, or what so ever you have. If you get a message because of system modification, click 'Keep read only'
7. Go to 'Install', then flash the TWRP installer zip, then magisk right after it
8. Just reboot and enjoy
The procedure is the same as always. I can confirm it's working because i rooted a few minutes ago
Just keep in mind the kernels and custom roms haven't been updated to 5.1.7 base yet and may not work until they are.
iElvis said:
Just keep in mind the kernels and custom roms haven't been updated to 5.1.7 base yet and may not work until they are.
Click to expand...
Click to collapse
Forgot the mention that, thanks!
Edit: Screenshots
Flash kernel works. Btw please don't create threads on how to root if the method hasn't changed lol
joemossjr said:
Flash kernel works. Btw please don't create threads on how to root if the method hasn't changed lol
Click to expand...
Click to collapse
Sorry, I thought that would be helpful for people who are worried about root because of updated bootloader.
A Moderator can remove this thread then
joemossjr said:
Flash kernel works. Btw please don't create threads on how to root if the method hasn't changed lol
Click to expand...
Click to collapse
Based on how things have been going so far, people are going to be asking. Just saying.
i understand butttttttttttttttttttttt this forum is flooded with how to flash twrp, how to root with 5.1.6, how to install 5.1.5 with twrp ect ect ect lol just trying to reduce clutter and make things a tad bit simpler. No offense guys lol
So if I already have twrp and Magisk installed is the method still the same?
Will this update lock the bootloader back?
Pretty sure I swiped to allow system modifications on my first twrp installation so will that matter?
joemossjr said:
i understand butttttttttttttttttttttt this forum is flooded with how to flash twrp, how to root with 5.1.6, how to install 5.1.5 with twrp ect ect ect lol just trying to reduce clutter and make things a tad bit simpler. No offense guys lol
Click to expand...
Click to collapse
Yes I know. I mean, you're right. Thought something like "new bootloader, new confusions". I justed wanted to help people if they're worried of a brick
dgunn said:
So if I already have twrp and Magisk installed is the method still the same?
Pretty sure I swiped to allow system modifications on my first twrp installation so will that matter?
Click to expand...
Click to collapse
Don't worry. You can use TWRP and your phone itself as always
Sconny said:
Don't worry. You can use TWRP and your phone itself as always
Click to expand...
Click to collapse
So do I flash the update in twrp?
Must the bootloader be unlocked again?
dgunn said:
So do I flash the update in twrp?
Must the bootloader be unlocked again?
Click to expand...
Click to collapse
No you flash in system via local upgrade
joemossjr said:
No you flash in system via local upgrade
Click to expand...
Click to collapse
Flash with local upgrade, reboot to fastboot, run twrp.img, install twrp, flash Magisk and reboot? No unlocking bootloader again?
If not correct please tell me
Yup that's it
joemossjr said:
No you flash in system via local upgrade
Click to expand...
Click to collapse
Flash in system.. you mean through the system updates in settings? And then I have to reinstall TWRP?
BossNexusS said:
Flash in system.. you mean through the system updates in settings? And then I have to reinstall TWRP?
Click to expand...
Click to collapse
Yes
joemossjr said:
Yes
Click to expand...
Click to collapse
What were the steps you followed if you don't mind?
Maybe someone will upload the full rom?
anyone tried hiding system updates inside magisk hide ?
it now shows only 224 update (canadian vpn), hence don't know what it will do when you take that route, anyone ?
I've always wanted to post one of these
https://developers.google.com/android/images
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
I was looking thru that post and didnt wanna risk wiping the device. I just had to wipe a few days ago due to Edxposed bootloop issue lol
Ha, yeah, I feel your pain there, wiping is way too much of a pain to do that frequently
Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
You can also flash the OTA file in stock recovery and not lose data.
spotmark said:
You can also flash the OTA file in stock recovery and not lose data.
Click to expand...
Click to collapse
Will it retain root or do you mean - https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Androider4Life said:
Retain root or have to re-root
Click to expand...
Click to collapse
Have to re-root using the Magisk method. Put stock boot on phone, patch boot with Magisk, put modded boot back on computer, and flash in fastboot. AFAIK, there is no way to retain root. Every time you flash the latest monthly patch, it flashes a new stock boot. Therefore, no root.
kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
There's a way with taking the ota through settings I found out how from a user on here which is:
Once received the ota , go to magisk first uninstall/restore images then download/install ota then DONT REBOOT, go back to magisk install magisk to inactive slot from the app then reboot and all should work with new ota update and have root still.
What is this update 4.3mb
Once again, my phone got bricked. I wanted to sideload, so I tried to get it into recovery, it wouldn't, so I tried a few times, and decided screw it. Now my phone bootloops. So, download the image and try flashing, it won't go into fastboot and fails. No matter what I do, I can't seem to save it. Can anyone help me with this? I'm trying a different computer in a sec, but, not sure if that will work either.
Edit: The different computer doesn't see it... FML
gettinwicked said:
Once again, my phone got bricked. I wanted to sideload, so I tried to get it into recovery, it wouldn't, so I tried a few times, and decided screw it. Now my phone bootloops. So, download the image and try flashing, it won't go into fastboot and fails. No matter what I do, I can't seem to save it. Can anyone help me with this? I'm trying a different computer in a sec, but, not sure if that will work either.
Edit: The different computer doesn't see it... FML
Click to expand...
Click to collapse
Just flash the factory image or ota thru flash.all bat file after you do/did the necessary steps like extract the images etc to platform tools folder on ur pc
Or visit here for more help/steps
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
gm007 said:
What is this update 4.3mb
Click to expand...
Click to collapse
Its just a security patch, we already had the updated rom in september, this just adds the latest security patch. Even though its only 4.3mb, its taking ages to patch, 10 mins still installing.
Jiggs82 said:
Just flash the factory image or ota thru flash.all bat file after you do/did the necessary steps like extract the images etc to platform tools folder on ur pc
Or visit here for more help/steps
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
Click to expand...
Click to collapse
You missed the part where I did try flashing the image. I've done this a hundred times, so, I did it right.
Anyway, I got it. I didn't realize my work computer had a USB-C port, so, I grabbed one and tried flashing the image with that. Worked! Thank God... I guess sdk tools doesn't like a USB 1 to C cable, and my phone doesn't like going into recovery...
Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
If you are rooted flash the boot.img of the factory image you are currently on to both slots:
Code:
fastboot flash boot --slot all boot.img
Then Do #4 'keep Data'
Homeboy76 said:
If you are rooted flash the boot.img of the factory image you are currently on to both slots:
Code:
fastboot flash boot --slot all boot.img
Then Do #4 'keep Data'
Click to expand...
Click to collapse
I am starting to feel more and more like a lot of the bootloop issues are being caused by OTAs swapping slots on install. Besides the --slot all patched boot, it might help to run the OTA twice to get it to install to both slots completely. Preferably though, quit using OTAs and work with -w removed flash-all installer (and even then possibly installing to both slots with an active slot swap in between and before rooting). The double install is common when installing custom ROMs, and the process for OTA sideloads is pretty similar.
Performance improvement, feels smooth and responsive. Glad i dont need to root this phone, ppl are having so many problems.
boe323 said:
Its just a security patch, we already had the updated rom in september, this just adds the latest security patch. Even though its only 4.3mb, its taking ages to patch, 10 mins still installing.
Click to expand...
Click to collapse
My download was 1.3 gb and took forever to install. That's more than just the security patch.. Build number is different too.
Sent from my Pixel 3 XL using Tapatalk
Worked exactly the same as the 10 and .C3 builds for me. Flash-all (minus -w) and patched boot in Magisk. No issues. It was not just security this month. See the functional patches in the bulletin.
https://source.android.com/security/bulletin/pixel/2019-10-01
is there new platform tools too?