hello, my miA3 was in V10.3.17.0.PFQEUXM, and i had some troubles with it after trying to root with magisk because of a wrong boot.img, and i lost wifi.
since I couldn't find a V10.3.17.0.boot.img to flash and get back wifi, i try to find some escape plan and finally i succeed to install twrp and then official V11.0.8.0 , but i would like to go back to V10.3.15.0 and root it ( or 10.3.17.0 if someone have the good boot.img ), is it possible?
Just download fastboot rom and you are good to go
arjo656 said:
hello, my miA3 was in V10.3.17.0.PFQEUXM, and i had some troubles with it after trying to root with magisk because of a wrong boot.img, and i lost wifi.
since I couldn't find a V10.3.17.0.boot.img to flash and get back wifi, i try to find some escape plan and finally i succeed to install twrp and then official V11.0.8.0 , but i would like to go back to V10.3.15.0 and root it ( or 10.3.17.0 if someone have the good boot.img ), is it possible?
Click to expand...
Click to collapse
If you want to keep your sensors and DRM working, follow this guide:
https://forum.xda-developers.com/showpost.php?p=82110807&postcount=224
amnher said:
Just download fastboot rom and you are good to go
Click to expand...
Click to collapse
ok,do you have a link with DL and tuto step by step?
_mysiak_ said:
If you want to keep your sensors and DRM working, follow this guide:
https://forum.xda-developers.com/showpost.php?p=82110807&postcount=224
Click to expand...
Click to collapse
thanks (again ) mysiak, the steps are clear but there is no link for dl any of the rom he's talking
edit : i downloaded a rom 10.3.15.0 here https://forum.xda-developers.com/mi-a3/how-to/rom-xiaomi-mi-a3-laurelsprout-t3962489, but when i double click on flash_all.bat nothing happends
arjo656 said:
thanks (again ) mysiak, the steps are clear but there is no link for dl any of the rom he's talking
edit : i downloaded a rom 10.3.15.0 here https://forum.xda-developers.com/mi-a3/how-to/rom-xiaomi-mi-a3-laurelsprout-t3962489, but when i double click on flash_all.bat nothing happends
Click to expand...
Click to collapse
Run the script from terminal window, it will show you an error message why it fails.
arjo656 said:
hello, my miA3 was in V10.3.17.0.PFQEUXM, and i had some troubles with it after trying to root with magisk because of a wrong boot.img, and i lost wifi.
since I couldn't find a V10.3.17.0.boot.img to flash and get back wifi, i try to find some escape plan and finally i succeed to install twrp and then official V11.0.8.0 , but i would like to go back to V10.3.15.0 and root it ( or 10.3.17.0 if someone have the good boot.img ), is it possible?
Click to expand...
Click to collapse
Guys, I did the update for android 10 in the second wave.
after trying to return to android 9 my device got stuck resetting the "android one" home screen, as there was no solution i put the "pixel" rom for mi a3.
Today as a test again I tried to flash the rom stock 9 and everything went back to normal as it was before, with everything working.
I believe that after installing "PIXEL" something made it back to normal.
alexjmachado said:
Guys, I did the update for android 10 in the second wave.
after trying to return to android 9 my device got stuck resetting the "android one" home screen, as there was no solution i put the "pixel" rom for mi a3.
Today as a test again I tried to flash the rom stock 9 and everything went back to normal as it was before, with everything working.
I believe that after installing "PIXEL" something made it back to normal.
Click to expand...
Click to collapse
yes , that's what sapper morton explained in a other post:
" I received Android 10 as an OTA 29th February, and a couple of days later I updated to v11.0.8.0 (locked bootloader); but I didn't enjoy it overall, so I did install Magisk, after a couple of days, I downgraded to Pie (March firmware); I lost my sensors, did try a couple of things, none of them solved the issue.
I knew from the beginning I could have flashed persist.img, but then again, I would've lost my DRM Keys (Widevine), thus I updated to Android 10 Stock (recovery firmware) to regain my sensors.
After a little search I read that downgrading from a custom Android 10 ROM (PX in my case) solves the issue on Pie, I tried and the sensors started working again on Android 9 Stock, without losing Widevine L1, since persist partition was intact. "
So my steps to solve the issue was as it follows:
1• Flashed Android 10 Stock (sensors working) [Recovery]
2• Flashed Android 9 Stock (sensors not working) [Fastboot]
3• Flashed Android 10 custom (sensors working) [Recovery]
4• Flashed Android 9 (sensors working) [Fastboot]
hello all
is there any download link to "3• Flashed Android 10 custom (sensors working) [Recovery]" or do you recommend a specific custom rom ?
I want to do the downgrade right
Related
Hello fellow xda members helpers and developers
I need to downgrade my Phone from Android 7 Build: C432B370 to Android 6
What do I need to make sure of in my Huawei P9 Lite Android 7 Emui 5 before following the Rollback/software upgrade procedure described in the respective Zip files.
Do I need to unroot and relock ? .. If yes which version of recovery or TWRP do I need.. if I am going to rollback.
I am a little hesitant at the moment becouse I managed to get into a bootloop yesterday by just flashing recovery_stock .
I am guessing it is becouse I unawarely flashed the wrong recovery_stock(?)
Recovery/Fastboot mode were not availiable - and then tried to flash the rollback via 3 button method.. which of course did not work.
( In case you are wondering how I managed to fix this: I let the battery drain to 0% - this broke the loop - afte the fifth try I managed to reset it with volume up + power all the way through booting)
So now I am back to square one..
Thank you
ok so I managed to fix this by myself: The problem I had was, I had a corrupted/wrong recovery on my Android 7.
So what I did was, I checked which build I excactly had .. in my case C432B370 ... downloaded the full rom. Extracted the stock recovery.img with "HuaweiUpdateExtractor" and flashed it.
Then I did the normal rollback procedure with both update.app files.
Had to unlock and root it once more... ( this time with the correct twrp) and voila it works.
So what do we learn?: dont trust simple internet guides if they not offer informations on file versions they offer ... they may not use the correct versions for your phone.
thrad can be closed or deleted
thanks for looking
Hi, i have new honor 9, as i open the phone , it is upgrade to B183 Version.
i need to automatic call recorder and i have found a zip.file to flash whit twrp. So i want install twrp and root...
The first time i download TWRP 3.1.1-1 and Supersu 2,82, i install all whit my zip file per automatic call recorder...
all is ok, twrp, i have root and call recorder working,,, but...
I lose navigation buttons and Camera Flash.
for navigation buttons isnt a problem... i can use only Home button ( i had a Meizu phone before but...
I need camera flash ! it have to work.
so....
for have again all working , i used the Rebrand Guide of HWOTA, whit B120 all work again.
cannot have more OTA upgraded but i think because i just had download them whit my imei.... ok i will wait new update for verifyng it.
I can use Finder Firmware Huawey for have manual upgrade.
Now i'm again in b183.
how can I do now for have a valid twrp or valid method for root phone? Because i read that same people have them..... but i think have reroll to b120 almost 50 time whithout always same results....
oh oh, i see now that i have wrong section. moderator can you move?
SOLVED!
After many time i can have all working now:
Starting to B183 firmware whit button and flash not working:
Step 1) Rollback on B120, downgrading by flashing with hwota scripts, this post . option are 2 (directory upgrade) and 1 (same brand). with this you will have working buttons
Step 2) Update to B183 (FF full-ota files timestamped 2017.12.28)
Step 3) Unlock the bootloader.
Step 4) Install the TWRP-3.1.1.1_120_130_170.img from this thread.
Step 5) Install Supersu SR5
WARNING: you have to be carefull when go in TWRP recovery: do not modify system data at twrp's boot, then rebooted choosing not to install twrp at twrp's exit prompt. ( dont'know if it is important... but so it work
so you will have a b183 firmware whit all working: root, button and flash.
please, reply if this work for you.
Add more infos about FF .
In updater system , no update available after roolback to B120.
Need to use Firmware Finder Huawei on Playstore.
1-Choose the desired full version
2-Check Firmware access for be sure not make mistakes.
3-Get an update throught DNs , register update and change Dns .
4- Come back to updater and check update .
angelobiz said:
Step 2) Update to B183 (FF full-ota files timestamped 2017.12.28)
Click to expand...
Click to collapse
In this step, did you do it with the HWOTA tool or with fully stock B120 inside the system?
Zuzler said:
In this step, did you do it with the HWOTA tool or with fully stock B120 inside the system?
Click to expand...
Click to collapse
While on stock B120 use the android application Huawei Firmware Finder to upgrade:
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146/amp/
But you could try to test to use HWOTA to upgrade from b120 to b183 and then report here?
I already tried upgrading to B182/183 with HWOTA. I was on B120 and did a B182 and B183 upgrade. I was left with no capacitive keys and no flash. Camera was working however.
Just right now downloading B183 on top of a new locked B120 with the Firmware Finder, will report back.
However, it's very inconvenient to update the system this way if you have an unlocked bootloader and are rooted. I mean, downgrade to B120, twice within HWOTA, upgrade within the system and then AGAIN re-unlock the bootloader which results in a factory reset - come on...
Does it also work with Magisk or only with SuperSu?
SuperSu already is nice, but the additional benefits like would be nice to have, especially passing SafetyNet.
Anyone still with missing navigation buttons? I might have a solution that does not require flashing firmware or doing factory reset
zxz0O0 said:
Anyone still with missing navigation buttons? I might have a solution that does not require flashing firmware or doing factory reset
Click to expand...
Click to collapse
Mind telling us?
For me everything worked fine by downgrading to B120 and then updating B183 through the OS.
Zuzler said:
Mind telling us?
For me everything worked fine by downgrading to B120 and then updating B183 through the OS.
Click to expand...
Click to collapse
Seems the problem is that the touch_key firmware is not flashed properly. I modified the TWRP recovery to include the firmware. After I rebooted once into the custom TWRP the buttons worked again.
zxz0O0 said:
Seems the problem is that the touch_key firmware is not flashed properly. I modified the TWRP recovery to include the firmware. After I rebooted once into the custom TWRP the buttons worked again.
Click to expand...
Click to collapse
Good. This might be a breakthrough. Could you please share a step by step guide what to do? Thanks.
zxz0O0 said:
Seems the problem is that the touch_key firmware is not flashed properly. I modified the TWRP recovery to include the firmware. After I rebooted once into the custom TWRP the buttons worked again.
Click to expand...
Click to collapse
good, can you share your modified TWRP recovery???
the solution not work if you do different. you have to downgrade to B120 to HWOTA whit file of its post. After have to upgrade to B183 whit FFH whit locked bootloader
ang stock recovery, after install twrp and supersu.
i dont know why, but so it work.
angelobiz said:
good, can you share your modified TWRP recovery???
the solution not work if you do different. you have to downgrade to B120 to HWOTA whit file of its post. After have to upgrade to B183 whit FFH whit locked bootloader
ang stock recovery, after install twrp and supersu.
i dont know why, but so it work.
Click to expand...
Click to collapse
It would be a good thing.
Edit : As we are all trying to make your device 100% functional with root.
Here is a link for a Su Emui , not testes yet. Work on the mosty Huawei devices
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
http://www.mediafire.com/file/pn2pv1rqih1ug81/SuperSU-v2.82-EMUI5-SELPermissive[1].zip
https://androidfilehost.com/?fid=673956719939815322
I had used this version and it work
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
zxz0O0 said:
Seems the problem is that the touch_key firmware is not flashed properly. I modified the TWRP recovery to include the firmware. After I rebooted once into the custom TWRP the buttons worked again.
Click to expand...
Click to collapse
Can you provide details?
I wonder if we can pull the touch_key firmware from a working B120 firmware and flash over a later version?
angelobiz said:
I had used this version and it work
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
Now i'm ok .
I used the good twrp and sideloaded Supersu.sr3 .
All buttons and flashlight work nice
zxz0O0 said:
Seems the problem is that the touch_key firmware is not flashed properly. I modified the TWRP recovery to include the firmware. After I rebooted once into the custom TWRP the buttons worked again.
Click to expand...
Click to collapse
So did your twrp fix touch_key once broken?
zxz0O0 said:
Seems the problem is that the touch_key firmware is not flashed properly. I modified the TWRP recovery to include the firmware. After I rebooted once into the custom TWRP the buttons worked again.
Click to expand...
Click to collapse
Can you please share your modified TWRP recovery, so we can test on our phones?
This issue is driving me crazy.
Thanks :good:
Hello,
I write to tell you about my problem with a rear camera of my Huawei Y6 [SCL-l01][C432B140] and ask for any possible help. I really like to use it and i tried to get it back, but even after back to my firmware and stock recovery my camera doesn't work anymore[You cannot connect to the camera] after first rom flash.
Let's start from begining:
Once i decided to install custom rom on my phone, i done everything like it was on tutorials. I unlocked bootloader, i backup my data and i flash TWRP 3.1.2. Of course, TWRP didn't shown any error or issues, but my backup after restore, cause bootloop of my device and after second reboot startin recovery[not even bootloader of OS].
I tried many fixes to get my camera working on Custom Roms like AOSP, DARKNESS, CM,[ and few from HUAWEI Y6 thread] and I always fails. After few tries i gave up. My problem was that my backup was broken and my recovery was flashed by TWRP. Lucly i found stock recovery for my phone and flashed it.
Stock recovery gave my chance to install my stock rom from UPDATE.app, but after i install my stock lolipop 5.1 - my camera won't work anymore.[Can't connect to the camera, flashlight doesn't work too].
I tought to myself "hell, it could be problem that my original soft is modificated", but luckly i had two smartphnoes of my type SCL-l01[not mine ]. I took copy of working one by TWRP and flash it to my doesn't working... It gave the same result [I used TWRP by fastboot boot twrp.img for survive of my stock recovery] - camera simply wasn't work anymore even after flash the same firmware [once from update.app and second from another scl-l01]
And there is my question - Is it possible to get this camera working again?
Just pls - don't write to my about basics like clear cache or force stop etc , becouse i tried it all.
Thanks for every answer - and sry for my mistakes in my statement.
have the same problem for quite some time, I tried to return to stock with the update.app and the camera no longer worked, and I did not find a way to make the camera work. In stock it does not work, and in ROMS as LineageOS either, eh done the same thing to reinstall the update.app and neither, I think it could be a hardware problem
I clarify, I have a SCL-L03
link plzz
i ccant find the oficial room for scl-l01 cen you guys give me the link:cyclops::crying::crying::crying::crying::crying:
WantedG said:
i ccant find the oficial room for scl-l01 cen you guys give me the link:cyclops::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
http://huawei-firmware.com/rom/huawei-y6/scll01/1194
If you want to flash it, use huawei updater extractor and extract the system.img and boot.img from the update.app and flash it from fastboot.
Or if you have stock recovery make an folder Dload in sdcard and put the update.app here. After that, press power button and volume up and down (your phone needs to be shutdowned)
That's it.
Thanks button works well if I helped
Hi,
My favourite phone is the Xiaomi Redmi note 3 Pro SE with Lineage OS 13 (Yes marshmallow).
I got a new one that was in endless bootloop and I planned to get it working.
I don't know if the bootloader has been unlocked and how (last time I checked it was written locked), if a custom ROM as been flashed or anything that could been done on it before I get it.
After many tries I first succeed to install LineageOs 13 on it, what I remember:
I go to fastboot mode
I go to edl mode
I flashed it with an old MiFlash 2016.04.01.0 64 bit with an old official ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_global_9aa2d85137 with recovery.img replaced by an old ZXC-TWRP 3.0.2-X. (This is the way to get a recovery with no need to unlock bootloader)
I started it directly to TWRP recovery mode (to be sure TWRP will stay it I guess?) changed the language and checked OTA checkbox in parameters
I started this old official ROM once (to get the full storage capacity)
I discovered it was a 16GB ROM / 2GB RAM version instead a 32GBROM / 3GB RAM I previously knowed
I restarted to TWRP recovery mode
I wiped david/cache
I flashed the last knowed LineageOS 13 for this phone: https://forum.xda-developers.com/re...ageos-13-0-t3533744/post83687823#post83687823
I wiped david/cache
I flashed the last radeon kerned on it
I wiped david/cache
I restarted it to LineageOS 13
I restarted to TWRP recovery mode, changed the language and checked OTA checkbox in parameters
I flashed magisk (sytemless)
I wiped david/cache
I restarted it to LineageOS 13
I could use it install a lot of things, was happy with it
Before succeeding I tried a lot of combinations of official ROM/TWRP/MiFlash versions and this couple was the only one working.
Other MiFlash versions don't detect the phone in edl mode
But 2 weeks later, just after installing a new app, the phone sudently reboots and I got stuck in bootloop again...
I could go to recovery one time, I selected reboot system, now I can't go to recovery anymore
I still can go to fastboot mode and edl mode, and I can flash a ROM, but whatever I flash I can't go away from bootloop.
What could the new bootloop come from?
Is my installation sequence good?
Why only this combination of official ROM/TWRP/MiFlash versions was working?
Why can't I start a ROM anymore after a new flash?
Why can't I go to the recovery anymore after a new flash?
How to check if the emmc memory is defective (I got no error while flashing)?
Thanks for reading, hope someone still cares on this old great phone
Sorry for my bad English
No clue what the problem may be. What app did you install? You could always try to go back to stock if you haven't already. Basically wipe phone completely and flash stock through mi flash.
JD. A said:
No clue what the problem may be. What app did you install? You could always try to go back to stock if you haven't already. Basically wipe phone completely and flash stock through mi flash.
Click to expand...
Click to collapse
Thanks for your answer.
The last app before bootloop was a sms/mms backup app on google store I get through Aurora.
I tried to flash the stock ROM (old one) kate_global_images_6.9.29_20160805.0000.29_6.0_glo bal_9aa2d85137 but it doesn't start, always bootloop.
I have no option to wipe on the only miflash version that detect my phone in edl : the 2016.04.01.0 64 bit version. so I choose flash all data/storage include, but still bootloop.
Why are you using such a old rom? Use latest miflash and latest global. On the bottom right of miflash you should have something like clean and lock. Just note that if you're unofficially unlocked you'll need to apply for unlock or unlock unofficially again.
JD. A said:
Why are you using such a old rom? Use latest miflash and latest global. On the bottom right of miflash you should have something like clean and lock. Just note that if you're unofficially unlocked you'll need to apply for unlock or unlock unofficially again.
Click to expand...
Click to collapse
Other Miflash version don't detect my phone when it is in edl mode
I could start other stock rom, I know tried this ones:
kate_global_images_7.6.8_20170608.0000.00_6.0_global_2040bd5a39
kate_global_images_8.12.13_20181213.0000.00_6.0_global_304fc0692b
But I couldn't flash my LineageOS 13 + recovery with those.
I tried so much combinations TWRP/Stock rom, I don't remember what I tested.
I just know the MiFlash 2016.04.01.0 64 bit with an old official ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_glo bal_9aa2d85137 with recovery.img replaced by an old ZXC-TWRP 3.0.2-X. was the only one combination that worked for me for installing LineageOS 13 + recovery working
Now, every time I try to flash something (whatever it is) it goes to bootloop...
Only fastboot and edl mode are working
If you have other links / combinations I would be happy to try
ROUGE13 said:
Other Miflash version don't detect my phone when it is in edl mode
I could start other stock rom, I know tried this ones:
kate_global_images_7.6.8_20170608.0000.00_6.0_global_2040bd5a39
kate_global_images_8.12.13_20181213.0000.00_6.0_global_304fc0692b
But I couldn't flash my LineageOS 13 + recovery with those.
I tried so much combinations TWRP/Stock rom, I don't remember what I tested.
I just know the MiFlash 2016.04.01.0 64 bit with an old official ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_glo bal_9aa2d85137 with recovery.img replaced by an old ZXC-TWRP 3.0.2-X. was the only one combination that worked for me for installing LineageOS 13 + recovery working
Now, every time I try to flash something (whatever it is) it goes to bootloop...
Only fastboot and edl mode are working
If you have other links / combinations I would be happy to try
Click to expand...
Click to collapse
This is a little bit to late to the party but the latest both dev rom and global works for me with the latest me miflash. No problems what so ever. Seems like you're facing a hardware issue.
JD. A said:
This is a little bit to late to the party but the latest both dev rom and global works for me with the latest me miflash. No problems what so ever. Seems like you're facing a hardware issue.
Click to expand...
Click to collapse
Hi,
No, not too late my phone is still waiting, so thanks for your answer
Could you tell me witch version of rom / tool did you use?
I will try on a other windows computer to be sure there is no conflict with old tools I installed before.
If it works I will flash CM13 (marshmallow), I thought I should not use a too recent dev/global ROM before flashing CM13, but I don't remember were I read this. Is this true?
ROUGE13 said:
Hi,
No, not too late my phone is still waiting, so thanks for your answer
Could you tell me witch version of rom / tool did you use?
I will try on a other windows computer to be sure there is no conflict with old tools I installed before.
If it works I will flash CM13 (marshmallow), I thought I should not use a too recent dev/global ROM before flashing CM13, but I don't remember were I read this. Is this true?
Click to expand...
Click to collapse
I'm not home this weekend so I can't say for sure. gismoZ recommends using the 8.0.2 firmware or something like that can't remember, but the latest works just fine on my kate. The latest miflash is from 20200314 and just get the latest global rom and try to flash it.
I tried with an other windows computer, I successfully used last MiFlash version
But now, whatever I flash, ROM version or recovery version, it stay in bootloop when I power it.
I expect the eMMC memory to be faulty but why doesn't I have any error while flashing?
How to be sure this comes from the eMMC chip?
Some people have successfully changed it on the mediatek version of the phone:
https://fr-fr.facebook.com/16816505...c-kmvtu-done/1821360108117225/?_fb_noscript=1
https://translate.google.com/transl.../03/service-hp-xiaomi-redmi-mi-note-mati.html
If I go on this solution I have some questions before:
Must the eMMC chip be programmed before soldering it?
If not, can I program it with MiFlash once soldered?
If not, have I to use some special touch/contact on the mainboard to program it?
How to be sure of the chip model to buy?
Will the chip come already balled? Or have I to ball it before soldering it on mainboard?
Could I buy a 32GB chip instead 16GB original one?
Something else to test before going on this crazy last chance solution?
I bought a EDL flash cable, but I think I don't need it on this phone, I alway success to go to EDL mode from fastboot mode with a small batch script.
Hello ,
Any chance I could get an answer anymore or is my problem too specific maybe?
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