Related
Welp, tried to root the Nexus S 4g.
On rebooting, it gets stuck at the Nexus S bootscreen, pauses, keeps going, etc.
Got CWM 3.0.0.5, and can fastboot, get into CWMRecovery.
From there, I'm at a loss. Tried to restore Nandroid backup, but it says a whole bunch of stuff, basically saying E: failed to find "cache" partition, Can't mount /cache/recovery/last_log, etc.
Tried to apply zip from CWM backup, it says "No files found."
Tried going into mounts/storage to mount USB storage, but nothing appears on desktop of either Mac or PC, so I can't get move files onto the SD card.
Now, when I just power up, it just says "Google," and there's a unlock icon at the bottom. Nothing else.
Anyone have any solutions?
Yeah stop using that old version. Of ClockworkMod recovery
Seriously use 3.0.2.4. Its in the clockwork thread in the dev section.
Sent from my Nexus S using XDA App
Would if I could, but I can't get anything on the SD card!
Trying to mount USB storage from CWM-- no drive shows up on Mac or PC for me to move stuff onto it.
Boot into fastboot by turning off phone, turn back on while holding volume rocker up. Leave it at the screen where you could select reboot, recovery etc. Download the above mentioned clockwork recovery image from the thread to your computer. Flash using fastboot command. No need to copy anything to SD card.
Sent from my Nexus S using XDA App
Having the exact same issue. Nothing appears in the nandroid folder now either after replacing the recovery image with 3.0.2.4 and I can't mount the USB storage or get anything onto the SD card. Phone won't boot. Unsure of the folder structure on this phone to try pushing a file with adb or fastboot.
Same issues here. I was able to flash CWM recovery 3.0.2.4, but when I go to "mounts and storage" and "mount USB storage", I the drive does not appear on both Mac and PC. I'd like to transfer the stock NS4G image onto the phone so I can install the zip from the sdcard...
When I try to use the command, "adb push", it can't find the SD card.
Same problem
I flashed it , and since then i cannot mount the device , i have a good image to push but the device is not opening up the storage for me to push the image.
I had the same problem. Got it all fixed up.
peabody42 said:
Welp, tried to root the Nexus S 4g.
On rebooting, it gets stuck at the Nexus S bootscreen, pauses, keeps going, etc.
Got CWM 3.0.0.5, and can fastboot, get into CWMRecovery.
From there, I'm at a loss. Tried to restore Nandroid backup, but it says a whole bunch of stuff, basically saying E: failed to find "cache" partition, Can't mount /cache/recovery/last_log, etc.
Tried to apply zip from CWM backup, it says "No files found."
Tried going into mounts/storage to mount USB storage, but nothing appears on desktop of either Mac or PC, so I can't get move files onto the SD card.
Now, when I just power up, it just says "Google," and there's a unlock icon at the bottom. Nothing else.
Anyone have any solutions?
Click to expand...
Click to collapse
I had the same problem this morning:
I posted a workaround that worked well for me in Post #35
http://forum.xda-developers.com/showthread.php?t=1072698&page=4
If it works for you click 'Thanks'
Figured it out
Alright , this is what i did to fix the problem, i booted up the system with the bad image i had, connected to wifi and downloaded the Nexus S 4G deoxed image that is out there directly from the internet to the phone. Then i moved it from the download folder to the root using file manager.
I rebooted into recovery and was able to wipe and then flash the recovery image and reboot. Once i rebooted i regained control over the usb and memory card. hope it helps you guys.
How Do I Fix "REALLY" Bricked and DEAD Nexus S4g?
All posts on this thread presuppose a working Nexus S 4g. When I use the term bricked, I mean dead. About a month ago I followed directions on one of these threads on how to easily and with one click route my jellybean running phone. For some reason the process never completed, and all I was able to accomplish was unlocking the phone. When I ran the check to see if it was truly rooted, the response showed the phone was still unrooted. About 30 days later it was deader than a brick. Somewhere I read that Jellybean on Sprint might be the culprit. Anyway, I have a dead phone. Sprint wouldn't even check it because the screen was cracked. Fortunately, I bought a new one, new to me anyway, on eBay for $37. It is still running android 2.3.7(Gingerbread), and the phone is attempting to push the Ice Cream Sandwich update. I am fighting the update until I figure out what killed my phone.
Just wondering whether there is anything I can do with my old phone, even if I only use it like an old iTouch for music and surfing via Wi-Fi. Anyone?
I attempted the one click method described here, but my desktop cannot find any devices. So it truly is dead. Comments appreciated. I have used several different cables, unsuccessfully.
sexynexy said:
All posts on this thread presuppose a working Nexus S 4g. When I use the term bricked, I mean dead. About a month ago I followed directions on one of these threads on how to easily and with one click route my jellybean running phone. For some reason the process never completed, and all I was able to accomplish was unlocking the phone. When I ran the check to see if it was truly rooted, the response showed the phone was still unrooted. About 30 days later it was deader than a brick. Somewhere I read that Jellybean on Sprint might be the culprit. Anyway, I have a dead phone. Sprint wouldn't even check it because the screen was cracked. Fortunately, I bought a new one, new to me anyway, on eBay for $37. It is still running android 2.3.7(Gingerbread), and the phone is attempting to push the Ice Cream Sandwich update. I am fighting the update until I figure out what killed my phone.
Just wondering whether there is anything I can do with my old phone, even if I only use it like an old iTouch for music and surfing via Wi-Fi. Anyone?
I attempted the one click method described here, but my desktop cannot find any devices. So it truly is dead. Comments appreciated. I have used several different cables, unsuccessfully.
Click to expand...
Click to collapse
Hi,
What method did u use to root? What thread? Cuz it may need to newest version of the recovery.
anyways...
Try charging up a battery on newer phone and put in dead phone... but instead if turning on normally, boot into recovery.
If it worked then use a back up to flash it back to stock. Assuming u were able to back it up b4 root.
If not plug into computer. See if it turns on or can go into either recovery or boat loader mode and if so perhaps computer will recognize it.
Vs Nexus S4G using tapatalk2
Hi.
I don't know much about details about root/room/recovery, but know some about
ODIN, CWM and other ROM to use.
I've been using Humble 5.0 for a while and my phone got unstable recently, so I ODIN the same Humble rom again, but that is how the problem started.
The main problem is, I can't wipe userdata or cache at all.
CWM says it wiped, but I always get Force close, so many that I can't even use the phone normally.
I tried to go back to stock ROM or any other, but all failed.
Stock ROM with stock recovery says, E:Can't mount /dev/block/mmcblk0p1 (Invalid argument). and most of the time, Bootloops.
Humble is the only option I can go into, and actually use the phone, but it has all the apps and data from the past, even though I wipe data/cache thousand times.
I even erased all SD data, formatted in FAT32, and nothing works.
Finalizing my status,
Can't mount...error with Stock ROM.
Bootloop with other ROM.
Constant Force Close with Humble 5.0 (Can't wipe data/cache).
Please help.
So stock, you used ODIN EE4 and PIT file to go back to stock and took the newest update and still have problems?
Thank you for the reply.
Yes. I tried ED1 and EE4, and even with PIT(repartition) and I get "Can't mount..." error.
I went back to Humble 5.0 which has all kind of force close (still showing all app names I had, mysterious), and formatted SD, factory reset, and tried ODIN ED1/PIT, but result is same.
I have a feeling my internal SD partition got screwed.
I am no pro myself.. But I am running GummyCharge Froyo 2.0 which comes with Imoseyon's Kernel and its rock stable even overclocked to 1,200 mhz for me.. You may want to try getting a copy of that as well as flashing with your SIM Card out and Battery in after booting into recovery.. Let me know if this helps at all!
jiehooni said:
Thank you for the reply.
Yes. I tried ED1 and EE4, and even with PIT(repartition) and I get "Can't mount..." error.
I went back to Humble 5.0 which has all kind of force close (still showing all app names I had, mysterious), and formatted SD, factory reset, and tried ODIN ED1/PIT, but result is same.
I have a feeling my internal SD partition got screwed.
Click to expand...
Click to collapse
I had a similar problem but dont remember what I did to fix lol like that helps you. Did you format your sd card on a computer or with your phone? If not try using an adapter and format on computer. Going back to stock has always solved my problems. There is a new cwm that came out. Just throwing stuff out there. Have you tried re downloading images of the stock ee4 and pit? It is loading so shouldnt be a problem , hmm. Maybe someone with more knowledge will pop in.
I tried GummyCharge 2.0.zip from SD but it didn't help.
I tried CWM 5.0, with many ROMs to wipe cache/data, no use.
I formatted my SD on PC, and from phone, same result.
What I don't understand is, even after I flashed Humble 5.0 ROM which I used right before, and only ROM it works now, it shows all apps I had even after many times of Wipe Data/cache/dalvic.
Even funnier, I delete some apps causing Force Close, and I reboot my phone, it always goes back to where I start. Same Home, the app is still there.
It is just weird.
Im getting FC now all of a sudden. It's you fault damn it lol. Said I was gonna reload anyhow. Just didnt want to do it twice in one night. Oh it is past 12pm so I guess it is another day.
It's been now 3 days, and I found this thread hopelessly.
Same problem I think.
http://forum.xda-developers.com/showthread.php?t=1191650&page=2
I hope somebody can help me fix it.
Now I can't even flash Humble, can't even get through recovery(stock or CWM).
I can't do anything now.
I will Odin back to stock and take it to the verizon tomorrow.
Thank you all of you for the help.
Tried a different usb cable, how did you flash the new cwm? So everytime it says pass through ODIN? Are you checking the right selections through ODIN and using PDA? Man just trying to think of everything and thats about it. Get another phone lol. Superuser and busybox?
I tried different USB cable, PC, installed Samsung driver again.
I took the phone to Verizon today, and they can't hard reset it either at that place.
I dropped the phone 3 month ago and it has a little dent, so that they refuse to repair it under warranty. I am sending it to MobileTechVideo tomorrow.
Thank you.
I'm having the same issues. I was on Humble 5.0 and had been using it without a problem for about 2 weeks and yesterday I noticed my phone reboot on it's own. After the reboot it was stuck in the boot loop. I've also tried reflashing Humble 5.0, tried the instructions on the fix your phone thread, tried flashing to stock and also tried the all in one Gingerbread 2.3.6 W/Root/CWR/IMO Kernel 4.0 to see if CWM would help any.
All successfully pass according to Odin, but they all still boot loop and all give error messages in their recovery modes if I try to do anything involving /cache or /data stating that they fail to mount.
Any thoughts would be greatly appreciated.
Okay, I started this thread with the issue of not being able to root. I bit the bullet and wiped it all and ended up being able to root. Now I have a much bigger issue... My phone wont go into storage mode. Not in the OS, not in CWM, not in download mode. It just can't be recognized by a computer. Yes I have the drivers installed, and the phone knows it's plugged in, it will charge and everything, it just wont give me the option to go into storage mode. This will be an issue if I ever need to flash it for any reason since download mode can't be recognized in ODIN. It was working a day ago... Think it's a hardware issue?
JoeVsFox said:
Okay, I started this thread with the issue of not being able to root. I bit the bullet and wiped it all and ended up being able to root. Now I have a much bigger issue... My phone wont go into storage mode. Not in the OS, not in CWM, not in download mode. It just can't be recognized by a computer. Yes I have the drivers installed, and the phone knows it's plugged in, it will charge and everything, it just wont give me the option to go into storage mode. This will be an issue if I ever need to flash it for any reason since download mode can't be recognized in ODIN. It was working a day ago... Think it's a hardware issue?
Click to expand...
Click to collapse
Storage mode and download mode are different to me atleast.
Have you tried settings/usb settings/ask on connection.
When you connect your usb cable from your computer to your phone it should beep and then ask what you want to do. Is your sd card good? Have you checked it maybe on your computer with an adapter?
Or are you talking about getting into ODIN?
Have you usb cable connected to the main usb port. Pull the battery,put it back in, connect the usb cable , hold the volume down button and power key. Worked every time for me. Not sure what else to say from me atleast. Someone else might chime in. Ive done it both with the battery and with out. Try a different usb port.
ODIN Flash Stock
blueis300 said:
So stock, you used ODIN EE4 and PIT file to go back to stock and took the newest update and still have problems?
Click to expand...
Click to collapse
If you have the charge pit file and EE4 you should be able to wipe everything on your phone. If I am correct, this bypasses all permissions and partitions and basically supercedes any roms or data you have. This should work. try another cable on a different usb port or another computer. I have hard brocked my phone numerous times and this was the only workable method. (if you want you can do a little solder job and have phone by fixed with the unbrickable mod here
I already sent my phone to the repair shop.
Btw, it is the normal case you described, but I tried different PCs, drivers, cables, USB slot, nothing works.
Thank you anyway.
blueis300 said:
Storage mode and download mode are different to me atleast.
Have you tried settings/usb settings/ask on connection.
When you connect your usb cable from your computer to your phone it should beep and then ask what you want to do. Is your sd card good? Have you checked it maybe on your computer with an adapter?
Or are you talking about getting into ODIN?
Have you usb cable connected to the main usb port. Pull the battery,put it back in, connect the usb cable , hold the volume down button and power key. Worked every time for me. Not sure what else to say from me atleast. Someone else might chime in. Ive done it both with the battery and with out. Try a different usb port.
Click to expand...
Click to collapse
Tried it with 2 different computers, different cables, different ports. Ask on connection is on. The SD card works fine when I put in in an adapter. The phone just doesn't data connect via usb. ODIN can't find it. Nothing. Pretty sure this is a hardware issue...
My phone just got back from the repair shop and they say they can't fix it. They think NAND got corrupted. Now I am really stuck...Man...
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.
People that can't get the roms beyond stock to work, are your phones activated?
Is it possible to use the Pac Man Rom or CM10 on an unactivated phone?
I'm having similar issues to others trying to flash Pac Man and CM10.2. The first boot was fine and I can access everything on the phone fine, including settings. I rebooted and the activation screen (which I skipped as this phone doesn't have service) always pops up but I would like to use it without putting it on a cell network. I can skip the screen fine (until I decide to disable it) but then have issues like the keyboard (physical and touch), systemUI or NAV Bar crashing with a constant message pop up telling me it has crashed. I have returned to stock using RSD and reflashed Pac Man and CM10.2 MANY (15+?) times, doing a clean install 99% of the time but also trying a couple dirty installs to cover my bases. I should also note that I flashed the phone to Cricket but have no plans to activate it anytime soon.
Another thing to note is that I had issues getting the custom roms to boot at all as the initial setup would take hours. One time I though it was a boot loop but I left it on all night and it had booted in the morning. I believe it has something to do with the file check at boot (with my 32GB low speed class SD card) but that seems to be resolved and I can get the custom roms to boot fine (on the first boot) even with my 32GB (witch is fine and has no errors nor is generic, before you ask.) I also have tried 2 4GB cards and a 2GB card, all different brands, with no change in behavior.
I have done everything below multiple times and in different orders.(If needed I can give a direct breakdown step by step but if you could do it with the files below, I have probably tried it)
Wipe the phone (including all storage internal and external SDs included)
Using RDS v6.15
RDS asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml.zip (Works 100% of the time and never has issues. I keep reverting back to this if I actually need to use the phone)
RDS ClockworkMod, TWRP, and Open Recovery without TWRP (Tried different versions when available)
Then used each recovery to install Pac Man or CM10.2 (tried 10.1 once but had the same issues and I didn't see the need to troubleshoot a rom people seemed to not want to develop for. So 10.1 was only tried once but has the same issues)
Installed GApps at this point but I also tried alternate versions of GApps and not installing it at all. All have the same effect and don't seem to be contributing to the problems at all.
A few installed I tried wiping the phone again or installing each zip multiple times. I also verified the zips were good when on the device to make sure there was no corruption at transfer.
I also tried multiple (confirmed working) SD cards and installing from the internal storage.
I have tried installing arrrghhh's Kernel too.
The issue ether seems to be boot loop (if it's doing a file check) or more often it works until I get one of the said crashes after a reboot.(blame Tyler message is getting SO old...) The time I see the errors seems to be accelerated if I mess with the settings a lot but I don't believe it is directly related to the settings.
My next recourse is to try and flash it back to Sprint (maybe check my Cricket settings) and see if that helps, without it being activated.
On a separate note.
If people need help I can help get you back to stock easily. The instructions/guides on here are all but useless if you don't know what you are doing already. I have seen down to "USE RDS" or "DELETE LINE MD5" like people would just know what that means. I understand RDS Lite is a standard tool for flashing phones but it's nigh impossible to find real explanations on what stuff does in context. I understand the basics though, so if anyone has any questions I can walk you through it.
To start with if you are stuck in a loop at the start of a new rom and it loops between the 'Welcome' Screen (Select your Language) and Activation screen just skip the initial setup by tapping the corners on your screen in a clockwise manor when on the 'Welcome' screen to skip the setup there is a video to explain it here
pocketnow(can't post links )com/how-to/android-quick-tip-how-to-bypass-touch-the-android-to-begin-video
Without doing this or activating the phone it seems to loop between those 2 screens forever (might indicate part of the problem with customs roms....)
I hope this is enough info to go off of I can give you a play by play with the actual files if you need. Maybe a video if needed and I'm feeling extra fancy.
Thanks for your time.
Hey buddy,
If you're trying to make a guide, make sure you call it what it is properly - RSD Lite.
Also, maybe clean up your post a bit so it's a proper guide (as you point out, it's needed) and make a separate thread for your question.
To answer your question, the unactivated phone shouldn't be an issue in of itself - you'll just get the nag screen like you were talking about.
I know there is an issue some are having with rebooting the 4.3 ROM's. Have you tried any 4.2.2 versions of anything? Carbon, CM10.1?
I wonder if your "flash" to Cricket is causing issue, I'm not sure. Let me know about 4.2.
Edit - I missed this part on my first read of your PM. Taking hours to boot is NOT normal. Perhaps remove the SD card entirely, flash using the internal SD... I've never heard of that. Anything over say 20 minutes is probably cause for concern.
Thanks for taking time to answer me.
In no way was I trying to make a guide yet but I guess I could. I just hate posting stuff without useful content so I figured throwing that in was better than nothing. I'll clean it up and set up some links later today. It's frustrating to try and make a full guide before I can post links that would be needed for it. You are totally right though! (complain about crappy guides and kind of make one... )
Part of my point there was that I can't post out of Q and A and this wasn't really a question so I made a question out of it and that's how my post ended up.
I have flashed many phones before but like I said I'll try and put it back on Sprint later today (probably will be a few hours) as I backed up the settings the phone came with. I know it was a wall of text and not the easiest to read so you probably missed it but I also said in my first post that I tried the internal SD card many times and the taking hours to boot isn't the standard and doesn't seem to happen at 99% of the time. It seems to be related to the recovery software I use as it happened a lot more when I was testing TWRP and none when I use clockwork.
What Recovery do you recommend? I swear they aren't made equal...
I tested CM10.1 once and it had the exact same issues as CM10.2 and Pac Man so I didn't test it further but if you want me to test it I can. I just didn't want the Rom.
I don't want Carbon either but I'll test that and AOKP next. It's just annoying that the stock rom works perfect but I can't get these to function at all. I almost wish I didn't get Pac Man to work at all. I'm very particular about my settings and NEED these features after I tried them Pac Man is AMAZING.
Thank you for the help and I hope I can get this worked out.
PS I saw that you were frustrated about working on a rom you don't have a device for. I hope you don't let a little thing like that stop you as, for the little time I have used it, it's all I want. Thanks again.
Blasz said:
What Recovery do you recommend? I swear they aren't made equal...
Click to expand...
Click to collapse
Well, OpenRecovery has probably the most work done for this device specifically. I liked TWRP, but it seems lately it has been unstable - you're not the first who has reported issues lately. I don't think CWM has been updated, unfortunately - but perhaps that's a good thing, it's stable that's for sure.
Blasz- I was just about to start a thread when I found yours, and it very accurately describes the issues I've been having. Here's my progress so far.
I got my Photon Q with Sprint and used it for a few months before Sprint started finding creative ways to take my "$79.99" bill and make it more like $140 a month. Naturally, I refused to pay. So I had a Photon Q with no cell service. This is fine, as I only need it to work on WiFi, not 2G/3G and there is no 4G in the area. Anyway.
At the time, I had Ice Cream Sandwich on it, using the (latest?) ICS firmware from Motorola. This worked very well, but I later tried to use a newer firmware, and all the custom ROMs had shown up while I hadn't been looking. All of these seemed to be based on JellyBean. First off, I tried CyanogenMod 10.2. Worked amazing well! I had literally no problems at all. However, while I was experimenting with different software for the phone, and wanted to see if "Arrrgghh"(sp?)'s kernels would give me some decent overclocking capability. Turns out, the kernel I picked wasn't compatible with the JB firmwares (I probably picked an older one by mistake.) Needless to say, it now wouldn't boot. It'd go to the "Unlocked bootloader" screen and stay there all night (literally, I tried that.)
So, I went back into CWM, which is the recovery I have installed. I erased /data, /cache and /system, and also the dalvik cache and battery stats for good measure. I also formatted /pds and /modem, I believe, which was probably dumb of me since I'm not sure what those do. Then I tried re-installing CM 10.2 from CWM. The installation went fine, and it works gorgeously. However, there's two weird issues:
1) WiFi and Bluetooth don't even BEGIN to work! Neither does Cell, as far as I can tell, because where CM used to be unable to make calls or access the internet (of course, I've not been paying my bill), it now shows an empty signal bar or "No Signal" (the little red X) in the notification bar ... When I try to turn on WiFi using the slider in Settings, it moves to "ON" (stays gray) and pauses for a few secs, then goes back to OFF. Same thing for BT. If I open the WiFi menu where you select an AP, it tells me to turn on WiFi. I do, using the slider up top, and the same thing happens. WiFi and BT simply won't turn on. Tried fiddling with every setting I can find.
Before this misadventure with the kernel/reinstall, WiFi worked great. I connected to a local AP and was surfing the net and downloading apps.
2) The system takes a VERY long time to boot up. It sits at the "Unlocked Bootloader" screen for up to a whole minute. Then it goes to the Cyanogen screen for about 30 seconds. Then it gets to the homescreen. It's fine so long as you let it boot up, but this doesn't seem normal.
Next I tried other ROMs thinking that might help. I installed AOKP, PacMan, CM1.0, Carbon, SlimBean, and I think a few others without results-- they all work but WiFi and BlueTooth are dead. PacMan is the only exception-- it boots up and then endlessly gives me "Blame Tyler" errors until I force the machine to shut off.
I also tried an older ROM, since these are all JellyBean ROMs and I wanted to get back to ICS (I'm not that fond of JB's interface) anyway. I was unable to find any ZIPs I could install through CWM of the stock firmware. I found some IMGs that it looks like I could install via Fastboot, but I don't currently have a PC with admin priveleges (it's not mine) so I can't install the drivers to use Fastboot or any part of the SDK. (I can, however, put files on my SD card, that doesn't require privleges.) The closest ROM I found to stock was "TwistedAsanti" beta-1 or whatever it's called. That installs fine, but again, it takes about 2 straight minutes to boot and it's useless after that:
It gets stuck at "Starting Services..." and will sit there forever, even left there all night. Behind this, a dialog pops up saying no cell networks were found and asking if I want to switch to GSM. (i've been trying GSM and CDMA ROMs all this time, I don't need cell access so I doubt it matters which I use. I'm in the USA.) You can pull down the notification bar and get into the Settings, and even launch a couple programs, but I can't find ANY way to get to a homescreen. Task manager shows Circles is running, which is a widget on the homescreen, so where the heck is that screen? .. I try, again, to turn on WiFi or BT without success. The friggin thing just won't turn on.
Did I eff it up by erasing the "PDS" or "modem" partition? Am I missing something obvious or is my phone just possessed?
In a few days I should have access to a computer where I can hopefully use Fastboot and see about installing a stock firmware (wish me luck). Until then, does anyone have a ZIP file I can flash from CWM to get back to an ICS firmware? I managed to find a copy of the stock firmware, in the form of a dump done from TWRP (in .win files). But as far as I know the only way to install TWRP is using Fastboot, and I've explained why I can't do that. I don't know a way to install TWRP from CWM. Maybe I can do it from CM10.2, if I can put APKs or something on my SD card. I can't get it on the network, so I have to copy all the files manually. Needless to say, it's a pain.
After my frenzy of ROM installing, I got frustrated and decided to see if TwistedAsanti would do SOMETHING if I let it sit at "Starting Services" overnight. To my mistake, I left it under my pillow and the system was quite toasty, and the battery had run dead. Plugging it back into the charger, it made a few worrying clicking noises from the speaker, then the green LED came on. This LED seems to mean "I'm charging, but the battery is too dead to turn on for a while." After it sits there a while, the green LED turns off and it just goes black. Or it goes to BOOTLOADER UNLOCKED and bootloops, or goes to black untilyou fiddle with the power button some more. I can once in a blue moon get to CWM. Sometimes it gets to the homescreen. It will charge up to about 4-7% and no further (battery got damaged by the heat?) It doesn't reliably work when plugged in, it likes to shut off at random anyway.
So now I'm stuck with a phone I can't seem to charge, or turn on reliably, and if I *do* get it to boot up, there's no way to connect it to a network.
Needless to say I'm pretty darn frustrated..
Thanks for any advice.
Epicenter714 said:
So now I'm stuck with a phone I can't seem to charge, or turn on reliably, and if I *do* get it to boot up, there's no way to connect it to a network.
Needless to say I'm pretty darn frustrated..
Thanks for any advice.
Click to expand...
Click to collapse
Did you try to use RSD Lite and flash the device back to stock?
arrrghhh said:
Did you try to use RSD Lite and flash the device back to stock?
Click to expand...
Click to collapse
Currently, I have no PC to use that has Admin priveleges, so I can't install the USB drivers or RSDLite. I also can't use fastboot to install TWRP to use the TWRP .win backups I found.
I did get a roommate to let me use his laptop for 10 minutes to try RSD Lite, but I had this result: Loaded the ".xml.zip" file for the 4.0.4 and 4.1.2 firmwares (after removing the 'getvar' line that causes problems) and it says the phone reported "FAIL". No further details. MiniRSD gives no info from the phone other than the model (it all stays blank), is that supposed to happen? I have the phone in "AP Fastboot" mode so I don't see the problem.
The guy who let me use his PC momentarily is computer-illiterate and thinks anything will break it, so he only let me use it momentarily, and won't let me touch it because I accidentally left an icon on his desktop. I'll have to ask someone else, I think I may know somone..
If I do, how do I get around this error in RSD Lite? Will keep doing research on my own .. thanks!
Epicenter714 said:
Currently, I have no PC to use that has Admin priveleges, so I can't install the USB drivers or RSDLite. I also can't use fastboot to install TWRP to use the TWRP .win backups I found.
I did get a roommate to let me use his laptop for 10 minutes to try RSD Lite, but I had this result: Loaded the ".xml.zip" file for the 4.0.4 and 4.1.2 firmwares (after removing the 'getvar' line that causes problems) and it says the phone reported "FAIL". No further details. MiniRSD gives no info from the phone other than the model (it all stays blank), is that supposed to happen? I have the phone in "AP Fastboot" mode so I don't see the problem.
The guy who let me use his PC momentarily is computer-illiterate and thinks anything will break it, so he only let me use it momentarily, and won't let me touch it because I accidentally left an icon on his desktop. I'll have to ask someone else, I think I may know somone..
If I do, how do I get around this error in RSD Lite? Will keep doing research on my own .. thanks!
Click to expand...
Click to collapse
Well remember - if you are on JB and you are downgrading to ICS, there are additional lines to remove.
Other than that, not sure why it would fail. Make sure 'fastboot devices' works in the command line before doing RSD perhaps.
arrrghhh said:
Well remember - if you are on JB and you are downgrading to ICS, there are additional lines to remove.
Other than that, not sure why it would fail. Make sure 'fastboot devices' works in the command line before doing RSD perhaps.
Click to expand...
Click to collapse
I'm trying to wipe the device clean and install ICS. Are there any other lines I need to remove? ..
As for Fastboot.. I did 'Fastboot Devices' and got no devices listed. How come it shows up in MiniRSD? .. I have the drivers installed, Windows says it installed an ADB device successfully. What are some reasons that might not work? Is there any sort of guide for this? Thank you
---------- Post added at 05:51 PM ---------- Previous post was at 05:29 PM ----------
Oh, as far as the weird booting problem, it seems the battery is fine and the charger died coincidentally at the same time as the overheating did. So my only problem is software now.. thanks.
Epicenter714 said:
I'm trying to wipe the device clean and install ICS. Are there any other lines I need to remove? ..
As for Fastboot.. I did 'Fastboot Devices' and got no devices listed. How come it shows up in MiniRSD? .. I have the drivers installed, Windows says it installed an ADB device successfully. What are some reasons that might not work? Is there any sort of guide for this? Thank you
---------- Post added at 05:51 PM ---------- Previous post was at 05:29 PM ----------
Oh, as far as the weird booting problem, it seems the battery is fine and the charger died coincidentally at the same time as the overheating did. So my only problem is software now.. thanks.
Click to expand...
Click to collapse
I have no clue what MiniRSD is - you mean RSD Lite?
If it doesn't show up in fastboot devices, sort that out before trying to use RSD.
As I stated previously, if you were on JB and going down to ICS you have additional lines which are needed to remove.
Yes, RSD Lite. I don't know where I got MiniRSD from.
I got it to show up in fastboot devices, but adb devices doesn't show it. Weird. Is that OK?
I was able to flash TWRP to the phone with Fastboot. RSD Lite was unable to find the phone. However, I opened the XML file and was able to figure out the flash commands to enter from a command prompt, so I did that:
I got these results... all of the files flashed successfully to stock, except for two. I forget the first, haven't got it in front of me, but here's the big one: SYSTEM! (Important, no?) Here's the error from fastboot:
>> fastboot flash system system.img.ext4
fastboot said:
target reports max download size 31457280 bytes
Invalid sparse file format at header magi
Click to expand...
Click to collapse
(then, Fastboot crashes.)
Does anyone know how to fix that? Also, the system image is way bigger than 31.4 MB. What is it talking about?
Thanks!
Epicenter714 said:
Yes, RSD Lite. I don't know where I got MiniRSD from.
I got it to show up in fastboot devices, but adb devices doesn't show it. Weird. Is that OK?
I was able to flash TWRP to the phone with Fastboot. RSD Lite was unable to find the phone. However, I opened the XML file and was able to figure out the flash commands to enter from a command prompt, so I did that:
I got these results... all of the files flashed successfully to stock, except for two. I forget the first, haven't got it in front of me, but here's the big one: SYSTEM! (Important, no?) Here's the error from fastboot:
>> fastboot flash system system.img.ext4
(then, Fastboot crashes.)
Does anyone know how to fix that? Also, the system image is way bigger than 31.4 MB. What is it talking about?
Thanks!
Click to expand...
Click to collapse
I would NOT recommend entering those fastboot commands in the XML file manually unless you KNOW what you are doing.
Sort out why RSD isn't working. adb and fastboot are two different things. If fastboot devices shows the device, RSD Lite should work fine. Try again.
Hello guys,
Long time reader, first time poster over here.
I'm having a serious problem and wouldn't bother you with it, but i've scrolled through hundreds of forumposts, tried serveral things but haven't find the solution yet. (because the problems in those posts are only a part of my problem :s)
So I hope, by posting and explaining it myself, you guys can help me fixing my HTC One S (wouldn't want to lose it this way -.- )
Here it goes: my phone has been rooted for more than a year now, i've used several ROMs, been through some problems but no big deal and was able to solve them myself).
A couple of months ago, I decided to try the newest Cyanogen (11) mod based on Android 4.4, needed a new recovery but got it installed and working fine.
After a while I installed a Nightly update, and after that the trouble started and went from bad to worse to nearly death
first of all the phone kept rebooting at total random moments, enormously frustrating!
so I decided to do another update, after this update, I wasn't able to turn my Wi-Fi on
No big deal i thought, but after a while it began to annoy me, so another Nightly update was incoming
After this update **** really got messy, the message "com.android.systemui has stopped" kept popping up and the only thing I could do was click OK, then it popped back up -> OK -> and so on and so on
so my phone was as good as useless at this point
At this point I've had it with this ROM, so I put another one on my internal SD card (via coupling with my PC): Beanstalk 4.4 STABLE
This new ROM actually was installed as an update of the previous one, so the damned message "com.android.systemui has stopped" was still popping up constantly.
At that point I totally had it with 4.4 and decided to put an older ROM on it with which i've had had a good experience.
And that's where **** got fcked up:
When I go into recovery (CMW 6.0.4.5) and want to access my internal storage, it says "E: can't mount /storage/sdcard0"
So I wanted to connect to my pc to flash a new ROM to my device using Fastboot, but my pc isn't recognizing my phone and neither is Fastboot.
In fastboot, when I try "fastboot device" it keeps searching and doesn't find my device.
My PC however sees my phone, cause I hear the usbconnection sound when they're coupled, but it isn't showing up as a Removable Storage Device.
So to summarize:
once my phone is booted, i can't do anything apart from clicking OK on the "com.android.systemui has stopped" alert
in recovery, i can't mount my internal storage
when 'connected' to the PC, the PC and fastboot can't detect the device.
Other info:
i've tried it on a pc running W7 and W8
phone is HTC One S S4
I hope you guys can help me out here!
PC connection
DieterW91 said:
Hello guys,
Long time reader, first time poster over here.
I'm having a serious problem and wouldn't bother you with it, but i've scrolled through hundreds of forumposts, tried serveral things but haven't find the solution yet. (because the problems in those posts are only a part of my problem :s)
So I hope, by posting and explaining it myself, you guys can help me fixing my HTC One S (wouldn't want to lose it this way -.- )
Here it goes: my phone has been rooted for more than a year now, i've used several ROMs, been through some problems but no big deal and was able to solve them myself).
A couple of months ago, I decided to try the newest Cyanogen (11) mod based on Android 4.4, needed a new recovery but got it installed and working fine.
After a while I installed a Nightly update, and after that the trouble started and went from bad to worse to nearly death
first of all the phone kept rebooting at total random moments, enormously frustrating!
so I decided to do another update, after this update, I wasn't able to turn my Wi-Fi on
No big deal i thought, but after a while it began to annoy me, so another Nightly update was incoming
After this update **** really got messy, the message "com.android.systemui has stopped" kept popping up and the only thing I could do was click OK, then it popped back up -> OK -> and so on and so on
so my phone was as good as useless at this point
At this point I've had it with this ROM, so I put another one on my internal SD card (via coupling with my PC): Beanstalk 4.4 STABLE
This new ROM actually was installed as an update of the previous one, so the damned message "com.android.systemui has stopped" was still popping up constantly.
At that point I totally had it with 4.4 and decided to put an older ROM on it with which i've had had a good experience.
And that's where **** got fcked up:
When I go into recovery (CMW 6.0.4.5) and want to access my internal storage, it says "E: can't mount /storage/sdcard0"
So I wanted to connect to my pc to flash a new ROM to my device using Fastboot, but my pc isn't recognizing my phone and neither is Fastboot.
In fastboot, when I try "fastboot device" it keeps searching and doesn't find my device.
My PC however sees my phone, cause I hear the usbconnection sound when they're coupled, but it isn't showing up as a Removable Storage Device.
So to summarize:
once my phone is booted, i can't do anything apart from clicking OK on the "com.android.systemui has stopped" alert
in recovery, i can't mount my internal storage
when 'connected' to the PC, the PC and fastboot can't detect the device.
Other info:
i've tried it on a pc running W7 and W8
phone is HTC One S S4
I hope you guys can help me out here!
Click to expand...
Click to collapse
I've had success getting a connection to Windows just be using a different USB port, the ones at the back are best. Then at least you get fastboot access...But I also still have the problem with the sdcard, still working on that, trying to figure out a way to fix it from fastboot...
any progress yet rosanna? I was also able to make the connection with my pc, by using the usb ports on the back (thanks for that!). But I haven't been able to mount my sd card yet. I tried with another recovery but that didn't do the trick.
I got into the UI of my current ROM, and then my pc said I needed to format the SD before I could use it.
But I wasn't sure this is a good idea to do in windows.
Anyone know if it is save to format your internal sd card when prompted to do so in windows?
Have a look here
Sent from my ElementalXed One S
Try using a Linux live cd (try Ubuntu). You'll need a blank DVD to burn the iso to. Reboot your computer and see if it recognizes your device (no drivers needed). If it does try a more stable build this time.
benJX said:
Have a look here
Sent from my ElementalXed One S
Click to expand...
Click to collapse
I did read through that thread and tried it.
But i'm not quite sure everything went as plannend.
I even think it went wrong on the first step, flashing back to the stock recovery. This one isn't included in the all in one toolkit right?
So I started searching for one myself (I have an S4 VLE version of the phone) but I haven't downloaded one yet, although I've seen links that bring me to new links and so on and so on, I wasn't quite sure which link to trust.
If you could help me further I would really appreciate it
DieterW91 said:
I did read through that thread and tried it.
But i'm not quite sure everything went as plannend.
I even think it went wrong on the first step, flashing back to the stock recovery. This one isn't included in the all in one toolkit right?
So I started searching for one myself (I have an S4 VLE version of the phone) but I haven't downloaded one yet, although I've seen links that bring me to new links and so on and so on, I wasn't quite sure which link to trust.
If you could help me further I would really appreciate it
Click to expand...
Click to collapse
1 minute - downloadlink is on the way
Here you are: http://forum.xda-developers.com/attachment.php?attachmentid=2622663&d=1394422408
You can flash it with the toolkit selecting "Custom recovery".
When you're Storage is back alive and kickin' you can flash a custom revovery again.
My favourites are
TWRP 2.7.0.0 - http://techerrata.com/file/twrp2/ville/openrecovery-twrp-2.7.0.0-ville.img
and
PhilZ advanced CWM - http://goo.im/devs/philz_touch/CWM_Advanced_Edition/ville
In my opinion TWRP is easiest to handle and PhilZ has some more features.
DieterW91 said:
I even think it went wrong on the first step, flashing back to the stock recovery. This one isn't included in the all in one toolkit right?
Click to expand...
Click to collapse
Another direct link here, I personally flashed it manually trough fastboot, for me the easiest and fastest way to do it. Then proceed to the clear storage and flash your custom recovery (like @LS.xD I recommend TWRP but this is your choice )
THX Guys! :victory:
Thanks to your links to the stockrecovery, my phone is back alive and kicking.
I feared for a while for my phone, but on the other hand I knew the xda community would help me fix it!
1000 times thanks :good::laugh:
DieterW91 said:
THX Guys! :victory:
Thanks to your links to the stockrecovery, my phone is back alive and kicking.
I feared for a while for my phone, but on the other hand I knew the xda community would help me fix it!
1000 times thanks :good::laugh:
Click to expand...
Click to collapse
Feel free to hit the "thanks" button