[Q] Connectivity to PC issue post BOOT-Loop - ONE Q&A, Help & Troubleshooting

Hello Lovely people of XDA,
It has been a while since I have requested help here due to the huge library of information available but I am unable to solve this one and I think it should be pretty simple.
For completeness, here is the order of events:
ROOTed One and running stock CM11s with no problems since August 2014.
Wanted a smoother system so flashed vanilla Franco Kernel (very nice) yesterday.
Wanted a bit more so after some searching, found the SlimSaber ROM with TyrV74-Linaro Kernel as a suitable choice.
Now, I followed order of install but stupidly, didnt clear the cache or dalvik cache following install.
I got stuck in boot loop so booted to fastboot to open recovery through ADB.
PROBLEM STARTS
My PC didnt recognise my device and this was confirmed through the blank list returned when using "ADB Devices" in the command window.
I updated the drivers through the ADB interface, restarted computer and tried again. Same thing. I then downloaded the drivers from the Google link in one of the forums (http://developer.android.com/sdk/win-usb.html#top), restarted and connected again. I then tried two solutions (although they both do the same thing) and update the drivers through Device Manager and searching for them using the "have disk" option.
This still didnt work.
From what I can tell this is a driver issue but I have installed several times now the most up to date drivers and from what I can tell, the only difference between my screenshots and the help pages/forum posts is that my Device Manager list doesn't recognise the phone as the A0001, just an "Android Device" (pic attached).
I have searched the forums and all roads lead to either re-installing the drivers or changing the driver settings through device manager, both of which I have tried several times but no joy when I use ADB to check for devices.
Any ideas? I will try anything as I now have a beautifully BOOT-Looped OnePlus!
Also, if anyone knows how to boot to recovery from phone off state then that will also help!

Also tried the Samsung drivers...

OK, having managed to get the Comp to regognise in Fastboot, is there a way I can flash a nandroid through fastboot? I have checked and it says I need to flash three images but the only saved backups I have are .win files and there is only one (judging by the size of the file)

ssjghost said:
OK, having managed to get the Comp to regognise in Fastboot, is there a way I can flash a nandroid through fastboot? I have checked and it says I need to flash three images but the only saved backups I have are .win files and there is only one (judging by the size of the file)
Click to expand...
Click to collapse
You can't flash a nandroid with fastboot, only with the specific recovery you used to create the nandroid.
Transmitted via Bacon

timmaaa said:
You can't flash a nandroid with fastboot, only with the specific recovery you used to create the nandroid.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks
But now I am in a situation where I can (kinda) boot to system and I get a few precious clicks before the ROM crashes (either flashed wrong or ROM unstable....but irrelevant) so can now boot to recovery (managed to quickly DL an advanced power menu) but I can not move my backup to the phone to flash the backup. Any ideas?

ssjghost said:
Thanks
But now I am in a situation where I can (kinda) boot to system and I get a few precious clicks before the ROM crashes (either flashed wrong or ROM unstable....but irrelevant) so can now boot to recovery (managed to quickly DL an advanced power menu) but I can not move my backup to the phone to flash the backup. Any ideas?
Click to expand...
Click to collapse
strangely enough....when I fastboot reboot, it loads to system and as long as I keep the phone connected to PC it loads...when I remove it and boot, it crashes. I know this is the case as I wiped cache and delvik and nothing happened when removed but when I booted to system while connected it started updated gapps.... if that helps anyone....

ssjghost said:
Thanks
But now I am in a situation where I can (kinda) boot to system and I get a few precious clicks before the ROM crashes (either flashed wrong or ROM unstable....but irrelevant) so can now boot to recovery (managed to quickly DL an advanced power menu) but I can not move my backup to the phone to flash the backup. Any ideas?
Click to expand...
Click to collapse
You don't need to boot into the ROM to get to recovery. Turn the phone off, then hold volume down + power, once you see the initial splash screen let go of power but keep holding volume down until you get to recovery.
Why can't you move the backup? Please provide specifics, it will decrease the amount of back-and-forth we have to do to solve your issue.
Transmitted via Bacon

timmaaa said:
You don't need to boot into the ROM to get to recovery. Turn the phone off, then hold volume down + power, once you see the initial splash screen let go of power but keep holding volume down until you get to recovery.
Why can't you move the backup? Please provide specifics, it will decrease the amount of back-and-forth we have to do to solve your issue.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks,
I cant move file as, I presume, its down to drivers. Which I am unclear as to why? I can access the device through fastboot but when I go through "MyComputer", I get the icon for the phone but when I enter, no files (See Screenshots). If you want specific screenshots then let me know. When I transfer the backup....

Which drivers do you currently have installed?
Transmitted via Bacon

timmaaa said:
Which drivers do you currently have installed?
Transmitted via Bacon
Click to expand...
Click to collapse
"SAMSUNG Android ADB Interface"
They seem to be the only ones that work since flashing new ROM and Kernel...

ssjghost said:
"SAMSUNG Android ADB Interface"
They seem to be the only ones that work since flashing new ROM and Kernel...
Click to expand...
Click to collapse
BTW, I do have full access to phone (BOOT to system) while plugged in and can install that way so Im thinking...maybe upload backup to server/cloud and then download through app on phone, boot to recovery and flash from there?

ssjghost said:
BTW, I do have full access to phone (BOOT to system) while plugged in and can install that way so Im thinking...maybe upload backup to server/cloud and then download through app on phone, boot to recovery and flash from there?
Click to expand...
Click to collapse
Sorry, to clarify, when I say "work" I mean allow fastboot recognition....doesnt recognise files through MyComputer.....

ssjghost said:
BTW, I do have full access to phone (BOOT to system) while plugged in and can install that way so Im thinking...maybe upload backup to server/cloud and then download through app on phone, boot to recovery and flash from there?
Click to expand...
Click to collapse
Yeah that's probably a reasonable option, but it most likely won't solve the issue of not being able to copy files across. When you're booted into Android does the device show up as an MTP device in Windows and allow you to copy files, or is it broken there also?
Transmitted via Bacon

timmaaa said:
Yeah that's probably a reasonable option, but it most likely won't solve the issue of not being able to copy files across. When you're booted into Android does the device show up as an MTP device in Windows and allow you to copy files, or is it broken there also?
Transmitted via Bacon
Click to expand...
Click to collapse
Sorry you will have to clarify as my tech knowledge ends there. MTB?
I DLed a multi-SD card mout app and it said nothing was recogned and to try the MTP fix option. However, after clicking that....phone crashed and reverts to bootloop.
How can I check your question from PC?

ssjghost said:
Sorry you will have to clarify as my tech knowledge ends there. MTB?
I DLed a multi-SD card mout app and it said nothing was recogned and to try the MTP fix option. However, after clicking that....phone crashed and reverts to bootloop.
How can I check your question from PC?
Click to expand...
Click to collapse
....or phone (re-read question...)

ssjghost said:
....or phone (re-read question...)
Click to expand...
Click to collapse
(Sorry to treat board as IM but I keep thinking of potentially useful info...)
Somewhat unhelpfully, I have only flashed slim gapps so if you refer to an app, please specify which one as I likely dont have it!

ssjghost said:
Sorry you will have to clarify as my tech knowledge ends there. MTB?
I DLed a multi-SD card mout app and it said nothing was recogned and to try the MTP fix option. However, after clicking that....phone crashed and reverts to bootloop.
How can I check your question from PC?
Click to expand...
Click to collapse
ssjghost said:
....or phone (re-read question...)
Click to expand...
Click to collapse
ssjghost said:
(Sorry to treat board as IM but I keep thinking of potentially useful info...)
Somewhat unhelpfully, I have only flashed slim gapps so if you refer to an app, please specify which one as I likely dont have it!
Click to expand...
Click to collapse
MTP is the format that's used to mount the internal storage on your phone to your PC so you see it as a removable drive. There's no app required, so if you're not seeing your phone storage on your PC then MTP isn't working.
First thing to try: go to Settings/Storage and hit the little menu button in the top corner, there should be an MTP option in there. If it isn't enabled, enable it and try connecting to your PC again. If it is already enabled then it's time to look at your drivers.
I'd completely uninstall the Samsung drivers, reboot your PC, then install the Universal adb drivers, reboot PC again, connect your phone to your PC, you should get an automatic popup saying that device drivers are installing (or something like that), let that complete, then try looking at your phone storage again.
Transmitted via Bacon

timmaaa said:
MTP is the format that's used to mount the internal storage on your phone to your PC so you see it as a removable drive. There's no app required, so if you're not seeing your phone storage on your PC then MTP isn't working.
First thing to try: go to Settings/Storage and hit the little menu button in the top corner, there should be an MTP option in there. If it isn't enabled, enable it and try connecting to your PC again. If it is already enabled then it's time to look at your drivers.
I'd completely uninstall the Samsung drivers, reboot your PC, then install the Universal adb drivers, reboot PC again, connect your phone to your PC, you should get an automatic popup saying that device drivers are installing (or something like that), let that complete, then try looking at your phone storage again.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks,
MTB is checked and phone still not seen in menu so DLing drivers and will let you know after restart.
BTW, should I update drivers through device manager before/after or not at all after restart?

ssjghost said:
Thanks,
MTB is checked and phone still not seen in menu so DLing drivers and will let you know after restart.
BTW, should I update drivers through device manager before/after or not at all after restart?
Click to expand...
Click to collapse
There should be no need to update the drivers, because they're a fresh download they should be the latest.
Transmitted via Bacon

timmaaa said:
There should be no need to update the drivers, because they're a fresh download they should be the latest.
Transmitted via Bacon
Click to expand...
Click to collapse
.....nice...it was already installed. Ill remove, restart, install, restart and let you know....:/

Related

[Q] phone is dead , can only enter in cloxkworkmod recovery

Hi all expert,
my nexus s is unrooted. i installed ADB in my win7. I did wipe out all data/sd card without any back up. so my phone cant go anywhere ,except into clockworkmod recover. when I try to boot, error say it cant find any image. I cant instal image if i cant get in to the phone and set the usb connection. So my question is how to force install image into the phone without enablimg the usb connection? Please help. thank you
rongsokan said:
Hi all expert,
my nexus s is unrooted. i installed ADB in my win7. I did wipe out all data/sd card without any back up. so my phone cant go anywhere ,except into clockworkmod recover. when I try to boot, error say it cant find any image. I cant instal image if i cant get in to the phone and set the usb connection. So my question is how to force install image into the phone without enablimg the usb connection? Please help. thank you
Click to expand...
Click to collapse
you have clockwork recovery right? theres an usb storage option in the recovery itself. connect it to your computer, turn on the usb storage. download a rom(and gapps) to your computer, copy/paste into the device, turn off usb storage, then flash the files in clockwork recovery. then reboot.
After you do what he said, either do alot of research about rooting, and flashing roms and kernels or sell your phone.
Sent from my Nexus S 4G using xda premium
simms22 said:
you have clockwork recovery right? theres an usb storage option in the recovery itself. connect it to your computer, turn on the usb storage. download a rom(and gapps) to your computer, copy/paste into the device, turn off usb storage, then flash the files in clockwork recovery. then reboot.
Click to expand...
Click to collapse
So I did follow your instruction. I went storage->mount usb storage->unmount(I can only select this, I try reboot the phone still give me this only option). so I also tried mount sdcard, mount system, all that.
Finlally, I got removable disk on my computer, but it show 0 byte, when i click on it, it says plz insert a disk into removeable disk. so i went click
property->hardwares->highlight Android UMS composite usb device(type: disk drive) and property. then I select driver-> and there is driver details, update driver. So do I update this driver? If so which driver?
I try to format it, it gives errorlz insert a disk into removeable disk
I have clcokworkmod recovery v5.0.2.0 and it is unrooted. thank you for the help!
I also install PDAnet into my computer but it keep saying connecting to your phone..... I try using different usb port and no luck.
rongsokan said:
So I did follow your instruction. I went storage->mount usb storage->unmount(I can only select this, I try reboot the phone still give me this only option). so I also tried mount sdcard, mount system, all that.
Finlally, I got removable disk on my computer, but it show 0 byte, when i click on it, it says plz insert a disk into removeable disk. so i went click
property->hardwares->highlight Android UMS composite usb device(type: disk drive) and property. then I select driver-> and there is driver details, update driver. So do I update this driver? If so which driver?
I try to format it, it gives errorlz insert a disk into removeable disk
I have clcokworkmod recovery v5.0.2.0 and it is unrooted. thank you for the help!
Click to expand...
Click to collapse
By the way you just click on mount usb storage and LEAVE IT there for a few seconds. It takes a little time for the computer to recognize it usually. You only click unmount when your done...
ok i got it. now i could put files into the sd storage. Do you guys know what i need to put for stock, out-of box image?
I need to reset this to factory setting and root the phone.
I did some serach but the file needed to download is not working anymore. anyone know? thank you
rongsokan said:
ok i got it. now i could put files into the sd storage. Do you guys know what i need to put for stock, out-of box image?
I need to reset this to factory setting and root the phone.
I did some serach but the file needed to download is not working anymore. anyone know? thank you
Click to expand...
Click to collapse
Here is a thought... read some more before messing with your phone instead of asking questions which have been already answered many times.
Sent from my Nexus S 4G
I have been reading reading again... the whole day today. I just dont want to install the wrong drive or file. for nexus s tehre is so many version. the one i got for bootloader is i9020xxka3
for baseband version- i9020xxkf1
fastboot mode stil showing- NO BOOT OR RECOVERY IMG
I give up may be I am too idiot.
obsanity said:
Here is a thought... read some more before messing with your phone instead of asking questions which have been already answered many times.
Sent from my Nexus S 4G
Click to expand...
Click to collapse
Coming from someone that also finds conditions & situations similar but not precisely like my own in the multitude of answered threads..... Some of us can get to a certain point but get stuck, and since these are devices we need to work we want to be sure we don't do something to turn an expensive device into a pretty paperweight.
You learned by fiddling and asking questions did you not? If you are sick of the same old question don't answer the thread.
Sorry, I have no great advice for the OP, you aren't an idiot you are uninformed [just yet] of the proper fix for your problem. I'm still trying to fix something myself so the couple of snipes hit a nerve this morning.
I read read read and read again, its been almost a week. Good god I cant get the solution or may be i dont undderstand it. I try go to cmd prompt and "type fast boot lock" to get it rooted. No luck
my phone situation:
No back up or recovery ( I wipe all sd/back up/system)
fasboot mode-no boot or recovery img
Lock state- unlocked
can only go into clockwork mod
my Goal: lock the phone and flash it to factory stock setting.
I just own nexus s for 7 days and did a ton of research coz stuck at google X animation keep loading and install MIUI and unroot the phone. Soooo stupid of me now that I broke the warranty. Softkeys is no even working!!!!!! when i suscessfully get into the phone.
is there a proper step by step to do this? is there any expert here that can point to the right direction? I am checking this post every 5 minutes
Clearly this is too much phone for you.
Sent from my Nexus S 4G using xda premium
Ok I'll try to help you.
According to what I gather from your posts, you've been successful in unlocking the bootloader and managed to flash CWM recovery, that's a good first step.
Your goal is still unclear. Ok, you want to re-lock the phone and 'restore to factory stock settings'? Does that mean you want a stock firmware on your phone or would you settle for a custom firmware, like Cyanogenmod or MIUI? Either way, visit the Nexus S Development forum, there's a full list of firmwares , just pick whichever you want and download that.
Here's a fantastic topic with a list of all firmwares and also plenty of links to guides:
http://forum.xda-developers.com/showthread.php?t=1067813
Enter CWM recovery mode (VolumeUP + Power button and select Recovery in the Bootloader options).
Go to mounts and storage. We want to mount or SDcard so we can transfer files from the PC to the SDcard as a USB mass storage device. Make sure the phone is connected through USB.
So, select the option: - mount USB Storage. Wait for a few seconds, it takes a while to get initialized by the PC.
Once it's recognized by your PC, copy the downloaded firmware to the SDcard. It should have a .zip extension and be approximately 100mb (of course depending on which flavour you picked, but that's somewhat the standard).
Once it's copied, go back in the CWM main menu and select "Install zip from sdcard". If you want, you can first wipe your cache and Dalvik cache, but since you clearly wiped everything already this shouldn't be necessary, so anyway; install zip from sdcard and select your firmware.zip file. Select it and press the power button to execute the install.
It will install the firmware plus the kernel that it's packed with, all this should be enough to get your phone booted. So reboot your phone and it should work.
Once you've successfully booted into your device, you can do whatever you like. If you want to lock the bootloader again though, you'll need to reverse the steps you took to unlock it. This is through ADB and Fastboot. But this topic explains it step by step and in detail, all credits to the OP: (http://forum.xda-developers.com/showthread.php?t=875630).
If the bootloader is locked again, you shouldn't have any issues with the warranty. It's a Nexus...
Some of your posts were a bit contradictory so I can only assume what your current status is with your phone.
Maybe you should also understand what everything means and does instead of blindy formatting disks and running random commands. Learn what ADB is, learn what Fastboot does. See how the bootloader works and where the recovery comes in, read up on the different firmwares and what kernels do. It might seem like a big investment of your time, but it will help you understand the boot process of the Nexus.
Good luck,
Greetz

[Q]Softbricked with no ADB or sdcard function ARGH!

NS4G
Will boot to fastboot and recovery
CWMR Touch 6.0.1.0
Situation:
My device started bootlooping after about a week of random restarts and freezes. I had just flashed BlackBean and now this, so I decided I was just going to flash a new ROM/Kernel combo. I remembered someone saying I should format /system to install the specific ROM, but I'm fairly sure I formatted /boot along with it, like an idiot. FYI - Fast Charge and a build.prop tweak to set permissions on boot was enabled when this happened. So then I try and flash a new ROM/Kernel combo to fix my bootloop and it wouldn't read the sdcard afterwards. Now it boots straight to fastboot everytime. Toolkit seems to be able to do some things via USB control like reboot the bootloader, but it does not detect an ADB device when I run the driver check or try to restore my CWM backup. I ran the stock+unroot option in Toolkit (was going to send it in thinking the sdcard thing was hardware at first) and it seemed to have went through the whole process correctly... Until the end when it did not reboot automatically like it should have. After doing this, I now get "STANDARD_SET_CONFIGURATION" on the phone when I insert the USB cord while in fastboot. It did not do this before, whether it is the new cord or the flash I do not know. My old cord WAS having problems with data though.
Problem:
I now have no USB debug or SDcard functionality. I assume because of missing files on /boot. I can mount nothing (except cache, but the PC doesn't recognize) without getting a "can't mount" error. This puts a serious dent in my novice ability to fix it. Anything in Toolkit that runs via ADB commands doesn't seem to work properly because it says the device is not in debug mode. PDAnet USB Drivers seemed to install without a hitch and device is recognized on my PC.
Errors:
When trying to mount ANYTHING except the cache while in CWM, I only get: "E:/ Can't mount /sdcard/".
If I try to mount USB storage I get: "E:/ Unable to write to ums lunfile (No such file or directory)Error mounting /sdcard!"
If I try to run any one click methods that use ADB I get: "Daemon not running* No ADB device detected. Make sure you have debugging enabled on your phone"
The log in CWM recovery always shows: "I: Set boot command "" failed to open /sys/class/android_usb/android0/state: No such file or directory" over and over (as many times as I tried to mount something while in recovery for that session)
Questions:
Do you think USB Fast Charge or having the build.prop tweaks enabled could have done something to USB debug? Is there a way to at least just fix the USB Debug problem? Am I correct in assuming that wiping the /system along with the /boot folder is what caused me to not be able to mount the /sdcard to flash another ROM? Is there a way to push the files I need onto the device to restore sdcard function and flash another zip?
Also, what fastboot do I need to be in to do the StockROM+Unroot method in the Toolkit? I have two. Only hold Vol Up/Power takes me to "FASTBOOT". Holding both Volumes+Power puts me into "FASTBOOT - NO BOOT OR RECOVERY IMG"
What is the difference?
I only ask because the Toolkit wants me to hold both volumes and up to get into bootloader mode, but they describe a big green "Start" with an android lying on it's back, mine does not look like that. It simply looks like regular fastboot, but says "FASTBOOT - NO BOOT OR RECOVERY IMG" instead.
It seems you messed with the ROM zip with some tool. Sorry could read your lengthy post completely.
I just want to know one thing clearly, what is the problem basically? where are you stuck?
Edit - Made it as concise as I could, hope it helps. Sorry for length.
Basically, the phone has a formatted /boot, /data, /sdcard, /system, dalvik cache, and I can't seem to use any of the flashing tools via Toolkit in Fastboot mode because the Toolkit says it "cannot find ADB device" please enable "debug" mode. Even when I run the driver check, it says ADB Device Not Found. Though I do have some control of the device via USB (I can use Toolkit to soft reboot from the bootloader) telling me my drivers are probably OK? I couldn't flash any ROM zips (or anything, even backups on the device) because I lost /sdcard functionality.
After a bunch of reading last night, it seems I want to Push a backup of /system and /boot onto the device, which should then restore USB functionality and allow me to flash a ROM... Right?
DizturbedOne said:
Edit - Made it as concise as I could, hope it helps. Sorry for length.
Basically, the phone has a formatted /boot, /data, /sdcard, /system, dalvik cache, and I can't seem to use any of the flashing tools via Toolkit in Fastboot mode because the Toolkit says it "cannot find ADB device" please enable "debug" mode. Even when I run the driver check, it says ADB Device Not Found. Though I do have some control of the device via USB (I can use Toolkit to soft reboot from the bootloader) telling me my drivers are probably OK? I couldn't flash any ROM zips (or anything, even backups on the device) because I lost /sdcard functionality.
After a bunch of reading last night, it seems I want to Push a backup of /system and /boot onto the device, which should then restore USB functionality and allow me to flash a ROM... Right?
Click to expand...
Click to collapse
Your storage memory is completely inaccessible?
Yes, no way to access it via CWM. ADB stuff does not work either. It seems Fastboot stuff DOES. I would like to find a boot.img and system.img to flash via Toolkit (I believe toolkit uses fastboot or odin for these) to see if that would work for me. Any ideas?
It seems like the easy nature of unlocking, rooting, and customizing this phone leads to less of these kind of discussions, I can usually find many files and discussions pertaining to this for HTC phones, but never for this phone.
My bootloader version is KE1, but my baseband version is LF2, makes no sense to me.
The KE1 bootloader was when I was on ICS, but the LF2 baseband was from Jellybean... wth?
Do you think the time I flashed "stock+unroot" on the toolkit that it only partially took? (I did try to back it up to ICS because the Jellybean download didn't work). It seemed as if it flashed everything via fastboot, but never restarted at the end and still won't boot when done.
same problem kinda
i am having the same problem as this with my nexus. mine started after i downloaded Jellybean.it worked fine for about 1 month. i had changed nothing but when i would change my battery or restart my phone it would get stuck at the google screen every now and then, then it started more often. i could normally pull the battery and restart it and it would work after a couple of times doing that. but now this last time i tried that the phone wouldnt go past google screen at all. i can access my clockwork mods recovery but when i try to install zip from sd i get the error cant load sd i have tried everything i know and cant get nothing to work. please help. i miss my nexus this prevail is too slow and small...
Your drivers don't seem to be installed properly.
Get that right, then you can reflash your recovery via fastboot, then you can mount your usb and transfer anything (rom kernel gapps etc etc)
Edit: oh and Bamamac82, that's not the same problem at all. Create a topic of your own.
polobunny said:
Your drivers don't seem to be installed properly.
Get that right, then you can reflash your recovery via fastboot, then you can mount your usb and transfer anything (rom kernel gapps etc etc)
Edit: oh and Bamamac82, that's not the same problem at all. Create a topic of your own.
Click to expand...
Click to collapse
@ polobunny - There is no way for me to install them more properly if I can't go into debug mode to install them though... I wiped out ALL drivers and manually reinstalled the drivers from PDAnet that had previously worked perfectly on my device. But now it never installs as Nexus S, only as Samsung ADB Interface or some such. I've tried it with PDAnet drivers and the Samsung drivers and have followed every driver install guide on the web... Any other suggestions on how to do this properly? I was even thinking of installing a Google SDK just to see if the drivers would work better...
@ Bamamac82 - Yes, that is pretty much the exact same problem, with the exception of the fact that you didn't wipe the /boot partition as I did. But yeah, I installed a JB ROM, it got a few random restarts, froze up twice, then one morning got stuck in a bootloop after I pulled the battery on a freeze up. Not having a working USB cord at the time botched me, because I couldn't get my drivers reliably installed before anything happened, I was using AirDroid because my OEM cable wasn't working with data reliably.
I totally thought the sdcard problem was because I formatted /boot in a hasty ROM flash though. Could I be wrong here?
DizturbedOne said:
There is no way for me to install them more properly if I can't go into debug mode to install them though... I wiped out ALL drivers and reinstalled the drivers from PDAnet that had previously worked perfectly on my device. But now it never installs as Nexus S, only as Samsung ADB Interface or some such.
And Bamamac82 has the exact same problem, with the exception of the fact that he didn't wipe the /boot partition as I did. But yeah, I installed a JB ROM, it got a few random restarts, froze up twice, then one morning got stuck in a bootloop after I pulled the battery on a freeze up.
I totally thought the sdcard problem was because I formatted /boot in a hasty ROM flash though. Could I be wrong here?
Click to expand...
Click to collapse
When you're in fastboot mode on your phone, on your windows PC point the unknown device or the device with an exclamation/question mark to the path where the .inf for the drivers are located. If it still doesn't detect it, you can always try and force it to install a certain device (adb debug bridge or something of the sort).
Once that is done as I said you won't have any problem fastboot'ing to your phone and doing the other steps. Windows drivers and especially the adb drivers can be finnicky.
Your SDcard problem has nothing to do with the fact your formatted boot partition though, those are not linked.
Edit: Oh and I know there is some people, namely with NS4Gs, that had issues with the drivers. I believe for some reason there's some missing IDs in the inf making it impossible to install automatically. Forcing it should work though.
Polobunny thank you so much for your help so far. My device has been softbricked for a week and I'm using a HTC Hero for now! It's atrocious. I'm going to try as you said when I get home tonight and will update if fastboot allows me to flash after that.
Any idea where I can get all the .img's I need? I can only find the complete .tgz for IMM76D (which is fine for now just want it back to working state) and don't know how to extract .img's from it. Can't even find the complete .tgz for JRO03R though, the link is always down. At this point, all I want is a factory img to start from so I can upgrade to JRO03R, root it, and then make a fresh NAND backup from there.
If I were you, I would download Odin, a factory image from Google (just search nexus s factory image), the SDK tools (Google it) and would "reset" the phone.
You will easily find a guide for Odin. Then you'll just have to follow it and your nexus should be fine (but it will be factory reseted and you will have lost all your data )
Sent from my Nexus S using xda premium
Sorry guys, have been putting late hours in at work and haven't had much time until this weekend.
@BenHeng, that's what I am about to look into tonight. I didn't want to learn an entirely new aspect to restore this, I have been limited on free time and am starting to think it will be less hassle than dealing with this.
Only caveat to that, is that I definitely would like to know what happened to cause the SDCARD problem, because that was the main problem that got to me here, would like to prevent that from happening again.
ADB
Make sure ADB debuging is checked under Developer options
localpagefirst said:
Make sure ADB debuging is checked under Developer options
Click to expand...
Click to collapse
Please read the thread before replying.
@polobunny - I did a complete manual install of the RAW drivers, and got it to recognize properly as a Nexus S, as it did when USB Debug and everything worked correctly... But it still does not recognize it as an ADB device when running a driver check.
Is it safe to continue forward with a flash via ODIN in this state?
Hi, I don't understand why you want to use ODIN, fastboot commands still don't work after you installed correctly your driver?
Anyway you can find all (new and old) originals google image here:
http://www.randomphantasmagoria.com/firmware/nexus-s/
Listen mate, the best way would be to flash the factory image via fastboot in bootloader mode. Follow this simple step to step guide.
If you have any issues. post them there on the blog post itself :good:
DizturbedOne said:
Please read the thread before replying.
@polobunny - I did a complete manual install of the RAW drivers, and got it to recognize properly as a Nexus S, as it did when USB Debug and everything worked correctly... But it still does not recognize it as an ADB device when running a driver check.
Is it safe to continue forward with a flash via ODIN in this state?
Click to expand...
Click to collapse
Please, please don't use a shi**y 1-click package thing. There's no driver check to be done other than using adb and typing "adb devices". Do it manually and report the results. It should show your adb device ID, a long string of number and letters.
polobunny said:
Please, please don't use a shi**y 1-click package thing. There's no driver check to be done other than using adb and typing "adb devices". Do it manually and report the results. It should show your adb device ID, a long string of number and letters.
Click to expand...
Click to collapse
I get nothing when I do that. It says "List of devices attached" and a blank line underneath. When I plug the USB in during fastboot I get "STANDARD_SET_CONFIGURATION" at the bottom, which I never get until I install the drivers.
It seems as if the computer must recognize the device in debug mode in some way to properly install the drivers.
Why is my sdcard partition unable to be written to? This never would have been a problem as I always keep a couple backup ROM's on the phone. Either way, it seems as if all of this is for nothing if the phone will not allow me to read/write to the memory in the device.

Phone won't boot up

I was trying wipe everything on the phone but for some reason it saids no OS. So when it boots up, I only see the google word on the screen.
Trying to flash the stock rom, followed instruction to install adb drivers...etc then boot the phone into fastboot mode,. This is the one screen I can get so far. Looks like my pc can't detect my phone. it saids failed when running those commands...Can someone give me a hint what to do next?
All I want is to put the stock rom back in.
thx
you didnt wipe data, you wiped your system partition, wiped the rom off your phone. and that screenshot is the stock recovery. you need to boot into the bootloader to flash the factory img(stock). the bootloader is the same as fastboot mode.
I did wipe data. I remember I checked that box
I also got this error in the command line.
simms22 said:
you didnt wipe data, you wiped your system partition, wiped the rom off your phone. and that screenshot is the stock recovery. you need to boot into the bootloader to flash the factory img(stock). the bootloader is the same as fastboot mode.
Click to expand...
Click to collapse
benzso63 said:
I did wipe data. I remember I checked that box
I also got this error in the command line.
Click to expand...
Click to collapse
before you tried any code.. did you do "fastboot devices" first, to make sure fastboot sees your phone?
also, sounds like you used twrp recovery. if you just swipe on the wipe screen, it wipes your partitions. if you chose advanced, then it gives you a list of things to wipe, then all you'd do is choose data and wipe.
I power down the phone, hit vol down + power. And I see the Fastboot mode
I connected the usb cable to my pc, but when I ran the code, it saids device not found. My pc can't see it
Now I am not using twrp at all just want to at least have the fastboot mode see my pc. but it is not.
Any other step i can make the phone communicate to my pc ?
simms22 said:
before you tried any code.. did you do "fastboot devices" first, to make sure fastboot sees your phone?
also, sounds like you used twrp recovery. if you just swipe on the wipe screen, it wipes your partitions. if you chose advanced, then it gives you a list of things to wipe, then all you'd do is choose data and wipe.
Click to expand...
Click to collapse
benzso63 said:
I power down the phone, hit vol down + power. And I see the Fastboot mode
I connected the usb cable to my pc, but when I ran the code, it saids device not found. My pc can't see it
Now I am not using twrp at all just want to at least have the fastboot mode see my pc. but it is not.
Any other step i can make the phone communicate to my pc ?
Click to expand...
Click to collapse
you're going to have to install that driver first, before it'll see your phone. you are using windows? try koushes universal adb driver for windows http://www.koushikdutta.com/post/universal-adb-driver
I did. I installed it. I have tried different drivers.
If I goto device manager, Android Device and under that it saids "Android Bootloader Interface".
I don't see anything saying Nexus or so.
simms22 said:
you're going to have to install that driver first, before it'll see your phone. you are using windows? try koushes universal adb driver for windows http://www.koushikdutta.com/post/universal-adb-driver
Click to expand...
Click to collapse
benzso63 said:
I did. I installed it. I have tried different drivers.
If I goto device manager, Android Device and under that it saids "Android Bootloader Interface".
I don't see anything saying Nexus or so.
Click to expand...
Click to collapse
If everything else fails try lg flashtool as a plan B. Link in my signagure.
Will try everything you say. Also this is a screen capture.
When I put the phone in fastboot mode, I notice this pops up under device manager (screen shot)
So does it mean it detects the phone right? But for some reason when I run the command code, it saids device not found.
bitdomo said:
If everything else fails try lg flashtool as a plan B. Link in my signagure.
Click to expand...
Click to collapse
benzso63 said:
Will try everything you say. Also this is a screen capture.
When I put the phone in fastboot mode, I notice this pops up under device manager (screen shot)
So does it mean it detects the phone right? But for some reason when I run the command code, it saids device not found.
Click to expand...
Click to collapse
It means you installed the drivers right.
Reboot your PC, try other USB port, close any unecessary apps in the background, avoid USB3.0 ports or run the flash-all.bat in administrator mode. These are the ideas that have come into my mind in this moment.
Oh by the way I was following your link.
RIght now my phone has the screen firmware update. do not unplug.. the usb connection until the process is complete....
Then follow the rest of your instructions.
Now how do I Enter your phone to Download Mode. ? Right now still with this screen "Firmware update".
bitdomo said:
It means you installed the drivers right.
Reboot your PC, try other USB port, close any unecessary apps in the background, avoid USB3.0 ports or run the flash-all.bat in administrator mode. These are the ideas that have come into my mind in this moment.
Click to expand...
Click to collapse
benzso63 said:
Oh by the way I was following your link.
RIght now my phone has the screen firmware update. do not unplug.. the usb connection until the process is complete....
Then follow the rest of your instructions.
Now how do I Enter your phone to Download Mode. ? Right now still with this screen "Firmware update".
Click to expand...
Click to collapse
When you see "Firmware update" that is the download mode. Watch the video I made. Maybe it explains everything more.
I got that part. Now I am using the LG Flash Tool, port 1 com41. I clicked the yellow arrow and screen showing it is ready. But on the phone I don't need any progress at all, it is till 0%. would it automatically run it itself ?
bitdomo said:
When you see "Firmware update" that is the download mode. Watch the video I made. Maybe it explains everything more.
Click to expand...
Click to collapse
benzso63 said:
I got that part. Now I am using the LG Flash Tool, port 1 com41. I clicked the yellow arrow and screen showing it is ready. But on the phone I don't need any progress at all, it is till 0%. would it automatically run it itself ?
Click to expand...
Click to collapse
What is shown on the PC?
Bro, now its running. I moved to usb 3.0 port. will keep you posted
Confirmed. Working Flawlessly ! OMG, you are my life saver. Really appreciate your hard work.
Man, you are the BEST !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
bitdomo said:
What is shown on the PC?
Click to expand...
Click to collapse
benzso63 said:
Bro, now its running. I moved to usb 3.0 port. will keep you posted
Confirmed. Working Flawlessly ! OMG, you are my life saver. Really appreciate your hard work.
Man, you are the BEST !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Your welcome.
You need to open a Master Class LOL. Seriously, you have no idea how frustrated when you can't get the phone to work.
bitdomo said:
Your welcome.
Click to expand...
Click to collapse
benzso63 said:
I was trying wipe everything on the phone but for some reason it saids no OS. So when it boots up, I only see the google word on the screen.
Trying to flash the stock rom, followed instruction to install adb drivers...etc then boot the phone into fastboot mode,. This is the one screen I can get so far. Looks like my pc can't detect my phone. it saids failed when running those commands...Can someone give me a hint what to do next?
All I want is to put the stock rom back in.
thx
Click to expand...
Click to collapse
if your pc cannot detect your phone , it seems you havn't install driver.

Black screen and nothing else...

Lets make a long story short, i just got my OPO, as an advanced android user i desided to put
ParanoidAndroid 4.6, but before I installed custom bootloader (TWRP) and rooted it. Since i am installing new ROM i did a backup and then i needed to wipe my device, by accident i wiped everything from my phone, including backup and new ROM. I was left with TWRP (It is my 1st android phone without sdcard so i started to panick), then i started it in fastboot mode, to check if I can copy ROM again from my pc, but it didnt work. Then i went to restart options in TWRP and choose restart in recovery mode, then my phone turned off. Apperently it did restart but now my screen is just black and I cant do anything with it. I was holding power button, then with volume up, then with volume down, no result. When i connect it to my PC i hear sound that phone is connected but still nothing is happening. Please help me what should I do. My guess is when i pressed to restart in recovery mode, it wasn't meant to be the custom one, so it tried to open one that dosen't exist. My phone was charged 40% when i was doing that.
Note1: Unknown USB Device (Device Descriptor Request Failed), this is what i get when I check Device Manager.
Many suggestions were made so far none of them help. Hope someone will help me here!
First, TWRP isn't a custom bootloader, it's a custom recovery. The phone can't 'open a recovery that doesn't exist', it opens whatever recovery you have installed at the time. Make sure the phone is powered off (hold power for about 10-15 seconds), then try booting into recovery again (hold power + volume down).
Transmitted via Bacon
Looks like you're using windows from the looks of you writing Device Manger so if you can boot back into fastboot then you're still okay!
Download this then just use the Flash CM11S option and it should bring you back to life.
Tool kits are amazing bro. Even as an advanced user myself they are still my favorite tools to use.
There is another problem
bigballa said:
Looks like you're using windows from the looks of you writing Device Manger so if you can boot back into fastboot then you're still okay!
Download this then just use the Flash CM11S option and it should bring you back to life.
Tool kits are amazing bro. Even as an advanced user myself they are still my favorite tools to use.
Click to expand...
Click to collapse
I tried all of the toolkits and fastboot, the problem is that i cant even see device when I type adb devices in cmd.
Only 1 thing
I just need to fix how to find device in adb and then it will be very easy.
Mod Edit: quoted post removed.
---------- Post added at 05:20 PM ---------- Previous post was at 05:16 PM ----------
[/COLOR]
Gapkobob said:
I tried all of the toolkits and fastboot, the problem is that i cant even see device when I type adb devices in cmd.
Click to expand...
Click to collapse
Gapkobob said:
I just need to fix how to find device in adb and then it will be very easy.
Click to expand...
Click to collapse
My friend you're in a bit more trouble than I think you realise you're in. Your device is showing up as QHSUSB_BULK in Windows, which means it's technically bricked. I believed you can save it though, have a look in this thread, you're gonna need to read through it all to find the solution you need. Let me know how you go.
Transmitted via Bacon
Simple driver issue.
The following steps will solve your problem: https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/
Solved !!!
Solved thx to everybody. http://forum.xda-developers.com/one...een-fastboot-adb-t2835696/page16#post55129486 this helped
Great news.
Transmitted via Bacon

[Q] Oneplus won't start anymore...

Hello all,
My oneplus one (64gb black) wont start anymore.
How did this happen?
Well,
yesterday after some trouble on my oneplus i tried an factory reset but my TWRP got stuck,
so i started the phone which was still fully working and wiped this: dalvik cache, system, data and cache
But because of that i didn't had a OS anymore ( i didn't know this was going to happen)
So i tried to install CM11 through fastboot commands but every time i got CRC errors in CMD.
So i tried it again and suddenly my phone wouldn't turn on anymore.
I charged it then for 12 hours but still didn't work.
Fastboot wont work, recovery won't work, it doesn't charge ( or atleast i cannot see it on the screen and on the led)
I tried to powercycle it but that doesn't work either.
Can anyone help me please?
Thanks!
BTW: Sorry for the bad english.
Maybe it could help to press the power-button for a long time. That's not a joke Try holding it for a least 10 seconds.
TriKE27 said:
Maybe it could help to press the power-button for a long time. That's not a joke Try holding it for a least 10 seconds.
Click to expand...
Click to collapse
Thanks for the answer but that doens't work either.
And what did you think that will happend when you wiped "system" partition?
I also bricked oneplus when I tried to revert to stock CM11 by flashing one-by-one cm11 partitions, but I found thread about unbricking phone using ColourOS firmware.
Look at this thread: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
rtomakov said:
And what did you think that will happend when you wiped "system" partition?
I also bricked oneplus when I tried to revert to stock CM11 by flashing one-by-one cm11 partitions, but I found thread about unbricking phone using ColourOS firmware.
Look at this thread: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
Thanks for the answer and yes i know but i was not thinking about it when i did that.
But i did what you said but the tutorial says this:
You can now proceed to install unsigned drivers from the file you downloaded. Open Device Manager, you should be seeing ugly yellow warning under other devices for QHUSB_BULK. Right click on the name and select Update Driver Software > Browse my Computer for driver software.
But the problem is that my pc doesn't recognize anything so i cannot see it in device manager.
Thanks
bboy521 said:
Thanks for the answer and yes i know but i was not thinking about it when i did that.
But i did what you said but the tutorial says this:
You can now proceed to install unsigned drivers from the file you downloaded. Open Device Manager, you should be seeing ugly yellow warning under other devices for QHUSB_BULK. Right click on the name and select Update Driver Software > Browse my Computer for driver software.
But the problem is that my pc doesn't recognize anything so i cannot see it in device manager.
Thanks
Click to expand...
Click to collapse
Can you see your phone in modems or ports section of device manager?
rtomakov said:
Can you see your phone in modems or ports section of device manager?
Click to expand...
Click to collapse
Thanks for the answer!
My phone is working again! Jeejj
The problem was the unknown device at device manager, so what i did was disconnecting my phone from pc and then press the power button for 1 min, connect it back and then the device manager recognized it!
I'm now flashing it back to exodus rom!
Thanks all!!
I have this situation before, wiping everything dalvik/cache/system/data and internal storage. So my phone has nothing, just few empty file. Now how do I solve it ?
Simply I boot into TWRP. Luckily the driver detect my phone after I connect to pc so I open internal storage, copy the rom and gapps and put em on TWRP folder. Then just go to install on TWRP and look for the folder and voila, flash and phone back to healthy state.
Never ever ever delete that internal storage again lol.
Indeed man
But with me TWRP wasn't available either so yea...
It wont happen again haha
But thanks bro!

Categories

Resources