Related
I unlocked the bootloader following Motorolas steps. I then flashed the latest version of TWRP avaiable on the development forum and then flashed Lineage OS + the root zip they provide and gapps. I couldn't figure out how to get out of the bootloop so I've since gone back to stock. Any idea what I was missing?
TWRP:
https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629
Lineage:
https://forum.xda-developers.com/moto-z-play/development/rom-unofficial-cyanogenmod-14-1-t3495644
Did you read the notices and entries on the Linage last pages of the thread that people are having it fail on the install, the latest release? That would be a clue...
I even tried flashing Pure Nexus but that too was stuck on a loop. I left it for about 10 minutes as it was loading. :/
I did the same thing like you on my first attempt, on my second I was able to install Lineage OS successfully. I'll provide the steps I did.
First attempt steps:
1. Unlocking the bootloader using Motorola website
2. Installing TWRP from the same link in your post.
At that point I tried booting the phone, but the phone was booting to TWRP only, tried wiping, format data from TWRP with no luck.
3. From TWRP flashed Lineage OS zip file and GAPPS nano package (the latest version of TWRP is able to see SD card).
At that point I was able to to boot LOS only after executing "fastboot erase user data". Doing the same from within TWRP was not doing the job. The problem was that after each reboot the phone was getting into bootloop again and "fastboot erase userdata" was necessary.
4. At that point I noticed that TWRP thread starts with warning that you have to install a patcher to disable this "verity" feature of the bootloader may be. And I installed the patcher "Verity_FE_patcher.zip"
The patcher didn't fix the issue and went back to stock Nougat using the guide below:
https://forum.xda-developers.com/moto-z-play/how-to/moto-z-play-reteu-firmware-otas-t3557917
First I tried "flashall.bat" , but it didn't wor.k and I flashed all the files manually using the guide . The phone booted normally and I updated it with one OTA update.
Second attempt steps:
1. I wanted to install the verity patcher before anything else and I boot TWRP 3.1.0.1 without flashing it. It booted normally and I realized that the SD card was formated and the patcher zip file is not there. I reboot the system and the phone got in bootloops again even the TWRP was not installed. I coppied the patcher zip, LOS zip, GAPPS zip on SD card . I tried to boot (without flashing) TWRP again, but for some reason TWRP was not able to boot.
2. I flashed TWRP
3. Booted TWRP and flashed verity patcher.
4. Wiped from TWRP and boot the system
At that point I was able to boot the stock firmware with TWRP installed and I was able to restart the phone normally.
5. Flashed LOS and nano GAPPS
Now everything seems to work properly.
Hope this will help.
Thanks. I'll give this a shot tonight. Our first attempts sound very alike.
Installed trwp and flashed multiple times my wileyfox swift to lineage 14.1
Swift wont boot gets stuck in bootloader....
Found a 14.0 image (linage) somewhere.... this works with no problems but seems an older built (buggy)
Anyone has 14.1 lineage on a swift with no problems ???
You can try installing Lineage 14.1. from CM13, see posts #155/#156 in thread 'Nightly 14.1 lineageOS Rom For Crackling'
went back to cyanogen the original firmware
Found the original firmware and twrp flashed back to that one...
https://forum.xda-developers.com/showpost.php?p=70510585&postcount=19
Old firmware but was happy with that one so.... problem solved....
Same bootloop on Wileyfox Swift, how did you...
...install the old COS on your Swift?
I downloaded all the files from G4liant's MEGA cloud storage but don't know how to continue.
Please, help if you can (see my reply to his post, too (as of today 25. June 2017)).
Thanks!
jwalesch
__________________________________________________________________________
eskodisk said:
Found the original firmware and twrp flashed back to that one...
https://forum.xda-developers.com/showpost.php?p=70510585&postcount=19
Old firmware but was happy with that one so.... problem solved....
Click to expand...
Click to collapse
original firmware
jwalesch said:
...install the old COS on your Swift?
I downloaded all the files from G4liant's MEGA cloud storage but don't know how to continue.
Please, help if you can (see my reply to his post, too (as of today 25. June 2017)).
Thanks!
jwalesch
__________________________________________________________________________
Click to expand...
Click to collapse
Do you have TWRP recovery installed on your wileyfox ?
Via the twrp recovery, you can install what is in one of the zipfiles
I guess this one :
cm-13.1.2-ZNH2KAS3LG-crackling-signed-42f2b8e414.zip
MD5: 0AEF4E4A468EF34A6DA65712156ECB2C
contains the twrp installable original firmware....
Installing works the same as you would eg install a lineage custom rom.... TWRP is rather fool proof... I tried to install some of the other files, in the other zipfiles and twrp just refused... so ... try.... no need to install google apps here, everything is in the image... As you will see in the filesize of het image, it is rather big, compared to the lineage custom roms... Everthing is there....
If you are so far... Let me know, i learned that you will have to disable the wileyfox to keep looking for updates, wileyfox will download over and over again the upgrade files, was kind of annoying...
TWRP recovery cannot be loaded on Wileyfox Swift
Hi!
I had TWRP installed, in fact in different versions.
But for whatever reason I cannot boot into TWRP anymore which is precisely one of the problems I'm having now that I wanted to flash the Lineage OS again on a second Swift (I might have erased the partition that I installed TWRP to). But I cannot install TWRP again either...
All I can reach is the bootloader which does give you an option to restart recovery but it doesn't work. The phone is stuck in a bootloop returning whatever you do to the bootloader.
So, I hoped to find some help in treating the phone to a new or its original bootloader...
Thanks for helping!
jwalesch
__________________________________________________________________________
eskodisk said:
Do you have TWRP recovery installed on your wileyfox ?
Via the twrp recovery, you can install what is in one of the zipfiles
I guess this one :
cm-13.1.2-ZNH2KAS3LG-crackling-signed-42f2b8e414.zip
MD5: 0AEF4E4A468EF34A6DA65712156ECB2C
contains the twrp installable original firmware....
Installing works the same as you would eg install a lineage custom rom.... TWRP is rather fool proof... I tried to install some of the other files, in the other zipfiles and twrp just refused... so ... try.... no need to install google apps here, everything is in the image... As you will see in the filesize of het image, it is rather big, compared to the lineage custom roms... Everthing is there....
If you are so far... Let me know, i learned that you will have to disable the wileyfox to keep looking for updates, wileyfox will download over and over again the upgrade files, was kind of annoying...
Click to expand...
Click to collapse
I have found a way to install TWRP (different versions) but didn't know how to start it.
In this post I found how to:
https://forum.xda-developers.com/wileyfox-swift/help/foolproof-twrp-guide-wileyfox-swift-t3616571
It's keeping the volume down button held down until TWRP starts, then you can do everything from there.
Everything?
I installed Lineage OS 14.1 (nightly as of 2017/06/19) as well as GApps, wiped Cache/DALVIK and restarted the system.
The OS wouldn't start, only the bootloader could I get the phone to start.
So, TWRP is there, the OS is there, even GApps are there, I just cannot boot into the OS to use the phone.
Any new ideas?
jwalesch
jwalesch said:
Hi!
I had TWRP installed, in fact in different versions.
But for whatever reason I cannot boot into TWRP anymore which is precisely one of the problems I'm having now that I wanted to flash the Lineage OS again on a second Swift (I might have erased the partition that I installed TWRP to). But I cannot install TWRP again either...
All I can reach is the bootloader which does give you an option to restart recovery but it doesn't work. The phone is stuck in a bootloop returning whatever you do to the bootloader.
So, I hoped to find some help in treating the phone to a new or its original bootloader...
Thanks for helping!
jwalesch
__________________________________________________________________________
Click to expand...
Click to collapse
jwalesch said:
[...]
So, TWRP is there, the OS is there, even GApps are there, I just cannot boot into the OS to use the phone.
Any new ideas?
jwalesch
Click to expand...
Click to collapse
Try installing the system and the GApps separately:
Wipe again, install system, then boot to system, when Lineage has successfully booted for the first time (may take a couple of minutes), go back to TWRP and install GApps.
jwalesch said:
I have found a way to install TWRP (different versions) but didn't know how to start it.
In this post I found how to:
https://forum.xda-developers.com/wileyfox-swift/help/foolproof-twrp-guide-wileyfox-swift-t3616571
It's keeping the volume down button held down until TWRP starts, then you can do everything from there.
Everything?
I installed Lineage OS 14.1 (nightly as of 2017/06/19) as well as GApps, wiped Cache/DALVIK and restarted the system.
The OS wouldn't start, only the bootloader could I get the phone to start.
So, TWRP is there, the OS is there, even GApps are there, I just cannot boot into the OS to use the phone.
Any new ideas?
jwalesch
Click to expand...
Click to collapse
I had the same problem with lineage.... only bootloader when powering on.... That is the reason why I went back to the original firmware because that solved my problem.... I once found an older lineage rom suggested somewhere on the forum that worked and got me out of the bootloader but that version was buggy... Updating from there to a the latest linage got me back to the bootloader only problem....
I will stay on the cyonogenmod now.... Until perhaps someone can tell me how to really solve the bootloader only by power up problem....
eskodisk said:
[...]
I will stay on the cyonogenmod now.... Until perhaps someone can tell me how to really solve the bootloader only by power up problem....
Click to expand...
Click to collapse
Are you back on the cm-13.1.2-ZNH2KAS3LG-crackling-signed-fastboot-84f0d5200b.zip?
If so, you should be able to install and run TWRP 3.1.1.0.
TWRP then should be able to mount all partitions, including 'system'.
Then you can install the current Lineage via TWRP, wipe and restart system.
When Lineage has booted once, you can go back to TWRP and install the GApps.
Let me know if you get stuck at one point.
total backup of existing system ?
kabu83 said:
Are you back on the cm-13.1.2-ZNH2KAS3LG-crackling-signed-fastboot-84f0d5200b.zip?
If so, you should be able to install and run TWRP 3.1.1.0.
TWRP then should be able to mount all partitions, including 'system'.
Then you can install the current Lineage via TWRP, wipe and restart system.
When Lineage has booted once, you can go back to TWRP and install the GApps.
Let me know if you get stuck at one point.
Click to expand...
Click to collapse
Can i backup my existing system in twrp... I tried lineage a dozen times before and always got stuck on bootloader. So can I backup my current setup because at the moment everything works as it should.... ????? I formatted my sd card as system memory so... ????
If TWPR is running and you can mount the system partition, you should be able to make a back-up via TWRP. (Not of your pictures, music and so on, see TWRP disclaimer.)
Install LineageOS from a running cm-13.1.2-ZNH2KAS3LG-crackling
Hi there!
Yes, my Wileyfox Swift is running the CyanogenMOD version cm-13.1.2-ZNH2KAS3LG-crackling.
Everything seems to be OK, it just wants to keep downloading an update which I can save but when I'm asked to install it the normally automatic installation process doesn't work:
The phone reboots back to TWRP but doesn't show the just downloaded .zip file (which normally would happen) and doesn't install it either. Installation stops in TWRP, when I tap on REBOOT > SYSTEM the OS reboots normally but shows the OS version I had before.
Can you tell me where these update .zip files are saved so that I could install it maybe from the TWRP's file manager?
If that doesn't work I would try to update TWRP and after that install the current Lineage OS over the CM 13.1.2 as you suggested.
Thanks for helping!
jwalesch
________________________________________________________________________________________________
kabu83 said:
Are you back on the cm-13.1.2-ZNH2KAS3LG-crackling-signed-fastboot-84f0d5200b.zip?
If so, you should be able to install and run TWRP 3.1.1.0.
TWRP then should be able to mount all partitions, including 'system'.
Then you can install the current Lineage via TWRP, wipe and restart system.
When Lineage has booted once, you can go back to TWRP and install the GApps.
Let me know if you get stuck at one point.
Click to expand...
Click to collapse
jwalesch said:
Hi there!
Yes, my Wileyfox Swift is running the CyanogenMOD version cm-13.1.2-ZNH2KAS3LG-crackling.
Everything seems to be OK, it just wants to keep downloading an update which I can save but when I'm asked to install it the normally automatic installation process doesn't work:
The phone reboots back to TWRP but doesn't show the just downloaded .zip file (which normally would happen) and doesn't install it either. Installation stops in TWRP, when I tap on REBOOT > SYSTEM the OS reboots normally but shows the OS version I had before.
Can you tell me where these update .zip files are saved so that I could install it maybe from the TWRP's file manager?
If that doesn't work I would try to update TWRP and after that install the current Lineage OS over the CM 13.1.2 as you suggested.
Thanks for helping!
jwalesch
________________________________________________________________________________________________
Click to expand...
Click to collapse
What update does it want to keep downloading? I guess it might be the official stock 7.1.1..
You probably need to download the Lineage.zip manually from official Lineage downloads.
Then restart to TWRP and install the Lineage.zip.
TWRP has a toggle button in the lower left corner, where you can switch from 'Install image' to 'Install zip'. With 'install zip', you should find the zip.
The update is cm-13.1.2-ZNH2KAS7EB-crackling.
I have it ready to be installed on the phone but it won't show in any filemanager, be it in TWRP nor the system's filemanager nor AMAZE filemanager which I also installed.
So, I assume the download either isn't actually saved properly or it's a hidden file or something of that sort.
In other threads they say that updates were saved to a folder called "cmupdater". I cannot find any folder with that name either.
I also have the latest LineageOS .zip file ready to be installed on my phone and have tried to install that from TWRP (by the way: Now running the latest version for the Wileyfox Swift, ie. twrp-3.1.1-0-crackling). All it does is it produces an error saying something like "Error 7... cannot be installed".
SOLVED for now:
From here https://cyanogenupdatetracker.com/downloads/ I downloaded the latest available CM version (SW27-WF-CRACKLING-CM-13.1.5-ZNH2KAS7EB-RECOVERY.zip) which seemed to be exactly the one that my phone kept downloading and couldn't install.
I copied it to my external sd card and installed it from there via TWRP.
After that the system rebooted normally, Android then updated all my installed apps and now the system is downloading yet another update:
Android 7.1.1 (Nougat) - TOS111B
As I know that version of Android on the Wileyfox it's not actually something I would want to install myself. But I shall try to install the latest Lineage OS instead.
Let's keep each other posted (in German?)!
___________________________________________________________________________________________________
kabu83 said:
What update does it want to keep downloading? I guess it might be the official stock 7.1.1..
You probably need to download the Lineage.zip manually from official Lineage downloads.
Then restart to TWRP and install the Lineage.zip.
TWRP has a toggle button in the lower left corner, where you can switch from 'Install image' to 'Install zip'. With 'install zip', you should find the zip.
Click to expand...
Click to collapse
jwalesch said:
The update is cm-13.1.2-ZNH2KAS7EB-crackling.
I have it ready to be installed on the phone but it won't show in any filemanager, be it in TWRP nor the system's filemanager nor AMAZE filemanager which I also installed.
So, I assume the download either isn't actually saved properly or it's a hidden file or something of that sort.
In other threads they say that updates were saved to a folder called "cmupdater". I cannot find any folder with that name either.
I also have the latest LineageOS .zip file ready to be installed on my phone and have tried to install that from TWRP (by the way: Now running the latest version for the Wileyfox Swift, ie. twrp-3.1.1-0-crackling). All it does is it produces an error saying something like "Error 7... cannot be installed".
SOLVED for now:
From here https://cyanogenupdatetracker.com/downloads/ I downloaded the latest available CM version (SW27-WF-CRACKLING-CM-13.1.5-ZNH2KAS7EB-RECOVERY.zip) which seemed to be exactly the one that my phone kept downloading and couldn't install.
I copied it to my external sd card and installed it from there via TWRP.
After that the system rebooted normally, Android then updated all my installed apps and now the system is downloading yet another update:
Android 7.1.1 (Nougat) - TOS111B
As I know that version of Android on the Wileyfox it's not actually something I would want to install myself. But I shall try to install the latest Lineage OS instead.
Let's keep each other posted (in German?)!
___________________________________________________________________________________________________
Click to expand...
Click to collapse
English is forum language I guess, you could probably send me a private message to clarify anything in German.
I also had the error 7 issue when installing Lineage, you need to wipe system (you will loose everything though, it is not possible to install Lineage over Cyanogen, like a dirty flash).
In TWRP, choose Wipe/advanced Wipe/ tick system only / repair, 2F2S. After that, format data.
Then the installation of Lineage with TWRP should run through. Let the system boot for the first time, if it runs, boot back to TWRP and install GApps.
With that method, I am on LOS nigthly 20170626 now and happy.
Hi kabu83!
Thanks a lot for your last reply - it helped me to finally get Lineage OS 14.1 installed!
At the moment the phone is rebooting the system after installing the GApps, everything seems to run smoothly and - guess what - I'm happy, too, now!
How about sending me a PM? (As I have no clue as to how that works it would be nice if you could send me that one more reply to let me know.)
Hello everyone,
after installing Omni-Rom without gapps I tried to install gapps via adb sideload on stock recovery.
Unfortunately no device was shown in device manager when starting sideload.
Anyone faced this issue?
Is there another way to install gapps?
Thank you!
No.
Stock recovery can only install official updates zip files, approved by OEM.
To install anything unofficial, like OpenGApps, you need a custom recovery, like TWRP.
BTW, I never get the sideload feature of official recovery to work in any phone I tried it (not much to tell the truth, but looks like a fake feature).
BubuXP said:
No.
Stock recovery can only install official updates zip files, approved by OEM.
To install anything unofficial, like OpenGApps, you need a custom recovery, like TWRP.
BTW, I never get the sideload feature of official recovery to work in any phone I tried it (not much to tell the truth, but looks like a fake feature).
Click to expand...
Click to collapse
Thank you! I wanted to install gapps on omni treble gsi...
Solved by copying zip to system partition, installing twrp, formatting data, installing gapps with twrp, reinstalling stock recovery and formatting data again with stock recovery...
What a waste of time... Hope we will get a working twrp soon.
Btw. have you tried to use the phone unencrypted with rooted stock kernel? With editing vendor > etc > fstab.qcom forceencrypted to encryptable it works, but without wifi in rom.
The question is: will reflashing the stock kernel/recovery heal that wifi problem? I would try, but right now everythin is set up fine - perhaps you already tried...
If that would work, then it would be easy to use twrp. Then you only would need to change the boot.img after using twrp...
So I've been following DavidRocher's tutorial to install a custom rom (the one that's linked around here the most), I've followed it before installing his RR official rom but as the room started showing a lot of issues, I decided to wipe everything and install something a little more stable such as lineage. I didn't care for Gcam or etc so I wouldn't have minded not having those at all.
However, even after following these steps now once again, even flashing the stock rom as asked for a brand new, clean install, twrp (offain) is hitting me with Error 1s on *any* custom rom that I try installing. I can seemingly flash the stock rom without any issues, but anything else and it's a solid no from TWRP.
Am I missing something?
The error itself is Error applying update: 28 (ErrorCode:: kDownloadOperationExecutionError) Updater process ended with Error: 1 error installing zip file.
I've been wiping, booting, rebooting, re-installing the custom rom, checking the unlocked bootloader and I have had no progress at all. I do not know why this is happening, could anyone please help me?
So, I found out that the -only- rom I can install is the one I originally installed, DavidRocher's official RR which seems to be no longer maintained. Which is also the rom I'm trying to get rid of... This doesn't sem to make any sense, does anyone have -any advice- at all?
JumboTSB said:
So, I found out that the -only- rom I can install is the one I originally installed, DavidRocher's official RR which seems to be no longer maintained. Which is also the rom I'm trying to get rid of... This doesn't sem to make any sense, does anyone have -any advice- at all?
Click to expand...
Click to collapse
Please can you describe exactly the steps that you did from boot to recovery and so?
SubwayChamp said:
Please can you describe exactly the steps that you did from boot to recovery and so?
Click to expand...
Click to collapse
Steps followed were:
Flashing stock daisy_global_images_V10.0.3.0.PDLMIXM_9.0 (flash_all.bat from bigota.d.miui.com/V10.0.3.0.PDLMIXM/daisy_global_images_V10.0.3.0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz)
Turning the phone off after it booted successfully;
Turning it on in fastboot;
Booting offain's twrp-daisy-3.3.0-0-offain.img through fastboot (fastboot boot twrp-daisy-3.3.0-0-offain.img);
No password entered;
Format Data;
Pushing custom rom & twrp;
Attempting to flash custom rom in any of the slots. At this point, it fails and gives me the error on any rom except the official Resurrection Remix rom from DavidRocher, which I can successfully install alongside twrp and force encryption disabler, change slots, install gapps and magisk and boot.
*Any* other rom just fails with that specific error code.
JumboTSB said:
Steps followed were:
Flashing stock daisy_global_images_V10.0.3.0.PDLMIXM_9.0 (flash_all.bat from bigota.d.miui.com/V10.0.3.0.PDLMIXM/daisy_global_images_V10.0.3.0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz)
Turning the phone off after it booted successfully;
Turning it on in fastboot;
Booting offain's twrp-daisy-3.3.0-0-offain.img through fastboot (fastboot boot twrp-daisy-3.3.0-0-offain.img);
No password entered;
Format Data;
Pushing custom rom & twrp;
Attempting to flash custom rom in any of the slots. At this point, it fails and gives me the error on any rom except the official Resurrection Remix rom from DavidRocher, which I can successfully install alongside twrp and force encryption disabler, change slots, install gapps and magisk and boot.
*Any* other rom just fails with that specific error code.
Click to expand...
Click to collapse
Try after to reboot to recovery, before of doing nothing or flash anything:
- Flash the TWRP installer.
- Then Wipe cache/dalvik, system and data
- Then Format data.
- Then change slot and reboot to recovery again.
- Now try to follow the usual steps by flashing rom, TWRP, changing slot, etc.
- If didn´t work change the place where it is the rom, extSDCard instead of internal memory or instead adb sideload.
SubwayChamp said:
Try after to reboot to recovery, before of doing nothing or flash anything:
- Flash the TWRP installer.
- Then Wipe cache/dalvik, system and data
- Then Format data.
- Then change slot and reboot to recovery again.
- Now try to follow the usual steps by flashing rom, TWRP, changing slot, etc.
- If didn´t work change the place where it is the rom, extSDCard instead of internal memory or instead adb sideload.
Click to expand...
Click to collapse
Attempted the following steps and adb sideload, error apparently still persists, sadly. This is just... So weird. It doesn't make any sense at all, maybe the official RR altered the partition sizes in some manner? I tried resizing/repairing them through TWRP and it also didn't change anything... ****.
JumboTSB said:
Attempted the following steps and adb sideload, error apparently still persists, sadly. This is just... So weird. It doesn't make any sense at all, maybe the official RR altered the partition sizes in some manner? I tried resizing/repairing them through TWRP and it also didn't change anything... ****.
Click to expand...
Click to collapse
The message through TWRP still the same? Try erasing boot partition where is allocated TWRP through
Code:
fastboot erase boot
then boot to offain TWRP, flash other recovery like Orange and see if this recovery can flash the rom and later flash again TWRP through Orange I don´t think that RR did that so I flashed both versions on my device and I don´t have this issue but if you sometime resized your partition I don´t guess that TWRP can restore it well, you could resize it again through the same method.
SubwayChamp said:
The message through TWRP still the same? Try erasing boot partition where is allocated TWRP through
Code:
fastboot erase boot
then boot to offain TWRP, flash other recovery like Orange and see if this recovery can flash the rom and later flash again TWRP through Orange I don´t think that RR did that so I flashed both versions on my device and I don´t have this issue but if you sometime resized your partition I don´t guess that TWRP can restore it well, you could resize it again through the same method.
Click to expand...
Click to collapse
I guess I'll try it with orange when I have a little more time then.. Spent the last 10-12 hours trying different procedures with twrp and they were pretty fruitless... It's still so weird, I'm definitely not new to flashing roms, I've done it so many times in the past and this is the very first time I get this sort of behavior. I'll update this once I try out OrangeFox.
hi!
your method has always worked for me, but this time I always get error 1.
I tried to install the pixel experience and lineage and nothing works, can you help me?
:good:
My device forum doesn't have instructions how to do it, i've posted asking there but better to ask here also. I found this post for the Mi A2 that isn't my device mines the Mi A3 https://forum.xda-developers.com/mi-a2/how-to/guide-discussion-aio-gsi-thread-mi-a2-t3933356
The device is A/B arm64 has slots a and b i dunno how that effects flashing here, flashing custom roms will install into the inactive slot then you gotta change your active slot to be the the slot it installed into, then install rest of files there, does this apply with gsi .img files also?
When i tried using flashing the .img file i used orangefox recovery wiped all partitions flashed to system, just says no os installed i will probably try doing that again and flashing DM-Verity & Forceencrypt Disabler and permissiver_v2.zip however who noes if that will help.
If someone can list the correct steps to flash using both fastboot method and twrp/orangefox recovery methods i would appreciate it. If it matters i was trying to flash android 10 gsi. I've seen many different methods listed depending on the device, so i guess that makes it harder to work out.
Thanks.
I've flashed it twice via TWRP with flashing DM-Verity & Forceencrypt Disabler and permissiver_v2.zip. Plus TWRP.
1st time it was into A slot. After 1st flashing I've restarted TWRP and booted into B slot. And then flashed slot B.
After rebooting and seeing Logo in 15 minutes - I've got Android.10
xVM said:
I've flashed it twice via TWRP with flashing DM-Verity & Forceencrypt Disabler and permissiver_v2.zip. Plus TWRP.
1st time it was into A slot. After 1st flashing I've restarted TWRP and booted into B slot. And then flashed slot B.
After rebooting and seeing Logo in 15 minutes - I've got Android.10
Click to expand...
Click to collapse
Thanks for the feedback, are you able to tell me the exact steps? like lets just say twrp is already installed and you factory reset, cleared all data.
Do you flash DM-Verity before you flash the rom? or after you flash the rom and what you just flash Forceencrypt Disabler and permissiver_v2.zip after installing the rom?
What i see with regular roms not gsi when you flash the rom if your on slot a it's actually installing it into slot b when you reboot that's where it is so you need to restart before flashing Magisk and other stuff. So i assume with the gsi maybe you need to reboot after installing as system image before flashing the other files?
Alister. said:
Thanks for the feedback, are you able to tell me the exact steps? like lets just say twrp is already installed and you factory reset, cleared all data.
Do you flash DM-Verity before you flash the rom? or after you flash the rom and what you just flash Forceencrypt Disabler and permissiver_v2.zip after installing the rom?
What i see with regular roms not gsi when you flash the rom if your on slot a it's actually installing it into slot b when you reboot that's where it is so you need to restart before flashing Magisk and other stuff. So i assume with the gsi maybe you need to reboot after installing as system image before flashing the other files?
Click to expand...
Click to collapse
Your better of using fastboot if flashing a gsi .img you dont need twrp really unless the rom is in a .zip format, or your wanting to add extras like magisk and such, or take a backup
Android 11
Did anyone tried Android 11 gsi??