Related
ROOTSide ROM
Base Flipside ROM with root/busybox/unknown sources enabled. Only thing different in this rom than rooting it yourself is you get to check/uncheck unknown sources. Yes, that means you can turn unknown sources ON and OFF! I have a clockworkmod recovery folder zipped up for distribution, but I want to post a full-fledged ROM zip file for the masses. PM me, and I will send you the ZIP file that I have right now.
What you get:
base install for the flipside (AT&T) with motoblur ready to set up. It is the exact same thing as doing a factory reset, but you get all the benefits of superuser with busybox and the addead feature of having unknown sources checkbox in the settings.
I will work towards a deoxed version this weekend as well.
No custom bootscreen (yet). No custom anything, really.
Almost There
I am currently in the middle of Deodexing the image. I have added in wifi tethering, and ensured it will have superuser and busybox pre-packaged. Next step is pushing this to my wife's phone and not having her get a pretty brick in return. If all goes well, I will be posting the image by morning light (CST).
Fingers Crossed!
Well
Things didn't go too well with my first build attempt. Appears to be a permission issue with the /system folder. I will sleep on it, and give it a second go in the morning. Sorry for the apparent "tease". If you want a faster build, I could use some other devs working with me.
Hey man, sounds like you're doing great! Keep it up...I already found a way to get the root with unknown sources checked, so i'm just gonna wait for the deoxed version! Hope it goes well as you try again.
Current Issues
unable to deodex the following:
/system/app/AABSync.odex
/system/app/blur-services.odex
Will try to load to phone without dodexing those two files. Hopefully all will go well.
Me too...good luck!!
jonsjava said:
unable to deodex the following:
/system/app/AABSync.odex
/system/app/blur-services.odex
Will try to load to phone without dodexing those two files. Hopefully all will go well.
Click to expand...
Click to collapse
Both of those files are att/moto bloat... just be rid of them
Sent from my MB508 using XDA App
Glad to see some work on this device, I love the form factor but it's obviously not very popular with devs...
Very interested to see this come around. I would like to streamline the wife's phone. Her battery life is a 1/3 of my rooted and flashed X10. Sadly though I am NOT a Dev nor even a cook.
I would have had something sooner, but I ran into issues not related to the ROM. Still working on it. Anybody have an idea for upgrading the CWM from the one we can currently use?
so I was curious, I was able to get to unlock mode with an sqlite thing and it worked just fine for me, but have you been able to knock out the bloat and stuff? cause it sounds like the makings of a custom rom lol
you know what the turtle said.. slowly but surely I will win this race
jonsjava said:
I would have had something sooner, but I ran into issues not related to the ROM. Still working on it. Anybody have an idea for upgrading the CWM from the one we can currently use?
Click to expand...
Click to collapse
Several ppl have said they have run into this problem...don't know what the deal is...
Is it possible to get CM7, or it's a problem with a locked kernel?
Ok, I just got a new phone for the Mrs., so I can break the flipside and unbreak it as much as I like.
Time for some real fearless development lol.
jonsjava said:
Ok, I just got a new phone for the Mrs., so I can break the flipside and unbreak it as much as I like.
Time for some real fearless development lol.
Click to expand...
Click to collapse
sounds good man, keep us posted on progress!!
So check this out...I messaged the guy at modmymobile and asked how things were going becuase I heard people were having problems getting an updated CMW and this is his response:
"been sittin on the updated cwm recovery binaries and been draggin my feet/takin a break the past week or 2. i'll throw something out soon, but cant commit to a timeframe, sorry."
Looks like things are on the up and up...stay patient everyone
GOOD JOB!!!,
We are waiting for the rom
Dukenukemx said:
Is it possible to get CM7, or it's a problem with a locked kernel?
Click to expand...
Click to collapse
I can't install CM7, it reboots and locks up, then I have to reinstall froyo. It never worked when I had eclair either.
Okeydokey. I installed a custom ROM ( VillainRom3.0 ) last night, and it has messed up a few things :/. Most apps randomly blank out and crash instantly - wifi doesn't work, phone freezes.
I'm rather new, and most of this stuff does confuse me; anyone able to post simple step by step of how to get a suitable kernal for VillainRom3.0 ?
EDIT: It also removed CWM and Superuser from the App menu :/
MegaJoshh- said:
Okeydokey. I installed a custom ROM ( VillainRom3.0 ) last night, and it has messed up a few things :/. Most apps randomly blank out and crash instantly - wifi doesn't work, phone freezes.
I'm rather new, and most of this stuff does confuse me; anyone able to post simple step by step of how to get a suitable kernal for VillainRom3.0 ?
EDIT: It also removed CWM and Superuser from the App menu :/
Click to expand...
Click to collapse
I was running villain rom with the standard chainfire kernel that most start with and that was stable - I must say though I wasn't too impressed with it - recently installed Westcrip's Resurrection ICS remix and boy am I happy I did! - if you want villain though just search for a compatible rom using the last letters from your baseband version - that normally does the trick! Good luck
I've found an old backup laying around, and got to installing that, so VillainRom is no longer on their. I'm back to a rooted firmware and that's it.
BUT: Now my computer ( nor any other ) recognises when It's pluggedin via USB :/.
I have this issue flashing some newer roms lately, not sure what it is.
To get back to a stock rom/rooted rom use the methods listed under the dev section of your phone that are the initial root direction using odin or something similar.
clarity1 said:
I have this issue flashing some newer roms lately, not sure what it is.
To get back to a stock rom/rooted rom use the methods listed under the dev section of your phone that are the initial root direction using odin or something similar.
Click to expand...
Click to collapse
Cheers, I ended up getting a working firmware on it, but I still have certain issues that are ****ting me >_>
Hello,
I am considering updating my gingerbread based ROM on my old EVO 4g (I am currently running Cyanogen mod 7.1)...
Its been a very long time since I've flashed a ROM to my phone, but I have been wanting to upgrade to an ICS/JB ROM for a while because (amongst other things) I hear that these android 4.0 ROMs are better when it comes to battery life.. As you can probably tell, I am not one of these folks that re-flashes their rom every week so I may be a bit rusty with this and I am a little bit intimidated. While I would like to try something new I also am a bit worried that my lack of experience may cause me to make a mis-step and mess up my phone..
The ROM I am looking at right now is the new release of MotoBlur'd, found here: .. I understand that this ROM is based on CyanogenMod 10, and since it seems I cannot get a version of the raw CM10 directly to install on my phone, perhaps MotoBlur'd is the next best thing...
But before I open up this can of worms and go off and wipe my phone and flash this new rom, I had 3 questions which I hope someone with experience can answer
1) All other things being equal, would this actually help with the battery life, over the Gingerbread based CM 7.1?
2) Is it still the case that Netflix and other video viewing apps do not work with this (or any other ICS/JB) ROM?? They mention it in the android dev thread, but no one has confirmed that these things work or not work.
3) Do I have to peroform any extra steps or install anything else (other than what is shown in the instructions) to move the phone from CM 7.1 to the latest Motoblur'd ?? For example do I need to install an ICS based ROM first before JB? Or can I just flash directly to this ROM??
Hopefully I can do this without causing too much damage or requiring too much help from the users in this forum... Of course any advice or suggestions anyone can give me would help...
Thanks
TPK2013
For number 3 just make sure your using the smelkus 4.3 recovery and for sure wipe the sd-ext to make sure you get a clean flash..
Sent from my PC36100 using xda app-developers app
hondafreak513 said:
For number 3 just make sure your using the smelkus 4.3 recovery and for sure wipe the sd-ext to make sure you get a clean flash..
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
1. battery life will be worse. most likely
2. That is stil lthe case
3. Read the Guide in my signature (Evo Superguide). It'll help you a lot
HipKat said:
1. battery life will be worse. most likely
2. That is stil lthe case
3. Read the Guide in my signature (Evo Superguide). It'll help you a lot
Click to expand...
Click to collapse
Excellent guide, Hipcat... I think this will really be helpful to me... As someone who doesn't do this all the time, it can really help to have a guide like that to cover all the bases.. I know we are supposed to try to search for the stuff that we need to know, but sometimes its hard to know even what we need to know, and sometimes the multitudes of information we find is contradictory or out of date, so this really helps..
I found a broken link on it, so I posted that as a reply in your thread (I hope thats okay)...
I think I may just stick with my GB based rom, as much as I would like to monkey around with ICS or JB.. I guess I don't see the sense of switching if it won't help my battery life and if it will prohibit the use of video playing apps (which, I know, suck a lot of battery)..
The biggest problem for me is the battery life (I found several contradictory explainations on how to calibrate the battery, I will try the one found in your guide next), but mainly I believe my problem is that I have too much garbage loaded on the phone (not reloading after a year and a half can do that), and a lot of stuff loads in the background so that is probably affecting my battery life.. Also I don't think I am using the most up-to-date radio, which is probably causing the most battery drain of all... So I am going to try the following...
1) I am going to (actually I already have) upgrade my radio to 2.15.00.01.15
2) As per your, and honda's suggestion I will try to update my recovery to smelkus 4.3 (I think I am using clockwork recovery right now, although I am not sure if that is the same thing or not)..
3) I will try to re-format and re-partition my SD card and attempt to install A2SD so I can have more room for apps (can I use A2SD with CM 7?)
4) I will wipe everything, and reload to CyanogenMod 7.2 (perhaps this will work better than 7.1) and reload about half the apps I have on there now (only the stuff I am using now)..
If battery life is my main concern, is there a better ROM I should be using??? I picked CM in the first place because it was an AOSP (no frills, no extra garbage) ROM, however I haven't been able to update my PRL (havent ever updated it, probably)...
Thanks again for your response... You and your guide have been quite helpful...
TPK2013
TPK2013 said:
Excellent guide, Hipcat... I think this will really be helpful to me... As someone who doesn't do this all the time, it can really help to have a guide like that to cover all the bases.. I know we are supposed to try to search for the stuff that we need to know, but sometimes its hard to know even what we need to know, and sometimes the multitudes of information we find is contradictory or out of date, so this really helps..
I found a broken link on it, so I posted that as a reply in your thread (I hope thats okay)...
I think I may just stick with my GB based rom, as much as I would like to monkey around with ICS or JB.. I guess I don't see the sense of switching if it won't help my battery life and if it will prohibit the use of video playing apps (which, I know, suck a lot of battery)..
The biggest problem for me is the battery life (I found several contradictory explainations on how to calibrate the battery, I will try the one found in your guide next), but mainly I believe my problem is that I have too much garbage loaded on the phone (not reloading after a year and a half can do that), and a lot of stuff loads in the background so that is probably affecting my battery life.. Also I don't think I am using the most up-to-date radio, which is probably causing the most battery drain of all... So I am going to try the following...
1) I am going to (actually I already have) upgrade my radio to 2.15.00.01.15
2) As per your, and honda's suggestion I will try to update my recovery to smelkus 4.3 (I think I am using clockwork recovery right now, although I am not sure if that is the same thing or not)..
3) I will try to re-format and re-partition my SD card and attempt to install A2SD so I can have more room for apps (can I use A2SD with CM 7?)
4) I will wipe everything, and reload to CyanogenMod 7.2 (perhaps this will work better than 7.1) and reload about half the apps I have on there now (only the stuff I am using now)..
If battery life is my main concern, is there a better ROM I should be using??? I picked CM in the first place because it was an AOSP (no frills, no extra garbage) ROM, however I haven't been able to update my PRL (havent ever updated it, probably)...
Thanks again for your response... You and your guide have been quite helpful...
TPK2013
Click to expand...
Click to collapse
Yep, I fixed that link and what you said is why I wrote that guide; because searching can be a real pain in the @ss sometimes. It's like a teacher telling you to look up a word you can't spell. Well how do you search for an answer if you're not really sure of the question?? lol
You cant update your PRL on any non-stock rom. It has to be stock for you to be able to do that
Well if battery life is your main concern I always suggest a good sense 3.0 ROM. If you are worried about bloat that can be removed. If you want I can hook you up with a rom/kernel combo with everything you want.
When I am not testing or making a new rom I use sense 3.0 and can get 8 hrs of heavy use on stock battery. Thats netflix with 3-4 hrs use plus web surfing and calls during the rest. On my extended battery with light use I can get 4+ days.
If you would like to try my rom pm me before you partion your sdcard. There are certain things you need to do for it to work right.
Sent from my PC36100 using xda app-developers app
CNexus said:
You cant update your PRL on any non-stock rom. It has to be stock for you to be able to do that
Click to expand...
Click to collapse
Perhaps I will go to stock and try to update the PRL before I go ahead and update the ROM to custom... However, this Evo is on Boost Mobile (not Sprint) network, so I am not sure how to appropriately update the PRL... Should I just update it as if it were a regular Sprint Evo 4g or does it matter?
CNexus said:
You cant update your PRL on any non-stock rom. It has to be stock for you to be able to do that
Click to expand...
Click to collapse
Umm updating prl only requires the *228 call from the phone and it works on any rom. Now to put a custom or older prl it takes a bit more. Updating your profile now that I do believe you have to be on a Sprint rom but I don't have Sprint so I can't say for sure.
Sent from my PC36100 using xda app-developers app
jlmancuso said:
Umm updating prl only requires the *228 call from the phone and it works on any rom. Now to put a custom or older prl it takes a bit more. Updating your profile now that I do believe you have to be on a Sprint rom but I don't have Sprint so I can't say for sure.
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
Never heard of that *228, so cant say anything about that
Updating profile and prl I've always seen and heard can only be done on stock, unless you use this ##codes apps I saw somewhere....
The ## codes only work on the sprint roms. To change prls on AOSP roms you need a windows pc with qpst setup and prl files on the pc. Then you have to enable diagnostic mode through adb or a terminal emulator. There is a thread here on our EVO forum to do it. I will bump it so you can check it out. It sure beats all the backing up and restoring to do it.
Edit: I bumped it. It is in the dev section.
jlmancuso said:
The ## codes only work on the sprint roms. To change prls on AOSP roms you need a windows pc with qpst setup and prl files on the pc. Then you have to enable diagnostic mode through adb or a terminal emulator. There is a thread here on our EVO forum to do it. I will bump it so you can check it out. It sure beats all the backing up and restoring to do it.
Edit: I bumped it. It is in the dev section.
Click to expand...
Click to collapse
Yeah. Theres an app that uses scripts to emulate the ##code functions.
Really? I can't believe I have not heard of that till now. Do you know what it is called? I would love to check it out.
Sent from my PC36100 using xda app-developers app
jlmancuso said:
The ## codes only work on the sprint roms. To change prls on AOSP roms you need a windows pc with qpst setup and prl files on the pc. Then you have to enable diagnostic mode through adb or a terminal emulator. There is a thread here on our EVO forum to do it. I will bump it so you can check it out. It sure beats all the backing up and restoring to do it.
Edit: I bumped it. It is in the dev section.
Click to expand...
Click to collapse
Found the thread, thanks!!
Now I just have to figure out which PRL file to use for my Evo on Boost, and where to find it (I think this is what stopped me from updating the PRL before, not knowing if I should use a sprint PRL or something else)...
Edit: I did find this thread regarding boost PRLs on EVO
And if there is indeed an app that emulates the ## commands, I would like to know what that is...
... TPK2013
Heck if your on boost you need a boost prl. You can Google boost prls and find dozens of them. I would suggest using the latest one. Just dial *228 and it will update your prl. After it finishes reboot your phone. It is really that simple. I do it on my cricket flashed EVO but it works for every service provider.
Sent from my PC36100 using xda app-developers app
I used the Brute force app to Root tried installing CWR and bootlooped How do I install a new recovery?
http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667
Flash back to stock and start over.
Lol as far as I know cwm don't exist for this phone lol
BAD ASS G3
I got TWRP to work although I really don't see the point of rooting this phone I don't hardly see any ROM's for this phone
gtrplr71 said:
I got TWRP to work although I really don't see the point of rooting this phone I don't hardly see any ROM's for this phone
Click to expand...
Click to collapse
There is the modified stock / AICP+variants / CM / SlimRom Variant Deviant
Still in the beta phases but progress none the less. My original link will take you back to stock without root so you will be all set without needing to re-root.
gtrplr71 said:
I got TWRP to work although I really don't see the point of rooting this phone I don't hardly see any ROM's for this phone
Click to expand...
Click to collapse
Maybe for the g4 more devs will be pulled towards this phone. You have 2 devs but 1 of them has PC down. Think he just fixed it but it takes a bit to load PC with everything. This phone would have more devs if they owned the phone. Some guys are working blind.
BAD ASS G3
Toneman07 said:
There is the modified stock / AICP+variants / CM / SlimRom Variant Deviant
Still in the beta phases but progress none the less. My original link will take you back to stock without root so you will be all set without needing to re-root.
Click to expand...
Click to collapse
BACARDILIMON said:
Maybe for the g4 more devs will be pulled towards this phone. You have 2 devs but 1 of them has PC down. Think he just fixed it but it takes a bit to load PC with everything. This phone would have more devs if they owned the phone. Some guys are working blind.
BAD ASS G3
Click to expand...
Click to collapse
I hear you thanks for the insight. one ques how do you enable USB debugging on this phone? I saw it and cant find the thread.
gtrplr71 said:
I hear you thanks for the insight. one ques how do you enable USB debugging on this phone? I saw it and cant find the thread.
Click to expand...
Click to collapse
Software information then repeatedly hit build number until you see toast message
Q&A for [ROM][SM-T900] CyanogenMod for Tab Pro 12.2 SM-T900 (v2wifixx)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][SM-T900] CyanogenMod for Tab Pro 12.2 SM-T900 (v2wifixx). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Rooting Tab Pro 12.2 with last firm done!
arcadia2uk said:
For rooting the latest firmware, did you use the CF-Auto-Root from the main site, marked KOT49H.T900XXUANB5, or a new one made for the KOT49H.T900UEUANI1? If the latter, would you mind posting a link to a T900UEUANI1 compatible version?
Click to expand...
Click to collapse
Don't needed. You can root the normal cf-auto-root with latest sock without problem.
After we pm chat last days about rollback to T900UEUAND4 as unique possibility for rooting, i decided to do a last try before that, and luckily works perfect:
-just did a factory reset to restore from B3 recovery i been trying to prev installed T900UEUANI1 stock, wipe caché with stock recovery, odined cf-auto-root and voilá, just rooted!
No need to do the old B3-rollback-prior-D4 method now. Just a normal auto-root with no hassling.
temp maybe?
chhaggerty said:
It sounds like you maybe having a "Sleep of Death" (SOD) issue. The T520 and P900 have had similar problems. I will out of town until Monday but I'll do some research and hope to have a solution soon.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
crpalmer said:
There is a deadlock in Samsung's code triggered by the CPU boost driver. Look in the t520 device repo for the commit that disables it (actually probably 2 commits because I removed some functionality that doesn't make sense for this processor).
Click to expand...
Click to collapse
Dauntless said:
Device: SM-T900
Android: 4.4.2 (Stock, unrooted)
Kernel: 3.4.39-2534013
When putting the tablet into sleep mode, it will automatically shut itself down. When I try to turn it back on, the tablet will only do so after I plugged in the charger. The battery itself is fully charged.
I've updated to the latest available firmware version that's available to me. I couldn't find any list of known issues, so I'm wondering if this is a common problem and if I should return my tablet?
Click to expand...
Click to collapse
Same here. It seems that the problem maybe is temperature: after some time charging it gets really hot and maybe can't awake from that and need rebooting.
I've disabled the magnet sensor vía 3rd app to off the close-lid functionality but don't improve the problem.
Here in summer the room gets to +30°c and the Tab ups to almost 65°c when it gets hot!
Maybe it just reach the temp threshold and self shutdown, or intend that not letting awake.
Perhaps CM11 build here charges battery too fast, with higher voltage than allowed and provoque overheating. I mean, i really feels that it's charging real fast..
Well currently its winter and cold. My tab was cool but it does not respond after deep sleep unless i reboot. Dev said he will look into it and i will wait. Not sure if temp is cause as mine was not definitely not hot.
Sent from my LG-D800 using XDA Free mobile app
lingarajug said:
Well currently its winter and cold. My tab was cool but it does not respond after deep sleep unless i reboot. Dev said he will look into it and i will wait. Not sure if temp is cause as mine was not definitely not hot.
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
Posted update last night, check it out
Thanks, btw, i was able to use ODIN to get a good version of TWRP and the ROM installed smoothly. I have encountered a few small bugs but nothing to report that is new. I noticed the "sleep of death" I think you are referring to, deep sleep resulting in a manual reboot to wake up. I have noticed my bluetooth disconnects and reconnects every few minutes during deep sleep..not sure why. will report back. Thanks SO SO much for the development, i love it, so sick of the green and blue and the settings tabs on this stock OS disgust me. I am curious tho, am I the only one who noticed significant slowdown and lag compared to stock? I do not put a lot of stock in benchmarks (skewed toward uncle sammy) but they also showed big slowdown....just my very humble and grateful early experiences. Thanks again.
total reflashing needed?
chhaggerty said:
Posted update last night, check it out
Click to expand...
Click to collapse
Well thanks, but,i don't see a flashing update but an entire 221MBs rom to flash..
Can you post just the little update file , if there's any, to flash above the installed rom?
I don't want to install rom, apps and config all over again.
Thanks!
-----
lingarajug said:
Well currently its winter and cold. My tab was cool but it does not respond after deep sleep unless i reboot. Dev said he will look into it and i will wait. Not sure if temp is cause as mine was not definitely not hot.
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
Yes you are right, i'd tried again and it SODs no matter what temp are. A shame.
-----
arcadia2uk said:
For rooting the latest firmware, did you use the CF-Auto-Root from the main site, marked KOT49H.T900XXUANB5, or a new one made for the KOT49H.T900UEUANI1? If the latter, would you mind posting a link to a T900UEUANI1 compatible version?
Click to expand...
Click to collapse
Well there's a problem right now, seems that this rom prevent to enter recovery.., this is what happen to me:
Reboot from Android with 'reboot to recovery' option and when the TWRP splash logo shows it enter in a bootloop always to this instance that TWRP logo appears.
Then i just installed the good old UAND4 rom and it works fine.
Maybe i shouldn't go to recovery direct from android to prevent bootloop happen and try to go the normal way from boot.
Don't know, maybe I'll try some day.., or maybe better wait to Android L comes to us.
Please advice all that stuff in the respective threads, i can't.., cause' these 'noobs-wait-to-10-posting-before' rules..
Greetings.
bertoxo said:
1. Can you post just the little update file , if there's any, to flash above the installed rom?
2. Yes you are right, i'd tried again and it SODs no matter what temp are. A shame.
3. Well there's a problem right now, seems that this rom prevent to enter recovery.., this is what happen to me:
Click to expand...
Click to collapse
1. You can "dirty"-flash (install w/o wiping) the new ROM over the old one - nothing to re-install - if you wish you could extract the kernel (boot.img) and flash it by Flashify
2. There haven't been reported any SOD issues after flashing chhaggerty's latest ROM version
3. I have had no issues with with TWRP after having flashed the KOT49H.T900UEUANI1 - I just assume that some parts of the Firmware, not touched by cm, has been improved (but since this is WIFI only, it might not be the case for a non phone device) why I preferred to make the update.
arcadia2uk said:
1. You can "dirty"-flash (install w/o wiping) the new ROM over the old one - nothing to re-install - if you wish you could extract the kernel (boot.img) and flash it by Flashify
2. There haven't been reported any SOD issues after flashing chhaggerty's latest ROM version
3. I have had no issues with with TWRP after having flashed the KOT49H.T900UEUANI1 - I just assume that some parts of the Firmware, not touched by cm, has been improved (but since this is WIFI only, it might not be the case for a non phone device) why I preferred to make the update.
Click to expand...
Click to collapse
1- but dirty flashing the update full rom performs well?
1.2- only the boot.img is needed for update?
3- have you tried the reboot-to-recovery option from android?
Thanks.
bertoxo said:
1- but dirty flashing the update full rom performs well?
1.2- only the boot.img is needed for update?
3- have you tried the reboot-to-recovery option from android?
Thanks.
Click to expand...
Click to collapse
The changes done between the two versions (99% sure) was only some modifications in the kernel-code. Why flashing the kernel only should be fine, it will resolve the SOD and also make it run cooler. But if you wish you can also dirty-flash. However, cover your bases with a full back-up.
No issues at all with the reboot to recovery option
arcadia2uk said:
The changes done between the two versions (99% sure) was only some modifications in the kernel-code. Why flashing the kernel only should be fine, it will resolve the SOD and also make it run cooler. But if you wish you can also dirty-flash. However, cover your bases with a full back-up.
No issues at all with the reboot to recovery option
Click to expand...
Click to collapse
Can you give me the boot.img update only to try (5MBs)?
220MBs in the posted download site go sooo sloow on any server..
Thanks a lot!
bertoxo said:
Can you give me the boot.img update only to try (5MBs)?
220MBs in the posted download site go sooo sloow on any server..
Thanks a lot!
Click to expand...
Click to collapse
HERE it is
unzip the downloaded file
place boot.img on your SD
use Flashify to flash the kernel
after this I believe flashify will boot you up in recovery, just reboot and you should be good to go.
Just remember to make a back-up for just in case...
HERE it is
unzip the downloaded file
place boot.img on your SD
use Flashify to flash the kernel
after this I believe flashify will boot you up in recovery, just reboot and you should be good to go.
Just remember to make a back-up for just in case...
Click to expand...
Click to collapse
Thanks!
Installed boot.img and works flawlessly. Now i can back using lid cover again and no more hangs.
I hope they can solve the auto-rotate thing next time.
flashing screen, powering down...
I have twrp 2.8, v2 of our Cyanogenmod, set processor to on demand as suggested...
Still when I play games like CoC and others, if I am not plugged in even with a lot of bat% left, I get a flashing screen and occasionally my tab just decides it needs to shut off.
Any thoughts on what to do? I have greenify and Xposed installed too...
It pretty frustrating.
THANKS GUYS!!
spk99 said:
I have twrp 2.8, v2 of our Cyanogenmod, set processor to on demand as suggested...
Still when I play games like CoC and others, if I am not plugged in even with a lot of bat% left, I get a flashing screen and occasionally my tab just decides it needs to shut off.
Any thoughts on what to do? I have greenify and Xposed installed too...
It pretty frustrating.
THANKS GUYS!!
Click to expand...
Click to collapse
My guess is that gaming need more power, why I would stop greeify and reset the governor to interactive while gaming. But other than that I have no ideas, as I haven't heard of this problem before.
This ROM is fantastic! Smooth, fast, responsive and just as described...big thanks.
spk99 said:
I have twrp 2.8, v2 of our Cyanogenmod, set processor to on demand as suggested...
Still when I play games like CoC and others, if I am not plugged in even with a lot of bat% left, I get a flashing screen and occasionally my tab just decides it needs to shut off.
Any thoughts on what to do? I have greenify and Xposed installed too...
It pretty frustrating.
THANKS GUYS!!
Click to expand...
Click to collapse
I don't know if you noticed, but chhaggerty just released a version 3, maybe this will work as there has been some work on the governors.
chhaggerty said:
New update see OP
Click to expand...
Click to collapse
Can i use the 4.4.4 GAPPS instead of 4.4.3 you are posting?
arcadia2uk said:
Thanks for another quality update, notably when reading how other cm11 exynos versions always seems to break something. With your T-900 cm11, I have never had any issues. The latest version is still running smooth, the changes in the CPU governor will probably allow for better battery life with the added conservative setting. However, I don't know what trade-off this will have on performance.
Click to expand...
Click to collapse
Maybe they start to use the big.LITTLE behavior of the Exynos, instead of ever using just the full power a15 cluster (battery eater).
I've haven't tried it but since it's a 4.4.4 rom they should work fine.
Error flashing ROM
Hi guys,
I get this error message when I try to flash CM11:
"Can't install this package on top of incompatible data. Please try another package or run a factory reset"
This is a brand new rooted SMT-900 Tab Pro 12.2". Here's some notes:
- I received the error using V1, V2, and V3, all receive the error message
- I downloaded two copies of v3 from two separate mirrors (CA and AZ), both receive the error message
- I did a factory reset and still received the error message
- Wiped davlik/cache/system partitions
- Tried on TWRP 2.7 and 2.8, both receive same error message
- All I have done to this tablet is root it, install TWRP, and create one backup
Any thoughts? I can try using CWM if someone can give me a quick overview of how to install it and remove TWRP (or keep TWRP).