Develop Bugs

[HOWTO]- Performing a Nandroid Restore Manually using ADB

[HOW TO] Perform a Nandroid Restore via the Android Debug Bridge (ADB)
(This guide assums that you have already installed and set up adb tools on you PC)
1. Start phone in recovery mode, by turning it on while holding "Home" and "Power" buttons.
2. Plug the phone into the PC with a USB cable
3. Start Windows Command Prompt on your PC, by pressing Start on your PC and typing CMD into the run or search bar depending on your operating system. Then selecting Command Prompt.
4. Within the command prompt window, change the directory to the one your adb tools are by typing the following:
cd c:\sdk\tools
Click to expand...
Click to collapse
The path you put in may be different to this example, as it depends where on your PC your adb tools are kept.
5. Then type:
adb shell
Click to expand...
Click to collapse
6. Now type:
mount /sdcard
Click to expand...
Click to collapse
7. Now you need to change directory again to the one holding your nandroid back-up data, so first type
cd /sdcard
Click to expand...
Click to collapse
8. Then type:
cd nandroid
Click to expand...
Click to collapse
9. Now you need to find the specific name for the folder that holds your Nandroid Backup images, so type:
ls
Click to expand...
Click to collapse
and view the list that appears.
10. Now to enter the folder you want to back up to type
cd HT**********
Click to expand...
Click to collapse
obviously replacing the *s with your numbers and letters. FYI the number string is your Device Serial number.
11. Again type
ls
Click to expand...
Click to collapse
and view the list that appears.
12. Now to enter the folder you want to back up to type
cd BCD***-********-****
Click to expand...
Click to collapse
obviously replacing the *s with your numbers and letters. FYI the format of these digits is BCDXYZ-YYYYMMDD-HHMM from when the back up was created.
13. Now type:
nandroid-mobile.sh restore
Click to expand...
Click to collapse
14. Just press enter to select default.
15. Double check that the Default backup that is found is the one you want then press enter again.
Your selected backup will now be restored. When your CMD window looks like the one below you can reboot your phone and it will be as you remember it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
A big thanks goes to Pulser, without whom I would still be stuck, and this guide wouldn't have been written.

Nice. But are steps 6-12 really necessary? When in shell it should enough enter nandroid-mobile.sh -r, press enter to get you the list of available backups, pressing enter once again restores the last backup, or if you want an older just type the full name of that backup.

Install apk
Hello Fellow Androids!
If this is off topic, please accept my apologies. I am searching through all of XDA for a simple solution to adding apk. Now before you start bashing, please keep in mind that I am well aware of the "search" options + google + XDA etc.
Long story short, I have:
1) Rooted
2) Fashed many Roms (currently on Stock 2.1)
3) Lag Fixxed (see signature)
4) Removed Bloatware
5) I am familiar with ABD and commands
Problem:
All I'm trying to do is install certain "apk"s using ADB. I am well aware of the Program that installs/ pushes apps automatically that are found in G1 + Vibrant + HTC + Droid Forums without having to do any typin......BUT.....I would like to know my way around ABD <----Main reason why i dont want the easy way out.
I have been here:
http://forum.xda-developers.com/showthread.php?t=716806
as well as here:
http://forum.xda-developers.com/showthread.php?t=743457
even been here:
http://forum.xda-developers.com/showthread.php?t=740545
I know what you are thinking, why not use them? As i said before, i would like to be efficient with ADB. So...
I have tried methods found here:
http://forum.xda-developers.com/showthread.php?t=517874
As well as:
http://forum.xda-developers.com/showthread.php?t=532719
The problem I am having is:
Whether i navigate to my folder (desktop with all my apps) and use either
"adb push app /system/sd/app
adb push app-private /system/sd/app-private"
or simply
"adb install <path to file> - Example: adb install c:/apps/apps2sd.apk"
I always get the error: "cant find <whatever apk> to install"
No matter which directory i have it, i get that message.
Note:
1) I have debugging on
2) I mounted sd <----also tried Without mounting
3) I have used the same command when I removed bloatware but i understand Adding apks are slightly different.
4) I have all the drivers installed + Microsoft's .net framework + etc
What am i doing wrong?
All Critics, input, education bashing (just not hating) lol are welcome. Thanks!

put adb in your path... cd to the apk directory and run adb push *.apk /system....

TylerDurdenK said:
[HOW TO] Perform a Nandroid Restore via the Android Debug Bridge (ADB)
(This guide assums that you have already installed and set up adb tools on you PC)
and view the list that appears.
12. Now to enter the folder you want to back up to type
obviously replacing the *s with your numbers and letters. FYI the format of these digits is BCDXYZ-YYYYMMDD-HHMM from when the back up was created.
13. Now type:
MD window looks like the one below you can reboot your phone and it will be as you remember it.
http://farm3.static.flicn.[/QUOTE]
I get the error "nandroid-mobile.sh not found" after step 13. please help.
Click to expand...
Click to collapse

Dont use this, use jordfaz's clockworkmod, if you really need to use this adb script then you need to get nandroid-mobile.sh script somewhere

Is there any way to root MIcromax A52 ????

I bought a new Micromax A 52 mobile. I tried every method to root my phone. but i couldn't root it. Pls any tech-wizards help me.

I got same problem and tell me where to get custom roms for micromaxa52
Sent from my A52 using Tapatalk 2

Root micromax a 52
DOWNLOAD all the attachments that i have here. first of all connect your device to pc and install its drivers (it ll ask you to install by default)
1. put the adb_usb.ini file in .android folder in c:>users>(your name)>.android
2. install unlock root.exe.
3. run unlockroot.exe and click on root.
thats all.

attachments
here are the attachments----------
http://www.mediafire.com/?jrzuezl8s5t8k0s

UnlockRoot doesn't work with Micromax A52
This tool doesn't work with the A52. I've tried multiple ways to get the boot.img so that our mods here can assist with this but have not been successful in getting that file.
In case anyone gets this working please do post here as its really frustrating when you have apps on the phone but are unable to update them.

any one tried the method ... does it work

Rooting A52
I tried this method, doesnt work, plz will someone come up with a Rooting process that actually Roots this Damn phone

go to a ubuntu PC open terminal type "lsusb".
now connect your device via usb cable and type "lsusb" again.( without quotes)
Give me the output in both the cases.
I may have something for you guys very soon.
---------- Post added at 12:40 AM ---------- Previous post was at 12:30 AM ----------
if you dont have ubuntu pc try this on a 32 bit windows pc
http://downloads.yahoo.com/software/windows-web-tools-lsusb-s577074
download it and then run it. I think it will do the job. And then post the outputs here.
But i would recommend to use ubuntu pc. and lsusb command from ubuntu terminal.
Try it asap and share your outputs here.

Anyone with the outputs for ubuntu??
if you are on a windows Pc you may download cygwin (google it and install it)
then you can get the lsusb command working (I am not sure of this)....Somebody please try the device with ubuntu pc or anyother linux based operating system.
Regards,
imetal1

i am on window 7 waiting for some one to try on ubuntu
i hope someone can root this dam device
---------- Post added at 05:44 PM ---------- Previous post was at 05:36 PM ----------
please see if these links help in any way
http://androidforums.com/a52-all-things-root/578997-how-safely-root-micromax-a52.html#post4867029
http://androidforums.com/a52-all-things-root/578997-how-safely-root-micromax-a52.html#post4874745
http://androidforums.com/a52-all-things-root/578997-how-safely-root-micromax-a52.html#post4874749

@kartikoli
try to download cygwin from google and run "lsusb" before and after plugging in your device to the computer.
or try to install the "lsusb" from the link that i posted earlier.
and post the outputs....Do it asap.

bro i am too limited with command line knowledge and dont think i would be abl to accomplish the task properly

Done with ubuntu 11.04
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Now what to do? The result is given by ubuntu...

Root micromax a52 mobile phone
steps to unroot your device :--
1. first of all install Android SDK from http://developer.android.com/sdk/index.html (make sure you have JDK installed)
->Follow all the steps there carefully and you will have a working SDK.
2. Remove all the android USB drivers installed on your device by the software in the attachment. -> http://www.2shared.com/file/mZdgGZG3/usbdeview.html
3. Now connect your device to PC and install Micromax's official drivers (you will get an auto-run prompt for the driver installation on connecting your device.
4. Now download the attachment here and put it into the C:/Users/(your_name)/.android.
-->.android folder you should get automatically NO NEED TO MAKE A NEW FOLDER...if the ".android" folder is not present...please download and install android SDK properly.
now put the file extracted from that zip into the folder ".android".
Restart your PC.
5. goto C:/Users/(your_name)/android-sdk/platform-tools. And open command prompt there.
6. And make sure that the mobile is attached to your PC via usb cable.
7. Type "adb devices" (without quotes).
8. your micromax device should be shown there. Now close the terminal.
9. Download and install this :--http://www.mediafire.com/?jrzuezl8s5t8k0s
10. click on Root option.
11. you are done!!!!!
NOTE: DOWNLOAD THIS adb_usb file only and not from any previous attachments.
LASTLY, Sorry for being late my internet connection was down
I have tried to make this guide as simple as possible. But still, should you need more information or there is any confusion do share. I would love to help you out.
Regards,
imetal1

Dude......i done kno whethr its working or not.......bt if it does......u r the 1st to crack it.....
tell me wat about the CWM for the phone.......need to backup the stock ROM....

Didn't Work.
Tried that too. It said failed to get shell root... Mate if you could tell me how i could give you my boot.img if that helps i will... else if there's a way to replace it with a unsecured boot.img do tell me.. In all other accounts There's been no bloody way to root this device..
To the contrary micromax ships half of its funbook rooted! And this bloody phone cannot be! God help me!

Did you followed the entire tutorial? If yes, then verify-->>
0. Enable USB debugging option on your device....(you will find it in settings/applications/development)
1. open command prompt in c:/users/ur_name/android-sdk/platform-tools/
2. type abd devices
do you see your device listed there????
tell me yes or no.
If no then make sure you have the SDK installed. do share your outputs.
NOTE : IF YOU HAD DISABLED YOUR USB DEBUGGING MODE EARLIER PLEASE TRY ONCE MORE BY ENABLING THE USB DEBUGGING MODE.
--------------------------------------------------------------------------------------------------------------------------------------------------
And about supplying the boot.img actually I am aware of commands that will help to get the boot,system,and recover.imgs out of the devices but for running those command we have to root the device first.....I am unaware of any such commands that extracts out these imgs from unrooted devices.
---------- Post added at 12:06 PM ---------- Previous post was at 11:45 AM ----------
if that also dosent works then try super-one click. (get it from google ) try diffrent versions of it and using different modes like ginger-break etc....its easy to use software.
I dont possess a52 so cant try myself but i ll do my best.
Regards,
imetal1

Nope. No Such luck.
Mate, Anyway i can have a quick chat with you? Um. Yeah debugging is on. And my device is listed. I may be a noob ova here but i'm dumb proof.
Anyway i tried this, superone click, gingerbreak and another batch file that restarts my phone 3 times...
uses a command
Code:
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
adb reboot
adb shell rm /data/local.prop > nul
adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
adb reboot
It fails at
Code:
adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
command. Zerg rush fails. Gingerbreak just hangs... So since all of the readily available market programs fail i was thinking of another approach where i saw this guy who flashed ICS to his Zopo ZP100 (MediaTek MT6575). The similarity over here is the board. My board is also a MT6575. So i was wondering if flashin it with this would work... (jus askin) Or if there was a chance to port an existing pre-rooted 2.3.6 rom to this board by replacin d drivers or such.. I have no idea but i'm ready to experiment around. Forgive me if i sound dumb... Do reply. And if your in for a quick chat today temme. I'll give you my skype ID somehow..
Ash1794
imetal1 said:
Did you followed the entire tutorial? If yes, then verify-->>
0. Enable USB debugging option on your device....(you will find it in settings/applications/development)
1. open command prompt in c:/users/ur_name/android-sdk/platform-tools/
2. type abd devices
do you see your device listed there????
tell me yes or no.
If no then make sure you have the SDK installed. do share your outputs.
NOTE : IF YOU HAD DISABLED YOUR USB DEBUGGING MODE EARLIER PLEASE TRY ONCE MORE BY ENABLING THE USB DEBUGGING MODE.
--------------------------------------------------------------------------------------------------------------------------------------------------
And about supplying the boot.img actually I am aware of commands that will help to get the boot,system,and recover.imgs out of the devices but for running those command we have to root the device first.....I am unaware of any such commands that extracts out these imgs from unrooted devices.
---------- Post added at 12:06 PM ---------- Previous post was at 11:45 AM ----------
if that also dosent works then try super-one click. (get it from google ) try diffrent versions of it and using different modes like ginger-break etc....its easy to use software.
I dont possess a52 so cant try myself but i ll do my best.
Regards,
imetal1
Click to expand...
Click to collapse

​Open a command line terminal in your platform-tools.
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
adb reboot
adb shell “echo \”ro.kernel.qemu=1\” > /data/local.prop”
adb reboot
adb shell id
//IF ID IS 0/root THEN CONTINUE, ELSE START OVER>
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
//UNDO EVERYTHING EXCEPT su
adb shell rm /data/local.prop
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.bak /data/local/tmp
adb reboot
If your device seems to bootloop, don’t worry, just keep inputting the commands.
If you get a permissions error on the call
adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
then you may try
adb shell rm /data/local.prop
And then try the echo command again. This may be due to having rooted prior without cleaning up properly.
-----------------------------------------------------------------------------
If all the above fails download the attachments here and extract it to your platform-tools folder. And run .bat file that is created. May be this would help.
Actually, I dont have the device so please share any errors that you are getting...better still post entire output.
Regards,
imetal1

Changing splash screen image via sdk

Hello.
For the past 3 hours i have struggled installing the sdk tools, so i could install custom splash images. I most of the time i was searching for a good tutorial but most of them failed me. Usualy i got a file(some kind of image), and i placed it into the rot of the sd card and just rebooted into hboot. the system detected the splash img file and prompted me to install it and that was that, but most of the threads contain a few codes that realy dont work for me. I installed sdk and it works fine but i realy dont understand from the codes forward how to put the .png image to .img and then flashing it trough the cmd prompt :s.

pitastrudl said:
Hello.
For the past 3 hours i have struggled installing the sdk tools, so i could install custom splash images. I most of the time i was searching for a good tutorial but most of them failed me. Usualy i got a file(some kind of image), and i placed it into the rot of the sd card and just rebooted into hboot. the system detected the splash img file and prompted me to install it and that was that, but most of the threads contain a few codes that realy dont work for me. I installed sdk and it works fine but i realy dont understand from the codes forward how to put the .png image to .img and then flashing it trough the cmd prompt :s.
Click to expand...
Click to collapse
Ok, a very rapid tutorial on splash screens:
You need an image that can fit you phone (480*800 pixels) and convert it to .img format
The best tutorial on how to flash a splash is this one: http://forum.xda-developers.com/showthread.php?t=1059520
If you want to flash the .img directly you will need ENG S-OFF (DO NOT FLASH ENG S-OFF if you phone was shipped with GB. Just flash the Hack Kit modified ENG S-OFF that supports all builds)
When you have the .img file ready, just put it in a folder in the PC where u can easily locate it.
Open a cmd as admin or terminal as root.
Enable usb debugging and charge only as default and plug the phone.
In cmd navigate to where the .img file is located (for instance: c:\users\your_user\Desktop)
Type: adb devices (it should show you serial number under devices attached)
If the above was allright type: adb reboot-bootloader (it will boot in fastboot usb)
Type: fastboot flash splash1 name_of_file.img
Once you get the OKAY. Finished near the bottom of the cmd session. Type: Fastboot reboot...
Enjoy your new splash...:laugh:

Thanks for all the help!
But there is another problem, you see when i try to make the .img file with the command in command prompt "adb nbimg -F splash1.bmp -w 480 -h 800", it rolls down some text,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and also when i went looking for the adb i doscovered this, and the instructions say
Step 3. Copy this Bitmap to your TOOLS folder of your SDK package
Step 4. From ADB, within the TOOLS directory, type the following
adb nbimg -F splash1.bmp -w 480 -h 800
Click to expand...
Click to collapse
The problem is that there is no adb in the tools folder but it went to platform-tools. Im realy out of luck

pitastrudl said:
Thanks for all the help!
But there is another problem, you see when i try to make the .img file with the command in command prompt "adb nbimg -F splash1.bmp -w 480 -h 800", it rolls down some text,
and also when i went looking for the adb i doscovered this, and the instructions say
The problem is that there is no adb in the tools folder but it went to platform-tools. Im realy out of luck
Click to expand...
Click to collapse
You are not out of luck...from adb means that you have to be located in the sdk-tools folder (c:\users\android\sdk\sdk-tools) in the cmd session and from there run the commands...adb stands for Android Debug Bridge which is the connection between PC and phone and was installed when u installed the sdk package.

Cool!

glevitan said:
Ok, a very rapid tutorial on splash screens:
You need an image that can fit you phone (480*800 pixels) and convert it to .img format
The best tutorial on how to flash a splash is this one: http://forum.xda-developers.com/showthread.php?t=1059520
If you want to flash the .img directly you will need ENG S-OFF (DO NOT FLASH ENG S-OFF if you phone was shipped with GB. Just flash the Hack Kit modified ENG S-OFF that supports all builds)
When you have the .img file ready, just put it in a folder in the PC where u can easily locate it.
Open a cmd as admin or terminal as root.
Enable usb debugging and charge only as default and plug the phone.
In cmd navigate to where the .img file is located (for instance: c:\users\your_user\Desktop)
Type: adb devices (it should show you serial number under devices attached)
If the above was allright type: adb reboot-bootloader (it will boot in fastboot usb)
Type: fastboot flash splash1 name_of_file.img
Once you get the OKAY. Finished near the bottom of the cmd session. Type: Fastboot reboot...
Enjoy your new splash...:laugh:
Click to expand...
Click to collapse
Thanks, I will be trying this tonight when I get home.

now it says could not open splash1.bmp. its in the right format, i tryed resaving it and everything.

pitastrudl said:
now it says could not open splash1.bmp. its in the right format, i tryed resaving it and everything.
Click to expand...
Click to collapse
If it is the nb file you won't be able to open it...

I cant get the nb file, the command cant open it,
here is the image, if you could try. I tryed with other images but it still cant open it

pitastrudl said:
I cant get the nb file, the command cant open it,
here is the image, if you could try. I tryed with other images but it still cant open it
Click to expand...
Click to collapse
That is not the image you have to flash to your phone (and rename to .img)...that is the one with the .nb extension...

Hey, every time i try to open it i cant and it clearly says,
Step 4. From ADB, within the TOOLS directory, type the following
Code:
nbimg -F splash1.bmp -w 480 -h 800
Step 5. Take your newly made nb image, and rename the extension to ".img"
Click to expand...
Click to collapse
I have done that, but the problem is that i wont open the damn splash1.bmp , so it would convert to the nb image.
And your last anwser is realy confusing me
That is not the image you have to flash to your phone (and rename to .img)...that is the one with the .nb extension...
Click to expand...
Click to collapse
If it is the image with the .nb extension then i have to rename it to .img?! it states in the instructions.
Step 5. Take your newly made nb image, and rename the extension to ".img"
Click to expand...
Click to collapse

[Tool]i9505 Quick Flasher

Now next to the i9500 Quick Flasher there also is the i9505 Quick Flasher, just slight changes to make partitions match
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download:
www.broodplank.net/I9505-Quick-Flasher-1.0.zip
Created for a fail-safe flash operation of boot.img and recovery.img, all other partitions (currently only system) are experimental.

broodplank1337 said:
Now next to the i9500 Quick Flasher there also is the i9505 Quick Flasher, just slight changes to make partitions match
Download:
www.broodplank.net/I9505-Quick-Flasher-1.0.zip
Created for a fail-safe flash operation of boot.img and recovery.img, all other partitions (currently only system) are experimental.
Click to expand...
Click to collapse
Tried this, it cannot connect to my S4. Yes, I have debugging enabled, and yes my device is in mtp mode.
I get:
Running checks, please wait...
<<< I9505 USB Connection >>>
[ ] I9505 USB Connection
Your I9505 is not connected or unreachable! Please read the instructions for reference.

Snakefood said:
Tried this, it cannot connect to my S4. Yes, I have debugging enabled, and yes my device is in mtp mode.
I get:
Running checks, please wait...
<<< I9505 USB Connection >>>
[ ] I9505 USB Connection
Your I9505 is not connected or unreachable! Please read the instructions for reference.
Click to expand...
Click to collapse
I had some issues with usb as well when I was testing the tool out, but It was fixed after a while, its actually not the tool but the way of mounting usb on the i9505. I fixed it by replacing the adb.exe file with the latest one (which is also included in the zip tho). Can you please test for me if your able to get a normal adb shell? (open cmd window in the quickflasher dir and type "adb shell"), if it says device not found there is an issue with debugging mode. if not then you should test this and pls give me the info:
adb get-state (should return "device")
adb devices (should return a connected device)
If you get negative results here you should kill adb.exe (taskkill /f /im adb.exe for group kill) and try again.
If it does work pls enter:
adb root
adb remount
adb shell
and tel me what you see.
The usb mode is a struggle on the i9505.. I thought hey lets upgrade to CM so I will have mass storage mode.. but no way, only MTP and PTP... (I added the Mass storage option and forced it to be available on my private build, but it still doesn't work..)
Currently trying to find out how to permanently enable oldskool mass storage + adb.

broodplank1337 said:
I had some issues with usb as well when I was testing the tool out, but It was fixed after a while, its actually not the tool but the way of mounting usb on the i9505. I fixed it by replacing the adb.exe file with the latest one (which is also included in the zip tho). Can you please test for me if your able to get a normal adb shell? (open cmd window in the quickflasher dir and type "adb shell"), if it says device not found there is an issue with debugging mode. if not then you should test this and pls give me the info:
adb get-state (should return "device")
adb devices (should return a connected device)
If you get negative results here you should kill adb.exe (taskkill /f /im adb.exe for group kill) and try again.
If it does work pls enter:
adb root
adb remount
adb shell
and tel me what you see.
The usb mode is a struggle on the i9505.. I thought hey lets upgrade to CM so I will have mass storage mode.. but no way, only MTP and PTP... (I added the Mass storage option and forced it to be available on my private build, but it still doesn't work..)
Currently trying to find out how to permanently enable oldskool mass storage + adb.
Click to expand...
Click to collapse
My results:
C:\Windows\system32>cd \
C:\>cd s4 root
C:\S4 root>cd qflash
C:\S4 root\qflash>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: more than one device and emulator
C:\S4 root\qflash>adb get-state
unknown
C:\S4 root\qflash>adb devices
List of devices attached
12138fc0 device
emulator-5554 offline
C:\S4 root\qflash>adb root
error: more than one device and emulator
C:\S4 root\qflash>

Snakefood said:
My results:
C:\Windows\system32>cd \
C:\>cd s4 root
C:\S4 root>cd qflash
C:\S4 root\qflash>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: more than one device and emulator
C:\S4 root\qflash>adb get-state
unknown
C:\S4 root\qflash>adb devices
List of devices attached
12138fc0 device
emulator-5554 offline
C:\S4 root\qflash>adb root
error: more than one device and emulator
C:\S4 root\qflash>
Click to expand...
Click to collapse
ah so you have the emulator in there as well.. thats the problem. to bypass the emulator use:
adb -d
for example adb -d shell or adb -d get-state
do you have an AVD emulator running currently?

broodplank1337 said:
ah so you have the emulator in there as well.. thats the problem. to bypass the emulator use:
adb -d
for example adb -d shell or adb -d get-state
do you have an AVD emulator running currently?
Click to expand...
Click to collapse
What emulator do I have, I've only used the files in your download, as far as I know. Any way to check / remove?
Edit: I had bluestacks installed a while back, but uninstalled it, could this have left some crap behind after it?

Snakefood said:
What emulator do I have, I've only used the files in your download, as far as I know. Any way to check / remove?
Click to expand...
Click to collapse
Hmm the emulator that comes with android sdk, is afaik the only one who can correspond with adb, but it would be odd if you ran it all the time.
check taskmgr, and look for emulator.exe/java.exe, to be sure also kill adb.
You can check if there is an existing emulator if you start AVD manager (if you don't have android sdk at all then its really strange )

broodplank1337 said:
Hmm the emulator that comes with android sdk, is afaik the only one who can correspond with adb, but it would be odd if you ran it all the time.
check taskmgr, and look for emulator.exe/java.exe, to be sure also kill adb.
You can check if there is an existing emulator if you start AVD manager (if you don't have android sdk at all then its really strange )
Click to expand...
Click to collapse
I didn't have sdk installed; I installed it and ran avd manager, doesn't show any installed.
when I run adb -d shell I get [email protected]:/ $

Snakefood said:
I didn't have sdk installed; I installed it and ran avd manager, doesn't show any installed.
when I run adb -d shell I get [email protected]:/ $
Click to expand...
Click to collapse
Ok the output is good. ill add a function to the tool to force adb usb connection
for the meanwhile you can use:
(put boot.img in adb dir)
adb -d push boot.img /sdcard/boot.img
adb -d shell su -c 'dd if=/sdcard/boot.img of=/dev/block/mmcblk0p20'
adb -d shell reboot

broodplank1337 said:
Ok the output is good. ill add a function to the tool to force adb usb connection
for the meanwhile you can use:
(put boot.img in adb dir)
adb -d push boot.img /sdcard/boot.img
adb -d shell su -c 'dd if=/sdcard/boot.img of=/dev/block/mmcblk0p20'
adb -d shell reboot
Click to expand...
Click to collapse
Do I rename my recovery.img from cwm to boot.img for the above, or is this for a different process?

Snakefood said:
Do I rename my recovery.img from cwm to boot.img for the above, or is this for a different process?
Click to expand...
Click to collapse
boot.img = mmcblk0p20
recovery.img = mmcblk0p21
the name of the .img doesn't matter but the partition is important.

Ahh, looking at your image, this now makes sense, I can see the destination partition names as you describe..
Well have a go at this later, unless you plan to release an update later today?
Sent from my Nexus 7 using xda app-developers app
Edit: couldn't get this working, so I just flashed using odin. Thanks for trying to get resolved tho.

Odin is the tool for me, no need more than that.

broodplank1337 said:
ah so you have the emulator in there as well.. thats the problem. to bypass the emulator use:
adb -d
for example adb -d shell or adb -d get-state
do you have an AVD emulator running currently?
Click to expand...
Click to collapse
Hi brood,
just stumbled upon this thread and read about Snakefood's problem.
Although he worked around the error by using Odin I want to give you a hint regarding this specific problem:
he obviously has an adb device installed called emulator-5554 but which is offline. He already gave himself the correct answer:
"I had bluestacks installed a while back, but uninstalled it, could this have left some crap behind after it?"
My diagnose is: yes, BlueStacks definitely leaves a lot of crap behind and does NOT uninstall cleanly. I tested it once and I saw myself compelled to restore an older windows image which I made BEFORE I installed BlueStacks on my windows machine.
BTW: BlueStacks is an Android emulator for Windows but a piece of *%$~#!!! crap, but that's just my humble opinion.
And BlueStacks uses such an adb emulator device entry although I'm not sure if it was called like that. But BlueStacks is not the only Android emulator and most probably other programs of this kind create such an adb entry as well.

skywalker01 said:
Hi brood,
just stumbled upon this thread and read about Snakefood's problem.
Although he worked around the error by using Odin I want to give you a hint regarding this specific problem:
he obviously has an adb device installed called emulator-5554 but which is offline. He already gave himself the correct answer:
"I had bluestacks installed a while back, but uninstalled it, could this have left some crap behind after it?"
My diagnose is: yes, BlueStacks definitely leaves a lot of crap behind and does NOT uninstall cleanly. I tested it once and I saw myself compelled to restore an older windows image which I made BEFORE I installed BlueStacks on my windows machine.
BTW: BlueStacks is an Android emulator for Windows but a piece of *%$~#!!! crap, but that's just my humble opinion.
And BlueStacks uses such an adb emulator device entry although I'm not sure if it was called like that. But BlueStacks is not the only Android emulator and most probably other programs of this kind create such an adb entry as well.
Click to expand...
Click to collapse
Hi Skywalker.
Long time no see . Anyways, OT. I have installed BlueStacks once (in the alpha or beta phase I believe) and I don't remember much of it but I do remember that it was crap idd. Also that it leaves "traces" (if you call adb a trace xd, more like a fail uninstall ) is very lame.. and causing problems for people who are not 100% familiar with adb and its daemon.
The AVD Emulator from the SDK may lag a bit but atleast it doesn't interfere with adb :silly:

Great tool broodplank1337, well done mate this will save ppl from making stupid mistakes

dublinz said:
Great tool broodplank1337, well done mate this will save ppl from making stupid mistakes
Click to expand...
Click to collapse
Thanks ^^, I think that is true hehe, using 'dd' to flash images isn't for the absolute beginner idd ;p

Hi guys,
If you need me to assist more with ahh testing just let me know. Is there an uninstaller to remove what bluestacks left behind, or is the Windows disc the only definite uninstaller
Sent from my GT-I9505 using xda app-developers app

Snakefood said:
Hi guys,
If you need me to assist more with ahh testing just let me know. Is there an uninstaller to remove what bluestacks left behind, or is the Windows disc the only definite uninstaller
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
You should first look in msconfig (start > run > msconfig) at the startup tab and look if there is any startup item from bluestacks.
If there is nothing there look in services.msc (start > run > services.msc) and check for any blue stacks service, and if there is any, disable it.
Next to that you can also use HijackThis (http://sourceforge.net/projects/hjt/) to find startup items. hope it helps

Hey Brood,
See you're doing great work here on the S4 section.:good:
I'm missing your input in the S+ section unfortunatly:crying:

Can't flash TWRP, "press any key to shutdown" in fastboot

Hello,
phone is a Xiaomi Mi 9 se, i had problem unlocking the bootloader using my main PC (AMD based) it kept getting stuck at 50%. Then i used a intel laptop and i unlocked the booloader.
Now i'm trying to flash a TWRP on recovery, but i cannot do anything on fastboot every command i give it the phone responds with "press a key to shutdown" and i get
FAILED (command write failed (Invalid argument)
On command line, both on the AMD and intel pc, i tried switching cables and PCs, both usb 2.0 and 3.0...
Update: So windows was installing kedacom driver for the smartphone, i managed to remove the wrong drivers (kedacom) now i see this driver by xiaomi and from what i see online is correct, but i still get the same error i don't know what to do anymore.

Burt_93 said:
Hello,
phone is a Xiaomi Mi 9 se, i had problem unlocking the bootloader using my main PC (AMD based) it kept getting stuck at 50%. Then i used a intel laptop and i unlocked the booloader.
Now i'm trying to flash a TWRP on recovery, but i cannot do anything on fastboot every command i give it the phone responds with "press a key to shutdown" and i get
FAILED (command write failed (Invalid argument)
On command line, both on the AMD and intel pc, i tried switching cables and PCs, both usb 2.0 and 3.0...
Click to expand...
Click to collapse
I think you need a special adb package for amd, but I don't remember the link try to search fastboot ryzen

redispade said:
I think you need a special adb package for amd, but I don't remember the link try to search fastboot ryzen
Click to expand...
Click to collapse
But it doesn't even work on a intel laptop... i still think it's a driver issue, Mi suite doesn't recognize the phone either. Is there another way to flash yours TWRP?

I had the dame peoblem, rebooted the PC a few times, then it works.

So windows was installing kedacom driver for the smartphone, i managed to remove the wrong drivers (kedacom) now i see this driver by xiaomi and from what i see online is correct, but i still get the same error i don't know what to do anymore.

I assume that you try to flash stock again, right? With Mi Flash Tool...

Fastboot commands (including unlocking the phone with offical tools) can fail on Intel devices.
Try this code: (Save this as .bat and run as administrator)
Code:
@echo off
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "osvc" /t REG_BINARY /d "0000" /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "SkipContainerIdQuery" /t REG_BINARY /d "01000000" /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "SkipBOSDescriptorQuery" /t REG_BINARY /d "01000000" /f
pause
Use the USB 2.0 port, and try again.
This thing comes from China MIUI forum.
This worked with my i7-8750H laptop, solving the "Press anykey to shutdown" problem (when unlocking however)
Also if it doesn't work for you and you wish a rollback, just delete the keys (in regedit) the batch has made and you're fully rolled back.

Catalysa said:
Fastboot commands (including unlocking the phone with offical tools) can fail on Intel devices.
Try this code: (Save this as .bat and run as administrator)
Code:
@echo off
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "osvc" /t REG_BINARY /d "0000" /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "SkipContainerIdQuery" /t REG_BINARY /d "01000000" /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "SkipBOSDescriptorQuery" /t REG_BINARY /d "01000000" /f
pause
Use the USB 2.0 port, and try again.
This thing comes from China MIUI forum.
This worked with my i7-8750H laptop, solving the "Press anykey to shutdown" problem (when unlocking however)
Also if it doesn't work for you and you wish a rollback, just delete the keys (in regedit) the batch has made and you're fully rolled back.
Click to expand...
Click to collapse
No luck with that, now it remains stuck at "sending recovery"

I finally did it using a third, older laptop

Catalysa said:
Fastboot commands (including unlocking the phone with offical tools) can fail on Intel devices.
Try this code: (Save this as .bat and run as administrator)
Code:
[user=8011874]@Echo off[/user]
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "osvc" /t REG_BINARY /d "0000" /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "SkipContainerIdQuery" /t REG_BINARY /d "01000000" /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "SkipBOSDescriptorQuery" /t REG_BINARY /d "01000000" /f
pause
Use the USB 2.0 port, and try again.
This thing comes from China MIUI forum.
This worked with my i7-8750H laptop, solving the "Press anykey to shutdown" problem (when unlocking however)
Also if it doesn't work for you and you wish a rollback, just delete the keys (in regedit) the batch has made and you're fully rolled back.
Click to expand...
Click to collapse
you are GENIUS, after almost one day searching your method worked for me
Thank you sooooo much

This worked for me and I hope the same goes for you all as well (
without using USB HUB and USB 2 port
).
I found the solution here .
Scenario:
1) Phone not detected with fastboot devices command
2) Phone goes into "Press any key to shutdown"
3) Just download this .bat file and run it as administrator
4) Remove your phone, get it back into fastboot mode (Power + Volume Down), connect it again
5) Open CMD and try to run any fastboot command & they'll run successfully.
P.S.: I too got my POCO F1 unlocked by using this with the modded MI Unlock app. Was tired of trying usb hub and extension thing though my PC is intel and not amd. It'll be happy to know how and what made it worked from technical aspect. Thank You.

Burt_93 said:
Hello,
phone is a Xiaomi Mi 9 se, i had problem unlocking the bootloader using my main PC (AMD based) it kept getting stuck at 50%. Then i used a intel laptop and i unlocked the booloader.
Now i'm trying to flash a TWRP on recovery, but i cannot do anything on fastboot every command i give it the phone responds with "press a key to shutdown" and i get
FAILED (command write failed (Invalid argument)
On command line, both on the AMD and intel pc, i tried switching cables and PCs, both usb 2.0 and 3.0...
Update: So windows was installing kedacom driver for the smartphone, i managed to remove the wrong drivers (kedacom) now i see this driver by xiaomi and from what i see online is correct, but i still get the same error i don't know what to do anymore.
Click to expand...
Click to collapse
USE this, work 100% for me, I found on youtube but i dont remenber the channel
remane to .bat