MIUI for Sony Xperia Z3 Compact (unlocked bootloaders)
miui v8 (31.12.2016) based on lpws521 ROM for Z3, great thanks to lpws521
Download
md5: 7DEE4978EDABB48ACBA265E5A7A74286
Features:
- Based on D5803_23.5.A.1.291
- Aroma installer
- Cut Chinese apps etc. (choose in aroma)
- Root
- Busybox
- Support init.d
- Apps signature disabled
- Patched hosts
- Gapps
etc.
Flash only via newest twrp
Known bugs:
First settings only in English language
Xposed don't work
I want to install this firmware. I have TWRP 3.0.2.0. How Can I update TWRP without unlock bootloader? I can't install this rom with my recovery (I become message: "cant write system to system partition" - or something similar (can not remember now exactly).
Is polish language on this rom?
EDIT:
I installed this rom without errors, but I have only black screen (no sony logo etc). Phone only wibrates when I turn power button. I can only flash stock rom with flashtool, nothing else.
and xposet? Do you have a black wallpaper bug? thanks
No, I have black screen, and phone won't turn on (phone is off). When I press power buton, phone short wibrates and nothing more. I can't go to recovery, or boot up. I can only flash rom with flashtool. When I flash rom with flashtool, I can made root, and recovery, and then flash any other rom, but when I flash Miui v8, I have this problem. Before I flash this rom I have MM (.291) rom, I try flash when I have kitkat rom-the same result. I have locked bootloader.
Sorry for my bad english.
Hi folx i tried it yesterday also and encountered the same bug - I came from AOSP and thought i have to flash stock first - but as i read your reports it is related to another reason..... Have you guys installed xposed in a first step ? Maybe this is the problem ....
Or is it related to another part of the aroma election ?
@greatslon : Which combination do you use ? language ? extra installations ? so maybe we can identify what doesn't work... But not to forget
A BIG THX for your work
Cheers
Rhonin
I tried much combinations in aroma, the same result.
Wysłane z mojego D5803 przy użyciu Tapatalka
jqtz3k said:
No, I have black screen, and phone won't turn on (phone is off). When I press power buton, phone short wibrates and nothing more. I can't go to recovery, or boot up. I can only flash rom with flashtool. When I flash rom with flashtool, I can made root, and recovery, and then flash any other rom, but when I flash Miui v8, I have this problem. Before I flash this rom I have MM (.291) rom, I try flash when I have kitkat rom-the same result. I have locked bootloader.
Sorry for my bad english.
Click to expand...
Click to collapse
The same happened to me when I flashed the advanced stock kernel (https://www.mediafire.com/?bmhccw2x4papa4m) over another MIUI8 ROM... so maybe it's kernel related (for locked bootlader)...
When you flash original stock kernel (using flashtool), the ROM boots up normally...
jqtz3k said:
How Can I update TWRP without unlock bootloader?
Click to expand...
Click to collapse
Try to flash this archive via current twrp View attachment twrp_Z3c_greatslon.zip
Rhonin86 said:
Which combination do you use ? language ? extra installations ? so maybe we can identify what doesn't work... But not to forget
Click to expand...
Click to collapse
I have no devices to test, but users in 4pda forum successfully tested rom.
Great work man! Hope you maintain this work
Is xposed working? Oh sorry you already write it
Could someone who succeeded in installing this ROM could describe from which ROM he is coming, which TWRP he is using, additionaly it would be interesting to know what he selected on aroma....
THX in advance
Rhonin
If i find the time after the we i have to read in the russian forum and try to understand ruski yasik
Cheers
I have try to install your TWRP, then MIUI - no result.
I made TA partition backup, then unlocked bootloader, install newest TWRP 3.0.2-1, then install MIUI - phone boot, but show only sony logo and nothing more. I have no idea how to install this rom. I try to install other kernel - no result.
EDIT:
I succesfully install this rom.
I install stock prerooted rom MM 291 (region CE1).
I boot phone with this rom.
I turn phone off, then boot to recovery ( TWRP 3.0.2-0).
I flash recovery from post #9, then reboot.
I install MIUI8, wipe dalvik&cache, then I install recovery from post #9 second time, then I wipe dalvik&cache, and reboot.
Everything is OK, but I don't know how to add google account. When I press icon Google Play - nothing happens.
jqtz3k said:
Everything is OK, but I don't know how to add google account. When I press icon Google Play - nothing happens.
Click to expand...
Click to collapse
You must launch "Google Installer" preinstalled app and press main button. If app freezes in last step, reboot phone and use Google apps normally.
There is the bug when you select a theme and you get a black wallpaper?
mine has bricked after installing rom too, i will try as described above..
Sent from my D5803 using Tapatalk
How Can I change chinese words to english on some apps (like internet browser, theme changer)? I have Xiaiomi account FC - any solution? This is china ROM? Can you made (or change to) global version?
any alternative installing method for locked bootloader? any suggestion?
Sent from my D5803 using Tapatalk
I found next bug. I have error in gallery.apk. When I watch any movie, and I press editor video, I see video editor for one second, and then I have "Unknown error" and nothing hapens.
Related
Thanks to blueether for His very useful thread
! ATTENTION !
There is a SIMPLE SOLUTION HERE
The C6833 modem works for my C6802 [TESTED]
Thanks to Triflot
Requirements:
*. DO IT AT YOUR OWN RISK, I'M NOT RESPONSIBLE FOR ANYTHING THIS WILL DO TO YOUR PHONE
1. Xperia Z Ultra (Absolutely! ) [Tested on XZU with Unlocked Bootloader]
2. FlashTool, Download link & tutorial here
3. Required FTF (NUT's *.532 & *.136)
4. Custom ROM
5. PC running Windows OS
How to get into Flash Mode:
1. Power Off your Z Ultra
2. Press & hold Vol-
3. Plug your phone to your PC (USB driver > read for intallation step here)
How to get into FastBoot Mode:
1. Power Off your Z Ultra
2. Press & hold Vol+
3. Plug your phone to your PC (USB driver > read for intallation step here)
[TRICK] Get Into FastBoot Mode/Flash Mode
If you're having trouble getting into FastBoot Mode/Flash Mode, you can try this trick
1. You have to be on Windows
2. Make sure you opened FlashTool & installed driver for Z Ultra
3. Open Device Manager
4. Show hidden device [Not really necessary, I did this to make sure my Z Ultra driver is installed]
5. Plug your phone while holding Vol+ (FastBoot) OR Vol- (Flash)
6. If it doesn't recognized by Windows, then Scan for hardware changes (this simulate USB Unplug & Replug for me), do this while holding the Volume Rocker
7. Repeat number 6 until you got it connected
For Windows 8/8.1 Only:
When you connected Z Ultra using Flash Mode to your PC, it'll disconnect after a while, to solve this problem, try to prepare your files you want to flash first, then when FlashTool asked to connect your phone, do step 1 to 7, your phone won't disconnect at the time it being flashed
Fresh Install [RECOMMENDED]
Steps:
1. Flash NUT's Modified *.532 STOCK ROM Using FlashTool [Default Settings, Flash Everything]
2. Flash extracted boot.img file from CUSTOM ROM You Want To Install via FastBoot Using FlashTool
3. Boot Into CWM/TW Recovery
4. Flash CUSTOM ROM + GAPPS via Recovery
5. Flash Custom Kernel Here If You Want To Use It, If Not, Then Go To Step 6
6. Reboot Into System You Just Installed [IDK If This Is Necessary]
7. Reboot To Flash Mode
8. Flash ANY *.136 STOCK ROM Using FlashTool
Settings:
[Wipe] Data : Unchecked
[Exclude] Kernel : Checked
[Exclude] System : Checked
9. Reboot, Hopefully IMEI and BASEBAND Will Be Available
Thanks to x1123 for his post here
Update Custom ROM [EXPERIMENTAL]*Please Correct Me If I Wrong
Steps:
*. This Will Not Keep Your Google Account, So, Contacts, Mails, Hangouts Messages, etc. That Related To Google Account Will Disappear
1. Flash NUT's Modified *.532 STOCK ROM Using FlashTool
Settings:
[Wipe] AppsLog : Unchecked
[Wipe] Cache : Unchecked
[Wipe] Data : Unchecked
2. Flash extracted boot.img file from CUSTOM ROM You Want To Install via FastBoot Using FlashTool
3. Boot Into CWM/TW Recovery
4. Flash CUSTOM ROM + GAPPS via Recovery [GAPPS Must Be Installed, Otherwise Google Framework Will Crash]
5. Flash Custom Kernel Here If You Want To Use It, If Not, Then Go To Step 6
6. Reboot Into System You Just Installed [IDK If This Is Necessary]
7. Reboot To Flash Mode
8. Flash ANY *.136 STOCK ROM Using FlashTool
Settings:
[Wipe] AppsLog : Unchecked
[Wipe] Cache : Unchecked
[Wipe] Data : Unchecked
[Exclude] Kernel : Checked
[Exclude] System : Checked
9. Reboot, Hopefully IMEI and BASEBAND Will Be Available [Some Google Apps Will Disappear, You'll Need To Re-Install It]
Tested ROMs: copied from here
Carbon - Build 8: Working
SlimKat: Not tested yet
LiquidSmooth: Not tested yet
FXF CM11: Not tested yet
CM11: Working
AOSP: Not tested yet
AOKP: Not tested yet
AICP: Not tested yet
Lungo: Not tested yet
PAC-man: Not tested yet
PA: Working
Chameleon OS: Not tested yet
GPe ROM: Not tested yet
halo gan,
do we have to do all these step to flash a custom rom?
Thanks gan.
satriamau said:
halo gan,
do we have to do all these step to flash a custom rom?
Thanks gan.
Click to expand...
Click to collapse
You should't have to. Just get recovery and flash. There does seem to be an issue with the odd c6802.
If you do lose you IMEI just flashing a FTF will restore it
blueether said:
If you do lose you IMEI just flashing a FTF will restore it
Click to expand...
Click to collapse
Hi! I've installed CM11 on my phone (C6806) and have lost the IMEI. How do I flash a FTF? I'm new to all this, can you please give me a bit more info? Thanks!
blueether said:
You should't have to. Just get recovery and flash. There does seem to be an issue with the odd c6802.
If you do lose you IMEI just flashing a FTF will restore it
Click to expand...
Click to collapse
I lost my imei yesterday so i have to go through this process. And since i'm already in a custom rom, so i don't need to flash boot.img via fastboot right? Just flash everything via recovery?
And if i do lost imei again, i just need to restore the backup of my previos rom?
Coming from a nexus, this quite confusing :/
Azra4 said:
Hi! I've installed CM11 on my phone (C6806) and have lost the IMEI. How do I flash a FTF? I'm new to all this, can you please give me a bit more info? Thanks!
Click to expand...
Click to collapse
You flash it via Flashtool. The link for the thread is in the op.
satriamau said:
You flash it via Flashtool. The link for the thread is in the op.
Click to expand...
Click to collapse
Thank you. So I need to install Flashtool. That should be easy enough. But what FTF should I use? I have a C6806 (GPE). I'm looking at this page - http://forum.xda-developers.com/showthread.php?t=2453921. Should I use "STOCK ROM] [FTF] Xperia Z Ultra (C6806) 14.3.A.0.681 "Generic US""?
Azra4 said:
Thank you. So I need to install Flashtool. That should be easy enough. But what FTF should I use? I have a C6806 (GPE). I'm looking at this page - http://forum.xda-developers.com/showthread.php?t=2453921. Should I use "STOCK ROM] [FTF] Xperia Z Ultra (C6806) 14.3.A.0.681 "Generic US""?
Click to expand...
Click to collapse
I don't think you should flash ftf to a gpe z ultra. I've read somewhere it'll brick your device.
Dang! OK, so how do I get my IMEI back then?
Azra4 said:
Dang! OK, so how do I get my IMEI back then?
Click to expand...
Click to collapse
you flashed the normal togari CM11 not the togari_gpe version? is so just flash the _gpe version over top
satriamau said:
halo gan,
do we have to do all these step to flash a custom rom?
Thanks gan.
Click to expand...
Click to collapse
blueether said:
You should't have to. Just get recovery and flash. There does seem to be an issue with the odd c6802.
If you do lose you IMEI just flashing a FTF will restore it
Click to expand...
Click to collapse
It's like blueether said, this steps meant for ODD C6802, not every C6802 need this step
Azra4 said:
Dang! OK, so how do I get my IMEI back then?
Click to expand...
Click to collapse
give blueether solution a try, because i don't really have many experience with GPe edition of XZU
Does this guide assume you've unlocked bootloader or is that not necessary?
Only asking because it says from stock to custom rom and I read that as completely stock untouched.
Sent from my C6806 using XDA Free mobile app
Riza said:
It's like blueether said, this steps meant for ODD C6802, not every C6802 need this step
give blueether solution a try, because i don't really have many experience with GPe edition of XZU
Click to expand...
Click to collapse
so i flash CM m11 over carbon rom, and i got this imei and baseband lost again.
is that mean i have the odd one and i have to do these painful steps to flash a rom?
is there any way to flash a rom, gapps and full wipe just from the recovery without losing imei and baseband?
thanks
satriamau said:
so i flash CM m11 over carbon rom, and i got this imei and baseband lost again.
is that mean i have the odd one and i have to do these painful steps to flash a rom?
is there any way to flash a rom, gapps and full wipe just from the recovery without losing imei and baseband?
thanks
Click to expand...
Click to collapse
So Carbon worked fine with no IMEI issues?
blueether said:
So Carbon worked fine with no IMEI issues?
Click to expand...
Click to collapse
No since i follow these steps while flashing carbon. I flash cm without these steps. Wanted to try cm since carbon giving me random reboots sometime. I love the features btw.
Oot : is there anyway i can turn heads up off on carbon?
Thanks.
juggz143 said:
Does this guide assume you've unlocked bootloader or is that not necessary?
Only asking because it says from stock to custom rom and I read that as completely stock untouched.
Sent from my C6806 using XDA Free mobile app
Click to expand...
Click to collapse
i tried this AFTER i unlocked my bootloader, so idk about XZU with locked bootloader, but i think it's safer to unlock your bootloader first, it's to avoid soft brick of the device, many thread says u must unlock your bootloader before you install any custom ROM
satriamau said:
so i flash CM m11 over carbon rom, and i got this imei and baseband lost again.
is that mean i have the odd one and i have to do these painful steps to flash a rom?
is there any way to flash a rom, gapps and full wipe just from the recovery without losing imei and baseband?
thanks
Click to expand...
Click to collapse
i'm afraid idk the other way, if you want to change your rom, then you must follow the fresh install guide, but if ure upgrading [from CM 11 to later CM 11] then follow upgrade guide
I looked at this a bit tonight. There's a c6x02.sh script which is run at the end of flashing ROMs on togari and honami (Z Ultra and Z1), which copies some particular modem firmware files needed for certain device models (C6802 for togari, C6902 for honami) if it detects that the device is one of these. This script is included in CM11, PA, PAC and SlimKat, but not in others, like Carbon and LiquidSmooth (because TARGET_DEVICE is improperly set in rhine-common/releasetools.py). As @wtfhax says here, the problem may be something around this.
Can someone with the lost IMEI problem on an AOSP ROM try flashing the two attached zips and tell us if either one solves the problem? One is with the c6x02 modem files which some ROMs copy over, while the other is with the "normal" files. Extracted from the latest CM11 nightly. Remember to say which device model you use.
Flash the attached c6833-modem.zip file for a workaround.
Triflot said:
I looked at this a bit tonight. There's a c6x02.sh script which is run at the end of flashing ROMs on togari and honami (Z Ultra and Z1), which copies some particular modem firmware files needed for certain device models (C6802 for togari, C6902 for honami) if it detects that the device is one of these. This script is included in CM11, PA, PAC and SlimKat, but not in others, like Carbon and LiquidSmooth (because TARGET_DEVICE is improperly set in rhine-common/releasetools.py). As @wtfhax says here, the problem may be something around this.
Can someone with the lost IMEI problem on an AOSP ROM try flashing the two attached zips and tell us if either one solves the problem? One is with the c6x02 modem files which some ROMs copy over, while the other is with the "normal" files. Extracted from the latest CM11 nightly. Remember to say which device model you use.
Click to expand...
Click to collapse
That makes perfect scene, good on you mate
Triflot said:
I looked at this a bit tonight. There's a c6x02.sh script which is run at the end of flashing ROMs on togari and honami (Z Ultra and Z1), which copies some particular modem firmware files needed for certain device models (C6802 for togari, C6902 for honami) if it detects that the device is one of these. This script is included in CM11, PA, PAC and SlimKat, but not in others, like Carbon and LiquidSmooth (because TARGET_DEVICE is improperly set in rhine-common/releasetools.py). As @wtfhax says here, the problem may be something around this.
Can someone with the lost IMEI problem on an AOSP ROM try flashing the two attached zips and tell us if either one solves the problem? One is with the c6x02 modem files which some ROMs copy over, while the other is with the "normal" files. Extracted from the latest CM11 nightly. Remember to say which device model you use.
Click to expand...
Click to collapse
WOW, works like a charm...
Device: C6802
Modem Works: C6833 [idk why]
btw, i added your solution to the first post, is it okay for you?
just tell me if you don't want to, thanks
Riza said:
WOW, works like a charm...
Device: C6802
Modem Works: C6833 [idk why]
btw, i added your solution to the first post, is it okay for you?
just tell me if you don't want to, thanks
Click to expand...
Click to collapse
Thanks, that's great!
Did you try the c6x02 file, too? And it didn't work? I wonder why it's included, then - I guess we should ask CM on their issue tracker. In the meantime, you can just delete the c6x02.sh file from the root of any ROM zip you want to install, and it should use functional modem files. (Or use the above zip, but it may become obsolete in the future.)
Still, this doesn't tell the full story if for example Carbon users have had the IMEI problem, since it doesn't have the script. Have you had reports of that, @blueether? Maybe they were caused by not flashing on top of a compatible stock ROM?
There was one I think. I'm not sure what the cause was though
Device information:
Xperia Z Ultra
Cyanogenmod 11 M12 (togari from offical cm side)
Smartphone is encrypted
Bootloader unlocked
Nothing else changed (kernel etc.)
Hi,
since a few hours i try to get TWRP 2.8.5.0 to work.
After installing it according the offical description and rebooting into the recovery, my z ultra only shows the Sony logo and doesn´t do anything (it took me some time to figure out how to turn it off... Power + vol up).
To get the cm cwm back, i´ve used fastboot to flash boot.img.
The integrated cwm can´t mount the encrypted data partition and is useless for me. To avoid problems on my heavily used z ultra, i tried TWRP first on my old (encrypted) Nexus 7 (2012) tablet, works like a charm and most important, it doesn´t have any problems with encrypted devices.
The installation on the Nexus 7 was not really mentionable, fastboot flash recovery file.img, that´s it.
The Z Ultra is different, the teamwin page says :
Download the above file. Copy the file to /sdcard/fotakernel.img and run the following commands using terminal emulator or in adb shell:
su
dd if=/sdcard/fotakernel.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
It won´t work, the above mentioned problem is the result.
Maybe i need a custom kernel, any suggestions?
Thanks for your help.
CM kernel probably doesnt allow to flash other kernel than it has (cwm). Flash great devs kernel and than twrp. I have it (at least multi rom 2.8.4 one) and it works.
However after screen off it reboots and i dont know what cause it
Thanks for your answear, i try it next weekend.
Code:
Rom: Resurrection Remix® Lollipop v5.3.6 - Togari
Kernel: from rom
Recovery: Dunno where it came from? Perhaps when flashing Candy5 Beta.
Im kind off in the same position, recovery says
Code:
E: Cannot load volume /misc
Finding update package...
Opening update package...
Installing update package...
Package is for device: ...[B][I]bla bla bla you get the thing[/I][/B]
E: failed to install /sideload/package.zip
E: Please take note of ..[B][I]bla bla bla[/I][/B]
Installation aborted.
E: Cannot load volume /misc!
When trying to flash any zip file. When the flash starts I see something like "verification failed" flashing by really quick .....I guess the verify is active which is causing this issue?
BUT this damn recovery has no damn setting to change that! Probably possible to modify some config.txt manually.
Is it possible to change recovery somehow from CM recovery?
I tried by flashing great devs with fastboot. Then it says finished but the same recovery is still present...
Sorry for ranting a bit ..I'm in the middle of some other projects going on with BSD but this one is driving me nuts :silly: I just want to flash TWRP on my device It should not be this difficult
My advice for you is to flash boot.img from resurrection remix - its great devs kernel v2 with twrp - or zombie kernel for 5.0 which has built in twrp.
Both can be flashed using fastboot, so u dont need working recovery for it and they both should work with all 5.0 roms except gpe one.
Im not sure what versions of recovery they have built in, but after that u can flash multirom zip, which has 2.8.4.x one (with mutirom support ofc,but its just addition for "stock" functions it has). I dont think u can use official twrp 2.8.5.0 with nonstock kernel as i tried to flash it to recovery partition and fotakernel and always it doesnt boot (recovery, rom and kernel worked fine, just after pressing vol+, vol- or power when purple light comes up, it changes to yellow and stay like this till i forced reboot).
I tried it with Great Devs KK (v1 + AICP 7.0l) and LP (v2 + RR or AICP 8.0 unofficial build), built in kernel in AICP 8.0 unofficial and Validus.
MultiROM twrp works fine with GD v1 and v2
ch3mn3y said:
My advice for you is to flash boot.img from resurrection remix - its great devs kernel v2 with twrp - or zombie kernel for 5.0 which has built in twrp.
Both can be flashed using fastboot, so u dont need working recovery for it and they both should work with all 5.0 roms except gpe one.
Im not sure what versions of recovery they have built in, but after that u can flash multirom zip, which has 2.8.4.x one (with mutirom support ofc,but its just addition for "stock" functions it has). I dont think u can use official twrp 2.8.5.0 with nonstock kernel as i tried to flash it to recovery partition and fotakernel and always it doesnt boot (recovery, rom and kernel worked fine, just after pressing vol+, vol- or power when purple light comes up, it changes to yellow and stay like this till i forced reboot).
I tried it with Great Devs KK (v1 + AICP 7.0l) and LP (v2 + RR or AICP 8.0 unofficial build), built in kernel in AICP 8.0 unofficial and Validus.
MultiROM twrp works fine with GD v1 and v2
Click to expand...
Click to collapse
....well im stuck. I have tried everything. Even hotbooting. That damn CM recovery is there no matter what!
I'm gonna give it a try tomorrow and start on zero. Either flash a stock rom with flashtool or scrubber port which is not based on cm.
I'll report later with some results
Mybe try to:
- dl your rom and zombie or gd
- open ur roms zip with ie 7zip
- delete boot.img
- unpack kernels zip and move boot.img to roms zip
- copy new zip to device
- flash stock
- flash kernel (zombie or gd)
- using built in recovery (should be twrp( flash roms zip
As there will be built in kernel with twrp it should stay after reboot.
If not do it again but before reboot in the and flash multirom zip
Sent using C6833 - AICP/GreatDevs
Solved the issue.
First I Downloaded
STOCK ROM] [FTF] Xperia Z Ultra 6833 14.4.A.0.118 "SRF FR".
GoogleDrive: Download FTF
Thanks to @dandyqb
Click to expand...
Click to collapse
And Flashtool 9.18.5
But I got stuck with Flashtool prompting me to move content from C:\flashtool\firmwares C:\users\admin\.flashtool/firmwares (??)
Abandoned flashtool and downloaded Flashtool 9.16.1 instead. But this time I hit another issue.
Code:
Flashing system bla bla bla.
Abort..
Error..
Device connected in Flashmode.
Grrrrr..!!
Abandoned the FTF file and downloaded
STOCK ROM] [FTF] Xperia Z Ultra 6833 14.4.A.0.118 "VodaFone UK".
mediafire: Download FTF
Thanks to @Feodorus 4PDA
Click to expand...
Click to collapse
This time it worked out. Flashtool read the FTF and pushed it to the device as it should.
Booted device and transfered files to my device
Code:
cm-Resurrection_Remix_LP_v5.3.6-20150221-togari.zip
gapps-lp-20141109-signed.zip
MultiROM-v30x-180115-UNOFFICIAL-togari.zip
I did the rest manually. Downloaded and opened [email protected]_LRX21P.S3.4201_by_Scrubber.
Took out the file "For_ALL_ZU_5.0_Scrubb_GPE_kernel_initD.img"
Renamed file and flashed it with
Code:
Fastboot flash boot boot.img
Booted into recovery and flashed
Code:
cm-Resurrection_Remix_LP_v5.3.6-20150221-togari.zip
gapps-lp-20141109-signed.zip
MultiROM-v30x-180115-UNOFFICIAL-togari.zip
Turned off device. Booted into Fastboot mode
Renamed "TWRP_multirom-togari_20150201-00.img" to "recovery"
Flashed file with
Code:
Fastboot flash recovery recovery.img
Fastboot reboot
Wooh.. And I reached a very unfamiliar place named Multirom upon boot saying Auto-boot! :good::laugh:
Glad u made it. It strange that u need steps with gpe port, but maybe some devices are different
Multirom lets u boot more than one rom. Its like grub on pc, so its good thing, but take 5-6 secs of additional booting time
And flash older version of flashtool (eg. 0.9.18.2), if u want to keepfirmwares in flashtool/firmwares folder. Devs change somethin and people like me with small system partition or ssd drive, which has limited space will have problems if it keeps that way (or well need to stay with older verions)
Sent using C6833 - AICP/GreatDevs
ch3mn3y said:
Glad u made it. It strange that u need steps with gpe port, but maybe some devices are different
Multirom lets u boot more than one rom. Its like grub on pc, so its good thing, but take 5-6 secs of additional booting time
And flash older version of flashtool (eg. 0.9.18.2), if u want to keepfirmwares in flashtool/firmwares folder. Devs change somethin and people like me with small system partition or ssd drive, which has limited space will have problems if it keeps that way (or well need to stay with older verions)
Sent using C6833 - AICP/GreatDevs
Click to expand...
Click to collapse
I didn't really need scrubbers kernel. I just used it to flash a recovery on to my device as I came from stock rom after flashing the FTF.
Just kind of a "safety first" step instead of jumping right onto flashing the multirom .img file and not knowing if its gonna boot or not. :silly:
Scrubbers gpe port was just the first rom that popped up in my head so its why I used it.
You can use Rashr to replace recovery in current kernel image on the go. I use it all the time to get TWRP - works perfectly. Can backup kernel image before modifying.
You can flash Philz, TWRP (any version, incl. 2.8.5.0) or any other recovery image from sdcard with it on top of AOSP kernel.
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
What kernel are u using? Im on GreatDevs and after flashing 2.8.5.0 it doesnt boot. I mean its flashed, but after reboot when i press vol+/- like i do with twrp 2.8.4 (multirom one)or before did with cwm it freezes on kernel logo (led color changes from purple to yellow)
Sent using C6833 - AICP/GreatDevs
ch3mn3y said:
What kernel are u using?
Click to expand...
Click to collapse
If this question is for me, I use official CM12.
Its in my forum and tapatalk signatures - Great Devs, KK one.
So maybe its it and cm11 kernel (or only GD) doesnt support 2.8.5+ ??
I can live with 2.8.4 for now (till I move to LP)
B.Maximenko said:
You can use Rashr to replace recovery in current kernel image on the go. I use it all the time to get TWRP - works perfectly. Can backup kernel image before modifying.
You can flash Philz, TWRP (any version, incl. 2.8.5.0) or any other recovery image from sdcard with it on top of AOSP kernel.
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
Click to expand...
Click to collapse
I have tried this app. And other similar apps I could find on play store. They did not work.
The output in this app showed that it successfully replaced recovery but on reboot CM recovery was still present.
B.Maximenko said:
You can use Rashr to replace recovery in current kernel image on the go. I use it all the time to get TWRP - works perfectly. Can backup kernel image before modifying.
You can flash Philz, TWRP (any version, incl. 2.8.5.0) or any other recovery image from sdcard with it on top of AOSP kernel.
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
Click to expand...
Click to collapse
the app doesn't work for me either (i'm running slimkat build 9 stock)
i can't get 2.8.5.0 working permanently (at least not after a power down)... it'll work right after a fastboot flash
lame Sony putting kernel and recovery together.... wth... my Note 2 was so much simpler to work with...
anyone got a TWRP theme which is suitable with xperia ultra z?
Hey guys,
I'll start by saying that i know i messed up realy bad and it is my fault, but i'm trying to revert this to no avail..i wouldn't make this post if haven't tried every possible solution i found.
So let's start,
I have a honor 7 PLK-L01 as the tittle says, i recently unlocked and rooted my phone, but i didn't make any backup (i know :/) because TWRP was in chinese..
After that i got into a bootloop, and i tried installing stock roms i got from here and other places, i tried every possible solution for 2 days now..
The only ROM i could get working was "PLK-UL-TL-CL_EMUI3.1_Android5.1_5.12.16" (can change language to english tho but some menus are still in chinese.),
wich is chinese and says my ip isnt supported when i try to log in to honor and comes with tons of chinese bloatware.
It only worked flashing with adb, flashing through dload (error when i tried to update) and TWRP (always get the error "No md5 file found") didnt work..
I've tried these full version ROMs and always end up in a boot loop:
PLK-L01C432B100
PLK-L01C432B121
PLK-L01C432B130
I used this guide to install de ROMs: http://forum.xda-developers.com/hono...e-fix-t3255452
I've tried using adb manual and using multitool, getting the same resuslts..(always using latest versions)
I dont understand how that a chinese rom could work tho, as it says on the info that it's the version PLK-C00B618 and my phone is PLK-L01(at least i think it is...the box where it came says it is the L01...), must be a custom ROM of some sorts?
So i was wondering if i could get some help on what i am doing wrong.
I just want to get back to stock with auto updates like i was before, and only mess with this when there's stable custom ROMs available..and always doing backup ofcourse (silly me..)!
Hope i you guys can help me with my problem, thanks a lot!
~Carnach
Hi,
Maybe i can help you in a few things. So first thing, you should try to download the official rom from here: www hihonor.com/global/support/search-result/?keywords=honor%207 and try to install from an SD card. Your TWRP is chinese but the location of the buttons is the same than the english version, so you can figure, what option is need for you. (google can help you, check the pics from the TWRP menu). And if you already installed this ROM, you can change the TWRP for an english version. (i found the good link in this article: www cyberkey.in/root-honor-7-install-twrp-recovery-100-working/
P.s.: I am sorry about the broken links, but i am a new user, so i can not use outside links yet.
Morelight said:
Hi,
Maybe i can help you in a few things. So first thing, you should try to download the official rom from here: www hihonor.com/global/support/search-result/?keywords=honor%207 and try to install from an SD card. Your TWRP is chinese but the location of the buttons is the same than the english version, so you can figure, what option is need for you. (google can help you, check the pics from the TWRP menu). And if you already installed this ROM, you can change the TWRP for an english version. (i found the good link in this article: www cyberkey.in/root-honor-7-install-twrp-recovery-100-working/
P.s.: I am sorry about the broken links, but i am a new user, so i can not use outside links yet.
Click to expand...
Click to collapse
I got TWRP in english after that using the multitool.
I've already tried that official rom you mentioned. When i try to install from TWRP, i get an error on instalation: "Skipping MD5 file check: no MD5 file found", from what i understand twrp can only be used to flash custom ROMs right?
If i use the only ROM that worked (PLK-UL-TL-CL_EMUI3.1_Android5.1_5.12.16), to try to manual update, gives an error that i have the wrong version for that update (makes sense since the version that shows on phone info is PLK-C00B618), so this must be a custom rom or a beta release?
The only way i can install a ROM is through odb, wich ends up in a bootloop whenever i try any stock ROM, even tried the 6.0 beta that froze my screen at honor logo instead of looping..
I install with odb using
fastboot flash boot BOOT.img
fastboot flash system SYSTEM.img
fastboot flash recovery RECOVERY.img
fastboot flash cache CACHE.img
fastboot flash cust CUST.img
Or multitool unbrick tool (flashboots BOOT, SYSTEM, RECOVERY and CUST).
Maybe it has something to do with root? version maybe? i've tried without SU, with TWRP version, with lastest stable version 2.65..and just can't get it working :/
The thing that is confusing me the most, is why that 5.1.1 version works and all others don't, im doing the exact same thing for all of them..
Just want to get back to stock..
Try installing full b121 through fastboot commands. Phone should bootloop, but that's fine for now. Then flash b170 boot and recovery, and your phone should start normally.
You can find the files here:
http://forum.xda-developers.com/showthread.php?t=3290348
Update from sdcard with buttons combination or local update won't work until You have TWRP. You need stock recovery for that.
Oh and You have to flash roms for Your device. If You have the PLK-L01 then roms for any other variants might not work and get You in situations like the one You're struggling right now.
Tapnięte za pomocą Honoraty Siódmej
Toldo said:
Try installing full b121 through fastboot commands. Phone should bootloop, but that's fine for now. Then flash b170 boot and recovery, and your phone should start normally.
You can find the files here:
http://forum.xda-developers.com/showthread.php?t=3290348
Update from sdcard with buttons combination or local update won't work until You have TWRP. You need stock recovery for that.
Oh and You have to flash roms for Your device. If You have the PLK-L01 then roms for any other variants might not work and get You in situations like the one You're struggling right now.
Tapnięte za pomocą Honoraty Siódmej
Click to expand...
Click to collapse
Did exactly like you said and it worked like a charm, after instaling boot and recovery from b170 it booted and then i updated with full b121 from sd card.
Everything is working perfectly now. Can't thank you enough!
I'd never find that out by myself...i was just trying to flash full roms :/
Thanks a lot!
Best regards,
Carnach.
It happened to me also and I ran into this solution somewhere around xda. Glad I could help.
Tapnięte za pomocą Honoraty Siódmej
Long story - Tried to apply the latest Marshmallow rooted package for D6503 on my 6502 that was already rooted with XZ dual recovery. It installed successfully, was rooted too...but I forgot to add the patch that would fix the radio not working. So I try to reboot to recovery...and that doesn't work anymore. I tried installing TWRP recovery from the manager app, but it wouldn't reboot. Then I ran the XZ recovery installer externally, and now my phone is ****ed. Stuck at an infinite boot loop.
At this stage the only thing I can access is flashtool and fastboot, and since my bootloader is locked I can't flash a recovery that way (nor do I want to permanently lose DRM keys/camera quality as I've heard happens with unlocking the bootloader). I have a memory card and I used the option to disable loading the recovery specified on the XZ thread by adding a 'donotload' file on the sd card.
Still no use - I get a Sony logo for about 5 seconds, the screen goes dark and back to the same. At this point probably my recovery is screwed up or non existent and a bad situation has gone worse with the bootloop.
What can I try now?
@KaiserSnorezay
XZDR is still not compatible with MM, that's why you got a bootloop...
Also you can't install the "regular" TWRP with twrp manager on a LB as there is no recovery partition... it won't work and probably will mess your phone in the process.
The solution is to flash any KK / LP .ftf with flashtool (i would wipe everything when flashing as i have backups of my data/apps) , root it with kingroot or any other method you like, install xzdr for KK/LP and finally reboot to recovery and install the latest MM prerooted rom from niaboc which already has root&recovery (not xzdr btw) included. Since you have D6502 don't forget to install the baseband patch after the rom again
http://forum.xda-developers.com/xperia-z2/development/rom-official-6-0-1-23-5-0-486-beta-t3336770
Just did it exactly this way yesterday on my friends d6503 (minus the d6502 patch obviously) had 0 troubles MM, root and recovery working perfectly.
Thanks, will try this today. Is wiping data required or can i get by by just flashing the older one?
ptmaniac said:
The solution is to flash any KK / LP .ftf with flashtool (i would wipe everything when flashing as i have backups of my data/apps) , root it with kingroot or any other method you like, install xzdr for KK/LP and finally reboot to recovery and install the latest MM prerooted rom from niaboc which already has root&recovery (not xzdr btw) included. Since you have D6502 don't forget to install the baseband patch after the rom again
Click to expand...
Click to collapse
I managed to flash and root 17.1.2.A.0.314, but once again I'm unable to get any damn recovery to work. Installed XZDR, after that TWRP, in both cases it refuses to boot into recovery mode. What am I missing?
KaiserSnorezay said:
I managed to flash and root 17.1.2.A.0.314, but once again I'm unable to get any damn recovery to work. Installed XZDR, after that TWRP, in both cases it refuses to boot into recovery mode. What am I missing?
Click to expand...
Click to collapse
Weird, after you have your phone rooted it should be simple to install xzdr... just enable usb debugging in the phone and make sure you have the adb drivers correctly installed in your pc.
Download the latest xzdr from nut's thread ( http://forum.xda-developers.com/showthread.php?t=2261606 ) unzip it and run install.bat . After a successful install the phone should reboot to twrp automatically and it's done.
Okay, I fixed it..using Flashfire! No idea why the recovery didn't work earlier, but now finally I'm on Marshmallow. Thanks for the help!
KaiserSnorezay said:
Okay, I fixed it..using ! No idea why the recovery didn't work earlier, but now finally I'm on Marshmallow. Thanks for the help!
Click to expand...
Click to collapse
hey bro, just read your post. Yesterday i got an update msg in my software update menu of my Xperia Z2 D6502. After i updated i went into bootloop. i have very important stuff in my phone. i updated earlier too all the updates that sony servers inform about. so then i thought to flash with the stock file. Although i didnt knew the firmware number , i just flashed with 5.1.1 , 1st with Customized IN & later with of US. Both of them didn't work as well. Please help me out. I'm not much aware about this root stuff & all. hope to get reply soon from you or anyone in this forum.
-also i don't know the exact firmware number-
dodge911 said:
hey bro, just read your post. Yesterday i got an update msg in my software update menu of my Xperia Z2 D6502. After i updated i went into bootloop. i have very important stuff in my phone. i updated earlier too all the updates that sony servers inform about. so then i thought to flash with the stock file. Although i didnt knew the firmware number , i just flashed with 5.1.1 , 1st with Customized IN & later with of US. Both of them didn't work as well. Please help me out. I'm not much aware about this root stuff & all. hope to get reply soon from you or anyone in this forum.
-also i don't know the exact firmware number-
Click to expand...
Click to collapse
Try what ptmaniac suggested - flash an older FTF that can be rooted (more recent ones can't), root it, install recovery and then flash the newest build.
You'll have to improve your Google-fu to find a suitable firmware and a root technique for it.
KaiserSnorezay said:
Try what ptmaniac suggested - flash an older FTF that can be rooted (more recent ones can't), root it, install recovery and then flash the newest build.
You'll have to improve your Google-fu to find a suitable firmware and a root technique for it.
Click to expand...
Click to collapse
okay. you mean flashing any old firmware ( which i did and still in bootloop ) & root it. Then installing recovery for the same firmware ?
with "recovery" will i be able to get back my whole data ?
KaiserSnorezay said:
Long story - Tried to apply the latest Marshmallow rooted package for D6503 on my 6502 that was already rooted with XZ dual recovery. It installed successfully, was rooted too...but I forgot to add the patch that would fix the radio not working. So I try to reboot to recovery...and that doesn't work anymore. I tried installing TWRP recovery from the manager app, but it wouldn't reboot. Then I ran the XZ recovery installer externally, and now my phone is ****ed. Stuck at an infinite boot loop.
At this stage the only thing I can access is flashtool and fastboot, and since my bootloader is locked I can't flash a recovery that way (nor do I want to permanently lose DRM keys/camera quality as I've heard happens with unlocking the bootloader). I have a memory card and I used the option to disable loading the recovery specified on the XZ thread by adding a 'donotload' file on the sd card.
Still no use - I get a Sony logo for about 5 seconds, the screen goes dark and back to the same. At this point probably my recovery is screwed up or non existent and a bad situation has gone worse with the bootloop.
What can I try now?
Click to expand...
Click to collapse
hey i am having same problem with my xperia Z2 , it stucked in bootloop ,i have already tried to flash new firmware from xperifirm using flash tool,but i think my usb debugging is off, what can i do ,i cant start my phone so there are no chances for turning USB debugging on,what can i do, any solution,, just want my phone back,it will be okay if I loose my all data..please
DedSec_35 said:
hey i am having same problem with my xperia Z2 , it stucked in bootloop ,i have already tried to flash new firmware from xperifirm using flash tool,but i think my usb debugging is off, what can i do ,i cant start my phone so there are no chances for turning USB debugging on,what can i do, any solution,, just want my phone back,it will be okay if I loose my all data..please
Click to expand...
Click to collapse
Sorry, I ditched my Z2 for a Oneplus 3 in August 2016. Learnt my lesson, only going to use phones with easily unlockable bootloaders.
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