Related
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.
This morning in my half-awake state I accidentally pressed "OK" to my phone asking me to go ahead with the (I'm guessing) 2.3.6 update. I KNEW I would end up doing something stupid like that. GRR!!
Anyway, the phone then launched itself into a white screen with blue text saying that it is doing the update, but nothing happens and it appears to be frozen.
I am rooted and was trying to avoid this update; like I said, I was half-awake.
I can't even get it to boot into download/recovery mode, it always goes straight to the white screen. Hopefully this isn't a double post; I checked here and google first but couldn't find anything for this phone. I'm really at a loss here. I have Titanium Backup and I got an external SD card, but I'm not sure if I actually backed up the apps to the external card (new to TB). I did a Kies contacts backup a few days ago so that at least is safe.
Is there any hope for my phone? If I can just get it back to a working state, I can live with my apps' data being erased. Any help appreciated.
Thank you!
Doh... sorry to hear that.. are you also running a custom rom, or customized ATT rom (I have the stock rom from the developers forums over the standard root after having tried a few custom roms).
I got the update message as well this morning, but I postponed it for 8 hours, however I am unable to get rid of the stupid notification, and am curious if after the 8 hours, it will force the update or let me postpone it agian (that will get annoying fast if I cannot disable the OTA update..)
I'd like to know how to cancel the update as well. I have it sitting in my notification bar. >_<
jvanbrecht said:
Doh... sorry to hear that.. are you also running a custom rom, or customized ATT rom (I have the stock rom from the developers forums over the standard root after having tried a few custom roms).
Click to expand...
Click to collapse
I'm still running stock 2.3.5. All I've had time to do is root and TB apps, haven't had the chance to play around with ROMs yet for this phone.
Yeah I postponed it for 8 hours, too. The 8hrs must have expired right as my alarm went off because the "Install this update?" message popped up and I hit it, thinking it was the snooze button -_-
Let me know if there's any way to get off of this screen my phone is stuck on! And then disable the obnoxious message for good.
Thanks again =)
Maybe try to remove battery.
lyndone58 said:
Maybe try to remove battery.
Click to expand...
Click to collapse
I have about 10-15 times since it first happened this morning. I also tried taking out the SIM and microSD cards. It's the only way I can get it to stay off to try to boot to recovery mode (which it still won't boot into); if I hold the power button to turn it off it just resets back into the white Software Update Screen (won't stay off).
Has anyone successfully applied this update yet?
Any other ideas? I appreciate the feedback so far!
Similar thing happened to me. I pulled the battery and booted in to CWM just fine. Restored from there.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
I don't believe I have CWM installed? How would I have known if I did? When I volume up + volume down + power and wait until the Samsung logo comes up it boots back to the white screen. Maybe I'm doing that process wrong?
Same thing happened to me this morning!
almost identical story
I've tried literally every combination to get to the reboot screen. ugh :'(
mrl3086 said:
I have about 10-15 times since it first happened this morning. I also tried taking out the SIM and microSD cards. It's the only way I can get it to stay off to try to boot to recovery mode (which it still won't boot into); if I hold the power button to turn it off it just resets back into the white Software Update Screen (won't stay off).
Has anyone successfully applied this update yet?
Any other ideas? I appreciate the feedback so far!
Click to expand...
Click to collapse
I haven't been rooting as much as some of the guys here, but I think if you take the battery out and it won't boot back even into recovery, you're hard-bricked and you're gonna have to start from scratch with a fresh stock rom. Go to download mode (turn off, hold vol up + down, insert powered usb cable) and put a stock rom back on using odin.
http://forum.xda-developers.com/showthread.php?t=1342348
You will basically get back to what your phone was when you took it out of the box and you'll have to install everything, your data (other than the data that is on a microSD card) won't be there.
If you have a backup that you did with CWM, then you can restore the backup after you do all this.
I think you got unlucky with the worst case scenario of what shouldn't happen during an update.
Thanks for the advice. I'll give it a try when I get home from work and will let you guys know how it goes.
For the future, is it generally recommended to de-root before doing any straight carrier update? Or is this just a total fluke that some of us are experiencing?
Will adb recognize your phone? If it does just adb reboot recovery
Sent from my SAMSUNG-SGH-I727 using xda premium
Lucidmike said:
I haven't been rooting as much as some of the guys here, but I think if you take the battery out and it won't boot back even into recovery, you're hard-bricked and you're gonna have to start from scratch with a fresh stock rom. Go to download mode (turn off, hold vol up + down, insert powered usb cable) and put a stock rom back on using odin.
http://forum.xda-developers.com/showthread.php?t=1342348
You will basically get back to what your phone was when you took it out of the box and you'll have to install everything, your data (other than the data that is on a microSD card) won't be there.
If you have a backup that you did with CWM, then you can restore the backup after you do all this.
I think you got unlucky with the worst case scenario of what shouldn't happen during an update.
Click to expand...
Click to collapse
AMAZING!! Thank you so much! Not only is my phone up and working but the update has installed!
I learned the following:
-you pretty much need a pc (not a mac) to do all the downloads correctly. I used a friends.
-to get your phone into download mode when it's frozen from the update, you have to hold down either vol + AND vol - (or just vol -) as well as the power button, simultaneously hold down power and also simultaneously plug in the usb. Then let go of the power button and remain holding down one or the two volume buttons.
THIS WAS JUST WITH MY SKYROCKET EXPERIENCE
I'm so happy. Thank you LucidMike
This just happened to my friend's phone. White screen no matter what. Stock everything, too. She's pretty bummed that there's no way to recover the videos and pictures on her phone before resetting it. Apparently she went to AT&T and they couldn't figure it out. They called tech support for her and THEY couldn't figure it out. She's currently on the phone with Samsung, but I doubt they'll be able to help either.
viralriot said:
This just happened to my friend's phone. White screen no matter what. Stock everything, too. She's pretty bummed that there's no way to recover the videos and pictures on her phone before resetting it. Apparently she went to AT&T and they couldn't figure it out. They called tech support for her and THEY couldn't figure it out. She's currently on the phone with Samsung, but I doubt they'll be able to help either.
Click to expand...
Click to collapse
AHHH!! Tell her to hang up the phone right now!! Use this method to fix her phone!! All of her data will still be there after it's done! After the process is complete, back it up to a computer (enable USB storage and just copy + paste and I used Kies to copy my contacts) and THEN do a full factory reset (reset recommended by everyone to ensure smooth function of phone). The method in the link will return her to the original stock version; I believe it may trip a counter that AT&T can use to determine if you've hacked your phone, but if you want a working phone...and there's also a chance that it WON'T trip the counter (some people say it did and some say it hasn't).
EDIT: Pictures and videos that I took with the phone are saved in /sdcard/DCIM/Camera, so you know where to copy her stuff from.
jessielooloo said:
AMAZING!! Thank you so much! Not only is my phone up and working but the update has installed!
I learned the following:
-you pretty much need a pc (not a mac) to do all the downloads correctly. I used a friends.
-to get your phone into download mode when it's frozen from the update, you have to hold down either vol + AND vol - (or just vol -) as well as the power button, simultaneously hold down power and also simultaneously plug in the usb. Then let go of the power button and remain holding down one or the two volume buttons.
THIS WAS JUST WITH MY SKYROCKET EXPERIENCE
I'm so happy. Thank you LucidMike
Click to expand...
Click to collapse
I'm trying to fix my boyfriend's phone (he actually didn't hack/root it or anything...but yesterday's update messed up his phone so it was stuck in the "SOFTWARE UPDATE" and "Loading..." frozen white screen). We tried taking out the battery, restarting it, everything. I tried your method of holding all three buttons while plugging in the USB and then letting go of the power button. What do you press when it asks you if you want to continue (up vol +) or cancel (vol -)? I chose vol -, and when it took me back to the white screen, I did it again and pressed vol +. Now I'm on a ODIN MODE page...will this affect his warranty or anything? What do I do next?
You need to have odin on your pc and the stock .tar and flash it. Here go here http://forum.xda-developers.com/showthread.php?goto=newpost&t=1509978
Read carefully follow directions exactly
silver03wrx said:
You need to have odin on your pc and the stock .tar and flash it. Here go here http://forum.xda-developers.com/showthread.php?goto=newpost&t=1509978
Read carefully follow directions exactly
Click to expand...
Click to collapse
Thanks! I read on the first page of the thread that it needs to be rooted though? This phone is brand new and never been rooted or hacked...will doing this void the warranty or anything unpleasant? (I'm the one that likes hacking my devices like my Nook Color...my boyfriend is a little more paranoid and would rather have it stay covered under warranty )
No actually. Thats incorrect..the stock tar. Is just as it sounds. The stock firmware the phone comes with.....dont need to be rooted to use odin. Actually if u odn the stock tar. It removes root.
mrl3086 said:
AHHH!! Tell her to hang up the phone right now!! Use this method to fix her phone!! All of her data will still be there after it's done! After the process is complete, back it up to a computer (enable USB storage and just copy + paste and I used Kies to copy my contacts) and THEN do a full factory reset (reset recommended by everyone to ensure smooth function of phone). The method in the link will return her to the original stock version; I believe it may trip a counter that AT&T can use to determine if you've hacked your phone, but if you want a working phone...and there's also a chance that it WON'T trip the counter (some people say it did and some say it hasn't).
EDIT: Pictures and videos that I took with the phone are saved in /sdcard/DCIM/Camera, so you know where to copy her stuff from.
Click to expand...
Click to collapse
Tried doing this, but this is all I get.
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/006> Added!!
That's it. Nothing else happens. Help?
EDIT: Nevermind! Plugged it into a different USB port (COM:6) and it worked flawlessly. All data is still on phone and it works like new! Thank you!
Hey guys,
Forgive me for being frantic and (probably) not taking the steps needed to research this issue, or not taking the time to do so, but I'm sure you can all presumably imagine -if you've not been in this situation before- that it SUCKS not having a phone in this day in age...
My problem: Atrix 2 (Rooted + CWM Recovery) now won't boot passed the "M" Motorola logo upon start up. It won't even allow me to access the factory Android Recovery by holding down Volume Up, Volume Down, and Power. I think I inadvertently bricked the phone? (Hope not!)
Further, the "M" Motorola logo is skewed in appearance, like its not even loading correctly. I'm not sure what to do. This is my first time rooting and getting experienced with custom ROMS.
Anyone able to help this helpless sap?
Thanks is advance to your replies...
Step 1 is where you tell what you did to get into the state you are in. You wouldn't believe how far it goes toward fixing something if you know how it got broken.
Sent from my MB865 using XDA
If you have CWM recovery on boot can't you just do a battery pull? You do NOT want to let that thing bootloop forever until the battery dies.
The End.
KEB64 said:
If you have CWM recovery on boot can't you just do a battery pull? You do NOT want to let that thing bootloop forever until the battery dies.
The End.
Click to expand...
Click to collapse
Agreed pull the battery. If you run out of juice you'll be in some serious trouble.
Did you try to flash the fkz? Unless you have CWM on Boot it's the only way you can get your phone working.
Okay, sorry for not giving a full rundown on what stupidity on my part cause all of this. Let me start by saying that (sadly) I am a great big n00b when it comes to Linux, and I thought that despite my research online I would sort of explore the CWM Recovery 'Advanced' sections.
I downloaded ROM Toolbox from the Play Store, and installed a custom boot animation, and replaced -or thought I was- the startup "M" logo with something else. This is what concerned me: After re-booting, the "M" logo was all crazy looking, with a "stretched" "M" logo over the top of the "regular" logo.
So, I uninstalled the app, but the logo was still all messed up. So, I used Root Uninstaller to get rid of the ROM Toolbox files, still no resolve to the crazy boot logo.
So, I went into CWM Recovery Advanced, and wiped everything. The Dalvik, cache, System, Data, etc... didn't think that it would -what appears to have happened- wipe out the OS on the phone.
I tried pulling the battery, and re-booting, won't boot passed the skewed "M" logo still. Tried getting into Android Recovery, and it looks to go through the recovery goes through its thing, but never boots normally afterward.
Sorry for being such an idiot, I really shouldn't have messed with this while half asleep, and again I can't apologize enough for being such a stupid n00b.
I can attach an image of the boot logo if that helps, but I'm worried I am just S.O.L. at this point...
Also, not sure what an FKZ is. I tried to install a 2.3.6 apk file to my wife's SD card on her phone and booting from the file after putting the SD card into mine. Still nothing.
pull the battery, put it back in, and hold vol up and down while turning on. choose ap fastboot at the menu. go to the thread in my signature and under the mirrors there is also a download of the return to stock script. run it while in fastboot and plugged in with usb. DO NOT pull the chord until it is done. when it is you should be good.
Apex_Strider said:
Okay, sorry for not giving a full rundown on what stupidity on my part cause all of this. Let me start by saying that (sadly) I am a great big n00b when it comes to Linux, and I thought that despite my research online I would sort of explore the CWM Recovery 'Advanced' sections.
I downloaded ROM Toolbox from the Play Store, and installed a custom boot animation, and replaced -or thought I was- the startup "M" logo with something else. This is what concerned me: After re-booting, the "M" logo was all crazy looking, with a "stretched" "M" logo over the top of the "regular" logo.
So, I uninstalled the app, but the logo was still all messed up. So, I used Root Uninstaller to get rid of the ROM Toolbox files, still no resolve to the crazy boot logo.
So, I went into CWM Recovery Advanced, and wiped everything. The Dalvik, cache, System, Data, etc... didn't think that it would -what appears to have happened- wipe out the OS on the phone.
I tried pulling the battery, and re-booting, won't boot passed the skewed "M" logo still. Tried getting into Android Recovery, and it looks to go through the recovery goes through its thing, but never boots normally afterward.
Sorry for being such an idiot, I really shouldn't have messed with this while half asleep, and again I can't apologize enough for being such a stupid n00b.
I can attach an image of the boot logo if that helps, but I'm worried I am just S.O.L. at this point...
Also, not sure what an FKZ is. I tried to install a 2.3.6 apk file to my wife's SD card on her phone and booting from the file after putting the SD card into mine. Still nothing.
Click to expand...
Click to collapse
Yeah wiping the system partition is a no no unless you flash another rom afterwards. Do like ikrasner says and you should be back to normal.
Sent from my MB865 using XDA
Thanks for all the help guys, I really hope that something positive comes about this... though, to go without mention, I certainly need more knowledge on WTH I am doing to my phone: understanding flashing ROMS, what dangers come with rooting, and a vast array of other "all things root" that I need to learn up on.
I will try to install from SD card the 2.3.5 zip tonight, but will it (the phone) look for the newest 2.3.6 OTA update and try to ask me to install? How does that work after rooting, will I re-brick my clearly bricked phone all over again?
As always, thanks for all your replies in advance -you guys really know what's going on here!
can you read chinese?
Maybe I can solve your question,but poor of my english.
and what is your phone type?
at&t hktw or china ?
Sent from my ME865 using xda premium
Apex_Strider said:
Thanks for all the help guys, I really hope that something positive comes about this... though, to go without mention, I certainly need more knowledge on WTH I am doing to my phone: understanding flashing ROMS, what dangers come with rooting, and a vast array of other "all things root" that I need to learn up on.
I will try to install from SD card the 2.3.5 zip tonight, but will it (the phone) look for the newest 2.3.6 OTA update and try to ask me to install? How does that work after rooting, will I re-brick my clearly bricked phone all over again?
As always, thanks for all your replies in advance -you guys really know what's going on here!
Click to expand...
Click to collapse
It should ask you to install 2.3.6. Just go into setting>about phone>check for updates. Or you could go and install one of the roms that are based on 2.3.6 such as Lithium Sonya or SCv5.
Okay gang, perhaps I'm just certifiably dumb, or I am simply just not doing this correctly. I downloaded the "Returntostock2.3.5.script" zip file and copied it to my wife's SD card to 'apply update from sdcard' option from the Android Recovery area by holding Vol Up, Vol Down, & Power buttons. What I got was this:
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
I tried to just plug the USB into the phone and run the 2.3.5. script from there. but again- I'm stuck in the crazy skewed "M" logo startup screen with nothing following. That's all the phone will do at this point, other than my getting into Android Recovery.
I'm not sure how or what fastboot is, or how it works. If the phone is plugged into the USB, it will only boot the stupid screwed up "M" logo screen. Noting else.
Apex_Strider said:
Okay gang, perhaps I'm just certifiably dumb, or I am simply just not doing this correctly. I downloaded the "Returntostock2.3.5.script" zip file and copied it to my wife's SD card to 'apply update from sdcard' option from the Android Recovery area by holding Vol Up, Vol Down, & Power buttons. What I got was this:
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
I tried to just plug the USB into the phone and run the 2.3.5. script from there. but again- I'm stuck in the crazy skewed "M" logo startup screen with nothing following. That's all the phone will do at this point, other than my getting into Android Recovery.
I'm not sure how or what fastboot is, or how it works. If the phone is plugged into the USB, it will only boot the stupid screwed up "M" logo screen. Noting else.
Click to expand...
Click to collapse
do not flash this. unzip it on your computer, choose to boot into fast boot in the same place you chose recovery, then run the .bat file that was in the zip.
Sent from my MB865 using XDA
What that file does is reflash your system.img, basically restoring your phone to factory default. And just as a sidenote you cannot flash things with the standard Android Recovery. You need CWM.
did you try apboot mode and ise fastboot to flash system.img ?
Sent from my ME865 using xda premium
Still not working... not sure how to flash from fastboot. I don't have any options to run a file from there, or at least not sure ow to go about that.
Fastboot sample, hope will help you.
http://bbs.gfan.com/mobile/android-3701449-1-1.html
Sent from my ME865 using xda premium
dickluo said:
Fastboot sample, hope will help you.
http://bbs.gfan.com/mobile/android-3701449-1-1.html
Sent from my ME865 using xda premium
Click to expand...
Click to collapse
So, if I'm looking at this correctly, I need to open command prompt from my computer, and type the commands in from there?
I don't think my computer is recogzining the phone in any way, as I cannot get into the 'manage usb connections' options.
If I have the 2.3.5.script downloaded on my desktop, and l plug my phone in after launching AP Fastboot on the phone, will the computer know where to flash the file to?
I know, I'm a dolt... please bear with me, I really need to get this thing working again -I feel naked without my phone!
Apex_Strider said:
So, if I'm looking at this correctly, I need to open command prompt from my computer, and type the commands in from there?
I don't think my computer is recogzining the phone in any way, as I cannot get into the 'manage usb connections' options.
If I have the 2.3.5.script downloaded on my desktop, and l plug my phone in after launching AP Fastboot on the phone, will the computer know where to flash the file to?
I know, I'm a dolt... please bear with me, I really need to get this thing working again -I feel naked without my phone!
Click to expand...
Click to collapse
Before using the restore script you need to install the usb drivers for your mb865, you can get those from here: http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/MotoHelper_2.1.40_Driver_5.5.0.exe
Next unzip the Return to Stock 2.3.5 Fastboot SCRIPT.zip to anywhere you like in your pc (example: C:\RestoreScript\ )
Next connect your phone with the usb cable to the pc and get into fastboot mode for this in your phone press volume down + volume up + power it should appear a screen with some options, use the volume down key of your phone to navigate through the menu until you see the Fastboot option, then enter by pressing the volume up key, this will show you some messages and the finally it should said usb connected.
Then open the folder where you extracted the Return to Stock 2.3.5 Fastboot SCRIPT files and search a .bat file call "Stock Restore" then run the file (double click on it) and it should open a command promt screen with some instructions if the phone is connected correctly and you installed the drivers correctly then in some point the screen will show you the id of your device and it will wait you to press the enter key to start the proccess, press key enter wait all the proccess until the program said to you its finished, after that it will reboot your phone and install the stock 2.3.5 when it boots up you should see the android logo and a progress bar filling up.
when it's done wait the reboot and your phone should be ok.
hope this helps.
jfrank1485 said:
Before using the restore script you need to install the usb drivers for your mb865, you can get those from here: http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/MotoHelper_2.1.40_Driver_5.5.0.exe
Next unzip the Return to Stock 2.3.5 Fastboot SCRIPT.zip to anywhere you like in your pc (example: C:\RestoreScript\ )
Next connect your phone with the usb cable to the pc and get into fastboot mode for this in your phone press volume down + volume up + power it should appear a screen with some options, use the volume down key of your phone to navigate through the menu until you see the Fastboot option, then enter by pressing the volume up key, this will show you some messages and the finally it should said usb connected.
Then open the folder where you extracted the Return to Stock 2.3.5 Fastboot SCRIPT files and search a .bat file call "Stock Restore" then run the file (double click on it) and it should open a command promt screen with some instructions if the phone is connected correctly and you installed the drivers correctly then in some point the screen will show you the id of your device and it will wait you to press the enter key to start the proccess, press key enter wait all the proccess until the program said to you its finished, after that it will reboot your phone and install the stock 2.3.5 when it boots up you should see the android logo and a progress bar filling up.
when it's done wait the reboot and your phone should be ok.
hope this helps.
Click to expand...
Click to collapse
jfrank1485,
This stepped me through the entire process without any confusion! Everything is back to normal! Hooray and three Huzzahs!
Also, many many thanks to dickluo, farshad525hou, lkrasner, mtnlion, and KEB64!
You guys really saved my stupid (you know what) on this deal! Next order of business: figure out what the heck I am doing before doing ANYTHING!
Problem solved, my world has regained sanity, and my phone is back to life!
You guys are the best, thank you all so much!!!
Apex_Strider said:
jfrank1485,
This stepped me through the entire process without any confusion! Everything is back to normal! Hooray and three Huzzahs!
Also, many many thanks to dickluo, farshad525hou, lkrasner, mtnlion, and KEB64!
You guys really saved my stupid (you know what) on this deal! Next order of business: figure out what the heck I am doing before doing ANYTHING!
Problem solved, my world has regained sanity, and my phone is back to life!
You guys are the best, thank you all so much!!!
Click to expand...
Click to collapse
I'm glad it work , keep it at hand before doing anything to your phone, it really helps
hello all,
I am new here and I have been searching the forums for a few days as well as the internet but I could not seem to find one that had my same problem, but if there is can you please direct me to it and apologies for that.
I was installing a new rom, the Blackout ICS Incredible v3.0.0 FULLY WORKING!!! [4.0.4][Sense 3.6], onto my inspire i did a full wipe using FULL_WIPE_1.5_EXT4_.zip and I cleared the caches. the install i thought went well because it went to 100% and i even chose what kind of background i could as well as choosing to over clock my processor. The phone the restarted after all of that and it went to the htc screen then faded to black, after about ten minutes of it being black screen i pulled out the battery.
Now when i try to recover it it wont go into hboot and it just goes to the htc white screen then it quickly fades to a black screen and stays like that.
so my question to you all is a Jtag the only way i can save my phone or is there something else i can do?
http://forum.xda-developers.com/showthread.php?p=30480411
Sent from a dream.
Teichopsia said:
http://forum.xda-developers.com/showthread.php?p=30480411
Sent from a dream.
Click to expand...
Click to collapse
Im sorry but I dont understand. I cannot enter hboot no mater what i do and don't you need to enter hboot to reflash it?
True, but I'm hoping you are doing something wrong.
Pull battery, wait a few minutes, place back in. Press and hold Volume down, then power button. Does it go into hboot? If not.
Read this.
http://forum.xda-developers.com/showthread.php?p=20382502
Edit: you are the first report with that issue after trying to flash that rom. My bet (that is, if you are new), you are not doing something wrong.
2nd edit: if you are new, then read the guide in post#7
http://forum.xda-developers.com/showthread.php?p=30007255
Sent from a dream.
Teichopsia said:
True, but I'm hoping you are doing something wrong.
Pull battery, wait a few minutes, place back in. Press and hold Volume down, then power button. Does it go into hboot? If not.
Read this.
http://forum.xda-developers.com/showthread.php?p=20382502
Edit: you are the first report with that issue after trying to flash that rom. My bet (that is, if you are new), you are not doing something wrong.
.
Click to expand...
Click to collapse
I really appreciate the help Teichopsia , but I've tried the power /volume - method many times and it still wont go to hboot. if it helps this is the 5 time i have have flashed a rom on my phone (and it is rooted) and yes sadly i had to be the first person to be unlucky enough to get my phone bricked from the blackout rom :crying:
i think i could get out of this mess if i could only get into hboot.
reading the method you linked to me will it work if i cant even get to the hboot screen? my phone only stays of the white htc logo screen for about 3 seconds then it goes to a lit black screen
on a side note should i report what happened to team blackout to see if they have any soloutions?
The only thing I can think of is trying to get into hboot without the sd card and sim card.
The rest is beyond my knowledge.
You'll need to wait for someone more knowledgable than myself to help you.
Remember, first press and hold the volume down button, while holding that down press the power button. Do not release either button till it shows the hboot. If that doesn't work, pull the battery for five minutes and try again. If you did this part exactly like that, then you can skip it.
Well, you already posyed your issue here, just wait for someone to help you. Glevitan is bound to show up sooner or later.
Sent from a dream.
I would see if you can send commands to it from adb while its in the blacked out state. adb is pretty easy to use and can be found easy online. if you get it installed type "adb devices", if it recognizes your device type "adb reboot bootloader" or "adb reboot recovery".
Novius vi said:
hello all,
I am new here and I have been searching the forums for a few days as well as the internet but I could not seem to find one that had my same problem, but if there is can you please direct me to it and apologies for that.
I was installing a new rom, the Blackout ICS Incredible v3.0.0 FULLY WORKING!!! [4.0.4][Sense 3.6], onto my inspire i did a full wipe using FULL_WIPE_1.5_EXT4_.zip and I cleared the caches. the install i thought went well because it went to 100% and i even chose what kind of background i could as well as choosing to over clock my processor. The phone the restarted after all of that and it went to the htc screen then faded to black, after about ten minutes of it being black screen i pulled out the battery.
Now when i try to recover it it wont go into hboot and it just goes to the htc white screen then it quickly fades to a black screen and stays like that.
so my question to you all is a Jtag the only way i can save my phone or is there something else i can do?
Click to expand...
Click to collapse
i also have the same problem. i'm using a DHD. and to add to that, my volume rocker is broken. i wonder why the warning not to select reboot immediately after installation wasnt part of the download as a readme or something. i may have just lost a perfectly good phone as a result
I can confirm as a third user and one knowledgable in flashing roms that the ICS blackout does the same thing to my phone. I can also confirm that pulling the battery and then trying hboot just results in the white htc screen instead of just popping up hboot. I was able to boot into recovery from the white htc screen by using adb and doing the "adb reboot recovery" command. I am able to restore my backup just fine so you guys will be able to fix it. it must just have a bad boot image for the version of hboot that we have installed.
Gizmoe said:
I can confirm as a third user and one knowledgable in flashing roms that the ICS blackout does the same thing to my phone. I can also confirm that pulling the battery and then trying hboot just results in the white htc screen instead of just popping up hboot. I was able to boot into recovery from the white htc screen by using adb and doing the "adb reboot recovery" command. I am able to restore my backup just fine so you guys will be able to fix it. it must just have a bad boot image for the version of hboot that we have installed.
Click to expand...
Click to collapse
Im sorry but this is the first time i have ever done something like that can you give me a step by step instruction how to do it or a link that says how, i dont want to sound lazy but I scared to mess up my phone even more
Use this guide its very easy. if you have already used your phone on your pc and the drivers are installed all you need to do is download the easyadb and follow the instrucions to where is says to type adb.exe. once it is started just type adb devices to make sure it sees your device and then adb reboot recovery
Ignore the fact the instructions are written for a xoom as it will work for any android device with the drivers already installed, which they should be from rooting, syncing and all the other stuff you have probably already done on pc.
UPDATE: I reinstalled ICS blackout but instead of wiping myself i just let aroma installer do it and everything went fine this time. I noticed the aroma installer reformats everything to ext4. its not mentioned in the op as a requirement but seems thats the case. Hboot version has nothing to do with it like i previously commented. It really is a cool rom with both ics and sense. I have only tried the sense version so far
Hope this helps?
Novius vi said:
Im sorry but this is the first time i have ever done something like that can you give me a step by step instruction how to do it or a link that says how, i dont want to sound lazy but I scared to mess up my phone even more
Click to expand...
Click to collapse
Just in case-- to get into recovery you must press and hold the volume down for a few seconds and then hold the power button. Do not do press them both at the same time. I realize you wrote that your volume rocker seems or is broken but I wrote above just in case-- when I first tried to root my phone, I was pushing them both at first and thought my rocker was broken....
Since you rooted the phone originally-- not sure how you did it. But if you go to this link you can download recovery flash. Read the "readme" file:
http://forum.xda-developers.com/showpost.php?p=29208930&postcount=10
Assuming you can get into recovery-- then reload the blackout ROM but you MUST let the aroma installer wipe and format do not use any other wipe/format tool. Then do NOT press the "FINISH" button-- instead press the back arrow-- you want to go back to flash recovery and reboot from there. If you press finish (like I did multiple times, the phone will just lockup).
Best of luck!
Three of us confirmed that hboot was inaccessible even after battery pull. I am no stranger to this device as well. The only fix was using adb reboot. Also if you actually reformat your partitions to ext4 before install, then aroma will install correctly. It's just not mounting anything if it's still in ext3 format. Definitely better to just do the full wipe within aroma though. I do agree with not hitting restart from aroma but someone already mentioned that a few posts up.
Thank you thank you thank you
After putting it into abd it recognized it and then i was able to put it into hboot. Im not out of the woods yet, but after not being to see hboot in so long, well its just amazing to see it again
ok now its in hboot it gives me 4 choices
bootloader
Reboot
Reboot Bootloader
power down
apologies again but just for reassurance which one should i select?
THANK YOU GUYS for getting me this far!!!
special thanks to Gizmoe for suggesting the adb route
Novius vi said:
After putting it into abd it recognized it and then i was able to put it into hboot. Im not out of the woods yet, but after not being to see hboot in so long, well its just amazing to see it again
ok now its in hboot it gives me 4 choices
bootloader
Reboot
Reboot Bootloader
power down
apologies again but just for reassurance which one should i select?
THANK YOU GUYS for getting me this far!!!
special thanks to Gizmoe for suggesting the adb route
Click to expand...
Click to collapse
Select bootloader to get to recovery option.
1shukla said:
Just in case-- to get into recovery you must press and hold the volume down for a few seconds and then hold the power
Assuming you can get into recovery-- then reload the blackout ROM but you MUST let the aroma installer wipe and format do not use any other wipe/format tool. Then do NOT press the "FINISH" button-- instead press the back arrow-- you want to go back to flash recovery and reboot from there. If you press finish (like I did multiple times, the phone will just lockup).
Best of luck!
Click to expand...
Click to collapse
I did exactly as you said I pressed finished and it asked if i wanted to reboot i said no. then it sent me back to recovery mode crossing my fingers hoping to see that it works:fingers-crossed:
Now, just manually reboot.
Sent from a dream.
You saved my phone!!
Thank you guys sooo much this Rom is great once I got past that minor issue
My phones working better than ever I even oced it a little bit
Again I am eternally grateful to you guys and team black out for this great Rom!
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.