Hello everybody!
Unfortunately my cell phone has a softbrick and I don't know how to fix it.
Starting position (unlocked bootloader):
I was on 10.0.7 Xiaomi.eu ROM (worked very well) and installed LuckyPatcher. After patching a file in LuckyPatcher, a reboot came and it took a long time, after the reboot, both SIM cards no longer worked and no WLAN.
Then I installed the Xiaomi.eu ROM with TWRP again - same error, then the original FastbootROM - same error.
I entered + # 06 # in the phone app and lo and behold, the phone no longer has an IMEI.
I hope someone can help me.
I have a TWRP backup, I restored the EFS but nothing changed. HOW can I extract modemst1.bin and modemst2.bin from efs1.emmc.win and efs1.emmc.win.sha2?
Regards Mirakulixs
1. try flashing original boot image without magisk (idk... worth a try, that's what I do when I boot loop because of some crap I installed, though I didn't check if I somehow lost my IMEI)
2. try flashing stock rom using miflash
Hey (same error is no IMEI´s and no Mac-Adress and Baseband is unknown)
to point 1 - same error
to point 2 - same error
try to flash zip with twrp.. - same error
with mi flash fastbook rom - same error
Related
Hey there, i will try to write the essentials of my problem
At the moment i cant get TWRP installed no matter which way or which version at it seems....
Part 1 - How rooted the phone / installed TWRP at first
1) Updated Stock 8.2.10.0 to 8.5.4.0 (Android 7) via OTA update of the phone.
2) Found out after the update that my sim card does not work and could not find any solution to this
(only sms worked, the signal is at 100%, sometimes at "X", and cant use mobile internet or get/make calls + also tried other cards which did not work)
3) Decided to Unlock the Phone and Root it (Working at the moment).
4) Flashed TWRP (newsest version of official website).
Part 2 - How the Flashing of the Rom did end in boot-stuck
5) Backupped (Bugged) 8.5.4.0 Phone
6) Wiped System, Data, Cache, Dalvik. Then flashed official Qualcomm 8.2.10.0 Image.
7) Phone tried one hour to boot, then i decided it wont start ever / bugged and rebooted it.
8) Tried to install the rom several times, with more wipes, with many reboots and also with the new 8.5.4.0 rom again. But phone keeps hanging at Boot.
9) Finally i used the (bugged) full backup of 8.5.4.0and had my old phone back at least, but with the sim bug again ... and without custom recovery as u will read now.
Part 3 - Other approaches of rescuing the phone
9) Tried to flash an older TRWP version (Cofface or something) via Minimal ADB cause i read that maybe the twrp version is making troubles.
10) Restarting into Recovery brings only the Fastboot (Vol Up + Power AND Vol down + Power) ,,, so nothing installed
11) Tried like 10 different img of twrp - restarted -> no Recovery installed
12) Tried Flashify app -> No Recovery installed...
Part 4 - Errors i had while flashing recovery (only when using the "boot imgname.img" command)
i rmember one error (after typing the above command for the first time): "FAILED dtb not found"
and one time i receiverd (i think the 2nd time above command in a row): "FAILED: read failed - too many links"
The install of the recoveries itself never showed an error by the way. That worked regarding cmd log.
Update 1: Flashing stock recovery works. Only thing that worked so far...
Used a guide on the english miui site (cant post links cause i got a new account)
Basically just the same procedure but with stock img.
So im here now, with a 8.5.4.0 working, but not able to phone/mobile internet Redmi Note 4 Global.
And im getting out of ideas. Please help
hi
so i have a Lenovo K8 plus 3 GB ram variant. Let me explain what happened first.
I unlocked my device's bootloader to flash the patched boot image for magisk root, then this orange state sign started showing up eerytime i booted up. then when the latest update rolled out in march, i decided to relock the bootloader and then update my device. did it and then a red state sign showing up accompanied by bootloop (it said something like rollback kernel too). so I formatted the whole thing via sp flash tool and downloaded the stock rom.
now when i try to flash it, preloader flashes FINE, recovery flashes FINE, but when it comes to md1img it shows this error: STATUS_INSUFFICIENT_BUFFER (0xC0010007). I tried flashing all the files individually to find the cause of the problem and see exactly which particular flash file was causing the problem. results are as follows.
[STATUS_INSUFFICIENT_BUFFER (0xC0010007) ]- this error was displayed while flashing these files - md1img, md1dsp, md1arm7, md3img.
[ STATUS_SEC_IMG_TOO_LARGE (0xC0020005)] - only popped up while flashing the oem image.
when I exclude these files from the queue, the rest files flash fine.
In short, I have a bricked phone which i am unable to flash via sp flash tool.
Thanks in advance
JDsingh007 said:
hi
so i have a Lenovo K8 plus 3 GB ram variant. Let me explain what happened first.
I unlocked my device's bootloader to flash the patched boot image for magisk root, then this orange state sign started showing up eerytime i booted up. then when the latest update rolled out in march, i decided to relock the bootloader and then update my device. did it and then a red state sign showing up accompanied by bootloop (it said something like rollback kernel too). so I formatted the whole thing via sp flash tool and downloaded the stock rom.
now when i try to flash it, preloader flashes FINE, recovery flashes FINE, but when it comes to md1img it shows this error: STATUS_INSUFFICIENT_BUFFER (0xC0010007). I tried flashing all the files individually to find the cause of the problem and see exactly which particular flash file was causing the problem. results are as follows.
[STATUS_INSUFFICIENT_BUFFER (0xC0010007) ]- this error was displayed while flashing these files - md1img, md1dsp, md1arm7, md3img.
[ STATUS_SEC_IMG_TOO_LARGE (0xC0020005)] - only popped up while flashing the oem image.
when I exclude these files from the queue, the rest files flash fine.
In short, I have a bricked phone which i am unable to flash via sp flash tool.
Thanks in advance
Click to expand...
Click to collapse
hey did you get it fixed and can you please send the link to the stock rom
yayjk said:
hey did you get it fixed and can you please send the link to the stock rom
Click to expand...
Click to collapse
TRY ASKING THE QUESTION ON THIS THREAD
https://forum.xda-developers.com/android/help/how-to-make-simple-android-apps-qna-t3776780
---------- Post added at 05:00 PM ---------- Previous post was at 05:00 PM ----------
JDsingh007 said:
hi
so i have a Lenovo K8 plus 3 GB ram variant. Let me explain what happened first.
I unlocked my device's bootloader to flash the patched boot image for magisk root, then this orange state sign started showing up eerytime i booted up. then when the latest update rolled out in march, i decided to relock the bootloader and then update my device. did it and then a red state sign showing up accompanied by bootloop (it said something like rollback kernel too). so I formatted the whole thing via sp flash tool and downloaded the stock rom.
now when i try to flash it, preloader flashes FINE, recovery flashes FINE, but when it comes to md1img it shows this error: STATUS_INSUFFICIENT_BUFFER (0xC0010007). I tried flashing all the files individually to find the cause of the problem and see exactly which particular flash file was causing the problem. results are as follows.
[STATUS_INSUFFICIENT_BUFFER (0xC0010007) ]- this error was displayed while flashing these files - md1img, md1dsp, md1arm7, md3img.
[ STATUS_SEC_IMG_TOO_LARGE (0xC0020005)] - only popped up while flashing the oem image.
when I exclude these files from the queue, the rest files flash fine.
In short, I have a bricked phone which i am unable to flash via sp flash tool.
Thanks in advance
Click to expand...
Click to collapse
TRY ASKING IN THIS THREAD
https://forum.xda-developers.com/android/help/how-to-make-simple-android-apps-qna-t3776780
How to Unbrick Lenovo K8 Plus 4GB
Hi All
I tried many stock roms and many versions of SP flash tool but none helped me to unbrick my lenovo k8 plus (4gb ram).
I was trying to downgrade it to Naugat from Oreo but it shows same error every time.
Error is (SP Flash tool version latest 5.18)
" Error_Status_Sec_Insufficient_Buffer( 0xC002004B)
[Hint]:
Verified boot is enabled.
Please download signed image (md1img-verified.img) or disable verified boot."
Plzzz help same problem
Enabled verified boot ...how to disabled
Same problem my lenovo k8plus
Enabled verified boot ...how to disabled
You need to use "Lenovo Moto Smart Assistant" instead of SPFlash tool to flash and you will be good to go. You can get the tool from the Lenovo official website.
JDsingh007 said:
hi
so i have a Lenovo K8 plus 3 GB ram variant. Let me explain what happened first.
I unlocked my device's bootloader to flash the patched boot image for magisk root, then this orange state sign started showing up eerytime i booted up. then when the latest update rolled out in march, i decided to relock the bootloader and then update my device. did it and then a red state sign showing up accompanied by bootloop (it said something like rollback kernel too). so I formatted the whole thing via sp flash tool and downloaded the stock rom.
now when i try to flash it, preloader flashes FINE, recovery flashes FINE, but when it comes to md1img it shows this error: STATUS_INSUFFICIENT_BUFFER (0xC0010007). I tried flashing all the files individually to find the cause of the problem and see exactly which particular flash file was causing the problem. results are as follows.
[STATUS_INSUFFICIENT_BUFFER (0xC0010007) ]- this error was displayed while flashing these files - md1img, md1dsp, md1arm7, md3img.
[ STATUS_SEC_IMG_TOO_LARGE (0xC0020005)] - only popped up while flashing the oem image.
when I exclude these files from the queue, the rest files flash fine.
In short, I have a bricked phone which i am unable to flash via sp flash tool.
Thanks in advance
Click to expand...
Click to collapse
Try with Lenovo Moto Smart Assistant. I too have bricked my phone... but I've successfully started my phone using this tool. you will get official signed ROM from here.
you can use LMSA tool to rescue,90% sucessfully ,don't use splashtool beacause it's many error if you choose wrong version
Had the same problem. Can confirm Lenovo's tool sucessfully recovers ohone from bricked state. A lifesaver!
Downloaded from https://lenovomobilesupport.lenovo.com/br/pt/downloads/ds101291-rescue-and-smart-assistant-lmsa
then updated to version 5.9.2.4 from inside the app itself
I've bricked my phone and am in need of help!
What I've done:
Unlocked bootloader with a code from DC-Unlocker then using minimal ADB and Fastboot to unlock
Flashed TWRP 3.1.1
Installed Magisk
Took TWRP backup - but I was unable to backup Data (I believe this was due to encryption - recovery.log shwed errors initially on Bluedorid files)
Wiped data with TWPR to try and do a factory reset
This is where my problems started and now I cant restore boot with TWPR the error is "No such file or directory"
I can ADB pull my recovery.log which says
Read info file, restore size is 12444160
Restoring 6 partitions...
Total restore size is 4512MB
I:Restore filename is: /external_sd/TWRP/BACKUPS/L5NDU17B18000539/Stock V7 2018-06-23--16-58-45/boot.emmc.win
I:Restore file system is: 'emmc'.
I:Restore file system is: 'emmc'.
Restoring Boot...
Error opening: '' (No such file or directory)
I can restore OEM recovery and do a factory reset but it hangs at 99%
power down then it goes back to factory reset and goes to 100% - message "Reset Successful!"
but... then it gets stuck in a boot loop
I've tried downloading other stock ROMS and extracting and flashing images via fastboot (Boot, cust, product, recovery, system, vendor, version)
I've tried Huawei Multi-tool but I lack the Userdata.img disk image
I've tried flashing Resurrection Remix N v5.8.5 For Honor 9 (STF) but without success, although the TWRP install says it is successful and the vendor.img flashes fine.
I've tried extracting UPDATE.app files and putting them in sd_card/dload and then 3 button resetting
I've tried the above in external_sd/dload (not sure why - desperation)
I've tried looking on as many threads as I can find on XDA but with no luck
I can always get to fastboot, flash TWRP or OEM recovery, I can also run ADB commands via Putty (in command line they display strangely)
Any suggestions would be greatly appreciated! I am at a loss an quite frustrated, and have been working on this for maybe 15 hours now.:crying:
LOL, Stop your mumbo-jumbos.
I guess you'r still with nougat partitioning because you're using a pretty much outdated twrp.
So just dload flash a nougat 'service repair firmware' from the same region you're firmware is actually, and not any random update.app you 'made' yourself.
For this you'll need a micro-sdcard (or usb-otg) exfat formated :
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
Fixed!
Thank you, I think I even saw this thread but for some reason did not download the file, also the exfat formatting tip was excellent. I owe you a beer!
Can I always use this method to go back if I totally destroy things again even If I update to Oreo?
oslo83 said:
LOL, Stop your mumbo-jumbos.
I guess you'r still with nougat partitioning because you're using a pretty much outdated twrp.
So just dload flash a nougat 'service repair firmware' from the same region you're firmware is actually, and not any random update.app you 'made' yourself.
For this you'll need a micro-sdcard (or usb-otg) exfat formated :
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
Click to expand...
Click to collapse
Unfortunatly, there only nougat 'service repair firmware' available publicly as far I know.
So, for now, you can only use this when on nougat.
When on oreo, you should use HuRUpdater with oreo's Twrp.
Or if you're oreo device is really messed badly, a paying app called DC-Phoenix then HuRUpdater.
Hi everyone,
I ran out of ideas with my problem, and could really use some help / advice with this.
Trying to updgrade my STF-L09C432 from B368 to B385 using HuRu updater, something went wrong and now it bootloops after the blue Honor logo.
Fastboot, Huawei eRecovery and TWRP are still working and accessible, my device is bootloader unlocked and says FPR unlock in fastboot mode.
So here's the detailed steps and procedure which I followed:
0) TWRP Backup of System + Data
1) Load three update files (FullOTA) via FF: update.zip (update.zip), update_data_full_public.zip (update_data_full_public.zip), update_full_STF-L09_hw_eu.zip (STF-L09_hw_eu/update_full_STF-L09_hw_eu.zip)
2) Create folder on SD-card with above files and TWRP v0.3 as recovery.img and the HuRu 0.4 zip file. Additionally I've left the HuRu 0.3 in the same folder renamed as HuRUpdater_0.3_old.zip
3) Installed the HuRu 0.4 from TWRP with zip verification disabled (tried before with enabled, but it failed -> call me stupid but I've double checked the checksum with a new download, so I took the risk).
4) the installation log showed warnings about some missing .zip files, but I ignored those as well, as I've never heard of them and didn't have them from FF.
5) rebooted the system and caught the first bootloop
Now I tried myself to fix it the following way, but unsuccessful until now:
1) Flashed TWRP into recovery_ramdisk because I didn't know the right procedure to boot into it
2) Flashed the new B385 versions of KERNEL.img, RAMDISK.img and RECOVERY_RAMDIS.img which I extracted from the UPDATE.APP -> still bootloop
3) Flashed TWRP into recovery_ramdisk again because I still didn't know the right procedure to boot into it
4) Flashed the old B368 versions of KERNEL.img, RAMDISK.img which I extracted from the UPDATE.APP, but not the RECOVERY_RAMDIS.img this time -> still bootloop
5) Then I've managed to boot into TWRP finally, and tried to restore my previous backup as a last resort, but that still didn't resolve my bootloop
Anybody has any idea what I could still try? Maybe I'm missing something obvious, or I'm still to new to this to see what is wrong.
If possible I'd like to keep my data intact, but I could probably extract most of it out of the backup, if nothing else helps.
Thank you very much!
Best regards,
Chris
Nobody has an idea?
Maybe the Seniors on the Honor9, @OldDroid or @zxz0O0?
After I've tried to restore the previous TWRP backup, now also TWRP won't boot anymore, therefore I'm stuck with fastboot or the Huawei stock recoveries...
Schrubbi said:
Nobody has an idea?
Maybe the Seniors on the Honor9, @OldDroid or @zxz0O0?
After I've tried to restore the previous TWRP backup, now also TWRP won't boot anymore, therefore I'm stuck with fastboot or the Huawei stock recoveries...
Click to expand...
Click to collapse
well, aslong as its still unlocked (frp & bl) i'm able to help.
Do you have telegram? if so, send me your username through pm.
Regards
I managed to get into TWRP again when I've installed the latest kernel and recovery images. After that I've realized that I still had Magisk installed and Active.
Uninstalling that solved my bootloop for now.
Unfortunately my backup restore just returned me to the previous version B368 which I already had installed... so lets see what happens if I apply the update again
---------------------
Edit:
Update applied, without magisk installed, still bootloop... At least the way back was quicker this time
Any hints what's going wrong are appreciated!
Really need help here.
I have an H930DS with TWRP installed, ROM Stock Pie 9.0 H930DS30b_00_OPEN_ESA_DS_OP_0903.
Bootloader is unlocked and rooted.
I tried flashing custom ROM through TWRP, it succeeded and able to boot into OS.
But since then:
1. The Sim Card is not working. Data is disabled. My simcard is ok, becuase I tried moving it to another phone, and it works just fine.
2. In the Settings - About screen, the Device Name is UNKNOWN. Model Name stated UNKNOWN as well. Cannot make/receive call.
I tried reinstall some others custom ROM, but always ended the same error. The simcard is disabled.
I tried reflashing the stock firmware with LGUP Tool (patched common.dll), it detected my device, but when trying to flash the ROM, at 4% it always give me and error message:
Error: 0x81000302, Please use latest DLL
LAF Protocol version is not match DLL = 0 Device = 57081888
Screenshot of the error message:
https://ibb.co/GRM67g2
PS: My device still able to boot into recovery TWRP, enter download mode, and booting into OS. But no data & no simcard.
Please help. Thank youuu
It works, simply download the TWRP-Flashable LG Stock ROM, Install Magisk & AK3_RCTD_Remover, Format Data, Reboot into Recovery, reinstall Magisk, then Reboot.
Tqqqq