a buddy of mine bought a nexus s off of craigslist that is constantly force closing when you boot it. it will force close everything then reboot itself. im attempting to unlock the bootloader but adb devices doesnt show the serial number like it does for my nexus s. when i hold down volume up+down and plug in the usb it goes to the unlock bootloader screen but it doesnt give you the option of yes or no. iv posted a picture to show what it looks like. i cant get the phone into download to try to fix it with odin either. any help would be appreciated.
edit: i finally got my pc to recognize it and we now have an unlocked bootloader, but now iv encountered another problem. i downloaded a recovery image and moved it to the tools folder of sdk when i type in the fastboot flash recovery command it responds with error: cannot load recovery.img.
To unlock bootloader, you have to use fastboot, not adb. So the correct command would be fastboot devices
To boot into the bootloader, you have to press volume up + power, not volume up+down and plug in the usb -- that would bring you into the Download Mode instead
suksit said:
To unlock bootloader, you have to use fastboot, not adb. So the correct command would be fastboot devices
To boot into the bootloader, you have to press volume up + power, not volume up+down and plug in the usb -- that would bring you into the Download Mode instead
Click to expand...
Click to collapse
i know, i used adb devices to see if my computer would even recognize the phone. i i can get into fastboot mode by pressing volume up and power but cant send a fastboot command to the phone because it doesnt recognize the phone. when i hold down volume up and down to get into download mode it sends me to the screen i showed in the pic. its the unlock bootloader screen except there is no option to click yes to unlock the bootloader. i would love to get into download mode and use odin hence why i pressed vol up and down and plugged in usb, but like i said it sends me to the unlock bootloader screen.
fosdos4790 said:
a buddy of mine bought a nexus s off of craigslist that is constantly force closing when you boot it. it will force close everything then reboot itself. im attempting to unlock the bootloader but adb devices doesnt show the serial number like it does for my nexus s. when i hold down volume up+down and plug in the usb it goes to the unlock bootloader screen but it doesnt give you the option of yes or no. iv posted a picture to show what it looks like. i cant get the phone into download to try to fix it with odin either. any help would be appreciated.
edit: i finally got my pc to recognize it and we now have an unlocked bootloader, but now iv encountered another problem. i downloaded a recovery image and moved it to the tools folder of sdk when i type in the fastboot flash recovery command it responds with error: cannot load recovery.img.
Click to expand...
Click to collapse
Before you try to unlock the bootloader I would flash the latest stock rom and see if it boots properly.
Sent from my PC36100 using XDA Premium App
fosdos4790 said:
edit: i finally got my pc to recognize it and we now have an unlocked bootloader, but now iv encountered another problem. i downloaded a recovery image and moved it to the tools folder of sdk when i type in the fastboot flash recovery command it responds with error: cannot load recovery.img.
Click to expand...
Click to collapse
Try one of these recovery images:
http://forum.xda-developers.com/showthread.php?t=988686
The full command is
fastboot flash recovery recovery.img
(make sure your recovery image file is actually named recovery.img)
If 'fastboot devices' returns your phone's id you can flash a custom recovery. Otherwise get a full _signed_ stock rom and flash from stock recovery.
Did you install all drivers? Deinstall existing and use either pdanet or sdk build in program to get them. You need like 3 different ones.
Try locking unlocking bootloader again.
There's always the chance you got a defective usb connector.
Sent from my Nexus S using XDA App
I apologize if I have understood this all incorrectly, but kindly clarify the following for me.
What I have already done:
1. Installed CWM (ClockWorkMod) on the tablet: Galaxy Tab 2 7.0 using Odin
2. Installed the rooting zip file from external sd
3. Made a backup image on an external sd
What I need to do:
1. Flash a custom ROM onto the device from my PC using fastboot
Errors:
1. Fastboot devices returns nothing (absolutely no response... please find the attached pic)
2. Adb reboot bootloader - just reboots the OS (not in fastboot)
3. Fastboot oem unlock says waiting for device endlessly.
My Queries:
1.I have a recovery mode and download mode (aka odin mode). Is either of them the FASTBOOT mode or is fastboot something completely different. If so how to get into FASTBOOT mode??
I read I have to get a USB icon and a Fastboot mode display on screen. I do not.
2. Why is my device not showing under fastboot devices (on download mode, neither show the device.), but adb devices shows the device under recovery mode
3. Is it possible to flash a ROM using fastboot if I have CWM installed. Or does CWM disable fastboot?
4. Also does this device have a Fastboot mode at all? If yes how to get into Fastboot mode??
From what I've read here, there is no fastboot mode on the Tabs.
Balthazar B said:
From what I've read here, there is no fastboot mode on the Tabs.
Click to expand...
Click to collapse
In that case, how do I flash a custom ROM onto the device?
Thanks!
rtindru said:
In that case, how do I flash a custom ROM onto the device?
Thanks!
Click to expand...
Click to collapse
load it on your external sdcard, boot into cwm and do a fullwipe/factory reset then install the zip from sdcard. poof, rom installed
to boot into cwm, turn off the tablet.
press and hold power and volume down (the one closes to power button) once the samsung tablet logo appears let go of power and continue holding vol down until cwm appears (this can take a couple minutes)
Thanks then!
Darunion said:
load it on your external sdcard, boot into cwm and do a fullwipe/factory reset then install the zip from sdcard. poof, rom installed
to boot into cwm, turn off the tablet.
press and hold power and volume down (the one closes to power button) once the samsung tablet logo appears let go of power and continue holding vol down until cwm appears (this can take a couple minutes)
Click to expand...
Click to collapse
Well thanks for the info.
I recently bought a HTC One XL 4G from the Telstra Shop. I unlocked the bootloader successfully through the HTC DEV website. Downloaded Hasoons 2000 HTC One X All in one kit and flashed the kernal with stock 2.6.39.4. The phone rebooted, displaying the message 'this mode is for development purposes...' Phone is running image version 2.40.841.4, HBOOT 1.14.0002. Radio 0.20os.32.09.15. EVITA S-ON.
What I can do: I can boot into recovery mode. The device in windows is displayed as 'my HTC Phone'. I can send Fastboot commands through the CMD window to relock bootloader, restart, clear cache etc.
What I can't do: The factory reset, clear storage,recovery etc when pressed reset the phone back to the ''this mode is for development purposes...' message. I have tried to use an ROM Ruu updater utility to reset back to stock but cannot find the right version for 2.40.841.4. I have downloaded a Stock_Root ODEX 2.40.841.4 that matches, however not sure how to install onto phone.
Obviously I am an extreme noob, however there does not seem to be many resources for the HTC One XL roms. Really run down with this process, don't seem to be making any headway. Should I send this back to Telstra ?
Please Help !!!!!
Connect to PC, install twrp recovery, boot into recovery, download and place flashable stock kernel or any ROM on your device ( you can mount sd card through recovery ).
You can also just download and flash kernel ( boot.img ) using below command while you have your phone in fastboot USB mode connected to PC
fastboot flash boot boot.img
Sent from my HTC One X using Tapatalk 2
kancherlapraneeth said:
Connect to PC, install twrp recovery, boot into recovery, download and place flashable stock kernel or any ROM on your device ( you can mount sd card through recovery ).
You can also just download and flash kernel ( boot.img ) using below command while you have your phone in fastboot USB mode connected to PC
fastboot flash boot boot.img
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the reply, appreciate your time. I connected to PC, successfully flashed 'openrecovery-twrp-2.3.1.0-evita'. Rebooted phone, stuck in loop still resets to 'this build is for development..' then switch off, then switches on again.
How do I boot into recovery ? ...the next step ?
power off -- then hold power + volume down - It will go to fastboot - from there you can go to recovery
kancherlapraneeth said:
power off -- then hold power + volume down - It will go to fastboot - from there you can go to recovery
Click to expand...
Click to collapse
Thanks so much. I am back in business.
Hey All,
My Dad's Xoom died over the weekend - 13months after purchase so is not covered by the warranty. He was browsing a site, it came up with a "Internet is not responding - do you want to continue to wait" message and he clicked Wait - after a second the tablet knocked off. It will not come on by pressing Power and only turns on by pressing Power and Vol +
It gets past the Motorolo logo screen and the device starts the boot animation, about 20 seconds into this it freezes and reboots - this continues in a loop. It's been GEDified and was running the last OTA update 4.1.2 - no root etc.
I can get into the stock recovery and performed a factory reset - but the same thing happens. I've also tried Update From USB with an OTG cable but the screen just shows Choose a package to install and under it has /sdcard but nothing else. I have a dummy zip on both the Flash disk and SD card so it's not reading either.
I've also tried to perform update via ADB - when I select it and connect to a PC (Win 7 32bit) it tries to install drivers but I see In Computer Management that it shows under Unknown. ADB Devices returns List of devices message but nothing under it.
I've also selected the fastboot command at boot, tried fastboot devices and the command does see the Xoom.
So my questions
1) Anyone seen anything like this issue before and know how to fix it?
2) Is it best to try to reinstall the ROM? If so, how do you suggest I can see it with ADB?
3) As I have Fastboot command, could I try to install CWM and see if that sees a ZIP on the sdcard - so I can install a new ROM.
Any help much appreciated :good:
so...I've just done a fastboot oem unlock
and then tried to flash the CWM recovery using the fastboot commands - no errors, press reboot and go into Recovery but still getting Android system recovery 3e :crying:
claned said:
so...I've just done a fastboot oem unlock
and then tried to flash the CWM recovery using the fastboot commands - no errors, press reboot and go into Recovery but still getting Android system recovery 3e :crying:
Click to expand...
Click to collapse
So just to add to this, I found the stock recovery.img, boot.img, userdata.img and system.img and used the fastboot commands to send all to the motorola - all succeeded without error....still the same problem though.
I installed RSD lite and tried a few SBF files but I'm getting an INI error - off to google possible solutions to that now
I have 2 Xoom tablets, in Germany, and I took the SD Card from one of them to put it on a new phone, the Tablet kept working fine until last week that I forgot to plug it and the battery ran out. When I charged it and started it, it didn´t work again, I got the Encryption message, nothing happens when I click the Reset Tablet either, I tried putting the SD card from my other Xoom but still nothing. I enter the Recovery mode and did a Factory Reset and the tablet was OK.
Battery run out again yesterday and got the same problem once again, but now factory reset is not working, tablet stays stuck at the "M" logo after doing it, I have repeat the operation a zillion times and nothing, it stays on the M. Plus I can´t turn it off either.
The model is the MZ604 and Android Version 4.0.4
I connected the xoom to the computer after installing the drives but it won´t recognize it. I got to do the fastboot and flashed motorolas images but nothing. I can´t do the adb reboot bootloader command because ADB won´t work, because I don´t have USB Debbuging checked, but I can´t check it now because I can´t get to settings (
What can I do to recover the tablet?
Anyone, is driving me crazy, no matter how many time I flash new images it always stays on the original, so I can´t flash any special recoveries either
I tried RDS too and after the reboot stays the same in the M logo, nothing changes. What can I do?
No ideas? :crying:
I want to save the tablet if possible.
Hi, could you explain exactly what you've tried?
In particular what you mean by "I got to do the fastboot and flashed motorolas images but nothing." and "no matter how many time I flash new images it always stays on the original, so I can´t flash any special recoveries either"
By flashed Motorola's images do you mean you flashed the stock images?
And when you say you flash new images but it always stays on the original, I assume you mean the recovery stays as Xoom default?
Let me know and I'll see if I can help.
alecbond said:
Hi, could you explain exactly what you've tried?
In particular what you mean by "I got to do the fastboot and flashed motorolas images but nothing." and "no matter how many time I flash new images it always stays on the original, so I can´t flash any special recoveries either"
By flashed Motorola's images do you mean you flashed the stock images?
And when you say you flash new images but it always stays on the original, I assume you mean the recovery stays as Xoom default?
Let me know and I'll see if I can help.
Click to expand...
Click to collapse
Yes I mean stock images, and yes, it always stays on Xoom default, it never changes no matter which Recovery image I flash.
The recovery is likely reverting to default because the Xoom does this automatically each boot.
We might be able to give you a recovery that stays put but the booting issue may or may not be something worse.
Being able to fix the recovery in place is reliant on adb working from recovery itself, which I'm unsure is possible.
Whilst you seem to have reasonable knowledge of flashing and using adb/fastbbot, I'll give full instructions.
I assume you have the necessary files for fastboot so I'll skip that.
Place your chosen recovery image in your fastboot folder. (I recommend ClockworkMod Touch recovery from here)
Hold shift and right click the folder containing your recovery image and fastboot files, then select 'open command prompt here'
Your PC is now setup for the fastboot process.
Connect your Xoom to your PC.
Power on your Xoom and once you see the Motorola logo, wait about 3 seconds, and press volume down.
The screen should show the Motorola logo in the center and '--> Android Recovery' in the top left.
Press volume down twice more until the top left says fastboot then press volume up.
The screen will say 'Starting Fastboot protocol support'
Now on your PC, in command prompt run the following:
fastboot flash recovery xxxx.img
Rename xxxx.img to whatever your recovery .img file is namedOnce verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Again, when you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery, you should now see your flashed recovery.
This is where I'm unsure. Try running the following:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.oldIf you are able to run this, this will rename the files that are reverting the recovery to default and prevent it happening again. If not, we can go ahead with attempting to flash stock images anyway.
To flash stock images download Build H.6.2-24 for Retail Europe (found here.)
Extract the files to your fastboot folder.
Again, reboot your Xoom, either by holding volume up and power, or from recovery.
And again, after about 3 seconds press volume down 3 times until the top left says '--> Fastboot' then press volume up.
Now run the following from command prompt:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lockThis will wipe all data on the Xoom, and hopefully reset it to stock.
Finally, run:
fastboot rebootand you should boot into Android 3.2(?), fingers crossed.
If you require further clarification or help let me know.
alecbond said:
The recovery is likely reverting to default because the Xoom does this automatically each boot.
We might be able to give you a recovery that stays put but the booting issue may or may not be something worse.
Being able to fix the recovery in place is reliant on adb working from recovery itself, which I'm unsure is possible.
Whilst you seem to have reasonable knowledge of flashing and using adb/fastbbot, I'll give full instructions.
I assume you have the necessary files for fastboot so I'll skip that.
Place your chosen recovery image in your fastboot folder. (I recommend ClockworkMod Touch recovery from here)
Hold shift and right click the folder containing your recovery image and fastboot files, then select 'open command prompt here'
Your PC is now setup for the fastboot process.
Connect your Xoom to your PC.
Power on your Xoom and once you see the Motorola logo, wait about 3 seconds, and press volume down.
The screen should show the Motorola logo in the center and '--> Android Recovery' in the top left.
Press volume down twice more until the top left says fastboot then press volume up.
The screen will say 'Starting Fastboot protocol support'
Now on your PC, in command prompt run the following:
fastboot flash recovery xxxx.img
Rename xxxx.img to whatever your recovery .img file is namedOnce verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Again, when you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery, you should now see your flashed recovery.
This is where I'm unsure. Try running the following:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.oldIf you are able to run this, this will rename the files that are reverting the recovery to default and prevent it happening again. If not, we can go ahead with attempting to flash stock images anyway.
To flash stock images download Build H.6.2-24 for Retail Europe (found here.)
Extract the files to your fastboot folder.
Again, reboot your Xoom, either by holding volume up and power, or from recovery.
And again, after about 3 seconds press volume down 3 times until the top left says '--> Fastboot' then press volume up.
Now run the following from command prompt:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lockThis will wipe all data on the Xoom, and hopefully reset it to stock.
Finally, run:
fastboot rebootand you should boot into Android 3.2(?), fingers crossed.
If you require further clarification or help let me know.
Click to expand...
Click to collapse
Thanks for the info, sadly I have done almost all that, I can´t use adb commands because I never allowed the tablet to do USB Debbuging, since I wasn´t doing anything that needed that and never thought I would need it. I think I didn´t kept the tablet connected to the PC, so I will try again and let you know if it works.
Like I said before, I'm unsure whether it'll work as I'm not an expert.
However, you may find this helps:
Whilst in recovery and connected to your PC, open Device Manager, find your Xoom, usually under 'Other devices'.
Then right click on your Xoom > Update driver software... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Pick your Xoom (either one if there's two shown)
Windows should confirm the driver installed then adb should work in recovery.
I believe ClockworkMod Recovery enables USB debugging anyway, through modifying default.prop
I'd recommend trying the above, and/or if that fails for any reason download Motorola USB Drivers here.
Thanks again but nothing works, I tried rebooting being connected to the PC and the same thing happens, the default recovery from the Xoom stays there, fastboot shows on the command Prompt and in the tablet that everything went ok and the new image was flashed but the rebooting kills it, and I can´t use any ADB commands because of the stupid USB Debugging, if something like this can happen, Motorola should have left it open from default or at least have a fail safe in case something like this could happen. RDS also flashes an image but when it rebbots the whole thing goes to hell, it stays on the damn logo with the same images. I think I can throw the tablet to the trash :crying:
Unless its a serious hardware issue, I wouldn't trash it! It clearly has life as you're able to successfully flash and such.
I'd recommend having a look at the FAQ.
alecbond said:
Unless its a serious hardware issue, I wouldn't trash it! It clearly has life as you're able to successfully flash and such.
I'd recommend having a look at the FAQ.
Click to expand...
Click to collapse
Thanks, but I have done everything, what is the good thing of a successful flash when the tablet returns to it´s previous state as soon as it reboots?
Plus I can´t use one of the most important things, adb, because of the usb debugging, I can´t get into the tablet to activated it, and even if there are recoveries which bypass this thing, I can´t flash them into the tablet, well I can, they just aren´t there after the reboot. And all this because the tablet run out of battery :crying:
ClockworkMod recovery itself allows the use of adb regardless of USB debugging setting.
I believe the command adb remount should allow it.
If adb is denied you can try what I said earlier
Whilst in recovery and connected to your PC, open Device Manager, find your Xoom, usually under 'Other devices'.
Then right click on your Xoom > Update driver software... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Pick your Xoom (either one if there's two shown)
Windows should confirm the driver installed then adb should work in recovery.
Click to expand...
Click to collapse
alecbond said:
ClockworkMod recovery itself allows the use of adb regardless of USB debugging setting.
I believe the command adb remount should allow it.
If adb is denied you can try what I said earlier
Click to expand...
Click to collapse
The problem lies with the recovery, I only have the default recovery from the xoom, it doesn´t matter how many times I flash it and everything seems to work correctly, when I restart the tablet I get the default recovery. I don´t understand why this happens, command prompt and the tablet in fastboot mode tell me the recovery has been flashed, but to use it I have to reboot and when I do I always find the same good for nothing recovery.
recovery
Hello,
I don't really understand your problem with the recovery ?
When you flash a custom recovery with fast boot, you restart the tab and after 2 or 3 second you see the Motorola Logo you push the volume down
and volume up button to enter in the new recovery.
If you flash custom recovery but restart completely the TAB without manually enter in the custom recovery, each time you retrieve the original recovery.
pots22 said:
Hello,
I don't really understand your problem with the recovery ?
When you flash a custom recovery with fast boot, you restart the tab and after 2 or 3 second you see the Motorola Logo you push the volume down
and volume up button to enter in the new recovery.
If you flash custom recovery but restart completely the TAB without manually enter in the custom recovery, each time you retrieve the original recovery.
Click to expand...
Click to collapse
Here is what happens, I flash new recovery, I restart the xoom with power and volume up, when the logo appears, after 3 seconds, I push volume down, recovery option shows, I press volume up and the default recovery is still there, not the new one I just flashed.
Is really no one out there that can help? :crying:
There's nowhere stated that, however I believe you already have unlocked your bootloader, didn't you? Because it's REALLY weird that it can't flash the recovery, I mean, you left the battery run out, then after charging you wasn't able to boot normally again.
I'll think a little, but give a check if your bootloader is really unlocked, the device should have installed the recovery, and as you didn't restart it entirely (let it go after the dual core logo), the recovery should be there...
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
I have done the fastboot oem unlock command, should I do it everytime? I can´t use adb, because like I said, I never check the USB Debugging, which I have done in my other tablet now, don´t want the same thing to happen twice.
is it dead?
hgokuh said:
is it dead?
Click to expand...
Click to collapse
I unfortunately believe that yes, however I'm still thinking about it! So don't give up! As soon as I have another answer I shall post something
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD