Database Users

HEEEEEEEEEEEEEELP ME - Can't able to go in fastboot mode

Hi All. During a upgrading phase I don' know what appened but:
- The device start only in recovery mode
- I don't able to go in fastbbot mode, both pressing keys on startup of device or by fastbbot command line
- the command "fastboot devices" give me any device attached, or other fastboot cmmand < waiting for device>
- command adb devices give me:
C:\Temp\android-sdk-windows\tools>adb devices
List of devices attached
HT936NG00644 recovery
- I am able to push .zip on Dream (adb push ...) and install it by ALT+S on Dream
- On the Dream I reach this error:
- E:Can't read MISC: (No space left on device)
- E:Can't open /cache/recovery/command
- any other adb command by command line, give me the follow error:
C:\Temp\android-sdk-windows\tools>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
HELPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPP, Its 4 days I didn't able to solve.
Can anyone help me ?
Thanks
Pippapeppa

pippapeppa said:
Hi All. During a upgrading phase I don' know what appened but:
- The device start only in recovery mode
- I don't able to go in fastbbot mode, both pressing keys on startup of device or by fastbbot command line
- the command "fastboot devices" give me any device attached, or other fastboot cmmand < waiting for device>
- command adb devices give me:
C:\Temp\android-sdk-windows\tools>adb devices
List of devices attached
HT936NG00644 recovery
- I am able to push .zip on Dream (adb push ...) and install it by ALT+S on Dream
- On the Dream I reach this error:
- E:Can't read MISC: (No space left on device)
- E:Can't open /cache/recovery/command
- any other adb command by command line, give me the follow error:
C:\Temp\android-sdk-windows\tools>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
HELPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPP, Its 4 days I didn't able to solve.
Can anyone help me ?
Thanks
Pippapeppa
Click to expand...
Click to collapse
What buttons are you holding while you bootup?

Hi JAguirre1231,
Thanks for the response.
I Hold Back+Power or Camera+Power. In any way I boot the Dream always go in Recovery Mode.
Thanks again for Your Help.
Pippapeppa

Try to reflash radio and SPL but be careful. I can't give you warranty that you will not broke your phone completely. You have damaged data in ROM (radio & SPL) and I think that reflashing it should help you but also can damage it completly (but I think that it shouldn't happen). The risks increase fact - you must flash radio & spl from recovery but this method is strongly discouraged because of risks to broke phone (read topics about dangerSPL and why you shouldn't use recovery to flash it).
http://forum.xda-developers.com/showthread.php?t=831139

Hi Gerdal,
Whitch version of Radios and SPL have I to reflash.
Which procedure can I follow ?
Thanks again, there are to many information and I understand that if we can chach procedure, sequence and version we can total brick the phone.
Regards
Pippapeppa

Radio - http://forum.xda-developers.com/showthread.php?t=640535
SPL - in attachments
Flash RADIO, reboot, wait - phone will reboot automatically to recovery, flash SPL, reboot and again wait before phone automatically rebot to recovery. If everything goes correct you can reboot and try to boot in fastboot.

Hi Gerdal,
I just done the two updated without errors.
I didn't resolve The dream start only in recovery mode .
I am desperate
I don't understand this thing, if I run by PC with Dream connected by USB the command:
C:\Temp\android-sdk-windows\tools>adb devices
I obtain:
List of devices attached
HT936NG00644 recovery
The devices is visisible and accesible by PC,
If I run:
C:\Temp\android-sdk-windows\tools>fastboot devices
Nothing is the response, I presume that the tool fastboot don't see the Dream.
Any Hel is appriacied
Regards Pippapeppa

fastboot devices will see phone only if phone is running in fastboot mode. Are you sure you pressing camera+power when you powering on phone? Can you try to flash any ROM in recovery, reboot (do not press any buttons) and try to boot to android? Maybe camera button is broken?
Actually I'm trying to find possibility to flash entire ROM (everything what is in nbh file) through recovery. This should repair everything. Maybe someone know what to do this and will write how to do that?

Hi
Gerdal said:
fastboot devices will see phone only if phone is running in fastboot mode. Are you sure you pressing camera+power when you powering on phone? "Can you try to flash any ROM in recovery", reboot (do not press any buttons) and try to boot to android? Maybe camera button is broken?
Click to expand...
Click to collapse
I haven't find any botton to switch off the Dream, the only way is reboot (HOME+BACK or PHONE+POWER+MENU). So immediatly after I press HOME+bACK I press CAMERA+POWER. Should be that the mapping of the keys are not correct ?
How can perform "Can you try to flash any ROM in recovery", I understood that this operation should be only in fastmode. If I can do it and You can tell me how should be a good way.
Thanks again
Pippapeppa

Which recovery are you using? Have you flashed once a custom recovery for example AmonRa Recovery or ClockWork recovery? If you have one of them you can flash any zip that contains ROM for example cyanogenmod. If you flash this and reboot, the phone should boot into this system. If not we need to find answer why it don't do that.
You are pressing rights buttons when you try to boot in fastboot so I don't understand why it don't works...

Sorry Gerdal I am a beginner on this space.
I explane you the context because I am very frustrated.
The device is of my collegues and I am test it for potential purchase. I have attempted to upgrade it to appreciate al the functionalities and I have done the trouble !
So I don't know which recovery I am using I know that the Dream has been rooted.
If You can be kind to explain me the major step to execute and the reference to the persion of files I will be grateful ... forever.
Thanks again
Pippapeppa

Hi Gerdal,
I have flashed with ionr1-signed.zip, the ROM installed before the Hang.
I have attempt to install and run this (http://forum.xda-developers.com/showpost.php?p=9221440&postcount=39), but without result. seems the internal partition are all broke / unconfigured and any script on this partitation are unavailable.
Always the same behavior
Thanks for any help

Sorry but I can't help you. I don't understand why these ways don't work for you.

Nexus one is not detected in ADB mode, yet detected in fastboot

Now I know what you are thinking: Well you need to install the drivers. Well that's all said and good, except the problem is when I boot int ADB (hboot? Unsure of what to call it.) There is no hardware at all being installed. At all. There isn't any devices that are connected and the computer doesn't detect anything. My problem is that my power button is broken, and I'm not quite able to get a new phone yet. Because of this, I cannot boot into recovery to flash a new rom, nor can I install Blackrose to use the trackball to avoid this problem. I'm just basically stuck because my phone is now a useless brick because I cannot flash a rom since I wiped my phone. Ideas?

try PASSIMG method?

will this help getting to recovery to flash rom without pwr button
http://forum.xda-developers.com/showthread.php?t=1419813

rugmankc said:
will this help getting to recovery to flash rom without pwr button
http://forum.xda-developers.com/showthread.php?t=1419813
Click to expand...
Click to collapse
Ha the ironic thing is I bought this and used it to wipe my phones rom because I was planning on installing blackrose and then QND. Sadly nope, because I can't get to the recovery itself because I can't press recovery on the bootloader bit.
////////////////
I'm unfamilliar with the Passimg method..got any links? I did a search but couldn't find anything.

Passimg is in wiki under nexus one, never used it--yet
So, not sure if it will help

Yeah not sure if it will work. If I read it correctly the OP wipe his phone clean, no OS or anything on it and can't get into recovery. I only suggest PASSIMG hopefully the phone pick it up upon reboot while holding down the VOL DOWN button.

ADB is a daemon that runs in OS, after the kernel boots.
You're booting into HBOOT. So you won't get anything but fastboot. This is normal and how it should be.
You can either use PASSIMG method, or open your phone and fix the power button for $30-something + having good hands, or even for $0 + thin wire + soldering equipment + very good hands, and optional microscope.

in this case would you be able to use fastboot boot recovery.img and restore a backup or flash a rom?

If you have unlocked bootloader - yes, by all means. But not without it.
The problem is that if power button failed, and bootloader isn't unlocked - you can't unlock it anymore, the procedure requires pressing power button to confirm.

did you try this tut on nexus one wiki?
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Unroot/restore
cheers

Question: If your power button doesn't work - how do you currently turn ON your phone?
Let's keep it simple and try the obvious first. Is USB Debugging turned on in the phone?
Go to Menu -> Settings -> Applications -> Development -> (check) USB Debugging.
2nd, make sure you have the android SDK installed on your computer (if so, download the usb drivers with the androidsdk app that's included).
You can also right click My Computer -> Manage -> Device Manager -> Make sure under Android Devices yours is listed and that there are no yellow question marks. If there is, do the android sdk drivers step and then right-click the icon in device manager, choose Update Driver and point it to the android sdk drivers folder.
Finally, ADB works in recovery and when phone it booted but NOT in Bootloader mode.
If you can get ADB working then you can install a custom recovery using Fastboot (in bootloader mode) then click Recovery to boot into the new recovery. Also, while in the recovery or ROM you can use "adb reboot recovery" to boot into recovery menu.
Hit Thanks if this helped.

" x " appears on the screen

Malfunction " x " appears on the screen !! help me what is going on

Haha... you'll need more information than that if you want real help.
Based on the limited information though I suspect your phone is stuck in a bootloop. I'd hook it up to the PC via USB and check the logcat. Probably something screwed up.. Maybe time to restore your latest backup.

Did you flash any ROM if so, did you clean your Dalvic+REgular Cache

If you don't have an Recovery:
- Connect your Micro SD on PC
- Download and insert on SD the stock ROM of your Nexus One
- Power ON your Nexus with Volume Down Pressed.
- Autmotically Restore Nexus (You should say Yes xD)
At this time, you decide if you want to be root and install other ROM

you better just list your setup info before doing anything
locked/unlocked bootloader
rooted/unrooted
which recovery are you using
what rom are you running stock/custom
what were you doing when this happened
a couple safe things you can do in meantime is to pull battery and reinsert and power on
if it goes back to X, pull battery and DO NOT power on. Hold down the pwr button and trackball at same time and see if you can get into recovery
the third is hold down trackball/vol-/power at same time while X is on screen and see if you can get to recovery that way
if you can't get to recovery you will need to fastboot new recovery, assuming you are unlocked
once you get into recovery do a nandroid if you are rooted
and copy it to pc as a secondary backup
it is possible you may need to try the passimg method in wiki
http://forum.xda-developers.com/wiki/Nexus_One/Guides_&_Tutorials#Unroot_.2F_Restore_your_Nexus
also to do fastboot commands you need usb debugging selected on phone--hope it is

Hello, i have a similar problem with my n1
the phone starts and just shows the nexus X - (waited for 15 min. nothing happend)
i can go to the bootloader / fastboot menu with PWR + (Vol-) but i can not go to the recovery mode. -> the phone reboots and get stuck at the X
the phone is rooted
blackrose / hboot 7.35.5017
radio 5.12.00.08
recovery was ext4
i had a german ics miui rom installed and tryed to install the latest ics miui us rom after it didn't booted the miui us rom i turned the phone off and tryed a few hours later to turn it on to reflash the german ics miui rom.
1.)
i tryed to install a new recovery image ->
recovery-clockwork-5.0.2.0-passion &
recovery-RA-passion-v2.2.1
(still get stuck at the X if i try to go to recovery mode)
2.)
i tryed this one with the passimg.zip but nothing happens if i put in the sd card :/
(with nothing i mean the green text show that the sd card is checking for PASSDIAG.zip and PASSIMG.zip but dosn't found it)
i also tryed:
3.)
erased boot
flash boot from passimg.zip (PASSIMG_Passion_Google_WWE_2.18.1700.1_FRG83_release_signed)
4.)
erased cache
erased userdata
started again with 1.)
5.)
got frustrated and erased system -.-
any ideas?

study it ,thank you
study it ,thank you

Hmm, sorry if its obvious but i have no idea what it could be or what i have to search to find the solution. Would be nice if you could give me a hint. Of course im not asking for a step by step solution. Thank you.
Send from my awesome SE K800i

not sure why you are flashing boot images
do you have a nandroid--copy your sdcard with the nandroid to pc--all of sdcard
are you flashing thru fastboot in command window
did you read my post above on getting to the fastboot screen--can you do that--the one with the 3 androids
pwr/vol-/trackball same time, may take 20-30 seconds
if you can get there, put your recovery image in your fastboot folder on pc, normally tools--assuming you have sdk installed, your phone must have usb debugging checked--I hope
open a command window and change directory to the tools folder or wherever the fastboot.exe file is. Something like:
cd/
cd/ android/android-sdk-windows/tools for me
then on same line type
fastboot devices (it should show your phone H#)
fastboot erase system
fastboot flash recovery recovery.img (or the exact name of the recovery image, checked by right clicking on the img file in your tools folder and looking under properties)
I would use amonra you listed above and check the md5 if possible
hopefully the recovery will flash
if not you can go to the wiki link i posted above and try passimg metthod from there, use correct one. don't add the .zip. Windows will had it automatically.
a side note, DON"T flash different roms without wiping all including System 3 times before flashing--prevents a lot of problems

rugmankc said:
a side note, DON"T flash different roms without wiping all including System 3 times before flashing--prevents a lot of problems
Click to expand...
Click to collapse
thank you very much
i already tryed everything else what you wrote but i didn't wiped 3 times... after erasing recovery partition 3 times i was able to flash a new recovery and it started.
Thanks a lot!

Glad that you got it

[Q] Stuck in boot loop - Save Photos?

Hi,
my Nexus 4 is stuck in a boot loop since 2 days. I found it turned off and assumed it crashed (has done that once or twice before), but after turning it on it's gets stuck on the boot up screen. I've tried restarting it numerous times, left it on the boot screen for hours - nothing.
I can access the recovery mode and according to most things I've found while searching the internet for a solution a "wipe data/factory reset" would hopefully do the trick, but the thing is... I haven't backed up my device in ages. (Stupid, I know.) I'm travelling and took a lot of pictures that I would hate to loose.
Is there any way to save them? I don't care for app data or anything else.
I wouldn't mind rooting it (was thinking about doing that anyway), but I'm pretty much a n00b when it comes to Android, haven't done more with it than simply using it.
I have read up quite a bit about rooting in the last two days (here on the forum and everywhere else) but I'm still not sure how exactly to do it, since all methods seem to require unlocking the bootloader and therefore deleting my photos (or just don't give much in the way of explanation).
I'm using a mac, but if necessary I also have Windows installed. I have installed Adb and fastboot following this guide.
The phone is not rooted, I don't have developer options or USB debugging enabled and it's running on 4.4.4.
I would be really grateful for help.

If you can boot into the bootloader you can install a custom recovery, I'd recommend twrp. Then booting into the custom recovery you could use adb to pull files off your device . But your bootloader needs to be unlocked. If it isn't I'm afraid you won't be able to get your photos
Sent from my SAMSUNG-SGH-I957 using XDA Free mobile app

bootloop issue
A.
Try to go into safe mode and backup your data.
Boot into Safe Mode:
1. Press/Hold Power button until power menu shows up
2. Tap/Hold Power off option
3. Choose OK to reboot in safe mode
B.
For bootloop problem:
Boot into Stock Recovery
1. Power+VolUp while booting to enter recovery
2. You can release buttons after you see Google on screen
(Note: Must be this sequence Press/Hold Power, THEN Press/Release VolUp, release Power)
3. Android fallen down screen - VolUp to toggle recovery menu
Now wipe Cache & Dalvik Cache in recovery and reboot the phone.
C.
If the (Option B) does not solved then try to flash the stock rom with the below given mentioned steps.
First download any stock rom and also the related usb drivers. Install the drivers into the PC.
Boot into the bootloader.
Open (fastboot.exe) Cmd prompt as admin. Put the stock rom into that particular folder.
fastboot flash bootloader filename.img
reboot the phone and return back to the bootloader.
Then, we will flash all other partitions.
fastboot flash radio filename.img
Again reboot the phone and go back into the bootloader
fastboot flash boot filename.
fastboot flash recovery filename.img
fastboot flash userdata filename.img
fastboot flash system filename.img
If you want to relock the bootloader of your device after flashing the device, put the device back in fastboot mode. Then type in the following command in the Terminal or Command Window you had opened earlier -:
fastboot oem lock
This will re-lock the bootloader of your Nexus device, restoring your warranty and putting the device back to complete stock.
I hope this helps you out.

Thank you, but is there a way to boot into safe mode if the phone isn't turned on? I can not get to the power menu since I can't turn the phone on...
I can only access the recovery menu.

Data backup
Alternate method you can do is that you have to download a software by name 'DROID EXPLORER' - (try to google it) you will find this software from the internet. Then install the software on your PC or Laptop. Once you open the software it will take some time to download the sdk files from the internet then install the windows sdk files also.
Later you go into the recovery mode with the usb cable connected to your PC. Then open the Droid Explorer software you will see your phone connected picture. Now double click and open it go to sdcard and copy all your pictures and other files to your system.
Finally, Once you backed up all your files now you can reflash with the proper rom from the recovery mode. From directly inserting the rom.zip file into the sdcard and run the custom rom after you wipe the partitions properly in recovery.
Note: Before wiping the partitions always unmount the system, data, cache and then wipe it.

HTC U Ultra stuck in bootloop..Can you experts validate the STEPS to solve the issue?

So, my HTC U Ultra got stuck in bootloop just 3 days after warranty ended(tough luck level : 100).
My phone runs on everything stock and no root.
I press all the buttons when powered off and it goes into bootloader mode. It displays options to boot into recovery mode, boot into download mode and power down, all of which(except power down) gets device into bootloop again.
THE PRIORITY OF GOALS IS : DATA RECOVERY > PHONE BOOTING AND WORKING PROPERLY AGAIN
I did a little research and figured out some sort of procedure by putting bits and pieces together :
1. Download ADB/Fastboot toolkit || universal driver from koush github // I have HTC Sync manager installed as well || twrp custom recovery image for htc u ultra || new ruu from htc support for rom update.
2. Now I put my phone into fastboot mode (since it doesn't show up on adb devices), connect to pc using usb.
3. I type in cmd : "fastboot devices" --> My device shows up there --> Again in cmd : "fastboot boot recovery mytwrp.img" --> the twrp boots into my phone
I was able to put this many steps together and after the last step, i have an abstract idea of what to do :
Enable USB Debugging using twrp recovery --> Use ADB Pull Command to get my all my data from phone to pc --> Use adb wipe the old Firmware (Not sure which command) --> Use adb again to flash new RUU (again not sure how, I've got an .exe file as RUU || should I get it in zip or img or any other format ? || Please help on this too) --> Finally Boot and hopefully everything turns out smooth and secure.
CAN YOU EXPERTS HELP ME TO PUT TOGETHER REMAINING STEPS (AND MODIFY ERRORS, IF ANY, OF EXISTING STEPS ) OF THIS PROCEDURE...???

Only to clarify: ADB and Fastboot are 2 completely different things.
ADB
is a protocol that allows you to communicate with an Android device that got booted, means its main Android OS is running
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb <ANY_SUPPORTED_ADB_SUBCOMMAND>
FASTBOOT
is a program used to manipulate (list, install, erase) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode with the fastboot protocol enabled.
IMPORTANT: Fastboot will only work if the OEM/Carrier has included support for the Fastboot protocol.
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot <ANY_SUPPORTED_FASTBOOT_SUBCOMMAND>

jwoegerbauer said:
Only to clarify: ADB and Fastboot are 2 completely different things.
ADB
is a protocol that allows you to communicate with an Android device that got booted, means its main Android OS is running
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb <ANY_SUPPORTED_ADB_SUBCOMMAND>
FASTBOOT
is a program used to manipulate (list, install, erase) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode with the fastboot protocol enabled.
IMPORTANT: Fastboot will only work if the OEM/Carrier has included support for the Fastboot protocol.
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot <ANY_SUPPORTED_FASTBOOT_SUBCOMMAND>
Click to expand...
Click to collapse
@jwoegerbauer Yes, thank you for the description, I understood the difference later on. Do you think the fastboot and adb steps I've mentioned will work properly ?

noobie12112 said:
@jwoegerbauer Yes, thank you for the description, I understood the difference later on. Do you think the fastboot and adb steps I've mentioned will work properly in my case?
Click to expand...
Click to collapse
Android boot loop error does not come out of thin air. There are several cases that may cause the Android is starting loop. If phone didn't get physically damaged then an action of the user is the main reason .
To answer your question: NO.
As already said:
ADB is integral part of Android OS hence if Android OS isn't started you can't make use of ADB, Fastboot is integral part of phone's bootloader ( comparable to a Windows PC's UEFI/BIOS ) means you can't access Android OS - will say its folders and files.

jwoegerbauer said:
Android boot loop error does not come out of thin air. There are several cases that may cause the Android is starting loop. If phone didn't get physically damaged then an action of the user is the main reason .
To answer your question: NO.
As already said:
ADB is integral part of Android OS hence if Android OS isn't started you can't make use of ADB, Fastboot is integral part of phone's bootloader ( comparable to a Windows PC's UEFI/BIOS ) means you can't access Android OS - will say its folders and files.
Click to expand...
Click to collapse
@jwoegerbauer Thank you for the insight. In my case, the phone wasn't physically damaged, the bootloop occurred out of the blue one day. Now, what I presumed I should do, is to flash a custom recovery (twrp) using "fastboot boot recovery.img" command, and using twrp (Can I enable USB Debugging using twrp ?) to access files, backup and then flash a new RUU. But I found that I need to unlock bootloader, is there any way to use command "fastboot oem unlock" and not lose data, or any other method to unlock bootloader, where i don't lose data?
Thank you for your help.

Unlocking phone's bootloader always causes complete loss of data.
Forget the TWRP thing, it's not helpful at all in your case.
Try to flash phone's Stock ROM by means of ADB - what requires ADB got installed on Windows computer and USB debugging got ( manually !!! ) enabled on phone.