Related
Im triyng to install the full version of the pre rooted stock it like over 800mg in size. It been installing for almost 10 or 15 minutes and not done yet. Is that normal or is this a problem? it still says installing and im using twrp to install.
AndroidSmitty said:
Im triyng to install the full version of the pre rooted stock it like over 800mg in size. It been installing for almost 10 or 15 minutes and not done yet. Is that normal or is this a problem? it still says installing and im using twrp to install.
Click to expand...
Click to collapse
You can try rebooting to the recovery and trying it again and see if that helps you...
RLKirk said:
You can try rebooting to the recovery and trying it again and see if that helps you...
Click to expand...
Click to collapse
Thanks i had to re install stock using the RUU.exe so i can charge my battery to 100% before i try again because my battery was way down to 19%. What all do i need to do to get successful root. I flashed the boot.img and twrp.img i got from his forum. everything i try to flash fails.
AndroidSmitty said:
Thanks i had to re install stock using the RUU.exe so i can charge my battery to 100% before i try again because my battery was way down to 19%. What all do i need to do to get successful root. I flashed the boot.img and twrp.img i got from his forum. everything i try to flash fails.
Click to expand...
Click to collapse
Follow the directions here: http://forum.xda-developers.com/showthread.php?t=2011611
I do have my boot loader unlocked its just i cant get rooted. I flashed the root files SuperSU i got from this forum and i tried flashing roms and it all fails.
You can try rebooting to the recovery
After the updating to 14.2.A.1.136 whenever I reboot/boot the phone it will stuck on the boot animation screen (the color wave still moving ) I have to force shut it down many time until it boot normal. XZU is rooted. Any idea what can be the problem and how to fix it.
Because I did factory reset it but did not help. Any one has the same problem
funfun99999 said:
After the updating to 14.2.A.1.136 whenever I reboot/boot the phone it will stuck on the boot animation screen (the color wave still moving ) I have to force shut it down many time until it boot normal. XZU is rooted. Any idea what can be the problem and how to fix it.
Because I did factory reset it but did not help. Any one has the same problem
Click to expand...
Click to collapse
In the two or three days after release of 136 I flashed it maybe 8 or 10 times and never had that issue did both clean, dirty and part flashes...
What update method did you use?
I would be tempted to do a full backup of your data and then do a clean install from a FTF or do a PCC fix phone (whatever it is called)
blueether said:
In the two or three days after release of 136 I flashed it maybe 8 or 10 times and never had that issue did both clean, dirty and part flashes...
What update method did you use?
I would be tempted to do a full backup of your data and then do a clean install from a FTF or do a PCC fix phone (whatever it is called)
Click to expand...
Click to collapse
i did used this
http://forum.xda-developers.com/showthread.php?t=2631768
using TWRP and Wiped Dalvik-Cache, System, Cache, Data
funfun99999 said:
i did used this
http://forum.xda-developers.com/showthread.php?t=2631768
using TWRP and Wiped Dalvik-Cache, System, Cache, Data
Click to expand...
Click to collapse
Locked BL or unlocked BL
What firmware were you running before the update?, and was it rooted etc?
blueether said:
Locked BL or unlocked BL
What firmware were you running before the update?, and was it rooted etc?
Click to expand...
Click to collapse
Locked BL + XZDualRecovery2.7.83 BETA
It was on 14.1.B.1.532 flashed ftf to get root and installed XZDualRecovery tried to update to 14.2.A.0.290 using http://forum.xda-developers.com/showthread.php?t=2612980
But the phone did not boot it keep hanging on the boot animation
So I update to 14.2.A.1.136 and it work but after few reboot this problem started.
funfun99999 said:
Locked BL + XZDualRecovery2.7.83 BETA
It was on 14.1.B.1.532 flashed ftf to get root and installed XZDualRecovery tried to update to 14.2.A.0.290 using http://forum.xda-developers.com/showthread.php?t=2612980
But the phone did not boot it keep hanging on the boot animation
So I update to 14.2.A.1.136 and it work but after few reboot this problem started.
Click to expand...
Click to collapse
OK so it was working fine before?
Have you installed xposed, or any modules lately? - I've had that hang a boot
You could always do a reinstall of the rom and then flash the stripped FTF again ie follow the instructions like doing a new install
@[NUT] any other ideas as it's your rom?
blueether said:
OK so it was working fine before?
Have you installed xposed, or any modules lately? - I've had that hang a boot
You could always do a reinstall of the rom and then flash the stripped FTF again ie follow the instructions like doing a new install
@[NUT] any other ideas as it's your rom?
Click to expand...
Click to collapse
yes it works fine
yes i installed xposed
ok i will do it now
you hang was because of xposed?
funfun99999 said:
you hang was because of xposed?
Click to expand...
Click to collapse
I had 1 hang straight after installing xposed and about 5 modules, a reset an it booted up fine - Yes I know I should have activated them 1 at a time
blueether said:
I had 1 hang straight after installing xposed and about 5 modules, a reset an it booted up fine - Yes I know I should have activated them 1 at a time
Click to expand...
Click to collapse
Is the xposed itself or did you find which modules it cause this problem
I just flash the rom again and restored all the apps/date but not the xposed and reboot it 4 time now and no hangs
funfun99999 said:
Is the xposed itself or did you find which modules it cause this problem
I just flash the rom again and restored all the apps/date but not the xposed and reboot it 4 time now and no hangs
Click to expand...
Click to collapse
No I don't know what module it was or even if it was xposed. I only hung the once so I didn't go digging to find out.
blueether said:
No I don't know what module it was or even if it was xposed. I only hung the once so I didn't go digging to find out.
Click to expand...
Click to collapse
Ok thank you very much.
Just remember that Xposed adds a recovery file on your internal storage in case things like these happen. So if Xposed causes any issues, like a bootloop, just boot into recovery and flash the "disable_xposed.zip" (or something with that name) and reboot. Voila.
I looked around for one but was unable to find one. Maybe Twi5sted's stock has the original kernel but encryption fails when I attempt it.
Any suggestions?
Yep, muinz_ri created a Stock De-Odexed ROM. I was successfully able to install Xposed by flashing everything through FlashFire and still have Knox 0x0.
http://forum.xda-developers.com/tmo...ow-to-update-to-stock-rooted-ob1-5-0-t3049676
Direct link to ROM download: https://www.androidfilehost.com/?fid=24052804347762756
TheAH said:
Yep, muinz_ri created a Stock De-Odexed ROM. I was successfully able to install Xposed by flashing everything through FlashFire and still have Knox 0x0.
http://forum.xda-developers.com/tmo...ow-to-update-to-stock-rooted-ob1-5-0-t3049676
Direct link to ROM download: https://www.androidfilehost.com/?fid=24052804347762756
Click to expand...
Click to collapse
That's awesome, wish I had known before I tripped Knox but oh well.
I'm getting a bootloop with a very bright split second tmobile splash screen just before it reboots. I have latest TWRP, link2sd and encryption... I wonder what the problem could be...
how to make stock recovery flashable?
I do have another question regarding this rom - would you happen to know how I may be able to make the embedded recovery image flashable? TWRP doesn't seem to be working at the moment with regard to decrypting and formatting /data but the stock recovery does. It can come in handy if there is a way to do it via mobile odin possibly or via some other program.
fishinpercolator said:
I do have another question regarding this rom - would you happen to know how I may be able to make the embedded recovery image flashable? TWRP doesn't seem to be working at the moment with regard to decrypting and formatting /data but the stock recovery does. It can come in handy if there is a way to do it via mobile odin possibly or via some other program.
Click to expand...
Click to collapse
Do you have twrp installed right now?
ShinySide said:
Do you have twrp installed right now?
Click to expand...
Click to collapse
Right now I have stock recovery as I recently reflashed the Rom. At some point however I plan to go back to TWRP.
If I run into encryption problems and need to do a reset, I would like to see if I can flash TWRP using TWRP app while booted in safe mode (if I am able to get that far).
What do you think?
fishinpercolator said:
Right now I have stock recovery as I recently reflashed the Rom. At some point however I plan to go back to TWRP.
If I run into encryption problems and need to do a reset, I would like to see if I can flash TWRP using TWRP app while booted in safe mode (if I am able to get that far).
What do you think?
Click to expand...
Click to collapse
Well encryption will be fine on stock recovery. I thought you had twrp and just wanted the stock recovery which I was going to tell you to post the stock recovery and I'll put it in a twrp flashable zip
ShinySide said:
Well encryption will be fine on stock recovery. I thought you had twrp and just wanted the stock recovery which I was going to tell you to post the stock recovery and I'll put it in a twrp flashable zip
Click to expand...
Click to collapse
I appreciate that... at some point I will be on TWRP though so I can post the stock recovery when I get home. Or how can I do it myself?
fishinpercolator said:
I appreciate that... at some point I will be on TWRP though so I can post the stock recovery when I get home. Or how can I do it myself?
Click to expand...
Click to collapse
Here, download this, extract the zip, put the recovery.img in the extracted folder, highlight meta-inf system and recovery.img and zip all three and flash it. Only use this zip for stock or custom recoveries
ShinySide said:
Here, download this, extract the zip, put the recovery.img in the extracted folder, highlight meta-inf system and recovery.img and zip all three and flash it. Only use this zip for stock or custom recoveries
Click to expand...
Click to collapse
Hey thanks! So I did as you said and flashed the stock recovery from the deodexed rom and it's still TWRP. Strange isn't it? It would make sense if the deodexed ROM came with TWRP but when I initially flashed it I can confirm it was stock android.
I'm confused....
fishinpercolator said:
Hey thanks! So I did as you said and flashed the stock recovery from the deodexed rom and it's still TWRP. Strange isn't it? It would make sense if the deodexed ROM came with TWRP but when I initially flashed it I can confirm it was stock android.
I'm confused....
Click to expand...
Click to collapse
Obvious question - did you reboot back to recovery after flashing?
fishinpercolator said:
Hey thanks! So I did as you said and flashed the stock recovery from the deodexed rom and it's still TWRP. Strange isn't it? It would make sense if the deodexed ROM came with TWRP but when I initially flashed it I can confirm it was stock android.
I'm confused....
Click to expand...
Click to collapse
Oh wait, I did something very wrong... fixing now...
Yay it worked, thanks a lot
I guess I should keep the stock recovery installed with this thing encrypted because TWRP seems broken (at least version 2.8.7.0). I emailed the developer about it.
Now I'm wondering for added flexibility, how I may be able to flash the stock recovery from MobileOdin. That seems to take .md5 files and not zips. Is this feasible to do?
fishinpercolator said:
Yay it worked, thanks a lot
I guess I should keep the stock recovery installed with this thing encrypted because TWRP seems broken (at least version 2.8.7.0). I emailed the developer about it.
Now I'm wondering for added flexibility, how I may be able to flash the stock recovery from MobileOdin. That seems to take .md5 files and not zips. Is this feasible to do?
Click to expand...
Click to collapse
Post the img I'll make you one tonight. It'll be 10x easier for me since I run Linux then telling you how on windows
ShinySide said:
Post the img I'll make you one tonight. It'll be 10x easier for me since I run Linux then telling you how on windows
Click to expand...
Click to collapse
Well thanks! Maybe you can point me toward the Windows way as I would like to do the same for the stock kernel, xposed, and the tethering addon.
fishinpercolator so are you having trouble with TWRP? What I did in FlashFire was flash the pre-rooted de-odexed ROM (that I linked earlier) then booted that. It was de-odexed and worked fine but boot took about 15 minutes (as it is de-odexed).
In FlashFire you need to hit the + and press Flash ZIP or OTA.
Then I installed FlashFire again (it was erased because I flashed a new ROM) and downloaded the Samsung 5.0 Xposed ZIP and flashed that in FlashFire using Flash ZIP or OTA. Basically since I have Knox 0x0, I use FlashFire as my "recovery" and it might be easier for you than finding a working TWRP image (although I am sure ShinySide is more than eager to help you). Then I installed the Xposed APK and had to reboot before it recognized the Xposed ZIP was installed.
After that, most Xposed modules started working for me.
TheAH said:
fishinpercolator so are you having trouble with TWRP? What I did in FlashFire was flash the pre-rooted de-odexed ROM (that I linked earlier) then booted that. It was de-odexed and worked fine but boot took about 15 minutes (as it is de-odexed).
In FlashFire you need to hit the + and press Flash ZIP or OTA.
Then I installed FlashFire again (it was erased because I flashed a new ROM) and downloaded the Samsung 5.0 Xposed ZIP and flashed that in FlashFire using Flash ZIP or OTA. Basically since I have Knox 0x0, I use FlashFire as my "recovery" and it might be easier for you than finding a working TWRP image (although I am sure ShinySide is more than eager to help you). Then I installed the Xposed APK and had to reboot before it recognized the Xposed ZIP was installed.
After that, most Xposed modules started working for me.
Click to expand...
Click to collapse
I haven't used flashfire but will look into it. I've already tripped knox a while ago so that's not my prime concern. I want this phone to be encrypted and would like to learn a way to fix on the fly while on vacation (and without a laptop) in the event a catastrophe happens. It seems TWRP may not be removing the crypto footer when I format data as I still get the encryption password prompt.
Seems like flashfire allows you to flash roms from USB? I will need instructions for that.... <pokes around>
::update::
For some reason I thought flashfire was command line driven... I have Mobile Odin and I read that it contains flashfire, something worth looking into.
Is there a way to flash roms using ADB from a usb stick?
(NOTE- I should clarify, is there a way to flash from a command prompt assuming custom recovery is not installed and the phone is soft-bricked).
fishinpercolator said:
Well thanks! Maybe you can point me toward the Windows way as I would like to do the same for the stock kernel, xposed, and the tethering addon.
Click to expand...
Click to collapse
Here https://www.androidfilehost.com/?fid=24052804347792016
ShinySide said:
Here https://www.androidfilehost.com/?fid=24052804347792016
Click to expand...
Click to collapse
Well thanks!
Ok so.. I am having some problems. Never had many issues with rooting etc before but my S6 Edge is being surprisingly difficult.
it an SM-G925I on 6.0.1 EPIK build
I've tried the Skipsoft tool thing multiple times. But for the love of god I cannot get a recovery installed nor root.
I've had the booting back to stock recovery problem along the way and followed the steps to boot into the custom but every time I go through the options and follow the steps by the time I try, the phone brings up recovery is not seandroid enforcing in RED in the top left of the screen.
I can just hold volume down and power to reboot back to android but so far I have not been having any luck getting root and recover =\
Any help greatly appreciated.
usb debugging enabled, obviously, Knox disabled (had to turn off reset protection to get Odin to flash)
aulterra said:
Ok so.. I am having some problems. Never had many issues with rooting etc before but my S6 Edge is being surprisingly difficult.
it an SM-G925I on 6.0.1 EPIK build
I've tried the Skipsoft tool thing multiple times. But for the love of god I cannot get a recovery installed nor root.
I've had the booting back to stock recovery problem along the way and followed the steps to boot into the custom but every time I go through the options and follow the steps by the time I try, the phone brings up recovery is not seandroid enforcing in RED in the top left of the screen.
I can just hold volume down and power to reboot back to android but so far I have not been having any luck getting root and recover =\
Any help greatly appreciated.
usb debugging enabled, obviously, Knox disabled (had to turn off reset protection to get Odin to flash)
Click to expand...
Click to collapse
Flash twrp through odin for custom recovery.
Cf autoroot for root flash through odin also.
Or
Flash supersu 2.78 sr1 systemless through twrp
callumbr1 said:
Flash twrp through odin for custom recovery.
Cf autoroot for root flash through odin also.
Or
Flash supersu 2.78 sr1 systemless through twrp
Click to expand...
Click to collapse
The tool I used was meant to basically do all of that but I cannot get passed the same issues I mentioned in my post.
aulterra said:
The tool I used was meant to basically do all of that but I cannot get passed the same issues I mentioned in my post.
Click to expand...
Click to collapse
Try to use what i said. Not the tool you used before. Do it manually ot will work
callumbr1 said:
Try to use what i said. Not the tool you used before. Do it manually ot will work
Click to expand...
Click to collapse
as I said, when I do it manually too, I conitnue to receive the same issues.
aulterra said:
as I said, when I do it manually too, I conitnue to receive the same issues.
Click to expand...
Click to collapse
Try to flash uni kernel flashable zip through odin, that should stop the seandroid error.
callumbr1 said:
Try to flash uni kernel flashable zip through odin, that should stop the seandroid error.
Click to expand...
Click to collapse
Do you have links to the correct things I need?
aulterra said:
Do you have links to the correct things I need?
Click to expand...
Click to collapse
https://download.chainfire.eu/791/CF-Root/CF-Auto-Root/CF-Auto-Root-zerolte-zeroltedv-smg925i.zip
Download that autoroot. Install the odin v3.10.6.
Flash the cf autoroot first and then tell me what happens after phone reboots.
callumbr1 said:
https://download.chainfire.eu/791/CF-Root/CF-Auto-Root/CF-Auto-Root-zerolte-zeroltedv-smg925i.zip
Download that autoroot. Install the odin v3.10.6.
Flash the cf autoroot first and then tell me what happens after phone reboots.
Click to expand...
Click to collapse
Thanks, I'll give it a go again Tomorrow (2 am atm)
aulterra said:
Thanks, I'll give it a go again Tomorrow (2 am atm)
Click to expand...
Click to collapse
Okay keep me updated
callumbr1 said:
Okay keep me updated
Click to expand...
Click to collapse
Ok so flashed the autoroot Hopefully right. Used the AP section, booted into download mode and flashed, it was succesful then restarted with the seandroid error But a second or so passed and it booted into cf autoroot which successfully rooted my device.
I guess that's a good thing.
Now all I need to do Is manage to install a custom recovery and find the best rom xD
Thanks for the help so far,
Eagerly waiting for more ^_^
aulterra said:
Ok so flashed the autoroot Hopefully right. Used the AP section, booted into download mode and flashed, it was succesful then restarted with the seandroid error But a second or so passed and it booted into cf autoroot which successfully rooted my device.
I guess that's a good thing.
Now all I need to do Is manage to install a custom recovery and find the best rom xD
Thanks for the help so far,
Eagerly waiting for more ^_^
Click to expand...
Click to collapse
Cool,,
Now download root checker from app store and install it. Press verify root to check.
Easiest way to flash twrp now is to download flashify from playstore.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
From there you can easily flash twrp.
Hope that works mate
callumbr1 said:
Cool,,
Now download root checker from app store and install it. Press verify root to check.
Easiest way to flash twrp now is to download flashify from playstore.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
From there you can easily flash twrp.
Hope that works mate
Click to expand...
Click to collapse
Ok so great news! Flashify worked and I think is amazing.. haha...
ONLY PROBLEM NOW.. is any roms I install don't seem to work. I can wipe, flash and then boot and the phone either gets stuck on the samsung full logo Or the animated glowing samsung boot image. Atleast I think. CarHD rom seemed stuck on the boot image for more than 5 minutes.
Any ideas?
aulterra said:
Ok so great news! Flashify worked and I think is amazing.. haha...
ONLY PROBLEM NOW.. is any roms I install don't seem to work. I can wipe, flash and then boot and the phone either gets stuck on the samsung full logo Or the animated glowing samsung boot image. Atleast I think. CarHD rom seemed stuck on the boot image for more than 5 minutes.
Any ideas?
Click to expand...
Click to collapse
It's normal when you flash a rom for it to take around 10 minutes to boot first time. I'm currently using car HD rom. The first time you flash it, it will stick on Samsung glowing logo for around 10 minutes maybe more. But give it time it will boot. There's a good choice of roms available but check they are compatible first line. Also in aroma installer for CarHD rom select full wipe
callumbr1 said:
It's normal when you flash a rom for it to take around 10 minutes to boot first time. I'm currently using car HD rom. The first time you flash it, it will stick on Samsung glowing logo for around 10 minutes maybe more. But give it time it will boot. There's a good choice of roms available but check they are compatible first line. Also in aroma installer for CarHD rom select full wipe
Click to expand...
Click to collapse
Ok! So I waited heaps longer like you suggested. It booted but for the love of god I can't stand that rom xD
Do you have any rom suggestions for my model?
aulterra said:
Ok! So I waited heaps longer like you suggested. It booted but for the love of god I can't stand that rom xD
Do you have any rom suggestions for my model?
Click to expand...
Click to collapse
Did you flash the aroma theme? If you just flash the ROM without the themes then it is just like stock ROM but with mods like viper, ad away and some good customisation options in ROM control and OTA
There's tyrannus rom, alexis rom, xtrestolite
Have a look on here there's quite a few
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?