Related
Unfortunatelly I don't have permissions to reply in this topic, so I created this one.
I have Installed CM7.2 (from Quarx) on stable recovery and ICS to latest recovery. I use multiboot for this.
Everything worked good, but one of the newest version of ICS has newer kernel, so after I choose it phone just stucks at Moto logo...
So I have 2 questions:
1) Is it possible to get working new ICS on multiboot?
2) If no, how can I delete ICS from latest recovery and install there other firmware?
Thanks
AstorDev said:
Unfortunatelly I don't have permissions to reply in this topic, so I created this one.
I have Installed CM7.2 (from Quarx) on stable recovery and ICS to latest recovery. I use multiboot for this.
Everything worked good, but one of the newest version of ICS has newer kernel, so after I choose it phone just stucks at Moto logo...
So I have 2 questions:
1) Is it possible to get working new ICS on multiboot?
2) If no, how can I delete ICS from latest recovery and install there other firmware?
Thanks
Click to expand...
Click to collapse
Nope its not possible to have the newer versions including 111207 on multiboot!
to get rid of ICS in the latest boot you can just flash an other .zip over it, like miui or stuff...
hope it helped, greetz Esok
It is possible
Yes, it is possible. The only vital pre-requisite is to upgrade the main CM7 system to 2.3.4 kernel version.
But before, take care of:
1. The 2.3.4 kernel has some issue regarding camera, specially green lens (I think it doesn't work yet). Red lens work great, after a few work around with some overlay libs. (all this stuff very well described on CM7 thread).
2. Once you upgrade the kernel, you could install CM9 latest test builds.
pros:
- both systems running latest GB kernel (remember be sure to use 2.3.4)
- great to have CM7 and CM9.
cons:
- be sure to fix your camera in CM7. (of course, hope you have red lens )
- in my case: CM9 boot, but it doesn't detect the baseband (if I check "About phone" Baseband details show "Unknown"). WiFi work Ok.
I really appreciate any advice in this last comment.
Happy holidays
Good Evening Dudes
I'm just introduced on this section and it's first time than i ve had a stuff like this awesome samsung
Smooth Fast Strong And God ! it's the beautifull customisable stock rom (it's really beautifull to compare with htc stock rom)
well the question is not here and the target also
i've never had the oppotunitities to try a CM 10.1 on any device Htc desire x hasnt official CM and not possible to port CM10.1 cauz Htc doesnt provide the kernel source.... damn
(it's was juste for put in situation)
What's the real interest -Gain can i expect with the CM10.1 on the Galaxy S4 ?
Whith this rom it's sound interesting to put a custom kernel also.
what can we do with cm 10.1 than we cannot with a stock rom ?
Yeah a know , i can make a backup on my stock rom , flash the cm 10.1 try and if doesnt like it restore to the backuped stock.
Thanks for your time
If you had any other suggestion better than the CM 10.1 (i know it s on nightlies sound like equal as alpha but
topic is open :s
Well the Stock ROM is pretty much as bloated as a whale. CM is only 200MB in size, so first of all it will save space on your internal memory. Second of all, you won't have a lot of processes running in the background like you do now, your phone will be a LOT more responsive. Ofcourse, as with any custom ROM, there will be some bugs and those ROMs will need testing and updates (that's why nightlies exist). But eventually there will be stable versions and imo, it'll beat the stock any day. On the other hand, the stock ROM has some functions like the IR blaster, the smart-pause, smart-scroll and hover function, etc. If you're a big fan of those things, stick with your Stock ROM. But if you would like to a clean, simple, bloat free and faster experience than you have now, a custom ROM is a great way to achieve it. But that's not the only thing ofcourse, CM also has some extra functions and customization options you won't find in your stock ROM, you can tweak your system quite a lot and there are some things I couldn't live without (for example swapping your menu key for your recent apps switcher, and putting the menu function on the long press ).
Thanks a lot
Sound really interesting
CM 10.1 it's more in touch with i'm looking for
The actual build of CM 10.1 can be used on a basic day usage ? or it's better to wait a few days ?
If i flash the cm now ? need also to flash another kernel or just flash the zip by philw touch recovery ?
can i come back to my stock backuped rom after if i want ? with the restore function of philz touch recovery ?
I'm using Philz Recovery too and yes you can flash CM10.1 from there (I have the latest build from June 12th on it). Before you flash, make your sure you wipe/factory reset your phone in Philz Recovery. You might also need to flash the CM10.1 rom 2 or 3 times (the second time it usually works), on the first try it always gives a Status 7 error (don't worry). Look at the thread for the Offical CM10.1 Nightlies, there's a lot information there!
It's working pretty good for me, I haven't found any major bugs so far. Just make sure you make a Nandroid backup in Philz Recovery first (and store it your external SD card for safety and to save space ofcourse ). You can always return to that backup through the restore function in Philz Recovery yes.
Also, if you update your CM10.1 with a new nightly build (for example next week, or next month), do it manually and flash it in the recovery each time. Updating it from the Settings->About->Cyanogenmod Updates menu bricked my phone today, so I guess there is still a bug there. Besides that, there are no issues what so ever according to me.
PS: You're from Liege? I'm from Genk
last question before the first try
With the original Cm we need to flash gapps separately or it's inside the rom ?
If external suppose to take the last release on goo
If I remember correctly you need to flash it separately
Sent from my GT-I9505 using xda app-developers app
Try This one -> http://forum.xda-developers.com/showthread.php?t=2296266
Yeah after flash the rom 4 times finally she install correctly ( 3 times error7 but no affraid)
Ui is clear, phone running smooth and very well no issue with wifi or 3g
The first bug i ve seen was about the carrier name -- the carrier name is showed like an id on a database (think the code for showed the cells with carrier name is not correct)
For the rest no speciq issue detected
Thanks a lot for your help
PS : i ve also find a answer to one of my question
when use cm you must flsah the gapps separately and link is coming on cyanogen page.
I ve read also than the build for the S4 T-mobile seems to work fine on this phone more bugs corrected on it ?
No trying BT for the moment cauz i dont had BT device
@disturbed : i ll try the rom linked this evening . Thanks a lot
Hello,
Tried many custom roms but usually end up coming back to the offical AOKP rom for the N4. I like the options and speed of the rom, find it very stable and use the theme engine. I haven't tried their 4.3 roms as they are all nightlies and I am always led to believe these are a bit risky for using as a daily driver. I use my phone for work and important things.
I have stayed with 4.2, but the only issue I have found is that the camera flash does not work. I have tried the latest stable 4.2 release, but then under instruction by aokp him/herself flashed the last 4.2 nightly as I was told there was a camera fix for that release. This was a clean install, I wiped and flashed.
Unfortunately I still cannot get the camera flash to work. I know my phone is not faulty as the flash works fine in Beanstalk, CM and other roms.
Anyone else experienced this?
The nightly releases for AOKP 4.3.1 are stable. Just make s nandroid backup and install them.
sent via tapatalk
ThemeManager crash with Franco/Hells kernel
Hi,
Did anyone had issue with ThemeManager. It's crashing always while restarting phone. I tried Franco/Hells kernel and it happens on both. It's working correctly on standard kernel. I tried to set up stock theme/clean data in application. Nothing helps.
For anyone who doesn't know; MoKee Nightlies are available for Thea, if anyone wants to try. It's pretty good.
http://download.mokeedev.com/?device=thea
Their original dev (and unkwon) must create a post for more detailed information...! But thanks for the advice.
Obviously. They haven't yet! Just telling people it's there.
It's pretty good, but at the moment Bluetooth is not working, can't connect to my Android Wear, so back to CM12 but I'll keep trying =)
hugoprh said:
It's pretty good, but at the moment Bluetooth is not working, can't connect to my Android Wear, so back to CM12 but I'll keep trying =)
Click to expand...
Click to collapse
Were you using a nightly or release build? Bluetooth is working fine for me. I'm on the latest release build. Smooth and stable.
mej0248 said:
Were you using a nightly or release build? Bluetooth is working fine for me. I'm on the latest release build. Smooth and stable.
Click to expand...
Click to collapse
Yep it was nightly 2015-05-23 , later I'll try the new nightly and if that does not work, then I will try the release build. Cheers for the info =)
How good is it? Is it better than CM?
I prefer it to CM. The release builds are great. No issues for me.
I4ve been on this ROM for a day now and it works like a charm. Mokee is really great. No buigs or FC for now
EDIT : GPS works for You ? I can't get a fix.... Did a clean flash of Mokee but still no GPS Fix
EDIT #2 : OK now it works, just have o erase modemst1 and modemst2 with fastboot
Hi everyone,
I've been enjoying Mokee for a week, flashed nightlys every two days and just discovered that their OTA system just download the changes from the rom installed to the new build. I tried to DL it and flash but I've an endless bootanimation after.
Is it the same for you too? Thanks
metalmoot said:
Hi everyone,
I've been enjoying Mokee for a week, flashed nightlys every two days and just discovered that their OTA system just download the changes from the rom installed to the new build. I tried to DL it and flash but I've an endless bootanimation after.
Is it the same for you too? Thanks
Click to expand...
Click to collapse
I don't use OTA.
I heard that it broke ever, then they fixed. I'll link to him.
Try using the Release builds instead. More stable and OTAs are every week or so.
Yes but releases are odexed and xposed does not work with odexed roms
Ok, I don't ever use Xposed with custom roms. Just stock.
Caution ! The 28/06 nightly doesn't work !
I will go back to CM because the 29/06 crashes when I use a theme.
Great rom but I honestly can't see the advantage over CM. Ota would be a plus but it fails.
Back on CM with Cyandelta for incremental updates
Another update on Mokee on Thea :
- OTA works great but you must not remove /system apps and modify build.prop however the phone will bootloop.
- OTA doesn't work with Xposed as well, bootloop
- Release versions (odexed ROM) are really smooth and seem to be more battery friendly than nightly releases...
- The ROM is bugfree, I've been using Mokke for two weeks now and no reboot, no freeze, perfect experience
metalmoot said:
flashed nightlys every two days and just discovered that their OTA system just download the changes from the rom installed to the new build. I tried to DL it and flash but I've an endless bootanimation after.
Click to expand...
Click to collapse
Same here, I'm really happy with Mokee (running release version), no bugs so far and smooth performance. However I tried as you did to download incremental update through Mokee Center and automatically flash through recovery (TWRP), but got endless boot animation, had to download full ROM and flash after wiping system/data/cache/dalvik.
Does anyone know if Mokee can be upgraded simply by flashing full ROM zip without wiping system and data?
Tried again updating through Mokee Center, this time downloading full ROM. Didn't get endless bootloop, but performance was really bad, moto g suddenly rebooted 2 times, very unstable. I decided to wipe all and reflash manually through TWRP. Working fine now... it seems that auto-update are not working very well. Anyone who didn't get those problems and successfully updated through Mokee Center?
I managed to have incremental updates working on release versions. You must not touch anything in /system (you can freeze apps however)
I've been updating like that for two releases and it works
Just a quick for OTA updates on nightly builds with Xposed.
Ota works if you uninstall xposed with the uninstaller zip before flashing OTA !
In this Thread I will port the Iron Rom from the Tab S to our Note 2014
Thanks to Tkkg1994 for making the awsome Iron Rom and xluco for the Kernel
Just to be clear: I didn't developed the Iron Rom (http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107) nor the xluco Kernel (http://forum.xda-developers.com/showthread.php?t=2725193. I just put them together.
Ok, first how you install the Iron Rom: Download the Iron Rom for the T800 and the xluco Kernel for SM-P600 first and put them on external SD Card. After that go into Recovery and wipe EVERYTHING exept external storage. Maby you can also wipe system only but i highly recommend yout to wipe everything. Install now the Iron Rom and DO NOT CHECK REBOOT AFTER THE IRON ROM INSTALLATION, when it has finished, install the xluco kernel. Than do a Reboot. for me, the Rom took some time to boot, and often did some random reboots. when you see the assistant, you have to be very fast, dont configure anything, as I already said before, it will very likely crash after some time.
So, now why I opned this Thread: I'm not a developer, so I cannot do this by myself. Hope I will get some help, I know everybody is waiting for a Lollipop Custom Rom
good point mate ... Maybe I'm going to give other CRs of that a Try ... have you tried that with other Custom ROMs like AOSP ones or others ?
Yes, I did. In the past I could get a KitKat Rom from our big brother P900 running on my device using the same method as I used here.
wulkanat said:
In this Thread I will port the Iron Rom from the Tab S to our Note 2014
Thanks to Tkkg1994 for making the awsome Iron Rom and xluco for the Kernel
Just to be clear: I didn't developed the Iron Rom (http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107) nor the xluco Kernel (http://forum.xda-developers.com/showthread.php?t=2725193. I just put them together.
Ok, first how you install the Iron Rom: Download the Iron Rom for the T800 and the xluco Kernel for SM-P600 first and put them on external SD Card. After that go into Recovery and wipe EVERYTHING exept external storage. Maby you can also wipe system only but i highly recommend yout to wipe everything. Install now the Iron Rom and DO NOT CHECK REBOOT AFTER THE IRON ROM INSTALLATION, when it has finished, install the xluco kernel. Than do a Reboot. for me, the Rom took some time to boot, and often did some random reboots. when you see the assistant, you have to be very fast, dont configure anything, as I already said before, it will very likely crash after some time.
So, now why I opned this Thread: I'm not a developer, so I cannot do this by myself. Hope I will get some help, I know everybody is waiting for a Lollipop Custom Rom
Click to expand...
Click to collapse
@wulkanat @hitman1376 were either of you able to get this ROM running on your device? If so, which build did you use? I've tried at least a dozen different configurations via Aroma Installer on both the 2.4.5 and 2.5 builds, but the SystemUI crashes on me within seconds of booting up every time.
raneym305 said:
@wulkanat @hitman1376 were either of you able to get this ROM running on your device? If so, which build did you use? I've tried at least a dozen different configurations via Aroma Installer on both the 2.4.5 and 2.5 builds, but the SystemUI crashes on me within seconds of booting up every time.
Click to expand...
Click to collapse
To be honest , I didn't try it out ... but , as the devices have so many things in common , it wasn't so odd ... but , does it happen the same on the MM ROM ?
With Best Wishes
Hitman1376
hitman1376 said:
To be honest , I didn't try it out ... but , as the devices have so many things in common , it wasn't so odd ... but , does it happen the same on the MM ROM ?
With Best Wishes
Hitman1376
Click to expand...
Click to collapse
You would think so. A couple years ago, it seemed like most apps/features were interchangeable between the Note 2014, Note Pro, Tab Pro, and Tab S on Kitkat. I distinctly remember my go-to ROM was originally designed for the Note Pro.
As far as IronROM V3.0 (MM) goes, the Aroma installer detected my device right away and put the kibosh on that experiment... not that it would have worked anyway seeing as how we don't have a 6.0.1 kernel... I was just hoping to get enough of the ROM installed so I could use TWRP's file manage to extract the files I want while still in recovery.
Anyway, now that my Note7 will be stuck with a non-rootable, unsupported, firmware for eternity; I figured it'd be fun to grab my old SM-P600 and see what havoc I can wreak on it.
raneym305 said:
You would think so. A couple years ago, it seemed like most apps/features were interchangeable between the Note 2014, Note Pro, Tab Pro, and Tab S on Kitkat. I distinctly remember my go-to ROM was originally designed for the Note Pro.
As far as IronROM V3.0 (MM) goes, the Aroma installer detected my device right away and put the kibosh on that experiment... not that it would have worked anyway seeing as how we don't have a 6.0.1 kernel... I was just hoping to get enough of the ROM installed so I could use TWRP's file manage to extract the files I want while still in recovery.
Anyway, now that my Note7 will be stuck with a non-rootable, unsupported, firmware for eternity; I figured it'd be fun to grab my old SM-P600 and see what havoc I can wreak on it.
Click to expand...
Click to collapse
Well , if you just want to play around , you can try out the stock Lollipop with my Prime Kernel and get better Performance and Battery or even CM13 / CM14 ... about the aroma , you can disable the device verification ... also I guess you can force the TW MM boot with Lollipop Kernel like it boots CM13 and CM14 ( I don't mean booting without any problems and also don't forget T-805's MM Kernels !! ) the Biggest problem is that we don't have a MM Bootloader which is the biggest problem ... anyway , this device is still so powerful to play newest games and OSs ... It's not fair to abandon it :laugh: ... You know ? I had a very busy day and I have been awake since around 6 AM when I woke for salat till now which is 12:41 AM :crying: !! so , My brain doesn't have any more juice and I need to get some sleep ... I hope you like my kernel ( esp. In case you'd like to test it out :laugh: ) ... I Updated it just some minutes ago
With Best Wishes
Hitman1376