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.
Related
I know some Stylos are able to obtain root. What's the scenario for the 3/3 Plus series?
AidenSurvival said:
I know some Stylos are able to obtain root. What's the scenario for the 3/3 Plus series?
Click to expand...
Click to collapse
dont know yet but the plus series is ure best bet from history speaking
as of rite now theyre no methods on any of the 3s
of coarse u can try king/kingo root prob be best bet
The Plus models from MetroPCS and TMobile have unlockable bootloader's, so all that's needed is TWRP to flash root
Sent from my LGMP450 using Tapatalk
Nice to know there will be an option in a month or two. I hear development on Stylos don't take too long considering their popularity.
I would love to know what's needed to attempt root on a device...I mean from scratch...like what is needed to access the /data file...and how to break thru the lock LG has to stop someone from mounting and rewriting certain files
Sent from my LG-TP450 using Tapatalk
SoonersChuck said:
I would love to know what's needed to attempt root on a device...I mean from scratch...like what is needed to access the /data file...and how to break thru the lock LG has to stop someone from mounting and rewriting certain files
Sent from my LG-TP450 using Tapatalk
Click to expand...
Click to collapse
Do the devices have fast boot. If so a oem unlock. Some one said metro and t mobiles where unlocked or unlockable
I'm no programming/root expert but in developer options you enable oem unlock.. then connected o the pc you type fastboot oem unlock from a command prompt.. the phone then says its unlocked .. that's as far as I went. Aso after that, when you boot the phone, it literally complains that it is missing security before it boots.
gregvolt said:
I'm no programming/root expert but in developer options you enable oem unlock.. then connected o the pc you type fastboot oem unlock from a command prompt.. the phone then says its unlocked .. that's as far as I went. Aso after that, when you boot the phone, it literally complains that it is missing security before it boots.
Click to expand...
Click to collapse
thats it you should be able to either flash su from fastboot or temp run a twrp image until one is made i think
TheMadScientist420 said:
thats it you should be able to either flash su from fastboot or temp run a twrp image until one is made i think
Click to expand...
Click to collapse
If this works for the previous poster, let me know. Rooting this thing would be a dream.
AidenSurvival said:
If this works for the previous poster, let me know. Rooting this thing would be a dream.
Click to expand...
Click to collapse
well I screwed it up. I erased the system partition. wait for an official to come out. had to go buy another phone. if anyone knows how to take the system partition from another phone and make a fastboot flashable copy of it. please by all means, fill me in so I can get the phone working again.
AidenSurvival said:
If this works for the previous poster, let me know. Rooting this thing would be a dream.
Click to expand...
Click to collapse
as stated may not be possible til a actuall twrp image is made
i know other devices with unlockable bl didnt have to flash twrp but run it in fast boot long enought to flash su then upon new reboot stock recov was still there but rooted
can u enable oem unlock the abd usb debugging then abd reboot fastboot?
you also can try coimmand in fastboot to either fastboot oem unlock or just oem unlock
but if u click yes in the fastboot dialouges ure device will be unlocked and wiped
---------- Post added at 09:29 AM ---------- Previous post was at 09:27 AM ----------
gregvolt said:
well I screwed it up. I erased the system partition. wait for an official to come out. had to go buy another phone. if anyone knows how to take the system partition from another phone and make a fastboot flashable copy of it. please by all means, fill me in so I can get the phone working again.
Click to expand...
Click to collapse
try my lg firmwares they normally carry metro and tmob firmwares to flash through download mode
---------- Post added at 09:31 AM ---------- Previous post was at 09:29 AM ----------
also guys as previous poster wiped system partition if im not mistaken there is a way to back up all patitions from fast boot i dont know commands but a quik google of backup device from fastboot should lead u rite then someone should be able to upload a system partition for said previous poster
---------- Post added at 09:35 AM ---------- Previous post was at 09:31 AM ----------
gregvolt said:
well I screwed it up. I erased the system partition. wait for an official to come out. had to go buy another phone. if anyone knows how to take the system partition from another phone and make a fastboot flashable copy of it. please by all means, fill me in so I can get the phone working again.
Click to expand...
Click to collapse
im waiting in the g4 threads to see if a few friends might be able to help us and u out if we can get a full device back up in fastboot then get it uploaded then there should be a command to reflash it through fastboot
im waiting in the g4 threads to see if a few friends might be able to help us and u out if we can get a full device back up in fastboot then get it uploaded then there should be a command to reflash it through fastboot[/QUOTE]
Great I can still get to fastboot so if I could get an image, I could flash it.
TheMadScientist420 said:
as stated may not be possible til a actuall twrp image is made
i know other devices with unlockable bl didnt have to flash twrp but run it in fast boot long enought to flash su then upon new reboot stock recov was still there but rooted
can u enable oem unlock the abd usb debugging then abd reboot fastboot?
you also can try coimmand in fastboot to either fastboot oem unlock or just oem unlock
but if u click yes in the fastboot dialouges ure device will be unlocked and wiped
---------- Post added at 09:29 AM ---------- Previous post was at 09:27 AM ----------
try my lg firmwares they normally carry metro and tmob firmwares to flash through download mode
---------- Post added at 09:31 AM ---------- Previous post was at 09:29 AM ----------
also guys as previous poster wiped system partition if im not mistaken there is a way to back up all patitions from fast boot i dont know commands but a quik google of backup device from fastboot should lead u rite then someone should be able to upload a system partition for said previous poster
---------- Post added at 09:35 AM ---------- Previous post was at 09:31 AM ----------
im waiting in the g4 threads to see if a few friends might be able to help us and u out if we can get a full device back up in fastboot then get it uploaded then there should be a command to reflash it through fastboot
Click to expand...
Click to collapse
LG might have removed the ability to boot an image without flashing it like they did with the Stylo 2 plus, and I don't think there is a kdz available yet as I been looking for one every couple of days but haven't found one.
Sent from my LGMP450 using Tapatalk
gregvolt said:
im waiting in the g4 threads to see if a few friends might be able to help us and u out if we can get a full device back up in fastboot then get it uploaded then there should be a command to reflash it through fastboot
Click to expand...
Click to collapse
Great I can still get to fastboot so if I could get an image, I could flash it.[/QUOTE]
so there is no way to make a backup through fastboot it is said that waiting for a kdz or .tot firmware and restoration through download mode with lg flash tool or lgup or support tool is best bet
do u still have download mode?
gregvolt said:
im waiting in the g4 threads to see if a few friends might be able to help us and u out if we can get a full device back up in fastboot then get it uploaded then there should be a command to reflash it through fastboot
Click to expand...
Click to collapse
Great I can still get to fastboot so if I could get an image, I could flash it.[/QUOTE]
https://forum.xda-developers.com/g4/help/one-help-fastboot-commands-t3623171
An existing fastboot does not mean that it support flashing custom recovery, check lg g6 threads to know what I'm talking about.
I want to purchase one of these from metro to use on my h20 account. If I flash a new rom will it get rid of that stupid unlock policy that makes you use the app after 90 days to unlock?
Anyone know if or when any updates even security patches will roll out for this device?
Sent from my LG-TP450 using Tapatalk
My bet is the situation is similar with G Stylo 2+.
Even with the latest 7.0 ROM, I still could flash TWRP and install SuperSU (not Magisk unfortunately).
roblox84 said:
I want to purchase one of these from metro to use on my h20 account. If I flash a new rom will it get rid of that stupid unlock policy that makes you use the app after 90 days to unlock?
Click to expand...
Click to collapse
There is no roms for this phone no root nothing yet
---------- Post added at 08:40 AM ---------- Previous post was at 08:38 AM ----------
mingkee said:
My bet is the situation is similar with G Stylo 2+.
Even with the latest 7.0 ROM, I still could flash TWRP and install SuperSU (not Magisk unfortunately).
Click to expand...
Click to collapse
Thats what it seems all the plus models eccept cricket. Seem to be rootable.
Ofcoarse no plus for me. Just the reg. So again just like g4 and many other devices i will not be able to get root
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.
Just whant to share dd backup I did who are test and working for at least BND-L21.
dd rip of official OTA 8.0.0.330.
If someone have need.
Cust.img : https://mega.nz/#!q9tn2C6T!JMMSDYN5qc4BQrmKwtjifGqg26Je8SjiToPBM7wktp4
Kernel.img : https://mega.nz/#!Kg8AADgJ!PmBFU4vM1nTvcJnT-AttXBvV7IIh93xdEPgSY9kE0BE
Product.img : https://mega.nz/#!zk8glLyJ!HIKFQoEMuShRYYvm3SWeIfmpLa3LrOI_ahpJ2PDFQXc
Ramdisk.img : https://mega.nz/#!WokUmYZJ!zusLmvamHNUfEVkzn-oEg3rescsnuPG29iRUlQM3E8M
Vendor.img : https://mega.nz/#!H5VnUJxZ!rSI4rg2Hy-cNn9-I1-dMt2y0MHq45ypu2MqL_OP7SZY
Version.img : https://mega.nz/#!q0d2ASiK!20PPaQcjevG_3Hzu1qeBS3ye6FnfG9pL6htA6vy5E8c
System.img : https://mega.nz/#!ShVTHRYJ!-Ha-K9UgKahc7KkRRSRHPkpuLSC4Yr0sZ_kCzEumRs0
If you don't use BND-L21 then use this files at your own risk.
it would have been nice
if files were on some other filehost.
plz share oeminfo too
kdark said:
plz share oeminfo too
Click to expand...
Click to collapse
Wiil try and do
U think it will work on L24?
A bit of context here - my device model is BND-L34 (Mate SE) and I had tried using a method that a user posted in a Mate SE specific thread that detailed how to manually update to Oreo.
Well, that failed miserably and I ended up with a bricked device. I had tried numerous different things to try and revive it (some that I had come up with on my own) and none of them worked. Then I thought to use Multi-Tool to unbrick it with a backup I had lying around but unfortunately it was a Nougat backup.
I had almost lost hope until stumbling upon this thread. I figured I had nothing else to lose so I decided to try to restore my phone with Multi-Tool and your backup files - all except for the system image because MEGA decided to **** block me due to it being a large file (you should definitely upload them elsewhere, by the way), so what I did was use a stock system image someone uploaded in the OpenKirin RROS thread along with the rest of your backup files.
I had also gotten a stock ramdisk_recovery.img file from somewhere else (forgot where but if anyone has trouble finding a stock recovery for Oreo I can upload mine). And VOILA (hope I spelled that right)! My device is back to life on Oreo and I couldn't be more happy.
SO all in all, even if you didn't intend for L34 users to use these files, I want to thank you!
System image I used (see post #2)
[url]https://forum.xda-developers.com/honor-7x/development/rom-t3765201[/URL]
(Screenshots below in a separate post)
Had to put them in a separate post if I didn't wanna go through the trouble of moving the screenshots to my PC and uploading them there
Thanks man, it's great..:good::good::good::good::good:
XandeR180 said:
A bit of context here - my device model is BND-L34 (Mate SE) and I had tried using a method that a user posted in a Mate SE specific thread that detailed how to manually update to Oreo.
Well, that failed miserably and I ended up with a bricked device. I had tried numerous different things to try and revive it (some that I had come up with on my own) and none of them worked. Then I thought to use Multi-Tool to unbrick it with a backup I had lying around but unfortunately it was a Nougat backup.
I had almost lost hope until stumbling upon this thread. I figured I had nothing else to lose so I decided to try to restore my phone with Multi-Tool and your backup files - all except for the system image because MEGA decided to **** block me due to it being a large file (you should definitely upload them elsewhere, by the way), so what I did was use a stock system image someone uploaded in the OpenKirin RROS thread along with the rest of your backup files.
I had also gotten a stock ramdisk_recovery.img file from somewhere else (forgot where but if anyone has trouble finding a stock recovery for Oreo I can upload mine). And VOILA (hope I spelled that right)! My device is back to life on Oreo and I couldn't be more happy.
SO all in all, even if you didn't intend for L34 users to use these files, I want to thank you!
System image I used (see post #2)
[url]https://forum.xda-developers.com/honor-7x/development/rom-t3765201[/URL]
(Screenshots below in a separate post)
Click to expand...
Click to collapse
plz share your ramdisk img file i tried to find it but didn't get it
XandeR180 said:
I had also gotten a stock ramdisk_recovery.img file from somewhere else (forgot where but if anyone has trouble finding a stock recovery for Oreo I can upload mine). And VOILA (hope I spelled that right)! My device is back to life on Oreo and I couldn't be more happy.
Click to expand...
Click to collapse
I would be very interested in the stock ramdisk_recovery, could you send me the link?
Is that L21 version Indian variant?
can i please get some help with unbricking my l24 variant. i have twrp installed but it says frp is locked. twrp says i have no os
Sonny1732 said:
can i please get some help with unbricking my l24 variant. i have twrp installed but it says frp is locked. twrp says i have no os
Click to expand...
Click to collapse
If twrp works, there is a patch file that you can use to unlock frp.
MOD EDIT: LINK REMOVED
Would be helpful to understand what caused this problem though.
mrmazak said:
If twrp works, there is a patch file that you can use to unlock frp.
MOD EDIT: LINK REMOVED
Would be helpful to understand what caused this problem though.
Click to expand...
Click to collapse
ive had installed twrp and magisk the night before and had the app call lspeed downloaded, the next morning i deleted the lspeed app and restarted the device and got stuck on a bootloop so i factory reseted and now i just get the first honor screen then it reboots to the hauwei erecovery
Sonny1732 said:
ive had installed twrp and magisk the night before and had the app call lspeed downloaded, the next morning i deleted the lspeed app and restarted the device and got stuck on a bootloop so i factory reseted and now i just get the first honor screen then it reboots to the hauwei erecovery
Click to expand...
Click to collapse
Ok. Some reason twrp does not good a good job with factory resets.
I suggest flash that frp unlock.zip
Then flash stock ramdisk.img and stock kernel.img.
That will remove magisk, for now anyway.
Then try to boot. If still not, then flash stock recovery and do factory reset. But if reset again locks frp. You will be stuck.
If you dont mind resetting from fresh system maybe just reflash with hurupdater or hwota, instead of flashing stock recovery.
mrmazak said:
Ok. Some reason twrp does not good a good job with factory resets.
I suggest flash that frp unlock.zip
Then flash stock ramdisk.img and stock kernel.img.
That will remove magisk, for now anyway.
Then try to boot. If still not, then flash stock recovery and do factory reset. But if reset again locks frp. You will be stuck.
If you dont mind resetting from fresh system maybe just reflash with hurupdater or hwota, instead of flashing stock recovery.
Click to expand...
Click to collapse
i dont mind at all resetting from fresh system how do i do that
Sonny1732 said:
i dont mind at all resetting from fresh system how do i do that
Click to expand...
Click to collapse
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
mrmazak said:
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
Click to expand...
Click to collapse
thank you, ill give it a try
---------- Post added at 09:03 AM ---------- Previous post was at 08:50 AM ----------
Sonny1732 said:
thank you, ill give it a try
Click to expand...
Click to collapse
i cant download the frp unlock.zip
Sonny1732 said:
thank you, ill give it a try
---------- Post added at 09:03 AM ---------- Previous post was at 08:50 AM ----------
i cant download the frp unlock.zip
Click to expand...
Click to collapse
Ok hold on
Should be this
https://mega.nz/#!nw0wAYoA!hYtf78s0AjwRCpPo_NQ2F4LYclngNBNurJNETypSNKQ
From @KingOfMezi
mrmazak said:
Ok hold on
Click to expand...
Click to collapse
i did the HuRUpdater_0.3.zip and now i can get to the just a sec screen after i select wifi during setup but now its stuck there
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...
Guy's, i need persist from 2101. Give me please. I have broken fingerprint, camera work perfectly. Try flash persist from 2103, EVERYTHING work excluding fingerprint. I think i can fix that, but i need persist from DN2101. Help please...
I have the same problem, OP does not want to provide the rom 100%. They offered me instead to send the phone in after-sales service.
persist img is uniqe if not backed-up you're screwed. you cant use someone elses persist back-up.
try contact OP aftersales in most cases when unlocked bootloader you still have warranty at oneplus
kkdamion said:
persist img is uniqe if not backed-up you're screwed. you cant use someone elses persist back-up.
try contact OP aftersales in most cases when unlocked bootloader you still have warranty at oneplus
Click to expand...
Click to collapse
Maybe we can re-calibrate fingerprint scanner via RL-071?
The engineer code not available on nord 2. I search how to enable it, no engineermode_config in vendor
D3ATHL355 said:
Maybe we can re-calibrate fingerprint scanner via RL-071?
Click to expand...
Click to collapse
I bought the calibrator, on the other hand it would be possible to have the persist partition of another to have a test base? Mine is empty.
deceirem said:
I bought the calibrator, on the other hand it would be possible to have the persist partition of another to have a test base? Mine is empty.
Click to expand...
Click to collapse
If i right understand you, take that. That from 2101.Just unzip.
deceirem said:
I bought the calibrator, on the other hand it would be possible to have the persist partition of another to have a test base? Mine is empty.
Click to expand...
Click to collapse
Ohhh, man that just *#899#)))
What is the difference between persist partition and persist image (emmc)? is one a backup or is it complementary? (they have the same files)
deceirem said:
I bought the calibrator, on the other hand it would be possible to have the persist partition of another to have a test base? Mine is empty.
Click to expand...
Click to collapse
deceirem said:
What is the difference between persist partition and persist image (emmc)? is one a backup or is it complementary? (they have the same files)
Click to expand...
Click to collapse
Man, i don't know, but persist flash via command "fastboot flash persist persist_image.emmc.win". Or persist.img, of you want rename it.
when you backup you can clearly distinguish between persist.img(sda16) and persist_image.emmc.win. I find that strange. Both have basically the same content, different weights, with a slightly different structure.
D3ATHL355 said:
Guy's, i need persist from 2101. Give me please. I have broken fingerprint, camera work perfectly. Try flash persist from 2103, EVERYTHING work excluding fingerprint. I think i can fix that, but i need persist from DN2101. Help please...
Click to expand...
Click to collapse
Hello brother can you please provide me persist image from DN 2103 .. i have issues with camera, fingerprint
Gpsinh677 said:
Hello brother can you please provide me persist image from DN 2103 .. i have issues with camera, fingerprint
Click to expand...
Click to collapse
I dont think, that it works with the persist from another phone but if you want to try: (better make a backup of your own broken persist before flashing)
Fingerprint calibrator working?