Related
For Those People Getting Error Installing Google Maps 3.1.0 on Hero ROM Here Is The Answer :
The Application Gets Downloaded But Says Application Signing Error, Actually Its Properly Signed, But For Some Reason, It Dosen't Install
Without Voice Search:
Steps:
1. Download This Apk
Updated Link:
Code:
http://android-latest-build-images.googlecode.com/files/GoogleMaps.apk
2. Go to Cmd : Start -> run -> cmd -> Enter
3. Cd to the folder where downloaded aplication is located
4. Type this & press Enter:
Code:
adb push GoogleMaps.apk /data/app_s
using adb push instead of adb install because it says certificate error...
5. Reboot or Else When Force Close / Wait Option Comes Press wait...
With Voice Search
Steps:
1. Download The .exe
(Packed with 7z)
Code:
http://android-latest-build-images.googlecode.com/files/Google%20Maps%20v3.1.1%20With%20Voice%20Search.exe
2. Run & Extract The Files Inside It Any Where
3. Run The .bat File
U r Done...
Thank you very much. That was irritating me.
[EDIT] Now 3.1.1 is out and I am getting same install error from market.
k let me check it out ll update it soon...
i updated to 3.1.1 using the market but i cant voice search.. how do u do it. i press settings nothing comes up.
thanks ,great idea,a 10 4 u
Thank you..Works great!
Works great.... thanks. i wonder can the youtube hHQ work the same way??? I anwer that yep....
http://forum.xda-developers.com/showthread.php?t=527768
Any way to do this on Terminal?
guitarfreak846 said:
Any way to do this on Terminal?
Click to expand...
Click to collapse
Terminal :
1. unzip the exe into an folder inside ur sdcard say /sdcard/maps
2. then go to terminal
3. Type this into terminal or make an text file insert these lines into it rename it to <any_name.sh> & put it into sdcard & run it (su then sh any_name.sh
Code:
su
cp /sdcard/maps/*.apk /data/app_s
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/maps/*.so /system/lib
I'm here give full guide for what I was learned from merrickville, codelover, and rocketero so all credits go to all of them either by direct guide and correction or by understanding their modified files. (is it OK codelover :good
To whom who don't know BlueStacks (as me before a week), it's emulated android system to works under windows system. for more info go to company page
A- REMOVE BLUESTACKS
Good tool from "Microsoft Fix it to install/uninstall Programs" thanx Ba7rani123
1- Run command (Win Key + R) -> "%programfiles%\BlueStacks\HD-Quit.exe" (WinX86) "%programfiles(x86)%\BlueStacks\HD-Quit.exe" (WinX64)
2- Open "task manager" by run command "taskmgr" -> "Processes" tab -> "HD-LogRotatorService.exe" -> right click -> "End Process Tree"
3- Open "programs and features" by run command "appwiz.cpl" -> uninstall "BlueStacks App Player" & "Notifications Center"
4- Delete all BS folders
"%userprofile%\AppData\Local\BlueStacksSetup"
"%programfiles%\BlueStacks" (WinX86), "%programfiles(x86)%\BlueStacks" (WinX64),
"%programdata%\BlueStacks"
"%programdata%\BlueStacksSetup"
Setup from Desktop
"%windir%\Installer" -> "View" -> "Details" -> right click on column header (i.e "Name", "Date Modified", "Type") -> "Authors" -> click over column header of "Authors" to sort files according authors -> search for "BlueStacks" and delete.
Note: "%ProgramData%\BlueStacks\Logs\Hypervisor.log" will persist to delete, we will delete it later after restart
5- Download RegScanner v1.95
Install -> open it -> Registry Scan Options (it will open automatic) -> select all keys in option Scan the following base key -> write on Find String "BlueStacks" -> wait till search finish -> select all and delete -> Resisted keys can be deleted manually by open in Regedit (F8)
I can't support this application because I have Windows 7 Manager, with perfect Registry Tools 1.1, it backup & delete all keys automatic
6- Repeat step (5) by searching for "Notification Center"
7- Reboot your devive now.
8- Now you can remove %ProgramData%\BlueStacks\Logs\Hypervisor.log
Click to expand...
Click to collapse
B- ROOTING BLUESTACKS
B-I- FIRST ROOTING METHOD (Ready made rooted /system)
Download rooted "Root.fs" and modified "initrd.img" for BlueStacks 0.7.7.813:
1- Download "BlueStacks-ThinInstaller_0.7.7.813.exe", "Root_Mod.rar" and "initrd_Mod.rar" from HERE
2- Setup BlueStacks 0.7.7.813 by file "BlueStacks-ThinInstaller_0.7.7.813.exe"
3- After setup finish installing, and BS open, close it (even before click "Got it") then run command (Win key + R) "%ProgramFiles%\BlueStacks\HD-Quit.exe" (WinX86), "%programfiles(x86)%\BlueStacks\HD-Quit.exe" (WinX64).
4- Extract "Root_Mod.rar" and "initrd.rar" into same folder "%programdata%\BlueStacks\Android" (P.S no need to make backup because it's already packed in zip file on "%programdata%\BlueStacksSetup\[xxxxxxxx].zip"
5- Open run command "%programfiles%\BlueStacks\HD-StartLauncher.exe" (WinX86), "%programfiles(x86)%\BlueStacks\HD-StartLauncher.exe" (WinX64)
Now your BlueStacks have root permission (Thanks CodeLover) and google apps (already supported).
OR
Download rocketero's rooted Root.fs & initrd.img from the 3rd post , thanks rocketero
Click to expand...
Click to collapse
B-II- SECOND ROOTING METHOD (Custom made rooted /system)
Rooting your "Root.fs" by your self, this method allow you root any versions of BlueStacks. it need to download "Portable Ubuntu Remix", [INFO: it's a portable Linux Ubuntu 10.4 LTS emulator that works under windows environment. for more information see PROJECT.
1- Download "Portable Ubuntu Remix" from HERE
2- Download "BlueStacks" from HERE
3- Run "Portable Ubuntu Remix" and change the path to "%programfiles%\" (WinX86) "%ProgramFiles(x86)%\" (WinX64)
4- Setup "BlueStacks" until it open -> close it.
5- Open run command (win key + R) "%ProgramFiles%\BlueStacks\HD-Quit.exe" (WinX86), "%programfiles(x86)%\BlueStacks\HD-Quit.exe" (WinX64).
6- Make RAR backup of your original "%programdata%\BlueStacks\Android\Data.sparsefs" in case of any errors may happen later.
7- Follow steps of F- MOD LATEST "SUPERUSER.APK", EXTRACTED "SU" BINARY, BUSYBOX FILES .
8- Follow steps of H- EDITING INITRD.IMG and place it in "%ProgramData%\BlueStacks\Android" (P.S: don't worry about original "initrd.img" because it is packed in zip file @ "%ProgramData%\BlueStacksSetup\[xxxxxxx].zip".
9- Open run command "%programfiles%\Portable_Ubuntu_V4_slim2\pubuntu.exe" (WinX86), "%ProgramFiles(x86)%\Portable_Ubuntu_V4_slim2\pubuntu.exe" (WinX64) and wait till it fully loaded (i.e top toolbar).
10- From the top toolbar select Applications -> Accessories -> Terminal.
11- Write the following commands (P.S: # means a note for you, it's not a command):
Code:
# Take a root permission
sudo su
# It will ask you for a root password: 123456
# Create a working folders
mkdir /b
mkdir /b/root
mkdir /b/system_sfs
mkdir /b/system_img
# Resize Root.fs to 500 MB
e2fsck -f -y "/media/cofs2/ProgramData/BlueStacks/Android/Root.fs"
resize2fs -f "/media/cofs2/ProgramData/BlueStacks/Android/Root.fs" 500M
# Mount root.fs to root folder
mount -o loop "/media/cofs2/ProgramData/BlueStacks/Android/Root.fs" /b/root
# Mount system.sfs to system_sfs folder
mount -o loop /b/root/android/system.sfs /b/system_sfs
# Extract system.img to /b folder
cp /b/system_sfs/system.img /b/root/android
# Resize system.img
e2fsck -f -y /b/root/android/system.img
resize2fs -f /b/root/android/system.img 480M
# Unmount system_sfs and delete it (make sure the command not unmount)
umount /b/system_sfs
rm /b/root/android/system.sfs
rmdir /b/system_sfs
# Mount system.img into system_img
mount -o loop /b/root/android/system.img /b/system_img
# Copy MOD "Superuser" & extracted "su" binary, busybox files (which you already did in step 7)
cp "/media/cofs2/pubuntu/Superuser.apk" /b/system_img/app
cp "/media/cofs2/pubuntu/su" /b/system_img/bin
cp "/media/cofs2/pubuntu/su" /b/system_img/xbin
cp "/media/cofs2/pubuntu/busybox" /b/system_img/xbin
chmod 6755 /b/system_img/bin/su
chmod 6755 /b/system_img/xbin/su
# Un mount system_img & delete folder
umount /b/system_img
rmdir /b/system_img
# Set Permission for system.img
chown 0:2000 /b/root/android/system.img
chmod 0644 /b/root/android/system.img
# Unmount root and save changes into root.fs
umount /b/root
rmdir /b/root
rmdir /b
12- Close Terminal and shut down Portable Ubuntu from system menu at top toolbar -> Shut Down
13- Open run command "%programfiles%\BlueStacks\HD-StartLauncher.exe" (WinX86), "%Programfiles(x86)%\BlueStacks\HD-StartLauncher.exe" (WinX64)
14- After BlueStacks run, download custom launcher (like Go Launcher HD for Pad, Apex).
15- Now your BlueStacks have root permission.
16- Make RAR backup of your "Root.fs" and "initrd.img".
Click to expand...
Click to collapse
C- BLUESTACKS INSTALLING TROUBLESHOOTS
1- If you have msgbox telling you of missing img, rerun the setup
2- If you the setup just start and finish very soon
See section A- REMOVE BLUESTACKS @ the top
Click to expand...
Click to collapse
D- ROOTING TROUBLESHOOTS
You have to reset BS files:
a) If you follow B-I- FIRST ROOTING METHOD:
1- Download "Root_MOD.rar", "initrd_MOD.rar" and "Data_Org.rar" from HERE
2- Extract them on "%programdata%\BlueStacks\Android"
b) If you follow B-II SECOND ROOTING METHOD:
1- If you already have previous root and made backup of your rooted "Root.fs" & edited "initrd.img" & stock "Data.sparsefs" -> just extract all back to "%programdata%\BlueStacks\Android"
2- If you don't have backup -> either extract them from "%programdata%\BlueStacksSetup\[xxxxxx].zip" and start from scrach, or follow above (a) steps of B-I- FIRST ROOTING METHOD.
Click to expand...
Click to collapse
E- BACKUP/RESTORE BLUESTACKS by Codelover via bat executable commands see HIS POST
F- MOD LATEST "SUPERUSER.APK", EXTRACTED "SU" BINARY, BUSYBOX FILES I got it from codelover's MOD superuser4BS.apk
1- Download last version of Superuser for x86 from HERE
2- Download 7-Zip & install it from HERE (if you didn't have it)
3- Download latest version of "busybox-i686" from HERE to "C:\pubuntu" (take attention it should be small letter) and rename the downloaded file into "busybox"
4- Extract "\system\bin\su" to "C:\pubuntu" we need it to copy it to "/system/bin" & "/system/xbin"
5- Extract "\system\app\Superuser.apk" to "C:\pubuntu"
6- Close 7-zip
7- Open "Superuser.apk" via "7-zip" -> extract "assets\sutools-x86" -> rename it into "sutools-armeabi" -> drag it back in 7-zip to replace existed "sutools-armeabi".
8- Make copy of "busybox" and rename this copy to "busybox-armeabi" -> drag it again in 7-zip to replace existed "busybox-armeabi"
8- Close 7-zip and now, you have latest files MOD Superuser,apk, extracted "su" binary and busybox files
Click to expand...
Click to collapse
G- COPY FILES TO /SYSTEM via ADB modified from codelover's commands (take a look on his POST)
You should have "su" with root permission.
[GOOD TOOL: "Add_Open_Command_Window_Here_as_Administrator.reg" HERE to allow you open command from any folder]
a) To replace old "superuser.apk" with new file
1- Download "CodeLover_SU.rar" (superuserX86-3.2RC3) from HERE -> extract it into "C:\pubuntu" OR use your own MOD file from step F- MOD LATEST "SUPERUSER.APK", EXTRACTED "SU" BINARY, BUSYBOX FILES
2- Run "Add_Open_Command_Window_Here_as_Administrator.reg" from "C:\pubuntu" folder
3- Write commands
Code:
adb connect 127.0.0.1:5555
adb -s 127.0.0.1:5555 shell su -c "rm /*uperuser.apk"
adb -s 127.0.0.1:5555 uninstall com.noshufou.android.su
adb -s 127.0.0.1:5555 install *uperuser.apk
Click to expand...
Click to collapse
b)Replace old "su" binary file with new file
1- Download "CodeLover_SU.rar" (suX86-3.2RC3) from HERE -> extract it into "C:\pubuntu" OR use your own Extracted file from step F- MOD LATEST "SUPERUSER.APK", EXTRACTED "SU" BINARY, BUSYBOX FILES
2- Run "Add_Open_Command_Window_Here_as_Administrator.reg" from "C:\pubuntu" folder
3- Write commands
Code:
adb connect 127.0.0.1:5555
adb -s 127.0.0.1:5555 push su.86 /sdcard/
adb -s 127.0.0.1:5555 shell su -c "cp /sdcard/su.86 /system/xbin/"
adb -s 127.0.0.1:5555 shell su -c "chown 0.0 /system/xbin/su.86"
adb -s 127.0.0.1:5555 shell su -c "chmod 6755 /system/xbin/su.86"
adb -s 127.0.0.1:5555 shell su -c "mv /system/xbin/su.86 /system/xbin/su"
adb -s 127.0.0.1:5555 shell su -c whoami # if you got "Root"
adb -s 127.0.0.1:5555 shell su -c "cp /system/xbin/su /system/bin/su"
Click to expand...
Click to collapse
c)Replace old "busybox" file with new file
1- Download latest version of "busybox-i686" from HERE to "C:\pubuntu" and rename the downloaded files into "busybox" OR use one you already download it in step F- MOD LATEST "SUPERUSER.APK", EXTRACTED "SU" BINARY, BUSYBOX FILES
2- Run "Add_Open_Command_Window_Here_as_Administrator.reg" from "C:\pubuntu" folder
3- Write commands
Code:
adb connect 127.0.0.1:5555
adb -s 127.0.0.1:5555 push busybox /sdcard/
adb -s 127.0.0.1:5555 shell su -c "cp /sdcard/busybox /system/xbin/busybox-i686"
adb -s 127.0.0.1:5555 shell su -c "chown 0.2000 /system/xbin/busybox-i686"
adb -s 127.0.0.1:5555 shell su -c "chmod 0755 /system/xbin/busybox-i686"
adb -s 127.0.0.1:5555 shell su -c "mv /system/xbin/busybox-i686 /system/xbin/busybox"
adb -s 127.0.0.1:5555 shell busybox
You should not have error
Click to expand...
Click to collapse
Click to expand...
Click to collapse
H- EDITING INITRD.IMG to mount /system for read & write, I got it from merrickville's initrd.img
1- Download 7-zip and install it
2- Download "NotePad++" from HERE and install it.
3- Copy "initrd.img" from "%programdata%\BlueStacks\Android\initrd.img" or extract it from "%programdata%\BlueStacksSetup\runtimedata_[xxxxxxx].zip" (where xxxxxx = ur BS version) to "C:\pubuntu".
4- Open 7-zip -> Tools -> Options -> Editor -> put the path of installed "NotePad++" ["%ProgramFiles%\Notepad++\notepad++.exe"]
5- Extract "initrd.img" via 7-zip -> open extracted file "initrd" via 7-zip -> right click "initrd" -> Edit
6- Search for:
Code:
[B]try_mount [COLOR="red"]ro[/COLOR] "$device /mnt || continue[/B]
(It should be after "for device in /dev/sr* /dev/sd.....")
and replaced with
[B]"try_mount [COLOR="red"]rw[/COLOR] $device /mnt || continue[/B]
7- Close it and save the file -> accept replacing of the file -> close 7-zip
8- Open "initrd.img" via 7-zip and replace "initrd"
9- Now you have your edited initrd.img -> copy back to "%programdata%\BlueStacks\Android"
Click to expand...
Click to collapse
If it helps you, give me thanks :good:
Looks preety awesome...
Will try it soon...
Sent from my GT-S7500 using xda premium
"E=mohazia;33618109]I'm here give full guide for what I was learned from mammadkhata and merrickville so all credits go to both of them.
To whom who don't know BlueStacks (as me before a week), it's emulated android system to works under windows system. for more info go to company page
You have 2 choices,
First Method:
:
Click to expand...
Click to collapse
I have a Root.fs rooted (& Initrd.img Edited) with system.img (/system partition) resized to 500MB that is working fine with BS07.7.813.
you can download it here: https://www.dropbox.com/s/rdf35z9cupl5xnb/Root-fs_and_Initrd-img-bs077813.rar
it's MD5(sum) is: FFA77658EF35AACDDA06B379CBF52CB8
it contains Root.fs and Initrd.img, this still can follow your method # 1 to root BS 077813.
A few notes:
- system partition resized to 500MB
- su version 3.2 x86-RC3-signed was added not only to /system/xbin but also to /system/bin as well as busybox to keep a fallback when updating the su binary.
- binary /system/bin/ls was symlinked to busybox instead of toolbox to get nice color file listings in a terminal
- superuser4BS.apk (moded by @codelover) was added to /system/app"
rocketero said:
Does your first method contain a Root.fs with /system resized to let's say 300MB or more?
I have a Root.fs rooted and with system.img resized to 500MB that is working fine with BS07.7.813.
you can download it here: https://www.dropbox.com/s/rdf35z9cupl5xnb/Root-fs_and_Initrd-img-bs077813.rar
it contains Root.fs and Initrd.img, this still can follow your method # 1 to root BS 077813.
A few notes:
- system partition resized to 500MB
- su version 3.2 x86 was added not only to /system/xbin but also to /system/bin as well as busybox to keep a fallback when updating the su binary.
- binary /system/bin/ls was symlinked to busybox instead of toolbox to get nice color file listings in a terminal
- superuser-3.1.3.apk was added to /system/app
Click to expand...
Click to collapse
Your link was added, thanx
but I'd like to ask, why u'll need system 500MB ???
mohazia said:
but I'd like to ask, why u'll need system 500MB ???
Click to expand...
Click to collapse
it's not exactly that you need 500M on /system partition, as the size will just increase as you add files to /system, if you don't add any files the partition will stay the size it was originally, it works as the sparcefs file sistem does, it will show only what you have added from the total. Let's say you have grown the /system parttition to 300MB, that's what it will show when you do a 'df -h /system' command.
rocketero said:
it's not exactly that you need 500M on /system partition, as the size will just increase as you add files to /system, if you don't add any files the partition will stay the size it was originally, it works as the sparcefs file sistem does, it will show only what you have added from the total. Let's say you have grown the /system parttition to 300MB, that's what it will show when you do a 'df -h /system' command.
Click to expand...
Click to collapse
aha, thanks.
The image u just share didn't had google account, right.
I had now data.fs and sdcard.fs, which I extracted from BS 0.7.2... and already integrated into my BS 0.7.7.813, the advantages of .fs that I can resize it very easy. Do u advice me to share it?
actually, rooting and make some customization, was attractive, now joy was solved, it's boring
I can't even play where's my water? on BS, is for me only or with all?
mohazia said:
aha, thanks.
The image u just share didn't had google account, right.
I had now data.fs and sdcard.fs, which I extracted from BS 0.7.2... and already integrated into my BS 0.7.7.813, the advantages of .fs that I can resize it very easy. Do u advice me to share it?
actually, rooting and make some customization, was attractive, now joy was solved, it's boring
I can't even play where's my water? on BS, is for me only or with all?
Click to expand...
Click to collapse
I do have a sdcard.fs of 8GB working with v0.7.7.813, but even that I have not much in it the size would be huge to share it which makes it almost impossible to upload to any file-sharing site like dropox or box.net. I saw in an old post a shared sdcard 2GB in size but that's the default size when installing BS older than 0.7.3.x I believe. The Data.fs it has been always 2GB in size.
The good thing from updating BS from older versions to the new ones is that it will carry out the old Data.fs and Sdcard.fs and it will incorporate them into Data.sparsefs and SDcard.sparcefs
About the apps/games that run in BS it's just trial an error, sometimes very disappointing that it doesn't run the one's preferred apps.
It says that "Blue stack player app download in progress" and says its "already installed", error. idk what happens
tichs said:
It says that "Blue stack player app download in progress" and says its "already installed", error. idk what happens
Click to expand...
Click to collapse
You'll get more responses if you post on the official BS thread here: http://forum.xda-developers.com/showthread.php?p=33701742#post33701742
Code:
11- Open Superuser -> Settings -> Automatic Response -> Allow
Now your BlueStacks have root permission and google apps.
you mean that now i don't need anymore google play store because the Google apps are integrated in my bluestacks market?
thanks
kianty99 said:
Code:
11- Open Superuser -> Settings -> Automatic Response -> Allow
Now your BlueStacks have root permission and google apps.
you mean that now i don't need anymore google play store because the Google apps are integrated in my bluestacks market?
thanks
Click to expand...
Click to collapse
no what I actually meant is that ur system now have google permission, you can now install google play and it will works.
OK, when I did this guide, I did not differentiate between apps that set on /system/app and /data/app.
I will attach google play now to installed as com.nosh*.apk, just download it and double click to install
Code:
I will attach google play now to installed as com.nosh*.apk, just download it and double click to install
excuse me... i have search for google play apk on first post but i don't found it... where is it?
thanks
kianty99 said:
Code:
I will attach google play now to installed as com.nosh*.apk, just download it and double click to install
excuse me... i have search for google play apk on first post but i don't found it... where is it?
thanks
Click to expand...
Click to collapse
I'm review now the method from scrash
i've installed the two apk you mentioned and say me an error:
Code:
apk installation failed: INSTALL_PARSE_FAILED_NO_CERTIFICATES
kianty99 said:
i've installed the two apk you mentioned and say me an error:
Code:
apk installation failed: INSTALL_PARSE_FAILED_NO_CERTIFICATES
Click to expand...
Click to collapse
OK, I just remove BS, for re-install it, to start from scrach, I will update soon
AMD Appzone its better than bluestacks? I read that they have some unique technology that uses the gpu to accelerate everything, is that available to normal blue stacks builds?
tichs said:
AMD Appzone its better than bluestacks? I read that they have some unique technology that uses the gpu to accelerate everything, is that available to normal blue stacks builds?
Click to expand...
Click to collapse
no, bs is a no gpu accelerator. Even youtube not work
Sent from my HTC Desire HD using xda premium
kianty99 said:
i've installed the two apk you mentioned and say me an error:
Code:
apk installation failed: INSTALL_PARSE_FAILED_NO_CERTIFICATES
Click to expand...
Click to collapse
1- Now delete ur root.fs & data.s* from %programdata%\bluestacks
2- Extract data.s* from the archeive @ %programdata%\bluestackssetup on %programdata%\bluestacks
3- Follow new guide (exactly) with excluding steps 1 and 3 (just skip and contiune in same sequance)
Sent from my HTC Desire HD using xda premium
mohazia said:
no, bs is a no gpu accelerator. Even youtube not work
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
so they are the same thing right just different name?
This is a work metod for root your not unlocked phone !
I find a solution after update to last new version
Download this : http://forum.xda-developers.com/showthread.php?t=2143437
After download and share fail with samba windows or mac sharing, you need to mount from file manage > remote storage
After fix permission go to adb folder and type :
"adb shell"
"cd /mnt/rfs0"
"./su"
"cd /"
"ln -s /mnt /storage"
Next step go to console and type :
adb kill-server
adb shell /storage/rfs0/pwn
Next : Install apk package from phone , Reboot Phone and now your phone is rooted!
Update from Play Market SuperSu and go.
Best regards,
m.
micron said:
This is a work metod for root your not unlocked phone !
I find a solution after update to last new version
Download this : http://forum.xda-developers.com/showthread.php?t=2143437
After download and share fail with samba windows or mac sharing, you need to mount from file manage > remote storage
After fix permission go to adb folder and type :
"adb shell"
"cd /mnt/rfs0"
"./su"
"cd /"
"ln -s /mnt /storage"
Next step go to console and type :
adb kill-server
adb shell /storage/rfs0/pwn
Next : Install apk package from phone , Reboot Phone and now your phone is rooted!
Update from Play Market SuperSu and go.
Best regards,
m.
Click to expand...
Click to collapse
lol if i saw this earlier i might not have unlocked my boot loader today. =) hope someone can try this
I gave this a try earlier today. I scoured through the forum to find that the new Ubuntu doesn't install ADB drivers by default, so you need to do this manually.
Anyway, I attempted to do it and got all the way to ./su. It then prompted me with the message "./su cannot execute - Permission denied". Obviously from there I can't link /mnt to /storage and I can't run pwn because it looks for the /storage folder.
If you have any suggestions how to get ./su running, let me know.
rykin said:
I gave this a try earlier today. I scoured through the forum to find that the new Ubuntu doesn't install ADB drivers by default, so you need to do this manually.
Anyway, I attempted to do it and got all the way to ./su. It then prompted me with the message "./su cannot execute - Permission denied". Obviously from there I can't link /mnt to /storage and I can't run pwn because it looks for the /storage folder.
If you have any suggestions how to get ./su running, let me know.
Click to expand...
Click to collapse
This method works but not all intructions are here.
First, you need to change permissions of su:
chown root:root su
chmod 6755 su
then run adb shell and remount / filesystem ro rw:
mount -o rw,remount /
now you can create symbolic link and run the exploit.
You can also perform rooting manually (without creating symlink and running pwn):
remount /system partition to rw: mount -o rw,remount /system
and copy su to /system/xbin, make sure that it has correct permissions (rwsr-sr-x) and that's it.
Now you can remount partitions back to ro.
Install supersu or superuser (whatever makes you happy, just check if it works correctly, superuser didn't work for me, it didn't prompt about root permission for any app, it just gave it, no matter how configured it was), Then install busybox, if you need one.
And you're done.
YES! Glad I waited!
Sent from my XT897 using xda premium
ujoty said:
This method works but not all intructions are here.
First, you need to change permissions of su:
chown root:root su
chmod 6755 su
then run adb shell and remount / filesystem ro rw:
mount -o rw,remount /
now you can create symbolic link and run the exploit.
You can also perform rooting manually (without creating symlink and running pwn):
remount /system partition to rw: mount -o rw,remount /system
and copy su to /system/xbin, make sure that it has correct permissions (rwsr-sr-x) and that's it.
Now you can remount partitions back to ro.
Install supersu or superuser (whatever makes you happy, just check if it works correctly, superuser didn't work for me, it didn't prompt about root permission for any app, it just gave it, no matter how configured it was), Then install busybox, if you need one.
And you're done.
Click to expand...
Click to collapse
Thank you. I just tried this and it worked. Confirmed with Root Checker. :>
micron said:
This is a work metod for root your not unlocked phone !
I find a solution after update to last new version
Download this : http://forum.xda-developers.com/showthread.php?t=2143437
After download and share fail with samba windows or mac sharing, you need to mount from file manage > remote storage
After fix permission go to adb folder and type :
"adb shell"
"cd /mnt/rfs0"
"./su"
"cd /"
"ln -s /mnt /storage"
Next step go to console and type :
adb kill-server
adb shell /storage/rfs0/pwn
Next : Install apk package from phone , Reboot Phone and now your phone is rooted!
Update from Play Market SuperSu and go.
Best regards,
m.
Click to expand...
Click to collapse
Thanks, I think this is exactly what I am looking for per this thread. Unfortunately, I don't quite have the knowledge (yet) to completely understand what you mean. I've rooted several phones, but never had to use ADB before so am unfamiliar with it. Also, what do you mean by this: "After download and share fail with samba windows..."?
cscotti said:
Thanks, I think this is exactly what I am looking for per this thread. Unfortunately, I don't quite have the knowledge (yet) to completely understand what you mean. I've rooted several phones, but never had to use ADB before so am unfamiliar with it. Also, what do you mean by this: "After download and share fail with samba windows..."?
Click to expand...
Click to collapse
By reading this link you will know hot to setup samba installation on a UBUNTU live cd. After doing that on your phone you should go to your FILE MANAGER --> remote storage and add the samba share to your phone. On the UBUNTU live cd, on your samba folder you should do this:
Code:
cd /path/to/share
wget http://vulnfactory.org/public/motoshare.tgz
tar xvf motoshare.tgz
sudo chown root:root pwn
sudo chmod 6755 pwn
After that you should put your phone in USB debugging mode and connect it to your PC. On your PC your should download the platform-tools folder of the Android SDK. The platform-tools folder contains adb (MAC) adb.exe (Windows) file. After you have adb, on your WIndows/MAC PC you should type:
Code:
./adb shell
cd /mnt/rfs0
./su
mount -o rw,remount /
cd /
ln -s /mnt /storage
exit (to exit the ADB shell)
adb kill-server
adb shell /storage/rfs0/pwn
Next you should copy eu.chainfire.supersu.apk on your phone storage and install it with file manager.
Reboot your device! Congratulations, your phone is rooted
desyncron said:
By reading this link you will know hot to setup samba installation on a UBUNTU live cd. After doing that on your phone you should go to your FILE MANAGER --> remote storage and add the samba share to your phone. On the UBUNTU live cd, on your samba folder you should do this:
Code:
cd /path/to/share
wget http://vulnfactory.org/public/motoshare.tgz
tar xvf motoshare.tgz
sudo chown root:root pwn
sudo chmod 6755 pwn
After that you should put your phone in USB debugging mode and connect it to your PC. On your PC your should download the platform-tools folder of the Android SDK. The platform-tools folder contains adb (MAC) adb.exe (Windows) file. After you have adb, on your WIndows/MAC PC you should type:
Code:
./adb shell
cd /mnt/rfs0
./su
mount -o rw,remount /
cd /
ln -s /mnt /storage
exit (to exit the ADB shell)
adb kill-server
adb shell /storage/rfs0/pwn
Next you should copy eu.chainfire.supersu.apk on your phone storage and install it with file manager.
Reboot your device! Congratulations, your phone is rooted
Click to expand...
Click to collapse
Wow, thanks for this. I was considering trying to condense down the instructions myself before I did this, but you beat me to it, and did a better job than I would have, considering I'm a novice at this stuff.
So your method uses a linux boot for samba, but then the rest is done on windows. Question: could you do the adb stuff on Linux? Seemed like some of the posts in the atrix threads were doing it that way, and I was just curious. I have mint 14-64 bit on a couple of my machines, as well windows, and was thinking this would be an opportunity to learn it a little better.
Sent from my XT897 using xda premium
Hello,
and what if I have unlocked bootloader? Is there any other way to root this phone?
desyncron said:
By reading this link you will know hot to setup samba installation on a UBUNTU live cd. After doing that on your phone you should go to your FILE MANAGER --> remote storage and add the samba share to your phone. On the UBUNTU live cd, on your samba folder you should do this:
Code:
cd /path/to/share
wget http://vulnfactory.org/public/motoshare.tgz
tar xvf motoshare.tgz
sudo chown root:root pwn
sudo chmod 6755 pwn
After that you should put your phone in USB debugging mode and connect it to your PC. On your PC your should download the platform-tools folder of the Android SDK. The platform-tools folder contains adb (MAC) adb.exe (Windows) file. After you have adb, on your WIndows/MAC PC you should type:
Code:
./adb shell
cd /mnt/rfs0
./su
mount -o rw,remount /
cd /
ln -s /mnt /storage
exit (to exit the ADB shell)
adb kill-server
adb shell /storage/rfs0/pwn
Next you should copy eu.chainfire.supersu.apk on your phone storage and install it with file manager.
Reboot your device! Congratulations, your phone is rooted
Click to expand...
Click to collapse
well that sounds a bit intimidating but thanks for spelling it out. I'll try to work up the nerve and make some time to give this a try.
Just curious, but why can't this be compressed into a one click batch file like before?
vangelm said:
Hello,
and what if I have unlocked bootloader? Is there any other way to root this phone?
Click to expand...
Click to collapse
If your bootloader is unlocked, you can easily root. You don't need any exploits etc.
Install TWRP, it will automatically root the device. Or, install CWM and then install SuperSU afterwards, which will root the device.
arrrghhh said:
If your bootloader is unlocked, you can easily root. You don't need any exploits etc.
Install TWRP, it will automatically root the device. Or, install CWM and then install SuperSU afterwards, which will root the device.
Click to expand...
Click to collapse
It works, thank you, have a nice day.
vangelm said:
It works, thank you, have a nice day.
Click to expand...
Click to collapse
Can you share what you did? Instructions seem to say that I need to install GooManager? The summary of GooManager says I need root to use it. TIA.
micron said:
This is a work metod for root your not unlocked phone !
I find a solution after update to last new version
Download this : http://forum.xda-developers.com/showthread.php?t=2143437
After download and share fail with samba windows or mac sharing, you need to mount from file manage > remote storage
After fix permission go to adb folder and type :
"adb shell"
"cd /mnt/rfs0"
"./su"
"cd /"
"ln -s /mnt /storage"
Next step go to console and type :
adb kill-server
adb shell /storage/rfs0/pwn
Next : Install apk package from phone , Reboot Phone and now your phone is rooted!
Update from Play Market SuperSu and go.
Best regards,
m.
Click to expand...
Click to collapse
**** I wish I saw this before i went to Motorola for my warranty voiding unlock code
---------- Post added at 05:01 PM ---------- Previous post was at 04:50 PM ----------
arrrghhh said:
If your bootloader is unlocked, you can easily root. You don't need any exploits etc.
Install TWRP, it will automatically root the device. Or, install CWM and then install SuperSU afterwards, which will root the device.
Click to expand...
Click to collapse
I like TWRP but CWM in my opinion is better (more supported).
amateurhack said:
Question: could you do the adb stuff on Linux? Seemed like some of the posts in the atrix threads were doing it that way, and I was just curious. I have mint 14-64 bit on a couple of my machines, as well windows, and was thinking this would be an opportunity to learn it a little better.
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
Yes. This can be done in Linux. I did it entirely with a LIVE USB. However, adb might not be installed by default (on mine it was not). To install it, do the following:
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
Click to expand...
Click to collapse
This will prevent you from running into errors when you start typing: adb shell
swintec said:
Can you share what you did? Instructions seem to say that I need to install GooManager? The summary of GooManager says I need root to use it. TIA.
Click to expand...
Click to collapse
Either use GooManager or the fastboot flash method. I think you do need to be rooted in order for GooManager to get the permissions it requires to flash recovery... So in that case, the only way initially to flash might be fastboot flash... Sorry.
alexwoellhaf said:
I like TWRP but CWM in my opinion is better (more supported).
Click to expand...
Click to collapse
Not even sure what this means. Any zip you can flash with CWM, you should be able to flash with TWRP. No?
They're both recoveries. One is touch-based, one isn't.
Having trouble with abd
Im running Ubuntu 12.04 full install (not live CD)
When I connect my phone, dmesg see the new device, and so does lsusb
dmesg
Code:
[ 290.617377] usb 2-1: USB disconnect, device number 2
[ 295.476023] usb 2-1: new high-speed USB device number 4 using ehci_hcd
[ 295.611624] scsi9 : usb-storage 2-1:1.0
[ 296.610626] scsi 9:0:0:0: Direct-Access motorola XT897 0001 PQ: 0 ANSI: 2
[ 296.611152] sd 9:0:0:0: Attached scsi generic sg3 type 0
[ 296.613548] sd 9:0:0:0: [sdc] Attached SCSI removable disk
lsusb:
Code:
Bus 002 Device 004: ID 22b8:2e36 Motorola PCS
However no matter what, when I run "adb devices", the phone does not show up.
51-android.rules
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="22b8", MODE="0666"
This is what I get with adb
Code:
[email protected]:/tmp/share# adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[email protected]:/tmp/share#
What else can I do???
desyncron said:
By reading this link you will know hot to setup samba installation on a UBUNTU live cd. After doing that on your phone you should go to your FILE MANAGER --> remote storage and add the samba share to your phone. On the UBUNTU live cd, on your samba folder you should do this:
Code:
cd /path/to/share
wget http://vulnfactory.org/public/motoshare.tgz
tar xvf motoshare.tgz
sudo chown root:root pwn
sudo chmod 6755 pwn
After that you should put your phone in USB debugging mode and connect it to your PC. On your PC your should download the platform-tools folder of the Android SDK. The platform-tools folder contains adb (MAC) adb.exe (Windows) file. After you have adb, on your WIndows/MAC PC you should type:
Code:
./adb shell
cd /mnt/rfs0
./su
mount -o rw,remount /
cd /
ln -s /mnt /storage
exit (to exit the ADB shell)
adb kill-server
adb shell /storage/rfs0/pwn
Next you should copy eu.chainfire.supersu.apk on your phone storage and install it with file manager.
Reboot your device! Congratulations, your phone is rooted
Click to expand...
Click to collapse
I am trying to run through these steps. For starters, when I enter the 'adp shell' I do not have a /mnt/rfs0 directory. The shared samba directory actually mounts at /storage/rfs0. No biggie. I go to that directory to run ./su. The su command runs, and I can see a pop up notification on my phone indicating the adb shell has been granted admin rights. The problem is that the ./su command never returns. As a matter of fact, if I just left it sit there, I get the admin rights pop up notification on my phone about once per minute so it seems like the su command is in some loop.
At this point I am stuck. I cant remount my file system as read/write without SU. I can run the ./su command in a different process, either in another adb shell or with the ./su& command but that does me no good as I cant execute any root commands in that same process.
Is there something that needs to change with the su command for the newer version my phone is running? I am running 9.8.2Q-122_XT897_FFW-5.
Thanks.
Use 'motochopper', search for it on xda then root is just one click away
Sent from my XT897 using xda app-developers app
+ Alcatel one touch pixi 4007E
+ Firmware Version: 2.3.6
+ Baseband Version: 6575M
+ Kernel Version: 2.6.35.7
+ Build number: GINGERBREAD
Useful shell commands
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod -R 755 <dir>
{ :;}; su
rm custpack/app/withlibs/Gmail.apk
rm custpack/app/withlibs/UNO3_20130613_100_gl_global.apk
rm custpack/app/withlibs/OnetouchLive_PIXO_20130723_V2.7_AMERICAS.apk
cd /data/data/com.bcmon.bcmon/files/tools
svc wifi enable
svc wifi disable
uname -a
mkdir backupwifi
mv WifiWsdsrv.apk backupwifi/WifiWsdsrv.apk
I hope these links are still valid, all is good and working October 5th, 2014, if any links die, please contact me and i'll see if i still have a copy of the files in a backup.
Device was rooted using the following software, from tutorial with these listed steps (below, cannot post links yet sorry) :
Software: Vroot App – VRoot_1.4.2.3195_Setup_95.exe @ a TinyURL
Tutorial: the root-alcatel-one-touch-pixi from ninjaromeo
Steps:
Make sure you have downloaded the above file.
Install it on your PC or Laptop.
Make sure that you have installed USB Drivers on your PC.
Then Open the installed program.
Now connect the phone to Computer using Original USB data cable that you got it when you bought the phone. Because using other kind of cables may not be detected by the computer. So only we are recommending to use the original.
Make sure that USB debugging is enabled on your phone.
Then wait for the Vroot to detect the device.
After that click the green button.
Then in a few seconds your mobile will be rebooted.
When it reboots your device must be rooted.
Then go to the Google Play store and download the SuperUser app or update it.
Now your mobile has been rooted successfully.
Then you can remove the phone from the Computer.
Normally first boot take some long time to complete. It will install the updates on the first boot. So, wait un till it finishes the booting process.
If your phone has stuck on the welcome screen or boot screen, just remove the battery and re insert it and do the above steps again.
Additional (important) software installed:
Terminal Emulator for Android
Jack Palevich
- June 20, 2014
Phone is rooted without issue all software installed fine but bcmon.apk (for wireless monitor mode) is not functioning by out of box root but i am working on it, arghum... aircrack-ng also does not function out of the box, titanium backup functions correctly and phone appears to operate perfect after Gmail.apk (bloatware) was removed (after many super stressful hours of directory scanning and OS information gathering but not bad for $99 and some mind numbing research lol!).
Argh... will keep posted on bcmon
Current issue (October 06th, 2014 12:48AM EST +10) = <message>command: 'cp' failed with exitValue = 127</message>
so...
install the following BusyBox to help get bcmon to work on this device:
BusyBox X
Robert Nediyakalaparambil [root]
- August 8, 2014
and now bcmon records are as follows:
"<record>
<date>Oct 6, 2014 2:16:47 AM</date>
<millis>1412522207853</millis>
<sequence>9</sequence>
<logger>com.bcmon.bcmon.chipsets.BCM4330B2</logger>
<level>FINE</level>
<class>com.bcmon.bcmon.chipsets.Chipset</class>
<method>detect</method>
<thread>0</thread>
<message>return false</message>
</record>"
then... now... i have arghum... downloaded the entire bcm4330/ directory from bcmon googlecode /svn/trunk/ and simply copied to the phone's sdcard via usb mode.
opened terminal (on phone) in su mode, navigated to bcm4330/driver/src/bcmdhd/ and attempted to launch sh build.sh but now have the following error:
"can't cd to /data/data/jackpal.androidterm/app_HOME/android/system/kernel/samsung/smdk4210
make: command not found"
More of a note really, a side bit of information
... installed Android SDK (Eclipse) and prerequisites (Java 64bit, in Windows), with phone connected via usb, and sdcard usb mode disabled (card mounted on phone and not windows).
Simply extraced archive to desktop (C:\Users\<username>\Desktop\adt-bundle-windows-x86_64-20140702).
Within the extracted folder you will find the following directory (providing the same versions) "\sdk\platform-tools" and within there resides the adb.exe windows command line tool.
I have now opened a command-line window (cmd.exe) at this directory ("\sdk\platform-tools", held shift and right-clicked on folder, windows 7) and issued the following commands:
adb reboot
adb /proc
things appear to have executed perfect, so i CUT all files and folders from the directory "C:\Users\<username>\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools" and pasted them into a new folder called "backup", i am now left with three files "adb.exe", "AdbWinApi.dll", "AdbWinUsbApi.dll" and one folder "\backup" in this directory...
i now re-execute the following command:
adb /proc
it would appear as though all the files that i CUT from this directory are in fact being rebuilt...
the adb.exe windows process finished with the result:
"31308 files pulled. 0 files skipped."
Click to expand...
Click to collapse
must say...
i dig this QR --> http://forum.xda-developers.com/member.php?u=1164149
and have concluded the following results.
bcmon is useless!, wifilog does not work on Alcatel one touch pixi 4007e but does on ZTE Telstra UNO T12, WiFiReaver, Wifi Analyzer and Wi-Fi Direct are all that is needed, in fact i have uninstalled bcmon and BusyBox.
Use mobiles to locate networks and normal means for wireless traversal, why else do people buy mobile phones?.
For an extra note on this model phone (and this will be posted in a separate thread) and help on removing apps manually (i had to do this as android would not allow me to uninstall and it was no longer listed as an installed app in Google Play )
I used the following commands (In Terminal Emulator) in this order to remove Wi-Fi Direct (in this case but same process should work for other apps) manually (remember this is only a backup of the app and not a complete removal in the phone system, bricks are not to be made but found, this merely removes the app from the android dashboard/desktop/app list)...
su
ls
cd system/app
ls
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mkdir backupwifi
mv WifiWsdsrv.apk backupwifi/WifiWsdsrv.apk
mv WifiWsdsrv.odex backupwifi/WifiWsdsrv.odex
mv WifiContactSync.odex backupwifi/WifiContactSync.odex
mv WifiContactSync.apk backupwifi/WifiContactSync.apk
mv WifiP2PWizardy.odex backupwifi/WifiP2PWizardy.odex
mv WifiP2PWizardy.apk backupwifi/WifiP2PWizardy.apk
And to actually remove the backupwifi folder (completely remove everything from system) issue the following command...
rm -r backupwifi
Click to expand...
Click to collapse
Hello everyone,
This method I'm going to write is tried on my own Lenovo A7600-H Kitkat 4.4.2 tablet, which I did not flash because I'm not sure about stock roms available on the net. If I had found a reliable rom I wouldn't be able learn this
To remove this virus you need to install busybox, Terminal emulator, Root explorer pro and you must have Supersu not superuser which is installed by Kingoroot. If you have rooted your device with kingoroot, so you need to change that.
Here is how to change that:
Google this: how to get ride and replace kinguser with supersu app (Follow first zidroid link)
I'm not able to submit links so im going to write the exact apps with developer names to download from Playstore.
Busybox Installer by JRummy Apps Inc.
Terminal Emulator by Jack Palevich
Root Explorer Pro by Speed Software
Once you have installed everything here is what to do in steps:
[Note: USB DEBUGGING MUST BE ENABLED Turn on Usb Debugging by going to settings> developer options> Usb debugging]
1) Turn off wifi/3G/4G, and then go to settings> apps> all> disable time service and monkey test. (If already frozen via titanium backup or other app) skip this.
2) Open Root explorer go to system/xbin and see if there is any file starting with a dot (eg: .ext.base) also note that every (.) file has diff permission then the rest of other files. So just remember those files with dots because those are the one that you're going to remove in terminal emulator.
3) Go back to system and then go to Priv-app folder and look for these two files
[1] cameraupdate.apk [2] providerCertificate.apk and also notice permission of these two files are different then the rest of Apks so these two are the base of MT TS virus and needs to be deleted.
4) Open Terminal Emulator OR if you have access to your device via adb from a computer.
5) WHAT TO TYPE IN TERMINAL EMULATOR or ADB (CMD Windows)
adb devices (Type this line if you're using adb Windows)
adb shell
su
mount -o remount,rw /system
cd system/priv-app
chattr -iaA providerCertificate.apk
rm providerCertificate.apk
chattr -aA cameraupdate.apk
rm cameraupdate.apk
cd ..
cd system/xbin
chattr -iaA .b
rm .b
chattr -iaA .ext.base
rm .ext.base
chattr -iaA .sys.apk
rm .sys.apk
[NOTE: If you are using older version than KK you need not to type priv-app just type cd system/app]
6) Please make sure you type the file name correctly just as providerCertificate C is capital otherwise permission wont change.
7) Exit Emulator/ADB
8) Go to settings> apps> all> send me the screenshot if you have Monkey test or Time Service there
9) I'm 100% sure if you've followed everything as I mentioned you are good as new and you don't need to flash.
10) I'm not a developer and That's it!
Money test and time service virus removal
In karbonn A 30
x-bin has these files :
.b
.ext.base
.sys.apk
root/system has no priv-app but app file, it has two files:
SettingProvider.apk
cameraupdate.apk
I have given command cd system/app
followed by
chattr -iaA SettingProvider.apk
....Error...
chattr-iaA not found
WHAT TO DO ?
drdkundu said:
In karbonn A 30
x-bin has these files :
.b
.ext.base
.sys.apk
root/system has no priv-app but app file, it has two files:
SettingProvider.apk
cameraupdate.apk
I have given command cd system/app
followed by
chattr -iaA SettingProvider.apk
....Error...
chattr-iaA not found
WHAT TO DO ?
Click to expand...
Click to collapse
If you don't have a priv-app folder than you are not on Kitkat and you have to delete files from system/app folder.
Well anyway you have to delete cameraupdate.apk and providerCertificate.apk
and you are deleting SettingProvider.apk which I never said you have to.
Please look closely
Nuh99 said:
If you don't have a priv-app folder than you are not on Kitkat and you have to delete files from system/app folder.
Well anyway you have to delete cameraupdate.apk and providerCertificate.apk
and you are deleting SettingProvider.apk which I never said you have to.
Please look closely
Click to expand...
Click to collapse
Dearest,
It is 4.0.4 ics , in app folder there is no providerCertificate.apk but SettingProvider.apk which is newer (as per date also AVG prompted it as malware and tried to uninstall but failed) than the original SettingProvider.apk ,i tried to insert screenshots,but prevented by forum thanks if you may share with me your email address i may be able to post
command : chatter... gives error message, is there different procedure for ics ?
Secondly,
I have searched out that karbonn A 30 is a rebranded version of vsun I 1S ,and original rom based on kitkat is available on their site, is it safe to flash vsun rom on it or shall I go for abacada rom available on xda?
drdkundu said:
Dearest,
It is 4.0.4 ics , in app folder there is no providerCertificate.apk but SettingProvider.apk which is newer (as per date also AVG prompted it as malware and tried to uninstall but failed) than the original SettingProvider.apk ,i tried to insert screenshots,but prevented by forum thanks if you may share with me your email address i may be able to post
command : chatter... gives error message, is there different procedure for ics ?
Secondly,
I have searched out that karbonn A 30 is a rebranded version of vsun I 1S ,and original rom based on kitkat is available on their site, is it safe to flash vsun rom on it or shall I go for abacada rom available on xda?
Click to expand...
Click to collapse
Send me screenshot or personally talk to me on www(.)facebook(.)com/99nuh
Btw you are unable to remove providersettings.apk because you might be typing wrong attributes for it.
To see its attribute cd system/app [enter]
then type lsattr to look for attributes of providersettings.apk
and then use those attributes with - and rm that file.
And If you want to flash your phone/tablet go with your brand official rom.
screenshots
Nuh99 said:
Send me screenshot or personally talk to me on www(.)facebook(.)com/99nuh
Btw you are unable to remove providersettings.apk because you might be typing wrong attributes for it.
To see its attribute cd system/app [enter]
then type lsattr to look for attributes of providersettings.apk
and then use those attributes with - and rm that file.
And If you want to flash your phone/tablet go with your brand official rom.
Click to expand...
Click to collapse
Screenshots below:
please add http.. before
//photos(dot)google(dot)com/photo/AF1QipNuigMsljp-1jsPLPqo_QuG_27vDUHS-DzSZZi-
//photos(dot)google(dot)com/photo/AF1QipMUmGdmU7TyETRaomzJzzKSuFYOiW7e53urGT6P
//photos(dot)google(dot)com/photo/AF1QipMRD8sJA0j84yHIzYSohk4KDggUTw2iTcGKZ7mU
//photos(dot)google(dot)com/photo/AF1QipNZQ7TTbDGrDNSMKMAtCt5I7P8_1QFQMyVRi6-_
drdkundu said:
Screenshots below:
please add http.. before
//photos(dot)google(dot)com/photo/AF1QipNuigMsljp-1jsPLPqo_QuG_27vDUHS-DzSZZi-
//photos(dot)google(dot)com/photo/AF1QipMUmGdmU7TyETRaomzJzzKSuFYOiW7e53urGT6P
//photos(dot)google(dot)com/photo/AF1QipMRD8sJA0j84yHIzYSohk4KDggUTw2iTcGKZ7mU
//photos(dot)google(dot)com/photo/AF1QipNZQ7TTbDGrDNSMKMAtCt5I7P8_1QFQMyVRi6-_
Click to expand...
Click to collapse
They are not opening. Error!
Kindly send me @ my fb.
Thanks, its work, no more monkey test and Time service on my android.
before: my Malwarebytes detect there are virus cameraupdate.apk;MusicProvider.apk;
LiveWallpaper.apk;SistemCertificate.apk and providerCertificate.apk .so i delete all on system/app. all can delete except cameraupdate.apk
I try your way but i have different case on my ColorOS android 4.2.2
Using App Master(EasyApps Studio) i find that :
monkey test refer to sytem/app/cameraupdate.apk
but time service refer to data/app/com.android.hardware.ext0-1.apk
so i add
cd data/app
chattr -iaA com.android.hardware.ext0-1.apk
rm com.android.hardware.ext0-1.apk
with Root explorer browse root directory and sd card search cameraupdate.apk and com.android.hardware.ext0-1.apk after find check list all then delete.
No need clear cache just delete
/data/dalvik-cache/[email protected]@[email protected]
/data/dalvik-cache/[email protected]@com.android.hardware.ext0-1.apk @classes.dex
This work
Thanks
Note:
if you find ...Error... chattr -iaA not found
WHAT TO DO ? its mean you only install app not yet istall busybox
after install Busybox Installer by JRummy Apps Inc. from play store open app
on tab installer, select busybox ver1.2 select intall location /system/xbin/ then touch Install
agzpur said:
Thanks, its work, no more monkey test and Time service on my android.
before: my Malwarebytes detect there are virus cameraupdate.apk;MusicProvider.apk;
LiveWallpaper.apk;SistemCertificate.apk and providerCertificate.apk .so i delete all on system/app. all can delete except cameraupdate.apk
I try your way but i have different case on my ColorOS android 4.2.2
Using App Master(EasyApps Studio) i find that :
monkey test refer to cameraupdate.apk
but time service refer to com.android.hardware.ext0-1.apk
so i add
cd data/app
chattr -iaA com.android.hardware.ext0-1.apk
rm com.android.hardware.ext0-1.apk
with Root explorer browse root directory and sd card search cameraupdate.apk and com.android.hardware.ext0-1.apk after find check list all then delete.
No need clear cache just delete
/data/dalvik-cache/[email protected]@[email protected]
/data/dalvik-cache/[email protected]@com.android.hardware.ext0-1.apk @classes.dex
This work
Thanks
Click to expand...
Click to collapse
Yes you don't need cache clear but doing it on a safe side is better.
If this post helped you please give a thumbs up!
i can't change the permission on root explorer.
Nuh99 said:
Hello everyone,
This method I'm going to write is tried on my own Lenovo A7600-H Kitkat 4.4.2 tablet, which I did not flash because I'm not sure about stock roms available on the net. If I had found a reliable rom I wouldn't be able learn this
To remove this virus you need to install busybox, Terminal emulator, Root explorer pro and you must have Supersu not superuser which is installed by Kingoroot. If you have rooted your device with kingoroot, so you need to change that.
Here is how to change that:
Google this: how to get ride and replace kinguser with supersu app (Follow first zidroid link)
I'm not able to submit links so im going to write the exact apps with developer names to download from Playstore.
Busybox Installer by JRummy Apps Inc.
Terminal Emulator by Jack Palevich
Root Explorer Pro by Speed Software
Once you have installed everything here is what to do in steps:
1) Turn off wifi/3G/4G Open settings> apps> all> disable time service and monkey test. (If already frozen via titanium backup or other app) skip this.
2) Open Root explorer go to system/xbin and see if there is any file starting with a dot (eg: .ext.base) also note that every (.) file has diff permission then the rest of other files. So just remember those files with dots because those are the one that you're going to remove in terminal emulator.
3) Go back to system and then go to Priv-app folder and look for these two files
[1] cameraupdate.apk [2] providerCertificate.apk and also notice permission of these two files are different then the rest of Apks so these two are the base of MT TS virus and needs to be deleted.
4) Open Terminal Emulator OR if you have access to your device via adb from a computer.
5) WHAT TO TYPE IN TERMINAL EMULATOR or ADB (CMD Windows)
adb devices (Type this line if you're using adb Windows)
adb shell
su
cd system/priv-app
chattr -iaA providerCertificate.apk
rm providerCertificate.apk
chattr -aA cameraupdate.apk
rm cameraupdate.apk
cd ..
cd system/xbin
chattr -iaA .b
rm .b
chattr -iaA .ext.base
rm .ext.base
chattr -iaA .sys.apk
rm .sys.apk
6) Please see if your device xbin has more files with dots because these are three files I had so if there are more you need to remove them with the same command I mentioned above (e.g:cd system/xbin [Enter] chattr -iaA .New.file & then rm .New.file and make sure you type the file name correctly just as providerCertificate C is capital otherwise permission wont change.
7) Exit Emulator/ADB shutdown your device go to recovery clear cache and restart.
8) Go to settings> apps> all> send me the screenshot if you have Monkey test or Time Service there
9) I'm 100% sure if you've followed everything as I mentioned you are good as new and you don't need to flash.
10) I'm not a developer and That's it!
Click to expand...
Click to collapse
i can't change the permission on root explorer. can you help me to fix it..it says failed to change permission because your sdcard..........something..
plz help me
dsamivai said:
i can't change the permission on root explorer. can you help me to fix it..it says failed to change permission because your sdcard..........something..
plz help me
Click to expand...
Click to collapse
You can't change it with Root Explorer you have to change permissions with Terminal Emulator by the entering the commands I've mentioned in my guide.
Nuh99 said:
You can't change it with Root Explorer you have to change permissions with Terminal Emulator by the entering the commands I've mentioned in my guide.
Click to expand...
Click to collapse
Hi, Im a user of 8.31 O+ phone. Ive downloaded all the 3 apps youve mentioned. But after installing busybox (the app) I cant install any version of it.. thats why everytime I'll type the commands in emulator indicated above, it says error...
please help... thank you
Nuh99 said:
Hello everyone,
This method I'm going to write is tried on my own Lenovo A7600-H Kitkat 4.4.2 tablet, which I did not flash because I'm not sure about stock roms available on the net. If I had found a reliable rom I wouldn't be able learn this
To remove this virus you need to install busybox, Terminal emulator, Root explorer pro and you must have Supersu not superuser which is installed by Kingoroot. If you have rooted your device with kingoroot, so you need to change that.
Here is how to change that:
Google this: how to get ride and replace kinguser with supersu app (Follow first zidroid link)
I'm not able to submit links so im going to write the exact apps with developer names to download from Playstore.
Busybox Installer by JRummy Apps Inc.
Terminal Emulator by Jack Palevich
Root Explorer Pro by Speed Software
Once you have installed everything here is what to do in steps:
[Note: USB DEBUGGING MUST BE ENABLED Turn on Usb Debugging by going to settings> developer options> Usb debugging]
1) Turn off wifi/3G/4G, and then go to settings> apps> all> disable time service and monkey test. (If already frozen via titanium backup or other app) skip this.
2) Open Root explorer go to system/xbin and see if there is any file starting with a dot (eg: .ext.base) also note that every (.) file has diff permission then the rest of other files. So just remember those files with dots because those are the one that you're going to remove in terminal emulator.
3) Go back to system and then go to Priv-app folder and look for these two files
[1] cameraupdate.apk [2] providerCertificate.apk and also notice permission of these two files are different then the rest of Apks so these two are the base of MT TS virus and needs to be deleted.
4) Open Terminal Emulator OR if you have access to your device via adb from a computer.
5) WHAT TO TYPE IN TERMINAL EMULATOR or ADB (CMD Windows)
adb devices (Type this line if you're using adb Windows)
adb shell
su
cd system/priv-app
chattr -iaA providerCertificate.apk
rm providerCertificate.apk
chattr -aA cameraupdate.apk
rm cameraupdate.apk
cd ..
cd system/xbin
chattr -iaA .b
rm .b
chattr -iaA .ext.base
rm .ext.base
chattr -iaA .sys.apk
rm .sys.apk
[NOTE: If you are using older version than KK you need not to type priv-app just type cd system/app]
6) Please see if your device xbin has more files with dots because these are three files I had so if there are more you need to remove them with the same command I mentioned above (e.g:cd system/xbin [Enter] chattr -iaA .New.file & then rm .New.file and make sure you type the file name correctly just as providerCertificate C is capital otherwise permission wont change.
7) Exit Emulator/ADB shutdown your device go to recovery clear cache and restart.
8) Go to settings> apps> all> send me the screenshot if you have Monkey test or Time Service there
9) I'm 100% sure if you've followed everything as I mentioned you are good as new and you don't need to flash.
10) I'm not a developer and That's it!
Click to expand...
Click to collapse
I get also the message : chattr: not found
I tried from adb and terminal
Any idea?
Nuh99 said:
I'm not a developer and That's it!
Click to expand...
Click to collapse
Forgive me, but your statement quoted above is the only one that makes sense here. You were booted from Security Discussion thread and you move here.
You confuse people, give nonsensical advice and don't seem to know what you are talking about. First of all the chattr command is not supposed to work on Android ext4, so, no wonder people can't remove files this way. And anyway, your prolong instructions are not worth the "paper" they are written on. Even if someone would succeed following them, there is no guarantee they remove the virus. The proper way is to completely reformat your phone including internal SD and external SD, which you do in recovery by formatting System, Cache, Dalvik cache, Data and both sd cards. Period. And for the future, don't install any third party apps unless you compile them from source by yourself or someone you trust.
OK
joshuas_79 said:
I get also the message : chattr: not found
I tried from adb and terminal
Any idea?
Click to expand...
Click to collapse
If you are having this error it means you have installed busybox app not busy box.
To do this open busybox app in your device, select busybox ver1.2, select intall location /system/xbin/ and tap install.
Then try the procedure
optimumpro said:
Forgive me, but your statement quoted above is the only one that makes sense here. You were booted from Security Discussion thread and you move here.
You confuse people, give nonsensical advice and don't seem to know what you are talking about. First of all the chattr command is not supposed to work on Android ext4, so, no wonder people can't remove files this way. And anyway, your prolong instructions are not worth the "paper" they are written on. Even if someone would succeed following them, there is no guarantee they remove the virus. The proper way is to completely reformat your phone including internal SD and external SD, which you do in recovery by formatting System, Cache, Dalvik cache, Data and both sd cards. Period. And for the future, don't install any third party apps unless you compile them from source by yourself or someone you trust.
Click to expand...
Click to collapse
but my problem is that I can't find firmware for my tablet: engel tb0725ips
joshuas_79 said:
but my problem is that I can't find firmware for my tablet: engel tb0725ips
Click to expand...
Click to collapse
Get a custom rom. If there is no custom rom, then do a factory reset and then format external and internal sd cards.
Brother Nuh has helped me solving cameraupdate and time service android malwares without flashing, may the Almighty bless him abundantly I really learnt some new things from him Thumbs Up for Brother Nuh:good:
optimumpro said:
Get a custom rom. If there is no custom rom, then do a factory reset and then format external and internal sd cards.
Click to expand...
Click to collapse
I can't find a custom recovery either, so only stock recovery with not many options. :crying: