Firstly im not new to android and certainly not new to unlocking/rooting/flashing custom ROMs. However, I might as well have been considering the rookie mistakes I made last night. A very good friend of mine has a Moto Razr HD and asked me to get CM11 on there after seeing it on my Nexus 5. No problem. Yeah right.
Heres what has transpired. It is XT925 and I unlocked it via the official Moto Unlock website. No troubles there. Then instead of rooting I flashed TWRP via fastboot. No problem. Boot into recovery, FAILED to make nandroid! I was tired and rushed and just totally skipped it. Such a rookie mistake. Then I attempted to flash CM11. Wiped, install and it fails. Tried sideloading root, and then the ROM still fails. This is the error I keep getting
set_metadata_recursive: some changes failed
E: Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/cm-11-20131230-NIGHTLY
Updating partition details.....
Failed
I would quite sincerely appreciate any help that could be had here. I have still working twrp, and I can still see all the data on the sdcard. Oh, and I did try another ROM. Same thing happens
brunswick000 said:
Firstly im not new to android and certainly not new to unlocking/rooting/flashing custom ROMs. However, I might as well have been considering the rookie mistakes I made last night. A very good friend of mine has a Moto Razr HD and asked me to get CM11 on there after seeing it on my Nexus 5. No problem. Yeah right.
Heres what has transpired. It is XT925 and I unlocked it via the official Moto Unlock website. No troubles there. Then instead of rooting I flashed TWRP via fastboot. No problem. Boot into recovery, FAILED to make nandroid! I was tired and rushed and just totally skipped it. Such a rookie mistake. Then I attempted to flash CM11. Wiped, install and it fails. Tried sideloading root, and then the ROM still fails. This is the error I keep getting
set_metadata_recursive: some changes failed
E: Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/cm-11-20131230-NIGHTLY
Updating partition details.....
Failed
I would quite sincerely appreciate any help that could be had here. I have still working twrp, and I can still see all the data on the sdcard. Oh, and I did try another ROM. Same thing happens
Click to expand...
Click to collapse
Ok I fixed my own problem. How you ask. I did some reading. Sorry to have cluttered up the forum folks. Just had to install the latest CM instead of TWRP. Fully functional phone again. But better.....
I have a Nexus 5 running stock Lollipop (5.0). My phone is rooted and has CWM Recovery installed. I've tried to update OTA to 5.0.1 twice now. Both time, it has downloaded the update and rebooted as usual. Then CWM Recovery prompts me to install the update. After hitting "Yes" it appears to install the update and then informs me that root may have been lost. I've tried saying both "yes" and "no" to fixing that. In both cases, I've retained root, but my phone remains at 5.0 instead of 5.0.1.
From my limited rooting knowledge, I can see flashing the factory image would be the most straightforward way to updating, but obviously that would wipe my phone. Titanium can only back up so much. Plus I want a simpler way to do this in the future. To me, it seems another solution would be to revert to the stock recovery and have that install the update. However, I don't know how to revert to the factory recovery without flashing the factory image. All of that being said, what is the best way to OTA with a stock ROM but a custom recovery?
KomradeNikolai said:
I have a Nexus 5 running stock Lollipop (5.0). My phone is rooted and has CWM Recovery installed. I've tried to update OTA to 5.0.1 twice now. Both time, it has downloaded the update and rebooted as usual. Then CWM Recovery prompts me to install the update. After hitting "Yes" it appears to install the update and then informs me that root may have been lost. I've tried saying both "yes" and "no" to fixing that. In both cases, I've retained root, but my phone remains at 5.0 instead of 5.0.1.
From my limited rooting knowledge, I can see flashing the factory image would be the most straightforward way to updating, but obviously that would wipe my phone. Titanium can only back up so much. Plus I want a simpler way to do this in the future. To me, it seems another solution would be to revert to the stock recovery and have that install the update. However, I don't know how to revert to the factory recovery without flashing the factory image. All of that being said, what is the best way to OTA with a stock ROM but a custom recovery?
Click to expand...
Click to collapse
It's been said about a million times on this forum:
You have to be stock or the OTA won't work. Stock system, stock recovery, stock kernel etc. Extract and flash files from the factory image just don't flash the userdata.img file.
Yaz75 said:
It's been said about a million times on this forum:
You have to be stock or the OTA won't work. Stock system, stock recovery, stock kernel etc. Extract and flash files from the factory image just don't flash the userdata.img file.
Click to expand...
Click to collapse
Thanks. I don't spend much time on here and I didn't see a post that gave me something concrete.
I'm currently downloading the 5.0.1 factory image from Google, but since it's such a large file and my internet is quite slow, it's going to be over an hour yet before its finished. That being said, I downloaded the .zip version of the OTA update as linked on phandroid and attempted to install it with CWM. Dispite the fact that I'm running Lollipop, I got the following error. I've shortened the name of the .zip because its quite long.
-- Installing: /sdcard/0/Download/***.zip
Finding update package...
Opening update package...
Installing update...
Package expects build fingerprint of google/hammerhead/hammerhead:5.0/LRX21O/1570415:user/release-keys or google/hammerhead/hammerhead:5.0.1/LRX22C/1602158:user/release-keys; this device has google/hammerhead/hammerhead:4.4/KRT16M/893803:user/release-keys
E:Error in /data/media/0/Download/***.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
I flashed the factory image for Android 5.0 a couple of weeks ago so I don't see any reason why it should see the KRT16M fingerprint. Any ideas?
EDIT: Never mind. Looks like this has the same effect and won't work if I'm not completely stock. I'll just wait for the factory image to download and flash that. Correct me if I'm wrong.
I am getting the same error.
KomradeNikolai said:
I'm currently downloading the 5.0.1 factory image from Google, but since it's such a large file and my internet is quite slow, it's going to be over an hour yet before its finished. That being said, I downloaded the .zip version of the OTA update as linked on phandroid and attempted to install it with CWM. Dispite the fact that I'm running Lollipop, I got the following error. I've shortened the name of the .zip because its quite long.
I flashed the factory image for Android 5.0 a couple of weeks ago so I don't see any reason why it should see the KRT16M fingerprint. Any ideas?
EDIT: Never mind. Looks like this has the same effect and won't work if I'm not completely stock. I'll just wait for the factory image to download and flash that. Correct me if I'm wrong.
Click to expand...
Click to collapse
I actually tried reverting to stock recovery using Flashify. Though it shows success but when I try to run the update, it doesn't get past the recovery mode, android with the red exclamation mark. Not sure where I am going wrong with it specially when I have been flashing since last 3 years.
Hey all,
I had a thread a while ago regarding how to get out of bootloop, now I seem to have a different issue so I wanted to make a new thread to refine the details of the problem.
These are the current settings, the only ones that work, but the rom has to be kept in airplane mode to avoid errors displaying
Phone = Huawei Honor 6 16GB (H60-L02) FDD-LTE
Bootloader = Unlocked
Recovery = CWM 6.0.5.1 exFAT
Rom = MIUI v4.9.6 (miui_hw60_slydermi_4.9.6_6c22a194a4_4.4.zip) Downloaded from the official miui website
I have tried to use the honor6 multi tool to flash different recoveries (official/stock) and none work except the above CWM version.
I have also tried to flash different roms, mainly from needrom.com and what i could download from this chinese forum
Note i have also been following tutorials in this thread
in an attempt to get back the stock rom, mainly the two sections
3 Button Restore not working and full restore method
I am unsure what step to take next, everything puts my phone into a bootloop, i would happily go back to stock recovery/rom but again they cause bootloops too
my last guess is it might have something to do with Build & Local Prop files? im not entirely sure what they are or how to use them.
thanks for any help offered!
1) Spent time to flash literally every single stock recovery offered by the Honor 6 Multi-tool,
- All EMUI 2.3 recoveries worked except for B120SP03
- Not a single EMUI 3.0 recovery worked, i tried every stable, developer and custom recovery.
2) I picked up an error in CWM, when i goto mounts and storage and try to format /cust
it gives me the following error:
Code:
Formatting /cust...
E:format_volume: make_extf4fs failed on /dev/block/platform/ff1fe000.dw
mmc0/by-name/cust
Error formatting /cust!
3) Could someone please inform me to what exactly build.prop and local.prop do, and how i can restore them? (I assume just push somewhere using adb)
I think my next plan of action is to push some of the stock prop files and then flashing their recoveries to see if that will get them to work.
Feel like a crazy person replying to my own thread but its helping me keep all information in one place and might help someone that is going through the same stuff.
After running through which recovery worked and which didnt (Still strange that some do and dont)
I flashed the highest version i could which is B121SP06 recovery using the honor 6 multi tool.
After that I downloaded a fresh copy of the B121SP06 rom, extracted the SYSTEM.img and flashed it
This booted and got me into android which is great, but its not having fun updating now.
It prompted me to update and gave me the OTA update from B121SP06 to B307SP03
I downloaded it and it reset into recovery and tried to flash it, the progress bar got less than 2% then it would stop and give me a big red exclamation mark with Software install failed! and the only option to shutdown system now
I also tried updating through the HiSuite and it again failed.
managed to install B310 with a little trickery
Using the multi tool, i performed the unbrick method with B121SP06 image files
Then i had the B310 update.app in the dlaod folder and performed the 3 button recovery method
it worked perfectly and i now have B310 on my phone, although updates are still not working, so i might have to manually download OTA's to update them.
Also recoveries that weren't working before like TWRP are.
After literally two weeks of reading thread after thread attempting to understand this , I tried to go from a sense ROM to a GPE ROM and I tried to flash the GPE firmware following Digital high's instructions here..
Things did not work out as instructed I'm afraid and that is probably due to my not understanding enough....nevertheless following DH instructions left me with repeated flash failures. Finally the following flashes got me from firmware 5.0.1- the firmware I was already on- to this:
fastboot flash zip VZWm8LfirmwareTWRP.zip - success; followed by the same ' flush" flash - again, success:
then:
fastboot flash zip 5.1_6_firmware+hboot.zip - and again another "flush" flash with success
From the way I read it we are then to reboot to bootloader and proceed further with recovery flashing the rom, blah, blah.... , however, my little android guy is overlaid with a black screen (instead of white) and he is dead. I rebooted to recovery to see if I could flash the sinless GPE ROM which is my goal in the first place (yes I realize it is a 4.4.4 but NOTHING flashes in recovery now) but now I m out of ideas. I have no workable phone and I have to get my ass to a new job in the afternoon. Can anyone help with either finishing my goal to install the sinless ROM or restore back to the adrenaline ROM I was running? I don't want to restore as I am afraid I may have altered the firmware and thus brick if I do restore...PLEASE HELP!!!! PLEASE!
right now my phone is sitting on the charger on the dead android screen. i don' dare touch it. What should i do?
Update: I am flashing digital highs GPE_5.1-multi_dh_051215.zip and I am getting a bootloader remote 24 "parsing android info fail". Does anyone know what that means or how to fix?
Update again: Figured out this needs to be flashed in recovery and not fastboot. Now I have been booting for about five minutes now. Hope I'm not bootlooped. ....
Figured it out
Got it figured out.
Mods, could you please close the thread. thanks!
kerryh said:
Got it figured out.
Mods, could you please close the thread. thanks!
Click to expand...
Click to collapse
Rather than end things with a statement that you figured it out, could you elaborate on the solution and/or describe what went wrong to cause the problem (if you happened to figure that out while finding your fix)? Someone else could come here with your same problem and you are likely poised to help them out with your newly found solution.
cntryby429 said:
Rather than end things with a statement that you figured it out, could you elaborate on the solution and/or describe what went wrong to cause the problem (if you happened to figure that out while finding your fix)? Someone else could come here with your same problem and you are likely poised to help them out with your newly found solution.
Click to expand...
Click to collapse
Believe me, I thought about trying to do just that. That's when I realized I am not sure that I totally understood what it was I did wrong in the first place. I believed the underlying issue might have been the order in which I flashed but I can't be sure because I ended up flashing files that probably shouldn't have been flashed to begin with . What I do know is that some firmware files needed to be flashed in RUU mode while others in regular fastboot and the GPE zip flashed through recovery, not regular fastboot as I thought it needed to be. And all that even being understood I still wasn't sure if I needed the firmwares with the hboot, without hboot, with or without recovery/boot .img's....
Going back and looking at my cmd window it appears the following worked in the following order:
FastbootRUU flash 5.0.1 firmware
fastboot VZWm8Lfirmware.zip
fastboot write superCID
fastbootRUU flash 5.1 firmware
reboot to hboot (dead android here) then reboot to recovery
Recovery flash GPE_5.1_muliti_dh_date.zip
Follow the promps to install and then reboot to glory...
I am still not clear on as to whether or not I can go back to my nandroid backups as those were taken on different firmwares obviously. Instinct tells me I would brick but idk...Looks like I am stuck on GPE for a while...
That probably confused more people than helped...See why I didn't post it?
kerryh said:
Believe me, I thought about trying to do just that. That's when I realized I am not sure that I totally understood what it was I did wrong in the first place. I believed the underlying issue might have been the order in which I flashed but I can't be sure because I ended up flashing files that probably shouldn't have been flashed to begin with . What I do know is that some firmware files needed to be flashed in RUU mode while others in regular fastboot and the GPE zip flashed through recovery, not regular fastboot as I thought it needed to be. And all that even being understood I still wasn't sure if I needed the firmwares with the hboot, without hboot, with or without recovery/boot .img's....
Going back and looking at my cmd window it appears the following worked in the following order:
FastbootRUU flash 5.0.1 firmware
fastboot VZWm8Lfirmware.zip
fastboot write superCID
fastbootRUU flash 5.1 firmware
reboot to hboot (dead android here) then reboot to recovery
Recovery flash GPE_5.1_muliti_dh_date.zip
Follow the promps to install and then reboot to glory...
I am still not clear on as to whether or not I can go back to my nandroid backups as those were taken on different firmwares obviously. Instinct tells me I would brick but idk...Looks like I am stuck on GPE for a while...
That probably confused more people than helped...See why I didn't post it?
Click to expand...
Click to collapse
When compared to the steps I took to flash the 6/15 build as cleanly as I could manage, here's what jumps out to me as strange or unnecessary:
-I don't know what the '5.0.1 firmware' is but I suspect it's the same as the 'VZWm8Lfirmware.zip' you flashed next. I chose to run the 5.0.1 RUU and considered that as complete of verizon 5.0.1 firmware as there is.
-I don't think that superCID has been necessary for DHs GPE for some time. I don't know that it would necessarily cause a problem but I've never gone to superCID and have had no problems
-flashing DH's carrier-agnostic 5.1 firmware is stated as optional in his OP and I think DH himself admitted a little while back that it may actually be the cause of some folks' wi-fi issues
Regarding restoring old nandroids to a system with updated firmware, I can say that each time a new official software has been released, I've flashed tigerstown's firmware-only zips alongside whatever custom rom I was running at the time with no issues. This points to a trend of successfully running roms on top of newer firmwares without issues. I know of many 5.x roms saying that you must update firmware but I've never read about a 4.x rom having issues with 5.x firmware. I don't think there's much risk of flashing a custom rom (or restoring a nandroid) from recovery that doesn't match the firmware beyond a possible bootloop.
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.