Related
I was gonna install a new ROM on my HTC Hero, and I forgot to flash the recovery image, after i installed the ROM, all my old stuff were there with the new stuff, and when I tried to use Recovery Flash To Back Up and flash a recovery image but it said BACK UP Failed could not run command.! Please Help Me!!!
Moved to Q&A as not development
So what happens when you power on with HOME + POWER?
ddotpatel said:
So what happens when you power on with HOME + POWER?
Click to expand...
Click to collapse
it goes to the Android System Recovery!
kevin5fan said:
I was gonna install a new ROM on my HTC Hero, and I forgot to flash the recovery image, after i installed the ROM, all my old stuff were there with the new stuff, and when I tried to use Recovery Flash To Back Up and flash a recovery image but it said BACK UP Failed could not run command.! Please Help Me!!!
Click to expand...
Click to collapse
OK. So first of all, calm down. Second of all, can you explain clearly what you did (step by step), and what isn't working, and what you are trying to do.
I can't make head nor tail of your story, but it sounds like you installed a new ROM and didn't wipe the data, and now can't do something to do with recovery.
Have you read up on flashing etc before doing this?
pulser_g2 said:
OK. So first of all, calm down. Second of all, can you explain clearly what you did (step by step), and what isn't working, and what you are trying to do.
I can't make head nor tail of your story, but it sounds like you installed a new ROM and didn't wipe the data, and now can't do something to do with recovery.
Have you read up on flashing etc before doing this?
Click to expand...
Click to collapse
OK I Was Gonna Install A New Mod On My Old VillianROM (HTC Hero)
Second I forgot to flash the recovery image b4 installing the ROM
I installed the ROM and then all my programs on my old ROM were there with the new ones.(is that normal?)
I tried to reinstall the ROM by flashing the Recovery Image This Time but Recovery Flash had an error. Cannot Back Up!
So IDK if what i did is right or Worng Please Help!
kevin5fan said:
OK I Was Gonna Install A New Mod On My Old VillianROM (HTC Hero)
Second I forgot to flash the recovery image b4 installing the ROM
I installed the ROM and then all my programs on my old ROM were there with the new ones.(is that normal?)
I tried to reinstall the ROM by flashing the Recovery Image This Time but Recovery Flash had an error. Cannot Back Up!
So IDK if what i did is right or Worng Please Help!
Click to expand...
Click to collapse
Your apps will remain unless you did a wipe.
And there is no need to flash recovery each time. This is fixable though. If you are able to flash VR12, it will install a recovery image for you automatically.
Do you have adb set up, as if so, this is pretty easy to do?
What writting comes up?
Edit... I'll leave you in Pulsers capable hands
Sent from my HTC Hero using XDA App
pulser_g2 said:
Your apps will remain unless you did a wipe.
And there is no need to flash recovery each time. This is fixable though. If you are able to flash VR12, it will install a recovery image for you automatically.
Do you have adb set up, as if so, this is pretty easy to do?
Click to expand...
Click to collapse
I did a factory wipe and IDK what a ADP set up is? I want to install another ROM called Madaco Custom Rom or w.e yea so can u add me on msn pm me your address
kevin5fan said:
I did a factory wipe and IDK what a ADP set up is? I want to install another ROM called Madaco Custom Rom or w.e yea so can u add me on msn pm me your address
Click to expand...
Click to collapse
Don't use MSN, I'm afraid, but if you go to www.villainrom.co.uk and go to "Follow us" and then click IRC, you can come to the instant chat and explain what's happened there, and you'll get it sorted It's like a group MSN
So I was walking my girlfriend through rooting her new Evo3D, and we couldn't get the phone to get past the 'MI' logo, so I figured it was a kernel thing. After four kernels and two versions of MIUI I realized that it wasn't the issue, it was the hboot.
She didn't back up, she has only had it since last night. I now know what I need to do to flash the ROM, but how can I get her back to stock so I can get the app needed?
Any help?
She has HBOOT 1.5, right?
Go back to the folder where you did all the rooting. Get the stock MIUI kernel (boot.img from the flashable zip) and place it in that folder. Open up a cmd and navigate to that folder.
Boot her phone into fastboot mode. (Vol down + power while the phone is off. Hit power button to select fastboot once it goes into bootloader) Plug the phone into the computer via USB
Type 'fastboot flash boot boot.img' in the kernel. If it successfully flashes, you are done! MIUI should boot up now that it has the appropriate kernel. You will need to do this for any ROM you flash.
As long as you have a recovery, just flash whatever rom you want through fastboot and the kernel will stick.
Or just download a stock rooted rom and flash that the same way you just tried to flash MIUI. It will work since you still have the original kernel.
Sent from my PG86100 using XDA App
flonker said:
As long as you have a recovery, just flash whatever rom you want through fastboot and the kernel will stick.
Or just download a stock rooted rom and flash that the same way you just tried to flash MIUI. It will work since you still have the original kernel.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Well, ROM's cant be flashed through fastboot. The ROM is flashed through recovery. Then you go to fastboot and flash the kernel with my guide above. After that, everything should be working fine.
yousefak said:
She has HBOOT 1.5, right?
Go back to the folder where you did all the rooting. Get the stock MIUI kernel (boot.img from the flashable zip) and place it in that folder. Open up a cmd and navigate to that folder.
Boot her phone into fastboot mode. (Vol down + power while the phone is off. Hit power button to select fastboot once it goes into bootloader) Plug the phone into the computer via USB
Type 'fastboot flash boot boot.img' in the kernel. If it successfully flashes, you are done! MIUI should boot up now that it has the appropriate kernel. You will need to do this for any ROM you flash.
Click to expand...
Click to collapse
Hopefully this works! Shes at church right now but I will have her do this ASAP and I'll report back!
(Awesome response time BTW)
Roms are flashed through fastboot just by loading your recovery into fastboot.
I never flash roms and kernels separately. Just go into fastboot, load your recovery, and flash as you normally would.
Sent from my PG86100 using XDA App
I had something similar when flashing MIUI. if you boot the recovery.img from fastboot it should work. you may want to re download just in case of a bad download.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
I'm having the same problem as epicchase. have attempted to flash miui many times. at first i tried to do it through my recovery. it didn't work. then i tried to use the fast boot method and flash it from the recovery that i opened from fast boot. i'm quite frustrated. it just wont boot miui, is it the kernel, i'm new to rooting in general but i think i know what i'm doing. i have spent who knows how many hours trying everything i can. i tried flashing the boot.img and the ROM separately. I have successively flashed android revolution hd, but that's no fun, its nearly the same as the stock ROM any suggestions would be appreciated. it boots but i guess it must be a boot loop but idk all i know is it freezes in the middle of the boot animation.
ps. i am rooted using the htc official method (unfortunately) and am s-on)
redstrike120 said:
I'm having the same problem as epicchase. have attempted to flash miui many times. at first i tried to do it through my recovery. it didn't work. then i tried to use the fast boot method and flash it from the recovery that i opened from fast boot. i'm quite frustrated. it just wont boot miui, is it the kernel, i'm new to rooting in general but i think i know what i'm doing. i have spent who knows how many hours trying everything i can. i tried flashing the boot.img and the ROM separately. I have successively flashed android revolution hd, but that's no fun, its nearly the same as the stock ROM any suggestions would be appreciated. it boots but i guess it must be a boot loop but idk all i know is it freezes in the middle of the boot animation.
ps. i am rooted using the htc official method (unfortunately) and am s-on)
Click to expand...
Click to collapse
Did you do a full wipe before you flashed? Find Virus's Superwipe tool (.zip), boot to recovery with fastboot, flash the superwipe.zip, then flash MIUI.
Twolazyg said:
Did you do a full wipe before you flashed? Find Virus's Superwipe tool (.zip), boot to recovery with fastboot, flash the superwipe.zip, then flash MIUI.
Click to expand...
Click to collapse
I will try that tonight thanks very much in advance
Sent from my PG86100 using XDA App
Twolazyg said:
Did you do a full wipe before you flashed? Find Virus's Superwipe tool (.zip), boot to recovery with fastboot, flash the superwipe.zip, then flash MIUI.
Click to expand...
Click to collapse
well it didn't work it did the same exact thing. I've been giving it about 10 mins to attempt to boot is that long enough? I'm new to non sense roms I've only ever used sense, is there something I'm forgetting to do that is different for non sense roms. *frustration* (and i thought i was beginning to understand this)
---------- Post added at 09:43 PM ---------- Previous post was at 08:46 PM ----------
okay well i tried to flash cyanogenmod 7 still no dice. I must be an idiot, sorry for being a noob.
this is what im doing.
im placing the .zip on root of my sd card. then opening my cmd.
i then type " cd c:\android" (i saved the recovery image in a folder named android) it says
"c:\android" just as it should i then type "fastboot boot recovery.img"
it restarts my phone in recovery
i press install .zip from sd card then click wipe cache and dalvik cache it goes and does its work
i then select the superwipe.zip it says flash compete however it says error or something but i just kind of ignored it.
i then select my miui.zip that i got from www.miui.us
i then select install .zip files the first thing that comes up is "md5 check fail- ignoring" and the continues and flashes (i have no clue what that part means but i continue anyway)
i select reboot and it starts to boot my phone i get the white screen with green htc.
i then get the miui boot animation for anywhere from 2-5 seconds and then it freezes.
i sit and nearly just stare at it and the clock. i wait at least 5 mins but have waited up to 30 mins.
the boot animation never restarts i just freezes there making me think it is not a boot loop (however the definition of an actual bootloop is slightly vague to me.)
anyway thanks for reading and if you have any suggestions i will be very happy for now im just gonna run my android revolution hd rom.
If superwipe isn't working, fastboot to recovery, go to the wipe menu, not install a zip, wipe dalvik, cache, and factory reset. Don't do the factory reset in android, do it in recovery. I'm guessing you got a corrupt download of superwipe, I would redownload it and try it again if I were you.
Try using this one.
Twolazyg said:
If superwipe isn't working, fastboot to recovery, go to the wipe menu, not install a zip, wipe dalvik, cache, and factory reset. Don't do the factory reset in android, do it in recovery. I'm guessing you got a corrupt download of superwipe, I would redownload it and try it again if I were you.
Try using this one.
Click to expand...
Click to collapse
Yayyyy perfect thankyou sooooo much I'm speechless thank you so much!!! it flashed like it was mardi gras.
Sent from my HTC EVO 3D using XDA App
this process doesnt work for me, i have been trying it for 2 mnoths..No avail, is there anyone who can make this work?
EVO 3D HBOOT 1.5
rcquartz said:
this process doesnt work for me, i have been trying it for 2 mnoths..No avail, is there anyone who can make this work?
EVO 3D HBOOT 1.5
Click to expand...
Click to collapse
What didn't work for you?
rcquartz said:
this process doesnt work for me, i have been trying it for 2 mnoths..No avail, is there anyone who can make this work?
EVO 3D HBOOT 1.5
Click to expand...
Click to collapse
make sure your phone is actually rooted if it is hboot 1.5 make sure to use htvdev.com
make sure you have a recovery image
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.