Database Info

[Q] Nexus S not working...

I'm going to probably get a lot of hate for this because there are a ton of forums that might get me here. I did search for about 3 hours tonight and discovered some things but am still confused. I hope someone can help this be more simple. So a friend has a Nexus S that isn't working (I have a Nexus S by the by too). It's unlocked but no ClockWork on it. I can press volume up and power to get to fastboot mode. When I click on "reboot," the phone will just loop on the Google logo. If I click recovery, it starts to boot then shows the triangle with the exclamation mark. From there, I can press power and up or down on volume to get the blue screen which says reboot system now, apply update, wipe, wipe. You get it. I'm stuck...I can also turn off the phone, hold volume up/down and plug in the usb to get to "downloading..."
I want to get this phone working and back to stock. I have the SDK Manager (my phone isn't rooted so I use it to take screenshots) and pda net (which I still don't understand why or how to use with this) and two versions of Odin. It seems like Odin can get this working but I can't get it to work or find a clear guide on how to use it and which ones to use. This is a Tmob Nexus S, I think the i9020. Any help would be so greatly appreciated and I will give you all the credit. Oh, and i can pull up the device on ddms with the sdk manager and can explore the files but there is nothing. I can't find a way to drag a file on the phone to "apply update from /sdcard." Sorry again and thanks again!

callison.168 said:
I'm going to probably get a lot of hate for this because there are a ton of forums that might get me here. I did search for about 3 hours tonight and discovered some things but am still confused. I hope someone can help this be more simple. So a friend has a Nexus S that isn't working (I have a Nexus S by the by too). It's unlocked but no ClockWork on it. I can press volume up and power to get to fastboot mode. When I click on "reboot," the phone will just loop on the Google logo. If I click recovery, it starts to boot then shows the triangle with the exclamation mark. From there, I can press power and up or down on volume to get the blue screen which says reboot system now, apply update, wipe, wipe. You get it. I'm stuck...I can also turn off the phone, hold volume up/down and plug in the usb to get to "downloading..."
I want to get this phone working and back to stock. I have the SDK Manager (my phone isn't rooted so I use it to take screenshots) and pda net (which I still don't understand why or how to use with this) and two versions of Odin. It seems like Odin can get this working but I can't get it to work or find a clear guide on how to use it and which ones to use. This is a Tmob Nexus S, I think the i9020. Any help would be so greatly appreciated and I will give you all the credit. Oh, and i can pull up the device on ddms with the sdk manager and can explore the files but there is nothing. I can't find a way to drag a file on the phone to "apply update from /sdcard." Sorry again and thanks again!
Click to expand...
Click to collapse
It seems your boot.img file either corrupted or missing.
Find a working copy of file, flash it via ADB interface or fastboot. Flash recovery file CWM. If that doesnt work, Try flashing CM7 Rom or someother ROM.
Did you check http://forum.xda-developers.com/showthread.php?t=895545 ?
Odin should be your last resort, if nothing really works for you.
If you want to return to stock, simply flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 .
Disclaimer : I take no responsibility of what so ever happens to your phone, however you should be good if you follow proper steps.

Thanks so much for the quick reply. I think I've made some headway...I can "see" the device with cmd by typing adb devices. After that though, I don't understand how to get the stock nexus s rom on the phone. How do I move that file to my phone (what's the line of code I type)? I've tried "adb install <c:\grh78> but it says the syntax isn't correct. Any more help is so greatly appreciated and I appreciate the already prompt response. Thanks!!!

callison.168 said:
Thanks so much for the quick reply. I think I've made some headway...I can "see" the device with cmd by typing adb devices. After that though, I don't understand how to get the stock nexus s rom on the phone. How do I move that file to my phone (what's the line of code I type)? I've tried "adb install <c:\grh78> but it says the syntax isn't correct. Any more help is so greatly appreciated and I appreciate the already prompt response. Thanks!!!
Click to expand...
Click to collapse
Download your rom of choice (stock, custom)
Flash Cwm via fastboot if you haven't already
Boot into recovery.
Use adb push to push your zipped rom to the sdcard (adb push file.zip /sdcard/file.zip)
Use cwm to flash this zip.
Sent from my Nexus S using xda premium

callison.168 said:
Thanks so much for the quick reply. I think I've made some headway...I can "see" the device with cmd by typing adb devices. After that though, I don't understand how to get the stock nexus s rom on the phone. How do I move that file to my phone (what's the line of code I type)? I've tried "adb install <c:\grh78> but it says the syntax isn't correct. Any more help is so greatly appreciated and I appreciate the already prompt response. Thanks!!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=9866675
http://forum.xda-developers.com/showthread.php?t=884093
These threads should be a complete solution to your issue.
Disclaimer : I take no responsibility of what so ever happens to your phone, however you should be good if you follow proper steps.

Wow fast responses. I bet it's annoying to help yet another person having issues (again, phone was given to me like this but yeah...) while you guys or gals already know how to do these things very well. Here's where I'm stuck. I enter this code in cmd:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
and it just says < waiting for device >.
Here's a pic of the screen that I'm on with my phone when i enter the command.
http://imgur.com/Pey3W
If I'm just in the first screen by holding volume up and power, the computer won't read the phone. So I click recovery, the screen shows it's trying to install something then the triangle exclamation mark, i press volume up/down with power and get this screen and the computer can "see" my phone on cmd.
How do I get this flipping clockwork on this phone or get the stock image on my sd card? Thanks again for helping me out guys. I have taken a look at the links you have sent me and that's where i found the download as well as the code to enter. I will keep looking at them but if you find a faster solution, please let me know.

One more thing to be super clear on...when I'm on the screen on the Nexus S that says Fastboot Mode on top in red and Lock State - Unlocked...my computer won't read the phone, therefore I cannot fastboot the recovery img...

callison.168 said:
One more thing to be super clear on...when I'm on the screen on the Nexus S that says Fastboot Mode on top in red and Lock State - Unlocked...my computer won't read the phone, therefore I cannot fastboot the recovery img...
Click to expand...
Click to collapse
So you already tried "fastboot devices" while in fastboot mode?
Edit: Actually it sounds you really want stock so download the complete stock OTA ROM (including boot.img etc.), rename it to update.zip and put it on the root of your sdcard. Boot into the stock recovery like you did already and hit apply update.
EDIT: Go here to download the correct OTA http://forum.xda-developers.com/showthread.php?t=1056062
Find the correct 2.3.6 "Full ROM" for your phone model. Sounds like in those instructions you don't need to rename to update.zip. Haven't seen stock recovery for a while so I don't remember.
If there is a wipe option in the stock recovery then do that first.

Yes I have tried fastboot devices in fastboot mode but nothing because my computer doesn't read the phone in that mode. And yes, I want to put the stock rom on there but that's the key, I can't get access to the root of my sdcard. I can't push anything into the sdcard to flash it. Any ideas what to type or how to access the sdcard? Thanks a million, billion.

Also, I can't get the phone to boot at all, like I can't get passed the Google Logo if I reboot so I can't access the sdcard in the traditional way.

callison.168 said:
Yes I have tried fastboot devices in fastboot mode but nothing because my computer doesn't read the phone in that mode. And yes, I want to put the stock rom on there but that's the key, I can't get access to the root of my sdcard. I can't push anything into the sdcard to flash it. Any ideas what to type or how to access the sdcard? Thanks a million, billion.
Click to expand...
Click to collapse
Connect with adb and type this:
adb shell mount /sdcard
Then type:
adb push rom.zip /sdcard/update.zip

callison.168 said:
Yes I have tried fastboot devices in fastboot mode but nothing because my computer doesn't read the phone in that mode. And yes, I want to put the stock rom on there but that's the key, I can't get access to the root of my sdcard. I can't push anything into the sdcard to flash it. Any ideas what to type or how to access the sdcard? Thanks a million, billion.
Click to expand...
Click to collapse
If fastboot devices returns NOTHING then this is most likely a driver issue. Remove the device through device manager, make sure you have a recent SDK (for the USB driver) and let it re-detect.
callison.168 said:
Also, I can't get the phone to boot at all, like I can't turn on the phone so I can't access the sdcard in the traditional way.
Click to expand...
Click to collapse
If you can get into the boot loader and get a proper USB driver you should be able to flash a recovery.
Once you've flashed Clockwork Mod (recovery) you'll be able to push to the sdcard using ADB or possibly mount the sd card through the CWM menu (although I've yet to have that work).
In order to get a recovery flashed though you need to get fastboot to see your device (unless you can already boot into recovery, then just use ADB).

irishrally said:
Connect with adb and type this:
adb shell mount /sdcard
Then type:
adb push rom.zip /sdcard/update.zip
Click to expand...
Click to collapse
If he's stuck at the Google logo and has a trash boot.img it's not likely he'll be able to get a shell via ADB. Now, if the system is hanging starting a device or looping during boot then that's possible.

krohnjw said:
If he's stuck at the Google logo and has a trash boot.img it's not likely he'll be able to get a shell via ADB. Now, if the system is hanging starting a device or looping during boot then that's possible.
Click to expand...
Click to collapse
He said he can access stock recovery and has connected with adb, unless I read wrong.

irishrally said:
He said he can access stock recovery and has connected with adb, unless I read wrong.
Click to expand...
Click to collapse
Indeed - I saw no clockwork and figured he'd toasted his recovery image as well, but it does look like stock recovery is there. ADB should push fine to the sdcard from recovery then.

More...so if i type in adb reboot bootloader in the recovery screen, it does just that...great. But then my computer makes a noise, a double tap if you will...like a dun dun, like something didn't work. When you plug in something to the computer it usually goes like dun na...but the phone clearly won't read when I'm in bootloader/fastboot mode. So when I type a command, nothing will work...

callison.168 said:
More...so if i type in adb reboot bootloader in the recovery screen, it does just that...great. But then my computer makes a noise, a double tap if you will...like a dun dun, like something didn't work. When you plug in something to the computer it usually goes like dun na...but the phone clearly won't read when I'm in bootloader/fastboot mode. So when I type a command, nothing will work...
Click to expand...
Click to collapse
That noise is that it detects a device has been connected (assuming a recent version of windows). If you want to flash CWM you need to get the driver sorted for the device. No amount of plugging/unplugging is going to fix it.
If you have the stock recovery you can boot into the stock recovery, use adb to push the full OTA package to the sd card and then just flash that from the stock recovery.

callison.168 said:
More...so if i type in adb reboot bootloader in the recovery screen, it does just that...great. But then my computer makes a noise, a double tap if you will...like a dun dun, like something didn't work. When you plug in something to the computer it usually goes like dun na...but the phone clearly won't read when I'm in bootloader/fastboot mode. So when I type a command, nothing will work...
Click to expand...
Click to collapse
Go to the stock recovery like you have done before and type the adb command I wrote above.

Thanks is all I can say. Okay so when I type in the command, this is what I get:
- exec '/system/bin/sh' failed: No such file or directory (2) -
the "stock recovery" I can get into is the picture I posted a link for. That's what I can access as well as the fastboot mode when I first turn on the phone with volume up/power. But when my computer makes the noise that it's connected (using Windows 7 64bit) it makes a different sound then the normal "device connected." Like it's corrupted.

by the way...if we can get this working, I'll post a picture of me holding the fixed phone!

[Q] Nexus s 4g locked up

Okay, first of all I know, I'm a total noob. I have followed these forums a long time and have successfully rooted a few phones. One of which was my nexus s 4g. I was trying to unroot the phone so I could get ics. This is when I ran into problems and right now I just want to be able to get my phone working again. Right now I am stuck on the Miui boot up screen and no matter how long I wait it stays on that screen. If I do a battery pull and hold down power and vol up I can get into the bootloader screen with the information as follows: fastboot mode, product name-Herring, HW Version Rev 34, Bootloader version-D720SPAKE1, Baseband version-D720SPAKE1, Carrier info, SPR, serial number-37308B81276A00EC, Lock State-locked. Then the different options I can choose are reboot bootloader, reboot, recovery, power off. If I choose reboot, it takes me back to the mius screen and stays there. If I choose recovery, I get the triangle with the exclamation point. I then hold power and up volume again and I get a screen that says Android system recovery <3e> with reboot system now, apply update from sd card wipe data/factory reset and wipe cache partition. I have tried all of these as well with no luck. When I go to apply update from sd card I get matrix-cfs_v15.5 zip, root.zip, update.zip and then what looks like apps such as Alarms/, Android/,MIUI?, etc. If I try to select any of the first ones such as matrix-cfs_v15.5 zip, I get Install /sdcard... , finding update package..., opening update package..., verifying update package..., E.signature verification failed, Installation aborted. Then it gives me the system recovery options again. Any help would be appreciated.

Did you try ADB fastboot method?

Not sure how to try that

I tried doing the adb, followed all directions and installed and when I go to the command prompt and type in anything, such as, adb reboot bootloader I get, adb is not recognized as an internal or external command, operable program or batch file.

ok I got that working now but when I type adb devices and press enter I get a message saying List of devices attached and then it doesn't show anything and I get the command prompt again saying:c:\android\android-sdk\platform-tools>

also since the phone is stuck in either the miui screen or bootloader I can't get into it to put it in usb debugging mode. I am trying on my own to get this going and am stuck any and all help would be very much appreciated.

TerryUK98 said:
Lock State-locked.
Click to expand...
Click to collapse
I think that means you have a locked bootloader.
And from what you're telling, I believe you have stock recovery.
Also, when you're in fastboot mode, I don't think adb commands apply. Use fastboot commands instead (i.e. fastboot devices).
Search for guides showing you how to install and use fastboot.

I did fastboot as well and the problem I think I am having is it's not recognizing my phone because usb debugging wasn't turned on before it locked up. How would I get it to recognize my phone or download an img to my phone if it is not being recognized. Sorry if this is a stupid question.

You don't need usb debugging in fastboot mode.
You either:
1. Don't have drivers installed.
2. Don't have fastboot installed correctly.
You really need to read a guide or two, through and thoroughly.
Bc it sounds like you have no clues.

Yeah dude. Take a step back and go over what you have installed and where you installed it.Yes, fastboot commands start with fastboot instead of adb. And you're on stock recovery.

Thanks for the answer that I don't need usb debugging in fastboot mode, I wasn't sure of that. I have downloaded and installed my drivers multiple times and when I use the device manager to update drivers it says I have the latest drivers installed already. Whenever I do fastboot commands I will type in fastboot devices and shouldn't my device serial number come up? It just gives me the line c:\android\android-sdk\platform-tools>
And is waiting on me to type a command in. And yes I have been looking at guides all night. I appreciate any help you guys might have and remember we were all noobs at one time.

The zip in this tutorial should help.
It has adb, fastboot, and the drivers needed.
And unlock the bootloader because it is locked.

Finally got it, I had everything downloaded that I needed already, but looking at different forums, etc, it seemed like everyone named it something different. So I just used the one link you gave me and did it exactly the same way and it worked. Thanks so much! and again thanks for your patience.

[Q] Stuck at Boot/Starting Apps

Hey folks!
Again a problem with my little phone.
Today I got similar reboots, after about 5 it got stuck at the bootscreen.
Tried to wipe cache+dalvik, booting it up again, but after it prepared all apps it stucks at the "Starting Apps" window..
Also flashed another kernel and recovery. Nothing worked so far..
Any help, because I don't want to wipe data because I made some important photos today and I don't wanna miss then..
Thanks in advance,
RS

RestlessScreams said:
Hey folks!
Again a problem with my little phone.
Today I got similar reboots, after about 5 it got stuck at the bootscreen.
Tried to wipe cache+dalvik, booting it up again, but after it prepared all apps it stucks at the "Starting Apps" window..
Also flashed another kernel and recovery. Nothing worked so far..
Any help, because I don't want to wipe data because I made some important photos today and I don't wanna miss then..
Thanks in advance,
RS
Click to expand...
Click to collapse
First of all you connect your phone to PC and try to copy all the content of /sdcard to your PC. If it doesn't work reboot your phone to fastboot and connect it to your PC with CMD (in fastboot folder) running and enter the command "adb pull /sdcard C:/" without quotes, Also you can replace C:/ to any address where you would like to copy all your SD data.
After that you can flash any ROM to get your device in working condition.
If you have any query do ask or you may end up losing all your data.

forgotter said:
First of all you connect your phone to PC and try to copy all the content of /sdcard to your PC. If it doesn't work reboot your phone to fastboot and connect it to your PC with CMD (in fastboot folder) running and enter the command "adb pull /sdcard C:/" without quotes, Also you can replace C:/ to any address where you would like to copy all your SD data.
After that you can flash any ROM to get your device in working condition.
If you have any query do ask or you may end up losing all your data.
Click to expand...
Click to collapse
Thanks for your tips, but like I said it's stuck in bootloop and I can't access it through pc.
Also adb won't work an yes, I've installed all drivers :b

RestlessScreams said:
Thanks for your tips, but like I said it's stuck in bootloop and I can't access it through pc.
Also adb won't work an yes, I've installed all drivers :b
Click to expand...
Click to collapse
Why don't you try the fastboot method.
Put your phone into Fastboot by pressing volume down+power button. Connect it to your PC, fastboot would recognize it for sure. You then enter the command. You can even use adb from fastboot.

forgotter said:
Why don't you try the fastboot method.
Put your phone into Fastboot by pressing volume down+power button. Connect it to your PC, fastboot would recognize it for sure. You then enter the command. You can even use adb from fastboot.
Click to expand...
Click to collapse
It just says "device not found" when using adb.
with fastboot I can flash things but can't pull or?

RestlessScreams said:
It just says "device not found" when using adb.
with fastboot I can flash things but can't pull or?
Click to expand...
Click to collapse
Is your boot loader unlocked, if not you'll have to unlock it first (but doing so will void your warranty).
Assuming that you have a unlocked device follow the steps below to get all your data. (I myself tried and it worked, so it must work on your device also)
1. Make sure you have installed drivers for your Moto G, if not then do it.
2. Download the adb file to access your phone during fast boot.
3. Download the TWRP recovery 2.7.0.0 by dhacker for falcon (Moto G) on your PC and copy it in the adb folder.
4. Rename the downloaded file to "recovery.img" without quotes.
5. Connect you phone in fastboot mode to your PC and flash the recovery by command "fastboot flash recovery recovery. img" without quotes.
7. On your phone then go to recovery option and press volume up key until phone vibrates. The phone will then go to recovery mode.
8. On your PC, in command prompt(adb) enter command "adb pull /data/media/0/ C:\Moto" without quotes. The process will start and may take hours depending on no's of file and their size.
P.S. I won't be able to answer any more of your question as I won't have data connection any more. I'm sure if you will follow all the steps properly, you will get all your data. If you can't understand anything then just Google it.

Phone doesn't proceed from boot animation!
Guys!
This would be my 1st time here. I've never faced any sort of problem with any of my android devices but this one.
My phone got lost a week back. So, I used "android device manager" to wipe/lock the phone but I think it didn't as the phone was switched off all this while.
So, some gentleman found my phone and returned it to me just today. I put it up for charging. It popped up 0% battery screen and turned on after 10-15min.
As soon as the boot animation(earth/buildings) finished it jumped to a black screen.
It has been on charging for last 3 hours.
So my questions are
1) Can I make back up of the data without turning it on/formatting it?
2) How can I make it to work?
Thanks a lot in advance!

vjsharma89 said:
Guys!
This would be my 1st time here. I've never faced any sort of problem with any of my android devices but this one.
My phone got lost a week back. So, I used "android device manager" to wipe/lock the phone but I think it didn't as the phone was switched off all this while.
So, some gentleman found my phone and returned it to me just today. I put it up for charging. It popped up 0% battery screen and turned on after 10-15min.
As soon as the boot animation(earth/buildings) finished it jumped to a black screen.
It has been on charging for last 3 hours.
So my questions are
1) Can I make back up of the data without turning it on/formatting it?
2) How can I make it to work?
Thanks a lot in advance!
Click to expand...
Click to collapse
@vjsharma89 :I have posted the answer in your thread.
And after you had backuped your data, factory reset your phone from fastboot by choosing factory option and then reboot it. Or should work fine.

delete this pls, wrong thread

Is it possible to unlock bootloader by using an app on the device? + few other [Q]

Hello, i am still preparing my device for Lolly-pop flashing, and i am reading instructions everywhere on the web. I have a couple of questions i wanted to ask before i proceed doing anything else.
First one, one of the hardest things to do is unlocking the boot-loader i think. There are many different ways to do that, and everyone looks very complicated, so i have no idea how should i do that. Longest instructions are usually the safest but have the biggest chance of messing things up.
Anyhow, due to my device being rooted, i looked in Play Store for other options and found this app https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
Can i just use that to unlock my bootloader? And as far as i understand, it will wipe my data as soon as i do that right?
Second one, how do i make sure my USB drivers are working correctly? When i put my phone in bootloader mode and plug it in my Windows 7 laptop, it detects the device as some Bootloader device (cant remember exact name). So is that meant to be like that?
Third one, are there any other easy methods for simply unlocking and locking the bootloader that doenst need some SDK downloading?I have an old android app dev sdk in my pc, can i use that? Can that be done only using the .zip image provided by google?
And just to confirm, are these instructions i have made for myself , are they correct? Will that work?
1) Unlock bootloader using the rooted app from play store.
2)Download and extract the .zip file to a folder on my pc desktop.
3)Put the phone in the bootloader mode, vol-up+vol-down+pwr.
4)plug it in my pc
5)run the flash-all script from the folder on desktop
6)not sure what is supposed to happen now, but i assume the device is going to power on?
7)when the device starts, turn it off, go in bootloader mode, then in recovery and wipe data/factory and cache.
8)somehow lock the bootloader, i do not yet know how will i do this, any tips?
Also there are videos on youtube but most of them are <1 year old, using old instructions i think.

1) yes that app will unlock the bootloader. It needs root though. It does not wipe data. Only fastboot unlock method wipes data for security.
2) click the guides link in my signature. Read then "adb and fastboot. What is it?" Thread. This will tell you how to configure everything properly.
3) use the app in 1 of fastboot. See above, SDK not required.
4) unless you're rooted step 1 will be done with fastboot.
All the guides and info threads you'd ever need are in my signature

rootSU said:
1) yes that app will unlock the bootloader. It needs root though. It does not wipe data. Only fastboot unlock method wipes data for security.
2) click the guides link in my signature. Read then "adb and fastboot. What is it?" Thread. This will tell you how to configure everything properly.
3) use the app in 1 of fastboot. See above, SDK not required.
4) unless you're rooted step 1 will be done with fastboot.
All the guides and info threads you'd ever need are in my signature
Click to expand...
Click to collapse
Ok so i can unlock the bootloader with that app. But i will not be able to lock it again, because i will lose root access after the flashing right?
I tried searching the thread you mentioned, but i cant find it. I tried using both search engines, in google and in forum. And i dont think there is link to the thread in your signature. Could you send me a link please?
I do not understand the 3) 4) . To which question are you replying?
Sorry for the massive confusion
EDIT: I just found the thread, looks like a lot of useful information!

nikssims said:
Ok so i can unlock the bootloader with that app. But i will not be able to lock it again, because i will lose root access after the flashing right?
I tried searching the thread you mentioned, but i cant find it. I tried using both search engines, in google and in forum. And i dont think there is link to the thread in your signature. Could you send me a link please?
I do not understand the 3) 4) . To which question are you replying?
Sorry for the massive confusion
EDIT: I just found the thread, looks like a lot of useful information!
Click to expand...
Click to collapse
Are you rooted now? Do you have a custom recovery?

rootSU said:
Are you rooted now? Do you have a custom recovery?
Click to expand...
Click to collapse
I am rooted but i do not have custom recovery
Edit: Plus also while going through those instructions i downloaded an app on my pc that installed usb drivers, adb, and fastboot. http://forum.xda-developers.com/showthread.php?t=2588979
As far as i understand, i have no need to download the huge SDK thing.
Edit 2: I tried running the adb and fastboot without having anything plugged in my pc, and it opened a cmd and some lines appeared and it shut it self off. Is something messed up? I have a very old android app dev sdk in my pc somewhere, could that be conflicting in some way?

nikssims said:
I am rooted but i do not have custom recovery
Edit: Plus also while going through those instructions i downloaded an app on my pc that installed usb drivers, adb, and fastboot. http://forum.xda-developers.com/showthread.php?t=2588979
As far as i understand, i have no need to download the huge SDK thing.
Edit 2: I tried running the adb and fastboot without having anything plugged in my pc, and it opened a cmd and some lines appeared and it shut it self off. Is something messed up? I have a very old android app dev sdk in my pc somewhere, could that be conflicting in some way?
Click to expand...
Click to collapse
How did you "run" adb and fastboot?

rootSU said:
Are you rooted now? Do you have a custom recovery?
Click to expand...
Click to collapse
bump

nikssims said:
bump
Click to expand...
Click to collapse
Rather than bumping (which is againt the rules within 24 hours btw), why not simply answer my previous question?

rootSU said:
Rather than bumping (which is againt the rules within 24 hours btw), why not simply answer my previous question?
Click to expand...
Click to collapse
Oh sorry, i posted the bump at the same time as you did reply me. Sorry
rootSU said:
How did you "run" adb and fastboot?
Click to expand...
Click to collapse
I simply clicked on the .exe files just to see what happens. It might be meant to work like that, i don't know. I just didn't want to risk plugging in my phone just to test adb and fastboot things.
Also couple of questions about this
Code:
Method 1. Easy method.
★Power off your phone.
★Boot it in fastboot by pressing and holding Power Button + Volume Down at the same time.
★Connect your phone to your PC through your USB cable.
★Execute the flash-all.bat script (for Windows) or flash-all.sh(for MAC and LINUX) in the folder where you extracted the factory images.
**!!** For MAC: You'll have to edit the flash-all.sh, and add "./" before every fastboot command.
★Wait for everything to flash.
★After everything finished, select "Recovery" using the volume buttons.
★When a small dead Android appears, press Power Button + Volume UP.
★Select "Wipe data/factory data reset"
★Reboot. Your phone should be stock.
So, when L comes out, i simply extract it on my desktop, and run the flash-all.bat thing, while having my nexus connected to pc while in the "fastboot" mode?
Also, do i need to wipe only the data/factory or do i need to wipe the cache too?
And will the flash-all.bat lock my bootloader? Or is that even needed?
Edit: Reading other threads all around the internet gives so many different kinds of answers, that i do not understand what should i do. One site says that bootloader can be left unlocked, other says that it must be locked. Then there are thousands of different ways to lock it, and each one looks complicated.

nikssims said:
Oh sorry, i posted the bump at the same time as you did reply me. Sorry
I simply clicked on the .exe files just to see what happens. It might be meant to work like that, i don't know. I just didn't want to risk plugging in my phone just to test adb and fastboot things.
Click to expand...
Click to collapse
You should read my "adb and fastboot. What is it?" thread. That is not how you use adb or fastboot.
nikssims said:
So, when L comes out, i simply extract it on my desktop, and run the flash-all.bat thing, while having my nexus connected to pc while in the "fastboot" mode?
Click to expand...
Click to collapse
Correct. Or you can just fastboot flash the system and boot.img manually (again, see my thread)
nikssims said:
Also, do i need to wipe only the data/factory or do i need to wipe the cache too?
Click to expand...
Click to collapse
If you use the flash-all.bat, it will overwrite your data with a blank userdata.img
nikssims said:
and will the flash-all.bat lock my bootloader? Or is that even needed?
Click to expand...
Click to collapse
No.... And yes if you're not going to have a custom recovery on there, locking your bootloader secures the device - providing you have a Pattern or PIN lock.
nikssims said:
Reading other threads all around the internet gives so many different kinds of answers, that i do not understand what should i do. One site says that bootloader can be left unlocked, other says that it must be locked. Then there are thousands of different ways to lock it, and each one looks complicated.
Click to expand...
Click to collapse
If you're going to be rooted, you can simply lock it with the app you mentioned in your first post. Or using fastboot. Try to avoid threads all over the internet. Everything you need is here on XDA.

Ok, that seems to be it for now. Now i will wait for the release of android L image, which seems to have been delayed untill 12 nov.
Thank you for your support!

Unlocking the bootloader is VERY easy. All you must do is have either the entire have android SDK installed, or you just need the platform tools(adb and fastboot). Once you have those, you either navigate to the folder where adb/fastboot is -or- add them to your path variable. Reboot your device into bootloader/fastboot mode, by turning phone off. Hold volume down/power at the same time, and your phone will now be in fastboot mode. Open command prompt and type in "fastboot oem unlock" (without the quotes). Thats it. Your device will ask you to confirm that you want to do this. Select yes. Use volume up/down to navigate through any prompts. Be aware, though, that this will perform a factory reset on device, which means it deletes personal files/apps. No big deal. You basically cannot brick a nexus device. If you need help, PM me.

bynarie said:
Unlocking the bootloader is VERY easy. All you must do is have either the entire have android SDK installed, or you just need the platform tools(adb and fastboot). Once you have those, you either navigate to the folder where adb/fastboot is -or- add them to your path variable. Reboot your device into bootloader/fastboot mode, by turning phone off. Hold volume down/power at the same time, and your phone will now be in fastboot mode. Open command prompt and type in "fastboot oem unlock" (without the quotes). Thats it. Your device will ask you to confirm that you want to do this. Select yes. Use volume up/down to navigate through any prompts. Be aware, though, that this will perform a factory reset on device, which means it deletes personal files/apps. No big deal. You basically cannot brick a nexus device. If you need help, PM me.
Click to expand...
Click to collapse
So if i place the fastboot.exe on my desktop, and then open the command prompt and type "cd desktop", and then "fastboot oem unlock". That should unlock my fastboot right? I just tried doing that without having any devices plugged in and it gave me a text <waiting for devices> in cmd.
I do not understand the part that you mean by navigating to the folder, you mean i have to navigate to the folder where i have fastboot.exe right?
If all that is correct, after i do all the flashing i have to do the same thing i did now, just use command "fastboot oem lock"?

nikssims said:
So if i place the fastboot.exe on my desktop, and then open the command prompt and type "cd desktop", and then "fastboot oem unlock". That should unlock my fastboot right? I just tried doing that without having any devices plugged in and it gave me a text <waiting for devices> in cmd.
I do not understand the part that you mean by navigating to the folder, you mean i have to navigate to the folder where i have fastboot.exe right?
If all that is correct, after i do all the flashing i have to do the same thing i did now, just use command "fastboot oem lock"?
Click to expand...
Click to collapse
I would suggest wherever you have fastboot AND adb located, put the folder in your path variable so you dont have to worry about it and you just open cmd and type fastboot or adb.. And you do not need to lock the bootloader back unless a) your taking device in for warranty repair or b) selling device. If you plan on keeping the device, just leave bootloader unlocked. That way you can play around with roms, recoveries and whatever else. Oh, and you need to have both fastboot.exe and adb.exe. First of all if your using fastboot when your device is loaded into android it doesnt work. It has to be in FASTBOOT MODE. Which means turning off device. Hold power + vol down. Then it will look like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then you can run "fastboot oem unlock" or "fastboot oem lock", or any other fastboot command. This is how we flash a custom recovery, which i definitely recommend. Here is a link to download TWRP recovery http://techerrata.com/browse/twrp2/hammerhead. Download the latest version(2.8.1.0), rename it to twrp.img and open cmd prompt and run fastboot flash recovery twrp.img - this will give you your recovery program. Then use vol up/down to navigate to recovery.

bynarie said:
I would suggest wherever you have fastboot AND adb located, put the folder in your path variable so you dont have to worry about it and you just open cmd and type fastboot or adb.. And you do not need to lock the bootloader back unless a) your taking device in for warranty repair or b) selling device. If you plan on keeping the device, just leave bootloader unlocked. That way you can play around with roms, recoveries and whatever else. Oh, and you need to have both fastboot.exe and adb.exe. First of all if your using fastboot when your device is loaded into android it doesnt work. It has to be in FASTBOOT MODE. Which means turning off device. Hold power + vol down. Then it will look like this
IMAGE
Then you can run "fastboot oem unlock" or "fastboot oem lock", or any other fastboot command. This is how we flash a custom recovery, which i definitely recommend. Here is a link to download TWRP recovery http://techerrata.com/browse/twrp2/hammerhead. Download the latest version(2.8.1.0), rename it to twrp.img and open cmd prompt and run fastboot flash recovery twrp.img - this will give you your recovery program. Then use vol up/down to navigate to recovery.
Click to expand...
Click to collapse
Thank you, that is a lot of useful information! I don't think i will install custom recovery though, because i simply want to update my device to Android L and keep it unrooted. Just completely stock android L. The reason i am doing it this way is because i messed my device up a bit using the towelroot and softkeyz app, and i doubt i will get android L over OTA.

nikssims said:
So if i place the fastboot.exe on my desktop, and then open the command prompt and type "cd desktop", and then "fastboot oem unlock". That should unlock my fastboot right? I just tried doing that without having any devices plugged in and it gave me a text <waiting for devices> in cmd.
I do not understand the part that you mean by navigating to the folder, you mean i have to navigate to the folder where i have fastboot.exe right?
If all that is correct, after i do all the flashing i have to do the same thing i did now, just use command "fastboot oem lock"?
Click to expand...
Click to collapse
This was all covered in my adb and fastboot thread. If you follow what I wrote there, there is no need to put things in the same folders or cd etc.

nikssims said:
Thank you, that is a lot of useful information! I don't think i will install custom recovery though, because i simply want to update my device to Android L and keep it unrooted. Just completely stock android L. The reason i am doing it this way is because i messed my device up a bit using the towelroot and softkeyz app, and i doubt i will get android L over OTA.
Click to expand...
Click to collapse
No problem! You are free to do as you want. Remember, people here at XDA are here to help you. Do not think you're asking a dumb or repeat question. If you need to know, ask. If you need any more help I will do my best. I would suggest a custom recovery though because it makes re freshing system and other things really simple. It gives you lower level access to the system than a apk app would. But, do as you wish. You will learn more as you go. I started out as a total n00b, just like everyone does. Eventually I messed my stuff up so bad i HAD to fix it LoL! Hang around IRC #xda-devs and the xda site if youd like to learn more. I think XDA is the most valuable resource ive ever seen for ANY community. I love it here. Anyway, have a nice day!

rootSU said:
This was all covered in my adb and fastboot thread. If you follow what I wrote there, there is no need to put things in the same folders or cd etc.
Click to expand...
Click to collapse
Ah yes indeed, i simply open the cmd and i can type commands instantly there without having to do that "cd" navigation part. That is great thanks!

bynarie said:
No problem! You are free to do as you want. Remember, people here at XDA are here to help you. Do not think you're asking a dumb or repeat question. If you need to know, ask. If you need any more help I will do my best. I would suggest a custom recovery though because it makes re freshing system and other things really simple. It gives you lower level access to the system than a apk app would. But, do as you wish. You will learn more as you go. I started out as a total n00b, just like everyone does. Eventually I messed my stuff up so bad i HAD to fix it LoL! Hang around IRC #xda-devs and the xda site if youd like to learn more. I think XDA is the most valuable resource ive ever seen for ANY community. I love it here. Anyway, have a nice day!
Click to expand...
Click to collapse
Thank you for you help!

One more thing. If you are ever interested in flashing a recovery, check out my GUI tool that does this for you. Just clicking buttons and selecting correct file. http://forum.xda-developers.com/general/general/project-droidtool-fastboot-adb-utility-t2928176

[Q] Stock OPO soft bricked after turning off at night.

Okay, here's the deal... I have an OPO (not mine) that is completely stock running, I would presume 5.0.2. I'm not exactly sure which build. But I was told that she turned the phone off at night and charged it. Turned it on in the morning and it got stuck on the cyanogen logo. No boot loops, no getting past that. Just sitting there. The device is stock, bootloader locked, no root. I also highly doubt that ADB debugging was turned on while it was working...
I'm trying to wipe it bring it back to stock, but I'm not having any success. I've gone in to Cyanogen recovery and wipe/factory reset, wipe cache, wipe media. Reboot, still stuck. When I click apply update in recovery, it gives me a bunch of errors saying so and so directory isn't found. So that leaves to me to believe that something went bad.
I just tried to fastboot oem unlock, said it finished in a few seconds. Then I tried to fastboot the factory image files and after the first one (modem), it gave me an error saying the bootloader is locked.
I'm out of ideas and the unbrick a hard bricked OPO thread said it wouldn't work, so I haven't tried it. Any advice on where to look would be much appreciated.

Anybody?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I get this when I hit Apply Update and then use storage as option.

moobieboobie said:
Anybody?
I get this when I hit Apply Update and then use storage as option.
Click to expand...
Click to collapse
Flash The whole Rom with fastboot to fix The Problem ....make a backup of your internal sdcard....

jamal2367 said:
Flash The whole Rom with fastboot to fix The Problem ....make a backup of your internal sdcard....
Click to expand...
Click to collapse
That's the problem. I can't because the bootloader is locked. When I try to unlock it, it runs the command. Then when I try to fastboot flash, it tells me the bootloader is locked. I have my own OPO that I have unlocked and rooted, so knowing how to unlock isn't an issue either.

moobieboobie said:
That's the problem. I can't because the bootloader is locked. When I try to unlock it, it runs the command. Then when I try to fastboot flash, it tells me the bootloader is locked. I have my own OPO that I have unlocked and rooted, so knowing how to unlock isn't an issue either.
Click to expand...
Click to collapse
Run CMD as Admin ...have you install the right driver for your phone and install the ADB drivers correctly? ...

jamal2367 said:
Run CMD as Admin ...have you install the right driver for your phone and install the ADB drivers correctly? ...
Click to expand...
Click to collapse
Yes, all updated drivers. Drivers are not the issue since I can execute commands while in fastboot. The issue is not having an unlocked bootloader, so I can't flash anything and it won't unlock bootloader.

moobieboobie said:
Yes, all updated drivers. Drivers are not the issue since I can execute commands while in fastboot. The issue is not having an unlocked bootloader, so I can't flash anything and it won't unlock bootloader.
Click to expand...
Click to collapse
Ps did phone was encrypt?

geowolf1000 said:
Ps did phone was encrypt?
Click to expand...
Click to collapse
No, phone was not encrypted and ColorOS unbrick didn't work. It recognizes the phone, I hit start and it does it's thing. After first green bar, it boot loops instead of flashing all the files. Ran as admin and all the drivers are good.

moobieboobie said:
No, phone was not encrypted and ColorOS unbrick didn't work. It recognizes the phone, I hit start and it does it's thing. After first green bar, it boot loops instead of flashing all the files. Ran as admin and all the drivers are good.
Click to expand...
Click to collapse
hit install from recovery
Choose file to update
Search files
Do you see your partition?
System exist?
What system do you have color or cyanogen?
Data?
Sd?

geowolf1000 said:
hit install from recovery
Choose file to update
Search files
Do you see your partition?
System exist?
What system do you have color or cyanogen?
Data?
Sd?
Click to expand...
Click to collapse
See post above with picture. It was running stock Cyanogen OS 12, not modded or anything. When I hit Apply Update and Choose from internal storage, I get the error in above picture.

moobieboobie said:
See post above with picture. It was running stock Cyanogen OS 12, not modded or anything. When I hit Apply Update and Choose from internal storage, I get the error in above picture.
Click to expand...
Click to collapse
But you have adb
Sideload full rom included recovery
From adb

geowolf1000 said:
But you have adb
Sideload full rom included recovery
From adb
Click to expand...
Click to collapse
If by sideload, you mean copy the rom to device and then load..I can not access device storage. ADB sideload rom through command line gives me the same errors you see in the above picture.

moobieboobie said:
If by sideload, you mean copy the rom to device and then load..I can not access device storage. ADB sideload rom through command line gives me the same errors you see in the above picture.
Click to expand...
Click to collapse
F**ing recovery
With adb you can navigate to system and change built.prompt and enable debugg mode
All the other method i know need root so dd (replace)recovery from adb

geowolf1000 said:
F**ing recovery
With adb you can navigate to system and change built.prompt and enable debugg mode
All the other method i know need root so dd (replace)recovery from adb
Click to expand...
Click to collapse
Can you give instructions on how to? I'm not too familiar with adb, but can follow steps.

moobieboobie said:
Can you give instructions on how to? I'm not too familiar with adb, but can follow steps.
Click to expand...
Click to collapse
Even this suggest need root.
All need root.... To system...

moobieboobie said:
Can you give instructions on how to? I'm not too familiar with adb, but can follow steps.
Click to expand...
Click to collapse
Another trick for installation is
Code:
fastboot boot <path/name of the recovery twrp img>
It will boot your phone into recovery once from the recovery image
stored in your PC temporarily
then you can flash the zip either by sideload or
Check this

geowolf1000 said:
Another trick for installation is
Code:
fastboot boot <path/name of the recovery twrp img>
It will boot your phone into recovery once from the recovery image
stored in your PC temporarily
then you can flash the zip either by sideload or
Check this
Click to expand...
Click to collapse
cannot fastboot boot recovery, tells me bootloader is locked and fails. the link requires unlocking bootloader, which is not working for me.

moobieboobie said:
cannot fastboot boot recovery, tells me bootloader is locked and fails. the link requires unlocking bootloader, which is not working for me.
Click to expand...
Click to collapse
Haz a parametre here

There is a way to flash an unlocked bootloader if you can't fastboot oem unlock.
As you already tried the color.zip method you should already have most of the needed files.
Download the attachment and unzip it into color folder replacing the files emmc_appsboot.mbn and rawprogram0_64.xml (backup the originals first).
-power off the OPO
-hold VolUp and plug into PC
-on PC open device manager, OPO should be in QDloader 9008
-keep an eye on device manager and start msm8974downloadtool from color.zip
-when in device manager the QDloader 9008 disconnects press stop in msm8974downloadtool
-OPO should now be Qualcomm Diagnostics 9006 in device manager
-download MiFlash from here http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable/ and set it up like on the pictures on that website
-click refresh. now it should show you OPO on the respective COM port. click flash
-when successfull finished unplug and press and hold power for 30 seconds
-now start into fastboot with power + VolUp and there is your unlocked bootloader
-now you can flash cos with fastboot
The rawprogram0_64xml is edited so that it only writes partition table and flashes sbl1, dbi, rpm, tz, recovery and emmc_appsboot.
This worked for me when i couldn't flash with msm8974downloadtool, it always flashed modem, started with flashing system and then began from the start again.

tropenfrucht said:
There is a way to flash an unlocked bootloader if you can't fastboot oem unlock.
As you already tried the color.zip method you should already have most of the needed files.
Download the attachment and unzip it into color folder replacing the files emmc_appsboot.mbn and rawprogram0_64.xml (backup the originals first).
-power off the OPO
-hold VolUp and plug into PC
-on PC open device manager, OPO should be in QDloader 9008
-keep an eye on device manager and start msm8974downloadtool from color.zip
-when in device manager the QDloader 9008 disconnects press stop in msm8974downloadtool
-OPO should now be Qualcomm Diagnostics 9006 in device manager
-download MiFlash from here http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable/ and set it up like on the pictures on that website
-click refresh. now it should show you OPO on the respective COM port. click flash
-when successfull finished unplug and press and hold power for 30 seconds
-now start into fastboot with power + VolUp and there is your unlocked bootloader
-now you can flash cos with fastboot
The rawprogram0_64xml is edited so that it only writes partition table and flashes sbl1, dbi, rpm, tz, recovery and emmc_appsboot.
This worked for me when i couldn't flash with msm8974downloadtool, it always flashed modem, started with flashing system and then began from the start again.
Click to expand...
Click to collapse
gave it a shot a few minutes ago.. As soon as 9008 dc fom device manager, i hit stop. the phone turns off or reboots (the screen goes blank)... I hear the connection, but no 9006.