Develop Bugs

[Q] Flash back from IMM30B to 4.0.2 for new leak

Hey guys, first time on here and im kinda a noob when it comes to the rooting stuff (ive done a few things but nothing hardcore) and i need some help getting onto this (IMM76K) update (and not sure if this is the right thread to put this in). A few weeks ago i unlocked my bootloader and (after some of the same issues im having now) temp booted into CWM and installed the 4.0.4 IMM30B update. Now with this new update, i wanted to get it installed or flash back to get the OTA (not sure if i can get the OTA on the leak update)
But, everytime i try to boot into CWM again (using this toolkit: http://forum.xda-developers.com/show....php?t=1614827) i constantly get fail messages. And it happens if i try to boot into CWM or try to flash the factory 4.0.2 update.
With the phone on and trying to use these (http://www.droid-life.com/2011/12/16...factory-state/) instructions, i constantly get the error "sending 'bootloader'... FAILED (remote: Invalid Command)". Im already in the fastboot bootloader.
With the toolkit, it wont start the factory img flash if the phone is on, and if im in the fastboot bootloader, it says it "fails" to boot into the bootloader (which, again, im already in) and fails to install all the img files and then just boots back into the older 4.0.4 leak.
I havent rooted my phone (but i tried that to get past this problem but i get the same error messages), only unlocked the bootloader. Sorry for the long post and if it seems like a block of text. This is just starting to really frustrate me. Thanks

Do you have ADB installed on your computer? It's hard to troubleshoot your problem if you don't.

Yea, i do. Im in school for programming and have installed all the android SDK stuff and eclipse since i want to make android apps/games (hopefully). I downloaded the fastboot.exe file and have it in the platform-tools folder with the adb.exe file

Go here (https://developers.google.com/android/nexus/images) and download mysid for Gnex.
It's gzipped so you will need to extract those files using 3rd party software (winzip works nicely).
Boot your phone normally. Connect to your computer and open a command prompt.
Type 'adb devices' and note the result.
Type 'adb reboot bootloader' and wait for the phone to enter the bootloader.
Once there type 'fastboot devices'.
If you don't get a response you have a driver problem. You need to DL the samsung driver.
If you do, flash each zip file in that package you DL'ed from google.
Start with 'fastboot flash bootloader <location of bootloader zip>'
Then, 'fastboot flash radio <file>'
ect. until you've flashed all the zip files. (Exactly like the instructions in your link but replace the files they gave you with the ones from google.)
Post here if you get an error message.

Ok, everything is fine until i get to flashing the bootloader, heres what i get (sorry it isnt an image)
D:\Android\android-sdk\platform-tools>adb devices
List of devices attached
0146A5B30300B014 device
D:\Android\android-sdk\platform-tools>adb reboot bootloader
D:\Android\android-sdk\platform-tools>fastboot devices
0146A5B30300B014 fastboot
D:\Android\android-sdk\platform-tools>fastboot flash bootloader bootloader-toro-
primekk15.img
sending 'bootloader' (2308 KB)... FAILED (remote: Invalid Command)
finished. total time: 0.001s
D:\Android\android-sdk\platform-tools>
This is what happens even when i use a toolkit to do it for me. Ive used the toolkit to reinstall the drivers a bunch of times and it still happens

Did you relock the bootloader? Type 'fastboot oem unlock'
---------- Post added at 09:07 AM ---------- Previous post was at 08:57 AM ----------
If that's not it then it's a driver issue.
Uninstall the ones you have (Control Panel -> Device Manager) and go to http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW? and install the samsung ones.
If you have problems with that I can walk you though it.

The only thing i was able to do from the toolkits was lock/unlock the bootloader (tried that last night using the toolkit to see if it fixed any problems). ill try installing the drivers and see what happens, thanks
edit: *I locked the bootloader last night and unlocked it again right after

blipp said:
The only thing i was able to do from the toolkits was lock/unlock the bootloader (tried that last night using the toolkit to see if it fixed any problems). ill try installing the drivers and see what happens, thanks
edit: *I locked the bootloader last night and unlocked it again right after
Click to expand...
Click to collapse
1) Throw away the toolkit;
2) Uninstall all drivers;
3) Install these drivers;
4) Make sure your bootloader is unlocked;
5) Open a command prompt in the directory where your both your fastboot file and CWM are located;
6) Reboot your device into fastboot mode (vol+ & vol- & power), and plug into your PC;
7) Make sure your device is recognized by your PC: fastboot devices
8) Flash or boot CWM
a) Flash by typing: fastboot flash recovery cwm.img
b) Boot by typing: fastboot boot cwm.img

sorry for being a noob at this, but where do i put the Universal Naked Driver stuff? Do i have to extract them to a specific folder? Im trying to install the drivers from the samsung website first though
Im not using the toolkits anymore and am trying to follow your instructions for the command prompt

blipp said:
sorry for being a noob at this, but where do i put the Universal Naked Driver stuff? Do i have to extract them to a specific folder? Im trying to install the drivers from the samsung website first though
Im not using the toolkits anymore and am trying to follow your instructions for the command prompt
Click to expand...
Click to collapse
Extract the zip to a directory. Plug your device in fastboot mode to your PC. Open device manager and find the phone. Right-click on it and select update driver. Select install yourself or whatever the option is, and navigate to the folder where you extracted the zip. I've found that those drivers are better than the Samsung-packaged drivers.

Also, do one or the other, but not both. Make sure you remove the old driver before you start the new.
In windows 7 you're gonna want to go to (install Universal Naked Driver)...
Control Panel -> Hardware and Sound -> Device Manager
In the list click the driver for your phone. It will either be in the USB list or listed as some kind of phone. Right-click and uninstall the driver. Reboot. Go back to device manager. Plug in device. Click update driver software when your device shows up. Then 'Browse my computer'. Then 'Let me pick from a list'. Then 'Have Disk'. Find the .inf files and windows will install the driver.

ok, i extracted the Universal zip into its own folder on the desktop, after i uninstalled the drivers and rebooted my PC, i plugged in the phone, waited for it to show up, and went to update the drivers. I got to the "Have Disk" and selected both of the .inf files that were in the extracted folder. Both of them caused a popup that said that folder didnt contain the drivers for my device.
When im in the fastboot bootloader the phone doesnt show up in my Device Manager. Is that a problem?
Thanks for helping me through this, my last phone was a Droid X and all i ever had to do was hold vol down and power and it got me to a recovery screen like CWM and i could install an update.zip.

blipp said:
ok, i extracted the Universal zip into its own folder on the desktop, after i uninstalled the drivers and rebooted my PC, i plugged in the phone, waited for it to show up, and went to update the drivers. I got to the "Have Disk" and selected both of the .inf files that were in the extracted folder. Both of them caused a popup that said that folder didnt contain the drivers for my device.
When im in the fastboot bootloader the phone doesnt show up in my Device Manager. Is that a problem?
Thanks for helping me through this, my last phone was a Droid X and all i ever had to do was hold vol down and power and it got me to a recovery screen like CWM and i could install an update.zip.
Click to expand...
Click to collapse
What OS are you running on your PC?

Windows 7

blipp said:
Windows 7
Click to expand...
Click to collapse
Ok, try this: go into the directory where you unzipped the drivers. Right-click on android_winusb.inf and select install.

Get an error popup - "The INF file you selected does not support this method of installation"

blipp said:
Get an error popup - "The INF file you selected does not support this method of installation"
Click to expand...
Click to collapse
Hmm. Not sure what is going on.
Let's try this step-by-step:
Boot your device into fastboot mode, plug into your PC, and open up device manager. Does your PC recognize your device? What does it show in task manager?

Nothing Shows up in device manager. The "imaging devices" section is opened by default. In the "devices and printers" window, however, there is an "unspecified" device, Android 1.0. Usually the galaxy nexus shows up in the "portable devices" section in device manager. Coins "scan for hardware changes" doesn't cause it to appear either
Sent from my Transformer using XDA

blipp said:
Nothing Shows up in device manager. The "imaging devices" section is opened by default. In the "devices and printers" window, however, there is an "unspecified" device, Android 1.0. Usually the galaxy nexus shows up in the "portable devices" section in device manager. Coins "scan for hardware changes" doesn't cause it to appear either
Sent from my Transformer using XDA
Click to expand...
Click to collapse
Ok, good. Now right click on the Android 1.0 and select "update driver software". Then click on "browse my computer for driver software", then click on the "Browse" button and make sure "include subfolders" has a check.
Now navigate to where you unzipped the drivers and click ok.

Its not giving me that option. Its not in device manager, its only showing in control panel->hardware and sound->devices and printers. Right clicking only gives me Eject, Create shortcut, troubleshoot, and properties. Properties only has General and Hardware. I even went into device manager and checked "show hidden devices" and its still not there. It only shows up now when its actually booted into android
Sent from my Transformer using XDA

[Q] adb Device Offline

I have been searching all over xda and google to try and solve this problem and I'm stuck. I'm trying to unlock the boot loader for my Nexus 7 (2013) that I just got yesterday and I have been following the video guide.
The problem I'm having is that when I do command "adb devices" it shows that my Nexus 7 is connected to my PC (windows 7) but it says "offline" and when I do "adb reboot bootloader" I get the error "device offline".
I have my device in developer mode and I enabled USB debugging in the settings already. In my search throughout the forums and followed the steps to make sure that my drivers were up to date. I tried doing it by manually selecting the drivers and by using the SDK Manager to install the Google USB drivers, neither of these fixed the problem.
I can't figure out what I'm doing wrong, please help!

Have you tried rebooting into the bootloader manually then if "fastboot devices" work?

If you aren't seeing a popup on your tablet when adb tries to communicate with it, then you need to upgrade your adb client to the latest version.
They added some RSA verification step to the adb connection and if you have the old client it just says device offline.
You can update "platform-tools" in the sdk manager or find a download of just the adb, fastboot client and 2 libraries. If I remember the link I'll add it.
Here's the link for just the new ADB and libraries.
http://forum.xda-developers.com/showthread.php?p=43842630#post43842630

Have u checked camera instead of mass storage? That's how I have to do it.
Sent from my Nexus 7 using Tapatalk 4

Sounds like a driver issue.
Make sure you've got the correct drivers installed. Open up Device Manager in Windows 7 and manually update the driver - http://developer.android.com/tools/extras/oem-usb.html

Read the tutorial and watch/follow the video: http://forum.xda-developers.com/showthread.php?t=2382051

Got this on a Mac today, on the first time I connected this device.
Updated to latest android-sdk, re-installed platform-tools, and it worked fine.

sfhub said:
If you aren't seeing a popup on your tablet when adb tries to communicate with it, then you need to upgrade your adb client to the latest version.
They added some RSA verification step to the adb connection and if you have the old client it just says device offline.
You can update "platform-tools" in the sdk manager or find a download of just the adb, fastboot client and 2 libraries. If I remember the link I'll add it.
Here's the link for just the new ADB and libraries.
http://forum.xda-developers.com/showthread.php?p=43842630#post43842630
Click to expand...
Click to collapse
Thanks for the response! I got the ADB part working and now I'm trying to finish with the rooting process.
edit: Only getting "database error" when trying to download the TWRP flashable zip

Forgot10- said:
Thanks for the response! I got the ADB part working and now I'm trying to finish with the rooting process.
edit: Only getting "database error" when trying to download the TWRP flashable zip
Click to expand...
Click to collapse
Are you saying you have a download problem or a flashing problem?
The twrp archive I used wasn't a flashable zip. It was just a zip file with twrp.img archived.
You need to unzip and flash the twrp.img (it has a longer name) using
fastboot flash recovery twrp.img

[Q] Help installing CM11 on My Ouya.

Hi,
I'm attempting to convert my Ouya to a regular Android device and I'm starting to work with the various manuals that exists
in the 'development' section of the forum.
I've performed the following steps:
1. installed the ADB drivers on Windows 7
2. connected the Ouya to the computers and fix the device manager to detect is as ADB driver.
3. checked that the device it detected (using "adb devices" command).
4. executed the 'adb reboot bootloader' command.
at this point the Ouya (with a wired keyboard connected) rebooted and the TV turned black (but it still detect the HDMI).
5. checked if the device is connected in fastboot, using the command: fastboot devices.
6. executed the command: fastboot boot OuyaCWMrecovery6.0.3.2.img
and it stuck in: 'downloading 'boot.img' ...'
Anyone knows what the problem is?

Anyone?
Please!!
section51 said:
Hi,
I'm attempting to convert my Ouya to a regular Android device and I'm starting to work with the various manuals that exists
in the 'development' section of the forum.
I've performed the following steps:
1. installed the ADB drivers on Windows 7
2. connected the Ouya to the computers and fix the device manager to detect is as ADB driver.
3. checked that the device it detected (using "adb devices" command).
4. executed the 'adb reboot bootloader' command.
at this point the Ouya (with a wired keyboard connected) rebooted and the TV turned black (but it still detect the HDMI).
5. checked if the device is connected in fastboot, using the command: fastboot devices.
6. executed the command: fastboot boot OuyaCWMrecovery6.0.3.2.img
and it stuck in: 'downloading 'boot.img' ...'
Anyone knows what the problem is?
Click to expand...
Click to collapse

section51 said:
Anyone?
Please!!
Click to expand...
Click to collapse
Did you try the oneclick install in the android development page?(http://forum.xda-developers.com/showthread.php?t=2350900) Then after that, update your recovery to the latest and then install this.... http://forum.xda-developers.com/showthread.php?t=2692836

jcgagtv699 said:
Did you try the oneclick install in the android development page?(http://forum.xda-developers.com/showthread.php?t=2350900) Then after that, update your recovery to the latest and then install this.... http://forum.xda-developers.com/showthread.php?t=2692836
Click to expand...
Click to collapse
I've used both links that jcgagtv699 sent me and I was able to install the OuyaCWMrecovery6.0.3.2.
From there I've upgraded the version to 6.0.4.8 and start installing the Ouya Bootmenu (http://forum.xda-developers.com/showthread.php?t=2692836)
and after it was installed successfully I get a menu when the ouya is loaded:
Normal boot
Alternate boot
Recovery
Failsafe
Bootloader
but the problem is that on matter what option I choose I get a RED screen with 'install from zip file'.
Help please!!!

Sounds like you only have the Bootmenu installed. From here you need to install cm11 at the "install from zip file" point.

Fastboot doesnt recognize my phone.. Help please!

So i wanted to install CyanogenMod on my xperia z1 Compact that i rarely use anymore.. but in order to do that i need to unlock my bootloader and stuff.. but in order to do that i have to get fastboot to work but whenever i try any commands i get <Waiting for any Device> or nothing at all.. i cant install the driver either (not sure if i install it using device manager but if i do then its failing.. a lot) Anyways any help would be awesome xD

3r0rfadeness said:
So i wanted to install CyanogenMod on my xperia z1 Compact that i rarely use anymore.. but in order to do that i need to unlock my bootloader and stuff.. but in order to do that i have to get fastboot to work but whenever i try any commands i get <Waiting for any Device> or nothing at all.. i cant install the driver either (not sure if i install it using device manager but if i do then its failing.. a lot) Anyways any help would be awesome xD
Click to expand...
Click to collapse
Install this - http://forum.xda-developers.com/showthread.php?t=2588979
Install this - http://www.flashtool.net
After Flashtool installs, go to drivers folder, (in flashtool folder), and run drivers.exe. check boxes for 'fastboot' 'flash mode' and 'Rhine' drivers. When done installing drivers, connect phone in fastboot mode, and you'll get a 'installing device software' popup. Click on 'skip Windows update search', and drivers will install. Then run fastboot commands.

levone1 said:
Install this - http://forum.xda-developers.com/showthread.php?t=2588979
Install this - http://www.flashtool.net
After Flashtool installs, go to drivers folder, (in flashtool folder), and run drivers.exe. check boxes for 'fastboot' 'flash mode' and 'Rhine' drivers. When done installing drivers, connect phone in fastboot mode, and you'll get a 'installing device software' popup. Click on 'skip Windows update search', and drivers will install. Then run fastboot commands.
Click to expand...
Click to collapse
i fixed it cant remember how tho xD

Fastboot interface is missing. Help!

On Device Manager (Window 10). Were updating the driver, I can only see ADB interface but no Fastboot interface. I'm on the latest version SDK from Google and have OnePlus driver installed. I can command ADB but not fastboot. What am I missing? My device is OnePlus 7T TMobile is sim unlocked and I can toggle OEM unlocking and is on.

Not sure what mean, but fastboot only works when you're booted in bootloader. (Adb reboot bootloader)
Sent from my OnePlus7TPro using XDA Labs

That's correct but when I fastboot cmd it get stuck on "waiting for device". So I read around on XDA on how to fix it and I tried to follow the instruction on PC - device manager, still no go.

PesTicide. said:
That's correct but when I fastboot cmd it get stuck on "waiting for device". So I read around on XDA on how to fix it and I tried to follow the instruction on PC - device manager, still no go.
Click to expand...
Click to collapse
I myself have never had this problem, I can only suggestion reinstalling OnePlus drivers.
Hopefully you figure this out
Sent from my OnePlus7TPro using XDA Labs

I reinstalled couple of times. Still no go! This is the first time that this happening. Never had problem since day one on Nexus devices. I'm going to try again and search more around.

You can also use the universal drivers by clockworkmod https://adb.clockworkmod.com/
Here's what I did.
1) Extract the android sdk platform tools and put on your c:// drive
2) Install the universal usb drivers
3) Enable usb debugging on your one plus and connect to computer. Switch to usb debugging mode and accept the popup on your one plus to allow the connection.
4) Open cmd and run "cd C:\platform-tools", then run "adb devices" to ensure that your devices is connected properly
5) Run "reboot bootloader" and device will restart into bootloader mode and fastboot will now work
*This is all assuming that you've already oem unlocked your devices as well already*

It work till fastboot. Still stuck at "waiting for device".

PesTicide. said:
It work till fastboot. Still stuck at "waiting for device".
Click to expand...
Click to collapse
Are you trying to open? Command shell? In windows 10 right? So for your information in windows 10 it's not supported , you have to open that platform tool folder which you installed already named as adb, platform tools , sdk may go into that folder and you will see a folders directory above there .. just click on that and type cmd and hit enter and cmd will pop up now you can use all your commands it's not your fault it's windows 10 fault ..maybe hope it may work for you

That how I done it. Fastboot Command appear on my Google Pixel 2 and 3 but I can't do it on my 7T. I don't get it
Thanks for the help! I tried working on Device Manager on PC yet doesn't work. Adb shell command work but no Fastboot command.

I found the solution! This is what I did and it worked for me! Here's the link for anyone who has the same issue I went through. Here you go and follow the instruction. http://www.wtfandroid.com/fix-fastboot-device-not-recognised-problem/
Mod you can close this thread. Thanks again for everyone who tried to help me. :highfive: