Quantum7+/tabtronics (jb 4.1.1) – root - General Questions and Answers

QUANTUM7+/TABTRONICS ( RK3066/JB 4.1.1) – ROOT
Just to share the experience. This is what worked for me...
All the CREDITS and THANKS go to the “digitalhigh” – for the post below (and the guys in the chain..):
http://forum.xda-developers.com/showthread.php?t=2102600
1. Android SDK Manager (used the following versions)
Android SDK Tools - Rev. 21.1
Android SDK Platform Tools - Rev. 16.0.2
2. Modify File (as explained in the original post):
C:\Users\<YOUR-PC-USER>\.android\adb_usb.ini
- add a line:
0x2207​
3. Install USB driver Win 32/64 respectively - they are attached in the original post above.
!Note: ignore PushThese.zip, attached in the original post – not required – as the “adb shell” gets the root on device straight away. Also, the “Superuser.apk” and the “su” in this attached .zip are not compatible with JB 4.1.1, that is installed on the device. The “Busybox” is also already installed on this device. You can download and update this later from “Google Play”... Hence, just do not use this .zip related step.
4. Download “Superuser-3.2-RC3-arm-signed”
Download the following “Superuser-3.2-RC3-arm-signed” package from location:
http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.2-RC3-arm-signed.zip
Unzip and copy “Superuser.apk” and “su” to the“adb” directory:
C:\Program Files\Android\android-sdk\platform-tools\
5. Tablet to PC:
“Developer options” → “USB debugging” → [v]
Connect Tablet to PC. Kick off the USB driver installation (if not yet done in Step 3).
From the Win command line:
Code:
cd C:\Program Files\Android\android-sdk\platform-tools\
adb devices
The device should respond as 0123456789ABCDEF, or something similar to this.
6. This is the “Step 15” of the original post with the "busybox" push skipped, just the small changes specific to the device:
Code:
adb shell
# mount -o remount,rw -t rfs /dev/block/st19 /system
# exit
adb push su /system/bin
adb install Superuser.apk
adb shell
[B]# chmod 4755 /system/bin/su[/B]
# mount -o remount,ro -t rfs /dev/block/st19 /system
# exit
adb reboot
7. Once your QUANTUM7+ rebooted you should have the “Superuser” app installed.
8. Install “Terminal Emulator” app from the “Google Play” and try to $ su. You should see the “Superuser” app permissions request etc., etc...
9. Update “Busybox” from the “Google Play” to the latest version.
10. I would suggest you to do the full nandroid backup as soon as you have rooted your device. You can look at this link or details (if interested in):
http://tips4droid.com/make-nandroid-backups-on-android-without-booting-into-recovery/
11. Just one more thing to say – by coupling 2 CPU cores, switching Governors to “interactive”, the I/O Scheduler to “noop” and extending the SD cache buffer to 4096, you device should easily outplay TF201 on the “Quadrant Standard” benchmark test.
-----------
Good luck!
======
EDITED(29/03/2013):
Installing CWM/recovery.img for RK3066
You can also download the stock firmware from the official site, use this as a base and follow the simple instructions from the tread below to install the CWM recovery.img for RK3066:
http://forum.xda-developers.com/showthread.php?p=30842147
Worked without any issue for me.

One of my mates recently got this tablet and I'll be trying to root it with him over the weekend.
If it works I'll come back and click thanks. If not, expect a ban Just kidding. Thanks so far for this guide

Related

[HOWTO´S] collection of how to do it :)

Hi all, im making a NEW thread for how to make custom ROM, change build.prop, how to theme (coming later)! i will make a colection of how to´s to this thread for now all of the how to´s are made by me but in future i will take how to´s from others too (with their permission ofc )
so subscribe to this thread!!
i hope that there will be many custom ROMs after this
now you all think why did i do this if theres another tutorial for making custom ROM? answer: this is good alternative and this is not just one HOWTO!
HOWTO´S
-custom ROM
-edit build.prop
-5 lockscreen mod and extended power menu
-deodexing
-install android sdk and use ADB
-port themes (coming later)
-make own bootanimation (coming later)
** you can also post your ideas for new how to´s!!!
have a nice day
p.s dont blame me if something happens to your device while doing these how to´s
p.p.s if you want some special how to you can always suggest it in this thread
[HOWTO] make a custom ROM
How to make custom rom:
you will need: ADB, root explorer (maybe) and the files that are going to be in your rom!
the guide is based on The Dark Lestat's guide, i made it more easier and specific
code to delete unwanted apps: (if ADB)
Code:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
rm /system/app/nameofapk.apk
code to add apps and stuff: (if ADB)
Code:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
exit
exit
adb push nameofapk.apk /system/app/
1. flash the ROM that will be your ROMs base. example: my ROMs base is JPM so i flashed clean JPM
2. make a list of the features that are going to be in your ROM
3. then start adding those features. example: i added live wallpaper support so i did this --> http://forum.xda-developers.com/showthread.php?t=793823 i also added JIT so i ran the automatic batch file from the thread --> http://forum.xda-developers.com/showthread.php?t=1026870 . then you just add those features.
4. put your sd card on to your phone (if it isnt there already )
5. when your done adding different features you go to ADB and type this:
Code:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
dd if=/dev/block/stl6 of=/sdcard/factoryfs.rfs
then you wait about 2 minutes and there will be some text and then you type this
Code:
exit
exit
and in your sd-card will be freshly created factoryfs.rfs, import your freshly created factoryfs.rfs to your desktop. now you choose your kernel.
5. kernel, download the kernel you want to your desktop.
6. download total commander to your pc
7. open total commander, open the base ROM.tar. example: my base ROM was JPM so i opened the JPM.tar and replaced the kernel and factoryfs.rfs with my factoryfs.rfs and my kernel (fugumod 2.2) using total commander.
delete everything else in the .tar but, Cache.rfs, factoryfs.rfs, zlmage and data.rfs and the logo!
then you test if you can flash your ROM... if it boots, you did it. if it doesnt, try again.
[HOWTO] edit BUILD.prop
HOW TO change firmware version, phone model, build version in "about phone"
1. open root explorer
2. go to /system, find build.prop, change to read/write mode. open the build.prop in text editor
* change build version: 4th line should say ro.build.display.id=(here you write your build version name), reboot and check build version in "about phone"
* change model number: 15th line should say ro.product.model=(here write your model number ), reboot and check model number in "about phone"
* change firmware version: 8th line should say ro.build.version.release=(here write your firmware version, like 3.0 honeycomb ), reboot and check firmware version in "about phone"
you can also change different things but ill write a guide of that later
hope you like it!
[HOWTO] port a THEME
reserved for later use
[HOWTO] get 5 lockscreen mod and extended power menu
-your ROM must be deodexed!
-you can get extended power menu and 5 lockscreen mod by downloading this --> http://www.megaupload.com/?d=PKHVA57W
-extract it to root of your sd-card
-open root explorer and copy/paste the files to /system/framework
-reboot and done
OR
use adb like this:
Code:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
exit
exit
adb push nameoffile.jar /system/framework/
-reboot and done
***NOTE rebooting might take some time so dont panic
[HOWTO] deodex ROM
you must be rooted
What you'll need:
A Windows based machine
xUltimate v2.2
Patience
Process:
-Unzip xUltimate v2.2, and launch "Main.exe"
-If everything goes well xUltimate should recognize the phone and make a connection. You now should see a list of options.
-Run option 1. After option 1 is done, run option 2.
-Now these well take a while. Run option 3.
-IMPORTANT: After you have run option 3, you MUST navigate to the xUltimate folder and find "origi_frame" folder, and delete "guava.odex" (if you even have it). It's a bad file, and interferes with deodexing process.
-Now run option 4, and wait.
-Exit xUltimate, and put the phone in USB mass storage.
-Go back into the xUltimate folder and copy "done_frame", and "done_app", and move them to the root of the sdcard.
-Open a command prompt, and do the following:
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
and voila your phone is deodexed
original guide by webst3r, i changed it so its easier to understand
[HOWTO] get ADB up and running (easy way)
ADB is an acronym for Android Debug Bridge and is a development tool for the Android Mobile Operating System
NOTE this is only for windows!
-open this link --> http://adf.ly/Xfyl wait 5 secs and click upper right corner "skip ads" it will download a program that automaticly installs android sdk (wich includes ADB)
-Open the app, leave the destination as C:\ and click ok/install
-Installing ADB/USB Drivers:
*NOTE* You may need additional (Device Specific) Drivers for your Device!
- Connect your Android Device to your PC using the provided USB Cable or just a plain ole 6-pin to 4-pin usb cable... (I prefer to use one with a ferite core)
- When the new hardware device notification pops-up on your pc point windows to the driver folder we moved to our C-drive(C:\android-sdk-windows\google-usb_driver) and install the adb driver.
** if your having issues with installing ADB drivers read this --> http://dl.dropbox.com/u/20575563/ADB_Drivers_for_dummies.pdf
-Running ADB from the Command Prompt:
-Windows XP: Select Start or Tap the Windows Key on your Keyboard, select
"Run" and type "CMD" then hit "Enter".
-Windows Vista/Win7: Select Start or Tap the Windows Key on your Keyboard, select the search box on the left and type "cmd" then hit "Enter".
Add the "ADB" directory path as a system variable in windows:
-To do this right-click on "My Computer" and select Properties. Next select the Advanced tab(Advanced Settings in Vista/7) then select Environment Variables.
-Click "New" under System Variables and add the following:
Variable =
Code:
adb
Value =
Code:
C:\android-sdk-windows\platform-tools
-Call up your Command Prompt:
Time to start adb
- Open up a Command Prompt Windows
- Type the commands below:
Code:
cd C:\android-sdk-windows\platform-tools
<-- Press Enter
Code:
adb.exe
<--Press Enter
and voila You will see alot of scripting fly through the command prompt window.
***note! you have to enable usb debugging in --> settings --> applications --> developement --> check usb debugging
tutorial is not made by me, its made by AndroidSamurai. i found it after lot of researching
[HOWTO] make your own update.zip
download and install, then watch the video
http://youtu.be/i0KzFPMA6-8
program and video made by Daneshm90
balaji.admin said:
Please include a Post for Deodexing the ROM. I've tried to deodex the DDJP2. But never succeeded.
Hope your post will help me.
Click to expand...
Click to collapse
there is a tut by rudolf..
[HOWTO] change app icon
How to change icons for app!
1.)
Things you need:
original app
your custom icon (size should be 48x48)
win rar
2.)
Unpack APK
3.)
Find file, for example: ic_launcher_settings.png (for settings.apk)
It should be in: res/drawable-mdpi or res/drawable-ldpi (dont know which icon phone uses, just replace both)
4.)
Rename you icon to, for example: ic_launcher_settings.png (for settings.apk)
5.)
Replace it
6.)
Final step is add files to old settings.apk archive and using root explorer copy it into /system/app/
DONE!
guide by peldax
jazux said:
hey, one question coming from me our device has the same resolution as htc wildfire? right? and device is ldpi or mdpi? please answer ASAP!!! i may have found very useful HOWTO that you will LOVE!!!
>>>>>>>>>>>>>>>>>>>>>>>>>
POX v.1.0 beta 2 released! be sure to try it out :]
<<<<<<<<<<<<<<<<<<<<<<<<<
GreeModding from finland :]
Click to expand...
Click to collapse
galaxy3 has ldpi - look there: http://developer.android.com/guide/practices/screens_support.html
jazux said:
-your ROM must be deodexed!
-you can get extended power menu and 5 lockscreen mod by downloading this --> http://www.megaupload.com/?d=PKHVA57W
-extract it to root of your sd-card
-open root explorer and copy/paste the files to /system/framework
-reboot and done
OR
use adb like this:
Code:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
exit
exit
adb push nameoffile.jar /system/framework/
-reboot and done
Click to expand...
Click to collapse
is this suit for every rom?
dxdiag32 said:
is this suit for every rom?
Click to expand...
Click to collapse
what do you mean? like does this work on other fw's than JPM? im not sure because i havent tested it, but i think it should work.
but it will surely work on every JPM based ROMs
>>>>>>>>>>>>>>>>>>>>>>>>>
POX v.1.0 beta 2 released! be sure to try it out :]
<<<<<<<<<<<<<<<<<<<<<<<<<
GreeModding from finland :]
Hey man a really nice tutorial
Can you add my tutorial on how to make bootanimations too
It would be appreciated
P.S. : If you tell yes,i'll give you a shortened version too
Deodexed Rom? How can i do it?.
cdesai said:
Hey man a really nice tutorial
Can you add my tutorial on how to make bootanimations too
It would be appreciated
P.S. : If you tell yes,i'll give you a shortened version too
Click to expand...
Click to collapse
yes i can add it
>>>>>>>>>>>>>>>>>>>>>>>>>
POX v.1.0 beta 2 released! be sure to try it out :]
<<<<<<<<<<<<<<<<<<<<<<<<<
GreeModding from finland :]
AndroKite said:
Deodexed Rom? How can i do it?.
Click to expand...
Click to collapse
ill do a tutorial later tonight!
>>>>>>>>>>>>>>>>>>>>>>>>>
POX v.1.0 beta 2 released! be sure to try it out :]
<<<<<<<<<<<<<<<<<<<<<<<<<
GreeModding from finland :]
AndroKite said:
Deodexed Rom? How can i do it?.
Click to expand...
Click to collapse
for now you can use this:
Thanks,i dont remenbre that you make a tutorial ,Thx.
AndroKite said:
Thanks,i dont remenbre that you make a tutorial ,Thx.
Click to expand...
Click to collapse
you welcome

Android Rooting (Simplified)

Hello everyone!
I know some of you are still roaming around here and there trying to root your phone; others wanting to root the phone without knowing what rooting is...
Wandering if it's illegal or not; and why should they be Rooting their Devices.
Well that's why i've done this tutorial with a lot of help from different sources.
It has been almost 2 days reading; reading; reading; and writing this tutorial to simplify and compact information scattered around this forum and the web.
Knowing the Basics
In order to explain everyone (specially noobs / starters); please follow this link.
(I advise you to open it in a "new Tab" or "Window"; so you don't loose yourself)
One thing before starting:
I found out that it is important to reboot the device and the PC after installing and Updating the following apps: "Super one Click" and SDK with your firmware version API's.
Some errors that occur during the Rooting with the "Super One Click" happen due to some kind of need to reboot of the machine and device.
As mentioned in Step #9
[...]
Now that you understand what rooting is; let's ROOT your Android.
P.S - As you already know; you are responsible for doing this process; or for anything that goes wrong.
“Rooting Your Android Phone”
Requirements:
Download: "android-sdk_r15" or Later Version.
After Downloading and Installing SDK; download the API's according to your Firmware Version.
(Check Step #1 and #12 of the Easy Rooting Method)
Download: "Super One Click Program"
(Link Goes to XDA Developers "Super one Click Program" Thread)
Download: "Java SE Development Kit 7" (or later)
I. (Easy Method - Using “One Click Rooting Program”)
Note: This method works for almost every Android phone.
1) Take a note of you brand model and android Firmware/ROM installed on you device.
(You need to know the version of your O.S to download your SDK API's later)
i.e:
“Model: Acer C4 Liquid Mini (E310)”
“O.S: Android Froyo v2.2”
2) Download/Install your Android Drivers. (PC)
3) Download/Install your Android SDK/ADB. (PC)
4) Open SDK (as Administrator) and mark the following things to download:
- “Tools” (Select the entire Folder)
- “Your Firmware/ROM Version Installed” (i.e: “Android 2.2 API”) (Select the entire Folder)
5) Now press “Install Packages” (The download will start; follow the next step after it’s completed)
6) Download / Install the Latest version of the rooting program (Super One Click Rooting Program); unzip it and install it on your computer.
7) Make sure that your phone has the "USB Debugging Mode" ON.
NOTE: To turn it on go to your device and press: “Menu” > “Settings” (Icon) > “Applications” > “Debug / Development” > “USB Debug”
8) Make sure you turn Off your Device and Remove the SD Card. It must be done without the SD Card.
9) Safely disconnect your Phone from the PC; and restart. (PC and Device)
10) When your Phone and Windows are ready; connect your phone to the PC.
Note: Just plug the cable. Do NOT select any option in the Phone.
Also you will notice that a small Android Icon will appear at the top left of the screen.
That means that you phone is prepared for debugging Mode.
11) Once again make sure that your phone has the "USB Debugging Mode" ON.
12) Run SDK/ADB as Administrator.
(Windows XP Users just double click to open)
13) Right Click the “Super One Click Rooting Program” and open it as Administrator.
(Or just double click; if you are using Windows XP)
14) Press "Update Check"; just to make sure you have the latest files. (Don't worry with the app version error; if it happens means you just downloaded it/you have the latest version)
14) Click the "Root" button and wait it to finish. (There should be no errors)
15) Once done; you should see “Superuser” permission in your phone’s apps.
Note: If so; your Device is Rooted. Congratulations!
II. (Advanced Method - Manually Rooting)
Pre-requisites
There are a few things that you need to have before you start rooting.
Obviously, you will need an Android device with Android 1.5 or higher and a USB cable to connect it to your computer.
You will also need to have some files for this:
SuperOneClick.zip and the Android SDK/ADB up and running on your computer.
(Run as Administrator if not using Windows XP)
If you are unfamiliar with ADB, GoodAndEvo site has an awesome ADB tutorial that should get you up to speed.
(Note that the tutorial in the Good and Evo Page is for HTC Devices)
First, we need to move some files around to make running commands a bit easier.
Unzip the SuperOneClick.zip and copy the following files: su-v3, busybox, Superuser.apk, psneuter, and GingerBreak; to the Android “ADB Platform-Tools folder”; which is contained in the Android SDK folder on your computer.
i.e: C:\Program Files\Android\Android-SDK\Platform-Tools\
These files can be found in the following SuperOneClickv2.1.1-ShortFuse folders:
- “Busybox” -> “Dependencies” folder
- “psneuter” -> “Exploit” folder
- “GingerBreak” -> “Exploits” folder
- “SuperUser.apk” -> “Root” folder
- “SU-V3” -> “Root” folder
Once copied rename “su-v3” to “su”.
If you are on Windows, you will also need to have proper drivers for your phone installed.
These can usually be found by going either to the manufacturer website or searching for the name of your phone and the word "Drivers."
Once you find drivers, download and install them like any other application.
Rooting your device
Now that you have ADB setup and the proper exploit files, you are finally ready to Root.
Before you start running commands, you need to put your phone in "USB Debugging" mode.
(Menu > Settings > Applications > Development > Enable USB Debugging) and connect the device to your computer.
Note: Just plug the cable and do not select any option in you device.
Now, open command prompt to run some commands.
Windows Vista/7 Users:
(Press "Windows Key" > Type: "CMD" > Right Click on "CMD" and Run it as Administrator)
In Linux, open whichever terminal emulator suits you. Once you have a command prompt, you need to enter your platform-tools folder, also called a directory.
You can use the "CD" or Change Directory command to accomplish this.
If your SDK folder is called "android-sdk" the command should look like this: cd android-sdk_r11-windows/platform-tools.
This command will leave you with a shell prompt in the platform-tools directory.
From here, you can run the commands that will actually root your phone.
Be sure to run these commands exactly as they are written.
The commands with an "$" or "#" will only run after the "adb shell" command.
First, here are the commands that run the” psneuter” exploit and gain a root shell.
Type them in the following order.
…Yes after the ADB and the “$” there is a “Space”.
• adb devices
• adb push psneuter /data/local/tmp
• adb shell
• $ cd /data/local/tmp
• $ chmod 777 psneuter
• $ ./psneuter
At this point, the exploit will run and close the shell.
You will need to run these commands to restart the ADB server.
• adb kill-server
• adb devices
Now comes the moment of truth.
Type:
• adb shell
...command to open a shell.
If you see a "#" sign, you have root access, so go ahead and continue to the next part of this tutorial.
If not, you can go back and try the previous steps again, or ask for help in the comments.
We now need to make this root permanent.
From the root shell you just opened, type the following commands.
• # mount -o remount,rw -t rfs /dev/block/st19 /system
• # exit
• adb push busybox /system/bin
• adb push su /system/bin
• adb install Superuser.apk
• adb shell
• # chmod 4755 /system/bin/busybox
• # chmod 4755 /system/bin/su
• # mount -o remount,ro -t rfs /dev/block/st19 /system
• # exit
• adb reboot
At this point, your device should reboot.
You can check for the Superuser icon in the app drawer, and then try a root only app like Titanium Backup.
If that app works, congratulations!
You have successfully rooted your Android device.
Prepare to enjoy all the benefits of root.
If you are having trouble with this tutorial or want to offer others a tip, please leave a comment.
Me or every XDA developer/user shall gladly help you out clarifying any error message or issue. (at least if i know how i will help)
Just make sure you did exactly as described; and only then post your question / expose your issue(s).
P.S
- Use “Code” Tags to report Logs.
- Remember to "Thank" if this tutorial helped you or if you find it usefull.
Special thanks to:
XDA Developers (Users & Staff)
Pocketables.net (Aaron Orquia)
CLShortFuse (For bringing such Great App)
I can´t do this with method #1 (freeze on step #6)
In method #2 ....
$ cd /data/local/tmp
cd /data/local/tmp
$ chmod 777 psneuter
chmod 777 psneuter
$ ./psneuter
./psneuter
Failed to set prot mask (Inappropriate ioctl for device)
$
Some help?
Regards
niki40 said:
I can´t do this with method #1 (freeze on step #6)
In method #2 ....
$ cd /data/local/tmp
cd /data/local/tmp
$ chmod 777 psneuter
chmod 777 psneuter
$ ./psneuter
./psneuter
Failed to set prot mask (Inappropriate ioctl for device)
$
Some help?
Regards
Click to expand...
Click to collapse
Greetings;
What's your device Make and Model?
Try/Check the following:
- Download the "Super One Click Program" Again. Since there is a new Fix for it.
Follow this Link to download and get more detailled info:
http://forum.xda-developers.com/showthread.php?t=803682
- Check that you have the USB Debug Turned ON (in your device)
---> List > Settings > Applicatons > Development > USB Debugging
- Check what version do you have in your device; and verify that SDK Manager has downloaded your Version API's; and Tools folder. (Look at status tab; it should say installed)
- Did you Restart the machine after the install of Super One Click and SDK Manager? (Only then Root the Device)
- In a Last case there's a small percentage that your phone isn't compatible with "Super One Click".
Thanx a lot bro
You Can Add This To The OP If You Want .
Press Thank If I Help .
For Sony Ericsson Xperia Only .
I Use A Sony Ericsson Xperia X10 And It Work Well .
The File Name Is Call Flash Tool .
The Fuction It Has Is ( Latest 4.2 )
Root
Flash Kernel
Flash Rom
One Click Unlocked Bootloader .
Click to expand...
Click to collapse
Thing You Need To Do Is :
Download The Two File .
Install In The Same Place .
Open The File .
Open Driver Folder .
Install The Driver .
And Open Flash Tool exe .
See If The Computer Detect Your Phone .
USB Debugging Must On .
Click to expand...
Click to collapse
Thing Your Need ( For Rooting Only ) :
https://github.com/Androxyde/Flashtool/downloads
==================================================
Unlocked Bootloader Try At Your Own Risk . Sony Ericsson Xperia X10 Success ) :
Only For Sony Ericsson Xperia Phone .
Download Generic version 2.3.3 build 3.0.1.G.0.75 ( http://www.multiupload.com/564T6TLUD8 )
Download DoomLoard Boot Manager . ( http://doomlord.sylvester20007.com/...tmanager/X10_2.3.3_Stock-BootManager-v1.3.ftf )
Put This Two File In Flash Tool Frimware Folder .
Open Flash Tool .
Press Flash .
Select All The File Inside .
Reboot Your Phone .
Root Your Phone .
And Install DoomLoard Boot Manager .
You Can Now Install Unlocked Bootloader Rom .
Click to expand...
Click to collapse
If Anyone Know Anything And Notice I Say Wrong Here Please Private Message Me Or Comment Here To Tell Me
Special Thank To :
Every One That Teach Me Last Time .
Androxyde For Flash Tool . http://forum.xda-developers.com/showthread.php?t=920746
DooMLoRD For DoomLoard Kernel And Boot Manager . http://forum.xda-developers.com/showthread.php?t=1278318
Every Body Who Click Thank .
Every Body Who Read .
Click to expand...
Click to collapse
==================================================
Do It At Your Own Risk . Press Thank If I Help
And Yes It Work For New Xperia ( 2011 Lines )
nice share...but i already rooted my xperia

[Emulator][Root] BlueStacks 0.7.7.813

I'm here give full guide for what I was learned from merrickville, codelover, and rocketero so all credits go to all of them either by direct guide and correction or by understanding their modified files. (is it OK codelover :good
To whom who don't know BlueStacks (as me before a week), it's emulated android system to works under windows system. for more info go to company page
A- REMOVE BLUESTACKS
Good tool from "Microsoft Fix it to install/uninstall Programs" thanx Ba7rani123
1- Run command (Win Key + R) -> "%programfiles%\BlueStacks\HD-Quit.exe" (WinX86) "%programfiles(x86)%\BlueStacks\HD-Quit.exe" (WinX64)
2- Open "task manager" by run command "taskmgr" -> "Processes" tab -> "HD-LogRotatorService.exe" -> right click -> "End Process Tree"
3- Open "programs and features" by run command "appwiz.cpl" -> uninstall "BlueStacks App Player" & "Notifications Center"
4- Delete all BS folders
"%userprofile%\AppData\Local\BlueStacksSetup"
"%programfiles%\BlueStacks" (WinX86), "%programfiles(x86)%\BlueStacks" (WinX64),
"%programdata%\BlueStacks"
"%programdata%\BlueStacksSetup"
Setup from Desktop
"%windir%\Installer" -> "View" -> "Details" -> right click on column header (i.e "Name", "Date Modified", "Type") -> "Authors" -> click over column header of "Authors" to sort files according authors -> search for "BlueStacks" and delete.
Note: "%ProgramData%\BlueStacks\Logs\Hypervisor.log" will persist to delete, we will delete it later after restart
5- Download RegScanner v1.95
Install -> open it -> Registry Scan Options (it will open automatic) -> select all keys in option Scan the following base key -> write on Find String "BlueStacks" -> wait till search finish -> select all and delete -> Resisted keys can be deleted manually by open in Regedit (F8)
I can't support this application because I have Windows 7 Manager, with perfect Registry Tools 1.1, it backup & delete all keys automatic
6- Repeat step (5) by searching for "Notification Center"
7- Reboot your devive now.
8- Now you can remove %ProgramData%\BlueStacks\Logs\Hypervisor.log
Click to expand...
Click to collapse
B- ROOTING BLUESTACKS
B-I- FIRST ROOTING METHOD (Ready made rooted /system)
Download rooted "Root.fs" and modified "initrd.img" for BlueStacks 0.7.7.813:
1- Download "BlueStacks-ThinInstaller_0.7.7.813.exe", "Root_Mod.rar" and "initrd_Mod.rar" from HERE
2- Setup BlueStacks 0.7.7.813 by file "BlueStacks-ThinInstaller_0.7.7.813.exe"
3- After setup finish installing, and BS open, close it (even before click "Got it") then run command (Win key + R) "%ProgramFiles%\BlueStacks\HD-Quit.exe" (WinX86), "%programfiles(x86)%\BlueStacks\HD-Quit.exe" (WinX64).
4- Extract "Root_Mod.rar" and "initrd.rar" into same folder "%programdata%\BlueStacks\Android" (P.S no need to make backup because it's already packed in zip file on "%programdata%\BlueStacksSetup\[xxxxxxxx].zip"
5- Open run command "%programfiles%\BlueStacks\HD-StartLauncher.exe" (WinX86), "%programfiles(x86)%\BlueStacks\HD-StartLauncher.exe" (WinX64)
Now your BlueStacks have root permission (Thanks CodeLover) and google apps (already supported).
OR
Download rocketero's rooted Root.fs & initrd.img from the 3rd post , thanks rocketero
Click to expand...
Click to collapse
B-II- SECOND ROOTING METHOD (Custom made rooted /system)
Rooting your "Root.fs" by your self, this method allow you root any versions of BlueStacks. it need to download "Portable Ubuntu Remix", [INFO: it's a portable Linux Ubuntu 10.4 LTS emulator that works under windows environment. for more information see PROJECT.
1- Download "Portable Ubuntu Remix" from HERE
2- Download "BlueStacks" from HERE
3- Run "Portable Ubuntu Remix" and change the path to "%programfiles%\" (WinX86) "%ProgramFiles(x86)%\" (WinX64)
4- Setup "BlueStacks" until it open -> close it.
5- Open run command (win key + R) "%ProgramFiles%\BlueStacks\HD-Quit.exe" (WinX86), "%programfiles(x86)%\BlueStacks\HD-Quit.exe" (WinX64).
6- Make RAR backup of your original "%programdata%\BlueStacks\Android\Data.sparsefs" in case of any errors may happen later.
7- Follow steps of F- MOD LATEST "SUPERUSER.APK", EXTRACTED "SU" BINARY, BUSYBOX FILES .
8- Follow steps of H- EDITING INITRD.IMG and place it in "%ProgramData%\BlueStacks\Android" (P.S: don't worry about original "initrd.img" because it is packed in zip file @ "%ProgramData%\BlueStacksSetup\[xxxxxxx].zip".
9- Open run command "%programfiles%\Portable_Ubuntu_V4_slim2\pubuntu.exe" (WinX86), "%ProgramFiles(x86)%\Portable_Ubuntu_V4_slim2\pubuntu.exe" (WinX64) and wait till it fully loaded (i.e top toolbar).
10- From the top toolbar select Applications -> Accessories -> Terminal.
11- Write the following commands (P.S: # means a note for you, it's not a command):
Code:
# Take a root permission
sudo su
# It will ask you for a root password: 123456
# Create a working folders
mkdir /b
mkdir /b/root
mkdir /b/system_sfs
mkdir /b/system_img
# Resize Root.fs to 500 MB
e2fsck -f -y "/media/cofs2/ProgramData/BlueStacks/Android/Root.fs"
resize2fs -f "/media/cofs2/ProgramData/BlueStacks/Android/Root.fs" 500M
# Mount root.fs to root folder
mount -o loop "/media/cofs2/ProgramData/BlueStacks/Android/Root.fs" /b/root
# Mount system.sfs to system_sfs folder
mount -o loop /b/root/android/system.sfs /b/system_sfs
# Extract system.img to /b folder
cp /b/system_sfs/system.img /b/root/android
# Resize system.img
e2fsck -f -y /b/root/android/system.img
resize2fs -f /b/root/android/system.img 480M
# Unmount system_sfs and delete it (make sure the command not unmount)
umount /b/system_sfs
rm /b/root/android/system.sfs
rmdir /b/system_sfs
# Mount system.img into system_img
mount -o loop /b/root/android/system.img /b/system_img
# Copy MOD "Superuser" & extracted "su" binary, busybox files (which you already did in step 7)
cp "/media/cofs2/pubuntu/Superuser.apk" /b/system_img/app
cp "/media/cofs2/pubuntu/su" /b/system_img/bin
cp "/media/cofs2/pubuntu/su" /b/system_img/xbin
cp "/media/cofs2/pubuntu/busybox" /b/system_img/xbin
chmod 6755 /b/system_img/bin/su
chmod 6755 /b/system_img/xbin/su
# Un mount system_img & delete folder
umount /b/system_img
rmdir /b/system_img
# Set Permission for system.img
chown 0:2000 /b/root/android/system.img
chmod 0644 /b/root/android/system.img
# Unmount root and save changes into root.fs
umount /b/root
rmdir /b/root
rmdir /b
12- Close Terminal and shut down Portable Ubuntu from system menu at top toolbar -> Shut Down
13- Open run command "%programfiles%\BlueStacks\HD-StartLauncher.exe" (WinX86), "%Programfiles(x86)%\BlueStacks\HD-StartLauncher.exe" (WinX64)
14- After BlueStacks run, download custom launcher (like Go Launcher HD for Pad, Apex).
15- Now your BlueStacks have root permission.
16- Make RAR backup of your "Root.fs" and "initrd.img".
Click to expand...
Click to collapse
C- BLUESTACKS INSTALLING TROUBLESHOOTS
1- If you have msgbox telling you of missing img, rerun the setup
2- If you the setup just start and finish very soon
See section A- REMOVE BLUESTACKS @ the top
Click to expand...
Click to collapse
D- ROOTING TROUBLESHOOTS
You have to reset BS files:
a) If you follow B-I- FIRST ROOTING METHOD:
1- Download "Root_MOD.rar", "initrd_MOD.rar" and "Data_Org.rar" from HERE
2- Extract them on "%programdata%\BlueStacks\Android"
b) If you follow B-II SECOND ROOTING METHOD:
1- If you already have previous root and made backup of your rooted "Root.fs" & edited "initrd.img" & stock "Data.sparsefs" -> just extract all back to "%programdata%\BlueStacks\Android"
2- If you don't have backup -> either extract them from "%programdata%\BlueStacksSetup\[xxxxxx].zip" and start from scrach, or follow above (a) steps of B-I- FIRST ROOTING METHOD.
Click to expand...
Click to collapse
E- BACKUP/RESTORE BLUESTACKS by Codelover via bat executable commands see HIS POST
F- MOD LATEST "SUPERUSER.APK", EXTRACTED "SU" BINARY, BUSYBOX FILES I got it from codelover's MOD superuser4BS.apk
1- Download last version of Superuser for x86 from HERE
2- Download 7-Zip & install it from HERE (if you didn't have it)
3- Download latest version of "busybox-i686" from HERE to "C:\pubuntu" (take attention it should be small letter) and rename the downloaded file into "busybox"
4- Extract "\system\bin\su" to "C:\pubuntu" we need it to copy it to "/system/bin" & "/system/xbin"
5- Extract "\system\app\Superuser.apk" to "C:\pubuntu"
6- Close 7-zip
7- Open "Superuser.apk" via "7-zip" -> extract "assets\sutools-x86" -> rename it into "sutools-armeabi" -> drag it back in 7-zip to replace existed "sutools-armeabi".
8- Make copy of "busybox" and rename this copy to "busybox-armeabi" -> drag it again in 7-zip to replace existed "busybox-armeabi"
8- Close 7-zip and now, you have latest files MOD Superuser,apk, extracted "su" binary and busybox files
Click to expand...
Click to collapse
G- COPY FILES TO /SYSTEM via ADB modified from codelover's commands (take a look on his POST)
You should have "su" with root permission.
[GOOD TOOL: "Add_Open_Command_Window_Here_as_Administrator.reg" HERE to allow you open command from any folder]
a) To replace old "superuser.apk" with new file
1- Download "CodeLover_SU.rar" (superuserX86-3.2RC3) from HERE -> extract it into "C:\pubuntu" OR use your own MOD file from step F- MOD LATEST "SUPERUSER.APK", EXTRACTED "SU" BINARY, BUSYBOX FILES
2- Run "Add_Open_Command_Window_Here_as_Administrator.reg" from "C:\pubuntu" folder
3- Write commands
Code:
adb connect 127.0.0.1:5555
adb -s 127.0.0.1:5555 shell su -c "rm /*uperuser.apk"
adb -s 127.0.0.1:5555 uninstall com.noshufou.android.su
adb -s 127.0.0.1:5555 install *uperuser.apk
Click to expand...
Click to collapse
b)Replace old "su" binary file with new file
1- Download "CodeLover_SU.rar" (suX86-3.2RC3) from HERE -> extract it into "C:\pubuntu" OR use your own Extracted file from step F- MOD LATEST "SUPERUSER.APK", EXTRACTED "SU" BINARY, BUSYBOX FILES
2- Run "Add_Open_Command_Window_Here_as_Administrator.reg" from "C:\pubuntu" folder
3- Write commands
Code:
adb connect 127.0.0.1:5555
adb -s 127.0.0.1:5555 push su.86 /sdcard/
adb -s 127.0.0.1:5555 shell su -c "cp /sdcard/su.86 /system/xbin/"
adb -s 127.0.0.1:5555 shell su -c "chown 0.0 /system/xbin/su.86"
adb -s 127.0.0.1:5555 shell su -c "chmod 6755 /system/xbin/su.86"
adb -s 127.0.0.1:5555 shell su -c "mv /system/xbin/su.86 /system/xbin/su"
adb -s 127.0.0.1:5555 shell su -c whoami # if you got "Root"
adb -s 127.0.0.1:5555 shell su -c "cp /system/xbin/su /system/bin/su"
Click to expand...
Click to collapse
c)Replace old "busybox" file with new file
1- Download latest version of "busybox-i686" from HERE to "C:\pubuntu" and rename the downloaded files into "busybox" OR use one you already download it in step F- MOD LATEST "SUPERUSER.APK", EXTRACTED "SU" BINARY, BUSYBOX FILES
2- Run "Add_Open_Command_Window_Here_as_Administrator.reg" from "C:\pubuntu" folder
3- Write commands
Code:
adb connect 127.0.0.1:5555
adb -s 127.0.0.1:5555 push busybox /sdcard/
adb -s 127.0.0.1:5555 shell su -c "cp /sdcard/busybox /system/xbin/busybox-i686"
adb -s 127.0.0.1:5555 shell su -c "chown 0.2000 /system/xbin/busybox-i686"
adb -s 127.0.0.1:5555 shell su -c "chmod 0755 /system/xbin/busybox-i686"
adb -s 127.0.0.1:5555 shell su -c "mv /system/xbin/busybox-i686 /system/xbin/busybox"
adb -s 127.0.0.1:5555 shell busybox
You should not have error
Click to expand...
Click to collapse
Click to expand...
Click to collapse
H- EDITING INITRD.IMG to mount /system for read & write, I got it from merrickville's initrd.img
1- Download 7-zip and install it
2- Download "NotePad++" from HERE and install it.
3- Copy "initrd.img" from "%programdata%\BlueStacks\Android\initrd.img" or extract it from "%programdata%\BlueStacksSetup\runtimedata_[xxxxxxx].zip" (where xxxxxx = ur BS version) to "C:\pubuntu".
4- Open 7-zip -> Tools -> Options -> Editor -> put the path of installed "NotePad++" ["%ProgramFiles%\Notepad++\notepad++.exe"]
5- Extract "initrd.img" via 7-zip -> open extracted file "initrd" via 7-zip -> right click "initrd" -> Edit
6- Search for:
Code:
[B]try_mount [COLOR="red"]ro[/COLOR] "$device /mnt || continue[/B]
(It should be after "for device in /dev/sr* /dev/sd.....")
and replaced with
[B]"try_mount [COLOR="red"]rw[/COLOR] $device /mnt || continue[/B]
7- Close it and save the file -> accept replacing of the file -> close 7-zip
8- Open "initrd.img" via 7-zip and replace "initrd"
9- Now you have your edited initrd.img -> copy back to "%programdata%\BlueStacks\Android"
Click to expand...
Click to collapse
If it helps you, give me thanks :good:
Looks preety awesome...
Will try it soon...
Sent from my GT-S7500 using xda premium
"E=mohazia;33618109]I'm here give full guide for what I was learned from mammadkhata and merrickville so all credits go to both of them.
To whom who don't know BlueStacks (as me before a week), it's emulated android system to works under windows system. for more info go to company page
You have 2 choices,
First Method:
:
Click to expand...
Click to collapse
I have a Root.fs rooted (& Initrd.img Edited) with system.img (/system partition) resized to 500MB that is working fine with BS07.7.813.
you can download it here: https://www.dropbox.com/s/rdf35z9cupl5xnb/Root-fs_and_Initrd-img-bs077813.rar
it's MD5(sum) is: FFA77658EF35AACDDA06B379CBF52CB8
it contains Root.fs and Initrd.img, this still can follow your method # 1 to root BS 077813.
A few notes:
- system partition resized to 500MB
- su version 3.2 x86-RC3-signed was added not only to /system/xbin but also to /system/bin as well as busybox to keep a fallback when updating the su binary.
- binary /system/bin/ls was symlinked to busybox instead of toolbox to get nice color file listings in a terminal
- superuser4BS.apk (moded by @codelover) was added to /system/app"
rocketero said:
Does your first method contain a Root.fs with /system resized to let's say 300MB or more?
I have a Root.fs rooted and with system.img resized to 500MB that is working fine with BS07.7.813.
you can download it here: https://www.dropbox.com/s/rdf35z9cupl5xnb/Root-fs_and_Initrd-img-bs077813.rar
it contains Root.fs and Initrd.img, this still can follow your method # 1 to root BS 077813.
A few notes:
- system partition resized to 500MB
- su version 3.2 x86 was added not only to /system/xbin but also to /system/bin as well as busybox to keep a fallback when updating the su binary.
- binary /system/bin/ls was symlinked to busybox instead of toolbox to get nice color file listings in a terminal
- superuser-3.1.3.apk was added to /system/app
Click to expand...
Click to collapse
Your link was added, thanx
but I'd like to ask, why u'll need system 500MB ???
mohazia said:
but I'd like to ask, why u'll need system 500MB ???
Click to expand...
Click to collapse
it's not exactly that you need 500M on /system partition, as the size will just increase as you add files to /system, if you don't add any files the partition will stay the size it was originally, it works as the sparcefs file sistem does, it will show only what you have added from the total. Let's say you have grown the /system parttition to 300MB, that's what it will show when you do a 'df -h /system' command.
rocketero said:
it's not exactly that you need 500M on /system partition, as the size will just increase as you add files to /system, if you don't add any files the partition will stay the size it was originally, it works as the sparcefs file sistem does, it will show only what you have added from the total. Let's say you have grown the /system parttition to 300MB, that's what it will show when you do a 'df -h /system' command.
Click to expand...
Click to collapse
aha, thanks.
The image u just share didn't had google account, right.
I had now data.fs and sdcard.fs, which I extracted from BS 0.7.2... and already integrated into my BS 0.7.7.813, the advantages of .fs that I can resize it very easy. Do u advice me to share it?
actually, rooting and make some customization, was attractive, now joy was solved, it's boring
I can't even play where's my water? on BS, is for me only or with all?
mohazia said:
aha, thanks.
The image u just share didn't had google account, right.
I had now data.fs and sdcard.fs, which I extracted from BS 0.7.2... and already integrated into my BS 0.7.7.813, the advantages of .fs that I can resize it very easy. Do u advice me to share it?
actually, rooting and make some customization, was attractive, now joy was solved, it's boring
I can't even play where's my water? on BS, is for me only or with all?
Click to expand...
Click to collapse
I do have a sdcard.fs of 8GB working with v0.7.7.813, but even that I have not much in it the size would be huge to share it which makes it almost impossible to upload to any file-sharing site like dropox or box.net. I saw in an old post a shared sdcard 2GB in size but that's the default size when installing BS older than 0.7.3.x I believe. The Data.fs it has been always 2GB in size.
The good thing from updating BS from older versions to the new ones is that it will carry out the old Data.fs and Sdcard.fs and it will incorporate them into Data.sparsefs and SDcard.sparcefs
About the apps/games that run in BS it's just trial an error, sometimes very disappointing that it doesn't run the one's preferred apps.
It says that "Blue stack player app download in progress" and says its "already installed", error. idk what happens
tichs said:
It says that "Blue stack player app download in progress" and says its "already installed", error. idk what happens
Click to expand...
Click to collapse
You'll get more responses if you post on the official BS thread here: http://forum.xda-developers.com/showthread.php?p=33701742#post33701742
Code:
11- Open Superuser -> Settings -> Automatic Response -> Allow
Now your BlueStacks have root permission and google apps.
you mean that now i don't need anymore google play store because the Google apps are integrated in my bluestacks market?
thanks
kianty99 said:
Code:
11- Open Superuser -> Settings -> Automatic Response -> Allow
Now your BlueStacks have root permission and google apps.
you mean that now i don't need anymore google play store because the Google apps are integrated in my bluestacks market?
thanks
Click to expand...
Click to collapse
no what I actually meant is that ur system now have google permission, you can now install google play and it will works.
OK, when I did this guide, I did not differentiate between apps that set on /system/app and /data/app.
I will attach google play now to installed as com.nosh*.apk, just download it and double click to install
Code:
I will attach google play now to installed as com.nosh*.apk, just download it and double click to install
excuse me... i have search for google play apk on first post but i don't found it... where is it?
thanks
kianty99 said:
Code:
I will attach google play now to installed as com.nosh*.apk, just download it and double click to install
excuse me... i have search for google play apk on first post but i don't found it... where is it?
thanks
Click to expand...
Click to collapse
I'm review now the method from scrash
i've installed the two apk you mentioned and say me an error:
Code:
apk installation failed: INSTALL_PARSE_FAILED_NO_CERTIFICATES
kianty99 said:
i've installed the two apk you mentioned and say me an error:
Code:
apk installation failed: INSTALL_PARSE_FAILED_NO_CERTIFICATES
Click to expand...
Click to collapse
OK, I just remove BS, for re-install it, to start from scrach, I will update soon
AMD Appzone its better than bluestacks? I read that they have some unique technology that uses the gpu to accelerate everything, is that available to normal blue stacks builds?
tichs said:
AMD Appzone its better than bluestacks? I read that they have some unique technology that uses the gpu to accelerate everything, is that available to normal blue stacks builds?
Click to expand...
Click to collapse
no, bs is a no gpu accelerator. Even youtube not work
Sent from my HTC Desire HD using xda premium
kianty99 said:
i've installed the two apk you mentioned and say me an error:
Code:
apk installation failed: INSTALL_PARSE_FAILED_NO_CERTIFICATES
Click to expand...
Click to collapse
1- Now delete ur root.fs & data.s* from %programdata%\bluestacks
2- Extract data.s* from the archeive @ %programdata%\bluestackssetup on %programdata%\bluestacks
3- Follow new guide (exactly) with excluding steps 1 and 3 (just skip and contiune in same sequance)
Sent from my HTC Desire HD using xda premium
mohazia said:
no, bs is a no gpu accelerator. Even youtube not work
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
so they are the same thing right just different name?

Useful one touch pixi 4007E rooting and shell commands

+ Alcatel one touch pixi 4007E
+ Firmware Version: 2.3.6
+ Baseband Version: 6575M
+ Kernel Version: 2.6.35.7
+ Build number: GINGERBREAD
Useful shell commands
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod -R 755 <dir>
{ :;}; su
rm custpack/app/withlibs/Gmail.apk
rm custpack/app/withlibs/UNO3_20130613_100_gl_global.apk
rm custpack/app/withlibs/OnetouchLive_PIXO_20130723_V2.7_AMERICAS.apk
cd /data/data/com.bcmon.bcmon/files/tools
svc wifi enable
svc wifi disable
uname -a
mkdir backupwifi
mv WifiWsdsrv.apk backupwifi/WifiWsdsrv.apk
I hope these links are still valid, all is good and working October 5th, 2014, if any links die, please contact me and i'll see if i still have a copy of the files in a backup.
Device was rooted using the following software, from tutorial with these listed steps (below, cannot post links yet sorry) :
Software: Vroot App – VRoot_1.4.2.3195_Setup_95.exe @ a TinyURL
Tutorial: the root-alcatel-one-touch-pixi from ninjaromeo
Steps:
Make sure you have downloaded the above file.
Install it on your PC or Laptop.
Make sure that you have installed USB Drivers on your PC.
Then Open the installed program.
Now connect the phone to Computer using Original USB data cable that you got it when you bought the phone. Because using other kind of cables may not be detected by the computer. So only we are recommending to use the original.
Make sure that USB debugging is enabled on your phone.
Then wait for the Vroot to detect the device.
After that click the green button.
Then in a few seconds your mobile will be rebooted.
When it reboots your device must be rooted.
Then go to the Google Play store and download the SuperUser app or update it.
Now your mobile has been rooted successfully.
Then you can remove the phone from the Computer.
Normally first boot take some long time to complete. It will install the updates on the first boot. So, wait un till it finishes the booting process.
If your phone has stuck on the welcome screen or boot screen, just remove the battery and re insert it and do the above steps again.
Additional (important) software installed:
Terminal Emulator for Android
Jack Palevich
- June 20, 2014
Phone is rooted without issue all software installed fine but bcmon.apk (for wireless monitor mode) is not functioning by out of box root but i am working on it, arghum... aircrack-ng also does not function out of the box, titanium backup functions correctly and phone appears to operate perfect after Gmail.apk (bloatware) was removed (after many super stressful hours of directory scanning and OS information gathering but not bad for $99 and some mind numbing research lol!).
Argh... will keep posted on bcmon
Current issue (October 06th, 2014 12:48AM EST +10) = <message>command: 'cp' failed with exitValue = 127</message>
so...
install the following BusyBox to help get bcmon to work on this device:
BusyBox X
Robert Nediyakalaparambil [root]
- August 8, 2014
and now bcmon records are as follows:
"<record>
<date>Oct 6, 2014 2:16:47 AM</date>
<millis>1412522207853</millis>
<sequence>9</sequence>
<logger>com.bcmon.bcmon.chipsets.BCM4330B2</logger>
<level>FINE</level>
<class>com.bcmon.bcmon.chipsets.Chipset</class>
<method>detect</method>
<thread>0</thread>
<message>return false</message>
</record>"
then... now... i have arghum... downloaded the entire bcm4330/ directory from bcmon googlecode /svn/trunk/ and simply copied to the phone's sdcard via usb mode.
opened terminal (on phone) in su mode, navigated to bcm4330/driver/src/bcmdhd/ and attempted to launch sh build.sh but now have the following error:
"can't cd to /data/data/jackpal.androidterm/app_HOME/android/system/kernel/samsung/smdk4210
make: command not found"
More of a note really, a side bit of information
... installed Android SDK (Eclipse) and prerequisites (Java 64bit, in Windows), with phone connected via usb, and sdcard usb mode disabled (card mounted on phone and not windows).
Simply extraced archive to desktop (C:\Users\<username>\Desktop\adt-bundle-windows-x86_64-20140702).
Within the extracted folder you will find the following directory (providing the same versions) "\sdk\platform-tools" and within there resides the adb.exe windows command line tool.
I have now opened a command-line window (cmd.exe) at this directory ("\sdk\platform-tools", held shift and right-clicked on folder, windows 7) and issued the following commands:
adb reboot
adb /proc
things appear to have executed perfect, so i CUT all files and folders from the directory "C:\Users\<username>\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools" and pasted them into a new folder called "backup", i am now left with three files "adb.exe", "AdbWinApi.dll", "AdbWinUsbApi.dll" and one folder "\backup" in this directory...
i now re-execute the following command:
adb /proc
it would appear as though all the files that i CUT from this directory are in fact being rebuilt...
the adb.exe windows process finished with the result:
"31308 files pulled. 0 files skipped."
Click to expand...
Click to collapse
must say...
i dig this QR --> http://forum.xda-developers.com/member.php?u=1164149
and have concluded the following results.
bcmon is useless!, wifilog does not work on Alcatel one touch pixi 4007e but does on ZTE Telstra UNO T12, WiFiReaver, Wifi Analyzer and Wi-Fi Direct are all that is needed, in fact i have uninstalled bcmon and BusyBox.
Use mobiles to locate networks and normal means for wireless traversal, why else do people buy mobile phones?.
For an extra note on this model phone (and this will be posted in a separate thread) and help on removing apps manually (i had to do this as android would not allow me to uninstall and it was no longer listed as an installed app in Google Play )
I used the following commands (In Terminal Emulator) in this order to remove Wi-Fi Direct (in this case but same process should work for other apps) manually (remember this is only a backup of the app and not a complete removal in the phone system, bricks are not to be made but found, this merely removes the app from the android dashboard/desktop/app list)...
su
ls
cd system/app
ls
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mkdir backupwifi
mv WifiWsdsrv.apk backupwifi/WifiWsdsrv.apk
mv WifiWsdsrv.odex backupwifi/WifiWsdsrv.odex
mv WifiContactSync.odex backupwifi/WifiContactSync.odex
mv WifiContactSync.apk backupwifi/WifiContactSync.apk
mv WifiP2PWizardy.odex backupwifi/WifiP2PWizardy.odex
mv WifiP2PWizardy.apk backupwifi/WifiP2PWizardy.apk
And to actually remove the backupwifi folder (completely remove everything from system) issue the following command...
rm -r backupwifi
Click to expand...
Click to collapse

[Discussion] XOLO Q2000L

About the device:
http://www.xolo.in/Q2000L
http://www.gsmarena.com/xolo_q2000l-6495.php
Stock Firmware:
Latest : S017_01-07-2014 (KitKat 4.4.2)
https://drive.google.com/uc?id=0B6xlBPoXgsR3U0JBWm5oT0J5bUU (Source)
Code:
File: Xolo Q2000L S017 01-07-2014-(by_xdafirmware.com).zip
CRC-32: eb227244
MD4: c8d1739be1fe45d43d8fd2a1615d680d
MD5: 07a484331431e523e5067186f07f0ac3
SHA-1: e808227b928fd03f0696ef6e37015432c06fade5
Flashing Instructions:
Prerequisites:
1. Broadcom MultiDownloader
(Latest one I can find is V2.0.1; Source)
2. Broadcom USB Download Device driver
(Latest one I can find is v1.0.5, mirror by @moulnisky. Broadcom uses two interfaces for flashing - one is serial/COM & another is USB but now they encourage to use the later one. Remember that the driver's digital signature isn't valid for 8.1/10 so you need to turn off driver signature enforcement to install the driver. To install the driver manually, open BRCM_WinUSB_ADB_Jungo_MTP_RNDIS_Driver_1.05.exe using 7-Zip, extract the contents & install the using bcmusbdl.inf)
Follow this tutorial, but we need some enhancements:
1. At step 8, I've chosen Download Mode as "Flash All Image" i.e the first one.
2. Skip step 9 & 10, come to step 11 i.e press 'Flash' button.
3. After that, connect the device in flashmode i.e as described in step 9. If Broadcom USB Download Device driver is properly installed, then flashing will begin. FYI, the hardware ID of the flashing interface is USB\VID_0A5C&PID_E720.
USB Debugging:
Broadcom bundles signed drivers for ADB/MTP/RNDIS interfaces along with the device itself (in the emulated CD drive). I've also mirrored it here. As an alternative, you can also use Android USB UnifL driver.
Remember that current ADB binary requires vendor ID whitelisting to detect Broadcom SoC. So execute Broadcom_SoC_Drivers.rar\AndroidPCUSBdrivers\andro id adb\brcm_adb_vendor_id.bat to do it. Otherwise ADB can't see the device, even if drivers are properly installed.
Rooting:
After you are able to communicate with the device through ADB, use iRoot to root it. Make sure to uninstall two Chinese bloatwares that came with Kinguser. I personally prefer to use SuperSU by @Chainfire, so we need to tinker with it again.
1. Install BusyBox.
2. Thanks to @idler1984, we've an easy way to switch from Kinguser to SuperSU. See here, search for "Q: I'd like switching to SuperSU, what shall I do?". I'm also providing the modified steps here which fits our needs:
2.1. Download SuperSU (I prefer the latest beta though). Open the zip, go to armv7 folder & extract the file named "su".
2.2. Use ADB to push su to /data/local/tmp:
Code:
adb push su /data/local/tmp
2.3. Start a su session and run the following commands:
Code:
adb shell
su
mount -o remount,rw /system
cat /data/local/tmp/su >/system/xbin/daemonsu && chmod 0755 /system/xbin/daemonsu
cat /data/local/tmp/busybox >/system/bin/busybox && chmod 0755 /system/bin/busybox
daemonsu -d &
Then keep the session running.
2.4. Open Kinguser, go to Settings -> Root authorization setting -> Remove Root permission. Click to remove root permission. It may crash but its harmless. Your su session should be still running.
2.5. Uninstall Kinguser app.
2.6. Go back to the su session and run following commands to replace su and cleanup:
Code:
cat /data/local/tmp/su >/system/xbin/su && chmod 0755 /system/xbin/su
busybox chattr -ia /system/bin/ddexe
busybox chattr -ia /system/bin/ddexe_real
cat /system/bin/ddexe_real >/system/bin/ddexe
busybox chattr -ia /system/xbin/ku.sud
rm /system/xbin/ku.sud
rm /system/xbin/pidof
rm /system/xbin/supolicy
2.7. Install SuperSU; get it from SuperSU zip => common\Superuser.apk.
2.8. Open SuperSU to update files & reboot.
2.9. (Optionally) make SuperSU a system app.
Other Notes:
1. This device has fastboot interface too; you can access it by running
Code:
adb reboot bootloader
2. To force install applications in SD card, use this:
Code:
adb install -s NAME.apk
Reserved for future use.
This post is kinda hard to find. But the instructions are good. They all work on my Xolo Q2000L.
Thank u @Titokhan for great help. Please help me over internal app storage issue. This phone is lacking good internal storage even it is having 8gb (5.29 gb on board). Please help.

Categories

Resources