I've got a friend with a Nexus One, she bought it over Craiglist. The phone worked fine, it was rooted and had 2.2 running on it and before that was CM 5.0.6. She was trying to flash nexdisire on it, and it when she started it up, it was on the nexus one boot up screen for 5 or 10 minutes. She got worried it wasn't working and she pulled the batter out. Now when she tries to start it into recovery mode, the LED just flashes and nothing happens. Anyone know if there's a way to fix this?
Related
Hey guys, I've got an odd problem and am hoping somebody out there can help me out.
I bought a nexus one a while ago and promptly rooted it and installed cyanogen's 5.0.6 mod. I followed the guide on XDA to the letter and had no problems at all. Cyanogen's mod was great and the trackball alert pro was amazing.
My brother saw my phone and after his jailbroken iPhone called it quits he bought one offline from www.google.com/phone. He asked me to unlock it and put cyanogen's mod on there.
I used the same files, that I did for my phone, and followed the same steps listed on the guide to the letter, just as I did for my own phone. I didn't change one thing in the process.
However, after booting past that lovely cyan colored x and getting into the phone, it would randomly reboot, and then get stuck at the solid X logo, forcing me to take out the battery. I would take it out, wait 30 seconds, put it back in, only to have it happen again.
I thought it was a wiping issue, so I redid everything to no avail. I even put everything back to stock, and tried once again doing everything I had done for my phone to no avail. I can't figure it out and it's frustrating me. All the files are the same that I used on my phone, nothing is different except the phone, yet whenever I install the Rom, it randomly reboots and gets stuck on the solid X logo.
So, as you can see I'm at a loss. I'm not sure why my phone works and his doesn't. FWIW his phone DOES NOT reboot when on stock everything, only when a custom ROM is on it. Also, I set my phone back to stock everything and re-rooted/flashed and have had no problem, yet when I do the same steps on his phone, random reboot/frozen.
Can anyone out there help?
Nobody?
SphericalPuma said:
Hey guys, I've got an odd problem and am hoping somebody out there can help me out.
I bought a nexus one a while ago and promptly rooted it and installed cyanogen's 5.0.6 mod. I followed the guide on XDA to the letter and had no problems at all. Cyanogen's mod was great and the trackball alert pro was amazing.
My brother saw my phone and after his jailbroken iPhone called it quits he bought one offline from www.google.com/phone. He asked me to unlock it and put cyanogen's mod on there.
I used the same files, that I did for my phone, and followed the same steps listed on the guide to the letter, just as I did for my own phone. I didn't change one thing in the process.
However, after booting past that lovely cyan colored x and getting into the phone, it would randomly reboot, and then get stuck at the solid X logo, forcing me to take out the battery. I would take it out, wait 30 seconds, put it back in, only to have it happen again.
I thought it was a wiping issue, so I redid everything to no avail. I even put everything back to stock, and tried once again doing everything I had done for my phone to no avail. I can't figure it out and it's frustrating me. All the files are the same that I used on my phone, nothing is different except the phone, yet whenever I install the Rom, it randomly reboots and gets stuck on the solid X logo.
So, as you can see I'm at a loss. I'm not sure why my phone works and his doesn't. FWIW his phone DOES NOT reboot when on stock everything, only when a custom ROM is on it. Also, I set my phone back to stock everything and re-rooted/flashed and have had no problem, yet when I do the same steps on his phone, random reboot/frozen.
Can anyone out there help?
Click to expand...
Click to collapse
I had the same issue with mine and a buddys N1... not sure exactly what to do but I wiped right before I put cyan on and the again right after and if started fine after that... wipe it was much as you do when you poo! lol worked for me! GOOOOD LUCK!
Thanks for the tip. When My brother gets off work i'll try it on his phone and let everybody know the results
-------------------------------------
Sent via the XDA Tapatalk App
zippa71385 said:
I had the same issue with mine and a buddys N1... not sure exactly what to do but I wiped right before I put cyan on and the again right after and if started fine after that... wipe it was much as you do when you poo! lol worked for me! GOOOOD LUCK!
Click to expand...
Click to collapse
Well I tried your suggestion with no luck. It rebotos and gets stuck at the X after about a minute inside the homescreen
Hi, hopefully someone can help me pinpoint what's broken so I know where to fix.
My phone comes on, but nothing shows on the screen, phone seems to make no sounds. Have not tried calling it yet
ADB shell works I can navitage the file structure.
Logcat goes on forever...
Backstory: I'm not new rooting and mods, rooted since jesusfreak's root, Been running on Cyanogen 5.0.7 since it came up, Updated to Cyanogen 6.0 a few hours ago everything was going fine phone was laying on the desk, picked it up and the screen wouldn't come on, I assumed the phone froze and pulled the battery. No G1 Screen, no bootscreen. Recovery same thing, Power+Camera same result.
I'm worried I'm looking at a broken ribbon cable? I shouldn't be able to adb if I was bricked right?
Well I just went ahead and bought a Vibrant...
Basically I woke up in the morning and my cognition 2.2 beta 9.1.2 had reflashed itself like I had just flashed it. I thought it was a bit weird, so I decided to try to install apps. It said I had no space for it, which was not true as I have plenty of space. When I restart my phone I lose all my settings etc, so I decided to try an odin oneclick restore, but it's stuck in download mode, and odin seems stuck saying "<ID:0/005> DO NOT TURN OFF TARGET!" I've been waiting for about 10 minutes now and i'm getting rather worried, as it has never taken this long. It seems like a hardware failure to me. What would be the next course of action?
I ended up successfully flashing back to stock, but now after boot, nothing is displayed. on the device, the keys do light up and respond to touch, however.
Update: Took it to the at&t store today and they gave me a brand new cappy, though unfortunately I can't put this one into download mode for some reason. Anyone know how to fix that? XD
Garjani said:
Update: Took it to the at&t store today and they gave me a brand new cappy, though unfortunately I can't put this one into download mode for some reason. Anyone know how to fix that? XD
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=812434
Have checked as many threads and post as possible - And I think I have royally screwed up. Problem is My HTC Google Nexus One will only vibrate continuously until either the battery or power is pulled. I did root the phone, and installed Clockwork Mod recovery making a full back up of the factory image. This was as far as I got in my quest to upgrade the OS to something more modern.
The phone worked for a day and a half after rooting, and worked fine after installing ROM Manager. But i kept getting prompted to upgrade from 2.1 Eclair to 2.3.6 Gingerbread. So I tried to run that upgrade and it failed with a triangle with exclamation mark. I rebooted and thought nothing of it. Later I installed Snapchat, and an hour after that the phone wouldn't respond to accessing 'settings' or any other system folder. So I had to pull battery. Tried to reboot and it stalled at the starting animation and that was the last action I saw from both the screen or otherwise.
So although I read there is a risk to rooting your phone, I figured it went smoothly as the phone functioned well for a day and a half.
Anyone have any thoughts on this? I read if you can't get to any of the 3 boot screens then you're bricked. I just can't understand how it happened so easily?
Hi all,
I am completely running out of things to try and do now.
After installing Android 7 on my Note 5 I had the strangest issue that i in general have never seen on a phone. The screen is simply black (which isnt that strange) and the phone is fully functional. Bare with me, after reseting it multiple times so it would finally come on the screen goes crazy and turns goes into so many colours (if it turns on that is). Its either that or jumps all around the phone, quite literally it glitches out completely. Its like one of those virus cut scenes you see in movies, it goes different colours, glitches out, jumps around and completely misformats.
From the beginning i knew this was not a broken screen.
So far i have tried.
1. Factory reseting the phone. That gave me about 5 minutes of normal use until i locked the phone and it wouldnt unlock again.
2. Factrory reseting multiple times... again to no avail, it would work for short periods of time and glitch out again.
3. Reflashing stock Android 7 in Odin. - No avail.
4. Flashing Dr.Kretans Rom... worked for 1 day which made me so happy and think that the problem was solved but then the same problem persisted.
5. Installing Arters Kernel.. (arter97-kernel-n920cig-22.0) Nothing... literally did that today and still NOTHING
6. Re partitioning. Quickest process and no avail.
In more detail, if the phone does sucessfully boot, and bare in mind sometimes it takes more than 2 hours to get ANYTHING on the screen (including recovery which doesnt boot up either until the initial apperance of something on the screen)
I tried taking the phone to a phone shop before doing anything myself and since in England this phone was never released theyre refusing to touch it. I tried calling samsung and they dont want to do anything either cause its not a UK variant.
Could someone please tell me anything else i can try. I feel like im totally running out of options here.
My phone details are as follow
Galaxy Note 5
SM-920I Singapore Singtel Variant
Running on 6.01 (i downgraded from Kretan)
And the kernel is the one previously mentioned v.22.0
I would appreciate anyone's help or suggestions so much at this point. All these problems started since the 7.0 update a few weeks back :/
Oh its also running TWRP recovery (arter97-recovery-n920cig-22.0-twrp_3.0.2-0.tar)