Related
HI Guys , its me again so after a long working night of disabling encryptions and verifications i finaly was able to boot a AOSP Generic System Image on my LG G7 (EUROPEAN VARIANT ONLY) and now im here to show you how to install
How to install ?
Download the GSI from PHH AOSP thread , take a/b ones with ot without gapps as you like
Download my SecuretyOff-Vendor-image and my Permissive boot.img
Reboot to fastboot and unlock your bootloader if you havent done it yet (you can find tutorials online, same method as on g6 and previous)
flash the magisk enabled securetyoff permissive kernel with the command "fastboot flash boot_a pathtoimghere"
Reboot your G7 to LG Stock os and install magisk manager and TerminalEmulator from PlayStore
Now copy the Downloaded Vendor file to your internal sdcard and rename it to vendor.img
Open TerminalEmulator (adb shell works aswell) and type su, hit enter, then type "dd if=/sdcard/vendor.img of=/dev/block/bootdevice/by-name/vendor_a" , hit enter m this will take some time pls be patient
Once youre done with flashing the new vendor reboot to fastboot again and flash the GSI with the following command "fastboot flash system_a pathtoimghere"
One last step before you can enjoy AOSP type "fastboot -w" and then "fastboot reboot"
Whats Working ?
So for me everyting works so far i just noticed 2 small bugs till now
1. the Notification LED wont stop blinking (im on that already)
2.sometimes the display turns black for about 0,5secs
3. if your headphone jack doesn't work open up a root shell and enter "setprop persist.sys.overlay.devinputjack true"
Credits
Me for testing and patching the **** out of that boot.img and vendor.img
AutoPrime for his G7 system Dump
Phhuson for his brilliant work on GSI's
Zefie for recommending me the right tool to repack kernel without bootloops (xD)
SGMarkus for providing ideas and additional Help
reserved
reserved 2
Update , Ressurection Remix Gsi and LineageOS Gsi work too , also i was able to fix the blinking led , but it doesnt work at all anymore (lights hal doesnt load will investiagte tomorrow) but RR or Los doesnt have gapps packed with them so you will need to wait for twrp to be ready (i think i will finish it in next few days)
J0SH1X said:
HI Guys , its me again so after a long working night of disabling encryptions and verifications i finaly was able to boot a AOSP Generic System Image on my LG G7 (EUROPEAN VARIANT ONLY) and now im here to show you how to install
How to install ?
Download the GSI from PHH AOSP thread , take a/b ones with ot without gapps as you like
Download my SecuretyOff-Vendor-image and my Permissive boot.img
Reboot to fastboot and unlock your bootloader if you havent done it yet (you can find tutorials online, same method as on g6 and previous)
flash the magisk enabled securetyoff permissive kernel with the command "fastboot flash boot_a pathtoimghere"
Reboot your G7 to LG Stock os and install magisk manager and TerminalEmulator from PlayStore
Now copy the Downloaded Vendor file to your internal sdcard and rename it to vendor.img
Open TerminalEmulator (adb shell works aswell) and type su, hit enter, then type "dd if=/sdcard/vendor.img of=/dev/block/bootdevice/by-name/vendor_a" , hit enter m this will take some time pls be patient
Once youre done with flashing the new vendor reboot to fastboot again and flash the GSI with the following command "fastboot flash system_a pathtoimghere"
One last step before you can enjoy AOSP type "fastboot -w" and then "fastboot reboot"
Whats Working ?
So for me everyting works so far i just noticed 2 small bugs till now
1. the Notification LED wont stop blinking (im on that already)
2.sometimes the display turns black for about 0,5secs
Credits
Me for testing and patching the **** out of that boot.img and vendor.img
AutoPrime for his G7 system Dump
Phhuson for his brilliant work on GSI's
Zefie for recommending me the right tool to repack kernel without bootloops (xD)
SGMarkus for providing ideas and additional Help
Click to expand...
Click to collapse
Amazing work friend
What about the rom with the DAC? I can change this in the settings of the sound more precise. So not like the lg rom, the preset sound profiles?
Look forward to this! Many thanks +++
what about the dac? sound does not work over jack connection.
Hi.
Does the wide camera work with this rom?
And does the radio fm work?
Where can I find the last release?
Thanks.
Sent from my LM-G710 using Tapatalk
ricxgp said:
Hi.
Does the wide camera work with this rom?
And does the radio fm work?
Where can I find the last release?
Thanks.
Sent from my LM-G710 using Tapatalk
Click to expand...
Click to collapse
wide angle works on aosp rom , fm radio idk but try , you can find the latest release in treble enabled device section of xda
Any word on AOSP 9? As far as I know it requires vndk 8.1 but the g7 launched with Android 8. Do we have to wait for Android 8.1/9 from LG for AOSP 9?
https://highonandroid.com/android-r...oject-treble-unlocked-bootloader-twrp-method/
I saw a video on youtube by max lee i do believe he said you could install this as long as you had twrp recover
I have the sprint verison so i cant try but if anyone with twrp can try and comment
LameMonster82 said:
Any word on AOSP 9? As far as I know it requires vndk 8.1 but the g7 launched with Android 8. Do we have to wait for Android 8.1/9 from LG for AOSP 9?
Click to expand...
Click to collapse
does not work will maybe never work
Guys, can anyone pls do this in adb (or if you have root with terminal app):
echo 0 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms >/sdcard/kallsyms.txt
UltraM8 said:
Guys, can anyone pls do this in adb (or if you have root with terminal app):
echo 0 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms >/sdcard/kallsyms.txt
Click to expand...
Click to collapse
With the stock ROM or with aosp?
LameMonster82 said:
With the stock ROM or with aosp?
Click to expand...
Click to collapse
Doesn't really matter
so the headphone jack is now fixed open up a root shell and type setprop persist.sys.overlay.devinputjack true then reboot and it will work
UltraM8 said:
Guys, can anyone pls do this in adb (or if you have root with terminal app):
echo 0 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms >/sdcard/kallsyms.txt
Click to expand...
Click to collapse
Hello, sorry for being so late but i finaly got the files that youre looking for. "Kptr_restrict" is attached in the post but "kallsyms" is too big so i uploaded it to my google drive. The link is:
https://drive.google.com/file/d/1Mn9jeS7n681dbRWvZqlundCuTAvNF4FJ/view?usp=drivesdk
LameMonster82 said:
Hello, sorry for being so late but i finaly got the files that youre looking for. "Kptr_restrict" is attached in the post but "kallsyms" is too big so i uploaded it to my google drive. The link is:
https://drive.google.com/file/d/1Mn9jeS7n681dbRWvZqlundCuTAvNF4FJ/view?usp=drivesdk
Click to expand...
Click to collapse
thx man!
LameMonster82 said:
Hello, sorry for being so late but i finaly got the files that youre looking for. "Kptr_restrict" is attached in the post but "kallsyms" is too big so i uploaded it to my google drive. The link is:
https://drive.google.com/file/d/1Mn9jeS7n681dbRWvZqlundCuTAvNF4FJ/view?usp=drivesdk
Click to expand...
Click to collapse
I've checked kallsyms, how did you get it? via terminal app, or adb (or even twrp maybe if it's possible on g7)? The prob is that functions addresses are zeros, that's not good.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I was able to solve the problem I had with the sensors, the gyroscope sensor and the accelerometer did not work, I discovered that it was because the persist.img partition was damaged, thanks to this method that works for me, With this tutorial you can also repair wifi and bluetooth if in your case it does not work.
I also clarify that this method works if you are ARB3 or ARB4
Attention: You must have the Bootloader unlocked and have Twrp installed
Download the lastest stable fastboot rom and unpack it. Find persist.img from downloaded folder and move it to internal storage.
1) Start the twrp with Vol + and power button
2) Advanced -> Terminal.
3) Execute these lines.
a) simg2img /sdcard/persist.img /sdcard/persist_EXT4.img - Converts de image from sparse to raw.
b) dd if=/sdcard/persist_EXT4.img of=/dev/block/bootdevice/by-name/persist - Flashes the persist block with new persist image.
4) Reboot to system.
Credits - 4pda
I hope it worked for you
Thanks for the tutorial. Someone in kaskus is trying to fix the sensor not working problem. He has UBL and already anti 4, need to be careful. Can't flash the persist.img 9.5.19.0 directly via fastboot (blocked by the ARP), even though has flash the dummy.img already. So he boot into TWRP dan try the dd command to put in the persist.img from fastboot rom immediately to the partition. Result? Bootstuck. Still can access fastboot and still can boot to TWRP. He have tried several method, and probably the mi flash with authorized account is the last resort. Since he only break his persist.img partition, I recommend him to try your method and it works!!! I just know that all img from fastboot rom are sparse img files.
BTW, I need some confirmation. We can flash the TWRP directly from fastboot or install it via TWRP too (updating TWRP by phone). Does it mean that the fastboot binary is capable to flash raw ext4 image and sparse img file? Or it is the TWRP that is capable to flash sparse img file? The dd command only accept raw img, not sparse img. That's why need to convert it first.
By using this method, we can basically dd manually every partition from TWRP, thus bypassing the anti 4 fastboot blocked out command.
This tutorial can also be used to bypass locked mi acc
GLokin666 said:
I was able to solve the problem I had with the sensors, the gyroscope sensor and the accelerometer did not work, I discovered that it was because the persist.img partition was damaged, thanks to this method that works for me, With this tutorial you can also repair wifi and bluetooth if in your case it does not work.
I also clarify that this method works if you are ARB3 or ARB4
Attention: You must have the Bootloader unlocked and have Twrp installed
Download the lastest stable fastboot rom and unpack it. Find persist.img from downloaded folder and move it to internal storage.
1) Start the twrp with Vol + and power button
2) Advanced -> Terminal.
3) Execute these lines.
a) simg2img /sdcard/persist.img /sdcard/persist_EXT4.img - Converts de image from sparse to raw.
b) dd if=/sdcard/persist_EXT4.img of=/dev/block/bootdevice/by-name/persist - Flashes the persist block with new persist image.
4) Reboot to system.
Credits - 4pda
I hope it worked for you
Click to expand...
Click to collapse
When you say the sensors do not work, do you mean that they do not rotate at all? Or do they cause games in fullscreen landscape mode to randomly flip upside down?
I had this bug in both ResurrectionRemix and LineagesOS, the only workaround is to force the device to be in landscape mode by changing the rotation to auto-rotate and back to landscape via the QuickSettings header bar
dgrayboy said:
When you say the sensors do not work, do you mean that they do not rotate at all? Or do they cause games in fullscreen landscape mode to randomly flip upside down?
I had this bug in both ResurrectionRemix and LineagesOS, the only workaround is to force the device to be in landscape mode by changing the rotation to auto-rotate and back to landscape via the QuickSettings header bar
Click to expand...
Click to collapse
the gyroscope sensor and the accelerometer did not work, but with this method it has been solved
GLokin666 said:
the gyroscope sensor and the accelerometer did not work, but with this method it has been solved
Click to expand...
Click to collapse
So previously, it totally would not rotate at all?
My issue is that the gyroscope and accelerometer works, but in landscape mode games, the screen would incorrectly flip upside down.
Minimizing the game and going to Accelerometer Calibration (https://play.google.com/store/apps/details?id=redpi.apps.accelerometercalibration) shows that the accelerometer is working fine, so not sure what could be causing the random upside down flips in landscape mode..
Does this way can also fixing broke fingerprint sensor? I've faced those problem sometimes when flashing too many custom rom not miui based. Flashing fastboot rom fixed it anyway...
GLokin666 said:
I was able to solve the problem I had with the sensors, the gyroscope sensor and the accelerometer did not work, I discovered that it was because the persist.img partition was damaged, thanks to this method that works for me, With this tutorial you can also repair wifi and bluetooth if in your case it does not work.
I also clarify that this method works if you are ARB3 or ARB4
Attention: You must have the Bootloader unlocked and have Twrp installed
Download the lastest stable fastboot rom and unpack it. Find persist.img from downloaded folder and move it to internal storage.
1) Start the twrp with Vol + and power button
2) Advanced -> Terminal.
3) Execute these lines.
a) simg2img /sdcard/persist.img /sdcard/persist_EXT4.img - Converts de image from sparse to raw.
b) dd if=/sdcard/persist_EXT4.img of=/dev/block/bootdevice/by-name/persist - Flashes the persist block with new persist image.
4) Reboot to system.
Credits - 4pda
I hope it worked for you
Click to expand...
Click to collapse
can you make it more specific how to convert sparse to raw
dgrayboy said:
So previously, it totally would not rotate at all?
My issue is that the gyroscope and accelerometer works, but in landscape mode games, the screen would incorrectly flip upside down.
Minimizing the game and going to Accelerometer Calibration (https://play.google.com/store/apps/details?id=redpi.apps.accelerometercalibration) shows that the accelerometer is working fine, so not sure what could be causing the random upside down flips in landscape mode..
Click to expand...
Click to collapse
This is for some users who have all sensors not working at all (get crossed at the sensor box). It is mostly come from the red box, chinese version. You are experiencing another random rotation issue, which happen in several users across multiple version including custom ROM. Some reported that they simply tap the phone and it suddenly flip upside down. I can't reproduce this, so it might be possible with the persist.img too.
Akhmadmandala said:
can you make it more specific how to convert sparse to raw
Click to expand...
Click to collapse
simg2img /sdcard/persist.img /sdcard/persist_EXT4.img - Converts de image from sparse to raw.
You type this in TWRP terminal emulator, before dd-ing the image to the persist partition.
Desmanto said:
This is for some users who have all sensors not working at all (get crossed at the sensor box). It is mostly come from the red box, chinese version. You are experiencing another random rotation issue, which happen in several users across multiple version including custom ROM. Some reported that they simply tap the phone and it suddenly flip upside down. I can't reproduce this, so it might be possible with the persist.img too.
simg2img /sdcard/persist.img /sdcard/persist_EXT4.img - Converts de image from sparse to raw.
You type this in TWRP terminal emulator, before dd-ing the image to the persist partition.
Click to expand...
Click to collapse
God thanks bro, i forgot to add space.
My phone got stuck but luckly i do solve it with your method.
Thanks man! You're awesome
Thanks , it's work for me.
i have flip issue when gaming. all sensor is oke no problem. but currently in custom rom xtended with custom kernel. does this method still worked or do i need to flash back miui rom first?
Additionally, this method will also fixed/permanently removes "Unofficial ROM" watermark issue on some CN device/ROM when migrating to Global ROM
What WiFi issues can be fixed with this method?
sidamos77 said:
What WiFi issues can be fixed with this method?
Click to expand...
Click to collapse
Like wifi and wifi hotspot can't turning on etc.
madorax said:
i have flip issue when gaming. all sensor is oke no problem. but currently in custom rom xtended with custom kernel. does this method still worked or do i need to flash back miui rom first?
Click to expand...
Click to collapse
You can do it in custom rom and miui. :fingers-crossed:
help me plz redmi note 5 pro
Hi please please help me miui note 5 pro some miui 10 beta wifi no longer working I tried with all the ways without you have returned miui 9 stable did not solve the problem I hope you help me please
((((( wifi mac address inconnu))))
abdogsm said:
Hi please please help me miui note 5 pro some miui 10 beta wifi no longer working I tried with all the ways without you have returned miui 9 stable did not solve the problem I hope you help me please
((((( wifi mac address inconnu))))
Click to expand...
Click to collapse
OK! Does your phone see the wifi networks around? If so, worry not! That had happened before and was not a hardware problem.
Sometimes, some partitions that are not touched by simply flashing, reflashing or restoring from twrp can get corrupted.
I believe that flashing a full rom from mi tolls on PC can solve it.
Also, this method should also.
In another thread I posted a zip (flash from TWRP) that worked for me in the past.. It simple removes some folders with corrupt files that **** your sensors. After a reboot, they come back to life. Mind to try? Also, a feedback would be appreciated!
Here it goes: https://forum.xda-developers.com/redmi-note-5-pro/how-to/masik-2-4-rom-t3828932/page31
GLokin666 said:
I was able to solve the problem I had with the sensors, the gyroscope sensor and the accelerometer did not work, I discovered that it was because the persist.img partition was damaged, thanks to this method that works for me, With this tutorial you can also repair wifi and bluetooth if in your case it does not work.
I also clarify that this method works if you are ARB3 or ARB4
Attention: You must have the Bootloader unlocked and have Twrp installed
Download the lastest stable fastboot rom and unpack it. Find persist.img from downloaded folder and move it to internal storage.
1) Start the twrp with Vol + and power button
2) Advanced -> Terminal.
3) Execute these lines.
a) simg2img /sdcard/persist.img /sdcard/persist_EXT4.img - Converts de image from sparse to raw.
b) dd if=/sdcard/persist_EXT4.img of=/dev/block/bootdevice/by-name/persist - Flashes the persist block with new persist image.
4) Reboot to system.
Credits - 4pda
I hope it worked for you
Click to expand...
Click to collapse
i have a redmi note pro. bootloader LOCKED, and i installed twrp. i tried this methos and i got simg2img not found.. pls help
edit: it worked!! probably bcos my bootloader is locked i cant convert it to raw file with the terminal, so here is what i did
i downloaded the persist.img for my phone and downloaded image kitchen (playstore) and used image kitchen to convert it to raw file.. and rebooted my phone to recovery-terminal then used the code dd if=/sdcard... bla... bla... as listed up... and i rebooted and bam... it worked .. am happy... thanks u are the man
sauliiin said:
OK! Does your phone see the wifi networks around? If so, worry not! That had happened before and was not a hardware problem.
Sometimes, some partitions that are not touched by simply flashing, reflashing or restoring from twrp can get corrupted.
I believe that flashing a full rom from mi tolls on PC can solve it.
Also, this method should also.
In another thread I posted a zip (flash from TWRP) that worked for me in the past.. It simple removes some folders with corrupt files that **** your sensors. After a reboot, they come back to life. Mind to try? Also, a feedback would be appreciated!
Here it goes: https://forum.xda-developers.com/redmi-note-5-pro/how-to/masik-2-4-rom-t3828932/page31
Click to expand...
Click to collapse
i forgot to mention to you that the file you share its empty. if i remeber well it only has META-INF file.
[Guide] [XT16XX] [Solve] G4+ Baseband/Network/Volte issue, Lost 1 IMEI & fingerprint
Important:
If you have IMEI=0, then this is the wrong thead. Follow this: [Guide] [XT16XX] [Solve] Moto G4/Plus IMEI=0 issue
This method is only tested on Nougat for now, for Oreo, new files will be needed.
Code:
#include <disclaimer.h>
/*
* Your warranty is now.......(wait a minute)........still valid?
*
* I am not responsible for bricked devices.
* YOU are choosing to make these modifications, and if you point
* your finger at me for messing up your device, I will laugh at you.
*/
This thread addresses the following problems:
Baseband version changed to some other country
Sim card getting detected, but no network
Both sims having a network but VoLTE doesn't work
G4 Plus turned to G4, i.e phone just shows one IMEI and no fingerprint
This method is only for the retail models of Moto G4/Plus, it may or may not work on any other models.
All of these issues have a common reason,
The modem files for your device has been corrupted/has some issue or have been changed to some other country.
Voltes isn't working since your baseband is of some other country and not Indian. If you have Indian baseband and still Volte doesn't work, then your modem files have been corrupted/ have some issues.
You have to push the modem, hw, fsg files for your own device.
We already had a thread addressing this issue, but it didn't have modem files for all baseband.
Finally, thanx to our fellow Moto G4 Plus users, for providing these files, we now have hw, modem, fsg files for all the five basebands i.e BRAZIL, LATAM, EMEA, INDIAN, and RETUSA.
Link to the files:
XT1640 [BRAZIL]:
Link: https://www.androidfilehost.com/?fid=11410963190603873179
md5: 8db666f13700e3d12b01051989e3f068
XT1641 [LATAM]:
Link: https://www.androidfilehost.com/?fid=11410963190603873829
md5: cab09417be82e508d0c54f54aac56498
XT1642 [EMEA]:
Link: https://www.androidfilehost.com/?fid=11410963190603873183
md5: e046d911b23c76cb88d5ccd7967d621f
XT1643 [INDIA]:
Link: https://www.androidfilehost.com/?fid=11410963190603873250
md5: d509c5a26305cc5261e707bdf91268e9
XT1644 [RETUSA]:
Link: https://www.androidfilehost.com/?fid=11410963190603873181
md5: 598191e577db1137df62ae996055f5da
Download modem, fsg, hw files according to your original baseband/device model.
Code:
Model Number Baseband
XT1640 BRAZIL
XT1641 LATAM
XT1642 EMEA
XT1643 INDIA
XT1644 RETUSA
Note: These files are extracted from the dual-SIM variant of Moto G4 Plus, so if you flash these on your Moto G4, these will work, but your device name will be changed to Moto G4 Plus (everything will still work fine, just your device will be treated as Moto G4 Plus by all apps) and if you flash these images on single SIM Moto G4 Plus, it will still work.
Pre-requisites:
You must be on Stock Nougat 7.0 (latest version preferred)
You must be rooted (install Elemental-X kernel first and then flash Magisk otherwise you will have boot issues)
Terminal app or adb drivers in PC/Laptop (I wouldn't recommend TWRP (official or unofficial as it has issues flashing hw.img)
Step 1: Download files
Download and place these files in your /sdcard directory.
/sdcard is the same as the Internal storage directory. Do not confuse it with micro Sdcard as it has its directory named as /external_sd
Step 2: Flash the files
Note: The below commands are to be typed in a terminal app or adb shell.
Q) How to type in adb shell?
A) Open command prompt in the folder where you have adb and fastboot installed and type:
Code:
adb shell
So lets start now!
Code:
su
This command it to get root access for the terminal/shell. Grant the root access and you will see that the $ symbol is replaced with # symbol which means that root access has been granted.
Code:
dd if=/sdcard/modem.img of=/dev/block/bootdevice/by-name/modem
dd if=/sdcard/fsg.img of=/dev/block/bootdevice/by-name/fsg
dd if=/sdcard/hw.img of=/dev/block/bootdevice/by-name/hw
Step 3: Flash the latest Stock ROM (April 2018)
That's it. After flashing, reboot and check your baseband. You would be on the baseband which you flashed in step 2.
Indian users, you will see INDIAN baseband if you flashed the files for it, and Volte would work.
Flash the latest Stock ROM from here: Stock N Firmware [Apr 01 Security Patch][fastboot]
Contributors:
@djumie and Erick Lima (for providing BRAZILIAN modem files)
@Nacoro and @Deivid_21 (for providing LATAM modem files)
@echo92 (for providing EMEA modem files)
@checksamir (for providing INDIAN modem files)
@Jleeblanch (for providing RETUSA modem files)
@Pranav (for testing the files)
@Heeth21 (and lastly, myself)
Also all the others who helped during the process
Complete Backup Zip/Script (All partitions)
Now since you have faced this issue, make sure to take a complete backup of all the partitions so that if you ever face an issue like this in future, you will always have your partitions with you to restore your device.
Here is the link to the thread to take complete backup of all partitions: [Guide] [XT16XX] Moto G4/Plus Complete Partition Backup/Restore Zip/Script
The above thread can backup/restore using TWRP flashable zip files for convenience.
reserved
Thank you for this guide, but unfortunately it didn't work. When I pushed the hw image my phone stop responding and I have to force a reboot with the power buttom. I will give up on this issue for now on. Thank you again.
I attached a logcat in case you can find something that could give an anwser about what happens after i push the hw img
Do I have to be on stock ROM for this to work? Can't it work when I'm on a custom ROM?
What happened was I flashed the latest arrow os build, which was faulty. I then clean flashed crdroid. After reboot, sim isn't working, and imei isn't showing anything. I restored my persist partition, with no result.
Any help?
Wow after Restoring Indian Baseband Volte works now.
Thanks Sir.
sxbino said:
Thank you for this guide, but unfortunately it didn't work. When I pushed the hw image my phone stop responding and I have to force a reboot with the power buttom. I will give up on this issue for now on. Thank you again.
I attached a logcat in case you can find something that could give an anwser about what happens after i push the hw img
Click to expand...
Click to collapse
There are a few more ways to make this work, so its too early to give up.
Are you on the latest Stock ROM (April 2018)? You need to be on the latest stock firmware for this to work as the files are extracted from the latest stock firmware.
1. Flash Stock ROM (latest version - April 2018) once again.
2. Flash official TWRP (I repeat official TWRP only).
3. Then go in Terminal of TWRP (Settings>Terminal), and then repeat step 2, but this time no need to type "su" command.
Edit: @sxbino, now that I have learnt a little to read logs, it appears that the logs doesn't contain anything about flashing those files.
Please collect logs from adb using the command:
Code:
adb logcat>log.log
This will start collecting and saving logs in a file named "log" which will be saved in the same folder where you have adb.
If you are using PC/Laptop to push the files, you can open 2 terminal/command prompt windows, one to collect logs and other to flash the files.
But is missing Brazil baseband.
I'm from Brazil and change mine for LATAM.
Does anyone have this files?
edjalmo said:
But is missing Brazil baseband.
I'm from Brazil and change mine for LATAM.
Does anyone have this files?
Click to expand...
Click to collapse
Right now, we haven't been able to get modem files for BRAZILIAN baseband. Will add them in the Google Drive link once they are available from fellow Brazilian users.
Edit: @edjalmo, BRAZILIAN modem files are now available.
CMKdaGreatest said:
Do I have to be on stock ROM for this to work? Can't it work when I'm on a custom ROM?
What happened was I flashed the latest arrow os build, which was faulty. I then clean flashed crdroid. After reboot, sim isn't working, and imei isn't showing anything. I restored my persist partition, with no result.
Any help?
Click to expand...
Click to collapse
You may try if you'd like to. It just didn't work for me(flashing/pushing those files on custom ROM) so I am asking to be on stock ROM.
All of the 64-bit Pie ROMs are causing this error. The developers are working hard to fix it.
I would recommend flash stock ROM. No need to worry about losing IMEI after flashing stock as now it is recoverable, the only condition is you should not try to restore somebody else's persist or efs partitions.
Heeth21 said:
You may try if you'd like to. It just didn't work for me so I am asking to be on stock ROM.
ArrowOS is causing some problem with efs partition. The developer Lyuu is working hard to fix it.
I would recommend flash sSock ROM. No need to worry about losing IMEI after flashing stock as now it is recoverable, the only condition is you should not try to restore somebody else's persist or efs partitions.
Click to expand...
Click to collapse
Somehow, I clean flashed crdroid again, this time restoring the efs partition right after ROM flash. Now my sim is working. Silly me
Update: BRAZLIAN modem files are now available and have been added to the drive link. OP has been updated.
Heeth21 said:
Right now, we haven't been able to get modem files for BRAZILIAN baseband. Will add them in the Google Drive link once they are available from fellow Brazilian users.
Edit: @edjalmo, BRAZILIAN modem files are now available.
Click to expand...
Click to collapse
Thank you very much
edjalmo said:
Thank you very much
Click to expand...
Click to collapse
@edjalmo, Please report back whether they worked or not. I have 2 pairs of modem files. If this one didn't work, I will upload the second pair of files.
Heeth21 said:
@edjalmo, Please report back whether they worked or not. I have 2 pairs of modem files. If this one didn't work, I will upload the second pair of files.
Click to expand...
Click to collapse
Yes! I tested and it worked! My model is XT1640.
Heeth21 said:
You may try if you'd like to. It just didn't work for me so I am asking to be on stock ROM.
ArrowOS is causing some problem with efs partition. The developer Lyuu is working hard to fix it.
I would recommend flash sSock ROM. No need to worry about losing IMEI after flashing stock as now it is recoverable, the only condition is you should not try to restore somebody else's persist or efs partitions.
Click to expand...
Click to collapse
The ArrowOS also broke the imei of my smartphone, I have tried everything but nothing, I hope that the developer of ArrowOS get a solution!
Heeth21 said:
Code:
#include <disclaimer.h>
/*
* Your warranty is now.......(wait a minute)........still valid?
*
* I am not responsible for bricked devices.
* YOU are choosing to make these modifications, and if you point
* your finger at me for messing up your device, I will laugh at you.
*/
This thread addresses the following problems:
Baseband version changed to some other country
Sim card getting detected, but no network
Both sims having a network but Volte doesn't work
G4 Plus turned to G4, i.e phone just shows one IMEI and no fingerprint
This method is only for the retail models of Moto G4/Plus, it may or may not work on any other models.
All of these issues have a common reason,
The modem files for your device has been corrupted/has some issue or have been changed to some other country.
Voltes isn't working since your baseband is of some other country and not Indian. If you have Indian baseband and still Volte doesn't work, then your modem files have been corrupted/ have some issues.
You have to push the modem, hw, fsg files for your own device.
We already had a thread addressing this issue, but it didn't have modem files for all baseband.
Finally, thanx to our fellow Moto G4 Plus users, for providing these files, we now have hw, modem, fsg files for all four basebands i.e LATAM, EMEA, BRAZIL, and INDIAN.
Here is the link to the files: https://drive.google.com/open?id=1NtOTKgmJIP_Ys26CYd9KBdwhWdGfbCqH
Download modem, fsg, hw files according to your baseband.
Note: These files are extracted from the dual-SIM variant of Moto G4 Plus, so if you flash these on your Moto G4, these will work, but your device name will be changed to Moto G4 Plus (everything will still work fine, just your device will be treated as Moto G4 Plus by all apps) or if you flash these images on single SIM Moto G4 Plus, it will still work.
Pre-requisites:
You must be on Stock Nougat 7.0
You must be rooted (install Elemental-X kernel first and then flash Magisk otherwise you will have boot issues)
Terminal app or adb drivers in PC/Laptop (I wouldn't recommend TWRP (official or unofficial as it has issues flashing hw.img)
Step 1: Download files
Download and place these files in your /sdcard directory.
/sdcard is the same as the Internal storage directory. Do not confuse it with micro Sdcard as it has its directory named as /external_sd
Step 2: Flash the files
Note: The below commands are to be typed in a terminal app or adb shell.
Q) How to type in adb shell?
A) Open command prompt in the folder where you have adb and fastboot installed and type:
Code:
adb shell
So lets start now!
Code:
su
This command it to get root access for the terminal/shell. Grant the root access and you will see that the $ symbol is replaced with # symbol which means that root access has been granted.
Code:
dd if=/sdcard/modem.img of=/dev/block/mmcblk0p1
dd if=/sdcard/fsg.img of=/dev/block/mmcblk0p16
dd if=/sdcard/hw.img of=/dev/block/mmcblk0p43
Step 3: Flash the latest Stock ROM (April 2018)
That's it. After flashing, reboot and check your baseband. You would be on the baseband which you flashed in step 2.
Indian users, you will see INDIAN baseband if you flashed the files for it, and Volte would work.
Contributors:
@echo92 (for providing EMEA modem files)
@checksamir (for providing INDIAN modem files)
@Nacoro and @Deivid_21 (for providing LATAM modem files)
@djumie and Erick Lima(for providing BRAZILIAN modem files)
@Pranav (for testing the files)
@Heeth21 (and lastly, myself)
Also all the others who helped during the process
Click to expand...
Click to collapse
I do not understand where to enter the commands, can you explain more detailed? does this also work for IMEI = 0?
luis dambrowski said:
I do not understand where to enter the commands, can you explain more detailed? does this also work for IMEI = 0?
Click to expand...
Click to collapse
Nope, if you have IMEI=0, go to this thread: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-moto-g4-plus-imei0-issue-t3859068
If there is any problems like baseband/network after restoring IMEI, come to this thread.
Update: RETUSA modem files are now available and have been added to the drive link. OP has been updated.
I just installed the files of the Brazilian version, they worked perfectly in the g4 xt1626, only the part of tv does not appear because my model is the version no plus, but the baseband is now correct, brazilian version. I just have to thank Heeth21, his job in keeping a baseband database and etc is phenomenal, will help a lot of people.
Dear all,
Here is a tutorial to unlock meizu E3 without any malicious software.
The idea is to edit frp partition and make the fastboot flashing unlock pass the security check.
Please note below might damage your phone so do it as your own risk, i do not responsible to any damage made.
Detail step:
(1)get root access
(2)install terminal emulater app
(3)dump frp partition
(4)modify frp by hex editor at offset 7fff8 and 7fff to 1 (not sure 7fff8 or 7ffff take the effect, so i edit both) as frp1
(5)write frp1 back to frp partition
(6)reboot boot loader
(7)fastboot flashing unlock
(8)press up-vol or down-vol (not sure, i stop here, feedback welcome)
(9)done
This is generic enough for MTK and Qcom soc, success story other than sdm636 and mt6755 are welcome.
Other phone unlock tutorial:
Meizu M3note bootloader unlock
Regards,
99degree
An unofficial twrp for MeizuE3 is available below for people unlocked bootloader and would like to play with custom rom.
twrp custome ver 3.3.1:
http://s000.tinyupload.com/?file_id=01088261345935635855
-ramdisk is from twrp.me model whyred
-kernel is self compile, based on LA.UM.8.2.r1-05700-sdm660.0
-with lcd and touchpad driver patched
BTW, this twrp support encrypted data partition, so it is working parallel with flyme8 well.
An official MeizuE3 recovery img is also provided here for people would like to boot and restore flyme back.
https://gofile.io/?c=pFRTJy
A vlog for booting MeizuE3 with LineageOS 17.1 up to splash screen is available at youtube:
It is based on below LOS custom system build from rcstar6696 and kvsjxd, credit him:
https://forum.xda-developers.com/mi-a2/development/10-x-lineage-17-0-jasminesprout-t3966643
and with his another wayne vendor:
https://forum.xda-developers.com/mi-a2/xiaomi-6x-wayne/rom-lineageos-17-0-t3989193
Found in other thread* that mentioned about persist partition might be wiped by LOS17 or other custom rom and cause Wlan mac missing etc. I suspect this is also true for unstable wifi too. So if there is anybody have an original persist partition dump please upload and share. [20200303]The issue is fixed by two thing. /persist/wlan_mac.bin modification. Recompile kernel to include 3 more modules (fw-api, qca-wifi-host-cmn, qcacld-3.0).
https://forum.xda-developers.com/showpost.php?p=80217431&postcount=2
Hi there,
MeizuE3 boots up LOS17.1 with WIFI, detail is at below youtube video. Check it out!
Custom ROM from rcstar6696 and ItsMeShouko, creadit them.
https://forum.xda-developers.com/mi-a2/development/10-x-lineage-17-0-jasminesprout-t3966643
Or my modified ROM based on above jasmine sprout ROM.
https://forum.xda-developers.com/android/development/meizu-e3-lineageos-17-1-rom-porting-t4055605
Thx,
99degree
The intention behind this thread is to share some experience of a little project where I try to migrate the Sony Xperia Shinano devices (based on Qualcomm MSM8974 chipset with a Broadcom BCM4339 wifi/bluetooth chip) from the old bcmdhd wifi driver to a close-to-mainline brcmfmac driver. I want to share the progress and status here, and maybe get some hints. It is work in progress, and for sure it still contains some mistakes - I haven't done something like this before and am still learning.
Why?
The Shinano devices are still maintained by the LineageOS, and some devices are currently on the official LineageOS 17.1 stream.
The kernel however is terribly outdated, based on msm-3.4
There are some wifi issues with all LineageOS-based ROMs since years, like weak 5GHz connections and non-working wifi in some countries. There are some hacks around that, but they work (afaik) by practically disabling the kernel-level regulatory system by e.g. setting a static country code like "DE".
I am curious if we can improve that by updating the kernel drivers and network/wifi components, and maybe also the firmware (to the latest release available from Broadcom, 6.37.34.43 ?) . I got the ideas from Sonyxperiadev/Loire (+ related platform config), the Linux Backport Project and other MSM8974 based devices.
Working so far:
Did a few tests only so far, STA with WPA2 and p2p (hotspot) seem to work
Wifi connection is stable on 2,4GHz on 00 world regulatory domain (tested on a Z3 and a Z3c)
5GHz manually setting a country code (could only test DE)
Switching countries / setting new regulatory domains is now working, too
Download speed looks OK to me, in my case at least better than before Download >60MBit, Upload >30 Mbit on some initial tests.
Not working yet:
WifiHAL (qcom-caf) does not work correctly. This may create multiple issues, tbd.
Connection bandwidth seems to be not reported correctly
I don't know if wowlan works (interrupts working?)
Stability: After 1-2 days without reboot wifi sometimes crashes but immediately reconnects. Reason not yet understood.
Patches & Picks
Kernel:
backported and configured brcmfmac, cfg800211 wireless configuration API and wireless network stack from linux-stable v5.8 by adopting the compatibility patches from the linux backporting project.
updated Shinano device tree, updated Z3, Z3c and Z2 (Z2 test needed!) defconfigs (unset bcmdhd and enabled brcmfmac) and removed board-sony_shinano-wifi.o in the arch-msm makefile
Note: the backported drivers and compatibility-patches are located in a separate backports/ subdirectory
Sorry, this is work in progress and contains some hacks, to be cleaned up later
--> https://github.com/LineageOS/androi...1...Tom1000:lineage-17.1-driver-backport-v5.8
Vendor blobs / device z3(c): removed proprietary firmware and replaced that by publicly available firmware for bcm4339 on linux-firmware.git
z3c --> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
z3 --> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
Shinano-common: Use qcwcn instead of bcmdhd WLAN device, serve wpa_supplicant_overlay.conf
--> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
msm8974-common: raise wpa_supplicant version (unknown if we need that) and update sysfs node for MAC address
--> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
As a follow up, the driver seems to work quite stable already. I still have issues with nl80211 private commands, as a mainline brcmfmac does not seem to accept command strings passed via a libnl control socket like this:
qcwcn/wpa_supplicant_8_lib/driver_cmd_nl80211.c
@vknecht : I've seen your backporting work for the Xperia X. How does this work for Loire with SODP? Does e.g. a "set country code request" work for you, and if so, can you give me a hint?
I need some feedback from people with a Z3/Z3c/Z3Dual to see if the new builds work in affected countries, where 5GHz wifi is not working on current custom ROMs like e.g. LineageOS 17.1. I would appreciate if you test one of the builds below and send me a full log.
WARNING: The following builds are for debugging purpose only. Do not use them as a daily driver, as they have SELinux disabled and create excessive log entries. This ROM is not stable, some features are not yet implemented.
Xperia Z3 (D6603):
lineage-17.1-20201227-UNOFFICIAL-z3.zip
drive.google.com
Xperia Z3c (D5803):
lineage-17.1-20201227-UNOFFICIAL-z3c.zip
drive.google.com
Xperia Z3Dual (D6633) Update 10Jan2021:
lineage-17.1-20210110-UNOFFICIAL-z3dual.zip
drive.google.com
Z3Dual build has SELinux enabled already
If possible, please follow these steps:
Install ROM with TWRP for Android 10 or Lineage Recovery for 17.1
If possible, factory reset the device. Be sure to get rid of all former Magisk modules which try to set country codes etc. (if applicable).
Make sure a a local SIM card is inserted.
Boot the device. Enable mobile data and enable wifi. Connect to a 5GHz capable access point or router.
Optional: Increase log buffer size. This may be required as the kernel is set to verbose logging, creating large logfiles. You can do this via settings/developer options or via adb:
adb logcat -G 8M
Get close to the access point or router, so that the device would prefer 5GHz over 2.4GHz.
Reboot the device and let wifi connect. Check if device uses a 5Ghz connection. (Ignore bandwith / speed for now.)
Create a logfile, e.g. with this command via adb:
adb shell logcat -d -b all > mylog.log
The logfile may contain private information, so I recommend not to post them public. Together with the ligfile I would like to know
a) Wifi 5GHz working?
b) The country in which you have tested this.
nice work bro.
i live in iran and in this build my Z3 Dual detects wifi networks while the sim card is also connected.
but in 10 Jan 2021 update my phone can't detect my router's wifi unfortunately while the previous build could do it without problems.
hotspot turns on on both 2.4GHz and 5GHz.
in this new build cellular network and data are working.
Thanks @TheShadowOfAGhost20 !
Can you please run a root shell (E.g. by connecting via ADB, run adb root, then adb shell) and then
$> iw wlan0 scan → scan for networks
and then look if your access point is found?
Furthermore, can you please check which WiFi channel this particular router ist set to, and if possible the bandwidth?
Mr.Tom_Tom said:
Thanks @TheShadowOfAGhost20 !
Can you connect via ADB, run adb shell and then
$> iw wlan0 scan → scan for networks
and then look if your access point is found?
Furthermore, can you please check which WiFi channel this particular router ist set to, and if possible the bandwidth?
Click to expand...
Click to collapse
i did that but got this error: "/system/bin/sh: iw: inaccessible or not found"
but i found the cause: my wifi channel was set to 12. i changed it and then got detected!
TheShadowOfAGhost20 said:
i did that but got this error: "/system/bin/sh: iw: inaccessible or not found"
Click to expand...
Click to collapse
Sorry I forgot to write that you have to do this as root, I edited the post accordingly.
TheShadowOfAGhost20 said:
i found the cause: my wifi channel was set to 12. i changed it and then got detected!
Click to expand...
Click to collapse
Tha sounds reasonable. However, Channel 12 should be usable in IR.
Mr.Tom_Tom said:
Sorry I forgot to write that you have to do this as root, I edited the post accordingly.
Tha sounds reasonable. However, Channel 12 should be usable in IR.
Click to expand...
Click to collapse
channel 13 has detection problem too. the others are OK
.sorry erroneous post
New buildsFeedbacks have been positive so far, so here are some updated builds.
Lineage Sources* as of 20 March 2021
Kernel sources* based on Linux 3.4.113 with backported wifi from 5.8.18 plus cherry-pick of the following changes:
bluetooth: fixed #ifdef'ed PM callbacks ("BTLowPower" wakelock) 50f16d16b32871c5ce97b029e68692008c848bb2
SELinux enforcing
Build as userdebug, normal loglevels
* For links to sources see 1st post. Z3Dual does not have official Lineage17.1 sources yet, bringup is in progress.
Xperia Z3 (D6603):
HiDrive
hidrive.ionos.com
md5: d7aaf1fea120df3e2aad10b3a2d32226
Xperia Z3c (D5803):
HiDrive
hidrive.ionos.com
md5: 456ff87441c3a63e8dc8c7a8d03bdf39
Xperia Z3Dual (D6633):
HiDrive
hidrive.ionos.com
md5: 1848681c82d608f3212f1ace621327cb
As always, feedback is welcome.
Has anyone found a bug/installed this latest build yet? lineage-17.1-20210320-UNOFFICIAL-z3dual
Finding this super stable.. The only thing that does not work for me is the advanced boot recovery that goes back into system, But that's a known issue.
Mr.Tom_Tom said:
New buildsFeedbacks have been positive so far, so here are some updated builds.
Lineage Sources* as of 20 March 2021
Kernel sources* based on Linux 3.4.113 with backported wifi from 5.8.18 plus cherry-pick of the following changes:
bluetooth: fixed #ifdef'ed PM callbacks ("BTLowPower" wakelock) 50f16d16b32871c5ce97b029e68692008c848bb2
SELinux enforcing
Build as userdebug, normal loglevels
* For links to sources see 1st post. Z3Dual does not have official Lineage17.1 sources yet, bringup is in progress.
Xperia Z3 (D6603):
HiDrive
hidrive.ionos.com
md5: d7aaf1fea120df3e2aad10b3a2d32226
Xperia Z3c (D5803):
HiDrive
hidrive.ionos.com
md5: 456ff87441c3a63e8dc8c7a8d03bdf39
Xperia Z3Dual (D6633):
HiDrive
hidrive.ionos.com
md5: 1848681c82d608f3212f1ace621327cb
As always, feedback is welcome.
Click to expand...
Click to collapse
hi mr.tom. it's perfect as always, found no bug except wifi signal power, it's weak compared to stock roms but there was no difference in speeds. maybe it's because of wifi icon that shows little weaker signal.
and about overheating: i didn't test this build for long but while working with it i have noticed that my device is cooler than previous builds, maybe it's because of this new kernel.
i have recorded 4k for about 7 minutes then my phone rebooted i think that was because of too much heat, then i've reinstalled stock rom, however, stock rom's camera won't let me record much and the app shuts down because of heat, so i can't find out if stock rom can record 4k at least without rebooting.
i need to test this build for more time i hope the heating is now gone
and one question: can you port cyberian camera mod for these roms? or is that possible?
netwave said:
Has anyone found a bug/installed this latest build yet? lineage-17.1-20210320-UNOFFICIAL-z3dual
Finding this super stable.. The only thing that does not work for me is the advanced boot recovery that goes back into system, But that's a known issue.
Click to expand...
Click to collapse
lineage os recoveries have these problems yet, there's no fix for that, only the developer can fix it. currently the twrp works if you flash it to FOTAKernel partition but i think the twrp is useless because it doesn't install these builds.
Surely better to do: fastboot boot recovery-20201012-TESTING-z3dual.img rather than a "flash" recovery. What would be the point in flashing a recovery if its not working.
Hey
Thanks @Mr.Tom_Tom for new build and @TheShadowOfAGhost20 for testing dev builds!
today i installed the new release
but i have some problems with recovery and boot
after installing Lineage i cannot boot to recovery again
i tried adb, android advanced boot options and "fastboot boot image.img"
none of them taken me to recovery mode
so i needed to install Magisk , OpenGApps , and rom itself with adb sideload and reboot to system because i can't boot to recovery again
i'm now installing my apps for daily usage testing - i need about one or two week to test and use and see if anything is wrong or not
for now WiFi problem is gone , i have full wifi access and both sims antenna
again , thanks to everyone puts effort on this project (and sorry for bad English)
i will update this post if i found anything
navidmafi said:
today i installed the new release
but i have some problems with recovery and boot
after installing Lineage i cannot boot to recovery again
i tried adb, android advanced boot options and "fastboot boot image.img"
none of them taken me to recovery mode
Click to expand...
Click to collapse
If your going to settings\system\developer options\advanced restart\power\restart recovery , Forget it! this method doesn't work for now, & will only boot you back into Lineage. It's an issue that hopefully get's fixed in the future.
But here's a better way of entering recovery without having to flash it...
Check all your drivers are installed correctly & make sure you have the correct recovery to hand.
Here's what I Command:
adb devices
adb reboot bootloader
fastboot devices
fastboot boot recovery-20201012-TESTING-z3dual.img
Good luck!
Hey again
Thanks to @netwave i can now boot to recovery without problems by going to fastboot from adb , and booting image directly by "fastboot boot"
while using devices after installing new release , i have a problem with WiFi connectivity
when i lock the screen by power button , the wifi disconnects
for example i use whatsapp a lot and when screen is locked wifi is not connected
i checked power settings - and even set the battery profile to "Quick" (and battery saver is off) but it did not help
is this a bug or a feature?
navidmafi said:
Hey again
Thanks to @netwave i can now boot to recovery without problems by going to fastboot from adb , and booting image directly by "fastboot boot"
while using devices after installing new release , i have a problem with WiFi connectivity
when i lock the screen by power button , the wifi disconnects
for example i use whatsapp a lot and when screen is locked wifi is not connected
i checked power settings - and even set the battery profile to "Quick" (and battery saver is off) but it did not help
is this a bug or a feature?
Click to expand...
Click to collapse
Have you tried without Magisk installed? Don't use v22.0 what ever you do as it disables WiFi
Ow
I'm using Magisk and it is version 22.0
and even root not works
should i reflash ?
Edit : Ok i'm flashing again now
navidmafi said:
Ow
I'm using Magisk and it is version 22.0
and even root not works
should i reflash ?
Click to expand...
Click to collapse
Install the Magisk uninstall.zip from recovery
when your back in Lineage your still have a disabled WiFi as Magisk does not uninstall correctly.
So Install the original boot extracted from the Lineage.zip to get things working again.
- adb devices
- adb reboot bootloader
- fastboot devices
- fastboot flash boot boot.img
- fastboot reboot
Then your be sorted.