Author Topic: MUCH W1 out soon! (Read 106272 times)

MementoMori · « **Reply #180 on:** December 09, 2014, 07:35:00 pm »

Quote from: Doggydogg on December 09, 2014, 05:34:20 pm

Quote from: MementoMori on December 09, 2014, 10:31:08 am
Hmm, I'm having a little bit of trouble with this pre-installed Super User app that was on here after my phone got unlocked. It doesn't seem to be giving permission to any root app. I tried to clear data but still can't seem to get it to function.

Any ideas?.

Thanks!.
Hi what did you have after root ? SuperSU or super user ? The reason I'm asking is because I've recently bought a mtk octocore phone and it had superSU installed and doesn't give proper root permission to titanium backup so titanium backup will not work , the easiest way around is to install super user by cwm put binary update zip on root of sd and update binary in recovery and its a winner
Ps. Do not fully unroot your device ! Just go into superSU settings and hit switch super user it will prepare for this , then install super user by cwm on playstore , update binary through recovery if it won't update for you then superSU will uninstall itself , if not you can just delete it

Hi,

Thanks for the reply. The device had SuperUser after unlock/root. Could you point me where to install CWM. I can't get to any point in SuperSu to have it update anything cuz can't get it any root access. Will CWM bypass this and install it?.

Thanks.

MementoMori · « **Reply #181 on:** December 11, 2014, 12:43:03 am »

Well I got KingUser running and able to give root access to apps. Would have preferred SuperSu but guess this will work. Wasn't sure which CWM to install and KingUser doesn't seem to be very easy to get rid of.

Cheers

twinkerz · « **Reply #182 on:** December 11, 2014, 02:55:41 am »

Can someone post the download link for the custom rom to me? thank you so much in advance!!

Nikojiro · « **Reply #183 on:** December 11, 2014, 10:04:36 am »

Quote from: MementoMori on December 11, 2014, 12:43:03 am

Well I got KingUser running and able to give root access to apps. Would have preferred SuperSu but guess this will work. Wasn't sure which CWM to install and KingUser doesn't seem to be very easy to get rid of.

Cheers

Hi, check out this tutorial: http://www.w0lfdroid.com/2013/11/How-to-Remove-Replace-VRoot-Chinese-superuser-with-SuperSU.html, I used this method to replace Kinguser with SuperSU, worked like a charm!

Cheers,

Nikojiro · « **Reply #184 on:** December 11, 2014, 10:12:02 am »

Hi,

I bought my W1 from diablotinbouky's shop (great shop, great service and cool dude, thanks!). I live in France and contribute to a french forum (http://www.open-consoles.com/) on open source gaming devices.

I am currently thoroughly testing the W1. There is another major french contributor to the forum, k0en, preparing a full review of the device.

The W1 has great potential, with good hardware and well above average build quality, but it is unfortunately marred by some critical software flaws. I woud like to submit a detailed bug report to the manufacturer, iReadygo, so please feel free to send me your own reports and observations so that we may consolidate these and show iReadyGo that there is interest in their device and have better chances that they consider a fix.

Cheers,

Niko

skelton · « **Reply #185 on:** December 11, 2014, 10:58:39 am »

Nikojiro, what about screen refresh rate? because if it's not 60 hz, then it's the fist thing they should fix. Also, what about joystick driver? Does it have a proper native joystick driver? Those are the essential things a gaming device should have.

Also, being a MTK6592, they should make a kitkat firmware instead of shipping it with Android 4.2.2

Nikojiro · « **Reply #186 on:** December 11, 2014, 11:20:14 am »

Quote from: skelton on December 11, 2014, 10:58:39 am

Nikojiro, what about screen refresh rate? because if it's not 60 hz, then it's the fist thing they should fix. Also, what about joystick driver? Does it have a proper native joystick driver? Those are the essential things a gaming device should have.

Also, being a MTK6592, they should make a kitkat firmware instead of shipping it with Android 4.2.2

Hi Skelton,

I have to confirm the screen refresh rate, I believe it is 60Hz. I tested a couple of emulators and didn't notice issues (Neo.emu, MD.emu, PPSSPP).

Unfortunately the joystick implementation is a total mess... Basically controls are split between 2 devices :

- mtk-kpd (keyboard device) handles dpad + A, B, X, Y, L, R, Start and Select
- the two analog sliders are a separate device (uinput? not sure)

The provided software mapping tools are not very good:

- KeyDIY which allows you to map whichever Android event code you want to dpad + A, B, X, Y, L, R, oddly Start and select can't be configured
- KeyAdapter is the touch mapper, but it locks the analogues so even if a game has onctroller support it never gets analog input... Plus you can't map Start and select either.

The worst part is the driver implementation, it ouputs stupid keyboard codes:

key 18 E
key 21 Y
key 30 A
key 31 S
key 45 X
key 48 B
key 56 LALT
key 100 RALT
key 103 DPAD_UP
key 105 DPAD_LEFT
key 106 DPAD_RIGHT
key 108 DPAD_DOWN

instead of

key 18 BUTTON_SELECT
key 21 BUTTON_Y
key 30 BUTTON_A
key 31 BUTTON_START
key 45 BUTTON_X
key 48 BUTTON_B
key 56 BUTTON_L1
key 100 BUTTON_R1
key 103 DPAD_UP
key 105 DPAD_LEFT
key 106 DPAD_RIGHT
key 108 DPAD_DOWN

which is what is configured in mtk-kpd.kl, but many native apps don't use the Android event layer... I a not very knowledgeable on native Android dev, this is what I understood so far.

A real shame...

I somehow managed to get things working for most gamepad compatible games by emulating a proper gamepad with Tincore Keymapper (while freezing away the default mappers, can't uninstall them as device is nand-protected), so there's a usable workaround, but I can't understand how they develop their software, or rather how they test it...

skelton · « **Reply #187 on:** December 11, 2014, 11:44:14 am »

Thanks for the info. it seems it doesn't have proper joystick driver, but a poor keyboard implementation. Well, using Tincore can be fixed, but it's something they should make properly in the driver.

for screen rate, you can use display tester app. If you use Broglia emulators make sure you are using them with frameskip 0. If screen is under 60 hz, ntsc games will run slow and if it's over 60 hz they should run a bit faster than normal with a jerky scrolling. though not all people notice this.

twinkerz · « **Reply #188 on:** December 11, 2014, 01:00:25 pm »

I have managed to flash using ka52's firmware update.zip. Thanks so much for that.

But now new apps that i install doesnt show up at all.. anybody facing this issue too?

Nikojiro · « **Reply #189 on:** December 11, 2014, 01:22:23 pm »

Hi there!

Following skelton's recommendations, I have backep up my ROM (Much Snail "european version" 5.6.24) and generated a CWM recovery img with MTKDroidTools. Flashed OK through MobileUncle Tools and booted alright.

I'm currently testing it and will let you know how it fares.

Nikojiro · « **Reply #190 on:** December 11, 2014, 01:38:27 pm »

Seems to work, I tested a backup and the generated files look ok. I'd be glad if someone else could look at geneated backups before I try a restore.

Here's the recovery image: https://drive.google.com/file/d/0BwcejGKSwuhHZ083RmRXQmhkNG8/view?usp=sharing

ka52 · « **Reply #191 on:** December 11, 2014, 02:15:33 pm »

Quote from: Nikojiro on December 11, 2014, 01:38:27 pm

Seems to work, I tested a backup and the generated files look ok. I'd be glad if someone else could look at geneated backups before I try a restore.

Here's the recovery image: https://drive.google.com/file/d/0BwcejGKSwuhHZ083RmRXQmhkNG8/view?usp=sharing

still loaded in chinese recovery

Nikojiro · « **Reply #192 on:** December 11, 2014, 02:20:45 pm »

How do you access your recovery? I use MobileUncle Tools to reboot to recovery, the key combination doesn't work for me.

diablotinbouky · « **Reply #193 on:** December 11, 2014, 02:40:21 pm »

Merci Nico pour le travail :-)

Are you sure it is a Chinese recovery? Not a manufactory program to test device?

ka52 · « **Reply #194 on:** December 11, 2014, 02:59:55 pm »

Quote from: Nikojiro on December 11, 2014, 02:20:45 pm

How do you access your recovery? I use MobileUncle Tools to reboot to recovery, the key combination doesn't work for me.

I can easily enter into the normal recovery by MtkDroidTools.
And when I press -Vol + Power, then I go to chinese recovery without any tools.
Please confirm.

Nikojiro · « **Reply #195 on:** December 11, 2014, 03:21:59 pm »

Quote from: ka52 on December 11, 2014, 02:59:55 pm

Quote from: Nikojiro on December 11, 2014, 02:20:45 pm
How do you access your recovery? I use MobileUncle Tools to reboot to recovery, the key combination doesn't work for me.
I can easily enter into the normal recovery by MtkDroidTools.
And when I press -Vol + Power, then I go to chinese recovery without any tools.
Please confirm.

Same for me, the chinese software is not the recovery, it seems to be some factory testing program, the first item launches a self-test for all onboard devices.

diablotinbouky could get confirmation, he has high profile native chinese staff on board

The actual recovery is hidden, it can only be accessed via an adb command, that's what MTKDroidTool does. Directly from the phone I use MobileUncle Tools "reboot to recovery", it works too.

Doggydogg · « **Reply #196 on:** December 11, 2014, 04:33:36 pm »

Quote from: MementoMori on December 09, 2014, 07:35:00 pm

Quote from: Doggydogg on December 09, 2014, 05:34:20 pm
Quote from: MementoMori on December 09, 2014, 10:31:08 am
Hmm, I'm having a little bit of trouble with this pre-installed Super User app that was on here after my phone got unlocked. It doesn't seem to be giving permission to any root app. I tried to clear data but still can't seem to get it to function.

Any ideas?.

Thanks!.
Hi what did you have after root ? SuperSU or super user ? The reason I'm asking is because I've recently bought a mtk octocore phone and it had superSU installed and doesn't give proper root permission to titanium backup so titanium backup will not work , the easiest way around is to install super user by cwm put binary update zip on root of sd and update binary in recovery and its a winner
Ps. Do not fully unroot your device ! Just go into superSU settings and hit switch super user it will prepare for this , then install super user by cwm on playstore , update binary through recovery if it won't update for you then superSU will uninstall itself , if not you can just delete it

Hi,

Thanks for the reply. The device had SuperUser after unlock/root. Could you point me where to install CWM. I can't get to any point in SuperSu to have it update anything cuz can't get it any root access. Will CWM bypass this and install it?.

Thanks.

Hi , not sure there is a cwm recovery for your device yet ? I ment cwm version of super user and if it won't update the binary then I can point you toward the update zip for the binary which you should be able to use through phones recovery

Nikojiro · « **Reply #197 on:** December 11, 2014, 05:16:51 pm »

Quote from: Doggydogg on December 11, 2014, 04:33:36 pm

Hi , not sure there is a cwm recovery for your device yet ? I ment cwm version of super user and if it won't update the binary then I can point you toward the update zip for the binary which you should be able to use through phones recovery

Wowowowow ... ok you can't flash CWM SuperSU without CWM, and flashing CWM SUperSU through the default recovery fails.

ka52 explained his method of rooting here: http://boards.dingoonity.org/android-devices/much-w1-out-soon!/msg117361/#msg117361.

If this doesn't work for you (it didn't for me), there's an alternative method :

1) Activate USB debugging by installing chinese 360 mobile assistant (Qihu360) app (APK provided on ka52's post)
2) Launch the app, slide from the upper left corner and flick the switch (see picture linked by ka52)
3) Download vRoot (MTKDroidTools can't root the W1) here http://www.mgyun.com/en/getvroot
4) Hook your W1 to your PC with an USB to micro USB data cable and fire up vRoot
5) Provided you have installed MTK USB drivers and Google ADB drivers (some google-fu will get you briefed), vRoot should pick up your W1 and you only need clicking on the big green button (the UI is full chinese but pretty much one click)
6) (optional) If you'd rather use SuperSU instead of Kinguser from vRoot as root manager, head here http://www.w0lfdroid.com/2013/11/How-to-Remove-Replace-VRoot-Chinese-superuser-with-SuperSU.html and follow the steps
7) You can safely uninstall the Qihu360 app, USB debugging will remain enabled.

Thanks to ka52 and diablotinbouky for steps 1-5, which I learned from them.

Now your W1 should be cleanly rooted.

!!!! IF YOU'RE FEELING BRAVE AND WANT TO TRY CWM READ BELOW !!!!
!!!! HUGE USUAL DISCLAIMER - ANYTHING BELOW IS AT YOUR OWN RISK !!!!
!!!! I CAN'T TAKE RESPONSIBILITY IF ANYTHING UNEXPECTED HAPPENS !!!!

Before anything else backup your ROM! Here's how :

1) Install MTKDroidTools (version 2.5.3)
2) Edit your build.prop (JRummyApps has a neat build.prop editor on Play Store), be sure to back up first. Set the prperty persist.sys.root_access to 3 instead of 0. This will allow root access to both apps and ADB. Save and reboot.
3) Connect your W1 via USB to the PC, start MTKDroidTools and wait for it to pick up your phone. Click the ROOT button on the bottom right to start a root adb shell. The square indicator on the bottom left will turn green.
4) Click the "backup " button and wait up. This will create a backup that you can later flash back with SPFlashTool if anything goes wrong. MTKDroidTools should also be able to flash this, but I've never tried.

Next CWM installation :

I provided a CWM recovery image, it's been generated by MTKDroidTools using my ROM backup and ithe auto CWM feature of MTKDroidTools (as explained here https://www.youtube.com/watch?v=u8aaL5qB82M, kudos to skelton for this tip).

It's pretty bleeding edge, all I have tested so far is backup.

I'll test restore soon, since the backup will allow to revert back to a safe point should anything go wrong. If anyone feels like repeating these steps and adding/correcting/building up upon them, pretty please do

Have fun!

ka52 · « **Reply #198 on:** December 11, 2014, 07:33:58 pm »

Port from 78Dian (v 5.6.24) for SP_flash_tool
all root from factory
https://yadi.sk/d/zUfibIMPdKE6B

MementoMori · « **Reply #199 on:** December 12, 2014, 03:45:37 am »

Quote from: Nikojiro on December 11, 2014, 10:04:36 am

Quote from: MementoMori on December 11, 2014, 12:43:03 am
Well I got KingUser running and able to give root access to apps. Would have preferred SuperSu but guess this will work. Wasn't sure which CWM to install and KingUser doesn't seem to be very easy to get rid of.

Cheers

Hi, check out this tutorial: http://www.w0lfdroid.com/2013/11/How-to-Remove-Replace-VRoot-Chinese-superuser-with-SuperSU.html, I used this method to replace Kinguser with SuperSU, worked like a charm!

Cheers,

Does it matter that I used KingRoot to get root. Will this method still work even though I didn't use VRoot?. Seems the end result for both methods is KingUser being installed.

Thanks.

EDIT: This worked

. I had to uninstall KingUser after (used TB) giving SuperSu root permission. Damn thing just didn't want to go away. Many thanks for the help.