[UNIVERSAL GUIDE] Root Any Android Device Manually ! - Upgrading, Modifying and Unlocking

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

Related

[MOD] 3-Click QuickTempRoot TerminalMOD :/

Alright all,
I know there's another thread about "easier" method, but this is easiest for me. 3-Clicks after installation.
I was really tired of typing the same crap over and over after rebooting just to get my temproot back to do more testing/playing.
So I redeveloped this to be quicker/easier upon reboot. Mainly I altered the Term app to be have a scripted start-up on the 1st 3 launches.
I also updated the su/Superuser combo with ChainDD's latest stuff.
Here's how it works, after it's installed.
3ClickTempRooter said:
1) You run the terminal app once, wait a few seconds and it disappears.
2) You run the terminal again, wait for it to FC.
3) You run the terminal a final time and receive root.
Click to expand...
Click to collapse
Now on each reboot, it will be simply 3-clicks (running terminal app 3 times).
Finally ... any executable script placed in /data/local/tmp will be in the path of the new terminal mod. This makes running other scripts very easy.
Installation
Download the attached QuickTempRooter.zip and place it in a directory and unpack it.
Turn on USB debugging and install through adb ...
Here's the adb installation snippet ...
Code:
adb kill-server
adb push su /sdcard/su
adb push Superuser.apk /sdcard/Superuser.apk
adb push busybox /data/local/tmp/busybox
adb push rage /data/local/tmp/rage
adb push root /data/local/tmp/root
adb shell chmod 0755 /data/local/tmp/busybox
adb shell chmod 0755 /data/local/tmp/rage
adb shell chmod 0755 /data/local/tmp/root
adb shell 'pm uninstall com.android.term'
adb install Term.apk
Has made my life wayyy easier when playing with this phone while we wait for the real-deal!!!
Hope you enjoy!
NOTES
If you get a permission denied on the ''adb shell 'pm uninstall com.android.term' '' ... this is normal if you don't have a terminal already installed or have an alternate terminal app (using a namespace other than com.android.term.
If you have another Terminal App installed, you may want to uninstall it first, to avoid confusion.
Also, you may need to reboot after the initial installation for it to work properly!
ummmmm.....Enomther??
Did you get a G2 already?
Great to see you helping out with this
Great to see you here man! Trying this now can't wait to get themes rolling once we get permanent root!
Sent from my T-Mobile G2 using XDA App
I get a permission denied response when running "adb shell 'pm uninstall com.android.term'"
burton14e7 said:
I get a permission denied response when running "adb shell 'pm uninstall com.android.term'"
Click to expand...
Click to collapse
If you didn't already have a terminal app installed that error is normal. Also you may need to reboot once after the initial installation for it to work properly.
~enom~
Thank you sir. Appreciate the goodness.
damn i wish i could hit the thanks button
Thanks man good to have you on the G2 too
Sent from my T-Mobile G2
enomther said:
If you didn't already have a terminal app installed that error is normal. Also you may need to reboot once after the initial installation for it to work properly.
~enom~
Click to expand...
Click to collapse
good to see you on this side.... i have terminal app installed rebooted but still get this denied when running adb shell 'pm uninstall com.android.term
Edit: fixed it uninstalled the Android Terminal E,ulator and just ran the setup now have root thanks
Thank You..
Enom.. (sigh)
Welcome Home..
thank u so much now i can wireless tether. easiest root ever
Sorry, this is my first Android. I came from WM and I was pretty good with it.
I've searched XDA, Youtube, and web to ADB and SDK. I've downloaded it and it's installed. The only thing I don't get is when you said to
"Download the attached QuickTempRooter.zip and place it in a directory and unpack it."
You mean place the extracted files into the sd card correct? That's why the command is "adb push su /sdcard/su".
ddgarcia05 said:
Sorry, this is my first Android. I came from WM and I was pretty good with it.
I've searched XDA, Youtube, and web to ADB and SDK. I've downloaded it and it's installed. The only thing I don't get is when you said to
"Download the attached QuickTempRooter.zip and place it in a directory and unpack it."
You mean place the extracted files into the sd card correct? That's why the command is "adb push su /sdcard/su".
Click to expand...
Click to collapse
No, he means on your PC. You are running adb to push files contained in the zip to your phone.
HamNCheese said:
No, he means on your PC. You are running adb to push files contained in the zip to your phone.
Click to expand...
Click to collapse
So they go into the tools folder? Damn. I think I've in over my head here.
Like this?
If you have better terminal, you can also add the rage and root to specific keys.
At this command I'm getting told "failed to copy 'su' to '/sdcard/su': Read-only file system"
adb push su /sdcard/su
kevdawg said:
At this command I'm getting told "failed to copy 'su' to '/sdcard/su': Read-only file system"
adb push su /sdcard/su
Click to expand...
Click to collapse
Unplug then plug ur phone back in then try again also make sure u are in usb debug mode
Good work, Temp root in like 5 seconds
Quick question, ok I was able to get root for a few mins, then it went away I guess I have to have the terminal always open or ignore so my taskiller doesnt terminated it?
Don't use task killers. (IMHO)
But I tend to have to reboot every once in a while to keep root in tacked within terminal but all my apps seem to stay with su permissions until reboot (or sometimes 12 hours)

[Q] youtube app porting help!!! please!!!

can someone please post DETAILED isntructions to put froyo or gingerbread youtube app thing on samsung epic 4g. ive tried so many time and cant do it. and i delted the stock youtube app with titanium but cant install the other app and i dont wanna pay for root explorer cuz idk if its gonna help at all. i tried using the cmd promt but it says permission denied everytime and it also says adb is not recognized as an internal storage.. PLEASE SOMEONE HELP MEEE I DONT HAVE A YOUTUBE AP AT ALL NOW!!!!!
betterment66 said:
can someone please post DETAILED isntructions to put froyo or gingerbread youtube app thing on samsung epic 4g. ive tried so many time and cant do it. and i delted the stock youtube app with titanium but cant install the other app and i dont wanna pay for root explorer cuz idk if its gonna help at all. i tried using the cmd promt but it says permission denied everytime and it also says adb is not recognized as an internal storage.. PLEASE SOMEONE HELP MEEE I DONT HAVE A YOUTUBE AP AT ALL NOW!!!!!
Click to expand...
Click to collapse
The new YouTube.apk just needs to be placed in '/system/app'. What I did was remove the original YouTube.apk and put the new one in its place and voila. Here is the method adapted for Windows (I think it's all right for Windows). This is also assuming you rooted with a one click root that included the remount script and that you have adb on your computer (the one click rooter should have adb included with it).
1. in the cmd prompt, go to the folder where you have adb and type:
Code:
adb.exe shell
2. inside shell:
Code:
$ su
# remount rw
# mkdir /sdcard/backup
# cp /system/app/YouTube.apk /sdcard/backup
# rm /system/app/YouTube.apk
# exit
$ exit
3. now in the cmd prompt again:
Code:
adb.exe push \path\to\YouTube.apk /system/app
4. Reboot the phone.
gremlyn1 said:
The new YouTube.apk just needs to be placed in '/system/app'. What I did was remove the original YouTube.apk and put the new one in its place and voila. Here is the method adapted for Windows (I think it's all right for Windows). This is also assuming you rooted with a one click root that included the remount script and that you have adb on your computer (the one click rooter should have adb included with it).
1. in the cmd prompt, go to the folder where you have adb and type:
Code:
adb.exe shell
2. inside shell:
Code:
$ su
# remount rw
# mkdir /sdcard/backup
# cp /system/app/YouTube.apk /sdcard/backup
# rm /system/app/YouTube.apk
# exit
$ exit
3. now in the cmd prompt again:
Code:
adb.exe push \path\to\YouTube.apk /system/app
4. Reboot the phone.
Click to expand...
Click to collapse
ok i get to remount rw but the when i type in the nect code it says
mkdir falied for /sdcard/backup read-only filesystem
I install it using terminal emulator.
All I do is type
Su
#rm /system/app/YouTube.apk
#cp /sdcard/DirectoryWithTheYoutubeApp/YouTube.apk /
system/app
Or after you rm, just use the "My Files" app and go on your sdcard and click YouTube.apk and it'll install and work fine. But remember to sign out of youtube before you close it by going to your page and clicking sign out or else it'll keep force closing after you start it up.
I hope I helped...
Sent from my SPH-D700 using XDA App
you guys are gonna freaking kill me. ALL THE TROUBLE I WAS HAVING WAS BECAUSE I HAD MY SDCARD MOUNTED THE WHOLE TIME I WAS TRYING TO DO THIS THE MINUTE I TRIED IT WITHOUT IT BEING MOUNTED IT WORKED...IM SO DUMB!!!!! LOL BUT THANKS FOR THE HELP ALL OF U!!!!!! U GUYS ROCK!!!! N SO DOES THE NEW UTUBE APP .....BTW I UNDERSTAND UR NOT SUPPOSED TO SIGN IN TO IT RIGHT???
I just uninstalled the original, put the modded youtube.apk in the SDX backup folder and installed (restored) it with SDX stock app remover. Simple, fast and no typing required.
Glad you got it worked out though.
me 2!!! this app rocks
Glad it's working! Having the SD card mounted while trying to adb is a common mistake and always a good first troubleshooting check.

[Q] HELP!!! Lcd Density Problem !!

Hi everybody,
Sorry for my bad english, i'm italian,
I've a problem with my a100 with stock ics. yesterday i've rooted it and i've installed lcd density modder. now, i've do a mistake and saved the dpi instead of temp apply. after the reboot the home won't start cause it freeze. i can only have access to settings i can't access the lcd density app. i've tried to reset to factory but it's still the same. Can anyone help me ?
thanks
Use adb to pull build.prop from /system use some text editor to open it and find this line ro.sf.lcd_density= and change it to ro.sf.lcd_density=160 then reboot.
The exact commands are :
Code:
adb pull /system/build.prop build.prop
adb push build.prop /system/build.prop
adb shell reboot
thank you so much, resolved
can you explain how to pull it up into the text editor i'm afraid i have the same problem and found this thread i enter the pull command and recieve this in cmd prompt:
C:\Users\Owner>adb pull /system/build.prop build.prop
224 KB/s (1841 bytes in 0.008s)
and now i'm lost.....
ilovemywife269 said:
can you explain how to pull it up into the text editor i'm afraid i have the same problem and found this thread i enter the pull command and recieve this in cmd prompt:
C:\Users\Owner>adb pull /system/build.prop build.prop
224 KB/s (1841 bytes in 0.008s)
and now i'm lost.....
Click to expand...
Click to collapse
Open your editor and then open build.prop in it.
Or name it build.txt then edit it then save as build.prop.
Tapatalked from my Galaxy S II.
pio_masaki said:
Open your editor and then open build.prop in it.
Or name it build.txt then edit it then save as build.prop.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
i'm a noob here i need more details on how exactly i should go about getting it opened
ilovemywife269 said:
i'm a noob here i need more details on how exactly i should go about getting it opened
Click to expand...
Click to collapse
Open whatever editor you want, then click on help for how to open documents in that program.
Otherwise, file>open>whereveryousavedit/build.prop
Then file>save.
Edit: for windows I suggest notepad++
Tapatalked from my Galaxy S II.
pio_masaki said:
Open whatever editor you want, then click on help for how to open documents in that program.
Otherwise, file>open>whereveryousavedit/build.prop
Then file>save.
Edit: for windows I suggest notepad++
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
ok i didn't save it anywhere how do i save it?
ilovemywife269 said:
ok i didn't save it anywhere how do i save it?
Click to expand...
Click to collapse
C:\Users\owner\build.prop from what you posted before.
Tapatalked from my Galaxy S II.
pio_masaki said:
C:\Users\owner\build.prop from what you posted before.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
ok now i get:
C:Users\Owner>adb push build.prop /system/build.prop
failed to copy 'build.prop' to '/system/build.prop' : Read-only file system
what am i doing wrong shouldn't it be in a Read-Write system?
ilovemywife269 said:
what am i doing wrong shouldn't it be in a Read-Write system?
Click to expand...
Click to collapse
adb remount
adb push build.prop /system/build.prop
Edit: if that fails try this:
adb shell mount -o remount,rw -t ext4 /dev/block/mmcblk0p3 /system
mount: permission denied (are you root?)
i was rooted before i factory reset i went through the adb root method which is basicaly how i achieved root to begin with except i used a cmd prompt terminal app and did it all on my tablet and now i'm not sure i never had a "full" root idk how to explain that but it told me i was rooted and could run root apps and such but it still limited me on a few things if this helps i have
"bootloader 0.03.06-ics (unlocked)"
it came stock with gb or honeycomb i had to find a .zip file to get ics
now i've tried to adb root again and failed i'm not sure why...
ilovemywife269 said:
mount: permission denied (are you root?)
i was rooted before i factory reset i went through the adb root method which is basicaly how i achieved root to begin with except i used a cmd prompt terminal app and did it all on my tablet and now i'm not sure i never had a "full" root idk how to explain that but it told me i was rooted and could run root apps and such but it still limited me on a few things if this helps i have
"bootloader 0.03.06-ics (unlocked)"
it came stock with gb or honeycomb i had to find a .zip file to get ics
now i've tried to adb root again and failed i'm not sure why...
Click to expand...
Click to collapse
OK time for info then. What ROM are you on? What recovery? Why did you use a method other then one intended for the a100? Being rooted but limited is probably due to missing or bad busy box installation.
Tapatalked from my A100 - Kuroikaze B3
i used an update zip for what i believed to be a stock ics rom and i rooted with a method that was intended for the a100:
Download the su binary from here.
Hook your device to the computer via USB cable.
Copy the su binary file to /mnt/sdcard/ on your tablet.
Open a command prompt on your Windows computer.
Change directory to where ADB is located. (This is usually the /tools or /platform-tools directory inside the Android SDK installation directory.)
Type in the following commands at the terminal (press Enter after each command):
adb shell /system/bin/cmdclient ec_micswitch ‘`mount -o remount,rw /system`’
adb shell /system/bin/cmdclient ec_micswitch ‘`cat /mnt/sdcard/su >/system/xbin/su`’
adb shell /system/bin/cmdclient ec_micswitch ‘`chmod 6755 /system/xbin/su`’
Install the Superuser app from the Android Market.
i used this method but i used terminal emulator on my tablet i didn't use adb
here is the update zip i used for ics- this is the error i get trying to attach the zip file:
The connection was reset
The connection to the server was reset while the page was loading.
The site could be temporarily unavailable or too busy. Try again in a few
moments.
If you are unable to load any pages, check your computer's network
connection.
If your computer or network is protected by a firewall or proxy, make sure
that Firefox is permitted to access the Web.
Use the script as intended. From the PC. If you go running them on the tab itself you may have missed one somewhere.
You can't attach a file that large to a post.
Tapatalked from my Galaxy S II.
when i enter the first shell command it denies me and asks me if i am root......
ilovemywife269 said:
when i enter the first shell command it denies me and asks me if i am root......
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=23285307
Use this method.
Tapatalked from my Galaxy S II.
i tried both ics rooting methods both of which told me they achieved root however i am still denied permission to remount
with my moto phones i've always been able to flash back to stock.....or flash back to life anyways is there a way to flash this tablet?

Videocon A20 How to root

Hi Friends,
I recently bought a Videocon A20 - with Android 2.3.5, and I have been unable to ROOT it.
I have tried with One Click, Un-Root, Adb-shell etc. Nothing seems to work.
It was so easy to ROOT with a Samsung Galaxy Y also my Karbonn A9+ (this was much easier)
But this Videocon V20 is more stuborn than a MULE ........:crying:
Anyone out there Can help me ?
PS: I have been able to get ADB Shell access and I get a "$" prompt and not "#" prompt, this means that - su will not work.
All the above applications are able to push - superuser application however the phone is not rooted.
CAN SOMEONE PLEASE HELP ME ????
Videocon A20
I am Having the same problem.
please tell me if you know the solution anytime.
Try universal gingerbread root method...
Sent from my GT-I5510 using xda premium
Have Videocon A20 same problem
Hi I also tried all the procedures from internet like SuperOneClick, Gingerbreak, etc........................ But No rooting done\
Please help me
My mobile getting switched off often due sys apps loading in to ram without my knowledge
I want to uninstall them
Please help me to root my Videocon A20
Thanks
[email protected]
Download z4root.apk(google it!!!) And extract the apk with your fav. Decompression tool.Go to res>raw
And you will find a file named rageitagainstthecage .
Now make a folder in C drive of any desired name (make sure that folder name doesn't contain space) and place the above file in this folder.
Now path should look like this:
C:\(foldername)\ rageitagainstthecage
Now attach your phone to pc with adb enabled and start command prompt and type the following commands and press enter after each command:
cd ..
cd ..
cd yourfoldername
adb push rageitagainstthecage /data/tmp/local/
adb shell "chmod 775 /data/tmp/local/rageitagainstthecage"
adb shell "./data/tmp/local/ rageitagainstthecage"
Now the exploit will run and after the completion of exploit,restart your phone and again attach the phone to pc and the you can push the su binary and app in following way(assuming that you have su and Superuser.apk in your folder located in c drive)
adb shell "mount -o remount rw /system "
adb push su /system/bin/
adb push Superuser.apk /system/app/
adb shell "chmod 775 /system/bin/su"
adb shell "chmod 775 /system/app/Superuser.apk"
Now time to check if ir worked
adb shell
su
If you see "#" instead of "$", your phone is rooted!!!!
BEST OF LUCK!!!!
Sent from my ZTE-BLADE using xda app-developers app
Did anyone tried it out?
i will try as soon as i get a20 frm my brother.....
Sent from my GT-I5510 using xda premium
AshuGite said:
i will try as soon as i get a20 frm my brother.....
Try this tool by binary...google it..
www.gleescape.com/wp-content/uploads/2012/12/Root_with_Restore_by_Bin4ry_v17.zip
http://techass.wordpress.com
Click to expand...
Click to collapse
nt working... :'(
[email protected] said:
Download z4root.apk(google it!!!) And extract the apk with your fav. Decompression tool.Go to res>raw
And you will find a file named rageitagainstthecage .
Now make a folder in C drive of any desired name (make sure that folder name doesn't contain space) and place the above file in this folder.
Now path should look like this:
C:\(foldername)\ rageitagainstthecage
Now attach your phone to pc with adb enabled and start command prompt and type the following commands and press enter after each command:
cd ..
cd ..
cd yourfoldername
adb push rageitagainstthecage /data/tmp/local/
adb shell "chmod 775 /data/tmp/local/rageitagainstthecage"
adb shell "./data/tmp/local/ rageitagainstthecage"
Now the exploit will run and after the completion of exploit,restart your phone and again attach the phone to pc and the you can push the su binary and app in following way(assuming that you have su and Superuser.apk in your folder located in c drive)
adb shell "mount -o remount rw /system "
adb push su /system/bin/
adb push Superuser.apk /system/app/
adb shell "chmod 775 /system/bin/su"
adb shell "chmod 775 /system/app/Superuser.apk"
Now time to check if ir worked
adb shell
su
If you see "#" instead of "$", your phone is rooted!!!!
BEST OF LUCK!!!!
Sent from my ZTE-BLADE using xda app-developers app
Click to expand...
Click to collapse
when it endterd to push the file it is displayng that adb not found.
Download adb binary(google it) and place all the downloaded files in system32/64 folder!
And then try it!
A simple solution if you are lucky
Well i have one simple solution for you .. I dont know A20 is mediatech or not . So if it is an MTk device then all you have to do is pull the stock recovery from your android and then provide it here
then i will compile a CWM bessed on that and then you will have CWM on your device and u can flash any su binary in zip and you will find it in my post ...
So if you r lucky then u will get the both CWM and root .. Otherwise bro without device i cant help ..
To pull your recovery type this in adb
adb shell
$su
#dd if=/dev/block/mmcblk0p13 of=/sdcard/recovery.img
you will have ur stock recovery in sdcard . it might be around 6.144mb or close ... but not greater that 10 mb
thebdcoder said:
Well i have one simple solution for you .. I dont know A20 is mediatech or not . So if it is an MTk device then all you have to do is pull the stock recovery from your android and then provide it here
then i will compile a CWM bessed on that and then you will have CWM on your device and u can flash any su binary in zip and you will find it in my post ...
So if you r lucky then u will get the both CWM and root .. Otherwise bro without device i cant help ..
To pull your recovery type this in adb
adb shell
$su
#dd if=/dev/block/mmcblk0p13 of=/sdcard/recovery.img
you will have ur stock recovery in sdcard . it might be around 6.144mb or close ... but not greater that 10 mb
Click to expand...
Click to collapse
I don't know why my videocon drivers are not installing in my pc which is running windows 7 64bit. Whenever i'm trying to write the code it's showing adb not found. plzzz help.
So nobody seems to have any solution for VIDEOCON A20 mobile.
byte_code said:
download z4root.apk(google it!!!) and extract the apk with your fav. Decompression tool.go to res>raw
and you will find a file named rageitagainstthecage .
Now make a folder in c drive of any desired name (make sure that folder name doesn't contain space) and place the above file in this folder.
Now path should look like this:
C:\(foldername)\ rageitagainstthecage
now attach your phone to pc with adb enabled and start command prompt and type the following commands and press enter after each command:
Cd ..
Cd ..
Cd yourfoldername
adb push rageitagainstthecage /data/tmp/local/
adb shell "chmod 775 /data/tmp/local/rageitagainstthecage"
adb shell "./data/tmp/local/ rageitagainstthecage"
now the exploit will run and after the completion of exploit,restart your phone and again attach the phone to pc and the you can push the su binary and app in following way(assuming that you have su and superuser.apk in your folder located in c drive)
adb shell "mount -o remount rw /system "
adb push su /system/bin/
adb push superuser.apk /system/app/
adb shell "chmod 775 /system/bin/su"
adb shell "chmod 775 /system/app/superuser.apk"
now time to check if ir worked
adb shell
su
if you see "#" instead of "$", your phone is rooted!!!!
Best of luck!!!!
Sent from my zte-blade using xda app-developers app
Click to expand...
Click to collapse
this process doesn't work with videocon a20. Plz help
---------- Post added at 01:30 AM ---------- Previous post was at 01:26 AM ----------
it's a challenge for every dev to root videocon a20. Nothing can penetrate this mobile. I've searched every single forum/site. Please do something
done done
i wud like u to telll u
i have the same cell as u
ie VIDEOCON A20
finally rooted and quite happy
please search
SKRILLEX STARK XDA
here is the sol......Peace Out
thebdcoder said:
Well i have one simple solution for you .. I dont know A20 is mediatech or not . So if it is an MTk device then all you have to do is pull the stock recovery from your android and then provide it here
then i will compile a CWM bessed on that and then you will have CWM on your device and u can flash any su binary in zip and you will find it in my post ...
So if you r lucky then u will get the both CWM and root .. Otherwise bro without device i cant help ..
To pull your recovery type this in adb
adb shell
$su
#dd if=/dev/block/mmcblk0p13 of=/sdcard/recovery.img
you will have ur stock recovery in sdcard . it might be around 6.144mb or close ... but not greater that 10 mb
Click to expand...
Click to collapse
i wud like u to telll u
i have the same cell as u
ie VIDEOCON A20
finally rooted and quite happy
please search
SKRILLEX STARK XDA
here is the sol......Peace Out
its so simple to root videocon A20
Dear friends use Kingo root i rooted my videocon A20 within minutes
Im here for another answer from anyone is there any custom rom available for
videocon A20
Please help me

[GUIDE][ROOT] Blu Dash 3.5 d170 - Help with recovery and root

Update: New guide is in post # 122
http://forum.xda-developers.com/showthread.php?p=40433602#post40433602
The guide is in post # 98
http://forum.xda-developers.com/showthread.php?p=39362805#post39362805
Hello,
I have a Blu Dash 3.5 and would like to install clockworkmod recovery and enable root access, but so far have not found anything. Could you help me?
thank you
I tried using SuperOneClick, Gingerbreak, zroot but all without success.
Anyone have any other option?
_ _
I managed to set up the android SDK on ubuntu but I get permission denied message when trying to copy the files to the /system
I suppose I have to remount the partition in RW to be able to put the files but no idea how to do this.
_ _
fenrixarena said:
Well you can't without it being rooted, right now I just don't care about it anymore it's just a phone, & $30 isn't worth just freeing up some space. No guarantee that will make it run smoother without crashes either, that could just be a result of interface, so a bit of speed don't seem worth it to me, I have my own ringtones with ringdroid so I'm happy.
Everything having to do with extracting the boot.img requires it to be rooted otherwise I know enough about enough crapola already I could make that all spiffy and zabam if I wanted. I would just literally edit all the img files and provide a simple update.zip given I could get signing to work!
unfortunately I get nothing from fastboot at all, not sure it would help though. oem unlock stuff is all I recall about that besides it being a great wau to flash images to the phone
let me know if you make any progress, I'll put in my effort if you do anything at all that intices me to find a path to progress
Click to expand...
Click to collapse
fenrixarena, hope you get to find any progress on rooting this phone. I also agree with you that it is no worth the time or effort with this kind of phone but I think that the challenge is interesting . In my case I have no idea on how you may root it but I am sure it is possible i guess it all in find another compatible boot.img that can be rooted, right?
Regards,
- -
_ _
What is the address of the site that charges $ 30? We can verify that other users would like to do and split the cost ...
I managed to make root ...
I found the CWM recovery and stock recovery for Qsmart.
I was very curious if it would work in BLU and ended up installing the CWM with fastboot. It did not work, the screen just stays with the BLU and not access the recovery.
Then I installed stock recovery and did not work ...
But I realized that Windows recognized the device connected and I recognized two units with unsupported format.
then returned to the prompt and saw that the ADB was working. I used the command 'adb shell' and to my surprise was how the cursor #
So without wasting time already put su and busybox in /system/ bin and superuser.apk in /system/app, I changed the permissions and restarted the phone. And the root was working perfectly. :victory:
Only one problem, I do not have the recovery installed.
I wonder how I can help you to make root without losing recovery
>>
I use Windowns 7 Pro x64 bits.
I installed the drivers in the SuperOneClick version 2.3.3.
With the drivers installed could use fastboot and adb command.
Turning on the phone + vol - access mode fastboot / bootloader
It would be good to get root without losing the recovery. Because we need him to compile a clockworkmod recovery.
I used the romdump and got the following files:
https://docs.google.com/file/d/0B5rQL4bfhfPRZXhhZkg1Mkx5SHc/edit?usp=sharing
I used the mkfs.yaffs2 to convert the file system.tar for system.img
https://docs.google.com/file/d/0B5rQL4bfhfPRMGdaNnQ4b1RwclU/edit?usp=sharing
This system.img would function on another device?
okay, I am having one problem, what did you type for the permissions?
I've got superuser.apk pushed and the su in the /system/bin but when i try to chmod 777 it returns to -r- after I reboot!
Here's howto manually back up now that I have recovery adb root:
cat /proc/mtd
Then just cat (mtd#) > /sdcard/(image.img)
You can restore via fastboot flash
fenrixarena said:
okay, I am having one problem, what did you type for the permissions?
I've got superuser.apk pushed and the su in the /system/bin but when i try to chmod 777 it returns to -r- after I reboot!
Here's howto manually back up now that I have recovery adb root:
cat /proc/mtd
Then just cat (mtd#) > /sdcard/(image.img)
You can restore via fastboot flash
Click to expand...
Click to collapse
you get root access in adb shell?
send su to /system/bin with permission 6755.
busybox to /system/bin with permission 755.
and superuser.apk to /system/app with 644.
reboot your phone
then download terminal emulator on your phone and enter the command su
if the cursor change to # worked
erickreisbr said:
you get root access in adb shell?
send su to /system/bin with permission 6755.
busybox to /system/bin with permission 755.
and superuser.apk to /system/app with 644.
reboot your phone
then download terminal emulator on your phone and enter the command su
if the cursor change to # worked
Click to expand...
Click to collapse
These are actually good news... Right on!!! Cheers if you manage to root Blu Dash 3.5 :victory:
Can someone guide me on how I can Root my phone? What adb tools do i need?
Regards
az0ik said:
These are actually good news... Right on!!! Cheers if you manage to root Blu Dash 3.5 :victory:
Can someone guide me on how I can Root my phone? What adb tools do i need?
Regards
Click to expand...
Click to collapse
I can upload the cwm.img & adb I used + fastboot. Not all adb.exe will recognize the phone. Also drivers from qsmart for adb bridge.
1 boot holding vol down + power (about 15 sec.)
Fastboot flash recovery cwm.img
Then turn phone off.
Boot holding vol UP + Power (about 15 sec)
Adb push su /system/bin
Adb push busybox /system/bin
Adb push superuser.apk /system/app
adb shell
~# chmod 6755 /system/bin/su
~# chmod 755 /system/bin/busybox
~# chmod 644 /system/app/superuser.apk
reboot your phone
terminal emulator - su
permission granted
IT WORKED!
---------- Post added at 02:21 AM ---------- Previous post was at 02:00 AM ----------
sorry, tomorrow I will upload a zip with the img i used and so forth all in one zip so you can root with that, unless it's here by someone else by then I gotta work!
fenrixarena said:
I can upload the cwm.img & adb I used + fastboot. Not all adb.exe will recognize the phone. Also drivers from qsmart for adb bridge.
1 boot holding vol down + power (about 15 sec.)
Fastboot flash recovery cwm.img
Then turn phone off.
Boot holding vol UP + Power (about 15 sec)
Adb push su /system/bin
Adb push busybox /system/bin
Adb push superuser.apk /system/app
adb shell
~# chmod 6755 /system/bin/su
~# chmod 755 /system/bin/busybox
~# chmod 644 /system/app/superuser.apk
reboot your phone
terminal emulator - su
permission granted
IT WORKED!
---------- Post added at 02:21 AM ---------- Previous post was at 02:00 AM ----------
sorry, tomorrow I will upload a zip with the img i used and so forth all in one zip so you can root with that, unless it's here by someone else by then I gotta work!
Click to expand...
Click to collapse
Thank you so much Fenrixarena!! You are awesome :good::good::good:. I still can believe it, i thought it was a lost hope... I really appreciate for uploading the files I am patient enough to wait another day
Follow the ADB and the recovery I've used.
The drivers installed by SuperOneClick, but have these here:
32 bits - http://www.mediafire.com/?21na032gnzbfza2
64 bits - http://www.mediafire.com/?1hrwo325cb1ej2w
Fx
fenrixarena said:
interesting, I got a cwm4s12.img that's larger(4.51) and because of having a 64bit laptop without 32bit support I had to use a smaller ADB (158kb) to be able to recognize the phone and only on regular usb debugging does superoneclick install drivers which was useless since I needed the drivers to work in recovery.
If those files don't work for you I will upload mine
I got my files from foreign thread, and since I download so many versions and custom versions of programs like adb I'm not sure where it came from !!
oh, and he rooted the phone first, I only did it on a more bothersome platform.
Click to expand...
Click to collapse
the root worked on your phone?
Now we need a recovery. I'm trying to learn how to compile cwm, but it is very complicated.

Categories

Resources