Hi,
My roger's dream decided to stop working today (i've only had it for like a week). It's rooted, but I haven't done anything major to it. It was running stably for a couple of days after rooting it so I'm fairly confident that it's unrelated.
I wasn't doing much at the time, messing with Klaxon i believe, but it randomly shut off and now whenever it tries to boot, it gets stuck at the splash screen (just playing it over and over).
I've tried booting in safe mode (w/ Home button) and it won't come up. That's about all i know how to do. can anyone help me out with this?
Thanks so much, i'm in a state of crisis right now.
Yea just wipe the phone, reapply the update.zip and it should be good. If that fails. You may need to backup your sd card, wipe that, redo it and put just the apps and apps-private folder back in and link it. (Unless your rom automates that for you)
You can also try in the recovery console from cy the alt-x to terminal, then type fix_permissions and do a fix ext filesystems. That may restore you as well.
Does pressing Power + camera key get you into the fastboot screen?
Related
Hello!
First real problem EVER with this phone. Am running Cyanogen's latest 4.1.999 build which has been running fine for the last 2 weeks. Nothing moved or changed recently besides un-installing the iMusic App earlier today. At any rate I had it plugged into my PC via USB, pulled cord out (never had an issue doing this before)... knew I had a couple txts waiting so tried to wake screen... lights came on but black screen (has delayed like this before... wasn't worried yet). Waited, tried pressing menu again then opening keyboard and pressing menu... nuthin. Suddenly a quick buzz and it reboots and I see the T-Mobile G1 screen (STILL not worried at this point since I know Cyanogen 4.1.999 is experimental and to not begrudge a random reboot here and there... HOWEVER... after sitting at G1 screen for a bit it simply fades out and SITS.... doing NOTHING. Black screen... no android logo... but button lights are on. Hit power button I get G1 screen again. What I've tried so far:
1. Removed/replaced battery and reboot - No change.
2. Removed/replaced SIM Card and reboot - No change.
3. Removed SD card and reboot - No change.
4. Wasnt able to at first, but now after leaving battery out for a bit I can boot into Recovery, did a wipe, tried rebooting... it just shuts off and doesnt reboot. Recovery again, tried restoring latest nandroid backup... it said it did, reboot, same thing. Finally tried recovery, then flashing latest HTC recovery build needed for Cyanogen's latest... it started, then screen went dark during the process. Almost like a bum power supply! RANDOM!!
Don't have ADB installed unfortunately... was going to but then I realized since I can't even boot into the OS to enable USB debugging what's the point?
Reasonably saavy here but by no means a coder... ideas?? Help?? Sympathy?? LOL
since you have tried a lot of things already, you may need to flash the rc29 image in bootloader and re-root your phone, if it still will not work after the rc29 flash, then it is hardware related altogether.
RC29?? Couldn'ty I just flash to 1.5 if it came to that?
themoebius said:
RC29?? Couldn'ty I just flash to 1.5 if it came to that?
Click to expand...
Click to collapse
to unroot you flash the DREAIMG.nbh file because it will overwrite everything.
themoebius said:
Hello!
First real problem EVER with this phone. Am running Cyanogen's latest 4.1.999 build which has been running fine for the last 2 weeks. Nothing moved or changed recently besides un-installing the iMusic App earlier today. At any rate I had it plugged into my PC via USB, pulled cord out (never had an issue doing this before)... knew I had a couple txts waiting so tried to wake screen... lights came on but black screen (has delayed like this before... wasn't worried yet). Waited, tried pressing menu again then opening keyboard and pressing menu... nuthin. Suddenly a quick buzz and it reboots and I see the T-Mobile G1 screen (STILL not worried at this point since I know Cyanogen 4.1.999 is experimental and to not begrudge a random reboot here and there... HOWEVER... after sitting at G1 screen for a bit it simply fades out and SITS.... doing NOTHING. Black screen... no android logo... but button lights are on. Hit power button I get G1 screen again. What I've tried so far:
1. Removed/replaced battery and reboot - No change.
2. Removed/replaced SIM Card and reboot - No change.
3. Removed SD card and reboot - No change.
4. Wasnt able to at first, but now after leaving battery out for a bit I can boot into Recovery, did a wipe, tried rebooting... it just shuts off and doesnt reboot. Recovery again, tried restoring latest nandroid backup... it said it did, reboot, same thing. Finally tried recovery, then flashing latest HTC recovery build needed for Cyanogen's latest... it started, then screen went dark during the process. Almost like a bum power supply! RANDOM!!
Don't have ADB installed unfortunately... was going to but then I realized since I can't even boot into the OS to enable USB debugging what's the point?
Reasonably saavy here but by no means a coder... ideas?? Help?? Sympathy?? LOL
Click to expand...
Click to collapse
Try adb, USB debugging is usually on with these modded ROMs. See if you can get a logcat to someone who is much more knowledgeable.
Hold on...not to call you out, but im pretty sure cm 4.1.999 HAS NOT been out for 2 weeks...please clarify...did you flash the newest update THEN had problems?
themoebius said:
Hello!
First real problem EVER with this phone. Am running Cyanogen's latest 4.1.999 build which has been running fine for the last 2 weeks. Nothing moved or changed recently besides un-installing the iMusic App earlier today. At any rate I had it plugged into my PC via USB, pulled cord out (never had an issue doing this before)... knew I had a couple txts waiting so tried to wake screen... lights came on but black screen (has delayed like this before... wasn't worried yet). Waited, tried pressing menu again then opening keyboard and pressing menu... nuthin. Suddenly a quick buzz and it reboots and I see the T-Mobile G1 screen (STILL not worried at this point since I know Cyanogen 4.1.999 is experimental and to not begrudge a random reboot here and there... HOWEVER... after sitting at G1 screen for a bit it simply fades out and SITS.... doing NOTHING. Black screen... no android logo... but button lights are on. Hit power button I get G1 screen again. What I've tried so far:
1. Removed/replaced battery and reboot - No change.
2. Removed/replaced SIM Card and reboot - No change.
3. Removed SD card and reboot - No change.
4. Wasnt able to at first, but now after leaving battery out for a bit I can boot into Recovery, did a wipe, tried rebooting... it just shuts off and doesnt reboot. Recovery again, tried restoring latest nandroid backup... it said it did, reboot, same thing. Finally tried recovery, then flashing latest HTC recovery build needed for Cyanogen's latest... it started, then screen went dark during the process. Almost like a bum power supply! RANDOM!!
Don't have ADB installed unfortunately... was going to but then I realized since I can't even boot into the OS to enable USB debugging what's the point?
Reasonably saavy here but by no means a coder... ideas?? Help?? Sympathy?? LOL
Click to expand...
Click to collapse
I am having the EXACT same problem with CM4.2.4. I certainly hope its not hardware, but it sure "feels" like it. Especially when my G1 is even shutting down from the Recovery Menu. I'll try to unroot and see if that resuscitates it.
Another one....
Have a look at my current issue on this thread: http://forum.xda-developers.com/showthread.php?t=582576. Check to see in bootloader mode what your board type is (it states it at the top for those who don't know).
Mine is currently showing an EVT board, which doesn't exist. I've pulled the battery out and am leaving it for a while. It could be a hardware issue, but I'm not sure. I was having the "fading screen" issue and eventually got back to RC7 (when I could get into recovery).
Which recovery are you using?
So I had root access. (i.e. when I first booted my G1 up it said something about a developer phone) and I tried flashing the dreaimg.nbh file to go back down to RC29. It fails every time won't let me do anything else. It just stays srtuck on the bootloader screen when I try to reboot. I've tried about everything I could think of and I'm at wits end. I really hope this problem can be fixed. Does anyone have any suggestions or know what went wrong? Thanks.
Re-download dreaimg.nbh file again. The one you're using may be corrupted.
Why do you want to go RC29 if you have root access? You should be able to flash anything on your phone as is, RC29 is only needed to gain the root.
It won't let me do anything. I'm unable to do anything to the SD card. Although, while typing this I just thought of something. If I got a card reader I could erase the file from my card since I can't do anything to the phone. Maybe that would work. But who knows because I've tried removing the card and booting up and it remains stuck on the bootloader screen. I literally can not do anything else, it's just permanently stuck like that. So I can't mess with anything. And the reason I was trying to downgrade is because I was trying to start all over again but I think I might have ended up screwing myself instead...
I am may be wrong, and please forgive me if I am, but from your post count I am getting the picture that you're pretty new to this.
Tell me if what you did is any different from these steps
You booted phone into h-boot mode holding power and camera buttons
Your phone found dreaimg.nbh and ran it on it's own.
You restarted the phone and got stuck in the boot loop.
Confirm that this is what happened
No, your assumption is not wrong at all. I am pretty new to this.
Yes, I did reboot my phone while holding down the camera button.
It found dreaimg.nbh and ran it but it failed so now I'm stuck in the boot loop with it constantly trying, and failing, to load dreaimg.
Thanks so much for your quick responses.
When it says "failed to load dreaimg.nbh" it means that it does not see it. I have a feeling that a file that you had was zipped.
Let's do this
Boot into recovery by holding power and home buttons
select wipe/factory reset or something along those lines and try booting up a your phone again. I'll be lurking around so just post what you find.
Take a note of which recovery you're running while you're at it too.
No, the file I had was not zipped I don't think cause it sees it and tries to update. It says update in progress then I get the progress bar but when it's finished it tells me: Update Terminate. Update Fail. Then it just goes back to the multi-colored bootloader screen and won't shut off. I can reset it by pressing call+menu+end but then it just starts all over again. So, I can't boot into recovery mode. Matter of fact, the only way to turn the phone off is to remove the battery. Otherwise, it just starts in bootloader mode and continues this viscous cycle.
At this point I don't even care about installing a ROM or anything, I just want a working phone.
I see. Yep.. you're S.O.L.
Just to make sure... when your phone is off and you hold power and home buttons it just goes to h-boot screen, right if so then unfortunately there's only one thing to do: get a card reader, re-download .nbh file and start over. At this point you have no working recovery or rom on your phone. Once you get that going you should be on your way to secure a root and flash whatever rom you need to.
Is it even fat32?
Damn. That's what I thought. I should have just left well enough alone until I did more research and knew exactly what I was doing but I get ADD when I'm hungover. Oh well. Thanks for your help.
This will happen from time to time.. it's always desirable to have a card reader handy. Also.. since you have nothing to loose, this would be a great time to re-format and re-partition your sdcard so you can start squiky clean.
Good luck.... let us know when this is worked out by adding [SOLVED] to the title of this thread.
I have G1 sitting around that I never messed with until last night, so if it's bricked, it's not a big deal. The phone will turn on, and loop through the splash screen. The only way it will boot is in safe mode. When trying to do ANYTHING in safe mode (aside from power down), everything will FC. If i go into the recovery menu with the Home plus End key sequence, I get the "can't open cache recovery command". I've tried to install RC33 in that screen, and get "installation interrupted".
The phone was given to me, so I really don't know if it was rooted or what was on it before. I do remember it worked, and just one day stopped working. When it was working I never saw a superuser icon or any other apps you usually see with a root. Thanks in advance for any help.
No one? Is there just a full update I can throw on the SD card and get it running?
Try formatting the sd card fat32, putting dreaimg.nbh(search) on it. Then, put it in the phone and boot with camera+power. Follow the onscreen instructions, and hopefully it'll work.
If it doesn't, not my fault. Good luck!
Thanks Michael, but I did that already and it really didnt change anything. I noticed the recovery menu looks a bit different, and when I go to safemode, the "android" looks different, but thats it. Still cant boot, and still shows there is no recovery in the recovery menu.
I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
whoisthisis said:
I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
select recovery by holding the vol buttons and power on boot just like fastboot. press vol - for recovery. when u see dead droid hit both vol up and vol down and theres the recovery
Thanks, I was finally able to get into recovery. Wiped data and did a factory reset which again got stuck at the logo screen. Went back into fastboot and ran RSDlite again to flash the stock ROM which gets me to the "Welcome to Droid4" screen where it says "touch the android to start" but the touchscreen is unresponsive. Starting to think there is something physically wrong with the phone....
send it to motorola, I've heard their customer support is pretty good. but if you voided your warranty by rooting/flashing other roms, I've heard bricking the phone and sending it in works to get a new one too
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
whoisthisis said:
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
Click to expand...
Click to collapse
So it has been a couple days now and the phone works totally fine. It looks like the problem was that by removing whatever bloatware that I did, the phone's OS got borked when VZW pushed an update of some kind. Flashing the stock ROM without doing a factory wipe would temporarily solve the problem but eventually the update would get pushed again and the whole thing would lock up again. The factory wipe + reinstall seems to have been the solution to the problem.
Droid 4 running Stock Jb 4.1.2, Safestrap 3.11, Liquid smooth 2.9, CM (last stable)
Everything working fine for a number of months, installed Liquid smooth via -> delete romslot 3, create romslot 3, install Liquid 2.8.
It ran for a number of days no problems. Restarted fine, all features worked great, even the annoying random restart from 2.4 went away.
6 - 10 days in, im surfin' the news sites at work, put it down, screen goes black, i pick it up. Hit the power button cause i realize its off and it just boot loops... so bad i had to vol-/+ pwr, go to flash mode and THEN turn it off b/c it just kept trying to restart, hang on logo.
I got home and decided to AP flash the latest:
9.8.2O-72_VZW-18-2
Blur_Version.98.72.182.XT894.Verizon.en.US for the maserati.
Boot looped a few times, i was able to get it to go into recovery mode, after that it loaded up the stock JB system. First boot it crashed and restarted, second boot it loaded but only the keyboard worked, not the touch screen. Went to the in OS option of factory reset mode + delete storage.
Rebooted, worked. Checked it a few boots, everything is fine. I use Druid 4 Utility Xt894 JB version and apply the root. Works great. Install safestrap, Create new partition, install liquid smooth 2.9. Works for an afternoon... at work today the touch screen stops responding, i restart it a few times. I try to enter recovery mode. Now im in boot loop again...
I've tried re flashing it again, a few times. I tried even going down to the previous release of JB for the phone. STILL 4.1.2!!!! But nothing.... it just boot loops... what did i do wrong? It was running great. No tweaks or anything done to it prior to it having its melt down.
Help please.. ive provided as much information as possible and though i only joined XDA now to post for help, i have read it for a long time as my main source for my phone and have donated to both CM and Liquidsmooth teams previously..
help!!!
I can't see where you are doing anything wrong. You have obviously done your research and have a good idea of what you are doing. I see, after you fastbooted, you went back to Liquid. I think I would try running CM10.1 or even stock for a few days and see if you have the issue there as well. If you do than it sounds to me like it might be a hardware issue. If not, maybe try re-downloading Liquid. Perhaps your zip got corrupted somehow.
I would love too. In fact i would be willing to run it on the stock crappy 4.1.2 if i could get it out of boot loop this time...
It just keeps boot looping on the logo. AP Fashboot flash and BP flash work but recovery and normal boot/reboot mode just goes into M logo boot loop.
I've re downloaded the 4.1.2 jb SBFs from 2 different sources to ensure its not a corrupt file, tried 18_1 and 18_2 software versions...
Is there a way to use the abd shell to get into the filesystem and check whats going on? Is the SBF the last call? or is there another route to see whats going on or just flash EVERYTHING? Like completely back to stock?
I can find my way around a PC file system but im not familiar with linux. Please help me understand, Is it like having CMOS and BIOS settings or equivalent to damaged CMOS firmware? What am i not replacing/reverting by SBF and HOW can i replace/revert BEYOND the basic sbf...
If ya point me in a direction or to someone who can help me out i can do all the foot work just point me in the right direction?
Is this applicable? I found a site talking about using CWM in a ADB shell file push to possibly get access to more features?
The article also goes into reading the busybox / ADB command screen? (sorry for not proper jargin) and see what its doing during the boot loop before it restarts?
Id add the link but i need more posts....
Update: Flashed 18_2 again with a "factory cable" i made, let it boot loop a series of times before it started up into the stock system again.
At first, again the touch screen wouldn't work, random lockups and restarts, etc. Since i just got it into the main system again and i had to leave for the weekend for a trip(no wifi or network), i couldn't mess with it all weekend but i left it on the whole time and kept checking its functionality... gradually its come back to full function. Touch screen works and is accurate, no more lockups, no more restarting, even stopped boot looping when i restart and enter recovery..
Im not sure and i couldn't find any forum converstations or write ups to support to idea but i think after a major crash and you flash new or reflash your SBF, it seems the phone needs time to recalibrate and index? Not sure, but just an FYI. Gonna try loading SS and liquid again.