Related
Hello,
I had a problem with my Motorola Xoom WiFi.
My girlfriend was playing with my tablet and couldn't guess my login pattern.
Unfortunately sign in via Google account did not worked and WiFi network was turned off, in Airplane mode!!
So I am looking for way how to unlock it without root access>> is that possible ?
How often did she try? You should be able to wait a little while and then enter the correct pattern. There's also a way to unlock the xoom without knowing the pattern or google account, but no one on this forum is gonna help you with that ('cause we can't be sure that it really is your xoom;-) )
So just try to wait a little while until you can enter the pattern again or try to reboot, maybe the pattern will appear again after that...
llama-power said:
How often did she try? You should be able to wait a little while and then enter the correct pattern. There's also a way to unlock the xoom without knowing the pattern or google account, but no one on this forum is gonna help you with that ('cause we can't be sure that it really is your xoom;-) )
So just try to wait a little while until you can enter the pattern again or try to reboot, maybe the pattern will appear again after that...
Click to expand...
Click to collapse
+1....
Had the same issue....next day I was able to unlock with the correct pattern
llama-power said:
How often did she try? You should be able to wait a little while and then enter the correct pattern. There's also a way to unlock the xoom without knowing the pattern or google account, but no one on this forum is gonna help you with that ('cause we can't be sure that it really is your xoom;-) )
So just try to wait a little while until you can enter the pattern again or try to reboot, maybe the pattern will appear again after that...
Click to expand...
Click to collapse
What cud I say!
It's mine and that's all )>by the way , if it wasn't mine I would hard rest it and it's done !
but for my important thing and special data .. i need to unlock it
now I'm in the past 2 days after it has been locked>> and the screen is just showing that damn "too many pattern attempts!" screen
I can control volume by it's button(and that the only thing that could change a thing in that screen), but is there any way to turn on wifi with or without button !?!?!?!
Do you have adb debugging enabled? I think you can change the wifi state in adb shell....
wes_s said:
Do you have adb debugging enabled? I think you can change the wifi state in adb shell....
Click to expand...
Click to collapse
I'm Sorry ..
I don't know what ADB debugging is ?
is their no any simpler way ?? or can u tell me about that ADB?!
AMDsn said:
I'm Sorry ..
I don't know what ADB debugging is ?
is their no any simpler way ?? or can u tell me about that ADB?!
Click to expand...
Click to collapse
I'm sorry >> I didn't enable ADB before
is it a dead end!!
I really just can't do hard reset, with no way of extraction for my data (it's 20g out of32)!
So >> Is there any new idea please !
Heeeeeeelp~!
You may need to fully wipe it.. you'll lose your data. This can be done through a connected PC.
Revert to the out-of-box state (stock/locked). There are many threads on this.
Or follow instructions here (you may need to register): MotoDev
Load up MZ604 Wifi (HWI69) - and go back through setup.
Once you enter your Google account - it will download your software and reload your wifi settings, etc.. Then let it go through the various OTA updates through ICS 404.
You'll have to redo your screens - but you'll get back a working Xoom.
I'm here, requesting help, i've read (i think) almost everything. Try everything and i'm not able to recover my G2x.
I'm from mexico, and my english it's no so good, i hope that everyone can understand what i'm trying to say U_U
I brought a used T-Mobile G2x from ebay. I was SOOO happy with the phone, a good one, a kickass and it was about $250 dlls for me. I think that was a good deal. The phone was on a average/good condition.
So, i rooted it, then after, moved the rom from stock to CM7 stable.
I changed then to eaglesblood ICS, then another eaglesblood, and then again CM7.
The phone was working very good. Then, a issue appeared.
Some day, the phone was a little slow, then i rebooted it. And then started the pain...
The screen showed the LG Logo, white brilliant. And after a seconds, power off. What!?
I tried to power on again. Nothing. I did the battery pull and then worked fine. I thought that was a simple bug or something.
Later, the phone ran out of energy. I pluged on the wall charger but nothing happened. I left it for an hour and tried to turn it on. Nothing...
Then charged the battery with a multicharger and the same problem. LG Logo, nothing. Checked on the CWM Recovery and did a cleanup of battery stats, nothing. I was desperate, so i've flashed my phone with Eaglesblood again. Vuala, the phone worked... 'till froze and i had to pull the battery... Again, LG Logo... nothing.
The phone boot up by himself after leaving it for an hour or more. But i had another problem... Battery at 999% Or battery stuck at 32% and suddenly dies...
I've checked with the battery app and saw that the battery said 0 mV
I have 2 batteries, and the both with the same problem. One LG, one chinese.
So, i went with a friend of mine, i took borrowed a battery of his LGO3D, and... nothing
The phone works with APX, powers on on the recovery, i even sometimes reads ok the battery and the phone comes alive, 'till i have to reboot it because the phone is so slow after 2 or 3 weeks without a reboot... but it's so rare and random...
I even updated the phone with the 21y baseband and the new stock rom, but keeps doing the same thing...
I'm just at the point that i want to throw the phone to the wall...
There are something that i can do?
Change some piece?
I must say that when the phone read the battery and it's ok, i can charge it normally, works perfectly, usb ok, everything it's like nothing was bad. But the problem is if the phone shut's down...
Get adb working with USB and if using a windows pc open Command Prompt and run
HTML:
adb devices
....Make sure your device is found, an ID number will appear if successful....
HTML:
adb reboot
....Let the phone start rebooting. When "adb devices" works and shows the phone ID again proceed...
HTML:
adb shell
$ su
# dmesg > /sdcard/dmesg.txt
# logcat -v time -d > /sdcard/logcat.txt
# exit
$ exit
adb pull /sdcard/logcat.txt %USERPROFILE%\Desktop\logcat.txt
adb pull /sdcard/dmesg.txt %USERPROFILE%\Desktop\dmesg.txt
exit
If you get a complaint with those last 2 commands; change %USERPROFILE% = whatever your username is where your Desktop is located. (i.e. C:\Users\me\Desktop\dmesg.txt)
Then either email them to me or post them on www.pastebin.com and post links to both files.
I'm a little lost...
First of All! Thanks for the help
And i dont know... The phone must be ON to do that?
The phone right now doesn't power on, just the LG Logo, at this point, when i attach to a computer via USB Cable, the computer doesn't detect anything...
I can enter the CWM Recovery, it's enough??
And a funny thing: The phone NEVER powers ON (Not even the LG LOGO) when usb or charger it's connected.
EDIT:
Good news, i've got adb working, but i don't have su, i'm downloading it thanks
EDIT AGAIN
The last time that i've flashed to stock rom the g2x forgot to root the phone
i've already tried with adb commands, but i got errors when i try...
I guess that i need usb debugging On, and i doesn't have it...
I'm on a dead end??
Go to the ROM for recovery thread in development section, follow it step by step and your phone will be 100% alive and kicking on GB 2.3.4.
Sent from my SPH-D710 using xda premium
supertaco said:
First of All! Thanks for the help
And i dont know... The phone must be ON to do that?
The phone right now doesn't power on, just the LG Logo, at this point, when i attach to a computer via USB Cable, the computer doesn't detect anything...
I can enter the CWM Recovery, it's enough??
And a funny thing: The phone NEVER powers ON (Not even the LG LOGO) when usb or charger it's connected.
EDIT:
Good news, i've got adb working, but i don't have su, i'm downloading it thanks
EDIT AGAIN
The last time that i've flashed to stock rom the g2x forgot to root the phone
i've already tried with adb commands, but i got errors when i try...
I guess that i need usb debugging On, and i doesn't have it...
I'm on a dead end??
Click to expand...
Click to collapse
If I recall you were the one who emailed me and I sent you links to NVFlash correct? Did that work for you? I'm just trying to see what your question really is. It sounded from you OP that the hardware perhaps keeps failing and no matter which ROM you flash, you eventually get stuck in bootloop like you are now. Are you just trying to get out of bootloop or is this a reocurring problem? If your stuck in bootloop then your only solution is to NVFlash a recovery and push a rom. If its reocurring then we gotta figure out why... thats where my instructions come in. So you need to tell us exactly what you're trying to do.
As for adb yes you can adb from recovery. You gotta go to Mounts and storage > Mount /system though or else the device wont show.
oOo B0XeR oOo said:
If I recall you were the one who emailed me and I sent you links to NVFlash correct? Did that work for you? I'm just trying to see what your question really is. It sounded from you OP that the hardware perhaps keeps failing and no matter which ROM you flash, you eventually get stuck in bootloop like you are now. Are you just trying to get out of bootloop or is this a reocurring problem? If your stuck in bootloop then your only solution is to NVFlash a recovery and push a rom. If its reocurring then we gotta figure out why... thats where my instructions come in. So you need to tell us exactly what you're trying to do.
As for adb yes you can adb from recovery. You gotta go to Mounts and storage > Mount /system though or else the device wont show.
Click to expand...
Click to collapse
Ok... my first problem: Language. I don't have problem with the reading, but writing... i'll try to put my words on the right place
I don't remember, when i first flashed my G2x i did it with the Rom Manager App... the result came on a bootloop. Then i used NVFlash and flashed a correct ClockworkMod Recovery. Installed CM7 and everything was fine. Then i wanted to try ICS and flashed it again. No problem. I normally follow the guides step by step, and the phone was right. Then, one day the phone froze and was the first time that i had the bootloop with the LG Bright Logo, then dim, and then power off.
The problem not was while i was flashing a rom. Because while i was on the problem, i flashed with NVFlash the original bootloader and then restore the original firmware, and the problem still there. Right now the phone has the stock rom, updated by the LG utility, and the problem persists.
I think that is what you say. The phone doesn't pass the LG Logo screen no matter which rom i flash... What i don't understand is that the phone seems to be ok. When it powers (a week ago) it worked just fine...
I don't think that is a bootloop caused by a bad flashing... i think that is a recurring problem...
I have this 2 folders with tools for the NVFlash, i think that the both of them are right...
One-Click-G2x-recovery-flasher-04-28-12 [Folder]
One-Click-G2x-recovery-flasher-09-23 [Folder]
They have the APX drivers and NVFlash and the One-click-G2xr-recovery-flasher app...
I'll mount the /system in recovery and i will try to get that log. With the /system mounted then i think that i can root the phone...
I'm gonna try... let's see what happen...
Thanks
EDIT: I noticed (when the problem first came) that the sticker of water damage was ripped off... is not there... But i don't know if the phone was really damaged by water, because i'm not the first owner... The phone was working fine for about 6 months and now it's just like i'm explaining...
supertaco said:
Ok... my first problem: Language. I don't have problem with the reading, but writing... i'll try to put my words on the right place
I don't remember, when i first flashed my G2x i did it with the Rom Manager App... the result came on a bootloop. Then i used NVFlash and flashed a correct ClockworkMod Recovery. Installed CM7 and everything was fine. Then i wanted to try ICS and flashed it again. No problem. I normally follow the guides step by step, and the phone was right. Then, one day the phone froze and was the first time that i had the bootloop with the LG Bright Logo, then dim, and then power off.
The problem not was while i was flashing a rom. Because while i was on the problem, i flashed with NVFlash the original bootloader and then restore the original firmware, and the problem still there. Right now the phone has the stock rom, updated by the LG utility, and the problem persists.
I think that is what you say. The phone doesn't pass the LG Logo screen no matter which rom i flash... What i don't understand is that the phone seems to be ok. When it powers (a week ago) it worked just fine...
I don't think that is a bootloop caused by a bad flashing... i think that is a recurring problem...
I have this 2 folders with tools for the NVFlash, i think that the both of them are right...
One-Click-G2x-recovery-flasher-04-28-12 [Folder]
One-Click-G2x-recovery-flasher-09-23 [Folder]
They have the APX drivers and NVFlash and the One-click-G2xr-recovery-flasher app...
I'll mount the /system in recovery and i will try to get that log. With the /system mounted then i think that i can root the phone...
I'm gonna try... let's see what happen...
Thanks
EDIT: I noticed (when the problem first came) that the sticker of water damage was ripped off... is not there... But i don't know if the phone was really damaged by water, because i'm not the first owner... The phone was working fine for about 6 months and now it's just like i'm explaining...
Click to expand...
Click to collapse
Ok, I bet your partition tables are messed up. If you can get that dmesg and logcat file it would be ideal but if you cant then we just gotta move forward.
First copy all your stuff from SDcard and internal memory into a folder on a PC. Make a backup using clockwork or whatever and also copy that onto a PC just to be safe.
Then you need to search the G2x forum for this batch utility called something like "auto-formatter partition repair tool" or something similar. If you cant find it message me.
Youll want to run that first, its going to completely wipe all of your stuff and reformat the blocks sizes. Once done youll need to NVFlash a CWM recovery again. Then push a ROM over to the phone and install with CWM. (Dont push a stock rom or anything Gingerbread. Ideally push EaglesBlood ICS since I know it works and can help you troubleshoot.
So i would do that first because i bet your upgrade when u said you attempted to install ICS corrupted the file system, which can happen if you dont format /system prior.
Get the utility, backup everything , format the partitions, NVflash CWM recovery, push ICS rom, install, install GAPPS, come back here and tell me it worked
oOo B0XeR oOo said:
Ok, I bet your partition tables are messed up. If you can get that dmesg and logcat file it would be ideal but if you cant then we just gotta move forward.
First copy all your stuff from SDcard and internal memory into a folder on a PC. Make a backup using clockwork or whatever and also copy that onto a PC just to be safe.
Then you need to search the G2x forum for this batch utility called something like "auto-formatter partition repair tool" or something similar. If you cant find it message me.
Youll want to run that first, its going to completely wipe all of your stuff and reformat the blocks sizes. Once done youll need to NVFlash a CWM recovery again. Then push a ROM over to the phone and install with CWM. (Dont push a stock rom or anything Gingerbread. Ideally push EaglesBlood ICS since I know it works and can help you troubleshoot.
So i would do that first because i bet your upgrade when u said you attempted to install ICS corrupted the file system, which can happen if you dont format /system prior.
Get the utility, backup everything , format the partitions, NVflash CWM recovery, push ICS rom, install, install GAPPS, come back here and tell me it worked
Click to expand...
Click to collapse
It's a shame that i cannot get that logcat... :/
Well... i have nothing to lose (data, or something), so i searched over the forums and i found this utility:
Code:
[URL="http://forum.xda-developers.com/showthread.php?t=1590523"]http://forum.xda-developers.com/showthread.php?t=1590523[/URL]
I think thats the right one, or at least, one of many...
That utility flashes a CWM Touch, then, i installed Eaglesblood Gingerbread (because the utility said that if i don't, the sdcard will not be recognized) and the gaaps...
Turned off the phone...
Turned On...
But then again, i have the LG logo bright, then dim, then power off :/
Do you think that could be a charger flex problem? Motherboard? I should burn it?? :/
Use the batch cleanup tool, then flash stock rooted ROM. That way you cab make sure something works, and stock is going to be the safest flash. If that works, then you can go on to custom Roms
Sent from my LG-P999 using xda premium
supertaco said:
It's a shame that i cannot get that logcat... :/
Well... i have nothing to lose (data, or something), so i searched over the forums and i found this utility:
Code:
[URL="http://forum.xda-developers.com/showthread.php?t=1590523"]http://forum.xda-developers.com/showthread.php?t=1590523[/URL]
I think thats the right one, or at least, one of many...
That utility flashes a CWM Touch, then, i installed Eaglesblood Gingerbread (because the utility said that if i don't, the sdcard will not be recognized) and the gaaps...
Turned off the phone...
Turned On...
But then again, i have the LG logo bright, then dim, then power off :/
Do you think that could be a charger flex problem? Motherboard? I should burn it?? :/
Click to expand...
Click to collapse
Yes thats the utility, and the post above by "rtotheichie" is correct too.
You cant flash a Gingerbread ROM. You need to either push a stock/rooted build, or an ICS build. It's that gingerbread -to- ICS thats causing the partition problem (if it even is that). So what you're doing is fixing it then messing it up again.
--> There could be any number of things going on and we can guess at anything but what good is that gonna do? ... You NEED to get that #dmesg log. I would focus on doing whatever you can to get ADB working because thats going to tell us exactly what is failing at boot time. Can you get into Recovery? I wouldn't even worry about starting the ROM, you should focus on getting into Recovery first. If you cant get into Recovery then you didn't flash it correctly with NVFlash. If you can get in, then go to Mounts & Storage > mount /system ...then get that ADB going using my 1st post above. Thats your only hope if you cant get it on your own.
oOo B0XeR oOo said:
Yes thats the utility, and the post above by "rtotheichie" is correct too.
You cant flash a Gingerbread ROM. You need to either push a stock/rooted build, or an ICS build. It's that gingerbread -to- ICS thats causing the partition problem (if it even is that). So what you're doing is fixing it then messing it up again.
--> There could be any number of things going on and we can guess at anything but what good is that gonna do? ... You NEED to get that #dmesg log. I would focus on doing whatever you can to get ADB working because thats going to tell us exactly what is failing at boot time. Can you get into Recovery? I wouldn't even worry about starting the ROM, you should focus on getting into Recovery first. If you cant get into Recovery then you didn't flash it correctly with NVFlash. If you can get in, then go to Mounts & Storage > mount /system ...then get that ADB going using my 1st post above. Thats your only hope if you cant get it on your own.
Click to expand...
Click to collapse
Well, i have no problems with recovery. Never had IT. But the last time i tried to use the commands failed... I'll post a video, maybe that will be more self explaining... I really appreciate that you take a time for helping me thanks
supertaco said:
Well, i have no problems with recovery. Never had IT. But the last time i tried to use the commands failed... I'll post a video, maybe that will be more self explaining... I really appreciate that you take a time for helping me thanks
Click to expand...
Click to collapse
No problem.
Well if you can get into recovery and if you have ADB and the drivers for the phone setup on your PC you should have no problems connecting. Try using a Windows PC if you can, it's funny but ADB is probably the only thing that is easier to get going the 1st time in Windows rather than Linux (Ubuntu).
Just keep trying and run
HTML:
$ adb devices
each time until a device ID shows up.
I've noticed you've posted this same question on like every single Android website that exists; but I'm telling you what the correct answer is and the only way you're going to be able to figure out what is going on is to get to a log file. No one has a magic trick that will automagically fix this from afar. Anything else is just guessing and checking.
In recovery, try going to Advanced > Show log ...what does that say? Also it won't hurt to try going to Advanced > Fix permissions. I doubt that will do anything for you but it won't hurt to try at this point.
oOo B0XeR oOo said:
No problem.
Well if you can get into recovery and if you have ADB and the drivers for the phone setup on your PC you should have no problems connecting. Try using a Windows PC if you can, it's funny but ADB is probably the only thing that is easier to get going the 1st time in Windows rather than Linux (Ubuntu).
Just keep trying and run
HTML:
$ adb devices
each time until a device ID shows up.
I've noticed you've posted this same question on like every single Android website that exists; but I'm telling you what the correct answer is and the only way you're going to be able to figure out what is going on is to get to a log file. No one has a magic trick that will automagically fix this from afar. Anything else is just guessing and checking.
In recovery, try going to Advanced > Show log ...what does that say? Also it won't hurt to try going to Advanced > Fix permissions. I doubt that will do anything for you but it won't hurt to try at this point.
Click to expand...
Click to collapse
I'll try that, today
And i know that aint no magic trick that fix my phone... I'll try everything to resolve the problem.
Thanks...
And another thing. I've checked my PM's, and saw that i've never send a PM to you. And no, i'm not flooding the entire www with my question. But i think that i should have used a diferent question to describe my problem. This is the first time that i ask for help, after reading and reading on the web, and almost everyone says: "send it back to t-mobile", but that's not an option for me. And my first choice (and olny) for asking help of course it's xda.
I remember that once clicked "show log" and an error pop out, but i didn't try the fix permissions options.
This is the video. Sorry for my bad english.
Video
supertaco said:
I'll try that, today
And i know that aint no magic trick that fix my phone... I'll try everything to resolve the problem.
Thanks...
And another thing. I've checked my PM's, and saw that i've never send a PM to you. And no, i'm not flooding the entire www with my question. But i think that i should have used a diferent question to describe my problem. This is the first time that i ask for help, after reading and reading on the web, and almost everyone says: "send it back to t-mobile", but that's not an option for me. And my first choice (and olny) for asking help of course it's xda.
I remember that once clicked "show log" and an error pop out, but i didn't try the fix permissions options.
This is the video. Sorry for my bad english.
Video
Click to expand...
Click to collapse
I saw the video.
Take out the battery > then put it back in.
Press and hold BOTH the [Power] and [Volume Down-] at the same time and keep holding them.
Keep them both pressed while the "LG logo" appears; shortly after you should see the white logo change to a BLUE logo... once you see that you can let go.
Does that work and get you into Recovery? ...let me know.
One other thing to try...
Plug your USB cable into the Computer ONLY ---Not the phone.
Take out the battery, do NOT put it back in.
Now (with the battery still removed), Press and Hold [Volume Up+] and [Volume Down-] together. Do not press the Power button.
While still holding both Volume buttons together, insert the USB cable into the phone.
Now wait a second or two, does the phone Power On into a "Download mode screen"?
If not, let go of the Volume buttons and unplug the USB from the phone.
Now plug the USB back into the phone. Press and hold the [POWER] Button for several seconds (still with NO battery in, just the USB).
Does that turn the phone on?
P.S. - This might be good to have as well:
User manual (Spanish): http://www.lg.com/us/products/documents/LG-G2x-UserGuide_ES.pdf
Service Repair Manual (English): http://www.mediafire.com/view/?cscdjc6p08t2omq
oOo B0XeR oOo said:
I saw the video.
Take out the battery > then put it back in.
Press and hold BOTH the [Power] and [Volume Down-] at the same time and keep holding them.
Keep them both pressed while the "LG logo" appears; shortly after you should see the white logo change to a BLUE logo... once you see that you can let go.
Does that work and get you into Recovery? ...let me know.
One other thing to try...
Plug your USB cable into the Computer ONLY ---Not the phone.
Take out the battery, do NOT put it back in.
Now (with the battery still removed), Press and Hold [Volume Up+] and [Volume Down-] together. Do not press the Power button.
While still holding both Volume buttons together, insert the USB cable into the phone.
Now wait a second or two, does the phone Power On into a "Download mode screen"?
If not, let go of the Volume buttons and unplug the USB from the phone.
Now plug the USB back into the phone. Press and hold the [POWER] Button for several seconds (still with NO battery in, just the USB).
Does that turn the phone on?
P.S. - This might be good to have as well:
User manual (Spanish): http://www.lg.com/us/products/documents/LG-G2x-UserGuide_ES.pdf
Service Repair Manual (English): http://www.mediafire.com/view/?cscdjc6p08t2omq
Click to expand...
Click to collapse
I'm currently downloading the service manual and the user manual.
Ok, i tried the first thing. The phone gets on recovery mode. All good.
On the second thing to try:
-I followed the steps just as you said: vol+ and vol- and connect usb cable. It makes a sound of connected device, checked and windows detects a NVIDIA USB Boot-recovery driver for Mobile devices, but the phone screen never powers up or show a download mode screen. When i flash anything with NVFlash it shows the Download mode screen...
-I plugged the phone without battery, and pushed the power button. The phone does not power on. Not even the LG logo or anything.
I'm still trying to get that logcat. But everytime that i want to type "su" on the adb shell says that cannot found su...
Now i'm on recovery.
Advanced> fix permissions: Done.
Show log:
Init.svc.adbd=running
I: Checking for extendedcommand...
I: Skipping execution of extendedcommand, file not found...
W: Failed to mount /dev/block/mmcblk0p1 (invalid argument)
W: Failed to mount /dev/block/mmcblk0p7 (invalid argument)
Fixing permissions...
/sbin/fix_permissions 2.04 started at 01-01-2007 00:00:36
cat: can't open '/data/system/packages.xml' : no such file or directory
cat: can't open '/data/system/packages.xml' : no such file or directory
/sbin/fix_permissions 2.04 ended at 01-01-2007 00:00:36 (runtime: 0m0s)
Done!
Whats the status on this are you still dead? Looks like you need to do that partition formatter script now... appears your partitions are messed up. What ROM is on there now?
oOo B0XeR oOo said:
Whats the status on this are you still dead? Looks like you need to do that partition formatter script now... appears your partitions are messed up. What ROM is on there now?
Click to expand...
Click to collapse
Sorry, i didn't get the mail of new post...
Yeah, it's still dead...
Today, i put the battery on the phone and it started right away. Battery status ok, everything working fine. But i didn't put a sim card, so i turned off the phone and it's dead again.
I don't know if i'm getting a GOOD partition formatter. But i've already used one... and the result it's the same...
And even tried a crazy method of one guy that put the phone on the fridge for 10 mins and then NVFlashed-it to a stock gb...
And nothing U_U
Power up, show a bright LG logo, then a less bright one... power off...
Thanks for your help...
EDIT:
Today i opened the phone, extracted the logic board and watched everything. A VERY SMALL bga chip (i don´t know wich) had a little crack on it, i cleaned with a soft brush and a little piece came off... Now the phone doesn't boot at all, not even the LG logo... i think that's the end...
If someone can indicate me where i can buy a new mainboard it would be very appreciated. Thanks.
END
LG
eBay
Stuff wanted/selling here
Find a person selling a great phone but like the screen is broken or something. Look at the repair manual i posted previously above.
Hello,
I am trying to fix my girlfriends HTC One S, she accidentally dropped it into the bathtub full of water, she picked it up fast, put it to rice so it sucks out the water and applied heat, the phone worked, but the touchscreen is totally unresponsive, is there any way how I could determine if the touchscreen is damaged, or the motherboard? I dont have anyone else around me who would give up their warranty and let me open theirs phone so I could test it. I already disassembled the phone, tried unplugging the connectors, checking if there is any visible water damage, but i got nothing, so either the panel or the motherboard must be damaged, I need some way to determine which one is it.
I will also add a conversation with Awesome, he was trying to help me at first and there are some more information.
The wet phone? I did reply. Is the phone rooted? If its not boot into the boot loader holding the volume down and power and click factory reset see if you get the touchscreen working again. If it doesn't work then you short circuit something but if it works and goes away then its your screen.
If your phone is rooted its gonna be hard to do factory reset.
Sent from my HTC One S using Tapatalk 2
Then I probably did not figure out the answer was for me
Well, the problem with that is, that there are some valuable photos inside and a factory reset would definitely remove them,
I was looking for a solution for backing them up, I got to a software, that can control the phone from PC without the need of being
installed in the phone, there was a slight problem since it required USB debugging to be turned on and it wasn't. So I was browsing
the internet to find out if it is possible to turn on USB debugging from PC, or perhaps somehow, until here on XDA in some thread
someone said it is impossible, so I gave up backing up the data and went straight for the repair, that is why I need somehow to find out
if either motherboard is damaged or digitizer, I have the phone totally disassembled. I am guessing that some touch controller on board is
damaged, since I cant see any visible damage to digitizer, but I am not sure and I do not want to buy wrong part.
Also the phone is not rooted and is using stock ROM.
Thank you
Yes without USB Debuggin its impossible to extract those files, and without u doing a factory reset I really can't think of doing or trying anything else to figure out what may be the problem. Since its water damage you really won't see if its short circuited. I'm more than sure you got a short circuit rather than needing a digitizer. Other than that feel free to open a new thread in the general section of the one s and asking there maybe other users will have other options for you.
Thank you for help.
Sapphire18 said:
Hello,
I am trying to fix my girlfriends HTC One S, she accidentally dropped it into the bathtub full of water, she picked it up fast, put it to rice so it sucks out the water and applied heat, the phone worked, but the touchscreen is totally unresponsive, is there any way how I could determine if the touchscreen is damaged, or the motherboard? I dont have anyone else around me who would give up their warranty and let me open theirs phone so I could test it. I already disassembled the phone, tried unplugging the connectors, checking if there is any visible water damage, but i got nothing, so either the panel or the motherboard must be damaged, I need some way to determine which one is it.
I will also add a conversation with Awesome, he was trying to help me at first and there are some more information.
The wet phone? I did reply. Is the phone rooted? If its not boot into the boot loader holding the volume down and power and click factory reset see if you get the touchscreen working again. If it doesn't work then you short circuit something but if it works and goes away then its your screen.
If your phone is rooted its gonna be hard to do factory reset.
Sent from my HTC One S using Tapatalk 2
Then I probably did not figure out the answer was for me
Well, the problem with that is, that there are some valuable photos inside and a factory reset would definitely remove them,
I was looking for a solution for backing them up, I got to a software, that can control the phone from PC without the need of being
installed in the phone, there was a slight problem since it required USB debugging to be turned on and it wasn't. So I was browsing
the internet to find out if it is possible to turn on USB debugging from PC, or perhaps somehow, until here on XDA in some thread
someone said it is impossible, so I gave up backing up the data and went straight for the repair, that is why I need somehow to find out
if either motherboard is damaged or digitizer, I have the phone totally disassembled. I am guessing that some touch controller on board is
damaged, since I cant see any visible damage to digitizer, but I am not sure and I do not want to buy wrong part.
Also the phone is not rooted and is using stock ROM.
Thank you
Yes without USB Debuggin its impossible to extract those files, and without u doing a factory reset I really can't think of doing or trying anything else to figure out what may be the problem. Since its water damage you really won't see if its short circuited. I'm more than sure you got a short circuit rather than needing a digitizer. Other than that feel free to open a new thread in the general section of the one s and asking there maybe other users will have other options for you.
Thank you for help.
Click to expand...
Click to collapse
Em so is the bootloader unlocked? you could try to see if adb is working in fastboot or if it is unlocked I think TWRP lets you use adb.
Well, its all in stock, so I guess the bootloader is locked, and without USB debugging turned on ADB doesn't recognize the phone.
Sapphire18 said:
Well, its all in stock, so I guess the bootloader is locked, and without USB debugging turned on ADB doesn't recognize the phone.
Click to expand...
Click to collapse
Ok but have you tried adb in fastboot?
adb in fastboot should work, regardless of the setting in the rom.
What android version is it running? If its running 4.1 you could use an OTG cable and hook up a mouse to control the device.
Goatshocker said:
adb in fastboot should work, regardless of the setting in the rom.
What android version is it running? If its running 4.1 you could use an OTG cable and hook up a mouse to control the device.
Click to expand...
Click to collapse
Omg so forgot you can use a mouse so going to do that now for no reason lol.
Darknites said:
Omg so forgot you can use a mouse so going to do that now for no reason lol.
Click to expand...
Click to collapse
Theres also an app that can share your kb/mouse to your android device, the device will see the kb/mouse as hardware plugged in.
ShareKM its called, works damn good on both my S and TF.
Goatshocker said:
Theres also an app that can share your kb/mouse to your android device, the device will see the kb/mouse as hardware plugged in.
ShareKM its called, works damn good on both my S and TF.
Click to expand...
Click to collapse
Cool think I have a play later.
Okay, here is what I got, the OTG cable is not working, that means the phone doesn't have Android 4.1.
The ShareKM application requires installation into the phone, meaning it is out of question too.
I am experimenting with this ADB in fastboot, but I am not really sure how that fastboot command works when I run ADB.exe trough command prompt and list devices, it show me only my other phone in USB debugging, when I run the fastboot.exe and type adb devices it says "waiting for the device", I do not really know how to work with this with a little guide, it shows me some commands there, i tried the one with rebooting into bootloader, but it still says only "waiting for device".
Could you give me a little guide perhaps link to guide what exactly I am supposed to do to run ADB in fastboot?
I am pretty technical type, dont need noobish explanation.
Thank you
Okay, I managed to get into fastboot, I always thought it is something with the fastboot.exe in SDK Platform-tools, well, anyway, I am inside, it says Fastboot USB, but adb still isnt showing the device in the list.
Also there is a big pink ***LOCKED***, that means that bootloader is locked I guess.
Any other ideas how I could backup the files? or any other suggestions?
Thank you
Moving slowly forward, I was being stupid and I was using the ADB command instead fastboot command, when I am in fastboot mode now, well, trough fastboot command now the PC recognizes the phone, altho what is the next step now?
Thanks again
Yeah, the ShareKM app was never really ment for you, it was more of a suggestion to dark sorry if it confused you.
I ran some quick tests, and yeah Im afraid adb is, in fact, not working in bootloader.
What happens if you boot into recovery? Maybe it works there?
What kind of things do you need to save? Is it just like pictures and stuff from the sdcard?
In that case, you could unlock the bootloader (this will wipe the device data, like applications etc) and install TWRP. Im 100% sure ADB works in TWRP without you needing to use the screen.
Just tried booting into recovery, the only thing I am receiving is big red exclamation mark, not sure what it means, I did some digging and it usually appears when someone is trying to do OTA update from custom ROM, strangely, this is original stock ROM.
One S doesn't posses SD card, it has 16Gb internal storage, but is probably divided into some system partition and data partition, if that is what you meant. Yes, it is only some photos and videos.
You said TWRP, as I did some background search, it says touch recovery, that kinda sounds it uses touch, and that is the one thing I can't use.
Or am I mistaken?
Sapphire18 said:
Just tried booting into recovery, the only thing I am receiving is big red exclamation mark, not sure what it means, I did some digging and it usually appears when someone is trying to do OTA update from custom ROM, strangely, this is original stock ROM.
One S doesn't posses SD card, it has 16Gb internal storage, but is probably divided into some system partition and data partition, if that is what you meant. Yes, it is only some photos and videos.
You said TWRP, as I did some background search, it says touch recovery, that kinda sounds it uses touch, and that is the one thing I can't use.
Or am I mistaken?
Click to expand...
Click to collapse
Right you say adb is see your phone now, download Quick ADB Pusher load it and see if you find the sd card if it does just copy over everything you want, it will need to be in pull mode for this.
Darknites said:
Right you say adb is see your phone now, download Quick ADB Pusher load it and see if you find the sd card if it does just copy over everything you want, it will need to be in pull mode for this.
Click to expand...
Click to collapse
It did not work, but I am going to describe everything I did: I started the phone, got into Bootloader, switched into fastboot and connected USB cable, then I started the Quick ADB pusher, switched into pull mode, opened ADB Explorer, but there I dont see anything, only "error: device not found".
Did I do anything wrong, or is it that the Quick ADB pusher doesn't work in fastboot?
Sapphire18 said:
It did not work, but I am going to describe everything I did: I started the phone, got into Bootloader, switched into fastboot and connected USB cable, then I started the Quick ADB pusher, switched into pull mode, opened ADB Explorer, but there I dont see anything, only "error: device not found".
Did I do anything wrong, or is it that the Quick ADB pusher doesn't work in fastboot?
Click to expand...
Click to collapse
Em did you try scan under select device?
Darknites said:
Em did you try scan under select device?
Click to expand...
Click to collapse
It shows me the phone there, under name SH27NW401121, but when I open the ADB explorer, there is only a folder named
"error: device not found" to me it looks like that Quick ADB pusher doesnt work in fastboot mode.
Sapphire18 said:
It shows me the phone there, under name SH27NW401121, but when I open the ADB explorer, there is only a folder named
"error: device not found" to me it looks like that Quick ADB pusher doesnt work in fastboot mode.
Click to expand...
Click to collapse
Then I'm out of ideas because unlocking the Bootloader will wipe the sd.
Indeed, Quick ADB is just a GUI front-end for adb commands. If adb doesnt work in a command line, Quick ADB wont work either.
Theres nothing I can do about that, its not like I can magically force your device into accepting adb commands.
Unlocking the bootloader wont wipe the SD... At least, it didnt for me (just the /Android/ folder).
Things like pictures taken and custom ringtones were still present after the unlocking.
So, ADB doesnt work when youre in recovery either? (the big red exclamation mark)
Goatshocker said:
Indeed, Quick ADB is just a GUI front-end for adb commands. If adb doesnt work in a command line, Quick ADB wont work either.
Theres nothing I can do about that, its not like I can magically force your device into accepting adb commands.
Unlocking the bootloader wont wipe the SD... At least, it didnt for me (just the /Android/ folder).
Things like pictures taken and custom ringtones were still present after the unlocking.
So, ADB doesnt work when youre in recovery either? (the big red exclamation mark)
Click to expand...
Click to collapse
And I am not throwing any blame either, I am just open to every solution
How would unlocking the bootloader help me? so I could put that TWRP inside and do some magic with it?
For the recovery part, I am not really sure how it is supposed to work, but every picture I googled shows some text
along with the exclamation mark, but the only thing I am getting is exclamation mark, and after a while the phone reboots.
I am guessing the recovery either wont load up, or something is wrong, should I try running ADB while that exclamation mark is shown?
I need to return a broken rooted phone, and have a question before I do so...
the phone has been rooted, and has the HellFire ROM installed. The phone currently won't boot up completely. It gets to the boot animation, and just loops forever. I first thought this was a battery issue, as I'm unable to even do a factory reset or get into download mode. After ordering a new battery, I found this wasn't the issue, and now need to send it back to tmobile.
now my question...
if I send it back, will they be able to tell if it's rooted, since it won't boot up, or is there a way I can make it impossible for them to find out? I've heard I can cook it in the microwave for a few seconds, but I'm not trying to blow anything up. LOL
any assistance would be greatly appreciated.
SevnSins said:
I need to return a broken rooted phone, and have a question before I do so...
the phone has been rooted, and has the HellFire ROM installed. The phone currently won't boot up completely. It gets to the boot animation, and just loops forever. I first thought this was a battery issue, as I'm unable to even do a factory reset or get into download mode. After ordering a new battery, I found this wasn't the issue, and now need to send it back to tmobile.
now my question...
if I send it back, will they be able to tell if it's rooted, since it won't boot up, or is there a way I can make it impossible for them to find out? I've heard I can cook it in the microwave for a few seconds, but I'm not trying to blow anything up. LOL
any assistance would be greatly appreciated.
Click to expand...
Click to collapse
Are you sure that you can't key combo into recovery?
If you have the time, make a jig to force your phone into download mode. Then you can use odin to flash stock.
If you are wanting to send it in for warranty because you can't accomplish the tasks above.
Then you have adb access on then run the tool in my signature and use the unroot command.
(It will take a while for adb to start up at the bootscreen but it does startup.)
Just make sure that you have drivers properly installed.
They shouldn't be able to tell the difference.
Lgrootnoob said:
Are you sure that you can't key combo into recovery?
If you have the time, make a jig to force your phone into download mode. Then you can use odin to flash stock.
If you are wanting to send it in for warranty because you can't accomplish the tasks above.
Then you have adb access on then run the tool in my signature and use the unroot command.
(It will take a while for adb to start up at the bootscreen but it does startup.)
Just make sure that you have drivers properly installed.
They shouldn't be able to tell the difference.
Click to expand...
Click to collapse
No, I've tried booting into recovery & download mode both several times, and they both are unsuccessful. When trying recovery, it displays the blue recovery starting text, but never goes into recovery. It just skips to the boot animation, and loops. When trying download mode, as soon as it asks to press volume up or down, the device powers off. it doesn't even give me the time to click anything.
Not sure what you mean by "make a jig to force download mode", but I'll give your second suggestion a try.
thanks
SevnSins said:
No, I've tried booting into recovery & download mode both several times, and they both are unsuccessful. When trying recovery, it displays the blue recovery starting text, but never goes into recovery. It just skips to the boot animation, and loops. When trying download mode, as soon as it asks to press volume up or down, the device powers off. it doesn't even give me the time to click anything.
Not sure what you mean by "make a jig to force download mode", but I'll give your second suggestion a try.
thanks
Click to expand...
Click to collapse
i downloaded your script, placed on a flash drive, and I'm getting the attached errors.
SevnSins said:
i downloaded your script, placed on a flash drive, and I'm getting the attached errors.
Click to expand...
Click to collapse
Which version of windows?
I have tested this script on four different machines,
It seems that your path variable is most likely messed up.(Unless you manage to find issues with my code which is appreciated too )
If you like then you can post the output of the path command while running adbClient and I can help you fix that problem.
Otherwise use the instadb command to fix this if you don't want to fix your potential path variable problem.
(instadb will install adb to the system)
Back to the topic at hand, Jig
There is a link to making a usb jig. (It is a VERY helpful link, as long as you take the time to read everything [The Xda way ] )
That can get you into download mode.
You can either go find a usb jig online and buy it, or you can make your own.
I also found this at the bottom of the page:
darkamikaze - "I got this from sparkfun. While it's not necessarily buying a complete jig, it saves the hassle of cutting a perfectly working usb cord
https://www.sparkfun.com/products/10031 "
I'm interested in the path thing though, so please do post the output of the path command being used inside the tool.
Lgrootnoob said:
Which version of windows?
I have tested this script on four different machines,
It seems that your path variable is most likely messed up.(Unless you manage to find issues with my code which is appreciated too )
If you like then you can post the output of the path command while running adbClient and I can help you fix that problem.
Otherwise use the instadb command to fix this if you don't want to fix your potential path variable problem.
(instadb will install adb to the system)
Back to the topic at hand, Jig
There is a link to making a usb jig. (It is a VERY helpful link, as long as you take the time to read everything [The Xda way ] )
That can get you into download mode.
You can either go find a usb jig online and buy it, or you can make your own.
I also found this at the bottom of the page:
darkamikaze - "I got this from sparkfun. While it's not necessarily buying a complete jig, it saves the hassle of cutting a perfectly working usb cord
https://www.sparkfun.com/products/10031 "
I'm interested in the path thing though, so please do post the output of the path command being used inside the tool.
Click to expand...
Click to collapse
I'm using Win7
I'm not as familiar with adb as I should be, as I haven't had to use it much through my experiences, so I don't really know my way around it that well.
instadb is asking for username & password info, and I don't know what goes in there.
I don't have a soldering iron, so I'll likely need to buy one it looks like.
I've attached the path output you requested.
thanks for your help
SevnSins said:
I'm using Win7
I'm not as familiar with adb as I should be, as I haven't had to use it much through my experiences, so I don't really know my way around it that well.
instadb is asking for username & password info, and I don't know what goes in there.
I don't have a soldering iron, so I'll likely need to buy one it looks like.
I've attached the path output you requested.
thanks for your help
Click to expand...
Click to collapse
Thanks for the path info.
If you want to build it then you can buy a soldering iron, but if you manage to buy an already built jig it might be cheaper and require less time. ey
instadb requires the username of an admin account on your machine and the password for that account. (It elevates user permissions then copies binaries to the system32 folder)
You can do this manually by copying the dlls for adb from the bin folder and the adb and fastboot executables from the bin folder into system32.
After that you shouldn't receive anymore errors.
Thanks for the info, apparently nothing is wrong with the path variable. (Whats weird is the "F:\-" in the photo you attached it should normally be drive letter:\path to adb , F:\bin in a variable)
Try my tool on a local drive. (Its finnicky sometimes )
Lgrootnoob said:
Thanks for the path info.
If you want to build it then you can buy a soldering iron, but if you manage to buy an already built jig it might be cheaper and require less time. ey
instadb requires the username of an admin account on your machine and the password for that account. (It elevates user permissions then copies binaries to the system32 folder)
You can do this manually by copying the dlls for adb from the bin folder and the adb and fastboot executables from the bin folder into system32.
After that you shouldn't receive anymore errors.
Thanks for the info, apparently nothing is wrong with the path variable. (Whats weird is the "F:\-" in the photo you attached it should normally be drive letter:\path to adb , F:\bin in a variable)
Try my tool on a local drive. (Its finnicky sometimes )
Click to expand...
Click to collapse
ok, looks like the script is working now, but I'm getting a "device unauthorized" error. The device is connected, and has the boot animation looping.
i also tried to reboot into recovery from your script, and get the same "device unauthorized" error.
screenshot attached.
SevnSins said:
ok, looks like the script is working now, but I'm getting a "device unauthorized" error. The device is connected, and has the boot animation looping.
i also tried to reboot into recovery from your script, and get the same "device unauthorized" error.
screenshot attached.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2401452
Its impossible to use adb at this point. (Never say never: Has adb worked before?)
You have a samsung phone right?
Your phone would have to be working to accept a key on screen for adb access.
The only thing now is the usb jig.
Lgrootnoob said:
http://forum.xda-developers.com/showthread.php?t=2401452
Its impossible to use adb at this point. (Never say never: Has adb worked before?)
You have a samsung phone right?
Your phone would have to be working to accept a key on screen for adb access.
The only thing now is the usb jig.
Click to expand...
Click to collapse
I do have a samsung phone (Galaxy S3), but I don't recall if I ever used adb with this phone. I know I've used it a few times in the past, but that could have been on my G1 & G2.
think I'm just going to put it in the microwave like I used to do my playstations. LOL! I need to get a working phone, and waiting for a jig to ship is going to take a few days I'm sure.
thanks again for all your help
SevnSins said:
I do have a samsung phone (Galaxy S3), but I don't recall if I ever used adb with this phone. I know I've used it a few times in the past, but that could have been on my G1 & G2.
think I'm just going to put it in the microwave like I used to do my playstations. LOL! I need to get a working phone, and waiting for a jig to ship is going to take a few days I'm sure.
thanks again for all your help
Click to expand...
Click to collapse
Well seems like a repair would leave you with the jig as the only option.
If your house burns down then I got your back there too.
You could just come chill with me.
Just make sure to post pics of your microwaved phone. (Or a video :laugh
Lgrootnoob said:
Well seems like a repair would leave you with the jig as the only option.
If your house burns down then I got your back there too.
You could just come chill with me.
Just make sure to post pics of your microwaved phone. (Or a video :laugh
Click to expand...
Click to collapse
well... where wasn't a fire, but I got a pretty cool spark. although; it still didn't "kill it" all the way. it's still try to boot up. I just decided to send it in, if they charge me for it, I'll just pay it. my job is taking over my phone bill anyways, so I shouldn't need to worry about it.
thank again for your help :good:
i bought the tf300 tablet on craigslist, guy stated the digitizer was replaced but it does not work. its a g01 digitizer (i have no idea what the original digitizer was). i read the dozen of pages of few threads but i cannot find any instructions on how to flash the digitizer board. i ordered the otg host adapter, as the tablet is stuck on the first page of the setup and i cannot really check any other things without it. can someone point me in the right direction on how to unlock, root, and program that chip to work with this new ts? thanks
karolpl2004 said:
i bought the tf300 tablet on craigslist, guy stated the digitizer was replaced but it does not work. its a g01 digitizer (i have no idea what the original digitizer was). i read the dozen of pages of few threads but i cannot find any instructions on how to flash the digitizer board. i ordered the otg host adapter, as the tablet is stuck on the first page of the setup and i cannot really check any other things without it. can someone point me in the right direction on how to unlock, root, and program that chip to work with this new ts? thanks
Click to expand...
Click to collapse
How about post # 104 of this thread? It's only on page 11, you might have noticed.
graphdarnell said:
How about post # 104 of this thread? It's only on page 11, you might have noticed.
Click to expand...
Click to collapse
what does "Get it into the device:
adb push 02-3011-4820.ekt /data/local/tmp" mean?
and get yourself into the device?
karolpl2004 said:
what does "Get it into the device:
adb push 02-3011-4820.ekt /data/local/tmp" mean?
and get yourself into the device?
Click to expand...
Click to collapse
It means you push the 4820 file from your PC to a temp folder in your tab. Afterwards, you flash it (following command). If you are in the dark about adb, it's time to search and learn to install and use it. Basically, you install ADB (platform-tools package); place the 4820 file in it; install drivers for your tab; use the windows command "cmd" as administrator to go to the ADB folder; check your tab availability (USB debugging ticked); then issue the commands on p. 11. If this sounds like Greek to you, you'd have to hit the books, only because I can't do it for you. It wouldn't take more than an hour.
If you can't afford to spend that much time on this, you should find someone who can. Otherwise, you're poorly equipped to mess around with it, honestly. If you get anywhere with it and get stuck, come back here with questions. People are willing to help.
after spending several days getting to know adb im sort of in a deeper hole. since twrp required touch and my digitizer was non responsive i installed cwm. unfortunately it would not mount anything, kept giving me errors. i kept fiddling with it and accidentally used the wipe option in fastboot. now i am stuck in an infinite loop that keeps taking me to cwm. i couldnt boot into the bootloader, until i finally managed to do so with command thru adb. my original firmware was 10.6.1.27.5, and i flashed 10.6.1.15.3. after restarting, it still loops back to cwm?? do i have to reflash the firmware to 10.6.1.27.5? or do i have to flash the recovery back to something? my main objective is to get the root working so i can update the files for digitizer..
karolpl2004 said:
after spending several days getting to know adb im sort of in a deeper hole. since twrp required touch and my digitizer was non responsive i installed cwm. unfortunately it would not mount anything, kept giving me errors. i kept fiddling with it and accidentally used the wipe option in fastboot. now i am stuck in an infinite loop that keeps taking me to cwm. i couldnt boot into the bootloader, until i finally managed to do so with command thru adb. my original firmware was 10.6.1.27.5, and i flashed 10.6.1.15.3. after restarting, it still loops back to cwm?? do i have to reflash the firmware to 10.6.1.27.5? or do i have to flash the recovery back to something? my main objective is to get the root working so i can update the files for digitizer..
Click to expand...
Click to collapse
Do you have fastboot?
lj50036 said:
Do you have fastboot?
Click to expand...
Click to collapse
i managed to get everything back. except i have no adb in fastboot, but adb works in twrp?
karolpl2004 said:
i managed to get everything back. except i have no adb in fastboot, but adb works in twrp?
Click to expand...
Click to collapse
adb in fastboot???