Database Users

motorola logo(brick maybe?)

so i went through the instructions on instaklling the tranquility rom, well after installing all i got was the motorola boot, nothing else, so i restarted the phone after about 10 min, and still nothing, so i reboot into recovery, and wiped the phone, well its still only showing the motorola logo, any suggestions?

Same thing happend to me
Sent from my DROIDX using XDA App

oxidant11 said:
so i went through the instructions on instaklling the tranquility rom, well after installing all i got was the motorola boot, nothing else, so i restarted the phone after about 10 min, and still nothing, so i reboot into recovery, and wiped the phone, well its still only showing the motorola logo, any suggestions?
Click to expand...
Click to collapse
Boot into recovery and load one of your backups. If you don't have backups, then you just learned why you need them. Of course, there are people who have uploaded nandroid backups to this site and others, find one of them, move it to your sdcard, boot into recovery, and install it.
If all this fails, then just .sbf. It doesn't take forever, and you can make a nice clean stock 2.2 backup after you root and then upgrade.

What OS are you running? Have you tried to SBF your phone back to factory?

Im guessing its 2.2 only
Sent from my DROIDX using XDA App

Yeah i got it back by doing spf. And then reloaded a backup, but i could never get into clockwork, what do u do yo get into clockwork because the only recovery i was able to get into was the recovery that comes with the phone, just would like to know.
Sent from my DROIDX using XDA App

The same thing happened to me trying to update using the update.zip. Installs everything normally but when it comes to booting it simply stops at the motorola logo, then if you reboot it several times taking the battery out it boots into the system.

Doesn't sound like your rooted? Have to be rooted to use Clockwork.
If you are rooted might try reinstalling the Bootstrap Recovery.

Would definitely suggest doing an SBF on the phone. The guides here are a little unorganized, so I wrote up a nice one below. Includes everything including the SBF file needed for flashing.
http://destdroid.com/showthread.php?18-How-to-Flash-2.1-(SBF)

Need help! My phone was rooted using the Easy Root process, all was peachy until I decided to try the latest leak of 2.2. Didn't work, got stuck at the M logo and could only get the bootloader screen up. I thought it was bricked but after searching high and low through the blogosphere got to this post. Now I've done the sbf as suggested, but when I try to do the Easy Root again, nothing happens. Any suggestions? I would like to root again so I can access the backup from my sd card and get my phone back to where I had it b/f. HELP!

Weird Issue. I seem to have 2 roms flashed at the same time!!

I have been using Rubix Focused 1.8.9 on my DX for a weeks or so and I was super happy with it. I have been getting a little ROM crazy though and had been reading up on Tranquility 3.5.1 and it seemed pretty cool so I decided to try it.
I think I messed something up in the install process because things were FCing left and right and it was just super laggy. So I decided to restore my nandroid backup that I had made right before installing Tranquility.
I was doing all this on a bus so I didn't realize that my batter was pretty low. Well halfway through my nandroid restore my batter died. Suffice it say that I was freaking out.
I got home and booted the phone and got the Tranqulity splash screen, followed by the Rubix splash screen. Then the phone booted up into Rubix exactly like it was in the backup.
I have no idea what is going on. I dont really mind the splash screens but I am afraid there may be some issues if there are files from both installs running at the same time.
Should I try restoring the backup again and let it go all the way through or do I have nothing to worry about?

Actually - and you can correct me if I am wrong - you got the tranquility boot logo and the rubix flash screen? If that is correct - you don't really need to worry about it. For whatever reason - the nandroid does not over write the boot logo.
I actually performed and sbf and when I rebooted my phone I still had my custom boot logo! It actually kind of bothered me. I thought the whole purpose of an sbf was to COMPLETELY restore your phone to its factory state.
So anyways - I wouldn't worry about it too much. I know it would drive me crazy to have the "wrong" boot logo. Here is a link to a thread with tons of boot logo's to choose from...
http://www.droidforums.net/forum/droid-x-hacks/91707-droid-x-custom-boot-logo-ill-create.html
good luck.

Tranquility just about killed my phone - any theories?

So I decided to give Tranquility a test and see how it compares to my currently running ApeX. I followed the usual procedures, data wipe/factory reset.....twice.
then installed TranQ and the TranQ App update.
The phone then boots up and freezes on the animation screen. So i reset it, then it won't boot at all past the Logo screen. Randomly it decides to boot up fine, but then 30 seconds of android and it reboots and freezes up.
So for some reason it won't let me boot into clockwork recovery, so i decide to just do the system only SBF it and be done.
So I've SBF'd it twice now, the first time it did a random restart and froze, and also kept the tranq boot animation. I did the 2nd sbf and it's got rid of the animation screen and back to droid, however the tranq boot logo is there.
I haven't proceeded to reactivate the phone yet, and just leaving it alone it hasn't restarted itself. I'm planning on rerooting and reinstalling clockwork recovery and see if i can get one of my old backups going.
But, any theories to what would have jacked it up so bad? and why the stock moto logo wasn't put back when SBF'ing?

update:
rerooted just fine using Z4, installed clockwork recovery just fine too.
Right now I'm doing a data wipe and reinstalling ApeX 1.3.1 from scratch from clockwork recovery. Then I'm gonna restore one of my backups.
Hopefully all goes well

update:
recovered to my backup just fine. Still didn't get rid of the tranq boot logo, thankfully i had a zip stored away of the stock logo so I installed that.
All is now well in the world.
Lesson from this......if it's working fine, leave yo sht alone!

Logo is stored in different place then a system sbf will update. That's not tranQ 's fault. I still use gummyJar though. Too much blur in TranQ for me

I had the exact same problem when I went from fission to tran q. I literally had to do the. 320 sbf then the. 340 sbf to get tran q to install right. Didn't like it and put fission back on

yea i had to do the same thing comming from fission, and because of it i am just staying on tranquility until Obsidian is more stable, then GOODBYE BLUR :-D

The trick to installing TranQ is to install it over stock. If you try to install it over another custom ROM you will have nothing but problems.
Sent from my DROIDX using XDA App

davidukfl said:
Lesson from this......if it's working fine, leave yo sht alone!
Click to expand...
Click to collapse
I feel your pain, but you shouldn't be discouraged (as long as you Nandroid, Nandroid, Nandroid!).
I also spent a week fiddling with TranQ before giving up due to random reboots. But I went ahead and installed GummyJar. It was worth it!
When you're ready to climb back onto the horse, you should try GummyJar. If you prefer a no-bur ROM, it's probably the best in terms of speed and stability.

well i had tried Gummy before, but it was a little buggy for me. Phone would restart after calls, hardware buttons wouldn't always work and a few other little things.
I actually just switched to Fission and it's pretty brilliant thus far. No problems at all, and the fission manager helps a lot

fmkaiba said:
Logo is stored in different place then a system sbf will update. That's not tranQ 's fault. I still use gummyJar though. Too much blur in TranQ for me
Click to expand...
Click to collapse
IT IS TranQ's fault. It is the only ROM that does this. Before you get rid of Tranq, you have to go in to the tools and set your boot logo back to stock. I have flashed many different ROMs and it is the ONLY ONE that makes sure to "leave its mark," LITERALLY.

had same problem when I went from fission. I had to sbf .32 then sbf .34 then did the tran q and it worked just fine after that. I didn't like it to much so I went back to fission. To get rid of the tran q I just did the same sbf method I did and went back to fission.

z06mike said:
IT IS TranQ's fault. It is the only ROM that does this. Before you get rid of Tranq, you have to go in to the tools and set your boot logo back to stock. I have flashed many different ROMs and it is the ONLY ONE that makes sure to "leave its mark," LITERALLY.
Click to expand...
Click to collapse
You're right on w/this..Its too bad I found out the hard way..

Endless Rebooting, about to smash phone to bits

Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.

Mecha2142 said:
Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.
Click to expand...
Click to collapse
hmm...
i don't know what kernel fresh comes with, but both of the other kernels are more aggressive ones, and i would guess your phone doesn't like them. i would try this:
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.

I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Sent from my PC36100 using XDA App

Well I'm still super new to the whole flashing of the ROM's. But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Sent from my PC36100 using XDA App

aimbdd said:
hmm...
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.
Click to expand...
Click to collapse
Yeah, I guess I should try the stock rooted rom. If I'm only able to use that instead of any other custom rom, though, I'm going to lose it. There's something inherently frustrating about a device refusing to work for no apparent reason.
chickut123 said:
I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Click to expand...
Click to collapse
I'm sort of hoping I won't have to do that, considering I'll likely get a refurbished unit.
Fredrow425 said:
But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Click to expand...
Click to collapse
I'm pretty sure that isn't the case at all. If there was an issue with the way I rooted my phone, it would have been present eight months ago when I bought it. This rebooting issue is relatively new, and it isn't bricked. I appreciate the advice, though.

It could be just a defective phone - memory isn't immortal or impervious to defects.
I'd downgrade to a Sprint ROM, and keep it stock and see how that works. You have to rule out bad hardware first, and that's the only way to do it.

I agree on all of your guys suggestions but one thing i noticed was that he said he wiped data then dalvic cache then he said he flashed the kernel then the rom. Maybe he should try and rewipe everything with calk format all then flash the rom and reboot. Then go back into recovery and flash your new kernel then reboot again and see whats up from there.

Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.

akrod2as said:
Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.
Click to expand...
Click to collapse
Yes, I first formatted the sd card in Windows and then partitioning it on the phone's recovery. Still no luck.

Yeah... Sprint rom or if you go through with the unrooting process (I forgot how...) then you can figure out if it is hardware.
But yeah, endless reboots are frustrating.
If Sprint rom is giving you troubles, then just return it and get a new one. It's gotta be hardware then.

Also you could try running stock rooted without any downloaded market apps. Just run what came with the phone.
You can also try stock rooted eclair 2.1
Mine started the reboot bs after the december update. Mine seems to reboot when I use it heavily even though I'm not overclocked (heats up). Before the 2.2 update, it was very fussy being outside during the summer. I would like to exchange mine for another, even though I don't use it anymore. It would be nice to have a fully functioning backup. My gf's daughter wants the evo very much. Even if I would do that, which I wouldn't, I wouldn't let someone use a possibly unstable phone. If an emergency happened, and the phone started it's rebooting bs, it would be very bad to not be able to use the phone when you need it the most.
I am guessing I would have to reactivate the evo, run it for a month or so, unroot and lock it, then take it to a service center and see if I can make it start rebooting like crazy. Maybe I will get lucky and they would give me another one. I don't care too much if it is a refurb as long as it is in good shape and works good.

Try removing the SD card and booting.
Sent from my PC36100 using XDA App

rebooting
I had this same problem with my evo. Sometimes it would be ok, but then others it wouldnt stop doing it, didnt matter what I did. It could be sitting by itself and I would hear it rebooting. Drove me mad!!!
My first evo was awesome, it was a hardware ver 3. My camera lens cracked and the gave me a refurb, hardware version 2. This is when my reboots started happening.
After 3 batteries from Sprint and two more refurbs I finally blew in front of a store full of customers telling them that either give me a NEW evo, hardware version 3 like I originally had with no problems or it was going against their wall.
I havent had one problem since.
I wasnt rooted yet so cant comment along those lines but if you take it back to stock and it still does it I recommend throwing it at one of Sprints walls. No need to do any drywall patching at your place LOL.
I hope you get it resolved as I can feel your pain!

It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.

bigmoogle said:
It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.
Click to expand...
Click to collapse
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?

Mecha2142 said:
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?
Click to expand...
Click to collapse
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.

herbthehammer said:
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.
Click to expand...
Click to collapse
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.

Mecha2142 said:
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.
Click to expand...
Click to collapse
Did you even try removing the sd card and booting the phone?

Same thing happend with my old evo it started after i install one of the first cm safe roms not nightlies not saying tyat was the cause, i tried evverything wiping unrooting botting without sd, ive been on android sice g1 and i tried everything nothing worked, ended up going to sprint and getting another refurnished it was prolly hardware issue maybe cpu overheating or something, anyways not sure why ppl are so scared of refurnished phones i believe they do a lot more tests on those phone than retail ones lol

akrod2as said:
Did you even try removing the sd card and booting the phone?
Click to expand...
Click to collapse
Yes. I've already said I tried booting the phone without the sd card several times now without success.

So, have I bricked my phone?

Used ROM Manager and downloaded Leedriod 3.0, ran Terminal Emulator and did everything by the book. Went into ClockWork Recovery mode and everything looked okay. Then went to HTC boot animation screen and that's where it has been ever since. Every five minutes or so I get the delightful sound of HTC and a permanently on HTC, Quietly Brilliant Boot screen. It's been going like that for about 25 minutes now.
Any help would be appreciated.

No its not bricked, its in bootloop.
This is what i do when it happens to me:
Pull out the battery. If the phone is off, turn it back on with volume down + power on button. Wait till you get the bootloader screen. Now select recovery. In ClockWork Recovery you can set your backup back. (if you had made one before).
I hope its helps you. Goodluck.

Or just copy another rom file to the sd card and flash again.

Unfortunately I made the classic error of not backing up first, was trying to do this while in work (not good) so I presume at this point I'm screwed

joooe said:
Or just copy another rom file to the sd card and flash again.
Click to expand...
Click to collapse
Thanks, will try that tonight.

It doesn't hurt to try to flash the rom you already have once again.

Just what joooe said. Use super wipe to clear data. just for sure.
Good luck.
Sent from my Desire HD using XDA Premium App

Just a quick thanks to you guys, did Super Wipe and installed Android Revolution 6.20 last night and all went well. It was worth the screw up to have the small learning curve in the end

I did this one of the first times i flashed roms
i did have abackup first but its a scary experience lol