I just find out that this rom https://forum.xda-developers.com/p8...m-lineageos-17-1-huawei-p8-lite-2017-t4064121 could be installed on our device wtih minor changes.After installing all things you will need to install stock recovery and wipe cache and try to do factory reset(i tried to but i got error massage) then you will successfully boot into rom
Contributors
@DarkJoker360
I can confirm that this works like a charm, here I posted the instructions for those who want to install it!
Hi when I try to wipe data and cache... I have an error because the data is not mounted, I've trying to change the system file to ext2 and ext4 but nothing change. I also tried to repair system file. What can I do ? My device is already emui 8 and it's an Huawei gr5 2017 bll-l22. Thanks for your help ?
Momo745040 said:
Hi when I try to wipe data and cache... I have an error because the data is not mounted, I've trying to change the system file to ext2 and ext4 but nothing change. I also tried to repair system file. What can I do ? My device is already emui 8 and it's an Huawei gr5 2017 bll-l22. Thanks for your help
Click to expand...
Click to collapse
Try the lastest TWRP in this thread
https://forum.xda-developers.com/p8...wrp-3-3-1-0-huawei-p8-lite-2017-t3953122/amp/
After installing system.img, u need to resize the system partition, until see the used space ~17xxmb and free ~18xx mb,
after that flash gapps
and MUST flash Magisk Phh 19.3
the flash the patch file.
After first boot, you need to, format data in erecovery
Everything works smoothly except......can not make and receive calls, ooopss
update, i try to roll back to emui8, and start the process again. it works now.
recommend to update, lets teach the old dog new trick
A big job ahead ?. I will try and I will tell you if it works thank you for your answer. One last question is there a way to keep a custom recovery because sometimes magisk's module causes a botloop (sorry for my bad English ?)
lucsi said:
Try the lastest TWRP in this thread
https://forum.xda-developers.com/p8...wrp-3-3-1-0-huawei-p8-lite-2017-t3953122/amp/
After installing system.img, u need to resize the system partition, until see the used space ~17xxmb and free ~18xx mb,
after that flash gapps
and MUST flash Magisk Phh 19.3
the flash the patch file.
After first boot, you need to, format data in erecovery
Everything works smoothly except......can not make and receive calls, ooopss
update, i try to roll back to emui8, and start the process again. it works now.
recommend to update, lets teach the old dog new trick
Click to expand...
Click to collapse
So I came back (finally) to emui 8 and I tried to install the recovery custom but I still cannot access the internal storage memory.
I think it comes from my model because I have a Huawei GR5 2017 which is supposed to be a 'copy' of the honor 6x but all the roms which require emui 5.x installed do not work.
In any case thank you very much for your help! [emoji106]
Envoyé de mon BLL-L22 en utilisant Tapatalk
Momo745040 said:
So I came back (finally) to emui 8 and I tried to install the recovery custom but I still cannot access the internal storage memory.
I think it comes from my model because I have a Huawei GR5 2017 which is supposed to be a 'copy' of the honor 6x but all the roms which require emui 5.x installed do not work.
In any case thank you very much for your help! [emoji106]
Envoyé de mon BLL-L22 en utilisant Tapatalk
Click to expand...
Click to collapse
The trick is you need 2 twrp.
https://drive.google.com/file/d/1-iErvJefoFri7HKNEU8uSnYo8kmIyVd9/view?usp=sharing
https://drive.google.com/file/d/1MnFBplsp3nZ3b0BiJ764cV67kHXeRzL4/view?usp=sharing
use twrp-3.3.1emui8v2.img for everything
In the last step after everything flashed, you flash the other twrp huaweitwrp.img
reboot into that twrp
chooose advances; fix encryption
reboot system, then you can access internal memory
the same process with android 10.
mine is also Gr5 2017 and now running 10, no bug
lucsi said:
The trick is you need 2 twrp.
https://drive.google.com/file/d/1-iErvJefoFri7HKNEU8uSnYo8kmIyVd9/view?usp=sharing
https://drive.google.com/file/d/1MnFBplsp3nZ3b0BiJ764cV67kHXeRzL4/view?usp=sharing
use twrp-3.3.1emui8v2.img for everything
In the last step after everything flashed, you flash the other twrp huaweitwrp.img
reboot into that twrp
chooose advances; fix encryption
reboot system, then you can access internal memory
the same process with android 10.
mine is also Gr5 2017 and now running 10, no bug
Click to expand...
Click to collapse
Thanks you very much for your help!
I'll try this weekend (I don't have time in week).
I will come back to say if it worked
Has anyone tried these github projects to unlock the bootloader of his Honor (6X) or Huawei Device?
Maybe it is possible to accelerate these programs by using cuda cores on nvidia graphic card(s).
https://github.com/SkyEmie/huawei-ho...ock-bootloader
https://github.com/Martazza/Huawei-Bootloader-Unlocker
lucsi said:
The trick is you need 2 twrp.
https://drive.google.com/file/d/1-iErvJefoFri7HKNEU8uSnYo8kmIyVd9/view?usp=sharing
https://drive.google.com/file/d/1MnFBplsp3nZ3b0BiJ764cV67kHXeRzL4/view?usp=sharing
use twrp-3.3.1emui8v2.img for everything
In the last step after everything flashed, you flash the other twrp huaweitwrp.img
reboot into that twrp
chooose advances; fix encryption
reboot system, then you can access internal memory
the same process with android 10.
mine is also Gr5 2017 and now running 10, no bug
Click to expand...
Click to collapse
I managed to find a compatible recovery but when I flashed everything and I did a factory reset from the erecovery the phone restarts and it displays the logo lineageOs for 5 seconds then it restarts and the screen remains black then it restarts and displays the logo then it restarts in erecovery telling me that the memory has been seriously damaged.
I think I will give up here([emoji28])but anyway thank you for your help [emoji106].
Envoyé de mon BLL-L22 en utilisant Tapatalk
at first it says encryption unsuccessful then i was told to format the date from twrp, now it stuck on boot animation, i have left it overnight and it reboots to bootloader with code BFM_S_NATIVE_DATA_FAIL 211 NA
reboot_panic_and_wdt_process_func
finally i managed to get it work, so now i'm going to post every single thing i did to make this rom works and i will try to be as noob friendly as possible
first thing first in case you mess everything up, i found out this guide to be some sort of remedy for all problems regarding honor 6x, because from here you will install stock emui 5 which you can use to upgrade to stock emui 8 from this guide
use the guide above if you want to go back to stock rom because every single custom rom will require you to flash from the stock rom
next i follow the guide provided here, after flashing the patch go back to stock oreo recovery which is available on the emui 8 folder you downloaded earlier
do factory reset and wipe cache after that load to bootloader again
finally flash huaweitwrp.img provided by lusci on the post #7
boot to system and enjoy
Raxul said:
at first it says encryption unsuccessful then i was told to format the date from twrp, now it stuck on boot animation, i have left it overnight and it reboots to bootloader with code BFM_S_NATIVE_DATA_FAIL 211 NA
reboot_panic_and_wdt_process_func
Click to expand...
Click to collapse
Have you followed all these instructions?
matyrock said:
How can there be such awesome people? It works in my Honor 6X! And it's fully de-googled man this is just perfect! Thank you very much for this...
These are the steps (thanks @DunoCZ) I followed if an Honor 6X user want to install this ROM:
- *Upgrade to EMUI 8!*
- *Remove the saved fingerprints and Google Accounts just in case*
- Flash the TWRP recovery from @Dil3mm4
- Format cache, dalvik cache, data and system: TWRP -> Wipe -> Advanced Wipe
- Flash the ROM via TWRP (you can try with fastboot but it already works with TWRP): TWRP -> Install -> Install Image
- Resize the system partition: TWRP -> Wipe -> Advanced Wipe -> System -> Resize (DO NOT FORMAT!)
- (Optional) Install GApps, Magisk
- (Required) Install patch
- Reboot and wait
Click to expand...
Click to collapse
D0ping said:
Have you followed all these instructions?
Click to expand...
Click to collapse
i did and the diffferent thing i did is to flash back stock recovery as mentioned by op, wipe the cache and then flash huaweitwrp.im provided by lusci
i edited my post above
Yea, i cant get it to work. No matter what i do after
- flashing system.img
- resizing the system partition
- installing opengapps
- installing magisk
- installing the patch
followed by either:
-straight up booting it.
- doing everything i can in every bootloader.
evenm if i freshly format /data the system get stuck in a boot. Have tried all of the recoveries in this thread. All are basically the same, from what i have observed.
Edit: Figured it out. apparently my gapps was somehow broken. Downloaded a fresh arm64-ogapps and all is working now
Darkitz said:
Yea, i cant get it to work. No matter what i do after
- flashing system.img
- resizing the system partition
- installing opengapps
- installing magisk
- installing the patch
followed by either:
-straight up booting it.
- doing everything i can in every bootloader.
evenm if i freshly format /data the system get stuck in a boot. Have tried all of the recoveries in this thread. All are basically the same, from what i have observed.
Click to expand...
Click to collapse
follow my guide here, this is how i managed to get it work, make sure you flash the rom with your CLEAN STOCK rom
Raxul said:
first thing first in case you mess everything up, i found out this guide to be some sort of remedy for all problems regarding honor 6x, because from here you will install stock emui 5 which you can use to upgrade to stock emui 8 from this guide
use the guide above if you want to go back to stock rom because every single custom rom will require you to flash from the stock rom
next i follow the guide provided here, after flashing the patch go back to stock oreo recovery which is available on the emui 8 folder you downloaded earlier
do factory reset and wipe cache after that load to bootloader again
finally flash huaweitwrp.img provided by lusci on the post #7
boot to system and enjoy
Click to expand...
Click to collapse
Raxul said:
at first it says encryption unsuccessful then i was told to format the date from twrp, now it stuck on boot animation, i have left it overnight and it reboots to bootloader with code BFM_S_NATIVE_DATA_FAIL 211 NA
reboot_panic_and_wdt_process_func
finally i managed to get it work, so now i'm going to post every single thing i did to make this rom works and i will try to be as noob friendly as possible
first thing first in case you mess everything up, i found out this guide to be some sort of remedy for all problems regarding honor 6x, because from here you will install stock emui 5 which you can use to upgrade to stock emui 8 from this guide
use the guide above if you want to go back to stock rom because every single custom rom will require you to flash from the stock rom
next i follow the guide provided here, after flashing the patch go back to stock oreo recovery which is available on the emui 8 folder you downloaded earlier
do factory reset and wipe cache after that load to bootloader again
finally flash huaweitwrp.img provided by lusci on the post #7
boot to system and enjoy
Click to expand...
Click to collapse
Ok let me make it simple for you.
1. Flash stock Oreo Rom (no need to boot it)
2. Flash TWRP by Dilemma in fastboot.
3. Go to recovery and wipe data by typing yes to decrypt data partition (if not already decrypted)
4. Go to fastboot and flash system.img
5. Reboot to recovery and resize system partition
6. Flash GApps
7. Flash los patches zip
8. Flash disable Dm verity patch
9. Flash magisk-phh zip in the end.
10. Reboot and wait.
I used these steps to flash different GSIs/ROMs and it works perfectly.
I managed to flash the rom but without flashing the gapps because I don't know exactly which one to flash should I flash gapps for android 10 arm64 or gapps for android 8.0 ??
try both and it gives me error 20
victorgrey999 said:
I managed to flash the rom but without flashing the gapps because I don't know exactly which one to flash should I flash gapps for android 10 arm64 or gapps for android 8.0 ??
try both and it gives me error 20
Click to expand...
Click to collapse
You need to resize the partition
flash android10 arm 64
lucsi said:
You need to resize the partition
flash android10 arm 64
Click to expand...
Click to collapse
I managed to flash the rom successfully, but I don't know if this only happens to me, I feel it is slow and the cell phone is heating up more than normal. ?
victorgrey999 said:
I managed to flash the rom successfully, but I don't know if this only happens to me, I feel it is slow and the cell phone is heating up more than normal. ?
Click to expand...
Click to collapse
Mine is ok. battery backup is ok.
Antutu ~96K point
You can install kernel management app to tweak the CPU freq
Related
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
I was the same predicament as you. I finally took the plunge and now I have Nougat running on my OP3. Here is what I did :
Start: OOS 3.2.8 w/ custom kernel and modified TWRP
1. Flash stock recovery (Google for a forum post in the OP3 forums on downloading the stock recovery and flash it through fastboot)
2. Reboot and let 3.2.8 start
3. Download Snap VPN and change the country to Canada. You will be prompted for the system update.
4. Let the update download (~1 GB)
5. Install the update. You may see an error of the installation may fail as your phone is rooted. Ignore and go ahead.
6. The installer will now boot to stock recovery and reboot with Nougat. All settings and apps will be maintained
The only catch is that you may have ext4 instead of f2fs. I am okay with it for now... But your mileage may vary
All the best!
Edit : Nougat running on my op3.
abhibnl said:
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
Click to expand...
Click to collapse
Are you rooted? Are you encrypted? What file systems are you using for your partitions? You're not giving full information. Why is formatting not an option if it'll give you the results you want?
To get to F2fs (I do recommend it)
Take a backup of your Data partition. , copy it to your pc with "adb pull /sdcard/Twrp/whatever".
Now go to Twrp>Wipe>Advanced select data and click on change file system. Change it to F2fs. Now restore your backup (Reader the guide all info is there). Profit!
anshulajain said:
I was the same predicament as you. I finally took the plunge and now I have Nougat running on my OP3. Here is what I did :
Start: OOS 3.2.8 w/ custom kernel and modified TWRP
1. Flash stock recovery (Google for a forum post in the OP3 forums on downloading the stock recovery and flash it through fastboot)
2. Reboot and let 3.2.8 start
3. Download Snap VPN and change the country to Canada. You will be prompted for the system update.
4. Let the update download (~1 GB)
5. Install the update. You may see an error of the installation may fail as your phone is rooted. Ignore and go ahead.
6. The installer will now boot to stock recovery and reboot with Nougat. All settings and apps will be maintained
The only catch is that you may have ext4 instead of f2fs. I am okay with it for now... But your mileage may vary
All the best!
Click to expand...
Click to collapse
I don't have any issues with ext4, infact i do feel ext4 is more stable than f2fs so file system is my last concern. Thanks for your method, but then how did u root again? Installing nougat is fine but what after that? I have read that you can't use modified twrp without formatting internal memory first, as it'll show you the pin issue. Let me know how do you propose a safe method to achieve root.
Renosh said:
Are you rooted? Are you encrypted? What file systems are you using for your partitions? You're not giving full information. Why is formatting not an option if it'll give you the results you want?
Click to expand...
Click to collapse
Yes i am encrypted, rooted, stock OOS 3.2.8 + Franco kernel. Official TWRP(not modified). I am using ext4, never used f2fs at all. The time to backup data and then to restore it all back is the reason formatting is not an "preferred" option for me. I can do it, but i would have to wait until i find enough time to do the whole process. I am in a full time job, so i hope you would understand.
Puddi_Puddin said:
To get to F2fs (I do recommend it)
Take a backup of your Data partition. , copy it to your pc with "adb pull /sdcard/Twrp/whatever".
Now go to Twrp>Wipe>Advanced select data and click on change file system. Change it to F2fs. Now restore your backup (Reader the guide all info is there). Profit!
Click to expand...
Click to collapse
Well this again defeats the purpose of my original question, but thanks mate. I would definitely read the guide if decide to switch to f2fs.
@abhibnl. BTW your encrypted. So the modified TWRP won't work.
How to fix:
Wipe Userdata with Fastboot / fastboot erase UserData
Boot into Twrp modified twrp.
Flash OOS 4.0 flash SuperSU and let it boot
You should be decrypted DO NOT install a boot password since you will be encrypted again.
I haven't rooted my phone again. My only reason to root is to install Adaway to block all ads. With DNS66 and Adguard, I have little incentive to root my stock nougat install.
Edit : I had encryption during 3.2.8 and it carried over to 4.0
Puddi_Puddin said:
@abhibnl. BTW your encrypted. So the modified TWRP won't work.
How to fix:
Wipe Userdata with Fastboot / fastboot erase UserData
Boot into Twrp modified twrp.
Flash OOS 4.0 flash SuperSU and let it boot
You should be decrypted DO NOT install a boot password since you will be encrypted again.
Click to expand...
Click to collapse
Thanks a lot for informing me mate. I really don't want to decrypt my storage as of now. I guess flashing stock recovery is the only solution now. Will hope someone would pick up the twrp and update it.
anshulajain said:
I haven't rooted my phone again. My only reason to root is to install Adaway to block all ads. With DNS66 and Adguard, I have little incentive to root my stock nougat install.
Edit : I had encryption during 3.2.8 and it carried over to 4.0
Click to expand...
Click to collapse
Seems like stock recovery is the best way as of now. Seems like I'll have to love without root until someone updates twrp to support encrypted storage.
I haven't updated to Nougat yet, but I looked over Chainfire's SuperSU changelog and its installation script and both of them confirm that from March installing SuperSU prevents forced encryption. Also many guides suggest installing it as way for disabling forced encryption. Of course you have to flash SuperSU just after flashing ROM, before booting the system.
abhibnl said:
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
Click to expand...
Click to collapse
Very simple indeed...
1. Switch on wifi
2. Download OTA and click install whem finished
3. Once installation completed, flash twrp .28 and latest su
4. Reboot and ignore any errors, youwill beup and running fine...
Zielony360 said:
I haven't updated to Nougat yet, but I looked over Chainfire's SuperSU changelog and its installation script and both of them confirm that from March installing SuperSU prevents forced encryption. Also many guides suggest installing it as way for disabling forced encryption. Of course you have to flash SuperSU just after flashing ROM, before booting the system.
Click to expand...
Click to collapse
That i already knew mate. But i WANT my storage to remain encrypted. And that's the issue with modified TWRP. You can't enter into recovery on that if your storage is encrypted.
kpmohamedhussain said:
Very simple indeed...
1. Switch on wifi
2. Download OTA and click install whem finished
3. Once installation completed, flash twrp .28 and latest su
4. Reboot and ignore any errors, youwill beup and running fine...
Click to expand...
Click to collapse
Again, "You can't enter into recovery on modified TWRP if your storage is encrypted." So i won't be able to enter into twrp in the first place, let alone flash anything.
abhibnl said:
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
Click to expand...
Click to collapse
In the same boat as you. I have OOS 3.2.8 encrypted, rooted and TWRP 3.0.2-1.26. I too would like to update but have way to much stuff on my phone to back it all up and restore it. Hope you or someone come's up with a solution. I will be following your thread.
Thanks.
Go to twrp. Press backup. Select only data. Save to PC youre backup for safety..
3.2.8 it's Android 6, 4.0 it's Android 7. Some apps might not work from base to base.
If you want to change to F2FS it will format youre phone, wipe phone full internal memory. If you want to change it back to ext4, same.
Clean flash, full wipe it's always better.
dmoses1969 said:
In the same boat as you. I have OOS 3.2.8 encrypted, rooted and TWRP 3.0.2-1.26. I too would like to update but have way to much stuff on my phone to back it all up and restore it. Hope you or someone come's up with a solution. I will be following your thread.
Thanks.
Click to expand...
Click to collapse
My suggestion (and my steps are in #1), install stock recovery, install snap VPN, download the update and install (ignore any errors on root). Once done, you will have Nougat with stock recovery, encryption maintained and all app data also intact.
anshulajain said:
My suggestion (and my steps are in #1), install stock recovery, install snap VPN, download the update and install (ignore any errors on root). Once done, you will have Nougat with stock recovery, encryption maintained and all app data also intact.
Click to expand...
Click to collapse
This is the last resort brother. With this method, unfortunately I won't have any root available. The only way now is to wait for updated twrp.
abhibnl said:
This is the last resort brother. With this method, unfortunately I won't have any root available. The only way now is to wait for updated twrp.
Click to expand...
Click to collapse
I dont know. I found this on Oneplus forum. May be worth trying. Just not 100% sure.....
Thanks! Will try and let you know
abhibnl said:
Thanks! Will try and let you know
Click to expand...
Click to collapse
Well, I tried something, waiting on it to finishing booting and see how it went.
I flashed twrp-3.0.2-1.28-oneplus3p version,
Flashed the OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip inside TWRP,
Flashed SR1-SuperSU-v2.79-SR1-20161221223537.zip right after flashing OTA zip.
Its rebooting and says Android is upgrading. Fingers crossed.
EDIT: Its booted and I am on Nougat, didnt lose my data and phone is still encrypted!
Edit: Ended up having issues with settings app locking up. So, I went a different route and its all working great now.
Downloaded the stock recovery image and renamed it to recovery.img
Make sure after you rename it its not named recovery.img.img, If you have show file extensions enabled on your pc you should already see the file extension.
Rebooted to bootloader - adb flash recovery recovery.img
Using the volume keys and power button selected - reboot recovery.
Now in stock recovery - flashed OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip
After rom is done flashing, went right back into bootloader. Did not let my phone reboot to start the OS.
Renamed twrp-3.0.2-1.28-oneplus3p.img to recovery.img
adb flash recovery recover.img
Powered off phone and Manually boot it into recovery by holding Power + Volume Down button.
Phone booted into TWRP
Flashed SR1-SuperSU-v2.79-SR1-20161221223537.zip
Wiped cache / dalvik
Rebooted system from TWRP and waited. System is really smooth now, no issues yet. Been playing with it for awhile now.
During the booting up process it might take a minute and it will reboot twice. Dont get nervous like I did thinking it was going to start bootlooping. It booted just fine. I read in a nother thread that SuperSU is what causes it to boot twice.
So......Now I have OOS 4.0 Nougat, Rooted, Encrypted and everything seems to be working fine.
Hey guys,
I got a problem and I am not sure what I’m doing wrong. I wanted to install a custom ROM to my Xiaomi Mi 6 but it doesn’t work. I’ve done similar steps to my Redmi 4X and there it worked just fine. A little help would be really appreciated.
Here is what I did. I updated my new device to the latest stable version with the updater app. I then had to install the official developer ROM (from MIUI) because of a bug (not able to register for unlock). I requested the unlock officially and after the waiting time unlocked the device with the MIUI unlock flash tool. In the developer options the device was shown as unlocked and also the bootloader was unlocked.
I installed TWRP 3.2.1-1 from the official website. After booting into TWRP I installed the latest mi-globe ROM (v9.5.3.0 oreo!). After a reboot I could see the logo of the mi-globe ROM but nothing would happen.
I did one mistake. The first time I installed the mi-globe ROM I forgot to wipe Dalvik, Cache, Data and System partition (clean install). So, after I recognized my mistake I rebooted into TWRP made the wipe and installed again but with no success.
After that I tried to install the next lower version of mi-globe (v9.2.4.0 with Android 7.1.1) but this got also stuck at the boot animation. The animation still moves but nothing happens. I waited for about 10 minutes.
5 minutes ago I flashed the official developer ROM with TWRP and it worked. The phone is booting. I was not able to flash the official stable ROM only the developer version works?!?!
Any idea what I did wrong? I flashed custom ROMs a couple of times but never got a problem like this.
Thank you!
Problem solved!
I got it working now. Problem was that wiping data is not enough. I read it in another post. So, if someone has the same problem here is how I solved it:
1. Boot into TWRP
2. FORMAT data (not wipe) - go to wipe, click button in right corner to format data
3. Type in “yes” (all data will be erased!!)
4. Reboot into recovery (TWRP)
5. Go to wipe and wipe Dalvik, Cache, and System
6. Reboot into recovery (TWRP)
7. Go to install and install zip of ROM you would like to install
8. Reboot system - worked!!
:good::good:
The rebooting into recovery is just for safety. I read that if system is wiped the partition could not be available for installation if you don't reboot. So, I guess its better to reboot just be sure.
I have one question or help if I can. I have Mi6 with a global stable rom 9.5.3.0 version. I want to go to the global developer rom. 8.4.12 how to do it if there is a way to not open the bootloader.
zolika1 said:
I have one question or help if I can. I have Mi6 with a global stable rom 9.5.3.0 version. I want to go to the global developer rom. 8.4.12 how to do it if there is a way to not open the bootloader.
Click to expand...
Click to collapse
just download the developer rom an place it in phone memory. goto settings>about>system update. press the 3 dot button and choose update package . Developer rom will be installed without unlocking bootloader.
saadtariq73 said:
just download the developer rom an place it in phone memory. goto settings>about>system update. press the 3 dot button and choose update package . Developer rom will be installed without unlocking bootloader.
Click to expand...
Click to collapse
thank you very much for the instructions, to erase everything from the phone or not?
zolika1 said:
thank you very much for the instructions, to erase everything from the phone or not?
Click to expand...
Click to collapse
It probably will yes. I seem to remember it happening even with locked bootloader
Hi all, I've asked this question here ( https://forum.xda-developers.com/9-lite/help/how-update-project-treble-gsi-image-t3851002 ) also but am hoping this forum is more specific to my needs. I'll repeat the question here perhaps i'll have better luck with an answer !
there's a lot about installing gsi images on various phones that support project treble but i cannot find anything about how you update them. I installed OmniRom beta3, via fastboot, on my H9L and 3 days later they put out an update. The rom works fine and i set it up to my preference with magisk and it even shows up as Play certified, so all is good. However, with the update I prefer not to go through the whole magisk uninstall/install again. Anyone here knows how you would update an existing gsi images ? If I use fastboot to load the new update wouldn't that erase everything again, as stated on the openkirin.net installation instructions here ( https://openkirin.net/user_guide/openkirin-rom-installation-instructions/ ) ? or could i just fastboot the new beta3.1 over beta3 and just not do a factory reset as recommended ?
If a factory reset is essential everytime then this basically means we have to rebuild everything everytime there is an update ! I hope not.
Weird everyone writes about installation and no one thinks about updates ?
xzyk said:
Hi all, I've asked this question here ( https://forum.xda-developers.com/9-lite/help/how-update-project-treble-gsi-image-t3851002 ) also but am hoping this forum is more specific to my needs. I'll repeat the question here perhaps i'll have better luck with an answer !
there's a lot about installing gsi images on various phones that support project treble but i cannot find anything about how you update them. I installed OmniRom beta3, via fastboot, on my H9L and 3 days later they put out an update. The rom works fine and i set it up to my preference with magisk and it even shows up as Play certified, so all is good. However, with the update I prefer not to go through the whole magisk uninstall/install again. Anyone here knows how you would update an existing gsi images ? If I use fastboot to load the new update wouldn't that erase everything again, as stated on the openkirin.net installation instructions here ( https://openkirin.net/user_guide/openkirin-rom-installation-instructions/ ) ? or could i just fastboot the new beta3.1 over beta3 and just not do a factory reset as recommended ?
If a factory reset is essential everytime then this basically means we have to rebuild everything everytime there is an update ! I hope not.
Weird everyone writes about installation and no one thinks about updates ?
Click to expand...
Click to collapse
Just reboot to recovery flash update wipe cache and dalvik if u want.reboot
marcukial said:
Just reboot to recovery flash update wipe cache and dalvik if u want.reboot
Click to expand...
Click to collapse
How do you flash .img image through factory recovery ? If you read the openkirin instructions their gsi images are all in .img format and supported only when flashed through factory recovery. TWRP recovery is not an option for me as this phone is not well supported through it. Thanks anyway.
xzyk said:
How do you flash .img image through factory recovery ? If you read the openkirin instructions their gsi images are all in .img format and supported only when flashed through factory recovery. TWRP recovery is not an option for me as this phone is not well supported through it. Thanks anyway.
Click to expand...
Click to collapse
Just do the same thing you did to flash the GSI in fastboot.
Code:
fastboot flash system system.img
You don't need to do any wipes, but it's a good idea to wipe cache from the stock recovery after updating.
Hi,
i was looking for the same question to update the gsi files.
But how can I update the other files that Huawei provides, is this necessary with Trebe or do i need only update the system.img?
I tried this Tutorial 2, but there is everytime a factory reset.
https://forum.xda-developers.com/p10/how-to/guide-manual-updgrade-to-update-oreo-t3758286
regards
bacardi
It's been three years since i changed phones and I naively thought that things had gotten easier.
But nope. Still a mess of stiching together various incomplete "guides" from around the web only
to end up with a phone stuck in a boot-loop.
It's a Galaxy S9. Using Odin I've been able to install TWRP 3.3.1-0.
With that I tried installing both Carbon ROM as well as Havoc OS each followed by Open Gapps 8.
In some of the "guides" there was mentions of no-verity, so I've tried adding that in various steps.
Still, the only thing that works reliably is power+bixby+up to enter twrp. It's the only way I've found
to power down the phone.
Very grateful for any suggestion.
I've thought about installing the ROM using Odin, but I'm afraid that I would lose twrp.
From TWRP boot into download mode and use Odin to flash stock.
Or download soldier ROM and flash that in TWRP. It's based on stock ROM.
basicreece said:
From TWRP boot into download mode and use Odin to flash stock.
Or download soldier ROM and flash that in TWRP. It's based on stock ROM.
Click to expand...
Click to collapse
Thanks for taking the time to reply - I appreciate it!
Just to be suuuper clear: Should I flash the ROM the same way as I did twrp? Option AP and F. Reset time?
And why stock ROM? That's where I came from. Ultimately I want a custom ROM (preferably Carbon or Havoc).
Is this a step towards that?
Sam Sunk said:
Thanks for taking the time to reply - I appreciate it!
Just to be suuuper clear: Should I flash the ROM the same way as I did twrp? Option AP and F. Reset time?
And why stock ROM? That's where I came from. Ultimately I want a custom ROM (preferably Carbon or Havoc).
Is this a step towards that?
Click to expand...
Click to collapse
Flashing stock will return your phone to the way it was when you bought it, having to flash TWRP etc all over again
When flashing stock you flash all 4 sections together and do not change any settings in Odin
CSC = Reset phone
HOME CSC = Do not reset
Only use one or the other
You will need to use CSC if you have TWRP / Custom installed
If you are wanting a custom ROM flashed from TWRP you should wait for someone else who knows why it won't flash to help you as I have just kept stock on my S9 so don't know what's wrong
You do know you flash the custom ROM zip using TWRP right? Copying it to your SD card then choosing it from TWRP itself, not using Odin
*Detection* said:
You do know you flash the custom ROM zip using TWRP right? Copying it to your SD card then choosing it from TWRP itself, not using Odin
Click to expand...
Click to collapse
That's exactly what I did. I used Odin to install twrp and then tried to install the custom ROM with twrp. That's when the wheels came off and the phone got stuck booting.
So what do I do to install a custom ROM on my S9?
I'm positive I've followed every step of the guides, but there's always the feeling that they are written for AnyAndroidPhone (TM) and that there's some device-specific quirk that's left out.
Sam Sunk said:
So what do I do to install a custom ROM on my S9?
I'm positive I've followed every step of the guides, but there's always the feeling that they are written for AnyAndroidPhone (TM) and that there's some device-specific quirk that's left out.
Click to expand...
Click to collapse
Then you should follow the guides on this XDA S9 forum instead, then you know they are for the S9
Sam Sunk said:
So what do I do to install a custom ROM on my S9?
I'm positive I've followed every step of the guides, but there's always the feeling that they are written for AnyAndroidPhone (TM) and that there's some device-specific quirk that's left out.
Click to expand...
Click to collapse
you still bricked?
In TWRP did the internal storage maybe say 0mb? Tat happens when you dont abort the factory reset after OEM unlock. If it is that than just go to advanced wipe, pormat your data to fat2 and then back to fat4
Hey there, I had the exact same problem over the past 2 days - so I feel your frustration.
I have a 9604f (galaxy s9) , and there are different types so you may have to see if yours is different. I also used ressurrection remix OS. Short version is:
1. Get resurrection remix (final version for starlte)
2. Get gapps (for 8.1 arm64)
3. Get magisk
The above 3 are all on the post for the official resurrection remix on this site with the header -[ROM] [OFFICIAL] [6/01/18] ResurrectionRemix 6.0 for S9/S9+ (Exynos)
4. Download the BRE5 vendor. I used a link that went to a mega.nz site and it worked. So I'm sure you'll be able to find one. I can't post links cause this is my first post.
5. Boot into twrp
6. Format data in wipe section of twrp
7. Wipe dalvik, cache, data, system.
8. Install in this order -do not reboot or wipe anything. Just install.
(I) BRE5 vendor
(II) resurrection remix ROM
(III) gapps
9. DONT WIPE cache, and reboot into the OS
10. If you want root -just go back into twrp once you have set up google, apps etc. And then install the magisk zip.
update
Not bricked any more.
The advice from @basicreece to install soldier worked. I made a second attempt to install Carbon afterwards but that resulted again in a twrp-only device. Now I'm back on soldier.
Perhaps I'll give @Madsikhey's instructions a go later.
To show my gratitude for all the help in times of darkness I'd like to give back and I'll let @basicreece decide:
1. Donation to XDA
2. Donation to EFF
3. A beer/coffee for yourself (PayPal)
Answer me in a PM.
Madsikhey said:
Hey there, I had the exact same problem over the past 2 days - so I feel your frustration.
I have a 9604f (galaxy s9) , and there are different types so you may have to see if yours is different. I also used ressurrection remix OS. Short version is:
1. Get resurrection remix (final version for starlte)
2. Get gapps (for 8.1 arm64)
3. Get magisk
The above 3 are all on the post for the official resurrection remix on this site with the header -[ROM] [OFFICIAL] [6/01/18] ResurrectionRemix 6.0 for S9/S9+ (Exynos)
4. Download the BRE5 vendor. I used a link that went to a mega.nz site and it worked. So I'm sure you'll be able to find one. I can't post links cause this is my first post.
5. Boot into twrp
6. Format data in wipe section of twrp
7. Wipe dalvik, cache, data, system.
8. Install in this order -do not reboot or wipe anything. Just install.
(I) BRE5 vendor
(II) resurrection remix ROM
(III) gapps
9. DONT WIPE cache, and reboot into the OS
10. If you want root -just go back into twrp once you have set up google, apps etc. And then install the magisk zip.
Click to expand...
Click to collapse
Hello, Iám also having the same problem. I got all the files needed but the BRE5 Vendor file, could anyone link it plz? Iám using a G960F (S9).
Haxomen said:
In TWRP did the internal storage maybe say 0mb? Tat happens when you dont abort the factory reset after OEM unlock. If it is that than just go to advanced wipe, pormat your data to fat2 and then back to fat4
Click to expand...
Click to collapse
Thanks :good::good::good:
I have somewhat same problem. Rooted my S9 original OS and it worked fine. After power off the phone is in bootloop and the only way to shut the phone off is to boot in the twrp and reboot-->shut off.
And the only way to get to the twrp is power+volume up+bixby button combination.
I made a thread about my problem, it's here
Problems with rooting Galaxy S9 (Android 10 Exynos SM-G960F)
Hi, this is My first post here, so be gentle. My old Oneplus died and I bought a used Samsung Galaxy S9. I tested the phone with an original OS and it worked fine. Yesterday I decided to root it (there are a few features that need root and I...
forum.xda-developers.com
Now I'm stuck and I need a help to proceed. What i should do to get the phone open again? Would it be a good idea to flash lineageOS now, or is there a way to reset the phone back to original?
I can open trwp or download mode, but cannot boot to the OS.
Hey guys,
It's nice to see preloader is received and I installed first time when I find it. Currently when I press Power+Up, it will have a DOS-like menu for me to choose, It occured after I installed preloader. At his point, can I install TWRP and then root? Will this DOS-like menu be replaced after TWRP? After installing TWRP, do I need to wipe data etc? I have heaps of apps and games installed, and I try not to do so.
My andorid is 9 and Chinese+Global Rom
Thanks
idog8818 said:
Hey guys,
It's nice to see preloader is received and I installed first time when I find it. Currently when I press Power+Up, it will have a DOS-like menu for me to choose, It occured after I installed preloader. At his point, can I install TWRP and then root? Will this DOS-like menu be replaced after TWRP? After installing TWRP, do I need to wipe data etc? I have heaps of apps and games installed, and I try not to do so.
My andorid is 9 and Chinese+Global Rom
Thanks
Click to expand...
Click to collapse
For the rom to work the way it is supposed to, you have to wipe everything except sd card. So you can backup those apps to sdcard or not. I advise you wipe everything, because it might bring you problems if you don't wipe them.
Okay I just did all this today. Let me quote it step by step.
1. Unlocked bootloader after waiting for 168 hours.
2. Flashed Indian version of MIUI 11 rom based on Android 9.
3. Flashed Pre-loader files & lk and lk2 files successively.
4. Flashed LR TWRP recovery.
5. Flashed a popular custom rom but found it buggy.
6. Reverted back to the Indian Rom again.
soleali said:
Okay I just did all this today. Let me quote it step by step.
1. Unlocked bootloader after waiting for 168 hours.
2. Flashed Indian version of MIUI 11 rom based on Android 9.
3. Flashed Pre-loader files & lk and lk2 files successively.
4. Flashed LR TWRP recovery.
5. Flashed a popular custom rom but found it buggy.
6. Reverted back to the Indian Rom again.
Click to expand...
Click to collapse
What popular rom did you tried, for how much time and what bugs you ve encountered?
Im on Global Rom and it seems quite stable. Just want root but scare of hard-bricking, I had this before and paid $30 for online services.
soleali said:
Okay I just did all this today. Let me quote it step by step.
1. Unlocked bootloader after waiting for 168 hours.
2. Flashed Indian version of MIUI 11 rom based on Android 9.
3. Flashed Pre-loader files & lk and lk2 files successively.
4. Flashed LR TWRP recovery.
5. Flashed a popular custom rom but found it buggy.
6. Reverted back to the Indian Rom again.
Click to expand...
Click to collapse
Why don't you install official TWRP? Also after installing, when you boot up with power+UP, still have preloader menu, then choose recovery to enter TWRP?
idog8818 said:
Why don't you install official TWRP? Also after installing, when you boot up with power+UP, still have preloader menu, then choose recovery to enter TWRP?
Click to expand...
Click to collapse
At first I installed LR TWRP but couldn't boot into custom OS. Then I installed Orangefox and I was able to boot. Yes pre-loader was already there... I guess pre-loader goes away when you flash any official MIUI rom as this happened with me. After flashing the Indian ROM again I had to flash pre-loader and recovery files.
Raresh T said:
What popular rom did you tried, for how much time and what bugs you ve encountered?
Click to expand...
Click to collapse
Cesium OS. Overall its a good os, much stable and can be definitely used as a daily driver except for the fingerprint sensor issue. If you try to wake up device using fingerprint, it freezes and never displays the screen even when the power button is pressed. You have to restart the device to make it workable. Its a known bug.
soleali said:
Okay I just did all this today. Let me quote it step by step.
1. Unlocked bootloader after waiting for 168 hours.
2. Flashed Indian version of MIUI 11 rom based on Android 9.
3. Flashed Pre-loader files & lk and lk2 files successively.
4. Flashed LR TWRP recovery.
5. Flashed a popular custom rom but found it buggy.
6. Reverted back to the Indian Rom again.
Click to expand...
Click to collapse
What exactly I need to do after installing twrp and first time in it. I read other posts saying tip something and even format data etc.
idog8818 said:
What exactly I need to do after installing twrp and first time in it. I read other posts saying tip something and even format data etc.
Click to expand...
Click to collapse
Just install Magisk and load any custom os of your choice when you are done installing twrp. Remember, some roms require a specific version of recovery and Magisk installation also needs to be done carefully. Good Luck!
soleali said:
Just install Magisk and load any custom os of your choice when you are done installing twrp. Remember, some roms require a specific version of recovery and Magisk installation also needs to be done carefully. Good Luck!
Click to expand...
Click to collapse
I did this 2 months ago, after "just install Magisk" It's hard bricked, and $30 to ask for online service to unlock.
did anyone tried flashing treble roms on the phone ? perhaps they work a bit better.
idog8818 said:
I did this 2 months ago, after "just install Magisk" It's hard bricked, and $30 to ask for online service to unlock.
Click to expand...
Click to collapse
Oh. What about the pre-loader? Didn't you install it in the first place?
soleali said:
Oh. What about the pre-loader? Didn't you install it in the first place?
Click to expand...
Click to collapse
When I bought this phone, there was no pre-loader yet, and not much users know it's so easy to brick.
idog8818 said:
When I bought this phone, there was no pre-loader yet, and not much users know it's so easy to brick.
Click to expand...
Click to collapse
In a new phone there is no pre-loader installed.