The zip contains flashone 2.0 and inside is the rom qfil that is called Qf722.zip.
I'll do the manual, but basically the same as with 720
https://mega.nz/#!hCgnQSCA!OW-Q4cyCd_2-Etm6nZRxz9M0FvvaKPpBAmJ7aknLN1o
Greetings.
BASIC INSTRUCTIONS
The file Qfil.zip must unzip it in the root of the hard disk.
Example: If the root is C: it should be C:\Qfil
Inside the Qfil folder is flashone 2.0 and the rom qfil Qf722.zip
Do not modify anything, just run as administrator main.exe that is inside the Qfil folder, and select the rom qfil that is inside the Qfil folder.
This always works so do not ask if the Qfil folder is not in the root, or if the rom qfil is not in the qfil folder.
Here I will put the manual, but it is very easy, unzip in the root of the computer, execute main.exe, in flash type "Qualcomm flash dead phone, press refresh, port 9008 must appear, and in select file select Qf722.zip
Then they give it to flash and wait.
The first time takes a little, because you have to unzip the rom, but for successive times, when asked if they want to decompress again they say no and go straight to flashing.
The decompression takes a little, but the flashing is fast, then you just have to press the power button a moment and the terminal turns on, with the development rom or in recovery.
They already do what they want, the bootloader is unlocked, they can flash what they want, or if they want an official rom like 26S through the recovery renaming the rom to update.zip.
Greetings.
---
Thanks bro!!!. I test at nigth.
Here is a good tutorial by tsongming:
https://forum.xda-developers.com/showpost.php?p=77688748&postcount=2
Thank you FJV,
I'll try tomorrow, it's too late for me..
Worked for me flawlessly.
Thank you so much F.J.V!!!
433Mhz said:
Worked for me flawlessly.
Thank you so much F.J.V!!!
Click to expand...
Click to collapse
Please explain briefly and which recovery and rom are you installing.
Can you tell more? Have efs good? What eui its working on default?
bppjenil said:
Please explain briefly and which recovery and rom are you installing.
Click to expand...
Click to collapse
The Rom is a development that only serves as a test. The recovery that installs is the official of leeco.
By fastboot you can install the rom you want, but my advice is to install TWRP, and with this the rom you want, unless you want to put an official rom leeco. In that case the flash by fastboot or with the stock recovery.
Greetings.
Guys here you have lot of custom ROMs, don't use stock one because it's old and trash:
https://forum.xda-developers.com/le-pro3/development
Here is the latest TWRP 3.2.3-0 for up to Oreo builds:
https://eu.dl.twrp.me/zl0/
I have tried almost all the ROMs from above link and if someone need any help just ask.
For a beggining I would recommend you Lineage 15.1 build from 05.09.2018 because it's most stable, you can download it from here and just flash it in TWRP 3.2.3-0 with Pico Gapps and Magisk 17.1:
https://mirrorbits.lineageos.org/full/zl1/20180905/lineage-15.1-20180905-nightly-zl1-signed.zip
I have the problem of memory.
the phone does not turn off
Probably because it's development ROM. Flash stock ROM and than do factory reset to recover memory and after flash Batyan 01D development ROM so you could unlock bootloader. After that unlock your bootloader and flash TWRP 3.2.3-0, flash 20s firmware and after that flash some custom ROM.
EDIT: As reported later there is no need to flash stock ROM to recover memory, just do factory reset. Because bootloader is unlocked in development ROM there is no need to unlock it, just proceed to flashing TWRP 3.2.3-0, firmware 20s and custom ROM of your choice.
Re: saludo
Al final lo has conseguido eres un campeon ha sido un año largo para nosotros gracias por ello at the end you have got a champion it has been a long year for us thank you for it
MnMchill said:
Guys here you have lot of custom ROMs, don't use stock one because it's old and trash:
https://forum.xda-developers.com/le-pro3/development
Here is the latest TWRP 3.2.3-0 for up to Oreo builds:
https://eu.dl.twrp.me/zl0/
I have tried almost all the ROMs from above link and if someone need any help just ask.
For a beggining I would recommend you Lineage 15.1 build from 05.09.2018 because it's most stable, you can download it from here and just flash it in TWRP 3.2.3-0 with Pico Gapps and Magisk 17.1:
https://mirrorbits.lineageos.org/full/zl1/20180905/lineage-15.1-20180905-nightly-zl1-signed.zip
Click to expand...
Click to collapse
Do we have to install "firmware-20S-X722-le_zl0" before installing Lineage OS? It's only 45mb
Which is the best ROM for battery life right now?
I'm getting "failed to mount /vendor" error all the time. Can't format storage, can't install roms
My device has been dead since June.
MnMchill said:
Probably because it's development ROM. Flash stock ROM and than do factory reset to recover memory and after flash Batyan 01D development ROM so you could unlock bootloader. After that unlock your bootloader and flash TWRP 3.2.3-0 and after that flash some custom ROM.
Click to expand...
Click to collapse
I have only restored, perfect memory.
the phone does not turn off when the charger is inserted
433Mhz said:
Do we have to install "firmware-20S-X722-le_zl0" before installing Lineage OS? It's only 45mb
Which is the best ROM for battery life right now?
I'm getting "failed to mount /vendor" error all the time. Can't format storage, can't install roms
My device has been dead since June.
Click to expand...
Click to collapse
Yes, you must flash 20s firmware before flashing Lineage 15.1.
Did you flashed TRWP 3.2.3-0? Best battery life have Lineage up to 05.09.2018 ROM. You are getting that Vendor partition error because you are trying to flash new Lineage and it's treble so it's needs to be flashed twice to work and doesn't have good battery life and that will be fixed in next build. That's why I'm telling you to flash Lineage 15.1 20180905 and not latest Lineage 15.1 but you probably don't read so READ what I'm writing please.
---------- Post added at 09:47 PM ---------- Previous post was at 09:42 PM ----------
ste73 said:
I have only restored, perfect memory.
the phone does not turn off when the charger is inserted
Click to expand...
Click to collapse
So you just did factory reset and your memory recovered, you didn't have to flash stock ROM to be able to recover memory, just to clear that?
As for your screen not turning of it's because it's development ROM. Development ROMs are not intended for use, they are for testing so flash some traditional ROM.
MnMchill said:
Yes, you must flash 20s firmware before flashing Lineage 15.1.
Did you flashed TRWP 3.2.3-0? Best battery life have Lineage up to 05.09.2018 ROM. You are getting that Vendor partition error because you are trying to flash new Lineage and it's treble so it's needs to be flashed twice to work and doesn't have good battery life and that will be fixed in next build. That's why I'm telling you to flash Lineage 15.1 20180905 and not latest Lineage 15.1 but you probably don't read so READ what I'm writing please.
Click to expand...
Click to collapse
I put on GizROM 1.0 after running root and twrp 3.2.2.0
MnMchill said:
Yes, you must flash 20s firmware before flashing Lineage 15.1.
Did you flashed TRWP 3.2.3-0? Best battery life have Lineage up to 05.09.2018 ROM. You are getting that Vendor partition error because you are trying to flash new Lineage and it's treble so it's needs to be flashed twice to work and doesn't have good battery life and that will be fixed in next build. That's why I'm telling you to flash Lineage 15.1 20180905 and not latest Lineage 15.1 but you probably don't read so READ what I'm writing please.
---------- Post added at 09:47 PM ---------- Previous post was at 09:42 PM ----------
So you just did factory reset and your memory recovered, you didn't have to flash stock ROM to be able to recover memory, just to clear that?
As for your screen not turning of it's because it's development ROM. Development ROMs are not intended for use, they are for testing so flash some traditional ROM.
Click to expand...
Click to collapse
Thanks, the problem also was the TWRP version. I took the one from the Lineage OS 15.1 thread. It worked with the regular one that you linked to.
No problem, glad you solved it. If someone need any more help just ask and please hit that thumb up button if you find any of my posts helpful. Now you all enjoy in your unlocked phones and you should buy @F.J.V some more beer if you haven't already. Good luck!
---------- Post added at 10:05 PM ---------- Previous post was at 09:59 PM ----------
ste73 said:
I put on GizROM 1.0 after running root and twrp 3.2.2.0
Click to expand...
Click to collapse
Why would you use such an old ROM and old TWRP, you have link for newer ROMs(Oreo at least) and TWRP 3.2.3-0 in links I posted above? Nevermind, do whatever you want...
Related
I am about to unlock the bootloader but im confused about the TWRP flashing...
I went through the newbie guide and see that we have flash Universal Boot Img Patcher (UBP) after flashing MIUI Recovery ROM Zip
I am confused about the MIUI Recovery ROM Zip... Which ROM is that.??
I am currently on MIUI Global 8.0 Stable (8.0.6.0). Can i just unlock bootloader and flash TWRP and Supersu
Please someone help me with step by step guide to unlock and root this phone...(Unlocking Moto seems easy)
$lim $hady said:
I am about to unlock the bootloader but im confused about the TWRP flashing...
I went through the newbie guide and see that we have flash Universal Boot Img Patcher (UBP) after flashing MIUI Recovery ROM Zip
I am confused about the MIUI Recovery ROM Zip... Which ROM is that.??
I am currently on MIUI Global 8.0 Stable (8.0.6.0). Can i just unlock bootloader and flash TWRP and Supersu
Please someone help me with step by step guide to unlock and root this phone...(Unlocking Moto seems easy)
Click to expand...
Click to collapse
you can try to unlock directly at your current stable rom, somebody able to do it while i can't do it and should move to dev rom to unlock.
if you failed to do it at current rom, you can move to dev rom using miflash and ofc using fastboot rom. if you should move to dev rom to unlock, choose LP rom since MM rom have forced encryption feature by default.
OK.. suppose now I unlocked the bootloader... wat should I do to flash twrp and root the phone.. should I just flash tarp and supersu or should I need to flash anything else... please help me step by step after unlocking bootloader...
follow lolipop unlock process Replace emmc_appsboot.mbn in dev rom and flash via mi flash done,
fastboot oem unlock-go
fastboot flash recovery recovery name.img
then flash radon latest marshmallow version and then flash supersu 2.76 done, its work for me,
$lim $hady said:
I am about to unlock the bootloader but im confused about the TWRP flashing...
I went through the newbie guide and see that we have flash Universal Boot Img Patcher (UBP) after flashing MIUI Recovery ROM Zip
I am confused about the MIUI Recovery ROM Zip... Which ROM is that.??
I am currently on MIUI Global 8.0 Stable (8.0.6.0). Can i just unlock bootloader and flash TWRP and Supersu
Please someone help me with step by step guide to unlock and root this phone...(Unlocking Moto seems easy)
Click to expand...
Click to collapse
This may give you method for rooting...
And for installing cm13 ROM too... With proof...
It worked for me .. I did the same...
First
download the required files from the given link: [50mb]
https://mega.nz/#!1NhDTQoR!cP7vrchwswOfj3oHQ5saZ2d0JkcmunEn5pqyOcpZDoE
INSTRUCTIONS: [redmi note 3]
1. Get into fastboot mode. Charge the phone first. Hold the power button and the volume down button simultaenously.
2. If you can open your current rom, open developer options by clicking on the build no several times in the about phone menu in settings. and select allow oem unlocking and usb debugging.
3. if not leave it... go on and connect your phone to the PC while in fastboot mode.
BUT, before that: open Command prompt on your PC. (search it on the search box). right click on it and open it in administrator mode.
type in: bcdedit /set testsigning on
hit enter and restart your pc
(this is imp.)
4. open the zip file and extract the contents. open the boot edl mode folder and click the edl.bat file. allow it to run.
5. now screen will turn black, do not disturb it. Now flash the twrp by running flash twrp.bat from the 'flash TWRP' folder.
6. Now go to Unlock folder and run the unlock bootloader.bat file.
your phone will boot into the TWRP recovery mode automatically.
if it opens in chineese you select every tab and find the globe icon.
if the globe icon is found on any of the tab select it and change the language to ENGLISH.
wipe your system from the wipe tab:
Now download the latest CM13 SNAPSHOT BUILD ROM FOR YOUR REDMI:
https://download.cyanogenmod.org/get/kenzo-snapshot.zip
and GAPPS:
http://opengapps.org/?api=6.0&variant=mini
do select the arm 64 version and mini one.
download from your pc and copy it to micro sd card. enter this card into you phone and go to mount in twrp.
mount the micro sd card storage.
select the zip file on the micro sd card from the install tab on twrp and flash it.
now go back and flash open gapps zip file.
now REBOOT to system. everything will work fine....
any rom could be installed after it by the same proccess.
you would beome comfortable in doing all this after once trying/.
if you even brick your phone there would always be a way out.
search it on youube.
because everything occurs in partitions , you think hat you have bricked but actually not. there's always a safe way out
---------- Post added at 05:19 PM ---------- Previous post was at 05:17 PM ----------
Do the above method till rooting and installing TWRP.
If you want to install cm14.1 for redmi note 3:
Follow this thread:
http://forum.xda-developers.com/redm...459382/page330
[email protected] said:
This may give you method for rooting...
And for installing cm13 ROM too... With proof...
It worked for me .. I did the same...
First
download the required files from the given link: [50mb]
https://drive.google.com/file/d/0B81...w?usp=drivesdk
INSTRUCTIONS: [redmi note 3]
1. Get into fastboot mode. Charge the phone first. Hold the power button and the volume down button simultaenously.
2. If you can open your current rom, open developer options by clicking on the build no several times in the about phone menu in settings. and select allow oem unlocking and usb debugging.
3. if not leave it... go on and connect your phone to the PC while in fastboot mode.
BUT, before that: open Command prompt on your PC. (search it on the search box). right click on it and open it in administrator mode.
type in: bcdedit /set testsigning on
hit enter and restart your pc
(this is imp.)
4. open the zip file and extract the contents. open the boot edl mode folder and click the edl.bat file. allow it to run.
5. now screen will turn black, do not disturb it. Now flash the twrp by running flash twrp.bat from the 'flash TWRP' folder.
6. Now go to Unlock folder and run the unlock bootloader.bat file.
your phone will boot into the TWRP recovery mode automatically.
if it opens in chineese you select every tab and find the globe icon.
if the globe icon is found on any of the tab select it and change the language to ENGLISH.
wipe your system from the wipe tab:
Now download the latest CM13 SNAPSHOT BUILD ROM FOR YOUR REDMI:
https://download.cyanogenmod.org/get/kenzo-snapshot.zip
and GAPPS:
http://opengapps.org/?api=6.0&variant=mini
do select the arm 64 version and mini one.
download from your pc and copy it to micro sd card. enter this card into you phone and go to mount in twrp.
mount the micro sd card storage.
select the zip file on the micro sd card from the install tab on twrp and flash it.
now go back and flash open gapps zip file.
now REBOOT to system. everything will work fine....
See the following overview video after installing the CM13 ROM:
https://www.youtube.com/watch?v=T--f7ClmQVM
any rom could be installed after it by the same proccess.
you would beome comfortable in doing all this after once trying/.
if you even brick your phone there would always be a way out.
search it on youube.
because everything occurs in partitions , you think hat you have bricked but actually not. there's always a safe way out
---------- Post added at 05:19 PM ---------- Previous post was at 05:17 PM ----------
Do the above method till rooting and installing TWRP.
If you want to install cm14.1 for redmi note 3:
Follow this thread:
http://.xda-.com/redm...459382/page330
Click to expand...
Click to collapse
How we can flash twrp without unlocking bootloder as you say, first flash twrp then unlock Bootloader it's Not posible,
XN Logos said:
How we can flash twrp without unlocking bootloder as you sat, first flash twrp then unlock Bootloader it's Not posible,
Click to expand...
Click to collapse
Both can be done.
Vice versa is also possible.
OK then click unlock bootloader first and then flash twrp.
The reverse can also be done. I did the reverse and I was amazed so thought I should as this to my tutorial
[email protected] said:
Both can be done.
Vice versa is also possible.
OK then click unlock bootloader first and then flash twrp.
The reverse can also be done. I did the reverse and I was amazed so thought I should as this to my tutorial
Click to expand...
Click to collapse
1. bro drive link you provided say file does not exist..............
2. do we have to follow all your steps every time for flashing rom???
Sorptarn said:
1. bro drive link you provided say file does not exist..............
2. do we have to follow all your steps every time for flashing rom???
Click to expand...
Click to collapse
Sorry I accidently removed the link.
I also deleted my review video of YouTube .
I will upload it and get you the link
---------- Post added at 11:08 AM ---------- Previous post was at 11:03 AM ----------
Sorptarn said:
1. bro drive link you provided say file does not exist..............
2. do we have to follow all your steps every time for flashing rom???
Click to expand...
Click to collapse
Once unlocked bootloader and flash twrp.
You don't have to take help of PC or any other thing.
You can always do it on the phone itself.
Boot into twrp by pressing upper volume and power button.
Wipe everything except storages (internal or external)
And then install the ROM zip file and gapps file accordingly.
Do it for any rom
---------- Post added at 11:20 AM ---------- Previous post was at 11:08 AM ----------
Wait uploading the file...
---------- Post added at 11:26 AM ---------- Previous post was at 11:20 AM ----------
Bro file uploaded.
Take it and enjoy.
https://mega.nz/#!1NhDTQoR!cP7vrchwswOfj3oHQ5saZ2d0JkcmunEn5pqyOcpZDoE
---------- Post added at 11:29 AM ---------- Previous post was at 11:26 AM ----------
XN Logos said:
How we can flash twrp without unlocking bootloder as you say, first flash twrp then unlock Bootloader it's Not posible,
Click to expand...
Click to collapse
New link updated for root files
https://mega.nz/#!1NhDTQoR!cP7vrchwswOfj3oHQ5saZ2d0JkcmunEn5pqyOcpZDoE
@[email protected] bro ye global stable miui8 lp mein kaam krega na.............
Sorptarn said:
@[email protected] bro ye global stable miui8 lp mein kaam krega na.............
Click to expand...
Click to collapse
any rom can be install from phone through twrp directly but this is for rom other than miui.
if you install the global stable miui 8 official then its gone. your phone will brick. the bootloader, since is unofficially unlocked, your phone would stuck at mi logo.
now if you wanna install miui rom without any such kinda loss, you see this video: the madthing he explained everything.
download a patched miui 8 rom that will support unofficially unlocked bootloader and will not cause any problem. and it supprts volte too.
or if you want the real miui 8 global rom back . this has to be done by pc.
Install miui 8 patched directly from twrp recovery. [easy one with extra features and safe and volte supported]
https://www.youtube.com/watch?v=B1U1T5gBzbI
Or install the stable miui 8 global offiical rom by pc method. doing everything again. [hard one, success not guaranteed but mostly works. follow each step correctly]
https://www.youtube.com/watch?v=YijIOh9b3mY
his would definetly help you.
do give a thumbs up if you found it helpful
[email protected] said:
any rom can be install from phone through twrp directly but this is for rom other than miui.
if you install the global stable miui 8 official then its gone. your phone will brick. the bootloader, since is unofficially unlocked, your phone would stuck at mi logo.
now if you wanna install miui rom without any such kinda loss, you see this video: the madthing he explained everything.
download a patched miui 8 rom that will support unofficially unlocked bootloader and will not cause any problem. and it supprts volte too.
or if you want the real miui 8 global rom back . this has to be done by pc.
Install miui 8 patched directly from twrp recovery. [easy one with extra features and safe and volte supported]
https://www.youtube.com/watch?v=B1U1T5gBzbI
Or install the stable miui 8 global offiical rom by pc method. doing everything again. [hard one, success not guaranteed but mostly works. follow each step correctly]
https://www.youtube.com/watch?v=YijIOh9b3mY
his would definetly help you.
do give a thumbs up if you found it helpful
Click to expand...
Click to collapse
Thnx fr the update..........
Bt was asking that im currently on miui 8 stable lp........ Th unlock krne k lie miui dev rom th flash nhi krni......
First try this the process I have suggested and given instructions. If any problem comes I would help.
It can alone unlock bootloader. No need to install global kenzo ROM.
I would help just text me
[email protected] said:
First try this the process I have suggested and given instructions. If any problem comes I would help.
It can alone unlock bootloader. No need to install global kenzo ROM.
I would help just text me
Click to expand...
Click to collapse
Tried to unlock bootloader, but the stuck at 50% saying unable to verify device something.. so tried logging into micloud and making hte device active.
Will try it today.
So after unlocking bootloader, just flash TWRP using adb commmands and flash SuperSU??
abihary said:
you can try to unlock directly at your current stable rom, somebody able to do it while i can't do it and should move to dev rom to unlock.
if you failed to do it at current rom, you can move to dev rom using miflash and ofc using fastboot rom. if you should move to dev rom to unlock, choose LP rom since MM rom have forced encryption feature by default.
Click to expand...
Click to collapse
Thank you... I tried to unlock it on global stable rom but not able to do it(stuck a 50%)
Can i just download and 6.9.15 global developer rom and flash it using updater and try unlocking the bootloader or is it necessary to flash fastboot rom only.
If yes, please provide the link for lollipop fastboot rom
$lim $hady said:
Thank you... I tried to unlock it on global stable rom but not able to do it(stuck a 50%)
Can i just download and 6.9.15 global developer rom and flash it using updater and try unlocking the bootloader or is it necessary to flash fastboot rom only.
If yes, please provide the link for lollipop fastboot rom
Click to expand...
Click to collapse
better go to global dev LP to avoid problem with data encryption at global dev MM.
you can download it from this link
abihary said:
better go to global dev LP to avoid problem with data encryption at global dev MM.
you can download it from this link
Click to expand...
Click to collapse
Thanks for the link. Downloading it now..could you please provide the steps to flash this file or a link which helps in flashing fastboot rom...
once i have flashed, just unlock it and flash twrp and supersu.
Any other steps to flash cm 13 or 14..??
$lim $hady said:
Tried to unlock bootloader, but the stuck at 50% saying unable to verify device something.. so tried logging into micloud and making hte device active.
Will try it today.
So after unlocking bootloader, just flash TWRP using adb commmands and flash SuperSU??
Click to expand...
Click to collapse
Yeah
---------- Post added at 10:09 AM ---------- Previous post was at 10:03 AM ----------
[email protected] said:
Yeah
Click to expand...
Click to collapse
If you do it by installing global dev kenzo ROM by mi flash then it may get stuck at 50-60℅ as happened to many here.
I have also experienced it. It got stuck at 40℅. It may happen.
It can say not enough memory to continue or whatever ****.
Leave it don't panic. The ROM has partially been installed.
Now cmtry power off. Or click on boot edl mode. Now directly click unlock bootloader .bat file which I provided. And then click on flash twrp. Bat file.
You phone will automatically boot into twrp and now go last tab of last second row, got to globe icon and change language and now go back and wipe everything.
No wiping internal storage if you have kept any ROM there. But I suggest wipe everything.
Insert a micro SD card or USB otg containing any ROM (because you need to boot up at least) and then flash it along with proper gapps.
---------- Post added at 10:12 AM ---------- Previous post was at 10:09 AM ----------
You phone will boot up and now if you want you can go again to twrp and install a proper ROM of your choice. Or if you want stay there. Boot loader unlocked twrp flashed and everything done.
[email protected] said:
Yeah
---------- Post added at 10:09 AM ---------- Previous post was at 10:03 AM ----------
If you do it by installing global dev kenzo ROM by mi flash then it may get stuck at 50-60℅ as happened to many here.
I have also experienced it. It got stuck at 40℅. It may happen.
It can say not enough memory to continue or whatever ****.
Leave it don't panic. The ROM has partially been installed.
Now cmtry power off. Or click on boot edl mode. Now directly click unlock bootloader .bat file which I provided. And then click on flash twrp. Bat file.
You phone will automatically boot into twrp and now go last tab of last second row, got to globe icon and change language and now go back and wipe everything.
No wiping internal storage if you have kept any ROM there. But I suggest wipe everything.
Insert a micro SD card or USB otg containing any ROM (because you need to boot up at least) and then flash it along with proper gapps.
---------- Post added at 10:12 AM ---------- Previous post was at 10:09 AM ----------
You phone will boot up and now if you want you can go again to twrp and install a proper ROM of your choice. Or if you want stay there. Boot loader unlocked twrp flashed and everything done.
Click to expand...
Click to collapse
Thanks but i don want to unlock it unofficially.. unless its not possible to unlock it officially..
$lim $hady said:
Thanks but i don want to unlock it unofficially.. unless its not possible to unlock it officially..
Click to expand...
Click to collapse
Wait for 1 or 2 weeks then.
And not sure whether it will accept your request or not. OK .
Welcome
TWRP 3.1.1-0 Moto G5 plus (potter)
Latest TWRP changelog :
3.1.1-0 full changelog
Working/Bugs :
I have just basically tested and all seems to be working (including decryption of /data). If something is broken lemme know.
Please do read the installation guide note !
IMPORTANT NOTE :
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
Force encryption is enabled by default in stock OS and twrp will successfully decrypt /data at first boot if all goes well
If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to wipe data once via twrp wipe options and reboot back to twrp for functioning of /data
Installation Guide :
Make sure you have unlocked bootloader
Reboot to bootloader
fastboot flash recovery twrp-****.img (if you want permanent flash) or fastboot boot twrp-****.img (if you want temporary
boot)
Download Link :
twrp_3.1.1-0_potter
Have used prebuilt kernel of existing sdcard fixed twrp released by vache and hence there is no kernel source to provide
XDA:DevDB Information
[Unofficial] TWRP 3.1.1-0 Moto G5 Plus, ROM for the Moto G5 Plus
Contributors
Santhosh M, vache
Source Code: http://using prebuilt stock kernel and hence no kernel source available
ROM OS Version: 7.x Nougat
Version Information
Status: Stable
Stable Release Date: 2017-03-21
Created 2017-03-21
Last Updated 2017-06-22
Reserved
Reserved
It it working properly? Can i flash Super su by temporary boot? I don't want to brick my device so asked this.. Kindly reply, thanks for the early build
Santhosh M said:
Reserved
Click to expand...
Click to collapse
Oh yussss tysm. Let's start the party. will be flashing right away when ill receive this device on 25
---------- Post added at 03:37 PM ---------- Previous post was at 03:24 PM ----------
virajkin said:
It it working properly? Can i flash Super su by temporary boot? I don't want to brick my device so asked this.. Kindly reply, thanks for the early build
Click to expand...
Click to collapse
It should be working that's why Dev has posted it. Try and let us know.
Santhosh M said:
Unofficial TWRP 3.1.0-0 Moto G5 (potter)
Latest TWRP changelog :
New features of 3.1.0 (adb backup, tweaked MTP startup routines and plenty of bug fixes - for full changelog)
Download Link
twrp-3.1.0-0-potter.img
Working/Bugs
I have just basically tested and all seems to be working. If something is broken lemme know.
Installation Guide
IMPORTANT NOTE : Since force encryption is enabled by default in stock OS TWRP will/might ask for decrypt password for /data while you boot for first time.
You would need to wipe data once via twrp wipe options and reboot back to recovery for twrp for functioning of /data
Make sure you have unlocked bootloader
fastboot flash recovery twrp-****.img (if you want permanent flash) or fastboot boot twrp-****.img (if you want temporary
boot)
XDA:DevDB Information
[Unofficial] TWRP 3.1.0-0 Moto G5 Plus, ROM for the Moto G5 Plus
Contributors
Santhosh M
Source Code:http://using prebuilt stock kernel and hence no kernel source available
ROM OS Version: 7.x Nougat
Version Information
Status: Stable
Stable Release Date: 2017-03-21
Created 2017-03-21
Last Updated 2017-03-21
Click to expand...
Click to collapse
This was the reason I went for this device.
Thank you very much.:good:
I tried booting to this recovery by fastboot boot twrp...img, to flash super su, it asked for a password, I selected cancel, so i couldnot see my internal storage folders, so just selected to reboot the system. Now the phone has stuck on ! Your device will boot in 5 seconds,, please help anyone. OP
virajkin said:
I tried booting to this recovery by fastboot boot twrp...img, to flash super su, it asked for a password, I selected cancel, so i couldnot see my internal storage folders, so just selected to reboot the system. Now the phone has stuck on ! Your device will boot in 5 seconds,, please help anyone. OP
Click to expand...
Click to collapse
Make sure u read whole OP at least once. Try to boot into fastboot. And flash again the twrp. U need to wipe your data with twrp first. Than boot ur device. Than flash latest stable SuperSu zip.
Thanks @Santhosh M for bringing twrp this fast will flash it as soon as my device arives.
fAIyaZ said:
Make sure u read whole OP at least once. Try to boot into fastboot. And flash again the twrp. U need to wipe your data with twrp first. Than boot ur device. Than flash latest stable SuperSu zip.
Thanks @Santhosh M for bringing twrp this fast will flash it as soon as my device arives.
Click to expand...
Click to collapse
Booted in TWRP and tried to wipe data, it gives error "failed to mount /data Invalid argument", unable to mount storage
virajkin said:
I tried booting to this recovery by fastboot boot twrp...img, to flash super su, it asked for a password, I selected cancel, so i couldnot see my internal storage folders, so just selected to reboot the system. Now the phone has stuck on ! Your device will boot in 5 seconds,, please help anyone. OP
Click to expand...
Click to collapse
even i got the same error message. guess i'll have to wait for stock firmware to be available now to flash and go back to stock and try again
virajkin said:
I tried booting to this recovery by fastboot boot twrp...img, to flash super su, it asked for a password, I selected cancel, so i couldnot see my internal storage folders, so just selected to reboot the system. Now the phone has stuck on ! Your device will boot in 5 seconds,, please help anyone. OP
Click to expand...
Click to collapse
virajkin said:
Booted in TWRP and tried to wipe data, it gives error "failed to mount /data Invalid argument", unable to mount storage
Click to expand...
Click to collapse
deepakdtg said:
even i got the same error message. guess i'll have to wait for stock firmware to be available now to flash and go back to stock and try again
Click to expand...
Click to collapse
Any advice? @Santhosh M
is it like we have to give password and not cancel it? and than wipe data and reboot?
none its properly mentioned to decrypt your device , why do you guys even hesitate to read
Seems like race got stared.
The download link does not work
Yes...Press cancel...Wipe data and reboot...It worked perfectly.
Would be better if someone actually followed exact that way and report if all is fine
Santhosh M said:
Yes...Press cancel...Wipe data and reboot...It worked perfectly.
Would be better if someone actually followed exact that way and report if all is fine
Click to expand...
Click to collapse
But I get error unable to mount /data invalid argument, phone stuck at warning message, please help
jaombk said:
The download link does not work
Click to expand...
Click to collapse
Just save the link. It'll dwld the file.
rayzen6 said:
Just save the link. It'll dwld the file.
Click to expand...
Click to collapse
Without success to download, would have another link to download.
@Santhosh M
Are you going to develop for G5 Plus? I enjoyed your roms for kenzo but you left the development.
Any plans for G5/G5 Plus?
jaombk said:
Without success to download, would have another link to download.
Click to expand...
Click to collapse
I can't able to upload here without dev's permission.
---------- Post added at 08:18 PM ---------- Previous post was at 08:02 PM ----------
naturist said:
@Santhosh M
Are you going to develop for G5 Plus? I enjoyed your roms for kenzo but you left the development.
Any plans for G5/G5 Plus?
Click to expand...
Click to collapse
+1
Never had kenzo but I was looking at development from beginning on that device. He was the first who brings custom rom to kenzo.
Squid will support and now santhosh has already started and gave twrp very fast. Future looks very bright to me.
naturist said:
@Santhosh M
Are you going to develop for G5 Plus? I enjoyed your roms for kenzo but you left the development.
Any plans for G5/G5 Plus?
Click to expand...
Click to collapse
I think that we will see squid2 here
Sent from my Moto G 2014 using XDA Labs
Return to Un-modded Stock:
Bootloader unlocked and TWRP and Root included
The file is 4gb compressed to 2gb. Depending on your connection it will probably take 20 to 45 minutes to download.
Be Advised
Do your research before flashing anything, I am not responsible for any damage caused to your device, due to impatience and missed steps. However, rest assured this recovery is solid and will absolutely return your X720 or X727 to stock 5.8.21s (with the bootloader already unlocked, TWRP installed and rooted)
I was asked by several people if I would be willing to share a link to my Stock X727 recovery, I created this thread to provide the 5.8.21s recovery for anyone who is experiencing dire issues or is simply wanting to restore the last official x727 recovery, as a daily driver or as a means to troubleshoot their issues by returning to the fully stock rom, stock partitions and ready to start over.
Attached is my full stock TWRP Recovery for my Le Eco Pro 3, version: 5.8.21s (X727)
It is a clean TWRP backup recovery that I did not mod in any way other than unlocking the bootloader.
The link is to my Google Drive account. https://drive.google.com/open?id=19dtLHmE5bsx5mdtEXOns4Z5drpeY79Em
The file is compressed
Ensure that you perform a full wipe before applying this recovery, and that you know what you are doing before attempting to install.
Please note that any changes that you make to your device is done at your own risk.
Please use caution and make sure that you have TWRP recovery installed.
Be in the habit of booting back to recovery before booting to system....This is a good practice for ensuring TWRP stays installed
You must unpack the downloaded 7zip file, before it will be useable.
As long as you can boot into TWRP and have root access you will have the full permissions needed to install anything , and reverse any actions that do not workout as planned.
Personally, I make a backup of my existing installation prior to making any changes. I recommend that you do the same. If you buy an OTG adapter and a USB 3.0 drive it takes 5 minutes.
The steps provided on the following link can be used to install my recovery file. https://forum.xda-developers.com/le-pro3/how-to/guide-return-to-stock-lock-bootloader-t3539513
When clicking the link, Google will attempt to scan. Click download to see the file, and then choose download if wanted.
Flash the appropriate files below for which ever device you own. ( X727 - Not needed, I provided the files anyway just in case.)
Firmware - X720
https://mega.nz/#F!kDgFQJ6R!MDhxCFw5KjfB0CfxAWwr9w
Firmware - X727
https://drive.google.com/open?id=136-4UpUUsj3exNsTc3d5n2iQuYUxr00H
Modems
X720: https://mega.nz/#F!pZ4WGARZ
Key : !2oG3Z2LS_wP8BzcWUQjfHg
X727: https://mega.nz/#F!NJ5VHS7Z
Key : !p0iO7bDiZ4kXny03EiAlWw
Build Prop Fix Device ID Tool ( Credit to @Ascertion )
https://mega.nz/#F!oAZ3yC4b
Key: !MDwbHXNTRdrpgMvQ42yviw
EFS:
Warning : Use this only if you have unrepairable IMEI Issues! Otherwise its not needed, and you could forever lose your original IMEI info.
https://drive.google.com/open?id=10n2VjwBYHmrq_PllcWmTaGUtMIeYynZ7
[B ]Just for Fun[/B] - Boot Screens and Boot Animations -
https://mega.nz/#F!JB51zbwR
Key: !sG_wXTPqyKpugg5QIZFo9w
These splash-screens and animations came from various sources. If you created them contact me so i can give you credit.
The Red Splash came from the Couco modified EUI : version 5.9.028s VR4
Other Helpful Hints and Tips More to Come!
Unlock Bootloader and Flash Roms, Gapps and Magisk https://forum.xda-developers.com/showpost.php?p=75009966&postcount=692 ( If using original Stock
Viper Settings : https://forum.xda-developers.com/showpost.php?p=75449097
Installing Viper and Dolby: https://forum.xda-developers.com/showpost.php?p=76362493&postcount=19
Edit
October 8, 2018:
I uploaded the Leeco Full Stock Rom 5.8.26s to my MegaDrive.
If you are selling your phone and want it to have stock without TWRP and without root , just flash this Rom and your stock radio driver "firmware" for your device
Link for EUI 21S : https://mega.nz/#!FRhh1ArL
Key: V5ua3oj91kFtgvLYBhl1X6Oq3bsScyDFruN3UptkWN0
A late reply to my issue but I just got around to restoring my Pro3. This worked while the last backup did not! Thanks!
Soul0Reaper said:
A late reply to my issue but I just got around to restoring my Pro3. This worked while the last backup did not! Thanks!
Click to expand...
Click to collapse
Thats Awesome! I am glad that it helped you.
Great work just what I needed only one problem for me after I flash rom reboot system and then go back into TWRP there seems to be encryption on it and I can't install or backup or do much. Is there a password or way around this TWRP encryption?
dunas2331 said:
Great work just what I needed only one problem for me after I flash rom reboot system and then go back into TWRP there seems to be encryption on it and I can't install or backup or do much. Is there a password or way around this TWRP encryption?
Click to expand...
Click to collapse
Sorry, I didn't get a notification for your message. The encryption is your storage.
Follow the instructions here to resolve: https://www.google.com/amp/s/forum....return-to-stock-lock-bootloader-t3539513/amp/
The link has instructions for getting past and removing encryption.
tsongming said:
Sorry, I didn't get a notification for your message. The encryption is your storage.
Follow the instructions here to resolve: https://www.google.com/amp/s/forum....return-to-stock-lock-bootloader-t3539513/amp/
The link has instructions for getting past and removing encryption.
Click to expand...
Click to collapse
Can you elaborate on what to do here I keep getting encryption password too and can't do anything in twrp
Hi tsongming, you know if can work on a x720?
thanks
Toni Moon said:
Hi tsongming, you know if can work on a x720?
thanks
Click to expand...
Click to collapse
Yes x720 and x727 are practically identical phones.
Sent from my LEX720 using XDA Labs
Scruffdog1978 said:
Can you elaborate on what to do here I keep getting encryption password too and can't do anything in twrp
Click to expand...
Click to collapse
I don't have time at the moment to provide lengthy instructions. With respect, I am providing a working, clean unlocked recovery file and pointing the way to instructions already that exist all throughout the LeEco forums.
But here's a quick answer
First use TWRP to reset your phone with a clean wipe, like you would for any ROM. Set developer options to the standard settings.
Next, your storage is encrypted. So it needs to be formatted. Use TWRP format the storage only. Then reboot to recovery.
****Important****
Don't ever format the storage without ensuring that you have a TWRP recovery. Always check the boxes to check if TWRP is installed before swiping. If you don't have a recovery you have a soft brick.
For you information, TWRP recovery is installed on it's on it very own partition. Formatting the storage does not affect the TWRP partition. Nonetheless, if you see the check box option, make sure they are checked.
I would suggest that you install the all in one tool : https://www.google.com/amp/s/forum....pment/tool-tool-one-mauronofrio-t3580611/amp/
This tool helps a lot and makes this stuff easier if are new to flashing custom Roms.. The all in one tool will update the Google driver and ADB installation on your computer.
After you format your drive you will have to flash the recovery from the PC. The links provided show all of the steps, or you can use the all for one tool. When your storage is encrypted you have no choice but to format.
If you use the all in one tool , see their page for instructions.
Read the instructions, then read them again. when learning something new it's a good idea to take notes.
Do not deviate from those steps or you could brick your phone.
There have been many people that have messaged me by PM who successfully returned to stock using my recovery, so it will work as long as you are careful and follow the instructions verbatim and you will be fine. Plus, It's a great idea to create your own working recovery before you begin.
Reminder, you are restoring to stock under you own discretion, I am not responsible if you miss a key step, have a power outage, use faulty cables or brick your device.
One final suggestion, when you install the recovery make sure your phone is fully charged. Unplug all unneeded external peripherals from your desktop computer.
Temporarily, disable antivirus, insert USB cable into the back of your desktop PC. Those outlets provide more power.
Please look past any typos, I typed this on little keys.
One last suggestion
Read this
http://www.androidtipsz.com/top-5-things-to-do-before-installing-a-custom-rom-on-your-android-device
Sent from my LEX720 using XDA Labs
Will I keep twrp after restore? Thanks
---------- Post added at 03:29 PM ---------- Previous post was at 02:53 PM ----------
meh4life321 said:
Will I keep twrp after restore? Thanks
Click to expand...
Click to collapse
Also, could I just restore the system?
Could I just flash this in TWRP and keep twrp as my recovery?
meh4life321 said:
Will I keep twrp after restore? Thanks
---------- Post added at 03:29 PM ---------- Previous post was at 02:53 PM ----------
Also, could I just restore the system?
Click to expand...
Click to collapse
No it will not keep twrp. follow the instructions in the link I provided above, there was no reason to duplicate the instructions on my post.
The difference is that my backup will restore your phone to Eui 5.8.21s with bootloader unlocked. You will need to reflash Twrp and root the phone with Magisk if you want to keep Twrp recovery ( that is what I would do) You will not be able to get OTA updates. But that doesn't matter because there probably not be any more OTA updates for the x727
Thank you, sir! This is great work. I was able to restore back to stock.
On the strange side of thing, my TWRP was saved. Previously, I was running AICP, but having multiple sound issues with it.
Here are the steps I followed to restore:
1) Move the file to OTG flash drive
2) Restore through TWRP via Restore
For my 727, it just reboot on logo, and doesn't go past it.
rob_z11 said:
For my 727, it just reboot on logo, and doesn't go past it.
Click to expand...
Click to collapse
It takes a while.
For me, I had the quickest experience by flashing Magisk afterwards. The stock Rom , Rooted, and with Xposed is actually pretty sweet.
tsongming said:
It takes a while.
For me, I had the quickest experience by flashing Magisk afterwards. The stock Rom , Rooted, and with Xposed is actually pretty sweet.
Click to expand...
Click to collapse
Will try again. How long is while? ?
rob_z11 said:
Will try again. How long is while?
Click to expand...
Click to collapse
It should not take more than 10 minutes, and will usually startup in 5. I just now restored one of my X727's with this recovery, using the OTG method that the last person used and viola in worked so there's no doubt. I have always used ADB until now.
However, unlike the other poster, I did lose Twrp and had to reinstall it.
Always, Always Ensure Twrp is permanently installed
Make sure that you are on the latest version of Twrp : https://twrp.me/leeco/leecolepro3.html
Run Magisk, install Rom, Install Magisk again
Personally, I use the latest version of Magisk : https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
You want a fully clean install before you flash.
Instructions are redundant of XDA: if you want something other than what you have read already: Click on my account history to find detailed instructions, ( I type too much, too often) Under most thanked, you can quickly find detailed instructions for installing , Roms, Rooting, Installing Twrp, How to wipe to avoid any issues.
Finally, if for some reason it still doesn't work, the file may have been corrupted.
Worst Case scenario : there are other recoveries available on XDA. Beware of the edited versions, they do not work as well as an unadulterated recovery.
tsongming said:
It should not take more than 10 minutes, and will usually startup in 5. I just now restored one of my X727's with this recovery, using the OTG method that the last person used and viola in worked so there's no doubt. I have always used ADB until now.
However, unlike the other poster, I did lose Twrp and had to reinstall it.
Always, Always Ensure Twrp is permanently installed
Make sure that you are on the latest version of Twrp : https://twrp.me/leeco/leecolepro3.html
Run Magisk, install Rom, Install Magisk again
Personally, I use the latest version of Magisk : https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
You want a fully clean install before you flash.
Instructions are redundant of XDA: if you want something other than what you have read already: Click on my account history to find detailed instructions, ( I type too much, too often) Under most thanked, you can quickly find detailed instructions for installing , Roms, Rooting, Installing Twrp, How to wipe to avoid any issues.
Finally, if for some reason it still doesn't work, the file may have been corrupted.
Worst Case scenario : there are other recoveries available on XDA. Beware of the edited versions, they do not work as well as an unadulterated recovery.
Click to expand...
Click to collapse
It actually worked for second time without any issues. Just can't get the root, but will follow your instructions.
Hi just wondering does this rom pass safetynet out of the box?
what is the date of the security patch of this rom?
thanks
blanktape said:
Hi just wondering does this rom pass safetynet out of the box?
what is the date of the security patch of this rom?
thanks
Click to expand...
Click to collapse
This recovery is stock EUI 5.8.21s. The exception is that the bootloader is unlocked, and it has TWRP Recovery instead of EUI Recovery. I do not remember which version of Magisk I Installed. I would advise that you flash the newest version of Magisk and you will not have any safety net issues.
If you are wanting a complete return to stock, you should instead reflash the stock Full Rom, which will reinstall EUI recovery and lockdown the bootloader.
Code:
*** Disclamer * Your warranty is now void. * *
We are 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 us for messing
up your device, we will laugh at you.
DISCONTINUED, MOVED TO BUILDING CRDROID AND AICP ANDROID PIE
Known Issues
No audio through speaker, currently trying to find a fix.
ROM ResurrectionRemix-O-v6.2.1-20181202
TWRP DOWNLOAD
INSTALLATION
I am assuming that most of you already know how to flash custom ROMS.
Boot into TWRP Recovery Flash TWRP 3.2.3-0 image
Wipe the System, Cache and Data.
Flash ROM Zipfile
Flash the GApps (optional, needed for Google Playstore to work).
(Optional) Flash root zipfile Majisk/SuperSU.
Wipe ART/Dalvik cache.
Reboot
Flashing the ROM itself the boot time is around 5 mins, if you flash Gapps + Majisk or SuperSU expect the first boot time to increase to about 7-8 mins
XDA:DevDB Information
SM-T350 ResurrectionRemix Oreo, ROM for the Samsung Galaxy Tab A series
Contributors
nubianprince
Source Code: https://github.com/Nubianprince/gt58wifi_rr
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Nougat
Version Information
Status: Beta
Beta Release Date: 2018-12-02
Created 2018-12-02
Last Updated 2019-03-23
Reserved
reserved
Did you guys just use the open source code of lineage 15.1 that didn't have working speaker. So is basically the same rom with different name. I'm still going to flash it for kicks but doesn't seem kinda pointless? Twrp should be better I'll let you know I'm assuming you forgot to mention gapps.
Funny cause the guy that built that took the source codes from someone else and that's why the speaker never got fixed because you don't know how to build or compile your just copying.
I got the rom up and running i was on marshmallow firmware and it worked fine. It takes awhile to boot up give it 10 minutes then when you start up it's really slow and lagging but after a couple reboots it works fine. I do say it's resremix tons of customization I haven't used any yet. I still think it's based off the lineage codes but it's different very different setup so it's worth installing if the damn speaker could get fixed it would be great. Bluetooth speaker or headphones work camera works I think the camera on this tablet is **** but works lol. Thanks for the rom guys. Twrp also seems to be working fine which is great because that's been a pain before.
Good job
Enviado desde mi SM-T320 mediante Tapatalk
So i am geting error 7. I have twrp 3.1.1-1_ashyx installed. I flash the new twrp recovery using install > install image > click the recovery file > click recovery partition and swipe to flash. then i follow all the other instructions and it still error 7 "this device is ." i found it odd that it doesnt list any name for the device. any help?
joejunior253 said:
So i am geting error 7. I have twrp 3.1.1-1_ashyx installed. I flash the new twrp recovery using install > install image > click the recovery file > click recovery partition and swipe to flash. then i follow all the other instructions and it still error 7 "this device is ." i found it odd that it doesnt list any name for the device. any help?
Click to expand...
Click to collapse
After you flashed the new twrp 3.2.3 did you reboot back into recovery? You can't just flash it then flash the rom you have to reboot in to recovery again to have it take effect. Also then follow all other instructions what instructions did you follow just a little more detail. Also what room or system were you on before?
I am coming from stock. When I flash from twrp and then click reboot recovery I get a boot loop. I've even tried doing the hold volume down + home + power and then moving to volume up, still doesn't work. I can't get twrp 3.1.0 to work, I always have to use 3.1.1. and I can't get the system to downgrade to marshmallow to test out anything else. It always fails with media failed to launch or something similar. I can only get the stock firmware ending in q1 and q5 to work (the latest ones running nougat). But I did notice on the twrp link that the nougat is for the t355 but appears to work on my t350.
joejunior253 said:
I am coming from stock. When I flash from twrp and then click reboot recovery I get a boot loop. I've even tried doing the hold volume down + home + power and then moving to volume up, still doesn't work. I can't get twrp 3.1.0 to work, I always have to use 3.1.1. and I can't get the system to downgrade to marshmallow to test out anything else. It always fails with media failed to launch or something similar. I can only get the stock firmware ending in q1 and q5 to work (the latest ones running nougat). But I did notice on the twrp link that the nougat is for the t355 but appears to work on my t350.
Click to expand...
Click to collapse
I'm not 100 percent what your saying. I believe your problems is with twrp you need to update twrp to version 3.2.3 which is on the first page of this thread. You need twrp 3.2.3 because the device tree is different for Oreo roms so much that you can't flash them with twrp 3.1.1. Downgrading system was not really the way to do it. I was just saying it worked from marshmallow not that you should be on marshmallow. When I downgraded from nougat firmware q1 and q5 bot to marshmallow I was able to downgrade but I got a drk error upon reboot. I just forced reboot and marshmallow stock worked but Downgrading is not usually good. Let's me also ask did you wipe efs partition with twrp 3.2.1 from the other thread at anytime? Try 3.2.3 either flash tar with Odin or extract img and flash in twrp recovery.
P.s. also yes twrp 355 3.1.1 does work on smt350 very well but still twrp3.2.3 should be the one to use.
If you wiped efs with twrp 3.2.1 and got an error you need to get back on to nougat firmware and then you into twrp terminal in advanced. Type in the first line hit enter then type in second command enter. You will no be able to boot marshmallow but you still might get drk error I got. It's because twrp 3.2.1 came from lte source codes and people think there the same there not the efs partition controls you Bluetooth and wifi on lte I'm sure it controls data. So it's not the same and it damages it and can't fix it because the partitions aren't setup right. I hope this helps. Guys take notes xda is for helping to not just getting root then leaving try to help out.
mke2fs /dev/block/mmcblk0p13
mount -w -t ext4 /dev/block/mmcblk0p13
joejunior253 said:
I am coming from stock. When I flash from twrp and then click reboot recovery I get a boot loop. I've even tried doing the hold volume down + home + power and then moving to volume up, still doesn't work. I can't get twrp 3.1.0 to work, I always have to use 3.1.1. and I can't get the system to downgrade to marshmallow to test out anything else. It always fails with media failed to launch or something similar. I can only get the stock firmware ending in q1 and q5 to work (the latest ones running nougat). But I did notice on the twrp link that the nougat is for the t355 but appears to work on my t350.
Click to expand...
Click to collapse
Device?
Firmware?
TWRP version?
Thanks tech guy. I will try this when I get home. I am back on stock firmware q5. I will just flash with Odin since I don't have twrp at all anymore. I will flash twrp 3.2.3. then I will try these commands. Fingers crossed it will work. Then I will boot into twrp if it works and flash the rom and gapps. I am not trying to root, just a better rom. I will post back soon
joejunior253 said:
Thanks tech guy. I will try this when I get home. I am back on stock firmware q5. I will just flash with Odin since I don't have twrp at all anymore. I will flash twrp 3.2.3. then I will try these commands. Fingers crossed it will work. Then I will boot into twrp if it works and flash the rom and gapps. I am not trying to root, just a better rom. I will post back soon
Click to expand...
Click to collapse
Ok you need root in twrp you'll need to see # on the command line that's super user sign and you can't reset you efs without out it but recovery might have root with flashing it but I don't think so. Main point flash magisk.
Techguy777 said:
I'm not 100 percent what your saying. I believe your problems is with twrp you need to update twrp to version 3.2.3 which is on the first page of this thread. You need twrp 3.2.3 because the device tree is different for Oreo roms so much that you can't flash them with twrp 3.1.1. Downgrading system was not really the way to do it. I was just saying it worked from marshmallow not that you should be on marshmallow. When I downgraded from nougat firmware q1 and q5 bot to marshmallow I was able to downgrade but I got a drk error upon reboot. I just forced reboot and marshmallow stock worked but Downgrading is not usually good. Let's me also ask did you wipe efs partition with twrp 3.2.1 from the other thread at anytime? Try 3.2.3 either flash tar with Odin or extract img and flash in twrp recovery.
P.s. also yes twrp 355 3.1.1 does work on smt350 very well but still twrp3.2.3 should be the one to use.
If you wiped efs with twrp 3.2.1 and got an error you need to get back on to nougat firmware and then you into twrp terminal in advanced. Type in the first line hit enter then type in second command enter. You will no be able to boot marshmallow but you still might get drk error I got. It's because twrp 3.2.1 came from lte source codes and people think there the same there not the efs partition controls you Bluetooth and wifi on lte I'm sure it controls data. So it's not the same and it damages it and can't fix it because the partitions aren't setup right. I hope this helps. Guys take notes xda is for helping to not just getting root then leaving try to help out.
mke2fs /dev/block/mmcblk0p13
mount -w -t ext4 /dev/block/mmcblk0p13
Click to expand...
Click to collapse
So...I am on stock nougat, nothing installed. I flash twrp 3.1.1, I go into twrp, click install, image, click recovery, root and install, then reboot and hold volume up and home, it says in yellow boot recovery, then goes to black screen. Then cannot power on, cannot boot into recovery, can only boot into download mode and reflash and try again.
---------- Post added at 06:40 PM ---------- Previous post was at 06:34 PM ----------
nubianprince said:
Device?
Firmware?
TWRP version?
Click to expand...
Click to collapse
SM-t350
Q5
TWRP 3.1.1
---------- Post added at 06:42 PM ---------- Previous post was at 06:40 PM ----------
Techguy777 said:
Ok you need root in twrp you'll need to see # on the command line that's super user sign and you can't reset you efs without out it but recovery might have root with flashing it but I don't think so. Main point flash magisk.
Click to expand...
Click to collapse
yes there is a # on my terminal when i open twrp 3.1.1.
i think the problem lies in rebooting after flashing the new recovery twrp, it just doesnt work. i am going to redownload and transfer to my sd card again and see if maybe the download was bad.
---------- Post added at 07:00 PM ---------- Previous post was at 06:42 PM ----------
Techguy777 said:
I'm not 100 percent what your saying. I believe your problems is with twrp you need to update twrp to version 3.2.3 which is on the first page of this thread. You need twrp 3.2.3 because the device tree is different for Oreo roms so much that you can't flash them with twrp 3.1.1. Downgrading system was not really the way to do it. I was just saying it worked from marshmallow not that you should be on marshmallow. When I downgraded from nougat firmware q1 and q5 bot to marshmallow I was able to downgrade but I got a drk error upon reboot. I just forced reboot and marshmallow stock worked but Downgrading is not usually good. Let's me also ask did you wipe efs partition with twrp 3.2.1 from the other thread at anytime? Try 3.2.3 either flash tar with Odin or extract img and flash in twrp recovery.
P.s. also yes twrp 355 3.1.1 does work on smt350 very well but still twrp3.2.3 should be the one to use.
If you wiped efs with twrp 3.2.1 and got an error you need to get back on to nougat firmware and then you into twrp terminal in advanced. Type in the first line hit enter then type in second command enter. You will no be able to boot marshmallow but you still might get drk error I got. It's because twrp 3.2.1 came from lte source codes and people think there the same there not the efs partition controls you Bluetooth and wifi on lte I'm sure it controls data. So it's not the same and it damages it and can't fix it because the partitions aren't setup right. I hope this helps. Guys take notes xda is for helping to not just getting root then leaving try to help out.
mke2fs /dev/block/mmcblk0p13
mount -w -t ext4 /dev/block/mmcblk0p13
Click to expand...
Click to collapse
Also in doing this wihtout having the twrp 3.2.3 and just trying from 3.1.1 results in mount: can't find /dev/block/mmcblk0p13 in /etc/fstab
I tried going into mount and clicking system too, still no dice. Really wanted to try this rom though, but all brick walls.
---------- Post added at 07:02 PM ---------- Previous post was at 07:00 PM ----------
Techguy777 said:
Ok you need root in twrp you'll need to see # on the command line that's super user sign and you can't reset you efs without out it but recovery might have root with flashing it but I don't think so. Main point flash magisk.
Click to expand...
Click to collapse
Soi you want me to flash magisk before I flash the new recovery, because i cant get the new recovery to work at all
And I think it is officially bricked now. I have tried to flash stock rom just to go back to having something that is working and I get the Error android and it gets to about 25 percent and resets to do the same thing. I have tried flashing twice, the official from sammobile, BSOD now.
joejunior253 said:
And I think it is officially bricked now. I have tried to flash stock rom just to go back to having something that is working and I get the Error android and it gets to about 25 percent and resets to do the same thing. I have tried flashing twice, the official from sammobile, BSOD now.
Click to expand...
Click to collapse
alright i think i am done being a whiney beezy. i was able ot do a ton of research, found that i might have had an esf failure or something. i flashed stock firmware, then reset odin without letting it reboot, flashed twrp, booted into it, rebooted the tablet and it works. i think i will wait for a from stock explanation on how to get this to work, i cannot get the recovery file to boot from twrp 3.1.1, it just black screens.
joejunior253 said:
alright i think i am done being a whiney beezy. i was able ot do a ton of research, found that i might have had an esf failure or something. i flashed stock firmware, then reset odin without letting it reboot, flashed twrp, booted into it, rebooted the tablet and it works. i think i will wait for a from stock explanation on how to get this to work, i cannot get the recovery file to boot from twrp 3.1.1, it just black screens.
Click to expand...
Click to collapse
Are you not English speaking? I said you had a efs error that's what I thought. You should have flashed the last version of nougat you had working when the error happened boot into stock and turned on USB debugging. Then you flash twrp either t355 3.1.1 or 3.2.3 are the best. I guess flash 3.1.1 for 355 at first then when you flash twrp on stock nougat boot into twrp and flash magisk 17.1 I'm having trouble with magisk 18 on some devices so use 17.1. Those terminal codes are tricky type them perfect or they don't work I recommend a couple times until it works. They should reset your efs partition then you reboot and flash your firmware again I'd say flash nougat again. Cause I flash marshmallow and got drk error. The firmware doesn't touch efs partition so once you screw it up your ass is grass unless you have a efs backup that works not the one from 3.2.1 twrp that screws everyone up. This is why people should not put stuff out until they have tested it. After you fix efs and can reboot then use twrp to flash twrp 3.2.3 by install image find the twrp 3.2.3 image select recovery. Flash because you can't flash Oreo with twrp 3.1.1. Then you can flash this rom.
You need root so you have to flash magisk in twrp after you flash twrp.
Try this code that will list partition blocks. Your efs should be 13. If it's not you don't have smt350 lol. Those codes work it Should say writing inode or something
ls -l /dev/block/bootdevice/by-name enter
mke2fs /dev/block/mmcblk0p13 enter
mount -w -t ext4 /dev/block/mmcblk0p13
Edit try SuperSU 2..82 sr5 beta or 2.79 sr3 because SuperSU is better for Samsung it's made to disable dm verity I think. Only up to nougat SuperSU will not work on Oreo you'll have to use magisk. The most important thing is after you flash the working stock firmware one of them will work I had this problem to only nougat q1 would work the rest didn't boot. So after I got my tablet running I flashed twrp 355 3.1.1 and went into terminal inside advance in twrp. I typed this commands and it worked it reset my efs partition my Bluetooth worked again my tablet would flash custom roms again and even downgrade back to marshmallow but I'm not recommending that. You type the first one hit enter type the second one hit enter then reboot. The firmware needs to be the same one you had when it errors if it's q5 then q5. I'm trying to help man I don't think your tablet is done I think it'll work again but it'll take some time and effort. You got this man . I always flash root first I don't think you have to because twrp already has root but I would say flash SuperSU first .
joejunior253 said:
So...I am on stock nougat, nothing installed. I flash twrp 3.1.1, I go into twrp, click install, image, click recovery, root and install, then reboot and hold volume up and home, it says in yellow boot recovery, then goes to black screen. Then cannot power on, cannot boot into recovery, can only boot into download mode and reflash and try again.
---------- Post added at 06:40 PM ---------- Previous post was at 06:34 PM ----------
SM-t350
Q5
TWRP 3.1.1
---------- Post added at 06:42 PM ---------- Previous post was at 06:40 PM ----------
yes there is a # on my terminal when i open twrp 3.1.1.
i think the problem lies in rebooting after flashing the new recovery twrp, it just doesnt work. i am going to redownload and transfer to my sd card again and see if maybe the download was bad.
---------- Post added at 07:00 PM ---------- Previous post was at 06:42 PM ----------
Also in doing this wihtout having the twrp 3.2.3 and just trying from 3.1.1 results in mount: can't find /dev/block/mmcblk0p13 in /etc/fstab
I tried going into mount and clicking system too, still no dice. Really wanted to try this rom though, but all brick walls.
---------- Post added at 07:02 PM ---------- Previous post was at 07:00 PM ----------
Soi you want me to flash magisk before I flash the new recovery, because i cant get the new recovery to work at all
Click to expand...
Click to collapse
Read everything i ve posted I said it was efs
Dude your all over the map man
1. Flash nougat firmware the last one you had boot up in the rom
2. Flash twrp 3.1.1
3. Flash SuperSU 2.7.9 or magisk 17.1 probably should go with SuperSU 2.82 SR5 beta.
4. Mack a back up
5. Reboot into rom
6. Reboot back into twrp and type that code it fixes your efs partition and resets it. Into terminal emulator inside twrp try it to it says writing inode or something like that. Both lines.
Reboot .
7. Go back into twrp flash image in install menu find twrp 3.2.3 I'm file make sure it's a image file.
Here's a section of my first post
Let's me also ask did you wipe efs partition with twrp 3.2.1 from the other thread at anytime? Try 3.2.3 either flash tar with Odin or extract img and flash in twrp recovery.
P.s. also yes twrp 355 3.1.1 does work on smt350 very well but still twrp3.2.3 should be the one to use.
If you wiped efs with twrp 3.2.1 and got an error you need to get back on to nougat firmware and then you into twrp terminal in advanced. Type in the first line hit enter then type in second command enter. You will no be able to boot marshmallow but you still might get drk error I got. It's because twrp 3.2.1 came from lte source codes and people think there the same there not the efs partition controls you Bluetooth and wifi on lte I'm sure it controls data. So it's not the same and it damages it and can't fix it because the partitions aren't setup right. I hope this helps. Guys take notes xda is for helping to not just getting root then leaving try to help out.
mke2fs /dev/block/mmcblk0p13
mount -w -t ext4 /dev/block/mmcblk0p13
If you can't boot into nougat go into twrp and type that code into the terminal emulator then when you get it to say writing idone or something it's working if you can't see the screen is black you have to search xda on tab a forms there's a fix a don't remember anyone please if you had twrp black screen what did you do? I've never had it.
---------- Post added at 02:36 PM ---------- Previous post was at 02:24 PM ----------
joejunior253 said:
So...I am on stock nougat, nothing installed. I flash twrp 3.1.1, I go into twrp, click install, image, click recovery, root and install, then reboot and hold volume up and home, it says in yellow boot recovery, then goes to black screen. Then cannot power on, cannot boot into recovery, can only boot into download mode and reflash and try again.
---------- Post added at 06:40 PM ---------- Previous post was at 06:34 PM ----------
SM-t350
Q5
TWRP 3.1.1
---------- Post added at 06:42 PM ---------- Previous post was at 06:40 PM ----------
yes there is a # on my terminal when i open twrp 3.1.1.
i think the problem lies in rebooting after flashing the new recovery twrp, it just doesnt work. i am going to redownload and transfer to my sd card again and see if maybe the download was bad.
---------- Post added at 07:00 PM ---------- Previous post was at 06:42 PM ----------
Also in doing this wihtout having the twrp 3.2.3 and just trying from 3.1.1 results in mount: can't find /dev/block/mmcblk0p13 in /etc/fstab
I tried going into mount and clicking system too, still no dice. Really wanted to try this rom though, but all brick walls.
---------- Post added at 07:02 PM ---------- Previous post was at 07:00 PM ----------
Soi you want me to flash magisk before I flash the new recovery, because i cant get the new recovery to work at all
Click to expand...
Click to collapse
No you can't flash magisk before twrp that makes no sense.
Please let me know what firmware update your trying to flash it Should be a the last one you had when you got the efs error and was able to boot into rom. That firmware only that one. No others will work I had this problem and fixed it. Also what twrp were you using when you got the efs error? Please answer it will help others to not touch it. I noticed that twrp 3.2.1 was taking down so I'm wondering did twrp 3.2.3 cause the error?
---------- Post added at 03:34 PM ---------- Previous post was at 02:36 PM ----------
Everyone did I not explain the fix right? I'm trying to learn how to help people on xda and if you guys think I didn't explain things right please let me know. I am fine with criticism so I can learn how to better help people.
liking it so far (been using for a day), i like the customization options for the UI. it took a bit in the setup thingy... it took a couple tries to get passed the "checking for update" spot. but it runs nicely now
Hi Bro., Can I flash this Rom on t355y ?
1. please read this very carefuly.this guide is made from my personal experience.
like some members of this forums told me and i think a little about it,there can be problem about downgrade to oreo with devices who have unlock device from operator.but i believe can be easily unlock with talk with operators,not sure,but be best to check it out by self.
firstly i am not noob,i am developer and compiler for many mtk device. sadly this is my FIRST
samsung device also snapdragon. so for me completely unknown.i want in first root and do custom roms but untill now
i dont find any device tree for this device.kernel source i have but device and vendor tree not.then i found i can
flash gsi on this device. so i do as i will explain in following text.
2. as many other of you i have update device on PIE and next days i install update i found possibility to flash gsi,
so i try. i found patched pie boot.img and try to flash gsi roms but none of them isnt boot.so i stop and again read gsi guide
for flash gsi.i read that devices shipped with some firmwares have chance to flash gsi roms.so i found oreo rom
for our device and flash it with odin.rom is boot without any problems.i set up all things as normall(google account)
and after all setup i go to device info and tap on build numbers 7-10 times and then developer settings is open,then i
checked if is there oem unlocking.(if you dont set up google account this settings will not shown(oem unlocking)).
when i see is ok and there,i power off device,go to download mode and connect with pc,and open odin,
and flash twrp(again thanks to ashyx).dont let odin to boot system(turn off auto rebbot in option),
so i reboot to recovery,go to wipe,choose format data,write yes and swipe.
after that i reboot to recovery you MUST flash oreo enforcing.zip,rmm and oreo patched boot.and go to install choose micro sd card and go to flash img. choose gsi rom you want and
flash it as system(pop up windows will ask wich partition you choose(system),then swipe to flash,after flashing you flash magisk,
and go to mount and mount system and reboot to system. firstly your device can reboot once-twice during,but dont worry
after that will go to boot and in short time,one- two minutes will boot.
3.now i must warning you.many of gsi roms work properly,but have many bugs.mtp dont works with pc in boot up,but in recovery
works without problems.for me is not problem,i can live with it.
3.1.sim card 2 is work but sim card 1 is not see it.also i can live with it.most of time i use 1 sim card,not both.
3.2.fm radio isnt show,and not work.
4.in short i give you again flash guide.
go to recovery (must be in oreo)
go to wipe-format data,write yes and swipe to format (many say to need back to recovery,i didnt do that but is your choice).
go to sd card and install oreo enforcing.zip,RMM bypass.zip and oreo patched boot.img
go to install and choose flash.img and choose gsi you want,and flash as system
go to install zip and flash magisk
then go to mount,mount system and reboot to system
device will reboot twice or more time and then after minute or two will reboot.be calm.
after device is reboot,enjoy.:good:
i will post some screenshots of booted gsi roms.oreo and pie.
list of booted gsi rom so far:
1. aex 5.7 oreo
2. aex 6.5 pie
3. aosdp pie(this rom not show network and sim cards)
4. aosp by phusson pie
5. bootlegger oreo
6. descendant 3.0 pie
7. dot os pie(dont show network and simcards)
8. havoc os pie
9. lineage 16 pie
10. RR oreo
11. RR pie
12. system DU oreo
13. xenon hd oreo
GSI with errors:
AOSDP (not shown sim cards,no network,all other stuff work,off course no fm radio)
Evolution X (dont want to boot.)
Octopus OS (dont boot)
Viper OS Official (not shown sim cards,all other stuff work except fm radio)
Dot OS (dont show sim cards,no network,no fm radio)
Liquid Remix (dont boot)
Omni rom (boot but goes constantly on reboot)
Pixel Expirience (boot but no sim cards and no network and no fm radio)
people one more notice: j4+ is ARM A ONLY device,dont flash any other gsi.
deleted
What version of RR Pie did you test? The May Release?
JDBS30 said:
What version of RR Pie did you test? The May Release?
Click to expand...
Click to collapse
all of them.
this link i used and choose one of them from your choice arm a only of course: https://get.resurrectionremix.com/?dir=gsi
I can't install Resurrection Remix
I face so much problems while installing custom roms, I tried Android Pie GSI, Pixel Experience, Resurrection Remix. But All of them crashes at boot animation. What can I do? I can't find any thread about that.
My phone is Samsung Galaxy J4+ (arm aonly).
Please help me?
elfennani said:
I face so much problems while installing custom roms, I tried Android Pie GSI, Pixel Experience, Resurrection Remix. But All of them crashes at boot animation. What can I do? I can't find any thread about that.
My phone is Samsung Galaxy J4+ (arm aonly).
Please help me?
Click to expand...
Click to collapse
my dear friend did you read my guide?. i explain wich gsi roms can flash and how.please read from start to end.it is very clear.
rudi021 said:
my dear friend did you read my guide?. i explain wich gsi roms can flash and how.please read from start to end.it is very clear.
Click to expand...
Click to collapse
Yes, I read everything, I tried Pixel Experience and Android Pie GSI before seeing this thread. So I decided to try Resurrection Remix, But it crashes while boot animation then after the phone gets restarted (bootloop)
elfennani said:
Yes, I read everything, I tried Pixel Experience and Android Pie GSI before seeing this thread. So I decided to try Resurrection Remix, But it crashes while boot animation then after the phone gets restarted (bootloop)
Click to expand...
Click to collapse
like i wrote your device must be on oreo,not on pie.thats my expirience.when i was on pie i cant boot any pie rom.after i flash oreo stock rom and flash twrp i flash and boot almost any gsi wich is aviable.you must be on oreo stock rom and then flash twrp,then flash oreo enforcing,rmm,then format data(write yes and swipe to format),then flash gsi as system,flash magisk,then go to mount and check system then reboot.thats it. maybe is my mistake i didnt write that you must do flash those thing before,but i supose people is knowing what must to do when do flash twrp. sorry.
rudi021 said:
like i wrote you must be on oreo,not on pie.thats my expirience.when i was on pie i cant boot any pie rom.after i flash oreo stock rom and flash twrp i flash and boot almost any gsi wich is aviable.you must be on oreo stock rom and then flash twrp,then flash oreo enforcing,rmm,then format data(write yes and swipe to format),then flash gsi as system,flash magisk,then go to mount and check system then reboot.thats it. maybe is my mistake i didnt write that you must do flash those thing before,but i supose people is knowing what must to do when do flash twrp. sorry.
Click to expand...
Click to collapse
How did you downgrade your firmware?
elfennani said:
How did you downgrade your firmware?
Click to expand...
Click to collapse
i found oreo firmware. if you want you can download from my google drive. here is link: https://drive.google.com/file/d/1KnqHZ8_EVTstJP5AMsMy_8Uc1QV-vMHe/view?usp=sharing
Please help
rudi021 said:
1. please read this very carefuly.this guide is made from my personal experience.
like some members of this forums told me and i think a little about it,there can be problem about downgrade to oreo with devices who have unlock device from operator.but i believe can be easily unlock with talk with operators,not sure,but be best to check it out by self.
firstly i am not noob,i am developer and compiler for many mtk device. sadly this is my FIRST
samsung device also snapdragon. so for me completely unknown.i want in first root and do custom roms but untill now
i dont find any device tree for this device.kernel source i have but device and vendor tree not.then i found i can
flash gsi on this device. so i do as i will explain in following text.
2. as many other of you i have update device on PIE and next days i install update i found possibility to flash gsi,
so i try. i found patched pie boot.img and try to flash gsi roms but none of them isnt boot.so i stop and again read gsi guide
for flash gsi.i read that devices shipped with some firmwares have chance to flash gsi roms.so i found oreo rom
for our device and flash it with odin.rom is boot without any problems.i set up all things as normall(google account)
and after all setup i go to device info and tap on build numbers 7-10 times and then developer settings is open,then i
checked if is there oem unlocking.(if you dont set up google account this settings will not shown(oem unlocking)).
when i see is ok and there,i power off device,go to download mode and connect with pc,and open odin,
and flash twrp(again thanks to ashyx).dont let odin to boot system(turn off auto rebbot in option),
so i reboot to recovery,go to wipe,choose format data,write yes and swipe.
after that i reboot to recovery you MUST flash oreo enforcing.zip,rmm and oreo patched boot.and go to install choose micro sd card and go to flash img. choose gsi rom you want and
flash it as system(pop up windows will ask wich partition you choose(system),then swipe to flash,after flashing you flash magisk,
and go to mount and mount system and reboot to system. firstly your device can reboot once-twice during,but dont worry
after that will go to boot and in short time,one- two minutes will boot.
3.now i must warning you.many of gsi roms work properly,but have many bugs.mtp dont works with pc in boot up,but in recovery
works without problems.for me is not problem,i can live with it.
3.1.sim card 2 is work but sim card 1 is not see it.also i can live with it.most of time i use 1 sim card,not both.
3.2.fm radio isnt show,and not work.
4.in short i give you again flash guide.
go to recovery (must be in oreo)
go to wipe-format data,write yes and swipe to format (many say to need back to recovery,i didnt do that but is your choice).
go to sd card and install oreo enforcing.zip,RMM bypass.zip and oreo patched boot.img
go to install and choose flash.img and choose gsi you want,and flash as system
go to install zip and flash magisk
then go to mount,mount system and reboot to system
device will reboot twice or more time and then after minute or two will reboot.be calm.
after device is reboot,enjoy.:good:
i will post some screenshots of booted gsi roms.oreo and pie.
list of booted gsi rom so far:
1. aex 5.7 oreo
2. aex 6.5 pie
3. aosdp pie(this rom not show network and sim cards)
4. aosp by phusson pie
5. bootlegger oreo
6. descendant 3.0 pie
7. dot os pie(dont show network and simcards)
8. havoc os pie
9. lineage 16 pie
10. RR oreo
11. RR pie
12. system DU oreo
13. xenon hd oreo
GSI with errors:
AOSDP (not shown sim cards,no network,all other stuff work,off course no fm radio)
Evolution X (dont want to boot.)
Octopus OS (dont boot)
Viper OS Official (not shown sim cards,all other stuff work except fm radio)
Dot OS (dont show sim cards,no network,no fm radio)
Liquid Remix (dont boot)
Omni rom (boot but goes constantly on reboot)
Pixel Expirience (boot but no sim cards and no network and no fm radio)
people one more notice: j4+ is ARM A ONLY device,dont flash any other gsi.
Click to expand...
Click to collapse
Thank you for sharing your experience. I was planning on trying to flash a GSI, but I have to wait 7 days for the OEM unlock on Stock Oreo. Of these files you listed, I do not have the "oreo patched boot." This is also necessary, and if so, where do I find it?
Thank you in advance and I count on your help.
Maxmiliano Coelho said:
Thank you for sharing your experience. I was planning on trying to flash a GSI, but I have to wait 7 days for the OEM unlock on Stock Oreo. Of these files you listed, I do not have the "oreo patched boot." This is also necessary, and if so, where do I find it?
Thank you in advance and I count on your help.
Click to expand...
Click to collapse
my dear friend just ask i will help you. this patched boot.img is made by ashyx. i will be bad member if i share his works without permissions.so i share with you his link. here is link for oreo patched boot.img https://androidfilehost.com/?fid=1395089523397921797
please follow instructions carefully. read twice and try to understand.enjoy.if you have any doubt please ask. thank you.
Thanks again. I am waiting for the 7 day period to reappear the OEM unlock option which disappeared when I returned to stock oreo. With your help, the procedure to be performed became clearer. When I do the procedure, can I continue to ask questions if any? I thank you once again.
Maxmiliano Coelho said:
Thanks again. I am waiting for the 7 day period to reappear the OEM unlock option which disappeared when I returned to stock oreo. With your help, the procedure to be performed became clearer. When I do the procedure, can I continue to ask questions if any? I thank you once again.
Click to expand...
Click to collapse
why not.i am not star just ask and if i can help i will please to do that.you can always send me personal message(PM) on xda
Maxmiliano Coelho said:
Thanks again. I am waiting for the 7 day period to reappear the OEM unlock option which disappeared when I returned to stock oreo. With your help, the procedure to be performed became clearer. When I do the procedure, can I continue to ask questions if any? I thank you once again.
Click to expand...
Click to collapse
like https://forum.xda-developers.com/member.php?u=9101376 say in reply if you have unlock before then your device is unlocked.so no need to wait another 7 days.you must just do follow tread for flash recovery.can miss first time,two but read guide and no fear.but you cant miss if you try again. once your device is unlock you can flash no metter numbers of flashing roms(stock 8 or 9)once is unlock thats it.so dont be affraid to ask help here or anywhere on our xda group.always some will help you.:good:
rudi021 said:
like https://forum.xda-developers.com/member.php?u=9101376 say in reply if you have unlock before then your device is unlocked.so no need to wait another 7 days.you must just do follow tread for flash recovery.can miss first time,two but read guide and no fear.but you cant miss if you try again. once your device is unlock you can flash no metter numbers of flashing roms(stock 8 or 9)once is unlock thats it.so dont be affraid to ask help here or anywhere on our xda group.always some will help you.:good:
Click to expand...
Click to collapse
Thank you! I followed in his footsteps and was successful in installing LineageOS 16. Working very well, but I felt a slight problem regarding the audio volume, which is extremely low.
I would like to ask one more question, which is about testing other GSI: Is there a need to install one of those files, or just the image and Magisk?
Thank you very much.
Maxmiliano Coelho said:
Thank you! I followed in his footsteps and was successful in installing LineageOS 16. Working very well, but I felt a slight problem regarding the audio volume, which is extremely low.
I would like to ask one more question, which is about testing other GSI: Is there a need to install one of those files, or just the image and Magisk?
Thank you very much.
Click to expand...
Click to collapse
once you perform flashing gsi,no need repeat every time this steps,just (at least i do like that) format data,reboot to recovery,flash gsi(as system.image) and flash magisk then mount system and reboot.about audio volume install viper fx audio apk(Magisk module),and then fix volume as your own.
kapmino269 said:
If anyone faced problems with booting some roms on
ROM LOGO NOT SAMSUNG .
use this :
https://www.androidfilehost.com/?fid=6006931924117925309
Tested on j415f
RR
AOSP
DESCENDANT ZERO .
Click to expand...
Click to collapse
sorry but this doesnt work on my side of flashing GSI.OREO base. i try on many gsi who doesnt boot but not help. i boot this PIE gsi (on oreo base): descendant 3.1.1.; Prisma os(still cant find way to get network,no sim detected);Havoc os (works perfectly);Dot os 3.0 (same no sim detect); RR 2019-04-06 very nice rom; AEX by enes sastim 2019-05-09(also very nice rom);Viper os (but is Official and dont let use it)(mean boot but no sim works);Zirconium aosp (work well but seems like android kitkat seems so simple(i dont like it);and many more with same problems,they booted but not have network work, or like omni rom booted but reboot and then all over again.have many roms but have problems with our device(mine is sm-j415fn). anyway i try do same in PIE update but cant boot any rom (gsi). why ? dont know? thats why i downgrade in oreo and can flash and boot almost all gsi on list. did they work or not is other story.thank you.
rudi021 said:
sorry but this doesnt work on my side of flashing GSI.OREO base. i try on many gsi who doesnt boot but not help. i boot this PIE gsi (on oreo base): descendant 3.1.1.; Prisma os(still cant find way to get network,no sim detected);Havoc os (works perfectly);Dot os 3.0 (same no sim detect); RR 2019-04-06 very nice rom; AEX by enes sastim 2019-05-09(also very nice rom);Viper os (but is Official and dont let use it)(mean boot but no sim works);Zirconium aosp (work well but seems like android kitkat seems so simple(i dont like it);and many more with same problems,they booted but not have network work, or like omni rom booted but reboot and then all over again.have many roms but have problems with our device(mine is sm-j415fn). anyway i try do same in PIE update but cant boot any rom (gsi). why ? dont know? thats why i downgrade in oreo and can flash and boot almost all gsi on list. did they work or not is other story.thank you.
Click to expand...
Click to collapse
me i have not a network on aex extended but on dot os i have
Envoyé de mon Phh-Treble vanilla en utilisant Tapatalk
kapmino269 said:
Guys , sorry I found error in my script and I fixed it I tested it on AEX official , I will test it in others then post it .
@rudi021
---------- Post added at 09:15 AM ---------- Previous post was at 08:29 AM ----------
v2 : https://www.androidfilehost.com/?fid=6006931924117930007
tested : work with rom logo bootloop 100%
Click to expand...
Click to collapse
thank you bro. i definetly try this on pie upgrade and inform you.thank you for your hard work. i am on vacation and when i come home i will try this.thank you and greetings from Croatia.:good:
also i stop build gsi roms for j4+ because my pc is old so i need little upgrade of same( RAM(have only 4 gb,need for pie at least 8 gb ,my motherboard can have 32 gb,), my processor is i3 but i will upgrade on i5 and after that i will continue work on it. but now i am on vacation with my wife and children and when i come hom ei will continue to work it.thank you once more.