Develop Bugs

Some Important info about Imei 0, No 4G, imei not back after flashing 8.1 rom.

Hi friend,
I installed custom rom 8.1 with twrp 64 bits and it was working fine. then i installed stock rom with fastboot mode and lost my imei.
went back to 8.1 rom and got imei back. I had already taken back up of my stock rom previously. so I though I should try that may be I will get imei back on stock. tried that and got Imei back on stock. everything fne till now.
now I have no 4G and started to fix 4G. flashed some back up found on some form thought may b it will resolve the issue.
restarted and no 4g.
tried to flash stock again and lost imei again.
now tried to flash custom 8.1 still no imei.
went back to back ups still no imei.
tried everything still no imei.
I don't know what happen.
Now lets discuss and fix this issue once for all.
Found some important information about our issue:
Network Related Partitions
modemst1 and modemst2: These partitions appear to contain non-essentials/temporary network related data. Interestingly, they are erased when flashing a stock rom, meaning they are probably not crucial, possibly some kind of ‘baseband cache’?
modem: The modem partition contains modem/baseband related files. These files store store settings that allow the device to communicate with cell towers, such as the frequencies. This partitions is region, not device, specific. This partition is flashed as part of the stock firmware flash procedure, so it also is likely not unique (again ensure to get firmware for the right region).
fsg: This partition also contains files related to the modem firmware/baseband. These files store store settings that allow the device to communicate with cell towers, such as the frequencies. This partitions is region, not device, specific. This partition is flashed as part of the stock firmware flash procedure, so it likely contains non-unique data (but ensure to get firmware for the right region).
Maybe ‘fsg’ and ‘modem’ are related to the modemst1 and modemst2 partitions?
Important/Unique Partitions
pds: This partition likely contains important device specific data like the IMEI, Serial Number, etc. It is important to backup this partition when you get the chance, as people in other threads attribute the loss of the IMEI to this partition. This is not included in stock firmware, reinforcing the importance of backing up this partition.
persist: Apparently this partition contains files related to WiFi, Bluetooth, MAC addresses etc. Nevertheless, it is quite important and should be backed up if possible.
hob and dhob: The exact function is not known, but they appear to contain very important information relating to the modem and/or IMEI.
fsc: Appears to be empty. Although, this partition could sometimes store important IMEI related info. Not included in factory firmware and so best left alone.
IMEI backup/restore scripts (pds partition)
Requirements:
- Device has to be rooted, with USB debugging enabled.
- Motorola fastboot (see attachment).
- ADB installed, minimal or the full ADK.
You can search the forum to find how to meet these requirements or for the terms described in this post beginning here:
http://forum.xda-developers.com/show....php?t=2558638
Installation:
Extract imei_scripts.zip (attached) and copy the scripts "imei_backup.bat" and "imei_flash.bat" into the ADB root directory.
Extract mfastboot_only.zip (attached) and copy "mfastboot.exe" into the ADB root directory.
Description/How to use:
These are batch scripts and can be run by double-clicking them or opening a command window from the ADB root. Help is also contained in the scripts. They are run interactively and won't execute anything without the user selecting a choice.
"imei_backup.bat"
Use this script to backup and restore normally using ADB.
"imei_flash.bat"
Use this script to flash the partition as an alternative to the other method using mfastboot while in bootloader mode. The backup, "pds.img" must be located in the ADB directory for the script to run.
The backup is made on the sdcard and is named "pds.img". You'll want to store this elsewhere once backed up. Once done, that's it! You don't need to do anything more. The purpose is as a preventative in the event of the loss of your IMEI.
Run the scripts for additional options and help.
Sources/Interesting information:
https://forum.xda-developers.com/moto-g/general/motorola-moto-g-partitions-explained-t3418644
https://forum.xda-developers.com/showthread.php?t=2675326
DISCLAIMER: Every information is form internet and xda and I will not be responsible for any loss of data or corrupt phones or sd card. That is, use only at your own risk!
Thanks to eastdata for making scripts.
And Professor Gibbins for providing important info.

Good evening. I am from Brazil and I am exactly with this problem. Since I do not speak English (sorry for this) I translated it through Google, but everything was confusing. Does this procedure go back to working the 4G or just backs up earlier to avoid this problem in the future? (but once sorry for not understanding the text) thank you.

When my Cedric was still alive, I tried to update the bootloader and the baseband to the latest January version using fastboot. I didn't touch the current ROM (LineageOS 15.1 unofficial). I flashed the following files to their adequate partitions: adspso.bin, bootloader.img, fsg.mbn, NON-HLOS.bin, and oem.img. The device worked well and was updated perfectly. Then... my curiosity got the best of me. Since the fastboot ROM includes commands to erase the modemst partitions, I thought it would be good to perform that operation (despite everything working well, stupid me). THIS killed IMEI for me:
Code:
fastboot erase modemst1
fastboot erase modemst2
My attempts to recover from this situation led me to try to downgrade to the November update, which ended in a dead device after trying to flash the November full ROM using RSD-Lite. I hope my experience can serve as a warning for others.

"If it ain't broke, don't fix it."
But then again, I've made that mistake many times as well xD

Cedric imei
Do I have to erase modemst1 and. 2 to install backup

ERROR MODE Attention! Please update system again.

Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!

Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system

mrmazak said:
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system
Click to expand...
Click to collapse
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore

Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
I give my phone to a friend to work on it. If he can't fix it I try new multi tools version to flash phone.

Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk

Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
I ever have similiar problem with you dude, but it's solved now, if you always stuck on " its OK but when my phone want to start its stuck on google page "just a sec...", its call google accont verification, i'll by bypass with this script, save as to .bat and put on adb folder
adb devices
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
adb shell am start -n com.google.android.gsf.login/
adb shell am start -n com.google.android.gsf.login.LoginActivity
pause
in fastboot type:
fastboot -w
after all it's works to me to bypass google account verification
and if now your problem is
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
i solve with re-flash system from this
https://androidfilehost.com/?fid=673956719939830152
fastboot flash system system.img
and doing TWRP Flashing
https://forum.xda-developers.com/devdb/project/?id=25826#downloads
fastboot flash recovery_ramdisk complete_twrp_ramdisk.img
and voila my problem solved..

mrmazak said:
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk
Click to expand...
Click to collapse
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (

Mohammadreza76646 said:
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (
Click to expand...
Click to collapse
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595

mrmazak said:
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595
Click to expand...
Click to collapse
It have stock recovery.

Mohammadreza76646 said:
It have stock recovery.
Click to expand...
Click to collapse
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)

mrmazak said:
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)
Click to expand...
Click to collapse
No. System boot successfully!
I will send you screenshot:

Mohammadreza76646 said:
No. System boot successfully!
I will send you screenshot:
Click to expand...
Click to collapse
here you are

Mohammadreza76646 said:
here you are
Click to expand...
Click to collapse
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.

mrmazak said:
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.
Click to expand...
Click to collapse
Thanks )
I'm so sorry for my posts, it's because I don't have a stable connection and I can't see notification of my thread.
I gave my phone to friend an he fix IMEI (I don't know how)
But OEM is steel lock.
I think he did it with using special box.

Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!![/QUOTE
Are u able.to boot into twrp ?
Click to expand...
Click to collapse

Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?

IonDEfeso said:
Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?
Click to expand...
Click to collapse
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)

mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.

mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Do you know what the boot.img files name is after extraction?
I have extracted all 3 update zips and cannot find anything called boot.img
By the way, thank you.. After updating magisk I have been dealing with failed recovery and failed boot for over a week and this is the first reply anywhere that looks promising

IonDEfeso said:
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.
Click to expand...
Click to collapse
if you were on oreo. then there is not a boot.img, instaed there is seperate ramdisk.img and kernel.img.
i have all the files already extracted for oreo and a backup from nougat as well.
https://androidfilehost.com/?w=files&flid=265998
make sure you know what you are doing before flashing.
for example. on oreo the boot and recovery share one kernel image. SO if kernel is messed up you will not be able to boot "boot" or "recovery"

[HOW-TO] Revert from an Oreo Custom ROM to stock and install Official Oreo via OTA

I decided to make this thread so people won't brick their devices/lose their IMEI/explode their phone when trying to update to the recently leaked/released Oreo Motorola ROM.
This is very information dense. Please, read this and the linked threads carefully and do not miss any step unless told so.
WARNING: This will erase all your data, reset all your settings. MAKE BACKUPS.
I also do not hold responsibility for any negative outcomes out of following this tutorial.
Always look for as many sources of information as you can. There is always something that isn't 100% correct in every tutorial.
Also, making it clear. This is for those who are currently on an Oreo CUSTOM ROM such as Lineage, Pixel Experience or other.
Preparation Steps:
Backup all your important files to your PC. You should do that since everything will be reset.
Make sure your phone is well charged. 80% at least. You want to be safe.
Boot into fastboot.
Install Minimal ADB and Fastboot.
In the command prompt of Minimal ADB and Fastboot, type:
Code:
fastboot getvar all
You will see a bunch of lines come up on the screen. Scroll and look for
Code:
(bootloader) ro.build.fingerprint[0]
.
This will tell the last version of the Stock ROM (Nougat) you had installed.
Example: "NPNS25.137-92-4" Yours won't/may not be the same.
Write it down somewhere. You will need this version number.
Open this link https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ to download the exact version you found. If anything, download a version above the one you found. Never an inferior. Those are Motorola's Official Nougat ROMs.
Keep it somewhere accessible in your PC and extract the zip. Remember where you put it, you will need it later.
You will now proceed to check your persist partition. Aka: The thing everyone overlooks and screws your IMEI.
IMPORTANT: Take a look at https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147 to find out if your persist partition has permission issues and see if it's recoverable. It is 99% likely that if you are on a custom Oreo ROM that the permissions won't be intact.
If that is the case (most likely), download NZedPred's TWRP Persist Restore zip into your phone.
Feel free to skip these last steps if you have a backup of your persist and efs.
Reboot into recovery and using the most recent TWRP make a backup of your persist and efs. (Information about this can be found on the second post of the "Fix Persist" thread. I am not willing to write a thousand instructions on one thread for the sake of not overcomplicating things.) //****ty steps: have/flash most recent TWRP > backup > select persist and efs > profit
These backups should be on a TWRP folder of the internal storage of your Moto G5. Reboot the phone (or mount USB) and copy that folder to your PC. In case anything goes wrong you will have a copy of your persist.
Steps:
Reboot into recovery (TWRP) using your preferred method. (Be it by the buttons, or via ADB (adb reboot recovery)).
Flash the TWRP Persist Restore zip.
Reboot into bootloader
Open (on your PC ofc) the folder with the extracted files of the Stock ROM zip (NOUGAT).
Open the extracted files folder then press Shift+RMB (Right Mouse Click/Button) and select "Open Command Prompt here" (It may work with Powershell??? If anything, write a post here)
For a quick test, type
Code:
fastboot
In case an error pops-up and tells you that it can't recognize such a command. Follow this article https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/ to add Minimal ADB and Fastboot to your system environment variables
Now, make sure that the path to the left of the typing cursor is the path of the folder where you have your extracted Nougat ROM files.
Please, for your phone's OTA update ability sake. Make sure that you are flashing the exact version you had before. The version you found by running fastboot getvar all.
The commands below will attempt to update the bootloader and gpt. You should NEVER flash an older version of the bootloader.
If you wish, you can skip the GPT/Bootloader commands. I haven't done myself because I flashed the correct version I had before anyway.
Copy and paste these commands and press enter in the CMD.
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 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
This will flash the Stock Nougat ROM you have downloaded and will reboot your phone. If all goes well you will be back on Nougat, set up your device as normal.
Attention, everything has been reset, erased, wiped.
Oreo OTA Steps:
After setting up everything, check for OTA's. You should be safe to install them. If you are on a recent firmware, you may only need to install security ones. Keep installing and checking until it says there are no more updates available.
This is where people **** up when they downgrade their bootloader by flashing an older Stock ROM than the one they had before.
Before proceeding, double check that there aren't any OTAs available or that Oreo is available at the time of reading this.
If Oreo is officially available, skip all of these steps and be happy.
Otherwise, if at the time of reading, there is a ZIP of the Oreo ROM that matches your region. Download it.
In case of RETLA, RETBR, and RETIN, at the time of writing, this is the correct file:
https://mega.nz/#!DxdSVaJb!5VEht-s6HYCNOZ2hXXVIPdFBqmWCuAvQL1Wzmp7rhZk or https://drive.google.com/open?id=1ZmtSW40oZi1EXD0PsRib3dqIeF9vauAY
In case you are on RETUS, RETAPAC, RETEU, etc. You may need another file that may not be available. The best course of action would be to wait for the Official OTA. :good:
Download it and put in the root of the internal storage of your Moto G5 Plus.
Go to the Settings app. In the Settings app, you'll want to find the OTA App (Motorola Update Services) by showing System apps and enable storage permissions.
Before you proceed: This is apparently indeed the official OTA that they will ship, which seems to be the same as the Soak 4. It's seemingly stable here, so, you should be fine to use that.
Check on your phone for an OTA.
Reboot it.
Check for an update again. There will be a prompt telling you about copying "system" files. Accept it.
After a while, another prompt will ask you about the update. There won't be a changelog, this is normal. Make sure your device is charged and install it.
Wait for the update to complete and you're done.
Tips:
You can also refer to this thread for some more information about fastboot flashing:
https://forum.xda-developers.com/g5-plus/development/stock-firmware-npn25-137-67-5-fastboot-t3694738
Refer to this thread if you need persist information:
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
Google and XDA are your friends.
It's good practice to wipe/reset your phone after you're done. Updates usually leave dirt behind. I haven't personally done this myself and everything is OK, but still...
Feel free to correct me on any mistake. It took me about an hour (or more) to write this and I could have potentially overlooked an important detail.

I flashed OPS28.85-13 by TWRP and when I put fastboot getvar all show me: ro.build.fingerprint[0] OPS28.85-13, so what should I do to flash the official OTA without troubles?, I read that probably I should flash nougat flashable by TWRP and then install Official Nougat and then Official Oreo , what do you think? Thanks!

TheGameExtreme said:
I flashed OPS28.85-13 by TWRP and when I put fastboot getvar all show me: ro.build.fingerprint[0] OPS28.85-13, so what should I do to flash the official OTA without troubles?, I read that probably I should flash nougat flashable by TWRP and then install Official Nougat and then Official Oreo, what do you think? Thanks!
Click to expand...
Click to collapse
Maybe I didn't explain the purpose of this thread...
This is meant for those who are currently in a CUSTOM Oreo ROM such as Lineage, Pixel Experience.
I assume you have the correct firmware installed already. No need to revert anything.
Well, that's what it says here.
Code:
(bootloader) ro.build.fingerprint[0]: motorola/potter_nt/potter_nt:8.1.0/OPS28.85-13/b8ea:user/release-keys
I don't think you need to do anything.
However, what's the bootloader version? Should be:
Code:
(bootloader) version-bootloader: moto-msm8953-C0.92

I had hardbricked my phone and am using a tarp flashablr stock ROM. Can I use this method to go back to stock?

BlackScout said:
Maybe I didn't explain the purpose of this thread...
This is meant for those who are currently in a CUSTOM Oreo ROM such as Lineage, Pixel Experience.
I assume you have the correct firmware installed already. No need to revert anything.
Well, that's what it says here.
Code:
(bootloader) ro.build.fingerprint[0]: motorola/potter_nt/potter_nt:8.1.0/OPS28.85-13/b8ea:user/release-keys
I don't think you need to do anything.
However, what's the bootloader version? Should be:
Code:
(bootloader) version-bootloader: moto-msm8953-C0.92
Click to expand...
Click to collapse
It says: version-bootloader: moto-msm8953-C0.8C, I think it's an older version because before to install Oreo by TWRP I had Nougat with the March security patch

TheGameExtreme said:
It says: version-bootloader: moto-msm8953-C0.8C, I think it's an older version because before to install Oreo by TWRP I had Nougat with the March security patch
Click to expand...
Click to collapse
Yeah, your bootloader is still from Nougat. One day, that could become a problem (hard brick) when taking OTA's.
You can easily fix that by going back to Nougat. (Just make sure to flash the exact version (or one above) the one you had before. Remember, never downgrade your bootloader.).
I think you can just fastboot flash NPNS-25.137.92-14 (since the difference between that and the base 92 patch is just security patches...), download the OTA zip that's been posted around and follow the last set of instructions here (The ones labeled Oreo OTA Steps)
Remember, flashing those TWRP zips made by NZedPred is technically not the same thing as fastboot flashing or taking an OTA. These zips don't upgrade your bootloader and the OP of those threads do not recommend you to take any OTAs.
Quoting from the source: https://forum.xda-developers.com/g5-plus/development/twrp-flashable-stock-builds-t3813351
The partition table and bootloader are not included, which makes it safer to up/downgrade.
Do not attempt to apply standard OTAs over these builds. They'll probably fail, worst case they will brick your phone
So if you want to take the Oreo OTA and have an upgraded bootloader (C0.92), don't flash these. Flash the official Stock ROM (Nougat) images using fastboot then take the OTA.

I got all the information from this guide thanx but one doubt is there , i have my own efs nd persist and i have also backed it up so do i need to restore the restore zip or m i good to just fastboot flash nougat rom and update it via OTA to oreo? I m using custom oreo rom right now and i have never lost 4g or imei that means my efs and persist is my original..

I successfully flashed nougat thnx to your guide.i have downloaded the oreo update but where to put it the update is not being detected in system update
I m an Indian user so retin variant and dwnlf the oreo file provided by you.

karan3660 said:
I successfully flashed nougat thnx to your guide.i have downloaded the oreo update but where to put it the update is not being detected in system update
I m an Indian user so retin variant and dwnlf the oreo file provided by you.
Click to expand...
Click to collapse
The zip file needs to be placed in the internal memory and not within any folder in the internal memory (i.e in the root directory of internal memory), after that you need to give storage permission to the updater app and reboot. After reboot, you need to check for updates and the updater app should now be able to pick up the zip file you placed in internal memory as a new system update

psychopac said:
The zip file needs to be placed in the internal memory and not within any folder in the internal memory (i.e in the root directory of internal memory), after that you need to give storage permission to the updater app and reboot. After reboot, you need to check for updates and the updater app should now be able to pick up the zip file you placed in internal memory as a new system update
Click to expand...
Click to collapse
I have to directly place the zip file?? I extracted it into folder maybe thats why updater app didnt detected
Let me try again.
Tried after placing the zipe file directly into the root of internal storage and gave motorola update service storage permission then rebooted
Still not detevtion the zip file.

karan3660 said:
I have to directly place the zip file?? I extracted it into folder maybe thats why updater app didnt detected
Let me try again.
Tried after placing the zipe file directly into the root of internal storage and gave motorola update service storage permission then rebooted
Still not detevtion the zip file.
Click to expand...
Click to collapse
There's no need to extract the file. Simply place the zip in the root directory. You must be on June 137-92-14 update to install it.

psychopac said:
There's no need to extract the file. Simply place the zip in the root directory. You must be on June 137-92-14 update to install it.
Click to expand...
Click to collapse
I was on 93-10 version thats y it didnt detect update.
Flashed 92-14 nd updated to stock oreo
Thanks for the guide

karan3660 said:
I was on 93-10 version thats y it didnt detect update.
Flashed 92-14 nd updated to stock oreo
Thanks for the guide
Click to expand...
Click to collapse
Just for your info: 93-10 is a firmware for reteu/retus/retapac devices, 92-14 is for retin/rebra.
So you won't receive future OTA as you are on the wrong software channel.
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
Just for your info: 93-10 is a firmware for reteu/retus/retapac devices, 92-14 is for retin/rebra.
So you won't receive future OTA as you are on the wrong software channel.
Click to expand...
Click to collapse
It's actually quite possible that future otas will still be picked up (although I wouldn't recommend that others try this). Flashing another channel was important before, but given that Moto seem to have unified the builds.

NZedPred said:
It's actually quite possible that future otas will still be picked up (although I wouldn't recommend that others try this). Flashing another channel was important before, but given that Moto seem to have unified the builds.
Click to expand...
Click to collapse
That would be a nice move from Moto/Lenovo.
So I should have said:
So you probably won't receive future OTA as you are on the wrong software channel.
Sent from my Moto G5 Plus using XDA Labs

The stock OTA update for retus can be found here: https://technoplanners.blogspot.com/...S28.85-13.html
I downloaded this to root internal storage and changed storage permissions but System update doesn't find it. I also tried putting it in the sdcard root with same result. I tried to adb sideload it but it failed because Nougat has to be at Build number NPNS25.137-92. Since I had previously installed the OTA June security patches I'm at Build number NPNS25.137-93. So I seem to be between a rock and a hard place.
Any suggestions has to how to get upgraded to oreo OTA?

nvrpayretail said:
The stock OTA update for retus can be found here: https://technoplanners.blogspot.com/...S28.85-13.html
I downloaded this to root internal storage and changed storage permissions but System update doesn't find it. I also tried putting it in the sdcard root with same result. I tried to adb sideload it but it failed because Nougat has to be at Build number NPNS25.137-92. Since I had previously installed the OTA June security patches I'm at Build number NPNS25.137-93. So I seem to be between a rock and a hard place.
Any suggestions has to how to get upgraded to oreo OTA?
Click to expand...
Click to collapse
This Oreo OTA requires the Brazil or Indian firmware to flash onto (possibly Latin America firmware). As you've found out, this OTA is NOT compatible with US devices as they're on a different stock build. You'd have to wait for the EU, APAC or US OTA updates to be leaked or released. You'd also have to be on the NPNS25.137-93-14 update to apply the OTA update when it arrives.

The OTA I linked to is for the retus version - Blur_Version.28.51.16.potter.retail.en.US.zip

nvrpayretail said:
The OTA I linked to is for the retus version - Blur_Version28.potter.retail.en.US.zip
Click to expand...
Click to collapse
Yup, I've checked the link and it's linking to the Brazil Oreo OTA update. Despite the suffix 'en.US', this does not necessarily mean this update is for the US devices.
Furthermore, looking at the OTA updater script, it specifically requires NPNS25.137-92-14 or OPS28.85-13:
Code:
Package expects build thumbprint of 8.1.0/OPS28.85-13/b8ea:user/release-keys or 7.0/NPNS25.137-92-14/16:user/release-keys
Since you have mentioned you have NPNS25.137-93-14 this OTA simply will not flash to your device. You must wait for the compatible OTA to be released.

nvrpayretail said:
The OTA I linked to is for the retus version - Blur_Version.28.51.16.potter.retail.en.US.zip
Click to expand...
Click to collapse
Despite its name, it is not the us ota.

[Guide] US988 Oreo to H933 Pie Stock ROM Keeping Root

So I had a bit of a hiccup trying to go from US998 to H933. The plan was to go from US998 Oreo to H933 Oreo and then update to Pie with the TWRP zip. But I never made it that far. Many things happened before getting back to US998 Oreo, which was my original starting point, but they should be irrelevant.
General disclaimers apply. Do this at your own risk. I've only done this one time on my phone with help and advice from @cloud1250000. This hasn't been "tested" further then that and this guide was written after the fact.
Please read the entire guide first then go back and follow step by step.
Prerequisites:
adb installed - Follow 3rep, steps 1, 2 and 3. here to install.
LG drivers installed
LGUP dev patched installed - located here - Courtesy of @tecknight.
See "HOW TO INSTALL DEV PATCHED LGUP" to install
Needed Files:
Stable TWRP 3.2.3.7
Original Pie recovery aka "original-recovery-pie.img" - Courtesy of @cloud1250000
Original Pie laf aka "laf-pie.img" - Courtesy of @cloud1250000
H933 Pie kdz - H93330k_00_OPEN_CA_OP_0906.KDZ
You'll also need:
AnyKernel 3 RCTD Remover - Courtesy of @JohnFawkes
Disable_Dm-Verity_ForceEncrypt_08.18.2019 (encryption disabler) - Courtesy of @Zackptg5
Magisk - latest here or v19.3 direct link
Rename TWRP-3.2.3-7-default.img to TWRP.img
Place the following on the root of your microsd card (though you could put it on your internal sd, you would just have to adjust the paths)
TWRP.img
original-recovery-pie.img
laf-pie.img
You can put these anywhere you like on your sdcard
AK3_RCTD_Remover.zip
Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Magisk-v19.3.zip
0) WARNING - You will be formating the internal data partition. Backup/move files from the internal storage or you will lose them!
1) Start with a H933 phone that has been converted to US998 on an Oreo rom, with bootloader unlocked. I was on this kdz specifically: US99820a_04_0330.kdz
2)Boot into download (vol + and plug in cable) mode/connect phone to the computer. Then open up the dev patched LGUP.
3) Select this kdz H93330k_00_OPEN_CA_OP_0906.KDZ.
4)Flash with partition DL, select all EXCEPT recovery.
5)It should reboot into recovery/TWRP
6.a) WARNING, Following procedure might be risky. Please read up on flashing laf and see if it's ok with you. I don't really know how risky it is, but I figured I would put in this warning.
6.b) Open a command window on your computer and run the following commands with adb. This puts TWRP into the laf partition and the stock recovery back into the recovery partition. Meaning we won't have TWRP in recovery but we will have a backup of it in laf, which we'll need. *inspired by @runningnak3d from the H932 root*
Code:
shell adb
cd external_sd
dd if=TWRP.img of=/dev/block/bootdevice/by-name/laf
dd if=original-recovery-pie.img of=/dev/block/bootdevice/by-name/recovery
7)Power off phone, turn it on. Let it do its thing for a bit, there will be a reboot and it will stay on LG logo for awhile. It should eventually boot to a setup screen. Great Pie is installed, now we need to install a few things in TWRP. Turn off the phone.
8)Boot into download mode (vol + and plug in cable) it will boot into TWRP (this is expected)
9.a) Follow from step 7 from this post. There is some of step 6 that should be followed also.
If you followed all of that you should have installed Magisk, Disable_Dm-Verity_ForceEncrypt_08.18.2019, and AnyKernel 3 RCTD Remover and performed a factory reset and did a format of data.
9.b) The final step of the above should have had you boot into android, once you've done that you can turn off your phone
10) Boot into download mode (vol + and plug in cable) it will boot into TWRP (this is expected)
11) Flash TWRP back to recovery by running the following command
Code:
shell adb
cd external_sd
dd if=TWRP.img of=/dev/block/bootdevice/by-name/recovery
11.b)If you would like to restore laf (so you can use LGUP) then also run this to restore LG's download mode. *It can be desirable to leave in the laf partition also. By leaving it there if for some reason you lose TWRP in recovery then you can boot into download mode and you'll have TWRP there. This is a personal decision.*
Code:
dd if=laf-pie.img of=/dev/block/bootdevice/by-name/laf
You're done, you now should have a H933 phone on H933 Pie with root.
If your mobile data doesn't work or you're not getting LTE, check your apn setting and play around on your phone to see if it will pick it up. Check that mobile data is on etc. Remove sim, turn off phone, insert sim then turn on phone etc. If none of that works then:
Reboot to TWRP/recovery (you can do so in Magisk, modules, 3 dots, reboot recovery) and run:
Code:
adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
Reboot and you should have data/LTE back
Big credit to @cloud1250000 who walked me through all of this, I was just a pawn. I can't thank Cloud1250000 enough!
Info and files taken from these posts:
https://forum.xda-developers.com/showpost.php?p=80363769&postcount=21
https://forum.xda-developers.com/showpost.php?p=80432411&postcount=135
Thanks to @cloud1250000 for the original-recovery-pie.img and laf-pie.img
Thanks to @ChazzMatt for all his help on the forums and I've linked to a lot of his stuff
Thanks to @runningnak3d for the inspiration for step 6b from his work on the H932 root. Please go here and click the THANK BUTTON!
Thanks to @tecknight for the DEV PATCHED LGUP! Please go here and click the THANK BUTTON!
Thanks to @Zackptg5 for the Disable_Dm-Verity_ForceEncrypt_08.18.2019 (encryption disabler)
I don't normally write guides but I had went through this and thought others would benefit from knowing the process. Please let me know if it needs some improvements.

nice guide!!
@ChazzMatt is it possible to move this guide to the guide section?

cloud1250000 said:
nice guide!!
@ChazzMatt is it possible to move this guide to the guide section?
Click to expand...
Click to collapse
Yeah, I'll ask mod to move it. I'll also reference it in the H933 Pie post #1.

Btw, this is mostly how I did it myself. so there's atleast 2 persons who followed this guide successfully..

I successfully updated to H93330k while retaining root/TWRP by mostly following these steps too. However, I skipped flashing TWRP to laf partition as it felt risky to me. I instead flashed Magisk zip to get root before flashing back stock recovery to get into OS. Once booted into Pie, I installed Magisk Manager, enabled ADB, then re-flashed TWRP using ADB with the command "dd if=TWRP.img of=/dev/block/bootdevice/by-name/recovery".

traybourne said:
I successfully updated to H93330k while retaining root/TWRP by mostly following these steps too. However, I skipped flashing TWRP to laf partition as it felt risky to me. I instead flashed Magisk zip to get root before flashing back stock recovery to get into OS. Once booted into Pie, I installed Magisk Manager, enabled ADB, then re-flashed TWRP using ADB with the command "dd if=TWRP.img of=/dev/block/bootdevice/by-name/recovery".
Click to expand...
Click to collapse
So you basically just followed this guide:
https://forum.xda-developers.com/showthread.php?p=78183349
I has started using that guide myself but I couldn't format my data partition in step 3. TWRP said it couldn't mount /data and reported it as 0KB.
While trying to fix that something got messed up and I had to try and get back to a working state. I finally got back to US998 Oreo and then did it this way.
If I understand correctly though, when I did the steps above, it's the same the as steps in this guide at the beginning. (Partition DL without recovery).Except in this guide you format data/factory reset before booting up. In my guide here you do it after.
I guess it's probably a good idea to suggest to people to try that guide/method first as it could be considered safer.
If users follow the guide linked in this post and they can format data in step 4 then they can continue with that guide. If formatting data doesn't work then they can jump to this guide and start at step 6.
Though I would also suggest if you can't format data to try and reboot back into recovery and try it again as even when I did this guide I think it might have had an error formatting data also but rebooting back into recovery allowed me to format data.
But I find LGUP kind of dangerous. It's not actually I'm sure but if used incorrectly it can go poorly. Thought that's true with anything.
I've actually left TWRP in laf as I don't see much negative. If I somehow loose custom recovery, I have a backup and if I need to use LGUP then I can always flash the original laf back while in TWRP from the laf partition. runningnak3d said flashing laf was fine and actually highlyrecommend it so that helps the decision (note that the suggestion was for people with a H932). He explains why its a good idea in the H932 thread.

bnevets27 said:
So you basically just followed this guide:
https://forum.xda-developers.com/showthread.php?p=78183349
I has started using that guide myself but I couldn't format my data partition in step 3. TWRP said it couldn't mount /data and reported it as 0KB.
While trying to fix that something got messed up and I had to try and get back to a working state. I finally got back to US998 Oreo and then did it this way.
If I understand correctly though, when I did the steps above, it's the same the as steps in this guide at the beginning. (Partition DL without recovery).Except in this guide you format data/factory reset before booting up. In my guide here you do it after.
I guess it's probably a good idea to suggest to people to try that guide/method first as it could be considered safer.
If users follow the guide linked in this post and they can format data in step 4 then they can continue with that guide. If formatting data doesn't work then they can jump to this guide and start at step 6.
Though I would also suggest if you can't format data to try and reboot back into recovery and try it again as even when I did this guide I think it might have had an error formatting data also but rebooting back into recovery allowed me to format data.
But I find LGUP kind of dangerous. It's not actually I'm sure but if used incorrectly it can go poorly. Thought that's true with anything.
I've actually left TWRP in laf as I don't see much negative. If I somehow loose custom recovery, I have a backup and if I need to use LGUP then I can always flash the original laf back while in TWRP from the laf partition. runningnak3d said flashing laf was fine and actually highlyrecommend it so that helps the decision (note that the suggestion was for people with a H932). He explains why its a good idea in the H932 thread.
Click to expand...
Click to collapse
Sort of, Step 8 of that guide did not work for me as I could not get into DL mode at that point, so I had to go back and dump the stock recovery, then flash it from within TWRP to get past that part. That guide also doesn't include the step to wipe modemst1 and modemst2 from TWRP, which was required for me to get data back.
I don't recall having issues with formatting data though, but honestly I was trying so many things I don't exactly recall what worked and what didn't. The whole process was a real pain lol.

cloud1250000 said:
Btw, this is mostly how I did it myself. so there's atleast 2 persons who followed this guide successfully..
Click to expand...
Click to collapse
Make that 3.
Tried LOS 17 and needed this to get back to somewhat normal state.
Kinda did it backwards as I wanted to retain on H93330k though.
Thanks!

You can't use lgup to replace the recovery with the original one because download mode won't work until you master reset.. and master reset is done by the original recovery lool.. so the original guide won't work because of that. (If you switch from us998 to another model)
Twrp in laf is good and I'm glad I reviewed the h932 root thread for that reason lol BUT you do lose download mode and lgup.. but you can easily revert it back with twrp with the laf I provided..
Anyway, it's very straightforward to do the switch.
Also do not go down to nougat for master reset.. since it remove twrp from laf (surprisingly they removed that in the pie master reset.. also pie does it master reset by itself.. it's just the best.)

christopherrrg said:
Make that 3.
Tried LOS 17 and needed this to get back to somewhat normal state.
Kinda did it backwards as I wanted to retain on H93330k though.
Thanks!
Click to expand...
Click to collapse
Make sure if you want to try customs roms to go with the h930 version (if available.. )

finally managed to.. convert an ls998+ to h933... sadly I lost my imei in the process lol
the only thing I had left was the meid on the back of the device... I think I figured how to get the imei from that (and it seems to be matching the right device :s) ... and I finally managed to restore it on the device..... following a bunch of different guide...
Sadly, the device lost its S/N number... not sure if it's important.. I think h933 phone doesn't have one.... atleast my original h933 doesnt...
Honestly big rookie mistake.. but now I got a fully working h933+ (volte )

cloud1250000 said:
finally managed to.. convert an ls998+ to h933... sadly I lost my imei in the process lol
the only thing I had left was the meid on the back of the device... I think I figured how to get the imei from that (and it seems to be matching the right device :s) ... and I finally managed to restore it on the device..... following a bunch of different guide...
Sadly, the device lost its S/N number... not sure if it's important.. I think h933 phone doesn't have one.... atleast my original h933 doesnt...
Honestly big rookie mistake.. but now I got a fully working h933+ (volte )
Click to expand...
Click to collapse
Did you brick your initial H933 or have you always been on ls998?

I`ve got 2
One h933 from bell and the other one is the ls998+ I got from ebay for 140usd...
when converting the ls998 to an h933... the lte would never work... tried deleting the modemst partition.. it would just kill data completely... so what I did was to take the working modemst1 and modemst2 from my h933 and flashed it on the ls998... it worked till a reboot... then data gone again... I've read somewhere that the fsg partition is the backup for modemst1.. so what I did is... flash on the ls998 the fsg, modemst1, modemst2 and op partition of my working h933...
very not a good idea.. turns out.. fsg, modemst1 and modemst2 is the EFS (where the imei is stored) :s so I basically lost my ls998 imei.. surprisingly tho.. lte was working fine and I could make calls lol... but the system didnt report the imei of my h933 phone.. it was just not displaying anything.. which is odd.. anyway.. after a couple of hour.. I found a way to restore the imei back

cloud1250000 said:
I`ve got 2
One h933 from bell and the other one is the ls998+ I got from ebay for 140usd...
when converting the ls998 to an h933... the lte would never work... tried deleting the modemst partition.. it would just kill data completely... so what I did was to take the working modemst1 and modemst2 from my h933 and flashed it on the ls998... it worked till a reboot... then data gone again... I've read somewhere that the fsg partition is the backup for modemst1.. so what I did is... flash on the ls998 the fsg, modemst1, modemst2 and op partition of my working h933...
very not a good idea.. turns out.. fsg, modemst1 and modemst2 is the EFS (where the imei is stored) :s so I basically lost my ls998 imei.. surprisingly tho.. lte was working fine and I could make calls lol... but the system didnt report the imei of my h933 phone.. it was just not displaying anything.. which is odd.. anyway.. after a couple of hour.. I found a way to restore the imei back
Click to expand...
Click to collapse
That's awesome! Great ending!

I have converted H933 to US998 Pie with bootloader unlocked and TWRP. Now my goal is to go back to H933 Pie, and keep the bootloader unlocked and TWRP. I have followed the post #1 in this site and post #2 in https://forum.xda-developers.com/lg...a-20g-twrp-t3868186/post78183349#post78183349, but phone doesn't boot to TWRP after Step #2 (Partition DL Canadian KDZ 30k). I tried several times and still couldn't succeed. I must miss some steps.
Can anybody please help provide what methods or link I should follow? Thanks in advance.

If it doesn't boot into TWRP, then what does it boot into?
Are you sure you're NOT flashing recovery?
BTW you might also find help in this telegram group
https://t.me/LGH933CAN

I've unlocked and rooted my H933 via the US 998 Nougat/Oreo firmware etc. however running into a snag in converting it back to the H933, as it seems despite de-selecting the recovery partition of the H933 pie firmware LGUP will still write over it along with TWRP.
I tried this again with the recovery backup partition also selected, then again by flashing TWRP to laf and laf to recovery yet the same patched LGUP I've been using throughout this entire process just writes over recovery/laf.
I've made sure to select PARTITION DL each time, is there a command line method to ensure these partitions are skipped? Running out of ideas honestly, I suppose I'll try refurbished US 998 Oreo to make sure the file system/partitions are untouched and try again...
traybourne said:
I successfully updated to H93330k while retaining root/TWRP by mostly following these steps too. However, I skipped flashing TWRP to laf partition as it felt risky to me. I instead flashed Magisk zip to get root before flashing back stock recovery to get into OS. Once booted into Pie, I installed Magisk Manager, enabled ADB, then re-flashed TWRP using ADB with the command "dd if=TWRP.img of=/dev/block/bootdevice/by-name/recovery".
Click to expand...
Click to collapse
Wondering how this is possible as wouldn't flashing the firmware overwrite the root required to access /dev/block/bootdevice/by-name/recovery? I was thinking maybe by skipping the boot partition so you retain the rooted boot.img from Magisk yet, flashed the H933 pie rom three times so far and de-selecting or not, it confirms immediately laf and recovery will be changed just the same.

fljanders said:
I've unlocked and rooted my H933 via the US 998 Nougat/Oreo firmware etc. however running into a snag in converting it back to the H933, as it seems despite de-selecting the recovery partition of the H933 pie firmware LGUP will still write over it along with TWRP.
I tried this again with the recovery backup partition also selected, then again by flashing TWRP to laf and laf to recovery yet the same patched LGUP I've been using throughout this entire process just writes over recovery/laf.
I've made sure to select PARTITION DL each time, is there a command line method to ensure these partitions are skipped? Running out of ideas honestly, I suppose I'll try refurbished US 998 Oreo to make sure the file system/partitions are untouched and try again...
Wondering how this is possible as wouldn't flashing the firmware overwrite the root required to access /dev/block/bootdevice/by-name/recovery? I was thinking maybe by skipping the boot partition so you retain the rooted boot.img from Magisk yet, flashed the H933 pie rom three times so far and de-selecting or not, it confirms immediately laf and recovery will be changed just the same.
Click to expand...
Click to collapse
See the H933 PIE KDZ thread. Has link to Instructions posted.
If that's what you've been following, sorry don't know...

ChazzMatt said:
See the H933 PIE KDZ thread. Has link to Instructions posted.
If that's what you've been following, sorry don't know...
Click to expand...
Click to collapse
It was, pretty sure there's nothing wrong with the guide, the concept makes sense it's just forcing LGUP to skip the recovery partition that's proving to be a challenge. I've got lgup_cmd installed though cannot find any info on how to specify Partition DL installation/skip recovery partition.
Following the guide I select Partition DL and the H933 pie kdz firmware, after selecting start I select all partitions and de-select Recovery however as below it seems to ignore that and flash the default recovery partition regardless:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

David X said:
I have converted H933 to US998 Pie with bootloader unlocked and TWRP. Now my goal is to go back to H933 Pie, and keep the bootloader unlocked and TWRP. I have followed the post #1 in this site and post #2 in https://forum.xda-developers.com/lg...a-20g-twrp-t3868186/post78183349#post78183349, but phone doesn't boot to TWRP after Step #2 (Partition DL Canadian KDZ 30k). I tried several times and still couldn't succeed. I must miss some steps.
Can anybody please help provide what methods or link I should follow? Thanks in advance.
Click to expand...
Click to collapse
Hey, not sure if anyone is still having issues with their devices not booting to TWRP after flashing 933 and therefore losing root + recovery, but after a day of trying to accomplish this on a non-Frankenstein US998 I realized how to force boot to recovery and preserve access.
Immediately when the phone reboots after flashing the .kdz...
Hold the power and volume down until you see the V30 logo, then release and reapply the power button.
Basically trying to master reset. Confirm repeatedly and it will boot to TWRP instead of wiping.
From there you can preserve TWRP, flash magisk, dm verity, etc. Golden :good:

unbrick Nokia 3.2

Hello together,
after many tries to get my nokia 3.2 rooted, i end up now with a black screen.
Only the Qulacomm mode is working.
Get anyone managed to flash the stock firmware with QFIL provided from the rooting thread?
I always end up with "sahara fails".
Every help is welcome!
Thanks!!!!

After many tries I have finally put my phone back to life.
My instructions how to do it will come soon!

page1875 said:
After many tries I have finally put my phone back to life.
My instructions how to do it will come soon!
Click to expand...
Click to collapse
please do, i encountered a similar problem.

HowTo Flash STOCK 00WW
1. Trigger nokia 3.2 to edl-mode (https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841)
2. Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
- This was the main problem. I never managed it to flash the image with the Windows Programmer QFIL. After more research in Internet, i found finally a Linux application called QDL that work directly without any problems. This application can be found here https://www.96boards.org/documentation/consumer/guides/qdl.md.html .
- Flashing the software ends up into a bootloop. Also i got a message on startup that the bootloader could not be trusted anymore. After a software-update, this message disappears.
3. Flash all the user images again manually with fastboot.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vendor vendor.img
flastboot flash vbmeta vbmeta.img
Whyever you have to flash this partitions only to the active partitions without the suffix _a or _b.
Then the bootloop is finished.
The phone boots normally to Android ONE.
The next problem which occurs on my phone is now that it is not able to connect to GSM network. I guess this happens because i deleted all the necessary partitions for the modem (modemst1, modemst2, fsg).
I get it managed to restore the imei, but still no service available.
In original my phone had the software 00EEA. Perhaps they use different drivers. My luck is that i got a cheap damaged phone from ebay with that firmware.
My next step is to modify the code from QDL that it can read the partitions from the damaged phone and save the software to computer.
Then i will flash this software to my phone and look if this software will run on my phone!

page1875 said:
1. Trigger nokia 3.2 to edl-mode (https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841)
2. Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
- This was the main problem. I never managed it to flash the image with the Windows Programmer QFIL. After more research in Internet, i found finally a Linux application called QDL that work directly without any problems. This application can be found here https://www.96boards.org/documentation/consumer/guides/qdl.md.html .
- Flashing the software ends up into a bootloop. Also i got a message on startup that the bootloader could not be trusted anymore. After a software-update, this message disappears.
3. Flash all the user images again manually with fastboot.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vendor vendor.img
flastboot flash vbmeta vbmeta.img
Whyever you have to flash this partitions only to the active partitions without the suffix _a or _b.
Then the bootloop is finished.
The phone boots normally to Android ONE.
The next problem which occurs on my phone is now that it is not able to connect to GSM network. I guess this happens because i deleted all the necessary partitions for the modem (modemst1, modemst2, fsg).
I get it managed to restore the imei, but still no service available.
In original my phone had the software 00EEA. Perhaps they use different drivers. My luck is that i got a cheap damaged phone from ebay with that firmware.
My next step is to modify the code from QDL that it can read the partitions from the damaged phone and save the software to computer.
Then i will flash this software to my phone and look if this software will run on my phone!
Click to expand...
Click to collapse
Thank you for your reply, it seems that your problem is more complicated than mine.
I have a global variant with 00WW software and i attempt to root the phone. I successfully flash the patched boot.img and had root access. However wi-fi didn't work after that.
Since before flashing the patched boot.img my phone was running on a different firmware from the one that boot.img was extracted from, so i think that was the problem.
I attempted to use QFIL to flash my phone back to 00WW_15 and it failed half way, bricked my phone.

Normally you can use the EDL Mode every time.
My phone only showed black screen and it was always possible to connect in EDL Mode and flash again.
Did you try to flash again? What happens then?

Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
Click to expand...
Click to collapse
What did you mean by Flash the given image ? Was it flash the firmware package with QFIL ?
My main problem is flashing, it always failed half-way and the error log reported that needed files were missing from the package.

Okay. I used the linux program QDL for flashing.
But i saw, that in the xml file rawprogram0.xml a few files are missing.
The linux programm jump over these files but perhaps QFIL do not.
For example is there a picture.img listed which is not available..
Try to remove them manually from the rawfile and test again.

page1875 said:
Okay. I used the linux program QDL for flashing.
But i saw, that in the xml file rawprogram0.xml a few files are missing.
The linux programm jump over these files but perhaps QFIL do not.
For example is there a picture.img listed which is not available..
Try to remove them manually from the rawfile and test again.
Click to expand...
Click to collapse
@update:
Also the files "demoapp.img", "dp_AP_signed.mbn" and "dp_MSA_signed.mbn" are missing.
Remove them from the XML file and try again!

@update
Okay QFIL still failed half-way but i manually flash the user images and my phone boots normally now

Hello,
my nokia 3.2 europe variant wont boot up its stuck in fastboot mode. What can i do to bring it back?
I get this: FAILED (remote: partition table doesn't exist)
P.S. if i do a fastboot reboot it boots back into bootloader

I also had this problems for many many times and don't know what went wrong when this happens.
The only thing that helped was flashing the complete firmware again in EDL-mode.
You can try first to flash only the 5 user-images with fastboot, which i mentioned before in this thread.
I uploaded this files for you, because you don't will find the europe files in internet yet.
Here is the link:
https://transfernow.net/81iti7q21s0s
Good luck!

Hi,
Thank you very much. Is this the complete Firmware? (All Images from Device) Another question: I couldnt Access the recovery System. Did you have the same Problem when your Nokia didnt boot up and was stuck in Bootloader? So is this normal that the recovery is unaccessible?

Yes, that also happens sometimes with my phone.
No, that are not all firmware files, which you need to do a full EDL-Flash.
But with this files you can first try a fastboot flash!
If it does not work, you can take all the other files from the Global-Stock-Firmware, given in the thread https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206.
Delete the 5 files with the same names, flash the Global-Stock-Firmware in EDL-Mode, with QFIL or QDL, (without the 5 files) and in the following flash the 5 europe-image files with fastboot.

Thanks, ive sent it in and got Friday a 00WW Variant of the device back. I will upload those User images for 00EEA to my Google drive so that anyone who needs those files can download them

hello
i wanted to install custom rom and i bricked my phone. i lost recovery mode and i have only fastboot mode .but can not write any img file for example twrp.img beacuse show this error : FAILED (remote: partition table doesn't exist). can please anyone help me.
thank you very much

thanks so much i was able to put my phone back to life. i had almost given up.

smure said:
thanks so much i was able to put my phone back to life. i had almost given up.
Click to expand...
Click to collapse
Hello to ervery one
how you flashed your phone. can you please guide?
i am also stucked in fastboot mode after rooting.

damn... I've been finding on how to restore the wifi and sound because I uninstalled magisk and it failed. I don't think I can thank you enough for this post.