IMEI gone after downgrading to Marshmallow. - Moto G4 Plus Questions & Answers

IMEI gone after downgrading to Marshmallow. - Moto G4 Plus Questions & Answers

Hello guys, I downgraded my xt1643 from nougat to marshmallow. Then my imei gone.Mobile data, wifi was not working, even I could not able to set up my phone. Then I flashed nougat soak test and everything was fine again.But the setup page required WiFi or mobile data to complete the setup. I want to go back into stock marshmallow. Please Help Me!!!

the main reason for imei loss is flashing a wrong stock rom, Are you absolutely sure you are flashing the stock rom MEANT FOR YOUR DEVICE ONLY?

1)Just to clarify, when you re-flashed the stock Nougat ROM, you got your IMEI back?
2)Which Marshmallow stock ROM are you trying to flash? There's quite a few different variants of the stock Marshmallow ROM and flashing the incorrect one for XT1643 appears to cause you to lose your IMEI. If I recall, MPJ24.139-63 was the last Marshmallow build for XT1643.
3)Why are you trying to downgrade to Marshmallow? If you downgrade from stock Nougat (especially the more recent June 2017 to December 2017 Nougat builds), remember that you cannot use OTA updates if you've downgraded. Using OTA updates whilst downgraded is a good way to hard brick your device.

I'm using the same marshmallow build you mentioned above to downgrade then also I'm getting imei 0 problem

alwinbernat said:
I'm using the same marshmallow build you mentioned above to downgrade then also I'm getting imei 0 problem
Click to expand...
Click to collapse
Try the following guide https://forum.xda-developers.com/moto-g4-plus/how-to/guide-moto-g4-plus-imei0-issue-t3859068
As an aside, since you've downgraded, do not use OTA updates, else you'll hard brick your device.

Port : ADB Interface
Baud Rate : Not Applicable
Device : Android
Operation : Read Info
Searching for Device... Found
Model : Moto G (4)
Version : 7.0
Hardware : qcom
Baseband : M8952_70030.25.03.62R DFLT_FSG
CPU : armeabi-v7a
SIM Card : ABSENT,READY
Type
MEID(1) : Null/Empty
Root Status : Not Rooted
Operation Finished.
Elapsed Time: 00:03
Module Ver. [1.3]
Log Saved to Logs\190626_120502.log
plz help me solve this....my country is india.....this baseband is indian baseband?and i m trying to root by elemental x and magiks.but not rooted.
C:\Users\bhavik\Desktop\Minimal ADB and Fastboot>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
athene_f:/ $ su
Permission denied
1|athene_f:/ $

Bhavik kaila said:
Port : ADB Interface
Baud Rate : Not Applicable
Device : Android
Operation : Read Info
Searching for Device... Found
Model : Moto G (4)
Version : 7.0
Hardware : qcom
Baseband : M8952_70030.25.03.62R DFLT_FSG
CPU : armeabi-v7a
SIM Card : ABSENT,READY
Type
MEID(1) : Null/Empty
Root Status : Not Rooted
Operation Finished.
Elapsed Time: 00:03
Module Ver. [1.3]
Log Saved to Logs\190626_120502.log
plz help me solve this....my country is india.....this baseband is indian baseband?and i m trying to root by elemental x and magiks.but not rooted.
C:\Users\bhavik\Desktop\Minimal ADB and Fastboot>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
athene_f:/ $ su
Permission denied
1|athene_f:/ $
Click to expand...
Click to collapse
you should have made an EFS backup in case anything goes wrong. And you should not downgrade.
Now.
Have you granted root permission to shell via magisk manager?
Because root permission for shell is denied. You must give shell root access, and then follow steps in thread mentioned above https://forum.xda-developers.com/moto-g4-plus/how-to/guide-moto-g4-plus-imei0-issue-t3859068
Also, as said earlier, never apply OTA Update in future as it will brick your device.
You can further upgrade your stock firmware via fastboot.

Related

How to get the stock rom

Hi guys,
I am a total noob with flashing etc.
Can somebody please be so nice to post here the right tutorial for my case? I want the Original Firmware.
I have read so many threads but they all sound different for me. :silly:
I have got an Motorola X Pure Edition from Ebay. It has Android 6.0 installed. I want to update to 7.0 but when it downloads the new firmware it will reboot and TWRP starts. I have downloaded the firmware 7.0 manually and tried to run it with TWRP but I get always error messages.
According to Bootloader:
Product: clark XT1575 32G P3C
Devise is unlocked
Status Code: 3
Software Status Modified
Do you need information about Baseband Version, Kernel and so on?
Appreciate your help :victory:

Nougat firmware for XT1575 is on androidfilehost.com linked to this thread. The linked thread includes instructions on how to use fastboot to flash the update. Updated baseband, kernel and all that are included in the full firmware package.
You'll need a PC setup for flashing too. Assuming you're using a windows PC you'll need to moto drivers you can get from here, and a minimal fastboot installation you can get from here.

Since you mentioned that TWRP is on your phone it tells me you're not stock. You MUST have all stock firmware on your phone to up grade to 7.0. Go to the "General" section of this forum and look-up "return to stock and lock bootloader". and read it very carefully.

Muffycheeks said:
Since you mentioned that TWRP is on your phone it tells me you're not stock. You MUST have all stock firmware on your phone to up grade to 7.0. Go to the "General" section of this forum and look-up "return to stock and lock bootloader". and read it very carefully.
Click to expand...
Click to collapse
No, you don't need to worry about returning to stock 6.0 to get an XT1575 to 7.0 anymore. Motorola-Firmware-Team released a leaked full firmware package for clark_retus-user 7.0 NPH25.200-22 linked to that acejavelin thread that I linked to. It isn't an incremental update, it is the whole package. Thanks to that, you don't have to return to fully stock 6.0, take or sideload an OTA, and hope for the best anymore.

Motorola Device Manager - Windows 10
Thanks guys for your comments.
Unfortunately I have already problems with the Motorola Device Manager (MDM). Seems like the drivers wont install.
Fastboot message = waiting for any device
I have run the MDM as an admin, activated USB Debugging and MTP but after installation of the MDM i get the congratulations message but i cant open the program.
I have installed the Media Feature Pack for Windows 10 and tried it again without success.
When i open the Motorola_Mobile_Drivers_64bit file from the Temp folder i can Repair or Remove Motorola Mobile Drivers Installation 6.4.0 but I can`t run it.
Other cable and USB Port does not help either.
Device Manager: Android Device --> Motorola ADB Interface
Any ideas how to fix this issue?

Adb works with turned on phone,
"adb devices"
"adb reboot bootloader"
Fastbot only with bootloader/fastboot mode
"fastboot devices" @Jonasson

dzidexx said:
Adb works with turned on phone,
"adb devices"
"adb reboot bootloader"
Fastbot only with bootloader/fastboot mode
"fastboot devices" @Jonasson
Click to expand...
Click to collapse
Can you please explain it for me? I have 0 experience with this stuff :silly:
When i type in adb reboot bootloader it shows an error: no devices/emulators found

Jonasson said:
Can you please explain it for me? I have 0 experience with this stuff :silly:
When i type in adb reboot bootloader it shows an error: no devices/emulators found
Click to expand...
Click to collapse
https://youtu.be/3Q8b0SuGvmI
https://www.google.pl/search?q=inst...1ZHYAhVN2aQKHSi7AoIQ_AUIESgB&biw=1056&bih=660
https://www.google.pl/search?biw=10...k1j0i8i30k1j0i8i13i30k1j30i10k1.0.Pe-SF0MQFkc
Go to movies in google results.

Thanks to all of you. I finally understood how it works. :angel:
Android 7.0 on it :good::victory:

Hi guys,
I did the update with above tutorial to Android Version 7.0. (Android security patch level: 1.September.2017)
But now they ask me to download new Android security updates . (New system software: 25.201.1 (8,0 MB)
Unfortunately when it is doing the restart it shows the error message:
Error!
And it shows a dead Android Robot.
Any ideas what has gone wrong. Not sure why I get the Software-update failure after doing the upgrade successfully from 6.0 to 7.0.
Moto X Pure Edition

Probably you forgot something, I think:
fastboot flash recovery recovery.img

dzidexx said:
Probably you forgot something, I think:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Thanks dzidexx..it does finally work

hello . i need NPH25.200-22-1 android for moto x pure;
any idea?

morvarid said:
hello . i need NPH25.200-22-1 android for moto x pure;
any idea?
Click to expand...
Click to collapse
No full images were ever released/leaked for anything newer than:
Style: NPH25.200-15
Pure: NPH25.200-22
You either need to get one of those to work for you, or move on to something else or a custom ROM. Sorry, but the version you have was never released as am image (that -1 sub version probably never was a full image internal to Moto either, most likely an OTA only) and no later version has ever leaked out. You can stop asking in multiple threads, the answer is the same.

[UNLOCK][UNOFFICIAL][G4] Unlock ANY* LG G4 device with UsU

About
UsU = Unofficial secureboot-off/steadfasterX Unlock
*works with any G4 model. Even though the h818 can be unlocked as well the touch display does not work anymore (should be possible to resolve but.. read on).
so I decided to remove it from the UsU unlock. Read the details and process here: h818 topic
This will "unlock" your bootloader and so enables you to install TWRP and custom ROMS as you like.
To be honest unlock is not the correct wording but I will still refer to it as unlock as the result is the same:
UsU will disable "Secure Boot" which verifies signatures on several partitions like: boot and recovery. Disabling secureboot means it will still verify and give you a secure boot error on boot BUT it will ignore and just boot afterwards (similar to a regular unlock).
This is the outcome of a loooooooong finding process. long? I started with the first attempt in this over 1 year ago. yes.. (think about my nickname heh?!)
A lot of stuff happend since then which all together helped me to accomplish UsU at the very end (yes all these links are my work including some brave testers ofc! ).
You wanna know how this big puzzle fits together?
UsU is not just an unlock! Its a combination of massive changes in TWRP, the G4 kernel and providing all the tools around like FWUL or SALT!
It was really my biggest project in android development and its not just providing the actual unlock files
Hijacking the boot process via EFIdroid, TWRP in FIsH and FIsH in general
AntiRollback and firehose(!) findings
Partition tables for any G4
mAid (fka FWUL) because I needed a valid base for all my testers (one of the reasons why I started FWUL)
The LG-Up replacement and now unlocking tool SALT ! Without SALT this all would be absolutely crazy risky and absolutely nothing for the average user!
many many unlock methods/theories (and millions of times soft and hard bricked) in my PoC thread
while unbricking I found a way to unbrick even when QFIl fails with my sdcard unbrick method
hard-hard bricked (no other recovery then by LG / chip replacement) for 4 times.. (thanks ILAPO!)
many TWRP tests and changes to detect UsU devices properly
HINT:
OPEN THIS THREAD IN A BROWSER!
NOT IN AN APP!
THATS THE ONLY WAY TO FULLY SEE EVERYTHING AS IT SHOULD BE
REQUIREMENTS
UsU does not care about a country version of a model (e.g. H815 TWN and H815 TUR are all referring to as H815).
So you will find only the main part of your model listed which means it will work for any of them!
1) Your device should be one of these (SALT will detect your device and only allows to flash for these variants):
LS991
F500
H810
H811 (wth? yes that works but.. you can unlock OFFICIALLY! its just a fastboot command!)
H812 (NOTE: firmware: v20x or higher is strictly required before flashing!)
H815 - any non EUR
H815 EUR (wth? yes that works but.. you can unlock OFFICIALLY! its just a login on the LG website)
disabled: H818 (KNOWN ISSUE: TOUCH STOPS WORKING! current state)
H819
US991
VS986
Note: SALT will tell you which ROM type is compatible with your device within the main screen: GPT compatibility
Yes there is a way to flash also H815 ROMs on those who do not support it out-of-the-box but this is very risky and requires either a change of the partition table or the ROM build developer need to change the fstab (riskless for you)
2) ARB less or equal 2
So ARB 3,4,5,........ WILL NOT WORK!!
Details:
Just use SALT to identify your current ARB and read here how to identify and verify: G4 AntiRollback
* Reason:
UsU is based on an ARB 2 based aboot (part of the bootloader stack - see FAQ #27) and so ARB > 2 will hard-hard brick your device if you would flash UsU on it. Hard-Hard brick means no way to recover other then sending for repair.
3) Your device firmware must be MM(keep Requirement #2 in your mind when upgrading to MM)
which one? I highly recommend the latest MM version for your model --> but again beware of the ARB (not greater then 2)!
H812 devices need special attention though: v20x or higher is strictly required before flashing!
Details:
Yes you can flash and use UsU even when on LP but believe me: you don't want to. You will encounter issues sooner or later when runnin LP so take your time and upgrade your device to MM before proceeding here.
LIMITATIONS / KNOWN ISSUES
(bootloader stack is explained and described in FAQ 27)
1) Do not use QFIL or flash any KDZ / TOTs or any ROM containing a bootloader stack (like v29a pure does) ! You WILL loose unlock and may hard-hard-brick your device (at least HARD BRICK)!
2) Do not use QFIL or flash any KDZ / TOTs or any ROM containing a bootloader stack (like v29a pure does) ! You WILL loose unlock and may hard-hard-brick your device (at least HARD BRICK)!
3) Do not flash any MM or N bootloader stack containing the file named: aboot. This will immediately lock your device and so definitively HARD BRICK!
4) If you want to flash a MM or N modem partition (aka firmware) you need to re-flash <model>_UsU_basebands_flash-in-twrp.zip otherwise you will bootloop, stuck on boot or see a blue screen with a modem crash (this may change if I ever get my kernel module working...)
5) If a ROM has no active developer or the developer has not made it UsU compatible you may need to open the ROM zip file on your PC and change the update-script within (just remove the assert line(s) at the top is enough)
6) The fastboot mode coming with UsU will enable fastboot flash but the command fastboot boot will not work (like on the semi-official N bootloader stack)
7) Most important: Once you go this way - there is (maybe) no way back! SERIOUSLY. The only way to make the device exactly like before is replacing the mainboard. If you're scared: good.
Read the new findings on that part here - some models may be able to revert UsU!
Think twice and don't complain later if you go on!
8) Do not use QFIL or flash any KDZ / TOTs or any ROM containing a bootloader stack (like v29a pure does) ! You WILL loose unlock and may hard-hard-brick your device (at least HARD BRICK)!
9) video framerates are lowered after flashing UsU. This is due to the fact that required files for high performance video will not load properly anymore and so must be replaced. Replacing those firmware files is a risk and as it is working ok enough for the most users that patch will not be included in any ROM. If you really think you need this patched ensure you read the instructions here thoroughly and understand them 100% before proceeding to apply it: G4-VideoLag-Fix
YES I REPEATED MYSELF 3 (THREE) TIMES (... for a reason)!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now (maybe) void (well not really but just for the case...)
*
* I'am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about this howto/unlock method
* before using it! ---> YOU <--- are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Downloads
YES. ALL of them:
Latest unlock package by steadfasterX (download the one for your device model only) --> <model>_UsU_unlock.zip (mirror)
Latest baseband package (download the one for your device model only) --> <model>_UsU_baseband_flash-in-twrp.zip (mirror)
Latest TWRP (PREVIEW-103 or higher!) by steadfasterX
- Nougat TWRP (if you plan to use + flash Nougat ROMs)
- Oreo TWRP (if you plan to use + flash Oreo ROMs)
- Pie TWRP (if you plan to use + flash Pie ROMs)
A custom ROM of your choice (see Requirements topic to find a compatible one!) --> e.g. all newer builds here: http://leech.binbash.rocks:8008/
Linux: I highly recommend to use mAid . This is an android lovers live ISO which can be booted from an USB stick which has everything needed on board - including SALT!
Latest mAid *persistent* by steadfasterX (HAVE TO be version 2.6 or later!): maid.binbash.rocks
only if NOT using mAid:
Latest SALT version (minimum version: v3.19!) by steadfasterX: SALT
Important note about bootloader/modem stuff!
You will find on several ROM threads the hint that you must have a specific bootloader stack (FAQ #27) in order to make the ROM working properly.
What in reality is needed on these ROMs is just the MODEM (aka firmware) partition nothing else. Believe me I know this for sure
1) Flash required modem partition in TWRP or fastboot mode
2) if using a ROM which is NOT specific an UsU ROM: Flash your baseband package (<model>_UsU_baseband_flash-in-twrp.zip) in TWRP again!! If you don't you will get bootloops, android hanging on boot or modem SoC crashes (blue demigod screen)
Flash UsU with SALT
(requires SALT v3.21 / mAid v3.2 or higher)
Before proceeding ensure that you have read and understood the "Limitations" topic and the "Changes in behavior" topic in this thread!
If you have a Windows PC the easiest way to get SALT is by flashing mAid v3.2 or higher on an USB stick (if you had read the "Downloads" topic above you should know that already).
Before you ask if there is a Windows version of SALT: read the FAQ in the SALT thread.
UsU can be flashed in 3 different ways! Every way will unlock your device the only difference is where you place the UsU files. Choose the one which fits best for you:
by an external sdcard (must be VFAT formatted)
by using your internal storage
by direct flashing (only when available - SALT will show this option only when possible for your device)
OK enough about all this: LETS UNLEASH YOUR DEVICE!
At very first: ensure you are using the LATEST version of SALT!
SALT contains an internal updater and when a new version has been detected online it will display an upgrade hint. DO THAT if you see any. It doesn't hurt to also trigger the update process even if you see no popup just to be sure that you have the latest version. You can also check the SALT release notes and compare the version with yours (title of the SALT window displays your version).
That step is really easy but incredible important. Do not miss that!
Just to say it again as its crucial important: USE THE SALT UPDATER to ensure you have the latest version!
Extract <model>_UsU_unlock.zip and copy the aboot_UsU.img, laf_UsU.img and rawres_UsU.img to either:
a) your external SDcard (directly on the external sdcard - not in any folder!). The sdcard must be formatted as VFAT.
or
b) connect your running Android device with your PC, select MTP mode in Android and copy it to the:
- "Internal Storage" and folder "Download" (exactly there!)
Start SALT
If you have not done already: DO A BACKUP NOW I'm serious this is your last chance to grab the important files and it just takes some minutes (in basic mode) but you have all in place if needed!
If you skip this step no one may can help you later!
Notice and WRITE DOWN the "GPT compatibility" info! DO NOT PROCEED IF IT STATES "unknown"
This part will become crucial important when it comes to which ROM you can flash!
The only valid information about that can be found in SALT!
If you see a "H811" there you have to flash H811 ROMs later (if no specific ROM is available for your model)
If you see a "H815" there you have to flash H815 ROMs later (if no specific ROM is available for your model)
If you see a "unknown" there you have to STOP and provide the SALT debug log (advanced menu)
Open the Advanced Menu
Click the "Unlock G4 (UsU)" button and read carefully the popup. Click Unlock, choose your unlock way and follow the instructions
If the UsU flashing fails for any reason (SALT will do important pre-checks and validiations before actually flashing):
If you see a popup about UsU flashing has partially failed do not be scared - just read and follow the instructions!
If you see a different error: do not reboot or power off the device! Ask for support and provide the debug log in SALT (in Advanced Menu -> Debug Logfile button -> Upload button and share the link)!
If the UsU flashing was successful (SALT will validate the flashing) continue:
Boot your device into fastboot mode (yes UsU has enabled an unlockedfastboot access for you!):
take out the battery
unplug the usb cable from the PC (not from the device)
Insert the battery again
wait 2 sec
press volume DOWN and while keeping it pressed: plug the USB cable to the device
keep volume DOWN pressed until you see the fastboot screen
Flash TWRP (yes you can do that now... because of UsU!):
fastboot flash recovery <twrp.img> (replace <twrp.img> with the real filename)
YOU MUST boot to TWRP now (you will notice a secure boot error but TWRP will load!):
disconnect USB cable
take out battery
put battery back in
press volume down AND the power button and keep both pressed until.. you see TWRP!
Gotcha! Try that with a locked phone and you will fail!
If you do not boot to TWRP after flashing it it will get OVERWRITTEN and you have to do all the steps for flashing TWRP again!
Optional (not needed when you flash an UsU compatible ROM later) Flash the baseband package now: <model>_UsU_baseband_flash-in-twrp.zip
While still in TWRP choose REBOOT menu and reboot to RECOVERY (yes again!)
Notice: TWRP will show your REAL device model when connected to the PC now.
If not: SHARE THE recovery LOG (how-to for grabbing the recovery log is written in FAQ #4A)!
I would say: its a good time to create a TWRP backup isn't it (ensure you also select "Bootloader" in TWRP backup)?
I HIGHLY RECOMMEND to do nothing else now. Just boot into your ROM as it is! Check if everything is working and proceed only if it boots fine and works fine!
Optional: just root now. Use Magisk or SuperSU to root your current installed stock ROM to see that it works
Done. Do not miss to read the Changes in behavior topic!
Whats next? Lol you are FREE! Flash SuperSu, Magisk or a custom ROM. Up to you. Flashing issues? Read the LIMITATIONS/KNOWN ISSUES topic (especially #1, #2, #3).
Changes in behavior
Booting to recovery, custom ROM booting (or stock but rooted), booting into download mode
You will notice a secure boot error ... and it will boot!!
... and NO: THIS MESSAGE CAN NOT BE REMOVED! If you can't live with that do not unlock
Fastboot
After you unlocked your device with this method you will also have an unlocked fastboot mode which can be accessed by a key combo:
take out the battery
unplug the usb cable from the PC (not from the device)
Insert the battery again
wait 2 sec
press volume DOWN and while keeping it pressed: plug the USB cable to the device
keep volume DOWN pressed until you see the fastboot screen
Now what? You can flash whatever you want here with: fastboot flash <partition> <filename>
you can NOT: fastboot boot .. as this is blocked like in the semi-official N bootloader stack.
TWRP/Recovery hardware key combo
Flashing UsU changes the way the regular factory reset screen key combo is working.
After flashing UsU we can boot directly into TWRP!
power off device
unplug the usb cable from the device (if any)
press volume DOWN + power button and KEEP THEM BOTH pressed the WHOLE TIME until you see "Recovery loading" or TWRP
Factory reset hardware key combo
As written above the regular key combo to get into the LG factory reset screen changes a bit:
power off device
disconnect any usb cable from the device
press volume UP + power button and KEEP THEM BOTH pressed until you see the LG logo the first time! THEN you have to immediately release the power button (ONLY that) and press and keep holding the power button directly again! Keep them pressed until you see the white LG factory reset screen
Proofs
Keep in mind: UsU will work for ANY LG G4 model and does not care about country specific ones, too! When I say: ANY, I MEAN any!
The only device which is a real special one because of different hardware (2 SIM slots) is the H818 which can be unlocked but has issues (see above)
confirmed:
check the current poll results: https://forum.xda-developers.com/poll.php?do=showresults&pollid=26680
LS991 (confirmed) --> https://forum.xda-developers.com/poll.php?do=showresults&pollid=26680
F500 (confirmed) --> https://forum.xda-developers.com/poll.php?do=showresults&pollid=26680
H810 (confirmed) --> https://forum.xda-developers.com/showpost.php?p=75126190&postcount=298 and https://forum.xda-developers.com/showpost.php?p=75736723&postcount=456
H812 (confirmed) --> https://forum.xda-developers.com/showpost.php?p=75126190&postcount=298
H815 (confirmed) --> My own one! and https://forum.xda-developers.com/showpost.php?p=75086602&postcount=276 and https://forum.xda-developers.com/showpost.php?p=75737617&postcount=458
H818 (confirmed)* --> https://forum.xda-developers.com/showpost.php?p=75133410&postcount=307 * SEE ABOVE REGARDING THE CURRENT ISSUES
H819 (confirmed) --> https://forum.xda-developers.com/poll.php?do=showresults&pollid=26680
US991 (confirmed) --> https://forum.xda-developers.com/poll.php?do=showresults&pollid=26680
VS986 (confirmed) --> https://forum.xda-developers.com/showpost.php?p=75109841&postcount=293
Support / Telegram
Of course in this thread but also by Telegram. I have created a generic group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
Model specific ROM threads
H810:
- AOSCP Nougat
- LineageOS Oreo - general LOS all-in-one thread
- LineageOS Pie - all-in-one thread
- /e/ OS Pie - all-in-one-thread
H812:
- AOSCP Nougat
- LineageOS Oreo (deprecated) new: general LOS all-in-one thread
- AtomicOS
- LineageOS Pie - all-in-one thread
- /e/ OS Pie - all-in-one-thread
H815:
- AOSCP Nougat
- LineageOS Oreo (deprecated) new: general LOS all-in-one thread
- LineageOS Pie - all-in-one thread
- /e/ OS Pie - all-in-one-thread
VS986:
- AOSCP Nougat
- LineageOS Oreo (deprecated) new: general LOS all-in-one thread
- LineageOS Pie - all-in-one thread
- /e/ OS Pie - all-in-one-thread
any other model:
- LineageOS Oreo - all-in-one thread
- LineageOS Pie - all-in-one thread
- /e/ OS Pie - all-in-one-thread
Making the baseband flashing obsolete
Well time goes by and so things change in the meantime. I have found a way to make the baseband flashing obsolete but that requires to flash either a device model specific ROM or kernel.
That means:
When you flash a full UsU compatible ROM (like those linked above) there is no need anymore to flash the baseband package.
When you flash another ROM which is not fully UsU compatible you can flash a kernel with UsU patches and so can avoid flashing the baseband package as well.
The UsU kernels can be found here.
When the ROM is neither fully UsU compatible nor there is no kernel with UsU patches you can or better must flash the baseband package.
Credits
Mohd Saqib for the ls991 userdebug bootloader (https://forum.gsmdevelopers.com/lg-g-series-unified/32523-lg-g4-h811-boot-repair-qfil.html) stack. Without him.. no "unlock"
LG for making a faulty mainboard which allowed me to replace it without an issue several times after hard-hard bricking
Me - steadfasterX bc I have done all this almost alone (besides the brave testers ofc) AND: just for FUN ! (I *CAN* UNLOCK OFFICIALLY!) and as the the whole guide and method is the result of many many days ... lol noooo *MONTHS* (!!!) of spending my free time on this topic!
neutrondev (details about technical understanding + support)
uio88 (donator), jasonlindholm (recurring unteachable donator!), pablo103 (donator), britx (donator), ReeS86 (donator), ling751am (donator), 01189998819991197253 (donator), Korpse (donator), decibel_nv (donator), bdasmith (donator), hteles (donator), Leg0V0geL (donator), britx (donator), doop (donator), street_android (donator), ErismaSS (donator), ingcolchado (donator), fauxmight (donator), NwOg1984 (donator), pablogrs (donator), romanofski(donator), nenich78 (donator)
The overall sum (just for UsU) of donations (as of 2023-04-03): $252 !
While donations are accepted and appreciated there is NO need for it. I have done all this for fun and I like thx clicks more then money LOL
XDA:DevDB Information
Unofficial secureboot-off/steadfasterX Unlock, Tool/Utility for the LG G4
Contributors
steadfasterX, the_naxhoo (tester), SePhIrOtX (tester), Chebhou (tester), fawadshah33 (tester), DoughMucker (tester), shane87 (tester), Guy Noir (tester), networkkid (tester), ling751am (tester), jmfecon (tester), r3pwn (tester)
Version Information
Status: Stable
Stable Release Date: 2018-03-08
Alpha Release Date (PoC): 2017-07-28
Created 2018-03-08

FAQ
0) Is/will UsU be available for ARB 3 or higher?
no. never.
Reason:
UsU is based on an ARB 2 based aboot (part of the bootloader stack) and so any ARB > 2 will hard-hard brick your device if you would flash UsU on it.
(Hard-Hard brick means no way to recover other then sending for repair)
1) Is UsU reversible?
Yes and no.
Details: https://forum.xda-developers.com/showpost.php?p=76444983&postcount=968
2a) So I can't flash any KDZ/TOT anymore?
2b) So I can't upgrade my STOCK ROM with the LG updater anymore?
Have you really read the limitations topic? I guess no.
You can't! At least for the KDZ flashing part: not yet.
SALT will allow flashing of KDZ files with the upcoming version 4.0 but until then do not flash with lgup and do not use the LG Android internal updater --> You WILL 100% brick your device.
Why? Read the above FAQ.
3) Will UsU void my guarantee?
Sure.
4) I have flashed UsU and now in Android settings and/or in fastboot it shows up as a LG LS991 - WHY?
The aboot mentioned in FAQ 1) is from a specific device: the ls991. Usually this is nothing which you need to care about. What you see in the Android settings is just parsed from the commandline (means from what aboot is telling) and has no further impacts of nothing. Its just a wrong named "variable" thats it. I still work on a fix to adjust this on boot to your real model but atm of writing it would require a kernel for each model just for this cosmetic thing..
As the UsU fastboot IS ls991 as written in FAQ #1 you will see it there and this is unchangeable - but nothing you need to care about.
5a) I flashed UsU and now the ROM bootloops
5b) I flashed UsU and now the ROM does not start
5c) I flashed UsU and now Android crashes with a blue/purple demigod screen
5d) I flashed UsU and now I have no SOUND and/or CAMERA anymore
5e) I flashed UsU and now I have no cell service anymore
Well there could be 3 reasons why this can happen:
- Either you have not flashed the baseband package in TWRP
- you try to boot a ROM which is not compatible with your model (check the GPT compatibility in SALT!)
- or you have a very sensitive (or strict..) device model
The first thing you should try is flashing the UsU kernel for your installed ROM.
If there is no UsU kernel for your ROM install a supported ROM and flash the UsU kernel afterwards.
If the problem persists or if you still want to use the unsupported ROM: flash the baseband package and the GPT compatibility is ok with the ROM you trying to flash.
If the problem persists:
1 )Try to flash the modem partition of your SALT backup before flashing UsU (nothing else!)
if the problem persists:
2) Some devices require to flash the full modem partition of Lollipop (instead of flashing the baseband package) in order to work after UsU has been flashed so if you are sure that you flashed the baseband package go here and download the modem or the KDZ file of a 10 (Lollipop) modem.img/modem.bin: codefire if you cant find what you need try that one: storagecow
Flash the modem file in fastboot mode like this:
Code:
fastboot flash modem modem.img
or in TWRP like this:
Code:
adb push modem.bin /tmp
adb shell
dd if=/tmp/modem.bin of=/dev/block/bootdevice/by-name/modem
sync
reboot
6) Is there a windows version to flash UsU?
No and there will be never one. Why? For this FWUL exists. Flash FWUL on an USB stick and boot from it. It's as easy as it sounds.
7) I want to use a custom ROM based on Android Nougat or Oreo. In the ROM OP they say I need the v29a/N bootloader stack. Is this true?
No. You will find in several ROM threads the hint that you must have a specific bootloader stack in order to make the ROM working properly.
What in reality is needed on these ROMs is just the MODEM (aka firmware) partition nothing else. Believe me I know this for sure
If you later want to install custom ROMs based on N or O (any model! and any ARB) --> N modem
1) Flash G4_29a_N_modem_UsU.zip in TWRP
2) Flash your baseband package (<model>_UsU_baseband_flash-in-twrp.zip) in TWRP again!! If you don't you will get bootloops, android hanging on boot or modem SoC crashes (blue demigod screen)
When you have a H815(!!!!) device with ARB = 0 you COULD flash the complete bootloader stack though (if you wish - but as said it is NOT needed. READ MY LIPS: IT IS NOT NEEDED but its possible though ):
UsU bootloader stack for N / O
8a) I flashed a KDZ with LGUp / LG Flashtools (you really hexedited a kdz/tot just to brick your device? cooool)
8b) I flashed the non-UsU (see FAQ 7 for the UsU one) v29a bootloader stack on my device
8c) I have no idea why but i bricked my phone (actually you have but you don't wanna tell)
You will need an external sdcard or something like the infinity dongle. In theory there is also the way to unbrick by QFIL but this way is incredible dangerous if you use the wrong files (read FAQ #23!!). The external sdcard method will work only when your device is detected in 9008/QDL mode. If you connect your device to the PC and see nothing (Windows: device manager, Linux/FWUL: open a terminal and type: lsusb) then this guide will not work for you. The only chance is to use e.g. infinity or QFIL but there is no QFIL guide out there I would trust..
For the external sdcard unbrick read and follow the sdcard unbrick guide.
It is important that you know which bootloader stack you had on your device (in terms of ARB)
The only difference for UsU devices is that you need to flash:
the aboot_UsU.img to the aboot partition, the laf_UsU.img to the laf partition and the rawres_UsU.img to the raw_resources partition:
Code:
fastboot flash aboot aboot_UsU.img
fastboot flash laf laf_UsU.img
fastboot flash raw_resources rawres_UsU.img
9a) Will UsU work for my model?
Yes (h818 has been disabled though)
9b) Will UsU work for my country/region?
UsU has no restriction on a specific G4 model or country version.
9c) Will UsU work for any ARB?
UsU will work on ARB 0, 1 and 2 ONLY and you will need LP or MM to be able to actually flash UsU.
Again flashing UsU is a risk always. It happens on your own responsibility!
10a) Will UsU allow me to flash TWRP?
Yes.
10b) Will UsU allow me to flash stock ROMs?
Yes. You will be able to flash stock LP, MM, N
10c) Will UsU allow me to flash custom ROMs?
Yes. You will be able to flash any custom ROM of your choice (any android version)
10d) Will UsU allow me to root my device?
Yes. Ofc you can root with magisk as usual.
11) I follow your PoC thread since the beginning.. So UsU has no limitations regarding cell service/signal anymore?
Everything should work (cell service, mobile data, wifi, BT, call, sms, etc). UsU will not replace the complete bootloader stack as it was done in the early implementations.
By keeping your real bootloader stack the hardware like camera, modem / baseband can be initialized as it should and so no limitations are known (yet).
Again flashing an unofficial unlock is always a risk. Do not blame me when something is not working as it should.
You do this on your own responsibility
12) I want to flash a custom ROM but there is none for my model available what now?
SALT will show a field named GPT compatibility. Just flash a ROM which is compatible with your device. Thats it.
Read more about the compat check in SALT in the SALT FAQ #15.
13) I want to flash a custom ROM but it says "This ROM is for device xxxx but this device is >.< !! You told that I can flash any ROM so whats wrong here?
I wrote it in the LIMITATIONS/KNOWN ISSUES topic of the OP but here again:
Taken from the OP:
5) If a ROM has no active developer or the developer has not made it UsU compatible you may need to open the ROM zip file on your PC and change the update-script within (just remove the assert line at the top is enough)
Click to expand...
Click to collapse
Here a guide by @sdembiske https://forum.xda-developers.com/showpost.php?p=76405252&postcount=947
14) I have unlocked with UsU and all went fine. I flashed a ROM and it bootloops and now my phone died!! What have you done with my device? It never had this issue before in the last years!?
Unfortunately this is not UsU's fault. It's yours. Or better its LGs. The g4 is known to have faulty mainboard and when you boot a fresh flashed ROM this is very heavy cpu intensive and so can cause the ILAPO which means the hardware fault occurs. Yes it has not happened to you in the past but how often did you flashed a new ROM in the past? Ask LG for a mainboard replacement (yes even when out of guarantee) or check the bootloop fix it list : https://bit.do/ilapofixg4
15) I flashed the LP modem, but now it wont let me get past lockscreen. Do I need to factory reset?
background info: the modem partition contains decrypt parts so the screenlock may fail to decrypt.
Doing a factory reset is one option which will fix this.
If you dont want to loose your data reset just the password of the screen lock:
https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008
16) I just wanna flash Nougat STOCK. Are there any worry free UsU downloads for it available?
Sure: here
After flashing ensure you flash your model baseband package!
After that and while still in TWRP: Choose Reboot -> RECOVERY ! This should ensure TWRP will not be overwritten on Android boot
17) What is the recommended way to backup with TWRP?
ONE/FIRST TIME backup. Do this just ONCE --> Select these partitions to backup:
Code:
- Firmware_Image
- EFS
- BL unlock state
- Bootloader
- Carrier
USUAL/DAILY BACKUP (e.g. to test other ROMs, before an upgrade, etc) --> Select these partitions to backup:
Code:
- Boot
- Recovery
- System
- Data
- Encryption metadata -> when your device is encrypted ONLY
- Firmware_Image
18) I have flashed the bootloader stack of N on my non-H815 device and now I have issues (no cell service, no bluetooth etc)
There could be 2 reasons why: Either you haven't read the OP guide properly and flashed the bootloader stack or you were one of the "early birds" flashed the full ROM which includes the Nougat bootloader stack.
H815-ONLY_ARB-0_29a_bootloader_UsU.zip (formerly named: G4_ARB-0_29a_bootloader_UsU.zip)
H815-ONLY_ARB-0_v29a_FULL-STOCK-ROM_UsU.zip (formerly named: G4_ARB-0_v29a_FULL-STOCK-ROM_UsU.zip)
The guide in the OP told you to do a SALT backup before flashing UsU.
If you have followed the guide properly you should have it and the above is one of the reasons why I said its required to do it.
( If you lost your backup there is still a way you can go: Follow FAQ #20 )
Open a terminal in the directory where you SALT backup before flashing UsU (or your extracted KDZ) is.
Then put your device in fastboot mode and type these commands:
Code:
fastboot flash factory factory.bin
fastboot flash hyp hyp.bin
fastboot flash modem modem.bin
fastboot flash pmic pmic.bin
fastboot flash rpm rpm.bin
fastboot flash sbl1 sbl1.bin
fastboot flash sdi sdi.bin
fastboot flash sec sec.bin
fastboot flash tz tz.bin
Read the output of the flashing on the screen and in your terminal. Do NOT flash anything else! Just the above - but ALL of the above! (if you miss a single file you will HARD BRICK)
If something is failing do NOT continue and try to re-do the above commands. if it still fails write in this thread or better come into IRC (when between Monday and Friday)!
If something failing here it WILL brick your phone.
19) I have flashed UsU but now I always see a secure boot error text at the top of my screen when booting (TWRP, Android, download and fastboot mode). Is it possible to remove that?
Really? I mean REALLY? Its clearly written in the OP - CHANGES IN BEHAVIOR !
20a)I have flashed UsU and now I want to downgrade/upgrade my bootloader stack. How?
20b)You were on LP or older MM firmware when you have flashed UsU and now having issues? -> Upgrade your bootloader to MM! Read here how:
Download a KDZ of your device model.
Keep in mind that there are frankenstein devices out there (means refurbished devices with mixed hardware inside so you think u have model XXX as it was shown in Android but the mainboard is NOT the same!).
How to identify a Frankenstein device? Read FAQ #21.
IMPORTANT: Check the ARB of that KDZ (SALT will show the ARB of a KDZ on extract!) - If you are unsure - DO NOT PROCEED. you can easily hard brick your device if!
Extract that KDZ with SALT - DO NOT USE ANY OTHER TOOL FOR EXTRACTING! The known windows tools like LG Firmware extract does not extract what we need here and not in the way we need it! So do not use that! You have been warned..
Open a terminal in the directory where you SALT backup before flashing UsU (or your extracted KDZ) is.
Then put your device in fastboot mode and type these commands (you have another file extension? read FAQ #24):
Code:
fastboot flash factory factory.bin
fastboot flash hyp hyp.bin
fastboot flash modem modem.bin
fastboot flash pmic pmic.bin
fastboot flash rpm rpm.bin
fastboot flash sbl1 sbl1.bin
fastboot flash sdi sdi.bin
fastboot flash sec sec.bin
fastboot flash tz tz.bin
Alternative with TWRP (if the above fastboot cmds work for you no need to do this!):
Code:
Boot TWRP
adb push factory.bin /tmp/
adb push hyp.bin /tmp/
adb push modem.bin /tmp/
adb push pmic.bin /tmp/
adb push rpm.bin /tmp/
adb push sbl1.bin /tmp/
adb push sdi.bin /tmp/
adb push sec.bin /tmp/
adb push tz.bin /tmp/
adb shell sync
adb shell "dd if=/tmp/factory.bin of=/dev/block/bootdevice/by-name/factory"
adb shell "dd if=/tmp/modem.bin of=/dev/block/bootdevice/by-name/modem"
adb shell "dd if=/tmp/hyp.bin of=/dev/block/bootdevice/by-name/hyp"
adb shell "dd if=/tmp/pmic.bin of=/dev/block/bootdevice/by-name/pmic"
adb shell "dd if=/tmp/rpm.bin of=/dev/block/bootdevice/by-name/rpm"
adb shell "dd if=/tmp/sbl1.bin of=/dev/block/bootdevice/by-name/sbl1"
adb shell "dd if=/tmp/sdi.bin of=/dev/block/bootdevice/by-name/sdi"
adb shell "dd if=/tmp/sec.bin of=/dev/block/bootdevice/by-name/sec"
adb shell "dd if=/tmp/tz.bin of=/dev/block/bootdevice/by-name/tz"
Download this verify tool to ensure the flashing was successful: [ATTACH]4687157[/ATTACH] ([URL="http://leech.binbash.it:8008/misc/verifyflash.zip"]mirror --> verifyflash.zip[/URL])
Usage:
extract verifyflash.zip
adb push verifyflash.sh /tmp/
adb shell chmod 755 /tmp/verifyflash.sh
adb shell /tmp/verifyflash.sh
Read the output of the flashing on the screen and in your terminal. Do NOT flash anything else! Just the above - but ALL of the above! (if you miss a single file you will HARD BRICK)
If something is failing do NOT continue and try to re-do the above commands. if it still fails write in this thread or better come into IRC (when between Monday and Friday)!
If something failing here it WILL brick your phone.
21)What is a frankenstein device and how can I identify if I have one?
A so called Frankenstein device shows up different in Android then it is in hardware.
Often happens on "refurbished" devices and almost everything you can buy on AliExpress is one.
The only way to identify your REAL model is by disassembling the device.
No there is NO other way. Everything else can be tricked by software.
Follow the guide here: https://www.ifixit.com/Guide/LG+G4+Motherboard+Replacement/51202
now you are able to see the REAL model printed on the front of your mainboard.
Is a Frankenstein bad? Hell yes. Can you live with one? Up to you. Technically there are good chances that it work as it should - especially when UsU'ing it.
Main problem here is that some stupid ppl out there take a board (often a h810 or h812 but there is no restriction) and flash a different PBL (primary boot loader) on it to load what they like to load. usually they flash h815 ROMs as that is best for selling as it can be unlocked officially (which NEVER works - as the IMEI and/or serial will never list a Frankenstein as a h815).
So actually it is not 100% clear what they did with your phone EXACTLY - and that leaves room for bricks when flashing stuff - or even worse: you might encounter partly not working stuff. In most of the Frankensteins I saw they work good when you flash the real models ROMs, bootloader stacks and modem partitions but well there is no guarantee for nothing here!
Other then that you can use SALT (part of mAid) to determine your model. This with the ARB shown gives you a 80 -90 % clue of your real device model.
E.g. when you bought a h815 (which is known to NEVER EVER have an ARB higher then 0) and it shows h810 in SALT then you can be 100% sure that it is not a h815 and 90% sure that it is the model shown in SALT instead.
22)I have a H812 and having issues after flashing the N stock ROM / AOSCP Nougat. What can I do?
Walk throughs:
Stock N report: https://forum.xda-developers.com/showpost.php?p=75913373&postcount=12 by user @grantdb (consider to show ur appreciation by clicking thx on that post)
AOSCP N report: https://forum.xda-developers.com/showpost.php?p=75890188&postcount=361 by user @sdembiske (consider to show ur appreciation by clicking thx on that post)
LineageOS O report: https://forum.xda-developers.com/showpost.php?p=76799406&postcount=1100 by user @sdembiske (consider to show ur appreciation by clicking thx on that post)
23)uhm I wanna / I have flashed with QFIL...
I wrote millions of times that using qfil is f*** dangerous and shouldn't be used.
The process of using QFIL with the wrong files can CONVERT your device or blow fuses! Never ever use qfil unless you REALLY understand what files you flash:
This requires to analyze the files (hexedit) you trying to flash with qfil. which is something 99% of the average user CAN'T.
Which means: do not use it unless you don't care about damaging your device ofc..
The only less-dangerous way is of unbricking from the 9008/QDL mode by my sdcard unbrick method but when you already used qfil you may have damaged your device already.
If you UsU'd your device there is even one more reason to NOT use qfil!
As said you shouldn't use qfil anyways but when you UsU'd your device it's even more important.
WHY I say using QFIL is evil?
Especially on devices which have no ARB >2 firmwares (like h812, h815, h818, h819 and F500) using QFIL is the worst idea you can have.
Just to be crystal clear: if you have UsU'd or not --> that doesn't matters!
QFIL is dangerous because:
some files you can find around will increase your ARB !
Increasing your ARB means you can never flash your original bootloader stack anymore (on devices having no ARB >2 firmwares)
If you can not flash your original bootloader stack anymore you can not load parts of the modem partition.
If you can not load these parts of the modem partitition you can not get any cell service - full stop. Yes here it ends. You can't go back and so you are stuck with like it is.
Well you can still go back by:
- replacing the mainboard
- replacing the cpu/whatever chip on the mainboard
There is ONE single exception to the above: If you have (still) a "nonfusing" device. Nonfusing devices may be able to flash any ARB but beware:
I had a nonfusing device which suddenly changed somewhen during my UsU hacking sessions.
I have one user who was able to flash a lower ARB then he had before because his device was stated as a nonfusing device. There is no guarantee but it is a chance for you.
Read more about the ARB background here: https://bit.do/unlockg4
24)I have a partition file with the extension: [ bin | image | img | mbn ]. How can I convert this?
The extension is not important. The way how you extract files - is. That's why I say all the time use SALT.
On Windows the file extension matters a lot which is not the case for Linux/Android.
There is no need to convert anything as they all are just raw image files.
25a)I have UsU'd but now in TWRP it does not show my model. Instead something like Chinese or strange characters.. How can I solve this?
25b)I have UsU'd but something went wrong while flashing..! I can still turn on the phone and I see the secure boot error.. What now?
25c)I have UsU'd but I cannot open the download mode anymore.. What now?
This can happen when you tried to flash UsU with a completely outdated version of SALT or using an unsupported version of FWUL (like using it in KVM, VMware ,..).
Ok how to fix this now?
Boot to fastboot mode.
Extract the UsU unlock zip file of your model.
Flash the following from that zip file:
Code:
fastboot flash raw_resources rawres_UsU.img
fastboot flash laf laf_UsU.img
That's it. TWRP will detect the model now correctly. If not share the TWRP log as described in the TWRP(!) thread FAQ 4a.
26a)How can I identify my bootloader stack from my backup files?
26b)How can I identify my current installed bootloader stack?
26a)
To find out which exact firmware version you had installed before UsU'd can be done easily when you have a backup (which you should have).
So to grab that info from your backup (requires Linux/FWUL):
Open a terminal in the directory where you have your SALT backup before UsU'd.
Then:
Code:
strings misc.bin | grep LG
It should display a long string containing your model name and the exact firmware version
26b)
There is no easy way atm for this. It is MUCH easier to just flash the newest bootloader stack like described in FAQ #20 in this post.
.. but if you really want something to start with:
a) do a SALT backup (basic)
b) extract sbl1 of any(!) KDZ files you can find for your model (you see now what a bad idea that is?)
c) do a md5sum on sbl1.img/bin (both: on your backup and the KDZ one) and compare. Once you have found a match you know the version.
27) a) What is the "bootloader stack" on the G4?
27) b) What is the boot process on a Qualcomm device like the G4?
The bootloader stack is a set of partitions (and optionally a partition table) which MUST be on the exact same firmware and ARB level.
There are exceptions to this but you really wanna risk a brick?
Keep the bootloader stack files together otherwise you will brick your device.
Why is explained in the following topic.
The LG G4's bootloader stack partitions are:
tz (Qualcomm Trust Zone. It performs low-level operations, including working with QFuses (rpmb secured mmc partition))
sbl1 (secondary bootloader)
sdi (trust zone storage partition. The data which is used by Trust Zone)
pmic (power management integrated circuit - related to rpm)
rpm (Resource and Power Manager firmware. Firmware for specialized SoC, responsible for resources and power)
aboot (<--- replaced by UsU ! so NEVER touch this again after UsU'ing) - Android boot, little kernel, lk, fastboot mode
hyp (Hypervisor - Virtual Machine Monitor, related to tz in order to protect the device/kernel - afaik)
Special partitions (NOT part of the bootloader stack - but either related, optional or as for the PBL - informative):
The following do not directly belongs to the above stack but it is related. You will never touch PBL, laf or raw_resources and the rest are optional ones.
PBL - Built-in ROM Qualcomm primary boot loader (read-only)
laf (download mode - can be anything on unlocked / UsU'd devices but for locked devices it MUST match the bootloader stack)
raw_resources - contains boot messages read by aboot. Examples: LG logo, bootloader has been unlocked warnings
recovery (recovery mode - can be anything on unlocked / UsU'd devices but for locked devices it MUST match the bootloader stack)
modem - hardware firmware (sound, baseband, camera, video, ...) accessed and loaded by rpm and Android (kernel, Android) - must STILL match the device's ARB of the bootloader! Otherwise those files cannot be read/loaded (most of them are signed so certificate protected!)
The boot process on a qualcomm device is as follows:
All of these partitions are signed by a certificate chain which starts in the PBL (which is read-only so cannot be altered - easily)
pbl verifies and boots: sbl1 partition
sbl1 verifies and boots: tz, then: aboot
aboot verifies the next boot stage (boot / recovery / laf partition):
-> for locked devices: enforce verification result (so decline boot when failed)
-> for unlocked or UsU'd devices: print just a warning (so continue when failed)
For a graphical view: https://lineageos.org/engineering/Qualcomm-Firmware/ (G4 is: "2013-2016 Era")
28)a) I want STOCK - how can I revert back once I flashed a custom ROM?
28)b) how can I flash another version of any STOCK rom for my model?
for Nougat: FAQ #16
for any other:
extract with SALT system + boot + modem partition of the stock ROM kdz of your choice
(beware of the ARB!!! SALT will tell you on extracting the ARB and in the main window your device's ARB. do not flash anything higher then what the SALT main screen is showing or you might have a paperweight afterwards!!!! yes, even the system image can blow fuses!)
flash them in fastboot:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash modem modem.img
boot TWRP (if you do not get into TWRP at the first try it gets overwritten. if that happens you must re-flash TWRP in fastboot)
flash the baseband package of your model
factory reset in TWRP (obviously all your data will be lost - so backup before)
if you encounter issues FORMAT data in TWRP (obviously all your data will be lost - so backup before)
29) I have a h810 and an ARB of 3 or higher. I heard there is a way to unlock this specific model somehow?! Is that true? If so how??
UsU will only work up to and including ARB 2 but the h810 is special as it turns out that its PBL (primary bootloader) SEEMS to be compatible with the h811.
There are 2 users reported that it worked for them but again this is EXTREMELY risky - especially on Frankensteins (i.e. refurbished models) !!!
I cannot guide you on that but check out my answer here: https://forum.xda-developers.com/showpost.php?p=80056484&postcount=1857
30) Video framerates are low(er) with UsU?
As mentioned in the OP above the video framerates might be lowered after flashing UsU.
This is due to the fact that the required files for high performance video will not load properly anymore and so must be replaced.
Replacing those firmware files is a risk and as it is working ok enough for the most users that patch will not be included in any ROM.
If you really think you need this patched ensure you read the instructions here thoroughly and understand them 100% before proceeding to apply it: G4-VideoLag-Fix
ZZZ) I have a problem / question not listed here. What should I do?
All known issues are either fixed or listed above but ofc it can happen that you find something which is not listed here and you want to report it.
The very first thing you have to do is:
Open TWRP
Choose the Wipe menu
Choose FORMAT DATA (not a factory reset!)
Test if your problem is gone
ATTENTION:
This will completely clean your internal storage - all pictures etc everything will be lost so ensure you have a backup!
HINT: TWRP will not save your internal storage in a backup (read here why) so you have to take care otherwise!

UsU background
UsU explained (in short words)
This is just for those want to understand what UsU is in detail and how it works.
If you are not interested in background information.. well its worth to read anyways
rawres_UsU.img -> raw_resources partition
when to be flashed:
once (part of the unlock ZIP), after flashing another raw_resources partition
what it is:
Contains logo for boot, download mode and recovery loading
laf_UsU.img -> laf partition
when to be flashed:
once (part of the unlock ZIP), after flashing another laf partition
what it is:
The laf partition holds your download mode. This one is optimized for UsU and SALT.
aboot_UsU.img -> aboot partition
when to be flashed:
once (part of the unlock ZIP), after flashing another aboot partition (which should NEVER happen as it would hard brick your phone)
what it is:
The debug/engineering/whatever aboot partition and the heart of UsU. The aboot partition is part of your bootloader stack and besides this it also holds the fastboot mode.
Its a leaked file originally coming from Mohd Saqib (see credits in the OP) who may even don't know what he provided in his unbrick guide.
Most important: If you ever flash a KDZ/TOT with one of the windows tools out there it will overwrite this partition and HARD-BRICK your device.
That's why I write this so explicit in the LIMITATIONS/KNOWN ISSUES topic of the OP!
For more details refer to the above FAQ #27!
<model>_UsU_baseband_flash-in-twrp.zip
when to be flashed:
once, after flashing another modem partition (e.g. H-ROM still containing the modem partition! which is incredible bad practice btw)
what it is:
model dependent baseband / radio / modem files (the stuff needed to make your cell service work).
I extracted for every model these files and provided a flashable ZIP as this ensures the modem will not crash when on MM or N firmwares.
To be specific these files are always the latest LP basebands I was able to find/extract for each model and yes its still a kind of hackish this way.
If I will be able to get the kernel module working this file will be obsolete on newer ROMs but will be necessary on all which do not have that kernel patch.

Thank you man! I've been waiting for this since last July! Will try it as soon as I get home

Thank you.
I`ve been USU`d!
9TP968739A2116456

I think I will take a 1 year vacation now...
.

Congrats
You worked very hard over the last year.

Glorious
Even though I own an h815 I want to thank you for your work. This is truly glorious and truly impressive!

steadfasterX said:
I think I will take a 1 year vacation now...
.
Click to expand...
Click to collapse
Hahah You deserve more than 1 year I'm so excited to try it as soon as possible. Downloading necessarily files right now. Thank you again !

Im not clear how you flash twrp. Do you use lglaf? adb? Please tell me

Congrats steadfaster!!!! Does anyone know if there are any working roms for VS986 yet?

TheLatios381 said:
Im not clear how you flash twrp. Do you use lglaf? adb? Please tell me
Click to expand...
Click to collapse
pls do not try to unlock bc the very first thing is it requires carefully reading.
I do not flash TWRP but you would when you follow the guide.
How? Its all described. Read or do not go further.
.

I finished the unlock processes but now i cannot connect to the mobile network on VS986. Tried to set up the APN settings but not working. I'm on stock 13B Lollipop rom.
Edit: Figured it out. Had to do the modem flash from FAQ: 5c) I flashed UsU and now Android crashes with a blue/purple demigod screen

I followed the instructions. It worked. I'm using lineageOS on my h812!!! Thanks steadfasterX.

I installed RR 7.1.2 (H811 ver) on my h812 but there are a few issues popping up, like sound not working, youtube videos barely able to play, and sensors not working. Is anyone else experiencing these issues?

How would I go about telling if a ROM has a bootloader stack in it? I am slightly confused. Which versions would cause problems? Is it just v29a? Or are there more that cause problems?
I have read the limitations 6 times and I don't understand.

LS991 roms
Are the H815 roms supposed to be in the LS991 Lineage 13 folder?

Lg g4 h812
For the H812, witch model should I take, H811 or H815?

TheLatios381 said:
I installed RR 7.1.2 (H811 ver) on my h812 but there are a few issues popping up, like sound not working and youtube videos barely playing, is anyone else experiencing these issues?
Click to expand...
Click to collapse
When sound is not working its very likely a modem partition issue. Read the FAQ regarding bootloop and flash the modem partition of your device
adam_s_459_ said:
How would I go about telling if a ROM has a bootloader stack in it? I am slightly confused. Which versions would cause problems? Is it just v29a? Or are there more that cause problems?
I have read the limitations 6 times and I don't understand.
Click to expand...
Click to collapse
A custom ROM will never include a bootloader stack unless it is a stock ROM. Like the v29a.
If you open the ROM zip and you find a file named aboot do not flash it.
Custom ROMs like aoscp or LOS will never contain the bootloader stack.
TheDerpyLlamas said:
Are the H815 roms supposed to be in the LS991 Lineage 13 folder?
Click to expand...
Click to collapse
Ah good one I have to remove that folder.
And regarding your question read FAQ 12
TJtheBLueDragon said:
For the H812, witch model should I take, H811 or H815?
Click to expand...
Click to collapse
read FAQ 12
Sent from my LG-H815 using XDA Labs

Since my H810 isn't my daily driver any more and after following this thread for a looong time I decided to take the plung and unlock. Salt said "Some parts of UsU couldn't be flashed!" and continued but when that was done I was unable to boot into fastboot mode. From there things mostly failed. I do have a full salt backup from a few days ago. Right now the phone won't boot into either download or fastboot mode. Happy be be a guinea pig. Logs below:
https://bpaste.net/show/6028668ee3a1

[Guide] Recover IMEI fully detailed

TRY AT YOUR OWN RISK I AM NOT RESPONSIBLE FOR ANY DAMAGES
It may or may not work
So I spent the last 48 hours trying to fix my phone following a lot of tutorials and finally after combining some methods together here is the simplest solution.
1- install twrp 32-bit
2- wipe everything including internal storage
3- with twrp connect to pc
4- transfer the debloated stock firmware download from here
5- flash it
6- reboot to system after full boot still no signal
7- turn off and boot to bootloader
8- run commands (fastboot erase modemst1, modemst2)
9- reboot and voila signal is back + imei is back (cant fix the 4g if any know how let me know)
If you want to install a custom rom 8.1.0 like pixelexperience follow these steps after the previous ones
1- reboot to recovery
2- install no-verity-opt-encrypt-5.1 download from here
3- reboot to recovery
4- wipe > advanced wipe > data only
5- reboot to bootloader
6- flash twrp 64 bit
7- start recovery
8- wipe > slide to factory reset
9- flash custom rom
10- reboot to system > error in sim card detection
11- reboot and voila works like charm but also no 4G only 3G

Can you post the twrp 32-bits? I can't find it
//---//
I do with twrp-3.1.1.0 and the imei keeps 0

Fehra said:
Can you post the twrp 32-bits? I can't find it
//---//
I do with twrp-3.1.1.0 and the imei keeps 0
Click to expand...
Click to collapse
It's on the first page of the dev section
Click here

AhmedtSadek said:
So I spent the last 48 hours trying to fix my phone following a lot of tutorials and finally after combining some methods together here is the simplest solution.
1- install twrp 32-bit
2- wipe everything including internal storage
3- with twrp connect to pc
4- transfer the debloated stock firmware download from here
5- flash it
6- reboot to system after full boot still no signal
7- turn off and boot to bootloader
8- run commands (fastboot erase modemst1, modemst2)
9- reboot and voila signal is back + imei is back (cant fix the 4g if any know how let me know)
If you want to install a custom rom 8.1.0 like pixelexperience follow these steps after the previous ones
1- reboot to recovery
2- install no-verity-opt-encrypt-5.1 download from here
3- reboot to recovery
4- wipe > advanced wipe > data only
5- reboot to bootloader
6- flash twrp 64 bit
7- start recovery
8- wipe > slide to factory reset
9- flash custom rom
10- reboot to system > error in sim card detection
11- reboot and voila works like charm but also no 4G only 3G
Click to expand...
Click to collapse
First thnks for sharing, i spend all day on it trying a lot of ways and nothing, i followed the steps with the stock rom and the signal looks like came back in the first view, but i went to see the IMEI and still 0, i tried to make a call and nothing, rebooted and the signal was lost. I really don't know what to do anymore, everything that i try fails =\

A possible solution from the G5 Plus forum
Hi all - I've done some work on potter (Moto G5 Plus) around the IMEI issue. I was wondering if someone would be able to see if what I have found for the G5 Plus, applies to other Moto phones. Below is my thread:
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
So, if someone is willing to help out, all you need is a stock rom with root access. Ideally I'd get two volunteers - one who has never flashed an oreo rom, and a second who has flashed an oreo rom and has had IMEI 0 at some stage (if it appears resolved, that's OK, you can still help). What is important for both scenarios is that you have never flashed someone else's persist.
All you'd need to do to help out is run the following commands via adb or in a shell, and paste the results:
Code:
su
ls -l /persist
That ensures a root shell (su), then lists details about the top level files in the persist folder, including their permissions and ownership.
The second one is this (still in a root shell, so su again if need be):
Code:
find /persist -type f
If anyone has questions, I'll keep an eye on this thread, and I'm also happy to take private messages.
Cheers

NZedPred said:
Hi all - I've done some work on potter (Moto G5 Plus) around the IMEI issue. I was wondering if someone would be able to see if what I have found for the G5 Plus, applies to other Moto phones. Below is my thread:
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
So, if someone is willing to help out, all you need is a stock rom with root access. Ideally I'd get two volunteers - one who has never flashed an oreo rom, and a second who has flashed an oreo rom and has had IMEI 0 at some stage (if it appears resolved, that's OK, you can still help). What is important for both scenarios is that you have never flashed someone else's persist.
All you'd need to do to help out is run the following commands via adb or in a shell, and paste the results:
Code:
su
ls -l /persist
That ensures a root shell (su), then lists details about the top level files in the persist folder, including their permissions and ownership.
The second one is this (still in a root shell, so su again if need be):
Code:
find /persist -type f
If anyone has questions, I'll keep an eye on this thread, and I'm also happy to take private messages.
Cheers
Click to expand...
Click to collapse
I tried that thread but it gives me error "chown: bad user 'rfs'"

AhmedtSadek said:
I tried that thread but it gives me error "chown: bad user 'rfs'"
Click to expand...
Click to collapse
Hi, as I stated in the potter thread and above, I need someone who has never installed an Oreo rom to run the commands in my post above. Then I will be able to see the correct ownership for cedric. The 'fix' commands in my Potter thread are specific to Potter.
So to take something from what you posted in the Potter thread, I can see a similar issue, as the owner of your rfs folder is a user and group called "oem_2903" which indicates that the same issue is present.

renanfamous said:
First thnks for sharing, i spend all day on it trying a lot of ways and nothing, i followed the steps with the stock rom and the signal looks like came back in the first view, but i went to see the IMEI and still 0, i tried to make a call and nothing, rebooted and the signal was lost. I really don't know what to do anymore, everything that i try fails =\
Click to expand...
Click to collapse
Yes same problem bro.. with me xda help us plzz what we can do

Hey again, I've worked on another workaround that I have tested on my G5 Plus, that should work with the G5 as well. This will also allow me to identify the correct owner of the rfs folder, which is key to making this work.
For someone who is willing, please back up your persist partition first, then try the following:
Boot into stock rom, ensuring that you have root enabled
Run the following commands via adb or a shell
Code:
su
chmod -R +X+r+w /persist/rfs
chmod -R +X+r+w /persist/hlos_rfs
Then reboot. Your IMEI should be recreated now. Now run the following and post the full output so that I can work out who the correct owner of the rfs and hlos_rfs folders are:
Code:
su
ls -lR /persist/rfs

I flashed a 8.1 Oreo room and then used fastboot erase modemst1,2. This recovered 4g and imei ( no voltle)
I got my volte after flashing stock Oreo.. by fedrey.

Sonisudhanshu said:
I flashed a 8.1 Oreo room and then used fastboot erase modemst1,2. This recovered 4g and imei ( no voltle)
I got my volte after flashing stock Oreo.. by fedrey.
Click to expand...
Click to collapse
Did you had ever restored that moto g4 Persist backup for volte.?

akshu2697 said:
Did you had ever restored that moto g4 Persist backup for volte.?
Click to expand...
Click to collapse
First of all this a g5 thread.
secondly i just simply installed stock oreo and that recovered my 4g imei and volte automatically

akshu2697 said:
Did you had ever restored that moto g4 Persist backup for volte.?
Click to expand...
Click to collapse
Sonisudhanshu said:
First of all this a g5 thread.
secondly i just simply installed stock oreo and that recovered my 4g imei and volte automatically
Click to expand...
Click to collapse
I'm from the G5+ forums. In case it's not common knowledge here, never restore a persist from another device. We have had numerous threads recommending to flash the persist of a G4/G4+ to restore Volte and other functionality. That has been the cause of countless permanent semi-bricked and bricked G5+ devices. The persist is unique to each device, and without your own, you can no longer guarantee full functionality, and in the worst case, you will permanently lose your IMEI.

NZedPred said:
Hey again, I've worked on another workaround that I have tested on my G5 Plus, that should work with the G5 as well. This will also allow me to identify the correct owner of the rfs folder, which is key to making this work.
For someone who is willing, please back up your persist partition first, then try the following:
Boot into stock rom, ensuring that you have root enabled
Run the following commands via adb or a shell
Code:
su
chmod -R +X+r+w /persist/rfs
chmod -R +X+r+w /persist/hlos_rfs
Then reboot. Your IMEI should be recreated now. Now run the following and post the full output so that I can work out who the correct owner of the rfs and hlos_rfs folders are:
Code:
su
ls -lR /persist/rfs
Click to expand...
Click to collapse
When I execute it, it says "chmod: bad mode '+ X + r + w'".
Do you know why it happens?
Code:
adb shell
cedric:/ $ su
cedric:/ # hmod -R +X+r+w /persist/rfs
sh: hmod: not found
127|cedric:/ # chmod -R +X+r+w /persist/rfs
chmod: bad mode '+X+r+w'
1|cedric:/ # chmod -R +X+r+w /persist/hlos_rfs
chmod: bad mode '+X+r+w'
1|cedric:/ #
[CODE]

TioNacho said:
Hey again, I've worked on another workaround that I have tested on my G5 Plus, that should work with the G5 as well. This will also allow me to identify the correct owner of the rfs folder, which is key to making this work.
For someone who is willing, please back up your persist partition first, then try the following:
Boot into stock rom, ensuring that you have root enabled
Run the following commands via adb or a shell
Then reboot. Your IMEI should be recreated now. Now run the following and post the full output so that I can work out who the correct owner of the rfs and hlos_rfs folders are:
When I execute it, it says "chmod: bad mode '+ X + r + w'".
Do you know why it happens?
Code:
adb shell
cedric:/ $ su
cedric:/ # hmod -R +X+r+w /persist/rfs
sh: hmod: not found
127|cedric:/ # chmod -R +X+r+w /persist/rfs
chmod: bad mode '+X+r+w'
1|cedric:/ # chmod -R +X+r+w /persist/hlos_rfs
chmod: bad mode '+X+r+w'
1|cedric:/ #
[CODE][/QUOTE]
Just follow the guide here:
[url]https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147[/url]
Those commands above only worked in certain environments (e.g. with a particular version of something, can't remember which).
Click to expand...
Click to collapse

Hi All, Am Moto G5 plus XT1687 user. I installed number of custom ROM's and finally head back to Stock. This is my headache now, I lost my IMEI & VOLTE. I tried so many steps as mentioned in XDA, same I also tried installing with someone's persist .win file. Permanently I lost my IMEI & VOLTE. If you guys need anything from my phone to find a solution, please ping me. Now I can use that phone as 2g device only.

[email protected] said:
Hi All, Am Moto G5 plus XT1687 user. I installed number of custom ROM's and finally head back to Stock. This is my headache now, I lost my IMEI & VOLTE. I tried so many steps as mentioned in XDA, same I also tried installing with someone's persist .win file. Permanently I lost my IMEI & VOLTE. If you guys need anything from my phone to find a solution, please ping me. Now I can use that phone as 2g device only.
Click to expand...
Click to collapse
Since my Moto G5 Plus (XT1687) isnt my primary phone I just flashed it back to stock 7.1 and when I got the Oreo OTA it fixed the IMEI problem.

sabbotage said:
Since my Moto G5 Plus (XT1687) isnt my primary phone I just flashed it back to stock 7.1 and when I got the Oreo OTA it fixed the IMEI problem.
Click to expand...
Click to collapse
Thanks for the reply. Please update with stock room details that you used. I will try the same and revert.

Back to Official Firmware - Huawei P Smart

I downloaded a rom from androidhost.ru thinking it was an official rom. My aim was downgrading. But it's not an official rom, i guess. And either I can't get back to official rom. Please help. The Huawei technical support told me that the device could be out of guarentee.

Try installing Hi Suite and do a recovery from there

Billabomb75 said:
Try installing Hi Suite and do a recovery from there
Click to expand...
Click to collapse
Thank you. I tried Hi Suite. Hi Suite says the firmware is updated.
There is no huawei identity part and there is no update information, the firmware seems updated.
I downloaded 155 version but i can't update. About phone section --> software number seems 8.0.0.0.46(0JVO).
I can downgrade or upgrade using androidhost.ru files but the other files (app or update.zip) don't work.
Eset Nod32 says the phone is rooted, root checker says the phone is not rooted.

Well try forcing your phone to install the official Rom... Try to boot into a download mode and flash through there

I download full ota zip and L11_hw_eu files from different sites. I turn off the device. I push the volume down and volume up and power button (force) the software installation fails.

Search XDA universal search for hurupdater ..
Get firmware finder from playstore ..download correct stock rom
Follow hurupdater instructions to update in recovery

Firmware finder doesn't find firmware for p smart.
Hurupdater needs unlocked bootloader i guess.

candask said:
Firmware finder doesn't find firmware for p smart.
Hurupdater needs unlocked bootloader i guess.
Click to expand...
Click to collapse
I have a huawei p smart and firmware finder & hurupdater is working ..but yes ..you need an unlocked bootloader ..
In that case
Download stock rom with firmware finder and put on sd
download stock recovery from p smart forum and flash with fastboot ..boot into stock recovery and use stock recovery to restore ...

And on a seperate note , I recommend downloading dc unlocker application and downgrading and unlocking bootloader using dc unlocker ..just search in XDA universal search ....it's a working method ..

Here you can see it :good:

KevMetal said:
I have a huawei p smart and firmware finder & hurupdater is working ..but yes ..you need an unlocked bootloader ..
In that case
Download stock rom with firmware finder and put on sd
download stock recovery from p smart forum and flash with fastboot ..boot into stock recovery and use stock recovery to restore ...
Click to expand...
Click to collapse
thank you but here somebody says:
"Unless your bootloader is unlocked you can't flash ANY .img file ..."

candask said:
thank you but here somebody says:
"Unless your bootloader is unlocked you can't flash ANY .img file ..."
Click to expand...
Click to collapse
No , you can flash only *signed files ...big difference ..you can ALWAYS flash files signed by huawei like stock recovery
https://drive.google.com/file/d/1dFFjCG2xeg9E08SZFA7jC9y21iX1sJgD/view
_there is stock recovery in link
_put in fastboot folder
_rename to recovery.img
_inside settings of phone enable usb debugging ..connect to pc ..in pop-up window allow debug connection (tick always allow )
_open cmd window as admin in fastboot folder
_Run the following commands
adb devices
*should show a serial number
adb reboot bootloader
fastboot devices
*should show a serial number
fastboot flash recovery_ramdisk recovery.img
fastboot reboot

KevMetal said:
No , you can flash only *signed files ...big difference ..you can ALWAYS flash files signed by huawei like stock recovery
https://drive.google.com/file/d/1dFFjCG2xeg9E08SZFA7jC9y21iX1sJgD/view
_there is stock recovery in link
_put in fastboot folder
_rename to recovery.img
_inside settings of phone enable usb debugging ..connect to pc ..in pop-up window allow debug connection (tick always allow )
_open cmd window as admin in fastboot folder
_Run the following commands
adb devices
*should show a serial number
adb reboot bootloader
fastboot devices
*should show a serial number
fastboot flash recovery_ramdisk recovery.img
fastboot reboot
Click to expand...
Click to collapse
thank you. but failed command not allowed?

Does your phone have the OEM UNLOCK option enabled in the developer settings / is the FRP setting disabled. Having an unlocked bootloader simplifies things a lot. I had a similar issue and used the PC version of the huawei firmware finder by TEAM MT and had to use the DNS method (either do via router or set the pc as a hotspot to reflash a lower version of firmware

I took the telephone to a shop for firmware repair. He tried for a couple of days and he also couldn’t get back to official software.

candask said:
Firmware finder doesn't find firmware for p smart.
Hurupdater needs unlocked bootloader i guess.
Click to expand...
Click to collapse
Hi, Candask
I see you are having problems getting back to official software for the Huawei P smart
Knowing that it says System 8.0.0.046 means you are running Huawei Firmware but System 8.0.0.046 usually means the firmware was made for a different model
How this works is the version folder ( partition ) includes information on the device model and if that version folder does not include the files for your region or model, it will display as System 8.0.0.046, not a serious issue but it is fixable
If you could get in contact with me on our Facebook page www.facebook.com/livitechdev
and also provide us with the Huawei P smart model number ( at the bottom of the phone on the back it will say Model: FIG-XXX, mine says FIG-LX1 )
And we will see if we can help you out - Thanks Ryan

8.0.0 is just the software version, what i think you need to match is for example mine is C782
example if you search you had found the following FIG-LX1C09B139 is device/model , and (8.0.0.139) is software version, id reckon aslong as you match the device and get the latest software version it would work

friartuckme said:
8.0.0 is just the software version, what i think you need to match is for example mine is C782
example if you search you had found the following FIG-LX1C09B139 is device/model , and (8.0.0.139) is software version, id reckon aslong as you match the device and get the latest software version it would work
Click to expand...
Click to collapse
@candask - this User is on the right track,
He would be able to get the software version of he already knows his phones model number C782, C472, C106, etc
The only place I believe you can find your model number inside Android is on the build number inside of settings>System>About Phone
8.0.0.137 ( C782 ) is the usual format
8.0.0 being Android version
137 being Huawei's version
( C782 ) being model number of device
the build number Candask has says
System 8.0.0.046( 0VJO )
Which does not give Indication of what model phone he has
Have you tried using E-recovery?

Livi-Tech said:
@candask - this User is on the right track,
He would be able to get the software version of he already knows his phones model number C782, C472, C106, etc
The only place I believe you can find your model number inside Android is on the build number inside of settings>System>About Phone
8.0.0.137 ( C782 ) is the usual format
8.0.0 being Android version
137 being Huawei's version
( C782 ) being model number of device
the build number Candask has says
System 8.0.0.046( 0VJO )
Which does not give Indication of what model phone he has
Have you tried using E-recovery?
Click to expand...
Click to collapse
hi livi-tech
I think what he is experiencing is when he has flashed a custom rom on his phone its changed the rom version name i believe, so even in e-recovery and fastboot it is being read as an unsupported device. il attach a picture to try and show
E-Recovery and attempting to use hisuite will work up until it checks his imei and device / software info then it is unable to proceed

friartuckme said:
hi livi-tech
I think what he is experiencing is when he has flashed a custom rom on his phone its changed the rom version name i believe, so even in e-recovery and fastboot it is being read as an unsupported device. il attach a picture to try and show
E-Recovery and attempting to use hisuite will work up until it checks his imei and device / software info then it is unable to proceed
Click to expand...
Click to collapse
Hello @friartuckme
I haven't had any issues with E-recovery and fastboot in the past no matter what my build number was or what custom ROM was flashed, not sure about HiSuite as I don't have a use for it but I had a look to confirm, even with the build number being different E-recovery still works and fastboot
This is my current setup
Build number: LiviTech (EM Pixel)
EMUI version: 8.0.0
E-recovery picks up: 8.0.0.137(C782) and starts downloading package
This was my setup when looking into compatibility issues a few months ago
Build number: System 8.0.0.046( 0VJO )
EMUI version: 8.0.0
E-recovery picks up: 8.0.0.137(C782) and starts downloading package
Deleting the whole version partition results in
Build number: System 8.0.0.046( OVJO )
EMUI version: 8.0.0
E-recovery picks up: 8.0.0.137(C782) and starts downloading package
( Would not recommend deleting version partition or modifying it unless you want phone to reset or apps to get removed, it's a Huawei issue )
I think I know what the issue his, the firmware he flashed sounds like Huawei firmware ( or a version of it ) but it sounds like the version partition included with that firmware doesn't include the files for his model.

SM-N900V Rooting Assistance Needed

Model Number: SM-N900V
Android Version: 5.0
BaseBand Version: N900VVRSEPL1
Kernel Version: 3.4.0 [email protected] #1
Build Number: LRX21VN900VVSEPL1
I think I have tried everything except those PC-based 1 click root apps. The arabic tool. CF-Root. Nothing. I'm starting to think I need an original kitkat firmware so some of these apps/hacks work. My goal is to get Magisk, TWRP and LineageOS installed.
Under Linux, ADB works fine. After I boot into bootloader mode, fastboot devices simply returns to a prompt. How do I get fastboot to see my device? Do I need to use Windows?
Also, there was some discrepancy about having a Exynos-powered device but in the "ODIN MODE" (bootloader) screen, it says, "QUALCOMM SECUREBOOT: ENABLE (CSB)". Does this mean it's safe to assume it's a Snapdragon device?
Any help is appreciated.

It looks like KitKat wasn't an option. Any help would be appreciated.

PBMaxx said:
Model Number: SM-N900V
Android Version: 5.0
BaseBand Version: N900VVRSEPL1
Kernel Version: 3.4.0 [email protected] #1
Build Number: LRX21VN900VVSEPL1
I think I have tried everything except those PC-based 1 click root apps. The arabic tool. CF-Root. Nothing. I'm starting to think I need an original kitkat firmware so some of these apps/hacks work. My goal is to get Magisk, TWRP and LineageOS installed.
Under Linux, ADB works fine. After I boot into bootloader mode, fastboot devices simply returns to a prompt. How do I get fastboot to see my device? Do I need to use Windows?
Also, there was some discrepancy about having a Exynos-powered device but in the "ODIN MODE" (bootloader) screen, it says, "QUALCOMM SECUREBOOT: ENABLE (CSB)". Does this mean it's safe to assume it's a Snapdragon device?
Any help is appreciated.
Click to expand...
Click to collapse
I spent over three days searching for the right combination of procedures and software (a lot of that you've already done) before I got my Note 3 rooted, bootloader unlocked, TWRP installed and finally LineageOS 14.1 installed.
What worked for me was: ArabicRootApp.exe that I found here: "https://download864.mediafire.com/8ca86uho3n2g/pvm1reerboz2c25/ArabicToolApp.zip", (installed to a Windows 10 box w/Samsung cell phone drivers installed - I included the URI to the file because the file seems to be difficult to find anymore), rooted the phone. "unlock_n3" run twice (through adb on Linux) unlocked the bootloader. Odin3 (on Windows again) installed TWRP, with which I installed LineageOS 14.1-20170713-UNOFFIICIAL-hlte).
The key is rooting the phone. After that, you'll have a "su" command you can execute in an adb shell and unlock_n3 will run.
I started with a clean android version 5.0 and ended up with version 7.1.2

wa7qzr said:
I spent over three days searching for the right combination of procedures and software (a lot of that you've already done) before I got my Note 3 rooted, bootloader unlocked, TWRP installed and finally LineageOS 14.1 installed.
What worked for me was: ArabicRootApp.exe that I found here: "https://download864.mediafire.com/8ca86uho3n2g/pvm1reerboz2c25/ArabicToolApp.zip", (installed to a Windows 10 box w/Samsung cell phone drivers installed - I included the URI to the file because the file seems to be difficult to find anymore), rooted the phone. "unlock_n3" run twice (through adb on Linux) unlocked the bootloader. Odin3 (on Windows again) installed TWRP, with which I installed LineageOS 14.1-20170713-UNOFFIICIAL-hlte).
The key is rooting the phone. After that, you'll have a "su" command you can execute in an adb shell and unlock_n3 will run.
I started with a clean android version 5.0 and ended up with version 7.1.2
Click to expand...
Click to collapse
the link isn't working anymore

Database Users

welcome