Related
Hey, guys Im trying to flash my my lg g2 sprint edition back to stock using the lg flash tool. I downloaded the sprint tot and dll and when it says flashing on the lg flash tools it brings up and error that says wrong dll or model, I looked at the model it detected and it says my sprint g2 was a d801.
How do i fix this?
Thanks.
Still need your help guys
Theboss1242 said:
Still need your help guys
Click to expand...
Click to collapse
same issue,
try to replace the dll file with this one:
http://forum.xda-developers.com/attachment.php?attachmentid=2553245&d=1391282521
good luck
Theboss1242 said:
Still need your help guys
Click to expand...
Click to collapse
What rom is your phone currently using right now?
Thank guys I got it to work using the dll. !!
Theboss1242 said:
Thank guys I got it to work using the dll. !!
Click to expand...
Click to collapse
do you think this dll would work for my at&t lg g2 that thinks its the d802 version??
afrojoc said:
do you think this dll would work for my at&t lg g2 that thinks its the d802 version??
Click to expand...
Click to collapse
i don't know, it worked for my ls980 with a d802 firmware
Alexandercat said:
i don't know, it worked for my ls980 with a d802 firmware
Click to expand...
Click to collapse
where did you get the dll?
OMG ITS WORKING!!!!!!
afrojoc said:
where did you get the dll?
OMG ITS WORKING!!!!!!
Click to expand...
Click to collapse
nice to know :good:
Please Help
I have the same issue. Flashtool thinks my phone is a D801. It boots normally for a few seconds and keep rebooting. Im Reading, dowloading and trying every method around since yesterday afternoon with no luck. I did replace the .dll you provided but i have a different error now, something like mismatch different files and it shows both files names. I just got this phone from a friend. it shows d801 tmo versión in flashtool so i think he was messing around with any tmo based rom (if exits). So flashtool does not let me flash the phone because of this(Think this is a 801 tmo)
I also tried lg suppor tool but it never download the firmware. It get stuck on downloading firmware or checking phone settings (something like that), I found my cell model on the back on the phone so im pretty sure is a SL980. So what comboof files i can use? Do i still can use the.dll provided? Do i have to rename something?(btw...i did and didnt work).
Any other tip? Did i miss something? I have no phone now so im kinda desperate. Thanks in advance for any help.
Sorry for any mistake, english is not my first language.
I will try ti explain you later what i did to fix this issue
Cant you go in fastboot mode?
Sent from my LG-D801 using xda app-developers app
Alexandercat said:
I will try ti explain you later what i did to fix this issue
Cant you go in fastboot mode?
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
No...how can i do it? i read pressing vol+ while connecting usb but i get to dowload. I know in fastboot i can flas img to phone but i cant get in to it
ToledoG28 said:
No...how can i do it? i read pressing vol+ while connecting usb but i get to dowload. I know in fastboot i can flas img to phone but i cant get in to it
Click to expand...
Click to collapse
ok this is what i did to unbrick my phone in your same conditions, in some steps maybe i made some mistakes but i went to the fastboot mode and there i replaced all kernel files of ls980 to fix the issue:
first you have to proceed to back to stock your phone with the T-Mobile USA D80110C_1.kdz :
http://forum.xda-developers.com/showthread.php?t=2432476
now your phone is a full d801, it will boot the system but will be unstable, you must be fast to go to make the developer options and debug your phone, make it on plane and and charging mode, maybe you will be able to do it after some reboots, u must insist.
download the ioroot11 program to root your device, remember always that is unstable, your device will be recognized for not long time, so you have to open the ioroot program often until it recognize your device and root it with the program.
after this step, if your phone is rooted but is still too much ustable to use the adb command (i tried to sideload and push the recovery but it always made me a sideload error), download this program:
http://forum.xda-developers.com/showthread.php?t=2633941
is a simple tool to flash the recovery, it worked in my case, you have to install the recovery of the d801, in my case the philz recovery worked, if everything will be right, you will flash the recovery.
When i was inside the recovery i tried to flash the justin sprint t mobile through the sideload command but it didn't work, same with cm11, i flashed the ls980twrp.zip and when i tried to go to recovery again i was in fastboot.
from fastboot i used the command fastboot erase to erase the partitions: aboot, boot, dbi,laf,misc, persist, recovery, rpm, sbl1, tz.
to erase you must use the command fastboot erase aboot aboot for example, to erase the boot you must repeat boot(fastboot erase boot boot) and so on.
after erased all files i flashed the partitions of ls980:
http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zv7_partitions
cmd fastboot flash aboot aboot and so on, (i didn't flashed the primaryGPT).
when i flashed all these files i pushed power volume+ and i was in upgrade firmware, so i went back to stock with zv7tot and dll..
it wasn't simple to find a way to back to stock, i guess to made some mistakes but i fixed my issue in this way, i am responsible of what i do with my phone, i cannot guarantee the same results with the others
Alexandercat said:
ok this is what i did to unbrick my phone in your same conditions, in some steps maybe i made some mistakes but i went to the fastboot mode and there i replaced all kernel files of ls980 to fix the issue:
first you have to proceed to back to stock your phone with the T-Mobile USA D80110C_1.kdz :
http://forum.xda-developers.com/showthread.php?t=2432476
now your phone is a full d801, it will boot the system but will be unstable, you must be fast to go to make the developer options and debug your phone, make it on plane and and charging mode, maybe you will be able to do it after some reboots, u must insist.
download the ioroot11 program to root your device, remember always that is unstable, your device will be recognized for not long time, so you have to open the ioroot program often until it recognize your device and root it with the program.
after this step, if your phone is rooted but is still too much ustable to use the adb command (i tried to sideload and push the recovery but it always made me a sideload error), download this program:
http://forum.xda-developers.com/showthread.php?t=2633941
is a simple tool to flash the recovery, it worked in my case, you have to install the recovery of the d801, in my case the philz recovery worked, if everything will be right, you will flash the recovery.
When i was inside the recovery i tried to flash the justin sprint t mobile through the sideload command but it didn't work, same with cm11, i flashed the ls980twrp.zip and when i tried to go to recovery again i was in fastboot.
from fastboot i used the command fastboot erase to erase the partitions: aboot, boot, dbi,laf,misc, persist, recovery, rpm, sbl1, tz.
to erase you must use the command fastboot erase aboot aboot for example, to erase the boot you must repeat boot(fastboot erase boot boot) and so on.
after erased all files i flashed the partitions of ls980:
http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zv7_partitions
cmd fastboot flash aboot aboot and so on, (i didn't flashed the primaryGPT).
when i flashed all these files i pushed power volume+ and i was in upgrade firmware, so i went back to stock with zv7tot and dll..
it wasn't simple to find a way to back to stock, i guess to made some mistakes but i fixed my issue in this way, i am responsible of what i do with my phone, i cannot guarantee the same results with the others
Click to expand...
Click to collapse
ok...i will try that...i was able to flash twrp and get to recovery
ToledoG28 said:
ok...i will try that...i was able to flash twrp and get to recovery
Click to expand...
Click to collapse
if you can go to twrp you can flash with adb, i wasn't able to go in recovery, just download with the d801 firmware, that explains why it was complicated
Thanks for all your help. I was able to erase everything via fastboot and my phone fell down and power off before flashing img and now is dead. I have a big blue pitbull inside the house who makes the disaster.,.lol. i just got one white from a friend for $160. Im sure this thread can help any people with a brick device. Thanks again.
Sent from my unknown using xda premium
Pity, dogs like smartphones :/
Inviato dal mio LG-LS980 utilizzando Tapatalk
but i get no adb?
what ToledoG28 said is exactly what I have been attempting to do to correct this issue but I am facing an additional issue. I had got to the point where I am running the d800 version on my ls980 and it is unstable as you said. I believed I had found a way out but when I connect to the computer no matter what I do I get no adb for no reason as far as I can tell.
makes no sense at all to me as I had adb before all this perfectly fine.
try this
boxorandyos said:
what ToledoG28 said is exactly what I have been attempting to do to correct this issue but I am facing an additional issue. I had got to the point where I am running the d800 version on my ls980 and it is unstable as you said. I believed I had found a way out but when I connect to the computer no matter what I do I get no adb for no reason as far as I can tell.
makes no sense at all to me as I had adb before all this perfectly fine.
Click to expand...
Click to collapse
you gotta go do device drivers and your device will show up as some unknown device so you install the adb devices for your phone and then you should get adb to show.
Alexandercat said:
same issue,
try to replace the dll file with this one:
http://forum.xda-developers.com/attachment.php?attachmentid=2553245&d=1391282521
good luck
Click to expand...
Click to collapse
The magic dll, worked for me d802 A very big thanks to you man. I spend hours trying to fix it all it needed was a magic dll from a MagicMan. Thank you again million times.
I went to flash the latest version of Mahdi ROM, which I have done many times without a problem. This time, however, the patch.zip that I downloaded failed to install and then I was stuck in a fastboot. I found another post on here where someone said that putting certain commands into the prompt would fix it so I made sure that I had all the right files for my LS980 and went ahead and did it.
These are the commands I followed that got me to this point:
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-boot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
But now I can't seem to bring up anything and I've tried powering it on, going into recovery, and going into download mode but none of those things seem to be working. When I plug it into my computer, it makes the little sound and it's recognized but only as an E: drive with one lonely folder in it titled "image" and then I get a bunch of pop ups saying that "You need to format the disk in drive S: (and other various letters) before you can use it".
I really hope someone here can help me and that I haven't completely ruined my phone because there's no way that I have the money or means to replace it.
cookierobots said:
I went to flash the latest version of Mahdi ROM, which I have done many times without a problem. This time, however, the patch.zip that I downloaded failed to install and then I was stuck in a fastboot. I found another post on here where someone said that putting certain commands into the prompt would fix it so I made sure that I had all the right files for my LS980 and went ahead and did it.
These are the commands I followed that got me to this point:
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-boot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
But now I can't seem to bring up anything and I've tried powering it on, going into recovery, and going into download mode but none of those things seem to be working. When I plug it into my computer, it makes the little sound and it's recognized but only as an E: drive with one lonely folder in it titled "image" and then I get a bunch of pop ups saying that "You need to format the disk in drive S: (and other various letters) before you can use it".
I really hope someone here can help me and that I haven't completely ruined my phone because there's no way that I have the money or means to replace it.
Click to expand...
Click to collapse
I have the same problem and haven't found an answer yet. Please let me know if you do.
arethosereal said:
I have the same problem and haven't found an answer yet. Please let me know if you do.
Click to expand...
Click to collapse
I wasn't able to fix it at all and ended up going to Sprint and getting a new phone. I basically just said it stopped charging correctly and then I woke up one morning and it wouldn't turn on. They took it as a hardware issue and I got it replaced. Thank goodness for Total Equipment Protection. I'm not sure who your carrier is, but Sprint gives two free replacements (as long as it is hardware or something similar) and then it's $25 for every replacement after that. Needless to say, I am going full stock and sticking with Nova Launcher this time around.
arethosereal said:
I have the same problem and haven't found an answer yet. Please let me know if you do.
Click to expand...
Click to collapse
You could have tried to flash stock firmware. Exactly same thing happened to me. Flashing stock firmware solved the problem.
http://forum.xda-developers.com/showthread.php?p=45293512
Te$la said:
You could have tried to flash stock firmware. Exactly same thing happened to me. Flashing stock firmware solved the problem.
http://forum.xda-developers.com/showthread.php?p=45293512
Click to expand...
Click to collapse
That's what I did. Thanks.
arethosereal said:
That's what I did. Thanks.
Click to expand...
Click to collapse
What problem did u face in flashing stock firmware?
Is your phone working now? How did u solve it?
Te$la said:
What problem did u face in flashing stock firmware?
Is your phone working now? How did u solve it?
Click to expand...
Click to collapse
I should have said I fixed the problem by flashing stock. All is ok now.
I just rooted again and am trying to figure out how to avoid the same problem, which happened when I tried to install TWRP via AutoRec. The thing is, I have the F320K version and it doesn't seem to like the custom TWRP in AutoRec. But I don't see an alternative, yet.
I'm missing something.
arethosereal said:
I should have said I fixed the problem by flashing stock. All is ok now.
I just rooted again and am trying to figure out how to avoid the same problem, which happened when I tried to install TWRP via AutoRec. The thing is, I have the F320K version and it doesn't seem to like the custom TWRP in AutoRec. But I don't see an alternative, yet.
I'm missing something.
Click to expand...
Click to collapse
Install the Autorec specific to your model. There should not be any problem cause most of us used autorec to install twrp.
Te$la said:
Install the Autorec specific to your model. There should not be any problem cause most of us used autorec to install twrp.
Click to expand...
Click to collapse
I did that, but got the white line issue and didn't see the fix from Cloudyfa until today. I guess I'll try it again, knowing I'll get the white lines. Kind of freaked me out a little.
I'll let you know after the process, tomorrow. Thanks.
So I've got my (recently purchased T_T) Australian G2 (D802T) in a bit of a pickle. Here's the story of my rapid descent into idiocy: Rooted with ioroot (went fine), installed TWRP via autorec (whoops!). From here I installed several roms but none would boot past optimizing apps - after some further reading this is apparently a known issue with the D802T.
From here I followed the instructions at http://forum.xda-developers.com/showthread.php?t=2432476 and successfully reset back to stock firmware using a D802T kdz I found online. On first boot the phone asked for a decryption pin, which I fixed by booting to the stock recovery and letting it do its thing. However, it seems that the image was for the 16GB version - I was left with only 10GB accessible space.
This is where I got double stupid - I followed about half of http://www.droidviews.com/your-32gb-lg-g2-shows-only-16gb-storage-space-heres-the-fix/ to fix the issue, but rather than copying over the blank images and re-imaging the firmware again, I tried to get clever by growing the userdata partition manually. Unfortunately it seems that I screwed up, since on next boot I once again had the decryption lock, and now neither the factory reset nor re-flashing the firmware will fix it. The last thing I tried tonight was installing the LG Mobile Support Tool and letting it automatically download and install the firmware, but it seems to be in the exact same condition. Apparently the kdz re-imaging (even CSE Flash) doesn't actually reformat anything... :/
Any ideas? I have access to:
download mode
stock recovery/factory reset screen
bootable stock ROM that locks me out due to thinking it's encrypted, when in fact it's just an incorrect partition table.
Is there any way to get adb access back? Or perhaps to get the phone in to some kind of usb mass storage mode as described in http://forum.xda-developers.com/showthread.php?t=2582142 ? As it is it's only recognized by linux as a serial device - if I could get rw access to the raw storage I think I could fix it up pretty easily.
Does anyone know of any way to get adb or fastboot working in this situation? All I can think of is to flash the kdz again and pull the usb out in attempt to break it even further, as I've read that the phone goes to fastboot or qhsusb_bulk when a boot partition is corrupted; but this seems very foolhardy.
How exactly do kdz flashes work? Is there any way to feed it a kdz file that will reformat the userdata partition correctly, or is that just never going to happen?
amdpox said:
Does anyone know of any way to get adb or fastboot working in this situation? All I can think of is to flash the kdz again and pull the usb out in attempt to break it even further, as I've read that the phone goes to fastboot or qhsusb_bulk when a boot partition is corrupted; but this seems very foolhardy.
How exactly do kdz flashes work? Is there any way to feed it a kdz file that will reformat the userdata partition correctly, or is that just never going to happen?
Click to expand...
Click to collapse
maybe you should first try downloading your kdz from here and trying that.
You don't want to be in qhsusb bulkmode, but if you want fastboot access you could run this command in your terminal
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
to nuke your laf partition and get fastboot through your button combination. But then you might be asking for a hardbrick.
Art Vanderlay said:
maybe you should first try downloading your kdz from here and trying that.
Click to expand...
Click to collapse
Doubt it'll be much different but I'll give it a shot, thanks.
You don't want to be in qhsusb bulkmode, but if you want fastboot access you could run this command in your terminal
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
to nuke your laf partition and get fastboot through your button combination. But then you might be asking for a hardbrick.
Click to expand...
Click to collapse
I don't have adb access or a custom recovery, so I can't run that command - in fact if I can get a shell open on the device at all I think I'd be most of the way to a fix. Why don't I want to be in bulkmode? It seems to me like exactly what I need - raw access to the internal memory as a block device.
amdpox said:
Doubt it'll be much different but I'll give it a shot, thanks.
I don't have adb access or a custom recovery, so I can't run that command - in fact if I can get a shell open on the device at all I think I'd be most of the way to a fix. Why don't I want to be in bulkmode? It seems to me like exactly what I need - raw access to the internal memory as a block device.
Click to expand...
Click to collapse
It's a last resort and it leaves very little margin for error. If you try to force your way into it by yanking out your cable or something you might find yourself hardbricked.
If you flashed a 20D kdz the method for entering hard reset is vol - power then vol up + vol - on lg logo maybe thats why you can't get in now.
Art Vanderlay said:
It's a last resort and it leaves very little margin for error. If you try to force your way into it by yanking out your cable or something you might find yourself hardbricked.
If you flashed a 20D kdz the method for entering hard reset is vol - power then vol up + vol - on lg logo maybe thats why you can't get in now.
Click to expand...
Click to collapse
Fair enough. It feels like I'm at the point of last resort, though.
I tried that 20D kdz, seems to be in the same state. (I'm guessing that's exactly the image that the automated support tool downloaded and flashed.)
Is this fixed ?
bender_007 said:
Is this fixed ?
Click to expand...
Click to collapse
Sadly not. Totally stuck for ideas here... anyone know anything more sensible to try than the cable-pulling?
nexus 6p bootloader shown but cant flash eny thing bootloader locked no recovery to flash ota tray every thin eny eidea pleasssssssssssssssssssssssssss
amermsn said:
nexus 6p bootloader shown but cant flash eny thing bootloader locked no recovery to flash ota tray every thin eny eidea pleasssssssssssssssssssssssssss
Click to expand...
Click to collapse
Hello,
Please if English is not your mother language, use an online translator like Google translate. The end of your story doesn't make sense.
What happened?
When you are in bootloader, select recovery mode and press power button, what happen? Does it bootloop?
Good luck...
Did you try installing a factory image?
developers.google.com/android/images
All you need to do is extract the downloaded zip, place your fastboot and adb files in there (or vice versa) and finally run flash-all.bat.
Be cautious: if there's any data left on the internal storage, it WILL be wiped.
Thozel said:
Did you try installing a factory image?
developers.google.com/android/images
All you need to do is extract the downloaded zip, place your fastboot and adb files in there (or vice versa) and finally run flash-all.bat.
Be cautious: if there's any data left on the internal storage, it WILL be wiped.
Click to expand...
Click to collapse
Hello,
Did you read the OP? Bootloader is LOCKED. I know you want to help and the post is a little bit hard to understand. But read before posting please...
Cheers...
amermsn said:
nexus 6p bootloader shown but cant flash eny thing bootloader locked no recovery to flash ota tray every thin eny eidea pleasssssssssssssssssssssssssss
Click to expand...
Click to collapse
Bootlooping with no recovery and bootloader is locked- there is no chance. Time for a new device.
5.1 said:
Hello,
Did you read the OP? Bootloader is LOCKED. I know you want to help and the post is a little bit hard to understand. But read before posting please...
Cheers...
Click to expand...
Click to collapse
I did, though to be fair it's not very well constructed.
How did you get it in this situation?
What you could try is booting into the bootloader and issue these commands through fastboot;
fastboot format cache
fastboot format userdata
They might work with a locked bootloader and could possibly solve your issues
Thozel said:
I did, though to be fair it's not very well constructed.
How did you get it in this situation?
What you could try is booting into the bootloader and issue these commands through fastboot;
fastboot format cache
fastboot format userdata
They might work with a locked bootloader and could possibly solve your issues
Click to expand...
Click to collapse
Hey,
"fastboot format" doesn't work unless unless the bootloader is unlocked...
Cheers...
5.1 said:
Hey,
"fastboot format" doesn't work unless unless the bootloader is unlocked...
Cheers...
Click to expand...
Click to collapse
I found a thread earlier that said in 'some' cases it does, so there is hope...
But I'm just gonna assume you're right. In which case OP's situation seems pretty hopeless unfortunately
BLOD
Sent from my Nexus 6P using XDA-Developers Legacy app
Hey guys, I need some help. I searched a lot and didn't find nothing that looks like my problem.
I had a OP5 with Magisk root and tried to back it to stock. Then I flashed OnePlus recovery again, wiped everything and install 5.1.3 again. Everything ok until I made some dumb ****.
I tried to re-lock my bootloader and now my phone says that it won't boot up because it's corrupted. I can boot into both recovery and fastboot but I can't install anything (I can only install through ADB sideload and it says install failed) and I can't re-unlock my bootloader because it says remote: Flashing Unlock is not allowed cant boot (but I can't boot so I can't enable oem unlock through developer menu).
There is anything that I can do to make my phone boot again?
Thanks in advance.
[TOOL] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery) use this
killerex said:
[TOOL] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery) use this
Click to expand...
Click to collapse
Thank u, killerex. Just one doubt: I see on the post about the tool that I need to have OEM unlocking enabled but, as I said, I can't do this since I can't boot. I can use this tool to flash Oxygen OS even with OEM unlocking disabled? And, if yes, how do I do, just flash the zip using the tool while in recovery?
ReeSilva said:
Thank u, killerex. Just one doubt: I see on the post about the tool that I need to have OEM unlocking enabled but, as I said, I can't do this since I can't boot. I can use this tool to flash Oxygen OS even with OEM unlocking disabled? And, if yes, how do I do, just flash the zip using the tool while in recovery?
Click to expand...
Click to collapse
Go to fastboot mode using the tool you can flash new recovery and unlock bootloader and flash rom..sorry for bad English
in fastboot mode, use fastboot command to flash new recovery and then install new rom in recovery. You can also use adb sideload in recovery.
thejuzo said:
in fastboot mode, use fastboot command to flash new recovery and then install new rom in recovery. You can also use adb sideload in recovery.
Click to expand...
Click to collapse
That's one of my problems, I can't flash new recovery cuz my bootloader is locked
killerex said:
Go to fastboot mode using the tool you can flash new recovery and unlock bootloader and flash rom..sorry for bad English
Click to expand...
Click to collapse
No problems, my english is not that good too. Just one more question: there's any difference if I go to fastboot through the tool or the power option (vol up + power), because since I can only boot my phone in fastboot or recovery there is no way to go to fastboot using the tool (I guess)
ReeSilva said:
No problems, my english is not that good too. Just one more question: there's any difference if I go to fastboot through the tool or the power option (vol up + power), because since I can only boot my phone in fastboot or recovery there is no way to go to fastboot using the tool (I guess)
Click to expand...
Click to collapse
no you have to be on fastboot mode..https://www.androidfilehost.com/?a=show&w=files&flid=38683
killerex said:
Go to fastboot mode using the tool you can flash new recovery and unlock bootloader and flash rom..sorry for bad English
Click to expand...
Click to collapse
It didn't work, as I said, it can't flash a recovery with a locked bootloader and I can't unlock because I can't boot to enable oem unlocking
ReeSilva said:
It didn't work, as I said, it can't flash a recovery with a locked bootloader and I can't unlock because I can't boot to enable oem unlocking
Click to expand...
Click to collapse
Good try!
ReeSilva said:
It didn't work, as I said, it can't flash a recovery with a locked bootloader and I can't unlock because I can't boot to enable oem unlocking
Click to expand...
Click to collapse
You could try this:
https://www.google.ca/amp/s/forum.x...uide-unbrick-guide-hard-bricked-t3761706/amp/
It should work for almost any state. I haven't had the need to use it yet, but let me know if it works for you.
Cheers! ?
ScRuFFy7 said:
You could try this:
https://www.google.ca/amp/s/forum.x...uide-unbrick-guide-hard-bricked-t3761706/amp/
It should work for almost any state. I haven't had the need to use it yet, but let me know if it works for you.
Cheers!
Click to expand...
Click to collapse
I was trying to do this but Mega has a quota. I'll try with this link. Thank you for your try to help doesn't matter the result
Did you use this tool https://photos.app.goo.gl/4Z5GpgZpmn6FooWn7
ScRuFFy7 said:
You could try this:
https://www.google.ca/amp/s/forum.x...uide-unbrick-guide-hard-bricked-t3761706/amp/
It should work for almost any state. I haven't had the need to use it yet, but let me know if it works for you.
Cheers!
Click to expand...
Click to collapse
It works
Thanks a lot.
You need to use the Qualcomm tool if it's that bad :
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
You're gonna lose all your data cos the phone will get a COMPLETE factory reset, take it as a life lesson to back up first
Oh...never mind then, lol
unbrick phone for chinese
https://youtu.be/bBP5eWvvrQM
btw,pls post it in q&a
djsubterrain said:
You need to use the Qualcomm tool if it's that bad :
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
You're gonna lose all your data cos the phone will get a COMPLETE factory reset, take it as a life lesson to back up first
Oh...never mind then, lol
Click to expand...
Click to collapse
Oh, actually lose my data is not a problem. My only fear was lose my phone LOL But the post from ScRuFFy7 works as a charm.