Last night, I downloaded InnovationsOS v3 from the Nexus One Android Development forum. Prior to this I was using FRF50, and I have a rooted Tmobile Nexus One. I wiped the phone back to factory settings and also wiped the Dalvik cache (as I've been told in the past). Flashing went just fine and within a few minutes I had InnovationsOS after a reboot. (Let me just say, with this one minor exception, InnovationsOS looks incredible and I loved every minute of it).
After install, I set up AdFree which removes ads. I decided to do a quick reboot. The reboot wasn't so quick, and it stuck on the startup screen (the Nexus One/Google logo with the unlocked symbol below) for about 3 minutes. I didn't think this was good, so I tried a battery pull hoping for a normal reboot. Instead, what I got was the android falling out of the box. I tried a battery pull again and attempted to enter recovery, which worked. I wiped, and reloaded FRF50, and rebooted. I got the android and the box image, which wouldn't let me even boot into recovery anymore after several battery pulls. After a couple minutes of being completely stumped (and scared lifeless) I let the phone sit, and somehow it booted into recovery, where I wiped (again) and flashed InnovationsOS (again). After it loaded, it rebooted, and it's been working great since then, with the exception of one minor screen/keyboard bug...I press S, and get Z, or I press delete, and I get enter, etc. Plus hitting OK or Cancel on dialog boxes is impossible and need to use the trackball.
So, I would like to reboot to fix this problem and want to know what will happen, and I want to know what I did wrong above. I know all this sounds completely noob for this forum but I'm willing to learn, which is why I've been experimenting with rooting and flashing roms.
Thanks a lot, any help is appreciated.
Related
Hi everyone,
I have a problematic Nexus One. I've googled the issue and read all the corresponding threads and none of them seem to have boot loop issues as bad as mine. At least I dont think so, anyway.
Where should I start? I recently bought the phone off ebay. The seller did clearly state the phone's issues and that he couldn't be bothered fixing it, let alone paying over $200 to send it back to Google to be repaired or replaced (from Australia). Call me a sucker for punishment, but I do like dabbling in electronics so I thought I'd give this a go and hopefully will be successful. It wouldn't bother me if it rebooted once every few days then rebooted again normally but this isn't the case. I'll try to describe it's behaviour as precisely as I an and I sincerely hope the collective expertise on this forum will be able to help me successfully resolve this issue. BTW, I've been using a gorgeous Desire since July.
The Nexus one is running Modaco r21, 4.06.00.12_7 radio, 2.6.32.9 kernel, CMR 2.5.1.0.
1. When the phone has been powered down for at least 5 mins, it will power up as normal. If left alone on the bench or very lightly used ie a few minutes, then pwr button sleep, no problem. If I continue 'sleeping' the phone every few minutes while using it it continues to function normally for a few hours. If I don't 'sleep' the phone and use it continuously, then after about 20 mins it goes into a reboot cycle with the static 'X' going on and off every few seconds then ending up with the continuously on "X" with the unlocked padlock underneath, which is unrecoverable until the battery is pulled.
2. Battery reinserted immediately after removal and the reboot cycle continues. I can boot into the white Recovery or Fastboot sreens but when I select an action like Recovery, the boot loops starts again. Battery pulled and reinserted again, boot loop occurs again. Pull battery and leave it out or powered down with battery inserted for 5 mins, reboots normally. Then point '1' above continues.
3. I have Rom Manager, Titanium and Superuser Permissions installed. I received the phone with Eclair installed and after many attempts managed to install the new radio and Modaco R21. Last night I tried doing a back up via Rom Manager since I cant get into the black Recovery screen and now Titanium and SU are force closing.
This is all I can think of right now and will update with more info as they come to light. I've been trying to install setcpu to see if underclocking will help however I have been unsuccessful due to SU force closing. I am an Android and Linux noob but am always willing to learn. I really would like to get more stability in this phone so I can either use it as my primary or back up.
Thanks in advance for all your help.
Edit. I magaed to do a factory reset when it dont momentarily allow me into Recovery mode. Wiped all data and davlic as well.
My first instinct is that the phone has suffered or is suffering from a heat problem of some type.
Do you have the android SDK set up on your computer? You should be able to flash an aftermarket recovery using the "fastboot flash" commands. You could also use the "adb reboot recovery" command to reboot the phone directly into recovery mode.
I'll give your suggestions a try. What fastboot commands should I be entering? I am an absolute virgin with all this.
Sent from my HTC Desire using XDA App
I think this thread should have some good information for you
Thanks for the link, mate. I'll have a read and I'm sure there'll be more Q's soon.
Sent from my HTC Desire using XDA App
Hi again,
I've installed Android SDK and usb drivers. Where do I go from there? I am a complete newbie at this so please be kind.
julian.kueh i was posting to ask how things have been progressing along this matter?
I got the same problem. No matter what I do, I can get into Recovery. It stay in loop with X
I change twice recover and nothing.
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.
Ok so I'm pretty sure my phone is done for, but I thought I'd see if anyone knew a solution before I go buy a new phone
Yesterday I dropped my phone (which was running Slimbean), but I popped the battery back in and it worked fine. Then about three hours later, it randomly shut off while I was using it, then started going into a bootloop. Occasionally it will start up all the way, but I'm lucky if its on for 10 minutes before turns back off and starts bootlooping again. I got it to boot into CWM, (the first time it shut off while I was in CWM) and wiped everything and reflashed Slimbeam, but it didn't change anything. Any ideas?
Go back in and do wipes on everything but external drive reflash wipe cache + dalvik cache + fix permissions then boot. Let sit 10 minutes before doing g any setup with Google or phone. This allows all drivers to load and configure prior to having more data to configure.
Sent from my CM10 Linero Odexed Powered by Evil
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.
Everything worked fine for almost a whole year, then my tablet started acting strange last night. It got really bad this morning so i was trying to install a antivirus thinking that might help, but it wouldn't open. Reports of program failures were popping up like crazy, so i turned it off and back on about five minutes later. Now its been over an hour and its stuck in the cyanodenmod loading screen, its never taken this long.
Is there any program i can use on my laptop to wipe everything on my tablet and install another os? I'm not sure how it'd work seeing as how its stuck loading. Do i need to let the battery die? I really just want to plug it in and wipe the whole thing but i haven't a clue where to start.
Please help?
I took the back off and unhooked the colorful wire thing from it to turn it off, and put it back. It restarted fine and now I'm attempting to wipe everything on it. When i first pushed the erase all button it didn't do anything, then after trying a few more times it restarted to a "teamwin" something (have no idea what that is) and it restarted again, so far its back on the cyanogenmod loading loop again. (I'm a little amazed i even managed to root it in the first place, considering i didn't know what "os" stood for before that. I really need help with stuff like this.)
If i can get it back to the normal screen, is there any program i can use to reformat everything and like an alternative to cyanogenmod for the program?
Which CyanogenMod version are you running ? The teamwin that you saw when it booted up was the recovery you flashed to install custom ROMs like CyanogenMod. Make sure you have the latest recovery before anything . take a look here and let me know when your up to date and we can put you device back in working form
http://forum.xda-developers.com/showthread.php?t=2218796