Hey guys,
Do you believe it would be possible to get Team Win Recovery Project on our devices? Because it looks much better than clockworkmod and it has so great functions! But I don't know much about this recovery; if this is only for nexus devices or Samsung or whatever, I just wanted to ask
It looks like they took the AOSP recovery and built it on top, but do you think it would be possible on xperias?
Sent from my Nexus 7 running Android 4.2.1
Okay it looks like we could give it a try and compile it, so would anybody be interested?
Who wants to know what TWRP is could look here!
There is a working recovery for the Xperia S, so maybe we could get one, too? Any developer who would be interested in that?
mihahn said:
Hey guys,
Do you believe it would be possible to get Team Win Recovery Project on our devices? Because it looks much better than clockworkmod and it has so great functions! But I don't know much about this recovery; if this is only for nexus devices or Samsung or whatever, I just wanted to ask
It looks like they took the AOSP recovery and built it on top, but do you think it would be possible on xperias?
Sent from my Nexus 7 running Android 4.2.1
Click to expand...
Click to collapse
I am pretty sure it can be done, because I am pretty sure there is support for mdpi screens (320x480). Thomas1991_12 compiled it for the Ray and I know that it wasn't easy and that ChampionSwimmer helped him out with the dual ramdisk kernel. The instructions from dees_troy are pretty easy to follow but of course it didn't work right out of the box but Thomas1991_12 might be able to help you out. Here is the final product thread: http://forum.xda-developers.com/showthread.php?t=2046977 and here is the dev thread: http://forum.xda-developers.com/showthread.php?t=1948097. It is also working on the X8 at least for ics.
TWRP is really nice. It has some added features which are nice but it is also a lot faster than CWM, at least on my device.
justmpm said:
I am pretty sure it can be done, because I am pretty sure there is support for mdpi screens (320x480). Thomas1991_12 compiled it for the Ray and I know that it wasn't easy and that ChampionSwimmer helped him out with the dual ramdisk kernel. The instructions from dees_troy are pretty easy to follow but of course it didn't work right out of the box but Thomas1991_12 might be able to help you out. Here is the final product thread: http://forum.xda-developers.com/showthread.php?t=2046977 and here is the dev thread: http://forum.xda-developers.com/showthread.php?t=1948097. It is also working on the X8 at least for ics.
TWRP is really nice. It has some added features which are nice but it is also a lot faster than CWM, at least on my device.
Click to expand...
Click to collapse
I would like to see this done, too, but I'm no developer at all, never did anything regarding kernels. I could try to get the recovery image, but I wouldn't know what to do after that. And if there are many errors I couldn't go on, so maybe a "real" dev could do it
Do you think we could even try to do this with cm10.1 cyanogenmod sources or better sync to cm9?
Edit syncing my repos to cm9, let's see how it works!
Okay I'm trying it on cm9, what to do with this error? I thought there was something to delete but not sure
Code:
make: *** Keine Regel vorhanden, um das Target »bootable/recovery/res/images/icon_firmware_error.png«,
benötigt von »out/target/product/mango/root/res/images/icon_firmware_error.png«, zu erstellen. Schluss.
Can you help me?
EDIT: Got it by deleting the whole #PRODUCT_COPY_FILES like explained here, but after flashing with
Code:
fastboot flash boot recovery.img
I get the FreeXperia logo and a black screen. What to do now?
mihahn said:
Okay I'm trying it on cm9, what to do with this error? I thought there was something to delete but not sure
Code:
make: *** Keine Regel vorhanden, um das Target »bootable/recovery/res/images/icon_firmware_error.png«,
benötigt von »out/target/product/mango/root/res/images/icon_firmware_error.png«, zu erstellen. Schluss.
Can you help me?
EDIT: Got it by deleting the whole #PRODUCT_COPY_FILES like explained here, but after flashing with
Code:
fastboot flash boot recovery.img
I get the FreeXperia logo and a black screen. What to do now?
Click to expand...
Click to collapse
obviously, debug. as its been said by justmpm it wont just work out of the box just like that. u probably need to to ask Thomas1991_12 what he changed in the source to get it working for ray. since all xperia 2011 gen share similar hardware, ray config should work for other 2011 phone too with minimal changes.
an0nym0us_ said:
obviously, debug. as its been said by justmpm it wont just work out of the box just like that. u probably need to to ask Thomas1991_12 what he changed in the source to get it working for ray. since all xperia 2011 gen share similar hardware, ray config should work for other 2011 phone too with minimal changes.
Click to expand...
Click to collapse
I wrote him a PM, hope he could help me :good:
Can't thank you for now because the 8 thx limit
mihahn said:
I wrote him a PM, hope he could help me :good:
Can't thank you for now because the 8 thx limit
Click to expand...
Click to collapse
I think Thomas1992_12 might be taking a holiday, as he isn't replying to questions in his kernel threads.
I never tried to compile with cm9 but with cm10 the black screen is where I got stuck. Thomas1992_12 was able to get past this point and if I remember correctly, the problem is with init.rc. If you check the ray dev thread, he has a solution for getting past it. After you fix this, you will
probably face the "ghost touches" on the screen and then you will have to figure out how to boot into recovery. Again, Thomas and/or ChampionSwimmer will probably be able to give you the fixes. But don't give up....you are really close!\
justmpm said:
I think Thomas1992_12 might be taking a holiday, as he isn't replying to questions in his kernel threads.
I never tried to compile with cm9 but with cm10 the black screen is where I got stuck. Thomas1992_12 was able to get past this point and if I remember correctly, the problem is with init.rc. If you check the ray dev thread, he has a solution for getting past it. After you fix this, you will
probably face the "ghost touches" on the screen and then you will have to figure out how to boot into recovery. Again, Thomas and/or ChampionSwimmer will probably be able to give you the fixes. But don't give up....you are really close!\
Click to expand...
Click to collapse
Thanks, I really want this project to be done!
First I downloaded the TWRP bootable/recovery sources as a zip, but the zip was named ..-jb-..zip so now after some research I'm trying it with ...-master-...zip and I hope I will get past this black screen. The init.rc is the one from TWRP, because I replaced the whole bootable/recovery folder with the files/folders from the master zip...
I think I will ask championswimmer, but I guess he is very busy, because he's such a great dev! :good:
GUYS I GOT IT! WORKING!!! TOUCH IS WORKING VERY WELL!!!
BUT!
I just flashed the cm9 FXP kernel and after that I flashed the recovery image. I plugged off and powered on and it's booting straight into TeamWinRecovery 2.2.2.1, hope somebody could help me to get booting in system.
Time is wrong, but touch is working guys
Will upload it for testing purpose if you want :good:
Working:
Touch
File Manager
Settings
Terminal Command
Onscreen Keyboard
Flashing Files
Wiping Cache/Dalvik Cache
Backup
Locking Phone in Recovery
Need to test:
Mount usb (not working in linux, will test with windows tomorrow)
Restore
Changing time zone
Not working:
Booting into system
Click to expand...
Click to collapse
mihahn said:
GUYS I GOT IT! WORKING!!! TOUCH IS WORKING VERY WELL!!!
BUT!
I just flashed the cm9 FXP kernel and after that I flashed the recovery image. I plugged off and powered on and it's booting straight into TeamWinRecovery 2.2.2.1, hope somebody could help me to get booting in system.
Time is wrong, but touch is working guys
Will upload it for testing purpose if you want :good:
Click to expand...
Click to collapse
You the man!!! You the man!!!
ChampionSwimmer has the fix for getting it to boot correctly. The one set up on the ray has dual recovery: hit the power key and you go into twrp, hit vol dwn and you get cwm.
Keep up mihahn, I want TWR so bad, that I can't sleep
Come on mihahn! You can do it!
Sent from Hubble Telescope
Okay guys I will upload it for testing and wait until Championswimmer can help me :good:
Okay guys go here if you want to see the progress or try it yourself
Related
These roms are flashable with xRecovery 0.1 (backup restore)
update 1
slightly updated AOSP rom to try :
AOSP 2.1 v.0.1
update 2
firmware load fixed, vibrate fixed, some other small fixes.
AOSP 2.1 v.0.2
Todo:
Voicecalls (GSM/3G)
Location services
Google checkin provider
Camera
reserved.............
only if we could mount sdcard and start adb logcat we could investigate further..
It was nice to roam around in 2.2
If we want to create working rom we should know which files from the original ROM are the drivers so we can take them and try to put them in the custom rom.Otherwise froyo will not be able to interact with our specific hardware.
you can ask some one more experians in custom roms so he could recognise the drivers
even if he don't have x8
remember: just ask for help , dont be rude and ask for custom rom
sorry for my bad english and for my interrubed
i am building a working one please wait. i have discovered the drivers and etc.
When it will be ready for test?
trapacska said:
i am building a working one please wait. i have discovered the drivers and etc.
Click to expand...
Click to collapse
nice info... i will waiting
hugerth said:
When it will be ready for test?
Click to expand...
Click to collapse
i started, i trying, i will share it as soon as i can! i would not like to share sh*t, because the working rom is better than a wrong one.
It's just about changing drivers? I would be too easy I think...
hugerth said:
It's just about changing drivers? I would be too easy I think...
Click to expand...
Click to collapse
no, there is some conf file and etc what i have to change.
trapacska said:
no, there is some conf file and etc what i have to change.
Click to expand...
Click to collapse
Share your finds..
One error which i am constantly getting is concerning gralloc any idea whats it about?
trapacska said:
i started, i trying, i will share it as soon as i can! i would not like to share sh*t, because the working rom is better than a wrong one.
Click to expand...
Click to collapse
I want to try this as soon as possible it will be great to have froyo run on my X8.
Thank you for your effort.
And Happy New Year !
trapacska said:
i started, i trying, i will share it as soon as i can! i would not like to share sh*t, because the working rom is better than a wrong one.
Click to expand...
Click to collapse
Best of Luck mate....
any progress? any good news for 2.2 froyo for our x8s??
any updates about the custom 2.2 froyo rom ?
now a little bit work, but just some minutes, and it says system is not responding and restart, but not full restart, just it get to the boot animation and then start.
the first step: i have to make it work, patches and drivers the second step. i tryed much thing to get working it, and i am sure i am not as far as i was.
I really hope that you will get this running because as it seams this will be the only way to get Froyo or Gingerbread on our X8.
Hope you will make this works. And if I can help with something let me know.
Hope this helps zdzihu released sources for his x10 froyo rom
Zdzihu x10 froyo source
trapacska said:
now a little bit work, but just some minutes, and it says system is not responding and restart, but not full restart, just it get to the boot animation and then start.
the first step: i have to make it work, patches and drivers the second step. i tryed much thing to get working it, and i am sure i am not as far as i was.
Click to expand...
Click to collapse
Maybe it's power managment, display, or some other driver problem? Or kernel?
Right guys THIS thread is for reporting bugs\issues and for solutions, PLEASE USE THIS THREAD and keep the DEV THREAD CLEAR. We need that thread clear for Deving uses. i will update this with every new release\hot\bugfix.
Please post logcats and please post your error like this:
Version of rom your running
DETAILED ERROR HERE (not just wifi doesnt work, explain on how it didnt work so we can reproduce)
Any mods your running and kernel version
Broken:
You Tell me
First issue encountered.
The zip file does not install, it aborts with a script failure in CWM. find recovery.log attached.
I'm gonna have a try at repackaging it and see if I can get it to install.
i *NEED* one or two people who are comfortable with adb\fastboot and able to flash a system.img for me
thanks
-Lloir
Give me a link and I'll do it...
Sent from my HTC Desire X using Tapatalk 2
NervGaz said:
Give me a link and I'll do it...
Sent from my HTC Desire X using Tapatalk 2
Click to expand...
Click to collapse
just uploading it, it's 200mb~ and i have crappy upload from sky so bare with me be up in about 30mins give or take
NervGaz said:
Give me a link and I'll do it...
Sent from my HTC Desire X using Tapatalk 2
Click to expand...
Click to collapse
yo dude did you get my PM??
Lloir said:
yo dude did you get my PM??
Click to expand...
Click to collapse
Only just saw it... replied in PM
Thread closed from the very same reason as the development one.
for those of you who want to help, flash the CM9 rom (i know it errors)
then go to advanced in clockwork mod and go to "report an error" select that and it will put a text file on the sdcard. i need this please
THIS IS SUPER IMPORTANT
thanks
Lloir said:
for those of you who want to help, flash the CM9 rom (i know it errors)
then go to advanced in clockwork mod and go to "report an error" select that and it will put a text file on the sdcard. i need this please
THIS IS SUPER IMPORTANT
thanks
Click to expand...
Click to collapse
Was in the process of cooking a my own lighter version of the stock rom and ended up without wifi and google play -newbie at work here - so I figured I'd just test this A01.zip while I'm at it.
I wiped all userdata, cache and dalvik, then installed A01.zip. All it says is "script aborted (no error message)E: Error in /sdcard/A01.zip (status 7)."
Recovery.log from cwm in my dropbox :
https://www.dropbox.com/s/nku5srjvhoixla9/recovery.log
cheers for the help man
infernal77 said:
Was in the process of cooking a my own lighter version of the stock rom and ended up without wifi and google play -newbie at work here - so I figured I'd just test this A01.zip while I'm at it.
I wiped all userdata, cache and dalvik, then installed A01.zip. All it says is "script aborted (no error message)E: Error in /sdcard/A01.zip (status 7)."
Recovery.log from cwm in my dropbox :
https://www.dropbox.com/s/nku5srjvhoixla9/recovery.log
cheers for the help man
Click to expand...
Click to collapse
much appreciated, im just looking through this and i see the problem. so *MIGHT* have a new build in the next few days
Lloir said:
much appreciated, im just looking through this and i see the problem. so *MIGHT* have a new build in the next few days
Click to expand...
Click to collapse
Lloir, you sent me a pm - couldn't reply because of your privacy settings - but sure, put it in dropbox and let me know
Hy all.
So is there any info that the rom booting or not? If everything right i will buy this phone at next week. Lloir, are you fully stopped the development for this phone? I hope i don't need to work with CM alone.
atis112 said:
Hy all.
So is there any info that the rom booting or not? If everything right i will buy this phone at next week. Lloir, are you fully stopped the development for this phone? I hope i don't need to work with CM alone.
Click to expand...
Click to collapse
Here's the situatino : LLoir helped us initially to get CWM 5 on the device (that still needs some work - I, maybe among others, donated so he'd help us back then) and then started work on a CM9. He stopped developing for the Desire X shortly after, for his own reasons. We were never able to install the first and only build he did through CWM (status 6/7) and when I did manage to install it, you couldn't take a logcat. At the moment there are only 2 people actively involved, Yasir, who has some experience in Android and me, but I'm not a developer at all and a total newbie to Android.
I did manage to build two test versions of CM9, one with the original device tree by Lloir and one with the MSM7k chipset, both of which gave the exact same result : no boot and no logcat possible.
Don't want to be negative, but that's the story, plain and simple. I'm more than a little disappointed with the situation the way it is and the lack of active interest from developers in the Desire X. But hey, its just a phone lol
infernal77 said:
Here's the situatino : LLoir helped us initially to get CWM 5 on the device (that still needs some work - I, maybe among others, donated so he'd help us back then) and then started work on a CM9. He stopped developing for the Desire X shortly after, for his own reasons. We were never able to install the first and only build he did through CWM (status 6/7) and when I did manage to install it, you couldn't take a logcat. At the moment there are only 2 people actively involved, Yasir, who has some experience in Android and me, but I'm not a developer at all and a total newbie to Android.
I did manage to build two test versions of CM9, one with the original device tree by Lloir and one with the MSM7k chipset, both of which gave the exact same result : no boot and no logcat possible.
Don't want to be negative, but that's the story, plain and simple. I'm more than a little disappointed with the situation the way it is and the lack of active interest from developers in the Desire X. But hey, its just a phone lol
Click to expand...
Click to collapse
Yes, i know that it's very very hard to develop without the device.
Htc is really new for me because i used sony every time. But sony don't support the developers so i won't buy it again. Now my xperia u is full bricked, but the service didn't repaired it and t-mobile give back my money so i can buy a new phone. It seems i will buy desire x. If i can buy it at next week, I start the work with cm soon, but maybe it will be long time because i need learn a lot about this device.
atis112 said:
Yes, i know that it's very very hard to develop without the device.
Htc is really new for me because i used sony every time. But sony don't support the developers so i won't buy it again. Now my xperia u is full bricked, but the service didn't repaired it and t-mobile give back my money so i can buy a new phone. It seems i will buy desire x. If i can buy it at next week, I start the work with cm soon, but maybe it will be long time because i need learn a lot about this device.
Click to expand...
Click to collapse
Take your time, just make sure to take a nandroid backup when you first get it in case your cid is different than the 1.14 and 1.18 RUU's that football posted Merry Christmas btw, enjoy the holidays !
atis112 said:
Yes, i know that it's very very hard to develop without the device.
Htc is really new for me because i used sony every time. But sony don't support the developers so i won't buy it again. Now my xperia u is full bricked, but the service didn't repaired it and t-mobile give back my money so i can buy a new phone. It seems i will buy desire x. If i can buy it at next week, I start the work with cm soon, but maybe it will be long time because i need learn a lot about this device.
Click to expand...
Click to collapse
Yay, we're getting a new developer on the forums!!!
I was working on a device tree (some patches have already been merged into Lloir's repository), and I noticed this article:
Windows For Devices said:
Qualcomm announced new chips that will let smartphone manufacturers upgrade existing designs to dual cores with no other hardware or software changes. The MSM8625 and MSM8225 run at up to 1GHz, include integrated 3G modems, and will work as drop-in replacements for the existing MSM7x27A and MSM7x25A devices, the company says.
Click to expand...
Click to collapse
It seems CM9 (link) only supports msm7x27 from the msm7k-series, but CM10 (link) supports msm7x27, msm7x30, msm8960, msm8660 and msm7x27a.
Maybe it's better if we try CM10 instead of CM9. Haven't tested it, though.
cobje said:
I was working on a device tree (some patches have already been merged into Lloir's repository), and I noticed this article:
It seems CM9 (link) only supports msm7x27 from the msm7k-series, but CM10 (link) supports msm7x27, msm7x30, msm8960, msm8660 and msm7x27a.
Maybe it's better if we try CM10 instead of CM9. Haven't tested it, though.
Click to expand...
Click to collapse
Thanks man, now that sheds a whole new light on our issues I was comparing the HTC Explorer (pico) to our device and vendor tree because it's the only HTC model based on MSM7xXXA that has an official CM9. Who wants another ice cream sandwich anyway ? I synced CM10 now, anyone wanna help build a new trees for JB ? Tips ?
Using Lloir's ICS config (on CM10), with BOARD_USES_QCOM_HARDWARE := true and TARGET_BOARD_PLATFORM := msm7x27a:
Terminal said:
frameworks/av/media/libstagefright/ExtendedWriter.cpp: In member function 'virtual android::status_t android::ExtendedWriter::addSource(const android::sp<android::MediaSource>&)':
frameworks/av/media/libstagefright/ExtendedWriter.cpp:86:19: error: 'AUDIO_FORMAT_QCELP' was not declared in this scope
frameworks/av/media/libstagefright/ExtendedWriter.cpp:88:19: error: 'AUDIO_FORMAT_EVRC' was not declared in this scope
frameworks/av/media/libstagefright/ExtendedWriter.cpp: In member function 'android::status_t android::ExtendedWriter::threadFunc()':
frameworks/av/media/libstagefright/ExtendedWriter.cpp:287:21: error: 'AUDIO_FORMAT_QCELP' was not declared in this scope
frameworks/av/media/libstagefright/ExtendedWriter.cpp:290:26: error: 'AUDIO_FORMAT_EVRC' was not declared in this scope
make: *** [/media/therbom/CM/cm-10.1/out/target/product/protou/obj/SHARED_LIBRARIES/libstagefright_intermediates/ExtendedWriter.o] Fout 1
make: *** Wachten op onvoltooide taken...
frameworks/av/media/libstagefright/TunnelPlayer.cpp: In member function 'virtual android::status_t android::TunnelPlayer::start(bool)':
frameworks/av/media/libstagefright/TunnelPlayer.cpp:322:58: error: 'AUDIO_OUTPUT_FLAG_TUNNEL' was not declared in this scope
frameworks/av/media/libstagefright/TunnelPlayer.cpp: In member function 'virtual void android::TunnelPlayer::resume()':
frameworks/av/media/libstagefright/TunnelPlayer.cpp:429:66: error: 'AUDIO_OUTPUT_FLAG_TUNNEL' was not declared in this scope
frameworks/av/media/libstagefright/TunnelPlayer.cpp: In member function 'int64_t android::TunnelPlayer::getTimeStamp(android::TunnelPlayer::A2DPState)':
frameworks/av/media/libstagefright/TunnelPlayer.cpp:713:21: error: 'class android::MediaPlayerBase::AudioSink' has no member named 'getTimeStamp'
make: *** [/media/therbom/CM/cm-10.1/out/target/product/protou/obj/SHARED_LIBRARIES/libstagefright_intermediates/TunnelPlayer.o] Fout 1
Click to expand...
Click to collapse
Starting on a new device config would be better.
Ramdisk Hijack - what is it?
- We are trying to load a custom ramdisk in order to be able to load a non-Sony based ROM on a locked bootloader using 2nd-init. This is a work in progress.
How can I help?
- My source code is here: https://github.com/keiranFTW/huashan_ramdisk-hijack also, you will find how to install this on there too.
You'll probably wonder why I'm trying to hack the stock ramdisk in - because my phone is my only device, I also need to use it as a phone. Once I can fix things this way I can move to using CyanogenMod Ramdisk.
Progress? CyanogenMod is currently booting on the phone but there are lots of non-working features.
This is not a ROM, do not install this unless you know what you are doing.
On completion I will give you this in form of an update.zip
#keiran
Any developers willing to help me out here?
I am busy with personal work, will check this out later... FYI you can't boot everything on same kernel... Specific kernel patches are required for some ROMs... Without those patches crucial rom features may not work...
Sent from my C6902 using xda app-developers app
DooMLoRD said:
I am busy with personal work, will check this out later... FYI you can't boot everything on same kernel... Specific kernel patches are required for some ROMs... Without those patches crucial rom features may not work...
Sent from my C6902 using xda app-developers app
Click to expand...
Click to collapse
I know this, and some of these kernel patches can be loaded as a module or even the ROM source code edited to suit the needs of the stock kernel.
Edit: I have had many people asking me if kexec could work, and the answer is no, probably not. Why? Because it requires a in-kernel patch as well as a module and so it is not possible to get it to work as we cannot flash a new kernel.
I have an idea and I'll start to merge changes soon
Sent from my C5303 using Tapatalk
I am not experienced in kernel dev but maybe i can contribute in limited extent.
Unluckily, i also got "NO" in bootloader unlockable and very dissappointed to see that.
I hope someone will be able to find an alternative.
Have you looked at this?
http://www.xda-developers.com/android/locked-bootloader-xperia-s-and-want-cm10-no-problem/
Work in peace...
OP
can you link me to some good references about chroot? I got the basic understanding, want to try it on linux on my laptop.
Closest analogy i can draw is the linux live cd, which runs the OS live without installation. If thats the case, and if we succeed in this process, we could use some partition to dump cm and run it from there.
But lets not get too far, im still in infancy stage.
Regards
Yasir
finally Got the basics of what you are doing... You are essentially doing the same thing letama atis112 and company did to run cm10 usng stock kernel, but hijacked stock ramdisk to run cm ramdisk.... Seems a good idea but will only work for CM10 (4.1 based) and later when locked bootloader gets 4.3, we could get cm10.2 as well. If you are doing the same thing they did, then hopefully it will work soon. If its something different, then wish u luck, ill keep tracking ur progress.
Yes, he is trying to have it done the same way as letama, atis and others with one minor difference - we don't have pre_hwconfig.sh, so he's trying with chargemon. Older ramdisk Keiran's github worked fine, but after some commits he made it doesn't boot. When I try with older ramdisk and newest step2.sh, everything except sdcard works fine. I have an idea - what if we kill every process with every possible way(killall5, pkill,etc) and then start it manually, by calling them from /system/bin? Maybe it's the way.
Some offtop here:
Maybe the kernel from leak works on locked BL's? If DooM haven't changed anything in it - it's very possible. Maybe someone with 4.3 leak on their phone would try locking the bootloader?(Of course only if that person knows how to unbrick, if something goes wrong).
MrSteve555 said:
Yes, he is trying to have it done the same way as letama, atis and others with one minor difference - we don't have pre_hwconfig.sh, so he's trying with chargemon. Older ramdisk Keiran's github worked fine, but after some commits he made it doesn't boot. When I try with older ramdisk and newest step2.sh, everything except sdcard works fine. I have an idea - what if we kill every process with every possible way(killall5, pkill,etc) and then start it manually, by calling them from /system/bin? Maybe it's the way.
Some offtop here:
Maybe the kernel from leak works on locked BL's? If DooM haven't changed anything in it - it's very possible. Maybe someone with 4.3 leak on their phone would try locking the bootloader?(Of course only if that person knows how to unbrick, if something goes wrong).
Click to expand...
Click to collapse
I assume you have the same issue of unlockable BL? anyways, i am waiting for 4.3 so that after playing with, we can try and run cm10.2 at least... + miui
I've redone your work, and i can succesfully hijack ramdisk...
I've CM booted up, but:
1. graphical glithes (i know the solution)
2. no baseband
3. no sdcard (inner, external)
But it's improvement
Source: https://github.com/dh-harald/hijack-ramdisk-huashan
dh.harald said:
I've redone your work, and i can succesfully hijack ramdisk...
I've CM booted up, but:
1. graphical glithes (i know the solution)
2. no baseband
3. no sdcard (inner, external)
But it's improvement
Source: https://github.com/dh-harald/hijack-ramdisk-huashan
Click to expand...
Click to collapse
If my girlfriend would let me and I was near you I would kiss you right now :*
Jokes aside, I think I might be able to fix SD card and the rest
Sent from my C5303 using Tapatalk
I dont think any processes with late_start class are working... This would explain SD and also network.
Try:
/system/bin/sdcard /data/media /mnt/shell/emulated 1023 1023
/system/bin/qseecomd
/system/bin/secchand
Anything really..
When I was hijacking ramdisk before but loading the stock ramdisk just for testing I also lost network as well as sdcard, and I'm sure that I lost WiFi too. A possible solution would be *not* to stop these services maybe?
Sent from my C5303 using Tapatalk
New source code is at: https://github.com/keiranFTW/huashan_ramdisk-hijack
- Updated to work with Android 4.3
- Using 2nd-init instead of chroot
- Recovery included (not sure if working)
#keiran
hijack
Hy
I modified the hijack source and recompiled the cm10.2 was.
hijack
dev tree
vendor blobs
I made a new thread on xda.
bagyusz said:
Hy
I modified the hijack source and recompiled the cm10.2 was.
hijack
dev tree
vendor blobs
I made a new thread on xda.
Click to expand...
Click to collapse
Hey,
Thanks, your changes have helped a lot, so I have expanded on them to make it possible to integrate into AOSP more easily. I also use /system/bin/chargemon instead of system/bin/wipedata, it is earlier in boot process.
I also might want to note that you are not killing all processes, you need awk {'print $2'} instead of awk {'print $2'}
But yeah, great work.. you did what many others couldnt.
My repositories:
dev tree
vendor blobs
hijack
Feel free to add pull requests, and i can add you to the repository if you like.
Keiran
If only this could be done in other devices, as I also have a locked Xperia, but it's a Live Walkman. Unfortunately it also has the Unlock Bootloader: "NO", so if could also be ported to other devices it would be great. Not forcing or pushing you, but trying something more updated than 4.0.4 would be great
is this...?
@KeiranFTW & @bagyusz
sick work guys way to not never give up and accomplish what was thought to not be possible goes without saying one of the best development breakthroughs this year!
hey, in either of your opinions would this in some way be portable to our locked as **** bls on S4 Verizon and AT&T? We havent had ASOP capabilities or 4.4 for that matter yet and everyone is stuck on safestrap 4.3 stock kernels. Any help on this would be much appreciated. Its either trying to port this method or trying that new AnyKernel2.0 today not trying to hard brick heh
msm7x27
KeiranFTW said:
.
Click to expand...
Click to collapse
would this method work on any msm7x27 after pointing partitions ?? @KeiranFTW
deleted.
I still don't know what you're talking about. eace
Sent from my C5303 using Tapatalk
concerning hijack
KeiranFTW,
i am sorry to bother you with what may or may not be a 4 square dev question(s).
can i attempt something similar without building custom kernel? ( i read evrything i can but, lack funds for proper hardware so am limited.)
can i alter the insmod-ing of kernel modules to come as close to the beginning of the boot process as possible and have hardware functional in spite of slaying zygote/android userspace ?
this thread http://forum.xda-developers.com/showthread.php?t=1937328 outlines a means to
mount?load? a loop device from init.rc
my thought is as i have a gt-p5210 x86 device it might be possible to fire up (no matter how ugly)
a livecd or straight forward ext4 linux.img.
I would be interested in any insight/ideas you may have toward that end.
thank you for your time.
m
Hi,
Just wondering if/when MadCatz will release the kernel?
I know linux being GPL, it has to be shared, but not sure about Nvidia's sources?
I'm new to android but not java(my day job) and linux.
I've compiled and installed my own kernels on desktop and on my mobile phone (Nokia N900).
I want to try and add a few things.. ie filesystem/DVB/webcam support etc.
Following this how to.
Apologies for the delay in getting this released. Here's the kernel source:
ftp://86.54.116.234/pub/software/mojo/firmware/mojo-jb-kernel.tar.gz
Mad Catz Rich said:
Apologies for the delay in getting this released. Here's the kernel source:
ftp://86.54.116.234/pub/software/mojo/firmware/mojo-jb-kernel.tar.gz
Click to expand...
Click to collapse
Sweet! many thanks :victory:
:highfive:
:good:
omg.... does this mean we can finally have a cifs module!? AWESOME!
So now that the kernel source is avialable, I'm looking forward to the first custom kernels. Would be great to have some kernel optimizations and other tweaks built in :good:
RollingRoman said:
So now that the kernel source is avialable, I'm looking forward to the first custom kernels. Would be great to have some kernel optimizations and other tweaks built in :good:
Click to expand...
Click to collapse
Yes i hope someone can make a kernel to re-apply resolution settings on the m.o.j.o, as mad catz said to me via a phone call some tv's can't adjust to 1080p natively because the os is preventing it,and stupidly they removed the resolution changing slider in settings don't ask me why they did that?
If there is a way to set resolution without endangering the console booting up afterwards would be awesome,i am thinking it is there but hidden away and accessable some way but don't know how,developer options can be opened but not resolution settings as far as i have found any way.
PHYSC-1 said:
Yes i hope someone can make a kernel to re-apply resolution settings on the m.o.j.o, as mad catz said to me via a phone call some tv's can't adjust to 1080p natively because the os is preventing it,and stupidly they removed the resolution changing slider in settings don't ask me why they did that?
If there is a way to set resolution without endangering the console booting up afterwards would be awesome,i am thinking it is there but hidden away and accessable some way but don't know how,developer options can be opened but not resolution settings as far as i have found any way.
Click to expand...
Click to collapse
I think it automatically sets the resolution based on the TV/monitor, try a different one?
TMK, the slider has nothing to do with the kernel.
gwaldo said:
I think it automatically sets the resolution based on the TV/monitor, try a different one?
TMK, the slider has nothing to do with the kernel.
Click to expand...
Click to collapse
I would do that but i only have a panasonic 50" plasma it's a 600hz 1080p it p50x50b model,there are 2 variants of it a hd ready and a 1080p model,i know it's the 1080p model as i used blu ray and xbox 360 and a wiiu etc in 1080p modes so it's definately not 720p only on my model.
I still think it is possible to reinstate that hdmi resolution slider though? I would love for someone to find a fix for that to bring back the slider though.
It also has nothing to do with the overscan as that's off,and the guy said it's an argument between the console's os and the tv,but maybe if i had an option to change resolution within the console when in operation it would ammend this,resolution changer pro works then looses usability eventually and it's awkward and time consuming to get that to work,only for it to stop after a time?
There is no forced hdmi resolution setting in the tv menu unless of course there is in engineer mode but all that seems to do when entered is show test and it's results coming up as ok,after testing it factory resets the tv as well so sick of trying that now.
Someone needs to get a custom rom made up with kitkat and 1080p natively set.
Mad Catz Rich said:
Apologies for the delay in getting this released. Here's the kernel source:
ftp://86.54.116.234/pub/software/mojo/firmware/mojo-jb-kernel.tar.gz
Click to expand...
Click to collapse
Unable to untar the tar.gz file. It says "tar: kernel/drivers/net/wireless/bcm43341/src/include/proto/p2p.h: Cannot open: Not a directory" and there are many lines like this. Tried everything from sudo, sudo -s, chmod, chown....
Also it says cannot mkdir: is not a directory
Its a .h and .c files ofcourse they aren't directories! Its not letting me execute make without errors since my source is like crap crawling with this "NOT A DIRECTORY"
Nothing is working. Command used was tar xvfz mojo-jb-kernel.tar.gz with many combinations and OS is Ubuntu 12.04 LTS 64 bit...
Mad Catz Rich said:
Apologies for the delay in getting this released. Here's the kernel source:
ftp://86.54.116.234/pub/software/mojo/firmware/mojo-jb-kernel.tar.gz
Click to expand...
Click to collapse
Can you help me. Is there any other place from where I can get source?
Thanks in advance..
Kingshoo said:
Can you help me. Is there any other place from where I can get source?
Thanks in advance..
Click to expand...
Click to collapse
Hey,
I suggest downloading with wget or a good download/ftp application if it's timeout on you.
It's not corrupted, it worked for me and the date stamp is still the same.
gwaldo said:
Hey,
I suggest downloading with wget or a good download/ftp application if it's timeout on you.
It's not corrupted, it worked for me and the date stamp is still the same.
Click to expand...
Click to collapse
It doesn't time out but it says some .c and .h cannot open: Not a directory when I use tar to extract it. Then I thought that I should install something else to extract and tried ARC. It extracted and then the same message box as appeared in windows 7 OS "file already exists cancel or overwrite"
I then said overwrite and then I get the extracted package. I just want to ask you that when you extracted it did you got any errors? What procedure you used to extract it? I downloaded twice with same results...
gwaldo said:
Hey,
I suggest downloading with wget or a good download/ftp application if it's timeout on you.
It's not corrupted, it worked for me and the date stamp is still the same.
Click to expand...
Click to collapse
OK as per your suggestion I used wget c and the address. That gave me again the same file and upon extracting it I am getting same errors.
May be that the file isn't corrupted as you can extract it and its possible that I am doing something wrong in extraction..
I tried to create the kernel from sources and got a make error, to remove that I must delete a line in the make file (Line no 603) and after that I can successfully compile the zimage. But the issue is that after completing the procedure for boot.img file the original and compiled one has a difference of 0.1 MB and device don't boot with the newly compiled boot.img
Please if you can provide me with the steps on how you exctracted it and which OS you are using?then it will be really helpful. Also can you please upload the makefile of kernel and config.gz file you are using to make the kernel...
One useful information that can prove that there is an issue in extraction:
Extracted content on windows OS with Administrator priviledges: 42889 items , 487.8 MB
Extracted content on Ubuntu with Tar and other utilities: 42692 items, 482.5 MB
gwaldo said:
Hey,
I suggest downloading with wget or a good download/ftp application if it's timeout on you.
It's not corrupted, it worked for me and the date stamp is still the same.
Click to expand...
Click to collapse
Seems like you are the only person who can help me as no one else seems to be active on MOJO development department. Sorry to disturb you again friend but you know I tried extracting on Android too and it failed there too!
I am completely exhaused with two days 24hrs of searching only extraction process. Please let me know if you successfully compiled and booted the kernel on your MOJO. If yes then I need more information from you as I had compiled the kernel but as I told you earlier it didn't worked... Please reply ASAP
Kingshoo said:
Seems like you are the only person who can help me as no one else seems to be active on MOJO development department. Sorry to disturb you again friend but you know I tried extracting on Android too and it failed there too!
I am completely exhaused with two days 24hrs of searching only extraction process. Please let me know if you successfully compiled and booted the kernel on your MOJO. If yes then I need more information from you as I had compiled the kernel but as I told you earlier it didn't worked... Please reply ASAP
Click to expand...
Click to collapse
Hi,
I'm in Aust. so there's a time difference.
I'm also about to leave on a 4week holiday and don't have my mojo dev stuff on my laptop.
I just used tar -vxzf filename
I think the only errors were a bad lsymbolic links which arent required.. from memory I could be wrong.
If you read the other threads here, I and someone else explain how we got the kernel compiled and yes it works fine.
http://forum.xda-developers.com/showthread.php?t=2691985&page=2
You dont use their makefile you recreate it .
If this is your first linux kernel or even android kernel, it's a tricky process and it takes time research all the steps.
Good luck
gwaldo said:
Hi,
I'm in Aust. so there's a time difference.
I'm also about to leave on a 4week holiday and don't have my mojo dev stuff on my laptop.
I just used tar -vxzf filename
I think the only errors were a bad lsymbolic links which arent required.. from memory I could be wrong.
If you read the other threads here, I and someone else explain how we got the kernel compiled and yes it works fine.
http://forum.xda-developers.com/showthread.php?t=2691985&page=2
You dont use their makefile you recreate it .
If this is your first linux kernel or even android kernel, it's a tricky process and it takes time research all the steps.
Good luck
Click to expand...
Click to collapse
I have gone through with the links you provided already and I understand every bit of conversation. Yes I am new to kernel compiling but its reasonably understandable.
I respect your valuable answer no matter when you reply since you have a minute for me and don't worry about TimeZone differences as I am not in a great hurry, I just don't wish to waste time on errors for which I ain't responsible
OK I tried compiling modules for which I had to compile the kernel to get the module.symvar file and "THE MODULES WORK!" that too with the Default kernel Makefile and ofcourse my own module Makefile.
"You dont use their makefile you recreate it" this line you wrote.. What do you mean by that??
I mean were you talking about the kernel Makefile or our own module Makefile, Please clear me here? As far as I know the Kernel Makefile should be the same when only compiling the stock kernel as that is my purpose "JUST TO COMPILE THE STOCK KERNEL"...
My compiled kernel boots but just shows a black screen! I don't want to spoil your holidays sincerely but if some help I can get from you then I will be able to relieve me from this burden
Hmm got it compiled finally even after that make issue with -k flag to make
Also all I needed was ramdisk from latest OTA and not the one from the kernel. That was the issue with kernel booting but it freezing at blank screen...
RESOLVED :highfive:
Kingshoo said:
Hmm got it compiled finally even after that make issue with -k flag to make
Also all I needed was ramdisk from latest OTA and not the one from the kernel. That was the issue with kernel booting but it freezing at blank screen...
RESOLVED :highfive:
Click to expand...
Click to collapse
Glad you got it working.
Re the makefile, I think you have to run config first to check your systems compilers/linkers/etc which then creates the makefile.
:highfive:
Mad Catz Rich said:
Apologies for the delay in getting this released. Here's the kernel source:
ftp://86.54.116.234/pub/software/mojo/firmware/mojo-jb-kernel.tar.gz
Click to expand...
Click to collapse
is there any reason this is done via some random ftp server and not some place like github/bitbucket with better management? or heck even sourceforge would be an improvement.
is that account for developer outreach? are there any datasheets on the components used in the device? sony does a beta program for updates on their flagship devices have you considered doing something similar where people can grab images and help test updates? ever think about tossing the device trees up for aosp to help encourage a porting of 3rd party roms and spread the community?
the nook color and touchpad being hack and having Cyanogenmod and the like being ported to it drove sales up, i would imagine having a hackable android console that isnt some no name chinese brand would probably do decent. unfortunately now with android tv you guys have some serious competition on the horizon, its a matter of how you go from here and try to make the most of it so everyone already has your product and doesnt need another.
edit: i also see there is several updates yet only one kernel source... any chance of updated source?
@Mad Catz Rich
The new update (205-TS) has a new kernel build of May 2nd.
Any chance that can be put on the server?
from http://madcatz.com/mojo/en-ca/
Ready to Root
As any Android power-user knows, the best way to get the most out of your device is to root it. Root access opens up all sorts of options including adding custom keymapping capabilities and installing custom ROMs. Mad Catz provides a short step-by-step guide to rooting, and our tech support team is ready to help.
The best part – rooting won’t void your warranty.
Click to expand...
Click to collapse
Please help, tech support team!
We need custom ROMs!
make kernelversion
3.4.35
e-mTz303 Presents ClearLimit ROM Based On JellyBean Cyanogen10.0 @kaleemmks Here Try This and HIT THANKS TOO
Features of ROM.
[*]CHANGELOG v3.1.4
Added Aroma Installer (Gives You Optional Apps To Install)
Added "data/app" Support
Fixed "symlink" Errors!
Fully Rooted (previous ROM = Errors For Root!)
Added Wireless Tethering Support!
Nano Text Editor And Bash Added!
Custom Bootanimation
[*]LOG FOR v3.0.3
JellyBean 4.1.2
Clean Cyanogen ROM
Added Cyanogen10 Custom Theme
Better Battery Life
Rooted
GApps NOT Included (Need To Be Flashed After Flashing ROM)
Find Out Yourself Or Wait Until Next Update
List Of Working And Non-Working
Working:
- GSM
- Data
- SMS
- Wi-Fi
- Bluetooth
- GPS
- Audio
- Video
- Torch
- Root
- Orientation
- USB Mass storage
- Touchscreen
- 720p Video Playback
- Wi-Fi Tethering
- And More That You'll Find Out!
Not Working:
The Brightness Bar on Status Bar. Also MTP & PTP Wont Work, Confirm Others Please.
Other Than That Everything Works Perfectly!
---------------------------------------------------------------------------------------
Regards, e-mTz303, HIT THANKS EVEN IF YOU HATE ME FOR BRICKING YOUR PHONE ( cause you Got A New Phone )
Download!
ÍThe Download For The ROM
DOWNLOAD LINK (v.3.1.4)
http://www.4shared.com/rar/FOlQXguyba/CM_CL_ruby-25_May_2015.html?
-------------------------------------------------------------------------------------------------------------------
OLD LINK (v3.0.3) :-
http://www.4shared.com/rar/DVgOfqvTba/ROM412ClearLimit_ROM_v303_CL_C.html
.
ScreenShot In Attachments!
---------------------------------------------------------------------------------------------------------------------------
Regards, e-mTz303, HIT THANKS EVEN IF YOU HATE ME FOR BRICKING YOUR PHONE ( cause you Got A New Phone )
Installation Tutorial
The Tutorial For Installing MY ROM!
- Make sure you're on the latest TWRP/CWM.
- Download My .RAR File! (DONOT PLACE IT ON THE STORAGE YET )
- Extract The Files Into External SD Card Now. ( It Will Unzip Two .ZIP Files )
- Boot Into Recovery Now
- No Need To Reset, Aroma Installer Will Do It For You, SO -»»
- Flash *NAME OF THE ROM* Now, Then
- Flash The GApps Present With The *ROM* In the External SD Card!
- Reboot And Viola You Are Running My Clean Cyanogen ROM, Tweaked With "dsixda kitchen"!
- Then Hit Thanks!
Credits
- Thanks To CyanogenMOD Developers!
- Thanks To dsixda's kitchen!
- Thanks To XDA For This Awesome Forum!
- Thanks To Jorge A. For Boot Animation!
---------------------------------------------------------------------------------------
Regards, e-mTz303, HIT THANKS EVEN IF YOU HATE ME FOR BRICKING YOUR PHONE ( cause you Got A New Phone )
i am gonna download and wiil share my experience
Be Safe!
kaleemmks said:
i am gonna download and wiil share my experience
Click to expand...
Click to collapse
I Fixed The Errors NOW! I am Gonna Upload The New ROM Files Soon Use That @kaleemmks
thanks coz i also failed to flash it in my phone
status 1 error
ok i m waiting for new rom
kaleemmks said:
thanks coz i also failed to flash it in my phone
status 1 error
ok i m waiting for new rom
Click to expand...
Click to collapse
The Old Download Link Gives Me An Status 6 Error But The New One Is Working Fine, The Link Is Right There In The "Download Post", Its Hidden.
Download It, It is a 500MB Plus Download. And Follow The Instructions Given To Install, It Works, just factory reset phone and then Flash, it will do the wiping! (Y) GOOD LUCK!
anyone cm12?
No Unfortunately No!
Alimataei said:
anyone cm12?
Click to expand...
Click to collapse
It Can't Happen. Google Converted Something To ART. And As Far as i Think The "HTC Amaze 4G" Does Not Support That
But Feel Like Thanking Me! and Try My ROM Hope i Bring CM11 To The Amaze1
Thanks e-mtz, downloading the ROM, will share my experience time to time.
e-mtz said:
It Can't Happen. Google Converted Something To ART. And As Far as i Think The "HTC Amaze 4G" Does Not Support That
But Feel Like Thanking Me! and Try My ROM Hope i Bring CM11 To The Amaze1
Click to expand...
Click to collapse
There is an option in cm11 developer options that u can switch between ART and DALVIK
Nice...wow
So far working like a charm, No major or minor fault detected till now, everything working flaw less, Got some more screenshots to share. :fingers-crossed:
Thankyou
Librastar said:
So far working like a charm, No major or minor fault detected till now, everything working flaw less, Got some more screenshots to share. :fingers-crossed:
Click to expand...
Click to collapse
:good: Its Good To See Someone Appreciating Me, Thankyou for your involvement
Instead of you Thanking Me, I Should Thank YOU!
Yes, There Is
Alimataei said:
There is an option in cm11 developer options that u can switch between ART and DALVIK
Click to expand...
Click to collapse
Yes I Saw It, But to be Noted CM11 Is Not Here For HTC Amaze YET, While In PAC-MAN The Option is there too, In All KitKat It's Present I Guess! In Developer Options, "SWITCHING FROM DELVIK TO ART"
i really don`t know what to say i thought that this device is dead and no one care about it any more but you give hope that there is something coming thank you so much for your work
Thankyou, But Note ***
basiouny said:
i really don`t know what to say i thought that this device is dead and no one care about it any more but you give hope that there is something coming thank you so much for your work
Click to expand...
Click to collapse
No Problem :good: But There Are Others Who Care About This Device too, We Can See Team Venom, and Other Teams Working For The Amaze, But The Only Problem is that The Official ROM Creators that want their name & fame don't want to work on This Device Anymore. We Can Take Example of CyanogenMod! Although They Released JB On the Amaze, they left Amaze On JB only. No KitKat Support While Other New Phones are Getting It. Also AOKP Doesn't Give **** About Amaze. Some Guys Ported It To Amaze But it turned to a "DEAD LINK". The Only AOKP I can Find is By Subham, The Xperia AOKP That Subham Gives Us . But PAC-MAN Are Releasing KitKat For Us Thats A Relief.THE QUESTION AGAIN? OUR RECOVERIES ARE NOT ALSO BEING DEVELOPED
Hello, does this ROM support HDMI out?
Sent from my Z970 using XDA Free mobile app
Hmm, Why Don't you Try It?
Moon83 said:
Hello, does this ROM support HDMI out?
Sent from my Z970 using XDA Free mobile app
Click to expand...
Click to collapse
HDMI Out? Does HTC Amaze Support That? I Think you Would Need Software's To Do That. But Make A Recovery of your Current ROM, and Then Try This ROM. If it doesn't Support HDMI Out, Recover It To your old ROM, and do notify us that if it works or not.
e-mtz said:
No Problem :good: But There Are Others Who Care About This Device too, We Can See Team Venom, and Other Teams Working For The Amaze, But The Only Problem is that The Official ROM Creators that want their name & fame don't want to work on This Device Anymore. We Can Take Example of CyanogenMod! Although They Released JB On the Amaze, they left Amaze On JB only. No KitKat Support While Other New Phones are Getting It. Also AOKP Doesn't Give **** About Amaze. Some Guys Ported It To Amaze But it turned to a "DEAD LINK". The Only AOKP I can Find is By Subham, The Xperia AOKP That Subham Gives Us . But PAC-MAN Are Releasing KitKat For Us Thats A Relief.THE QUESTION AGAIN? OUR RECOVERIES ARE NOT ALSO BEING DEVELOPED
Click to expand...
Click to collapse
Well, there are several things I would like to clarify, ruby is a MSM8660 device, I mean by this ?
many drivers do not work well, because HTC does not support these devices in favor of the MSM8960,
even you can see that CAF does not support MSM8660,
now there are many Samsung devices that are MSM8660 and they are supported ?, how this is possible?
because they were able to migrate to the kernel-3.4 without complications, since Samsung used as a basis MSM8660, to jump at MSM8960, something that HTC didn't. :crying:
there are several devices MSM8660 HTC with kernel-3.4, and it is thanks to the work of expert and passionate people, like sultanxda,
and even I tried base myself on their work to port it to Ruby, but it's a long process, also I don't want make brick the phone from my brother.
I see that you mention that cyanogenmod, only gave support to JB, we developers have a life outside xda and code. Many do this out of love and passion!
answering your question the recovery menu: of course, you can see my basketbuild! https://basketbuild.com/devs/JoseGalRe/ruby/recovery
note: no need to do the red and giant letter, if you put it in bold is perfect!
Greetings!
Greetings, & Thankyou
josegalre said:
Well, there are several things I would like to clarify, ruby is a MSM8660 device, I mean by this ?
many drivers do not work well, because HTC does not support these devices in favor of the MSM8960,
even you can see that CAF does not support MSM8660,
now there are many Samsung devices that are MSM8660 and they are supported ?, how this is possible?
because they were able to migrate to the kernel-3.4 without complications, since Samsung used as a basis MSM8660, to jump at MSM8960, something that HTC didn't. :crying:
there are several devices MSM8660 HTC with kernel-3.4, and it is thanks to the work of expert and passionate people, like sultanxda,
and even I tried base myself on their work to port it to Ruby, but it's a long process, also I don't want make brick the phone from my brother.
I see that you mention that cyanogenmod, only gave support to JB, we developers have a life outside xda and code. Many do this out of love and passion!
answering your question the recovery menu: of course, you can see my basketbuild! https://basketbuild.com/devs/JoseGalRe/ruby/recovery
note: no need to do the red and giant letter, if you put it in bold is perfect!
Greetings!
Click to expand...
Click to collapse
HAHA. Ok I get it, so can your Recoveries support GApps 4.4.x? If that's the case i am ready to give it a shot.
And Ye Bold is Perfect, i Found the Red, Giant A little annoying myself
EDIT :- I Did Try your 4EXT Recovery. But I removed It After I got TWRP because your 4EXT Failed To Flash GApps 4.4.x please Guide Me in downloading the Recovery That Supports GApps 4.4.x
Oh and Yea Isn't the "Amaze" a "MSM8260" Device?