Related
Hello hello,
I unlocked bootloader, installed TWRP 2.8.7.0 (adb -> fastboot method) and then I flashed SuperSU 2.46 zip. After reboot from TWRP my phone stuck.
I can't access TWRP or i don't know how to…
System isn't starting BUT sometimes after few minutes of seeing LG logo i see standard wallpaper and suddenly animation freezes. That's all.
When i go to recovery mode (voldown+power, release power and press power again) I can "do" factory reset. I choose 2xYES and i see green android. Then phone is restarting but i should enter to TWRP, right?
I tried to flash stock system (kdz, tot, dz) via:
- LG Flash Tool 2014
- LG Flash Tool 1.8.6.527
- LGUP
- LG Bridge
but nothing…
My phone PID and IMEI is null :/ (and "CUMSS" to :?)
I tried fix that with QPST (2 different versions) but in device manager my phone is only detected as COM port. No "Android Device". I can't read and write anything…
adb isn't working
I tried all USB 2.0 ports, different drivers, roms (even not for 815), dlls.
I fought 3 days and still have brick, not smartphone
I have only download mode working.
I can send commands to com port (Send_Command.exe) but sometimes nothing happen, sometimes i see "fail" after sent command.
Any ideas? Can I install recovery through download mode? Or maybe somebody know how to send files to phone in download mode but without adb?
I had stock rom MM V20L. What else you need to know?
Thanks for any suggestions, sorry for chaos in post and my english.
After trying different roms in different programs with 3 versions of dlls and different drivers…
I found solution: just reinstalled .NET Framework and then finally i flashed by LGUP (refurbish, v20L, kdz, dll 0.0.3.23)!
Welcome back H815
2 0 said:
After trying different roms in different programs with 3 versions of dlls and different drivers…
I found solution: just reinstalled .NET Framework and then finally i flashed by LGUP (refurbish, v20L, kdz, dll 0.0.3.23)!
Welcome back H815
Click to expand...
Click to collapse
where did you founf v20L kdz i need it because my phone wont flash any kdz i think its to prevent downgrades
https://lg-firmwares.com/lg-h815-firmwares/
Try some from skdubg's link. This is probable the same as mine
PLS Europe PL/Poland H81520l_00_0928.kdz 1.68 G 2016-11-25
Click to expand...
Click to collapse
download-file/?fileId=4325 I can't post links
This is MD5 of my file 8f685baf42869c50ec5f1b7770aa3957 *H81520l_00_0928.kdz
If you still can't flash then i will upload my kdz somewhere. GL
LG G4 Model F500L Stuck on download mode After Downgrade
Hi
i have a problem with my LG G4 Model F500L i try to downgrade from Marsmallow to Lolilpop By Flashing with LGUP Tool when i flash it. it error at 16% boot fail. So i disconnect USB and pull out battery and when i turn on it stuck on download mode.. i have try to flash with any firmware and any LG Tools but it's still fail at writing boot step i had try with Optopus box but it's still fail at wrting boot fail what is the problem . i need help now.... i just bought my phone for a week. Thanks for your helping ....
When i try to flash a rom using QFIL i am getting bellow error
Download Fail:System.Exception: Failed to Switch to Emergency Download mode
at QC.QMSLPhone.Phone.QPHONEMS_SwitchToEDL()
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
Download Fail:Switch To EDL FailSystem.Exception: FireHose Fail
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
at QFIL.Tech.DownloadTech.SwitchToEDL()
Finish Download
malli_18arjun said:
When i try to flash a rom using QFIL i am getting bellow error
Download Fail:System.Exception: Failed to Switch to Emergency Download mode
at QC.QMSLPhone.Phone.QPHONEMS_SwitchToEDL()
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
Download Fail:Switch To EDL FailSystem.Exception: FireHose Fail
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
at QFIL.Tech.DownloadTech.SwitchToEDL()
Finish Download
Click to expand...
Click to collapse
shutdown your phone, press volume up and until it connect to the pc
solved: disconect baterry
connect cable
and press vol up -vol down and download qfill ok
ahmetbysoy said:
solved: disconect baterry
connect cable
and press vol up -vol down and download qfill ok
Click to expand...
Click to collapse
thanks its worked.
please help. Flashing Micromax Sliver 5 .
Validating Application Configuration
Load APP Configuration
Load ARG Configuration
Process Index:0
Validating Download Configuration
Image Search Path: C:\
Programmer Path:C:\Users\dell\Desktop\Micromax_Q450_V3_12.08.15\Micromax_Q450_V3_12.08.15\Firmware\prog_emmc_firehose_8916.mbn
Image Search Path: C:\Users\dell\Desktop\Micromax_Q450_V3_12.08.15\Micromax_Q450_V3_12.08.15\Firmware
Image Search Path: C:\Users\dell\Desktop\Micromax_Q450_V3_12.08.15\Micromax_Q450_V3_12.08.15\Firmware
RAWPROGRAM file path: C:\Users\dell\Desktop\Micromax_Q450_V3_12.08.15\Micromax_Q450_V3_12.08.15\Firmware\rawprogram_unsparse.xml
PATCH file path:C:\Users\dell\Desktop\Micromax_Q450_V3_12.08.15\Micromax_Q450_V3_12.08.15\Firmware\patch0.xml
Start Download
COM Port number:6
Switch To EDL
Download Fail:Switch To EDL FailFailed to Switch to Emergency Download mode
Finish Download
Hello all,
Yesterday night i slept with 3% charge and from today morning I am stuck on lenovo logo whenever I am trying to start.
I'm damn worried for data.
I've tried with some steps from this page but neither I am able to get device working nor am I able to get into recovery mode.
FYI, I haven't tweaked anything in my cell yet. Its a factory piece yet as bought before 2 years.
Thanks Guys.
How about for non removable battery? i have the same error
Download Fail:System.Exception: Failed to Switch to Emergency Download mode
at QC.QMSLPhone.Phone.QPHONEMS_SwitchToEDL()
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
Download Fail:Switch To EDL FailSystem.Exception: FireHose Fail
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
at QFIL.Tech.DownloadTech.SwitchToEDL()
Finish Download
---------- Post added at 02:36 PM ---------- Previous post was at 02:32 PM ----------
ndn13d said:
thanks its worked.
Click to expand...
Click to collapse
i have the same issue but my battery non removable Ive been search my device but no one iv seen
Download Fail:System.Exception: Failed to Switch to Emergency Download mode
at QC.QMSLPhone.Phone.QPHONEMS_SwitchToEDL()
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
Download Fail:Switch To EDL FailSystem.Exception: FireHose Fail
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
at QFIL.Tech.DownloadTech.SwitchToEDL()
Finish Download
ndn13d said:
thanks its worked.
Click to expand...
Click to collapse
it didnt worked for me , my phone is just having the looping back to logo . not having port for 5 minutes too.. please help
aditya krishna b said:
it didnt worked for me , my phone is just having the looping back to logo . not having port for 5 minutes too.. please help
Click to expand...
Click to collapse
I had the same problem. If you have TWRP recovery on your phone already you might be able to boot into recovery mode. If you can, then you'll be able to copy an image or TWRP Recovery from your computer and hopefully flash from there.
I couldn't load a rom successfully that way BUT by flashing an image file onto the Vibe P1 and then switching the phone OFF (using TWRP) it enabled me to enter fastboot and successfully load an OS using QFIL. I managed to load p1a42 onto my p1c58 but now need to sort my modem out.
So:
Boot into TWRP recovery
Attempt to load a recovery file or image on to your Vibe P1 by USB
Retry TWRP Recovery to load the recovery file
If it's not successful then retry QFIL and hopefully it will work for you.
Give it a go! Good luck bud!
in sut tool error code 0xc3ba problem
how solve it
Almost Bricked Phone, Lenovo Vibe Shot z90a40
TimboD said:
I had the same problem. If you have TWRP recovery on your phone already you might be able to boot into recovery mode. If you can, then you'll be able to copy an image or TWRP Recovery from your computer and hopefully flash from there.
I couldn't load a rom successfully that way BUT by flashing an image file onto the Vibe P1 and then switching the phone OFF (using TWRP) it enabled me to enter fastboot and successfully load an OS using QFIL. I managed to load p1a42 onto my p1c58 but now need to sort my modem out.
So:
Boot into TWRP recovery
Attempt to load a recovery file or image on to your Vibe P1 by USB
Retry TWRP Recovery to load the recovery file
If it's not successful then retry QFIL and hopefully it will work for you.
Give it a go! Good luck bud!
Click to expand...
Click to collapse
I have twrp but by mistake have wiped out whole system too.
I can access twrp and from here {https://download.mokeedev.com/file.php} i have download mokee 71.2, copied in sdcard and when i try to flash this into phone, it start flashing and detect device and after detecting, the phone just turned off everytime.
i also have download stock rom but in QcomDLoader my phone is not detecting, but in QFIL its get detected but got same error msg as everyone have, also i can not remove battery too.
thanks,
need help
wiped everything in twrp lenovo phab
prajapatdinesh55 said:
I have twrp but by mistake have wiped out whole system too.
I can access twrp and from here {https://download.mokeedev.com/file.php} i have download mokee 71.2, copied in sdcard and when i try to flash this into phone, it start flashing and detect device and after detecting, the phone just turned off everytime.
i also have download stock rom but in QcomDLoader my phone is not detecting, but in QFIL its get detected but got same error msg as everyone have, also i can not remove battery too.
thanks,
need help
Click to expand...
Click to collapse
did you solve the proble? i have same problem
The more secure is to flash stock rom. No need to reboot to recovery
ahmetbysoy said:
solved: disconect baterry
connect cable
and press vol up -vol down and download qfill ok
Click to expand...
Click to collapse
I have been more than ten days trying thousands of explanations and programs. Your explanation is so simple and effective that I thank you infinitely.
It works 100% on sealed phones, you do not have to remove the battery, you just have to let it run out and carry out your process.
WORKS 100%
Thanks for sharing!
My z00ad (ze551ml) dead severals days ago. Right now it just showing 4 colors bar after 2 times vibration.
Why dead?
Upgrade to MM by manual update (placing MM firmware in internal storage and automatically update OS) then after I found many bugs in wifi connection & bad performance, I decide to downgrade it to LL again using xFSTK downloader using 3 files which is fnx dwr, ifwi, image os files from amtech.vn. The proces was success until FW & OS download,, but not directly go to bootloader screen after 4 colors bar.
Trying button combinations, replug power pin, trying different cable & PC and OS (win7, XP, win8) trials for 5 days straight but still fail (300~ trials).
I surrender to ubrick with xFSTK 1.7.0 and trying to use Intel Phone Flash Tool 5.5.2.0. Because this software also have xFSTK feature and GPflash setting
I already try to flash with RAW files (open it with winrar, unrar and found flash-ramdump.xml) but unfortunatelly Intel Phone Flash Tool say:
02/09/17 12:15:53.597 ERROR : Automatic reboot is not supported on this device, please reboot the device manually
02/09/17 12:15:53.597 ERROR : [Port 0/1/1] Failed to reboot the device
preview error using Phone Flash Tool 5.5.2.0
i.imgur[dot]com/xLbJFci.jpg
Maybe I have to flash using firmware.zip not raw files. But I cant find flash.xml in severals firmware from asustek.
I need an information about what firmware which have flash.xml in the zip file? (not RAW firmware), because I need this file for flashing.
Please help
My device(Nubia z11 minis) is hard bricked, i think its a dead bootloader, my computer detects device at 9008(old I think) port no partition of device is visible. I tried Qfil and Nubia studio tool both fail with error Qfil gave me Sahara error couldn't communicate with flash programmer
While Nubia tool gave me file not found error. I need help to fix.
Device has no led
Does anybody here knows about MPRG8953.Mbn
And 8953_msimage.mbn
Nikhil Joshi said:
My device(Nubia z11 minis) is hard bricked, i think its a dead bootloader, my computer detects device at 9008(old I think) port no partition of device is visible. I tried Qfil and Nubia studio tool both fail with error Qfil gave me Sahara error couldn't communicate with flash programmer
While Nubia tool gave me file not found error. I need help to fix.
Device has no led
Click to expand...
Click to collapse
Ok. Folder with raw image (where is rawprogram abd mbn file) should be in root of c: partition.
Also, try miflash if qfil fails
Already tried it's no use
Found a solution but i need two file MPRG8953.mbn and 8953_msimage.mbn
https://gizchina.it/2017/01/nubia-z11-mini-s-unbrick-nubia-studio-tool/
Послато са NX549J уз помоћ Тапатока
Nikhil Joshi said:
Found a solution but i need two file MPRG8953.mbn and 8953_msimage.mbn
Click to expand...
Click to collapse
i want it too.
Anyone try this link?
China or Global ROM?
https://drive.google.com/file/d/1uBnrVo_TfIa8iUWrDGr7j90SojFEs-4z/view
and
https://drive.google.com/file/d/1wM1ymz9CRArNcmqaIjlVZbrWOlis0VqJ/view
My phone is blinking when connected to my system, but no display, no recovery mode.. its just blink.. none of the side keys responded to boot menus/ fastboot menus..
i followed instructions, its getting patched through qfil tool, but still the same problem. phone is not booting to normal.
any clue will help to recovey my phone...
So i've bricked my oneplus 3 (oxygen 5.0.5) rooted with magisk 13 by flashing a custom rom, it was in a bootloop after the update.
I tried factory resetting via TWRP because i had a backup ready but the reset somehow failed and my phone rebooted and showed a failed md5 check with these checks failed:
* Cache : Failed
* Boot : Failed
* System : Failed
* Recovery : Failed
* md5 checksum failed
When i try to boot into recovery mode (twrp) it gives me the same message and loops.
Since then i've tried flashing several recovery.img's with several modded and non modded twrp versions, none of them got me into twrp.
I have tried the popular mega unbrick guide from Naman Bhalla twice but didn't help either.
Any ideas ?
Thanks in advance
EpicLawR said:
So i've bricked my oneplus 3 (oxygen 5.0.5) rooted with magisk 13 by flashing a custom rom, it was in a bootloop after the update.
I tried factory resetting via TWRP because i had a backup ready but the reset somehow failed and my phone rebooted and showed a failed md5 check with these checks failed:
* Cache : Failed
* Boot : Failed
* System : Failed
* Recovery : Failed
* md5 checksum failed
When i try to boot into recovery mode (twrp) it gives me the same message and loops.
Since then i've tried flashing several recovery.img's with several modded and non modded twrp versions, none of them got me into twrp.
I have tried the popular mega unbrick guide from Naman Bhalla twice but didn't help either.
Any ideas ?
Thanks in advance
Click to expand...
Click to collapse
Your only way out seems to be the Mega Unbrick Guide. What happens when using it? Is your phone recognised properly? Which Windows version are you using?
tnsmani said:
Your only way out seems to be the Mega Unbrick Guide. What happens when using it? Is your phone recognised properly? Which Windows version are you using?
Click to expand...
Click to collapse
Thanks for the reply,
When i use the tool, it seems to be working fine until the reboot. The tool detects my device as a com device and downloads everything and completes the downloading process without errors.
When the tool is done i unplug my phone to let it reboot, the md5 checksum fails again BUT this time not with the "recovery : failed" error. At this point i can still not boot into recovery mode. The only thing i can acces is the fastboot screen.
I am using windows 10 Version 1709 on an ASUS ROG g502 laptop.
EpicLawR said:
Thanks for the reply,
When i use the tool, it seems to be working fine until the reboot. The tool detects my device as a com device and downloads everything and completes the downloading process without errors.
When the tool is done i unplug my phone to let it reboot, the md5 checksum fails again BUT this time not with the "recovery : failed" error. At this point i can still not boot into recovery mode. The only thing i can acces is the fastboot screen.
I am using windows 10 Version 1709 on an ASUS ROG g502 laptop.
Click to expand...
Click to collapse
It can't be "as a com device". It has to be detected as defined in the Guide, something like QDLoader 9008 or so. I am not sure of the exact name. Check the Guide. Unless it is detected exactly as described in the Guide, the unbricking will not be successful. Plus sometimes you have to use the tool multiple times before it succeeds.
If, as you say, there are no 'failed' messages and if you are able to boot to the bootloader, you can also try sideloading the OOS ROM.
EDIT: Must have been asleep.
EDIT: On Win 10, disabling driver signature verification is very important before you install the Qualcomm drivers.
tnsmani said:
It can't be "as a com device". It has to be detected as defined in the Guide, something like QDLoader 9008 or so. I am not sure of the exact name. Check the Guide. Unless it is detected exactly as described in the Guide, the unbricking will not be successful. Plus sometimes you have to use the tool multiple times before it succeeds.
If, as you say, there are no 'failed' messages and if you are able to boot to the bootloader, you can also try sideloading the OOS ROM.
EDIT: Must have been asleep.
EDIT: On Win 10, disabling driver signature verification is very important before you install the Qualcomm drivers.
Click to expand...
Click to collapse
My device was detected as a 9008 by my computer, but by the tool it was detected as a com device. driver signature vertification was disabled when trying the tool multiple times, but i can try to use it on another computer.
Sideloading the OOS rom didn't work the first time i tried it, but i am not very familiar with that so i can try that again aswell.
Thanks.
EpicLawR said:
So i've bricked my oneplus 3 (oxygen 5.0.5) rooted with magisk 13 by flashing a custom rom, it was in a bootloop after the update.
I tried factory resetting via TWRP because i had a backup ready but the reset somehow failed and my phone rebooted and showed a failed md5 check with these checks failed:
* Cache : Failed
* Boot : Failed
* System : Failed
* Recovery : Failed
* md5 checksum failed
When i try to boot into recovery mode (twrp) it gives me the same message and loops.
Since then i've tried flashing several recovery.img's with several modded and non modded twrp versions, none of them got me into twrp.
I have tried the popular mega unbrick guide from Naman Bhalla twice but didn't help either.
Any ideas ?
Thanks in advance
Click to expand...
Click to collapse
Try to flash stock recovery if succeeded then wipe complete, after twrp with root and then install stock oos
Msmdownload is low level format tool, another method of flashing won't work if it isn't.
Since you said that msm reported succeed but after it you still got a hash fail, it's either you flash the wrong file or a you've got a bad emmc..
You can't easily brick a Oneplus device. At worst you've screwed up your options for self-contained flashing via twrp. The two most common issues restoring to stock via sdk tools on a PC are i) wrong drivers being used, make sure you've installed the oneplus drivers on your computer and the device is recognised properly; and ii) you don't have full admin rights - make sure you've run the CMD shell as administrator before you execute any of the sdk commands.
hello
1.do u unlocked your bootloader?
2.connect your phone to PC into bootloader, if you can... try these codes with fastboot
fastboot erase cache
then
fastboot flash recovery ***.img
then
fastboot boot ***.img
then you should see you recovery....
before flashing ROM go to mount and mount system,recovery and data
then flash ROM