10i for T-Mobile V20 H918 is out.
It's still anti-rollback v00. :good:
Android Security Patch: 2016-12-01 (dirtycow/recowvery patched)
Download Link
UPPERCUT should work if using LGUP/KDZ.
If you flash this KDZ there is no current root method for 10i... so no TWRP etc (at this very moment anyway).
Everyone who can only boot to download mode.. this should save you.
those w/TWRP already can use the images (or wait for someone to make a flashable "rom" zip.
H91810-system.img.zip is just the system.img compressed, not a flashable zip.
if flashing the stock system.img/boot.img be careful not to lose TWRP..
delete the "recovery-from-boot.p" in system while still in TWRP if you want to be extra safe.
I don't have a V20 and won't be supporting this thread. Just providing files.
Thanks for this. Wonder what the changes from v10d are (other the exploit patch)
If and when someone creates a flashable zip, can we flash SuperSU after we flash the ROM to still have root?
Great.. My replacement is coming today which means it'll probably self update on first boot before I can do anything about it..
I love you daddi
Is this also OTA? I see nothing
kyledowling said:
If and when someone creates a flashable zip, can we flash SuperSU after we flash the ROM to still have root?
Click to expand...
Click to collapse
yes, that's how it works. tho.. idk if it's user-error or what... sometimes people flash supersu and it doesn't patch the boot.img and when they boot into android they lose twrp. hasn't happened to me but ¯\_(ツ)_/¯ . so that's why I also suggested removing the recovery-from-boot.p as an option.
people could also just dd the images manually if they don't want to wait for a zip... but I guess those comfortable with dd already know that.
Swizzle82 said:
Great.. My replacement is coming today which means it'll probably self update on first boot before I can do anything about it..
Click to expand...
Click to collapse
lol just don't put a sim in or connect it to wifi before you use recowvery.
autoprime said:
yes, that's how it works. tho.. idk if it's user-error or what... sometimes people flash supersu and it doesn't patch the boot.img and when they boot into android they lose twrp. hasn't happened to me but ¯\_(ツ)_/¯ . so that's why I also suggested removing the recovery-from-boot.p as an option.
people could also just dd the images manually if they don't want to wait for a zip... but I guess those comfortable with dd already know that.
lol just don't put a sim in or connect it to wifi before you use recowvery.
Click to expand...
Click to collapse
Great idea.. Sometimes you're smart, lol
Swizzle82 said:
Great idea.. Sometimes you're smart, lol
Click to expand...
Click to collapse
altho now that i think about it.. they may force you on the setup screen. but theres no way it'll download/install in the time it takes to get through setup. so just disable internet as soon as you're setup. :good:
autoprime said:
altho now that i think about it.. they may force you on the setup screen. but theres no way it'll download/install in the time it takes to get through setup. so just disable internet as soon as you're setup. :good:
Click to expand...
Click to collapse
What I usually do is make a twrp back up from my old phone and restore it on the new phone after making a fake backup and moving the old one in the new folder the fake backup created. Theoretically this should restore my google account without ever having to initially setup my account when I turn on the new phone. Right? Or do you think it'll cause authentication issues?
Swizzle82 said:
Great.. My replacement is coming today which means it'll probably self update on first boot before I can do anything about it..
Click to expand...
Click to collapse
As long as it isn't preloaded you should be able to get around it...
Common sense isn't all that common
ZDeuce2 said:
As long as it isn't preloaded you should be able to get around it...
Common sense isn't all that common
Click to expand...
Click to collapse
I'm sure I'll get it figured out.
Hopefully @Eliminater74 will make part 1 & 2 ROM for H918 users.
mingkee said:
Hopefully @Eliminater74 will make part 1 & 2 ROM for H918 users.
Click to expand...
Click to collapse
Is he coming to the v20. Plz say yes.
System.img.zip, do I just rename it to system.img? Cause I extracted from zip file and system.img did not flash. But when I renamed it, it flashed but wouldn't boot.
kcsevo said:
System.img.zip, do I just rename it to system.img? Cause I extracted from zip file and system.img did not flash. But when I renamed it, it flashed but wouldn't boot.
Click to expand...
Click to collapse
If you really want this, just use the LG Bridge and update it through that. It's much easier than flashing manually and accomplishes the same thing.
kibmikey1 said:
If you really want this, just use the LG Bridge and update it through that. It's much easier than flashing manually and accomplishes the same thing.
Click to expand...
Click to collapse
Oh sweet! But for the file itself do I need to extracted or rename the file? I flashed the system.img and boot in twrp but it hung in LG logo. And I'm also trying to retain root.
kcsevo said:
Oh sweet! But for the file itself do I need to extracted or rename the file? I flashed the system.img and boot in twrp but it hung in LG logo
Click to expand...
Click to collapse
You don't need the file at all. Just download the LG Bridge from the LG website, install the LG Universal mobile drivers, plug in your phone and use the software update option. It does it all by itself, and will restart your phone on it's own.
kibmikey1 said:
You don't need the file at all. Just download the LG Bridge from the LG website, install the LG Universal mobile drivers, plug in your phone and use the software update option. It does it all by itself, and will restart your phone on it's own.
Click to expand...
Click to collapse
Do i need to be back factory stock including recovery to use this option? And I'm guessing this way would make me lose root? Thank you for your responses.
kcsevo said:
Do i need to be back factory stock including recovery to use this option? And I'm guessing this way would make me lose root? Thank you for your responses.
Click to expand...
Click to collapse
You only need to plug in your phone and let it work. Since this is a stock image, you will lose root. Also, the as described in the original post on page 1, the December security patch also patches the dirty cow exploit used to achieve root, so once you flash this, you'll be stock unrooted until a new method comes along.
Related
I managed to pull the 5.0 Lollipop OTA update file and load it to Android File Host.
Word of warning, should you try to use this file to update, you will likely lose root, possibly without the chance to root once complete or even ODIN back to 4.x. This is primarily for devs to use to try to make pre-rooted and custom ROMs with.
The link to the file is below:
https://www.androidfilehost.com/?fid=95916177934552137
@muniz_ri, @RockRatt, @iB4STiD and @Joe-Tech, I believe you guys may be interested in this.
May the odds ever be in our favor.
@Apoplectic1 you awesome man, will see what i can do with it
Doesn't flash, wipes /Data stating "Footer is wrong"
Apoplectic1 said:
I managed to pull the 5.0 Lollipop OTA update file and load it to Android File Host.
Word of warning, should you try to use this file to update, you will likely lose root, possibly without the chance to root once complete or even ODIN back to 4.x. This is primarily for devs to use to try to make pre-rooted and custom ROMs with.
The link to the file is below:
https://www.androidfilehost.com/?fid=95916177934552137
@muniz_ri, @RockRatt, @iB4STiD and @Joe-Tech, I believe you guys may be interested in this.
May the odds ever be in our favor.
Click to expand...
Click to collapse
Thanks for the heads up. I will create the ROM later tonight.
DankHeals said:
Doesn't flash, wipes /Data stating "Footer is wrong"
Click to expand...
Click to collapse
It's not a flashable zip. Even if you were to flash it, it would not be able to update you due to you being rooted, it will fail I'm afraid.
muniz_ri said:
Thanks for the heads up. I will create the ROM later tonight.
Click to expand...
Click to collapse
I've probably told you this about a dozen times now, but you are the man! :highfive:
Apoplectic1 said:
I've probably told you this about a dozen times now, but you are the man! :highfive:
Click to expand...
Click to collapse
No worries and thanks for capturing the ota.
Apoplectic1 said:
It's not a flashable zip. Even if you were to flash it, it would not be able to update you due to you being rooted, it will fail I'm afraid.
Click to expand...
Click to collapse
I fully unrooted and went stock before attempting, but that's a shame. Thought it would be flashable via update in stock recovery. :/
cant wait to have this flashable.. been waiting soooo long
When O when will the wait end.... Canada S4 and I still can't install this AT&T one
How to use this file ???
DankHeals said:
Doesn't flash, wipes /Data stating "Footer is wrong"
Click to expand...
Click to collapse
Because you flashed the archived cfg file. To flash the update you have to unpack the zip file and change the extension of the CFG file to ZIP. But anyway even this cfg fails to install, so don't try because i already did.
Update via adb or external sd card using stock recovery doesn't work !
Is there a way to flash it ???
lordnihilusmd said:
Because you flashed the archived cfg file. To flash the update you have to unpack the zip file and change the extension of the CFG file to ZIP. But anyway even this cfg fails to install, so don't try because i already did.
Update via adb or external sd card using stock recovery doesn't work !
Is there a way to flash it ???
Click to expand...
Click to collapse
Thanks for the info... been looking for a way to flash this without success
W1zz_ said:
Thanks for the info... been looking for a way to flash this without success
Click to expand...
Click to collapse
You could try pushing the cfg file to /cache/fota, uninstall Safestrap, full unroot, reboot and then installing the update the standard way, but getting root afterward is iffy.
Can somebody pull out the modem?
Apoplectic1 said:
You could try pushing the cfg file to /cache/fota, uninstall Safestrap, full unroot, reboot and then installing the update the standard way, but getting root afterward is iffy.
Click to expand...
Click to collapse
Thanks man, my situation is a little more complicated however since I have the i337m(Canadian S4) wasn't sure I'd be able to install this OTA in any way. Kind of came to the conclusion that I will have to wait for a custom Rom, unless my understanding of how this all works is wrong.
I will try but i already did full unroot . When flashing via recovery it says something like frameworkres-apk has unexpected content ... Standard way ? but it will tell me software update interrupted
Apoplectic1 said:
It's not a flashable zip. Even if you were to flash it, it would not be able to update you due to you being rooted, it will fail I'm afraid.
Click to expand...
Click to collapse
It won't flash even without root. Tried flashing via stock recovery, no dice just like the others. Flashing results in wiping /data.
Short road...
Easiest way possible odin back to NB1 then take the OTA to lollipop that's the easiest way man
lordnihilusmd said:
I will try but i already did full unroot . When flashing via recovery it says something like frameworkres-apk has unexpected content ... Standard way ? but it will tell me software update interrupted
Click to expand...
Click to collapse
brownie9987 said:
Easiest way possible odin back to NB1 then take the OTA to lollipop that's the easiest way man
Click to expand...
Click to collapse
OTA from ODIN stock has never worked for me. Maybe it's because it's SIM-less?
What do you mean by Simless?
The link below is a stock flashable zip of the LG V20 10p ROM. I extracted it from the latest 10p KDZ file using kdztools and python 2.7 on Windows. I built the ROM from the extraction using Superrs kitchen version 3 on Linux.
A HUGE thanks goes out to Superr who is ALWAYS helpful and I couldn't do this with out his help.
READ ALL WARNINGS BEFORE PROCEEDING
This rom is not rooted but you can flash magisk or SuperSU to root it. It does not flash recovery. It does not encrypt.
Using magisk it works with both Samsung and Android [email protected] which is the main reason I built it.
Issues: none, but see warnings
Flash at your own risk. I'm not responsible if your device gets bricked.
Warnings based on what we know:
WARNING #1 You must flash the 10p modem and bootloader for this to work. If you don't you will soft brick.
WARNING #2 Once you go to 10p modem and bootloader you can't go back to previous versions. If you try you will HARD brick your device.
WARNING #3 10P rom only works with 10p modem and 10p bootloader. Any other combo SOFT bricks.
WARNING #4 TWRP backups of previous versions will not restore correctly once you are on 10p. When you restore a previous version (10k and before) you will soft brick. You can unbrick by just installing the 10p ROM, modem, and bootloader over the top of your restore *****Restores and Backups of 10p roms work just fine.
BOTTOM LINE: Going to 10p is a TOTAL commitment and there probably will never be a way to go back. That said, I'm on 10p and so far it works great.
ROM Links:
Drive: https://drive.google.com/file/d/0B3y-9RMsaMSbOTRENzBObzU0Qkk/view?usp=drivesdk
Get 10p Modem and 10p bootloader here:
https://forum.xda-developers.com/v20/development/firmware-twrp-flashable-bootloader-modem-t3547268
*****Be sure to thank the OP on that thread!*****
Here's the stock 10p kernel, just for grins. 10n and 10p Kernels are both ARB 1 and work with this ROM
drive: https://drive.google.com/open?id=0B3y-9RMsaMSbYk56a2txV3gtMkE
Clean install instructions: twrp backup, wipe, install ROM, install 10p modem, install 10p bootloader, install root of your choice, reboot
Dirty install works fine over Weta ROM or NATF ROM, but not over aosp or lineage roms: twrp backup, install ROM, install 10p modem, install 10p bootloader, install root of your choice, reboot.
Enjoy. Please give thanks if this ROM is helpful for you.
texasaggie1 said:
Hi All, I have extracted the latest 10P rom from a KDZ file. I am testing (looks Great so far) and will upload it shortly.
Click to expand...
Click to collapse
I see the kdz I uploaded is in great use, Sucks I cant use the flashbale I updated and it does not allow you to downgrade havn't tried to root it yet
dudeawsome said:
I see the kdz I uploaded is in great use, Sucks I cant use the flashbale I updated and it does not allow you to downgrade havn't tried to root it yet
Click to expand...
Click to collapse
dang, that sucks man
texasaggie1 said:
dang, that sucks man
Click to expand...
Click to collapse
It does but I believe someone will find a exploit to root it
TWRP Backup
be sure to make a nand / twrp backup before you do anything.
apparently the system.img or boot.img made a change somewhere and now my phone wont boot at all
texasaggie1 said:
apparently the system.img or boot.img made a change somewhere and now my phone wont boot at all
Click to expand...
Click to collapse
Come on guys, you don't all have to go brick your phones just to keep me company
But seriously... hard brick?
If so I feel for you man. Lets hope a solution arrives sooner rather than later. (Well I guess you Americans can just give it to you dealer, and everything will be allright)
nvm, jumped the gun there
back in business using a modded script from 10k
If it's a modded script than it's no longer a true 10p right?
storm68 said:
If it's a modded script than it's no longer a true 10p right?
Click to expand...
Click to collapse
The script only tells the recovery what to flash and doesn't make changes to boot or system.
Sent from my LG-H918 using Tapatalk
bxlegend said:
The script only tells the recovery what to flash and doesn't make changes to boot or system.
Click to expand...
Click to collapse
Ah. Gotcha! Thanks for the info. ?
Yes its a true 10P. Looks like the rom needs 10p bootloader and modem to function. It's working like a champ for me now. I am uploading and will post after work tomorrow
storm68 said:
Ah. Gotcha! Thanks for the info.
Click to expand...
Click to collapse
People are bricking phones with 10p looks like. I put fotakill on phone and for the first time I still get the update. Ugh. Almost like they are delivering the update in a different method now. Don't know! ?
storm68 said:
People are bricking phones with 10p looks like. I put fotakill on phone and for the first time I still get the update. Ugh. Almost like they are delivering the update in a different method now. Don't know!
Click to expand...
Click to collapse
not sure why anyone would flash the modem/bootloader separately of the full ROM... that's just asking for trouble
storm68 said:
People are bricking phones with 10p looks like. I put fotakill on phone and for the first time I still get the update. Ugh. Almost like they are delivering the update in a different method now. Don't know! ?
Click to expand...
Click to collapse
Turn off notifications for Play Store and you will stop getting bugged to update
texasaggie1 said:
Turn off notifications for Play Store and you will stop getting bugged to update
Click to expand...
Click to collapse
Lol... That's not the update I'm talking about. The system update... ?
storm68 said:
Lol... That's not the update I'm talking about. The system update...
Click to expand...
Click to collapse
The guy who posted the 10p ota update was linking to google servers. So maybe ota is delivered through the google services?
askermk2000 said:
The guy who posted the 10p ota update was linking to google servers. So maybe ota is delivered through the google services?
Click to expand...
Click to collapse
Hhmmmm
storm68 said:
Lol... That's not the update I'm talking about. The system update...
Click to expand...
Click to collapse
I know but if you turn off play store notifications (block them) you won't get bugged about the 10p update and by default you won't accidentally say yes to it ?
I know it says you can't restore previous backups, but can you do a full install of pre-10p ROMs if you decide this one isn't suitable?
I have just received the OTA and it is failing to install...
Anybody else facing this issue? Any ideas on how to fix it?
I have my Pixel 2 rooted right now, not sure if this can affect OTA?
luizffgarcia said:
I have my Pixel 2 rooted right now, not sure if this can affect OTA?
Click to expand...
Click to collapse
Being rooted is your issue
krelvinaz said:
Being rooted is your issue
Click to expand...
Click to collapse
What is the easiest way around it then? Do i have to download the factory image and flash it losing everything i have configured? Or is there another way?
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Follow them steps
Nothing seems to work for me though i cant install ota no matter what but hopefully it should work for you.
It has for everyone else!
UpGrad3 said:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Follow them steps
Nothing seems to work for me though i cant install ota no matter what but hopefully it should work for you.
It has for everyone else!
Click to expand...
Click to collapse
Thanks but this also does not work for me, it starts step 1 but then the installation fails...
Any other options?
EDIT: LOL and now i lost magisk and root
luizffgarcia said:
Thanks but this also does not work for me, it starts step 1 but then the installation fails...
Any other options?
EDIT: LOL and now i lost magisk and root
Click to expand...
Click to collapse
I'm in the same boat...dies at step 1. Look familiar?
https://forum.xda-developers.com/showpost.php?p=74518728&postcount=53
Only I didn't lose root, as I re-installed Magisk before rebooting.
JayBlack_686 said:
I'm in the same boat...dies at step 1. Look familiar?
https://forum.xda-developers.com/showpost.php?p=74518728&postcount=53
Only I didn't lose root, as I re-installed Magisk before rebooting.
Click to expand...
Click to collapse
Yeah i sideloaded the OTA and it worked, but now i am struggling to put back snoke and magisk...
Every time i try i get stuck in the google logo, not sure whats going wrong
luizffgarcia said:
Yeah i sideloaded the OTA and it worked, but now i am struggling to put back snoke and magisk...
Every time i try i get stuck in the google logo, not sure whats going wrong
Click to expand...
Click to collapse
That happened the first time I tried to root. Had to flash the factory image and start over. Guess I could do that...but seems there has to be an easier way. I'm really curious why the method in that guide doesn't work for me.
Does flashfire work to install the OTA?
luizffgarcia said:
Thanks but this also does not work for me, it starts step 1 but then the installation fails...
Any other options?
EDIT: LOL and now i lost magisk and root
Click to expand...
Click to collapse
JayBlack_686 said:
I'm in the same boat...dies at step 1. Look familiar?
https://forum.xda-developers.com/showpost.php?p=74518728&postcount=53
Only I didn't lose root, as I re-installed Magisk before rebooting.
Click to expand...
Click to collapse
Download the full factory image. Open the flash all bat file with notepad and edit out the -w and save it. Then run it. That will flash the full factory image but leave apps and data in place.
Then you reroot it.
TonikJDK said:
Download the full factory image. Open the flash all bat file with notepad and edit out the -w and save it. Then run it. That will flash the full factory image but leave apps and data in place.
Then you reroot it.
Click to expand...
Click to collapse
Thanks. When I re-root, do I need to do the whole patch boot image process again? Or should I reuse the patched_boot.img that I used when I rooted the first time?
JayBlack_686 said:
Thanks. When I re-root, do I need to do the whole patch boot image process again? Or should I reuse the patched_boot.img that I used when I rooted the first time?
Click to expand...
Click to collapse
Redo it, otherwise you are a month behind on the boot IMG.
TonikJDK said:
Redo it, otherwise you are a month behind on the boot IMG.
Click to expand...
Click to collapse
Thank you. One last question: when I rooted, I used the snoke kernel and pointed to that .img file when patching the boot image (no reason, other than that's what everyone seemed to be using when root first happened). It sounds like this time, I should get the full factory image, extract, grab the boot.img from within that and patch THAT to be up to date. Correct?
JayBlack_686 said:
Thank you. One last question: when I rooted, I used the snoke kernel and pointed to that .img file when patching the boot image (no reason, other than that's what everyone seemed to be using when root first happened). It sounds like this time, I should get the full factory image, extract, grab the boot.img from within that and patch THAT to be up to date. Correct?
Click to expand...
Click to collapse
Correct, you can use whatever boot IMG you want. Snoke may be updated to November... don't know...bit if it is and you like it use it.
Waiting for answers. I finally succeeded with rooting my xiaomi mi a2 lite, everything works perfect, I was so excited to install Xposed but then my phone started to lag AF. I uninstalled it and then the update show up in the notification bar, great but "couldn't install system update". Is it because of the root or TWRP?
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?
I signed up for a beta test on centernode and received a smartphone to test. The phone is so new that I cannot find any information about it on the internet. The bootloader is unlocked on it. I was reading that you can use magisk to root any device with an unlocked bootloader and system image. Since the phone is so new I cannot find a system image. Is it still possible to root the device? Is there a way I can backup the stock ROM and create a system image that way? Is there something else that will work? I really want to root the device because it came with a preinstalled app which is a system booster type app. It will not let me uninstall it, disable it, or force stop it. When I install my app for my alarm clock it keeps killing the app and the alarm will not go off. I have went through all of the app settings and cannot get it to stop. It also keeps interfering with my VPN. I would also like to root th device to remove some of the bloatware and to have access to the HOST file. Could someone please help me this? I would greatly appreciate it. Thanks guys!
I'm not known for giving good advice but if I was in your situation I would try to install the lastest version of Magisk and hope for the best. Knowing how I am it would be driving me nuts wondering if it would work.
That booster app, have you tried uninstalling it with adb?
Gregbmil1 said:
I'm not known for giving good advice but if I was in your situation I would try to install the lastest version of Magisk and hope for the best. Knowing how I am it would be driving me nuts wondering if it would work.
That booster app, have you tried uninstalling it with adb?
Click to expand...
Click to collapse
Hey, thanks for your reply. I am really eager to root it. I almost just went for it. However, then I thought about it. If something went wrong I would not have any way to recover the phone since there is not a system image available yet. I have not given adb removal a try yet as I figure it would just be easier to go with rooting since it will help me with everything I am trying to achieve. If I cannot root it then I will go the adb route. Hopefully someone will come along and help me out. Fingers crossed
Let us know what you end up doing. Are you expected to send the phone back after the beta testing? If you are responsible for any damages done to it, I would not try it.
You could send it back bricked and say you have no idea what happened to it, lol. That or say you were "testing" the security of the device and that it passes
bigroc2223 said:
I signed up for a beta test on centernode and received a smartphone to test. The phone is so new that I cannot find any information about it on the internet. The bootloader is unlocked on it. I was reading that you can use magisk to root any device with an unlocked bootloader and system image. Since the phone is so new I cannot find a system image. Is it still possible to root the device? Is there a way I can backup the stock ROM and create a system image that way? Is there something else that will work? I really want to root the device because it came with a preinstalled app which is a system booster type app. It will not let me uninstall it, disable it, or force stop it. When I install my app for my alarm clock it keeps killing the app and the alarm will not go off. I have went through all of the app settings and cannot get it to stop. It also keeps interfering with my VPN. I would also like to root th device to remove some of the bloatware and to have access to the HOST file. Could someone please help me this? I would greatly appreciate it. Thanks guys!
Click to expand...
Click to collapse
If you have the firmware then you're in luck (especially if it's the full one)
Download a program for windows called "Payload Dumper"
Open the zip (firmware) and copy out the payload.bin file.
Copy this to the input folder from payload dumper.
Run the exe for payload dumper
It'll output a bunch of files to output folder
You'll see a boot.img file this is essentially the file you use to boot your phone and also where magisk would reside too.
Copy this to your phone.
Install the latest Magisk then open it
Click install and then patch a file, navigate to the boot.img
Click the boot.img and it'll output a file to "SDcard\Downloads" usually called magisk_patched.img
Copy this to your fastboot folder on your computer and open a CMD / Powershell command to that location.
Then boot to fastboot / bootloader mode
Then type:
fastboot boot "name of patched boot.img"
eg:
fastboot boot magisk_patched.img
The phone will boot
From this point you are rooted but you need to make it permanent as you haven't flashed the boot sector at this point, you're only booting an image, if you were to reboot you'd lose it.
Open Magisk again then click install again.
Now instead of just seeing patch a file you'll see "Install Directly" + "Install after an OTA"
Click Install directly, allow it to finish, then reboot.
You're now fully rooted.
Heres my guides for the oneplus 8 pro, don't use the images there as they're for the 8 pro, you also can download payload dumper from there too.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
IT's easy.
Good luck
dladz said:
If you have the firmware then you're in luck (especially if it's the full one)
Download a program for windows called "Payload Dumper"
Open the zip (firmware) and copy out the payload.bin file.
Copy this to the input folder from payload dumper.
Run the exe for payload dumper
It'll output a bunch of files to output folder
You'll see a boot.img file this is essentially the file you use to boot your phone and also where magisk would reside too.
Copy this to your phone.
Install the latest Magisk then open it
Click install and then patch a file, navigate to the boot.img
Click the boot.img and it'll output a file to "SDcard\Downloads" usually called magisk_patched.img
Copy this to your fastboot folder on your computer and open a CMD / Powershell command to that location.
Then boot to fastboot / bootloader mode
Then type:
fastboot boot "name of patched boot.img"
eg:
fastboot boot magisk_patched.img
The phone will boot
From this point you are rooted but you need to make it permanent as you haven't flashed the boot sector at this point, you're only booting an image, if you were to reboot you'd lose it.
Open Magisk again then click install again.
Now instead of just seeing patch a file you'll see "Install Directly" + "Install after an OTA"
Click Install directly, allow it to finish, then reboot.
You're now fully rooted.
Heres my guides for the oneplus 8 pro, don't use the images there as they're for the 8 pro, you also can download payload dumper from there too.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
IT's easy.
Good luck
Click to expand...
Click to collapse
So it sounds like since this is a beta device and I cannot find a firmware image in out of luck?
I guess the only other option I have is finding someone who can port twrp for my device. Then I can just root via TWRP. However, from what I have read that might not even be an option as Android 11 mostly has to be rooted the hard way which you have gave instructions on above.
Can anyone think of anything else I can try?
bigroc2223 said:
So it sounds like since this is a beta device and I cannot find a firmware image in out of luck?
I guess the only other option I have is finding someone who can port twrp for my device. Then I can just root via TWRP. However, from what I have read that might not even be an option as Android 11 mostly has to be rooted the hard way which you have gave instructions on above.
Can anyone think of anything else I can try?
Click to expand...
Click to collapse
You can also extract the boot image... Can't remember the commands for this via ADB, Google ADB extract boot.img
dladz said:
You can also extract the boot image... Can't remember the commands for this via ADB, Google ADB extract boot.img
Click to expand...
Click to collapse
Awesome this is exactly what I was trying to figure out in my original post. Since there is no stock firmware available yet (beta unit) what is the best way to backup the device so I do not get a brick in the process? Thanks again for your help.
bigroc2223 said:
Awesome this is exactly what I was trying to figure out in my original post. Since there is no stock firmware available yet (beta unit) what is the best way to backup the device so I do not get a brick in the process? Thanks again for your help.
Click to expand...
Click to collapse
An actual back up? Probably twrp if available.
If not then you'd need a recovery method.
So providing you have a recovery solution you should be fine.
dladz said:
An actual back up? Probably twrp if available.
If not then you'd need a recovery method.
So providing you have a recovery solution you should be fine.
Click to expand...
Click to collapse
Ahhh okay since it is a beta device no one has made TWRP for it yet. What do you think the risk is of manually pulling the boot img, patching, and flashing is? If I can get that to work I will try to port twrp to the device. Thanks again for the help.
bigroc2223 said:
Ahhh okay since it is a beta device no one has made TWRP for it yet. What do you think the risk is of manually pulling the boot img, patching, and flashing is? If I can get that to work I will try to port twrp to the device. Thanks again for the help.
Click to expand...
Click to collapse
You're very welcome.
Chances of it not booting after doing that? Absolutely zero.
It's a copy not a cut, so you're fine.
The only problem you may encounter is the ability to access the device on that level.
Just turn on usb debugging and make sure ADB works as it should be checking on ADB devices.
Then go ahead with the pull.
You'll be fine.
Also once you have the boot.img if the patched one doesn't work then just reboot and you're back to normal.
I would advise against flashing it, just boot it.
dladz said:
Just turn on usb debugging and make sure ADB works as it should be checking on ADB devices.
Then go ahead with the pull.
You'll be fine.
Also once you have the boot.img if the patched one doesn't work then just reboot and you're back to normal.
Click to expand...
Click to collapse
You can't simply run
Code:
adb devices
adb pull boot.img > C:\boot.img
to clone phone's boot.img to PC.
The correct way is described here
Extract Boot.img Directly from Device Without Downloading Firmware
In this tutorial, we will show you the steps to extract the boot.img file directly from your device without downloading the firmware.
www.droidwin.com
jwoegerbauer said:
You can't simply run
Code:
adb devices
adb pull boot.img > C:\boot.img
to clone phone's boot.img to PC.
The correct way is described here
Extract Boot.img Directly from Device Without Downloading Firmware
In this tutorial, we will show you the steps to extract the boot.img file directly from your device without downloading the firmware.
www.droidwin.com
Click to expand...
Click to collapse
I did not say that you could?? I said pull it.
Before that I said look it up / Google it
Thanks for your help guys I appreciate it greatly. I am going to give this a try today. I will report back and let you guys know how it goes.
One last question. Since this beta unit I got is a tracfone branded unit with an unlocked bootloader is it possible that they could push a firmware which will lock the bootloader at some point? If so is there any way to prevent that from happening? Thanks again for all your help.
bigroc2223 said:
Thanks for your help guys I appreciate it greatly. I am going to give this a try today. I will report back and let you guys know how it goes.
One last question. Since this beta unit I got is a tracfone branded unit with an unlocked bootloader is it possible that they could push a firmware which will lock the bootloader at some point? If so is there any way to prevent that from happening? Thanks again for all your help.
Click to expand...
Click to collapse
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
dladz said:
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
Click to expand...
Click to collapse
It's a phone for testing which I am allowed to keep.
dladz said:
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
Click to expand...
Click to collapse
It is a phone for testing which I am allowed to keep. Specs are Snapdragon 750g, Adreno 619, and 4gb of ram. Not too shabby for a free phone. It is a lot snappier than the moto e6 I was previously using.
dladz said:
I did not say that you could?? I said pull it.
Before that I said look it up / Google it
Click to expand...
Click to collapse
This method requires TWRP. So this will not work.
bigroc2223 said:
Nvm
Click to expand...
Click to collapse
dladz said:
Again!!!? What's your problem??
You're just trying to (for whatever reason) prove me wrong and yet again I wasn't being descriptive of an ADB pull!!!
You're pulling the boot.img off the device by whatever means.
To be clear for the final time, I'm not stating to use twrp, a script or anything else I said look it up / Google it!
Now if you've helped the chap then that's great, looking at what I said and attempting to put me straight when you clearly don't have to, is no help to you or the chap needing help it's just making you look like you're on a power trip.
Click to expand...
Click to collapse
I'm just trying to get some help here guys that's it. I appreciate everyone's efforts and opinions. Let's all try to work together and try to find a solution peacefully please.
So far I have adb installed and working. I have tried to use the commands I was able to locate via google. So far nothing works. I have also tried uninstalling some programs using adb which did not work. I think I am going to have to find someone who could port twrp for me
bigroc2223 said:
I'm just trying to get some help here guys that's it. I appreciate everyone's efforts and opinions. Let's all try to work together and try to find a solution peacefully please.
So far I have adb installed and working. I have tried to use the commands I was able to locate via google. So far nothing works. I have also tried uninstalling some programs using adb which did not work. I think I am going to have to find someone who could port twrp for me
Click to expand...
Click to collapse
Sorry I got the wrong end of the stick, I thought you was a second person posting..
Forget what I said