LG G3 VS985
I flashed the kernel and modem to 24B then flashed crdroid 7.1 rom and gapps. Now i'm unable to get pixel launcher as a system app. Haven't attempted to get assitant yet. Any suggestions?
csongcuan said:
LG G3 VS985
I flashed the kernel and modem to 24B then flashed crdroid 7.1 rom and gapps. Now i'm unable to get pixel launcher as a system app. Haven't attempted to get assitant yet. Any suggestions?
Click to expand...
Click to collapse
why did you flash 24b? anyway enabling root access is in the developer options
cory733 said:
why did you flash 24b? anyway enabling root access is in the developer options
Click to expand...
Click to collapse
I got the error "E: Error executing updater binary in zip" when i tried to flash the rom. It was failing the baseband check.
cory733 said:
why did you flash 24b? anyway enabling root access is in the developer options
Click to expand...
Click to collapse
I got the error "E: Error executing updater binary in zip" when i tried to flash the rom. It was failing the baseband check. Anyways thanks!
csongcuan said:
I got the error "E: Error executing updater binary in zip" when i tried to flash the rom. It was failing the baseband check. Anyways thanks!
Click to expand...
Click to collapse
It failed the baseband check because you need the 35b bootstack. Do a search for xdabbeb's 35B bootstack. When yiou have that start over with a total wipe. Then flash in this order:
35b Bootstack
Cr Droid 7.1
Open Gaps ARM 7.1 (of your choice, I used pico)
35b Bootstack
Be sure to flash the 35b Bootstack first AND last. Also use TWRP, and keep using the "add zip" button until you have all 4 zips in queue THEN swipe to flash.
I've been running Cr Droid 7.1 since it was officially released several months ago, and it has worked perfectly. Been my dd since I ran across it, and I love it..
Every feature has worked for me. But I don't have BT ni my ride so I don't know about that. But Wifi, data, Hotspot, BT to other devices, Beam - they've all worked on my G3
Related
All:
I have attempted to flash TWRP via various methods to no avail. I have somehow messed something up so I cannot get the stock recovery to work. I can get into the stock recovery screen, but if I select anything, it says Secure boot error. I am currently on OTA 5.0.1 VS98523C. Any advice on how to proceed? I have looked at KDZ options, but am wondering if I can just get the stock recovery back and let it ride until TWRP is available.
Thanks in advance,
Steven
I'm having trouble with getting TWRP to flash successfully. Using their app and flashify
MrSpohn1 said:
All:
I have attempted to flash TWRP via various methods to no avail. I have somehow messed something up so I cannot get the stock recovery to work. I can get into the stock recovery screen, but if I select anything, it says Secure boot error. I am currently on OTA 5.0.1 VS98523C. Any advice on how to proceed? I have looked at KDZ options, but am wondering if I can just get the stock recovery back and let it ride until TWRP is available.
Thanks in advance,
Steven
Click to expand...
Click to collapse
In theory, you can use the dd comment to put the aboot back, but I would not recommend it as I got my phone hard bricked that way. (so dead that even KDZ does not work)The safest way is KDZ back to 10b, and then stump root. Then:
1. Install TWRP manager from Google Play.
2. From TWRP manager you can choose your phone model and download and install TWRP recovery.
3. Follow the instruction from this link to use TWRP to install the 23c
http://forum.xda-developers.com/verizon-lg-g3/development/rom-rom-base-lp-upgrade-bump-t3051884
Never do OTA if you have rooted your phone. It needs to be completely stock for OTA to work.
/\ What he said.
Twrp doesn't work after lollipop because of the signing requirements in the bootloader.
It needs to be rolled back to 10-12b and then rooted and then you can load twrp. Once you have twrp you can load jasmine or skydragon which are both 5.01.
http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
Thanks! So if I want to use xposed, I should roll back to the other versions of lollipop?
thanks all. I KDZ'd 12b stock rom, rooted, then flashed TWRP through flashify. I then went into recovery and installed the 23c rom. I used skydragon 4.0.0 because I tried to flash Jasmine 7.0 like 8 times. I did not have any of the bottom keys and I could not access my pulldown menu. I could not figure out why this was happening. Skydragon worked for me perfectly. Thanks All.
I got the update for the January Security Update today. I grabbed the .zip's location and the link on Google's servers is:
https://android.googleapis.com/pack...51c56752.signed-angler-MMB29P-from-MMB29M.zip
Hope it helps others!
PSA: this is not flashable over custom ROMs, and cannot be used to install the factory OS from nothing. That's what the factory images are for . This .zip is solely to incrementally update from the December security update to the January one.
Is there an easy way to flash this update.zip without the need of a computer?
tinker_tf said:
Is there an easy way to flash this update.zip without the need of a computer?
Click to expand...
Click to collapse
Unless you have a custom recovery, no. Sorry about that
Updated. Thanks for the link!
I have a rooted, stock ROM and TWRP and with several Xposed Modules, can I flash this?
Also, I don't have the December update, where do I find that?
And lastly, I'm on MDB08L Build, will that work?
For those wanting to use this update and have completely stock system based on MMB29M. Boot into recovery and do an ADB sideload update.zip (rename zip first). Mine updated with no issues.
CipherSec said:
I have a rooted, stock ROM and TWRP and with several Xposed Modules, can I flash this?
Click to expand...
Click to collapse
If you've got all that set up, why not just update using the full factory image (without the wipe)
LeoRex said:
If you've got all that set up, why not just update using the full factory image (without the wipe)
Click to expand...
Click to collapse
I assumed I'll lose all my system modifications (i.e. Xposed Modules and their settings) as well as losing root and TWRP and having to reroot again.
pmedwards25 said:
Unless you have a custom recovery, no. Sorry about that
Click to expand...
Click to collapse
This is exactly the file you need if you don't have custom recovery, don't have root, and have not unlocked bootloader. It is the same file that would eventually come to you OTA. You do however need access to adb and a computer. I don't think this is flashable with a custom recovery.
Thanks..
Thanks for this file bro. dont need to wait.
Alright, feeling like a complete noob, here. I'm on systemless root 2.61 with TWRP. I fastboot flashed the stock boot.img and stock recovery, then tried to sideload the OTA zip. I got a "system contains unexpected contents" error, then installation aborted. Now, with systemless root, I had the understanding that flashing the stock system.img would not be necessary. I was not using systemless root before when I flashed the previous OTA zip. Can anyone spot where I might have gone wrong?
Casyis said:
Alright, feeling like a complete noob, here. I'm on systemless root 2.61 with TWRP. I fastboot flashed the stock boot.img and stock recovery, then tried to sideload the OTA zip. I got a "system contains unexpected contents" error, then installation aborted. Now, with systemless root, I had the understanding that flashing the stock system.img would not be necessary. I was not using systemless root before when I flashed the previous OTA zip. Can anyone spot where I might have gone wrong?
Click to expand...
Click to collapse
Try flash stock system image
Does this update fix the LTE issue?
HRodMusic said:
Does this update fix the LTE issue?
Click to expand...
Click to collapse
No it does not
I got it:
For systemless root, fastboot flash: 1) boot.img; 2) recovery.img; 3) vendor.img; 4) system.img
Boot to recovery and enter sideloade mode. adb sideload [update].zip
Reboot to bootloader. Re-flash TWRP, then in TWRP re-flash kernel (if custom) & superSU.
I used a toolkit to root my 6P. I'm using rooted stock rom. I got an OTA update but it seems I can't update it that way as per all others. So how do I go about installing this on my mobile? Do I need to unroot, flash stock recovery & then flash the new image? Then again I have to root?
fyi: i'm rooted with systemless root and twrp
I tried to take this update per usual as i would if i were unrooted, of course that didn't work totally. i assumed i would just find the update.zip file (i did: /data/data/com.google.android.gms/app.download/update.zip, icywtk) but when i tried to flash that it said the zip was corrupted. i deleted the zip and now it still says my december build is up to date. can't we just flash the update.zip with twrp? i did allow for the system to be modified this time when i booted twrp.
asj0422 said:
fyi: i'm rooted with systemless root and twrp
I tried to take this update per usual as i would if i were unrooted, of course that didn't work totally. i assumed i would just find the update.zip file (i did: /data/data/com.google.android.gms/app.download/update.zip, icywtk) but when i tried to flash that it said the zip was corrupted. i deleted the zip and now it still says my december build is up to date. can't we just flash the update.zip with twrp? i did allow for the system to be modified this time when i booted twrp.
Click to expand...
Click to collapse
I am rooted with twrp. Same deal, twrp reports and error 7 when trying to flash the Jan security update.
kmp14 said:
I am rooted with twrp. Same deal, twrp reports and error 7 when trying to flash the Jan security update.
Click to expand...
Click to collapse
i just tried this again with the same results. it says that the installer is expecting a different build (the one that my settings app shows i'm on) but that i have a build called huawei/mmasomething/ dee_stroyer somethingsomething. (i would post exactly what it says but i've already rebooted into system). I do remember something with "dee_stroyer" when i was rooting but it's not the system...
anyone else have any ideas? i'd like to just update normally and keep my data... and the stock android with root.
EDIT: also, the update won't update my recovery will it? i don't want to have to reflash that. i should be able to update even when i'm away from a computer haha.
Rooted with TWRP. I just tried an ADB sideload and get the same error.
Today I've flashed the recovery with TWRP to install SuperSU.
Is there any possibility of installing the stock recovery to be able to install Android updates normally again without losing all data and SuperSU?
You sir, are not alone with this question. Been eagerly looking for an answer for the same question..
reconman said:
Today I've flashed the recovery with TWRP to install SuperSU.
Is there any possibility of installing the stock recovery to be able to install Android updates normally again without losing all data and SuperSU?
Click to expand...
Click to collapse
Use the search function, it has already been covered.
Anarchist77 said:
Use the search function, it has already been covered.
Click to expand...
Click to collapse
I can't find anything for the G5, only for other phones.
The only option I currently know of is to flash the whole KDZ and then install TWRP and SuperSU again. Is there another way?
As long as the system is modified in any way, the only way to install ota updated is through LGUP because before applying the update there is a system integrity check ran and if that fails you will most likely get into bootlops or worst
Here is what I did to get a 10D rooted system
Thank you @gwolfu.
I successfully followed a guide to rooting my phone using TWRP, DisableForceEncryption (DFE), and Magisk. I now want to flash the latest (stock) ROM and re-apply DFE.
But there seem to be many versions of DFE available, some with/without version numbers, and some with/without the word "treble". And all are anonymous uploads on file-locker sites... :-/
What does "treble" mean? Does the DFE version number correspond to the Magisk version? I couldn't find a DEF v20 anywhere...
Who produces DFE -- is there an official website/source for the latest version(s)?
Cheers
For the latest MIUI Stock Rom you don't need dfe.
ConradB said:
For the latest MIUI Stock Rom you don't need dfe.
Click to expand...
Click to collapse
Thanks. So, I can just just flash the latest ROM in TWRP, and... it won't overwrite TWRP, or lose root access, or cause any boot/encryption problems...?
Presumably I'd need to re-flash Magisk (after flashing the ROM) to retain root access...?
Will the phone be re-encrypted after updating to the latest stock ROM?
esuhl said:
Thanks. So, I can just just flash the latest ROM in TWRP, and... it won't overwrite TWRP, or lose root access, or cause any boot/encryption problems...?
Presumably I'd need to re-flash Magisk (after flashing the ROM) to retain root access...?
Will the phone be re-encrypted after updating to the latest stock ROM?
Click to expand...
Click to collapse
Which version is at the moment installed?
IF by latest stockrom you mean miui 10.3.8 then when i flashed the vendor firmware and didnt flash dfe, i was locked out and I lost all the data!
In Miui Roms firmware and vendor are always integrated. There is IMHO no reason to flash only the vendor.
ConradB said:
Which version is at the moment installed?
Click to expand...
Click to collapse
I have MIUI 10.3.7.0 and want to upgrade to MIUI 10.3.8.0. The file I have downloaded is miui_POCOF1Global_V10.3.8.0.PEJMIXM_b5d72aa3ba_9.0.zip.
YasuHamed said:
IF by latest stockrom you mean miui 10.3.8 then when i flashed the vendor firmware and didnt flash dfe, i was locked out and I lost all the data!
Click to expand...
Click to collapse
Yes -- all the guides I've read say that, having installed a custom recovery to root the device, all subsequent ROM updates need to have DFE (or some similar software) applied in order to prevent a boot-loop. This article gives a lot of information, although most of it goes over my head.
https://miui.blog/any-devices/dm-verity-opt-encrypt-force-encryption-disabler-xiaomi/
ConradB said:
In Miui Roms firmware and vendor are always integrated. There is IMHO no reason to flash only the vendor.
Click to expand...
Click to collapse
What do you mean by "flashing the vendor"...?
esuhl said:
I have MIUI 10.3.7.0 and want to upgrade to MIUI 10.3.8.0. The file I have downloaded is miui_POCOF1Global_V10.3.8.0.PEJMIXM_b5d72aa3ba_9.0.zip.
Yes -- all the guides I've read say that, having installed a custom recovery to root the device, all subsequent ROM updates need to have DFE (or some similar software) applied in order to prevent a boot-loop. This article gives a lot of information, although most of it goes over my head.
https://miui.blog/any-devices/dm-verity-opt-encrypt-force-encryption-disabler-xiaomi/
What do you mean by "flashing the vendor"...?
Click to expand...
Click to collapse
First backup your data
Flash 10.3.8.0 dirty in twrp
wipe cache, dalvik cache in twrp
reboot the device (not rooted)
reboot into twrp and flash magisk 19.3 (i don´t know if the newer Versions will work with MIUI Rom)
reboot into system
thats it
the other guy flashed the vendor partition only, without a reason in miui and ran into encryption.
Here is a very good site "Globe Rom" https://mi-globe.com/miui-firmware-rom-builder-features/65/
Click on MIUI 9.6.27 and Change to MIUI 10.3.8.0 then create your own rom with including Magisk and other nice tools.
You can flash the Globe Rom according to the same instructions as above and Magisk is after the first reeboot
immediately active.
ConradB said:
First backup your data
Flash 10.3.8.0 dirty in twrp
wipe cache, dalvik cache in twrp
reboot the device (not rooted)
reboot into twrp and flash magisk 19.3 (i don´t know if the newer Versions will work with MIUI Rom)
reboot into system
thats it
Click to expand...
Click to collapse
Aha! It works! :laugh: Thank you so much! :victory:
So... now I've "disabled forced encryption", do I ever need to worry about it again? Can I flash a new version of TWRP, or use a custom ROM and just use Magisk to re-root?
esuhl said:
Aha! It works! :laugh: Thank you so much! :victory:
So... now I've "disabled forced encryption", do I ever need to worry about it again? Can I flash a new version of TWRP, or use a custom ROM and just use Magisk to re-root?
Click to expand...
Click to collapse
Just it of curiosity what does it say about encryption under Settings -> Security?
Sent from my POCO F1 using XDA Labs
esuhl said:
Aha! It works! :laugh: Thank you so much! :victory:
So... now I've "disabled forced encryption", do I ever need to worry about it again? Can I flash a new version of TWRP, or use a custom ROM and just use Magisk to re-root?
Click to expand...
Click to collapse
If you flash Miui-Roms than no dfe needed.
If you flash a custom rom you should flash dfe.
guhvanoh said:
Just it of curiosity what does it say about encryption under Settings -> Security?
Click to expand...
Click to collapse
Settings -> "Security status" just shows:
Find device -- Off
Security update -- 2019-09-01
Google Play Protect > (Looks fine / No harmful apps found)
"Additional settings" -> Privacy -> "Encrypted & credentials" shows as "Encrypted".
However, the sub-option "Encrypt device using lock screen password" is turned off.
So just remember that if you want to move to another custom ROM you're going to have to format data. You're system is encrypted.
Sent from my POCO F1 using XDA Labs
i am using this
Disable force Encryption treble + Magisk20.2.zip (JAN 2020)
YasuHamed said:
i am using this
Disable force Encryption treble + Magisk20.2.zip (JAN 2020)
Click to expand...
Click to collapse
I only found DFE uploaded by someone. How can I get latest version? Isn't here any thread of it?
For some reason i can't get any rom to flash,
I keep getting error 7 (e1001 failed to update system image), doesn't matter if i try to flash lineage 16 or 17, g7 h-rom (based on stock 8).
Which is strange because i was able to flash roms before.
i tried flashing with twrp 3.3.1-0, 3.2.2-1 and 3.2.3-2 and orangefox recovery.
i have the h850 model and i currently use stock oreo.
After flashing the oreo kdz i've now factory reset the phone but have not attempted to flash a rom yet.
Any help would be appreciated.
dylank said:
For some reason i can't get any rom to flash,
I keep getting error 7 (e1001 failed to update system image), doesn't matter if i try to flash lineage 16 or 17, g7 h-rom (based on stock 8).
Which is strange because i was able to flash roms before.
i tried flashing with twrp 3.3.1-0, 3.2.2-1 and 3.2.3-2 and orangefox recovery.
i have the h850 model and i currently use stock oreo.
After flashing the oreo kdz i've now factory reset the phone but have not attempted to flash a rom yet.
Any help would be appreciated.
Click to expand...
Click to collapse
Did you by any chance tick the "verify zip signature" in the "swipe to flash" screen?
totalnoob34 said:
Did you by any chance tick the "verify zip signature" in the "swipe to flash" screen?
Click to expand...
Click to collapse
no, i didn't have that ticked
Doing a factory reset fixed the issue