Related
hello friends. i flashed tethered cyanogen mod 11 with bumped twrp recovery. dont know what happened. the installation was smooth. however after i wished to flash another custom rom i couldnt get into recovery. it gave me oot sector verify secure boot error. i tried download mode to flash stock with lg flash tool 2014. but it is also not detecting the device in any com41.. adv is detecte but nothing else. i researched and could make it that i accidentaly deleted my "laf" partition. so i need a link to any guide of how to restore that.
thanks all. but in need of help :crying::crying::crying::crying:
[email protected] said:
hello friends. i flashed tethered cyanogen mod 11 with bumped twrp recovery. dont know what happened. the installation was smooth. however after i wished to flash another custom rom i couldnt get into recovery. it gave me oot sector verify secure boot error. i tried download mode to flash stock with lg flash tool 2014. but it is also not detecting the device in any com41.. adv is detecte but nothing else. i researched and could make it that i accidentaly deleted my "laf" partition. so i need a link to any guide of how to restore that.
thanks all. but in need of help :crying::crying::crying::crying:
Click to expand...
Click to collapse
I think you flashed the boot.img instead of just booting it. have you tried doing the button thing to get into recovery
powerdown(pull out battery)
press and hold volume- and power untill you see the lg logo, then release and press and hold volume- and power, then chose yes and yes(with volume+, volume - and the power button) and you should be in twrp
Yeah tried the button combo. But instead of twrp or factory reset it gives boot certification error. Secure boot verify.
same thing what did you do to fix this??
[email protected] said:
Yeah tried the button combo. But instead of twrp or factory reset it gives boot certification error. Secure boot verify.
Click to expand...
Click to collapse
markslo112 said:
same thing what did you do to fix this??
Click to expand...
Click to collapse
try to get to download mode or fastboot
vol up while inserting usb cable and quote be next time I can't check every answer individually
suljo94 said:
try to get to download mode or fastboot
vol up while inserting usb cable and quote be next time I can't check every answer individually
Click to expand...
Click to collapse
can't do neither of that, if i try download mode the phone shows the same error and turns off. The PC recognizes the phone as "Qualcomm HS-USB QDLoader 9008(COM5). The screen on the phone however is turned off.
markslo112 said:
can't do neither of that, if i try download mode the phone shows the same error and turns off. The PC recognizes the phone as "Qualcomm HS-USB QDLoader 9008(COM5). The screen on the phone however is turned off.
Click to expand...
Click to collapse
you are screwed because you need to send it in(not really fixable)
suljo94 said:
try to get to download mode or fastboot
vol up while inserting usb cable and quote be next time I can't check every answer individually
Click to expand...
Click to collapse
suljo94 said:
you are screwed because you need to send it in(not really fixable)
Click to expand...
Click to collapse
Yeah I know...I will send it in tomorrow, but I doubt they will repair it for free because I messed with it and they will probably see I did something I shouldn't do to the phone. What should I say when I turn it in? Probably best if I say I tried to update it and something went wrong?
I am not new to rooting and unlocking Androids. My LG G3's UI would randomly freeze where I had to reboot the device to have it working again. Today I decided to flash the vanilla unicorn rom in recovery. I downloaded the rom and copied it over to the phone but the copy process kept getting stuck at some point, that I always had to cancel it.
So I decided to wipe cache and data to just reinstall the official d855 CM13 rom I had earlier on the device's storage, the wipe got stuck for at least 20 mins. I got impatient and removed the battery trying to reboot into recovery, but I was stunned and stuck on the LG Splash screen logo, I kept trying to reboot into recovery but couldn't get past the LG splash screen.
I then decided to try rebooting into fastboot, I was able to boot into fastboot the normal way without any issues but every attempt at getting TWRP just wasn't yielding anything useful. The closest I've gotten to seeing TWRP since then was with the fastboot command
Code:
fastboot boot recovery.img
which reboots showing the TWRP splash screen image without actually showing TWRP, but I've noticed I can access adb while the screen is stuck on the TWRP splash screen image.
I can't do any sideload of the zips on my computer because TWRP just stays there stuck on the splash screen so I can't enable sideloading. I have spent hours with this and it has taken too much of my time, attempts at
Code:
fastboot flash recovery recovery.img
just returns with an error in cmd with FAILED (remote: flash write failure).
I can't figure out what to do anymore, I'm left with a phone that can't boot into the rom and recovery, only the fastboot and download mode works. I just need the phone to let me boot into recovery so I can flash the files I need to and have my phone back to its earlier state.
I'll really appreciate everyone's support, thanks!
geek-x said:
I am not new to rooting and unlocking Androids. My LG G3's UI would randomly freeze where I had to reboot the device to have it working again. Today I decided to flash the vanilla unicorn rom in recovery. I downloaded the rom and copied it over to the phone but the copy process kept getting stuck at some point, that I always had to cancel it.
So I decided to wipe cache and data to just reinstall the official d855 CM13 rom I had earlier on the device's storage, the wipe got stuck for at least 20 mins. I got impatient and removed the battery trying to reboot into recovery, but I was stunned and stuck on the LG Splash screen logo, I kept trying to reboot into recovery but couldn't get past the LG splash screen.
I then decided to try rebooting into fastboot, I was able to boot into fastboot the normal way without any issues but every attempt at getting TWRP just wasn't yielding anything useful. The closest I've gotten to seeing TWRP since then was with the fastboot command which reboots showing the TWRP splash screen image without actually showing TWRP, but I've noticed I can access adb while the screen is stuck on the TWRP splash screen image.
I can't do any sideload of the zips on my computer because TWRP just stays there stuck on the splash screen so I can't enable sideloading. I have spent hours with this and it has taken too much of my time, attempts at just returns with an error in cmd with FAILED (remote: flash write failure).
I can't figure out what to do anymore, I'm left with a phone that can't boot into the rom and recovery, only the fastboot and download mode works. I just need the phone to let me boot into recovery so I can flash the files I need to and have my phone back to its earlier state.
I'll really appreciate everyone's support, thanks!
Click to expand...
Click to collapse
Does your computer recongnise your phone. If it does you (probably) can use LG up tool to flash kdz file
dusan17 said:
Does your computer recongnise your phone. If it does you (probably) can use LG up tool to flash kdz file
Click to expand...
Click to collapse
I have tried using the flash tool, but I can't get into Download mode to use the LG Flash tool to get back to stock. All I get is fastboot.
There was a tutorial about using two wires on the emmc, but I haven't been able to get the Qualcomm HD_USB 9008 to show up in Device manager.
Sent from my ONE A2005 using Tapatalk
geek-x said:
I have tried using the flash tool, but I can't get into Download mode to use the LG Flash tool to get back to stock. All I get is fastboot.
There was a tutorial about using two wires on the emmc, but I haven't been able to get the Qualcomm HD_USB 9008 to show up in Device manager.
Click to expand...
Click to collapse
I have the same case with my old LG L90. I spent a lot of time trying to get it back to life without success . I have read another post similar to this but the wire thing worked. I really don't know then.
dusan17 said:
I have the same case with my old LG L90. I spent a lot of time trying to get it back to life without success . I have read another post similar to this but the wire thing worked. I really don't know then.
Click to expand...
Click to collapse
What kind of wire did you use in getting it to work?
And how were you able to get windows to show the QLoader usb com port. ?
geek-x said:
What kind of wire did you use in getting it to work?
And how were you able to get windows to show the QLoader usb com port. ?
Click to expand...
Click to collapse
I didn't want to mess around with motherboard so i gave phone to my uncle because he is better than me in that stuff. But sadly we didn't bring it back to life.
dusan17 said:
I didn't want to mess around with motherboard so i gave phone to my uncle because he is better than me in that stuff. But sadly we didn't bring it back to life.
Click to expand...
Click to collapse
Damn.
geek-x said:
Damn.
Click to expand...
Click to collapse
I saw people unbrick devices that way we propably did somenthing wrong. For the wires i would use copper wires.
Do you have Qualcomm drivers installed in pc?
I have unbricked many mobile using this pin shortening trick.it's simple.just make sure you are shortening the right pins.
Jahanzaibawan said:
Do you have Qualcomm drivers installed in pc?
I have unbricked many mobile using this pin shortening trick.it's simple.just make sure you are shortening the right pins.
Click to expand...
Click to collapse
I can't get the Qualcomm drivers to show up in Device Manager, even after installing the Qualcomm drivers and I have enabled test mode and all that. My com ports don't show anything Qualcomm at all.
Jahanzaibawan said:
Do you have Qualcomm drivers installed in pc?
I have unbricked many mobile using this pin shortening trick.it's simple.just make sure you are shortening the right pins.
Click to expand...
Click to collapse
Does it also matter that I am using a USB 3.0 port? My laptop has no 2.0 ports.
This might be helpful http://forum.xda-developers.com/spr...fix-hard-brick-recovery-guide-t3132359/page59
dusan17 said:
This might be helpful http://forum.xda-developers.com/spr...fix-hard-brick-recovery-guide-t3132359/page59
Click to expand...
Click to collapse
Thanks for that post. I'll give it a try again tonight, I just need the Qualcomm 9008 drivers to come up.
Cause I noticed every time attach the wire to the board, windows recognizes the phone with an error "USB device not recognized" and in device manager a yellow warning mark next to one of the USB device icons.
Sent from my ONE A2005 using Tapatalk
geek-x said:
Thanks for that post. I'll give it a try again tonight, I just need the Qualcomm 9008 drivers to come up.
Cause I noticed every time attach the wire to the board, windows recognizes the phone with an error "USB device not recognized" and in device manager a yellow warning mark next to one of the USB device icons.
Click to expand...
Click to collapse
I that case right click chose update drivers and chose drivers manualy. Something like that should help you get device recognized
dusan17 said:
I that case right click chose update drivers and chose drivers manualy. Something like that should help you get device recognized
Click to expand...
Click to collapse
What directory will I choose to install the drivers from, the Qualcomm installation directory doesn't seem to contain the actual driver files.
geek-x said:
What directory will I choose to install the drivers from, the Qualcomm installation directory doesn't seem to contain the actual driver files.
Click to expand...
Click to collapse
Uf, i don't know it should be listed.
geek-x said:
Does it also matter that I am using a USB 3.0 port? My laptop has no 2.0 ports.
Click to expand...
Click to collapse
Yup.mostly 3.0 doesn't work.80% 3.0 cause the problem.
Jahanzaibawan said:
Yup.mostly 3.0 doesn't work.80% 3.0 cause the problem.
Click to expand...
Click to collapse
I'll try to get a USB 2.0 laptop to try this on. I just hope it works this time.
i installed cm14.1 today from the cyanogenmod website i had everything running fine until i reboot into recovery. i got a black screen and it didnt bot into recovery at all so i held my power button and volume down and nothing happens. i cant even boot up into fast boot or anything. nothing is turning my phone on. when i connect it to my pc nothing happens. is there anything i can do?
There's a mega unbrick guide for the OnePlus 3, use that then install the correct firmware and install the custom TWRP and re flash the ROM
i tried that method but the device doesnt even show up on my pc
envious86 said:
i tried that method but the device doesnt even show up on my pc
Click to expand...
Click to collapse
Get this sorted yet? You'll need a modified TWRP recovery for the newest CM based builds. I went through the same thing yesterday or the day before. Try holding volume down and power for like 30 seconds until you feel it vibrate that it is rebooting. Then hold volume *UP* while it reboots or if you see the "your device is not safe..." flash screen hurry and press volume down and go into fastboot. From there you can fastboot flash a new recovery.
I had the same problem as well, in device manager go to ports (com & LPT) and it will show up there under qualcum device. Don't forget to go and turn off certificate verification
Thanks guys I'll try this after work. Hopefully it works. If not sure oneplus are hopefully releasing a new phone soon
No it didn't work. I have a feeling I deleted something I shouldn't have because I was clearing out my files before I restarted and that was that.
you gotta use special twrp recovery for cm14.1...
https://www.androidfilehost.com/?fid=385035244224394867
Just use the recovery rahditzz provided you with a link, if your phone is stuck on black screen with white led hold your power button until it turns off, then boot to fastboot and flash the recovery and you will boot...
rahditzz said:
you gotta use special twrp recovery for cm14.1...
https://www.androidfilehost.com/?fid=385035244224394867
Click to expand...
Click to collapse
thanks didnt work. when i fastboot flash recovery and boot again it just goes into a black screen again
Then use unbrick method 2..
rahditzz said:
Then use unbrick method 2..
Click to expand...
Click to collapse
neither method works. all i can do is get into fastboot mode thats it. it wont show up on my pc at all
Method 2 workshop 100%, unless its a hardware fault..
Are you pushing volume up while plugging in cable?
I am. To be honest its very complex too me. I'm new to android and all this is so hard. I follow steps but I'm not 100% sure what I doing. Also my computer isn't great. Do these methods work on vista? Is there a video tutorial or anything? Sorry for annoying you and you don't understand how thankful i am for your help.
I jeep getting the sahara communication failed error
envious86 said:
I am. To be honest its very complex too me. I'm new to android and all this is so hard. I follow steps but I'm not 100% sure what I doing. Also my computer isn't great. Do these methods work on vista? Is there a video tutorial or anything? Sorry for annoying you and you don't understand how thankful i am for your help.
Click to expand...
Click to collapse
Your running vista???? Good god update your OS!!
Maybe your fastboot drivers got updated? There were some reports around this. You could try reinstalling the drivers and following the unbrick guide without an internet connection.
Sent from my ONEPLUS A3003 using Tapatalk
Cool u can boot into Fastboot, what error do you get when you type Fastboot devices? Nothing shows up?
Hello community members,
TL;DR no adb, no fastboot, no flashmode, no QDloader (or similar) ... how to unbrick it?
I was trying to force Android to allow lower lcd backlight brightness levels by patching framework-res.apk and I had the edited zip file ready to flash. Then I realized that my Android 7 Ressurection remix ROM (thread) flashed Cyanogenmod recovery, which I don't like. So I decided to reflash TWRP 3.0.2 (link) ( edit: using "fastboot flash boot twrp.img", which was almost fatal mistake) and it has gone almost well. The phone started to boot into recovery mode everytime (and took a long time doing so). So I googled a bit and found this thread which lead me to this thread. I was looking forward to seeing my display brightness at lower than default values, so I probably skipped some security checks and texts with red color, so I flashed the zip with the boot.img replaced. After flashing I chose reboot and nothing happened since.
The problem is I flashed something that was not for my device (extracted boot.img to wrong mmcblk). The command that bricked my phone is (from META-INF/com/google/android/updater-script):
Code:
package_extract_file("boot.img", "/dev/block/mmcblk0p6");
After that it doesn't boot, doesn't light up LED (even when charging), doesn't get detected by PC in any state.
So I have no adb, no fastboot and no flashmode and not even a QDloader or similar mode.
Is there a way to unbrick it?
EDIT: How to unbrick it using JTAG interface? If I find somebody that has the required equipment, what data do I need to give them?
Hey there! Did you manage to solve the issue, because I just got into the same situation after the zip didn't save the corrected partitions but the initial ones... So i ended up without any signs of life in my phone
valkata752 said:
Hey there! Did you manage to solve the issue, because I just got into the same situation after the zip didn't save the corrected partitions but the initial ones... So i ended up without any signs of life in my phone
Click to expand...
Click to collapse
Nope, I found no solution ... even some kind of Qualcomm flashing mode via COM (serial port over USB) does not show up nowhere. I gave up and bought a used S5 mini, which is full of features I appreciate.
I'm gonna keep this Xperia M for some time if some solution comes up.
hi , can you boot into recovery ? ..if yes, i can maybe help
olibub said:
hi , can you boot into recovery ? ..if yes, i can maybe help
Click to expand...
Click to collapse
No, as I said, the phone does not react on anything. I would be able to put it back together if this was possible.
mik13ST said:
No, as I said, the phone does not react on anything. I would be able to put it back together if this was possible.
Click to expand...
Click to collapse
:/ this will be a problem... try look here http://rootmyandroid.org/how-to-unbrick-your-android-device-the-ultimate-guide.html/
and find this article "Unbrick any android device with Once Click Unbrick tool"
mik13ST said:
No, as I said, the phone does not react on anything. I would be able to put it back together if this was possible.
Click to expand...
Click to collapse
can you still access fastboot mode? anyway you need to know first what is exactly partition that you overwrite with boot.img :/
. That was really critical -_-
olibub said:
:/ this will be a problem... try look here http://rootmyandroid.org/how-to-unbrick-your-android-device-the-ultimate-guide.html/
and find this article "Unbrick any android device with Once Click Unbrick tool"
Click to expand...
Click to collapse
Nice looking tutorial, but I cannot find any download link for that One Click Unbrick Tool in that article. I doubt it would work, they are not explaining what it does.
Nicklas Van Dam said:
can you still access fastboot mode? anyway you need to know first what is exactly partition that you overwrite with boot.img :/
. That was really critical -_-
Click to expand...
Click to collapse
No, as I said. The partition that got overwritten was /dev/block/mmcblk0p6. It was overwritten by boot.img from LG OPTIMUS 3D that I link to in the main post.
here you can download unbrick tool https://forum.xda-developers.com/showthread.php?t=1153310
olibub said:
here you can download unbrick tool https://forum.xda-developers.com/showthread.php?t=1153310
Click to expand...
Click to collapse
I don't think this has any chance that it will work.
"This Software:
Will work on all Samsung devices which use Odin3"
Do you know how to use Flashtool?
If so, did you already attempt flashing a ftf via Flashmode (Hold VolDown)?
PhoenixTwoFive said:
Do you know how to use Flashtool?
If so, did you already attempt flashing a ftf via Flashmode (Hold VolDown)?
Click to expand...
Click to collapse
I know what Flashtool is. I know what ftf is. I used it once I think.
But the phone does not boot into flashmode as I mention in the main post.
im super worried right now, this is my only phone and really need it these days, thing is i tried to flash a kdz to my phone with lg up 1.14 and worked, everything was fine, but it had a may 2019 security patch and didnt want to update via OTA, so i downloaded a more recent kdz and did the same, but now with LG UP 1.15, thing is, this time, when it was supposed to reboot and show a circle that says "erasing" it stayed off.
now it doesnt react to anything, not even the volume down+power or the volume up and conecting to acces download mode it stays at a blank screen with no reaction, not even a vibration.
however, when changing ports, it stared installing a divice, however it said this:
qusb_bulk_cid:0402 _sn:c9aaeafb is set up and ready to go
i sherched and this appears to be a qualcomm brick, please tell me i can recover my phone.
someone help me quick please
ok, i installed qualcomm drivers and now my phone is detected as hs usb qdloader 9008 (COM9), which indeed is a qualcomm brick.
does anyone knows what to do next?
I think you can flash with qfil but I don't have much knowledge about that, sorry ... I hope someone who knows about it will help you soon
Ricky Almonte said:
I think you can flash with qfil but I don't have much knowledge about that, sorry ... I hope someone who knows about it will help you soon
Click to expand...
Click to collapse
yeah, i read that, got the files, even the firehose and did it. but now i have a new problem, im still brick but now my phone cant be recognice, every time it is conected the only thing it happens is the led blinking red, which i read it is the worst possible outcome. (im sure i did the qfile process correctly, i did it very carfully and only after reading like 6 posts so that i could be well informed.... it got quite techy)
why!! :crying::crying:
i read that mostly happens to the t mobile version of the phone, but mine is the cannadian one, i dont get it.
can someone now help me with this red blinking led?? i read a lot but the only thing i found is that ill need to open my phone and use the test points to access qualcomm mode, but it doesnt say more, i dont know where to begin:crying:
did u flash on lgup via cmd or via GUI? if gui, u picked refurbish or other command? Some guys erase their imei mac etc picking other commands in the gui (dl partition is safe), making their smartphone become a thing made of hardware with no identity.
manuhuelva said:
did u flash on lgup via cmd or via GUI? if gui, u picked refurbish or other command? Some guys erase their imei mac etc picking other commands in the gui (dl partition is safe), making their smartphone become a thing made of hardware with no identity.
Click to expand...
Click to collapse
mmmm... i used the lgup version 1.13 via GUI, for my first time, i used refurbish since it was the default, it worked fine.
when i downloaded a more recent kdf for my second install, i also downloaded the version 1.14 for the lgup, i tried to acces the gui like normal but didnt work since it asked me to log in, so i read i could also do it via CMD, so i used CMD for my second test.
Thats when my phone began intalling like normal, but in the reboot section of the install, it turned off to never turn on again
ThePanhead said:
mmmm... i used the lgup version 1.13 via GUI, for my first time, i used refurbish since it was the default, it worked fine.
when i downloaded a more recent kdf for my second install, i also downloaded the version 1.14 for the lgup, i tried to acces the gui like normal but didnt work since it asked me to log in, so i read i could also do it via CMD, so i used CMD for my second test.
Thats when my phone began intalling like normal, but in the reboot section of the install, it turned off to never turn on again
Click to expand...
Click to collapse
I hope u could resolve it. try other lgup versions. If u cant go download mode, hold vol- and power with plugged usb to pc and when the phone restarts u have to release too fast the buttons and hold vol+ until u get into download mode.
Hi, so my phone boots to lg g7 thinq splash screen and gets stuck there. I have a PM flashed to 11g. I can access download mode, edl, fastboot, and I can access all partitions in qfil. Can anyone send a copy of their mpt partition? I think I overwrote it on accident. Thanks.
Try this method...
https://forum.xda-developers.com/lg...to-recover-hardbrick-9008-mode-boxes-t4052841
Reyklein said:
Try this method...
https://forum.xda-developers.com/lg...to-recover-hardbrick-9008-mode-boxes-t4052841
Click to expand...
Click to collapse
I'm currently trying that out now. Can you backup your mpt partition in qfil so I can download it? Thank you.
I was actually successful in using qfil to flash but sadly it still isn't enough to fix my problem. It still stays stuck at "lg g7 thinq" splash screen. Also lost access to fastboot.
damprobot said:
I was actually successful in using qfil to flash but sadly it still isn't enough to fix my problem. It still stays stuck at "lg g7 thinq" splash screen. Also lost access to fastboot.
Click to expand...
Click to collapse
In edl mode load xml file 0 and again edl mode load xml1 ......... Repaet till xml6
Baijoosharma said:
In edl mode load xml file 0 and again edl mode load xml1 ......... Repaet till xml6
Click to expand...
Click to collapse
I flashed them one by one this time and still it won't boot completely. If anyone can share their mpt partition from qfil it'd be much appreciated.
damprobot said:
I flashed them one by one this time and still it won't boot completely. If anyone can share their mpt partition from qfil it'd be much appreciated.
Click to expand...
Click to collapse
This is the only option i did it in 4 days repeat and repeat thats it r u usung same ezdextrat file attached in thread ir your own extracted files ? Doenload from here and repeat 0123456 untill monile turn on you will loss imei
I know I'm doing it correctly, as you can see in my screenshot above. The extracted files are not what I need. I need mpt partition, which isn't part of the kdz.
In other words, I messed up a partition the kdz won't fix.
I fixed my issue. Turns out my mpt partition WAS the issue. What I did was wipe mpt in Qfil then reflash everything and it finally booted.
Just an FYI for anyone flashing blindly like me: double check which partition is highlighted in blue before flashing! Lol
Congrats your imei is still there ?
Baijoosharma said:
Congrats your imei is still there ?
Click to expand...
Click to collapse
Yes, everything working well. I'm currently on evolution x now
damprobot said:
Yes, everything working well. I'm currently on evolution x now
Click to expand...
Click to collapse
same issues i faced but lost imei strange
damprobot said:
I fixed my issue. Turns out my mpt partition WAS the issue. What I did was wipe mpt in Qfil then reflash everything and it finally booted.
Just an FYI for anyone flashing blindly like me: double check which partition is highlighted in blue before flashing! Lol
Click to expand...
Click to collapse
would you pls tell that what is mpt partotions. and what if the partitions is blue then whats the case? and what to look at. and 2nd i also unbrick ny phone using 9008 method eith 11g dzextracted. i was then flashed my own stock of eaw but my dual sim phone was now showing single sim. after that i flash many kdzs but no success.