Related
EDIT on Jan 18,2015
Please see post #9 for a flashable zip of the stock ROM with root that is taken after updated to B148.
Below original post has version B126.
******** ORIGINAL *********
Fix soft-bricked Mate 2 (MT2-L03) phone using TWRP
If you messed up the phone and it came to a state that phone can not boot into android, if you have TWRP installed and have a backup, then you know how to fix that easily.
But if you don't have your own backup, I have upload my system partition so hopefully you can use this to restore your phone. The backup is taken very close to stock, and it is rooted with SuperSU installed.
BTW, there is a "safe mode" boot method, so try that before using twrp recovery:
http://forum.xda-developers.com/asc...ted-amazon-app-store-stuck-boot-loop-t2872628 (post 6 and 7)
Steps to Restore you phone if all other ways failed:1. Your MT2-L03 need have bootloader unlocked, and TWRP recovery installed properly. Even your phone is soft bricked, as long as you can boot into bootloader mode, you can still unlock bootloader and install twrp recovery.Unlock bootloader: http://forum.xda-developers.com/ascend-mate2/general/progress-rooting-ham2-t2867975
Install twrp: http://forum.xda-developers.com/asc.../2014-09-22-teamwin-recovery-project-t28851442. Boot into twrp recovery and select "System" partition only, and backup it to your external storage (yes, I know your system partition is bad, this step is to create proper twrp backup directory)
3. Download following file to your PC, unzip it.http://tinyurl.com/qzxkm4x
FileName: TWRP_BACKUPS_stock-system-with-root.zip4. Turn off phone and take out your SD card out and plug into PC, then navigate to following directory under the SDCARD: \TWRP\BACKUPS\xxxxx, the xxxxx is a string that different in each phone
5. Copy all the files unzipped from step 3 to above location. overwrite any files with same name.
6. Put back the SDcard to the phone, and boot into TWRP recovery.
7. Choose restore, select the only entry that you did the backup, and select "System" only, perform the restore.
8. Wipe your dalvik cache, cache.
9. Then reboot.
10. If you still have problem, boot into recovery again, and wipe /data parition as well (Factory Reset).Download the MT2-L03 backup here:
http://tinyurl.com/qzxkm4x
FileName: TWRP_BACKUPS_stock-system-with-root.zip
And thanks @dbmj unlock bootloader, @Modding.MyMind build twrp recovery, and @D33PTHAWTE confirmation that this fixed his phone.
Glad you got this posted. This will be very vital to many people down the road. And great work on giving instructions to create a backup for the simplicity of automating the needed directories for usage of the actual shared backup. Thumbs up bro.
@D33PTHAWTE, welcome back
For everyone not getting TWRP to work I have done it on 3 HAM2s and all work try this.
1.flash this stock recovery https://drive.google.com/folderview?id=0B-nJFDpWA4MdVjhEYzU3TXlMZ0U&usp=sharing
2.even if you have your own use that because I know that works and I dont know what yours is.
3.boot into the recovery and make sure that its the stock recovery and its working.
4. restart the phone 2 or 3 times to be safe
5. flash using twrp using 15 second ADB installer.
Has anyone followed thoes steps and that recovery above? (not your own) if not try that and let me know. take a screen shot of what ADB is showing you so I can see that TWRP was successfully installed. Starting at square one. Flash twrp and show me its flashed.
superbass311 said:
For everyone not getting TWRP to work I have done it on 3 HAM2s and all work try this.
1.flash this stock recovery https://drive.google.com/folderview?id=0B-nJFDpWA4MdVjhEYzU3TXlMZ0U&usp=sharing
2.even if you have your own use that because I know that works and I dont know what yours is.
3.boot into the recovery and make sure that its the stock recovery and its working.
4. restart the phone 2 or 3 times to be safe
5. flash using twrp using 15 second ADB installer.
Has anyone followed thoes steps and that recovery above? (not your own) if not try that and let me know. take a screen shot of what ADB is showing you so I can see that TWRP was successfully installed. Starting at square one. Flash twrp and show me its flashed.
Click to expand...
Click to collapse
i tried several time cant boot into twrp ....tried through adb it says flash done in 1.1 or something sec seems like all went well ...but when u try and boot into recovery it goes to android recovery screen with broken android mark .....
other than this phone works well and boots normally into android and i can make calls etc ...its just when i try to boot into recovery it always goto ...factory recovery with android and red mark ....whats goign on ...thanks
Hey I tried this on my phone, I think everything worked okay. Android ui crashes constantly when my sim card is inserted. When I try to do the OTA update it says theres an error with facebook in the cust folder. I tried to copy that from the zip but it failed to copy. Im out of ideas of what to do next.
notoriouspk said:
i tried several time cant boot into twrp ....tried through adb it says flash done in 1.1 or something sec seems like all went well ...but when u try and boot into recovery it goes to android recovery screen with broken android mark .....
other than this phone works well and boots normally into android and i can make calls etc ...its just when i try to boot into recovery it always goto ...factory recovery with android and red mark ....whats goign on ...thanks
Click to expand...
Click to collapse
What button combination are you using? And did you have unlocked bootloader?
notoriouspk said:
i tried several time cant boot into twrp ....tried through adb it says flash done in 1.1 or something sec seems like all went well ...but when u try and boot into recovery it goes to android recovery screen with broken android mark .....
other than this phone works well and boots normally into android and i can make calls etc ...its just when i try to boot into recovery it always goto ...factory recovery with android and red mark ....whats goign on ...thanks
Click to expand...
Click to collapse
aragon257 said:
Hey I tried this on my phone, I think everything worked okay. Android ui crashes constantly when my sim card is inserted. When I try to do the OTA update it says theres an error with facebook in the cust folder. I tried to copy that from the zip but it failed to copy. Im out of ideas of what to do next.
Click to expand...
Click to collapse
Hi, I have seen these issues pretty frequent recently that:
1) /cust partition is not covered in this TWRP backup, so after restore, you may still got facebook app mismatch failure when upgrade.
2) Even after a successful OTA upgrade, many people (include myself) met problem to reflash the TWRP image.
So, give me a few days, I think I can make a flashable zip that has latest (B148) stock ROM with root, probably this weekend.
xordos said:
Hi, I have seen these issues pretty frequent recently that:
1) /cust partition is not covered in this TWRP backup, so after restore, you may still got facebook app mismatch failure when upgrade.
2) Even after a successful OTA upgrade, many people (include myself) met problem to reflash the TWRP image.
So, give me a few days, I think I can make a flashable zip that has latest (B148) stock ROM with root, probably this weekend.
Click to expand...
Click to collapse
Thank you so much!
Please try install this zip from recovery:
http://tinyurl.com/q62m68x
MT2L03_B148_Stock_ROM.zip
File Size: 670,252,615 md5: 684bcb2674367814b96eadfa0debe846
Click to expand...
Click to collapse
This is a clean Stock ROM (flashable zip) with Root after upgrade to B148 for MT2L03.
It should only be used for plain carrier unlocked Huawei MT2-L03. Other varies (carrier locked) MT2L03 is un-tested and may brick your phone.
This ROM include /cust, /firmware, /system and /boot partition.
The official B148 update also contains update to SBL1/ABoot/TZ/RPM partition, they are not included due to risk concern.
I didn't fully test this ROM, I just pickup the image from my early backups. I installed it to my already updated phone and boot up fine. So please try it and let me know if you see any problems.
Working great for me! thank you, fixed all my problems.
aragon257 said:
Working great for me! thank you, fixed all my problems.
Click to expand...
Click to collapse
Imei is correct after flashing this?
Moody66 said:
Imei is correct after flashing this?
Click to expand...
Click to collapse
A little confused on what you mean... My sim card works fine in my phone now
aragon257 said:
A little confused on what you mean... My sim card works fine in my phone now
Click to expand...
Click to collapse
Someone tried using a similar process to swap a consumer cellular mate to a standard mate. They lost their imei in the process.
Moody66 said:
Someone tried using a similar process to swap a consumer cellular mate to a standard mate. They lost their imei in the process.
Click to expand...
Click to collapse
Oh I dont think I did, I havent noticed anything. I do have the standard mate and not a consumer cellular mate.
standard ham2 bought from gethuawei
just testing your stock rom zip and everything works fine.
thank you for your effort and time.
after flashing i have no toggles and i dont have LTE so far
thugmafia said:
after flashing i have no toggles and i dont have LTE so far
Click to expand...
Click to collapse
toggle is set in settings -- notif panel, lte pls check apn settings.
xordos said:
toggle is set in settings -- notif panel, lte pls check apn settings.
Click to expand...
Click to collapse
its all gray out meaning i cant turn it on and the APN is set i used to get LTE on tmobile but now it juz 3G H 4G
Is your phone mt2l03 and bought as unlocked?
Another thing you can try is do a factory reset (to be safe backup /data first) and wipe cache, dalvik cache.
xordos said:
Is your phone mt2l03 and bought as unlocked?
Another thing you can try is do a factory reset (to be safe backup /data first) and wipe cache, dalvik cache.
Click to expand...
Click to collapse
yes i did i returned to the back up but still no LTE but the speed is the some
and one more thing i notice was the not home screen style to be able to hide the nar bar
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 had CM13 official build installed, all was well until I had OTA update which I have done many times on that phone as well as others. After update I was unable to login as my password/pin no longer worked. Factory reset solved that problem and when it booted back I was unable to read sim card or connect to wifi or even Bluetooth. Trying to flash stock resulted in failing. I tried using dload which results in fail. as well as extracting update.app and using fastboot which does flash however stuck on boot loop. If I install a stock rom through twrp it hangs at flash screen. If I flash cm13 it boot but I am unable to use 4g/wifi or anything.
AsuraDas said:
I had CM13 official build installed, all was well until I had OTA update which I have done many times on that phone as well as others. After update I was unable to login as my password/pin no longer worked. Factory reset solved that problem and when it booted back I was unable to read sim card or connect to wifi or even Bluetooth. Trying to flash stock resulted in failing. I tried using dload which results in fail. as well as extracting update.app and using fastboot which does flash however stuck on boot loop. If I install a stock rom through twrp it hangs at flash screen. If I flash cm13 it boot but I am unable to use 4g/wifi or anything.
Click to expand...
Click to collapse
Are you using the latest firmware for your phone?
muradulislam said:
Are you using the latest firmware for your phone?
Click to expand...
Click to collapse
Yes
u did wipe every thing before u flash stock ? u should fully wipe ur device . ( data, system cache , dalvik and internal memory ) all this should be wiped then u can flash each img throw TWRP to same partition , try again should work with stock then u can go back to CM !.
Yes through twrp and fastboot. Also when trying to flash using update.app I am on stock recovery
while wiping u got any error ? of success with 0 errors ?
No errors that, I don't think
When I try to wipe using stock recovery (factory reset) it always fails. Although I can wipe cache
AsuraDas said:
When I try to wipe using stock recovery (factory reset) it always fails. Although I can wipe cache
Click to expand...
Click to collapse
Try using dload after flashing stock recovery through bootlaoder.
I did, I just feels like I have tried every combination and every trick to get this up and running. IDK it seems like the cm13 update messed up a partition and only cm13 works and only partially works because 4g and wifi are not working at all. :'(
AsuraDas said:
I did, I just feels like I have tried every combination and every trick to get this up and running. IDK it seems like the cm13 update messed up a partition and only cm13 works and only partially works because 4g and wifi are not working at all. :'(
Click to expand...
Click to collapse
Well that could mean there is a problem with your EFS partition. But I don't know how an OTA could have messed it up. How did you update CM13? Did you use CyanDelta?
It was OTA which was flashed through TWRP recovery
In About Phone check to see if Baseband and IMEI numbers are shown. If not then something must be wrong with your EFS partition.
Going to stock through Huawei updater is the only way to fix this IMO, unless you have made a backup of your EFS partition earlier.
Try the Huawei update using another firmware since the one you have may be corrupted.
only sollution is trial and error,,
just make it a two way..
if you have stock recovery, try rollback package and install lollipop
and if youve twrp, download a lollipop firware backup and just rostore..
any one of those will get you on emui3 and you can start it fresh again..
gud luck
xskull03 said:
In About Phone check to see if Baseband and IMEI numbers are shown. If not then something must be wrong with your EFS partition.
Going to stock through Huawei updater is the only way to fix this IMO, unless you have made a backup of your EFS partition earlier.
Try the Huawei update using another firmware since the one you have may be corrupted.
Click to expand...
Click to collapse
having issue with EFS without a backup for it is like breaking ur device , installing stock will always fail .
if EFS not recognized or missing the only solutions is service center only .
and if ( only ) if the phone works he will not be able to get any network to work .
xskull03 said:
In About Phone check to see if Baseband and IMEI numbers are shown. If not then something must be wrong with your EFS partition.
Going to stock through Huawei updater is the only way to fix this IMO, unless you have made a backup of your EFS partition earlier.
Try the Huawei update using another firmware since the one you have may be corrupted.
Click to expand...
Click to collapse
No imei numbers are shown, and I have tried to go through Huawei updater but I just can't seem to get it to work
md1008 said:
No imei numbers are shown, and I have tried to go through Huawei updater but I just can't seem to get it to work
Click to expand...
Click to collapse
service center , EFS is missing or damaged u can't connect ur phone to network any more .
AsuraDas said:
I had CM13 official build installed, all was well until I had OTA update which I have done many times on that phone as well as others. After update I was unable to login as my password/pin no longer worked. Factory reset solved that problem and when it booted back I was unable to read sim card or connect to wifi or even Bluetooth. Trying to flash stock resulted in failing. I tried using dload which results in fail. as well as extracting update.app and using fastboot which does flash however stuck on boot loop. If I install a stock rom through twrp it hangs at flash screen. If I flash cm13 it boot but I am unable to use 4g/wifi or anything.
Click to expand...
Click to collapse
Can I know which version of stock ROM you are On before flashing custom ROM ?
So I contacted Honor support and they said since I unlocked bootloader that my warranty is void. I asked if they have out of warranty repair and they said they do not. Seems like my phone is now an iPod Classic with a touch screen since I can't even use wifi or Bluetooth. If anyone has any suggestions on how to fully restore this phone I am all ears
AsuraDas said:
So I contacted Honor support and they said since I unlocked bootloader that my warranty is void. I asked if they have out of warranty repair and they said they do not. Seems like my phone is now an iPod Classic with a touch screen since I can't even use wifi or Bluetooth. If anyone has any suggestions on how to fully restore this phone I am all ears
Click to expand...
Click to collapse
I am not sure but if there is a twrp backup on the internet for your phone, flash that using twrp...
Hi.
Yesterday i flashed on my phone ressurection remix on nougat. It booted up properly and everything was ok. So i decided to flash Boeffla kernel as i think its best. Phone was starting more than hour and then truned off. I booted it up in recovery mode just to reinstall system without the kernel and then first problem appeared. It couldn't mount E:/data because i had this problem once i knowed what to do (format data and data/storage) after this i flashed cm 13 to be sure that everything is working. There 2nd problem appeared, it had 0049 imei. I thought that i'll just flash the backup that i had in my phone but i forgot that it was deleted as i formated storage. I looked in my computer for efs backup and found a backup made by this
PHP:
https://forum.xda-developers.com/galaxy-s3/general/tool-backup-restore-efs-imei-sgsiii-t1901098
and restored it. After that i rebooted phone and i gave me "unknown" imei and baseband. What can i do? I also have efs pro backup but the app don't see it ;-;
Thanks for any help it will be appreciated
ps. If it's corrupted backup i can pay for writing the proper one, but i want to make sure that the backup i broken
you can open efs.img with 7zip and copy in twrp that files nv_data.bin and nv_data.bin.md5 to efs partition?
stock rom working ?
imo erase efs and radio partition and reflash in twrp, maybe that custom roms dont working for you (depends on version galaxy s3)
Before flashing anything else to phone, I also recommend flashing the latest stock ROM from sammobile.com with Odin to see if that restores the imei.
It cannot be opened as an archive. Customs are working properly because before this error with /data partition i used this rom and everything worked properly, then i decided to flash the boeffla kernel which i think caused whole problem. After flashing other modems it stays unknown
EDIT: I tried also zuluman patch modem but it didn't work. I don't have chance to go to stock by odin because my pc is not recognising it in download mode(probably broken usb port in phone)
its should working (opening with 7zip), do you have recovery twrp ? (easer way that "play" with updater-script)
stock rom you can flash via terminal in twrp
Did you flash the correct Boeffla kernel?. Are you sure you flashed the correct Boeffla kernel?.
Beamed in by telepathy.
shivadow said:
Did you flash the correct Boeffla kernel?. Are you sure you flashed the correct Boeffla kernel?.
Beamed in by telepathy.
Click to expand...
Click to collapse
Latest for lineage os which is a variation of cm and ressurection remix is some kind based on it if im not wrong ofc
I presume you wiped dalvik and reinstalled resurrection remix so the only way to go is back to stock. Any problems after that, at least you'll have a solid base to work from.
Beamed in by telepathy.
shivadow said:
I presume you wiped dalvik and reinstalled resurrection remix so the only way to go is back to stock. Any problems after that, at least you'll have a solid base to work from.
Beamed in by telepathy.
Click to expand...
Click to collapse
Stock + zulumans patch worked, backup wasn't corrupted. Thanks all of you guys that tried to help. I appreciate that
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.