hey,
today i got notification about a new OTA update (H85010D)
but my phone is on TWRP Recovery so it's not possible to intall OTA.
is there any way to install this OTA update manually? or can i find it as zippable file?
The KDZ needs to be downloaded, extracted and made flashable in TWRP for that to work... Otherwise, you have to flash it with the LG Flash tool or LGUP.
I recommend waiting for autoprime to create a flashable h850 zip if you're not in a hurry.
karendar said:
The KDZ needs to be downloaded, extracted and made flashable in TWRP for that to work... Otherwise, you have to flash it with the LG Flash tool or LGUP.
I recommend waiting for autoprime to create a flashable h850 zip if you're not in a hurry.
Click to expand...
Click to collapse
Not necessarily. OTA could be flashed with TWRP, if we knew where the OTA zip is.
fonix232 said:
Not necessarily. OTA could be flashed with TWRP, if we knew where the OTA zip is.
Click to expand...
Click to collapse
That too, but then again, it's much cleaner to have a TWRP flashable zip. As to get the OTA flashed, you need to have an unrooted, unmodified system partition. The OTA does a diff on files and if you have any modifications, might just fail or cause other nonsense on your phone.
I personally just LGUP'ed my phone to V10d... Battery life is surprisingly better.
karendar said:
That too, but then again, it's much cleaner to have a TWRP flashable zip. As to get the OTA flashed, you need to have an unrooted, unmodified system partition. The OTA does a diff on files and if you have any modifications, might just fail or cause other nonsense on your phone.
I personally just LGUP'ed my phone to V10d... Battery life is surprisingly better.
Click to expand...
Click to collapse
Rooting is now systemless Except if you upgrade from a ROM that does /system modifications.
fonix232 said:
Rooting is now systemless Except if you upgrade from a ROM that does /system modifications.
Click to expand...
Click to collapse
Let me rephrase that to avoid further confusion:
You need an unmodified boot image (Which is modified by a SuperSU flash), an unmodified system partition (Removing system apps and files) and depending on the update, an unmodified recovery partition (Flashing TWRP). In other words, if you modify from stock ANYTHING, OTA has a chance of failing, even if flashed in TWRP... The OTA simply patches existing files and partitions. So it's really a waste of time to bother with the OTA version unless you're full stock. You're better off getting a TWRP flashable zip, it's much less of a headache.
karendar said:
Let me rephrase that to avoid further confusion:
You need an unmodified boot image (Which is modified by a SuperSU flash),
Click to expand...
Click to collapse
False. Boot.img is overwritten without checking previous version.
karendar said:
an unmodified system partition (Removing system apps and files) and depending on the update, an unmodified recovery partition (Flashing TWRP).
Click to expand...
Click to collapse
This is correct. However... Systemless SU and Xposed do not modify the system partition, thus making a pure OTA possible, through stock recovery.
karendar said:
In other words, if you modify from stock ANYTHING, OTA has a chance of failing, even if flashed in TWRP... The OTA simply patches existing files and partitions. So it's really a waste of time to bother with the OTA version unless you're full stock. You're better off getting a TWRP flashable zip, it's much less of a headache.
Click to expand...
Click to collapse
A TWRP flashable ZIP will result the same as an OTA - patches the system partition (without removing any additional files, e.g. new ringtones, apps, etc.), overwrites boot (and possibly recovery). If you root with the systemless option, you'll have to flash the root zip again, otherwise you should be fine.
I unlocked the bootloader, i'm in v20b, is possible have root?
danielg90 said:
I unlocked the bootloader, i'm in v20b, is possible have root?
Click to expand...
Click to collapse
850? Then yes.
Sent from my LGE LG-H830 using XDA Labs
Nick216ohio said:
850? Then yes.
Sent from my LGE LG-H830 using XDA Labs
Click to expand...
Click to collapse
How?
Related
This is a stock boot.img I use where I edited ramdisk and sepolicy for regular root. I also changed force encryption to encryptable and permissive Enforcing
I will continue to post new boot.img each update here.
Downloads
NBF26f big thanks for the update was done by @googy_anas
https://drive.google.com/file/d/0B4yuQy7Zn1WSdTFCMEtRbXpSREE/view?usp=drivesdk
NBD91K
https://www.androidfilehost.com/?fid=529152257862678470
NRD90U
https://drive.google.com/file/d/0B6DDdWOgUhVVMFpGTFlTQWVQOW8/view
@holla420 good looks on doing boot.img again.
NPD90G
https://www.androidfilehost.com/?fid=24591023225178833
big shout out to my homie @holla420 for knocking out this boot.img for everyone.
NPD56N
https://www.androidfilehost.com/?fid=24572369242686570
big shout out to my homie @holla420 for knocking out this boot.img for everyone
NPD35K
https://drive.google.com/file/d/0B4yuQy7Zn1WSQmdfZ3dNMW02Z3c/view?usp=drivesdk
Decrypted boot.IMG and no DM check for NPC91K
https://drive.google.com/file/d/0B4yuQy7Zn1WSVVJSbWpGaU1sTlU/view?usp=drivesdk
Decrypted boot.IMG for Android N build NPC56W
https://drive.google.com/file/d/0B4yuQy7Zn1WSZm11VE1KZmx3RG8/view?usp=sharing
Decrypted boot.IMG for Android N build inital release
https://drive.google.com/file/d/0B4VEhClrJEWpekpneFdUWkhBX1E/view
Big thanks to my good friend and co-dev @toknitup420 don't forget to thank him you see him around
works perfect. Good looks @Tigerstown.
Sent from my Nexus 6P using Tapatalk
Tigerstown said:
This is a stock boot.img I use where I edited ramdisk and sepolicy for regular root. I also changed force encryption to encryptable.
Download https://drive.google.com/file/d/0B4yuQy7Zn1WSTnE4bmxNZXRMdGs/view?usp=docslist_api
Click to expand...
Click to collapse
Eli5, What's the point of a normal root when you can just flash the systemless root and be done with it?
floepie said:
Eli5, What's the point of a normal root when you can just flash the systemless root and be done with it?
Click to expand...
Click to collapse
what's the point of systemless root is what you should be asking yourself
Tigerstown said:
what's the point of systemless root is what you should be asking yourself
Click to expand...
Click to collapse
Because you don't have to rely on the generosity of someone modifying the boot image to accommodate the older method, thereby requiring only 1 recovery flash?
floepie said:
Because you don't have to rely on the generosity of someone modifying the boot image to accommodate the older method, thereby requiring only 1 recovery flash?
Click to expand...
Click to collapse
Why are you even in this thread if you have no interest in using traditional root. Stop trolling and leave the thread. If you don't want it, then don't use it. It's been posted for users that want traditional root and don't know how to mod their own boot.img. Also you're incorrect about the amount of flashing in recovery. You still only need to flash one zip. The SuperSU zip. The boot image gets flashed in fastboot. Soooooooo when you're updating to newest software from Google, you simply use this modded boot.img instead of the one from Google. So technically there are absolutely no extra steps taken in order to use this boot.img.
Sent from my Nexus 6P using Tapatalk
Huh? No, really, I think I'm too old to be "trolling". Just curious to know if there are any potential advantages of the traditional method - not from a selfish perspective, but more out a, well, curiosity. Can we just keep this to the level of a civil "discussion"?
Is this still Enforcing? Is it possible to get a stock or close to stock kernel that is Permissive for a project I'm working on? I just need a boot.img. Thanks!
toknitup420 said:
Why are you even in this thread if you have no interest in using traditional root. Stop trolling and leave the thread. If you don't want it, then don't use it. It's been posted for users that want traditional root and don't know how to mod their own boot.img. Also you're incorrect about the amount of flashing in recovery. You still only need to flash one zip. The SuperSU zip. The boot image gets flashed in fastboot. Soooooooo when you're updating to newest software from Google, you simply use this modded boot.img instead of the one from Google. So technically there are absolutely no extra steps taken in order to use this boot.img.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I agree and thank you. as I am traditional root user. thank you for the boot img
Sent from my Nexus 9
floepie said:
Eli5, What's the point of a normal root when you can just flash the systemless root and be done with it?
Click to expand...
Click to collapse
Why do you guys attack the above person for asking "explain like I am 5, why does anyone want this?"
Tigerstown said:
what's the point of systemless root is what you should be asking yourself
Click to expand...
Click to collapse
toknitup420 said:
Why are you even in this thread if you have no interest in using traditional root. Stop trolling and leave the thread. If you don't want it, then don't use it. It's been posted for users that want traditional root and don't know how to mod their own boot.img. Also you're incorrect about the amount of flashing in recovery. You still only need to flash one zip. The SuperSU zip. The boot image gets flashed in fastboot. Soooooooo when you're updating to newest software from Google, you simply use this modded boot.img instead of the one from Google. So technically there are absolutely no extra steps taken in order to use this boot.img.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Would it have been better if the question were phrased: "Why do you need a separate modified boot.img, when you can force system root using any SuperSU above 2.65? It will still patch the boot.img and disable "forceencrypt"?
So, I'll ask....why do you need a modified boot.img and SuperSU, if SuperSU 2.6x will *automatically modify the boot.img for you and can be installed as system or system-less via terminal commands? Is it because you are using the stock rom and SuperSU will not install as system root due to lack of space in /system?
Edit: *automatically modify boot.img when installing as system-less, OR can be forced to install as system root via terminal commands?
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Why do you guys attack the above person for asking "explain like I am 5, why does anyone want this?"
Would it have been better if the question were phrased: "Why do you need a separate modified boot.img, when you can force system root using any SuperSU above 2.65? It will still patch the boot.img and disable "forceencrypt"?
So, I'll ask....why do you need a modified boot.img and SuperSU, if SuperSU 2.6x will *automatically modify the boot.img for you and can be installed as system or system-less via terminal commands? Is it because you are using the stock rom and SuperSU will not install as system root due to lack of space in /system?
Edit: *automatically modify boot.img when installing as system-less, OR can be forced to install as system root via terminal commands?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Why use the terminal cmd? I make this for myself. I posted for people that want it. If you don't want it or need it that is cool. I flash this when flashing factory imgs and I can reboot still decrypted then I boot to twrp flash SuperSU zip and I'm done. I'm not a fan of systemless root. Do you know why it was even created??
guitardedhero said:
Is this still Enforcing? Is it possible to get a stock or close to stock kernel that is Permissive for a project I'm working on? I just need a boot.img. Thanks!
Click to expand...
Click to collapse
Yes it's still Enforcing
floepie said:
Because you don't have to rely on the generosity of someone modifying the boot image to accommodate the older method, thereby requiring only 1 recovery flash?
Click to expand...
Click to collapse
This boot.img isn't flashed in recovery so still one flash. This is fastboot when your updating factory imgs.
freddienuxx said:
I agree and thank you. as I am traditional root user. thank you for the boot img
Sent from my Nexus 9
Click to expand...
Click to collapse
no problem I do it for every update. I just decide to start posting them for people like yourself. ??
Hi,
Should I be using this file to update from MMB29P to MMB29Q and still maintain root?
I must flash the file through TWRP?
Touchmetallic said:
Hi,
Should I be using this file to update from MMB29P to MMB29Q and still maintain root?
I must flash the file through TWRP?
Click to expand...
Click to collapse
you can use this as boot.img to update yes. But keep root no. You just need to flash factory imgs with this boot.img then boot up and boot to twrp flash SuperSU 2.67 and you will be updated with regular root.
Flash this boot.img thru fastboot just like you do factory imgs not via recovery.
Tigerstown said:
you can use this as boot.img to update yes. But keep root no. You just need to flash factory imgs with this boot.img then boot up and boot to twrp flash SuperSU 2.67 and you will be updated with regular root.
Flash this boot.img thru fastboot just like you do factory imgs not via recovery.
Click to expand...
Click to collapse
Thanks for your reply.
Sorry if this is a redundant question as I'm not an expert, but is there an easy way to update without losing root?
Touchmetallic said:
Thanks for your reply.
Sorry if this is a redundant question as I'm not an expert, but is there an easy way to update without losing root?
Click to expand...
Click to collapse
No need to be sorry it's all good... Unfortunately no. You can just flash SuperSU zip in twrp after updating to new factory imgs with this modified boot.img and your 100% rooted again.
Touchmetallic said:
Thanks for your reply.
Sorry if this is a redundant question as I'm not an expert, but is there an easy way to update without losing root?
Click to expand...
Click to collapse
I recommend not flashing the userdata.img as that will wipe your internal storage sense it's still 6.0.+ FYI but that's up to you and don't flash the recovery.img either in factory imgs cause that will replace your twrp with stock recovery
Tigerstown said:
Why use the terminal cmd? I make this for myself. I posted for people that want it. If you don't want it or need it that is cool. I flash this when flashing factory imgs and I can reboot still decrypted then I boot to twrp flash SuperSU zip and I'm done. I'm not a fan of systemless root. Do you know why it was even created??
Click to expand...
Click to collapse
Ahh I see. That makes sense given that you are decrypted. Appreciate that.
Having followed SuperSU threads since late November, seems like it was created to make accepting OTAs easier. That, or to work around the limits of Marshmallow and /system rom space. If not that, then no I don't.
Sent from my Nexus 5X using Tapatalk
After taking root I'll still be able to update my phone using OTA? If so, the update will remove the root?
As updates OTA behave in relation to Xposed? Is everything going to work?
Sorry for the English, I used Google translator.
kubixmaster3009 said:
After taking root I'll still be able to update my phone using OTA? If so, the update will remove the root?
As updates OTA behave in relation to Xposed? Is everything going to work?
Sorry for the English, I used Google translator.
Click to expand...
Click to collapse
Unfortunately you can't update via OTA if your device is rooted.
To install OTA,
recover the ROM backup ( that you ''hopefully" made before rooting using TWRP ) from TWRP and then, install the OTA.
Edit: Or , (if you are patient enough to download the full ROM) you can dirty flash the full ROM and then install OTA.
When you do this, custom recovery (eg., twrp) will be replaced by stock oneplus recovery . Hence, you should again flash the custom recovery img through adb.
What if we extract the update file and only take the files that will not effect the recovery (the really updated files), make them into a flashable zip and overwrite the current system files?
Just dirty flash the full ROM, then the OTA zip(s) and after that root it again, flash Xposed or whatever you want.
There's no need to restore any backup or reflash recoveries etc.
Firefly1337 said:
Just dirty flash the full ROM, then the OTA zip(s) and after that root it again, flash Xposed or whatever you want.
There's no need to restore any backup or reflash recoveries etc.
Click to expand...
Click to collapse
You are right about dirty flashing the full ROM zip.
But, the recovery will be replaced by stock oneplus recovery when you install OTA update as of my experience.
sankarshan said:
You are right about dirty flashing the full ROM zip.
But, the recovery will be replaced by stock oneplus recovery when you install OTA update as of my experience.
Click to expand...
Click to collapse
Why should it be?
I can confirm from personal experience that this won't happen.
//Edit: Do you actually mean 'install' OTAs with the official updater in android itself? If so, then I don't know.
But by flashing the OTA zip (in recovery) it won't replace your recovery.
Firefly1337 said:
//Edit: Do you actually mean 'install' OTAs with the official updater in android itself? If so, then I don't know.
But by flashing the OTA zip (in recovery) it won't replace your recovery.
Click to expand...
Click to collapse
1.Yeah, I meant updating via "official updater".
2. That's one of the reasons why they(manually flashable OTA zips) are made. aren't they?
@sankarshan Yes you're right. I thought you meant flashing them as zip because I specifically spoke of flashing the OTA zips
winesh said:
What if we extract the update file and only take the files that will not effect the recovery (the really updated files), make them into a flashable zip and overwrite the current system files?
Click to expand...
Click to collapse
That's a great idea @winesh I also wonder if it is possible.
winesh said:
That's a great idea @winesh I also wonder if it is possible.
Click to expand...
Click to collapse
Are you talking to yourself? LOL
A reddit user captured his link to the DP
Here is the link
https://android.googleapis.com/pack.../f9cb176ee75399a48e927d9f1bd6aeb6a643272c.zip
Credit: https://m.reddit.com/r/Nexus6P/comments/5edfam/captured_my_ota_url/?compact=true
Flash guide: *should* work
1. Boot twrp on DP1
2. flash SU of choice
3. reboot
4. install FlashFire from play store
5. Select "Flash firmware package"
6. Select the zip
7. Flash it!
**** A FEW DISCLAIMERS
**** TWRP seems to be based on 6.0.1 and the OTA can only be flashed on 7.1.1
**** In this case twrp will NOT flash this OTA file
**** FlashFire IS REQUIRED
**** I am not google. Yes I am sorry that force encrypt wiped your data or you got stuck in
**** a boot loop because you flashed it incorrectly BUT I am NOT google, I am NOT even
**** the person who captured the link for the ota ALL I DID WAS SHARE IT
**** If your data partition got wiped, you got stuck in a boot loop, or the guide didn't work
**** chances are you did something wrong
**** if you would like support but Google up in the DMs
**** I am happy to help just know I won't troubleshoot what you screwed up
Would we get a full OTA as well?
gqukyo said:
Would we get a full OTA as well?
Click to expand...
Click to collapse
If by full OTA you mean full ROM zip, here it is.
WelcomeToTheSkye said:
A reddit user captured his link to the DP
Here is the link
https://android.googleapis.com/pack.../f9cb176ee75399a48e927d9f1bd6aeb6a643272c.zip
Credit: https://m.reddit.com/r/Nexus6P/comments/5edfam/captured_my_ota_url/?compact=true
Click to expand...
Click to collapse
Sorry for being a noob but do I flash the zip file through TWRP or is there some other way? I am rooted with custom recovery on DP1.
Thanks
marmeak7 said:
Sorry for being a noob but do I flash the zip file through TWRP or is there some other way? I am rooted with custom recovery on DP1.
Thanks
Click to expand...
Click to collapse
If you're rooted, use flash fire from play. It restores twrp and root after updating. Haven't used any other method. No problems. Best app ever.
Just updated. Sound louder, November security patch and overall smoother scrolling.
No regrets getting the 6P. Amazing phone.?
It work fined at my Nexus 6p. All the rooted apps working fine. Thank you very much for your sharing. Appreciated it.
Just curius, has anyone of you guys unencrypted?
I installed it with flashfire but I'm still at DP1... Am I doing something wrong?
I installed it as flash zip or ota but nothing still got the message to update.
Is it because I have installed custom kernel?
Can't flash it in TWRP --> error
edit: I got E3001: the build fingerprint doesn't match. How can I fix this?
I succesfully flashed using Flashfire.
First thing I noticed is the many (repeating) superuser notifications I get for apps getting root during boot.
DRD70 said:
I installed it with flashfire but I'm still at DP1... Am I doing something wrong?
I installed it as flash zip or ota but nothing still got the message to update.
Is it because I have installed custom kernel?
Click to expand...
Click to collapse
the same for me... I only have twrp and have modified system... maybe is because of that... but I tought that would not be a problem... guess I'm going the twrp way
hmm, now I get it... this is not a full ota file.
Will I be able to flash it via TWRP like I did with the full OTA file from DP1 ??
^You need the full ota not this type of ota...
So this is the update from DP1 to DP2, correct? Is there any other way to install it besides with Flashfire? I've always installed from my PC, so is there any way to sideload it or install the zip through TWRP?
DRD70 said:
I installed it with flashfire but I'm still at DP1... Am I doing something wrong?
I installed it as flash zip or ota but nothing still got the message to update.
Is it because I have installed custom kernel?
Click to expand...
Click to collapse
You must be on dp1 and select flash firmware package not flash zip
ahmd gomaa said:
You must be on dp1 and select flash firmware package not flash zip
Click to expand...
Click to collapse
I was on dp1 and my first selection was firmware package and nothing happened. So i tried the other with the same outcome.
I finally revert it to stock and got ota update the dp2 since I'm a beta tester and root it again.
Rooted with TWRP on NPF10C
So I'm rooted and have TWRP installed, how can I update to DP2 ?
aakash dabrase said:
So I'm rooted and have TWRP installed, how can I update to DP2 ?
Click to expand...
Click to collapse
Install FlashFire from the play store and select firmware
swa100 said:
Can't flash it in TWRP --> error
edit: I got E3001: the build fingerprint doesn't match. How can I fix this?
Click to expand...
Click to collapse
Noted it in the op
Twrp is based on 6.0.1 afaik just use FlashFire
WelcomeToTheSkye said:
Install FlashFire from the play store and select firmware
Click to expand...
Click to collapse
Here's what I did:
1. Downloaded the OTA (137 MB) on pc.
2. Copied it to phone.
3. Selected Flash OTA in flashfire and selected the zip.
4. Flashfire failed to do it.
Should I use flash firmware option instead of flash OTA?
Also there are further options to select like recovery etc. What about them?
aakash dabrase said:
Here's what I did:
1. Downloaded the OTA (137 MB) on pc.
2. Copied it to phone.
3. Selected Flash OTA in flashfire and selected the zip.
4. Flashfire failed to do it.
Should I use flash firmware option instead of flash OTA?
Also there are further options to select like recovery etc. What about them?
Click to expand...
Click to collapse
Yep select firmware (it says that in op) select what you would like to keep
I just received the OTA update from 7.1.1 DP2 to MNF26F.
Here is the OTA url to download:
https://android.googleapis.com/pack.../2c6f100d0f9ef8ccee10d661b7454adb7161aa0e.zip
You can sideload it into your device and you will be on the official 7.1.1 release.
Just got it too. Only 27 megabytes.
Just download it... Where the downloaded OTA file located in our file system?
deani77 said:
Just download it... Where the downloaded OTA file located in our file system?
Click to expand...
Click to collapse
/data/data/com.google.android.gms/app_download/
If rooted on dp2 I can just download and install through TWRP, no?
I installed this and I got a boot loop, so careful. First time ever with an issue and I didn't bring my cable
thedead69 said:
I installed this and I got a boot loop, so careful. First time ever with an issue and I didn't bring my cable
Click to expand...
Click to collapse
Any more info? What version were you on before? Rooted? Used TWRP? What version of TWRP?
RaceFaceXC said:
If rooted on dp2 I can just download and install through TWRP, no?
Click to expand...
Click to collapse
No. ota only installs on stock images.
http://forum.xda-developers.com/showthread.php?p=62924118
Points 12/ and 13/
RaceFaceXC said:
Any more info? What version were you on before? Rooted? Used TWRP? What version of TWRP?
Click to expand...
Click to collapse
Rooted with SuperSU on DP2. Using flashfire
I got this OTA this afternoon. Stock DP2 on Verizon.
rchtk said:
No. ota only installs on stock images.
http://forum.xda-developers.com/showthread.php?p=62924118
Points 12/ and 13/
Click to expand...
Click to collapse
Thank.
I think I knew this at some point. Wasn't sure so that's why I asked.
thedead69 said:
Rooted with SuperSU on DP2. Using flashfire
Click to expand...
Click to collapse
Can you or someone help me??
Yesterday I received the notification. Download the file from here, as I am rooted, twrp and custome kernel.
I tried to flash this via flashfire, but after phone reboots, nothing happens... am I doing something wrong??
I open flashfire, choose Flash ZIP or OTA, choose the file, on the options I don't change anything (it only has Restore boot and recovery images ticked) and then on the main screen I press Flash. Then phone reboots and nothing happens, it enters again on android.
Someone??
onesolo said:
Can you or someone help me??
Yesterday I received the notification. Download the file from here, as I am rooted, twrp and custome kernel.
I tried to flash this via flashfire, but after phone reboots, nothing happens... am I doing something wrong??
I open flashfire, choose Flash ZIP or OTA, choose the file, on the options I don't change anything (it only has Restore boot and recovery images ticked) and then on the main screen I press Flash. Then phone reboots and nothing happens, it enters again on android.
Someone??
Click to expand...
Click to collapse
Can you enter bootloader or recovery with power/vol dn? If so, try sideloading a stock image? Or, if you can get into recovery restore with a nandroid backup?
Link ota for NEXUS 5X PLEASE
Link ota for NEXUS 5X PLEASE
hanibioud said:
Link ota for NEXUS 5X PLEASE
Click to expand...
Click to collapse
Wrong forum. This is for the Nexus 6P.
RaceFaceXC said:
Can you enter bootloader or recovery with power/vol dn? If so, try sideloading a stock image? Or, if you can get into recovery restore with a nandroid backup?
Click to expand...
Click to collapse
I didn't even try, cause I can enter on twrp fine. As I said, I have twrp and root. My sys is obviously modified. I'm not even trying to sideloaded over bootloader cause it wont work. The same thing on TWRP. I think that sideloading on TWRP only works with full OTAs and not with this one, that is an incremental OTA file, unless I'm completely wrong (I wish).
Anyone's got a changelog for those 26 MB of 'system stability and performance' ?
onesolo said:
Can you or someone help me?? Someone??
Click to expand...
Click to collapse
Download the full Google image- not OTA and flash that. If you can still boot the OS, use FF to flash boot, system, vendor. If you cannot boot OS, use ADB Fastboot to flash those partitions. Yes, I used the full image to go from DP2 to Public Release using FF. If more details are needed, check out the FF thread.
v12xke said:
Download the full Google image- not OTA and flash that. If you can still boot the OS, use FF to flash boot, system, vendor. If you cannot boot OS, use ADB Fastboot to flash those partitions. Yes, I used the full image to go from DP2 to Public Release using FF. If more details are needed, check out the FF thread.
Click to expand...
Click to collapse
yep, that is what I'm going to do... I guess not even FF can flash an mere incremental OTA (only full OTAs). bad luck
onesolo said:
yep, that is what I'm going to do... I guess not even FF can flash an mere incremental OTA (only full OTAs). bad luck
Click to expand...
Click to collapse
I didn't think flashing a ota over a rooted os, let alone a highly modified os/kernel/etc was a good idea with any utility.
I'm currently sitting at TWRP and was going to restore my backup... it's gone. I was going to reboot to OS... TWRP warns me I have no OS installed.
In my tired state trying to solve an unrelated problem I must have killed my backup a few hours ago without noticing and then decided to use TWRP to format my phone so I could restore my backup... that I previously killed.
What can I do from this state? My brain is fried from hours of trying various troubleshooting threads across the internet and I'm just at a loss how to install the OS again without bricking and I don't want to make a mistake.
Appreciate the help. I do have US998820e_02_0910.kdz downloaded on my PC which is the latest KDZ I have downloaded.
teknomedic said:
I'm currently sitting at TWRP and was going to restore my backup... it's gone. I was going to reboot to OS... TWRP warns me I have no OS installed.
In my tired state trying to solve an unrelated problem I must have killed my backup a few hours ago without noticing and then decided to use TWRP to format my phone so I could restore my backup... that I previously killed.
What can I do from this state? My brain is fried from hours of trying various troubleshooting threads across the internet and I'm just at a loss how to install the OS again without bricking and I don't want to make a mistake.
Appreciate the help. I do have US998820e_02_0910.kdz downloaded on my PC which is the latest KDZ I have downloaded.
Click to expand...
Click to collapse
If you did format stuff and yur backup then nothing can help
Mrxyzl said:
If you did format stuff and yur backup then nothing can help
Click to expand...
Click to collapse
I feel that's not correct... could I not use LGUP or copy over a basic backup provided by someone here just to get me back to point where I can get back to stock?
If I plug the phone into the PC I can access the storage.... could I not copy something over and then use the running TWRP to install it?
teknomedic said:
I feel that's not correct... could I not use LGUP or copy over a basic backup provided by someone here just to get me back to point where I can get back to stock?
If I plug the phone into the PC I can access the storage.... could I not copy something over and then use the running TWRP to install it?
Click to expand...
Click to collapse
Oh i mean that your backup is already gone completely no way to get back your backup. And ofcourse you can flash a new rom anew
Lol, that's what I thought... But I'm also very tired.
Can I just copy over my KDZ and then install via TWRP? I've always just used backups in the past.
This is a secondary phone that was wiped before anyways so I haven't lost anything important.... The backup was only there to speed things up.
If you are in TWRP, connect to PC and drag over your firmware TWRP flashable zip and Magisk. And whatever else you need, maybe encryption disabler, root check disabler. With Oreo TWRP flashable zip (since you have US998), all you need is the zip file and Magisk.
In TWRP file explorer, find location where you just copied them. Then install them.
US998 20h TWRP flashable zip
https://androidfilehost.com/?fid=1395089523397941723
I've attached Magisk 18 to this post. You can update after you reboot to system. (TWRP 18.X is friendlier with Oreo TWRP-FLASHABLE zips.)
Sent via open market LG US998 V30/V30+
teknomedic said:
Lol, that's what I thought... But I'm also very tired.
Can I just copy over my KDZ and then install via TWRP? I've always just used backups in the past.
This is a secondary phone that was wiped before anyways so I haven't lost anything important.... The backup was only there to speed things up.
Click to expand...
Click to collapse
If your kdz is twrp flashable zip you can copy it over to your phone and flash via recovery.
If the kdz is not twrp flashable you will lose twrp/ root (if available) and will revert to stock recovery.
pvramk said:
If your kdz is twrp flashable zip you can copy it over to your phone and flash via recovery.
If the kdz is not twrp flashable you will lose twrp/ root (if available) and will revert to stock recovery.
Click to expand...
Click to collapse
Yes, TWRP flashable zip is available for his US998 phone.
See post above.
---------- Post added at 08:54 AM ---------- Previous post was at 08:45 AM ----------
teknomedic said:
Lol, that's what I thought... But I'm also very tired.
Can I just copy over my KDZ and then install via TWRP? I've always just used backups in the past.
This is a secondary phone that was wiped before anyways so I haven't lost anything important.... The backup was only there to speed things up.
Click to expand...
Click to collapse
No, don't copy over KDZ. Copy over the TWRP flashable zip version of the KDZ.
See my post above. I give download link to latest Oreo US998 TWRP flashable zip. Also Magisk. I attached that to the post. Flash both, then reboot.
Hey, at least you now have a VERY clean install! This is the technique some people do on purpose to start fresh.
Thank you ChazzMatt... why did I suspect you'd be my hero once again, ha.
ChazzMatt said:
If you are in TWRP, connect to PC and drag over your firmware TWRP flashable zip and Magisk. And whatever else you need, maybe encryption disabler, root check disabler. With Oreo TWRP flashable zip (since you have US998), all you need is the zip file and Magisk.
In TWRP file explorer, find location where you just copied them. Then install them.
US998 20h TWRP flashable zip
https://androidfilehost.com/?fid=1395089523397941723
I've attached Magisk 18 to this post. You can update after you reboot to system.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
LOL... I wasn't opposed to starting fresh... that was my ultimate goal, but I've not been in this exact situation before as I've always kept my backups. Being tired and in a hurry was my downfall this time. I just didn't want to go any further without proper advice as I was worried about bricking and just wanted to double make sure I wouldn't do that on my next attempt to "fix" it alone.
ChazzMatt said:
Yes, TWRP flashable zip is available for his US998 phone.
See post above.
---------- Post added at 08:54 AM ---------- Previous post was at 08:45 AM ----------
No, don't copy over KDZ. Copy over the TWRP flashable zip version of the KDZ.
See my post above. I give download link to latest Oreo US998 TWRP flashable zip. Also Magisk. I attached that to the post. Flash both, then reboot.
Hey, at least you now have a VERY clean install! This is the technique some people do on purpose to start fresh.
Click to expand...
Click to collapse
There are basically several options here.
If you can still boot into fastboot or even TWRP there's nothing to fear. It's really hard to completely brick a phone anyways.
So as suggested either use a flashable kdz (you can even adb sideload it to avoid the copying) or just flash (or sideload) any other ROM. Good luck
teknomedic said:
I feel that's not correct... could I not use LGUP or copy over a basic backup provided by someone here just to get me back to point where I can get back to stock?
Click to expand...
Click to collapse
Connect the phone to the computer, and push a stock TWRP zip to the device and flash it. If you have an ad card port on the PC, then push it to the SD card and put it in the phone.
Sent from my LG-H932 using XDA Labs
NM, saw my man @ChazzMatt using his forum superhero Powers again.
Download any zip of your choice and reboot. Then let Google backup restore your apps and settings.
Running into a new issue... after flashing 20H TWRP and Magisk I rebooted the phone. Android OS did it's first install and I made it to the setup screen... then while I was typing in my wifi password the phone simply shut down (played the shutting down LG logo animation). I turned the phone back on and same results... after loading to the Android setup screen around 1 to 15 seconds later the phone shuts down again. Phone has never done this before.
Any thoughts?
I'm not sure if it matters, but this was originally a US Verizon V30 that I unlocked and rooted following the guides here which "converted" to a US998.
ChazzMatt said:
If you are in TWRP, connect to PC and drag over your firmware TWRP flashable zip and Magisk. And whatever else you need, maybe encryption disabler, root check disabler. With Oreo TWRP flashable zip (since you have US998), all you need is the zip file and Magisk.
In TWRP file explorer, find location where you just copied them. Then install them.
US998 20h TWRP flashable zip
https://androidfilehost.com/?fid=1395089523397941723
I've attached Magisk 18 to this post. You can update after you reboot to system. (TWRP 18.X is friendlier with Oreo TWRP-FLASHABLE zips.)
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
teknomedic said:
Running into a new issue... after flashing 20H TWRP and Magisk I rebooted the phone. Android OS did it's first install and I made it to the setup screen... then while I was typing in my wifi password the phone simply shut down (played the shutting down LG logo animation). I turned the phone back on and same results... after loading to the Android setup screen around 1 to 15 seconds later the phone shuts down again. Phone has never done this before.
Any thoughts?
I'm not sure if it matters, but this was originally a US Verizon V30 that I unlocked and rooted following the guides here which "converted" to a US998.
Click to expand...
Click to collapse
Okay I think I know what the problem is... you may have to flash 20, F, g, H all back-to-back. Then reflash Magisk
Or flash the full 20h KDZ in LGUP , reinstall TWRP and reflash the three root files. Your choice.
The problem is there were so many changes between 20e and 20H with the TWRP flashable zips that you have to flash them all back to back to get the full firmware.
You can stack them in TWRP and flash them all at the same time followed by magisk.
lol... okay... I'll get to downloading, lol. Any recommended custom ROM suggestions? lol
ChazzMatt said:
Okay I think I know what the problem is... you may have to flash 20, F, g, H all back-to-back. Then reflash Magisk
Or flash the full 20h KDZ in LGUP , reinstall TWRP and reflash the three root files. Your choice.
The problem is there were so many changes between 20e and 20H with the TWRP flashable zips that you have to flash them all back to back to get the full firmware.
You can stack them in TWRP and flash them all at the same time followed by magisk.
Click to expand...
Click to collapse
teknomedic said:
lol... okay... I'll get to downloading, lol. Any recommended custom ROM suggestions? lol
Click to expand...
Click to collapse
Sorry, no, I'm still running rooted stock firmware. But others who use custom ROMs may have suggestions for your gaming issue, mentioned in your PM.
Check this out below and see if it helps you any.
https://forum.xda-developers.com/lg-v30/how-to/guide-enable-gps-change-rubber-banding-t3889811
Sent via open market LG US998 V30/V30+
I downloaded and installed ROM 20E from this thread under older zips.... https://forum.xda-developers.com/lg-v30/development/rom-fw-us99820e-twrp-zip-t3868415
still doing the same behavior. First boot Android does setup, then if I let it sit a few seconds it shuts down and reboots, gets to Android and then shuts down again... over and over.
ChazzMatt said:
Sorry, no, I'm still running rooted stock firmware. But others who use custom ROMs may have suggestions for your gaming issue, mentioned in your PM.
Check this out below and see if it helps you any.
https://forum.xda-developers.com/lg-v30/how-to/guide-enable-gps-change-rubber-banding-t3889811
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
Okay, think it's working. Having looked through the ROM maker's thread Magisk v18 is... needed? I previously installed a newer version (v19.2) which can cause this boot loop issue.... I also installed the ROM without any Magisk which still caused the boot loop which is why I wasn't thinking Magisk was the issue.... but after trying 20H with v18 Magisk... no more boot loop. Go figure.
teknomedic said:
I downloaded and installed ROM 20E from this thread under older zips.... https://forum.xda-developers.com/lg-v30/development/rom-fw-us99820e-twrp-zip-t3868415
still doing the same behavior. First boot Android does setup, then if I let it sit a few seconds it shuts down and reboots, gets to Android and then shuts down again... over and over.
Click to expand...
Click to collapse
teknomedic said:
Okay, think it's working. Having looked through the ROM maker's thread Magisk v18 is... needed? I previously installed a newer version (v19.2) which can cause this boot loop issue.... I also installed the ROM without any Magisk which still caused the boot loop which is why I wasn't thinking Magisk was the issue.... but after trying 20H with v18 Magisk... no more boot loop. Go figure.
Click to expand...
Click to collapse
Well, glad you got it working.
But the Magisk thing is why I had specifically attached Magisk 18 to my first post in this thread and said to use it... I even explained why.
I assumed you were using it.