yashsingh1/xdaforums huggingface dataset:
[Device Reviews and Information] psychoTR2:
I noticed that the battery doesn't drain as fast when it hits 15%. And it goes into deep sleep now. Looks good so far, but I can't say anything conclusive yet. My USB cord crapped out on me, so I haven't charged it to 100% and calibrated it, so I'll keep you guys posted as I test it tomorrow.

Performance wise, I notice a lot less jitter when I pull down the quick settings, so for me, that alone is worth testing this kernel out!
[Device Reviews and Information] juancollado2003:
people interested on better battery life should follow this http://xdaforums.com/showthread.php?p=67026383
[Device Reviews and Information] donedos:
Now it's working... Thank..!?
[Device Reviews and Information] Teblakuda4o4:
Can anyone who's changed their boot animation provide a link to a dark one. The default boot animation is too bright and I feel like its just a waste of battery life
[Device Reviews and Information] TheRealShani:
Got mine from this list. I used ROM Toolbox to install the animation. The one that looks like a Poke Ball should work for you.

http://xdaforums.com/android/themes/bootanimations-50-flashable-t3059659
[Device Reviews and Information] Teblakuda4o4:
Thanks.. . I'll check them out
[Device Reviews and Information] H4MM3RD0WN:
Any wizards out there know if I use TWRP in read-only mode to root/flash supersu if I'll be able to take OTA's? Root is systemless and in read-only mode TWRP won't stick after reboot, so with no modification to /system, I should be able to take an OTA upgrade right? And if I read-only TWRP it won't stay after reboot but will root stay without custom recovery installed? I know after an OTA I'd have to do the re-root process, I just want to make sure I'll have root and be able to take OTA.
[Device Reviews and Information] DevBurrito:
I'm pretty sure that if you're rooted, you cant OTA. But do not fear, there are still wayz:

1. Make a NANDroid backup

2. Download attached stock recovery (unzip the zip file DO NOT FLASH)

3. Flash unSU.zip. download: https://www.androidfilehost.com/?fid=24269982087014111

4. Boot to bootloader and flash stock recovery.

5. OTA!!

6. Boot to bootloader (power + vol down)

7. Reflash TWRP

8. Flash SuperSU

9. Reboot!!
[Device Reviews and Information] H4MM3RD0WN:
I appreciate the tutorial. The #2 post in this thread is the root process and I was earlier told its a systemless root. What I was thinking of doing was flashing SuperSU thru TWRP (as in the directions) but using TWRP in "read-only" mode which would let me flash SuperSU but wouldn't keep TWRP, leaving me with stock recovery. I'm hoping that would leave me with root, but with stock recovery and an unmodified /system so taking an OTA is simple. If its not I'll follow the steps you gave me.
[Device Reviews and Information] edrock200:
FYI for those that want spflashtool the links off of the page linked in the original post didn't work for me but I found the tool here:

*edit* I'm not allowed to post links yet. Google sp-flash-tool-v5.1532.00.zip

The first link should be to a com site named androidmtk. That worked for me.
[Device Reviews and Information] elbastardo1:
You can backup the stock recovery (or just download the whole original firmware) flash TWRP, flash supersu and then flash stock recovery back.

There's no way to boot TWRP or custom recovery without flashing it first.

Keep in mind that, no matter if you have stock recovery, you will not be able to install system updates if you are rooted, even if you try to flash it with stock recovery.

It happened to me. Used the "full unroot" command from chainfire's superSu. Flashed stock recovery back and updated, Then flashed custom recovery and flashed superSu once again.
[Device Reviews and Information] joeybear23:
I flashed this, but my Kernel version is still showing up as the stock kernel...
[Device Reviews and Information] black_host:
thank you

thank you
[Device Reviews and Information] H4MM3RD0WN:
This might be a stupid question, but would I flash stock recovery thru TWRP or ADB
[Device Reviews and Information] elbastardo1:
Adb
[Device Reviews and Information] juancollado2003:
It is a stock kernel modified
[Device Reviews and Information] ToucanRask:
So I had this installed for the whole day today. It was working perfectly fine when all of a sudden my auto rotate stopped working. I flashed back to the original modified kernel and it's back to normal now.
[Device Reviews and Information] juancollado2003:
What model is you phone?
[Device Reviews and Information] Deznuts:
can someone please creat a full rom dump of blu one x 2016 provide the link...
[Device Reviews and Information] ToucanRask:
What do you mean by model? It's the Blu Life One X. Or more specifically L0070UU.
[Device Reviews and Information] juancollado2003:
Well, don't know why happens that
[Device Reviews and Information] DevBurrito:
What partitions do u need
[Device Reviews and Information] juancollado2003:
Well guys I'm trying to get all 3g bands, now I can switch between 3g bands but I can't have them together....... Yet
[Device Reviews and Information] Deznuts:
everything ..like a stock rom that you download from the internet
[Device Reviews and Information] juancollado2003:
Well guys I achieved to unlock wcdma900 on BLOX, now I have BLOX and Wiko bands toguether, just restore this nvdata with twrp, https://mega.nz/#!sRpUkYiY!foQ-YlQypebWtpdeJZ58Bk9QzwmUGOZbMzX7xVMDtnA

To unlock wcdma850 and lte on Wiko just flash this https://mega.nz/#!8Jh1VARR!vH-Xm-yJpn1dmPDI_8lO2EuKAlww-KFsIlWA4ufZO0Y

It's a TWRP backup so put the folder on your TWRP folder
[Device Reviews and Information] DevBurrito:
Simply run commands:

adb shell
su
dd if=/dev/block/[partition label, looks like mmcblk0p20] of=/sdcard/[partition name eg: system].img

Get partition labels from: http://xdaforums.com/general/device...lu-life-one-x-2016-porting-resources-t3385109 :highfive:
[Device Reviews and Information] SCrid2000:
http://xdaforums.com/showpost.php?p=65064353&postcount=128
[Device Reviews and Information] Higorp:
Wiko Fever Special Edition with Android Marshmallow

Hi guys, the Wiko launched a new Fever Special Edition That It's the same phone, but comes with 1GB more RAM and 32GB of storage and with the Android Marshmallow so it's a great news because the Wiko offer the rom of their devices

Device sales started in this week then this rom not available yet, but should soon be available.

I can't link, but these are the rom page and the Fever Special Edition page

fr.wikomobile.com/maj.php?telephone=1215

fr.wikomobile.com/m1215-fever-special-edition
[Device Reviews and Information] H4MM3RD0WN:
Any way you can link the kernel / give a tut for the process? never used sp flash tool and never installed a kernel :eek:

EDIT: nevermind, I found it. trying this shortly.
[Device Reviews and Information] disleyxc:
Does anyone with the modified kernel get slower charging times now?
[Device Reviews and Information] juancollado2003:
First charge takes time before flashing the kernel, it can even get stuck on some battery level, keep testing
[Device Reviews and Information] elbastardo1:
Tested custom kernel. Much, much better battery life. One observation, present in both stock and custom kernel.

I notice that if I start using the phone right after unplugging it the battery drains relatively fast (around 1% per minute) until it reaches the 85%. Then it drains more slowly (around 3-5 minutes per 1% of screen time). However if I plug it back to the charger and let it hit 100% and unplug it, it will drain at around 1% for every 3-5 minutes of screen time.

Also if I unplug it but don't use it for a while (10-15 minutes) it will also drain at 1% for every 3-5 minutes of screen time.
[Device Reviews and Information] juancollado2003:
Use better battery stats to know what is draining your batt, also follow the guide to get better battery life
[Device Reviews and Information] disleyxc:
I've noticed much better OST as well but I've also noticed that it's taking much longer than usual to charge ever since I flashed the kernel

---------- Post added at 08:35 AM ---------- Previous post was at 08:17 AM ----------

Guys this has major implications for us I think the developers out there who managed to port the Eragon ROM might be interested in this as it could lead to a potential port of Android M since they are the same phone
[Device Reviews and Information] SCrid2000:
The Eragon port isn't really a port, per se, as it is the exact same system OS with the original BLOX kernel.

The hope is that a port isn't actually needed for the new fever OS, and that the OS will simply run on the BLOX.
[Device Reviews and Information] Deznuts:
see the thing is i dont own a BLOX..i own mmx canvas 5 and i want to install blu stock rom to try out some custom rom
[Device Reviews and Information] DevBurrito:
I can try to make that for u :D PM me

---------- Post added at 02:35 PM ---------- Previous post was at 02:32 PM ----------

Although I have managed to edit some core files to allow baseband, and am in the process of debugging before upload. :highfive:
[Device Reviews and Information] disleyxc:
SMS Problems and MTK Engineering Mode

Hey guys. So I am unable to send texts when over 4G and its infuriating. This only happens when the SIM is in the second slot though (the idiot at the store activated it in that slot) and I can send texts when on 4G when the SIM is in the first slot. I messed around a bit with the MTK settings and have been unable to return the functionality. I am using MetroPCS as my carrier and was wondering if anyone can help me fix this problem. Any help is appreciated. Thanks in advance.

Edit: I also used BADMOFO'S backup in order to try and reset my phone but no luck
[Device Reviews and Information] idontkn1:
Why does it matter what slot it was activated in? Just move it from slot 2 to slot 1. I see no reason why what slot it's activated in would matter unless MetroPCS locks the sim to a slot, I've never used them. I know that I've been able to swap a Cricket, At&T and T-Mobile sim between both slots without any issue.
[Device Reviews and Information] elbastardo1:
What do you mean activate it in that slot? You can receive calls in slot 2 but not in slot 1? :eek:
[Device Reviews and Information] disleyxc:
Yeah for MetroPCS they lock the SIM to a IMEI number on the phone so a particular SIM slot
[Device Reviews and Information] juancollado2003:
You can swap imei using many tools, you also can have 3g on metro using this TUT, http://xdaforums.com/general/device-reviews-and-information/tut-mt6753-blu-life-one-x-bands-t3389479
[Device Reviews and Information] donedos:
I agree with your observations... It drains fast when using it.

---------- Post added at 01:16 AM ---------- Previous post was at 01:11 AM ----------

Have you fix the camera problem? I have here 4 rom but with camera camera problem..
[Device Reviews and Information] DevBurrito:
Nope, next will try to replace libcamalgo.so, though would rather not do that...
[Device Reviews and Information] donedos:
​

I managed to boot the UMI Rome ROM in our device and its front facing camera is working with flash. But the rear camera is still the problem. I have no time debugging this problem.
[Device Reviews and Information] DevBurrito:
Full port or boot.img replacement?
[Device Reviews and Information] FernandoRocker:
Amazon. I'm going to ask for a replacement.
[Device Reviews and Information] feegus:
Awesome work fellas, I wonder about losing possible OTA updates as well but I can't run any phone without AdAway so root is a must :)
[Device Reviews and Information] SCrid2000:
I wasn't able to get it, sorry :( Didn't realize that new bootloaders don't allow you to boot a recovery without flashing it. Tried a few other things, but ultimately just flashed the custom recovery.

I did flash the stock Wiko Fever recovery and it worked fine though, its possible we'll be able to use that to update.

Now, that being said, if someone wants to try flashing a prerooted system image and backing up the stock recovery, I can get you a prerooted system image.
[Device Reviews and Information] gruiz3:
What would the process involve?
[Device Reviews and Information] Bad_MOFO_33:
I am still unable to boot into stock Wiko recovery. Can you upload the one that worked for you(maybe my downloads are getting corrupted) Are you flashing with an app like flashify? Or flashing IMG from twrp or fastboot command?
[Device Reviews and Information] rogersa2k:
I have flashed CWM and TWRP many times as explained in the OP.

- Aaron
[Device Reviews and Information] Bad_MOFO_33:
I am able to flash twrp and cwm without any issues. My issue is trying to revert back to the stock recovery.
[Device Reviews and Information] rogersa2k:
Whoops, misunderstood you. No idea how to do that yet. :(

- Aaron
[Device Reviews and Information] SCrid2000:
It would involve me backing up my system image using the instructions at http://xdaforums.com/showthread.php?t=2450045, and some brave soul who hasn't flashed a custom recovery flashing it via fastboot "fastboot flash system system.img" - I'm not certain it would work and might cause a bootloop, although I suppose worst case scenario you could boot back into the bootloader, flash the custom recovery, and then flash a different image? TBH I haven't ever tried that exact process.

I used fastboot to flash the recovery from http://fr.wikomobile.com/update-918-FEVER. I uploaded just the recovery to mega if you don't want to download the entire Wiko image: https://mega.nz/#!Us8B2aIQ!Bomkf3vnbVK_hWnwp0b46JVOCj7wsMKOoXuufyCGFrg
[Device Reviews and Information] Bad_MOFO_33:
That worked, thanks.:good:
[Device Reviews and Information] clu1688:
Need help. I have tried many times using the Amazon Watcher's method, everytime I turn on the cellphone "Vol Up + Power", my windows 7 shows a pop "installing device driver software...." and then says "Device driver software was not successfully installed". When I clicked on details, it shows "MTP USB Device....Device unplugged".

So I downloaded the MTP USB driver from Microsoft, installed, reboot, still the same warning message.

my ADB command doesn't see my device and has no effect. It appears somehow I don't have correct driver installed.

By the way, I did install the Kindle driver from the 1st post here.

Any suggestions? Very much appreciate any input,
[Device Reviews and Information] SCrid2000:
What OS are you running?

Windows 10 didn't need me to install any drivers (I already had ADB and Fastboot installed of course). I would suggest uninstalling both the kindle and mtp drivers and rebooting your PC.
[Device Reviews and Information] rogersa2k:
Yeah, sorry. I have not tried this with Windows 7 or 8. Also, as I mentioned in the OP, on my Windows 10 desktops I already had the Kindle driver installed and the BLU Life One X 2016 just worked. If someone wants to post a link to known-working MediaTek drivers I'll add it to the OP.

- Aaron
[Device Reviews and Information] rogersa2k:
I would but since I already have CWM I cannot help. Do you have any experience with the SP Flash Tool? Have you created a scatter file before? Can you make one for the BLU Life One X 2016 if the one from Wiko Fever thread isn't 100% correct?

Thanks!

- Aaron
[Device Reviews and Information] SCrid2000:
I had no experience with any MTK devices before the Blu. My understanding (from the Wiko thread and PMing the OP of that one) of a scatter file is that it lists the partitions as they exist on the device. The Fever scatter is in that thread is attached, and below is the partition map for Blu (for some reason MTK tool won't create a scatter. Weird.), and you can see that the two are different:

emmc_p1: 00000400 00001800 "proinfo"

emmc_p2: 00001c00 00002800 "nvram"

emmc_p3: 00004400 00005000 "protect1"

emmc_p4: 00009400 00005000 "protect2"

emmc_p5: 0000e400 00000400 "lk"

emmc_p6: 0000e800 00000400 "para"

emmc_p7: 0000ec00 00008000 "boot"

emmc_p8: 00016c00 00008000 "recovery"

emmc_p9: 0001ec00 00004000 "logo"

emmc_p10: 00022c00 00005000 "expdb"

emmc_p11: 00027c00 00000400 "seccfg"

emmc_p12: 00028000 00001000 "oemkeystore"

emmc_p13: 00029000 00003000 "secro"

emmc_p14: 0002c000 00004000 "keystore"

emmc_p15: 00030000 00002800 "tee1"

emmc_p16: 00032800 00002800 "tee2"

emmc_p17: 00035000 00000800 "frp"

emmc_p18: 00035800 00010000 "nvdata"

emmc_p19: 00045800 00012800 "metadata"

emmc_p20: 00058000 00600000 "system"

emmc_p21: 00658000 000c8000 "cache"

emmc_p22: 00720000 01633c00 "userdata"

emmc_p23: 01d53c00 00008000 "flashinfo"

none: 00000000 00000000 bmtpool
[Device Reviews and Information] SCrid2000:
Just had an idea for restoring stock recovery - might or might not work.

Has anyone tried running /system/etc/install-recovery_original.sh? I'm guessing that the original one is supposed to be the stock one, and the recovery renames the original and replaces it with one that won't try to restore the recovery using /system/recovery-from-boot.p (which would explain why the custom recovery sometimes needs to be flashed multiple times perhaps?). I can't do it because I've flashed recovery multiple times, so the backup is the one that I suspect is installed by the recovery. That being said, I might have a backup on my home pc of the original install-recovery.sh from when I did an adb pull right when I got the blu.

Edit: might also be able to get it from the Wiko Fever system.img.

Edit 2: There's a backup of the install-recovery script in the bin folder (which is good, because the Blu recovery has a different hash than the Wiko one). I was able to run it via the terminal and it flashed the stock recovery using the recovery-from-boot.p. I extracted the stock recovery using "dd if=/dev/block/mmcblk0pxx of=/sdcard/recovery.img" and uploaded the stock recovery to Mega (see post below). I tested it out by flashing CWM and then reflashing the stock recovery (both using fastboot).

Link: https://mega.nz/#!do0TSBpR!DT3_q-vLX2hd3whArpiHsCI40DtD2zxJ0rGWkEu20bQ
[Device Reviews and Information] gruiz3:
Windows 7 driver for mtk

I followed these for the driver on windows 7 and bing bang boom! Done!
[Device Reviews and Information] bobloadmire:
Any word on Marshmallow?
[Device Reviews and Information] SCrid2000:
Here is the stock recovery: https://mega.nz/#!do0TSBpR!DT3_q-vLX2hd3whArpiHsCI40DtD2zxJ0rGWkEu20bQ

If you're interested on how I got it, see http://xdaforums.com/showpost.php?p=64822873&postcount=56.
[Device Reviews and Information] aestylis:
BLU is rather lacking when it comes to updates. What I have read is that BLU is promising an update by end of Q1 (April).
[Device Reviews and Information] donedos:
Its just the system..flashed thru spflashtool, edited the build.prop and fixed baseband/imei.
[Device Reviews and Information] DevBurrito:
Kk I'll tinker with that. Hopefully fix the back cam
[Device Reviews and Information] mantarkus:
Hey guys

Just noticed a couple of bugs on my device (stock, no root).

First, the ringtone resets to the default ringtone no matter what I select. Same with the txt notification, it will play a few times but it goes back to the default.

Second, when I select to display contacts from my google accounts, it displays contacts from Google and SIM card. Any other option does not display anything.

The first one is a known bug, but the second one not sure. Any work around you might know of?

Thanks

David C.
[Device Reviews and Information] juancollado2003:
Guys, days ago I flashed my BLOX with Wiko firmware, I noticed I had data connection icon on both sims, can another person confirm that?
[Device Reviews and Information] DevBurrito:
Do you mean the modified system.img or full os?? :good:
[Device Reviews and Information] juancollado2003:
Using the https://mega.nz/#!05JwwZTQ!KRaw0awsubo7uKCg5mkAK94st9G-HayaZCaPIViVFkU Blufever Rom
[Device Reviews and Information] SCrid2000:
Is that the most recent v39 fever system image?

It's worth noting that the boot image and possibly a few others for the BLOX are newer than the original firmware (which is what badmofo was kind enough to pass to us).
[Device Reviews and Information] juancollado2003:
Are we talking about data connection icon on both sims or someone changed the channel?
[Device Reviews and Information] edjocute:
Tried this and managed to swap between utms 1/2/5/8 or 1/2/4/5 (as verified from engineering mode). Is there anyway to unlock and swap the LTE bands as well using nvdata?
[Device Reviews and Information] juancollado2003:
Sure but you will lose imei so will have to fix it
[Device Reviews and Information] dubhlinn:
still no fix for installing custom recovery????
[Device Reviews and Information] juancollado2003:
Follow the guide, everyone here have twrp installed
[Device Reviews and Information] donedos:
The problem you are facing is in the APN settings... Create a new APN and make sure its correct. Wiko's default apn has proxy that causes the problem.
[Device Reviews and Information] juancollado2003:
What I'm saying is, with BLOX I can't have data connection on both sims at same time but on Wiko I can
[Device Reviews and Information] mantarkus:
Hey guys

Kingoroot worked for me, checked root status with various root checkers. So I have two questions:

First.- What bloatware do you guys recommend uninstalling

Second.- Am I good to install TWRP and Viper from here on?

David C.
[Device Reviews and Information] elbastardo1:
For all of those who (like me) are having problems displaying emojis, I found this

http://android.wonderhowto.com/how-to/get-android-ns-all-new-emojis-right-now-0170328/

tested. works like a charm
[Device Reviews and Information] dubhlinn:
i have followed the guide. even made a post about recovery not flashing and somebody responded saying they already know of the issue. i think its on page 49. i cant get twrp nor cwm to install even though both the cmd window and my phone show that it has. after fastboot reboot, it just goes to stock android recovery no matter what i do.

---------- Post added at 09:01 PM ---------- Previous post was at 08:15 PM ----------

im getting lost during the instal custom recovery instructions during step 13

step 13 says "For CWM type fastboot flash recovery recovery-custom-wiko-fever.img or for TWRP type fastboot flash recovery TWRP_WikoFever_2.8.7.0.img"

1. after extracting the file/foler from the .rar, the folder is named "TWRP_Recovery_Fever"

2. inside this folder is a file named "recovery.img"

this means the instructions and command for step 13 are no longer accurate and/or effective. or am i just crazy?

regardless i have tried the command "fastboot flash recovery recovery.img" and it appears to send to the phone rather quickly. the command window shows completed and the phone shows usb transfer completed. however any attempt in any way to get to the recovery leads me to the stock android recovery and nothing has changed.
[Device Reviews and Information] mantarkus:
Ok guys, for those that might be interested.

I successfully rooted my phone with KingoRoot for PC (using this software I rooted a few years ago a Leago Lead 3, an even more obscure MTK phone)

With System App Remover I removed Kingo SuperUser and installed SuperSU instead.

Using Flashify I flashed TWRP, obviously the version that was provided by Rogersa2K.

And installed Viper4Android following Tha Watcher's instructions

I'll install Xposed as soon as I figure out if I really need it.

So this is the method I used and it worked for me, if anyone tries this it's on your own. Props to the guys that started this thread and for providing the links and instructions.

Thanks for reading.

P.S. With my luck, after I did all this, BLU will certainly have an update to Marshmallow with a better battery life and solved all bugs anytime soon.

UPDATE: Successfully installed Xposed, Gravity Box is a must :)

David C.
[Device Reviews and Information] ToucanRask:
Sorry to burst your bubble, but a user here contacted BLU support and they said that Marshmallow is NOT coming to this phone. I hope somebody sure does make use of that Wiko Fever Special Edition 6.0 Rom though.