yashsingh1/xdaforums huggingface dataset:
[Device Reviews and Information] deryalex96:
error

http://www.kephost.com/image/vozE

EDIT1:

I tried again and it succeed.ed. Uploading to mega.

UPDATE:

Mega seemed extremely slow, so I uploaded the readback to Dropbox. I really hope it is useable and You can make a flashable firmware from it.

https://www.dropbox.com/s/dwd7kmln64cohd6/READBACK ROM M808.zip?dl=0

UPDATE - 2 new links:

Here are the new links for my readback. I am really excited about what you can do with it.

https://mega.nz/#!DQpQQYQA!0y3mxgGds...jGWTT4kaLtBWbI

or

https://drive.google.com/open?id=0B7...jR0ZURqTklJOWs
[Device Reviews and Information] bigrammy:
Many Thanks deryalex96. :good:

It may take a week or so to try make it flashable.

Little busy just now preparing for the Holidays. :o
[Device Reviews and Information] Iye Vice:
Happy upcoming Xmas & NY2017 holidays! Dropbox link seems to be broken. Is it possible to ask you to upload the readback to GDrive or some other cloud? Please, NOT to Baidu! ;)
[Device Reviews and Information] deryalex96:
Yes, of course, I will edit this post if upload finishes. Dropbox said: "This email is an automated notification from Dropbox that your Public links have been temporarily suspended for generating excessive traffic."

Here seems to be hiding people who downloaded it many times. ಠ_ಠ

Happy Holidays to all of You!

-deryalex96
[Device Reviews and Information] Iye Vice:
Thanks, 4pda.ru community will be eagerly awaiting the URL ;). By the way, how did you do with your biophysics and molecular cellbiology and other 4 exams?
[Device Reviews and Information] deryalex96:
Hit a like here if you want an AOSP ROM for M808, our beloved phone:

https://www.facebook.com/MediatekAndroidDevelopers/posts/1202229446527493

Thanks for the question. I got mark 4 on both of them, last week mol.cellbiology and today biophysics. (5 is the best, 1 is failed here). Next will be on 28th Dec: Biometry and SPSS Statistics, so I need to learn. Medical university is not so easy :laugh:
[Device Reviews and Information] deryalex96:
Here are the new links for my readback. I am really excited about what you can do with it.

https://mega.nz/#!DQpQQYQA!0y3mxgGdsYhOt-pu6Ex_AZF0ZXy7njGWTT4kaLtBWbI

or

https://drive.google.com/open?id=0B70PlwpvafKaUjR0ZURqTklJOWs
[Device Reviews and Information] bigrammy:
Wow the watchers must of hit the Dropbox link pretty hard :laugh:

Thanks for creating the Mega and Gdrive mirrors though :good:

Congrats on the results so far, seems all your hard work is paying off so keep it up :highfive:

Peace and goodwill to all :o
[Device Reviews and Information] deryalex96:
I've just found this. Can anyone compare this and mine, what is the difference and which might be newer?

https://m.facebook.com/story.php?story_fbid=1888052401414633&substory_index=0&id=1394098657476679
[Device Reviews and Information] bigrammy:
It seems this is the official MM upgrade so it should be the latest and most stable.

Official Download Here ZM1-622Q-0-00WW-A04-update.zip

Warning: This needs to be flashed using the OFFICIAL STOCK recovery!! not TWRP.

In my opinion Since we were using official MM Beta ROM's you/we are probably still on the Beta version line which is for testing and debugging so while it my well be the most up to date it maybe less stable than the None Beta version Line. :o

PS: I sent you a PM regarding the "hidden" Partition readback
[Device Reviews and Information] Eleichstetten:
Unfortunately I did not save the original recovery.

As I would like to try this version: is there somebody out there, who can tell me where I can find it?
[Device Reviews and Information] deryalex96:
Hello,

I have read the PM, I will have time after 28th Dec.

Today morning my infocus got a new OTA named as 622Q, I have not let it update yet, and now I saved the update.zip, but if this is the same as you and Taiwan101 uploaded, it is not necesarry to do the mentioned readback, is it?

If not, I let it upgrade itself OTA.

(And because this happened (got official stable build OTA), I do not think my 00WW_6_22M version was a betaline, just an officially unpublished build, like there are samsung firmwares which exist on sammobile, but kies does not show them.)
[Device Reviews and Information] bigrammy:
What is your current rom version? LP or MM

Thanks deryalex96 :good:

Your 00WW_6_22M version update flashed the hidden partition according to the fver

ZM1,hidden,,ZM1-0-VV-0001-hidden.img.ext4,0030,ZM1-0-0030-0001-hidden.img.ext4,HiddenImg

as said this partition contains many important setup config files and folders which are Region specific it also has many audio .bin files which is why the audio sounds so much better on our device than it does on many other mt6753 devices :D

I cant say which files or folders were updated specifically in your update maybe none but yours is the latest known version of the hidden partition and the missing piece in the Infocus update jigsaw puzzle. :laugh:

The 622Q update does not update the hidden partition at all . :confused:
[Device Reviews and Information] Eleichstetten:
Oh, yes. I should have mentioned: My actual version is MM: 6.22D
[Device Reviews and Information] bigrammy:
No problem.

HERE is Stock ZM1-0-622D-00WW-recovery.img
[Device Reviews and Information] naosediz:
update isn't working for me... it shows a error (forgot to print) and after that software update is showing that android is up-to-date and still on 622d and it hasn't updated.....

but.... i've managed to extract the firmware.zip file if someone need's it
[Device Reviews and Information] bigrammy:
I have made the 622Q update TWRP flashable so you should be able to upgrade without issues.

I will post it tomorrow with instructions when the uploads are done.

Warning to other users: I have only tested this official upgrade on MM and I am unsure if it's even compatible with LP. If anyone got a OTA update on LP please let us Know and if possible capture it before updating :good:
[Device Reviews and Information] ilyapn:
Good time of day! Can you ask to put Stoke recoveri for 518j_04? Thenks!
[Device Reviews and Information] bigrammy:
Warning only for those already on mm

WARNING: THIS ONLY FOR THOSE ALREADY ON MM​

Build Date: Dec 08 2016

ZM1-622Q-0-00WW-A04-update-TWRP.zip Size: =	1.48 GB

Type: = MM TWRP Flashable Not for LP ROM's

Comment: = Warning: I have only tested this official upgrade on MM.

ALWAYS BACKUP FIRST.

1. Copy the update zip to your sdcard and also the Latest SuperSU flashable .zip

2. Boot to TWRP MM recovery

3. Disconnect the phone from PC

4. Unmount data from the TWRP mount menu

5. Now select INSTALL and choose the ZM1-622Q-0-00WW-A04-update-TWRP.zip

6. After it finishes Without Errors Reboot or Flash the Latest SuperSU.zip

NOTE: You may get "data busy error" if you do not unmount data!!

Remove the PC/USB Lead and choose unmount data from TWRP Menu before Flashing

NOTE: 2 If you are brave and wish to try going from LP to MM :cowboy:

Then to make things easy you should copy to sdcard and Flash the MM TWRP straight after flashing the update zip and before booting to system.

SuperSU and other links are in my post http://xdaforums.com/showpost.php?p=67345310&postcount=182

---------- Post added at 10:38 AM ---------- Previous post was at 10:27 AM ----------

Sorry google translate has done a poor job on your post. Do you mean Stock Recovery for the 518j LP firmware. :confused:
[Device Reviews and Information] ilyapn:
Yes, 5.1 LP stock recovery
[Device Reviews and Information] drei.liter.milch:
Thanks [MENTION=3924647]bigrammy[/MENTION]
[Device Reviews and Information] ilyapn:
Can I upgrade from across the TWRP LP on MM with the aid of the firmware A01-6220-0-00WW-A01-update.zip
[Device Reviews and Information] bigrammy:
For upgrading the firmware from LP to MM it is better and safer to use SPFlashtool :good:

I would recommend using the ZM1-0-622D-00WW-A03.zip with SPFlashtool :o

If you still wish to try using the A01-6220-0-00WW-A01-update.zip then here is ZM1-518J-0-00WW-stock-recovery.img that you wanted :fingers-crossed:
[Device Reviews and Information] ilyapn:
Thank you Friend!:good:

Unfortunately recovery not come, after rebooting in recovery is open robot.
[Device Reviews and Information] paulroland:
So, i did the beta-testing - and...it works...

I came from LP, rooted with TWRP like described in this thread

http://xdaforums.com/showpost.php?p=66276407&postcount=23

I exactly followed the steps from Bigrammy and ihave no problems so far. I did no wipe. Only one thing i forgot...the TWRP is gone because i havn't flashed it during the update process. How did i get the MM TWRP on my MM-phone?

Thanks
[Device Reviews and Information] Iye Vice:
Dear bigrammy! I've updated 622D to 622Q yesterday via TWRP (somehow). But today, following your instruction, I have trouble finding 'data' in my TWRP 'Mount' menu. Which position did you mean?https://i.imgsafe.org/3d819dd373.png
[Device Reviews and Information] bigrammy:
Your a brave man :laugh:

Thanks for reporting back :good:

Yes to make things easy you should of also flashed the MM TWRP straight after flashing the update zip and before booting to system.

Did you by any chance flash the SuperSU zip if so I can give you the adb shell commands to flash the MM TWRP :fingers-crossed:

If not then SPFlashtool is the answer.

If it already worked why would you try it again :confused:

That TWRP version is not mine so I have no idea sorry.

My LP TWRP is HERE

My MM TWRP is HERE Please Follow the installation instructions
[Device Reviews and Information] Eleichstetten:
Just to keep you informed (my initial setting was MM 6.22D with TWRP 02 from bigrammy):

Yesterday I did copy the update file (6.22Q, the official one Bigrammy refered to in post #300)

to my phone (twice: once in internal memory, once to SD-card).

After a restart, the phone told me: "You have update!" (something like that)

As I did have trouble with my PC and the flashtool, I thought: No risk, no fun.

So I agreed to update.

The update started, phone was restarted and the boot did lead me to my (your) preinstalled TWRP-Recovery.

As expected, nothing else happened.

So I did clean the internal memory, installed the update file using TWRP, installed SU and did a reboot.

-> Fine, everything is up and running.

ROM-Language is english and some chinese.

It is neat and clean. Just the usual GAPPS. Nothing that can be blamed as being bloatware.

I´m realy impressed.

I tried to use morelocale to switch it to german (just for the later installed apps), but that failed.

After a boot it´s back again to en/US.

Therefore I tried another app for changing local parameters: "MoreLangs/Ländereinstellung" by Sightidea Studio.

What did the trick was: follow the app´s recommendation and use the "adb pm" procedure.

The German translation is good. Just some small apps stay in english language, but if needed, they can easily

be replaced by another "german speaking" app.

I will now do some tests, but on the long run, I will try to go back to 6.22D using my backup, because that was a

multilingual version including german language.
[Device Reviews and Information] paulroland:
Thanks for the "brave", but i just cant wait...

Yes, i installed SuperSU.zip, so it would be kind, to get the adb shell commands (did not do that before, so...)

By the way another problem apears...i played with my new MM-phone and i try to format the SD-card as an internal storage - the phone offers me this opportunity - but i fails totally. After formatting, the phone doesn't recognize the SD-card anymore, not as internal, not as external. Maybe a mounting problem? But without TWRP...i put it out, put it in again, no chance

The good news , all other things work well, as far as i can say after 2 hours...
[Device Reviews and Information] naosediz:
Hi bigrammy. Thanks for the work you had making this possible.. bit i've tried putting twrp on spft and it flash OK, but when i put in recovery modelo it just apears the dead bot
[Device Reviews and Information] bigrammy:
I have not tested the SD-card as internal storage maybe someone eles can help on that one :confused:

Ok so to flash recovery.

1. Make sure you have adb installed on your PC.

2. Rename the MM ZM1-0-622B-00WW-A02-TWRP.img to mmtwrp.img and copy it to the root of your internal storage along with the TWRP folder and file.

3. Enable usb debugging and set SuperSU to grant all by default (you can change it back after).

4. Open the cmd prompt or terminal if on linux and type

adb devices

the cmd window should return you something like

ZM1??????????? device

If it does we are good to go.

5. Copy the following commands and execute them one by one.

adb shell

su

the $ sign will change to # if all is well

dd if=/sdcard/mmtwrp.img of=/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/recovery

It will take a few seconds to respond but it should say so many bits transferred and the amount of time.

If says that then type

exit

exit

adb reboot recovery

:fingers-crossed:

You need to flash twrp the boot into recovery without booting to system.

Also make sure you are flashing the correct version LP or MM depending on your rom.
[Device Reviews and Information] paulroland:
Thanks, but before i go to work, a simple question: What do you mean with "along with the TWRP folder and file."? There must be a TWRP folder on the storage? And what file?
[Device Reviews and Information] bigrammy:
Get the MM recovery from My post HERE under the "CLICK TO SHOW CONTENT" Button You can read the instructions there regarding the TWRP folder which is included in the recovery download .zip

Basicly rename any old TWRP Folders you have to Ori-TWRP and copy the TWRP folder from the .zip to the root of the internal SDcard.
[Device Reviews and Information] drei.liter.milch:
Hi guys

Formatting the sd as Internal Storage caused problems in the previous mm releases for me, too.

At The moment im running 00ww_6_22d+twrp3.0.2.2, but will flash The update today and will give a report
[Device Reviews and Information] bigrammy:
Thanks.

I missed your post edits due to the xda system not notifying us of edits to posts. :o

Just for clarity a few notes to others

The official ota update will fail if you have my MM TWRP installed when you receive the OTA.

For those with my MM TWRP installed please use the update from post #309 Here

It seems there are a few different versions of TWRP recovery from other dev's :eek:

All my posts are regarding the use of My TWRP versions ONLY as I have no control how others are handling things in their versions.

Note the /dev/block paths are different in TWRP MM to the stock recovery so official updates need to be edited first before flashing them.
[Device Reviews and Information] ag.steel:
There seems to be problems with this official update (If we roughly translate chinese comments), so infocus pulled the update from the official website.

I sent en email to their support, here is the answer :
[Device Reviews and Information] paulroland:
[MENTION=3924647]bigrammy[/MENTION]

All done, after typing the last code it says "no such file" - remember, the phone doesn't recognize my sd card at the moment, i only have the internal storage. Do we have to change the part with the "sdcard"?
[Device Reviews and Information] bigrammy:
I suspect the update is causing issues for those upgrading the Firmware Version eg: LP to MM.

Like I have said before it is very difficult to perform a 100% successful Firmware Version Upgrade using just the recovery.

Firmware Updates are not a issue using recovery. Note: Upgrade and Updates are different.

For Mediatek devices it is ALWAYS preferred to upgrade Firmware using SPFlashtool in Firmware Upgrade mode. :good:

This ensures a clean installation of all partitions including Userdata and Cache. Restoring LP 5.1 Userdata and Cache on a MM Rom is never a good idea due to compatibility and permission issues.

If you own a MediaTek Phone I recommend you all learn to use SPFlashTool there are Many Many Many guides/tut's on xda and youtube. :good: :good:

I have uploaded the official Firmware that was on the Infocus website before they pulled it. I have added it to My MM firmware post #182

---------- Post added at 02:14 PM ---------- Previous post was at 02:00 PM ----------

Check your spellings and spaces ensure your working as root #

The "sdcard" should be your internal sdcard by default.

Type the following to check.

adb shell

su

ls /

Look for sdcard in the list then

ls /sdcard/

see if you can see the recovery in the list eg: this is my output.

root@ZM1:/ # ls /sdcard/
Alarms
Android
DCIM
Download
Movies
Music
Notifications
Pictures
Podcasts
Ringtones
TWRP
amazonmp3
backups
twrp-v3-recovery.img
twrp-v4-recovery.img
twrp-v5-recovery.img
twrp-v6-recovery.img
root@ZM1:/ #
[Device Reviews and Information] paulroland:
So i found the recovery in this list and i'm working as root, but still "No such file or directory". Everytime i wrote the command, i can't see the whole command line. The longer i wrote, the first part of the command disappears in the cmd - Is this normal? I'm confused,what is wrong? The same results with the terminal emulator directly on the phone

[IMG="sdcard"]http://www.pixxomo.de/sdcard1.jpg[/IMG]

[IMG="cmd"]http://www.pixxomo.de/cmd1.jpg[/IMG]
[Device Reviews and Information] bigrammy:
Sorry it should be

dd if=/sdcard/mmtwrp.img of=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/recovery

MSDC0 should be lowrer case.
[Device Reviews and Information] paulroland:
Thanks, that was it...Now i try to flash again, to solve the problem with the external sdcard
[Device Reviews and Information] paulroland:
After getting the TWRP running, i decided to make a clean factory reset - bad idea, now i have a non-rooted MM phone, with no TWRP and i think no recovery at all (to install superSu). When i have root, i can easily install the TWRP via ADB - i did this 100 times today...

What is the easiest way to root again - thanks!
[Device Reviews and Information] bigrammy:
You should still have TWRP as doing a reset will not wipe the recovery partition :confused:

If you formatted the whole of Userdata then you will need to re copy the TWRP folder to your Internal sdcard again.

Enable usb debugging the adb reboot recovery :fingers-crossed:

EDIT: If you booted to recovery and just had a black screen then the recovery is fine and waiting 2 mins then the screen will wake up but doing the above will fix the black screen delay
[Device Reviews and Information] paulroland:
Thanks :good:, i had the same idea but i use "adb reboot recovery" instead of "reboot recovery" ...:p

TWRP and root , working:victory:
[Device Reviews and Information] bigrammy:
Cool :cool:

I have been working on a updated recovery for the past few days that supports the new and old MTK partition paths which is now just about ready :fingers-crossed:

This means no more editing of updater-scripts and it should now support factory updates as well as custom ones :D

It still has the black screen bug so it will need the TWRP folder and config file as before. :o
[Device Reviews and Information] drei.liter.milch:
So here i am. Just flashed your modified update and here is my report so far

I came from 622D_A05+TWRP3.0.2.2+Magisk+systemless xposed+magisk phh superuser.

-booted into recovery

-unticked data in mount menu

-dirty flashed your modified update.zip

-went to terminal in advanced menu

-entered commands for systemless su:

echo SYSTEMLESS=true > /data/.supersu

echo BINDSYSTEMXBIN=false >> /data/.supersu

-flashed the newest supersu2.79.zip

-rebooted into system

!! -noticed no supersu apk installed

-installed it manually

-opened it and app says sth. like “no su-file installed and

supersu can't install it. That's a problem! If you just

upgraded to Android 5.0 you have to root again

manually. ..“

-switched device off

-booted to recovery via hardkeys

-flashed older supersu2.78.zip

-rebooted to system

-status quo: not rooted

While writing this, I noticed that I forgot to tick data in mount section after installing the update.zip..

I'll give it a try..

UPDATE

Fixed it! Here the steps:

-booted to recovery via hardkeys

-flashed unSU.zip (found somewhere here on xda)

---FLASHED MAGISK-UNINSTALL.ZIP (I think that was the

point)

-flashed supersu2.79.zip

-rebooted to system

-status quo: 6_22Q+TWRP3.0.2.2+SL SuperSu 2.79

Can't notice any changes to the D_A05 so far.

But i'll keep you informed..

:)
[Device Reviews and Information] bigrammy:
Never mind you found the answer :D

Talk about dirty flashing !!
[Device Reviews and Information] Iye Vice:
Dear bigrammy! I want to thank you for your updated TWRP 3.0.2 for MM. I tried to experiment - take out the Gallery2 APK from LP 5.1 firmware, in order to replace stock camera app in MM (which, unfortunately, has very little MODE options (only Normal & Panorama), while 5.1 camera (integrated into Gallery app) had PIP mode, and some other cool addons.

So, I flashed 5.1, got what I needed, then flashed MM 622D, then 622Q update. But TWRP recovery by Taiwan101 failed to boot ;(. Then I opened your XDA bookmark & found your new TWRP 3.0.2 (nice blue one ;) which flashed perfectly via SPFT. Also, I found your full 622Q firmware, which is being downloaded right now to my PC. For that, I also thank you! Sorry to have forgot to congratulate you on Merry Xmas occasion (which I do now), but I still have time to wish you a Happy New 2017 in advance (which I also do now).

You are doing excellent job, so be healthy & wealthy & keep your life in focus ;)!
[Device Reviews and Information] drei.liter.milch:
Noticed small changes in the settings menu..

New Option in Accessibility menu: Switch Access

https://support.google.com/accessibility/android/answer/6122836?hl=en&ref_topic=6151780

Seems to be built in customizable HW key Feature. Nice

----

Btw: the earlier versions of the mm roms (or at least one of them) contained a fihtdc-package Installer with silent install feature, which I miss in the newer versions..

Could anybody extract and upload the apk-file for me? I don't kept the old roms and unfortunately run on mobile internet at the moment. Thanks in advance

And a happy New year of course =)
[Device Reviews and Information] virusx:
Hi,

First I wish you all a happy new year :)

EDIT: I finally got my PC to detect my phone by keeping it plugged, pressing Power + Vol down, and SP Flash Tool opened, update ready.

I'm flashing ZM1-0-622D-00WW-A03 and will update to 622Q afterward.

EDIT 2: My phone got 622D-A03 rom now but I can't access recovery. I tried to flash TWRP and A03 recovery back but I still have a black screen more than 2 minutes.

I updated from 622B to 622Q using TWRP and the ZM1-622Q-0-00WW-A04-update-TWRP file but now I'm stuck at InLife logo.

I think that my zip file was corrupted or something like this.

I tried to go back to TWRP to reflash a new ZIP but I can't access TWRP anymore.

When I try to boot in recovery (Power + Vol up) I got a dead Android robot with red exclamation warning.

I still can boot in Fastboot mode (Power + Vol down).

But my Win 10 computer doesn't seems to detect my phone using SP Flash Tool.

Does anyone here knows the procedure to get my phone back to life ?

I have downloaded every tools available here but I'm not sure if my Win 10 PC is having the right drivers and which version of flash tool to use.

Thanks in advance
[Device Reviews and Information] bigrammy:
Updated MM TWRP

UPDATED MM RECOVERY: = Identical to older MM TWRP but I have added support for both New and Old Partition Paths.

New paths= Used by Official OTA's etc

/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name

Old paths= Used by Many custom Flashable .zip

/dev/block/platform/mtk-msdc.0/by-name

See My Post here for download https://xdaforums.com/showpost.php?p=67345310&postcount=182

EDIT:

Sorry!!!

It seems my new MM recovery is not working with the older partition paths so please let me try to find the reason it broke :o

I had it working but I built so many versions getting it to work I need to retrace things. :rolleyes:

NOW FIXED!! :victory: