yashsingh1/xdaforums huggingface dataset:
[Blu Pure XL] acheron1502:
I got my grey phone on Monday and have been messing around a bit.

Could not get Helium to work on Widnows 7, but I do have ADB connection.

Using Ubuntu Linux, I was able to get Helium to connect last night. Had to follow the steps listed at the link below to setup the correct UDEV rules and adb_ini file. BLU Pure XL Vendor ID was 271d (two seven one dee).

http://stackoverflow.com/questions/12111005/how-to-register-this-tablet-to-ubuntu-udev-list

I've been trying to follow [MENTION=1632145]FuMMoD[/MENTION] and [MENTION=4015860]xathras[/MENTION] footsteps and see where we can go from here.

I finished repo syncing the Omni 5.1 branch last night as well to possibly build TWRP. Also fired off an email to Blu Service Dept on a whim asking for Sources or a Stock ROM ZIP to work with.

[MENTION=1632145]FuMMoD[/MENTION] & [MENTION=4015860]xathras[/MENTION] - Perhaps we can all work together to figure this thing out? I'm used to HTC devices and just unlocking bootloader via HTC Dev site.
[Blu Pure XL] FuMMoD:
If Blu releases sources I'm down to help out. There's so much locked down on the device St software level though. If only we could force the system to be read and write.
[Blu Pure XL] acheron1502:
FYI - your local_manifests.xml file might have a typo. I think you have an extra dash in the github link to the SaberMod Linux repo.
[Blu Pure XL] acheron1502:
I downloaded the TWRP IMG for the XIAOMI Redmi Note 2 that was posted earlier and ran it thru Android Image Kitchen.

Was able to extract the attached FSTAB file from it.

I think this looks like a good base for the TWRP.fstab file that we need...
[Blu Pure XL] jasonmastertech:
Im going to start a bounty thread to award the developer(s) who can successfully provide root & twrp recovery.
[Blu Pure XL] stryfe60401:
Blu sent me a pdf of how to get the kernel for the Pure XL. Haven't looked at it thoroughly yet. Will look and post it when I get home
[Blu Pure XL] stryfe60401:


---------- Post added at 03:13 AM ---------- Previous post was at 03:13 AM ----------

That's what Blu sent me. I don't know if it's useful.
[Blu Pure XL] axxtran:
Darn, I don't even see our phone when I connected
[Blu Pure XL] mhajii210:
If they sent you that it's definitely incorrect information. Our phone is not listed. I would suggest you kindly let them know.
[Blu Pure XL] stryfe60401:
Will email them first thing in the morning.
[Blu Pure XL] stryfe60401:
Emailed back, if you go on blu twitter account you can see my **** talk too. I figure they won't listen to polite talk.
[Blu Pure XL] Twista2k7:
I think after this pure experience this might be my first and last Blu phone
[Blu Pure XL] onemotodroid:
If folks would return their phones than Blu will get the message.
[Blu Pure XL] axxtran:
The only thing that is stopping me from returning this and grabbing a nexus 6 or 6p are the capacitive/ dedicated buttons. I'm far too used to having them haha
[Blu Pure XL] stryfe60401:
The phone isn't bad, it's just the ****ery by Blu that's annoying. I'm looking into the Vivo X6 or the Mate 8. I can't go back to anything less in size.
[Blu Pure XL] onemotodroid:
I also think the phone is great, its just not supported by Blu very well. Their has been no update since the first release. If root was available the small issues with the phone would be fixed.
[Blu Pure XL] Techronico:
What small issues?
[Blu Pure XL] onemotodroid:
Number one: all play store apps not running
[Blu Pure XL] BusySignal:
I'm starting to think Blu might not have the technical expertise to release any meaningful updates for the Pure XL. If you look at YouTube reviews of the Gionee E8, which our phone is based on, you'll see the OS, the interface, the apps, are exactly the same as ours. I could not tell what Blu changed other than the boot logo and the modem to support the US bands.

If Gionee doesn't update their E8, we might be SOL.
[Blu Pure XL] onemotodroid:
Blu has not updated the software on this phone. I can only guess that what you buy now is what you have to live with. No thanks!
[Blu Pure XL] onemotodroid:
Number Two: I was not able to get Android Pay to work.
[Blu Pure XL] mhajii210:
There is a way to get Android Pay to work. You have to install the HTC Sense Home launcher, use your data connection and not Wi-Fi, and then add a credit card. Please see this thread for more info http://xdaforums.com/pure-xl/general/doesnt-android-pay-sucks-t3231957.
[Blu Pure XL] lopestom:
After reading all the comments, I wonder if the users already have a custom recovery?

If not: Is there any experienced User to revive your phone with SPFT? Obviously I not see the stock ROM BLU phone. But how has the Allview phone is already something.

If someone has extreme confidence, experience and knowledge, PM me.
[Blu Pure XL] jasonmastertech:
Not rushing or looking for an eta from developers. Just curious...any new progress anyone can update us with in reference to root or custom recovery?
[Blu Pure XL] hamendezc:
blu pure life xl and gionee elife e7

I have a doubt, the feroxx user is working on a ROM-based omnirom 5.1-6.0 for Gionee elife e7; but I wonder if the Gionee elife e7 and blu pure life xl have the same components, I understand that the elife Gionee e7 works with two versions of snapdragon processor, one runs the msm8974 and the other 32GB LTE version runs with msm8974AB.

Feroxx version which no work and unfortunately because it is new can not post on the developer forum,

these data are the pure life xl

Modelo del dispositivo: BLU Life Pure XL

Tipo de dispositivo: Tabléfono

Fabricante: BLU

Modelo: LIFE PURE XL

Marca: BLU

Placa: MSM8274

Dispositivo: BLU

Hardware: qcom

Producto: BLU

RAM instalada: 3 GB LPDDR3

Memoria total: 2863 MB

Modelo de SoC: Qualcomm Snapdragon 800 (MSM8974)

Arquitectura del núcleo: 4x Qualcomm Krait 400 @ 2150 MHz

Proceso de fabricación: 28 nm

Conjunto de instrucciones: 32-bit ARMv7

Revisión de CPU: r2p0

Núcleos de CPU: 4

Rango de reloj de CPU: 300 - 2150 MHz

Resolución de pantalla: 1080 × 1920

Tecnología: LTPS LCD

Tamaño de pantalla: 68 mm × 122 mm

Pantalla en diagonal: 5,5 pulgadas

Densidad de píxeles: 401 ppp (xxhdpi)

xdpi / ydpi: 160 / 160 ppp

Vendedor de GPU: Qualcomm

Renderizador de GPU: Adreno (TM) 330

I'm sorry, I do not know English

Tengo una duda, el usuario feroxx está trabajando en una rom basada en omnirom 5.1-6.0 para el gionee elife e7; sin embargo me gustaría saber si el gionee elife e7 y el blu pure life xl poseen los mismos componentes, tengo entendido que el gionee elife e7 trabaja con dos versiones de procesadores snapdragon, uno corre con el msm8974 y el otro version lte de 32 gb corre con el msm8974AB.

No se cual version trabajo feroxx y lamentablemente por ser nuevo no puedo postear en el foro de desarrolladores,

estos son los datos de pure life xl

Lo siento no se ingles
[Blu Pure XL] ekeluo:
This thread is about the Blu Pure XL, not the similarly named but completely different Life Pure XL from last year. The Gionee equivalent is the E8
[Blu Pure XL] levchikb:
that is not a small issue my friend ... that is HUGE
[Blu Pure XL] mhajii210:
I have not had any problems with any Google Play Store app. The only app that didn't work for me was Android Pay, and all I had to do was change the launcher to get it to work. Not sure what he means by all Google Play Store apps not running.
[Blu Pure XL] acheron1502:
I have not touched this in a little while. I heard/saw somewhere that the Kernel Source might be released sometime this month, which would make this a bit easier.

Hopefully the source gets released and we can get Root and custom Recovery from there. If not, I plan on tinkering with this again in a couple weeks after I move into my house.
[Blu Pure XL] dexterxx:
Hi,

From here's another Allview X2 Xtreme user. Also still without success on root.

Trying to boot my device from uploaded by FuMMoD boot.img... tell me, It's neccessary to flash it? I've freeze on "downloading" after typing "flashboot boot h:\...\boot.img" and (at now) don't know what to try next...

Tried:

KingoRoot, KingRoot, iRoot, RootGenius, TowelRoot, FramaRoot, FramaRootPlus... ofc no luck. So now I'm trying now with adb/fastboot/recovery.

Also I've asked polish support on fb for some advice, still no answer ;) lol. - they won't help

Kernel: 3.10.72+

No. C: X2_Soul_Xtreme_0301_V5687 (latest)

If I may help... just tell. Right now more researches, learn & tries.
[Blu Pure XL] lopestom:
You can copy your stock recovery (pull recovery - example: adb pull *– Transfer file from Android device to PC.) and send it for trying create Custom recoveries.

Search/Learning on Google:

Search 1

Search 2

Is need too if the bootloader is lock. Search command: fastboot oem unlock
[Blu Pure XL] dexterxx:
I saw by getvars that bootloader is unlocked (there was discusion on one german forum where FuMMoD posts). I'll try to find time today to do that.

Is there are some dirs that I should ignore on copy/pack? I'm using that phone as my private ;)
[Blu Pure XL] lopestom:
Since there is no stock ROM for Allview (but there is an updating file. I believe not help.) BLU and Gionee devices, then all users should be careful that you are not brick.

For the Custom recovery I already have the boot.img file that Allview file. But it is also necessary recovery.img and know the partitions of system / data / cache for flashing correctly on your phone.

Obviously with ROOT everything would be more interesting. Even if someone knows a lot of development, something wrong can happen. Therefore, one should be careful about what we do.

At first time stock boot.img and recovery.img may already be of great use.
[Blu Pure XL] lopestom:
About file x2.rar 1.2GB: have recovery.img?

If yes, can you only upload recovery.img?!

If no: that file is same to other file on other post?

If that file is update from Allview and have boot.img and files on the folders called ****....p

So it's protected for only stock recovery flashing.... Cannot modified that...

If the informations is from your phone So that's very good...:thumbup:
[Blu Pure XL] dexterxx:
There's no recovery in there (I think so). As I posted before, I could not access recovery or boot block: /dev/block/platform/mtk-msdc.0/by-name/ (can't dd by chmod configuration from factory_init).

Pack contains almost all files which I was able to adb pull from device.

Any advice what to do now?

What's the problem to create like-stock update zip for recovery? We need to sign it with private key, which we dont have, am I right? (I'm still noob, last days I'm reading as many as I can).

edit:

BTW I figured out why "downloading" freezees with my fastboot - just changed USB port and cable fixed issue ]:->

But I can't boot it with any boot.img I have... (E8_amigo3.1.6_T3097, this post's hacked, 66d0c1f4c2dfe8abab357b3d5e6550bb) :(

downloading 'boot.img'...

OKAY [ 0.457s]

booting...

FAILED (remote: unknown command)
[Blu Pure XL] spit85:
I found some firmware on the amigo os website. They have build the whole rom for the gionee e8. It looks the same as from the allview x2, only in Chinese.

Under the link below you can choose between three firmware versions.

http://www.amigo.cn/mobile.php?id=39

Just use Google translate to translate the website, and you find the download links.

Hopefully on of the three versions is complete and has a recovery image included. I downloading the latest version at the moment, but the downloadspeed is very slow.

Verstuurd vanaf mijn X2_Soul_Xtreme met Tapatalk
[Blu Pure XL] lopestom:
Well. Any User should take care not to delete any of the ROM.

On the part of private key: this is not important because we need not to create a custom recovery. But the META folder may be interesting.

I read a long time ago that some users were able ROOT installing SUperSu with the update.zip file. They just changed/included the lines in the update-script file and made flash with the stock recovery. But that was for another phone with different Soc than yours. So I have my doubts.

In addition, perhaps the issue of not having the ADB_insecure as done in the boot.img file made by FuMMod, may be blocking any access to your phone.

For now, as you wrote that has its main phone, better is to have patience and read more about another way to get ROOT. The main and best to have the recovery.img file.

I could even take a test file catching kernel on the boot.img file and put in Custom recovery of Xiaomi Redmi Helio so that someone could test. Without guaranteeing a have stock recovery, I will not risk any wrong action.

If you or other user have a access for stock recovery file so.... Upload that and we can made any progress...:cool:
[Blu Pure XL] dexterxx:
I've used UPDATE-SuperSU-v2.46.zip.

1. Changed CERT.RSA with that from 66d0c1f4c2dfe8abab357b3d5e6550bb.zip

2. Added to update-script first line

getprop("ro.product.device") == "X2_Soul_Xtreme" || abort("This package is for \"X2_Soul_Xtreme\" devices; this is a \"" + getprop("ro.product.device") + "\".");

3. Added whole META-INF/com/android

4. Changed name to update.zip.

No luck as I expected. I think we need to decompile update-binary to look wha's happening there.

In latest E8_amigo3.1.6_T3097.zip there's only 1KB recovery.sig greping by "recovery". Now I'm donwloading amigo3.1.1 cuz it looks on page like it have +=10MB ;)

edit:

In older package same situation. BTW compare:

edit2:

Another question, does Mtk_Droid_Tool_v2.5.3 (and olders) connect's with your phone? I can't... also when using buildin adb terminal - can't see my device. Using Minimal ADB and Fastboot package anything works fine....

Current my latest idea is somehow by recovery move /data/local/tmp/ (su, Superuser) to /system/bin... any idea how to do that ;) Think abstract! hehe...
[Blu Pure XL] spit85:
If I pause the virusscanner on my computer, mtk droid tools recognize my phone. If the virusscanner is on, mostly mtk droid tools doesn't recognize my phone. But I can't create a scatter file with mtk droid tools, or root the phone with it.

I felt asleep, so I haven't take a look at the firmwares. Lol

And move the su binaries to the bin folder doesn't work. I tried it, but I can't remount it to r/w.

I break my brains later. Now I wake up. Lol
[Blu Pure XL] acheron1502:
Hey [MENTION=4424265]dexterxx[/MENTION] ... you have a file that we do not in your /system/xbin called amigosu !!

Perhaps you have the tools to run commands with elevated access ?
[Blu Pure XL] acheron1502:
We have root !!

UPDATE 4: WE HAVE ROOT! :highfive: Files are at bottom of the post.

UPDATE 3: Scatter V3 - fixed dyslexic typos for the TEE2 partition ( thx [MENTION=4424265]dexterxx[/MENTION] )

UPDATE 2: added NVRAM.img and Scatter file V2 that adds a missing FRP partition information

UPDATE 1: added SYSTEM.img link to bottom ... it is a very large file

I might be getting somewhere here...

I was able to dump the Boot.img and Recovery.img from my BLU Pure XL tonight!

Using SP Flash Tool v5.1540.00, the correct VCOM drivers for the Gionee E8, and the attached scatter file that I made, I was able to use the Readback function to dump the Boot and Recovery partitions.

(Scatter file is a modified Xiaomi Note 2 scatter file with partition start addresses and lengths that match my phones data from /proc/partinfo)

Then you can use Android Image Kitchen to unpack the images into RAMDISK and SPLIT_IMG folders.

All links are to Android File Host

BLU_PUREXL_MT6795_Android_scatter_v3.txt

WE HAVE ROOT

Boot into Bootloader

Flash TWRP using "fastboot flash recovery <recovery.img>"

Reboot to TWRP by "fastboot reboot" then holding VOL+

Flash SuperSu zip file to complete root process

BLU_PURE_XL_TWRP.img

SuperSU v2.46 zip
[Blu Pure XL] dexterxx:
Woooohooo, congrats!

BTW gread reasearch, but....

How to use it :D

I'll try later, after job.

> amigosu -v
16 com.gionee.systemmanager

edit:

Is there any "whoami" in Android? Also tried 'amigosu root' but still no grants :(

edit2:

amigosu 50kB, real su 372kB...
[Blu Pure XL] lopestom:
It's time to progress...

Amjgosu should have only simple permissions by Amigo application...

No real Su file...

But now with that files is very important to all users can revive the phone.

Important too saving the NVRAM folder from device.

I go unpack custom recovery by Xiaomi Helio and repack with the information by your files..After with time put link here for anyone test....
[Blu Pure XL] dexterxx:
God damnit. I can't connect my device with MTK Droid Tools... trying and trying, no luck. (adb 1.0.31 from latest MTKDT can't see my phone... adb 1.0.32 from Minimal ADB and Fastboot works good. Tried to replace adb.exe but then MTKDT not works :x Also tried many drivers, w/out success...)

May I use your's scatter file? How to figure values to

linear_start_addr

physical_start_addr

partition_size

?

Values from /proc/emmc not looks enought similar :P

edit:

Nevermind :P emmc_p7: 0000e900 00008000 "boot"

e900 x block_size: 0x20000 = linear_start_addr: 0x1d20000

same as in Your scatter ;)

edit2:

Diff in my case:

partition_name: tee2

partition_size: 0xc60000 [not 0x6c0000]
[Blu Pure XL] acheron1502:
My values for the Scatter were pulled from /proc/partinfo.

Be sure to grab Scatter V2 from my post. It has FRP partition that I skipped over last time.

MTK DT has issues if you phone is in MTP mode. When I switched to just PTP mode it connected.

However, I have not tried using this to root the phone as it doesn't really support MT6795 yet. (and we dont have a stock ROM zip)

I've been using SP Flash Tool to Readback the partitions using the VCOM driver.
[Blu Pure XL] dexterxx:
Look at my edit2 in post above, I've recalculated my addresses and I found difference. I've used v2.

Looks like I did it... I was able to unpack both img's with kitchen. What's next?

Allview_X2_Xtreme_0301_V5687_SYSTEM.zip

7c4fe7bcb26464bc8bc1fa1f9f268524 *Allview_X2_Xtreme_0301_V5687_BOOT.img.zip

bef0f26daa6a24c80a85b5fe355b5fcc *Allview_X2_Xtreme_0301_V5687_RECOVERY.img.zip

e16e0bce2d3554b3546ca80db6471daf *Allview_X2_Xtreme_0301_V5687_SYSTEM.zip
[Blu Pure XL] bemolx:
I'll try to edit this boot.img to get insecure boot. Thanks for uploading this IMG

Sent from Nexus 5
[Blu Pure XL] lopestom:
Hi guys,

Today I had a little time for see your files recovery.img

So you can see the difference of Files from each device. Look attached file.

Maybe Allview have a next version updated bcoz Allview brand release update.zip than BLU....

I'm make some progress to create Custom recovery. But is need any user that have guarantee and knowledge to test and if not work know how to flash stock recovery again.

I need know who want test.
[Blu Pure XL] dexterxx:
I think I'm to big coward... but if I'll have warranty that I won't brick phone - I may try :P

Right now when I have my img'es I may flash it back any time? Except when recovery may modify something outside that...

What big is risk?
[Blu Pure XL] lopestom:
It all depends on how and what the User does.

I want to make clear that not have the phone in my hands. I'm here to help and maybe have donation....

If I had one Pure XL / Allview X2 Xtreme on my hands, I would test myself. Everything would be easier.

Cannot give you security. But I can say that if you know the progress that has been made out so far with access fastboot / adb - scatter file for SPFT, then with the files already placed in each post, it seems that you have conditions to revive the phone in case something goes wrong.

Some considerations: whether the phone has bootlooader unlocked (that wipe your data);

understand that each company may have modified a file or address block on the phone;

Be aware that the decision is yours and you can have two results: SUCCESS or problems (some easy to solve and others not).

So if I do a Custom recovery test file, I will do for each phone BLU and other to Allview. I saw that the kernel is different in every recovery-boot of the two phones.

What happens if the test file could not succeed?

First the phone will restart several times. But will not the system the first time. In this case, the phone will turn on after restarting a few times.

Remember to always have good battery power (70% ~ 100%).

In this case, you will be able replace the stock recovery with fastboot / adb / spft again.

But if the phone does not go back:

Staying on the logo: reflash stock recovery is device restart.

Do not connect more: reflash rom stock and stock ROM.

Even so it may be that no go on (soft brick).

I even doing a test file for many BLU users and other brands, many files were not successful the first time. But I guarantee that if you hold the flashing process correctly, will be able to have the case reset the phone and finally he had restarted.

Finally, it will be able to succeed with a Custom recovery or just reflash your stock recovery.

Any decision is the User own responsibility!!
[Blu Pure XL] acheron1502:
WORKING TWRP LOCATED HERE

[MENTION=4939713]lopestom[/MENTION] - I'd be willing to test the Blu recovery you make.

I attempted last night by combining file from my stock recovery and the one from HTC E9 that was posted earlier... but not sure if I did it correctly.

WARNING - NOT TESTED - WARNING

posting for comparison purposes only

BLU_PURE_XL_TWRP.img

WORKING TWRP LOCATED HERE

File size seemed to line up with stock recovery when repacked, but I've never ported a recovery image this way :confused:
[Blu Pure XL] lopestom:
If other device have same architecture (MEDIATEK Soc) and others regular specs...so maybe work.... Is very need put your kernel and others lines to start and look address blocks!!

Downloading now for look...

But only look really on 3h...

Warning: Not make any actions with doubts!!
[Blu Pure XL] acheron1502:
I misspoke earlier ... I used the TWRP image for Xiaomi Redmi Note 2 (xiaomi hermes) which uses same MT6795, so it should be okay to use for porting.

Awaiting your test build of TWRP for the BLU Pure XL to test. *crosses fingers that it comes close to my attempt*

FYI - I updated my Scatter File in my POST to fix a typo in the TEE2 partition.
[Blu Pure XL] bemolx:
FOR

ALLVIEW X2 XTREME

ONLY

I made a insecure boot.img that allows us to put root files etc. on phone's system partition.

To check if my IMG works follow these (of course bootloader must be unlocked):

- Enable ADB Debugging

- Reboot device to bootloader & only "fastboot boot new_boot.img"

- Once booted - "adb shell"

If you see something like: "root@android:/ #" we've got it! Now you can flash this boot.img to do further modifications.

If you failed obtaining root, report it back

as I can fix this IMG. I don't have this device on my own now so I can't check it myself. I can not guarantee that will work perfectly.

Good luck ;)
[Blu Pure XL] spit85:
It worked for my allview x2 xtreme. And I was able to install supersu from chainfire. My phone is finally rooted.
[Blu Pure XL] bemolx:
Does it work after reboots etc.? Any root app works?
[Blu Pure XL] dexterxx:
spit85, which method - fastboot flash or sp tool? fastboot boot works for you? I can't still skipy above

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot h:\X2\my.backup\BOOT.img
downloading 'boot.img'...
OKAY [ 0.841s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.852s

Damn.

What's the difference vs bemolx image?
[Blu Pure XL] lopestom:
[MENTION=4546066]spit85[/MENTION]

Have you confirmed TWRP working?? Version??

You tested:

- backup

- restore

- install file from sdcard

- wipes

:confused:

Confirm if work and your device pls....:rolleyes:
[Blu Pure XL] acheron1502:
In your image:

Default.prop

- ro.adb.secure is still set to 1

- ro.secure is still set to 1

fstab.mt6795

- /system is mounted as ro instead of rw

Not sure if this boot image will allow permanent root, but I cannot check as I have the BLU phone.
[Blu Pure XL] bemolx:
Damn.. I've set it before re-packing this.. Anyway I'll try again