D85120G-Untouched_Stock_Restore.zip
Flash Full Stock (system/kernel/modem/recovery) No Root, No Mods, 100% Stock
Thanks.
Since this is the full rom, not OTA, has anyone successfully twrp from stock rooted 20e and then SuperSU and kept root? Will TiBu frozen system apps stay frozen as well? TIA
What exactly is this rom?
cenwesi said:
What exactly is this rom?
Click to expand...
Click to collapse
The name of the zip file and first post tells you what it is.
LG G3 D851, Pac-Man ROM, Tapatalk 4.9.5
do we flash it through TWRP? or any other custom recovery?
Yes, just as you would w/ any other ROM. Perform a full wipe beforehand, excluding both internal and external storage. And if you want to retain root and recovery, make sure to flash those immediately after (add them to the queue in TWRP).
Just flash this rom.. Everything works fine..
Sent from my A1-840FHD using XDA Free mobile app
This may be a stupid question but I flashed this and it says I'm still vulnerable to stagefright, isn't this suppose to patch it.
Sent from my LG-D851 using Tapatalk
I flashed the same 20g ROM, and according to the Lookout Stagefright Detector app, my device is not vulnerable to Stagefright.
works but
Followed these instruction using twrp
http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667
I had to reset phone after flashing and setting up. Because the phone was no functioning correctly.
Unfortunately Stagefright CVE-2015-6602 is still vulnerable according to
Zimperium Stagefright detector app.
Lookout Stagefright Detector will not detect the latest Version 2.0 vulnerabilities of Stagefright and make it clear in there app description.
"This app does not support detection of Stagefright 2.0 vulnerabilities. "
So here we go again in the waiting game.
Wouldn't it be better if google took Stagefight out of the rom, so it can could be updated in play store?
painless
Wiped cache & Dalvik cache, flashed the OP update zip then flashed TWRP custom recovery and finally SupurSU.
Tested using Lookout Stagefright Detector and all is well.
side note: needed to regain writing privileges for my external SD
Thanks core720!
Works Great
AndroidUzer said:
Wiped cache & Dalvik cache, flashed the OP update zip then flashed TWRP custom recovery and finally SupurSU.
Tested using Lookout Stagefright Detector and all is well.
side note: needed to regain writing privileges for my external SD
Thanks core720!
Click to expand...
Click to collapse
Thanks bro,
Did exact same steps as you suggest and it worked great. Just in case anyone needs them....
Here is Super Su:
https://www.androidfilehost.com/?w=...b6cc0224f97f975b25bd6fd089dffab48899dd59ac9fc
ANd here is TWRP:
https://www.androidfilehost.com/?w=...9a65ee4397109b889147c21f3bf0e48037fffad3bccb3
fc3211 said:
Thanks bro,
Did exact same steps as you suggest and it worked great. Just in case anyone needs them....
Here is Super Su:
https://www.androidfilehost.com/?w=...b6cc0224f97f975b25bd6fd089dffab48899dd59ac9fc
ANd here is TWRP:
https://www.androidfilehost.com/?w=...9a65ee4397109b889147c21f3bf0e48037fffad3bccb3
Click to expand...
Click to collapse
Thanks for the two links. Very helpful
Anyone do it dirty, no wipes? From 20e to 20g? -Cuz restoring apps and settings is "such fun". Thanks.
skipaaa said:
Anyone do it dirty, no wipes? From 20e to 20g? -Cuz restoring apps and settings is "such fun". Thanks.
Click to expand...
Click to collapse
I landed here because I tried the 20e to 20g update and got the "unexpected version" error via twrp. Responding to my own post cuz I got bold and did it anyways.
...So, I had TWRP 2.8.7.0 D851 installed. Did full backups with Titanium paid version and TWRP. Started with STOCK rooted d85120e, left it rooted, and used TRWP to install
1) STOCK d95120g from top of this thread,
2) TWRP d851 2.8.7.0 found elsewhere (above link is 2.8.6.0), and
3) the SuperSU zip from link found just above.
Rebooted system without any wipes. A few minutes to update apps on first reboot and mostly good to go. Had to update SupserSU binaries via normal mode, and reinstall busybox. Busybox froze on black screen on multiple attempts during it's startup check, so on next attempt, I didn't let it finish the check, just told it to install, and has been bliss all day. So far, so stable. Better have the backups and not need them than need them and not have them. Settings show D85120G and Lookout shows NOT vulnerable to stagefright.
Sitting pretty. Hope this helps others who couldn't use the 20E to 20G update method to keep stock roms with optional root.
Wiped everything as stated and flashing reboots TWRP, anyone know why this happens?
Thank you! Works - rooted 20e to 20g
AndroidUzer said:
Wiped cache & Dalvik cache, flashed the OP update zip then flashed TWRP custom recovery and finally SupurSU.
Tested using Lookout Stagefright Detector and all is well.
side note: needed to regain writing privileges for my external SD
Thanks core720!
Click to expand...
Click to collapse
I was on rooted 20e and did what you said. Works like a charm, I have 20g now without any problems. Thank you everyone! :]
I finally came out of lurk mode to say thanks. This untouched ROM has saved me from 2 soft bricks. Works flawlessly.
it has no sound please help
Related
Just wanted to let everyone know that the 1.2.5i OTA that I received today has completely fixed the screen over-sensitivity issues for me.
I used to have a lot of issues with things like typing on the keyboard and scrolling through lists and the app drawer, but all those issues are completely gone now.
Also, the OTA did not mess with root. Root is intact.
Sent from my X9006 using Tapatalk
It also deleted everything an now I have to install everything again! So annoyed may not even go back to colouros, I'm am more than fed up with this phone this has happened to me twice, where the phone has decided to delete everything! Really starting to wish I didn't get the find 7
themsubtle said:
It also deleted everything an now I have to install everything again! So annoyed may not even go back to colouros, I'm am more than fed up with this phone this has happened to me twice, where the phone has decided to delete everything! Really starting to wish I didn't get the find 7
Click to expand...
Click to collapse
That is very strange. Did not delete anything for me, even the root is intact.
Sent from my X9006 using Tapatalk
rajitsingh said:
That is very strange. Did not delete anything for me, even the root is intact.
Sent from my X9006 using Tapatalk
Click to expand...
Click to collapse
My root is intact but everything else back to default factory settings and as titanium or the built in backup app don't work I now have to start again, i am really not happy would quite happily sell this phone now
Also there seems to be a bug with the new update where if you go into apps in the settings, it's force closes the settings app
Also since the update a lot of the system apps such as the backup and restore app force closes!
themsubtle said:
Also there seems to be a bug with the new update where if you go into apps in the settings, it's force closes the settings app
Also since the update a lot of the system apps such as the backup and restore app force closes!
Click to expand...
Click to collapse
It cannot be the update fault!! Check very well whats goes wrong. The update ist very good and completely fixed the screen over-sensitivity issues.:good:
blessingme said:
It cannot be the update fault!! Check very well whats goes wrong. The update ist very good and completely fixed the screen over-sensitivity issues.:good:
Click to expand...
Click to collapse
It must have been the update, because I have haven't changed anything else for it to happen, the update has fixed the screen sensitivity too which is good,but I am getting a lot of force closes, from settings app, backup and restore app, and few other system apps.
No issues
I had no issues with the update or any update. I still have root, settings are the same and all to data is there. Maybe your OTA packet got corrupted.
jebulol said:
I had no issues with the update or any update. I still have root, settings are the same and all to data is there. Maybe your OTA packet got corrupted.
Click to expand...
Click to collapse
It may have done because I lost all of my settings, apps and data, root was fine but thinking of possibly going to custom rom soon but not which is the most stable with least bugs
No issues here.
Every OTA update has been fine and dandy. I still have root since 1.2.1.
you're not alone.
themsubtle said:
It may have done because I lost all of my settings, apps and data, root was fine but thinking of possibly going to custom rom soon but not which is the most stable with least bugs
Click to expand...
Click to collapse
My girl's phone had something similar happen.
She updated to 1.2.5i OTA and lost everything - as if the phone went through a factory reset.
It even lost root. Irritated me to no end.
For reference, root was gained a couple of days prior on 1.2.4i through TWRP recovery and the supersu update 2.02.
The recovery was then flashed to the Find7 Mod recovery in the rooting thread on oppo forums.
I suspect that the OTA screw up may have been due to this Find7 mod recovery. I'm not sure.
How did you get root? and what recovery was on the phone when you did the OTA update?
scar200 said:
My girl's phone had something similar happen.
She updated to 1.2.5i OTA and lost everything - as if the phone went through a factory reset.
It even lost root. Irritated me to no end.
For reference, root was gained a couple of days prior on 1.2.4i through TWRP recovery and the supersu update 2.02.
The recovery was then flashed to the Find7 Mod recovery in the rooting thread on oppo forums.
I suspect that the OTA screw up may have been due to this Find7 mod recovery. I'm not sure.
How did you get root? and what recovery was on the phone when you did the OTA update?
Click to expand...
Click to collapse
I use the same modified recovery as I also used the same method for rooting on 1.2.4i. Even upgraded my supersu after rooting. It has to be something else.
Sent from my X9006 using Tapatalk
rajitsingh said:
I use the same modified recovery as I also used the same method for rooting on 1.2.4i. Even upgraded my supersu after rooting. It has to be something else.
Sent from my X9006 using Tapatalk
Click to expand...
Click to collapse
hmmm, then I'm not sure.
Her x9006 (Int-EU) is less than a week old and had nothing significant done except OTA (to 1.2.4i) then root before the 1.2.5i OTA was released.
scar200 said:
My girl's phone had something similar happen.
She updated to 1.2.5i OTA and lost everything - as if the phone went through a factory reset.
It even lost root. Irritated me to no end.
For reference, root was gained a couple of days prior on 1.2.4i through TWRP recovery and the supersu update 2.02.
The recovery was then flashed to the Find7 Mod recovery in the rooting thread on oppo forums.
I suspect that the OTA screw up may have been due to this Find7 mod recovery. I'm not sure.
How did you get root? and what recovery was on the phone when you did the OTA update?
Click to expand...
Click to collapse
I had the same as you modded recovery, and I gained root at 1.2.4i (the same way too supersu update thru twrp, then flashed modded recovery) not sure what happened but am still getting force closes when I go into apps in settings and couple other system apps
Also I have the find 7 qhd version
themsubtle said:
I had the same as you modded recovery, and I gained root at 1.2.4i (the same way too supersu update thru twrp, then flashed modded recovery) not sure what happened but am still getting force closes when I go into apps in settings and couple other system apps
Also I have the find 7 qhd version
Click to expand...
Click to collapse
Hmmm, when she gets back, I'll try to test if this modded recovery is indeed the issue.
I'm thinking of using the stock recovery provided by oppo on their forums.
Have you thought of doing full reflash to try and get rid of all the FCs?
scar200 said:
Hmmm, when she gets back, I'll try to test if this modded recovery is indeed the issue.
I'm thinking of using the stock recovery provided by oppo on their forums.
Have you thought of doing full reflash to try and get rid of all the FCs?
Click to expand...
Click to collapse
Yeh you'll have to let us know what you find out, Yeh I'm thinking that to, i have got twrp installed at the moment but that was only to do a backup.
I have thought of doing full wipe and re-flash but I haven't got a way to restore everything because titanium backup or the built in backup app are not working
themsubtle said:
Yeh you'll have to let us know what you find out, Yeh I'm thinking that to, i have got twrp installed at the moment but that was only to do a backup.
Click to expand...
Click to collapse
Ok, I did multiple tests, and am listing the 2 important ones.
Test 1
1. I reflashed back to 1.2.1i then OTA-ed to 1.2.2i (the next OTA it detected was1.2.5i), flashed TWRP and Update SuperSU 2.02 (to get root) then flashed the x9077-official-recovery-mod.
2. Installed some apps, changed some settings then OTA-ed to 1.2.5i - everything was deleted and I lost root after the OTA - essentially I had to go through the new phone start up menu (language, area, wifi, etc.).
*Initial problem replicated*.
Test 2
I did the exact same procedure again as in Test 1 step 1, but instead of the mod recovery I flashed the Stock Recovery for Find 7/7a (from the thread of the same name in the oppo forums, I used version 0712).
Then I again installed the same apps, changed the same settings and OTA-ed to 1.2.5i.
All the apps and settings remained but the phone lost root.
*Only significant delta between the 2 cases was the recovery version.*
Conclusion
The problem in my girl's case was the x9077-official-recovery-mod.img recovery. OTA-ing using that recovery caused her phone to go through a factory reset. This problem isn't present if the stock recovery direct from Oppo was used. Lesson learnt.
Hope this helps someone. Cheers.
themsubtle said:
I have thought of doing full wipe and re-flash but I haven't got a way to restore everything because titanium backup or the built in backup app are not working
Click to expand...
Click to collapse
Quick update, I switched the SU app from SuperSU to CWM's Superuser and that appears to have solved Titanium Backup issues (based on a thread in oppoforums).
It also made FolderMount usable (I set it up to link some folders from the internal storage to the external SD card).
Hope this helps.
scar200 said:
Quick update, I switched the SU app from SuperSU to CWM's Superuser and that appears to have solved Titanium Backup issues (based on a thread in oppoforums).
It also made FolderMount usable (I set it up to link some folders from the internal storage to the external SD card).
Hope this helps.
Click to expand...
Click to collapse
I can confirm that switching to CWM's Superuser works. When I updated to 1.2.5i I wasn't able to restore my data for ANY of my apps via Rom Toolbox. I decided to replace the Superuser app caused I remembered that worked for me once with a custom rom on the HTC Amaze, and sure enough now my apps' data has been restored. Success. :good:
rajitsingh said:
Just wanted to let everyone know that the 1.2.5i OTA that I received today has completely fixed the screen over-sensitivity issues for me.
I used to have a lot of issues with things like typing on the keyboard and scrolling through lists and the app drawer, but all those issues are completely gone now.
Also, the OTA did not mess with root. Root is intact.
Sent from my X9006 using Tapatalk
Click to expand...
Click to collapse
Hi, regarding the screen touch oversensitivity issue, just one question - are you using any sort of screen protector?
I have a tempered glass screen protector. I tried everything from 1.2.4i to 2.0.1i beta and the screen problem is there. Hearing good news about this 1.2.5i update and need somebody to confirm it works.
Hi all
My friend's wife has a swift with YOG4PAS33J and he says her notifications mention a system upgrade.
Has anyone else noticed same? I ask because https://cyngn.com/support mentiones Cyanogen OS 12.1 (5.1.1) cm-12.1-YOG4PAS33J-crackling.
Thanks
Yes I have installed the upgrade YOG7DAS2FI and now running cyanogen 12.1.1.
Yep - changelog on twitter (Wileyfox).
It seems I haven't posted enough to allow me to post links.
is a ZIP file available for flashing via TWRP?
Dior DNA said:
is a ZIP file available for flashing via TWRP?
Click to expand...
Click to collapse
Thanks to 4PDA
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45683960
PS Never tried.
I am using CM13 Teamasek's ROM as my daily driver
mermigas said:
Thanks to 4PDA
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45683960
PS Never tried.
I am using CM13 Teamasek's ROM as my daily driver
Click to expand...
Click to collapse
thanks
FYI the 4PDA is YOG7DAS2BC but above was mentioned YOG7DAS2FI
Dior DNA said:
thanks
FYI the 4PDA is YOG7DAS2BC but above was mentioned YOG7DAS2FI
Click to expand...
Click to collapse
Sorry. My Russian is not so good!!
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45707464
mermigas said:
Sorry. My Russian is not so good!!
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45707464
Click to expand...
Click to collapse
your russian seems good enough
meanwhile https://cyngn.com/support got updated
Hey, I'm new to rooting and I'm wondering how I should go about installing this update. I assume I can't just download it OTA, so what steps should I go through to install the update? Should I use the update pack from cyanogen support (can't post link)? If so, which one? cm-12.1-YOG7DAS2FI-crackling-signed-fastboot-07863145a7.zip or cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip? Sorry for my noobishness!
seb5049 said:
Hey, I'm new to rooting and I'm wondering how I should go about installing this update. I assume I can't just download it OTA, so what steps should I go through to install the update? Should I use the update pack from cyanogen support (can't post link)? If so, which one? cm-12.1-YOG7DAS2FI-crackling-signed-fastboot-07863145a7.zip or cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip? Sorry for my noobishness!
Click to expand...
Click to collapse
Is your firmware stock? Then OTA should announce itself and install fine (unless perhaps if your phone is encrypted).
Dior DNA said:
Is your firmware stock? Then OTA should announce itself and install fine (unless perhaps if your phone is encrypted).
Click to expand...
Click to collapse
I've rooted my phone using a guide on this forum. I have also installed TWRP recovery.
seb5049 said:
I've rooted my phone using a guide on this forum. I have also installed TWRP recovery.
Click to expand...
Click to collapse
OK . you can then download the official firmware and install it. When prompted by TWRP recovery to install SU chose NO.
mermigas said:
OK . you can then download the official firmware and install it. When prompted by TWRP recovery to install SU chose NO.
Click to expand...
Click to collapse
Should I install everything in the zip? Won't that wipe all of my data?
seb5049 said:
Should I install everything in the zip? Won't that wipe all of my data?
Click to expand...
Click to collapse
The cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip updater-script does not seem to wipe data.
You may want to wipe dalvik and /cache first though.
Dior DNA said:
The cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip updater-script does not seem to wipe data.
You may want to wipe dalvik and /cache first though.
Click to expand...
Click to collapse
OK, one last thing: How do I flash the zip? Can I just put it on my phone and use TWRP to install it? Or do I have to use adb? And what's dalvik?
seb5049 said:
OK, one last thing: How do I flash the zip? Can I just put it on my phone and use TWRP to install it? Or do I have to use adb? And what's dalvik?
Click to expand...
Click to collapse
You flash using TWRP. The zip can be put on sdcard (internal or external).
The dalvik cache holds some sort of compiled java code. For minor upgrades one can perhaps leave it untouched. For major upgrades one typically wipes it. It does not hurt to wipe dalvik cache. After install, it is regenerated as part of the android upgrade.
Note that stock firware is probably unrooted so you may want to reinstall supersu update zip from twrp. Also, upgrade may or may not overwrite twrp with stock recovery so you may have to reflash twrp.
I have not done the upgrade myself (I will one day, I have no Swift, a friend has one).
Success
Dior DNA said:
You flash using TWRP. The zip can be put on sdcard (internal or external).
The dalvik cache holds some sort of compiled java code. For minor upgrades one can perhaps leave it untouched. For major upgrades one typically wipes it. It does not hurt to wipe dalvik cache. After install, it is regenerated as part of the android upgrade.
Note that stock firware is probably unrooted so you may want to reinstall supersu update zip from twrp. Also, upgrade may or may not overwrite twrp with stock recovery so you may have to reflash twrp.
I have not done the upgrade myself (I will one day, I have no Swift, a friend has one).
Success
Click to expand...
Click to collapse
Ok, I flashed the update, everything works fine except that every few seconds I get a box that says "Unfortunately, Google Play Services has stopped.". Super annoying!
EDIT: Allowing wakelocks for Google Play Services in Privacy Guard fixes it.
seb5049 said:
Ok, I flashed the update, everything works fine except that every few seconds I get a box that says "Unfortunately, Google Play Services has stopped.". Super annoying!
EDIT: Allowing wakelocks for Google Play Services in Privacy Guard fixes it.
Click to expand...
Click to collapse
@seb5049
Just for my information: did you wipe dalvik-cache?
Google Play and Google Play Services typically may get updated / changed during or right after upgrade.
Dior DNA said:
@seb5049
Just for my information: did you wipe dalvik-cache?
Google Play and Google Play Services typically may get updated change during or right after upgrade.
Click to expand...
Click to collapse
Yeah, I did. By the way, I disabled the permissions again, but everything's fine now.
Just an informative message in case people were having same issues I was, reading the posts, I see many are.
The amazing @Chainfire has a working beta method which allows me a simple, fully stock rooted OL1, with deep sleep fixed, and a small tweak to get Titanium Backup (TiBu) working on my sprint galaxy s6 (SM-G920P).
Note that chainfire's site (http://autoroot.chainfire.eu/) as of 1/16/16 had a autoroot version for the G920P that installed the 2.65 NOT the 2.66 (or 2.67) (beta deep sleep fixed versions) of SuperUser SU, so you'll have to TWRP install the 2.66 or 2.67 to get the deep sleep fix
Here's the brief GUIDE how I did it:
1. Download OL1 here's the sammobile link http://www.sammobile.com/firmwares/download/62965/G920PVPU3BOL1_G920PSPT3BOL1_BST/
2. Download ODIN 3.10.6 http://forum.xda-developers.com/showthread.php?t=2711451
3. Download CFautoroot for the Sprint Galaxy s6, and consider donating to @Chainfire https://download.chainfire.eu/785/CF-Root/CF-Auto-Root/CF-Auto-Root-zerofltespr-zerofltespr-smg920p.zip
4. ODIN flash first the Stock OL1 and then the CFautoroot
5. Download and flash THIS TWRP https://dl.twrp.me/zeroflte/twrp-2.8.7.0-zerofltespr.img.tar.html or select appropriate one from https://dl.twrp.me/zerofltespr/ *(note that 3.0.0-0 is now available, but I haven't tried it yet, 2.8.7.0 still working well)
6. DEEP SLEEP FIX Download SU 2.67 Beta https://download.chainfire.eu/897/SuperSU/BETA-SuperSU-v2.67-20160121175247.zip
*** Note- this beta version of SU works PERFECTLY on my 920P phone, and fixed the deep sleep issue
7. Move the SU 2.67 Beta to your phone's hard drive. Put it somewhere you can find it easily.
8. Boot into TWRP recovery (power, home key and volume up). Click "Install" and select the 2.67 SU Beta zip folder you just downloaded.
OPTIONAL:
9. Fix TiBu: Easy fix- uncheck in SU the "mount namespace separation"
Done.
Finally- pure stock rooted, nearly no crashes, everything seems to work. :good:
UPDATE 2.20.16: Both Beta versions 2.66 and 2.67 SuperSu DID in fact eventually crash, but only after 10 days did i get my first, and after 5 weeks, it has only occurred with Dolphin Browser, and only rarely- so might be a setting related to that app. Still way better and more stable than unikernel method.
that's awesome!
Sent from my S6 using tapatalk
Did it trip Knox?
1619415 said:
Did it trip Knox?
Click to expand...
Click to collapse
I had previously used @djvoleur 's UniKernel v8 and v9, so I already had knox tripped
Saafir said:
It says he Odin'd TWRP so I would assume so. Kind of confused to what good ths method is lol
Click to expand...
Click to collapse
I couldn't find a pure stock with a pure stock kernel way to root. Rooting using the UniKernel method kept me with a very buggy system that repeatedly crashed, no matter what I did to manipulate it.
Once chainfire autoroot became available for the s6, that was great- but it had the deep sleep issue (and also messed with a TiBu setting). His 2.66 update fixed the deep sleep issue, and a simple settings change fixed the TiBu issue.
googling for these answers wasted a lot of my time, and reading posts- I saw that others were struggling with this too-- especially since they weren't sure his methods would work on the sprint version of the s6.
So I just thought I'd save people some time, confirm that the methods work great on the 920P, and give them links to how to do it
I just tried this procedure.
Everything goes ok, but TWRP will not accept input. If I touch the screen nothing happens. After a bit, the screen will lock (and swiping with my finger wont work) and the only alternative is to reset using pwr-home-voldn. I tried TWRP 2.8.7.1 and 2.8.7.2 and both do it. TWRP 2.8.7.0 works ok, but the first time I tried, it put the phone into a boot loop where the animation would start, and then reboot.....
I was running OL1 stock (got the phone two days ago).
Still investigating... Reloading stock ROM.
At least 2.8.7.0 allowed me to input into TWRP. Was able to flash SuperSU. Did not get stuck on boot animation this time.
Huey Driver said:
I just tried this procedure.
Everything goes ok, but TWRP will not accept input. If I touch the screen nothing happens. After a bit, the screen will lock (and swiping with my finger wont work) and the only alternative is to reset using pwr-home-voldn. I tried TWRP 2.8.7.1 and 2.8.7.2 and both do it. TWRP 2.8.7.0 works ok, but the first time I tried, it put the phone into a boot loop where the animation would start, and then reboot.....
I was running OL1 stock (got the phone two days ago).
Still investigating... Reloading stock ROM.
At least 2.8.7.0 allowed me to input into TWRP. Was able to flash SuperSU. Did not get stuck on boot animation this time.
Click to expand...
Click to collapse
Hmm, interesting.
I used twrp-2.8.7.1-zerofltespr.img and that worked just fine.
I only had an issue when I (briefly, mistakenly) tried to use the TWRP from this link http://forum.xda-developers.com/galaxy-s6/general/guide-android-6-0-marshmallow-beta-how-t3277533/post64613464#post64613464
When I flashed that incorrect TWRP, I got stuck in the same manner you did-- but twrp-2.8.7.1-zerofltespr.img worked fine.
Of note- I fixed the link above to go to the https://dl.twrp.me/zeroflte/ and https://dl.twrp.me/zeroflte/twrp-2.8.7.0-zerofltespr.img.tar.html pages.
Somehow though it seems I have a copy of the sprint version of 2.8.7.1, I can only see the 2.8.7.0 listed on the TWRP sites. I am sure that also should work fine
good luck
**Correction: the newest TWRP is 2.8.7.0 for the G920P
It may well just be something I did. Like I said, brand new phone....
I used ODIN, and I got the downloads from the TWRP site (dl.twrp.me)...
Regardless, I got 2.8.7.0 to work and I have root. Not really sure what the differences are.
Just kind of putting it out there for others....
my phone is already rooted, can i uninstall supersu 2.44 and flash supersu 2.66?
legola said:
my phone is already rooted, can i uninstall supersu 2.44 and flash supersu 2.66?
Click to expand...
Click to collapse
yes- essentially- but because the supersu 2.66 beta is in a zip file (with multiple files for the multiple system architectures in it), you can't (i don't believe) flash through ODIN.
You must download the zip directly onto your phone hard drive (somewhere easy to find), or download on your laptop and transfer to your phone (again, putting somewhere easy to find), then boot into recovery, and install via TWRP. It should replace the supersu file, and automatically fix any deep sleep issue, if you haven't already fixed that previously
spammy l said:
yes- essentially- but because the supersu 2.66 beta is in a zip file (with multiple files for the multiple system architectures in it), you can't (i don't believe) flash through ODIN.
You must download the zip directly onto your phone hard drive (somewhere easy to find), or download on your laptop and transfer to your phone (again, putting somewhere easy to find), then boot into recovery, and install via TWRP. It should replace the supersu file, and automatically fix any deep sleep issue, if you haven't already fixed that previously
Click to expand...
Click to collapse
It actually won't, unless your stock. Unikernel will just keep overwriting it since it's prerooted.
spammy l said:
Hmm, interesting.
I used twrp-2.8.7.1-zerofltespr.img and that worked just fine.
I only had an issue when I (briefly, mistakenly) tried to use the TWRP from this link http://forum.xda-developers.com/galaxy-s6/general/guide-android-6-0-marshmallow-beta-how-t3277533/post64613464#post64613464
When I flashed that incorrect TWRP, I got stuck in the same manner you did-- but twrp-2.8.7.1-zerofltespr.img worked fine.
Of note- I fixed the link above to go to the https://dl.twrp.me/zeroflte/ and https://dl.twrp.me/zeroflte/twrp-2.8.7.0-zerofltespr.img.tar.html pages.
Somehow though I have a copy of the sprint version of 2.8.7.1, I can only see the 2.8.7.0 listed on the TWRP sites. I am sure that should work fine
good luck
Click to expand...
Click to collapse
actually, AFAIK for our G920P, the latest TWRP is 2.8.7.0.
Your 2.8.7.1 might be named wrongly. could you please check in the TWRP screen?
yaibakt said:
actually, AFAIK for our G920P, the latest TWRP is 2.8.7.0.
Your 2.8.7.1 might be named wrongly. could you please check in the TWRP screen?
Click to expand...
Click to collapse
You are correct- I checked the TWRP screen, and it is in fact 2.8.7.0. My file must be named incorrectly. I edited that post to reflect this. Thanks for pointing this out. :good:
spammy l said:
You are correct- I checked the TWRP screen, and it is in fact 2.8.7.0. My file must be named incorrectly. I edited that post to reflect this. Thanks for pointing this out. :good:
Click to expand...
Click to collapse
:good:
one more thing:
i use your trick and CAN restore apps by titanium backup. thank you.
but, could you confirm for me that: can you uninstall a system app by titanium backup?
for me, when i tap a system app in tita, and uninstall it, then reboot the phone, the app appears again.
i have to use root explorer to delete the app manually.
yaibakt said:
:good:
one more thing:
i use your trick and CAN restore apps by titanium backup. thank you.
but, could you confirm for me that: can you uninstall a system app by titanium backup?
for me, when i tap a system app in tita, and uninstall it, then reboot the phone, the app appears again.
i have to use root explorer to delete the app manually.
Click to expand...
Click to collapse
Hi- Glad the titanium backup trick worked for you- it frustrated me a bit until i found that answer.
Yes- I can confirm that both uninstalling and/or freezing system apps work in TiBu, and they do not re-install. When I uninstall a system app with TiBu, it does stay uninstalled after reboot.
Maybe it is a security issue? I use an english translation of LBE security, but have also used X-privacy, and both those (along with some other programs) block unwanted installations.
spammy l said:
Hi- Glad the titanium backup trick worked for you- it frustrated me a bit until i found that answer.
Yes- I can confirm that both uninstalling and/or freezing system apps work in TiBu, and they do not re-install. When I uninstall a system app with TiBu, it does stay uninstalled after reboot.
Maybe it is a security issue? I use an english translation of LBE security, but have also used X-privacy, and both those (along with some other programs) block unwanted installations.
Click to expand...
Click to collapse
thank you.
how weird over here...
i can freeze apps, but cannot uninstall apps by titanium. it was possible when i root my phone using unikernel v8.
one feedback from here: the battery life is somehow worse than using unikernel v8. yesterday i just had about 3h15' on screen from 100% to 1% battery, compared to about 4h30-5h onscreen with unikernel v8. the usage is normal like everyday of mine.
however im just using this method for 1 day so i will give it some more days to see if there is any improvement...
yaibakt said:
thank you.
how weird over here...
i can freeze apps, but cannot uninstall apps by titanium. it was possible when i root my phone using unikernel v8.
one feedback from here: the battery life is somehow worse than using unikernel v8. yesterday i just had about 3h15' on screen from 100% to 1% battery, compared to about 4h30-5h onscreen with unikernel v8. the usage is normal like everyday of mine.
however im just using this method for 1 day so i will give it some more days to see if there is any improvement...
Click to expand...
Click to collapse
hmmm- bizarre.
Not sure exactly what is going on with your system. As for the battery- mine has been working great (by s6 standards)- way better than unikernel v9, and at least as good as unikernel v8.
Are you sure it is deep sleeping? Positive it is running SuperSU v2.66? (could check on the settings page) Also, though I'm sure you'd know if it weren't deep sleeping, you could try running the "CPU Deep Sleep Info Widget" to double check. https://play.google.com/store/apps/details?id=de.cmweb.deepsleep&hl=en
As for mine- I'm over a week into this method, haven't crashed a single time to lock screen, battery is working great (for a s6), and all apps seem to work smoothly- without all the bugs I was experiencing with unikernel.
Hope your phone gets sorted out soon too
yeah, im sure that all the setting on my phone are the same between unikernel v8 and this method. i use SU v2.66 too.
i havent got any crash on v8 either, so basically i just compare v8 and this method in battery life.
i dont use v9 since it's reported to have lockscreen issue.
but well, i'll being using this method at least till weekend to see. i'll just be able to re-flash the rom if necessary at that time anyway.
thank you.
I have been away from the forums for a few weeks, i was curious if this or any method allows for rooting but retaining knox status? I am rooted (with the old pingpong method) but stayed on OE2 (5.0.2) to keep knox intact. I would love to get updated to the latest OS rooted but keep knox intact still.. not sure if its possible, so i check with yall..
sj
Sent from my SM-T210R using Tapatalk
If i were to skip the custom recovery flash, would i be able to receive ota updates?
Sent from my SM-G920P using Tapatalk
This was tough to get as LG locked down all known exploits with the ZVI release. It took some hardware hacking to pull a clean unmodified system and kernel. Here is a flashable zip:
http://jacobstoner.com/LS980ZVI.zip
This includes a bootstack with an older bootloader and TWRP 2.8.7.3. The ZVI kernel has been bumped to work with the older bootloader. Otherwise this is completely unmodified and unrooted so if you want root then flash SuperSU after flashing this.
http://download.chainfire.eu/supersu
Thanks for sharing, i am on cyanogenmod 11, can i install it with hybrid bootstack and blestagator's bumped twrp?
It will replace your bootstack and update twrp, but it will work fine.
Thanks, man! I wait for it so long! Because I'm still on ZVG because ZVI was unrootable. So all what I need is just clean flash room in recovery and install supersu app? Without any unlockers? Downloading now, making backups and give a try!
astherion said:
Thanks, man! I wait for it so long! Because I'm still on ZVG because ZVI was unrootable. So all what I need is just clean flash room in recovery and install supersu app? Without any unlockers? Downloading now, making backups and give a try!
Click to expand...
Click to collapse
Yes, just flash in recovery and flash the supersu zip from the link above. You can dirty flash over ZVG, it will overwrite the whole system partition anyway.
Confirmed! If works! Just made clean installation 20 minutes ago & flash supersu.zip through recovery. Superuser works fine. So now I've try restore zvg & flash over it. Because I use lots of exposed modules & dorimanx kernel, titanium backup, lucky patcher, freedom etc. For this sw root is critical... Thanks a lot for latest ZVI + root! Later I link to your thread for peoples from russian 4PDA LG G2 thread. Lots of people will be happy!
ROM working well for me too. Thanks!
Not ever try to flash on installed rom! You'll receive a lots of lags after! Make app backup & flash "clean" install through recovery. I found also 1 issue in recovery: then screen goes off after you turn it on you see only blue-grey-black-white stripes with tiny squares. It happens not always but sometimes.
P.S. Previously I also used bumped 2.8.7.3 TWRP and has no problems. Also I use xposed, so when I flash ZVI on ZVG & restore apps backup has lots of lags like force close systemUI, deleted unworking software etc. So - clean install! After that - restore backup, but only user apps, not system like xposed apps, home g4 launcher, dialer etc.!
Rom
Its working fine ... but i am facing network lock issue...Kindly help
To nomansabir: what means network lock? Simlock? Or you can't switch cdma/lte?
astherion said:
To nomansabir: what means network lock? Simlock? Or you can't switch cdma/lte?
Click to expand...
Click to collapse
Dear i am facing sim lock problem.... Its showing Invalid sim card message...
SIM-unlock
Nomansabir: you need made sim-unlock again.
Download Wirking+Hotspot.zip. You must be rooted 1st. Install adbdinsecure2.00.apk, open it, accept root privileges, use checkbox "enable insecure adb" - exit apk. Connect g2 to pc, open simunlock.exe with admin rights, phone must reboot itself after correct installation. Voila: you phone is now sim-free!!!
P.S. You can delete adbdinsecure.apk after
astherion said:
Nomansabir: you need made sim-unlock again.
Download Wirking+Hotspot.zip. You must be rooted 1st. Install adbdinsecure2.00.apk, open it, accept root privileges, use checkbox "enable insecure adb" - exit apk. Connect g2 to pc, open simunlock.exe with admin rights, phone must reboot itself after correct installation. Voila: you phone is now sim-free!!!
P.S. You can delete adbdinsecure.apk after
Click to expand...
Click to collapse
Thnx astherion .... its working fine now.....
jacob019 said:
This was tough to get as LG locked down all known exploits with the ZVI release. It took some hardware hacking to pull a clean unmodified system and kernel. Here is a flashable zip:
http://jacobstoner.com/LS980ZVI.zip
This includes a bootstack with an older bootloader and TWRP 2.8.7.3. The ZVI kernel has been bumped to work with the older bootloader. Otherwise this is completely unmodified and unrooted so if you want root then flash SuperSU after flashing this.
http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
that's wonderful, @jacob019, thanks for sharing this highly waited zip of the ZVI, as far as i am on cloudy G2 3.3 with my LS980 for a long time and have not experienced the stock firmware after ZVG.
I have two questions in my mind if you could please clear them.
1. Is there any problem in the ZVI like most of the LG updates have not been without bugs or lagging ?
2. Can i flash this zip directly from my already installed TWRP without going back to stock ZVG or ZVE? (I have Cloudy G2 3.3 installed with blastgator's boot stack/baseband) {Cloudy G2 v3.3 is indeed a perfect ROM for my LS980 till now}
Thanks again for the great job you have done
talvigi said:
1. Is there any problem in the ZVI like most of the LG updates have not been without bugs or lagging ?
2. Can i flash this zip directly from my already installed TWRP without going back to stock ZVG or ZVE? (I have Cloudy G2 3.3 installed with blastgator's boot stack/baseband) {Cloudy G2 v3.3 is indeed a perfect ROM for my LS980 till now}
Click to expand...
Click to collapse
1. I've been using it for a couple weeks, seems quite stable but I'm a light user.
2. Yes, you can flash it directly from your already installed TWRP. No need for any other preparation.
jacob019 said:
1. I've been using it for a couple weeks, seems quite stable but I'm a light user.
2. Yes, you can flash it directly from your already installed TWRP. No need for any other preparation.
Click to expand...
Click to collapse
Thanks @jacob019 for your time and again for your great job.
I will try it as soon as the download of the zip file will be completed.
And i also must try the SIM unlock as you mentioned above because i live out of US and am using GSM network not CDMA, so i think to do that i need some preparations.
I hope there are thousands in this line to need ZVI and the SIM unlock. Hail Jacob.
What is the flashing procedure by the way? is it same as we flash custom ROM (wipe system, devlock, cache and data) or just wipe dev lock and cache and flash the zip file
Just reboot to tarp recovery, choose wipe - advanced - check all except "sdcard" - wipe and just flash zip. Also better to flash supersuper.zip if you need root. Reboot - profit!
For me it works flawlessly, slight more battery drain, but solved by dorimanx kernel, xposed & greenify app. I didn't see the even mentioned lags in this Rom. Working for me the same as ZVG & also rootable!
astherion said:
Nomansabir: you need made sim-unlock again.
Download Wirking+Hotspot.zip. You must be rooted 1st. Install adbdinsecure2.00.apk, open it, accept root privileges, use checkbox "enable insecure adb" - exit apk. Connect g2 to pc, open simunlock.exe with admin rights, phone must reboot itself after correct installation. Voila: you phone is now sim-free!!!
P.S. You can delete adbdinsecure.apk after
Click to expand...
Click to collapse
@astherion, Thanks for the SIM Unlock files, by the way rooted is OK but but what is "after correct installation" is it what the software in PC does with the mobile or something else? And developer options have to enabled or otherwise?
Edited: Thank you very much guys specially @jacob019 and @astherion, you guys rock the party. The stock Lollipop is flashed perfectly and SIM Unlock was the most simple step i have every seen in the LG world, But astherion you should have mentioned the USB debugging option as it needs to be enabled before running the simunlock.exe from the PC, and an other thing i can see Hands free activation disturbs after every reboot (i have just rebooted twice and it cameup both times) and battery level also going very fast don't know why but, this can be a major issue which may force some people like me to go back to Cloudy. My battery was at 75% and 4 hours 12 minutes remaining and after i rebooted to recovery and wiped devlock cache and data, still battery says 69 % 3 hours 3 minutes remaining. This is dangerous, the battery graph is showing like a forward slash is on the graph panel, I will attach pics.
Indeed this all made me a fan of you guys,
So I am on ZVH, rooted with TWRP installed. Can I just flash the zip files?
When doing a clean install, are you just totting back to an earlier release(ZVE or G), rooting and installing TWRP and then this zip files?
tekweezle said:
So I am on ZVH, rooted with TWRP installed. Can I just flash the zip files?
When doing a clean install, are you just totting back to an earlier release(ZVE or G), rooting and installing TWRP and then this zip files?
Click to expand...
Click to collapse
Yes, you can just flash the zip file; should be no need to wipe data if you're coming from ZVG. Also there is no need to tot back to an earlier release unless you are already on ZVI because wiping data and installing this zip will produce just as clean of an install.
@talvigi, battery is okay for me; but I'm used to stock. I'm not sure about disabling activation because I'm using it on Sprint. I'm sure you can find info on how to improve both of those issues, but there isn't anything to be done here since this is an unmodified stock rom.
I have rooted firetv 1 with latest rBox pre-rooted ROM. I have noticed if I put the box in sleep mod for a while, it will change to TWRP recovery screen when wake it up. I have to reboot it every time in order to back to normal. Anyone has the same problem?
Thanks.
Seattleweather said:
I have rooted firetv 1 with latest rBox pre-rooted ROM. I have noticed if I put the box in sleep mod for a while, it will change to TWRP recovery screen when wake it up. I have to reboot it every time in order to back to normal. Anyone has the same problem?
Thanks.
Click to expand...
Click to collapse
Most folks that have had this problem is because they did not block updates properly. And you have an update in the hopper. And TWRP being your last line of defense is blocking the installation of that update since it is not a PreRooted ROM. So each time your device is idle it tries to install the update. And TWRP stops it at reboot.
Luckily there are solutions.
http://www.aftvnews.com/how-to-stop...rom-installing-on-a-fire-tv-or-fire-tv-stick/
And at the very least do Method 1. But both Method 1 & Method 5 are what is recommended to stop this from happening in the future.
http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/
Y314K said:
Most folks that have had this problem is because they did not block updates properly. And you have an update in the hopper. And TWRP being your last line of defense is blocking the installation of that update since it is not a PreRooted ROM. So each time your device is idle it tries to install the update. And TWRP stops it at reboot.
Luckily there are solutions.
http://www.aftvnews.com/how-to-stop...rom-installing-on-a-fire-tv-or-fire-tv-stick/
And at the very least do Method 1. But both Method 1 & Method 5 are what is recommended to stop this from happening in the future.
http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/
Click to expand...
Click to collapse
Thanks you very much. I believe I did one BEFORE flash to new pre-root ROM. I tried to do it again this morning, found the superuser is not there anymore after flash to pre-root ROM from rbox. I am confused since I rooted firmware and unlocked bootlocker. I does not me to install superuser anymore. Please help me:crying::crying::crying:
Seattleweather said:
Thanks you very much. I believe I did one BEFORE flash to new pre-root ROM. I tried to do it again this morning, found the superuser is not there anymore after flash to pre-root ROM from rbox. I am confused since I rooted firmware and unlocked bootlocker. I does not me to install superuser anymore. Please help me:crying::crying::crying:
Click to expand...
Click to collapse
If you are able to still go into TWRP. I would try to flash the latest PreRooted ROM using a USB Stick. Also make sure you include a MD5 for safety. DO NOT WIPE anything but Dalvik Cache & Cache. See if that restores your PreRooted FW back to normal. This is just a guess since it has never happened to me before.
Maybe someone with this problem the fixed things can chime in. Others that this has had happened to did not have access to TWRP.
Y314K said:
If you are able to still go into TWRP. I would try to flash the latest PreRooted ROM using a USB Stick. Also make sure you include a MD5 for safety. DO NOT WIPE anything but Dalvik Cache & Cache. See if that restores your PreRooted FW back to normal. This is just a guess since it has never happened to me before.
Maybe someone with this problem the fixed things can chime in. Others that this has had happened to did not have access to TWRP.
Click to expand...
Click to collapse
FIXED!!!
I tried to install superuser apk , but failed. Since I still have access to TWRP, I installed with flashable superuser. Then I cleared OTA and blocked the updates again with your suggestion. I did Method 1 before, but forgot to do it again after update. Thank you very much!!!
Seattleweather said:
FIXED!!!
I tried to install superuser apk , but failed. Since I still have access to TWRP, I installed with flashable superuser. Then I cleared OTA and blocked the updates again with your suggestion. I did Method 1 before, but forgot to do it again after update. Thank you very much!!!
Click to expand...
Click to collapse
np, glad it is back to normal.
Method 1 helps when you flash a new PreRooted ROM. And Method 5 helps to make sure your FW version is never low enough to think an update would apply to your device. Method 5 needs to be redone when ever you flash a ROM. And Method 1 must be redone when ever you factory reset thru TWRP or clean more then the Dalvik Cache & Cache thru TWRP. NEVER do a factory reset from FireOS 5. Only use TWRP for that.
Forgot to add. NEVER INCLUDE SYSTEM IN ANY OF YOUR WIPES. Flashing a PreRooted ROM will take care of System. So leave it alone. Most bricks happen because folks wipe SYSTEM & they do not Flash a PreRooted ROM before doing a reboot.