Related
Hello,
I've unlocked my bootloader and subsequently had installed TWRP (months ago).
Not long after, I decided to go back to stock for a while, and went back to CM a month ago.
However, I realized back then that I was loading into stock recovery even after taking the steps to install TWRP (http://forum.xda-developers.com/honor-5x/development/root-kiw-l24-usa-kiwi-t3305190)
During these steps, there were no errors (fastboot/adb logs show all things were done successfully).
However, some funky quirk (that I don't remember) got me loaded with TWRP once, which gave me the window to install CM (I remember it involving having to be connected to the PC).
Now I'm trying to install a new CM build, but I can't get it loading TWRP.
I've downloaded the TWRP Manager App, which tells me that I have TWRP 3.0.0.0, but when I reboot to recovery, I am given the stock EMUI recovery.
Does anyone know what is happening in this case? Has anyone experienced a similar issue?
Thank you!
undesputed said:
Hello,
I've unlocked my bootloader and subsequently had installed TWRP (months ago).
Not long after, I decided to go back to stock for a while, and went back to CM a month ago.
However, I realized back then that I was loading into stock recovery even after taking the steps to install TWRP (http://forum.xda-developers.com/honor-5x/development/root-kiw-l24-usa-kiwi-t3305190)
During these steps, there were no errors (fastboot/adb logs show all things were done successfully).
However, some funky quirk (that I don't remember) got me loaded with TWRP once, which gave me the window to install CM (I remember it involving having to be connected to the PC).
Now I'm trying to install a new CM build, but I can't get it loading TWRP.
I've downloaded the TWRP Manager App, which tells me that I have TWRP 3.0.0.0, but when I reboot to recovery, I am given the stock EMUI recovery.
Does anyone know what is happening in this case? Has anyone experienced a similar issue?
Thank you!
Click to expand...
Click to collapse
Reinstallt it try this TWRP http://www.mediafire.com/download/15g5i63gke9ddgp/kiwi_twrp_3-21_recovery.img its version 3.0.2.0 (Most recent)
The most recent is 5-14 (also based on v3.0.2.0 ).
TWRP 5.14
3-21 was built on March 21, and 5-14 on May 14.
mooms said:
The most recent is 5-14 (also based on v3.0.2.0 ).
TWRP 5.14
3-21 was built on March 21, and 5-14 on May 14.
Click to expand...
Click to collapse
Just for the record I'm using a even newer one than the 5-14 posted above
@yuweng posted a version of 3.0.2.0 that will make images of many partitions on the phone that even 5-14 ignores
you can download it here >> https://www.androidfilehost.com/?fid=24588212152305793
please note it was discovered early on that you cannot share the oeminfo partition on the phone, it's locked to your device and can / will brick a phone it's not from. just be careful what you restore with such a powerful version of TWRP.
@undesputed
I have seen this before where flashing TWRP does not seem to stick.
boot to the bootloader and see if frp is unlocked ... if not you need to
boot to your OS and remove your google account from the device
reboot to the bootloader and attempt the flash again. if it still fails to stick you can always just use
fastboot boot twrp.img and it will work just fine... just not installed
Arobase40 said:
Do you mean 3.0.2.0 is newer and supports more partitions than 5-14 ???
Click to expand...
Click to collapse
Their both 3.0.2.0 the one I just posted has more features
Sent from my SM-N920T using Tapatalk
clsA said:
Just for the record I'm using a even newer one than the 5-14 posted above
@yuweng posted a version of 3.0.2.0 that will make images of many partitions on the phone that even 5-14 ignores
you can download it here >> https://www.androidfilehost.com/?fid=24588212152305793
please note it was discovered early on that you cannot share the oeminfo partition on the phone, it's locked to your device and can / will brick a phone it's not from. just be careful what you restore with such a powerful version of TWRP.
@undesputed
I have seen this before where flashing TWRP does not seem to stick.
boot to the bootloader and see if frp is unlocked ... if not you need to
boot to your OS and remove your google account from the device
reboot to the bootloader and attempt the flash again. if it still fails to stick you can always just use
fastboot boot twrp.img and it will work just fine... just not installed
Click to expand...
Click to collapse
@clsA
frp is labeled as "UNLOCK" as oppsed to bootloader labeled as "UNLOCKED".
If it's just about removing my google account, will this be resolved the next time I do a factory reset?
Nevertheless, thank you so much for the command fastboot boot twrp.img, I realized that that was what I had used the last time.
I'm currently able to boot into TWRP this way. Awesome!
@clsA
Thanks for the link & infos.
Can you tell which features are added in this new TWRP ? name of the partitions ?
Thanks.
mooms said:
@clsA
Thanks for the link & infos.
Can you tell which features are added in this new TWRP ? name of the partitions ?
Thanks.
Click to expand...
Click to collapse
it would be much easier to just install it and test it for yourself
I did find a bug it would not backup to my OTG stick
clsA said:
it would be much easier to just install it and test it for yourself
I did find a bug it would not backup to my OTG stick
Click to expand...
Click to collapse
I don't use all the features, so i will maybe miss the changes.
Never used OTG to made a backup (I use ext_SD), I don't know if it works with other builds of TWRP.
mooms said:
I don't use all the features, so i will maybe miss the changes.
Never used OTG to made a backup (I use ext_SD), I don't know if it works with other builds of TWRP.
Click to expand...
Click to collapse
USB-OTG works flawlessly on the 5-14 version I was not able to use it with the newer one @yuweng posted in his guide
the screen shots show all the partitions it's able to work with
Arobase40 said:
I thought 3.0.2.0 was just an interim version between twrp_2-27 and twrp_5-14... ^^
Click to expand...
Click to collapse
your confusing TWRP versions with TWRP release dates
2-27 and 5-14 are release dates where as 3.0.2.0 is the version of TWRP not the date
the first version of TWRP for this device was actually 2.8.7.0 and was released on 2-16-2016
Same issue
Hey so I have the same exact issue umm did you ever resolve this problem becuSe I can't seem to crack it and it's a bit frustrating cuz by no means am I a pro but coming from using the OnePlus one the OnePlus 2 the OnePlus x and the Nexus 6 rooting them and restoring them after many failed attempts resulting in bricking my phone and even eventually unbrick them I do know a thing or two and I am stumped please help you are the only other person in this world other then my self that seems to be having this issue if you don't mind would you be so kind and email gmail me cuz I don't use or check this forum often thanks millerfamily805
clsA said:
Just for the record I'm using a even newer one than the 5-14 posted above
@yuweng posted a version of 3.0.2.0 that will make images of many partitions on the phone that even 5-14 ignores
you can download it here >> https://www.androidfilehost.com/?fid=24588212152305793
please note it was discovered early on that you cannot share the oeminfo partition on the phone, it's locked to your device and can / will brick a phone it's not from. just be careful what you restore with such a powerful version of TWRP.
@undesputed
I have seen this before where flashing TWRP does not seem to stick.
boot to the bootloader and see if frp is unlocked ... if not you need to
boot to your OS and remove your google account from the device
reboot to the bootloader and attempt the flash again. if it still fails to stick you can always just use
fastboot boot twrp.img and it will work just fine... just not installed
Click to expand...
Click to collapse
Can it be used with other honor devices?
Got my answer... Thanks...
Sent from my PLK-L01 using XDA Labs
It depend on the device
I used to flash new ROM's on my old Galaxy S2 and there was never a issue of bootloader thing and same goes for old Xiaomi phones like redmi 1s.
But recently When xiaomi started locking bootloader , even after unlocking bootloader ,In most of ROM threads there is warning to delete the bootloader file from MIUI recovery ROM and then flash the ROM through recovery as it'll relock the bootloader.
Why does this happen so ?
1) What is the difference between official and unofficial unlocked bootloader ?
2) How much difference does one make if we want to flash all type of ROM's including MIUI , CM ,RR etc ?
3) Is there any way in which bootloader once unlocked , we don't have to worry about getting it relocked by flashing other ROM's like exactly what happens in most other android smartphones after unlocking their bootloader ?
Please clear the above doubts as it's becoming very confusing and irritating on flashing the ROM and what points needed to be kept in mind to avoid bricking the RN3.
Read this thread, my phone was officially unlocked the bootloader and used alka twrp to flash official rom with the ease. No need to do anything, just flashed it, superSU and exposed. Rebooted my phone, done. Only failed on incremental ota update, rebooted phone and received a second ota full rom and always success.
http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
Sent from my Redmi Note 3 using Tapatalk
lack of good/complete tutorials
I believe flashing has always been a tricky job, more or less. The fact of the matter is that (for our device) I see very little complete tutorials in ROM threads, they all focus on the last bit of flashing. Some hazards are being mentioned and in the best case scenario you get a link to a vague solution (cross other forums and boards), never a full tutorial in the starting topic or the second post however. Back in the days you would see full explanations in every ROM thread, first posts were even being reserved for that. Nowadays users are being supposed to know it al which most do not.
Besides from the complete guides I also noticed that whenever something is explained, the explanations themselves are poor in terms of language (grammar as well as vocabulary) causing even more problems for newbies to fully understand what they are up to.
I am ne to the Xiaomi community but I am absolutely not new to flashing, cooking etc. (started back in the days with iPAQ's and so on) but I also had a though time to end up where I am now with a official unlocked phone that is rooted, has a custom recovery and a Xiaomi.eu ROM. MY journey was a long one but I must conclude that none of the steps were a real hazard, but combining everything in a workflow in correct order was a pain in the back.
First thing that came to me was the idea of writing down my experiences in the form of a FULL tutorial, which I might do when I find the time. I am pretty sure this will help many fellow flashers, newbies and pro's, to establish what most of us did.
These were just my two cents.
P.S. One more thing I noticed is that there are a lot of unfinished projects, they do the job that they were needed for, but they do nothing else.
e.g. Why are there so many custom recoveries, are there no developers anymore that can combine them all to one-fits-all ?
timberwolf60 said:
Read this thread, my phone was officially unlocked the bootloader and used alka twrp to flash official rom with the ease. No need to do anything, just flashed it, superSU and exposed. Rebooted my phone, done. Only failed on incremental ota update, rebooted phone and received a second ota full rom and always success.
http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
That is a lot of If else there
Why we can't just flash any rom after unlocking bootloader officially and always have to fear about bootloader relock again?
If i am not mistaken this situation is in Xiaomi phones right ?
Dust2Dust said:
I believe flashing has always been a tricky job, more or less. The fact of the matter is that (for our device) I see very little complete tutorials in ROM threads, they all focus on the last bit of flashing. Some hazards are being mentioned and in the best case scenario you get a link to a vague solution (cross other forums and boards), never a full tutorial in the starting topic or the second post however. Back in the days you would see full explanations in every ROM thread, first posts were even being reserved for that. Nowadays users are being supposed to know it al which most do not.
Besides from the complete guides I also noticed that whenever something is explained, the explanations themselves are poor in terms of language (grammar as well as vocabulary) causing even more problems for newbies to fully understand what they are up to.
I am ne to the Xiaomi community but I am absolutely not new to flashing, cooking etc. (started back in the days with iPAQ's and so on) but I also had a though time to end up where I am now with a official unlocked phone that is rooted, has a custom recovery and a Xiaomi.eu ROM. MY journey was a long one but I must conclude that none of the steps were a real hazard, but combining everything in a workflow in correct order was a pain in the back.
First thing that came to me was the idea of writing down my experiences in the form of a FULL tutorial, which I might do when I find the time. I am pretty sure this will help many fellow flashers, newbies and pro's, to establish what most of us did.
These were just my two cents.
P.S. One more thing I noticed is that there are a lot of unfinished projects, they do the job that they were needed for, but they do nothing else.
e.g. Why are there so many custom recoveries, are there no developers anymore that can combine them all to one-fits-all ?
Click to expand...
Click to collapse
Yes right , but i think Xiaomi is the culprit here for every complicated procedure here.
What's the difference between officially and unofficially unlocked bootloader ? and how's Xiamio.eu ROM is different from global stable ROM ?
akhil17kr said:
Yes right , but i think Xiaomi is the culprit here for every complicated procedure here.
What's the difference between officially and unofficially unlocked bootloader ? and how's Xiamio.eu ROM is different from global stable ROM ?
Click to expand...
Click to collapse
Xiaomi.eu weekly rom was cooked from cn dev rom, removed Chinese apps and put in Google apps and more European languages. Those who wish to flash it must officially unlocked bootloader.
Sent from my Redmi Note 2 using Tapatalk
timberwolf60 said:
Xiaomi.eu weekly rom was cooked from cn dev rom, removed Chinese apps and put in Google apps and more European languages. Those who wish to flash it must officially unlocked bootloader.
Sent from my Redmi Note 2 using Tapatalk
Click to expand...
Click to collapse
and What's the difference between officially and unofficially unlocked bootloader ? i have unofficially now , should i officially unlock it ? if it makes flashing procedure easy ?
akhil17kr said:
Yes right , but i think Xiaomi is the culprit here for every complicated procedure here.
What's the difference between officially and unofficially unlocked bootloader ? and how's Xiamio.eu ROM is different from global stable ROM ?
Click to expand...
Click to collapse
Couple of examples: Xiaomi.eu gives me different locales and languages. It also sets default GPS location to Europe instead of Asia which provides a faster GPS fix. It is however behind in development so it doesn't have MIUI 8 yet.
As for the bootloader unlock: I have not looked into that since there is no need. If you follow all the steps in correct order and with correct ROM's official unlocking cannot go wrong. The culprit however is the complete chaos (now I said it) in instructions and tutorials. So I have not looked into the unofficial bootloader unlocking.
Dust2Dust said:
Couple of examples: Xiaomi.eu gives me different locales and languages. It also sets default GPS location to Europe instead of Asia which provides a faster GPS fix. It is however behind in development so it doesn't have MIUI 8 yet.
As for the bootloader unlock: I have not looked into that since there is no need. If you follow all the steps in correct order and with correct ROM's official unlocking cannot go wrong. The culprit however is the complete chaos (now I said it) in instructions and tutorials. So I have not looked into the unofficial bootloader unlocking.
Click to expand...
Click to collapse
do you mind reading this question and clarify the steps , asked in Official CM13 thread. Nobody answered there:-
"Hey , I've unlocked RN3 bootloader unofficialy and currently on MIUI stable version with root and TWRP recovery.
I want to taste official CM13 but no plans to use it , just test it. After using it for day or 2 , i want to switch back to my MIUI ROM.
What should be the ideal steps through which i can avoid all these hassles of Bootloader relock stuff.
Can't we just normally go back to MIUI ROM by restroing using TWRP backup ?
Here's what i'll do , please correct the steps:-
1) Flash TWRP alka version and make complete backup of current MIUI ROM.
2) Wipe system ,data, cache,dalvik cache.
3 First flash CM-fIrmware file,then CM13 ROM , then gapps.
4) Reboot and use CM for 2-3 days.
Now to go back to the MIUI ROM backup:-
1) Reboot to alka recovery.
2) Wipe system ,data, cache,dalvik cache.
3) restore the MIUI Nandroid backup (Deselect firmware file.)
4) Reboot
DONE ! Back to MIUI.
If my steps are right ?
Please guide on the same. "
akhil17kr said:
do you mind reading this question and clarify the steps , asked in Official CM13 thread. Nobody answered there:-
"Hey , I've unlocked RN3 bootloader unofficialy and currently on MIUI stable version with root and TWRP recovery.
I want to taste official CM13 but no plans to use it , just test it. After using it for day or 2 , i want to switch back to my MIUI ROM.
What should be the ideal steps through which i can avoid all these hassles of Bootloader relock stuff.
Can't we just normally go back to MIUI ROM by restroing using TWRP backup ?
Here's what i'll do , please correct the steps:-
1) Flash TWRP alka version and make complete backup of current MIUI ROM.
2) Wipe system ,data, cache,dalvik cache.
3 First flash CM-fIrmware file,then CM13 ROM , then gapps.
4) Reboot and use CM for 2-3 days.
Now to go back to the MIUI ROM backup:-
1) Reboot to alka recovery.
2) Wipe system ,data, cache,dalvik cache.
3) restore the MIUI Nandroid backup (Deselect firmware file.)
4) Reboot
DONE ! Back to MIUI.
If my steps are right ?
Please guide on the same. "
Click to expand...
Click to collapse
I did the same steps above after flashing resurrection remix with cm13 radio,after restoration of miui from twrp Alka backup my fingerprint sensor stopped working bcos the firmware didn't restore and I unchecked that partition so what i did was again.
1) go back to twrp Alka
2) flash the full MIUI 8 rom .zip and rebooted
3) then the fingerprint started working .
So Alka twrp has a bug in Restoration of firmware partition .so be careful and have a full twrp Alka backup and then flash cm13 and firmware
akhil17kr said:
do you mind reading this question and clarify the steps , asked in Official CM13 thread. Nobody answered there:-
"Hey , I've unlocked RN3 bootloader unofficialy and currently on MIUI stable version with root and TWRP recovery.
I want to taste official CM13 but no plans to use it , just test it. After using it for day or 2 , i want to switch back to my MIUI ROM.
What should be the ideal steps through which i can avoid all these hassles of Bootloader relock stuff.
Can't we just normally go back to MIUI ROM by restroing using TWRP backup ?
Here's what i'll do , please correct the steps:-
1) Flash TWRP alka version and make complete backup of current MIUI ROM.
2) Wipe system ,data, cache,dalvik cache.
3 First flash CM-fIrmware file,then CM13 ROM , then gapps.
4) Reboot and use CM for 2-3 days.
Now to go back to the MIUI ROM backup:-
1) Reboot to alka recovery.
2) Wipe system ,data, cache,dalvik cache.
3) restore the MIUI Nandroid backup (Deselect firmware file.)
4) Reboot
DONE ! Back to MIUI.
If my steps are right ?
Please guide on the same. "
Click to expand...
Click to collapse
They look more or less correct, I choose not to go the CM way (yet) since there are still some flaws that I can't live with.
I would try to go to official unlock, whatever it takes. It just looks more solid & safe from what I have been reading so far.
Also I would choose to use an other Recovery:
Official TWRP with F2FS Support
• Based on official TWRP 3.0.2-2 & updated CyanogenMod source
• Adds Support For F2FS based file systems.
• Used for flashing official CyanogenMod 13 based ROMs.
• Users with official unlocked bootloader will have to flash Universal Boot Img Patcher (UBP) after flashing MIUI Recovery ROM Zip.
• Users with unofficial unlocked bootloader should strictly not use this TWRP for flashing MIUI Recovery ROM Zip.
That seems optimized for CM the most.
II should tell you that I received the phone two days ago and I am also still catching up on reading.
Add on, taken from the above link:
In case of unofficial unlock:
4. Flashing Official CM13 ROM
• Flash F2FS TWRP & Backup Current ROM.
• Select /data & /cache Partitions & Select Change File System
• Select F2FS & Swipe To Change
• Reboot to Recovery & Factory Reset
• Reboot to Recovery & Flash CM13 Firmware
• Reboot to Recovery & Flash CM13 Zip
• Flash Appropriate GApps Version Zip & Reboot to System
• To Return Back To Any ROM After Flashing CM13, Flash Safe TWRP v2 & Proceed.
Since i am newbie to this forum and all this rooting stuff, i am lately confused about lot of stuff about poco f1 in respect of flashing new rom over miui rom and also over some other custom rom plus back up/restore of existing rom.
I faced lot of problems of encryption and decryption and had to format my phone number of times. I am listing out few procedure for installing new rom over other customer rom and miui rom which i learned from this wonderful forum plus also the procedure of backing up your existing rom. So request all the experience developers to guide newbie like us step wise so we can also enjoy the fruitful advantage of this lovely forum.
for installing new rom i learned from this link https://forum.xda-developers.com/poco-f1/help/to-custom-rom-want-to-install-rom-t3902913 to follow the below mentioned procedure. I also posted my respective questions along with this step for answer from my beloved developers.
1. Remove pattern and pin. If you don't do this step then you will have to factory reset your phone with stock MIUI. (Is it compulsory to remove pattern and pin, what if we remove lock screen password by simply deleting these files from twrp
1.gatekeeper password key
2.gatekeeper pattern key
3.locksettings.db
4.locksettings.db-shm
5.locksettings.db-wal
will there be a problem)
2. Wipe all except internal storage and external storage.(this is understood)
3. Flash vendor and rom.(do i really need to flash vendor before flashing rom and this is applicable to all the custom roms i mean if i have pixel rom and want to install nytrogen rom, do i need to flash vendor all the time....plus where can i get this vendor file, can anyone provide a link for that)
4. Flash disableforceencryption with magisk 18.0.(this is very important to me, what is disableforceencryption file do,do i need to flash every time whenever i try to flash new custom rom)
5. Flash your twrp again so it isn't replaced by stock.(i still did not understand this part but still which twrp to flash official one or unofficial one, since official one gave me lot of trouble so i had to revert back to unofficial one, kindly provide your input in this)
Further for backing up your existing rom following steps have been learned from some different thread, kindly provide your input whether the same is right or wrong.
System image
Vendor image
Boot
Data
Modem
Efs
Please co-operate on this because lot of newbie like me facing different problem, your valuable input can bring smile on our faces.
Thanks in advance.
mandyady said:
Since i am newbie to this forum and all this rooting stuff, i am lately confused about lot of stuff about poco f1 in respect of flashing new rom over miui rom and also over some other custom rom plus back up/restore of existing rom.
I faced lot of problems of encryption and decryption and had to format my phone number of times. I am listing out few procedure for installing new rom over other customer rom and miui rom which i learned from this wonderful forum plus also the procedure of backing up your existing rom. So request all the experience developers to guide newbie like us step wise so we can also enjoy the fruitful advantage of this lovely forum.
for installing new rom i learned from this link https://forum.xda-developers.com/poco-f1/help/to-custom-rom-want-to-install-rom-t3902913 to follow the below mentioned procedure. I also posted my respective questions along with this step for answer from my beloved developers.
1. Remove pattern and pin. If you don't do this step then you will have to factory reset your phone with stock MIUI. (Is it compulsory to remove pattern and pin, what if we remove lock screen password by simply deleting these files from twrp
1.gatekeeper password key
2.gatekeeper pattern key
3.locksettings.db
4.locksettings.db-shm
5.locksettings.db-wal
will there be a problem)
2. Wipe all except internal storage and external storage.(this is understood)
3. Flash vendor and rom.(do i really need to flash vendor before flashing rom and this is applicable to all the custom roms i mean if i have pixel rom and want to install nytrogen rom, do i need to flash vendor all the time....plus where can i get this vendor file, can anyone provide a link for that)
4. Flash disableforceencryption with magisk 18.0.(this is very important to me, what is disableforceencryption file do,do i need to flash every time whenever i try to flash new custom rom)
5. Flash your twrp again so it isn't replaced by stock.(i still did not understand this part but still which twrp to flash official one or unofficial one, since official one gave me lot of trouble so i had to revert back to unofficial one, kindly provide your input in this)
Further for backing up your existing rom following steps have been learned from some different thread, kindly provide your input whether the same is right or wrong.
System image
Vendor image
Boot
Data
Modem
Efs
Please co-operate on this because lot of newbie like me facing different problem, your valuable input can bring smile on our faces.
Thanks in advance.
Click to expand...
Click to collapse
1. Yes, if you are able to find all the files related to locks, then you can delete them and boot. But it is much easier to remove the locks before flashing the new ROM.
3. Vendor firmware has to be flashed if you wipe. Also when some custom ROM specifically asks for a particular version of vendor firmware. The vendor firmware can be found on the download page of Xiaomi.
4. When the OEM ROM is flashed, it will encrypt your phone. Custom ROMs require unencrypted phone (some of them don't). But the TWRP now handles encryption/decryption and so, in my opinion, you don't need DFE zip at all if you have the correct TWRP (you already seem to have it).
5. If you are flashing OEM ROM, the built in recovery will overwrite the TWRP. To avoid this, you can flash Magisk immediately after flashing the ROM, before booting. It will preserve TWRP. No need for re-flashing TWRP if you are flashing custom ROM since they do not have in-built recovery. Further, I understand that the unofficial TWRP handles encryption/decryption better. So stick with it unless you have problems with it.
If you backup all the partitions, you can choose which ones to restore, the downside being that a lot of space will be required. But it is safer.
Hope you are smiling!
I thought I would share this ROM just in case anyone wants something a little different to the Shipped Stock Sony Firmware
The ROM is based on Sony XA F3111 (Single SIM UK Firmware)
Firmware Version: 33.3.A.1.97
Build Date: Fri Sep 15 04:41:21 CST 2017
It has only been tested on my own UK version Sony XA F3111
BootLoader needs to be Unlocked and of course Usual T&C's apply. Use at your own risk don't blame me if you brick your device or lose your valuable data etc etc.
So what's different about this ROM??
Ok so I have been working on this for quite sometime during the little free time I have.
The ROM is my own preferences only and it may not be to everyone's tastes so you're quite welcome to take it, leave it, add to it, strip it, mod it, etc, etc.
The ROM ditches the not so useful stuff of Sony's but retains what I consider the good stuff like Music Album and the Camera.
Where possible I have replaced the Sony stuff with Google's Stuff which receive regular updates and keep the Rom looking fresh.
The trick to this ROM was finding a good balance without breaking anything in the process which I think I have now achieved.
This is a list of the visible apps installed, there are quite a few none visible Sony & MediaTek apps still installed that relate to settings functions and some background stuff.
Google Apps:
Clock
Calculator
Contacts
Calendar
Chrome
Drive
Files
GMail
Hangouts
Maps
Messages
Phone
Photos
Play Store
Wallpapers
YouTube
Sony Apps:
Album (Please disable this in /settings/app It will constantly search for other apps I removed otherwise. Use the pre-installed Google Photos app instead)
Camera
Music
Radio
Swiftkey (Left this in because I like it)
There is nothing Fancy about this ROM it's based on pure stock with the mods being restricted to the following.
Converted boot.elf to Boot.img
forceencryption Removed.
dm-verity Removed
I converted all the images in the stock Boot Animation so it is now a much more pleasing black rather than the awful white burning out your eyeballs one.
I remember messing with the logo partition once before and that did not end well so I left it alone. Sadly the logo splashscreen is still the awful white version.
TWRP Recovery fixed to support more partitions (Backing Up and Restore)
Flashing InstructionsThe ROM is packaged as a TWRP Backup containing system, oem, boot and recovery (TWRP)
First you will need to install this TWRP HERE which has oem partition support and others too.
1. Install the TWRP Recovery above.
2. Boot to the new TWRP and backup oem, system and boot then move it to a safe place off device or to and external sdcard. Same goes for anything you value like pictures, music, etc, etc
3. Once you have Backed Up everything FORMAT your /data partition using TWRP. Wipe > Format Data (type yes to confirm)
When that's done choose Wipe > Advanced Wipe and select Dalvik / ART Cache and Cache after that from the TWRP menu choose Reboot and select Recovery
4. When back in recovery swipe to allow then do a quick Backup of any small partition like boot or recovery. This will just create the folders on your clean data partition unless your default backup is external sdcard.
5. Now extract/unpack the downloaded ROM from HERE and move the folder SonyXA-Android-One to TWRP/BACKUPS/Sony_XA/
6. Once done go to TWRP Menu and choose Restore and select SonyXA-Android-One
7. Once done go to the Reboot Menu and Choose Power OFF
8. Wait a few Mins and power on normally.
First boot can take a while but if you see the boot animation start everything should be fine so go have a brew while you wait.
Play Services will want to Update so allow that then most apps will need to be updated to the latest version.
Arrange the app icons and widgets on your Home screen and choose a nice wallpaper or live wallpaper and your done.
Hopefully everything will be quick & smooth. :fingers-crossed:
The ROM is not pre rooted so Root in the usual way using Magisk
PS: Ensure you check your app permissions and Default APPS the Phone app is Not the Default one even though it's the only one installed so please choose it Manually along with any others that do not set by themselves.
Thanks
Some Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
......
.....
.....
Thank you so much! I'm looking a long time for a custom ROM for xperia xa. The hardware and the device itself are still good for an average user like me but the bloatware are really annoying. A custom ROM based on stock ROM brings the stability but better performance, I hope. I will definitely try it at the next weekend. :good:.
If some one else tried it, please post your experience with other country versions.
z4Android said:
Thank you so much! I'm looking a long time for a custom ROM for xperia xa. The hardware and the device itself are still good for an average user like me but the bloatware are really annoying. A custom ROM based on stock ROM brings the stability but better performance, I hope. I will definitely try it at the next weekend. :good:.
If some one else tried it, please post your experience with other country versions.
Click to expand...
Click to collapse
Thanks. :good:
Be sure to let me know how you get on with it. :fingers-crossed:
I am not sure where you are from or which version of the XA you have but I am sure the ROM could be easily adapted for your own version.
All I would need would be a backup of your /oem & /boot partitions and the build.prop from your /system .
There is a modem config file in /oem which states telefonica uk I am unsure if this has any effect at all as I am sure I have flashed firmware from other European regions with no noticable effects.
I'm from Germany. I not sure but I think it should be no problems installing on my device f3111 single sim like yours (but german version of course ).
I'm not at home now. When I get back I will try your ROM. If it doesn't work I will backup OEM and boot partition as you mentioned. Last time I try to make a backup with twrp I got a error that system cannot be mounted. No idea why, so I hope I don't need make backup (I will just backup my data manually).
z4Android said:
I'm from Germany. I not sure but I think it should be no problems installing on my device f3111 single sim like yours (but german version of course ).
I'm not at home now. When I get back I will try your ROM. If it doesn't work I will backup OEM and boot partition as you mentioned. Last time I try to make a backup with twrp I got a error that system cannot be mounted. No idea why, so I hope I don't need make backup (I will just backup my data manually).
Click to expand...
Click to collapse
Hi, Your version should have no issues as it's identical to mine :good:
As for TWRP yes it does have issues with Unmounting /system for some reason
So if you mount /system from the Mount Menu TWRP or auto mount system you will not be able to Unmount mount it due to the "device or resource busy" error
If this happens you will need to ensure auto mounting is unselected and reboot to recovery from the Reboot menu.
I will look into the TWRP issue later to make things easier
Greetings,
quick question: Does the ROM restore procedure keep the TWRP on the boot partition somehow? Will it be possible to boot in TWRP after restoring the modded ROM?
I got the "bluesplash" ROM right now, it's modded quite similar and was restored by TWRP the same way. If only TWRP would sill be accessible...
Bluesummerz said:
Greetings,
quick question: Does the ROM restore procedure keep the TWRP on the boot partition somehow? Will it be possible to boot in TWRP after restoring the modded ROM?
I got the "bluesplash" ROM right now, it's modded quite similar and was restored by TWRP the same way. If only TWRP would sill be accessible...
Click to expand...
Click to collapse
TWRP lives in the Recovery partition which can be accessed by holding Volume Down and pressing the Power button until you see the logo then release the Power button but keep holding the volume down.
This ROM is based on Android 7.0 and I think your current bluesplash ROM is based on Android 6.0 if I am not mistaken so there may be some unknown issues so I would recommend upgrading your device to 7.0 before flashing this ROM
bigrammy said:
TWRP lives in the Recovery partition which can be accessed by holding Volume Down and pressing the Power button until you see the logo then release the Power button but keep holding the volume down.
This ROM is based on Android 7.0 and I think your current bluesplash ROM is based on Android 6.0 if I am not mistaken so there may be some unknown issues so I would recommend upgrading your device to 7.0 before flashing this ROM
Click to expand...
Click to collapse
Hey, thanks for the quick response!
of course I meant recovery but still maybe you can clear this one up for me in general. Since I'm looking our for a decent custom ROM (and while waiting for the LinageOS port) I was wondering about some stuff...
1. You're right the bluesplash ROM is Android 6. It does have some nice features which I guess have to weight off for against how much I'd like Android 7. Also Security Update status of Bluesplash is January 2017 and won't update beyond that... while the screenshot here tells it's August 2017.
2.
I unlocked the bootloader, flashed the TWRP by fastboot and used the TWRP on my F3111 to successfully restore the bluesplash ROM. Now holding down Volume- while booting to enter TWRP does NOT work any more. You'll still see like one quick 'flicker' on the boot animation which kinda suggests "ok, would have booted to recovery, but not this time".
Here comes the part I never really understood even after using this awesome forum for finding and flashing custom ROMs for several phones. Even though, TWRP is on the recovery and the kernel is on the boot partition (right?) so often you'll read instructions on TWRP threads containing download links for recovery.img AND boot.img. I had - or guess I had to - fastboot-flash both .img files to boot into TWRP.
I never had this when the flashing was done by TWRP "install" .zip mechanisms. Bluesplash as well as this ROM - if I'm not mistaken - comes not in that format but by the Backup/Restore TWRP feature. So for me it seems, that using "install .zip" does flash system partition and maybe boot but keeping recovery for re-entering TWRP, while the "Restore backup" also flashes the boot.img in a way such that TWRP won't boot. Also just re-flashing recovery.img and boot.img after restoring Bluesplash kinda break the normal, non-TWRP boot
--> So how can this be, how is it supposed to be and what is the connection between recovery and boot partitions when it comes to TWRP?
--> does all of this goes for this Android 7 ROM as well? Can anyone verify that on this ROM you'll still be able to boot in TWRP?
3. I know now I got the Sony Xperia XA F3111. When I first got it with stock firmware, I somehow flashed TWRP and when I USB connected the phone while in TWRP to a PC, it showed up as "ukulele". I thought I got "tuba" which was reinforced when some ROM couldn't get flashed, saying "this rom [...] is for ukulele [...] this is tuba".
Bluesummerz said:
Hey, thanks for the quick response!
of course I meant recovery but still maybe you can clear this one up for me in general. Since I'm looking our for a decent custom ROM (and while waiting for the LinageOS port) I was wondering about some stuff...
1. You're right the bluesplash ROM is Android 6. It does have some nice features which I guess have to weight off for against how much I'd like Android 7. Also Security Update status of Bluesplash is January 2017 and won't update beyond that... while the screenshot here tells it's August 2017.
2.
I unlocked the bootloader, flashed the TWRP by fastboot and used the TWRP on my F3111 to successfully restore the bluesplash ROM. Now holding down Volume- while booting to enter TWRP does NOT work any more. You'll still see like one quick 'flicker' on the boot animation which kinda suggests "ok, would have booted to recovery, but not this time".
Here comes the part I never really understood even after using this awesome forum for finding and flashing custom ROMs for several phones. Even though, TWRP is on the recovery and the kernel is on the boot partition (right?) so often you'll read instructions on TWRP threads containing download links for recovery.img AND boot.img. I had - or guess I had to - fastboot-flash both .img files to boot into TWRP.
I never had this when the flashing was done by TWRP "install" .zip mechanisms. Bluesplash as well as this ROM - if I'm not mistaken - comes not in that format but by the Backup/Restore TWRP feature. So for me it seems, that using "install .zip" does flash system partition and maybe boot but keeping recovery for re-entering TWRP, while the "Restore backup" also flashes the boot.img in a way such that TWRP won't boot. Also just re-flashing recovery.img and boot.img after restoring Bluesplash kinda break the normal, non-TWRP boot
--> So how can this be, how is it supposed to be and what is the connection between recovery and boot partitions when it comes to TWRP?
--> does all of this goes for this Android 7 ROM as well? Can anyone verify that on this ROM you'll still be able to boot in TWRP?
3. I know now I got the Sony Xperia XA F3111. When I first got it with stock firmware, I somehow flashed TWRP and when I USB connected the phone while in TWRP to a PC, it showed up as "ukulele". I thought I got "tuba" which was reinforced when some ROM couldn't get flashed, saying "this rom [...] is for ukulele [...] this is tuba".
Click to expand...
Click to collapse
You are confusing things beyond what they need to be
This is why I said you should first upgrade to 7.0 You can use FlashTool for this if need be. After that is done simply rename the recovery.emmc.win & boot.emmc.win from the download to recovery.img & boot.img then fastboot them to recovery & boot respectively.
You Should now be able to boot to TWRP and use restore once your /data partition is FORMATED per the instructions above.
TWRP is a stand alone recovery.img complete with the kernel and on Android 7.0 you can boot to recovery without any issue providing the bootloader is unlocked.
You would need to be at this stage for flashing Lineage 14.1 anyway so may as well do it now just in case we make any break through on that which is still very much a WIP.
bigrammy said:
You are confusing things beyond what they need to be
This is why I said you should first upgrade to 7.0 You can use FlashTool for this if need be. After that is done simply rename the recovery.emmc.win & boot.emmc.win from the download to recovery.img & boot.img then fastboot them to recovery & boot respectively.
You Should now be able to boot to TWRP and use restore once your /data partition is FORMATED per the instructions above.
TWRP is a stand alone recovery.img complete with the kernel and on Android 7.0 you can boot to recovery without any issue providing the bootloader is unlocked.
You would need to be at this stage for flashing Lineage 14.1 anyway so may as well do it now just in case we make any break through on that which is still very much a WIP.
Click to expand...
Click to collapse
And that is exactly why I like these forums, if you provide enough insight to a question, you'll get the full-spectrum answer, splendid!
And yes, confusing things is in my nature, also I might find it troublesome to know when I get like off topic here, so please stop me the moment, it would be better to switch to pm.
So the image format in those firmware bundles, typically having the emmc.win file extension are actually the same binary format as the fastboot .img ones? Now that's good to know.
Upgrading with FlashTool: I'll use the stock Android 7 Firmware for this right?
After that I fastboot recovery first, then boot using the renamed files from this threads ROM, got it. And then booting into TWRP, doing the system format, making it 'ready' for the restore.
And if everything goes as planned, you would guarantee, that after this thread's ROM is restored, booting into TWRP does work?
PS
indeed, Linage for F3111 would be glorious, meanwhile, what does WIP stand for (no native speaker here from Germany)
Bluesummerz said:
So the image format in those firmware bundles, typically having the emmc.win file extension are actually the same binary format as the fastboot .img ones? Now that's good to know.
Click to expand...
Click to collapse
Correct they are essentially a dd backup of the entire partition in question.
[Edit] To expand TWRP does not convert anything so if those partitions had the stock recovery & boot .elf format on them when the backup was performed they will still be .elf's which are not fastboot compatible. Those in my ROM have already been converted to .img format which is compatible with fastboot.
If you ever got stuck for some reason then you could simply use FlashTool to restore the Stock Recovery (fotakernel), Boot, OEM & System
Bluesummerz said:
Upgrading with FlashTool: I'll use the stock Android 7 Firmware for this right?
Click to expand...
Click to collapse
Correct.
My Phone is restored using the F3111_33.3.A.1.97_1302-4476_R2B.ftf (FlashTool Firmware) and the ROM is based on this version.
Try to use a 33.3.A.1.97 if possible as I know that works.
Bluesummerz said:
After that I fastboot recovery first, then boot using the renamed files from this threads ROM, got it. And then booting into TWRP, doing the system format, making it 'ready' for the restore.
Click to expand...
Click to collapse
Fastboot the recovery and the boot then You Simply need to follow the Flashing Instructions from step 2 in the first post from this point.
It is /data that gets wiped manually BTW (By The Way). TWRP will take care of the /system during it's restore tasks.
Bluesummerz said:
And if everything goes as planned, you would guarantee, that after this thread's ROM is restored, booting into TWRP does work?
Click to expand...
Click to collapse
Yes providing you did everything correctly I see no reason why it would not work for you unless your device is a extra special Sony XA
Bluesummerz said:
indeed, Linage for F3111 would be glorious, meanwhile, what does WIP stand for (no native speaker here from Germany)
Click to expand...
Click to collapse
It stands for a Work In Progress.
The term work-in-progress (WIP) describes partially finished goods awaiting completion.
Does it has VOLTE support
Great work bro
I am from India using f3116 Dual Sim version
I really wanted VOLTE
does anyone tried it?????
altmash mirza said:
Great work bro
I am from India using f3116 Dual Sim version
I really wanted VOLTE
does anyone tried it?????
Click to expand...
Click to collapse
Not sure about VOLTE
If anyone did try this ROM nobody reported back
I guess this device is dead now as there seems to be very little activity which is a shame
drm fix working in case we use sony backups?
Hi, i just want to give a feedback. I could restore your backup successfully. Every things work fine, no issuses till now. Thank you very much. :good:
Do you plan to make a rom based on oreo or maybe pie it would be great.
z4Android said:
Hi, i just want to give a feedback. I could restore your backup successfully. Every things work fine, no issuses till now. Thank you very much. :good:
Do you plan to make a rom based on oreo or maybe pie it would be great.
Click to expand...
Click to collapse
Thanks for the feed back. :good:
Sorry no Oreo or Pie unless we fix the Ril issue on none Stock custom ROM's like the Lineage 14.1
bootlogo
bigrammy said:
I thought I would share this ROM just in case anyone wants something a little different to the Shipped Stock Sony Firmware
The ROM is based on Sony XA F3111 (Single SIM UK Firmware)
Firmware Version: 33.3.A.1.97
Build Date: Fri Sep 15 04:41:21 CST 2017
It has only been tested on my own UK version Sony XA F3111
There is nothing Fancy about this ROM it's based on pure stock with the mods being restricted to the following.
Converted boot.elf to Boot.img
forceencryption Removed.
dm-verity Removed
I converted all the images in the stock Boot Animation so it is now a much more pleasing black rather than the awful white burning out your eyeballs one.
I remember messing with the logo partition once before and that did not end well so I left it alone. Sadly the logo splashscreen is still the awful white version.
TWRP Recovery fixed to support more partitions (Backing Up and Restore)
Click to expand...
Click to collapse
hello sir @bigrammy,
i want to ask about bootlogo.
i have follow this guide :
1. https://forum.xda-developers.com/android/general/info-how-to-device-partition-info-adb-t3766930 : for get detail of android partition
2. https://forum.xda-developers.com/showthread.php?t=1953726 : For Changing Bootlogo App
3. https://forum.xda-developers.com/oneplus-3t/themes/change-oem-splash-screen-t3516818 : for flash and dump logo partition
i have done with editing bootlogo, but i cant flash logo.img to logo partition.
twrp : black screen - no boot
fastboot : not allowed
can you guide me to doing this?
Hello, I got this phone from my grandfather and I would like to give it to my little sister, the system being really bloat I want to put a custom rom on the phone to have more space and battery life, so I found yours which loook very nice, can you just tell me if that this rom is 100% compatible with a European Xperia XA F3111 ? Also, is the rom easy to use ? for an 11 years old girl ?
Thanks a lot, great job !!
Codetrr said:
hello sir @bigrammy,
i want to ask about bootlogo.
i have follow this guide :
1. https://forum.xda-developers.com/android/general/info-how-to-device-partition-info-adb-t3766930 : for get detail of android partition
2. https://forum.xda-developers.com/showthread.php?t=1953726 : For Changing Bootlogo App
3. https://forum.xda-developers.com/oneplus-3t/themes/change-oem-splash-screen-t3516818 : for flash and dump logo partition
i have done with editing bootlogo, but i cant flash logo.img to logo partition.
twrp : black screen - no boot
fastboot : not allowed
can you guide me to doing this?
Click to expand...
Click to collapse
If your TWRP is not working you should fix this FIRST before doing anything else.
Warning: The logo partition is very important and as I said before it's part of the secure boot chain so if the logo does match the signature and or hash the ROM will boot loop or soft brick it did for me when I tried to change it so be very careful and make sure you can recover the phone with FlashTool.
To find partitions on Mediatek devices use this cmd.
Code:
ls -l /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name
This will give you a list of all partitions by-name and the actual dev block.
The logo partition is
Code:
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo
So to flash the logo.img with dd you would copy the logo.img to your internal sdcard and use the following cmd.
Code:
dd if=/sdcard/logo.img of=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo
Sorry I cannot test your logo's because my wife use's this phone now as her everyday phone so she would not let me mess around with it now.
Akinimaginable said:
Hello, I got this phone from my grandfather and I would like to give it to my little sister, the system being really bloat I want to put a custom rom on the phone to have more space and battery life, so I found yours which loook very nice, can you just tell me if that this rom is 100% compatible with a European Xperia XA F3111 ? Also, is the rom easy to use ? for an 11 years old girl ?
Thanks a lot, great job !!
Click to expand...
Click to collapse
The ROM is just stock ROM with most bloat ware removed and Google alternatives installed. I would recommend not to use the Sony "Album" app as it requires some other Sony apps which I removed and it continually looks for these apps. So just disable it in /settings/apps and use the pre-installed Google photos instead.
Also ensure you manually set the Phone app as the default dialer even though it's the only one or you will not be able to make or answer calls.
11 year girl! I would not worry they probably know more than we do at that age :laugh:
Yes it should be 100% compatible with a European Xperia XA F3111 ?
How to do this ?
I just rooted and flashed my old LG, and probably the by the "good" method. So if you have a link for the way to root and flash this phone, you'll make me very happy. I know that I have to go in adb flash TWRP as recovery, go in recovery by resetting the phone. Once this is done I have to wipe the phone, put the rom (and opengaps ?). And finally flash the rom. But previously I saw a lot of commands and warning so I'm a bit confused ?
Thanks for your attention ??
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