yashsingh1/xdaforums huggingface dataset:
[Device Reviews and Information] edjocute:
I haven't tried installing the update since from your experiences, restoring stock recovery is insufficient to make it work.

The problem lies in the SHA-1 hash of the files in /system which the updater-script checks. The offending statement is in line 120:

apply_patch_check("/system/bin/install-recovery.sh", "ed3f46e726ce8e540e62fb94c259e8a5020544fe", "67e0eb9fc4641bc8f136c2ba391706ef01909dff") || abort("\"/system/bin/install-recovery.sh\" has unexpected contents.");

The second string of characters (67e0eb9fc4641bc8f136c2ba391706ef01909dff) is the expected hash of the current install-recovery.sh file in /system/bin.

Can you check your new SHA1 hash and see if it matches the expected one? It should be easier than replacing the file and trying to reflash install.zip.
[Device Reviews and Information] kwkbnk:
You can remove the assert checks from beginning of updater_script which will prevent the update from checking the hash of system files. However once the update starts patching files it will recheck the hash and if hash doesn't match, the file will not be patched to newer version. So you may end up with a mix of old and new files.

I may try to see if I can revert back and pull a system dump and either post that or put it in a zip file to make Flashable stock Rom.
[Device Reviews and Information] edjocute:
Guys, the original install-recovery.sh is still there as /system/bin/install-recovery_original.sh. This file has an SHA1 hash that checks out with the one in apply_patch_check.

Rename install-recovery_original.sh to install-recovery.sh and try the OTA update again.
[Device Reviews and Information] Bad_MOFO_33:
So I soft-bricked my phone. Can someone grab the scatter.txt for me?
[Device Reviews and Information] SCrid2000:
It's in the update.zip

---------- Post added at 04:50 AM ---------- Previous post was at 04:49 AM ----------

Tried that, got a bootloop :(
[Device Reviews and Information] Ackerlight:
Has anyone tried to root it after the update?
[Device Reviews and Information] Zdog291:
Yes, I rooted through flashing via TWRP on the updated from and everything went smoothly
[Device Reviews and Information] mswguitar:
How did you revert to stock? Did you just unroot, then flash the stock recovery or was there anything else? I'd like to try installing the update but I've already unlocked the bootloader, installed TWRP and rooted according to the guide.
[Device Reviews and Information] tinpanalley:
So after all the comments from people citing battery, camera, and other problems, is it fair to say that this MM update does more harm than good?

(Consequently, does anyone know how to remove the icon about the update on my phone?)
[Device Reviews and Information] Teblakuda4o4:
Just a note on battery alone, I've been getting more hours than before the update.

My only issues with the update are the camera, double-tap to wake, and YouTube crashing my systemui Everytime the video ends and automatically goes to the next video.
[Device Reviews and Information] tinpanalley:
Ok, well that's a pretty bad series of things to have go wrong. Even if the battery is better.
[Device Reviews and Information] Teblakuda4o4:
Could be my Xposed modules or magisk related. I'm going to clean install from a complete flash. See if that makes any difference.
[Device Reviews and Information] tinpanalley:
That would be interesting.
[Device Reviews and Information] jorensanbar:
This is my tutorial to install TWRP 3.1.0 + SuperSU 2.79, works from Stock device too.

https:// plus. google. com/u/0/+JorgeSand%C3%ADBarquero/posts/PoamshsZFaJ

Delete spaces.
[Device Reviews and Information] Gizopizo:
I tried to update to MM, but it failed. I went into twrp and tried to factory reset, which wiped my OS. I get an error about the system not being mounted. I can still get into twrp. What would my next steps be? I don't mind using a custom ROM or going back to stock. Do I need to sideload?
[Device Reviews and Information] :
Someone earlier posted a full twrp backup of rooted stock. Download that and when in twrp do adb push *that-backup* /sdcard/ . Now the backup is on your phone but you need to put it in the right folder. Do a small backup of anything, that will generate a backup folder, then move the folder of the stock backup to the same location that the other backup was generated in. Now go to restore screen and restore it.
[Device Reviews and Information] Gizopizo:
Thanks! I'll give it a try.
[Device Reviews and Information] elbastardo1:
Freeze (disable) the wireless update app.
[Device Reviews and Information] lopestom:
Read:

TWRP 3.1 for Blu life one x 2016 Marshmallow using my backup

Give credits to Larry Miller!
[Device Reviews and Information] juancollado2003:
Full working or same issues?

Enviado desde mi BLU LIFE ONE X mediante Tapatalk
[Device Reviews and Information] tinpanalley:
Hm... everything runs beautifully after updating but the camera becomes uselessly dark using Footej that worked great before on Lollipop. The main camera works ok but I can't use the main camera, the little beep after focusing drives me mental and it can't be removed.

Any workaround for this camera or has BLU messed this up?
[Device Reviews and Information] sldier11:
Google Camera

I haven't used Footej but the Google camera app works great as a replacement for the system camera

http://www.apkmirror.com/apk/google-inc/camera/camera-2-7-010-release/google-camera-2-7-010-2617962-30-android-apk-download/
[Device Reviews and Information] tinpanalley:
Cool, interesting. No problem with exposure but unfortunately I've grown to used to being able to focus one spot and take the light reading of another. And this app doesn't give me that. Thank you though!
[Device Reviews and Information] Awanonimik:
Is there a list of custom ROMs somewhere?
[Device Reviews and Information] tinpanalley:
Hmm.. not sure what it is, but after a smooth start, now I have several problems.

- Apps decide suddenly they can't connect (facebook, other online dependent apps)

- Shortcuts appear twice on my screen (Arrow Launcher) but removing one causes them both to disappear upon reboot

- Heavy delays and lags where none existed before

Is this possibly caused by not having done a hard reset after updating or is the 6.0 update just buggy?
[Device Reviews and Information] ElijahSilas:
Soft Brick with TWRP recovery and 6.0 Marshmallow

:eek: would anyone be willing to make a complete nandroid backup (everything system boot etc.) and upload it somewhere. I can't use my device at all but i have access to the custom recovery i've tried everything. I know this is a lot to ask but please help!
[Device Reviews and Information] Teblakuda4o4:
Within this forum, someone posted a link to a backed up system (the first update V14) using twrp. Find and restore using that. You may have to change recovery to the lollipop compatible one on the first page.

Good Luck.
[Device Reviews and Information] Rambinho:
Fastboot Flash Recovery doens't work

Guys, I tried many ways to install the custom recovery, but the fastboot flash recovery doesn't work. It says, it can't be loaded. Can anyone help me?
[Device Reviews and Information] Teblakuda4o4:
Could be your drivers, try reinstalling them.
[Device Reviews and Information] juancollado2003:
Open bootloader

Enviado desde mi BLU LIFE ONE X mediante Tapatalk
[Device Reviews and Information] ElijahSilas:
I went ahead and used SP Flashtool to flash the phone back to stock Lollipop and then re-upgraded to marshmallow. thanks for the help!
[Device Reviews and Information] Rambinho:
I did that. By the way, I can open the bootloader just with the phone. I can't do that using Minimal ADB and Fastboot software.

---------- Post added at 05:05 PM ---------- Previous post was at 04:30 PM ----------

ok, i finally finished this step, but I can't enter in the recovery mode (CWM). It says devices not found.
[Device Reviews and Information] Teblakuda4o4:
Did u have a backup of your nvdata? When you flash with spflash that gets deleted as well.
[Device Reviews and Information] Rambinho:
Which driver should I install?
[Device Reviews and Information] ElijahSilas:
I did not back it up, and i haven't used a sim card. I'm fairly new to this. Everything works just fine, is there something important that I don't know about?
[Device Reviews and Information] elbastardo1:
Yeah, sometimes nvdata gets corrupted and you get an invalid (blank) imei, which makes the phone unusable for calls and texts.

Happened to me, thankfully I had a backup.
[Device Reviews and Information] Teblakuda4o4:
The Amazon fire drivers from the 2nd post on this forum.
[Device Reviews and Information] tinpanalley:
Has there been any resolution from BLU or otherwise for this issue with all the camera apps being dark? Anyone else have this problem or figured out how to fix it?
[Device Reviews and Information] Rambinho:
I did it everything, but when I install the CWM mode, and when I enter the recovery mode, It doen's appear the install zip option. It seems the recovery isn't customized, I instal the custom recovery, but it doesn't have the "install zip" option.
[Device Reviews and Information] Rambinho:
Thank you so much for that. The only thing that wasn't working was to install the custom recovery. It didn't appear the custom recovery to install the root.

Now, I can live well.

Love you!!!
[Device Reviews and Information] ElijahSilas:
did anybody else not get android marshmallow emojis after the upgrade?
[Device Reviews and Information] elbastardo1:
emojis on this phone are the worse. I used emoji switcher and works like a charm, but you need root access.
[Device Reviews and Information] TiTiB:
After MM 6 UPDATE HAS ANYONE HAD ROOT SUCCESS WITH APK?

Before anyone asks, I don't have access to a computer?

When I first got my phone, and it was still Lollipop, I used Kingroot successfully. No such luck now, In fact I have tried every apk root solution I could find (at least 8 or 9 of them) with no luck. The ones I tried, that I remember:

Kingroot 5.2

Framaroot

iRoot

Towelroot (just for kicks, really)

Kingoroot

Rootmaster

z4root

Thank you
[Device Reviews and Information] bobbiegenius:
Have you tried C.F. Autoroot?
[Device Reviews and Information] TiTiB:
Requires a computer, yes?
[Device Reviews and Information] bobbiegenius:
The new Android app by Chainfire called

CF Autoroot... get info @ https://autoroot.chainfire.eu/

So... no, it requires no computer.:good:
[Device Reviews and Information] juancollado2003:
Stop recommending things you haven't tried before, CF-Auto-Root is for samsung only, is a boot that needs to be flashed by odin using a computer

Enviado desde mi BLU LIFE ONE X mediante Tapatalk
[Device Reviews and Information] tinpanalley:
I'm sorry to keep bothering about this but it's the only community that talks about this phone... anyone else unable to use their camera with any other app because of getting a very dark screen/viewfinder? I'm trying to deal with BLU on this. Not getting anywhere.
[Device Reviews and Information] Gizopizo:
Hi jazzzooo,

Sorry to bring up this blast from the past, but I'm still unable to get back to stock on my Blu Life One X. I followed your directions and when I try and restore using the zip file of the rooted stock (the file I used is BLU_L0070UU_V12_REPAIR.zip), it doesn't "take." When I go to reboot my device within twrp, it still says "No OS installed." I reboot anyway, and it gets stuck on the white splash screen with BLU Bold Like US. I can still get into twrp.

Just for clarity, this is how I did a couple of things: I used an external sd card and copied the file of the rooted stock from my PC onto that card. I then put that sd card in my Blu. I moved the zip file from the card to the phone using the File Manager option in twrp. I created the backup folder like you said. Does the zip file go in that backup folder, or "next to" that backup folder within twrp? I ask because when I go to restore, I don't see the zip file, just the backup folder. Anyway, did any of those steps I took foul up my attempt?
[Device Reviews and Information] :
You got the wrong file, the repair.zip if for spflash tool (worst case scenario), look for the post where you got that zip file, the same post contains a twrp backup, unzip that and put it in your twrp backups folder.
[Device Reviews and Information] Gizopizo:
Jazzzooo,

Man, I am so dumb. I don't know how many hours I searched for solutions to mounting problems and partitions. I had the wrong zip file the whole time. Thank you so much for your help!
[Device Reviews and Information] :
Lol, it's OK, I did the same thing when I first tried. Good luck, tell me if it works
[Device Reviews and Information] Gizopizo:
I

Yup, it did work. Got my phone up and running again. Thanks, again!

---------- Post added at 09:56 PM ---------- Previous post was at 09:08 PM ----------

Actually, I do have another question. This whole thing started when I tried to update to MM when Blu rolled it out a month or two ago. Is the fact that it is rooted make updating via that method problematic? If a phone is rooted, should I only update the OS via twrp or some other method, and not try and update using the official method?
[Device Reviews and Information] :
I just lost my root after updating, but you should be able to update with root
[Device Reviews and Information] scorpionx:
I need some help. So I've been trying to fix my IMEI number ever since the new marshmallow update came out for the phone. However, the tools I've used in the past seem to not work anymore. The preloader will only register as a device for a few seconds and then disappear, causing the IMEI repair tool to fail. Are there new instructions on how to do this? I can't get my t-mobile sim card to work without this fix.

Also, is there a working bootloader to root the new marshmallow rom?
[Device Reviews and Information] Teblakuda4o4:
How did u lose your imei?
[Device Reviews and Information] scorpionx:
I have no idea. When the stock marshmallow rom was installed I went from having IMEI to not having it.
[Device Reviews and Information] Teblakuda4o4:
Someone posted a trwp backup of LP v14, restore that and you should get a imei.

Then u can update to marshmallow again from stock Android.
[Device Reviews and Information] SirPeriwinkle:
Hi everyone, I was messing around with my life one x and i managed to brick it pretty badly. I cant even get into fastboot. Anyone have any tools or stock roms I can use to try and get it back working?
[Device Reviews and Information] Teblakuda4o4:
Use spflashtools and the Blu firmware v12 to try n get it working. The firmware link is somewhere in the first few pages of this thread ( or u can search it). Make sure u have the drivers installed to use spflashtools with the blu
[Device Reviews and Information] Awanonimik:
Unable to flash TWRP or CWM

Everything seems to work fine, I flash CWM, both sending and installing are "OK", but does not seem to actually install it. I've tried with TWRP as well, also didn't work. Some help would be appreciated.
[Device Reviews and Information] Teblakuda4o4:
Don't reboot to the phone after install, reboot straight into the recovery after it installs.

What I do is hold the power button till phone goes off after flashing twrp, then go straight to recovery.
[Device Reviews and Information] Awanonimik:
I tried that, didn't work. Now I used a different copy of twrp, then used "fastboot boot twrp.img", worked fine, flashed SuperSU, and now it won't boot. Stuck on the white "Bold Like Us" screen. Any help? I can get into stock recovery, presumably twrp by using the same steps as before. Will check shortly, for the purposes of helping please assume I can.

Thanks in advance,

<Awanonimik>
[Device Reviews and Information] Teblakuda4o4:
Try flashing a another version of SuperSU. If u used the one from this forum, try the latest version and vice-versa.
[Device Reviews and Information] Awanonimik:
I would, but now for some reason it can't find my device anymore. Here's the exact wording of the errors:

when attempting to flash with "fastboot flash recovery twrp.img":

"sending 'recovery' <11912 KB>...

FAILED <command write failed <No such device or address>>

finished. total time: 0.007s"

--------------------------------------------------------

While writing this post I succeeded in booting to TWRP, installed the latest version of SuperSU. I got past the white screen, the install advised me it could take a while to boot the first time. Currently waiting to see if it will.

EDIT

> Worked fine, now attempting to install Xposed, looks like it's working, just optimizing apps now.

> Just a quick warning, probably unnecessary as it tells you when you attempt it; don't try to install the sdk22 versions of Xposed if you're running Marshmallow, you'll want the sdk23 versions.

> Thanks for your help, without your (rather obvious) solution, I wouldn't have managed this.

Cheers,

<Awanonimik />
[Device Reviews and Information] gustavo76016:
Has anyone found a fix for the dark camera issue? Its really annoying...
[Device Reviews and Information] tinpanalley:
I wrote to them back and forth about 7 times. It was a nightmare. They'd ask for info and then after getting what they asked for they'd ask again! I couldn't believe it. Anyway we eventually got to a point where they were willing to acknowledge the problem with the camera after several proofs sent by me and they said they'd do an RMA return but I'd have to be willing to be without the phone altogether for about a month and I just dont have another device to replace it so I'm out of luck. If you persist with photo proof of your dark camera screen, some dark photos, your IMEI and proof of purchase, I'm sure theyll offer you the same replacement/repair.
[Device Reviews and Information] gustavo76016:
Yeah, not an option though as i bought the phone from another country so itd be too much of a mess :p

Also, wouldn't rolling back to 5.1 be a better option?
[Device Reviews and Information] tinpanalley:
6.0 is too good. Don't want to have to go back.
[Device Reviews and Information] tinpanalley:
Here's a weird thing... I plug in my wife's phone to copy some ebooks and music to it and the phone doesn't give me the usb options? I try mine, it works fine. Both are 100% identical in setup. Any ideas?
[Device Reviews and Information] TiTiB:
repost to see if anyone has had success yet
[Device Reviews and Information] lopestom:
Simple!

MM ROM only accept ROOT if you flash/Install TWRP/CWM-CTR for flash SuperSU...zip

Others applications/ways to have ROOT maybe don't work because in MM ROM has very hard block to do!

So BLOX 2016 has TWRP to MM ROM created a time ago.....
[Device Reviews and Information] TiTiB:
Thanks for the reply [MENTION=4939713]lopestom[/MENTION]

Maybe I'm missing something. I 'm on the MM update, with no other modifications. I don't have access to a computer in order to install anything via adb, so, to my understanding, I can only use an APK root solution.

Please correct me if I'm wrong...please ?
[Device Reviews and Information] lopestom:
Yes. Has a other "solution"..... [creating a correct flashable zip to flash recovery file or using the terminal emulator apk, etc].......

But that's a hard step because can brick the phone if the process no have sucess.

Therefore without a security process or with computer (to unlock bootloader and/or flash files with SPFT) you go wait the correct apk ROOT by developers. :rolleyes:

good luck
[Device Reviews and Information] laradio6:
Blu life one x Marshmallow Imei fix and root

m gonna post instructions with links on how to fix these issues soon :D
[Device Reviews and Information] TiTiB:
Thanks, again. I'll just continue to check every now and then.
[Device Reviews and Information] Teblakuda4o4:
Which issues?
[Device Reviews and Information] laradio6:
issues revolving around rooting on mm for the blox and imei issues, I am at work so when I get home I will post the instructions
[Device Reviews and Information] Teblakuda4o4:
Oh alright. Thought you were referring to the issues in mm itself, like camera and such.
[Device Reviews and Information] elbastardo1:
Problem is, is not a hardware problem. Is a software problem. Camera works fine with Lollipop. And depending on the camera app, sometimes is the front camera and sometimes is the back camera. I highly doubt a replacement phone will fix the problem. Unless it's a revision with updated cameras or a different MM update than the publicly released version.
[Device Reviews and Information] Teblakuda4o4:
Can someone upload a working twrp backup of marshmallow.

This morning my phone just wouldn't turn on and no matter how many times i flashed the stock firmware, doesnt work. If it did, all apps would constantly crash till the phone reboots.

** Update**

Finally got it to boot using the Wiko Fever firmware. Was the NV Data error ever solved to get working imei?
[Device Reviews and Information] sldier11:
Yes download and use googles camera app. it works fine.

apkmirror.com/apk/google-inc/camera/camera-2-7-010-release/
[Device Reviews and Information] tinpanalley:
No. It doesn't. This isn't about an app or another. It is a defect of the phone. Even BLU Admitted it to me.

The Google camera doesn't make a difference.
[Device Reviews and Information] sldier11:
This was a reply to the dark front camera with the upgrade to 6.0 on the Blu Life One X 2016 model.

I have two of these phones and the google camera app fixes the front camera issue. Download it and try it yourself or don't. Doesn't matter to me.
[Device Reviews and Information] elbastardo1:
It fixes the front camera issue, but screws up the back camera. You end up having to use a different camera app for each camera.
[Device Reviews and Information] sldier11:
Be sure to use HDR mode and the back camera works fine
[Device Reviews and Information] andrewstas:
How to root my BLOX?

Hi everybody. I am totally newbie to rooting a phone, so I would like to have your advice on this.

I only want to root my BLOX2016 but I do not want to lose any data, app, photos etc. I just want to be able to install certain apps that need root. I still use Lollipop and I will probably stick with it.

Is there any easy way to do the root without risking losing/erasing anything from my phone?

Is there a PC software to do what is needed to be done without the need of special steps from the user?

As I told I have no idea on how is this done, so I want to avoid to deal with problems which could even be easy for an expert but which will cost me hours and possibly wrong decisions on the steps to follow.

Thank you in advance for your help. :cool:
[Device Reviews and Information] gilby2704:
Crdroid v3.5 (N) for MMX Canvas 5, Blu life one x 2016 and Clones

Hello all here is a custom ROM for our BLOX this is not my work I am just sharing my findings with the resources already available here and elsewhere to make it all work sim card, LTE, auto rotate, sensors.

Substratum Supported

Built- in Root

Requirements:

Important!! You must be in stock Lollipop in order to work

If you upgraded to marshmallow you will have to flash back using sp flash tool.

Unlocked bootloader

Root

TWRP 3.0.0 (IT WILL ONLY WORK WITH THIS VERSION ANY OTHER WILL GIVE YOU AN ERROR) Link: https://www.androidfilehost.com/?fid=24459283995311359

Instructions to flash ROM:

1. Download ROM and save it on your PCs desktop, there are 2 files only download the one named Crdroid v3.5.zip you will not need the other file.

https://drive.google.com/drive/folders/0By8Mtxif2hXHVUtDa1pLSkV0dzQ

2. For sim card detection:

Open the ROM zip. With 7zip file manager and take the stock folders: firmware and mddb - directly copy to folder system/etc/

After copying folders close the zip and save the ROM to your device sdcard.

3. Reboot to TWRP

Wipe

System

Data

Cache

Dalvik cache

4. Flash ROM

5. Flash gapps ARMx64 7.1 Pico Gapps

http://opengapps.org/

6. Reboot

Credits/Contributions:

Asfand2k16 (ROM)

Scrid2000 (TWRP)

lopestom (Sim Detection)

Model number will say E481 is because this device is a direct clone of the Micromax Canvas 5

Bugs:

If you encounter lag after first boot go to settings-Display-live display and change it to off.

WiFi nv ram error but it works anyway