Related
I've seen this problem mentioned in a few threads but not seen any definitive fix.
My current install :
Stock NPD35K system, vendor, bootloader
Xceede's v8.01 kernel
TWRP 3.02 v6.0
Encrypted data partition
I currently get bootloops every time I boot into TWRP. After using TWRP and attempting to reboot it will then bootloop into recovery refusing to boot the system.
I have found it can be fixed by rebooting into fastboot and the "fastboot reboot" command. But this is frustrating if I don't have a laptop handy.
This happens every time I need to boot into recovery to install or update via TWRP. Is anyone else getting the same bootloops and has anyone found a permanent fix?
Thanks guys.
Sent from my Nexus 6P using Tapatalk
Hi Jake,
I had exactly the same issue since NPD35K except the fastboot reboot solution did not work for me.
What i could find was that if you flash the default vendor, recovery and cache partition via fastboot and then put off the tablet, it should after all of this boot correctly to the system.
Cheers,
Mathieu
You are not alone ..
I had the recovery bootloop once myself.
I did the "fastboot reboot" command and since then the Pixel C is booting fine again.
Did several installations afterwards .. no problems anymore.
Just once ..
But if you get it every reboot this a real problem.
Right now I am not able to help you .. just don't know the root cause and how to fix it.
As it looks like, it helps if you go back to stock recovery, like mentioned above.
I can not confirm this .. as I don't have the problem.
Good luck !
Thanks for the advice guys.
As I said it only bootloops immediately after boating into TWRP (even if I don't install anything), if I reboot from system it's fine.
At the moment I prefer to keep TWRP installed and reboot from fastboot if I need to use TWRP. I don't see an advantage to installing the stock recovery. It would be great to pinpoint what's causing this though.
Sent from my Pixel C using Tapatalk
I'm still getting this TWRP bootloop. I've tried several versions - 3.0.0, 3.0.21, 3.0.23. I've tried numerous times re-flashing stock using NRT and then flashing the recovery again. I've also tried fastboot-reboot.
I'm on stock 7.1.1 - NMF26H. If i need to install a different version for this to work I can do that.
Is there perhaps some particular version of TWRP that everyone but me is using? Or are there some specific versions of other files that I also need to flash along with TWRP? From what I've read if I get past this once that's probably it.
Thanks
badwiring said:
I'm still getting this TWRP bootloop. I've tried several versions - 3.0.0, 3.0.21, 3.0.23. I've tried numerous times re-flashing stock using NRT and then flashing the recovery again. I've also tried fastboot-reboot.
I'm on stock 7.1.1 - NMF26H. If i need to install a different version for this to work I can do that.
Is there perhaps some particular version of TWRP that everyone but me is using? Or are there some specific versions of other files that I also need to flash along with TWRP? From what I've read if I get past this once that's probably it.
Thanks
Click to expand...
Click to collapse
Pls install latest bootloader and latest factory image via fastboot, manually.
Pls use latest fastboot binaries from Google.
Pls install 3.0.2-23 via fastboot as well.
Reboot directly into TWRP and not into system in between.
Install SuperSu.zip v2.79 in TWRP.
Reboot into system.
The first time the system will boot twice .. it's normal.
followmsi said:
Pls install latest bootloader and latest factory image via fastboot, manually.
Pls use latest fastboot binaries from Google.
Pls install 3.0.2-23 via fastboot as well..
Click to expand...
Click to collapse
Thank you. I'll try this today. If I use s tool like NRT to flash "stock" to the device, does that cover what's described in the first step - latest bootloader and latest factory image - or is there something else I need to flash at that step?
Thanks
badwiring said:
Thank you. I'll try this today. If I use s tool like NRT to flash "stock" to the device, does that cover what's described in the first step - latest bootloader and latest factory image - or is there something else I need to flash at that step?
Thanks
Click to expand...
Click to collapse
Maybe your problem is related to the tool itself
For this reason I recommend to use the official google fastboot tool for complete flashing of factory image including bootloader.
To have a proper base to continue ..
Good luck !
EDIT: .. no need to wipe data here. Just a fresh system, vendor, cache and boot image from factory image.
followmsi said:
Maybe your problem is related to the tool itself
For this reason I recommend to use the official google fastboot tool for complete flashing of factory image including bootloader.
To have a proper base to continue ..
Good luck !
Click to expand...
Click to collapse
I think that answers my question - the original factory image including the bootloader.
I'll try it in a few hours. Thank you very much!
That worked! I was currently on stock 7.1.1 so I tried it first without re-flashing, although I was prepared to go back to that step if it didn't work.
First I downloaded SuperSU 2.79 and copied the ZIP to my device.
I used Minimal ADB and Fastboot (which I think is taken from the official Google source) and flashed recovery-twrp-3.0.2.23.followmsi-ryu.img.
Then I rebooted into recovery - not system - and flashed SuperSU.
Finally I rebooted into system.
The Google logo appeared for a moment and then it booted again (exactly as you said.) Then it booted normally.
Finally! Thank you very much! Hopefully this will help someone else too. It can be the smallest detail we miss that makes the difference.
badwiring said:
That worked! I was currently on stock 7.1.1 so I tried it first without re-flashing, although I was prepared to go back to that step if it didn't work.
First I downloaded SuperSU 2.79 and copied the ZIP to my device.
I used Minimal ADB and Fastboot (which I think is taken from the official Google source) and flashed recovery-twrp-3.0.2.23.followmsi-ryu.img.
Then I rebooted into recovery - not system - and flashed SuperSU.
Finally I rebooted into system.
The Google logo appeared for a moment and then it booted again (exactly as you said.) Then it booted normally.
Finally! Thank you very much! Hopefully this will help someone else too. It can be the smallest detail we miss that makes the difference.
Click to expand...
Click to collapse
You are welcome ..
``
tried numerous times to flash TWRP to my Pixel C 8.0.0 (OPR1.170623.032, Nov 2017) every time with bootloop in to recovery...
most recently hoping twrp-3.2.0-0-dragon would work
---------- Post added at 07:44 PM ---------- Previous post was at 07:29 PM ----------
tried to reflash ryu-opr1.170623.032-factory-020f1cf9's boot.img and it still bootlooped.
Tried to flash the recovery and now its bootlooping into stock recovery. Any ideas?
for a stock google device, this things a nightmare to work with compared to my nexus devices
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.
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.
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
Hey
couldn't find anything related to my situation so I decided to ask. Here it goes:
After having to wait an entire week to unlock the bootloader (really??) its finally unlocked and I decided to install LineageOS.
Got a Mi10T Lite, gauguin, M2007J17G. It managed to snuck in an update to something like August 2020 security level at some point but after unlocking it got reset, so I suppose it had Android 10 and MIUI 12(?).
Simple enough, have done that countless times before.
- Flashed recovery, format data/factory reset as explained in wiki
- adb sideloaded ROM (nightly builds 20220822 and 20220815) - both succeeded
After rebooting the devices enters the bootloader again.
The wiki never mentions behaviour like this and I couldn't find anything online.
Do I need to flash latest MIUI ROM again?
Any ideas what went wrong and how to solve this issue?
I unzipped the ROM and fastboot boot boot.img which just resulted in a reboot to fastboot again.
Any idea or, preferrably, a solution would be most welcome
Thanks in advance.
woelkchen said:
Hey
couldn't find anything related to my situation so I decided to ask. Here it goes:
After having to wait an entire week to unlock the bootloader (really??) its finally unlocked and I decided to install LineageOS.
Got a Mi10T Lite, gauguin, M2007J17G. It managed to snuck in an update to something like August 2020 security level at some point but after unlocking it got reset, so I suppose it had Android 10 and MIUI 12(?).
Simple enough, have done that countless times before.
- Flashed recovery, format data/factory reset as explained in wiki
- adb sideloaded ROM (nightly builds 20220822 and 20220815) - both succeeded
After rebooting the devices enters the bootloader again.
The wiki never mentions behaviour like this and I couldn't find anything online.
Do I need to flash latest MIUI ROM again?
Any ideas what went wrong and how to solve this issue?
I unzipped the ROM and fastboot boot boot.img which just resulted in a reboot to fastboot again.
Any idea or, preferrably, a solution would be most welcome
Thanks in advance.
Click to expand...
Click to collapse
Try to flash the last firmware or rom
V13.0.4.0.SJSMIXM
https://xiaomifirmwareupdater.com/firmware/gauguin/
https://xiaomirom.com/en/rom/mi-10t-lite-gauguin-global-fastboot-recovery-rom/
TWRP
https://androidfilehost.com/?w=files&flid=318225
Thx. Went ahead and did that which ofc solved the issue. Thx a lot
Hi, I have same issue. I installed lineage 19.1 2022-09-26 on Mi 10T lite, actually last nightly, and after succesfull installation, after reboot lineage doesnt start and i have just fastboot mode. I have lineage recovery installed, and if i try to install recovery-rom, i dont feel comfortable on installing fastboot-rom, i get error, just after 47% i get unknown signature and it ask if i want continue, if i choose yes continue, on device it says it cant downgrade so its stopped. I also deleted cache but it didnt help, im not very happy to format system partition, im worried to brick it. Should i format system partition? And how deal with missing signature when i try to push stock rom? should i allow it?
BolognaTown said:
Hi, I have same issue. I installed lineage 19.1 2022-09-26 on Mi 10T lite, actually last nightly, and after succesfull installation, after reboot lineage doesnt start and i have just fastboot mode. I have lineage recovery installed, and if i try to install recovery-rom, i dont feel comfortable on installing fastboot-rom, i get error, just after 47% i get unknown signature and it ask if i want continue, if i choose yes continue, on device it says it cant downgrade so its stopped. I also deleted cache but it didnt help, im not very happy to format system partition, im worried to brick it. Should i format system partition? And how deal with missing signature when i try to push stock rom? should i allow it?
Click to expand...
Click to collapse
Cant use LOS recovery for stock rom.
go back to Miui
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
NOSS8 said:
Cant use LOS recovery for stock rom.
go back to Miui
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Click to expand...
Click to collapse
i didnt understand completely, should i find stock recovery and 'fastboot flash recovery stock-recovery.img'
or just using miflashtool without adding any stock recovery?
BolognaTown said:
i didnt understand completely, should i find stock recovery and 'fastboot flash recovery stock-recovery.img'
or just using miflashtool without adding any stock recovery?
Click to expand...
Click to collapse
Use Miflash and read the tutorial carefully.
Miflash=Fastboot rom
Thank you, i unbricked it, and i installed lineage. Great Job