yashsingh1/xdaforums huggingface dataset:
[Device Reviews and Information] elbastardo1:
TouchPal has adware, don't confuse that with malware. Not the same thing (though both are annoying)

and no, life mark is not the same phone as life One X. No custom roms as far as I know. Chipset is similar though, so the custom recovery might work and with that you should be able to root and eliminate touchpal. You cannot replace the dialer, at least not that easily. Though I'd suggest you try to root via KingRoot or KingoRoot first
[Device Reviews and Information] Teblakuda4o4:
Has this happened to anyone else?

My Blox started lagging like crazy so i flashed back the stock firmware v12. Then "reboot" stopped working properly, it just sort of goes off-ish and doesnt come back on, so ihave to long press power button to force shut down.

So... i flash the firmware again and this time it wont boot up, just gets stuck it bootloop.

help if you can :D
[Device Reviews and Information] tinpanalley:
Wait... I just ordered two BLU Life One X from Amazon. Are you telling me the dialer has adware?? Or did I misunderstand?
[Device Reviews and Information] SCrid2000:
Probably a typo, touchpal is the keyboard.
[Device Reviews and Information] Teblakuda4o4:
Well somehow, now that the stock blu firmware wasnt working, the wiko fever M v31 flashed and booted up.

Anyone tried restoring a Blox twrp backup of the nvram partition on the wiko M?
[Device Reviews and Information] elbastardo1:
Read carefully. "always&forever" was claiming the Blu Life Mark that has TrueCaller and TrueDialer had malware. I have no way of confirming this since I don't own the Life Mark nor those apps are installed in the Life One X.

What I can confirm is that TouchPal (the keyboard that comes pre-installed in the Life One X) does have adware. Ads and offers will be displayed in your lockscreen as long as that keyboard remains active. You have to disabled it or uninstall it (for uninstall you need to be rooted).
[Device Reviews and Information] rawlinsshemar:
Has anyone tried this yet?

What works and what does not work?
[Device Reviews and Information] SCrid2000:
Yes. When I did it it did not do anything.
[Device Reviews and Information] gruiz3:
I posted a while back about my blox not charging. I thought it was the charging port, after three dissasemblies it powered on and charged. I'm not sure but I think the trick was to plug it in while the battery was disconnected and then reconnect it while plugged in. But now I have a peculiar issue. It has the red charging light on while off and not connected. Then it runs warm while on and idle is destroying the battery. I've recovery reset the device and did a battery disconnect with a quick dis/reassembly. No dice it drains pretty steadily. Any recommendations?
[Device Reviews and Information] Teblakuda4o4:
Anyone tried the CM 13 for the wiko fever on our Blox yet? Does it work?
[Device Reviews and Information] SCrid2000:
When I tried it a month or two ago it didn't boot.
[Device Reviews and Information] Teblakuda4o4:
OK
[Device Reviews and Information] JazzzoooHere:
So I have this weird problem, I wanted to root my blox so I did a factory reset from the stock recovery. The phone boots up like normal and i start clicking thru the setup. The I need to enter in my wifi password so i click on the password field and nothing happens, the keyboard is not showing up on the screen. I would assume that the system has been damaged in some way so that the stock keyboard isn't working.

How would I fix this?

Edit: Note that I cannot activate usb debugging as i cannot get past the setup
[Device Reviews and Information] gilby2704:
I got blox with wiko fever cm13
[Device Reviews and Information] kijp15:
How are u guys getting into stock recovery?? Do we need to install a stock recovery for the blox? It takes me straight to factory mode, thanks guys.

---------- Post added at 12:22 PM ---------- Previous post was at 12:21 PM ----------

How are you guys getting into stock recovery?? Do we need to install a stock recovery for our blox?? It just takes me straight to factory mode and there's no way to do a factory reset.
[Device Reviews and Information] SCrid2000:
Very cool, care to give a step by step of how you got it working?
[Device Reviews and Information] gilby2704:
Wiko Fever cm13

1. Flash wiko fever marshmallow rom

http://xdaforums.com/showpost.php?p=68427480&postcount=926

For better root:

https://download.chainfire.eu/999/SuperSU/BETA-SuperSU-v2.77-20160827190633.zip

2. Download Wiko Fever cm13

http://www.mediafire.com/file/ifyabb6g1x4ju4r/cm-13.0-20160915-UNOFFICIAL-Wiko_Fever-1.zip

3. Follow this guide

http://xdaforums.com/showpost.php?p=68063625&postcount=41

IMPORTANT: Replace the mddb and firmware folders ONLY! do not replace boot.IMG or camera files.

After replacing the files save the rom on the SD card..

4. Boot to twrp

Wipe

System

Data

Cache

Dalvik cache

5. Flash rom

Flash gapps ARMx64 6.0 Pico Gapps http://opengapps.org/

Reboot!
[Device Reviews and Information] Teblakuda4o4:
Since you copied the framework and mddb folders, I assume network is working? Is it? No nvram error?

---------- Post added at 11:38 AM ---------- Previous post was at 11:34 AM ----------

[MENTION=7887515]JazzzoooHere[/MENTION]

If when you press <power + up vol> ,you go into factory and not recovery maybe you somehow removed the recovery. If your phone is rooted, you could use flashify and simply flash the recovery back. If not rooted you could try spflashtools to flash it.
[Device Reviews and Information] gilby2704:
Network is working 3g, hspa+

Still get nvram error
[Device Reviews and Information] elbastardo1:
This happened to me because I removed the Touchpal keyboard and had to do a factory reset. Process is discussed somewhere in this thread, but you will need to install VCOM drivers and use SP Flash tool with original firmware in order to restore your phone to factory state. You could also try to flash Gapps Aroma via TWRP and install Google Keyboard. Dont know if that will work though
[Device Reviews and Information] tinpanalley:
A few questions..

1.Can anyone help me understand how to remove touchpal from my phone?

2. Anyone have an issue with their keyboard losing all responsiveness? Laggy input?

3. So the rooting really DOES work? I'd love to have a CM rom.
[Device Reviews and Information] elbastardo1:
1) You need root for that. Ccleaner, link2sd, and many other apps will let you completely uninstall touchpal once you give them root permissions. Keep in mind that is recomended you install another keyboard in case the AOSP keyboard fails. I use swiftkey

2) Sometimes it gets a bit laggy. For me it's usually some app hoging my cpu in the background. To keep apps at bay I use Greenify with xposed activated. To kill instantly anything that mightbe resilient to greenify I use "Fast reboot" from the play store

3) As fas as I know, there are no working CM ports. Don't think it's even needed. The life one has a pretty decent near stock android experience. I downloaded a CM port that was made for the Qmobile variant, but bluetooth, camera, sim card and sd card were not working. There was a guy in here that was developing a CM port for it, but he explained he no longer has the device and thus, will not work anymore on it.

Since this phone is a little over a year old now, and it there are better options right now, I doubt anyone will likely develop any ports for it. The phone itself proved to be not that popular and in the end, there were too many returns and negative reviews on Amazon. I myself returned 3 phones before getting one that worked fine.
[Device Reviews and Information] DevBurrito:
Reboot your phone to the bootloader. (Vol-up + Power i think). Then flash a recovery. Then reboot to your recovery (Vol-down +Power?). Flash 5.1 stock gaaps (opengaaps.org). This will replace the stock keyboard apk with google's, and it should work!

(DONT HOLD ME TO THE KEY SHORTCUTS for Recovery and Bootloader
[Device Reviews and Information] tinpanalley:
Is there a good way to root this phone that DEFINITELY works. Not a lot of community out there for this particular model so I haven't seen anything saying that one way is particularly flawless. Thanks!
[Device Reviews and Information] joeybear23:
For me, the easiest method was to use KingRoot and then move to SuperSU with SuperSUme Pro ($4) then uninstall KingRoot and its apps.
[Device Reviews and Information] elbastardo1:
Download ADB drivers. OEM Unlock bootloader via fastboot. Flash TWRP via fastboot. Flash supersu binaries from chainfire using TWRP.

All resources are on this thread, mostly in the first few pages.

Keep in mind that unlocking the bootloader will factory reset the device. And this will void your warranty. But so will do rooting using any other method as well.

There are plenty advantages to have a custom recovery installed, including NAND backups and the ability to flash xposed, emojis, etc.
[Device Reviews and Information] fierogt42:
Anyone have a link to a stock recovery image? I used to have it but I can't find it now. I would really appreciate it.

I made a backup before using TiBu to incorporate updates into the system ROM, but it broke things and the SD card with my backup suddenly died, not recognized by any devices. Can't even format and try to recovery files. It's just dead.

Edit: found them. Posting in case anyone else finds this post with the same question:

https://mega.nz/#F!84gVTIxY!B0PVanNo5MbdOTiIO7d2HA!owRXQYDa

https://mega.nz/#!Op1V2DIC!DZ1ziHRq50W3XJGJB44pQMDQqYofaXpIKicCVDS2lhw
[Device Reviews and Information] fierogt42:
I flashed TWRP which let me root proper with a supersu.zip. I think I'm still using 2.8.7.0 branded by Hanuma50.
[Device Reviews and Information] tinpanalley:
I just want to get rid of Touchpal. Driving me crazy. But you're certain then that doing it the way you mentioned has no bricking possibility (other than user error)? It's something straight forward that definitely works?

...shame there are no ROMS. Although, really, this is pretty stock already.
[Device Reviews and Information] tinpanalley:
If I have to hard reset my phone, will Android just put itself back to the state it was in just by logging in again and reinstall all the apps? I'm guessing that contacts and calendar and other Google world things will come back instantly but what about, as I said, apps reinstalled and saves?
[Device Reviews and Information] elbastardo1:
Yes it will. This is a google feature, not an android feature. You will have to choose "set as X device" instead as "set as new device" and choose YES when Google asks to restore apps. Keep in mind this relies on what Google backed up from your device to begin with,. If, when you initially configured your device, didn't choose "backup my device, apps, settings, etc.", then it is unlikely that Google will restore anything
[Device Reviews and Information] tinpanalley:
Ok, understood. Any clue how you go back and add that "backup my device" setting after the fact?

So it will actually go and reinstall all the apps again? And the saves? Interesting. Somebody told me something called Helium but my PC refuses to recognise my phone for some reason.
[Device Reviews and Information] Zenda1970:
In order to do the 16MM update:

1. Perform the update

2. Flash secro + preloader using spft

Cheers
[Device Reviews and Information] Zenda1970:
Hi guys,

Has anyone been successful in making the autorotate work in fever MM rom??
[Device Reviews and Information] feegus:
Hardware issue ;

The bottom right quadrant of my screen is sketchy with touches. Has anyone taken apart this phone to adjust or replace the digitizer?

I likely won't bother replacing it but I'd like to poke around and see if something is loose or fixable.
[Device Reviews and Information] Zenda1970:
I suggest to use SP Flash tools for flashing the custom recovery (either TWRP or CWM). This way you don't need to mess around with the settings plus it doesn't wipe your phone.

As for rooting I use SuperSU. Works well in Lollipop and Marshmallow.
[Device Reviews and Information] Zombieattackready:
Just an old lady here who loves her BLOX. Definitely don't know what I'm doing but I've run in to a couple of same issues mentioned; 1) increased and faster battery drain over time compared to new. 2) I'm afraid to power down: my home page disappeared and fiddling around it to me forever to fix for now : vol+ plus power, tap power, then select recover... It took a few times but eventually worked. Any other suggestions. I can't replace. I'm in Italy now and Amazon is totally screwed up here.
[Device Reviews and Information] tinpanalley:
I get "installation aborted" everytime I try to flash BETA-SuperSU-v2.52.zip.

Can anyone tell me why that might be?
[Device Reviews and Information] Teblakuda4o4:
Try another version, then update
[Device Reviews and Information] tinpanalley:
Another version of SuperSU? Where do I find one?
[Device Reviews and Information] Froid:
Using the latest 2.79 here without issues...

https://xdaforums.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703

Sent from my Nexus 6P
[Device Reviews and Information] tinpanalley:
I don't understand this.. I unlocked the bootloader, I installed the custom recovery, and when I put in that SuperSU app it tells me I'm not rooted. I thought the SuperSU is what roots you? I'm just following the instructions on the first page where "install root" is the process of flashing over the SuperSU app.

What am I doing wrong?
[Device Reviews and Information] Froid:
You're using the flashable zip in TWRP? That will root and install the SuperSU app. You need to put the flashable zip on your internal storage, a micro SD card or a USB stick if you have an OTG cable. Then flash that zip in TWRP.

Sent from my Nexus 6P
[Device Reviews and Information] tinpanalley:
The thing is no matter how many times I've done it, the flashable TWRP zip doesn't install TWRP it installs CWM. I'm following this link. (by the way it's not called "TWRP_WikoFever_2.8.7.0" as it says in the instructions, it's just called "recovery", so I type that into the fastboot command instead)

I do step 1, no problem.

I do step 2, no problem, and then when it reboots I see the Android with the open stomach and the red triangle. I then have to push power to get the recovery menu to appear and that's where the SuperSU zip aborts installation.
[Device Reviews and Information] Froid:
That's the stock Android recovery you're seeing. That's why it won't flash. After you flash TWRP and reboot, it's restoring the stock recovery. Make sure when you start, you have developers option and enable unlock ticked. When you unlock the bootloader are you verifying that it was unlocked? If so, when you fastboot flash recovery are you seeing success?

Sent from my Nexus 6P
[Device Reviews and Information] tinpanalley:
I totally thought I did. But I can check again.

When I type "fastboot devices" I get 0123456789ABCDEF. Yes, I see success.
[Device Reviews and Information] Froid:
I personally don't reboot after I flash recovery in the fastboot for this reason. First make sure the SuperSU zip is on a micro SD or USB because the internal storage may be wiped. ADB reboot bootloader. Type fastboot devices to make sure it sees your device. Type fastboot OEM unlock or fastboot OEM unlock-go if the first command fails. You should see your phone prompt you for unlock approval. I believe it's volume up for yes, down for no. After you say yes, you should see success in the command prompt. Type fastboot reboot-bootloader. When it reboots to fastboot type fastboot flash recovery recovery.img if that's what the file is called. You should see success. Type fastboot reboot, but hold down the power and volume up and volume down all at the same time. You should get another screen that asks if you want recovery press volume up. Go ahead and do that. This should boot to TWRP. Give it write access and format data. This will wipe your storage so make sure you have the SuperSU zip on the micro SD or USB stick. Flash the root zip and reboot. Should be good to go. Definitely go back to developer option and make sure unlock and USB debug is ticked.

Sent from my Nexus 6P
[Device Reviews and Information] tinpanalley:
How am I confirming it sees my device? Nobody says that.

So you're saying do all this instead of the original instructions? This is going to wipe my phone again?
[Device Reviews and Information] Froid:
When the phone is on plug it in to the computer. Go to folder where the TWRP recovery IMG is. Hit Control+Shift+right click at the same time. You'll see a pop-up window with options. Click the option Open Command window/prompt here. Type ADB devices. If it sees your phone, it'll give you the device ID. If it does, type ADB reboot bootloader. Wait for it to boot to fastboot mode. Type fastboot devices. If it sees you, it'll give the device ID as you stated it does. Once you're at this point, you can unlock the bootloader and flash TWRP. You can attempt to use the OP directions, but if it keeps restoring the stock 3E recovery, then you'll need to try the other method. The stock recovery is restored on reboot so if we attempt to reboot to TWRP recovery right from fastboot, it never has the chance to restore it. Once you're in TWRP, it will rename the file with a .bak at the end of it, so it will never restore the stock recovery again. That's done behind the scenes so nothing you'll need to worry about. As far as wiping your phone. Unlocking will wipe it and personally I had to format data in order for TWRP to flash the SuperSU zip. You can absolutely try to flash it without formatting data and see if that works. I would always assume your device would be wiped when unlocking. Worst case scenario, it does wipe it and at least you're prepared.

Sent from my Nexus 6P
[Device Reviews and Information] tinpanalley:
I only have Minimal installed, so I don't think I can just type that anywhere. What I've done is left the img files in the Minimal folder.

What I was saying about unlocking is that since I've already followed step 1, am I not already unlocked with the bootloader?
[Device Reviews and Information] Froid:
OK that's fine. As long as the file is in your path when you're in fastboot mode

Sent from my Nexus 6P
[Device Reviews and Information] tinpanalley:
I'll try all this again. Thank you so much for the detailed help. I just wanna get certain baked-in apps off the phone. I can't imagine there's much point to trying any ROMs, this phone is already basically Vanilla. Unless there's a fully functional Marshmallow out there?
[Device Reviews and Information] Froid:
Honestly I'd stick to the stock build. There's a Wiko Fever marshmallow build, but there's issues and it's definitely not worth it IMO. I think there's CM13 for the Wiko Fever as well, but again there's supposedly bugs and it's not as simple as flashing the ROM. Just be careful debloating. I personally just freeze what I don't need with Tibu. The One X likes to bootloop for no apparent reason and removing certain apps could cause this happen.

Sent from my Nexus 6P
[Device Reviews and Information] tinpanalley:
Ok, I did what you said, I used your button hold combo and got TWRP. I didn't exactly see the options you suggested for giving it write access and formatting data. But the thing is that I checked first to confirm that unlocking the bootloader had worked the first time this afternoon and it said that it had. So, since it had formatted the phone earlier, and I hadn't done anything to the phone since speaking to you, I just figured it's already formatted and I've started resetting the phone to my desired setup. So all I did was flash the SuperSU and it worked fine. Luckily, I had bought Titanium years ago so that was a quick install and then I just froze TouchPal and a few others I hate running in the background. So THANK YOU!!

Now, despite what I had been told, the phone did NOT at all reinstall all my apps for me. I had to physically go in there and do one after the other manually. So that was a pain, but it's fine, I just wish I hadn't been told they'd all reinstall. Or at least that was what I understood. Maybe I was wrong.

So, doing anything more than freezing can really cause problems?
[Device Reviews and Information] Froid:
Glad it worked out. Keep em frozen for a couple days and make sure nothing hokey happens. If all is well, make a back up and delete what you don't want. I'm sure it'll be fine, but just have a backup ready just in case.

Sent from my Nexus 6P
[Device Reviews and Information] psychoTR2:
Alright, It's been fun, you guys. Just pulled the trigger on a Nexbit Robin, so I won't be around here very much anymore. Thanks for making time with the BLOX an interesting one!
[Device Reviews and Information] firehawk12:
I'm looking to root my phone, and I am just wondering if the instructions in the OP from a year ago still work? Thanks.
[Device Reviews and Information] SCrid2000:
Yes, the OS is the same so the instructions are still applicable.
[Device Reviews and Information] rinkeedink:
Exactly, from my experience with 2 BLOX phones, BLU has never updated the software at all, even for security. They just seem to release new phones instead.
[Device Reviews and Information] Zenda1970:
Has anyone resolved the autorotate issue with the Wiko fever MM ROM?
[Device Reviews and Information] slowjett:
Hey guys not sure if this has been covered but I can not use FB live on my Life One X... It lags very hard. Audio does not sync, in fact its WAY off. Videos are laggy in general on this phone, especially in lower light. Any suggestions or known fixes? Thanks a bunch!!
[Device Reviews and Information] elbastardo1:
I can confirm that indeed audio is stuttering and out of sync. Video looks ok but Im in a well illuminated area. It's probably a camera driver issue and I doubt there is something that can be done to fix it.
[Device Reviews and Information] Ftheccat:
Hey, so I I found this step by step tutorial, that shows pretty clearly how to backup the NVRAM. It's in spanish, but it's pretty straightforward still. http://jorgen.cubava.cu/2015/04/01/...ara-telefonos-con-procesadores-mtk-parte-iii/
[Device Reviews and Information] xboxhaxorz:
does this apply to the x2 as well, because i tried flashing both cwm and twrp and they dont seem to be installed
[Device Reviews and Information] SCrid2000:
No, the x2 is a completely different phone.
[Device Reviews and Information] wickid_d:
What he said, lol. No, I actually just bought an X2 as well since my X2016 decided to poop out on me, and am currently looking to see which wiko phone is compatible so I can grab a custom recovery.. (Edit: This won't happen as it's 2 different processors, must use Qualcomm drivers/tools as per BLOX2.com) rooting is a similar process, but you ALWAYS want to stick with a compatible recovery to your phone. Hopefully as Blu gets more popular and gets up there with the big-timers (Samsung, Moto, LG, etc), there will be more done for our phones.. Would be nice to see more Dev for our phones.. I'm seriously on a campaign, even IRL, to drive more people towards Blu, since they're inexpensive and comparable to the Big Leagues.. lol Heck, the X2 is a TRUE (unlike its predecessor that this thread is based on) octacore Qualcomm Snapdragon CPU, complimented with an Adueno 505.. this thing is boss when it comes to speed, let's hope the charging issues have been worked out... So far so good... The quick charging feature is also boss compared to the X2016.. Blu has a made a VAST improvement to the last one!

I'd honestly recommend everyone who has a X2016 to upgrade, who can afford it, and let's get some crunchyroll going on this thing!!

Ok, done with my speech and ad, you all may return to your regularly scheduled thread.. lol

Peace..
[Device Reviews and Information] fawasme:
Blu Life Mark OEM Unlock, Volume UP does not work!

Hi all,

After enabling developer options, enabling OEM Unlock, rebooting to recovery, then Fastboot, I get the screen to press volume up to Confirm OEM Unlock and erasing all data, but the phone just doesnt continue, only lets me go back to fastboot.

Has anyone experienced this issue?, is there any trick we are missing for this model?

Thanks,

Fawasme