Helloo...
I had my nexus one updated to cm 6.1.1 stable.
The next day i noticed he keeps restarting the phone.
I thought let me pull out de battery and turn the phone on.
Now its stuck at the coloured x and i cant get in recovery.
When i boot into recevory it gets stuck again at the coloured x.
I have flashed stock kernel frg33 and flashed amon recovery with fastboot and tried the passimg method to but it still gets stuck.
My phone is rooted and unlocked bootloader.
What can i do now?
Thnxx in advance
Can you get into bootloader by--> holding down volume-dwn, then pressing the power button, and the releasing the power button while still holding down volume-dwn?
You might need to remove you battery in between tries of this (plus pressing the power button i hear, with the battery removed to drain and remaining power..for 5 secs at least).
If that doesn't work, you could try the three finger salute for Android: Volume dwn+trackball pressed, then tapping power button and letting go of power button, and then the other two.
in most cases you will still be able to use adb
try running 'adb reboot recovery'
Like i sad, i can boot into recovery using the bootloader. But when it start up in recovery it gets stuck at the coloured x.
Fastboot is working but i cant get the adb to work.
Fastboot sees my device an adb doesnt.
What can i do to make adb work?
I installed new sdk and htc sync.
Running on windows 7
try to flash a new recovery through fastboot
download amon ra
open up a cmd
"cd " to directory where you downloaded it
rename amon-ra-recovery.xxxx.img to recovery.img
fastboot flash recovery recovery.img
then try to boot to recovery again
I tried that 10 times but it doesnt work.
Still gets stuck at the coloured x
Fastboot flash the system, bootloader, userdata, etc, and seem if it will boot to system?
Sent from my Nexus One using XDA App
this might sound a bit daft but try taking your sdcard out of the phone and rebooting to recovery
Tried that all. But doesnt work
What sort of error messages are you getting?
Sent from my Nexus One using XDA App
Have you tried to erase cache and dalvik through fastboot commands?
Sent from my Nexus One using XDA App
Nothing!!
Everything what i try to do goes wel.
Update with passimg goes wel.
Fastboot system, boot, userdata, bootloader, everything goes wel.
I dont get any error.
But when i start my phone it gets stuck by the coloured x.
Looks like hardware failure, then...
Sent from my Nexus One using XDA App
Oke that is not good cause i have no waranty anymore.
danger-rat said:
Have you tried to erase cache and dalvik through fastboot commands?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
What is the fastboot command to erase dalvik?
Good question - I've used the erase cache command, and just assumed there would be an erase dalvik command. I may be wrong...?
Sent from my Nexus One using XDA App
Ashvan said:
Oke that is not good cause i have no waranty anymore.
Click to expand...
Click to collapse
When did you get your phone?
Sent from my Nexus One using XDA App
I bought it second hand in september this year. I think its a year old now.
But since i have everything unlocked the waranty is void?
What is a dalvik cache exactly?
Does nobody knows the fastboot command to erase it?
Ashvan said:
I bought it second hand in september this year. I think its a year old now.
But since i have everything unlocked the waranty is void?
Click to expand...
Click to collapse
The very first nexus phones are just coming up to a year old, so the chance is that yours is still in warranty. Call HTC, and see what they say...
Sent from my Nexus One using XDA App
Related
I recently recieved a Nexus One that I cannot reflash at all. It simply will sit at the static X logo upon boot. I can still access the bootloader. Recovery does not work at all. I have tried to wipe and restore using fastboot, and whenever I try to write any images, they seem to push to the phone (progress indicator on phone fills up, etc) but I never get a finished message on the computer. I let it sit for half an hour before I gave up on it and pulled the battery. I have tried this with Windows 7 on a desktop and a MacBook Pro, using various different USB ports and cable combinations on them. I cannot do the PASSIMG.zip method either because the phone never seems verify the FRG83 image but will never offer me the Yes or No dialog to write out the files. It kicks back to the regular bootloader options.
Is this Nexus One bricked? Can I bring it back from the next-to-dead? Am I really just missing something obvious here?
By the way, have you unlocked the bootloader? Using fastboot to push anything requires unlocked bootloader.
The bootloader is unlocked.
Ok well this might be a stupid question but you said you were using windows 7 and with windows the extension is hidden so if you name the file passimg.zip it will actually be named passimg.zip.zip and the phone won't recognize it so try naming it passimg
Also for the passimg method did you try using the frg33 file instead of the frg83 file.
I have Windows set to show all extensions regardless. I would say I'm plenty savvy when it comes to computers, just not Android (yet )
I tried both the FRG33 and FRG83 files. They just don't seem to do anything. The phone seems to check them: It says that it found the PASSIMG.zip and the progress bar in the upper right slowly fills up. Once it fills, it sits for a second and just kicks back to the normal bootloader choices as usual.
Thank you for all the quick responses! I hope I can fix this Nexus One. It's practically in mint condition...
It's strange that the bootloader is unlocked but you can't flash any ROMs :/
When you say that recovery doesn't work at all what exactly do you mean by that? When you boot into recovery what happens?
Now since we talked passimg I doubt it will work more than the others but did you try the GRI40 file?
I cannot seem to find a GRI40 that can act as a passimg. And when I say recovery doesn't work at all I mean that I just proceed to the the static, non-moving nexus logo and it doesn't ever proceed past it. I have tried to use "fastboot boot recovery.img" with a ClockworkMod and Amon_RA image and it seems to upload to the phone but I just end up with the nexus logo.
It seems that I can fastboot erase the userimg and cache, and get results that are expected. When I fastboot flash anything it sends to the phone but the phone never seems to do anything with it past that point.
When it gets stuck on the static X logo do you get 7 vibrations?
Did you try and fastboot flash Amon-RA then try and reboot into recovery. And for the GRI40 file it's on htc's developers web site http://developer.htc.com/
I only get one vibration. I tried to flash Amon_RA and reboot but it's like the flash never completes. I don't get anything different.
same issue here and browsing since yesterday for a proper solution and not yet !! any brave ideas ,pls share!
OverdrivenCore said:
I only get one vibration. I tried to flash Amon_RA and reboot but it's like the flash never completes. I don't get anything different.
Click to expand...
Click to collapse
Try fastboot erase to erase everything on the phone then flash fresh recovery
Sent from my Nexus one using xda app-developers app
Kind of in the same boat, opened a thread my self but none of the suggestions are working. When im in fast boot it freezes for a second a runs a quick check. I just about catch it saying wrong passimg image or something along them lines.
Sent from my GT-I9100 using xda premium
Here is what happened:
1) Installed Android Rev HD, worked fine.
2) Installed Xposed mod and bricked device (got stuck at Beats Audio)
3) Booted into recovery, restored Nandroid backup (of STOCK rom).
4) That worked fine and I was able to boot back into stock.
5) Then I went back in Recovery to Install Android Rev HD back, after that was installed, I got a prompt in Recovery that root might be removed and asked if I wanted to restore it or something. I clicked yes and my phone immediately turned off.
Now I am stuck in a loop. The phone keeps restarting and then booting into recovery but the recovery screen only flashes for 1s before the phone restarts and completes the whole cycle again. I am only able to boot into the bootloader. Even if I power down the device, once I turn it back on, it tries to boot back into recovery again and starts the whole loop. Please help.
Update: I tried reflashing recovery using the All-In-One-Toolkit but it says "error: device not found". However, the command "fastboot devices" does detect the device.
Update 2: Tried using adb to "fastboot flash recovery" but it wouldn't work. I tried reflashing CWM (downloaded from their website) and TWRP but both of them suffer the same "load up for a split second" and then restart issue.
Update 3: Wiped the cache and now im able to boot back into recovery.
You need to force it to turn off me thinks. Not sure how you do it on the One. On my old sensation it was power+volume keys. Once off connect it to a charger, see if it charges, if yes then it should get passed flash screen. Try flashing a Rom but make sure you are fresh flashing, not flashing over something.
The quick restart thing sounds like a command that's stuck. Once it gets to fastboot it's rebooting as the commands there, but not clearing the command.
Sent from my HTC One using XDA Premium HD app
OllieArmageddon said:
You need to force it to turn off me thinks. Not sure how you do it on the One. On my old sensation it was power+volume keys. Once off connect it to a charger, see if it charges, if yes then it should get passed flash screen. Try flashing a Rom but make sure you are fresh flashing, not flashing over something.
The quick restart thing sounds like a command that's stuck. Once it gets to fastboot it's rebooting as the commands there, but not clearing the command.
Sent from my HTC One using XDA Premium HD app
Click to expand...
Click to collapse
Im able to turn it off via bootloader but it isn't doing me any good since once I power the phone back on, it goes back into the loop again.
If you can turn it off in bootloader, can you not flash recovery?
Sent from my HTC One using XDA Premium HD app
OllieArmageddon said:
If you can turn it off in bootloader, can you not flash recovery?
Sent from my HTC One using XDA Premium HD app
Click to expand...
Click to collapse
I was able to reflash recovery via adb but the "new" recovery still had the same problem of immediately closing. However, I wiped the cache via adb and now it works.
In bootloader->recovery, conncect your phone to pc, use this command line "fastboot erase cache" under a folder which contains fastboot.exe and related stuff. This will fix the problem.
Sent from my HTC One using xda app-developers app
yhd4711499 said:
In bootloader->recovery, conncect your phone to pc, use this command line "fastboot erase cache" under a folder which contains fastboot.exe and related stuff. This will fix the problem.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks this resolved my issue
Good job man thanks saved my day. This fixed my bootloop and restarts thankssssssss
I had installed the google edition from trickdroid and I had an issue with com.android.phone stopped every 5 seconds. I tried to go back to stock rom from my twrp backup. Now my phone shows HTC and shuts off. I have tried holding down the power button for about 5 minutes. nothing happened. I tried the volume up and power button. That worked once but now I can't get it to work again. I get no power led or anything. I just want to get into fastboot/recovery.
Its Volume DOWN and power button to get into bootloader.
Before restoring your nandroid, did u do a wipe in recovery? And/or the command fastboot erase cache in fastboot mode?
Sent from my HTC One using xda premium
I have heard TWRP was having issues with flashing nandroids and I'm reading about a constant slew of bootlooping ect.. or was this fixed with 2.5.5.0?
Sent from my HTC One using xda app-developers app
Did you wipe from trickdroid to ge? And so no response now?
hardstuffmuc said:
Its Volume DOWN and power button to get into bootloader.
Before restoring your nandroid, did u do a wipe in recovery? And/or the command fastboot erase cache in fastboot mode?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Hi sorry to but in but does erase cache in fastboot do the same as clear cache in recovery?
Btw running the gpe rom no problems, was just curious, this is the first htc I've owned so new to the whole fastboot/bootloader thing.
Also think your right op is Def a dirty flash
I had erased the device factory reset, erased the cache and installed from twrp 2.5.5.
The phone finally died and when I plugged it back in I finally got some sort of action. I was able to get back into recovery and go to cm. Booted into that and tried ge again and it worked.
Sent from my HTC One using xda app-developers app
When you look around the q&a sections it is obvious that users jump very fast into rooting and flashing without being completely familiar with the process.
Flashing recovery in fastboot should be done after pointing to the fastboot folder:
fastboot erase cache
fastboot flash recovery name-of-recovery.img
fastboot erase cache
Then, after booted into recovery when flashing rom.zip of different custom roms but on same base, another cache wipe/dalvik cache wipe before installing the .zip, and also a factory wipe plus cache/dalvik cache wipe when switching base ( cm to sense, 2.17.... to 2.19 ect or when advised by dev).
Sometimes after installing a bootloop happens, first power off and boot up again, if no success another wipe followed by another install of the .zip
OTG cable always comes in handy with a USB storage stick for a sideload.
Fact is, our One is a very moody device
Bootloops do happen, to have adb/fastboot being recognised sometimes several tries to connect to computer is necessary, using different usb ports.
I haven't had any problems and flashing RUUs I think is not really necessary unless returning phone for repair ect.
Sent from my HTC One using xda premium
Hi, i'm really desperate...
I have a HTC One rooted and S-0FF with latest firmware
In the afternoon i tried no flash a new rom (android revoluton HD) and then it started to bootloop, i tried to get into recovery mode (cwm) and again it reboorts and gent in bootloop, i tried accesing the adb and nothing, my devices not shows when using command "adb devices"
I have Windows 8 64-bit and lastest htc drivers installed
Please Help
i don't think recovery would get into a bootloop so you must be holding the wrong buttons (should be power + vol down to get into the bootloader). from there select the recovery option and it should enter.
you might need to wipe the dalvik cache or reflash the rom.
So you have a bootloop and you can't enter fastboot. I know exactly what you're talking about, It has happened to me twice. I think all I did was keep trying to hold down the Volume Down and Power buttons and at some point it got into the bootloader. I don't know why it happens but if I can say anything, it's that android devices can be extremely weird. Just keep holding the buttons. It's not such a big deal, if your screen shows something (splash or boot animation) then you're far from very extreme issues.
If you have S-OFF, the world is your oyster! Look in a few guides/threads how to recover.
The reason you have a boot loop is because you need twrp recovery to flash android revolution
Sent from my HTC One using XDA Premium 4 mobile app
Find the solution
Yep! after the adb command "show devices" didn't work, i started to search in the forums and i see one about a command with something like "asb getvar" kind a thing. That command works and show my HTC one information that appear in top of the bootloader screen, then i flashed TWRP and send Android Revolution HD by sideload, then install and everything works again.
The only drwback is that my sd card got completely wiped
Thank you for your replies guys :good:
That's why I always have a backup of my ad card on my pc just in case
Glad you got it working though!
Sent from my HTC One using XDA Premium 4 mobile app
I left my phone charging overnight. Woke up, and saw that my XT1063 was stuck on the Unlocked Bootloader screen.
1. Tried to do a Factory reset from the fastboot screen and it went back to the same white screen.
2. Went into recovery and I see this message at the bottom of the screen
http://postimg.org/image/u8zi9d5ud
3. I have tried to format the cache/dalvik cache. Nothing has changed. I used fastboot and booted into TWRP and get this result.
http://postimg.org/image/5emdm1rij
4. Tried format/wipe cache from fastboot. Nothing changes. Tried flashing other versions of TWRP and Phil's CWM, stock recovery remains.
Is there anything that can be done? I'd like some help really as I've only has 3 months with this phone. I'm willing to do anything right now
There's nothing I can do?
I'm assuming nothing can be done...
I m by no means a professional, but it looks like some of your partitions are corrupt. If there is any way to flash the stock ROM, do that. But failing that, I'm really not sure what to do.Maybe do a search on google to see if others have fixed it on other devices, then try the same?
xN1ghtShadoWx said:
I m by no means a professional, but it looks like some of your partitions are corrupt. If there is any way to flash the stock ROM, do that. But failing that, I'm really not sure what to do.Maybe do a search on google to see if others have fixed it on other devices, then try the same?
Click to expand...
Click to collapse
I've searched and tried those methods. for one, I can;t use ADB. Is there any way to format the cache partitions? When I try to do a wipe function from stock recovery, it gives back the same message.
So I have a useless moto g :crying:
In would just do the following command in fastboot:
"fastboot erase cache"
If this doesn't work, I'm really not sure
Sent from my Nexus 7 using XDA Free mobile app
Tried that too :'( oh man...
So if you try that, does it give you an error message or does it just not work? If this is the case, you may be dealing with a bricked phone ?
Sent from my Nexus 7 using XDA Free mobile app
xN1ghtShadoWx said:
So if you try that, does it give you an error message or does it just not work? If this is the case, you may be dealing with a bricked phone
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
This is what i get -
http://postimg.org/image/3q9zqob4x/