Database Info

[Q] Can Not Get Into Recovery

I am unable to get into recovery of any type on my Xoom. When I try to get into recovery I get the Android with an exclamation point. I've tried factory reset; I've followed instructions for CWM recovery, etc. I just can't get past the damn Android with the exclamation point (inside a yellow triangle). Can anyone help?
BTW, there are no programs or data on the internal storage of the Xoom.

Use ADB to unlock your device again and push the recovery image again. Then try to boot into recovery.

Ok, I unlocked the Xoom and it rebooted. After the Xoom rebooted, I ran adb reboot bootloader and the Xoom went into fastboot. Now what command do I use to push the recovery image? From the platform-tools directory if tried: "adb fastboot push recovery recovery.img and nothing happened." I then tried "adb fastboot flash recovery recovery.img" without success. Help!

sddenizen said:
Ok, I unlocked the Xoom and it rebooted. After the Xoom rebooted, I ran adb reboot bootloader and the Xoom went into fastboot. Now what command do I use to push the recovery image? From the platform-tools directory if tried: "adb fastboot push recovery recovery.img and nothing happened." I then tried "adb fastboot flash recovery recovery.img" without success. Help!
Click to expand...
Click to collapse
Assuming your in the directory with the recovery.img as well:
Code:
fastboot flash recovery recovery.img
(no adb, no push)

Do the following plz with this recovery image. I assume you already have android sdk installed and adb on your laptop.
To download:
• Recovery Image: http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.img
Steps:
1. Power off your XOOM device.
2. Press and hold the volume down button while pressing the power button at the same time. Note: Even if your xoom starts again, just keep the button pressed until you see "Starting fastboot protocol" on the screen.
3. Connect Xoom to your computer via USB.
4. Open a ‘Command Prompt’ or ‘Terminal’ window on your computer in your sdk/tools folder.
5. unlock your xoom and flash the recovery image. The recovery image should be in your current working directory where you have command line navigated to: Type:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery eos-recovery-r6.img
fastboot reboot adb reboot recovery
Now, you have your device unlocked and recovery installed. I prefer this recovery than others. Give it a try.
Sent from my MZ601 using Tapatalk 2

Thanks, that worked and I'm back in operation with the Xoom. I really appreciate the support this forum provides.

I am happy I could help, and happier you are back to xoom operations without issues

Unlock, reboot and issue resolved!!! Cheers

[Q] What should I do?

I'm newbie in the Android world. I'm now rooting my HTC IncS using this guide (http://forum.xda-developers.com/show....php?t=2118187) and now stuck at step 3 which is unlocking bootloader. In this area I'm stuck where command prompt and fastbooting is included.
I'm not moving on steps unless I fastboot my IncS before I connect so I can do the step 8 and so on htcdev.com ...
What to do? I need how to fastboot my IncS. Thanks for the help.

The link is broken, but this is how fastboot is used:
1. Go to the fastboot folder and press shift+right click, then select open command prompt here
2. type in: "fastboot flash boot boot.img" where the boot.img is the file, you put in the folder before. It can also be kernel.elf, so then you type: fastboot flash boot kernel.elf

Thank you for the reply. :good::good::good:
But can you help me more? I have already flash my recovery and when I select recovery from the bootloader, it doesn't open the window where I will install the .zip files. It always turn on everytime I do it. Is there a step I did wrong?
Here is the guide I'm referring.
http://forum.xda-developers.com/showthread.php?t=2118187

[Q] After erasing the recovery with fastboot my LG p350 don't start

Hello,
I have followed a tutorial for solving the problem of "Fastboot mode started
udc_start()" from this thread http://forum.xda-developers.com/showthread.php?t=2131247 and something was go wrong.
I have done this steps in the sdk platform tools folder:
1- fastboot erase recovery
2- fastboot flash recovery recovery.img ( here i've got an error)
3- fastboot reboot
Everyting was ok until I have tried to write the .img file on the phone. I've got an error that I don't have enough space. I think I have deleted the recovery file and now it's stuck, because it's not booting. The 4 leds from the bottom it's flashing continuously and the screen remains to the LG logo. I have tried to connect the phone to the PC but the device it's not recognized anymore. I get this message in the adb tool "Waiting for device"
I really appreciate if it's someone that can help me

I have a p500 and I had the exact same problem as you. But I was able to fix it after a lot of Googling.
Can you get to fastboot right now? If so, make sure that the recovery you downloaded is correctly named "recovery.img" and is placed in the same folder as adb.exe is located. After that, type:
Code:
fastboot devices
into ADB. If your device is listed then proceed and type:
Code:
fastboot flash recovery recovery.img
If nothing comes up when you ask it to list fastboot devices you need to delete all of the drivers associated with your p350, and then reinstall them using a toolkit or PDAnet. Then go back and try fastboot devices again.
.

Logan_M said:
I have a p500 and I had the exact same problem as you. But I was able to fix it after a lot of Googling.
Can you get to fastboot right now? If so, make sure that the recovery you downloaded is correctly named "recovery.img" and is placed in the same folder as adb.exe is located. After that, type:
Code:
fastboot devices
into ADB. If your device is listed then proceed and type:
Code:
fastboot flash recovery recovery.img
If nothing comes up when you ask it to list fastboot devices you need to delete all of the drivers associated with your p350, and then reinstall them using a toolkit or PDAnet. Then go back and try fastboot devices again.
.
Click to expand...
Click to collapse
No, I can't get to fastboot. I can't do anything with the command line. It remains to the logo screen

catalin11 said:
No, I can't get to fastboot. I can't do anything with the command line. It remains to the logo screen
Click to expand...
Click to collapse
Can you pull the battery and then use the combination to get into Fastboot? If you can't get to fastboot, then the problem is beyond what I'm capable of doing.
Though, the problem may be that you completely deleted your recovery.

Logan_M said:
Can you pull the battery and then use the combination to get into Fastboot? If you can't get to fastboot, then the problem is beyond what I'm capable of doing.
Though, the problem may be that you completely deleted your recovery.
Click to expand...
Click to collapse
Now, I'm back to the first problem
"Fastboot mode started udc_start()
-- suspend --
-- suspend --
"

catalin11 said:
Now, I'm back to the first problem
"Fastboot mode started udc_start()
-- suspend --
-- suspend --
"
Click to expand...
Click to collapse
if i write this in cmd "fastboot flash recovery recovery.img" it apear < waiting for device > and nothing happens

catalin11 said:
if i write this in cmd "fastboot flash recovery recovery.img" it apear < waiting for device > and nothing happens
Click to expand...
Click to collapse
now i'm in the emergency mode

Problem solved:
1- download the official drivers from LG Site
2- cmd and:
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot -w
fastboot flash recovery recovery.img (Clowork custom recovery)
Fastboot Reboot
Installing Cyanogen after i erase everything (fastboot erase sdcard). I like fresh starts

some1 pls help me
catalin11 said:
Problem solved:
1- download the official drivers from LG Site
2- cmd and:
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot -w
fastboot flash recovery recovery.img (Clowork custom recovery)
Fastboot Reboot
Installing Cyanogen after i erase everything (fastboot erase sdcard). I like fresh starts
Click to expand...
Click to collapse
can u plz elaborate...i too have the same problem....plz..

Logan_M said:
If so, make sure that the recovery you downloaded is correctly named "recovery.img" and is placed in the same folder as adb.exe is located.
Click to expand...
Click to collapse
That is incorrect. The recovery does NOT have to be named recovery to use fastboot to flash it, although it does make life simpler

xt926 stuck in ap fastboot "sticky bit factory_fastboot

i had to sbf my phoe and now its stuck in the boot loader on each power up i can enter the boot menu and get to lock screen, but the bootloader msg is very annoying i used the rsd script generator and used unerversal i tried others by taking out the gpt and tz but same results

A quick search will get you the answer on how to clear the sticky bit error.
Sent from my HTC6525LVW using Tapatalk

i have the same problem and i didnt find anyway to fixit

Sticky Bit Fastboot
and here is the fix
First you want to download this zip file extract the file to your computer so it should read C:\Android
Next click on it once so it's selected hold left shift and right click and click on "open command window here"
Now plug in you phone and boot it up normally, then make sure usb debugging is enabled.
now in the command window type "adb devices" (this makes sure your device is hooked up and ready to be fixed)
List of commands to type in. ( in order)
1. adb reboot bootloader
2.fastboot oem fb_mode_set
3.fastboot oem fb_mode_clear
3.fastboot erase userdata
4.fastboot erase cache
5.fastboot reboot
download all the files from here
http://www.2shared.com/file/M1n_-B0-/all.html
use the first 3 command only like what i did so you wont lose your data

my phone is stuck on the boot loop. i think i cant follow this fix. do you have any other fix? thanks

[Q] one won't start

Hi, my son's oneplus one mobile will not start up. When we press the "on" button, we see the first "1+ powered by android" screen, then the word "cyanogen" is written across the screen. This word continues to slowly blur and un-blur slightly, but the system never comes any further. (The phone is fully charged).
We can also boot to a "cyanogen recovery" screen, where there are several options - where I guess a "factory reset" could be worth a try. If we do a factory reset, is there any way to maintain installed apps, and especially "progress" in these apps?
Thanks for any help,
Peter

You could try to use adb to backup the data, but you wont be able to save the progress in the apps I think, some apps have their progress stored online with your google account(Clash of clans for example)

ok, thanks (I don't know what "adb" is, but I'll google it).
Otherwise, has anyone seen this startup problem before, and are there any good solutions?
Thanks.

Hmm, seems that "adb" requires installation and/or enabling on the phone - as I can't start the phone, I don't think I can use this unfortunately.

You don't have access to adb unless it was previously enabled. Can you shed some light on what caused this situation please? It makes it a lot easier to troubleshoot. Do you know what build of Cyanogen OS was installed on the phone before this happened?

Hi, thanks for the reply. The phone's battery run out and the phone shut down. The power supply was attached, and it was attempted to turn the phone on - but this resulted in the current state where the phone stops at the "cyanogen" screen. The phone has since been charged over night, but will still not start. As to the current OS version - we are unfortunately not sure. My son says he last performed an OS update a few weeks ago.

xdzgor said:
Hi, thanks for the reply. The phone's battery run out and the phone shut down. The power supply was attached, and it was attempted to turn the phone on - but this resulted in the current state where the phone stops at the "cyanogen" screen. The phone has since been charged over night, but will still not start. As to the current OS version - we are unfortunately not sure. My son says he last performed an OS update a few weeks ago.
Click to expand...
Click to collapse
Ok, thanks. If you can get into the stock recovery you should try flashing the latest build from here, then reboot the phone.

Thanks for the suggestion - but what do you mean with "stock recovery"? We can get to a menu with these options:
reboot system now
apply update
wipe data/factory reset
wipe cache partition
wipe media
reboot to bootloader
power down
view recovery logs
Can we use one of these to upload a new OS to the phone?
"Apply update" gives the options:
apply from ADB (does this mean adb *is* running on the phone?)
choose from internal storage
"Reboot to bootloader" results in a screen where it says "fastboot mode", but gets no further than this screen.

xdzgor said:
Thanks for the suggestion - but what do you mean with "stock recovery"? We can get to a menu with these options:
reboot system now
apply update
wipe data/factory reset
wipe cache partition
wipe media
reboot to bootloader
power down
view recovery logs
Can we use one of these to upload a new OS to the phone?
"Apply update" gives the options:
apply from ADB (does this mean adb *is* running on the phone?)
choose from internal storage
"Reboot to bootloader" results in a screen where it says "fastboot mode", but gets no further than this screen.
Click to expand...
Click to collapse
That's the stock recovery. The "apply from adb' option is present whether you have adb enabled or not, so that's a no-go. I've just realised that you won't be able to use the recovery to flash the zip anyway, because there's no way to transfer the zip to the device without adb.. I think your only option will be to unlock the bootloader and flash the stock images with fastboot. Unfortunately this will erase all data on the phone, but right now you don't really have any other option. So what you'll need to do is this:
1. Install adb/fastboot onto your PC, the 15 seconds adb installer is probably the easiest option for this.
2. Use the reboot to bootloader option in recovery to put the phone in fastboot mode.
3. Navigate to where adb.exe and fastboot.exe are located on your PC, hold shift and right-click, then select open command prompt here.
4. Make sure your phone is connected to the PC via usb cable and (in the terminal window that popped up after the previous step) issue this command:
Code:
fastboot devices
It should return the serial number of the device, if it does you have a working fastboot connection. If it doesn't return the serial number you might have to play around with drivers.
5. Once you know you've confirmed that you have a working fastboot connection you can check the status of the bootloader with this command:
Code:
fastboot oem device-info
There will be a few lines of text. One of the lines will be 'bootloader unlocked: true/false". If it says true you can move on to step 6, if it says false you will need to unlock it with step 5a.
5a. Unlock the bootloader with this command:
Code:
fastboot oem unlock
The phone will automatically go through the unlock process, and will probably try to boot into the OS. Get back into fastboot mode by using the option in recovery, or by shutting the device off by holding the power button and then using the fastboot mode button combo (hold power + volume up).
6. Once you know you have an unlocked bootloader you can now flash the stock images to the device:
-Download the latest stock images to your PC from here. If you don't want the latest build you can find all stock images mirrored here thanks to @Spannaa.
-Unzip the file you downloaded and put its contents into your fastboot folder (the same folder that you have adb.exe and fastboot.exe located in on your PC).
-Open a command prompt from within your adb/fastboot folder (shift + right click, select open command prompt here).
-Issue these fastboot commands:
Code:
fastboot flash modem NON-HLOS.bin
Code:
fastboot flash sbl1 sbl1.mbn
Code:
fastboot flash dbi sdi.mbn
Code:
fastboot flash aboot emmc_appsboot.mbn
Code:
fastboot flash rpm rpm.mbn
Code:
fastboot flash tz tz.mbn
Code:
fastboot flash LOGO logo.bin
Code:
fastboot flash oppostanvbk static_nvbk.bin
Code:
fastboot flash boot boot.img
Code:
fastboot flash cache cache.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash system system.img
Code:
fastboot flash userdata userdata_64G.img
or fastboot flash userdata userdata.img if you have the 16gb model)
Please note: flashing the userdata will wipe your internal storage (your virtual sd card). It's possible to flash these images without that command if a full wipe isn't completely necessary in your situation.
-Reboot your device with this command:
Code:
fastboot reboot
-It's now safe to disconnect your usb cable.
Click to expand...
Click to collapse
Hopefully the phone will boot up now.

Thanks heaps for the info. My son has now re-established his telephone - though he lost all his data/progress/photos etc.. Is there a recommended backup mechanism for the OnePlus One? (Maybe he can run a backup application on his PC once a week which takes a snapshot of his phone?)

xdzgor said:
Thanks heaps for the info. My son has now re-established his telephone - though he lost all his data/progress/photos etc.. Is there a recommended backup mechanism for the OnePlus One? (Maybe he can run a backup application on his PC once a week which takes a snapshot of his phone?)
Click to expand...
Click to collapse
The best way is by creating a backup with TWRP recovery. You'll find instructions on how to flash it (and how to make a backup) in my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471