Related
Hey everyone,
First of all, i apologize if any of what i'm asking here is stuff that has been covered before. I have been searching myself for answers for the last several days and have found plenty of good info, but i am new to android and i think i need to ask some question to help get a base level understanding of what i need to do. I am a bit nervous about bricking my phone so i maybe haven't been as adventurous trying to get everything running as god intended.
Firstly, i have used and understand Odin, using it to flash roms and such. I have rooted the phone and installed ROM Manager and clockworkmod 4.0.1.5 on the phone, but when i boot into recovery mode, it is still on the android recovery 3e and i cannot do the update.zip, I get signature verification failed. Now i KNOW this is cause of the android recovery 3e, and i have found this issue has been encountered plenty before, but my confusion is in some of the solutions i have found. Mainly the terminology and how the steps directly apply to the phone. For example, I found on another forum thread :
1- Copy the Zimage from your rooted kernel and paste it to SD card of your phone.
2- Flash the Stock kernel via Odin to get rid of Yellow triangle.
3- Flash the Zip file (Zimage) via CWM which you've already pasted in Step 1.
i don't really understand what the zimage is. Why do i need it, what IS it frankly? Where do i get it or a stock kernel for my phone. Does versioning matter much? i read that for the most part the kernels are almost identical to each other, and the fact all i really need is for the android recovery mode to be 2e or whatever it is (so it will not do the signature check on the update.zip file), that i don't really need to pay much attention to the actual kernel version.
What i really need i guess is for someone to break it down for me and either explain the steps or give me a detailed step by step on how to get clockworkmod recovery working so i can proceed with the cyanogen mod running on phone (not enjoying touchwiz at all).
Again, sorry if i am giving anyone spasms at my noobish-ness, but i have been searching for my answers for a day or two now and i haven't been able to find anything that really tells me what i need to know.
Phone : GT-I9100M
Android : 2.3.3
Kernal : 2.6.35.7-I9100XWKDD-CL
Build : GINGERBREAD.UGKG2
Thanks
riccochet said:
Hey everyone,
clockworkmod 4.0.1.5 on the phone, but when i boot into recovery mode, it is still on the android recovery 3e
That means you have not installed it flash CWM and \Root from here .
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
Beware of following instructions from a separate rom to the one you are flashing .
1- Copy the Zimage from your rooted kernel and paste it to SD card of your phone.
2- Flash the Stock kernel via Odin to get rid of Yellow triangle.
3- Flash the Zip file (Zimage) via CWM which you've already pasted in Step 1.
i don't really understand what the zimage is.
ZImage is the kernel .
Why do i need it, what IS it frankly? Where do i get it or a stock kernel for my phone. Does versioning matter much? i read that for the most part the kernels are almost identical to each other, and the fact all i really need is for the android recovery mode to be 2e or whatever it is (so it will not do the signature check on the update.zip file), that i don't really need to pay much attention to the actual kernel version.
You are confusing yourself .
Flash correct CWM from above link .
Choose the custom rom and follow the instructions posted for that rom .
CyanogenMod as the man says
Warning : Not for new users, flash this build only if you know what you are doing !!!
#Followed by his install instructions ~~~
jje
Click to expand...
Click to collapse
Thanks for the reply. I have been doing more reading and i think i am understanding the rooting process a bit better.
I looked at the link you posted (thanks for that, i saw the forum post for the i9000 but i never could find the i9100 post for some reason) and i DO have another question after reading through a good chunk of the posts on it.
There is no CF Root for my kernel, but the reply that was made to someone else with my kernel version was :
"Flash the Stock 2.3.4 ROM (XXKG5, XXKG6 or XXKG7) and root with CF-Root-XXKG6."
I understand that process and how it works but i thought you were only supposed to flash roms based on your firmware version? My KDD kernel version is running on 2.3.3
Will this cause any issues if i flash the stock 2.3.4 ROM?
Download cm7 zip for the newest nightly.
Copy it to internal sd card.
Flash any cf root kernel
Boot into recovery
Wipe data and cache, you will lose all your data on your phone, so backup sms (I recommend sms backup +), also you will lose App data so you might want to back that up first using something like titanium backup.
Wipe dalvik cache (under advanced)
Chose install zip from sd card
Select the cm7 zip
Reboot
If you get stuck at the boot screen go back into recovery and flash the zip again
Sent from my GT-I9100 using XDA Premium App
Thanks Veyka.
I think i'm ok with the CM7 install process. I am probably going to wait until i really feel like i understand the whole process from front to back before i start messing with that though.
I can't get to that point yet however since i haven't been able to get CWM recovery working yet. I have the Android Recovery 3e, which will not install from zip files that aren't digitally signed.
So i'm trying to get CF Root installed and working, however, as mentioned in my previous post there is no CF Root for my kernel. I would like it clarified if it is ok for me to flash to a 2.3.4 stock ROM (i'm running 2.3.3) and then use a CF root for a the new ROM.
I was under the impression that this was not a good idea.
If i should not be doing this, is there a recommended way to upgrade my firmware to 2.3.4 so i can use a newer CF Root?
Thanks
Pick a new stock rom, I would go for kg6, flash it via odin.
Then flash the kg6 CF root kernel via odin and you will have cwm recovery.
Don't put the pit into odin and don't tick repartition or update bootloader.
There is a good thread with all the info you need on flashing stock roms with odin and a list of all avaliable roms.
Sent from my GT-I9100 using XDA Premium App
Thanks for all the help. I was able to make sense of the process (which is actually quite simple, just needed to put it all together in my head to make sense) and get everything done.
Appreciate all the help!
veyka said:
Download cm7 zip for the newest nightly.
Copy it to internal sd card.
Flash any cf root kernel
Boot into recovery
Wipe data and cache, you will lose all your data on your phone, so backup sms (I recommend sms backup +), also you will lose App data so you might want to back that up first using something like titanium backup.
Wipe dalvik cache (under advanced)
Chose install zip from sd card
Select the cm7 zip
Reboot
If you get stuck at the boot screen go back into recovery and flash the zip again
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
Hi,
I have rooted my phone using the quick root guide found here and therefore I have my stock kernel back w/ root. Do I need to install a cf root kernel?
Also, when the new ROM gets flashed how does one recover the apps and data lost?
NABNAP said:
Hi,
I have rooted my phone using the quick root guide found here and therefore I have my stock kernel back w/ root. Do I need to install a cf root kernel?
Also, when the new ROM gets flashed how does one recover the apps and data lost?
Click to expand...
Click to collapse
Use Titanium Backup PRO for your app. You can backup all of them then restore on any rom.
Is there anything that Titanium Backup doesn't back up for which I need to use another application?
Thanks.
NABNAP said:
Is there anything that Titanium Backup doesn't back up for which I need to use another application?
Thanks.
Click to expand...
Click to collapse
sms.. use another app to backup your sms.. for example sms backup as mentioned before..
I've tried to install CM9 in my LWW but ended up in a boot loop
tried wiping everything but it's not helping.
I've also tried to install Ex MiUI4 also same result. got the boot logo but
restarting over n over again.
What am i missing here
I have rooted , BL unlocked 4.0.4 stock rom.
Please guide me to install CM9 in a proper way.
Need some help here guys.
Did you flash the proper kernel?
Hi!
First of all, sorry for hijacking the thread but I'm in a similar situation, so there maybe no need to create a new topic.
Well, I also want to try CM9, but I've got some doubts yet.
My LWW is not rooted nor with bootloader unlocked, and I'm running official ICS 4.0.4.
I've been reading the tutorials/FAQ topic in this section and making some research (many thanks to all the community!:good but just to be on the safe side I need to clarify this.
I really need to root my phone in order to run CWM, which, subsequently is required to flash new kernel and ROM, right?
In case I want to go back to full stock, will I be able to backup stock kernel and ROM, then restore them, then re-lock bootloader, and finally, able to install OTA updates?
Thanks in advance!
You don't have to root and/or install CWM in order to install a custom ROM, that requires custom kernel.
These custom kernels already include root and recovery, so you don't need to install them manually, else you're just wasting your time.
And yes, make sure to install that custom kernel aswell.
Great! Thanks for your answer!:good:
I pretend to install FXP CM9.
Just one more thing... in case I need/want to revert to full stock (kernel+ROM) is it enough to re-lock bootloader and then "repair" in PC Companion? Or will this just mess things up and in that case I would need to install CWM to backup stocks (before flashing new kernel+ROM of course)?
Thanks again!
First flash stock ROM using flashtool. Then, relock bootloader. You can't repair with PC Companion while you're on CM9
Got it!
Thanks a lot for your help!:good:
Feanor88 said:
Did you flash the proper kernel?
Click to expand...
Click to collapse
I have flash the boot.img file inside of the CM9 zip file.
I guess that is the correct kernel ?
these are the steps i have followed.
1.) Boot in to recovery
2.) Wiped all user data, cache, dalvik cache, battery stats.
3.) Installed the cm-9.0.0-RC1-coconut.zip file (it had boot.img file also. should i need to remove it ?)
taken from : http://download.cyanogenmod.com/get/jenkins/3487/cm-9.0.0-RC1-coconut.zip
(haven't flashed the baseband zip yet)
4.) Reboot the phone into fastboot mode.
5.) flashed the kernel (taken from above zip file )
6.) Reboot the phone.
Ended up in Boot loop every time.
You need to flash the kernel. Use Flashtool. Enter fastboot (make sure you have proper drivers installed) and flash the boot.img. Then you'll be able to boot properly
what is the correct kernel would be ?
Sorry, I might have mistaken you. Did you already flash the boot.img via fastboot mode?
Ok, now I remember. I think the provided kernel does not work, it's bugged. You should use another one. I'll search the forum, there are other threads about this. Do the same, you'll find an answer in the first 2 or 3 pages of this forum
Here it is
http://forum.xda-developers.com/showpost.php?p=28354324&postcount=7
Yes CM9 kernel is not working, it s bugged.
You should try "FXP 127" or "FXP 128" kernel.
Try FXP 128 because it is the latest one and with less bugs....
You can download it from here....
FXP 128 - CM9
Feanor88 said:
Sorry, I might have mistaken you. Did you already flash the boot.img via fastboot mode?
Ok, now I remember. I think the provided kernel does not work, it's bugged. You should use another one. I'll search the forum, there are other threads about this. Do the same, you'll find an answer in the first 2 or 3 pages of this forum
Here it is
http://forum.xda-developers.com/showpost.php?p=28354324&postcount=7
Click to expand...
Click to collapse
deamonoid said:
Yes CM9 kernel is not working, it s bugged.
You should try "FXP 127" or "FXP 128" kernel.
Try FXP 128 because it is the latest one and with less bugs....
You can download it from here....
FXP 128 - CM9
Click to expand...
Click to collapse
Hey thanks a lot guys. finally it worked.
This community is awesome i would say :good:
Have you try this site?
"androidust"
deamonoid said:
Yes CM9 kernel is not working, it s bugged.
You should try "FXP 127" or "FXP 128" kernel.
Try FXP 128 because it is the latest one and with less bugs....
You can download it from here....
FXP 128 - CM9
Click to expand...
Click to collapse
So.. If i want to flash FXP CM9 ROM, i should use FXP128 kernel? How about latest 142 kernel? It's also bugged?
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
I'll do a quick a run down of what my phone has been through, so you have the info you need before asking.
1. Bought used i9305 with defect charger port
2. Soldered on a new port
3. Flashed CWM
4. Flashed ROM's for a while.
5. Reflashed to stock.
6. Tried to flash CWM again but soft-bricked my phone.
7. Reflashed to stock.
8. Flashed CWM and now i keep getting different errors when trying to flash Custom ROM's.
I first off started to have this problem: Status 7.
I did the updater-script fix, to no avail.
Then i got Status 4 error, and can't find anything about it on the webs.
So it won't let me flash any CR's.
I tried:
Updater-Script fix (Gave me Status 4 right after)
Different ROM's (CM , AOKP)
Different Recoveries (CWM Touch , CWM Non Touch , CM Recovery , TWRP (Didn't flash correctly so it didn't show)
Different Kernels (Stock and AGNi)
Also when i flashed recoveries on a stock kernel, and i booted into OS then it overwrites the recovery, so i had to pull out the battery and boot directly into the recovery and when i rebooted the custom recovery was gone. until i installed AGNi.
UPDATE:
I have a thing i will try later today, which is flashing another firmware file.
If this works, then i'll post it.
Drew McIntyre said:
UPDATE:
I have a thing i will try later today, which is flashing another firmware file.
If this works, then i'll post it.
Click to expand...
Click to collapse
Did you try using mtk tools if it is possible?
Mokin said:
Did you try using mtk tools if it is possible?
Click to expand...
Click to collapse
I'll try that now.
Mokin said:
Did you try using mtk tools if it is possible?
Click to expand...
Click to collapse
Sorry, but what should this tool help with?
Never used that tool, and can't find a tutorial on howto.
Drew McIntyre said:
Sorry, but what should this tool help with?
Never used that tool, and can't find a tutorial on howto.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=52vWfCLZrrU
This is a tutorial which helped me, and this is how to flash roms
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Mokin said:
https://www.youtube.com/watch?v=52vWfCLZrrU
This is a tutorial which helped me, and this is how to flash roms
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Click to expand...
Click to collapse
My device is rooted (AGNi kernel roots it)
And i know how to flash CR's, i have done it since 2012, but this error is very new to me.
UPDATE:
After flashing a old firmware (3.1.2 Jelly bean) it seems it has fixed this, but i'm still encountering problems.
The new problem is that somehow i don't have a recovery anymore, i fixed this by flashing a custom recovery.
I could install the zip file, but even after /system wipe and factory reset the phone would not boot.
I proceeded to unbrick the hardbrick with my RIFF.
i also checked that it was for my i9305, which is was.
UPDATE:
After i removed CF-AutoRoot files from my NAND it worked outta nowhere.
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.