Hi,
I own a Huawei G535-L11 with unlocked bootloader and no system installed (the entire system partition was wiped during a faulty update).
I'm trying to compile a ClockworkMod Recovery for this device but every image I compile boots into a black screen.
The device mounts a Qualcomm Snapdragon 400 with an Adreno 305 GPU.
The kernel is available for download here. And here is a repository with the changes I made so far.
I would greatly appreciate any help to compile a working CWM.
Thanks.
Related
Hi i have iball slide 6318i Rockchip (rk2928) device
I have been trying to make CWM recovery from past one week with no luck all i get is black screen on bootiing into recovery :crying:
here is stock recovery -click
here is boot.img - click
here is CWM recovery - Touch - Non touch
(that i buid using builder.clockworkmod.com touch one status, manifest is here)
here is the method i used to get all required img files http://forum.xda-developers.com/images/icons/advanced/prompt.png
su
cat /proc/mtd
dd if=/dev/mtd/mtd3 of=/sdcard/recovery.img
And i have also tried the generic CWM recovery for rk2928 devices by fun [here] it also didnt work
Device specifications
Os JELLYBEAN 4.1.1
Ram 1gb ddr3
Cpu 1.2Ghz arm cortex a9
reply appreciated :good::good:
sooorajjj said:
Hi i have iball slide 6318i Rockchip (rk2928) device
I have been trying to make CWM recovery from past one week with no luck all i get is black screen on bootiing into recovery :crying:
here is stock recovery -click
here is boot.img - click
here is CWM recovery - Touch - Non touch
(that i buid using builder.clockworkmod.com touch one status, manifest is here)
here is the method i used to get all required img files http://forum.xda-developers.com/images/icons/advanced/prompt.png
su
cat /proc/mtd
dd if=/dev/mtd/mtd3 of=/sdcard/recovery.img
And i have also tried the generic CWM recovery for rk2928 devices by fun [here] it also didnt work
Device specifications
Os JELLYBEAN 4.1.1
Ram 1gb ddr3
Cpu 1.2Ghz arm cortex a9
reply appreciated :good::good:
Click to expand...
Click to collapse
Hi,
did You manage to get CWM working? I have a similar device, though fun_s generic CWM works for me, I want to build my own to make a solid ROM for my device!
Shmarkus said:
Hi,
did You manage to get CWM working? I have a similar device, though fun_s generic CWM works for me, I want to build my own to make a solid ROM for my device!
Click to expand...
Click to collapse
yes i got funs recovery to work on this tablet and if u want to make u can make one for this device but remember ter are no rockchip 2928 sources available:silly::silly::silly:
sooorajjj said:
yes i got funs recovery to work on this tablet and if u want to make u can make one for this device but remember ter are no rockchip 2928 sources available:silly::silly::silly:
Click to expand...
Click to collapse
Hi,
thanks for Your reply. I was planning to use prebuilt kernel. But first, I'd need to get my CWM working and it's a pain without proper reference. Fun_'s generic image (from your first post) works fine for me but there's something missing or wrong in the boardconfig.
What did You do to get the recovery working? I am experiencing similar problems with my recovery (black screen / screen with only backlight)
Shmarkus said:
Hi,
thanks for Your reply. I was planning to use prebuilt kernel. But first, I'd need to get my CWM working and it's a pain without proper reference. Fun_'s generic image (from your first post) works fine for me but there's something missing or wrong in the boardconfig.
What did You do to get the recovery working? I am experiencing similar problems with my recovery (black screen / screen with only backlight)
Click to expand...
Click to collapse
nah the black screen is not recovery buddy its rkflashmod
and my recovery works as expected take a look here
and if u need more info pls pm or post ur whatsapp id or no
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
I flashed a custom ROM, which I compiled from source, to my Archos 101c Platinum tablet and now the touchscreen is flipped (touches on the left side of the screen result in touches on the right of the screen). The partitions that the OTA update updated are the system, recovery and boot partitions.
I flashed the system partition to a known working version, and it did not fix the issue. I assume this means the problem is in the boot partition, which I do not have the source code for (the pre-compiled binaries are present in the source tree).
Has anyone had this problem before, or know what the fix is?
cameron-martin said:
I flashed a custom ROM, which I compiled from source, to my Archos 101c Platinum tablet and now the touchscreen is flipped (touches on the left side of the screen result in touches on the right of the screen). The partitions that the OTA update updated are the system, recovery and boot partitions.
I flashed the system partition to a known working version, and it did not fix the issue. I assume this means the problem is in the boot partition, which I do not have the source code for (the pre-compiled binaries are present in the source tree).
Has anyone had this problem before, or know what the fix is?
Click to expand...
Click to collapse
I have the same device since some days. How did you flash it. I didn't see any root, recovery, custom rom threads so far.
Hi, first of all let me clear some things up about my phone.
Model: Intex Cloud Tread (Not a very popular phone so no developers on XDA)
Stock ROM: Android 5.1
Rooted: Yes
Chipset: MT6591 (The same as MT6592 just 2 cores less. So my guess is 6592 stuff should also work. Please correct me if I am wrong)
Kernel: 3.10.72
Bootloader: Unlocked
Custom Recovery: NO! :crying: <-- This is my issue.
I've tried MTKDROID Tools to make a CWM recovery. But when booted into the recovery it just show a grey screen and slowly fade away into a shutdown.
Tried TWRP with Easy Magic TWRP (Both Auto and Manual using the recovery.img) and it also showed the grey screen and turned off after a while.
When I searched all over google for day and nights for quite a few months now I learned that both the methods only work until KITKAT. (Still not sure about that)
I don't know what I should do next. I'm desperate for a recovery. Should I manually port a TWRP recovery? If then, from where should I port? An how exactly should I port?
I've found some recoveries for MT6592 and I was thinking if it will support my 6591 and will it work with lollipop?
Please help!
Never mind. Successfully ported TWRP 3.0. I will soon upload it here for other users...
Hi. I recently bought couple of tv boxes and decided to modify their firmware for my needs (root in progress).
All devices are Amlogic S905X based, so i found multiple TWRP builds for s905x and tried to boot from sdcard.
Obviously i failed: none of them were loaded and device just stuck at logo screen. So i decided to build my own version of TWRP based on stock recovery. As far as i'm writing this message obviously i failed again.
I'm unable to unpack stock ramdisk and kernel, looks like they were encrypted and are decrypted by second stage bootloader during boot. Though i'm experienced in cracking but i never had a deal with bootloader disassembly and analysis, so i need help unpacking this at least tell me how to disassemble bootloader correctly.
I've attached recovery and boot images.
boot - https: //yadi.sk/d/zpwSfpHhAx4QGQ
recovery = https: //yadi.sk/d/67jx76xOYUU0Mw