Yesterday my phone started acting up. All running process crashed and not many was able to start. I had to constantly click "force close". I think this started after I installed the Google+ app, but not sure.
I have tried uninstalling all unnecessary apps, without luck. I then tried wiping to factory settings by using the Android menu, but without any changing. I then tried by holding vol+ and power, going in to recovery and wiping both to factory and app cache. This doesn't change anything either. By googling I can see some suggests to hold vol- and power, to get to a another wiping-functionality but this just boots my Nexus S to normal state - no menu appears.
Has anybody an idea of what I can do?
Edit: more info; if I click "Report" and investigate the message sent to Google, I see that error has something to do with SQLite-relatet classes. Which makes some sense, alot of my changes are reset each time the phone is rebooted. For instance did I miss a call a couple of hours before the phone went crazy - this is shown at each boot in the notification area eventhough I clear the area and/or goes to missed call section
Factory reset via menu does delete all your "custom" apps, so I'd say it's not one of the existing apps causing problems.
The way you describe function after your factory reset sounds like factory reset didn't work properly.
If you feel safe I'd recommend rather flashing 2.3.4 again using either Odin or the OTA zip from Google (requires open bootloader).
I think you're right that factory reset doesn't do what is expected. Once I click it, the phone reboots and shows the Android guy next to an unwrapping package. This lasts only 2 seconds, then it reboots itself again and goes into normal phone mode (where all the app-crashing starts again).
I have not flashed or rooted my phone before, but I will consider this now since my NS is pretty much a brick. Thank you for your swiftly response.
Edit: Shouldn't I get a menu, when I push and hold vol- button, while turning on the device? Right now it just boot as normal.
Before you use odin....try going into rom manager a reflashing clockwork! Ive had that android dude on my screeen but reflashibg via rom manager always fixed it. Try that
Sent from my Nexus S using XDA Premium App
Wow my Nexus has totally shut me out.
I cannot use ClockworkMod unfortunately since I am not able to root my phone. It is not detectable via USA (when I use vol+/pwr and connect USB). I am unable to check the USB Debugging option on the phone. Each time I check it, go to home-screen and back to the menu, it has de-selected it again. Also I noticed when I read the info that is sent to Google for all those app-crashes I get, I see SQLiteException and error in an SQLite.java file. So it seems like some database layer is broken.
I read one could copy the ClockWork.img to my phone and use the standard recovery option to flash the img (I think). But when I go into the recovery menu, the file is gone. When I boot the phone again, it has deleted the .img file - eventhough if I copy it to several different folders, they are all gone :-(.
I feel pretty screwed at the moment. How can I else wipe all data?
I'd recommend to check if your device is correctly identified in windows. Missing USB drivers might cause problems. Get the latest drivers and a guide from here.
If you succeed booting into fastboot properly (vol up and power) you can follow this guide. Get the latest cwm recovery.img here.
Last option would be to boot into download mode (vol up + vol down + power + plugging in usb cable) and use Odin from samfirmware.com
--
All options require correctly working USB drivers.
I managed to unlock the bootloader, by quickly turning on USB-debugging (before any processes started to crash) and install the drivers from this post:
http://forum.xda-developers.com/showpost.php?p=6819751&postcount=4
A reboot later, I got this message:
"System UIDs Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
Right below was a button saying "Im feeling lucky" (??)
I installed ClockworkMod using fastboot and tried "Fixing permissions" with no luck. I will try some ROM later on, and hope it will bring my phone back
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
rentaric said:
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
Click to expand...
Click to collapse
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
DennisRP said:
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
Click to expand...
Click to collapse
See I'm no expert on this whole thing. At this point I'd just flash a whole new system via Odin. Prolly not the smartest or safest option, but that's what I'd do because I don't know better. If that wouldn't fix it either, I'd return the phone on warranty
I was looking at Odin from the start, since nothing else seemed to be working.
So right now I got started on Odin. Followed the .pdf steps and flashed the bootloader at first succesfully. I was asked to remove the battery and re-connect my NS. Began downloading "pda" and "phone", but at around 10% a big fat red "fail" message appeared and now I just see the Google-logo on startup. I still cant flash any roms via fastboot.
Im too tired too right now, been working with this for 14 hours straight. I will look at it tomorrow evening. Thanks for your help rentaric
Weird, you're not the first one who had trouble running Odin using their guide.
Overall it's pretty simple.
Enter download mode. Vol up vol down and power at the same time while plugging in the USB cable. Start Odin, should show a yellow colored box with a port number. Uncheck everything but reset timer and auto reboot. Unzip the correct zip file from samfirmware.com (check if you got i9020 or i9023 and get the universal Odin exe), apply file from the folder accordingly. Bootloader and bootloader. Phone and modem. Pda and pda. Csc can remain empty (will change carrier info in fastboot).
Double check md5 hash to avoid broken files.
Sent from my Nexus S using XDA App
rentaric said:
Weird, you're not the first one who had trouble running Odin using their guide.
Click to expand...
Click to collapse
Of course I did not go to bed, how should I be able to sleep with a broken phone .
The firmware suggested on samfirmware.com for my phone, was 2.3.3 and some other version (my phone was 2.3.4.2/GRJ22 or something similar, I suspect that might be the cause. Also I unchecked everything, that might also have been of importance). The flash will always fail when everything was downloaded - it then said something about "remote" and "Loke" and then fail. But as I mentioned, I had succesfully flashed boot.img (2.3.3) thus no boot occured now. I googled the correct bootloader, used fastboot and was booting succesfully again.
I began looking more into the sdcard, as error-messages was leading me this way. To compress 4 hours of investigations into a few lines, it seems as my PBA is malfunctioning as other xda-members have experinced. Only solution is sending the phone to Samsung for a PBA replacement. I purchased the phone in Bestbuy USA and the danish Samsung partners are not too joyfull about this - I will contact Samsung and hope they can help me.
I experinced the exact same thing as this poor guy - http://forum.xda-developers.com/showthread.php?t=993403
Every thing you try to do to /sdcard is worthless.
Formatting (USB/using CWM/using adb shell linux commands) says "Succes" but nothing happens.
Copying files says "Succes" but nothing happens. If I boot phone into CWM, mount usb and upload new rom/apk/whatever and try to do a "install update.zip" it fails with some mounting errors.
Im ready to go cry in a corner - I really want this to be fixable via software, but I probably have to realize that this is a hardware issue.
Apparently Samsung doesn't offer worldwide warranty for cellularphones :´(. God it sucks to pay repair-expenses on a 1 month old mobile.
Hey guys,
I think my phone is partially bricked. I know that sounds weird, but here's the situation:
I was able to unlock my bootloader (faced multiple write errors using fastboot but it did unlock eventually), I can't reflash using Odin (it fails Error is "Complete Write Fail"), when I tried to format some partitions using clockwork I get:
E: format_volume: make_extf4fs failed on /dev/block/platform/s3c-sdhci.0/by-name/system
Error formatting /system!
No linux newb here, so I'm guessing my internal partition is fubared..
Here's what's funny... I can flash a rom and boot into the rom usually on the first try. If I boot into the rom, it runs fine until I reboot the phone. Then it takes another *LITERALLY* 10 times of pulling the battery and rebooting the phone because the phone sticks at the Google boot logo. I can boot into recovery, fastboot, no problem.
As my phone sits right now: I can flash clockwork, bootloader unlocked. I'm having to try the NAND restore to 2.3.1 to get it to work. I rebooted the phone multiple times, no problems but then after a phone call...get a notification that the sd card was suddenly removed and now I'm back to square one..
Does anyone have a clue as to why my phone decided to unmount the internal storage and why I can't get this thing to work correctly 100%?
Thanks guys..
Btw, I usually can't mount the USB storage using clockwork when I get these errors. I have to keep rebooting the phone until I get lucky enough to format the /sdcard, then try and mount it up to my computer.
Just rebooted the phone, flashed /system, and mounted up the USB..
Can anyone explain this??
otisranson said:
Hey guys,
I think my phone is partially bricked. I know that sounds weird, but here's the situation:
I was able to unlock my bootloader (faced multiple write errors using fastboot but it did unlock eventually), I can't reflash using Odin (it fails Error is "Complete Write Fail"), when I tried to format some partitions using clockwork I get:
E: format_volume: make_extf4fs failed on /dev/block/platform/s3c-sdhci.0/by-name/system
Error formatting /system!
No linux newb here, so I'm guessing my internal partition is fubared..
Here's what's funny... I can flash a rom and boot into the rom usually on the first try. If I boot into the rom, it runs fine until I reboot the phone. Then it takes another *LITERALLY* 10 times of pulling the battery and rebooting the phone because the phone sticks at the Google boot logo. I can boot into recovery, fastboot, no problem.
As my phone sits right now: I can flash clockwork, bootloader unlocked. I'm having to try the NAND restore to 2.3.1 to get it to work. I rebooted the phone multiple times, no problems but then after a phone call...get a notification that the sd card was suddenly removed and now I'm back to square one..
Does anyone have a clue as to why my phone decided to unmount the internal storage and why I can't get this thing to work correctly 100%?
Thanks guys..
Btw, I usually can't mount the USB storage using clockwork when I get these errors. I have to keep rebooting the phone until I get lucky enough to format the /sdcard, then try and mount it up to my computer.
Click to expand...
Click to collapse
otisranson said:
Just rebooted the phone, flashed /system, and mounted up the USB..
Can anyone explain this??
Click to expand...
Click to collapse
yup, this ones explainable. classic symptoms of a ns with its internal sd card dying/dead. it happens way too often unfortunately. luckily its a fairly easy and inexpensive repair, if youre not under warranty.
Any direction on how to fix it while not under warranty?
Or take it to tmobile?
otisranson said:
Any direction on how to fix it while not under warranty?
Click to expand...
Click to collapse
check out any local mobile device repair shops. you could probably do it yourself if you dont fear taking the phone apart, it should be to difficult of a repair. its just a matter of buying a replacement(ebay?), taking the phone apart, and replacing the sd.
Found this breakdown, but I don't see where the internal storage is..
http://www.ifixit.com/Teardown/Nexus-S-Teardown/4365/1
I've been having similar issues..what is the exact part name for the SD?...I wanna search to buy one
Sent from my Nexus S 4G using XDA Premium App
I think its:
Samsung KB100D00WM-A453 memory package and S5PC110A01 1GHz Cortex A8 Hummingbird Processor.
I'm going to try to find another nexus s mother board as a whole, that's my only option.
otisranson said:
Found this breakdown, but I don't see where the internal storage is..
http://www.ifixit.com/Teardown/Nexus-S-Teardown/4365/1
Click to expand...
Click to collapse
I think it's in step 10
i seen something a few weeks ago online on how to replace this...it was a video..i just cant remember where i seen it!
I ended up just purchasing a new phone on ebay.. If I find a nexus s with a cracked screen, I will swap out the mobo.
You can check whether there are blocks flagged as bad by FTL (Flash Translation Layer) in recovery. Check recovery.log file (it can be, the bad blocks will show up after formats).
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.
Hey guys, my phone recently shut down by itself and now won't turn back on. And, when I try to factory reset the boot menu comes up with this "/misc partition fail" problem. I tried using odin recovery, but when the installation starts, the phone says "fail due to frp lock". Please, help me out with this. model sammsung sm-j530s
You specified your phone doesn't turn on but you're able to access odin and recovery mode? Try flashing the same firmware to your phone via odin and see if that fixes the problem. If not, launch recovery mode via power + volume up + home and hit reset device and reboot the system. What does your phone say when you try to boot it up normally? Does it get stuck on a loop? And this happened by itself? Not trying to accuse you, but were you trying to root the phone or mess with the partitions? Did you download some malicious app or malware came into your phone (Highly doubt but I am trying to find all solutions)?
mohhaxs said:
You specified your phone doesn't turn on but you're able to access odin and recovery mode? Try flashing the same firmware to your phone via odin and see if that fixes the problem. If not, launch recovery mode via power + volume up + home and hit reset device and reboot the system. What does your phone say when you try to boot it up normally? Does it get stuck on a loop? And this happened by itself? Not trying to accuse you, but were you trying to root the phone or mess with the partitions? Did you download some malicious app or malware came into your phone (Highly doubt but I am trying to find all solutions)?
Click to expand...
Click to collapse
Nah, didn't try rooting. was downloading a game via play store and it said there was some problem with partitions and told me to factory reset the phone. Then I thought I would lose all the data, so I turned it off thinking it would go away. It didn't, but it now gets stuck on samsung screen and blacks out. Odin didn't help by the way
Khabibullo said:
Nah, didn't try rooting. was downloading a game via play store and it said there was some problem with partitions and told me to factory reset the phone. Then I thought I would lose all the data, so I turned it off thinking it would go away. It didn't, but it now gets stuck on samsung screen and blacks out. Odin didn't help by the way
Click to expand...
Click to collapse
Do you know what game was it? I have a device over here I can try downloading it on. Though it could have been some malware on your phone pre-existing. Can you at least get to the odin screen? If you flash the same firmware to your phone, it will work. Or if you can go to recovery mode, you can do reset to your device if you're out of options.