Optimus Slider bricked - General Questions and Answers

I'm not sure where the right place to post this is, but maybe it can be moved to the right subforum. I have an Optimus Slider that is bricked. It is now stuck at the LG Logo. I do not have CWM installed, because I hadn't gotten around to doing that yet. Here is my problem: While I have the rom zip, bin, dlls, etc... I have tried booting into recovery and flashing the ROM from update.zip, but it says that it is not signed. I have tried the Smartflashtool, but it does not list any ports, thus I cannot do anything (though in Emergency Mode, my phone is on COM9). I have tried adb and fastboot, but they say device not found. I have even tried this: search "unbrick almost no matter what only lg optimus slider q unbrick coming soon" (with quotes)
It seems that if I could just get into a bootloader, flash a recovery image, or get a stock rom that is signed(even though the one I have apparently is) to just flash, I could be back up and running. Unfortunately, I am hitting a wall on every method I try. Please, can anybody help me?

Related

Problems while flashing Optimus M. Please help

Hey all,
I have been a long time flasher of phones however I did a bonehead move and need to see what if anything can be done. Here is what happened.
I have an Optimus M and I have successfully upgraded and downgraded the phone before. Today I was trying a downgrade and as I was flashing I was deleting some files to make some room on my netbook and deleted the .cab flash file. So I tried many times to get the image to take to no avail. I went to my other netbook and tried to flash with the upgrade file and no go there either. What I get when I try to turn the phone on is a very quick LG logo and then nothing. When I hook up the phone on usb with no battery I get a s/w screen however no recovery or reboot sequence I have been able to find works either. Here is a list of what I have already tried. Please let me know if there is anything else you can think of.
-Downgrade flash with Kp500
-pulled out battery and allowed to sit
-connected to other cpu to try upgrade flash via lg upgrader (no go)
-tried recovery sequence
-tried hard reset sequence
Man after all of these years of hacking phones I would hate to think I finally have had the bad luck to make a stupid mistake and brick one.
Thanks everyone!

[Q] Another Botched CWM upgrade

Hi Folks Im looking for help. I have the p920 AND I botched it.
I tapped for CWM to upgrade to the latest version and it all went wrong now im stuck on an LG logo with some what fuzzy appearance. Nothing happens eventually goes black.
Looking for some assistance?
I have searched as many bricked LGoptimus 3d posts and threads on here and tried but to no avail. I have the LGtool working but doesnt find the LG the latop cant detect it, it have some times shown something connecting but windows 7 knows best as aposed to letting me select the correct driver.
Help would be greatly appreciated.
DOBW said:
Hi Folks Im looking for help. I have the p920 AND I botched it.
I tapped for CWM to upgrade to the latest version and it all went wrong now im stuck on an LG logo with some what fuzzy appearance. Nothing happens eventually goes black.
Looking for some assistance?
I have searched as many bricked LGoptimus 3d posts and threads on here and tried but to no avail. I have the LGtool working but doesnt find the LG the latop cant detect it, it have some times shown something connecting but windows 7 knows best as aposed to letting me select the correct driver.
Help would be greatly appreciated.
Click to expand...
Click to collapse
try to flash the recovery using fastboot
The same thing happened to me a few days ago.
Version 6.0 of CWM Recovery caused my phone no stop boot at LG logo.
Use LG's official flash tool to recover phone (you will need to input your IMEI).
It will flash the latest stock rom to your phone.
After that I flashed CWM Recovery 5.0, that one works fine.
yep first time i tried cwm 6 i got stuck on lg boot too and without recovery... you can recover using fast boot like sww said (flash cmw 5 recovery in fastboot [if you go this way flash x and u bin's too, that way if you want to upgrade to cm10 you will be ready] and then restore rom in cmw) or put your phone in download mode (vol up+pwr) and use LG_KDZ_FW-Update_OfflineFix to flash a full kdz (that's how i did it) or like daniel.mota said use the official flash tool to make emergency recovery (probably the easiest method).
btw I tried flashing cmw 6 again a few days ago and it flashed fine this time, entered recovery fine, backed up fine but never restores correctly...
I agree. The new version has a lot of bugs. When I tried to reinstall a previous rom backup it stated that the md5sum was incorrect when it checked among other small glitches. I'm back to v5.0.2.7.
After back to version 5.0.2.7. The same back up was fine.
Sent from my LG-P925 using xda premium

[Q] Successful flash having no effect on soft brick

Boot takes me to a blank white screen, so does booting recovery mode.
I can only enter odin download right now.
I re-partitioned and flashed the correct stock rom for my country which completes successfully on the pc and device installing the bin files in every partition but this is not unbricking the device from booting to white screen in normal and recovery booting.
What am I doing wrong? Possibly an incorrect pit file for the rom? Am i missing something? Or is hardware probably broken aat this point?
See if you can dig up a 3 part stock firmware to flash (assuming you haven't already, a little vague about exactly what you have flashed, I also presume you're talking about an I9100 ?). Could well be a case of corrupted NAND, this is sometimes the case where you seem to get a successful flash but bootloop won't go away & you're still stuck with only download mode. Fix for that is a motherboard replacement, but I wouldn't be calling it just yet.
If you can't find a 3 part firmware (or if you've already tried one), just get hold of as many stock roms (from Samfirmware/AndroidFirmwares.net/Samsung-Updates.com) as you can & flash away; sometimes these cases are fixed by perseverance (the first 10 flashes don't work, but for whatever strange reason the 11th works, for example).
Search for Hopper8's 'Odin troubleshooting' thread & try all the stuff in that thread, might be something really small/obvious that's causing problems here.
I will continue flashing roms, I havnt yet found any roms for the device that arent all in one, flashing CWM recovery roms didnt work. Corrupt NAND would make sense being that it became randomly bricked in the first place and i have managed to change the fuzziness pattern of the white screen with some flashes, I would maybe have expected a write error though. I read his guide, I have taken care of everything on it.
If i attempt to flash different versions of jellybean will there be any conflicts with the device or the pit file being that it is 4.1.2 from the store?
Is there an answer for resetting Binary flash count or system status from this odin only state?
Is there an odin, usb jig or sd card method?
Whoa. You shouldn't be posting here for a Note. I'm asking mods to move your thread. Posting about devices in forums for different devices ain't allowed. Nobody here is going to be able to give you sensible advice because we're not familar with the device.

Bricked d801

i have LG G2 D802 32gb ... heres the details...
i tried to flash twrp recovery which lead me to fastboot with no recovery no download mode no adb connection just fastboot...
after two days of reading threads after threads i flashed "pgpt32g.img" "rpm.img" "sbl1.img" "sgpt32g.img" and "tz.img" with fastboot.. after that i finally saw my device booted normally.. but dont know why the touch went crazy... like theres something wrong with the screen... i thought i messed it up or its some software issue... so i downloaded D80220F_00.kdz and flashed it on my phone... once again i am stuck.. now on LG logo... after that i downloaded ""Europe OPEN D80220B_00"" "TMO-EE 32GB D80210B_00" and "UK Open 16GB D80210B_00" and flashed them one by one ... i am still at my LG logo phone doesnt go further....
now... i found these websites here on xda
http://lg-firmware-rom.com/
http://csmg.lgmobile.com:9002/csmg/b...heck2.jsp?esn=
i searched the firmware by entering my imei and both sites are gave me D80220C_00.kdz now... i flashed this file too... nothing happened all i see is LG logo and led changing colors....i also tried hard resetting the phone ....I flashed the file "D80220C_00"and nothing happend..
then followed a thread and i successfully booted into QHSUSB__BULK mode then i followed the steps
http://forum.xda-developers.com/showthread.php?t=2582142
...when i opened the back of my phone it says its D801 not D802.... so i downloaded d801's kdz....when i tried to flash d801's kdz but everytime i tried got stuck at 2% and unsuccessful. some guy posted he had the same condition and he flash d802 kdz... i flashed the f**king file and now i am again stuck at LG logo.. no recovery no download mode....just this irritating lg logo and and led light changing colors... tried to hard reset it nothing happens...
its been 10 days and i bricked this phone the first day i bought it... plzzz help me guys...
Here you go. Try searching a bit more next time. Hope you get it figured out.
Don't be intimidated just follow the steps one by one and if you get confused search in the thread. If you don't find what you need then ask. There is a lot of support in that forum it seems. I'm not sure what you are going to do with a d801 once you get all this sorted out though.
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404

Moto G (falcon) - Recovery img problem

Ok, I've been reading around the forum for about a week, trying to solve a problem with an original moto g (falcon). Basically my cousin got the moto g a few years back, and I, in my ignorance, tried to root the device for him. What I can remember was oem unlocking the bootloader with Motorola's unlock code through their website and adb. then my cousin freaked about the warranty warning on the boot animation, and decided against it. So cut to now, I'm a little more experienced, the phone's years old now, and he'd like to refresh it with a new rom, which I suggested, trying to help him. So forgetting what I'd originally done those years ago, I started the process of rooting the phone, installing a custom recovery, to hopefully put a lighter rom on it for him.
OK so it's a UK Retail on tesco mobile, moto g xt1032 running Android 5.1.
in bootloader menu it says "Device Locked status 2", dunno what this is in relation to.
first I checked the bootloader was still unlocked, and adb said it was. so I tried to use CF-autoroot to finish the job, but there was issues. it restarted the phone into fastboot mode, but when the script started, pc end did nothing, on the phone it said, "flashing unlock" and just sat there for 10-15mins doing nothing (i left it the time, just incase it was doing it).
So i read a little more, and found because i'd already unlocked the bootloader, I could just flash a custom recovery and root from adb? so I downloaded the latest twrp and tried. I was unable to do so. it said the partition wasn't the right size? should have documented it, but really didn't expect to run into any problems.
So I restarted and tried to do my usual fallback, and flash the factory image and start again, But couldn't find a source for the specific img, and tried to keep fighting on.
So I noticed that the phone wouldn't respond to adb or fastboot once in fastboot mode, when in android with usb debugging, no problems, in fastboot, didn't show up as adb devices?
I tried booting into the recovery from the bootloader menu, and got a no command. So there isn't a recovery, and I can't flash a new one? if i could find the stock recovery, I would try that.
so apart from deleting all his apps and settings, I hadn't solved the problem at all, and had to leave the job there as I couldn't find a solution.
I know this isn't the most detailed, but I've done this with quiet a few phones now, and felt I was pretty competent. I see everyday as an excuse to learn more, and like to think I have humility. So, I'm assuming I did something those years ago to damage the recovery? I'm running out of ideas, and was hoping someone could point me in the right direction?
I've lurked on xda for years, and learned so much about this kind of thing through my past experiences, but I'm stumped this time, and feel obliged to resolve the problem, as it was me who caused it.
TL DR
Can't flash recovery, no command when I try to open recovery, trying to either factory image back, or root/custom recovery it.
any insight would be much appreciated.
Hi. I just rooted and installed CM13 on an old XT1034 about two days ago. I am also sort of a ROM noob, I have ROMed a few devices, but usually but following strict step by step guides I have found here on XDA. Over the years I have some minor understanding of the process now.
I also got the "No command screen" when trying to get into TWRP recovery. The issue seems to be that if you reboot via ADB and the ROM launches it will automatically rewrite the recovery to the stock one, and when you try to go to recovery from fastboot, it gives you the "no command" error. Apparently you can get to the stock recovery from there by a hardware key combo, something like holding up vol for 10 sec then a quick press of power (I can't remeber the exact key sequence or what forum I read it in). If it does this you have to reflash TWRP again. This issue is mentioned here (http://wiki.cyanogenmod.org/w/Install_CM_for_falcon) in step 8 about installing recovery. What I ended up doing was after the flash of TWRP via ADB, I manually powered down, then manually bood into fastboot by holding volume down and power, and selecting recovery. This was a bit fiddly and I had to attempt it a few times but eventually it worked and TWRP installed.
The issue with the phone not being recognized may be due to incorrect drivers. I had no issue with this because I installed the official driver package from Motorola. It is available in their website in the developer section. I don't have the URL right now.
Hopefully this helps, for me CM13 Official has been an a stable fresh start for this old device.

Categories

Resources