Database Users

H420/H422 ROMs/Kernels/Recoveries and flash guide

When compiling ROMs it is advised to use H324 source because it's not so broken and is universal for single/dual sim.
Kernel in development(fixes, etc.) by vitek999 @ 4PDA
https://github.com/vitek999/LGE_H324_Kernel_3.10.54
ROMs for now:
Lollipop (all roms don't have a working hotspot, maybe something minor):
djperya @4pda
AOSP
Exception OS
lol_max_lik @4pda
RessurectionRemix
Dr.Leo6565 @4pda
BlissPop 4.0.3
AICPv10
CM12.1, needs patch, quite buggy
Marshmallow UI
Platinum L
Remix UI
Custom Mod H422
DoogeeOS
VibeUI
ZenUI
Sony Z4 Mod
LivUI
X-Pop
NovaUI
Sensetion OS
Xplay OS
DJUMANJI 4.0
ColorOS
Igronafr229 @4pda
GreatAOSP ROM
CleanPOP 7.0.2
Sense7
ROM galaxy note 5
LP Prime
AisakaYui @4pda
Stock, TWRP flashable
Marshmallow (extremely buggy, headphones don't work at high volumes, cameras barely work):
Dr.Leo6565 @4pda
CrDroid
AICPV11
Igronafr229 @ 4pda
CM13
Kernels for now:
OptiSmartKernel
How to flash?
Best method is MTK FlashTool(download)
Grab uboot (This is for devices that have android 5.0 on them, should work for all models, tested on my H420 and works)
Grab TWRP 3.0
1. Unzip Flashtool.
2. Get recovery.img and uboot.img from recovery and uboot zips.
3. Open flash-tool.exe
4. Select scatter file. which is in the same folder as flash-tool.exe
{
"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"
}
5. Select your uboot and recovery.img click on the highlighted, it will open the file picker.
6. Turn off your phone, plug in usb cable in the computer.
7. Click the download button in flashtool, plug the usb cable.
8. Wait for it to say ok.
DONE!
To enter recovery:
1. Turn phone off.
2. Hold power and volume down
3. When screen turns on, let go of the buttons and quickly hold them again.
4. A menu should appear about factory reset. Don't worry, it won't since the recovery is custom.
5. Select yes using volume keys, you'll need to do it two times.
6. Voila!
To root stock 6.0, download this and place files in flashtool like in the guide above, just pick the files and flash. (recovery.emmc.win = recovery; logo.emmc.win = logo etc.) afterwards you can go ahead and get a magisk zip and flash it (it needs to be modified to be able to patch our device, thanks to the people @ 4pda for being so helpful) here
CREDITS:
Vitek999 for kernel and being very helpful
djperya for flashtool and being very helpful
Everyone else for the ROMs, thanks guys!

Kicka$$ stuff.

Tomo123 said:
Kicka$$ stuff.
Click to expand...
Click to collapse
Thanks, now that I have a working kernel source I'll make my own. Also overclocking will be very easy.

excuse me for my ignorance. Will this work with h440n?

Korelev said:
excuse me for my ignorance. Will this work with h440n?
Click to expand...
Click to collapse
No, these are completely different devices.

Aosp 5.0.2 language
hello today I installed the ROM AOSP 5.0.2 on my lg H420 and noticed that not had my language ( Portuguese - Portugal ).
Already I installed an application to change my language but some aplications as the system continue in English.
someone can give me a hand?

Thyago Vergueira said:
hello today I installed the ROM AOSP 5.0.2 on my lg H420 and noticed that not had my language ( Portuguese - Portugal ).
Already I installed an application to change my language but some aplications as the system continue in English.
someone can give me a hand?
Click to expand...
Click to collapse
Which applications are these? I think that some applications can use only English language.

polfrank said:
Which applications are these? I think that some applications can use only English language.
Click to expand...
Click to collapse
System apps like "phone" "settings" "contacts" "messaging"....
please i need to fix !!!

hello
my phone when i power off and when i put the cable dont do nothing just charge the phone...
can you helpe me?i have debbuging on and i try also off

anatol55 said:
hello
my phone when i power off and when i put the cable dont do nothing just charge the phone...
can you helpe me?i have debbuging on and i try also off
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B_UKqVTCg2_xMUo2XzRzaWVaSzQ/view?usp=drive_web install this

Guys can i unlock bootloader of my lg h442

mayankjet said:
Guys can i unlock bootloader of my lg h442
Click to expand...
Click to collapse
yes just flash it as told to. There's even CM13 (android 6.0.1) just look up the 4pda thread.

so if i update h420 to marshmallow i'll still be able to flash it with this method and gain root access?

+&o_o said:
so if i update h420 to marshmallow i'll still be able to flash it with this method and gain root access?
Click to expand...
Click to collapse
forget my last question (kinda stupid). i have a problem if you guys could help me would be great. after flashing everything succesfully on the phone, wich is a spirit H420, under phone info now i get H422. it wouldn't be a problem if only i could flash the marshmallow kdz meant for the H420, but the installation process via LGUP doesn't even start. i've seen interesting stuff on 4pda, maybe i could find H420 lollipop stock there? to start from scratch before updating?
can anyone help me to revert the phone info?

+&o_o said:
forget my last question (kinda stupid). i have a problem if you guys could help me would be great. after flashing everything succesfully on the phone, wich is a spirit H420, under phone info now i get H422. it wouldn't be a problem if only i could flash the marshmallow kdz meant for the H420, but the installation process via LGUP doesn't even start. i've seen interesting stuff on 4pda, maybe i could find H420 lollipop stock there? to start from scratch before updating?
can anyone help me to revert the phone info?
Click to expand...
Click to collapse
In my case, I tried to upgrade my H420 from LP to MM via lg Mobile support tool or lg pc suite, but neither does the trick, constantly getting error. I have the MM .kdz file that is named as "H42020C_00_0530" but I tried to flash it through lg flashtool 2014, this one in vain too. What I should do to get Marshmallow? Thanks!

paulalastor said:
In my case, I tried to upgrade my H420 from LP to MM via lg Mobile support tool or lg pc suite, but neither does the trick, constantly getting error. I have the MM .kdz file that is named as "H42020C_00_0530" but I tried to flash it through lg flashtool 2014, this one in vain too. What I should do to get Marshmallow? Thanks!
Click to expand...
Click to collapse
apparently marshmallow can't be flashed using flashtool 2014, in 4pda there's a link to this video. the video is in russian, but to put it simply: go to lg site of your country, go to support, find your device, download drivers and "LG support tool" wich is a new version of the 2014 flash tool, install both of them, insert the phone turned on because the software needs to recognise the model of the phone. it will find the upgrade, "the phone may reboot, do not disconnect etc.", sadly it will go through the process of downloading the update from the internet, so no use of our kdz.
i've managed to get untill "upgrade available" step using a mobile connection, but since the firewall of my university is filtered (and beside the weight of the file, my phone would reboot, so no tethering) i can't update now. as soon as i get to a private connection i'll try. let me know if you succeed.

+&o_o said:
apparently marshmallow can't be flashed using flashtool 2014, in 4pda there's a link to this video. the video is in russian, but to put it simply: go to lg site of your country, go to support, find your device, download drivers and "LG support tool" wich is a new version of the 2014 flash tool, install both of them, insert the phone turned on because the software needs to recognise the model of the phone. it will find the upgrade, "the phone may reboot, do not disconnect etc.", sadly it will go through the process of downloading the update from the internet, so no use of our kdz.
i've managed to get untill "upgrade available" step using a mobile connection, but since the firewall of my university is filtered (and beside the weight of the file, my phone would reboot, so no tethering) i can't update now. as soon as i get to a private connection i'll try. let me know if you succeed.
Click to expand...
Click to collapse
No way with lg support tool, it didn't pass over the download of the firmware, just give error. I resolved following (by google translate) this: http://4pda.ru/forum/index.php?showtopic=686154&st=2500#entry50284916, then the green colored link Прошивка android 6.0 с нуля через LG Flashtool, finally download the attachment named H422, about 1,1 Gb. But the guide assumes that you utilize a firmware with .dz extension, not .kdz...We need an extractor/converter, just get this http://forum.xda-developers.com/attachment.php?attachmentid=3136613&stc=1&d=1422375946.
Then, if you have, like me, downloaded the v20c MM stock firmware from a site like this: http://lg-phone-firmware.com/index.php?id_mod=190, just extract the two files needed to flash our H420: "LGUPc.dll" and "H42020c00.dz". I hope I've explained myself well or almost....:silly:
If needed, just ask. I'm pretty happy with my solution.:victory:
---------- Post added at 08:22 PM ---------- Previous post was at 08:19 PM ----------
I'm just searching/waiting now for root process...

paulalastor said:
No way with lg support tool, it didn't pass over the download of the firmware, just give error. I resolved following (by google translate) this: http://4pda.ru/forum/index.php?showtopic=686154&st=2500#entry50284916, then the green colored link Прошивка android 6.0 с нуля через LG Flashtool, finally download the attachment named H422, about 1,1 Gb. But the guide assumes that you utilize a firmware with .dz extension, not .kdz...We need an extractor/converter, just get this http://forum.xda-developers.com/attachment.php?attachmentid=3136613&stc=1&d=1422375946.
Then, if you have, like me, downloaded the v20c MM stock firmware from a site like this: http://lg-phone-firmware.com/index.php?id_mod=190, just extract the two files needed to flash our H420: "LGUPc.dll" and "H42020c00.dz". I hope I've explained myself well or almost....:silly:
If needed, just ask. I'm pretty happy with my solution.:victory:
---------- Post added at 08:22 PM ---------- Previous post was at 08:19 PM ----------
I'm just searching/waiting now for root process...
Click to expand...
Click to collapse
DONE! thanks mate! owe you one
a clarification to anyone who might come here: the 2013 version of lg flash tool, wich is required for this guide is contained in the H422.rar of the russian guide. it took me a couple of minutes to understand. also i didn't understand the part of the green link, but i managed to update anyway, so i think your advice is pretty clear.
i'm not sure if this kind of update was needed for my device (didn't try upgrade tool), but since it was succesfull for you, i already posses the .kdz and i'm on a limited connection, i decided to give it a try...and SUCCESS!
already like marshmallow, hope memory leak doesn't affect our devices, and can't wait for root!

Some ROM`s
crDroid Android (6.0.1) - ttp://4pda.ru/forum/index.php?showtopic=686154&view=findpost&p=50064727
CyanogenMod 12.1 (5.1.1) - ttp://4pda.ru/forum/index.php?showtopic=686154&view=findpost&p=50327122
CyanogenMod 13 (6.0.1) - ttp://4pda.ru/forum/index.php?showtopic=686154&view=findpost&p=49486910
Blisspop (5.1.1) - ttp://4pda.ru/forum/index.php?showtopic=686154&view=findpost&p=50521514
AICP v10 (5.1.1) - ttp://4pda.ru/forum/index.php?showtopic=686154&view=findpost&p=50521514
Ressurection Remix (5.1.1) - ttp://4pda.ru/forum/index.php?s=&showtopic=686154&view=findpost&p=50521997

marshmallow root
quick update for you guys. it appears that on 4pda someone has managed to get permanent root.
here's the http://4pda.ru/forum/index.php?showtopic=686154&st=3180#entry50879512 link

P10 Firmware on the Mate 9, Android O, and other recent experiments

Over the past month, although I haven't been able to post to XDA, I've gotten a lot of interesting information which I think can be discussed here. I'd also like to report the results of some experiments.
1. Flashing P10 firmware to the Mate 9
Surprisingly, it is possible to flash P10 firmware to the Mate 9, and it boots. A Mate 9 can even be rebranded as a P10. Unfortunately, there is something different about the Wifi driver, and Wifi does not work. It seems the mobile radios, bluetooth, etc. do work, though. I wasn't able to test this very thoroughly, and I don't recommend anyone else does, as it's impossible to recover it even with offline firmware, but it would be possible in the future for someone to build a ROM based on P10 firmware, I'm pretty sure.
2. Android O
Huawei has an internal Android O build for the Mate 9. This build comes pre-rooted for Huawei's internal development use, which opens up the option of rebranding without ever unlocking the bootloader, and doing other such tricks. Apart from looking at it and seeing the Android O features, the build is pretty useless as a daily driver. Things like the play store can't be installed easily. The recovery which comes with the build has broken Wifi, and I needed to use a HiSuite exploit to get it to restore to previous versions.
With both of the above mentioned firmwares, the recovery system is different. The TWRP which we currently have for the Mate 9 does not work. Rebuilding the recovery image with the tools available also does not work. Something's different about the way the recovery image is made, but I can't figure out what it is. So it's not possible to have TWRP yet in either of these environments, which makes them much less useful.
Even more interestingly, the P10 recovery images which do not work when flashed to a Mate 9 running EMUI 7.0, do work if the Mate 9 is running Android O build, or if it's running the P10 roms.
It's very easy to tell which environment it's in, as the EMUI 5.0 Recovery has a light blue theme, while the Android O / P10 builds, and so on have a dark blue theme.
It should also be possible to flash Mate 9 ROMs on the P10, which would let P10 users access TWRP (but they would lose Wifi in eRecovery, making it very, very hard to revert to P10 ROM)
--What from here?--
Eventually, these updates will be released for the Mate 9, and we'll need to rebuild TWRP. A nice side effect is, if we build a working TWRP for the P10, it will also work with future Mate 9 builds. I'm hoping that the next internal EMUI 5.1/Android O build will have Wifi working in eRecovery to make it possible to do more research on this with an easier recovery method.
For the sake of research, I will upload and link to the recovery img from the Android O build. Feel free to poke around with it! Note that just flashing this to your Mate 9 running EMUI 5.0, it will not work. Hopefully TWRP based off of this can be made. I've tried and have not been successful building something which will boot, despite it being easy for EMUI 5.0-based recovery.
Link for Boot, Recovery, Recovery2 from EMUI 5.1 / Android O build for MHA-AL00:
https://drive.google.com/file/d/0B6ox6M5Lb2JYRVZSNnB1YmpNX1E/view?usp=sharing

Hey buddy, welcome back. :good:
Sent from my MHA-L29 using XDA Labs

That's good news. Let's see what our great minds can do with this.
I am glad to see you here @duraraa.
All the best,
AB

duraaraa said:
Over the past month, although I haven't been able to post to XDA, I've gotten a lot of interesting information which I think can be discussed here. I'd also like to report the results of some experiments.
1. Flashing P10 firmware to the Mate 9
Surprisingly, it is possible to flash P10 firmware to the Mate 9, and it boots. A Mate 9 can even be rebranded as a P10. Unfortunately, there is something different about the Wifi driver, and Wifi does not work. It seems the mobile radios, bluetooth, etc. do work, though. I wasn't able to test this very thoroughly, and I don't recommend anyone else does, as it's impossible to recover it even with offline firmware, but it would be possible in the future for someone to build a ROM based on P10 firmware, I'm pretty sure.
2. Android O
Huawei has an internal Android O build for the Mate 9. This build comes pre-rooted for Huawei's internal development use, which opens up the option of rebranding without ever unlocking the bootloader, and doing other such tricks. Apart from looking at it and seeing the Android O features, the build is pretty useless as a daily driver. Things like the play store can't be installed easily. The recovery which comes with the build has broken Wifi, and I needed to use a HiSuite exploit to get it to restore to previous versions.
With both of the above mentioned firmwares, the recovery system is different. The TWRP which we currently have for the Mate 9 does not work. Rebuilding the recovery image with the tools available also does not work. Something's different about the way the recovery image is made, but I can't figure out what it is. So it's not possible to have TWRP yet in either of these environments, which makes them much less useful.
Even more interestingly, the P10 recovery images which do not work when flashed to a Mate 9 running EMUI 7.0, do work if the Mate 9 is running Android O build, or if it's running the P10 roms.
It's very easy to tell which environment it's in, as the EMUI 5.0 Recovery has a light blue theme, while the Android O / P10 builds, and so on have a dark blue theme.
It should also be possible to flash Mate 9 ROMs on the P10, which would let P10 users access TWRP (but they would lose Wifi in eRecovery, making it very, very hard to revert to P10 ROM)
--What from here?--
Eventually, these updates will be released for the Mate 9, and we'll need to rebuild TWRP. A nice side effect is, if we build a working TWRP for the P10, it will also work with future Mate 9 builds. I'm hoping that the next internal EMUI 5.1/Android O build will have Wifi working in eRecovery to make it possible to do more research on this with an easier recovery method.
For the sake of research, I will upload and link to the recovery img from the Android O build. Feel free to poke around with it! Note that just flashing this to your Mate 9 running EMUI 5.0, it will not work. Hopefully TWRP based off of this can be made. I've tried and have not been successful building something which will boot, despite it being easy for EMUI 5.0-based recovery.
Link for Boot, Recovery, Recovery2 from EMUI 5.1 / Android O build for MHA-AL00:
https://drive.google.com/file/d/0B6ox6M5Lb2JYRVZSNnB1YmpNX1E/view?usp=sharing
Click to expand...
Click to collapse
Welcome back ?

mate 9 will never come with emui 5.1 even with official Android O update.... but it will come with enhanced features and will stay on 5.0 version as it's ...

Nilezcode said:
mate 9 will never come with emui 5.1 even with official Android O update.... but it will come with enhanced features and will stay on 5.0 version as it's ...
Click to expand...
Click to collapse
Source of this information?

What new features did you notice in the Android O build?

Nilezcode said:
mate 9 will never come with emui 5.1 even with official Android O update.... but it will come with enhanced features and will stay on 5.0 version as it's ...
Click to expand...
Click to collapse
No, it'll be 5.1. It already is.
{
"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"
}

MishaalRahman said:
What new features did you notice in the Android O build?
Click to expand...
Click to collapse
The only thing I noticed was a new files app, and some new developer options. I'm pretty sure it's just targeted for Android O development, and not for bringing any new features. It's missing all languages except Chinese and English, for example, it's missing a System Update app, eRecovery doesn't work, very incomplete.
Still, interesting, and I'm not an expert with what's new with Android to the point where I know what to look for, so if there's something I should be looking for, let me know.

duraaraa said:
The only thing I noticed was a new files app, and some new developer options. I'm pretty sure it's just targeted for Android O development, and not for bringing any new features. It's missing all languages except Chinese and English, for example, it's missing a System Update app, eRecovery doesn't work, very incomplete.
Still, interesting, and I'm not an expert with what's new with Android to the point where I know what to look for, so if there's something I should be looking for, let me know.
Click to expand...
Click to collapse
Can you look for Android O specific features to see if they work, such as Picture in Picture? If you know how to use ADB, enter an ADB shell, then open up the YouTube app and start a video.
While the video is paused type:
input keyevent 171
This would be definitive proof that this is indeed Android O. We can try other stuff too.

Any built in apps from P10 that can be installed on the Mate 9? Is there an apk list?

I seemed to remember reading in reviews of the P10 that the camera hardware is the same as our Mate 9/pro, but with upgraded software. Is this something you can verify based on the firmwares you have? When can we Mate 9 users expect this upgrade?
Cheers!

Willyman said:
I seemed to remember reading in reviews of the P10 that the camera hardware is the same as our Mate 9/pro, but with upgraded software. Is this something you can verify based on the firmwares you have? When can we Mate 9 users expect this upgrade?
Cheers!
Click to expand...
Click to collapse
Sorry, can't verify one way or the other. Although I did get P10 software running on the Mate 9, I didn't get the Camera app.

glad to see you here
ive also found that TWRP breaks the phone when you try to recover some partitions (/product i think)
hopefully things can change in the future, the partitions are a pain in the rear to play with
ive also read huawei wont name emui 5.1 on the mate 9 but will have the exact same features when upgraded (and will have the same 5.0 version)

Would you be able to share more screenshots of what you found?

MishaalRahman said:
Can you look for Android O specific features to see if they work, such as Picture in Picture? If you know how to use ADB, enter an ADB shell, then open up the YouTube app and start a video.
While the video is paused type:
input keyevent 171
This would be definitive proof that this is indeed Android O. We can try other stuff too.
Click to expand...
Click to collapse
I finally got a chance to try this. It worked.

Judging by your screenshot, you also got the Play Store and Wifi working, correct?

MishaalRahman said:
Judging by your screenshot, you also got the Play Store and Wifi working, correct?
Click to expand...
Click to collapse
Wifi always worked on Android O, since it's for the Mate 9. It doesn't work when running P10, P10 Plus, or other newer EMUI 5.1 phones' builds on the Mate 9. The issue seems to be the kernel.
I sideloaded google services and managed to get play store working, yes.

Many are doubting that this is actually Android O. Can you show a screen recording of picture-in-picture mode being started from the YouTube app?
1) Start a screen recording
2) Open up YouTube
3) Start a video
4) Send the input keyevent 171 ADB command
5) End recording
That should put any doubt to rest.

MishaalRahman said:
Many are doubting that this is actually Android O. Can you show a screen recording of picture-in-picture mode being started from the YouTube app?
1) Start a screen recording
2) Open up YouTube
3) Start a video
4) Send the input keyevent 171 ADB command
5) End recording
That should put any doubt to rest.
Click to expand...
Click to collapse
Perhaps next time I install it, I will. The picture in the previous post is the result of sending keyevent 171 ADB command while running a youtube video. The video continues to run regardless of what you do with the phone, but I couldn't find a way to close it.
Who, exactly, is doubting that it's Android O?

Xiaomi Mi Pad 2 has been EoL'd

{
"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"
}
Link:
https://xiaomi.eu/community/threads/7-9-14.41552/
Latest version for Mi Pad 2 can be downloaded from here https://www.androidfilehost.com/?w=files&flid=213123 (MIUI 9) for global* version or from MIUI http://en.miui.com/download-296.html (MIUI 8) for Chinese version.
*Mi pad 2 doesn't really have global version, .EU version comes with pre-installed google services and removed Chinese bloatware.
This is a bad news for Mi Pad 2 owners because they do not have any solid custom ROM support for their device, which is due to lack of propitiatory Intel Atom's source code. So even if developers tried hard to deliver custom ROM they simply cannot. So unlike Mi Pad 1 even if Xiaomi EoL'd the support in a similar way last week, they can still get custom ROMs and patch support as long as developers delivers them. But for Mi Pad 2 it is simply not possible.

Yes, we do. Thanks to livedten and multirom.me. I'm getting tired of redirecting people (https://multirom.me/read.php?tid=445&fid=54).
Livedten has done very well with his MIRU Mod. I suggest everyone who owns a Mi Pad 2 to flash the MIUI firmware and MIRU mod from Multirom.me
The reason why Xiaomi.eu has dropped support for Mi tablets can be found here "Sorry guys, we have no more free time to take care of tablets and debug them.. " (https://xiaomi.eu/community/threads/is-the-mi-pad-3-is-still-being-updated.41551/#post-386099).
Furthermore, if you paid attention to what @tank0412 wrote, you would know that Lenovo has a Nougat update scheduled and that opens the door for Android N development for the Atom series. Lastly, if you really want Mi Pad 2 development, I suggest you donate a Mi Pad 2 to @KonstaT over at Modaco (http://www.modaco.com/forums/forum/445-other-devices/) - he's the brain behind all Atom custom rom development.

Palm Trees said:
Yes, we do. Thanks to livedten and multirom.me. I'm getting tired of redirecting people (https://multirom.me/read.php?tid=445&fid=54).
Livedten has done very well with his MIRU Mod. I suggest everyone who owns a Mi Pad 2 to flash the MIUI firmware and MIRU mod from Multirom.me.
Click to expand...
Click to collapse
Dose it support OTA updates? Or has repo where I can download latest version of the ROM? I don't understand Russian language. Sorry.
And MIUI.com has also suspended maintaining Latte device.

udaan said:
Dose it support OTA updates? Or has repo where I can download latest version of the ROM? I don't understand Russian language. Sorry.
And MIUI.com has also suspended maintaining Latte device.
Click to expand...
Click to collapse
If you understand how to use a translator, you'll navigate just fine. Follow the instructions in the link provided.
Just like Xiaomi.eu, OTA updates aren't supported, but I never had a dirty flash gone sour from neither Xiaomi.eu or Multirom.me. That is, of course, if you follow the instructions properly. Meaning firmware version must match MIRU Mod version in order for both to work. Livedten hasn't updated MIRU Mod since 3/9-2017, so currently the two don't match. I'm sure it'll only be a matter of time before the two are aligned again and we can enjoy MIUI 9 development on Mi Pad 2.
Please provide an official link stating that MIUI 9 development has been suspended. Either way, I'm very satisfied with the performance of my Mi Pad 2 using MIRU mod. Though I am curious to see, if Lenovo releases an Android N update as scheduled and if that could potentially help spark the development of custom roms and sort some of the current issues

Palm Trees said:
If you understand how to use a translator, you'll navigate just fine. Follow the instructions in the link provided.
Just like Xiaomi.eu, OTA updates aren't supported, but I never had a dirty flash gone sour from neither Xiaomi.eu or Multirom.me. That is, of course, if you follow the instructions properly. Meaning firmware version must match MIRU Mod version in order for both to work. Livedten hasn't updated MIRU Mod since 3/9-2017, so currently the two don't match. I'm sure it'll only be a matter of time before the two are aligned again and we can enjoy MIUI 9 development on Mi Pad 2.
Please provide an official link stating that MIUI 9 development has been suspended. Either way, I'm very satisfied with the performance of my Mi Pad 2 using MIRU mod. Though I am curious to see, if Lenovo releases an Android N update as scheduled and if that could potentially help spark the development of custom roms and sort some of the current issues
Click to expand...
Click to collapse
.EU rom is far better than Chinese ROM. I haven't tried Russian roms because I cannot read it and google doesn't do justice on translation. I got to the yandex link, but there are so many stuffs in there. Like what do I install? If you look at the OP, I have linked the latest link for .EU ROM, which Is what I am using now. It surely is faster than MIUI 8. But sadly it has been EoL'd as you can see. They are not going to maintain it any longer.
And officially they have said MIUI 9 will be last MIUI update for MiPad2, somewhere. Cant find link, look it for yourself.

udaan said:
.EU rom is far better than Chinese ROM. I haven't tried Russian roms because I cannot read it and google doesn't do justice on translation. I got to the yandex link, but there are so many stuffs in there. Like what do I install? If you look at the OP, I have linked the latest link for .EU ROM, which Is what I am using now. It surely is faster than MIUI 8. But sadly it has been EoL'd as you can see. They are not going to maintain it any longer.
And officially they have said MIUI 9 will be last MIUI update for MiPad2, somewhere. Cant find link, look it for yourself.
Click to expand...
Click to collapse
I asked you for a link, because I couldn't find any information confirming Xiaomi will stop releasing more updates for Mi Pad 2. Spreading fake news is never good. Mi Pad 2 hasn't been EOL'd. Only by Xiaomi.eu, but not by others.
Livedten actually points out that it doesn't matter if you use Xiaomi.eu, Multirom.me, etc. MIRU mod should be compatible with all of them.
multirom_MIPAD2_7.9.14_v5.1_b10.zip can be found here https://multirom.me/index.php?m=app&a=view&id=11&app=roms
A MIRU Mod version that matches 7.9.14_v5.1_b10 hasn't been uploaded, so you'll have to install MIRU Mod.

Palm Trees said:
A MIRU Mod version that matches 7.9.14_v5.1_b10 hasn't been uploaded, so you'll have to install MIRU Mod.
Click to expand...
Click to collapse
Speaking of which, Livedten released the next MIRU Mod a few hours ago
https://yadi.sk/d/TMSj0qARzAWVp

Palm Trees said:
Speaking of which, Livedten released the next MIRU Mod a few hours ago
https://yadi.sk/d/TMSj0qARzAWVp
Click to expand...
Click to collapse
So do I just flash it over to MIUI9?

udaan said:
So do I just flash it over to MIUI9?
Click to expand...
Click to collapse
Make a backup first. Just in case. As can be read in the 'ИЗМЕНЕНИЯ_MIRU_universal.docx' document
"Mod (and its idea) is completely reassembled, should work on any firmware , multirom . me , xiaomi . eu , miui . su , en . miui . com ... and so on. in any case, the key operating time is on the firmware from the multirom . me ." This excerpt was translated using Google Translate.

Palm Trees said:
Make a backup first. Just in case. As can be read in the 'ИЗМЕНЕНИЯ_MIRU_universal.docx' document
"Mod (and its idea) is completely reassembled, should work on any firmware , multirom . me , xiaomi . eu , miui . su , en . miui . com ... and so on. in any case, the key operating time is on the firmware from the multirom . me ." This excerpt was translated using Google Translate.
Click to expand...
Click to collapse
btw, will they release the full ROM in future like .EU folks?

udaan said:
btw, will they release the full ROM in future like .EU folks?
Click to expand...
Click to collapse
Probably, yeah. But beware, you might have to download the firmware zip many times, if you decide to use the MIUI 9 firmware from multirom.me, always run 'test archive' with e.g. 7zip. If no errors show, you're ready to flash, if errors show, you have to re-download. I think it's because of a server issue. I use Ninja Download Manager to succesfully download the .zip. MIRU mod downloads perfectly, since it's hosted elsewhere.

After a few tests I managed to flash MIUI9 with MIRU Mod. You must flash both multirom_MIPAD2_7.9.14_v5.1_b10.zip + MIRU_mod_16.09.2017_для_MIPAD2_UNIVERSAL.zip at the same time in order to get it to work.

https://androidfilehost.com/?fid=817550096634797955

is there any working download link for the latest multirom and miru mod package?
cant find it anywhere anymore.
i found a yandex folder "MIUI_9_BACKUP" containing:
MI_mod_08.02.2018_для_MIPAD2_UNIVERSAL.zip with 144.2MB
MIRU_mod_16.09.2017_для_MIPAD2_UNIVERSAL.zip with 336.2MB
But without any instructions or anything and dont know what to do with it

So... I had the Mi pad 2 laying in my house running on MIUI 9 and one day I got curious and tried to unlock its bootloader.
I didn't remember my password and the recovery phone no. is discontinued now. and I couldn't change it or sign out.
So like an idiot, I factory reset it. And now it's asking for a password for the last mi id.
can anyone help me? Will and edl flash do the work?
THANKS

2018 A500 upgrade thread(downloads to most files required to upgrade)

A500 Upgrade Thread​
{
"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 have been collecting files for the a500 for a while now and I finally decided to release them since Tegraowners seems to officially be down. I have most of the roms from Tegraowners as well as some files to unlock the bootloader.​
ROMS​
DISCLAIMER: I did not create the cm 12 or omnirom for this device all credit goes to thor2002ro for these roms.
Katkiss 5.1.1:https://forum.xda-developers.com/iconia-a500/development/rom-katkiss-rom-t3794425
CM 12.1: http://www.mediafire.com/file/h866pllu9zvjqjn/CM12.1-Tegraowners_ROM_v7t1.rar/file
OmniRom 5.1.1: http://www.mediafire.com/file/ghd72j3g618kk9g/OMNIROM-5.1.1-Tegraowners_ROM_v13t2.zip/file
OmniRom 4.4.4: http://www.mediafire.com/file/7bw7hitf09dc3bh/OMNIROM-4.4.4-Tegraowners_ROM_v23.1t1.zip/file​
Unlocking bootloader/Recovery​
Bootloader unlock files: http://www.mediafire.com/file/o7m2ouwo6zuod4d/A500-Bootloader-Nvflash.zip/file (This is untested but I think it should work, the instructions are in the zip file)
Twrp 2.8: http://www.mediafire.com/file/e7wpny5f39vw3pc/update-recovery-TWRP-rev2.0-beta4.zip/file ​
Bootloader unlock tutorial​Step 1: Get your cpuid - https://forum.xda-developers.com/showthread.php?t=1624645
Step 2: Convert it into an SBK - https://forum.xda-developers.com/showthread.php?t=1810618
Step 3: Download the a500 drivers - http://www.mediafire.com/file/pde8rojv1t8gnif/USB_Acer_1.00.0524_A30H_A31H_A32H_A500_A501.zip/file
Step 4: Download the files to install the bootloader - http://www.mediafire.com/file/o7m2ouwo6zuod4d/A500-Bootloader-Nvflash.zip/file
Step 5: Follow the instructions in "how to.txt"
Step 6: Download a rom and flash in twrp
This tutorial is based of this thread so big thanks to KaijiKun .

Do you think you can post a tutorial on how to install custom roms for this tablet? I've been trying to figure this out ever since I got one of these and I find it way too confusing. I want to get 5.1.1 up and running.

Onehit21 said:
Do you think you can post a tutorial on how to install custom roms for this tablet? I've been trying to figure this out ever since I got one of these and I find it way too confusing. I want to get 5.1.1 up and running.
Click to expand...
Click to collapse
Sure I will add it to this post that is actually what I am working on now.

turnert said:
Sure I will add it to this post that is actually what I am working on now.
Click to expand...
Click to collapse
I just updated the thread, the tutorial is up.

I was able to successfully install some of these roms on my tablet. I was wondering what version of gapps should I download? I have a version of gapps from a different forum site that I've been using. Which version of gapps from their website would I use on the omnirom (5.1.1)?

Onehit21 said:
I was able to successfully install some of these roms on my tablet. I was wondering what version of gapps should I download? I have a version of gapps from a different forum site that I've been using. Which version of gapps from their website would I use on the omnirom (5.1.1)?
Click to expand...
Click to collapse
I just use opengapps, but don't forget to format the data partition to f2fs in recovery so that googe play works correctly

PLS. HELP !!!!
turnert said:
A500 Upgrade Thread​
I have been collecting files for the a500 for a while now and I finally decided to release them since Tegraowners seems to officially be down. I have most of the roms from Tegraowners as well as some files to unlock the bootloader.​
ROMS​
DISCLAIMER: I did not create the cm 12 or omnirom for this device all credit goes to thor2002ro for these roms.
Katkiss 5.1.1:https://forum.xda-developers.com/iconia-a500/development/rom-katkiss-rom-t3794425
CM 12.1: http://www.mediafire.com/file/h866pllu9zvjqjn/CM12.1-Tegraowners_ROM_v7t1.rar/file
OmniRom 5.1.1: http://www.mediafire.com/file/ghd72j3g618kk9g/OMNIROM-5.1.1-Tegraowners_ROM_v13t2.zip/file
OmniRom 4.4.4: http://www.mediafire.com/file/7bw7hitf09dc3bh/OMNIROM-4.4.4-Tegraowners_ROM_v23.1t1.zip/file​
Unlocking bootloader/Recovery​
Bootloader unlock files: http://www.mediafire.com/file/o7m2ouwo6zuod4d/A500-Bootloader-Nvflash.zip/file (This is untested but I think it should work, the instructions are in the zip file)
Twrp 2.8: http://www.mediafire.com/file/e7wpny5f39vw3pc/update-recovery-TWRP-rev2.0-beta4.zip/file ​
Bootloader unlock tutorial​Step 1: Get your cpuid - https://forum.xda-developers.com/showthread.php?t=1624645
Step 2: Convert it into an SBK - https://forum.xda-developers.com/showthread.php?t=1810618
Step 3: Download the a500 drivers - http://www.mediafire.com/file/pde8rojv1t8gnif/USB_Acer_1.00.0524_A30H_A31H_A32H_A500_A501.zip/file
Step 4: Download the files to install the bootloader - http://www.mediafire.com/file/o7m2ouwo6zuod4d/A500-Bootloader-Nvflash.zip/file
Step 5: Follow the instructions in "how to.txt"
Step 6: Download a rom and flash in twrp
This tutorial is based of this thread so big thanks to KaijiKun .
Click to expand...
Click to collapse
FRUSTRATED ACER A500 USER HERE. (if i cant upgrade it, i guess i have to move on and buy a new updated tab):
this is going to be my first time to do this and im taking my risk to upgrade my android version for my a500 tab. before i decide to throw this away im going to give this risk a shot. but please if someone is reading, can you help me with the SUPER DETAILED INSTRUCTION" as this is my first time.
I was able to read the post, and download the files on the link provided and tried my best to follow them. im super lost, and i am not sure if im doing them correctly. first, i tried getting my CPUID , and i only got a 11 digits, and tried to add "0" in front of the first digit, but still it wont convert it to SBK, i tried adding "0000" and it gives me a SBKcode. but im not sure if its correct coz i just added "0000" to make it 15-digit. second i open the a500 flash tool, and tried to incorporate the boot, kerner, then click next, now theres another options to upload the file like, recovery, userdata, etc.. I JUST CHECKED THE BOOTLOADER ZIP FILE AND I DONT KNOW HOW TO INCORPORATE THEM CORRECTLY TO THE APX FLAH TOOL. IM TOTALLY LOST!!!!! HELP?!
IF YOURE WILLING TO HELP ME OUT, CAN WE DO IT ON A LIVE CHAT? LIKE IN FB MESSENGER, WHATSAPP? VIBER? THANKS AND HPOING FOR A POSITIVE RESPONSE

[email protected] said:
FRUSTRATED ACER A500 USER HERE. (if i cant upgrade it, i guess i have to move on and buy a new updated tab):
this is going to be my first time to do this and im taking my risk to upgrade my android version for my a500 tab. before i decide to throw this away im going to give this risk a shot. but please if someone is reading, can you help me with the SUPER DETAILED INSTRUCTION" as this is my first time.
I was able to read the post, and download the files on the link provided and tried my best to follow them. im super lost, and i am not sure if im doing them correctly. first, i tried getting my CPUID , and i only got a 11 digits, and tried to add "0" in front of the first digit, but still it wont convert it to SBK, i tried adding "0000" and it gives me a SBKcode. but im not sure if its correct coz i just added "0000" to make it 15-digit. second i open the a500 flash tool, and tried to incorporate the boot, kerner, then click next, now theres another options to upload the file like, recovery, userdata, etc.. I JUST CHECKED THE BOOTLOADER ZIP FILE AND I DONT KNOW HOW TO INCORPORATE THEM CORRECTLY TO THE APX FLAH TOOL. IM TOTALLY LOST!!!!! HELP?!
IF YOURE WILLING TO HELP ME OUT, CAN WE DO IT ON A LIVE CHAT? LIKE IN FB MESSENGER, WHATSAPP? VIBER? THANKS AND HPOING FOR A POSITIVE RESPONSE
Click to expand...
Click to collapse
I can help but first a need a bit of info.
What version of Android is your tablet on?
Is it rooted?
What did you get as your cpuid?
And also I think you have the wrong files because this guide doesn't use a500 flash tool. In the a500-bootloader-nvflash zip just click a501.bat and follow the instructions.

Thanks for fast response
turnert said:
I can help but first a need a bit of info.
What version of Android is your Android on?
Is it rooted?
What did you get as your cpuid?
And also I think you have the wrong files because this guide doesn't use a500 flash tool. In the a500-bootloader-nvflash zip just click a501.bat and follow the instructions.
Click to expand...
Click to collapse
THANK FOR FAST RESPONSE!
----What version of Android is your Android on? - here are the info of my acer tab:
IT IS ACER A500 - ANDROID 4.0.3 kernel ver: 2.6.39.4+
build# Acer_AV041_A500_1.033.00_PA_CUS1
---Is it rooted? NOT ROOTED
---What did you get as your cpuid? i used the USBDeview and i saw "usb port acer iconia tab a500" i double click on it and it gives me a full detail of the the USB device.
Serial no.: 12612914715
Product ID: 3341
Vendor ID: 0502

[email protected] said:
THANK FOR FAST RESPONSE!
----What version of Android is your Android on? - here are the info of my acer tab:
IT IS ACER A500 - ANDROID 4.0.3 kernel ver: 2.6.39.4+
build# Acer_AV041_A500_1.033.00_PA_CUS1
---Is it rooted? NOT ROOTED
---What did you get as your cpuid? i used the USBDeview and i saw "usb port acer iconia tab a500" i double click on it and it gives me a full detail of the the USB device.
Serial no.: 12612914715
Product ID: 3341
Vendor ID: 0502
Click to expand...
Click to collapse
your probably going to have to root it use ics root in this link
http://www.mediafire.com/file/8q1190khi3i01wo/Acer+Iconia+A500+Tools+by+blackthund3r.rar
you are probably going to have to disable any antivirus programs you have

Thanks for fast response
turnert said:
your probably going to have to root it use ics root in this link
you are probably going to have to disable any antivirus programs you have
Click to expand...
Click to collapse
sorry for late reply. ive been trying to do the rooting by using the ICS root blackthundr ONLY, and press the button at the bottom with check marks of what it is going to install, but the info at the bottom says "loading file info" and nothing is happening. usb debugging is on, and tab is on while on its homepage, so what i did i just click the button part to do the process, until it says done. but when i check the tablet nothing happened. no new apps was install. can we do a live chat, like in whatsapp or viber so i can also take photos of what im doing and what is going on, so you can track down everything?

[email protected] said:
sorry for late reply. ive been trying to do the rooting by using the ICS root blackthundr ONLY, and press the button at the bottom with check marks of what it is going to install, but the info at the bottom says "loading file info" and nothing is happening. usb debugging is on, and tab is on while on its homepage, so what i did i just click the button part to do the process, until it says done. but when i check the tablet nothing happened. no new apps was install. can we do a live chat, like in whatsapp or viber so i can also take photos of what im doing and what is going on, so you can track down everything?
Click to expand...
Click to collapse
It's pretty late where I am(11:25pm as of now) but I have work off tomorrow so I could probably help you. Pm me with contact details and we can figure it out tomorrow.

turnert said:
It's pretty late where I am(11:25pm as of now) but I have work off tomorrow so I could probably help you. Pm me with contact details and we can figure it out tomorrow.
Click to expand...
Click to collapse
still there to help?

Thank you, thank you, thank you for posting these links!

Gapps for Omnirom 4.4.4
Hi, many thanks for gathering all here.
I've tried CM12, but found it unusable due to slowness.
Then I put Omnirom 4.4.4 which runs fine, but I'm having trouble with the gapps.
I tried OpenGapps ARM 4.4 pico, and my /data is formatted as f2fs, but Play is showing a black screen and play service stops all the time.
Which gapps version do you use ? I need a stable version.
Thank you
Acer A500

chrisdroid33 said:
Hi, many thanks for gathering all here.
I've tried CM12, but found it unusable due to slowness.
Then I put Omnirom 4.4.4 which runs fine, but I'm having trouble with the gapps.
I tried OpenGapps ARM 4.4 pico, and my /data is formatted as f2fs, but Play is showing a black screen and play service stops all the time.
Which gapps version do you use ? I need a stable version.
Thank you
Acer A500
Click to expand...
Click to collapse
From what I've tested omnirom 5.1.1 seems to run a little better than cm 12 so you could try that. When you overclock it to about 1.5 GHz it runs pretty good. As for the Google play bug idk how to fix that I haven't tried KitKat on my device in a while.

turnert said:
From what I've tested omnirom 5.1.1 seems to run a little better than cm 12 so you could try that. When you overclock it to about 1.5 GHz it runs pretty good. As for the Google play bug idk how to fix that I haven't tried KitKat on my device in a while.
Click to expand...
Click to collapse
Thanks a lot the opengapps work fine with this version. I'll stick to this. :good:

Hello I stumbled upon this because it seems to be the most detailed but I have an ACER A501 and so I can not use the blackthunder to get my CPUID and my file explore allows me to go to 'fuse' but i do not see my cpuid there either. please help. These are all my device details.
Model number: A501
Android version: 3.2.1
Kernel version: 2.6.36.3+
Build number: Acer_A501_4.066.24_COM_GEN1

Klaw El said:
Hello I stumbled upon this because it seems to be the most detailed but I have an ACER A501 and so I can not use the blackthunder to get my CPUID and my file explore allows me to go to 'fuse' but i do not see my cpuid there either. please help. These are all my device details.
Model number: A501
Android version: 3.2.1
Kernel version: 2.6.36.3+
Build number: Acer_A501_4.066.24_COM_GEN1
Click to expand...
Click to collapse
Try the USB deview method that is what I originally used with my a501.
https://forum.xda-developers.com/showthread.php?t=1624645

turnert said:
Try the USB deview method that is what I originally used with my a501.
https://forum.xda-developers.com/showthread.php?t=1624645
Click to expand...
Click to collapse
Thing is i don't understand this
"Suggest you extract to the same folder you used for your adb files,
USBDeview will only work when you have previously plugged your tab into the PC WHILE
you were running HC Rom and BL"
specifically adb files ad i also didnt plug it in previously running those things

[OFFICIAL] LineageOS 20 for the Nokia 6.1 (2018)/6.1 Plus

{
"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"
}
Nokia 6.1 (2018)/6.1 Plus
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 20 thread for the Nokia 6.1 (2018)/6.1 Plus.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
Nokia 6.1 (2018)​
PL2 - Official builds​
PL2 - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.​
Nokia 6.1 Plus​
DRG - Official builds​
DRG - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.​
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.​
Find any? Report them according to this guide.​
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.​
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!​
Kernel Source: https://github.com/LineageOS/android_kernel_nokia_sdm660

Is this rom based on Android 13?

ardwivedi16 said:
Is this rom based on Android 13?
Click to expand...
Click to collapse
yes

very excited waiting

worked my phone, yesterday i tried clean flash but not boot, and today i tried update with sideload and worked

I updated a PL2 device from your inofficial Lineage 19.1 to this one. Worked fine. The camera flash is still not working.

Thanks for your work supporting our devices! This is a bootloop for me on DRG. (It goes directly to a black screen after the Android One logo and immediately resets. It doesn't get to the LOS boot animation.)
I tried even flashing completely back to stock before flashing the rom but got the same result. It might be an issue with your kernel since I can see the LOS boot animation for a brief moment if I flash to a non-LOS boot.img. Still doesn't boot though.
I don't know, maybe other DRG users will have better luck. I appreciate that new A13 roms are being made though.

kazekiri said:
Thanks for your work supporting our devices! This is a bootloop for me on DRG. (It goes directly to a black screen after the Android One logo and immediately resets. It doesn't get to the LOS boot animation.)
I tried even flashing completely back to stock before flashing the rom but got the same result. It might be an issue with your kernel since I can see the LOS boot animation for a brief moment if I flash to a non-LOS boot.img. Still doesn't boot though.
I don't know, maybe other DRG users will have better luck. I appreciate that new A13 roms are being made though.
Click to expand...
Click to collapse
flash lineageos 19.1 unofficial first and then update lineageos 20 via adb sideload

backspace123// said:
flash lineageos 19.1 unofficial first and then update lineageos 20 via adb sideload
Click to expand...
Click to collapse
I did try adb sideload in lineage recovery, but unfortunately my result was the same whether I used that or TWRP. I think a kernel issue. Maybe the kernel just disagrees with my phone. I have the China X6 6GB variant of DRG. Usually I have no trouble flashing custom roms, but come to think of it, LOS based builds have given me the same bootloop issue on this device in the past.
EDIT 11/17
Today I confirmed that lineage-19.1-20221111-UNOFFICIAL-DRG.zip works perfectly on my DRG, but even if I update from there using LOS recovery adb sideload, lineage-20.0-20221110-UNOFFICIAL-DRG.zip will not get to the LOS boot animation on my DRG. If I replace boot.img with the one from lineage-19.1-20221111-UNOFFICIAL-DRG.zip then it will show the LOS boot animation for a brief moment. Looks like a kernel issue, maybe related to my exact DRG variant (X6 6GB).

kazekiri said:
I did try adb sideload in lineage recovery, but unfortunately my result was the same whether I used that or TWRP. I think a kernel issue. Maybe the kernel just disagrees with my phone. I have the China X6 6GB variant of DRG. Usually I have no trouble flashing custom roms, but come to think of it, LOS based builds have given me the same bootloop issue on this device in the past.
EDIT 11/17
Today I confirmed that lineage-19.1-20221111-UNOFFICIAL-DRG.zip works perfectly on my DRG, but even if I update from there using LOS recovery adb sideload, lineage-20.0-20221110-UNOFFICIAL-DRG.zip will not get to the LOS boot animation on my DRG. If I replace boot.img with the one from lineage-19.1-20221111-UNOFFICIAL-DRG.zip then it will show the LOS boot animation for a brief moment. Looks like a kernel issue, maybe related to my exact DRG variant (X6 6GB).
Click to expand...
Click to collapse
on my device worked, i tried update using lineageos19.1 official

schwedenespresso said:
I updated a PL2 device from your inofficial Lineage 19.1 to this one. Worked fine. The camera flash is still not working.
Click to expand...
Click to collapse
Hello, regarding the camera, it is quite likely that it is the kernel as such, in fact, in previous versions, LOS 18.1, 17.1, the flash worked from the camera application, but now it does not work, at the time it was published Official LineageOS for this device, the flash has never worked correctly as such (other applications were not able to take the picture with the flash on the camera due to failure in its execution) as if it did with the manufacturer's version, it is possible that the manufacturer has kept some hidden details at the code level or that the driver has not been fully released on the devices so that the developers themselves have difficulties to achieve a 100% functional version (without errors so to speak), the only solution to this problem is install a custom kernel, it seems some users with knowledge in programming found a way to solve the problem with the flash in the camera + the zoom failure as such, I have not found out if the developer would have adapted the kernel for the versions of android 13 for this specific device than if it is available for versions prior to the unofficial LOS 20 available.
Best regards

Hello everyone, for all those who have problems with their recovery (nothing is displayed, but it feels like it works internally), I will leave you a post that I made months ago, the recovery options should be the same for the latest versions, hopefully It is useful for you, remember that the installation process of LineageOS can last more than 4 minutes.
LineageOS recovery instructions for use build 2022-08-30 -When starting the recovery, 4 options will be presented, which are these.
Reboot system now.
Apply update
2.1)For this step I recommend selecting the first option with the power button of the device, which is by ADB
3)Factory Reset
3.1)Format data/factory reset
4. Advance
4.1) advanced options, with this image it will serve to guide you in how many clicks you have to press to access the option with the power button of the device to access one of these options.
Best regards

backspace123// said:
on my device worked, i tried update using lineageos19.1 official
View attachment 5763487
Click to expand...
Click to collapse
I'm happy for your man, but it isn't going to work on my DRG. I tried everything, and I am a long-time rom flasher and know what I'm doing. The kernel in this rom will not boot on my specific variant of DRG. I've had issues similar to this with certain roms in the past. There seem to be subtle differences between my DRG and the one that most people have. Most other roms will work on my phone, but occasionally some come with a kernel that will not boot on my phone. It just bootloops immediately after the Android One logo. Doesn't even get to the rom boot animation.
I will try again when the next update is released. It sounds like there are still more changes to the kernel coming.

kazekiri said:
I'm happy for your man, but it isn't going to work on my DRG. I tried everything, and I am a long-time rom flasher and know what I'm doing. The kernel in this rom will not boot on my specific variant of DRG. I've had issues similar to this with certain roms in the past. There seem to be subtle differences between my DRG and the one that most people have. Most other roms will work on my phone, but occasionally some come with a kernel that will not boot on my phone. It just bootloops immediately after the Android One logo. Doesn't even get to the rom boot animation.
I will try again when the next update is released. It sounds like there are still more changes to the kernel coming.
Click to expand...
Click to collapse
are you on android 9 or 10 firmware?
And no, no kernel changes coming.

npjohnson said:
are you on android 9 or 10 firmware?
And no, no kernel changes coming.
Click to expand...
Click to collapse
Mine should be 10 firmware since I updated to the last DRG OTA just before flashing your ROM.

kazekiri said:
Mine should be 10 firmware since I updated to the last DRG OTA just before flashing your ROM.
Click to expand...
Click to collapse
Figured it out - next build should work. give it like, 4 hours.

npjohnson said:
Figured it out - next build should work. give it like, 4 hours.
Click to expand...
Click to collapse
Yep. Whatever you did worked! Booted on my DRG. Haven't tested everything yet, but so far seems great.
Thanks! You are one dedicated dev!

So what is everyone using for the camera on this rom? I'm having the common issue where I can only take a few pics before the shutter stops responding, and the phone needs to be restarted before I can take any more pics. Same issue with both gcam and even the camera included with the rom. (DRG)

I have the same camera issue, any solution for DRG?

kazekiri said:
So what is everyone using for the camera on this rom? I'm having the common issue where I can only take a few pics before the shutter stops responding, and the phone needs to be restarted before I can take any more pics. Same issue with both gcam and even the camera included with the rom. (DRG)
Click to expand...
Click to collapse
Weird, works on PL2. got logs?