Related
Hai.
I have a galaxy note 3 sm n9005. Have already rooted by finding forum from xda and even install twrp recovery following the guides given.
But im trying to install custom rom. And tried all the roms tat is given from xda for note 3 and could install single one.
Please help to resolve this problem. Im confuse.
Tq.
Not enough details.
It's probably the version of recovery you're using.
Which version of TWRP and what errors are you receiving?
es0tericcha0s said:
Not enough details.
It's probably the version of recovery you're using.
Which version of TWRP and what errors are you receiving?
Click to expand...
Click to collapse
Im using twrp 3.0.2.1 and everytime i try to install a rom it stuck at samsung screen.
And it show md5 not found.
What roms have you tried? What firmware were you on before you started flashing? Sometimes newer roms need the newest firmware like the bootloader and modem to run correctly. Are you wiping system, data, and both caches? If you are going from a Touchwiz rom to, say, a CM based, it might also be necessary to wipe the internal storage. Of course you should back all that up to a PC first, if you do that.
es0tericcha0s said:
What roms have you tried? What firmware were you on before you started flashing? Sometimes newer roms need the newest firmware like the bootloader and modem to run correctly. Are you wiping system, data, and both caches? If you are going from a Touchwiz rom to, say, a CM based, it might also be necessary to wipe the internal storage. Of course you should back all that up to a PC first, if you do that.
Click to expand...
Click to collapse
Resurrection remix.unicorn.slim.and all cynogen rom is working. Im trying install s7edge custom rom for darkwolf and darklord. I even updated the bootloader and modem according to tutorial. I used odin to flash them..
N9005xxugboa1
Lrx21v.n9005xxugbob6
I have my stock rom n internl backed up. I try all. And still it always stuck on samsung screen.
Are you installing the kernel after the rom flash? A lot of newer Samsung roms don't have the kernel built in like CM roms.
es0tericcha0s said:
Are you installing the kernel after the rom flash? A lot of newer Samsung roms don't have the kernel built in like CM roms.
Click to expand...
Click to collapse
How can install kernel after. Everytime i install it reboots its self to samsung screen. Or should go back to recovery and install the kernel back. And thank you for your help till now.
That's definitely why it's not booting, if you didn't do the kernel. If the rom has the Aroma installer, typically the last question asks if you want to reboot now and has a check mark in by default. Just uncheck and it'll go back to recovery. But you can also just go back and flash now and should be good.
es0tericcha0s said:
That's definitely why it's not booting, if you didn't do the kernel. If the rom has the Aroma installer, typically the last question asks if you want to reboot now and has a check mark in by default. Just uncheck and it'll go back to recovery. But you can also just go back and flash now and should be good.
Click to expand...
Click to collapse
I have uncheck the reboot after install. When i install the rom it automatically reboot itself. It doesnt show anything or show done. Once it even show os not found.
Hi
Where can i install or find the latest kernel
It's in the installation instructions for the rom.
es0tericcha0s said:
It's in the installation instructions for the rom.
Click to expand...
Click to collapse
Hi.
I have found the bootloader and modem for my sm n9005 from the installation instruction for the rom.
I try to flash according to the tutorial.and my baseband didnt change. I try flash using odin 3times.
Im not sure where i did wrong.can u help me
Tq
Remove the battery for 10 seconds. Put it back in and reboot to download mode. Uncheck auto reboot. Flash then check auto reboot and flash again. Should stick.
tq
es0tericcha0s said:
Remove the battery for 10 seconds. Put it back in and reboot to download mode. Uncheck auto reboot. Flash then check auto reboot and flash again. Should stick.
Click to expand...
Click to collapse
Tq
Will try and let you know
sitijohn85 said:
Tq
Will try and let you know
Click to expand...
Click to collapse
Hi
I tried as said and it didnt chnge.
Can i ask bootloader should be at bl and modem should be at cp. Is it correct.
Hi
Thank you for your help.
I did the change on bootloader and modem.
Now im i need to know two more thing.
I download 2 dffernt kind of bootloader n modem.
I flash blxxxxxbpb1 and cpxxxxxboj1..this 2 files were tar.md5 files
Another one which i didnt flash. Blxxxxxxbpb1 and cpxxxxxxxbpb2..this 2 files are tar.tar files..
Can i know whats the different with this 2 files.
One more thing is when i chnge the bootloader and modem will the kernel changes. Or is it different.
Please guide me..im confuse.
Someone might have just mislabeled them. Flashing those will not affect kernel. Different partition of the phone.
Hi
I did change the bootloader n modem.
And even change the kernel as told in the forum. It was note5 port kernel.7.1.0..
After trying to install the darkwolf rom.it was still the same..it did not work.
Please help me
sitijohn85 said:
Hi
I did change the bootloader n modem.
And even change the kernel as told in the forum. It was note5 port kernel.7.1.0..
After trying to install the darkwolf rom.it was still the same..it did not work.
Please help me
Click to expand...
Click to collapse
This is the recommended kernel
https://www.androidfilehost.com/?fid=24572369242687310
Recommended recovery is TWRP 2.8.7.0 not the newer 3.0+
Flash other recovery. Boot to TWRP. Wipe system, data, cache, dalvik. Flash rom. Wipe caches. Flash kernel. Reboot. Should work according to lots of people on the thread for that rom.
Hi.
How flash kernel.
just flash the tar.md5 file or the tar.zip file
I have RN4 SD with RR Nougat and ElectraBlue kernel. How can I reinstall stock kernel? And what is the latest android version of stock kernel for mido?
nikkky said:
I have RN4 SD with RR Nougat and ElectraBlue kernel. How can I reinstall stock kernel? And what is the latest android version of stock kernel for mido?
Click to expand...
Click to collapse
Reflash whatever ROM you are using to go back to stock kernel.
And how can I go back to stock ROM?
nikkky said:
And how can I go back to stock ROM?
Click to expand...
Click to collapse
If you wanna return to stock ROM including stock recovery etc. use MiFlash to flash stock fastboot image, guide = http://en.miui.com/thread-565784-1-1.html
It's really easy, just follow from point B).
I'm on RR nougat with fanvo kernel and redwolf recovery, i want to revert back to stock miui rom(only rom, i would like to keep redwolf), can you guy's show me the step? I try to flash stock rom 9.5.9 global in redwolf but failed. TIA
w4y4n said:
I'm on RR nougat with fanvo kernel and redwolf recovery, i want to revert back to stock miui rom(only rom, i would like to keep redwolf), can you guy's show me the step? I try to flash stock rom 9.5.9 global in redwolf but failed. TIA
Click to expand...
Click to collapse
Follow guide above (dont relock bootloader) and then just flash Redwolf.
Thank you sir, i'm aware about fastboot method, but i just don't have pc right now to flash, maybe there is other way to revert back without pc, by recovery method maybe? Btw, thank for your reply sir :good:
w4y4n said:
Thank you sir, i'm aware about fastboot method, but i just don't have pc right now to flash, maybe there is other way to revert back without pc, by recovery method maybe? Btw, thank for your reply sir :good:
Click to expand...
Click to collapse
Im pretty sure you can just download stock ROM from http://en.miui.com/download.html (down ATM for some reason) and flash it normally, also dont forget to flash lazyflasher since you are going back to stock. (Redwolf might be taking care of it, not sure)
I allready try it sir, it failed. Failed when flashing system in recovery (not finish flashing stock rom), phone suddenly reboot and stuck on logo. Force to reboot to recovery, can't mount system, but after reboot recovery everything back to normal, and flash RR again so i can use my phone :laugh:
Btw, i try to flash miui 9.5.9.0 NCFMIFA, sorry for my english
w4y4n said:
I allready try it sir, it failed. Failed when flashing system in recovery (not finish flashing stock rom), phone suddenly reboot and stuck on logo. Force to reboot to recovery, can't mount system, but after reboot recovery everything back to normal, and flash RR again so i can use my phone :laugh:
Btw, i try to flash miui 9.5.9.0 NCFMIFA, sorry for my english
Click to expand...
Click to collapse
Maybe you tried to flash fastboot ROM? Link filename you tried to flash.
Due download page shutdown, here is recovery file that i allready try to flash, miui_HMNote4XGlobal_V9.5.9.0.NCFMIFA_b57067babe_7.0
Sorry can't refer the link sir, just the file name :laugh:
w4y4n said:
Due download page shutdown, here is recovery file that i allready try to flash, miui_HMNote4XGlobal_V9.5.9.0.NCFMIFA_b57067babe_7.0
Sorry can't refer the link sir, just the file name :laugh:
Click to expand...
Click to collapse
You are kidding right? This is not even full ROM, this seems like incremental update package (only 45.1MB) that's why you cant flash it.
Just wait till http://en.miui.com/download.html is working and download latest stable or developer ROM and flash it.
Edit:
Here is link to stable 9.5.10.0 http://bigota.d.miui.com/V9.5.10.0.NCFMIFA/miui_HMNote4XGlobal_V9.5.10.0.NCFMIFA_2300218819_7.0.zip
Or developer 8.2.1 http://bigota.d.miui.com/8.2.1/miui_HMNote4XGlobal_8.2.1_7fda810f8d_7.0.zip
It full rom sir, about 1,3gb in size. Thank you sir, i'll try developer rom later
k3lcior said:
You are kidding right? This is not even full ROM, this seems like incremental update package (only 45.1MB) that's why you cant flash it.
Just wait till http://en.miui.com/download.html is working and download latest stable or developer ROM and flash it.
Edit:
Here is link to stable 9.5.10.0 http://bigota.d.miui.com/V9.5.10.0.NCFMIFA/miui_HMNote4XGlobal_V9.5.10.0.NCFMIFA_2300218819_7.0.zip
Or developer 8.2.1 http://bigota.d.miui.com/8.2.1/miui_HMNote4XGlobal_8.2.1_7fda810f8d_7.0.zip
Click to expand...
Click to collapse
Flashing the stock rom using OrangeFox recovery works? I'm on Lineage OS by Zeelog
Mido is a really cool device. I was using MiracleDROID from the beginning. Best ROM ever made (just my opinion). But it is not supported anymore. Thanks to Hikari no Tenshi and Lakku.
I can't call some telephone numbers anymore. No clue, why. I would like to "reset" the phone.
FW: org. stable ROM then following attached guide.
Is that a good idea? Any help or experience is appreciated.
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?
i recently have tried many kernels like(sesh kernel)(lowrun kernel)(optimus drunk kernel) the problem is while iwas using one of them i restarted my device , to stuck at the brand name(poco)while booting up, i went to twrp many times and flashed many other kernels but got the same issue, only the stock kernel(miui offical kernel) worked and the phone booted up normally, iam so confused, i hope you help me with this issue or provide me info if u had countered this issue before on poco f1 device!
thanks for all your hard work developers!!!
Did you dirty flash the ROM zip in between flashing custom kernel? Shouldn't flash one custom kernel over another one. That can cause issues.
amn1987 said:
Did you dirty flash the ROM zip in between flashing custom kernel? Shouldn't flash one custom kernel over another one. That can cause issues.
Click to expand...
Click to collapse
dirty flash i dunno wat dirty mean here but yea iwas flashing kernel over kernel, also iam using miui offical rom no custom roms! if i need to flash rom zip everytime then its useless, i dont need to wipe my data everytime!
Yep, that's the problem, you don't just flash kernel over another one and expect your device to behave normally. Atleast dirty flash your rom so you have the original kernal back and try different kernel after that (though I wouldn't recommend). If you don't clean flash and encounter issues, it's your fault, don't whine.
khanhlinh said:
Yep, that's the problem, you don't just flash kernel over another one and expect your device to behave normally. Atleast dirty flash your rom so you have the original kernal back and try different kernel after that (though I wouldn't recommend). If you don't clean flash and encounter issues, it's your fault, don't whine.
Click to expand...
Click to collapse
i have nerver whined over this as you can see above, iwas clueless, that is why i asked in the first place, the thing iam bothered about it now is, if i need to (dirty?) flash my rom then i need to reset and delete allmy data again, never expected the need to do that, thx for ur reply and be assure i won't whine since i knew the issue and it's consequences!
Do you have the fastboot flash archive file on your PC somewhere? Of the stock rom you are currently using. You can check what version of official rom you are currently using and I can send you the boot.img file from the archive (that is the partition that contains the stock kernel). Flashing that is what reverts you back to stock kernel.
All of this is a requirement for flashing a different custom kernel. It goes like this : you flash a custom kernel >dont like it>flash the stock boot.img through recovery>reboot to system>go back to recovery>flash the new kernel you want to test. If I wasnt clear, contact me, I think I can help.
crazy_4_and1 said:
Do you have the fastboot flash archive file on your PC somewhere? Of the stock rom you are currently using. You can check what version of official rom you are currently using and I can send you the boot.img file from the archive (that is the partition that contains the stock kernel). Flashing that is what reverts you back to stock kernel.
All of this is a requirement for flashing a different custom kernel. It goes like this : you flash a custom kernel >dont like it>flash the stock boot.img through recovery>reboot to system>go back to recovery>flash the new kernel you want to test. If I wasnt clear, contact me, I think I can help.
Click to expand...
Click to collapse
about boot.img yea i have that system on my pc, but i already backed up the stock boot.img before installing my first custom kernel, but after that i didnt work as ur talking about reflashing stock kernel then boot then return to recovery then flash another custom kernel, instead i flashed custom kernel after another, didnt include between each custom kernel a stock kernel flash process, that is why iam having this issue, now even if i tried to flash custom kernel(although iam using now the stock kernel)i will end up soft bricked! but iam now need 1 help if youcan answear me bcs i dunno why icant make another thread,
if i used twrp backup process and created a restore zip for my system(nandroid backup for reflashing stock rom ) then i wiped my all data, then if the zip file is in my phone the it should be wiped out so, how can i then restore my zip or use it through twrp to restore my old system and everything(if the new rom wasn't good for me?????)
and if i moved the zip file i created using twrp to pc and my phone while flashing new rom got soft brick then how will the pc be able to recognize the phone to be able to move the zip file to it and then flash it through twrp??? i never found an answear through xda yet and hope ucan answear my questions and assure me before flashing my stock rom again! i dont want to lose any info about these process before flashing, if i lost, it would be too late for my precious data you knew!
Nasrk said:
about boot.img yea i have that system on my pc, but i already backed up the stock boot.img before installing my first custom kernel, but after that i didnt work as ur talking about reflashing stock kernel then boot then return to recovery then flash another custom kernel, instead i flashed custom kernel after another, didnt include between each custom kernel a stock kernel flash process, that is why iam having this issue, now even if i tried to flash custom kernel(although iam using now the stock kernel)i will end up soft bricked! but iam now need 1 help if youcan answear me bcs i dunno why icant make another thread,
if i used twrp backup process and created a restore zip for my system(nandroid backup for reflashing stock rom ) then i wiped my all data, then if the zip file is in my phone the it should be wiped out so, how can i then restore my zip or use it through twrp to restore my old system and everything(if the new rom wasn't good for me?????)
and if i moved the zip file i created using twrp to pc and my phone while flashing new rom got soft brick then how will the pc be able to recognize the phone to be able to move the zip file to it and then flash it through twrp??? i never found an answear through xda yet and hope ucan answear my questions and assure me before flashing my stock rom again! i dont want to lose any info about these process before flashing, if i lost, it would be too late for my precious data you knew!
Click to expand...
Click to collapse
First rule before flashing anything to your device - Always backup your data to your pc, cloud ,etc. You never know what can go wrong. Now for your kernel issue as crazy_4_and1 said you have to be on stock kernel to try a new kernel. Just flash boot.img to your boot partition through twrp. You don't have to flash the whole rom. Flashing boot.img doesn't wipe your data. And about your soft brick issue as long as twrp recovery is accessible you can restore your created backup. MTP works in twrp. You can flash your stock rom again without wiping internel storage to resolve any system related problems. Just wipe system, cache, data and dalvik/art. Your app data will be gone but your internal storage will be intact. You can also dirty flash without wiping data but it usually causes problems. If recovery can't be accessed you can flash fastboot rom. Fastboot rom will wipe everything.
callmebutcher101 said:
First rule before flashing anything to your device - Always backup your data to your pc, cloud ,etc. You never know what can go wrong. Now for your kernel issue as crazy_4_and1 said you have to be on stock kernel to try a new kernel. Just flash boot.img to your boot partition through twrp. You don't have to flash the whole rom. Flashing boot.img doesn't wipe your data. And about your soft brick issue as long as twrp recovery is accessible you can restore your created backup. MTP works in twrp. You can flash your stock rom again without wiping internel storage to resolve any system related problems. Just wipe system, cache, data and dalvik/art. Your app data will be gone but your internal storage will be intact. You can also dirty flash without wiping data but it usually causes problems. If recovery can't be accessed you can flash fastboot rom. Fastboot rom will wipe everything.
Click to expand...
Click to collapse
thanks for your great help, i will do as u said and inform you anything if something went wrong, thanks for simplified explanaitions that i think every begginer need it!
Nasrk said:
i recently have tried many kernels like(sesh kernel)(lowrun kernel)(optimus drunk kernel) the problem is while iwas using one of them i restarted my device , to stuck at the brand name(poco)while booting up, i went to twrp many times and flashed many other kernels but got the same issue, only the stock kernel(miui offical kernel) worked and the phone booted up normally, iam so confused, i hope you help me with this issue or provide me info if u had countered this issue before on poco f1 device!
thanks for all your hard work developers!!!
Click to expand...
Click to collapse
Which version of Android u use 9 or 10 please update Android 10 then
After flash any kernal flash Dfe zip then u must boot
But if u are want a best kernel with great performance and less heating than others then u must use amog787 kernel if u use once u stick with it always believed me this kernel is used in oxygen os if you use any oos rom then u know what I am talking
Nasrk said:
thanks for your great help, i will do as u said and inform you anything if something went wrong, thanks for simplified explanaitions that i think every begginer need it!
Click to expand...
Click to collapse
i did a process took 6 hours of my time, faced many errors but went out victorious, so the summary of my work is:
when u back up dont backup 'system' but backup everything its fine,
why?bcs when u want to restore using ur nandroid backup(its twrp backup) during the restore process when flashing 'system' it will give you error, just when u restore make sure system isnot the one beside others, also backup system image it is the system itself.
second, my poco f1 when was soft bricked(i bricked it) if u went to fastboot(if twrp recovery suddenly stopped appearing) in my situation adb didnt recognise the phone, so iwas almost hopeless, also miflash tool whenever i give it rom to flash it gives me errors, but somehow i went back to twrp and flashed the stock rom using usb(otg) thqt was my way to break through this issue, so ( never ever lose twrp, if u lost it, and adb drivers didnt recognise ur device while in fastboot(maybe it was bcs my old drivers or bug) ur doomed)!!!! and nandroid wont backup everything u need, just the apps and ur old system, all ur interneal storage(if u didnt wipe it like me) will still as it is, it isnt backed up with the backup zip!.
i tried many sites (including xda forums) to find solutions for my errors but none of them helped me out, so this is my experience and if someone need help ask me i will try ti help him, and i ask all of who sees this post to share his poco f1 experience bcs no matter developers says, the testers know the situation better!!
goodluck everyone!
varunsngh786 said:
Which version of Android u use 9 or 10 please update Android 10 then
After flash any kernal flash Dfe zip then u must boot
But if u are want a best kernel with great performance and less heating than others then u must use amog787 kernel if u use once u stick with it always believed me this kernel is used in oxygen os if you use any oos rom then u know what I am talking
Click to expand...
Click to collapse
i will try ur kernel but ur way of publishing kernel name is fishy!!
crazy_4_and1 said:
Do you have the fastboot flash archive file on your PC somewhere? Of the stock rom you are currently using. You can check what version of official rom you are currently using and I can send you the boot.img file from the archive (that is the partition that contains the stock kernel). Flashing that is what reverts you back to stock kernel.
All of this is a requirement for flashing a different custom kernel. It goes like this : you flash a custom kernel >dont like it>flash the stock boot.img through recovery>reboot to system>go back to recovery>flash the new kernel you want to test. If I wasnt clear, contact me, I think I can help.
Click to expand...
Click to collapse
Nasrk said:
i did a process took 6 hours of my time, faced many errors but went out victorious, so the summary of my work is:
when u back up dont backup 'system' but backup everything its fine,
why?bcs when u want to restore using ur nandroid backup(its twrp backup) during the restore process when flashing 'system' it will give you error, just when u restore make sure system isnot the one beside others, also backup system image it is the system itself.
second, my poco f1 when was soft bricked(i bricked it) if u went to fastboot(if twrp recovery suddenly stopped appearing) in my situation adb didnt recognise the phone, so iwas almost hopeless, also miflash tool whenever i give it rom to flash it gives me errors, but somehow i went back to twrp and flashed the stock rom using usb(otg) thqt was my way to break through this issue, so ( never ever lose twrp, if u lost it, and adb drivers didnt recognise ur device while in fastboot(maybe it was bcs my old drivers or bug) ur doomed)!!!! and nandroid wont backup everything u need, just the apps and ur old system, all ur interneal storage(if u didnt wipe it like me) will still as it is, it isnt backed up with the backup zip!.
i tried many sites (including xda forums) to find solutions for my errors but none of them helped me out, so this is my experience and if someone need help ask me i will try ti help him, and i ask all of who sees this post to share his poco f1 experience bcs no matter developers says, the testers know the situation better!!
goodluck everyone!
Click to expand...
Click to collapse
Well, I use Pitch Black Recovery, as it patches the installation of stock roms so I does not get erased by stock recovery. Then, the softbrick you are talking about is probably caused by flashing a kernel but not disabling dm-verity (that's a requirement if you want a stock rom/custom kernel combo) someone correct me if I'm wrong. So, the order, for a custom kernel install would be 1. Clean flash your ROM, 2. boot it 3. Reboot to recovery and flash the custom kernel 4. Flash dm-verity disabler 5. Reboot to system.
You just need a boot.img file on your sd card/pc, so you can flash just that file if your rom fails to boot.
I keep my phone unencrypted, so i use DFE/DM-verity disabler zip (literally just google it and it will point you to a thread here on XDA). I had a ****ton of proble.s booting a custom kernel/rooted official MIUI. And it was all due to flash order.
In my case it is : 1. Clean flash ROM 2. Boot it 3. Reboot to recovery 4. Change file system to f2fs (data lartition) 5. Flash Kernel/Magisk/DFE (in that order). 6. Reboot to recovery. Done. If you run into more problems booting, i bet it is due to a flash order mistske. So write here, Ill reflash, stay encrypted and check which order it is that these files need to be flashed in so it boots every time.
crazy_4_and1 said:
Well, I use Pitch Black Recovery, as it patches the installation of stock roms so I does not get erased by stock recovery. Then, the softbrick you are talking about is probably caused by flashing a kernel but not disabling dm-verity (that's a requirement if you want a stock rom/custom kernel combo) someone correct me if I'm wrong. So, the order, for a custom kernel install would be 1. Clean flash your ROM, 2. boot it 3. Reboot to recovery and flash the custom kernel 4. Flash dm-verity disabler 5. Reboot to system.
You just need a boot.img file on your sd card/pc, so you can flash just that file if your rom fails to boot.
I keep my phone unencrypted, so i use DFE/DM-verity disabler zip (literally just google it and it will point you to a thread here on XDA). I had a ****ton of proble.s booting a custom kernel/rooted official MIUI. And it was all due to flash order.
In my case it is : 1. Clean flash ROM 2. Boot it 3. Reboot to recovery 4. Change file system to f2fs (data lartition) 5. Flash Kernel/Magisk/DFE (in that order). 6. Reboot to recovery. Done. If you run into more problems booting, i bet it is due to a flash order mistske. So write here, Ill reflash, stay encrypted and check which order it is that these files need to be flashed in so it boots every time.
Click to expand...
Click to collapse
nice reply and thanks for your concerns, i use disable file encryptions but only when flashing magisk ,never expected to use it with custom kernels, but i have one thing bother me, u said that i need "clean flash rom" but i restored my rom using nandroid while i already had broked my phone(if i flashed any custom kernel other than stock kernel)so is my rom ok or not, do i need to flash a new stock rom? and is it recommended if iwant to change the custom kernel later to another custom kernel to flash stock kernel between them? do u have the flash order between custom kernels over stock rom without causing issues? i would like to know if u have any info, and
thanks for ur info that will help me in future!!!
Nasrk said:
nice reply and thanks for your concerns, i use disable file encryptions but only when flashing magisk ,never expected to use it with custom kernels, but i have one thing bother me, u said that i need "clean flash rom" but i restored my rom using nandroid while i already had broked my phone(if i flashed any custom kernel other than stock kernel)so is my rom ok or not, do i need to flash a new stock rom? and is it recommended if iwant to change the custom kernel later to another custom kernel to flash stock kernel between them? do u have the flash order between custom kernels over stock rom without causing issues? i would like to know if u have any info, and
thanks for ur info that will help me in future!!!
Click to expand...
Click to collapse
Not that you need to flash a stock ROM every time, I'd just do it the first "next" time (if you want to be sure you did nothing wrong, once, you NEED to flash a clean installation). I wouldn't know if your backup is fine if I dont know exactly what partitions did you backup and if you backed your system right after the installation.
It is not recommended it is OBLIGATORY to flash the stock kernel between the flashes.
If changing kernels, only, I just flash the stock boot.img, reboot to system to see if all is good, then reboot to recovery and flash the kernel+magisk (I cant remember exactly, but I think you lose root if you flash the stock kernel). Ill make a reminder to check.
crazy_4_and1 said:
Not that you need to flash a stock ROM every time, I'd just do it the first "next" time (if you want to be sure you did nothing wrong, once, you NEED to flash a clean installation). I wouldn't know if your backup is fine if I dont know exactly what partitions did you backup and if you backed your system right after the installation.
It is not recommended it is OBLIGATORY to flash the stock kernel between the flashes.
If changing kernels, only, I just flash the stock boot.img, reboot to system to see if all is good, then reboot to recovery and flash the kernel+magisk (I cant remember exactly, but I think you lose root if you flash the stock kernel). Ill make a reminder to check.
Click to expand...
Click to collapse
iam waiting for your response about root if it get earsed or not
Nasrk said:
iam waiting for your response about root if it get earsed or not
Click to expand...
Click to collapse
With flashing the stock kernel, it does.
Newer custom kernels apply a patch so magisk stays intact
Stock ones do not.
Hello everyone, a little question. Now I'm running Android 10 miui 11.0.1 rooted with magisc and using pitch black recovery.. It supports the Ota update the same as stock recovery.
My question now is if I upgrate from MIUI 11.0.3 to miui 12.0.3 what will happens with the root? Will I need to delete the data partition?.. Maybe the new version fill found the phone rooted and the phone won't boot.. So I will need to format data..
Pleae answer to me guys asap. I can update the rom using twrp recovery.. But i don't want to lose all my data from the phone if it found the root
Sorry for my bad English..
Phone : mi 8 lite
Rom : official global rom miui 11.0.3 rooted with magisk
the update is : miui12.0.3 (860mb)
derrekgamer said:
Hello everyone, a little question. Now I'm running Android 10 miui 11.0.1 rooted with magisc and using pitch black recovery.. It supports the Ota update the same as stock recovery.
My question now is if I upgrate from MIUI 11.0.3 to miui 12.0.3 what will happens with the root? Will I need to delete the data partition?.. Maybe the new version fill found the phone rooted and the phone won't boot.. So I will need to format data..
Pleae answer to me guys asap. I can update the rom using twrp recovery.. But i don't want to lose all my data from the phone if it found the root
Sorry for my bad English..
Phone : mi 8 lite
Rom : official global rom miui 11.0.3 rooted with magisk
the update is : miui12.0.3 (860mb)
Click to expand...
Click to collapse
Probably you will need to root again!
It will format the partitions before flash the new one.
.
persona78 said:
Probably you will need to root again!
It will format the partitions before flash the new one.
.
Click to expand...
Click to collapse
Hmm.. It is a simple Ota update so maybe it won't format anything.. But I'm thinking after Ota update done maybe the root is gone.. And for the Android 10 if you root your phone after flashing magisk always need to perform a data format..so I don't want to lose anything yet.. I don't know.. ?
derrekgamer said:
Hmm.. It is a simple Ota update so maybe it won't format anything.. But I'm thinking after Ota update done maybe the root is gone.. And for the Android 10 if you root your phone after flashing magisk always need to perform a data format..so I don't want to lose anything yet.. I don't know.. ?
Click to expand...
Click to collapse
Hmmm....
Better to understand how magisk perform the root to understand where files go, i think it do something in boot.img and that is one if the images that Will be flashed i know, i updated it yesterday and a little tweak i had done was gone.
persona78 said:
Hmmm....
Better to understand how magisk perform the root to understand where files go, i think it do something in boot.img and that is one if the images that Will be flashed i know, i updated it yesterday and a little tweak i had done was gone.
Click to expand...
Click to collapse
Yes the magisc use boot.img for root. So the new Ota update will get for sure a new boot.img.. So my phone will no more be rooted.. And if root after that I need to clear the data.. So.. No reason.. Better no update ?
persona78 said:
Hmmm....
Better to understand how magisk perform the root to understand where files go, i think it do something in boot.img and that is one if the images that Will be flashed i know, i updated it yesterday and a little tweak i had done was gone.
Click to expand...
Click to collapse
i updated. and the phone is stuck at miui logo. Formated data and works again.
derrekgamer said:
i updated. and the phone is stuck at miui logo. Formated data and works again.
Click to expand...
Click to collapse
You can install stock recovery and do factory reset, i think it will do a better reset than TWRP.
persona78 said:
You can install stock recovery and do factory reset, i think it will do a better reset than TWRP.
Click to expand...
Click to collapse
nono. i did reset factory using twrp and works very fine, i got a very good twrp That keep force encrypt
derrekgamer said:
nono. i did reset factory using twrp and works very fine, i got a very good twrp That keep force encrypt
Click to expand...
Click to collapse
i tell you that because i think stock recovery reset some other partitions that TWRP doesn´t reset. And you can always change again to TWRP.
But it worked for you is what matters.
I've updated my mi 8 lite. I am using orange fox recovery, updated it using OTA (orange fox also sports it since you keep some auto generated files at sdcard) and I had not to format data partition. In fact, the update did not erase any user info. The only thing I had to do was to flash magisk zip again and voila, root is back and full functional again.