Database Info

[Q] My Nexus S won't boot at all... Help, please

Hi
I'm facing a problem with my Nexus S, before it was working... but, unfourtunatlly i just make some modification in the system file and now my phone not working and stuck at the google logo black screen... exactly, i think the problem in the java runtime.jar file that was in the system folder, i replace it with another file and all that done since i want to add another language to the system so that it can understand it. but, the device now is not working....
I tried to enter the recovery mode and wipe all data, but nothing change. its keep the same. so i tried also to format the system (from the recovery) since, the modification done in that folder... also, its not working....
So, I think the best way right now is to return it to the default rom(official one from google) , i download it, and tried to flash it using the "fastboot" command but it keep give me error when writing for system.img file....
What can I do right know ??? I can't use my device at all...
Help me Guys, please.....

For future reference Factory wipe doesn't touch /system...just /data.
If you formatted your /system, and it actually formatted, all you can do now is restore a working system.
If you didn't make your own nandroid backup of the system (and you ALWAYS should in the future before messing with system level modifications) to have a known working configuration, then your best bet in my opinion is to go to this thread: http://forum.xda-developers.com/showthread.php?t=884093
Download the nandroid image from there and flash it to your phone using Clockwork Recovery.
Good luck.

distortedloop said:
For future reference Factory wipe doesn't touch /system...just /data.
If you formatted your /system, and it actually formatted, all you can do now is restore a working system.
If you didn't make your own nandroid backup of the system (and you ALWAYS should in the future before messing with system level modifications) to have a known working configuration, then your best bet in my opinion is to go to this thread: http://forum.xda-developers.com/showthread.php?t=884093
Download the nandroid image from there and flash it to your phone using Clockwork Recovery.
Good luck.
Click to expand...
Click to collapse
But, The question here is.... how can i flash it when i can't get access to the memory(since the Nexus S doesn't have sd memory slot) and to the system ??
when i enter the recovery, all i can do is use the fastboot command.... can i use it here ??
Thanks alot .....

If you boot into Clockwork, you should be able to use it's mounts menu to mount the sdcard...then use adb to push the files to your sdcard. adb should be active and working in clockwork.
If that doesn't work out for you, you could also try the Odin and "download mode" approach from this thread: http://forum.xda-developers.com/showthread.php?t=947950

distortedloop said:
If you boot into Clockwork, you should be able to use it's mounts menu to mount the sdcard...then use adb to push the files to your sdcard. adb should be active and working in clockwork.
If that doesn't work out for you, you could also try the Odin and "download mode" approach from this thread: http://forum.xda-developers.com/showthread.php?t=947950
Click to expand...
Click to collapse
Thank you sooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo much distortedloop....
as what u said.... the mount already available in the clockwork.. but i didn't see it before.....
Now i got my Nexus S back to me again.....
Thank u soooooooooooooo much Man... I appreciate it

abd640 said:
Thank you sooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo much distortedloop....
as what u said.... the mount already available in the clockwork.. but i didn't see it before.....
Now i got my Nexus S back to me again.....
Thank u soooooooooooooo much Man... I appreciate it
Click to expand...
Click to collapse
Glad you're up and running again.

Hello guys
I have the same problem, but i guess for different reasons.
I applyed the superboot from the modaco´s forum on my nexus s, but I guess I did it with the wrong version (i had got the 2.3.4 ota before doing so and used a 2.3.3 version) and now my phone won´t boot. My rom was stock. Now, it remains on that google initial screen. I can´t get to upload anything for the device since I guess the usb debug mode is off, although when I connect the device to the computer, the system shows the usb driver. I guess my device is GT90 something, can´t say for sure. Have to check at the box.
That said, I´d like some help on what to do about it.
I´ll be forever grateful!

ectole said:
Hello guys
I have the same problem, but i guess for different reasons.
I applyed the superboot from the modaco´s forum on my nexus s, but I guess I did it with the wrong version (i had got the 2.3.4 ota before doing so and used a 2.3.3 version) and now my phone won´t boot. My rom was stock. Now, it remains on that google initial screen. I can´t get to upload anything for the device since I guess the usb debug mode is off, although when I connect the device to the computer, the system shows the usb driver. I guess my device is GT90 something, can´t say for sure. Have to check at the box.
That said, I´d like some help on what to do about it.
I´ll be forever grateful!
Click to expand...
Click to collapse
try to boot into bootloader. root the phone n install a recovery.img, then reinstall a custom rom or the stock rom.

deeren said:
try to boot into bootloader. root the phone n install a recovery.img, then reinstall a custom rom or the stock rom.
Click to expand...
Click to collapse
The thing is that i already have clockworkmode installed and i can access it through bootload, in fact is the only thing i can do. My problem is that i just can´t send the recovery.img from the pc to the phone. And I also think that the usb debug mode is unavailabe, so I can´t activate it.
I´m new to this thing so the only way I could move files into the phone was through windows explorer drag and drop. Honestly I´m lost without it.
Is there a different way to push it to the phone ?
I understand this forum is intended to more experienced users, and for that I apologise.

Guys I found a solution by enabling USB from clockwork! Thanks! Keep the good work!
Sent from my Nexus S using XDA Premium App

Hello "ectole", could you let me know how you get out of it. I am in the same problem. I followed this guide http://forum.xda-developers.com/showthread.php?p=13800735#post13800735 to root my phone, now I always boot into clockwork. I can I boot into Nexux again?

Hi guys,
I'm in a similar situation. I tried to install CyanogenMod 7 to my Nexus S (ATT), got stuck at the skating dude.
Booted back into Clockwork, and tried to flash back to the stock firmware, but I think I accidentally flashed the wrong one (for the 9020T instead of 9020A) build. Now I can't get into ClockworkMod or anything on the screen whatsoever.
Does anyone have any tips at all? I'm really screwed here, would appreciate it a lot...
J

Hey bante just go to clockwork then to mount/dismount menu and the last option should be mount USB storage. Mount it and stay there and your PC should see the sd card. Then upload what you want.
Sent from my Nexus S using XDA Premium App

HELP!!! Odin bricked my Nexus S i9020a
I attempted to use odin to restore my phone. Could not get past bootloading screen. Put phone in recovery mode and used odin and grh78 firmware.
Odin went thru the whole process and said success, then my phone shut off, and will not power back on. Any ideas?

OkNewMedia said:
I attempted to use odin to restore my phone. Could not get past bootloading screen. Put phone in recovery mode and used odin and grh78 firmware.
Odin went thru the whole process and said success, then my phone shut off, and will not power back on. Any ideas?
Click to expand...
Click to collapse
Which phone version you got?
Sent from my Nexus S using XDA App

OkNewMedia said:
I attempted to use odin to restore my phone. Could not get past bootloading screen. Put phone in recovery mode and used odin and grh78 firmware.
Odin went thru the whole process and said success, then my phone shut off, and will not power back on. Any ideas?
Click to expand...
Click to collapse
By 'recovery mode', do you mean download mode? (you hold both vol up and vol down then plug in USB)

My Nexus s not boot at all
Hi
I'm facing a problem with my Nexus S, before it was working... but, unfourtunatlly i just make some modification in the system file and now my phone not working and stuck at the google logo black screen...
it doesn't entering the recovery mode. it only stucks at the google black logo screen
What can I do right know ??? I can't use my device at all...
Help me Guys, please.....

shavinder said:
Hi
I'm facing a problem with my Nexus S, before it was working... but, unfourtunatlly i just make some modification in the system file and now my phone not working and stuck at the google logo black screen...
it doesn't entering the recovery mode. it only stucks at the google black logo screen
What can I do right know ??? I can't use my device at all...
Help me Guys, please.....
Click to expand...
Click to collapse
flash either clockwork or twrp recovery via fastboot.

but how can i do this thing

jstennis1591 said:
Hi guys,
I'm in a similar situation. I tried to install CyanogenMod 7 to my Nexus S (ATT), got stuck at the skating dude.
Booted back into Clockwork, and tried to flash back to the stock firmware, but I think I accidentally flashed the wrong one (for the 9020T instead of 9020A) build. Now I can't get into ClockworkMod or anything on the screen whatsoever.
Does anyone have any tips at all? I'm really screwed here, would appreciate it a lot...
J
Click to expand...
Click to collapse
Sounds like you flashed i9023 software. You could try Odin. Does your computer recognize the phone?
Sent from my Nexus S 4G using xda premium

[Q] Help needed, bootloader error frequently

Hi everyone, i am using milestone A853 model, i follow exactly the guide to root the phone and everything goes perfect, i can boot up and use all the custom rom as usual. BUT the problem now i having is, it happened randomly sometimes i reboot my phone it just got into this bootloader err 1A,23,35,23,00 and i have to flash the GOT 2.2.1.sbf again and do a nandroid restore, i have to flash my phone around 4 times a week.
FYI, i tried the 3 button combination to get into open recovery but still it leads me to the bootloader err page.. is there anyway i can get rid of this?? i need to constantly be with a pc to get my phone working

[d]amour said:
Hi everyone, i am using milestone A853 model, i follow exactly the guide to root the phone and everything goes perfect, i can boot up and use all the custom rom as usual. BUT the problem now i having is, it happened randomly sometimes i reboot my phone it just got into this bootloader err 1A,23,35,23,00 and i have to flash the GOT 2.2.1.sbf again and do a nandroid backup, i have to flash my phone around 4 times a week.
FYI, i tried the 3 button combination to get into open recovery but still it leads me to the bootloader err page.. is there anyway i can get rid of this?? i need to constantly be with a pc to get my phone working
Click to expand...
Click to collapse
According to this thread, it might be an issue with a bad SD card.
http://www.android-hilfe.de/motorola-milestone/12635-milestone-startet-nicht-mehr.html
Can you try with another SD card?
Is it possibly that you have the older version of the Milestone bootloader? (90.73), you can try to flash the VR from kabaldan's website( http://android.doshaska.net/rootable) instead of G.O.T., you just need to put OR on your SD card yourself.

i am using the bootloader 90.78 and androidiani 3.3 open recovery...i try to format my sd card first see if it helps....i flashed my phone yesterday and using a fresh new iceandfire rom 3.0, i tried a couple of times rebooting and turn off my phone and it just boot up without any problem, however this morning i tried to reboot once more and i got this bootloader error again...frustrating =/

[d]amour said:
i am using the bootloader 90.78 and androidiani 3.3 open recovery...i try to format my sd card first see if it helps....i flashed my phone yesterday and using a fresh new iceandfire rom 3.0, i tried a couple of times rebooting and turn off my phone and it just boot up without any problem, however this morning i tried to reboot once more and i got this bootloader error again...frustrating =/
Click to expand...
Click to collapse
AOR dont updated recently, try FuFu openrecovery. it is based on AOR but have many new features and fix, like mmc fix, ext4 module, etc...
if your problem is beacuse the sdcard then you have the mmc error, what is fixed be kabaldan, and he provided a module for the fix, or you have a broken sdcard.

Changing the a different OR will help? i already apply the dsifix.ko 2.6 by kabaldan in my /system/lib/modules directory, just only did a nandroid restore to my phone now, will monitor how long it will last till the next bootloader err...sigh, btw is it ok if i keep trying to reboot like 5 times in an hour time?

[d]amour said:
Changing the a different OR will help? i already apply the dsifix.ko 2.6 by kabaldan in my /system/lib/modules directory, just only did a nandroid restore to my phone now, will monitor how long it will last till the next bootloader err...sigh, btw is it ok if i keep trying to reboot like 5 times in an hour time?
Click to expand...
Click to collapse
5 times seems a bit excessive to me. If all you are trying to do is see if you will boot into the bootloader when you really wanted the recovery, 2 times every hour or so should suffice.

wait a sec, you can enter the recovery console? try to not use the autoboot to or script. if the phone booted to the bootloader mode you can see a triangle, then push the camera and the volume up button to entering the basic recovery mode.
at this point the sdcard not used. then you can try to the update menu, now the phone trying to load the OR update.zip from the sdcard. if you have problem only with the last step, then your sdcard maybe broken, if you have the error at the first step, it is possible that your phone nand memory is failing. in that case you need to call the motorola customer service for the repair.

vadonka said:
wait a sec, you can enter the recovery console? try to not use the autoboot to or script. if the phone booted to the bootloader mode you can see a triangle, then push the camera and the volume up button to entering the basic recovery mode.
at this point the sdcard not used. then you can try to the update menu, now the phone trying to load the OR update.zip from the sdcard. if you have problem only with the last step, then your sdcard maybe broken, if you have the error at the first step, it is possible that your phone nand memory is failing. in that case you need to call the motorola customer service for the repair.
Click to expand...
Click to collapse
Recovery console? you mean the console mode after enter the androidiani menu?i can go straight into AOR with the camera + power button after turning it off.
whenever i got the bootloader error, i cant do anything though, the camera button with volume up is not working.All i can do is flash the .sbf file again.
But for now my phone is still working since the last nandroid restore i did this morning, reboot a few times normally and also reboot to recovery both are working as usual.

[d]amour said:
Recovery console? you mean the console mode after enter the androidiani menu?i can go straight into AOR with the camera + power button after turning it off.
whenever i got the bootloader error, i cant do anything though, the camera button with volume up is not working.All i can do is flash the .sbf file again.
But for now my phone is still working since the last nandroid restore i did this morning, reboot a few times normally and also reboot to recovery both are working as usual.
Click to expand...
Click to collapse
it is sadly, but it is possible that your phone nand memory unstable or have some crc error. do you often reflash before?

vadonka said:
it is sadly, but it is possible that your phone nand memory unstable or have some crc error. do you often reflash before?
Click to expand...
Click to collapse
i only started flashing few weeks ago but the bootloader error occur too frequently that i have to flash at least once every 2 days...for now i see that it lasted longer than usual,if it is really nand memory unstable means that there is nothing i can do to fix it?

[d]amour said:
i only started flashing few weeks ago but the bootloader error occur too frequently that i have to flash at least once every 2 days...for now i see that it lasted longer than usual,if it is really nand memory unstable means that there is nothing i can do to fix it?
Click to expand...
Click to collapse
you cant fix that, only the motorola service, but i suggest to try it some benchmark software like antutu benchmark. with that you can test the memory and see what happened.

well i guess the only solution will be not turning off my phone/reboot for as long as i could, don't wan to take risk later it gets into bootloader error again

My phone always stuck at bootloader when it's hot while booting up.
Wait few minutes or use a fan to cool it down will solve it.
When this happen, recovery mode won't start
and flashing new ROM won't help or even make problem worse because of extra heat produced.
Avoid rebooting after gaming/heavy use is my workaround.

imTigger said:
My phone always stuck at bootloader when it's hot while booting up.
Wait few minutes or use a fan to cool it down will solve it.
When this happen, recovery mode won't start
and flashing new ROM won't help or even make problem worse because of extra heat produced.
Avoid rebooting after gaming/heavy use is my workaround.
Click to expand...
Click to collapse
when u stuck in the bootloader it shows the error code like mine? or just the usual bootloader screen? i tried leaving the phone for few hours without doing anything but it still stuck at the bootloader screen with error code =/

I doubt this will help, but can you try flashing an official 2.2 sbf and try it for a few days? or maybe get an official 2.2 sbf, then root it, then install a rom.

hey there just to informed you guys here that my phone currently had no bootloader error so far for a week, i am using Froyo Mod 2.9.3 and everything just work well. Wonder what happen actually to my phone previously when i flash other rom.
Just wanna ask will the following step i did causes a bootloader error?
-Flash 2.2.1 got sbf files.
-Reboot to recovery (using the latest minimod), Click on root phone (i not sure will this cause the problem as this is suppose to be for stock rom?? plz correct me if am wrong)
-Wipe Dalvik,cache and data
-Apply update of custom rom and gapps.
-Reboot

[Q] I'm pretty sure I'm screwed. HELP!

Ok so I usually do searching (in this case a few hours of searching), to get help but I am in a very unique situation. Long story.
I tried updating my rooted nexus 5 to android 4.4.3 via CWM Recovery. It seemed to be taking an extremely long time to flash the rom. (I think it was a mod stock rom with root) So I shut it down, of course it wouldnt boot. So I did a whole wipe and reset in CWM, nothing. So I did it using Command prompt with one of the guides here. Worked great! Got it running, apps downloading. Then I noticed that my storage was cut in half. (It said I had 12 gigs and not 28, I have a 32 gig nexus 5) I read up and found someone who re locked, then unlocked hit boot loader. So I did that using Command Prompt. Now im stuck in a boot loop. Here's the kicker, When you lock the bootloader, the phone gets wiped. Well there went my USB debugging mode. So now, Im stuck in a boot loop and no way to get out. Ive tried using CWM to factory reset. Nothing.
I think I may have to get a new phone. From what Ive found theres no other way to get usb debugging mode on unless your in the phone. Without that, I cant do anything with command prompt. I dont post really at all, just read. So for me to do this means I am really stuck. Any advice or ideas would be greatly appreciated! I have all the latest drivers and everything.

Can you access the recovery? If so, format cache partition and then perform a factory reset and try to boot. If it fails, download the factory images and flash it. Factory images are flashed in fastboot mode and doesn't require a working OS or USB Debugging.
Follow the links in my signature and read everything mentioned it those threads. I'm sure your phone will be up and running in no time!

Thanks for the quick reply. Yes I can get into clockwork mod. Ive tried wiping data factory reset, wiping dalvik and cache partitions. When I do a factory data reset, I get this:
Formatting data /data...
error mounting /data...
Skipping format...
Formatting /cahce
Formatting /sd-ext...
E: Unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure!
Skipping format...
Data Wipe Complete
Still in boot loop.

zeroshift11 said:
Thanks for the quick reply. Yes I can get into clockwork mod. Ive tried wiping data factory reset, wiping dalvik and cache partitions. When I do a factory data reset, I get this:
Formatting data /data...
error mounting /data...
Skipping format...
Formatting /cahce
Formatting /sd-ext...
E: Unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure!
Skipping format...
Data Wipe Complete
Still in boot loop.
Click to expand...
Click to collapse
Dumb question, but do you have access to your latest back up on your phone?

Boot into recovery and adb push a rom zip
Sent from my Nexus 5 using Tapatalk

zeroshift11 said:
Ok so I usually do searching (in this case a few hours of searching), to get help but I am in a very unique situation. Long story.
I tried updating my rooted nexus 5 to android 4.4.3 via CWM Recovery. It seemed to be taking an extremely long time to flash the rom. (I think it was a mod stock rom with root) So I shut it down, of course it wouldnt boot. So I did a whole wipe and reset in CWM, nothing. So I did it using Command prompt with one of the guides here. Worked great! Got it running, apps downloading. Then I noticed that my storage was cut in half. (It said I had 12 gigs and not 28, I have a 32 gig nexus 5) I read up and found someone who re locked, then unlocked hit boot loader. So I did that using Command Prompt. Now im stuck in a boot loop. Here's the kicker, When you lock the bootloader, the phone gets wiped. Well there went my USB debugging mode. So now, Im stuck in a boot loop and no way to get out. Ive tried using CWM to factory reset. Nothing.
I think I may have to get a new phone. From what Ive found theres no other way to get usb debugging mode on unless your in the phone. Without that, I cant do anything with command prompt. I dont post really at all, just read. So for me to do this means I am really stuck. Any advice or ideas would be greatly appreciated! I have all the latest drivers and everything.
Click to expand...
Click to collapse
Try changing to TWRP recovery by using - fastboot flash recovery recoveryname.img
Format data, factory reset your devices in TWRP,
Then, install any rom using adb sideload in TWRP

Oh and if you're booting in any way possible, you're never screwed ?
Sent from my Nexus 5 using Tapatalk

zeroshift11 said:
Ok so I usually do searching (in this case a few hours of searching), to get help but I am in a very unique situation. Long story.
I tried updating my rooted nexus 5 to android 4.4.3 via CWM Recovery. It seemed to be taking an extremely long time to flash the rom. (I think it was a mod stock rom with root) So I shut it down, of course it wouldnt boot. So I did a whole wipe and reset in CWM, nothing. So I did it using Command prompt with one of the guides here. Worked great! Got it running, apps downloading. Then I noticed that my storage was cut in half. (It said I had 12 gigs and not 28, I have a 32 gig nexus 5) I read up and found someone who re locked, then unlocked hit boot loader. So I did that using Command Prompt. Now im stuck in a boot loop. Here's the kicker, When you lock the bootloader, the phone gets wiped. Well there went my USB debugging mode. So now, Im stuck in a boot loop and no way to get out. Ive tried using CWM to factory reset. Nothing.
I think I may have to get a new phone. From what Ive found theres no other way to get usb debugging mode on unless your in the phone. Without that, I cant do anything with command prompt. I dont post really at all, just read. So for me to do this means I am really stuck. Any advice or ideas would be greatly appreciated! I have all the latest drivers and everything.
Click to expand...
Click to collapse
First of all you most certainly not screwed.
Now what you have done is oem unlock without google stock recovery.
For the process of wiping userdata to complete , after you type fastboot oem unlock and restart the phone will boot to recovery and execute the wipe.
Because you have cwm recovery the process is stuck and hence the bootloop.
You need to boot to bootloader and type : fastboot -w (press enter) ,it will erase userdata and cache, and restart to system.
You can also try "fastboot format data " and "fastboot format cache" .but if -w worked then no need for that.
If you still stuck in bootloop then you need to flash the stock factory img.

zeroshift11 said:
Thanks for the quick reply. Yes I can get into clockwork mod. Ive tried wiping data factory reset, wiping dalvik and cache partitions. When I do a factory data reset, I get this:
Formatting data /data...
error mounting /data...
Skipping format...
Formatting /cahce
Formatting /sd-ext...
E: Unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure!
Skipping format...
Data Wipe Complete
Still in boot loop.
Click to expand...
Click to collapse
No need to worry. Download the 4.4.3 factory images and follow the guide "How to flash factory image" which is linked in my signature.
Or, if you want to try out a custom rom, you can push the rom.zip and gapps.zip to your device using "adb push" or sideload it in recovery.

I really appreciate the help guys. Ok I would love to try these, but, I cant do anything with the command prompt. It always says "waiting for device"
I have the latest good drivers installed from ADB. In my device manager the Yellow ! triangle is there beside the android bootloader interface. Ive tried uninstalling the drivers and the software and doing it again and nothing. Mind you, when I do that, it shows up as samsung android devices so that could be a a problem. Im going to try and work on that. Any other ideas?

zeroshift11 said:
I really appreciate the help guys. Ok I would love to try these, but, I cant do anything with the command prompt. It always says "waiting for device"
I have the latest good drivers installed from ADB. In my device manager the Yellow ! triangle is there beside the android bootloader interface. Ive tried uninstalling the drivers and the software and doing it again and nothing. Mind you, when I do that, it shows up as samsung android devices so that could be a a problem. Im going to try and work on that. Any other ideas?
Click to expand...
Click to collapse
I had a similar problem and solved it by going to update driver software, browes my computer, let me pick from a list on the computer. Then find the android adb interface
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
I had a similar problem and solved it by going to update driver software, browes my computer, let me pick from a list on the computer. Then find the android adb interface
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Done that. A few times. Says it's up to date. Problem for me that I can see so far, any tutorial on how to unlock bootloader or side load, requires USB debugging, which is turned off. Thats why I get the waiting for device message in Command Prompt.

zeroshift11 said:
I really appreciate the help guys. Ok I would love to try these, but, I cant do anything with the command prompt. It always says "waiting for device"
I have the latest good drivers installed from ADB. In my device manager the Yellow ! triangle is there beside the android bootloader interface. Ive tried uninstalling the drivers and the software and doing it again and nothing. Mind you, when I do that, it shows up as samsung android devices so that could be a a problem. Im going to try and work on that. Any other ideas?
Click to expand...
Click to collapse
Are you in fastboot mode while running fastboot commands? If so,
Uninstall each and every driver installed on your computer. Download the full android sdk from here: http://developer.android.com/sdk/index.html
Open SDK manager and download all the required tools. Also, download the usb_driver from within the sdk manager. Now connect your device to your computer and let it detect. Now, open device manager, right click on the recognized device (Name of the nexus device may be different. Don't worry). Select update driver. Now navigate to the usb_driver folder which you had downloaded previously and select it. Once the driver is updated, windows might reconnect the device. (Ding ding sounds). Once it does, open cmd from the fastboot folder and try running the commands again.

zeroshift11 said:
Done that. A few times. Says it's up to date. Problem for me that I can see so far, any tutorial on how to unlock bootloader or side load, requires USB debugging, which is turned off. Thats why I get the waiting for device message in Command Prompt.
Click to expand...
Click to collapse
No, pick it yourself, see below the search for driver software
Sent from my Nexus 5 using XDA Free mobile app

vin4yak said:
Are you in fastboot mode while running fastboot commands? If so,
Uninstall each and every driver installed on your computer. Download the full android sdk from here: http://developer.android.com/sdk/index.html
Open SDK manager and download all the required tools. Also, download the usb_driver from within the sdk manager. Now connect your device to your computer and let it detect. Now, open device manager, right click on the recognized device (Name of the nexus device may be different. Don't worry). Select update driver. Now navigate to the usb_driver folder which you had downloaded previously and select it. Once the driver is updated, windows might reconnect the device. (Ding ding sounds). Once it does, open cmd from the fastboot folder and try running the commands again.
Click to expand...
Click to collapse
Doing that again. Maybe I missed a step last time but I tried that already a few times. Im trying again.

zeroshift11 said:
I really appreciate the help guys. Ok I would love to try these, but, I cant do anything with the command prompt. It always says "waiting for device"
I have the latest good drivers installed from ADB. In my device manager the Yellow ! triangle is there beside the android bootloader interface. Ive tried uninstalling the drivers and the software and doing it again and nothing. Mind you, when I do that, it shows up as samsung android devices so that could be a a problem. Im going to try and work on that. Any other ideas?
Click to expand...
Click to collapse
zeroshift11 said:
Done that. A few times. Says it's up to date. Problem for me that I can see so far, any tutorial on how to unlock bootloader or side load, requires USB debugging, which is turned off. Thats why I get the waiting for device message in Command Prompt.
Click to expand...
Click to collapse
I think the drivers aren't installed properly. My phone comes up as Android Device, then in the drilldown Android Composite ADB Interface.
I know you've said you've done it many times, but try reinstalling the drivers manually. Go to whatever it's listed as under Device manager->Right click->Update Driver. I can't remember the exact prompts, but basically don't let it look online. Tell it that you want to install drivers you have on your computer. Navigate to where ever you have driver files and install it.
Try different USB ports/cables. Computers are weird. Sometimes this actually works.

Ok so I uninstalled the drivers from the device manager, went to control panel did it there as well. I have the SDK on my desktop, I installed the google drivers. But I also had downloaded just the google driver manually from their website. Unrared it, plugged my phone in, it detected the phone, I manually updated drivers to the ones I got from the google page. It updated. I was in bootloader mode, and I get that the drivers installed successfully, then it also says Device could not start (error code 10). Anything I type into command prompt still says waiting for device.

Johmama said:
I think the drivers aren't installed properly. My phone comes up as Android Device, then in the drilldown Android Composite ADB Interface.
I know you've said you've done it many times, but try reinstalling the drivers manually. Go to whatever it's listed as under Device manager->Right click->Update Driver. I can't remember the exact prompts, but basically don't let it look online. Tell it that you want to install drivers you have on your computer. Navigate to where ever you have driver files and install it.
Try different USB ports/cables. Computers are weird. Sometimes this actually works.
Click to expand...
Click to collapse
Wow........switching usb ports worked..............Thanks so much! Ok so bootloader unlocked. Now Ill try factory reset, if nothing Ill flash original recovery and do it again. After I sideload the stock zip.

Thanks to everyone here my phone is back up. Who knew the USB would have been the issue I was having. Its up, but again my storage was cut in half. Back to 12 gigs. So Im going to look for a fix unless anyone here has it haha.

zeroshift11 said:
Thanks to everyone here my phone is back up. Who knew the USB would have been the issue I was having. Its up, but again my storage was cut in half. Back to 12 gigs. So Im going to look for a fix unless anyone here has it haha.
Click to expand...
Click to collapse
Clear cache and factory reset in the stock recovery
Sent from my Nexus 5 using XDA Free mobile app

[Q] Locked Bootloader with TWRP, Won't unlock anymore

Ok, I'm an idiot. A big one.
I was looking to flash back to stock after using some lollipop roms. I was using TK's toolbox which was an extremely handy utility but in the peak of my madness, I hit lock bootloader with TWRP still installed.
Since hitting lock bootloader i'm not stuck with TWRP and it's crippled my phone since the current ROM no longer seems to be fully functional...I can't seem to download anything else from the web. Everything seems to fail.
I've tried fastboot oem unlock and it goes through the process that appears to be successful but it just boots back into TWRP and it's not unlocked. Does anyone have any suggestions or do I have a $300 paper weight. haha

Tonymhoffman said:
Ok, I'm an idiot. A big one.
I was looking to flash back to stock after using some lollipop roms. I was using TK's toolbox which was an extremely handy utility but in the peak of my madness, I hit lock bootloader with TWRP still installed.
Since hitting lock bootloader i'm not stuck with TWRP and it's crippled my phone since the current ROM no longer seems to be fully functional...I can't seem to download anything else from the web. Everything seems to fail.
I've tried fastboot oem unlock and it goes through the process that appears to be successful but it just boots back into TWRP and it's not unlocked. Does anyone have any suggestions or do I have a $300 paper weight. haha
Click to expand...
Click to collapse
Believe it or not, I have the same problem since yesterday. Its driving me mad since I'm no expert on rooting/unlocking
Phone gets detected by PC and by the toolbox but I can not unlock my phone again.
I am now stuck with TWRP and the only rom I can flash is Slimkat, all the others fail. If I hit unlock bootloader in the toolbox it goes through the process (fast) and it gives no error, boots back up to TWRP and thats it, but it is still locked
I just want it back locked and stocl CM11

Firstly, don't use toolkits. They are often the cause of issues.
Follow this thread to solve your problem: http://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390

Fixed it!
Solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912

PewLaserBeam said:
Fixed it!
Solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Click to expand...
Click to collapse
Damn you're lucky!
I'm having more issues because my phone won't let me download anything. It's like there is no SD card detected. I can't get that file onto my phone to flash it. Any ideas how I can do it?
I have ADB enabled and it shows up in my devices but it won't respond to adb sideload oneplusone-bootunlocker.zip
It responds to fastboot commands.. it just won't let me download anything off the net onto the device. IT will however update phone apps.. It's so damn frustrating.

Tonymhoffman said:
Damn you're lucky!
I'm having more issues because my phone won't let me download anything. It's like there is no SD card detected. I can't get that file onto my phone to flash it. Any ideas how I can do it?
I have ADB enabled and it shows up in my devices but it won't respond to adb sideload oneplusone-bootunlocker.zip
It responds to fastboot commands.. it just won't let me download anything off the net onto the device. IT will however update phone apps.. It's so damn frustrating.
Click to expand...
Click to collapse
I had this yesterday + I kept getting the message 'No OS installed'. Since it was already half 'broken', out of frustration I clicked everything and used all sorts of commands I could find (not the best idea I know :angel untill my PC detected the internal memory and then I downloaded 6-7 roms just to be sure. Slimkat was the only one without a fail.

How did you get the files over to your phone then if it wouldn't let you send them to it?
I finally got my internal memory to show up by mounting the system in the TWRP recovery.. But still getting an error that the device stopped responding or is disconnected.. However, it will let me open and view any file on the system, it just won't let me write to it.

Adb sideload did the fix for me after a while.
But it looks loke you have another problem.

Tonymhoffman said:
How did you get the files over to your phone then if it wouldn't let you send them to it?
I finally got my internal memory to show up by mounting the system in the TWRP recovery.. But still getting an error that the device stopped responding or is disconnected.. However, it will let me open and view any file on the system, it just won't let me write to it.
Click to expand...
Click to collapse
Instead of trying to sideload the unlocker zip have you tried using the adb push command?

Timma
Thanks for the reply. The solution for me was to mount the phone in TWRP. This allowed my SD card to be explored in Windows. However, it still would not allow me to copy files to the main directory and just out of frustration I quickly drag and dropped a PDF file that landed on a folder in the SD directory and it worked. Haha. So I then tried to copy the file inside another folder instead of the main directory. Success. What a headache and big ass mistake I'll never make again.
Note to self. Do not lock the bootloader with a custom recovery still installed. Ever.

Oneplus One Freezing On Startup

He there, just recently my phone had an update and i said yes to it. After the update completed It rebooted but never started back up.
When turned on, it just get up to the OnePlus One logo screen and stays there. I have tried a factory reset as I can access the recovery menu but the factory reset doesn't seem to do anything. I let the battery drain until the phone died and then charged it but it still will not start. Plugging it into my PC lets it charge but it does not let you access the storage. Its not a driver problem as it was working fine before the update.
I have tried fast boot but it just gets stuck on the fast boot screen.
I tried using OnePlus One Toolkit but it cant find the phone
I have read that I need to flash it but it would seem I need to transfer a file onto the phone but nothing recognizes the phone to transfer it to.
Can anyone help?
Thanks in advance,

Zastarx said:
He there, just recently my phone had an update and i said yes to it. After the update completed It rebooted but never started back up.
When turned on, it just get up to the OnePlus One logo screen and stays there. I have tried a factory reset as I can access the recovery menu but the factory reset doesn't seem to do anything. I let the battery drain until the phone died and then charged it but it still will not start. Plugging it into my PC lets it charge but it does not let you access the storage. Its not a driver problem as it was working fine before the update.
I have tried fast boot but it just gets stuck on the fast boot screen.
I tried using OnePlus One Toolkit but it cant find the phone
I have read that I need to flash it but it would seem I need to transfer a file onto the phone but nothing recognizes the phone to transfer it to.
Can anyone help?
Thanks in advance,
Click to expand...
Click to collapse
Your persist partition might be corrupt. Grab this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/view?usp=docslist_api
Then do this with fastboot:
Code:
fastboot erase persist
fastboot flash persist persist.img

Didn't work sadly. Maybe I should just flash everything?

Zastarx said:
Didn't work sadly. Maybe I should just flash everything?
Click to expand...
Click to collapse
Yeah, it's worth a shot. You can find full instructions in section 8 of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471

Yay!
It worked, thanks a lot!