Develop Bugs

update 18-may dualizer major update: full toolkit(beta)!

major update here, the dualizer has become a feature rich toolkit for dualbooting. this includes a modified version of amon ra's recovery image. you need it to use the dualizer toolkit, it is included and can be flashed with one command.
it is a beta version for now. i have tested each option, but i cannot foresee all conditions you might have on your phone... have a backup at all time! and don't forget to backup the stuff from your sdcard before installing dualboot, during the creation of this toolkit i accidently deleted everything on mine...
there is no logging at the moment, if you get any error messages please paste them here in full.
i haven't tried a nandroid backup at all yet, and wouldn't advice you to do it either. please use apps like titanium backup to backup your stuff. i will be looking into getting some kind of nandroid capability, but that is not a trivial topic. i can however imagine to have full pc-based backup capabilites, sometime in the future...
before you use any of the romX options make sure you have installed the dualboot environment, i have no idea what happens otherwise...
i have tried to include a full description, please let me know if something is unclear (i hope it is obvious that romX needs to be replaced with either rom1 or rom2):
Code:
kendon's dualboot toolkit for the HTC Hero
usage: ./dualizer <option>
place the two roms you want to use for dualbooting in the
rom1 and rom2 subdirectories. make sure directories do
contain other files. you can use the temp/ subdir of the
two rom folders to store your roms while you want to flash
another update.zip
you need a modified version of Amon_Ra's custom recovery image.
it can be installed with this tool, see the options.
options are:
help show this information
vmsetup prepare ubuntu vm for usage
check-dev check if your device is properly attached and connected via adb
boot-rec reboot hero to currently flashed recovery
check-rec check if RA-hero-v1.6.2-DBmod is currently flashed
boot-dbmod put hero in fastboot mode (back+power) first!
fastboot hero with RA-hero-v1.6.2-DBmod
no permanent changes are done, works with unlocked spl only
NOTE: the trackball doesn't select, use green key instead
unlocked-spl copies update.zip for unlocked spl to sdcard, so you can flash it.
if this goes wrong it can brick your phone, make sure you do it right!
flash-dbmod flash RA-hero-v1.6.2-DBmod to recovery partition (permanently)
NOTE: the trackball doesn't select, use green key instead
install-db ALL your data will be lost, so you better have a backup!
install dualboot environment on htc hero
this includes partitioning of the sdcard
place roms in folders rom1 and rom2 first!
romX wipedata wipe data/factory reset romX
romX wipedalvik wipe dalvik-cache for romX
for the following options place update.zip file in folder romX first!
romX flash flashes update.zip from folder romX
romX makeboot create boot.img-update.zip files for romX
romX makeboot push create boot.img-update.zip files for romX and push it to /sdcard
i don't see any potential to brick your phone, even if it fails, as the critical parts (spl, radio) are not touched at all. worst that could happen is that you have to do a full wipe and flash a rom... be careful while flashing recovery and/or bootloader though!
as always: use at own risk!
note: first (and maybe second) boot maybe painfully slow. after that it gets better, see for yourself if it is too slow for you. i have been using villainrom and slidevillain in a dualboot for a few days now, i haven't noticed too much slowdown. then again i don't care too much about this.
credits: huge thx to the ppl in this thread: http://forum.xda-developers.com/showthread.php?t=594077 the information in there helped a lot.
changelog:
v0.2: major update, toolkit for flashing, wiping etc.
v0.1: initial release

installation & usage instructions
please read the first post before you install dualboot!
instructions for windows:
instructions for windows said:
the dualboot install can now set up all necessary stuff in a fresh installed ubuntu virtual machine in virtualbox. you must have adb access to your hero from the windows command line, if you need help check theunlockr.com for their awesome video tutorials.
here is a great howto install virtual box in windows: http://www.psychocats.net/ubuntu/virtualbox
and this is the second part, howto install ubuntu in a virtual machine: http://www.psychocats.net/ubuntu/installing
once you are done installing ubuntu download the archive from the first post and follow these steps (the default download directory is "Downloads", so i'm gonna use that in this example):
- go to "Downloads", you find it in "Places" in the upper menu bar
- rightclick the zipfile you just downloaded and select "Extract Here"
- open a terminal window: goto Applications, Accessoires, Terminal
- execute these commands:
Code:
cd ~/Downloads/dualizer/
chmod +x dualizer
./dualizer setup
it will ask for your password once, then do some stuff and finally reboot the virtual machine.
once rebooted, connect your hero to your pc, rightclick on the usb sign in the lower right corner of the virtual machine window and select the "HTC Android Phone". some hardware installations from windows might pop up (happened to me), just click on next and let them do their stuff. if it doesn't work at first shut down ubuntu, then restart your pc and continue. "reboot tut gut", as the german likes to say
back to ubuntu, with your hero connected to pc and virtualbox, open a terminal and check if your hero is detected by adb with the following commands:
Code:
cd ~/Downloads/dualizer/
./dualizer check-dev
this will tell you if your device is properly connected. you can now continue with the options you can get from
Code:
./dualizer help
Click to expand...
Click to collapse
instructions for linux:
instructions for linux said:
you need java, perl and zip setup, make sure that these are available. then follow these steps:
- extract the attached zipfile from the first post on your pc (for this example i'll assume you extracted it on your desktop).
- get the two roms you want to dualboot, do not extract them.
- put one rom in the rom1 folder, the other rom in the rom2 folder inside the dualizer folder on your desktop.
- open a terminal, cd to the folder and make the main file executable by typing:
Code:
cd ~/Desktop/dualizer
chmod +x dualizer
- turn on your hero (recovery or normal, doesn't matter)
- connect your hero to your pc and check if your hero is detected by adb with the following commands:
Code:
./dualizer check-dev
this will tell you if your device is properly connected. you can now continue with the options you can get from
Code:
./dualizer help
Click to expand...
Click to collapse

reserved...

Holy... this is incredible. Great job on getting this out.

I use a virtual box and ubuntu 10.04 lts.The method seems to work but in step 3 on partition card my hero restarts and boots in recovery and i don't have time to mount the usb/htc device into virtual box so i get in step 5 an no device found error.The time is very short.I have to press USB-MS toggle on my hero and after that i have to mount it in virtual box.I've tried it over 20 times but i don't have time and in terminal get me the error.Is there a way to pause the process or a solution to my problem?
Sorry for my bad english
EDIT:SOLVED.Set the sleep from dualizer in step3 from 15 to 30.Wainting for setup to finish.Cross my fingers
EDIT2: Ok now this is getting awkward.Waiting on step 4 (push to sd) for 25 minutes now.I have checked the log.Last line says mounting /dev/block/mmcblk0p1 on /sdcard failed: No such file or directory.Should I wait for it any longer?Or what should I do now?

As I have said on the VillainROM forum; this is really outstanding work.
Well done, Kendon.

Zero00SM said:
EDIT2: Ok now this is getting awkward.Waiting on step 4 (push to sd) for 25 minutes now.I have checked the log.Last line says mounting /dev/block/mmcblk0p1 on /sdcard failed: No such file or directory.Should I wait for it any longer?Or what should I do now?
Click to expand...
Click to collapse
that shouldn't happen, and the pushing shouldn't take longer than a few minutes. you should cancel it by pressing ctrl-c, if you fancy debugging then check why it wouldn't mount. otherwise you can partition your sdcard, do a full wipe and should be able to flash a regular rom.
i guess i underestimated the complexity of the virtual machine solution, gotta look deeper into this... *sigh*

Hi, regarding the Apps2SD issue... Would it ever be possible for the two ROMs that are dual booting to have the same apps sourced from one place... if that makes any sense...
Like in windows... you can "install for all users" so if you log off and someone else logs in with there account the very same apps are there...
Ok bad analogy since we are talking about dual booting different versions like (Vista & Windows 7) ... but the same data on hdd is accessible...
is this possible with the dual booting scenario?
If I had Slide Villain and Villain 5.5 .. both being 2.1 ROMs which would make app compatibility a non-issue...
If I booted up Villain 5.5 and made changes to an app / save data .. could this not be accessible with the slide rom.. I would hate having to install the very same apps on another partition..worst of all if you have save data (such as a game) and wanted to play it on one of the ROMs your game progress would be different?
you could just use Titanium to transfer over the data but agaqin it is a long procedure.
It would be fantastic if we could mirror image exactly what we have on our main Roms to our "secondary roms" ...

Amazing !
Ciao
Fred

Yeah this is really amazing. I have read this on villainRom forum, and i was stupified .
But, if i want to flash another Rom as primary and need to wipe cache, i need to do this process again! Am i right?

for the shared apps:
a shared apps2sd directoy/partition is possible, although you'd have the problem that apps are installed to one market only, and idk what would happen when you update an app in one rom, would the update get market-linked in the other? you can solve this with titanium backup, but it isn't really comfortable at all. i'll think about this.
for shared data: in theory possible as well, but i don't think it would work out well. you cannot distinguish between system data and apps data that easily, and i don't think it would work to share system data (sense settings etc) between two different roms...
@masterxiter: easiest way to do this is to use the installer script again. you can wipe the cache manually, installing another rom would be really complicated (about as complicated as the installer script )...

Sweet. But is there any way i can run this in cygwin? every version of linux ive tried so far doesnt support my crap compaq wifi card or most things, or even wired for that matter, and running ubuntu in a virtual machine gives a reboot every time after step 1 (maybe cos i suck at terminal)

i'll try some time, but i have never used cygwin... so don't expect anything too soon.

joshman99 said:
Sweet. But is there any way i can run this in cygwin? every version of linux ive tried so far doesnt support my crap compaq wifi card or most things, or even wired for that matter, and running ubuntu in a virtual machine gives a reboot every time after step 1 (maybe cos i suck at terminal)
Click to expand...
Click to collapse
if you install ubuntu in an virtual machine like VMware(paid) or virtualbox(free) you can just use linux, it will automatically grab all your internet settings and stuff from the windows installation(main computer) so your windows will be like some kind of router for your virtual machine with everyhing working.
Very nice tutorial, i'm not going to try it.. because my phone has to be resend to HTC for fixing some dead pixels, there just messers with screens
BTW. you can also try another linux version sounds crazy, maybe try backtrack?? the only thing you need is linux, backtrack is..

I have backtrack 4 (I could never get wifi on that either, but tbh i couldnt work out how to try (that distro is soo confusing imo). I got backtrack 3 to work a while back, so if i can find the disk im gnna try that.
Also virtualbox didnt put my internet settings at all (maybe co im on win7 ultimate?)
Thanks for the suggestions, cos i know cygwin aint the most elegant solution

changing rom 1 and rom 2
i test lotz of roms.... everyday they are being updated...
say if i dualize with ahero0.8 and Kimera 1.7....
wud i be able to update aHero to 0.9 and leave kimera as it is???
simply can i update JUST ONE rom???

manual setup??
i tried it got error in step 3 and then 'Device not found errors...'
can u make a tutorial for doing it manually.....

kendong2 said:
please read the first post before you install dualboot!
instructions for linux:
you need java, perl and zip setup, make sure that these are available. then
Click to expand...
Click to collapse
hihi.. i am trying to do a dual boot, so im wondering what u mean by.. need java , perl and zip setup... can advice me?

He means that you need to have Java, perl and zip installed and configured on your Linux system. If you dont have that installed and configured correctly than the install script wont be able to run.

lolnl said:
He means that you need to have Java, perl and zip installed and configured on your Linux system. If you dont have that installed and configured correctly than the install script wont be able to run.
Click to expand...
Click to collapse
oh noes.. .i do not have those in my ubuntu, does that mean i cant do a dual boot? btw, i saw post 2 and post 3 ... are they the same instruction ? or different? (one for windows user and one for linux?)

[TUT] Smphony.W25/Karbonn.A7/Mobistar.S01/Ktouch.W650 Rooting Process and Custom ROMs

Symphony W25 device Finally Rooted !
{
"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"
}
All credits go to jason_cheng
Procedure given below:
1. First of all, you need Drivers For your symphony W25 (Smphony.W25/Karbonn.A7/Mobistar.S01/Ktouch.W650 All are the same phone)
Driver for winXP
Get them here (uploaded by prasad12ka4) Or Here uploaded by rainwalker
Click to expand...
Click to collapse
Drivers for Win 7 / Win 8
Get them here
Click to expand...
Click to collapse
64-Bit Win 7 Drivers
Get them here
Click to expand...
Click to collapse
Install them while connecting your phone on "USB debugging mode", and going to "device manager > other devices" on your pc. After installation disconnect the phone.
(I believe some of you are having problems installing the drivers. I recommend you install the drivers on a freshly installed winXP pc. I faced a lot of trouble doing it on my Win8 pc)
2. Download Android software development kit (SDK) from Here and install in pc. Default installation Directory should be C:\Program Files\Android\android-sdk
3. Android SDK may need Java development kit (JDK) installed in pc. If you need jdk, go here or go to their Website to download
3. Download Fastboot From Android Central and keep it inside
C:\Program Files\Android\android-sdk\platform-tools folder
4. Download Clockwork Mod Recovery for w25 from Link #1 or Link #2, unzip and copy to the same folder. replace duplicate (if prompted).
5 hook your phone up with pc in USB debugging mode and go to C:\Program Files\Android\android-sdk\platform-tools folder, Press Shift+right click inside that folder and select "open cmd window here". It opens a cmd window for that folder.
In the cmd window, type
Code:
adb devices
If the driver installations are correct, you'll see your device connected as w650 (as symphony is re-branded from k-touch w650)
6. Disconnect phone from pc and reboot it into the bootloader, by turning it off and holding [vol-up]+[power]
Till screen turns green and says fastboot:recovery ?, Like below
7. Plug your phone into your computer. On cmd window, type:
Code:
fastboot devices
Reply should be "???????????? fastboot" Meanng fastboot detected the device.
8. In the cmd line, type
Code:
fastboot boot recovery-english.img
And that's it. You'll have booted into the custom recovery (cwmr), and from there you can do a full backup, or restore a backup, or wipe the phone. Use vol up/down to navigate through screen and Power to select an item.
9. Use CWMr to backup your ROM. (It will be saved in: "SD card/clockwork mod/backup" on phone.) and reboot. Copy the backup into pc for further use.
Step 8 was to make sure cwmr works on the phone. It's a temporary port of cwmr on your device.
if problem occurs (less likely to occur), let us know in a comment and don't proceed further.
Otherwise, Proceed below for permanent port..
10. Repeat step 6 and 7. Go to C:\Program Files\Android\android-sdk\platform-tools folder and click on recovery.bat file. Click on it and in the next window, Press any key
Permanent port will be completed
reboot phone if not rebooted automatically.
11. To check cwmr, Repeat step 6 but keep pressing the two buttons even if the screen turns green (fastboot). Continue until.....
screen is red (recovery). after that you'll see Clockwork mod recovery page.
You'll need it to restore your original rom if you mess up anything.
12 In CWMr,
a)]Go to Advanced
b) Choose "Wipe dalvik-cache"
c) Now go to "Mounts & Storage"
d) Choose "Format /cache"
e) Shutdown your phone
13. Download and unzip bootrepack from this post (by jason_cheng). Copy the "boot.img" file from "rootrepack" folder and paste to C:\Program Files\Android\android-sdk\platform-tools folder
14. Repeat steps 6 & 7 (green screen)
15. In cmd window type
Code:
fastboot flash boot boot.img
and
Code:
fastboot reboot
see image below if you have any confusion.
16. After the phone is restarted, type in cmd window:
Code:
adb shell id
which should result "uid=0(root) gid=0(root)"
Rooting is now Unofficially completed
17. To verify, Type each line in cmd window, and press enter
Code:
adb shell
Code:
echo "1" > /system/pwned
Code:
cat /system/pwned
If the Reply to the last line is "1", Congrats ! you have root access to your phone!!
Now remove that test file you created just now. Type:
Code:
rm /system/pwned
What now?
18. Install "Superuser" from Play store
It does not come with su binary. For that, Go to this post and download only the attachment. Unzip it and put the files in C:\Program Files\Android\android-sdk\platform-tools folder.
19. Now open cmd window, type each line and enter.
Code:
adb remount
Code:
adb push su /system/xbin/su
Code:
adb shell
Code:
chmod 4755 /system/xbin/su
now open superuser and check for su binary. I don't recommend su update.
20. Install "Busybox free" from Play store (optional)
Rooting Officially Complete.​
If you face problems at any step, please let us know in comments. We'll try to help.you out.
Also feel free to try out the IceCream Sandwitch based roms & the upcoming Jelybean rom for Symphony W25 on the second post of this thread.
If any of you come across a new rom for w25. Please do share.
If you come across dead links on my thread, plz let me know by posting comments, or PM me.
If you find this post useful, then plz hit the thanks button and share it with people who have this phone and waiting for root
End of tutorial.​
.usefull links:
Karbonn Mobile A5 & A7 (Android 2.3.6)
Link2sd tuorial in bangla: সহজেই বাড়িয়ে নিন অ্যান্ড্রয়েডের ইন্টারনাল মেমোরি
How To Solve Internal Memory Problem(Great Post)

Custom Roms for Symphony W25 / Mobistar s01 / KTouch W650 / Karbonn A7
Custom Roms for Symphony W25 / Mobistar s01 / KTouch W650 / Karbonn A7
Here you'll find Custom ROM For Karbon A7 device. Which might also be campatible for Symphony w25. Read the respective posts/ comments carefully before downloading and installing.
(first of all back up your existing ROM with cwmr before any change you do to it.)
1) ICS ROM v1 for Symphony W25, Created By rainwalker
Click to expand...
Click to collapse
2) ICS ROM v2 for Symphony W25, Created By rainwalker
Click to expand...
Click to collapse
3) MIUI Gingerbread 2.3.7 ROM (update.zip file), moded By rainwalker
Click to expand...
Click to collapse
4) Rooted Stock ROM of Symphony W25 (update.zip file), uploaded By rainwalker
Click to expand...
Click to collapse
5) Stock Google android gingerbread for a7 by meosuper
Click to expand...
Click to collapse
6) ICS Huawei For Karbonn A7 / S01 by meosuper, Uploaded by ItsmezakiR
Click to expand...
Click to collapse
7) Official ICS ROM for Karbonn A7/Symphony W25 Uploaded by The Droid Master
Click to expand...
Click to collapse
8) Walton Primo ROM modified for A7 Uploaded by vinodkbishnoi
Click to expand...
Click to collapse
9) XION ROM FOR A5/A7 Uploaded by deadlyindian
Click to expand...
Click to collapse
10) ICS refresh V3 Uploaded by meosuper
Click to expand...
Click to collapse
11) CyanogenMod 10 (Karbonn A7) Beta Posted by prasad12ka4
Click to expand...
Click to collapse
12) Backstreet MOD™ v4.1.1 created by The Droid Master
Click to expand...
Click to collapse
13) Lithium 7 for Karbonn a7, symphony w25 and Mobiistar s01 Created by rainwalker
Click to expand...
Click to collapse
14) XINIX 8 for Symphony w25 Created by rainwalker (Recommended)
Click to expand...
Click to collapse
15) CyanogenMod 10 rom for W25 [Beta]
Click to expand...
Click to collapse
16) JELLYBEAN rom for W25 [Beta]
Click to expand...
Click to collapse

Maybe is needed to extract the "boot.img" to remove the restrictions on it, and make it rootable... Have you tried with generic "rooters"?

ICS Baseband Versions For Karbonn A7
ICS Baseband Versions For Karbonn A7 (= Symphony W25)
ItsmezakiR said:
1. 591369_8379_WCDMA_V000001
2. 591357_8376_WCDMA_V0005
3. 591352_8376_WCDMA_V0007
4. 591347_8376_WCDMA_V3070
Click to expand...
Click to collapse
ICS Search Key to Power Key (for Symphony W25)
vinodkbishnoi said:
Hi,
Karbonn A7 ICS. Now you can use search key of your A7 as power key.
Follow the procedure...
1. Download 7x27a_kp.kl.zip file and extract it.
2. Open terminal/Command prompt.
3. Connect your phone to PC via USB.
4. Run following commands.
c:/> adb devices
c:/> adb pull /system/usr/keylayout/7x27a_kp.kl
now copy this file on a safe place. So that if anything goes wrong you could be able to restore it.
now open folder where you have extracted the zip file. The extracted file will be of same name as "7x27a_kp.kl"
c:/> adb push <path to file 7x27a_kp.kl> /system/usr/keylayout/​
Now reboot your phone. You will be able to use your search key as power key.
Click to expand...
Click to collapse
Change partition size on A7/W25
Part1:
Anil_Sharma said:
To begin with, you need a hex editor, HxD - Freeware Hex Editor is a great editor and it is very small(less than an MB). Then you need a baseband to edit, you need to locate the file named ' appsboot.mbn '.
That file contains the partition tables, remember this tutorial is about editing the partition tables not extending your physical memory.
So, lets get cracking. Open HxD from programs and open the appsboot.mbn file, now press F3 and search for ' cache ' and press F3 until you see something like this
.
As you can see the highlighted section of the picture
,
there are a few repetitions of ' F0 F0 F0 F0 xx ' multiple times, you are concerned with only the first two /system and /cache partitions respectively.
Remember, you don't need to specify the partition size for /data as it is done automatically when you flash the baseband.
Now back to the hex editing part, once you've decided how much space(in MBs only) you wanna allocate to /system and /cache use this link to Convert hex/dec and select the two digits after the F0 F0 F0 F0 like in this pic
and type the hex number for example in the screenshot B4 in hex equals 180 in decimal, which means /system is allocated 180 MB of space and do the same with Cache, I would recommend allocating 10 MB to it as you hardly ever use it. Then flash the baseband like you normally do through Fastboot.
If you have any doubts ask me and I will do my best to clear things to you. Click Thanks if I helped you, doesn't cost anything
Click to expand...
Click to collapse
Part2:
vinodkbishnoi said:
Hi,
I am attaching a file named "appsboot.mbn". This is used to determine partition size on android system.
There are two ways you could use it.
1. Replace appsboot.mbn file in any baseband update BP folder.
2. If you are handy with fastboot commands there is very simple method. Just boot your phone in fastboot mode (green screen mode) and use
following command....
C:\>fastboot flash APPSBL <path to appsboot.mbn>​
And you are done.
You will find following changes.
1. Your partition size will be as shown in screenshot.
2. When you run command adb devices you will no more find S01 there, it will be A7
Download file here...
Download
Thanks
Click to expand...
Click to collapse

no one for help??

ahmed.zunaid said:
no one for help??
Click to expand...
Click to collapse
Your phone is the same with mobiistar s01 and karbonn a7, maybe the developer of symphony keep the original cpu clock(1ghz) and s01, a7 was underclocked to 800 to save battery. Now if you want to root.you must install fastboot driver and install cwm recovery for a7 first.then backup your current rom... when done, install rooted rom for s01 and you will have root, but your cpu will be underclocked to 800ghz.
And can you send me the link to download your backup rom??? I need the 1ghz kernel to mod my rom... thanks.
(If install drivers on w7 pc fail, try to use another pc with wXP-32bit).

These phones aren't - or shouldn't be - that difficult to root. I have just rooted an Xplorer W10 from W7 x64 (and reproduced on Linux), and it went without a hitch. Just a number of gotchas to watch out for (from here on I actually refer to W10 and all other models since they are of the same series):
1. Uninstall any kind of driver you have installed. Symphony does not provide drivers for their Android phones, as far as the website is concerned. You get what you pay for, and this is a relatively remote brand, so don't expect much. In fact, don't expect anything at all.
2. Download and run SuperOneClick. Click on the other tab and choose to check for drivers. You should be prompted to install a driver. Do it.
3. Unplug and replug the USB. Go into the ADB folder and shift-right-click, open a command prompt here. Type 'adb devices' and press ENTER. There should be at least one device listed (in the form of an alphanumeric serial).
4. If there is no device listed by ADB, use Linux to root. There is no need to install any driver on Linux, and SuperOneClick is multi-platform. You will need the mono package on Linux instead of .NET.
5. The phone is actually partially rooted. Whether by intention or by mistake, I am not sure. SuperOneClick will warn of this, so just choose to continue with the rooting process.
6. You should now be rooted.
Background:
There is no exotic bootloader locking going on with these phones, as far as I can tell. The manufacturers/vendors are really just trying to capture a certain segment of the market, so I doubt they'd go through extensive efforts to lock you in. Just find any exploit (right now psneuter and zergRush), put them on the phone along with the su and busybox binaries, execute the exploit, and you'll be good to go with the Superuser app.

ok ...
jason_cheng said:
These phones aren't - or shouldn't be - that difficult to root. I have just rooted an Xplorer W10 from W7 x64 (and reproduced on Linux), and it went without a hitch. Just a number of gotchas to watch out for (from here on I actually refer to W10 and all other models since they are of the same series):
1. Uninstall any kind of driver you have installed. Symphony does not provide drivers for their Android phones, as far as the website is concerned. You get what you pay for, and this is a relatively remote brand, so don't expect much. In fact, don't expect anything at all.
2. Download and run SuperOneClick. Click on the other tab and choose to check for drivers. You should be prompted to install a driver. Do it.
3. Unplug and replug the USB. Go into the ADB folder and shift-right-click, open a command prompt here. Type 'adb devices' and press ENTER. There should be at least one device listed (in the form of an alphanumeric serial).
4. If there is no device listed by ADB, use Linux to root. There is no need to install any driver on Linux, and SuperOneClick is multi-platform. You will need the mono package on Linux instead of .NET.
5. The phone is actually partially rooted. Whether by intention or by mistake, I am not sure. SuperOneClick will warn of this, so just choose to continue with the rooting process.
6. You should now be rooted.
Background:
There is no exotic bootloader locking going on with these phones, as far as I can tell. The manufacturers/vendors are really just trying to capture a certain segment of the market, so I doubt they'd go through extensive efforts to lock you in. Just find any exploit (right now psneuter and zergRush), put them on the phone along with the su and busybox binaries, execute the exploit, and you'll be good to go with the Superuser app.
Click to expand...
Click to collapse
I've used SuperOneClick before. In both 7 and XP machines. It gets stuck at "step 7".
Ok i'll try to do it again following your steps. I'll upload the screenshots
thanks for helping btw ...

No use ....
Nope. It didn't work. Hangs at step 7 (Pic Attached). tried on XP and 7.
Drivers install this time. and cmd>adb shell shows attached device, just like you said. but nothing happens after step7: waiting for device
I guess this process in not for me
can you provide link or tell me the process on how to add cwm recovery and backup the stock rom from the phone?
So that I can upload for you guys to check it out.
Note: my phone goes to recovery mode using the same method described in Karbonn Mobile A5 & A7 (Android 2.3.6
I checked.

ahmed.zunaid said:
Nope. It didn't work. Hangs at step 7 (Pic Attached). tried on XP and 7.
Drivers install this time. and cmd>adb shell shows attached device, just like you said. but nothing happens after step7: waiting for device
I guess this process in not for me
can you provide link or tell me the process on how to add cwm recovery and backup the stock rom from the phone?
So that I can upload for you guys to check it out.
Note: my phone goes to recovery mode using the same method described in Karbonn Mobile A5 & A7 (Android 2.3.6
I checked.
Click to expand...
Click to collapse
Unfortunately, CWMR needs to be built for your hardware in order for it to work. I think CWMR for the Karbonn should work without modification if it has the same hardware, so see if you can find info on getting CWMR onto the Karbonn. If the bootloader is really locked then you'll have to find some way to unlock first.
Backup the recovery partition [1] before doing anything, although I cannot verify whether it's the same partition across all phones. If anything goes wrong you will lose the ability to boot into recovery mode, but your phone will work. With a backup of the partition you can just bit-copy and rewrite the partition exactly as it was.
Because you already have the drivers installed using SuperOneClick, you may like to see now if Unlock Root works [2]. Else, go ahead and root the phone using the manual method. First, run the exploit [3]. Tell us how this goes, then we'll continue (basically upload the su binary and optionally the Superuser app). Otherwise we need to see what other exploit works.
[1] http://forum.xda-developers.com/showthread.php?t=1160213
[2] http://lifehacker.com/5873745/unlock-root-roots-nearly-250-android-devices-in-one-click
[3] http://forum.xda-developers.com/showthread.php?t=1296916

Could you please also report back with some files after running the following commands (you will find them prefixed with w25_ from the folder you're running ADB):
Code:
adb shell cat /proc/cpuinfo > w25_cpuinfo.txt
adb shell getprop > w25_propinfo.txt
Thanks. I suspect the W25 does not have the Karbonn A7 hardware. If the Karbonn is a rebranded Mobilstar S01 then it has a Qualcomm ARMv7 processor. The Symphony phones (hypothesis based on the only one phone I have, that is a W10) are rebranded Tinno [1] phones, with MediaTek processors.
My W10 is ARMv6, so it depends on whether the W25 has an SoC based on the latest MTK proc (which is ARMv7) [2]. That is highly unlikely because it (the proc) would be too powerful for the model number. As you may or may not know, binaries are not portable across ARM cores.
The phones do indeed have the same chassis and general specs, but any attempt to port and/or copy files/ROMs must be taken with great care and precautionary steps. There is, of course, no rule that each model must depend on the same manufacturer, but it's better to be safe than sorry.
[1] tinno.com (i'm not allowed to post links, funny, did so in the previous post)
[2] mediatek.com

jason_cheng said:
Could you please also report back with some files after running the following commands (you will find them prefixed with w25_ from the folder you're running ADB):
Code:
adb shell cat /proc/cpuinfo > w25_cpuinfo.txt
adb shell getprop > w25_propinfo.txt
Thanks.
...... ...... ......
Click to expand...
Click to collapse
#1 cpuinfo Attached
#2 Prop info Attached
It says ARMv7 processor. So what should I do now?
[off topic. rooted my friends Xperia arc today. Was very easy, like : DL kernel>click some stuffs>plug out>turn off>press n hold button>plug in>done
they should've made it simple for this one. just sayin .. :/ ]

ahmed.zunaid said:
#1 cpuinfo Attached
#2 Prop info Attached
It says ARMv7 processor. So what should I do now?
[off topic. rooted my friends Xperia arc today. Was very easy, like : DL kernel>click some stuffs>plug out>turn off>press n hold button>plug in>done
they should've made it simple for this one. just sayin .. :/ ]
Click to expand...
Click to collapse
Well, popular devices have more people tinkering with them and hence more results I suppose for budget devices we are on our own. After all, I believe these phones are pretty value for money and the effort to tinker is worth it.
Anyway, my suspicions are wrong. Symphony (or whoever they rely on) hand-pick reference models and do not depend on any particular vendor. The W25 is ARMv7 from Qualcomm, rebranded from K-Touch W650 [1] with modest hardware upgrades, almost similar to the Mobiistar and Karbonn:
Mobiistar Touch S01: Qualcomm MSM7225A
Symphony Xplorer W25: MSM7627A or MSM7625a (but because of 1GHz clock more likely the former) [2]
Either way the differences are minor I presume. Clock speeds are different and on-chip options vary slightly depending on what the manufacturer opts for. So with a bit of work someone could port existing recoveries and ROMs from similar devices. See [2] for a list of such devices in the respective row for MSM7627A.
You can worry about this when you come to recovery. The first hurdle to get through is root, so have you proceeded to run an exploit?
Also, if you haven't done anything, I would suggest doing a factory reset and then backing up the entire ROM simply with the cat command [3]. The homemade unsigned backup may come in handy later as there is no official ROM update.
[1] 123.chinatronic.com/products.php/K-Touch-W650 [replace 123 with www]
[2] en.wikipedia.org/wiki/Snapdragon_(system_on_chip)
[3] android-dls.com/wiki/index.php?title=HOWTO%3a_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images

jason_cheng said:
..... Symphony (or whoever they rely on) hand-pick reference models and do not depend on any particular vendor. The W25 is ARMv7 from Qualcomm, rebranded from K-Touch W650 [1] with modest hardware upgrades, almost similar to the Mobiistar and Karbonn:
Mobiistar Touch S01: Qualcomm MSM7225A
Symphony Xplorer W25: MSM7627A or MSM7625a (but because of 1GHz clock more likely the former) [2]
Either way the differences are minor I presume. Clock speeds are different and on-chip options vary slightly depending on what the manufacturer opts for. So with a bit of work someone could port existing recoveries and ROMs from similar devices. See [2] for a list of such devices in the respective row for MSM7627A. ....
Click to expand...
Click to collapse
it says HTC Desire VC T328d, Huawei Ascend C8812 ...
jason_cheng said:
............
You can worry about this when you come to recovery. The first hurdle to get through is root, so have you proceeded to run an exploit?
Also, if you haven't done anything, I would suggest doing a factory reset and then backing up the entire ROM simply with the cat command [3]. The homemade unsigned backup may come in handy later as there is no official ROM update.
[1] 123.chinatronic.com/products.php/K-Touch-W650 [replace 123 with www]
[2] en.wikipedia.org/wiki/Snapdragon_(system_on_chip)
[3] android-dls.com/wiki/index.php?title=HOWTO%3a_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images
Click to expand...
Click to collapse
Not sure how to use these commands. It says that the phone needs to be rooted to use these.
I'm trying to install clockworkmod.
meanwhile, If you have time, plz provide a simplified tutorial.
The zergrush in http://forum.xda-developers.com/showthread.php?t=1296916 doesn't download btw

Sorry, yes, that needs root. You must do everything you can to get root on the phone, because whatever you do you must have a backup. For CWMR, you must back up your recovery partition, else if your CWMR image does not happen to be compatible with your device you risk losing recovery mode.
For MTK devices like the W10, there is a method for non-rooted phones to carry out the backup [1], but I'm not sure about Qualcomm. So in the end, root is unavoidable.
1. Just get zergrush binary from the SuperOneClick archive (it is in another folder along with psneuter).
2. Copy the zergrush binary to the ADB folder.
3. Open a cmd window in the ADB folder just as you would normally type adb commands, then:
Code:
adb push zergrush /data/local/tmp/
adb shell chmod 755 /data/local/tmp/zergrush
adb shell /data/local/tmp/zergrush
Report back with the output.
[1] bm-smartphone-reviews.blogspot.com/2012/04/creating-rom-dump-of-your-mt65x3-device.html

jason_cheng said:
1. Just get zergrush binary from the SuperOneClick archive (it is in another folder along with psneuter).
2. Copy the zergrush binary to the ADB folder.
3. Open a cmd window in the ADB folder just as you would normally type adb commands, then:
Code:
adb push zergrush /data/local/tmp/
adb shell chmod 755 /data/local/tmp/zergrush
adb shell /data/local/tmp/zergrush
Report back with the output.
Click to expand...
Click to collapse
Hellions with blue flames !
See The attached pic

I have the same phone It's original model is ktouch w650
i evem tried to use update.zip method but it says sd storage not found
how do i know if my bootloder is unlocked or locked
tried unlock root with driver installed it says failed to aquire root access\
in adb shell it shows $ sign and if i try to get root acess it says acess denied

Oh boy, it looks like the vulnerability has been patched in your version of Android. Either that, or there is some hardware peculiarity (buffer size being reported wrongly - that's also when this zergrush error comes up) which I do not yet know how to deal with. There is another exploit called 'tacoroot' but I do not prefer going that route as it's not as foolproof/universal as zergrush.
Update zips need to be signed. When your recovery tries to verify the signature it fails, as it is not the signature of the manufacturer that made the update.zip.
Have you guys tried ALL the rooting methods posted in the A5/A7 thread? In the meantime I'll take a look at how Qualcomm ROMs can be dumped.
edit: I'm pretty sure your device has a fastboot mode. If so, you can "hot" boot any cwmr image without flashing it using "fastboot boot theimage.img" as far as I can recall. Having fastboot is a blessing (which the MTK devices do not have) so follow the first few pages of the A7 thread.

thanks
thanks for your hard work....
can you tell me how to acess fastboot?
and also when i press and hold vlo up and power button its displayes" Ap fastboot:recovery " and screen becomes green and then if i keep pressing it goes red into recovery mood
but if i let go at green screen it stays that way
and when i pressed vol down+ power key it said im black screen and yello text " ENTRY QPST DOWNLOAD "

shaon121 said:
thanks for your hard work....
can you tell me how to acess fastboot?
and also when i press and hold vlo up and power button its displayes" Ap fastboot:recovery " and screen becomes green and then if i keep pressing it goes red into recovery mood
but if i let go at green screen it stays that way
and when i pressed vol down+ power key it said im black screen and yello text " ENTRY QPST DOWNLOAD "
Click to expand...
Click to collapse
Sorry, the W10 is my first ever experience with Android (I was looking for a cheap way to find out how the stuff works), and as it does not even have a bootloader mode I have no idea about fastboot. I have only been with this phone/Android for about a month, so there's still a lot more to learn.
But as far as I can tell "AP Fastboot" already implies that you are in fastboot mode. You need the fastboot drivers installed on your PC, and then when you are at the green screen the phone will accept fastboot commands. [1]
If you guys manage to do this, what I would suggest is hot-loading a Karbonn A7, Mobiistar S01 or any other potential compatible CWMR image, then immediately making a full ROM backup. You can then upload recovery.img and I'll see if I can port it, and after that boot.img so we can at least get you root adb shell if by then rooting is still a problem.
And btw, if it was not clear in my previous post, rooting using current "standard" methods is not going to work as the latest gingerbread vulnerability (which zergrush exploits and many of the tools use zergrush) has been patched since December 2011. Unfortunately, it looks like the build of 2.3.6 that the W25 has is from a period after that, so zergrush on the W25 is a no-go. If you want to try, just follow the adb steps above which was posted for ahmed.zunaid.
[1] http://www.androidcentral.com/how-i-back-my-stock-unrooted-galaxy-nexus

[GUIDE][All-In-One]LG Optimus Me P350

So, I decided to write this guide here as I couldn't find a complete one and had to jump from thread to thread (and sometimes even the sub-forum) for finding the answer.
First I wrote it in my blog and I decided to post it here. Maybe some steps are vague in details but I'm planning to detail it even more (remember, I wrote it in my personal blog first). So, here it is:
AIO LG Optimus Me P350 Guide​
Some Personal History
My experience with Android. UF! Where to start? So, I got my phone from the United States. You have no idea how wonderful it was to have the phone in my hands. Anxiety and curiosity. For some reason I always read that the first thing anyone does is root the phone and then continue doing everyday activities that do not require root, so I tried to live without rooting the phone, but I couldn’t wait for the week to go by. I had to get the best! Small problems, fixes and updates. And since I have my phone on sale, I publish this step by step guide to modify it and not die trying.
Tech Specs
Let’s start from the beginning, know the phone. Mid/low-range phone created by LG for those in a short budget but want to have a good Android experience. It has a 600 MHz processor, 256 MB RAM and ROM capacity of 512 (140 MB available for applications and data). 2.8 inch capacitive screen, 240 × 320 screen resolution. Wi-Fi b/g wireless connection, Bluetooth 2.1 with EDR, and USB 2.0 up to 480 Mbit/s. 3.1 MP camera (no flash) and FM Radio. Not bad for a basic device. Complete specifications can be found here. Enough for a casual user. But if you’re not a casual user (hence a XDA member), read on.
First of all, everything you do on the phone number is on your own. You yourself are responsible for what you do, not do, stop doing, fail, fail to read and/or shortcut you may have taken. These steps are the ones that worked for me. I am not responsible if the phone dies in the process, the cat bites the cable in the middle process, the heavens begins to fall, the 3rd world war starts or if the neighbor has a heart attack … You’ll be calling 911 afterwards… You’ve been warned!
USB Debugging
The first thing you have to learn is to turn on USB debugging. Here is a guide how to do it (If you wanna see a pictorial guide). But essentially you have to go to Settings > Application > Development and check where it says USB Debugging. Pretty easy. What is this good for? Well, for starters. modify the phone however we see fit. But most important USB Debugging allows the phone to communicate verbosely with PC with the Android SDK installed. More on this later.
KDZ Updater
KDZ Updater is an application used by LG for flashing official operating systems themselves. How did this application saw daylight outside the company, I don’t know very well, but apparently a leak appeared on LG India, but not sure. In any case, this application is our last line of salvation and the main tool for our little friend.
To install official KDZs must follow these steps:
Install the updated drivers by following the steps listed on this page.
Connect the phone with USB Debugging activated
IMPORTANT: Disable the Virtual USB Modem device from Windows Device Manager. Omit this step and the device may brick in the upgrade process.
Run the application in Administrator mode (only required on Windows Vista / 7).
In the Type drop-down list select 3GQCT and in PhoneMode, DIAG. Where it says Version, will appear the version that is installed on the phone.
Select the KDZ file to install by clicking on the button with the folder icon. Preferably save the file KDZ in the root of the hard drive as there will be little chance for error when reading the file.
Press the button “Launch Software Update”. The phone will reboot into Emergency Mode. This is normal.
Pray all you know and go for a cup of tea. The process takes about 8 to 10 minutes.
If all went well, the phone will turn off and the program displays a line that says = FINISHED =.
To start, first go into recovery mode by pressing the following buttons: Vol- & Power. This will make any old or unnecessary information to be removed. The phone will reboot into the system normally.
Original Thread
Root (Gingerbreak and SuperOneClick)
Ok, what we came here for. Rooting the phone. How do I do? It’s scary! Says who?! Lets start with the choices we have. Ok, we have the phone, but we have not updated anything, How do I get root? Gingerbreak comes on the scene. Pretty simple process: download, Enable USB Debugging, run, press Root, wait for the restart, confirm. Simple, right? Also read the instructions and warning on the link above in case something I overlooked, but that basically is the process. By the way, install Busybox, very important for future processes.
Stop, stop, stop … And if I upgraded the phone? Gingerbreak seems not to work! What do I do?! Mainly, DO NOT PANIC! First things first. Go to “About phone” and see that version it says; something different than 2.2? Cool, no problem. SuperOneClick comes on scene. Download the application, unzip. I assume you already installed the drivers, right? Otherwise, do it and come back when you have done so. Ready? Continue. Turn on USB Debugging and connect the phone to the computer. Execute the application and press the button that says “Root”. Need more information? Here is a video explaining step by step (its in spanish, but graphics needs no language) and if the antivirus gets all paranoid, read the explanation here.
Recovery (Amon-RA and CWM)
Ok, moving on. Just as clarification: From this step on, the phone should already be rooted. Otherwise, you will mourn at the very end because the phone will brick and you’ll end with a very good and expensive paperweight. What is a Recovery? Here the answer.
This is essential before changing the insides of the phone and a step that I believe needs to be forever linked to rooting process. Why? Simple! Installing a Recovery allows full system backup and restore if something goes wrong. That linking to rooting process? Because if you install a root application, modify the system, and damage the system, it can be restored to a previous time and we’re all happy campers. See?
So this is where we get our hands dirty. Initially, I ask again, have you installed the drivers? (From this point on I shouldn’t ask) Have you rooted the phone? Responded twice yes? Perfect. Now, download the Android SDK or only the .zip attached here (unzip preferably in C:\ADB\) to continue this process. Also download the Recovery that you will install, we have Amon-RA and ClockworkMod (CWM) v5, v5 touch, and v6, extract the recovery.img file to the folder where adb.exe is (If you used the SDK installer, should be at C:\Program Files\Android\android-sdk\platform-tools\; if you used the .zip, and extracted as recommended, C:\ADB\). Which to choose? My recommendation, CWM v5 (either one). Connect the phone to the computer in with USB Debugging activated. By the way, how do you feel using command line in Windows? Moving on…
Open a command window, go to where adb.exe is and run the following commands:
Code:
adb push recovery.img /sdcard/
adb push flash_image /sdcard/
With this we have copied what we need into the phone’s SD card. Just to clarify: 1) the flash_image file can only be found in the recovery Amon-RA zip (not sure if it is generic or modified exclusively for the P350, then I’d rather play it safe) and 2) CWM recovery v5 and v5 touch files come in zip-installable, but you can open the file and use recovery.img in it. In CWM v6 there is an installable zip and another to follow this same process. Lets continue…
Code:
adb shell
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# sync
Up to this we have only prepared the area to install the Recovery. It it recommended to reboot the phone in this step, in case you run out of virtual memory but is not really so necessary (If you see an error message, then reboot). That’s yours decision. Continue…
Code:
adb shell
$ su
# flash_image recovery /sdcard/recovery.img
# sync
To confirm that everything is installed without issues it must happen one thing and do another thing. What must happen is when you execute the flash_image command, no errors should appear, if otherwise reboot and repeat the last block of commands. What must be done is execute the command reboot recovery and if everything is alright, you should go into Recovery menu, if not then all the information has been erased and back to square 1 (it happened to me the first time).
Kernel
Just for safety: are drivers installed? Root acquired? Recovery installed? Already made a backup of the ROM in use at the moment (so far should be the LG ROM)? Do it!!
So, what’s a kernel? Here’s the answer. What choices do we have? Well not too many, it depends. Are we still on the LG Stock ROM or a Froyo-based ROM (oh, getting ahead aren’t we?!)? Well, the truth, with this ROMs there are not many: Team Pecan Kernel would be my recommendation, RoQ Kernel which also works quite well. CM7 ROM or any other Gingerbread-based? Ron's RM CAF Kernel (updated weekly), pax0r kernel (discontinued), Vivek Kernel (also discontinued but higher than pax0r). Read how to use Recovery for the installation of installable zip files from Recovery. This is also applicable for the installation of ROMs.
ROM
Still with me? Still no cardiac arrest? Relax, breathe! As we reach the last modification process of the phone. After surviving this, you will have the full capacity to recover the phone from any eventuality. Dictionary, which is a ROM? Here the answer.
ROM, What options do we have? Well, although it may seems, there are many options to choose from! We have some created from source code, based-on and others that have been “ported” to work with the device. Among those created from the source we have: CyanogenMod 7.2, Pure CM Invasion and CyanogenMod 9 (Work in Progress, not quite stable), based-on: Androm x4.2 (CM7) Arc XP (CM7), Gingerbread Optimus UI (CM7) Gingerblur (CM7) and MIUI v4 (based on CM7, Arc XP with a theme very close to the real MIUI, Japanese ROM). Ports: JoyOS, ICS (Discontinued unstable), BeautySense (Decent and functional).
Further Development/Tweaks
At the moment a new tool has been released called LG P350 Pecan Toolkit, developed by antdking. Its in early development and so far it roots, unroots and installs recovery. Saves some the hassle of the command line but if we haven’t gone through all the problems and commands, what have we learned? Anyways, here’s the original thread where you can follow the development and post ideas or bugs.
If you wanna go all-in into ROM cracking and research, we have also the LGExtract tool, which unpacks the KDZ file into bits and pieces. DZ Extract Tool extracts the files within a DZ package very much into source code. I've used these tools but as my experience with coding and android development is very close to none all I've done is extract the files and read them. Antdking reminded me of a simple yet powerful tool to continue decompiling the LG filesystem called unyaffsmbn. I came across it when we were trying to decompile baseband (amss.mbn) for CM9 without success, just lo later know that the tool just decompiled system.mbn. Oh well. Antdking compiled unyaffsmbn into a nice little tool ready to work, here it is.
The volume on this phone, as many may know, is low. But there is a way to elevate it. Execute the phone app and press: 3845#*350#. This will bring up a Hidden Menu. Go to: Device Test > Sound Test > Audio CAL Tool > Subsystem Calibration. In the Gain Type dropdown list, select Speaker Gain. Set Data textbox gets focus, input the number 90 and press OK button. In Gain Type, select Input1 Gain, and we press Ok button again. Exit the Hidden Menu. This will elevate the speaker volume but just temporary, it will be restored to default values when rebooted. So either don't reboot or repeat this process everytime you reboot.
And that would be all. Happy hacking!
Great kudos to the real developers here:
drapalyuk: For the first ever recovery for P350, Amon-RA
pax0r: Started it all, Kernel, ROM
ron gokhle: ROMs, Kernel and Recovery builds
vivekkalady: Kernel, Touch Recovery, first ICS port, and some other fix work
nikhil4186: For the KDZ Guide (although written originally for LG P500
antdking: For a great-to-be toolkit

great guide good job

Nicely written.Its a really good guide for all those who are new to P-350 and I believe that it will help them to learn some of the basic stuff.Well done!

to go on the end of this guide, how to extract the files out of the system.mbn to get the system files
http://db.tt/7VruqEzr
it returns similar files to what you find in a rom
I did not make unyaffsmbn
I made the tool that uses unyaffsmbn
enjoy

antdking said:
to go on the end of this guide, how to extract the files out of the system.mbn to get the system files
http://db.tt/7VruqEzr
it returns similar files to what you find in a rom
I did not make unyaffsmbn
I made the tool that uses unyaffsmbn
enjoy
Click to expand...
Click to collapse
got the PM and you reminded me of that tool (I remembder I came across it when we were trying to crack amss.mbn for CM9)... I'll post the original thread and the tool you just mentioned...

Updated adding unyaffsmbn tool... Thanks antdking!

Added Volume tweak for speaker to sound harder.

Added P350 (and guide) to XDA wiki. http://forum.xda-developers.com/wiki/LG_Optimus_Me

dbarrera said:
Added P350 (and guide) to XDA wiki. http://forum.xda-developers.com/wiki/LG_Optimus_Me
Click to expand...
Click to collapse
thanks man :good::good::good::good::good::good::good::good:

Guys We have got Official Support From XDA Please Move This Thread To Our Device Section

Very good!!!
I placed some problem I am having, just in case you have time an patience for this case.
Tks
http://forum.xda-developers.com/showthread.php?t=2461183

Great Guide Man! Thanks a lot.

Root Telstra T-Hub 2 (Technicolor)

Wanting to root my new Telstra T-Hub 2, made by Technicolor.
There appears to be no USB drivers available (nothing via Google)
There also appears to be no way to get into the Download Mode for connection to Odin. (again nothing on Google)
So these two points have left me a bit lost.
It is running Android (GB) 2.3.7
Any one have any ideas????

Rabs_1976 said:
Wanting to root my new Telstra T-Hub 2, made by Technicolor.
There appears to be no USB drivers available (nothing via Google)
There also appears to be no way to get into the Download Mode for connection to Odin. (again nothing on Google)
So these two points have left me a bit lost.
It is running Android (GB) 2.3.7
Any one have any ideas????
Click to expand...
Click to collapse
I got ADB working on my T-Hub 2 by using the generic Google drivers, and edited the adb_usb.ini to just say 0x069B
So far I have problems rooting it.

wocko1 said:
I got ADB working on my T-Hub 2 by using the generic Google drivers, and edited the adb_usb.ini to just say 0x069B
So far I have problems rooting it.
Click to expand...
Click to collapse
BUMP

I have this Tablet as-well and having the same problem.
any ideas on the best way to root this thing?
wocko1 do you have any more details on how to got that far?
Thanks guys.
Rabs_1976 said:
Wanting to root my new Telstra T-Hub 2, made by Technicolor.
There appears to be no USB drivers available (nothing via Google)
There also appears to be no way to get into the Download Mode for connection to Odin. (again nothing on Google)
So these two points have left me a bit lost.
It is running Android (GB) 2.3.7
Any one have any ideas????
Click to expand...
Click to collapse

was it released in any other countries as another device?
even if we got root on it what can we do for a custom ROM if noone can dev for it

Madaz2 said:
was it released in any other countries as another device?
even if we got root on it what can we do for a custom ROM if noone can dev for it
Click to expand...
Click to collapse
We as owners/users of T-Hub 2 devices require sensible answers to important questions.
We need usb drivers for the T-Hub 2, either from Telstra or from Technicolor the manufacturer of the device so that we can attain " ROOT ACCESS" via a usb cable connection to a computer.
Unless we can get "ROOT ACCESS" we cannot move applications to an external SD card (32 GB in my case) or use Titanium Backup or certain Antivirus programs that require "ROOT ACCESS".
Please accept the undeniable fact that 1 Gigabyte of storage on the internal SD card is totally insufficient and pathetic, almost as pathetic as the fact that we are still stuck with "Gingerbread" which puts us three versions behind on Android which is now up to "JellyBean" v2.
The fact is, I believe the Android operating system running on the T-Hub 2 is, like all other versions of Android, based on the Linux kernel which is software using the GNU General Public License, which allows people to see, copy, use, and modify for their own needs.
If indeed I am correct in my assumption then Telstra/Technicolor could be in breach of a world standard which would mean that the proprietary blocks and gates that they have built to prevent access to the kernel on the T-Hub 2 are illegal.

Download Mode discovered...and more...
I thought this:
Hold "Volume-" and "Volume+" and "Power Button" boots into download mode. This is incorrect.
This gets you to recovery mode (which shows the Android robot fallen over).

Help!
wocko1 said:
I got ADB working on my T-Hub 2 by using the generic Google drivers, and edited the adb_usb.ini to just say 0x069B
So far I have problems rooting it.
Click to expand...
Click to collapse
Have been looking for the drivers everywhere, and so far none of them have worked. Even tried wireless adb to no avail. Also tried gingerbreak but still nothing. Sick of looking at the bloatware. Someone please help!

anyone had more success now that it has ICS 4.0.4

Yes, it can be rooted, but...
Hi,
Yes, much more progress. I've gained ADB root access using the restore method (i.e., restoring a backup which has been modified to install a file to a strange path, e.g,: ../../../system/bin/su), I recommend creating your own restore file rather than using one of the many out there and using it to install the necessary SU software to the appropriate locations.
If your device isn't detected by ADB, check that the device ID has been added to the ADB config file. The Thub2 ID is not recognised automatically. Also, when using fastboot remember to specify this ID or it won't find your THub.
The biggest issue with the THub2 is that Telstra have (in an oddly intelligent move) adopted SquashFS for the root file system; this is the FS used on things like linux liveCD's, and it's 100% RO (well, 99% RO . I have gotten around this in a number of ways. 1: I copied the SquashFS partition using DD to an Ext4 partition, then forced a dirty unmount of the SquashFS partiition chained to a mount of the new Ext4 partition to /system. RW access no problems, SU installs OK, but no persistence without forcing the dirty unmount each boot. 2: I copied the SquashFS partition to my ~ using DD, mounted and edited the partition, then re-flashed to the thub. worked much better, persistence across reboots, but dangerous and dodgy method that could risk many NANDs. 3: I cross-compiled a busybox containing UnionFS to Android.
Option 3 is by far the best option. UnionFS provides a transperent RW layer for SquashFS filesystems, writing the updates that couldn't be written to a RO system like squash to another partition (e.g., Ext4 on SD card). Mount a UnionFS system over /system to enable write access to the system. Maybe a better idea to mount it at /, but that raises other problems I couldn't be bothered dealing with.
I mentioned above that SquashFS is on 99% RO (in all my other experiences, it has been well and truly 100% RO, so this indicates something else a-going on that we should be able to use; I haven't looked into it yet.). For some reason, files installed to the Thub2 using the Restore method are persistent. Very useful, and should lead to a cleaner method.
So rooting so far:
Root with Restore method to install (1 & 2., SU bins, or 3., UnionFS Busybox)
Remount / as RW
-->Path 1 & 2
Dirty unmount /system && dirty unmount /system2 && mount /dev/block/etc.. NOTE: Once you dirty unmount /system, you will need to reference the location of the Ext4 partiition using the absolute (real) name of the device. You will also need to invoke busybox from a fully qualified path, eg. /data/local/tmp/busybox, as the internal /bin applications are no longer available (eg., mount).​
-->Path 3
No need to umount /system, just mount the UnionFS system over the top.​
Finally, for Paths 1 & 3...
Install Superuser application and be free!​
So to sum up; I have easily rooted the Thub2 to root over ADB using a number of methods, however the Restore method works 100% of the time. I have mounted an Ext4 system to /system in order to have RW, but this isn't persistent. I have re-flashed the SquashFS with modified content, and this works a treat, but is RO and dangerous to NAND. I have mounted a UnionFS system over the SquashFS system, and this seems to provide the best all round performance.
I also wrote a short and nasty .apk to mount the UFS system without terminal, so that's a go as well.
Have fun pulling it all apart; I don't read these message boards, so I probably won't se any questions. More than enough to get rooted though.

THub Drivers and ADB Access
THUB 2 DRIVER INSTALLATION AND ADB ACCESS
This method sets out how to install drivers for the THub 2 and access ADB (Android Debug Bridge).
Access to ADB is the usual way that you use to Root an Android device.
Please note that not all ADB versions work. If you download and try a root method, you may have to copy the ADB.exe and support files across so that the root method can at least have a chance of working.
INSTALLING GOOGLE UNIVERSAL ANDROID DRIVERS
1. Ensure that Debugging has been enabled – Settings  Developer options  USB debugging and make sure the box is checked
2. The following is for Windows 7, other versions will be similar
3. Unzip the file and copy contents to a folder on the C: drive. I copied it to a folder I named THub
4. Plug the THub into your PC and it will try to find suitable drivers – some drivers may load and install but at least one will come up with “No driver found”
5. Open “Computer”
6. Click on “System properties”
7. Click on “Device Manager”
8. Under “Other devices” you will see T-Hub2 with an icon with a yellow exclamation mark.
9. Right-click the device and select "Update Driver"
10. Select "Browse my computer for driver software"
11. Select "Let me pick from a list of device drivers"
12. Click “Show All Devices”
13. Click “Have disk …”
14. Browse to where you put the extracted files
15. Select and open “Android_winusb.inf”
16. Select “Android Composite ADB Interface”
17. Click “Next” and then Click “Yes” (Ignore warning)
18. Wait until the software installs
19. You should now have Android Composite Interface” under the “Android Phone” listing
If you have problems, ensure Debugging is selected and try unplugging the THub and reconnecting it
ACCESSING ADB
1. Ensure that Debugging has been enabled – Settings  Developer options  USB debugging and make sure the box is checked
2. The following is for Windows 7, other versions will be similar, It also assumes that the file has been down loaded, unzipped and installed in a folder called THub on you C: drive
3. Connect the THub to your PC
4. Click in the “Start” icon, lower left icon on your PC Desktop
5. In the entry box type in “CMD” and push “Enter”
6. You will be at the “Command Prompt”
7. You need to navigate to the “THub” folder, the following are my entries, and yours should be similar.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Terry>cd .. and “Enter”
C:\Users>cd .. and “Enter”
C:\>
C:\>cd THub and “Enter”
C:\THub>
8. At the THub folder type in “ADB devices” and “Enter”
9. You should get an output similar to this:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
01545CAB0B015004 device
C:\THub>
10. You now have ADB access
11. Try “adb shell” and “Enter” to enter ADB and then “ls” and “Enter” to get the THub Root folder listing
What next, I don’t know but at least we have ADB access?
I have been trying to copy system files to my SD card to have a look at them but have no success.
Does anyone know how?
Here is the site I uploaded the files to:
"You can fill in the missing bits"
xxx.mediafire.com/download/voku3wnuff5s2ef/THub.zip
NOTE: There is also a file called “UniversalAdbDriverSetup6.msi”.
I don’t know what it is for, but I installed it anyway. It MAY be necessary for the above method.

Firstly, I understand this is an old thread but quite a lot of us Australians have this THub 2 now because Telstra seem to basically be handing them out like shots at a party.
As far as I know this thing still has no root access. You can get into ADB with it without too much trouble.
But what I really want to know is how I can get root access with SuperSU so I can install something like AdAway to remove the seemingly ridiculous amount of advertisements that apps and etc. come with.
In addition to that, after installing just TWO small apps. It seems the device's internal memory is already full and it cannot install any more apps.. I need root access in order to run Apps2SD so I can move some apps to the SD card that I have purchased for it.
Does anyone, and I mean anyone have any ideas about how to root this thing? There has to be some Australian who has a rooted version with SuperSU running.
I tried 'towelroot' but the device just rebooted (meaning it failed) and then when I ran the .apk again it said that the device was unsupported.
It's one thing to be able to get access to the root partition (which is possible over ADB) but it's another to be able to run apps with root privileges.
For any information.
The specs are:
Manufacturer - Technicolor
Operating System - Ice Cream Sandwich 4.0.4
Processor - 1 GHz dual core
Screen - 7″ (1024 x 600 pixels)
Camera - 1.9 MP rear camera, 1.2 MP HD front camera
RAM - 1GB
Storage - 2 GB Internal with an expandable Micro SD card slot (1GB internal usable)
Battery - 6000 mAh (non-removable)
I know it's nothing amazing, but if I could root the device and change the DPI, remove advertisements and install a few hacks. I'd get so much more out of the device.
I picked it up in almost perfect condition second-hand off eBay for only $15. They're worth $360 AU brand-new.
If anyone has any information at all, please do post something. My apologies again for bumping a super old thread but otherwise I was going to just start my own.

Possible to restore system partition
Hi Guys,
I done goofed.
I killed my T-Hub by flashing a corrupted system partition and now the device wont boot and only displays the Telstra logo at the boot loader. I do have a backup of my system partition however I cant work out how I would perform the restore. The boot loader will not allow an ADB connection so no luck there.
Im thinking JTAG may be my only option. I have experience with this on other devices but i cant find the JTAG terminals on this thing? I must have tapped about 60 different combinations of testpoints now and have only been able to get console out of the radio module which is obviously no good for talking to the kernel.
Any help would be greatly appreciated.
Cheers,
Swamp

SwampCrack1210 said:
Hi Guys,
I done goofed.
I killed my T-Hub by flashing a corrupted system partition and now the device wont boot and only displays the Telstra logo at the boot loader. I do have a backup of my system partition however I cant work out how I would perform the restore. The boot loader will not allow an ADB connection so no luck there.
Im thinking JTAG may be my only option. I have experience with this on other devices but i cant find the JTAG terminals on this thing? I must have tapped about 60 different combinations of testpoints now and have only been able to get console out of the radio module which is obviously no good for talking to the kernel.
Any help would be greatly appreciated.
Cheers,
Swamp
Click to expand...
Click to collapse
I'm completely new to this. What ROM would i look for to install on the THUB if any? And if i could install it?

clearburn said:
I'm completely new to this. What ROM would i look for to install on the THUB if any? And if i could install it?
Click to expand...
Click to collapse
sorry but no one has developed a ROM for this device, there is no demand

Madaz2 said:
sorry but no one has developed a ROM for this device, there is no demand
Click to expand...
Click to collapse
Thanks. I thought there might have been a rom from the basic device that didn't have all of the Telstra stuff on it.
It is currently a brick

if you can root it then you could install Titanium backup and uninstall the bloatware off of it

Some moderate success
I have had some moderate advancements of late.
I can get temporary ADB root using the directory traversal exploit
.
While the above method gets you a root terminal session, as it screws with some settings the device is nearly unusable due to screen flicker and general lag. I guess the exploit breaks some settings. Does anyone know how to leave the exploit in place and restore the settings file to eliminate the flickering and lag?
I have been able to export the system partition, edit it (add su.bin and SuperUser.apk) then swap the system mount so the device uses my edited system partition as described by malleus. When I try to flash my partition the device reboots and is in a semi brick state (reboot loop, stuck on boot loader Telstra logo).
I was able to obtain the OTA update files by getting an old 2.3.7 device, rooting it then grabbing the OTA files using ADB once it had downloaded them. These OTA's can be flashed from an SD card (ext4 format) in 3e recovery. This was a good bit of progress as it means I can restore from a bricked state. If anyone needs them, the files I have are:
Product_4.0.4_3.38-FOTA
Product_4.0.4_3.48-FOTA
This is all new territory for me but i think I am getting close to achieving full, persistent root in 4.0.4.
Any help would be appreciated.

I would be very interested in your progress as I have one of these but in default state it is only usable as a phone on the DECT base.....
Having some useful apps running off an SD card would help no end (like multimedia remote for my home theatre system)
Cheers,
Alex B
SwampCrack1210 said:
I have had some moderate advancements of late.
I can get temporary ADB root using the directory traversal exploit
.
While the above method gets you a root terminal session, as it screws with some settings the device is nearly unusable due to screen flicker and general lag. I guess the exploit breaks some settings. Does anyone know how to leave the exploit in place and restore the settings file to eliminate the flickering and lag?
I have been able to export the system partition, edit it (add su.bin and SuperUser.apk) then swap the system mount so the device uses my edited system partition as described by malleus. When I try to flash my partition the device reboots and is in a semi brick state (reboot loop, stuck on boot loader Telstra logo).
I was able to obtain the OTA update files by getting an old 2.3.7 device, rooting it then grabbing the OTA files using ADB once it had downloaded them. These OTA's can be flashed from an SD card (ext4 format) in 3e recovery. This was a good bit of progress as it means I can restore from a bricked state. If anyone needs them, the files I have are:
Product_4.0.4_3.38-FOTA
Product_4.0.4_3.48-FOTA
This is all new territory for me but i think I am getting close to achieving full, persistent root in 4.0.4.
Any help would be appreciated.
Click to expand...
Click to collapse

Has anyone made any progress on this?
I have two of these tablets that have sat unused since I got them from Telstra. I really just want to update it to at least 4.1, but there's no official release from Telstra for the T-Hub, and I don't think there will be. Are ports entirely unfeasible?
Do you think I could contact Technicolor? What should I say?
P.S. there is a recovery mode, because I've booted into it.
hxxp://imgur.com/O0uq4Uk

[DEV][WIP] xubuntu on tf300tg 0.1.2 (updated 130408)

*** ABOUT ***
This is an attempt to build a completely clean installation of xubuntu for the tf300tg (and probably tf300t). Most notably it does not reuse the ac100 ubuntu package.
I also want it to be as completely documented as possible starting from an official ubuntu repository and kernel source, until everything is working. Which does not mean it is for a complete beginner to reproduce...
It's not (yet) packaged : you at least need to be able to install a blob for the kernel, and a rootfs to a dedicated partition.
It's also not yet as cleaned up and documented as I would for the kernel side of things.
Everything is done on device on (and for) a tf300tg but as been reported to work on tf300t.
Most of the hard work was done by others. I mostly started from rabit's tf700 ubuntu, and added some insight from cb22 work on arch to get something working.
*** STATUS ***
What works :
- it boots into a clean xubuntu dm/desktop, with wifi (improved), 3g
- it also boots into android (stock, didn't try cm)
- 3g also works under android (new)
- touchpad / touchscreen
- 3d acceleration (version 16.3 of nvidia drivers)
- cpu and gpu overclock (respectively to 1,5 GHz and 446 MHz)
What I know doesn't work, isn't there yet :
- sound
- bluetooth
- some key remapping (esc, alt, ...)
Many other things I didn't check (sensors ?).
*** HOWTO install ***
0. of course you can break many things doing that ; you should have access to nvflash (never had to use it though) and with a recovery installed (I'm on twrp 2.4.3.0)
1. unpack xubuntu_tf300tg_rootfs-0.1.2.img.lzma to the internal storage and move / rename to linux/rootfs.img (/data/media/linux/rootfs.img)
1bis. you can change your keyboard layout in /etc/default/keyboard (replace "us" by whatever is your locale)
2. install the kernel blob using fastboot or "dd if=xubuntu_tf300tg_kernel-0.1.2oc.blob of=/dev/block/mmcblk0p4"
You should be able to reboot into xubunfu (or android).
3. log in as guest, from "user and groups" in the "settings manager", add one user, set password, change account type to administrator, add to sudo group (root password wil be asked : root)
4. logout, then login into your newly created user
5. open "language support" from the settings manager, and when it says missing locales, either choose install if you want "en" or "ask me later" if you want something else (in which case you can chose to install your own language, and configure them on the "regional format" page ; don't forget to apply system wide on both pages
6. change root password
Your second reboot should be more satisfying
*** HOWTO improve ***
1. find out what does not work and tell in the thread
2. understand what is documented bellow and propose correction / evolutions in the thread
3. don't hope for frequent updates : I do that alongside a more than full time job and tending to a two years old child. Still I will update.
*** DOWNLOAD ***
rootfs : http://d-h.st/vYf
kernel : http://d-h.st/UAy
misc config files : http://d-h.st/TEZ
nvidia drivers : http://d-h.st/pwQ
md5sum :
4f572c110c3f06f54699c826fed692f4 src-0.1.2.tar.lzma
249826271f4fadff4352217467e4ed2e xubuntu_tf300tg_kernel-0.1.2oc.blob
3263de707c2586d1e2177367f067361a xubuntu_tf300tg_rootfs-0.1.2.img.lzma
cf20b01281be3ef4b6d4631ae5cea67b R16.3.tar.lzma

*** HOW is it done / rootfs ***
I did it from ubuntu (rabits') on my tf300tg. Should be doable from another platform. Definitly doable from self.
As root.
# unset languages / locales
export LANG=C
unset LC_ADDRESS
unset LC_IDENTIFICATION
unset LC_MEASUREMENT
unset LC_MONETARY
unset LC_NAME
unset LC_NUMERIC
unset LC_PAPER
unset LC_TELEPHONE
unset LC_TIME
# mount a cleanly ext4 formated partition (futur root partition)
mount /dev/mmcblk1p2 /media/p1
# install initial minimal system
apt-get install debootstrap
debootstrap quantal /media/p1 http://ports.ubuntu.com/
# prepare to chroot
mv /media/p1/etc/apt/sources.list /media/p1/etc/apt/sources.list.orig
cp src/sources.list /media/p1/etc/apt/sources.list
mv /media/p1/etc/fstab /media/p1/etc/fstab.orig
cp src/fstab_chroot /media/p1/etc/fstab
mkdir /media/p1/run/user
# chroot into the new system and mount all special filesystems
chroot /media/p1
mount -a
# download xubuntu (avoiding unity which is recommended by lightdm)
apt-get update
apt-get upgrade
apt-get install xserver-xorg
apt-get --no-install-recommends install lightdm
apt-get install lightdm-gtk-greeter
apt-get install xubuntu-desktop
# install nvidia drivers and tuned nv.conf
tar xf R16.3.tar
update-alternatives --force \
--install /etc/ld.so.conf.d/arm-linux-gnueabihf_EGL.conf arm-linux-gnueabihf_egl_conf /usr/lib/nvidia-tegra/ld.so.conf 9000 \
--slave /usr/lib/xorg/modules/drivers/tegra_drv.so nvidia_drv /usr/lib/nvidia-tegra/xorg/modules/drivers/tegra_drv.abi13.so
ldconfig -v
update-rc.d ondemand disable
# change root password to something of your chosing and exit chroot
passwd root
# configure touchscreen and touchpad
apt-get install xserver-xorg-input-multitouch
exit
cp src/mtev.so /media/p1/usr/lib/xorg/modules/input
mkdir /media/p1/etc/X11/xorg.conf.d
cp src/50-elan* /media/p1/etc/X11/xorg.conf.d
# change hostname
# edit /media/p1/etc/hostname and replace tf300tg with your chosen hostname
# edit /media/p1/etc/hosts and insert a line (second one) with "127.0.0.1 yourhostname"
# hide the partitions from mmcblk0 (thanks cb22)
echo 'ENV{ID_PATH}=="platform-sdhci-tegra.3", ENV{UDISKS_IGNORE}="1"' > /media/p1/etc/udev/rules.d/80-hide_tf300tg_partitions.rules
# change keyboard defaults
# edit /media/p1/etc/default/keyboard ; replace "pc105" by "asus_laptop" ; you can also change "us" to your locale
# create mountpoints for system and data
mkdir /media/p1/system /media/p1/data
# configure for loading wifi module
echo bcm4329 >> /media/p1/etc/modules
#
cp /media/p1/etc/fstab.orig /media/p1/etc/fstab
*** HOW is it done / kernel ***
The kernel source is default asus 10.4.3.9 from asus' website download section. Patched to add cpu overclock from faux's kernel and gpu overclock from motley's kernel (diff file in src.tar.lzma).
Initial kernel config file is taken from stock 10.4.3.9 android, with options added to support ubuntu and oc. path to the nvram for bcm4329 modified.
Ramdisk is mostly that from rabbits 0.8.0, with some modificaitons to enable modem support under android.
*** Todo ****
- modify config / kernel to use nvidia's R16.3 tool to patch wifi ;
- build initramfs anew from tf300t/tg stock android initramfs (currently rabbits modified tf700) ;
- bluetooth and sound ;
- key remapping.

reserved 2

Sounds promising! Keep it up, hopefully other devs see this and help you out :good:

Re: [DEV][WIP] xubuntu on tf300tg 0.1.0
Good job, I will tray luck to night when I back from work.
P.S. I heave no dock - that means no keabord and mouse
Sent from my GT-I9100 using xda app-developers app

Keshukas said:
Good job, I will tray luck to night when I back from work.
P.S. I heave no dock - that means no keabord and mouse
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your interest.
Although I would be happy to have some feedback, it may be a bit early if you don't have a dock : it's completely functionnal with a dock and mouse (I've been using it for work - and build - for a few days), without a keyboard and mouse, you will not go farther than xubuntu' login screen.
Anyway if you still wan't to try it, tell me if you reach xubuntu blue login screen.

Re: [DEV][WIP] xubuntu on tf300tg 0.1.0
On the rabbit Ubuntu for tf700 are virtual keabord (beside clock switch ) witch I use to login to Ubuntu
Sent from my GT-I9100 using xda app-developers app

Assuming this is a dual boot kernel, how does the kernel know where ubuntu is installed if not installed on internal sdcard? Also what's the minimum size partition that can be used?

Moved the thread for ya...

Yes!!! ) Thanks I wait for it )) Xubuntu is my lovely linux, I have it on PC, Notebook, installed on fathers PC and now for tablet!! :good::good::good:

Keshukas said:
On the rabbit Ubuntu for tf700 are virtual keabord (beside clock switch ) witch I use to login to Ubuntu
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I know that and it can be reproduced (look at rabits' /etc/X11/xorg.conf ; and needs packages xserver-xorg-input-multitouch and mtev).
But I have not yet abandonned all hope of doing it the ubuntu way (ie. with evdev).
TechyNut said:
Assuming this is a dual boot kernel, how does the kernel know where ubuntu is installed if not installed on internal sdcard? Also what's the minimum size partition that can be used?
Click to expand...
Click to collapse
Rabits modified the boot image so that it checks /dev/sda*, then /dev/mmcblk1p*, then an img file on /dev/mmcblk0p8. The first which looks to be an ubuntu partition is used as root. He also activated vt (having a console during boot) in is kernel configuration. I reproduced both.
NRGZ28 said:
Moved the thread for ya...
Click to expand...
Click to collapse
Thanks. Induced some noise on other threads

Ramdisk initrd.img in your kernel blob file is not a gzip !!!

Ok starting test
1. Yours kernel most start android if no Linux in /dev/sda1 or /dev/mmcblk1p* or on /dev/mmcblk0p8. Some I understand ?
Now making backup of me tablet ( TF300t ) and flashing kernel to test it.
2. I planing Make Linux on me ExtSDcard (MiniSD 8 gb) and plug sdcard in tablet and then reboot tablet. i hope to start Xubuntu

akurpiel said:
Ramdisk initrd.img in your kernel blob file is not a gzip !!!
Click to expand...
Click to collapse
No. It's lzma.
You can check rabits' git for details : https://github.com/rabits/tf700
Keshukas said:
Ok starting test
...
i hope to start Xubuntu
Click to expand...
Click to collapse
I hope too. Thanks for testing.

Can't mount linux
So I thought I'd give this a try. These are the steps I took to install this:
1. Formated 8gig SD card as ext4
2. Extracted rootfs to SD card.
3. Inserted SD in base
4. copy /system/vendor and /system/etc from your tf into /system on that partition ; copy /data/misc from your tf into /data on that partition
5. fastboot -i 0x0b05 flash staging xubuntu_tf300tg_kernel-0.1.0.blob
6. reboot
6. Kernel boots prompting option, select 1 (linux) and fails to mount partition and boots into android with no other problem.
What am I missing?

ColMustard said:
So I thought I'd give this a try. These are the steps I took to install this:
1. Formated 8gig SD card as ext4
2. Extracted rootfs to SD card.
3. Inserted SD in base
4. copy /system/vendor and /system/etc from your tf into /system on that partition ; copy /data/misc from your tf into /data on that partition
5. fastboot -i 0x0b05 flash staging xubuntu_tf300tg_kernel-0.1.0.blob
6. reboot
6. Kernel boots prompting option, select 1 (linux) and fails to mount partition and boots into android with no other problem.
What am I missing?
Click to expand...
Click to collapse
I have had some occurences of hitting return to fast at the prompt and init not detecting correctly the SD card. So maybe let it timeout into trying to boot linux.
If that does not work, you can choose "s" at the prompt, then from there check into /dev/ which disks / partitions are recognized. Provided that your linux partition is the first and only one on the SD card, you should have a /dev/sda and /dev/sda1. What do you see ?
Also remove any usb drive, which could appear as /dev/sda (and make the sd card appear as /dev/sdb).

Some RABIT write "In-device microSD really bad works." :crying:
I heave problems to boot from sd now i think extract xubuntu in /data/media/linux/rootfs.img
-- Update --
MicroSD - /dev/block/mmcblk1p1

schrdlu said:
I have had some occurences of hitting return to fast at the prompt and init not detecting correctly the SD card. So maybe let it timeout into trying to boot linux.
If that does not work, you can choose "s" at the prompt, then from there check into /dev/ which disks / partitions are recognized. Provided that your linux partition is the first and only one on the SD card, you should have a /dev/sda and /dev/sda1. What do you see ?
Also remove any usb drive, which could appear as /dev/sda (and make the sd card appear as /dev/sdb).
Click to expand...
Click to collapse
Well it looks like it's a no go for me. it could be that I used Minitool Partition Wizard to format because I could not get to my linux machine at the time.
I also tried flashing the kernel over 3 different ROM:
1. CROMI 3.4.4 - Keep failing with Encryption error after boot animation prompting me to reset the device.
2. Hydro 7 - Keep failing with Encryption error after boot animation prompting me to reset the device.
3. CM 10.1 - Failed to get pass boot animation.
I'll have to re-flash Asus stock ROM (10.4.2.20) in order to fully test this, I might have to reformat the sd on linux also.

ColMustard said:
Well it looks like it's a no go for me. it could be that I used Minitool Partition Wizard to format because I could not get to my linux machine at the time.
I also tried flashing the kernel over 3 different ROM:
1. CROMI 3.4.4 - Keep failing with Encryption error after boot animation prompting me to reset the device.
2. Hydro 7 - Keep failing with Encryption error after boot animation prompting me to reset the device.
3. CM 10.1 - Failed to get pass boot animation.
I'll have to re-flash Asus stock ROM (10.4.2.20) in order to fully test this, I might have to reformat the sd on linux also.
Click to expand...
Click to collapse
Me to. I can't boot to android at all
I still tray boot to xubuntu with this kernel and I make img on the internal card

Keshukas said:
Me to. I can't boot to android at all
I still tray boot to xubuntu with this kernel and I make img on the internal card
Click to expand...
Click to collapse
Yeah, I did notice that the kernel looks for the /data/media/linux/.img for a last effort. I was thinking on doing the same.