Try to enter recovery mode, get warning triangle - Nexus One Q&A, Help & Troubleshooting

I've followed up to step 3 of part III on http://theunlockr.com/2010/01/08/how-to-load-a-custom-rom-on-the-nexus-one/
When I select recovery, it shows me the n1 logo with the unlock symbol below it, then it goes to a green android with a warning triangle.
The video shows a recovery screen, and volume up + power doesn't give me the menu with the correct options.
I've tried it plugged in and not.

You didn't flash the recovery correctly, that is the stock recovery screen.

Thanks, that helped.
Well anyway, I downloaded cyanogen from here: http://theunlockr.com/downloads/android-downloads/android-roms/nexus-one-roms/
and when it booted up it kept giving me "x application failed, force close" for pretty much everything, and no matter how many times I hit force close, the messages kept coming.
So I'm trying to recover to stock for now, as I need my phone for tomorrow, and I forgot what my serial/key/build was. Is there anyway of finding that out so I know which ROM to flash?

XSafire said:
I've followed up to step 3 of part III on http://theunlockr.com/2010/01/08/how-to-load-a-custom-rom-on-the-nexus-one/
When I select recovery, it shows me the n1 logo with the unlock symbol below it, then it goes to a green android with a warning triangle.
The video shows a recovery screen, and volume up + power doesn't give me the menu with the correct options.
I've tried it plugged in and not.
Click to expand...
Click to collapse
Did you remove the two scripts like you were told? /system/etc/install-recovery.sh and /system/recovery-from-boot.p

XSafire said:
Thanks, that helped.
Well anyway, I downloaded cyanogen from here: http://theunlockr.com/downloads/android-downloads/android-roms/nexus-one-roms/
and when it booted up it kept giving me "x application failed, force close" for pretty much everything, and no matter how many times I hit force close, the messages kept coming.
So I'm trying to recover to stock for now, as I need my phone for tomorrow, and I forgot what my serial/key/build was. Is there anyway of finding that out so I know which ROM to flash?
Click to expand...
Click to collapse
Wipe /data and /cache in recovery before reinstalling the custom rom should address the force close issues.

Related

[Q] Soft-Bricked G1

So I purchased a used G1 and I knew it has some software issues. I have no idea what version OS or anything is on this phone. Issue is it will not boot up into the OS. After researching (I am new to android) I have found what it can and what I cant get it to do. I can get into recovery mode no problem and after an ALT-L I see "Android System Recovery <2e>". The phone usually boots into this mode straight away, or I can hold home+power and it will enter the mode. Tried doing a "wipe data/factory reset" but nothing changes. If I reboot the phone and hold "back" I would expect it to enter Fastboot mode where I could do stuff. Instead I see the "rainbow screen" very briefly and then a message saying that if I want to restore factory setttings press send, otherwise hit any other key to cancel. No matter what I press nothing happens and I have to pull battery. I can only get into this mode every now and then. It seems pretty finicky about getting into it, and again no options when I do. Finally the camera+power to get into the bootloader does nothing. I can get the PC to see the phone when in recovery mode. It showed up as a mass storage device and i got that changed over to "Android Phone" by installing the SDK drivers.
Is there anything I can do on the recovery screen? That is the only thing that consistently works. I have tried a few update.zip files (various OTA updates I downloaded) but I either get a "No signature" error or it starts installing and then immediately get an "Installation aborted".
Any help to get this up and running would be appreciated. Hopefully its not just useless. For now an OEM 1.5 build is really all a i need. I can worry about updating/rooting later.
Download dream.nbh and format your sd card then place the dream onto ur sd card reboot holding home+cam button and let it do its magic that's how I fixed mine I'm sure if you go to the htc site you will find all the files u need just do a bit more research before trying this
Sent from my HTC Magic/Dream using XDA App
I mentioned in my original post that the camera+power button to enter bootloader mode does not do anything. I have already researched solutions, but it only seems I have access to the recovery mode screen. What can be done from there to assist with this issue (if anything)?
Download and flash the files from here http://developer.htc.com/adp.html (ota radio and system image) rename them update and flash them one at a time
Sent from my HTC Magic/Dream using XDA App
As for the no sig error just do some reasarch on adb shell and flash clockworkmod recovery from there its easy once u do some searching.....dw a couple of weeks ago I was you lol it'll pan out ok the people round here are really helpful
Sent from my HTC Magic/Dream using XDA App
Does this require adb? I have not been successful in making my pc get an adb connection. When in recovery mode the phones shows up on my pc and I got it to show up as android, but "adb devices" does not show anything listed. Everything referencing adb says it needs USB Debugging enabled, but I cant do that I cant get into the OS to enable. I dont seem to be able to enter fastboot mode either (see original post).
Download the radio and recovery image format sd card rename the ota radio update.zip boot into recovery and select apply update from sd card one you have that done delete the update.zip and then place the recovery image on sd card but rename update.zip and do the same....should work for ya
Sent from my HTC Magic/Dream using XDA App
When trying to update the radio files (tried all 3 versions on the download page) I get the "E: No signature (5 files)" error. Can I generate a valid signature for the files?
its worth a try lol if that dont work then i really dont know whats wrong lol
So far I have tried the following files:
The following pass verification and I get to the "Installing update..." but I then instantly get an "Installation Aborted". No other error message as to why:
signed-kila-CRC1-from-CRB43-FIX.7ca4a1d7.zip
signed-kila-DRC83-from-CRC1.c41b93c1.zip
signed-kila-ota-148830.de6a94ca.zip
signed-PLAT-RC33-from-RC30.zip
signed-RC30-from-RC29-fat.1582cace.zip
The following I get a "No Signature" error:
signed-dream_gfh-ota-147201.6d1386de.zip
ota-radio-2_22_19_26I.zip
ota-radio-1_22_12_29.zip
ota-radio-1_22_14_11.zip
I did a Wipe data and Cache before each update.zip attempt and this was using the "Android system recovery <2e>" screen.
Ideas? I will look and see if I can add a signature to the radio files.
dont spose u flashed the recovery with clockworkmod recovery 2.5.0.7
too short
I have not been successful flashing anything to the phone so far. All this was done via the "Android system recovery <2e>".
I signed the radio files myself, but they came out identical and same issues occurred. No idea what the "No signature" error is. Seems like a bunch of people get it on the forums, but no solutions. No idea why the good updates suddenly abort.
forum.xda-developers.com/showpost.php?p=4647751&postcount=1
Unfortunatly that seems to require fastboot, adp, or a rooted phone. I tried installing another SPL and I keep getting the "No Signature" error.
wow man your having a tough ass time lol ill keep researching for ya
i think your home button maybe stuck lol
far to short
You know thats not a bad idea. It does actually boot into recovery mode without holding the home button like you are meant to. Would holding home when powering on prevent the boot loader from starting if I hold the camera button?
on my g1 if i hold home power and cam buttons i get the bootloader/fastboot menu
So I ordered a new battery for it today too. The phone does not seem to work too long without being plugged in. Maybe that will help.
I also managed to capture some pictures of the screens I have, so maybe that will assist people with diagnosing the issue.
The first is the rainbow screen I get when holding back on a reboot. It flashes for 1 second or so and then displays the white screen with blue text. The last pic is the recovery menu I have access to.
It looks like this is a fully stock phone, no flashes. I am going to keep trying to get into that bootloader screen. Getting into the rainbow screen works once every 20 tries or so. Maybe the bootloader is similar. Hitting send on the white screen does nothing and requires a battery pull to reset phone.
how long can you stay in the coloured menu for ?????? also what happens if you stay there like what options do you get???

G1 will not recover ??

I have G1 sitting around that I never messed with until last night, so if it's bricked, it's not a big deal. The phone will turn on, and loop through the splash screen. The only way it will boot is in safe mode. When trying to do ANYTHING in safe mode (aside from power down), everything will FC. If i go into the recovery menu with the Home plus End key sequence, I get the "can't open cache recovery command". I've tried to install RC33 in that screen, and get "installation interrupted".
The phone was given to me, so I really don't know if it was rooted or what was on it before. I do remember it worked, and just one day stopped working. When it was working I never saw a superuser icon or any other apps you usually see with a root. Thanks in advance for any help.
No one? Is there just a full update I can throw on the SD card and get it running?
Try formatting the sd card fat32, putting dreaimg.nbh(search) on it. Then, put it in the phone and boot with camera+power. Follow the onscreen instructions, and hopefully it'll work.
If it doesn't, not my fault. Good luck!
Thanks Michael, but I did that already and it really didnt change anything. I noticed the recovery menu looks a bit different, and when I go to safemode, the "android" looks different, but thats it. Still cant boot, and still shows there is no recovery in the recovery menu.

[q] need help! Black screen on my verizon galaxy tab 7

I tried a flash and think i messed my tab...now its just a black screen with a faint light in the background like its on but its no images.......my battery icon pops up then distorts away and thats it ....can get into download mode but not recovery.....tried holding all 3 buttons got this lil android dude in the corner with a sign sayin something about power reset but cant select nothing......help me please......
Put it in d/l mode and flash one of the stock roms with Heimdall.
D
i tried a stock flash with heimdall it flashed successfully but i still get the SAMSUNG logo that flashes and go away,buttons light up at the bottom,can go in download mode but not reboot mode,phone stay on with a faint light ,so i assume that its on somehow.....help
Did you follow this exactly?
http://forum.xda-developers.com/showthread.php?t=967175
One thing I missed here before was to wipe data and cache. Otherwise I go into boot loop.
how to get recovery mode
i cant wipe nothing because i cant get to recovery,just download mode
done it step by step
i followed evrything it flashed successfully but when it rebooted i turned off.and tried recovery but nothing......
chubbyflood said:
i followed evrything it flashed successfully but when it rebooted i turned off.and tried recovery but nothing......
Click to expand...
Click to collapse
Use UnBrickable Mod
http://forum.xda-developers.com/showthread.php?t=1341753
Although you get a black screen on boot, it might still be working....
Chubbyflood,
If you are in the same situation as I am then the tab is still working, you are just getting black screen on boot up. It played tricks on me for ages when I was first rooting by tablet; but it turned out it is just the boot up screen that isn't showing.
This is my situation:
-Press and hold Power button to turn on.
-I see the Galaxy Tab / Samsung initial boot image for about 1 second, and also hear the "boot chime"
-Then the screen goes completely blank (but you can tell it is still on with a little light showing.
-The four "hard button" lights will light up briefly a couple times
-Wait approximately 30 seconds to a minute (to be safe and give the tablet time to boot up - it is actually booting up)
-Tab the Power button once, to turn the tablet off (now the screen is clearly off)
-Tab the Power button again, and the tablet will be up and running as normal.
I am guessing the boot animation / images are failing in some way, but the tablet is booting up as normal.
I've just learned to live with it, because I haven't had a chance to figure out what's going on, but it honestly took me a good hour or so, and a few (unnecessary) flashes, before I realized the thing was up and running fine, it just need to have the button pressed on and off.
One final thing to mention; don't have the tablet plugged into anything. I seem to remember leaving it plugged into the PC didn't help (I think).
Hope that makes sense.
Cheers
Ed.
Has your situation been resolved?
I am in the same boat. What I have done to temporarily fix this was to Flash a ROM that uses Hemdall and it will boot as flukebu stated but only with the Galaxy Cubed ROM.
I cannot get the factory files to boot as you have stated.
I have continually tried to return to stock using the files provided on this forum and all "unbrick" posts.
While flashing the stock images everything completes and works well. The device reboots and the Samsung Splash screen appears. Once it appears it disappears and scrambles the screen. I believe it then goes into a bootloop which easily enough I could access factory recovery to correct but when I do attempt to access factory recovery the screen is as posted above (black but illuminated).
Once I flashed Galaxy Cubed ROM and it booted I hit the power button and the locksreen appeared. I can tell you I was excited but there are some issues with that ROM I have not tried to correct yet because my main goal is to return to stock.
Even with this ROM working correctly I have attempted to access CWM once installed to complete a Data Wipe and that does not show up either.
I would really like to find a solution to this I want to return to stock and not have this custom ROM running.
Juiced_RL said:
Has your situation been resolved?
I am in the same boat. What I have done to temporarily fix this was to Flash a ROM that uses Hemdall and it will boot as flukebu stated but only with the Galaxy Cubed ROM.
I cannot get the factory files to boot as you have stated.
I have continually tried to return to stock using the files provided on this forum and all "unbrick" posts.
While flashing the stock images everything completes and works well. The device reboots and the Samsung Splash screen appears. Once it appears it disappears and scrambles the screen. I believe it then goes into a bootloop which easily enough I could access factory recovery to correct but when I do attempt to access factory recovery the screen is as posted above (black but illuminated).
Once I flashed Galaxy Cubed ROM and it booted I hit the power button and the locksreen appeared. I can tell you I was excited but there are some issues with that ROM I have not tried to correct yet because my main goal is to return to stock.
Even with this ROM working correctly I have attempted to access CWM once installed to complete a Data Wipe and that does not show up either.
I would really like to find a solution to this I want to return to stock and not have this custom ROM running.
Click to expand...
Click to collapse
Have you found a resolution to this? Mine tab is doing the exact same thing as yours after the cubed rom.

[Q] Boot problem. Cannot access recovery. milestone

Well, short summary : Cyanogenmod 6.3.6 for milestone(milaq)
​Androidiani Milestone Openrecovery (based on the Openrecovery by Skrilax_CZ by 89luca89 and Azhad)
Everything was smooth and good. But sometimes I would run into some low memory situations. The recovery menu had some memhack
options. I tried them. This is when trouble started.
Current symptoms :
Phone switches on and does not go past the Motorola M logo. It just stays there. Only way to switch off is to pull battery
Cannot load into recovery. I see a yellow exclamation mark with a small phone icon. And it just stays there. Not the box with an arrow pouring into a phone.
Can load into bootloader. Gets recognized in RSD lite. Can reflash vulnerable recovery upto the point that it needs a restart. It cant restart so it asks me to manually restart which i cannot do.
What should be done? . I've gone through all threads thatt seemed relavent. It always calls to reflash the vulnerable recovery, which I can do but cannot reboot
Thank you in advance.
I hope I'm wrong, but I guess your phone is hardbricked.
Maybe someone with greater knowledge could help you.
(Try to ask around on the #milestone-modding IRC channel)
Erovia said:
I hope I'm wrong, but I guess your phone is hardbricked.
Maybe someone with greater knowledge could help you.
(Try to ask around on the #milestone-modding IRC channel)
Click to expand...
Click to collapse
Thank you for your reply. I really hope it isn't hardbricked, I only tried some settings from the recovery menu.
How does the IRC channel work?
I just describe my problem in the common are or do i ask someone specific?
I see in the irc-log you already found it. I hope your problem will be solved.
if nothing will help flash a full sbf firmware with rsd lite....
all data and settings gone, but i think your device will boot again
Erovia said:
I see in the irc-log you already found it. I hope your problem will be solved.
Click to expand...
Click to collapse
Thank you very much. You directed me in the right direction. My phone is ficed and running fine now. I'd like to post the problem and the solution here.
Problem : Phone will not boot past M logo. Phone will load into bootloader. Attempts to get to recovery will result in phone stuck at yellow exclamation mark with phone icon, not the typical arrow pouring out of box into phone icon. Phone will not charge.
Solution : In a general scenario, to get to recovery hold 'x' and power up, keeping it pressed until yellow exclamation mark with phone icon comes up. Then press volume up and then press camera key. This will get you to standard android recovery. I use androidiani-openrecovery so I apply the relevent update and load openrecovery. Then you wipe date, wipe cache, wipe dalvik. Then apply cyanogenmod update. And reboot. Softbrick solved.
Now, I was unable to get past the yellow exclamation and phone icon. Pressing volume up and camera button did nothing. I wouldn't budge. Turns out, when I replaced the digitizer on my phone, I placed the camera button upside down. So the camera button would click but would not half click(for focussing). Apparently recovery is loaded when volume up is held down and the camera button is half pressed. Turned the camera button over and voila! recovery. What followed is in the previous paragraph.​
So that's how to deal with a softbrick. A bazillion thanks and much respect to nadlabak.
-FuFu- said:
if nothing will help flash a full sbf firmware with rsd lite....
all data and settings gone, but i think your device will boot again
Click to expand...
Click to collapse
That makes sense. That would work I guess
I haven't tried that though as the problem was fixed, described in my last post.
I presume the procedure to flashing a full sbf firmware is the same as the vulnerable_recovery.
PS: Thank you for your great work on the OR minimod :good:
i try my best to add some nice features to OR
and i rescue some devices by flashing a full sbf, if something going wrong when i test something and if it dont pass the M Logo i just reflash 2.2.1 and try again

Captivate gets stuck with black screen after booting. No response to anything

Phone: Samsung Captivate I-896, with AT&T stock Android 2.2 flashed to it. Rooted and unlocked.
Action: Deleted some *.odex files from Root/Data/App, following a guide to get around the "out of space" message while trying to install software. Cleared Delviks cache directory.
Problem: First restart after above actions(which didn't resolve the out of space message issue), phone shows start-up animations, gets stuck with black screen. Left like this overnight, nothing happens. Vibrates every 50 seconds or so. Respons to hardware Vol+ press with the home/back/menu backlight. Otherwise, no response to anything, black screen(backlight on). Does not receive phone calls. I do not know for sure if the action listed above is the one that caused this situation, but I assume so since it was the last action taken before the issue appeared.
Solutions attempted: Tried every possible permutation/combination of buttons/usb cable/etc/ restarts etc. listed here: http://forum.xda-developers.com/showthread.php?t=858765&page=1, except Jig. The phone would not go into recovery or DL mode.
Question.
Am I correct in assuming that forcing the phone into recovery mode and reflashing a new system(or reflashing the old one) is the only way to get the phone to work again?
There is no way to "soft-reset" the phone, with all settings reverted back to stock, if it does not boot up completely?
Titerepayaso said:
Phone: Samsung Captivate I-896, with AT&T stock Android 2.2 flashed to it. Rooted and unlocked.
Action: Deleted some *.odex files from Root/Data/App, following a guide to get around the "out of space" message while trying to install software. Cleared Delviks cache directory.
Problem: First restart after above actions(which didn't resolve the out of space message issue), phone shows start-up animations, gets stuck with black screen. Left like this overnight, nothing happens. Vibrates every 50 seconds or so. Respons to hardware Vol+ press with the home/back/menu backlight. Otherwise, no response to anything, black screen(backlight on). Does not receive phone calls. I do not know for sure if the action listed above is the one that caused this situation, but I assume so since it was the last action taken before the issue appeared.
Solutions attempted: Tried every possible permutation/combination of buttons/usb cable/etc/ restarts etc. listed here: http://forum.xda-developers.com/showthread.php?t=858765&page=1, except Jig. The phone would not go into recovery or DL mode.
Question.
Am I correct in assuming that forcing the phone into recovery mode and reflashing a new system(or reflashing the old one) is the only way to get the phone to work again?
There is no way to "soft-reset" the phone, with all settings reverted back to stock, if it does not boot up completely?
Click to expand...
Click to collapse
Sounds pretty accurate. You'll have to get a jig to get in download mode, flash stock Odin KK4 to fix w/e happened during your testing.
Thanks Bwolf. I just tried ADB console on a different computer and it connects to the device just fine in spite of black screen. I guess I had one thing right, USB DEBUGGING enabled before this whole deal.
Question: is there any way I can restore the phone using the console without wiping everything?
Titerepayaso said:
Thanks Bwolf. I just tried ADB console on a different computer and it connects to the device just fine in spite of black screen. I guess I had one thing right, USB DEBUGGING enabled before this whole deal.
Question: is there any way I can restore the phone using the console without wiping everything?
Click to expand...
Click to collapse
Make a backup with ADB.
Once that's done, push download mode with it and get Odin KK4 (without bootloaders). You'll have to start from there to fix w/e went wrong.
You don't have to wipe your sd doing so but you will lose your apps and such. If you backed up your phone with your Play Store account, it will re-download your apps as you're done booting up.
To get back up where you were, grab Corn Kernel, flash it with Odin 1.87 and then follow the full instructions of the ROM you wanna use.

Categories

Resources