10 hours after i tried using the swapper 2...my galaxy s3 GT-I9300 rebooted suddenly and got stuck in the galaxy s3 logo. I was rooted and had sotmax v14 running on it. I flashed it several times with that ROM and also cm 10.1 from the sd card. Then i flashed it with a stock ROM using odin. I had access to download mode and recovery mode. In the stock recovery mode it showed something like "E:/eror mounting efs((invalid arguement)).
I have very little knowledge about flashing and i do not even know what EFS is and thus i dont remember of taking a backup of that efs. I flashed it with CF root to access CWM recovery. Now in CWM recovery when i chose sd car it says
"E:cant mount sd card" and when i tried to mount efs it displayed "error mounting efs".
I have been trying hard for 2 days with little food. Any help would be highly appreciated. Help me. What should i do now?? Iam stuck on the galaxy s3 logo no matter what i do...i tried everything factory reset wipe data cache etc etc. please help!!!!
please help i have the same problem when i try to restore my efs folder
i have access to download mode and costum recovery but the phone is all time in bootloop in the logo of samsung galaxy s3 gt i9300
just restore the efs backup you've made. if you didn't, try restoring any nandroid backups, maybe they have efs included. if that doesn't work, try looking in the sdcard for some files that have "efs" in the name, some kernels back it up automatically. use adb to view the files (Google it). if that doesn't work, try flashing a stock rom and factory resetting from recovery.
and that is absolutely everything you can do.
Glebun said:
just restore the efs backup you've made. if you didn't, try restoring any nandroid backups, maybe they have efs included. if that doesn't work, try looking in the sdcard for some files that have "efs" in the name, some kernels back it up automatically. use adb to view the files (Google it). if that doesn't work, try flashing a stock rom and factory resetting from recovery.
and that is absolutely everything you can do.
Click to expand...
Click to collapse
thanks for your help my problem is solved by flashing a stock rom 4.0.4 with odin but i have cheked the phone bootloader update option
good, make sure to hit "thanks"
Glebun said:
just restore the efs backup you've made. if you didn't, try restoring any nandroid backups, maybe they have efs included. if that doesn't work, try looking in the sdcard for some files that have "efs" in the name, some kernels back it up automatically. use adb to view the files (Google it). if that doesn't work, try flashing a stock rom and factory resetting from recovery.
and that is absolutely everything you can do.
Click to expand...
Click to collapse
The main problem is I am not able to access the sdcard as it says sdcard cannot be mounted. I remember to have made backups with ROM manager but i dont have access to it. I had ICS 4.04 running on it when i purchased the phone. I tried flashing the phone with two compatible ROMs from Sammobile.com which are jellybean ROMs and factory resetting it, but that did not help too. Are those the stock ROM for the galaxy S3 or should I flash it with ICS 4.04??? Please help me. Thanks in advance!!!!
vijay005100 said:
The main problem is I am not able to access the sdcard as it says sdcard cannot be mounted. I remember to have made backups with ROM manager but i dont have access to it. I had ICS 4.04 running on it when i purchased the phone. I tried flashing the phone with two compatible ROMs from Sammobile.com which are jellybean ROMs and factory resetting it, but that did not help too. Are those the stock ROM for the galaxy S3 or should I flash it with ICS 4.04??? Please help me. Thanks in advance!!!!
Click to expand...
Click to collapse
Were you able to fix the problem?
Please help !!
Quote:
Originally Posted by Glebun View Post
just restore the efs backup you've made. if you didn't, try restoring any nandroid backups, maybe they have efs included. if that doesn't work, try looking in the sdcard for some files that have "efs" in the name, some kernels back it up automatically. use adb to view the files (Google it). if that doesn't work, try flashing a stock rom and factory resetting from recovery.
and that is absolutely everything you can do.
---------
thanks for your help my problem is solved by flashing a stock rom 4.0.4 with odin but i have cheked the phone bootloader update option
---------
:crying::crying:
I have got the exact same problem with my S3 GT-I9300, phone bootloop, error mounting efs after flashing omega rom aokp. Can you please explain in detail
which stock rom 4.0.4 you used ?
which odin version you used because I am finding that it is greyed out on every flashing of rom that I did ?
any other detail you think I should know coz I am quite new to this flashing stuff.
Thanks
Thanks you !!!
YESS i tried flashing the stock rom i was previously on cm10.2(andriod 4.3) now im stuck in a bootloop do i have to flash the gapps also?please urgent please reply
gmat11 said:
YESS i tried flashing the stock rom i was previously on cm10.2(andriod 4.3) now im stuck in a bootloop do i have to flash the gapps also?please urgent please reply
Click to expand...
Click to collapse
Try reading the stickies in general forum, follow the instructions on how to return to stock.
Hi
I reccently bought i9300 ( hongkong ) and it came with 4.3, i tried rooting it with CF-Root, The process itself completes with no problem but when i open SuperSu, It asks to update binaries but when i do it fails.
All of the fellow xda helpers have suggested to install CWM and than flash Update SuperSU ***.zip from chainfire, I did that as well ( i flashed the latest zip) But the problem is there.
Can anybody help me with that?
The CF-ROOT and flashable supersu i have flashed are:
UPDATE-SuperSU-v1.91
UPDATE-SuperSU-v1.86
UPDATE-SuperSU-v1.10
CF-Auto-Root-m0-m0xx-gti9300
CF-Root-SGS3-v6.4
Now as i am not rooted so i can't backup the EFS (i don't want to take the risk of loosing my IMEI) and flash stock 4.1.2.
-----------------------------
Here are the details of my phone:
Model no: i9300
Android version: 4.3
Baseband: I9300XXUGNA8
Kernel: 3.0.31-i902166 [email protected]#1
Build no: JSS15J.I9300ZSUBNB1
------------------------------
Thanks
Backup your data.Try to use factoy rom (XXUGMJ9) for odin with pit and repartition.. Flash philz touch recovery and flash lastest update-supersu-v2.01 and should work without error.
Enviado desde mi GT-I9300 mediante Tapatalk
MD500 said:
Backup your data.Try to use factoy rom (XXUGMJ9) for odin with pit and repartition.. Flash philz touch recovery and flash lastest update-supersu-v2.01 and should work without error.
Enviado desde mi GT-I9300 mediante Tapatalk
Click to expand...
Click to collapse
i already did a backup through cwm, Is it good enough ? as i have read in the forum that if you dont have efs backup and you flash stock through odin, you may end up with lost imei; That's the boat i don't wana be on ... so i await your response on that.
Also can you guide me or give me a link to PIT and Repartition stuff, as i am new to samsung, i moved from htc.
After flashing stock, philz, do i need to flash cf-root through odin or update-supersu will do the rooting trick?
Thanks for your response
predator_b4u said:
i already did a backup through cwm, Is it good enough ? as i have read in the forum that if you dont have efs backup and you flash stock through odin, you may end up with lost imei; That's the boat i don't wana be on ... so i await your response on that.
Also can you guide me or give me a link to PIT and Repartition stuff, as i am new to samsung, i moved from htc.
After flashing stock, philz, do i need to flash cf-root through odin or update-supersu will do the rooting trick?
Thanks for your response
Click to expand...
Click to collapse
You should only use pit files as a last resort! Use only if your phone is not booting or major problems like that and definitely not because you can't root!
If you flash latest PhilZ there is a option in the settings to fix supersu try that way first or try a different version of su from playstore.
tallman43 said:
You should only use pit files as a last resort! Use only if your phone is not booting or major problems like that and definitely not because you can't root!
If you flash latest PhilZ there is a option in the settings to fix supersu try that way first or try a different version of su from playstore.
Click to expand...
Click to collapse
using odin i have installed latest PhilZ recovery, although the superSu is having the similar problem but i was able to find " backup efs" underr custom backup, i think internally my phone is already rooted, as custom recovery went on smooth. Will that efs recovery be enough to bring my phone IMEI back? Can you suggest what else should i backup ?
predator_b4u said:
using odin i have installed latest PhilZ recovery, although the superSu is having the similar problem but i was able to find " backup efs" underr custom backup, i think internally my phone is already rooted, as custom recovery went on smooth. Will that efs recovery be enough to bring my phone IMEI back? Can you suggest what else should i backup ?
Click to expand...
Click to collapse
If done properly then yes also I would also suggest making another backup with PhilZ recovery there is a option in settings to do that ( you can never have too many backups) also if you want you can do a full nandroid backup which will restore your phone to how it was before you flashed anything.(but remember nandroid won't backup efs you have to do that separately)
For any fellow xdaz who are seeking help in the same case as mine, Let me update on what i did and what went wrong (although i am still not upto the rooting part)
so as i was on 4.3 ( I9300XXUGNA8)- The rom won't let me root, whatever i did, and i am talking about clearing cache, dalvik, cf-root, superSU update, clearing all superSU app and reinstalling via market and odin.
Than i thought i would ditch the rom and maybe downgrade ( for me that was the wrong idea )
along the way ( as suggested by " tallman43 " i did install PHILZ and did custom backup of efs and i made around 4-5 backups, Big thanks for the awesome suggestion ....i suggest you do the same, as trust me i later found out that 1-2 backups have corrupted files ( i don't know why).
i also downloaded neat rom and in that Aroma installer (rom installer) there was an option for efs backup as well, so i did that and installed that rom. Rom installed without any problem, root was also working fine, i personally love the rom but i have to give my phone to someone and i was hoping for total stock whereas in neat rom there are tags here and there, i would love to have em but as i said earlier...
i downloaded Stock 4.1.2 (I9300OZSEMK2) -- flashed it, flashed went fine but now i got 0000 as my imei, i tried restoring through philz but nothing happened
i restored previously made backup of my old 4.3 but now the imei was displaying " NULL "
finally i stopped there and searched the forums and read through many similar problems, i downloaded 4.3 (I9300XXUGNA8) from sam mobile , flashed it and voila the imei and network is back.
I am not sure what fixed the imei and why was it giving problems on 4.1.2 but i am happy with the results.
I will update for the rooting part and that would be my next step.
http://forum.xda-developers.com/galaxy-s3/general/ref-imei-efs-stuff-i9300-including-t2393289
I came across this thread as I am facing the same problem with rooting.
I was on a rooted i9300 and did an upgrade to 4.3 via Kies.
Now when I run through the rooting process using CF method, Odin posted success.
I see inside the console (while flashing cf auto root) that SU binaries are being installed and all. But once the phone reboots, root checker reports phone is not rooted.
I tried a couple of other ways and the closest I got was to see TWRP recovery console once, but once the phone reboots, and I try to go back into recovery - it is still Samsung's recovery console.
Actually all I want is to flash a custom ROM because the phone has been running ridiculously slow. Can I flash it through Odin (under AP) or I have to use a custom recovery like clockwork or TWRP.
duoxx said:
I came across this thread as I am facing the same problem with rooting.
I was on a rooted i9300 and did an upgrade to 4.3 via Kies.
Now when I run through the rooting process using CF method, Odin posted success.
I see inside the console (while flashing cf auto root) that SU binaries are being installed and all. But once the phone reboots, root checker reports phone is not rooted.
I tried a couple of other ways and the closest I got was to see TWRP recovery console once, but once the phone reboots, and I try to go back into recovery - it is still Samsung's recovery console.
Actually all I want is to flash a custom ROM because the phone has been running ridiculously slow. Can I flash it through Odin (under AP) or I have to use a custom recovery like clockwork or TWRP.
Click to expand...
Click to collapse
If you want only to flash a custom rom then you do not need to root custom roms come already rooted (alot of people make this mistake )..Just flash a custom recovery with Odin then follow the procedure in the stickies to flash a custom rom.
this is my story
- i have an efs backup from (4.1.2-I9300XXEMF6) and on stock(sammy) roms or stock based no problem with network .
- but if i flashed any aosp based rom i get unknown baseband problem and the same problem after try all efsv2 modems,patched modems ,old modems(also ril) and kernels and efs restore .
- sometimes after stock full firmware no error in baseband but no service and after any try to flash any baseband from cwm or efs restore i get unknown baseband again .
please help i want to use aosp rom
Click to expand...
Click to collapse
Edit fixed:
After 3 days of testing many methods here is steps that working:
1- copy your efs folder files to sdcard
2- after flash stock 4.1.2 root and adb try to format your efs using efs professional if no error go to last step but if you get (cant mount efs error) and phone doesn't boot go to next step
3-download this file Here and flash with odin this will fix can't mount efs and phone will boot normaly but no network
4- using xplore file manger and set access to root and mount and copy replace efs folder files with your original efs folder in step 1
After this network will work for stock and aosp roms
Please use this only if you getting unknown baseband on aosp roms
malakmagd said:
this is my story
- i have an efs backup from (4.1.2-I9300XXEMF6) and on stock(sammy) roms or stock based no problem with network .
- but if i flashed any aosp based rom i get unknown baseband problem and the same problem after try all efsv2 modems,patched modems ,old modems(also ril) and kernels and efs restore .
- sometimes after stock full firmware no error in baseband but no service and after any try to flash any baseband from cwm or efs restore i get unknown baseband again .
please help i want to use aosp rom
Click to expand...
Click to collapse
Flash stock 4.1.2 with odin, once verifyed its working then install custom recovery then try a asop rom.
Darke5tShad0w said:
Flash stock 4.1.2 with odin, once verifyed its working then install custom recovery then try a asop rom.
Click to expand...
Click to collapse
do you think that i forget to do this
flash , pit , repair efs with advanced box on Samsung ,etc with no hope
i want to know what make official roms only work
i founded today some thing new when i get unknown baseband i used efs pro or file manger and fixed nv_data.bin permisions modem work but after restart came back to unknown baseband but some times after many tries modem work but imei lost and the same after many tries
malakmagd said:
do you think that i forget to do this
flash , pit , repair efs with advanced box on Samsung ,etc with no hope
i want to know what make official roms only work
Click to expand...
Click to collapse
I wanted you to do this so we could start fresh and go from there since you have flashed many other items.
Ok thank you but i fixed it but not sure it will still for ever i will post procedures in my first post
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.