Thought I'd post this since I felt a lot of people here needed it.
Steps to flash Pie GSI:
1.) Unlock your bootloader using the unlock app from https://www.asus.com/Phone/ZenFone-5Z-ZS620KL/HelpDesk_Download/
2.) Download the latest firmware (80.30.96.80 at the moment) from https://www.asus.com/Phone/ZenFone-5Z-ZS620KL/HelpDesk_BIOS/.
3.) Extract this firmware and grab payload.bin from it.
4.) Download payload_dumper from https://androidfilehost.com/?fid=818070582850510260.
5.) Extract payload_dumper and put payload.bin inside payload input.
6.) Open payload_dumper.exe and let it extract the contents of payload.bin
7.) You should find the extracted images in payload_output.
8.) Flash the vbmeta.img from payload_output using the command, "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img", this is done to disable dm-verity to let the GSI boot.
9.) Download the latest Phh Pie A/B GSI from https://github.com/phhusson/treble_experimentations/releases
10.) Extract and flash the GSI using the command, "fastboot flash system filename.img", replace filename with the name of the image.
11.) Reboot and you're done.
Known issues (on all GSIs):
1.) VoLTE doesn't work.
2.) Mobile network settings crashes... You can't change APN settings or whatever.
3.) Magisk is unusable since it appears to break a lot of things including RIL and WiFi.
Other than said issues, GSIs are mostly stable enough to use as daily drivers.
Thanks for a detailed guide!
Some screenshots will also be appreciated.
robinhood1808 said:
Thanks for a detailed guide!
Some screenshots will also be appreciated.
Click to expand...
Click to collapse
I don't use gsi now, attached screenshot from back when I did
kailashrs said:
I don't use gsi now, attached screenshot from back when I did
Click to expand...
Click to collapse
Thanks for the detailed guide. Can u tell what was the battery backup that u we're getting while on GSI since most of the Zenfone 5z users face issues with battery just curious. And how is the over all experience on custom rooms on 5z?? How about Camera, Sound etc?
Finally something atleast.. been waiting for something for this device...
vysakhnraju said:
Thanks for the detailed guide. Can u tell what was the battery backup that u we're getting while on GSI since most of the Zenfone 5z users face issues with battery just curious. And how is the over all experience on custom rooms on 5z?? How about Camera, Sound etc?
Click to expand...
Click to collapse
1.) sound, I don't think stereo mode works, outdoor mode wouldn't work either
2.) battery should be more or less same, didn't extensively test
3.) camera, you can't use the wide angle yet, you can use gcam tho, I guess
This is fantastic. It's working for me. Had to format internal storage, but small loss for working GSI.
Thanks for posting in this quiet community.
Can we flash 8.1 based stable ROM..??
Custom rom
kailashrs said:
I don't use gsi now, attached screenshot from back when I did
Click to expand...
Click to collapse
How did you go back to custom rom?
pannu2don said:
Can we flash 8.1 based stable ROM..??
Click to expand...
Click to collapse
They don't boot for some reason
drsandy71 said:
How did you go back to custom rom?
Click to expand...
Click to collapse
? I don't understand
kailashrs said:
? I don't understand
Click to expand...
Click to collapse
Thank you.. I solved my problem using the earlier guide for downgrading..
Custom rom
I didn't find vbmeta? Help me please
---------- Post added at 02:45 AM ---------- Previous post was at 02:12 AM ----------
X-san said:
This is fantastic. It's working for me. Had to format internal storage, but small loss for working GSI.
Thanks for posting in this quiet community.
Click to expand...
Click to collapse
Please provide vbmeta.img link..
---------- Post added at 02:46 AM ---------- Previous post was at 02:45 AM ----------
X-san said:
This is fantastic. It's working for me. Had to format internal storage, but small loss for working GSI.
Thanks for posting in this quiet community.
Click to expand...
Click to collapse
Please provide vbmeta.img link..
sathishdhaya said:
I didn't find vbmeta? Help me please
Click to expand...
Click to collapse
It's in the Asus factory image.
To be precise, it's in the payload.bin file in the factory image zip. You'll need to extract payload.bin and dump it to get vbmeta.img.
All the links and info you need are in the OP. Please read critically.
Edit:
You might just want vbmeta, but it's best to follow the instructions and download the factory image.
You can use the factory image to go back to stock and/or flash a clean boot.img.
8.) Flash the vbmeta.img from payload_output using the command, "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img", this is done to disable dm-verity to let the GSI boot.
Thanks for your efforts - When flash by using above command - error msg coming as below
PS C:\Windows\system32> fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
C:\adb\fastboot.exe: unknown option -- disable-verity
Pls help me out.
If we try the same with pie based stock rom that is released, will the bugs mentioned in the first posr work now? Has Anyone tried it?
Tried GSI rom on Zenfone 5z after Pie update and then revert to asus stock rom
1)VoLTE doesn't work. - Could not check
2.) Mobile network settings crashes... You can't change APN settings or whatever. - Still not working
3.) Magisk is unusable since it appears to break a lot of things including RIL and WiFi. - Did not tried
4) Camera is slow dam slow
Update
shaz.mrd said:
Tried GSI rom on Zenfone 5z after Pie update and then revert to asus stock rom
1)VoLTE doesn't work. - Could not check
2.) Mobile network settings crashes... You can't change APN settings or whatever. - Still not working
3.) Magisk is unusable since it appears to break a lot of things including RIL and WiFi. - Did not tried
4) Camera is slow dam slow
Click to expand...
Click to collapse
RR GSI work great
sim setting page doesn't crash but sim cannot be deactivated
will provide more update after few days usages
RR gsi does not have gapps
shaz.mrd said:
RR GSI work great
sim setting page doesn't crash but sim cannot be deactivated
will provide more update after few days usages
Click to expand...
Click to collapse
Was unable to install gapps via twrp.
Currently on pixel experience rom, So far all good
shaz.mrd said:
Was unable to install gapps via twrp.
Currently on pixel experience rom, So far all good
Click to expand...
Click to collapse
Volte working?
---------- Post added at 01:49 AM ---------- Previous post was at 01:48 AM ----------
And incase if I follow the steps provided... How to install twrp ?
Related
Tutorial(downgrade8.1.0=>7.1.1)use nougat stok/custom-roms on Oreo BC-12 bootloader
This tutorial is for the users wich are not satisfied by Oreo 8.1.1 rom
Also can be used by users wich changed the touchscreen from some reazons
and on Oreo 8.1.1 this new touchscreen not work
First got to Settings/System/Developer option and chec OEM-unlockin to be ENABLED!
for flashing twrp-recovery may be need to unlock the bootloader by code but it should work only with OEM-unlocking enabled
Downgrading with FASTBOOT!
1) Charge youre phone to at least 50-70%, better is 100%
2) Download the FILES necessary for downgrading
3) Reboot the phone in bootloader and connect to the pc
4) Opend the terminal and write "fastboot" or "mfastboot" depends by your instaled fastboot
5) Copy/Paste in terminal the lines writed in "fastboot-mfastboot.txt" atached to files
or write them one by one and press ENTER
WAIT 'till it finish
6) In bootloader screen, from buttons vol-up & vol-down navigate and set to "reboot recovery" and press Power
Phone should boot in TWRP-recovery!
Now you have to install a custom-rom or a stok-rom TWRP flashable with Install option
""for this use the instruction to install posted by the developer of each rom""
Also you can RESTORE an older 7.1.1 backup made before update to OREO
Reboot and enjoy by nougat-7.1.1 rom on oreo-8.1.0 bootloader
Downgrading with TWRP
Files to be flashed with TWRP for the users wich have olready the TWRP-recovery instaled!
1) Download the files
2) Copy the zip archive on the sdcard
3) Reboot the phone in TWRP-recovery
4) Search and install the zip
5) Install nougat 7.1.1 rom or restore an older backup made before update to OREO
Enjoy!
reserved
Thank You very much
---------- Post added at 06:02 PM ---------- Previous post was at 05:38 PM ----------
vaserbanix said:
This tutorial is for the users wich are not satisfied by Oreo 8.1.1 rom
Also can be used by users wich changed the touchscreen from some reazons
and on Oreo 8.1.1 this new touchscreen not work
First got to Settings/System/Developer option and chec OEM-unlockin to be ENABLED!
for flashing twrp-recovery may be need to unlock the bootloader by code but it should work only with OEM-unlocking enabled
Downgrading with FASTBOOT!
1) Charge youre phone to at least 50-70%, better is 100%
2) Download the FILES necessary for downgrading
3) Reboot the phone in bootloader and connect to the pc
4) Opend the terminal and write "fastboot" or "mfastboot" depends by your instaled fastboot
5) Copy/Paste in terminal the lines writed in "fastboot-mfastboot.txt" atached to files
or write them one by one and press ENTER
WAIT 'till it finish
6) In bootloader screen, from buttons vol-up & vol-down navigate and set to "reboot recovery" and press Power
Phone should boot in TWRP-recovery!
Now you have to install a custom-rom or a stok-rom TWRP flashable with Install option
""for this use the instruction to install posted by the developer of each rom""
Also you can RESTORE an older 7.1.1 backup made before update to OREO
Reboot and enjoy by nougat-7.1.1 rom on oreo-8.1.0 bootloader
Downgrading with TWRP
Files to be flashed with TWRP for the users wich have olready the TWRP-recovery instaled!
1) Download the files
2) Copy the zip archive on the sdcard
3) Reboot the phone in TWRP-recovery
4) Search and install the zip
5) Install nougat 7.1.1 rom or restore an older backup made before update to OREO
Enjoy!
Click to expand...
Click to collapse
Also, can I flash Stock Nougat (using fastboot) after this? And is there any chance of my device being hardbricked?
ShattrdChain said:
Thank You very much
---------- Post added at 06:02 PM ---------- Previous post was at 05:38 PM ----------
Also, can I flash Stock Nougat (using fastboot) after this? And is there any chance of my device being hardbricked?
Click to expand...
Click to collapse
No! you cant flash a full nougat rom with fastboot.
Bootloader cant be downgraded!
for hardbricked phones you have first to boot it using the sdcard img.
then when you get bootloader working without sdcard, can use this tutorial
Sent from my Moto G (5S) using Tapatalk
vaserbanix said:
No! you cant flash a full nougat rom with fastboot.
Bootloader cant be downgraded!
for hardbricked phones you have first to boot it using the sdcard img.
then when you get bootloader working without sdcard, can use this tutorial
Sent from my Moto G (5S) using Tapatalk
Click to expand...
Click to collapse
Oh ok. Thank You very much
I successfully rolled back to 7.1 using this method. No errors or issues. Everything worked flawlessly. A big thank you @vaserbanix
What are the problems with 8.1? I'm still on Android 7 (RETEU)
Argon007 said:
What are the problems with 8.1? I'm still on Android 7 (RETEU)
Click to expand...
Click to collapse
1. Oreo Battery drains considerably faster than 7.1. (But charges faster too)
2. Fingerprint unlocks slower than 7.1
3. Lags slightly when doing intensive tasks.
Now we need a maintainer for (a) Nougat rom(s)..
Ænimal said:
Now we need a maintainer for (a) Nougat rom(s)..
Click to expand...
Click to collapse
YES indeed!
Im in 8.1.1 stock rom. Can i install a custom 7.1.2 (ViperOS) with this method? Tks.
mysticauls said:
Im in 8.1.1 stock rom. Can i install a custom 7.1.2 (ViperOS) with this method? Tks.
Click to expand...
Click to collapse
lineage 14.1 work so it should work ViperOS too!
to be sure ask in ViperOS thread.
Thankyou!
Hello!
Do you lose biometrics by installing twrp?
vaserbanix said:
YES indeed!
Click to expand...
Click to collapse
LOS14.1 has been updated:
NEW BUILD: https://www.androidfilehost.com/?fid...63190603848665
Change log: November 18 Security Update
NOTE: Like so many other users, I too updated my device with OREO and stuck with that. I haven't tried downgrading it because I don't want to end up with a hard-bricked device once again. Point here is the new build is not tested. So please take a TWRP backup before using this build. Don't forget to post me even if works fine.
Thanks,
KS
Click to expand...
Click to collapse
EDIT: When I try to quote properly I get logged out for some reason, so see this thread obviously (and don't forget to thank @kalyansundhar ):
https://forum.xda-developers.com/moto-g5s/development/rom-lineageos-14-1-t3727918
Fantastic tutorial, vaserbanix. Thank you!
Does anybody know where can I get a nougat stock rom TWRP flashable? There is a thread with stock roms but all of them are only flashable via Fastboot...
I would like to get this in particular: [MONTANA_NPP26.102-49-14]
---------- Post added at 08:38 PM ---------- Previous post was at 08:13 PM ----------
ShattrdChain said:
I successfully rolled back to 7.1 using this method. No errors or issues. Everything worked flawlessly. A big thank you @vaserbanix
Click to expand...
Click to collapse
Thank you so much for your feedback, ShattrdChain! :good:
May I know what rom did you use for flashing with this method?
And do you know if bootloader needs to be unlocked in order to downgrade with this guide?
TWRP method doesn't work (bootloop), pls fix or delete.
FanderWasTaken said:
TWRP method doesn't work (bootloop), pls fix or delete.
Click to expand...
Click to collapse
i understand it work!
just chek the twrp version!
is posible the twrp to dont read some partitons.
this can make the differences betwen work or not
ask eric rutgers ( @GoldeneyeS2), he instaled sucesful that downgrade.zip
Thankyou!
vaserbanix said:
i understand it work!
just chek the twrp version!
is posible the twrp to dont read some partitons.
this can make the differences betwen work or not
ask eric rutgers ( @GoldeneyeS2), he instaled sucesful that downgrade.zip
Thankyou!
Click to expand...
Click to collapse
Its works great.
You can also use fastboot to downgrade!
can the downgrade be done without the bootloader unlocked?
the methods don't work for xt1799-2!
Follow these easy steps
Makes sure you have the GSI image on your sdcard before starting this.
1.Unlock Bootloader
2. Boot into bootloader, check your slot if on B switch to A and vice versa.(fastboot set_active a/b)
3.Download twrp and flash it (fastboot flash boot boot.img)
4.Boot into twrp,Format data or in bootloader run this command "fastboot format userdata" to get rid if encryption else gsi wont boot then go to reboot switch slots to your opposite one, go to "install" navigate to your sdcard where you place the gsi , look for 'select image" then flash your gsi.
5.To flash gapps if your using a aosp gsi go to twrp then go into /wipe/advanced wipe/ select system on the options then "repair or change file system" then press on "resize file system" this will resize your system partiton back to 2.7gigs and allow you to flash gapps.
6.Go back to "reboot" and select the opposite slot that you selected on step 4, then reboot to system ignore the "no system image detected" message
7.Boot back into boot loader and run "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" updated link with .45 update vbeta.img https://www.mediafire.com/file/by0s4xv6op9so0d/vbmeta.img/file
8. Your gsi "should" boot
Group support Zenfone5z GSI:
https://t.me/Zenfone5zGSI
Downloads:
https://forum.xda-developers.com/pr...vice-development/pie-erfan-gsi-ports-t3906486
https://forum.xda-developers.com/project-treble/trebleenabled-device-development AOSP based GSI's
Fixes and WorkArounds
Bluetooth incall audio fix, go to /vendor/etc and delete, a2dp_audio_policy_configuration.xml. and reboot
Volte Fix for GSi credits to rohan and kalish on telegram group
Install the ims.apk(adb push it to /system/app) attached and add this lines to /system/build.prop and reboot
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
For root( magisk) on stock latest .45 pie update and on gsi's flash this patched boot.
https://www.mediafire.com/file/5v40eov7vp320k7/.45patched_boot.img/file
How is this different from other GSI's?
Does anyone of the GSI has VoLTE working.,?
mmahith18 said:
How is this different from other GSI's?
Click to expand...
Click to collapse
These are the ported DSI from various OEMs, for eg. Oxygen OS, H2OS, MIUI, etc.
---------- Post added at 03:07 PM ---------- Previous post was at 03:05 PM ----------
@rafyvitto
Thanks a lot for sharing this XDA thread, can you also mention which GSIs are currently at least booting on Zenfone 5Z? Would really appreciate that.
Thanks though.
hamzain said:
These are the ported DSI from various OEMs, for eg. Oxygen OS, H2OS, MIUI, etc.
---------- Post added at 03:07 PM ---------- Previous post was at 03:05 PM ----------
@rafyvitto
Thanks a lot for sharing this XDA thread, can you also mention which GSIs are currently at least booting on Zenfone 5Z? Would really appreciate that.
Thanks though.
Click to expand...
Click to collapse
To my knowledge and by the guys on the telegram group, oxygen os boots and has some bluetooth issues same with hydrogenOS fyi its one the most stable gsi's from erfan, Pixel beta Q also works but has quite a lot of issues, i havent tested sony/miui or any of the other gsi's sorry.
rafyvitto said:
To my knowledge and by the guys on the telegram group, oxygen os boots and has some bluetooth issues same with hydrogenOS fyi its one the most stable gsi's from erfan, Pixel beta Q also works but has quite a lot of issues, i havent tested sony/miui or any of the other gsi's sorry.
Click to expand...
Click to collapse
Thanks.
I'm sorry, I'm asking too much, is VoLTE working.?
hamzain said:
Thanks.
I'm sorry, I'm asking too much, is VoLTE working.?
Click to expand...
Click to collapse
Yes you need to install the apk and add the build.prop lines in first post.
rafyvitto said:
Yes you need to install the apk and add the build.prop lines in first post.
Click to expand...
Click to collapse
Thanks.
---------- Post added at 07:29 PM ---------- Previous post was at 07:02 PM ----------
rafyvitto said:
Yes you need to install the apk and add the build.prop lines in first post.
Click to expand...
Click to collapse
One more question, Hdrfix.zip has to be flashed only for OOS or for any GSI?
hamzain said:
Thanks.
---------- Post added at 07:29 PM ---------- Previous post was at 07:02 PM ----------
One more question, Hdrfix.zip has to be flashed only for OOS or for any GSI?
Click to expand...
Click to collapse
Only for hydrogen/OSS as i stated in first post correct.
Here you can find the latest updates on efrans gsi's https://build.lolinet.com/file/GSI/ , the post he made on treble forum dosnt have the latest gsi's.
rafyvitto said:
Only for hydrogen/OSS as i stated in first post correct.
Click to expand...
Click to collapse
Thanks, I will get back with the reviews.
Ok.
So today being a holiday, gave hefty 10 hours to try every single GSI mentioned in this thread. And here are my findings:
1. MIUI port - Boots, buttery smooth, no mobile data or VoLTE, as mentioned in the OP, ims.apk doesn't get installed, hence unusable.
2. OOS port - Bootloops, tried multiple times, no success.
3. One UI - Unable to flash the image, says unable to write in the system partition.
4. Xperia Port - Again, boot loop.
5. HOS - Unable to boot.
Did not try Android Q.
One more thing, as per the instruction, when I try to 'Format Data' through TWRP, it says unable to erase data, data partition busy.
I followed step by step for all the mentioned ROMs, can someone help me?
Also, ims.apk is uninstallable, tried many times.
hamzain said:
Ok.
So today being a holiday, gave hefty 10 hours to try every single GSI mentioned in this thread. And here are my findings:
1. MIUI port - Boots, buttery smooth, no mobile data or VoLTE, as mentioned in the OP, ims.apk doesn't get installed, hence unusable.
2. OOS port - Bootloops, tried multiple times, no success.
3. One UI - Unable to flash the image, says unable to write in the system partition.
4. Xperia Port - Again, boot loop.
5. HOS - Unable to boot.
Did not try Android Q.
One more thing, as per the instruction, when I try to 'Format Data' through TWRP, it says unable to erase data, data partition busy.
I followed step by step for all the mentioned ROMs, can someone help me?
Also, ims.apk is uninstallable, tried many times.
Click to expand...
Click to collapse
1. The app has to be pushed to /system/app should work that way.
2. You should be able to wipe data if you go to bootloader switch to slot were trwp is not installed then switch back to were it IS installed then boot twrp and wipe data, thats what i do and it works.
3. Try the updated gsi's from the link i posted a few post back.
Also, i added lates .45 vbeta.img and patched boot.img for root on first post, enjoy guys.
rafyvitto said:
Also, i added lates .45 vbeta.img and patched boot.img for root on first post, enjoy guys.
Click to expand...
Click to collapse
I tried so many times, but the results are unchanged, only MIUI boots.
But when I pushed the ims.apk and added the lines to build.prop it got stuck at bootloop.
I tried everything, I just need OOS to boot.
Also, one more thing I noticed is, MIUI boots only when I don't flash permissive2.zip, when I flash this zip even MIUI fails to boot
---------- Post added at 02:01 PM ---------- Previous post was at 02:01 PM ----------
rafyvitto said:
Also, i added lates .45 vbeta.img and patched boot.img for root on first post, enjoy guys.
Click to expand...
Click to collapse
I donwloaded all the newest GSIs and followed the instructions properly.
---------- Post added at 02:02 PM ---------- Previous post was at 02:01 PM ----------
rafyvitto said:
1. The app has to be pushed to /system/app should work that way.
2. You should be able to wipe data if you go to bootloader switch to slot were trwp is not installed then switch back to were it IS installed then boot twrp and wipe data, thats what i do and it works.
3. Try the updated gsi's from the link i posted a few post back.
Click to expand...
Click to collapse
And I also did the slot switching, but 'Format Data' still says 'Failed to mount /data, partition busy'
https://sourceforge.net/projects/mactavishao-builds/ found more oem framework gsi's havent had time to flash any yet.
rafyvitto said:
https://sourceforge.net/projects/mactavishao-builds/ found more oem framework gsi's havent had time to flash any yet.
Click to expand...
Click to collapse
Excellent keep up the good work
Added, use "fastboot format userdata" in bootloader, to the steps in case formatting data does not work in twrp.
rafyvitto said:
Added, use "fastboot format userdata" in bootloader, to the steps in case formatting data does not work in twrp.
Click to expand...
Click to collapse
Which is the most stable as of now?... Can't be stable as stuck but best to it
rafyvitto said:
Added, use "fastboot format userdata" in bootloader, to the steps in case formatting data does not work in twrp.
Click to expand...
Click to collapse
Thanks.
So as I go over the custom roms available in the development section I cannot help but notice how many users state that the rom is causing random reboots. It is usually due to said user flashing the custom rom over a beta OOS version instead of the latest stable build as the OP instructions usually indicate. The reboots are hardly caused by the rom itself. I am putting together this guide to help users go from beta back to stable. This will allow a clean install of the custom rom and usability as it is intended.
This can also be used to just go back to stable from beta if you want to run the stable OOS.
There are 2 ways to do this. One is via TWRP if that is what you prefer or you can also use the MSM tool to flash back to the latest stable. Both ways will wipe and format your internal data. This is due to the mismatch in security patches between beta and stable. So be sure to make a backup of your internal storage if there is stuff there that you need. You have been warned.
NOTE: Highly recommended to use a computer to make things easier. If you do not have a computer available, use the TWRP method listed below to get back to stable OOS. Once OOS boots, you can download your custom rom of choice using your phone and install it.
Here are the links for the latest MSM tool and latest stable zip if you want to use the TWRP method:
Latest MSM Tool
Latest stable OOS to flash in TWRP
TWRP Steps:
Download latest OOS stable from link above
Flash OOS stable build
Flash TWRP installer
Reboot to TWRP
Factory Reset
Format Data type 'yes' when prompted
Reboot to System
Your phone will reboot to OOS. If you want to run OOS stable you are done. Just set up your phone as normal from here.
If you want to run a custom rom, reboot to TWRP, you can transfer your custom rom, gapps, magisk, kernel and twrp installer using a PC. If no PC is available, download your rom and needed files like twrp, magisk etc. using OOS stable first. Then you can reboot to recovery and follow the installation steps provided by your rom developer on their page.
Steps for MSM:
Download the latest MSM tool with link from above. Boot phone to EDL either by powering off the phone then holding Vol + and - with Power or my preferred way via adb by typing adb reboot edl. Plug in phone once in EDL and let MSM do its thing. If you are not sure how to use MSM, the link for the MSM tool outlines the steps. Your phone will reboot to OOS. If you want to run OOS stable you are done. Just set up your phone as normal from here. Note, your bootloader is locked. You will need to do an oem unlock to install twrp and magisk if you want root or to install a custom kernel.
If you want to run a custom rom or root your phone, get to the settings screen.. you can skip setting up your phone so just hit skip on all the prompts for set up. Go to settings, enable developer options. Make sure OEM unlock is selected and USB debugging is selected. Once you do that, do adb reboot bootloader. Then do the following:
fastboot oem unlock
It will reboot the phone. Skip through the set up again and go back to settings. Enable developer options and enabled USB debugging. Then run adb reboot bootloader. In the bootloader, do the following:
fastboot boot <twrp.img> (replace this with the actual file name)
From there, you can transfer your custom rom, gapps, magisk, kernel and twrp installer using a PC. Follow the installation steps provided by your rom developer on their page.
i am on OpenBeta9,can i use the Twrp Method for a downgrade to the Stable 9.0.13?
Gesendet von meinem xXx_NoLimits_6.0 on ONEPLUS 6T mit Tapatalk
MarcoG: said:
i am on OpenBeta9,can i use the Twrp Method for a downgrade to the Stable 9.0.13?
Click to expand...
Click to collapse
Given the problems with rolling back security patches I wondered the same thing. However, assuming we wiped everything including system it should work. Having said that, when I previously tried rolling back to the latest stable from beta, when I fastboot flashed everything to both slots, I could never get it to boot and was able to flash beta and get it running again.
ultyrunner said:
Given the problems with rolling back security patches I wondered the same thing. However, assuming we wiped everything including system it should work. Having said that, when I previously tried rolling back to the latest stable from beta, when I fastboot flashed everything to both slots, I could never get it to boot and was able to flash beta and get it running again.
Click to expand...
Click to collapse
I'd like to see a resolution to this ^
This should not be this complicated any time I my base whether it beta or stable I never met to do all of this...
It's super simple to go back to whatever oos version you want without the need of msm tool and all this extra stuff.... I've went from beta to stable and back to beta several times no issues... And you are going to have to format data no matter what if you are changing oos versions and don't want to run into an encryption problem.
You can just back everything up
Boot to fastboot
Fastboot format userdata
Fastboot boot twrp. img
Transfer needed files. (oos, twrp)
Flash oos + twrp
Reboot recovery (make sure the slot changed)
Flash oos + twrp
Reboot system make sure it boots up right
Now you can go flash the rom you want
Causical said:
I'd like to see a resolution to this ^
Click to expand...
Click to collapse
I can verify the TWRP steps outlined above (in the OP, not the comment with Fastboot) worked perfectly for me. Did everything in exactly the same order. Was on beta 8 and went to 9.0.13 without a hitch.
se7ensde said:
This should not be this complicated any time I my base whether it beta or stable I never met to do all of this...
It's super simple to go back to whatever oos version you want without the need of msm tool and all this extra stuff.... I've went from beta to stable and back to beta several times no issues... And you are going to have to format data no matter what if you are changing oos versions and don't want to run into an encryption problem.
You can just back everything up
Boot to fastboot
Fastboot format userdata
Fastboot boot twrp. img
Transfer needed files. (oos, twrp)
Flash oos + twrp
Reboot recovery (make sure the slot changed)
Flash oos + twrp
Reboot system make sure it boots up right
Now you can go flash the rom you want
Click to expand...
Click to collapse
what about directy through TWRP? can I just replace fastboot with TWRP in your instructions or does Formatting userdata erase internal files (ie: TWRP, Magisk, etc... I'm only asking because I've only ever updated to the latest OOS and I'm just curious for future possible future tinkering)
---------- Post added at 12:38 AM ---------- Previous post was at 12:34 AM ----------
ultyrunner said:
I can verify the TWRP steps outlined above (in the OP, not the comment with Fastboot) worked perfectly for me. Did everything in exactly the same order. Was on beta 8 and went to 9.0.13 without a hitch.
Click to expand...
Click to collapse
Awesome, you sir are THEE man. Please get a job with XDA or something
Causical said:
Awesome, you sir are THEE man. Please get a job with XDA or something
Click to expand...
Click to collapse
Um ... OK ... ?
Causical said:
what about directy through TWRP? can I just replace fastboot with TWRP in your instructions or does Formatting userdata erase internal files (ie: TWRP, Magisk, etc... I'm only asking because I've only ever updated to the latest OOS and I'm just curious for future possible future tinkering)
---------- Post added at 12:38 AM ---------- Previous post was at 12:34 AM ----------
Awesome, you sir are THEE man. Please get a job with XDA or something
Click to expand...
Click to collapse
Yeah sure you can mix up the steps or skip whatever you want..
se7ensde said:
Yeah sure you can mix up the steps or skip whatever you want..
Click to expand...
Click to collapse
LOL, yeah. I was kind of surprised with the smart-ass comment, but then again lots of people on here don't follow instructions, do things out of order and then wonder what went wrong or why they suddenly have a $700 paper weight. Given how much chatter there's been about the MSM tool (not an option on Mac) or needing to fastboot flash individual images (which didn't work for me), I was surprised how easy moving back to stable completely via TWRP is. I'm used flashing Nexus and older Samsung devices, which used to be dead-simple.
ultyrunner said:
LOL, yeah. I was kind of surprised with the smart-ass comment, but then again lots of people on here don't follow instructions, do things out of order and then wonder what went wrong or why they suddenly have a $700 paper weight. Given how much chatter there's been about the MSM tool (not an option on Mac) or needing to fastboot flash individual images (which didn't work for me), I was surprised how easy moving back to stable completely via TWRP is. I'm used flashing Nexus and older Samsung devices, which used to be dead-simple.
Click to expand...
Click to collapse
You were probably surprised with the smart ass comment because it wasn't a smart ass comment Sgt. Dillweed (that was a little smart ass)...I don't generally give a thanks to someone to be a smart ass, but nice to know where your head's at.
Causical said:
You were probably surprised with the smart ass comment because it wasn't a smart ass comment Sgt. Dillweed (that was a little smart ass)...I don't generally give a thanks to someone to be a smart ass, but nice to know where your head's at.
Click to expand...
Click to collapse
Nope. I was surprised because ...
Awesome, you sir are THEE man. Please get a job with XDA or something
Click to expand...
Click to collapse
... is definitely smart-ass, and seems odd after receiving a like. If you don't see that in the tone, I'm afraid I can't help you.
I think THAT may be more indicative of where your head's at. But ... carry on and you keep on doing you, bud.
ultyrunner said:
Nope. I was surprised because ...
... is definitely smart-ass, and seems odd after receiving a like. If you don't see that in the tone, I'm afraid I can't help you.
I think THAT may be more indicative of where your head's at. But ... carry on and you keep on doing you, bud.
Click to expand...
Click to collapse
Cool I'm glad you can explain the "tone" and characteristics of my own words to me. I'll remember to try and not be so nice towards you next time, at least if I really be a **** it won't be mistaken.
I WAS originally thrilled by your simple and to the point response, but since you decided to twist my words and make yourself look like a jack ass... well nicely done, is all I have to say ?
Words of a Wise Guy: "hmmm seems odd after receiving a like..."
Huh, just think about that one for a second.
Causical said:
Cool I'm glad you can explain the "tone" and characteristics of my own words to me.
Click to expand...
Click to collapse
Clearly someone has to, because you can't understand that everyone isn't inside your head to hear the little voices that define 'polite' for you. Anyway, you're on the ignore list now.
ultyrunner said:
Clearly someone has to, because you can't understand that everyone isn't inside your head to hear the little voices that define 'polite' for you. Anyway, you're on the ignore list now.
Click to expand...
Click to collapse
Oooo scary...I guess I'll take my "like" or thanks back whatever you call it.
the.emilio said:
So as I go over the custom roms available in the development section I cannot help but notice how many users state that the rom is causing random reboots. It is usually due to said user flashing the custom rom over a beta OOS version instead of the latest stable build as the OP instructions usually indicate. The reboots are hardly caused by the rom itself. I am putting together this guide to help users go from beta back to stable. This will allow a clean install of the custom rom and usability as it is intended.
This can also be used to just go back to stable from beta if you want to run the stable OOS.
There are 2 ways to do this. One is via TWRP if that is what you prefer or you can also use the MSM tool to flash back to the latest stable. Both ways will wipe and format your internal data. This is due to the mismatch in security patches between beta and stable. So be sure to make a backup of your internal storage if there is stuff there that you need. You have been warned.
NOTE: Highly recommended to use a computer to make things easier. If you do not have a computer available, use the TWRP method listed below to get back to stable OOS. Once OOS boots, you can download your custom rom of choice using your phone and install it.
Here are the links for the latest MSM tool and latest stable zip if you want to use the TWRP method:
Latest MSM Tool
Latest stable OOS to flash in TWRP
TWRP Steps:
Download latest OOS stable from link above
Flash OOS stable build
Flash TWRP installer
Reboot to TWRP
Factory Reset
Format Data type 'yes' when prompted
Reboot to System
Your phone will reboot to OOS. If you want to run OOS stable you are done. Just set up your phone as normal from here.
If you want to run a custom rom, reboot to TWRP, you can transfer your custom rom, gapps, magisk, kernel and twrp installer using a PC. If no PC is available, download your rom and needed files like twrp, magisk etc. using OOS stable first. Then you can reboot to recovery and follow the installation steps provided by your rom developer on their page.
Steps for MSM:
Download the latest MSM tool with link from above. Boot phone to EDL either by powering off the phone then holding Vol + and - with Power or my preferred way via adb by typing adb reboot edl. Plug in phone once in EDL and let MSM do its thing. If you are not sure how to use MSM, the link for the MSM tool outlines the steps. Your phone will reboot to OOS. If you want to run OOS stable you are done. Just set up your phone as normal from here. Note, your bootloader is locked. You will need to do an oem unlock to install twrp and magisk if you want root or to install a custom kernel.
If you want to run a custom rom or root your phone, get to the settings screen.. you can skip setting up your phone so just hit skip on all the prompts for set up. Go to settings, enable developer options. Make sure OEM unlock is selected and USB debugging is selected. Once you do that, do adb reboot bootloader. Then do the following:
fastboot oem unlock
It will reboot the phone. Skip through the set up again and go back to settings. Enable developer options and enabled USB debugging. Then run adb reboot bootloader. In the bootloader, do the following:
fastboot boot <twrp.img> (replace this with the actual file name)
From there, you can transfer your custom rom, gapps, magisk, kernel and twrp installer using a PC. Follow the installation steps provided by your rom developer on their page.
Click to expand...
Click to collapse
Thank you it works[emoji16]
Gesendet von meinem ONEPLUS A6013 mit Tapatalk
se7ensde said:
Fastboot format userdata
Click to expand...
Click to collapse
What is formatted? The complete internal sdcard?
TWRP Steps:
Download latest OOS stable from link above
Flash OOS stable build
Flash TWRP installer
Reboot to TWRP
Factory Reset
Format Data type 'yes' when prompted
Reboot to System
Will this work if I'm on beta14 with July security patch, and I want to flash back to stable . 15 with June security patch? I'm using TWRP 3.3.1-6. I ask because I would like to flash back to stable but will not have access to my laptop for a week or two, so I'd like to do it right through twrp if at all possible
Ryano89 said:
TWRP Steps:
Download latest OOS stable from link above
Flash OOS stable build
Flash TWRP installer
Reboot to TWRP
Factory Reset
Format Data type 'yes' when prompted
Reboot to System
Will this work if I'm on beta14 with July security patch, and I want to flash back to stable . 15 with June security patch? I'm using TWRP 3.3.1-6. I ask because I would like to flash back to stable but will not have access to my laptop for a week or two, so I'd like to do it right through twrp if at all possible
Click to expand...
Click to collapse
Yes.
Mannan Qamar said:
Yes.
Click to expand...
Click to collapse
Thanks, I only ask because I see a lot of disagreement about it on different threads. Some say you can do it, other's say you can't do it if you are flashing back to an older security patch. It's not urgent for me so I might just wait until I have access to my laptop again, but I was hoping to do it now. Won't format completely erase the device?
TWRP for EMUI 9.1
THIS TWRP IS FOR DEVICES WITH KIRIN 65x SOC (HI6250) RUNNING EMUI 9.1 AND NOT EMUI 8
What's different from TWRP for Android 8?
erecovery_ramdisk option to flash .img
system_root partition for 9.1
What works now?
You can now flash .zip like Gapps and they'll work (before it gave error 64)
What doesn't work?
At the moment, I don't know if ADB sideload works.
Otherwise, everything seems to be working.
How to flash this TWRP
To recovery_ramdisk
Code:
fastboot flash recovery_ramdisk [TWRP].img
I DIDN'T BUILD ANY OF THIS
I only modified a TWRP (which I don't know the author, sorry) to make it work good on hi6250 EMUI 9.1 devices.
I would like to have the hardware and knowledge to build and develop new stuff but at the moment I can't.
Download - https://drive.google.com/open?id=10VONtu_Bf6grW60N7K8gMrzQSG-rswni
Feel free to contact me on Telegram
https://t.me/GelberVogel (PM) - temporary
screenshots
This guy's doing gods work, saved me from throwing a perfectly good device into the trash. Working perfectly, tested on an ANE-LX1!
Anyone know ROMs that will work with emui 9?
I Know openkirin a long time but the Bluetooth is restarting in the emui 9 based builds.
with this recovery boot the gsi roms? currently only the openkirin gsi boot, but using adb... All the gsi I've flashed by adb or the previous recovery give bootlop
joaomoreira1001 said:
Anyone know ROMs that will work with emui 9?
I Know openkirin a long time but the Bluetooth is restarting in the emui 9 based builds.
Click to expand...
Click to collapse
Probably phh treble
Linux Lounge said:
Probably phh treble
Click to expand...
Click to collapse
i will try it thanks
---------- Post added at 09:09 PM ---------- Previous post was at 08:48 PM ----------
Linux Lounge said:
Probably phh treble
Click to expand...
Click to collapse
nope that does not boot
Yellow_B_ird said:
TWRP for EMUI 9.1
What's different from TWRP for Android 8?
erecovery_ramdisk option to flash .img
system_root partition for 9.1
Click to expand...
Click to collapse
Hello, please can someone tell me how to flash it in erecovery_ramdisk partition?
I have recovery brick and i can't flash it in recovery_ramdisk...
This is my last hope!
Mustaine635 said:
Hello, please can someone tell me how to flash it in erecovery_ramdisk partition?
I have recovery brick and i can't flash it in recovery_ramdisk...
This is my last hope!
Click to expand...
Click to collapse
Tell me what device do you have (luckily I came back to XDA early enough, I hope)
Also, try flashing stock kernel (I can send mine for HUAWEI P Smart 2018 FIG-LX1C432 EMUI 9.1 B120)
Yellow_B_ird said:
Tell me what device do you have (luckily I came back to XDA early enough, I hope)
Also, try flashing stock kernel (I can send mine for HUAWEI P Smart 2018 FIG-LX1C432 EMUI 9.1 B120)
Click to expand...
Click to collapse
I have p smart fig-lx1.
I tried to flash it using fastboot flash erecevery_ramdisk [file].img but it says failed...
The standard recovery was bricked because i used hurupdater to update to emui 9.1... The phone works but i have no recovery so i can't do anything...
Yellow_B_ird said:
Tell me what device do you have (luckily I came back to XDA early enough, I hope)
Also, try flashing stock kernel (I can send mine for HUAWEI P Smart 2018 FIG-LX1C432 EMUI 9.1 B120)
Click to expand...
Click to collapse
It works! I had to flash 3 files for the stock recovery (recovery_ramdisk, _vbmeta and _vendor). Then i flash the twrp recovery and it works. The only problem is that when i browse internal storage, the folders name are all random characters... Why that?
Another question is, how can i root my device now?
Mustaine635 said:
It works! I had to flash 3 files for the stock recovery (recovery_ramdisk, _vbmeta and _vendor). Then i flash the twrp recovery and it works. The only problem is that when i browse internal storage, the folders name are all random characters... Why that?
Another question is, how can i root my device now?
Click to expand...
Click to collapse
Glad it worked!
Just flash Magisk like you would with any TWRP assuming it works. If you want recovery and root in a stupid way.. just flash my TWRP to recovery and in recovery, flash my or any other TWRP/recovery to e-recovery and after that, flash Magisk like usual.
Thank you for the build. Any chance of flashing this on a device with locked bootloader, like using an official flash tool to flash a signed recovery or using e-recovery (I have experience with bootloader and flashing but not with Huawei/Kyrin)?
I keep getting a (remote: partition length get error) error ... Any help ?
Thanks a lot!! :good:
The Google Drive Link doesn't work!
I am trying to root my Huawei P Smart but the Google Drive Link for TWRP doesn't work https://forum.xda-developers.com/huawei-p-smart/development/recovery-twrp-3-2-1-0-t3953343
Was your Google account terminated. If you are able to can you send me the TWRP Image or if your Google account works can you upload the TWRP image to Google Drive?
Love from Greece![/QUOTE]
Hi, gelber here.
I'm sorry for the confusion, but I really barely touch XDA and as I deleted my old Google account, I lost access to this XDA account (I_am_gelber) and to that gdrive link. However, I can defo give the file back in a bit but I'm surely gonna forget. If you really want the file, please pm me at t.me/ActuallyNotGelb since I still need to give it a quick find.
Thanks!
ActuallyNotGelb said:
Hi, gelber here.
I'm sorry for the confusion, but I really barely touch XDA and as I deleted my old Google account, I lost access to this XDA account (I_am_gelber) and to that gdrive link. However, I can defo give the file back in a bit but I'm surely gonna forget. If you really want the file, please pm me at t.me/ActuallyNotGelb since I still need to give it a quick find.
Thanks!
Click to expand...
Click to collapse
Can you please upload the file to some website. I'm unable to create a Telegram account right now so can you please upload the image to any website? It would mean a lot for me for you to do that!
GreekProgrammer said:
Can you please upload the file to some website. I'm unable to create a Telegram account right now so can you please upload the image to any website? It would mean a lot for me for you to do that!
Click to expand...
Click to collapse
Any luck?
BlissRoms
BlissRoms based on Android 11
Bliss ROMs comes with a wide selection of customization options from around the Android community as well as unique options developed by our team. With so many options available, you’ll find it hard not to enjoy the Blissful experience.Special Thanks to : @FullOfHell @xstefen @OmkarTheAndroid @apophis9283 @Constrabus for their knowledge and help. @dpryor88 for testing the rom at any hour of the day. Got his stamp of approval.
@LuK1337 for his LOS device trees
And everybody in Kangarooster Meadows Testing Field Of Dreams TG group
BlissROM Download
DO NOT FLASH GAPPS
Installing from Android 11 Rom's.
Install latest OOS Full OTA Both Slots
MAKE SURE UR ON SLOT A TO FLASH
fastboot reboot fastboot
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash system_ext system_ext.img
fastboot reboot bootloader
reboot to recovery and format everything in recovery
BUGS
Permissive
You Tell Me
Sources
BlissRoms Github
BlissRoms Gerrit
Device Sources
Kernel Source
Mine!!
Another one just in case
Thankyou for this rom. I would definitely try it out. Waiting for the TWRP release for backup solutions before flashing
Kudos +1
For the KB2005/US version?
ins5736 said:
For the KB2005/US version?
Click to expand...
Click to collapse
Yes all models im using it on my tmo version
I didn't found kebab in the "BlissRom Download" which link to "https://sourceforge.net/projects/blissroms/files/Q/enchilada/".
Does magisk works, pass basic and safety net? Tnx for the rom
manhong2112 said:
I didn't found kebab in the "BlissRom Download" which link to "https://sourceforge.net/projects/blissroms/files/Q/enchilada/".
Click to expand...
Click to collapse
Yes. @omariscal1019 Wrong download link, mate.
Link fixed sorry guys
theincognito said:
Yes. @omariscal1019 Wrong download link, mate.
Click to expand...
Click to collapse
Link fixed
Just waiting for TWRP to get started with. Wondering why it's getting delayed for oneplus 8t. It's always been easy and quick with development and TWRP for oneplus devices. Fingers crossed.
deleted
ehy dev the file img system-ext its too large to install, i try it three times but dont work, i used lastest platform tools, and not work
just for feedback "too large to install..."
thanks
iaio72 said:
ehy dev the file img system-ext its too large to install, i try it three times but dont work, i used lastest platform tools, and not work
just for feedback "too large to install..."
thanks
Click to expand...
Click to collapse
Did u read the instructions. Did u make sure u were in slot a ... Did u flash full update to both slots? I hav never had that problem nor my tester
omariscal1019 said:
Did u read the instructions. Did u make sure u were in slot a ... Did u flash full update to both slots? I hav never had that problem nor my tester
Click to expand...
Click to collapse
How does one flash OOS to slot_b? I know I have OOS in slot a but how do I know and how do I install it on slot_b? Thanks for the help
Jed!Master said:
How does one flash OOS to slot_b? I know I have OOS in slot a but how do I know and how do I install it on slot_b? Thanks for the help
Click to expand...
Click to collapse
when flash full ota zip from oneplus thru local upgrade twice
omariscal1019 said:
Did u read the instructions. Did u make sure u were in slot a ... Did u flash full update to both slots? I hav never had that problem nor my tester
Click to expand...
Click to collapse
I know very well the instructions thanks, and I find to install to both slot, but remain the problem to system-ext it's too large ....
iaio72 said:
I know very well the instructions thanks, and I find to install to both slot, but remain the problem to system-ext it's too large ....
Click to expand...
Click to collapse
weird i dont have that problem. nor my testers. tell u the truth i dont know why only u have that problem
So guys I been holding back since this got released. How has the time been for everyone? Any issues? How's battery life?