Database Users

Unable to update OTA since repair - alternatives?

Hi all,
To cut a long story short, around the time MM was being released I cracked my display and broke the digitiser. Before sending the phone off for repair I got the update notification -.- but sent it away without updating as I couldn't accept it. Phone returned and working but no OTA notification, factory reset a few times, sim out and try again, all the usual tricks. They flashed my phone in the factory (came back wiped) and for some reason this firmware isn't getting the OTA update.
So after persevering with Lollipop (and cracking the display again, and fixing it myself this time) I'm getting Marshmallow one way or another. I just would like to know the best way.
I'd rather keep everything as stock as possible (in terms of bootloaders and rooting) and my current plan was to flash TWRP and try running a MM OTA file. I'm just looking to verify this would work and if so, any pitfalls (future OTAs) or things that could go horribly wrong by doing something idiotic.
I'm on an EU XT1572 so I'm assuming a general EU OTA file will work?
Thanks in advance for any assistance,
Phil

clarkey586 said:
Hi all,
To cut a long story short, around the time MM was being released I cracked my display and broke the digitiser. Before sending the phone off for repair I got the update notification -.- but sent it away without updating as I couldn't accept it. Phone returned and working but no OTA notification, factory reset a few times, sim out and try again, all the usual tricks. They flashed my phone in the factory (came back wiped) and for some reason this firmware isn't getting the OTA update.
So after persevering with Lollipop (and cracking the display again, and fixing it myself this time) I'm getting Marshmallow one way or another. I just would like to know the best way.
I'd rather keep everything as stock as possible (in terms of bootloaders and rooting) and my current plan was to flash TWRP and try running a MM OTA file. I'm just looking to verify this would work and if so, any pitfalls (future OTAs) or things that could go horribly wrong by doing something idiotic.
I'm on an EU XT1572 so I'm assuming a general EU OTA file will work?
Thanks in advance for any assistance,
Phil
Click to expand...
Click to collapse
Easy-peasy.
*NOTE - Using TWRP to flash the OTA.zip IS NOT an option, it WILL fail. You can however use the stock recovery and ADB sideload it.. but the following is how I would probably do it. It's also easier IMO.
I'm assuming your bootloader is unlocked since you were talking about using TWRP so grab the WHOLE 6.0 firmware for your phone (I'm guessing your're RETEU so -> XT1572_CLARK_RETEU_6.0_MPHS24.49-18-3_cid7_subsidy-DEFAULT_CFC.xml.zip - It's 1.3GB in size) and then reboot the phone into the bootloader (Fastboot mode) and use the files in it to flash everything (this process will wipe the phone so backup anything important first) with fastboot and you will be on a clean completely stock 6.0 with the february patch.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Standalone Fastboot & adb installer - LINK
WHOLE Firmware - LINK
Good luck! If your bootloader is not already unlocked and you don't want to unlock it there is still hope.. it will just be a bit different process by using the OTA zips and the stock recovery.. let me know if you MUST go down this route.. it's a bit more of a PITA IMO.
EDIT* If terminal commands are not your thing you can also try using RSDLite.(Official Moto tool). but I've not personally tried it with my Moto X Pure... I like the terminal

DaMadOne said:
Easy-peasy.
*NOTE - Using TWRP to flash the OTA.zip IS NOT an option, it WILL fail. You can however use the stock recovery and ADB sideload it.. but the following is how I would probably do it. It's also easier IMO.
I'm assuming your bootloader is unlocked since you were talking about using TWRP so grab the WHOLE 6.0 firmware for your phone (I'm guessing your're RETEU so -> XT1572_CLARK_RETEU_6.0_MPHS24.49-18-3_cid7_subsidy-DEFAULT_CFC.xml.zip - It's 1.3GB in size) and then reboot the phone into the bootloader (Fastboot mode) and use the files in it to flash everything (this process will wipe the phone so backup anything important first) with fastboot and you will be on a clean completely stock 6.0 with the february patch.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Standalone Fastboot & adb installer - LINK
WHOLE Firmware - LINK
Good luck! If your bootloader is not already unlocked and you don't want to unlock it there is still hope.. it will just be a bit different process by using the OTA zips and the stock recovery.. let me know if you MUST go down this route.. it's a bit more of a PITA IMO.
EDIT* If terminal commands are not your thing you can also try using RSDLite.(Official Moto tool). but I've not personally tried it with my Moto X Pure... I like the terminal
Click to expand...
Click to collapse
Thanks a million.
I've not unlocked my bootloader, but I don't think it should be a problem there's plenty of tutorials etc for that.
Ideally, I'd not like to wipe my phone but alas it looks like that's going to be the case and I'll trust your advice rather than looking for a lazy way out haha. Is there any way to back up everything (even just apps, etc) without root though?
Cheers :good:

clarkey586 said:
Thanks a million.
I've not unlocked my bootloader, but I don't think it should be a problem there's plenty of tutorials etc for that.
Ideally, I'd not like to wipe my phone but alas it looks like that's going to be the case and I'll trust your advice rather than looking for a lazy way out haha. Is there any way to back up everything (even just apps, etc) without root though?
Cheers :good:
Click to expand...
Click to collapse
Yea, your warranty is void at this point anyways so why not just unlock it! I root and use TiBu.. so I've not tested other backup methods but I'm pretty sure there are backup apps on the playstore that don't require root you could try.
BUT, the step "fastboot erase userdata" is what erases your installed apps/setting and personal files, etc. Really you can just SKIP that step and you SHOULD be ok. Then your apps and settings will be there when you boot 6.0. I was just providing instructions for a fully clean flash. I would say you have a 98% chance it will be just fine though if you don't erase userdata.
EDIT* oh and IIRC you will probably get an error or weird msg with the gpt.bin part of the flash.. ignore it..
EDIT 2* Here is one such app that doesn't look like it requires root. If you go this route make sure you copy everything over to your PC after using the backup app if you are going to run the "fastboot erase userdata" command.
GOOD LUCK!
---------- Post added at 06:38 PM ---------- Previous post was at 06:07 PM ----------
Just out of curiosity.. I've just read some posts on here about people getting their phones back from repair and their bootloader says "Device is ENGINEERING" instead of "Device is LOCKED" or "Device is UNLOCKED".
What does yours say? I'm mainly just wondering if it being in ENGINEERING mode is why you are not getting the OTA...

DaMadOne said:
Yea, your warranty is void at this point anyways so why not just unlock it! I root and use TiBu.. so I've not tested other backup methods but I'm pretty sure there are backup apps on the playstore that don't require root you could try.
BUT, the step "fastboot erase userdata" is what erases your installed apps/setting and personal files, etc. Really you can just SKIP that step and you SHOULD be ok. Then your apps and settings will be there when you boot 6.0. I was just providing instructions for a fully clean flash. I would say you have a 98% chance it will be just fine though if you don't erase userdata.
EDIT* oh and IIRC you will probably get an error or weird msg with the gpt.bin part of the flash.. ignore it..
EDIT 2* .... is one such app that doesn't look like it requires root. If you go this route make sure you copy everything over to your PC after using the backup app if you are going to run the "fastboot erase userdata" command.
GOOD LUCK!
---------- Post added at 06:38 PM ---------- Previous post was at 06:07 PM ----------
Just out of curiosity.. I've just read some posts on here about people getting their phones back from repair and their bootloader says "Device is ENGINEERING" instead of "Device is LOCKED" or "Device is UNLOCKED".
What does yours say? I'm mainly just wondering if it being in ENGINEERING mode is why you are not getting the OTA...
Click to expand...
Click to collapse
Haha suppose you're right! Sure I'll probably just wipe my device in the end, be nice to have a clean go at MM haha.
The bootloader status was indeed locked so I don't know what's causing the issue?
Anyway, thanks a million for the help I'll update if/when all goes well :good:

Despite my best efforts, it seems to have been in vain. I'm getting an error when trying to unlock the bootloader (something along the lines of no backup available, please try again) which is common to people who have sent their phone in for repair.
I'm just wondering if I could flash the firmware regardless of bootloader (Odin maybe?) At this point I'm happy to root suit and boot I'm just a bit sick of moto at this stage so want to be able to control my phone haha.
Any help much appreciated

clarkey586 said:
Despite my best efforts, it seems to have been in vain. I'm getting an error when trying to unlock the bootloader (something along the lines of no backup available, please try again) which is common to people who have sent their phone in for repair.
I'm just wondering if I could flash the firmware regardless of bootloader (Odin maybe?) At this point I'm happy to root suit and boot I'm just a bit sick of moto at this stage so want to be able to control my phone haha.
Any help much appreciated
Click to expand...
Click to collapse
Odin is for Samsung. Moto has RSDLite. But if your bootloader is locked the firmware package must be signed by Moto and I don't thing the ones floating around the web are.
So this is the point where it seems you're stuck with the (possibly) more PITA way. What you need to do is find the OTA zip that goes from 5.1.1 -> 6.0 and use the stock recovery to flash that with ADB. Boot to stock recovery, press button sequence to get the menu (I THINK at the fallen android dude you hold vol up for a few seconds then hit the power button while still holding it.. it's something like that to get the actual useful menu) then towards the bottom is an update via ADB, plug phone into pc via usb and select that and then in terminal do "adb sideload <OTA_file>.zip" and it will flash the OTA, assuming your device passes it's check it will feel like it's taking forever. This method won't wipe your phone either.
EDIT* HERE is a post with a link to the EU OTA and much better instructions than mine You can flash it with adb sideload or like that post says by copying it to your phone before booting the recovery and flashing it.
And then.. assuming you get to 6.0 using that OTA hopefully you can trigger the february OTA to auto download. If not... HERE is a link to a post with the february OTA zip for your phone. Flash it the same as last one.
If flashing the OTA with a locked bootloader and stock recovery doesn't work I'm afraid you're either stuck or your phone is on a return path to Moto again.

DaMadOne said:
Odin is for Samsung. Moto has RSDLite. But if your bootloader is locked the firmware package must be signed by Moto and I don't thing the ones floating around the web are.
So this is the point where it seems you're stuck with the (possibly) more PITA way. What you need to do is find the OTA zip that goes from 5.1.1 -> 6.0 and use the stock recovery to flash that with ADB. Boot to stock recovery, press button sequence to get the menu (I THINK at the fallen android dude you hold vol up for a few seconds then hit the power button while still holding it.. it's something like that to get the actual useful menu) then towards the bottom is an update via ADB, plug phone into pc via usb and select that and then in terminal do "adb sideload <OTA_file>.zip" and it will flash the OTA, assuming your device passes it's check it will feel like it's taking forever. This method won't wipe your phone either.
EDIT* HERE is a post with a link to the EU OTA and much better instructions than mine You can flash it with adb sideload or like that post says by copying it to your phone before booting the recovery and flashing it.
And then.. assuming you get to 6.0 using that OTA hopefully you can trigger the february OTA to auto download. If not... HERE is a link to a post with the february OTA zip for your phone. Flash it the same as last one.
If flashing the OTA with a locked bootloader and stock recovery doesn't work I'm afraid you're either stuck or your phone is on a return path to Moto again.
Click to expand...
Click to collapse
Ah sure I'll give that a go! Just checking if there are any precautions I should be taking for this? Don't want to brick the phone without the ability to flash it back to life again!

clarkey586 said:
Ah sure I'll give that a go! Just checking if there are any precautions I should be taking for this? Don't want to brick the phone without the ability to flash it back to life again!
Click to expand...
Click to collapse
You should be fine. The OTA zip is going to check all of the files it is going to patch first and only upgrade if everything passes. If it finds ANYTHING amiss... it will refuse to flash it. If it refuses to flash it your only hope is to send it to Moto unfortunately.

DaMadOne said:
You should be fine. The OTA zip is going to check all of the files it is going to patch first and only upgrade if everything passes. If it finds ANYTHING amiss... it will refuse to flash it. If it refuses to flash it your only hope is to send it to Moto unfortunately.
Click to expand...
Click to collapse
You, my friend, are a hero.
That seems to have done the trick with no issues (going to see if I can potentially unlock the bootloader now) and I'm finally on MM haha. Seems I have to perform the Feb security update separately too for some reason but I'm not too worried about doing things manually.
Sent you a small token of my appreciation, have a pint on me
Thanks once again

clarkey586 said:
You, my friend, are a hero.
That seems to have done the trick with no issues (going to see if I can potentially unlock the bootloader now) and I'm finally on MM haha. Seems I have to perform the Feb security update separately too for some reason but I'm not too worried about doing things manually.
Sent you a small token of my appreciation, have a pint on me
Thanks once again
Click to expand...
Click to collapse
Sweet! Thanks for the pint! Glad you're updated now. Did it end up giving you the OTA for the February patch or did you have to use the 2nd OTA?

DaMadOne said:
Sweet! Thanks for the pint! Glad you're updated now. Did it end up giving you the OTA for the February patch or did you have to use the 2nd OTA?
Click to expand...
Click to collapse
Had to use the 2nd OTA.zip but I didn't really try any of the remove sim card stuff or waiting long. No unlockable bootloader either but I'm satisfied for the moment haha.

XT1642: IMEI show as 0 (even after reflashing to original unrooted)

Hi,
I have G4 Plus XT1642 (retapac). It came shipped with 6.0.1 MPJ24.139-48 preinstalled.
Well i flashed, deleted, maybe bricked and then made it work again with the latest version i wanted to have (139-63) and then rooted it. Everything worked/works, but the wifi mac shows as 02 000000 or something (but no problem with that, wifi mac is fixed with some earlier backup i have, it also gets fixed when i flash to original).
But the worst thing is: Both IMEI show as 0. In the setting menu, and also when dialing the command *#06# (Both IMEIs show 0).
It gave some errors at fastboot because of "downgrade" or so, but i think that's not the issue.
I tried everything, also reflashed to my original version (ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip). Everything is fine, wifi mac displays as original also, but IMEIs still are 0.
No matter what I do, both IMEI show as 0, and SIM cards don't work ofcourse (they work, show carrier names etc but don't get accepted, ---> "emergency calls only", because IMEI is 0 i think.
Before you ask: No i don't have a very early TWRP backup from before flashing, deleted it because I had later backup I though everything was working, didn't try any SIM at that time.
How can I fix this? Is there any hope?
What gives me the little hope: At "boot thing" when I type fastboot getvar imei, it shows the correct imei! It doesn't list the second sim though.
Thanks in advance!

bauss1 said:
Hi,
I have G4 Plus XT1642 (retapac). It came shipped with 6.0.1 MPJ24.139-48 preinstalled.
Well i flashed, deleted, maybe bricked and then made it work again with the latest version i wanted to have (139-63) and then rooted it. Everything worked/works, but the wifi mac shows as 02 000000 or something (but no problem with that, wifi mac is fixed with some earlier backup i have, it also gets fixed when i flash to original).
But the worst thing is: Both IMEI show as 0. In the setting menu, and also when dialing the command *#06# (Both IMEIs show 0).
It gave some errors at fastboot because of "downgrade" or so, but i think that's not the issue.
I tried everything, also reflashed to my original version (ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip). Everything is fine, wifi mac displays as original also, but IMEIs still are 0.
No matter what I do, both IMEI show as 0, and SIM cards don't work ofcourse (they work, show carrier names etc but don't get accepted, ---> "emergency calls only", because IMEI is 0 i think.
Before you ask: No i don't have a very early TWRP backup from before flashing, deleted it because I had later backup I though everything was working, didn't try any SIM at that time.
How can I fix this? Is there any hope?
What gives me the little hope: At "boot thing" when I type fastboot getvar imei, it shows the correct imei! It doesn't list the second sim though.
Thanks in advance!
Click to expand...
Click to collapse
https://firmware.center/firmware/Motorola/Moto G4 (Plus)/Stock/XT1642/
#for marshmallow
Try to flash modem files for your phone
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
#for nougat

BlackBeats said:
https://firmware.center/firmware/Motorola/Moto G4 (Plus)/Stock/XT1642/
#for marshmallow
Try to flash modem files for your phone
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
#for nougat
Click to expand...
Click to collapse
Yes. Did exactly that. Flashed the files of XT1642_ATHENE_6.0.1_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip ... with the commands
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Showed some "errors" at fastboot at some, but I think that was normal. And flashing worked.
But in the end, both IMEI are still 0.
Even reflashed the NON-HLOS.bin. IMEI numbers are still 0.

Additional information:
The original version this retapac XT1642 G4 plus came shipped with was MPJ24.139-48.
I then wanted to update to the latest non-nougat version, which is MPJ24.139-63.
I could not update directly to MPJ24.139-63 from MPJ24.139-48. (Because the internal recovery showed error, that flashed version must origin from MPJ24.139-23.4).
So I overflashed (with fastboot) to MPJ24.139-23.4. So the version then was even lower than it came shipped with lol. Then from MPJ24.139-23.4, used the internal recovery (not TWRP), to apply the OTA update file MPJ24.139-63. Since then the Wifi mac was 020000000 or something, sometimes random wifi disconnects, and imei 0. After going back to original again, wifi mac is fixed, but sim imei numbers still are 0.
Edit: not sure if the imei and wifi errors accured since MPJ24.139-23.4, or after the OTA update file, or sometime inbetween because i deleted something in TWRP.

bauss1 said:
Additional information:
The original version this retapac XT1642 G4 plus came shipped with was MPJ24.139-48.
I then wanted to update to the latest non-nougat version, which is MPJ24.139-63.
I could not update directly to MPJ24.139-63 from MPJ24.139-48. (Because the internal recovery showed error, that flashed version must origin from MPJ24.139-23.4).
So I overflashed (with fastboot) to MPJ24.139-23.4. So the version then was even lower than it came shipped with lol. Then from MPJ24.139-23.4, used the internal recovery (not TWRP), to apply the OTA update file MPJ24.139-63. Since then the Wifi mac was 020000000 or something, sometimes random wifi disconnects, and imei 0. After going back to original again, wifi mac is fixed, but sim imei numbers still are 0.
Click to expand...
Click to collapse
Try flashing nougat I guess downgrade created a problem

BlackBeats said:
Try flashing nougat I guess downgrade created a problem
Click to expand...
Click to collapse
I don't want nougat. Can I go back to MPJ24.139-63 from nougat? But maybe worth a try if nobody knows any other possibility

bauss1 said:
I don't want nougat. Can I go back to MPJ24.139-63 from nougat? But maybe worth a try if nobody knows any other possibility
Click to expand...
Click to collapse
Try removing oem fb set command
If it doesn't work then flash nougat then use 6.0.1 custom ROM
Edit fb_mode_set

Flashed everything again, without the fastboot oem fb_mode_set (MPJ24.139-48). Both IMEIs are still 0, everything else is fine though, original wifi mac.
---
Then took original over the air update it offered me (NPJ25.93-14). Installed without problems.
But, guess what.... it made things worse.
Now i am on NPJ25.93-14, the IMEIs still are 0, and the wifi mac address is at 02:00:00:00:00:00 again.
What I noticed is, in settings it shows the IMEI SV (Slot1) and IMEI SV (Slot2). They both changed to 08. I think they were 03 or so before.
Edit: In the boot recovery thing it says the usual stuff:
Battery OK (Charging)
flashing_unlocked
Software status: Official
...
So... updating to Nougat did not help, made things worse (wifi mac weird again, IMEI still 0).
Any other ideas?

Anyone looking for the solution to this problem, it has been fixed here: [Guide] [XT16XX] [Solve] Moto G4/Plus IMEI=0 issue

LS 997 root or unlock bootloader?

I am new to LG devices... this is the first lg device for me.
I am on ZVA latest software version.
I want to have root in my phone or unlock the bootloader to install lineagos roms.
Could I do these two things without any risks to hard brick the phone?
I am familiar with adb and fastboot instructions.
Thank you.

If you can find out what ARB version you are on (I hear that Sprint pulled access to that hidden menu), and it is still 0, then maybe.
I am working to find a model that has a KDZ that is close enough to the LS997 that it will boot. If it will boot, then it can be rooted, and the proper firmware flashed back onto the phone.
-- Brian

The apk in first post of this thread may give you access to hidden menu. Let us know if it worked please
https://forum.xda-developers.com/v20/help/lg-v20-cdma-to-lte-gsm-switch-via-t3602409

loopytee said:
The apk in first post of this thread may give you access to hidden menu. Let us know if it worked please
https://forum.xda-developers.com/v20/help/lg-v20-cdma-to-lte-gsm-switch-via-t3602409
Click to expand...
Click to collapse
I think you are talking about unlock CDMA or GSM service.
But I am talking about unlocking bootloader and root.
I think this app doesn't work anymore since the production and lab menu couldn't be accessed.
But as I understand the main problem is how to return to the stock after root?

runningnak3d said:
If you can find out what ARB version you are on (I hear that Sprint pulled access to that hidden menu), and it is still 0, then maybe.
I am working to find a model that has a KDZ that is close enough to the LS997 that it will boot. If it will boot, then it can be rooted, and the proper firmware flashed back onto the phone.
-- Brian
Click to expand...
Click to collapse
What is ARB stands for?
Got it
Anti Rollback=1

anees02 said:
What is ARB stands for?
And how to obtain it?
I have came from Samsung world so don't know a lot about LG.
Click to expand...
Click to collapse
Anti roll back---Arb
In hidden menu. (if you can access it)
Choose SVC Menu then choose Version and scroll to the bottom. You will see Anti-Rollback Version.

loopytee said:
Anti roll back---Arb
In hidden menu. (if you can access it)
Choose SVC Menu then choose Version and scroll to the bottom. You will see Anti-Rollback Version.
Click to expand...
Click to collapse
Yes Got it
In my case ARB=1
What does that mean?
Couldn't flash old firmware?

anees02 said:
I think you are talking about unlock CDMA or GSM service.
But I am talking about unlocking bootloader and root.
I think this app doesn't work anymore since the production and lab menu couldn't be accessed.
But as I understand the main problem is how to return to the stock after root?
Click to expand...
Click to collapse
I am only referring to the apk linked in the first post. I realize that thread is not what you are looking for.
Did the apk work for you to access hidden menu? What zv# are you on?

loopytee said:
I am only referring to the apk linked in the first post. I realize that thread is not what you are looking for.
Did the apk work for you to access hidden menu? What zv# are you on?
Click to expand...
Click to collapse
Yes the app works and it said
ARB=1
And I am on ZVA software version.

Unfortunately there isn't any firmware out there that is ARB version 1 AND December 2016 security patch or older, so no, you can't root at this time.
I am guessing ZVA incremented ARB because ZV9 is still ARB 0.
-- Brian

anees02 said:
Yes the app works and it said
ARB=1
And I am on ZVA software version.
Click to expand...
Click to collapse
Ok thanks
Here is the current info about Arb and whats being worked on. As far as I know if your Arb is anything other then 0 then you can't root yet. I say yet because there is some great work being do with alot of hope for all.
Here are some links to whats going on currently
https://forum.xda-developers.com/v20/help/want-help-rooting-security-patches-t3680397
https://forum.xda-developers.com/v20/how-to/laf-download-mode-how-root-t3676011

runningnak3d said:
Unfortunately there isn't any firmware out there that is ARB version 1 AND December 2016 security patch or older, so no, you can't root at this time.
I am guessing ZVA incremented ARB because ZV9 is still ARB 0.
-- Brian
Click to expand...
Click to collapse
I think so. ARB
On ZV9 it was 0.
On ZVA it's 1.
So I have to wait until there's a method that doesn't matter about ARB value.

You could still do a really awesome thing for the people that are already rooted, or are about to be rooted -- dump your phone so that they can't have the latest firmware.
If you wouldn't mind, grab a copy of the patched LG UP, and use the dump function. This can not harm your phone in ANY way. What it does is reads the partitions on your phone, and saves them out to files.
We need:
aboot
abootbak
apdp
boot
cmnlib
cmnlib64
cmnlib64bak
cmnlibbak
devcfg
devcfgbak
factory
hyp
hypbak
keymaster
keymasterbak
laf
lafbak
modem
msadp
persist
pmic
pmicbak
raw_resources
raw_resourcesbak
rct
recovery
recoverybak
rpm
rpmbak
sec
system
tz
tzbak
xbl
xbl2
xbl2bak
xblbak
You can leave the rest unchecked. They are either not needed, or unique to your phone.
-- Brian

runningnak3d said:
You could still do a really awesome thing for the people that are already rooted, or are about to be rooted -- dump your phone so that they can't have the latest firmware.
If you wouldn't mind, grab a copy of the patched LG UP, and use the dump function. This can not harm your phone in ANY way. What it does is reads the partitions on your phone, and saves them out to files.
We need:
aboot
abootbak
apdp
boot
cmnlib
cmnlib64
cmnlib64bak
cmnlibbak
devcfg
devcfgbak
factory
hyp
hypbak
keymaster
keymasterbak
laf
lafbak
modem
msadp
persist
pmic
pmicbak
raw_resources
raw_resourcesbak
rct
recovery
recoverybak
rpm
rpmbak
sec
system
tz
tzbak
xbl
xbl2
xbl2bak
xblbak
You can leave the rest unchecked. They are either not needed, or unique to your phone.
-- Brian
Click to expand...
Click to collapse
Ok.
I will search for the patched version of LG UP.
And I hope that I find a time to charge my laptop and dump these partitions.

Some quick instructions for you:
Download the patched LG UP from this thread: link.
Make sure you install it in C:\Program Files (x86)\LG Electronics\LGUP or it will either read the wrong model file (if you had a previous installation of LG UP), or it will not be able to find the model file at all.
Put your phone into download mode (power off / hold vol. up / plug in USB cable)
Use LG UP to dump your phone. When you run it, there will be additional radio buttons.
Pick the one that says DUMP and click Start. You will be asked what partitions to dump, please check all the partitions listed above.

runningnak3d said:
Some quick instructions for you:
Download the patched LG UP from this thread: link.
Make sure you install it in C:\Program Files (x86)\LG Electronics\LGUP or it will either read the wrong model file (if you had a previous installation of LG UP), or it will not be able to find the model file at all.
Put your phone into download mode (power off / hold vol. up / plug in USB cable)
Use LG UP to dump your phone. When you run it, there will be additional radio buttons.
Pick the one that says DUMP and click Start. You will be asked what partitions to dump, please check all the partitions listed above.
Click to expand...
Click to collapse
I already dump the required partitions but LG UP recognized my software version ZV6 and it is really ZVA as shown on the attatched pic.
The size of the folder before compression is 5.88 GB. after compression 2.53 GB.
What about the difference in version between LG UP and the real version?

I see ZV6 in the attached pic. That is weird. Obviously you aren't on ZV6 if you are ARB 1. If you don't mind, can you zip those up and post a link? The files I had you dump are the exact files that you get from a KDZ so there is no personal info.
-- Brian

runningnak3d said:
I see ZV6 in the attached pic. That is weird. Obviously you aren't on ZV6 if you are ARB 1. If you don't mind, can you zip those up and post a link? The files I had you dump are the exact files that you get from a KDZ so there is no personal info.
-- Brian
Click to expand...
Click to collapse
Yes I am now uploading the zip file but the internet is very slow that before 4 hours I have started the uploading,until now it only upload 750 MB of 2.53 GB.
So if the uploading process finished successfully I will pm the link to your inbox.

This is from about phone>>software version

runningnak3d said:
I see ZV6 in the attached pic. That is weird. Obviously you aren't on ZV6 if you are ARB 1. If you don't mind, can you zip those up and post a link? The files I had you dump are the exact files that you get from a KDZ so there is no personal info.
-- Brian
Click to expand...
Click to collapse
PM sent to you.

F'd up hard, would need some assistancea restoring stock

Didn't want to post because I thought I would solve the issue with a simple MiFlash restore to stock, but oh well, here I go:
Due to my excitement about the Pie update (Beta), I got a fastboot flashable zip that was posted on a thread and attempted to flash it myself, manually.
Commands I executed (one by one, not through the bat script):
Code:
fastboot flash sbl1 sbl1.img
fastboot flash sbl1bak sbl1.img
fastboot flash rpm rpm.img
fastboot flash rpmbak rpm.img
fastboot flash tz tz.img
fastboot flash tzbak tz.img
fastboot flash devcfg devcfg.img
fastboot flash devcfgbak devcfg.img
fastboot flash dsp dsp.img
fastboot flash aboot aboot.img
fastboot flash abootbak aboot.img
fastboot flash lksecapp lksecapp.img
fastboot flash lksecappbak lksecapp.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlibbak cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cmnlib64bak cmnlib64.img
fastboot flash keymaster keymaster.img
fastboot flash keymasterbak keymaster.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot set_active a
I probably should never have flashed all this but I will explain what happened in case someone more savvy knows exactly what happened and lends a helping hand.
So all the commands passed fine, except for the fastboot flash system ones. I executed the first one and it flashed parts of 500mb or so on the partition, around 6 times. Same on the system_b.
I suppose that these flash onto the different slots (A/B), correct me if I'm wrong. Then rebooted and it would bootloop (don't blame anyone since I f'd up) and I was like "Okay then, guess I will restore with MiFlash.
Well I did. First weird thing to notice, it would only take around 213 seconds, while it would normally take around 300 seconds so I suspected I might have messed up. Note that I always restore to the April security patch to be able to enable Camera2API. Booted fine, then it was time for me to input my SIM's PIN. I do so, and a message shows up saying "SIM PIN operation failed" and after that it would close and re-open the PIN prompt, basically every time I tried to type the PIN. It basically wouldn't even let me input the PIN itself. Sometimes, if I'm fast enough I can successfully submit it but it's still messed up and doesn't work properly.
I know, I shouldn't have flashed the thing in the first place (since it's also supposed to be confidential), but I did and I regret doing so. For anyone interested, the bootloader is unlocked and I can enter fastboot mode normally. Didn't try flashing a different stock image since this is the one I always use and it works.
If anyone has got any idea about what happened here and if there's any solution, I would be really thankful.

Update: Also tried flashing one of the 8.1 fastboot images. It flashed without errors. While booting though, it crashed like 2 seconds after asking for my PIN.

michkost858 said:
Update: Also tried flashing one of the 8.1 fastboot images. It flashed without errors. While booting though, it crashed like 2 seconds after asking for my PIN.
Click to expand...
Click to collapse
Try booting without simcard, if you are able to boot, toggle off sim pin from settings and try booting with simcard

apexashwin said:
Try booting without simcard, if you are able to boot, toggle off sim pin from settings and try booting with simcard
Click to expand...
Click to collapse
Have tried this. Boots fine without SIM card. In fact, even with the SIM card in I can press the back button and skip the prompt but it will pop up again. But I still can't properly use the SIM

Why flash April update? You can enable camera2api on any ota update! :/

WhatzIt2Ya said:
Why flash April update? You can enable camera2api on any ota update! :/
Click to expand...
Click to collapse
I don't think it's what matters at the moment.

michkost858 said:
I don't think it's what matters at the moment.
Click to expand...
Click to collapse
Ugh, yes it does. You need the latest modems etc. for it to flash properly. That's why, you see in custom rom threads say, 'you must be on latest stock firmware before flashing'.
---------- Post added at 10:12 AM ---------- Previous post was at 10:11 AM ----------
michkost858 said:
I don't think it's what matters at the moment.
Click to expand...
Click to collapse
So, before you flash pie beta update. You MUST be on latest November update for it to flash properly.

WhatzIt2Ya said:
Ugh, yes it does. You need the latest modems etc. for it to flash properly. That's why, you see in custom rom threads say, 'you must be on latest stock firmware before flashing'.
---------- Post added at 10:12 AM ---------- Previous post was at 10:11 AM ----------
So, before you flash pie beta update. You MUST be on latest November update for it to flash properly.
Click to expand...
Click to collapse
Just to be clear. I wasn't trying to flash any extra firmware after failing to install the Pie Beta flashable. I tried rolling back to stock.
Also, I was in the latest November update, before flashing the Pie beta flashable, so that's not what's wrong.
About the reason I flash the April update, it's just so I don't get wipes when I lock/unlock the bootloader on the process of enabling Camera2API.
Right now, I just want to get back to stock, didn't try flashing the Pie beta a second time after I failed and I won't.

Also my IMEIs are correct, if that matters in any way. I believe something got corrupted in the partitions (might be bsing) but yeah. Now whatever version I'm on (7.1,8.0,8.1) the issue still persists.
So I'd like to make a full restore, from the ground up, I suppose.

Try install lastest stock firmware using Miflash with Mi A1 in EDL Mode (search here in the forum how to get it there). If it works, then you can flash April firmware or do whatever you want.

nitroax said:
Try install lastest stock firmware using Miflash with Mi A1 in EDL Mode (search here in the forum how to get it there). If it works, then you can flash April firmware or do whatever you want.
Click to expand...
Click to collapse
I guess I can try that but will that be any different than flashing the same firmware with MiFlash on fastboot?
Also, should I change something on the flash scripts of the fastboot images so that they work properly on EDL mode (saying this cause I read somewhere that they shouldn't have the 'fastboot reboot bootloader' command to prevent bricks, might be bs)?

michkost858 said:
I guess I can try that but will that be any different than flashing the same firmware with MiFlash on fastboot?
Also, should I change something on the flash scripts of the fastboot images so that they work properly on EDL mode (saying this cause I read somewhere that they shouldn't have the 'fastboot reboot bootloader' command to prevent bricks, might be bs)?
Click to expand...
Click to collapse
I had a similar problem. Solved restoring persist and EfS backup.

sipollo said:
I had a similar problem. Solved restoring persist and EfS backup.
Click to expand...
Click to collapse
Hmm, I don't have such a backup. Is there a way to restore one?

michkost858 said:
Have tried this. Boots fine without SIM card. In fact, even with the SIM card in I can press the back button and skip the prompt but it will pop up again. But I still can't properly use the SIM
Click to expand...
Click to collapse
I've read this is a November patch bug, apparently it works only if your system language is set to English. Try booting without SIM, change your system language to English(US) if it isn't already, remove PIN lock from your SIM-card. Then insert SIM again and see if you can boot without problems... If yes, then you have to either keep your system language English or keep SIM PIN lock disabled.
michkost858 said:
Hmm, I don't have such a backup. Is there a way to restore one?
Click to expand...
Click to collapse
A zip with backups you can place on your internal storage and restore from TWRP is floating around in THIS thread, try looking it up. There is also extensive discussion over this problem with potential solutions.

manpildo said:
I've read this is a November patch bug, apparently it works only if your system language is set to English. Try booting without SIM, change your system language to English(US) if it isn't already, remove PIN lock from your SIM-card. Then insert SIM again and see if you can boot without problems... If yes, then you have to either keep your system language English or keep SIM PIN lock disabled.
A zip with backups you can place on your internal storage and restore from TWRP is floating around in THIS thread, try looking it up. There is also extensive discussion over this problem with potential solutions.
Click to expand...
Click to collapse
Yes this is a known bug. This should fix pin issue

manpildo said:
I've read this is a November patch bug, apparently it works only if your system language is set to English. Try booting without SIM, change your system language to English(US) if it isn't already, remove PIN lock from your SIM-card. Then insert SIM again and see if you can boot without problems... If yes, then you have to either keep your system language English or keep SIM PIN lock disabled.
A zip with backups you can place on your internal storage and restore from TWRP is floating around in THIS thread, try looking it up. There is also extensive discussion over this problem with potential solutions.
Click to expand...
Click to collapse
.:Addicted:. said:
Yes this is a known bug. This should fix pin issue
Click to expand...
Click to collapse
Thanks for pointing me in the right direction. Will be watching over the thread linked.

G6 Bootloader info

Hiya guys!
So, I've been plucking away at trial and error with my G6 (H873 Canadian) now that I have edl to fall back to and by using qdloader flashes to write my nand I have written my device with a hybrid of the pie beta 29a and an unlocked us997 aboot. after modifying the devinfo partition... my magisk modified boot image gets me as far as my lockscreen. I can login but my background is black. if I open magisk manager it shows it as installed but then crashes seconds later. ideas? I have very minimal knowledge of the partition structure and the chain of trust for this device and I am absolutely sure it's my mistake so maybe someone who is kind enough and has the time could explain a bit more to me about the inner workings of this mishmash bootup and possibly help me fix it to remain booted? Preferrable if I don't have to downgrade by the way pie has saved this device performance wise.

After more screwing about I somehow relocked the bootloader and the key that worked before is now rejected. Any help?

No further luck but it doesn't matter. the boot loops have stopped and my changes are intact. h873 running dual speaker mod and adblocking hosts file. root, however, is not still functioning and my attempted viper4android install is in some weird instant reboot to bootloader limbo.

If I can do it by simply ****ing around I'm confident someone can do more than me with enough time and knowledge. I'm not giving up either. I just honestly don't know what I'm doing. I do caution anyone who messes with this sort of stuff to dump a full partition level backup of your phone. I know I nearly lost my misc partition (imei won't work right without it) and was saved by an earlier dump in my preliminary testing

H873: Question what aboot did you use and how did you modify the devinfo partition? Ive literally been working on the aboot in Ghidra for 5 weeks, I have root in system with a modified su98, system is not currently mountable because it is not referenced in /proc/mounts . From what I can gather the devinfo must have 0x2 at both 0x10 and 0xe0 while both are equal to 2 and device reset is called the unlock bit in rpmb is equal to Y else it is N then it will erase unlock key from rpmb. Also im not afraid of bricking I have been in edl mode well over 50 times and have explored every single partition on this thing. I have the aboot for US997 unlocked variant and the files from runningnak3d's AFH. The fastboot portion of the aboot when looking at the de-compiled code in Ghidra is extremely small and strict.