Related
I will try to describe problem as much as I can:
1.Unlocked bootloader(unofficial way).
2.Installed TWRP 3.0.M4-0(success).
3.Installed(in such order as stated by some guide) : CM14.1 Firmware(Kate) - 26.11.2016 >>> CM14.1-20161222 Nightly Kenzo >>> Opengapps arm64 7.1 nano with TWRP(success).
4.Reboot, CM 14.1 launches correctly, although it has saved settings and apps from MIUI, making it real mess. Now the problem starts. I assumed by doing factory reset I'll get clean 14.1 - wrong. After that turning on my phone causes it to launch TWRP instead of system.
(Failed)Attempts to fix:
1.Install CM14.1 again.
2.Wipe + install CM14.1 again.
3.Can't get into EDL mode(as stated here http://en.miui.com/thread-290959-1-1.html)
Additional info:
1.Fastboot mode launches, but 'adb devices' doesn't find anything(it was before). Device manager sees phone as well as MiFlash. Not succesful trying to update drivers(system found them up-to-date).
2.I have Kate edition, started installing after reading this http://forum.xda-developers.com/redmi-note-3/how-to/index-custom-roms-t3396628 , last posts states, that sometimes it's necessary to flash non-hlos.bin file to system(not sure if even necessary in my case, as CM14.1 launched before factory cleaning).
3.Only similar thing I found is : http://forums.androidcentral.com/sa...p-after-factory-reset-cyanogenmod-12-1-a.html , but about different device and CM version.
I'll appreciate any suggestions on how to fix it(either getting into CM14.1 or back to MIUI, preferably the first).
@edit - Solved myself. For anyone encountering such problem, I could install succesfully MIUI back, when I launched my windows in Disable Drivers Signature Mode.
what exactly have you done at the point "factory cleaning" ? do you mean anything in running android or in TWRP?
h0LLe said:
what exactly have you done at the point "factory cleaning" ? do you mean anything in running android or in TWRP?
Click to expand...
Click to collapse
Factory clean from android settings after running CM14.1 succesfully for the first time. No idea why it caused a problem, but as I wrote in edit, it is solved.
Hi guys,
first of all: I am an idiot
I was using an old nightly from CM 13-kenzo and decided to do some preparation to finally migrate to Lineage without data loss.
So I wanted to go to CM14.1 before flashing the experimental Lineage and the nightly.
What did I flash with TWRP?
1.) ROM: cm-14.1-20161225-NIGHTLY-kenzo.zip
2.) GAPPS 7.1 ARM64 micro
3.) Firmware: CM14.1-firmware_20161205.zip
I think I should have flashed the firmware first, moreover, I didn't wipe caches.
What's happening now?
Recovery mode does not work (the display just flash for half a second)
Booting does not work (ofc )
Fastboot mode still works.
How can I fix this nice problem with Cyanogenmod?
Any help is much appreciated.
Bro,I also faced this problem. Just go to guides section and follow the guide"install zcx twrp without unlocking bootlader" one. And flash by that method twrp and you will get it all back.
I have also faced problem same you are facing and solved it!!!
Btw. which recovery you used while installing this build?
ATG Droid said:
Btw. which recovery you used while installing this build?
Click to expand...
Click to collapse
Your bootloader is locked
Snooze4 said:
Hi guys,
first of all: I am an idiot
I was using an old nightly from CM 13-kenzo and decided to do some preparation to finally migrate to Lineage without data loss.
So I wanted to go to CM14.1 before flashing the experimental Lineage and the nightly.
What did I flash with TWRP?
1.) ROM: cm-14.1-20161225-NIGHTLY-kenzo.zip
2.) GAPPS 7.1 ARM64 micro
3.) Firmware: CM14.1-firmware_20161205.zip
I think I should have flashed the firmware first, moreover, I didn't wipe caches.
What's happening now?
Recovery mode does not work (the display just flash for half a second)
Booting does not work (ofc )
Fastboot mode still works.
How can I fix this nice problem with Cyanogenmod?
Any help is much appreciated.
Click to expand...
Click to collapse
. Your bootloader is lock, if you still can get to fastboot, then enter edl mode and use miflash to unlock yourboot loader again
Thx. Does Miflash work on a chromebook?
Mrxyzl said:
. Your bootloader is lock, if you still can get to fastboot, then enter edl mode and use miflash to unlock yourboot loader again
Click to expand...
Click to collapse
Do you mean the MiFlash Unlock tool? That doesn't work.
It's saying "Your device isn't supported by Mi Unlock" Go to .../unlock to apply for Mi Unlock support.
If you mean XiaomiMiFlash tool, what exactly do I have to flash?
Snooze4 said:
Do you mean the MiFlash Unlock tool? That doesn't work.
It's saying "Your device isn't supported by Mi Unlock" Go to .../unlock to apply for Mi Unlock support.
If you mean XiaomiMiFlash tool, what exactly do I have to flash?
Click to expand...
Click to collapse
Yes, I mean Miflash tool. You need to folow this guide
http://en.miui.com/thread-235865-1-1.html
And remember you will lost all data in internal memory, you will get back to MIUI with that guide. Then try to unlock your bootloader officially or unofficially again.
Or if you woud like to take risk then you can try this way https://forum.xda-developers.com/redmi-note-3/how-to/unlock-unofficially-install-zcx-twrp-t3586778 without data lost
Mrxyzl said:
Yes, I mean Miflash tool. You need to folow this guide
http://en.miui.com/thread-235865-1-1.html
And remember you will lost all data in internal memory, you will get back to MIUI with that guide. Then try to unlock your bootloader officially or unofficially again.
Or if you woud like to take risk then you can try this way https://forum.xda-developers.com/redmi-note-3/how-to/unlock-unofficially-install-zcx-twrp-t3586778 without data lost
Click to expand...
Click to collapse
Regarding your 2nd link:
now bring your phone in action and turn on oem unlock from developer optipn(tap miui version 7 time and find developer option in additional option)
sign out of your mi account
Click to expand...
Click to collapse
That would be the impossible part. So I guess I've to work with the first link. Thanks.
So if you damaged the recovery and your bootloader is locked theres no way to rescue this phone without a xiaomi shop but good luck
Okay problem solved. I used this guide https://forum.xda-developers.com/redmi-note-3/how-to/kate-guide-install-lineage-os-locked-t3546154 and it worked like a charm.
Thread can be closed.
Hello,
My Thor device seems to be bricked after trying to enable encryption in Lineage OS (this happened a couple of months ago).
The device used to have an unlocked bootloader with TWRP 3.1.1-1, Lineage OS 14.1 20170710 and Open GApps installed and was running without any problems (thanks to all the people here who have made this possible btw!) until enabling encryption. The encryption process was running for an eternity (more than one day), so I switched the device off.
Since then, I only get a grey "kindle fire" logo. No booting of Lineage or TWRP anymore . It's possible to start in fastboot mode via pressing the on/off switch and the volume button simultaneously, though.
I don't have any experience with bricked devices. Any suggestions what to do? And are there known issues with encryption on this device?
Many thanks in advance for your help!
RiseT said:
Hello,
My Thor device seems to be bricked after trying to enable encryption in Lineage OS (this happened a couple of months ago).
The device used to have an unlocked bootloader with TWRP 3.1.1-1, Lineage OS 14.1 20170710 and Open GApps installed and was running without any problems (thanks to all the people here who have made this possible btw!) until enabling encryption. The encryption process was running for an eternity (more than one day), so I switched the device off.
Since then, I only get a grey "kindle fire" logo. No booting of Lineage or TWRP anymore . It's possible to start in fastboot mode via pressing the on/off switch and the volume button simultaneously, though.
I don't have any experience with bricked devices. Any suggestions what to do? And are there known issues with encryption on this device?
Many thanks in advance for your help!
Click to expand...
Click to collapse
Have you tried booting a TWRP image from fastboot? If that works recovery will be a lot easier.
fastboot devices
--> if no response to this command you'll need to update host drivers
fastboot boot <twrp-image-name>
--> you can download a suitable TWRP image from here
Davey126 said:
Have you tried booting a TWRP image from fastboot? If that works recovery will be a lot easier.
fastboot devices
--> if no response to this command you'll need to update host drivers
fastboot boot <twrp-image-name>
--> you can download a suitable TWRP image from here
Click to expand...
Click to collapse
Excellent! MANY MANY THANKS! You've made my day! Worked like a charm (i. e. worked like a charm after my usual trial & error for hours to make Windows accept a Kindle Fire driver for fastboot - had to force one it warned me about on it to make it finally work).
A couple more question if I may:
When and why does one need a "Fastboot cable" (always been confused about this)?
Do you happen to know if device encryption normally works with this device?
Does switching debugging off in Lineage prevent unbricking via fastboot like this (wouldn't think so but want to make sure)?
Thanks again!
RiseT said:
Excellent! MANY MANY THANKS! You've made my day! Worked like a charm (i. e. worked like a charm after my usual trial & error for hours to make Windows accept a Kindle Fire driver for fastboot - had to force one it warned me about on it to make it finally work).
A couple more question if I may:
When and why does one need a "Fastboot cable" (always been confused about this)?
Do you happen to know if device encryption normally works with this device?
Does switching debugging off in Lineage prevent unbricking via fastboot like this (wouldn't think so but want to make sure)?
Thanks again!
Click to expand...
Click to collapse
Quick answers as I'm on the move (sorry for brevity) ...
- Moto drivers almost always work with HDX devices; install this package (don't have to launch it) which includes drivers; no warnings either
- Fastboot cables are largely ineffective on Amazon devices and rarely needed (special/unique cases beyond scope of this post)
- Encryption is NOT supported with custom ROMs on this device; dipping your head in boiling oil is a more enjoyable experience
- Prior debug setting in Lineage should have little/no impact on unbricking success
If you are unable to reload a ROM (Lineage in particular) you may have to do some further work on the data partition to remove encryption remnants. Post back if this is the case; I'll try to scare up the related material.
Davey126 said:
If you are unable to reload a ROM (Lineage in particular) you may have to do some further work on the data partition to remove encryption remnants. Post back if this is the case; I'll try to scare up the related material.
Click to expand...
Click to collapse
Thanks for your replies!
Thanks, my Thor is already up & running with the latest LineageOS and Open GApps. No problems so far. Prior to installing, In order to play it safe, I've made sure to wipe/format all partitions (including the data partition) from TWRP. Had a feeling that this would possibly be a good thing to do after that (partially?) failed encryption experience...
RiseT said:
Thanks, my Thor is already up & running with the latest LineageOS and Open GApps. No problems so far. Prior to installing, In order to play it safe, I've made sure to wipe/format all partitions (including the data partition) from TWRP. Had a feeling that this would possibly be a good thing to do after that (partially?) failed encryption experience...
Click to expand...
Click to collapse
Suspect encryption run was incomplete as simply the wiping data partition in TWRP is usually insufficient to remove critical remnants. A format is needed along with something else I don't immediately recall. You would be aware if that was needed as Lineage would hang on boot.
I can second this warning, do NOT USE ENCRYPTION. I tried so unter Lineage OS 14.1. As a result I had to wipe/format the data partition using TWRP, which let me escape from the bootloop.
Davey126 said:
Suspect encryption run was incomplete as simply the wiping data partition in TWRP is usually insufficient to remove critical remnants. A format is needed along with something else I don't immediately recall. You would be aware if that was needed as Lineage would hang on boot.
Click to expand...
Click to collapse
Can you give more details on how to remove these remnants? I did the same thing as OP this morning & now I'm here trying to undo my mistake :crying:
I still have TWRP 3.1.1-1 & I can flash stock 4.5.5 rom, but I can't flash any other custom roms as I'd get into a boot loop with grey kindle fire logo. I did wipe everything except sdcard, and the stock rom is running perfectly fine, except for root & gapps, of course.
Edit: SOLVED, courtesy to this post https://forum.xda-developers.com/showpost.php?p=74710623&postcount=1029
How to fix stuck on splash screen when TWRP 3.4.0-0 is installed permanently
I've tried several ways myself to get it up and running. As long as the device is encrypted, TWRP cannot start. It gets stuck in an infinite loop. The keymaster-3-0 service starts, but it is stopped immediately. It continues like this in a never ending loop. The only solution is to fully decrypt the device. At least this worked for me.
THE FOLLOWING STEPS WILL DELETE ALL YOUR DATA! IT IS NOT POSSIBLE TO CREATE A BACKUP OF YOUR ENCRYPTED DATA IN TWRP AND RESTORE IT ON A DECRYPTED PARTITION! USE TITANIUM BACKUP OR SIMILAR SOLUTIONS! YOUR DEVICE WILL BE RESET TO FACTORY SETTINGS!!
>>> *** UPDATED (see 5. ) *** <<<
Installation guide: (pay attention to keep this order!!)
1. Backup your data!!
2. Boot TWRP via fastboot:
Code:
fastboot boot twrp-3.4.0-0-evert.img
3. Format data to remove encryption. Wipe > Format Data > type 'yes' and swipe to confirm.
4. Flash the Disable_Dm-Verity_ForceEncrypt.zip
!!! 5. Disable HAB verification by flashing this .zip hab_disabler.zip !!! (*)
6. Flash the TWRP installer.zip
7. Install Magisk (optional)
8. Reboot to system and enjoy!
(*) HAB (High Assurance Boot) is a second verification process/service. It checks /system and /oem partition. The hab_disabler.zip will delete/patch the related files. (for further information see "update-binary")
During first boot...
...your device will reboot once. Don't panic, that's quite normal!
...animation after "Hello Moto" will take 2-3 min.
*** tested on PPWS29.116-20-23
WoKoschekk said:
How to fix stuck on splash screen when TWRP 3.4.0-0 is installed permanently
I've tried several ways myself to get it up and running. As long as the device is encrypted, TWRP cannot start. It gets stuck in an infinite loop. The keymaster-3-0 service starts, but it is stopped immediately. It continues like this in a never ending loop. The only solution is to fully decrypt the device. At least this worked for me.
THE FOLLOWING STEPS WILL DELETE ALL YOUR DATA! IT IS NOT POSSIBLE TO CREATE A BACKUP OF YOUR ENCRYPTED DATA IN TWRP AND RESTORE IT ON A DECRYPTED PARTITION! USE TITANIUM BACKUP OR SIMILAR SOLUTIONS! YOUR DEVICE WILL BE RESET TO FACTORY SETTINGS!!
Installation guidepay attention to keep this order!!)
1. Backup your data!!
2. Boot TWRP via fastboot:
3. Format data to remove encryption. Wipe > Format Data > type 'yes' and swipe to confirm.
4. Flash the Disable_Dm-Verity_ForceEncrypt.zip
5. Flash the TWRP installer.zip
6. Install Magisk (optional)
7. Reboot to system and enjoy!
During first boot your device will reboot once. Don't panic, that's quite normal!
Edit: Tested on build PPWS29.116-20-23
Click to expand...
Click to collapse
I follow your process to install TWRP Recovery,
Install successfully working fine,
But when I restart the moto g6 plus
It's everytime stuck on moto boot logo and restart again then stuck on boot logo
After that I restore boot.img using TWRP then flash magisk Manager working fine when I restart the phone agian stuck on boot logo.
(TWRP working fine thanks for your method or work but afterthat I flash magisk Manager first time everything working fine properly but when restart the device every time stuck on moto boot logo, I have to do process again)
I want sell my phone , Mood Off.
Dk Gautam said:
I follow your process to install TWRP Recovery,
Install successfully working fine,
But when I restart the moto g6 plus
It's everytime stuck on moto boot logo and restart again then stuck on boot logo
After that I restore boot.img using TWRP then flash magisk Manager working fine when I restart the phone agian stuck on boot logo.
(TWRP working fine thanks for your method or work but afterthat I flash magisk Manager first time everything working fine properly but when restart the device every time stuck on moto boot logo, I have to do process again)
I want sell my phone , Mood Off.
Click to expand...
Click to collapse
I tried it on my own. First boot runs fine but the second one ends in a bootloop. I already know whats wrong. Give me a few hours to fix this.
Dk Gautam said:
I follow your process to install TWRP Recovery,
Install successfully working fine,
But when I restart the moto g6 plus
It's everytime stuck on moto boot logo and restart again then stuck on boot logo
After that I restore boot.img using TWRP then flash magisk Manager working fine when I restart the phone agian stuck on boot logo.
(TWRP working fine thanks for your method or work but afterthat I flash magisk Manager first time everything working fine properly but when restart the device every time stuck on moto boot logo, I have to do process again)
I want sell my phone , Mood Off.
Click to expand...
Click to collapse
The problem has been fixed!!
I rebooted several times from system to recovery and vice versa. Magisk and TWRP (installed permanently) work fine. No issues known yet.
Everything working fine, after flashed permanently TWRP,
Magisk Manager also work fine the main issue here
If we flash magisk Manager using TWRP
You can restart the device several time working fine.
If we open magisk Manager and enable magisk hide for apps , then restart the device stuck on boot logo..
If we flash magisk Manager and don't open magisk Manager it will be working fine no issue , if we open magisk Manager then close after we restart the device stuck on boot logo.
If you find any solution about this then good. Otherwise please don't spent valueable time on it,
This devices create more problems only
Moto G6 Plus
Thanks for work.
Dk Gautam said:
Everything working fine, after flashed permanently TWRP,
Magisk Manager also work fine the main issue here
If we flash magisk Manager using TWRP
You can restart the device several time working fine.
If we open magisk Manager and enable magisk hide for apps , then restart the device stuck on boot logo..
If we flash magisk Manager and don't open magisk Manager it will be working fine no issue , if we open magisk Manager then close after we restart the device stuck on boot logo.
If you find any solution about this then good. Otherwise please don't spent valueable time on it,
This devices create more problems only
Moto G6 Plus
Thanks for work.
Click to expand...
Click to collapse
It works fine fir me. I enabled Magisk Hide to hide some apps but my device doesn't loop after that.
Did you use the updated method?
- Magisk was repacked with new name
- Magisk Hide enabled
- modules installed
- rebooted to recovery and then to system => no looping
- rebooted the device normally => no looping
At this moment I'm using my G6+
Dk Gautam said:
Everything working fine, after flashed permanently TWRP,
Magisk Manager also work fine the main issue here
If we flash magisk Manager using TWRP
You can restart the device several time working fine.
If we open magisk Manager and enable magisk hide for apps , then restart the device stuck on boot logo..
If we flash magisk Manager and don't open magisk Manager it will be working fine no issue , if we open magisk Manager then close after we restart the device stuck on boot logo.
If you find any solution about this then good. Otherwise please don't spent valueable time on it,
This devices create more problems only
Moto G6 Plus
Thanks for work.
Click to expand...
Click to collapse
I don't know why you are having this problem...
Flashed the Stock ROM, followed my guide and enabled Magisk Hide.
But no issues with that.
WoKoschekk said:
I don't know why you are having this problem...
Flashed the Stock ROM, followed my guide and enabled Magisk Hide.
But no issues with that.
Click to expand...
Click to collapse
The Problem has been fix,
I skip the 5th process, HAB disabler,
I flashed stock rom latest build security patch, PPWS29.116.16.24.
1. Format data using TWRP with Temporary boot.
2. Flash DM Verity Disable.
3. Flash HAB Disabler
4. Flash TWRP 3.4.0.0.zip
5. Re-start tha device.
6. Install magisk manager using TWRP.
7. Everything is working Fine.
8. I have a one question...
Lineage os 17.1 latest build for evert
Can support VoLTE ?????
I flashed Lineage os 17.1 on my moto g6 Plus
Everything is awesome but VoLTE not Show
Then I removed Lineage OS.
Dk Gautam said:
The Problem has been fix,
I skip the 5th process, HAB disabler,
I flashed stock rom latest build security patch, PPWS29.116.16.24.
1. Format data using TWRP with Temporary boot.
2. Flash DM Verity Disable.
3. Flash HAB Disabler
4. Flash TWRP 3.4.0.0.zip
5. Re-start tha device.
6. Install magisk manager using TWRP.
7. Everything is working Fine.
8. I have a one question...
Lineage os 17.1 latest build for evert
Can support VoLTE ?????
I flashed Lineage os 17.1 on my moto g6 Plus
Everything is awesome but VoLTE not Show
Then I removed Lineage OS.
Click to expand...
Click to collapse
Great!! Thanks for your reply!
I'm using neither Lineage nor VoLTE so I don't know if it's supported.
hello OP
hello.
it stuck on downloading 'boot.img'
does anyone have some tip so i can flash twrp?
thanks in advance for your comments.
d_g_m_2000 said:
hello.
it stuck on downloading 'boot.img'
does anyone have some tip so i can flash twrp?
thanks in advance for your comments.
Click to expand...
Click to collapse
Are you trying to boot TWRP?
WoKoschekk said:
Are you trying to boot TWRP?
Click to expand...
Click to collapse
thanks for your help.
yes, the command that i use is
fastboot boot twrp.img
i tried with another usb cable, another usb port.... even when i try "fastboot oem device-info" it does not show results yet "fastboot devices" it works.
i try another platform tools, even installed qualcom drivers.. but still it wont boot up to twrp 3.4-0-0
sometimes even it say command failed unknown
i cant even flash stock firmware... it just say fail to all commands
blankflash bat does not work also, it stuck on <waiting device>
i try on usb 3.0 and 2.0 and still the same results.
my device is xt1296-6
ok, ia my pc, i try in another and it boot up... i got ryzen 5 2600 just if anyone else find out what da f*ck is going on... thanks in advance for your comments.
d_g_m_2000 said:
thanks for your help.
yes, the command that i use is
fastboot boot twrp.img
i tried with another usb cable, another usb port.... even when i try "fastboot oem device-info" it does not show results yet "fastboot devices" it works.
i try another platform tools, even installed qualcom drivers.. but still it wont boot up to twrp 3.4-0-0
sometimes even it say command failed unknown
i cant even flash stock firmware... it just say fail to all commands
blankflash bat does not work also, it stuck on <waiting device>
i try on usb 3.0 and 2.0 and still the same results.
my device is xt1296-6
Click to expand...
Click to collapse
Have a look at this thread, especially post #4.
https://forum.xda-developers.com/g7-play/help/unlock-bootloader-t4164019
WoKoschekk said:
Have a look at this thread, especially post #4.
https://forum.xda-developers.com/g7-play/help/unlock-bootloader-t4164019
Click to expand...
Click to collapse
sorry for spamming your thread, i just want to make clear that my pc is the culprit of my problems.
i try this tutorial in other pc and it got it nice and esay.
i use it to flash lineage 17 official, that i'm now surprised that it replace twrp with their own recovery :/
anyway.. thank in advance for all your help and... people, this tutorial works great!!
d_g_m_2000 said:
sorry for spamming your thread, i just want to make clear that my pc is the culprit of my problems.
i try this tutorial in other pc and it got it nice and esay.
i use it to flash lineage 17 official, that i'm now surprised that it replace twrp with their own recovery :/
anyway.. thank in advance for all your help and... people, this tutorial works great!!
Click to expand...
Click to collapse
Since recovery is inside the boot partition Lineage implements a own recovery for their boot.img
Glad to hear that! Thanks a lot!!
WoKoschekk said:
Since recovery is inside the boot partition Lineage implements a own recovery for their boot.img
Glad to hear that! Thanks a lot!!
Click to expand...
Click to collapse
hi OP.
now i'm on pixel experience and they also remove twrp and install their own recovery... is this new normal? or i'm doing something wrong installing twrp.
thanks in advance for your comments.
d_g_m_2000 said:
hi OP.
now i'm on pixel experience and they also remove twrp and install their own recovery... is this new normal? or i'm doing something wrong installing twrp.
thanks in advance for your comments.
Click to expand...
Click to collapse
Yes, it's normal. I don't know why they do that... The only useful function there is ADB and that's all.
But you can replace them with TWRP, that's absolutely no problem. Reboot into bootloader and boot your twrp.img to install it.
WoKoschekk said:
Yes, it's normal. I don't know why they do that... The only useful function there is ADB and that's all.
But you can replace them with TWRP, that's absolutely no problem. Reboot into bootloader and boot your twrp.img to install it.
Click to expand...
Click to collapse
that's is a real bummer... thank you for your comments!
Hi i install pixel experence rom and im having a problem i canflash anything from my device, storage dont shows corrrct size and, shows binders with aleaty names with nothing inside, and i can't transfer with USB
Hey guys found our first custom ROM, it's not official but I've been using it for about a week now and the performance is excellent.
There is not many bugs that I've noticed and build is very stable. One big I've noticed is that when kernel is on performance, the screen does not go off automatically.
I've used Kernel Tasker to avoid this issue by turning on performance for certain apps and games, while keeping the system at Interactive for most tasks.
At the bottom is the link for instructions, the OS and gapps. There is a thread in this forum for passing safety net which I recommend. It solved all issues for me since magisk is failing safety net while other safety apps are passing. All the best rooting enjoy the ROM.
Redmi 9C (angelica) First Custom ROM! (Lineage OS 17 Android 10 )
This blog has move and will not be update again.For new update please open ▶▶
langithitam.wordpress.com
I have tried before you but can't flash it in recovery
After that my phone didn't boot more into system
So I flashed my phone and make workable you should remove this thread
MHaseebpk said:
I have tried before you but can't flash it in recovery
After that my phone didn't boot more into system
So I flashed my phone and make workable you should remove this thread
Click to expand...
Click to collapse
I am still using this ROM daily with no problems, before you flash make sure you remove Mi Account. If you do not remove account, phone will bootloop with any ROM you flash.
Pitch black recovery keeps restarting every time when I tried to flash this custom
I don't know what is wrong
Tried so much but in vein
Finally I flashed my phone and makes it workable
MHaseebpk said:
Pitch black recovery keeps restarting every time when I tried to flash this custom
I don't know what is wrong
Tried so much but in vein
Finally I flashed my phone and makes it workable
Click to expand...
Click to collapse
Defintely something wrong. I *did*remove my Mi Account, but to no avail, the phone keeps returning to Pich Black Recovery. I would say: not at all recommended to use this ROM. I am quite experienced in rooting phones, but this one fails in any respect. Do not use this ROM!
JoostA said:
Defintely something wrong. I *did*remove my Mi Account, but to no avail, the phone keeps returning to Pich Black Recovery. I would say: not at all recommended to use this ROM. I am quite experienced in rooting phones, but this one fails in any respect. Do not use this ROM!
Click to expand...
Click to collapse
I don't know what u guys are doing wrong but I'm still using this ROM till today, haven't found anything else but haven't really looked either.
Follow the instructions on the website to the T, wipe when it tells u to wipe and flash everything in order.
The model 9C I'm using is the global variant and it's not NFC. So perhaps you guys are using different variant but I doubt that could be the problem.
I believe somewhere u guys skipped or improvised a step because from my experience with rooting, 1 little detail skipped or over looked or something that might seem harmless can brick a phone.
I have been rooting since 2015 and my 1st phone was hauwei mate 7. Nearly hard bricked the phone and I had to pay to unlock bootloader using DC Unlocker. I rooted using a 3rd party rooting app, can't remember the name but it almost cost me the phone.
But this ROM works for me but it's a gsi ROM, it's not actually a custom ROM. There are other gsi ROMs out there that u could try. Download treble info for more info on which gsi is compatible.
Dawood99 said:
I don't know what u guys are doing wrong but I'm still using this ROM till today, haven't found anything else but haven't really looked either.
Follow the instructions on the website to the T, wipe when it tells u to wipe and flash everything in order.
The model 9C I'm using is the global variant and it's not NFC. So perhaps you guys are using different variant but I doubt that could be the problem.
I believe somewhere u guys skipped or improvised a step because from my experience with rooting, 1 little detail skipped or over looked or something that might seem harmless can brick a phone.
I have been rooting since 2015 and my 1st phone was hauwei mate 7. Nearly hard bricked the phone and I had to pay to unlock bootloader using DC Unlocker. I rooted using a 3rd party rooting app, can't remember the name but it almost cost me the phone.
But this ROM works for me but it's a gsi ROM, it's not actually a custom ROM. There are other gsi ROMs out there that u could try. Download treble info for more info on which gsi is compatible.
Click to expand...
Click to collapse
I remember now, King Root that was the culprit app I used with that hauwei mate 7. 1st and last time I ever rooted with 3rd party app. I was so proud of myself when I saved that phone lol still am.
Booting into Lineage ROM. Perhaps others will have difficulty but if u follow instructions carefully and phone has been rooted properly, it will work.
I recommend the guide for rooting by 0purple. How to root and pass safetynet.
Also very important remove Mi account and reboot phone to insure that phone won't lock similar to Google account lock. So remove all accounts and back up data. As the instructions indicate you will be wiping phone as OS requires a clean install.
i flash this customer rom to remove mi account after done camera not work! and after format user data now stuck at recovery i reflash it with stock rom and custom rom but always stuck at logo ! any solution pleas?
Got the same thing - kept on going to Pitch Black. Tried this - worked better https://androidfilehost.com/?fid=2188818919693787699
JaxxFrost said:
Got the same thing - kept on going to Pitch Black. Tried this - worked better https://androidfilehost.com/?fid=2188818919693787699
Click to expand...
Click to collapse
Is there no bugs in this rom
How did you flashed while pbrp keeps restarting?
MHaseebpk said:
Is there no bugs in this rom
How did you flashed while pbrp keeps restarting?
Click to expand...
Click to collapse
I think the ROM originally posted might have a problem. Try follow my link and use 'snooks4tech's' rom. There is also a different recovery and vbmeta in this download that I flashed in fastboot. The rest of the process I more or less followed as per dawood99's video, eg the step to wipe those 3 things in Pitchblack, copy this rom over, and install it along with Gapps and Magisk with Pitchblack. I don't see Magisk in my phone now though. I'm not very experienced with custom roms BTW so not too sure if I had the right Magisk file. Snooks4tech's download has got instructions as well and does not mention Magisk. Thanks to Dawood99 for the video, even if I had problems with the rom it gave me a good overview of the steps and I learned a lot.
PS maybe I didn't answer your question. I had to download the Mi flasher, somehow I got it back into Fastboot, I think by holding power and down volume, then flashed it back to stock Xiaomi. Then I started the custom rom flashing process again. I think I flashed Pitchblack again, and Snooks4tech's vbmeta and recovery. It then booted into Pitchblack properly again, and I could do the rest.
So far this rom is working reasonably well for me, Google play store doesn't work but I side-install APK's by downloading from browser. F-droid app is also intermittently not giving me any apps when I search.
Again I'm not expert at all this so take what I say with a pinch of salt, I could be talking rubbish here and there.
Both ROMs and Install Instructions cause in a boot into PBRP recovery (tried with v3.0+3.1) and MIUI also doesn't boot :-(
My steps:
- In PBRP recovery
-> adb reboot bootloader
In Bootloader
-> fastboot flash vbmeta vbmeta9c.img
Then I reboot phone with 3 different trys
-> 1. fastboot reboot
-> 2. Power On + Vol Up
-> 4. Power On + Vol Down
--> With all trys phone reboots into PBRP recovery
Push ZIP Files via MTP isn't possible, so:
-> adb push [LineageROM].zip /
-> adb push [GApps].zip /
Then in PBRP I go to "Install"
-> [LineageROM].zip with "Patch AVB2.0 Verity"
-> [GApps].zip also with "Patch AVB2.0 Verity"
Then I reboot to system from PBRP
But then PitchBlack reboots into recovery
Upgrade and downgrade of PBRP from 3.0 to 3.1 and back to 3.0 works without any problems.
Please help me, many thanks in advance!
/edit: Flashed original MIUI and reinstalled PBRP, then tried to install Lineage again, but boots only in recovery after flashing booth ROMs.
JaxxFrost said:
I think the ROM originally posted might have a problem. Try follow my link and use 'snooks4tech's' rom. There is also a different recovery and vbmeta in this download that I flashed in fastboot. The rest of the process I more or less followed as per dawood99's video, eg the step to wipe those 3 things in Pitchblack, copy this rom over, and install it along with Gapps and Magisk with Pitchblack. I don't see Magisk in my phone now though. I'm not very experienced with custom roms BTW so not too sure if I had the right Magisk file. Snooks4tech's download has got instructions as well and does not mention Magisk. Thanks to Dawood99 for the video, even if I had problems with the rom it gave me a good overview of the steps and I learned a lot.
PS maybe I didn't answer your question. I had to download the Mi flasher, somehow I got it back into Fastboot, I think by holding power and down volume, then flashed it back to stock Xiaomi. Then I started the custom rom flashing process again. I think I flashed Pitchblack again, and Snooks4tech's vbmeta and recovery. It then booted into Pitchblack properly again, and I could do the rest.
So far this rom is working reasonably well for me, Google play store doesn't work but I side-install APK's by downloading from browser. F-droid app is also intermittently not giving me any apps when I search.
Again I'm not expert at all this so take what I say with a pinch of salt, I could be talking rubbish here and there.
Click to expand...
Click to collapse
Thanks dude but I'm not responsible for making that video or am I responsible for the website or the files posted on it. I merely stumbled upon the ROM and I should not be credited for it. The creator is credited on the Website I believe and all credit should go to him.
Diotrihhi said:
Both ROMs and Install Instructions cause in a boot into PBRP recovery (tried with v3.0+3.1) and MIUI also doesn't boot :-(
My steps:
- In PBRP recovery
-> adb reboot bootloader
In Bootloader
-> fastboot flash vbmeta vbmeta9c.img
Then I reboot phone with 3 different trys
-> 1. fastboot reboot
-> 2. Power On + Vol Up
-> 4. Power On + Vol Down
--> With all trys phone reboots into PBRP recovery
Push ZIP Files via MTP isn't possible, so:
-> adb push [LineageROM].zip /
-> adb push [GApps].zip /
Then in PBRP I go to "Install"
-> [LineageROM].zip with "Patch AVB2.0 Verity"
-> [GApps].zip also with "Patch AVB2.0 Verity"
Then I reboot to system from PBRP
But then PitchBlack reboots into recovery
Upgrade and downgrade of PBRP from 3.0 to 3.1 and back to 3.0 works without any problems.
Please help me, many thanks in advance!
/edit: Flashed original MIUI and reinstalled PBRP, then tried to install Lineage again, but boots only in recovery after flashing booth ROMs.
Click to expand...
Click to collapse
Same problem
JaxxFrost said:
Got the same thing - kept on going to Pitch Black. Tried this - worked better https://androidfilehost.com/?fid=2188818919693787699
Click to expand...
Click to collapse
Tried this too but same problem
What about fm radio? does this rom include it? ty
haw fix the camera wont work ???
Dawood99 said:
Hey guys found our first custom ROM, it's not official but I've been using it for about a week now and the performance is excellent.
There is not many bugs that I've noticed and build is very stable. One big I've noticed is that when kernel is on performance, the screen does not go off automatically.
I've used Kernel Tasker to avoid this issue by turning on performance for certain apps and games, while keeping the system at Interactive for most tasks.
At the bottom is the link for instructions, the OS and gapps. There is a thread in this forum for passing safety net which I recommend. It solved all issues for me since magisk is failing safety net while other safety apps are passing. All the best rooting enjoy the ROM.
Redmi 9C (angelica) First Custom ROM! (Lineage OS 17 Android 10 )
This blog has move and will not be update again.For new update please open ▶▶
langithitam.wordpress.com
Click to expand...
Click to collapse
the speaker in calls is heard very quietly and the battery runs out very quickly
hi can anyonehelp me my side load is corrupted mtp does not work and my fastboot also does not work after trying to install this i dont know how to fix this and the rom does not work it auto boot to pitch black recovery