Bricked phone - LG Optimus L90

I tried installing TWRP but I messed up somewhere, now my screen stays black, when I connect it to the computer it shows this:
oi61.tinypic.com/qqpqg2.jpg
When I try to flash a kdz it stops and it says there's no device connected, I cannot go into download mode or fastboot. When I remove the battery and I keep it plugged in to the PC it shows the battery with a question mark (?).
With the LGMobile Support Tool, when I try to upgrade recovery, it stops at around 35% and it says my battery is too low and it can harm my device if I proceed to update, and it forces me to close it.
Once again, I tried flashing KDZ, I made sure the battery was 100%, I tried to enter download and fastboot mode, no result.
oi59.tinypic.com/15cloq0.jpg
oi61.tinypic.com/qqpqg2.jpg
I can't even format the partition or put anything inside it because it's write protected.
Is there anything I can do to unbrick my phone? (D405n)
EDIT: I have a spare LG L90 if that helps, if I can use anything from that one (software) you could tell me what to try and I'll attempt a fix.

READ A ****ING GENERAL FORUM!!!!!!!!!!!! HEREEEEEEEEEEEEEEE http://forum.xda-developers.com/lg-l90/general/how-to-unbrick-hardbricked-phone-t3100163

TreQUS said:
READ A ****ING GENERAL FORUM!!!!!!!!!!!! HEREEEEEEEEEEEEEEE http://forum.xda-developers.com/lg-l90/general/how-to-unbrick-hardbricked-phone-t3100163
Click to expand...
Click to collapse
No need for the caps and other stuff. I can barely understand that tutorial, if you could fix the grammar and update the steps for better understanding I might be able to do it.

TreQUS: also, the general forum you mention does not yield any help in case you you encounter the "write protected" message. Read better next time.

Related

Sony Z1 Fastboot File Recovery

Hey All!
I have a Sony Xperia Z1, which although advertised as waterproof, somehow got water damage after a day at the waterpark, even though all the flaps were perfectly closed and the phone even had a case that covered the whole back and sides of the phone.
After a few days of letting the phone dry out, now I'm able to connect it to my laptop, but only in fastboot mode as the phone won't boot up and I can't turn on USB Debugging to try and do something via ADB. Anyway, the bottom line is that I need to recover the files from my phone. I read about pulling files out through ADB, but I have no idea if it's possible to somehow acces the phone memory through Fastboot mode or at least switching to ADB using fastboot. The phone has insurance so I don't really care about the hardware, I just want my photos and files(which I realise I was an idiot for not backing up regularly).
Please help!
P.S. The phone isn't and has never been rooted.
Try here: http://forum.xda-developers.com/showthread.php?t=1849170
Thanks. I read everything but unfortunately the information found on that page and the links provided there doesn't help in my situation. From what I read there, the solutions include wiping all the data off the phone, which is exactly what I don't want to do. I would just need to somehow switch from the current Fastboot mode(blue light) to ADB, so that I can use the "pull" cmd and download my files from the phone.
Sorry to hear mate. Perhaps you find some ideas here:
http://forum.xda-developers.com/showthread.php?t=2229250
Thank you. I tried those solutions last night, I managed to enter flash mode, flashed only the system files, without wiping the data, everything was succesful, but unfortunately there was no change in my phone's state. Still no response when trying to power it up, still no ADB access. I'm starting to think that my data can't be recovered in the phone's current state
If you can get flashmode and flash system files succesfully and without errors you could also try to flash whole ftf of your device and wipe everything else but data.

[Q] Help with seemingly perma-bricked LG G2 (VS980)

Hi all -
Thanks for checking in on my tale of woe. The summary is that I have seemingly nuked my partitions on my LG G2 (Verizon Edition VS980) so that nothing happens when I try to power the device on (literally nothing, no logo, no screen backlight turning on, etc.). In Windows, with some coaxing, the device will appear as a QHSUSB_BULK device (with a yellow exclamation point in Device Manager, and even when I boot into Linux to look at the partitions, they aren't visible.
How I got here:
I was happily running XDABBEB VS980 2.3.0 from http://forum.xda-developers.com/showthread.php?t=2715408 with a few Xposed framework tweaks. Great ROM.
I dirty-flashed XDABBEB's VS982.5 v1.0.0 from http://forum.xda-developers.com/verizon-g2/development/xdabbeb-s-vs982-5-v1-0-0-t2975551 to have a look at the G3 interface. I did a Nandroid backup first, like any good crack flasher
I neglected to read the 2nd step of the VS982.5 thread carefully enough - about the fact that this ROM was bumped. I still am not sure what that means.
I played with VS982.5 for a bit, and it didn't really seem like I'd want to use it long term. Also, some of the LG apps didn't seem to work on first try, not sure if that was an additional flash required. (QRemote was what I ran into). Anyway, I thought I'd go back to VS980 2.3.0 for then by just restoring my Nandroid.
Booted into TWRP to restore the Nandroid. It did it's thing.
Upon reboot, the device showed the LG Logo and showed a Security Error in the upper left-hand corner, and sat there briefly, then shut off the screen. (Sorry, I don't remember the precise text, it was in small white letters, several lines' worth of text).
I tried rebooting a couple of different ways, and eventually gave up and followed this guide: http://forum.xda-developers.com/showthread.php?t=2582142
From a Linux Live CD (Specifically an old Hiren's 15.2), I thought I'd followed the instructions correctly. The partitions did show up correctly under /dev/sdk1.../dev/sdk36 or whatever. I did the dd as prescribed with the files.
Then I tried to reboot, and here we are. Apparent hard-brick.
What I've tried since the Linux fiasco.
Rebooting many different ways. (Recovery mode, etc.)
Going back to stock with kdz and tot methods, following this: http://forum.xda-developers.com/showthread.php?t=2432476 . The device is not recognized, probably because the normal USB driver won't load.
Checking to see if it'd show up in adb and fastboot commandline interfaces. No, of course.
Booting back into Linux to try the dd again. No luck. The 30+ partitions don't show up under /dev
Letting it charge, thinking the battery may have died. It has been plugged in long enough that it should be 100%. (I can't tell when the device is on or off any more, because there are literally no indications.). This doesn't seem to have made any difference
Holding the Down button and plugging in the USB port gives the QHSUSB_BULK (Code 28) error in Windows, so at least it's doing something... but not much.
Ideally, of course, I'd like to restore the partitions, get my nandroid written back to the device, and carry on with life. Failing that, I'd like to get the nandroid off so I don't have to spend hours setting up another G2. My mistake for keeping the nandroid on the device - I've never bricked a device this badly, and it's always been recoverable with some googling!
Help!
P.S. Sorry about the cross-post from the General LG G2 Troubleshooting forum - I hadn't realized there was a VS980-specific one.
I had this happen "going back" to a nandroid after testing the new G3 ROM myself...only I was able to boot recovery after the security error...you can't I'm presuming?
I couldn't boot into recovery. But yeah, my device is far past that point now - it seems to be pretty busted.
I'm a newbie that also screwed up his phone after trying xdabbeb's new G3 ROM. Seems like a lot of people doing this. Took a long time, but I was able to get back to stock with the LG Flash tool method. I was able to get into recovery and flash xdabbebs 'restore download mode' file though.
If you don't have recovery or download mode or fastboot screen, I think you are permanently bricked. But I'm a newb, so hopefully some experts will chime in here.
waingro808 said:
I'm a newbie that also screwed up his phone after trying xdabbeb's new G3 ROM. Seems like a lot of people doing this. Took a long time, but I was able to get back to stock with the LG Flash tool method. I was able to get into recovery and flash xdabbebs 'restore download mode' file though.
If you don't have recovery or download mode or fastboot screen, I think you are permanently bricked. But I'm a newb, so hopefully some experts will chime in here.
Click to expand...
Click to collapse
Yeah, my main issue is that I can no longer get my drives to mount in ANY fashion, I just keep getting the QHSUSB_BULK busted driver. in Device manager. I don't know if there is a driver that I can install that'll enable the partitions back in Windows, and I don't know how to install additional USB drivers in Linux.
Mark-7 said:
Yeah, my main issue is that I can no longer get my drives to mount in ANY fashion, I just keep getting the QHSUSB_BULK busted driver. in Device manager. I don't know if there is a driver that I can install that'll enable the partitions back in Windows, and I don't know how to install additional USB drivers in Linux.
Click to expand...
Click to collapse
I would try this. http://forum.xda-developers.com/showthread.php?t=2582142
Sent from my XDABBEB VS982.5 v1.0.0 with ART using XDA free mobile app
z3pp3lin said:
I would try this. http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
Thanks - I tried that in my step 7 already, in both Ubuntu and Slax. The dev/sdk1-36 partitions no longer show up.
I thought I'd update this story to let people know how it ended.
I ended up ordering another LG G2, but saw this thread late one night:
http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830
I had to make a Windows XP VM to get it running with the HS-USB 9008 mode, but after I did that, I kept getting the "device was not found in dload trying flash programmer" error.
I ended up contacting one of the guys in that thread who did a teamviewer session with some custom build of the b2b support tool, and he was able to unbrick it. He does charge for the service though.
It wiped the phone, but it is back in service now under XDABBEB's 2.3.0.
So now I have a spare LG G2 on its way.

Help with soft bricked L90

Let me start by saying I am not a developer and have never even rooted a phone. A google search led me to this forum, and I hope someone here may be able to help me. I am not familiar with some of the terminology, but I am an engineer, so I can understand the concepts.
My L90 D415 died last night and is stuck with the following text on the screen:
[10800] fastboot_init()
[10900] USB init ept @ 0xffd8000
[10920] udc_start()
I downloaded the USB driver from the LG website, and the phone shows up in Device Manager as Marshall London Bootloader Interface.
I got several more lines on the screen when I plugged and unplugged the USB cable, including "fastboot: oops!" I'm guessing that's not good.
I have no clue what to do next. TIA for any help with this.
D415 is a PITA to unbrick. As it shows fastboot you may be able to flash TWRP custom recovery to flash a custom ROM. But first try to start the phone in download mode to flash stock KDZ, it's explained in another thread.
If you can't then probably your phone's partition table is messed up, join other threads where people are trying to unbrick it.

I bricked my Moto X 2013 VZW Dev Edition - any chance of revival?

I'll start out by saying I was careless and had not read various threads before flashing things and causing my issues. I've already bought a replacement phone but I'd like to see if there's any chance to revive the Moto X or not.
What happened:
I had unlocked the bootloader years ago. I was running the (mostly) stock Lollipop 5.1 with XPosed, and got noticed of a security update.
After fully charging the battery, I flashed stock recovery over my custom recovery (TWRP) and then, without thinking, got the latest image from Motorola without realizing it was a 4.4.4 image.
I flashed the system partition using this image thinking it would remove SU and that I could install the update - this soft-bricked the phone when I tried to boot.
Too late, but at this point I re-flashed TWRP and ran a backup. I used adb to extract the backup and my other files from the /sdcard partition.
Factory Reset. The phone boot up at this point.
I tried flashing the logo, gpt.bin (I forgot that Lollipop changed how partitioning worked) and then did another Factory Reset. Phone boots fine.
I then tried restoring the data from my nandroid backup. Rebooted once, and phone seemed to start. And then it went black.
At this point, the phone does not appear to boot at all. I can't use Vol Down + Power to boot into Fastboot, and if I connect to a computer, it does not see the device... USUALLY.
If I connect via USB to my Windows computer, and try to boot into Fastboot, the green LED behind the volume will flash once and my computer will signal the "Hardware connected" sound. I can try to run 'adb reboot bootloader' but adb reports that it doesn't see any devices. My system events note a USB Input Device was added but don't get any further. Within 5 seconds, the "hardware disconnected" sound fires. About 20 seconds later, this will repeat on its own.
I just tried making a fastboot cable from a spare micro usb cable... I may have done it wrong - but it does not seem to have had any effect. The result is the same. It's possible I didn't solder the connection well, though (it was difficult exposing the terminals on my particular cable).
The screen is always black and never lights up in any way.
It kind of makes me think that the device is attempting to boot, fails, and cycles. Is there anything I can do?
At this point I am able to get into fastboot after bricking my XT1060DEV in a similar way. Follow the guide as best as you can in this post. Toward the end of that thread you can see the sequence of events that led me to at least fastboot mode.
Awaiting a response from someone who might know which gpt.bin and bootloader I can flash to have more than a blank phone. I'll try to keep you updated.
EDIT:
You might find it easiest to get QHUSB set up using this guide. This guide has been superseded by the previously posted one, but some people still report success following it.
PiArc said:
At this point I am able to get into fastboot after bricking my XT1060DEV in a similar way. Follow the guide as best as you can in this post. Toward the end of that thread you can see the sequence of events that led me to at least fastboot mode.
Awaiting a response from someone who might know which gpt.bin and bootloader I can flash to have more than a blank phone. I'll try to keep you updated.
EDIT:
You might find it easiest to get QHUSB set up using this guide. This guide has been superseded by the previously posted one, but some people still report success following it.
Click to expand...
Click to collapse
I may not have a chance for a few days, but I will try this. I did try to download the software on the second link you provided and some of the links on that page were broken.
I'm not going to lie, navigating those threads is harsh.
Towards the end of the first linked thread you can see a post with what ended up getting me into fastboot. It might be a decent little roadmap to guide you in the right direction (plus, I think the files I indicate in that particular post are all still up).
Keep us updated!
ohioDroid said:
I'll start out by saying I was careless and had not read various threads before flashing things and causing my issues. I've already bought a replacement phone but I'd like to see if there's any chance to revive the Moto X or not.
What happened:
I had unlocked the bootloader years ago. I was running the (mostly) stock Lollipop 5.1 with XPosed, and got noticed of a security update.
After fully charging the battery, I flashed stock recovery over my custom recovery (TWRP) and then, without thinking, got the latest image from Motorola without realizing it was a 4.4.4 image.
I flashed the system partition using this image thinking it would remove SU and that I could install the update - this soft-bricked the phone when I tried to boot.
Too late, but at this point I re-flashed TWRP and ran a backup. I used adb to extract the backup and my other files from the /sdcard partition.
Factory Reset. The phone boot up at this point.
I tried flashing the logo, gpt.bin (I forgot that Lollipop changed how partitioning worked) and then did another Factory Reset. Phone boots fine.
I then tried restoring the data from my nandroid backup. Rebooted once, and phone seemed to start. And then it went black.
At this point, the phone does not appear to boot at all. I can't use Vol Down + Power to boot into Fastboot, and if I connect to a computer, it does not see the device... USUALLY.
If I connect via USB to my Windows computer, and try to boot into Fastboot, the green LED behind the volume will flash once and my computer will signal the "Hardware connected" sound. I can try to run 'adb reboot bootloader' but adb reports that it doesn't see any devices. My system events note a USB Input Device was added but don't get any further. Within 5 seconds, the "hardware disconnected" sound fires. About 20 seconds later, this will repeat on its own.
I just tried making a fastboot cable from a spare micro usb cable... I may have done it wrong - but it does not seem to have had any effect. The result is the same. It's possible I didn't solder the connection well, though (it was difficult exposing the terminals on my particular cable).
The screen is always black and never lights up in any way.
It kind of makes me think that the device is attempting to boot, fails, and cycles. Is there anything I can do?
Click to expand...
Click to collapse
Try reflashing twrp via fastboot, install custom ROM -OR- download latest XML for your variant flash via rsd lite or manual flash.
Note: When using the XML you will lose everything, including data on internal storage.
Hopefully this helps ?
Also, if your phone stays black it's likely the battery is dead. Leave it hook up for awhile or keep trying to boot into fastboot(while plugged into outlet, not PC) and leave it for a couple of hours, should charge.
I'm speaking from personal experience, just without having Xposed framework, lol.
Sent from my Moto X using Tapatalk

Moto e5 play issue.

Hello everybody! I need help with my Moto e5 play XT1921-3 the problem that I have been facing is that the phone won't turn on like it used to. It still, charges, but I can only get it into ap fastboot mode and it does not let me access any of the features like recovery mode, because when I select it, it just turns the phone off and flashes a charging logo over and over again. I have never rooted my phone or have done anything riskful with it. It is very difficult to get it into ap fastboot with the battery inserted in the phone, but it is possible. This problem happened out of nowhere. All I did was take out the battery of my phone, after Shutting it off all the way. Then when I put the battery back in, this is when this problem started happening. This has happened to me before and I have fixed it before, using rsd lite, but now when I try to use rsd lite, I get a failed error everytime saying "failed partion gpt.bin/32" I also tried to fix that error, but I just keep getting an error after error message, I even took it to the T-Mobile store and they told me to keep it charged overnight. This is starting to get very stressful because I need my phone. If anyone can please help me, that will be very appreciated. Thank you.
Here's some stuff that should get you going again. The 3 links I posted all contain the necessary files to flash your phone to stock. You'll need the latest firmware for your phone as well. Install the Moto drivers, adb and fastboot files, and use the xml to batch converter to convert the firmware to a Windows batch script (assuming you use Windows). All the links will have instructions on installation and usage. If you need any more help let me know. I have the same device. http://www.rootjunkysdl.com/files/Android Programs/RSD_Lite_Motorola_XML_To_Batch_Script.zip
http://rootjunkysdl.com/files/?dir=Adb Fastboot Files
http://rootjunkysdl.com/files/?dir=Android Drivers/Motorola

Categories

Resources