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
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.
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
Important Update on Dec 2, 2011: Please do not update to Vizio Update 1.5. This will remove the root as well as disable this hack. According to user felixand in this Post.
I decided to start a new thread.
For those who would like to root, please see the instructions in the first post of this thread. This works for me.
http://forum.xda-developers.com/showthread.php?p=18805532
### Please use V3 version: DooMLoRD_v3_ROOT-zergRush-busybox-su.zip ###
Edited to add: If the above DooMLoRD method does not work you can use SuperOneClick. SuperOneClick can be found here: SuperOneClick. Download it and expand it. You will also need to download DooMLoRD_v3_ROOT-zergRush-busybox-su.zip. Expand it as well. Copy the new zergRush binary from the files directory of DooMLord into the exploits directory of the SuperOneClick folder. Then run SuperOneClick to root. Thanks to those who tried this method. See post by marvin02 below.
ACKNOWLEDGEMENTS:
I am not the original developer. I just helped test it. Please thank the developer of zergRush who fixed this code on the Vizio. Post by Ch4lky here.
http://forum.xda-developers.com/showthread.php?p=19396835
For those interested in the original source code of this exploit it is here.
Source code: https://github.com/revolutionary/zergRush
Binary: https://github.com/revolutionary/zergRush/downloads
Edited: Info about Vizio update 1.5 on Dec 2, 2011.
so to read into what you are posting - we need to follow directions and use the http://forum.xda-developers.com/attachment.php?attachmentid=784296&stc=1&d=1321435888
which is "DooMLoRD_v3_ROOT-zergRush-busybox-su.zip"
again, I am at work and can't download, but does above file contain the additional files called out in the script - namely busybox, su, and superuser.apk - if I were to guess from the filename, I would say yes...
to sum up:
place the 4 fileset(s) into a common directory under your adb setup - for consistency - we'll call this "files"
so we end up with
./files/zergRush
./files/busybox
./files/su
./files/Superuser.apk
is this about right?
Rich
Yes, that is correct.
okay - so the next step is the rewriting of the vold.fstab file to properly map the internal mount point and the external microSDHD card.
I remember seeing something on the Pandigital Novel forums that had suggestions on this topic...
Any ideas as to what the Vizio needs?
1) first so as not to break the current OS settings
2) then, to remap the mount point as needed so that software like APP2SD will behave correctly.
(looking forward to getting home tonight)
Rich
Wow, I was about ready to get rid of this thing. Will be giving this a go today and seeing about some dev support for roms and what not.
Kudos!
For me the doomlord script stuck waiting for the device.
I put the zergrush exploit into the exploits folder of SOC 2.2 (replace the one that is there) and it worked liked a charm.
Edit: SD Card mount point mod
If you are having issues rooting here is some troubleshooting:
To test your connection with adb:
After installing the drivers open a command prompt in the folder where the adb.exe is located at, make sure USB debugging is on and connect your VTAB to your computer.
Now type "adb devices" without the quotes and you should see:
D:\Android\tools>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
Your serial number here device
If this does not work then adb is not connecting to your VTAB.
For me the version of adb that is packaged with the doom script does not connect, but the version packaged with SOC 2.2 does. I copied the zergRush exploit from doom's script to the exploit folder on SOC 2.2 and used SOC. I am on WinXP Pro.
If you are using 64 bit windows make sure you install the drivers as an admin and run the doom script or SOC 2.2 as an admin.
Now...
Who feels like making a custom recovery?
I guess I'll start on CWM porting...
Maybe now that it has root, XDA should create a subforum for it?
blackcog said:
Who feels like making a custom recovery?
I guess I'll start on CWM porting...
Click to expand...
Click to collapse
This is great. Please post your progress. That will be very helpful.
majorpay said:
Maybe now that it has root, XDA should create a subforum for it?
Click to expand...
Click to collapse
We have to request it here.
http://forum.xda-developers.com/showthread.php?t=1301121
rprr said:
This is great. Please post your progress. That will be very helpful.
Click to expand...
Click to collapse
As embarrassing as it is, I'm actually having a terrible time getting a proper dump of the boot img. It seems to be corrupt every time I pull it
Once I get that much, the rest is a breeze. Probably 20 minutes, tops.
blackcog said:
As embarrassing as it is, I'm actually having a terrible time getting a proper dump of the boot img. It seems to be corrupt every time I pull it
Once I get that much, the rest is a breeze. Probably 20 minutes, tops.
Click to expand...
Click to collapse
May I ask how you are trying to dump the boot img?
Hey rprr, I just wanted to say I love you and offer you any females in my family for inpregnation.
sigeltek said:
Hey rprr, I just wanted to say I love you and offer you any females in my family for inpregnation.
Click to expand...
Click to collapse
Thanks, I showed that to my DW and she burst out laughing But, the real credit should go to the devs of zergRush and Ch4lky in particular. Please see my OP for the link to Ch4lky's post if you wish to "Thank" his post.
Same problem here.
The doomlord rooting kit did not work for me either. However, the superoneclick 2.2 with zergrush exploit copied into the exploit folder did work.
---------- Post added at 09:13 PM ---------- Previous post was at 08:52 PM ----------
Do get my device rooted runnning ADB under Vista (32-bit) I did the following:
1) First the Vizio provided ADB driver would not install. I instead did the following.
2) After making sure that any previous drivers were uninstalled from Device Manager including the Android Composite ADB driver. This driver would install for my VTAB successully but I was unable to communicate to the tablet using ADB. I deleted this driver and clicked on "delete the driver software". I also deleted the USB mass storage device and USB composit device.
3) I did a clean boot of the VTAB and then enabled the USB debugging.
4) I connected the VTAB to the USB port and this enabled "installing new hardware"
5) On my machine, I allowed it to search for the device driver and the key was to ensure that it would fail and close.
6) Go into control panel, device manager and you should now have other device named VTAB1008 with yellow highlight.
7) Right mouse click and select "update driver software"
8) then select "browse my computer for driver software"
9) then select "let me pick from a list of device drivers"
10) Select "ADB interface" and then select "Android Sooner ADB testing interface".
11) Once this driver was installed, I was successful in seeing the VTAB through ADB.
12) Install SuperOneClick version 2.2
13) Download the doomlord V3 toolkit and copy the zergrush file under the /files directory to the exploit directory under SuperOneClick (replacing the existing zergrush file)
14) Once this was done, SuperOneClick was successful
rprr said:
May I ask how you are trying to dump the boot img?
Click to expand...
Click to collapse
Actually, after several hours and a chat with a vizio tech, I've finally been able to diagnose it as a hardware malfunction.
On that note, my vtab has died. This is number two. I don't think I'll invest in a third. Sorry, guys.
blackcog said:
As embarrassing as it is, I'm actually having a terrible time getting a proper dump of the boot img. It seems to be corrupt every time I pull it
Once I get that much, the rest is a breeze. Probably 20 minutes, tops.
Click to expand...
Click to collapse
I do not now how to do what you are doing, but I found this guide. Don't know if it is helpful.
blackcog said:
Actually, after several hours and a chat with a vizio tech, I've finally been able to diagnose it as a hardware malfunction.
On that note, my vtab has died. This is number two. I don't think I'll invest in a third. Sorry, guys.
Click to expand...
Click to collapse
Sorry about your VTAB. May I ask again how you were trying to extract the boot.img?
marvin02 said:
I do not now how to do what you are doing, but I found this guide. Don't know if it is helpful.
Click to expand...
Click to collapse
Thanks. I did try that but still cannot get to the boot.img.
recently bought a Huawei ascend y200 and i want to root it!
Any advice gratefully received
in Germany done since may
http://www.android-hilfe.de/root-custom-roms-modding-fuer-huawei-ascend-y200/250421-how-root-werkseinstellung-systemupdate.html
root huawei ascend Y200
thank you very much! anyway is there any english version.
BR
Root Ascend Y200
Then you need to learn German in order to root this device.
your friend.
Come to me Sochhean, i will do it for you for free.
Sent from my Galaxy Nexus
In the German Board is now an english HowTo. I cant link to them, because i’m a new user @xda
Root Huawei Y200 Succesfully (ENGLISH)
sochhean said:
recently bought a Huawei ascend y200 and i want to root it!
Any advice gratefully received
Click to expand...
Click to collapse
Hi, I've successfully rooted my phone. I have a Huawei Y200.it might be easier if you waited for OneClickRoot do be launched maybe they have the device listed for auto flashing that does everything for you.
OneClickRoot: ==> I can't post links sorry ..New User, please search on internet..
But anyway, here's the batch file I think I uploaded it..
So its easy once you root it, but WARNING: DO NOT INSTALL CLOCKWORK MODE AGAIN THROUGH ROM Manager OR ANY SOURCE. (this might bring you into bootloop)
follow steps to use the batch file...
1- You need to do this on your phone: Allow USB Debugging and STAY AWAKE Function, STOP fastboot mode. Now Install ADB Drivers when connecting phone into computer via usb and debugging mode is on (you'll see a drive usually green on your computer, check for "drivers" inside driver folders and install windows drivers.
2- You need to install Android SDK : ==> New User, Can't post links, Search Android SDK..
navigate to default download location: " C:\Program Files\Android\android-sdk\platform-tools ", shift + right click inside the folder with nothing selected, and run command prompt from there. run following command "adb devices" and it should list a device number.
3- Now exctract the zip file in attachement and run these in order: -"adb.exe" then -"fastboot.exe" then -"root_v5.2.bat". It should say a succesfull message and ( as i remember) phone should reboot (if it states "reboot phone now" in cmd prompt). now you shoudl be rooted and see "SuperUser" application installed.
4- Check if you're properly rooted with a "rootchecker" market app. If App requested root access by SuperUser (ofcourse you'll tap Accept right?) and says you have proper root, you can now jump around and scream " I rooted my phone" like i did... You can now Install Link2sd app and enjoy free enternal storage since you've rooted your phone... Any Directions using Link2sd repost or you can search internet... One limitation is you can'r use swap (to increase your RAM ), and have to go through different ROM's. If rooted your phone succesfully please inform and on any questions about ROM switching...
Hi there.
The root process isn't so hard , bit the rom switch what would be important for me (not the method, i know that and i'we installed modified recovery its working...)
Went to hell and back @google to find any custom roms for this little fckr but besides the clean base rom and the ics por (whats not working for me) i could not find any other rom. Sorry my bad i have found one origonal stock rom too, bit besides theese do you know is there any other roms exists for u8655?
anyone try the above method?
is there anyone try the above method for English version?
An earlier version, on hungarian with english and german language included... worked perfect. Since 6 months.
MoH21 said:
Hi, I've successfully rooted my phone.
Click to expand...
Click to collapse
Hey, i know the file, that attached...
I'm happy that you understand my realy bad translation of this howto
tapped via my huawei mobilephone
1- You need to do this on your phone: Allow USB Debugging and STAY AWAKE Function, STOP fastboot mode. Now Install ADB Drivers when connecting phone into computer via usb and debugging mode is on (you'll see a drive usually green on your computer, check for "drivers" inside driver folders and install windows drivers.
2- You need to install Android SDK : ==> New User, Can't post links, Search Android SDK..
navigate to default download location: " C:\Program Files\Android\android-sdk\platform-tools ", shift + right click inside the folder with nothing selected, and run command prompt from there. run following command "adb devices" and it should list a device number.
3- Now exctract the zip file in attachement and run these in order: -"adb.exe" then -"fastboot.exe" then -"root_v5.2.bat". It should say a succesfull message and ( as i remember) phone should reboot (if it states "reboot phone now" in cmd prompt). now you shoudl be rooted and see "SuperUser" application installed.
4- Check if you're properly rooted with a "rootchecker" market app. If App requested root access by SuperUser (ofcourse you'll tap Accept right?) and says you have proper root, you can now jump around and scream " I rooted my phone" like i did... You can now Install Link2sd app and enjoy free enternal storage since you've rooted your phone... Any Directions using Link2sd repost or you can search internet... One limitation is you can'r use swap (to increase your RAM ), and have to go through different ROM's. If rooted your phone succesfully please inform and on any questions about ROM switching...
Click to expand...
Click to collapse
This procedure is for CWM, not for root.The root phone you must copy superuser.signed 3.0.7 on memory card, and boot phone in cwm, and install zip from sd card/choose zip from sd card/superuser.signed3.0.7/yes, and reboot system now, when is proces for install zip over.Then your phone is rooted, you think because write ROOT_V5.0.2 it is for root-NO, this for install CWM.
MoH21 said:
Hi, I've successfully rooted my phone. I have a Huawei Y200.it might be easier if you waited for OneClickRoot do be launched maybe they have the device listed for auto flashing that does everything for you.
OneClickRoot: ==> I can't post links sorry ..New User, please search on internet..
But anyway, here's the batch file I think I uploaded it..
So its easy once you root it, but WARNING: DO NOT INSTALL CLOCKWORK MODE AGAIN THROUGH ROM Manager OR ANY SOURCE. (this might bring you into bootloop)
follow steps to use the batch file...
1- You need to do this on your phone: Allow USB Debugging and STAY AWAKE Function, STOP fastboot mode. Now Install ADB Drivers when connecting phone into computer via usb and debugging mode is on (you'll see a drive usually green on your computer, check for "drivers" inside driver folders and install windows drivers.
2- You need to install Android SDK : ==> New User, Can't post links, Search Android SDK..
navigate to default download location: " C:\Program Files\Android\android-sdk\platform-tools ", shift + right click inside the folder with nothing selected, and run command prompt from there. run following command "adb devices" and it should list a device number.
3- Now exctract the zip file in attachement and run these in order: -"adb.exe" then -"fastboot.exe" then -"root_v5.2.bat". It should say a succesfull message and ( as i remember) phone should reboot (if it states "reboot phone now" in cmd prompt). now you shoudl be rooted and see "SuperUser" application installed.
4- Check if you're properly rooted with a "rootchecker" market app. If App requested root access by SuperUser (ofcourse you'll tap Accept right?) and says you have proper root, you can now jump around and scream " I rooted my phone" like i did... You can now Install Link2sd app and enjoy free enternal storage since you've rooted your phone... Any Directions using Link2sd repost or you can search internet... One limitation is you can'r use swap (to increase your RAM ), and have to go through different ROM's. If rooted your phone succesfully please inform and on any questions about ROM switching...
Click to expand...
Click to collapse
when you say RUN adb.exe fastboot.exe and root.bat what do you mean and where do i run them? ive installed platform tools and have done adb devices//my device is there. i extract the files and run them in cmd and double clicking and it doesnt reboot. i guess im having trouble with the .zip i know the files are good. any help :good:would be appreciated.
sketchscarz said:
when you say RUN adb.exe fastboot.exe and root.bat what do you mean and where do i run them? ive installed platform tools and have done adb devices//my device is there. i extract the files and run them in cmd and double clicking and it doesnt reboot. i guess im having trouble with the .zip i know the files are good. any help :good:would be appreciated.
Click to expand...
Click to collapse
sup
Sent from my H866C using xda app-developers app
Yo brow I'm trying to root the h866c. These directions may work but I think that the huawei mercury root directions will make this a functioning root check it out
Sent from my SPH-D600 using Tapatalk 2
AW: [Q] help for root huawei ascend Y200
German: http://www.droidwiki.de/Huawei_Y200/Root
...using tapatalk on my huawei honor smartphone
Since Firmware B898, the bootloader is locked. no way for using clockworkmod... No downgrade possible.
...using tapatalk on my huawei honor smartphone
det-happy said:
Since Firmware B898, the bootloader is locked. no way for using clockworkmod... No downgrade possible.
...using tapatalk on my huawei honor smartphone
Click to expand...
Click to collapse
Hi there
I did a research about this lock and i found a modified kernel what is capable of unlocking again the bootloader. (Claimed by the author, that it should solwe rhe issue)
Please tell me, since i did not upgraded the firmware due to the issue, could it be true?
Because i did not found any feedback from the users who tried it.
Can we count on another unlockibg method, or is this true that the bl can be unlocked via adb kerbel flash?
Thanks in advance.
I found an information on the german android-board
--> http://www.android-hilfe.de/huawei-ascend-y200-forum/414947-b898.html#post5670959
Fuchsteufel told us, that the recovery is working, but only with adb-commands, without any screen.
The solution is to flash an new version of the kernel and the cwm
fuchsteufel said:
für B898 Modified CMW
B898 kompatible Bootimages
Click to expand...
Click to collapse
Thank you.
Hi all,
EDIT
Thanks to techdudester on the second page, getting rid of the malware is now even easier!
Just flash the image he found here with the following procedure and you're good to go!
Instruction:
1. Flash the new ROM.
a. Get the ROM here . (Use this ROM only if you have a Venstar V140D tablet!)
b. Follow the linked tutorial to install the flash software and flash the new ROM on your device with: Phoenix Suit.
Voila, ready!
Enjoy your malware free tablet!
Tips and tricks. (or something...)
Get adb working (needed for all the other tricks down below):
1. Download the Google development tools (sdk) here and install them on your computer. I assume you have windows 7 installed during the rest of this tutorial.
2. Connect your device to your computer and make sure it is installed correctly.
a. Connect your device while its powered on via USB to your pc.
b. Go to Start, right click "My Computer" and select "Properties". Click "Device Manager".
c. Right click the Android device with the exclamation mark and select "Update Driver Software...".
d. Select "Browse my computer for driver software".
e. Select "Let me pick from a list of device drivers on my computer".
f. Keep "Show All Devices" selected and click Next.
g. Click "Have Disk..." and click "Browse..."
h. You can find the drivers in the "SDKInstallLocation"\sdk\extras\google\usb_driver directory and click OK. Replace SDKInstallLocation with the location that you selected during installation of the SDK.
i. Select the "Android ADB Interface" driver from the list and click Next.
j. Confirm installation by clicking on "Yes". Sometimes you also have to click on "Install" if a screen pops up to ask you again if you really want to install the driver...
k. Click "Close".
To use it:
Open a command prompt (in search type "cmd" followed by ENTER) and go to the following directory ""SDKInstallLocation"\sdk\platform-tools".
If you want a backup of your tablets system directory (highly recommended!) use:
"adb pull /system C:\system"
where C:\system is the target location on your local computer where you want the backup of the system directory.
Remove the update package (this doesn't work for updating the tablet, so, useless.)
adb remount
adb shell
cd system/app
rm Update.apk
exit
Remove the unwanted apps (dragonfire.apk etc)
adb remount
adb shell
cd system/preinstall
rm *
exit
If you would like to have your tablet in the correct time zone after factory reset, you will have to adjust the build.prop file.
First you need to get it to your pc so you can edit it:
in the command prompt window and at the same location as in the tutorial above type "adb pull /system/build.prop C:\temp\build.prop".
Just in case, make a copy of the build.prop in Windows Explorer so you always have the original file if something goes wrong.
Now you can edit the build.prop, but DON'T EDIT IT WITH THE WINDOWS NOTEPAD! Use Notepad++ or similar to edit the build.prop.
After you made the changes (and be careful here, you could end up with a tablet that does not want to boot up, solution further down below) you have to upload the file back to your tablet.
in the command prompt type:
adb remount
adb push C:\temp\build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
Don't forget the last line! If you do not chmod the file (set the correct permissions) your tablet will not boot up.
Changes in the build.prop:
Time zone:
Default time zone is "persist.sys.timezone=Europe/London"
you can change this to your locale time zone like "persist.sys.timezone=Europe/Amsterdam" (for the netherlands )
Search the internet for valid time zones.
Change the default language:
The default language is determined by these two values in the build.prop:
persist.sys.language=en
persist.sys.country=US
For dutch change them to:
persist.sys.language=nl
persist.sys.country=NL
and again, search the internet for valid language values.
Higher brightness after factory reset:
Add the following line to the build.prop file (at the top of the file)
ro.ph.def_brightness=225
You pushed the build.prop without changing the permissions:
No problem. Just connect your booting tablet to the PC, install the driver if its not installed correctly like explained in the tutorial, and then change the rights via adb. It's no problem that it's not fully booted!
in a command prompt in the adb directory:
adb remount
adb shell chmod 644 /system/build.prop
adb reboot
If you pushed a wrong non functioning build.prop, just use this method to push the original build.prop (you know, the copy you made ) back to the device (followed by setting the correct permissions of course).
Remove the (in my opinion) irritating boot sound:
adb remount
adb shell
cd system/media
rm boot.wav
exit
rom download
can you provide another way to download the rom file ,i cant seem to get the registration process to work
stevethesignguy865 said:
can you provide another way to download the rom file ,i cant seem to get the registration process to work
Click to expand...
Click to collapse
I have dropped it here. Hope this helps
I bought the same tablet for my daughter. She's (and so am I) suffering from a lot of annoying popups and ads.
Thanks for sharing your instructions here, very hard to find them!
Since I'm a complete newbie: one important question. When you flash the ROM, all of the apps (games) will be removed I guess?
Second question: can you put the stock rom on a different location? Both of the links (including Filedropper) don't contain any files...
Thanks!
1ce/ said:
I bought the same tablet for my daughter. She's (and so am I) suffering from a lot of annoying popups and ads.
Thanks for sharing your instructions here, very hard to find them!
Since I'm a complete newbie: one important question. When you flash the ROM, all of the apps (games) will be removed I guess?
Second question: can you put the stock rom on a different location? Both of the links (including Filedropper) don't contain any files...
Thanks!
Click to expand...
Click to collapse
Yes, all applications will be removed. As soon as you configure the tablet again with the same gmail account, it will probably start installing the applications and games automatically, but in game progress will be lost for most (not online) games.
I am re-uploading the file. Will update this post with the link as soon as it finishes
edit: upload finished, get it while its there LINK
BlueFlame said:
edit: upload finished, get it while its there LINK
Click to expand...
Click to collapse
Great! Thanks for the swift response. The file is about 307 MB. Is this correct? I'll start working on it, probably this weekend. I'll keep you posted.
1ce/ said:
Great! Thanks for the swift response. The file is about 307 MB. Is this correct? I'll start working on it, probably this weekend. I'll keep you posted.
Click to expand...
Click to collapse
Yes, thats correct. Once unpacked it will be around 520 MB.
Good luck!
Hi BlueFlame,
Thanks for the post. Is it possible to get the image uploaded again? Would be much appreciated.
Maylar said:
Hi BlueFlame,
Thanks for the post. Is it possible to get the image uploaded again? Would be much appreciated.
Click to expand...
Click to collapse
On request. You can find it here. (Adjusted link. Stored on Google Drive)
Thanking you. Very much appreciated.
Thank's for a fantastic procedure... Worked very well.
First step doesn't work for me: Phoenixsuit gives an error: 'Open Firmware failed'
with three possible reasons:
- firmware version is too old
- firmware format is broken
- firmware is used by other application.
Version used: 1.0.6
Firmware file: a33_599x_v11_1024x600_gc0308_2035_1015a.img
Any ideas?
1ce/ said:
First step doesn't work for me: Phoenixsuit gives an error: 'Open Firmware failed'
with three possible reasons:
- firmware version is too old
- firmware format is broken
- firmware is used by other application.
Version used: 1.0.6
Firmware file: a33_599x_v11_1024x600_gc0308_2035_1015a.img
Any ideas?
Click to expand...
Click to collapse
Is that the firmware that I provided?
If not, try to download it again.
If so, I think that your tablet has a newer firmware than this one. You could contact the seller of your tablet for the current (latest) firmware for this tablet.
If you get a newer firmware, please share
Image file invalid
Hi Blueflame,
I've tried to re-flash, but at some point i'm getting the message at livesuit V1.11 that the image file is invalid.
It's the 3rd time i have downloaded the file, what could be cause of this error?
Greetz Mike
mcwheelz said:
Hi Blueflame,
I've tried to re-flash, but at some point i'm getting the message at livesuit V1.11 that the image file is invalid.
It's the 3rd time i have downloaded the file, what could be cause of this error?
Greetz Mike
Click to expand...
Click to collapse
Not sure. Will upload it again this weekend just to be sure that it's not my uploaded image. (I will let you know once I've done that)
You can, on the other hand, contact the supplier (where you bought the tablet) and ask them for the latest version of the ROM. I would also be interested in that
BlueFlame said:
Not sure. Will upload it again this weekend just to be sure that it's not my uploaded image. (I will let you know once I've done that)
You can, on the other hand, contact the supplier (where you bought the tablet) and ask them for the latest version of the ROM. I would also be interested in that
Click to expand...
Click to collapse
Uploaded again! same link (just made it a new version in Google Drive).
Open Firmware failed - possible solution
1ce/ said:
First step doesn't work for me: Phoenixsuit gives an error: 'Open Firmware failed'
with three possible reasons:
- firmware version is too old
- firmware format is broken
- firmware is used by other application.
Version used: 1.0.6
Firmware file: a33_599x_v11_1024x600_gc0308_2035_1015a.img
Any ideas?
Click to expand...
Click to collapse
Try to put the image file in a directory without special characters (i.e. c:\temp). Worked for me.
wundabua
Te real FIX is In!
Ok, i have one of these allwinner, Venstar, "whatever", A33 D140v tablets. It had all the usual problems and more, because the first thing I tried, was to use the built in recovery to "restore to factory". This made things even worse, because after the recovery, I couldn't reach the Google authentication servers.
I am pro tech with 25 years in the trenches and I have to admit this thing really threw me for a loop, because I spent an entire day researching the solution, installing Android SDK, drivers, Phoenix Suit, Live Suit, etc. These were all very complicated "solutions" that took me exactly nowhere. I finally found the answer in a rather stupid Youtube video.
The REAL answer is actually very quick and easy compared to all these other recommended methods.
In the first place, model V140d image is only used for these infected tablets. The actual model is V11 and once you use the quick restore method I discovered, you will have a malware free V11 model. The whole secret to this method, is the fact that these units were designed to be quickly, automatically and completely restored in less that 5 minutes through the use of their built in micro SD slot.
Imagine that!
If you check your tablet that came new in the box as something other than V140d, the method I used will most probably not work for you.
Anyway, the quick method I discovered, can be seen on my own tech support site. To find it, Google: Just Call Techdude
Then click on the support link at the top of the page on my site and all will be revealed.
techdudester said:
Ok, i have one of these allwinner, Venstar, "whatever", A33 D140v tablets. It had all the usual problems and more, because the first thing I tried, was to use the built in recovery to "restore to factory". This made things even worse, because after the recovery, I couldn't reach the Google authentication servers.
I am pro tech with 25 years in the trenches and I have to admit this thing really threw me for a loop, because I spent an entire day researching the solution, installing Android SDK, drivers, Phoenix Suit, Live Suit, etc. These were all very complicated "solutions" that took me exactly nowhere. I finally found the answer in a rather stupid Youtube video.
Click to expand...
Click to collapse
Hi techdudester,
The combination "pro tech with 25 years in the trenches" and "very complicated "solutions"" sounds a bit strange.
But either way, a THANK YOU is in order!
The ROM you found works on my tablet (flashed yesterday) and so far so good. No popups and no unwanted application downloads!
I will adjust my initial post to incorporate this image.