Database Develop

N1 wont boot into bootloader! Instead goes to OS

Facts:
Ive searched the site multiple times, cannot find the same issue elsewhere
Ive unlocked my bootloader and rooted my N1, so I know how to access the bootloader/recovery
When I hold down the rollerball and hit power to start the N1, it boots straight to the OS, not the bootloader menu
The OS is: Android 2.2, Build FRF50, Kernel [email protected] #5
The OS doesnt show a cell signal
The OS has lines through moving graphics
The OS crashes to the X graphic with the moving colors about every 30sec to 2 minutes
I can access abd-mac commands via usb, but ./adb-mac reboot recovery just reboots my phone back to the OS again
I tried http://wiki.cyanogenmod.com/index.php/RE-recovery-img
but the last step of ./adb-mac shell flash_image recovery /sdcard/recovery.img
comes back with "error opening /sdcard/recovery.img: No such file or directory
Im sure the recovery.img is on the sd card
in the gui of the OS I tried looking at the available space of the sd, and it states sd- unavailable
available space - unavailable.
Any more ideas?

I can think of three options:
boot to fastboot by holding the trackball while turning on the phone (you say this doesn't work)
boot to bootloader by holding volume down while turning on the phone
if your OS is stable enough, try installing "Quick Boot" from the market (it requires root). That app has the option to reboot to either bootloader, or recovery

just follow this guide forum.xda-developers.com/showthread.php?t=636795 no such file is because you have to put the recovery image in the root folder of the sd card in other words it should'nt be within another folder when you open and view your sd card.

slicklynice said:
just follow this guide forum.xda-developers.com/showthread.php?t=636795 no such file is because you have to put the recovery image in the root folder of the sd card in other words it should'nt be within another folder when you open and view your sd card.
Click to expand...
Click to collapse
Thanks slickynice, but recovery.img is on the root of the sd card.

pikipirs said:
I can think of three options:
boot to fastboot by holding the trackball while turning on the phone (you say this doesn't work)
boot to bootloader by holding volume down while turning on the phone
if your OS is stable enough, try installing "Quick Boot" from the market (it requires root). That app has the option to reboot to either bootloader, or recovery
Click to expand...
Click to collapse
Thanks pikipirs. vol down while booting doesnt do anything for me either. I cant access anything with market. Is there a way to manually install the "quick boot" app with abd-mac?

Try something like rom manager or quickboot and see if they can get you into recovery?

MSigler said:
Try something like rom manager or quickboot and see if they can get you into recovery?
Click to expand...
Click to collapse
Do you know if any is accessible from the explorer because my market doesnt respond.

DrBlast33 said:
Do you know if any is accessible from the explorer because my market doesnt respond.
Click to expand...
Click to collapse
Hold on, I'll find the APK for the free clockworkmod rom manager.

Actually he hasn't posted an APK, why can't you get it from market again?

My OS isnt stable enough, I have no radio, so I connect via wifi. When I go to the market, it says Loading.... and then the OS crashes to the X graphic with flying colors.... and the market is closed again.

DrBlast33 said:
My OS isnt stable enough, I have no radio, so I connect via wifi. When I go to the market, it says Loading.... and then the OS crashes to the X graphic with flying colors.... and the market is closed again.
Click to expand...
Click to collapse
Does ADB work?

Yes, adb-mac command works, but ./adb-mac reboot recovery or ./adb-mac reboot bootloader doesnt boot into the recovery or bootloader, instead it just restarts the phone back to the OS.
Thats why if I can get something to install via adb, I can do it that way, and hopefully get it to the bootloader to install a working rom.

is it stable enough to try to run an app?

amazingly trivial suggestion here, but have you attempted to reset to factory defaults from inside the system? Perhaps this will give you just enough stability to accomplish a recovery load so you can get your phone back to a happy state.
Of course, I have no idea why that would resolve your issue but nobody has suggested it yet and your situation sorta sucks
Best of luck!!

Thanks for your suggestions. Yes, it freezes up when I try to do factory defaults again. But I did a factory default before I put the bad rom on it, so its pain without any apps currently. Some apps will work like the browser for a few minutes. Not many other apps to use, since it was wiped prior.

Well, looks like Im going to send it to HTC. They said it will be $196+ to fix it. They have to replace the main board which, if its the only issue, is $196. Ill be shipping it out tomorrow. Anyone with any last suggestions before I bite the bullet on $200? I guess it beats buying the phone again for $580!

Try volume down and power to boot?

MSigler said:
Try volume down and power to boot?
Click to expand...
Click to collapse
Tried it, just boots to the OS still.

Try safe mode? Turn it off, wait for the X and the unlock icon, then hold trackball until it boots. Should say "Safe mode" in the lower left corner. Might be able to get it running stable and fix from there.

MSigler said:
Try safe mode? Turn it off, wait for the X and the unlock icon, then hold trackball until it boots. Should say "Safe mode" in the lower left corner. Might be able to get it running stable and fix from there.
Click to expand...
Click to collapse
I am able to boot to safe mode.... but Im not sure what I can do while in it that I cant do while in the OS otherwise.

[Q] Help! - Need to restore phone! No rainbow screen

First off, I've read/tried using software from thread: http://forum.xda-developers.com/showthread.php?t=442480
I found the phone in the subway. when i power it up it goes to the default boot menu.
I don't know anything about the phone. Could be UK, US, AUS, PVT, or DVT.
I can't get to the rainbow screen (fastboot) found when pressing while device is off (holding camera + pwr button (end)). So i can't flash DREAIMG.nbh. (RC 29) assuming the phone is american.
I do get the default restore menu though. I press alt+L to get the menu. After if i try to flash anything it says that it doesn't pass verification.
So I need to know what file(s) I can flash from the default boot menu that can fix the phone that will pass verification.
Also forgot to mention when i am in the default boot menu and press alt+L, in yellow at the bottom phone displays following error message: "E: Can't open /cache/recovery/command"
Thanks...

Sorta sounds like someone used an app that kills the phone if they lose it or they knew it was bricked and just left it there.
is there any water damage to this phone at all?
why not try posting an ad on craigslist and see if anyone lost it ~.~

All water dmg indicators do not show they were wet at any time. Also how would i make sure i would be returning it back to the correct user? it was found with no SIM, can't even check for addtl' info.
Also if there was ever an app that would brick the phone when someone looses it, thats the first about me hearing it.
Anyone with some actual technical/dev input?

So i found some information at http://android-dls.com/wiki/index.php?title=OTA_Updates#RC28
When I go to install the update, it says thats its opening the package, then verifying the update, finally it trys to install the update and about 70% through it aborts.
Is there any kind of RUU i can use to completely reinstall the software up? If so where could i find it?
Any thoughts?

[GUIDE] [01/05/2011] Root your Incredible (AMOLED & SLCD Support!) + FAQ

Updated 01/05/2011
Support for both AMOLED & SLCD owners!
With the release of Unrevoked 3.31, DINC owners are now able to obtain root and S-OFF with the Nov OTA and it also supports recoveries for both AMOLED and SLCD users!
I have put together an extensive guide on how to get root for both AMOLED & SLCD users! Rooting is now even easier than ever.
The guide is available at http://jonsuh.com/2010/11/root-your-droid-incredible-how-to/
FAQ
Blank Recovery Screen Issue
For those of you coming across the issue of the blank/black recovery screen:
Do NOT boot straight into recovery with Volume Up+Power.
Boot into HBOOT FIRST with Volume Down+Power.
Then select RECOVERY from the HBOOT menu.
I rooted before the OTA and the OTA will not install
Read my article on how to Unroot your Droid Incredible at http://jonsuh.com/2011/01/unroot-your-droid-incredible/
Then read my article on how to root.

link doesnt work

I apologize; link is fixed and should be working now.

Looking to try this, but my SD card appears to be formatted to FAT16. How do I format it to FAT32?
Edit: Spoke too soon, got it. I'll post an update when once I'm done.

works perfectly took about 45 minutes
Sent from my ADR6300 using XDA App

papi92 said:
works perfectly took about 45 minutes
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
It is more time consuming but it does work! Glad to know u were able to get it to work. I think it was worth it. So much better having root back
Sent from my ADR6300 using XDA App

I'm already S-Off and rooted, running (mostly) stock. I skipped to step 5B, to update to the OTA update. However, when I attempt to apply update.zip, it fails during the "Verifying current system" step. The text is below:
assert failed: apply.patch.check("/system/app/Mail.apk", <insert two long non-matching hash values here>)
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Anyone run into this or have a clue?
Thanks.

danman7 said:
I'm already S-Off and rooted, running (mostly) stock. I skipped to step 5B, to update to the OTA update. However, when I attempt to apply update.zip, it fails during the "Verifying current system" step. The text is below:
assert failed: apply.patch.check("/system/app/Mail.apk", <insert two long non-matching hash values here>)
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Anyone run into this or have a clue?
Thanks.
Click to expand...
Click to collapse
Well truthfully, the OTA update doesn't do much but add more crapware. There isn't any other reports of the OTA being a significant update so you'd be safe to not even install the OTA. If you're annoyed with the reminder, if you've done all I've told you to, if you click "Install" it should just time out and not do anything and never remind you again.

Not Working For Me
This process does not appear to be working for me.
After doing all up to and including the "ADB" stuff and typing "reboot bootloader", my phone just boots to the bootloader and does nothing. I never get the prompt to process the update.
Where did I go wrong? I've tried this four times with the same results.

ozone777 said:
This process does not appear to be working for me.
After doing all up to and including the "ADB" stuff and typing "reboot bootloader", my phone just boots to the bootloader and does nothing. I never get the prompt to process the update.
Where did I go wrong? I've tried this four times with the same results.
Click to expand...
Click to collapse
Did you make sure you didn't rename the file something different? It should be "PB31IMG.zip" in the root of your SDCARD.
Also did you make sure your SDCARD was formatted to FAT32? and not FAT/FAT16?

UNREVOKED 3.22 HAS BEEN RELEASED.
Get your copy at www.unrevoked.com.
This thread will be changed within the next 24 hours to accommodate the new Unrevoked. No longer need to downgrade to root.

jsuh said:
Did you make sure you didn't rename the file something different? It should be "PB31IMG.zip" in the root of your SDCARD.
Also did you make sure your SDCARD was formatted to FAT32? and not FAT/FAT16?
Click to expand...
Click to collapse
No good.
I am running Windows 7 64-bit.
I formatted the removable sdcard to fat32 and the PB31IMG.zip file is named correctly.
I type in "./flash_image misc /sdcard/mtd0.img" and immediately get the "#" prompt after it confirms my entry.
I then type "reboot bootloader" and the phone goes to the bootloader and just sits there until I tell it to reboot.
Should I be doing all of this from the internal storage instead of the removable card?
New Info:
I just tried it again and this time instead of rebooting from the bootloader screen I selected "bootloader" and it checked the image and gave me the option to flash. I said "yes" and it is now loading the image.

ozone777 said:
No good.
I am running Windows 7 64-bit.
I formatted the removable sdcard to fat32 and the PB31IMG.zip file is named correctly.
I type in "./flash_image misc /sdcard/mtd0.img" and immediately get the "#" prompt after it confirms my entry.
I then type "reboot bootloader" and the phone goes to the bootloader and just sits there until I tell it to reboot.
Should I be doing all of this from the internal storage instead of the removable card?
Click to expand...
Click to collapse
Nope, you shouldn't, but no worries, the new Unrevoked version should be able to get you root without having to follow all my directions.
Just go to www.unrevoked.com/recovery then download and run the proper version.

Uh-Oh!
I think I just bricked the phone.
After saying yes to flashing the image, the phone went black and never woke up. now I can't turn it on although the soft buttons light up when I press the power button.
Is there any key combination that will get me to recovery or am I screwed?

Updated 12/2/2010
With the release of Unrevoked 3.22, I provided instructions for root for BOTH AMOLED & SLCD owners!
Enjoy
http://jonsuh.com/2010/11/root-your-droid-incredible-how-to

ozone777 said:
I think I just bricked the phone.
After saying yes to flashing the image, the phone went black and never woke up. now I can't turn it on although the soft buttons light up when I press the power button.
Is there any key combination that will get me to recovery or am I screwed?
Click to expand...
Click to collapse
Is there any way to get the phone back?

ozone777 said:
Is there any way to get the phone back?
Click to expand...
Click to collapse
You can try to hold volume down and the power button to get back into hboot. That may get you back to a workable position.
Hope that help...

g00gl3 said:
You can try to hold volume down and the power button to get back into hboot. That may get you back to a workable position.
Hope that help...
Click to expand...
Click to collapse
Already tried all the standard key combos with no success.
I thinks its time to stick a fork in it.
Time of death...3PM.
This doesn't mean I won't try again with the replacement Verizon sends out to me.
Gotta get back on the horse.

ozone777 said:
Already tried all the standard key combos with no success.
I thinks its time to stick a fork in it.
Time of death...3PM.
This doesn't mean I won't try again with the replacement Verizon sends out to me.
Gotta get back on the horse.
Click to expand...
Click to collapse
Pull the battery out put it back in and turn it back on (u said that it was an slcd?). U mentioned that the soft keys turn on right? Have u tried re running unrevoked with the new recovery mod for slcds? Look at my site for directions.
It may b that unrevoked would still recognize ur phone being plugged in and rerun the root process with the proper recovery.
Sent from my ADR6300 using XDA App

The 3.22 works great. The one thing I kept getting hung up on was after I installed the drivers by going into device manager etc etc was that windows was still asking me to install hardward drivers for usb device... so I followed along with windows and installed the driver again. Immediately after I installed the drivers for the second time unrevoked picked up my phone and started the process. It went all the way through and went to "done." (forgot to remove the PB31IMG.zip from trying to push the downgrade before - so it tried loading the update and failed...all I had to do was choose dont reboot, that brought me back to the hboot screen then unrevoked picked it back up).
The one problem I kept running into was that the new 3.22 unrevoked wouldnt pick my phone up even after I installed the drivers with device manager etc. So I tried a few different computers...still nothing and still asking me a second time to install the drivers. After I installed the drivers the second time everything was smooth from there.

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.

Massive problem with the tablet

I have spent about 10 hours sitting here, with over 200 tab open trying to find a solution to my problems but I could not find one. My last option is to post here and hope someone can help me out.
I recently bought the tf701t which came with Android 4.2.2. Everything worked fine. A few days ago, I got pushed an update to android 4.3 but it was .1.7 not .1.18 (the newest apparently). With that update, my problems came. When I light up the device by pressing the power button, the lock screen was unresponsive. I pressed my pin numbers in but there was no response and it was as if the touchscreen was broken. However, the home and back button were all working fine. I had to randomly keep pressing until it finally started becoming responsive. When I got in, the quick management window (the one you get by swiping down), kept popping up the moment i press the screen. Because of this, I couldnt do anything. I couldn't even turn off the tablet as the power off option was unable to be pressed by me (When i did press, the window came up again).
After a while, i managed to get around this by again randomly pressing stuff. I got really frustrated and decided maybe if I install a custom rom, this problem might be fixed.
I read around a bit and found that the CROMix rom required firmware 1.18, which I did not have. Because of this, i decided to try install 1.18. First i used the asus unlock tool. Next I tried booting into recovery but here I met my problem. I have guides telling me to first boot using power button + volume down key. This worked. It then told me to choose the RCK option and press the volume up key. This however, did not work. When I selected the RCK option, the android figure appeared lying down with a red triangle and exclamation mark over it.
Unsure of what to do in this situation, i read one of the guides on this forum which said simply place the 1.18 zip file (yes i unziped the zip file from the file i downloaded), in the root folder then reboot and it would automatically update. This didnt happen.
I then tried using the adb thing but it said no devices were connected even when my tf701t was connected to the PC. I guessed that I needed to be in the recovery mode that I could not get into, before it would work.
I then read around and they said I had to first get Rom manager + the CMR recovery thing but Rom Manager said it needed root access. In order to get root access, I needed to get into the recovery mode yet again.
So now I am stuck. Whenever I try the RCK option, the error pops up and I can't get any further.
WIll someone please help me? I have no idea what to do anymore except throw the tablet out.

zhuang281 said:
I have spent about 10 hours sitting here, with over 200 tab open trying to find a solution to my problems but I could not find one. My last option is to post here and hope someone can help me out.
I recently bought the tf701t which came with Android 4.2.2. Everything worked fine. A few days ago, I got pushed an update to android 4.3 but it was .1.7 not .1.18 (the newest apparently). With that update, my problems came. When I light up the device by pressing the power button, the lock screen was unresponsive. I pressed my pin numbers in but there was no response and it was as if the touchscreen was broken. However, the home and back button were all working fine. I had to randomly keep pressing until it finally started becoming responsive. When I got in, the quick management window (the one you get by swiping down), kept popping up the moment i press the screen. Because of this, I couldnt do anything. I couldn't even turn off the tablet as the power off option was unable to be pressed by me (When i did press, the window came up again).
After a while, i managed to get around this by again randomly pressing stuff. I got really frustrated and decided maybe if I install a custom rom, this problem might be fixed.
I read around a bit and found that the CROMix rom required firmware 1.18, which I did not have. Because of this, i decided to try install 1.18. First i used the asus unlock tool. Next I tried booting into recovery but here I met my problem. I have guides telling me to first boot using power button + volume down key. This worked. It then told me to choose the RCK option and press the volume up key. This however, did not work. When I selected the RCK option, the android figure appeared lying down with a red triangle and exclamation mark over it.
Unsure of what to do in this situation, i read one of the guides on this forum which said simply place the 1.18 zip file (yes i unziped the zip file from the file i downloaded), in the root folder then reboot and it would automatically update. This didnt happen.
I then tried using the adb thing but it said no devices were connected even when my tf701t was connected to the PC. I guessed that I needed to be in the recovery mode that I could not get into, before it would work.
I then read around and they said I had to first get Rom manager + the CMR recovery thing but Rom Manager said it needed root access. In order to get root access, I needed to get into the recovery mode yet again.
So now I am stuck. Whenever I try the RCK option, the error pops up and I can't get any further.
WIll someone please help me? I have no idea what to do anymore except throw the tablet out.
Click to expand...
Click to collapse
Did you try to put the update on the external sd card? Not sure if that would make a difference but i remember i used to put it there...
You could also flash a custom recovery and flash the update that way. You can find more info in this thread:
http://forum.xda-developers.com/showthread.php?t=2636093

You should safely be able to update your factory firmware first by putting it at /sdcard location.. Then just reboot. It automatic. I Thought there was also an update available in settings after that. Don't unlock til you are at 4.3.
To unlock with Asus unlock tool make sure Google 2 Step verification is disabled.
Then I used fastboot to flash CWM recovery from a computer. I think you flash with fastboot from the newly unlocked bootloader. Power + Vol DOWN.
After you have flash recovery then you can enter it. No scary man lying down.

YayYouFixedIt said:
You should safely be able to update your factory firmware first by putting it at /sdcard location.. Then just reboot. It automatic. I Thought there was also an update available in settings after that. Don't unlock til you are at 4.3.
Click to expand...
Click to collapse
I forgot to mention one thing at the start. I don't actually have on hand a external microSD card. Which I think might be why placing the zip file in the root of the internal storage did not work.
Should it work? Is there any way to get around it? I've been trying to use sideload with cwm (finally got cwm working), but it comes up with "failed to write data protocol fault no status"
EDIT: Through cwm, I chose "choose zip from /sdcard" then select the "0" file directory then i found my zip at the location. I selected it and confirmed install. However, it then comes up with "Error in data/media/0/(name of update here).zip status 6"
Thanks for the help so far but anyone have an idea about this?

Not sure. After googling I see this
http://forum.xda-developers.com/showthread.php?t=1535546
---------- Post added at 09:54 AM ---------- Previous post was at 09:45 AM ----------
You can put the zips anywhere when your recovery is installed.

Okay so I finally managed to get the custom rom installed and working. However, this did not fix my problem with the touchscreen. I think it is because it only changed the firmware but not the android version (still 4.3).
Is there any place I could find android 4.2.2 rom? This was the one the tablet was on before the update that screwed everything up. If I could downgrade to that version, it may work again.
Thanks
I gave up and just put on the android 4.3 ota from droidbasement. Now the tablet randomly restarts and is stick in reboot loop. It wont even allow me to boot into cwm recovery to delete the cache. But i accept that I now have a $600 piece of **** on my hands. Going to bed. Night.

Ya i dont like the whole void your warranty for "using it" idea. If it responds to fastboot you might be ok.

You should be able to download a 4.2.2 rom from Asus' website (.47 was the last build for 4.2.2). You can use fastboot to install it.

Alta1r said:
You should be able to download a 4.2.2 rom from Asus' website (.47 was the last build for 4.2.2). You can use fastboot to install it.
Click to expand...
Click to collapse
I tried that before but it stated "update aborted" immediately after i pressed confirm, in CWM.
But all that is in the past now. I am pretty sure that the tablet is hard bricked since it no longer even opens bootloader. I accidentally pressed the wipe data option and I read that irreversibly damages the tablet. When I hold pwr+vl down, nothing happens anymore, it keeps on its reboot loop.