Database Users

[Q] Help! Droid 2 bricked (sort-of)

Ok, so here is the situation:
I rooted my Droid 2, no problem. You guys give very easy to follow directions, so kudos.
Things worked fine once rooted for a week or so, then I installed LCD Density changer. I put in the new density I wanted, it told me to reboot. Fine, I do so. Once I do it, it goes into an endless boot cycle.
My first thought was boot into recovery and do 'restore to factory defaults', so I figured out how to do that, and it 'worked'. But once I restarted, now it reboots with an LCD density of 90 (like I set in LCD Density changer); it takes me to the initial setup screen, works for 10-15 seconds, then reboots. I repeated the 'restore to factory defaults' and same thing.
I'm at a loss as to what to do! I've read about 'flashing' a recovery...can I do that while my phone is in its current state?
Thanks so much for your help, people!

I think you can flash your phone. I don't think you need to have your phone working to flash. Maybe just having it on?

phud1066 said:
Ok, so here is the situation:
I rooted my Droid 2, no problem. You guys give very easy to follow directions, so kudos.
Things worked fine once rooted for a week or so, then I installed LCD Density changer. I put in the new density I wanted, it told me to reboot. Fine, I do so. Once I do it, it goes into an endless boot cycle.
My first thought was boot into recovery and do 'restore to factory defaults', so I figured out how to do that, and it 'worked'. But once I restarted, now it reboots with an LCD density of 90 (like I set in LCD Density changer); it takes me to the initial setup screen, works for 10-15 seconds, then reboots. I repeated the 'restore to factory defaults' and same thing.
I'm at a loss as to what to do! I've read about 'flashing' a recovery...can I do that while my phone is in its current state?
Thanks so much for your help, people!
Click to expand...
Click to collapse
Yup, you should be able to get in just fine to flash it again. Just turn the phone on while holding down the UP arrow on the D-pad. I've done a lot of stupid stuff to every Droid I've owned, and still haven't managed to brick one permanently.

jcsugrue said:
Yup, you should be able to get in just fine to flash it again. Just turn the phone on while holding down the UP arrow on the D-pad. I've done a lot of stupid stuff to every Droid I've owned, and still haven't managed to brick one permanently.
Click to expand...
Click to collapse
You're right! This let me get access to the bootloader, and flash the recovery .sbf I found in another thread. I'm keeping my fingers crossed, but this seems to be working. Thanks for your help!

Update: Fixed!
RSD Lite worked while the phone was at the bootloader. I flashed the recovery, and everything seems to be fine and dandy now. Thanks for your help, darkonion and jcsugrue!

phud1066 said:
RSD Lite worked while the phone was at the bootloader. I flashed the recovery, and everything seems to be fine and dandy now. Thanks for your help, darkonion and jcsugrue!
Click to expand...
Click to collapse
No problem. Glad that my tutorial can help!

jcsugrue said:
Yup, you should be able to get in just fine to flash it again. Just turn the phone on while holding down the UP arrow on the D-pad. I've done a lot of stupid stuff to every Droid I've owned, and still haven't managed to brick one permanently.
Click to expand...
Click to collapse
I had given up all hope of restoring my phone until I read this. Thanks you very much

phud1066 said:
RSD Lite worked while the phone was at the bootloader. I flashed the recovery, and everything seems to be fine and dandy now. Thanks for your help, darkonion and jcsugrue!
Click to expand...
Click to collapse
RSD lite would not work while I was in the bootloader program. It would get to 100% then would go into a second flashing of image file then it would fail. I am pretty sure I have bricked my phone, but still hanging on to it hoping against hope that I can fix it. I have tried almost everything, with the exception of using Linux. I don’t know where to get it or how much it costs.
I wound up having to buy another Droid 2 from the Verizon store here in town. :/
Sent from my DROID2 using XDA App

Terri M said:
I have tried almost everything, with the exception of using Linux. I don’t know where to get it or how much it costs.
Click to expand...
Click to collapse
Linux unlike Mac and Windows is basically free. Ubuntu is free to download. I dual boot windows 7 and Ubuntu 10.04.
Sent from my DROID2 using XDA App

Nexus One "continuously reboots to "X" screen."

Hi everybody!
I'm trying to buy a used Nexus One, good price, but the owner claims that the phone "continuously reboots to "X" screen." but that IT can be fixed flashing the rom.
Is it true?
I'm reading on the internet that having the nexus one loop rebooting is a somehow common problem, and people got it fixed flashing the rom, or by moving some shifted pins on the battery. Do you guys think it's something reparable? Everybody that had this issue solved it? Or I risk that the phone is actually broken, and I might be buying a phone that I will not be able to use?
Thanks!

fastboot
just check for fastboot. the rest is easy cheeze.
how much is a good deal ?

unlocked $300 (cad)
What should I check? Instruct me plz, I never had a nexus one or even a Droid phone before ... (coming from 2 years old HTC cruise, with WM 6.5 with an XDA rom ....)
If I meet the guy, how to I check that hes not selling me a bricked nexus lol ?

Installing a new rom will fix it
Sent from my IPhone 4 using XDA App

Amritttt said:
Installing a new rom will fix it
Sent from my IPhone 4 using XDA App
Click to expand...
Click to collapse
are you 100% ?
I dont mind working on it, I just want to make sure that it is reparable via software/roms.
ppl plz tell yours, im just about calling this guy, really dont wanna waste $300
what is its restarts so much, that I cant flash the rom or something? there's no way that that could be the case, right?

sold ... goddamit lol But I'll get one one way or another

I was having this happen to me a lot. I moved in to a new place with no cable or internet yet, so my N1 was under extremely heavy use. And when it was warm, it would get both the touch screen problem and the random reboots.
I was using pershoots 2.35 Kernal. I went back to the stock kernal and the phone has since been running a lot cooler. Zero reboots, touch screen responds correctly. I take the stock kernal stability over an OC kernal any day.

It's a kernel issue that can most likely be fixed by flashing a new
ROM/Kernel, however there is always a small chance that it is triggered by faulty hardware.

My Nexus had this Problem Was unfixable by software. Hardware defect. I wouldn't buy.
Still waiting for my swap unit

i had a friend with a similar problem. He rooted the phone with the 1-click root app from the market, he then installed ROM manager from the market and try to flash Cyanogen mod ROM, afterward the phone went black. The only thing happen to the phone now is the X screen and its keep boot loop. I tried went to fastboot, works fine, then I tried to go to Recovery but it restart right afterward!!!
Now how am I suppose to wipe, or flash new rom without getting into the recovery? I got to fastboot and plugged in the USB cable and tried to ran terminal but it was unsucessful. I tried to copy some new files to the phone via adb command but keep getting the error "BootMagic failed".
Any help?

xxlikquidxx said:
i had a friend with a similar problem. He rooted the phone with the 1-click root app from the market, he then installed ROM manager from the market and try to flash Cyanogen mod ROM, afterward the phone went black. The only thing happen to the phone now is the X screen and its keep boot loop. I tried went to fastboot, works fine, then I tried to go to Recovery but it restart right afterward!!!
Now how am I suppose to wipe, or flash new rom without getting into the recovery? I got to fastboot and plugged in the USB cable and tried to ran terminal but it was unsucessful. I tried to copy some new files to the phone via adb command but keep getting the error "BootMagic failed".
Any help?
Click to expand...
Click to collapse
all is not lost if you can still get into hboot:
Have you tried to restore these original files via adb?
boot boot.img
recovery.img
system.img

I have this problem now...
It keeps on rebooting and rebooting ... and just comes not forther than the flashing X..
I tried system wipe but this didnt help ( I installed a battery widget which wasn't for my rom)
how can i restore my nexus now?
Pleas help!
Edit: Found a way...
Unlock you phone, fastboot, clockworkmod(?) recovery and the select the nandroid backup...
about passimg (see lower) i have no clue

passimg FRG33...
Sent from my Nexus One using XDA App

Even though solved, something to keep in mind: Its probably a ROM (or kernel issue as they said), but I had a revolving X due to a bad battery too.

it can be solved
ViSK said:
Hi everybody!
I'm trying to buy a used Nexus One, good price, but the owner claims that the phone "continuously reboots to "X" screen." but that IT can be fixed flashing the rom.
Is it true?
I'm reading on the internet that having the nexus one loop rebooting is a somehow common problem, and people got it fixed flashing the rom, or by moving some shifted pins on the battery. Do you guys think it's something reparable? Everybody that had this issue solved it? Or I risk that the phone is actually broken, and I might be buying a phone that I will not be able to use?
Thanks!
Click to expand...
Click to collapse
4 color problem can be solved ..

[Q] Stuck at android logo

Hello. I looked over all the forums and other site's forums. (Android forums, droid x forums etc...) and finally had to post. Sorry for the trouble.
I have a droid x I got 9/2010, one of the first ones out. Recently on a friend's advice i rooted and uninstalled some of the "bloatware". (NFS demo, Blockbuster, etc...). Then I made the mistake of OTA-ing to GB. You guys probably know what happened. So then I decided to factory reset, which just dug the hole deeper. Now I can't get past the "m" logo unless I go into safe mode. I'm thinking about calling VZ as a last resort
I have purchased a full version of clockwork as well as the dx bootstrap, but i understand that without getting into a normal boot I cannot run those programs to try and change the rom/run recovery.
I tried SBF-ing, as well as reinstalling the bloat, both with no luck. Any other ideas?
Thanks a million,
Danny

Did you do a full sbf? If worst comes to worst, and you have insurance, call verizon and tell them you lost it
Sent from my DROID X running MIUI

Yeah, i'm trying the SBF again, using the Linux instructions in the sticky. (My laptop runs Ubuntu) I still can only boot into safe mode. I'm probably gonna leave it in safe mode for now so I can call Verizon. I may not say i've lost it, maybe that it's broken and I don't want to ship a bag of metal parts through the mail/take to store. I figured I was up a creek, but I thought to check. Thanks!

Whenever you SBF and the phone misbehaves, you should do a factory reset. Did you try that?
Edit: Just reread your post and saw you did try that. Try the SBF again followed immediately by factory reset. Also, try the Droid2 bootstrap instead.

Try the bootstrap? If it's a program I need to run then your advice is moot. I can only get into safe mode, which doesn't allow me to run anything. And now my phone displays no icons, just the top status bar. The screen is blank, i can't switch panels and i can't access any menus. I think it's a paperweight.

Can you get to the bootloader screen? If so you can sbf with 1kds linux cd
Sent from my DROIDX using XDA App

I followed a thread explaining how to "sbf" using Ubuntu. (it's a sticky on this forum) I have Ubuntu Linux on my laptop so i did it. It still got stuck at the "m" logo. I "sbf"-ed again with a different sbf file supposed to be Gingerbread. Still stuck at the logo. I understand since my phone will boot it not considered a brick. (I work in the IT field and have dealt with bricked routers,etc...) But the last two sbf's failed.
I'm still open to suggestions. I may go to a VZ store tomorrow afternoon, but until then i'll try anything since it can't get much worse.

I'd try 1kds. One way or another you should be able to get back to froyo and start over. Just to be sure you are using d2 bootstrap?
Sent from my DROIDX using XDA App

I'm under the impression that this "bootstrap" thing is a program you have to run while in the phone's OS. If so i'm out of luck since I can't. My phone won't boot into safe mode anymore. Now it looks like a normal boot, but there's no icons, just a black background and the upper status bar. (signal, clock etc). i can't get any menus except the sliding unlock screen. The buttons on the bottom do nothing. (Holding HOME displays a screen saying I have no recent programs, ironic since I can't run anything/go anywhere)
So if Bootstrap is something I can load/run without being in the OS, i'm good. But everything I read says otherwise. Thanks either way.

D2 bootstrap is an app. You could run your phone forever without it. It's primary function is allow you to get into cwm to flash things or make a nandroid backup.
Sent from my DROIDX using XDA App

I just discovered that. So it's something I could have installed before it all went south. I'm trying this 1kds sbf thing, but i think it's gonna fail like the last time. I'll post the results later.

Well it lets me into the OS, and it's not safe mode, but I can't really do anything. The screens are still empty. I can get to the apps menu, but touching any of the icons does nothing. If it did i'd just run the z4root and then bootstrap from my SD card. But the icons won't do anything. I'll keep trying things until I can run stuff from my card. I'm determined to get this to work.

You successfully burned the 1kds discount, got your phone into bootloader mode, and ran the disc? What did your pc screen say the moment you ran the sbf?
Sent from my DROIDX using XDA App

You should be able to SBF your phone and then immediately boot it into the recovery menu (hold the Home key while turning on the phone, then press the Search key to get the recovery menu). From there, do a reset, wipe, or whatever it's called. That should get rid of whatever remaining software turds is causing your phone problems. If that still doesn't work, then I'd chalk it up to a hardware problem.

I did burn and run the CD. It didn't say anything special after it ran but i wasn't looking for something special. Now I can't get to the recovery menu. It's still frozen at the logo. I can get into safe mode, sometimes. I'm gonna take it into VZ tonight just to see. But I recently found out I haven't been paying for insurance this whole 11 months i've had it. So my idea of a replacement got more expensive.

Was trying to find out if you got to the "boot baby boot" screen before it did it's thing. Bummer it didn't work.
Sent from my DROIDX using XDA App

Yeah, i think it's a hardware issue so i'll see what Verizon says. Regardless thank you all for helping. I'll give you "thanks" after work today. Rock on!

[Q] GoLauncher seems to throw my KF into a bootloop?

I was having problems yesterday, I though my KF was bricked. I got some help and I got my phone to start again. But for some reason even after following this thread http://forum.xda-developers.com/showpost.php?p=19552626&postcount=1 my KF was still rooted when everything was over. I don't know why it was still rooted but when I tried to root it again, SuperOneClick said "Are you sure you want to root, you are all ready rooted".
Anyways I installed Root Explorer, it worked, so I guess I still had root. So now I wanted to install the Android Market. But first I wanted to switch Launcher because I have to anyways in the end.
I installed GoLauncher (GO_Launcher_EX_HDTest_V2.69Beta.apk) from their website. After installation, my KF seemed to lag, almost become unresponsive. Then a popup appear telling me to pick eithier the Amazon Launcher or GoLauncher. I picked GoLauncher and my KF wouldn't turn back on. I have to press the Power button a few times really fast to get back to the Lock Screen. Once I'm their I'll slide the lock arrow across and my screen just shuts off, my KF doesn't power off, just the screen. I turned my phone off for 20 seconds, restarted and back into bootloop with that Kindle Fire splash screen. I cant say for sure that it is GoLauncher but the first time my KF boot looped it was after I installed it and the 2nd time happened immediately after GoLauncher was installed.
I really don't know what I'm doing wrong or missing? Am I using the wrong version of GoLauncher or am I missing a step? Right now I'm following the "Unbricking" guide again to get my KF to work.
EDIT: I just followed steps 1-6 from the Unbricking guide and my KF is working again, but like I said for some reason I still have root. If I can't figure out what I'm having launcher trouble I'm just going to unroot I guess.

Try version 2.68

Droidanian said:
Try version 2.68
Click to expand...
Click to collapse
Does it need to be installed in any certain way? Once installed how do I switch from stock to GoLauncher?

Just install it the normal way and choose "Open" once the installation is complete.

Kinda sounds like HD test version of the launcher was too much. I think go launcher has a failsafe style thing where when it becomes too much for the device, the choose launcher option pops up but...you choose go launcher again anyway lol. You probably weren't bricked or anything like that, actually what it sounds like is the launcher was malfunctioning or eating up all the resources causing the device to become unresponsive. Did you restore your kindle already? If not, a few adb commands could probably get you out of the situation

foxdog66 said:
Kinda sounds like HD test version of the launcher was too much. I think go launcher has a failsafe style thing where when it becomes too much for the device, the choose launcher option pops up but...you choose go launcher again anyway lol. You probably weren't bricked or anything like that, actually what it sounds like is the launcher was malfunctioning or eating up all the resources causing the device to become unresponsive. Did you restore your kindle already? If not, a few adb commands could probably get you out of the situation
Click to expand...
Click to collapse
yeah i had to use fast boot and what not to get the kindle back on, but once i did i just installed golauncher 2.68 the latest stable one and everything works except sometimes widgets will say i dont have any space left but i have plenty.
i guess like you said that HD golauncher was just too much and was messing my KF up.

As mentioned to you already in the unbrick thread, you still have root after the fix because it doesn't remove the system partition. Why not just leave it stock until these types of things are more stable. You might get yourself into trouble where my guide will not help you anymore.

ubeezee said:
As mentioned to you already in the unbrick thread, you still have root after the fix because it doesn't remove the system partition. Why not just leave it stock until these types of things are more stable. You might get yourself into trouble where my guide will not help you anymore.
Click to expand...
Click to collapse
If he bricks it again, good luck getting help from anyone, period. It's obviously your choice what you do with your device, but it does not mean I or ubeezee (we work together to solve the questions) or anyone else will help you to undo it. However, Amazon seems to be willing to forgive him so I guess he can still go that route.
I told you why your device is still "rooted," do you not listen? Not listening/reading is probably why you ended up in the predicament you were in. You don't read and you don't listen to what people say when you ask questions.
Accidents are forgivable...blatantly doing something you know will probably screw your device up (after you already screwed it up once by doing so) is not so much.

Nexus 7 Wont Boot

Ok, so everything was going fine and dandy so i decided to root my nexus 7. it was amazing, i was able to over/underclock. Then i remembered an app that i had called chainfire3d that allows you to force certain things on the gpu such as anti aliasing and full 32 bit color on some things. anyways after an install it needed to reboot. once rebooted, it just sits at the google screen with the little lock thats open at the bottom. going into bootloader by holding down all the buttons gets me to the screen but then it freezes. cant boot, cant get into bootloader. any help?
Thanks in advance.

jombo2323 said:
Ok, so everything was going fine and dandy so i decided to root my nexus 7. it was amazing, i was able to over/underclock. Then i remembered an app that i had called chainfire3d that allows you to force certain things on the gpu such as anti aliasing and full 32 bit color on some things. anyways after an install it needed to reboot. once rebooted, it just sits at the google screen with the little lock thats open at the bottom. going into bootloader by holding down all the buttons gets me to the screen but then it freezes. cant boot, cant get into bootloader. any help?
Thanks in advance.
Click to expand...
Click to collapse
sounds like you need to go to the android development list and look for the unbrick thread that has directions to put the original os back on. Then reflash your favorite recovery/rom..etc.

jinside said:
sounds like you need to go to the android development list and look for the unbrick thread that has directions to put the original os back on. Then reflash your favorite recovery/rom..etc.
Click to expand...
Click to collapse
ok, but. im no android fixing expert, but i know my way around it really well. anyways, cant you do nothing if you cant at least get to the recovery screen?!
i have no idea.\
*EDIT
Finally got recovery to work by lots of reboots and was able to reflash the whole thing. i guess let this be a lesson to people trying chainfire.