[Q] I think I may have bricked my phone...(Answered) - Droid Incredible Q&A, Help & Troubleshooting

Edit: Found the solution to my problem (in comments below).
I installed the latest version of CM7 last night, and everything was running smoothly until I downloaded Launcher Pro. At that point, every time I tried to do something, I got an error message along the lines of "android.media process has stopped unexpectedly", or something extremely similar.
So this morning I decided to reboot my phone and when booting, even after removing the SD card and putting it back in, it got stuck in the CM animation (the Android riding the skateboard).
So I held volume down and power and went into that menu and choose backup/restore, where it then took me to ROM Manager's little menu. After trying to hit backup and restore again, it looks like it's trying to load something from ROM Manager, but it just gets stuck with a black screen with the hat and arrow (ROM Manager's logo).
Is there anything I can do to fix my phone without having to do a complete reset?

In clockworkmod recovery, use the optical joystick instead of the power button (as a selector). Took me forever to figure that out Lmao. Your phone is not bricked, don't worry.... I mean you did do a nandroid right?
Sent from my ADR6300 using XDA App

That did it, I had been using the power button by mistake.
Thanks for the input! I had done a Nandroid and I use Titanium Backup, so after reverting back to the stock Sense UI, I downloaded 7.02 instead of the latest CM7.

Glad that worked for you!
Sent from my ADR6300 using XDA App

Related

[Q] defrost freezes in reboot, but starts normal

Hi,
I'm a real neewbie so please be gentle.
I've rooted my phone and put defrost 5.4 on it.
Works good and i'm figuring out how things work.
I found out now that when i reboot the phone it gets stuck in starting up.
The colors exploding from the left and the right side to become a "X", but then after a while the x is not made any longer and after half an hour it is still trying to make an X.
Take out the battery, put it back and start the phone and it starts normal.
When i install something from the "defrost setup" its downloaded and when i press install the phone restarts, it is unpacking the file, reboots and then gets stuck again.
Have to take out the battery to start the phone again.
What can be the couse of this??
Just found out that also a "normal start" ends up in a endless bootscreen.
The only way to start the phone is take the battery out, put it back and press "start".
Do a full wipe and try another ROM is my first suggestion.
So idid a wipe, after that a recovery (had to start all over again) but the endless bootscreen still remains.
???
1) Find a new ROM and put it on the root of your SDCARD
2) Boot into Recovery by pressing BACK and the POWER button
3) Perform a full wipe (data/factory reset) and cache
4) Flash the new ROM
5) Boot the phone
If you still have problems post logcat.
i've cleaned and whiped (i think) almost everything.
Installed a fresh defrost 5.6.
Installed the defrost apps addon, the phone reboots and a screen apears with a android an a box with an arrow out.
Text is passing by, the phone reboots and starts up.
So far so good, but when i restart or reboot the phone its hangs in this endless lashing coulorfull screen.
I've tried to make a "logcat".
Hopefully it tells you more than it tells me.
i am having the same problem.
first off all: you can press power + volume down + optical joystick to restart phone.
no need to remove battery
my last logcat (with Error filter): www wog-fds.de/log_bootloop.txt
i started to have this problem when i redid the unrevoked process (dont really remember why, thou).
thx for help
edit: not sure but the first logcat looks like somethings missing
heres anotherone without filter www wog-fds.de/log_bootloop2.txt
thx
OK, maybe this is getting somewhere.
I also did a re-revoke, but i do know why.
the first attempt to root my phone ended up in a small disaster.
At the end of the proces i found out that i have a SLCD screen and not an AMOLED, so my phone was as good as dead.
Thanks to someone on a Dutch forum i was able to get my phone back to life.
After that i rooted my phone with the latest version of unrevoked, and this time i was succesfull.
But now i am encountering this problem and it is no fun.
I have at the moment nothing running on the phone because after a re-re-reinstallation i can start all over again with al the apps and so on.
It hangs at the final stages of the boot it looks like.
I had a similar problem when I was messing around with my old framework.
So why you're getting it, I have no idea.
First thing is first Bud
Download DeFrost 5.7 And use the latest version (Illuminate some issues to start with)
What your saying is the Boot Animation (The Multi Colour X animation "Nexus Boot Animation"
You get a boot loop on there....
How long have you left it trying to boot? the first boot after a Reflash does take alot longer than normal as it has to write to a number of files first.
(This only occurs on a New ROM or a Reflash of the frameworks)
So first off Lets Get that latest ROM on the SD Card:
Use w/e method you need to to get it on there
Turn the Phone Off "Where going to load recovery"
Press the Down Volume Key and press the power button Once.
You will see a white screen with Android images at the bottom:
Press the Volume down once (Recovery) when this is highlighted press the power button
Where now in a black screen Press Volume Up and Power
(We should now have a Blue Menu (Am taking it by the issues you talk about your using Clockwork Recover.......)
Go down to Apply sdcard:update.zip
And press the power button. So where now Clock Work Recovery
(If you dont have Clockwork i.e. Fake Flash Update.zip maybe someone can post it for me, Limited for time in work, But search for Fake FLash Clockwork if you dont have it.
Then go down to Wipe Date/Factory Reset
Select the only line that is Populated.
Go back to main menu and go to install Zip from SDCard and press the OJ
Select Choose Zip from SDCard.
Find you ROM and press the OJ
Wait some time and press the back button a few times, and select the reset option?
DO NOT INSTALL NO MODS OR THEMES, THIS CAN ONLY BE DONE AFTER A FULL BOOT OF A CLEAN ROM.
Leave it some time, as the first boot is always the longest.
Fingers crossed you should be OK.
What your talking about is a problem with the ROM (as the bootanimation is called by the ROM)
dave7802 said:
DO NOT INSTALL NO MODS OR THEMES, THIS CAN ONLY BE DONE AFTER A FULL BOOT OF A CLEAN ROM.
Click to expand...
Click to collapse
That'd be my guess too. If you try to apply a mod before you've let the ROM unpack itself it does exactly as you describe.
What your saying is the Boot Animation (The Multi Colour X animation "Nexus Boot Animation"
You get a boot loop on there....
How long have you left it trying to boot? the first boot after a Reflash does take alot longer than normal as it has to write to a number of files first.
(This only occurs on a New ROM or a Reflash of the frameworks)
I've installed the defrost.
After it came in full working conditions i've added the defrost add-on.
Phone shuts down, starts again in the screen with the one doid and a box with an arrow out.
Some writing apears and the phone starts again.
The colours apears and making a cross and this goes faster and faster and then a screen where i have to enter my sim-unlockcode and the phone is up and running.
So far so good.
When i now switch the phone off or give it a reboot ( in the screen after a long press on the powerbutton) the phone starts in the white screen with HTC logo, then the colours apear making a cross, but after time this goes slower and slower until the cross is not ever made again.
The colours appear trying to make a cross and diappear and comming back again, and this goes on for ( i left it once for 1/2 an hour)
I will give it a go with the 5.7
thanks for the help.
Really, i heave my phone for one month now and it is my first android thing.
Never worked with linux etc etc.
What does "press the OJ" means ??
oj = optical joystick
@dave7802
thanks for the answer but i have the bootloop also when i do a manual restart without flashing anything.
i use defrost 5.7
i did a restart after flashing
bye
strange thing to happen. it must be in the ROM because it wasn't happening on the stock ROM.
so try another ROM some like cyanogen or opendesire. is it happening also?
Wel, i've come to the point that i think "WTF", it works and the only thing is the start/reboot.
I'm not going to re-re-re-re sign in to my google account, and not want to re-re-re-re-enter my mail account again.
Thanks to "olaxe" i know how to start the phone wthout taking out the battery.
anyway, everybodie, thanks for reading etc.
OK so you guys are still having the same issue.
Can we provide as much info as possible,
As i use DeFrost 5.7 and i just done a normal reboot and its working fine,
if its a problem with the ROM everyone would have the issue,
All i can think is a MOD you have installed is conflicting,
So some info you can provide:
What MODS are you running / installing, like Super Circle Battery, or Custom HAVS and SVS?
What version where they developed for?
i.e. are you installing MODS that where developed for an older version of defrost? as the frameworks change on each version and so do the HAVS and SVS
If your not flashing anything how about installing it?
It could be an app you used worked for an older version, and since the update its no longer working?
olaxe
thanks for the answer but i have the bootloop also when i do a manual restart without flashing anything.
i use defrost 5.7
i did a restart after flashing
Click to expand...
Click to collapse
You say you have not flashed anything? and then you said you restarted after flashing? i dont follow?
What settings are you using and apps do you have installed?
What are you doing in clockwork recovery, are you wiping then installing JUST DEFROST then letting your system start up?
or
Are you flashing a couple of things like defrost and super circle battery?
Dave,
A nephew, who ownes a desire and is "into android" from the moment of the first googlephone, was going to root my desire.
The great misstake (we found out after we've dit it) was that he used a version of unrevoke witch was mend for use with amoled and i own a slcd.
So my phone would'nt show anything anymore. Only the bootscreen when pressed vol down and power.
I've followed several advises of diehards, have put "this.zip" on the sdcard, "that.zip" and even "ifthisdon'twork.zip" shoot me.
All i got in the bootscreen was "no image" "no image or wrong image" and "version is older".
After a week a guy on a dutch forum told me to download some files to my computer, take the sdcard out of the phone, connect the phone to the computer and then type the following:
3. Typ in je commandprompt:
code:
1
2
3
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip rom210.zip
After that the phone came back to live and i was happy as a child.
After that i did the unrevoked thing with the latest version and the phone was rooted.
Put the sdcard back, formatted it whitin the phone and after that i placed the defrost 5.4 on the root of the sdcard.
Did the full wipe, dalvikwipe and flashed the defost 5.4
After a while i had the defrost up and running.
In the defrost setup i found the defrost addon.
downloaded it (all IN the phone) and after that pressed "install".
The phone shuts down a screen appears with the one droid and a box, the phone restarts and is up and running.
Then i found in the defrost setup a file "no adds"
Installed that to and then the troubles start.
Hangs in the bootscreen.
I can only start the phone when the power is completely turned of ( battery out) or with vol down, power and trackball pressed at the same time.

[Q] Constant Bootloops ARRGHHHH

Ok, so here is my story:
I rooted way back in July right after I got my Evo, so I started on Android 2.1. I flashed and used OMJ's ROM for quite a while until I discovered Cyanogen mod, which I switched to after trying OMJ's 2.2 ROM.
I used CM6 for a long time, eventually flashing some nightly builds, culminating in nightly build number 140. At some point in this process, I started having real trouble with bootlooping CONSTANTLY (and I couldn't even make a nandroid backup because it would reboot inside the backup process). I eventually got it to stop bootlooping after many many reboots and wipes (full wipe, cache wipe, dalvik wipe) and restarts and got CM to boot.
I just now flashed CM6.1 and started getting constant bootloops again. I assumed it was a problem with CM, so I decided eff it, I'm going with a different ROM and downloaded Calkulin's EViO 1.5 rom to try, but it can't boot either.
I can get to the android screen, which displays no signal, then it reboots. I can't get out of this cycle. When I was on CM, I had issues with starting up - I had to hold down the power button quickly and press airplane mode, then it would reboot again, but it would come all the way up. Then once it was fully booted I could disable airplane mode and it would stay online. After that point, I just decided never to reboot the phone, but this is a huge problem that I can't figure out how to fix.
I have tried wiping using Clockwork and Amon Ra, but neither makes a difference.
Any help would be GREATLY appreciated. Thanks!!!
it reboots while making nandroid? So even if you hold vol down + power and go to the recovery from there it is rebooting?
xHausx said:
it reboots while making nandroid? So even if you hold vol down + power and go to the recovery from there it is rebooting?
Click to expand...
Click to collapse
Correct, I hold volume down + power to get into recovery, then choose nandroid and backup, then while it is creating a nandroid backup, it reboots.
Does anyone have any ideas? At this point, I have no clue what to do, and I can't boot into any ROM.
If you Google it you'll see its an incredibly common problem not just with those of us who have modded our phones but those with stock roms who have never done so it happened to me when I originally flashed cm6 to my phone as well but it eventually fixed itself if you can get it to boot try factory reset it may help
Sent from my PC36100 using XDA App
hackulous said:
If you Google it you'll see its an incredibly common problem not just with those of us who have modded our phones but those with stock roms who have never done so it happened to me when I originally flashed cm6 to my phone as well but it eventually fixed itself if you can get it to boot try factory reset it may help
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Factory reset just wipes your data using your recovery doesn't it? Either way, I've tried that, and no dice.
I mean, I guess at the very least I could try to bring the phone into Sprint... is there a shipped RUU I can flash so they can look at it?
edit: found the latest RUU (http://forum.xda-developers.com/showthread.php?p=8474707)
I'm gonna try this and see what happens.
http://www.google.com/m/url?client=...IQFjAA&usg=AFQjCNHQ2016xLF_DLz7uVoilk8Hm1EsRg
Sent from my PC36100 using XDA App
same problem. no solution. i am now fully bricked, aka i reboot before i can pull down lockscreen (rom changes, unroot, nothing works) return before it gets so bad you cant unroot.
No good man I hope you got insurance
Sent from my PC36100 using XDA App
Ewe, thats no good. I would use the ruu but Do Not Use The Newest One. You will lose root and the new 3.30 people are having trouble rooting
Sent from my PC36100 using XDA App
same thing happening to me. Stuck in bootloop now, started out as just a random reboot that would boot than reboot than hold for a while. Right now im completely stuck in bootloop =(.
Is there a way to put a stock rom on my phone with just booting to recovery?
These sound like hardware issues but if your recovery is working fine then it may be something else. Did you try the RUU while in the recovery?
Just don't use the newest one
Sent from my PC36100 using XDA App
dkdude36 said:
same problem. no solution. i am now fully bricked, aka i reboot before i can pull down lockscreen (rom changes, unroot, nothing works) return before it gets so bad you cant unroot.
Click to expand...
Click to collapse
I was finally able to get to a point where I could get it to boot - here is what I did.
I wiped everything using amon ra's recovery, then flashed the latest cyanogen mod from here: http://mirror.teamdouche.net/get/supersonic/update-cm-6.1.0-RC1-Supersonic-signed.zip, then when it booted, it would get constant bootloops, but it would get to the home screen for a few seconds each time.
You have to click through the intro menus reaaaallly freakin fast so you see the desktop with the live wallpaper. DON'T sign into a google account. It will probably bootloop again, and if it doesn't, quickly hold down the power button and select airplane mode. If it reboots again, it will power up completely successfully in airplane mode. Then make sure you're in an area of good signal and disable airplane mode until you have 3G, and then sign into a google account. If it starts bootlooping again, quickly hold the power button and press airplane mode - you can always boot successfully in airplane mode for some reason...
xHausx said:
These sound like hardware issues but if your recovery is working fine then it may be something else. Did you try the RUU while in the recovery?
Just don't use the newest one
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
It could be hardware related, but I'm not 100% sure at this point...
The reboots seem to be correlated with signal strength. If I have 1 bar of signal (in CM, so not cell signal), it will reboot before it gets to 3G.
Also any flash on a website reboots the phone for some reason. I don't know if that's common or not.

[Q] My EVO works fine...except I cannot get into Recovery to backup my ROM! Help!

I have a rooted (Supersonic EVT2-2 SHIP S-OFF; HBOOT-0.93.0000) EVO that I'm running Warm 2.2 RLS 4 on. I have it set up the way that I wanted and it is running perfect (enough for me).
Yesterday, I caught a glimpse of the MIUI ROM that has an iPhone theme so I wanted to try it out. So, I used Titanium to back up my apps and data to my SD card (8GB with 3GB open). Then, I went to ROM Manager to back up my ROM. I saw that there was an update for the ClockworkMod Recovery so flashed it up to 3.0.0.5. Then I went to Backup Current ROM, kept the suggested name, and hit OK. After a few seconds, the Splash Screen (white HTC EVO 4G) briefly shows, the phone buzzes and then I'm on the initial Bootloader menu screen (with the three Androids at the bottom).
I highlight Bootloader, then I hit the Power button to go to the next set of menus, and the phone does it's checks. After the checks, I push the Volume Down button to go to Recovery, then hit the Power button. The splash screen shows again, the phone buzzes, and I'm back at the initial Bootloader screen.
Whether I use the Quick Boot app, the ROM Manager app, or the Power and Volume Down method, I cannot get past the Bootloader screen to get into Recovery. All I get is Splash, buzz, then the initial Bootloader. Warm 2.2 RLS4 is a nice stable ROM, but I am starting to feel limited, which is why I rooted the phone a few months ago.
Could someone PLEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEZZZZSSSSSSEEEEE help me with this? I have been reading forums and Googling this issue for hours and I can't find an answer. I am far from a comp engineer, but I can follow instructions pretty well.
Thanks a million!
Try using ROM Manager to reflash your recovery, that should fix it for you.
Fourth times the charm! WHEEWWW!!!
It's seems to be working now and I'm backing up my ROM as I type. I went into ROM Manager and flashed it again and this time I went into Recovery straight from ROM Manager (I had did it indirectly via the ROM backup before) and I saw a orange and black menu, instead of the green and black. COOOLLLL!!!!
I tried to go into recovery from the Quick Boot app and that works too, NIICCEE!!!
I guess after you flash the ClockworkMod Recovery, you have to "initialize" it by going to it directly from ROM Manager, or else any other method you try won't work? I'm not sure but it seems like it.
A good lesson, glad I can fully enjoy the EVO again.
Cheers!
Glad you got it figured out

[Q] Problems after restoring in Clockworkmod

Hello, this is kind of a long story but.......I was in clockworkmod recovery looking to restore back to a backed up rom. I saw a backup titled, 2000-01-01.00.00.16/. I didn't remember a backup that had that named and it said it was from the year 2000. Out of curiosity I decided to backup to it. Then It got stuck or what appeared to be stuck on "checking md5 sum". After ten minutes I pulled the battery thinking it hadn't even started restoring. When I put the battery back in I got the charging battery icon with a cloud and a thermometer, assuming this meant that the phone was to hot I felt the back and it wasn't hot at all. I tried to power the phone off but each time I turned it back on I got the same icon. Finally I tried plugging it in. Then the icon went away and the booted into clockworkmod. So then I restored to the Unnamed rom and the led notification light wouldn't go off. Then every time I turn the phone off I get the thermometer icon and have to plug it in. On top of that my computer won't recognize the phone. I want to use Odin to go back to stock but since the computer won't recognize it I'm stuck with a phone full of problems. Any suggestion?
First backups can't contains signs /&%*+# etc...
Second.. can you get to recovery?
Sent from my SPH-D710 using XDA Premium App
omg .. i THINK YOU BRICKED YOUR PHONE!!
But not to worry, most likely it's an easy fix. Reboot phone a couple times, MAKE SURE DRIVERS & EVERYTHING are INSTALLED FIRST, open ODIN with proper .TAR file, .PIT NOT needed. Only Auto Reboot box should be checked, then plug in to pc. Wait for phone to connect and hit start. BE PATIENT. If it doesn't work try booting into CMW, holding POWER and VOL UP buttons. Hope this helps!
Thanks everyone for the help. I ended up downloading mobile odin from the market, and then flashing the stock unrooted EK02.tar file. I still had the same problems and figured it was a hardware problem. So I took it into my local sprint store and they took one look and it and ordered me knew for free, no questions asked!

[Q] [Soft Brick] Bootloop after installing custom boot animation (Chainfire's logcat)

Hello!
I purchased the tablet (SM-P600 WiFi model) a few months back. I rooted when I bought and it was working without any problems, but today I tried to install this "boot animation", and it put my device into a soft brick. When I try to boot the device, first the initial Samsung logo shows up, then it's just blank screen without any sound and after a while (by the time device would normall boot), it justs restarts again and repeats the same thing again. I am able to access recovery (TWRP, installed it and made first backup 2 days ago) and download mode as well.
I've tried to recover backup I made 2 days ago (fully working) but it doesn't fix anything. The bootloop continues.
To clarify some things, I'm running on 4.3 (MJ6) stock, flashed SELinux Permissive kernel yesterday, but it was working fine until now.
This is the actual boot "animation": https://play.google.com/store/apps/details?id=eu.chainfire.livelogcat
I installed, and after trying to reboot, the bootloop problems started
I hope you can help me Thank you in advance.
After some fiddling around, finally downloading stock firmware (slow wifi here) from sammobile.com and flashing it with ODIN, I've recovered from the bootloop. I am still interested though in why it happened in the first place. Can anyone please provide me with some insight ?
Thank you anyway
After trying to restore backup from 2 days ago (which was working perfectly fine), there again is no boot animation after initial boot logo, no sound, but if I press power key and any of the capacitive touch buttons, home key, etc., the tablet vibrates but nothing appears on the screen. It's getting kind of weird.
EDIT:
I just tried flashing stock firmware again, and after only restoring /data/, things like home button, capacitive buttons, Settings button in Quick Settings/Notification etc. don't work. Can anyone help me with restoring the data I had from that working backup?
Titanium Backup can extract apps and data from TWRP/CWM backups. It's kind of a slow process, but it works.
Sent from my SM-P900 using Tapatalk
dodo99x said:
Titanium Backup can extract apps and data from TWRP/CWM backups. It's kind of a slow process, but it works.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
I actually tried that, I have PRO version of Titanium Backup, but it only found a SINGLE app from the whole working backup (About 7GB). I also tried Nandroid Backup Explorer which only found one app (with data) as well, most of the others (some were even totally missing) had no data at all. After manually examining the backup, there actually was only 1 app data folder in /data/data/. No WiFI settings or anything else either.
So I have the tablet restored with most of the apps. But every single one of them (except one that doesn't even hold any permanent data that I know of) has lost their data. I have since flashed CWM because it always worked for me.
At least you're up and running again. I tried this logcat app (over a year ago) on my N10 and my N7, both got a bootloop as well.
Sent from my SM-P900 using Tapatalk
shiinkotheone said:
Hello!
I purchased the tablet (SM-P600 WiFi model) a few months back. I rooted when I bought and it was working without any problems, but today I tried to install this "boot animation", and it put my device into a soft brick. When I try to boot the device, first the initial Samsung logo shows up, then it's just blank screen without any sound and after a while (by the time device would normall boot), it justs restarts again and repeats the same thing again. I am able to access recovery (TWRP, installed it and made first backup 2 days ago) and download mode as well.
I've tried to recover backup I made 2 days ago (fully working) but it doesn't fix anything. The bootloop continues.
To clarify some things, I'm running on 4.3 (MJ6) stock, flashed SELinux Permissive kernel yesterday, but it was working fine until now.
This is the actual boot "animation": https://play.google.com/store/apps/details?id=eu.chainfire.livelogcat
I installed, and after trying to reboot, the bootloop problems started
I hope you can help me Thank you in advance.
Click to expand...
Click to collapse
just do a factory reset..
and if u have made a backup using titanium then u will b able to recover the lost apps too..
★PLEASE DONT FORGET TO PRESS THANKS★

Categories

Resources