We need captures of the OTA payload, URL, metadata, etc. Anything we can get. We also need to study how our partitions change and which have changed. We also need a sound method to accept OTA when rooted (Temp Magisk revert, accept OTA, reinstall Magisk to other slot, reboot?) or revert to stock (restore both sets of boot and dtbo slots?).
Only lead I have is from our NSG friends. Action happens in /data/ota_package. Not sure if anything ends up in /cache.
This OTA includes fixes for GPS, December security level, and "general bugs fixed". n41 5G does not appear to be included, but recent FCC filings suggest that it's at least being tested.
https://fccid.io/2ABZ2-EE143/Test-Report/I19Z62071-WMD01-Part27-NR-Rev0-4569370
https://fccid.io/2ABZ2-EE143/Letter/FCC-cover-letter-C2PC-letter-template-rev1-4569357
It would be a really good time to bring back a Telegram or Discord channel.
Edit: OTA package snagged! https://android.googleapis.com/pack.../aa21536ec572b3c15ab76c49160441f041cf6a27.zip
Credit to xian from the NSG Telegram
<Mod edit>
Can I take this update if I was once rooted but have now flashed back to original boot.img? Obviously once updated I'll run the partition script to pull new partitions so I have virgin partitions on the new build.
OTA Direct Link
Not sure if it will take for me because of my haxing about.
---------- Post added at 12:13 ---------- Previous post was at 12:06 ----------
ntzrmtthihu777 said:
OTA Direct Link
Not sure if it will take for me because of my haxing about.
Click to expand...
Click to collapse
Didn't take. Investigating.
---------- Post added at 13:05 ---------- Previous post was at 12:13 ----------
Bad vbmeta_a hash.
---------- Post added at 13:07 ---------- Previous post was at 13:05 ----------
kirschdog1 said:
Can I take this update if I was once rooted but have now flashed back to original boot.img? Obviously once updated I'll run the partition script to pull new partitions so I have virgin partitions on the new build.
Click to expand...
Click to collapse
apparently you need all stock partition. I need a good vbmeta_a apparently
ntzrmtthihu777 said:
OTA Direct Link
Not sure if it will take for me because of my haxing about.
---------- Post added at 12:13 ---------- Previous post was at 12:06 ----------
Didn't take. Investigating.
---------- Post added at 13:05 ---------- Previous post was at 12:13 ----------
Bad vbmeta_a hash.
---------- Post added at 13:07 ---------- Previous post was at 13:05 ----------
apparently you need all stock partition. I need a good vbmeta_a apparently
Click to expand...
Click to collapse
U want mine from the read back so i can upload
omariscal1019 said:
U want mine from the read back so i can upload
Click to expand...
Click to collapse
Vbmeta_a? Sure. At class so I can't do anything with it yet.
Good news guys, Looks like we will be getting our MSM Tool in about a week
By creating our own ops or the kindness of OnePlus and leakers?
I'm not sure how that would change our situation with the new protections OnePlus is using on MSM tools. We'd have a good rescue method at the very least, but likely not a conversion method.
The only undisclosed exploit I know of is for the Sprint OnePlus 7 Pro 5G and that's purely for a bootloader and/or SIM unlock.
Edit: Saw your post in the other thread. I really hope the tech isn't full of crap like the others promising remote sessions that they never follow up on or provide the wrong files.
ntzrmtthihu777 said:
Vbmeta_a? Sure. At class so I can't do anything with it yet.
Click to expand...
Click to collapse
In a bit ill upload
So i shouldn't accept this update if rooted then?
omariscal1019 said:
In a bit ill upload
Click to expand...
Click to collapse
Cool. Looks like both sides have to be how TMobile
expects them to be in order for the update to work.
ntzrmtthihu777 said:
Cool. Looks like both sides have to be how TMobile
expects them to be in order for the update to work.
Click to expand...
Click to collapse
Yeah that **** happ n on the moto z2f back like two years ago couldnt update if u werent stock on both slots
Bildo41383 said:
So i shouldn't accept this update if rooted then?
Click to expand...
Click to collapse
Think it won't work anyway. It checks hashes of the
other side before applying, and if they don't match
it can't apply the update (brotli diff format, not a
full update.zip style update which just replaces
everything).
But what's the end state of the slots after an update?
A on 16, B on 19? Is 13/14 gone?
LLStarks said:
But what's the end state of the slots after an update?
A on 16, B on 19? Is 13/14 gone?
Click to expand...
Click to collapse
Yeah. My understanding is that 19 installs over 13. I'm
not one hindered percent sure though.
Partition hashes are going to be important. I think we still have our backups and whatever was documented in TEK's thread.
LLStarks said:
Partition hashes are going to be important. I think we still have our backups and whatever was documented in TEK's thread.
Click to expand...
Click to collapse
Note that these hashes may be deep dm-verity
hashes not plain sha256 and so on.
i know i can't get the update to actually update it fails i have tried going back to stock from my backed-up images locked the bootloader seems i cant get it to update
Yeah I'm having the same problem. All I did was root by flashing Magisk. I have since uninstalled the root/Magisk etc and I still get install problem at the very end of the OTA install . Thoughts?
I haven't updated to the new OTA yet, because I now have to restore from a backup so that it doesn't error again. I was curious how many partitions changed since January 2nd, 2020, and since rooting and using the phone for two weeks from the time of that 02 JAN backup the SHA-1 checksum of 43 different partitions have changed. I'll have to look at logs to where the error is from (i.e., because it happened even after I flashed back original unmodified boot_b), or I could just restore everything back.
adb sideload says it flashed it but phone stays the same...
Related
Hi all, Just curious, Im running S-on, latest firmware 3.16, 1.12.11.1119 with TWRP 2.3.3 and had been running MeanBean since 2.9 and Mikey has done a fantastic job, Rom running absolutley flawless. My question is, I get the MeanBean OTA and keep downloading and installing them, is this ok? I keep reading people having all kinds of issues and am begining to be hesitant now when the MeanBean OTA indicator pops up, but the latest 3.03 dirty flashed just fine. Thanks again to Mikey and all the developers!
Dave
OTA
You should be fine. After it downloads it boots into TWRP anyway so it does automatically what you would do manually, so I wouldn't be hesitant at all doing it that way.
Why are you still S-on?
---------- Post added at 09:25 PM ---------- Previous post was at 09:21 PM ----------
NEVER EVER NEVER EVER take an OTA if you don't know exactly who the source of the OTA is. It can unroot your phone if you take the wrong one.
I wasnt sure if I could go S-Off with the latest Firmware. What is the best method?
musicman625 said:
You should be fine. After it downloads it boots into TWRP anyway so it does automatically what you would do manually, so I wouldn't be hesitant at all doing it that way.
Why are you still S-on?
---------- Post added at 09:25 PM ---------- Previous post was at 09:21 PM ----------
NEVER EVER NEVER EVER take an OTA if you don't know exactly who the source of the OTA is. It can unroot your phone if you take the wrong one.
Click to expand...
Click to collapse
Only thing I'm hesitant of, is if I got a good download. I always check my MD5, I'm not sure if the OTA updater does that. When downloading directly on the phone I've gotten many bad downloads. I usually d/l on the computer and Airdroid to the phone and check the MD5 in ES File Explorer.
wolfclan68 said:
Only thing I'm hesitant of, is if I got a good download. I always check my MD5, I'm not sure if the OTA updater does that. When downloading directly on the phone I've gotten many bad downloads. I usually d/l on the computer and Airdroid to the phone and check the MD5 in ES File Explorer.
Click to expand...
Click to collapse
You can find the zip file downloaded through OTA Updater by opening ES File Explorer to sdcard/OTA-Updater/download and check the MD5 from there.
I wasnt sure if I could S-Off with the latest Firmware and what method to use. TWRP seemed like it worked around it and Mean has been running great, so I left it S-on. I already bricked a phone once and luckily HTC fixed it for me at no charge.
spursdude said:
You can find the zip file downloaded through OTA Updater by opening ES File Explorer to sdcard/OTA-Updater/download and check the MD5 from there.
Click to expand...
Click to collapse
That's true forgot about that. But the OTA prompts you to install immediately. Just some extra steps I guess, but worth it to be sure.
---------- Post added at 01:13 PM ---------- Previous post was at 01:08 PM ----------
drich66 said:
I wasnt sure if I could S-Off with the latest Firmware and what method to use. TWRP seemed like it worked around it and Mean has been running great, so I left it S-on. I already bricked a phone once and luckily HTC fixed it for me at no charge.
Click to expand...
Click to collapse
Dirty Racun says it will handle all Hboots. I say do it. Just PRECISELY follow instructions. Make sure all the drivers and software required are properly updated and you're on a compatible OS version.
I got mine on initial release, did LazyPanda S-OFF within the first week. No issues!
Good luck!
wolfclan68 said:
That's true forgot about that. But the OTA prompts you to install immediately. Just some extra steps I guess, but worth it to be sure.
Click to expand...
Click to collapse
Once OTA updater prompts you to install, simply click cancel, go into ES file explorer and find the ROM that just downloaded, verify MD5 is good. If it is (which it should be, I personally have never run into an issue with OTA updater) then just bounce into recovery and flash the ROM you just downloaded.
Sent from my EVO using Tapatalk 2
Hey guys,
I need a creative solution to restore my phone to stock for warranty claim. My USB does not work so I don't have the usual option of using Odin.
I thought I had found a solution with Mobile Odin but whenever I try to run, it mentions it is not compatible with my device. I am currently on Hyperdrive 17.1 via SS.
Thanks
guyver2077 said:
Hey guys,
I need a creative solution to restore my phone to stock for warranty claim. My USB does not work so I don't have the usual option of using Odin.
I thought I had found a solution with Mobile Odin but whenever I try to run, it mentions it is not compatible with my device. I am currently on Hyperdrive 17.1 via SS.
Thanks
Click to expand...
Click to collapse
If you are on NC5 I have a nandroid backup of a stock NC5 image that only has root. I could give you a link to my dropbox that has the zip and you could flash through safestrap then unroot, etc.... I imagine that would work. Up to you if you want to try it. Just let me know cuz I'm gonna have to boot into it myself and remove all my contacts and everything.
liljoe727 said:
If you are on NC5 I have a nandroid backup of a stock NC5 image that only has root. I could give you a link to my dropbox that has the zip and you could flash through safestrap then unroot, etc.... I imagine that would work. Up to you if you want to try it. Just let me know cuz I'm gonna have to boot into it myself and remove all my contacts and everything.
Click to expand...
Click to collapse
I mean anything is worth a shot...Can you install that via safestrap?
I guess I'm trying to just go back to full stock and even remove the 'custom' message from the boot screen. If only mobile Odin worked..anyone have experience with that and S4?
guyver2077 said:
I mean anything is worth a shot...Can you install that via safestrap?
I guess I'm trying to just go back to full stock and even remove the 'custom' message from the boot screen. If only mobile Odin worked..anyone have experience with that and S4?
Click to expand...
Click to collapse
@joshm.1219 this seem reasonable to do?
---------- Post added at 05:20 PM ---------- Previous post was at 05:19 PM ----------
guyver2077 said:
I mean anything is worth a shot...Can you install that via safestrap?
I guess I'm trying to just go back to full stock and even remove the 'custom' message from the boot screen. If only mobile Odin worked..anyone have experience with that and S4?
Click to expand...
Click to collapse
Yes, you'd be able to flash my NC5 nandroid via safestrap.
liljoe727 said:
@joshm.1219 this seem reasonable to do?
---------- Post added at 05:20 PM ---------- Previous post was at 05:19 PM ----------
Yes, you'd be able to flash my NC5 nandroid via safestrap.
Click to expand...
Click to collapse
Yes it should work, generally you don't want to use nandroids from another phone of course, but if he's just doing it to return to stock for warranty, it should be enough to get it to boot, etc.
guyver2077 said:
Hey guys,
I need a creative solution to restore my phone to stock for warranty claim. My USB does not work so I don't have the usual option of using Odin.
I thought I had found a solution with Mobile Odin but whenever I try to run, it mentions it is not compatible with my device. I am currently on Hyperdrive 17.1 via SS.
Thanks
Click to expand...
Click to collapse
https://www.dropbox.com/sh/bnhwfph6konr7ad/AACqXaf0UTS9pRP8A7GVS6FHa?dl=0
There you go. You should be able to download these files and put the in extsd/TWRP/backup/d.......
And "restore" in safestrap. You will then need to remove safestrap, supersu, and towel root apps and unroot. You may be able to unroot through supersu but I'm not sure. I hope this works for you...keep me posted so I can delete the dropbox folder if it works. Ill be deleting the folder in a day or two anyway just in case. The files are good but I assume no risk if something does go wrong as I've never done anything like this before...you should be OK though.
You may need to flash this https://www.androidfilehost.com/?fid=23501681358539843 for WiFi also.
Great. Well i have downloaded all files onto my SD in the directory mentioned...
When i go into SS to restore, nothing appears. Any idea?
Try making a folder called 'stock' or something in extsd/TWRP/backups/d...... And moving everything to the new folder.
---------- Post added at 10:35 PM ---------- Previous post was at 10:35 PM ----------
guyver2077 said:
Great. Well i have downloaded all files onto my SD in the directory mentioned...
When i go into SS to restore, nothing appears. Any idea?
Click to expand...
Click to collapse
Try making a folder called 'stock' or something in extsd/TWRP/backups/d...... And moving everything to the new folder.
---------- Post added at 10:44 PM ---------- Previous post was at 10:35 PM ----------
guyver2077 said:
Great. Well i have downloaded all files onto my SD in the directory mentioned...
When i go into SS to restore, nothing appears. Any idea?
Click to expand...
Click to collapse
Actually, hold on. I just found an nc5 flashable zip on my extsd. Gimme a min to upload to dropbox. You will def need the WiFi modules I linked to earlier also.
---------- Post added at 11:10 PM ---------- Previous post was at 10:44 PM ----------
guyver2077 said:
Great. Well i have downloaded all files onto my SD in the directory mentioned...
When i go into SS to restore, nothing appears. Any idea?
Click to expand...
Click to collapse
This is an NC5 flashable zip, just install in safestrap as you normally would. It may just be a ROM but I can't remember. https://www.dropbox.com/s/mth9zpmxqg75jgc/VRUFNC5_Rooted_Stock-v2.zip?dl=0
You should be able to unroot and everything. Let me know how it goes.
try replacing usb port
I started fixing phones (mainly iDonts because screens are a LOT cheaper), but I've replaced a usb port on an s4 active and it took me less than 10 minutes start to finish (for your first time I would watch the youtube video a few times and take as much time as needed, and btw fridge magnets work great for not losing screws)
the part should be $10 to $20 with shipping on amazon, and tool kit is less than $5 (the part might come with tools, look in description)
just search youtube "how to replace usb galaxy s4"
the usb port (and attatched flex cable) is not carrier specific, however, it probably differs from the s4 active and mini, and unfortunately don't have one to see if it is, so be sure to look out for that. The procedure IS different between S4 active, S4 mini, regular S4 so be sure you're watching a how to video on the right model
if you need any help with this, reply to this thread or pm and i will help you out.
Unless you have very shakey hands and/or can't see those small screws, I am confident you can do it, for not much has to come apart to replace the usb. The hardest part is the flex cable connection to the motherboard, but if you disconnect it with a PLASTIC tool, you greatly reduce risk of damage, so use plastic. A magnifier may help to see what you're doing, especially when fitting the new cable connection
Good luck!
edit: just looked back n saw the part about warranty. Well, I'm pretty sure you can get away with this, if it is a defective usb port. Those long samsung cables go bad after awhile so try another one (if you knew that already, disregard) and make sure verizon doesn't claim misuse (i.e. forced cable upside down; I used to work for them, they wouldn't replace phones for that reason but that was almost 4 years ago) just maybe try and make it look well taken care of if going warranty route. I am still pretty sure there are no void stickers on any screws, but I can check as soon as I figure out how to get safestrap back after forgetting to flash supersu after Hyperdrive rls19. I miss mdk...wish i didn't break that $180 display, I went with $100 Asurion claim (btw it was a brand new replacement, so any void stickers would be there)
Anyways, hope this helps, reply if need more, and good luck!
liljoe727 said:
Try making a folder called 'stock' or something in extsd/TWRP/backups/d...... And moving everything to the new folder.
---------- Post added at 10:35 PM ---------- Previous post was at 10:35 PM ----------
Try making a folder called 'stock' or something in extsd/TWRP/backups/d...... And moving everything to the new folder.
---------- Post added at 10:44 PM ---------- Previous post was at 10:35 PM ----------
Actually, hold on. I just found an nc5 flashable zip on my extsd. Gimme a min to upload to dropbox. You will def need the WiFi modules I linked to earlier also.
---------- Post added at 11:10 PM ---------- Previous post was at 10:44 PM ----------
This is an NC5 flashable zip, just install in safestrap as you normally would. It may just be a ROM but I can't remember. https://www.dropbox.com/s/mth9zpmxqg75jgc/VRUFNC5_Rooted_Stock-v2.zip?dl=0
You should be able to unroot and everything. Let me know how it goes.
Click to expand...
Click to collapse
Good news. I'm now on a stock rom! Thanks for all your help.
Now to get rid of the custom lock on boot screen and I should be good to go.
guyver2077 said:
Good news. I'm now on a stock rom! Thanks for all your help.
Now to get rid of the custom lock on boot screen and I should be good to go.
Click to expand...
Click to collapse
If I'm not mistaken, that logo can only be removed with an Odin .tar full wipe, for that custom lock shows up when anything to the ROM is changed, which it still may be. Locked bootloader means anything before the safestrap logo is locked (i think). I may be full wiping via odin today for I need to get root again, so I can let ya know if it gets rid of that.
Obviously I'm still a newb to xda, but I've been rooting for few years now, so keep that in mind. Just tryin to get my thx count up so I can actually post things lol. But if I am wrong about ANY of this, I am open to any criticism (so long as not rude and quick explaination why)
Hope this helps
Edit: maybe try flashing that zip again, but wiping system first? But if you lost safestrap I'm not sure how that is possible
guyver2077 said:
Good news. I'm now on a stock rom! Thanks for all your help.
Now to get rid of the custom lock on boot screen and I should be good to go.
Click to expand...
Click to collapse
You can try triangle away from the play store.
Hello, I am new as a poster on these forums, but not new as a visitor, but I thought I would have the best luck asking around here. So basically I was being stupid and on my HTC One M8, which has been rooted for some time, I wanted to put the 5.0.1 GPE Skydragon on. I had been trying to get S-off in the past, but it had failed. Today I tried again, but still wouldn't get past first bottle. Either way I was impatient and misinterpreted a tutorial someone had created, implying you already had S-Off. I though that would be a later step and this was a different method, so I tried to flash the ROM with S-On, and things went downhill from there. I could make my phone vibrate by using the volume buttons, but a dark screen that displayed nothing. I was able to access my boot loader and TWRP, so I know the screen isn't kill. When inside of TWRP, I clicked on system cache along with Davlik and other ones, so it screwed my system no also. Also, if I plug it into my computer the internal sd and external sd do appear, so that's good. But in recap I am stuck where I can only access TWRP and boot menu, and because my S is on, I cant seem to flash anything nor get past it. Please help, my phone is vital especially in Finals Week.
The best way to recover is to flash a RUU...I do not have links for you, but I have been here for a few months. I've heard when problems exist, the best thing to do is flash a RUU...I might be completely wrong, but give wonder_never_cease a pm. He's a very knowledgeable person.
jxcorex28 said:
The best way to recover is to flash a RUU...I do not have links for you, but I have been here for a few months. I've heard when problems exist, the best thing to do is flash a RUU...I might be completely wrong, but give wonder_never_cease a pm. He's a very knowledgeable person.
Click to expand...
Click to collapse
couldn't find that user... he is on the forum, correct?
Its wonders_never_cease
But in all seriousness this information is posted time and time again here. I'm sure wonders has better things to do than to do your searches for you. Not trying to be rude but its all right here.
- Sent from a payphone ...
tommy_riley said:
Its wonders_never_cease
But in all seriousness this information is posted time and time again here. I'm sure wonders has better things to do than to do your searches for you. Not trying to be rude but its all right here.
- Sent from a payphone ...
Click to expand...
Click to collapse
Well, I have looked around, nothing in the same predicament that I am in currently... So I will send him a message anyway, maybe I'll get lucky.
Update: I messaged him and no reply yet, this is urgent, so if anyone can directly help me I would appreciate it greatly.
As instructed above if unable to boot into bootloader to flash a custom recovery and pushing a custom rom to phone,flash the ruu thats for your software build you had prior to this fiasco,patience is a virtue eh...lol...
tommy_riley said:
Its wonders_never_cease
But in all seriousness this information is posted time and time again here. I'm sure wonders has better things to do than to do your searches for you. Not trying to be rude but its all right here.
- Sent from a payphone ...
Click to expand...
Click to collapse
"sent from a payphone". i love it!
"all I can really do, is stay out of my own way and let the will of heaven be done"
ryankrogh said:
When inside of TWRP, I clicked on system cache along with Davlik and other ones, so it screwed my system no also.
Click to expand...
Click to collapse
You mean you wiped something, like system? What were you trying to accomplish by doing this, exactly?
---------- Post added at 01:43 PM ---------- Previous post was at 01:41 PM ----------
ryankrogh said:
Well, I have looked around, nothing in the same predicament that I am in currently...
Click to expand...
Click to collapse
This same situation gets asked several times a day.
Just restore the nandroid you made. If you didn't make one, than that is a mistake I suggest you never repeat ever again.
If no nandroid, you just need to flash a ROM (either by adb sideloader, adb push, mount memory in recovery, or put on removable SD). A ROM that matches you current firmware will avoid the long boot times and broken WiFi that are symptomatic of a firmware mismatch. You haven't posted enough info for us to know what firmware you are on (hboot and radio number).
---------- Post added at 01:45 PM ---------- Previous post was at 01:43 PM ----------
jxcorex28 said:
The best way to recover is to flash a RUU...I do not have links for you
Click to expand...
Click to collapse
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Relock the bootloader to RUU (with s-on).
---------- Post added at 01:52 PM ---------- Previous post was at 01:45 PM ----------
BTW, what is with all the bad thread titles today? At least 4 threads in this forum titled "HELP", "[Q]" or something similar. This this is a Q&A and help forum, so of course you are asking for help and have a question. But please try to give your thread a specific title describing your issue, to help keep the forum organized.
redpoint73 said:
You mean you wiped something, like system? What were you trying to accomplish by doing this, exactly?
---------- Post added at 01:43 PM ---------- Previous post was at 01:41 PM ----------
This same situation gets asked several times a day.
Just restore the nandroid you made. If you didn't make one, than that is a mistake I suggest you never repeat ever again.
If no nandroid, you just need to flash a ROM (either by adb sideloader, adb push, mount memory in recovery, or put on removable SD). A ROM that matches you current firmware will avoid the long boot times and broken WiFi that are symptomatic of a firmware mismatch. You haven't posted enough info for us to know what firmware you are on (hboot and radio number).
---------- Post added at 01:45 PM ---------- Previous post was at 01:43 PM ----------
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Relock the bootloader to RUU (with s-on).
---------- Post added at 01:52 PM ---------- Previous post was at 01:45 PM ----------
BTW, what is with all the bad thread titles today? At least 4 threads in this forum titled "HELP", "[Q]" or something similar. This this is a Q&A and help forum, so of course you are asking for help and have a question. But please try to give your thread a specific title describing your issue, to help keep the forum organized.
Click to expand...
Click to collapse
The issue has been resolved after a stressful weekend, there was a droid news article that worked for me, so the RUU method worked in the end. Thanks anyway!
with very little activity lately for the LGV20, specifically the H918 T-Mobile variant, I created a TWRP flashable package for the recent H91810q release. this zip flash every partition included in the latest KDZ package with the exception of recovery to keep TWRP. standard disclaimer applies, you do all of this at YOUR OWN risk! because 10q is not rootable, you need to be root'd before flashing this! failure to do so will probably cause you to lose root and/or lose TWRP! and worst of all, because 10q can't be downgraded to 10j (last version where you can still obtain root via dirtycow) because of Anti-RollBack, you're fscked!
NOTE1: you can find the partitions that will be flashed in the updater-script. to be extra cautious you can back up all of the partitions that will be overwritten with the following: dd if=/dev/block/bootdevice/by-name/{partition} of=/external_sd/backup/{partition}.img.
NOTE2: boot partition has been modified only to remove rctd, nothing else so I consider this to still be stock
Instructions:
download H91810u.zip file listed below and put on microSD card
download your choice of root and put on microSD card, choose from either Magisk or SuperSU *Note: v12.0 of Magisk does not work with the LGV20 device in general and v14.0 is recommended.
backup any data from internal "SD card"
boot into TWRP (requires TWRP recovery to already be installed)
create a TWRP backup of the device
flash zip from microSD card by using "Install"
FLASH YOUR CHOICE OF ROOT - Flashing root is VERY IMPORTANT BEFORE REBOOTING!
reboot
profit!
Download:
H91810q.zip
old 10q md5sum: 8c2e76ded9759a63b1ffac86f3941649
new 10q md5sum: c7d4086b3a0a786d1501ef7e4ce22f32 - re-zipped in Linux for proper alignment
H91810r.zip
wrong 10r md5sum: 9e2e1f8c56079d7bf629ce5e375d7551 (this is actually the md5sum for the KDZ)
correct 10r md5sum: 194b2bc41aa6dbdd7b9a371392f7b930
H91810s.zip
10s md5sum: f187fdefe4c3612c5811e9fbeb0748c5
H91810t.zip - rctd and triton both disabled, previous versions only removed rctd
10t md5sum: b00c2f644b15eb15e459c48830caa5da
H91810u.zip - rctd and triton both disabled, previous versions only removed rctd
10u md5sum: f51b2b11a30dc448b0da0edc750bb587
Flashing Process (what flashing this zip does):
flash necessary partition images with the exception of recovery (to keep TWRP) from the KDZ
rename /system/recovery-from-boot.p to /system/recovery-from-boot.bak to prevent stock recovery from being installed on boot
wipes dalvik-cache and cache
BIG thanks to @McNutnut on guidance, as well as his script to put all of this together!
also thanks to @bullghost for the KDZ extractor (https://forum.xda-developers.com/showthread.php?t=2600575)
@Tilde88 for the original updater-script template w/root (https://forum.xda-developers.com/v20/development/us996-nrd90m-modded-notsostock-rom-v5-1-t3526542)
Awesome thanks.. I'm on it!
---------- Post added at 12:50 AM ---------- Previous post was at 12:07 AM ----------
Didn't work... Still shows 10p. I noticed the flash process was rather fast also.
storm68 said:
Awesome thanks.. I'm on it!
---------- Post added at 12:50 AM ---------- Previous post was at 12:07 AM ----------
Didn't work... Still shows 10p. I noticed the flash process was rather fast also.
Click to expand...
Click to collapse
Dude, thanks for whipping this out so fast! (TWSS) I will get right on making a debloated rom from this. Is it ARB 1?
So I HAVE to flash root? Sometimes I don't flash root because of my gear S3 watch.
I just flashed but still showing 10p. But the kernel info shows Sept 12. So the kernel is updated but wondering on why it still shows 10p on software info @ about phone.
storm68 said:
Awesome thanks.. I'm on it!
---------- Post added at 12:50 AM ---------- Previous post was at 12:07 AM ----------
Didn't work... Still shows 10p. I noticed the flash process was rather fast also.
Click to expand...
Click to collapse
hold on, let me re-zip and re-upload. I had used two different methods to add the files to the archive so I'm going to re-do it all with one method
texasaggie1 said:
Dude, thanks for whipping this out so fast! (TWSS) I will get right on making a debloated rom from this. Is it ARB 1?
So I HAVE to flash root? Sometimes I don't flash root because of my gear S3 watch.
Click to expand...
Click to collapse
yes, this is ARB1 and yes, root is needed if you want to stay root'd
As you can see the updater script shows install 10p.
storm68 said:
As you can see the updater script shows install 10p.
Click to expand...
Click to collapse
yep, for some reason using Windows to create zip files causes inconsistencies. I've zipped up everything in Linux this time and double checked the updater script to make sure everything is good to go and am uploading it as I type... I've already updated the OP with the new md5sum and the link should remain the same. I'll give a heads up once it's live
Ok thanks for your time. Appreciate it. ?
storm68 said:
Ok thanks for your time. Appreciate it.
Click to expand...
Click to collapse
done! uploaded and downloaded myself to verify everything is the correct one. this should bring you to 10q for everything... sorry for the troubles of flashing again. don't forget to flash root just in case lol
No problem. No apology needed being you really don't have to do this for the community. Thanks again.
Sorry if I'm asking an obvious question but when did t mobile release a new update? I thought the latest version was 10p???
Flashed... All good!
---------- Post added at 02:41 AM ---------- Previous post was at 02:40 AM ----------
Still_living714 said:
Sorry if I'm asking an obvious question but when did t mobile release a new update? I thought the latest version was 10p???
Click to expand...
Click to collapse
Mine came yesterday. Updater to 10q. If you haven't gotten it yet you will..
storm68 said:
Flashed... All good!
---------- Post added at 02:41 AM ---------- Previous post was at 02:40 AM ----------
Mine came yesterday. Updater to 10q. If you haven't gotten it yet you will..
Click to expand...
Click to collapse
Any big improvements that you can see?
i flashed and once i unlocked my phone, it kept saying process.android keeps stopping repeatedly. booted back into twrp to restore the backup i made in twrp and now the keeps rebooting to the lg screen. Can anybdoy help me out please. i was ww kernel and 10k
Still_living714 said:
Any big improvements that you can see?
Click to expand...
Click to collapse
I would have to wait and see. But first hand it's about the same as 10p no rctd.
---------- Post added at 04:02 AM ---------- Previous post was at 03:26 AM ----------
Lgv20user said:
i flashed and once i unlocked my phone, it kept saying process.android keeps stopping repeatedly. booted back into twrp to restore the backup i made in twrp and now the keeps rebooting to the lg screen. Can anybdoy help me out please. i was ww kernel and 10k
Click to expand...
Click to collapse
First of be advised that this is anti roll back. Once on it you can't go backwards to other older roms. In reference to your problem you'll have to do a battery pull. Put battery back in. Now hold down volume down and power button at the same time, when you see LG screen release power button for two seconds then push again holding down power. During all this never release volume down. Now you'll get a reset screen with yes and no option. Use volume key to choose yes, twice..... This will get you back to TWRP. In your case I wouldn't even bother with back up but you can try again if want. What I would do is flash something else that I know works. Then decide from there what to do... Maybe redownload again. May be corrupt some how. I assume your on h918. Hope so! Good luck.
storm68 said:
I would have to wait and see. But first hand it's about the same as 10p no rctd.
---------- Post added at 04:02 AM ---------- Previous post was at 03:26 AM ----------
First of be advised that this is anti roll back. Once on it you can't go backwards to other older roms. In reference to your problem you'll have to do a battery pull. Put battery back in. Now hold down volume down and power button at the same time, when you see LG screen release power button for two seconds then push again holding down power. During all this never release volume down. Now you'll get a reset screen with yes and no option. Use volume key to choose yes, twice..... This will get you back to TWRP. In your case I wouldn't even bother with back up but you can try again if want. What I would do is flash something else that I know works. Then decide from there what to do... Maybe redownload again. May be corrupt some how. I assume your on h918. Hope so! Good luck.
Click to expand...
Click to collapse
what do you recommend i flash
Lgv20user said:
what do you recommend i flash
Click to expand...
Click to collapse
Well we really don't know if your system went to 10q now, so........ You can try again. On both, the backup or 10q. Since you know now how to get to TWRP with battery pull you can try both, see what works. Try backup first. If it doesn't work you may have system in 10q now being you backed up a 10k system may not work now. If it doesn't try q again. If that doesn't work then download 10p or redownload 10q and side load on TWRP from computer. Then flash again. These are steps I would do.. if someone tells you different then it's your choice. Different ways for different things.
storm68 said:
Well we really don't know if your system went to 10q now, so........ You can try again. On both, the backup or 10q. Since you know now how to get to TWRP with battery pull you can try both, see what works. Try backup first. If it doesn't work you may have system in 10q now being you backed up a 10k system may not work now. If it doesn't try q again. If that doesn't work then download 10p or redownload 10q and side load on TWRP from computer. Then flash again. These are steps I would do.. if someone tells you different then it's your choice. Different ways for different things.
Click to expand...
Click to collapse
so 10q is showing up. i am having issues with the modem i believe because i dont get tmobile recepetion and as soon as i put into airplane mode, the error message stops.
I haven't tried the 10p weta kernel yet but it may not work being this stock kernel on 10q is updated to the September security patch. May try later today.
First off, thanks for keeping my beloved H918 alive!. Thought all future dev for the V20 was dead.
Now a question. Any timeframe on a debloated version? Not in a hurry mind you, just curious.
If anyone can, could you please extract your persist.img or persist partition as i think mine is corrupt or something, making the sensors stop working.
Ayit Boss Geez said:
If anyone can, could you please extract your persist.img or persist partition as i think mine is corrupt or something, making the sensors stop working.
Click to expand...
Click to collapse
Use the MSM tool
juliusedward said:
Use the MSM tool
Click to expand...
Click to collapse
I have, multiple times but the sensors still don't work. I'm not sure the persist partition actually gets flashed in that.
bump, i really need someone to please post their persist partition
even posting the folder mnt/vendor/persist/sensors as a zip would help
juliusedward said:
Use the MSM tool
Click to expand...
Click to collapse
Msm doesn't fix sensor issues especially the issue with fingerprint enrollment.
persist.img fixes the errors.
---------- Post added at 07:37 PM ---------- Previous post was at 07:32 PM ----------
Ayit Boss Geez said:
bump, i really need someone to please post their persist partition
even posting the folder mnt/vendor/persist/sensors as a zip would help
Click to expand...
Click to collapse
You need persist.img which we know already.
It would be a good idea for 7t pro owners to back up their persist.img.
Hopefully someone with a 7t pro will help you soon.
I have 7t pro 5g McLaren TMO and I will share my persist with you but Im not sure that would work without side affects.
Edit.
On a side note it was confirmed on 7t pro 5g McLaren that if you msm to older version and then OTA update to the latest software version it will be fixed. Have you tried this yet ? @Ayit Boss Geez
twinnfamous said:
Msm doesn't fix sensor issues especially the issue with fingerprint enrollment.
persist.img fixes the errors.
---------- Post added at 07:37 PM ---------- Previous post was at 07:32 PM ----------
You need persist.img which we know already.
It would be a good idea for 7t pro owners to back up their persist.img.
Hopefully someone with a 7t pro will help you soon.
I have 7t pro 5g McLaren TMO and I will share my persist with you but Im not sure that would work without side affects.
Edit.
On a side note it was confirmed on 7t pro 5g McLaren that if you msm to older version and then OTA update to the latest software version it will be fixed. Have you tried this yet ? @Ayit Boss Geez
Click to expand...
Click to collapse
Im pretty sure i did try it but in the end i sent it off for warranty repair. I'll update with results.
Update:
The warranty repair worked as it replaced the main board so I think it was the persist partition. I have also now backed up my persist partition.
Good that you recovered it ... anyway, also attached to this post.
twinnfamous said:
Msm doesn't fix sensor issues especially the issue with fingerprint enrollment.
persist.img fixes the errors.
---------- Post added at 07:37 PM ---------- Previous post was at 07:32 PM ----------
You need persist.img which we know already.
It would be a good idea for 7t pro owners to back up their persist.img.
Hopefully someone with a 7t pro will help you soon.
I have 7t pro 5g McLaren TMO and I will share my persist with you but Im not sure that would work without side affects.
Edit.
On a side note it was confirmed on 7t pro 5g McLaren that if you msm to older version and then OTA update to the latest software version it will be fixed. Have you tried this yet ? @Ayit Boss Geez
Click to expand...
Click to collapse
Can you tell me which msm was used or point me to the thread that talks about which msm was used before ota? I ask because I've tried msm but not all of them.
Ayit Boss Geez said:
Update:
The warranty repair worked as it replaced the main board so I think it was the persist partition. I have also now backed up my persist partition.
Click to expand...
Click to collapse
How do you back up the persist.img and why is it needed?
foobar66 said:
Good that you recovered it ... anyway, also attached to this post.
Click to expand...
Click to collapse
Can I just flash this zip with magisk? I have 7t pro McLaren so j don't have twrp.
lendawg said:
Can I just flash this zip with magisk? I have 7t pro McLaren so j don't have twrp.
Click to expand...
Click to collapse
It's not a flashable zip from what I can see. I'm guessing you need to extract persist.img from the zip and flash it with fastboot but I haven't done that before so I don't know the exact commands.
knpk13 said:
It's not a flashable zip from what I can see. I'm guessing you need to extract persist.img from the zip and flash it with fastboot but I haven't done that before so I don't know the exact commands.
Click to expand...
Click to collapse
Should be fastboot flash persist. Tried before when this happened on my other device and it flashed but still didn't fix. Hopefully it works this time around.
lendawg said:
Should be fastboot flash persist. Tried before when this happened on my other device and it flashed but still didn't fix. Hopefully it works this time around.
Click to expand...
Click to collapse
The issue is that a foreign persist.img will fix sensor calibration data and therefore fix all sensors, cameras etc. But you won't be able to use the fingerprint sensor unless you've restored your own persist.img.
A foreign one will always mismatch and make the fingerprint sensor unavailable. That's why I keep a backup of mine just in case.
Even the MSM Tool won't fix it as it is something device specific that should persist at all times hence persist.img.
EDIT: You can backup EFS by booting TWRP (it doesn't need to decrypt /data):
- Get adb and fastboot on your computer
- "fastboot boot TWRP.img"
- Type in
Code:
adb shell
dd if=/dev/block/bootdevice/by-name/persist of=/tmp/persist.img
exit
adb pull /tmp/persist.img persist.img
This will copy the persist partition as an .img file to the /tmp/ folder on your device and the last command will copy it to your computer's user folder.
To do the same in reverse (restoring the persist partition):
Code:
adb push PATHONCOMPUTER/persist.img /tmp/persist.img
adb shell
dd if=/tmp/persist.img of=/dev/block/bootdevice/by-name/persist
exit
Macusercom said:
The issue is that a foreign persist.img will fix sensor calibration data and therefore fix all sensors, cameras etc. But you won't be able to use the fingerprint sensor unless you've restored your own persist.img.
A foreign one will always mismatch and make the fingerprint sensor unavailable. That's why I keep a backup of mine just in case.
Even the MSM Tool won't fix it as it is something device specific that should persist at all times hence persist.img.
EDIT: You can backup EFS by booting TWRP (it doesn't need to decrypt /data):
- Get adb and fastboot on your computer
- "fastboot boot TWRP.img"
- Type in
This will copy the persist partition as an .img file to the /tmp/ folder on your device and the last command will copy it to your computer's user folder.
To do the same in reverse (restoring the persist partition):
Click to expand...
Click to collapse
So you're saying I won't be able to get it to work by flashing someone else's persist? I ask because I have one right now I was gonna try
lendawg said:
So you're saying I won't be able to get it to work by flashing someone else's persist? I ask because I have one right now I was gonna try
Click to expand...
Click to collapse
I don't think so. You can try as there is nothing that really could go wrong or make it worse except it not working afterwards.
Macusercom said:
I don't think so. You can try as there is nothing that really could go wrong or make it worse except it not working afterwards.
Click to expand...
Click to collapse
Damn...looks like another warranty exchange for me then smh. Can't believe flashing Blu spark is what messed it up I never had problems before with that kernel.
---------- Post added at 12:12 AM ---------- Previous post was at 12:01 AM ----------
twinnfamous said:
Msm doesn't fix sensor issues especially the issue with fingerprint enrollment.
persist.img fixes the errors.
---------- Post added at 07:37 PM ---------- Previous post was at 07:32 PM ----------
You need persist.img which we know already.
It would be a good idea for 7t pro owners to back up their persist.img.
Hopefully someone with a 7t pro will help you soon.
I have 7t pro 5g McLaren TMO and I will share my persist with you but Im not sure that would work without side affects.
Edit.
On a side note it was confirmed on 7t pro 5g McLaren that if you msm to older version and then OTA update to the latest software version it will be fixed. Have you tried this yet ? @Ayit Boss Geez
Click to expand...
Click to collapse
Well I ran the 10.0.16 msm and ota'd and it didn't work for me just a heads up.
knpk13 said:
How do you back up the persist.img and why is it needed?
Click to expand...
Click to collapse
The persist partition has the sensor signatures and is not changed over updates. also doesn't get flashed over msm (i'm pretty sure). Therefore, its best to back it up as if anything goes wrong on it, such as mine, you can just reflash it and get everything working again. I don't remember how I backed it up, but i think I got the list of the blocks and labels over fastboot or adb and just copied the persist partition over. Just do some google searches. while your at it, you may as well back up the modemst1 and 2 partitions as well as they have the IMEI (I think).
lendawg said:
Damn...looks like another warranty exchange for me then smh. Can't believe flashing Blu spark is what messed it up I never had problems before with that kernel.
---------- Post added at 12:12 AM ---------- Previous post was at 12:01 AM ----------
Well I ran the 10.0.16 msm and ota'd and it didn't work for me just a heads up.
Click to expand...
Click to collapse
Also, it's not blu_spark that messes it up as i'm using it. Just make sure to back it up once you get your phone back from the repair.
Ayit Boss Geez said:
The persist partition has the sensor signatures and is not changed over updates. also doesn't get flashed over msm (i'm pretty sure). Therefore, its best to back it up as if anything goes wrong on it, such as mine, you can just reflash it and get everything working again. I don't remember how I backed it up, but i think I got the list of the blocks and labels over fastboot or adb and just copied the persist partition over. Just do some google searches. while your at it, you may as well back up the modemst1 and 2 partitions as well as they have the IMEI (I think).
Click to expand...
Click to collapse
I just posted the commands to back it up a few posts before MSM Tool doesn't restore it. It contains all sensor configuration and calibration data including the fingerprint sensor. But you won't be able to use the fingerprint sensor if you're not using your own persist.img backup. Everything else would work fine though. And you're correct about modemst1 and modemst2.
I have been writing with him on the blu_spark thread. There was an issue with the fingerprint sensor not working on the 7T due to changing the VerifiedBootState flag. It got fixed with an update of blu_spark but somehow his fingerprint enrollment got corrupted. I can't say if it was coincidence but given that he is the only one with permanent issues, there is probably something else caused it or helped causing it. But I can't tell what and how. This is why backing up persist.img is always a good idea. It seems that it can be easily corrupted.