Is there any way to root Toshiba excite at300se ?.Or Stock ROM link .I try to find the adb driver and CWM for the this tablet.:crying:
Don't worry bro.....
We will find the solution (one day)
did anyone find a way to root the AT300SE (Excite 10SE), or the AT305, they are the same as far as I know
the AT305 is the US edition.
Check this below link for ABD driver from Toshiba
hxxp://support.toshiba.com/support/viewContentDetail?contentId=4001725
Hope there will some more development for this device..
Finally rooted !!!
Hopelessly I tried the Motochopper and it WORKED !!!
My AT300SE is rooted.
You need:
a PC,
the motochopper http://forum.xda-developers.com/showthread.php?t=2228613
and
ADB driver http://support.toshiba.com/support/viewContentDetail?contentId=4001725
*edit*
Attention please: only for 4.1 JB (not 4.0.3 ICS)
tasos66 said:
Finally rooted !!!
Hopelessly I tried the Motochopper and it WORKED !!!
My AT300SE is rooted.
You need:
a PC,
the motochopper http://forum.xda-developers.com/showthread.php?t=2228613
and
ADB driver http://support.toshiba.com/support/viewContentDetail?contentId=4001725
Click to expand...
Click to collapse
Thank man for the update..
Did u try CWM or TWRP For recovery .To make stock backup
are you sure that it worked???
Doesn't seem to work on the Excite 10LE aka At200 :crying:
ftomas said:
are you sure that it worked???
Doesn't seem to work on the Excite 10LE aka At200 :crying:
Click to expand...
Click to collapse
For at300se it worked perfectly.
What exactly is the problem?
Did the pc recognized the device, as an adb connection?
tasos66 said:
For at300se it worked perfectly.
What exactly is the problem?
Did the pc recognized the device, as an adb connection?
Click to expand...
Click to collapse
I don't have the at200 here....
i didn't get any errors from the script, if i didn't have the correct drivers should have been an error on the script, no?
the script runs... and then i ask for enter to reboot.... the at200 reboots but no working SU
ftomas said:
I don't have the at200 here....
i didn't get any errors from the script, if i didn't have the correct drivers should have been an error on the script, no?
the script runs... and then i ask for enter to reboot.... the at200 reboots but no working SU
Click to expand...
Click to collapse
Sorry to hear that
there are several Motochopper versions out there, how many Mb is the zip file that you downloaded?
I downloaded four or five of them, maybe one of them will work for you.
tasos66 said:
Sorry to hear that
there are several Motochopper versions out there, how many Mb is the zip file that you downloaded?
I downloaded four or five of them, maybe one of them will work for you.
Click to expand...
Click to collapse
+/- 2mb
where can i find those files?
ftomas said:
+/- 2mb
where can i find those files?
Click to expand...
Click to collapse
I will send you the file I used and worked for at300se, later today (about 22:00 Greek time)
---------- Post added at 03:01 PM ---------- Previous post was at 02:13 PM ----------
ftomas said:
+/- 2mb
where can i find those files?
Click to expand...
Click to collapse
O.K. I found the link.
http://mirror21.downloadandroidrom.com/download/GalaxyS4/root/motochopper.zip?token=
Good Luck!
tasos66 said:
Finally rooted !!!
Hopelessly I tried the Motochopper and it WORKED !!!
My AT300SE is rooted.
You need:
a PC,
the motochopper http://forum.xda-developers.com/showthread.php?t=2228613
and
ADB driver http://support.toshiba.com/support/viewContentDetail?contentId=4001725
Click to expand...
Click to collapse
Did not work for me either. I own an AT300SE-101
Click for details here.
http://forum.xda-developers.com/showthread.php?p=42700267#post42700267
Worked fine.No problem for rooting device (at300se).......:good: After the root superSu got update and as well as binary.
Is any update on Recovery and stock ROM....
dashu42332 said:
Worked fine.No problem for rooting device (at300se).......:good: After the root superSu got update and as well as binary.
Is any update on Recovery and stock ROM....
Click to expand...
Click to collapse
I dont know whats the problem.... but dont work
ftomas said:
I dont know whats the problem.... but dont work
Click to expand...
Click to collapse
Disable antivirus software and firewall.
tasos66 said:
Disable antivirus software and firewall.
Click to expand...
Click to collapse
Hummm, did you see the photo i post?
ADB seems to be working... or not? the push command seem to be successful... its fails when installing superuser.apk?
Other thing... this is part of the the run.bat with some notes in front, because i don't know linux can you see if the notes are right?:
adb push pwn /data/local/tmp/ - send the pwn (exploit) to the tablet
adb shell chmod 755 /data/local/tmp/pwn - change pwn permissions
echo [*] Pushing root tools...
adb push su /data/local/tmp/ - send SU to the tablet
adb push busybox /data/local/tmp/ send busybox to the tablet
adb install Superuser.apk - install superuser on the tablet (where scrip seem to give the error)
echo [*] Rooting phone...
adb shell /data/local/tmp/pwn - WHATS THIS COMMAND DOES?
echo [*] Cleaning up...
adb shell rm /data/local/tmp/pwn - delete pwn
adb shell rm /data/local/tmp/su - delete SU
adb shell rm /data/local/tmp/busybox - delete busybox
echo [*] Exploit complete
ftomas said:
Hummm, did you see the photo i post?
ADB seems to be working... or not? the push command seem to be successful... its fails when installing superuser.apk?
Other thing... this is part of the the run.bat with some notes in front, because i don't know linux can you see if the notes are right?:
adb push pwn /data/local/tmp/ - send the pwn (exploit) to the tablet
adb shell chmod 755 /data/local/tmp/pwn - change pwn permissions
echo [*] Pushing root tools...
adb push su /data/local/tmp/ - send SU to the tablet
adb push busybox /data/local/tmp/ send busybox to the tablet
adb install Superuser.apk - install superuser on the tablet (where scrip seem to give the error)
echo [*] Rooting phone...
adb shell /data/local/tmp/pwn - WHATS THIS COMMAND DOES?
echo [*] Cleaning up...
adb shell rm /data/local/tmp/pwn - delete pwn
adb shell rm /data/local/tmp/su - delete SU
adb shell rm /data/local/tmp/busybox - delete busybox
echo [*] Exploit complete
Click to expand...
Click to collapse
It looks like the adb driver works fine but I am afraid your tablet can not be rooted by this method .
I am IT engineer and manager but not Android developer so I cannot help you any furthermore.
Maybe this is a good reason for a tablet upgrade
Good luck!
regards
Tasos
Please check your Android version in your tab. Because above steps will work only for Android version 4.1 or above. ....
dashu42332 said:
Please check your Android version in your tab. Because above steps will work only for Android version 4.1 or above. ....
Click to expand...
Click to collapse
hum......
I only have ICS 4.0.3
Related
This Guide is for those who cant root their devices by tools like SuperOne , UnlockRoot etc .Because Adb cant recognize their devices .
This is a manual method and i like it most . first thing you need is adb .
download su and superuser.apk . download and install moborobo . now extracy su and superuser to your adb folder .
now connect a27 with moborobo . it will install drivers . dont disconnect your device with moborobo .
While connected with moborobo open command prompt in your adb folder .
type
Code:
adb devices
if you find your device listed then type
Code:
adb remount
Code:
adb push su /system/bin/
Code:
adb push su /system/xbin/
Code:
adb shell chmod 4755 /system/bin/su
Code:
adb shell chmod 4755 /system/xbin/su
Code:
adb install superuser.apk
Hey,, i cant install the spreadtrum driver it is showing does not contain 3rd party digital signature
rv6598 said:
Hey,, i cant install the spreadtrum driver it is showing does not contain 3rd party digital signature
Click to expand...
Click to collapse
install google drivers . no need to install spreadtrum .
pls send me driver link
driver link pls.... thnks
moborobo is not installing the driver
cant find the device in command prompt
Pls help me
i cant find the devices in the command prompt
rv6598 said:
Pls help me
i cant find the devices in the command prompt
Click to expand...
Click to collapse
try moborobo method .
not working
it is not working
Vibhav Jha said:
This Guide is for those who cant root their devices by tools like SuperOne , UnlockRoot etc .Because Adb cant recognize their devices .
This is a manual method and i like it most . first thing you need is adb .
download su and superuser.apk . download and install moborobo . now extracy su and superuser to your adb folder .
now connect a27 with moborobo . it will install drivers . dont disconnect your device with moborobo .
While connected with moborobo open command prompt in your adb folder .
type
Code:
adb devices
if you find your device listed then type
Code:
adb remount
Code:
adb push su /system/bin/
Code:
adb push su /system/xbin/
Code:
adb shell chmod 4755 /system/bin/su
Code:
adb shell chmod 4755 /system/xbin/su
Code:
adb install superuser.apk
Click to expand...
Click to collapse
where i can find adb folder and where i have to extract???????????
rv6598 said:
Hey,, i cant install the spreadtrum driver it is showing does not contain 3rd party digital signature
Click to expand...
Click to collapse
i have driver link but due to i am a new to xda therefore xda not allowing me to post outsiders link so plz mail me if u want driver link
[email protected]
Micromax bolt a27
Vibhav Jha said:
This Guide is for those who cant root their devices by tools like SuperOne , UnlockRoot etc .Because Adb cant recognize their devices .
This is a manual method and i like it most . first thing you need is adb .
download su and superuser.apk . download and install moborobo . now extracy su and superuser to your adb folder .
now connect a27 with moborobo . it will install drivers . dont disconnect your device with moborobo .
While connected with moborobo open command prompt in your adb folder .
type
Code:
adb devices
if you find your device listed then type
Code:
adb remount
Code:
adb push su /system/bin/
Code:
adb push su /system/xbin/
Code:
adb shell chmod 4755 /system/bin/su
Code:
adb shell chmod 4755 /system/xbin/su
Code:
adb install superuser.apk
Click to expand...
Click to collapse
is it applicable to Micromax Bolt A27
Micromax A27 Big Problem.....Help..!!!
[email protected] said:
is it applicable to Micromax Bolt A27
Click to expand...
Click to collapse
hiiiii...
theres a big problem with me..with my micromax a27
i hv installed cwm and taken backup of stock rom.
but mistakenly formatted system,data,cache....and all things in mounts and storage.
and then i realised that for booting into cwm is through quick boot (from thats what i was booting to recovery, i dont know any other way to boot)...
so u know my problem.....
plz say any way through which i can directly boot into cwm recovery and get my phone back...through buttons.....
plz im in big trouble and i waiting for replies.....
plz do reply immediately.....
there has to be a way out there to recover back...
Through pc....cmon dev's
Plz reply with concern. .....its very important to me.....
Plz show all the instructions....
not working help us to root micromax a27
unlockroot ( with moborobo) not working
First.. Use a powerful cable for e.g. samsung galaxys or canvas hds usb cable.. Your phone will be recognized by adb too.. Once that happens unlockroots good to go
Sent from my XT1028 using XDA Free mobile app
---------- Post added at 05:55 AM ---------- Previous post was at 05:46 AM ----------
Im no dev but.. If u want to boot into recovery u first have to boot in fastboot mode "power + volume down" .. Then you have to download recovery.img of ur phone from google then .. Check if your phone is connected by typing "fastboot devices"
If it shows a random number your good to go.. Den put your downloaded recovery.img in your ad and fast boot folder.. N open fastboot by pressing shift and right click and open window here and type "fastboot flash boot recovery.img" and then normal remove battery and normal boot.. U will boot in recovery
Sent from my XT1028 using XDA Free mobile app
Has anyone had a successful root on a plt7602g. I have tried a couple different methods.
Rooting the PLT7602G
sallanm said:
Has anyone had a successful root on a plt7602g. I have tried a couple different methods.
Click to expand...
Click to collapse
Here is a procedure to root the Curtis Proscan PLT7602G tablet (Build number PLT7602G-ANDROID4.2.2-v1.0.0).
1. Install adb on your computer and enable adb on the tablet. http://developer.android.com/tools/help/adb.html
2. Enable ADB on the tablet:
Settings > About Tablet > tap build number 7 times until it says "You are now a developer!"
Developer options > switch On > OK
Check "USB Debugging" > OK
3. Connect USB and wait for ADB drivers to load on the PC. Using the Google drivers installed with ADB, your system may need manual help to find the right drivers: Go into Windows device manager > Update Driver Software > browse My Computer for driver software > 'Let me pick from a list of devices drivers...' > Pick Android ADB Interface from the model list.
4. You will see a notification "USB Debugging Connected" on the tablet.
5. If this is the first time, you will next see a dialog on the tablet asking "Allow USB debugging?" Check "Always allow from this computer" and click OK.
6. At the command prompt on the computer enter "adb devices". You should see the device listed. If not, reboot the PC and repeat steps 1 through 5 as necessary to get everything working together.
C:\Users\entropy>adb devices
List of devices attached
CD1LBROR50 device
C:\Users\entropy>7. Download pwn.zip here: http://forum.xda-developers.com/showpost.php?p=53407127
8. Unzip "pwn" from the zip file to your windows current directory
9. At the command prompt on the computer enter the following sequence of commands:
C:\Users\entropy> adb push pwn /data/local/tmp/pwn
C:\Users\entropy> adb shell chmod 755 /data/local/tmp/pwn
C:\Users\entropy> adb shell /data/local/tmp/pwn
Beaups and jcase were here
donations may go here, pleaes say what it was for -> [email protected]
10. After a few seconds, you should hear the USB disconnect sound, followed by the USB connection sound again.
11. At the command prompt, enter “adb devices” and ensure the device is listed as before. If not, wait a few seconds and then repeat this step.
C:\Users\entropy> adb devices
12. At the command prompt, enter:
C:\Users\entropy> adb shell
7. At the shell prompt, enter "su". You should now have a root prompt.
[email protected]:/ $ su
[email protected]:/ #
8. Exit back out to the command prompt:
[email protected]:/ # exit
[email protected]:/ $ exit
C:\Users\entropy>
9. On the tablet, go to the play store, download and install the latest SuperSU, or use the Google Play link in this thread: http://forum.xda-developers.com/show....php?t=1538053
10. Open the SuperSU that you just installed. SuperSU will prompt you to install a newer su binary when you run it, so click “Continue” do that, then “Normal”, then “OK”.
11. Reboot the tablet.
The tablet should now be fully rooted. Please let me know if you find any errors or if anything is unclear. I hope you find this useful!
I've downloaded the "Unrevoked" USB driver but the device is not being installed...
Marco Dufal said:
I've downloaded the "Unrevoked" USB driver but the device is not being installed...
Click to expand...
Click to collapse
It has been a while since I got this working and I honestly don't remember exactly what I did to make it work.
Try this... install the official Google driver and reboot:
http://developer.android.com/sdk/win-usb.html
If i still doesn't work, download the adb_usb.ini from here and replace the adb_usb.ini in c:\users\<yourusername>\.android\adb_usb.ini with this one, then reboot and try again. I verified that this adb_usb.ini contains the necessary device ID, so that should definitely do the trick.
https://github.com/apkudo/adbusbini
If you get it working, please post here so others can benefit.
Sice I had already installed the official Google drivers I proceeded with the adb_usb.ini method, but even after rebooting my pc it didn't work... What worked for me was:
Going into window device manager -> Update Driver Software -> browse my computer for driver software -> 'let me pick from a list of devices drivers...' -> Picked Android ADB Interface (from the model list).
I don't get why it did't install it automatically since the driver is actually compatible; did the same thing with another device (Sony experia E1). I got two of them, the first one got recognized while I had to do this process for the second one... Maybe it's my pc fault..
Anyway thank you very much for your replies and the guide. Am I risking to brick the device by following it ?
P.S.
For those who have android studio installed, to run the guide prompt commands you can set an environment variable called 'adb' with this value 'C:\Users\{USERNAME}\AppData\Local\Android\sdk\platform-tools\adb.exe' and easily replacing 'adb' with '%adb%' .
For example : 'C:\Users\{any directory}>%adb% devices'
Marco Dufal said:
Sice I had already installed the official Google drivers I proceeded with the adb_usb.ini method, but even after rebooting my pc it didn't work... What worked for me was:
Going into window device manager -> Update Driver Software -> browse my computer for driver software -> 'let me pick from a list of devices drivers...' -> Picked Android ADB Interface (from the model list).
I don't get why it did't install it automatically since the driver is actually compatible; did the same thing with another device (Sony experia E1). I got two of them, the first one got recognized while I had to do this process for the second one... Maybe it's my pc fault..
Anyway thank you very much for your replies and the guide. Am I risking to brick the device by following it ?
P.S.
For those who have android studio installed, to run the guide prompt commands you can set an environment variable called 'adb' with this value 'C:\Users\{USERNAME}\AppData\Local\Android\sdk\platform-tools\adb.exe' and easily replacing 'adb' with '%adb%' .
For example : 'C:\Users\{any directory}>%adb% devices'
Click to expand...
Click to collapse
I'm glad you got ADB working. Thanks for the additional tips, I'm sure they will be useful to others.
I don't think there is any significant risk of bricking unless you make a horrible mistake, like deleting everything in /system instead of shifting the new file into place. Anything else, like accidentally picking the wrong su binary to install, should be easily recoverable by just rebooting if necessary and then trying again.
maximumentropy said:
I'm glad you got ADB working. Thanks for the additional tips, I'm sure they will be useful to others.
I don't think there is any significant risk of bricking unless you make a horrible mistake, like deleting everything in /system instead of shifting the new file into place. Anything else, like accidentally picking the wrong su binary to install, should be easily recoverable by just rebooting if necessary and then trying again.
Click to expand...
Click to collapse
Quick info. I am rooting because of the low storage. Currently this is my storage situation :
total 4GB
Firmware 2.04GB
---------------------
Total space 1.96GB
197MB Available
232MB Apps
few KB Cached data & Misc.
There must be something wrong... Anyway my question is. Should I flash a custom rom to free some of the firmware allocated memory ? How is the external card going to be used (can I install app on it) ?
EDIT
I get
`su: not found`
Marco Dufal said:
Quick info. I am rooting because of the low storage. Currently this is my storage situation :
total 4GB
Firmware 2.04GB
---------------------
Total space 1.96GB
197MB Available
232MB Apps
few KB Cached data & Misc.
There must be something wrong... Anyway my question is. Should I flash a custom rom to free some of the firmware allocated memory ? How is the external card going to be used (can I install app on it) ?
Click to expand...
Click to collapse
I haven't found any custom ROMs for this tablet. If you know of some, please speak up. You could try reflashing the original ROM but that might be overkill. You can use an app like DiskUsage to help you identify what's eating the most space.
Marco Dufal said:
EDIT
I get
`su: not found`
Click to expand...
Click to collapse
I can't help you if you give me an error message but no hint of what you entered that caused the message.
maximumentropy said:
I haven't found any custom ROMs for this tablet. If you know of some, please speak up. You could try reflashing the original ROM but that might be overkill. You can use an app like DiskUsage to help you identify what's eating the most space.
Click to expand...
Click to collapse
Thanks I will check it up.
maximumentropy said:
I can't help you if you give me an error message but no hint of what you entered that caused the message.
Click to expand...
Click to collapse
C:\Users\Marco\AppData\Local\Android\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $
Marco Dufal said:
Thanks I will check it up.
C:\Users\Marco\AppData\Local\Android\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $
Click to expand...
Click to collapse
Please try entering it with full path:
[email protected]:/ $ /system/xbin/su
maximumentropy said:
Please try entering it with full path:
[email protected]:/ $ /system/xbin/su
Click to expand...
Click to collapse
Still negative result :
[email protected]:/ $ /system/xbin/su
/system/xbin/su
/system/bin/sh: /system/xbin/su: not found
127|[email protected]:/ $ ls /system/xbin/
ls /system/xbin/
dexdump
io
[email protected]:/ $
Marco Dufal said:
Still negative result :
Click to expand...
Click to collapse
What is your build number in Settings > About Tablet?
maximumentropy said:
What is your build number in Settings > About Tablet?
Click to expand...
Click to collapse
PLT7602G-ANDROID4.2.2-v1.0.0
Marco Dufal said:
PLT7602G-ANDROID4.2.2-v1.0.0
Click to expand...
Click to collapse
Well, I apologize for being an idiot. That's what I get for trying to document a root procedure I did last year, from memory. I have several similar cheap tablets and I misremembered this one as being pre-rooted as I described.
I just re-flashed from stock and re-rooted it. Fortunately, I had left enough breadcrumbs on my computer that I was able to reconstruct the right procedure.
I will do another full run-through within the next few days as soon as I have some time, to make sure I have everything 100% straight, and will clean this up to update the OP. Meanwhile, if you're feeling brave, here's the notes I took as I did it:
Settings > About Tablet > tap build number until it says you are a developer
Developer options > switch On > OK
USB Debugging > OK
Connect USB
see "USB Debugging Connected" notification
Wait for "Allow USB debugging?" dialog, check "Always allow from this computer" and click OK
adb devices
Download pwn.zip here: http://forum.xda-developers.com/showpost.php?p=53407127
Unzip "pwn" from the zip file to your windows current directory
adb push pwn /data/local/tmp/pwn
adb shell chmod 755 /data/local/tmp/pwn
adb shell /data/local/tmp/pwn
Hear USB disconnect sound
Wait about 1 minute (may or may not need to disconnect and reconnect USB cable)
adb wait-for-device
adb shell
su (should give a root shell)
exit
Install SuperSU from Play Store
Run it
The SU binary needs to be updated. Continue?
Continue > Normal > OK
Reboot
Don't worry it's ok.. Anyway I am not felling brave at all so I think that I will wait for now...
Marco Dufal said:
Don't worry it's ok.. Anyway I am not felling brave at all so I think that I will wait for now...
Click to expand...
Click to collapse
No guts, no glory!
I updated the instructions in post #2 and did another trial run through. Give it a shot at let me know if you run into any trouble. You already have ADB functioning, so you can just skip to step 6 and go from there.
http://forum.xda-developers.com/showpost.php?p=59530490&postcount=2
maximumentropy said:
No guts, no glory!
Click to expand...
Click to collapse
Just did it and every thing worked ! It was fast and clear... Now I wonder, how many devices can I root with the same procedure ?
Marco Dufal said:
Just did it and every thing worked ! It was fast and clear... Now I wonder, how many devices can I root with the same procedure ?
Click to expand...
Click to collapse
Great, I'm glad it worked for you!
The pwn exploit will work with many JellyBean devices. Many of the cheap Chinese tablets don't even need it though, as they will either give you a root prompt immediately when you connect using ADB, or after entering "su" to ADB. The trick then is just to use that access to install an "su" from SuperSU or another full SU package, so that you get full root from the user interface as well as from ADB. You could still use the pwn method on such a device, but I personally prefer to use the least invasive method to get the required access.
maximumentropy said:
Great, I'm glad it worked for you!
The pwn exploit will work with many JellyBean devices. Many of the cheap Chinese tablets don't even need it though, as they will either give you a root prompt immediately when you connect using ADB, or after entering "su" to ADB. The trick then is just to use that access to install an "su" from SuperSU or another full SU package, so that you get full root from the user interface as well as from ADB. You could still use the pwn method on such a device, but I personally prefer to use the least invasive method to get the required access.
Click to expand...
Click to collapse
Sorry if this is a newb question but can this be done if your microusb port is broken? I can get the file on the tablet via sd card but I can't seem to perform the steps with Terminal Emulator like I had hoped. This is using the same ProScan PLT7602G as in the OP.
Thanks
Ian1331 said:
Sorry if this is a newb question but can this be done if your microusb port is broken? I can get the file on the tablet via sd card but I can't seem to perform the steps with Terminal Emulator like I had hoped. This is using the same ProScan PLT7602G as in the OP.
Thanks
Click to expand...
Click to collapse
I don't think it will work in a terminal emulator because you need to run with uid 2000 (shell) for permission on the /data/local/tmp directory.
I have a NEC Terrain NE-201A1A, use android 4.0.4 stock rom, I don't know how to root it, who can help me? Thanks so much
There is not any root method
zolahn said:
I have a NEC Terrain NE-201A1A, use android 4.0.4 stock rom, I don't know how to root it, who can help me? Thanks so much
Click to expand...
Click to collapse
At least for now, there is not any permanent root method. Only a temp shell root. NEC Terrain is NAND/bootloader locked, S-on and does not have fastboot support.
You should have used search. More about this:
Rooting NEC Terrain
NEC Terrain: ADB/CDC Serial Driver, 3e Recovery Password, and Root
NEC Terrain Rooting and Flashing Guide
Root method discovered for NEC Terrain?
Unlocking of NEC Terrain SIM/Root
FFDA said:
At least for now, there is not any permanent root method. Only a temp shell root. NEC Terrain is NAND/bootloader locked, S-on and does not have fastboot support.
You should have used search. More about this:
Rooting NEC Terrain
NEC Terrain: ADB/CDC Serial Driver, 3e Recovery Password, and Root
NEC Terrain Rooting and Flashing Guide
Root method discovered for NEC Terrain?
Unlocking of NEC Terrain SIM/Root
Click to expand...
Click to collapse
I read all thread but I can't install this driver in my computer, I think this driver is not correct for my phone, do u have other driver for nec terrain?
I'm using linux
zolahn said:
I read all thread but I can't install this driver in my computer, I think this driver is not correct for my phone, do u have other driver for nec terrain?
Click to expand...
Click to collapse
I am assuming that you are using Windows so try this ADB Driver Installer.
Hi
FFDA said:
I am assuming that you are using Windows so try this ADB Driver Installer.
Click to expand...
Click to collapse
Can u guide me how to root it? (tmp root). thanks
I can try
zolahn said:
Can u guide me how to root it? (tmp root). thanks
Click to expand...
Click to collapse
I have never tried getting temp shell root from windows, but it should pretty simple. First of all you have to set up adb (if you don't have it yet try this) and then just do this:
In windows cmd, go to folder where your run_root_shell file is.
Push run_root_shell to /datal/local/tmp folder using command: adb push run_root_shell /data/local/tmp/
Set permissions to run_root_shell: adb shell chmod 777 /data/local/tmp/run_root_shell
Go to adb shell using command: adb shell
Lastly get root temp using command: /data/local/tmp/run_root_shell
Good luck
zolahn said:
I read all thread but I can't install this driver in my computer, I think this driver is not correct for my phone, do u have other driver for nec terrain?
Click to expand...
Click to collapse
Here's a list of root apps you can try:
Framaroot
Vroot
For PC(plug your device into your PC and start rooting):
Kingo android root
These are really simple applications that helps you root your device with just a click.
---------- Post added at 09:46 PM ---------- Previous post was at 09:43 PM ----------
Before I forgot to mention this, after you've root your device with Kongo android root, the action can be reversed(unroot). You can't unroot with framaroot(in my memory), with vroot you can simply unroot your device by uninstalling this app.
FFDA said:
I have never tried getting temp shell root from windows, but it should pretty simple. First of all you have to set up adb (if you don't have it yet try this) and then just do this:
In windows cmd, go to folder where your run_root_shell file is.
Push run_root_shell to /datal/local/tmp folder using command: adb push run_root_shell /data/local/tmp/
Set permissions to run_root_shell: adb shell chmod 777 /data/local/tmp/run_root_shell
Go to adb shell using command: adb shell
Lastly get root temp using command: /data/local/tmp/run_root_shell
Good luck
Click to expand...
Click to collapse
So if i use ubuntu, how can root it?
Let's try Linux!
zolahn said:
So if i use ubuntu, how can root it?
Click to expand...
Click to collapse
You understand that this temp shell root does not let you debloat the phone, resize partition, ect? It basically lets you read more partitions through adb shell (Command line. NO graphical interface)?
If you still what to gain temp root:
Open terminal. Press
Code:
CTRL+ALT+T
at the same time.
In terminal paste:
Code:
sudo apt-get install android-tools-adb
and enter password. If you get an error that there isn't such application or similar paste this command:
Code:
sudo add-apt-repository ppa:phablet-team/tools && sudo apt-get update
and then the first one again.
Add the rule to 99-android.rules file. Open the file with this command:
Code:
sudo gedit /etc/udev/rules.d/99-android.rules
and paste in the window that just opened this line (Don't forget to add YOUR account name where it saids so in this line)
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0409", ATTR{idProduct}=="0358", MODE="0666", OWNER="[B]your Linux account name[/B]"
save and close the window.
At this point you may need to restart your PC for changes to take effect, so better do it. Also turn debugging mode in your NEC Terrain and connect it to you PC with USB cable.
Go to folder where your run_root_shell file is, right-click and choose "open in terminal".
Check if ADB is set up right. Type in terminal:
Code:
adb devices
Your should see text like this:
Code:
List of devices attached
ea1f2870 device
Tell me if you see this:
Code:
List of devices attached
???????????? no permissions
Push run_root_shell to /datal/local/tmp folder using command:
Code:
adb push run_root_shell /data/local/tmp/
Set permissions to run_root_shell:
Code:
adb shell chmod 777 /data/local/tmp/run_root_shell
Go to adb shell using command:
Code:
adb shell
Lastly get root temp using command:
Code:
/data/local/tmp/run_root_shell
If you see # instead of $ in terminal you have shell root privileges.
Lets continue discussion in one thread!
http://forum.xda-developers.com/showthread.php?p=59514154#post59514154
I created a GitHub repo to collect information, also on how to disable apps (since thats as good as it gets for now).
i am trying to install my e400 and at command
adb shell "ln -s /data /data/gpscfg/gps_env.conf"
i take a msg "permission denied"
any suggestion?
Try this:
adb shell
su (then accept from phone)
ln -s /data/data/gpscfg/gps_env.conf
If you want enter to /data folder, you should have root acces.
fbli_41 said:
Try this:
adb shell
su (then accept from phone)
ln -s /data/data/gpscfg/gps_env.conf
If you want enter to /data folder, you should have root acces.
Click to expand...
Click to collapse
http://prntscr.com/4qudfm
Still cant :/
when i type ''su'' nothing appers in screen
[email protected] said:
http://prntscr.com/4qudfm
Still cant :/
when i type ''su'' nothing appers in screen
Click to expand...
Click to collapse
finally rooted it with Kingo.
Is the problem solved?
fbli_41 said:
Is the problem solved?
Click to expand...
Click to collapse
yes yes ...i just enabled usb debugging ,inserted usb ,run Kingo Root and rooted successfully
I'm happy
[email protected] said:
finally rooted it with Kingo.
Click to expand...
Click to collapse
Thank you very much! :victory:
I was trying to install gapps and now when I reboot I am stuck and the Play Store language select screen. When I click next, it takes me to settings. I have no home or back button so I cant get anywhere other than the settings menu. I have tried a factory reset with no avail. I also tried a manual update, but I have disable OTA updates so it wont recognize the .bin file on my SD. If only I could get to ES File Explorer. Any tips on fixing this problem?
Code:
adb shell "su -c 'mount -o rw,remount /system'"
adb shell "su -c 'mv /system/priv-app/SetupWizard.apk /system/priv-app/SetupWizard.apk.old'"
adb shell "su -c 'mount -o ro,remount /system'"
ONYXis said:
Code:
adb shell "su -c 'mount -o rw,remount /system'"
adb shell "su -c 'mv /system/priv-app/SetupWizard.apk /system/priv-app/SetupWizard.apk.old'"
adb shell "su -c 'mount -o ro,remount /system'"
Click to expand...
Click to collapse
Care to elaborate? I am a complete noob and shouldn't have been trying this at all. I can't access anything on my Kindle other than settings. Do I run this in command prompt on windows?
Edit: I also wanted to add that I am not one of the guys who sits around waiting for an answer without researching the problem lol
You need install adb on your PC - http://forum.xda-developers.com/showthread.php?t=2317790
Install drivers for our tablet (no need to reboot fastboot just manual install drivers for your kindle at device manager) - http://forum.xda-developers.com/showpost.php?p=59268023&postcount=8
Open CMD (cd C:\Program Files (x86)\Minimal ADB and Fastboot>)and paste these commands. I assume you rooted if you can block ota.
ONYXis said:
You need install adb on your PC - http://forum.xda-developers.com/showthread.php?t=2317790
Install drivers for our tablet (no need to reboot fastboot just manual install drivers for your kindle at device manager) - http://forum.xda-developers.com/showpost.php?p=59268023&postcount=8
Open CMD (cd C:\Program Files (x86)\Minimal ADB and Fastboot>)and paste these commands. I assume you rooted if you can block ota.
Click to expand...
Click to collapse
Apparently I no longer have root since I reset to factory. I do have the adb drivers installed, but I get stuck when using the command prompt because I dont have su access. Anyway for me to root it with only access to settings? I am on 4.5.2
are you sure?
earlier I had root even after hard reset on 4.5.2
anyway you could try install kingroot but I do not sure
I think @Cl4ncy and @Davey126 may clarify this.
ONYXis said:
are you sure?
earlier I had root even after hard reset on 4.5.2
anyway you could try install kingroot but I do not sure
I think @Cl4ncy and @Davey126 may clarify this.
Click to expand...
Click to collapse
Yes, I no longer had root access. Thanks to all of your other help and suggestions, I have been able to successfully get my Fire HDX working again. With all of the info you gave I was able to research and piece together what I needed. I was able to install Kingroot through cmd and then use the commands you gave to get rid out of settings. Thanks alot!