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] Ascend P1 cannot access bootloader/fastboot, cannot root?

Huawei ascend p1 B226
I was follow the steps to root my phone so that i can install CWM on the phone.
But i cannot open fastboot/bootloader mode,
i tried to use the command "adb reboot bootloader" to log into the bootloader mode
but my phone was stuck at the logo.
the device manager also show me an unknown driver "Blaze".
i tried to install the driver "Blaze" into "adb bootloader interface"
but when i check on"fastboot devices"
i only get
"? fastboot"

You're using the wrong drivers for fastboot.
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Or manually load the Google USB driver as shown here:
http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/3/

es0tericcha0s said:
You're using the wrong drivers for fastboot.
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Or manually load the Google USB driver as shown here:
http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/3/
Click to expand...
Click to collapse
i don't get it, i install the installer from the link you gave me, but i'm still get blaze
i can't get the step of getting unknown device "usb 1.0" from 2nd url.

enzo19 said:
i don't get it, i install the installer from the link you gave me, but i'm still get blaze
i can't get the step of getting unknown device "usb 1.0" from 2nd url.
Click to expand...
Click to collapse
Ok, try this:
Extract the adb-setup-1.3.exe like you would a zip file.
Plug in phone while in bootloader mode
Open Device Manager
Follow the directions on the 2nd link, but use the android_winusb you find in the extracted exe /driver folder.
That really should do the trick. If it does not, let us know which version of Windows you are using and if it is 32/64.

Rooted phone, OTA update causes bootloop

All of the drivers are installed on this PC(Windows 10), and it recognizes it as connected in the device manager but it doesn't show up as a drive. ADB doesn't recognize the device so most methods shown here don't work. And the Microsd install doesn't work either(it gives an error shortly after you press power to go into recovery mode). So I'm not sure what else to do. Any hints or suggestions. It's a Z00A device.
Thanks!

Follow this link to add proper drivers to be recognized by sideload and then do adb sideload the whole firmware if you can enter into fastboot.
For bootloop issues,busybox,xposed and viper4fx have to be uninstalled and reinstalled. Good luck.

Grid4 said:
Follow this link to add proper drivers to be recognized by sideload and then do adb sideload the whole firmware if you can enter into fastboot.
For bootloop issues,busybox,xposed and viper4fx have to be uninstalled and reinstalled. Good luck.
Click to expand...
Click to collapse
I downloaded the drivers a month ago when I was rooting the phone in the first place, it worked and was recognized. Are you saying to download additional drivers? Just want to make sure I'm going down the right path.

MRomeo99 said:
I downloaded the drivers a month ago when I was rooting the phone in the first place, it worked and was recognized. Are you saying to download additional drivers? Just want to make sure I'm going down the right path.
Click to expand...
Click to collapse
If you have drivers installed then follow 2nd last post for the pc to recognize phone when adb sideload is started.
Read entire thread as people have gone through what you are facing now.

ADB not working - returns "unauthorized"

As title says, I cannot use adb: "adb devices" returns "UNAUTHORIZED" if I launch command with phone plugged in and in android environment.
If I try in bootloader mode, download mode or recovery mode it returns "list of attached device" like it is empty list and cant see phone.
Phone is M9 ViperOneM9 4.3.0 firmware 3.35.401.12 recovery TWRP 3.0.0.0.
I am using a Win 10 PC where ADB command is perfectly working with my other M9 (ViperOneM9 4.2.1 same firmware as above, TRWP 2.8.7.1).
I read various posts and the problem seems to be the phone not showing the prompt to accept RSA key.
Yes, I am with USB debug ON and install from unknow sources ON (this last is useless but I say the same).
I think to have tried most of everything people suggest in different posts:
- updated and reinstalled android sdk
- deleted adbkey and adbkey.pub in my %user%/.android folder (then it recreates files but still no prompt on phone)
- tried different versions of HTC drivers on PC
- tried different versions of adb (1.0.31, 1.0.32 and also a pre 1.0.30 I dont remember exactly which one)
- tried installing Minimal ADB and Fastboot [4-27-16] http://forum.xda-developers.com/show....php?t=2317790
- wiped everything from TWRP recovery under "advanced" button and reinstalled rom with wipe during aroma installer
- looking in the phone in "system/data/misc/adb" for adb keys files but my folder is empty (checked on my other fully working M9 and that folder is empty too)
- toggled USB debugging on/off rebooting phone and PC
I also tried setting up a virtual machine with Windows 7 but I am not able to install drivers for the phone (yellow triangle in device manager).
Set up a virtual machine with Debian 8.4.0, installed android-tools-sdk, updated last version and "adb devices" here return OFFLINE
What can i do? It is like 7 hour I am trying but nothing is working.
Any help is greatly appreciated.
Thanks everyone

I'm sure that first time using and, a window requesting to authorize your PC pops up on the phone. Have you ever seen this window and authorized the PC. If not you could toggle of USB debugging in developer options, restart phone, toggle debugging on.
Then I'd deactivate display standby, connect phone to PC, in CAD type: adb kill-server and after this adb devices. When the window pops up on your phone agree to it and allshould be fine.
Sent from my HTC One M9 using XDA Labs

Same here
I have the same problem, and also try many way.
Finally I have to flash another rom to solve it.
Have you solved on this Viper rom?

ok, I found a stupid solution.
Because adb is ok on another rom, so I copy this file.
/data/adb/adb_key
Restore it after flash Viper, and I finale can use adb debugging on Viper ROM.

adb device offline
:good::good::good:
aseeme555076 said:
ok, I found a stupid solution.
Because adb is ok on another rom, so I copy this file.
/data/adb/adb_key
Restore it after flash Viper, and I finale can use adb debugging on Viper ROM.
Click to expand...
Click to collapse
Copy adb_keys from another device to /data/misc/adb/adb_keys and setting permissions to 0640 for system:shell works for me, too.

bsdroid said:
setting permissions to 0640
Click to expand...
Click to collapse
THANKYOU!

Thaoldwise said:
As title says, I cannot use adb: "adb devices" returns "UNAUTHORIZED" if I launch command with phone plugged in and in android environment.
If I try in bootloader mode, download mode or recovery mode it returns "list of attached device" like it is empty list and cant see phone.
Phone is M9 ViperOneM9 4.3.0 firmware 3.35.401.12 recovery TWRP 3.0.0.0.
I am using a Win 10 PC where ADB command is perfectly working with my other M9 (ViperOneM9 4.2.1 same firmware as above, TRWP 2.8.7.1).
I read various posts and the problem seems to be the phone not showing the prompt to accept RSA key.
Yes, I am with USB debug ON and install from unknow sources ON (this last is useless but I say the same).
I think to have tried most of everything people suggest in different posts:
- updated and reinstalled android sdk
- deleted adbkey and adbkey.pub in my %user%/.android folder (then it recreates files but still no prompt on phone)
- tried different versions of HTC drivers on PC
- tried different versions of adb (1.0.31, 1.0.32 and also a pre 1.0.30 I dont remember exactly which one)
- tried installing Minimal ADB and Fastboot [4-27-16] http://forum.xda-developers.com/show....php?t=2317790
- wiped everything from TWRP recovery under "advanced" button and reinstalled rom with wipe during aroma installer
- looking in the phone in "system/data/misc/adb" for adb keys files but my folder is empty (checked on my other fully working M9 and that folder is empty too)
- toggled USB debugging on/off rebooting phone and PC
I also tried setting up a virtual machine with Windows 7 but I am not able to install drivers for the phone (yellow triangle in device manager).
Set up a virtual machine with Debian 8.4.0, installed android-tools-sdk, updated last version and "adb devices" here return OFFLINE
What can i do? It is like 7 hour I am trying but nothing is working.
Any help is greatly appreciated.
Thanks everyone
Click to expand...
Click to collapse
Install this driver manually from the device manager, the phone must be connected to the computer https://yadi.sk/d/TVkbNcXv3KP7mQ

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: