Code:
*** Disclamer
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Introduction
This is the LineageOS 18.1 for LG G8s ThinQ
Click to expand...
Click to collapse
Installation instructions
1. Install Q Stock Rom onto your phone , follow some tutorial you can find in this forum
2. Flash boot.img and dtbo.img by typing fastboot flash boot boot.img and fastboot flash dtbo_a dtbo.img and fastboot flash dtbo_b dtbo.img
3. Wipe your userdata by typing fastboot erase userdata
4. Reboot the phone and immeditly do the recovery key combination
5. In Lineageos recovery select install and then sideload from adb
6. On your computer type adb sideload pathtotheromzip and press enter
7. The rom should now be flashed , flash gapps and other mods like magisk the same way
Click to expand...
Click to collapse
Download
ROM
RECOVERY
Click to expand...
Click to collapse
Changelog
Code:
Current changelog:16.01.2021
[note] 1st Release of Lineage 18.1
[new] Android 11 R
[changed]
[fixed] Rom boots into OS
Older changelogs:
Click to expand...
Click to collapse
FAQ
What doesnt work ?
You tell me
This is only for G8s not for G8 also not for G8X
VOLTE DONT WORK AND IT WONT EVER WORK
For Gapps i recommend NikGapps
Click to expand...
Click to collapse
Thanks To/Credits
Code:
@SGCMarkus
Sources
Code:
[URL="https://github.com/J0SH1X/android_kernel_lge_sm8150]Kernel[/URL]
[URL="https://github.com/J0SH1X/android_device_lge_sm8150-common"]Common[/URL]
[URL="https://github.com/J0SH1X/android_device_lge_betalm"]Device[/URL]
[URL="https://github.com/J0SH1X/android_device_lge_beta-common"]Device-Common[/URL]
Great work. Do you plan to do official LineageOs version?
Any chance for g8?
We wait for the next releases, finally something new. Already installed but hopefully soon a fix for the headphone jack
Great Work!!
Hello! Excuse me, is there a chance to install TWRP on the LG G8s?
thanks for your work that exactly what im looking for
lg makes some good hardware but the worst software support, im corrently waiting for january security patch but not yet
i want to ask if you will keep supporting LG G8S ?
OzAcid22 said:
We wait for the next releases, finally something new. Already installed but hopefully soon a fix for the headphone jack
Click to expand...
Click to collapse
Hello, did you test the variant of the 19 or 23?
Any1 that tried it can tell pros and cons vs LG stock Android 10 rom ?.
I'd like to try it but that means loosing DTS: X codec, equalizer or whatever it is that makes sound much better, and as long as I know Android 11 is worse than 10 for gaming, isn't it?
Does this rom has newer & better drivers for Adreno GPU?
BlackSunCL said:
Hello, did you test the variant of the 19 or 23?
Click to expand...
Click to collapse
19 but in 23 it has not been fixed yet I think, just read the change log of 23
Eduxki said:
Any1 that tried it can tell pros and cons vs LG stock Android 10 rom ?.
I'd like to try it but that means loosing DTS: X codec, equalizer or whatever it is that makes sound much better, and as long as I know Android 11 is worse than 10 for gaming, isn't it?
Does this rom has newer & better drivers for Adreno GPU?
Click to expand...
Click to collapse
I change everything a bit, the rom is obviously more stock and faster, especially if you use the gestures for navigation, it is true you lose the audio features, On the gaming side, I think it doesn't change much and I think it has the same drivers as the stock rom. The sure thing is that if you love android "stock" it is much better, unfortunately it is still very unripe for certain aesthetic things(For example the "notification panel" top bar turns out to be lower than the height of the notch, but you can fix it through some mods and magisk) but maybe soon it will be fixed.
I need help, I flash both the boot.img and the dtbo.img like said in the instructions and when I try to reboot into said Lineageos recovery it never works and I tried ever feasible key combination and it never goes into a lineageos recovery to continue the flashing, Any help or feed back would be appreciated.
sockopucko said:
I need help, I flash both the boot.img and the dtbo.img like said in the instructions and when I try to reboot into said Lineageos recovery it never works and I tried ever feasible key combination and it never goes into a lineageos recovery to continue the flashing, Any help or feed back would be appreciated.
Click to expand...
Click to collapse
I would recommend a flash of the stock system and then repeat the steps, if the volume keys and the Power on / off work you should go to the lineage recovery. Have you checked if there is any error during the terminal flash? Or check the files by re-downloading them, let me know if it works, to enter recovery mode you have to keep the volume key down and the power key, at the first writing you have to leave the power key and then press it again
OzAcid22 said:
I would recommend a flash of the stock system and then repeat the steps, if the volume keys and the Power on / off work you should go to the lineage recovery. Have you checked if there is any error during the terminal flash? Or check the files by re-downloading them, let me know if it works, to enter recovery mode you have to keep the volume key down and the power key, at the first writing you have to leave the power key and then press it again
Click to expand...
Click to collapse
Ok well I managed to get the recovery working by tapping the volume down key while the lg logo was up but now every time I try to adb sideload the Lineageos file it get's stuck at 47% on computer and then spits out an error saying failed to read command no error I've tried a number of "fixes" to no avail.
sockopucko said:
Ok well I managed to get the recovery working by tapping the volume down key while the lg logo was up but now every time I try to adb sideload the Lineageos file it get's stuck at 47% on computer and then spits out an error saying failed to read command no error I've tried a number of "fixes" to no avail.
Click to expand...
Click to collapse
I initially had the same problem apparently maybe you have multiple versions of adb installed, try to delete and uninstall everything and then install only one, check that the zip file is not damaged by simply opening it from the PC, if it gives you an error that will be the problem , if you had to try several times to transport the file through adb sidelaod just go to advanced and restart the recovery and then try the step again
OzAcid22 said:
I initially had the same problem apparently maybe you have multiple versions of adb installed, try to delete and uninstall everything and then install only one, check that the zip file is not damaged by simply opening it from the PC, if it gives you an error that will be the problem , if you had to try several times to transport the file through adb sidelaod just go to advanced and restart the recovery and then try the step again
Click to expand...
Click to collapse
I've uninstalled and reinstalled adb drivers on my computer but I'm still getting the same problem I think I'll just wait until there's a twrp recovery for the device being that it makes processes like this a whole lot easy, Thank you for the help anyway I appreciate it.
You can only install 19 the others don't work .. even if you install 19 and try to update to the latest version after the update it doesn't work anymore.
sockopucko said:
Ok well I managed to get the recovery working by tapping the volume down key while the lg logo was up but now every time I try to adb sideload the Lineageos file it get's stuck at 47% on computer and then spits out an error saying failed to read command no error I've tried a number of "fixes" to no avail.
Click to expand...
Click to collapse
Its normal for it to get "stuck" at 47%, because at that point its sideloaded to device already and should already be showing its installing on the device, it does give a wierd error but installs anyway, allow it to install and make sure you erased userdata in fastboot before trying to flash
Btw - you can install from ext SD as well not just sideload
If all fails, restore with LGup and make sure you first boot into lg rom and pass setup and FRP, device gives a wierd formatting bootloop if you dont.
Boot into fastboot
Erase userdata
Flash boot and dtbo
Boot into los recovery
Sideload /install zip from SD
After installing step 2 passes, reboot, give it a minute, rom should be booted
HI guys! i have any hard problem, i've delete all partition with "QFIL" and i've not files backup.qcn or rawprogram.xml or patch.Please if is possible load here your files for help me- ty much guys
Qualcuno può aiutarmi?
Related
Hello everyone, I have the problem, that my 3T boots to recovery every time I boot. The system is no more booting. What I did was, "updating" in the CM about/update menu (from unofficial cm14.1 13.12. to 14.12. ).
So maybe an open recovery script was created and booted to bootloader. Update failed but I did it manually.
From now on the phone does just only boot twrp recovery (or is it a boot loop ?). I tried to restore a backup and install the oxygen os via zip and wiped all partitions (except internal storage) but nothing helps. Does anyone know this and can give me advice ? Thank a lot in advance.
Edit:
For the OnePlus One if found an error report which look a little bit my error:
The problem is suspected to stem from the "persist" partition getting corrupted during the reboot, even though CyanogenMod doesn't use this particular location. The damaged area doesn't get fixed like other partitions because a filesystem integrity check isn't ran. It's left corrupted, and even though the area isn't needed for the OS to run, the OnePlus One boot loops anyway.
Click to expand...
Click to collapse
But the partition layout on the 3T seems to be different, I can see only partitions like sda etc ...
same here
Called the 1+ support and they sent me the same file like in this post http://forum.xda-developers.com/oneplus-3t/help/unbrick-unbrick-tutorial-oneplus-3t-t3515306 They offered me a telephone support slot in 2 days, but I tried myself, now the default system is booting again. If you need assistance write I can guide you as best as i can.
Good luck to you.
sniperle said:
Called the 1+ support and they sent me the same file like in this post http://forum.xda-developers.com/oneplus-3t/help/unbrick-unbrick-tutorial-oneplus-3t-t3515306 They offered me a telephone support slot in 2 days, but I tried myself, now the default system is booting again. If you need assistance write I can guide you as best as i can.
Good luck to you.
Click to expand...
Click to collapse
Thank you!
Enviado do meu ONEPLUS A3003 através de Tapatalk
Thnaks so much
sniperle said:
Called the 1+ support and they sent me the same file like in this post http://forum.xda-developers.com/oneplus-3t/help/unbrick-unbrick-tutorial-oneplus-3t-t3515306 They offered me a telephone support slot in 2 days, but I tried myself, now the default system is booting again. If you need assistance write I can guide you as best as i can.
Good luck to you.
Click to expand...
Click to collapse
:good:
I follow your recommendation thanks for your assistance I fixed my OP3T,
What a mess ... after all this I wanted to install my CM backups again, but TWRP refused to boot. I had only a black screen with a white LED when going to recovery. But now after some hours I have a solution to this. You need to update Oxygen OS before going on !!
Make a full system update or flash this update via TWRP: http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_3.5.3/
After this TWRP is booting as expected.
Now I'll enjoy a beer or two or ....
Good luck to all others. If anybody needs assistance ... contact me.
never had a issue
Please help!!!! I tried flashing the update for the latest OTA, I had the full zip. I have unlocked bootloader, twrp, phh supersu, magisk and xposed. I did a nandroid backup and then clicked Wipe- Dalvik and Cache. I then flashed the zip. For 20 mins the boot logo was spinning around, so I rebooted into twrp to see what was going on. Now I can't reboot and it shows no data, it says my device is encrypted and I can't see any files. What can I do??
Was your internal storage encrypted before ?
TWRP doesn't show your internal storage and didn't ask for a password ?
fix bootloop
Boot into your recovery [Vol+ and Power]
Connect your phone to your PC
Execute the following fastboot command on your PC (More informations on fastboot)
Code:
fastboot continue
Your phone will start right away. :good:
I solved the problem
OK what i did was when the phone was starting and vibrating I push the power bottom and volume down bottom at the same time ,then i connected the phone to the PC,from the panel in the phone there are 3 categories to erase everything on the phone I did it all(1,2,3) and then I put the phone in ADB mode from the control panel in the phone,After that I flash via fastboot the original .zip from one plus for the version 4.0.3 (1.4 GB) ,when it finished I restarted and the phone started normal again,I hope this help someone alse,I was so desesperated:silly:.
RE
TOMASITO95 said:
OK what i did was when the phone was starting and vibrating I push the power bottom and volume down bottom at the same time ,then i connected the phone to the PC,from the panel in the phone there are 3 categories to erase everything on the phone I did it all(1,2,3) and then I put the phone in ADB mode from the control panel in the phone,After that I flash via fastboot the original .zip from one plus for the version 4.0.3 (1.4 GB) ,when it finished I restarted and the phone started normal again,I hope this help someone alse,I was so desesperated:silly:.
Click to expand...
Click to collapse
how ? can you please teach me ( my op3t didn`t go to system is says " md5 checksum failed , recovery failed , boot failed , system failed , boot_aging failed , dsp failed , modem failed please help me (
Change USB port
Try a different USB port. I flashed it through a 2.0 USB port instead of the 3.0 and no checksum error!
im really stupid, i was installing twrp, i did a advanced wipe to afterwards install a custom rom, and when my phone was done wiping i accidentally pushed the power button and turned of my phone. now it is stuck in fastboot mode. i tried reinstalling twrp but i can't boot into twrp, it keeps turning on in fastboot mode
thanks in advance
Reflash miui with miflash, be sure yo untick the lock thing onnthe bottom sonyoubdont lock bootloader, then try again.
Sounds like partition is fked
Rikkertbiemans said:
im really stupid, i was installing twrp, i did a advanced wipe to afterwards install a custom rom, and when my phone was done wiping i accidentally pushed the power button and turned of my phone. now it is stuck in fastboot mode. i tried reinstalling twrp but i can't boot into twrp, it keeps turning on in fastboot mode
thanks in advance
Click to expand...
Click to collapse
After flashing TWRP and still in fastboot, hold power and vol+. Keep both held while it reboots, it takes a few seconds. When the Redmi logo appears and the phone vibrates release the power button. Keep holding the vol+ button until it boots into TWRP.
Robbo.5000 said:
After flashing TWRP and still in fastboot, hold power and vol+. Keep both held while it reboots, it takes a few seconds. When the Redmi logo appears and the phone vibrates release the power button. Keep holding the vol+ button until it boots into TWRP.
Click to expand...
Click to collapse
this was the first thing i tried, but it keeps rebooting to fastboot, if i hold it longer it wil just reboot again. i've tried miflash, but miflash can't find a flash all.bat and when i go into explorer i can't find it either.
problem solved, i installed another version of twrp, deleted it and reinstalled the first one. thanks for all answers, it really helped along
Hey glad to hear you solved the issue. What version of TWRP did you end up flashing and what tool did you use to flash it? I'm facing a similar issue.
Thanks
kh805794 said:
Hey glad to hear you solved the issue. What version of TWRP did you end up flashing and what tool did you use to flash it? I'm facing a similar issue.
Thanks
Click to expand...
Click to collapse
I can't answer for OP, but he looks to have abandoned the thread.
What I can recommend from personal experience is that using latest version of TWRP - I think it's 4.3.3 (can't tell you exactly, as I'm writing this without checking my laptop on which I have the TWRP and ROM files) - will resolve all your problems.
Thanks for your reply I actually just managed to get root/TWRP/Magisk to work. A lot of the TWRP recovery images that I encountered just caused the phone to boot loop or get stuck on fastboot mode.
The TWRP that worked for me was twrp-3.3.1-15-raphael-mauronofrio.img
following:
fastboot flash recovery twrp-3.3.1-15-raphael-mauronofrio.img
For reference I have the global Mi 9T Pro
Rikkertbiemans said:
problem solved, i installed another version of twrp, deleted it and reinstalled the first one. thanks for all answers, it really helped along
Click to expand...
Click to collapse
I am also having this issue, after doing the exact same thing you did...
Would you be able to post the download link you got your TWRP version from? And maybe go into a little more detail about the reinstalling order (if that is important)?
Also the "mauronofrio" version didn't work (I have the Mi 9T), are there any other options out there?
Many thanks for any responses
camelCaseOnly said:
I am also having this issue, after doing the exact same thing you did...
Would you be able to post the download link you got your TWRP version from? And maybe go into a little more detail about the reinstalling order (if that is important)?
Also the "mauronofrio" version didn't work (I have the Mi 9T), are there any other options out there?
Many thanks for any responses
Click to expand...
Click to collapse
Did you ever get this solved? I'm in a similar situation after what I thought was a normal ROM flashing.
EDIT: Nevermind. Got it fixed using MiFlash.
theCroh said:
Did you ever get this solved? I'm in a similar situation after what I thought was a normal ROM flashing.
EDIT: Nevermind. Got it fixed using MiFlash.
Click to expand...
Click to collapse
Hey sorry didn't see your reply... I haven't had time in the last month to look at it so I'm still stuck. How did you fix it using MiFlash? Did you make it force load TWRP onto the phone or something?
I think there is definitely something wrong with the partition, as when I plug it into the computer it no longer comes up in "my computer" - although I do have the MIUI recovery working again.
Cheers
Rikkertbiemans said:
im really stupid, i was installing twrp, i did a advanced wipe to afterwards install a custom rom, and when my phone was done wiping i accidentally pushed the power button and turned of my phone. now it is stuck in fastboot mode. i tried reinstalling twrp but i can't boot into twrp, it keeps turning on in fastboot mode
thanks in advance
Click to expand...
Click to collapse
Flash images manually mr
camelCaseOnly said:
Hey sorry didn't see your reply... I haven't had time in the last month to look at it so I'm still stuck. How did you fix it using MiFlash? Did you make it force load TWRP onto the phone or something?
I think there is definitely something wrong with the partition, as when I plug it into the computer it no longer comes up in "my computer" - although I do have the MIUI recovery working again.
Cheers
Click to expand...
Click to collapse
I just flashed a full fastboot MIUI ROM in fastboot using the MiFlash portable tool. No need to do anything in recovery.
Edit: You can find fastboot ROMs from the OP of this thread https://forum.xda-developers.com/k20-pro/how-to/redmi-k20-pro-firmware-10-3-8-0-9-6-13-t3939647/ (labeled as ...fastboot)
EpickBroVlad said:
Flash images manually mr
Click to expand...
Click to collapse
Where can I find the right commands for flashing
theCroh said:
I just flashed a full fastboot MIUI ROM in fastboot using the MiFlash portable tool. No need to do anything in recovery.
Edit: You can find fastboot ROMs from the OP of this thread https://forum.xda-developers.com/k20-pro/how-to/redmi-k20-pro-firmware-10-3-8-0-9-6-13-t3939647/ (labeled as ...fastboot)
Click to expand...
Click to collapse
I'm still not able to get TWRP working... I think all of my problems will be solved as soon as I can get into it, but each time I load the recovery image on (using command prompt) it says it completes, but when I try to reboot it into recovery mode it never works (if I use command prompt to reboot into recovery it just shuts down but if I hold the button combination it either reboots back into fastboot or the original MIUI recovery mode - and yes, I am using the right button combinations).
I've tried every version of TWRP I could find, so I'm certain its not a problem with the recovery image itself... Have you or anyone else had this happen before? It's so infuriating that it just doesn't work, but I don't know why...
BTW the commands I'm using are
Code:
fastboot flash recovery "recovery.img"
(which works) and then
Code:
fastboot boot "recovery.img"
(which gives 2 OKs, but the phone just turns off).
(this all after setting the directory to my adb folder)
camelCaseOnly said:
I'm still not able to get TWRP working... I think all of my problems will be solved as soon as I can get into it, but each time I load the recovery image on (using command prompt) it says it completes, but when I try to reboot it into recovery mode it never works (if I use command prompt to reboot into recovery it just shuts down but if I hold the button combination it either reboots back into fastboot or the original MIUI recovery mode - and yes, I am using the right button combinations).
I've tried every version of TWRP I could find, so I'm certain its not a problem with the recovery image itself... Have you or anyone else had this happen before? It's so infuriating that it just doesn't work, but I don't know why...
BTW the commands I'm using are
Code:
fastboot flash recovery "recovery.img"
(which works) and then
Code:
fastboot boot "recovery.img"
(which gives 2 OKs, but the phone just turns off).
(this all after setting the directory to my adb folder)
Click to expand...
Click to collapse
This worked
https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363
now shall I keep read only or allow modifications?
claudioita said:
This worked
https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363
now shall I keep read only or allow modifications?
Click to expand...
Click to collapse
Unfortunately I wasn't able to access that link for some reason, but I did FINALLY manage to get it to work using another version from this thread; specifically the 4PDA 3.3.1-3 build and instructions referenced in the original post (I was using MIUI 11.0.1.0 at the time).
solution
you need the version for youre board if you open aida64 on youre phone is says davinci on my xiaomy mi 9t so download the twrp for davinci and it works i had the same problem too stuck in fast boot , im new to this this is my frist time im trying to install a new beta for miui
camelCaseOnly said:
Unfortunately I wasn't able to access that link for some reason, but I did FINALLY manage to get it to work using another version from this thread; specifically the 4PDA 3.3.1-3 build and instructions referenced in the original post (I was using MIUI 11.0.1.0 at the time).
Click to expand...
Click to collapse
Yy
help!
my honor 9 lite bootloader is unlocked and i have installed an unknown kernel and now when i want boot into twrp it will boot into stock recovery and when i flash twrp and boot it will boot into stock
i tried all of twrp versions :|
wtf should i do?
plz help me
So i flashed The pixelrom for mi8, and so far so good, but now i want to install magisk and twrp is gone, it was replaced with the stock recovery, and now when i try to do the exact same process with xiaomitoolv2 he detects my phone has pixel 4 and doesn't detect, i tried fastboot but it doesn't work either, Im running xubuntu x64
https://i.imgur.com/J9E6QmWl.png
EDIT: AFTER SEEING SOME POSTS HERE ON XDA I MANAGED TO USE XIAOMI MI FLASH TOOL WITH SUCCESS!, I NEEDED A USB HUB AND CONNECT THE PHONE IN FASTBOOT AND THEN APPLY THE STOCK IMAGES!, ANYONE WHO NEEDS HELP THIS SOLUTION CAN WORK ( ALL MY 3 USB PORTS DIDN'T WORK, WITH HUB IT WORKED )
ClaudioG123 said:
So i flashed The pixelrom for mi8, and so far so good, but now i want to install magisk and twrp is gone, it was replaced with the stock recovery, and now when i try to do the exact same process with xiaomitoolv2 he detects my phone has pixel 4 and doesn't detect, i tried fastboot but it doesn't work either, Im running xubuntu x64
https://i.imgur.com/J9E6QmWl.png
Click to expand...
Click to collapse
You do not have fastboot? ( think its more likely that you just can see the fastboot screen, but the phone is likely in fastboot mode. Because it sounds like you flashed a custom splash screen, which is causing your fastboot screen to not come up.
Also It seems that you missed some of the steps outlined in the install instructions for the Pixel rom ( I assume the Pixel 3 Q rom?)
You must install Magisk on that rom, you must use recommended TWRP,
I haven't used Ubuntu for flashing Roms recently so I can't provide solid recent steps on Ubuntu.
So I would suggest using a PC , ( surely you know someone with a PC) Enter fastboot, then you can verify that the phone actually can enter fastboot by checking Device manager, or by verifying that the phone is seen by ADB
If you are unable to access fastboot, you will need to go into EDL mode. Once in EDL
Download fastboot dipper images rom, and use flashall.bat method to restore the phone.
Download dipper_global_images_9.6.27_20190627.0000.00_9.0_global or a newer fastboot rom such as 10 .3..5 But It has to be a fastboot rom and not a Recovery rom
Unpack the rom twice on your desktop
You will be left with a folder and inside you will see batch files and a image folder.
Doubleclick Flashall.bat ( be careful on what you click, you want flashall.bat only) with the phone attached an in Recovery mode, fastboot or EDL
Flashall.bat is a batch script that will wipe your phone and restore all images, and then boot to system.
You should then Setup rom
Afterwards install TWRP and root then create a full Twrp backup and save to your PC.
This way you will have a quick solution if you ever need it again in the future.
Enjoy a working phone
Rom Link : https://bigota.d.miui.com/9.6.27/di...27_20190627.0000.00_9.0_global_30e0fc22ef.tgz
Any images fastboot rom will work, you can use the one I listed above or you can use the recent 10.3.5 Stable images rom, just find the link via Google.
I just spent 20 minutes typing this, so be considerate and click thanks or send me a beer if you want.
tsongming said:
You do not have fastboot? ( think its more likely that you just can see the fastboot screen, but the phone is likely in fastboot mode. Because it sounds like you flashed a custom splash screen, which is causing your fastboot screen to not come up.
Also It seems that you missed some of the steps outlined in the install instructions for the Pixel rom ( I assume the Pixel 3 Q rom?)
You must install Magisk on that rom, you must use recommended TWRP,
I haven't used Ubuntu for flashing Roms recently so I can't provide solid recent steps on Ubuntu.
So I would suggest using a PC , ( surely you know someone with a PC) Enter fastboot, then you can verify that the phone actually can enter fastboot by checking Device manager, or by verifying that the phone is seen by ADB
If you are unable to access fastboot, you will need to go into EDL mode. Once in EDL
Download fastboot dipper images rom, and use flashall.bat method to restore the phone.
Download dipper_global_images_9.6.27_20190627.0000.00_9.0_global or a newer fastboot rom such as 10 .3..5 But It has to be a fastboot rom and not a Recovery rom
Unpack the rom twice on your desktop
You will be left with a folder and inside you will see batch files and a image folder.
Doubleclick Flashall.bat ( be careful on what you click, you want flashall.bat only) with the phone attached an in Recovery mode, fastboot or EDL
Flashall.bat is a batch script that will wipe your phone and restore all images, and then boot to system.
You should then Setup rom
Afterwards install TWRP and root then create a full Twrp backup and save to your PC.
This way you will have a quick solution if you ever need it again in the future.
Enjoy a working phone
Rom Link : https://bigota.d.miui.com/9.6.27/di...27_20190627.0000.00_9.0_global_30e0fc22ef.tgz
Any images fastboot rom will work, you can use the one I listed above or you can use the recent 10.3.5 Stable images rom, just find the link via Google.
I just spent 20 minutes typing this, so be considerate and click thanks or send me a beer if you want.
Click to expand...
Click to collapse
Tried that but this happens in the batch file, also it goes to the fastboot screen where it appears fastboot and the figure, but when i press the batch he leaves that screen and goes to black screen with on top saying press to restart or shutdown, and that error occurs on the batch, even if the phone isn't conected it gets me that error
ClaudioG123 said:
Tried that but this happens in the batch file, also it goes to the fastboot screen where it appears fastboot and the figure, but when i press the batch he leaves that screen and goes to black screen with on top saying press to restart or shutdown, and that error occurs on the batch, even if the phone isn't conected it gets me that error
Click to expand...
Click to collapse
And also I only went Linux because on Windows the phone was getting detected but wasn't working, and Linux was detecting and working with xiaomitoolv2
I will try on Linux to see If the error persists, but that error can he there because the phone, the brand, model and codename are the same has the pixel 4
ClaudioG123 said:
And also I only went Linux because on Windows the phone was getting detected but wasn't working, and Linux was detecting and working with xiaomitoolv2
I will try on Linux to see If the error persists, but that error can he there because the phone, the brand, model and codename are the same has the pixel 4
Click to expand...
Click to collapse
If you are using linux and successful rebooted the phone into fastboot mode, just try to replace the recovery.
Download the recent version of TWRP for your phone and move it to the fastboot directory then open a shell in that directory.
Type in your shell: "sudo fastboot flash recovery yourtwrpimage.img"
Now, unplug the USB and you MUST reboot and immediately hold down the upvolume and power until the TWRP boots. If you miss it, the system will replace the stock recovery image again and you will have to start over.
You can then individually flash the partition images of your choice or ROM ZIP file, but you will still have to flash the full fastboot images after you get the phone recognizing as an mi8.
Agimax said:
If you are using linux and successful rebooted the phone into fastboot mode, just try to replace the recovery.
Download the recent version of TWRP for your phone and move it to the fastboot directory then open a shell in that directory.
Type in your shell: "sudo fastboot flash recovery yourtwrpimage.img"
Now, unplug the USB and you MUST reboot and immediately hold down the upvolume and power until the TWRP boots. If you miss it, the system will replace the stock recovery image again and you will have to start over.
You can then individually flash the partition images of your choice or ROM ZIP file, but you will still have to flash the full fastboot images after you get the phone recognizing as an mi8.
Click to expand...
Click to collapse
Will try soon as im home, if i get waiting for device should i wait?
Agimax said:
If you are using linux and successful rebooted the phone into fastboot mode, just try to replace the recovery.
Download the recent version of TWRP for your phone and move it to the fastboot directory then open a shell in that directory.
Type in your shell: "sudo fastboot flash recovery yourtwrpimage.img"
Now, unplug the USB and you MUST reboot and immediately hold down the upvolume and power until the TWRP boots. If you miss it, the system will replace the stock recovery image again and you will have to start over.
You can then individually flash the partition images of your choice or ROM ZIP file, but you will still have to flash the full fastboot images after you get the phone recognizing as an mi8.
Click to expand...
Click to collapse
I can try to see if he works with xiaomitoolv2, and will try what you said and post here
tsongming said:
you do not have fastboot? ( think its more likely that you just can see the fastboot screen, but the phone is likely in fastboot mode. Because it sounds like you flashed a custom splash screen, which is causing your fastboot screen to not come up.
Also it seems that you missed some of the steps outlined in the install instructions for the pixel rom ( i assume the pixel 3 q rom?)
you must install magisk on that rom, you must use recommended twrp,
i haven't used ubuntu for flashing roms recently so i can't provide solid recent steps on ubuntu.
so i would suggest using a pc , ( surely you know someone with a pc) enter fastboot, then you can verify that the phone actually can enter fastboot by checking device manager, or by verifying that the phone is seen by adb
if you are unable to access fastboot, you will need to go into edl mode. Once in edl
download fastboot dipper images rom, and use flashall.bat method to restore the phone.
download dipper_global_images_9.6.27_20190627.0000.00_9.0_global or a newer fastboot rom such as 10 .3..5 but it has to be a fastboot rom and not a recovery rom
unpack the rom twice on your desktop
you will be left with a folder and inside you will see batch files and a image folder.
doubleclick flashall.bat ( be careful on what you click, you want flashall.bat only) with the phone attached an in recovery mode, fastboot or edl
flashall.bat is a batch script that will wipe your phone and restore all images, and then boot to system.
you should then setup rom
afterwards install twrp and root then create a full twrp backup and save to your pc.
this way you will have a quick solution if you ever need it again in the future.
enjoy a working phone
rom link : https://bigota.d.miui.com/9.6.27/di...27_20190627.0000.00_9.0_global_30e0fc22ef.tgz
any images fastboot rom will work, you can use the one i listed above or you can use the recent 10.3.5 stable images rom, just find the link via google.
I just spent 20 minutes typing this, so be considerate and click thanks or send me a beer if you want.
Click to expand...
Click to collapse
i used this solution but i go i connected the phone in a usb hub!
ClaudioG123 said:
i used this solution but i go i connected the phone in a usb hub!
Click to expand...
Click to collapse
Did you try as @Agimax suggested? You have shown that the device is seen in fastboot. If you can push recovery to the phone then the issue will be easily resolved.
You should also be able to use this modified MiFlash : https://forum.xda-developers.com/android/software/tool-miflash-linux-t3708847
( Maybe you are already using this?)
I have also had the issue in the past where fastboot was available but attempting to push recovery failed. In some cases trying alternate versions of TWRP would work, and for me fastboot flashall will usually always work.
Another option is to push the images from the images folder individually. if one fails go to the next and then come back and retry the images that failed the first time. (Edit: I just reread Agimax post above, he mentioned this already.)
If you are in EDL mode you should be able to restore the stock images without receiving the error message You can enter EDL without opening the device, either by using a EDL deep flash cable or https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
Another option ( requires a PC) is QPST, which I have used a lot in the past, its quick and easy to use. : https://miui.blog/any-devices/qualcomm-qpst-tool/
tsongming said:
Did you try as @Agimax suggested? You have shown that the device is seen in fastboot. If you can push recovery to the phone then the issue will be easily resolved.
You should also be able to use this modified MiFlash : https://forum.xda-developers.com/android/software/tool-miflash-linux-t3708847
( Maybe you are already using this?)
I have also had the issue in the past where fastboot was available but attempting to push recovery failed. In some cases trying alternate versions of TWRP would work, and for me fastboot flashall will usually always work.
Another option is to push the images from the images folder individually. if one fails go to the next and then come back and retry the images that failed the first time. (Edit: I just reread Agimax post above, he mentioned this already.)
If you are in EDL mode you should be able to restore the stock images without receiving the error message You can enter EDL without opening the device, either by using a EDL deep flash cable or https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
Another option ( requires a PC) is QPST, which I have used a lot in the past, its quick and easy to use. : https://miui.blog/any-devices/qualcomm-qpst-tool/
Click to expand...
Click to collapse
Your solution worked with the phone in fastboot, but i had to try a usb hub, that's all, has for roms, experienced both of pixelrom3 and havoc and didn't conviced me enough, i find miui 11 of xiaomi.eu more good looking and doesn't have bugs, and thank you, you are a lifesafer, if it wasn't for that i would have never flashed stock rom back
tsongming said:
Did you try as @Agimax suggested? You have shown that the device is seen in fastboot. If you can push recovery to the phone then the issue will be easily resolved.
You should also be able to use this modified MiFlash : https://forum.xda-developers.com/android/software/tool-miflash-linux-t3708847
( Maybe you are already using this?)
I have also had the issue in the past where fastboot was available but attempting to push recovery failed. In some cases trying alternate versions of TWRP would work, and for me fastboot flashall will usually always work.
Another option is to push the images from the images folder individually. if one fails go to the next and then come back and retry the images that failed the first time. (Edit: I just reread Agimax post above, he mentioned this already.)
If you are in EDL mode you should be able to restore the stock images without receiving the error message You can enter EDL without opening the device, either by using a EDL deep flash cable or https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
Another option ( requires a PC) is QPST, which I have used a lot in the past, its quick and easy to use. : https://miui.blog/any-devices/qualcomm-qpst-tool/
Click to expand...
Click to collapse
After i put the usb usb on laptop both solutions worked, and i was in windows and not linux, in linux works also
ClaudioG123 said:
After i put the usb usb on laptop both solutions worked, and i was in windows and not linux, in linux works also
Click to expand...
Click to collapse
That's great sorry for being late to respond, I haven't had time to check XDA for a couple of days. But I an really glad that you got everything sorted out.
BTW, I agree about Xiaomi.EU, and I also find it to be the most stable...by far. Plus, it's obviously the most up to date. No doubt that AOSP roms are fun, but also very unpredictable. I keep Xaiomi.EU on mi daily driver, ( the Mi8) and I tinker around with AOSP roms on my old phones.
Take care
tsongming said:
That's great sorry for being late to respond, I haven't had time to check XDA for a couple of days. But I an really glad that you got everything sorted out.
BTW, I agree about Xiaomi.EU, and I also find it to be the most stable...by far. Plus, it's obviously the most up to date. No doubt that AOSP roms are fun, but also very unpredictable. I keep Xaiomi.EU on mi daily driver, ( the Mi8) and I tinker around with AOSP roms on my old phones.
Take care
Click to expand...
Click to collapse
Currently on miui 11 on mine, and it's perfect, like the design vs miui 10 from official, it's fast and stable, only thing is that some apps that use gps are sometimes bugged, and does your mi8 drain battery a bit faster than in miui 10?
ClaudioG123 said:
Currently on miui 11 on mine, and it's perfect, like the design vs miui 10 from official, it's fast and stable, only thing is that some apps that use gps are sometimes bugged, and does your mi8 drain battery a bit faster than in miui 10?
Click to expand...
Click to collapse
Yeah, I don't think that they have that part completely sorted yet. I definitely had better battery life on the last Xiaomi.EU Pie rom. But its not too bad with this latest version. Checking Gsam battery manager just now my average is 7HR's 6 Min SOT Whereas with the Miui 11 Xiaomi EU Chinese Stable rom, I averages about 10 hrs SOT ( If I remember correctly)
Personally, I am not having any app issues.
Usually if I had a permissions issues after restoring apps, I would just uninstall and reinstall the app and that will usually take care of any issues. Another thing to check , is t make sure that any problem apps have the right permissions enabled.
tsongming said:
Yeah, I don't think that they have that part completely sorted yet. I definitely had better battery life on the last Xiaomi.EU Pie rom. But its not too bad with this latest version. Checking Gsam battery manager just now my average is 7HR's 6 Min SOT Whereas with the Miui 11 Xiaomi EU Chinese Stable rom, I averages about 10 hrs SOT ( If I remember correctly)
Personally, I am not having any app issues.
Usually if I had a permissions issues after restoring apps, I would just uninstall and reinstall the app and that will usually take care of any issues. Another thing to check , is t make sure that any problem apps have the right permissions enabled.
Click to expand...
Click to collapse
Im using Europe instead of china, does it change? Read changelog and didnt figured it out
This app works on android 9 but on 10 it bugs didn't had the issue back with miui 10 stock
Liked the fact that they boosted sound
ClaudioG123 said:
Im using Europe instead of china, does it change? Read changelog and didnt figured it out
This app works on android 9 but on 10 it bugs didn't had+ the issue back with miui 10 stock
Liked the fact that they boosted sound
Click to expand...
Click to collapse
I am also using the Xiaomi EU rom because I want to use Android 10, and as I mentioned for me the battery life is fine. So I wouldn't recommend changing.
If you having app issues, see if there is a beta version of that app.
tsongming said:
I am also using the Xiaomi EU rom because I want to use Android 10, and as I mentioned for me the battery life is fine. So I wouldn't recommend changing.
If you having app issues, see if there is a beta version of that app.
Click to expand...
Click to collapse
Mate, you are using MIUI 10 eu latest beta pie update or stable? I curiuous your rom coz you saying you are taking good battery life.
Sorry for my bad English.
harnkalkn said:
Mate, you are using MIUI 10 eu latest beta pie update or stable? I curiuous your rom coz you saying you are taking good battery life.
Sorry for my bad English.
Click to expand...
Click to collapse
I am using the weekly Xiaomi.Eu beta rom, averaging 7 hours and 15 minutes SOT and no real issues.
mi 8 bricked
i bricked mi 8 when i try to re-lock bootloader. now i only received a main menu and red massage "this miui version can't be installed on this device". anyone can help me?
Hi,
I want to share how I recovered my Zenfone 8 from some really bad flashing, ending up with nothing more than fastboot access.
It is really simple:
Get ADB/Fastboot drivers, for example from here:
https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows
Downoad and extract this RAW image from ASUS:
https://dlcdnets.asus.com/pub/ASUS/...06D-ASUS-99.1004.0404.82-1.1.31-9999-user.zip
Turn off your phone
Reboot to fastboot mode by pressing and holding the Volume Up and Power keys simultaneously
Connect your phone to the PC
Run the flashall_AFT.cmd from the extracted archive
When finished, reboot if not already done automatically
It could happen, that the system still won't start now, but don't worry, just wait it out.
After several reboots it will offer to do a factory reset. Do it and the system will boot properly afterwards.
Regards,
Hyper
Do you believe this could help with the ram dump issue?
There is a newer raw out:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/WW-ZS590KS-30.11.51.115-MR0-user_20210826-release.zip
Blumi511 said:
Do you believe this could help with the ram dump issue?
Click to expand...
Click to collapse
I have no idea, but I think it can't get worse by trying it.
Flashing the firmware (so called "RAW"-firmware) that allows one to turn back to A11 on the A12 beta page, should get back every device back to a working condition if the problem isn't hardware or extremely messed up in the few partitions that the raw doesn't flash.
I tried using this method to get back to stock from OmniROM, but after several reboots, the phone is stuck in fastboot mode. I tried booting normally and recovery mode, and it immediately goes back to fastboot mode. Any ideas?
/Edit: Got it to boot by flashing Lineage recovery, rebooting into it, and doing a factory reset from there.
HyperCriSiS said:
Hi,
I want to share how I recovered my Zenfone 8 from some really bad flashing, ending up with nothing more than fastboot access.
It is really simple:
Get ADB/Fastboot drivers, for example from here:
https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows
Downoad and extract this RAW image from ASUS:
https://dlcdnets.asus.com/pub/ASUS/...KS-30.11.51.115-MR0-user_20210826-release.zip
Turn of your phone
Reboot to fastboot mode by pressing and holding the Volume Up and Power keys simultaneously
Connect your phone to the PC
Run the flashall_AFT.cmd from the extracted archive
When finished, reboot if not already done automatically
It could happen, that the system still won't start now, but don't worry, just wait it out.
After several reboots it will offer to do a factory reset. Do it and the system will boot properly afterwards.
Regards,
Hyper
# Thanks to NisseGurra for the link to the latest RAW image.
Click to expand...
Click to collapse
Thank you very much! This safed my phone! I stupidly flashed the boot image from a different build and wasn't able to boot. Only your flash.cmd worked! I hat to comment out the hardwareid check though, because mine was 0 somehow.
I guess I have terrible luck. My zf8 isnt getting detected on fastboot but is visible on ADB. Have a stupid issue with the playstore where it is throwing up the authentication error and isnt logging into anything. I thought ill flash the stock rom back but no joy. driver not found on device manager.
amdpcman said:
I guess I have terrible luck. My zf8 isnt getting detected on fastboot but is visible on ADB. Have a stupid issue with the playstore where it is throwing up the authentication error and isnt logging into anything. I thought ill flash the stock rom back but no joy. driver not found on device manager.
Click to expand...
Click to collapse
This could also be just an issue with the fastboot drivers. Try reinstalling them, also clearing up orphaned devices in device manager could help.
amdpcman said:
I guess I have terrible luck. My zf8 isnt getting detected on fastboot but is visible on ADB. Have a stupid issue with the playstore where it is throwing up the authentication error and isnt logging into anything. I thought ill flash the stock rom back but no joy. driver not found on device manager.
Click to expand...
Click to collapse
This is a known issue with Windows 10 computers. They have some sort of signature check where even if you install the correct drivers, they don't really get "installed" because of this check. There is a workaround for this though, I'm not sure how.
However, if you have a Win 7, Vista / 8 PC, adb and fastboot will both work flawlessly with no hassles (experienced personally).
NisseGurra said:
There is a newer raw out:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/WW-ZS590KS-30.11.51.115-MR0-user_20210826-release.zip
Click to expand...
Click to collapse
Where do you get latest RAW links from?
I could not find them via Asus site.
HyperCriSiS said:
Where do you get latest RAW links from?
I could not find them via Asus site.
Click to expand...
Click to collapse
A12 beta page. The firmware that allows you to go back to A11
NisseGurra said:
There is a newer raw out:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/WW-ZS590KS-30.11.51.115-MR0-user_20210826-release.zip
Click to expand...
Click to collapse
Is this download working for anybody? I've downloaded it twice (at 10 hours each), and both times it fails to extract. It gives a "data error" on the super.img file.
Yippee38 said:
Is this download working for anybody? I've downloaded it twice (at 10 hours each), and both times it fails to extract. It gives a "data error" on the super.img file.
Click to expand...
Click to collapse
Works for me.
is there a newer image out?
it would be good if there is a full raw android 12 image posted...since android 12 is released now.
Hi there,
Installed LineageOS 18.1 yesterday because my phone was having awkward moments, I want to go back to RAW stock, but I can't finalize the install.
I followed OP's instructions, but I never could find the flashall_AFT.cmd from the extracted archive.
Anyway, i managed to use LineageOS Recovery, but it requires signature at 47% , and when I press Yes, it says :
E:error: 21
Installing update...
E: Package is for product ASUS_I006D but expected sake.
Installation version
Installation tried : UL-I006D-ASUS-31.1004.0404.81-1.1.25-2111-user.zip.
When I tried WW-ZS590KS-30.11.51.115-MR0-user_20210826-release.zip, it required signature after 0.2 seconds, with following message :
E:footer is wrong
update package verificationtook 0.2 s (result 1).E:Signature verification failed
E:error: 21
Installing update...
E:Open failed: /metadata/ota: No such file or directory
E:Couldn't mount Metadata.
E:Failed to find update binary META-INF/com/google/android/update-binary.
I resetted before launching above operations, everytime.
What can I do to go back to Asus RAW Rom ?
Forward thanks and best regards.
EDIT : OK, found it, I just had to extract the .zip file. I thought I had to flash it like any image.
My bad.
HyperCriSiS said:
Hi,
I want to share how I recovered my Zenfone 8 from some really bad flashing, ending up with nothing more than fastboot access.
It is really simple:
Get ADB/Fastboot drivers, for example from here:
https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows
Downoad and extract this RAW image from ASUS:
https://dlcdnets.asus.com/pub/ASUS/...06D-ASUS-99.1004.0404.82-1.1.31-9999-user.zip
Turn off your phone
Reboot to fastboot mode by pressing and holding the Volume Up and Power keys simultaneously
Connect your phone to the PC
Run the flashall_AFT.cmd from the extracted archive
When finished, reboot if not already done automatically
It could happen, that the system still won't start now, but don't worry, just wait it out.
After several reboots it will offer to do a factory reset. Do it and the system will boot properly afterwards.
Regards,
Hyper
Click to expand...
Click to collapse
Thank you so much! You saved my phone! The only thing is that I couldn't find the flashall_AFT.cmd file in the new image, I had to use the WW-ZS590KS-30.11.51.115-MR0-user_20210826-release.zip, and it worked perfectly. After I flashed the boot.img trying to get root on android 12 several times, my phone was in a ram dump state.
HyperCriSiS said:
Hi,
I want to share how I recovered my Zenfone 8 from some really bad flashing, ending up with nothing more than fastboot access.
It is really simple:
Get ADB/Fastboot drivers, for example from here:
https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows
Downoad and extract this RAW image from ASUS:
https://dlcdnets.asus.com/pub/ASUS/...06D-ASUS-99.1004.0404.82-1.1.31-9999-user.zip
Turn off your phone
Reboot to fastboot mode by pressing and holding the Volume Up and Power keys simultaneously
Connect your phone to the PC
Run the flashall_AFT.cmd from the extracted archive
When finished, reboot if not already done automatically
It could happen, that the system still won't start now, but don't worry, just wait it out.
After several reboots it will offer to do a factory reset. Do it and the system will boot properly afterwards.
Regards,
Hyper
Click to expand...
Click to collapse
Thanks! This helped me after I got into a ramdump situation. I flashed a rom and a boot image through the bootloader instead of fastboot and got things corrupted.
On my Asus Zenfone 8, I upgraded from Lineage OS 18.1 to 19.1.
When I wanted to flash gapps and did a reboot into recovery, since then the device no longer works.
I can't get into recovery and I can't get into fastboot mode.
When I turn off the device and turn it on again, the following appears on the screen.
Waiting for flashing full ramdump...
PLS help me
Code:
*** Disclamer
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Introduction
This is the LineageOS 19.1 for LG G8s ThinQ
Click to expand...
Click to collapse
Installation instructions
1. Install R Stock Rom onto your phone , follow some tutorial you can find in this forum
2. Flash boot.img and dtbo.img by typing fastboot flash boot boot.img and fastboot flash dtbo_a dtbo.img and fastboot flash dtbo_b dtbo.img
3. Wipe your userdata by typing fastboot erase userdata
4. Reboot the phone and immeditly do the recovery key combination
5. In Lineageos recovery select install and then sideload from adb
6. On your computer type adb sideload pathtotheromzip and press enter
7. The rom should now be flashed , flash gapps and other mods like magisk the same way
Click to expand...
Click to collapse
Download
ROM
RECOVERY
Click to expand...
Click to collapse
Changelog
Code:
Current changelog:01.07.2022
[note] 1st Release of Lineage 19.1
[new] Android 12.1 S
[changed]
[fixed] Rom boots into OS
Older changelogs:
Click to expand...
Click to collapse
Code:
Current changelog:16.01.2021
[note] 1st Release of Lineage 18.1
[new] Android 11 R
[changed]
[fixed] Rom boots into OS
FAQ
What doesnt work ?
You tell me
This is only for G8s not for G8 also not for G8X
VOLTE DONT WORK AND IT WONT EVER WORK
For Gapps i recommend NikGapps
Click to expand...
Click to collapse
Thanks To/Credits
Code:
@SGCMarkus
Sources
Code:
[URL="https://github.com/J0SH1X/android_kernel_lge_sm8150]Kernel[/URL]
[URL="https://github.com/J0SH1X/android_device_lge_sm8150-common"]Common[/URL]
[URL="https://github.com/J0SH1X/android_device_lge_betalm"]Device[/URL]
[URL="https://github.com/J0SH1X/android_device_lge_beta-common"]Device-Common[/URL]
1st
SURPRISE ************S
thanks man
Has anyone already had the time to test it? I have set for myself, that I'm first going to finish my thesis, before loading this rom. Anyway, thanks @J0SH1X for your effort!
Its works for me, but video output dont work via usb c.
Its a kernel thing?
Does Widevine show up as L1 on DRM INFO?
eclipsek20 said:
Does Widevine show up as L1 on DRM INFO?
Click to expand...
Click to collapse
Okay, so I flashed the ROM and originally when the internet was still working checked and it displayed L3, I tried to install NikGapps (Full) and Magisk however now the internet doesnt seem to be working (and I cant connect to new wifi networks) along with the pixel launcher (Here is my logcat), I will now do a clean reflash.
eclipsek20 said:
Okay, so I flashed the ROM and originally when the internet was still working checked and it displayed L3, I tried to install NikGapps (Full) and Magisk however now the internet doesnt seem to be working (and I cant connect to new wifi networks) along with the pixel launcher (Here is my logcat), I will now do a clean reflash.
Click to expand...
Click to collapse
It seems that Wifi 5ghz doesn't work, along with that the os seems to be flimsy with dual sim once turned on the first time, however recovers when you set the defaults. Also I tried flashing magisk along with NikGApps and it doesn't seem to work, (I might've done something wrong?) anyway, I think ill just stick to my stock OS.
eclipsek20 said:
Okay, so I flashed the ROM and originally when the internet was still working checked and it displayed L3, I tried to install NikGapps (Full) and Magisk however now the internet doesnt seem to be working (and I cant connect to new wifi networks) along with the pixel launcher (Here is my logcat), I will now do a clean reflash.
Click to expand...
Click to collapse
that launcher is trying to access methods which are not provided by the os (getwindowcornerradius), idk what can i do about that
J0SH1X said:
that launcher is trying to access methods which are not provided by the os (getwindowcornerradius), idk what can i do about that
Click to expand...
Click to collapse
I guess nothing can be perfect, but thank you for making android 12 possible on this phone.
Hey @J0SH1X , thank you very much for your work! Almost everything works fine for me. Just two small things.
1. The encryption of the device does not work unfortunately. After starting the encryption it directly says "Wait while your phone is being encrypted. Time remaining 00:00". Tried it several times, and also left it encrypting over night, but it never finished (so always had to reboot the phone and than do a factory reset since the encryption was unsuccessful). Any idea or solution for that?
2. When the phone is off, and I plug in a cable to charge, the phone is (of course) rebooting after a short moment. But the touchscreen is completely not working than unfortunately, just the power and volume keys are working. So I have to reboot the phone with the revovery key combination. Any idea for that?
Happy to hear from any of you
Great work!
NikGApps kept crashing for me but BiTGApps did the trick. Enjoying the Lineage experience.
Help a noob out: I have Magisk installed, how do I gain root access? Thanks
(Edit) I tried the standard procedure from the Github repo after installing the Magisk apk directly from the phone but got stuck in a bootloop with the device that kept saying that it had to erase my data. Do I have to install from adb? Any suggestion?
There wouldn't happen to be a way to change to betalm from alphalm would there? Something similar to a cross flash or something. Lineage 19 on my G8 would be neat.
Hey @J0SH1X , and I got a second question here if you don't mind.
When the phone is off, and I plug in a cable to charge, the phone is (of course) rebooting after a short moment. But the touchscreen is completely not working than unfortunately, just the power and volume keys are working. So I have to reboot the phone with the revovery key combination. Any idea for that?
Thanks in advance
.
Thanks for your work,I am new here , I want to download a rom which is stable and power saving.