Is there any way to root MIcromax A52 ???? - Upgrading, Modifying and Unlocking

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

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

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

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

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

any one tried the method ... does it work

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Related

steps for gfree using mac.help!

hi! im one of those G2 users that was unlocked but no network signal.. i know that this has been fixed.. just want to ask since im really not familiar with all the terms..
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
what exactly means " You will need to download a program called gfree that will first copy partition 7 of the phone, then patch it, then reflash back to your phone"
im using mac.. download already sdk.. my phone already recognized.. i just dont know what exactly to do with the gfree_02 zip file or how do i open it. thanks.
You need a tool on your Mac that can recognise ZIP files and un-zip them. I had a quick Google and found loads. I don't know whether there's anything built-in though, I know very little about Macs.
All you need to do is to extract the contents of gfree_02.zip to your Mac, then you can follow the rest of the instructions. I assume you have got adb working, based on what you've said.
You can probably just double click it to unzip it or, maybe right click and open with Archive Utility.
What version OS are you running on your Mac? 10.5? 10.6? etc..
unzip files, place in the platform-tools older where your adb is, open up terminal and push the files to your phone then run terminal emulator and follow this wiki article.
http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting
m0bstar said:
unzip files, place in the platform-tools older where your adb is, open up terminal and push the files to your phone then run terminal emulator and follow this wiki article.
http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting
Click to expand...
Click to collapse
hi! thanks for the quick response i tried doing but when i typed adb push gfree /data/local it says (gfree folder is in the platform tools folder)
cannot stat 'gfree': No such file or directory
or
when i type in adb push /Users/xxxxxx/Desktop/gfree_02 it says (gfree is in desktop)
Android Debug Bridge version 1.0.26 - (and shows all the commands)
all i need is to push gfree right? but i cant do the right command.. pls help thanks
It's hard to say, but it seems like you haven't unzipped the .zip file yet. Can you see the files? There should be about 9 files, mostly ending in .c and .h You only need the one called gfree (with no extension).
if you did unzip and gfree in on the desktop - you can see the file, not just the enclosing folder, then try:
adb push /Users/xxxxxx/Desktop/gfree
now it says:
$ adb push /Users/xxxxxxx/Desktop/gfree
adb: permission denied
is there like a step by step on how to do it?
Did you put in the target location? The /data/local/ bit at the end
Adb push /users.../desktop/gfree_02/gfree /data/local/
Sent from my CyanogenMod Vision
accons said:
now it says:
$ adb push /Users/xxxxxxx/Desktop/gfree
adb: permission denied
is there like a step by step on how to do it?
Click to expand...
Click to collapse
Are you typing that on your phone (terminal emulator) or on your PC/Mac ? It needs to be on your PC/Mac, not the phone.
You need to unzip the gfree files and place them individually in the platform-tools folder not as /plantform-tools/gfree/.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
make sure type in terminal "cd /computer-name/sdk-folder-location/platform-tools/"
then follow through with "./adb"
and then start pushing the gfree files with "./adb push gfree"
thanks for all your reply!
im done with these:
make sure type in terminal "cd /computer-name/sdk-folder-location/platform-tools/"
then follow through with "./adb"
and then start pushing the gfree files with "./adb push gfree"
and then i typed ./adb shell as mentioned on the wiki:
On your computer's terminal/command line, navigate to where the gfree file is, and then…
adb push gfree /data/local
adb shell
but when i tried the next step on wiki
This copies gfree to your phone, then puts you in your phone's terminal. Then (IN THE ADB SHELL) do this:
su
cd /data/local
chmod 777 gfree
./gfree -f
sync
when i typed su --it says
su: permission denied
what happened? thanks.
sounds like you arent temp rooted, you sure you temp rooted first?
i havent temp root my phone yet.. coz when i type
$ adb push su /sdcard/su
when i hit enter it will reply
cannot stat 'su': No such file or directory
i need the right command for my mac and also the right path for my g2 terminal emulator.. coz the initial command is export PATH+/data/local/bin:$PATH
is this correct or do i need to change the directory or my command.
all i really need is to "unlock" my phone..
thank you..
accons said:
i havent temp root my phone yet.. coz when i type
$ adb push su /sdcard/su
when i hit enter it will reply
cannot stat 'su': No such file or directory
i need the right command for my mac and also the right path for my g2 terminal emulator.. coz the initial command is export PATH+/data/local/bin:$PATH
is this correct or do i need to change the directory or my command.
all i really need is to "unlock" my phone..
Click to expand...
Click to collapse
Your PATH is ok because it is finding the "adb" command ok.
What isn't ok is that it can't find "su" when you try to use adb to copy (push) it to the phone. You need to do a "cd" to change directory to wherever you unzipped the files that you are trying to push.
e.g. if "su" and the other files are in /tmp on your Mac, then you need to do "cd /tmp" and then run the adb commands.

Root samsung gem sch-i100

Can anyone tell me how to root a samsung gem (sch-i100) I posted this in 2 other sections already about month ago but I've had no respnoses at all. Can anyone tell me anything????
Sent from my SPH-D700 using Tapatalk
One click Root?
Google it, and that device might not be supported by a dev who's rooted it yet.
justen7723 said:
Can anyone tell me how to root a samsung gem (sch-i100) I posted this in 2 other sections already about month ago but I've had no respnoses at all. Can anyone tell me anything????
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I found this through Google:
Download and Install Samsung Drivers
64bit:
http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x64.shtml
32bit:
http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x86.shtml
Download and Install ADB
Android SDK | Android Developers
http://developer.android.com/sdk/index.html
Download the attached files
Setup ADB to work in your PATH
Windows: Go to System Properties > Advanced Tab > Environment Variables
Click on the Path variable under System Variables and hit edit
Add a colon: and the location of your android-sdk tools folder
In example :C:\Android\SDK\android-sdk-windows\tools
connect your phone with the usb cable and go to settings > applications > enable debugging
run cmd
cd to the directory of the unzipped files included and follow these commands to a tee
adb push su /sdcard/su
adb push rage.bin /data/local/tmp/rage.bin
adb push busybox /sdcard/busybox
adb shell
cd /data/local/tmp
chmod 0755 rage.bin
./rage.bin
wait....
when it brings you back to your original shell or windows cmd promt follow these commands
adb shell
mount -t rfs -o remount,rw /dev/block/stl9 /system
cd /system/xbin
cat /sdcard/su > su
cat /sdcard/busybox > busybox
chmod 4755 su
chmod 4755 busybox
exit
adb install Superuser.apk
Thats it, I hope this helps you. Its a complete rooting process.
Once you have Root, simply download ROMManager from the Market, do a "Backup" from the app, and download whichever ROM you want from the list of available ROMs inside the app, enjoy!
Read more: how to root android 2.1 on Samsung Gem - JustAnswer http://www.justanswer.com/cell-phones/4ztjq-root-android-2-1-samsung-gem.html#ixzz1VhiYTWP4
Thanks haven't tried it yet but I will, (its for a friend)
Sent from my SPH-D700 using Tapatalk
kennyglass123 said:
I found this through Google:
[/url]
Click to expand...
Click to collapse
Impressive, most impressive.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried this method and got it to work but it still didnt root im running 2.2.1 though i dont know how to get this going
I'm missing something here.. where does rage.bin come from? For that matter, where are the superuser and busybox binaries coming from?
jimnutt said:
I'm missing something here.. where does rage.bin come from? For that matter, where are the superuser and busybox binaries coming from?
Click to expand...
Click to collapse
Why necro this thread? Let it die in peace.
Sent from my SPH-D700 using Tapatalk
kennyglass123 said:
I found this through Google:
Download and Install Samsung Drivers
64bit:
http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x64.shtml
32bit:
http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x86.shtml
Download and Install ADB
Android SDK | Android Developers
http://developer.android.com/sdk/index.html
Download the attached files
Setup ADB to work in your PATH
Windows: Go to System Properties > Advanced Tab > Environment Variables
Click on the Path variable under System Variables and hit edit
Add a colon: and the location of your android-sdk tools folder
In example :C:\Android\SDK\android-sdk-windows\tools
connect your phone with the usb cable and go to settings > applications > enable debugging
run cmd
cd to the directory of the unzipped files included and follow these commands to a tee
adb push su /sdcard/su
adb push rage.bin /data/local/tmp/rage.bin
adb push busybox /sdcard/busybox
adb shell
cd /data/local/tmp
chmod 0755 rage.bin
./rage.bin
wait....
when it brings you back to your original shell or windows cmd promt follow these commands
adb shell
mount -t rfs -o remount,rw /dev/block/stl9 /system
cd /system/xbin
cat /sdcard/su > su
cat /sdcard/busybox > busybox
chmod 4755 su
chmod 4755 busybox
exit
adb install Superuser.apk
Thats it, I hope this helps you. Its a complete rooting process.
Once you have Root, simply download ROMManager from the Market, do a "Backup" from the app, and download whichever ROM you want from the list of available ROMs inside the app, enjoy!
Read more: how to root android 2.1 on Samsung Gem - JustAnswer http://www.justanswer.com/cell-phones/4ztjq-root-android-2-1-samsung-gem.html#ixzz1VhiYTWP4
Click to expand...
Click to collapse
Wow, that's extraordinarily similar to the process I had to use to root my Epic4G WAY back in Nov of 2010. Those were scary times.
I remember that while I was doing this my Epic went black and unresponsive, and it took me several hours to get it working again. I felt faint and was shaking the whole time.
From that point on I always told friends who wanted to root- it's not really any fun until you think that you've bricked your phone a couple of times.
sent from my secret underground bunker
Samsung gem i100
I recently got a samsung gem i100. Biggest problem with it was it didn't have the new version of google play (market) on it. I like installing programs from the website, not typing away looking for the right app on my phone. So I installed APK installer, and upgraded the os from 2.1 to 2.2. Which did kill google market.. However I have a different phone and on that phone I have an app called APK extractor(the phone is rooted) I extracted he newest version of google play and uploaded it to the Gem. Google play works fine so far... The 3g data isn't working but the phone is for my kid and Verizon charges for data now. It works ok, but would like the 3g data to work again.any ideas? (The only data it has is wifi. I wonder if it is a setting somewhere, I wouldn't mind throwing on a new os if there was one I could find so long as it was compatible.)
Samsung gem i100
I was hoping someone on here had a unmodified Samsung gem i100 from Verizon so they could use super one click on it and root it then back up the rom, and share it because I broke mine by updating it to 2.2... (the rom for Verizon is 2.1, but 2.2 is for US cellular and Alltel) I downloaded the source code from Samsung in a long shot attempt to repackage it so it will make the data work on the gem again. I think the problem with 2.2 lies in the drivers for the board. If I can fix that then 2.2 should work for Verizon. Although I have no idea what I'm doing I have downloaded Oracle VM VirtualBox, and setup what I need for Android kitchen so I can run the current rom from there and hopefully make the changes...
The other project I'm working on is to find out why the game Temple Run 2 will run on a Droid 4 but not a Droid 1, and if there is a way to modify the Droid 1 so it can run it. My kids like the game, but I don't want them using my phone to play it all the time...
Any pointers would be great. I don't look forward to teaching myself how to write programs but it seems that is my only option...
Are you aware that this is the Epic 4G (with keyboard) forum?
Sent from my Nexus 7 using Tapatalk 2
norcalnub said:
I was hoping someone on here had a unmodified Samsung gem i100 from Verizon so they could use super one click on it and root it then back up the rom, and share it because I broke mine by updating it to 2.2... (the rom for Verizon is 2.1, but 2.2 is for US cellular and Alltel) I downloaded the source code from Samsung in a long shot attempt to repackage it so it will make the data work on the gem again. I think the problem with 2.2 lies in the drivers for the board. If I can fix that then 2.2 should work for Verizon. Although I have no idea what I'm doing I have downloaded Oracle VM VirtualBox, and setup what I need for Android kitchen so I can run the current rom from there and hopefully make the changes...
The other project I'm working on is to find out why the game Temple Run 2 will run on a Droid 4 but not a Droid 1, and if there is a way to modify the Droid 1 so it can run it. My kids like the game, but I don't want them using my phone to play it all the time...
Any pointers would be great. I don't look forward to teaching myself how to write programs but it seems that is my only option...
Click to expand...
Click to collapse
Also. The Droid 1 has an armv6 processor and the Droid 4 has an armv7 processor. So in order for the game to play on the Droid 1, you'd need to find someone who knows how to port games from armv7 to armv6.
Sent from my SPH-D700 using Tapatalk 2
nikon120 said:
Are you aware that this is the Epic 4G (with keyboard) forum?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Apparently they are not aware -_____-
silly necroers.
---------- Post added at 04:50 PM ---------- Previous post was at 04:41 PM ----------
https://code.google.com/p/intercept-root/

Root ZYNC Z930 by adb commands

Hi everyone,
I have rooted my Zync z930 tablet with adb commands and just wants to let you know.
After going through lots of root methods i came to know the procedure.
Hope my method helps you.. :good:
I have collected the required drivers, files and uploaded them to 4shared.
Just Download the required files from http://www.4shared.com/rar/WiRHc5mG/Zync_Z930_Root_tools.html
And extract it.
To install adb drivers for your tablet, enable usb debugging in your tablet.
Go to settings ->developer option ->tick USB debugging and then connect your tablet to your PC with the usb cablet supplied with your tablet.
Now windows will show Failed to install drivers. just close it.
Go to desktop, right click on Computer -> manage ->device manager, you will see Z930 with an error symbol. Right click on it, update driver software.
->Browse my computer for driver software.
->let me pick from a list of devices on my computer.
->have disk
->select the location where you have extracted Zync Z930 Root tools.rar. Point on drivers. And click ok.
->it will show Android adb interface
click ok. it will show certificate warning. Just accept and let in install.)
So now you have installed your adb drivers....
Rooting your tablet
Now in the "Zync Z930 Root tools" folder, hold shift and right click.
"open command window here"
in the command window, type the following commands..
adb devices
(it will show the connected tablet with a different digits, thats normal)
adb root
(it will give you root permission)
adb shell
(U will be taken to Android shell)
(now in the shell, type the following commands, please take care of the space, comma and other signs and symbols carefully and execute)
(If you get $ sign, you still don't have root permission, if you have #, it means you have the root permission)
#mount -o remount,rw -t rfs /dev/block/st19 /system
#exit
(you'll be taken back)
adb push busybox /system/bin
adb push su /system/bin
(Please NOTE: if you have upgraded to JB, you don't need to install superuser.apk, you can skip that "adb install superuser.apk" step)
adb install superuser.apk
adb shell
(Again you'll be taken to the shell)
#chmod 4755 /system/bin/busybox
#chmod 4755 /system/bin/su
# mount -o remount,ro -t rfs /dev/block/st19 /system
#exit
adb reboot
(Your tablet will be rebooted, And thus your tablet is Successfully rooted.)
You will see that now u have superuser.apk installed. Use an application like titanium backup which requires root access.
Also you can use "root checker application" to check whether you got root access or not...
If i have helped anyone please hit thanks botton...
And Please let me know whether you got root permission or not....
Enjoy your rooted tablet....:good:
thanks
Thanks for the method. I will try tonight and post here.
can you access fastboot ..?
i have rooted my z930 already , but anyways good work :good:
have u unlocked fastboot ..?
Works
It works. There is a typographical error where you've written busybin instead of busybox.
@jaideep, thanks for the correction, i'll edit it, actually it was late night when i had typed those steps, so just messed.
Anyway thanks again...
@sector1369, no i havent tried unlocking fastboot.
Anyone working on custom ROM on this tablet?
Anyone knows to fix WiFi and battery backup of this tablet?
Help Me Pls
I Have zync z909 plus , how Can I Root My Tablet. Superoneclick Is failed to root My Tab!!! Help Me Plsz!!
not worked ..
today i hav flashed JB again on my z930 ...
this time i decided to try your method to root...
all commands executed successfully but root permissions denied ...
NOT ROOTED
see ss
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sector1369 said:
today i hav flashed JB again on my z930 ...
this time i decided to try your method to root...
all commands executed successfully but root permissions denied ...
NOT ROOTED
see ss
Click to expand...
Click to collapse
after trying ur method i cant even root by other method...
i had to flash JB again...
install busybox?
Sector1369 said:
after trying ur method i cant even root by other method...
i had to flash JB again...
Click to expand...
Click to collapse
You don't have to install the busybox...and Do you have the Android SDK? because for me the adb.exe which came with the rar didn't work properly. The adb reboot leaves the cmd not responding forever. I had to use the adb with the Android SDK to get the rooting done...
unable to install usb drivers in zync z930
plz hepl me....m unable to install usb drivers of my z930 on window 7...i hv tried manually too but it dsnt accept those.
Hey Help Me How to Root zync z909 plus
Help Me How To Root My zync z 909 Plus
how to root zync z99
well ... i have Zync Z99 tablet. i want to root it. so i want to know if this same method will work on Z99 also or not .. please help me!
win32.tr0jan said:
You don't have to install the busybox...and Do you have the Android SDK? because for me the adb.exe which came with the rar didn't work properly. The adb reboot leaves the cmd not responding forever. I had to use the adb with the Android SDK to get the rooting done...
Click to expand...
Click to collapse
Install PdaNet software on your windows7 and let that software install adb drivers on your laptop/PC
ROOTED D2-1061g
arunal_123 said:
Hi everyone,
I have rooted my Zync z930 tablet with adb commands and just wants to let you know.
After going through lots of root methods i came to know the procedure.
Hope my method helps you.. :good:
I have collected the required drivers, files and uploaded them to 4shared.
Just Download the required files from http://www.4shared.com/rar/WiRHc5mG/Zync_Z930_Root_tools.html
And extract it.
To install adb drivers for your tablet, enable usb debugging in your tablet.
Go to settings ->developer option ->tick USB debugging and then connect your tablet to your PC with the usb cablet supplied with your tablet.
Now windows will show Failed to install drivers. just close it.
Go to desktop, right click on Computer -> manage ->device manager, you will see Z930 with an error symbol. Right click on it, update driver software.
->Browse my computer for driver software.
->let me pick from a list of devices on my computer.
->have disk
->select the location where you have extracted Zync Z930 Root tools.rar. Point on drivers. And click ok.
->it will show Android adb interface
click ok. it will show certificate warning. Just accept and let in install.)
So now you have installed your adb drivers....
Rooting your tablet
Now in the "Zync Z930 Root tools" folder, hold shift and right click.
"open command window here"
in the command window, type the following commands..
adb devices
(it will show the connected tablet with a different digits, thats normal)
adb root
(it will give you root permission)
adb shell
(U will be taken to Android shell)
(now in the shell, type the following commands, please take care of the space, comma and other signs and symbols carefully and execute)
(If you get $ sign, you still don't have root permission, if you have #, it means you have the root permission)
#mount -o remount,rw -t rfs /dev/block/st19 /system
#exit
(you'll be taken back)
adb push busybox /system/bin
adb push su /system/bin
(Please NOTE: if you have upgraded to JB, you don't need to install superuser.apk, you can skip that "adb install superuser.apk" step)
adb install superuser.apk
adb shell
(Again you'll be taken to the shell)
#chmod 4755 /system/bin/busybox
#chmod 4755 /system/bin/su
# mount -o remount,ro -t rfs /dev/block/st19 /system
#exit
adb reboot
(Your tablet will be rebooted, And thus your tablet is Successfully rooted.)
You will see that now u have superuser.apk installed. Use an application like titanium backup which requires root access.
Also you can use "root checker application" to check whether you got root access or not...
If i have helped anyone please hit thanks botton...
And Please let me know whether you got root permission or not....
Enjoy your rooted tablet....:good:
Click to expand...
Click to collapse
ROOT D2-1061g. These commands plus having the latest su, busybox, and supersu files in the same directory as adb.exe worked! My Digital 2 (D2) 1061g tablet is now rooted. Whoo hoo!
jmreyesiii said:
ROOT D2-1061g. These commands plus having the latest su, busybox, and supersu files in the same directory as adb.exe worked! My Digital 2 (D2) 1061g tablet is now rooted. Whoo hoo!
Click to expand...
Click to collapse
Its sound good that you have succeeded to get root...
Enjoy your device...
Sent from my HTC Vision using xda app-developers app
can u tell me how to flash zync table 99plus
can u tell me how to flash zync table 99plus
can tou make a video tuto plz
i can't open commande in xp

[Tool]i9505 Quick Flasher

Now next to the i9500 Quick Flasher there also is the i9505 Quick Flasher, just slight changes to make partitions match
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download:
www.broodplank.net/I9505-Quick-Flasher-1.0.zip
Created for a fail-safe flash operation of boot.img and recovery.img, all other partitions (currently only system) are experimental.
broodplank1337 said:
Now next to the i9500 Quick Flasher there also is the i9505 Quick Flasher, just slight changes to make partitions match
Download:
www.broodplank.net/I9505-Quick-Flasher-1.0.zip
Created for a fail-safe flash operation of boot.img and recovery.img, all other partitions (currently only system) are experimental.
Click to expand...
Click to collapse
Tried this, it cannot connect to my S4. Yes, I have debugging enabled, and yes my device is in mtp mode.
I get:
Running checks, please wait...
<<< I9505 USB Connection >>>
[ ] I9505 USB Connection
Your I9505 is not connected or unreachable! Please read the instructions for reference.
Snakefood said:
Tried this, it cannot connect to my S4. Yes, I have debugging enabled, and yes my device is in mtp mode.
I get:
Running checks, please wait...
<<< I9505 USB Connection >>>
[ ] I9505 USB Connection
Your I9505 is not connected or unreachable! Please read the instructions for reference.
Click to expand...
Click to collapse
I had some issues with usb as well when I was testing the tool out, but It was fixed after a while, its actually not the tool but the way of mounting usb on the i9505. I fixed it by replacing the adb.exe file with the latest one (which is also included in the zip tho). Can you please test for me if your able to get a normal adb shell? (open cmd window in the quickflasher dir and type "adb shell"), if it says device not found there is an issue with debugging mode. if not then you should test this and pls give me the info:
adb get-state (should return "device")
adb devices (should return a connected device)
If you get negative results here you should kill adb.exe (taskkill /f /im adb.exe for group kill) and try again.
If it does work pls enter:
adb root
adb remount
adb shell
and tel me what you see.
The usb mode is a struggle on the i9505.. I thought hey lets upgrade to CM so I will have mass storage mode.. but no way, only MTP and PTP... (I added the Mass storage option and forced it to be available on my private build, but it still doesn't work..)
Currently trying to find out how to permanently enable oldskool mass storage + adb.
broodplank1337 said:
I had some issues with usb as well when I was testing the tool out, but It was fixed after a while, its actually not the tool but the way of mounting usb on the i9505. I fixed it by replacing the adb.exe file with the latest one (which is also included in the zip tho). Can you please test for me if your able to get a normal adb shell? (open cmd window in the quickflasher dir and type "adb shell"), if it says device not found there is an issue with debugging mode. if not then you should test this and pls give me the info:
adb get-state (should return "device")
adb devices (should return a connected device)
If you get negative results here you should kill adb.exe (taskkill /f /im adb.exe for group kill) and try again.
If it does work pls enter:
adb root
adb remount
adb shell
and tel me what you see.
The usb mode is a struggle on the i9505.. I thought hey lets upgrade to CM so I will have mass storage mode.. but no way, only MTP and PTP... (I added the Mass storage option and forced it to be available on my private build, but it still doesn't work..)
Currently trying to find out how to permanently enable oldskool mass storage + adb.
Click to expand...
Click to collapse
My results:
C:\Windows\system32>cd \
C:\>cd s4 root
C:\S4 root>cd qflash
C:\S4 root\qflash>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: more than one device and emulator
C:\S4 root\qflash>adb get-state
unknown
C:\S4 root\qflash>adb devices
List of devices attached
12138fc0 device
emulator-5554 offline
C:\S4 root\qflash>adb root
error: more than one device and emulator
C:\S4 root\qflash>
Snakefood said:
My results:
C:\Windows\system32>cd \
C:\>cd s4 root
C:\S4 root>cd qflash
C:\S4 root\qflash>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: more than one device and emulator
C:\S4 root\qflash>adb get-state
unknown
C:\S4 root\qflash>adb devices
List of devices attached
12138fc0 device
emulator-5554 offline
C:\S4 root\qflash>adb root
error: more than one device and emulator
C:\S4 root\qflash>
Click to expand...
Click to collapse
ah so you have the emulator in there as well.. thats the problem. to bypass the emulator use:
adb -d
for example adb -d shell or adb -d get-state
do you have an AVD emulator running currently?
broodplank1337 said:
ah so you have the emulator in there as well.. thats the problem. to bypass the emulator use:
adb -d
for example adb -d shell or adb -d get-state
do you have an AVD emulator running currently?
Click to expand...
Click to collapse
What emulator do I have, I've only used the files in your download, as far as I know. Any way to check / remove?
Edit: I had bluestacks installed a while back, but uninstalled it, could this have left some crap behind after it?
Snakefood said:
What emulator do I have, I've only used the files in your download, as far as I know. Any way to check / remove?
Click to expand...
Click to collapse
Hmm the emulator that comes with android sdk, is afaik the only one who can correspond with adb, but it would be odd if you ran it all the time.
check taskmgr, and look for emulator.exe/java.exe, to be sure also kill adb.
You can check if there is an existing emulator if you start AVD manager (if you don't have android sdk at all then its really strange )
broodplank1337 said:
Hmm the emulator that comes with android sdk, is afaik the only one who can correspond with adb, but it would be odd if you ran it all the time.
check taskmgr, and look for emulator.exe/java.exe, to be sure also kill adb.
You can check if there is an existing emulator if you start AVD manager (if you don't have android sdk at all then its really strange )
Click to expand...
Click to collapse
I didn't have sdk installed; I installed it and ran avd manager, doesn't show any installed.
when I run adb -d shell I get [email protected]:/ $
Snakefood said:
I didn't have sdk installed; I installed it and ran avd manager, doesn't show any installed.
when I run adb -d shell I get [email protected]:/ $
Click to expand...
Click to collapse
Ok the output is good. ill add a function to the tool to force adb usb connection
for the meanwhile you can use:
(put boot.img in adb dir)
adb -d push boot.img /sdcard/boot.img
adb -d shell su -c 'dd if=/sdcard/boot.img of=/dev/block/mmcblk0p20'
adb -d shell reboot
broodplank1337 said:
Ok the output is good. ill add a function to the tool to force adb usb connection
for the meanwhile you can use:
(put boot.img in adb dir)
adb -d push boot.img /sdcard/boot.img
adb -d shell su -c 'dd if=/sdcard/boot.img of=/dev/block/mmcblk0p20'
adb -d shell reboot
Click to expand...
Click to collapse
Do I rename my recovery.img from cwm to boot.img for the above, or is this for a different process?
Snakefood said:
Do I rename my recovery.img from cwm to boot.img for the above, or is this for a different process?
Click to expand...
Click to collapse
boot.img = mmcblk0p20
recovery.img = mmcblk0p21
the name of the .img doesn't matter but the partition is important.
Ahh, looking at your image, this now makes sense, I can see the destination partition names as you describe..
Well have a go at this later, unless you plan to release an update later today?
Sent from my Nexus 7 using xda app-developers app
Edit: couldn't get this working, so I just flashed using odin. Thanks for trying to get resolved tho.
Odin is the tool for me, no need more than that.
broodplank1337 said:
ah so you have the emulator in there as well.. thats the problem. to bypass the emulator use:
adb -d
for example adb -d shell or adb -d get-state
do you have an AVD emulator running currently?
Click to expand...
Click to collapse
Hi brood,
just stumbled upon this thread and read about Snakefood's problem.
Although he worked around the error by using Odin I want to give you a hint regarding this specific problem:
he obviously has an adb device installed called emulator-5554 but which is offline. He already gave himself the correct answer:
"I had bluestacks installed a while back, but uninstalled it, could this have left some crap behind after it?"
My diagnose is: yes, BlueStacks definitely leaves a lot of crap behind and does NOT uninstall cleanly. I tested it once and I saw myself compelled to restore an older windows image which I made BEFORE I installed BlueStacks on my windows machine.
BTW: BlueStacks is an Android emulator for Windows but a piece of *%$~#!!! crap, but that's just my humble opinion.
And BlueStacks uses such an adb emulator device entry although I'm not sure if it was called like that. But BlueStacks is not the only Android emulator and most probably other programs of this kind create such an adb entry as well.
skywalker01 said:
Hi brood,
just stumbled upon this thread and read about Snakefood's problem.
Although he worked around the error by using Odin I want to give you a hint regarding this specific problem:
he obviously has an adb device installed called emulator-5554 but which is offline. He already gave himself the correct answer:
"I had bluestacks installed a while back, but uninstalled it, could this have left some crap behind after it?"
My diagnose is: yes, BlueStacks definitely leaves a lot of crap behind and does NOT uninstall cleanly. I tested it once and I saw myself compelled to restore an older windows image which I made BEFORE I installed BlueStacks on my windows machine.
BTW: BlueStacks is an Android emulator for Windows but a piece of *%$~#!!! crap, but that's just my humble opinion.
And BlueStacks uses such an adb emulator device entry although I'm not sure if it was called like that. But BlueStacks is not the only Android emulator and most probably other programs of this kind create such an adb entry as well.
Click to expand...
Click to collapse
Hi Skywalker.
Long time no see . Anyways, OT. I have installed BlueStacks once (in the alpha or beta phase I believe) and I don't remember much of it but I do remember that it was crap idd. Also that it leaves "traces" (if you call adb a trace xd, more like a fail uninstall ) is very lame.. and causing problems for people who are not 100% familiar with adb and its daemon.
The AVD Emulator from the SDK may lag a bit but atleast it doesn't interfere with adb :silly:
Great tool broodplank1337, well done mate this will save ppl from making stupid mistakes
dublinz said:
Great tool broodplank1337, well done mate this will save ppl from making stupid mistakes
Click to expand...
Click to collapse
Thanks ^^, I think that is true hehe, using 'dd' to flash images isn't for the absolute beginner idd ;p
Hi guys,
If you need me to assist more with ahh testing just let me know. Is there an uninstaller to remove what bluestacks left behind, or is the Windows disc the only definite uninstaller
Sent from my GT-I9505 using xda app-developers app
Snakefood said:
Hi guys,
If you need me to assist more with ahh testing just let me know. Is there an uninstaller to remove what bluestacks left behind, or is the Windows disc the only definite uninstaller
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
You should first look in msconfig (start > run > msconfig) at the startup tab and look if there is any startup item from bluestacks.
If there is nothing there look in services.msc (start > run > services.msc) and check for any blue stacks service, and if there is any, disable it.
Next to that you can also use HijackThis (http://sourceforge.net/projects/hjt/) to find startup items. hope it helps
Hey Brood,
See you're doing great work here on the S4 section.:good:
I'm missing your input in the S+ section unfortunatly:crying:

[UNIVERSAL GUIDE] Root Any Android Device Manually !

THIS GUIDE NO LONGER WORKS BECAUSE ANDROID ISN'T WHAT IT USED TO BE BACK IN 2013-14.
PLEASE STOP WASTING TIME TO FOLLOW THIS OBSOLETE METHOD 1. PLEASE REFER ONLY TO METHOD 3​
The Ultimate Guide to Rooting any Android Device Manually !!!!​
Wanting to ROOT Your Phone but can't do Because Of No rooting Guides or want to learn to root any device ? Then , This Guide Is For YOU
OK So lets start....
**What You Need**
1.Your Unrooted Android Device.
2.ADB Drivers Installed On Your PC. If you Don't Have Download From Here :
Code:
adbdriver.com/‎
3. The Most Inportant Root Kit Made By Me (N'ayam Amarsh'e) - Download From The Attachment.
4.Strength And Courage 'Coz Rooting Voids Your Warranty... If You have a samsung device then Don't Worry Your warranty is gone forever... But if you own any other, maybe you can void it or maybe......
I've Written Android Device as ADV to make it more easy....
**Steps**
So you have the adb drivers installed let's go....
1. Open The root kit by Extracting The Rootkit with WinRAR....
2.Turn 'USB DEBUGGING' 'ON' in your ADV...
3. Connect your ADV to Your PC...
4.In the root kit Open Cmd.exe File ... [ IF YOU CAN'T OPEN CMD, GOTO C:/WINDOWS/SYSTEM32/ COPY CMD .EXE TO YOUR ROOTKIT FOLDER]
5. In CMD window Type the following command...
Code:
->adb devices *Your device will get listed in the window if it doesn't check your adb drivers or if you have followed the steps properly...
->adb push busybox /data/local/tmp
->adb push su /data/local/tmp
->adb push Superuser.apk /data/local/tmp
If you Succeed Move On ...
6.Then You need Root Shell Type :
Code:
adb shell
Note that you see a "$" sign in the command prompt. That means you are not in 'su' shell.
7.Next run the following commands in the shell to change permissions and get some limited privileges for the Superuser files:
Code:
->chmod 6755 /data/local/tmp/su
->chmod 755 /data/local/tmp/busybox
->chmod 644 /data/local/tmp/Superuser.apk
{Note}The names of the files are case sensitive!
8.Done ? Now You need to open a copy of linux which has nautilus... So enter your linux (I recommend using ubuntu 11.4) and type in the terminal (ctrl+alt+T)
Code:
->sudo nautilus
this will open nautilus with root privileges...
You can just boot it from USB so no hassle of installing it... http://www.cyberciti.biz/tips/download-ubuntu-linux-11-04-iso-cd-dvd-images-natty-narwhal.html
Having your ADV connected with USB to PC switch it off and put it in download/recovery mode...
superlouro said:
DEVICE OFFLINE?
! SOLUTION ! (click me)
Click to expand...
Click to collapse
9.In The Exploring Window navigate to
Code:
/data/local/tmp
and move/cut 'su' and 'busybox' to
Code:
/system/bin
...
10.From the tmp Folder you went earlier Move/cut 'Superuser.apk' to
Code:
/system/app
11.Now Reboot You ADV ... Congrats ! You're now ROOTED !
Many Users Are Having Problem with This Method, If you can't do the method 1. Try Method 2.
METHOD 2
PLEASE DON'T ASK ME ABOUT THIS METHOD, THIS IS JUST FOR A TRY, MY BROTHER FOUND THIS METHOD TO BE WORKING, I HAVEN'T TRIED IT YET!
This is linux based method, It's quite easy if you follow every step correctly...
You need to download psneuter, https://github.com/tmzt/g2root-kmod/tree/master/scotty2/psneuter
When you have it execute the following...
Code:
adb devices
Code:
adb push psneuter /data/local/tmp
This will copy the file to your device and now we'll execute it..
Code:
adb shell
cd /data/local/tmp
chmod 777 psneuter
./psneuter
Now You'll see
Code:
adb kill-server
adb devices
adb shell
now # will appear in place of $, or after typing $su.
Code:
# mount -o remount,rw -t rfs /dev/block/st19/system
# exit
$ adb push busybox /system/bin
$ adb push su /system/bin
$ adb install Superuser.apk
$ adb shell
# chmod 4755 /system/bin/busybox
# chmod 4755 /system/bin/su
# mount -o remount,ro -t rfs /dev/block/st19/system
# exit
$ adb reboot
Now your device will reboot and you can see SuperUser App in your app drawer...
----------------------------------------------------------------------
METHOD 3
There is no chance of the phone not getting rooted with my method but If you don't want to do the above methods, Try these, I'm pretty sure they will root your device with ease...
1. Framroot App [Not On Google Play]-http://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
2.KingoRoot App - www.kingoapp.com
3.One Click Root Free/Pro (My Favorite app, roots many devices with No-Brick Guarantee) - www.oneclickroot.com
4.Root Master App - forum.xda-developers.com/showthread.php?t=2672150
5.z4root App - http://forum.xda-developers.com/showthread.php?t=833953
6.Easy rooting toolkit App-http://forum.xda-developers.com/showthread.php?t=1321582
7.Vroot Software - http://vrootdownload.info/ or http://www.mgyun.com/en/getvroot
8.SRSRoot Software - http://www.srsroot.com
9.Unlock Root Software - http://www.unlockroot.com/download.html
10.Universal Androot App - forum.xda-developers.com/attachment.php?attachmentid=391774
ONLY FOR MTK DEVICES- MTK DROID TOOLS- http://forum.gsmhosting.com/vbb/f60...3-2014-imei-repair-rooting-tool-more-1780568/
HOPE THESE WILL DO....
Press Thanks To appreciate me to Work On Other Guides And Roms....
Your Appreciation Is Needed...
And This GUIDE IS Originally By N'ayam Amarsh'e
I have any error. Device is offline.
---------- Post added at 09:13 AM ---------- Previous post was at 09:02 AM ----------
uukasz92 said:
I have any error. Device is offline.
Click to expand...
Click to collapse
Problem solved i download another adb drivers and work fine
In /UserData/local/tmp i only have one file "directory" and nothing else. It's look like something block the data folder.
uukasz92 said:
In /UserData/local/tmp i only have one file "directory" and nothing else. It's look like something block the data folder.
Click to expand...
Click to collapse
that means you have not properly pushed the files into the directory.... Try installing adb drivers again and do the same steps...Good luck
When you open cmd just type ' adb devices' if your device gets listed then you can start if it doesn't check your drivers...
After uinstall all adb drivers and phone drivers comand prompt shows me a device code and status ofline. At the begining i install atached to therad package of adb drivers. But lately some where in Internet I find some update package of adb drivers. And there was the same sort of files like in your package. I put them there and replace and after that adb shows the device is working and status is online but your guide still does not work. Question is where is real problem ? I checked and Debug Mod is on, drivers are installed.
Try this , download android commander and try to copy the busybox , su and superuser to data/local/tmp
N'ayam Amarsh'e said:
Try this , download android commander and try to copy the busybox , su and superuser to data/local/tmp
Sent from my Mi-492 using xda app-developers app
Click to expand...
Click to collapse
I used the same files in android commander because program can't finde my device to.
Which phone you have.... Try to download its original drivers this might help...
I using Samsung Galaxy Grand Neo (GT-I9060) Jelly Bean 4.2.2
Now is working. But how to move "su" and busybox into system/bin ? Android commander says " You need root to do this." when i try to copy does files into system/bin. Folders are protected and I dont have premission to do anything with them.
uukasz92 said:
I using Samsung Galaxy Grand Neo (GT-I9060) Jelly Bean 4.2.2
Now is working. But how to move "su" and busybox into system/bin ? Android commander says " You need root to do this." when i try to copy does files into system/bin. Folders are protected and I dont have premission to do anything with them.
Click to expand...
Click to collapse
Sorry I forgot that Android Commander works only for rooted phones... Silly Me...
OK you will need to do it with Droid Explorer
OR
linux and in the linux you'll have to type 'sudo nautilus' it'll open it with root privilages...
N'ayam Amarsh'e said:
Sorry I forgot that Android Commander works only for rooted phones... Silly Me...
OK you will need to do it with Droid Explorer
OR
linux and in the linux you'll have to type 'sudo nautilus' it'll open it with root privilages...
Click to expand...
Click to collapse
And in your guide need little correct. In step 9 should be /data/local/tmp not /UserData/local/tmp. Does are two diffrent folders. And before I think I do something wrong when all files be already on right place
Droid Explorer cant change folders premission too. Command prompt says : Read-only drirectory. I don't know what to do now.
uukasz92 said:
And in your guide need little correct. In step 9 should be /data/local/tmp not /UserData/local/tmp. Does are two diffrent folders. And before I think I do something wrong when all files be already on right place
Click to expand...
Click to collapse
thanks.... Guide is updated now
Good 1 helped alot
harmeet singh said:
Good 1 helped alot
Click to expand...
Click to collapse
I am happy that I helped....
Hi! First thank you for that guide. I rooted several devices but with a noname(10.1" A10 dual core) china tablet I have some problems so I hope your solution works.
I have some problems/questions:
1. Step 5: Are you sure it's:
Code:
adb push su /data/local/tmp
instead of
adb push su /data/local/tmp[B][SIZE="5"]/[/SIZE][/B]
I'm currently not able to look at the data folder but if I change the directions e.g to /test/local/tmp it just creates a "tmp" file and overwrites the file with every push command.
2. Step 6: If it's a $ it's not rootet, what should be there if it's rooted? I have a # there. Rootchecker says it's rooted since the beginning, but I cant access with superuser/supersu etc.
3. Step 8 doesn't work. I use a virtual box with ubuntu 13.10(Stinson: new is always better?) for the first time. With "sudo nautilus" I get the message that root access is not granted(failed to register client). I used "gksudo nautilus" instead... does that matter?
4. I can't connect my device to the virtual box. I tried to add the usb device but didn't work. USB Developer Android[0223] is in virtual box connected. However, I dont know where to find it in ubuntu. I'm a ubuntu noob sorry :/
5. Is there another way to get rw permissions?
Thanks in advance :good:
thankyou for information i think is hard for me
Very nice, ty
Humbel said:
Hi! First thank you for that guide. I rooted several devices but with a noname(10.1" A10 dual core) china tablet I have some problems so I hope your solution works.
I have some problems/questions:
1. Step 5: Are you sure it's:
Code:
adb push su /data/local/tmp
instead of
adb push su /data/local/tmp[B][SIZE="5"]/[/SIZE][/B]
I'm currently not able to look at the data folder but if I change the directions e.g to /test/local/tmp it just creates a "tmp" file and overwrites the file with every push command.
2. Step 6: If it's a $ it's not rootet, what should be there if it's rooted? I have a # there. Rootchecker says it's rooted since the beginning, but I cant access with superuser/supersu etc.
3. Step 8 doesn't work. I use a virtual box with ubuntu 13.10(Stinson: new is always better?) for the first time. With "sudo nautilus" I get the message that root access is not granted(failed to register client). I used "gksudo nautilus" instead... does that matter?
4. I can't connect my device to the virtual box. I tried to add the usb device but didn't work. USB Developer Android[0223] is in virtual box connected. However, I dont know where to find it in ubuntu. I'm a ubuntu noob sorry :/
5. Is there another way to get rw permissions?
Thanks in advance :good:
Click to expand...
Click to collapse
For Your First Answer You Need not to worry /tmp and /tmp/ are the same...
2.Have you tried typing 'adb shell' then ' su ' if yes there's your solution.... If not then you have problem with su binary or busybox....
3.You have an Ubuntu 11.4 .iso file so burn it to a blank disk and boot your live disk .... It should be all right then...
4.Answer in 3....
5.Answer in 3....
6.Press Thanks if I helped...
bro im confused wt to do exactly in that sudo ... step pls give a brief explaination

Categories

Resources