[KERNEL][UsU][STOCK|TITAN] UsU patched kernel versions - G4 Android Development
About
Who needs this?
When you unlocked by UsU you have to flash a special baseband package afterwards in order to make ROMs working higher then LP (so MM, N, ..).
This is annoying on the one hand and can cause problems on the other.
These UsU kernels are specific for your model and available for several custom and stock ROMs.
Just flash the corresponding UsU kernel after flashing a ROM and ensure that your modem partition is pure the one of yours model version (so no baseband package flashed).
Guide
(read FAQ #1 if you have the baseband package flashed currently!)
Choose the right UsU kernel (according to the ROM you have)
Ensure you have a ROM installed which is compatible with an UsU kernel (means an UsU kernel exists for your ROM and version)
If not: Flash a ROM which has an UsU kernel available NOW.
Download the UsU kernel to your PC
Boot device in fastboot mode (check the UsU OP thread for a how-to)
Flash the downloaded UsU kernel (has to be done again after a ROM flashing!):
Code:
fastboot flash boot <model>_xx_boot_xx.img
(replace "<model>_xx_boot_xx.img" with the real filename)
Reboot and enjoy:
Code:
fastboot reboot
Downloads
steadfasterX leech Server
Choose the folder of your device (all the ones named "-UsU" are obviously those of your interest)
Choose the ROM flavor of the ROM you have installed or want to install
Choose the version of that ROM
Download the latest boot image you can find (the higher the build number the newer)
Sources / Changelogs
aoscp | lineageos | rr : nougat
aoscp | lineageos | rr : oreo
stock : nougat
Credits
kessaras - without him the custom versions of the UsU kernels wouldn't be what they are
me - I provided the UsU patches included in every UsU kernel, a Jenkins build server, a download server and many of my free time.. so yes I think I can get some credits too
XDA:DevDB Information
UsU kernel versions, Kernel for the LG G4
Contributors
steadfasterX, kessaras
Source Code: https://github.com/Suicide-Squirrel
Kernel Special Features: Making UsU baseband package flashing obsolete
Version Information
Status: Nightly
Created 2018-03-15
Last Updated 2020-04-14
Frequently Asked Questions
FAQ
1) I want to use an UsU kernel but I had flashed the baseband package as recommended by the UsU thread. What do I need to do?
Pretty simple. Flash the modem partition again in fastboot.
Which one depends...
I highly recommend to use a MM modem of YOUR model (for MM ROMs) or the v29a N modem (for N and O ROMS).
Unfortunately for some models the v29a N modem does not work fine so you will be the safest when using the MM one of your device model.
Ensure you have a ROM installed which is compatible with an UsU kernel (means an UsU kernel exists for your ROM and version)
If not: Flash a ROM which has an UsU kernel available NOW.
Extract the latest MM KDZ of your device model with SALT (do NOT use the windows tools!)
Boot device in fastboot mode (check the UsU OP thread for a how-to)
Flash the modem:
Code:
fastboot flash modem modem.bin
(or if named img: fastboot flash modem modem.img)
Flash the downloaded UsU kernel:
Code:
fastboot flash boot <model>_xx_boot_xx.img
(replace "<model>_xx_boot_xx.img" with the real filename)
Reboot and enjoy:
Code:
fastboot reboot
2) Where are the sources for the UsU kernels?
AOSCP - Nougat -> here
AOSCP - Oreo -> here
STOCK - Nougat -> here
3) Are all UsU kernels based on the TITAN stuff?
No. Only AOSCP Nougat / Oreo for now are based on the TITAN kernel.
STOCK is pure STOCK plus the UsU patches.
ZZZ) I miss a UsU kernel for my ROM!! Could you provide it please?
Do not hesitate to ask.. KINDLY. There is no guarantee. Maybe I will add it - maybe not. There are too many out there to build for all of them.
Up to then you are stuck with flashing the baseband package or switch to an UsU kernel supported ROM
Reserved
steadfasterX said:
About
When you unlocked by UsU you have to flash a special baseband package afterwards in order to make ROMs working higher then LP (so MM, N, ..).
This is annoying on the one hand and can cause problems on the other.
These UsU kernels are specific for your model and available for several custom and stock ROMs.
Just flash the corresponding UsU kernel after flashing a ROM and ensure that your modem partition is pure the one of yours model version (so no baseband package flashed).
Click to expand...
Click to collapse
Just a couple of quick questions/clarifications:
- Is the H812 kernel for AOSCP in the downloads here, the same as the version you loaded in post # 327 in the bootloader unlock thread?
- If one was to restore the original TWRP backup of the just unlocked stock rom, should one for example, flash the 'stock' kernel after restoring? - also as an ancillary question, should one then install the TWRP preview version for 'stock' after the restore as well that you have uploaded in your TWRP thread?
Thanks,
S.
sdembiske said:
Just a couple of quick questions/clarifications:
- Is the H812 kernel for AOSCP in the downloads here, the same as the version you loaded in post # 327 in the bootloader unlock thread?
- If one was to restore the original TWRP backup of the just unlocked stock rom, should one for example, flash the 'stock' kernel after restoring? - also as an ancillary question, should one then install the TWRP preview version for 'stock' after the restore as well that you have uploaded in your TWRP thread?
Thanks,
S.
Click to expand...
Click to collapse
No they are not the same because I had to rebuild all kernel versions .
The stock kernel is only for the nougat based ROM available so if you had v29a before or when creating the backup then yes. But if you were on lollipop or marshmallow then a nougat kernel makes no sense on these.
there is no TWRP stock version available since a long time already.. just flash the latest N preview.
Sent from my LG-H815 using XDA Labs
Sorry, deleted. Thank you!!!
steadfasterX said:
About
These UsU kernels are specific for your model and available for several custom and stock ROMs.
Just flash the corresponding UsU kernel after flashing a ROM and ensure that your modem partition is pure the one of yours model version (so no baseband package flashed).
/QUOTE]
Downloaded latest H812 kernel for AOSCP, all went smooth but lost SuperSU on reboot - just had to re-flash it in TWRP again and reboot to reinstate. All good!
Click to expand...
Click to collapse
I did some research. Read that device drivers are stored in the kernel. So that means no matter what rom, if the kernel is H812, you cannot get the FM radio, right? Unless you can find a way to install H815 fm radio driver onto h812 kernel.
I have H812 unlocked with UsU and flashed baseband and I stayed on the stock MM rom.
As far as I can figure this is what I should do to get stock Nougat
Don't wipe anything in TWRP
Flash stock nougat rom G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip then reboot into fastboot,
flash modem.bin from my original SALT backup of original MM modem,
flash UsU kernel h812_stock_boot_build-11-nougat.img
reboot to system and enjoy!
Hopefully this is right!
Edit: Everything works perfectly except calls and corrupted sdcard!
Attached the error log for when making a call.
Thanks Chief :good: one should not need this kernel, in my case H815, if one is having no issues?
Edit: I do have a no Sim detection issue with aoscp oreo
grantdb said:
I have H812 unlocked with UsU and flashed baseband and I stayed on the stock MM rom.
As far as I can figure this is what I should do to get stock Nougat
Don't wipe anything in TWRP
Flash stock nougat rom G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip then reboot into fastboot,
flash modem.bin from my original SALT backup of original MM modem,
flash UsU kernel h812_stock_boot_build-11-nougat.img
reboot to system and enjoy!
Hopefully this is right!
Edit: Everything works perfectly except calls and corrupted sdcard!
Attached the error log for when making a call.
Click to expand...
Click to collapse
Checkout faq zzz in the UsU thread..
jason_l367 said:
Thanks Chief :good: one should not need this kernel, in my case H815, if one is having no issues?
Edit: I do have a no Sim detection issue with aoscp oreo
Click to expand...
Click to collapse
Well up to you if you flash it or not. If everything is working I see no other reason then cosmetics.
This is a very well known issue for aoscp oreo! Just use the a search in that thread! They also have issues with battery drain etc and I always said oreo is nothing which I can recommend atm. Its a play ground for me even if it boots and most things are working.
All I did for working everything with bootloader unlocked with SALT and baseband flashed on stock MM H812:
First thing I did was follow the following since I allready flashed the baseband after unlocking:
FAQ
1) I want to use an UsU kernel but I had flashed the baseband package as recommended by the UsU thread. What do I need to do?
Pretty simple. Flash the modem partition again in fastboot.
Which one depends...
I highly recommend to use a MM modem of YOUR model (for MM ROMs) or the v29a N modem (for N and O ROMS).
Unfortunately for some models the v29a N modem does not work fine so you will be the safest when using the MM one of your device model.
Ensure you have a ROM installed which is compatible with an UsU kernel (means an UsU kernel exists for your ROM and version)
If not: Flash a ROM which has an UsU kernel available NOW.
Extract the latest MM KDZ of your device model with SALT (do NOT use the windows tools!)
Boot device in fastboot mode (check the UsU OP thread for a how-to)
Flash the modem:
Code:
fastboot flash modem modem.bin
(or if named img: fastboot flash modem modem.img)
Flash the downloaded UsU kernel:
Code:
fastboot flash boot <model>_xx_boot_xx.img
(replace "<model>_xx_boot_xx.img" with the real filename)
Reboot and enjoy:
Code:
fastboot reboot
Click to expand...
Click to collapse
In the above procedure I first used my backup MM modem and calls had no sound then I repeated the same procedure using the N modem and it bootlooped.
Restored my FULL TWRP backup (Boot, Recovery, System, Data, Cache, Firmware image, EFS, BL unlock state, Bootloader, Carrier) to MM stock with root and custom kernel (LuPus).
Booted into the system once to make sure all working.
Boot into recovery.
Mount system partition.
Flash full stock nougat (G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip).
Reboot into recovery.
Mount system partition.
Flash baseband file (H812_UsU_baseband_flash-in-twrp.zip).
Reboot into system.
Wait for stock rom to fully load (Takes about 15 mins).
SIM and SD card fully working! Network is immediate with no delay only on first boot for some reason then see below.
Reboot into recovery.
Flash Magisk.
Reboot into system.
Notification that Network unavailable, service disabled message where carrier name should be, then the network works (had
to select my provider under APN settings and then my provider under network selection because it auto selected the wrong
but working provider) Network takes a couple of minutes to kick in properly on each reboot.
Bluetooth, Sound, calls, SMS, GPS, NFC, Camera(pics and vids incl playback), LG Apps like Quick remote and Health (even FM
Radio app runs but no sound), Dolby Atmos, Magisk all working!
Phone is now a LGLS991 and baseband unknown in settings.
EVERYTHING IS PERFECT!
steadfasterX said:
Checkout faq zzz in the UsU thread..
Click to expand...
Click to collapse
Do you think I will get any better than what I have by formatting Data?
Thanks!
grantdb said:
[............] EVERYTHING IS PERFECT!
Click to expand...
Click to collapse
Thx for your report!
so basically u did this (including what we discussed on IRC):
unlocked with UsU
flashed the baseband package
created a full TWRP backup
Flash full stock nougat (G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip)
flashed your backuped MM modem
flashed UsU kernel: h812_stock_boot_build-11-nougat.img
-> result: booted but calls had no sound
flashed N modem
flashed UsU kernel: h812_stock_boot_build-11-nougat.img
-> result: bootlooped
restored the full backup of the TWRP backup (means also: modem + baseband pkg)
-> result: booted, all working
Flash full stock nougat (G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip).
Flash baseband file (H812_UsU_baseband_flash-in-twrp.zip)
-> booted (took 15 min). Notification that Network unavailable, service disabled message where carrier name should be, then the network works (had
to select my provider under APN settings and then my provider under network selection because it auto selected the wrong
but working provider) Network takes a couple of minutes to kick in properly on each reboot.
Bluetooth, Sound, calls, SMS, GPS, NFC, Camera(pics and vids incl playback), LG Apps like Quick remote and Health (even FM Radio app runs but no sound)
Flashing Magisk, Dolby Atmos
-> result: all working
Note:
Phone is now a LGLS991 (known and written in FAQ of UsU thread) and baseband unknown in settings.
Is that summary correct?
Cheers
steadfasterX said:
Thx for your report!
so basically u did this (including what we discussed on IRC):
[.........]
Is that summary correct?
Cheers
Click to expand...
Click to collapse
Yes that's it!
Thank you once again for all your work and help!
Cheers!
EDIT: The network only takes 40 seconds to start working on boot.
steadfasterX said:
Thx for your report!
so basically u did this (including what we discussed on IRC):
unlocked with UsU
flashed the baseband package
created a full TWRP backup
Flash full stock nougat (G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip)
flashed your backuped MM modem
flashed UsU kernel: h812_stock_boot_build-11-nougat.img
-> result: booted but calls had no sound
flashed N modem
flashed UsU kernel: h812_stock_boot_build-11-nougat.img
-> result: bootlooped
restored the full backup of the TWRP backup (means also: modem + baseband pkg)
-> result: booted, all working
Flash full stock nougat (G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip).
Flash baseband file (H812_UsU_baseband_flash-in-twrp.zip)
-> booted (took 15 min). Notification that Network unavailable, service disabled message where carrier name should be, then the network works (had
to select my provider under APN settings and then my provider under network selection because it auto selected the wrong
but working provider) Network takes a couple of minutes to kick in properly on each reboot.
Bluetooth, Sound, calls, SMS, GPS, NFC, Camera(pics and vids incl playback), LG Apps like Quick remote and Health (even FM Radio app runs but no sound)
Flashing Magisk, Dolby Atmos
-> result: all working
Note:
Phone is now a LGLS991 (known and written in FAQ of UsU thread) and baseband unknown in settings.
Is that summary correct?
Cheers
Click to expand...
Click to collapse
So what does this tell us H812 users about the source of the problem. Flashing the original ARB O Nougat ROM (+ N bootloader stack?) kills calls. If you go back to the original state after unlock, then flash ARB any Nougat + baseband you are fine. So steadfasterx, can you answer this question: What does flashing the ARB O ROM (+N bootloader stack) do to continue to kill calls even after you flash with another ROM? What do you need to do (other than restoring a backup) to undo this? My original TWRP backup wouldn't boot so restoring a nandroid isn't an option for me.
mwahahaa said:
So what does this tell us H812 users about the source of the problem. Flashing the original ARB O Nougat ROM (+ N bootloader stack?) kills calls. If you go back to the original state after unlock, then flash ARB any Nougat + baseband you are fine. So steadfasterx, can you answer this question: What does flashing the ARB O ROM (+N bootloader stack) do to continue to kill calls even after you flash with another ROM? What do you need to do (other than restoring a backup) to undo this? My original TWRP backup wouldn't boot so restoring a nandroid isn't an option for me.
Click to expand...
Click to collapse
your bootloader stack (all files mentioned in FAQ 18) must be on MM
you would flash G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip (as described in the guide)
you would flash the baseband package
you would boot
everything should work but give it time (15min to fully boot the first time)
you should set the preferred network type to 3G or 2G (this setting here is the most important and - until now- missing part!)
reboot
give it at least 5min if it still does not connect to cellular network you may need to search cellular networks manually - several times if needed
you may need to set a cell network manually
you may need to reboot again
all the above has been written already but some users still report that this does not work for them. Maybe the time factor is important (most users are impatient)
steadfasterX said:
your bootloader stack (all files mentioned in FAQ 18) must be on MM
you would flash G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip (as described in the guide)
you would flash the baseband package
you would boot
everything should work but give it time (15min to fully boot the first time)
you should set the preferred network type to 3G or 2G (this setting here is the most important and - until now- missing part!)
reboot
give it at least 5min if it still does not connect to cellular network you may need to search cellular networks manually - several times if needed
you may need to set a cell network manually
you may need to reboot again
all the above has been written already but some users still report that this does not work for them. Maybe the time factor is important (most users are impatient)
Click to expand...
Click to collapse
I did all of that exactly and absolutely nothing has changed. No matter what I flash (AOSCP ROM, Stock ROM kernel, modem, radio, etc. etc. my calls hang up immediately when I dial and I don't receive any incoming calls. I am kicking myself for botching the SALT backup because the phone is useless to me without voice.
mwahahaa said:
I did all of that exactly and absolutely nothing has changed. No matter what I flash (AOSCP ROM, Stock ROM kernel, modem, radio, etc. etc. my calls hang up immediately when I dial and I don't receive any incoming calls. I am kicking myself for botching the SALT backup because the phone is useless to me without voice.
Click to expand...
Click to collapse
Yea the backup is gold in many situations...
There is still one thing (at least) you can try :
Do a basic backup in SALT now if you have no backup anymore.
If you have made a backup in the meanwhile ensure you see the modemst1 and modemst2 and misc images there. If not: do a backup NOW and do not proceed until you have these!!
It is also a good idea to do a backup in TWRP including EFS and NO unlock state so you have 2 ways of a backup! Do not skip that. It's done in a second..
Erase the following partitions (part of the EFS and contains network unlock state too! Means you will loose the network unlock if any):
fastboot erase modemst1
fastboot erase modemst2
As said you will loose your network unlock if any and in some circumstances even the imei .
That's why it is important to have the above partitions as a backup.
Boot. Search networks etc.
When booted check imei (*#06# in the dialer), too.
If you loose cell service and imei is still there:
You may need to network unlock the device again and as that may not popup on boot you may must type a secret code in the dialer to open it manually (Google it)
When even that has no positive effect ensure you format data as described in faq zzz and re-do the above erase commands in fastboot afterwards. Then boot again.
You can restore the both partitions and so going back to the current state by either restoring by TWRP the EFS or flashing the SALT backup in fastboot :
fastboot flash modemst1 modemst1.image
fastboot flash modemst2 modemst2.image
This will give you any network unlock back and if lost imei too.
Sent from my LG-H815 using XDA Labs
mwahahaa said:
So what does this tell us H812 users about the source of the problem. Flashing the original ARB O Nougat ROM (+ N bootloader stack?) kills calls. If you go back to the original state after unlock, then flash ARB any Nougat + baseband you are fine. So steadfasterx, can you answer this question: What does flashing the ARB O ROM (+N bootloader stack) do to continue to kill calls even after you flash with another ROM? What do you need to do (other than restoring a backup) to undo this? My original TWRP backup wouldn't boot so restoring a nandroid isn't an option for me.
Click to expand...
Click to collapse
I flashed the any ARB stock rom + baseband package and i also have the result of no call audio... I need this!!!
Related
Some clarity on flashing modem/bootstack - esp for D851 (T-mob)
Can anyone help explain very clearly which modem/bootstack is needed for various android versions ESPECIALLY on the D851? I'm familiar with flashing roms but the modem/bootstack is just a layer of complexity I'm not quite sure about. I thought better to ask before I do something stupid. My current setup is D851 (T-mob), TWRP 3.0.2-0, Fulmics ROM 6.7. My baseband version shows : MPSS.DL2.0.1.c1.13-00053-M8974AAAAANPZM-1 1) Which version does this correspond to, what versions are available, and where? I searched here + google and I found here: http://downloads.codefi.re/autoprime/LG/LG_G3/D851/stock_partitions/10R. But depending on the version the modem is image file (20R), or some is bin file (20e), and some is flashable zip (30D). How to safely flash bin or img files? And if I flash 20e modem do i also need to flash 20e boot, bootloader etc? Confused! 2) How to know which version for different andriod i.e. marshmallow, nougat etc. 3) When/how should I flash and can i brick if I use the wrong version? For example I want to flash a 7.1 ROM and i've read posts saying 20e modem works well. Could anyone explain, step by step, how I should flash modem: before or after rom/gapps etc. 4) Last question - TWRP 2.8 or so used to have an option to check for backup of modem but that no longer appears in 3.0+. Does TWRP 3.0+ backup include the modem even though there is no specific box to check for that? Thanks in advance!
emailej said: Can anyone help explain very clearly which modem/bootstack is needed for various android versions ESPECIALLY on the D851? I'm familiar with flashing roms but the modem/bootstack is just a layer of complexity I'm not quite sure about. I thought better to ask before I do something stupid. My current setup is D851 (T-mob), TWRP 3.0.2-0, Fulmics ROM 6.7. My baseband version shows : MPSS.DL2.0.1.c1.13-00053-M8974AAAAANPZM-1 1) Which version does this correspond to, what versions are available, and where? I searched here + google and I found here: http://downloads.codefi.re/autoprime/LG/LG_G3/D851/stock_partitions/10R. But depending on the version the modem is image file (20R), or some is bin file (20e), and some is flashable zip (30D). How to safely flash bin or img files? And if I flash 20e modem do i also need to flash 20e boot, bootloader etc? Confused! 2) How to know which version for different andriod i.e. marshmallow, nougat etc. 3) When/how should I flash and can i brick if I use the wrong version? For example I want to flash a 7.1 ROM and i've read posts saying 20e modem works well. Could anyone explain, step by step, how I should flash modem: before or after rom/gapps etc. 4) Last question - TWRP 2.8 or so used to have an option to check for backup of modem but that no longer appears in 3.0+. Does TWRP 3.0+ backup include the modem even though there is no specific box to check for that? Thanks in advance! Click to expand... Click to collapse Quote: Originally Posted by graig79 10c Baseband: MPSS.DI.2.0.1.c1.13-00009-M8974AAAAANPZM-1 10m Baseband: MPSS.DI.2.0.1.c1.13-00018-M8974AAAAANPZM-1 20e Baseband: MPSS.DL2.0.1.c1.13-00053-M8974AAAAANPZM-1
emailej said: Quote: Originally Posted by graig79 10c Baseband: MPSS.DI.2.0.1.c1.13-00009-M8974AAAAANPZM-1 10m Baseband: MPSS.DI.2.0.1.c1.13-00018-M8974AAAAANPZM-1 Click to expand... Click to collapse Quote: Bootstack=partitions needed to boot a rom. 20B update by LG and TMO has specific newer partitions like aboot, boot.img. system.img, modem.img, etc. needed to run and boot the rom. If your on 10R Kitkat and try to flash just the rom, it won't boot, or won't have data connection, etc. Haven't tried it yet, but its not good. If you want to go back to 10R Kitkat that you have as your backup, then you need to flash the 10R Bootstack for your backup to boot. ************** HOW TO FLASH: ************** Step 1: Full wipe unless already on rom. Do not wipe internal storage. Step 2: Flash appropriate Lollipop Bootstack. Step 3: Flash ROM.
Where can I find a copy of the 21c modem for D851 A number of people keep referring to the 21C modem, but I can't find a copy of it. I'm trying to install Fulmics 8.0 on my LG G3, but for some reason the modem file seems to be missing. Thanks
egerio01 said: A number of people keep referring to the 21C modem, but I can't find a copy of it. I'm trying to install Fulmics 8.0 on my LG G3, but for some reason the modem file seems to be missing. Thanks Click to expand... Click to collapse Why do you need to flash a new modem? LG G3 what model do you have?
Just need help as I am new to zuk z2
Hi.. I am a noob but I am a pro in Mi4 ( cancro) but this time It has locked bootloader and I got unlocked img from zuk developer website is about 512 byte and two users comment in the bootloder unlocking and twrp recovery section they are facing issue and actually unlocked boot img file should have 1kb but I am confused and another q can I flash terble compatable twrp at once and regarding rom installation also which partition to be earsed ( efs) and which not to and baseband update section I got it and rom installation I got but after baseband update I have to restore Efs???
And what is the size of unlocked boot img you guys got
Which zui you do have? Probably nougat one, so ur baseband should be 1.70, if its then there is no need to flash baseband. Don't know about size on unlock img but you should go ahead and see ifs its getting any error then share here.
Ok
One more thing baseband for oreo is needed
I want to flash aex oreo
And what is that efs
lollipopkiller said: Ok Click to expand... Click to collapse First flash official twrp then according to your need and read full post carefully of the rom you are going to install. There are several twrp and vendor to factory and vice versa zips, some latest build of roms need these zips to be flashed first and some don't required treble twrp so first read instructions carefully,
Ya I did but I have misconception with baseband
Can you msg me in whtsapp 9853687062
Bro plz msg me
lollipopkiller said: Ya I did but I have misconception with baseband Click to expand... Click to collapse If your baseband is 1.70 you don't need to flash baseband
stock rom oreo OPS28.85.13 volte and efs
HI guys this thread only for those who don't have their own persists, efs and installed someone else persists and want to install stock oreo ops28.85.13. I had lost my efs and persist so there it is I lost my IMEI and VOLTE (networks on both sims) So, overcome these issue that's what I did 1. - I installed TWRP flashable pixel experience Rom and erase my modset1 and modset2 and reboot after that I got up my IMEI number and took a back up of efs using TWRP and place to a safe place like on pc or google drive. 2. - but VOLTE is not fixed so fixing VOLTE is not gonna work on pixel experience you have to install stock ROM nougat version using FASTBOOT download only that version suitable for you or specific to your device. 3. - After flashing stock nougat Rom check your IMEI information from Setting>about>status>imei info. If it is zero now you have to flash TWRP after flashing TWRP Restore your pixel experience efs into nougat and reboot after that you should see networks on your device or check IMEI information 4. - coming to VOLTE, I found some threads about someone persist and I downloaded that persist and flash it on my stock nougat ROM and reboot after rebooting I got my VOLTE working. The first thing takes a backup of your efs and persist and again place it somewhere safe. 5. - now oreo ops28.85.13 comes so, I was a little bit afraid to install it because again I am gonna lose my IMEI and persist. 5.1 - installation of oreo is a bit tricky what you have to do download oreo from this link https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433 and follow the commands installed oreo 5.2 - now you will lose your IMEI and persist again so you should have the backup of EFS and persist from nougat version and installed TWRP on your oreo device 5.3 - now download TWRP flash oreo soak1 with the aroma installer and flash firmware only firmware nothing else and don't reboot go back and restore your efs and persist and reboot it will get up your network and VOLTE :laugh: :laugh:
i also lost my persist i flash other's persist can i recover my persist and move to custom oreo rom?? currently i am on PE latest patch with VOLTE using other persist. Guide me to recover My persist.
DhruvanBhalara said: I also lost my persist I flash other's persist can I recover my persist and move to custom oreo rom?? currently, I am on PE latest patch with VOLTE using other persist. Guide me to recover My persist. Click to expand... Click to collapse sorry bro if u flash someone persists then there is no way u can get back your own persist the same thing happened to me bro but if want to try to go to this thread and check it out https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147 just follow the instruction bro but do one thing first take a backup of your current Persist and EFS using TWRP and place it somewhere safe because if you can't get your own persist this backup will help you to get VOLTE to work on stock oreo I hope you understand what I am trying to say
I flashed the ota over stock 7.0 and it installed successfully but lost imei and both sims. Please help
i installed ota of oreo over stock nougot but forgot that i used other persist earlier. now my imei is gone no network is gone too. So i installed pixel experiance and also used erase modem command and now in pixel rom too my network is gone. what should i do. Pls guide me through this
i tried this guide, but after flashed pixelexperience my imei doesnt back
Did you use lastest PE 8.1 Rom? I tried recover imei on Oreo Roms but it didn't work maybe I need old Oreo roms?
I F*cked up! Help me please?
Long story short bought a G5 Cedric running latest official firmware oreo 8.1, didn't like it cuz it's too heavy, unlocked the bootloader, flashed twrp then flashed lineage 17 but can't pass safetynet,(clean) flashed resurrection remix after same problem, then i flashed omni rom and suddenly my IMEI was gone and can't install gapps, what to do now? I just want a good custom rom that passes safetynet, don't care if it's pie or Q.
Flash a rom where imei works Backup efs partition using 64bit twrp You can then restore efs partition if you loose imei With regards to safetynet none of the custom roms will pass without you doing some work You need to flash magisk Flash Busybox magisk module Flash props config module and follow all the instructions on how to change device fingerprint eg to a pixel 4 https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228/ Hide magisk manager with a random package name from magisk settings Hide app that detects root with magisk hide from its settings You can also try the universal safetynet patcher magisk module if the above doesn't work but some report it causes bootloops on some devices/roms
Thank you for the quick response, i have a few questions regarding what you said: 1- how will i know which rom to flash where the IMEI works before flashing the actual rom itself? 2- how do i know if my current twrp is 64bit or not? it's the one from the Lineage 17 thread. 3- when im succesfull in executing those steps and i have to back up efs, where can i find it to restore it if i flash another rom again? because last time before flahsing i wiped system,dalvik & Cache & data but not the storage and yet my back-up was gone? TheFixItMan said: Flash a rom where imei works Backup efs partition using 64bit twrp You can then restore efs partition if you loose imei With regards to safetynet none of the custom roms will pass without you doing some work You need to flash magisk Flash Busybox magisk module Flash props config module and follow all the instructions on how to change device fingerprint eg to a pixel 4 https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228/ Hide magisk manager with a random package name from magisk settings Hide app that detects root with magisk hide from its settings You can also try the universal safetynet patcher magisk module if the above doesn't work but some report it causes bootloops on some devices/roms Click to expand... Click to collapse
maserati2011 said: Thank you for the quick response, i have a few questions regarding what you said: 1- how will i know which rom to flash where the IMEI works before flashing the actual rom itself? 2- how do i know if my current twrp is 64bit or not? it's the one from the Lineage 17 thread. 3- when im succesfull in executing those steps and i have to back up efs, where can i find it to restore it if i flash another rom again? because last time before flahsing i wiped system,dalvik & Cache & data but not the storage and yet my back-up was gone? Click to expand... Click to collapse 1 - You will have to try roms yourself to find out 2 - All custom roms from oero onwards are 64bit - you wouldn't be able to flash them without a 64bit twrp so you already have one 3 - data/media/twrp/backups or storage/emulated/0/twrp/backups I recommend changing the storage location to your sdcard so they don't get deleted when you wipe data or transferring to a pc Formatting data is effectively formatting internal storage as the device is encrypted
TheFixItMan said: 1 - You will have to try roms yourself to find out 2 - All custom roms from oero onwards are 64bit - you wouldn't be able to flash them without a 64bit twrp so you already have one 3 - data/media/twrp/backups or storage/emulated/0/twrp/backups I recommend changing the storage location to your sdcard so they don't get deleted when you wipe data or transferring to a pc Formatting data is effectively formatting internal storage as the device is encrypted Click to expand... Click to collapse I'm currently sticking with m_vaisakh's AOSP-10 as it shows both my IMEI numbers, its also the most stable and reliable out of the Android 10 roms for the G5 CEDRIC, i do have a problem though: i tried 2 simcards in the dual sim function and they both worked but no 4G, just 3G/HSPA+ both SIM-1 & SIM-2, how can i fix this issue?
maserati2011 said: I'm currently sticking with m_vaisakh's AOSP-10 as it shows both my IMEI numbers, its also the most stable and reliable out of the Android 10 roms for the G5 CEDRIC, i do have a problem though: i tried 2 simcards in the dual sim function and they both worked but no 4G, just 3G/HSPA+ both SIM-1 & SIM-2, how can i fix this issue? Click to expand... Click to collapse fastboot erase modemst1 fastboot erase modemst2 fastboot reboot If rebuilding the efs doesn't work I do not know Backup efs first incase it fails to rebuild and imei is 0 again - use a twrp 64 bit to back it up and obviously save to sdcard & pc incase you need to re-flash rom as wiping data will erase your backup on internal storage
TheFixItMan said: fastboot erase modemst1 fastboot erase modemst2 fastboot reboot If rebuilding the efs doesn't work I do not know Backup efs first incase it fails to rebuild and imei is 0 again - use a twrp 64 bit to back it up and obviously save to sdcard & pc incase you need to re-flash rom as wiping data will erase your backup on internal storage Click to expand... Click to collapse it didn't work as my IMEI was 0 on both sims, thankfully i backed up EFS before erasing, so I managed to restore the IMEI again. Is there really no other way to get 4G back?
Hello friend, did you get my reply regarding 4G ?
maserati2011 said: Hello friend, did you get my reply regarding 4G ? Click to expand... Click to collapse As stated before - I do not know the answer I don't own this device
maserati2011 said: Hello friend, did you get my reply regarding 4G ? Click to expand... Click to collapse Which ROM are you using and didn't you got your IMEI?
riyan65 said: Which ROM are you using and didn't you got your IMEI? Click to expand... Click to collapse I was using m_vaisakh's AOSP_10 where i retrieved my IMEI (after losing it on different roms) i tried both sims and had only 3G no 4G. Now i have switched to OfficerJimLahey's CarbonROM_7 Android_9 both my IMEI numbers show but i haven't tested 4G with simcards yet.
maserati2011 said: I was using m_vaisakh's AOSP_10 where i retrieved my IMEI (after losing it on different roms) i tried both sims and had only 3G no 4G. Now i have switched to OfficerJimLahey's CarbonROM_7 Android_9 both my IMEI numbers show but i haven't tested 4G with simcards yet. Click to expand... Click to collapse If it doesn't work in rom then move back to stock Oreo and once you got the 4g take backup of efs and persist and move to custom ROM. If the 4g is available then no need to restore backup, if not restore the backup and enjoy 4g.
riyan65 said: If it doesn't work in rom then move back to stock Oreo and once you got the 4g take backup of efs and persist and move to custom ROM. If the 4g is available then no need to restore backup, if not restore the backup and enjoy 4g. Click to expand... Click to collapse How do i do that? using the Lenovo Moto Smart Assistant?
maserati2011 said: How do i do that? using the Lenovo Moto Smart Assistant? Click to expand... Click to collapse Flash stock rom firmware via fastboot Stock rom firmware is available via https://mirrors.lolinet.com/firmware/moto/cedric/official/ If you don't know what one to choose I suggest latest retail If you don't know how to flash stock firmware via fastboot Google is your friend
TheFixItMan said: Flash stock rom firmware via fastboot Stock rom firmware is available via https://mirrors.lolinet.com/firmware/moto/cedric/official/ If you don't know what one to choose I suggest latest retail If you don't know how to flash stock firmware via fastboot Google is your friend Click to expand... Click to collapse i have flashed stock rom using Lenovo Moto Smart Assistant, IMEI is there, 4G works, how can i relock the bootloader from here? cuz i wanna sell the device.
maserati2011 said: i have flashed stock rom using Lenovo Moto Smart Assistant, IMEI is there, 4G works, how can i relock the bootloader from here? cuz i wanna sell the device. Click to expand... Click to collapse I wouldn't re-lock it for several reasons 1- you need the unlock code to unlock it again & Motorola will say its already been unlocked 2 - Even if you re-lock it it will still display its been unlocked previously 3 - if you ever need to flash stock firmware via fastboot again it may fail with permission denied as the firmware may not be fully signed & you can't flash unsigned firmware with a locked bootloader 4 - if you ota update & it it fails & you hardbrick then again same as point 3 If you really want to Google how to & you need fully signed firmware else it will not lock
TheFixItMan said: I wouldn't re-lock it for several reasons 1- you need the unlock code to unlock it again & Motorola will say its already been unlocked 2 - Even if you re-lock it it will still display its been unlocked previously 3 - if you ever need to flash stock firmware via fastboot again it may fail with permission denied as the firmware may not be fully signed & you can't flash unsigned firmware with a locked bootloader 4 - if you ota update & it it fails & you hardbrick then again same as point 3 If you really want to Google how to & you need fully signed firmware else it will not lock Click to expand... Click to collapse I'm going to respond to each point you mentioned: 1- I still have the email from Lenovo containing the unlock code, do i need the same code to relock the bootloader? 2-are you sure it will still say it's been unlocked before? 3-what does fully signed mean? i searched through the link you sent me earlier and i found the same one that i flashed through LMSA, that is XT1676_CEDRIC_RETEU_DS_8.1.0_OPP28.85-19-4-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip is the one I flashed through LMSA not fully signed? 4-there's no updates anymore after the version i mentioned in point 3. side question: does this method you mentioned still applies to relock the bootloader without the aforementioned issues? PS: it still says ID: bad key on the bootloader unlocked warning, even though i retrieved my IMEI number, shouldn't it display my IMEI number instead of bad key?
maserati2011 said: I'm going to respond to each point you mentioned: 1- I still have the email from Lenovo containing the unlock code, do i need the same code to relock the bootloader? 2-are you sure it will still say it's been unlocked before? 3-what does fully signed mean? i searched through the link you sent me earlier and i found the same one that i flashed through LMSA, that is XT1676_CEDRIC_RETEU_DS_8.1.0_OPP28.85-19-4-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip is the one I flashed through LMSA not fully signed? 4-there's no updates anymore after the version i mentioned in point 3. side question: does this method you mentioned still applies to relock the bootloader without the aforementioned issues? PS: it still says ID: bad key on the bootloader unlocked warning, even though i retrieved my IMEI number, shouldn't it display my IMEI number instead of bad key? Click to expand... Click to collapse You don't need code to lock bootloader - just to unlock it Yes the bootloader will display its locked but will also give a status code that states its been previously unlocked Fully signed means each part of the firmware has been signed by Motorola - sometimes the boot.img isn't You will always get bad key or n/a with an unlocked bootloader - this is normal - you can flash a modded logo.bin to replace this Those are the steps to re-lock the boot-loader - obviously oreo firmware has more sparsechunk so add the extra parts
TheFixItMan said: You don't need code to lock bootloader - just to unlock it Yes the bootloader will display its locked but will also give a status code that states its been previously unlocked Fully signed means each part of the firmware has been signed by Motorola - sometimes the boot.img isn't You will always get bad key or n/a with an unlocked bootloader - this is normal - you can flash a modded logo.bin to replace this Those are the steps to re-lock the boot-loader - obviously oreo firmware has more sparsechunk so add the extra parts Click to expand... Click to collapse So basically i should leave it unlocked it's better this way yes? and if i want to flash a modded logo.bin do i need to flash TWRP again?
maserati2011 said: So basically i should leave it unlocked it's better this way yes? and if i want to flash a modded logo.bin do i need to flash TWRP again? Click to expand... Click to collapse No you can do it via fastboot fastboot flash logo logo.bin
Question help to explain please
[GUIDE] Back to stock ROM howto / Downgrade howto There maybe a number of reasons to go back to the stock ROM. We do not discuss them here :) But what to do if you flashed something, wanting to go back to stock, and did not brick your Realme X2 yet? :) Here is super quick howto guide. There are... forum.xda-developers.com this guys says I have found out that in fact stock recovery does not exist as a prebuilt file It is being created by the script /system/bin/install-recovery.sh on a basis of stock boot partition and a patch file /system/recovery-from-boot.p It means in theory you can recreate stock recovery having only Realme ozip file. EDIT1 The command to do it in Linux shell is Code: bspatch boot.img selfmade_stock_recovery.img recovery-from-boot.p Cool! Tested. EDIT2. For the current moment when unlocked bootloader breaks fingerprint sensor: as soon as the bootloader is locked again, fingerprint starts functioning as it should. EDIT3 Becomes clear that each ROM release has its own stock recovery which is generated automatically on the basis of boot.img and recovery-from-boot.p . Not only boot.img is being changed each release, but recovery-from-boot.p is changing as well. If the wrong stock recovery is installed, you might not be able to decrypt data and connect to WiFi from within recovery. Seemingly it may bring you serious problems if locking back bootloader (thus bricking the device). Good thing (as I understood, but not checked yet) is that after flashing stock ROM with a help of a stock recovery next reboot should replace your stock recovery with an up-to-date version of it. So to be on a safe side make sure that you rebooted to system and that your recovery reflashed by the system before you lock bootloader. EDIT4 In order to combine everything in one place: Stock recoveries for RMX1991 (China version): here Stock recoveries for RMX1992 (India version): here Stock recoveries for RMX1993 (Euro version): here EDIT5 In later ROM releases patch and script files are relocated into vendor partition, they are /bin/oppo-install-recovery.sh and /recovery-from-boot.p there. EDIT6 Please note that the method above is working with officially downloaded ROMs from realme support site (read here why). any idea how to explain this in easy understanding word for me to have a stock recovery.img for RMX3363