Database Info

HTC Status AT&T rom 2.14.502.2

Here it is for those who need it. I needed it to flash my phone back to stock. The update that was pushed out recently would not work on my rooted phone because I was using a UK rom when I rooted it so I need a stock ('merica) AT&T Status rom that no one seemed to have for any reason. I found the latest update on the HTC website and downloaded their installer, and that failed too. It wouldn't authorize... So into the trash InstallShield exe I went a digging and riped this out of the .cab
I used fastboot to flash the userdata.img, system.img, boot.img and recovery.img to my Status. Rebooted and did a factory reset. SUCCESS. :good:
Download Here:
http://www.mediafire.com/download.php?ncwqh41qa4ry7hi

Lucky-Casper said:
Here it is for those who need it. I needed it to flash my phone back to stock. The update that was pushed out recently would not work on my rooted phone because I was using a UK rom when I rooted it so I need a stock ('merica) AT&T Status rom that no one seemed to have for any reason. I found the latest update on the HTC website and downloaded their installer, and that failed too. It wouldn't authorize... So into the trash InstallShield exe I went a digging and riped this out of the .cab
I used fastboot to flash the userdata.img, system.img, boot.img and recovery.img to my Status. Rebooted and did a factory reset. SUCCESS. :good:
***Going to have to message me to get the download link because this wont let me post it yet.***
Click to expand...
Click to collapse
Have you found something new with this update?

bungphe said:
Have you found something new with this update?
Click to expand...
Click to collapse
Haven't seen anything new yet.
Just pulled this from HTC's website:
"HTC Status™ for AT&T ROM Update | 05.3.2012
Starting May 3rd 2012, HTC will be rolling out a system update for the HTC Status.
This update will only be available for AT&T HTC Status customers and will be sent to the device over the air. Once the release is ready, users will receive a notification on their device advising them of this update and provide instructions to receive and install it. Users can proactively check for this update by going to Home > Menu> Settings > AT&T Software Update > Check for updates.
As an alternative solution, the system update can be downloaded to a PC and manually applied to the device. See the section at the bottom of these instructions for more information.
This system update includes:
Memory allocation fixes to improve low memory issues
Data throttling fix"

So the device is unrooted again?
Did they really solve the low memory issue?
---------- Post added at 09:17 PM ---------- Previous post was at 09:12 PM ----------
Please tell me how to download and flash the rom, thanks.

slow_kknd said:
So the device is unrooted again?
Did they really solve the low memory issue?
---------- Post added at 09:17 PM ---------- Previous post was at 09:12 PM ----------
Please tell me how to download and flash the rom, thanks.
Click to expand...
Click to collapse
My device is now unrooted and I don't really see a reason to root it again. I also never ran into the low memory issue so I can not answer that question. I'll pm you the link...

thanks
Lucky-Casper said:
Here it is for those who need it. I needed it to flash my phone back to stock. The update that was pushed out recently would not work on my rooted phone because I was using a UK rom when I rooted it so I need a stock ('merica) AT&T Status rom that no one seemed to have for any reason. I found the latest update on the HTC website and downloaded their installer, and that failed too. It wouldn't authorize... So into the trash InstallShield exe I went a digging and riped this out of the .cab
I used fastboot to flash the userdata.img, system.img, boot.img and recovery.img to my Status. Rebooted and did a factory reset. SUCCESS. :good:
***Going to have to message me to get the download link because this wont let me post it yet.***
Click to expand...
Click to collapse
nice, i need to fix one, the one you downloaded is htc_status_mr_update_2.14.502.2_us.exe? and when i 7unzip, i only see:
.rsrc - folder
.data
.rdata.text
certificate and
a [0] file of 161,869 kb
so how did you got userdata, system and boot from this file?
thank you very much indeed
atv

atv said:
nice, i need to fix one, the one you downloaded is htc_status_mr_update_2.14.502.2_us.exe? and when i 7unzip, i only see:
.rsrc - folder
.data
.rdata.text
certificate and
a [0] file of 161,869 kb
so how did you got userdata, system and boot from this file?
thank you very much indeed
atv
Click to expand...
Click to collapse
First I used Universal Extractor to extract the files properly from htc_status_mr_update_2.14.502.2_us.exe, because of it being an Install Shield installer. Once it extracted the files in the correct structure I then had to use ZIP Scan on the data1.cab file because Install Shield uses its cab format and very few programs can export them correctly. Once you extract data1.cab you will have all that you need.

hi again
i really want to thank you for your help, the phone was stuck at cmw (s-on) and now its back, but i think that as your post, i should have flashed, userdata.img before, and i did it boot.img then system.img and then i could not flash the userdata.img but the phone turned on finally.
see attached
take care
wilston
atv

atv said:
i really want to thank you for your help, the phone was stuck at cmw (s-on) and now its back, but i think that as your post, i should have flashed, userdata.img before, and i did it boot.img then system.img and then i could not flash the userdata.img but the phone turned on finally.
see attached
take care
wilston
atv
Click to expand...
Click to collapse
Glad I could help my friend!

this is not ICS?

stayfidz said:
this is not ICS?
Click to expand...
Click to collapse
Of course it is! This is the official ICS from HTC, you can read it here: http://www.htc.com/www/help/android4faq/?cid=android4blog

stayfidz said:
this is not ICS?
Click to expand...
Click to collapse
Still GB.

stayfidz said:
Alex C.
1.You confused me, saying it was just a kernel!
2. I've a uk phone, can i install this US on mine?
3. CM9 is way Tard right now?
Re
Click to expand...
Click to collapse
You can install any one your phone. I have had the Asian and UK roms installed before but I would still suggest staying with your region.

[Q] [TF700] Root not working after updating Cromi-X to 4.7.0

Hello there ! Newbie here.
I've just updated my Asus TF700T to Cromi-X 4.7.0.
After the installation, I noticed that it was not rooted anymore. When opening SuperSU, an error message appears: "There is no SU binary installed and SuperSu cannot install it, it's a problem."
I tried afterwards a fresh install of Cromi-X, but the problem was still there.
Then I tried to execute the Motochopper script, which appeared as successful, but the error message is still there.
Do you know what could be the solution for this problem ? Without root, I cannot execute applications like lagfix, titanium backup and full screen, which is annoying.
Thanks in advance for your help !
And sorry for my english (french talking here !)

Sounds like the ROM didn't flash properly. Flash it again please.

sbdags said:
Sounds like the ROM didn't flash properly. Flash it again please.
Click to expand...
Click to collapse
I did, several times...
First I tried with and without the TWRP root option (after the Cromi-X install, TWRP proposes to root the tablet). Both of these two options didn't work.
Then I tried with full wipe, even the microsd (just let the Cromi-X installation archive on it). At this point, the tablet offered me the possibility of updating the supersu. I did update it, but when opening super su, the same error message appears.
I don't know what other test I can do. Any ideas ?
Thanks for your answer.

Soralito said:
I did, several times...
First I tried with and without the TWRP root option (after the Cromi-X install, TWRP proposes to root the tablet). Both of these two options didn't work.
Then I tried with full wipe, even the microsd (just let the Cromi-X installation archive on it). At this point, the tablet offered me the possibility of updating the supersu. I did update it, but when opening super su, the same error message appears.
I don't know what other test I can do. Any ideas ?
Thanks for your answer.
Click to expand...
Click to collapse
The only time I have ever seen this is when the ROM doesn't complete its flash in twrp. So it gets partially flashed.
When you flash you get the chance to save a log. It gets saved to the same folder as the zip file you flashed. Can you post it please.
Also make sure you turn on signature verification in twrp before flashing. My files are signed and this will stop it flashing a corrupted download.

sbdags said:
The only time I have ever seen this is when the ROM doesn't complete its flash in twrp. So it gets partially flashed.
When you flash you get the chance to save a log. It gets saved to the same folder as the zip file you flashed. Can you post it please.
Also make sure you turn on signature verification in twrp before flashing. My files are signed and this will stop it flashing a corrupted download.
Click to expand...
Click to collapse
Hello, I can't find any log file in the folder of my zip file... What would be the name of this log file ? Maybe I can find it somewhere else...
I have re-downloaded the rom from another source and try a new flash tonight.
Anyway thanks for your help ! (I just noticed I was talking to THE developer of Cromi-X Sir, it's an honor )

It's working now !
I flashed the rom downloaded from another mirror, and activated the zip signature verification, and it works now
Many thanks for your help, and your fabulous work on this rom.
See you soon on this forum !

Soralito said:
It's working now !
I flashed the rom downloaded from another mirror, and activated the zip signature verification, and it works now
Many thanks for your help, and your fabulous work on this rom.
See you soon on this forum !
Click to expand...
Click to collapse
You are welcome - glad you got it sorted

Hey there guys and gals. Newbie here. I've read this thread and I am having the same issue as the original poster. I don't really understand what was said here but this is my question: if I downloaded the motochopper root app to the tablet and opened it from there and did the root right from my tablet would the root take hold then? I have an Asus TF700 by the way.

Motochopper is an exe you use on your PC. You cannot install it on the tablet. And it worked only up to firmware version 10.6.1.14.8.
Read this, most of your answers should be answered...
http://forum.xda-developers.com/showthread.php?t=2688891

berndblb said:
Motochopper is an exe you use on your PC. You cannot install it on the tablet. And it worked only up to firmware version 10.6.1.14.8.
Read this, most of your answers should be answered...
http://forum.xda-developers.com/showthread.php?t=2688891
Click to expand...
Click to collapse
Should I factory reset to stock software first or just go ahead and run the new root software?
---------- Post added at 03:32 AM ---------- Previous post was at 02:47 AM ----------
reubdog30 said:
Should I factory reset to stock software first or just go ahead and run the new root software?
Click to expand...
Click to collapse
It worked!!! I'm good now. Thanks for your help!!

[Q] OTA version XNPH38R Incremental does not install

I'm prompted to install the XNPH38R Incremental with the message "System update is ready"
I tap on Install update, the phone then does it's thing, reboots and shows the splash screen logo a few seconds, then the recovery comes up and the text scrolls at lightning speed (a second or so) then the phone powers up in full and is ready for use.
When I go to my homescreen the prompt is there again for me to upgrade with the "System update is ready" message.
As such the update doesn't apply successfully. No error messages at all.
Phone is stock ROM (version 11.0-XNPH33R), only thing I did extra was to unlock the bootloader using OnePlus One Toolbox v2 (64 GB). This was done in order for me to root it. Oh, I also installed PhilZ Recovery using this same toolbox.
Any ideas why this happens?
...or suggestions as to how I can do the update?
PS, I saw that there's another tread (http://forum.xda-developers.com/oneplus-one/help/apply-ota-stock-root-franco-23r-twrp-t2900311) with a OTA update failure but that one is different as there's errors involved so I felt that the suggestions were not applicable in my case.

try manually going thru the recovery and run update file from /cache directory. and see what errors is trowing
look for cm-bacon-3628510d76-to-ac1ccf7921-signed.zip

NiTRoN69 said:
try manually going thru the recovery and run update file from /cache directory. and see what errors is trowing
look for cm-bacon-3628510d76-to-ac1ccf7921-signed.zip
Click to expand...
Click to collapse
I found the update file and tried to install in manually. The attached image shows the error message which has no meaning to me. I then cleared the cache and also the dalvik cache, booted up, checked for update, downloaded the update and install.
Same problem happened so back to square one

JJD809 said:
I found the update file and tried to install in manually. The attached image shows the error message which has no meaning to me. I then cleared the cache and also the dalvik cache, booted up, checked for update, downloaded the update and install.
Same problem happened so back to square one
Click to expand...
Click to collapse
That error message is saying that you have a modified lockscreen.
Transmitted via Bacon

timmaaa said:
That error message is saying that you have a modified lockscreen.
Transmitted via Bacon
Click to expand...
Click to collapse
Ah! that makes sense. I got the lockscreen after reading an article about it on the XDA news pages (http://www.xda-developers.com/android/dynamic-oneplus-one-lock-screen/) which took me to this thread http://forum.xda-developers.com/oneplus-one/development/dynamic-oneplus-one-lockscreen-t2890808
From here forward, how do you suggest I proceed. Is there a way to "uninstall" this lock screen or is it a matter of me doing a factory reset and starting afresh?

Unless there's a return to stock zip in the thread where you got your modified lockscreen, you'll need to start fresh.
Transmitted via Bacon

Trying to apply on a stock Oneplus One, just with root and TWRP.
Code:
asset failed: apply_patch_check("/system/app/Music2.apk","....","....")
E: Error executing updated binary in zip '/cache/cm-bacon...signed.zip
Any ideas?

timmaaa said:
Unless there's a return to stock zip in the thread where you got your modified lockscreen, you'll need to start fresh.
Transmitted via Bacon
Click to expand...
Click to collapse
hi, I have the almost the same problem, I did a factory reset but it gives me error again, what should I do

fackamato said:
Trying to apply on a stock Oneplus One, just with root and TWRP.
Code:
asset failed: apply_patch_check("/system/app/Music2.apk","....","....")
E: Error executing updated binary in zip '/cache/cm-bacon...signed.zip
Any ideas?
Click to expand...
Click to collapse
System modification on Music2.apk. Read the above advice by timmaaa.
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
shcxatter2 said:
hi, I have the almost the same problem, I did a factory reset but it gives me error again, what should I do
Click to expand...
Click to collapse
Boot on TWRP recovery and flash XNPH38R OTA zip. See here: 4. Latest OTA incremental update zip

Primokorn said:
System modification on Music2.apk. Read the above advice by timmaaa.
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
Boot on TWRP recovery and flash XNPH38R OTA zip. See here: 4. Latest OTA incremental update zip
Click to expand...
Click to collapse
that's exactly what my problem is I cannot install the update , twrp just gives me error

Use the modified XNPH38R update. You can find it in the xnph38r thread in general.
You did system modifications. By using the modified script, it won't check for those files.
This is why I say when you want to do system changes, just use a custom ROM because OTAs are going to be a headache for you if u dont intend on using what the OTA provided to you.

zephiK said:
Use the modified XNPH38R update. You can find it in the xnph38r thread in general.
You did system modifications. By using the modified script, it won't check for those files.
This is why I say when you want to do system changes, just use a custom ROM because OTAs are going to be a headache for you if u dont intend on using what the OTA provided to you.
Click to expand...
Click to collapse
I'm trying to figure out what "system modifications" I've done. It's probably freezing apps in titanium backup, as google's music always FC's on all devices, so had to be ignored.

fackamato said:
I'm trying to figure out what "system modifications" I've done. It's probably freezing apps in titanium backup, as google's music always FC's on all devices, so had to be ignored.
Click to expand...
Click to collapse
Freezing apps in TB does nothing for those system modifications. Just flash the modified script XNPH38R update and you'll be able to update. I've said this 2 times now.

zephiK said:
Freezing apps in TB does nothing for those system modifications. Just flash the modified script XNPH38R update and you'll be able to update. I've said this 2 times now.
Click to expand...
Click to collapse
Thanks. I think it only has the full one not the incremental one?

Nexus 5 with "TeamWin" failed update - and won't start again

Hello everyone.
Two hours ago I received the notification about the Android 5.0 update. I downloaded it and hit "Install". Then, "TeamWin" started, but not the update. I rebooted into System and tried to update again - but it tells me that 4.4.4 is the latest version I can get now. I'm on Build KTU84P now.
1) Do I need to remove TeamWin? If yes, with what?
2) How can I start the update again? I'm on a super slow connection and it would hurt to download the 500 MB again…
Thank you!

Fablus said:
Hello everyone.
Two hours ago I received the notification about the Android 5.0 update. I downloaded it and hit "Install". Then, "TeamWin" started, but not the update. I rebooted into System and tried to update again - but it tells me that 4.4.4 is the latest version I can get now. I'm on Build KTU84P now.
1) Do I need to remove TeamWin? If yes, with what?
2) How can I start the update again? I'm on a super slow connection and it would hurt to download the 500 MB again…
Thank you!
Click to expand...
Click to collapse
You need to remove TeamWin, and load up your stock recovery. I don't have the exact instructions for this unfortunately.
The OTA update will come back to your phone soon, usually. Did for me within the hour.
The issue I am having now, back with stock recovery, is during the install I am getting a dead Android error icon, and can't continue. Looking for any help I can, and hopefully it will help you too.

Mysticodex said:
You need to remove TeamWin, and load up your stock recovery. I don't have the exact instructions for this unfortunately.
The OTA update will come back to your phone soon, usually. Did for me within the hour.
The issue I am having now, back with stock recovery, is during the install I am getting a dead Android error icon, and can't continue. Looking for any help I can, and hopefully it will help you too.
Click to expand...
Click to collapse
Maybe we need http://forum.xda-developers.com/google-nexus-5/general/stock-checker-zip-prepare-ota-t2927865?
Gosh, this used to be so easy all the time.

if you are using twrp, why the heck are you trying to install the ota? why not download(from xda) and flash a recovery flashable stock or aosp build, and make life much easier for yourself? heck, i dirty flashed from 444 to 5.0 via an aosp flashable zip without any issues, and kept all my data.

simms22 said:
if you are using twrp, why the heck are you trying to install the ota? why not download(from xda) and flash a recovery flashable stock or aosp build, and make life much easier for yourself? heck, i dirty flashed from 444 to 5.0 via an aosp flashable zip without any issues, and kept all my data.
Click to expand...
Click to collapse
I've read http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523 and it clearly states
-Do a factory reset (maybe you can keep data coming from STOCK 4.4.4 - maybe)
Click to expand...
Click to collapse
And I didn't want to count on a maybe.

I'm using stock recovery, rooted as per normal, and a custom kernal. OTA is giving an Android dead error, with no text. Trying to figure out how to diagnose this.

Fablus said:
I've read http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523 and it clearly states
Click to expand...
Click to collapse
it clearly states what? to use recovery version 2.8+? i used an older version, twrp version 2.6.2.4. what else?
---------- Post added at 05:51 PM ---------- Previous post was at 05:48 PM ----------
Mysticodex said:
I'm using stock recovery, rooted as per normal, and a custom kernal. OTA is giving an Android dead error, with no text. Trying to figure out how to diagnose this.
Click to expand...
Click to collapse
it wont flash over a rooted rom anymore as of lollipop. you can flash the factory img via fastboot though, in your bootloader.

simms22 said:
it clearly states what? to use recovery version 2.8+? i used an older version, twrp version 2.6.2.4. what else?
---------- Post added at 05:51 PM ---------- Previous post was at 05:48 PM ----------
it wont flash over a rooted rom anymore as of lollipop. you can flash the factory img via fastboot though, in your bootloader.
Click to expand...
Click to collapse
Trying to remove the root right now via SuperSU. I am hopeful it will work better afterwards.
Edit: SuperSU unrooted it, rebooted, did OTA again, error again. Is there no way to find out what this error is?

[US996] TWRP Flashable Stock Firmwares

I've put together some stock flashable TWRP zips which will install firmwares for the US996. Since this is a TWRP flashable ZIP this assumes you've already got access to TWRP. I use these to update or restore the stock image easily. Wiping data so far has not been required but if you experience issues you may want to consider it.
These zips flash every partition included in the latest firmware. If you want to err on the safe side (which is what I do before testing these) you could dump images of you current partitions to roll back to in case of an issue. (dd if=/dev/block/bootdevice/by-name/{partition} of=/external_sd/backup/{partition}.img). You'll find all partitions in the updater-script.
Download:
10f - SPL 2016-12-01 - Download (md5: 5c5241beb05385f1bb62cd9931d16675)
10h - SPL 2017-04-01 - Download (md5: 9516ecc55cc3b167154ab184fb419c4b)
10k - SPL 2017-09-01 - Download (md5: 075a5bae7201bc08cc3238a64fc9882a)
10l - SPL 2017-11-01 - Download (md5: 80560956009ac459cef5d4b48e934625)
10n - SPL 2017-11-01 - Download (md5: efbb74d3cc8e688cdabdf60e63a30792)
10o - SPL 2018-02-01 - Download (md5: e52e820b9a908e4b0c19727aadd113a6)
10p - SPL 2018-04-01 - Download (md5: d10f6b5b5e4372ff1577df2fe91830b0)
SPL = Security Patch Level
Instructions:
Boot into TWRP ("reboot recovery" from shell)
Put us99610*.zip onto /external_sd/
TWRP -> Install -> /external_sd/us99610*.zip
Install your desired root: Magisk or SuperSU
TWRP -> Reboot -> System
Your device may reboot a couple times and this is normal. You will then boot into the system.
What does it do?
Flashes partition images (skipping recovery) from the kdz - http://lg-firmwares.com/lg-us996-firmwares/
Moves /system/recovery-from-boot.p to /system/recovery-from-boot.bak to prevent stock recovery from being installed on boot
Wipes cache & dalvik-cache
Note
These firmwares are a mix between USA (Unlocked US996), UCL (US Cellular), and BPT (Brightpoint) but have not had problems running cross-variants. However, one thing I'd like to point out is an issue I saw reported by another user. They stated that after they flashed US Cellar US996 updates (10h/10k/10l) their Unlocked US996 device was being picked up as the US Cellular device when attempting to use the LG website bootloader unlock. This is most likely due to the US Cellular bootloader being flashed and the device reporting a US Cellular device ID. This hasn't caused any issues when your device has already been bootloader-unlocked but I would not suggest that users re-lock their bootloader when running this US Cellular firmware as you may risk running into problems unlocking. The same user had also reported that they just flashed the 10f kdz with LGUP to correct the problem but not a risk I'd like to see anyone take. Just a word of caution.
Special thanks to,
@bullghost for the kdz extractor (https://forum.xda-developers.com/showthread.php?t=2600575)
@Tilde88 for the updater-script template w/root (https://forum.xda-developers.com/v20/development/us996-nrd90m-modded-notsostock-rom-v5-1-t3526542)

Thanks for this! Just curious, is there an actual reason we would need to format data and factory reset? Isn't this just basically the same as updating, just more manually than taking the OTA? Like the same as extracting factory images and manually flashing them on Nexus devices?

jeston said:
Thanks for this! Just curious, is there an actual reason we would need to format data and factory reset? Isn't this just basically the same as updating, just more manually than taking the OTA? Like the same as extracting factory images and manually flashing them on Nexus devices?
Click to expand...
Click to collapse
I'm just not sure that if during the OTA update there are special steps to migrate data to be compatible with the new firmware. To err on the safe side I just suggested you format. Considering it's 7.0 -> 7.0 I don't see why there would be an issue leaving your data in place so if anyone tries it, definitely report back! I personally like starting fresh slate when upgrading.

McNutnut said:
I'm just not sure that if during the OTA update there are special steps to migrate data to be compatible with the new firmware. To err on the safe side I just suggested you format. Considering it's 7.0 -> 7.0 I don't see why there would be an issue leaving your data in place so if anyone tries it, definitely report back! I personally like starting fresh slate when upgrading.
Click to expand...
Click to collapse
Cool, I'll probably give it a try after work tomorrow. I'll let you know how it goes.

Thanks for this. Any word whether 10i that could get this treatment?

The_FNG said:
Thanks for this. Any word whether 10i that could get this treatment?
Click to expand...
Click to collapse
Has the unlocked US996 gotten 10i? I was only aware of 10f. That is the only .kdz I've got access to.

Alright, finally flashed it without wiping anything. Went just fine :good:

jeston said:
Alright, finally flashed it without wiping anything. Went just fine :good:
Click to expand...
Click to collapse
Great to hear!

Link is dead
Sent from my LG-US996 using Tapatalk

mr pnut said:
Link is dead
Sent from my LG-US996 using Tapatalk
Click to expand...
Click to collapse
Working for me. Anyone else having issues?

McNutnut said:
Working for me. Anyone else having issues?
Click to expand...
Click to collapse
Ok I got it bro it's working thru chrome not thru Tapatalk app thx bud
Sent from my LG-US996 using Tapatalk

Just ran this myself-no data wipe, just followed the rest of the directions. Worked like a charm, no problems. THANK YOU!!

Added 10h. This time without the automatic root to allow users to install their own preference (SuperSU or MagiskSU).

McNutnut said:
Added 10h. This time without the automatic root to allow users to install their own preference (SuperSU or MagiskSU).
Click to expand...
Click to collapse
Awesome... since I'm new here, may I ask if there's anything that a KDZ can do that this can't? Other than "prepare the phone for a warranty return" or "sell on Swappa as stock" ??? As you know from the other thread... I'm trying to recover from some problems I was having, and I suspect that I have some corruption. I need to burn it down and hope it rises from the ashes.

DrPhant0m said:
Awesome... since I'm new here, may I ask if there's anything that a KDZ can do that this can't? Other than "prepare the phone for a warranty return" or "sell on Swappa as stock" ??? As you know from the other thread... I'm trying to recover from some problems I was having, and I suspect that I have some corruption. I need to burn it down and hope it rises from the ashes.
Click to expand...
Click to collapse
There are three files in the KDZ which aren't used in the zip: "BackupGPT", "PrimaryGPT", and "recovery". The first two appear to be the partition table structure and the last being the stock recovery. So if your partition layout got messed up, LGUP+KDZ would be able to fix that where the zip won't. I don't know for sure what else LGUP has to offer on top of that, but from what it sounds like, LGUP + KDZ can restore a bricked phone to stock. I've never had to use LGUP myself...fortunately.

What are the MD5 hashes of the zip files? I downloaded the US996-10h file, and tried to flash it, and TWRP says it's invalid. Did I do something wrong?

DrPhant0m said:
What are the MD5 hashes of the zip files? I downloaded the US996-10h file, and tried to flash it, and TWRP says it's invalid. Did I do something wrong?
Click to expand...
Click to collapse
I've got an MD5 of 9516ecc55cc3b167154ab184fb419c4b on 10h. I went ahead and downloaded the file from the link and it matches the source file I uploaded. Possibly a bad download? Give it another shot if the MD5 doesn't match. If it does match...let me know ha.

CONFIRMED! successfully flashed your US996-10h package, followed by Magisk 11.6 and it's booted and rooted! thanks for all your work and help! btw, Magisk v13.0 (0b4baad) also works in case anyone was curious. 12.0 seems to be fscked for all LGV20...
EDIT: with 10d, 10f, and now 10h whenever I reboot the screen brightness always resets to 100% even after I've set it to auto. does this happen to anyone as well?

McNutnut said:
I've got an MD5 of 9516ecc55cc3b167154ab184fb419c4b on 10h. I went ahead and downloaded the file from the link and it matches the source file I uploaded. Possibly a bad download? Give it another shot if the MD5 doesn't match. If it does match...let me know ha.
Click to expand...
Click to collapse
Yep. Bad download. It was 0.2GB shy.
I flashed the new one... and I can't thank you enough that it actually worked! Magisk v13 is installed and SafetyNet passes! I really like some of the bonuses that WETA ROM offered (bandwidth monitor and other battery/clock choices)... but I might stick with this for a while just because I've tried so long to get that crazy issue fixed.
A TWRP-flashable solution was exactly what I needed because LGUP was *not* working for me. It wouldn't even run on my PC, let alone get to the point where it would recognize my phone and flash a full fw.
:good::good::good:I wish I could thank the OP 1000x.:good::good::good:

nice, thanks for this. i'm gonna flash to just go back to a stock rooted 10f rom.
---------- Post added at 03:53 PM ---------- Previous post was at 03:49 PM ----------
wait, this won't wipe internal storage or anything right?