hey guys,
my nexus one switched off all of a sudden... I've tried to switch it on but it's not working anymore... it freezes on the booting animation
additionally, it's not charging
i'm thinking of flashing the stuck rom?
any ideas how to do so?
the device is not rooted!
seas of tears said:
hey guys,
my nexus one switched off all of a sudden... I've tried to switch it on but it's not working anymore... it freezes on the booting animation
additionally, it's not charging
i'm thinking of flashing the stuck rom?
any ideas how to do so?
the device is not rooted!
Click to expand...
Click to collapse
try a hard reset but you might loose your stuff like apps. http://www.androidcentral.com/how-hard-reset-google-nexus-one
Related
Hello, just today I've recieved my new google nexus one, after charging the battery for 2 hrs, i tried to start the nexus one, but when nexus animation starts it's converted into blue instead of coloured.
then my device reboot without touching anything,
it still doing like this 2-3 times then hang on the nexus coloured symbol.
after a while i tried to start again it was the same
another try, it worked and start android system , and after 4 minutes it restarted and doesn't boot the system again, just restarting
i don't know what's going wrong with it.
Please Hellllllp
i highly dought you animation turned blue on a new phone without the bootloader unlocked and a custom rom on it.
Actually, YES, my friend unlocked it and put an Arabic supported ROM, I tried to change the ROM to the original and still the same
Well seems like he has flashed Cyanogen for you too.. Try reflash it and se if that helps.
I tried to reflash the ROM, I have the same problem everytime,
janat83 said:
I tried to reflash the ROM, I have the same problem everytime,
Click to expand...
Click to collapse
Did you try to wipe first?
Redestwing said:
Did you try to wipe first?
Click to expand...
Click to collapse
yes, I've tried that as well, nothing changed
Hello everybody !
I use a stock 2.2 ROM on my N1 for a while and started to experience a strange problem - when i switch on the device it vibrates 7 times and does not turn on. The screen is black.
Removed the battery, tried again, the same result.
What this could mean ? Please, help !
baudy2 said:
Hello everybody !
I use a stock 2.2 ROM on my N1 for a while and started to experience a strange problem - when i switch on the device it vibrates 7 times and does not turn on. The screen is black.
Removed the battery, tried again, the same result.
What this could mean ? Please, help !
Click to expand...
Click to collapse
Try reflashing the stock RUU rom... should fix it. If not, you need to call for support.
The vibrates mean the phone can't initialise... normally fixed by a battery pull.
i have a nexus one stuck on hboot..i bought it thinking i can just restore it,thinking its simple since its a nexus anyways i put the stock pass.img and after it checks it always gets stuck idk what to do done it over and over .
garcia8479 said:
i have a nexus one stuck on hboot..i bought it thinking i can just restore it,thinking its simple since its a nexus anyways i put the stock pass.img and after it checks it always gets stuck idk what to do done it over and over .
Click to expand...
Click to collapse
1) you bought it broken? hehe
2) i can try to help you, be more specific
3) waiting for your answer
lol i guess
buttons n power work
2) everytime i try and try put shipped rom it keeps freezing, not sure whats wrong or what i should do.
and thank you
Hello, everyone.
I have already installed CM11 on my Moto G XT-1040, peregrine. I was curious to learn a bit more about kernels and tried to download one and flash it via TWRP. The problem is that I got one from XT-1032, falcon, without noticing it. The kernel is XPerience 17+ and it's frozen on the boot until this very moment. What should I do? Did I brick my phone or is there a way to recover it?
Oh. It seems that the battery got the phone killed and it finally turned off. (Feels like having some kind of Apple device, which cannot be turned off until the battery is still alive).
I put it to charge... any ideas of the next step? It responded, at least to the charging.
So, now to the real question... can I try to flash the old kernel again? If yes, how?
(I'm really hoping to enter the recovery mode!!)
I'm hoping someone can help me out!
Thanks in advance,
Rodolfo.
Nevermind, I got it backed up and restored it.
rodolfoakira said:
Hello, everyone.
I have already installed CM11 on my Moto G XT-1040, peregrine. I was curious to learn a bit more about kernels and tried to download one and flash it via TWRP. The problem is that I got one from XT-1032, falcon, without noticing it. The kernel is XPerience 17+ and it's frozen on the boot until this very moment. What should I do? Did I brick my phone or is there a way to recover it?
Oh. It seems that the battery got the phone killed and it finally turned off. (Feels like having some kind of Apple device, which cannot be turned off until the battery is still alive).
I put it to charge... any ideas of the next step? It responded, at least to the charging.
So, now to the real question... can I try to flash the old kernel again? If yes, how?
(I'm really hoping to enter the recovery mode!!)
I'm hoping someone can help me out!
Thanks in advance,
Rodolfo.
Click to expand...
Click to collapse
If anyone had the same problem, I hope you guys had a backup file on TWRP, which restores almost everything but the bootloader logo from the other kernel.
Good news, the problem was solved just with the Recovery Mode. It needed to get into the bootloader, which was only possible after the battery died.
rodolfoakira said:
Oh. It seems that the battery got the phone killed and it finally turned off. (Feels like having some kind of Apple device, which cannot be turned off until the battery is still alive).
Click to expand...
Click to collapse
Holding the power button for 20 seconds or so didn't work?
No it didn't. Unfortunatelly. D:
unwired said:
Holding the power button for 20 seconds or so didn't work?
Click to expand...
Click to collapse
No it didn't. Unfortunatelly. D:
No commands were working at the time. Just the frozen bootloader screen from the wrong kernel. When the battery died, after some 5 minutes or so of charge I managed to turn it on on the bootloader and put it on recovery mod. Wow, I killed all my nerves, thinking I lost my close-to-new phone. Then backup saved my day!
i was using my phone this morning alright and it suddenly froze for 5 seconds and turned off. i tried opening again, but it was looping back to the LG splash screen. this was annoying enough because i wasn't doing any experiments or anything. i was using it like i usually do and it suddenly did this. i tried to reset it, same. went to TWRP to make a backup but even the recovery froze and turned off. moved a rom to the phone and tried flashing it, THE RECOVERY AGAIN FROZE AND PHONE TURNED OFF! i then considered flashing it to stock. i opened LG UP and put my phone into download mode, then started the flashing process. it completed all the way to 100 and then my phone turned to the lg screen and then to the TMOBILE screen and then again rebooted and got into a bootloop! what the hell is happening? flashing the stock is like the final solution. what should i do? Please please please help me i'll get into a lot of trouble if i dont fix my phone.
Armaghan Bashir said:
i was using my phone this morning alright and it suddenly froze for 5 seconds and turned off. i tried opening again, but it was looping back to the LG splash screen. this was annoying enough because i wasn't doing any experiments or anything. i was using it like i usually do and it suddenly did this. i tried to reset it, same. went to TWRP to make a backup but even the recovery froze and turned off. moved a rom to the phone and tried flashing it, THE RECOVERY AGAIN FROZE AND PHONE TURNED OFF! i then considered flashing it to stock. i opened LG UP and put my phone into download mode, then started the flashing process. it completed all the way to 100 and then my phone turned to the lg screen and then to the TMOBILE screen and then again rebooted and got into a bootloop! what the hell is happening? flashing the stock is like the final solution. what should i do? Please please please help me i'll get into a lot of trouble if i dont fix my phone.
Click to expand...
Click to collapse
infamous bootloop, a hardware issue. you need to send it back to LG or tmobile. relock the bootloader.
raptorddd said:
infamous bootloop, a hardware issue. you need to send it back to LG or tmobile. relock the bootloader.
Click to expand...
Click to collapse
Can't do both because i live in Pakistan and i Bought it second hand. So i do not have it's box amd neither the warranty. Wat should i do now?
Armaghan Bashir said:
Can't do both because i live in Pakistan and i Bought it second hand. So i do not have it's box amd neither the warranty. Wat should i do now?
Click to expand...
Click to collapse
that sucks. well you can bake the board but its temporary sometimes. or you could make it boot freezing it and install kernele auditor and disable big cores. may need a custom kernel for that..
or buy a motherboard..
Could you explain these methods in a bit detail? The baking and freezing
Armaghan Bashir said:
Could you explain these methods in a bit detail? The baking and freezing
Click to expand...
Click to collapse
do a search on how to fix LG G4 bootloop. the freezing its somewhere in here tmobile section. i know you have to put in plastic bag and have it in the freezer so it doesnt get hot and bootloop is just to keep it cold to point of no bootloop while you retrieve data. but you can disable big cores. and let it run on 4 cores.