[root] Wiko Fever [MT6753]

[manos78]

(Rooting guide at post #5 http://xdaforums.com/showpost.php?p=63803008&postcount=5)
(Stock ROMS at post #7 http://xdaforums.com/showpost.php?p=63939728&postcount=7)

Hi,

The new flagship from Wiko, the Wiko Fever, it's a great device. :good:

Here my research with it:

- MT6753 with 16GB ROM and 3G RAM
- Bootloader LOCKED (you can unlock it using one option in the developers hidden menu (you know how to enable it!) and then after reboot in the bootloader execute "fastboot oem unlock" (note, that selecting OK you will erase your data!).
:good:

- You can download an EXPERIMENTAL (=ALPHA) custom Recovery (CWM-Carliv) from here (you need to flash it to use it):
***removed***

- Also you can download the original DUMP of the boot.img and recovery.img from here:
http://www.sendspace.com/file/zy9q6g
:silly:

You can pack/unpack the recovery/boot using the CarlivImageKitchen selecting "normal" (not MTK) version!

 

[grandesballo]

..

 

[manos78]

Hi,

This device (Wiko Fever) is the same as Micromax Canvas 5 E481:
http://www.micromaxinfo.com/mobiles/smartphones/canvas/canvas-5-e481

Also, is identical to Blue Life ONE X:
http://www.bluproducts.com/index.php/life-one-x-2016
Follow the thread (with custom Kernels) at:
http://xdaforums.com/general/device-reviews-and-information/blu-life-one-x-2016-t3287428

Then the same firmware and rooting procedure will be shareable between both!

Here a great guide for Wiko Fever & Clones:
http://xdaforums.com/android/general/guide-clones-t3421539

 

[manos78]

Hi,

Here the scatter file for Wiko Fever Lollipop 5.1.

Two versions: a) extracted from stock update (scatter_stok); b) made by hand (scatter3).

 

[manos78]

Rooting GUIDE

Hi,
Good news: Rooting is done! :victory:

Here is the guide for rooting your Wiko Fever:

Warning (for newbies): First copy all indicated files to your SD card using your phone in normal state. Or use a PC and a SD reader for copy them when indicated.

1) Unlock bootloader:

1.1) Boot for first time your device. I recommend to NOT register/login/add Wifi/add accounts/etc., because the unlock process DELETES all your data in the device. So to go more fast, skip all, and go directly to SETTINGS. In section ABOUT DEVICE, enable the developer options with eight time picks over “Build number”. Then in SETTINGS/DEVELOPER OPTIONS, enable the option “OEM unlocking”. Then power off.

1.2) Power on the device in the BOOTLOADER mode (using ADB: "adb reboot-bootloader"). Execute in your computer the command “fastboot oem unlock”, say YES with “vol+” and “power” buttons. Then select reboot. This ERASES completely your device (factory restore), but the bootloader will be UNLOCKED! Two reboots needed.

2) Install custom Recovery:

2.1) Download from here the BETA 1 of CWM BETA 2 of CWM BETA 3 of CWM: http://www.sendspace.com/file/4g87bj
OR Download TWRP Beta 1 for Lollipop 5.1 from Hanuma: http://www.sendspace.com/file/y4jel8
(Original post: http://xdaforums.com/showpost.php?p=64543542&postcount=45)
OR Download TWRP 3.0.2.0 for Marshmallow from Hanuma: https://www.sendspace.com/file/9ms9zz
(Original post: http://xdaforums.com/showpost.php?p=67531723&postcount=217)

2.2) Boot in the BOOTLOADER mode (using ADB: "adb reboot-bootloader"). Then execute command “fastboot flash recovery recovery-custom-wiko-fever.img”; and then “fastboot reboot”.

3) Rooting:

3.1) Copy last beta of SuperSU v2.52 to your SD Card (file BETA-SuperSU-v2.52.zip).
http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

3.2) Boot in the CWM with “Vol+” and “Power” buttons.

3.3) Install ZIP from external-sd card.

3.4) Reboot and don’t select “fix root”, only “Yes”.

3.5) After boot, start SuperSU and configure it. Root done!


4) Xposed install:

4.1) Copy last release of Xposed Installer to your SD Card. Use files from here:
http://xdaforums.com/showthread.php?t=3034811
* xposed-v78-sdk22-arm64.zip
* XposedInstaller_3.0_alpha4.apk
* xposed-uninstaller-20150831-arm64.zip (in case of errors).

4.2) Boot in the Recovery, and install the framework (file xposed-v78-sdk22-arm64.zip).

4.3) After reboot, install the Xposed APK (file XposedInstaller_3.0_alpha4.apk).

4.4) Reboot. The Xposed framework is running.

Enjoy!

Notes: Before starting to root your device I recommend to do a full DUMP of the firmware using the SP Flash Tool. Use my handmade scatter file. :angel:

Thank you to all developers & supporters! :highfive:

 

[manos78]

ChangeLog:

- Beta 3: Fixed ADB shell with root uid.

- Beta 2: Fixed SELinux context support in ext4 filesystem. Full woking for rooting!

Note: If you like to use adb shell in recovery but an error like "exec '/system/bin/sh' failed: No such file or directory" then first mount /system partition.​

- Beta 1: Don't use this version, has a bug with SELinux contexts!

- Alpha(1,2,3): Pre-releases.

 

[manos78]

List of stock ROMs (for flashing with SPFlashTools) for Fever V8 (16GB/3GB) only:

- Lollipop v39 (last version until 5/2016): http://world.wikomobile.com/scripts/telecharger.php?id=140&type=MAJ

- Lollipop v22 (update 02.12.2015): http://fr.wikomobile.com/scripts/telecharger.php?id=105&type=MAJ

- Lollipop v18 (update 10.11.2015): http://fr.wikomobile.com/update-918-FEVER-4G

In case you need it!

List of stock OTA ROMs (for flashing with CWM/TWRP Custom Recovery):

If you have rooted your device, you can upgrade using these ROMs...

- Lollipop v39 (pre-rooted, with Xposed and ViPER Audio):
part 1: http://www.sendspace.com/file/d0js30 md5: e8706e0f5860e907fb8169856fc5e3b9
part 2: https://www.sendspace.com/file/iv4mnb md5: dd76926221ef40c872e4548a9b9e1f19
part 3: https://www.sendspace.com/file/6lfd18 md5: 838e6e608983a296611a284831fffd47
WARNING: At time this is untested! Give feedback with a post in the thread!
Decompress it using 7zip in your PC, copy files to your SD Card TWRP/Backup folder, and restore this backup with TWRP

Probably you want to use these versions!

 

[manos78]

Hi,

God news! I de-bricked my device... ****ing erroneous selinux context attributes in /system/lib64/ and /system/bin/ are the reason!

So, I don't futher need the stock SYSTEM partition. I'll continue with the rooting process... soon I'll publish it.

 

[djsolidsnake86]

this device can support cm12-cm13?

 

[manos78]

this device can support cm12-cm13?

I hope!
Maybe will be easy for some developer to port one CM13 firmware for MT6753 to this device.
The opensource package for this device isn't at time available. Sorry!

 

[cippaciong]

Verify that the bootloader is unlocked

Hi manos78, first of all thanks for this guide and all the efforts you are putting into this.

1.1) Boot for first time your device. I recommend to NOT register/login/add Wifi/add accounts/etc., because the unlock process DELETES all your data in the device. So to go more fast, skip all, and go directly to SETTINGS. In section ABOUT DEVICE, enable the developer options with eight time picks over “Build number”. Then in SETTINGS/DEVELOPER OPTIONS, enable the option “OEM unlocking”. Then power off.

1.2) Power on the device in the BOOTLOADER mode. Execute in your computer the command “fastboot oem unlock”, say YES with “vol+” and “power” buttons. Then select reboot. This ERASES completely your device (factory restore), but the bootloader will be UNLOCKED! Two reboots needed.

I just followed these steps to unlock the bootloader and I think everything worked as expected. Anyway, is there a way to be 100% sure that the bootloader is unlocked before (and without) flashing the recovery?

Thanks again!

 

[Profeta11]

hi guys, i followed the guide and all worked also with the last update

 

[manos78]

I just followed these steps to unlock the bootloader and I think everything worked as expected. Anyway, is there a way to be 100% sure that the bootloader is unlocked before (and without) flashing the recovery?

After the command "fastboot oem unlock" If you see the Warning message and the device is rebooted and formating the data partition, then you have for sure unlocked the bootloader.

But if you like to check it: "fastboot getvar all"; then find for the status of bootloader.

 

[oile]

Thank you manos78!!
The only way of rooting is unlock bl->cwm->flash superSU? or is it possible to flash just a prerooted system.img keeping bootloader locked?

Also, have you noticed that sdcard0 become sdcard1 when inserting a sd card (wich replaces sdcard0) ? is there a way to avoid that? Choosing "internal memory" as default storage didn't avoid apps writing their datas on the slower SD :/

 

[cippaciong]

But if you like to check it: "fastboot getvar all"; then find for the status of bootloader.

Unlocked
You have been really helpful, thank you!

 

[manos78]

Thank you manos78!!
The only way of rooting is unlock bl->cwm->flash superSU? or is it possible to flash just a prerooted system.img keeping bootloader locked?

Also, have you noticed that sdcard0 become sdcard1 when inserting a sd card (wich replaces sdcard0) ? is there a way to avoid that? Choosing "internal memory" as default storage didn't avoid apps writing their datas on the slower SD :/

Hi,

I try to boot the custom recovery image with fastboot without flash and it fails. So for rooting, at time, the only way is: unlock->flash custom recovery->install superSU. But after that, you can try to: flash stock recovery->re-lock, if you like (not tested by me! Be carefull!). However, with the custom recovery you can do full backups, so I recomend it. The side effect is that you can't upgrade with OTAs.

Another option is use the original stock firmware and readback/flash the SYSTEM partition and modify it using an external computer (modify the IMG). But, this solution is quite complex.

Finally, related to the SD-CARD. The "internal memory" is only for "media", not for Apps. I use one 64GB SD on my Fever and I store in it: photos, music & ISO/IMG images. Any other data is in the internal storage (emulated sdcard). Also, I "installed" (=moved) some huge games (>100MB) to the sdcard (the real SD); and I store my Google Kiosk and Music files on the sdcard (also the real SD). Please, don't care about the sd storage, is working right on the stock firmware.
:good:

 

[oile]

Actually I could inject root files into the system.img can anybody provide it? Do you know if bootloader only accepts images signed by manufacturer? In that case, a modded image can cause a security error. But I don't think it is so complicated on mediatek, given the fact that is possible to flash a custom recovery without any security check using flash tool.

About sd, I don't think I get what you mean by "media". System needs a "sdcard0" for a lot of apps like Sygic and Whatsapp and games like real racing. If sd card replaces it being sdcard0 instead of sdcard1 everything seems screwed to me: these apps are forced to write and read from a very slow memory (even a class 10 is way slower than internal memory)

 

[manos78]

About sd, I don't think I get what you mean by "media". System needs a "sdcard0" for a lot of apps like Sygic and Whatsapp and games like real racing. If sd card replaces it being sdcard0 instead of sdcard1 everything seems screwed to me: these apps are forced to write and read from a very slow memory (even a class 10 is way slower than internal memory)

In stock Fever ROM:

/sdcard --> the REAL SD Card (the Sygic data, Google Music & Kiosk, etc. are in the REAL SD Card)
/storage/sdcard1 --> the EMULATED SD (internal memory)

Then you can use the SD as real one with Apps, and use alternative (emulated) when you like. The "media" Apps can use sdcard0 (real) or sdcard1 (emulated).

Related to this sentence: "hese apps are forced to write and read from a very slow memory (even a class 10 is way slower than internal memory)"
Please, remember: both, external memory and internal memory, have LIMITED life (write operations). Then, what you prefer: write more on the internal and not interchangable memory, or in a removable and inexpensive memory?
Please, think well! :angel:
Also, FYI, in my current Wiko Fever I use a 64GB SDXC UHS-II, far away than a simple class 10 (x15 reads/x30 writes).

 

[cippaciong]

Actually I could inject root files into the system.img can anybody provide it? Do you know if bootloader only accepts images signed by manufacturer? In that case, a modded image can cause a security error. But I don't think it is so complicated on mediatek, given the fact that is possible to flash a custom recovery without any security check using flash tool.

I'm quite accustomed to filesystems and partitions since I've been using Linux for many years but I've got almost zero experience with Android internals, so please help me to understand if I got this right.
Now that I have unlocked the bootloader I can (potentially) flash "any" .img file on "any" partition (given that I'm using the right file on the right partition), right? So I could dump my system partition, put the su binary inside and then reflash it in fastboot mode?
I'm sorry if my questions might sound dumb to you but I'd like to start tinkering with Android a bit more but having a hard time finding a good starting point.

 

[manos78]

Now that I have unlocked the bootloader I can (potentially) flash "any" .img file on "any" partition (given that I'm using the right file on the right partition), right? So I could dump my system partition, put the su binary inside and then reflash it in fastboot mode?

Hi,

Unlock bootloader is for booting NON-SIGNED kernels (the boot or the recovery), not for partitions.

When you unlock the bootloader you can install (or boot) a CUSTOM recovery. In the custom recovery you can mount and modify the SYSTEM partition (where is included the root).

For "flash" or "dump" the internal memory of the device, if it's using a MTK cpu (like the Fever) then you can use SP FLASH TOOL. You have the scatter file in this thread!