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

DPI Changed and now no Boot!!!

Hey I changed my DPI settings to 180 and the Phone only shows the Google Screen with that lock Icon
and then turns black.
What can I do to revert this? can someone please help?

You did make backup before doing that RIGHT?

It had nothing too important that I needed on it. So no, I didn't

Well I would say just reflash your current ROM on top of your setup now. You should still be able to get into recovery just fine.

NYYFan325 said:
Well I would say just reflash your current ROM on top of your setup now. You should still be able to get into recovery just fine.
Click to expand...
Click to collapse
Unfortunately the .zip file isn't on the internal memory
I tried to mount the USB to transfer a .zip rom over
But it keeps saying
E:can't mount /sdcard/
is this normal? Did the internal memory get warped?
Could ODIN be used to help me out?
I shouldnt have gone along with this post I saw that suggested that 180 DPI would send the User Interface into "Tablet mode" because I really wanted the Notification/ Status Bar in the same bar as the on screen "Back, Home and Task" buttons
And that would have been the only mod that I have done. and look what happens.

throwback1718 said:
Unfortunately the .zip file isn't on the internal memory
I tried to mount the USB to transfer a .zip rom over
But it keeps saying
E:can't mount /sdcard/
is this normal? Did the internal memory get warped?
Could ODIN be used to help me out?
I shouldnt have gone along with this post I saw that suggested that 180 DPI would send the User Interface into "Tablet mode" because I really wanted the Notification/ Status Bar in the same bar as the on screen "Back, Home and Task" buttons
And that would have been the only mod that I have done. and look what happens.
Click to expand...
Click to collapse
If you go to the bootloader and redo the command fastboot oem lock and then fastboot oem unlock it will lock and unlock your boot loader also reformatting your scard. Once you do that go back to recovery and try putting the zip file on again

throwback1718 said:
Unfortunately the .zip file isn't on the internal memory
I tried to mount the USB to transfer a .zip rom over
But it keeps saying
E:can't mount /sdcard/
is this normal? Did the internal memory get warped?
Could ODIN be used to help me out?
I shouldnt have gone along with this post I saw that suggested that 180 DPI would send the User Interface into "Tablet mode" because I really wanted the Notification/ Status Bar in the same bar as the on screen "Back, Home and Task" buttons
And that would have been the only mod that I have done. and look what happens.
Click to expand...
Click to collapse
you cant mount the sd card because there is no sd card.
use adb
adb push locationofrom /data/meda

NYYFan325 said:
If you go to the bootloader and redo the command fastboot oem lock and then fastboot oem unlock it will lock and unlock your boot loader also reformatting your scard. Once you do that go back to recovery and try putting the zip file on again
Click to expand...
Click to collapse
My apologies... I literally just got this Nexus today. again, I was just trying to make a minor tweak...
Anyhow, I don't know too much about the phone. How is the command fastboot oem lock done?
I can't use the search button right now too much

It' s very simple to fix that, I asume that you did the "tweak" in /system/build.prop right? If so just boot into recovery, if you can't then use the GNex toolkit, once in recovery connect the phone to the computer and it should see your phone as an adb device, open from the toolkit a command prompt, start adb service and pull the modified build.prop to your computer then correct whatever you mess in it (DPI) and then push the fixed build.prop to the phone and finally your GNex will boot normally.
Sent from my Galaxy Nexus using xda premium

^^^ Actually I downloaded an app from the play store to do it... does this still apply to me ?
I'm mad at myself
Sent from my HERO200 using Tapatalk 2

throwback1718 said:
^^^ Actually I downloaded an app from the play store to do it... does this still apply to me ?
I'm mad at myself
Sent from my HERO200 using Tapatalk 2
Click to expand...
Click to collapse
Yes, because all that this app did is changed the value in your build.prop. What you want to do is go to this file and change ro.sf.lcd_density from 180 to 320, save and reboot.

ok I'm having difficulty here. I can't do any of the adb functions. Again like I said, I got this phone just yesterday. So drivers and such havent been installed. Apparently when using the toolkit to install the drivers to the computer, you need to enable USB debugging. Which I can't do. Because the phone isn't booting.
So is there a work around for this? Its the damn first step and I'm stuck already.
I literally haven't done anything to this phone. Clockworkmod was installed prior to me getting the phone, and so was Fastboot.
I have been looking online for Nexus USB drivers but its difficult .... Any suggestions?

Try this and see if you can install the drivers or if your pc detect the gnex: power off the phone, press and keep pressed volume down button while you turn on the phone, this should make you boot into fastboot or odin's mode I'm not pretty sure. Try it and let us know.
Sent from my Nook Tablet using xda premium

iferlive said:
Try this and see if you can install the drivers or if your pc detect the gnex: power off the phone, press and keep pressed volume down button while you turn on the phone, this should make you boot into fastboot or odin's mode I'm not pretty sure. Try it and let us know.
Sent from my Nook Tablet using xda premium
Click to expand...
Click to collapse
It goes into download mode. With "ODIN" in the top left corner.
So doing this should substitute the fact that I can't enable USB debugging because I can't boot the phone?

Ok now I'm home and I have my laptop here so I can help you more efficiently, mi computer also didn't recognized my gnex in odin mode, lets try something else, turn off your phone, and connect it to your pc and wait until you hear the windows sound of "new device attached" if so then proceed with the installation of drivers vie the toolbox, once done that and if we have look toolbox should see your device, let me know what happens, and tell me what app did you use and what density you did set so I can recreate the event in my phone
---------- Post added at 07:44 PM ---------- Previous post was at 07:01 PM ----------
Oh I got it dude, so you have already installer CWM Recovery right? ok Here is the solution so you can have adb, I assume that you have already installed the drivers wich is so simple and you don't need the phone to do that, turn off your phone and press volume up and volme down buttons keep them pressed while pressing the power button "KEEP ALL PRESSED" and you will boot into FASTBOOT Mode, if the installation of the driver was correctly made the ToolBox will detect your device in FastBoot (I recommend you to reboot your computer if it didn't recognize the phone), then use the volume keys to select "Recovery Mode" and press the power button, this will make your GNex boot into CWMR! wich means that you can use adb commands (CWMR has natively adb enabled) your pc should recognize the new device and prepare the drivers, after this just refres the ToolBox screen with option 25 and you will see your device number in the list of adb devices.
Ok once done that (that tricky part) in the ToolBox select option 14 adn select "no" to the secure image cuestion, this will reboot your phone, now put this do download the build.prop "/system/build.prop" with no quotes and hit "enter"
Now go to the ToolBox installation folder and go into the folder caller "pulled_files_are_put_here" ther will be your GNex build prop, open it with a text editor (WordPad) and edit this entry: ro.sf.lcd_density=320 you mess with this value so lets restore it to the default one which is 320, save the file.
Now move the recently corrected build.prop to the folder called "put_files_to_push_here" which is in ToolBox installation folder, and in the ToolBox windows select option 13, now put build.prop as the name of the file to push, it will say "file found" and nos put the directory where it goes which is: /system/
Reboot
And Voila! your GNex should now boot normally.
Good Look man, let me know if you could do it.

1) Reboot your device in CWM and plug into you computer.
2) Install these drivers. If you don't know how, have a read here.
3) Download the adb files from here and unzip them in to a directory.
4) Open a command prompt in that same directory.
5) In the menus on your device in CWM, mount /system.
6) In the command prompt, type: adb pull /system/build.prop
7) Open that file in a text editor and change the line that starts with ro.sf.lcd_density to have a value of 320. Close and save it.
8) In the command prompt, type: adb push build.prop /system/
9) In the command prompt, type: adb shell chmod 644 /system/build.prop
10) Reboot.

iferlive said:
Ok once done that (that tricky part) in the ToolBox select option 14 adn select "no" to the secure image cuestion, this will reboot your phone, now put this do download the build.prop "/system/build.prop" with no quotes and hit "enter"
And Voila! your GNex should now boot normally.
Good Look man, let me know if you could do it.
Click to expand...
Click to collapse
Stuck at this part. The phone tried to reboot and it didnt... Just black screen It kept saying "Waiting for adb Mode"
{
"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 it still does now. what now? I unplugged and went back to CWM but it still says waiting for adb mode.
Thanks for being patient with me BTW

efrant said:
1) Reboot your device in CWM and plug into you computer.
2) Install these drivers. If you don't know how, have a read here.
3) Download the adb files from here and unzip them in to a directory.
4) Open a command prompt in that same directory.
5) In the menus on your device in CWM, mount /system.
6) In the command prompt, type: adb pull /system/build.prop
7) Open that file in a text editor and change the line that starts with ro.sf.lcd_density to have a value of 320. Close and save it.
8) In the command prompt, type: adb push build.prop /system/
9) In the command prompt, type: adb chmod 644 /system/build.prop
10) Reboot.
Click to expand...
Click to collapse
I was looking at the instructions on installing those drivers and it appears that it requires that the phone be on and booted into Android.
I can't do that because I get no further than the black screen.

Don't panic I'm writing a new possible solution wait a few minutes

throwback1718 said:
I was looking at the instructions on installing those drivers and it appears that it requires that the phone be on and booted into Android.
I can't do that because I get no further than the black screen.
Click to expand...
Click to collapse
It can be booted in CWM instead. It makes no difference.
Sent from my Galaxy Nexus using Tapatalk 2

[How To] Get 100% Supercharged Using V6 Supercharger

For you who don't know abour V6 supercharger, read here http://forum.xda-developers.com/showthread.php?t=991276
Before using this script, it's recommended to patch your services.jar first. I'll tell you how to patch your services.jar
1. Download ultimatic jar patcher toos from here http://forum.xda-developers.com/showthread.php?t=1914159
Note:
a) If you are downloading Ultimatic_Jar_Patcher_Tools_RC6_ALL_DEX_Windows.exe.zip, THIS FILE IS NOT ZIP FILE, RENAME IT TO Ultimatic_Jar_Patcher_Tools_RC6_ALL_DEX_Windows.exe! Then simply execute that file using Administrator Privilege.
b) If you are downloading Ultimatic_Jar_Patcher_Tools_RC6_ALL_DEX_Windows.exe.zip and your are using CM 10.1, YOU CAN'T PATCH YOUR services.jar, BECAUSE adb.exe version isn't compatible with CM 10.1. Simply, download Ultimatic_Jar_Patcher_Tools_RC7_TEST6_ALL_DEX_ALL_OSes_NO_FLASH.zip, extract it, and replace adb.exe with your working adb.exe.
c) If you are downloading Ultimatic_Jar_Patcher_Tools_RC7_TEST6_ALL_DEX_ALL_OSes_NO_FLASH.zip, and you are using CM10.1, YOU CAN'T PATCH YOUR services.jar, because adb.exe version isn't compatible with CM10.1. Simply replace adb.exe inside that directory with your working adb.exe.
How to know that adb.exe is working or not for CM10.1? Simply do
Code:
adb.exe devices
If your device is OFFLINE, then your adb.exe is out to date. You can update your android SDK then run adb FROM YOUR android SDK directory.
Code:
adb.exe devices
If your device is ONLINE, then you have a working adb.exe. Copy this working adb.exe to ultimatic_jar_patcher directory.
If you are using CM9 or CM10, then you don't have to doubt about adb.exe :fingers-crossed:
2. Enable android debuging under developer option.
3. Before you're patching your services.jar, you have to test adb first, just to make sure that you won't failed on next step.
Code:
[email protected]:~/Downloads/Android/Tweaks/Ultimatic_Jar_Patcher_Tools# ./adb devices
List of devices attached
0123456789ABCDEF device
[email protected]:~/Downloads/Android/Tweaks/Ultimatic_Jar_Patcher_Tools# ./adb shell
[email protected]:/ #
{
"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"
}
4. Then execute ultimatic_jar_patcher_adb.bat (if you're using windows), or ultimatic_jar_patcher_adb.sh (if you are using linux)
Code:
[email protected]:~/Downloads/Android/Tweaks/Ultimatic_Jar_Patcher_Tools# sh ultimatic_jar_patcher_adb.sh
5. What if he ask you:
Press enter key when ready...
Click to expand...
Click to collapse
Just press enter
Enter an IP for Wireless ADB or...
Just press the enter key for USB:
Click to expand...
Click to collapse
Depend on how you enable debug mode. If you are using USB for debug mode, just press enter. If you are TCP/IP for debug mode, you have to insert your phone's IP separate with ":" and your debug port eg: 127.0.0.1:65535
It's better to run adb as Root if you can!
If it don't work, just try again and say no next time...
...since it should still work
Restart adb as root? Enter Y for Yes, any key for No:
Click to expand...
Click to collapse
Depend on how you execute this file, if you are execute this file using this command
Code:
[email protected]:~$ sh ultimatic_jar_patcher_adb.sh
You have to restart adb as root, just press Y, then ENTER.
If you are execute this file using this command
Code:
[email protected]:~$ sudo sh ultimatic_jar_patcher_adb.sh
Then you don't have to restart adb as root. Just press ENTER.
It's size and timestamp should change later!
Press the enter key when ready...
Click to expand...
Click to collapse
Just press enter.
==========================================================
About to run Ultimate Jar Power Tools...
==========================================================
Press the enter key when ready...
Click to expand...
Click to collapse
Just press enter :silly:
================================================
"Jelly ISCream" for Jelly Bean and Ice Cream!
================================================
Wanna SuperCharge your services.jar?
Enter Y for Yes, any key for No:
Click to expand...
Click to collapse
Press Y, then ENTER
Select a Launcher Strength...
(H)TK, (B)ulletProof, any key for Die-Hard:
Click to expand...
Click to collapse
Press ENTER to choose Die-Hard mode (I'm using this mode). Press B, then ENTER to choose BullerProof mode (This Breaks "Long-Press Back To Kill"!). Press H then ENTER to choose HardToKill mode.
Wanna test out The Maximum MultiTasking Mods?
Enter Y for Yes, any key for No:
Click to expand...
Click to collapse
If you are a gamer, press ENTER. Enabling multitask mode will make you have less free ram! But i'd rather enabling it, I prefer to multitask mode. Android phone would be better if it's not going lag, even you are running so much applications at one time. For gaming, i'd rather use my Laptop. If you want to use MultiTasking Mode, just press Y, then ENTER.
Wait until
Code:
[email protected]:/ #
Is coming up! Then YOU ARE DONE! Reboot your device, and you'll see "Android is upgrading..." screen at startup. Yes! Your dalvik cache is removed. Just wait a minute.
Step Two, how to use V6 Supercharger?
Note:
a. Make sure you have BusyBox v1.21.0.git, this will make V6 script working at all.
b. If you have patched your services.jar, you have to reboot your device first before going to use this script!
1. Download V6 Supercharger from here http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021 i'm usingV6_SuperCharger_for_Android-Update9_RC12_Test_6.sh.pdf one.
Note about downloading:
a. THIS FILE IS NOT PDF FILE, for best result, download from PC or LAPTOP by right-click on link, then select "SAVE LINK AS". Rename it to anything, but with .sh extension!
b. After download this script, push it to your device using adb.
Code:
[email protected]:~/Downloads/Android/Tweaks# adb push V6_SuperCharger_for_Android-Update9_RC12_Test_6.sh /sdcard/V6.sh
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
3735 KB/s (357571 bytes in 0.093s)
2. Run this Script as root, you can use adb or android terminal emulator to execute this script. In this tutorial, I'm using adb to execute this script, it's easier then using phone, since you have to input some character, and it's easier to ctrl+c if you're doing bad thing to cancel it
Code:
[email protected]:~/Downloads/Android/Tweaks# adb shell
[email protected]:/ #
Move to directory where your V6 script is located.
Code:
[email protected]:/ # cd sdcard
[email protected]:/sdcard #
Execute this script! Make sure you are PASS on TEST DRIVE!
If you are PASS, then you can go further.
4. What if he ask:
Please select scrolling speed (1 - 3):
Click to expand...
Click to collapse
Scrolling speed is sleep time to display next output, select 3 mean you have to wait 3 seconds to see next output. Don't like waiting? Just selet 0, he don't give you "0" option, but it will make this script faster since we don't have to wait to see next output. Press 0, then ENTER.
Pick a Kernel Strength / "Reboot Tolerance":
Click to expand...
Click to collapse
Press H then ENTER.
Enable Miscellaneous & SD Card Speed Tweaks?
Enter Y for Yes, any key for No:
Click to expand...
Click to collapse
Press Y, then ENTER
Enable 3G TurboCharger Enhancement?
Enter Y for Yes, any key for No:
Click to expand...
Click to collapse
Press Y, then ENTER
Run Fix Alignment on boot?
Note 1 : If you say Yes...
Wheel Alignment and Fix Emissions...
...On Boot are automatically disabled!
Note 2 : If you say No...
Wheel Alignment and Fix Emissions...
...boot options become available!
Enter Y for Yes, any key for No:
Click to expand...
Click to collapse
Press Y, then ENTER
Run Detailing on boot?
Enter Y for Yes, any key for No:
Click to expand...
Click to collapse
Press Y, then ENTER
How often? 1=every boot to 9=every 9th boot:
Click to expand...
Click to collapse
You choose, I'm using every 3. So press 3 then ENTER
Disable AWESOME V6 Animation? (Say "NO"!)
=======
Enter Y for Yes, any key for No:
Click to expand...
Click to collapse
Just press ENTER
Apply SuperMinFree Calculator Settings?
If not, come back later for more options!
Enter Y for Yes, any key for No:
Click to expand...
Click to collapse
Press Y, then ENTER
Done, you've got 100% SuperCharged!
Press Thanks if this useful for you

Confirmed!
V6 Supercharger DOESN'T WORK ON CM 10.1. Use KickAssKernelizer and 3G_Supercharger instead.

help me, i downloaded the 1st one, i just cant rename it, window just keep it as a zip file

Thanks for the thread. I was stuck at 50% for the longest time. After seeing your thread, I unSupered my device, and followed your steps and was 100% in less than 10 minutes.
The trick was doing the Ultimatic Jar Patch BEFORE running the V6 script. Thanks for the help!

omegahanggara said:
Confirmed!
V6 Supercharger DOESN'T WORK ON CM 10.1. Use KickAssKernelizer and 3G_Supercharger instead.
Click to expand...
Click to collapse
How about KitKat?
CM11 Powered G-Wonder

[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:

[GUIDE] Set up Android SDK (ADB) for Windows 8 / 8.1 / [ADB][Bootloader][Fastboot]

Android SDK - Powerful tool and easy to set up for use with your HTC One M8
{
"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"
}
The Reason that you would want to use Android SDK is because its very easy, it's well updated and it just WORKS! There is much more use with HTC devices with adb then with Samsung when it comes to the daily things like splash screens, radio updates, firmware. You will be dealing a lot with the bootloader and fastboot flashing. So to help out, I will post a helpful guide to help you get started for use with the HTC One M8.​
Click to expand...
Click to collapse
USB 3.0 Information if Needed
USB 3.0 Windows 8 Solution Link 1
USB 3.0 Windows 8 Solution Lin 2 - Found in above thread
Part 1. Follow These Steps Below - (Preparation)
1. Download Android SDK For Windows
2. Click the
either the 32bit version or 64bit version
3. Create a folder in the C: and name it Android. See below
4. Place adt-bundle-windows in the Android Folder you just created. Use WinZip, WinRAR or 7-Zip to extract the contents inside the folder. See Below
5. Once extracted, Double click SDK Manager and instal all 4.4.2 and 4.3 items and under tools (SDK Tools and Platform Tools). See Picture Below
6. After all packages are installed and updated, download the latest HTC Sync Manager and install once download completes
7. Once Sync Manager completes installation process, go to control panel and uninstall HTC Sync Manager only, you will see HTC Driver in there as well (LEAVE IT THERE)
8. Important, make sure you enable developer options and turn on USB Debugging. Instructions Below if you are unsure how to do that
1. Go to Settings > About > Software information > More > Tap Build Number 5x
2. Once you get notification saying Developer options is unlocked go back to > settings
3. Click Developer options
4. Add check in the box USB Debugging
9. Plug phone into the computer and let it install all the drivers, you should see pop ups.
Click to expand...
Click to collapse
The Computer and Phone are now prepped for you to start the whole ADB Process
Click to expand...
Click to collapse
Part 2. Verifying ADB is set up properly and Working
1. Open Command Prompt and Change directories to your platform-tools folder. This is where all the adb files are located. See Below
In Command Prompt Type - Refer to Part 3 so you no longer need to Change Directory
Code:
cd c:\Android\sdk\platform-tools
2. In Command prompt type
Code:
adb devices
3. If your output shows your device attached like below, then you are good to go!!!
YOU ARE FINISHED!!! Below is a command to get into the bootloader if interested!! Good Luck
Click to expand...
Click to collapse
Part 3. Environment Variables - No need to Change Directory in Command Prompt Anymore (This is if you want to - Not Required)
1. Press Win+R, then type sysdm.cpl
2. Click Advanced Tab
3. Click Environment Variables Button
4. Under System Variables, find Path, click to highlight it and then hit the edit button
5. Go to the end of the Variable Value and add the following exactly as you see it in the code box below
Code:
;C:\Android\sdk\platform-tools
6. Click OK to accept the changes you just added
7. Open Command Prompt again to verify by pressing Win+R and type cmd and hit enter
8. Once Command Prompt is open -> Simply type adb devices with your device connected with USB Debugging already enabled
9. If you did everything correctly, there is no need to change paths anymore
Click to expand...
Click to collapse
Getting into the Bootloader
In Command Prompt Type:
Code:
adb reboot bootloader
Thanks To:
Ashraf - Images used for Environment Variables - Not all were his since the guide was modified

Reserved if needed
Sent from my HTC6525LVW using Tapatalk

Thanks for the guide!
Can you add instructions for how to add adb to the environment variables so it can be accessed without having to cd to the platform-tools folder?
Sent from my HTC One M8

VolcanicSkunk said:
Thanks for the guide!
Can you add instructions for how to add adb to the environment variables so it can be accessed without having to cd to the platform-tools folder?
Sent from my HTC One M8
Click to expand...
Click to collapse
I will look into it if I have some time, you can post it in here if you like if you think others will appreciate it. Thanks
Sent from my HTC6525LVW using Tapatalk

OP Updated
Updated OP
1. Added Environment Variables to no longer have to Change Directory
2. Cleaned up OP
3. Added Thanks

bdorr1105 said:
Updated OP
1. Added Environment Variables to no longer have to Change Directory
2. Cleaned up OP
3. Added Thanks
Click to expand...
Click to collapse
Will this work for Windows 7 as well? I have Windows 7, and every time I try to plug my phone in to start the unlocking process, and I click on "Get Token ID"
It just sits at that screen and does nothing. Any help would be greatly appreciated!

theimmortalone said:
Will this work for Windows 7 as well? I have Windows 7, and every time I try to plug my phone in to start the unlocking process, and I click on "Get Token ID"
It just sits at that screen and does nothing. Any help would be greatly appreciated!
Click to expand...
Click to collapse
It should work the same for windows 7, but keep in mind the guide was created on Windows 8....I do not know the path of your adb folder, also, the phone will prompt you to allow the computer to access it, YOU HAVE TO ALLOW IT, or it will never work!!!
What command did you type? I dont see anything except HTC' ????

bdorr1105 said:
It should work the same for windows 7, but keep in mind the guide was created on Windows 8....I do not know the path of your adb folder, also, the phone will prompt you to allow the computer to access it, YOU HAVE TO ALLOW IT, or it will never work!!!
What command did you type? I dont see anything except HTC' ????
Click to expand...
Click to collapse
Okay, well that is my problem then, every time I plug my phone in, and it never asks me to allow it or not. How can I fix that issue? IT does it on my XP, but that is slower then hell so I prefer not to use it.
And as far has the "HTC" part, it doesn't go past that folder. I thought the all-in-one root kit was supposed to do it automatically?

theimmortalone said:
Okay, well that is my problem then, every time I plug my phone in, and it never asks me to allow it or not. How can I fix that issue? IT does it on my XP, but that is slower then hell so I prefer not to use it.
And as far has the "HTC" part, it doesn't go past that folder. I thought the all-in-one root kit was supposed to do it automatically?
Click to expand...
Click to collapse
You may have already accepted it, lets resolve the steps in order to make sure thats the problem, if you follow the guide, you create a Android folder and then extract the bundle inside of that
the path should be C:\Android\sdk\platform-tools
I want to you to open Command Prompt and do the following:
1. Win+R or Start>Run>cmd Hit enter
2. cd c:\Android\sdk\platform-tools
3. type adb devices > Look for prompt on phone and allow it
If it shows your device connected you are good to go

bdorr1105 said:
It should work the same for windows 7, but keep in mind the guide was created on Windows 8....I do not know the path of your adb folder, also, the phone will prompt you to allow the computer to access it, YOU HAVE TO ALLOW IT, or it will never work!!!
What command did you type? I dont see anything except HTC' ????
Click to expand...
Click to collapse
bdorr1105 said:
You may have already accepted it, lets resolve the steps in order to make sure thats the problem, if you follow the guide, you create a Android folder and then extract the bundle inside of that
the path should be C:\Android\sdk\platform-tools
I want to you to open Command Prompt and do the following:
1. Win+R or Start>Run>cmd Hit enter
2. cd c:\Android\sdk\platform-tools
3. type adb devices > Look for prompt on phone and allow it
If it shows your device connected you are good to go
Click to expand...
Click to collapse
I honestly do not remember that pop up coming up on my phone. So I'm not sure what's up with that. But I will do what you said above, and report back.

theimmortalone said:
I honestly do not remember that pop up coming up on my phone. So I'm not sure what's up with that. But I will do what you said above, and report back.
Click to expand...
Click to collapse
Also make sure have USB debugging enabled.... It's part of the process
Sent from my HTC6525LVW using Tapatalk

bdorr1105 said:
You may have already accepted it, lets resolve the steps in order to make sure thats the problem, if you follow the guide, you create a Android folder and then extract the bundle inside of that
the path should be C:\Android\sdk\platform-tools
I want to you to open Command Prompt and do the following:
1. Win+R or Start>Run>cmd Hit enter
2. cd c:\Android\sdk\platform-tools
3. type adb devices > Look for prompt on phone and allow it
If it shows your device connected you are good to go
Click to expand...
Click to collapse
SUCCESS!!
I believe I should be good to go now right?
---------- Post added at 06:07 PM ---------- Previous post was at 05:59 PM ----------
theimmortalone said:
SUCCESS!!
I believe I should be good to go now right?
Click to expand...
Click to collapse
Holy **** I finally got it to work. Thanks for your help man! Appreciate it!

theimmortalone said:
SUCCESS!!
I believe I should be good to go now right?
Click to expand...
Click to collapse
Yes you should, you need to go to C:\Android and double click SDK Manager.exe and update Android 4.4.2 API by clicking the check box. See Attached Picture
If you do not want to have to change directories, then you need to add that path just as the instructions say to do!
C:\Android\sdk\platform-tools

theimmortalone said:
SUCCESS!!
I believe I should be good to go now right?
---------- Post added at 06:07 PM ---------- Previous post was at 05:59 PM ----------
Holy **** I finally got it to work. Thanks for your help man! Appreciate it!
Click to expand...
Click to collapse
No problem