Hi guys,
First up here are the details of the phone that I am currently using:
Zeaplus M7
MediaTek MT6752
Android 5.0
Root = YES
Unlocked = YES
Secure = NO
The Problem
I have compiled CWM using the CM-11.0 branch, and TWRP using the OmniRom and TWRP Minimal sources, but I always end up with the same problem, regardless of whether I flash CWM or TWRP.
After flashing either of the recovery.img files to the phone, I can attempt to boot into recovery and what happens is the phone restarts, sits at the splash logo (boot screen) and sits there for around 15-30seconds (using the stock recovery, it will already have booted by this point), and then it will just restart the phone and it will continue to boot to the system as normal.
This happens on both CWM and TWRP. What is causing both the recoveries to hang at the boot screen without actually entering the recovery? Is there a way I can get a logcat or log of what is happening during the recovery bootup so I can check if there are any error messages going on behind the scenes that I am missing out on?
If you need anymore information please let me know!
Thanks
Just committed the most recent files for a CWM (11.0) build. (Also contains some older files used for the TWRP build)
https://github.com/alien-13/android_device_zeaplus_m7
Hopefully that may help out a little bit more. Not 100% sure what could be causing the issue as the P6000 has a working TWRP, and I have based this device tree around the P6000 device tree (with specific changes made to suit the M7).
Not sure if this will help, I also have the z+m7 , have tried the ele p 7000 Rom on it and it works fine, twrp installs fine, but will not download from playstore , both are from needrom made by s7yler, when I go back to m7 Rom with the p7000 twrp package exactly the same happens as happens to your phone, have noticed in m7 Rom and Mijue t500 Rom which are the same, there is a file called Encrypt, which I have never seen in other roms.could this be a problem
There is now a twrp for the zeaplus m7 on the zeaplus forum
Hello,
I try to port Cyanogenmod to my tablet (codename: hwt1a21l/chipset: MSM8916). I build a recovery image according to the CM-Wiki. Target was CM11 because the tablet is based on Android 4.4.4 and huawei have specific downloads for 4.4.4 (kernel source). If this would work, I go further with current CM releases.
After boot into fastboot/rescue and flash the CM-recovery, the tablet restarts repeatly in rescue/fastboot (every time I press the key combination for recovery). If I flash the stock recovery, the stock recovery displays (if I press the combination for recovery).
If I execute a "fastboot boot"-command with my custom image, the output says "signature checking failed". (with "fastboot boot" on an official image, there is no problem, of course)
Bootloader is unlocked. Root access is denied (su command not found and I cannot search through the bin-directories - permission denied). I tried SuperSU, Fararoot, Kingroot, Kingo-Root. If I upload a busybox executable to the device, the shell command of 'busybox su' prints out an error about 'setuid'. A 'chmod s' doesnt work (permission denied).
I have two logs. One log for a working recovery with very detailed information and one with the pre-boot process.
Which steps can be performed to go further? Any hints are welcome
I thought about a custom aboot, sbl-hacking, etc but I didnt find any useful information for this case. (ok, I can buy IDA, which is a little bit expansive )
I read documentation about boot-image signing, but it looks like, that CM do this stuff for me? (keys-file in res is updated)
EDIT: I have no attachments button below my message form?!
Hi I have tablet with similar specs (T1-821L) and also want to compile twrp for it. I haven't much time to do this but I can give you advice to search github for device tree for similar device and modify it later. It's the sources I tried to suit to my device: https://github.com/surdupetru/g620s_twrp. I read also that cyanogenmod sources are more compatibile with Huawei devices but you can encounter problems during compilation. Omni sources are easier to compile from but contains outdated repos which also can brake the compilation and you should drag and drop manually them from cyanogenmod. I suggest you to start with older sources like cm11, cm12.1 or omni 4.4, 5.1. You can also ask more experienced devs on IRC: http://webchat.freenode.net/?channels=twrp or here: http://forum.xda-developers.com/showthread.php?p=32965365 and also g620s devs. Hope this helped you a bit .
I think the problem is the signature validation. It looks like, CM, OMNI, TWRP, etc. doesnt sign the Image with an (appropriate) certificate, that the Huawei accepts.
To fully confirm this assumption, I try to debug with an UART and/or AudioJack "device".
4got said:
Hi I have tablet with similar specs (T1-821L) and also want to compile twrp for it. I haven't much time to do this but I can give you advice to search github for device tree for similar device and modify it later. It's the sources I tried to suit to my device: https://github.com/surdupetru/g620s_twrp. I read also that cyanogenmod sources are more compatibile with Huawei devices but you can encounter problems during compilation. Omni sources are easier to compile from but contains outdated repos which also can brake the compilation and you should drag and drop manually them from cyanogenmod. I suggest you to start with older sources like cm11, cm12.1 or omni 4.4, 5.1. You can also ask more experienced devs on IRC: http://webchat.freenode.net/?channels=twrp or here: http://forum.xda-developers.com/showthread.php?p=32965365 and also g620s devs. Hope this helped you a bit .
Click to expand...
Click to collapse
I have the very same device (T1-821L) did you have any success with TWRP?
Con_Sole said:
I have the very same device (T1-821L) did you have any success with TWRP?
Click to expand...
Click to collapse
Unfortunetly no. I started modifying this tablet month ago and tried many things like: replacing kinguser with supersu but without success and repacking system.img extracted from stock firmware to place su binaries inside but also without success. I thought about bringing supersu to device without twrp because there is FlashFire but if it's impossible I will try to compile twrp.
I downloaded and installed (from twrp.me the new version 3.2.0-0 of the TWRP recovery for our Honor 7 and installed it using version 3.1.1-0. Installation OK but the device remains locked on bootlogo. I reinstalled version 3.1.1-0 with fastboot and the phone started without problems. I reinstalled version 3.2.0-0 with fastboot, the installation was successful but the phone remains locked on bootlogo. Has anyone tried?
yes, I did today and the same problem. I'm using 3.1.1.0
i wrote a message to Team TWRP and they removed v3.2.0.0 from the download site.
The TWRP team has released version 3.2.1-0-plank.img for the H7. Same problem as 3.2.0-0 except that this time the phone succeeds in rebooting in normal mode, but can not reboot in recovery (locked on bootlogo)... Back to 3.1.1-0 ... wait & see
p.s: I warned them
I thought the twrp team was a serious team. But do the recovery tests before publishing them?
no they don't test every release....
i assume there is an automatic build structure - as soon there are a new 'core'-version of twrp the changes are pushed to the device specific trees and at night the build will produce a new recovery for all devices....
TWRP 3.2.1-0 removed from the download site.
Hi, TWRP team response: "Thanks for the report. I will disable the job until the device tree is fixed. The files have been removed."
Someone here to fix the tree?
Would be nice to know, if TWRP writes any log file which notes the cause of the loop or if there is any way to enable a log like these.
I assume, that logcat will not work since we are in an early state of the boot-process and the adb interface won't be up at that time.
Have anyone a copy of TWRP 3.2.* ?
I deleted my copies and the only way to get them would be to create a device tree and i'm not sure how...
Dattel01 said:
Someone here to fix the tree?
Would be nice to know, if TWRP writes any log file which notes the cause of the loop or if there is any way to enable a log like these.
I assume, that logcat will not work since we are in an early state of the boot-process and the adb interface won't be up at that time.
Have anyone a copy of TWRP 3.2.* ?
I deleted my copies and the only way to get them would be to create a device tree and i'm not sure how...
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=818070582850504177
thanks for your reply...
in the meantime i switched the device and my old H7 will have its eventide in the hand of my wife
Is you link a working copy or is it still the old version that crashes?
Twrp
Why there is no option for honor 7x in twrp?
** UNOFFICIAL A-TEAM RELEASE**
*******Testing ONLY*******
**testing has only been done on GN2200 July patch device but should atleast boot into twrp on other sec patch on GN2200 devices***
***Let us know if not***
*****HEED THE WARNING OF IMPENDING APOCALYPSE, DOOM, BOOTLOOPS , BRIMSTONE AND FIRE, AND ALSO TWRP ******
***NOBODY IS RESPONSIBLE FOR WHAT YOU DO WITH THIS EXCEPT YOU***
***DO NOT BUILD AND FLASH THIS UNLESS YOU KNOW EXACTLY WHAT YOUR DOING***
****DONT DO ANYTHING I SAY, I CANT BE HELD RESPONSIBLE FOR WHAT I SAY OR DO*****
**THIS IS AN ** UNOFICIAL RELEASE ** SO DONT GO CRYING TO ANYONE THAT YOU MADE YOURSELF AN EXPENSIVE PAPERWEIGHT IF YOU USE ANYTHING IN THIS POST***
********* THE RESPNSIBILITY LIES SOLELY UPON YOU***
***FLASHING IN CURRENT STATE DOES NOT BOOT INTO SYSTEM****
****READ EVERYTHING BEFORE YOU DO ANYTHING******
******ONLY POSTING THIS FOR DEV PURPOSES*******
******Huge THANKS to PizzaG for this!!!******
***Thanks to Eduardo as well for his contributions, he may still be working on his own release***
Am posting this with a copy/paste i posted in telegram group..
We need people with the knowledge/skills and experience to help get this TWRP finished AND/OR work out the bugs.
GitHub - PizzaG/recovery_device_oneplus_OP515AL1
Contribute to PizzaG/recovery_device_oneplus_OP515AL1 development by creating an account on GitHub.
github.com
*this is not ready for release but the source is here for anyone who can build upon it*
touch is not working
you cant fastboot boot on this device so DO NOT flash this to your device without a backup of your stock/current boot image
issues we are having is no touch, can't mount /data, and so far cant boot into system with the recovery installed so if you want to use it youll need to flash this to boot, use it for whatever and then flash stock boot back, if your magisk patched youll need to flash the backup of that patched boot image you made before flashing this in order to get back into your system....... i have sort of found a slight work around for having to keep flashing the boot partitions until someone can get this to boot by placing my current boot image on an sdcard along with the twrp, flash the twrp to the active boot partition, boot into twrp, install image and install your backed up boot image to the current slot, then go back to advanced and install twrp to ramdisk and select and install the twrp image to the ramdisk, if your magisk patched you need to flash magisk zip right now, you can adb shell into twrp to pull a copy of this boot image if you want and i have flashed my "twrp-ramdisk installed boot image" on the Slot that my system is on and stock/backup boot image to inactive slot because its the only way to boot back to system for now without reflashing the stock(backed up) boot image back to the slot. and reboot into bootloader, change active and reboot and your back into your system.... when you need twrp you can set active to the other slot, it will bootloop once into bootloader and choose recovery to get back to twrp... when done reboot to bootloader and set active back to the other slot and reboot into system.............otg mouse works, adb works, mtp works, some work has been done on the touch but thats still not working yet, everything seems to be mounting except data............. big shout out to PizzaG for this
***this is a very round-about way to get a currently buggy twrp on the device but if you have a usb-c adapter and mouse you can navigate twrp....***
PizzaG doesnt have the device and has spent more time than anyone could possibly ask someone to spend on this for free... I dont have the skills required yet to really work on this. I have tested as much as possible and here it is for those who can build and work on it. i dont recommend releasing in its current form because im sure alot of people will be complaining and bricking their devices. if you can build it im sure you can work on it and should have the skills to atleast recover and have the sense to make backups first.......
Thanks again to everyone who has already donated the valuable time working on this for us and to everyone who will follow and build upon this!
You can find the telegram group for our device here:
You can find the A-Team in telegram
Also FYI in case you missed the post about our kernel source, it can be found here:
GitHub - OnePlusOSS/android_kernel_msm-5.4_oneplus_sm6375 at oneplus/sm6375_r_12.0.1_oneplus_nord_n20_5g
Contribute to OnePlusOSS/android_kernel_msm-5.4_oneplus_sm6375 development by creating an account on GitHub.
github.com
If anyone with experience building twrp and especially for OnePlus devices needs a tester or any files from the device hit me up on telegram @PsYk0n4uT2 and I will do my best to provide whatever you need and test builds along with providing logs.
heres a compiled boot image from the above tree as of 10/02/2022.
**remeber it DOES NOT boot to system, this is twrp only, not installed into recovery ramdisk yet. so BACKUP YOUR STOCK(current) boot image FIRST**** you will have to flash your stock(current) boot image back to boot back into your system. you can sort of get around this by above mentioned method BUT here it is for the GN2200 anyways. working on my July patched device and my May patched device so it should work for other GN2200 sec patches too...
***BACKUP BACKUP BACKUP*****
also cant change active slot from twrp, must reboot to bootloader to change active slot
Heres TWRP installed to ramdisk on a july patched boot image. does not boot to system but since it doesnt you should still be able to use this on any patch for testing purposes.....
You can backup your boot image and flash your current boot image to inactive slot and flash this to active slot by selecting recovery from bootloader after it loops once.... use twrp then go back to bootloader and change active and reboot to get back into your system.
**BACKUP YOUR CURRENT BOOT IMAGE****
***DOES NOT BOOT TO SYSTEM**
***YOU WILL NEED YOUR CURRENT BOOT IMAGE TO BOOT YOUR SYSTEM< YOU SHOULD ALREADY HAVE A BACKUP OF YOUR STOCK IMAGE IN THE CASE THAT YOU ARE MAGISK PATCHED ALREADY< KEEP A COPY OF BOTH IN CASE YOU DECIDE TO WIPE DATA< YOU WILL NOT BOOT BACK INTO YOUR SYSTEM WITH A MAGISK PATCHED BOOT IMAGE IF YOU WIPE DATA*******
if someone can get their system to boot after installing the TWRP from post 4 or their own build after personal edits please post here how you were able to achieve the install and maintain booting into system..
currently twrp indicates that path to /mnt could not be found and cant mount /data .. i think if someone could fix this maybe some progress could be made
ScarletWizard said:
I wonder if TWRP will work for devices with a serial number defeicy
Click to expand...
Click to collapse
halfway working on mine, just isnt finished yet, we need someone who knows alot more about this than i do. another dev is working on twrp but needs a device. the serial wont affect anything else other than the oneplus care app and getting the unlock token..... other than that u have full functionality.... the one posted above needs ALOT of work to finish. no touch yet but it could work for SOME things....
I know C/C++ at a decent level, however; I don't have much experience with low level stuff (especially dealing with bootloaders and other specific proprietary android kernel stuff). If there is anything that needs testing, I am down for it since this is just a secondary phone for me and I won't be too upset if it explodes.
I'm going to attempt this
[ SOLUTION ] [ MTK ] to Fix Touch not Working on TWRP / Philz Due to Kernel Disabled Touch.
In this tutorial, i'm going to show how i managed to patch kernel to enable touch in recovery TWRP / Philz. WARNING : This worked fo...
factopea.blogspot.com
It's written for mtk device but might have similar enough instructions to port for qcom kernel,
But I believe this is what is needed to get the TWRP touch going
Is the trwp.fstab using the right version? Both have different
Code:
/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,inlinecrypt,reserve_root=32768,resgid=1065,fsync_mode=nobarrier latemount,wait,resize,check,formattable,fileencryption=aes-256-xts:aes-256-cts:v2+inlinecrypt_optimized+wrappedkey_v0,keydirectory=/metadata/vold/metadata_encryption,metadata_encryption=aes-256-xts:wrappedkey_v0,quota,reservedsize=128M,checkpoint=fs
Try this instead in twrp.fstab
Code:
/data f2fs /dev/block/bootdevice/by-name/userdata flags=fileencryption=ice:aes-256-cts;wrappedkey;keydirectory=/metadata/vold/metadata_encryption
Techted89 said:
Is the trwp.fstab using the right version? Both have different
Code:
/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,inlinecrypt,reserve_root=32768,resgid=1065,fsync_mode=nobarrier latemount,wait,resize,check,formattable,fileencryption=aes-256-xts:aes-256-cts:v2+inlinecrypt_optimized+wrappedkey_v0,keydirectory=/metadata/vold/metadata_encryption,metadata_encryption=aes-256-xts:wrappedkey_v0,quota,reservedsize=128M,checkpoint=fs
Try this instead in twrp.fstab
Code:
/data f2fs /dev/block/bootdevice/by-name/userdata flags=fileencryption=ice:aes-256-cts;wrappedkey;keydirectory=/metadata/vold/metadata_encryption
Click to expand...
Click to collapse
i just unpacked the twrp image with AIK and made the suggested edits and repacked, reflashed, same...... another person is working on twrp and has gotten much of the fstab corrected in their build but their keeping their source closed til they get it ready for release and is still very far from being finished with it and doesnt have much time to work on it right now so we are just kinda stuck waiting on someone that knows what their doing to help get this going. the other person has touch working on theirs so i know its possible i just dont know how long it will be before we see a beta even
Techted89 said:
Is the trwp.fstab using the right version? Both have different
Code:
/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,inlinecrypt,reserve_root=32768,resgid=1065,fsync_mode=nobarrier latemount,wait,resize,check,formattable,fileencryption=aes-256-xts:aes-256-cts:v2+inlinecrypt_optimized+wrappedkey_v0,keydirectory=/metadata/vold/metadata_encryption,metadata_encryption=aes-256-xts:wrappedkey_v0,quota,reservedsize=128M,checkpoint=fs
Try this instead in twrp.fstab
Code:
/data f2fs /dev/block/bootdevice/by-name/userdata flags=fileencryption=ice:aes-256-cts;wrappedkey;keydirectory=/metadata/vold/metadata_encryption
Click to expand...
Click to collapse
also i see a recovery.fstab instead of twrp.fstab in /system/etc. is this what your referring to?
You need both from what iv read ,. TWRP.flags is a module that rewrites the stab at a certain point which may be the reason it's not compiling but I will post. Recovery.fstab is supposed to be a copy paste from the boot.img and gives the general mount partitions locations,. TWRP.fstab is mounted using the same partitions but different format/flag structure to be available to TWRP .
Techted89 said:
You need both from what iv read ,. TWRP.flags is a module that rewrites the stab at a certain point which may be the reason it's not compiling but I will post. Recovery.fstab is supposed to be a copy paste from the boot.img and gives the general mount partitions locations,. TWRP.fstab is mounted using the same partitions but different format/flag structure to be available to TWRP .
Click to expand...
Click to collapse
Interesting article above. Were you able to get that to work? I know it says MTK but seems like mechanism should be the same, or atleast I would assume anyways that the function would be very similar in the case of a flag. Was told you needed to use original kernel but then I couldn't get that to boot period. I'm out of my area of knowledge at this point but always willing to learn.
Also I tried messing around a little with the f stab and TWRP flags I was told that TWRP flags is pretty much the same as the twrp.fstab... also this build needs to have something added to the drivers I do believe that this is somehow related to USB touch it is a goodix gt9886 touch panel using the Samsung 9886 drivers. Maybe the init's need some help here as well.
I have the programming knowwledge that TWRP would require, but have not as of yet created one as my devices were typically readily complete before-hand. Once my device is back up, and running I am going to boot into Ubuntu and give it a go.
I need some excuse to have learned assembly x86, c, c++, Java, Python, and rust and have been eyeing learning scripting so it could be a fun side project assuming it is still incomplete as of the moment?
Is it normal for manufacturers to use components from other's in their builds? The kernel posted seemed to indicate at least a couple Samsung files included.
Well C is a guarantee possibly some C++ as well and definitely some sh scripting if you know rust and know how to attach it to C well enough that could add more possibilities I would imagine. The recovery is from my understanding in the boot image Android Image Kitchen would help you see it unmodified if that is the case.
I found a unofficial TWRP that flashes to the boot partition, and works pretty damn well, id have to say! I am not an experienced developer, I just like to flash around on my phone in my spare time.. Anyways here y'all go:
I am down while I got partitions backed up to the cloud.