So I'm trying to flash my Nexus One to Cyanogen 6.0 and I followed the steps very carefully. I dragged the rom and Google addon onto my SDcard, turned off my phone and loaded bootloader (track ball+ power button), waited and selected Bootloader, then Recovery.
A couple of seconds later, my phone was on the original Nexus One logo screen, and then all the sudden there's a caution sign (!) in a yellow triangle with a little green android robot right beside it. I waited it out (5 minutes) and nothing happened, so I took my battery out of my phone to restart it.
After that, I decided to upgrade to Froyo through my phone. I clicked "Install Now", and it said that it will be installed and needed to restart my phone. It rebooted, went to the Nexus One logo, and then the same caution symbol with the little green android logo popped up again and it froze. Once again, I had to take the battery out.
Does anybody know the cause of this?
stewroids said:
So I'm trying to flash my Nexus One to Cyanogen 6.0 and I followed the steps very carefully. I dragged the rom and Google addon onto my SDcard, turned off my phone and loaded bootloader (track ball+ power button), waited and selected Bootloader, then Recovery.
A couple of seconds later, my phone was on the original Nexus One logo screen, and then all the sudden there's a caution sign (!) in a yellow triangle with a little green android robot right beside it. I waited it out (5 minutes) and nothing happened, so I took my battery out of my phone to restart it.
After that, I decided to upgrade to Froyo through my phone. I clicked "Install Now", and it said that it will be installed and needed to restart my phone. It rebooted, went to the Nexus One logo, and then the same caution symbol with the little green android logo popped up again and it froze. Once again, I had to take the battery out.
Does anybody know the cause of this?
Click to expand...
Click to collapse
You soft-bricked your phone. You didn't follow the steps completely right I'm guessing. This is repairable, reflash a stock rom, reroot your N1, then try the steps again.
Thank you for the reply.
Could you re-direct me to a link on the proper way to unroot, and flash a rom? I remember I ran into a problem with Windows 7 not reading my Nexus One which really messed something up during the process.
Related
In December of last year, I had my friend root and install CyanogenMod onto my Mytouch 3G Slide. Everything was working fine until I wanted to update my ROM and tried to boot my phone into recovery mode to make a NANDroid backup. A screen with a picture of a phone and a red exclamation point inside a triangle would appear, and I'd have to pull the battery out to restart the phone.
Then, I tried to access the bootloader by holding the volume down and power buttons. After some loading, it asked me if I wanted to update. Not knowing what it was asking, I said no, and tried to access the actual recovery menu, but the same screen showed up.
I tried again, this time accepting the update. Now, when my phone boots, the stock mytouch splash screen appears and the phone does nothing from there.
At this point, what would be the best solution? Is my phone just bricked, or is there a way to restore it to the stock firmware/recover CyanogenMod?
EDIT: For clarification, I can still access the bootloader, where I have four options: Fastboot, Recovery (See problem above), Clear Storage, and Simlock.
EDIT 2: I left it on the splash screen and discovered that it seems to have just thrown my phone into a stock factory state, running 2.1-update 1. Not sure if it's still rooted.
I have a USCC Mesmerize (Galaxy S). Today I followed instructions on how to root my phone from androidadvices(dot)com
I got to this step:
That’s it as soon as you click on the Start option, you will see that the device will be rooted successfully within 10 minutes of clicking on the Start and also after the process is finished, the device will be rebooting and also the Clock work mod recovery tool too will be inducted in your Galaxy S
It took about 10 seconds until it said PASS, then my phone restarted. The phone shows the Samsung logo and then bright colors flash on the screen. About 5 seconds later the phone restarts doing the same thing.
I went out and downloaded the stock one and tried this. The process took a few minutes which seemed promising but the phone does the same thing. The colors are lighter this time around but the phone still doesn't boot.
Am I missing something?
Phone version was 2.3.4
My Nexus 5 seems to get stuck at the update screen (the standing green android with the spinning polyhedron) after flashing to stock(+unroot) with softbrick/bootloop checked. The flash completed without error. I've left it at this screen for over an hour and not only does it not progress it doesn't even get to the progress bar at the bottom.
This afternoon my (unrooted, bootlocked, stock) N5 turned itself off 3 times while on the charger. Powered back on and then would find it turned off 20 or so minutes later when I checked it again. After the third time it booted to the "Google" screen and would go no further. I tried a hard reset but it gave an error. So I plugged it into my laptop and fired up Wug's NRT, unlocked the bootloader (at which point it got stuck at the same update screen described above for around an hour). I held power till it went off, booted back into bootloader (which showed as unlocked) and performed the flash to stock(+unroot) with softbrick/bootloop checked and ended up at the update animation again. Any thoughts other than RMA?
****Edit: Finally got the phone to boot after fastboot booting twrp. Was able to to wipe the phone (after multiple attemps blocked by can not mount storage/cache/etc/etc errors). Flashed 4.4 and the phone now boots to android BUT radio is non-functional (no signal despite being in my normal coverage area), any attempt to add an APN causes a hard reboot (had to go through all the setup screens again). Additionally, the phone won't turn off, even hard power downs (holding the button for 30 secs) lead to an immediate reboot. Still RMAing but I was able to relock the bootloader.
You really shouldn't RMA a phone after messing it up yourself by using a toolkit when you didn't know what you were doing.
Flash the factory images manually. That should get your phone up and running again.
Chromium_ said:
You really shouldn't RMA a phone after messing it up yourself by using a toolkit when you didn't know what you were doing.
Flash the factory images manually. That should get your phone up and running again.
Click to expand...
Click to collapse
Performed a manual flash with the exact same results. There is apparently something wrong with the hardware (which may explain why it was turning itself off and then wouldn't boot past the google logo.
gallahad2000 said:
Performed a manual flash with the exact same results. There is apparently something wrong with the hardware (which may explain why it was turning itself off and then wouldn't boot past the google logo.
Click to expand...
Click to collapse
Yep, I would agree.
I have a rooted Verizon Wireless Galaxy S3, for reference. So today I decided to attempt to install Cyanogenmod and searched for something to install it on my phone. I found Rom Manager on the Play Store and installed it, and went into it. I installed Clockworkmod and flashed it, and everything went reasonably well until I rebooted my phone. At this point, it automatically booted into Recovery Mode, or at least tried to. What it really did was display the screen with the Samsung logo and "RECOVERY BOOTING....." at the top in blue letters. Then, it shows a screen with a yellow warning triangle, which gave me the "System Software not authorized by Verizon Wireless has been found on your phone" message, saying "SECURE FAIL:KERNEL" at the top. Now, after a bit of searching, I had found that I should flash a factory image, so I connected my phone to my computer, and that's when the strange stuff began. First, my phone started vibrating approximately once every second for a short amount of time(about 0.1 second) and my computer wasn't detecting it. When I tried to turn my phone on, it just displayed the normal first boot screen and then nothing else happened, and it went back to a black screen.
I've looked all over the place, but I can't find anyone that has encountered my problems and I have no idea how to proceed.
somesortofthing said:
I have a rooted Verizon Wireless Galaxy S3, for reference. So today I decided to attempt to install Cyanogenmod and searched for something to install it on my phone. I found Rom Manager on the Play Store and installed it, and went into it. I installed Clockworkmod and flashed it, and everything went reasonably well until I rebooted my phone. At this point, it automatically booted into Recovery Mode, or at least tried to. What it really did was display the screen with the Samsung logo and "RECOVERY BOOTING....." at the top in blue letters. Then, it shows a screen with a yellow warning triangle, which gave me the "System Software not authorized by Verizon Wireless has been found on your phone" message, saying "SECURE FAIL:KERNEL" at the top. Now, after a bit of searching, I had found that I should flash a factory image, so I connected my phone to my computer, and that's when the strange stuff began. First, my phone started vibrating approximately once every second for a short amount of time(about 0.1 second) and my computer wasn't detecting it. When I tried to turn my phone on, it just displayed the normal first boot screen and then nothing else happened, and it went back to a black screen.
I've looked all over the place, but I can't find anyone that has encountered my problems and I have no idea how to proceed.
Click to expand...
Click to collapse
Were you on either of the locked bootloaders of 4.3 or 4.4.2? If so your issues lies there to begin with. No custom recovery other than safestrap will work with the locked bootloaders. Your lucky you didn't hard brick it
From my Wicked S3 on SOKP
ShapesBlue said:
Were you on either of the locked bootloaders of 4.3 or 4.4.2? If so your issues lies there to begin with. No custom recovery other than safestrap will work with the locked bootloaders. Your lucky you didn't hard brick it
From my Wicked S3 on SOKP
Click to expand...
Click to collapse
Well, can I somehow get my phone into working order? Because it's as good as bricked right now.
Guys, I had my recovery flashed to stock again from TWRP, and was flashing the stock firmware with the help of this thread
http://forum.xda-developers.com/showpost.php?p=47820707&postcount=1
Now, I might have skipped to notice the following point in my impatience
Downgrading:
The 1st command "mfastboot flash partition gpt.bin" will fail on 4.4.2 to 4.3 downgrade. Skip this command if you are downgrading and continue with the other commands, which should work.
Click to expand...
Click to collapse
But still all went fine and I booted into my new stock firmware (4.3) and I got an OTA update for 4.4.4 and I downloaded it and went to install it. The device reboots, android starts its installation process and I left it there for it to finish.
Now starts the problem. I come to check the status of the updation process and the screen is off. I'm trying to turn on the phone and it just refuses to boot up. No LED notification light blinking, no white charging screen when connected to wall point charger. Just dead, just like that. The weird thing being, the battery charge was at 90%+ when it all started.
What should I do now. I tried vol down + power combo for 2 mins, just the power button for 2 mins and such combinations.
Help me out guys.
:crying::crying::crying:
joecizac said:
Guys, I had my recovery flashed to stock again from TWRP, and was flashing the stock firmware with the help of this thread
http://forum.xda-developers.com/showpost.php?p=47820707&postcount=1
Now, I might have skipped to notice the following point in my impatience
But still all went fine and I booted into my new stock firmware (4.3) and I got an OTA update for 4.4.4 and I downloaded it and went to install it. The device reboots, android starts its installation process and I left it there for it to finish.
Now starts the problem. I come to check the status of the updation process and the screen is off. I'm trying to turn on the phone and it just refuses to boot up. No LED notification light blinking, no white charging screen when connected to wall point charger. Just dead, just like that. The weird thing being, the battery charge was at 90%+ when it all started.
What should I do now. I tried vol down + power combo for 2 mins, just the power button for 2 mins and such combinations.
Help me out guys.
:crying::crying::crying:
Click to expand...
Click to collapse
Dude.. seems like your phone has been hardbricked!!!