Database Info

{TUToRIAL]HOW TO DEODEX I9001 FOR NOoBS

HOW TO DEODEX YOUR I9001
THIS IS A SIMPLE GUIDE FOR THE NOOBS SO THAT THEY CAN DEODEX THERE I9001
What you'll need:
A Windows based machine
JDK
ANDROID SDK
LATEST XULTIMATE
And A Rooted I9001
Process:
1. Unzip xUltimate v2.2, and launch "Main.exe"
2. If everything goes well xUltIMATE should recognize the phone and make a connection. You now should see a list of options.
3. Run option 1. After option 1 is done, run option 2.
4. Now these well take a while. Run option 3.
5. IMPORTANT: After you have run option 3
6. Now run option 4, and wait.
7. Exit xUltimate, and put the phone in USB mass storage.
8. Go back into the xUltimate folder and copy "done_frame", and "done_app", and move them to the root of the internal sdcard not in the external sd.
9. Now Put the phone in USB DEBUGGING mode and DON'T PUT THE PHONE IN MASS STORAGE MODE
10. Open a command prompt, and do the following:
Code:
$ su
# stop
# mount -o remount rw /system
# rm /system/app/*.odex
# rm /system/framework/*.odex
# cp /sdcard/done_app/* /system/app/
# cp /sdcard/done_frame/* /system/framework/
# mount -o remount ro /system
# reboot
Credits to -
Xeodoxus for xultimate
Ghostlypickel for this guide
DO THIS AT YOUR OWN RISK
IF YOU LYK MY POST THEN PLEASE PRESS THE THANKS BUTTON
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

RESERVED...

RESERVED..........

For Android 2.3.x using this command
busybox cp /sdcard/done_app/* /system/app/
busybox cp /sdcard/done_frame/* /system/framework/

Maybe a stupid question but what are the benefits when I'm deodex my i9001?
Sent from my GT-I9001 using XDA App

oudbrood said:
Maybe a stupid question but what are the benefits when I'm deodex my i9001?
Sent from my GT-I9001 using XDA App
Click to expand...
Click to collapse
it is easier to make themes/mods for deodexed firmware

@ oudbrood
and you will got more space in system

Thanks for the reply's.
I get smarter every day
Sent from my GT-I9001 using XDA App

Not understand something here...does the phone always on usb? No plug in n plug out usb? The commant have to type where? Pc? Like this...start-run-cmd-enter?
GT-I9001 Adrenaline Shot - powered by Instanet free edition

Lol, thread looks familiar
kkrraazzyy said:
3. Run option 1. After option 1 is done, run option 2.
4. Now these well take a while. Run option 3.
5. IMPORTANT: After you have run option 3
6. Now run option 4, and wait.
Click to expand...
Click to collapse
Can be done in one step (option 5 - Pull and Deodex all).
Note that deodexing (steps 3 and 4) sometimes returns errors. Just repeat the procedure and it will work a second (or third) time...
kkrraazzyy said:
10. Open a command prompt, and do the following:
Click to expand...
Click to collapse
You can also make a batch file to move files from the xUltimate folder onto your device (put this patch-file into the xUltimate folder - this will not use the sdcard and push the files directly onto the device!). Something like this:
Code:
@echo off
jar\adb -d remount
jar\adb -d push done_app /system/app
jar\adb -d push done_frame /system/framework
echo all ok? going to remove *.odex files...press a key to continue...
pause >nul
jar\adb -d shell rm /system/app/*.odex
jar\adb -d shell rm /system/framework/*.odex
jar\adb -d remount
echo rebooting...press a key to continue...
pause >nul
jar\adb -d reboot
pause
---------- Post added at 08:31 AM ---------- Previous post was at 08:29 AM ----------
pyronia said:
Not understand something here...does the phone always on usb? No plug in n plug out usb? The commant have to type where? Pc? Like this...start-run-cmd-enter?
Click to expand...
Click to collapse
Yes, running Main.exe and deodexing requires the device to be plugged into USB. Using ADB also uses USB, although you can do it from your device too with shell tools. And if you want an automated DOS script for moving the files using ADB, see above
---------- Post added at 08:42 AM ---------- Previous post was at 08:31 AM ----------
One more thing: you need BusyBox too:
https://market.android.com/details?id=stericson.busybox

do i have to flash again tweak like adrenaline shot after deodexing???

pyronia said:
do i have to flash again tweak like adrenaline shot after deodexing???
Click to expand...
Click to collapse
No, it does not touch any of those (Adrenaline, Root, CWM, etc.)

Hahaha...i just back from bootloop....i think it will not workout for me...
GT-I9001 Adrenaline Shot - powered by Instanet free edition

pyronia said:
Hahaha...i just back from bootloop....i think it will not workout for me...
GT-I9001 Adrenaline Shot - powered by Instanet free edition
Click to expand...
Click to collapse
Lol, glad you're still laughing so how did you do it? On which base-ROM? I've done it several times and never had any issues...

nikagl said:
Lol, glad you're still laughing so how did you do it? On which base-ROM? I've done it several times and never had any issues...
Click to expand...
Click to collapse
ZSKP6...it stuck when i try to use terminal modulator...all apps fc then bam!!! Mr. Bootloop came out after remove battery....
GT-I9001 Adrenaline Shot - powered by Instanet free edition

So...using shell other than adb doesn't work tx 4 testing )
Sent from my GT-I9001 using XDA App

It doesn't work with the shell on your mobile since when u type "stop" it totally freezes.. ADB SHELL IS REQUIRED. the poster might want to say that since this is just a 100% copy of the deodex I9003 tutorial
when i tried it my phone got in a bootloop tho.. but I will try later again

I used ADB and it works. No bootloop or errors

to deodex always use ADB
and be sure that you have busybox installed on your device
otherwise the commands cant be executed

Guys, what am I doing wrong?
- Rooted XXKPS
- Ran main.exe ok with all steps.
- All okay until "(busybox) cp /sdcard/done_app/* /system/app/"
It can't find my sdcard.. I'm sure I have the files placed in the root of the internal sdcard.

[Guide] How to Downgrade Latest Hboot 2.00.0002>> without using HTC Dev V2

This method works for software version 2.11 and above and doesn't work for version 2.10 below.. Please use zegRush if this doesn't work for you.
FOR PHONES THAT ARE NOT ROOTED
Note: For locked bootloaders only. Do not use Htc dev prior to using this guide.
First thanks to:
1. mtothearkus
2.petarpLab..
3.jcase for TacoRoot..
4. amidabuddha
5.zryvffn (misc_version_universal)
I AM NOT RESPONSIBLE FOR ANYTHING THAT MAY HAPPEN TO YOUR DEVICE..
This was tested on latest OTA ASIA 2.15.xx with latest Hboot 2.00.0002.
Latest 2.15 cannot be rooted with zegRush so did some research..
Things Needed:
1.tacoroot
2.misc_version (download attachments below)
3.OLDEST RUU for your "REGION/ BRAND".. i repeat, specific region to avoid customer ID error.
4. adb (you know how it works)
5. phone in USB debugging mode.
STEPS:
1. download tacoroot and misc and put all files in your desired directory.
2. Run terminal and change location to where you files are.
3. now type:
Code:
adb push tacoroot.bin /data/local/tmp/tacoroot
adb push misc_version /data/local/tmp/
4.After pushing all the files, run tacoroot by typing:
Code:
adb shell
chmod 777 /data/local/tmp/*
/data/local/tmp/tacoroot --setup
5. After this commands your phone "REBOOT" the phone to recovery. Now press vol up then power then REBOOT to boot the phone normally. Wait till it boots completely and then type:
Code:
adb shell
/data/local/tmp/tacoroot --root
6.This command will gets you out of adb shell.. so we need to get back to adb shell and you will see "#" sign..meaning you are temp rooted and we can then proceed to changing MISC_VERSION:
Code:
adb shell
cd /data/local/tmp
./misc_version -s 1.27.405.6
7. After its done you can now flash your "REGION/ BRAND specific RUU".
8. After your done with RUU. Proceed to http://revolutionary.io..
Happy Flashing
FOR ROOTED PHONES
*Proceed with:
STEP 3
STEP 6
STEP 7
STEP 8
-Done
*Added misc_version_universal thanks to zryvffn

Thx you are marvelous! I will try it later
Sent from my HTC Desire S using XDA App

scan6 said:
Thx you are marvelous! I will try it later
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
Say if you did it by this procedure.

Yes! it works very wellwith my version 2.13 to1.47
It's quite easy to do it
Thx a lot!
Sent from my HTC Desire S using XDA App

Thx for the guide. Worked great. I downgraded from 2.15 to 1.31 asia wwe.
From my Desire S Using XDAP

Hey man, I've added your guide to my thread http://forum.xda-developers.com/showthread.php?t=1186401
Just to let you know. Thanks for the great guide.

nodeffect said:
Hey man, I've added your guide to my thread http://forum.xda-developers.com/showthread.php?t=1186401
Just to let you know. Thanks for the great guide.
Click to expand...
Click to collapse
hey dude thanks.. btw this guide is for those who can't downgrade using mtothearkus method.. those recent 2.15.x versions..its just the same but it uses different root methods.. all credits to mtothearkus..appreciate it dude..thanks..

Thanks, noted.

After rebooting phone from recovery, typing
adb shell
/data/local/tmp/tacoroot --root
Answer:
Rebooting into root.
cannot create /data/local.prop: permission denied
and phone restart...
Desire S, Android 2.3.5, Hboot 2.00.0002

qpkqkma said:
After rebooting phone from recovery, typing
adb shell
/data/local/tmp/tacoroot --root
Answer:
Rebooting into root.
cannot create /data/local.prop: permission denied
and phone restart...
Desire S, Android 2.3.5, Hboot 2.00.0002
Click to expand...
Click to collapse
Dude what your software version number? brand if any?.. if this root doesnt work.. try zegRush method..
or try this
Update to latest available firmware, then try.
If that fails, do a factory reset and try.

Software : 2.10.401.8
Kernel: 2.6.35.10
Non-branded, lastest firmware.
Late I´ll try factory reset.

qpkqkma said:
Software : 2.10.401.8
Kernel: 2.6.35.10
Non-branded, lastest firmware.
Late I´ll try factory reset.
Click to expand...
Click to collapse
Zergrush method from mtothearkus's thread should work for you

qpkqkma said:
Software : 2.10.401.8
Kernel: 2.6.35.10
Non-branded, lastest firmware.
Late I´ll try factory reset.
Click to expand...
Click to collapse
That's it.. hehe. 2.10 is an old firmware.. ASIAN OTA is 2.15.. so try the zegrush method.. this tut was developed for those who can't root using the zegRush..thanks amidabuddha..=)

Signed up here at xda just to say that this worked nicely on my Desire S.
I had difficulty making the ADB code given by shadi22 work at first, but after redoing them and just copy pasting them in terminal, they worked. My Desire S also had an Asia 2.15 ROM and 2.00.0002 Hboot. Used the Asia WWE 1.48.707.1 RUU to downgrade the HBOOT after changing the misc-version and tacorooting, then Revolutionary all the way
At first, I thought that I made a mistake choosing this phone (My Desire's display got borked and SISPH's repair quote was way too expensive for a nearly two year old device ) because of the need to downgrade the hboot before getting S-OFF, but shadi22's method is probably the most elegant of all the S-OFF methods on 2.00.0002 devices

HAHAHA.. thanks dude.. Anyway.. SISPH are full of dumb people.. i had problem with my device too.. a green dot on an LCD screen. my phones on warranty but never had it repaired since they have no replacement part yet. so give up on the idea for that damn SISPH.. They had the worst customer service.. they should never have been contracted with HTC on the first place.. No HTC on my next phone. The reason to go with HTC was mainly for the developers in this beloved site.. But now im seeing great dev from other phone section..=)

Try to do a zergRush method. Everything run fine, i do steps 1-5, do a step 6 (run RUU etc etc.) but RUU say me error updating, phone stuck on HTC logowhen i pull out cable it load in HBOOT and say "RUU Security Fail ! Update Fail!".
Sucks.....im downloading RUU with SW 2.10.401.8 to recover phone.....
Any other method ?

Hey guys,
So I tried this method but encountered the following issue as shown in the image below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does anyone have any ideas as to where I have went wrong?
Kind regards,
DJM.

dontjudgemekk said:
Hey guys,
So I tried this method but encountered the following issue as shown in the image below:
Does anyone have any ideas as to where I have went wrong?
Kind regards,
DJM.
Click to expand...
Click to collapse
Off hand I would say that /data/local/tmp was not empty before you started and contains more than just the 2 files you copied there, thus the command chmod 777 /data/local/tmp/* is failing.
Why not just do 2 chmod commands for the 2 files you copied?

tpbklake said:
Off hand I would say that /data/local/tmp was not empty before you started and contains more than just the 2 files you copied there, thus the command chmod 777 /data/local/tmp/* is failing.
Why not just do 2 chmod commands for the 2 files you copied?
Click to expand...
Click to collapse
How would I clear the /data/local/tmp directory?
Can you phrase what you mean by performing 2 chmod commands for the 2 files better? I dont understand what you mean unfortunately. Are you referring to the tacoroot.bin and misc_version files?

dontjudgemekk said:
How would I clear the /data/local/tmp directory?
Can you phrase what you mean by performing 2 chmod commands for the 2 files better? I dont understand what you mean unfortunately. Are you referring to the tacoroot.bin and misc_version files?
Click to expand...
Click to collapse
Yes after you create the adb shell and get the $ prompt type:
chmod 777 /data/local/tmp/misc_version
chmod 777 /data/local/tmp/taco root.bin

root auxus core x2 3g using Android Debug Bridge ADB

Build Properties of Auxus Core X2 3G contains the ro.build.user=root by default firmware update and also Default Properties contains ro.secure=0, ro.debuggable=1. So rooting the devices made very easy.
The following are the things to do to get root access in the front end
Update the binary of the Superuser
Setting the chown & chmod to the Superuser binary
Install the Superuser.apk
Optional:Installing the Root Checker & Root Unistaller
The following are the files required to do the above
ADB Driver for the Rockchip board (Auxus Core X2 Shipped with RK3066)
ADB file & ADB library files
Latest Superuser binary & apk files
Optional:Rootchecker & Root Uninstaller files
Source:
ADB Driver : XDA Post (http://78.140.134.121/d/6ea124157e9cda25ab1707cbcba7/usb_driver.zip)
ADB Files : http://forum.xda-developers.com/showthread.php?t=1987280
SU Files : http://downloads.androidsu.com/superuser/
Optional:RootCheck: http://joeykrim.com/
Optional: RootUnistaller:http://www.apkmania.co/2012/12/root-uninstaller-pro-v32-apk.html
Customizing the folder for the Auxus
Create folder e.g., C:\Auxus\
Extract the ADB files and Copy the adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll to Auxus
Extract the Superuser files and Copy the \system\app\Superuser.apk and \System\bin\su to Auxus
Optional:Also place the RootCheck & RootUnistaller apk
Creating batch file named ROOT.bat
Creating batch file : ROOT.bat
The following code to be added to batch file
Code:
echo off
echo Check list of devices connected
adb devices
pause
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
echo Rebooting 1/3
adb reboot
echo After Reboot to home screen unlock and press any key
pause
echo Setting Kernel Properties
adb shell rm /data/local.prop > nul
adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
echo Rebooting 2/3
adb reboot
echo After Reboot to home screen unlock and press any key
pause
adb shell id
pause
echo ADB Mounting root drive
adb remount
echo Pushing Superuser files
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
echo Removing changes except ROOT
adb shell rm /data/local.prop
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.bak /data/local/tmp
echo Installing application
adb push superuser.apk /system/app/superuser.apk
echo Rebooting 3/3
adb reboot
echo ROOTED
pause
Also append below code if optionals downloaded
Code:
echo ADB Mounting root drive
adb remount
echo Installing Root Check & Root Uninstall
adb push Root_Uninstaller_Pro.apk /system/app/Root_Uninstaller_Pro.apk
adb push RootCheckPro.apk /system/app/RootCheckPro.apk
echo Done
pause
echo Rebooting
adb reboot
echo After Reboot to home screen unlock and press any key
pause
Steps to root
Install the ADB driver by double clicking the DPInst-32bit.exe
Now windows will prompt for the Driver security - Click Install anyway to proceed
Now connect the Auxus Core X2 3G in USB Debugging mode, the driver will be identified by windows (if not restart)
Now run the ROOT.bat (Run as Administrator)
The tablet will be reboot 3 times (if optional files used reboot 4 times)
Now run the ROOT.bat file and Auxus Core X2 3G rooted successfully.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer :
Though tested many times with my tablet and the post drafted carefully. Kindly Backup data before proceed; All the files download from various link from internet and the attachment (Auxus.rar) contains the combination of them. Screenshots generated by author.
ROOT AT YOUR OWN RISK. Author is not responsible for what you do on your device. Author is not responsible for liability of any kind.

combined attachment included
Update: Auxus.rar is combination made from the above said link and with root batch files. ROOT AT YOUR OWN RISK. Author is not responsible for what you do on your device. Author is not responsible for liability of any kind.

Thanks a bunch!!
I will try this method on my corex2 this weekend and let you know the result. Thanks a lot!:good:

my tabs back camera is very slow and lagging in preview, does anyone having corex2 3g can confirm?

Rear camera- laggy- known issue
guyton100 said:
my tabs back camera is very slow and lagging in preview, does anyone having corex2 3g can confirm?
Click to expand...
Click to collapse
Yes, this is a known issue with the CoreX2. Lets hope that they will fix this issue with future firmware updates.

Please tell me how to unroot the same

Kudremukh said:
Please tell me how to unroot the same
Click to expand...
Click to collapse
muruggan_a has reported a post.
Reason:
Hi Friends,
I have done a pre-booking of X2 3G, i have faced the following issues
1) I was unable to send any 2010 MS office documents from win 7 laptop to auxus x2 3g
2)Even after i paired my tablet with my laptop, i cannot connect the media service from my tablet to laptop using bluetooth
3)Nokia BT head set doesnt get paired
And my last query is if i can root the device whether i can use 3G dongle instead of using SIM slot?
Please help me,
I have handedover to iberry service center and asked for replacement because of the bluetooth issue which i mentioned above. I got the replacement device but that also have the same problem. The new device had some scratches behind so given them back and asked for replacement.

Device Not found
When I oopen ROOT.bat In,
Win 8 it says error:device not found
Win 7 it says path not recognized or something like that
plz help me how to fix it and the
ADB unknown USB driver you gave when i open it win rar says that the file is corrupted or what i dont know
plz help me here:crying:

Will this work for Auxe CoreX4?
skv_vlr_mech said:
Build Properties of Auxus Core X2 3G contains the ro.build.user=root by default firmware update and also Default Properties contains ro.secure=0, ro.debuggable=1. So rooting the devices made very easy.
The following are the things to do to get root access in the front end
Update the binary of the Superuser
Setting the chown & chmod to the Superuser binary
Install the Superuser.apk
Optional:Installing the Root Checker & Root Unistaller
The following are the files required to do the above
ADB Driver for the Rockchip board (Auxus Core X2 Shipped with RK3066)
ADB file & ADB library files
Latest Superuser binary & apk files
Optional:Rootchecker & Root Uninstaller files
Source:
ADB Driver : Unknown (http://78.140.134.121/d/6ea124157e9cda25ab1707cbcba7/usb_driver.zip)
ADB Files : http://forum.xda-developers.com/showthread.php?t=1987280
SU Files : http://downloads.androidsu.com/superuser/
Optional:RootCheck: http://joeykrim.com/
Optional: RootUnistaller:http://www.apkmania.co/2012/12/root-uninstaller-pro-v32-apk.html
Customizing the folder for the Auxus
Create folder e.g., C:\Auxus\
Extract the ADB files and Copy the adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll to Auxus
Extract the Superuser files and Copy the \system\app\Superuser.apk and \System\bin\su to Auxus
Optional:Also place the RootCheck & RootUnistaller apk
Creating batch file named ROOT.bat
Creating batch file : ROOT.bat
The following code to be added to batch file
echo off
echo Check list of devices connected
adb devices
pause
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
echo Rebooting 1/3
adb reboot
echo After Reboot to home screen unlock and press any key
pause
echo Setting Kernel Properties
adb shell rm /data/local.prop > nul
adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
echo Rebooting 2/3
adb reboot
echo After Reboot to home screen unlock and press any key
pause
adb shell id
pause
echo ADB Mounting root drive
adb remount
echo Pushing Superuser files
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
echo Removing changes except ROOT
adb shell rm /data/local.prop
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.bak /data/local/tmp
echo Installing application
adb push superuser.apk /system/app/superuser.apk
echo Rebooting 3/3
adb reboot
echo ROOTED
pause
Also append below code if optionals downloaded
echo ADB Mounting root drive
adb remount
echo Installing Root Check & Root Uninstall
adb push Root_Uninstaller_Pro.apk /system/app/Root_Uninstaller_Pro.apk
adb push RootCheckPro.apk /system/app/RootCheckPro.apk
echo Done
pause
echo Rebooting
adb reboot
echo After Reboot to home screen unlock and press any key
pause
Steps to root
Install the ADB driver by double clicking the DPInst-32bit.exe
Now windows will prompt for the Driver security - Click Install anyway to proceed
Now connect the Auxus Core X2 3G in USB Debugging mode, the driver will be identified by windows (if not restart)
Now run the ROOT.bat (Run as Administrator)
The tablet will be reboot 3 times (if optional files used reboot 4 times)
Now run the ROOT.bat file and Auxus Core X2 3G rooted successfully.
Disclaimer :
Though tested many times with my tablet and the post drafted carefully. Kindly Backup data before proceed; All the files download from various link from internet and the attachment (Auxus.rar) contains the combination of them. Screenshots generated by author.
ROOT AT YOUR OWN RISK. Author is not responsible for what you do on your device. Author is not responsible for liability of any kind.
Click to expand...
Click to collapse
Will the above procedure work for the Corex4 as well?

guyton100 said:
my tabs back camera is very slow and lagging in preview, does anyone having corex2 3g can confirm?
Click to expand...
Click to collapse
yes, it is there, but front camera is good. I posted support query in manf webpage and searching the firm update to make custom rom

cdwarak said:
Will the above procedure work for the Corex4 as well?
Click to expand...
Click to collapse
try root methods of Samsung Exynos 4412 for CoreX4 3g

iNOXIA2012 said:
When I oopen ROOT.bat In,
Win 8 it says error:device not found
Win 7 it says path not recognized or something like that
plz help me how to fix it and the
ADB unknown USB driver you gave when i open it win rar says that the file is corrupted or what i dont know
plz help me here:crying:
Click to expand...
Click to collapse
If Root.bat not worked manual use the code as mentioned in the thread.
I'm using windows 7 only and also verified with the XP.
Try downloading the files from source links. If device not recognized then it is the issue of the USB driver installation; Also refer the Screenshots and steps in the post

Kudremukh said:
Please tell me how to unroot the same
Click to expand...
Click to collapse
in command prompt, path to the adb folder
adb remount
adb shell rm /system/app/superuser.apk
adb shell rm /system/bin/su
adb reboot
and so on...

!!!Rooted!!! This method works like a charm. Thanks man!! Trying to figure out if we have cwm recovery for corex2. I tired a couple of them meant for other rockchip 3066 devices but no dice.

clockworkmod-recovery-for-auxus-core-x2
s.rahus said:
!!!Rooted!!! This method works like a charm. Thanks man!! Trying to figure out if we have cwm recovery for corex2. I tired a couple of them meant for other rockchip 3066 devices but no dice.
Click to expand...
Click to collapse
Check out for CWM
http://forum.xda-developers.com/showthread.php?p=37584364#post37584364

Link Error
ADB Driver URL that you gave wont work gives me Error

iNOXIA2012 said:
ADB Driver URL that you gave wont work gives me Error
Click to expand...
Click to collapse
Please find attachment file that i downloaded from the link what i mentioned in first post

skv_vlr_mech said:
please find attachment file that i downloaded from the link what i mentioned in first post
Click to expand...
Click to collapse
thank you so much

Great It worked flawlessly. I wasn't able to root using moborobo or Zhuo. But this method worked. Thanks

Has it got GPS or not???
Hi,
Can anyone please tell whether Auxus core X2 3G has got inbuild GPS or not.

[Q] Need Help Ramos W41 bootloop

Hi..
I have a Ramos W41
- quadcore ATM 7025
- RAM 1 GB DDR3
- GPU Vivante GC1000
and now my tablet is bootloop after I upgraded the OS to 4.2.2
I used tablet product tool to flashed it.
I forgot to enter the "ramosvendorapk.img" when I reflash
I try to reflash, the tablet doesn't detected on my PC, and now it's just stuck at the logo, and it can't to enter the recovery mode
please help me to solve this
thank you

Arhick said:
Hi..
I have a Ramos W41
- quadcore ATM 7025
- RAM 1 GB DDR3
- GPU Vivante GC1000
and now my tablet is bootloop after I upgraded the OS to 4.2.2
I used tablet product tool to flashed it.
I forgot to enter the "ramosvendorapk.img" when I reflash
I try to reflash, the tablet doesn't detected on my PC, and now it's just stuck at the logo, and it can't to enter the recovery mode
please help me to solve this
thank you
Click to expand...
Click to collapse
can you get it into recovery?

Try rebooting into recovery.. Then wipe data and cache.
Sent from my Qmobile Noir A10 using Tapatalk

keifus.rahn said:
can you get it into recovery?
Click to expand...
Click to collapse
mrtaim3 said:
Try rebooting into recovery.. Then wipe data and cache.
Sent from my Qmobile Noir A10 using Tapatalk
Click to expand...
Click to collapse
No, this tablet cannot enter the recovery mode
when I see in the buildprop, the recovery mode was disable by its factory, I also tried to enable
but still can't recovery

you must contact to the developer of this Tablet.

mrtaim3 said:
you must contact to the developer of this Tablet.
Click to expand...
Click to collapse
okay..don't you have a solution ?
I tried to contact the developer, but they don't reply yet..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Ur device is not in use of many ppl so its hard to find the solution of it.. The only way u can reset ur device is by going into recovery. or try resetting ur device through tablet tool. Or try reflashing.. Switch off the tablet connect it with usb.. And wait till it detects. Make sure u have installed ur tablet drivers.
Sent from my Qmobile Noir A10 using Tapatalk

mrtaim3 said:
Ur device is not in use of many ppl so its hard to find the solution of it.. The only way u can reset ur device is by going into recovery. or try resetting ur device through tablet tool. Or try reflashing.. Switch off the tablet connect it with usb.. And wait till it detects. Make sure u have installed ur tablet drivers.
Sent from my Qmobile Noir A10 using Tapatalk
Click to expand...
Click to collapse
thank you for your responds
my tablet is not detected on my PC, and when usb connected to my computer it's just charging..
the usb drivers is installed.
and this tablet not supported recovery mode, I already tried.

Arhick said:
thank you for your responds
my tablet is not detected on my PC, and when usb connected to my computer it's just charging..
the usb drivers is installed.
and this tablet not supported recovery mode, I already tried.
Click to expand...
Click to collapse
I feel sorry that i couldn't help you.. Take it to any repair shop or just wait for the developers to respond.

Arhick said:
Hi..
I have a Ramos W41
- quadcore ATM 7025
- RAM 1 GB DDR3
- GPU Vivante GC1000
and now my tablet is bootloop after I upgraded the OS to 4.2.2
I used tablet product tool to flashed it.
I forgot to enter the "ramosvendorapk.img" when I reflash
I try to reflash, the tablet doesn't detected on my PC, and now it's just stuck at the logo, and it can't to enter the recovery mode
please help me to solve this
thank you
Click to expand...
Click to collapse
So I've did some Research on your device and it seems like everyone is having the same problem and there seems that a fix hasn't been Resolved yet. But here are a few things you can try to resolve this issue... (1) If you can take the battery out plug it in to the charger / Then take the battery out and unplug /\ This is to make shure you have no power left in the device wait about a minit then place the battery back in and press the volume down for about 30 seconds and the press and hold the power button while holding the volume down key When the screen lights up let go of the power and keep holding volume down for 15 seconds that should give you some options on restoring your device if that dont work then try doing the same with vol up instead of down or try holding both volume keys and ive noticed that there is a restart hole next to the volume keys if so do the charger steps but with out the vol keys....Find somthing to press and hold the reset button and while holding the reset button power on the device and see if any luck..
(2) PC NEEDED WITH SDK if you have a pc and you have the android sdk set up u can try connecting to your device using / adb /echo/ if you dont have the sdk you can get it here with a tut on using adb= http://developer.android.com/sdk/index.html now if your ready here is a way to connect to your device threw adb... Using ADB as solution
ADB can be used to access the phone while booting, be aware that some bootloops make it unable to use ADB since they do not go further then the manufacturer logo. (In new CWM versions it’s possible to use adb)
The only tricky part about using ADB with bootloops is that you have to do it on the right time, this is different from every device, but normally it’s after the manufacturer logo that the partitions get mounted. The easiest way to enter your phone in this part is using a batch script that monitors the state of your device and connects directly when possible.
I use this script for example, called ondemand.bat (requires adb.exe and the 2 dlls)
1 @ECHO off
2 cd /d %~dp0
3 echo.
4 echo Waiting for device…
5 adb wait-for-device
6 echo.
7 adb -d shell stop
8 adb push mycwmfix.zip /sdcard/mycwmfix.zip
9 adb reboot recovery
Linux Version (ondemand.sh):
1 #!/system/bin/sh
2 echo " "
3 echo "Wating for device..."
4 ./adb wait-for-device
5 echo " "
6 ./adb -d shell stop
7 ./adb push mycwmfix.zip /sdcard/mycwmfix.zip
8 ./adb reboot recovery
This script will wait for the device to become ready, when it’s ready it freeze the device, so the script has more time to push the file (instead of keep rebooting). Then it will push the specified cwmfix zip to your sdcard, and after that it will reboot in recovery so you can install the cwm fix you made. You can also make an batch script that pushes the files automatically to your phone, here is an example:
(1 @ECHO off
(2)cd /d %~dp0
(3)echo.
(4)echo Waiting for device...adb wait-for-device
(5)echo.
(6)adb -d shell stop
(7)adb -d shell su -c "mount -o remount rw /system"
(8)adb push framework-res.apk /system/framework/framework-res.apk
(9)adb -d shell chmod 644 /system/framework/framework-res.apk
(10)adb push SystemUI.apk /system/app/SystemUI.apk
(11)adb -d shell chmod 644 /system/app/SystemUI.apk
(12)adb reboot
(13)Linux version:
1#!/system/bin/sh
2echo " "
3echo "Waiting for device..."
4./adb wait-for-device
5echo " "
6./adb -d shell stop
7./adb -d shell su -c "mount -o remount rw /system"
8./adb push framework-res.apk /system/framework/framework-res.apk
9./adb -d shell chmod 644 /system/framework/framework-res.apk
10./adb push SystemUI.apk /system/app/SystemUI.apk
11./adb -d shell chmod 644 /system/app/SystemUI.apk
12./adb reboot
This script will wait for the device to become ready, when it’s ready it freeze the device, so the script has more time to push the file (instead of keep rebooting). Then it will push framework-res.apk and SystemUI.apk to the directory it belongs to, after that it changes the permissions of the files to RW-R-R (644) and then it will reboot.
Please note that on some devices the command “su -c” cannot be used after using the “stop” command, it gives an error then (Segmentation Fault).
What you can do to prevent this is adding “adb remount” just under the “adb wait-for-device” line, and remove the “adb -d shell su -c “mount -o remount rw /system” line.
Save the script and run it again.
You are probably able to fix your bootloop with this guide, in some rare cases some other partitions could be damaged, then I advice you to install the stock rom (which is no .zip in most cases)
Once you master the fixing of bootloops you can fix your phone independently !
You can try this if all else fails GOOD LUCK SIR :fingers-crossed: http://www.mediafire.com/?9oghmlgoqpm44qe

[CLOSED] Help if you can

If anyone can help me... I have been dealing with JP6 tablets and now I can not get into the target tablet using terminal.. ADB shell is not working ... I'm trying to root.. I tried using this command
su
adb kill-server
adb start-server
adb wait-for-device root
adb disable-verity
adb reboot
adb wait-for-device root
adb remount
But it stops after the first adb waiting-for-device root ... And hangs up...here is what I'm getting when I Adb shell and another command can anyone assist to get around this??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

DjPlaymysong14 said:
If anyone can help me... I have been dealing with JP6 tablets and now I can not get into the target tablet using terminal.. ADB shell is not working ... I'm trying to root.. I tried using this command
su
adb kill-server
adb start-server
adb wait-for-device root
adb disable-verity
adb reboot
adb wait-for-device root
adb remount
But it stops after the first adb waiting-for-device root ... And hangs up...here is what I'm getting when I Adb shell and another command can anyone assist to get around this?? View attachment 5756087View attachment 5756091
Click to expand...
Click to collapse
Are you trying to root a unrooted device itself via terminal emulator?

Yes I am, it was working fine until the signal came through, what I would do before , while tablet was turning on from host device type adb root and then do adb disable-verity ... Now when I do adb root I get the adb vendors screen.. Same screen when I do adb shell.. Any suggestions?
Goddamn_srilankan said:
Are you trying to root a unrooted device itself via terminal emulator?
Click to expand...
Click to collapse
..

DjPlaymysong14 said:
Yes I am, it was working fine until the signal came through, what I would do before , while tablet was turning on from host device type adb root and then do adb disable-verity ... Now when I do adb root I get the adb vendors screen.. Same screen when I do adb shell.. Any suggestions?
..
Click to expand...
Click to collapse
I don't have any experiences with JP6 tablets to tell you what to do at that point. Long time ago i tried to do many things with that terminal emulator to push su binaries into the system but failed. Have you done that before?

That is what I need to do a friend said we need to push the binary there but if I can't adb root or adb shell how can I push over just su adb push and use my bin folder?

DjPlaymysong14 said:
That is what I need to do a friend said we need to push the binary there but if I can't adb root or adb shell how can I push over just su adb push and use my bin folder?
Click to expand...
Click to collapse
No you can't. Because that's not the way to do it. To check this, create a dummy file on your storage and rename it as "su". Then try to copy or move it into the system using cp or mv commands as below.
mv /storage/su /system/xbin
The only message you get is "permissions denied".

That is what I need to do a friend said we need to push the binary there but if I can't adb root or adb shell how can I push over just su adb push and use my bin folder?
Goddamn_srilankan said:
No you can't. Because that's not the way to do it. To check this, create a dummy file on your storage and rename it as "su". Then try to copy or move it into the system using cp or mv commands as below.
mv /storage/su /system/xbin
The only message you get is "permissions denied".
Click to expand...
Click to collapse
If you don't mind thats my gram info I don't want to mess up my host tab by doing something wrong that way I can screen shot u what I see

DjPlaymysong14 said:
DjPlaymysong14 said:
If you don't mind thats my gram info I don't want to mess up my host tab by doing something wrong that way I can screen shot u what I see
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Well, that's a android emulator right? Try to download pre-rooted Cyanogen OS based android emulator or Linage OS based android emulator. That's the easiest thing you can do to get a rooted android host on your pc. Hope this will work for you.

I'm using a rooted tablet to root another tablet using terminal .. With 2 micro USB cords

it noit work if u dont have 2 devices connected with cable

I'm using a rooted tablet to root another tablet using terminal .. With 2 micro USB cords
I was hacking these tablets all weekend using terminal commands.. A signal was sent and its now preventing me from hacking I need a new binary but really don't know where to start

DjPlaymysong14 said:
I'm using a rooted tablet to root another tablet using terminal .. With 2 micro USB cords
Click to expand...
Click to collapse
That won't work due to security features of these devices.
I think you should get into read more threads about ADB and Superuser to understand what is a ADB (Android debug bridge) connection and what is rooting.

DjPlaymysong14 said:
I'm using a rooted tablet to root another tablet using terminal .. With 2 micro USB cords
I was hacking these tablets all weekend using terminal commands.. A signal was sent and its now preventing me from hacking I need a new binary but really don't know where to start
Click to expand...
Click to collapse
You can't install ADB DRIVERS or USB DRIVERS on that rooted tablet. Do you have a windows computer?

Yea I went from hacking them to now its preventing me I know there has to be a work around. Just thought someone new of it... I did over 20 of them all using terminal commands and pushing files but adb shell not working nor adb root. .. Last question when I enter adb wait-for-device root should target be in the on or off state? And does it take a while to get the confirmation box after?

Goddamn_srilankan said:
You can't install ADB DRIVERS or USB DRIVERS on that rooted tablet. Do you have a windows computer?
Click to expand...
Click to collapse
I do not have access to no PC everything I'm using is o. This rooted tablet this is how I was hacking other tablets

DjPlaymysong14 said:
I do not have access to no PC everything I'm using is o. This rooted tablet this is how I was hacking other tablets
Click to expand...
Click to collapse
Well, technically that's not possible to get access through adb shell to another non-rooted device via micro USB cord using your rooted tablet. Even if you are able to get access through those cables, you can't modify the system of other device. That's completely not possible to do and that rooting means not just pushing binaries into a system. Read more rooting threads on the forum to learn more about that huge process.
Hope this will help you
Thank you

MOD ACTION:
Thread closed.
@DjPlaymysong14
We know where the JP6 tabs come from and where they are used. We do not allow any discussions about this tablet in view of Rule 9:
9. Don't get us into trouble.
Don't post copyrighted materials or do other things which will obviously lead to legal trouble. If you wouldn't do it on your own homepage, you probably shouldn't do it here either. This does not mean that we agree with everything that the software piracy lobby try to impose on us. It simply means that you cannot break any laws here, since we'll end up dealing with the legal hassle caused by you. Please use common sense: respect the forum, its users and those that write great code.
Click to expand...
Click to collapse
Please avoid posting about this tab any further.