My phone upon reboot usually gets stuck on a "Sorry! Process system is not responding" "Force Close" or "Wait".
Neither option works and I have to do a battery pull.
It doesn't matter what ROM I use it always happens.
Would someone be able to tell me how to get a log from bootup? And would someone be willing to look at the log for me?
Thanks guys!
Sent from my PG86100 using XDA Premium App
tes5884 said:
My phone upon reboot usually gets stuck on a "Sorry! Process system is not responding" "Force Close" or "Wait".
Neither option works and I have to do a battery pull.
It doesn't matter what ROM I use it always happens.
Would someone be able to tell me how to get a log from bootup? And would someone be willing to look at the log for me?
Thanks guys!
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
I don't mean to sound like a tool by suggesting this, but, have you wiped? Wipe cache and dalvik to start off with see if that works...and if it doesn't do a full wipe and get back to us.
Again, I'm not trying to be a ****...if you are beyond this level of help, well, we're gunna need more details.
i can tell you how to get a log but i cant tell you whats wrong using the log
plug your phone into your computer, using adb type in "adb logcat" and press enter and you should see a whole bunch of text start appearing
before you flash a rom do you do factory resets and make sure to wipe your cache and dalvik cache? that could be the problem..
I have done it all, wiped dalvik, cache, and everything else. I even tried using CWM instead of twrp and the issue remains.
Thanks everyone for trying to help...
Sent from my PG86100 using XDA Premium App
tes5884 said:
I have done it all, wiped dalvik, cache, and everything else. I even tried using CWM instead of twrp and the issue remains.
Thanks everyone for trying to help...
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
If you've done a full wipe and tried different roms then I would be inclined to believe that the issue is likely hardware.
tes5884 said:
I have done it all, wiped dalvik, cache, and everything else. I even tried using CWM instead of twrp and the issue remains.
Thanks everyone for trying to help...
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
I would use TWRP and do this:
Go into wipe menu, then Wipe cache, wipe dalvik, wipe data (factory reset). Go into advanced menu (I think) and there should be another wipe menu. Wipe /system. Then flash the ROM of your choice and it should be fixed. Wiping /system manually is the key since some ROMs don't do that (mine does, however)
Thanks ill try the advanced system wipe.
Sent from my PG86100 using XDA Premium App
Negative I tried formatting system and all the rest. It didn't work. The strange thing is when I remove my sdcard it boots fine, I tried a second sdcard and the same issue.
Thanks again guys.
Sent from my PG86100 using XDA Premium App
Another strange thing is, when I reboot via "adb reboot" it works fine...
tes5884 said:
Negative I tried formatting system and all the rest. It didn't work. The strange thing is when I remove my sdcard it boots fine, I tried a second sdcard and the same issue.
Thanks again guys.
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
stock card?
daneurysm said:
stock card?
Click to expand...
Click to collapse
none of these are stock card, I cant seem to find my stock card.
As a matter of fact I dont think I ever even booted with my stock card. Do you think that can be the issue?
Thanks
tes5884 said:
none of these are stock card, I cant seem to find my stock card.
As a matter of fact I dont think I ever even booted with my stock card. Do you think that can be the issue?
Thanks
Click to expand...
Click to collapse
In a word, yes. Are any of these 'bargain' cards you got online by chance? If not and they are from a reputable vendor I would put them in the computer, copy data off and format them....and if that still doesn't help find a 'known good' card and go on from there. The stock card would be preferable, but, if you can't find that a 'known good' card is the next best thing. If the stock card or a 'known' good card doesn't help I'm still inclined to think it's a hardware error...but after hearing about the SDcard I'm leaning towards the phone is fine the card is screwed.
daneurysm said:
In a word, yes. Are any of these 'bargain' cards you got online by chance? If not and they are from a reputable vendor I would put them in the computer, copy data off and format them....and if that still doesn't help find a 'known good' card and go on from there. The stock card would be preferable, but, if you can't find that a 'known good' card is the next best thing. If the stock card or a 'known' good card doesn't help I'm still inclined to think it's a hardware error...but after hearing about the SDcard I'm leaning towards the phone is fine the card is screwed.
Click to expand...
Click to collapse
ok I appreciate the help and I will look for a new card.
Went to a sprint store, they said its probably a hardware issue and they ordered me a new one.
Here's to hoping the new one one won't have any issues....
I appreciate all the help from you guys.
Sent from my PG86100 using XDA Premium App
Related
Hey guys, I'm another newbie who F'ed up their phone here to ask for help lol. I tried to do a restore using the system recovery and it froze, I did a batter pull and soft bricked it I guess. I tried doing a sbf, and I couldn't figure it out but my phone just randomly restarted and it seemed like the sbf worked. So I just tried to restore the data only in advanced recovery and I think it is frozen again. Can anyone please explain how to do a proper restore from the bootstrap recovery? Thanks,
CominWitDaSauce said:
Hey guys, I'm another newbie who F'ed up their phone here to ask for help lol. I tried to do a restore using the system recovery and it froze, I did a batter pull and soft bricked it I guess. I tried doing a sbf, and I couldn't figure it out but my phone just randomly restarted and it seemed like the sbf worked. So I just tried to restore the data only in advanced recovery and I think it is frozen again. Can anyone please explain how to do a proper restore from the bootstrap recovery? Thanks,
Click to expand...
Click to collapse
At The Recovery Screen It's Backup & Restore>External SD Card Or Internal SD Card(Wherever You Saved To)>Restore>(Yourfilename). Example: 2011-07-26.23.36.03/
MikeJ92YJ said:
At The Recovery Screen It's Backup & Restore>External SD Card Or Internal SD Card(Wherever You Saved To)>Restore>(Yourfilename). Example: 2011-07-26.23.36.03/
Click to expand...
Click to collapse
That's exactly what I did and now it says
Checking MD5 sums...
Restoring Data...
6860ba6
And the progress bar is just not moving and has not even started to fill in.
Am I just impatient? How long should it take, I gave it 15 minutes before I pulled the battery last time, should I wait longer this time?
Plz help
Sounds Like You Got A Corrupted Backup There. I Would Try Another One Or SBF And Start Over. (It Sucks I Know I've Done It A Dozen Times.)
MikeJ92YJ said:
Sounds Like You Got A Corrupted Backup There. I Would Try Another One Or SBF And Start Over. (It Sucks I Know I've Done It A Dozen Times.)
Click to expand...
Click to collapse
Alright, thanks.
Are You Running A ROM?
MikeJ92YJ said:
Are You Running A ROM?
Click to expand...
Click to collapse
Yes, Affinty.
I'm Working On Uploading The Affinity ROM As A Nandroid File For You To Simply Put On Your SD Card /clockworkmod And Restore Using Mine. Wipe Data/Cache.
Or You've Already Begun The Process Of SBF'ing?
MikeJ92YJ said:
I'm Working On Uploading The Affinity ROM As A Nandroid File For You To Simply Put On Your SD Card /clockworkmod And Restore Using Mine. Wipe Data/Cache.
Or You've Already Begun The Process Of SBF'ing?
Click to expand...
Click to collapse
No, that would be great, thank you!
I'm Uploading The Zip Now. Unzip The File Place Into Your clockworkmod/backup Folder. Perform A Restore Like Normal Before Rebooting Wipe Data/Cache To Be Sure Things Load Smoothly.
Perfect thanks!
Sent from my DROID X2 using XDA Premium App
Ok, do I just did a back up through nandroid to see if I could find a problem, and towards the end, it said something like,
Did not find sdcard-ext
Skipping backup of sdcard-ext
Our something like that, I'm thinking thats a problem, but I have an external sd card.
Sent from my DROID X2 using XDA Premium App
It Says About 15 More Minutes Until Done.
Couple Key Things Here Is That This Is Fully Deodexed. I Switched The vold.fstab File To Switch SD Card. Stock Messaging App Has Been Replaced With CM6's Latest. I'm Pretty Sure All Authentication Services Have Been Deleted.
CominWitDaSauce said:
Ok, do I just did a back up through nandroid to see if I could find a problem, and towards the end, it said something like,
Did not find sdcard-ext
Skipping backup of sdcard-ext
Our something like that, I'm thinking thats a problem, but I have an external sd card.
Sent from my DROID X2 using XDA Premium App
Click to expand...
Click to collapse
I Know What You're Talking About But I Can't Think Off The Top Of My Head. Something Tells Me That Has To Do With MD5 Sums.
MikeJ92YJ said:
It Says About 15 More Minutes Until Done.
Couple Key Things Here Is That This Is Fully Deodexed. I Switched The vold.fstab File To Switch SD Card. Stock Messaging App Has Been Replaced With CM6's Latest. I'm Pretty Sure All Authentication Services Have Been Deleted.
Click to expand...
Click to collapse
I was going to deodex but it seemed too complicated and I didn't know what it did exactly. Do you have super charger script? I know nothing about cm6, but I'll try it, thanks again, your helping me out a lot.
Sent from my DROID X2 using XDA Premium App
CominWitDaSauce said:
I was going to deodex but it seemed too complicated and I didn't know what it did exactly. Do you have super charger script? I know nothing about cm6, but I'll try it, thanks again, your helping me out a lot.
Sent from my DROID X2 using XDA Premium App
Click to expand...
Click to collapse
Yup Super Is In It, You'll Have To Rerun Yours Again Anyways. Speaking Of Scripts I Also Applied The 3G Turbo. The New GPS, Host, And Profile Files Are Also In This.
Here's The Link To Download It.
https://rapidshare.com/files/1324042949/Affinity_ROM.rar
THIS IS NOT MY ROM, THIS IS ONLY MY NANDROID BACKUP.
Wow, I Have Too Much Going On That I Failed To Realize All You Need To Do Is Reinstall The Affinity ROM. If It Doesn't Boot Successfully Then Do A Factory Reset.
I might be confused but it looks like I have to pay to download this?
Sent from my DROID X2 using XDA Premium App
CominWitDaSauce said:
I might be confused but it looks like I have to pay to download this?
Sent from my DROID X2 using XDA Premium App
Click to expand...
Click to collapse
Well You Could Pay And Buy A Membership Totally Up To You
OR
You Could Click The "Free Download" At The Bottom Right.
So I wanted to change my keyboard... In fact I *did* change my keyboard.
At first whenever I wanted to use the keyboard (for notepad for example) it would say something like "Unable to reach" but after a while the keyboard just started working.
Then I switched on wifi and everything started crashing with the usual "Unfortunately (insert every task) has stopped working".
I know I can probably solve this by doing a factory wipe... but I also know that there MUST be a better way to solve this problem.
I have adb installed. I have Siyah kernel.
I can access the whole damned phone from my laptop in or out of recovery mode. I just don't know where to look to fix the problem.
A possible clue:
I tried flashing Keyboard-Blau.zip when my keyboard wasn't working. But CWM aborted the flash with an unknown error.
This is very similar to what happened the last time I had this problem. The only thing in the zip anyway was AXT9IME.apk in the system/app folder.
Any ideas would be appreciated.
P.S. I have also wiped cache and davlak cache AND attempted to install a rom. All permissions in system/app seem fine.
Could it be that system is mounted as r/w somehow?
EDIT2: Just now when I tried to to wipe dalvik (sp) cache it said something about:
"Unknown volume for path sd-ext"
Just a note.
Also I have erased /system then installed the rom again and it's still acting up.
TeamRainless said:
So I wanted to change my keyboard... In fact I *did* change my keyboard.
At first whenever I wanted to use the keyboard (for notepad for example) it would say something like "Unable to reach" but after a while the keyboard just started working.
Then I switched on wifi and everything started crashing with the usual "Unfortunately (insert every task) has stopped working".
I know I can probably solve this by doing a factory wipe... but I also know that there MUST be a better way to solve this problem.
I have adb installed. I have Siyah kernel.
I can access the whole damned phone from my laptop in or out of recovery mode. I just don't know where to look to fix the problem.
A possible clue:
I tried flashing Keyboard-Blau.zip when my keyboard wasn't working. But CWM aborted the flash with an unknown error.
This is very similar to what happened the last time I had this problem. The only thing in the zip anyway was AXT9IME.apk in the system/app folder.
Any ideas would be appreciated.
P.S. I have also wiped cache and davlak cache AND attempted to install a rom. All permissions in system/app seem fine.
Could it be that system is mounted as r/w somehow?
EDIT2: Just now when I tried to to wipe dalvik (sp) cache it said something about:
"Unknown volume for path sd-ext"
Just a note.
Also I have erased /system then installed the rom again and it's still acting up.
Click to expand...
Click to collapse
What rom are you on? Did you do a full wipe when you flashed it?
Sent from my GT-P7510 using xda premium
kilometers4 said:
What rom are you on? Did you do a full wipe when you flashed it?
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
Wanamlite. Latest version. And I sure did...
TeamRainless said:
Wanamlite. Latest version. And I sure did...
Click to expand...
Click to collapse
What keyboard did you choose? One from the play store?
Edit : have you tried to flash the rom over what you have now, with no wipe?
Sent from my GT-P7510 using xda premium
kilometers4 said:
What keyboard did you choose? One from the play store?
Edit : have you tried to flash the rom over what you have now, with no wipe?
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
Yes I tried it.
And somebody had uploaded the stock, touchwiz keyboard. So I copyed it over and set the permissions correctly.
TeamRainless said:
Yes I tried it.
And somebody had uploaded the stock, touchwiz keyboard. So I copyed it over and set the permissions correctly.
Click to expand...
Click to collapse
Hmm.. The only thing I can think of is wiping cache, dalvik one more time EDIT: and try to fix permissions from cwmr. If that doesn't work I would make a nandroid backup and flash your rom with a full wipe again to see if that fixes it. At least you can restore the backup if it doesn't
Sent from my GT-P7510 using xda premium
kilometers4 said:
Hmm.. The only thing I can think of is wiping cache, dalvik one more time EDIT: and try to fix permissions from cwmr. If that doesn't work I would make a nandroid backup and flash your rom with a full wipe again to see if that fixes it. At least you can restore the backup if it doesn't
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
Yeah I know a full wipe will fix it. I've already done that and screwed it up again a few more times for testing purposes.
My point is that there SHOULD be a way to fix it without a full wipe.
I mean if you've got root access, CWM recovery, AND you can actually boot the phone and access adb at the home screen... Then it should be possible to fix the problem.
It's a shame android dosnt return an error telling you WHY something is crashing. Then it would be a cinch.
TeamRainless said:
Yeah I know a full wipe will fix it. I've already done that and screwed it up again a few more times for testing purposes.
My point is that there SHOULD be a way to fix it without a full wipe.
I mean if you've got root access, CWM recovery, AND you can actually boot the phone and access adb at the home screen... Then it should be possible to fix the problem.
It's a shame android dosnt return an error telling you WHY something is crashing. Then it would be a cinch.
Click to expand...
Click to collapse
What keyboard are you trying?
Sent from my GT-P7510 using xda premium
kilometers4 said:
What keyboard are you trying?
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
This one: http://forum.xda-developers.com/showthread.php?t=1483428
...from post #2. Then I tried the zip in post 3 and four. (If you'd like to replicate the error just backup your /data then you can do whatever the hell you want and just restore /data and you'll have everything.) Then I tried flashing the zip from post 3 or 4... which didn't work. Followed the directions for changing permissions on the keyboard.
I hadn't realized you could backup everything from CWM Recovery. And hadn't even considered that just restoring /data would work without screwing everything up again... but work it did! Wish I had realized that a couple of weeks ago... but I didn't really want that data anyway.
Basically I just want the touchwiz keyboard because the standard android one is too small for my hands.
But I can't quite figure out how changing two files... and even changing them back later... could crash the whole damned OS beyond repair.
TeamRainless said:
This one: http://forum.xda-developers.com/showthread.php?t=1483428
...from post #2. Then I tried the zip in post 3 and four. (If you'd like to replicate the error just backup your /data then you can do whatever the hell you want and just restore /data and you'll have everything.) Then I tried flashing the zip from post 3 or 4... which didn't work. Followed the directions for changing permissions on the keyboard.
I hadn't realized you could backup everything from CWM Recovery. And hadn't even considered that just restoring /data would work without screwing everything up again... but work it did! Wish I had realized that a couple of weeks ago... but I didn't really want that data anyway.
Basically I just want the touchwiz keyboard because the standard android one is too small for my hands.
But I can't quite figure out how changing two files... and even changing them back later... could crash the whole damned OS beyond repair.
Click to expand...
Click to collapse
It might be a bad zip/apk file
Sent from my GT-P7510 using xda premium
kilometers4 said:
It might be a bad zip/apk file
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
It absolutely was. But what did it do and how could I fix it?
Story:
First a factory reset from the phone.
I have wiped all, battery stats, user files, caches and Dalvik cache, all you can wipe from Clockwork.
Then I formated everything that you can format in Clockwork.
After this I flashed original firmware (unbranded version though) from Odin.
I got rid of the problems I had except one.
Every time I reboot the phone warns that I lost connection for roaming, until I start internet.
Only I have roaming disabled in settings.
Also there was STILL files left in the phone, the folder and files accepted via bluetooth on internal sd card.
I don't know if there's anything else left but these files showed up in Gallery.
How can this be after I reset, wiped and formatted everything? Makes no sense to me.
I really have no idea what to do.
Cant find anything similar in threads to find sollutions from.
And it seems to be pointless to wipe and reformat yet another time.
Any tips at all to get me started would be really great!
You have to manually delete everything. Clockwork does not delete storage files.
Sent from my GT-I9300 using Tapatalk 2
have u tried flashing the latest modem ?
Sent from my GT-I9300 using xda premium
joshnichols189 said:
You have to manually delete everything. Clockwork does not delete storage files.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I know, I meant the system reset, wipe and formats.
But even in CW there is options to format system amongst other tings, that should have done it I think?
vegeta1 said:
have u tried flashing the latest modem ?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Hmm.. no I haven't.
Samsung support thinks the 3G chip is broken? I don't know about that?
I first noticed that when I went to take pictures that a toast message would popup that said something along the lines of "Unable to save file to sdcard due to insufficient file privaleges". Originally I thought it was the Rom at fault which I will leave nameless beings that its occoring with every Rom I've flashed since as well. But only after switching between the 3 Roma I had saved on my sdcard prior to this incident, I tried to download a newer Rom to see if it was a bug that had been fixed but couldn't download anything to my sdcard. The only time I can download is through the market or via adb push so I know the internal storage isn't broken, but not recieving the correct permissions.
Has anyone else experienced this or have a fix because I don't want to bring the phone back "re-locked" and ask for a replacement. But I also do not want to buy a new phone or go through asurion. Thanks in advance and happy hollidays!
Sent from my HTC6435LVW using xda premium
Sjflowerhorn said:
I first noticed that when I went to take pictures that a toast message would popup that said something along the lines of "Unable to save file to sdcard due to insufficient file privaleges". Originally I thought it was the Rom at fault which I will leave nameless beings that its occoring with every Rom I've flashed since as well. But only after switching between the 3 Roma I had saved on my sdcard prior to this incident, I tried to download a newer Rom to see if it was a bug that had been fixed but couldn't download anything to my sdcard. The only time I can download is through the market or via adb push so I know the internal storage isn't broken, but not recieving the correct permissions.
Has anyone else experienced this or have a fix because I don't want to bring the phone back "re-locked" and ask for a replacement. But I also do not want to buy a new phone or go through asurion. Thanks in advance and happy hollidays!
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
Backup everything from your storage. Go into recovery and format /sdcard. I had the same thing happen. Worked fine after the format and restoring the files.
I'm getting ready to head home so ill do it when I get there. Should I format it in cwmr recovery or through settings just so I make sure I do it the way you did it. Less room for error lol. And thanks a lot I'm really hoping that it helps! I miss having the camera mostly for taking pictures of my 14 month old Son Hambo!
Sent from my HTC6435LVW using xda premium
Sjflowerhorn said:
I'm getting ready to head home so ill do it when I get there. Should I format it in cwmr recovery or through settings just so I make sure I do it the way you did it. Less room for error lol. And thanks a lot I'm really hoping that it helps! I miss having the camera mostly for taking pictures of my 14 month old Son Hambo!
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I did it from in CWM recovery.
Flak_Munky said:
I did it from in CWM recovery.
Click to expand...
Click to collapse
Thanks, and That's what she said. . Lol
Edit : when I format my sdcard, will I have to reflash afterwards or will I still have functionality?
Sent from my HTC6435LVW using xda premium
No reflash needed. Just format and reboot.
Flak_Munky said:
No reflash needed. Just format and reboot.
Click to expand...
Click to collapse
Your my hero!
Sent from my HTC6435LVW using xda premium
Still having problems
Flak_Munky said:
I did it from in CWM recovery.
Click to expand...
Click to collapse
How do you do it through TWRP? I'm having this issue and I can't figure out how to get it to go away either.
Thanks!
Hey all. Can anyone tell me exactly what "success rebooting by reason oem-00" means? And why is it every time I boot into recovery I get can't mount cache/recovery/command. I believe its my sdcard. Thanks!
Sent from my PG86100 using xda app-developers app
AGoogleUser said:
Hey all. Can anyone tell me exactly what "success rebooting by reason oem-00" means? And why is it every time I boot into recovery I get can't mount cache/recovery/command. I believe its my sdcard. Thanks!
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
I doubt it's your SDcard. Its mount point is at /sdcard, not /cache. Sounds like you either need to wipe your cache or you're trying to do something with s-off when you're still s-on.
This is making the assumption that you're trying to flash an update via recovery. If not, please ignore.
Tourney3p0 said:
I doubt it's your SDcard. Its mount point is at /sdcard, not /cache. Sounds like you either need to wipe your cache or you're trying to do something with s-off when you're still s-on.
This is making the assumption that you're trying to flash an update via recovery. If not, please ignore.
Click to expand...
Click to collapse
I'm completely stock. Just when I make a selection in recovery I get a bunch of errors. I can't factory reset, well I can but it won't fix the problem. I can run an ruu over and over and still get the same errors. I'm just wondering what the success reboot means and why it won't let me choose anything in recovery. Should I flash 4ext?
Sent from my PG86100 using xda app-developers app
Ya me to think its sd card problem i recomennd format card ree root re install clock work mod it will fix it .....
HOPE SO
DONT JUST SAY THANKS CLICK IT..
Sent from my LG-P500 using xda premium t from my LG-P500 using xda premium
harshgpt816 said:
Ya me to think its sd card problem i recomennd format card ree root re install clock work mod it will fix it .....
HOPE SO
DONT JUST SAY THANKS CLICK IT..
Sent from my LG-P500 using xda premium t from my LG-P500 using xda premium
Click to expand...
Click to collapse
I've already formatted, without backing up my picture music ect.., and still won't fix. What could be causing the ruu not to fix my phone?
Sent from my PG86100 using xda app-developers app
It still sounds to me like it's not an SDcard issue since the mountpoint isn't /sdcard, but after looking at some Google results I could be wrong. Do you still get the error if you boot with the SDcard removed?
Tourney3p0 said:
It still sounds to me like it's not an SDcard issue since the mountpoint isn't /sdcard, but after looking at some Google results I could be wrong. Do you still get the error if you boot with the SDcard removed?
Click to expand...
Click to collapse
I'm not sure. But I really don't wanna pull the sd. That requires taking the battery out and if I do that I'm stuck in a boot loop.
Sent from my PG86100 using xda app-developers app
I believe you can unseat the SD card without entirely removing it or the battery. If not, no big deal.
What method are you using to flash the RUU? It seems to me like the installer would automatically wipe the /cache directory, but that's probably not a safe assumption to make. At this point it couldn't hurt to install 4ext and make absolutely sure all partitions other than sdcard are wiped. Also, do you get any mount errors other than /cache/recovery/command?
I would try the following, seeing if there is progress after each step:
1) Unseat the sdcard without removing the battery, if possible. If not then skip this step.
2) Install 4ext and wipe cache (all cache, not just davlik)
3) Remove battery and remove sdcard. I know this sucks and you'll get boot loops, but it doesn't matter because the next step is:
4) Wipe all partitions other than sdcard. Even wipe sdcard if you've got a backup. Then attempt an RUU install.
If none of these work, I'm out of ideas. Maybe someone else can chime in. I know there used to be a lot of reports from other devices about /cache/recovery/command and some other directories not being mountable when the eMMC died. It's possible yours is dying and the cache is getting corrupted by hardware failure. That's a worst case scenario, but we gotta eliminate all other possibilities before we make that call.
Tourney3p0 said:
I believe you can unseat the SD card without entirely removing it or the battery. If not, no big deal.
What method are you using to flash the RUU? It seems to me like the installer would automatically wipe the /cache directory, but that's probably not a safe assumption to make. At this point it couldn't hurt to install 4ext and make absolutely sure all partitions other than sdcard are wiped. Also, do you get any mount errors other than /cache/recovery/command?
I would try the following, seeing if there is progress after each step:
1) Unseat the sdcard without removing the battery, if possible. If not then skip this step.
2) Install 4ext and wipe cache (all cache, not just davlik)
3) Remove battery and remove sdcard. I know this sucks and you'll get boot loops, but it doesn't matter because the next step is:
4) Wipe all partitions other than sdcard. Even wipe sdcard if you've got a backup. Then attempt an RUU install.
If none of these work, I'm out of ideas. Maybe someone else can chime in. I know there used to be a lot of reports from other devices about /cache/recovery/command and some other directories not being mountable when the eMMC died. It's possible yours is dying and the cache is getting corrupted by hardware failure. That's a worst case scenario, but we gotta eliminate all other possibilities before we make that call.
Click to expand...
Click to collapse
Yes when I try to wipe the cache in stock recovery I get a bunch of mourning errors. Recovery.log last.log and a few others. I'll try yo get the SD out. If not I'll install 4ext and try to wipe cache. How would I go about wiping my partitions? I can use 4ext without root correct? Thanks!
Sent from my PG86100 using xda app-developers app
AGoogleUser said:
Yes when I try to wipe the cache in stock recovery I get a bunch of mourning errors. Recovery.log last.log and a few others. I'll try yo get the SD out. If not I'll install 4ext and try to wipe cache. How would I go about wiping my partitions? I can use 4ext without root correct? Thanks!
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Installing 4ext without root should be no problem. Just make sure the device is unlocked using the HTC Dev Tool (mandatory). Then go through the flashboot process for recovery.img. It couldn't hurt to install SuperSU while you're in there, though that's outside the scope of what we're trying to repair right now. Once you're in 4ext, under the Wipe menu, there should be an option for "Wipe all partitions other than sdcard" (paraphrased). Go with that. Though if the stock recovery didn't do it, I don't have high hopes for 4ext to be able to.
The fact that you're getting multiple mounting errors leads me to believe you have a bad eMMC. If all the steps from the previous post fail, that'll tell you for sure.
Tourney3p0 said:
Installing 4ext without root should be no problem. Just make sure the device is unlocked using the HTC Dev Tool (mandatory). Then go through the flashboot process for recovery.img. It couldn't hurt to install SuperSU while you're in there, though that's outside the scope of what we're trying to repair right now. Once you're in 4ext, under the Wipe menu, there should be an option for "Wipe all partitions other than sdcard" (paraphrased). Go with that. Though if the stock recovery didn't do it, I don't have high hopes for 4ext to be able to.
The fact that you're getting multiple mounting errors leads me to believe you have a bad eMMC. If all the steps from the previous post fail, that'll tell you for sure.
Click to expand...
Click to collapse
Okay. Just gotta wait since I let my dad borrow my laptop. Should be home soon. If it is emmc, where does that put the phone? Beyond repair? If so I'm not to worried since I'm upgrade eligible soon. Just worried that I'm gonna get stuck in a bootloop and have to use the recovery option from fast boot since thats the only thing that cures the bootloop (until next battery pull) and start over again. Pain in the butt!
Sent from my PG86100 using xda app-developers app
I would recommend that you do a Titanium Backup, but since you don't have root that's out of the question. Kind of an unfortunate situation. I've never done this, but it seems like you could probably use Online Nandroid to make a nandroid backup of your working system. Then if you ever get stuck in a boot loop, you could restore the backup to your current (hopefully) working configuration. It doesn't help you right now, but it might help in the future. Just make sure to root it while you're doing all this.
I believe eMMC is on the main logic board. You might want to call Sprint to confirm, but it stands to reason that you could probably swap in another one. I'm noticing a couple on eBay in the 30-40 dollar range. Not sure if there are any phone-specific values on the logic board that make the board unswappable, but hopefully Sprint could tell you for sure.
Maybe you'll get lucky and that's not the problem anyway.
Tourney3p0 said:
I would recommend that you do a Titanium Backup, but since you don't have root that's out of the question. Kind of an unfortunate situation. I've never done this, but it seems like you could probably use Online Nandroid to make a nandroid backup of your working system. Then if you ever get stuck in a boot loop, you could restore the backup to your current (hopefully) working configuration. It doesn't help you right now, but it might help in the future. Just make sure to root it while you're doing all this.
I believe eMMC is on the main logic board. You might want to call Sprint to confirm, but it stands to reason that you could probably swap in another one. I'm noticing a couple on eBay in the 30-40 dollar range. Not sure if there are any phone-specific values on the logic board that make the board unswappable, but hopefully Sprint could tell you for sure.
Maybe you'll get lucky and that's not the problem anyway.
Click to expand...
Click to collapse
Normally i use App Monster Pro. No root. Im going to back up and and flash the recovery right now. Ill let you know what happens. Hopefully this works.
well i removed the battery and sd card and replaced the battery and she booted up fine! no bootloop this time. Maybe its the sd after all? but i think your right cause i get cant mount cache recovery command and thats not on the sd like you said. Im going to boot back down, remove battery reinstall sd and then see if it boots up.
EDIT: reinserted sdcard and it booted up fine AGAIN. Why phone?! haha. Wonder what was causing the bootlooping when the battery was removed?
I checked for those locations in my cache directory and they don't exist for me either. That probably means they're created dynamically during recovery, but I know very little about what happens behind the scenes there. Maybe certain parts of your cache are unwriteable. Just to clarify, the mount errors happened even while the sd card was out and continued to exist even after it was put back in, right? Maybe it's the sd card after all if not. Any errors while wiping all the partitions?
Glad to hear that it's at least sort of working for now. Couldn't hurt to do a nandroid backup anyway just in case it happens again while you're out and about and don't have time to do a full manual reinstall.
Tourney3p0 said:
I checked for those locations in my cache directory and they don't exist for me either. That probably means they're created dynamically during recovery, but I know very little about what happens behind the scenes there. Maybe certain parts of your cache are unwriteable. Just to clarify, the mount errors happened even while the sd card was out and continued to exist even after it was put back in, right? Maybe it's the sd card after all if not. Any errors while wiping all the partitions?
Glad to hear that it's at least sort of working for now. Couldn't hurt to do a nandroid backup anyway just in case it happens again while you're out and about and don't have time to do a full manual reinstall.
Click to expand...
Click to collapse
Haven't flashed the recovery just yet. My primary goal was to get this boot looping to stop. Success! I will flash recovery tonight. And I haven't checked the recovery.
Sent from my PG86100 using xda app-developers app