[INFO][MT2-L03]ClockWorkMod recovery config for MT2L03 - Huawei Ascend Mate 2

Hi,
Just want to share what I already did on clockworkmod recovery, hopefully it can be a little bit helpful. It is mostly based on the TWRP build.
https://github.com/xordos/android_device_huawei_MT2L03/tree/cm-10.2
I will not post the image file as I think TWRP is better for daily use recovery. This is just shared purely for development purpose.
Cheers,
xordos.

Related

[Q] Where is CWM manager on δ-HyperDroid-Androidmeda-v3.0?

HI,
I've flashed the latest Androidmeda over the previous version (VXD).
I've noticed that after flashing, CWM manager was missing from the app list.
According to the changelog, no changes were made to CWM manager application, and even the kernel is the same, so why can't i find CWM manager?
shrek3 said:
HI,
I've flashed the latest Androidmeda over the previous version (VXD).
I've noticed that after flashing, CWM manager was missing from the app list.
According to the changelog, no changes were made to CWM manager application, and even the kernel is the same, so why can't i find CWM manager?
Click to expand...
Click to collapse
As this is a ROM related issue, please post your question in Androidmeda thread.
P.S.: You may have to flash a kernel containing the CWM Manager app (e.g. CF-Root) to bring it back again to your phone. Then re-flash the ROM's kernel back.
It_ler said:
As this is a ROM related issue, please post your question in Androidmeda thread.
P.S.: You may have to flash a kernel containing the CWM Manager app (e.g. CF-Root) to bring it back again to your phone. Then re-flash the ROM's kernel back.
Click to expand...
Click to collapse
Thank you for your quick response, It_ler, i'll give it a shot. too bad that the ROM developers didn't mention it in their changelog.
Regarding the posting issue, this is the first time that I've posted a comment here, and according to this:
"shrek3, you do not have permission to access this page. This could be due to one of several reasons:
Please Read: New members (those with fewer than 10 posts) are not permitted to post to development-related forums. The developer forums are intended for experienced users and developers to discuss ways to improve technical aspects related to ROMs and Software. While you may be an expert, we ask ALL users to avoid posting questions about using or installing ROMs and software in the Development Forums. To encourage this new Users can read but not post in these forums.
To ask Questions about developing your device, installing ROMs, software and themes you must go to the Q&A or General Forum.
Remember, your question has very likely been asked already, so please search before posting.
Your user account may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation."
I cant post this question in Androidmeda thread.
Just go to the Market and install the app AppExtractor. You can extract the APK from your nan-backup (made with CWM) and saved on the sdcard. Then install the APK as usual .
Sent from my GT-I9100 using xda premium
UpInTheAir said:
Just go to the Market and install the app AppExtractor. You can extract the APK from your nan-backup (made with CWM) and saved on the sdcard. Then install the APK as usual .
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
That's the weird thing, UpInTheAir. that if i'm flashing the previous ROM (VXD), i can see that CWM manager is present, and the version is 3.0. and when i open the same ROM (on my PC), i cant find the CWM apk anywhere. I've extracted the 2.8.7 ROM (the one that was released before VXD) and i did found CWM manager apk under the data folder, which was version 2.0.
So i was just wondering, how the version was upgraded from 2.0 to 3.0 after I've flash the VXD ROM, even if there wasn't CWM apk inside, and the kernel is the same kernel?
Sorry if I've confused you guys, but I'm just starting to get to know the Android OS structure more deeply, and i would really like to know what I've been missing.
Thanks
Did the ROM come with a different or updated custom kernel? So maybe updated with the kernel part of the ROM ?
The kernel and recovery partition go hand in hand.
Eg. Flashing Chainfire's CF-Root kernel will give both CWM Manager & CWM Recovery.
Sent from my GT-I9100 using xda premium
Search for "CWM Manager apk" on the forums, there are copies of CWM Manager 2.0 floating around. It installs as an app. Unsure if there are versions of 3.0 available.
Actually, yes. but as far as i understood from the developers, they didn't touch the kernel.
Is there a way to compare between the previous kernel and the current?
I know there is a way to extract the Zimage file, like any other Linux kernel, but would i be able to know the differences?
And one more question: on post #2 by It_ler, he suggested to flash a different kernel (i.e. CF-Root) , and then flash the ROM kernel. if i'll do that, then the latter kernel that i flashed, will wipe also the CWM (recovery and manger) that were flashed earlier, am i right?

(Q) how do I make android for my phone with no rom? And more Q's

Every tutorial I have read states that to make a custom rom for my phone, I need to download a rom for my phone first. Huh?
My phone is the kyocera rise from sprint.
As far as I know there are no roms publicly available for my phone. I have attempted to make a nandroid backup to see if that would produce a base rom to work with but I can't install a custom bootloader cause clockworkmod doesn't support my phone.
I have successfully rooted however.
My goal is to rewrite the AOSP rom to make a whole new OS for my phone based on android.
So in short here are my 2 questions:
How do I make a custom rom with no rom publicly available for my phone?
How do I install a custom bootloader for my phone if cwm doesn't support my phone?
I am not new to programming, I have 8 years of experience.
I know java, ruby, c# and c++ so if the solution requires programming that's fine with me.
Sent from my C5155 using Tapatalk
liquidmetalix said:
Every tutorial I have read states that to make a custom rom for my phone, I need to download a rom for my phone first. Huh?
My phone is the kyocera rise from sprint.
As far as I know there are no roms publicly available for my phone. I have attempted to make a nandroid backup to see if that would produce a base rom to work with but I can't install a custom bootloader cause clockworkmod doesn't support my phone.
I have successfully rooted however.
My goal is to rewrite the AOSP rom to make a whole new OS for my phone based on android.
So in short here are my 2 questions:
How do I make a custom rom with no rom publicly available for my phone?
How do I install a custom bootloader for my phone if cwm doesn't support my phone?
I am not new to programming, I have 8 years of experience.
I know java, ruby, c# and c++ so if the solution requires programming that's fine with me.
Sent from my C5155 using Tapatalk
Click to expand...
Click to collapse
Before you start making a custom ROM your going to want to port CWM to your device that way you can make backups that you can restore if the custom ROM you make doesn't function. To port CWM check out this great guide. After you have successfully ported CWM and tested it you can move on to custom ROM. From here you have two options. Now that you have CWM on your phone you can make a nandroid backup and create a custom ROM from that. The other option is to create a device and vendor tree for your phone and then build AOSP from source using the device and vendor tree. If you need any more help or have any questions let me know .
Thank you for the prompt reply.
That link was very informative.
If I build the AOSP rom and flash it, will I lose the ability to use my hardware keyboard? If so, is there a way to regain it?
I would assume there must be a way to copy the drivers from my nandroid backup but not sure where they are stored.
Sent from my C5155 using Tapatalk
liquidmetalix said:
Thank you for the prompt reply.
That link was very informative.
If I build the AOSP rom and flash it, will I lose the ability to use my hardware keyboard? If so, is there a way to regain it?
I would assume there must be a way to copy the drivers from my nandroid backup but not sure where they are stored.
Sent from my C5155 using Tapatalk
Click to expand...
Click to collapse
When you build an aosp rom from source some parts may be broken like h/w keyboard for example! There are various mentods to fix those! Seeing as you've programming experience it wouldn't be too hard
Check out the chef central!
Sent from my Tab2 using Tapatalk 2
Went about 6 pages deep in chef central and didn't see anything referencing or relating to hardware keyboard issues. I did however see some very interesting posts on kernel editing. Unfortunally kyocera has not made the kernel sources available for my device.
Sent from my C5155 using Tapatalk
liquidmetalix said:
Went about 6 pages deep in chef central and didn't see anything referencing or relating to hardware keyboard issues. I did however see some very interesting posts on kernel editing. Unfortunally kyocera has not made the kernel sources available for my device.
Sent from my C5155 using Tapatalk
Click to expand...
Click to collapse
You can try extracting the drivers for the hardware keyboard which can be found in the kernel. To do this take the boot.img file and split it, from here you will get a ramdisk from the ramdisk you can extract the kernel. From there you should be able to access the kernel and then extract the hardware keyboard drivers.
Sent from my SCH-I535 using xda premium
liquidmetalix said:
Unfortunally kyocera has not made the kernel sources available for my device.
Click to expand...
Click to collapse
The kernel sources have been released since. Here you go: Kyocera Developer
I had this phone for about 2 days before I jumped on a better deal (thanks, Black Friday!). Good luck with developing for this. I know there are a lot of people looking to get at least a custom recovery for it.
This additional information may be helpful as well. Since there is no recovery to flash things (like kernel, mods, etc.) you might want to consider Flash Gordon. It allows you to "flash any flashable zip (except for Roms) without having a recovery installed". If you were to do that, you could then install Onandroid, which allows you to "make a nandroid backup without switching off the phone". With that backup, you could get the necessary files to then create your own ROM. The problem would then be flashing the ROM but if you have the kernel source (see previous post), time, and a lot of will power, you could port CWM or TWRP. Hope this helps someone!

[Q] Changing ROM changes recovery as well?

Hi!
I am new to this phone an I am confused about one thing. With my previous phone, I installed any ROM that I wanted, and the cwm recovery would be the same, and will not be affected at all. But, I changed my ROM to PACman ROM and I noticed that the cwm recovery version changed as well.
So, I have three questions:
- Firstly, How does this work? I opened up a ROM zip package, but I only found the regular android files, but I didn't find any recovery.img. So, how does replacing the ROM replace the recovery work when a ROM is flashed?
- Secondly, does changing only the kernel also change the cwm recovery? For example, if I flash Dorimanx kernel, will it also change the cwm recovery? If yes, then how does this work?
- Lastly, if I build a ROM, is it necessary to add a recovery with the ROM as well? Or, if I build a ROM without recovery, will it affect the recovery when it is flashed?
I know that these questions might have long answers, but I am keen to know the answers, no matter how long they are.
Please try to answer all three of the questions. Or, answer as many as you can, because those questions regarding the changing of cwm recovery is very confusing.
Thank You.
Hello, congrats on your new phone Unfortunately, i can't give you lenghty information about this because i don't think i know that much, but here are some facts for you:
-When you flash a new ROM, it will overwrite kernel too, so you will have a new kernel,
-When you flash a new kernel, it will overwrite the recovery, so you will have a new recovery,for example if A kernel has cwm as recovery, if you flash A kernel you will have cwm, and if B kernel has TWRP as recovery, when you flash B kernel you will have TWRP recovery,
-Since you have to have a kernel for your ROM, if you build a ROM, you must have a kernel=recovery, you can build the kernel yourself or use someone's kernel, but recovery must be embedded in the kernel (As far as i know)
When you start building your own ROM, i think you will find out the "how"s yourself though
Dakura said:
Hello, congrats on your new phone Unfortunately, i can't give you lenghty information about this because i don't think i know that much, but here are some facts for you:
-When you flash a new ROM, it will overwrite kernel too, so you will have a new kernel,
-When you flash a new kernel, it will overwrite the recovery, so you will have a new recovery,for example if A kernel has cwm as recovery, if you flash A kernel you will have cwm, and if B kernel has TWRP as recovery, when you flash B kernel you will have TWRP recovery,
-Since you have to have a kernel for your ROM, if you build a ROM, you must have a kernel=recovery, you can build the kernel yourself or use someone's kernel, but recovery must be embedded in the kernel (As far as i know)
When you start building your own ROM, i think you will find out the "how"s yourself though
Click to expand...
Click to collapse
That was short, but it does kind of make sense. Since I am using CM kernel right now, I guess the recovery will already be in there. But, If I want to create my own kernel from scratch, then are there any guides or information pages that give me an idea on how to do it?
Thanks.
All that stuff is in the development sections (where the devs live), Q&A is the wrong place for stuff like this (Q&A is for n00bs with busted phones). Google/XDA search for specifics or maybe ask a few devs in the threads devoted to their kernels/roms.
Yep, the recovery will be embedded to kernel. Here is the index of guides: http://forum.xda-developers.com/showthread.php?t=1826497 (thanks to pelpa87)
Index of kernels: http://forum.xda-developers.com/showthread.php?t=1702166 (thanks to GaboWinter)
I use G variant and there is a nice tutorial for us, you can read and see if there is anything you want to learn from there : http://forum.xda-developers.com/showthread.php?t=2495727 (thanks to Black_Prince)
MistahBungle said:
All that stuff is in the development sections (where the devs live), Q&A is the wrong place for stuff like this (Q&A is for n00bs with busted phones). Google/XDA search for specifics or maybe ask a few devs in the threads devoted to their kernels/roms.
Click to expand...
Click to collapse
I don't believe you.
Dakura said:
Yep, the recovery will be embedded to kernel. Here is the index of guides: http://forum.xda-developers.com/showthread.php?t=1826497 (thanks to pelpa87)
Index of kernels: http://forum.xda-developers.com/showthread.php?t=1702166 (thanks to GaboWinter)
I use G variant and there is a nice tutorial for us, you can read and see if there is anything you want to learn from there : http://forum.xda-developers.com/showthread.php?t=2495727 (thanks to Black_Prince)
Click to expand...
Click to collapse
Thanks for your time.
Dakura said:
Yep, the recovery will be embedded to kernel.
Click to expand...
Click to collapse
But, if, for example, I install dorimanx kernel, then the recovery embedded in dorimanx kernel will be installed. So, if I dualboot a second ROM from dorimanx recovery, then the recovery from the second ROM would be installed. That would mean that I won't be able to dualboot again?
Hmm, i think dualbooting has some different mechanisms, since you dual boot you have to have ONE kernel that supports dual boot, recovery will be the same since kernel is the same. So basically, you have A rom which has A kernel, then you flash B rom which has B kernel to dualboot, but there can't be two kernels at the same time so you must choose between A kernel or B kernel (both has to support dualboot ofc), and since recovery is embedded in kernel, you will have A recovery or B recovery, not both.

A little help please, I don't want to brick my phone!

I am currently running Beekos PacMan ROM and I love it so far. I need a little help in flashing back to Viper before I go out of town. I was reading on MDMowers post about flashing back to an older ROM from the modded TWRP recovery. I am trying to install Viper back on my phone and use a recovery that is compatible with the apps2sd mod that is somewhere in the development section. Could someone help point me in the right direction or a quick explanation to what recovery I should use and which ones are compatible with apps2sd mod? I would really appreciate any help, info, links and of course your time.
Thanks In Advance!
TheGOAT232412 said:
I am currently running Beekos PacMan ROM and I love it so far. I need a little help in flashing back to Viper before I go out of town. I was reading on MDMowers post about flashing back to an older ROM from the modded TWRP recovery. I am trying to install Viper back on my phone and use a recovery that is compatible with the apps2sd mod that is somewhere in the development section. Could someone help point me in the right direction or a quick explanation to what recovery I should use and which ones are compatible with apps2sd mod? I would really appreciate any help, info, links and of course your time.
Thanks In Advance!
Click to expand...
Click to collapse
To properly install Viper on this phone, you must use a TWRP recovery. CWM variants will appear to work, but Viper install scripts will not work properly. If you love CWM, then you can use TRWP to install Viper, then change recovery to CWM...
Anything TWRP v2.6.3.0 or higher should work with Viper (and I think the apps2sd mod as well). Official v2.6.3.0 link
You may be able to use mdmower's TWRP 2.7.1.2 build (or higher) for fireball "Standard partition layout". Mdmower Fireball TWRP page
I also suggest flashing the Infernal Kernel for improved performance (and swipe-2-wake)
Huge thanks for all the info, it was exactly what I needed.

Kernel and recovery

Hi,
I wish to install a newer ROM than the one I currently have, yet it seems I might need a new kernel and CWM instead if TWRP.
So my questions are:
1. How do I know if I need a new kernel?
2. At some kernel threads, it is said that they only work with kitkat ROMs for example, and other ROMs might brick the phone with this kernel.
So do I flash a new kernel first or a new ROM first? Basically, how do I not brick my phone?
3. I read somewhere that SGS2 users can't install recovery without installing a new kernel. Is it true?
4. I would appreciate some directions about installing a new recovery (I would probably need CWM).
5. Why is it so hard to find answers to these probably many times asked questions?
Thanks.
peasmaker said:
Hi,
I wish to install a newer ROM than the one I currently have, yet it seems I might need a new kernel and CWM instead if TWRP.
So my questions are:
1. How do I know if I need a new kernel?
2. At some kernel threads, it is said that they only work with kitkat ROMs for example, and other ROMs might brick the phone with this kernel.
So do I flash a new kernel first or a new ROM first? Basically, how do I not brick my phone?
3. I read somewhere that SGS2 users can't install recovery without installing a new kernel. Is it true?
4. I would appreciate some directions about installing a new recovery (I would probably need CWM).
5. Why is it so hard to find answers to these probably many times asked questions?
Thanks.
Click to expand...
Click to collapse
1 - if you are happy with your current rom, dont flash a kernel if not sure what you are doing!
2 - kk and LP kernels are not compatible between them as your cpu doesn't fit in a incompatible motherboard ! newer kernels are safe from brickbug ! you wont brick your phone with a wrong kernel (kk kernel over LP rom), just a bootloop.
3 - because a kernel is a recovery and a recovery is a kernel.
4 - Slimsaber is a good rom to start see first and second post
5 - is not hard to find if you know were to look!
ultravy said:
3 - because a kernel is a recovery and a recovery is a kernel.
Click to expand...
Click to collapse
Just a small correction. A recovery (CWM or TWRP) can not be installed by itself because we don't have a recovery partition. Therefore kernel with a custom recovery needs to be installed.
ultravy said:
1 - if you are happy with your current rom, dont flash a kernel if not sure what you are doing!
2 - kk and LP kernels are not compatible between them as your cpu doesn't fit in a incompatible motherboard ! newer kernels are safe from brickbug ! you wont brick your phone with a wrong kernel (kk kernel over LP rom), just a bootloop.
3 - because a kernel is a recovery and a recovery is a kernel.
4 - Slimsaber is a good rom to start see first and second post
5 - is not hard to find if you know were to look!
Click to expand...
Click to collapse
1. I am happy with the current ROM, yet I want to flash the kernel to fix the annoying FPBug and to finally get LP ROM. And I might not know what am I doing, but if I won't try I will never know
I've flashed a new kernel and a new LP ROM, and I'm trying some others.
I still find it difficult to find a kernel that answers my needs since many kernels are hiding in specific posts and some kernel threads doesn't mention which recovery they install.
gsstudios said:
Just a small correction. A recovery (CWM or TWRP) can not be installed by itself because we don't have a recovery partition. Therefore kernel with a custom recovery needs to be installed.
Click to expand...
Click to collapse
I appreciate both help, I learned some new stuff thanks to you guys.

Categories

Resources