I've been trying 8.1 roms for a week and I was ok with Bootleggers rom, till i found that bluetooth was not working properly. After that, I tried another rom (AOSP Extended) but I found that the camera was missing. Since that happened, every 8.1 rom that I flash, has no camera. What could it be? Or What should I do?
-I do clean flashing with every rom. (Wipe data, cache, davlink/art cache, system).
-I tried miui 10 (Android 6.0.1) Mi globe, and the camera is working normaly. (Just to make me sure that I wasn't a hardware problem).
-I have ecrypt password for booting android and TWRP (It was set since the first 8.1 rom that I flashed).
-I use the latest nano gapps.
Camera doesn't work with encrypted data. Decrypt (wipe) or use 7.1
THANK YOU A LOT, my camera randomly stopped working and i was wondering why then i got to your thread and by getting to miui10 camera works again.
Dnxss said:
I've been trying 8.1 roms for a week and I was ok with Bootleggers rom, till i found that bluetooth was not working properly. After that, I tried another rom (AOSP Extended) but I found that the camera was missing. Since that happened, every 8.1 rom that I flash, has no camera. What could it be? Or What should I do?
-I do clean flashing with every rom. (Wipe data, cache, davlink/art cache, system).
-I tried miui 10 (Android 6.0.1) Mi globe, and the camera is working normaly. (Just to make me sure that I wasn't a hardware problem).
-I have ecrypt password for booting android and TWRP (It was set since the first 8.1 rom that I flashed).
-I use the latest nano gapps.
Click to expand...
Click to collapse
Please download GCMOD5
Related
Hi,
yesterday i went through the process of flashing custom rom and i just want to share my experience.
My daily driver was the latest MIUI7 because it was very stable and battery life was good (stock global stable, locked bootloader). But i decided to try custom rom mainly because i had strange performance issues every now and then.
1. Applied for official unlock - Unlock Page
2. I read many posts and i tought it might be best to upgrade to MIUI8 first. I updated with the official updater app.
3. Unlocking didnt work because you need a Developer Rom of MIUI installed to link the device to you Mi account and successfully unlock. I downloaded latest global dev rom and flashed with official updater app.
4. Unlocked successful with official Mi Unlock Tool.
5. Installing TWRP ZCX - worked and was easy
6. Backup System, Data, Firmware, Modem with TWRP (didnt need it so far)
7. Flash Nitrogen OS
8. Reboot to system - "to start android enter password" - surprised and shocked so i googled and found a hint to "format data" because storage might be encrypted.
9. In TWRP - Wipe i "formated data" so all files were deleted! be sure to backup everything!
10. Nitrogen OS booted (no need for Gapps - everything is built in)
11. Flash fingerprint fix - apparently i have the Goodix and need this fix for fingerprint to work
12. I was confused because there was no caller app (call worked but no UI) so i flashed new and again and tried Psy Firmware but i just had to set the caller app in settings.
13. All is working good so far :fingers-crossed:
Thanks for all the work done by this community. I greatly appreciate all the cool stuff! :highfive:
EDIT: I have FPC sensor not Goodix. The fix is for FPC! Thanks to @Denis:) for pointing that out.
You are wrong on some points ;p
Its so easy to flash roms on all snapdragon devices
Theres a need for gapps, it doesnt come preinstalled on roms, which is a good thing.
If you flashed fpc fix and it works now, it means you have FPC sensor, not goodix (which is good -like me), dev of NOS will make fpc default from now on.
For next time, you need to format data when you come from Miui MM, because it encrypts data by default.
Also I suggest formatting data,cache to F2FS, it actually makes it even faster a bit imo, but ita not a must.
Denis:) said:
For next time, you need to format data when you come from Miui MM, because it encrypts data by default.
Also I suggest formatting data,cache to F2FS, it actually makes it even faster a bit imo, but ita not a must.
Click to expand...
Click to collapse
I have installed LineageOS several times over MIUI but I didn't need to format data. Why does this happen in nitrogen os, any idea?
Denis:) said:
...
Click to expand...
Click to collapse
The level of difficulty may be different for different people
I flashed NitrogenOS and Gapps but then did a wipe and flashed only NiOS but in the end i had all the Google apps... Maybe this part didn't get wiped - Thanks for pointing that out.
Right, FPC sensor - my mistake
The encryption thing was confusing because there is not much info on that topic here - especially the guides. Thanks for confirming this is a thing.
This F2FS format thing is done in TWRP?
If you didnt wipe system aswell, gapps and ROM persisted.-dirty flash (update ROM)
If you want to update ROM + gapps, you must wipe System aswell with dalvik/art, cache
Then flash ROM+gapps , wipe cache and reboot
F2FS is done in twrp but you must have f2fs compatible twrp - I successfuly use rc1 latest by TheStrix, obviously if you choose to format data, cache you will lose data and you will have to clean flash ROM.
P.s By the way, when was your device made? Im just curious
funkymaster said:
The level of difficulty may be different for different people
I flashed NitrogenOS and Gapps but then did a wipe and flashed only NiOS but in the end i had all the Google apps... Maybe this part didn't get wiped - Thanks for pointing that out.
Right, FPC sensor - my mistake
The encryption thing was confusing because there is not much info on that topic here - especially the guides. Thanks for confirming this is a thing.
This F2FS format thing is done in TWRP?
Click to expand...
Click to collapse
If you want to experiment please try to format the partitions using f2fs and tell us your results.
I tried it but was unsuccessful since when I tried it there was no recovery that could support f2fs. Remember only dadii's TWRP works still I recommend you confirm it again.
Im using this one by thestrix and it works perfect;
https://www.androidfilehost.com/?fid=529152257862707658
currently i don't feel like tinkering with my phone any more. So i keep the F2FS in mind for some time in the future
Hm i don't know where to find the build date of my phone i bought it April 2016
Hi,
I've got a RN3, snapdragon version, 3GB of RAM. Unlocked bootloader. TWRP 3.0.2-2
I've been using CM for a while, android 6.0.1 and I've been trying now for a few days to move to Nougat.
I've tried different roms: NitrogenOS, lineage OS, resurrectionRemix.
I've also tried flashing different versions os miui firmware: 7.3.16, 7.3.23, 7.3.30
So, after all that, the result is always the same. The flashing seems successful, the phone boots but then I cannot go through the initial setup screen.
I choose the wifi network but when I try to enter the password, the screen resets every 5 seconds or so. I know it's resetting/reloading because the password I've typed so far goes away and I have to start again. It happens every few seconds and I cannot setup wifi properly.
I tried changing the password to aaaaaaaaaa to make it easy and quick to setup. Once I go through that, it stays for ever in the next screen "checking information" (or something like that). Again, it seems to be reloading this screen every few seconds.
is there something am I missing? Maybe I'm flashing firmware/rom in the wrong order?
I'm back with android 6.0.1 now and the phone works fine.
thanks in advance for your help.
Flash Kenzo Firmware , Rom & Nougat Gapps not MM , next reboot system
Sent from my Redmi Note 3 using Tapatalk
VaibhavKumar07 said:
Flash Kenzo Firmware , Rom & Nougat Gapps not MM , next reboot system
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
thanks @VaibhavKumar07
so, this is exactly what I've tried a few times.
what about wipes and all that stuff?
I don't mind doing a clean install and reinstalling/reconfiguring everything.
I've tried different things, but for example what is mentioned in the thread "CM13/14/14.1/AOSP N firmware for KENZO/KATE [VoLTE][12.1.2017]"
-Reboot to TWRP recovery
-Flash firmware
-Factory reset (data, cache and dalvik-cache)
-Flash your favorite Marshmallow or Nougat ROM
-Reboot your phone
is that still valid for the nightly builds from April 2017?
On Cm firmwares I was unable to get VoLTE working so recommend you to flash Miui beta firmware search in SD Rom or guide section you'll find em if not message me again .
Regarding procedure :
- First flash Twrp 3.1.1.0 from official site cuz that's latest
- Next go & wipe check everything except SD card & OTG
- Flash Firmware
- Flash Rom
- Flash Gapps Arm *64 Android N from Open apps
- Flash Any Add-ons if required like kernel or Sound enhancement mods ( optional )
- Clean cache/dalvik cache
- Reboot
Mention the Rom you're flashing!
Sent from my Redmi Note 3 using Tapatalk
So, I did all that several times, except for flashing the latest twrp version. I'm on 3.0.2-2 because it flashes ok but when rebooting it's back to 3.0.2-2. I'm doing this from fastboot. I'm not only loading, but flushing. It seems to be ok but then it's gone after reboot.
Anyway, I've tried this procedure with 3 different roms:
ResurrectionRemix
LineageOS
Nitrogen OS
flashing latest versions for each rom.
Could the twrp not updating properly have something to do with this issue? does the latest version fix some flashing issues with Nougat?
the thing is that if flashed and boots, but it doesn't run properly as mentioned.
I will try to get latest twrp version working and report back if that makes any difference.
VaibhavKumar07 said:
On Cm firmwares I was unable to get VoLTE working so recommend you to flash Miui beta firmware search in SD Rom or guide section you'll find em if not message me again .
Regarding procedure :
- First flash Twrp 3.1.1.0 from official site cuz that's latest
- Next go & wipe check everything except SD card & OTG
- Flash Firmware
- Flash Rom
- Flash Gapps Arm *64 Android N from Open apps
- Flash Any Add-ons if required like kernel or Sound enhancement mods ( optional )
- Clean cache/dalvik cache
- Reboot
Mention the Rom you're flashing!
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
so, still fighting with this.
i managed to upgrade to twrp 3.1.0-1, all good.
however, i still have the same problem with the initial screen, it keeps reloading every few seconds and can't finish the setup or even skip it.
i've tried different versions of firmware. I've also tried flashing the latest miui rom (dev and global) and then a custom rom.
i've tried different builds (different dates) of the following roms:
nitrogenOS
lineageOS
aospextended
mokee
resurrectionremix
exact same behaviour with all these roms.
what am I doing wrong? i'm on marshmallow and everything works fine, but stuck moving to nougat. do I have to flash something not mentioned already to move from custom MM to custom Nougat?
txutxe said:
so, still fighting with this.
i managed to upgrade to twrp 3.1.0-1, all good.
however, i still have the same problem with the initial screen, it keeps reloading every few seconds and can't finish the setup or even skip it.
i've tried different versions of firmware. I've also tried flashing the latest miui rom (dev and global) and then a custom rom.
i've tried different builds (different dates) of the following roms:
nitrogenOS
lineageOS
aospextended
mokee
resurrectionremix
exact same behaviour with all these roms.
what am I doing wrong? i'm on marshmallow and everything works fine, but stuck moving to nougat. do I have to flash something not mentioned already to move from custom MM to custom Nougat?
Click to expand...
Click to collapse
Try this once (Clean) :
Flash Nitrogen
Reboot
Flash gapps and firmware.
Hope it may work for you.
Hey guys,
Googe play services keeps stopping
android.process.media keeps stopping
bluetooth keeps stopping
at the first start (google register)
I tried: 2 different roms: mcaosp + pixel, newest gapps (nano), flashed data, cache, dalvik + system
Do you have any solutions/ tipps? I want to try pie
Greetings
I had this problem too, tried all variants of gapps, bitgapps. All variants of twrp, all pie ROMs and same error. You can try and see that if you create a second user in the phone, suddenly all works perfectly.
tl;dr:Just try crdroid ROM, the one worked for me on the owner user
Flash the ROM first without gapps then boot normally.Turn off phone,go to TWRP and then flash GAPPS.
Had this issue many times and its quite annoying.
Thanks for the answers. I tried this 2 times ;(
It just dont work with your tipps. I will go back to oreo until I get news about this
no fix yet ;/
Flashed all except usb otg + sd card, installed firmware 9.6.2 and tried syberia + arrow rom. (Followed the install tutorials)
Android PIE dont like me ;(
EDIT: Got AOSP Extended to work but now it searches for updates since 10 minutes. (I have good wlan <.<)
Hi. I bought a Pocophone last February. Since then, the phone keeps randomly rebooting and shutting down. I have flashed EU roms, Global & Beta fastboot roms, OTA roms, custom roms etc. But the random reboot problem was persistent through out all roms.
I flashed the latest Pixel Experience CAF rom a few days ago, along with DFE and latest vendor. The phone has not been rebooting and the experience and smoothness was very good, apart from some force crashes in some apps. I flashed the EU rom after the random rebooting was stopped, thinking that may be the problem was solved in a vendor update. Sadly, the issue persists in MIUI rom. So I flashed back to PE.
Now my question is, why is my phone rebooting in MIUI? How was this solved in a PE build? Am I missing something, like a particular step, when flashing a rom? I have searched through a lot of XDA posts but can not find a proper solution. I would like to use eu versions of MIUI as I have been a Nexus and Android One user since Nexus 4 days and now crave something other than plain stock android.
Also, I bought the phone without warranty through an unofficial local store and returning the phone to Xiaomi for checking hardware defects is not possible.
The steps I follow in TWRP is usually:
1. format data, 2. reboot to recovery, 3. wipe cache, dalvik cache, system, data, 4. flash vendor, 5. flash rom, 6. flash DFE, 7. flash gapps, 8. flash magisk, 9. reboot to system
yowlzany said:
Hi. I bought a Pocophone last February. Since then, the phone keeps randomly rebooting and shutting down. I have flashed EU roms, Global & Beta fastboot roms, OTA roms, custom roms etc. But the random reboot problem was persistent through out all roms.
I flashed the latest Pixel Experience CAF rom a few days ago, along with DFE and latest vendor. The phone has not been rebooting and the experience and smoothness was very good, apart from some force crashes in some apps. I flashed the EU rom after the random rebooting was stopped, thinking that may be the problem was solved in a vendor update. Sadly, the issue persists in MIUI rom. So I flashed back to PE.
Now my question is, why is my phone rebooting in MIUI? How was this solved in a PE build? Am I missing something, like a particular step, when flashing a rom? I have searched through a lot of XDA posts but can not find a proper solution. I would like to use eu versions of MIUI as I have been a Nexus and Android One user since Nexus 4 days and now crave something other than plain stock android.
Also, I bought the phone without warranty through an unofficial local store and returning the phone to Xiaomi for checking hardware defects is not possible.
The steps I follow in TWRP is usually:
1. format data, 2. reboot to recovery, 3. wipe cache, dalvik cache, system, data, 4. flash vendor, 5. flash rom, 6. flash DFE, 7. flash gapps, 8. flash magisk, 9. reboot to system
Click to expand...
Click to collapse
If you really want a miui base I suggest following instructions on say how to install xiaomi.eu which says "FORMAT /data partition (NEVER wipe System or Persist!)"
Start of with a clean miui base installed using fastboot and after that do the following,
1.install twrp or orange fox (any that supports decryption)
2. format data
3. reboot to recovery
4. flash rom, reboot.
5. Setup device, reboot.
6. Flash magisk. Reboot
7. Never ever flash fde/fed just throw that zip in the trash.
8. Do what ever you like, miui is working for you
9. Buy me a beer.
Sent from my POCOPHONE F1 using Tapatalk
Hi, I've recently repaired my mido with a new screen after a fall. After this I tried some custom roms. Initially I managed to install lineage 18.1. After I switched to dotOS. From this point on, the phone restarts a few seconds after the launcher appears. To fix this I used MiFlah to install latest MIUI, formatted data, wiped everything, tried TWRP and Orangefox, tried other custom roms with no changes. Now only stock MIUI11 works. Other custom roms (included lineage) gets the phone continuously rebooting. Could be an hardware problem? What am I doing wrong? It is the first time in ages I have problems flashing ROMS .-.
Thanks.
gabritb01 said:
Hi, I've recently repaired my mido with a new screen after a fall. After this I tried some custom roms. Initially I managed to install lineage 18.1. After I switched to dotOS. From this point on, the phone restarts a few seconds after the launcher appears. To fix this I used MiFlah to install latest MIUI, formatted data, wiped everything, tried TWRP and Orangefox, tried other custom roms with no changes. Now only stock MIUI11 works. Other custom roms (included lineage) gets the phone continuously rebooting. Could be an hardware problem? What am I doing wrong? It is the first time in ages I have problems flashing ROMS .-.
Thanks.
Click to expand...
Click to collapse
The vendor partition could have some code/ file that persists stock ui or system
and make sure your phone was rooted before flashing custom rom
and also via twrp flashing. from what Ive seen flash in twrp before flash custom rom( https://www.google.com/search?client=firefox-b-d&q=disable+encryption+treble ) then flash the "verity and encryption disabler ,theres another one to re enable encyption only " then flash custom rom
after flashing custom rom reboot poweroff(switch phone off via twrp)
reboot into twrp and flash whatever else you need
now reboot to system and your phone should work fine
Thanks, it worked!
I did:
Flash last miui with miflash
Flash recovery
Flash you suggested zip
Format data
Flash lineage 17.1 (android10)
WIpe system, data, cache, art cache
Flash any android 11 ROM
gabritb01 said:
Thanks, it worked!
I did:
Flash last miui with miflash
Flash recovery
Flash you suggested zip
Format data
Flash lineage 17.1 (android10)
WIpe system, data, cache, art cache
Flash any android 11 ROM
Click to expand...
Click to collapse
Holy **** how did you come up with this.
Either the zip with Magisk somehow fixed it or installing the android 10 rom somehow. Either way doesn't make sense
flairepathos.info said:
The vendor partition could have some code/ file that persists stock ui or system
and make sure your phone was rooted before flashing custom rom
and also via twrp flashing. from what Ive seen flash in twrp before flash custom rom( https://www.google.com/search?client=firefox-b-d&q=disable+encryption+treble ) then flash the "verity and encryption disabler ,theres another one to re enable encyption only " then flash custom rom
after flashing custom rom reboot poweroff(switch phone off via twrp)
reboot into twrp and flash whatever else you need
now reboot to system and your phone should work fine
Click to expand...
Click to collapse
Didn't work for me,
- did all the steps , exactly - flashed stock fastboot , then flashed Android 10 based rom crDroid + pico gapps. worked fine for 2 hours or so .
but interesting enough , phone freezes then shutdown without restarting , then i would go and trun it back on , but fingerprint not working now
heroboy107 said:
Didn't work for me,
- did all the steps , exactly - flashed stock fastboot , then flashed Android 10 based rom crDroid + pico gapps. worked fine for 2 hours or so .
but interesting enough , phone freezes then shutdown without restarting , then i would go and trun it back on , but fingerprint not working now
Click to expand...
Click to collapse
i think somewhere in the process the persist partition gets damaged .
heroboy107 said:
i think somewhere in the process the persist partition gets damaged .
Click to expand...
Click to collapse
so if you have magisk you can use a zip file to chmod 744 or 644 (it may be "chmod root 744" )the /persist partiton and thatll mean only true root has access
so 7 is read write execute 6 is read and write 4 is read only 5 is read execute i forgot which number was execute only 1 maybe?
so play with the permissions or look in the root folder for boot.p or permissions.sh then you can modify in there the permissions, it can cause bootloop , so always keep an original copy or youll hae to reflash(DISCLAIMER)
so you can pull the file using adb+root / or a root explorer
Copy it to phone then edit then copy to SDCARD
reboot to twrp then use shell/terminal "chmod 777" the partition where the file is / or read write everything
then copy the file and overwrite the original