Database Info

[Q] Nexus s Stuck at fastboot OEM UNlock

My Nexus s is stuck at GOOGLE LOGO
Here is the Boot Loader Details.
Boot Loader version is : I9020XXKA3
baseband : I9020XXKB1
Locked sTate : LOCKEd
I have downloaded the stock nandroid , but not able to put it on the phone memory.
then tried to unlock the BOOT Loader in order to install Clock..Recovery , but there also after selecting Yes while Running Fastboot oem unlock , phone does not do anything.
then tried to load the file using ADB mode, but when i run adb devices , it doesnt show any device. or when i run adb remount it says "Error device not found"
Please help me get out of it.....

The order to unlock bootloader is:
download all drivers for nxs
download sdk tools
unzip sdk tools on your hdd
start a cmd prompt
navigate to the /tools folder inside sdk (if some adb files are missing get them here, they go into the /tools folder)
connect nxs via usb (enable usb debugging)
type "adb devices" in cmd (should return the device number)
type "adb reload bootloader"
after phone rebooted into fastboot mode type "fastboot oem unlock"
[without the ""s and install drivers if needed]

when i run adb devices it just shows this as shown below.. it doesnt give device serial number,although when i type adb remount it says device not found.
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
running ADB reboot says "Device not found"
although i can see in device manager as "android bootloader interface"
moreover when i run fastboot devices
it does show me my device serial number.
JUST to Emphasize I Am not able to start the phone so cant enable usb Debugging

Did you install the PDAnet drivers? I don't think your PC detects your phone correctly for this to work.
Install those drivers, hook the NS up to your PC and boot into bootloader. Running the adb and fastboot commands should work then.
Greetz

I did try try to install pdanet but it also fails eventually , and installation aborts .
I wonder when fastboot mode is detecting right it does display the interactive screen for unlocking boot loader on my phone .then could it still be driver issue
Can you confirm if adb needs "USB DEbugging enabled" which i can't do as mentioned

Yes you need USB debugging for adb
Sent from my Nexus S using Tapatalk

is there a way to enable usb debugging without phone getting started.

justsahid said:
is there a way to enable usb debugging without phone getting started.
Click to expand...
Click to collapse
If fastboot devices showed your serial number, you should be fine. Adb is for when android is up and running. You can mount the sdcard in recovery to copy the image files over for nandroid. If that doesn't work you can always flash in fastboot.

Yes but I am with Stock Recovery ,
IN order to mount SD card I need Clock work recovery and clock work recovery needs UNlocked Boot Loader
SO when I run the COmmand "Fastboot OEM Unlock"
My phone shows me one screen to choose Yes or NO
then I choose "YES" and hit the power button to unlock but then it stays there forever and never Unlocks the Boot Loader.

justsahid said:
Yes but I am with Stock Recovery ,
IN order to mount SD card I need Clock work recovery and clock work recovery needs UNlocked Boot Loader
SO when I run the COmmand "Fastboot OEM Unlock"
My phone shows me one screen to choose Yes or NO
then I choose "YES" and hit the power button to unlock but then it stays there forever and never Unlocks the Boot Loader.
Click to expand...
Click to collapse
If you do Fastboot OEM Unlock and then you wait for a while, and pull the battery, then put it back in and hold volume up + power and go back into bootloader mode, does it say LOCKED or UNLOCKED?

I waited for around 15 mins and then pulled out the battery , and then again went to boot loader it still says LOCKED.
IS it possible to execute Nandorid.zip using fastbot mode ?

Use Odin?
Sent from my Nexus S using XDA App

justsahid said:
I waited for around 15 mins and then pulled out the battery , and then again went to boot loader it still says LOCKED.
IS it possible to execute Nandorid.zip using fastbot mode ?
Click to expand...
Click to collapse
Exactly what all did you do before you tried fastboot oem unlock?

I opened the boot loader and run the command Fastboot Devices it did show me my device
then i run fastboot oem unlock , with which my phone showed up one screen confirming boot loader unlock where i chose "Yes" and hit the power button
i waited for 15 mins , tried multiple times and waited even more than an hour
nothing happens in the cmd promt neither on the phone.

Maximilian Mary said:
If fastboot devices showed your serial number, you should be fine. Adb is for when android is up and running. You can mount the sdcard in recovery to copy the image files over for nandroid. If that doesn't work you can always flash in fastboot.
Click to expand...
Click to collapse
Please help me how can i flash using fastboot I tried Fastboot update update.zip(2.3.3 official update)
it gave me following error
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt

Justsahid - I'm in the exact same predicament as you (as of this morning). I'm still trying to figure out how to get the phone to unlock. I noticed there isn't any post regarding success or if you still have this issue
To all:
When trying to wipe data/factory reset in the recovery mode I receive the following error message:
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/blockplatform/s3c-sdhci.0/by-name/userdata
Formating Cache...
Data wipe complete
Then when I go and try to "apply update from /sdcard" is shows this message:
E:failed to mount /sdcard
I just wanted to know if those messages would indicate that the "Internal memory" is inaccessible and that all attempts to fix this issue is futile. Keep in mind, I'm also getting the same error message as Justsahid when trying to fastboot the update.
Eskaycee

Eskaycee said:
Justsahid - I'm in the exact same predicament as you (as of this morning). I'm still trying to figure out how to get the phone to unlock. I noticed there isn't any post regarding success or if you still have this issue
To all:
When trying to wipe data/factory reset in the recovery mode I receive the following error message:
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/blockplatform/s3c-sdhci.0/by-name/userdata
Formating Cache...
Data wipe complete
Then when I go and try to "apply update from /sdcard" is shows this message:
E:failed to mount /sdcard
I just wanted to know if those messages would indicate that the "Internal memory" is inaccessible and that all attempts to fix this issue is futile. Keep in mind, I'm also getting the same error message as Justsahid when trying to fastboot the update.
Eskaycee
Click to expand...
Click to collapse
I tried everything with no success...then finly I sent the phone go samsung ..as per them there was some electrical part malfunctionining so they replaced it... I hope I will get my phone back by Tuesday

Wow. That's good to know. Thanks for sharing.
Sent from my Nexus S 4G using XDA App

Time for a odin flash

I waiting????????????????????

Phone Stuck on Cyanogen Logo

I was charging my phone when I noticed it restarted itself and then now it's stuck on the Cyanogen Logo screen.
I've gone into Recovery, pressed wipe data/factory reset but nothing actually happens. A bunch of stuff shows up saying
E:failed to mount / cache (Invalid argument)
E:Can't mount / cache / recovery /last install
E: can't open /cache recovery/last install
I tried pressing wipe cache partition, same thing
I pressed wipe media, same thing.
Reboot to bootloader, it just stuck on Fastboot logo.
I havn't done anything to the phone such as rooting or unlocking bootloader. I just left the phone as it is and only did system updates provided by Cyanogen.
Any idea?

megamonkey said:
I was charging my phone when I noticed it restarted itself and then now it's stuck on the Cyanogen Logo screen.
I've gone into Recovery, pressed wipe data/factory reset but nothing actually happens. A bunch of stuff shows up saying
E:failed to mount / cache (Invalid argument)
E:Can't mount / cache / recovery /last install
E: can't open /cache recovery/last install
I tried pressing wipe cache partition, same thing
I pressed wipe media, same thing.
Reboot to bootloader, it just stuck on Fastboot logo.
I havn't done anything to the phone such as rooting or unlocking bootloader. I just left the phone as it is and only did system updates provided by Cyanogen.
Any idea?
Click to expand...
Click to collapse
You probably have a corrupt persist partition. Download this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/view?usp=docslist_api
You'll need to unlock your bootloader, which will wipe your device, but it's the only way. I have a guide here that explains how to unlock it (also how to install adb/fastboot and the drivers). Once you've unlocked your bootloader, put the persist file in your fastboot folder, open a command prompt from within your fastboot folder (shift + right click, then select open command prompt here), and issue these commands:
Code:
fastboot erase persist
fastboot flash persist persist.img
Once it's done flashing you can try rebooting your phone. If it still doesn't boot you'll have to go back to my guide and follow the instructions in section 8 to flash the stock images.

There's no way of saving my photos is there? I assume no...but might as well ask.
Thanks so much for the help!

megamonkey said:
There's no way of saving my photos is there? I assume no...but might as well ask.
Thanks so much for the help!
Click to expand...
Click to collapse
Unfortunately not if you can't boot into the OS.

I typed: fastboot oem unlock
It says OKAY
So when I type: fastboot oem device-info
<bootloader> Device tampered:true
<bootloader> Device unocked: false
<bootloader> Charger screen enabled: false
I assume something went wrong?

megamonkey said:
I typed: fastboot oem unlock
It says OKAY
So when I type: fastboot oem device-info
<bootloader> Device tampered:true
<bootloader> Device unocked: false
<bootloader> Charger screen enabled: false
I assume something went wrong?
Click to expand...
Click to collapse
Yeah, this happens sometimes. I can only suggest you try again in the hope that it works, without the bootloader unlocked there's gonna be nothing you can really do.

So I keep typing it till it shows true for "Device unlocked"?
I typed it 4 times now....it still doesn't say Device Unlocked True...

megamonkey said:
So I keep typing it till it shows true for "Device unlocked"?
I typed it 4 times now....it still doesn't say Device Unlocked True...
Click to expand...
Click to collapse
It isn't going to work. You're only other option is to try this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
I know you're not hard-bricked but this is likely your only chance to get the phone working again.

Heisenberg said:
It isn't going to work. You're only other option is to try this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
I know you're not hard-bricked but this is likely your only chance to get the phone working again.
Click to expand...
Click to collapse
I'll try doing all over again one last time. But I was reading the guide you gave me, it says it won't work on soft-brick, will it still work tho?

megamonkey said:
I'll try doing all over again one last time. But I was reading the guide you gave me, it says it won't work on soft-brick, will it still work tho?
Click to expand...
Click to collapse
I'm pretty sure others in similar situations to you have used it, I could be wrong.

Heisenberg said:
I'm pretty sure others in similar situations to you have used it, I could be wrong.
Click to expand...
Click to collapse
I tried using the method but I'm not sure why it isn't working. I ran the program and it gave me a few problems letting me know what's wrong with my phone:
userdata_64G.img: FAILED
boot.img: FAILED
persist.img: FAILED
recovery.img: FAILED
system.img: FAILED
I'm running near the end where nothing is going my way and I may need to either ask someone to attempt to fix it or buy a new phone...

nexus 5 softbrick

Hey,
Hopefully you guys can give me some help with the problem ive been having,
My nexus 5 is stuck in bootloop, i can get into the bootloader and the lockstate is unlocked but no custom recovery is appearing like it used to. I tried flashing using ADB but my phone doesn't show up as a device on my pc.
i have tried to wipe the cache ect and it comes up with "E:failed to mount /cache (invalid argument)
I only really know the basics of this stuff (only ever used the basic stuff to root and flash my phone)

You must use fastboot commands while being into the bootloader, not adb.

mworley1991 said:
Hey,
Hopefully you guys can give me some help with the problem ive been having,
My nexus 5 is stuck in bootloop, i can get into the bootloader and the lockstate is unlocked but no custom recovery is appearing like it used to. I tried flashing using ADB but my phone doesn't show up as a device on my pc.
i have tried to wipe the cache ect and it comes up with "E:failed to mount /cache (invalid argument)
I only really know the basics of this stuff (only ever used the basic stuff to root and flash my phone)
Click to expand...
Click to collapse
Yeah, exactly what primokorn says...
Primokorn said:
You must use fastboot commands while being into the bootloader, not adb.
Click to expand...
Click to collapse
If you use the command "fastboot devices" and your phone with a code appears in the command prompt then there's no problem with your drivers.
Just reflash the factory image, you can use the automatic process if you run "flash all". You can also flash the images manually but if you go for that option make sure you don't forget to flash the cache image, that will fix your problem with mounting the cache partition.

ADB commands are used when the phone is booted into the ROM.
Flash the latest stock ROM from here to see if it solves the issue: https://developers.google.com/android/nexus/images
If the phone still bootloops, flash the userdata.img in fastboot. After flashing the userdata.img file in fastboot, boot directly into stock recovery using the power/volume buttons, perform a factory wipe, and reboot.

FAILED (Remote: GPT command failed) Zenfone 2 Ze550ml

So i have a zenfone 2 ze550ml that is stuck on asus logo. I have tried :
1) Entering recovery mode and saw the dead android logo with a “error!” Text.
2) “power+volume up” trick to enter recovery mode (didn’t work)
3)fastboot erase cache
4)adb sideload “zip file”
5)Asus Flash Tool
6)fastboot with system splashscreen droidboot img’s ( sucessful but still stuck on logo)
7)xFTSK was successful (but phone still stuck on logo)(not the 5 0’s)
8) all the fastboot command was a success, except the oem command
9) uninstall all the programs necessary, and install it again
10) use other devices to try (still doesn’t work)
When i was searching online i still couldn’t understand:
1 ) A problem with “fastboot oem partition /tmp/partition.tbl” the error command was "FAILED (remote: GPT command failed)"
2) unlocking the bootloader “unroot” with fastboot (could it be open through fastboot?)
3) how to use the TWRP (can’t understand)
I found a simillar thread : http://https://forum.xda-developers.com/general/help/asus-zenfone-a601cg-fastboot-removing-t3630569#post75658798
I have read :
http://https://forum.xda-developers.com/zenfone2/general/unbrick-vid-tutorial-restore-serial-t3411064/page1
All the 18 page and asked there
https://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455/page1
All the 48 page and ask there
What i’ve discovered
1) the problem is with the software not hardware
2)if you don’t have a loading under the “asus in search of incredible” that means the main board is broken. Reason: heat, to much flashing, etc
Conclusion:
1)change the main component(really really expensive)
2)change it if you get gpt error
I subscribed and ask to the threds, still got no reply. I want to know what the command is for and how to solve it.
Ps. I’ve flash this phone numerous times this is the first this ever happened.
And i ask someone at asus service center about it. Hope this will ease someone stress.

Moto G XT1033 - SDCARD read only

Hi all,
Last week my MOTO G gone... It was locked in Motorola screen. I let it discharger 0% so many times last week.
My device was bootloader locked, with no USB debugging.
Ok, i search a lot and found some information. I used the bellow link:
https://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492/
I ran bootloader and try recovery option, but got "Boot up failed message"
I did the some steps: unlock bootloader and then I tried flash a rom in fastboot. No error message returns, but the device always stay in unlocked bottloader screen. I used XT1033 5.02, 5.1 roms but without success.
Then... Tried command:
mfastboot flash recovery twrp-3.2.1-0-falcon.img
But when I reboot phone and entered recovery, got "no command" error.
Following my link guide above, I tried the command:
mfastboot boot twrp-3.2.1-0-falcon.img
And success! I finally could enter in TWRP and backup all my data. Good!
But my sdcard is appearing as read only!
I tried:
WIPE option (Wipes Data, Cache and Dalvik),
Advanced WIPE option (the partitions before and Data and Internal Storage ),
and Format Data option - No success
I did all the steps with partition Data mounted and repeated it again unmounted, booting the device in each try.
I tried the option Repair or Change File System (/data is F2fs) and tried to change the partition to EXT4 - no success.
I tried the same commands described in page 7:
https://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492/page7
and got the same results - no success.
I tried to use PUSH command, but it returns error failed to copy <filename> - read only file system.
Please, could you help me? Thanks in advance.

Your phone's eMMC chip probably died. You have no choice but to do a motherboard replacement. Or get just the chip replaced, but it's risky, since it involves resoldering and reballing BGAs.
Those frequent full discharges killed the chip, I suspect.
Since you've got your data backed up, I suggest you try either of these options.