Related
I've had an LG E970 running the stock ROM for about a year and decided to try out CM. I'm new to this, but I did some research and went ahead and rooted the phone, and then installed ClockworkMod. That went smoothly, so I tried to install CM through CWM and it appeared to work until it finished booting up and led me to the encryption PIN screen. My PIN from the stock ROM won't open it. CWM can't mount the encrypted data partition to wipe it.
I can boot to CWM or the CM encryption screen. I tried doing a restore on CWM but keeping getting MD5 errors. I haven't had any luck finding the stock ROM anywhere online, I tried an LG tool to get the kdz but it kept giving me error messages when I entered the serial number. I used Titanium to backup everything beforehand, but I can't figure out how to use the files to restore the old ROM. I can put files onto the SD card with my computer, but don't know if that'll be any help. I tried using the ADK to connect to the phone in fastboot, but the phone doesn't show up when I enter the fastboot devices command. Will an older version of CM thats based on the same version of Android the phone was encrypted with be able to open the data? I've tried researching this but everything I've found suggests going about it in different ways and nothing I've tried has worked.
If anybody could give me any help I'd appreciate it.
You may wish to refer to [GUIDE][E970]Using LG Flash Tool To Flash .tot Files {Alternate To LGNPST}[WIP]
Of note to you is Post #8 If you still have issues, you can post on that thread as well.
I followed that guide, but got stuck because the LG Flashtool is identifying my phone as a Nexus 4 and not allowing me to install the E970 files. I think the phone ID changed because the CM version I downloaded was converted from the Nexus ROM. I was able to flash an earlier version, but it had the same problem. Do you have any suggestings for a ROM with the correct phone ID? Is there any other ROM that might be able to decrypt the stock Android encrypted data?
Thanks!
I fixed it!
By plugging my SD card into the computer, I was able to add new ROMs to it and flash them in CWM. I was trying out different ROMs, hoping one would show up as the right phone model in LG Flashtool, and I found one for LG Official Kitkat 4.4.2 Stock. It was able to decrypt the data and now my phone is usable again. I'll revert to the stock recovery, wipe the phone (including encryption) and then start over with CM.
Here's a link to the ROM in case anybody else has this problem later:
http://forum.xda-developers.com/showthread.php?t=2771440 - Thread
http://level99.nighthorsemedia.com/geeb/LG-KK-4.4.2-Fixed.zip - Download Link
Thanks!
Hey there fellas,
Being a part time/spare time "mod wanna be", I've successfully modded different cell phones every now and then.
Lately I bought, 2nd hand, a XT925 running as it was in the attached screen shot + unlocked BL, rooted and CWMR touch 6.0.4.4.
Since the phone was rebooting itself kinda often, since I've been told that Epinters builds was JBBL based and also based on the phone info 3.0.x Kernel, I thought it was ok to flash a stock ROM and after that, upgrade to KK via OTA.
I've flashed the JB 4.1.2 BR Retail via fastboot and everything went ok. I let it boot, ran through configurations and just made myself sure that basic options were working ok. The OTA pops up, I downloaded it and proceed to install...an error pops up while it was somewhere around 25-30% of the flashing process.
I talked to the previous owner and he said that he went to CM because the cell never was able to install OTAs, there was always errors on the installation process.
With that in mind, I proceed to research some tutorials about alternative methods on how to install KK OTA.
I've found one here and another one on other forum, which was more suited to my needs since I'm at Brazil. Both are suggesting the same method:
Requirements:
1.Stock/unmodified JB4.1.2
2.Stock recovery
3.Unrooted
4.Bootloader unlocked
Since I met all the requirements, I proceeded to give it a try.
The next steps was:
1.Download a JB custom recovery and flash it via fastboot
2.Correct OTA installed on the external SD card
3.Install the OTA via custom recovery
4.install KK custom recovery
5.Root
Steps 1 and 2 were ok but again, while attempting to flash the OTA there was errors. Since Ive tried the whole process several times with different files, doing MD5 checksums, with different custom recoveries, I may divide the errors in 2 separate categories:
Error category 1:
While verifying current system, different .apks has unexpected contents. Status 7 as the final status error.
Since I was battling with this for 36 hours non stop, just before going to have some sleep, I decided to format internal SD since I thought maybe there was some leftovers from previous installations.
Apparently everything went ok and i proceed to flash the another SBF this time (I was trying the JB4.1.2 BR Retail). Since I've heard one of the latest KK kernel was the DE I decided to give it a try. Downloaded it from the official motorola page and flahed it via fastboot. This time I didn't stayed on front of PC because I needed some coffee! When I cam back, everything seemed to be ok since there was a message at the end saying so.
Phone rebooted and JB4.1.2 was installed, basic configurations done and OTA downloaded through the cell phone. Installation failed again! With this OTA fail already in mind, I previously downloaded the DE OTA from a post here and had it downloaded already to the external SD card. Installed JB custom recovery and proceed to flash the OTA...it failed again!
There was almost 40 hours without sleeping so my brain didn't allowed me to keep going.
After 10 hours of rest, I was back to keep fighting....and there comes the next type of errors:
Error category 1 +2 +3+4
1+2+3 because after several attempts on the whole process, the error 1 popped up some times, there was, as well, a new error (error 2) while flashing the OTA via custom recovery (please see the attached screen shot).
Finally, the errors 3+4 (actually the error number 3 is the one I'm concerned the most about). Its sort of a bootloader menu error message and the error number 4 shows up while trying to flash SBF and or Custom recoveries and they are as follow
Bootloader menu error message:
10.98(*) (sha-5b608bc, 2012-11-23 19:48:44)
eMMC Info: Size16GB
Device is UNLOCKED. status code: 3
Fastboot reason: Boot menu selected
USB Connected
downgraded security version
Update gpt_main version failed
Pre flash validation failed for gpt
Fastboot error messages while trying to flash SBFs and or custom recoveries
<bootloader> Variable not supported!
target max-download-size: 30MB
FAILURED (remote failure)
My conclusions/doubts are as follows:
1.Does that internal SD format has something to do with the bootloader menu errors message? I feel it has started to show up after I did it...maybe it's just coincidence though!
2.The .xml editing part still making me feel something suspicious about the Fastboot error messages.
3.Does that Epinters CM11 KK 4.4.4 Kernel 3.0.101-11512-g9511901 has something to do with that scaring Bootloader error message about downgrading?
...or is it just me being a noob?!?
However, If you came this far, congrats! I really truly respect your commitment to help people and your passion for computer/programming/Android related things!
People like this are the real responsible for bringing men out of caves all the way through the days we live in and as far as to reach the moon!
Now if you help me to get out of this and reach my goal of having KK4.4.4 official DE(or any newest other one which works where I live), rooted, unlocked BL, I'll be more than happy to ask for your permission to invite you to some beers!
Cheers!
RMarques said:
Hey there fellas,
Being a part time/spare time "mod wanna be", I've successfully modded different cell phones every now and then.
Lately I bought, 2nd hand, a XT925 running as it was in the attached screen shot + unlocked BL, rooted and CWMR touch 6.0.4.4.
Since the phone was rebooting itself kinda often, since I've been told that Epinters builds was JBBL based and also based on the phone info 3.0.x Kernel, I thought it was ok to flash a stock ROM and after that, upgrade to KK via OTA.
I've flashed the JB 4.1.2 BR Retail via fastboot and everything went ok. I let it boot, ran through configurations and just made myself sure that basic options were working ok. The OTA pops up, I downloaded it and proceed to install...an error pops up while it was somewhere around 25-30% of the flashing process.
I talked to the previous owner and he said that he went to CM because the cell never was able to install OTAs, there was always errors on the installation process.
With that in mind, I proceed to research some tutorials about alternative methods on how to install KK OTA.
I've found one here and another one on other forum, which was more suited to my needs since I'm at Brazil. Both are suggesting the same method:
Requirements:
1.Stock/unmodified JB4.1.2
2.Stock recovery
3.Unrooted
4.Bootloader unlocked
Since I met all the requirements, I proceeded to give it a try.
The next steps was:
1.Download a JB custom recovery and flash it via fastboot
2.Correct OTA installed on the external SD card
3.Install the OTA via custom recovery
4.install KK custom recovery
5.Root
Steps 1 and 2 were ok but again, while attempting to flash the OTA there was errors. Since Ive tried the whole process several times with different files, doing MD5 checksums, with different custom recoveries, I may divide the errors in 2 separate categories:
Error category 1:
While verifying current system, different .apks has unexpected contents. Status 7 as the final status error.
Since I was battling with this for 36 hours non stop, just before going to have some sleep, I decided to format internal SD since I thought maybe there was some leftovers from previous installations.
Apparently everything went ok and i proceed to flash the another SBF this time (I was trying the JB4.1.2 BR Retail). Since I've heard one of the latest KK kernel was the DE I decided to give it a try. Downloaded it from the official motorola page and flahed it via fastboot. This time I didn't stayed on front of PC because I needed some coffee! When I cam back, everything seemed to be ok since there was a message at the end saying so.
Phone rebooted and JB4.1.2 was installed, basic configurations done and OTA downloaded through the cell phone. Installation failed again! With this OTA fail already in mind, I previously downloaded the DE OTA from a post here and had it downloaded already to the external SD card. Installed JB custom recovery and proceed to flash the OTA...it failed again!
There was almost 40 hours without sleeping so my brain didn't allowed me to keep going.
After 10 hours of rest, I was back to keep fighting....and there comes the next type of errors:
Error category 1 +2 +3+4
1+2+3 because after several attempts on the whole process, the error 1 popped up some times, there was, as well, a new error (error 2) while flashing the OTA via custom recovery (please see the attached screen shot).
Finally, the errors 3+4 (actually the error number 3 is the one I'm concerned the most about). Its sort of a bootloader menu error message and the error number 4 shows up while trying to flash SBF and or Custom recoveries and they are as follow
Bootloader menu error message:
10.98(*) (sha-5b608bc, 2012-11-23 19:48:44)
eMMC Info: Size16GB
Device is UNLOCKED. status code: 3
Fastboot reason: Boot menu selected
USB Connected
downgraded security version
Update gpt_main version failed
Pre flash validation failed for gpt
Fastboot error messages while trying to flash SBFs and or custom recoveries
<bootloader> Variable not supported!
target max-download-size: 30MB
FAILURED (remote failure)
My conclusions/doubts are as follows:
1.Does that internal SD format has something to do with the bootloader menu errors message? I feel it has started to show up after I did it...maybe it's just coincidence though!
2.The .xml editing part still making me feel something suspicious about the Fastboot error messages.
3.Does that Epinters CM11 KK 4.4.4 Kernel 3.0.101-11512-g9511901 has something to do with that scaring Bootloader error message about downgrading?
...or is it just me being a noob?!?
However, If you came this far, congrats! I really truly respect your commitment to help people and your passion for computer/programming/Android related things!
People like this are the real responsible for bringing men out of caves all the way through the days we live in and as far as to reach the moon!
Now if you help me to get out of this and reach my goal of having KK4.4.4 official DE(or any newest other one which works where I live), rooted, unlocked BL, I'll be more than happy to ask for your permission to invite you to some beers!
Cheers!
Click to expand...
Click to collapse
thats a lot to process lol
i have a 926 not a 925 and know nothing about the specifics of updating.
however, you have and may have made some universal errors.
- when flashing with rsd a couple partitions can not be flashed equal or downgraded. these are tz/trustzone and gpt/partitioning file. therefore these lines need to be edited out of the xml unless you are upgrading. thats why you have the fastboot error, from trying to downgrade the partition table. any correct flash, updating or removing the partition and tz lines, should make this go away.
- as far as the update files. if they are true update pulls and not modified files made to flash in custom recovery, they need to be flashed in stock recovery, not cwm. without seeing the post the files came from, i cant say which you have, but the poster should have identified which they are.
there isnt much else i can comment on, but hope that helps get you on the right path.
Thanks for stopping by, reading and replying!
I'll try to touch it point by point, saying so:
1. I have flashed several times attempting to succeed on this, all of them I've used Fastboot.
2. I didn't knew, nor read nothing anywhere about the partitions that can not be flashed equal or downgraded anywhere I researched before I decided to proceed.
3. I've got what you said and I pretty much agree with that, in fact, i was pretty sure about that there was some mistake(s) in the .xml.
4. "Fastboot error, from trying to downgrade the partition table. Any correct flash, updating or removing the partition and tz lines, should make this go away." Are you talking about the following error?
"downgraded security version
Update gpt_main version failed
Pre flash validation failed for gpt"
...if so, thank God, it scared me to dead!
- As for the update files, I followed the tutorials and it was clearly stated that they was meant to be flashed using a JBBL custom recovery. http://forum.xda-developers.com/showthread.php?t=2760840&page=60 (Post #599)
Thanks again and from where I'm at atm, any kind of input helps a lot!
RMarques said:
Thanks for stopping by, reading and replying!
I'll try to touch it point by point, saying so:
1. I have flashed several times attempting to succeed on this, all of them I've used Fastboot.
2. I didn't knew, nor read nothing anywhere about the partitions that can not be flashed equal or downgraded anywhere I researched before I decided to proceed.
3. I've got what you said and I pretty much agree with that, in fact, i was pretty sure about that there was some mistake(s) in the .xml.
4. "Fastboot error, from trying to downgrade the partition table. Any correct flash, updating or removing the partition and tz lines, should make this go away." Are you talking about the following error?
"downgraded security version
Update gpt_main version failed
Pre flash validation failed for gpt"
...if so, thank God, it scared me to dead!
- As for the update files, I followed the tutorials and it was clearly stated that they was meant to be flashed using a JBBL custom recovery. http://forum.xda-developers.com/showthread.php?t=2760840&page=60 (Post #599)
Thanks again and from where I'm at atm, any kind of input helps a lot!
Click to expand...
Click to collapse
yes, that error should be fixed by any good flash.
if for some reason its not, get "mfastboot" and flash the most current version you have ever had on the phone and *** flash the partition file first, followed by the rest of the files. mfastboot can write equal partition files. if the partition file flash fails, you dont have the newest one.
hopefully re-flashing without the partition file works, then you wont need to mess with mfastboot.
looks like that is a modified ota file as you stated, sorry but i cant help with whatever the issue is with that part.
Solved!
http://forum.xda-developers.com/showthread.php?p=56598858
Sent from my Razr HD/Unlocked KKBL/TWRP2.8.1.0/Latest CM11 M11 Nightly/ART Runtime
I've got an A700 that appears semi bricked. I can use fastboot to install a recover, and then use the recovery to install, say, OmniROM, but then I get freespace errors on the data partition when trying to install GAPPS, but otherwise OmniROM boots and runs seemingly fine. Wanting to start over from scratch so I can have Google Apps access, I try to install the stock ROM from Acer's site via the update.zip file, but TWRP and CWM both error out with an Error 7 (product name mismatch), so I edit the update script and remove the first line/product name check and get an Error 6 (Unsure why)...
My next course of action was to flash the stock recovery, so I could then hopefully flash the stock ROM, but I can't seem to find a live link. Can anyone help, or suggest another course of action?
Thanks
Did you look here : http://forum.xda-developers.com/iconia-a700-a510/general/tools-firmware-collection-tools-t3002768 ?
Shreps said:
Did you look here : http://forum.xda-developers.com/iconia-a700-a510/general/tools-firmware-collection-tools-t3002768 ?
Click to expand...
Click to collapse
Thanks, but I don't see any stock recovery files in there. Am I missing it? Also, all the stock files I do see are EMEA (Europe, Middle East, Africa), I'm pretty sure I would need the PA (Pan America) files since it was purchased in the US? Not sure if there's a difference
Hello guys,
I have a p5113 tablet that i have been having trouble with. I have tried flashing like 5 different roms and they all boot loop. I think its because I am using an old recovery (Device Specific TWRP 3.0.0-0) the problem is only the old recoveries are working for me. When i flash the latest common TWRP (3.0.3-0) Wiping gets stuck at updating partition details, it wont install any roms it stays at "detected filesystem ext4", and if I try to reset the tablet through TWRP menu it wont do anything. When I use the old recoveries it flashes and wipes fine. When i flash stock rom through odin, the system works fine. I have tried different versions of the latest twrp but to no avail. Thank you in advance for your help.
EDIT: I finally have a custom rom working on this tablet, it is Dhollmen stock 4.2.2 with GT-P5110_PhilZ-Touch-Recovery_6.59.2. recovery, device specific TWRP 3.0.0-0 would give me error 7. Im very happy but I would like to get Marshmallow on this tablet if anyone can help with that.
Install the 3.0.3-0 common TWRP, then try to format data (Wipe ->Format Data-> type yes). Reboot recovery once and then perform a wipe of all partitions (Wipe->Advanced Wipe-> select everything). If you get stuck at "updating partition details..." just wait. It could take as long as five minutes some times to get unstuck.
This is the link for the thread of Slim6, the mm rom I recommend by Andi:
https://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified/rom-slim6-t3414798/page1
And this is an aosp mm rom also by Andi, try it if above fails
http://builds.unlegacy-android.org/aosp-6.0
Flash both with TWRP 3.0.3-0
If problems continue, post the recovery log (you can find it after reboot at /cache/recovery/ )
landetta said:
Hello guys,
I have a p5113 tablet that i have been having trouble with. I have tried flashing like 5 different roms and they all boot loop. I think its because I am using an old recovery (Device Specific TWRP 3.0.0-0) the problem is only the old recoveries are working for me. When i flash the latest common TWRP (3.0.3-0) Wiping gets stuck at updating partition details, it wont install any roms it stays at "detected filesystem ext4", and if I try to reset the tablet through TWRP menu it wont do anything. When I use the old recoveries it flashes and wipes fine. When i flash stock rom through odin, the system works fine. I have tried different versions of the latest twrp but to no avail. Thank you in advance for your help.
EDIT: I finally have a custom rom working on this tablet, it is Dhollmen stock 4.2.2 with GT-P5110_PhilZ-Touch-Recovery_6.59.2. recovery, device specific TWRP 3.0.0-0 would give me error 7. Im very happy but I would like to get Marshmallow on this tablet if anyone can help with that.
Click to expand...
Click to collapse
have you used the twrp on the http://andi34.github.io/ website? and roms compiled before 3/22/16 dont flash with common twrp when I updated twrp I had downloaded the zip and went into twrp to flash it I havent used a pc at all to install twrp and root . so I just put the zip on my sd card and it updated it did you update twrp with odin?
Thank you for your reply,
Yes I used the recoveries from Android Andi, and yes I have installed recoveries in zip form through recovery and Odin. Unfortunately neither have worked. I did use the latest recoveries when I tried to install the newer roms but it just gets stuck, I can't even make nandroid backups it also gets stuck with the newer recoveries.
Edit:
@ john99ap Sorry i just got home, I tried what you said but it just got stuck at both wipes, I waited 10 mins but a no-go. I found the logs, I couldn't paste them in here because it exceeded character length so I put it in pastebin. I didn't know which log to use so I am giving you the ones that I think are more relevant
Log:
pastebin/gpWgBEm7
Last_log:
pastebin/12uLYgwS
Last_log.10
pastebin/asePpLBa
Thank you guys again for your help!
landetta said:
Log:
pastebin/gpWgBEm7
Last_log:
pastebin/12uLYgwS
Last_log.10
pastebin/asePpLBa
Thank you guys again for your help!
Click to expand...
Click to collapse
I can't find anything in these logs
I need the log in which you try to install the zip file.
Try this:
-Install TWRP 3.0.3-0 (if it's not already there)
-Reboot and delete all recovery logs you can find
-Install the zip without doing anything else before or after so that the log is as clean as possible
-Post any log you find
PS: you could upload logs in your reply by hitting the button with a stapler on the bottom left corner
Thanks for your reply, sorry about the old logs, here are the new ones like you requested. Hopefully you find something in these new ones. Thanks again for all your help BTW I don't have any staples in my advanced reply so I had to use Pastebin again sorry. I think its because of my low post count.
pastebin/UcntGLTZ
pastebin/Fq8V7WUf
PS: Not even the reboot button works on 3.0.3-0.
Sorry but I can't find anything in these logs either. Maybe it's my fault since I 'm not an expert
At your first post you said device specific twrp gives you error 7. This is caused by a safety check in which your recovery checks if your device is compatible with the rom. In your case, it must be a mistake of the recovery (I had the same issue with my p3110 device specific twrp). So you could just remove the safety check.
Here's how to do it:
- Go to the zip you want to install and find the file /META-INF/com/google/android/updater-script
-Edit it with a text editor and remove the first line (it begins with asserts and ends at the first semicolon)
-Install the zip
Good luck!
john99ap said:
Sorry but I can't find anything in these logs either. Maybe it's my fault since I 'm not an expert
At your first post you said device specific twrp gives you error 7. This is caused by a safety check in which your recovery checks if your device is compatible with the rom. In your case, it must be a mistake of the recovery (I had the same issue with my p3110 device specific twrp). So you could just remove the safety check.
Here's how to do it:
- Go to the zip you want to install and find the file /META-INF/com/google/android/updater-script
-Edit it with a text editor and remove the first line (it begins with asserts and ends at the first semicolon)
-Install the zip
Good luck!
Click to expand...
Click to collapse
Awe thanks anyways dude, I really appreciate you trying. One last thing, on Andi's website he say that device specific 3.0.0-0 recovery should work to flash the latest roms. If anyone can confirm this maybe I can get the new roms working on it. Thanks again for all your help john99ap :good:
I made this zip courtesy of SuperR's kitchen free version. I look forward to playing with the donate version.
This is a %100 stock ROM which also will flash the stock recovery. I had some difficulty on first setup. It is highly recommended you flash a custom kernel over this ROM. If you use the stock kernel you may get the secure startup screen. In order to get past this you have to flash stock recovery and let the phone reset.
ALSO REMEMBER WHEN YOU ENTER THE WRONG PASSWORD ON THE SECURE STARTUP SCREEN IT MAY WIPE YOUR SD CARD AS WELL!!! I always end up corrupting my SD somehow when messing with my daily driver
Edit:. It looks like flashing a custom kernel gets rid of all of the above problems. I wanted to try a completely stock experience.
Downloads for : LG V20 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
If anyone is still using my old ROM YOU MUST STOP USING IT! I have identified multiple problems with it including boot failures excesive heat and other glitches most likely due to the partitions being different. I took the time to verify that most of the partitions from NotYetADev's ROM are different from mine. Unfortunately I'm not smart enough yet to be able to build my own update binary at this time. However I have developed a hacky work around. I've essentially just repacked NotYetADev's zip with my own ROM images I dumped from my 100% Stock VS995 running 20d. I haven't tried dailey driving the ROM from the repacked zip file alone. It might run just fine. However I noticed the build.prop was showing VS99520c still. So just to be safe I built the boot and system image Zip in superR's kitchen to flash over NotYetADev's.
Required Files:
VS99520d OREO Prerequisites.zip
vs9520dRAW2.zip
no-verity-opt-encrypt-6.0.zip By abdyasar
Magisk 24.3 By topjohnwu
VS995_1.0-ezV2020.zip By ezzony
Recomended Files:
alpha-modedui_overlay_dark.zip By I95swervin
Alpha-moddedui-IOSsignal-RoundedRecent.zip By I95swervin
Safetynet-fix-v2.3.1.zip By kdrag0n
Auto_Debloat_Lgv20_msm8996_Oreo_v8.8s_flashable.zip AKA Leamon Drop By Darnrain1
Troubleshooting files:
Unmodified Stock LG Recovery Image
If you aren't running Verizon firmware you MUST do a factory reset. You might be able to get away with dirty flashing over VS99520c if you are running NotYetADev's ROM. If you are running Leamon Drop I think you are going to have to factory reset also. I always wipe cache and Dalvik when presented the opertunity.
First tap install VS99520d OREO Prerequisites.zip then Add more Zips.
Next select Magisk 24.3.zip then Swipe to confirm Flash.
Boot System. If you see static boot that's good. When you get to the setup screen shutdown. I swaped out NotYetADev's stock recovery image with a VS995 TWRP recovery image. But you may want to boot into fastboot and flash a TWRP recovery image just to be sure.
Once back in TWRP Format Data
reboot recovery
Wipe everything but SD card and USB OTG BE CAREFUL!
install VS99520dRAW2.zip
add no-verity-opt-encrypt-6.0.zip
add Magisk 24.3
When done reboot system and see if it boots. If it doesn't boot or there are services crashing you may need to flash stock recovery image via fastboot and run it. You could also try the entire flashing process again. Whenever I run stock recovery I always remove the SD card before booting just in case.
If the system Boots I would install EZ V2020 kernel next. Also the easiest way to install the corect Magisk app is to rename the magisk.zip to magisk.apk and install it from your file browser. I would ask you hold off on running the Lemon Drop debloat script to help me test this ROM. I know I shouldn't have mentioned it but it's so awsome!
I thought I figured out a way to get around the limitations of the free version of SuperR's Kitchen. However after testing the files I've uploaded I notice the build number is showing SuperR instead of "OPR1.170623.032". It's probably harmless but considering I donated I feel I shouldn't have it in my ROM. The problem is that the newer donate version of the kitchen doesn't produce a ROM that boots. You can either edit your build.prop yourself for now. Perhaps later I'll fix it and upload a stock build.prop.
Thanks for posting this, will give it a try and see how it compares against Alpha O rom which is on 20c.
This installed fine and was able to reboot back into TWRP, wipe data, and re-install the ezV2020 kernel. It booted into standard setup, not the secure startup that you mentioned. Going to apply the following and then check performance: https://forum.xda-developers.com/t/...hones-volte-and-wifi-calling-working.4432865/
@Whosondephone or @nickb2b hoping one of you can help me out here as I can't figure out what went wrong or how to progress on this.
I have a VS995 that was running 7.0 with Magisk root and using the MK2000 kernel and TWRP. I loaded this zip and after boot I got the decryption error mentioned in the OP so I went ahead and wiped data.
Upon reboot into the OS I had a total static screen, which IIRC is due to no longer having a custom ROM. Luckily, I was still able to adb shell in and reboot to recovery but TWRP was no longer working. It would boot to TWRP splash screen but then would just continue on and I could never get into TWRP.
After finally getting the device to be detected by my Win 10 as an ADB device (the standard driver packages didn't work by themselves and I manually needed to set the device as an ADB device in device manager), I was able to fastboot flash the latest TWRP.
Then I was able to flash a custom kernel (tried both the ev2020 kernel linked above and the latest oreo MK2000). The static was gone and I got the Verizon Hello start screen.
After 30 seconds or so on the Verizon screen it brings me to screen that says
"Decryption Unsuccessful
The password you entered is correct, but unfortunately your data is corrupt.
To resume using your phone you need to perform a factory reset....."
Then there is a "reset phone" button that when I click on will bring me to TWRP.
I have tried to wipe data, factory reset, reset data using the stock recovery, etc all multiple times.
I keep getting this upon boot.
I tried to revert to the official latest KDZ using uppercut but constantly get "spc code does not match" at 4% of load.
Please let me know if you can assist.
EDIT: I've been able to reload the 7 KDZ and am working on re-unlock with dirtysanta. Once that is done I'd like to try this again. Any advice on how to get it to work?
Oh God. I'm currently working tirelessly on getting the definitive version of this ROM going.
After you re-dirty Santa and get rid of secure startup "decryption unsuccessful" I recommend flashing a full Oreo ROM Like alpha Omega rom. Google "where are the alpha omega rom threads" to find it. It has been brought to my attention that developers flash additional partitions on the vs995 variant. I have made a zip with the required partitions but I'm not ready to release it. When you install Alpha Omega I would recommend selecting no kernel. Then flash EZv2020 kernel separately after. You could use mk2000 also however many users including myself think it has problems. Flashing a custom kernel should get rid of the secure boot issue and static boot.
Reboot and setup.
Then dirty flash my ROM over the alpha Omega install. Flash custom kernel again. I flash magic just for good measure. I'll come back with the version number later. I have problems with newer versions of magisk.
As a side note if you see the static boot on a v20 you know you're in good shape. That is a side effect of the dirty Santa root method on the stock kernel. It can easily be removed by covering the proximity sensor, after the phone has booted, making sure the screen turns black, second screen too. When you release your thumb on the proximity sensor the screen will be normal.
if you're still getting the secure startup screen, it's hacky. I tried so many troubleshooting steps I don't remember exactly which one worked. I believe I got past it by flashing the stock recovery from a backup. All the stock recovery does is once it loads is immediately factory reset the phone, probably some other proprietary nonsense too. When you run the stock recovery all you see is multiple rings white red blue green on top of each other. You have no options for anything.
I REPEAT!!! POWER DOWN YOUR PHONE AND REMOVE THE SD CARD BEFORE RESETTING. THE SECURE STARTUP RESET THINGY ERASES THE SD CARD TOO.
I have a backup of it from a dump I did. I'm not sure if the dirty Santa root method makes a backup of your stock recovery, I don't think so.
Once the stock recovery completes reboot the phone and set it up. Shut down the phone. You can then run fastboot by holding volume down and plugging in USB cable. On the computer open a command prompt in your fast food directory type
fastboot flash recovery "enter TWRP image name here."
I'm not sure if this is important or not. However I cross flash all my V20'S with US996 stock firmware and perform dirty Santa. Whether the phone is a VS995 or US996 Varrient.
And I'm quite sure I've had success flashing this ROM over stock Dirty Santa US996 Nougat. Success as in boot up anyways.
My daily driver is set up given the previous instructions.
Whosondephone said:
Oh God. I'm currently working tirelessly on getting the definitive version of this ROM going.
After you re-dirty Santa and get rid of secure startup "decryption unsuccessful" I recommend flashing a full Oreo ROM Like alpha Omega rom. Google "where are the alpha omega rom threads" to find it. It has been brought to my attention that developers flash additional partitions on the vs995 variant. I have made a zip with the required partitions but I'm not ready to release it. When you install Alpha Omega I would recommend selecting no kernel. Then flash EZv2020 kernel separately after. You could use mk2000 also however many users including myself think it has problems. Flashing a custom kernel should get rid of the secure boot issue and static boot.
Reboot and setup.
Then dirty flash my ROM over the alpha Omega install. Flash custom kernel again. I flash magic just for good measure. I'll come back with the version number later. I have problems with newer versions of magisk.
As a side note if you see the static boot on a v20 you know you're in good shape. That is a side effect of the dirty Santa root method on the stock kernel. It can easily be removed by covering the proximity sensor, after the phone has booted, making sure the screen turns black, second screen too. When you release your thumb on the proximity sensor the screen will be normal.
Click to expand...
Click to collapse
Thanks. I'm downloading the Alpha Omega Oreo variant A-O_VS995_20C_1.3.1.zip right now.
Android File Host shows it is going to be 8 hours to get (not a problem on my end...Fiber).
In the meantime I just finally got the VS995 Nougat dirty santa's again with SuperSU installed according to the original instructions.
I am trying to flash your ROM again right now on top since I won't be able to try the AO method until tomorrow.
P.S. I only use this phone for my kids as a "tablet" so I don't need to be on any network. I'm simply looking for a ROM that is at least 8.0+ that I can root. If you have other suggestions on a good one that might be easier to load, I'm all ears.
TraderJack said:
Thanks. I'm downloading the Alpha Omega Oreo variant A-O_VS995_20C_1.3.1.zip right now.
Android File Host shows it is going to be 8 hours to get (not a problem on my end...Fiber).
In the meantime I just finally got the VS995 Nougat dirty santa's again with SuperSU installed according to the original instructions.
I am trying to flash your ROM again right now on top since I won't be able to try the AO method until tomorrow.
P.S. I only use this phone for my kids as a "tablet" so I don't need to be on any network. I'm simply looking for a ROM that is at least 8.0+ that I can root. If you have other suggestions on a good one that might be easier to load, I'm all ears.
Click to expand...
Click to collapse
You should be more than fine with alpha Omega rom then. Nobody knows what the 20d update actually did. It has the same 2018 security patch as 20c.
The only reason I'm making this ROM is to because you cannot set up Wi-Fi calling using alpha Omega ROM.
You could also try flashing the AOUS996 Universal version. You get some interesting extras such as being able to pin recent apps, keep and from being closed. Along with more LG themes if you're into that kind of thing.
I also recommend i95swervin's dark themed UI mod and rounded recents.
You could try lineageos. The last version I tried was pie. They supposedly fixed the headphone out. And they supposedly made it easier to install. Historically you had to flash lineageos over nugget firmware. You lose always on display. The second screen is treated as a notch. I would probably still use it if it's supported VoLTE. I think they're up to Android 11 now.
TraderJack said:
Thanks. I'm downloading the Alpha Omega Oreo variant A-O_VS995_20C_1.3.1.zip right now.
Android File Host shows it is going to be 8 hours to get (not a problem on my end...Fiber).
In the meantime I just finally got the VS995 Nougat dirty santa's again with SuperSU installed according to the original instructions.
I am trying to flash your ROM again right now on top since I won't be able to try the AO method until tomorrow.
P.S. I only use this phone for my kids as a "tablet" so I don't need to be on any network. I'm simply looking for a ROM that is at least 8.0+ that I can root. If you have other suggestions on a good one that might be easier to load, I'm all ears.
Click to expand...
Click to collapse
Well I was able to get the Dirty Santa exploit with SuperSU and TWRP back on the device as it was before. I tried one more time to flash your ROM but it simply hung (on the static screen) with the Verizon logo. I let it sit for 30 minutes, tried to clear data again and then let it sit for another 30 minutes and it never booted.
I then reloaded the Nougat kdz again and went through DirtySanta a second time. However I can't get it to properly complete. I get through all the way until I have to "fastboot flash boot bootbackup.img" and then setup the device again. The final step is supposed to be rebooting to recovery and then flashing SuperSU again but this is impossible because of the static screen. You are unable to turn the screen off in TWRP so assuming it is actually booting to TWRP I can't do anything because I can't see anything. I tried to install a custom kernel at TWRP, but that is apparently overwritten on the bootbackup.img flash so again, I don't see how this is possible as it all appears to be a catch-22.
Then, I tried after reapplying the kdz again - when I was able to reboot into recovery the first time - I tried to apply the Alpha Omega Oreo Rom which finished downloading. I'm not sure if it is completing correctly or not, it looks mostlyOK, but at the end says creating some symlinks fails and exists with an error 7. But within twrp screen there are no errors. So I reboot and then it just gets stuck at the LG screen after boot.
I have no idea how it worked the first time since I have followed the guide to a T both times. I've actually re-tried about 5 times now. So I'm left with a phone that I can get 7 back on, but I can't get it properly rooted so it becomes basically useless to me.
I'm going to load back on stock KDZ again and hopefully find a solution to move forward.
I failed to mention. Don't use super SU. The goal of Dirty Santa is to unlock your bootloader. Aka give you fastboot. With fastboot you can then flash a custom recovery. That's it. Stop.
To preface we are using US996 KDZ and TWRP image regardless of which phone model you have.
Here are the steps I recommend for flashing on a VS995 or US996:
1. Using patched LG Up flash US99610f firmware KDZ
2.Download TWRP 3.7.0_9 for US996
3.Place the TWRP image in your fastboot folder. Open the step three file in notepad and replace all TWRP images with the download one. Example:
Fastboot flash recovery TWRP3.7.0_9.img
4.Save and run step 3. Or just enter it manually.
5.in TWRP you format data.
6.reboot recovery
7.install my zip
8.install ezv2020 VS995 kernel if using my ROM.
Whosondephone said:
I failed to mention. Don't use super SU. The goal of Dirty Santa is to unlock your bootloader. Aka give you fastboot. With fastboot you can then flash a custom recovery. That's it. Stop.
Here are the steps I recommend for flashing on a VS995 or US996:
1. Using patched LG Up flash US99610f firmware KDZ
2.Download TWRP 3.7.0_9 for US996
3.Place the TWRP image in your fastboot folder. Open the step three file in notepad and replace all TWRP images with the download one. Example:
Fastboot flash recovery TWRP3.7.0_9.img
4.Save and run step 3. Or just enter it manually.
5.in TWRP you format data.
6.reboot recovery
7.install my zip
8.install ezv2020 VS995 kernel if using my ROM.
Click to expand...
Click to collapse
Thanks. I actually found an archive I put together over 4 years ago on the process that worked best for me.
Using it I was able to use dirtysanta and then put the latest Magisk (well v.23), the latest BTTF for 7.0 and TWRP 3.7.
I'm confident that with this procedure I can recover to this point again without a problem.
Tomorrow I will try the procedure you listed above, however since I am already on the 13A 7.0 VS995 version, is there a way I should try it from here? After all, if it fails I can just reload the kdz from 996 and go from there.
One other question that has me kind of scratching my head. I have written in my archive - and the dirtysanta instructions say that after step 2:
"Verizon Users Vibrator will be constantly going off, until the whole process is complete (Past Android Setup Wizard)."
And I seem to recall that this in fact did happen years ago when I did this process, but when I go through it all again I never have the vibration issue. I'm reading something that makes is sound like maybe 13A doesn't have that problem, but the archive I wrote has me loading 13A *and* mentions the vibration - meaning I think I did get it previously on 13A.
Any ideas why I don't seem to have any issue with vibration anymore when doing this process from the start of KDZ load?
Honestly I wish I knew. Someone has mentioned to me that there are a set of instructions out there to fix the vibration issue. As I'm sure you can relate, I've always just been happy enough when the thing works. For whatever reason I did those instructions on my new US996 and the Vibration issue was gone. Only thing I can say is the US996 firmware doesn't vibrate at all on power up or power off. However the VS995 does.
I'll also add that I flashed the partitions zip I recently added to the first post to my new US996. I think before flashing the system. Probably doesn't matter which order though.
In the past when switching from a US996 firmware to a VS995 firmware the vibration comes back. I was shocked when it did not this time.
Edit: to clarify it does vibrate on startup like normal. Short vibration. In other words it gets the signal to shut off!
I've also noticed there are at least two boot corruption screens. The older one from Nougat with less words and a better rhyming scheme. Then I think AO ROM flashes a newer one with Oreo that has more words and no rhyming. I also throw out there that I swear at some point early on in my rooting learning phase there was a third one that mentioned press the power button to skip this message. I might be hallucinating however I remember being so thankful for it. And I had no idea what caused it. This was at a time when I had no idea what I was doing.
Whosondephone said:
I failed to mention. Don't use super SU. The goal of Dirty Santa is to unlock your bootloader. Aka give you fastboot. With fastboot you can then flash a custom recovery. That's it. Stop.
To preface we are using US996 KDZ and TWRP image regardless of which phone model you have.
Here are the steps I recommend for flashing on a VS995 or US996:
1. Using patched LG Up flash US99610f firmware KDZ
2.Download TWRP 3.7.0_9 for US996
3.Place the TWRP image in your fastboot folder. Open the step three file in notepad and replace all TWRP images with the download one. Example:
Fastboot flash recovery TWRP3.7.0_9.img
4.Save and run step 3. Or just enter it manually.
5.in TWRP you format data.
6.reboot recovery
7.install my zip
8.install ezv2020 VS995 kernel if using my ROM.
Click to expand...
Click to collapse
I can't get this process to work, not even the first step.
I downloaded the US99610f kdz but when I try to use UPPERCUT to flash it tells me it can't because it is a 996 and I'm on 995 (in slightly different terms). I tried both the refresh and upgrade options.
I notice you said using "patched LG Up" which is what I believed Uppercut was doing, but just to make sure I searched and also found this thread:
LGUP 1.16.3 Patched Setup installer - w/ LGMobile drivers and Common_DLL
Hey guys, i always had issues with getting LGUP to work correctly, so therefore i just made an installer that installs everything in one package. LGUP_Common.dll should work for devices above the LG G6. For any problems with it, don't hesitate to...
forum.xda-developers.com
It used a newer version of LG Up which had some more options, but basic error messages were the same.
So I'm not sure how you are flashing 996 onto this device if it doesn't already have a 996 ROM.
EDIT: Update, I searched around and found this thread:
[GUIDE][UNBRICK] Patch LGUP to unlock features & unbrick V20 (Variant mismatch fix)
[GUIDE][UNBRICK] Patch LGUP to unlock features & unbrick V20 (Variant mismatch fix) Team After a flash gone very bad, I got myself a brick with a locked bootloader & wrong viariant in LGUP [US996-->H990ds]. In my attempt to recover I tried...
forum.xda-developers.com
I assume it is the patched LGUP you were talking about? I installed it and it successfully detects my device, but I continue to get this same error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm going to try to flash the Alpha Omega Rom again and see if I can get that working.
I can't believe this phone was old 4 years ago and still today we don't have a clear cut way to install a rooted Oreo :/
If you have any more ideas I'm open to them as I doubt this AO install will work.
EDIT: Going through some more threads it seems I need to use the Partition DL option to cross-flash. I am trying that selecting all partitions. Hope I don't make my phone unrecoverable...I'll report back if I get through your procedure.
Well this just continues to be a sh** show. I was able to successfully flash the US996 kdz using the partition DL option.
After the first boot my ABH screen was gone and the boot logo was different but it booted up right into a "Secure start-up" error and I had to enter my password in incorrectly 30 times (with delays) to proceed. So that was 15+ minutes just there.
Actually, it was pretty weird because at about attempt 15 I started writing some of this response and I was kind of absent mindedly just typing in a password every 30 seconds when it would let me. At attempt 4 or 5 when I typed in a couple of random characters, instead of telling me it was invalid, it actually rebooted into the setup. That seems kind of amazing that I could have randomly guessed an encryption password by typing in a couple of characters?
Anyway, I had no other option other than going through almost 30 times because the key presses to try to get into recovery didn't work (not even stock recovery) and the bootloader is relocked so I could not just go and run step 3 again to re-flash twrp as you instructed.
I'm not sure what I am missing in your instructions, but it doesn't seem possible to do them without running a full exploit again after going to US996. And, I don't know which exploit that would be. It seems there is a dirtyelf exploit for the US996 model (?), but I'm not about to try that on my actual 995 without knowing for sure what to do.
I've confirmed I can get back into download mode, so I *hope* I can recover back to my 995 KDZ and move on if need be.
In the meantime I'm going to keep it on what is currently the US996 kdz you told me to flash which appears currently to be in a completely locked state.
If you can provide some precise instructions on how to move on from here it would be appreciated.
You can run the dirty Santa exploit on us996 firmware. Just like you would on VS995 firmware. Just once you get into TWRP your done. You don't need to follow any more steps for the dirty Santa procedure if you're going to flash a ROM.
Yes there are many different types of LG up. The one I'm using has the dump option. I am pretty sure I was able to select upgrade on mine and it doesn't give me any issues with the wrong type of phone.
Whenever you flash a kdz you return to stock/locked. At least as much as possible. I thought you'd have to deal with that secure boot. Somehow.
The best guide I follow to this day is "High On Android V20 root". It's not 100% accurate, and is slightly outdated but it it the best.
I realize I failed to mention to dirty Santa before the step 3. If you need extremely detailed instructions I can't give them until the weekend when I'm around my PC. I can give thorough instructions perhaps sometime today.
Whosondephone said:
You can run the dirty Santa exploit on us996 firmware. Just like you would on VS995 firmware. Just once you get into TWRP your done. You don't need to follow any more steps for the dirty Santa procedure if you're going to flash a ROM.
Yes there are many different types of LG up. The one I'm using has the dump option. I am pretty sure I was able to select upgrade on mine and it doesn't give me any issues with the wrong type of phone.
Whenever you flash a kdz you return to stock/locked. At least as much as possible. I thought you'd have to deal with that secure boot. Somehow.
The best guide I follow to this day is "High On Android V20 root". It's not 100% accurate, and is slightly outdated but it it the best.
I realize I failed to mention to dirty Santa before the step 3. If you need extremely detailed instructions I can't give them until the weekend when I'm around my PC. I can give thorough instructions perhaps sometime today.
Click to expand...
Click to collapse
Yes, I found this thread on reddit which is the only indication I have found anywhere that stated dirtysanta was ok to run on the us996 firmware. So I did that and continued on with the process until step 3 and booted into TWRP.
Then I canceled out of the password prompt, wiped data and flashed your ROM. BTW it seemed to take almost 2x longer than it has in the past (maybe like 12-14 minutes instead of like 6-8). It seemed to go ok until the end when I got this:
Code:
*********************
Magisk 24.3 Installer
*********************
cannot mount /system
-unmounting partitions
mount: failed to mount /dev/block/platform/soc/624000.ufshc/by-name/system at /system: Invalid argument
VS99520d 3 Installed
script succeeded: result was [VS99520d 3 Installed]
Updating partition details...
Failed to moun '/system' (Invalid Argument)
...done
I tried to flash the us995 ev kernel but it said that my phone was a 996. Then at the bottom it said something like "You are on and this is for Oreo." Those multiple spaces are there because it was actually blank, as if it couldn't read the variable.
I tried to reboot to system anyway and it just rebooted to the bootloader.
I have now rebooted into TWRP, cleared data again for good measure, wiped my SD card, am recopying your ZIP and will try to install one more time just because.
I don't see it working though, so I don't think this procedure is a success.
If you are using an LGUP procedure that allows you to do an "upgrade" instead of a Partition DL maybe something is different with your setup. You haven't been really descriptive in most of your steps and in the OP this seemed more or less like a drop in on stock and flash, which it clearly has turned out not to be. I do appreciate the help so if you have a more specific set of instructions that has definitely worked for you I'll give it another go.
P.S. "High On Android V20 root" doesn't have a single hit on Google.
P.P.S: This might be what you were referring to?
How to Root LG V20! [AT&T/Sprint/Verizon/Korean] | HighOnAndroid.com
highonandroid.com
Not to sound ungrateful - because I really do appreciate the help and if it gets me there in the end it should be worth it (assuming I can get there within the next day because I've already spend close to 10 hours on this), but you really need to be a bit more descriptive in your instructions. Especially As someone releasing files for other's uses without appropriate background and caveats can lead to headaches, wasted time, and possibly bricked devices. I know everything here is use at your own risk, but I assume you would actually want people to use your stuff if you are bothering sharing in the first place.
Anytime you have to format data in TWRP. You need to reboot recovery. Otherwise the partitions are not visible to TWRP.
Whosondephone said:
Anytime you have to format data in TWRP. You need to reboot recovery. Otherwise the partitions are not visible to TWRP.
Click to expand...
Click to collapse
I definitely did do a reboot recovery in TWRP after clearing the data the first go. I didn't know it was required, but I followed your instructions to do it anyway. I am still re-copying your zip, but once that is done I will clear data and reboot recovery once more before I try the re-flash.