Hey lovely ladies and gents,
So here is the situation: I have an LG Optimus l70 MS323, which until yesterday was with a stock ROM. I banged my head against the wall, trying desperately to follow a guide and root it, along with trying to unlock the bootloader until I watched a video (in Spanish. Thank you high school spanish!) which used flashify to flash a CWM and boot to the custom recovery. I loved it, since that meant that I would be able to finally flash an official Cyanogenmod OS. The first ROM that I flashed was cm-13.0-20160121-NIGHTLY-w5.zip, which worked and made me feel SO HAPPY (I almost yelled Eurika for the sake of historical comedy). I then went ahead and installed an Superuser-SU binary update through the CWM recovery because I wanted to keep on having root. Then I installed a nano gapps package for ARM, Android 6.0 with some minor complications (mostly the "Setup Wizard" crashing every 2 seconds). I rewiped and reinstalled Cyanogenmod through CWM, flashed gapps on the same go, and made a little backup through the recovery menu. I booted up successfully to be met with that buttery-smooth GUI of Marshmallow (ugh, so good.) I decided to go ahead and fetch some apps from the Play Store, such as Messenger and ROM manager. I saw that the Cyanogenmod Update Center had pushed out a notification that the newest nightly snapshot is already downloaded and decided "Meh. What new features have been added? Let's reboot and reinstall." At that point it was 4:40am (keep in mind that I've been trying to get the goddamn phone to cooperate since ~10pm) and I noticed that the boot sequence takes up a lot longer and told myself "It's probably taking a bit longer than usual, it's normal." I put the phone next to my head, hoping that it's going to be ready to use in the morning.
Fast forward to 8:07 am. Bootloader is still going, phone is so hot it can cook an egg.
GNAAAAAAAAAAAAAAAAAAAHHHH. WHY YOU GOTTA DO DIS TO ME PHONE?!??! WHY!?!
SO, the CURRENT situation:
1. Whenever I press the power button, it starts off normally. According to my definition of bootloop, it's stuck in a bootloop.
After hours of staring that goddamn cyanogenmod mascot do you realize that it's going to boot itself into the booting oblivion.
2. I don't have access to CWM. I have tried holding down the power buttons with godknowswhat combinations (I like to call them the Naruto Jutsu of pure despair). Maybe I should hold the buttons for 2 milliseconds longer and it might work. *Sigh*
3. I don't think that I can use fastbood or adb. My computer doesn't see the phone. (GNAAHHAHASDJFLSKDHFSLJHLKJ.)
4. I am totally clueless about what I should do or try. I've basically softbricked my phone and don't know how to unbrick it.
So, now that you see that saying that I'm frustrated is truly an understatement, what do you suggest I do?
In advance, I'd like to thank you SO MUCH for even giving a sh!t about my problem.
Other misc info: I have a 32GB SD card on which I have all the different tools I have used throughout this journey.
I am willing to have it back on stock ROM. My biggest goal is to somehow boot into CWM recovery. From there on, I will be able to deal with it. Until I come back to this forum, begging for mercy.
Have u tried using LG suite or LGUP u need to go to LG 's firmware page I'm not sure about this phone but it worked w my k7 about 100 times also helped unlock it. Check out the LG k7 forum lots of guys on there that use the lgup program and can help
Welp,
I've gone & done it again. My 2nd z3v came from Amazon a few days ago, refurbished, like new. Got the 200GB card for it, went to Verizon & got the SIM, swapped it with my work phone (iPhone 4s) line.
(Now I have 2. But the 1st one was replaced for being in this same situation.)
Got home, swapped the phones back cause I really still wasn't sure I wanted to mess up this z3v with my job (landscaping = lots of dirt).
It had 4.4.4, and I let it update to the latest two part Lollipop to see what the hubbub was about (nothing).
Decided I wanted to make it basically a clone of my primary z3v, so I rooted from the update directly using GigaSPXs guide.
Successful rooted 509 achieved, but with one problem; it kept telling me I had no space left, even though the internal SD had 21 GB left. Peculiar.
Made a recovery file on my #1 z3v's SD. Copied everything from #1 SD to #2 SD, and attempted to "clone" #2 z3v by installing that latest zip copied from z3v #1, but Recovery kept saying "No File Found".
Checked all 5 recovery points I had on there, and each said the same thing. Checked other things on the SD card, and it showed them, but when I tried to open them, it said "No File Found".
Mounting problem? Made sure everything was mounted, etc. Still, same problem.
Tried wiping Dalvik 3 times, but also accidentally wiped System Cache.
Now it sticks at the SONY Xperia logo. I can get to the Sony Recovery options, but Factory Reset doesn't do anything.
Was it System Cache wipe that killed it, and can anything be done?
This time, I took some notes as I went. I was confident, but I've done this before (bricked), so I decided to list what I did as I went along. I highly recommend everyone take notes for when they screw up. LOL!
AddictedToGlass said:
Welp,
I've gone & done it again. My 2nd z3v came from Amazon a few days ago, refurbished, like new. Got the 200GB card for it, went to Verizon & got the SIM, swapped it with my work phone (iPhone 4s) line.
(Now I have 2. But the 1st one was replaced for being in this same situation.)
Got home, swapped the phones back cause I really still wasn't sure I wanted to mess up this z3v with my job (landscaping = lots of dirt).
It had 4.4.4, and I let it update to the latest two part Lollipop to see what the hubbub was about (nothing).
Decided I wanted to make it basically a clone of my primary z3v, so I rooted from the update directly using GigaSPXs guide.
Successful rooted 509 achieved, but with one problem; it kept telling me I had no space left, even though the internal SD had 21 GB left. Peculiar.
Made a recovery file on my #1 z3v's SD. Copied everything from #1 SD to #2 SD, and attempted to "clone" #2 z3v by installing that latest zip copied from z3v #1, but Recovery kept saying "No File Found".
Checked all 5 recovery points I had on there, and each said the same thing. Checked other things on the SD card, and it showed them, but when I tried to open them, it said "No File Found".
Mounting problem? Made sure everything was mounted, etc. Still, same problem.
Tried wiping Dalvik 3 times, but also accidentally wiped System Cache.
Now it sticks at the SONY Xperia logo. I can get to the Sony Recovery options, but Factory Reset doesn't do anything.
Was it System Cache wipe that killed it, and can anything be done?
This time, I took some notes as I went. I was confident, but I've done this before (bricked), so I decided to list what I did as I went along. I highly recommend everyone take notes for when they screw up. LOL!
Click to expand...
Click to collapse
Use Flashtool to flash it back to 4.4.4. After that, don't try to do your attempt again. They're two separate devices and they are both uniquely different internally.
OK, how do I use flashtool? The PC doesn't recognize the phone as anything hooked up to it. Flashtool doesn't recognize it's there.
AddictedToGlass said:
OK, how do I use flashtool? The PC doesn't recognize the phone as anything hooked up to it. Flashtool doesn't recognize it's there.
Click to expand...
Click to collapse
IIRC, hold down the down (or up) button and hook the phone to the computer. I think it should trigger recognition from there.
GigaSPX said:
IIRC, hold down the down (or up) button and hook the phone to the computer. I think it should trigger recognition from there.
Click to expand...
Click to collapse
If that doesn't work and you have connected your phone to your computer before try removing all related Sony drivers from the computer. If you are OK with registry edits you could look for any instances of your phone there too.
Komet1 said:
If that doesn't work and you have connected your phone to your computer before try removing all related Sony drivers from the computer. If you are OK with registry edits you could look for any instances of your phone there too.
Click to expand...
Click to collapse
Don't I need the drivers installed?
Yes,, reinstall them preferably from outside your computer. You are wanting the drivers on your computer to be overwritten by fresh drivers, even if they have the same version numbers. You want the computer to "think" this is the first time the phone has ever been connected to it.
Where do I get th drivers for re-installation?
AddictedToGlass said:
Where do I get th drivers for re-installation?
Click to expand...
Click to collapse
Try this. If you do take this route don't be discouraged if it doesn't work the first time. I have had something similar happen and on occasion it has taken a few tries. Windows doesn't like to let go of drivers that are already installed.
Xperia Z3 drivers
"Phone driver for Xperia Z3 (D6603, D6616, D6653, D6643, SOL26, D6708, SO-01G, and 401SO) (Microsoft Windows™ XP 32bit/64bit and later). Use drivers for debugging, or when erased from phone."
DLed the replacement drivers, but Flashtool isn't recognizing the z3v. I know I'm doing something wrong because it isn't recognizing my other (functioning) z3v, either.
So I Googled driver installation on Windows 8.1 because I remembered that it won't allow unsigned drivers without manual installation, and I needed a refresher course for all the steps. I am uncertain I successfully removed all of the previous ones, though. What I did find out, but did not know, was that putting 8.1 into that mode (where it'll install unsigned drivers) is a temporary situation. According to a poster on a blog (for whatever that's worth...), once the PC is restarted, it comes out of that "test mode", and unsigned drivers no longer work again. I usually keep the PC on, but it has restarted since I last messed with Flashtool.
Obviously I need to figure out where I'm going wrong on this to even begin work on the phone. (I miss XP.)
Details about the z3v behavior:
The screen is stuck on the SONY XPERIA logo.
Pressing the power button by itself has no effect, no matter how long I hold it.
Pressing the power button with the volume down will power it off, but it just powers back on by itself.
Pressing the power button and holding both the power button and the volume down while it cycles back on gets me into the Android Recovery menu.
From Recovery;
Selecting "Power Down" USUALLY powers it down, but sometimes it immediately restarts.
Selecting "Factory Reset" cycles it through the logo and into an attempt (Droid animation with blue bar rolling) for about 5-6 seconds, and then it restarts into the SONY XPERIA logo again.
Selecting "Safe Mode" simply restarts it the same way.
Selecting "Continue Power Up" obviously does the same.
All that is while not tethered to the PC. NO color LED comes on, except for an occasional orange while it's hooked to the PC.
Got a couple of suggestions about the PC connection:
Try a different USB cable.
Have you looked in Device Manager and removed any reference to the Sony there as well?
Here is a blog post about an Xperia S that wouldn't connect, the steps should be the same:
Connect the phone via USB and go to the Device manager on the computer. Check if you can locate the phone or any Unknown/New device that could be the phone or if you perhaps see the phone as a device. Right click it and select to uninstall.
Still in Device manager open the list for USB controllers (Universal Serial Bus Controllers) and right click each one of these controllers and select to uninstall.
When all of this is done reboot your computer and before connecting your phone again repeat step 2.
You should of course not have to do this every time you connect your phone to your computer but hopefully this could remove any error causing your phone not to connect properly.
I'M BACK!!!
And here's a lesson from one noob to all others; Never overlook the simplest things.
Komet1, your suggestion of trying a different cable struck me as desperate, but when I looked at what I had been using, I realized it was the cheap cable Amazon sent with the phone (It didn't come with a Sony charger and cable, just a crappy generic set).
I swapped cables and viola!, I now have 4.4.4 back.
I'll not be making the stupid mistake of swapping restores from one phone to another again.
Thanks all!
Important lessons for beginners...
Take notes. I'm glad I did this time because last time I bricked I couldn't remember what I had done to brick it, or what I had tried to unbrick it. It helps when you can provide detailed info, otherwise it becomes too frustrating for those who can help. It can also help keep you from panicking and going in circles.
AddictedToGlass said:
I'M BACK!!!
And here's a lesson from one noob to all others; Never overlook the simplest things...
Thanks all!
Important lessons for beginners...
Take notes. I'm glad I did this time because last time I bricked I couldn't remember what I had done to brick it, or what I had tried to unbrick it. It helps when you can provide detailed info, otherwise it becomes too frustrating for those who can help. It can also help keep you from panicking and going in circles.
Click to expand...
Click to collapse
Awesome! Been there, done that with the bricking. It's a wonderful feeling when you watch the phone respond and realize you just solved the problem.
Sure is!
DOH!!!!
Hello
I need some advice and help if someone can.
My LG V10 was rooted and on latest Eliminators room. It was working perfectly and few days ago while ending the phone call it just switched off.
Since then i have been trying to bring it back to life but without any success .
I can boot it to fastboot but no commands are accepted in fastboot mode, no download mode . It only goes to logo and the information that software can not be checked , further from there it goes nowhere . Since i am mac user , i installed VM of Win 7 and only thing it detects is Qualcom 9008......
Please some advice and help what is possible to do.
In fastboot mode i can not do anything.......
Sent from my iPhone using Tapatalk
This is the exact thing that happened to me last night too. I was wondering if my phone pushed the latest update on accident or something to cause it.
Another thread in the Q & A Section has reports of this happening and maybe being a hardware issue.
I plan on trying to do a full restore back to stock tonight when I get home from work to see if I can bring it back to life. I also read somewhere that you need to have the latest binary for fastboot to work.
The few minutes I messed around with it last night, my fastboot was sending but not writing. I'll keep you posted it I have any success tonight after work.
Side note the thread I mentioned above the S/N for the phones having issues started with 510...
Also, I can get mine to boot into recovery but once I try to erase or install it freezes and boot loops again.
I will play with it from tomorrow again. From yesterday i have gave it to one service center but they have not succeeded to do anything. I have succeeded in one moment to get to download mode which laster only about 2 seconds, not enough even to connect it to lg up, suspecting tht it is maybe something because of VM that doesn't' discover phone complerely. Tomorrow morning i shall pick it up and during next few days i shall try again, if i succeed to find a solution it would be good. I was also planing to do complete factory back up to stock last version. But...
Sent from my iPhone using Tapatalk
bildo said:
This is the exact thing that happened to me last night too. I was wondering if my phone pushed the latest update on accident or something to cause it.
Another thread in the Q & A Section has reports of this happening and maybe being a hardware issue.
I plan on trying to do a full restore back to stock tonight when I get home from work to see if I can bring it back to life. I also read somewhere that you need to have the latest binary for fastboot to work.
The few minutes I messed around with it last night, my fastboot was sending but not writing. I'll keep you posted it I have any success tonight after work.
Side note the thread I mentioned above the S/N for the phones having issues started with 510...
Also, I can get mine to boot into recovery but once I try to erase or install it freezes and boot loops again.
Click to expand...
Click to collapse
I have the same problem with my v10 do you found a solution ?
No. I bought a new phone and my v10 is now a paperweight. I have not really tried too fix either. Jumped on project fi and got a got a 5x on the cheap. Couldn't be happier.
I've had luck flashing my LG from within a virtual machine, running on top of Linux Mint. I tried both VMware Workstation and VirtualBox. Just make sure to install the guest additions within VMware, or the extension pack within VirtualBox. Also download the LG driver and install that inside the VM too. Each VM software may have settings relating to sharing a real USB port with the VM, make sure you look into that and enable the relevant options. Otherwise the VM may not detect the device.
On the other hand, my v10 isn't hardbricked, I'm just going to hold onto it as long as possible until it goes belly-up. Which it will probably do sooner rather than later, if the issues I've had are any indication. If you're only seeing Qualcomm 9008, fastboot not responding to any commands, and no download mode, this def sounds like a hardbrick. If you're still under warranty I would recommend getting it replaced by LG. If you have insurance then cash it in.
This is the 3rd v10 I've had, so far I've done 2 exchanges if I remember correctly. These phones are definitely susceptible to big issues. Like the now famous LG bootloop scenario.
Hope you get this figured out!
I have hard-bricked my N10 5G and it shows up as 900E, but most online stuff talks about 9008 mode.
MSMDownloadTool V4.0 doesn't see the phone, I think because it expects 9008.
How do I get my phone back to 9008?
Or if not 9008, then how do I fix this?
I have downloaded qfil.exe and qpst tool, but I haven't been able to find any binaries to install.
What images do I need, where do I get them, and how do I return back to normal OxygenOS, or even a basic Android?
(I originally got here because Oxygen kept using up storage space for "system". I succeeded a few months ago in resetting the device back to normal, but then the storage got used up again. I totally forgot what I did last time, so this time I totally f*ed it up. I tried Android 12.1, but it kept crashing with modem error, then wouldn't start. Then I managed to get Android 11 on there, and it was more stable, but modem still kept crashing. After that, various ROMs, recoveries, TWRPs, Magisk, etc., and I really don't know the landscape that well. I got to some point of doing a flash_all.bat from fastboot for some Oxygen image, and it stopped part way. The phone now only shows up as 900E.)