Hi there,
Just got the new mini pro (SK17i) and I've tried SuperOneClick root and Gingerbreak to no avail =( Since the device is pretty new I understand it may just not work, but to those who have gotten it to work, could you give me a walkthrough of what drivers you've downloaded?
A related question: does anyone know how to boot into recovery? I've tried a number of button combinations but with no success. I figure this might help with SOC, or it may not, but thought I'd give it a shot.
And finally, not sure if it's warranted yet, but it'd be awesome if we could get a separate SK17i forum going, so as not to confuse with the X10 mini pro.
A lot to ask in one post, I know, but greatly appreciated!
looloopoopie said:
Hi there,
Just got the new mini pro (SK17i) and I've tried SuperOneClick root and Gingerbreak to no avail =( Since the device is pretty new I understand it may just not work, but to those who have gotten it to work, could you give me a walkthrough of what drivers you've downloaded?
A related question: does anyone know how to boot into recovery? I've tried a number of button combinations but with no success. I figure this might help with SOC, or it may not, but thought I'd give it a shot.
And finally, not sure if it's warranted yet, but it'd be awesome if we could get a separate SK17i forum going, so as not to confuse with the X10 mini pro.
A lot to ask in one post, I know, but greatly appreciated!
Click to expand...
Click to collapse
I can't help you ATM, but I'm agree with you when you said they should create a new forum specially for the new mini pro.
And I've a question, is it smooth, fast, and stable with SE firmware ? Is there any lag issue when you play 3D games ? Because I will buy it soon. Thx.
FrenchKoR said:
I can't help you ATM, but I'm agree with you when you said they should create a new forum specially for the new mini pro.
And I've a question, is it smooth, fast, and stable with SE firmware ? Is there any lag issue when you play 3D games ? Because I will buy it soon. Thx.
Click to expand...
Click to collapse
It's actually quite nice and stable, despite some of the extra stuff loaded in stock. I haven't stressed it too much with various games, but it does run very smoothly. Quadrant scores - if they matter much - hover around 1750.
looloopoopie said:
It's actually quite nice and stable, despite some of the extra stuff loaded in stock. I haven't stressed it too much with various games, but it does run very smoothly. Quadrant scores - if they matter much - hover around 1750.
Click to expand...
Click to collapse
Thanks a lot for your reply, I'm very exciting about this future acquisition.
I think superuser.apk will be fixed soon to work with new mini pro.
FrenchKoR said:
Thanks a lot for your reply, I'm very exciting about this future acquisition.
I think superuser.apk will be fixed soon to work with new mini pro.
Click to expand...
Click to collapse
No problem, and thanks for the input on SU! I seriously can't wait for root >.<
Hye just wait since the device is new there has to pass some time before the make a subforum about it
So just wait!
Sent from my mini pro using CyaNoComb 1.3
I found a few article maybe can use here, its origin a japanesse but i input them on google translate
http://translate.google.com/transla...=en&u=http://ruotal.sakura.ne.jp/blog/?p=2743
http://translate.google.com/transla...=en&u=http://ruotal.sakura.ne.jp/blog/?p=2743
http://translate.google.com/transla...p://d.hatena.ne.jp/ssknot/20110802/1312279146
http://unlockbootloader.sonyericsson.com/which-phones
English infromation is here.
wikiwiki.jp/knot/?SK17i-en
Hmm.. i tried it many time but always failed when try to edit system.img
Really annoying, can someone help please?
http://www.mediafire.com/?7tbf9f4ctcar26j
Here the dump rom for edit the system.img to gain root
Im stuck on progress, maybe someone can help?
(Important!!) Before unlock bootloader, initialize your mini pro with SEUS (Sony Ericsson Update Service) to download the official ROM image into your PC.
http://www.sonyericsson.co.jp/support/software/updateservice/
See Sony Ericsson bootloader unlock official site. Follow the instruction page, except No.8 and 10. See below regarding No.8 and 10.
http://unlockbootloader.sonyericsson.com/
http://unlockbootloader.sonyericsson.com/instructions
No.8 does not work. If you have the latest USB driver (which version is 12/06/2010,4.0.0000.00000 or newer) in your Android SDK folder, just add below description in the android_winusb.inf.
[Google.NTx86]
; SonyEricsson
%SingleAdbInterface% = USB_Install, USB\VID_0FCE&PID_0DDE
%CompositeAdbInterface% = USB_Install, USB\VID_0FCE&PID_0DDE&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0FCE&PID_0DDE
for 64 bit Windows
[Google.NTamd64]
; SonyEricsson
%SingleAdbInterface% = USB_Install, USB\VID_0FCE&PID_0DDE
%CompositeAdbInterface% = USB_Install, USB\VID_0FCE&PID_0DDE&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0FCE&PID_0DDE
No.10 - To enter fastboot mode, turn off the phone, hold [Vol Up] button, then connect USB cable. (It will turn on Blue LED.)
▲ ▼
Extract system image from downloaded SEUS image files Edit
Find 3 "FILE_(numbers)" files in SEUS db folder below. The file size are about 66KB, 15MB and 150MB.
C:\Program Files\Sony Ericsson\Update Service\db\13740270\blob_fs
Download ConvertTool.zip from here
Extract ConvertTool.zip, then put the 3 FILE_(numbers) files into the same folder.
Execute below command from cmd prompt. You will get 3 tgz files.
SeusDecrypt.bat FILE_(numbers)
The smallest file should be renamed "loader.sin".
Extract the largest file with 7-zip (as WinZip does not work), or rename *.tgz to *.zip, then extract it with WinRAR. You will get FILE_(number) files again.
Extract it with 7-zip or WinRAR to get *.sin files.
Download SIN2IMG from here
Convert system.sin to img file.
SIN2IMG system.sin system.img
▲ ▼
Modify system image Edit
Use linux PC
Download unyaffs tool from here, then make it
Download yaffs2 tool (mkfs.yaffs2.x86) from here, then put it into the same folder as unyaffs
Put system.img into the same folder as unyaffs
Extract the system.img into my_system folder
mkdir my_system
cd my_system
sudo ../unyaffs ../system.img
Modify my_system folder as you like. For example, download the Superuser and extract it,
mkdir extracted_superuser
cd extracted_superuser
sudo unzip su-2.3.6.1-ef-signed.zip
sudo cp extracted_superuser/system/app/Superuser.apk my_system/app/
sudo cp extracted_superuser/system/bin/su my_system/bin/
sudo chmod 644 my_sustem/Superuser.apk
sudo chmod 06755 my_system/bin/su
Compress my_system folder to image file.
sudo mkfs.yaffs2.x86 my_system my_system.img
▲ ▼
Burn system image Edit
Recommend using Windows PC, as Windows Android SDK has fastboot tool by default
Turn off the phone, then wait for a while.
Hold [Vol up] button, then connect USB cable. (will turn on the blue LED.)
Execute below command from cmd prompt
fastboot flash system my_system.img
Hi all!
I started the thread with request for dedicated new minis forum. Add your comments in it or we won't get it
http://forum.xda-developers.com/showthread.php?p=16580633
Regards to DooMLoRD.
We have firmware for FlashTool (4.0.A.2.368).
http://forum.xda-developers.com/showthread.php?t=1216783
There's also rooting instructions (the same as here, only for devices with unlocked bootloader).
Brilliant - many thanks for keeping us posted!
Hi everyone! I read all available threads but still cant find the way to root my device.
The problem is that i can not access S1 Fastboot mode - LED indicator just doesn't turn to blue.
Is there any other way to gain root access on SK17i with 4.0.A.2.368 firmware, without the need of fastboot mode at all?
um can any one of you please give me a guide on how to get a cyanogen mod on my xperia mini pro sk17i?my device currently has android 2.3.4. i managed to root my device using the doomlord method.but what am i supposed to do after that to get cyanogen mod 7.1?
Guys, there is already a sub forum for this device. Don't keep asking here.
Sorry for english
Sent from my U20i using xda premium
Related
hey guys, been a short term fan of android, and i recently (or what i thought so) rooted my X10i with the original RB..20 Firmware.
Today i updated to the new R2BA026 firmware. and my device appears routed but it not, how do i go about rooting this firmware to remove the annoying Moxier apps etc.
Plz Plz Plz Help
http://forum.xda-developers.com/showthread.php?t=740240
Read this thread !!!
I just found it Lol
Thank you for telling me anyhow.
im really stuck on rooting it even with the instructions. im in the CMD.exe and all im getting is it cannot find the files even though they are directly on my C drive and also it IS connected via USB / Development mode
hellllllllllllllllp!
do you have adb installed ?
I prefer this method - forum.xda-developers.com, having tried the other today it's a bit more complicated afterwards imo trying to run adb.
the other way you said to me i tried on my unlocked X10i, but it wont work on this build as its already above the 24 build.
Ive downloadd the SDK and i have the ADB.exe in the kit but am i looking at the wrong thing? how would i install it if it just runs a cmd.exe?
With this method you can root any regional firmware, atleast up to 026 and you will get updates from seus, root will be gone but its hopefully just to root the new firmware again.....
Saw somewhere a full script with adb inside no need to install it on the computer but atm i can find it
ok well, erm, which method would be better, ?? shall i do the original root procedure i did before flashing the files on to the phone?
fkofilee said:
the other way you said to me i tried on my unlocked X10i, but it wont work on this build as its already above the 24 build.
Ive downloadd the SDK and i have the ADB.exe in the kit but am i looking at the wrong thing? how would i install it if it just runs a cmd.exe?
Click to expand...
Click to collapse
extract the exploid_x10 to a folder with the same name directly under C:
then put the adb.exe, AdbWinApi.dll,AdbWinUsbApi.dll into same folder
then cd to that folder with command promt and then run runme.cmd
that should do it
ok well so far so goo most of the files are moving on to the SD card BUT...
c:\exploid_x10mini>adb push su /sdcard/su
failed to copy 'su' to '/sdcard/su': Permission denied
thats what im getting on my Cmd panel.
Sorry, adb.exe, AdbWinApi.dll,AdbWinUsbApi.dll should be put into Exploid_x10/FILES folder.........
so do i have to create a folder inside the exploid_x10mini? because the files are already there
fkofilee said:
so do i have to create a folder inside the exploid_x10mini? because the files are already there
Click to expand...
Click to collapse
nah then u got the right one, your sdcard shouldnt be mounted to pc
and you have to turn wifi off and on when program tells you to
usb debugging should be enables on the phone aswell
all good till running rootshell when it comes back saying...
$ rootshell
rootshell
rootshell: permission denied
sorted YEY!!!
Thank you for all your help. Im not a complete noob ith computers, i know quite a bit but, dealing with android is a bit of a new experience.
fkofilee said:
ok well, erm, which method would be better, ?? shall i do the original root procedure i did before flashing the files on to the phone?
Click to expand...
Click to collapse
It's personal preference I guess.
I rooted... now what?
How do I remove the Timescape and other crap after rooting with this method? If you didn't guess, I am a complete noob with Android.
I have to my hands for a few days only a X10 mini prototype with fw 2.1 (not final fw - debug)
Tell me any dev if they want any file to upload and maybe help him for any way.
Check my photos to proved it what i say!
http://img405.imageshack.us/i/1286524385375.jpg/
http://img140.imageshack.us/i/1286524445708.jpg/
http://img412.imageshack.us/i/1286524481171.jpg/
http://img253.imageshack.us/i/1286524511580.jpg/
Many thanks to Bin4ry and wolfilein who helped me to dump the below files!!!
Dump System With ADB:
http://rapidshare.com/files/424248203/System__updated_with_ADB_.rar
Dump Bootloader:
http://rapidshare.com/files/424303620/spl.bin
Note:
1. Root permision only from ADB shell # [not from device (terminal emulator)]
2. Universal Androot 1.6.1 doesn't works!
Can you try to locate the lockscreen.apk(?), idk if there is such a file but if yes can you post it please, thanks for the screenshots btw
Lef.teris said:
I have to my hands for weekend only a X10 mini prototype with fw 2.1 (not final fw - debug)
Tell me any dev if they want any file ( as /system ) to upload (rapidshare) and maybe help him for any way.
Check my photos to prove what i say!
http: //img405.imageshack.us/i/1286524385375.jpg/
http: //img140.imageshack.us/i/1286524445708.jpg/
http: //img412.imageshack.us/i/1286524481171.jpg/
http: //img253.imageshack.us/i/1286524511580.jpg/
Click to expand...
Click to collapse
Looks the same except for the lockscreen , Good job OP , bad job SE... so no surprises huh??
Could you post a video of this?????
I really think the new Interface looks much better.
tejagamer said:
Could you post a video of this?????
I really think the new Interface looks much better.
Click to expand...
Click to collapse
Its the same ' BLUE BLUE BLUE ' :x , frankly i expected a little more
ya
its the same blue
But i feel its abit darker
Dunno why
Lets wait for official though
Can you dump the loader please so that i can compare to stock one?
Procedure is decribed in X10 forums - custom rom development.
Regards
Bin4ry
Sent from my X10i using Tapatalk
Oooo go Bin4ry thanks!
Sent from my X10i using Tapatalk
You can't just tease us like that. Anything new to report?
System dump please
install the android SDK (developers.android.com)
start CMD (type cmd in search box after opening windows "start")
change path to android sdk\"tools" folder by typing in "cd c:\PATH_TO_YOUR_SDK\tools" (note: PATH_TO_YOUR_SDK is the location of your "android-sdk-windows" folder)
on your phone: Setting -> Applications -> Developer -> Debug Mode
connect your phone with your pc
back to cmd console: type "adb pull /system"
the full system dump shall be in YOUR_SDK_FOLDER\tools\system
Cheers
further reply, sorry!
Bin4ry said:
Can you dump the loader please so that i can compare to stock one?
Procedure is decribed in X10 forums - custom rom development.
Regards
Bin4ry
Sent from my X10i using Tapatalk
Click to expand...
Click to collapse
Bin4ry for some reason i don't know why i can't use ADB connection with specific phone (probably reason it's a prototype phone) maybe it want different driver. for my other x10 mini RTL i haven't any issue with ADB.
it need a driver called SEMC HSUSB Device (from device manager - Windows)
http: //img219.imageshack.us/img219/557/10102010131939.jpg
I find another way to pull files from this prototype x10 mini with ftp app
If you know how can i solve with issue please tell me!
In the Menu where USB-Debug is located, there should be an option with PC-Companion. If you check this the phone will ask if you want to install PC-Companion if a usb-cable is connected.
If you choose Install on phone, then in Windows a new Drive will popup, the driver should be located there.
Regards
Bin4ry
Bin4ry said:
In the Menu where USB-Debug is located, there should be an option with PC-Companion. If you check this the phone will ask if you want to install PC-Companion if a usb-cable is connected.
If you choose Install on phone, then in Windows a new Drive will popup, the driver should be located there.
Regards
Bin4ry
Click to expand...
Click to collapse
Pc-Companion installed on my pc but nothing found, it not recognised as connected phone!
Pop up menu is disabled when connecting the phone with pc (not the same with ratail x10 mini)
I try to install other drivers (for X10 mini, X10) but nothing, also nothing found with windows update on Win7
maybe you can copy the things that are need to sdcard an use an terminal emulator for this ??
wolfilein said:
maybe you can copy the things that are need to sdcard an use an terminal emulator for this ??
Click to expand...
Click to collapse
Please tell how can i do this!
@Bin4ry, isn't root required to install io_ex2.ko? Is it not required to dump the boot loader?
Is it worth trying Exploid to gain root? Although I believe we think it won't work. It's got to be worth a try
yes first you need to root the x10 minni
but i think that i is already rooted
then extract this zip to sdcard
forum.xda-developers.com/attachment.php?attachmentid=407185&d=1285348031
open an terminal emulator app and give in
Code:
su
cd /sdcard
insmod io_ex2.ko
cat /proc/splimage > /sdcard/spldump.bin
then you upload the file spldump.bin
(it is on sdcard)
Nice one wolfilein.
@Lef.teris, when you manage to get the drivers sorted of the adb, please try the following: http://android.doshaska.net/x10miniroot
Edit: although I doubt this will work - try using the drivers from here!
wolfilein said:
yes first you need to root the x10 minni
but i think that i is already rooted
then extract this zip to sdcard
forum.xda-developers.com/attachment.php?attachmentid=407185&d=1285348031
open an terminal emulator app and give in
Code:
su
cd /sdcard
insmod io_ex2.ko
cat /proc/splimage > /sdcard/spldump.bin
then you upload the file spldump.bin
(it is on sdcard)
Click to expand...
Click to collapse
I try to gain root with universal androot 1.6.1 but doesn't works. I can't try with exploit, i have issue with ADB driver
Any other way to gain root? so i can take and upload the file you want!
Another thought - could you right click on one of the devices in screenshot you uploaded (this one) and select properties, then click the details tab. Next in the drop down box select Hardware Ids.
Could you post the text thats in there? Hopefully we'll be able to find a driver
Hi,
I've recently purchased a Huawei Mediapad Tablet running honeycomb 3.2.
I would like to root this tablet but am unable to find any guides on the web.
Any pointers and guides would be much appreciated.
Thanks
bump for you interested to know as well
Yeah, I also bought mediapad last 2 weeks, this honeycomb really unstable, hang/reboot very often. And when I switched to full resolution 1280x800, you can feel lagging. Disappointed with stock ROM.
i want to root huawei mediapad su302,please,thanks
Same here...
Just picked on up tonight, not bad hardware but the os needs a kick in the a$$.
Lets get this going people, time is a wasting!
I have beginner modding skills if anyone wants to help me start this?
Recently, I read some reference from some Chinese Forum..
There are Rooted ROMs... and tutorials about how to root by youself..
If you decide to create a rooted rom by yourself..
You need a Linux environment to do that...
Here's how I did mine...
1. First of All, download the latest ROM from Huawei official site..
http://www.huaweidevice.com/worldwide/technicaIndex.do?method=gotoProductSupport&productId=3779&tb=0
2. Unzip it, you'll have a folder "dload"
3. Extract the file" system.img.ext4" from the Update.zip
4. Copy the "system.img.ext4" into your Linux Environment..
5. mount the image file like these...
#mkdir /mnt/tmp
#mount -o loop system.img.ext4 /mnt/tmp
6. put the "superuser" binary into the path /mnt/tmp/xbin
#cp su /mnt/tmp/xbin
7. Assgin the correct permission to the su binary
#chmod 6755 /mnt/tmp/xbin/su
8. Unmount the path and copy the system.img.ext4 into the original Update.zip
#umount /mnt/tmp
9. Put the "dload" folder into the root directory of a Micro-SD
10. Power Up your mediapad, when it vibrates, press and hold Volume Down until you see the Android icon, and it will try to flash the new ROM.
11. After everything is done, Look for Super User from Market, you'll see.
--
For su binary.. you can find it here http://androidsu.com/superuser/
Here's the product of all the above steps...
http://www.multiupload.com/0WPLQILCGH (114.73MB)
(I was using the official ROM dated 26 November..
and Put the su binary Together the superuser app into the system directory.
nothing else I have done to the ROM..)
You can also flash the system.img.ext4 into your mediapad directly via fastboot
to activate the fastboot mode of mediapad..
1. Connect your mediapad to your Computer with USB cable
2. Power up the mediapad with Volume Up button press and hold until your computer sense it and install the correct driver for it.
3. Direct flash your mediapad like this..
fastboot flash system system.img.ext4
then, reboot your mediapad..
you'll have your apps un-touched, while you have the latest system. enjoy~!
--
Fastboot, extracted from the Android SDK..
Many thanks squide, especially for the system image. I was too lazy to break out ubuntu...
I now have a rooted mediapad.
However the command below did not work for me.
squide said:
3. Direct flash your mediapad like this..
fastboot flash system.img.ext4
.
Click to expand...
Click to collapse
I had to use fastboot flash system system.img.ext4
last rom with root + busybox + some app
http://uploading.com/files/53f162e9/dload.rar/
I can now run my favourite titanium backup.
squide said:
Here's the product of all the above steps...
http://www.multiupload.com/0WPLQILCGH (114.73MB)
(I was using the official ROM dated 26 November..
and Put the su binary Together the superuser app into the system directory.
nothing else I have done to the ROM..)
You can also flash the system.img.ext4 into your mediapad directly via fastboot
to activate the fastboot mode of mediapad..
1. Connect your mediapad to your Computer with USB cable
2. Power up the mediapad with Volume Up button press and hold until your computer sense it and install the correct driver for it.
3. Direct flash your mediapad like this..
fastboot flash system.img.ext4
then, reboot your mediapad..
you'll have your apps un-touched, while you have the latest system. enjoy~!
--
Fastboot, extracted from the Android SDK..
Click to expand...
Click to collapse
Thanks. Manage to root my mediapad without losing the installed apps.
Btw use this link to get the fastboot
http://dl.google.com/android/android-sdk_r13-windows.zip
squide said:
5. mount the image file like these...
#mkdir /mnt/tmp
#mount -o loop system.img.ext4 /mnt/tmp
Click to expand...
Click to collapse
Which distro are you using?
I'm having some problems writing to the image after mounting it as a loop back for Ubuntu 10.4
just a question about this device as GSMarena shows GSM support does it mean the you can use it as a phone.
freeko2 said:
just a question about this device as GSMarena shows GSM support does it mean the you can use it as a phone.
Click to expand...
Click to collapse
It's been discussed quite a bit in the Hardwarezone forum. I cannot post a link yet, so just google for 'mediapad hardwarezone forum'.
You need to install the HuaweiMediaPadPhone.apk which you can request from those in the forum. You can also find the link for Mediafire on the forum.
Once you install the apk, you will get the standard Phone and Messaging apps which you can use to make phone calls over GSM and also SMS. Working well for me.
venomrat said:
Many thanks squide, especially for the system image. I was too lazy to break out ubuntu...
I now have a rooted mediapad.
However the command below did not work for me.
I had to use fastboot flash system system.img.ext4
Click to expand...
Click to collapse
Thanks. I had a lab full of Linux systems, so I tried to put the 'su' in myself. Thanks to this fastboot procedure, I have a rooted system with no apps lost.
venomrat said:
Many thanks squide, especially for the system image. I was too lazy to break out ubuntu...
I now have a rooted mediapad.
However the command below did not work for me.
I had to use fastboot flash system system.img.ext4
Click to expand...
Click to collapse
So did you Root it with a PC?
Could you give me some info on how you did this?
I have sdk r13 & fastboot (is 1.img the file I need to flash?)
It's quite easy. just ensure.
1. Your Android SDK is installed correctly
2. Mediapad Fastboot USB driver is detected
3. get the correct system.img.ext4
4. Ensure fastboot works before issuing the flash command
by doing this you would not lose the current installed apps as this would only flash the
updated system plus root binary. After doing so please download superuser from android market
the flash process take less than 10 minutes.
btw i use this command
fastboot flash system system.img.ext4
yup i use a pc to this.
disclaimer:
there's risk of bricking your mediapad. do it at your own risk.
Thanks,
I might try this.
Where can I find system.img.ext4?
DUH!!!! I unzipped the Hauwei firmware folder update.zip and found it - that's the right one right?
---------- Post added at 02:37 PM ---------- Previous post was at 01:55 PM ----------
Also, I don't know if you saw or not, but I lost 4G connection since I originally had a T-Mobile SpringBoard and flashed the Hauwei firmware to it. Do you think rooting it will allow the 4G again? If so, would it be easy for a 'tard like me to do ?
yup that's the right file. I'm using mediapad.
Probably this rom resources file does not have the 4g icon.
Do you still have the same broadband speed?
Can you please verify this using speedtest?
Here's my recent speeds (3G). I wish I would've saved my 4G tests, but didn't realize I was going to loose all of that.
https://skydrive.live.com/redir.asp...372FEF79249B184B!172&authkey=!AHnxi6Q8Yj6srLQ
Also, what do you know about typing ()()2846579()()+ in the calculator. Can anything really be modified here? I've played around with the preferred frequencies and radio bands, but not sure what's really going on. And I think some of it goes back to a default anyway.
I was hoping that something like no 4G icon was the issue, but looking at the speeds (these are test from an area that I know get 4G speeds). I go to:
Settings >Mobile networks>Network operators>Search networks I only see T-Mo and AT&T 2G & 3G
Hello all,I had bought a local tablet from calcutta called ICE Xtreme on which I had nightmares,but it also helped me learn n now here is it,a short yet complete guide for ur allwinner devices.
Like me,some of u might have been bored enough abt the stock rom that we decide to experiment.since allwinner CPUs can boot over USB(livesuit mode) n SD cards (phoenixcard) we think nothing will b wrong n flash without a full rom backup (i hav a script uploaded here,find it n hav a look), after the flash we find the stock ROM gone,camera,touch,wi-fi etc gone haywires n cache is mounted as SDCARD!!! Yes,those who used livesuit hav been in stuff lik this. Now I was also in one n upon reading alot I hav seen ppl editing bootloaders,using keyboard mouse,plugging HDMI(lcd broken). After a month of fiddling wit my device its time i share a shortcut that can save many hours of ur life.
Also do backup the boot n bootloader on ur pc as sumtimes flashing destroys the SD.
1st step. Backup ur bootloader n boot images. Use "cat dev/block/nandc > sdcard/dump/boot.img" to backup boot..nw backup bootloader the same way,by replacing nandc wit nanda.
Now u use adb pull method to backup ur system,etc,data(its optional,only do it if u want ur apps).n any other folder from the root of ur device.my script can help u do it instantly. Anyways,u must get the etc n system folder.
After that ur free to flash any ROM image through any method (actually,livesuits the best if u can find the img). Now after flash ur device is on right?? Does the SDCARD mount??if no then turn on USB debug,in adb shell type cd dev/block <enter> then type ls n ull see a list of nand partitions,the last one is the SDCARD in raw format.so format is by: su busybox mkfs.vfat dev/block/nand[drive letter,i.e. nandj] n then type vold.ur sdcard will mount.
Now send those boot n bootloader files to SDCARD/dump. U can use mkdir or mannually make the dir n copy. Thn simply type "cat sdcard/dump/boot.img > dev/block/nandc" n same way type nanda n bootloader to restore the bootloader. Now use adb to push the files of ur stock ROM system/vendor/modules(which u backed up earlier) to tablets system/vendor/modules. N the contents of etc folder to etc on the tablet.nw reboot.
Hey!!! Its working.the LCD shift is gone,cam n wi-fi doing good,touch is not reversed or stuff. Congratulations u restored ur tablet,n now running a completely diffrent ROM on it.enjoy.
Heres another shortcut ive learned. U can get any update.zip n convert it to licesuit image. Just extract the system dir. Thn copy it to ur SDCARD. Make modification if needed,copy the modules u backed up.In adb shell type make_ext4fs -s -l 300M -a system <filename.img> (dir of ur system,i.e mnt/sdcard/system) it will make u a .img file which is same as the system.fex file u get when u break a livesuit image. Copy n replace the ROMs boot n bootloader.fex files wit ur backed up boot n bootloader.img (rename .img to .fex) pack the image again to livesuit format n burn it. It will install like a normal ROM. BUT MAKE SURE FILE PERMISSIONS OF READ WRITE N EXECUTE IS INTACT. ELSE ULL ENJOY HOURS OF BOOTANIMATION. but if ur stuck use the method above n flash any other ROM n fix the RON fr ur device. Guys ROM developing n editing fr allwinner devices are not easy...BTW id lik to thank user [iamabadduck] fr his actual A10 backup script. On which i made mine. Im still doing experiments. Hope this info i shared makes the readers modest enough to make the hit thanks. Bye. [ ill b around,so if any quests,ill ans them].
I was very excited to see someone finally post a guide for these mysterious tablets! Thank you!
However, I ran into some difficulties trying to make use of them, but I think this has more to do with my hardware and trying to match it with the appropriate ROM and compatibility zip.
You see, I have a Kocaso M1060W. It's a very nice little tablet but trying to identify it has been difficult. As far I can tell, it's a clone of the Protab2XXL (I don't know what version) or something called the BC1077. It seems easier identifying other Allwinner A10's, apparently. I know some identifying information can be found in the build.prop file and that's how I figured out the tablets of which it is a clone. I even tried finding a database of different ImageSuit images I could try to use, but either there is none or my Google skills are suffering. Does it matter that Kocaso chose to go with PhoenixCard for flashing their tablets? Some documentation suggests the images for both are the same.
Can you help me find documentation that would help me identify the board and the hardware? Let me know what information you need from the tablet, and I will get it to you. Identification would go a long way towards me making use of your steps.
Also, a question. After the rom is flashed and you "adb shell" in, you have me trying to mount the sdcard directory via the nand block devices, and then entering "vold". It doesn't error but nothing seems to happen. Even stranger, running "mount" tells me that it's done something. Is it because most of the ROM flashes require the data wipe that I should assume I have the capability to read/write within the SDCARD directory?
Allwinner A10 ghost touch (Icoo D70W, goodix chip)
Hello There!
I've got this tablet since last year, but it worked brilliantly for four minutes only.
Here is some detail:
ICOO D70W, Allwinner A10 board , 1 Gb of RAM and 8Gb storage, ICS android.
7 inch IPS display on 1024X600 resolution capacitive multitouch.
The original firmware was a nightmare, so slow , and full of chinese thing with no google play, quick decision -> get another firmware.
I've installed an actual version of AOKP ( I think it was the 9th version) and I used one of those comp file which was for an ainol tablet same hardware details.
After this , my big four minetes has started until a figured out the camera does not work.
I used another compatibility file, from a hyundai tablet same camera details, camera ok , but the touch chip went down and cannot get back, since that.
Ghost touches on the screen, but the normal touches are recognised as well.
Do you have any idea, how to reflash that touch driver chip?
attached files from the original firmware, maybe give some help:
And a video on y_-tube, with this watchcode: YfNZf2BgL3w or use "ICOO D70W ghost touch problem" keyword
Thanks in advance.
Zsolt
Compatability
konyazsolt said:
Hello There!
I've got this tablet since last year, but it worked brilliantly for four minutes only.
Here is some detail:
ICOO D70W, Allwinner A10 board , 1 Gb of RAM and 8Gb storage, ICS android.
7 inch IPS display on 1024X600 resolution capacitive multitouch.
The original firmware was a nightmare, so slow , and full of chinese thing with no google play, quick decision -> get another firmware.
I've installed an actual version of AOKP ( I think it was the 9th version) and I used one of those comp file which was for an ainol tablet same hardware details.
After this , my big four minetes has started until a figured out the camera does not work.
I used another compatibility file, from a hyundai tablet same camera details, camera ok , but the touch chip went down and cannot get back, since that.
Ghost touches on the screen, but the normal touches are recognised as well.
Do you have any idea, how to reflash that touch driver chip?
attached files from the original firmware, maybe give some help:
And a video on y_-tube, with this watchcode: YfNZf2BgL3w or use "ICOO D70W ghost touch problem" keyword
Thanks in advance.
Zsolt
Click to expand...
Click to collapse
If you could Post an lsmod from both the Working Firmware and the Non-Working I will take a swing at answering your question...The problem is likely one compat file is installing drivers for one of Your pieces of hardware and not the other and the other compat file is istalling the driver for the other piece but not the One... confusing sounding...
But Bottom Line is If I had the Lsmod from the working Hardware and the 2 compatability files you tried I could likely alter one of the compatability files to cover All of your hardware.
Or better yet pull the Bootloader.img and the Boot.img out of your Tab and send them to me...
you can do this by opening a cmd window from a directory where you wish to store the .img files then type the following :
adb shell su -c "cat /dev/block/nandc > /mnt/sdcard/nandc-root.img" (Press enter Key)
adb pull /mnt/sdcard/nandc-root.img (Press enter Key)
That will give you the Boot.img (named nandc-root.img)
adb shell su -c "cat /dev/block/nanda > /mnt/sdcard/nanda-bootloader.img" (Press enter Key)
adb pull /mnt/sdcard/nanda-bootloader.img (Press enter Key)
That will give the bootloader.img (named nanda-bootloader.img)
send those from both your OEM Rom that is working and the Target Rom you wish to make work .... from that I can either write a compat patch for it or send back the edited ones from your Target Rom (the one you wish to work)
Srry i cudnt keep my promise of being around. Had been pretty busy looking for stock JB ROMs in livesuit format. Found some. Some worked n some didnt. Will abt the touchscreen issue if that Rom has a focaltech ftx_5x touchscreen its broken. U hav to compile it again leaving out the multitouch part in a header file. Do a google search. There r alot of articles. N abt da nand part well not all roms break the internal SD partition. The busybox thing u do only when ur internal cards dont mount. It will NOT WORK FOR A MICROSD IF U HAV ONE. Its generally mounted as extsd.
Try reading from here:
konyazsolt said:
Hello There!
I've got this tablet since last year, but it worked brilliantly for four minutes only.
Here is some detail:
ICOO D70W, Allwinner A10 board , 1 Gb of RAM and 8Gb storage, ICS android.
7 inch IPS display on 1024X600 resolution capacitive multitouch.
The original firmware was a nightmare, so slow , and full of chinese thing with no google play, quick decision -> get another firmware.
I've installed an actual version of AOKP ( I think it was the 9th version) and I used one of those comp file which was for an ainol tablet same hardware details.
After this , my big four minetes has started until a figured out the camera does not work.
I used another compatibility file, from a hyundai tablet same camera details, camera ok , but the touch chip went down and cannot get back, since that.
Ghost touches on the screen, but the normal touches are recognised as well.
Do you have any idea, how to reflash that touch driver chip?
attached files from the original firmware, maybe give some help:
And a video on y_-tube, with this watchcode: YfNZf2BgL3w or use "ICOO D70W ghost touch problem" keyword
Thanks in advance.
Zsolt
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1520943
It's a thread about the allwinner A10 or EKEN T01A.. it shows how to reflash to original and updated EKEN firmwares via livesuit. And also i think they mentioned something about touchscreen issues. Hope it helps
Hi please help me! I have nightmares too with my tablet:
Hi, i have a mid tabler model HBD-Mid-708G like that http://marcopolocompany.fucsio.com/e...oducts/MC-708G . This is a Boxchip a10 with 11 partitions, i get this info throw ADB.
My problem was try to install CWM getting the error Can´t Mount / Read!!!!!
I have been used this roms:
F1-4.1.1-20130319.2.0.6-A721_v4.2
pdf_android4.0.10_ctp7_public_en_0319
Q7_512M+flash+Gmail
rom_woo_comet_404_291112_0cd4d
RSH-A10-C2
speed.1.1.1
sun4i_crane_t01a-linsay-20120411
and only rom_woo_comet where some Ok! .
Solved this CWM problem flashing a rom_woo_comet using LiveSuit but the result is an screen resolution problem: (the image attach) .
So please any can say me a correct rom?
Thanks
accessing nand
hi there,
this is interesting stuff you are talking about here. Unfortunately, I get stuck to the beginning. How do you access the nand???
you say sart with cat dev/block/nandc > sdcard/dump/boot.img
I'd love to but where do you enter these commands? When I connect my tablet to my computer, I see certains parts as usb storage, and I have no way of entering commands to the tablet. From within android, everything is blocked...
thanks for your help
nacxo said:
Hi please help me! I have nightmares too with my tablet:
Hi, i have a mid tabler model HBD-Mid-708G like that http://marcopolocompany.fucsio.com/e...oducts/MC-708G . This is a Boxchip a10 with 11 partitions, i get this info throw ADB.
My problem was try to install CWM getting the error Can´t Mount / Read!!!!!
I have been used this roms:
F1-4.1.1-20130319.2.0.6-A721_v4.2
pdf_android4.0.10_ctp7_public_en_0319
Q7_512M+flash+Gmail
rom_woo_comet_404_291112_0cd4d
RSH-A10-C2
speed.1.1.1
sun4i_crane_t01a-linsay-20120411
and only rom_woo_comet where some Ok! .
Solved this CWM problem flashing a rom_woo_comet using LiveSuit but the result is an screen resolution problem: (the image attach) .
So please any can say me a correct rom?
Thanks
Click to expand...
Click to collapse
You need to edit your script.bin inside the bootloader.img... there is a utility to do this on techknow.me...
to do it manually you need to extract the script.bin file from the bootloader.img ... easiest way is from adb shell
Open a windows command window (this assumes you have adb.exe in your Path .. if not you must do this from the
same folder where adb.exe is located)
type the following
adb shell su -c "cat /dev/block/nanda > /mnt/sdcard/nanda-bootloader.img"
adb pull /mnt/sdcard/nanda-bootloader.img
this will place a file called nanda-bootloader.img in the folder where you ran the windows command window.
Now copy the file to your Linux Machine or VM
and from a terminal do the following:
mkdir bootloader
sudo mount -t vfat ./nanda-bootloader.img bootloader
This mounts the bootloader image to the bootloader folder.... in the bootloader folder copy the script.bin file to another location for editing.
to edit it must be converted to fex... you will need the fex tools for this I have them posted here: http://www.4shared.com/zip/Nzn6PV-b/tools.html
your Linux machine has to be x64 for those to work.
from the folder containing the tools folder and script.bin file open a terminal and do the following:
./tools/bin2fex script.bin > script.fex
this will create the script.fex file which is editable in a linux text editor, open the file and edit the [lcd0_para] section
to correct your screen shift ... the exact settings needed are impossible for me to determine as I do not
have your tab nor the rom you originally had on it.. if you have the original rom available (with screen position correct)
you can pull the script.bin from that rom and replace the entire [lcd0_para] section with the same section from your working rom
to solve the issue.
once edited convert back to .bin from a terminal with the following commands:
./tool/fex2bin script.fex > script.bin
now open the bootloader folder as superuser and delete the script.bin and script0.bin located inside...
copy the new script.bin file in and also copy it and rename the copy to script0.bin and place that there as well.
then from folder containing bootloader folder open a terminal and do the following:
sudo umount bootloader
now copy nanda-bootloader.img to windows machine.
open a Command window in the folder containing your new nanda-bootloader.img file and do the following
adb push nanda-bootloader.img /mnt/sdcard
adb shell su -c "cat /mnt/sdcard/nanda-bootloader.img > /dev/block/nanda"
adb shell rm /mnt/sdcard/nanda-bootloader.img
adb shell su -c "sync"
adb shell su -c "reboot"
if all was done properly your tab should now reboot with the correct screen geometry. The utility I mentioned does
pretty much all of this for you, but i cannot link it here as it is on techknow.me which requires registration to
download ... and the rules forbid links to such sites here.
I hope that all helps you.
---------- Post added at 12:24 PM ---------- Previous post was at 12:16 PM ----------
djahma said:
hi there,
this is interesting stuff you are talking about here. Unfortunately, I get stuck to the beginning. How do you access the nand???
you say sart with cat dev/block/nandc > sdcard/dump/boot.img
I'd love to but where do you enter these commands? When I connect my tablet to my computer, I see certains parts as usb storage, and I have no way of entering commands to the tablet. From within android, everything is blocked...
thanks for your help
Click to expand...
Click to collapse
You must have the ADB drivers installed and know where they are located, placing them in your Path statement is a good idea if you intend to do much ROM editing or direct Tablet commands from and adb shell.
NOTE: To open a command window from any folder on your computer in Explorer browse to the folder you want to open command window from
then in an area of the folder window that is empty right click mouse while holding shift then select open command window here
Once you have ADB INstalled, if the adb.exe is in your path open a command window from any folder you like on windows and type the commands in the command window. If ADB.exe is not in your path you must open a command window in the folder containing adb.exe
(Usually the android SDK Platform tools folder)
I Hope that helps
Thanks fsebentley, I've now copied all nandX partitions.
what I'm trying to do now, is to create a bootable sd card. I believe I must tailor u-boot.bin to boot a specific kernel with my specific hardware setup.
I've found a lot of resource for arm boards, but almost none for tablets, except for direct flashing but I'm not ready to go this far.
So, do you know about a nice tool to read what's in u-boot.bin and eventually modify it?
Touchpad driver
Hi!
I need some help!! I want to include touchpad driver an cm9 installer because when I instal the system with CWM but the touchpad not working!!!
Here is the topic where you can find the ROM: http://forum.xda-developers.com/show....php?t=1861445
Sorry I write here because I can't write in the original topic.
Thank for help!!!
Apad 711 stuck at boot logo
Hi Guys,
I need help. one of my friend has a Apad711 tablet and his stock android recovery was changed by cwm 5.08 incorrect version and hence the power + - or power button was not responding.
I took over and had flashed 6.0.2 8 cwm by following this forum http://forum.xda-developers.com/showthread.php?t=2189640
and recovery was working properly, but then i though of upgrading it to cyanogen mod 9 and downloaded the files using this forum
http://forum.xda-developers.com/showthread.php?t=1760929
however after the update was completed the touchscreen didnt work and I had to connect a usb OTG cable along with usb mouse to get into recovery. I then did a little research and tried flashing a couple of compatibility zip
711i_compatibility_1.1.0.zip, lyf1_compatibility_1.1.0.zip, 711i_compatibility_1.2.0.zip, lyf1_compatibility_1.2.0.zip which had similar specs from this website http://old.androidfilehost.com/main/Allwinner_A10_Developers/christiantroy/misc/
but even after doing so touchscreen,camers etc didnt work.
since i had made a backup of stock rom using cwm before flashing cyanogenmod 9 i thought of restoring it back using cwm 6.0.2.8
i was able to restore the back up but to my surprise i am now stuck at apad boot logo and cannot boot to recovery using the volume - and power key. i tried to connect the tablet to pc so that i can get into adb interface and reboot to recovery but the computer detects the tab as unknown device
I now need help to get into recovery and flash a rom that would make it work or complete tutorial to install/flash a new /stock rom or cyanogenmod to get the device back to life.
please refer to the manufacturers website link listed below for specs:--
http://www.apadtab.com/711_spec.php
Any help would be greatly appreciated.
allwinner a10., broken bootloader
Hi i've got a eneoze tablet with an allwinner A10., now i've flashed my bootloader with berryboot en it was working., later i wanted to change some things in de configs of the berryboot bootloader and i messed up. Now my tablet is completely dead.
It doesn't doe anything when i try to turn it on., de screen doesn't even light up., it isn't recognised when i connect it to the pc so fastboot., adb aren't working eather.
Do you have any ideas on how to resolve this.?
Greets Sam
sammekevremde said:
Hi i've got a eneoze tablet with an allwinner A10., now i've flashed my bootloader with berryboot en it was working., later i wanted to change some things in de configs of the berryboot bootloader and i messed up. Now my tablet is completely dead.
It doesn't doe anything when i try to turn it on., de screen doesn't even light up., it isn't recognised when i connect it to the pc so fastboot., adb aren't working eather.
Do you have any ideas on how to resolve this.?
Greets Sam
Click to expand...
Click to collapse
If you can't flash it from your pc, create a bootable sd card. For example, you could copy your berryboot image to the sd card and boot from it.
Supposedly, you saved your tablet nand into an image before messing up with that nand. Once you boot from sd, flash the nand again with that saved image. Good luck to you
need a little help
i wnt to increase resolution of my a10 tab from 800x480 to 1024x600....to do so i need to edit the bootloader(bootloader.fex)
but,the problem is i can't edit the bootloader.fex correctly......how to edit properly
Guys, I've got it!
EDIT 2:
DON'T FOLLOW THIS TUTORIAL UNLESS YOU REALLY WANT TO UNLOCK YOUR BOOTLOADER. YOU'LL LOSE BRAVIA ENGINE/ X-REALITY SUPPORT!
There are now root methods that don't require you to unlock your bootloader/ forfeit certain functionality.
EDIT:
As I won't be responsible for releasing pirated software, here's a rooted 475 system.img prepared by m3dd0g: http://www.androidfilehost.com/?fid=23060877490000325
Please understand the risks involved with using such a file provided by someone else. It may contain malware that collects sensitive data. I'm not saying m3dd0g has done this or would do this, but equally, I haven't checked.
Using the above file, follow this tutorial from step 21 (step 38 if you are already running 475): http://forum.xda-developers.com/showpost.php?p=44612882&postcount=15
If you're not comfortable with using the provided system.img, then follow the above tutorial from the beginning to create your own (though this is a fairly involved process).
You will need to have unlocked your boot loader first. Please understand the implications of this before doing it (loss of Bravia Engine, loss of official upgrades).
You may be able to stop after step 42 in the tutorial. If so, you should be able to avoid any data loss. However, if you are unable to use Google Play Store after flashing, you'll need to continue from step 43, which will erase all of your data.
Remember, the risk is all on you if you follow these instructions and you may end up bricking your device. If you're not comfortable with any of the steps, then protect your investment by stopping!
ShALLaX said:
Guys, I've got it!
Click to expand...
Click to collapse
Share with us please... Need it badly...
dralex88 said:
Share with us please... Need it badly...
Click to expand...
Click to collapse
Please note that I have since written a much more detailed procedure for this. I will not remove this post as it gives a good overview of what is required to obtain root access to your device. However, if you want to run through the process, I would recommend starting with this post: http://forum.xda-developers.com/showpost.php?p=44612882&postcount=15
So, I can share the steps, but I can't really share the binaries since they belong to Sony. When I get some more time, I'll make this a bit more detailed.
1) Unlock bootloader. This is required as this method uses flashboot, not flash mode.
2) Obtain the HK 471 version of the stock ROM (ftf) and flash it. It's uploaded on these forums. (You'll lose ALL OF YOUR DATA!)
3) Extract system.sin
4) Explode system.sin to system.elf.
5) Extend system.elf to the correct size. (dd if=/dev/zero of=/tmp/moreZeroes bs=4096 count=5118; cat /tmp/system.elf /tmp/moreZeroes > /tmp/system.fixed)
6) Mount it. (mount -o loop /tmp/system.fixed -t ext4 /mnt/rootfs)
7) Replace su (obtain the hacked version, copy it to /mnt/rootfs/xbin/su; chmod 06755 /mnt/rootfs/xbin/su)
8) Repackage the file system (make_ext4fs -s -l 2048M -a system /tmp/system.img /mnt/rootfs)
9) Boot to "FastBoot" mode.
10) fastboot flash system /tmp/system.img
11) Boot to "Flash" mode.
12) Reflash the HK 471 ROM, but exclude ALL .sin files. Only choose to clear DATA, CACHE and APPSLOG. (You'll lose ALL OF YOUR DATA... AGAIN!)
13) Boot.
14) Log into Google account.
15) Install SuperSU.
16) Install Root Checker.
17) Enjoy.
Thanks dude! But I don't know how to extend, extract,explore,exam,excuse...........!!!!!!!! Sorry:*)
Just upload the ftf file you make, so easy. can you do that for your fans? Thank you so much
Sent from my C6802 using xda premium
kkkok8051 said:
Thanks dude! But I don't know how to extend, extract,explore,exam,excuse...........!!!!!!!! Sorry:*)
Just upload the ftf file you make, so easy. can you do that for your fans? Thank you so much
Sent from my C6802 using xda premium
Click to expand...
Click to collapse
As I said, I can't release these files because they do not belong to me. They are the property of Sony and I cannot redistribute them.
If someone else wants to take on this risk, that will be their decision. Maybe someone like DooMLoRD can write a shiny script to do all of this automatically. However, you'll always need to source an "FTF" from Sony using this method.
ShALLaX, can this method be applied without unlocking bootloader? Flashtool generally can flash everything but the kernel on locked phones, but here it seems there's no need for kernel flashing at all...
Drakosha said:
ShALLaX, can this method be applied without unlocking bootloader? Flashtool generally can flash everything but the kernel on locked phones, but here it seems there's no need for kernel flashing at all...
Click to expand...
Click to collapse
It's a fair question and something I was wondering. "I don't know," is the answer. I'm very, very green/ new when it comes to Android (I've only owned an Android device for about a week and have never used one previously). If it is possible without unlocking the boot loader, then that's fantastic news (and makes me wish that I hadn't unlocked mine). Unfortunately, I have no way of trying this myself anymore. If anyone wants to give it a go, they're more than welcome...
When the boot loader is unlocked, I would have expected Sony to put in some sort of verification of what's being flashed. This way, they could reject unofficial system.img flashes. Without this, it's pretty much impossible to secure the device from being rooted; once you have unadulterated access to the file system, you can do anything you like.
Update: Since this uses flashboot, unlocking is required. If this was restricted purely to flash mode, then an unlock would not be necessary.
ShALLaX said:
As I said, I can't release these files because they do not belong to me. They are the property of Sony and I cannot redistribute them.
If someone else wants to take on this risk, that will be their decision. Maybe someone like DooMLoRD can write a shiny script to do all of this automatically. However, you'll always need to source an "FTF" from Sony using this method.
Click to expand...
Click to collapse
Pls, can you share more details at colum 4,5,6,7,8 how to explore ,expand n mount, and use what tools to do that? Flashtool,7zp,cmd I got and what tool need prepare? Thx
Sent from my C6802 using xda premium
It has finally been accomplished. Pretty freaking sweet!
Without this, it's pretty much impossible to secure the device from being rooted
Click to expand...
Click to collapse
Well, almost every Samsung device gets rooted exactly the same way I'll wait for someone to put the modified ftf file in the Internet and then I'll try to flash it not with fastboot, but with Flashtool using flashmode. As far as I remember, only kernel.sin does not flash this way on locked phones.
kkkok8051 said:
Pls, can you share more details at colum 4,5,6,7,8 how to explore ,expand n mount, and use what tools to do that? Flashtool,7zp,cmd I got and what tool need prepare? Thx
Sent from my C6802 using xda premium
Click to expand...
Click to collapse
Yes, I'm just leaving the office now. As I said in my original post, I'll put up more detailed instructions a bit later. Certainly today. Thanks for your patience.
ShALLaX said:
Yes, I'm just leaving the office now. As I said in my original post, I'll put up more detailed instructions a bit later. Certainly today. Thanks for your patience.
Click to expand...
Click to collapse
thanks your are the man.:good:
I'll wait for the automatic root
Thanks for this accomplishment!
Pandora's Box is now open. I am eager to root immediately but I think I will wait a little bit and see some further development of the methods.
I guess the ADB commands described is to be performed through FastBoot.
HowTo
Right, here goes. I originally wrote this guide from memory, but since ROM 475 was released, I have run through it again, so I can confirm that it works. This isn't really for the faint-hearted, but I've tried to be as detailed as possible so that most people should be able to get through it. This tutorial probably applies to any Sony device that uses the same FTF/ SIN flashing mechanism.
What's frustrated me with the Android community (that I've seen so far) is people wanting to look like "Gods" by providing one-click rooting/ flashing solutions but not provide the technical explanations. Anyone that has a fairly decent understanding of Linux would find what I've achieved with this to be trivial and simple. All I have done is learned how to use existing tools and examine file formats at a very, very high level with a hex editor.
With this tutorial, I wanted to empower people with the knowledge of how to actually achieve the outcome of a rooted (Sony?) device. Yes, this HowTo will still require a fairly decent level of knowledge of Linux, operating systems and general principles of software and security architecture. However, I hope that this will be helpful for budding developers, system administrators and enthusiasts. Give a man a fish or teach a man to fish and all that. I'm happy to answer any follow-up questions.
All the above fluffiness aside... If you break your Xperia Z Ultra, you only have your-(impatient)-self to blame. If any of this intimidates you, please wait for someone else to release a rooted ROM. However, throughout all of my experimenting, I have always been able to fix my device by reflashing a stock FTF - though this is not a guarantee of safety to you. If you proceed with following these instructions, then the risk is all on you.
YOU WILL LOSE ALL OF YOUR DATA IF YOU FOLLOW THIS TUTORIAL UNLESS YOU TAKE A BACKUP FIRST!
Wherever possible, I have given credit to the original authors of tools and works.
You will need:
1) A Windows computer (I used a 64bit installation, but this probably isn't essential).
2) A Linux computer (VM works fine). I used Ubuntu LTS, but am a Gentoo enthusiast - I just didn't have time to install Gentoo! I used a 64bit installation, this may be required if you download a pre-built make_ext4fs binary.
3) An FTF for the Xperia Z Ultra. This is a legal grey area. Technically, you are entitled to use this, but I doubt that re-distribution is permitted. Please understand your legal stance when you download this. I used this ROM: https://docs.google.com/file/d/0B3BbH280MSmoVy1STFRRRDJBQ1k/edit
4) Flashtool (thank you, Androxyde, for the nice Java wrapper): http://forum.xda-developers.com/showthread.php?t=2229790
5) WinRAR (or anything that can unpack a .jar/ ftf). Thanks Alexander Roshal. Even though you make us pay for RAR, it's still one of the nicest compresion utilities for Windows.: http://www.rarlabs.com
6) ChainFire's "su" command. I'm sure ChainFire needs no introduction to seasoned members: http://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip
7) make_ext4fs. Though I'm sure this isn't the primary concern of people, my conscience obligates me to let you know that this code is provided by Google as part of Android. The source is available here: https://android.googlesource.com/pl...4d4b4db09a7052fc5fa108ac21f1b1948/ext4_utils/. It is licensed under the Apache 2.0 licence. You can build this yourself if you have an Android build environment, or you can cheat and download a binary from here: https://github.com/EpicAOSP/make_ext4/raw/master/bin/make_ext4fs (do make sure you download it with no extension).
8) The Android SDK (for Windows for this tutorial). Of course, this is provided by Google: http://developer.android.com/sdk/index.html
9) A fair amount of disk space - the unpacked system.sin file is around about 2.3GiB in size and you need to make a copy of this whilst extending it. Additionally, you'll also need to repack it. If you keep all of these files around, that'll be about 7GiB of storage space required in Linux alone. I would do this with anything less than about 10GiB of free disk space both in Windows and in Linux before you start.
Steps:
[Windows]
1) Install FlashTool to C:\Flashtool.
2) Open up the FTF in WinRAR, extract "system.sin" - it's pretty large, so give it some time.
3) Open up FlashTool.
4) Choose "File > Switch Pro".
5) Choose "Tools > Sin Editor".
6) Browse to the extracted "system.sin"
7) Click "Extract data" and wait. This takes a while, but eventually a larger "system.elf" file will appear in the same directory as the "system.sin" file.
8) Copy this to your Linux box. The tutorial assumes you copy it to /tmp/system.elf
The problem with this extracted ELF is that it seems to be truncated in some way. So, you need to extend it so that the geometry matches the expectation of the ext4 file system contained within. My extract was 5,118 blocks short (a default ext4 block is 4KiB). So, we'll extend it now. I'm not sure if this is a deficiency in the SIN extractor or something else. You can verify how many blocks you are out by through running "dmesg," which will show you how many blocks the ext4 file system believes it occupies and how many blocks the actual loopback device takes up.
[Linux]
To make things easier, you can just do all of this as root to avoid permission issues (but be careful not to ruin your distro).
9) Copy make_ext4fs to /bin then run chmod 755 /bin/make_ext4fs
10) Copy UPDATE-SuperSU-v1.51.zip to /tmp, then run: cd /tmp; unzip UPDATE-SuperSU-v1.51.zip; mv system/xbin/su /tmp/su
11) To create the extension part of the filesystem, run: dd if=/dev/zero of=/tmp/moreZeroes bs=4096 count=5118
12) To append the extension to the ELF, run: cat /tmp/system.elf /tmp/moreZeroes > /tmp/system.fixed
You now have the /system file system available to mount.
13) Make a temporary mount point: mkdir /mnt/systemfs
14) Mount the file system: mount -o loop -t ext4 /tmp/system.fixed /mnt/systemfs
15) Change directories to the mounted file system: cd /mnt/systemfs
16) Delete the old "su" binary: rm -rf ./xbin/su
17) Put ChainFire's "su" binary into place: cp /tmp/su ./xbin/su
18) Set the owner, suid bit and file permissions for the hacked "su" binary so that we can obtain root by running the binary: chown 0.0 ./xbin/su; chmod 06755 ./xbin/su
19) Now, we need to make the new system.img. Run: cd /tmp; make_ext4fs -s -l 2048M -a system /tmp/system.img /mnt/systemfs
20) You should now have a /tmp/system.img file. Copy this back to your Windows system to C:\system.img
[Windows]
21) Copy the FTF ROM file to "C:\Flashtool\firmwares\"
22) Launch FlashTool
23) Click the "lightning bolt" (flash) button.
24) Choose "Flashmode".
25) Select the FTF ROM file.
26) Ensure that Wipe is ticked for "DATA", "CACHE" and "APPSLOG".
27) Ensure that no exclusions are ticked.
28) Wait until FlashTool asks you to plug in your device in Flashmode.
[Xperia Z Ultra]
29) Ensure the USB cable is disconnected.
30) Power off your device fully (hold the power button and press "Power Off", then confirm).
31) Hold down the Volume-down rocker then plug in the USB cable. The LED should cycle through the prime colours very quickly. FlashTool should begin flashing. Be patient, this takes a while (enable debug logging prior to this if you want more verbose output.
32) When flashing is completed, unplug your USB cable and power on your device.
33) go to "Settings > About phone" and relentlessly tap "Build number" until you are informed that "You are now a developer".
34) Go to "Settings > Developer options" and tick "USB debugging".
35) Ensure the USB cable is disconnected.
36) Power off your device fully (hold the power button and press "Power Off", then confirm).
37) Hold down the Volume-up rocker then plug in the USB cable. The LED should remain illuminated blue.
[Windows]
38) Unpack the Android SDK to C:\adt-bundle-windows-x86_64-20130729 (or similar).
39) Open a command prompt (cmd.exe)
40) Change directory to the Android SDK platform tools: cd C:\adt-bundle-windows-x86_64-20130729\sdk\platform-tools
41) Execute: "fastboot.exe flash system C:\system.img". Be patient, this will take a while.
42) When the shell returns, execute: "fastboot.exe continue". You will probably see the battery icon, if you do, hold down the power button to turn your device on. If your phone doesn't start up, try unplugging the USB cable and powering on. If this doesn't work, hold down the volume-up rocket and power button until you hear the vibration motor pulse three times. After this, try powering on as normal. If it's still dead, something went wrong and I apologise. You'll have to reflash your phone with the FTF (see step 22). You will still have lost all of your data.
[Xperia Z Ultra]
43) Ensure the USB cable is disconnected.
44) Power off your device fully (hold the power button and press "Power Off", then confirm).
[Windows]
45) Launch FlashTool.
46) Click the "lightning bolt" (flash) button.
47) Choose "Flashmode".
48) Select the FTF file.
49) Ensure that Wipe is ticked for "DATA", "CACHE" and "APPSLOG".
50) Ensure that ALL exclusions are ticked. If you do not do this, you're going to have to go back to step 22.
51) Wait until FlashTool asks you to plug in your device in Flashmode.
[Xperia Z Ultra]
52) Hold down the Volume-down rocker then plug in the USB cable. The LED should cycle through the prime colours very quickly. FlashTool should begin flashing. Be patient, this takes a while (enable debug logging prior to this if you want more verbose output.
53) When flashing is completed, unplug your USB cable and power on your device.
54) Log in to Google Play.
55) Install SuperSU.
56) Start up SuperSU. You will probably be prompted to update the "su" binary - do so!
57) Install SuperSU to /system. Follow the instructions carefully.
58) Install Root Checker.
You should be done.
I hope people are successful with rooting their devices and enjoy the freedom that it brings. Anyone is free to copy, adapt or correct this tutorial as they wish; there is no licence and there are no conditions provided with this HowTo. It'd be nice to receive credit if this work is re-published or re-used, but that's not something I can control. Please respect the contributions of the original authors of the tools used within - all I did was string them together.
Be good to each other and enjoy.
ShALLaX said:
Guys, I've got it!
Click to expand...
Click to collapse
This is fantastic, thanks a lot
You should make a new thread in the "Xperia Z Ultra Android Development" section, and make a mod sticky it so people can easily find it
LordManhattan said:
You should make a new thread in the "Xperia Z Ultra Android Development" section, and make a mod sticky it so people can easily find it
Click to expand...
Click to collapse
This isn't really "Android Development," though. It's not even Linux development. It's just hacking/ manipulation at best.
Please release it, we really need root！
---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------
Very complicated!
ShALLaX said:
This isn't really "Android Development," though. It's not even Linux development. It's just hacking/ manipulation at best.
Click to expand...
Click to collapse
Well, if you go to a random device section here at XDA, you'll quickly realize that the rooting tutorials are in that section. Original Android Development is only for original development (Cyanogenmod, AOKP, kernels etc.), while the regular Android Development is for guides, kanged ROM's (Sony ROM's, kanged CM/AOKP, kernels etc.), so if you make an (somewhat) easy to follow tutorial, it should go there If you're in doubt, just PM a mod