Hai.
I have a galaxy note 3 sm n9005. Have already rooted by finding forum from xda and even install twrp recovery following the guides given.
But im trying to install custom rom. And tried all the roms tat is given from xda for note 3 and could install single one.
Please help to resolve this problem. Im confuse.
Tq.
Not enough details.
It's probably the version of recovery you're using.
Which version of TWRP and what errors are you receiving?
es0tericcha0s said:
Not enough details.
It's probably the version of recovery you're using.
Which version of TWRP and what errors are you receiving?
Click to expand...
Click to collapse
Im using twrp 3.0.2.1 and everytime i try to install a rom it stuck at samsung screen.
And it show md5 not found.
What roms have you tried? What firmware were you on before you started flashing? Sometimes newer roms need the newest firmware like the bootloader and modem to run correctly. Are you wiping system, data, and both caches? If you are going from a Touchwiz rom to, say, a CM based, it might also be necessary to wipe the internal storage. Of course you should back all that up to a PC first, if you do that.
es0tericcha0s said:
What roms have you tried? What firmware were you on before you started flashing? Sometimes newer roms need the newest firmware like the bootloader and modem to run correctly. Are you wiping system, data, and both caches? If you are going from a Touchwiz rom to, say, a CM based, it might also be necessary to wipe the internal storage. Of course you should back all that up to a PC first, if you do that.
Click to expand...
Click to collapse
Resurrection remix.unicorn.slim.and all cynogen rom is working. Im trying install s7edge custom rom for darkwolf and darklord. I even updated the bootloader and modem according to tutorial. I used odin to flash them..
N9005xxugboa1
Lrx21v.n9005xxugbob6
I have my stock rom n internl backed up. I try all. And still it always stuck on samsung screen.
Are you installing the kernel after the rom flash? A lot of newer Samsung roms don't have the kernel built in like CM roms.
es0tericcha0s said:
Are you installing the kernel after the rom flash? A lot of newer Samsung roms don't have the kernel built in like CM roms.
Click to expand...
Click to collapse
How can install kernel after. Everytime i install it reboots its self to samsung screen. Or should go back to recovery and install the kernel back. And thank you for your help till now.
That's definitely why it's not booting, if you didn't do the kernel. If the rom has the Aroma installer, typically the last question asks if you want to reboot now and has a check mark in by default. Just uncheck and it'll go back to recovery. But you can also just go back and flash now and should be good.
es0tericcha0s said:
That's definitely why it's not booting, if you didn't do the kernel. If the rom has the Aroma installer, typically the last question asks if you want to reboot now and has a check mark in by default. Just uncheck and it'll go back to recovery. But you can also just go back and flash now and should be good.
Click to expand...
Click to collapse
I have uncheck the reboot after install. When i install the rom it automatically reboot itself. It doesnt show anything or show done. Once it even show os not found.
Hi
Where can i install or find the latest kernel
It's in the installation instructions for the rom.
es0tericcha0s said:
It's in the installation instructions for the rom.
Click to expand...
Click to collapse
Hi.
I have found the bootloader and modem for my sm n9005 from the installation instruction for the rom.
I try to flash according to the tutorial.and my baseband didnt change. I try flash using odin 3times.
Im not sure where i did wrong.can u help me
Tq
Remove the battery for 10 seconds. Put it back in and reboot to download mode. Uncheck auto reboot. Flash then check auto reboot and flash again. Should stick.
tq
es0tericcha0s said:
Remove the battery for 10 seconds. Put it back in and reboot to download mode. Uncheck auto reboot. Flash then check auto reboot and flash again. Should stick.
Click to expand...
Click to collapse
Tq
Will try and let you know
sitijohn85 said:
Tq
Will try and let you know
Click to expand...
Click to collapse
Hi
I tried as said and it didnt chnge.
Can i ask bootloader should be at bl and modem should be at cp. Is it correct.
Hi
Thank you for your help.
I did the change on bootloader and modem.
Now im i need to know two more thing.
I download 2 dffernt kind of bootloader n modem.
I flash blxxxxxbpb1 and cpxxxxxboj1..this 2 files were tar.md5 files
Another one which i didnt flash. Blxxxxxxbpb1 and cpxxxxxxxbpb2..this 2 files are tar.tar files..
Can i know whats the different with this 2 files.
One more thing is when i chnge the bootloader and modem will the kernel changes. Or is it different.
Please guide me..im confuse.
Someone might have just mislabeled them. Flashing those will not affect kernel. Different partition of the phone.
Hi
I did change the bootloader n modem.
And even change the kernel as told in the forum. It was note5 port kernel.7.1.0..
After trying to install the darkwolf rom.it was still the same..it did not work.
Please help me
sitijohn85 said:
Hi
I did change the bootloader n modem.
And even change the kernel as told in the forum. It was note5 port kernel.7.1.0..
After trying to install the darkwolf rom.it was still the same..it did not work.
Please help me
Click to expand...
Click to collapse
This is the recommended kernel
https://www.androidfilehost.com/?fid=24572369242687310
Recommended recovery is TWRP 2.8.7.0 not the newer 3.0+
Flash other recovery. Boot to TWRP. Wipe system, data, cache, dalvik. Flash rom. Wipe caches. Flash kernel. Reboot. Should work according to lots of people on the thread for that rom.
Hi.
How flash kernel.
just flash the tar.md5 file or the tar.zip file
Related
Hi
Can a rooted phone be rerooted as in without unrooting? (i'll explain)
I rooted my boyfriend's phone over a year ago and therefore cannot remember what method I used. Per his request, I wanted to install a new rom however, I am getting a signature verification error. While looking for answers, most posts recommend disabling the signature BUT I do not have that option when i go into recovery. My only thought in fixing this is to place a root over the root lol
Any advice?
texaslittleangel said:
Hi
Can a rooted phone be rerooted as in without unrooting? (i'll explain)
I rooted my boyfriend's phone over a year ago and therefore cannot remember what method I used. Per his request, I wanted to install a new rom however, I am getting a signature verification error. While looking for answers, most posts recommend disabling the signature BUT I do not have that option when i go into recovery. My only thought in fixing this is to place a root over the root lol
Any advice?
Click to expand...
Click to collapse
Sounds like you dont have a custom kernel and instead are trying to flash a rom via stock kernel.
Just reboot into download mode and flash Siyah kernel in ODIN. Once its installed you can reboot into custom recovery and flash new rom. I would advise to wipe data/factory reset in custom kernel before or after installing new rom.
TheATHEiST said:
Sounds like you dont have a custom kernel and instead are trying to flash a rom via stock kernel.
Just reboot into download mode and flash Siyah kernel in ODIN. Once its installed you can reboot into custom recovery and flash new rom. I would advise to wipe data/factory reset in custom kernel before or after installing new rom.
Click to expand...
Click to collapse
Can you please point me in the right direction on how to do this? It is the first time I run into a problem such as this one in 4 phones i've had
Which one from this list?
Is booting into custom the same as the normal Recovery boot?
texaslittleangel said:
Can you please point me in the right direction on how to do this? It is the first time I run into a problem such as this one in 4 phones i've had
Which one from this list?
Is booting into custom the same as the normal Recovery boot?
Click to expand...
Click to collapse
It depends on which firmware is now installed on his phone, which version of Siyah can be installed.
No, CWM Recovery isn't the same as stock Recovery. To flash a new rom you should have CWM Recovery, as you will have when you've flashed Siyah.
About the flashing itself: just search for rooting and flashing guides, here on xda or google. There are plenty of them.
Good luck.
Sent from the Matrix
TheATHEiST said:
Just reboot into download mode and flash Siyah kernel in ODIN. Once its installed you can reboot into custom recovery and flash new rom. I would advise to wipe data/factory reset in custom kernel before or after installing new rom.
Click to expand...
Click to collapse
I am now in ODIN 3 and have managed to boot into download mode. My question now is in ODIN where do I add the SiyahKernel S2-v4.1.5 (i went with the first version they have) where do I add it: bootloader, pda, phone or csc?
EDIT: PDA. <
Did exactly what Athiest suggested but now some purple yin yangish logo appears while turning on but nothing after, just a black screen
you have a bootloop.
go into cwm recovery clean cache and the advance clean dalvik cache and reboot, that might fix the problem.
SOLVED
Cosmic Blue said:
you have a bootloop.
go into cwm recovery clean cache and the advance clean dalvik cache and reboot, that might fix the problem.
Click to expand...
Click to collapse
VOILA!!!!! Genius, worked like a charm. I am out of the dog house lol
Hey Guys
I came from Stock Rom, rooted my device and flash recovery. And when i come to install any custom rom my device get into a boot loop.
Fortunately I got a back up and every time a try a different custom rom and i can go back to stock.
Well i have tried with the following roms
CM10
AOKP
Slim Roms
Paranoid
Everytime i have tried any of these roms i do carefully everty step. Just exactly like the tutorial says. I've been done this before, installing custom rom in other device, like nexus s, gs3, gs2. Im familiar with those stuffs.
And i don´t think it has to do with some corrupted file when i download the base.
I have tried to reflash recovery and nothing.
Tried to change kernel, i changed to siyah and nothing. After i install custom rom , the device just show the logo of the rom and ask select language and bam!, there is the boop loop
I don´t know what else to do.
I have read something about clear nand with odin , but i dont see those options.
If anyone knows what to do, please let me know.
Thnks
Aditional Info:
Baseband: GT-I9300XXELLA
Kernel: Stock
Root with Odin3 v3.04 - CF-Auto-Root-m0-m0du-gti9300t.tar
International Version
4.1.2
Recovery 6.0.3.1
I Flash the Recovery with Rom Manager V5.5.2.3
You are wiping everything before you flash right?
wangdaning said:
You are wiping everything before you flash right?
Click to expand...
Click to collapse
Yes, i did all the wipes everytime. Reset factory, Dalvik and format system (in some cases). And nothing, still boot loop. :crying:
krizalvarez said:
Yes, i did all the wipes everytime. Reset factory, Dalvik and format system (in some cases). And nothing, still boot loop. :crying:
Click to expand...
Click to collapse
Only other suggestion is trying another recovery, I use Philz which can be flashed through odin. Oh, and did you fix permissions?
Ok im gonna try with another recovery. And yes i tried fix permissions.
I let you know what happen
Sent from my GalaxyS3 from xda-developers app
wangdaning said:
Only other suggestion is trying another recovery, I use Philz which can be flashed through odin. Oh, and did you fix permissions?
Click to expand...
Click to collapse
Today i tried with philz, cool recovery btw, but nothing. My device still stuck on boop loop after i install any custom rom
I have tried these option after i get the boop loop> wipe factory reset, wipe cache partition. And before install> wipes, fix permissions. But none of these options have help me.
Another suggestion?
What happens with stock odin flashed roms ??
jje
It boots normally, everything's fine with stock rom.
Sent from my GalaxyS3 from xda-developers app
krizalvarez said:
It boots normally, everything's fine with stock rom.
Sent from my GalaxyS3 from xda-developers app
Click to expand...
Click to collapse
That suggests a problem that is one of the following .
EXT SD card faulty
Custom rom download faulty
CWM recovery faulty.
user not following instructions .
Try flashing a Samsung Based custom rom .
jje
What do you mean boot loop is it actually restarting after boot and restating again ??
Yes. Exactly that's what i mean. It restart over and over again.
External sd card > i dont have one
Recovery > i tried with cwm and philz
Downloaded rom > i have tried download from the xda developer site and tried with different files, different roms
Im pretty sure i follow the instructions just the way it is
Sent from my GalaxyS3 from xda-developers app
Flash samsung based cwm rom .
http://forum.xda-developers.com/showthread.php?t=1868004
jje
JJEgan said:
Flash samsung based cwm rom .
http://forum.xda-developers.com/showthread.php?t=1868004
jje
Click to expand...
Click to collapse
Hey JJE, what the purpose to flash a Samsung Based Rom with CMW?
Do i have to install Odexed or Deodexed ?
Thnks for your comments
krizalvarez said:
Hey JJE, what the purpose to flash a Samsung Based Rom with CMW?
Do i have to install Odexed or Deodexed ?
Thnks for your comments
Click to expand...
Click to collapse
Do i have to install Odexed or Deodexed ?
Whatever you want .
Difference see Google.
https://www.google.co.uk/search?q=O...fficial&client=firefox-a&channel=np&source=hp
Hey jje, what is the purpose of flash a samsung based rom?
With this I understand that it will alow me to flash a custom rom after that, is that right?
Another question, how can i go back like all factory settings, i mean clear everything. I format internal sd, factory reset, do the wipes, fix permissions and once again try to install a custom rom but phone doesn't boot after show logo. Actually i install the same rom in another i9300 and everything's go fine, so the file is ok.
Sent from my GalaxyS3 from xda-developers app
Samsung-based ROM is a custom ROM based on the stock one.
Hi, i'm new in these things so have a few questions.
Iwould like to flah thecyanogenmod but my galax 2s syas it is not a gt-I9100.
So i read some things about removing the assert line from a script and so on.
Do i need to flah an older rom before the cm11 nightly?
Do i need to flash the kernel first? or just use the latest cwm? (or rom manager/clockword?)
Can i reflash the S2 with an cyanogenmod kitkat version after i flashed it with an other kitkat rom for this device?
(still i did not succed to flash any rom to it)
thanks for any help !
JJSJJS said:
Hi, i'm new in these things so have a few questions.
Iwould like to flah thecyanogenmod but my galax 2s syas it is not a gt-I9100.
So i read some things about removing the assert line from a script and so on.
Do i need to flah an older rom before the cm11 nightly?
Do i need to flash the kernel first? or just use the latest cwm? (or rom manager/clockword?)
Can i reflash the S2 with an cyanogenmod kitkat version after i flashed it with an other kitkat rom for this device?
(still i did not succed to flash any rom to it)
thanks for any help !
Click to expand...
Click to collapse
First of all check if it g version or not.
To best of my understanding you can install it directly as far as you are rooted.
Sent from my GT-I9100 using xda premium
You don't need to flash an older version before KK. You just need KK compatible recovery. Or you can flash a KK compatible kernel, reboot to recovery and flash your KK rom.
Hello, thank you both for your replies.
Finally some clear answers
The model says GT-I9100 and not with g behind it, thanks.
I found some things about the status 7 error and about removing some line in a script in the zip.
So i will try the kitkat recovery (in my understanding this is also the kernel?) and then flash it with kitkat rom.
I would like to flash the one from cyangenmod, but doe it really mather which custom kitkat rom i take? At least they are all without the providers code like Vodafone or others?
Thanks again. I will update the thread if it succeeds or not.
Hi,
so i could not install the latest Recovery_CWM_6.0.4.7_I9100.zip as it gave an error E: signature verification failed.
then i tried recovery-clockwork-touch-5.8.1.5-galaxys2.zip and this works. But with this i can't install CM11. as i get the status 7 error.
So i will try some other versions kitkat compatible.
I also took a look at the kernels section but it is not clear wich one to use for CWM6 as i don't know what XXLSR or DDLS3 means, and which is correct for Netherlands.
Do you have any idea? (i am not allowed to post there yet)
Thanks for your help.
For choice of kernel -
1. Gustavo's - I don't remember the version. Check the op.
2. Dorimanx - you can try 10.43v100.
3. Apollo - 7.0b Cm
They will bring the KK compatible recovery you want on your phone. Then after rebooting to recovery you can flash any custom rom as they are not locked by any carriers.
banjara said:
For choice of kernel -
1. Gustavo's - I don't remember the version. Check the op.
2. Dorimanx - you can try 10.43v100.
3. Apollo - 7.0b Cm
They will bring the KK compatible recovery you want on your phone. Then after rebooting to recovery you can flash any custom rom as they are not locked by any carriers.
Click to expand...
Click to collapse
Thank you very much Banjara !
i'll keep trying, will report if i succeed
oh oh no good.....
JJSJJS said:
Thank you very much Banjara !
i'll keep trying, will report if i succeed
Click to expand...
Click to collapse
oh boy oh boy
i followed this http://forum.xda-developers.com/galaxy-s2/development/kernel-lazing-safe-stock-kernels-t2293576
and now it is stuck on boot screen, can't even reboot in recovery mode to get the back rom back pfffff
what should i do now......even the usb cable aint working, i'm flashing to the external sdcard via an other phone and the replace the sdcard to the galaxy s2
thanks for any help :crying::crying::crying::crying::crying:
JJSJJS said:
oh boy oh boy
i followed this http://forum.xda-developers.com/galaxy-s2/development/kernel-lazing-safe-stock-kernels-t2293576
and now it is stuck on boot screen, can't even reboot in recovery mode to get the back rom back pfffff
what should i do now......even the usb cable aint working, i'm flashing to the external sdcard via an other phone and the replace the sdcard to the galaxy s2
thanks for any help :crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
If you are able to go back to download mode
1. Flash a stock rom via odin
2. Flash a custom kernel via Odin. You might find some in the link you put there or you can search for hirox kernel. Remember, you have to download Odin flash able kernel and follow the op.
3. Once you have custom kernel, reboot to recovery. Flash any of the kernels in clockworkmod mentioned in my previous post.
4. Reboot to recovery. Flash your rom.
If you are unable to go to download mode try all the methods mentioned in the below link to bring it back to normal. It will need patience and perseverance. http://forum.xda-developers.com/galaxy-s2/general/guide-t2345831
Thank you for your patience and your help Banjara.
This forum and it's people are 100 times better the on Gyanomed were totally no support is given...
I will try it and come back, at least the phone able to start in the download mode.
Probably the usb connector has some loose contacts as i can get no contact with pc.
I got this phone from my brother and he told me that it never worked, just loading the battery
So i tried an other cable from an cheap android pad, but also no luck
maybe tommorow, i have another cable from an android stick pc at my job, maybe it will work
else i have to open it to check the connector under a microscope and probably resolder(hotair) it with a lot of flux... what a pitty... :crying:
lucky i have some experience on it, i repaired a lot of qtek phone, some years ago, always that connector broken.
I'm originally an tv(crt,lcd,plasma) repair technician, but now on an other job
Pfew, i managed to rsolder the connector with help of the microscope on my job.
I could even connect to odin. so that's is good progression. i had a wrong kernel downloaded, so it failed.
now i have the correct one and will use Siyah-s2-v6.0b5.tar
But unfortunately the battery is really emptying quickly when it stays in the phone, i don't know why.
So i will have to charge it an then give it another try with this kernel.
The ROM should still be original as i did not flash it before, just the kernel.
The phone is now saying battery empty, can't download.
To be continued...
Jippieeee!
GREAT !!!!
It worked! flashed the kernel Siyah-s2-6.0b5 and it started ! :victory:
Now what is the best way to proceed, there are so many topics on this it is overwhelming.
Should i first flash a Kernel or first a rom?
Can i flash them right after each other? (kernel reboots) so ROM and directly Kernel in one go?
thanks for your help!
{SOLVED}
Ok this is solved, thank you guys and dolls !
i managed to flash the cwm 6++++ and then the OMNI kitkat (latest) and the gAPPs
and it is working ! i am verry happy ! :laugh::laugh::laugh::laugh::laugh:
:thumbup::beer::beer:
one more thing
i noticed there is also another kernel now in the phone.
How to get rid of the yellow exclamation mark?
i saw some footage on youtube how to do it with the correct kernel.
But can i also extract the kernel from the ROM.tar i used and flash it with Odin?
Or is there another way?
thanks for your help. ---> edit
ok found some here: http://forum.xda-developers.com/galaxy-s2/orig-development/30-10-2012-k-la-lp-t1103399
but is it also good enough to unroot your device or are some functionality's then lost when using OMNI- rom ?
Thanks for your help
there arent any funcions lost it just gives your phone informations so that it thinks its all fine and dont displays the yelow horror . Btw i used TWRP KK kernel on my gs2 and installed prerooted rom aosp neatrom 5.8 kk and dont have problems with triangle. Also neatrom 4.1.2 with extended battery life is there if you dont like kitkat =D
Radelos said:
there arent any funcions lost it just gives your phone informations so that it thinks its all fine and dont displays the yelow horror . Btw i used TWRP KK kernel on my gs2 and installed prerooted rom aosp neatrom 5.8 kk and dont have problems with triangle. Also neatrom 4.1.2 with extended battery life is there if you dont like kitkat =D
Click to expand...
Click to collapse
Thanks Radelos, then i will try to unroot it again. And that will be it then.
Now using the OmniKK nightly of 8th of june, it runs very smooth, no issues till now, all is working well. :good:
btw idk what is the exact rom your willing to use but for no triangle would also do an clean install of stock rom, then root with framroot that you can find here on site and then flash KK compatible recovery and ofc kk rom with it. Here is the rom i used, its prerooted and on first boot starts direct into recovery so its for lazy ppl =D factory format data/system then flash TWRP touch recovery and in cwm reboot recovery option. And then just flash rom
Rom
http://uloz.to/x13p4YVr/drhd-base-lpq-re-light-tar
KK TWRP touch recovery
http://uloz.to/xyw9UkTk/kk-kernel-21-04-twrp-zip
Radelos said:
btw idk what is the exact rom your willing to use but for no triangle would also do an clean install of stock rom, then root with framroot that you can find here on site and then flash KK compatible recovery and ofc kk rom with it. Here is the rom i used, its prerooted and on first boot starts direct into recovery so its for lazy ppl =D factory format data/system then flash TWRP touch recovery and in cwm reboot recovery option. And then just flash rom
Rom
http://uloz.to/x13p4YVr/drhd-base-lpq-re-light-tar
KK TWRP touch recovery
http://uloz.to/xyw9UkTk/kk-kernel-21-04-twrp-zip
Click to expand...
Click to collapse
So with this process, will there be no yellow triangle?
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?
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.