Related
I tried doing 3button recovery but couldn't get in. I can get in downloading mode every time though. When I try to flash back to stock, Odin gets stuck on the "sbl.bin" step? I have tried multiple times with the same result. Any advice would be greatly appreciated. Thanks
wow, you don't eeven realize how lucky you have been thus far. sbl.bin is the secondary bootloader, it must be freezing RIGHT AFTER its flashed because if it hung DURING its flash that would have bricked. and i mean bricked, as in power button does nothing and your only option would have been jtag. but since you are still able to get into download mode first swap usb ports(one on the back of the pc no hubs, if its already in the back switch to another one) and restart your computer then use this package http://forum.xda-developers.com/showthread.php?t=995143 this doesnt conatin any bootloaders so if it fails you cant brick the worst you will get is the "phone....!....pc" screen in which case just boot into download mode, swap ports again and keep trying until it succeeds.
I bought a Nexus S from craigslist last night and it was out of juice. The seller was like oh bring it back if it doesnt work and I fell for it! I have the box/manuals/charger and everything so the phone was not stolen. When I put it on charge and turned it on this morning all that comes on the screen is google and a unlocked padlock on it. I thought that I can restore it. Went to the recovery mode by pressing volume up an power switch and tried reboot/recover and power off and they all lead to the same screen. volume down and power leads to nothing. So I called the seller and his phone keeps saying its disconnected. I realize I should have been more careful.
Now I am wondering if there is a way to restore the phone as I think that the seller messed up trying to mod the phone and there is no OS on the phone. Does anyone know how to fix this problem? I tried installing various recoveries and nothing seems to work since I cannot get super user to load nor can I boot up the phone to the OS. Please help a noob!
What is that "same screen" you are talking about? If it's the Droid with a "!" then you have to press vol up + power again to activate stock recovery.
Since you can access fastboot you should be able to flash a new recovery with adb.
Download the cwm recovery image, put it in /tools folder, run adb in cmd prompt, command is "fastboot flash recovery <recoveryimagename>.img", after that you can mount the internal storage via cwm recovery, copy any rom you like onto it, then "install from zip". I'd also format all parts of the phone once (mount and storage) and wipe dalvik cache (wipe) before you flash the new rom.
If it all doesn't help put the phone into download mode (vol up + vol down and then plug in usb cable while holding those two buttons), samfirmware.com has files (Odin) for the i9020 and i9023 (not NS4G yet).
In case your pc/laptop misses USB drivers you can find a guide on how to install adb and the drivers on unlockr.com.
even easier then that, just download the one click root (the gsm version for gsm or the ns4g one for cdma). turn the phone off then boot it back up by holding volume up and power. this will get you into fastboot, from there run the one clicks until it starts to do stuff to your phone, you may need to boot into fastboot mode again at some point. but it will get you a custom recovery loaded up from there you can download a custom rom and flash it in recovery and have a fully working phone
sounds liek the guy tried to root it and messed up something so he sold it privatly seeing as he couldnt figure it out. his loss is now your gain
the phone as you describe it is fully recoverable (dont use odin as its rather risky if you dont know what to do with it, not when you have things like fastboot or recovery mode)
mitrals said:
So I called the seller and his phone keeps saying its disconnected. I realize I should have been more careful.
Click to expand...
Click to collapse
If you were interested in getting in touch with the seller, try calling that number from another phone. You have been Google Voice blocked.
However, your issue is easily fixed I think and this shouldn't be needed.
rentaric: It keeps going back to the screen that says Google and has a unlocked padlock at the bottom center. I tried doing the recovery by the following link: http://forum.xda-developers.com/showthread.php?t=1007782 (The phone is unlocked as it states in Lock State-Unlocked). I was able to finish part 3 as well. In part 4 I get stuck at step #8, where pressing recovery gets me back to Google and unlocked padlock screen. I repeated the procedure multiple times and always get stuck at part 4 step 8. I am trying to get samfirmware going after I try one click root. Will post results.
shabbypenguin: I will download one click root and see where that takes me. I also think there might be some water damage to the phone as the strip on the phone is red and at times buttons dont work.
t1n0m3n: I called the seller from 5 different numbers (US and Canada numbers) and it says the line is disconnected for all numbers. I think he disconnected his phone.
Other notes: Phone looks in great condition so if I can get it running it would be awesome. I paid $250 for it thinking its a great price if the phone worked. Attached is the picture of what the phone does on start up.
are you sure you were able to flash the recovery correctly? does the md5 match? maybe try re-downloading the file?
fastboot flash recovery recovery.img
make sure you are using the recovery specific to your device (NS, NS4G)
Where do I find the MD5?
Here is what the phone says on the bootloader mode:
FASTBOOT MODE
PRODUCT NAME - HERRING
HW VERSION - REV 16
BOOTLOADER VERSION - I9020XXKA3
BASEBAND VERSION - I9020UCKD1
CARRIER INFO - ATT
SERIAL NUMBER - 31310A98550B00EC
LOCK STATE - UNLOCKED
And the rest..
Please let me know if anyone can help! Thank you
Are you rebooting the phone after installing the custom recovery (part 3, step 5)?
If yes, skip the rebooting part and go directly into recovery from bootloader screen. In case it works you can continue to mount the usb storage, copy a ROM on your sdcard, unmount, then go back to "Install from zip" after doing all 3 wipes available in "wipe" menu.
If no, then I have no further ideas then using Odin.
Same issue for me, maybe this phone got the NAND Flash problem. Warm it up then try to turn on your Nexus, it worked for me but I sent my Nexus last week to Samsung for repair.
There is a thread in Google Mobile Help Forum (google.com) in Help forum > Google Mobile > Android Devices > Android Applications (not listed above)
Sorry but i can't post the link.
Regards.
I am having the same exact problem with my phone. The only difference is that my Nexus is a sprint phone. Were you able to get your phone working and how did you do it?
---------- Post added at 05:27 PM ---------- Previous post was at 05:15 PM ----------
Im having the same problem with my phone. I have a nexus s and I think I need to flash [RECOVERY] clockwork because it says "fastboot mode - No boot or recovery img." Im using a mac but I cant seem to get it working. Can someone help me. I cant seem to figure out what to do and where to start.
Greetings! First of all, I would like to thank anyone who takes the time to help me diagnose and resolve this issues, let alone anyone who takes the time to read this thread.
I've been having issues with my Xoom (ICS 4.0.0) for about 3 weeks now.
A brief history of the issue's occurrence:
-I unrooted the device and returned it to stock.
-Everything was fine and dandy until one day it spontaneously said something along the lines of 'Android is upgrading..', and then performed a reset.
-Since resetting, it bootloops.
The device only turns on when plugged into a charger and hard reset.
The device only turns off when allowed to boot loop for minutes and then hard reset (it simply does not reset, and just turns off).
I'm not the most technically-savvy person with android devices but here are some things I've done/noted.
When trying to use adb commands, it does not recognize the device or properly issue commands.
I've tried wiping data/clearing cache to no avail.
EDIT: I've tried fastbooting, but the bootloader will not unlock. When trying to unlock, it simply resets and then acts as though it was never unlocked.
I have no idea how to return it to a stock image. All I know is that I have a micro-SD and some spare time.
Could anyone help me understand what exactly is going on with my Xoom?
If I can provide you with any more information, please let me know.
Thanks again. (=
If it was stock and spontaneously upgraded it sounds like a bad OTA upgrade. I've been rooted from the start so never have taken an OTA upgrade...don't you need to accept it or can it just upgrade on it's own?
Anyway, can you get it into fastboot mode?
Volume up and power, then at dual core screen, press volume down...if you see something like "entering fastboot mode" you're not bricked. You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
If you haven't done so, just google 'recovering Xoom using fastboot' and you should get some good information.
Good luck!
Remember to grab the MZ604 files if you have the Wifi only version of the Xoom.
http://developer.motorola.com/products/software/ <------ Grab the files here. The files are for the US version of the Wifi Xoom only.
Instructions to return it to stock
1) First you need the Moto Drivers - Read this thread to START you - http://forum.xda-developers.com/showthread.php?t=981578
Should have these drivers installed if you have rooted your Xoom before.
2) Make sure you have the latest SDK - adb and fastboot should be in /platform-tools -
http://developer.android.com/sdk/index.html
Should have the android SDK if you have rooted your Xoom before.
3) Place all the downloaded stock image files into the SDK Tools folder.
4) If you are booting up from scratch, you can get the Xoom in fastboot mode by doing the following. Use command prompt to perform the rest of the steps
Hold VolDown and Power button will boot unit for fastboot mode
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 lock
If you Xoom is booted up already follow the commands below using command prompt to perform the steps
adb reboot bootloader <---- reboots the Xoom into fastboot mode.
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 lock
As Always If This Was Helpful Hit the Thanks!
Yeah, what Mjamocha said...
okantomi said:
Yeah, what Mjamocha said...
Click to expand...
Click to collapse
LOL Thanks.
okantomi said:
Anyway, can you get it into fastboot mode?
Click to expand...
Click to collapse
Yes, I can. But so far nothing has been successful in terms of fastboot commands.
okantomi said:
You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
Click to expand...
Click to collapse
When I try to execute fastboot commands such as 'fastboot flash boot boot.img'.. it says the following:
Device still locked. Device must be unlocked first. Failed to process command error(0x8)
Whenever I try to unlock the bootloader, it appears to be successful at first and then the device reboots. But it just reboots to a bootloop, and the bootloader still says its locked. Perhaps I made a mistake in communication. The bootloader is currently locked and will not unlock, as just described.
When I try to unlock it and it reboots, even if I access the fastboot menu right away, it still says the device is still locked.
Thoughts?
Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.
slacka-vt said:
Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.
Click to expand...
Click to collapse
Yes, I can get into android recovery. However, within a second of switching into recovery mode, the robot falls down and there appears to be a red triangle caution sign containing an exclamation point.
When trying to do a factory reset, it says all data is wiped (as normal). Upon rebooting, it continues to bootloop. So essentially the factory reset and cache clear options in the Android Recovery menu do not produce the expected results.
Pretty odd. I didn't mess with the Xoom at all prior to this issue.
Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.
slacka-vt said:
Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.
Click to expand...
Click to collapse
Yeah, just tried it to no avail. Thanks so much for your help anyway. (=
I'm not sure what to do now.
I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.
slacka-vt said:
I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.
Click to expand...
Click to collapse
I hear ya. I've tried 2 different cords and 3 different computers. I'm using a Mac (10.6.8) right now, but have used 2 PCs (Vista + 7).
Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?
slacka-vt said:
Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?
Click to expand...
Click to collapse
I got the 'device still locked' error. Weird, huh?
How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.
slacka-vt said:
How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.
Click to expand...
Click to collapse
Yeah I tried that. Won't lock or unlock successfully. Locking produces no difference, and unlocking produces the same 'device still locked' error. This is getting out of hand! Thanks so much for your advice. You think I should open it up?
I hate to be so persistently annoying about this, but could anyone possibly suggest a method of working around the locked bootloader?
Is there anything I can do with an SD card to remedy the device's stubborn foolery?
I think you should give it a try, I have bricked my xoom a few times and have always been able to flash the stock imagine to recover. You really have nothing to lose by pulling the battery pin just be careful.
Sent from my Xoom using xda premium
I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?
cherlamperter said:
I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?
Click to expand...
Click to collapse
I have looking for a utube how to guide but no luck, I just might make one for you so you will know what to expect. Give me a few and I will get back to ya.
Sent from my Xoom using xda premium
Let me start off by saying that I just got this phone and decided to install a custom recovery and rom on it. As I do with all my phones that allow me to do so. I got the phone with android 4.4.4 on it, rooted it with Kingroot, and proceeded to use the XZDualrecovery tool to install TWRP. After that was all done, I downloaded the Z5 Expierience Rom, and I'm going to take a long shot here and say that I must have majorly missed something. Because after flashing that Rom in TWRP, my phone will do next to nothing. All went fine with the install of the ROM itself. Wiped Dalvik/Cache before restart.
If i hold down the power button I get a single vibration and then the phone does nothing (Does not even turn on backlight). If I plug the phone into my computer the phone will start a sequence of Red (LED), Green (LED), Vibrate. It does this aobut once every second. I can access Fastboot if I hold the volume + button, the LED then goes solid blue and the phone stops the LED - Vibration sequence. The only problem I have, as far as just not being able to Flashtool it back to life is, not being able to get the phone to go into Flashmode. No matter what I do, the phone will not let me get it into Flashmode. Im sure there is a good reason for this, I am just not sure what it is.
I've been flashing Roms and Recoveries since G1 days. I'm usually pretty decent at figuring this kind of thing out, but this thing has got me puzzled. I clearly went terribly wrong somewhere here, hopefully someone who knows this phone much better than I can point me in the right direction and hopefully get my less than 10 hour phone working again.
P.S. - If the phone is plugged into the wallcharger is does something similar to when it is plugged into my computer, but instead of a Sequence of Red - Green - Vibrate, I just get a steady red blink folled by a vibration. The phone will continue to do so until unplugged from the charger.
All help is very appreaciated!
I'm having the same issue. Anyone with the fix would be appreciated
Not sure what to try at this point!
I've been looking non-stop in my free time for a fix for this thing, and no matter what I do I keep getting the same results. Not really sure where to go from here, I have tried Flashtool, Emma, and PC Compainion out of desperaity. I tried all three options on teo seperate computers (One Windows 10 and the other Windows 7.) I have also tried multiple cables. No matter what I do all this thing will do is blink at me and vibrate. Is this thing hard bricked? I read its close to impossible to hard brick one of these phones. I'm wiling to accept that I have if that is the case. Just would like an opinion from someone who has some knowledge with these.
Same here, someone plz help.
If is only a change of batery or the phone is dead completly, an the stop trying to revive it.
Thanks .
Nick1801 said:
Let me start off by saying that I just got this phone and decided to install a custom recovery and rom on it. As I do with all my phones that allow me to do so. I got the phone with android 4.4.4 on it, rooted it with Kingroot, and proceeded to use the XZDualrecovery tool to install TWRP. After that was all done, I downloaded the Z5 Expierience Rom, and I'm going to take a long shot here and say that I must have majorly missed something. Because after flashing that Rom in TWRP, my phone will do next to nothing. All went fine with the install of the ROM itself. Wiped Dalvik/Cache before restart.
If i hold down the power button I get a single vibration and then the phone does nothing (Does not even turn on backlight). If I plug the phone into my computer the phone will start a sequence of Red (LED), Green (LED), Vibrate. It does this aobut once every second. I can access Fastboot if I hold the volume + button, the LED then goes solid blue and the phone stops the LED - Vibration sequence. The only problem I have, as far as just not being able to Flashtool it back to life is, not being able to get the phone to go into Flashmode. No matter what I do, the phone will not let me get it into Flashmode. Im sure there is a good reason for this, I am just not sure what it is.
I've been flashing Roms and Recoveries since G1 days. I'm usually pretty decent at figuring this kind of thing out, but this thing has got me puzzled. I clearly went terribly wrong somewhere here, hopefully someone who knows this phone much better than I can point me in the right direction and hopefully get my less than 10 hour phone working again.
P.S. - If the phone is plugged into the wallcharger is does something similar to when it is plugged into my computer, but instead of a Sequence of Red - Green - Vibrate, I just get a steady red blink folled by a vibration. The phone will continue to do so until unplugged from the charger.
All help is very appreaciated![/QUOTE
!st question is did you flash the correct rom for your device?
If you can go to recovery, then try to flash another rom,
Or use adb/fastboot to try and flash recovery img and use fastboot to reboot recovery.
Alternatively you may have to flash a kernel relevant to your rom.
Click to expand...
Click to collapse
Try this and see if it helps.........
If your phone is unbranded, i.e. not locked to a carrier, download a any generic(customized) firmware for your device through Xperifirm and flash it through Flashtool. It will wipe all your data (excluding your microSD, of course) but you don't have any other choice. This is most probably unbrick it...... So, try it and all the best.:good:
EDIT: If you've tried it, then go for this. Luckily you've fastboot still working, right? So, go to fastboot mode and flash a recovery image through it. It may take a lot of time but if recovery works, you can install a stock based rom for your device and then go back to stock firmware through Xperifirm and Flashtool.....
The phone is a Verizon model. I've tried to unlock the bootloader using command prompt following the sony instructions, after recieving my unlock key. I am able to connect to the phone and all of the fastboot commands work until I try and run the one to actually unlock the bootlaoder. That says the it is "not allowed." I think that is because I never enabled OEM Unlocking in the developers menu though. Not sure if there is a stock kernel I should try an flash through fastboot. Or if there is a stock recovery file that is flashbable through fastboot with a locked bootloader. The phone is definetley working in fastboot and somehow still knows how to charge. Im pretty sure at this point the problem is that the phone has a custom rom on it but the bootloader is still locked. I cannot unlock the bootloader because I can't get in Android to enable the proper options. Have also tried Flashtool for unlock the bootloader, along with extracting kernel sins from a stock 4.4.4 and a stock 5.0.1 FTF and trying to flash them. Since the begining I have still seen no change in the phone behavior.
Nick1801 said:
The phone is a Verizon model. I've tried to unlock the bootloader using command prompt following the sony instructions, after recieving my unlock key. I am able to connect to the phone and all of the fastboot commands work until I try and run the one to actually unlock the bootlaoder. That says the it is "not allowed." I think that is because I never enabled OEM Unlocking in the developers menu though. Not sure if there is a stock kernel I should try an flash through fastboot. Or if there is a stock recovery file that is flashbable through fastboot with a locked bootloader. The phone is definetley working in fastboot and somehow still knows how to charge. Im pretty sure at this point the problem is that the phone has a custom rom on it but the bootloader is still locked. I cannot unlock the bootloader because I can't get in Android to enable the proper options. Have also tried Flashtool for unlock the bootloader, along with extracting kernel sins from a stock 4.4.4 and a stock 5.0.1 FTF and trying to flash them. Since the begining I have still seen no change in the phone behavior.
Click to expand...
Click to collapse
dude I'm from the Verizon side yea like you have an bootloader status unlock no so your not going to change that and you can only flash Verizon z3v stuff you are really lucky if you can still get to fastboot after doing this. Use flashtool and flash a Verizon ROM from the z3v section only and pray it works.
I was attempting a network unlock on this device (not frp) as i actually own this phone. i managed to get the combination file flashed through odin and i obtained a network unlock code that worked just fine. i cannot get the device to boot into download mode for the life of me. i can get the device into recovery but not sure where to go from there. i've tried everything. i have the proper firmware downloaded but i can't flash it. odin picks up the device after it has booted into the combination binary. and upon selecting download mode or upload mode from within the UI it asks for a pin then does nothing. i tried straight talk and samsung technical support and they were absolutely no help. please help.
me too
oi0i0io said:
I was attempting a network unlock on this device (not frp) as i actually own this phone. i managed to get the combination file flashed through odin and i obtained a network unlock code that worked just fine. i cannot get the device to boot into download mode for the life of me. i can get the device into recovery but not sure where to go from there. i've tried everything. i have the proper firmware downloaded but i can't flash it. odin picks up the device after it has booted into the combination binary. and upon selecting download mode or upload mode from within the UI it asks for a pin then does nothing. i tried straight talk and samsung technical support and they were absolutely no help. please help.
Click to expand...
Click to collapse
I have been round and round with this device... I found that from recovery boot to bootloader takes it straight to download but not odin mode, phrase saying do not turn off target...wtf.. also at times, not always for some reason, holding ALL buttons to power up takes me in to dwnld mode... Im at the point I am willing to brick this unit just trying to get past frp.
this is running pie, im next goiung to attempt dwngrdng to 8.0 to try and bypass frp... It is my only available device and I am cvurrently without phone as apparently my moto e5 can not take stairs one at atime.. good luck.
remove sim...reboot to bootloader from recovery
sory, you prolly alreadt did this , im new here, just totally liking seeing someone elese hating the device atm... lol