Database Users

Velocity Cruz Tablet modding

The cruz tablet has android 2.0, no market pre-installed. I'm attempting to load the market on to it by tracking down .apk files for the market (vending.apk?) I havent had any success with adb installing it. I can use adp for just about every thing else it seems. I'm very new at this thus far. Any suggestions?
Whenever i run adp install vending.apk i get an error failure [install_failed_older_sdk] any idea what this means? maybe the vending.psk is intended for newer versions of android? I've tried another vending.psk (supposidly for pre-froyo items and it gave me the error missing libraries)
Thoughts? Ideas? Thanks

your doing it wrong, first you have to have root, next you need to flash a gapps update. If you can't flash you can unzip the update and push the files to their right system directory using adb.
Sent from my HTC Vision using XDA App

my device is rooted, but I'm having a hard time finding the zip file on step 2 there, i have build eclair 2.0-r1.1
Interestingly enogh i still cant delete files or uninstall much, is this something related to CHMOD or similar?
(on second thought I access shell (#) through adb and i can delete at will. I'm learning quickly but still can't figure out the steps to throw the market on this thing. If anyone can help me with more of a step by step or point me somewhere, i would really like to add to the lackluster modding community for the cheap velocity
If i can just somehow package the marketplace in to a rom for this thing (i used to do roms for windows mobile) I think the device interest will grow

I actually made a bunch of progress the other night, ill share my progress tomorrow in detail but it went something like this:
boot with power and volume - (down)
then you can chmod the /etc/permissions. ( and other dies) - from what I could tell this was only way to change system partition to writable?
then you can copy xmls, jar, and install all. the apk's with adb
that's as far as I got, market would run, but never got any pages to show up or was able to login (if that was a feature in 2.0) I would be more interested in an upgrade to 2.1? (if that's even possible?)

Which market APK did you use?
I think? for a 2.1 we would have to take the source 2.1 and go from there, I have no clue how to do that or where to start but I would like to take a shot.
Ideas?
I am actually quite happy with what I have right now, I picked it up for 170 at best buy and have most of the apps I want (with the exception of angry birds ) The tablet has seemed to speed up as time has gone on and 2.1 would be great!
From the get go with this tablet you can adb shell and you get the # meaning rooted.

I used the Market APKs from some phone ROMs AOSP 2.4 release that I found on communityforum.com

Here are the steps (from my notes) that I used. Note the FAILED, but could be a good starting point for you: Keep in mind this is from my first 8 hours of trying to learn Android, my first ADB session, etc, I am NOT an expert at this, just dangerous given all the other information others have shared, most of this comes from other device/forums for people trying to install the android market. Got my starting point from a post that stated that to install Android Market you had to:
Install:
1) GoogleApps.apk
2) SetupWizard.apk
3) TalkProvider.apk
4) Vending.apk
5) GoogleCheckin.apk
6) gtalkservice.apk
and copy and locations below:
/system/etc/permissions/com.google.android.datamessaging.xml
/system/etc/permissions/com.google.android.gtalkservice.xml
/system/framework/com.google.android.gtalkservice.jar
/system/lib/libgtalk_jni.so
------------------------------------------------------------------
HERE IS AS FAR AS I GOT:
------------------------------------------------------------------
Power up and Vol - (together - not sure if this was necessary but for some reason I couldn't ADB SHELL in and make modifications originally - although it might have been a skill thing on my part)
ADB REMOUNT
ADB SHELL
CD /SYSTEM/ETC
ls -l shows: drwxr-xr-x root root 2010-12-15 15:40 permissions
chmod 775 permissions
ls -l shows: drwxrwxr-x root root 2010-12-15 15:40 permissions
exit
exit
adb push com.google.android.datamessaging.xml /system/etc/permissions
0 KB/s (829 bytes in 1.000s)
adb push com.google.android.gtalkservice.xml /system/etc/permissions
52 KB/s (832 bytes in 0.015s)
ADB SHELL
CD /system/etc/permissions
ls -l
-rw-r--r-- root root 1139 2010-11-05 15:38 required_hardware.xml
-rw-r--r-- root root 8188 2010-11-05 15:38 platform.xml
-rw-rw-rw- root root 829 2011-01-10 23:20 com.google.android.datamessaging.xml
-rw-rw-rw- root root 832 2011-01-10 23:20 com.google.android.gtalkservice.xml
cd ..
chmod 755 permissions
ls -l
drwxr-xr-x root root 2011-01-11 01:43 permissions
cd ..
ls -l
drwxr-xr-x root root 2010-12-15 15:41 lib
drwxr-xr-x root root 2010-12-15 15:40 fonts
drwxr-xr-x root shell 2010-12-15 15:41 bin
drwxr-xr-x root root 2010-12-15 15:40 framework
chmod 775 framework
chmod 775 lib
drwxrwxr-x root root 2010-12-15 15:41 lib
drwxr-xr-x root root 2010-12-15 15:40 fonts
drwxr-xr-x root shell 2010-12-15 15:41 bin
drwxrwxr-x root root 2010-12-15 15:40 framework
exit
adb push com.google.android.gtalkservice.jar /system/framework
1698 KB/s (27139 bytes in 0.015s)
adb push libgtalk_jni.so /system/lib
29 KB/s (9460 bytes in 0.312s)
ADB SHELL
cd /system/
chmod 755 lib
chmod 755 framework
drwxr-xr-x root root 2011-01-11 01:47 lib
drwxr-xr-x root root 2010-12-15 15:40 fonts
drwxr-xr-x root shell 2010-12-15 15:41 bin
drwxr-xr-x root root 2011-01-11 01:47 framework
exit
ADB INSTALL
SetupWizard.apk
GoogleApps.apk
TalkProvider.apk
REBOOT
vending.apk
gtalkservice.apk
GoogleCheckin.apk
GmailProvider.apk
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb install Gmail.apk
2472 KB/s (710975 bytes in 0.280s)
pkg: /data/local/tmp/Gmail.apk
Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION]
GoogleContactsSyncAdapter.apk (success)
GooglePartnerSetup.apk
GoogleSettingsProvider.apk
At some point during the APK install and a device reboot the devices comes to complete crap and you need to use the VelocityMicro.com Cruz firmware update.zip to 'restore' the device to it's original state - so I would suggest being careful with what I've done above because your likely to make your device extremely unstable. My GUESS is it's somewhere after the first three APK installs and the reboot (after the first reboot it comes back fine, all steps after that cause failure, reboot, GUI starts acting all funky, can't swipe to login, etc and it's done)
If I get a chance, I'll try to play with it some more tonight.
The Attached SUCCESS.ZIP contains the files from the AOSP2.4 download I used to get this far...

I cant seem to get mine in to the pre-boot enviornment
Anywho i did everything with the device on and completed. It seems stuck in a reboot loop, probably from the setup wizard i'm assuming? Have you tried not installing as many apk's? Maybe something is trying to run and causing it. Can it be done without the wizard?
I've created some scripts that install good apps that work well with the tablet thus far and a script that will auto-uninstall bloat shortcuts and programs that it ships with

If you take the update.zip from the velocitymicro.com website firmware update for the cruz, and load it (power and Vol +) it'll recover the system (can't say i didn't warn you!
It's something AFTER this step that screws it up.
ADB INSTALL
SetupWizard.apk
GoogleApps.apk
TalkProvider.apk
REBOOT
I found this today and am going to dig into it a bit more to play with it, to see if it leads somewhere:
http://www.slatedroid.com/velocity-...-vm-cruz-(testers-needed!)/msg63584/#msg63584
and this:
http://www.slatedroid.com/pandigita...ment/easy-market-hack-for-bpdn-e-reader-help/
might lead to something?

tried item at first link. the batch corrupted the rom and i had to run the update.zip again
yes i did have adb installed and set up. I've been trying something similar to this for a while, just the manual way

I was able to get some apps installed via the handango.com market. Select the T-mobile G1 and you can download/install gmail, google reader, gdocs, google apps, maps, etc but as of now none of them work.
discovered 'adb bugreport' which seems to show issues with installed app. just did a clean reinstall of update.zip and am going to start from scratch one app at a time to see if i can make any headway there instead of blindly installing a bunch of crap and hoping that it works.

when i enter
>adb shell
I keep getting "access denied"
any ideas what I may be doing wrong?

are you mounting the device first? 'adb remount' if you have multiple USB devices it maybe confused, make sure your mounting the right device.

tullywork said:
are you mounting the device first? 'adb remount' if you have multiple USB devices it maybe confused, make sure your mounting the right device.
Click to expand...
Click to collapse
My tablet is the only USB device attached to the pc. It is the T301
i get all the way to the android-sdk-windows\tools directory (there is more to the directory i just didn't type it all.
from there i try
>adb shell
>adb mount
>adb remount
and each time I get 'access denied'

I've been hoping activity would pick up for modding the Velocity Micro Cruz Tablet T100 series. Glad to see good old XDA has taken a bite as I've been following the Cruz Tablet on Slatedroid which recently split the Cruz into Reader and Tablet forums.
I've been playing with the Android SDK and ADB under Lubuntu Linux. http://www.slatedroid.com/index.php?topic=14771.0 I have a system.img that someone in the cloud created that has the Market but it doesn't have access to protected apps. I used a modified build.prop with a ro.build.fingeprint... for another device and can get a more complete Market with access to protected apps. From there I am able to install apps from the Market with the AVD and move them to Cruz Tablet for installation.
But I haven't had success connecting to the Cruz using ADB under Linux. I have not located the USB device id for the Cruz Tablet. The ADB devices command shows the AVD fine but the Cruz shows up with question marks. Windows and Macs just work but Linux requires a USD device ID. If anyone knows the ID for the Cruz Tablet T100 series please post.
:8

I think my tablet is going back to best buy tomorrow. 170 was a great deal but too many issues with it. I wasnt really impressed with the battery life and nothing over android 2.0 is a major bummer. I need my tether! RIP Cruz

Agreed. I actually returned mine last week. The biggest killer was no Android Market or Google Apps. Had it at LEAST had Google Apps, I would have kept it, shame because the look/feel/etc was nice and I thought it had promise, but limited Apps obviously made it a brick (to me). I kept my Viewsonic GTablet, lots more work on the black market for that device, so it suits my needs (although I'm not a huge fan of the long 10" form factor, something closer to 8 or 9 inch and a 4:3 ratio seems to be my personal preference, definitely looking forward to checking out the Xoom.

I think mine is going back as well. Lack of Market is a killer. I can't even use appslib.

i9020T (OEM unlocked) 2.3.4 rooted using SuperOneClick 1.9.1

I don't know am I lucky or something.
Story: I manually update from 2.3.3 (with supercurio kernel) to stock 2.3.4.
OH NO!!! Low contrast comes back.
I tried some method to root the phone in order to use ROM manager (clockworkmod) but I got no success, but I did an experiment to flash the kernel using adb (I flash netarchy kernel extracted from this package http://forum.xda-developers.com/showthread.php?t=936219 ) with the following command:
cd\
cd (your adb tools location)
fastboot flash boot netarchy.img (make sure you copied the kernel to that directory to avoid hassle)
After that, I tried to run superoneclick 1.9.1 http://forum.xda-developers.com/showthread.php?t=803682 again using GingerBreak and this time it's working!!! (I was prompted to install busybox during root process).
After I restarted the phone, it's really rooted (I can use ROM manager and Root Explorer) and I run ROM manager again to flash clockworkmod and reboot to recovery. I picked this package to flash http://forum.xda-developers.com/showthread.php?t=949292 (get stock 2.3.4 version).
When you are in recovery, choose install zip package and MAKE SURE YOU TOGGLE SIGNATURE CHECK to bypass, and flash the James Bond kernel as well as other drivers.
Now my NS got "old color/contrast" and rooted. YAY!!!
Here is the log:
Code:
SuperOneClick v1.9.1.0
Checking drivers...
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Getting OS Version...
2.3.4
OK
2.3.4
Pushing GingerBreak...
1264 KB/s (16830 bytes in 0.013s)
OK
chmod GingerBreak...
OK
Running GingerBreak...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
OK
Starting ADB Server...
OK
Waiting for device...
OK
Running GingerBreak...
ROOTED
Pushing busybox...
3305 KB/s (1062992 bytes in 0.314s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/platform/s3c-sdhci.0/by-name/system
OK
Remounting system with read-write access...
OK
Pushing su-v2...
693 KB/s (26264 bytes in 0.037s)
OK
chmod su...
OK
Pushing Superuser.apk...
2369 KB/s (196521 bytes in 0.081s)
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Checking for busybox
Copying busybox (/system/xbin/)...
OK
chmod busybox (/system/xbin/)...
OK
Installing busybox (/system/xbin/)...
OK
Remounting system with read-only access...
OK
Running a SU test...
Success!
Don't forget to reboot!
note: my NS is OEM unlocked

Will this work on my Nexus S running 2.3.4? About Phone Info shows the following:
Baseband Version = i9020XXKD1
Kernel version 2.6.35.7-ge382d80
[email protected] #1
Build number = GRj22
The boot loader is already unlocked.
Thanks in advance!

Anubis2k12 said:
Will this work on my Nexus S running 2.3.4? About Phone Info shows the following:
Baseband Version = i9020XXKD1
Kernel version 2.6.35.7-ge382d80
[email protected] #1
Build number = GRj22
The boot loader is already unlocked.
Thanks in advance!
Click to expand...
Click to collapse
It should work with i9020 as well. The only difference is for T-Mobile US (as long as 3G is 900/AWS/2100).

It's funny, I didn't like the fixed colors Google did to the Nexus S in 2.3.3 and higher but oh well and I got used to it... Then I was trying out some kernels (netcharty, etc.. that has "fixed" colors)...and it was back to the old way before Google fixed it.... and man holy cow, it's horrible. I can clearly see now how people were saying the original Nexus S colors were REALLY BLUE. heh.

[Q] How to tell if rooted correctly?

I followed the BurritoRoot method on my KF 6.2.1. I have installed the marketplace, a new launcher, and lots of other apps.
All I wanted to do was change the permission to stop the wallpaper rotation. However when i browse with ES File Explorer, I get "empty folder" if I look in /data. So I attempted to open the setting of ES File Explorer and select "Root Explorer". and it told me Sorry test failed unable to run this feature on your phone.
Finally I downloaded a program called "Root Check" and clicked Verify Root Access, its gives me "Sorry, you don't have root access."
However the fact I can install all these apps, etc leads me to believe I do have access.
One last this. I have a Nexus S 4g root, and it often prompts me to to use superuser app, I am not seeing this on the KF.
I do have GO Task manager widget, that shows the superuser icon as loaded.
I am very confused. In the end all I wanted was to stop the blasted wallpaper changer. HA!
ty!

crimsontide said:
I followed the BurritoRoot method on my KF 6.2.1. I have installed the marketplace, a new launcher, and lots of other apps.
All I wanted to do was change the permission to stop the wallpaper rotation. However when i browse with ES File Explorer, I get "empty folder" if I look in /data. So I attempted to open the setting of ES File Explorer and select "Root Explorer". and it told me Sorry test failed unable to run this feature on your phone.
Finally I downloaded a program called "Root Check" and clicked Verify Root Access, its gives me "Sorry, you don't have root access."
However the fact I can install all these apps, etc leads me to believe I do have access.
One last this. I have a Nexus S 4g root, and it often prompts me to to use superuser app, I am not seeing this on the KF.
I do have GO Task manager widget, that shows the superuser icon as loaded.
I am very confused. In the end all I wanted was to stop the blasted wallpaper changer. HA!
ty!
Click to expand...
Click to collapse
If you used BurritoRoot and you were able to successfully install the Market, then you likely have root.
Easiest and simplest way to 100% know is connect your KF to your PC. Run the following:
Code:
adb shell
su
If it says "su: Permission Denied" you don't have root (or at least it is not currently enabled). If it just gives you a prompt run:
Code:
id
If it comes back and says "uid=0(root) gid=0(root)" then you are good.

Make sure you use the superuser posted in the burritoroot post. There was one posted originally that was no good with the kindle fire but they updated to a working one.
Sent from my HD7 T9292 using XDA Windows Phone 7 App

if you want to know your kindle is rooted, use root checker, installed it on you KF and check.
http://www.mediafire.com/?jj8sx4ojvq9i198

litotamez said:
if you want to know your kindle is rooted, use root checker, installed it on you KF and check.
I tried that app and it reports, "Sorry, you don't have root access."
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac devices
List of devices attached
7766000600000001 device
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac shell
$ su
su: permission denied
$
Looks like I have some more work to do, and I am not sure where to start.
I have installed on the KF:
BurritoRoot: Kindel Fire Edition 1.0.0
version 1.0.0
SuperUser version 3.0.6
Click to expand...
Click to collapse

Ok I went back and re-ran everything. Had to uninstall SuperUser in the middle, but things seem to be working better now!!!
HTML:
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac root
adbd is already running as root
Traveler:KindleFireRootMacLinux crimsontide$ adb push su /system/xbin/su
-bash: adb: command not found
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac push su /system/xbin/su
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac shell chown 0.0 /system/xbin/su
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac shell chmod 06755 /system/xbin/su
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac install Superuser.apk
4426 KB/s (785801 bytes in 0.173s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac install Superuser.apk
2858 KB/s (785801 bytes in 0.268s)
pkg: /data/local/tmp/Superuser.apk
Success
Traveler:KindleFireRootMacLinux crimsontide$ ./adb-mac reboot

[Q] ADB Remount: Remount failed: Operation not permitted

So I was trying earlier to use ADB while trying to add WIFI to one of the ROMs.. I guess I mistyped something and now it is giving me this error..
How can I fix this? It's not really irking me but sometimes I just want to push a file through ADB and I don't want to keep having this error..
Code:
C:\adt-bundle-windows\sdk\platform-tools>adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount failed: Operation not permitted
C:\adt-bundle-windows\sdk\platform-tools>adb remount
remount failed: Operation not permitted
C:\adt-bundle-windows\sdk\platform-tools>adb devices
List of devices attached
003cf8f9ded1abcc device
C:\adt-bundle-windows\sdk\platform-tools>adb root
adbd cannot run as root in production builds
C:\adt-bundle-windows\sdk\platform-tools>adb remount
remount failed: Operation not permitted
C:\adt-bundle-windows\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
C:\adt-bundle-windows\sdk\platform-tools>adb root
adbd cannot run as root in production builds
C:\adt-bundle-windows\sdk\platform-tools>adb remount
remount failed: Operation not permitted
C:\adt-bundle-windows\sdk\platform-tools>
For some reason if I delete the whole adt-bundle-windows and extract it again from the .zip file.. It mounts but keeps getting the error
Code:
C:\adt-bundle-windows\sdk\platform-tools>adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount failed: Operation not permitted
I'll be going to sleep soon, so if you need me to do something, I might not get back to you till morning.
Thanks for helping me!

You need an insecure kernel to have root in adb. Or root your phone.

klin1344 said:
You need an insecure kernel to have root in adb. Or root your phone.
Click to expand...
Click to collapse
i'm using franco.kernel - test 5.. and i am rooted? i can use supersu, ti backup, root explorer
Sent from my Nexus 4 using Tapatalk 2

Bump, any help on this?

Bumping this. I am having the same issue. Rooted on the latest stock andriod. Custom kernel as well.

You need an insecure boot.img
Either download the one on this post or enable root over adb if you are running CyanogenMod or AOKP.

Use the set of commands in the sticky.
Doesn't need an insecure kernel.

I've had this happen before. I fixed it by first killing adb with "adb kill-server", then do "adb root" to make adb run as root. Then you can "adb remount" to write to the filesystem, then push away! Hope that helps.

ess.boyer said:
I've had this happen before. I fixed it by first killing adb with "adb kill-server", then do "adb root" to make adb run as root. Then you can "adb remount" to write to the filesystem, then push away! Hope that helps.
Click to expand...
Click to collapse
This worked for me. I was pulling my hair out trying to get the system rw. adb root, did the trick. Make sure you set the phone in to root for adb in Settings/Developer option/Root Access

You are the f'ing man.

What is "adb kill-server".
ess.boyer said:
I've had this happen before. I fixed it by first killing adb with "adb kill-server", then do "adb root" to make adb run as root. Then you can "adb remount" to write to the filesystem, then push away! Hope that helps.
Click to expand...
Click to collapse
@ess.boyer;35057736 , thanks in advance , boss I am new user of android. I use Lenovo A789(ICS 4.0.4, MKT6577 from China) .I have rooted by mobile with SP_Flash_Tool_v3.1222.00 . Now I have remount problem. I want to solve it. What is "adb kill-server" . How can I get"adb kill-server"
and how can I able "adb remount" to write to the filesystem . Please help.

GUYS GUYS
i had this problem with Cyanogen and my kernel is Googy max
ye ADB ROOT command will work. But you can use adbd insecure APP and you don't need adb root command any more

what do i do with the img file??

No root method works for e400!! lg l3

ive tried cydia impactor superoneclick and spectrum window and bin4ry none of them are working to root the phone
which method currently works to root stock lg e400?
please develop a new method for rooting lg e400

bug 8219321 and 9950697 are being shown as unpatched on this firmware V10L june 7 2013
still no root exploit is working.

Moved here as this does not belong in the Development Section, please read the Forum Rules on posting....

Judge Joseph Dredd said:
Moved here as this does not belong in the Development Section, please read the Forum Rules on posting....
Click to expand...
Click to collapse
thanks this problem has been solved:good:

psychem said:
thanks this problem has been solved:good:
Click to expand...
Click to collapse
Did you root your phone? I can help you if not.

Ckovvi said:
Did you root your phone? I can help you if not.
Click to expand...
Click to collapse
ya i have rooted it

Please tell me how to root it.i have tried all methods my version is v10L.

ragunathan said:
Please tell me how to root it.i have tried all methods my version is v10L.
Click to expand...
Click to collapse
have you tried this?
http://forum.xda-developers.com/showthread.php?p=56495206
Sent from my LG-P705 using XDA Free mobile app

Tried iroot but says no roo permission.

ragunathan said:
Tried iroot but says no roo permission.
Click to expand...
Click to collapse
thats strange it should root your phone with out any problems.
Sent from my LG-P705 using XDA Free mobile app

Screenshot

Bro the only rooting method working with L3 is Superoneclick with Rageagainstthecage (version 1.7)
To run the exploit you must change the exploit engine from pseneuter to rageagainstthecage.All other methods don't work.
Inviato dal mio LG-E400 con Tapatalk 2

I tried the method described above, this one also crashes on looking for device. I got usb debugging on, latest drivers installed and full battery. The phone has the last software, which is V10j-OCT-17-2012. Android version 2.3.6.
I have seen other LGL3/E400 phones rooted, so what am I doing wrong here and how can I actually root my phone then?
Thanks in advance.
410172_Chief

It might just be the software version that is not compitable with the current rooting methods. Is there a way to downgrade my LG L3/E400 to a firmware that is rootable?
With the firmware of my device, 10J, it says E400GO. It is from Vodafone, The Netherlands. Don't know if that information will help but you never know.
So I am trying to root my LG L3 E400GO. Who knows how to do the trick?
Oh my...
SuperOneClick v1.7.0.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
5 KB/s (5392 bytes in 1.000s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
ROOTED
Pushing busybox...
1462 KB/s (1062992 bytes in 0.710s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/mmcblk0p14
OK
Reading OS Version properties...
Version: 2.3.6
OK
Remounting system with read-write access...
OK
Pushing su-v2...
2565 KB/s (26264 bytes in 0.009s)
OK
chmod su...
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Copying busybox (/system/xbin/)...
OK
chmod busybox (/system/xbin/)...
OK
Installing busybox (/system/xbin/)...
OK
Pushing Superuser.apk...
4797 KB/s (196521 bytes in 0.040s)
OK
Remounting system with read-only access...
OK
Running a SU test...
Success!
Though it did not reboot at all, I might have just rooted it.

410172 said:
It might just be the software version that is not compitable with the current rooting methods. Is there a way to downgrade my LG L3/E400 to a firmware that is rootable?
With the firmware of my device, 10J, it says E400GO. It is from Vodafone, The Netherlands. Don't know if that information will help but you never know.
So I am trying to root my LG L3 E400GO. Who knows how to do the trick?
Oh my...
SuperOneClick v1.7.0.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
5 KB/s (5392 bytes in 1.000s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
ROOTED
Pushing busybox...
1462 KB/s (1062992 bytes in 0.710s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/mmcblk0p14
OK
Reading OS Version properties...
Version: 2.3.6
OK
Remounting system with read-write access...
OK
Pushing su-v2...
2565 KB/s (26264 bytes in 0.009s)
OK
chmod su...
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Copying busybox (/system/xbin/)...
OK
chmod busybox (/system/xbin/)...
OK
Installing busybox (/system/xbin/)...
OK
Pushing Superuser.apk...
4797 KB/s (196521 bytes in 0.040s)
OK
Remounting system with read-only access...
OK
Running a SU test...
Success!
Though it did not reboot at all, I might have just rooted it.
Click to expand...
Click to collapse
Yea it doesn't reboot...i did three phones like that yesterday.
Yes man!You rooted it!
Check for the superuser app in your app drawer.
Inviato dal mio LG-E400 con Tapatalk 2