Android 5.1 Possibly Coming February 2015

Google released Android 5.0 just over a month ago, and since then Lollipop has been trying to … more

Double Tap to Wake on the Nexus 6 Without Root

A few weeks ago, we featured an app which allowed the Nexus 6 to regain the double tap to wake … more

Make Your Own Heat Sink for the LG Optimus 4X HD

Its not a rare occurrence that performing a resource heavy task on your Android device (e.g. … more

Learn How to Create an Old School Dialer

XDA is not only a great source for custom ROMs, kernels, and various modifications for numerous … more

Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[Q] D-INC Won't Boot

OP spcagigas

22nd January 2014, 06:31 PM   |  #1  
OP Senior Member
Flag Metro Detroit
Thanks Meter: 31
 
151 posts
Join Date:Joined: Jan 2010
More
Hi All,
I searched for this, and didn't see anything, so please forgive me if this has been covered before...

My son has an Incredible that was updated to Evervolv last month (I'd tell you the exact build, but...). The day before yesteday, it crashed with the error message saying process android.phone has stopped. The screen was unresponsive at that point, and the phone wouldn't shutdown by holding the power button down (tried holding it for over a minute, and nothing...). I pulled the battery and tried to restart the phone. Everything seemed to be booting normal, but he'd immediately get either the "process.android.phone has stopped" or "process.android.media has stopped" (or both in succession), and the phone would then freeze. Pulled the battery again and booted into recovery (CM ver. 5.0.2.0) to wipe cache and Dalvik cache, but am getting errors there as well:

E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log

I did try to wipe the cache and Dalvik cache, and it seemed to do that OK (at least, doing so didn't throw any other errors), but that didn't fix the bootloop problem. Next, tried to do a factory reset from recovery. Got the following results:

-- Wiping data...
Formatting /data...
Formatting /cache...
Formatting /datadata...
E:format_volume: no MID partition "datadata"
Formatting /sd-ext...
No app2sd partition found. Skipping format of /sd-ext. (No problem -- no SD card installed)
Formatting /sdcard/.android_secure...
Error mounting /sdcard/.android_secure!
Skipping format...
Data wipe complete.

Rebooted, and still stuck in bootloop...

So, any ideas on what I should try next to get this phone up and running again? I haven't run into this much trouble with this phone before.

Thanks, and Saludos!
SPC
23rd January 2014, 12:05 AM   |  #2  
Senior Member
Flag Nevada
Thanks Meter: 77
 
889 posts
Join Date:Joined: May 2008
More
Quote:
Originally Posted by spcagigas

Hi All,
I searched for this, and didn't see anything, so please forgive me if this has been covered before...

My son has an Incredible that was updated to Evervolv last month (I'd tell you the exact build, but...). The day before yesteday, it crashed with the error message saying process android.phone has stopped. The screen was unresponsive at that point, and the phone wouldn't shutdown by holding the power button down (tried holding it for over a minute, and nothing...). I pulled the battery and tried to restart the phone. Everything seemed to be booting normal, but he'd immediately get either the "process.android.phone has stopped" or "process.android.media has stopped" (or both in succession), and the phone would then freeze. Pulled the battery again and booted into recovery (CM ver. 5.0.2.0) to wipe cache and Dalvik cache, but am getting errors there as well:

E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log

I did try to wipe the cache and Dalvik cache, and it seemed to do that OK (at least, doing so didn't throw any other errors), but that didn't fix the bootloop problem. Next, tried to do a factory reset from recovery. Got the following results:

-- Wiping data...
Formatting /data...
Formatting /cache...
Formatting /datadata...
E:format_volume: no MID partition "datadata"
Formatting /sd-ext...
No app2sd partition found. Skipping format of /sd-ext. (No problem -- no SD card installed)
Formatting /sdcard/.android_secure...
Error mounting /sdcard/.android_secure!
Skipping format...
Data wipe complete.

Rebooted, and still stuck in bootloop...

So, any ideas on what I should try next to get this phone up and running again? I haven't run into this much trouble with this phone before.

Thanks, and Saludos!
SPC

probably need to charge it at this point. Format data (factory reset)
wipe cache and then dalvik and flash a different rom
The Following User Says Thank You to Vernox701 For This Useful Post: [ View ]
23rd January 2014, 02:26 AM   |  #3  
OP Senior Member
Flag Metro Detroit
Thanks Meter: 31
 
151 posts
Join Date:Joined: Jan 2010
More
Will try this evening and report back...
23rd January 2014, 03:30 AM   |  #4  
OP Senior Member
Flag Metro Detroit
Thanks Meter: 31
 
151 posts
Join Date:Joined: Jan 2010
More
Quote:
Originally Posted by Vernox701

probably need to charge it at this point. Format data (factory reset)
wipe cache and then dalvik and flash a different rom

Ehh... No luck. Tried copying another ROM to an external sd card, and CWM won't mount the external SD card. Tried renaming the ROM UPDATE.ZIP and got this error:

Code:
E:unknown volume for path [SDCARD:update.zip]
E:can't mount SDCARD:update.zip
Installation aborted.
any other ideas, or is this one a goner?
23rd January 2014, 11:25 AM   |  #5  
Account currently disabled
Thanks Meter: 2,073
 
3,923 posts
Join Date:Joined: Sep 2010
I'd try changing to the latest TWRP. The newer CWM never played well with my phone.
The Following User Says Thank You to Pons For This Useful Post: [ View ]
23rd January 2014, 03:47 PM   |  #6  
OP Senior Member
Flag Metro Detroit
Thanks Meter: 31
 
151 posts
Join Date:Joined: Jan 2010
More
Will try that this evening. Need to configure ADB on my laptop, though, since I can't seem to mount emmc or external sd card right now.

Thanks for the advice.
23rd January 2014, 08:20 PM   |  #7  
Senior Member
Flag Nevada
Thanks Meter: 77
 
889 posts
Join Date:Joined: May 2008
More
Quote:
Originally Posted by spcagigas

Will try that this evening. Need to configure ADB on my laptop, though, since I can't seem to mount emmc or external sd card right now.

Thanks for the advice.

Its all a guess on my end maybe your sd card is failing.... have you tried a different sd card make sure its fat32
27th January 2014, 01:25 AM   |  #8  
OP Senior Member
Flag Metro Detroit
Thanks Meter: 31
 
151 posts
Join Date:Joined: Jan 2010
More
Quote:
Originally Posted by Vernox701

Its all a guess on my end maybe your sd card is failing.... have you tried a different sd card make sure its fat32

Yep, tried two other SD cards with no luck. Can't get the phone to mount either of them, though they were freshly formatted. Also can't get ADB to see this phone to push anything to it. Gonna retire it, I guess...

Thanks to all for the recommendations!

Saludos,
spc
29th January 2014, 05:13 AM   |  #9  
zachf714's Avatar
Senior Member
Flag Mooresville
Thanks Meter: 1,003
 
3,576 posts
Join Date:Joined: Jun 2012
More
Quote:
Originally Posted by spcagigas

Yep, tried two other SD cards with no luck. Can't get the phone to mount either of them, though they were freshly formatted. Also can't get ADB to see this phone to push anything to it. Gonna retire it, I guess...

Thanks to all for the recommendations!

Saludos,
spc

I have had this happen before, RUU the phone and it should fix it
30th January 2014, 09:39 PM   |  #10  
OP Senior Member
Flag Metro Detroit
Thanks Meter: 31
 
151 posts
Join Date:Joined: Jan 2010
More
Quote:
Originally Posted by zachf714

I have had this happen before, RUU the phone and it should fix it

Thanks. I've decided to retire this phone -- the failure to boot was really the last straw for it.

Post Reply Subscribe to Thread

Tags
bootloop
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes