yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Q&A, Help & Troubleshooting] PHOENIXROSE:
yep APN is correct and bluetooth is off
[Infinix HOT 2] AonSyed:
For which devices, should work

IMPORTANT

* Do NOT ask for support for flashing in this thread.
* Do NOT use this unofficial build and ask for support at the official threads.

What is working?

Service
Text Data
Call
Audio
WiFi
Google Now
GPS
MMS
Video playback
Audio playback
Internal/External
SDcard mounting
Themes All CM features
Screen Record
Bluetooth
Wifi Shared
Video Recording (Camu)
Youtube 720p
Sync Reboot fixed
Move Apps to SD
Xposed
FM

What doesn't work -

You tell us !

Do NOT wipe anything other than system data and cache
DO NOT dirty flash over any other ROM
Wipe data, cache, and dalvik cache

*** ((but do not report bugs if you didn't full wipe))

Download Link : HERE

Flashing Method

Wipe

Flash ROM

Flash Xposed (if you want)

Reboot !

Credits:

pharaohs-team.com

XDA:DevDB Information

[5.1.1]Amigo OS for Infinix HOT 2, ROM for the Infinix HOT 2

Contributors

AonSyed, ibrahim Fath El-bab, Mohammed_3sam

ROM OS Version: 5.1.x Lollipop

ROM Kernel: Linux 3.10.x

Version Information

Status: Stable

Current Stable Version: 1.0

Stable Release Date: 2016-05-31

Created 2016-05-30

Last Updated 2017-01-23
[Infinix HOT 2] dany(X-team)Tester:
Yeah..

Amigo OS
[Infinix HOT 2] DummyPilot:
looks like u upload wrong file dude, just 6.8kb there
[Infinix HOT 2] AonSyed:
Yup seems so. Thanks for pointing out.

Link updated
[Infinix HOT 2] jaybee104:
incredible

Nice screenshots, pls try uploading the status bar screenshot
[Infinix HOT 2] ayoub lg leon:
i port this rom to my wiko mt6580 but i have bootloop plz help
[Infinix HOT 2] dany(X-team)Tester:
please fix it because the camera button to capture images sunk partly in the navbar ..

and the home button in the navbar is not working ..

and the rest is very nice rom..
[Infinix HOT 2] AonSyed:
Will be fixed in next update :)
[Infinix HOT 2] Eng-AliEid:
Flash Gapps and the home button is Work :D
[Infinix HOT 2] essgen:
Can I flash from xui rom

---------- Post added at 08:00 AM ---------- Previous post was at 07:58 AM ----------

Where is the Gapps link?
[Infinix HOT 2] DummyPilot:
Play Store Error

Installing from stock infinix rom step by step but when downloading on play store its stuck on "download pending"
[Infinix HOT 2] AonSyed:
Yes you can flash from any ROM

Use opengapps
[Infinix HOT 2] OjekGOjack:
olaa,amigo....going to download, this rom looks like flyme but quicksettings toggle from bottom :good::cool: and for NavBar bugs, maybe i will make the hw.mainkey=1 and using navbar from PS/anywhere :D good job :good::good:
[Infinix HOT 2] AonSyed:
Thanks and nav bar works with latest GAPPS.
[Infinix HOT 2] essgen:
Flash it used it and move on.

Stable

Ok

Just the interface isn't quite appealing like every Gioonee phone.

But good work and thumbs-up
[Infinix HOT 2] AonSyed:
Thanks for appreciation.
[Infinix HOT 2] AonSyed:
Use nonta72's guide
[Infinix HOT 2] essgen:
Moved back but still not contented wish it was abit more fancy bit must say perfect job.

Try something else but pls not cm base oh something different.

Maybe even a 6.0
[Infinix HOT 2] essgen:
Loving it but flash doesn't work from ui please fix
[Infinix HOT 2] essgen:
Generates text messages to US lines charged at 15 naira daily. Accessibility keeps going off. Only one led light works (green). Battery life not good.

Please can you port this rom into infinix stock rom, for the ui, double tap to sleep among others
[Infinix HOT 2] jaybee104:
Great
[Infinix HOT 2] anzer77:
hey bro., what do u mean "do not wife anything than system data and chace" but u say again "wife dalvik chace...."?!
[Infinix HOT 2] aanuu:
can someone tell me how to remove white circle when i swipe from bottom, and my torch button on quick settings didn't go well, so i downloaded other app. can someone help me?

i did all from instruction except install xposed

btw, i'm using pico gapps
[Infinix HOT 2] ibnu alfajar:
I port to any devices but home button not work

How to fix it?
[Galaxy S 4 Q&A, Help & Troubleshooting] VALYYYY:
After an update to latest version of Lollipop (Germany - DBT) via Odin, menu and back buttons not work at all.

What can I do to bring them to life?
[Galaxy S 4 Q&A, Help & Troubleshooting] Rhoban:
I fear you might have a corrupted button firmware.

And it doesn't seem to be an easy fix either, because you can't simply flash the button firmware...
[Galaxy S 4 Q&A, Help & Troubleshooting] VALYYYY:
Does anyone know about it?
[Galaxy S 4 Q&A, Help & Troubleshooting] Rhoban:
There was another thread for this, but no one has found a perfect solution.
[8525, TyTN, MDA Vario II, JasJam General] theshez:
Hey, I just got a new AT&T 8525 about 4 or 5 days ago and I've been having a lot of problems with it, actually. Sometimes, when I'm using it the touch screen will just stop responding. I would just press the power button so the display goes away but then when I try to turn it back on, it just doesn't do anything at all! The led's still flash and everything.

To get it working again, I just take the battery out and then it works for maybe a couple hours until it happens again. I tried to look up the problem and I think I remember seeing that it could be from having a program that is constantly using data connections such as a weather program or an rss feed program.

I'm using WM5.

Can anyone please help me??

Thank you!
[8525, TyTN, MDA Vario II, JasJam General] theshez:
Anyone at all? It would be great if someone could help me.
[Android Software Development] :
Changelog and working builds

CHANGELOG 19-07-2016:

- fix backup for old mtk phones.

Lollipop

1. Jiayu S3+

2. Zopo Speed 7+

3. Zopo Speed 7

4. Mlais Mx Base

5. Alcatel Pop C2/C3

6. ZTE Blade L3 / Digicel DL910

7. Nous NS5511

Marshmallow

1. Zopo Speed 7+

2. Zopo Speed 7+ with adopted storage

3. Zopo Speed 7

4. Zopo Speed 7 with adopted storage

* NOTE: sadly the kernel source for zopo marshmallow isn't published so these two don't have touch in recovery, but you can use them as in CWM with phone buttons.

[*]

QCOMM devices

:

1. Huawei Honor 5x (kiwi)

2. Samsung Galaxy A5 (SM-A500FU)
[Android Software Development] kirito9:
[MENTION=5186178]carliv[/MENTION] is back!!! Thanks a lot for this.

Should I port or should I build?
[Android Software Development] :
:) You should build it of course. I won't make porting recoveries anymore.

Actually wait for a day or two because I'm working on some improvements and I'll push them to github soon.

Also I have a working version for cm13 too. That also need some more tests before release.
[Android Software Development] faizauthar12:
I will wait for cm13 support :)

Anyway this recovery support arm64?
[Android Software Development] AP756:
Sure. Look at the phones already supported

Gesendet von meinem HERO1 mit Tapatalk
[Android Software Development] kirito9:
Goood xD. No more complaints from users who "brick" their devices and blame you :laugh:
[Android Software Development] :
All things are mostly done.

Just a little heads up: Added usb-otg support for install zip menu - should work with ntfs, fat, exfat and fat32 usb flash drives (I tested only with fat32). Other improvements too for both versions (lollipop and marshmallow).

I'll push the source tomorrow.

Attached a screenshot of the recovery for marshmallow (cm13).
[Android Software Development] BouyaPK:
Thanks to Master [emoji322]
[Android Software Development] :
Thread updated with instruction and links for the new version for cm-13 and the version for lollipop is upgraded to 5.2.

If some of you build a working recovery and want to share here the link, just post a replay and I'll add it in post #2.

If you have a buildable device tree public on github and want a recovery built for it ask here and maybe I or someone else will do it in some free time.

;)
[Android Software Development] exodius48:
[MENTION=5186178]carliv[/MENTION] do you interested to build this recovery for kenzo (redmi note 3 pro) ?

here's kernel source for it: https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/kenzo-l-oss
[Android Software Development] :
The kernel alone is useful only if builds out of the box, but you still need a proper device tree to build, even with a prebuilt kernel. For building a recovery or a ROM that is what you need. I can't build a recovery only with that. Maybe someone else have the phone and manage to create the device tree and it will build the recovery.

Cheers
[Android Software Development] BouyaPK:
Look forward to Flash system Image In Carliv Menu

Thank You :o
[Android Software Development] LowTension:
Finally CTR for LP & MM! Amazing [MENTION=5186178]carliv[/MENTION], I love this recovery.
[Android Software Development] :
Update to version 5.3 for lollipop and 6.2 for marshmallow

CHANGELOG 12-06-2016:

- activated working support for ntfs, exfat and f2fs;

- rewritten the flash image menu for better functionality and more protection to avoid mistakes;

- change the local busybox libs and modules names to avoid conflicting with existing external folder;

- some other small fixes and improvements (you can check the github commits).
[Android Software Development] kirito9:
[MENTION=5186178]carliv[/MENTION]

Hi, I have a device tree that I used for TWRP https://github.com/kirito96/device_Alcatel_4032 recovery and I would like to know if this is enough for building CTR or do I need a "complete" device tree? Thanks.
[Android Software Development] :
Not really complete like in building ROMs, but you have to do some changes:

- convert it to cm building or, better and easier for you since it's for omni, to aicp.

- then you need to add in boardconfig partitions sizes (twrp doesn't need that because it checks the size from dumchar_info or partinfo).

- add that recovery/root/etc folder with ctr.fstab in it.

- add specific flags in boardconfig, but if your device has a small recovery partition let the crypto flag out (don't use it at all) and you will gain almost 2 Mb.

- add resolution and desired font if you want to not use the default which is for 540x960 dpi.

and that's it ...

Take a look at my mlais device tree (link in OP)-sorry, in post #3 to see these things - I have a branch for aicp too.

And I see your device use mtk header. You can check in my github for the lenovo p780 device tree where I implemented the mkbootimg part from my kitchen.

Cheers!

PS: if you can send me your phone dumchar_info file and a stock boot image I'll try to convert your device folder to use it as an example for other people about how to do it.
[Android Software Development] kirito9:
[MENTION=5186178]carliv[/MENTION]

Thanks for informing me, but for now I think I'll opt for a device tree that you made and I'll use that as a base for other devices that I'll work on in the future.

I've attached the dumchar_info.txt file below along with the stock boot.img. Funny thing is, I have 2 stock boot.img. I have for which my phone came with (4.2.2) and an AOSP upgrade with 3.10.xx kernel (5.1.1). I uploaded both because this recovery is for LP right? Which should be 3.10.xx kernel. In any case, I'll use what you made as a base. Thanks again.
[Android Software Development] bigrammy:
You did it!!! :victory:

Good thing I was checking up on you or I might of missed it. :eek:

Thanks carliv I realize this project must of been a huge effort on your part and I for one am very grateful :highfive:
[Android Software Development] anaconda875:
How can i unpack these files bro? It's Z1 dualrecovery

---------- Post added at 07:44 PM ---------- Previous post was at 07:42 PM ----------

I want to unpack, modify, repackage these files! It's Z1 dualrecovery. Any suggestion bro? Plz help
[Android Software Development] DeadSquirrel01:
For these i don't know, I don' t have a sony device
[Android Software Development] bigrammy:
OT (Off Topic) :o

There is plenty of info on xda and the Sony threads about this subject so just do some searching and ask on the threads where you got the recoveries. :good:
[Android Software Development] Aditya Kr:
nice one
[Android Software Development] qwerfaseeh:
hi can anyone help me in making custom recovery for my new device as there is no support available any where so guys please i have a backup of my device so i can provide you with the required files ad MT6755 is not supported by many software and i tried but failed to make custom recovery for Marshmallow.
[Android Software Development] vampirefo:
Thanks for this recovery, came in handy, I bought a new phone, that disables touch in recovery, making TWRP almost useless on my phone.

Compiled using LineageOS 13, CM13 is no more.

No matter compiled just fine, finally can get rid of CM11 source, I kept just to compile cwm based recoveries.

I uploaded recovery to needrom.

http://www.needrom.com/download/blu-life-max-carliv-recovery/
[Android Software Development] kirito9:
[MENTION=5186178]bluefirebird[/MENTION] Hello again, I'm back compiling your recovery again but this time for Spreadtrum chipset. I'm not sure if it supports or it would need some specific flags but here's the device tree if you have time to check it.
[Android Software Development] :
Thread closed at OP request

Regards

Sawdoctor
[Android Software Development] :
:) Thanks, you have no idea how hard it was, but I pulled it off finally.
[Android Software Development] :
[MENTION=5515628]kirito9[/MENTION] you gave me some work to do ;)

Thanks for this. I found that way the recovery doesn't build for arm devices, only arm64 and I fixed that in the last hours (and some other things too since I started). So, now I have to push the update and your device tree. I'm not sure if the dumchar info you gave me is right... boot and recovery 20 Mb ... but I used it and I've built a recovery for you to play with until I push the new version (tonight). The thing is that is bigger than 6 Mb but if your partition is 20 Mb there is no problem (other way you have to remove the f2fs binaries from sbin).
[Android Software Development] bigrammy:
If you thought it was hard then I can't even begin imagine it :laugh:

I have managed to port the Zopo Speed7 MM 6.0 to my Infocus v5 m560/m808 AKA ZM1 (Never known so many names for one phone :laugh: )

All works perfect except mounting the sdcard to the PC :(

Nothing to do with the recovery but it seems sys.usb.config=mass_storage,adb is hijacked by Infocus for automatic loading of the phones drivers.iso.

The lun file has loop0 echoed to it by default but this identifies itself as a CD-ROM to the PC :confused:

#5.mass_storage,adb
on property:sys.usb.config=mass_storage,adb
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor ${sys.usb.vid}
write /sys/class/android_usb/android0/idProduct C001
write /sys/class/android_usb/android0/functions ${sys.usb.config}
write /sys/class/android_usb/android0/f_mass_storage/lun-cdrom/file "[COLOR="Blue"]/dev/block/loop0[/COLOR]"
write /sys/class/android_usb/android0/enable 1
start adbd
setprop sys.usb.state ${sys.usb.config}

I have tried other loops and mmcblk's but not had any success yet not sure if I will have to re format the sdcard or not.

If anyone with the speed7 on MM could could upload the init.mt6735.usb.rc from the boot.img or let me know what the lun "file" says it would be a great help. :good:

I will take a shot at compiling the recovery when I get my linux PC sorted but I doubt it will make any difference to this problem. :confused:
[Android Software Development] :
Well, I have a Speed 7+ and all testing are done on it. So if the lunfile I used is the same it should work for your phone too. My recovery can work also with lunfile defined in ctr.fstab like in old cwm:

/sdcard	vfat	/dev/block/mmcblk1p1	/dev/block/mmcblk1	[COLOR="Red"]lun=sys/class/android_usb/android0/f_mass_storage/lun/file[/COLOR]

This one works in Speed 7+.

By any chance have you changed idVendor and idProduct in init.rc? That could be the problem if the driver in windows or udev rules in linux can't connect your device.

The recovery has Google's vendor and product like any other recovery (twrp, cm) and it will be recommendable to not change those especialy if you have google usb drivers installed.

write /sys/class/android_usb/android0/idVendor 18D1
write /sys/class/android_usb/android0/idProduct D003
write /sys/class/android_usb/android0/f_ffs/aliases adb
write /sys/class/android_usb/android0/functions mass_storage,adb

So the idProduct should be D003 for mass storage with idVendor 18D1.

;) I'm sure you'll find the way to make it work.

PS Almost forgot. You are talking about an external sdcard don't you? I just want to be sure, because the internal sdcard can't be mounted in mass storage (doesn't have a lun file).
[Android Software Development] bigrammy:
Hi,

Yes bro I mean external_sd :o

I will retry the product and vendor id's as suggested :fingers-crossed:

So my file path is

lun=sys/class/android_usb/android0/f_mass_storage/[COLOR="Red"]lun-cdrom[/COLOR]/file

EDIT: Same problem bro with the google id's :(

Mounts as a non readable CD-ROM. I would be interested to see what your lun "file" actually says eg: which loop or mmcblk it refs too.

Got work in the morning so I will do some more tests tomorrow evening.
[Android Software Development] kirito9:
[MENTION=5186178]carliv[/MENTION]

Thanks a bunch for compiling for me!! I really appreciate your hard work!!.

And yes I forgot to mention it. I'm using a stock Vodafone 785 (clone of my device) ROM/Layout where the boot partition and recovery partition are both increased to 20MB. Before it was 6MB on my old layout. This was a wonderful find and I thank whoever tried it to see that it was working. /OT

I'll check the recovery and report back.

---------- Post added at 07:30 PM ---------- Previous post was at 06:35 PM ----------

As I suspected, this recovery won't boot on my 3.4.67 kernel. I have to change the kernel to that of AOSP(3.10.xx) and make a few changes in fstabs. This AOSP ROM doesn't use custpack and also mobile_info. It couldn't detect external sdcard until I used your second layout

/sdcard	datamedia	/dev/null
/external_sd	vfat	/dev/block/mmcblk1p1	/dev/block/mmcblk1

It was more or less like the paths were switched. But other than vibrate (probably kernel) everything else works!! Thanks

CTR 5.3- https://www.androidfilehost.com/?fid=24588232905719935
[Android Software Development] :
:confused:Hm, maybe your phone doesn't have a mass storage function? When you are on android and connect the phone to PC there is a mass storage option in usb connection list? I attached both usb rc files from zopo to check them. The lun file is in init.usb.rc

Cheers

:)I'm glad it worked. :good: Soon you will build it by yourself and you can add your vibrate file in BoardConfig. Just few tests to make before pushing the updated version.
[Android Software Development] kirito9:
Yes very soon :). I'm also planning to build for more Alcatel devices being upgraded to LP kernel. I'll will update you once the device tree is ready ;)
[Android Software Development] bigrammy:
Hi sorry for the late reply been at Work :(

For Info:

Ok mate like I say this has nothing at all to do with your recovery which works as it should :good:

Infocus have messed around quite a bit with the Mass Storage and sdcard.

By default the phone does not have a mass storage option just mtp, ptp and charge only

I have tracked things down some what. :cowboy:

By default the mass storage "function" is used for the driver.iso which contains the phone drivers and setup.exe which mounts automatic every time you plug the phone to the PC. :mad:

This is achieved by infocus echoing /dev/block/loop0 to the lun "file" and setting the "ro" file to 1 with root and read only permissions.

I added this line

write /sys/class/android_usb/android0/f_mass_storage/lun-cdrom/file

to the recovery init.rc which now removes /dev/block/loop0 :good:

Reading the Lun file with cat while in recovery now gives me the correct blk

/dev/block/mmcblk1p1

:good:

I have 2 further mods to make then I think I will have it working as intended :fingers-crossed:

To Do: (After some dinner :laugh: )

1. Change the file "ro" permissions and echo 0 (zero) to it from the recovery init.rc so the sdcard is RW.

2. Re-format the SDcard . (I think the SDcard maybe partitioned by default to allow the factory ROM apps to SD to function.)
[Android Software Development] :
:laugh: I told you you'll find a way out! I hope it will work, otherwise you'll have to use usb-otg to bring some external files... if the phone has otg.

Ok, all done. I opened a pull request on your repo with changes I made. I converted it for aicp (which I use now) and If you use aicp it will build in both lp-5.1 and mm-6.0 (when there will be a mm kernel for it). Also updated the recovery and now it builds for non-arm64 too. Now you can start building :highfive:
[Android Software Development] kirito9:
I already merged your commit ;). Can I build it with CM or do I have to convert it again? If I have to use AICP then it's no problem. I would just download the source and build.
[Android Software Development] bigrammy:
:laugh: Yes I got usb-otg and that works perfect. :good:

Some useful info should others run into some issues on 6.0

SDcards explained for Android 6.0 :good:
[Android Software Development] :
For now I would recommend aicp - seems better, and has all the good parts from cm too. :good:
[Android Software Development] kirito9:
I'll begin downloading now :)
[Android Software Development] :
update to versions 5.5 and 6.3

CHANGELOG 20-06-2016:

- added back isolation flags in BoardConfig for ntfs, exfat and f2fs to exclude any of them from build;

- cleand some dead code;

- improved the graphical experience;

- some other small fixes and improvements (you can check the github commits).

Visual there is no difference only functional, so I didn't change the screenshots.
[Android Software Development] BouyaPK:
This is not Support for backup and restore with USB OTG.

I like your work very much, I will wait. :o
[Android Software Development] whitelyon78:
This recovery works in Huawei G7 ??
[Android Software Development] BouyaPK:
Not Sapport Snapdragon
[Android Software Development] :
Yes, it should if someone will build it for that device.
[Android Software Development] :
I'll add OTG for backup and restore in the next update. Cheers,
[Android Software Development] bigrammy:
Hi carliv,

I need a little advice bro.

I cannot seem to get the file ro to change from 1 to 0 no matter how I try.

I even tried changing it on init but it still reverts to 1

I even tried using ES File explorer pro but it fails to edit the ro file also. :confused:

Is this selinux at play or something else. :confused:

Does the platform.xml in /system/etc/permissions come into play while in recovery?

I have work for a few days now so no rush but If you think of anything that maybe causing this issue please let me know so I can try find a workaround for the usb mass_storage function on this Infocus. :o

Other than this one thing it works perfect :highfive:
[Android Software Development] :
Hi bigrammy,

Yes the selinux rules are more thightened in marshmallow with a lot of neverallow rules. But if you are talking about the mass storage thing I don't think that recovery can be modded to do this by itself. The lunfile is in sys, which is in root of device, controlled by boot image not system. So I prepared a boot image for you to test using the zip archive you posted for that phone. Please flash it, boot to android and see if the mass storage option is in usb list of connections and even if it is not there, flash the recovery without any modification in init file and see if it works. I reverted the lines they changed to assign mass storage lun file to cd-rom. I hope it will work...
[Android Software Development] globula_neagra:
[MENTION=5186178]carliv[/MENTION]

If I build a device tree using your example from github will you be able to have a look, just to see if is correct ? (I have no sources for the device besides the ones dumped from the device, boot img etc).
[Android Software Development] :
Sure, make it and push it on github, then give me the link. I'll take a look and I'll check even if it builds. For that device I have no source also and I used same things as you have to.