Related
Okay so i had a rooted phone with xionia kernel and decided to use my nandroid backup to restore to stock VM Rom. Well like an idiot i factory reset from android GUI with stock VM ROM and forgot i had thuderc custom recovery. Now my phone is stuck in recovery mode and i cant flash to another rom or restore my nandroid backup. i"ve seen posts about this specific problem and people just get refered to a thread thats not specific for my problem. If i can get any help to get my phone back to stock or rooted just so i can still use it, it would be deeply appreciated.
You can try to help yourself by using the RomTools present here:
http://forum.xda-developers.com/showthread.php?t=971245
Other than that the only other solution I can see right now is to enter in Emergency\Download mode and flash with KDZ.
Please follow the guide here: http://prepaidandroid.org/index.php?title=How_to_restore_your_Optimus_V_to_almost_original_condition
and try to flash the stock recovery again.
chavezezequiel said:
Okay so i had a rooted phone with xionia kernel and decided to use my nandroid backup to restore to stock VM Rom. Well like an idiot i factory reset from android GUI with stock VM ROM and forgot i had thuderc custom recovery. Now my phone is stuck in recovery mode and i cant flash to another rom or restore my nandroid backup. i"ve seen posts about this specific problem and people just get refered to a thread thats not specific for my problem. If i can get any help to get my phone back to stock or rooted just so i can still use it, it would be deeply appreciated.
Click to expand...
Click to collapse
truely kdz is the best option to revive your phone chk out this thread http://forum.xda-developers.com/showthread.php?t=883314 download your desired stock rom and flash via kdz if u need any file to download i.e.pc suite etc just get it from the thread i created http://forum.xda-developers.com/showthread.php?p=12959016#post12959016 and follow the guide from error i bet it is the best guide to revive the phone.
FIRST YOU CAN TRY THE GUIDE PROVIDED BY MARIO AS YOUR PHONE IS ABLE TO BOOT INTO RECOVERY GIVE IT A TRY IF IT DOESNT WORK OUT TRY MINE
good luck
k thanks gonna try to use romtools and flash my stock recovery. i"ll keep updated.
marioemp2k7 said:
You can try to help yourself by using the RomTools present here:
http://forum.xda-developers.com/showthread.php?t=971245
Other than that the only other solution I can see right now is to enter in Emergency\Download mode and flash with KDZ.
Please follow the guide here: http://prepaidandroid.org/index.php?title=How_to_restore_your_Optimus_V_to_almost_original_condition
and try to flash the stock recovery again.
Click to expand...
Click to collapse
k so i tried flashing the recovery and it said everything worked but im back to thunderc recovery. Was i supposed to place the stock recovery in a certain folder to be flashed to the phone?
Got It Working
I Finally got it. I forgot to place the stock recovery in the romtools folder. THANK YOU GUYS for your help. i really appreciate it!
im really sorry to bring this up but i am trying this is NOTHING is working. I really need this fixed... Its driving me crazy.
iv tried flashing the recovery doesn't work, tried flashing a new rom, doesn't work. i dont know what to do!\
never mind, i had to manually remount and un mount system to get it to work, thanks a lot!!!!!!!!!
So let me see if i understand this correctly. From what i have read, it looks like i cant install CWM recovery without installing a custom Kernel? So me backing up my stock set up is pretty much out of the question? So everytime i wish to install a different custom rom i am essentailly reinstalling CWM recovery as well?
How can i backup my stock set up and restore it if i screw something up, or install a rom that i am not happy with? I am coming rom an epic 4g on sprint and it was different with that galaxy phone.
Flash a CF Root kernel that matches your firmware, create your near stock b/u. This will be your point to fall back on. 99.99% of ROMs you flash will include a kernel, that also has CWM, it may be a different version but they all work the same, for the most part. The majority of kernels include CWMr 5 or higher.
You'll always have the option of restoring your "stock" b/u so long as you don't delete it. Titanium b/u is the ticket to back up all your apps and their data rather than having to extract those apps/data from a CWM b/u.
You only have to root once. The easiest way to unroot is to flash a stock firmware. Flashing a stock kernel back on after you've rooted will replace CWM recovery with stock recovery, but you'll remain rooted. Probably doesn't address all your questions, but you've got a start.
mudferret said:
Flash a CF Root kernel that matches your firmware, create your near stock b/u. This will be your point to fall back on. 99.99% of ROMs you flash will include a kernel, that also has CWM, it may be a different version but they all work the same, for the most part. The majority of kernels include CWMr 5 or higher.
You'll always have the option of restoring your "stock" b/u so long as you don't delete it. Titanium b/u is the ticket to back up all your apps and their data rather than having to extract those apps/data from a CWM b/u.
You only have to root once. The easiest way to unroot is to flash a stock firmware. Flashing a stock kernel back on after you've rooted will replace CWM recovery with stock recovery, but you'll remain rooted. Probably doesn't address all your questions, but you've got a start.
Click to expand...
Click to collapse
forgot to mention that i am rooted now. using oneclickroot.
Just flash a custom kernel with CWM recovery installed inside.
Such as:
- Siyah
- Phoenix
- Ninphetamine
etc...
DO NOT FLASH STOCK KERNEL AS IT WILL DELETE CWM RECOVERY. ROM MANAGER DOES NOT INSTALL RECOVERY ON YOUR PHONE.
nicholaschum said:
Just flash a custom kernel with CWM recovery installed inside.
Such as:
- Siyah
- Phoenix
- Ninphetamine
etc...
DO NOT FLASH STOCK KERNEL AS IT WILL DELETE CWM RECOVERY. ROM MANAGER DOES NOT INSTALL RECOVERY ON YOUR PHONE.
Click to expand...
Click to collapse
is it as simple as using Odin, clicking PDA and flashing the downloaded kernel? and there should be no side effects from using a custom kernel such as Siyah?
Getting back to 100% stock is easy, odin flash a rom.
CF root *is* the stock kernel, just with some bits added (CWM recovery and root).
CF root with your stock rom is defo the safest bet.
jerseykat1 said:
is it as simple as using Odin, clicking PDA and flashing the downloaded kernel? and there should be no side effects from using a custom kernel such as Siyah?
Click to expand...
Click to collapse
Yes if you get the kernel in odin tar file, otherwise flash CF root and use CWM recovery to flash the zips.
Hello. I have galaxy S2, and I wanted to install CWM. I installed it (CWM-KitKatCompatible-i9100) with odin with auto reboot unchecked and after that it doesn't boot up. It can go to odin and CWM modes, but the android doesn't launch. I did a recovery to phone storage, but still I cant launch the phone... Can anyone help me?
Flash a compatible kernel to your installed rom via recovery. Or you can flash an insecure kernel via Odin.
Simple cwm flashing won't boot up your phone.
banjara said:
Flash a compatible kernel to your installed rom via recovery. Or you can flash an insecure kernel via Odin.
Simple cwm flashing won't boot up your phone.
Click to expand...
Click to collapse
Would you mind explaining how to flash a compatible kernel to my phone via recovery? Also I didn't install any rom just cwm. And where should I get a proper kernel to my android? Sorry for dumb questions, but I'm not experienced enough as you see...
V6xas said:
Would you mind explaining how to flash a compatible kernel to my phone via recovery? Also I didn't install any rom just cwm. And where should I get a proper kernel to my android? Sorry for dumb questions, but I'm not experienced enough as you see...
Click to expand...
Click to collapse
Well, there are 3 kernels which are quite popular here which have their depth range till kitkat roms.. A simple search on xda for them will lead you to the respective threads.
1. Gustavo's
2. Dorimanx
3. Apolo
If you want a KK rom then download a KK compatible kernel mentioned in the op for those threads, put that on external sdcard and boot to recovery. There you can flash the Kernel file. As you don't have a rom on your phone it would be better if you download a rom and gapps package too and flash them. After flashing a kernel, reboot to recovery and then flash rom and gapps.
If it's difficult for you to put those files on sdcard, you can flash a stock rom via Odin, flash a kernel e.g. philz, apolo,hirox via Odin. Search for these keywords here on xda. Once you have a working kernel and rom, you can download a custom rom and gapps, put it on your phone and follow the procedure which I mentioned first.
If my steps are still confusing to you then you require to search for these terminologies here on xda,read and understand them carefully and then proceed.
You didn't mention what OS/Firmware was on your phone before you started.....this is VERY important to know as it will decide what you can / cannot flash.....
Custom kernels are OS version dependent.....some will only work with ICS, others will only work with JB.....some are exclusively for KK.
You need to check this.....
My wife says I'm a phone geek....She's probably right
keithross39 said:
You didn't mention what OS/Firmware was on your phone before you started.....this is VERY important to know as it will decide what you can / cannot flash.....
Custom kernels are OS version dependent.....some will only work with ICS, others will only work with JB.....some are exclusively for KK.
You need to check this.....
My wife says I'm a phone geek....She's probably right
Click to expand...
Click to collapse
well I couldn't check cause it couldn't boot up, unless there's another way... But whatever I managed to write 4.4.2 Kitkat on my S2 and there's alot missing feature's like, I cant organise my program menu, I cant add many widgets that I had used in my previous android, there are no notes, phone file explorer and other what is irritating... Maybe there's some another pack that I missed when installing or what?
Right, I have a set of issues which all seem vaguely connected but I can't figure out how to resolve.
I've unlocked my bootloader and I've been messing about with recoveries and CM11 etc.
The situation however is that I installed doomkernel, got into CWM and installed CM11, all good.. went to go back into the recovery and it's gone, it just hangs if I try, no worries I thought I'll just reflash doomkernel, then the ROM doesn't boot so I have to reflash boot.img from the CM11 zip.
That kills the recovery again... rinse and repeat basically, it looks like I can't have CM11 and CWM which is a PITA.
Plenty of people in the CM11 thread seem to be having no issues with either retaining the recovery or using cyandelta, neither of which work for me and whilst CM11 is still in nightly I really need to be able to upgrade frequently.
Also, using flashtool to unlock the bootloader was fine but I can't flash a recovery from there as the option is greyed out on both CM11 and the stock ROM..
I'm lost, I've tried several combinations but I've also gone dangerously close to bricking the phone so I've backed off..
Can anyone give me any pointers?
The only thing I haven't done is download the ROM from the frexperia site as I can't make sense of which ROM I need, I can't see Z2 or Sirius mentioned anywhere and I've learned the painful way in the past not to flash the wrong ROM.
So now I'm back to the stock rooted ROM but there's a bunch of issues with it such as it loving switching the wifi on and off, proximity sensors thinking my face is my fingers, the useless lock screen etc etc.
HALP! Thanks all
Try this:
1 - install recovery.
2 - reboot into recovery.
3 - flash CM11, don't reboot.
4 - flash gapps, don't reboot.
5 - flash recovery & reboot.
Does this leave you with a recovery? There is an option to upgrade recovery in CM11 settings -> developer options -> update CM recovery. Try this and see what happens.
Sent from my SGP311 using XDA Free mobile app
I haven't been flashing the recovery from within CWM, in fact I'm not even sure you can with it being a kernel image as thats how Sony's work? If I flash the doomkernel again I know CM11 won't boot and sort of vice versa..
EDIT - Sorry I didn't see you had a Z2.. have you managed to pull this off? Any tips on a recovery flashable kernel?
mrmatt100 said:
I haven't been flashing the recovery from within CWM, in fact I'm not even sure you can with it being a kernel image as thats how Sony's work? If I flash the doomkernel again I know CM11 won't boot and sort of vice versa..
EDIT - Sorry I didn't see you had a Z2.. have you managed to pull this off? Any tips on a recovery flashable kernel?
Click to expand...
Click to collapse
Reintall stock. Skip Doom Kernel, directly fastboot CM boot.img. Flash CM in your now working recovery.
Thats what worked for me
Sent from my Xperia Z2 using Tapatalk
Sorry what do you mean by skin the kernel? I'm not a n00b but I've never heard that before?
but thanks for the help!
Myself5 said:
Reintall stock. Skin Doom Kernel, directly fastboot CM boot.img. Flash CM in your now working recovery.
Thats what worked for me
Sent from my Xperia Z2 using Tapatalk
Click to expand...
Click to collapse
Still stuck on this, I do know I've got stock with doom kernel and I've fastboot flashed the CM boot.img from the CM11 nightly, that basically results in a phone that won't boot OR go into recovery.
Literally the only way I can get into CWM is by using doom kernel and the stock ROM (obviously rooted and using xposed etc if that makes a difference) and the moment I flash anything from within CWM it obviously overwrites the boot.img meaning I can boot normally but not with a working recovery.
I can't escape the feeling that I ought to be flashing a specific version perhaps from freexperia rather than the cyanogenmod website or I need a different kernel to kick the process off rather than doom kernel.
Very confusing and a real shame doom kernel only works with stock ROMs
Sorry the skin part was a spelling misstake. Should have been SKIP. I issued the same as you, my problem was somehow related to DoomKernel. So just Flash Stock now (using a ftf in flashtool) and then straight the boot.img from the CM zip. Now boot in the recovery (press vol down when the Amber led lights up at the boot process) and flash the CM zip in this recovery (wipe data/Factory reset and format /system before ofc (least that what I would recommend)). Flash Gapps if you whish. Reboot to your now working CM install.
Sent from my Xperia Z2 using Tapatalk
Myself5 said:
Sorry the skin part was a spelling misstake. Should have been SKIP. I issued the same as you, my problem was somehow related to DoomKernel. So just Flash Stock now (using a ftf in flashtool) and then straight the boot.img from the CM zip. Now boot in the recovery (press vol down when the Amber led lights up at the boot process) and flash the CM zip in this recovery (wipe data/Factory reset and format /system before ofc (least that what I would recommend)). Flash Gapps if you whish. Reboot to your now working CM install.
Sent from my Xperia Z2 using Tapatalk
Click to expand...
Click to collapse
Absolutely 100% spot on, I'm so happy! Thanks
mrmatt100 said:
Absolutely 100% spot on, I'm so happy! Thanks
Click to expand...
Click to collapse
hello i'm having this exact same issue and i will be trying this taday when home from work. the only thing i'm not sure about is the ftf in flashtool.
don't know what ftf stands for, but i presume flashtool is the official sony flash tool?
http://developer.sonymobile.com/services/flash-tool/
thanks for the answer.
skuko said:
hello i'm having this exact same issue and i will be trying this taday when home from work. the only thing i'm not sure about is the ftf in flashtool.
don't know what ftf stands for, but i presume flashtool is the official sony flash tool?
http://developer.sonymobile.com/services/flash-tool/
thanks for the answer.
Click to expand...
Click to collapse
I think there's the official and an unofficial tool, I used the one from here http://www.flashtool.net/index.php
And a .ftf file is an official sony ROM, bit like how you end up with .zip files for non official ROMs, HTCs have .RUUs and iPhones have .ISPW files.
There's a list of .ftf files on here somewhere, grab the latest from there.
For what it's worth, I went CM11, got fed up with the camera quality so went to xistenz and romaur, both slightly unstable so I went back and back again to a stock .ftf, rooted it and I'm just using a bunch of xposed tweaks now and it looks pretty much the same as AOSP now. You only see the difference when you're in settings.
skuko said:
hello i'm having this exact same issue and i will be trying this taday when home from work. the only thing i'm not sure about is the ftf in flashtool.
don't know what ftf stands for, but i presume flashtool is the official sony flash tool?
http://developer.sonymobile.com/services/flash-tool/
thanks for the answer.
Click to expand...
Click to collapse
I meanwhile found a even easier way to solve this problem. Just go into faatboot mode (turn off phone press Vol+ and attach USB) and do "fastboot erase recovery" this will boot the kernels default recovery (CWM) again. This all is caused by some missing tools in the kernel which is not loading TWRP. However even with the tool provided by @Dees_Troy it does not load TWRP, now instead of hanging at the black screen with no recovery it still loads CWM after flashing TWRP to the recovery partition.
Sent from my Xperia Z2 using Tapatalk
Myself5 said:
I meanwhile found a even easier way to solve this problem. Just go into faatboot mode (turn off phone press Vol+ and attach USB) and do "fastboot erase recovery" this will boot the kernels default recovery (CWM) again. This all is caused by some missing tools in the kernel which is not loading TWRP. However even with the tool provided by @Dees_Troy it does not load TWRP, now instead of hanging at the black screen with no recovery it still loads CWM after flashing TWRP to the recovery partition.
Sent from my Xperia Z2 using Tapatalk
Click to expand...
Click to collapse
so if i want to get rid of the doomkernel, i still need to reflash the stock ftf, correct?
skuko said:
so if i want to get rid of the doomkernel, i still need to reflash the stock ftf, correct?
Click to expand...
Click to collapse
In case you want back to stock, yes. In case you want from Doom to CM just erase the recovery partition and fastboot flash the CM boot.img
Sent from my Xperia Z2 using Tapatalk
seems to have worked, my kernel in "about phone" now says:
3.4.0cyanogenmod-g449fd42
[email protected] #1
Mon Aug 18 09:30:35 BST 2014
i used the boot.img from your carbon rom nightly.
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.