Related
i installed this rom
http://forum.xda-developers.com/showthread.php?t=2658344
i downloaded the official nightly and wiped system and data and installed gapps
everything works fine
but i don't have the camera app in my app-drawer
although i have it in system/app and i tried clicking on it and it reinstalled the camera but still it doesn't exist in my appdrawer!?
i have an LG p768 and i installed the camera patch but i don't know if it is compatible with CM11?!
also i wanted to say that i installed google camera and it said cannot connect to camera so i guess the patch did not work.
but i was just interested to know why the camera app did not show up in my appdrawer
also wanted to say that in one of the screenshots of the thread above you can see the camera shortcut in the homescreen (which i did not have when i flashed the rom)!!
repply
try with this patch, i always use it and works fine
hit thanks if solve your problem
squal59 said:
try with this patch, i always use it and works fine
hit thanks if solve your problem
Click to expand...
Click to collapse
thank you for your reply! but i already used this fix but it doesn't help
i don't why but i have this problem only in the Mokee rom. (other roms work fine and camera works perfect)
i installed the rom with the instructions then i installed supersu.zip and p768-camera.zip and booted the rom.
but no matter what i tried to do i can't see the camera in app-drawer.
i can see it in system/app and i even tried installing it (by clicking on it) and still nothing.
i really love this rom but i can't use my it without having the camera.
LSGio said:
thank you for your reply! but i already used this fix but it doesn't help
i don't why but i have this problem only in the Mokee rom. (other roms work fine and camera works perfect)
i installed the rom with the instructions then i installed supersu.zip and p768-camera.zip and booted the rom.
but no matter what i tried to do i can't see the camera in app-drawer.
i can see it in system/app and i even tried installing it (by clicking on it) and still nothing.
i really love this rom but i can't use my it without having the camera.
Click to expand...
Click to collapse
You have a unlocked bootloader?? If you had you don't need flash the zip for su access, come in the rom...maybe the cause of your error is for this, try wiping cache, dalvij cache, system and if you are in artas CWM, go to mount and storage and choose the last option named as "fotmat data and data media (storage/sdcard) this solved various problems for me, and reinstall without the su zip only the rom, gapps and the patch. Reboot and tell me
squal59 said:
You have a unlocked bootloader?? If you had you don't need flash the zip for su access, come in the rom...maybe the cause of your error is for this, try wiping cache, dalvij cache, system and if you are in artas CWM, go to mount and storage and choose the last option named as "fotmat data and data media (storage/sdcard) this solved various problems for me, and reinstall without the su zip only the rom, gapps and the patch. Reboot and tell me
Click to expand...
Click to collapse
no ! unfortunately it didn't work for me!
and also i don't think i have artas cwm cause i don't have the option you wrote (format data and data/media) so can you please give me a link to artas CWM and i'll try again. and yes i have an unlocked bootloader.
does artas recovery work on p768?
also i will try to install another kitkat rom to see if camera apears there or not.
P.S: thank you for your help
LSGio said:
no ! unfortunately it didn't work for me!
and also i don't think i have artas cwm cause i don't have the option you wrote (format data and data/media) so can you please give me a link to artas CWM and i'll try again. and yes i have an unlocked bootloader.
does artas recovery work on p768?
also i will try to install another kitkat rom to see if camera apears there or not.
P.S: thank you for your help
Click to expand...
Click to collapse
http://d-h.st/6j0
here is the link "credits of artas" for the CWM of artas, try flashing as a normal zip and reebot, you must be in artas cwm, if not work for you this way, then you need flash it trouhg ADB on fastboot, try it and tell me
squal59 said:
http://d-h.st/6j0
here is the link "credits of artas" for the CWM of artas, try flashing as a normal zip and reebot, you must be in artas cwm, if not work for you this way, then you need flash it trouhg ADB on fastboot, try it and tell me
Click to expand...
Click to collapse
just wanted to say that i tried another kitkat rom called "SOKP"
http://forum.xda-developers.com/optimus-l9/development/p760-765-768-t2812133/post54154388
and the camera worked there.
so i don't think that the problem is in the fix.
i'm gonna wait for an update to mokee rom and see if it fixes the camera.
I don't know what I did but I think it's really serious and important for me to be solved, that's why I am requesting for your help!
As I have reached the of Limit flashing ROMs over and over again, I came to the following occasion:
After casually flashing a new oreo based ROM, having installed also the Gapps, everything was fine for the time being. Suddenly when I tried to flash the magisk manager, from TWRP recovery it was saying that the installation had failed and that magisk failed to mount vendor(never before asked)!
I flashed one or two times stock ROM(miui 9), but I think that it might not be the proper one! For example, there used to be such a problem in the past, but when I slashed stoke MIUI 8 the problem was fixed! I don't know what's going on!
I also get sometimes unusual errors from TWRP and my device seems to be unstable! Do you think that I might have caused a serious problem to my device after flashing and flashing over and over again?
Here is a screenshot: https://drive.google.com/file/d/18xj7Xj3UWWG7NW7N_uOt7iECBMvkoyRP/view?usp=drivesdk
Device: mido
TWRP: any
ROM: any
Magisk: any
**Problem solved**
Steps to solution:
1. Flash latest MIUI from custom recovery or Mi Flash.
2. Boot up and finish the initial set up.
3. Reboot into recovery and flash latest magisk zip file.
4. Reboot and see that magisk manager is installed
5. Then reboot again into TWRP, wipe everything and format data!
6. Flash ROM, GAPPS and then latest magisk manager!
Done!
David_#27 said:
I don't know what I did but I think it's really serious and important for me to be solved, that's why I am requesting for your help!
Click to expand...
Click to collapse
The questions are - which TWRP (and is it standard or Treble); which ROM (and is it standard or Treble)? which Magisk (and is it standard or Treble)?
DarthJabba9 said:
The questions are - which TWRP (and is it standard or Treble); which ROM (and is it standard or Treble)? which Magisk (and is it standard or Treble)?
Click to expand...
Click to collapse
First of all I noticed the problem when I had official TWRP 3.2.1-0, OMNI ROM(Oreo 8.1) and standard magisk manager(v16.0) zip file!
Do you have an SD card in your phone? Maybe that's causing problems.
I don't see why flashing ROMs a lot would cause you many issues. Could even be a hardware issue with your onboard eMMC storage or something else.
David_#27 said:
First of all I noticed the problem when I had official TWRP 3.2.1-0, OMNI ROM(Oreo 8.1) and standard magisk manager(v16.0) zip file!
Click to expand...
Click to collapse
Hmmm ... perhaps you should wipe everything (system, cache, and dalvik) and then format your data partition (which will also wipe your internal SD) and start afresh.
Go back to stock rom using fastboot method or MiFlash tool, that way you'll go back to complete stock and it maybe able to solve your problem
@DarthJabba9 and @rrgreatvijay5, thanks a lot for you're help, but I've already tried both of the methods you provide me! Maybe it is a hardware issue like @sk8223 says...
But, I won't quit till I find the solution to this problem!
The hardware is FINE! FIY, we were together when we were flashing, so let me provide some additional info.
We flashed the latest Dev ROM that was available, the one from the 29th of March. Everything flashed successfully, MIUI, TWRP, ROMs, other mods, etc. Only Magisk has issues so this is in no way a hardware issue. The worst thing that could have happened would be to mess up the partitions on your emmc, but that is extremely unlikely and can be fixed.
The question we should be asking here is what firmware do most people use? We'll just download and flash that.
Thanks all for your help!
---------- Post added at 12:25 PM ---------- Previous post was at 12:23 PM ----------
sk8223 said:
Do you have an SD card in your phone? Maybe that's causing problems.
I don't see why flashing ROMs a lot would cause you many issues. Could even be a hardware issue with your onboard eMMC storage or something else.
Click to expand...
Click to collapse
That's a good point. Not the emmc part, but the SD part. Try moving the Magisk zip to the root of your internal storage.
chrismin13 said:
The hardware is FINE! FIY, we were together when we were flashing, so let me provide some additional info.
We flashed the latest Dev ROM that was available, the one from the 29th of March. Everything flashed successfully, MIUI, TWRP, ROMs, other mods, etc. Only Magisk has issues so this is in no way a hardware issue. The worst thing that could have happened would be to mess up the partitions on your emmc, but that is extremely unlikely and can be fixed.
The question we should be asking here is what firmware do most people use? We'll just download and flash that.
Thanks all for your help!
---------- Post added at 12:25 PM ---------- Previous post was at 12:23 PM ----------
That's a good point. Not the emmc part, but the SD part. Try moving the Magisk zip to the root of your internal storage.
Click to expand...
Click to collapse
That's exactly what I meant! Thank you Chris!
So guys what firmware do you use in order to flash custom roms?
David_#27 said:
So guys what firmware do you use in order to flash custom roms?
Click to expand...
Click to collapse
You may try any of these, i usually flash latest one.
https://androidfilehost.com/?w=files&flid=236737
Edit: If you have already tried fastboot flashing method, my guess would be your firmware has already restored to stock, so it wont make any difference, but still give it a shot
Did you by any chance change the partitions fro F2FS to EXT4? Could that cause problems?
sk8223 said:
Did you by any chance change the partitions fro F2FS to EXT4? Could that cause problems?
Click to expand...
Click to collapse
No I didn't... The partitions is already ext4 formatted!
sk8223 said:
Did you by any chance change the partitions fro F2FS to EXT4? Could that cause problems?
Click to expand...
Click to collapse
Correct me if I'm wrong, but all partitions on mido are ext4. AFAIK, he has never changed any partitions to F2FS. Still, going back to stock would revert that and we have done that already a couple of times.
@David_#27 Let's try going back to stock again and flashing Magisk on MIUI, just to be sure.
chrismin13 said:
Correct me if I'm wrong, but all partitions on mido are ext4. AFAIK, he has never changed any partitions to F2FS. Still, going back to stock would revert that and we have done that already a couple of times.
@David_#27 Let's try going back to stock again and flashing Magisk on MIUI, just to be sure.
Click to expand...
Click to collapse
Very good idea dude! I will give it a shot!
I don't think this could have been the solution since magisk basically patches the boot image and that is different for all the roms (it comes with the rom). Oreo is a treble built and i suppose magisk doesn't support it as of now, the second time you flashed the rom (after flashing miui) was it a nougat based rom???.
Although I found a link to a custom magisk made for treble builds {https://forum.xda-developers.com/project-treble/trebleenabled-device-development/unofficial-treble-enabled-resurrection-t3761279}. But I tried it and it didn't work for me. So I guess we will have to wait for @topjohnwu to release treble support. Correct me if I a wrong
Maximus909 said:
I don't think this could have been the solution since magisk basically patches the boot image and that is different for all the roms (it comes with the rom). Oreo is a treble built and i suppose magisk doesn't support it as of now, the second time you flashed the rom (after flashing miui) was it a nougat based rom???.
Although I found a link to a custom magisk made for treble builds {https://forum.xda-developers.com/project-treble/trebleenabled-device-development/unofficial-treble-enabled-resurrection-t3761279}. But I tried it and it didn't work for me. So I guess we will have to wait for @topjohnwu to release treble support. Correct me if I a wrong
Click to expand...
Click to collapse
Just flash casually this one: https://drive.google.com/file/d/1Agu5zLOi5U37Ri8-fGFNOre2LY32_WGX/view?usp=drivesdk
If the problem remains, you should flash latest stock ROM, using TWRP or MiFlash and then try it all over again!
David_#27 said:
Just flash casually this one: https://drive.google.com/file/d/1Agu5zLOi5U37Ri8-fGFNOre2LY32_WGX/view?usp=drivesdk
If the problem remains, you should flash latest stock ROM, using TWRP or MiFlash and then try it all over again!
Click to expand...
Click to collapse
I am about to try 16.4 treble built...found the link after a bit of digging... If it works (or it doesn't) I will update, also using the redwolf treble built recovery, checking if that helps....
David_#27 said:
Just flash casually this one: https://drive.google.com/file/d/1Agu5zLOi5U37Ri8-fGFNOre2LY32_WGX/view?usp=drivesdk
If the problem remains, you should flash latest stock ROM, using TWRP or MiFlash and then try it all over again!
Click to expand...
Click to collapse
All right so all done, and succeful this time. Now the problem was actually with the recovery and not magisk itself.... So what we need to do is flash redwolf recovery for tteble builds and download treble compatible 16.4 magisk version. I tried flashing through standard twrp but failed so we need this treble build :good:
Redwolf Recovery {treble build, for MIDO ONLY} : https://androidfilehost.com/?fid=746010030569954397 .
Magisk 16.4 modded : https://androidfilehost.com/?fid=962187416754478287 .
guys want to flash twrp to flash notification zip but am confused about few thing can you guys can help if the possible explanation in simple words will be appreciated
1: I read my data will get encrypted (what is this thing all about ) what encryption means i mean i know what encryption is in general but what does it mean here and how will it affect me i dont care if my user data get deleted when i flash but i dont wana get bootloop or soft brick
2: any proper noob friendly tutorial
3: can i flash global beta through twrp i dont want root etc just twrp
4 : can i retain twrp after i install global beta without root and magisk
5 : isnt there any portable twrp which i can boot to to flash that zip and all back to normal mean stock recovery
Check this out. Twrp is not official yet, but can use force encryption disabler to keep TWRP work on next reboot to recovery. So far no problem to flash rom via twrp.
https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405
thomas140 said:
Check this out. Twrp is not official yet, but can use force encryption disabler to keep TWRP work on next reboot to recovery. So far no problem to flash rom via twrp.
https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405
Click to expand...
Click to collapse
thnax for the reply ut that is what my confusion is what dycription means and how it effects
bravo2526 said:
thnax for the reply ut that is what my confusion is what dycription means and how it effects
Click to expand...
Click to collapse
For what I know, if you boot into twrp via fastboot, it will be encrypted back to stock recovery if you don't install the force encryption disabler.
Meaning that, this force encryption disabler is to help to keep the twrp recovery.
thomas140 said:
For what I know, if you boot into twrp via fastboot, it will be encrypted back to stock recovery if you don't install the force encryption disabler.
Meaning that, this force encryption disabler is to help to keep the twrp recovery.
Click to expand...
Click to collapse
o yes its making sense now so if i dont use encryption disabler it will return me to stock recovary. and i f i do it will keep the twrp. ok if it is the case then what will happen if i flash twrp and flash that notification zip and reboot it without that encryption disabler will my phone will be reset or not on next boot
bravo2526 said:
o yes its making sense now so if i dont use encryption disabler it will return me to stock recovary. and i f i do it will keep the twrp. ok if it is the case then what will happen if i flash twrp and flash that notification zip and reboot it without that encryption disabler will my phone will be reset or not on next boot
Click to expand...
Click to collapse
Shouldn't need to reset, just that when you go to next reboot recovery, stock recovery will haunt you.hahaha...
thomas140 said:
Shouldn't need to reset, just that when you go to next reboot recovery, stock recovery will haunt you.hahaha...
Click to expand...
Click to collapse
lolz haunt in good or bad way?
bravo2526 said:
lolz haunt in good or bad way?
Click to expand...
Click to collapse
Well, There's no good and bad when you still can boot as per normal, just that the recovery will be different, either twrp or stock though...
Use the one with working decryption so you don't have to worry about it. Forget every other Recovery and the Encryption Disabler, it just makes things complicated and it's an out-of-date work around for other Recovery's which aren't fixed yet.
If you use official MIUI then you will need to reflash or boot TWRP again if you want to use it, because stock Recovery will replace TWRP when you boot official MIUI. This isn't so bad because it keeps OTA working (unless you flashed Magisk of course, which will need to be uninstalled first before OTA).
CosmicDan said:
Use the one with working decryption so you don't have to worry about it. Forget every other Recovery and the Encryption Disabler, it just makes things complicated and it's an out-of-date work around for other Recovery's which aren't fixed yet.
If you use official MIUI then you will need to reflash or boot TWRP again if you want to use it, because stock Recovery will replace TWRP when you boot official MIUI. This isn't so bad because it keeps OTA working (unless you flashed Magisk of course, which will need to be uninstalled first before OTA).
Click to expand...
Click to collapse
Does this link ok to go for since it mention with working decryption?
https://forum.xda-developers.com/poco-f1/development/recovery-twrp-3-2-3-decryption-t3853004
Now I am still using the version that needs the disabler, can I just reflash the new twrp file, clear dalvik cache?
thomas140 said:
Does this link ok to go for since it mention with working decryption?
https://forum.xda-developers.com/poco-f1/development/recovery-twrp-3-2-3-decryption-t3853004
Now I am still using the version that needs the disabler, can I just reflash the new twrp file, clear dalvik cache?
Click to expand...
Click to collapse
You can dirty flash the recovery over the one you currently have, it won't affect your phone at all. Keep in mind though that your device will stay decrypted, you'll have to encrypt it manually via the phone settings.
franz said:
You can dirty flash the recovery over the one you currently have, it won't affect your phone at all. Keep in mind though that your device will stay decrypted, you'll have to encrypt it manually via the phone settings.
Click to expand...
Click to collapse
Interesting, if stay decrypted, that's fine as the twrp will continue stay for future reboot to receovery.
You said that can manually encrypt via phone setting, but how to do that?
thomas140 said:
Well, There's no good and bad when you still can boot as per normal, just that the recovery will be different, either twrp or stock though...
Click to expand...
Click to collapse
so refreshing to know. The only thing that haunts is boot loop to which we non-tech guys are afraid of and technical guys assume that every one knows the basics and hence the confusion occurs as no clear guide becomes available in new days of any mobile launch waiting a noob friendly thread for poco which might explain these in an order but thanx for the time you took to clear a bit
thomas140 said:
Interesting, if stay decrypted, that's fine as the twrp will continue stay for future reboot to receovery.
You said that can manually encrypt via phone setting, but how to do that?
Click to expand...
Click to collapse
yeah its interesting to know i mean why its needed or y will anyone will encypt it again. any scenario ?
bravo2526 said:
yeah its interesting to know i mean why its needed or y will anyone will encypt it again. any scenario ?
Click to expand...
Click to collapse
Perhaps, break up with the mistress (TWRP) and go back to the wife/husband(Stock recovery)? :laugh:
thomas140 said:
Perhaps, break up with the mistress (TWRP) and go back to the wife/husband(Stock recovery)? :laugh:
Click to expand...
Click to collapse
lolz you are funny so you are tempting us to keep mistress no problem if it locks your wealth(data) . meanwhile, global beta 8.10.25 is up for twrp anyone tried?
bravo2526 said:
lolz you are funny so you are tempting us to keep mistress no problem if it locks your wealth(data) . meanwhile, global beta 8.10.25 is up for twrp anyone tried?
Click to expand...
Click to collapse
No idea, I am still stick with miui global 9.6.25. haha
ps: I have no mistress but I have a wife:laugh:
bravo2526 said:
guys want to flash twrp to flash notification zip but am confused about few thing can you guys can help if the possible explanation in simple words will be appreciated
1: I read my data will get encrypted (what is this thing all about ) what encryption means i mean i know what encryption is in general but what does it mean here and how will it affect me i dont care if my user data get deleted when i flash but i dont wana get bootloop or soft brick
2: any proper noob friendly tutorial
3: can i flash global beta through twrp i dont want root etc just twrp
4 : can i retain twrp after i install global beta without root and magisk
5 : isnt there any portable twrp which i can boot to to flash that zip and all back to normal mean stock recovery
Click to expand...
Click to collapse
The simplest option for u is to download twrp with working encryption.
Dont flash it , just boot into recovery by fastboot command thru adb.
Flash whatever u want to and once done flashing , reboot and u will boot with stock recovery. That way for stock roms u can update via OTA also.
There's a thread in Q&A , will post the link in some time , would suggest u read it.
https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-root-unlock-bootloader-t3852520
thomas140 said:
Does this link ok to go for since it mention with working decryption?
https://forum.xda-developers.com/poco-f1/development/recovery-twrp-3-2-3-decryption-t3853004
Now I am still using the version that needs the disabler, can I just reflash the new twrp file, clear dalvik cache?
Click to expand...
Click to collapse
That's the only one last I checked, yes that's it.
You will need to reflash stock ROM (actually just vendor) if you want to enable encryption enforcement again in your ROM.
CosmicDan said:
That's the only one last I checked, yes that's it.
You will need to reflash stock ROM (actually just vendor) if you want to enable encryption enforcement again in your ROM.
Click to expand...
Click to collapse
Hmm..
My current info:
Mini 9.6.25
Twrp (need to flash with Force encryption Disabler)
So here's my step to do:
Download the twrp with decryption enabled.
Download same stock rom.
Flash the stock rom
Flash the new twrp I downloaded.
That's all?
Will it be asking for password and stuff? Because as I know if it happens, I need to wipe data, right?
Another scenario, if I am going to flash miui 10 beta or stable in the future, I need to wipe data to get it work after flash?
So I unlocked the bootloader and managed to flash TWRP (after some issues with the wrong drivers and usb3 ports).
Then I tried to flash LOS 16, but TWRP said my firmware wasnt up to date.
Since I just wanted to play around with a new ROM I went to the next on the list and that was OMNI ROM. Flashed that, which worked, but when I booted it complained about Google Play not being responsive or something. So I booted back into TWRP.
I'm not sure at which point TWRP started to ask for a password, but I think it was after and not before I flashed Paranoid Android after OMNI ROM didnt work (so on my third ROM now). When I booted PA, the PW splash screen came up but then instantly booted back to TWRP. TWRP asks for a PW now, but I just hit cancel and then its bypassed.
So then I went back to OmniROM and it said something about my phone being encrypted and I had to do a factory reset. Which I did. And now when the phone starts it asks for a password.
I can still get into TWRP, and then hit cancel when it also asks for a pw.
So how do I fix this? There is no important data on the phone that needs to be saved.
Grateful for any help!
Hi, use same password you had, when your phone was running, worked for me. I hope it also fix ur problem. If not, maybe try adb sideload different rom? I did that on my xiaomi mi a1 and it worked.
Also you need to install firmware & vendor for lineage OS, i think you can find it on the post of the rom.
lordnakki said:
Hi, use same password you had, when your phone was running, worked for me. I hope it also fix ur problem. If not, maybe try adb sideload different rom? I did that on my xiaomi mi a1 and it worked.
Also you need to install firmware & vendor for lineage OS, i think you can find it on the post of the rom.
Click to expand...
Click to collapse
Thanks! Thing is that there never ever was a password set on the phone...
BrotherZero said:
Thanks! Thing is that there never ever was a password set on the phone...
Click to expand...
Click to collapse
Boot back on twrp. U beed format internal store because ur phone is encrypt. It will earse all ur data (phone store) and u need to have a zip rom on sdcard( to reinstall a rom to boot on system after u format data). After install rom then flash a file called fde.If u havent a sdcard, u need a pc to flash a rom throught fastboot. Remember u need a fde file (search on forum or google) and u will know when need to flash it. My advice is if u want to play with this phone, u would have: a sdcard, a zip rom on sdcard, fde zip file, a twrp of course. Good luck.
tiennhu89 said:
Boot back on twrp. U beed format internal store because ur phone is encrypt. It will earse all ur data (phone store) and u need to have a zip rom on sdcard( to reinstall a rom to boot on system after u format data). After install rom then flash a file called fde.If u havent a sdcard, u need a pc to flash a rom throught fastboot. Remember u need a fde file (search on forum or google) and u will know when need to flash it. My advice is if u want to play with this phone, u would have: a sdcard, a zip rom on sdcard, fde zip file, a twrp of course. Good luck.
Click to expand...
Click to collapse
Thanks! Yeah, I got an SD card for that ready.
When you say FDE do you mean FED (Force Encryption Disabler)? FDE is File Disk Encryption?
And is it possible to keep encryption? I thought TWRP supported encryption now?
BrotherZero said:
Thanks! Yeah, I got an SD card for that ready.
When you say FDE do you mean FED (Force Encryption Disabler)? FDE is File Disk Encryption?
And is it possible to keep encryption? I thought TWRP supported encryption now?
Click to expand...
Click to collapse
Yeah, my fauls. Force Encryption Disabler. FED is for sure because its happened for me. Im having twrp which support encryption. But when i flash a rom then reboot (without flash fed). My phone ask for password. So i know it. Now im flashing fed when i flash any rom (with or without support encryption).
1. Format data.. as in look for the words FORMAT DATA...
this will delete the TWRP PASSWORD
2. FLASH FED...
3. FLASH YOUR ROM
tiennhu89 said:
Yeah, my fauls. Force Encryption Disabler. FED is for sure because its happened for me. Im having twrp which support encryption. But when i flash a rom then reboot (without flash fed). My phone ask for password. So i know it. Now im flashing fed when i flash any rom (with or without support encryption).
Click to expand...
Click to collapse
Thanks! And sorry for the late reply, been away for a bit. Are you saying it doesnt matter if the TWRP supports encryption or not, it wont work? Thats a shame.
santiagoruel13 said:
1. Format data.. as in look for the words FORMAT DATA...
this will delete the TWRP PASSWORD
2. FLASH FED...
3. FLASH YOUR ROM
Click to expand...
Click to collapse
Again, sorry for the late reply. And again, there is no way to keep encryption with Poco F1 and official TWRP?
Hi,
I'll try to keep latest TWRP by wzsx150, that are posted in MIUI Chinese forum here.
Downloads: Google drive
Latest: V3.3.0 April 21st
Changelog (translated):
v3.3.0 April 21st
1. Update to the latest 3.3.0 version, adjust and optimize
v3.2.3 April 1st
1. Update the built-in root to magisk-19.0, And other built-in feature upgrades
2. Other optimization adjustments
Finally. Thank you very much
edit : Can anyone install Magisk? Tried to install but no luck here
RinzImpulse said:
Finally. Thank you very much
edit : Can anyone install Magisk? Tried to install but no luck here
Click to expand...
Click to collapse
As seen on other forums Magisk v19 should work. Wipe Cache / Dalvik after installing...
Deep-Knight said:
As seen on other forums Magisk v19 should work. Wipe Cache / Dalvik after installing...
Click to expand...
Click to collapse
forget to update. yes, beta version works fine. forget that P only works with v19
Does it work with the Global version?
All 3 files seems to be for the China version.
Sent from my Mi 9 SE using Tapatalk
It works. CN just means the language and the origin. For some reason my data keeps getting encrypted after each reboot
can we perform backup and restore with this TWRP?
Tested backup of data, system and boot partitions working ok with 0421.
Haven't tested restore.
danielwright said:
Tested backup of data, system and boot partitions working ok with 0421.
Haven't tested restore.
Click to expand...
Click to collapse
+1
Yeah, I haven't tested restore too
Does anyone know of which files to make a backup from, in order to have a full working rom? There are so many files!
And what about this encryption tab in backup, what's that for?
Sent from my [device_name] using XDA-Developers Legacy app
putti71 said:
Does anyone know of which files to make a backup from, in order to have a full working rom? There are so many files!
And what about this encryption tab in backup, what's that for?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
The encryption tab is an optional feature if you want to encrypt the backup files generated with a password - much like adding a password to a zip file.
For which partitions to backup to save a full working ROM - see https://twrp.me/faq/whattobackup.html however I haven't tested for MIUI 10/Android Pie on the 9SE.
Did someone successfully restore a backup made with this recovery?
For anyone having issues with flashing. Try disconnecting the cable after flashing and boot into recovery with power + vol up. I am running on stable eu rom with magisk now. Seems to work smoothly
decayed.cell said:
It works. CN just means the language and the origin. For some reason my data keeps getting encrypted after each reboot
Click to expand...
Click to collapse
Did you solve the problem? Cause I have the same on my Redmi 5 Plus and it's VERY annoying. I must format data everytime I want to flash a zip file, or I get an error message. I was planning to buy this phone but the lack of community support scares me quite a bit.
PurPLe SKy said:
Did you solve the problem? Cause I have the same on my Redmi 5 Plus and it's VERY annoying. I must format data everytime I want to flash a zip file, or I get an error message. I was planning to buy this phone but the lack of community support scares me quite a bit.
Click to expand...
Click to collapse
You just need to put in your PIN and it will decrypt
decayed.cell said:
You just need to put in your PIN and it will decrypt
Click to expand...
Click to collapse
But the recovery doesn't ask me for any pin or pattern.
I flashed twrp recovery and all seems good but when i try to boot into twrp there is always still the stock recovery. I tried also with 2 different fastboot but nothing changes. What i need to do ?
when the recovery is flashed, instead of rebooting device when in fastboot mode, just press vol+and power button
PeterImmel said:
Did someone successfully restore a backup made with this recovery?
Click to expand...
Click to collapse
Hi i would to known if restore works Fine?
PurPLe SKy said:
But the recovery doesn't ask me for any pin or pattern.
Click to expand...
Click to collapse
I boot up MIUI normally first. Then set a PIN, then reboot into fastboot and flash TWRP. After that I get a prompt