Related
used oden to flash CWM. now i cant boot into android, it just keeps kicking me into CWM recovery.
anyone see this? any suggestions? would a wipe fix it?
did you flash a rom if so which one?
no ROMs, simply just tried flashing CWM via Odin
may i ask why 2.3.5?
what were you trying to do?
i am still able to get into Download mode to flash files via Odin, so i dont think all is lost. but, still just stuck in recovery. when i try to reboot it just takes me right back into recovery. i may have flashed an incorrect version of CWM which could be the cause of this problem. if that was the case, any ideas as to how i can get back into a proper boot?
xwhofarted said:
may i ask why 2.3.5?
what were you trying to do?
Click to expand...
Click to collapse
I was trying to flash CWM so i could flash a custom ROM. Had this phone forever and was just looking to try out some ROMs out there.
As long as you odin cwm none of your os is really touched.
try the cwm 4 fixed for cm7. http://forum.xda-developers.com/atta...2&d=1311907538
Now when you reboot your device the stock kernel will over right the cwm.
also make sure you put the odin file in the PDA section.
So basically flash the new cwm and try booting into normal that should get you back where you started from. 100% stock.
that link didnt work. tried searching for the thread without any luck
for some reason it truncated the link with a '...' and it thinks that is part of the hyperlink
dl.dropbox.com/u/14764513/cwm4_fixed_for_cm7-ODIN.tar <- cwm 4 fixed for cm7
thanks.. so i flashed this via odin. same problem. i start the phone. the samsung logo comes up. it disappears for a second. then it comes back up and kicks me into recovery.
weird right? any suggestions
ok then what is your endgame?
Now before you said you flashed just the CWM, may i ask why...if you did not intend to flash a rom? were you going to flash a Kernel or obtain root?
Perhaps you should try this
Download this: http://forum.xda-developers.com/showthread.php?t=1278838
It is a custom kernel.
Now Flash CWM with odin
Put battery back in [dont touch power button yet]
Hold down BOTH volume and Power all at once * Dont let go until you see Samsung Logo.
[should still be plugged into pc via usb]
You will boot into CWM
using the volume up and down-Scroll down to Mounts and storage [select it by hitting the power button]
Then scroll to Mout USB storage
~now you should be able to see your SDCard as storage on your PC, put the Kernel some where on your SD Card~
[back on your phone Then Select Unmount
Scroll to ****Go bacK***** [select]
Scroll to install zip from sd card [select]
Select choose zip from sdcard
Navigate to where you have the zip
Select it
Scroll down to Yes-Flash........
Let the phone do its thing!
Good luck!
Your bootlooped...if you can get into cwm wipe all three and flash a rom thats compatible with the version of cwm you have installed. Or odin back to stock and start over...
droidstyle said:
Your bootlooped...if you can get into cwm wipe all three and flash a rom thats compatible with the version of cwm you have installed. Or odin back to stock and start over...
Click to expand...
Click to collapse
yea i started to figure that was the case. if i flash the full odin package for EH03 via odin and that will start me at the beginning?
thanks again for everyones help.
Yes,
Keep in mind all data will be gone [except on your sd card like photos and what not]
Good Luck!
xwhofarted said:
Yes,
Keep in mind all data will be gone [except on your sd card like photos and what not]
Good Luck!
Click to expand...
Click to collapse
yes i am aware. did however make a backup of my current setup. i am stuck in recovery, but recovery still works. so i was able to make a backup and hopefully i can restore at some point. also, i had been rooted earlier and immediately made a tb backup of my apps. all is not lost
thanks a bunch guys! happy holidays ill let you know if i succeed
This may sound dumb but
make sure you are NOT hitting "reboot recovery" and you ARE hitting "reboot system now"
xwhofarted said:
dl.dropbox.com/u/14764513/cwm4_fixed_for_cm7-ODIN.tar <- cwm 4 fixed for cm7
Click to expand...
Click to collapse
the link is broken can you re upload it ?
xwhofarted said:
As long as you odin cwm none of your os is really touched.
try the cwm 4 fixed for cm7. http://forum.xda-developers.com/atta...2&d=1311907538
Now when you reboot your device the stock kernel will over right the cwm.
also make sure you put the odin file in the PDA section.
So basically flash the new cwm and try booting into normal that should get you back where you started from. 100% stock.
Click to expand...
Click to collapse
that link is broken can you upload up the tar file
Hi. I'm running CyanogenMod on my Samsung Galaxy S II i777 (the AT&T one). I was running UnNamed ROM on it, and that had ClockworkMod Recovery v5.0.2.7. But after I flashed CyanogenMod, the ClockworkMod Recovery downgraded to v5.0.2.3. How can I update back to the 5.0.2.7 version?
The reason I ask is because in v5.0.2.3, the backup options are limited, and it doesn't allow me to restore my old, v5.0.27 Nandroid backups in case I need to. I've done a Google search and searched the XDA forums, and the only help I found was to use the ROM Manager app. However, in this post, user creepyncrawly advises me not to use ROM Manager because it "has problems on this phone." I also found some custom kernels, but those were for different phone models.
So how can I update ClockworkMod Recovery without losing any data?
You need to install a kernel that has the newer CWM.
Your post doesn't make sense unless you installed a VERY old CM7 release, considering that the CWM 5.0.2.7 binary in my kernels was pulled FROM CyanogenMod.
I made a mistake. I meant to say that I have CWM Recovery 5.0.2.6, not 5.0.2.7. But my problem is still the same: in CWM Recovery, I don't have the option to "Advanced Restore from SD card." Even when I move my old Nandroid backups (created under CWM Recovery 5.0.2.7) to my phone, they're still not picked up by CWM Recovery 5.0.2.6.
Anyway, thanks for letting me know how to update. Any zImage from any custom ROM will work, right? I'm just trying to do this without incrementing the flash counter on my phone. So I need to choose one from this subforum, and flash with Mobile Odin?
Completely_Clueless said:
I made a mistake. I meant to say that I have CWM Recovery 5.0.2.6, not 5.0.2.7. But my problem is still the same: in CWM Recovery, I don't have the option to "Advanced Restore from SD card." Even when I move my old Nandroid backups (created under CWM Recovery 5.0.2.7) to my phone, they're still not picked up by CWM Recovery 5.0.2.6.
Anyway, thanks for letting me know how to update. Any zImage from any custom ROM will work, right? I'm just trying to do this without incrementing the flash counter on my phone. So I need to choose one from this subforum, and flash with Mobile Odin?
Click to expand...
Click to collapse
Flashing in CWM won't trip the flash counter. I suggest using SiyahKernel, since I'm pretty sure Entropy's Daily Driver doesn't support CM7.
Solved!
jcracken said:
Flashing in CWM won't trip the flash counter. I suggest using SiyahKernel, since I'm pretty sure Entropy's Daily Driver doesn't support CM7.
Click to expand...
Click to collapse
This worked beautifully! I now have CWM Recovery 5.0.2.7, and my phone info shows that I have SiyahKernel as well.
Thank you very much!
jcracken said:
Flashing in CWM won't trip the flash counter. I suggest using SiyahKernel, since I'm pretty sure Entropy's Daily Driver doesn't support CM7.
Click to expand...
Click to collapse
It doesn't support CM7, but should be able to restore a CM7 Nandroid.
Hi everyone.
i rooted my phone with this guide which installed a based CWM recovery on my phone with Siyah-s2-v6.0b4.tar using Odin.
Now i want to run a touch CWM recovery but no matter how i tried- no way worked and i always get the based CWM recovery again.
I tried ROM manager and RECOVERY tools but none of these actually worked (although i got success messages).
I also tried to download the recovery file from the official site of CWM, but when i tried to copy it to my sd card an error message popped out saying copy can't be done and the device is not connected or working or something.. i can copy other zip files without any problem.
can anyone help?
thanks.
1) Do not use Rom Manager with the SGS2. It will break recovery and/or cause bootloops eventually. It may even brick your phone. You don't need it.
2) Any recovery flashed independently of the kernel on the SGS2 will only persist until the next reboot, which is why what you're trying isn't working. If you want a touch version of CWM, flash/run a kernel which has this. Which kernels ? Read the kernel threads in the development section (I don't use PhilZ on my SGS2, but his comes to mind as I use it on my I9505).
heywebi
MistahBungle said:
1) Do not use Rom Manager with the SGS2. It will break recovery and/or cause bootloops eventually. It may even brick your phone. You don't need it.
2) Any recovery flashed independently of the kernel on the SGS2 will only persist until the next reboot, which is why what you're trying isn't working. If you want a touch version of CWM, flash/run a kernel which has this. Which kernels ? Read the kernel threads in the development section (I don't use PhilZ on my SGS2, but his comes to mind as I use it on my I9505).
Click to expand...
Click to collapse
thank you very much! i'm relieved i didn't brick my phone, that could have been a mess..
flashing kernels is like regular flashing? just installing the zip file? do i need to wipe any data or cache or something?
thanks for your response.
Follow the flashing instructions for the kernel in question to the letter (always on the first page of the kernel thread, always very clear/precise/easy to follow).
MistahBungle said:
.... I use it on my I9505).
Click to expand...
Click to collapse
In that case, great to still see you in the s2 forums
Sent from a galaxy far, far away
So here's the deal, I'm really nervous and stressed because i offered my friend to root and flash cyanogenmod on his sg s3 (i9300 US international) , so i rooted without a problem then copied cyanogenmod and gapps to internal storage. I went to flash both via clockwork recovery, I did everything I was so supposed to do and while flashing cyanogen mode i got install interupted message (along with status 7 or something like that) from that point on i can't get out of clockwork recovery, i tried everything including wiping all data, only 2 screens i can get to are clockwork recovery and downloading mode, I think i should flash stock rom via Odin but I don't know which region version to download because US or UK international aren't option for some reason. I really really need help on this one guys, I'm freaking the hell out. What should I do
thanks
TheOxi said:
So here's the deal, I'm really nervous and stressed because i offered my friend to root and flash cyanogenmod on his sg s3 (i9300 US international) , so i rooted without a problem then copied cyanogenmod and gapps to internal storage. I went to flash both via clockwork recovery, I did everything I was so supposed to do and while flashing cyanogen mode i got install interupted message (along with status 7 or something like that) from that point on i can't get out of clockwork recovery, i tried everything including wiping all data, only 2 screens i can get to are clockwork recovery and downloading mode, I think i should flash stock rom via Odin but I don't know which region version to download because US or UK international aren't option for some reason. I really really need help on this one guys, I'm freaking the hell out. What should I do
Click to expand...
Click to collapse
error 7 has to do with old recovery. download the latest cwm (at least 6.0.4.4), twrp or philz touch put it on external sd card and flash it through recovery. restart recovery and you should be able to flash cm11
I don't think you have a nandroid backup?
what do you mean with us and uk versions are no option?
Darkened_Sky said:
error 7 has to do with old recovery. download the latest cwm (at least 6.0.4.4), twrp or philz touch put it on external sd card and flash it through recovery. restart recovery and you should be able to flash cm11
I don't think you have a nandroid backup?
what do you mean with us and uk versions are no option?
Click to expand...
Click to collapse
I meant no option as in I can't see it as download option anywhere, only the other regions. Other thing is, odin recognizes S3 while in downloading mode but my computer itself doesn't for some reason. It recognized it before this whole incident (hence files being on the storage) maybe me puting the files on internal storage before was the mistake.Btw no i don't have backup, I guess Im dumb but I didnt think i needed it, thought it was simple process without any complications.
TheOxi said:
I meant no option as in I can't see it as download option anywhere, only the other regions. Other thing is, odin recognizes S3 while in downloading mode but my computer itself doesn't for some reason. It recognized it before this whole incident (hence files being on the storage) maybe me puting the files on internal storage before was the mistake.
Click to expand...
Click to collapse
so which cwm version did you use?
if it's an old one try it the way I mentioned above. I would recommend philz touch (can be flashed through cwm) because there you can choose in wipe options to clean to install a new rom and then flash cm11. and you can also make an efs backup if you haven't already done it.
so maybe you do not need to reflash the stock rom
Darkened_Sky said:
so which cwm version did you use?
if it's an old one try it the way I mentioned above. I would recommend philz touch (can be flashed through cwm) because there you can choose in wipe options to clean to install a new rom and then flash cm11. and you can also make an efs backup if you haven't already done it.
so maybe you do not need to reflash the stock rom
Click to expand...
Click to collapse
latest cm11.2 nightly, but how am i supposed to put philz touch on external storage if my pc doesn't recognize the device, only Odin does. what would happen if I'd flash the stock rom with Odin right now? I dont mind losing all the data
TheOxi said:
latest cm11.2 nightly, but how am i supposed to put philz touch on external storage if my pc doesn't recognize the device, only Odin does. what would happen if I'd flash the stock rom with Odin right now? I dont mind losing all the data
Click to expand...
Click to collapse
Why not use Philz recovery tar via Odin ???
STICKYS
http://forum.xda-developers.com/showthread.php?t=2344125
UNDERSTAND FIRST
http://forum.xda-developers.com/showthread.php?t=2362743
JJEgan said:
Why not use Philz recovery tar via Odin ???
STICKYS
http://forum.xda-developers.com/showthread.php?t=2344125
UNDERSTAND FIRST
http://forum.xda-developers.com/showthread.php?t=2362743
Click to expand...
Click to collapse
Cool I got the Philz now but there's still the problem of getting different cm or current one into external storage also i cant access the old cm file on philz recovery now, i think it was big mistake putting the files into internal storage instead of external, any idea how to get my pc to recognize the device? it had no problem before the screwup
Don't you have a external sd card reader? Or put your sd card in another phone and copy from there..
tallman43 said:
Don't you have a external sd card reader? Or put your sd card in another phone and copy from there..
Click to expand...
Click to collapse
considering i dont have that option, do you see any other way around this? Im quiet in a pickle over here
TheOxi said:
considering i dont have that option, do you see any other way around this? Im quiet in a pickle over here
Click to expand...
Click to collapse
Then if you managed to flash Philz with Odin you must flash back to stock using Odin....
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.