[Guide][DualBootPatcher] Multi Boot for Note Pro 12.2 - Galaxy Note Pro 12.2 Android Development

I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
First of all, I want to say big thanks for @chenxiaolong
Only his hard work allowed us to use an easy way to switch firmware.
I just built the debug version of the program with small changes to our tablets, checked it and pulled request to the author.
From today (version 9.1.0.r205.g1dc88ed2) our devices are officially supported.
Supported both devices – SM-P905 (viennalte) and SM-P900 (v1awifi).
SM-P905 - tested by me.
SM-P900 - not checked yet.
Official site: https://dbp.noobdev.io
Source code: https://github.com/chenxiaolong/DualBootPatcher
Official thread: https://forum.xda-developers.com/showthread.php?t=2447534
Here I just want create a small guide, how to use program.
Primary rom – big rom (touchwiz rom), it will be store in system partition. Another roms will eat part of data partition.
Let's see example:
Primary firmware – touchwiz rom (my port or official 5.0.2 firmware) with root.
First additional firmware – lineage 13
Later you can add as many firmwares as you want.
1. Download additional firmwares and gapps (if you need it)
2. Download the most recent snapshot release of Dual Boot Patcher and install it on tablet.
3. Open Dual Boot Patcher and grant root permission. Open menu (3 lines at the top left corner) and go to the ROMs. It will promt set kernel (say yes) or you can press 3 dot menu key and click “Set kernel”. It's should be done only once - Dual Boot Patcher will store boot for primary partition.
4. Then open menu again and go to the “Patch Zip file”. Press “+” at the right bottom corner and then “Add flashable zip”. Chose “lineage 13” zip file. In new small window: Device will be selected automatically (LTE or Wifi version), in the “Partition configuration” select “Data slot” and then enter an ID: “lineage13” for example. In description you will see: “Installs ROM to /data/multiboot/data-slot-lineage13” and press continue. Then program will prompt store new zip file. It's very important: you should store zip in the internal storage. Then you need to start convert (press checkbox at the right top corner).
5. Make item 4 for gapps (on this moment I getting crash of the program, just run program again). When you will enter an ID – it's should be the same as for firmware. If you entering “lineage13” for rom, you should entering “lineage13” for gapps too.
6. Now we have both files in the internal storage. Reboot in TWRP. Very important: just flash both files without ANY wipes and then reboot.
7. Your device will boot into new rom. Install Dual Boot Patcher app and set the kernel for your second ROM as well.
8. Now if you want back to the primary rom – in ROMs menu just press to the primary rom (you will see message: “Successfully switched ROM”) and reboot.
9. If you need more additional roms – repeat items 4-7 with new Data slot ID
10. Wipe additional rom – in ROMs – press 3 dot menu for needed rom – select “Wipe ROM” - and check all items, except last one (“Multiboot files”).
11. Remove additional rom – in ROMs – press 3 dot menu for needed rom – select “Wipe ROM” - and check all items here.
I played yesterday with Dual Boot Patcher, installed 4 roms - it's working great.
Just carefully use guide.

@Valera1978
Awesome news! Thank you for sharing.

---

nick_stokes said:
I ask you to clarify, the patch should be applied to all files? supersu, xposed, any addons? or only ROM and GApps?
Click to expand...
Click to collapse
All files.
The idea is: replace links (mount) to partitions (like system, data, cache) to folder in data partition or sdcard. This is why we need to patch the firmware and additionals in program.
So we need to be careful with the aroma installer that use their own update-binary (not our case).
I checked on the 13.0, 14.1 and my port. All was fine.

---

error message
i clicked 'set kernal' but received an error message "could not determine the boot partition because this device's codename 'v1awifikx' is not recognized"
what should I do? help please.... T_T

TaeJaLee said:
i clicked 'set kernal' but received an error message "could not determine the boot partition because this device's codename 'v1awifikx' is not recognized"
what should I do? help please.... T_T
Click to expand...
Click to collapse
Added the request (https://github.com/chenxiaolong/DualBootPatcher/pull/485) to the author.
I hope soon (today\tomorrow) will be a version with v1awifikx support.

SM-P901 ( v1a3g, v1a3gxx ) not supported, please add too.

Could you add gtanotexlwifikx codename for the Samsung Galaxy Note Pro 12.2 (Wifi) ? Please...

TaeJaLee said:
Could you add gtanotexlwifikx codename for the Samsung Galaxy Note Pro 12.2 (Wifi) ? Please...
Click to expand...
Click to collapse
in patcher choose v1awifi

it occurs error in installing..
I guess because of different codename (T800 <-> P900)
(without dualboot patching, it was installed successfully)

Hi @Valera1978
thanks for this amazing port.
I did successed in flashing my primary ROM (a modified & rooted & bloatware free '5.0.02' Samsung stock rom: LL-5.0.2-TW]CivZ_P900_Lollipop-5.0.2-Rev4.0 [BPA1][Final Release]), then installed the DualBoot app with success and set the kernel -> fine.
Then I patched an unofficial resurrection remix 5.8.5 as multiboot-data-01 with its respective opengapps pico, both with success and flashed them with TWRP also with success.
RR ROM boot and setup are fine!
up to there all is fine.
But then I simply can't install the DualBoot App on my data-01 ROM (the RR 5.8.5). I get an error message saying I can't install (don't have the exact message in mind and I forget to bring my tab with me at work).
what could cause this miss-behavior?
I know I can still swap ROMs with TWRP with the tips you mentionned (did not tried yet as I did not finalized setting up my RR rom).
For folks wanting to try DualBootPatcher on P900 (v1awifi) do not try to install as secondary nor as cashed slots: you simply do not have enough space (well I think I did succesed with a LineageOS on cache but not sure, RR always failed).
This seems to work grand on data slots.
thanks in adance for your help.
Die

Thank you for topic. lineage os of installation is completed and os is running but other files (gapps ) are not installed, error occurs.
Edit: resolved when the latest version of the twrp was installed
https://dl.twrp.me/v1awifi/twrp-3.4.0-0-v1awifi.img.tar.html
Thank you very much it works great.

does someone still has a link to the multiboot patcher?

KHPKero said:
does someone still has a link to the multiboot patcher?
Click to expand...
Click to collapse
hello, you can just search for the realese number and find it that way. There is more newer versions too

Related

[HOW-TO][LS-980] Restore, Downgrade, Install CyanogenMod on LG G2

READ ME FIRST I am more than willing to help you guys, so if you have questions, please ask me via my facebook page, as I get notifications there instantly. http://facebook.com/vacationlandtech
Also of note, I no longer have a LG G2, and it has been a long time since I made this, if you can be as descriptive as possible when asking questions, that would help a lot. Also, because it has been quite a while since I've been in the G2 community, I'm not up to speed on anything newer than early November, 2014. I don't have experience with ZVE+, CM12+, CloudyG3, etc. so if you have problems with new ROMs and software, get help from the people who make/support those ROMs and software.
Good luck!!
So I've been helping around the forums with people trying to install CyanogenMod on the Sprint LG G2 (LS-980). I have done this successfully and will outline my steps to do so below. A small caveat – I've only gotten this to work the way I'll outline below. I've tried getting CyanogenMod after the LS980ZVA/C/D OTA and no matter what I do I cannot get it to work. That being said, let's get to it.
Edit: I've added videos!!
Part 1: http://youtu.be/NRwlxeUprZE
Part 2: http://youtu.be/7rohyf_W13k
Part 3: http://youtu.be/Uw3J5ZTb3ro
*REMEMBER* - Always create Nandroid backups before flashing a ROM or doing anything, really.
Required Materials (some of these files (LS980ZV8_13.TOT) are over 2GB, FYI):
EDIT: I have put all the required files into a .ZIP archive and uploaded it to Mega
There has been a report that that the CyanogenMod .zip in my file is corrupt. You can still download the file I uploaded, just get CyanogenMod from the link below.
Update: I uploaded *just* the LS980ZV8_13.TOT file to Mega. Here is the link (beware it's not zipped, it's over 3GB).
Code:
* LS980ZV8_13.TOT - [URL]http://storagecow.eu/Xda/LG%20G2/Stock/Sprint/LS980ZV8_13.zip[/URL]
* LGLS980_20130904_LGFLASHv151.dll - [URL]http://storagecow.eu/Xda/LG%20G2/Stock/Sprint/LGLS980_20130904_LGFLASHv151.dll[/URL]
* LG Flash Tool - [URL]http://storagecow.eu/Xda/LG%20Software/TOT%20FlashTool/Setup_LGFlashTool_1.8.1.1023.exe[/URL]
* MegaLock.dll - [URL]http://storagecow.eu/Xda/LG%20Software/TOT%20FlashTool/MegaLock.dll[/URL]
* IOroot25 - [URL]http://downloads.codefi.re/autoprime/LG/ioroot/ioroot.zip[/URL]
* LG G2 (Verizon) USB Driver - [URL]http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00520120427[/URL]
* GApps - [url]https://s.basketbuild.com/gapps[/url]
Now, back up any files you want to keep from your phone. This process will remove EVERYTHING from your phone INCLUDING Internal Storage! Also install the USB Driver.
Let's get to it (please read all instructions before doing anything):
Resetting to Stock
Required files: LG Flash Tool, MegaLock.DLL, LS980ZV8_13.TOT, USB Drivers.
1. Install LG Flash Tool , but don't launch it yet!
2. Copy MegaLock.DLL to the root of the installation directory of LG Flash Tool.
3. Launch LG Flash Tool.
4. Check “Manual Mode”
5. Browse to the .DLL file you downloaded by clicking the “...” button to the right of the first text box.
6. Browse to the .TOT file (it'll have to be unzipped) by doing the same thing for the 2nd box.
7. Click okay, then click the green arrow at the top right of the window.
8. Wait for one of the boxes to turn green and say “Ready”
9. Turn off your phone.
10. Plug in the phone to your computer while holding the Vol+ key to put your phone in download mode.
11. Open Device Manager on your computer by pressing Win+R and typing “devmgmt.msc” without the quotes, then pressing enter.
12. Scroll down to “Ports” and expand it.
13. There will be an Android entry, right click it and select “Properties”
14. Select the Port Settings tab, and select Advanced.
15. Change the port number to 41.
16. You may have to unplug and reconnect your phone.
17. The box that said ready should now have some messages inside it (ie. “Waiting for connection.” and stuff about phone checks).
18. Allow the flash tool to do its job, after anywhere between 10 minutes and half an hour the phone will be done resetting. In my experience, the flash tool will always say there was an error after the phone reboots, this is because the phone reboots into Android, but the flash tool has done everything it needs, don't worry!
19. You can now unplug your phone and close LG Flash Tool.
20. Your phone is now on stock LG firmware LS980ZV8!
** - If you're going on to flash CyanogenMod, get through the initial set up, let the phone activate, but don't worry about getting apps or settings, they'll be gone after we flash CM.
Rooting
Required files: IOroot25, USB Drivers
** - I'm going to write this as if you've just reset to stock firmware.
1. Navigate to Settings > About Phone > Software Information
2. Tap on Build Number 7 times, or until there is a pop-up stating that “You are now a developer!”
3. Go back to Settings
4. Go into Developer Settings
5. Enable USB Debugging
6. Plug your phone into your computer.
** - If there is a RSA Fingerprint pop-up, accept it and check Remember this fingerprint
7. Navigate to Ioroot (you may have to extract/unzip the files) and execute root.BAT
8. Follow the on-screen instructions.
** - Note that Ioroot automatically backs up your EFS partition, make sure to keep these files in a safe location, as they can come in handy if something goes wrong.
9. After Ioroot is finished, you can close the program, unplug your phone and disable USB debugging.
10. You're now rooted, you may verify by downloading a Root Checker app from the Google Play Store.
Installing a Custom Recovery
Required Files: None
1. On your phone, navigate to the Google Play Store.
2. Search for FreeGee and install it.
3. Open FreeGee and allow it to download the device list.
4. After the download is finished, you will see a changelog list, close this.
5. Tap on install TWRP (or CWM if you're more comfortable with ClockWork Mod).
** - I recommend TeamWin Recovery Project for newer users because it is more end-user friendly, touch-capable, etc.
6. Wait for FreeGee to do its thing, then you have a custom recovery installed.
7. If you want to, let FreeGee reboot you into Recovery in order to verify.
Installing CyanogenMod 11
Required Files: CyanogenMod 11 ZIP, USB Drivers
** - Get the CyanogenMod 11 ZIP from https://download.cyanogenmod.org/?device=ls980 I recommend using the latest SNAPSHOT – get the NIGHTLY only if there are problems with the SNAPSHOT.
1. Place the CM 11 ZIP on the root directory of your internal storage.
2. Power off your phone (without it plugged in).
3. Turn on your phone holding PWR+VOL-Down until the screen says “Recovery mode”
** - The screen may say something about a factory reset, in this case press the power button 3 times and you'll be brought into recovery.
4. Tap on install
5. Scroll down to the CM 11 ZIP and tap it
6. Follow the instructions and when prompted to wipe the dalvik and cache, select yes.
** - you may have to do an advanced wipe and select everything except for internal storage, but do this only if CyanogenMod doesn't install properly.
7. You now have CyanogenMod 11 on your phone!
**- You will have to install GApps in order to access the Google Play Store and other Google Apps. You can download it using the browser on your phone or by transferring the .zip file to the root of your phone.
**- To install GApps just boot into recovery, select Install, and navigate to the GApps .zip. Swipe to install.
If you have any questions or any issues, just let me know. Not everything is accurate as I don't have access to Windows right now so I'm going based off memory. I plan on reinstalling Windows 8.1 Professional and making a video to go along with this. If at any point throughout this walkthrough you find inaccurate information or something goes wrong, let me know and I'll help out/update the article. Good luck!
Thanks so much for your sharing this. I have downgrade my phone from ZVD to ZV7 and get it rooted and CM11 installed. However, I found CM11 is not stable and my GPS module didn't work now. Could you recommend a everyday-use ROM with tethering capability? Many thanks.
damiloveu said:
Thanks so much for your sharing this. I have downgrade my phone from ZVD to ZV7 and get it rooted and CM11 installed. However, I found CM11 is not stable and my GPS module didn't work now. Could you recommend a everyday-use ROM with tethering capability? Many thanks.
Click to expand...
Click to collapse
I use CyanogenMod 11 as my everyday ROM, never have any issues (besides some personal preferences). To confirm that you have a good stable build, check your build number and info. I will post mine below for you to compare to.
To check your build number navigate to Settings > About Phone
Code:
Model Number.................LG-LS980
CyanogenMod Version..........11-20140804-SNAPSHOT-M9-ls980
Android Version..............4.4.4
Baseband Version.............M8974A-AAAANAZM-1.0.190034
Kernel Version...............3.4.0-CM+
[email protected] #1
.............................Sun Aug 3 22:34:14 PDT 2014
I used this download for my CM: Direct Download from CyanogenMod
official.xian said:
I use CyanogenMod 11 as my everyday ROM, never have any issues (besides some personal preferences). To confirm that you have a good stable build, check your build number and info. I will post mine below for you to compare to.
To check your build number navigate to Settings > About Phone
Code:
Model Number.................LG-LS980
CyanogenMod Version..........11-20140804-SNAPSHOT-M9-ls980
Android Version..............4.4.4
Baseband Version.............M8974A-AAAANAZM-1.0.190034
Kernel Version...............3.4.0-CM+
[email protected] #1
.............................Sun Aug 3 22:34:14 PDT 2014
I used this download for my CM: Direct Download from CyanogenMod
Click to expand...
Click to collapse
I am using the same ROM as yours. I will flash back to Stock ROM and if the GPS still doesn't work, I have to contact LG to get a replace one.
damiloveu said:
I am using the same ROM as yours. I will flash back to Stock ROM and if the GPS still doesn't work, I have to contact LG to get a replace one.
Click to expand...
Click to collapse
Sounds good. I can confirm that my GPS works fine on this ROM so... Good luck. Let me know if you have any questions!
Can U help me with this....
I have LG G2 LS980ZVC Rooted device, and SuperUser is installed.
I want to migrate from stock ROM to CyanogenMod ROM.
But I want the device to work as of the LG G2 D802 (International).
As I will be using it in INDIA (GSM 850/900/1800/1900).
I am very much new to Android and confused to pick the ROM and about the installation procedure.
Seek expert advice about this concern.
Plz suggest... ( attach Hyper link of threads / Videos about the procedure of installation and ROM download link while replying).
Thanks in Advance.......
AJ, I will do some research as to unlocking this phone. I am a bit busy right now but I'll reply by the end of the day.
This phone is already unlocked and works fine with Indian SIM
This phone is already unlocked and works fine with any Indian SIM. I Just want to migrate to CyanogenMod ROM.
official.xian said:
AJ, I will do some research as to unlocking this phone. I am a bit busy right now but I'll reply by the end of the day.
Click to expand...
Click to collapse
I can't find any information regarding unlocking on CyanogenMod specifically, but maybe you could do the same steps at: http://forum.xda-developers.com/showthread.php?t=2655133 after you follow my instructions to install CyanogenMod.
:Confused
This phone is already unlocked and works fine with any Indian SIM.
I am Just confused to pick between these two CyanogenMod ROMs :
1. (ls980 LG G2 (Sprint))
https://download.cyanogenmod.org/?device=ls980
https://download.cyanogenmod.org/get/jenkins/78482/cm-11-20140804-SNAPSHOT-M9-ls980.zip
OR
2. (d802 LG G2 (Intl))
https://download.cyanogenmod.org/?device=d802
https://download.cyanogenmod.org/get/jenkins/78458/cm-11-20140804-SNAPSHOT-M9-d802.zip
And any guidelines to install the CynogenMod ROM, as I am New to this.
Thanks in Advance. .
official.xian said:
I can't find any information regarding unlocking on CyanogenMod specifically, but maybe you could do the same steps at: http://forum.xda-developers.com/showthread.php?t=2655133 after you follow my instructions to install CyanogenMod.
Click to expand...
Click to collapse
Never, I repeat NEVER flash or install ANYTHING that is not specifically for your phone!! This is the fastest way to brick your device, possibly permanently. I understand that you have already unlocked your phone, but you've done so on a stock ROM. What I was saying is follow my instructions to install CyanogenMod (the LS980 version) on your phone, then (re)unlock it following the instructions at the thread I linked to. I'm not sure how to unlock on CM11, but it can be done: LG G2 LS980 GSM UNLOCKED!: http://youtu.be/r8XCpm046-k
damiloveu said:
Thanks so much for your sharing this. I have downgrade my phone from ZVD to ZV7 and get it rooted and CM11 installed. However, I found CM11 is not stable and my GPS module didn't work now. Could you recommend a everyday-use ROM with tethering capability? Many thanks.
Click to expand...
Click to collapse
I did try and after a lot of got it to work CM11, you only need ZV8 modem/radio.
Had problems with the GPS even try a lot of apps none of them got it to work, then change the gps.conf file for the orginal LG conf and worked great. The only ROM that the GPS worked since the start was PA all of the others are based on CM so the file wont work, at least for me.
The gps.conf file its on "etc" folder.
CM really its great but to me Omni and most of all that i try in this days (trying to get a good GPS just to play Ingress) Its PA
Good luck
emi_fer said:
I did try and after a lot of got it to work CM11, you only need ZV8 modem/radio.
Had problems with the GPS even try a lot of apps none of them got it to work, then change the gps.conf file for the orginal LG conf and worked great. The only ROM that the GPS worked since the start was PA all of the others are based on CM so the file wont work, at least for me.
The gps.conf file its on "etc" folder.
CM really its great but to me Omni and most of all that i try in this days (trying to get a good GPS just to play Ingress) Its PA
Good luck
Click to expand...
Click to collapse
I've never had an issue with CyanogenMod. If you wipe before you install and don't do anything funky with it you shouldn't have a problem. Following my instructions CyanogenMod works flawlessly (for me at least).
official.xian said:
I've never had an issue with CyanogenMod. If you wipe before you install and don't do anything funky with it you shouldn't have a problem. Following my instructions CyanogenMod works flawlessly (for me at least).
Click to expand...
Click to collapse
Always Wipe data/Factory reset when change to a different ROM, as i said the only one that worked for me its PA because uses the stock gps.conf thats all
emi_fer said:
Always Wipe data/Factory reset when change to a different ROM, as i said the only one that worked for me its PA because uses the stock gps.conf thats all
Click to expand...
Click to collapse
How long ago did you have problems?
official.xian said:
So I've been helping around the forums with people trying to install CyanogenMod on the Sprint LG G2 (LS-980). I have done this successfully and will outline my steps to do so below. A small caveat – I've only gotten this to work the way I'll outline below. I've tried getting CyanogenMod after the LS980ZVA/C/D OTA and no matter what I do I cannot get it to work. That being said, let's get to it.
*REMEMBER* - Always create Nandroid backups before flashing a ROM or doing anything, really.
Required Materials (some of these files (LS980ZV8_13.TOT) are over 2GB, FYI):
Code:
* LS980ZV8_13.TOT - [URL]http://storagecow.eu/Xda/LG%20G2/Stock/Sprint/LS980ZV8_13.zip[/URL]
* LGLS980_20130904_LGFLASHv151.dll - [URL]http://storagecow.eu/Xda/LG%20G2/Stock/Sprint/LGLS980_20130904_LGFLASHv151.dll[/URL]
* LG Flash Tool - [URL]http://storagecow.eu/Xda/LG%20Software/TOT%20FlashTool/Setup_LGFlashTool_1.8.1.1023.exe[/URL]
* MegaLock.dll - [URL]http://storagecow.eu/Xda/LG%20Software/TOT%20FlashTool/MegaLock.dll[/URL]
* IOroot25 - [URL]http://downloads.codefi.re/autoprime/LG/ioroot/ioroot.zip[/URL]
* LG G2 (Verizon) USB Driver - [URL]http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00520120427[/URL]
Now, back up any files you want to keep from your phone. This process will remove EVERYTHING from your phone INCLUDING Internal Storage! Also install the USB Driver.
Let's get to it (please read all instructions before doing anything):
Resetting to Stock
Required files: LG Flash Tool, MegaLock.DLL, LS980ZV8_13.TOT, USB Drivers.
1. Install LG Flash Tool , but don't launch it yet!
2. Copy MegaLock.DLL to the root of the installation directory of LG Flash Tool.
3. Launch LG Flash Tool.
4. Check “Manual Mode”
5. Browse to the .DLL file you downloaded by clicking the “...” button to the right of the first text box.
6. Browse to the .TOT file (it'll have to be unzipped) by doing the same thing for the 2nd box.
7. Click okay, then click the green arrow at the top right of the window.
8. Wait for one of the boxes to turn green and say “Ready”
9. Turn off your phone.
10. Plug in the phone to your computer while holding the Vol+ key to put your phone in download mode.
11. Open Device Manager on your computer by pressing Win+R and typing “devmgmt.msc” without the quotes, then pressing enter.
12. Scroll down to “Ports” and expand it.
13. There will be an Android entry, right click it and select “Properties”
14. Select the Port Settings tab, and select Advanced.
15. Change the port number to 41.
16. You may have to unplug and reconnect your phone.
17. The box that said ready should now have some messages inside it (ie. “Waiting for connection.” and stuff about phone checks).
18. Allow the flash tool to do its job, after anywhere between 10 minutes and half an hour the phone will be done resetting. In my experience, the flash tool will always say there was an error after the phone reboots, this is because the phone reboots into Android, but the flash tool has done everything it needs, don't worry!
19. You can now unplug your phone and close LG Flash Tool.
20. Your phone is now on stock LG firmware LS980ZV8!
** - If you're going on to flash CyanogenMod, get through the initial set up, let the phone activate, but don't worry about getting apps or settings, they'll be gone after we flash CM.
Rooting
Required files: IOroot25, USB Drivers
** - I'm going to write this as if you've just reset to stock firmware.
1. Navigate to Settings > About Phone > Software Information
2. Tap on Build Number 7 times, or until there is a pop-up stating that “You are now a developer!”
3. Go back to Settings
4. Go into Developer Settings
5. Enable USB Debugging
6. Plug your phone into your computer.
** - If there is a RSA Fingerprint pop-up, accept it and check Remember this fingerprint
7. Navigate to Ioroot (you may have to extract/unzip the files) and execute root.BAT
8. Follow the on-screen instructions.
** - Note that Ioroot automatically backs up your EFS partition, make sure to keep these files in a safe location, as they can come in handy if something goes wrong.
9. After Ioroot is finished, you can close the program, unplug your phone and disable USB debugging.
10. You're now rooted, you may verify by downloading a Root Checker app from the Google Play Store.
Installing a Custom Recovery
Required Files: None
1. On your phone, navigate to the Google Play Store.
2. Search for FreeGee and install it.
3. Open FreeGee and allow it to download the device list.
4. After the download is finished, you will see a changelog list, close this.
5. Tap on install TWRP (or CWM if you're more comfortable with ClockWork Mod).
** - I recommend TeamWin Recovery Project for newer users because it is more end-user friendly, touch-capable, etc.
6. Wait for FreeGee to do its thing, then you have a custom recovery installed.
7. If you want to, let FreeGee reboot you into Recovery in order to verify.
Installing CyanogenMod 11
Required Files: CyanogenMod 11 ZIP, USB Drivers
** - Get the CyanogenMod 11 ZIP from https://download.cyanogenmod.org/?device=ls980 I recommend using the latest SNAPSHOT – get the NIGHTLY only if there are problems with the SNAPSHOT.
1. Place the CM 11 ZIP on the root directory of your internal storage.
2. Power off your phone (without it plugged in).
3. Turn on your phone holding PWR+VOL-Down until the screen says “Recovery mode”
** - The screen may say something about a factory reset, in this case press the power button 3 times and you'll be brought into recovery.
4. Tap on install
5. Scroll down to the CM 11 ZIP and tap it
6. Follow the instructions and when prompted to wipe the dalvik and cache, select yes.
** - you may have to do an advanced wipe and select everything except for internal storage, but do this only if CyanogenMod doesn't install properly.
7. You now have CyanogenMod 11 on your phone!
If you have any questions or any issues, just let me know. Not everything is accurate as I don't have access to Windows right now so I'm going based off memory. I plan on reinstalling Windows 8.1 Professional and making a video to go along with this. If at any point throughout this walkthrough you find inaccurate information or something goes wrong, let me know and I'll help out/update the article. Good luck!
Click to expand...
Click to collapse
I am in the process of resetting everything back to stock. However, I was reading other articles and it mentioned that you must choose the correct files that correspond to either the 16gigs or 32 gigs. In this set of instructions however, it only provides users with one zv8 file for download. I just don't want to mess something up by using the incorrect files. Would appreciate someone's help. Thanks
Robles23 said:
I am in the process of resetting everything back to stock. However, I was reading other articles and it mentioned that you must choose the correct files that correspond to either the 16gigs or 32 gigs. In this set of instructions however, it only provides users with one zv8 file for download. I just don't want to mess something up by using the incorrect files. Would appreciate someone's help. Thanks
Click to expand...
Click to collapse
I have seen what you're talking about elsewhere but I don't believe that this applies in this situation. I have the 32GB LS980, and haven't had an issue, still have all my storage space. From everything that I've gathered from the internet when learning how to do everything a wrote the size doesn't matter. If you're still concerned I can do some more digging, but I don't think you'll have a problem.
official.xian said:
I have seen what you're talking about elsewhere but I don't believe that this applies in this situation. I have the 32GB LS980, and haven't had an issue, still have all my storage space. From everything that I've gathered from the internet when learning how to do everything a wrote the size doesn't matter. If you're still concerned I can do some more digging, but I don't think you'll have a problem.
Click to expand...
Click to collapse
Very much appreciate your answer brother. I also have a 32gb model. No need to do more research. I will try this method ones I get home from work today. Ones again, I appreciate your repay and tutorial.
Robles23 said:
Very much appreciate your answer brother. I also have a 32gb model. No need to do more research. I will try this method ones I get home from work today. Ones again, I appreciate your repay and tutorial.
Click to expand...
Click to collapse
Glad to help. If you feel unsure about anything I'm also working on a video to upload to YouTube as well (after I finish it I'll edit the OP) that goes over the process. Good luck.
official.xian said:
Glad to help. If you feel unsure about anything I'm also working on a video to upload to YouTube as well (after I finish it I'll edit the OP) that goes over the process. Good luck.
Click to expand...
Click to collapse
Hell yeah I will love to watch and follow that tutorial. I will wait for it. Thank you!

[G800F/M/Y][ROM][5.1.1][LMY48G] CyanogenMod 12.1 for G800F/M/Y [Alpha 15/08/2015]

This is a CyanogenMod 12.1 ROM for the Exynos3470 based Samsung Galaxy S5 mini (G800F/G800M/G800Y). Support for G800M is untested so far.
DO NOT USE IT FOR G800H OR YOU WILL BRICK YOUR DEVICE
Although G800F and G800H share the same name they are not related in terms of hardware due to the different SoCs used (Exynos vs. Snapdragon).
Hence please do not ask for support or ROMs for the G800H.
Working features
Receiving and making calls
Hardware sensors (Light, Orientation, Compass, Proximity, Acceleration)
Audio
Bluetooth (audio in HFP seems to be distorted with at least some headset devices)
Wifi
HW accelerated GUI
USB-OTG (Keyboard, Mouse, USB-Audio, Mass-Storage)
Camera (pictures+video: Back+Front)
MTP storage
IR
GPS
NFC
Non-working features:
Fingerprint scanner (no app for tests found)
Pulse sensor + Step counter (no app for tests found)
Hall sensor
SELinux
Known issues:
See the Bug Report section of this thread
Disclaimer:
You flash this image at your own responsibility. I am not responsible for any damage that might be caused by flashing this image (bricked device, lost data, ...)
Flashing this kernel image will trigger the KNOX counter, so your warranty will be void.
Applications that use KNOX (e.g. "Private Mode") might not work anymore when returning to the stock ROM, as the device is regarded as compromised. Do not flash this ROM if you need those applications.
The image is only for Exynos3470 based S5 Mini variants SM-G800F/M/Y.
It might be instable, crash your device, drain your battery, or even might damage your smartphone (e.g. if an USB-OTG device drains too much power)
Some users reported that their touch-screen stopped working permanently after some weeks of usage. For some user's (two at the moment including me) NFC stopped working permanently. Probably this issues are not related to this ROM as also many stock user's complain about hardware issues (random reboots, black screens, unresponsive touchscreen) but you have been warned.
Backup your data before flashing and check if the original firmware is present (e.g. at SamMobile)
Click to expand...
Click to collapse
Before you start:
Backup your data, like call history, contacts, sms, WhatsApp messages, favourite app settings that are on internal and external sd (by using Titanium Backup or other apps available on PlayStore). At least all internal data will be lost in any case. If you have bad luck you might also loose data from your external sd card.
Download:
Odin3-v3.07 (it is contained in CF-Auto-Root)
TWRP 2.8.7.0 recovery image [08/07/2015] (AndroidFileHost Mirror)
CM 12.1 ROM for G800F/M/Y (AndroidFileHost Mirror)
Google Apps (contains Google Play, ...) for Android 5.1.1 from Jajb (Recommended) or the one that suits you best from Consolidated GApps.
Install recovery:
Reboot your device into Odin mode: turn off your device, then press Volume-Down + Home + Power button at the same time and release them.
Confirm the following warning message with the Volume-Up button.
Connect your device to your PC via USB
Make sure the device driver's are installed on your PC
Start Odin
In Odin select PDA and select the recovery image (recovery.tar.md5)
Check that only "Auto Reboot" and "F. Reset Time" is set
Click on "Start": the kernel image should be flashed now and the device should reboot afterwards. By flashing the recovery, your warranty will be void.
After the recovery flashing process was successful, power of your device. If not restart into Download mode and flash again or flash the stock rom.
Before you flash:
You need the latest TWRP recovery (see above). Otherwise TWRP might not be able to flash the ROM. This is because TWRP checks now if the device is "supported".
Wipe the device to avoid problems with remaining files from the old installation (see instructions below). This also applies if you already installed an older version of CM 12.1.
Flash CyanogenMod:
Reboot into recovery mode (Press Volume-Up + Home + Power button)
If you come from a stock ROM, this is your opportunity to make a Backup of your phone(Backup, then select Boot, System, Data, then swipe to backup). Note that the recovery might fail to restore the backup when you want to go back to the stock ROM (for me it got stuck after a restore during boot. But the backup was made with a different version of TWRP, so it might work in general) - simply do not expect too much of it at the moment.
If you haven't copied the installation files yet, you can now copy the GApps and CyanogenMod zip to your internal sd or external sd (be careful not to put the files into the data directory of the internal sd card as this will be deleted in the next step). Be sure that MTP is enabled (inside Mounts, click on Enable MTP), then, from your pc, copy the files. If MTP does not work from recovery, try it directly from Android or remove the external sd card from the phone and put it into your PC.
Wipe Dalvik Cache, Cache, System and Data (inside Wipe -> Advanced Wipe). Do not report problems if you did not wipe those partitions as the problems are most probably related to this!
Install the CM 12.1 ROM zip-package
Install the GApps zip-package
Reboot the system and enjoy a Lollipop
How to root:
No SuperSu is needed as CyanogenMod already comes with integrated root support. Root access is disabled by default.
You normally do not need root access. If you want to activate root access for apps, do the following:
Open the Settings menu, select "About Phone"
Tap on the "Build number" entry seven times. You should be notified, that the developer settings are now active.
Open the Settings menu, select "Developer options". Enable root access by selecting "Apps" in the "Root-Access" setting.
In case you want to go back to the stock ROM:
lf you do not have the latest ROM for the G800F you can download it from SamMobile
Reboot your phone into Odin mode
Open Odin on your PC and connect your smartphone with your PC via USB
If you have a zip-file unzip it so that you have a .tar.md5 file
In Odin click on the PDA button and select the .tar.md5 file. Then press "Start".
Normally the stock rom fails to boot as the data from CM12 is still on the data partition. So after flashing the stock rom, reboot into recovery mode (it looks a bit different now). First wipe the data partition, then wipe the cache.
Reboot
Changelog
Code:
15/08/2015:
* Synchronize with newest CM 12.1 sources (contains stagefright patches)
08/07/2015:
* Update to latest CM-12.1 sources (LMY48G)
* Camera app supports saving pictures to external SD-cards
* Partition sizes of system and data slightly reduced to avoid "unable to mount /system" failure during installation on some variants of the G800 (e.g. G800Y)
19/05/2015:
* Update to CyanogenMod 12.1 (Android 5.1.1)
* Merged Kernel-sources from G800FXXU1ANL1
* Re-enabled NFC
* TWRP update
11/04/2015:
* Update to CyanogenMod 12.1 (Android 5.1)
* Update to TWRP 2.8.6.0
* Fixed blinking capacitive touchkey lights
* Fixed unresponsive touchscreen on wake-up
* Added support for Automatic Brightness control
* Added advanced touchscreen settings (Glove and Hovering mode)
* Use open-source Light-HAL, Power-HAL and IR-HAL implementations
* Updated Power-Profiling
23/03/2015:
* Fixed non-working mic on incoming call issue
* Fixed non-working menu-button
* Synchronized with latest CyanogenMod sources
This section is for developers:
A README file with build instructions can be found here:
Code:
https://github.com/cm-3470/patcher_kminilte
Sources:
Code:
https://github.com/cm-3470/android_device_samsung_kminilte
https://github.com/cm-3470/android_vendor_samsung_kminilte
https://github.com/cm-3470/android_kernel_samsung_kminilte
https://github.com/cm-3470/android_device_samsung_smdk3470-common
Developers welcome
At the moment the G800F/M/Y specific port of this ROM is only done by one person (hennymcc). Although Unjustified Dev also works on this ROM he does not own an Galaxy S5 Mini but a Galaxy Light which has a similar base but is different when it comes to camera, nfc and other components (maybe even slightly when it comes to audio and radio).
Help from other developers is always welcome. See the bug/feature section and this thread to see what is missing. Just give some short info (here in this thread or PM) that you want to work on some issue or feature so that work can be synchronized. Maybe there are also other devs that want to work with you on the same issue.
Knowledge in how the kernel works and good programming skills in C, C++ and Java would be nice but not necessary for all problems. At least you should be able to build the ROM and test your changes yourself but you do not need experience in porting ROMs.
Thanks to Unjustified Dev from Team Regular. As the S5 mini (G800F/M/Y) and the Galaxy Light are quite similar we worked on this together.
XDA:DevDB Information
[G800F/M/Y][ROM][5.1.1][LMY48G] CyanogenMod 12.1 for G800F/M/Y [Alpha 15/08/2015], ROM for the Samsung Galaxy S5 Mini
Contributors
hennymcc, Unjustified Dev
Source Code: https://github.com/cm-3470
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP Recovery [version from 15/08/2015]
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2015-04-15
Last Updated 2015-09-22
FAQ:
Question:
I'm trying to flash this rom but it says to me: "This package is for kmniltexx, kminiltedv, kminilteub; this device is kminilte. E:Error executing updater binary zip ...."
Answer:
The device names were changed with the newest CM12 build to be able to distinguish between G800F (kmniltexx), G800Y (kminiltedv) and G800M (kminilteub) as all of them are kminilte devices. The new builds of TWRP and CM12 detect the correct device at runtime.
Older TWRP releases (for example that of RVR in another XDA thread) still detect the device as kminilte (instead of kmniltexx,...) and hence are not able to install the new CM 12 releases so please do not install RVR's TWRP if you want to install CM 12. Always use the TWRP image linked in the first post of this thread.
Reserved
As none of the pre-alpha testers reported any issues with NFC, I assume that the broken NFC of LS97 and me was caused by electrostatic discharge while removing and re-inserting the battery (at least I did this hundreds of times). In addition we already broke our NFC some weeks ago after having used 5.0.2 for some while, so this ROM should be at least as safe as 5.0.2 and there is no direct link between the custom ROM and the broken NFC.
Just as a precaution: to avoid damage of the NFC-chip (which is connected to the antenna in the battery) by electrostatic discharge, use the power button to reboot the smartphone instead of removing the battery.
What a nice first post for this new ROM
Are the links above the same like the ones you posted into the comments in your 5.0.2 thread? Just so i know if something has changed in thos links obove.
CTXz said:
Are the links above the same like the ones you posted into the comments in your 5.0.2 thread? Just so i know if something has changed in thos links obove.
Click to expand...
Click to collapse
Exactly the same.
hennymcc said:
Exactly the same.
Click to expand...
Click to collapse
Ok thanks. Also have you figured out whats up with the screen turning on after locking delay since turning off nfc didn't result changes. Also it doesn't happen always. Only sometimes
CTXz said:
Ok thanks. Also have you figured out whats up with the screen turning on after locking delay since turning off nfc didn't result changes. Also it doesn't happen always. Only sometimes
Click to expand...
Click to collapse
I haven't looked any deeper into this so far.
So how is the Final version going to look like if this is Alpha... Damn [emoji41]
I have a small problem, everytime i touch the screen my capacitive buttons light up. I already tried disabling this in the settings but it doesn't let me do that.
Anyone have soms advice ?
Nielsieboy said:
I have a small problem, everytime i touch the screen my capacitive buttons light up. I already tried disabling this in the settings but it doesn't let me do that.
Anyone have soms advice ?
Click to expand...
Click to collapse
Hey. What i did is just rather turn them off completely.
Settings > Buttons > Backlight > Uncheck Illuminate buttons
Else there is no fix, due cm12.1 universality it doesn't work with the buttons like the stock ROM did.
CTXz said:
Hey. What i did is just rather turn them off completely.
Settings > Buttons > Backlight > Uncheck Illuminate buttons
Else there is no fix, due cm12.1 universality it doesn't work with the buttons like the stock ROM did.
Click to expand...
Click to collapse
Well tried that but The setting just changes back to the default.
Nielsieboy said:
Well tried that but The setting just changes back to the default.
Click to expand...
Click to collapse
Ok thats wierd. Have you wiped all partitions you needed to like said above ( dalvik cache, cache, system, data )
If it gets verry anoying you might give a reflash a try. Also i know this sounds funny but did you atleast try rebooting the device?
---------- Post added at 08:55 PM ---------- Previous post was at 08:50 PM ----------
Also did you give this a shot https://play.google.com/store/apps/details?id=com.deskangel.kblight
There are many more apps on gplay for button backlight. Just search it
i've flashed it yesterday over the old buidl (without full wipe). so i got FC's on several google apps.
after flashing several different gapps for lolipop 5.1 the errors with the FCs are still stere.
then i've made a full clean install with full wipe and installed the pa gapps from the 04-10-2015 and now everything works fine & smooth.
tommorrow ill gonna test the bluetooth cause on the old build there were sond errors....
but for now it looks very good
I've discovered something. If you enable LiveDisplay the device will lag a bit.
And when you think I did a full wipe and reflashed the ROM, just to find out that my problem was related to this little feature...
@henny: can you confirm that this mod will work on your build ?
It sounds very good
Nielsieboy said:
I have a small problem, everytime i touch the screen my capacitive buttons light up. I already tried disabling this in the settings but it doesn't let me do that.
Anyone have soms advice ?
Click to expand...
Click to collapse
it doesnt let you do that? why not? for me it worked...(i hate those lights too)
DerMoeJoe said:
@henny: can you confirm that this mod will work on your build ?
It sounds very good
Click to expand...
Click to collapse
I personally don't see a lot of advantages in it and would not recommend it, especially for this phone, regardless of whether or not it's compatible.
LS97 said:
I personally don't see a lot of advantages in it and would not recommend it, especially for this phone, regardless of whether or not it's compatible.
Click to expand...
Click to collapse
Why not. I use it for daily use and i have to say i have less bugs than my stock rom had.
With that it boosted my phone like hell and there is no more lagg when oppening apps, going to the homescreen, scrolling through apps and no more touchwiz. Plus you got the newest android up to date. That fixed some app issues with my phone ( i no longer got the app not compatible error after lolipop. Oh yeah and no more bubble sounds when pressing on something Thaankk you! There are many other things that i preffer over the stock rom. So i see so much potential in this ROM and would preffer it as much as i can if you got a s5 mini g800f.
CTXz said:
Why not. I use it for daily use and i have to say i have less bugs than my stock rom had.
With that it boosted my phone like hell and there is no more lagg when oppening apps, going to the homescreen, scrolling through apps and no more touchwiz. Plus you got the newest android up to date. That fixed some app issues with my phone ( i no longer got the app not compatible error after lolipop. Oh yeah and no more bubble sounds when pressing on something Thaankk you! There are many other things that i preffer over the stock rom. So i see so much potential in this ROM and would preffer it as much as i can if you got a s5 mini g800f.
Click to expand...
Click to collapse
The only way to find out if it works is to try it. So if you want this feature you can flash that mod and report if it works .
I personally do not need it as I want the phone to turn off when I "power it off".
Note that the mod could cause stability issues. So before reporting bugs here you should reinstall CM 12.1 first with a full wipe and check if the problem is still present.
Edit:
this was supposed to be an answer to DerMoeJoe's question about the QuickBoot mod

[G4][UNOFFICIAL][ALPHA] EFIdroid for the LG G4

EFIDroid
A UEFI based Android bootloader.
EFIDroid provides an easy Installer, good looking Material Design user interfaces and uses very dynamic code.
Homepage: efidroid.org
Take over control before loading the Operating system.
EFIDroid attempts to make it easy for both users and developers to control their boot experience.
Multiboot
Install and boot any number of operating systems and recovery tools.
Boot plugins
Change the boot behavior without modifying ROM's. Swapping internal/external memory, overclocking or modifying the ramdisk. Live and without any permanent modifications.
UEFI Apps
EFIDroid uses UEFI in the background which means that you can boot other bootloaders like GRUB or rEFInd and even small games
Download
see Installation section
Requirements
The main OS (that one you currently use) must be rooted to use the efidroid app.
You may be able to install magisk later in a secondary ROM (never tried it though)
Hint:
lineageos root add-on works (tested on LOS 15.1) and magisk will NOT work. Use supersu.
TWRP / FlashFire installable ZIP:
Stable: supersu-stable
Beta: supersu-beta
Latest: supersu
At the moment the only TWRP which is working for efidroid is: twrp-3.1.1 - any newer TWRP release will fail with a ramdisk size error which is not due to a missing kernel patch. It's a known issue for efidroid and one of the reasons for the efidroid rewrite
I maybe find a workaround to get newer TWRP versions installed.. we will see..
So if you have a newer version of TWRP installed currently: upgrade/downgrade to that version first.
Installation
A full howto with screenshots can be found here
Unlock your device! This will NOT work with a locked bootloader (you know about UsU?)
Download the EFIDroid Manager from Google Play Store - Has been removed..
Efidroid manager download: main efidroid thread
Download the latest version by opening the "Downloads" tab of this thread (requires to open this thread in a browser)
Activate my efidroid OTA server:
Option 1 (permanent): modify /system/build.prop
Boot to TWRP
Make a backup (including system partition)!
Mount System partition in TWRP
enable the efidroid OTA server:
Code:
adb shell
echo "efidroid.server_url=https://raw.githubusercontent.com/steadfasterX/efidroid_ota_lgg4/master" >> /system/build.prop
reboot
verify that the efidroid server URL has been set properly:
Code:
adb shell getprop efidroid.server_url
Option 2 (will be lost on reboot): using setprop
Set the efidroid OTA server:
Code:
adb shell
setprop efidroid.server_url https://raw.githubusercontent.com/steadfasterX/efidroid_ota_lgg4/master
verify that the efidroid server URL has been set properly:
Code:
adb shell getprop efidroid.server_url
Open EFIDroid Manager
HINT: If you see an error like "cannot load device info, please check your connection : no value for lge/H815" then the above OTA url has not been set or is set wrong.
Go to Install/Update
Click Install --> HINT: THIS WILL MOVE YOUR BOOT AND RECOVERY PARTITION CONTENT
This means
1. from now on EFIDroid will boot each time u power on the device.
2. the recovery partition gets backed up and you will see it in EFIDroid again as (if TWRP): TWRP (internal).
3. you can still boot your main ROM by just choosing it from the list --> your ROM name - (internal)
If you don't like this you can install EFIDroid to either: recovery or boot partition only. But this is a manual process and when you upgrade with EFIDroid Manager it may overwrite your changes.
Install a custom ROM
A full howto with screenshots can be found here
Open EFIDroid Manager
Open the menu "Operating Systems" and click the FAB (Floating Action Button) at the bottom
Choose in the screen /data/media/0/multiboot as location.
Enter a name for the ROM
Optional: Choose another icon for the ROM
You can leave the partitions as they are (Schema LoopSystem + BindOther) Press the tab "PARTITIONS" and choose "LoopAll". You will see that the data partition is quite big (the g4 internal storage is just 23 GB so you choose a smaller size for each ROM to fit all your ROM slots).
Tip "data" and select GB in the drop down. Choose a proper size (i.e. 2 GB) depending on what you wanna do with that ROM and how many you wanna install (each ROM will take 4 GB for system + the data size you choose here)
In the tab "REPLACEMENTS" click the floating plus button and add a new cmdline override:
Code:
Name = androidboot.selinux
Value = permissive
press the tick in the top right corner to finish the setup
Now you can see your newly created ROM slot in the list
Reboot
Once you are in the efidroid, you can navigate around with volume down to go down, volume up to go up and the power button to confirm your selection.
To flash a ROM to the new empty slot, select TWRP (Internal) , press power and select the slot name with power again
At the moment the system partition is just empty and needs to be formatted before you can use it!
In TWRP:
select WIPE -> Advanced Wipe -> select "system" and "cache", then swipe to wipe.
select WIPE -> "Format Data" button
Reboot -> System. When you see efidroid again choose TWRP and select the new ROM slot again to boot TWRP again.
Install your ROM of your choice.
Hint: If you get an error regarding device detection you have to remove the assert line(s) within the ROM zip first
Supported devices
Any LG G4 model which can be unlocked (yea even UsU ones but that still requires some more work to detect them properly)
Known Issues
The Operating System list in the EFIDroid Manager is empty just upgrade to the latest EFIDroid manager app..
after installing a ROM it may bootloop under some circumstances
AROMA installer flickers extremely. Workaround: press power to turn off screen then turn it on again. It still flickers but u can see and use the installer at least.
As we need to use TWRP 3.1.1 (see requirements) UsU devices get not detected correctly!
The state of this project is ALPHA so expect issues and even data loss is possible (so do a TWRP backup often)
Booting a secondary ROM and working in a secondary ROM may feel slower (that's by design)
if a ROM has set selinux to enforcing it will not boot! --> If you setup the ROM slot properly (see above REPLACEMENTS tab) you do not need to care about.
Without that adjustment in the efidroid manager you have to modify the boot.img of every ROM:
change the cmdline from
androidboot.selinux=enforcing
to
androidboot.selinux=permissive
I started a while ago to make selinux policies for efidroid but it's not that easy and so atm no ROM which has selinux set to enforcing will boot.
Credits
@m11kkaa for EFIDroid
@J0SH1X for bringing a first port for the G4
@steadfasterX for being steadfast and optimizing efidroid
XDA:DevDB Information
EFIDroid for the LG G4, Tool/Utility for the LG G4
Contributors
steadfasterX, @m11kkaa, @J0SH1X
Source Code: https://github.com/steadfasterX/efidroid_device_lge_g4
Version Information
Status: Alpha
Created 2017-04-14
Last Updated 2018-12-17
Workarounds for known issues
1) random app crashes, settings do not persist on reboot
The reason is that file permissions get not set correctly on the bind mounted data partition.
So nothing can be stored there (or what get stored will be stored with the wrong perms).
When creating a new ROM slot it is important (atm) that you choose LoopAll .
This would create a data partition image with 23 GB which is way too much so you need to touch the data partition in the partitions tab and set the size to GB and choose e.g. 2 GB.
2) no WiFi
First boot TWRP internal / primary slot
Code:
adb shell cp /data/misc/wifi/config /external_sd/data_misc_wifi_config
Then for each slot you created you must reboot TWRP in its slot and:
Code:
adb shell cp /external_sd/data_misc_wifi_config /data/misc/wifi/config
adb shell chown system.wifi /data/misc/wifi/config
adb shell chattr +i /data/misc/wifi/config
Reserved
I tried to install Efidroid on my LG G4 (H815, bootloader unlocked, ResurrectionRemix 5.8.2). I install the App and modify the build.prop with the efidroid url, but every time i start the app i get the error-massage:
Error. Can't load device info. Please check your connection. No value for lge/h815.
Could you help me fixing this?
jokuu said:
I tried to install Efidroid on my LG G4 (H815, bootloader unlocked, ResurrectionRemix 5.8.2). I install the App and modify the build.prop with the efidroid url, but every time i start the app i get the error-massage:
Error. Can't load device info. Please check your connection. No value for lge/h815.
Could you help me fixing this?
Click to expand...
Click to collapse
Oh damn. I forgot to update the OTA for the other devices..
There is nothing you can do on your site atm.. Sorry I will fix it asap and let you know..
.
Sent from my LG-H815 using XDA Labs
still hard at it heck yea
jokuu said:
I tried to install Efidroid on my LG G4 (H815, bootloader unlocked, ResurrectionRemix 5.8.2). I install the App and modify the build.prop with the efidroid url, but every time i start the app i get the error-massage:
Error. Can't load device info. Please check your connection. No value for lge/h815.
Could you help me fixing this?
Click to expand...
Click to collapse
ok done. please try again
.
steadfasterX said:
ok done. please try again
.
Click to expand...
Click to collapse
Now it works. Thank you! :good:
ok .. im able to boot a LL based ROM now (Imperium ROM).. but only ONCE. lol..
Well I can boot into it again after booting in the TWRP version of that ROM and doing a factory reset from within TWRP...
Cleaning /data, /cache and dalvik cache manually does NOT work.. interesting. <-- I tested with a special (FIsH) TWRP version which does not WIPE but RM only.. Once I switched to a regular TWRP it is still strange but at least behaves the same now: When I wipe /data and /cache I can boot (but only when wiping both).
Update:
Keeping strange:
When I wipe /data only -> no boot
When I wipe /cache only -> no boot
When I wipe both -> boot ok .. wtf.?!
I will look into /misc - maybe the reason can be found here!
.
I just booted a second rom successfully using efi on my h811
My primary rom: lineage nougat
My secondary rom: resurrection remix (mm)
First boot was slow, second a little less slow, third and so on boot at normal speed.
Anyone else with an h811 care to try it coz @steadfasterX thinks mine booted coz i have an h811.
So if anyone else with an h811 can test it, that would help.
Btw, you all jelly? :victory:
Update: i have a complex sort of bootloop.
I decided to flash gapps.
Now when i try to boot the rom, i get the optimizing apps screen, then starting apps, then the boot logo, then again starting apps, and again boot logo and it goes on like that.
If i clear cache and dalvik i get the optimizing apps again, then the circle continues.
Maybe its gapps?
Or maybe its coz you all were too much jelly
tanveer7652 said:
Update: i have a complex sort of bootloop.
I decided to flash gapps.
Now when i try to boot the rom, i get the optimizing apps screen, then starting apps, then the boot logo, then again starting apps, and again boot logo and it goes on like that.
If i clear cache and dalvik i get the optimizing apps again, then the circle continues.
Maybe its gapps?
Or maybe its coz you all were too much jelly
Click to expand...
Click to collapse
heat
kevp75 said:
heat
Click to expand...
Click to collapse
Heat? What do you mean
tanveer7652 said:
Heat? What do you mean
Click to expand...
Click to collapse
I believe he thinks you have the ilapo because he don't know what efidroid is.
have you tried to wipe /data as mentioned (on IRC) ?
.
tanveer7652 said:
Heat? What do you mean
Click to expand...
Click to collapse
steadfasterX said:
I believe he thinks you have the ilapo because he don't know what efidroid is.
have you tried to wipe /data as mentioned (on IRC) ?
.
Click to expand...
Click to collapse
LOL I have a good idea with efidroid is
Everytime you wipe cache/dalvik your device has to rebuild the dalvik.
When your device rebuilds dalvik it has to work.. and work hard... as a result of the device working harder than normal, it generates heat. if it gets too hot, it will reboot.
I sometimes get it on a plain ol' stock rom
@steadfasterX im back to work on it just bought a new g4 today and currently im in unlock progress
J0SH1X said:
@steadfasterX im back to work on it just bought a new g4 today and currently im in unlock progress
Click to expand...
Click to collapse
Congrats. Please remember some of us poor guys when u buy another g4 ?
---------- Post added at 03:31 PM ---------- Previous post was at 03:30 PM ----------
kevp75 said:
LOL I have a good idea with efidroid is
Everytime you wipe cache/dalvik your device has to rebuild the dalvik.
When your device rebuilds dalvik it has to work.. and work hard... as a result of the device working harder than normal, it generates heat. if it gets too hot, it will reboot.
I sometimes get it on a plain ol' stock rom
Click to expand...
Click to collapse
But it doesn't get hot.
kevp75 said:
LOL I have a good idea with efidroid is
Click to expand...
Click to collapse
oh that's good
kevp75 said:
Everytime you wipe cache/dalvik your device has to rebuild the dalvik.
When your device rebuilds dalvik it has to work.. and work hard... as a result of the device working harder than normal, it generates heat. if it gets too hot, it will reboot.
I sometimes get it on a plain ol' stock rom
Click to expand...
Click to collapse
tbh I don't think that this is the case here. We have bootloops when something changes in /data. This is not heat related. It is something efidroid related..
J0SH1X said:
@steadfasterX im back to work on it just bought a new g4 today and currently im in unlock progress
Click to expand...
Click to collapse
u like pain do u ?
steadfasterX said:
oh that's good
tbh I don't think that this is the case here. We have bootloops when something changes in /data. This is not heat related. It is something efidroid related..
Click to expand...
Click to collapse
theres software bootloop and hardware bootloop. i only get software when i install something or say remove gapps. or mess with system . flashing rom fix it..

LineageOS 16.0 (build 20190425) - Microg, sig spoofing with full SafetyNet

UPDATE 06 OCT 2019: I will be returning to the project next week...
Apologies for my long silence over the past few months. After the initial release of this ROM I started focusing on getting the fingerprint sensor to work, which after some struggle I got it working. I then began spending time on removing non-FLOSS apps, services and providers that comes with lineageOS and replacing them with even better FLOSS alternatives. I made some good progress on this and created an automated build script for this. I also wanted to make the installation of the ROM easier, so I even created a script that automates the entire flashing procedure for you....yip...it's pretty cool On the security side I also made some good progress: I've applied several recommended hardening patches to the base system, and also patched the flawed mac-address randomization implementation that still exists in android today.
As I got close to preparing for release, google decided to stop support for maps-api V1 which is used by migrog. This completely broke all map views in apps and even started crashing the mobile browser. Because of the complexity of the android build workflow and tool-chain, I initially thought I screwed something up, but it was only after a couple of days of pulling my hair out people started reporting it on github. I had to wait for the mapbox implementation of microg to be released, and it eventually came a few weeks later.
It was shortly after the release that my personal priorities changed. I've been occupied (visa related) with that ever since but I'm happy to report that I should be able to return back to the project next week. Obviously some time has passed, so I will have to get up to speed with the latest releases of all of the repos and get that merged with my local changes, but that should only take a day. Hopefully there won't be many breaking changes, and if that is the case then I should be in a position to release V2 in about two weeks!
Cheers,
fanix (git-repo here: https://github.com/FaN11X?tab=repositories). Once you see commits you'll know I've started.
New build is available apparently.... don't know if it's the same dev..
UPDATE 08 MAY 2019: I'm in the process of adding support for the in-display fingerprint sensor. Stay tuned.
This is a lineageos 16.0 build from source on 25 April using latest source. The ROM is has been prepatched for system lavel signature spoofing based on the MicroG Android Pie patch (url removed, sigh). I did however change the protection level from "Dangerous" to "Signature|Restricted". This is a more secure way of enable signature patching as it requires the app using signature spoofing to be privaliaged, in other words, it needs to be installed to /system/priv-app in order for it to be granted this permission. This means that you wont be at risk of downloading and installing apps that might abuse signature spoofing.
The ROM also passes FULL SafetyNet with microg installed. It uses a custom build from Nanadroid which contains all the latest code changes which you wont find in there official releases as its not yet been packaged as a release. This solved many issues for me, like safetyNet now passing which allows me to install and run banking applications (like Barclay's Mobile Banking) and also uber seems to work just fine using the UnifiedNLP backend providers.
This custom ROM has NO google related apps or code, and you have the ability to switch on google released integration services through the microg services menu.
WORKING
So far... everything I've tested. (except fingerprint)
NOT WORKING
On-display fingerprint.
Installation steps:
1. Restore to stock firmware. I recommend the following Fastboot ROM as thats the one I used. *url removed* (download file search google "equuleus global images V10.2.2.0.PECMIXM")
2. Put device in fastboot mode (adb reboot bootloader or Power Button + Vol Down)
3. Flash using MiFlash (Find it on google and be sure to select the "FLASH ALL.bat" option at the bottom and NOT the LOCK on, otherwise you will relock your device)
4. After flashing the stock ROM, let it boot up, then enable developer options and USB debugging.
5. Flash TWRP
* adb reboot bootloader
* fastboot erase recovery
* fastboot flash TWRP_equuleus_1102.img
* fastboot boot TWRP_equuleus_1102.img
6. Once in TWRP, goto WIPE and select DATA. Enter the word "yes" and once it is complete, go back to main menu, RESTART=>RECOVERY to reboot and automatically boot back into recovery.
7. Goto WIPE again, but this time WIPE DalvicCache, SYSTEM & Cache by selecting all 3 and wiping them (NO NOT RESTART AFTER THIS STEP
8. Once wipe is complete, push the content from the download folder provided below to the sdcard folder of the phone.
* adb push download_folder_containing_all_the_files /sdcard/
example: adb push /home/fanix/Downloads/lineageosrom /sdcard/
9. Once complete, you are now ready to flash lineage ROM. Select the lineageos zip file and flash it. (filename => lineage-16.0-20190425-UNOFFICIAL-equuleus.zip)
10. Once complete, you can then reboot to system to load lineage. After going through the lineage setup, you can then install microg (if you want)
Optional - Installing microg (from latest nanodroid) FULL SAFETYNET SUPPORTED
* Boot into TWRP (adb reboot recovery)
* Goto INSTALL, and select the following file: (NanoDroid-microG-20.7.92.20190424.zip).
* NOTE: This will install microg, including MsfProxy and UnifiedNLP with 4 backend providers. It will also install Aurora Store & Fake store.
* When install is complete, reboot and once in lineage, you can configure microg. You can log into google store using Aurora, either with your own account or their anonymised account. This allows you to download anything form the google app store, including apps that require verification, like mobile banking apps.
* If you want, you can test your SafetyNET using Magisk. You can find the magisk manager in the download folder. Install that and test SafetyNET. You do NOT need to root your phone to test this, you can simply install the manager. If you want to root your phone, simply boot back into TWRP and select the magisk 19.0 zip file and that will then also root your device.
Enjoy!
DOWNLOAD LINK:
https://drive.google.com/open?id=1aJ...bkaHPw86sgHYMj
I've contacted one of the mods and asked if thye could post the link. Hope they do, otherwise if someone has the ability to post links then message me and i'll PM you the download link which you can then share to the thread.
Cheers
fanix
Hi fanix-uk,
Thank you very much! Is 3D face recognition working or just the 2d with the front camera?
mateHD said:
Hi fanix-uk,
Thank you very much! Is 3D face recognition working or just the 2d with the front camera?
Click to expand...
Click to collapse
Not sure, I haven't tried it. To be honest I've never used that feature on this phone before.
fanix-uk said:
Not sure, I haven't tried it. To be honest I've never used that feature on this phone before.
Click to expand...
Click to collapse
I tried it. Face unlock works with google smartlock. It use IR sensor, not the front camera, but it isn't 3D. So it works without light, but less secure than the stock rom version.
Btw. the rom works perfectly. Thanks again.
Is possible to have the miui camera with this rom?
mateHD said:
I tried it. Face unlock works with google smartlock. It use IR sensor, not the front camera, but it isn't 3D. So it works without light, but less secure than the stock rom version.
Btw. the rom works perfectly. Thanks again.
Click to expand...
Click to collapse
You are most welcome! Thanks for testing it... I'm working on a new release with some really cool features, including
Updated, hardened kernel.
Wireguard kernel module built into kernel.
Removal of non-FOSS apps/providers/services and replace with FOSS alternatives
Weather provider integration with openweathermap.
In-display fingerprint
perillo95 said:
Is possible to have the miui camera with this rom?
Click to expand...
Click to collapse
I can try and grab the camera app and drivers from stock and package it for you, but won't be including proprietary software in this build. I'll keep you posted.
fanix-uk said:
You are most welcome! Thanks for testing it... I'm working on a new release with some really cool features, including
Updated, hardened kernel.
Wireguard kernel module built into kernel.
Removal of non-FOSS apps/providers/services and replace with FOSS alternatives
Weather provider integration with openweathermap.
In-display fingerprint
Click to expand...
Click to collapse
Looking forward to it. I will probably try the current version as soon as I'm allowed to unlock my bootloader.
fanix-uk said:
I can try and grab the camera app and drivers from stock and package it for you, but won't be including proprietary software in this build. I'll keep you posted.
Click to expand...
Click to collapse
With miui camera and the in-display fingerprint would be a perfect ROM, Great work
thanks a lot for LOS!
Q: do i need to install gapps after ROM?
eerastov said:
thanks a lot for LOS!
Q: do i need to install gapps after ROM?
Click to expand...
Click to collapse
Yes.
Whats up with the new version? Can i help somehow?
Thanks
Hi Fanix
I really appreciate what you have done for Mi8 Pro. If you did not share your work here, I think I nearly sell my phone, as the MIUI is pretty trash.
Also, thanks for your progress on adding in-display finger sensor, after you done it I feel you can create one link for donation. I really hope you can keep develop on this phone and make LOS Andorid Q available in the future.
Kind regards
One of Mi8 Pro users
---------- Post added at 07:51 AM ---------- Previous post was at 07:47 AM ----------
I flashed this rom on my phone, it works really well. And I flashed a Gapps on my phone, work well as well. I did not flash the Nanadroid on my phone, is it necessary? I just worry about it becasue you said something related to SafetyNet, ahaha. I do not know if I do not have it, is my phone still safe?
Thanks a lot again.
fanix-uk said:
UPDATE 08 MAY 2019: I'm in the process of adding support for the in-display fingerprint sensor. Stay tuned.
This is a lineageos 16.0 build from source on 25 April using latest source. The ROM is has been prepatched for system lavel signature spoofing based on the MicroG Android Pie patch (url removed, sigh). I did however change the protection level from "Dangerous" to "Signature|Restricted". This is a more secure way of enable signature patching as it requires the app using signature spoofing to be privaliaged, in other words, it needs to be installed to /system/priv-app in order for it to be granted this permission. This means that you wont be at risk of downloading and installing apps that might abuse signature spoofing.
The ROM also passes FULL SafetyNet with microg installed. It uses a custom build from Nanadroid which contains all the latest code changes which you wont find in there official releases as its not yet been packaged as a release. This solved many issues for me, like safetyNet now passing which allows me to install and run banking applications (like Barclay's Mobile Banking) and also uber seems to work just fine using the UnifiedNLP backend providers.
This custom ROM has NO google related apps or code, and you have the ability to switch on google released integration services through the microg services menu.
WORKING
So far... everything I've tested. (except fingerprint)
NOT WORKING
On-display fingerprint.
Installation steps:
1. Restore to stock firmware. I recommend the following Fastboot ROM as thats the one I used. *url removed* (download file search google "equuleus global images V10.2.2.0.PECMIXM")
2. Put device in fastboot mode (adb reboot bootloader or Power Button + Vol Down)
3. Flash using MiFlash (Find it on google and be sure to select the "FLASH ALL.bat" option at the bottom and NOT the LOCK on, otherwise you will relock your device)
4. After flashing the stock ROM, let it boot up, then enable developer options and USB debugging.
5. Flash TWRP
* adb reboot bootloader
* fastboot erase recovery
* fastboot flash TWRP_equuleus_1102.img
* fastboot boot TWRP_equuleus_1102.img
6. Once in TWRP, goto WIPE and select DATA. Enter the word "yes" and once it is complete, go back to main menu, RESTART=>RECOVERY to reboot and automatically boot back into recovery.
7. Goto WIPE again, but this time WIPE DalvicCache, SYSTEM & Cache by selecting all 3 and wiping them (NO NOT RESTART AFTER THIS STEP
8. Once wipe is complete, push the content from the download folder provided below to the sdcard folder of the phone.
* adb push download_folder_containing_all_the_files /sdcard/
example: adb push /home/fanix/Downloads/lineageosrom /sdcard/
9. Once complete, you are now ready to flash lineage ROM. Select the lineageos zip file and flash it. (filename => lineage-16.0-20190425-UNOFFICIAL-equuleus.zip)
10. Once complete, you can then reboot to system to load lineage. After going through the lineage setup, you can then install microg (if you want)
Optional - Installing microg (from latest nanodroid) FULL SAFETYNET SUPPORTED
* Boot into TWRP (adb reboot recovery)
* Goto INSTALL, and select the following file: (NanoDroid-microG-20.7.92.20190424.zip).
* NOTE: This will install microg, including MsfProxy and UnifiedNLP with 4 backend providers. It will also install Aurora Store & Fake store.
* When install is complete, reboot and once in lineage, you can configure microg. You can log into google store using Aurora, either with your own account or their anonymised account. This allows you to download anything form the google app store, including apps that require verification, like mobile banking apps.
* If you want, you can test your SafetyNET using Magisk. You can find the magisk manager in the download folder. Install that and test SafetyNET. You do NOT need to root your phone to test this, you can simply install the manager. If you want to root your phone, simply boot back into TWRP and select the magisk 19.0 zip file and that will then also root your device.
Enjoy!
DOWNLOAD LINK:
https://drive.google.com/open?id=1aJ...bkaHPw86sgHYMj
Click to expand...
Click to collapse
hello I have tried treble version but i got MusicFX Force Close i hope you can fix this
and maybe you can port Miui Camera on this ROM thanks for your work
I found a bug :
NFC is not found in Settings and NFC Icon on status bar is error
Edit :
sometimes when opening the camera, freeze and got pop-up cannot be connected to the camera
And for musicFX is working...
Thanks
fanix-uk said:
UPDATE 08 MAY 2019: I'm in the process of adding support for the in-display fingerprint sensor. Stay tuned.
This is a lineageos 16.0 build from source on 25 April using latest source. The ROM is has been prepatched for system lavel signature spoofing based on the MicroG Android Pie patch (url removed, sigh). I did however change the protection level from "Dangerous" to "Signature|Restricted". This is a more secure way of enable signature patching as it requires the app using signature spoofing to be privaliaged, in other words, it needs to be installed to /system/priv-app in order for it to be granted this permission. This means that you wont be at risk of downloading and installing apps that might abuse signature spoofing.
The ROM also passes FULL SafetyNet with microg installed. It uses a custom build from Nanadroid which contains all the latest code changes which you wont find in there official releases as its not yet been packaged as a release. This solved many issues for me, like safetyNet now passing which allows me to install and run banking applications (like Barclay's Mobile Banking) and also uber seems to work just fine using the UnifiedNLP backend providers.
This custom ROM has NO google related apps or code, and you have the ability to switch on google released integration services through the microg services menu.
WORKING
So far... everything I've tested. (except fingerprint)
NOT WORKING
On-display fingerprint.
Installation steps:
1. Restore to stock firmware. I recommend the following Fastboot ROM as thats the one I used. *url removed* (download file search google "equuleus global images V10.2.2.0.PECMIXM")
2. Put device in fastboot mode (adb reboot bootloader or Power Button + Vol Down)
3. Flash using MiFlash (Find it on google and be sure to select the "FLASH ALL.bat" option at the bottom and NOT the LOCK on, otherwise you will relock your device)
4. After flashing the stock ROM, let it boot up, then enable developer options and USB debugging.
5. Flash TWRP
* adb reboot bootloader
* fastboot erase recovery
* fastboot flash TWRP_equuleus_1102.img
* fastboot boot TWRP_equuleus_1102.img
6. Once in TWRP, goto WIPE and select DATA. Enter the word "yes" and once it is complete, go back to main menu, RESTART=>RECOVERY to reboot and automatically boot back into recovery.
7. Goto WIPE again, but this time WIPE DalvicCache, SYSTEM & Cache by selecting all 3 and wiping them (NO NOT RESTART AFTER THIS STEP
8. Once wipe is complete, push the content from the download folder provided below to the sdcard folder of the phone.
* adb push download_folder_containing_all_the_files /sdcard/
example: adb push /home/fanix/Downloads/lineageosrom /sdcard/
9. Once complete, you are now ready to flash lineage ROM. Select the lineageos zip file and flash it. (filename => lineage-16.0-20190425-UNOFFICIAL-equuleus.zip)
10. Once complete, you can then reboot to system to load lineage. After going through the lineage setup, you can then install microg (if you want)
Optional - Installing microg (from latest nanodroid) FULL SAFETYNET SUPPORTED
* Boot into TWRP (adb reboot recovery)
* Goto INSTALL, and select the following file: (NanoDroid-microG-20.7.92.20190424.zip).
* NOTE: This will install microg, including MsfProxy and UnifiedNLP with 4 backend providers. It will also install Aurora Store & Fake store.
* When install is complete, reboot and once in lineage, you can configure microg. You can log into google store using Aurora, either with your own account or their anonymised account. This allows you to download anything form the google app store, including apps that require verification, like mobile banking apps.
* If you want, you can test your SafetyNET using Magisk. You can find the magisk manager in the download folder. Install that and test SafetyNET. You do NOT need to root your phone to test this, you can simply install the manager. If you want to root your phone, simply boot back into TWRP and select the magisk 19.0 zip file and that will then also root your device.
Enjoy!
DOWNLOAD LINK:
https://drive.google.com/open?id=1aJ...bkaHPw86sgHYMj
Click to expand...
Click to collapse
Current anything is good !
thanks a lot again
Any news plss
Any news?
Still others are maintaining this rom, looking forward to updating
I was willing to bring up the rest of the hardware and make this device official, but I don't have the device. Is there any interest in donating a device for such purpose?
bgcngm said:
I was willing to bring up the rest of the hardware and make this device official, but I don't have the device. Is there any interest in donating a device for such purpose?
Click to expand...
Click to collapse
Would love to be in a position to do that. However, I have just had my OnePlus 6T stolen, and now need my Mi 8 Pro as a daily driver. Would be happy to donate to get the fingerprint reader working on AOSP / GSI-Treble ROMs for the MI 8 Pro.

[Guide] Install Ubuntu Touch on the G7 Power

WARNING: English isn't my primary language. Sorry for any misunderstanding.
So I've heard of people that wanted to try Ubuntu on their phones(one of them being me). However as of now there isn't a helpful guide for installing it. I'm fixing that.
What works:
-Screen(has some harmless graphical glitches though)
- Mobile data
- Wifi
- Calls
- Camera
- SD card
- You tell me
What doesn't work:
- Messages
- VoLTE
- Wifi Calling
- You tell me
Prerequisites:
- An Android 9.0 Custom ROM that doesn't use the stock /vendor(this one worked great for me, but if you are free to use another one)
- Halium kernel(I'll attach a TWRP script below). You can also try this build by erfanoabdi, however I haven't tested how it works.
- halium-ramdisk
- apparmor-enabler
- GSI Ubports script
- TWRP/OpenFox
1. Wipe data and internal storage(if you're on stock, do it on the Settings app. Otherwise, just do it however you want to as long as it disables the encryption). You shouldn't actually need to do this, since Ubuntu Touch resides only in system partition.
2. Install whatever custom ROM you chose. You don't need to boot it, just reboot to bootloader once you finish installing it. If you do boot into it though you'll need to repeat Step 1.
3. Wipe System(you shouldn't need to but it never hurts )
4. Flash the Halium kernel along with halium-ramdisk.zip and apparmor_enabler.zip.
5. Flash the GSI script.
6. Reboot.
Hopefully you'll boot into Ubuntu after that.
Kernel source used for the kernel in the .zip below
Thanks to:
- Erfanoabdi from Github(idk if he has an XDA account). He's the one that did all the heavy lifting for me.
- The guys at the Halium Telegram.
ultracoolguy said:
WARNING: English isn't my primary language. Sorry for any misunderstanding.
So I've heard of people that wanted to try Ubuntu on their phones(one of them being me). However as of now there isn't a helpful guide for installing it. I'm fixing that.
What works:
- Mobile data
- Wifi
- Calls
- Camera
- SD card
- You tell me
What doesn't work:
- Messages
- VoLTE
- Wifi Calling
- You tell me
Prerequisites:
- An Android 9.0 Custom ROM that doesn't use the stock /vendor(this one worked great for me, but if you are free to use another one)
- Halium kernel(I'll attach a TWRP script below). You can also try this build by erfanoabdi, however I haven't tested how it works.
- halium-ramdisk
- apparmor-enabler
- GSI Ubports script
- TWRP/OpenFox
1. Wipe data and internal storage(if you're on stock, do it on the Settings app. Otherwise, just do it however you want to as long as it disables the encryption).
2. Install whatever custom ROM you chose. You don't need to boot it, just reboot to bootloader once you finish installing it. If you do boot into it though you'll need to repeat Step 1.
3. Wipe System(you shouldn't need to but it never hurts )
4. Flash the Halium kernel along with halium-ramdisk.zip and apparmor_enabler.zip.
5. Flash the GSI script.
6. Reboot.
Hopefully you'll boot into Ubuntu after that.
Kernel source used for the kernel in the .zip below
Thanks to:
- Erfanoabdi from Github(idk if he has an XDA account). He's the one that did all the heavy lifting for me.
- The guys at the Halium Telegram.
Click to expand...
Click to collapse
Thanks a lot for this, installed on my Ocean and it boots, but asks for password. Whats the password.
thanks
Update: password is phablet
Base: Lineage OS by dark98
1, Swipe from right to left (edge drag right to left) to task manager very temperamental
2, removing lockscreen crashes
3, Swipe off (closing opened apps) temperamental) requires holding on the app for like 3 seconds before dragging off to close.
essojay said:
Thanks a lot for this, installed on my Ocean and it boots, but asks for password. Whats the password.
thanks
Update: password is phablet
Base: Lineage OS by dark98
1, Swipe from right to left (edge drag right to left) to task manager very temperamental
2, removing lockscreen crashes
3, Swipe off (closing opened apps) temperamental) requires holding on the app for like 3 seconds before dragging off to close.
Click to expand...
Click to collapse
I can actually confirm all of these. Sadly I can't do much about them. It probably has to do with the GSI implementation itself.
ultracoolguy said:
I can actually confirm all of these. Sadly I can't do much about them. It probably has to do with the GSI implementation itself.
Click to expand...
Click to collapse
thanks for your work once more, Erfan confirm that much it has to do with GSI. Much respect to you guys.. Its a matter of time before this is sorted, thanks once more.
bR
Is there any workaround to get messages to work?
twfs said:
Is there any workaround to get messages to work?
Click to expand...
Click to collapse
Sorry for responding so late. I haven't used Ubuntu Touch in a while so I don't know of any. However, maybe messages work now idk.
none of the links are downloadable from
Hi! I've been trying to install it on my device for 4~5 days. Downloaded everything from https://mirrors.lolinet.com/ and it simply doesn't boot (stuck on unlock warning screen).
Is there any way you can help me?

Categories

Resources