just for my knowledge, Im wondering about having to flash the 4.1 and 4.2 boot.img depending on which rom i use. I looked in twrp backup, and it backs up the boot.image doesnt it? doesnt this mean it also restores it? meaning no need to fastboot it?
Thanks in advance
Mikey F said:
just for my knowledge, Im wondering about having to flash the 4.1 and 4.2 boot.img depending on which rom i use. I looked in twrp backup, and it backs up the boot.image doesnt it? doesnt this mean it also restores it? meaning no need to fastboot it?
Thanks in advance
Click to expand...
Click to collapse
Short answer, no. Fast boot the image every time. Long answer is to search Google and these forums to understand what a boot.img is and why it needs to be flashed
Kraizk said:
Short answer, no. Fast boot the image every time. Long answer is to search Google and these forums to understand what a boot.img is and why it needs to be flashed
Click to expand...
Click to collapse
Ok, no probs, thank you very much Kraizk!!
:good:
Only need to flash boot.img when theres a custom kernel all stock boot.img will work for diff roms with stock kernel bit its still a good habit to flash boot.img when flashing new Rom if you don't know what your doing to prevent problems
Sent from my HTC One X+ using XDA Premium HD app
ok, so, i made a backup with twrp of my stock rom (im in uk, my phone is non branded) and then flashed lloir 4.2.1 rom, followed by the reccommended kernel, which is great, I love aosp. but i didnt save my old boot.img from my stock , which was 4.1.2? if i want to flash my backup of that, do i need to flash a different kernel? and if so, which one?
Mikey F said:
ok, so, i made a backup with twrp of my stock rom (im in uk, my phone is non branded) and then flashed lloir 4.2.1 rom, followed by the reccommended kernel, which is great, I love aosp. but i didnt save my old boot.img from my stock , which was 4.1.2? if i want to flash my backup of that, do i need to flash a different kernel? and if so, which one?
Click to expand...
Click to collapse
I believe TWRP should have saved your boot.img unless you specified otherwise. If you want to restore from a backup, you'll need to transfer the boot.img from the backup to your computer (there should be a folder containing it in your internal memory), restore the backup, and then use the "fastboot flash boot boot.img" command to flash your old boot.img. If you really did lose your old boot.img somehow, I suspect you can find a stock one floating around the forums.
Related
Today I got my S2 replaced as there was a lit pixel, the stock rom on it currently isn't actually listed here: http://forum.xda-developers.com/showthread.php?t=1075278
It's XWKI5
How do I got about extracting the rom in a way that will contribute to that thread? Won't touch it until I can safely get the rom off and saved for the thread
EDIT: And to add to this, if I do extract the rom would it be wise to update the rom first via kies or just leave it as factory and supply it?
Anyone got any ideas? Not wanting to bump but can't use until I get it extracted >_>
Odin flash Clockworkmod recovery then make a nandroid backup of it to get the boot.img and system.img
Sent from my GT-I9100 running on CheckRom RevoHD™ v4.0
Will do! Thank you!
kyleforge said:
Odin flash Clockworkmod recovery then make a nandroid backup of it to get the boot.img and system.img
Click to expand...
Click to collapse
Flashing CWM via Odin will overwrite "boot.img" with the CWM kernel
But for the system it'll work, yeah
I have done the backup, who would be best to sent it to? Not sure how it would need to be prepared for contribution. Does the backup include kernal etc? If so how would I go about taking the kernal from it and flashing it on with miui?
Yes i'm new, but am loving it
I've unlocked the bootloader of my Desire X, but whenever I try to install Android revolution, it gives me a bunch of errors saying the file couldn't be opened, any rom I stick on the SD has trouble being read by Nexus recovery , I've tried 3 other SD cards. Also after I rooted the phone, I still can't give applications such as Titanium backup root privileges because it says it couldn't find the root binary?
I've got Nexus recovery installed on stock 4.2.
I've also wanted to try other recoveries, is it as simple as flashing a new one through fastboot or do I have to do something else?
I really need help, so I'd be grateful for any you can offer me
Fahim92 said:
I've unlocked the bootloader of my Desire X, but whenever I try to install Android revolution, it gives me a bunch of errors saying the file couldn't be opened, any rom I stick on the SD has trouble being read by Nexus recovery , I've tried 3 other SD cards. Also after I rooted the phone, I still can't give applications such as Titanium backup root privileges because it says it couldn't find the root binary?
I've got Nexus recovery installed on stock 4.2.
I've also wanted to try other recoveries, is it as simple as flashing a new one through fastboot or do I have to do something else?
I really need help, so I'd be grateful for any you can offer me
Click to expand...
Click to collapse
If you are on stock 4.2, you also have HBoot 1.25, so maybe you can't install these roms because your HBoot it isn't 1.24 or lower.
Try to re-flash stock recovery, then flash neXus' again.
Or maybe it can be kernel stuff, did you flash the attached boot.img?
JoseluSpark said:
If you are on stock 4.2, you also have HBoot 1.25, so maybe you can't install these roms because your HBoot it isn't 1.24 or lower.
Try to re-flash stock recovery, then flash neXus' again.
Or maybe it can be kernel stuff, did you flash the attached boot.img?
Click to expand...
Click to collapse
But the rom does say it is available for 1.25+
and do I have to flash a stock recovery? Can't I install another recovery (not stock) by using the fastboot command?
Fahim92 said:
But the rom does say it is available for 1.25+
and do I have to flash a stock recovery? Can't I install another recovery (not stock) by using the fastboot command?
Click to expand...
Click to collapse
Also, is there a recovery that's sure to work with Hboot 1.25 JB?
If so, can I just flash that recovery over my current one?
Anybody?
Fahim92 said:
Anybody?
Click to expand...
Click to collapse
If you want, PM me your skypename and i'll guide you step by step.
ShadowCodeGaming said:
If you want, PM me your skypename and i'll guide you step by step.
Click to expand...
Click to collapse
I don't have Skype
Can you just provide help for me on here? I'd really appreciate it.
Here's my situation in case I wasn't clear in OP, I installed the Nexus recovery but it wasn't able to flash the rom I wanted, so now I want to flash another recovery, and was just wondering whether I could just flash another recovery on top of the old one or if I have to do something else?
Fahim92 said:
I don't have Skype
Can you just provide help for me on here? I'd really appreciate it.
Here's my situation in case I wasn't clear in OP, I installed the Nexus recovery but it wasn't able to flash the rom I wanted, so now I want to flash another recovery, and was just wondering whether I could just flash another recovery on top of the old one or if I have to do something else?
Click to expand...
Click to collapse
Look in the 'Desire X Original Android Development' Section for a TWRP recovery for JB hboot. It's working great for me. You can flash it the same way you flashed the NexusRecovery (fastboot)
ShadowCodeGaming said:
Look in the 'Desire X Original Android Development' Section for a TWRP recovery for JB hboot. It's working great for me. You can flash it the same way you flashed the NexusRecovery (fastboot)
Click to expand...
Click to collapse
So I can just flash it over the current recovery I have? I don't need to go back to stock?
Right
Sent from my black pearl using Tapatalk 2
Fahim92 said:
So I can just flash it over the current recovery I have? I don't need to go back to stock?
Click to expand...
Click to collapse
Yeah. You can just flash it over the NexusRecovery. You never have to go back to stock.
Okay, I just flashed TWRP over my current recovery.
I've tried to flash Sense revolution and it just fails through TWRP, why is this?
Wipe the phone and try again.
Maybe It can be because of MD5 verification. Only happens on that ROM?
Enviado desde mi HTC Desire X
Fahim92 said:
Okay, I just flashed TWRP over my current recovery.
I've tried to flash Sense revolution and it just fails through TWRP, why is this?
Click to expand...
Click to collapse
Try both ics and jb twrp
Sent from my HTC Desire X using xda app-developers app
I'm having troubles when i wan't to install this ROM :
http://forum.xda-developers.com/showthread.php?t=2555350 .
I'm using the dl from the first post, i'm using fastboot flash boot boot.img (the boot.img i'm getting from the zip-file).
I do a factory reset from the bootloader, then i do a factory reset in the twrp recovery
then i flash the boot.img in the jb hboot 1.25.0002
then i flash the zip file and i reboot.
but i never get to see the boot image. just a black screen...
Can someone help me?
tcornelis said:
I'm having troubles when i wan't to install this ROM :
http://forum.xda-developers.com/showthread.php?t=2555350 .
I'm using the dl from the first post, i'm using fastboot flash boot boot.img (the boot.img i'm getting from the zip-file).
I do a factory reset from the bootloader, then i do a factory reset in the twrp recovery
then i flash the boot.img in the jb hboot 1.25.0002
then i flash the zip file and i reboot.
but i never get to see the boot image. just a black screen...
Can someone help me?
Click to expand...
Click to collapse
You're definitely using a TWRP recovery made for JB hboot? @GtrCraft, did you put the right boot.img inside the zip?
Also, you can try flashing a custom JB kernel of your choice.
@dansou901 I believe so, flashing this (http://forum.xda-developers.com/showthread.php?t=2344254) work like a charm (except for the rom that hasn't got any wifi, ...)
How can i check to be sure?
tcornelis said:
@dansou901 I believe so, flashing this (http://forum.xda-developers.com/showthread.php?t=2344254) work like a charm (except for the rom that hasn't got any wifi, ...)
How can i check to be sure?
Click to expand...
Click to collapse
For booting that ROM a CM kernel is needed. As you have installed one (if it works like you said), you need to install a JB Sense kernel (just pick one from Original Android Development section). Then reinstall SuperSense and you should be fine.
I'll give that a go and let you know
@dansou901 , i've used this boot.img (http://forum.xda-developers.com/showthread.php?t=2337389) because i've already been able to flash that rom as well.
but now i can't seem to get rid of my previous custom rom. i've done a factory reset, i wiped everything there is to wipe, i've flashed the above boot.img and supersense but it's still another custom rom on my device :s
tcornelis said:
@dansou901 , i've used this boot.img (http://forum.xda-developers.com/showthread.php?t=2337389) because i've already been able to flash that rom as well.
but now i can't seem to get rid of my previous custom rom. i've done a factory reset, i wiped everything there is to wipe, i've flashed the above boot.img and supersense but it's still another custom rom on my device :s
Click to expand...
Click to collapse
That's a CM kernel as well. I told you to use a Sense kernel. Use this one for example: http://forum.xda-developers.com/showthread.php?t=2483489
and your recovery should work again as expected. Btw, which recovery did you install? Please give the link.
this is the twrp recovery.img http: // teamw . in / project / twrp2 / 140 (yeah, can't post outside links yet)
i'll give that one a shot
tcornelis said:
this is the twrp recovery.img http: // teamw . in / project / twrp2 / 140 (yeah, can't post outside links yet)
i'll give that one a shot
Click to expand...
Click to collapse
That one's made for ICS, if I recall correctly... Don't use it. Use this one instead: http://forum.xda-developers.com/showthread.php?t=2099513 But be sure to use a JB version.
After changing my recovery, finally i was able to flash the custom rom. I used the boot.img you gave me, but is that going to affect some of the features in the rom?
And i would like to thank you allready
tcornelis said:
After changing my recovery, finally i was able to flash the custom rom. I used the boot.img you gave me, but is that going to affect some of the features in the rom?
And i would like to thank you allready
Click to expand...
Click to collapse
No, it's not. You can however choose the kernel yourself as I said... But keep in mind that it has to be a JB Sense kernel (just read the OP of the kernel thread carefully, then you'll know). For recoveries, keep this in mind.
No Title Here
The boot.img in the SuperSENSE-dx5 zip is stock, every JB Sense kernel should work though
GtrCraft said:
The boot.img in the SuperSENSE-dx5 zip is stock, every JB Sense kernel should work though
Click to expand...
Click to collapse
His problem wasn't the kernel but the wrong recovery he used, it's fixed now.
Sent from my HTC Desire X using XDA Premium 4 mobile app
dansou901 said:
His problem wasn't the kernel but the wrong recovery he used, it's fixed now.
Sent from my HTC Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Perfect :good:
So I finally tried some AOSP, but missed my camera immensely so I went to switch back to my backup that I made in TWRP.
Unfortunately AOSP roms use CWM recovery and it won't recognize my TWRP so I've tried to redo the Dual Recovery method but since I no longer have stock kernel it fails.
Now I've also tried to use fastboot to flash a boot.img which I thought was a stock kernel....but obviously I was wrong or it didn't want to work.
Either way as of now I'm using FlashTool to flash stock image, then root, then install DualRecovery again and THEN restore backup.
Does anyone know where I went wrong and hopefully provide a faster solution in case I go back to trying ASOP again? Maybe backup in CWM next time?
Now I do have to flashable DualRecovery.zip that I did try in CWM but it didn't work either, I'm guessing since I didn't have stock kernel...
Thanks in advanced. Why didn't Sony just have a dedicated recovery partition!
Flash doom Lords kernel (v9 is it?) which has twrp, restore back up, done
Mr.R™ said:
Flash doom Lords kernel (v9 is it?) which has twrp, restore back up, done
Click to expand...
Click to collapse
Thanks, I thought about that but I didn't want any other kernel than stock. Couldn't find stock, but I went the long route and now I'm back in business!
ZPaul2Fresh8 said:
Thanks, I thought about that but I didn't want any other kernel than stock. Couldn't find stock, but I went the long route and now I'm back in business!
Click to expand...
Click to collapse
the recoveries in the original development sections are actualy stock kernels with recovery, you could use those instead if you dont want dooms modded/custom kernel
Envious_Data said:
the recoveries in the original development sections are actualy stock kernels with recovery, you could use those instead if you dont want dooms modded/custom kernel
Click to expand...
Click to collapse
Well I did try to use the dual recovery but it didn't work. It says it is only for stock kernel so I didn't expect it to, but I had to try...
@ZPaul2Fresh8
EDIT: DON'T INSTALL IF YOU STILL WANT TO USE CM!!!
It won't boot the system of cm if you flashed the twrp img, just flash it if you want to go to a backup!
"
It was very easy for me, at the end i had a twrp 2.7.0.0 in my cm11'd Z2, you need pc, and usb cable, and fastboot and adb drivers, lol its way easier than flashing .ftf, go to http://forum.xda-developers.com/showthread.php?t=2764971 and download the zip and extract it, follow this tout: http://forum.xda-developers.com/showthread.php?t=1752270 and you will be all good...
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.