yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] :
Vibe ui? it's good, although i prefered stock 5.0, this one is the best from all three ported Vibe ui roms.

http://bbs.elephone.hk/thread-4436-1-1.html#.VWHDS0_tmko
[Android Q&A, Help & Troubleshooting] Some Devil:
Installed the one I posted link to, works like a charm.

P.S. I had stock 5.0 and it had some glitches/screen flickered, vibe 2.5 tho doesn't have these bugs (atleast after few hours of testing)
[Android Q&A, Help & Troubleshooting] :
Hmm? Your Blaster came with official 5.0? or you flashed it?
[Android Q&A, Help & Troubleshooting] Some Devil:
I flashed it (P6000 5.0 official ROM) from link in your main post and then flashed vibe ui 2.5 rom through cwm
[Android Q&A, Help & Troubleshooting] :
Hah and i thought that i missed some Just5 update. :D anyway did you flash this too?

https://onedrive.live.com/redir?res...5722&authkey=!AH0Lby_Znhqq2PQ&ithint=file,zip ( i removed sdcard swap, as i thought it isn't needed)

These mods were made by [MENTION=4056517]HypoTurtle[/MENTION]

More info...

http://bbs.elephone.hk/thread-3981-1-2.html#.VWR7vk_tmko

---------- Post added at 05:23 PM ---------- Previous post was at 04:59 PM ----------

Updated Main discussion Post!
[Android Q&A, Help & Troubleshooting] Some Devil:
Nope, I didn't. Most of these fixes are useless for me, since I don't use the features they fix :D And I already have this recovery installed. But thank you for the link, I'll maybe install xposed later
[Android Q&A, Help & Troubleshooting] Sasha_Baron:
Problem with sp flash tools

How did you flash cm 12.1? I read that you have to use sp flash tools, but you haven't mentioned that. I tried to flash with it, but when i pressed download and connected my blaster without battery, nothing happened. Hope you can help :).
[Android Q&A, Help & Troubleshooting] :
Hi there is loads of tutorials in bbs.elephone.hk about flashing
[Android Q&A, Help & Troubleshooting] T__K:
Greetings!

Can you confirm how well do BlueTooth and USB keyboards work with Blaster? ...And with how many |what hidden caveats? :)

That should be relevant to developing with the device.

Thank you!

All the Best!
[Android Q&A, Help & Troubleshooting] Some Devil:
has anybody tried "150622 Update！Elephone P6000 VIBE_2.5 Multilang【Android 5.0 Lollipop】" (can't post links, but you can find it on bbs.elephone site)? It says i need to upgrade using sp flashtols, but i'm kinda afraid of bricking my device.
[Android Q&A, Help & Troubleshooting] :
Yeah i tried, not worth it, wait for official 5.0, I would be on stock also, but my backup seems faulty.
[Android Q&A, Help & Troubleshooting] Some Devil:
Official you mean by just5 devs or elephone?
[Android Q&A, Help & Troubleshooting] :
By just5, Kristaps Skutelis confirmed that there will be update to 5.0, somewhere is the link to his twitter account, in which it shows Blaster running 5.0.
[Android Q&A, Help & Troubleshooting] Ruldis:
Official 5.0 update

Hey there!

I've been bugging just5 for about two months now - and here's what I got out of them (answered on their FB page):

"Būs iespējams atjaunināt Blaster 4.4 uz Lollipop sākot no 01.08. Just5 veikalā Brīvības 40, Rīgā"

From this I conclude that there will be no OTA. I will have a look myself Saturtday and see for myself how they manage the update, I can update you on the matter if you wish.
[Android Q&A, Help & Troubleshooting] dl06007:
Can you upload official blaster Lollipop backup?
[Android Q&A, Help & Troubleshooting] Ruldis:
I paid their showroom a visit today, unfortunately none of the "service" members was there, so I was told to wait till Monday (Aug 3rd). The wait is on till then, once I get it - I'm sure I could.

On a side note, seeing how the Blaster 2 is practically identical to Blaster I think that's what I'm going to get at their office. It won't be an upgrade as I was told, but a full fresh install. Regardless - have to wait till Monday...
[Android Q&A, Help & Troubleshooting] dl06007:
PS. would be nice if you could upload official blaster kitkat 4.4.4 backup and official lollipop 5.0 backup for SP flash tool.
[Android Q&A, Help & Troubleshooting] mite_jan:
Please do a backup from the blaster 2 lollipop

And tell us are the gestures there and is the interface smooth

This is our only hope since Elephone doesnt give a damn about us
[Android Q&A, Help & Troubleshooting] spaceman740:
News about 5.0

I`we send an email to user-support

And they answered. that the update can be made only in the showroom in Riga
[Android Q&A, Help & Troubleshooting] dl06007:
but if I already rooted the phone and flashed 5.1.1?
[Android Q&A, Help & Troubleshooting] Ruldis:
sorry - already have the update applied, haven't been able to get online in the past days.
[Android Q&A, Help & Troubleshooting] dl06007:
nice! waiting for 5.0 backup :)
[Android Q&A, Help & Troubleshooting] Ruldis:
Right, so I got it

[IMG="Blaster L"]http://http://xdaforums.com/picture.php?albumid=12374&pictureid=49828[/IMG]

[IMG="About"]http://xdaforums.com/picture.php?albumid=12374&pictureid=49829[/IMG]

Couple of things to note:

1) You can only get the update at their office - no OTA for Blaster upgrade

2) The update takes ~15min in total. While I was waiting - I played around with the Blaster 2 model - which had an app (can't exactly recall the name) that dealt with updates over WiFi - OTA respectively.

Speaking of the L backup - I think I'll need help on this one as I am not exactly sure as to what kind of backup you guys are asking for.

P.S.

The gestures, as far as I've checked them are smooth, overall - I'd say the performance has improved.

What I've noticed so far:

1) No more resolution restrictions on the camera (full HD 1080p is now an option in the Google camera)

2)GPS is now much faster - am yet to check accuracy.

---------- Post added at 07:58 AM ---------- Previous post was at 07:53 AM ----------

I'm afraid I'm stuck for now - can't get this thing rooted..
[Android Q&A, Help & Troubleshooting] bigrammy:
I think you will need a valid scatter file for that :confused:

You could try the KitKat and Elephone LP one's but if they changed any partition size it will give you an error. :(

Maybe adb shell was left open and will still work :fingers-crossed:
[Android Q&A, Help & Troubleshooting] Ruldis:
Well I'll have to call it quits for now, I was thinking of the scatter file, yes... but that's a tat above the level of my competence with android in general. :confused: I wasn't able to root it or get a custom recovery going - I'll have a look around and try again.
[Android Q&A, Help & Troubleshooting] HypoTurtle:
The stock ROM backup of 4.4.4 is found here from OP. Just scatter is missing - one from the P6000 should work.

For 5.0 backup does anyone have adb access, does the phone have fastboot when pressing Vol up & Power from off. And anyone have SPFlash installed and know it works/connects?
[Android Q&A, Help & Troubleshooting] Ruldis:
I attempted that... and it just gives out some gibberish I cannot read (Chinese I guess). I may be doing something wrong, but I can't get the adb access. From where I am - I don't have any of the above mentioned connectivity.
[Android Q&A, Help & Troubleshooting] HypoTurtle:
The chinese menu sound like factory mode - did it say something like PCBA at the top?

If Vol Up gets to PCBA - what does Vol Down do? It will either be a menu (recovery/fastboot/normal) or will boot into stock recovery - I guess.

If you have adb installed you might just need to add the vendor_id to a file (C:/Users/${Username}/.android/adb_usb.ini). The MTK vendor_id is 0x0e8d) but Just5 might have a different one - USBDeview will be able to show you it.
[Android Q&A, Help & Troubleshooting] Ruldis:
ok my bad - what I entered was factory mode then, I have a silicone case - and I guess I was clumsy enough to press the wrong thing POWER + UP opens a menu where you can choose recovery/fastboot/normal. The recovery does nothing, just throws out an error, normal - proceeds to normal boot. I'll have to check adb and fastboot.
[Android Q&A, Help & Troubleshooting] HypoTurtle:
Was recovery error something like: No commands sent.... If so I'd take that as being stock recovery - it's only really supposed to used for installing OTA updates (if there are any) - and to factory reset/encrypt device etc. i.e. commands are sent from system (or bundled within a .zip shell) that the stock recovery reads. If you press the power button again while in recovery you should get a menu on screen.

Let me know if you get adb/fastboot running: from fastboot I would run fastboot getvar all; from adb cat /proc/partinfo from either of those we should be able to create/modify a proper scatter.txt for the partition layout.
[Android Q&A, Help & Troubleshooting] Ruldis:
fastboot getvar all gives me this:

(bootloader) max-download-size: 0x8000000

(bootloader) partition-size:userdata: 32000000

(bootloader) partition-type:userdata: ext4

(bootloader) partition-size:cache: 1a800000

(bootloader) partition-type:cache: ext4

(bootloader) partition-size:system: 80000000

(bootloader) partition-type:system: ext4

(bootloader) partition-size:metadata: 2460000

(bootloader) partition-type:metadata: raw data

(bootloader) partition-size:tee2: 500000

(bootloader) partition-type:tee2: raw data

(bootloader) partition-size:tee1: 500000

(bootloader) partition-type:tee1: raw data

(bootloader) partition-size:expdb: a00000

(bootloader) partition-type:expdb: raw data

(bootloader) partition-size:custom: 12c00000

(bootloader) partition-type:custom: ext4

(bootloader) partition-size:logo: 800000

(bootloader) partition-type:logo: raw data

(bootloader) partition-size:para: 80000

(bootloader) partition-type:para: raw data

(bootloader) partition-size:secro: 600000

(bootloader) partition-type:secro: ext4

(bootloader) partition-size:recovery: 1000000

(bootloader) partition-type:recovery: raw data

(bootloader) partition-size:boot: 1000000

(bootloader) partition-type:boot: raw data

(bootloader) partition-size:lk: 60000

(bootloader) partition-type:lk: raw data

(bootloader) partition-size:seccfg: 40000

(bootloader) partition-type:seccfg: raw data

(bootloader) partition-size:protect2: a00000

(bootloader) partition-type:protect2: ext4

(bootloader) partition-size:protect1: a00000

(bootloader) partition-type:protect1: ext4

(bootloader) partition-size:nvram: 500000

(bootloader) partition-type:nvram: raw data

(bootloader) partition-size:proinfo: 300000

(bootloader) partition-type:proinfo: raw data

(bootloader) partition-size:preloader: 40000

(bootloader) partition-type:preloader: raw data

(bootloader) off-mode-charge: 1

(bootloader) warranty: no

(bootloader) unlocked: yes

(bootloader) secure: no

(bootloader) kernel: lk

(bootloader) product: K01Q_E

(bootloader) version: 0.5

all: Done!!

finished. total time: 0.016s

Which I assume is a good thing :D Speaking of the error - on the 4.4.4 custom recovery had a constant dead android icon in the background with the "no command...", and the power button just switched the menu on and off. Now... it would seem that there simply is no recovery, because it just shows the dead android.
[Android Q&A, Help & Troubleshooting] HypoTurtle:
Yea looks like custom and metadata partitions are larger (space taken from userdata); should be able to make a scatter from that - having the adb command would make it easier though.

You might be able to get something in stock recovery messing with the power/volume buttons - I'm sure there's something there...

Edit: Oh and try flashing the custom recovery through fastboot "fastboot flash recovery recovery.img".

EDIT 2: Scatter attached based on fastboot values
[Android Q&A, Help & Troubleshooting] mite_jan:
Mtk droid tool anyone?

Create the scatter file with that program (not sure if it will work without root) but even if the phone doesnt have root this program can try to root it

[YOUTUBE]YZFO5WIyES8[/YOUTUBE]

If you need root first try kingroot or framaroot (newest version)

http://androcontent.blogspot.gr/2015/05/root-any-mtk-lollipop-running-phone.html?m=1

Edit

You can create the scatter file without root with mtkdroid tools, from there it should be easy
[Android Q&A, Help & Troubleshooting] dl06007:
cant create from mtkdroid, button greyed out.
[Android Q&A, Help & Troubleshooting] mite_jan:
If you have usb debugging enabled on the phone and the ADB driver installed when you connect the phone with the cable the program should give you info for the phone and BLOCKS MAP shouldnt be grayed (try runnong as administrator aswell)
[Android Q&A, Help & Troubleshooting] bigrammy:
Yes bro that's good :good:

Thanks for taking the time to do that bro let's hope it works :fingers-crossed:

If adb is working I think there will be no problem pulling the partitions. :good:

MTKDroidtools will not do that for our SoC :crying:

[MENTION=6855800]Ruldis[/MENTION] thanks for your time bro you must be feeling the pressure a bit. :eek:

We have waited so long now for a good Kernel everyone is very eager to get their hands it :D

If you get any problems with SPFlashtool then just try these following adb cmd's :fingers-crossed:

Ensure debugging is on

Run these from the cmd prompt

adb shell

Then

dd if=/dev/block/mmcblk0p8 of=/sdcard/recovery.img

This will pull the recovery to your sdcard 16MB.

Then

dd if=/dev/block/mmcblk0p7 of=/sdcard/boot.img

This will pull the boot to your sdcard. 16MB.

It may or may not work depending on how tight they locked it down. :fingers-crossed:
[Android Q&A, Help & Troubleshooting] mite_jan:
Didnt knew that mtkdroid tool doesnt work for our soc

Itallian guy made mtkdroid alternative called spacemtk tool especially designed for that soc

Download link

http://chinagadgetsreviews.blogspot.gr/2015/07/download-spacemtktool-v110.html?m=1

I am pretty sure you can root the phone with iroot former vroot

You just need usb debugging and adb driver
[Android Q&A, Help & Troubleshooting] HypoTurtle:
Will only work if stock rooted I'd guess...

What I'd do to keep a full copy of stock is readback the full ROM_0 with SPFlash (to manually split later if needed) - or just nvram & recovery. Then flash one of the P6000 recoveries - and make a ROM backup; install superSU etc.
[Android Q&A, Help & Troubleshooting] bigrammy:
adb shell has worked for me before on non rooted devices also, sometimes you do need to boot to recovery for it work. I think it all depends on the adbd version that's used in the boot or recovery.img It's easy to try it regardless :laugh:

SPFlashtool is the guaranteed way to go but as we know some people have real problems getting it to work if they are new to MTK :eek:

I would of thought the elephone LP custom recovery's would work anyway as long as the android version was the same :confused:
[Android Q&A, Help & Troubleshooting] HypoTurtle:
It's the dd part that I think needs root to read from the /dev's; and yea proper recovery adb shells drop straight into root # shell so no problem there anyway.
[Android Q&A, Help & Troubleshooting] Ruldis:
I will be giving this a go, however, as much as I hate to be doing this, you all will have to wait another bit. I'm going off world in terms of network coverage (yes, this country still has places where one bar of network is worth gold) for the next 3-4 days, and I won't be able to do much from there. :( I'll give it a go once I get back. I really apologize for kicking your hopes up like this, I'm not dropping this though, very much interested in pulling this off! :angel:
[Android Q&A, Help & Troubleshooting] bigrammy:
:crying: :crying: No problems bro we understand ;) and thanks for your efforts so far :good:
[Android Q&A, Help & Troubleshooting] fcuk:
How to activate stock recovery in Blaster's stock lollipop:

1) Reboot with volume up and power button both pressed.

2) Choose recovery mode

3) When dead android appears press both vol up and power button again
[Android Q&A, Help & Troubleshooting] mite_jan:
Desperately waiting for that backup :)

I have the phone 3 more days with me
[Android Q&A, Help & Troubleshooting] bigrammy:
Finally someone got the boot.img

Finally someone got the boot.img :victory:

Just need 4pda member to download it :o

4pda forum post here
[Android Q&A, Help & Troubleshooting] mite_jan:
boot img from 4pda , just unzip it

testing right now
[Android Q&A, Help & Troubleshooting] HypoTurtle:
Already done: TWRP (with touch)

Vibe 2.8 boot.img with Blaster2 kernel
[Android Q&A, Help & Troubleshooting] mite_jan:
so except for the touch recovery what do we get with this ?

i have flashed it and i dont know if it is placebo but touch is not jumping like previously
[Android Q&A, Help & Troubleshooting] HypoTurtle:
I haven't checked yet but we should have off screen gestures (as the VibeUI supports it on the system side). This is a tad off topic here as this is a Blaster Q&A.

For the Blaster what it means is that the Blaster2 is likely just a Blaster1 with a 5.0 ROM preinstalled (there might be an included new screen firmware driver as well as the samsung camera - but not 100%; irrespective the zImage is a tad smaller than the P6000's).

The reason I think there might be an additional touchscreen driver is that the 5.0 recovery with P6000 kernel wouldn't boot - still waiting feedback on the recoveries with the Blaster2 kernel - there could be something different with the partition layout etc. that's causing the recovery not to boot...
[Android Q&A, Help & Troubleshooting] mite_jan:
i have checked the twrp that you have provided and everything works

i am back on stock firmware so no screen gestures for me (btw i have found why was the interface laggy , i had to disable Antialiasing from engineering mode)
[Android Q&A, Help & Troubleshooting] Ksantor:
Just5 BLASTER with Android 5.0 (OS details)

Ok, so I've updated my BLASTER to Android 5.0 in the service center (Riga, Latvia).

One note: after about 30 min I gave my device to one of the employees, he (employee) came back and told me, that after OS update (flashed the ROM obviously), the "back" button on the screen (the right one) stopped responding. He also told me, that they will replace the screen on the device. After the screen had been replaced, everything is OK now.

As this is my first post, cant include any links (I guess).

If I'll be banned for this, well, so be it! :)

Device info screenshot (sort of direct link) - https on goo.gl/photos/Y5qrJ4oRmnvgMR7i7
[Android Q&A, Help & Troubleshooting] mite_jan:
we already know this info :)

it is useless to us in this condition
[Android Q&A, Help & Troubleshooting] Xabadou:
I tried Blaster boot.img patched on Modstockv3 (from 4pda) for P6000:

Bootloop.
[Android Q&A, Help & Troubleshooting] mite_jan:
for me it works perfectly fine
[Android Q&A, Help & Troubleshooting] Xabadou:
The original boot.img from Just5 Blaster or patched one?
[Android Q&A, Help & Troubleshooting] mite_jan:
boot.img from blaster 2 lollipop
[Android Q&A, Help & Troubleshooting] Ruldis:
I'm back, ready.

Hello y'all!

So I'm back from my trip to the depths of nowhere, and as I've noted - I've missed out on a few things while I was gone.

For now I am absolutely stuck at the root phase - tried everything I know and could find:

genius root

framaroot

kingroot

iRoot

Do not work

- also tried a few other methods that I can't recall right now - nothing. Can't really get things going without root, or maybe it's my incompetence... probably the latter :D

What I need to know now, I guess, is if the backup is still needed (really sorry for the added delay), and can it be made without actually having root access (which I understood, is possible, but I couldn't quite pull it through, I'm sort of basic on this, sorry again)
[Android Q&A, Help & Troubleshooting] mite_jan:
i think russian fellow got root through this recovery that Hyper Turtle provided

you can use the scatter that he attached in some previous post

or use mobileuncletools an flash the recovery from there

View attachment CWM_Just5B2.img

flash supersu through recovery

View attachment UPDATE-SuperSU-v2.40.zip
[Android Q&A, Help & Troubleshooting] Ruldis:
Will have a go at that now. Before I start, tho, any point in pulling the stock recovery?
[Android Q&A, Help & Troubleshooting] mite_jan:
not really except if there is OTA which just5 doesnt do anyway
[Android Q&A, Help & Troubleshooting] Ruldis:
The Blaster 2 has a dedicated app that manages potential OTA's, but there is no such app or functionality in the updated Blaster.

What's with the recoveries available in mobileuncle? Any good?

Should I flash your CWM or HypoTurtle's TWRP?
[Android Q&A, Help & Troubleshooting] mite_jan:
dont know about recoveries in mobileuncle from internet but you can add local recovery just add the recovery.img file on the sdcard (internal storage) and it should read it on the top

both recoveries are from hypoturtle so both should work probably
[Android Q&A, Help & Troubleshooting] HypoTurtle:
A backup without rooting would be preferable. Using SPFlash - the scatter on the previous page and Readback - (might need root to backup the preloader).
[Android Q&A, Help & Troubleshooting] Ruldis:
I've got CWM recovery going - works like a charm, many thanks for that, rooting won't be a problem now if backing up without root fails. :)

I'm going to give the backup a go right now, give you an update.

UPDATE: in mtk tools I get an error: " --- ERROR : --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!! ...which kind of stops me from doing anything else - any ideas?

ODD: under "Phone Information" it says that I'm running 4.4.4 - am I missing some drivers or something?

---------- Post added at 05:15 PM ---------- Previous post was at 04:19 PM ----------

"The preservation folder on the computer: C:\Users\rozalijs\Desktop\Blaster Project Files\MtkDroidTools\backups\p6000_700101_backup_150812-201334\

--- The SD card in phone isn't found!

--- We keep blocks:

- nodl_proinfo - ERROR : Zero file, no space left on device!

--- We keep folders contents copying on PC

- /system

--- task end with ERROR ---"

This is what I get when I try to first start the backup.
[Android Q&A, Help & Troubleshooting] HypoTurtle:
I wouldn't do the backup with MTK Tools - just stick with SPFlash - there is a Space MTK Tool that might work but I can't find a link to download it.

In SPFlash; you need to go to click:

Readback

Add

Double click on long file name (.../ROM_0)

Name it what ever you want and click save

Fill in start address and length then click OK

Click on Read Back and connect the phone

You could add all the 20 partitions and backup - using the scatter to get the start address and length - but keep the nvram.img etc. to yourself. Or just readback system and nvram - the others can be taken from the running device after rooting

(some of the partitions are blank so don't really need backed up - you'd be fine with the partitions seen in the Download page of SPFlash and nvram)​

NVRAM: Start address - 0x380000 Length - 0x500000 that's 5MB in size

SYSTEM: Start address - 0x1b000000 Length - 0x80000000 this is 2GB
[Android Q&A, Help & Troubleshooting] Ruldis:
uuuuu - wowowoow, slow down there...

no idea what nvram.img is :confused:

the scatterfile made and posted here gives me 11ish partitions :confused:

what mode should the phone be connected in? :confused:
[Android Q&A, Help & Troubleshooting] HypoTurtle:
Nvram has stuff like your imei numbers - it's specific to your individual device so it's handy to have a backup somewhere.

If you look at the scatter in notepad for example you will see all the partitions (the other 10 are 'hidden'). You only really need the 11 shown if you want to restore back to stock - the others are either blank or would typically never be changed (except by using Format All & Download in SPFlash).

You used SPFlash to install the recovery right? In any case the phone just needs to off and connected after pressing the Read Back button on the Readback page.
[Android Q&A, Help & Troubleshooting] Ruldis:
I used standard fastboot procedure to get the recovery in.

I have the phone off - and I set the system start and length - but... nothing really happens. It just keeps waiting :confused: