Database Develop

[SOLVED]/Help/ Update Lineage 13.0 to Lineage 15.1 GN7000

Hello guys,
I don't know if here is the good place to post. My bad and SORRY for my english, I'm french and I'm learning by myself specially in watching tv series with subtitles :fingers-crossed:
I'm currently on version Lineage 13.0-20170204-UNOFFICIAL-n7000 (6.0.1) and I would like to install OREO 8.1.0 (Lineage 15.1).
I don't want to mess up everything so I ask for help as I know I can rely on tips here.
Should I install Lineage 14 first and then move to 15? There is explanation on Updating If you are running an earlier NightOwl cm15.1 alpha version: but nothing if we are on other version. Is the cm version important here? It must be another cm15 or it works no matter version we installed? So I'm confused and after spending 1 month to recover a BLOD Nexus 5X without recovery and locked fastboot... I know I must check twice before doing anything.
So if someone can enlighten me. Thank you

Edit :
I followed Updating If you are running an earlier NightOwl cm15.1 alpha version.
When I try to flash the ROM, it end up with :
- detected filesystem ext4 for /dev/block/mmcblk0p9
- Patching system image unconditionally...
- E1001 : Failed to update system image.
- Updater process ended up with ERROR : 7
- Error installing zip file '/sdcard0/Nightowl-lineage15.1-beta2-n7000.zip
Help please. Thank you
yessade said:
Hello guys,
I don't know if here is the good place to post. My bad and SORRY for my english, I'm french and I'm learning by myself specially in watching tv series with subtitles :fingers-crossed:
I'm currently on version Lineage 13.0-20170204-UNOFFICIAL-n7000 (6.0.1) and I would like to install OREO 8.1.0 (Lineage 15.1).
I don't want to mess up everything so I ask for help as I know I can rely on tips here.
Should I install Lineage 14 first and then move to 15? There is explanation on Updating If you are running an earlier NightOwl cm15.1 alpha version: but nothing if we are on other version. Is the cm version important here? It must be another cm15 or it works no matter version we installed? So I'm confused and after spending 1 month to recover a BLOD Nexus 5X without recovery and locked fastboot... I know I must check twice before doing anything.
So if someone can enlighten me. Thank you
Click to expand...
Click to collapse

SOLVED
yessade said:
Edit :
I followed Updating If you are running an earlier NightOwl cm15.1 alpha version.
When I try to flash the ROM, it end up with :
- detected filesystem ext4 for /dev/block/mmcblk0p9
- Patching system image unconditionally...
- E1001 : Failed to update system image.
- Updater process ended up with ERROR : 7
- Error installing zip file '/sdcard0/Nightowl-lineage15.1-beta2-n7000.zip
Help please. Thank you
Click to expand...
Click to collapse
I went to WIPE-ADVANCED and format Kalvin, Cache, System and Data.
- Flash lanchon REPIT
- Flash the rom without error.
After successfully flashed the ROM, Wipe Kalvin cache and flash gApps.
After "5-7"minutes of rebooting, the phone was updated to CM15 and running smoothly.
If my post can help someone else.
Admin, this thread can be tag SOLVED.

Moto g5s xt-1799-2 rr

Managed to succesfully port Ressurection Remix (7.1) to the Moto Green Pomelo (xt1799). Rom boots and all features work apart from Fingerprint reader.
Need help with fixing fingerprint

dmilz said:
Managed to succesfully port Ressurection Remix (7.1) to the Moto Green Pomelo (xt1799). Rom boots and all features work apart from Fingerprint reader.
Need help with fixing fingerprint
Click to expand...
Click to collapse
Sorry for mb inappropriate question: Do you have a physical device? If you do, did you unlock and root it (cos i have some issues with that)?

irewer said:
Sorry for mb inappropriate question: Do you have a physical device? If you do, did you unlock and root it (cos i have some issues with that)?
Click to expand...
Click to collapse
Yes i do..
I unlocked bootloader and rooted

dmilz said:
Managed to succesfully port Ressurection Remix (7.1) to the Moto Green Pomelo (xt1799). Rom boots and all features work apart from Fingerprint reader.
Need help with fixing fingerprint
Click to expand...
Click to collapse
Have you figured the problem out yet? Is there any other known custom ROMs working on Pomelo? Also how did you do it? I don't see Montana in Downloads section for the ROM.

sixtheninth said:
Have you figured the problem out yet? Is there any other known custom ROMs working on Pomelo? Also how did you do it? I don't see Montana in Downloads section for the ROM.
Click to expand...
Click to collapse
No, i didnt get the chance to figure it out as i broke my moto screen completely. There are no custom roms for the xt-1799-2, wish i had shared it. But if you are interested you can easily port the roms for any moto g5s over to your xt-1799-2

dmilz said:
No, i didnt get the chance to figure it out as i broke my moto screen completely. There are no custom roms for the xt-1799-2, wish i had shared it. But if you are interested you can easily port the roms for any moto g5s over to your xt-1799-2
Click to expand...
Click to collapse
Yeah, I am very interested. I tried RR, LineageOS, Viper for other montanas, all crashed after boot back into bootloader. Also I'd be interested getting Oreo based ROMs. So far I m stuck with chinese ZUI 3.1 which prevents me from flashing or installing Gapps.

sixtheninth said:
So far I m stuck with chinese ZUI 3.1 which prevents me from flashing or installing Gapps.
Click to expand...
Click to collapse
You can unclock (XT1799-2 may be 'secretly' unlocked already), root your device, flash custom TWRP (escpecially for Moto G5S XT1792/1794 and Green Pomelo XT1799-2) - and then you'll be able to install Open GApps via TWRP/root.
Also you can simply open special Lenovo App Store on your ZUI-based phone (look for it carefully!), install Google Store's apk from out there - and be enjoying with any GApps and other official apk's.
sixtheninth said:
Also I'd be interested getting Oreo based ROMs.
Click to expand...
Click to collapse
If you will flash bootloader version 07 (not 06 as you have on any available ZUI stock ROMs), you'll be able to flash distinct Oreo firmware (XT1792 for Brasil/India/EU) in straight way (thread 1; thread 2). BUT YOU'RE GOING TO LOSE NFC and SELFIE-CAMERA in cause of special drivers lack!!! And you will have no way for downgrading of firmware in cause higher version bootloader.
* also you would prefer to flash Moto G5s' stock Android 7.1.1 firmaware (XT1794) on your Green Pomelo (XT1799-2), using this manual.
** stock Green Pomelo's ZUI-based Android 7.1.1 firmware you can find here

irewer said:
You can unclock (XT1799-2 may be 'secretly' unlocked already), root your device, flash custom TWRP (escpecially for Moto G5S XT1792/1794 and Green Pomelo XT1799-2) - and then you'll be able to install Open GApps via TWRP/root.
Also you can simply open special Lenovo App Store on your ZUI-based phone (look for it carefully!), install Google Store's apk from out there - and be enjoying with any GApps and other official apk's.
If you will flash bootloader version 07 (not 06 as you have on any available ZUI stock ROMs), you'll be able to flash distinct Oreo firmware (XT1792 for Brasil/India/EU) in straight way (thread 1; thread 2). BUT YOU'RE GOING TO LOSE NFC and SELFIE-CAMERA in cause of special drivers lack!!! And you will have no way for downgrading of firmware in cause higher version bootloader.
* also you would prefer to flash Moto G5s' stock Android 7.1.1 firmaware (XT1794) on your Green Pomelo (XT1799-2), using this manual.
** stock Green Pomelo's ZUI-based Android 7.1.1 firmware you can find here
Click to expand...
Click to collapse
Thanks a lot! I was unable to Flash Gapps 7.1 in TWRP due to incorrect architecture error. I see that Oreo original ROM will probably never arrive to this phone, so I'll stick to 7.1. What buzzes me the most is that there is no custom rom compatible with XT1799 without losing some of its extra functions. I wonder how hard it will be to port Lineage, RR or similar to enjoy. I've been always using custom roms and now I feel kinda left out
---------- Post added at 10:31 AM ---------- Previous post was at 10:23 AM ----------
sixtheninth said:
Thanks a lot! I was unable to Flash Gapps 7.1 in TWRP due to incorrect architecture error. I see that Oreo original ROM will probably never arrive to this phone, so I'll stick to 7.1. What buzzes me the most is that there is no custom rom compatible with XT1799 without losing some of its extra functions. I wonder how hard it will be to port Lineage, RR or similar to enjoy. I've been always using custom roms and now I feel kinda left out
Click to expand...
Click to collapse
Update, I just fastboot flashed the Firmware from the links provided, but managed to hard brick my phone!!!!!! ((( Don't know what to do now.

careful with flashing other moto g5s model roms on the xt-1799-2, its different and so you might get a brick. The best you can do is port like i said. You can unlock bootloader by "fastboot oem flashing" if that doesnt work for you try "fastboot oem unlock". I will be back on the pomelo xt-1799-2 soon as i am planning to order another one. Infact you guys will need a section dedicated to the xt-1799-2

sixtheninth said:
Thanks a lot! I was unable to Flash Gapps 7.1 in TWRP due to incorrect architecture error. I see that Oreo original ROM will probably never arrive to this phone, so I'll stick to 7.1. What buzzes me the most is that there is no custom rom compatible with XT1799 without losing some of its extra functions. I wonder how hard it will be to port Lineage, RR or similar to enjoy. I've been always using custom roms and now I feel kinda left out
---------- Post added at 10:31 AM ---------- Previous post was at 10:23 AM ----------
Update, I just fastboot flashed the Firmware from the links provided, but managed to hard brick my phone!!!!!! ((( Don't know what to do now.
Click to expand...
Click to collapse
Hope this helps to unbrick
http://motog5szuirom.blogspot.com/2018/01/zui-31-for-moto-g5s-stock-rom.html

dmilz said:
careful with flashing other moto g5s model roms on the xt-1799-2, its different and so you might get a brick. The best you can do is port like i said. You can unlock bootloader by "fastboot oem flashing" if that doesnt work for you try "fastboot oem unlock". I will be back on the pomelo xt-1799-2 soon as i am planning to order another one. Infact you guys will need a section dedicated to the xt-1799-2
Click to expand...
Click to collapse
I agree, a since it is a slightly different phone a independent section can be great. Now, I am not a developer, so things like porting ROMs is not in my skillset, but I understand that selfie cam and nfc will not work on any custom ROM even if ported simply due to driver issue. I have rooted my phone previously, so I was past unlocking. Problem was that I soft bricked moment I pressed 'factory reset' - the phone would just endlessly keep booting into recovery mode, which was strange as it had stock ROM updated by reseller into a global version. Then I tried to flash various custom ROMs without any luck. Pretty much tried any Montana ROM I could find, but as I said, I don't know how to port so I got stuck in recovery loop. Then I found out about Oreo project and tried to fastboot flash that. That was a major mistake. It upgraded bootloader to 7 without me realising this. I found out nfc and selfie camera not working, so I wanted to downgrade to stock chinese firmware and just install gapps manually. After I fastboot flashed the nougat firmware - my phone hard bricked and won't even respond it seems dead. Thus your link will not help. Anyway I am already on a mission to try to revive it using following method: https://forum.xda-developers.com/showpost.php?p=75932514&postcount=1
Thank you anyway and if by chance you stumble upon some cool compatible ROM or to be honest a ROM that works really good - I don't really need NFC, but fingerprint scanner, turbo charger, selfie camera and reasonable battery management (some ROMs apparently drain it too quickly) would surely be features to keep. Also, if you have at hand a guide on how to port these roms which I can learn, I'd be very grateful.
Thank you
Six

sixtheninth said:
Problem was that I soft bricked moment I pressed 'factory reset' - the phone would just endlessly keep booting into recovery mode ...
Click to expand...
Click to collapse
At the moment you could use TWRP menu* 'Reboot - Bootloader' to boot in Fastboot Flash Mode (yes, it's bootloader) - and then press Power button (with 'START' tag in front of it).
But you have preferred to experiment ... You lost bootloader in due of custom 'chinese suppliers' firmware (non-original ROM) and forbidden factory reset with it.
* if you had stock recovery, you need to change mode with Volume buttons to Fastboot Flash Mode - and do the next steps in the same way; also you would be able directly to boot in Fastboot mode (bootloader) using long press Power button + Volume Down button
sixtheninth said:
... Then I found out about Oreo project and tried to fastboot flash that. That was a major mistake. It upgraded bootloader to 7* without me realising this ... I wanted to downgrade to stock chinese firmware ... my phone hard bricked and won't even respond it seems dead ...
Click to expand...
Click to collapse
I warned you in straight way at that my post with a load of links to instructions and threads ('... you will have no way for downgrading of firmware in cause of higher version bootloader ...'). But you are bustler and illiterate, pardon me. By the way... do you know English or just use Google Translate?
* I have some unapproved info that OPP28.65-37[-2] firmware even uses bootloader version 12 (BL: BC12)
sixtheninth said:
Anyway I am already on a mission to try to revive it using following method: https://forum.xda-developers.com/showpost.php?p=75932514&postcount=1
Click to expand...
Click to collapse
Yes, it may be will help you to boot in Fastboot menu. Please, read all method instructions carefully (RTFM!!!), don't experiment on your own risk/luck.
On Russian forum we have some examples of 'reviving' XT1799-2 with XT1794 mmcblk0.img - but it's the question of bootloader version and disk partition. May be now you have either bootloader version 06 and partition again or corrupted/mixed software or something else, so may be you'll be need to use distinct XT1799-2 mmcblk0.img. I have it ('Repair' folder), but there aren't any proved mentions of it's compatibility / applicability / integrality - all our XT1799-2 'bricks' were re-covered with XT1794 mmcblk0.img finally.
If you know Russian language or wanna risk to translate with Google Tranlsate (omg, please, don't do that ) - you may use Russian 4pda forum because at this very moment it has the most full load of info about XT1799-2 flashing and repairing (yes, all Slavs are misers and adventurers) not in Chinese language.
dmilz, I sincerely beg your pardon for messing up in your RR port thread

irewer said:
At the moment you could use TWRP menu* 'Reboot - Bootloader' to boot in Fastboot Flash Mode (yes, it's bootloader) - and then press Power button (with 'START' tag in front of it).
But you have preferred to experiment ... You lost bootloader in due of custom 'chinese suppliers' firmware (non-original ROM) and forbidden factory reset with it.
* if you had stock recovery, you need to change mode with Volume buttons to Fastboot Flash Mode - and do the next steps in the same way; also you would be able directly to boot in Fastboot mode (bootloader) using long press Power button + Volume Down button
I warned you in straight way at that my post with a load of links to instructions and threads ('... you will have no way for downgrading of firmware in cause of higher version bootloader ...'). But you are bustler and illiterate, pardon me. By the way... do you know English or just use Google Translate?
* I have some unapproved info that OPP28.65-37[-2] firmware even uses bootloader version 12 (BL: BC12)
Yes, it may be will help you to boot in Fastboot menu. Please, read all method instructions carefully (RTFM!!!), don't experiment on your own risk/luck.
On Russian forum we have some examples of 'reviving' XT1799-2 with XT1794 mmcblk0.img - but it's the question of bootloader version and disk partition. May be now you have either bootloader version 06 and partition again or corrupted/mixed software or something else, so may be you'll be need to use distinct XT1799-2 mmcblk0.img. I have it ('Repair' folder), but there aren't any proved mentions of it's compatibility / applicability / integrality - all our XT1799-2 'bricks' were re-covered with XT1794 mmcblk0.img finally.
If you know Russian language or wanna risk to translate with Google Tranlsate (omg, please, don't do that ) - you may use Russian 4pda forum because at this very moment it has the most full load of info about XT1799-2 flashing and repairing (yes, all Slavs are misers and adventurers) not in Chinese language.
dmilz, I sincerely beg your pardon for messing up in your RR port thread
Click to expand...
Click to collapse
Well as irony had it, I did the operation literally seconds before I have read your warning. I was desperate of being stuck in either chinese rom or recovery loop. Anyway, I am amidst of transferring mmcblk0.img for XT1795 to my SD drive via Rufus. Problem is that it won't let me to choose GPT only MBR, so I hope that can still work. Another problem is that I don't how to check the actual bootloader version I am having there installed right now should I manage to get there.

sixtheninth said:
Another problem is that I don't how to check the actual bootloader version I am having there installed right now should I manage to get there.
Click to expand...
Click to collapse
The version of installed bootloader you can check in Fastboot Flash Mode (bootloader as actually, Power + Volume Down buttons pressing and so on).
The version of non-installed firmware you can find into special '.info' file, for example: file 'MONTANA_RETCN_NZS26.68-108_cid11_subsidy-DEFAULT_regulatory-DEFAULT_CFC_montana_retcn.info' inside ZUI-based MONTANA_RETCN_NZS26.68-108 ROM has this line:
Code:
MBM Version: BC.06

I used Win 10 and Rufus on XT-1799-2 using XT-1794 and 95 files, both holding power button for over 1min but screen remained black (

sixtheninth said:
I used Win 10 and Rufus on XT-1799-2 using XT-1794 and 95 files, both holding power button for over 1min but screen remained black
Click to expand...
Click to collapse
Because there were Android 7.1.1 images of mmcblk0 with corresponding partition and bootloader version (BC.07; and you may be need BC.08-BC.12 at this moment :shrugging: ).
Have you tried XT1799-2 mmcblk0.img (7.1.1)?
Have you ever found XT1794 Android 8.1.0-based mmcblk0.img ?

[/COLOR]
irewer said:
Because there were Android 7.1.1 images of mmcblk0 with corresponding partition and bootloader version (BC.07; and you may be need BC.08-BC.12 at this moment :shrugging: ).
Have you tried XT1799-2 mmcblk0.img (7.1.1)?
Have you ever found XT1794 Android 8.1.0-based mmcblk0.img ?
Click to expand...
Click to collapse
The results so far are underwhelming. I did the operation in Linux following https://forum.xda-developers.com/showpost.php?p=75932514&postcount=1 . Dowloaded both .img XT1794 and 95, checked the MD5 and flashed them on my sd card. Neither of them worked. Light was flashing at various intervals, but even after two minutes of holding the power button screen remained pitch black. I downloaded your image file for 1799-2, but ended with the very same result. I have not found XT1794 Android 8.1.0-based mmcblk0.img, yet. Would you know anything about it?

1799-2
Hello. I installed OREO 8.1 on MOTO 1799-22. The front camera and NSF do not work. No one will tell you the solution? Thank you friends.

nikolaiderho said:
Hello. I installed OREO 8.1 on MOTO 1799-22. The front camera and NSF do not work. No one will tell you the solution? Thank you friends.
Click to expand...
Click to collapse
But did you recover it from hard brick by using mmcblk0.img based on Oreo?

Have you done with your RR port for xt1799 yet?
I have purchased the xt1799 Green Pomelo,unlocked bootloader,and installed the twrp. I tried to flash many 7.1 Roms that were intended for g5s and always failed. please notify me if you are still working on the port.

Data security and phone encryption. Miui custom rom

My new MI8 SE is not my daily use, so I got time to check all available MIUI custom rom (eu,Globe,MiRum,Miuipro,Ros,MS and Masik 1.8.)
At this point no problem, they install very well and they answer my needs.
BUT:
AS EVERYBODY should know that it is very easy to delete the central Password and finger print by the mean of our sophisticated tool (I mean TWRP).
In order to be safe '(without turning back to stock rom) I tried to encrypt the phone WITHOUT success...
Process failed every time with different results (full reset, logo loop for hours, partial encrypt for data only). But was always the point that minimum security can't be reached!
Question:
-Can you well sleep If you mind that you are having all your precious data available in the wind as soon your phone is lost or stolen or even worst let in some bad friends hands...? It takes 1 mn to delete the file without any computer.
I see a partial solution by installing afterward a stock recovery that does allow to trick the system file.
(If somebody has it, I am available to test this option, but don't tell me to flash a stock rom as solution!!)
Your comments/solutions are welcome.

You can have encryption with custom ROM, if the corresponding kernel enabled built-in force encryption.
I'm currently running phh treble 9.0 encrypted, with stock kernel patched by this script:
https://forum.xda-developers.com/an...rceencrypt-t3817389/post77572812#post77572812

NexusRunner said:
You can have encryption with custom ROM, if the corresponding kernel enabled built-in force encryption.
I'm currently running phh treble 9.0 encrypted, with stock kernel patched by this script:
https://forum.xda-developers.com/an...rceencrypt-t3817389/post77572812#post77572812
Click to expand...
Click to collapse
Thanks for taking care of my post.
This is old now.
I've investigated a bit more and found ways to get MIUI custom ROM encrypted. (for now I want to stay with MIUI stuff!)
I know that almost all AOSP like rom may well encrypt from first install.
My aim was and is still to warn people that without encrypt their phone are open like a lost book.
Thanks for the very interesting and documented thread (link) you directed me to.

lolo9393 said:
Thanks for taking care of my post.
This is old now.
I've investigated a bit more and found ways to get MIUI custom ROM encrypted. (for now I want to stay with MIUI stuff!)
I know that almost all AOSP like rom may well encrypt from first install.
My aim was and is still to warn people that without encrypt their phone are open like a lost book.
Thanks for the very interesting and documented thread (link) you directed me to.
Click to expand...
Click to collapse
If you don't mind could you post a detailed guide to flash our Mi 8 Se. I tried once and got mine hard bricked and i'm scared to try again.
Our forum lacks detailed instruction and it's all hit and trial. And since you have had your hands dirty, could you do that?

me_death said:
If you don't mind could you post a detailed guide to flash our Mi 8 Se. I tried once and got mine hard bricked and i'm scared to try again.
Our forum lacks detailed instruction and it's all hit and trial. And since you have had your hands dirty, could you do that?
Click to expand...
Click to collapse
The process do not differ from other XIAOMI phone and is available at main forums.
Exemple:
https://xiaomi.eu/community/threads/9-1-24-26.48919/
or here
http://en.miui.com/search.php?mod=f...hsubmit=yes&kw=how+to+flash+custom+rom&month=
If you have specific issue with flashing process you are allowed to post in order to get support.

lolo9393 said:
The process do not differ from other XIAOMI phone and is available at main forums.
Exemple:
https://xiaomi.eu/community/threads/9-1-24-26.48919/
or here
http://en.miui.com/search.php?mod=f...hsubmit=yes&kw=how+to+flash+custom+rom&month=
If you have specific issue with flashing process you are allowed to post in order to get support.
Click to expand...
Click to collapse
Thanks Could you just point me the recovery you're using? that would be great, like exact recovery. I backed up my rom and then while restoring my device, it got hard bricked. :silly:

me_death said:
Thanks Could you just point me the recovery you're using? that would be great, like exact recovery. I backed up my rom and then while restoring my device, it got hard bricked. :silly:
Click to expand...
Click to collapse
Available MI8 SE are located here:
https://drive.google.com/drive/folders/1IeCtb6vRO4CRe76s0BD_5TQiSnymPBTT
Just take care to flash latest 1227 version after EU rom older than 8.12.20 date.
In my view it's a mistake to backup anything with TWRP because as of today nothing is stable. Better to stay with MIUI backup and computer duplication.

lolo9393 said:
Available MI8 SE are located here:
https://drive.google.com/drive/folders/1IeCtb6vRO4CRe76s0BD_5TQiSnymPBTT
Just take care to flash latest 1227 version after EU rom older than 8.12.20 date.
In my view it's a mistake to backup anything with TWRP because as of today nothing is stable. Better to stay with MIUI backup and computer duplication.
Click to expand...
Click to collapse
Thank you so much for all the help.

lolo9393 said:
Available MI8 SE are located here:
https://drive.google.com/drive/folders/1IeCtb6vRO4CRe76s0BD_5TQiSnymPBTT
Just take care to flash latest 1227 version after EU rom older than 8.12.20 date.
In my view it's a mistake to backup anything with TWRP because as of today nothing is stable. Better to stay with MIUI backup and computer duplication.
Click to expand...
Click to collapse
I tried EU rom again. This time i flashed TWRP 1227, then cleared my data, flashed rom and then flashed TWRP again and still i'm stuck at fastboot. I got my phone up running using MiFlash but i can't seem to run EU rom :crying:

me_death said:
I tried EU rom again. This time i flashed TWRP 1227, then cleared my data, flashed rom and then flashed TWRP again and still i'm stuck at fastboot. I got my phone up running using MiFlash but i can't seem to run EU rom :crying:
Click to expand...
Click to collapse
What EU rom did you install?
This doesn't work with STABLE version. Only DEV EU rom
like latest 9.2.24/25

me_death said:
I tried EU rom again. This time i flashed TWRP 1227, then cleared my data, flashed rom and then flashed TWRP again and still i'm stuck at fastboot. I got my phone up running using MiFlash but i can't seem to run EU rom :crying:
Click to expand...
Click to collapse
9. What EU rom did you install?
This doesn't work with STABLE version. Only DEV EU rom
like latest 9.2.14

lolo9393 said:
What EU rom did you install?
This doesn't work with STABLE version. Only DEV EU rom
like latest 9.2.24/25
Click to expand...
Click to collapse
I tried installing
https://xiaomi.eu/community/threads/9-2-14-15.49206/
Version: WEEKLY 9.2.15

me_death said:
I tried installing
https://xiaomi.eu/community/threads/9-2-14-15.49206/
Version: WEEKLY 9.2.15
Click to expand...
Click to collapse
That's OK!
you flash 9.2.15 with TWRP 1102 or 1217.
YOU DON't REBOOT THE ROM.
you flash twrp 1227 and THEN you reboot the rom and wait install finish, take some time be partient.
simple!

lolo9393 said:
That's OK!
you flash 9.2.15 with TWRP 1102 or 1217.
YOU DON't REBOOT THE ROM.
you flash twrp 1227 and THEN you reboot the rom and wait install finish, take some time be partient.
simple!
Click to expand...
Click to collapse
Finally i got it working following your instructions on the MIUI EU forum. Thanks a bunch. :victory: :highfive:
To others for reference. Following are the procedures that i followed to boot up Miui Eu :silly:
- Flash official 8.12.13 (Dev Fastboot Rom) through MiFlash.
- Flash TWRP 1102
- Clean Data
- Push/ Copy and Flash 8.12.20( EU Rom), it booted up finally without redirecting to Fastboot.
- Update 8.12.20 to latest available from system updater.
- Now there won't be any recovery or we aren't able to enter into available recovery even though the system boots.
- Flash TWRP 1227.

GSI Questions

sorry if these are noob questions, however GSI's and custom roms confuse me, and I really don't want to brick my phone on accident
Preface:
I have a rooted moto g6 with an unlocked bootloader that supports project treble. as per getprop ro.treble.enabled running pie 29.55-24 Software channel Retail US
1. Can I flash a GSI on my phone
2. Where is there a good guide on how to flash a gsi
3. Will it factory reset my phone
4, Is there anything I should do beforehand
5. Are there any GSI's I can't flash
(What I think is 1:yes 2:If i knew i wouldn't be here 3:yes 4:backup system images 5: Yes
Thanks

Android Adam said:
sorry if these are noob questions, however GSI's and custom roms confuse me, and I really don't want to brick my phone on accident
Preface:
I have a rooted moto g6 with an unlocked bootloader that supports project treble. as per getprop ro.treble.enabled running pie 29.55-24 Software channel Retail US
1. Can I flash a GSI on my phone
2. Where is there a good guide on how to flash a gsi
3. Will it factory reset my phone
4, Is there anything I should do beforehand
5. Are there any GSI's I can't flash
(What I think is 1:yes 2:If i knew i wouldn't be here 3:yes 4:backup system images 5: Yes
Thanks
Click to expand...
Click to collapse
There are different types of treble devices you know. Only a couple GSI work on the g6.
GSI is a system image, so usually flash with fastboot.
Fastboot flash system system.img
Or in TWRP with the "install image" option.
The G6 does not have a b partition. So only try ones that say "arm A only". Meaning arm, not arm 64, and a - only, not a/b.
There is an entire section of this site devoted to it. Search "Project Treble". Without the quotes obviously
Here you go
https://forum.xda-developers.com/project-treble
Better yet here ya go
Built for the g6.
All GSIs are generic system images, so technically they can Flash on any device that has treble (with the correct CPU architecture and partitioning scheme) but when one gets built for your device most of the bugs have been worked out

madbat99 said:
There are different types of treble devices you know. Only a couple GSI work on the g6.
GSI is a system image, so usually flash with fastboot.
Fastboot flash system system.img
Or in TWRP with the "install image" option.
The G6 does not have a b partition. So only try ones that say "arm A only". Meaning arm, not arm 64, and a - only, not a/b.
There is an entire section of this site devoted to it. Search "Project Treble". Without the quotes obviously
Here you go
https://forum.xda-developers.com/project-treble
Better yet here ya go
Built for the g6.
All GSIs are generic system images, so technically they can Flash on any device that has treble (with the correct CPU architecture and partitioning scheme) but when one gets built for your device most of the bugs have been worked out
Click to expand...
Click to collapse
Thank you so much. I installed Lineage OS from https://forum.xda-developers.com/pr...i-lineageos-16-0-gsi-arm64-ab-how-to-t3908029 and my phone is working HOWEVER I can't read battery usage from setting but /data/system/batterystats.bin exists

Android Adam said:
Thank you so much. I installed Lineage OS from https://forum.xda-developers.com/pr...i-lineageos-16-0-gsi-arm64-ab-how-to-t3908029 and my phone is working HOWEVER I can't read battery usage from setting but /data/system/batterystats.bin exists
Click to expand...
Click to collapse
I would try the one I linked to. It is the most likely to have everything working. Descendant two dot two
The one you're trying to use says it's extremely specific to his device. Majorly buggy for others. Including A only devices.

Android Adam said:
Thank you so much. I installed Lineage OS from https://forum.xda-developers.com/pr...i-lineageos-16-0-gsi-arm64-ab-how-to-t3908029 and my phone is working HOWEVER I can't read battery usage from setting but /data/system/batterystats.bin exists
Click to expand...
Click to collapse
Did you ever manage to get battery to work? Mine doesn't either nor does the USB-C port

Sorry I need help installing the ROM GSi RR I get an error in the text of insufficient space and I get error 70 to someone else happens? And I tried to fix the problem and when I managed to install the gapps the phone did not start someone can help me?

ACM1PT said:
Sorry I need help installing the ROM GSi RR I get an error in the text of insufficient space and I get error 70 to someone else happens? And I tried to fix the problem and when I managed to install the gapps the phone did not start someone can help me?
Click to expand...
Click to collapse
Please link to the rom so I can try to help. describe what you're trying to do

Android Adam said:
Please link to the rom so I can try to help. describe what you're trying to do
Click to expand...
Click to collapse
Could you give me a guide on how to install with gapps? Sorry I have to write in English everything I did my language is Spanish sorry

ACM1PT said:
Could you give me a guide on how to install with gapps? Sorry I have to write in English everything I did my language is Spanish sorry
Click to expand...
Click to collapse
I need to know which rom you are using. Please post a link to it. Is this it https://www.google.com/amp/s/forum....urrection-remix-v7-0-arm64-32-b-t3891636/amp/

Android Adam said:
I need to know which rom you are using. Please post a link to it. Is this it https://www.google.com/amp/s/forum....urrection-remix-v7-0-arm64-32-b-t3891636/amp/
Click to expand...
Click to collapse
Are you using Oreo or pie

Android Adam said:
Are you using Oreo or pie
Click to expand...
Click to collapse
pie bro,
I will try to install again have it happen

ACM1PT said:
pie bro,
I will try to install again have it happen
Click to expand...
Click to collapse
I found the problem. The system partition is too small so GApps always fails. To solve it go to twrp adb push your rom, and flash it. Then go to format then system hit repair then resize and confirm. Of you are flashing a big GApps (Super) do it again. Flash GApps then Magisk (for root) then you're done

[GUIDE] Install LineageOS 20 on SM-T290 and SM-T295 with Google Apps (MindTheGapps)

Install LineageOS 20 on SM-T290 and SM-T295 with Google Apps (MindTheGapps)​
* Your warranty is now void. (It might already been)
* I am not responsible for any damage that it may do to your device. I WARNED YOU
* It's your choice to do it. Not mine. I just made it as I wanted to do it, but you have the choice to do so. If you choose to do it, you know that it may have consequences.
Click to expand...
Click to collapse
WARNING! This won't work on a bootloader with version U4! Flashing won't work and so you will not be able to use this guide. Unfortunately, you can also currently not downgrade the bootloader, making it impossible to get any custom stuff (custom recovery, custom ROM, etc.) on your device...
Hello there! This is another guide from me here on XDA Developers! Today, I will show you how to install LineageOS 20 on an SM-T290 and SM-T295, and yes, it works on both! Let's get started:
Prerequisites​But first, make sure you have all of this:
An SM-T290 or SM-T295 tablet
TWRP (v3.7.0 recommended for SM-T290 and v3.5.2 for SM-T295)
Unlocked bootloader
1. Download LineageOS 20 ZIP from here (There stands it is for gtowifi, but it also works on the LTE model).
2. Choose the nightly build for the ZIP, it is very stable even though it is nightly.
3. OPTIONAL BUT I DO NOT RECOMMEND: You could also choose the recovery, but that's more like the stock recovery and I recommend you to keep TWRP as it has better features.
4. Download the ZIP that has the format 'lineage-20.0-YYYYMMDD-nightly-gtowifi-signed.zip'
- OPTIONAL: Download the recovery image for LineageOS 20 with the format 'lineage-20.0-YYYYMMDD-recovery-gtowifi.img'.
5. Download MindTheGapps from here.
6. Choose the one with the format 'MindTheGapps-13.0.0-arm64-YYYYMMDD_BBBBBB.zip'
7. Follow the links to download the ZIP file.
8. Place the LineageOS and MindTheGapps ZIP to an SD card or USB drive. If you choose to also take LineageOS recovery, you will also need to place the .IMG to an SD card or USB drive.
9. Insert the SD card or USB drive into your tablet.
10. Boot the device into TWRP.
11. Go to 'Wipe' > 'Swipe to Wipe'.
12. Then go once again to 'Wipe' > 'Format data' > 'Swipe to format'.
13. Go to install, make sure that it is not install image but as flash ZIP!
14. Use the select storage button to choose the storage where the ZIPs are saved.
15. Choose the LineageOS 20 ZIP and swipe to install.
16. Wait until it is done and now install MindTheGapps.
17. Optional step (depending on whether you have the following things):
- Install Magisk (root) ZIP if you have it. You could also do this later on.
- Install LineageOS recovery ZIP if you have chosen to use it. This can also be done later.
17. Click on 'Reboot system' or go to 'Reboot' > 'System'.
18. Wait until the boot is done.
19. Go through the setup, but WAIT! First read the step below.
20. Depending on whether you have LineageOS recovery or TWRP, you need to enable the option 'Auto-update LineageOS Recovery/LOS Recovery' in the setup if you have LineageOS/LOS Recovery and disable that if you have TWRP.
21. Once the setup completed, you are done!

That was easy to follow. Thank you.

Heeni said:
That was easy to follow. Thank you.
Click to expand...
Click to collapse
No problem!

Heeni said:
That was easy to follow. Thank you.
Click to expand...
Click to collapse
Nice. Guess you have LineageOS 20 right now.

Minionguyjpro said:
Nice. Guess you have LineageOS 20 right now.
Click to expand...
Click to collapse
Yes. I was previously running a GSI, but I like this better.
I'm not using Gapps, so I just skipped para. 16. I did install Magisk.
Does OTA update work with TWRP, or only with Lineage recovery?

Heeni said:
Yes. I was previously running a GSI, but I like this better.
I'm not using Gapps, so I just skipped para. 16. I did install Magisk.
Does OTA update work with TWRP, or only with Lineage recovery?
Click to expand...
Click to collapse
It does work with TWRP. It uses an OpenRecoveryScript. If you have Gapps (which you don't have), you need to reflash them afterwards. Also Magisk needs to be reflashed, but it is much easier to do than the stock!

How does this tablet with LineageOS work now?
Has it become more responsive than the original Samsung ROM or does it continue to suffer from the same exasperating slowness that characterized it?

dequadim said:
How does this tablet with LineageOS work now? Has it become more responsive than the original Samsung ROM or does it continue to suffer from the same exasperating slowness that characterized it?
Click to expand...
Click to collapse
I'm not sure, but it has some good features though. Some parts are a bit buggy, but most are not. It's also much faster.

Hello, thank you for the installation guide. Used my T290 and everything was working perfectly fine... I then decided to use LineageOS for MicroG and also everything ist working...
LineageOS 20 for MicroG:
gtowifi
My other SM-T295 is now on Bootloader5 (T295XXS5CWA1) so I think there is no way anymore to get LineageOS 20 on it. I now ordered a "new" SM-T295, which is supposed to be on Android 9. When I use the Guide above, is the cellular modul and LTE working with the CustomRom? Or should I use the GSI? Why is it such a different between those two devices?

SGX22 said:
Hello, thank you for the installation guide. Used my T290 and everything was working perfectly fine... I then decided to use LineageOS for MicroG and also everything ist working...
LineageOS 20 for MicroG:
gtowifi
My other SM-T295 is now on Bootloader5 (T295XXS5CWA1) so I think there is no way anymore to get LineageOS 20 on it. I now ordered a "new" SM-T295, which is supposed to be on Android 9. When I use the Guide above, is the cellular modul and LTE working with the CustomRom? Or should I use the GSI? Why is it such a different between those two devices?
Click to expand...
Click to collapse
Hello there! LTE will not be included, but you have 2 workarounds:
Make a hotspot over Wi-Fi with your phone or any other SIM device
Use the GSI ROM, which may have support
Well, LTE doesn't work, because of this: LineageOS is made on base of the drivers and packages of the device. And, they are almost the same I think, that's why the other stuff will or should work. But, the SM-T295 also has a driver and/or package for the SIM, LTE and so. And because it was originally made for the SM-T290, instead of an SM-T295, it will not include those drivers and so the support for it. You could try a GSI, although I had issues with it. But I may have done it wrong or so.., I always say: if there is an official custom ROM, use that over GSI, because it was really made for the device and includes the drivers and packages for the device. Although I don't really know whether GSI is bad, it may also work correctly..., if you try GSI, and it doesn't work, you could take a look at this: https://forum.xda-developers.com/t/gsi-lte-fix.3925151/

dequadim said:
How does this tablet with LineageOS work now?
Has it become more responsive than the original Samsung ROM or does it continue to suffer from the same exasperating slowness that characterized it?
Click to expand...
Click to collapse
In my opinion it is much faster and very responsive. It is really an improvement!

SGX22 said:
In my opinion it is much faster and very responsive. It is really an improvement!
Click to expand...
Click to collapse
Well, I will install it as soon as I can.

I flashed TWRP on my T295 But unfortunately i got this eroor SECURE CHECK FAIL : recovery.img)

nima2005com said:
I flashed TWRP on my T295 But unfortunately i got this eroor SECURE CHECK FAIL : recovery.img)
Click to expand...
Click to collapse
That's I think because your bootloader version is 4 or higher, instead of 3..., this updates after an update, and it can also not be downgraded for now. Bootloader version 3 has not got this protection that disallows flashing custom things like TWRP. Bootloader version 4 and higher do have...

Minionguyjpro said:
That's I think because your bootloader version is 4 or higher, instead of 3..., this updates after an update, and it can also not be downgraded for now. Bootloader version 3 has not got this protection that disallows flashing custom things like TWRP. Bootloader version 4 and higher do have...
Click to expand...
Click to collapse
ok i haved installed this rom on T295 Android 9 Bootloader 3 And everything works .Thanks for making this awesome rom . the only bug i noticed is low brightness . i think oneui max brightness was higher than this rom

nima2005com said:
ok i haved installed this rom on T295 Android 9 Bootloader 3 And everything works .Thanks for making this awesome rom . the only bug i noticed is low brightness . i think oneui max brightness was higher than this rom
Click to expand...
Click to collapse
Note: as i experienced you cant install Twrp on android 10 bootloader 3

nima2005com said:
I flashed TWRP on my T295 But unfortunately i got this eroor SECURE CHECK FAIL : recovery.img)
Click to expand...
Click to collapse
You can repair it quickly. Please search on youtube.

Deleted, need to search some further to make sure it is correct...

nima2005com said:
ok i haved installed this rom on T295 Android 9 Bootloader 3 And everything works .Thanks for making this awesome rom . the only bug i noticed is low brightness . i think oneui max brightness was higher than this rom
Click to expand...
Click to collapse
Hello, I ordered a "new" T295 with Android 10, but it is T295XXU4BUD3 as well, like my old T295. Is there still no way to get LineageOS on it.
I must say I am very disappointed now. I tried so many things bought 3!!! Devices.. It is just to much work to get LineageOS on a tablet. Is there any (small Tablet) that I can put LineageOS on with LTE which is working. Man, I am trying this for 2 years now..... What about Sony Tablets?

SGX22 said:
Hello, I ordered a "new" T295 with Android 10, but it is T295XXU4BUD3 as well, like my old T295. Is there still no way to get LineageOS on it.
I must say I am very disappointed now. I tried so many things bought 3!!! Devices.. It is just to much work to get LineageOS on a tablet. Is there any (small Tablet) that I can put LineageOS on with LTE which is working. Man, I am trying this for 2 years now..... What about Sony Tablets?
Click to expand...
Click to collapse
Well, an old Samsung Galaxy Tab 4 with LineageOS 18.1 (Android 11). I helped someone today to get it on his device! It was very easy to do, so.