yashsingh1/xdaforums huggingface dataset:
[Blu Pure XL] xathras:
Wow! So much happening - well done everybody.

There appear to be two ways to proceed from now. Either change the boot image and/or create a custom recovery.

Changed boot image

This looks more difficult than I first thought. We are going to have to de-compile the kernel, then make changes and re-compile it. Even though both phones are using the same kernel (30.10.72+) there may well be differences in other parts of the image (see post #10).

Custom recovery

This approach has the advantage that the same recovery should(?) work for both the Blu and the Allview. Also a non-working test recovery won't stop the phone from booting normally. A non-working boot image will mean re-flashing the original image before the phone can be used again.

Have look at this thread for creating a custom TWRP recovery:

http://xdaforums.com/showthread.php?t=1943625

I can't try this out immediately because I've got a complex Android Studio build environment on my desktop machine that I don't want to disturb. However, I do have a laptop that has the required RAM and space. All I have to do is install Windows on it (sigh!).

Starting a toolbox

Not all the existing tools will work with the new Mediatek 64-bit SoC chips. In particular, MTK Droid Tools 2.5.3 won't. When I tried it it couldn't find enough info. to create a scatter file, but it did display a blocks map. The values it shows could be used to edit another scatter file manually. The syntax of a scatter file is fairly simple. MTK Droid tools is no longer being maintained, but do try it anyway: http://xdaforums.com/showthread.php?t=2160490

The latest version of SP Flash Tool (v.5.1532.00) does work with the Helio X10 (mt6795) chipset. Download it from here: http://azmicellular.blogspot.co.uk/2015/08/sp-flash-tool-v5153200.html

or Google for: "sp flash tool 5.1532".

There is a new tool called MTKIMG that can unpack and repack boot.img and recovery.img for MTK devices, but I haven't tried it yet to see if i works with our chipset. Find it here:

http://xdaforums.com/android/development/tools-unpack-repack-boot-img-utility-t3154621

There are several phones on the market that Use the Helio X10, so it is possible that new tools will appear shortly
[Blu Pure XL] FuMMoD:
Could you please install MTK droid tools and open it and take a screen shot of the blocks map please. I uploaded a copy of it for you. You have to have ADB currently setup for this to work. Thanks

https://app.box.com/s/hcqwlc28gcxie2ix35tos1jhu2deexoj

---------- Post added at 03:41 PM ---------- Previous post was at 03:37 PM ----------

Thank you for the links! Currently using all what you've provided. I submitted a bootimg to the developer of MTKIMG so he can modify it to work with the MT6795 chipset. I'm pretty bad at documenting at the moment so your posts are extremely helpful for others. I'm just multitasking and trying new ideas. Really appreciate the support from all you guys.

Update : I have a completely modified and editing bootimg from the Allview ready to go. Only issue is I'm having trouble repacking it. Once repacked It will have all settings for secure disabled in order to enable root.
[Blu Pure XL] xathras:
Here is a screenshot of the Allview blocks map. How does it compare to the Blu Version?
[Blu Pure XL] FuMMoD:
Scatter files are completely identicle but they don't match what the OTA has.

preloader 0x0
pgpt 0x0
proinfo 0x80000
nvram 0x380000
protect1 0x880000
protect2 0x1280000
seccfg 0x1c80000
lk 0x1cc0000
boot 0x1d20000
recovery 0x2d20000
secro 0x3d20000
para 0x4320000
logo 0x43a0000
frp 0x4ba0000
expdb 0x4ca0000
tee1 0x56a0000
tee2 0x5ba0000
system 0x6800000
cache 0xba000000
userdata 0xd4800000
flashinfo 0xFFFF0084
sgpt 0xFFFF0004
[Blu Pure XL] xathras:
Custom recovery

Once we have root we could try one of these "magic" recovery installers

http://xdaforums.com/showthread.php?t=2798257

http://xdaforums.com/showthread.php?t=2748169
[Blu Pure XL] xathras:
Example MT6795 scatter file

This is the scatter file for the Xiaomi Note 2 (Helio X10 based) phone.
[Blu Pure XL] xathras:
We only need boot and recovery to use SP Flash Tool. Are they different from the OTA?
[Blu Pure XL] FuMMoD:
Yes our scatter files are different from the OTA scatter file inside the OTA.zip
[Blu Pure XL] xathras:
What are your thoughts on using fastboot?

http://xdaforums.com/showthread.php?t=1752270

I forgot to mention that the blocks map screenshot I posted was taken BEFORE the OTA update arrived. I flashed it, so now we are on DIFFERENT machines.
[Blu Pure XL] FuMMoD:
That's what I'm working on doing. The bootimg I have won't repack yet. If it does we'll have root. I'll continue on it once I get out of work.
[Blu Pure XL] xathras:
See my edit to post #57.
[Blu Pure XL] FuMMoD:
Were you able to take out the recovery or bootimg?
[Blu Pure XL] FuMMoD:
I'm starting to really hate BLU. The more I try the more disgusted i feel that they lock the phone down like this and then refuse to give any updates.
[Blu Pure XL] schorsch9999:
Here you go :)

The Block Map after the OTA update.
[Blu Pure XL] FuMMoD:
Update : So I managed to repack the boot img and I'm stuck in a bootloop. Doesn't get past the BLU splashscreen. It looks like I got root since on the recovery screen it doesn't display "Normal" when i check root.
[Blu Pure XL] FuMMoD:
So I tried to flash the regular boot img from the allview without any modifications and it actually booted to the BLU splash screen the one with the colors not the splash logo. So it went further this time and it didnt loop. It just froze on that screen. So I'm guessing the problem is something with the repacking. What I'm going to try to do is push the whole OTA to the phone and get it to run the Allview version instead of the BLU one.

UPDATE : OK IT BOOTS !! So the bootimg is IDENTICLE!!!! I just have to find a better method for repacking the image so it compiles with no errors. Guys we're almost there.
[Blu Pure XL] mhajii210:
Woot woot

So the phones are practically identical? You made my night! :good:
[Blu Pure XL] DannyHammons:
I have the kernel source code for the MTK 6795. Apparently they put it out on a server "accidentally". Of course, it had been saved off by the time they removed it. While I'm a programmer, I have very little extra time to do anything with it. But, if sharing it gets us any closer to root, custom recoveries, or custom ROMS, I'll be happy to share it.
[Blu Pure XL] FuMMoD:
I have 2 Sources of the MTK 6795 available. Please upload and PM it to me so I can compare if it's the same or not. Thank you.

---------- Post added at 11:29 PM ---------- Previous post was at 10:35 PM ----------

Update : Hey guys I managed to repack a working bootimg with ro.secure=0. This is the 2nd milestone we have accomplished together!

Currently have kingoroot running since it uses that adb.secure=0 and ro.secure=0 as an exploit to force root. Hopefully this works, if not no worries since we're already unsecured.

I've tried over 10 bootimg unpacking and repacking tools. The only one to give me a working boot img is this android kitchen one.

[DEV][TOOL] Android Image Kitchen - Unpack/Repack Kernel Ramdisk [Win/Android/Linux]

http://xdaforums.com/showthread.php?t=2073775
[Blu Pure XL] stryfe60401:
I am no help to anything but I want to say thanks to all those putting in the time and effort to do this. Appreciate to effort!
[Blu Pure XL] FuMMoD:
Default prop is properly configured for root.

#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.adb.secure=0
persist.sys.usb.config=mass_storage
persist.service.acm.enable=0
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
ro.zygote=zygote64_32
ro.mount.fs=EXT4
camera.disable_zsl_mode=1
dalvik.vm.dex2oat-Xms=64m
dalvik.vm.dex2oat-Xmx=512m
dalvik.vm.image-dex2oat-Xms=64m
dalvik.vm.image-dex2oat-Xmx=64m
ro.dalvik.vm.native.bridge=0

Update : adb root command yields

restarting abdb as root

Update 2 : The system is a read only system. I'm trying to figure out how to change to read and write but it keeps denying all my shell commands.

Update 3: Looks like the device is setup to support FM radio

# FM Radio device node
mknod /dev/fm c 193 0;
chmod 0660 /dev/fm
chown system media /dev/fm
[Blu Pure XL] xathras:
There's an interesting story behind this. Many phones have had the ability to support FM radio for years. But the major carriers have insisted that it be disabled during negotiations with phone manufacturers. From their point of view they would prefer users to be streaming their music (and making them money) than be listening to free FM. After a deluge of protest AT&T have capitulated and will allow FM from 2016, other carriers are still thinking about it.

http://www.androidauthority.com/att-to-require-working-fm-radio-chips-android-phones-629989/

http://www.opb.org/about/connect/mobilefm/

http://freeradioonmyphone.org/take-action/

The built-in FM ability was a feature that attracted me to the Gionee E8. The early specs. said "FM - recordable". As a UK Radio 4 junkie one of the first things I did after unboxing my Allview was to try to find the radio app. I was really p****d off when I couldn't find it. After some hunting around I found the Spirit app and managed to get it running on my first generation Galaxy Note (2011?) which I have running a custom Android 5.1.1 rom.

http://xdaforums.com/apps/spirit-fm/app-spirit2-free-source-real-fm-radio-t2951455
[Blu Pure XL] mscion:
Perhaps this is jumping the gun but I was wondering if you think that Xposed will work on this device once you've successfully rooted. Thanks!
[Blu Pure XL] FuMMoD:
Too early to tell. Let me work on getting root first and I'll test out xposed and all the rest of the goodies.

---------- Post added at 10:03 AM ---------- Previous post was at 10:02 AM ----------

I'm pulling at straws right now. I have the default prop molded but my issue right now is with adb. I can't run any root commands through adb or else I get permission denied. I need a way to make the system to read/write.
[Blu Pure XL] clipcarl:
Are you saying you've achieved root but can't mount the system read/write? What commands have you tried? Thanks!
[Blu Pure XL] FuMMoD:
I'm not sure if I've achieved root. From what I've read root is acquired by editing those lines which I have successfully done. I can't push SuperSU or the SU binary due to the system being read only. So I'm pretty much stuck for the moment. Even trying adb remount gives me a permissions denied error. In my instance I have not achieved root since SuperSU cannot run.
[Blu Pure XL] mscion:
Hi. Would using this approach be helpful in regards to adbd insecure? Or would there still be a r/w problem....

http://xdaforums.com/showthread.php?t=2593581
[Blu Pure XL] FuMMoD:
Nope I still have a r/w problem. My secures are set to 0 already.

ro.secure=0
ro.adb.secure=0
[Blu Pure XL] xathras:
Here's some info. that might help. At least it clarifies the problem.

http://xdaforums.com/showthread.php?t=2593581
[Blu Pure XL] mscion:
This is the same link I gave in previous post. lol
[Blu Pure XL] xathras:
My apologies. I forgot to read before posting.
[Blu Pure XL] mscion:
No worries! The key thing is to follow steps 5 and 6. At least this is what I did when it tried it for my Note Edge. I was then able to r/w to system using adb commands. Don't know if it will work for the Blu device...
[Blu Pure XL] FuMMoD:
Yup tried it. Can't run any adb commands unfortunately.

The way to exploit this device is through the boot img for now. Maybe I can throw a command into the default prop?
[Blu Pure XL] FuMMoD:
So i pulled all the recovery files from the OTA hoping one was the recoveryimg but it doesn't look like it. I'm going to try to see if any of these are of any help. It seems I can also pull stuff using ADB pull but once again system is read only so I can't do anything else.
[Blu Pure XL] mhajii210:
Linux

Is it possible there is something wrong with the Windows adb drivers? I was never able to get Helium to work using Windows and the same generic Google adb drivers you mentioned, but I was successful once I figured out how to get Linux to recognize the device. Now Helium works, and adb commands work. I have a feeling you might have better luck using Linux to ultimately root the phone. I'm not a developer, otherwise I would help :crying:
[Blu Pure XL] jerrybritt:
I have Helium up and running like a charm. I used the drivers from one of the chinese versions and I got everything moved over.
[Blu Pure XL] mhajii210:
Would you mind sharing a link to the driver you used to get Helium to work via Windows? I would much rather use Windows instead of Linux to activate Helium in the future. Thank you!
[Blu Pure XL] jerrybritt:
The Link I used

http://androidmtk.com/download-gionee-usb-drivers and then chose the Gionee E8. This is the same phone from all I have researched and like I said Helium is working great for me. Good Luck:)
[Blu Pure XL] mhajii210:
I tried the drivers you mentioned and still no luck on Windows 10. What Windows version are you using? Everything installed fine, but the Helium desktop program doesn't seem to detect that the phone is connected. I am obviously able to access the phone and all the files. It's really not a big deal for me since I'm able to activate Helium using Linux. Are you using Windows 7? Maybe Helium isn't working on Windows 10 for some reason.
[Blu Pure XL] jerrybritt:
Windows 10 on Surface Pro 3
[Blu Pure XL] mscion:
So is current status that we don't have root?
[Blu Pure XL] FuMMoD:
Unless stated otherwise, no. When I get root I'll update but if I don't mention it just assume we don't.
[Blu Pure XL] mhajii210:
Were you able to get Helium to work on Windows? Strange that I used the Gionee drivers and still no luck for me.
[Blu Pure XL] xathras:
Compile custom TWRP recovery

Has anyone given some thought to the alternative method of rooting the phone? If we could build a custom recovery image we should be able to flash supersu.zip from it.

This link ( http://xdaforums.com/showthread.php?t=1943625 ) seems to be the goto thread on the subject. All the "smarts" for the build appear to live in the "BoardConfig.mk" file. The author of the thread recommends using the Omnirom source code.

I found this link ( http://docs.omnirom.org/Setting_Up_A_Compile_Environment ) on how to set up a compile environment. Fortunately, I have a laptop that's not doing much at the moment, so I installed a clean Ubuntu 14.04 on it and am now doing a repo sync, which is going to take some time.

Once I have a build environment I'll try compiling a known working BoardConfig.mk file to check that everything is O.K. (paths, libraries, etc).

This should be doable as long as the custom recovery is small enough to fit in the existing recovery partition. Does anyone else have a suitable build setup and the time to help with this?

Please let me know your thoughts.
[Blu Pure XL] mhajii210:
I don't understand one thing... isn't this phone the same as the Gionee Elife E8? Shouldn't this root method http://www.skyneel.com/2015/06/how-to-root-gionee-elife-e8-without-pc.html work? Here is another link http://howrootguide.com/root-guide/gionee-elife-e8.html.
[Blu Pure XL] schorsch9999:
Yes

No, pls forget this rooting-links they all not works or not true (not to say it's spam)!...
[Blu Pure XL] FuMMoD:
Guys whatever rooting method you find on Google relating to the E8, allview and pure xl trust me I've tried. The auto rooting methods don't work and a lot of those sites are fake and filled with Spyware.

I managed to get an email back from BLU regarding sources.
[Blu Pure XL] FuMMoD:
So I've decided to return my Pure xl this week and have sworn off all BLU devices. Sorry guys it's been fun
[Blu Pure XL] mhajii210:
Sorry to hear that! I'm pretty certain I would be able to root the phone using Linux, but I presently have no need to root it. Plus I'm returning my current Pure XL and I'm waiting for the new one to arrive. There's a small section on my display where the oleophobic coating has been somehow scratched. It looks like a drop of some harsh chemical dissolved it. It was like that right out of the box. It's very slight and not noticeable, but I figured I would exchange it while I still have the time. Please reconsider if at all possible! I truly feel you can't beat this phone when it comes to the specs you're getting for the money. I have no doubt we will have root in the near future.
[Blu Pure XL] FuMMoD:
Specs are nice but the company and the software are such a huge bottle neck I won't consider it again. This was my first and last Blu product that's for sure. The ui is just so terrible and their support I'd equally as bad. I tried my best via Linux and Windows and the problem is with the phone itself.
[Blu Pure XL] clipcarl:
Would you mind sharing your knowledge with me or helping me obtain root? I (and many others here) would prefer to have root even though the phone is still great without it. I'm an experienced Android user with the Linux developer SDK installed but I'm not familiar with what needs to be done to obtain root from scratch. I'd be happy to post the results here and maintain it if you'd prefer not to yourself. Heck, if you can come up with or help me come up with the first working root for this phone I'll PayPal you $150. PM me if you're interested.
[Blu Pure XL] mhajii210:
My knowledge only has to do with actually using Linux. I personally have never come up with a root method, but I do think I would be able to given enough time. I hope I'm not being full of it. I will see if I'm able to help once Marshmallow is on more devices. One thing I would suggest, why don't we start a bounty? We were able to fix the camera wrapper on the HTC M9 (which I still own) that way. I wonder if there is enough demand to do the same with this phone? I personally would be willing to chip in to help jump-start the bounty. I think the issue is if we can have enough talented developers with time to help out.
[Blu Pure XL] schorsch9999:
Hey, don't give up so fast...! ;)

See it as a challenge :cool:

Well, BLUE ( and Allview also) only sell the device under his name - not more. So i don't think that they can give you support in this case.

It is a Gionee Device, so we must ask there for support and how to root.

It gives the LeTV One/X600 s1 device with the same CPU and Android 5 that is already rooted - so it must be possible.

Before you go can you please leave us your modded boot.img so far?

PS: Sorry for my bad english
[Blu Pure XL] xathras:
I'm sorry to see that you couldn't stay the course.
[Blu Pure XL] FuMMoD:
I don't mind continuing but I rather not have 350 tied into this device lol. I'll upload the modified bootimg later. There's only one unpacking and repacking method that works for our device bootimg and I'll post the link again. It's an android kitchen booting repacker.
[Blu Pure XL] xathras:
Fair enough, but would you mind dropping in to this thread from time to time. I'm making some progress with compiling a custom TWRP recovery. If I can build one that's no bigger than the existing recovery all(?) I have to do is flash it with fastboot.

The build environment I first used turned out to be obsolete, so I had to tear it down and start again. However, I did get lucky this morning. I found a BoardConfig.mk for the HTC M9+ which also uses the MTK X10 Helio. It gives me the CPU entries needed. Next thing to do is create a fstab. Once I've done that, would you mind taking a look at it?
[Blu Pure XL] mhajii210:
Guys we should all chip in and help pay the $350 so FuMMoD can continue to help us root this phone! Anyone with me?
[Blu Pure XL] stryfe60401:
I'm willing to donate to this.
[Blu Pure XL] FuMMoD:
I'll take a look at it tomorrow. Sounds like a good lead.

Here is my modified bootimg i have compiled from the Allview bootimg that boots on the Pure XL.

https://drive.google.com/file/d/0B25U42vL3cnkbU9iWk9jMUozeWc/view?usp=sharing
[Blu Pure XL] xathras:
EXPERIMENT: Root without modifying /system

Not immediately useful, but very interesting.

http://xdaforums.com/showpost.php?p=63197935&postcount=2
[Blu Pure XL] xathras:
TWRP

I'm making some progress with compiling a TWRP recovery. It's taking time since I'm having to learn a lost of things as I go. The BoardConfig.mk I'm making has 4 major sections - cpu/platform entries, kernel entries, file system entries and TWRP specific flags. The cpu/platform entries are taken from 2 other devices with the MediaTek X10 Helio SoC and should work. The file system entries can be made in several ways, but all the info. needed is available. There are loads of TWRP flags but not many of them are essential.

The next task is to try and figure out whether to use our own kernel or compile one using the TWRP sources.

http://xdaforums.com/showthread.php?t=2201860&page=489&nocache=1 post #4881

The attached files are the BoardConfig.mk so far, a file of various bits of BoardConfig.mk code that I've come across and my Allview post-OTA partition info. You can find your own partition info. in /proc/mounts, /proc/partinfo, /proc/partitions and by using the "DiskInfo" app.

Setting up a build environment

http://xdaforums.com/showthread.php?t=1943625&page=489 post #1012

How to compile TWRP touch recovery

http://xdaforums.com/showthread.php?t=1943625
[Blu Pure XL] xathras:
TWRP (2)

The story today -

I tried a build this morning, but all I could get from "lunch" was "invalid combo". After searching a dozen or more pages for info. on the lunch command I finally came across the command "choosecombo". This allows you to enter lunch options one by one. Why was this command only mentioned once???????

So now I know that when "make -j9 recoveryimage" fails it's because it can't find the device in the device tree. There's more to it than just creating device->allview->x2xtreme and dropping the "BoardConfig.mk" into it. Creating a device tree for a new device requires editing and/or creating several other files.

I've just found this link http://www.netmite.com/android/mydroid/development/pdk/docs/build_new_device.html for "Building Android for a new Mobile Device". There's a lot of good info in it, but I'm not going to get into it right now (my brain hurts!).
[Blu Pure XL] FuMMoD:
Good progress man! I feel you on the brain hurting thing haha. Take a break and think about other ways to approach it. This twrp route is a good lead for the moment. I need to setup my build machine again since my ubuntu setup got corrupted.
[Blu Pure XL] stryfe60401:
So Blu on Twitter stated that they will release kernels to people who request it through their technical support.
[Blu Pure XL] xathras:
TWRP

Sorry, I can't do this - it's outside my skill set. Best of luck to you all.:(
[Blu Pure XL] mhajii210:
Bounty

I think the best way is to start a bounty. Please see this link to see how it can be achieved http://xdaforums.com/one-m9/general/bounty-htc-one-m9-aosp-cm12-1-camera-t3193175.
[Blu Pure XL] FuMMoD:
That's funny since they gave me the run around through emails, twitter, facebook. :D
[Blu Pure XL] Techronico:
Has there been any progress since Nov 8?
[Blu Pure XL] thesticks00:
I would also like to know this. Not trying to rush anyone. I would just like to get an idea of the odds of us getting root on t his device. If root is not likely coming to BLU Pure XL, I will be forced to return the device to amazon and pick up a 6P. Fortunately I have 30 days to find out if we will get root (amazon return policy).