root problem: NookandZergy.bat not working here - Barnes & Noble Nook Tablet
Sorry for opening a new thread on this, but as new users can't post - for a good reason, I am sure - in the dev's section, I, being a new user, can't as well...
I have the same problem as described by haggardh and arko.amit, which is the nt not showing up when running the NookandZergy.bat after following all the steps mentioned, hopefully, properly. Running the NookandZergy.bat as admin gives an error message stating the command "adb" is unknown.
Just hoping to emphasise that this issue might be statistically significant (and worth looking into)...other than that this is just another me-too-post. Sorry once more.
Give this a go:
http://forum.xda-developers.com/showthread.php?t=1363652
i had to download the program in that thread and delete all usb references to Nook from my computer.
My Solution to Root
Wurstwarenfachverkäuferin said:
Sorry for opening a new thread on this, but as new users can't post - for a good reason, I am sure - in the dev's section, I, being a new user, can't as well...
I have the same problem as described by haggardh and arko.amit, which is the nt not showing up when running the NookandZergy.bat after following all the steps mentioned, hopefully, properly. Running the NookandZergy.bat as admin gives an error message stating the command "adb" is unknown.
Just hoping to emphasise that this issue might be statistically significant (and worth looking into)...other than that this is just another me-too-post. Sorry once more.
Click to expand...
Click to collapse
I experienced some of the same problems you and haggard wrote about and even some other users that were experiencing no serial number showing up when running the Nookandzergy.bat. After reading and a little experimentation of my own I got mine rooted last night. My test machine was Windows XP SP3 I am skipping the tgps.apk part on the Nook because I ran into no problems with it. It did goes as the instructions said. With that said make sure you put all the checks in the right place in the debug menu.
First of all if you can't run adb then you have the adb.exe in the wrong folder or you are trying to execute with the wrong path. Should be in the C:\ntroot directory. Open a command line up (Start > RUN >CMD)
You will need to change to directory c:\ntroot
Once your cmd prompt reads C:\ntroot you should be able to run adb. You really shouldn't have to unless you are running into a problem with the serial number not showing up after running zerg. If that is the case you can always run "adb devices" that will start the adb daemon and then run the command and tell you rather or not your computer is seeing the nook. If you get no devices connected then you are back to the driver issue.
My solution for the driver issue I got the same USB Mass Storage Device and then would try and change the driver to the Android one, but kept getting the above problem when trying to run zerg.
So I uninstalled the driver (Android and USB Mass Storage) and unplugged the Nook.
Then in Windows Explorer went to the usbdrivers folder and right-clicked on the file android_winusb.inf and clicked "install"
I then plugged the nook back in and the driver showed correctly in Device Manager as an Android device.
I then ran zergy again and it all worked an the ID showed up correctly.
I hope this helps.
k
Thanks for the suggestions. The OS is Win 7 64 if that matters.
I have de- and reinstalled the usb-driver several times in the device-manager (installing by "install..." from explorer's context menu doesn't work for this file and this OS) - the device just doesn't show up in command line, regardless whether I use the adb devices command or run the nookandzergy.bat.
Sounds definitely to be the driver. I read the link posted by AugustusBot helpful, but not sure it would work for sure. I had to uninstall and reinstall until finally I ran the INF like you mentioned that didn't work for you.
Does the device show up with an exclamation or as a USB mass storage device?
With no specific driver installed (intentionally, that is), the device is shown as both usb mass storage device and "nook tablet" with the yellow exclamation mark within the device manager.
I also used that usb deview tool mentioned in the other thread to wipe all usb devices. This doesn't do a permanent uninstall - as deleting the driver would. Unplugging a device and plugging it in again and it would just show up as it did before... Either way, the tool doesn't help here.
Have you right clicked on Nook tablet within device manager clicked properties > driver > update driver software > update driver > browse my computer for driver software > Let me pick from a list of device drivers > Have Disk > Browse > C:\ntroot\usbdrivers\android_winusb.inf
I just tried that process on a Windows 7 64bit and got an error saying the device driver is not compatible with a 64 bit OS. If you get the same error you may have to find the 64 bit version of that device driver or if you are familiar with working with XP classic within Windows 7 you may have better luck using it through that.
Try right clicking on the mass storage device and select to install manually then install from a specific location, have disk, then select the inf file for the driver... might work.
Sent from my BNTV250 using xda premium
I did install the driver both ways using the bat-file and manually through device manager, pointing to the folder that contains the inf-file. Actually, you can't point to a file but only to folders (saying "you", I mean "me", of course; is that different on your machine?)
(Why do I get a prevent-spam-wait-5-mins-message editing my own post? Weird.)
I have successfully updated the drivers under Device Manager and it changed from nook device with exclamation mark to android composite interface and and it still does not show up when running the nookandzrgy.bat file. I tried the methods listed here to no avail. Any new info out there?
armysean77 said:
I have successfully updated the drivers under Device Manager and it changed from nook device with exclamation mark to android composite interface and and it still does not show up when running the nookandzrgy.bat file. I tried the methods listed here to no avail. Any new info out there?
Click to expand...
Click to collapse
Download the settings file listed in the post via your tablet, install using the package installer, enable debugging (checking both debugging options) run the script to root.
Sent from my HTC Glacier using xda premium
I had no end of difficulties with the root process.
Running Windows 7 32 bit.
Procedure to root instructions neglect to emphasise the NEED to DROP the Nook Tablet into debug mode first before connecting it to the PC. I didn't do this, and so Window drivers were installed automatically on first connect, and this started a long trip trying to replace the drivers to no avail. Eventually managed to removed the drivers from all USB using the tools from another thread.
After that, I managed to install the USB drivers and have the Nook show up as an Android phone.
Unticked/ticked all debug mode a second time to ensure they are locked in place.
Run the Zergy.bat and get the numbers for ID of the tablet, and the thing starts to proceeds and then stops with an error stating that it is not a Tablet device... 8(
Gave up and re run the entire procedure on a Windows XP laptop (fresh install) and everything went through without a hitch. I now have a rooted Nook Tablet.
I suspect something in Windows 7 is interferring with the second script.
Key point:
Put Tablet in debug mode first.
Untick and retick the USB connection on Tablet before each attempt to run Zergy script.
Another thing I did, but was unsure if it fixed anything was manually changed the runmefirst.bat script to look like this:
@echo off
echo Please unplug your nook device before continuing!
pause
if exist "c:\ntroot\.android\adb_usb.ini" echo You do not need to have it added!
IF NOT EXIST "c:\ntroot\.android\" md "c:\ntroot\.android"
echo 0x2080 > "c:\ntroot\.android\adb_usb.ini"
echo success!
echo now plug it back in
echo now install the drivers - instructions in the thread
echo **************************************************************
echo * Install "Nook" with the drivers I provided in this pack. *
echo * You can find the fixed drivers in the "usbdrivers" folder. *
echo * After your done you should have adb access through DOS! *
echo **************************************************************
devmgmt.msc
pause
echo "now you can run the Nook&Zergy"
ping 1.1.1.1 -n 1 -w 2000 > NUL
and the nookandzergy.bat script to look like this:
@echo off
color 0c
adb kill-server
cls
:vendorfixed
find "0x2080" "c:\ntroot\.android\adb_usb.ini"
if errorlevel==0 goto start
if errorlevel==1 goto novendor
:start
cls
adb kill-server
adb devices
echo did your nook Tablet show up?
echo type Y for yes and N for no
SET /P menunr=Please make your decision:
IF %menunr%==Y (goto check)
IF %menunr%==N (goto sorry)
:check
echo first need to make sure you didnt lie about it showing up and check for root.
adb wait-for-device
echo verifying that your device is indeed a Barnes and Noble Nook tablet
del build.prop
adb pull system/build.prop
find "ro.product.device=blaze" build.prop
if ERRORLEVEL==0 SET device=Nook Tablet
if ERRORLEVEL==1 goto oops
echo now checking for root!
del su.txt
adb pull /system/bin/su su.txt
cls
if exist su.txt echo already rooted! && goto prerooted
if not exist su.txt goto ok
k
cls
echo your device is a %device% meaning we can continue!
ping 1.1.1.1 -n 1 -w 2000 > NUL
echo now just making sure you WANT to root it!
:choice1
set /p C=(Y/N)?
for %%? in (Y N) do if /I "%C%"=="%%?" goto ok1
goto choice1
k1
set C1=%C%1
goto %C1%
:Y1
adb push zergrush /data/local/zergy
adb shell "chmod 755 /data/local/zergy;cd /data/local/;./zergy"
adb wait-for-device
adb install Superuser.apk
adb remount
adb push su /data/local/tmp/
adb shell "cd /data/local/tmp;chmod 777 su;cd /;mount -o remount,rw -t rootfs rootfs /"
adb push su /system/bin/su
adb shell chmod 4755 /system/bin/su
adb install busyboxinstall.apk
cls
:N1
echo would you like to install gApps?
:choice2
set /p C=(Y/N)?
for %%? in (Y N) do if /I "%C%"=="%%?" goto ok2
goto choice2
k2
set C2=%C%2
goto %C2%
:Y2
set gapps=yes
adb remount
adb push system\app\CarHomeGoogle.apk /system/app/
adb shell chmod 644 /system/app/CarHomeGoogle.apk
adb push system\app\FOTAKill.apk /system/app/
adb shell chmod 644 /system/app/FOTAKill.apk
adb push system\app\GenieWidget.apk /system/app/
adb shell chmod 644 /system/app/GenieWidget.apk
adb push system\app\GoogleBackupTransport.apk /system/app/
adb shell chmod 644 /system/app/GoogleBackupTransport.apk
adb push system\app\GoogleCalendarSyncAdapter.apk /system/app/
adb shell chmod 644 /system/app/GoogleCalendarSyncAdapter.apk
adb push system\app\GoogleContactsSyncAdapter.apk /system/app/
adb shell chmod 644 /system/app/GoogleContactsSyncAdapter.apk
adb push system\app\GoogleFeedback.apk /system/app/
adb shell chmod 644 /system/app/GoogleFeedback.apk
adb push system\app\GooglePartnerSetup.apk /system/app/
adb shell chmod 644 /system/app/GooglePartnerSetup.apk
adb push system\app\GoogleQuickSearchBox.apk /system/app/
adb shell chmod 644 /system/app/GoogleQuickSearchBox.apk
adb push system\app\GoogleServicesFramework.apk /system/app/
adb shell chmod 644 /system/app/GoogleServicesFramework.apk
adb push system\app\LatinImeTutorial.apk /system/app/
adb shell chmod 644 /system/app/LatinImeTutorial.apk
adb push system\app\MarketUpdater.apk /system/app/
adb shell chmod 644 /system/app/MarketUpdater.apk
adb push system\app\MediaUploader.apk /system/app/
adb shell chmod 644 /system/app/MediaUploader.apk
adb push system\app\NetworkLocation.apk /system/app/
adb shell chmod 644 /system/app/NetworkLocation.apk
adb push system\app\OneTimeInitializer.apk /system/app/
adb shell chmod 644 /system/app/OneTimeInitializer.apk
adb push system\app\Talk.apk /system/app/
adb shell chmod 644 /system/app/Talk.apk
adb push system\app\Vending.apk /system/app/
adb shell chmod 644 /system/app/Vending.apk
adb push system\etc\permissions\com.google.android.maps.xml /system/etc/permissions/
adb push system\etc\permissions\features.xml /system/etc/permissions/
adb push system\framework\com.google.android.maps.jar /system/framework/
adb push system\lib\libvoicesearch.so /system/lib/
echo Thank you for choosing to install gapps courtesy of anlog
ping 1.1.1.1 -n 1 -w 2000 > NUL
cls
:N2
echo Would you like to replace certain system applications to make you have a more tablet like experience?
echo this replaces Keyboard, Email, Gallery, and adds live wallpapers! Please select Y or N.
echo you need another launcher to be able to use live wallpapers.
:choice3
set /p C=(Y/N)?
for %%? in (Y N) do if /I "%C%"=="%%?" goto ok3
goto choice3
k3
set C3=%C%3
goto %C3%
:Y3
adb push Email.apk /system/app/Email.apk
adb push Gallery3D.apk /system/app/Gallery.apk
adb push LatinIME.apk /system/app/LatinIME.apk
adb push LiveWallpapers.apk /system/app/LiveWallpapers.apk
adb push LiveWallpapersPicker.apk /system/app/LiveWallpapersPicker.apk
adb shell chmod 644 /system/app/Email.apk
adb shell chmod 644 /system/app/Gallery.apk
adb shell chmod 644 /system/app/LatinIME.apk
adb shell chmod 644 /system/app/LiveWallpapers.apk
adb shell chmod 644 /system/app/LiveWallpapersPicker.apk
:N3
@echo off
echo Please select 1 for Go launcher
echo Please select 2 for ADW Launcher
echo please select 3 for HoneyComb Launcher
echo Please select 4 for none of them and to continue to the debloater
SET /P launch=Please make your decision:
IF %launch%==1 (set launcherinstall="yes "& set launcher=GO)
IF %launch%==2 (set launcherinstall="yes "& set launcher=adw)
IF %launch%==3 (set launcherinstall="yes "& set launcher=Honeycomb_Launcher)
IF %launch%==4 (goto debloater)
echo %launcher%
adb install launcher\%launcher%.apk
IF %launcherinstall%=="yes " adb install launcher\Homecatcher.apk
pause
goto debloater
:sorry
echo Your device is not found, I'm sure USB debugging HAS to be enabled.
ping 1.1.1.1 -n 1 -w 2000 > NUL
exit
ops
echo your device is NOT a nook tablet! Please try again with either usb debugging properly enabled, or with the correct device hooked up. You might also need to install drivers!
echo just incase you missed doing it, running runmefirst.bat
if exist runmefirst.bat call runmefirst.bat
if not exist runmefirst.bat echo No batch file found!
:complete
echo OK!
:N4
echo Thank you for using Indirect's batch script to root the nook tablet combined with Anlog's script to install gApps.
adb shell chmod 644 /system/app/*.apk
adb shell chmod 644 /data/app/*.apk
set install=ok
if install==ok echo GOOOD JOB! Now rebooting!
adb reboot
ping 1.1.1.1 -n 1 -w 2000 > NUL
exit
:novendor
cls
echo Oops! You do not have the USB Vendor ID entered into the correct file! Running runmefirst to correct this.
ping 1.1.1.1 -n 1 -w 2000 > NUL
call runmefirst.bat
goto vendorfixed
rerooted
cls
echo Your device was found to be rooted. Which is upsetting because now the root won't work again (you already have root) so you also can't use this script to install gApps or system mods.
echo _
echo because ADB doesn't allow us to remount unless adb is running as root (can't run without a kernel mod)
echo _
echo You can however download the one click unroot app in the Android Development section to unroot after you install it on your device.
echo _
echo However, before you do that, I suggest backing everything up as it COMPLETELY wipes the device (including the system partition) so you lose root and all mods.
echo _
echo Have a nice day!
ping 1.1.1.1 -n 1 -w 10000 > NUL
exit
:debloater
cls
echo Do you want to de-bloat the device?
echo This does NOT remove anything that would remove access to the nook function of E-reading and whatnot. Just removes
echo Hulu, default launcher (if you installed a new one), default search app (if you used gApps), Chess, Sudoku and thats it.
echo Search being removed will actually stop you from using the search function in the nook bar.
:choice4
set /p C=(Y/N)?
for %%? in (Y N) do if /I "%C%"=="%%?" goto ok4
goto choice4
k4
set C4=%C%4
goto %C4%
:Y4
ebloatmenu
cls
echo Please select 1 for Full Debloat (Launcher, games, Hulu and pandora, so basically 2,3, and 4.)
echo Please select 2 for Launcher only removal (Will only run if you have installed a new launcher) It's a safety feature.
echo Please select 3 for Game applications removal
echo Please select 4 for Media application removal (Hulu and Pandora) (NOT NETFLIX)
echo Please select 5 to run the EXTREME debloater (Does all of the above and
echo removes ALL barnes and noble apps from your device
echo so you lose ALL functionality towards B and N but
echo you have a normal android tablet
echo DO NOT ASK FOR SUPPORT WITH THIS OPTION, you will be ignored.)
echo Select 6 to finish this section of the script.
SET /P debloat=Please make your decision:
IF %debloat%==1 goto Full
IF %debloat%==2 goto Launcher
IF %debloat%==3 goto Game
IF %debloat%==4 goto Media
IF %debloat%==5 goto Extreme
IF %debloat%==6 goto complete
:Full
adb shell rm -r /system/app/Chess.apk
adb shell rm -r /system/app/Sudoku.apk
adb shell rm -r /system/app/Crossword.apk
if %launcherinstall%==yes adb shell rm -r /system/app/Home.apk
if %gapps%==yes adb shell rm -r /system/app/GSearch.apk
adb shell rm -r /system/app/Hulu_Plus_159.apk
adb shell rm -r /system/app/Pandora.apk
set gapps=no
goto debloatmenu
:Launcher
if %launcherinstall%==yes adb shell rm -r /system/app/Home.apk
if %gapps%==yes adb shell rm -r /system/app/GSearch.apk
set gapps=no
goto debloatmenu
:Games
adb shell rm -r /system/app/Chess.apk
adb shell rm -r /system/app/Sudoku.apk
adb shell rm -r /system/app/Crossword.apk
if %gapps%==yes adb shell rm -r /system/app/GSearch.apk
set gapps=no
goto debloatmenu
:Media
adb shell rm -r /system/app/Hulu_Plus_159.apk
adb shell rm -r /system/app/Pandora.apk
if %gapps%==yes adb shell rm -r /system/app/GSearch.apk
goto debloatmenu
:Extreme
Echo ARE YOU POSITIVE YOU WANT TO RUN THIS?
echo We will not be mad if you say no,
echo these apps that are removed do nothing to the tablet
echo but remove the ability to read from the library and in general use the entire nook as an e-reader / anything from barnes and noble
echo and it turns it into a normal android tablet.
echo I removed these apps and the tablet itself functions fine
echo I just can't use anything from B&N.
echo If you run this, I WILL NOT HELP YOU!
echo Use the one click unroot app to get back all of these apps.
:choice5
set /p C=(Y/N)?
for %%? in (Y N) do if /I "%C%"=="%%?" goto ok5
goto choice5
k5
set C5=%C%5
goto %C5%
:Y5
adb shell rm -r /system/app/Accessories.apk
adb shell rm -r /system/app/AppLauncher.apk
adb shell rm -r /system/app/B3AndroidReader.apk
adb shell rm -r /system/app/BnAppInstaller.apk
adb shell rm -r /system/app/BnAuthenticationService.apk
adb shell rm -r /system/app/BnCloudRequestSvc.apk
adb shell rm -r /system/app/BnConnectivityService.apk
adb shell rm -r /system/app/BnPolicyManagerSvc.apk
adb shell rm -r /system/app/CloudService.apk
adb shell rm -r /system/app/CryptoServer.apk
adb shell rm -r /system/app/DemoMode.apk
adb shell rm -r /system/app/DRPReader.apk
adb shell rm -r /system/app/GSearch.apk
adb shell rm -r /system/app/Home.apk
adb shell rm -r /system/app/LatinImeTutorial.apk
adb shell rm -r /system/app/Library.apk
adb shell rm -r /system/app/NookCommunity.apk
adb shell rm -r /system/app/Quickoffice_Viewer_3.3.5.apk
adb shell rm -r /system/app/RDGEReaderAcclaim.apk
adb shell rm -r /system/app/Reader.apk
adb shell rm -r /system/app/Shop.apk
adb shell rm -r /system/app/Social.apk
adb shell rm -r /system/app/Hulu_Plus_159.apk
adb shell rm -r /system/app/Pandora.apk
adb shell rm -r /system/app/Chess.apk
adb shell rm -r /system/app/Sudoku.apk
adb shell rm -r /system/app/Crossword.apk
if %launcherinstall%==yes adb shell rm -r /system/app/Home.apk
if %gapps%==yes adb shell rm -r /system/app/GSearch.apk
goto debloatmenu
:N5
echo you decided to not run the Extreme Debloater
echo now returning you to the debloater menu.
ping 1.1.1.1 -n 1 -w 1000 > NUL
goto debloatmenu
My reasoning was prior to me changing the path from %USERPROFILE to C:\ntroot I was receiving an error in profile path due to Windows XP having the profile set to C:\documents and settings\kerry63\... and I was getting some error about not being able to parse the space in "documents and settings".
I would not imagine this needing to be changed on Windows 7 due to the fact that the %USERPROFILE should be C:\users\kerry63 hence no spaces. All the runmefirst.bat script does is place the .android folder with a .ini file that gives the vendor ID to the nookandzergy.bat script.
This is nothing new just trying to make sure all the bases are covered since people do run different Windows OS. I take no credit for the script just trying to give advice and procedures that helped me get mine working. I did have all the problems that everyone else spoke about.
I had to triple check the three changes made in the debug mode by tgps.apk on the NOOK.
Changed the script and then ran it.
Installed drivers and uninstalled them until I got the NOOK! and installed the .inf prior to the plugging in of the NOOK.
The above scripts are verbatim of what I used you can use them by just pasting them separately into notepad and naming them accordingly.
Hope this helps.
armysean77 said:
I have successfully updated the drivers under Device Manager and it changed from nook device with exclamation mark to android composite interface and and it still does not show up when running the nookandzrgy.bat file. I tried the methods listed here to no avail. Any new info out there?
Click to expand...
Click to collapse
Make sure the Tablets is in debug mode and automount is unticked. Even if it is set correctly, untick and retick the settings BEFORE each attempt to run the Zergy script.
In my case, I manage to get it ot recognise the tablet, but the scripot aborted with an error stating that it is not a tablet device... 8(
Running the same procedure again on another laptop running xp worked.
kerry63 said:
Another thing I did, but was unsure if it fixed anything was manually changed the runmefirst.bat script to look like this:
[...]
My reasoning was prior to me changing the path from %USERPROFILE to C:\ntroot I was receiving an error in profile path due to Windows XP having the profile set to C:\documents and settings\kerry63\... and I was getting some error about not being able to parse the space in "documents and settings".
I would not imagine this needing to be changed on Windows 7 due to the fact that the %USERPROFILE should be C:\users\kerry63 hence no spaces. All the runmefirst.bat script does is place the .android folder with a .ini file that gives the vendor ID to the nookandzergy.bat script.
This is nothing new just trying to make sure all the bases are covered since people do run different Windows OS. I take no credit for the script just trying to give advice and procedures that helped me get mine working. I did have all the problems that everyone else spoke about.
I had to triple check the three changes made in the debug mode by tgps.apk on the NOOK.
Changed the script and then ran it.
Installed drivers and uninstalled them until I got the NOOK! and installed the .inf prior to the plugging in of the NOOK.
The above scripts are verbatim of what I used you can use them by just pasting them separately into notepad and naming them accordingly.
Hope this helps.
Click to expand...
Click to collapse
If I got that right, you changed the paths replacing %userprofile% with c:\ntroot. Sorry for asking, as I should be able to find out myself, but... are there more changes made? (The runmefirst.bat you used is not the same (anymore) as in the root-thread by indirect.)
However, I replaced %userprofile% with c:\ntroot in both scripts. The outcome was an empty .android folder being created in c:\ntroot by the runmefirst.bat - this didn't happen before. Other than that still no device listed by adb.
I gave it one more try and used the runmefirst.bat from the usbdrivers.zip - after that the nook was listed and more or less rootable (more: it kind of worked; less: the root script's command line just closed at some point within the debloating leaving the device in Idontknowwhat state... but it still seems to work)
However, as there are two files named runmefirst in the whole package, people should be told which runmefirst.bat to actually run first (or at all).
Thanks for all the advice! It did help.
Solved
I tried several computers and could not get the nook to install with the unknown devise question mark. I finally figured it out. I had an SD card already installed in the Nook. It kept getting registered as a mass storage device. I removed the SD card and started with a fresh install of XP. Everything worked perfect.
this orked for me that way... hope this help you guys.
dodgepot said:
Try right clicking on the mass storage device and select to install manually then install from a specific location, have disk, then select the inf file for the driver... might work.
Sent from my BNTV250 using xda premium
Click to expand...
Click to collapse
thanks. for all the great minds and great Devs here.
Files
Do you guys still have access to these files all links I've found point to a drop box folder that is out of order.
Related
[Q] ADB Problems
I just rooted my x2, and installed eclipse. I cant get adb to push, I get permisson denied. I cant do adb remount cuz I get operation not permitted. I had it working once, but now It wont let me do it. Im trying to theme and I need adb push to work. I also tried putting an app on the sdcard and using root explorer to change the apk, all i did was make 1 png edit and the apk wasnt working. Im not sure whats going on and any help would be nice.
TheMuffStuff said: I just rooted my x2, and installed eclipse. I cant get adb to push, I get permisson denied. I cant do adb remount cuz I get operation not permitted. I had it working once, but now It wont let me do it. Im trying to theme and I need adb push to work. I also tried putting an app on the sdcard and using root explorer to change the apk, all i did was make 1 png edit and the apk wasnt working. Im not sure whats going on and any help would be nice. Click to expand... Click to collapse My Thoughts Are, PC Mode Updated Drivers Correct Path Pointing To ADB Folder Inside Android SDK Some Computers Need The USB Cable To Be Plugged In The Back Not The Front Due To Front Ports Aren't Supported Make Sure You're Using The Right Commands ie. adb push <Local> <Remote> -Copy File/Dir To Device
Im gunna try some more today, also when I just make 1 png edit in an apk, and use my sdcard, then root explorer to swap the apks, the new apk gets an error, even tho I only made 1 edit. Its being weird. Edit: Ive tried PC Mode, updated all drivers. My paths are fine, as im on the same computer that ive done all my theming on for my fascinate/charge. I am using USB's in the back, same one ive always used. Im using the right commands. My phone is rooted using the 1 click script. Im not really sure what else it could be. Im just getting permission errors, I have a feeling its a root problem. I dont know. Edit:: The only thing I can think of is trying to sbf back to stock, update to pre-rooted gingerbread, and try that?
Honestly it sounds like you are not rooted. I had troubles running the script as well after it came out. I had already rooted earlier in the day using the actual researchers blog instructions. http://vulnfactory.org/blog/2011/08/25/rooting-the-droid-3/ Those steps are all you need then you can push the su and Superuser.apk files. I wrote a vb script file to install the drives and push the files but I need to do more testing before I put that out for people to try. Using the one click is nice but with everything flying by so fast its easy to miss an error. If you have the one click extracted open a command prompt and navigate to that folder. Then run the commands as follows: adb shell mv /data/local/12m /data/local/12m.bak ln -s /data /data/local/12m (POWER OFF DEVICE IT WILL REBOOT ON ITS OWN) adb shell rm /data/local/12m mv /data/local/12m.bak /data/local/12m mv /data/local.prop /data/local.prop.bak echo "ro.sys.atvc_allow_netmon_usb=0" > /data/local.prop echo "ro.sys.atvc_allow_netmon_ih=0" >> /data/local.prop echo "ro.sys.atvc_allow_res_core=0" >> /data/local.prop echo "ro.sys.atvc_allow_res_panic=0" >> /data/local.prop echo "ro.sys.atvc_allow_all_adb=1" >> /data/local.prop echo "ro.sys.atvc_allow_all_core=0" >> /data/local.prop echo "ro.sys.atvc_allow_efem=0" >> /data/local.prop echo "ro.sys.atvc_allow_bp_log=0" >> /data/local.prop echo "ro.sys.atvc_allow_ap_mot_log=0" >> /data/local.prop echo "ro.sys.atvc_allow_gki_log=0" >> /data/local.prop (POWER CYCLE) adb shell (# WILL BE LISTED) exit adb remount adb push busybox /system/xbin/busybox adb push su /system/xbin/su adb push Superuser.apk /system/app/Superuser.apk adb shell chmod 4755 /system/xbin/su adb shell chmod 755 /system/xbin/busybox Anything that is in () is not to be typed but informative. The steps above have worked for me on 2 X2's so far and a friends DROID3.
Pulling build.prop with ADB
Hi, Finally I can enter recovery mode after messing up with build.prop on Xperia Tablet S tablet is visible in ADB as C:\Users\Amiga\Desktop\adb>adb devices List of devices attached 0123456789ABCDEF recovery but rest of the commands doesn't work C:\Users\Amiga\Desktop\adb>adb shell * daemon not running. starting it now on port 5037 * * daemon started successfully * error: closed So I don't know how to pull out build.prop from Tablet
Amiga4ever123 said: Hi, Finally I can enter recovery mode after messing up with build.prop on Xperia Tablet S tablet is visible in ADB as C:\Users\Amiga\Desktop\adb>adb devices List of devices attached 0123456789ABCDEF recovery but rest of the commands doesn't work C:\Users\Amiga\Desktop\adb>adb shell * daemon not running. starting it now on port 5037 * * daemon started successfully * error: closed So I don't know how to pull out build.prop from Tablet Click to expand... Click to collapse The reason you are getting the "error: closed" message is because the version of System Recovery installed on your tablet inhibits ADB from accessing the tablet's file system. You are not going to be able to pull or push the build.prop file.
Ok I can't use ADb so how can I replace faulty build.prop file or make recovery? Any ZIP file that I can put on SD card?
Amiga4ever123 said: Ok I can't use ADb so how can I replace faulty build.prop file or make recovery? Any ZIP file that I can put on SD card? Click to expand... Click to collapse You can try copying an OTA update file to an SD card and using System Recovery to install it, but I do not believe doing that will work. I believe you have bricked your tablet to the point where you have to send your tablet to Sony for repair.
Cat McGowan said: You can try copying an OTA update file to an SD card and using System Recovery to install it, but I do not believe doing that will work. I believe you have bricked your tablet to the point where you have to send your tablet to Sony for repair. Click to expand... Click to collapse So its very easy to brick this amazing sony device
Cat McGowan said: The reason you are getting the "error: closed" message is because the version of System Recovery installed on your tablet inhibits ADB from accessing the tablet's file system. You are not going to be able to pull or push the build.prop file. Click to expand... Click to collapse Hi cat tried to PM you but can?t do it... Can you teach me how to copy/restore (pull and or push) the original build.prop in my cell (now bricked) i had the original file (buil.prop) inside it... i am learning about adb commands. thanksss. The main problem I have: An issue with ADB VCOM drivers (in windows) (tried in a couple of PCS, the device manager "see" the vcom preloader only a little moment (when connect the cell with usb cable) and then dissapear... then with command adb devices: no devices found... can you help me?
federimau said: Hi cat tried to PM you but can?t do it... Can you teach me how to copy/restore (pull and or push) the original build.prop in my cell (now bricked) i had the original file (buil.prop) inside it... i am learning about adb commands. thanksss. The main problem I have: An issue with ADB VCOM drivers (in windows) (tried in a couple of PCS, the device manager "see" the vcom preloader only a little moment (when connect the cell with usb cable) and then dissapear... then with command adb devices: no devices found... can you help me? Click to expand... Click to collapse The reason ADB is reporting no devices are found may be because (1) your device is bricked, which probably means you are not going to be able to pull/push files from/to your device, (2) you do not have ADB drivers for your device properly installed on your PC, and/or (3) you do not have USB debugging enabled in your tablet's Developer options settings. It's good you are learning how to use ADB and there are plenty of ADB tutorials to be found via Google, etc.; e.g., HERE. Here is what you specifically ask for. Pulling the build.prop file from your tablet to your PC is easy, just use these commands. Code: adb wait-for-device adb pull /system/build.prop adb kill-server Pushing the build.prop file from your PC to your tablet is more complicated. (1) Your tablet must have root access. If it doesn't, attempts at pushing the file to your tablet's /system directory will fail. (2) Along with having root access, you must have SuperSU or Superuser, and Busybox installed on the tablet. (3) You have to temporarily set your tablet's /system directory's properties from RO to RW, which must be done quickly because your tablet's OS monitors the /system directory's properties and will reboot the tablet if it detects the directory's properties have been changed from RO. (4) To issue the ADB commands as quickly as possible, the commands must be put into a DOS batch command script file. For example, create and run a batch file named doit.bat containing the following commands. Code: adb wait-for-device adb push build.prop /build.prop adb shell "su -c 'stop ric'" adb shell "su -c 'busybox pkill -f /sbin/ric'" adb shell "su -c 'mount -ro remount,rw /'" adb shell "su -c 'chmod 0440 /sbin/ric'" adb shell "su -c 'stop ric'" adb shell "su -c 'busybox pkill -f /sbin/ric'" adb shell "su -c 'mount -ro remount,rw /system'" adb shell "su -c 'busybox cp -af /build.prop /system/build.prop'" adb shell "su -c 'chmod 0744 /system/build.prop'" adb shell "su -c 'rm /build.prop'" adb shell "exit" adb kill-server Good luck.
Cat McGowan said: The reason ADB is reporting no devices are found may be because (1) your device is bricked, which probably means you are not going to be able to pull/push files from/to your device, (2) you do not have ADB drivers for your device properly installed on your PC, and/or (3) you do not have USB debugging enabled in your tablet's Developer options settings. It's good you are learning how to use ADB and there are plenty of ADB tutorials to be found via Google, etc.; e.g., HERE. Here is what you specifically ask for. Pulling the build.prop file from your tablet to your PC is easy, just use these commands. Code: adb wait-for-device adb pull /system/build.prop adb kill-server Pushing the build.prop file from your PC to your tablet is more complicated. (1) Your tablet must have root access. If it doesn't, attempts at pushing the file to your tablet's /system directory will fail. (2) Along with having root access, you must have SuperSU or Superuser, and Busybox installed on the tablet. (3) You have to temporarily set your tablet's /system directory's properties from RO to RW, which must be done quickly because your tablet's OS monitors the /system directory's properties and will reboot the tablet if it detects the directory's properties have been changed from RO. (4) To issue the ADB commands as quickly as possible, the commands must be put into a DOS batch command script file. For example, create and run a batch file named doit.bat containing the following commands. Code: adb wait-for-device adb push build.prop /build.prop adb shell "su -c 'stop ric'" adb shell "su -c 'busybox pkill -f /sbin/ric'" adb shell "su -c 'mount -ro remount,rw /'" adb shell "su -c 'chmod 0440 /sbin/ric'" adb shell "su -c 'stop ric'" adb shell "su -c 'busybox pkill -f /sbin/ric'" adb shell "su -c 'mount -ro remount,rw /system'" adb shell "su -c 'busybox cp -af /build.prop /system/build.prop'" adb shell "su -c 'chmod 0744 /system/build.prop'" adb shell "su -c 'rm /build.prop'" adb shell "exit" adb kill-server Good luck. Click to expand... Click to collapse Wowww Cat, you are the one!! Thanks in Advance The main problem I have: An issue with device recognition in windows PC... driver ADB VCOM MTK 6592 (tried in different PCS windows Xp and 8) (the device manager "see" the vcom preloader but only a little moment (in the first instant when connect the cell (cell off) with usb cable) and then dissapear (disconnect) the vcom preloader... I think If I can reach the way to get this connection running ok I can progress with this... will fight hard... When I type the command adb devices, result: no devices found... Tried to upgrade the vcom drivers (when i can catch it in the active state in device manager)... nothing Tried to "on" the phone... nothing Tried to flash a new ROM from Recovery (MIUI or Feelingme 078)... ERROR installation aborted I can see this effect (with usbview): the usb is recognized in the PC (but just for a little moment at the instant when plug it), then disconnect... I need to recover the original build.prop.bak from coolpad memory, rename it to build.prop and send it to coolpad again... I think i can flash (from recovery) an original build. prop (packed as update.zip) doing the wipes and apply update from sdcard)... anyone can assist me on this? This new 9976A item comes to me with 048 version, custom buid version 265 and rooted from factory... Anyone can please help me?
Cat McGowan said: The reason ADB is reporting no devices are found may be because (1) your device is bricked, which probably means you are not going to be able to pull/push files from/to your device, (2) you do not have ADB drivers for your device properly installed on your PC, and/or (3) you do not have USB debugging enabled in your tablet's Developer options settings. It's good you are learning how to use ADB and there are plenty of ADB tutorials to be found via Google, etc.; e.g., HERE. Here is what you specifically ask for. Pulling the build.prop file from your tablet to your PC is easy, just use these commands. Code: adb wait-for-device adb pull /system/build.prop adb kill-server Pushing the build.prop file from your PC to your tablet is more complicated. (1) Your tablet must have root access. If it doesn't, attempts at pushing the file to your tablet's /system directory will fail. (2) Along with having root access, you must have SuperSU or Superuser, and Busybox installed on the tablet. (3) You have to temporarily set your tablet's /system directory's properties from RO to RW, which must be done quickly because your tablet's OS monitors the /system directory's properties and will reboot the tablet if it detects the directory's properties have been changed from RO. (4) To issue the ADB commands as quickly as possible, the commands must be put into a DOS batch command script file. For example, create and run a batch file named doit.bat containing the following commands. Code: adb wait-for-device adb push build.prop /build.prop adb shell "su -c 'stop ric'" adb shell "su -c 'busybox pkill -f /sbin/ric'" adb shell "su -c 'mount -ro remount,rw /'" adb shell "su -c 'chmod 0440 /sbin/ric'" adb shell "su -c 'stop ric'" adb shell "su -c 'busybox pkill -f /sbin/ric'" adb shell "su -c 'mount -ro remount,rw /system'" adb shell "su -c 'busybox cp -af /build.prop /system/build.prop'" adb shell "su -c 'chmod 0744 /system/build.prop'" adb shell "su -c 'rm /build.prop'" adb shell "exit" adb kill-server Good luck. Click to expand... Click to collapse Cat i will need to pull the backup file... then the code i need is... (please monitor it for me) adb wait-for-device adb pull /system/build.prop.bak adb kill-server and... when you push the correct and original file adb wait-for-device adb push build.prop /build.prop is it ok? or the path is this? adb push build.prop /system/build.prop (if there are a build.prop in the device this will overwrite it?
federimau said: Cat i will need to pull the backup file... then the code i need is... (please monitor it for me) adb wait-for-device adb pull /system/build.prop.bak adb kill-server and... when you push the correct and original file adb wait-for-device adb push build.prop /build.prop is it ok? or the path is this? adb push build.prop /system/build.prop (if there are a build.prop in the device this will overwrite it? Click to expand... Click to collapse adb push build.prop /system/build.prop
Cat McGowan said: adb push build.prop /system/build.prop Click to expand... Click to collapse Thanks cat, as i say, the main problem in this case is: i have a short window of time when the windows PC see the driver in the device manager... then disconnects... do you have any idea what can i do to establish this connection betweeen the android device and the computer without interruption? ---------- Post added at 05:22 PM ---------- Previous post was at 05:12 PM ---------- Cat McGowan said: adb push build.prop /system/build.prop Click to expand... Click to collapse cat, i´m doing 2 bat files (edited with notepad, is this correct?) one file: pull.bat with code adb wait-for-device adb pull /system/build.prop.bak adb kill-server another file: push.bat with code adb wait-for-device adb push build.prop /system/build.prop adb shell "su -c 'stop ric'" adb shell "su -c 'busybox pkill -f /sbin/ric'" adb shell "su -c 'mount -ro remount,rw /'" adb shell "su -c 'chmod 0440 /sbin/ric'" adb shell "su -c 'stop ric'" adb shell "su -c 'busybox pkill -f /sbin/ric'" adb shell "su -c 'mount -ro remount,rw /system'" adb shell "su -c 'busybox cp -af /build.prop /system/build.prop'" adb shell "su -c 'chmod 0744 /system/build.prop'" adb shell "su -c 'rm /build.prop'" adb shell "exit" adb kill-server what do you think? ---------- Post added at 05:51 PM ---------- Previous post was at 05:22 PM ---------- federimau said: Thanks cat, as i say, the main problem in this case is: i have a short window of time when the windows PC see the driver in the device manager... then disconnects... do you have any idea what can i do to establish this connection betweeen the android device and the computer without interruption? ---------- Post added at 05:22 PM ---------- Previous post was at 05:12 PM ---------- cat, i´m doing 2 bat files (edited with notepad, is this correct?) one file: pull.bat with code adb wait-for-device adb pull /system/build.prop.bak adb kill-server another file: push.bat with code adb wait-for-device adb push build.prop /system/build.prop adb shell "su -c 'stop ric'" adb shell "su -c 'busybox pkill -f /sbin/ric'" adb shell "su -c 'mount -ro remount,rw /'" adb shell "su -c 'chmod 0440 /sbin/ric'" adb shell "su -c 'stop ric'" adb shell "su -c 'busybox pkill -f /sbin/ric'" adb shell "su -c 'mount -ro remount,rw /system'" adb shell "su -c 'busybox cp -af /build.prop /system/build.prop'" adb shell "su -c 'chmod 0744 /system/build.prop'" adb shell "su -c 'rm /build.prop'" adb shell "exit" adb kill-server what do you think? Click to expand... Click to collapse I think need to remove the first line? adb wait-for-device
federimau said: Thanks cat, as i say, the main problem in this case is: i have a short window of time when the windows PC see the driver in the device manager... then disconnects... do you have any idea what can i do to establish this connection betweeen the android device and the computer without interruption? Click to expand... Click to collapse You need to solve that problem before you can do anything else. Find an xda-developers forum that deals with your device and look there for fixes for your device's drivers. I am confident I can help you with Sony tablet drivers, but not your device's drivers. I don't even know the model of your device. Create and use the following CheckDriver.bat file to help you troubleshoot the drivers. The script simply opens a DOS command window, starts the adb server, then lists the devices the adb server finds. The DOS command window will stay open until you press any key. If the script hangs, press ctrl+c to abort the script and close the DOS command window, then open another DOS command window and issue the "adb kill-server" command to stop the adb server. Code: @echo off echo Starting ADB server and waiting for device. echo. adb wait-for-device adb devices pause adb kill-server federimau said: cat, i´m doing 2 bat files (edited with notepad, is this correct?) one file: pull.bat with code adb wait-for-device adb pull /system/build.prop.bak adb kill-server another file: push.bat with code adb wait-for-device adb push build.prop /system/build.prop adb shell "su -c 'stop ric'" adb shell "su -c 'busybox pkill -f /sbin/ric'" adb shell "su -c 'mount -ro remount,rw /'" adb shell "su -c 'chmod 0440 /sbin/ric'" adb shell "su -c 'stop ric'" adb shell "su -c 'busybox pkill -f /sbin/ric'" adb shell "su -c 'mount -ro remount,rw /system'" adb shell "su -c 'busybox cp -af /build.prop /system/build.prop'" adb shell "su -c 'chmod 0744 /system/build.prop'" adb shell "su -c 'rm /build.prop'" adb shell "exit" adb kill-server what do you think? Click to expand... Click to collapse Looks okay. Just keep in mind that the scripts are based on what is required for Sony tablets. Your device may require something a little different. federimau said: I think need to remove the first line? adb wait-for-device Click to expand... Click to collapse No. The "adb wait-for-device" command is what starts the adb server and causes the script to wait until the adb server detects a device before the next command in the script is issued. Similar to the CheckDevice.bat file, you can insert the "@echo off" command at the beginning of your .bat files and the "pause" command just before the "adb kill-server" to cause the DOS command window stay open so you can see what is going on and the DOS command window will stay open until you press any key. Again, if the script hangs, press ctrl+c to abort the script and close the DOS command window, then open another DOS command window and issue the "adb kill-server" command to stop the adb server.
Cat McGowan said: You need to solve that problem before you can do anything else. Find an xda-developers forum that deals with your device and look there for fixes for your device's drivers. I am confident I can help you with Sony tablet drivers, but not your device's drivers. I don't even know the model of your device. Create and use the following CheckDriver.bat file to help you troubleshoot the drivers. The script simply opens a DOS command window, starts the adb server, then lists the devices the adb server finds. The DOS command window will stay open until you press any key. If the script hangs, press ctrl+c to abort the script and close the DOS command window, then open another DOS command window and issue the "adb kill-server" command to stop the adb server. Code: @echo off echo Starting ADB server and waiting for device. echo. adb wait-for-device adb devices pause adb kill-server Looks okay. Just keep in mind that the scripts are based on what is required for Sony tablets. Your device may require something a little different. No. The "adb wait-for-device" command is what starts the adb server and causes the script to wait until the adb server detects a device before the next command in the script is issued. Similar to the CheckDevice.bat file, you can insert the "@echo off" command at the beginning of your .bat files and the "pause" command just before the "adb kill-server" to cause the DOS command window stay open so you can see what is going on and the DOS command window will stay open until you press any key. Again, if the script hangs, press ctrl+c to abort the script and close the DOS command window, then open another DOS command window and issue the "adb kill-server" command to stop the adb server. Click to expand... Click to collapse I am working with all of you advices... i owe you a drink (if you agree!!!) Thanks
Cat McGowan said: You need to solve that problem before you can do anything else. Find an xda-developers forum that deals with your device and look there for fixes for your device's drivers. I am confident I can help you with Sony tablet drivers, but not your device's drivers. I don't even know the model of your device. Create and use the following CheckDriver.bat file to help you troubleshoot the drivers. The script simply opens a DOS command window, starts the adb server, then lists the devices the adb server finds. The DOS command window will stay open until you press any key. If the script hangs, press ctrl+c to abort the script and close the DOS command window, then open another DOS command window and issue the "adb kill-server" command to stop the adb server. Code: @echo off echo Starting ADB server and waiting for device. echo. adb wait-for-device adb devices pause adb kill-server Looks okay. Just keep in mind that the scripts are based on what is required for Sony tablets. Your device may require something a little different. No. The "adb wait-for-device" command is what starts the adb server and causes the script to wait until the adb server detects a device before the next command in the script is issued. Similar to the CheckDevice.bat file, you can insert the "@echo off" command at the beginning of your .bat files and the "pause" command just before the "adb kill-server" to cause the DOS command window stay open so you can see what is going on and the DOS command window will stay open until you press any key. Again, if the script hangs, press ctrl+c to abort the script and close the DOS command window, then open another DOS command window and issue the "adb kill-server" command to stop the adb server. Click to expand... Click to collapse Cat, i can not establish a stable and in-time connection between cell and PC... type adb wait-for-device and never "see" the cell i have the drivers upgraded with usbview software i see the PC "see" the cell a short amount of time, then disconnects... any advice??
federimau said: Cat, i can not establish a stable and in-time connection between cell and PC... type adb wait-for-device and never "see" the cell i have the drivers upgraded with usbview software i see the PC "see" the cell a short amount of time, then disconnects... any advice?? Click to expand... Click to collapse Sounds to me your device simply is not responding to the adb server's attempt to connect. Again, my advice is for you to find an xda-developers forum that deals specifically with your device and look there for fixes for your device.
@Cat McGowan Thank you for the info, but it's not working on Recovery mode! I try to backup and restore the build.prop file on cmd in recovery & in bootloop case. working: adb wait-for-device adb pull /system/build.prop.bak or adb pull /system/build.prop adb kill-server not working push to the system: (even the cmd showing the opposite) adb wait-for-device adb push build.prop /system/build.prop adb kill-server I'm tring to resotre from PC or SD card... (after changing the permission to system folder (instead only build.prop file) to 00644 the device keep get to Recovery mode! (with root browser app) only flashing again the rom fix it.) I got an error too: - exec '/system/bin/sh' failed: Permission denied (13) - by the way what Should to be on? SuperSU or Superuser (ADB shell allow ?) Developer Mode (Enable ADB ) +USB Debugging on i'm worng what else? I want to add some info: I know the best way to edit this file only by : Notepad++ or EditPlus editor to preserve UNIX encoding or Turbo Editor ( File Editor ) app. read here: http://forum.xda-developers.com/showpost.php?p=54970011&postcount=171 http://forum.xda-developers.com/showpost.php?p=55094822&postcount=203 and great script from user. http://forum.xda-developers.com/showpost.php?p=55113422&postcount=208 will this work too on recovery or bootloops mode? backup: adb shell su mount -o remount,rw /system cp /system/build.prop /system/build.prop.bak mount -o ro,remount /system/ /system ---- restore: adb shell su mount -o remount,rw /system cp system/build.prop system/build.prop.bootloop cp system/build.prop.bak system/build.prop chmod 00644 system/build.prop reboot
[Q] P7500 3G keep rebooting even with factory reset
Hi all, Here's my case, The tab keep rebooting itself (galaxy tab - samsung logo - startup page). On the startup page it stil able to run it around 6/7 seconds and freeze then the same thing happen again. I tried wipe all data/factory reset and wipe cache in recovery mode,but it still happen. I wonder by factory reset all data would be deleted but still i able to view the old files from "get zip from sd card" option. Tried Odin with usable ROM last time. Still the same. In Mounts and Storage, there's no mount usb options for me. So cant boot from usb. Please advice. Thanks a lot. Too many in my head now. Eric
ericantona7 said: Hi all, Here's my case, The tab keep rebooting itself (galaxy tab - samsung logo - startup page). On the startup page it stil able to run it around 6/7 seconds and freeze then the same thing happen again. I tried wipe all data/factory reset and wipe cache in recovery mode,but it still happen. I wonder by factory reset all data would be deleted but still i able to view the old files from "get zip from sd card" option. Tried Odin with usable ROM last time. Still the same. In Mounts and Storage, there's no mount usb options for me. So cant boot from usb. Please advice. Thanks a lot. Too many in my head now. Eric Click to expand... Click to collapse think this called a boot loop. and i found this... which i do not familiar with this. ------------------- Chapter 3 Using ADB as solution ADB can be used to access the phone while booting, be aware that some bootloops make it unable to use ADB since they do not go further then the manufacturer logo. (In new CWM versions it’s possible to use adb) The only tricky part about using ADB with bootloops is that you have to do it on the right time, this is different from every device, but normally it’s after the manufacturer logo that the partitions get mounted. The easiest way to enter your phone in this part is using a batch script that monitors the state of your device and connects directly when possible. I use this script for example, called ondemand.bat (requires adb.exe and the 2 dlls) @ECHO off cd /d %~dp0 echo. echo Waiting for device… adb wait-for-device echo. adb -d shell stop adb push mycwmfix.zip /sdcard/mycwmfix.zip adb reboot recovery 1 2 3 4 5 6 7 8 9 @ECHO off cd /d %~dp0 echo. echo Waiting for device… adb wait-for-device echo. adb -d shell stop adb push mycwmfix.zip /sdcard/mycwmfix.zip adb reboot recovery Linux Version (ondemand.sh): #!/system/bin/sh echo " " echo "Wating for device..." ./adb wait-for-device echo " " ./adb -d shell stop ./adb push mycwmfix.zip /sdcard/mycwmfix.zip ./adb reboot recovery 1 2 3 4 5 6 7 8 #!/system/bin/sh echo " " echo "Wating for device..." ./adb wait-for-device echo " " ./adb -d shell stop ./adb push mycwmfix.zip /sdcard/mycwmfix.zip ./adb reboot recovery This script will wait for the device to become ready, when it’s ready it freeze the device, so the script has more time to push the file (instead of keep rebooting). Then it will push the specified cwmfix zip to your sdcard, and after that it will reboot in recovery so you can install the cwm fix you made. You can also make an batch script that pushes the files automatically to your phone, here is an example: @ECHO off cd /d %~dp0 echo. echo Waiting for device... adb wait-for-device echo. adb -d shell stop adb -d shell su -c "mount -o remount rw /system" adb push framework-res.apk /system/framework/framework-res.apk adb -d shell chmod 644 /system/framework/framework-res.apk adb push SystemUI.apk /system/app/SystemUI.apk adb -d shell chmod 644 /system/app/SystemUI.apk adb reboot 1 2 3 4 5 6 7 8 9 10 11 12 13 @ECHO off cd /d %~dp0 echo. echo Waiting for device... adb wait-for-device echo. adb -d shell stop adb -d shell su -c "mount -o remount rw /system" adb push framework-res.apk /system/framework/framework-res.apk adb -d shell chmod 644 /system/framework/framework-res.apk adb push SystemUI.apk /system/app/SystemUI.apk adb -d shell chmod 644 /system/app/SystemUI.apk adb reboot Linux version: #!/system/bin/sh echo " " echo "Waiting for device..." ./adb wait-for-device echo " " ./adb -d shell stop ./adb -d shell su -c "mount -o remount rw /system" ./adb push framework-res.apk /system/framework/framework-res.apk ./adb -d shell chmod 644 /system/framework/framework-res.apk ./adb push SystemUI.apk /system/app/SystemUI.apk ./adb -d shell chmod 644 /system/app/SystemUI.apk ./adb reboot 1 2 3 4 5 6 7 8 9 10 11 12 #!/system/bin/sh echo " " echo "Waiting for device..." ./adb wait-for-device echo " " ./adb -d shell stop ./adb -d shell su -c "mount -o remount rw /system" ./adb push framework-res.apk /system/framework/framework-res.apk ./adb -d shell chmod 644 /system/framework/framework-res.apk ./adb push SystemUI.apk /system/app/SystemUI.apk ./adb -d shell chmod 644 /system/app/SystemUI.apk ./adb reboot This script will wait for the device to become ready, when it’s ready it freeze the device, so the script has more time to push the file (instead of keep rebooting). Then it will push framework-.apk and SystemUI.apk to the directory it belongs to, after that it changes the permissions of the files to RW-R-R (644) and then it will reboot. Please note that on some devices the command “su -c” cannot be used after using the “stop” command, it gives an error then (Segmentation Fault). What you can do to prevent this is adding “adb remount” just under the “adb wait-for-device” line, and remove the “adb -d shell su -c “mount -o remount rw /system” line. Save the script and run it again. You are probably able to fix your bootloop with this guide, in some rare cases some other partitions could be damaged, then I advice you to install the stock rom (which is no .zip in most cases) Once you master the fixing of bootloops you can fix your phone independently ! ------------------------------------- anyone know how? where do i need to put the script file to? thanks.
ADB push alternative from Android device itself (non-rooted)
I have a non-rooted Android device with stock ROM 4.4.2 and I have the following test shell script: Code: adb push test.sh /data/local/tmp adb shell "cd /data/local/tmp; chmod 755 test.sh" adb.exe shell "sh /data/local/tmp/test.sh > /dev/null 2>&1 &" If I run this over ADB from PC to my device, it simply works. Now convert this to: Code: cp test.sh /data/local/tmp cd /data/local/tmp; chmod 755 test.sh /system/bin/sh /data/local/tmp/test.sh > /dev/null 2>&1 &" and it doesn't work. It says permission denied on /data/local/tmp. Is there any other EXT4 place on a non-rooted device that I can do this? Well, I cd to /data/local/tmp and even submitting a 'ls' command inside Terminal Emulator doesn't work, it says permission denied, but when doing it from PC to Android using ADB it's fine. Is there any workaround for this? I want to be able to do this on the device itself. Thanks
idoit said: I have a non-rooted Android device with stock ROM 4.4.2 and I have the following test shell script: Code: adb push test.sh /data/local/tmp adb shell "cd /data/local/tmp; chmod 755 test.sh" adb.exe shell "sh /data/local/tmp/test.sh > /dev/null 2>&1 &" If I run this over ADB from PC to my device, it simply works. Now convert this to: Code: cp test.sh /data/local/tmp cd /data/local/tmp; chmod 755 test.sh /system/bin/sh /data/local/tmp/test.sh > /dev/null 2>&1 &" and it doesn't work. It says permission denied on /data/local/tmp. Is there any other EXT4 place on a non-rooted device that I can do this? Well, I cd to /data/local/tmp and even submitting a 'ls' command inside Terminal Emulator doesn't work, it says permission denied, but when doing it from PC to Android using ADB it's fine. Is there any workaround for this? I want to be able to do this on the device itself. Thanks Click to expand... Click to collapse No there isnt, not if you try using /data partition. ADB can read this partition (and that too was added around android kitkat itself for purpose of adb backup etc). So ADB can read this partition, but terminal emulator and such cannot. Assuming that you have a great reason to simply not copy the sh file to user-usable internal memory, /system partition is the one place where you can copy things without actually having root (and even access them with terminal emulator, but not manipulate them), and this isn't that simple either. Rather, the method will be device dependent. For instance, if you have a phone like Nexus phones, simply download stock firmware, open/extract it depending on what format it is (img or tar), add your sh file and repack the firmware, then flash it into the phone. The firmware should be same as your current installed so your applications dont mess up. But this method is not only long (and messy if your device has integrity checks on firmware files), but also not possible on some phones (as far as I know). You can also try copying the sh file with adb to /data/data/com.android.terminal. Then you should be able to access this with terminal emulator (since an app has permissions inside its own data folder). However I have not tested this method and I am not sure it will work. Besides this, every app (including terminal emulator) runs in a sandbox and does not have access to anything except /system (read-only access), emulated user-storage and its own data inside /data/data/. So in phone itself, you cannot read the file unless you copy it to /system or user-memory. And this finally implies that except above two methods, there is no other way to copy file to some other place except user-memory and be able to read it using some app inside phone itself without rooting.
Thanks for your comprehensive reply. I resolved the problem. Yes, it's right, I can simply run the shell script without even moving it to /data/local/tmp... so now I can conveniently running it directly from my phone without having to turn a computer on and do it over ADB.
thankx
Installing SuperSU to BlueStacks
Hey everyone, I am a new member and I haven't ever developed anything for Android, even though I am a CS major, thus I am not very familiar with kernels , bootloaders and recoveries. Anyway, I decided that I wanted BlueStacks on my computer. I have been going through a variety of Android emulators and this is the one interface I like the most. I have downloaded the pre-rooted version of BlueStacks 2.0.0 (from here: http://forum.xda-developers.com/wiki/BlueStacks_App_Player) and I have downloaded some apps to check if it was rooted, in fact. And yes, it is, but it doesn't have SuperSU installed. I have then tried to install SuperSU. But once I click on SuperSU icon I get an error message "There is no binary SU installed and SuperSU cannot install it .... " and it suggests to install SuperSU manually. Since then I have been reading a little about how Android boots and I have tried some apps like RecoveryReboot, QuickBoot, etc. None of them work. I have tried to find ways to see if the BootLoader is locked or to discover if the system has or doesn't have a recovery but no luck. I believe there's no recovery mode available. Instead of going through the kernel and bootloader (which I am not familiar with and would take me ages to figure out) I decided to look for alternative ways. I have found this apk: http://forum.xda-developers.com/showthread.php?t=2250555 which looked promising because it would allow me to install SuperSU without going through recovery mode. But, unfortunately, after selecting the zip file with SuperSU, I receive an error saying that this package is not a flashable zip. Anyway, instead of keep looking, I was wondering if anyone has an idea of a way to install SuperSU in this version of BlueStacks. I know that some previous versions have SuperSU installed by default, but I like BlueStacks 2 interface and some functionalities better. Thank you!
How to install SuperSU and root BlueStacks 2.0.x.x manually I'm a total noob when it comes to android but somehow I've managed to root latest 2.0.8.5638 with trial and error method Here is what I've done. I'm not sure if its the right way tho 1. Download SuperSU 2.46 from their site or download this: https://dl.dropboxusercontent.com/s/v5kje7gsb9q3pp8/tmp.7z?dl=1 I've only added necessary files in the zip. Open cmd and push this files to BlueStacks. If you've downloaded complete supersu package then you'll need "libsupol.so, su, supolicy" from "x86" folder and "Superuser.apk" from "common" folder. You'll also need adb installed and added to your environment variable path or you can use "C:\Program Files (x86)\BlueStacks\HD-Adb.exe" instead of adb... Code: adb push xbin\su /data/local/tmp adb push xbin\supolicy /data/local/tmp adb push lib\libsupol.so /data/local/tmp adb push app\Superuser.apk /data/local/tmp 2. Run adb shell in cmd Code: adb shell And type this in shell, it will grant you root permission. They left this and also busybox in latest versions. Code: /system/xbin/bstk/su 3. Remount with rw rights. Not sure about first and last though, /dev/sda1 /system is necessary. Code: mount -o rw,remount /dev/block/sdb1 /data mount -o rw,remount /dev/sda1 /system mount -o rw,remount / / 4. cd to /data/local/tmp and give these permissions below to files. Code: cd /data/local/tmp chmod 0775 su chmod 0775 supolicy chmod 0664 libsupol.so chmod 0664 Superuser.apk 5. Move/copy this files. Code: cp su /system/xbin/su cp su /system/xbin/daemonsu cp supolicy /system/xbin/supolicy cp libsupol.so /system/lib/libsupol.so cp Superuser.apk /system/app/Superuser.apk 6. You have to edit init.sh file. You can do it with vi Code: busybox vi /system/etc/init.sh Scroll down to end of script. You'll see something like this. Code: init|"") do_init ;; esac change it to Code: init|"") do_init /system/xbin/daemonsu --auto-daemon & ;; esac then exit with ":wq!" or alternatively you can copy that file to bluestacks shared folder and edit it with your text editor then copy it back. Its easier this way. Code: cp /system/etc/init.sh /storage/sdcard/windows/BstSharedFolder/init.sh edit init.sh file in "C:\ProgramData\BlueStacks\UserData\SharedFolder" then copy it back to BlueStacks. Code: rm /system/etc/init.sh cp /storage/sdcard/windows/BstSharedFolder/init.sh /system/etc/init.sh P.S. if you use "cp -f" you may not need to write "rm" command, haven't tried it myself. Like I said, noob here Ok, now you should have root access. You may want to install apps like apex launcher, root explorer etc. Then you can uninstall BlueStacks' bloatware if you want. ::bluestacks things Code: rm /mnt/prebundledapps/com.google.android.apps.photos-1.apk rm /mnt/prebundledapps/downloads/BstFakeGps.apk rm /mnt/prebundledapps/downloads/MyBluestacks.apk rm /mnt/prebundledapps/downloads/bluestacksHome.apk rm /mnt/prebundledapps/downloads/bluestacksServices.apk rm /mnt/prebundledapps/downloads/newAppFinder.apk rm /mnt/prebundledapps/downloads/setupWizard.apk rm /data/downloads/AppGuidance.apk rm /data/downloads/AppSettings.apk rm /data/downloads/BstFakeGps.apk rm /data/downloads/MyBluestacks.apk rm /data/downloads/S2P.apk rm /data/downloads/bluestacksHome.apk rm /data/downloads/bluestacksServices.apk rm /data/downloads/newAppFinder.apk rm /data/downloads/setupWizard.apk 7. Remount with readonly again. Code: mount -o ro,remount /dev/sda1 /system mount -o ro,remount / / 8. Don't know what it does but I've seen it on some instructions Code: sync 9. Open a cmd with admin rights and kill BS2 completely then open it again. Code: taskkill /f /t /im "BlueStacks.exe" /im "HD-Agent.exe" /im "HD-Adb.exe" /im "HD-BlockDevice.exe" /im "HD-FrontEnd.exe" /im "HD-Network.exe" /im "HD-Service.exe" /im "HD-SharedFolder.exe" /im "HD-UpdaterService.exe" /im "HD-LogRotatorService.exe" 10. Open SuperSu app in BS2, it may want you to update su binaries. Update it with normal option and restart it. Use taskkill way to completely kill it again. 11. Run adb shell again. You may need to run "adb kill-server" command first. 12. Run "adb shell" command then type "su". SuperSu will want grant permission approval for shell. Give it and now you should have a rooted BS2