Hi ! my Oneplus 5 has slightly taken rainwater in my pocket. The phone wouldn't start up again.
I changed the battery. The phone reboots, the screen displays "1+ Powered by Android", then the screen starts to display lineage Logo and turns black and a white LED lights up.
I can't access the recovery mode by pressing power button + volume down.
Would you have an idea that would allow me to fix it? (I wanted to unbrick the phone but I can't enter to recovery ...)
thank you for your help
Use an EDL flasher (commonly known as unbrick tool). You can find it here on XDA
Pierre02 said:
Use an EDL flasher (commonly known as unbrick tool). You can find it here on XDA
Click to expand...
Click to collapse
Thanks for your answer. I wanted to follow this guide (https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706) but MSM Download Tool can't see my OnePlus (I followed the instructions but my phone doesn't appear under COMs and Ports).
For your information, I can get into the fastboot. With linux, the phone is well recognized in fastboot (it is also recognized with the tool TOOL_ALL_IN_ONE_2.0.1.3).
Code:
I tried this :
Sending 'recovery' (33689 KB) OKAY [ 1.320s]
Writing 'recovery' OKAY [ 0.317s]
Finished. Total time: 1.721s
Sending 'boot.img' (33689 KB) OKAY [ 1.289s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: 00000050')
fastboot: error: Command failed
tifriis said:
Thanks for your answer. I wanted to follow this guide (https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706) but MSM Download Tool can't see my OnePlus (I followed the instructions but my phone doesn't appear under COMs and Ports).
For your information, I can get into the fastboot. With linux, the phone is well recognized in fastboot (it is also recognized with the tool TOOL_ALL_IN_ONE_2.0.1.3).
Click to expand...
Click to collapse
You have to install drivers in special mode aka non signed driver install allowed mode in windows 10.
It's num 7 in the list of advance system startup.
For some reason i didn't had to do anything as my laptop already had everything somehow, i just open tool and flashed to 7.1 to test my phone. Now back to 10.
Only think I did before was installed htc 10 drivers to unlock and have custom rom on it.
atifsh said:
You have to install drivers in special mode aka non signed driver install allowed mode in windows 10.
Click to expand...
Click to collapse
Thanks but I did it (I followed this link : https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/ and I run "bcdedit /set testsigning on" then I restarted).
Maybe I have to uninstall some drivers before because my phone doesn't appear in the category " Ports (COM & LPT) ?
Here my screen after booting : https://cncloud.zaclys.com/index.php/s/bqMF3cDzMScjzgd
Thanks for your help
Hi ! I think I managed to install the driver (I had to remove old drivers).
Now MsmDownloadTool gives me this state :
Code:
Index : 1
Com : COM3
Status of Connection : Connected
SN :
Status of Communication : Param preprocessing
I'm stuck in "Param preprocessing". Phone have green LED. Any ideas ?
Thanks to help me to save my phone
For infomation, I succeed to use MSM Download Too. I was sotck in "Param preprocessing" because my battery was too low.
However, when my OP5 reboot, it displays the 1+ logo then get stuck with the red point and white circle, then reboot.
Any ideas ?
tifriis said:
For infomation, I succeed to use MSM Download Too. I was sotck in "Param preprocessing" because my battery was too low.
However, when my OP5 reboot, it displays the 1+ logo then get stuck with the red point and white circle, then reboot.
Any ideas ?
Click to expand...
Click to collapse
This is probably an hardware fault
Thanks for your support. Do you think it's the motherboard ?
Do you know if I can buy another one ?
Thanks for all, I apprieciate !
Related
Hi guys, I'm having a weird problem with my zenfone 5 (a501cg). I have searched a lot but still can't find out a proper solution So I post it here and try to provide as much information as possible so hopefully developers at xda can help me.
My phone is rooted and I'm currently using modded rom called "bazzrom pinaslang" in the forum. Recently I want to use another rom so I decide to use adb sideload again.
However, the problem occurs: using adb sideload only show "error" message". BUT Adb devices show the phone.
Then I decide to use adb reboot fastboot to enter fastboot. But the phone only show a usb icon, and using "fastboot devices" doesn't show the device anymore.
I try other way by enter recovery mode "adb reboot recovery". The phone show resting android with "no command" message. I also try hold power and press down volumn after that but nothing happend. I try anything with that "power" + "volumn" combo but nothing happend (or it just shutdowns the phone).
Also, using "power" + "up volumn" to enter Droid boot doesn't work.
Driver is install. In device manager it shows "Android composite adb interface".
The only good news is my phone still boots normally and I can use it. Please help me get back my fastboot so I can upgrade my phone to Lollipop and other modded ROM.
Thank you so much !!!!
techgeard said:
Hi guys, I'm having a weird problem with my zenfone 5 (a501cg). I have searched a lot but still can't find out a proper solution So I post it here and try to provide as much information as possible so hopefully developers at xda can help me.
My phone is rooted and I'm currently using modded rom called "bazzrom pinaslang" in the forum. Recently I want to use another rom so I decide to use adb sideload again.
However, the problem occurs: using adb sideload only show "error" message". BUT Adb devices show the phone.
Then I decide to use adb reboot fastboot to enter fastboot. But the phone only show a usb icon, and using "fastboot devices" doesn't show the device anymore.
I try other way by enter recovery mode "adb reboot recovery". The phone show resting android with "no command" message. I also try hold power and press down volumn after that but nothing happend. I try anything with that "power" + "volumn" combo but nothing happend (or it just shutdowns the phone).
Also, using "power" + "up volumn" to enter Droid boot doesn't work.
Driver is install. In device manager it shows "Android composite adb interface".
The only good news is my phone still boots normally and I can use it. Please help me get back my fastboot so I can upgrade my phone to Lollipop and other modded ROM.
Thank you so much !!!!
Click to expand...
Click to collapse
Hi,
Have you tried to boot into your system, enable USB debugging and run
Code:
adb reboot-bootloader
?
dgadelha said:
Hi,
Have you tried to boot into your system, enable USB debugging and run
Code:
adb reboot-bootloader
?
Click to expand...
Click to collapse
Hi dgadelha, thanks for your reply.
I have tried your suggestion before but phone only reboots and display usb icon. I also try power volumn combi like i did in my post but still nothing happened.
Usb debugging is enabled.
Techgeard.
techgeard said:
Hi dgadelha, thanks for your reply.
I have tried your suggestion before but phone only reboots and display usb icon. I also try power volumn combi like i did in my post but still nothing happened.
Usb debugging is enabled.
Techgeard.
Click to expand...
Click to collapse
In that case, follow the "Last resort" part of this guide http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=33800
It will reinstall your fastboot when the USB icon appears
dgadelha said:
In that case, follow the "Last resort" part of this guide
It will reinstall your fastboot when the USB icon appears
Click to expand...
Click to collapse
Hi dgadelha,
I have seen your link before my post, but I still wonder because the "last resort" in the link is used for "bricked" phone or the one that doesn't start up or stuck in somewhere. My phone can still boot and use quite normal : ( except one thing that my sd card always unmounted in this Pinaslang modded rom.
TG.
UPDATE I decide to try xFSTK but my computer still recognizes the device as "adb..." . if I turn off developer mode it becomes "portable device" in Window Device Manager.
The xFSTK can't recognize any Cloverfieldplus. (it shows "CLOVERFIELDPLUS...: 0")
TG.
techgeard said:
Hi dgadelha,
I have seen your link before my post, but I still wonder because the "last resort" in the link is used for "bricked" phone or the one that doesn't start up or stuck in somewhere. My phone can still boot and use quite normal : ( except one thing that my sd card always unmounted in this Pinaslang modded rom.
TG.
Click to expand...
Click to collapse
Hi,
Because the last resort will use a hardware function (xFSTK way) to update your dnx, ifwi and fastboot images. This way you can restore your fastboot.
Thanks.
techgeard said:
UPDATE I decide to try xFSTK but my computer still recognizes the device as "adb..." . if I turn off developer mode it becomes "portable device" in Window Device Manager.
The xFSTK can't recognize any Cloverfieldplus. (it shows "CLOVERFIELDPLUS...: 0")
TG.
Click to expand...
Click to collapse
You must instal the drivers it mentioned.
Also it will appear as Cloverview when the USB logo appears
Thanks!
dgadelha said:
Hi,
Because the last resort will use a hardware function (xFSTK way) to update your dnx, ifwi and fastboot images. This way you can restore your fastboot.
Thanks.
You must instal the drivers it mentioned.
Also it will appear as Cloverview when the USB logo appears
Thanks!
Click to expand...
Click to collapse
Hi dgadelha,
After a while I can start the xFSTK and begin download. However, after some attempts it always say error. The same messages show up as below:
Code:
start
sending dner
writeoutpipe dner
writeoutpipe 0
write----> dner
windriver Error: 0x20000015, Timeour expired
LogError
Error Code:1 - Connection Error
Failed to start Dldr state matchine, aborting...
void CloverviewPlusDownloader::do_abort()
Abott
FAIL
.....
techgeard said:
Hi dgadelha,
After a while I can start the xFSTK and begin download. However, after some attempts it always say error. The same messages show up as below:
Click to expand...
Click to collapse
Hi techgeard,
Looks like it's a driver timeout.
Which OS are you using? I see they used Windows 7 or before on the tests.
Also you should try getting xFSTK developers (on SourceForge) to help about this issue.
Thanks.
dgadelha said:
Hi techgeard,
Looks like it's a driver timeout.
Which OS are you using? I see they used Windows 7 or before on the tests.
Also you should try getting xFSTK developers (on SourceForge) to help about this issue.
Thanks.
Click to expand...
Click to collapse
Iam using Win7x64. The same with the guy posting in the link.
TG.
Hi Guys,
My OnePlus 2 has this issue where if i restart the phone it gets stuck on the Boot Screen which shows OnePlus Logo powered by Android.
I can boot my phone to Fastboot and i can only boot into the phone by using command "fastboot continue"
When i try to use command "fastboot oem unlock" the phone reboots and gets stuck on the OP logo
Fastboot oem device-info shows
... INFO Device tampered: true
INFO Device unlocked: false
INFO Device is_verified: false
INFO Charger screen enabled: false
INFO Display panel:
INFO console_locked: 1
INFO exec_console_unconsole: 0
OKAY
and if i try to install twrp recovery by using the command "fastboot flash recovery recovery.img" i get the following message
sending 'recovery' (25956 KB)... OKAY
writing 'recovery'... FAILED (remote: device is locked. Cannot flash images)
Please help
http://forum.xda-developers.com/oneplus-2/general/guide-oneplus-2-mega-unbrick-recover-t3397257
I have tried all those methods and none of them worked for me
pankaj2m said:
I have tried all those methods and none of them worked for me
Click to expand...
Click to collapse
Go to oneplus website & download official rom zip file. Push it into sdcard using fastboot. Go to stock recovery (vol_down + power) & flash the zip file.
I can't boot into to recovery hence can't flash.. I have the official rom zip from oneplus but can't flash it as I can't boot into recovery.. That's the problem
Can anyone please help me with this?? :'(
pankaj2m said:
Hi Guys,
My OnePlus 2 has this issue where if i restart the phone it gets stuck on the Boot Screen which shows OnePlus Logo powered by Android.
I can boot my phone to Fastboot and i can only boot into the phone by using command "fastboot continue"
When i try to use command "fastboot oem unlock" the phone reboots and gets stuck on the OP logo
Fastboot oem device-info shows
... INFO Device tampered: true
INFO Device unlocked: false
INFO Device is_verified: false
INFO Charger screen enabled: false
INFO Display panel:
INFO console_locked: 1
INFO exec_console_unconsole: 0
OKAY
and if i try to install twrp recovery by using the command "fastboot flash recovery recovery.img" i get the following message
sending 'recovery' (25956 KB)... OKAY
writing 'recovery'... FAILED (remote: device is locked. Cannot flash images)
Please help
Click to expand...
Click to collapse
Try the first method in this page https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Its worked in my mobile, when i lost everything (even fastboot also gone). Its surely work. It will flash Oneplus 2 official recovery. You should ensure that your device is detected in your computer and Its shows as Qualcomm 9008
eldos777 said:
Try the first method in this page https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Its worked in my mobile, when i lost everything (even fastboot also gone). Its surely work. It will flash Oneplus 2 official recovery. You should ensure that your device is detected in your computer and Its shows as Qualcomm 9008
Click to expand...
Click to collapse
I followed the all the 3 methods from the post you mentioned.
When i run MSM8994DownloadTool and START, it just stays there. I waited for 1hr for something to happen but nothing.
It Doesnot work for me.
For now, i use Fastboot Continue command in fastboot in case my devices shuts down
pankaj2m said:
I followed the all the 3 methods from the post you mentioned.
When i run MSM8994DownloadTool and START, it just stays there. I waited for 1hr for something to happen but nothing.
It Doesnot work for me.
For now, i use Fastboot Continue command in fastboot in case my devices shuts down
Click to expand...
Click to collapse
Thats means your device is not detected, Did you check device manager in your computer? Is is showing your mobile as Qualcomm 9008?? If it is not please follow the steps on the website, I already given. No need wait 1 hr. If your device is detected, then you can see a green line, and it will finish within 5mnts.
eldos777 said:
Thats means your device is not detected, Did you check device manager in your computer? Is is showing your mobile as Qualcomm 9008?? If it is not please follow the steps on the website, I already given. No need wait 1 hr. If your device is detected, then you can see a green line, and it will finish within 5mnts.
Click to expand...
Click to collapse
Hi Eldos,
In device manager it shows as RELINK HS-USBQDLoader 9008 (COM8)
i followed your instructions but it still does not work. When i run the MSM8994DownloadTool, it does not do anything.
Anything else i can try. I am stuck in this big problem. When my phone switches off, the only way i can boot is by going to FASTBOOT and running command "fastboot continue" only then my phone boots.
Please help.
Thanks,
Pankaj
pankaj2m said:
Hi Eldos,
In device manager it shows as RELINK HS-USBQDLoader 9008 (COM8)
i followed your instructions but it still does not work. When i run the MSM8994DownloadTool, it does not do anything.
Anything else i can try. I am stuck in this big problem. When my phone switches off, the only way i can boot is by going to FASTBOOT and running command "fastboot continue" only then my phone boots.
Please help.
Thanks,
Pankaj
Click to expand...
Click to collapse
Can you come in Team Viewer??
eldos777 said:
Can you come in Team Viewer??
Click to expand...
Click to collapse
Yes, sure.. how do i talk to you?
pankaj2m said:
Yes, sure.. how do i talk to you?
Click to expand...
Click to collapse
Give me your Teamviewer ID and Password
eldos777 said:
Give me your Teamviewer ID and Password
Click to expand...
Click to collapse
ID: 527533613
Password: 6953
pankaj2m said:
Can anyone please help me with this?? :'(
Click to expand...
Click to collapse
PM me
Problem Solved
Deep problem
I have gone through all the unbrick guides, even with a Oneplus technician but we weren't able to unbrick it. I'm guessing that after the oxygen 3.0.2 update, I wiped out the partition (not sure). The phone was unlocked with some TWRP version before that. I totally forgot to update it the right way. I can get use fastboot to go into the OS, but trying to flash doesn't work since it's locked. Trying to unlock it supposedly works but it remains locked. We tried the Qualcomm drivers, installed the certificates and the device is seen as Qualcomm 9800 yadda, yadda, yadda, but the MSM8994DownloadTool.exe doesn't detect the device, therefore it stays there doing nothing. Yes, we changed the developer options in the settings but nothing seems to work. The LTE doesn't work properly either...it shows an exclamation mark, so I have to switch to 3G. I'm in dire need of help, and if anyone can help me, you'd certainly qualify for a master tech support agent or something cause not even they could help me with this. Thanks in advance if any of you can help! I'm using a Windows 10 on a Mac, using Parallels VM...
CharlieVasquez said:
I have gone through all the unbrick guides, even with a Oneplus technician but we weren't able to unbrick it. I'm guessing that after the oxygen 3.0.2 update, I wiped out the partition (not sure). The phone was unlocked with some TWRP version before that. I totally forgot to update it the right way. I can get use fastboot to go into the OS, but trying to flash doesn't work since it's locked. Trying to unlock it supposedly works but it remains locked. We tried the Qualcomm drivers, installed the certificates and the device is seen as Qualcomm 9800 yadda, yadda, yadda, but the MSM8994DownloadTool.exe doesn't detect the device, therefore it stays there doing nothing. Yes, we changed the developer options in the settings but nothing seems to work. The LTE doesn't work properly either...it shows an exclamation mark, so I have to switch to 3G. I'm in dire need of help, and if anyone can help me, you'd certainly qualify for a master tech support agent or something cause not even they could help me with this. Thanks in advance if any of you can help! I'm using a Windows 10 on a Mac, using Parallels VM...
Click to expand...
Click to collapse
I finally got the MSM tool to detect the phone. While still in Qualcomm mode, I disconnected it and connected it to the to Mac usb ports and kept clicking on the tool to start. The green lights finally showed and I'm waiting to see what happens. I will keep you updated.
CharlieVasquez said:
I finally got the MSM tool to detect the phone. While still in Qualcomm mode, I disconnected it and connected it to the to Mac usb ports and kept clicking on the tool to start. The green lights finally showed and I'm waiting to see what happens. I will keep you updated.
Click to expand...
Click to collapse
K, I finally booted normally into the OS, went back and rooted the phone. Now we're good to go again. Not even the tech support agents were able to help me with this one.
It's been years for you to hear this problem (hard brick)
I have a hard bricked yureka .I have gone through the thread which have posted in in xda and yu forums
https://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
http://forums.yuplaygod.com/threads/project-reviving-hard-bricked-yu-qloader-9008-mode.10236/
my problem is different form the cases that I read in these threads
In my case the mobile
* is not deducting in Windows*
*it goes to fastboot mode*
*it gets rebooting when connected to windows or charger*
*stable when connected to Windows in fastboot mode*
*during normal start up it goes to fastboot mode and starts rebooting *
*when connected to Windows in fastboot mode the device manager shows it as unknown device under USB*
anyone plz guide me to understand brick my yu....
plz help me .....I'm ineeded of help
I have attached the picture and videos for ur consideration
the link of the Google drive
https://drive.google.com/folderview?id=0B3JWgilAzvw0TjZRb0ZyZDB1Qkk
Install drivers
solution for unknown device
Install adb drivers for fastboot mode and try flashing with signed fastboot flash files
Santhosh Rasa said:
It's been years for you to hear this problem (hard brick)
I have a hard bricked yureka .I have gone through the thread which have posted in in xda and yu forums
https://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
http://forums.yuplaygod.com/threads/project-reviving-hard-bricked-yu-qloader-9008-mode.10236/
my problem is different form the cases that I read in these threads
In my case the mobile
* is not deducting in Windows*
*it goes to fastboot mode*
*it gets rebooting when connected to windows or charger*
*stable when connected to Windows in fastboot mode*
*during normal start up it goes to fastboot mode and starts rebooting *
*when connected to Windows in fastboot mode the device manager shows it as unknown device under USB*
anyone plz guide me to understand brick my yu....
plz help me .....I'm ineeded of help
I have attached the picture and videos for ur consideration
the link of the Google drive
https://drive.google.com/folderview?id=0B3JWgilAzvw0TjZRb0ZyZDB1Qkk
Click to expand...
Click to collapse
Parkadhe Anna said:
solution for unknown device
Install adb drivers for fastboot mode and try flashing with signed fastboot flash files
Click to expand...
Click to collapse
thanks ... I will try and reply the results ...
Parkadhe Anna said:
solution for unknown device
Install adb drivers for fastboot mode and try flashing with signed fastboot flash files
Click to expand...
Click to collapse
thanks ... I will try and reply the results ...
Hy bro.
I m having same problems two days ago.
I found the solution which issuccessfully working for me. First : downloade the universal necked driver (google it mostly found on google nexus 5 thread).
Second : change ur phone's battery. Get a new battery.
Third : remove ur batterry. Reinsert ur battery. Press volume down & connect USB cable u see the fastboot mode release volume down. Then go to device manager in ur computer and search unknown driver. Right click on it and select update driver update it manually ( google it how to manually update driver) browse the necked driver & select winusnb.inf then select Asus fastboot interface ur device got connect. Now flash official stock cm11 firmware through ygdp tool. That's it. Sorry for my bad English.
I ran into a bit of an issue and am stuck with a bootlooping G6 US997.
What got me into this pickle:
I unlocked the bootloader
I flashed TWRP successfully, by:
Running fastboot flash recovery TWRP.img
Unplugging USB and holding Vol- and Power from fastboot, then lifting and re-pressing Power when the LG logo appeared
Hitting Yes, Yes
Being in TWRP and allowing modification of System
Formatting Data (Wipe > Format Data > Yes)
I installed the DM verity and encryption file so that it would boot
I wiped Cache/Dalvik
I rebooted into System
It booted successfully so I went back to TWRP and installed Lineage OS, Open Google Apps, and the Lineage SU addon
This booted successfully, so I went and with OEM unlock disabled booted into fastboot to see if I could get rid of the annoying orange screen at the start saying that the bootloader was unlocked
To do this, I ran fastboot oem lock, not seeing/ignoring the red text at top telling me to Please check "Enable OEM unlock" in Developer options.
I then rebooted with fastboot reboot and I encountered a red warning: "Your device has failed a routine safety check and will not boot." It is now in a bootloop at that screen, cycling between black, the LG logo, and the warning.
I managed to enter recovery mode (with the key-combo) and got the stock recovery "factory reset and wipe" option, which I had been previously getting when entering TWRP, so I selected "Yes, Yes" and then it went back into the bootloop, completely avoiding TWRP.
Where I currently am:
I can get into fastboot mode (Vol- with usb plugged in) and I can get into the factory reset mode which is the gateway into TWRP. I cannot get into TWRP, and I cannot flash anything, boot into any images, or unlock the bootloader ( Please check "Enable OEM unlock" in Developer options). If I could do that I think I can get it fixed.
My questions:
How can I do the OEM unlock without access to Developer Options? (I have the unlock file to flash, just need access)
Or How can I bypass the red warning page and boot into Lineage OS?
Any help would be appreciated, I really would like to get this working.
Have you tried to boot in download mode and flash the original firmware with LGUp+Uppercut?
Killua96 said:
Have you tried to boot in download mode and flash the original firmware with LGUp+Uppercut?
Click to expand...
Click to collapse
I've been trying to, I forgot to update the post though. I found the US99715a_05_0908 KDZ, and I installed Uppercut, LGUP, and the drivers from the Uppercut thread, but whatever I do it never recognizes the device. And when I go into download mode it quickly pops back out to the warning screen after about 10 seconds. After the warning it reboots in 10 seconds, I have a pretty small window.
I was thinking of trying LG Flash Tool 2.0.1.6, yet I haven't figured out how to use it yet. I may try more with Uppercut, maybe different drivers? If there were a way to keep it in download mode longer, that would really help. Thank you for replying, I've seen your name around the forums!
mwsundberg said:
I've been trying to, I forgot to update the post though. I found the US99715a_05_0908 KDZ, and I installed Uppercut, LGUP, and the drivers from the Uppercut thread, but whatever I do it never recognizes the device. And when I go into download mode it quickly pops back out to the warning screen after about 10 seconds. It looks like it might still be in download mode, but interrupted by the warning, the way the screens flash. After the warning it reboots in 10 seconds, I have a pretty small window.
I was thinking of trying LG Flash Tool 2.0.1.6, yet I haven't figured out how to use it yet. I may try more with Uppercut, maybe different drivers? Thank you for replying, I've seen your name around the forums!
Click to expand...
Click to collapse
I know this could be a stupid question, but have you tried to run the unlock command? If yes, what does it says?
Killua96 said:
I know this could be a stupid question, but have you tried to run the unlock command? If yes, what does it says?
Click to expand...
Click to collapse
fastboot flash unlock unlock.bin gives:
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.047s]
writing 'unlock'...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.063s
I had flashed it before but forgot to reenable the option in developer tools, I can't find a way to enable it from fastboot yet.
mwsundberg said:
fastboot flash unlock unlock.bin gives:
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.047s]
writing 'unlock'...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.063s
I had flashed it before but forgot to reenable the option in developer tools, I can't find a way to enable it from fastboot yet.
Click to expand...
Click to collapse
You can't, fastboot is a mode that allows many things but it's not a God-like mode where you can do everything.
By locking the bootloader while having unsigned partions flashed you have essentially hard bricked the device, and if the only way to flash stock signed partitions (lgup+Uppercut) doesn't work it means that you have to find a way to boot the phone in qhsusb9008 (usually by hardware) and try to flash a tot file, if there is one.
Sorry but is highly unlikely that you will able to recover your G6, hope to be wrong.
Killua96 said:
You have to find a way to boot the phone in qhsusb9008 (usually by hardware) and try to flash a tot file, if there is one.
Sorry but is highly unlikely that you will able to recover your G6, hope to be wrong.
Click to expand...
Click to collapse
How might I go about doing this, or is there a chance I can actually access LGUP and have just been messing up so far? If there were a video of what using LGUP and Uppercut properly looked like, that would be really helpful.
Also, is there any hope of LG or a phone store with LGUP being able to fix this (for less than the price of a new G6)?
mwsundberg said:
Also, is there any hope of LG or a phone store with LGUP being able to fix this (for less than the price of a new G6)?
Click to expand...
Click to collapse
It depends on how much it'll cost to you a new G6, they could ask you maybe 200-250 bucks.
mwsundberg said:
How might I go about doing this, or is there a chance I can actually access LGUP and have just been messing up so far? If there were a video of what using LGUP and Uppercut properly looked like, that would be really helpful.
Click to expand...
Click to collapse
Go in fastboot with the phone connected to the PC, keep pressed vol- and power until the phones turn off in that exact moment leave those two buttons and keep pressing only the vol+ one, this should bring you in download mode, if it stuck then you could use LGUP and Uppercut, otherwise there is nothing software related that you can do, imho obviously
Killua96 said:
Go in fastboot with the phone connected to the PC, keep pressed vol- and power until the phones turn off in that exact moment leave those two buttons and keep pressing only the vol+ one, this should bring you in download mode, if it stuck then you could use LGUP and Uppercut, otherwise there is nothing software related that you can do, imho obviously
Click to expand...
Click to collapse
Managed to get a messed up G6 from a friend working again. Thanks. XDA forever
Guys, need help !!!
I have tried to install SEA oreo version on Indian phone via LGUP... Flash was successful (100%) but it got stuck on LG Logo..
Procedure followed for H870DS (IND)
1. Downloaded SEA Oreo KDZ File (H870DS20a_00_OPEN_SG_DS_OP_0518.kdz)
2. Installed LGUP... Made new Common folder inside C/Prog file/LG/Model
3. Extracted DLL file from KDZ & renamed it LGUP_Common.dll and kept in Common folder
4. Entered in download mode
5. Opened LGUP.. selected KDZ and Upgrade..
6. Boom.. 100% completed.. it has shown that phone is rebooting..
7. But then it got stuck on LG Screen
I cant access recovery now
I can open Hard Reset option (Vol down+Power) only.. Made hard reset but no use
I cant enter in download mode
I dont know if it is charging or not
It is not even switching off by pressing power button for long time
Pl help me...
---------- Post added at 08:33 PM ---------- Previous post was at 08:30 PM ----------
it has anything to do with "Enable OEM unlock" in Developer options"
There is a way to enter download mode. Just hold down button and power button. Just when you see LG logo leave power button for a second. Push power button again and hold with down button. Now press yes twiche for the hard reset prompt. Now IMPORTANT, when screen goes black immediately press and hold up button. While holding up button plug usb cable into the PC. Now use Uppercut 1.0.0.0 and flash your kdz.
Same issue, Just that I was trying downgrade to Nougat. Oreo messed up my phone to the extent that, none of the sensors (including Fingerprint are not working). The load was a success, but after 1st restart it went into boot loop.
I only had USB Debug enabled in the DO before this issue, so it might work with the OEM unlock dissabled.
Software needed...
LG Bridge
Meathod...
Please charge the phone before this is done, at least 80%, will be better.
Connect the computer with LG G6 H870DS (Indian), might work for all models. "not tested"
If the USB debug is enabled, you will hear the USB disconnection and connection notification sound during bootloop
When you hear disconnection sound, press the "volume up key" until the Firmware Update mode appears
Once you are in Firmware Update mode, the USB connection will be stable (In bootloop, it keeps disconnecting)
Disconnect the USB cable
Start LG Bridge/Software Updates, connect when App asks to connect the phone
This will update you phone to the latest official software update..
This solution can work for all phones that have a hardware based menu to get into Firmware Update mode, definitely works on all LG phones to get out of bootloop. I have tested on LG G2, G4 and G6 Indian devices.
And a suggestion to all mates is, to enable USB debugging and the OEM unlock as soon as you get hands on your new devices. Always saves the hassle of running around the LG service center, its a big issue in India at-least. I love LG for its hardware quality but sadly LG smartphones have a bad history of software issues
hi yesterday i was far from home with 5% battery and i take some calls some photos and battery 0%
when i got home i plugged in and battery is too laow message screen appear and after the message:
The boot loader is unlocked and software integrity cannot be guaranteed. Any data stored on the device may be available to attackers. Do not store any sensitive data on the device.
Visit this link on another device to learn more:
g.co/ABH
can.t be power off when this message appear, i need to let battery drain and power key do nothing
and msmdownloand show nothing
Oneplus 6T on latest beta
Windows 10 i don.t know if has all drivers needed for a unbricked process
amkulcsar said:
hi yesterday i was far from home with 5% battery and i take some calls some photos and battery 0%
when i got home i plugged in and battery is too laow message screen appear and after the message:
The boot loader is unlocked and software integrity cannot be guaranteed. Any data stored on the device may be available to attackers. Do not store any sensitive data on the device.
Visit this link on another device to learn more:
g.co/ABH
can.t be power off when this message appear, i need to let battery drain and power key do nothing
and msmdownloand show nothing
Oneplus 6T on latest beta
Windows 10 i don.t know if has all drivers needed for a unbricked process
Click to expand...
Click to collapse
I've had this before. If your phone has fully discharged and you plug in the charger the phone will boot up and stay on that message.
Just leave it to charge for five minutes, unplug the charger, then force reboot it by holding the power and volume down buttons together until it reboots. It should then boot normally and then you can plug in and continue charging.
ebproject said:
I've had this before. If your phone has fully discharged and you plug in the charger the phone will boot up and stay on that message.
Just leave it to charge for five minutes, unplug the charger, then force reboot it by holding the power and volume down buttons together until it reboots. It should then boot normally and then you can plug in and continue charging.
Click to expand...
Click to collapse
SOLVED
wait till screen get of install drivers correctly then press volume keys (+ and -) and connect to pc, in device manager appear at ports as qualcom... and open msmdownload tool and press start
amkulcsar said:
SOLVED
wait till screen get of install drivers correctly then press volume keys (+ and -) and connect to pc, in device manager appear at ports as qualcom... and open msmdownload tool and press start
Click to expand...
Click to collapse
Yeah you didn't need to do that. Just disconnect the charger and hard reboot and you would have been fine like I said, but oh well.
amkulcsar said:
SOLVED
wait till screen get of install drivers correctly then press volume keys (+ and -) and connect to pc, in device manager appear at ports as qualcom... and open msmdownload tool and press start
Click to expand...
Click to collapse
Did you manage to get rid off the corrupted screen message doing this?
That's a standard message if you've unlocked your bootloader. It doesn't signify corruption or an actual issue. You won't get rid of it without locking your bootloader.
Hello everyone, I unlocked my bootloader, but unfortunately I made an error when unlocking it but flashing it. so that he writes me when starting qualcom crashdump mode. and I don't know how to get out of it. also where I get the original onplus6 t software. and i work with linux via terminal. who can help me with this? on the one hand, where can I get the original os9 andriod software? and the second question is how I get the whole thing back on my cell phone and that it comes out of this warning from the grass dump
Hello. Please look on XDA for MSM tool for your device (enchilada or fajita depending on 6 or 6t). It will reinstall OOS back on your phone and relock the bootloader. There are a few videos on YouTube that will guide you through the process. It's a (short) but stressful process, but it does really work.
carrabelloy said:
Hello everyone, I unlocked my bootloader, but unfortunately I made an error when unlocking it but flashing it. so that he writes me when starting qualcom crashdump mode. and I don't know how to get out of it. also where I get the original onplus6 t software. and i work with linux via terminal. who can help me with this? on the one hand, where can I get the original os9 andriod software? and the second question is how I get the whole thing back on my cell phone and that it comes out of this warning from the grass dump
Click to expand...
Click to collapse
If your original plan was to get custom firmware don't bother with msm tool and getting stock, it's unnecessary. Twrp can be booted from fastboot if your bootloader is unlocked and you can do anything you need to do from there.
carrabelloy said:
Hello everyone, I unlocked my bootloader, but unfortunately I made an error when unlocking it but flashing it. so that he writes me when starting qualcom crashdump mode. and I don't know how to get out of it. also where I get the original onplus6 t software. and i work with linux via terminal. who can help me with this? on the one hand, where can I get the original os9 andriod software? and the second question is how I get the whole thing back on my cell phone and that it comes out of this warning from the grass dump
Click to expand...
Click to collapse
I'm in the same boat. Have you found any solution yet? I also use linux.
Brettroth said:
If your original plan was to get custom firmware don't bother with msm tool and getting stock, it's unnecessary. Twrp can be booted from fastboot if your bootloader is unlocked and you can do anything you need to do from there.
Click to expand...
Click to collapse
This was my plan and I soon realized I was not ready. I have unlocked the phone and the bootloader but I'm stuck, not able to get twrp to flash. Here's my error message:
[email protected]:/home/chad/Downloads# fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (32628 KB)...
OKAY [ 0.973s]
writing 'recovery'...
FAILED (remote: No such file or directory)
finished. total time: 0.975s
[email protected]:/home/chad/Downloads#
ce_lloyd said:
This was my plan and I soon realized I was not ready. I have unlocked the phone and the bootloader but I'm stuck, not able to get twrp to flash. Here's my error message:
[email protected]:/home/chad/Downloads# fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (32628 KB)...
OKAY [ 0.973s]
writing 'recovery'...
FAILED (remote: No such file or directory)
finished. total time: 0.975s
[email protected]:/home/chad/Downloads#
Click to expand...
Click to collapse
Should be fastboot boot (path and filename of twrp.img) once it boots then you can flash twrp from within.
I have done that as well. It appears to work, but then I get QUALCOM CrashDump Mode Attempted to kill init! wxitcode=0x0000000b complete..and..exit
This is a T-Mobile branded phone, does that matter or change anything?
ce_lloyd said:
I have done that as well. It appears to work, but then I get QUALCOM CrashDump Mode Attempted to kill init! wxitcode=0x0000000b complete..and..exit
This is a T-Mobile branded phone, does that matter or change anything?
Click to expand...
Click to collapse
If you are on a11 you have to use the twrp.img that is posted on the cross development thread that works for opt6 and 6t. TWRP-3.6.0_11-OP6xT.img