Develop Bugs

[Q] Yet another bricked Defy: no response at all

Disclaimer:
I have the same problem this guy have:
http://forum.xda-developers.com/showthread.php?t=1036327
But no one in the thread was able to understand him, so I'm trying to open a new thread to organize the thoughts (there are too many people with too many problems posting there).
What happened:
I have a 1-month-old Defy. On the 2nd day I already had it rooted, running froyo (with Pays ROM), overclocked, undervolted and all this stuff. Three days ago, suddenly, it started to FC apps randomly. So I wiped. Then it became stuck on M logo. No big deal.
I tried then to reflash the SBF via RSDLite, but for some reason I only had the previous SBF (3.4.2-155-2) and my phone was running on 3.4.3-11. Don't know if it has downgradeability issues, but I couldn't flash it. It threw some checksum errors in the process and wasn't able to finish the process. Then my phone became "Code Corrupt". I was still able to see it in RSDLite. No big deal.
I didn't know the battery wouldn't charge in the bootloader screen, so I quickly ran into a "Battery Low / Cannot Program" state. It was written in the screen what happened. I knew what I had to do. No big deal.
I read about the MacGyver method, but prefered instead to use a universal charger to charge my battery. Was charging all night, seem to work on other defy (tested it later). But, now, my phone makes no response to battery insertion. Not even power+vol up, nothing. No white led, no bootloader, no code corrupt, no nothing. Ok, that's a big deal.
If I connect it to USB, nothing happens. No driver instalation, no device recognized, no RSDLite, no bootloader, no white led. Nothing.
The only response I have from the phone is: if I pull the battery and put it again while connected to USB, the computer will make an USB connection sound, then 2 seconds later, it makes an USB disconnection sound. If I open the device manager, it shows the Motorola Device for 2 seconds (OMAP something) and then it desapears. So I'm not able to see it in RSDLite.
I tried even to power up the phone with the MacGyver-crafted USB cable (with and without battery inserted together), but the computer response is the same. That is the only thing that makes me believe that my Defy isn't entirely dead. But isn't much useful after all.
Hope I explained it well. I'm one of those guys who doesn't speak english well, so I hope you guys understand me . Thanks in advance.

I would really like to be helpful, but it looks, that you tried everything. Only one thing. Try to check the battery voltage and if you can, try another battery in your phone. The charger could broke your battery, even if it one time worked in another phone.

Try reinstall usb drivers, rsdlite, different usb port, and different pc.

@peetr_
The battery seems to still work, as putting it in the phone makes it to be recognized (for 2 seconds) on the PC. Also, the phone seems to get a little warm while with the battery.
@ABC_Universal
I tried. Installed all the drivers in another PC I have here and tried the same methods I said before. Same results.

If you're planning to dumb the phone into a dumb site.. let me know when and where...
Ok... you need to narrow down the possibility here by putting another full charged battery and see if the phone do get connected status via PC. External charger might just toast your battery if you read carefully your entire story back starting from this line "I didn't know the battery wouldn't charge in the bootloader screen, so I quickly ran into a "Battery Low / Cannot Program" state. It was written in the screen what happened. I knew what I had to do. No big deal."
External charger might giving out totally different voltage/current rating from the defy own charger.

im having the same issue, did you solve it?

im having the same issue, did you solve it?

try putting a different Defy's battery, doesn't work just give it for RMA... you'll get a replacement. looks like a hardware problem to me...

You have tried the McGyver-trick?

I tried using another battery in it and didn't work. I was far from a computer when I tried, so I didn't check if I was able to connect it to PC (even if the screen was totally black). But if it was a battery problem, I was expecting at least the bootloader to appear, but still nothing happened.
I took it to RMA two weeks ago. Here in Brazil they take too long to return it =/. Still waiting.
skattegat: I tried. With and without battery inserted together. Both cases, I was only able to listen the USB connection start and end, 2 seconds later. I know the cable was working because even without battery, when I touch the wires, I was able to listen the usb connection sound.

Ok. At least you have the time now to enjoy your sunny weather in Brazil...

RSD lite sucks... Well it doesn't suck but it refuses to work anymore no matter what I do!
Use sbf_flash in linux and it should do the trick! PM me if you need help

First flash the sbf. Then enter stock recovery and do the recovery from there. Flashing does not wipe cache. But after the flash the recovery will do the wipe automaticly.
Sent from my MB525 cm7quarx

Just a follow up:
My phone returned today from the warranty. Is fully working now, but I noticed the IMEI has changed. So I guess they changed the entire circuit.
It's not helpful for those who have the same problem, but I'm happy again

i have problem too..
I made a mistake in ROM CM7: I "install the 2nd init". and the results stuck on the boot logo .. : (
I finally went into the boot loader, then flash again use 3.4.2_177 SBF-005_NORDIC (do not wipe the data) .. remain stuck at the boot logo. and I try to use flash SBF-Stock.UKTmobile 3.4.3_11 (not wipe the data) and the results .... still stuck>> it's just an animated logo appears only.
AND THEN ---------------------------------
for this case:
I want to get into stock recovery:
1. defy turn off, turn the power button + volume down (hold a while)
2. logo appears>> android +! (the menu does not appear anything)
3. and I do not know anymore what should I do: (
please help me Quarx
thanks before

Don't see why you should ask the same question in multiple topics. My answer still is the same:
If pushing the lower right corner doesn't do the trick, try instead pushing both volume buttons at the same moment. Worked for me
Sent from my MB525 using XDA App

Fotogravin said:
Don't see why you should ask the same question in multiple topics. My answer still is the same:
If pushing the lower right corner doesn't do the trick, try instead pushing both volume buttons at the same moment. Worked for me
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
it's work..!! sorry i ask same question on other thread.
i'm so confuse
makasih gan

hey omneon are you able to solve your problem..plz help me man mine defy is stuck on m logo. same problem like your..

[Q] Galaxy Nexus black screen of death

Basically, this: http://forum.xda-developers.com/showthread.php?t=1384415
No one responded to that thread because it was in the wrong forum.
I got the "Phone -- ! -- PC" screen, and was attempting to fix it before getting this black screen of death.
Galaxy Nexus GSM
Rooted, Codename ROM, don't think there is a Kernel in there
Carrier: Virgin Mobile
Edit: I won't be able to respond for a couple hours as I'm going to work. Any and all help is much appreciated.
Original post from above thread below:
Hello guys,
I have recently bought my first android phone, the Samsung Galaxy Nexus.
On the second day I decided to root it since I needed market enabler, as my local market (UAE) has literally no apps.
I rooted using the SDK tools, fastboot and superboot. Everything worked fine for 1 day.
However, the next day, the phone just died on me, and would not boot at all. It kept getting stuck on the "Google" image at startup. At that point, I could still go into the bootloader. I tried locking/unlocking the bootloader again, since that basically wipes all the date on the phone, but it still refused to load, it would get stuck at the startup animation.
After a few more attempts, it kept spam restarting every time I tried to switch it on.
At that point, I was downloading the default OEM ROM so I could reflash that onto the phone. However, I thought I could try using the superboot bat file again, and maybe that would fix the problem. BIG MISTAKE.
As soon as I ran that file, the phone COMPLETELY died. It will not start at ALL, it will not go into Bootloader, not go into Recovery mode, and not even go into Download (odin) mode.
The ONLY possible response you can get from it, is when you plug it into the PC. My PC seems to play that "detection" sound, same sound as when you plug in a USB, but it would just play that sound over and over again, as if im plugging/unplugging a device really quickly. It seems like the phone is continously restarting itself. When I connect the phone to the PC and that disconnect/reconnect sound comes up, I went into my device manager and I could see the following:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Now the problem is since I cant get into any mode whatsoever, its a bit hard to diagnose the phone. I know there is a "recovery" slot at the bottom of the phone that is accessible with a small pin, but I dont for the life of me know how that works or what it does. Does anybody know how to work that or what it actually does?
Any help would be appreciated! Thanks fellas.
Click to expand...
Click to collapse

What i with my little (almost nothing experience in android) would do its going to another computer with no drivers installed, would download the toolkit and install those drivers, then plug the phone and see what happen, im sure its not bricked since the computer recognice it.. I did lot of stuff with blackberry and there was a lot of ways to recover a phone like that... From here if the toolkit recognice it in any way.. Then you could try to do some of those steps.. As far as i tried doing all kind of stuff to my phone, toolkit its for much the Best Tool and way to do anything to your phone or at least for starters like me
Sent from my Galaxy Nexus using xda premium

But the computer doesn't actually recognize it. The "detection" sound it makes is for an unresponsive device. It won't charge, won't be recognized, and no matter what combo I use, it doesn't turn it.
I played dumb, called Samsung, and now I'm going to send it in. Thanks for the help though.

sometimes my screen goes blank and I have to pull the battery and everything comes back to normal

qhsusb_bulk no download mode no recovery no bootanimation

Can anyone help me with this problem?? I tried many ways but there isnt anything possible. The community either ignores me or gives me a simple answer. Can anyone just give me a suggestion of what i cant do?

You can't do anything with it by the looks of things, it's gone.

me too.....

On the same boat but mine is being recognized by my PC.

Same here... some extra info.. but still broken.
It happened yesterday. I have the H812 Canadian version. It just was suddenly, I wake up and pull it from the charger, read some mails during breakfast, go to work and then the screen didn't turn on. Holding the power button did nothing.
- Pull the battery, put it back, nothing.
- Then maybe I though maybe the phone didn't charged properly overnight and the battery died. I plug the charger and the battery logo pop-up 2 seconds later it boot up on the LG animation logo. It goes stuck loping there.
- After 30 minutes, holding power button did nothing, pull the battery. Always on the charger put the battery back and it immediately went to Recovery Mode and at the end showing "fastboot mode". What!!! I thought this phone bootloader is locked.
- I unplugged for the power and put in on the computer and it was recognized as "Marshall phone". I tested "fastboot devices" command and it was recognized. Well it could be recovered if I had a image that I could applied.
- I tried to applied a previous download KDZ "H81210H_00.kdz" even that my phone was already on "v10n". But fastboot didn't liked the kdz file format.
- Previously also I did a backup of the system partition but also the format is incorrect for fastboot.
- So no available files that I could apply on fastboot.
- I removed the usb and battery put it back. Black screen. Nothing.
- Plug the phone without battery on the USB and for my surprise the computer still recognized as "QHUSB_BULK" but not recognized driver. Which reading around, I understand is a Qualcomm low level mode to start up programming a device, but no information of how to do it.
- To go back fastboot, I had to simultaneously plug the USB and insert the battery at the same time. Sometimes even the fastboot gives an error that could start. Which it makes me think the phone ROM has a major corruption and it's booting on the emergency bootloader.
So, I didn't have time to keep playing around to see if I could do anything else. I drove to a Fido store and drop it to send it to LG for repair.
This is my first brand phone out of Nexus, I'm really disappointed with LG (actually this will be the case with any major Android brand phone).
- First there used to be a way to recover the current KDZ, now they closed the path.
- Later, only offers unlock boot loader on one model that is not in north america.
- No fastboot recovery images. Zero, nada.
So, many times I had bricked my Nexus phones by tweaking and playing around, and it always there is a way to recover it. The LG G4 brick itself on my pocket and I feel helpless to try to recover it. Even my wife iPhone's I have been able to restore them by downloading the full recovery image.
I'm seriously thinking resell my LG G4 as soon as it's back and go back to Nexus phones (5X).

tacua said:
It happened yesterday. I have the H812 Canadian version. It just was suddenly, I wake up and pull it from the charger, read some mails during breakfast, go to work and then the screen didn't turn on. Holding the power button did nothing.
- Pull the battery, put it back, nothing.
- Then maybe I though maybe the phone didn't charged properly overnight and the battery died. I plug the charger and the battery logo pop-up 2 seconds later it boot up on the LG animation logo. It goes stuck loping there.
- After 30 minutes, holding power button did nothing, pull the battery. Always on the charger put the battery back and it immediately went to Recovery Mode and at the end showing "fastboot mode". What!!! I thought this phone bootloader is locked.
- I unplugged for the power and put in on the computer and it was recognized as "Marshall phone". I tested "fastboot devices" command and it was recognized. Well it could be recovered if I had a image that I could applied.
- I tried to applied a previous download KDZ "H81210H_00.kdz" even that my phone was already on "v10n". But fastboot didn't liked the kdz file format.
- Previously also I did a backup of the system partition but also the format is incorrect for fastboot.
- So no available files that I could apply on fastboot.
- I removed the usb and battery put it back. Black screen. Nothing.
- Plug the phone without battery on the USB and for my surprise the computer still recognized as "QHUSB_BULK" but not recognized driver. Which reading around, I understand is a Qualcomm low level mode to start up programming a device, but no information of how to do it.
- To go back fastboot, I had to simultaneously plug the USB and insert the battery at the same time. Sometimes even the fastboot gives an error that could start. Which it makes me think the phone ROM has a major corruption and it's booting on the emergency bootloader.
So, I didn't have time to keep playing around to see if I could do anything else. I drove to a Fido store and drop it to send it to LG for repair.
This is my first brand phone out of Nexus, I'm really disappointed with LG (actually this will be the case with any major Android brand phone).
- First there used to be a way to recover the current KDZ, now they closed the path.
- Later, only offers unlock boot loader on one model that is not in north america.
- No fastboot recovery images. Zero, nada.
So, many times I had bricked my Nexus phones by tweaking and playing around, and it always there is a way to recover it. The LG G4 brick itself on my pocket and I feel helpless to try to recover it. Even my wife iPhone's I have been able to restore them by downloading the full recovery image.
I'm seriously thinking resell my LG G4 as soon as it's back and go back to Nexus phones (5X).
Click to expand...
Click to collapse
Look at the Canadian Thread in the general section, there are some direct links to kdz's there.
Here you go
http://forum.xda-developers.com/g4/general/canadian-guide-complete-source-lg-g4-t3212449

Done that
mb_guy said:
Look at the Canadian Thread in the general section, there are some direct links to kdz's there.
Here you go
http://forum.xda-developers.com/g4/general/canadian-guide-complete-source-lg-g4-t3212449
Click to expand...
Click to collapse
I had lurked this forums for 3 year now, and until now I signed up to post my experience. So yeah, I have looked on this forum and other sites for the correct KDZ. If you look careful on that post (as I did) that latest full LP version KDZ is 10h, which already have it for a while. However when this happened to my phone, it was already on 10n which is the version I expect to find somewhere to be able to recover my phone. Recently, I see that is available version 20e but that is already MM, I want to observe how it behave on the community before I decide to go there.
No matter what is the case, the phone was sent for repair. I think mine when under the worst case scenario of the so much mentioned bootloop. So much, that it even opened the bootloader and show me the fastboot prompt, although that the Canadian version is locked.
For my experience with the Nexus, they come with two bootloaders, the normal that can be updated locked and unlocked and a emergency bootloader that is available when the device is almost bricked and the normal bootloader is borked. Finally there is a low level manufacturer flashing that use the OEM SOC application to put the initial ROM. In the past I have been able to play with the Rockchip and the Nvidia Tegra 3, applications at that level. So those devices are simple "unbrickables". Low level Qualcomm (QHUSB_BULK) flashing is barely mentioned on the net, no process detailed, no application available so far that I can find.
My experience with LG so far is like buying a PC with installed OS, no recovery CDs, no website to download the recovery, no access to the BIOS, no "normal" human soul is allowed to create a full backup of the HD without going on a major hackaton with not assurance that what you get will work in future case of emergency. If something happens to the OS when you are out of warranty... you are royally screwed.

Guys try the oven method it may work. Some are saying it lasted 24 hrs others say its still active. It may be dangerous but worth a shot since no one else is taking action on this fix.

Also my phone was just rooted. At that time I wasn't trying to do anything with modifying but just using instagram.

(FIXED) Samsung Galaxy Tab S 8.4 will not fully boot up.

I've had my Samsung Galaxy Tab S 8.4 (SM-T705Y) for just over two years now and it has worked brilliantly beside the odd issue here and there, including the device freezing from time-to-time. Each time that particular freezing issue has happened, I've used the 'Power and Volume Down buttons' technique and it has successfully fixed the issue.
Now, a few days ago, I was using my tablet for normal morning things; music app playing in the background, YouTube opened on the side, using the preinstalled Browser and Google Chrome apps, etc. I am not sure if it was updating any Google or Samsung apps at the time. The screen froze up so I left it for a few minutes, seeing if it would unfreeze. When it didn't, I used the same Power and Volume Down technique, which successfully forced-restarted the tablet. There was a small mistake I made doing this; I was holding down both the Power button and Volume Up button. It took me around thirty seconds to realise why the screen wasn't turning off and switched to the Volume Down button. At the time, both my earphones and the charging cord were connected.
However, upon the loading screen, I noticed that it did not pass the Samsung logo screen with the little explosion of blue circles and just kept replaying the same animation repeatedly. The Application History and Back buttons did not light up and the device did not vibrate as it normally does when it boots up. I repeated the Power-Volume Down technique to see if that would fix the issue. Once again, the tablet rebooted normally but was stuck at the logo screen playing the animation. I tried this same force-restart again, this time without the charger plugged in. No change.
So, I left it running through the animation while doing Google searches through forums and getting into contact with Samsung as to what the issue could be. I'll list down below what my tablet can and can't do at the moment and hopefully someone will have a clue as to what is going on and how to fix it. I will point out now that it was not going through a firmware update at the time, the device is not rooted and nor do I plan on taking that path with it, and I have not made any changes to it that can void the warranty.
It can:
- Recharge (The battery icon will show up if it is force-restarted and the charger is plugged in at the time.)
- Reboot (It's not exactly stuck in a bootloop, more of just the 'explosion' animation replaying over-and-over.)
- Enter Recovery Mode
It cannot:
- Enter Safe Mode
- Be Shut Down without the charger attached (As stated above, the device will only turn off with the Power-Volume Down buttons held for about 30 seconds and that causes the device to restart, not turn off. The only way for it to completely shut down is to have the charger connected and then unplug it after the battery icon appears.)
I have tried removing the SD card and placing it back in, power-cycling it, letting it run on the animation until the battery runs out and then letting it recharge to 100% before turning it on again, connecting it to Samsung Smart Switch (which recognises that there is a Samsung device connected, but not being able to register the device itself), and wiping the Partition Cache (Also note; the Recovery Mode has the 'No Command' sign with the android laying down and the red triangle with the exclamation point above it. Clearing the Partition Cache seemed to go smoothly, however when I chose the 'reboot device now' option, the 'No Command' sign changed to 'Error!' and rebooted the device anyway.) I am now currently trying another technique written on a different website (though since I am a new user, I cannot post up URLs at the moment). So far, plugging in the earphones alone hasn't worked and the device is currently connected to my laptop - which is shut off - and still has the earphones connected, but the animation is the only thing the screen is still showing.
I have important files saved in the internal storage of my Tab S and I do not have them backed up, which is the only issue that's stopping me from just going ahead and doing a Factory Reset as I cannot lose these files.
I am unsure if my Tab S is soft-bricked or if this is another issue entirely and I just missed something that could have already fixed it.
Yes, this is a long and detailed post, but hopefully with these details, someone will be able to help with this issue. If I can restore my Tab S to its condition before the freeze, that would be amazing, but I can definitely settle with only being able to salvage my files from the internal storage and then performing a Factory Reset on it.
Thank you in advance~

It might be a corrupt partition. The way i know involve rooting or the other one might format your device to factory setting.

edan1979 said:
It might be a corrupt partition. The way i know involve rooting or the other one might format your device to factory setting.
Click to expand...
Click to collapse
Really? I might look into that a bit more, thanks! With the second method you mentioned, how likely are the chances of it formatting the device to the factory settings?

AussieMouse said:
Really? I might look into that a bit more, thanks! With the second method you mentioned, how likely are the chances of it formatting the device to the factory settings?
Click to expand...
Click to collapse
download the official firmware and flash it via odin. it usually fix this type of problem. but usually the files on the internal storage/sdcard will be intact. only the data apps will be gone. this will not break your warranty (its already 2 yo device... no more warranty anyway ^_^)

edan1979 said:
download the official firmware and flash it via odin. it usually fix this type of problem. but usually the files on the internal storage/sdcard will be intact. only the data apps will be gone. this will not break your warranty (its already 2 yo device... no more warranty anyway ^_^)
Click to expand...
Click to collapse
Alright, I'll try that and let you know how it goes. Is there any specific website I should download the firmware (4.4.2 KitKat) from? (Yeah, I agree with you there! Still, just to be on the safe side~)

KIT KAT? ok that's old... hahaha... why dont you try MM. I think you can search for it at fw.updato.com probably can see all related firmware there.

edan1979 said:
KIT KAT? ok that's old... hahaha... why dont you try MM. I think you can search for it at fw.updato.com probably can see all related firmware there.
Click to expand...
Click to collapse
Haha Yeah, I'm not too fond of installing software updates due to past experiences~ I'll have a look around.

AussieMouse said:
Haha Yeah, I'm not too fond of installing software updates due to past experiences~ I'll have a look around.
Click to expand...
Click to collapse
MM is ok. I dont have any problem with it.

edan1979 said:
MM is ok. I dont have any problem with it.
Click to expand...
Click to collapse
Thank you so much for your help! I managed to find the KitKat 4.4.2 firmware on SamMobile and flashing it restored everything~

soft bricked from ota update

now, i have no idea if this is the actual definition of "soft bricked"... so ill just tell you my story.
ok... so a quick history... phone was never rooted... ota update in november caused the phone to reboot every time the screen went off. had to install "wakelock app" to make it usable... update in december caused the phone to not be able to turn on. im not sure what happened. started the update, let the phone sit for a little while... when i looked at it again... nothing. it was just dead. no buttons would turn it on. had to get a new phone. note 4 was a private purchase, so no warranty options.
after leaving the battery out for a week, it would turn on but get stuck on verizon screen, get real hot, and every 30 seconds, blip a vibrate and a screen flash.... so... i tried clearing cache, tried a FDR... nothing. so i basically tried what is on this page:
https://forum.xda-developers.com/no...mware-firmware-kernel-modem-recovery-t2942937
with the newest firmware through odin... i unzipped the file, put the phone in download mode, connected it, waited for blue box, browsed to tar.md5 in "ap" box, and hit start when ready. got an error, after a while, i pulled the battery, and now when i turn on in download mode it says "your device didnt update successfully. use the verizon software repair assistant on a computer to repair your device and complete the update"
kies does not recognize my phone... i can't find a software repair assistant. if i try to run odin again, it just gives me "complete(write) operation failed"
hoping i can figure out how to salvage this thing. not super hip to phone software. ive managed to root numerous phones in the past. this is the first time ive had an issue, and its with the first phone i didnt root.
thanks in advance. sorry if this is totally newb level stuff. i just really need help, and get lost real quickly trying to do my own research... but trust me, ive tried.

idiggplants said:
now, i have no idea if this is the actual definition of "soft bricked"... so ill just tell you my story.
ok... so a quick history... phone was never rooted... ota update in november caused the phone to reboot every time the screen went off. had to install "wakelock app" to make it usable... update in december caused the phone to not be able to turn on. im not sure what happened. started the update, let the phone sit for a little while... when i looked at it again... nothing. it was just dead. no buttons would turn it on. had to get a new phone. note 4 was a private purchase, so no warranty options.
after leaving the battery out for a week, it would turn on but get stuck on verizon screen, get real hot, and every 30 seconds, blip a vibrate and a screen flash.... so... i tried clearing cache, tried a FDR... nothing. so i basically tried what is on this page:
https://forum.xda-developers.com/no...mware-firmware-kernel-modem-recovery-t2942937
with the newest firmware through odin... i unzipped the file, put the phone in download mode, connected it, waited for blue box, browsed to tar.md5 in "ap" box, and hit start when ready. got an error, after a while, i pulled the battery, and now when i turn on in download mode it says "your device didnt update successfully. use the verizon software repair assistant on a computer to repair your device and complete the update"
kies does not recognize my phone... i can't find a software repair assistant. if i try to run odin again, it just gives me "complete(write) operation failed"
hoping i can figure out how to salvage this thing. not super hip to phone software. ive managed to root numerous phones in the past. this is the first time ive had an issue, and its with the first phone i didnt root.
thanks in advance. sorry if this is totally newb level stuff. i just really need help, and get lost real quickly trying to do my own research... but trust me, ive tried.
Click to expand...
Click to collapse
do a battery pull to shut off your phone then boot into download mode like normal unzip and flash this ( https://www.androidfilehost.com/?fid=24588232905720219 ) in the ap slot.

do a battery pull to shut off your phone then boot into download mode like normal unzip and flash this , link was here, in the ap slot.
OP, did you try this process listed above and did it fix your problem or did you something else? Thank you.

SPIRITJCC98 said:
do a battery pull to shut off your phone then boot into download mode like normal unzip and flash this , link was here, in the ap slot.
OP, did you try this process listed above and did it fix your problem or did you something else? Thank you.
Click to expand...
Click to collapse
nope, didnt work. was pretty pissed at the time. i had to give up and get a lgv20.