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!!!!
Related
I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
elead1 said:
I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
Click to expand...
Click to collapse
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
VeNuM said:
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
Click to expand...
Click to collapse
I will post back with results. Not like I've got much else to do with it right now, eh? :laugh:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
Damn. Well I've been there done that too...
send it to htc.
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
i had the same problem but my situation was that i downgraded the radio while s-on. I was in the same situation that you are right now. i did everything i could but nothing worked so my last hope was sending it to HTC and say that i lefted updating the software while sleeping and when i woke up it was like that. i sended they didnt even ask, i got it back like new . :laugh:
My RAZR MAXX has been working just fine, even after travel to Germany (connected to Vodaphone just fine). I have the phone in the Bahamas and it has a Batelco SIM in it. It handled voice calls as expected. Yesterday, I bought a data access package as my original package had expire. Installing the package required having a Batelco rep enter the needed APN data. After that, the phone worked well for 24+ hours with the data and voice networks. The wheels fell off when I powered down the phone.
On powering the phone back up, it does the opening red Motorola logo, the opening animatation with full audio, and then goes into the "dancing sparks" animation. And that's where it stays. It's been running in this mode for over 30 minutes since I last tried to power the phone down to pull the SIM and SD card ([/shug] might as well try that). Actually, at this point, the phone seems to be reluctant to power down (holding the upper button down may or may not lead to powering down and even if that happens, the phone just starts to reboot instead of staying dark). Soft reset only stops the "sparky" animation and then the phone reverts to the "M" logo and animation again and again and again and...
The OS is an OTA Jelly Bean supplied by Verizon (can read the detail rev numbers of course). The only recent changes I can point to are some pushed app updates (Firefox, Facebook, and I forget the third) and the entry of the Batelco APN.
So the question is this: is there any way to give the phone a good swift kick to break this cycle. If not, how do I get the OEM ROM for this thing?
Please keep in mind that I'm in the Bahamas, where surface mail can take 4-5 weeks to arrive. Plan B is to have stuff air freighted in (costs are astonomical and Bahamian customs may want a piece of the action). Bottom line: external hardware is almost impossible here.
In doing more reading on the problem, I found out about getting into the boot menu (power down, hold power, vol up, and vol down). I can get to the menu. I selected recovery and... nada. After a while the phone just boots yet again. Either I don't know how to enforce the recovery choice or the phone is really boogered. BTW, the phone does accept charging. That is, it was dead (blank screen) after looping overnight. Plug in the charger and back to looping, which continues with the charger not plugged in.
Nevermind - I got to recover mode. Helps to read the instructions fully...
You can try using this: http://www.droidrzr.com/index.php/t...ndows-mac-linux-all-in-one/page-9#entry251858
But that would delete all your apps and stuff. but it also might fix your problem.
The fun just won't stop. I wiped the cache and rebooted. No change. I went for the full FDR and rebooted. No change. This is one sick puppy...
Gus194 said:
You can try using this [deleted]
But that would delete all your apps and stuff. but it also might fix your problem.
Click to expand...
Click to collapse
Went there, tried that, and couldn't down load the file to successfully. I tried two mirrors and nothing (7zip said "not archives"). I also tried the file from RootJunk's download page (I'd post the URL but it's being blocked while I'm a noob).
That tanked, too.
I keep seeing references to an ADB Motorola JB ROM but can't seem to find it via Google. The idea is to just stuff the proper ROM in and get on with it. since all the user data was smoked in trying to reset the phone, losing user data is the least of my concerns.
Suggestions on this avenue of approach?
Have you tried downloading here? http://batakang.com/dr_utility.php
Gus194 said:
Have you tried downloading here? http://batakang.com/dr_utility.php
Click to expand...
Click to collapse
Thanks - I'll check it out. I finally(!!!) successfully downloaded DROID_RAZR_Utility_Jellybean_XT912_WinMacLin from RootJunky and will be trying it ASAP.
Great! Tell me how it goes?
Gus194 said:
Great! Tell me how it goes?
Click to expand...
Click to collapse
So far, it goes down the tubes. I successfully expanded the file onto the admin desktop. The next step is to get the correct ADB drivers installed. That tanks with an error message, from the installer, about a network failure to read the .msi file with the updates. Network failure??? The file's on the machine and I'm in admin, not user, space. ARGHHH!!!
Try getting the Drivers from here: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Gus194 said:
Try getting the Drivers from here: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Click to expand...
Click to collapse
I got past the driver problem by using the installer to remove the existing drivers (no clues as to their rev. number but they went away) and then install the new drivers. I've actually gotten to the point reloading the phone but... now the darn thing says I have no SIM installed. In fact I have two, a Batelco SIM and a VZW SIM. I tried both and all the darn phone says is "I can find no SIM". In fact, I used the Batelcom SIM in a RAZR flip phone to verify all is well with the SIM. And it is. But the RAZR MAXX won't see it. GNGHHH!!!
RBEmerson said:
So far, it goes down the tubes. I successfully expanded the file onto the admin desktop. The next step is to get the correct ADB drivers installed. That tanks with an error message, from the installer, about a network failure to read the .msi file with the updates. Network failure??? The file's on the machine and I'm in admin, not user, space. ARGHHH!!!
Click to expand...
Click to collapse
The driver issue was fixed by removing the existing driver (no idea which rev. was present in the PC but it went away as it should) and installing the new driver. Why the network message showed up is unclear but it didn't happen after removing the existing driver.
DROID_RAZR_Utility_Jellybean_XT912_WinMacLin took two tries to run properly but it did run. The boot loop is stopped at last. But...
Now the phone reports it can't find the SIM. I have two SIM's - a VZW SIM (worked in the US and Germany) and a Batelco SIM. The Batelco SIM worked prior to the failure and it still works in a RAZR flip phone.
The boot process runs as expected and ends in the starting screen for the setup process. At this point the battery and signal (none - of course) icons show up. A couple of seconds later, the SIM icon shows up with a slashed red circle on it. Advancing to the next screen gives a "SIM not found" and the only option is to power down.
Popping the SIM out and in does nothing. Trying to boot to safe mode does nothing. ARGHHH!!!
Try going into recovery and factory reset.
Or I could try taking my head out of my a**. The SIM was in the wrong side up. Something I cleverly repeated over and over. [/ rolled eyes]
At this point I'm back to what appears to be a factory original RAZR MAXX with JB.
Great thanks for all the help on this project!!
Good to hear!
At the moment I'm using EasyTether to connect with the interwebs and post this note. Case closed, I'd say. )
Before the incident, I had root, no unlocked bootloader, stock JB, v20h.
What had happened was I was trying the Font Installer app in th Play Store because of the added customization that would have been nice.
I found a cool font, and I backed up my current fonts and then pressed install. SuperSU asked for permissions like normal and then my phone restarted.
Then it was so that my phone was stuck at the T-Mobile boot animation after the LG Logo. For about 15 minutes. This is where I believed something was starting to go very wrong. After contemplating for a few extra minutes, I decided to just take out the battery and restart. Same outcome. I thought of all the things that were on the phone thus far because I had just gotten it recently, and decided that it wouldn't hurt me to just do a hard reset by pressing home + vol down + power. Everything went smoothly. Except for the fact that even after I did that, it was leaving me at the T-Mobile screen.
I decided to look on the forums for development and tried to do the unbrick method, to no avail after about 3 hours now. I used the LG User Support Tool and since I hadn't updated to V20f, I decided to do that to see if it would solve my problem. It still didn't, and I'll be honest, I'm a little upset just typing this right now.
I also tried the Upgrade Recovery option and it warmed my heart to see that the process was actually starting. But right at the screen where it says that it is supposed to be downloading something, it freezes up and nothing happens no matter how long I wait. I saw somewhere that it should be a glowing red bar, but I do not see that anywhere, it is just frozen, saying Time Elapsed: 00:12. And before anyone asks, yes, I ran absolutely everything as an administrator.
Is there any possible way to bring this phone back? Any help would be immensely appreciated. Thank you in advanced.
anticlotto_ said:
Before the incident, I had root, no unlocked bootloader, stock JB, v20h.
What had happened was I was trying the Font Installer app in th Play Store because of the added customization that would have been nice.
I found a cool font, and I backed up my current fonts and then pressed install. SuperSU asked for permissions like normal and then my phone restarted.
Then it was so that my phone was stuck at the T-Mobile boot animation after the LG Logo. For about 15 minutes. This is where I believed something was starting to go very wrong. After contemplating for a few extra minutes, I decided to just take out the battery and restart. Same outcome. I thought of all the things that were on the phone thus far because I had just gotten it recently, and decided that it wouldn't hurt me to just do a hard reset by pressing home + vol down + power. Everything went smoothly. Except for the fact that even after I did that, it was leaving me at the T-Mobile screen.
I decided to look on the forums for development and tried to do the unbrick method, to no avail after about 3 hours now. I used the LG User Support Tool and since I hadn't updated to V20f, I decided to do that to see if it would solve my problem. It still didn't, and I'll be honest, I'm a little upset just typing this right now.
I also tried the Upgrade Recovery option and it warmed my heart to see that the process was actually starting. But right at the screen where it says that it is supposed to be downloading something, it freezes up and nothing happens no matter how long I wait. I saw somewhere that it should be a glowing red bar, but I do not see that anywhere, it is just frozen, saying Time Elapsed: 00:12. And before anyone asks, yes, I ran absolutely everything as an administrator.
Is there any possible way to bring this phone back? Any help would be immensely appreciated. Thank you in advanced.
Click to expand...
Click to collapse
did you hard reset? then turn off your phone disconnect the battery, connect to the pc holding the volume up button? then try the Update Recovery?
i would just go through that process over and over until it works, theres not really a way to brick this phone i've heard...
CROSSFREEZE said:
did you hard reset? then turn off your phone disconnect the battery, connect to the pc holding the volume up button? then try the Update Recovery?
i would just go through that process over and over until it works, theres not really a way to brick this phone i've heard...
Click to expand...
Click to collapse
Thank you for your reply! I have tried hard resetting multiple times, but I had removed some bloatware apps (I will quarantine them next time instead because I don't wanna go through this ever again) and I have tried the kdz method to only be stuck at 15% every time when I followed instructions to the pixel. I have tried to do it on windows 7 and windows 8. I have also tried the fastboot method by lelus, and that manages to "work" but I am still stuck at the tmobile boot screen afterwards. I have gotten the hang of the process of getting into the fastboot, but what do I do from there? I chose to flash ics xloader and uboot, but the process goes by so fast, I'm not even sure it is doing anything. The LG Tool has really gotten me nowhere, it just gives me a lovely error and then cannot continue the upgrade recovery process.
It said somewhere that after I flash through the fastboot I then have to try the kdz method, so I am going to do that now and see if it works. I don't know if there would be a difference between flashing a jb kdz or an ics kdz, but I will just do ics to be on the safe side.
I am quite happy to say that flashing the ics kdz was successful, and my phone is now up and running.
My p769BK is stuck on the LG screen. /: months
Sent from my LG-MS770 using xda app-developers app
im terrible with fastboot, i used the unlock the bootloader for noobs with an offline flash.
heres what i did to get out of bootloops....
alright, this is all from memory but the offline flash didnt work as well for me when stuck in weird bootloops.
Step one-going back to online flash---->
A---
the easiest way i found was to go to C:/windows/system32/drivers/ect/hosts
right click>open with notepad
there should be two lines at the bottom
"127.0.0.1 csmg.lgmobile.com
127.0.0.1 csmgdl.lgmobile.com"
i would cut them out and paste them in a text doc in the same folder for reference later...
but either way you should remove them from the hosts file and save
B----
Make sure your small server is closed! once you minimize it it should go down to your status bar (shttps)
Step two-LGMS---->
make sure you have LG mobile support installed or install it.
open lg mobile support
install needed drivers for your phone
power your phone off/remove the battery
put battery back in
connect it to your computer holding down the volume up button
S/W UPDATE mode should pop up, if it doesn't preform and hardreset and try again til it works (it will)
then in the top right corner there should be a button or two click them both until you see
"restore update" or Update restore or something to that effect
select that
and let it ride man
i got my phone ****ed many times and just had to keep redoing this until it worked. if your bootloader is truely unlocked you can probably go through all that again and get CM10 working, i did but im still working through kinks.....
GOOD LUCK feel free to ask any more Q's about this process if you run into any problems
Alright. I need some advice one last time, I swear... after this I'm not going to try to do anything.
Phone worked quite well for 2 days. I was enjoying this rom quite a bit. I decided to change the DPI down to 560. I saw that some others in this thread had done so quite easily... so I used this app to change it. Made the change to 560, granted supersu permission and rebooted. Only problem is that... the phone has yet to turn back on. At the moment the only thing I can get it to do is give me a screen that shows a large white empty battery with a cable leading up to it and a hazard exclamation mark in the bottom right when I am trying to put it in download mode. I have tried on multiple computers to restore back to stock following these directions. The best that happens is my computer recognizes an unrecognized device. No luck.
I would love to change the buildprop back or anything, but not even adb recognizes the device.
Otherwise, nothing. I can't get into recovery. I can't get the phone to start at all. All black screen. I can't get any reaction out of it. Any advice would be helpful, I'm on hour two of this. I realize that this is most likely not a problem with the rom, but wanted to see if anyone else had an issue and has advice/let anyone else who's thinking of changing the DPI and shared my troubles reconsider.
Thanks again!
The empty the battery logo is because the phone is dead try charging it for like 30 mins. Also it seems that app you used is 3 years old so it does not support lollipop or even kitkat. After charging it try get it into recovery and restore a backup. If you don't have a backup try wiping your data and cache.
1619415 said:
The empty the battery logo is because the phone is dead try charging it for like 30 mins. Also it seems that app you used is 3 years old so it does not support lollipop or even kitkat. After charging it try get it into recovery and restore a backup. If you don't have a backup try wiping your data and cache.
Click to expand...
Click to collapse
Thanks for the reply!
That emblem only shows up when the battery is removed and I'm trying to put the phone in download mode. So it makes sense. Any other ideas? The battery that I'm using is about 80% full. I still can't find a way to recovery mode.
What other information can I provide to help you out?
Well when your in download mode it does not take any commands can you get the lg powered by android screen? Or just nothing happens? If nothing at all happenes it is most likly bricked. If it boots to the lg screen it is most likly soft bricked.
Bricked- Phone is dead and very very hard to fix if there is a fix
Soft Brick- No OS so you have to reinstall a rom could also be, because of apps.
1619415 said:
Well when your in download mode it does not take any commands can you get the lg powered by android screen? Or just nothing happens? If nothing at all happenes it is most likly bricked. If it boots to the lg screen it is most likly soft bricked.
Bricked- Phone is dead and very very hard to fix if there is a fix
Soft Brick- No OS so you have to reinstall a rom could also be, because of apps.
Click to expand...
Click to collapse
No screen. For anything (other than described).
This is exactly what I was afraid of, but my phone has always been odd. This dead battery screen has always shown up in download mode... even when my phone worked, I've never had the firmware update screen. Which has always been weird to me.
However, the only time my phone shows anything is with the dead battery screen. During such it will show up as an unrecognized device when attached to a computer, again... it's always done this. I was just curious if there was something else or a suggestion that someone more experienced then myself might have.
No that I read it, it sounds like there maybe a very slim chance of getting your device to work. If you mange to get some drivers for the unreconized device driver you maybe able to send adb and fastboot commands. I found this one tool (will limk below) that is call cydia impactor I found in one of rootjunky's toolkit files. I used this one function that was able to make drivers for my sony smartwatch 3 and phone. I will link for the direct download make sure to extract the zip. Inside of the zip you will find another zip called "Impactor_0.9.14.zip" make sure to extract it to it's own folder. If you want you can delete the first folder juat save the impactor folder. Then run the program called "Impactor" can connect your phone to the computer and click on the tab called "USB" then click the button called "Driver Scan". Follow any on screen instructions. It should now generate a driver for your phone if all went well and it will be reconized. Then you should be able to run adb reboot recovery or fastboot reboot-bootloader. The fact that your computer is even seeing the phone tells me that it has so hope of being fixed because your computer see's it. Your device might be in a bootloop of some sort. You may just have no os installed and it may have just glitched.
Download: http://rootjunkysdl.com/getdownload.php?file=Tegra Note 7/ADB root.zip (will immeditly download it)
Worst case scenario, you may try this, or at least read it for general info. I don't think you'll have to go this far though
http://forum.xda-developers.com/showthread.php?t=2582142
[FIX] NO Recovery mode, No download mode, after OTA on rooted LG G2
i changed my dpi once and it bootlooped on me. i was lucky enough to get into recovery and then i restored the data partition from an older nandroid.
i agree with 16. it does sound like the drivers may not be loaded up properly if your computer recognizes a device. have you tried the official lg drivers?
What system are you guys running?
Well, I've found out that for whatever reason... on my phone I have to take out the battery for a period of ~5-10 mins on any change DPI, system rom update, anything. Otherwise, my phone will not turn on. So if someone else find this, give it a try.
Hello, XDA forumites!
I've been lurking and reading a lot of threads in here for years, using all your knowledge to fix various phones. Today though is the day I first post and it is for good reason. I'm a guy who loves challenges but this one is making me go insane. I've spend the last two days looking for ways to fix this phone but NOTHING works.
So, the deal is that this phone turns on fine. It boots, it gets to the lockscreen and... it restarts itself. Again and again and again until the battery is removed. To fix it, I've tried the following:
- recovering/updating it through the Huawei official "firmware" supplied by the site: you put the file they supply on an SD card, inside a folder named "dload" and then hold vol up and down along with the power button to make the phone install the contents of that file, named UPDATE.APP. Needless to say it doesn't work. A menu appears with the options reboot system now, apply update from sdcard, apply update from cache, wipe/data factory reset, wipe cache partition and calibrate touch screen. Trying to apply update from sdcard only lets me browse the SD looking for the file but doesn't actually see the file itself, it just shows the dload folder empty (I've tried with 4 different versions of the file compatible with phones from Central America which is where I am ATM). Also, the factory reset does nothing (although it shows it wipes data), everything's there when I start the phone up.
- flashing it with SD Flash Tool: apparently partially works with the last version 3 of the tool (although nothing changes) while version 5 of SDFT doesn't even see the phone (drivers are correctly installed, adb detects it, more on this later). A problem that arises is that I can't flash the SEC_RO package on it (don't know why) nor the PRELOADER (not that one is supposed to normally, but I feel like it would fix my problem in this case).
- cleaning it in safe mode: booting it in safe mode made me notice that it was an app pretending to be Whatsapp causing the restarts (or, perhaps, the one that loads immediately after? The phone has several malware apps). In safe mode those apps didn't load so the phone stayed on. So I cleaned everything, activated USB debugging (for later use in adb mode) and restarted only to find everything as it was before I did the cleanup. I tried rooting it in safemode, cleaning again, still reverts to full "normality" after the restart. Same results when using the phone's proprietary SW HiSuite.
- installing CWM's recovery img through adb+fastboot: I installed all the possible - necessary or unnecessary - drivers (Google's, phone's official ones, PDANet ones) and the phone is correctly detected by the PC (visible in Device Manager) and is visible through the adb devices command. But as soon as I adb reboot bootloader it to fastload the CWM image, the phone stops being seen correctly and doesn't show up in fastboot devices, only showing "NEW: SAFE OLD:RISK" on a black background on its screen.
So, to recap: the phone restarts because of a malware at startup, reverts any and all changes made to it in safemode, doesn't wipe from the recovery menu, apparently has a corrupted bootloader and is impervious to normal flashing SW... Anyone got any more ideas on how to deal with it? The only option left that comes to mind is to fix it directly by flashing the internal memory using JTAG/RIFF but I don't have the equipment (nor do I intend to buy it).
Bump, hoping for some help...
One more bump, still stuck
First, don't get happy: I have no answer to your problem. Sorry. But I have a similar one. I was running a very efficient, rooted, stock ROM G730-U251, until I decided to switch from 'Ninjamorph Free' to 'Pro'. I've been made a lot of changes with Free version for a long time without any issues at all. Then, one day, when making a small, useless change with 'Pro', something went wrong; phone just rebooted and refused to get past bootanimation. With no custom recovery on hand, only solution for this is to flash ROM. Though I had no problem finding the official, stock UPDATE.APP, which flashed smoothly from the SD card to be fair. Mess came when, once flashed, I decided to install OTA update available, which I overlooked since phone was new. Big, BIG mistake. It just came with more restrictions than ever, letting me root, yes, but this time with 'Kingroot' only (as stock, I had no problem rooting with Framaroot) but soon discovered I wasn't able to use 'Super-Sume', 'Adaway' and 'Link2SD', because some system parts now CAN'T be mounted rw, even using ES File Explorer. To avoid any complication, decided to reflash UPDATE.APP just as I did before. No way I can do it this time. Don't know exactly why, but assuming it's not possible to update with a previous version of the 'same' ROM. So now I'm looking for a flashable stock ROM in order to try SP flash tool. Phone is in working state right now (not as yours), but I just don't feel comfortable with it as it is right now, because those apps are always the main reason why I actually root every single of my devices and simply because I like to have my stuff as my own way as possible. You know, truth is there's not much of an advanced support for this phone, not even here at XDA and I think that's because this is a Latin America version. We owners of G730-U251 devices are pretty much on our own, to say the least. Whatever, if the whole deal gets more complicated than it is, there's a strong possibility for me to end up getting rid of this phone. Sad. Really. It's actually a good phone. Though it WAS better...