Related
My friend came with an Alcatel One Touch Pop C7, and asked me to update its system
Here are some mods I found, but didn't find here in XDA so I thought it would be good to share here
KitKat!
- Video tutorial (in Spanish):
https://www.youtube.com/watch?v=-hXKFwgBh6E
- Files:
.. Tools and driver for Windows:
https://mega.nz/#F!QVwynRiQ!8HFjc0wf3hpkeIuVZfl7hg
.. Rom KitKat
https://mega.nz/#F!2QFFibwI!M9a5BeDL9aJLMwMAAqp5cg
Note: you won't need to download 2 GB file usrdata.img!
It should work in all C7 models: 7040A, 7040D, 7040E, 7040F, 7041D, 7041X, 7042+
This ROM is made to model 7041D. As I'm using 7040E, I had to install two ROMs before:
1. This 7041D Dual stock full ROM:
https://yadi.sk/d/QZgW7x85fgn3P
2. Use this scatter file...
http://www54.zippyshare.com/v/SNRc7C4R/file.html
... to install this 7041X stock ROM - DON'T INSTALL 7041X PRELOAD!!! -
https://drive.google.com/file/d/0B3_5MAPXTV5baERzTW9FSkU5TTA/view
3. Now I can install KitKat ROM
http://www.mediafire.com/?ysnje8a96pt0q8h
Mega mirror broken
Custom Recovery!
CTR 3.0 (i prefer this in Alcatel C7)
http://www.mediafire.com/download/181r8crfw7bhag3/CTR_V_3.0_.img.zip
TWRP 2.8.2.0 + scatter file
http://www.mediafire.com/download/2ivw86tvu79twun/Teamwin_recovery.rar
PhilZ-touch
http://www.mediafire.com/download/v1tq848r1p1j534/PhilZ-touch.zip
Whatever custom recovery you choose, you need a scatter file to install it. So, you can download TWRP (because of scatter) and your preferred recovery
Single SIM
This ROM is made to a dual sim device. If you own a single sim model, to avoid issues, edit your build.prop line
Code:
dualsim.ui.support=true
Inserting a "#" in its beginning. It will be
Code:
#dualsim.ui.support=true
- Hereafter there are files that I've not tested
ROMS for MT6582
These ROMs are (apparently) easy to port
- Cyanogenmod 12.1 Beta 6
- Cyanogenmod 13 Stable
- SlimROM Marshmallow
- Resurrection Remix 5.7.3
... and many others
Porting guide:
http://www.mtkroms.com/2015/08/install-real-lollipop-on-all-mtk.html
Credits:
- ElDavoChannel: KitKat files and tutorial
- JoaoS: solution to non 7041D devices
- MTKRoms: AOSP ROMs for MT6582
Thank you so much,this post is underrated.
I managed to upgrade it for 4.4 kitkat and it's faster and better now. I've been looking for this for a long time.
appreciated.
Pop c7 7041x
Hey, so I tried to upgrade my father's phone to cm 13 from another source (your link is dead...) and it gives me symlink missing error in CWM Recovery I wanted to try the CTR one (got 2.4 version from online videos) and it just goes blank screen and bootloops until I put right stock EBR to work again.
I will have the phone again next sunday like 11 AM (UTC) I would hope you could help me get a ROM that doesnt give symlink error in installation. This time I will try to install this CTR version.
Rom
Recovery 3.0.2 Alcatel pop c7
I used this ROM on my 4071x succesfully, but I dint "Download" the MBR, EBR1 or EBR2 onto my phone, as they apeared to be binairy the same (that means completly equal). there another thread where i wrote way too much but basicly this rom is awesome. sadly the Accelerometer doesnt work anymore. maybe a system module. Pokemon Go works no crysis yet tho.
thanks you so much .
admin XDA
My device is Alcatel one touch pixi 3
I have tried many times to install the ROM CyanogenMod 12.1 on my galaxy J5 j500m more without get the error '' could mount filesystem devblock / bootloader ... in such file directory '' something written not remember right message, already tested several versions different cm old and new versions and other models without the j500m, already tried to install on my adb sideload too, but all I get this error a long time already managed to perform this installation but now I can no longer
obs: I went to the Android 6.0 but I downgrade back to 5.1.1 and so to install the 12.1 cm but can not
NOTE 2: already tried the 2.8 version of TWRP also.
help me really want to run this rom
sorry my bad english
I used the CM12.1 by nick verse and it was good. Try re flashing the stock rom then the recovery before you flash CM12.1
John
twrp Porter-
as we know there is no tool available to port twrp for mt67XX. Phone so here i create a Simple and user friendly tool to Manually Port twrp for the Mediatek MT67XX Phone also Work with MT65XX new 32 bit phone .
The tool is Not based on Source This is a manually Porting Method where we use Stock Recovery to Port a custom Recovery. i have Port twrp for almost all latest MT67XX Chip from source and you can use as a Port Recovery,[Link below]..
What you need
1. tool Download Here https://androidfilehost.com/?fid=962021903579481564
2. Stock recovery [dump using SP tool or using Miracle box] Rename it 'stock.img'
3. Ported twrp from same chip [ Here is My collection- https://www.androidfilehost.com/?w=files&flid=220042] select according your chip if not work try from other phone. rename it 'port.img'
Note- i have Not enable auto copy to keep work with all chip Manually copy Paste Require.
Instructions-
Place port.img and stock.img in tool folder
Run twrp Kitchen.exe and follow on screen instructions
Donation-
You can Donate Me http://paypal.me/droiddeveloper
Faq-
1. Touch Not Work-
it's due to kernel source try to port from other twrp,
final solution use OTG or compile from source.
2. unable to mount partition's-
check and fix fastab in ramdisk folder before hiting enter.
3,. is this Work on old MT65XX Phone-
yes you can use it for MT65XX phone.
4. is This Method work 100% on all Phone-
No it can't work 100% on all phone but work on up to 90% of Mediatek Phone.
5. is this Support Nougat and oreo Images-
yes this one Support oreo and Nougat Recovery Images.
XDA:DevDB Information
twrp porter , Tool/Utility for all devices (see above for details)
Contributors
XN Logos
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2017-09-30
Created 2017-10-01
Last Updated 2018-01-06
@XN Logos
Thanks for the tool.
I cannot download the recovery
MT6757 6.0 MM.rar
MT6757 Nougat helio P25 6GB RAM.zip
MT6797 Helio X27 6.0MM.rar
you can download from androidfilhost.
here is twrp for ulefone t1 ported using this tool base umi plus e. Helio p25, this tool not work on umidigi crystal 4GB/64GB i have tried but not success. https://androidfilehost.com/?fid=673368273298987398
Thank u for your great job, i think the recovery we obtain is called "image-new.img" (and not "recovery-new.img" as it's mentioned in the screen instruction). I successfully get this recovery but don't know how to flash it ( because my phone is locked and not rooted "LENOVO C2- k10a40-" ( MT6735 ). HELP PLZ and thanks again .
walid77dz said:
Thank u for your great job, i think the recovery we obtain is called "image-new.img" (and not "recovery-new.img" as it's mentioned in the screen instruction). I successfully get this recovery but don't know how to flash it ( because my phone is locked and not rooted "LENOVO C2- k10a40-" ( MT6735 ). HELP PLZ and thanks again .
Click to expand...
Click to collapse
You can flash it using SP flash tools, take scatter file from your ROM and then flash with SP tools...
Here is Fastboot Guide, but you can face adbd and large image error with fastboot.
Code:
fastboot oem unlock
fastboot flash recovery recovery-new.img
Please, help me to find usb vcom drivers for my device : LENOVO C2, k10a40, MT6735. Thank u again
walid77dz said:
Please, help me to find usb vcom drivers for my device : LENOVO C2, k10a40, MT6735. Thank u again
Click to expand...
Click to collapse
I beleive that any question not related to TWRP porter is OT here. Check driver v. 5.1632.
mod edit - needrom links removed not allowed due to registration required in order to download
Here is all Flash tools and drivers-
https://androidfilehost.com/?w=files&flid=216849
XN Logos said:
Here is all Flash tools and drivers-
https://androidfilehost.com/?w=files&flid=216849
Click to expand...
Click to collapse
You can get all news about Mediatek driver and tools (like Flashtool) here:
http://www.androidiani.com/forum/mo...l-flash-di-telefoni-con-chipset-mediatek.html
The latest driver (ADB + Preloader) is 5.1632 (the link that I posted), and is good fro XP up to Windows 10 and didn't rqeuire to disable driver sign.
The latest version for Flashtool (for Windows and Linux) is 5.1728
In the link that I posted are available Gogle Platform Tools (adb.exe/fastboot.exe) usefull for flash boot or recovery without using Flashtool.
base added for Helio X23 [Rename rk.bak to recovery.img]
https://androidfilehost.com/?fid=745849072291678959
Hi
great tool for mtk user y have à mt6797M ( elephone s7 4G )
if I understand correctly I need the recovery stock (I have) and a port recovery ( don't have ) but there are none in the link you give., I tried with MT6797 + helio + x25 + 6.0 but I have a MT6797M with android 7, I'm not sure try to flash .
is it possible for you to make a port of the MT6797M Helio X20 M ?
And my fil name: image-new.img not recovery-new.img it's normal ?
Thinking i got same request as Bradco but MT6753M chip Cubot Cheetah 2
I was not able to find the "1st kernel file", guessing it is xx.img-zImage file.
Here my device nougat stock recovery (or at page 4 device review)
With my device at the moment TWRP seems to work only on Marshmallow. It would be nice if someone like to share an updated recovery
BTW
It took me a few retries to check extracting recoveries requiers 3 or 4 times press enter instead of just a singel press any key
@toBsucht Psp @Bradco we have twrp for both Phone 1. Elephone S7 and 2.cubot cheetah 2 no need to Port again. search Forum..
XN Logos said:
@toBsucht Psp @Bradco we have twrp for both Phone 1. Elephone S7 and 2.cubot cheetah 2 no need to Port again. search Forum..
Click to expand...
Click to collapse
yes there is this twrp: TWRP 3.0.3 by Jemmini (I have it) available on needrom and xda
it works with android 6 without problem but not with android 7.
This TWRP 3.0.3 by Jemmini is based on rom: S7_4g_20170110092009_v1.9.zip which is a rom android 6: https://bbs.elephone.hk/thread-12895-1-1.html#.WdiBplu0OM
My rom got this one: s7_4g_20170814163417_v2.4.zip which android 7 v2.4
I tried this :
1. clean install the rom: s7_4g_20170814163417_v2.4.zip
2. start the phone
3. flash the twrp : TWRP_303_Elephone_S7_4g_v1.9
4. reboot the phone but it is blocking on the logo ( I access the recovery but can not start the phone )
5. y tried 2/3 times but once the recovery install it remains on the logo.
after searching I found only this recovery TWRP_303_Elephone_S7_4g_v1.9
I do not know if there is an update because all DROPbox links are down.
@Bradco
Please read carefully the object of this thread. It's only about TWRP porter.
Is not a thread of support for mod recovery about specific devices.
For this please post in the specific thread for the device. Thanks.
@XN Logos
I propose to add this as first object of firs post
- Scope of this thread
Scope of this thread is only to discuss about TWRP porter application.
Please don't discuss about support for recovery for specific devices.
For this please post in the specific thread for the devices.
bovirus said:
@Bradco
Please read carefully the object of this thread. It's only about TWRP porter.
Is not a thread of support for mod recovery about specific devices.
For this please post in the specific thread for the device. Thanks.
@XN Logos
I propose to add this as first object of firs post
- Scope of this thread
Scope of this thread is only to discuss about TWRP porter application.
Please don't discuss about support for recovery for specific devices.
For this please post in the specific thread for the devices.
Click to expand...
Click to collapse
yes sorry,
I explain just my situation, the subject of my post is well on the port of TWRP for processor MT6797M and not on elephone s7. I must speak well of the phone to explain the problem correctly.
Ps : y test this tuto : https://forum.xda-developers.com/showthread.php?p=32965365#post32965365
but y don't find the file BoardConfig.mk
Pretty much same here!
i took a look to default.prop it use a string:
ro.build.version.sdk=24 (stock v14 recovery)
ro.build.version.sdk=23 ( twrp recovery)
even more that needs to be updated in default.prop file from old TWRP to enable it on API24 i.g.
ro.build.fingerprint (seems to be a littel more work)
i stopped repacking TWRP since i note bad image maybe brick my phone.
Also someone told me marshmallow uses ID_creation code = MOB30J; Nougat uses ID_creation code = NHG47N .... idk
funny i removed a additioinal password request. Another user now got additional :highfive: and idk how it occur
Yes Guys, This thread is only for tool Not for Specific Device. So you can ask only for Port base [MT67XX] not for twrp. if you need twrp You can contact Me or create yourself using tool.
XN Logos said:
Yes Guys, This thread is only for tool Not for Specific Device. So you can ask only for Port base [MT67XX] not for twrp. if you need twrp You can contact Me or create yourself using tool.
Click to expand...
Click to collapse
ok I understand, I want to try to do it myself, can you make a port of MTK 6797M ?
( this is what I needed at the start, I came on this thread to do the twrp myself.
thank you in advance
As already written it is not that easy to use if some errors occur. Also i did not 100% on it which files i have to remove if tool say "delete following":
1. kernel (is it x.img-zImage?)
2. kernel offset (i guess i found)
and that flase "press ANY key" message! Just as a little sidenote for your update.
Hello,
I am using kingwear 98 (kw98)
https://www.smartwatchspecifications.com/Device/kingwear-kw98/
It's a smart watch based on MTK6580.
I am trying to understand what is the best method to install twrp on mediatek devices.
1. Is it by using the magic twrp installer ?
2. Or by manually porting twrp to our specific device , as seen in some tutorials here (porting twrp with same chipset into socket recovery)?
Well, actually I did try a 3rd option:[/B][/B]
3. I tried to use AllCall-W1_recovery recovery.img ( which has the same chipset).
https://mega.nz/#!kfgmmRRD!RcvPwf0Jc-BAwM4Sf9fYJrmF3DsTQTEYtE2LVeWyE10
Surprisingly it worked . Yet, after several days without issues, last week it became dead.
So, I don't understand how it worked in the first place (it is same chipset, but probably use totally different interface , and drivers ! ) , and if it became dead because something it might be wrong to put same recovery image of another device, without. proper porting.
So, should I flash same image (allcall W1 recovery) again on a new kw98 device that I will buy, or use one of the above methods (port twrp manually into my stock, or install magic twrp for mediatek).
Thank you,
ranran
Hello, I managed to install TWRP in a Samsung Galaxy Note SM-N900, which seems to be as far as I can tell the ha3g variant. The TWRP that I could install is 3.4.0-0-ha3g and it seems to work (thou I cannot always boot into it).
After that I did copy the zip files for lineage-14.1-20200717 in a SD card, and proceeded to wipe the internal data (cache, System, data, and dvlink partitions). Then I tried to install the aforementioned zip file, and it shows the blue progress bar stuck at the very begining and the message "patching system image unconditionally" until the battery runs out (like hours).
What step I am missing?
SM900 is not Qualcom its Exynos model not ha3g .
See EXYNOS section and TWRP ,me for twrp variants .
Do not flash ha3g on non ha3g models .
Galaxy Note 3 Exynos Android Development
Android development for the Exynos-powered Galaxy Note 3
forum.xda-developers.com
well, that is exactly what I am doing. Sorry if I am slow around here, but the link that you provided just sent me to the forum where this question is posted. There is some discution about official lineageOS for ha3g there, but is 2 years old and the link to the download piece is broken, actually....
Aah, no. I just realized that is not the same subforum. Thanks.
wpkzz said:
Sorry if I am reposting, but I am a bit confused about how the hierarchy of subforums works here, and I thought this question was on Q&A, but I was redirected here:
Hello, I managed to install TWRP in a Samsung Galaxy Note SM-N900, which seems to be as far as I can tell the ha3g variant. The TWRP that I could install is 3.4.0-0-ha3g and it seems to work (thou I cannot always boot into it).
After that I did copy the zip files for lineage-14.1-20200717 in a SD card, and proceeded to wipe the internal data (cache, System, data, and dvlink partitions). Then I tried to install the aforementioned zip file, and it shows the blue progress bar stuck at the very begining and the message "patching system image unconditionally" until the battery runs out (like hours).
What step I am missing?
Click to expand...
Click to collapse
It's happened with me too when I am using the latest version of twrp. I go back to v3.1 of twrp and it's working fine now
Basics you are flashing stuff for qualcom model , you have exynos model .
Sorry JJEgan, but I do not follow you. I have the Exynos Variant and I am installing things meant for the Exynos variant. I never said that I am flashing stuff for Qualcom. The TWRP that I downloaded has in its name this:
twrp-3.4.0.0-ha3g.img
So, it seems to be the right one (and it seems to work).
And the lineage os, after unzipping it, in the file updater-script, has this line
...Target: samsung/ha3gub/ha3g:5.0...
So, they seem to be for the Exynos Variant, if the exynos is the ha3g.... and as far as I can tell, they are the same. Or at least the links that I followed said that, like this one:
https://forum.xda-developers.com/t/recovery-exynos-n900-official-twrp-for-ha3g.3406899/
Try an older TWRP.
Try a different rom .
Well I did try another os rom, namely mokee rom 7.1. It could be installed, aparently, but it doesn't seem to be able to run. It did the full install (I repeated the process three times to check) and it always reported succesfull install, but when I tried to start the phone it shows the "Galaxy Note " start screen and then goes black (and off, it seems). The twrp can still be used, though.
I shall try the twrp 3.1 and see what happens.
Okey, i tried with the twrp 3.1 and it showed the full install of lineageos-14.1, but it happened the same as with the mokee rom: when it restarts it shows the Galaxy Note 3 screen, then goes blank/black and it shuts off. Let my try another method and see what happens.
No luck with adb sideload either. Same result.