All,
I've been following posts on XDA since my original droid incredible days. I've rooted and maintained two phones, never have any issues.
Recently I purchased a T-Mobile Springboard (got a crazy promotion price through my company) which ran stock TMo Honeycomb. Eager to get ICS and eager to get rid of the power-on tmobile jingle, I installed the latest S7-302u firmware update from Huawei's website. I am aware that my device is technically S7-303u, but the update worked fine and I had little-to-no bugs. I am very pleased with this tablet.
Now here where I get stupid.
A coworker of mine then tells me that he has a S7-303u update.zip file that he can give me, which I don't object to. I give him my micro SD, he places the file in the 'dload' folder with 'unlmt.cfg'. I then reconsider my predicament, and decide that I'm happy with my current firmware, even if it's not made specifically for my tablet hardware version. If it ain't broke, don't fix it.
By the evening, I forget that the update file is on my SD card.
Before going to bed, I extinguish the battery and let it power down. I then plug it in the the wall and fall asleep.
Around 3 am (3 hours later) I was woken up to my springboard rebooting. Confused, I pick it up and see that it's in some kind of boot-loop. The screen turns on, but stays black, and then immediately powers down, and restarts. This process repeats indefinitely. I hold the power button down, trying to do a hard-reboot, but it doesn't seem t work. Then, after about 5 "holding the power button down for 10 seconds", the device reboots and I am graced with the gracious Huawei MediaPad logo.
The device automatically goes into recovery mode and installs the forgotten update.zip....
Now I'm pissed, specifically because I've lost my high scores in Trainyard Express and just because I now how to re-install all my apps. It's annoying, but it's not the end of the world. Or so I thought.
I use my tablet 75% of the time for reading through the kindle app, and on this version of ICS the kindle app doesn't work! So immediately I decide to revert back to the old S7-302u update that I originally had installed, following the same steps I did to manually update the device previously.
I now cannot, for the life of me, get this thing to boot into recovery mode. The only thing I can get this device to do is get to the "Enter into fastboot mode" screen by holding the power button and the volume+ key (the one closest to the power button).
A few other symptoms:
1. The device is set to quickstart mode by default and I don't see any option to deactivate it. The only way to get the device to actually "turn off" is to choose restart to hold the power button down for a hard reboot.
2. If I hold down the power button for ten seconds, I expect the device to power down and stay down. This is not the case. It always reboots immediately. I have no way of actually fully powering this device down (not counting the quick-start power-down).
3. No charging indication. I'm not sure if this is a hardware or software issue. My device will charge, but it does not give any indication on the screen or the battery icon.
Now I'm stuck wondering what to do. Did I ruin this device? I wanted to avoid rooting it because of the loss of 4G data, but now I'm afraid that I might need root-permissions to fix whatever I messed up.
Thanks in advance for your help.
Daniel
PS. Just so you all know my experience, I've rooted and maintained a droid incredible and currently, my galaxy nexus. I however, have no programming experience what-so-ever. I'm just good at following directions (usually).
What happens if you pull the micro sd card out? It should stop the boot loop (in theory). If the install didn't go through it should boot up normally to the previous version. In settings you can turn off FastBoot.
You might have to look at the sd card on a computer and either get rid of the unlmt.cfg from the dload folder and it shouldn't try to boot to the dload folder.
eurobass said:
All,
I've been following posts on XDA since my original droid incredible days. I've rooted and maintained two phones, never have any issues.
Recently I purchased a T-Mobile Springboard (got a crazy promotion price through my company) which ran stock TMo Honeycomb. Eager to get ICS and eager to get rid of the power-on tmobile jingle, I installed the latest S7-302u firmware update from Huawei's website. I am aware that my device is technically S7-303u, but the update worked fine and I had little-to-no bugs. I am very pleased with this tablet.
Now here where I get stupid.
A coworker of mine then tells me that he has a S7-303u update.zip file that he can give me, which I don't object to. I give him my micro SD, he places the file in the 'dload' folder with 'unlmt.cfg'. I then reconsider my predicament, and decide that I'm happy with my current firmware, even if it's not made specifically for my tablet hardware version. If it ain't broke, don't fix it.
By the evening, I forget that the update file is on my SD card.
Before going to bed, I extinguish the battery and let it power down. I then plug it in the the wall and fall asleep.
Around 3 am (3 hours later) I was woken up to my springboard rebooting. Confused, I pick it up and see that it's in some kind of boot-loop. The screen turns on, but stays black, and then immediately powers down, and restarts. This process repeats indefinitely. I hold the power button down, trying to do a hard-reboot, but it doesn't seem t work. Then, after about 5 "holding the power button down for 10 seconds", the device reboots and I am graced with the gracious Huawei MediaPad logo.
The device automatically goes into recovery mode and installs the forgotten update.zip....
Now I'm pissed, specifically because I've lost my high scores in Trainyard Express and just because I now how to re-install all my apps. It's annoying, but it's not the end of the world. Or so I thought.
I use my tablet 75% of the time for reading through the kindle app, and on this version of ICS the kindle app doesn't work! So immediately I decide to revert back to the old S7-302u update that I originally had installed, following the same steps I did to manually update the device previously.
I now cannot, for the life of me, get this thing to boot into recovery mode. The only thing I can get this device to do is get to the "Enter into fastboot mode" screen by holding the power button and the volume+ key (the one closest to the power button).
A few other symptoms:
1. The device is set to quickstart mode by default and I don't see any option to deactivate it. The only way to get the device to actually "turn off" is to choose restart to hold the power button down for a hard reboot.
2. If I hold down the power button for ten seconds, I expect the device to power down and stay down. This is not the case. It always reboots immediately. I have no way of actually fully powering this device down (not counting the quick-start power-down).
3. No charging indication. I'm not sure if this is a hardware or software issue. My device will charge, but it does not give any indication on the screen or the battery icon.
Now I'm stuck wondering what to do. Did I ruin this device? I wanted to avoid rooting it because of the loss of 4G data, but now I'm afraid that I might need root-permissions to fix whatever I messed up.
Thanks in advance for your help.
Daniel
PS. Just so you all know my experience, I've rooted and maintained a droid incredible and currently, my galaxy nexus. I however, have no programming experience what-so-ever. I'm just good at following directions (usually).
Click to expand...
Click to collapse
Thanks
What is the firmware version of S7-302u are you installed in your S7-303u?
Hey, I have the springboard and did the exact thing you did, somehow the stock recovery was all messed up, best bet is to install twrp using fastbood and cm10. just follow after_silences instructions here,
http://forum.xda-developers.com/showthread.php?t=2045808
[Edit]once you change tmo stock firmware you'll lose your 4g option(there my be a fix for this now)but you will be able to text and make calls over 2g, edge2 and 3g"no need for WiFi or side app"[Edit]
Related
So, this is a two-part question. First time asking a question here, so if I'm forgetting anything, lemme know.
Got a Droid X2 in November. Pretty awesome phone, all things considered. I did, however, notice a small bug: every rare once in a while when waking my phone, the phone would wake up without turning the screen on. I could still interact with the phone normally (unlocking the phone, pressing keyboard buttons with the vibration feedback, etc.), but I wouldn't be able to see anything.
I hazarded that maybe the ROM that I was already planning on installing would fix this. Maybe the horrible and evil Verizon bloatware was doing something silly with the software side of the phone. I went ahead and rooted the phone.
Weeelll, it didn't fix it. It still fails to wake up the screen sometimes, and now it's been doing it more frequently. Sometimes, it will even show a snow-crash-filled screen. I installed the 2.3.4 SBF and took it back to Verizon, and was able to show them the bug fairly quickly. They said that I could use the warranty to get it replaced. The thing that made me pause was that the man there told me that if I sent it back and they found out I rooted it, they'd charge me the full 500$ for a new one.
My questions:
1. Does anyone else have this bug, and is there a way to fix it? I poked around the forums, and haven't seen anything like this.
2. Would flashing an SBF erase any signs of rooting the device? If I did trade in the phone in that condition, would I get hit with that 500$ charge? How would Verizon tell if a phone's ever been rooted?
-Whistle
Remove your SD card and sbf they will not know. They can not tell if you sbf it maybe a factory reset would not hurt as well. Do not put any rooted apps on it. Why did he say that did you have a custom rom or rooted apps on it at the time?
SBF brings you to out of box state...nothing will show..
After you SBF be sure to do a system recovery and wipe data and cache...
There are great tutorials in the General section here...
To enter normal recovery, power off your x2, plug your phone in to a wall charger then hit volume down and power button until you see FASTBOOT... then use volume down until Android Recovery...then hit,, volume Up...then hit both volume up and down, you will see a triangle with an exclamation point, Again hit both volume up and down at the same time and it will bring you into recovery. From there you can wipe data and cache....
Note: after SBF it is a good idea to do this to eliminate anything left astray....
Good luck
PS.it takes about twenty minutes to complete.
Dee Ex Two - See Em Seven
Yesterday I could connect as usual. Today I cannot. My Prime sees the router and shows Good or Excellent but, as soon as I press Connect the icon goes to poor and constantly tries connecting. I've rebooted the router many times and have done a Factory reset with no luck. I cannot figure what the heck happened. Any help sure appreciated.
Sent from my ADR6400L using xda app-developers app
That sucks
- unlocked?
- jb update?
- root?
- tried another router?
Had pretty much the exact same issue 2 hours ago. All I did was reboot the prime.
Sure does suck.
- unlocked? .....No. I never could get the Asus unlocker to work. I do have a serial.
- jb update?.....No haven't attempted that.
- root?.....Yes but, no CWM
- tried another router?.....I haven't. My wife's tablet, laptop and both our phones connect.
Mine jus cycles saying Obtaining IP, Authentication problem.
Weird that it says Good or Excellent signal strentgh until I try to connect. Then, it instantly goes to Poor.
Geez...
Thanks to both of you for replying.
Sure does suck.
- unlocked? .....No. I never could get the Asus unlocker to work. I do have a serial.
- jb update?.....No haven't attempted that.
- root?.....Yes but, no CWM
- tried another router?.....I haven't. My wife's tablet, laptop and both our phones connect.
Mine jus cycles saying Obtaining IP, Authentication problem.
Weird that it says Good or Excellent signal strentgh until I try to connect. Then, it instantly goes to Poor.
Geez...
Thanks to both of you for replying.
I would go ahead with the jb update... would allow a change in software with a gleaming chance of keeping root.
Yeah, that makes sense. Seems I'd have nothing to lose. Is there "1" method that folks are
using? I'll search for the instructions.
Thank you again
thenrz said:
I would go ahead with the jb update... would allow a change in software with a gleaming chance of keeping root.
Click to expand...
Click to collapse
You could try deleting the saved connection and re-creating it. Has there been a recent firmware update on the router?
"You could try deleting the saved connection and re-creating it. Has there been a recent firmware update on the router?"
You know, I've long pressed on the connect and select "Forget" but the router still shows, and
of course says "Excellent" signal. If I press again it wants my password. Been doing this cycle
over and over. Not sure if there has been an update over the past few days as it is a router/modem
from Brighthouse. Still, my phone, my wife's TF101, and phone connect.
JohnDaddyo said:
"You could try deleting the saved connection and re-creating it. Has there been a recent firmware update on the router?"
You know, I've long pressed on the connect and select "Forget" but the router still shows, and
of course says "Excellent" signal. If I press again it wants my password. Been doing this cycle
over and over. Not sure if there has been an update over the past few days as it is a router/modem
from Brighthouse. Still, my phone, my wife's TF101, and phone connect.
Click to expand...
Click to collapse
Well, this hasn't happened with my Prime, but I have seen it happen with another device - specifically one of my two Roku boxes. After a firmware update to my router, one of the two Roku's every once in a while will act just like your prime is even though every other wireless device (even the other Roku) does work. And, the one with the problems is much closer to the router than the one that works fine. Both Roku's have the same firmware even. Sometimes wireless just seems like its far from being an exact science.
I have found with my prime that it seems to help if I set it to either "g only" or "N Only" and not mixed mode. But that just seems to give me better reception - doesn't make any difference to establishing a connection in the first place.
Just getting little sicker each day. Definately not built for this. I went through every page and tab of my BHN Moto Surfboard router and could not see any where to select or change b, g, or n. I've even messaged (twice) this Josh person who has great youtube videos on how he was able to put the official Jellybean rom on his Prime. I was hoping for a fee, he would do mine but sadly, no response.
Sometimes I wonder if the heart ache is worth it all. MANY thanks to those that have tried to help.
John
Hey John,
If you didn't unlock your Prime this should work.
Download the right(US, WW, etc.) JB firmware(v.10.4.2.15) from the Asus site.
Copy it to a micro-SD card. Place it in your Prime and with the standard FileManager copy it to the root of your internal SD.
Reboot your Prime. You must see a yellow triangle in the lower right corner. That is the message to update to JB.
Hope it works.
sammytheman said:
Hey John,
If you didn't unlock your Prime this should work.
Download the right(US, WW, etc.) JB firmware(v.10.4.2.15) from the Asus site.
Copy it to a micro-SD card. Place it in your Prime and with the standard FileManager copy it to the root of your internal SD.
Reboot your Prime. You must see a yellow triangle in the lower right corner. That is the message to update to JB.
Hope it works.
Click to expand...
Click to collapse
Don't you have to unzip the initial download which yields yet another zip file and put that on your memory stick?
I will try this in the morning but, at the risk of sounding "corny" I am so grateful
for all the replies. Truly thankful
John
oops...
does the fact that I cannot get a connection on my Prime (yet?) matter?
State of the Prime
I downloaded and followed your instructions, placing the zip within the zip on my micro
and then using File Mgr, moved the zipped US_epad_user_10_4_2_15_UpdateLauncher file
to the root of my internal storage and rebooted. I did not get a yellow triangle but a blue one
in the notification area which said there is an update/. I clicked it and got the Green Droid with a
progress bar. When all that finished I ended up at an ASUS screen with the "powered by Nvidia Tegra in
the bottom right. It has been at least twenty minutes and has stayed on this screen.
I'm going to reboot again and if nothing changes, reboot holding power and vol down, followed by vol up.
a trembling,
John
update
Still stuck on the black screen. Cannot turn the device off. Full battery but maybe by tomorrow it will shut off.
JohnDaddyo said:
State of the Prime
I downloaded and followed your instructions, placing the zip within the zip on my micro
and then using File Mgr, moved the zipped US_epad_user_10_4_2_15_UpdateLauncher file
to the root of my internal storage and rebooted. I did not get a yellow triangle but a blue one
in the notification area which said there is an update/. I clicked it and got the Green Droid with a
progress bar. When all that finished I ended up at an ASUS screen with the "powered by Nvidia Tegra in
the bottom right. It has been at least twenty minutes and has stayed on this screen.
I'm going to reboot again and if nothing changes, reboot holding power and vol down, followed by vol up.
a trembling,
John
update
Still stuck on the black screen. Cannot turn the device off. Full battery but maybe by tomorrow it will shut off.
Click to expand...
Click to collapse
Maybe you can use this guide:
http://forum.xda-developers.com/showthread.php?t=1909820
My problem is that I'm stuck on a pretty much black screen. I cannot even turn off the Prime.
The only way is to drain the battery. When I hold vol down and power, it clears and vibrates
but, comes right back to that same Asus screen. It's on right now.
lame update:
I was able to turn it off by holding vol up and power.
Sucks that just being able to turn it off is a good thing.
Your not unlocked I would send it in for warranty
I'd have to wonder at this point, if I'm void. I've had it since it came out. Plus, it
seems I bricked it. Trying flash the jb rom. As I say, it will not boot.
as if...LOL
the only way I can power off is, to hold vol up after I feel it buzz/vibrate
Wondering if removing the jb zip off of the internal root would do anything?
edit:
dumb ass me obviously because I cannot boot, I can't even get to the internal root.
does anyone think a rectangular device would fly, like a Frisbee?
Yup, another NEWB having trouble looking for help. Have a rooted ATRIX 4g, (ADB/Fastroot method), but am away from home, so do not have access to the PC with drivers, ADB, etc. on it. I am running stock ROM, took the last OTA update and retained Root using Rootkeeper. I did not unlock the bootloader. Today phone started soft-boot like symptoms after I downloaded an app (Mayo Clinic PAtient App) partially installed it - app installed, but was waiting on info to login, when phone locked and I pulled battery. At this point, phone will not boot. It goes through Motorola Dual Core to Rethink possible, but then times out and reboots before loading OS. I have downloaded Motorola Drivers, I can bring up RSD, I can get to Fastboot menus. Any and all help appreciated!
Tried Fastboot Andriod Recovery, got white Triangle with yellow exclamation point. Somebody please tell me I wont have to do a factory reset. :crying: At least I have my usb battery charger with me, charging up a battery just in case.
Worst timing ever - all the relatives have my cell phone number for updates on my Wife, we are at Mayo Rochester all week.
Another odd thing - can't get the phone into safe mode.
Damn I am stubborn. After repeated efforts - and we're talking about 90 minutes here, I found by holding down the up/down vol buttons at the same time and holding them all the way through the painfully slow Rethink possible, past the long vibrate, all the way to home screen, I could get into safe mode. First time the phone still rebooted. Second time could not get past lock screens, third time I got in and uninstalled last couple programs I installed and the phone boots normally again. Hope this helps others.
Hi I'm pretty new to rooting and flashing and all that modifying my phone stuff. Firstly I'd like to thank @roirraW "edor" ehT and @LASERWOLF452 for the guides on rooting my phone which I've been trying to do for over a year, but just now finally succeeded.
Now I've run into a problem leaving my phone useless. Not sure if software or hardware problem. After I turn my phone on, which sometimes that doesn't work, it gets to LG logo then screen goes black, all buttons unresponsive including power button. I think I softbricked my phone because sometimes it gets stuck in the bootloop. (Edit: It doesn't go into the bootloop that often, mostly just blackscreens after LG logo or when I turn it on, it vibrates and that's all, logo doesn't even pop up.) Sometimes when I pull the battery out, wait a few minutes, then put it back in I can get it to turn on and get to the PB Screen after the LG logo (because I have the PitchBlack theme installed). Sometimes I can even get to my home screen even open an app, but then everything freezes and screen goes off. Usually after any of these attempts, doing anything with the power button results in nothing, not even a single vibration. It makes me think that the phone is on just the screen is unresponsive. So I have to pull the battery out and try again. I held volume down and power button til LG logo came on, then let go of power button and immediately held it again until I got into recovery. Scrolled down to factory reset, clicked yes, then most of the time the phone shuts off and the LG logo comes on and goes black again. One time it got TWRP to open up. But it froze and screen went black. I finally got it to go into TWRP again randomly, but trying to click on the "Advanced" key in the process of wiping the dalvik cache my phone half froze. By half froze I mean just that. The status bar showed my phone's changing temperature, the minutes were changing and the battery percent showed. When I went to slide the arrow to wipe the cache it wouldn't move. It was like the bottom part of my touchscreen wasn't working. Then I pressed the power button and it locked the screen and said slide to unlock but I couldn't slide the slider. So it's like half of my phone functioned and half didn't.
I wasn't having major issues like this except occasionally getting my phone to receive a charge or turn on. This booting issue started yesterday when I was at work. I was just playing pokemon GO and decided to charge my phone. I unplugged a charger for a Bose speaker (one of those color sound ones) and plugged it into my phone and it immediately shut off and wouldn't get past the LG logo. After a long night of failed attempts to get it working, this is where I am now.
I rooted my phone last week. After the first night I freaked out because I couldn't get my phone to turn on the next morning, I forgot to charge it and the battery was drained. It wouldn't even receive a charge. Then I googled some stuff and found out that taking the battery out and putting it back in can sometimes get it to receive a charge. Then I have to unplug it before turning it on or else it'll just reboot with the battery logo. I've had to do this every time when the battery is completely drained.
I rooted my phone by downgrading to 35B and doing all that LG FlashTool stuff then used Stump. Then installed TWRP and CM13. The most recent thing I have been messing with is Xposed Installer and downloaded and activated a few modules yesterday. Could those have done something? A few were out of date that I decided to give a try. After I turn my phone on and feel it vibrate and all that, I think it actually is turning on. Whether it makes it to the LG logo or not, it seems like it is turning on and maybe the screen just isn't functioning the way it's supposed to. I can't turn it on again, holding the power button does nothing.
Sorry that this was really long, tried to give a detailed description of my issue. Phone has been useless for 24 hours now. It really sucks because I need it, will be traveling through a few airports later today and need to call people to make sure I have rides. Only thing I can think to try is get a new battery. I would really appreciate any help that anyone can provide! I'm desperate.
Update: Recently I have been able to get the phone to start up like normal and get to the home screen, check my texts, that kind of stuff, but within 30 seconds it freezes and shuts off.
I'll confess, I didn't read everything, but a few questions and suggestions. FYI if it were me I'd skip right to suggestion #3.
Can you still access TWRP?
If so,
1. Try wiping Cache and Dalvik /ART or if that doesn't work wipe Cache, Dalvik /ART and Data.
2. If both don't help, wipe them again, then do a fresh flash of whatever preferably stock based ROM you want and the appropriate Bootstack.
3. I would flash the 10B TOT and start fresh. It's often enough the experience of users who flash non-stock or international stock-based ROMs to have various troubles.
No matter what caused the problem, TOTs contain more partitions that KDZs and flashing TOTs can fix problems that KDZs can't.
Good luck, keep us posted.
roirraW "edor" ehT said:
I'll confess, I didn't read everything, but a few questions and suggestions. FYI if it were me I'd skip right to suggestion #3.
Can you still access TWRP?
If so,
1. Try wiping Cache and Dalvik /ART or if that doesn't work wipe Cache, Dalvik /ART and Data.
2. If both don't help, wipe them again, then do a fresh flash of whatever preferably stock based ROM you want and the appropriate Bootstack.
3. I would flash the 10B TOT and start fresh. It's often enough the experience of users who flash non-stock or international stock-based ROMs to have various troubles.
No matter what caused the problem, TOTs contain more partitions that KDZs and flashing TOTs can fix problems that KDZs can't.
Good luck, keep us posted.
Click to expand...
Click to collapse
Sorry I know it was super lengthy. Sometimes I can access TWRP and sometimes I can't. I'm getting so aggravated with my phone! I think I successfully wiped Dalvik which did not help so I'll try to do the others if my phone wants to cooperate with me. Most of the time it doesn't even want to boot into recovery. Most of the time after clicking Yes under factory data reset the LG logo pops up then my phone just goes black.
Update: Wiped Davlik/Art, Cache, and Data. Rebooted and saw the CM13 logo instead of PB but then immediately shut down.
Yeah, I'd definitely go the 10B TOT route.
I've rooted a few phones, but I'm not a ninja like these other xda'ers are. I'm running Jasminerom 8.0 (which is excellent on the g3), a couple of weeks ago, I tried Dirty Unicorns, but it didn't seem to play well with my phone, so I went back to JR 8.0 (by restoring my nandroid backup) then tried to upgrade to JR 9.0 then 9.1. I didn't even get the LG start screen, the screen was black, but I could tell the phone was on by a couple of noises. I did hyelton's "[Guide] LG G3 Stock Firmware (Go Back to Stock) KDZ & TOT Method With LGUP" http://forum.xda-developers.com/showthread.php?t=2785089 It puts the phone back to dead stock, you have to root again and reinstall twrp, then you can go to the rom you want. It scared me pretty good, but within a day or 2, I had my phone back to where it was. Don't forget to thank the devs who post these guides, they can get you out of almost any jam you get into.:good:
FesterBesterTester said:
I've rooted a few phones, but I'm not a ninja like these other xda'ers are. I'm running Jasminerom 8.0 (which is excellent on the g3), a couple of weeks ago, I tried Dirty Unicorns, but it didn't seem to play well with my phone, so I went back to JR 8.0 (by restoring my nandroid backup) then tried to upgrade to JR 9.0 then 9.1. I didn't even get the LG start screen, the screen was black, but I could tell the phone was on by a couple of noises. I did hyelton's "[Guide] LG G3 Stock Firmware (Go Back to Stock) KDZ & TOT Method With LGUP" http://forum.xda-developers.com/showthread.php?t=2785089 It puts the phone back to dead stock, you have to root again and reinstall twrp, then you can go to the rom you want. It scared me pretty good, but within a day or 2, I had my phone back to where it was. Don't forget to thank the devs who post these guides, they can get you out of almost any jam you get into.:good:
Click to expand...
Click to collapse
I was literally in the middle of following the instuctions in the guide you linked, then when I have FlashTool all ready, I noticed my phone turned off. I read that I might have to put it back in download mode after messing with device manager. Now the problem is I can't get it to download mode. I can get the download mode and blue dots image, but doesn't go to the next screen with the "firmware update don't unplug phone" it just goes to blackscreen help I was literally just in download mode now my computer says it doesn't recognize the last usb device that I plugged in
ArcticPat said:
I was literally in the middle of following the instuctions in the guide you linked, then when I have FlashTool all ready, I noticed my phone turned off. I read that I might have to put it back in download mode after messing with device manager. Now the problem is I can't get it to download mode. I can get the download mode and blue dots image, but doesn't go to the next screen with the "firmware update don't unplug phone" it just goes to blackscreen help I was literally just in download mode now my computer says it doesn't recognize the last usb device that I plugged in
Click to expand...
Click to collapse
Do a battery pull to make sure it is shut off, then do the Vol up while plugging in the usb cable. Even if the screen stays black, it should still go into download mode (that's exactly what had happened to me). When you go into Device Manager, you should see LGE Modem listed under Ports, and keep following hyelton's instructions. I was sure mine was dead, but it worked fine.
FesterBesterTester said:
Do a battery pull to make sure it is shut off, then do the Vol up while plugging in the usb cable. Even if the screen stays black, it should still go into download mode (that's exactly what had happened to me). When you go into Device Manager, you should see LGE Modem listed under Ports, and keep following hyelton's instructions. I was sure mine was dead, but it worked fine.
Click to expand...
Click to collapse
I managed to get into download mode, two additional times. The first time, after started FlashTool, it said download failed at 10%.After an hour I finally got it to go into download mode again. Got to 57% then said download failed. My phone won't stay on or something. Everything was going smoothly, then boom black screen download failed. This has been the problem the entire time with my phone. Sometimes I can get to the homescreen, open my texts, browser an app or 2 then freeze and black screen. It won't stay on long enough for FlashTool so what the hell do I do now?!
Now my phone won't even vibrate when I plug it in while holding Vol Up. It comes up as something slightly different in device manager though. I kept FlashTool open even with the failed download, but it says "Can't change to download mode" in the port 1 box.
Also sometimes after plugging in, when it does vibrate, the LG logo comes on instead of DL mode. When that happens my phone appears as something QualCom in device manager then disappears.
Also, does it matter if my COM41 says 'in use'?
ArcticPat said:
I managed to get into download mode, two additional times. The first time, after started FlashTool, it said download failed at 10%.After an hour I finally got it to go into download mode again. Got to 57% then said download failed. My phone won't stay on or something. Everything was going smoothly, then boom black screen download failed. This has been the problem the entire time with my phone. Sometimes I can get to the homescreen, open my texts, browser an app or 2 then freeze and black screen. It won't stay on long enough for FlashTool so what the hell do I do now?!
Now my phone won't even vibrate when I plug it in while holding Vol Up. It comes up as something slightly different in device manager though. I kept FlashTool open even with the failed download, but it says "Can't change to download mode" in the port 1 box.
Also, does it matter if my COM41 says 'in use'?
Click to expand...
Click to collapse
Now you're getting into territory that I have no experience with. I'm sorry I can't help any farther, I hope some of the more experienced xda'ers can help you out.
FesterBesterTester said:
Now you're getting into territory that I have no experience with. I'm sorry I can't help any farther, I hope some of the more experienced xda'ers can help you out.
Click to expand...
Click to collapse
lol thanks for your help! The only issue I've run into the past hour is that I haven't been able to get into Download Mode. When I hold Vol Up and connect USB it either loads the LG logo or just goes blank. Doesn't give me the 'download mode' with the blue dots.
So I'm guessing it's a bad thing if my phone shows up as Qualcomm HS-USB QDLoader 9008 (COM9)?
Phone just shuts off too fast to do anything. If I successfully make it to download mode, only shows for two minutes in device manager. Qualcomm only shows up for about 2 minutes too. What do I do? I can't even flash the 10B TOT because of this.j
It used to be hard to get the battery to charge, but now I can't get it to charge at all!
Update: I realized, the longer I leave my phone alone, the longer it stays on. I waited an hour then tried Download Mode again. Phone stayed in Download Mode long enough for me to get to the blue screen and the red 3. I forgot what to do when I got to this point so I just let it go and it turned off by itself. I took out the battery, then tried to reboot and it hit the LG logo and the little Android when you first set up your phone then black screen.
Update 2: After waiting another hour, I got the phone to sort of start up. Got to the LG logo, then the green android with a blue loading bar underneath then wham! Green screen saying Tz crash! DemiGod Crash Handler. And some other stuff. What the heck is this? Never even heard of it before.
Update 3: tried to flash again, reached the blue screen with the red 3, pulled out USB and battery then tried to boot up and doesn't even boot up.
Sorry for double post, but this is a huge update. I realized the longer I leave my phone alone, the longer it will stay on. So I left the battery out for an hour. Finally I was able to flash 10B TOT and got to the blue screen with the big 3 on it. I wasn't sure what to do so I just left it there and it eventually shut itself down. Tried to boot up and same thing, black screen after LG logo. Does this mean I'm out of luck @roirraW "edor" ehT ?
Don't tell me this has been a hardware issue the whole time... I even tried new batteries today when I went to a cell phone outlet. Tested 4 LG G3 replacement batteries all with the same blackscreen after LG logo
It does sound like hardware, but its very possible the battery itself is the only issue. Unfortunately, without a spare to try, I don't know any way of finding out for sure if that's the issue without buying a new battery. LG's had them on sale for $15 from time to time, but I don't know if they are now or if they're in stock. On the one hand, I'd hate to see you buy a new one locally only to find out that doesn't fix anything but if the battery is the only issue it's a shame to write the phone off. If you lived around Columbus, Ohio I'd offer for you to try my battery just to see what happens.
There definitely has been enough of a precedent of user's batteries being the culprit with this phone.
That's what I get for reading only 5 out of 6 of the new posts. Sorry, yeah, it doesn't sound like there's much hope. Glad you at least had a place to try a different battery without buying one. I don't know what else to suggest - you could try sending it to LG for service. I can vouch for their warranty service - I can't personally report on their out of warranty. In warranty they returned my tablet fixed four days after they paid to have it packaged and shipped to them.
EDIT: Nevermind, only read part of the post and provided bad advice, lol.
roirraW "edor" ehT said:
It does sound like hardware, but its very possible the battery itself is the only issue. Unfortunately, without a spare to try, I don't know any way of finding out for sure if that's the issue without buying a new battery. LG's had them on sale for $15 from time to time, but I don't know if they are now or if they're in stock. On the one hand, I'd hate to see you buy a new one locally only to find out that doesn't fix anything but if the battery is the only issue it's a shame to write the phone off. If you lived around Columbus, Ohio I'd offer for you to try my battery just to see what happens.
There definitely has been enough of a precedent of user's batteries being the culprit with this phone.
That's what I get for reading only 5 out of 6 of the new posts. Sorry, yeah, it doesn't sound like there's much hope. Glad you at least had a place to try a different battery without buying one. I don't know what else to suggest - you could try sending it to LG for service. I can vouch for their warranty service - I can't personally report on their out of warranty. In warranty they returned my tablet fixed four days after they paid to have it packaged and shipped to them.
Click to expand...
Click to collapse
The guy almost didn't let me try the battery. It was a dinky little stand in a farmers market and I was like let me see if they have any batteries. Luckily they did and I was like can I try it? He had the audacity to say sure but that's 20$ extra. Then I said how much is the battery? He said $40. THIS GUY!!! I almost had to beg just to see if it worked, and he finally agreed. He wouldn't even let me do it myself so I gave him my phone and he tried 3 different batteries and still the same problem.
I really appreciate that you would offer a stranger to test out your battery. It's funny that you live in Columbus because I actually go to school near there! I don't go to OSU but I go to OWU in Delaware, Ohio. But you are right, I'm not currently there but will be there soon.
Anyway, I decided that I had given it my all after trying different batteries, flashing the 10B TOT, etc. and made myself go to the Verizon store. Told the guy that greeted me that my phone wouldn't boot. Mind you I'm a little nervous because I don't want them to find out it's rooted if the 10B TOT didn't flash correctly, but I figured I'd had this phone for over two years, it's out of warranty so whatever. He tried to boot it and got nothing, not even the LG logo. So he said since the screen isn't cracked and no water damage I can get a new phone for free. You should have seen my face, my jaw dropped. I said "What?" He told me I have some warranty extension insurance. I said I know I had some insurance where I paid like 8$ a month, but I canceled that last year. He told me no, you have insurance and you pay 9$ a month. I was astonished and was like wow I thought I cancelled it, oh well, if it fixes my phone for "free" then let's do it. So now I'm eagerly waiting for the phone to arrive in the mail. I've had a brick for 4 days now so I'm feeling all kinds of disconnect. My only regret is that I didn't go into Verizon earlier.
So I'm hoping their warranty service is as great as you say. My only fear is that when I put my current battery, sim, and back cover on the new phone that it won't boot. I suppose at least I'll know for a fact that it's the battery at that point. Weird though that I've had this battery for two years and not a single issue...
Would it be wise to go through the root process again? I did all this in the first place just so I could cheat in pokemon, but then found so many cool modules from Xposed that made my life feel that much better.
ArcticPat said:
Would it be wise to go through the root process again? I did all this in the first place just so I could cheat in pokemon, but then found so many cool modules from Xposed that made my life feel that much better.
Click to expand...
Click to collapse
Only you can determine that, sorry mate.
roirraW "edor" ehT said:
Yeah, I'd definitely go the 10B TOT route.
Click to expand...
Click to collapse
I am on fulmics ROM 5.3 with 35B bootstack. Want to go back to kk10B what should i do.. Like do i need special .dll file as i use 35B bootstack?
Never used kdz or tot except for 10B on my phone. Means Never used kdz or tot to flash official lp or MM
Sent from my LG-VS985 using Tapatalk
minhas729 said:
I am on fulmics ROM 5.3 with 35B bootstack. Want to go back to kk10B what should i do.. Like do i need special .dll file as i use 35B bootstack?
Never used kdz or tot except for 10B on my phone. Means Never used kdz or tot to flash official lp or MM
Click to expand...
Click to collapse
The 35B Bootstack should allow you to use the original .DLL, because it's the correct combination of partitions from both 12B and 35B - which are necessary in order to be able to get into TWRP and as far as I'm aware allow using the old .DLL but also as far as I know and have experienced, you can use the newer .DLL any time. It's only when you're 100% stock 35B or higher that you can't flash the TOT without the newer .DLL, and can't flash KDZs older than 35B.
See post #5 of this thread for a link to a post. The post has another link to directions for Verizon. You can get the 10B TOT and the newer .DLL from my Android File Host link the bottom of the first post of @annoyingduck 's stickied return to stock thread in the General section, also in my signature below.
Hello community, I have problems with my LG X Power (LS755v6), the UI is giving some not typical errors (the UI has stopped), the UI appears and disappears and it doesn't allow to use other applications, five minutes later the smartphone freezes and restarts but when it does it doesn't show the LG logo and it doesn't start normally it only shows the notification led blinking. To make it work I have to press (Power, Vol+, Vol-) together and then it manages to turn on and charge the system, until the same thing happens.
Another thing, once I did the reset to turn it back on the battery was at 60% and when I reset the indicator showed me 37%, I have many doubts. The model is LGLS755 (ZV6), Android 6.0.1, Kernel 3.18.22+, Sprint (US) and comes unlocked with Box (I'm using it in Latin America). I'm afraid to make a hard-reset or try to install the factory ROM because I read that it loses the SIM unlock, give me some ideas, what to do?, going to the cellphone technician is my last option (is expensive here), thanks.
PD: I haven't installed anything strange (I don't think it's malware), I haven't modified anything in the system, I'm not ROOT, I haven't changed permissions for ADB, I haven't crappy apps, nothing. It is my first phone and so far it had worked very well, with a great battery, has two years of use and an average of 92 cycles of battery charge, the only battery app I use (ch.cerebrum.ChargeCycleCounter).
I'm sorry if I made the post where I shouldn't or if I broke a rule, I'm new hereI'm sorry if I made the post where I shouldn't or if I broke a rule, I'm new here.
Tenta reinstala a rom stock
Help