Related
I finally rooted my TF to Prime 1.5. Which custom kernel do you use? Are there advantages to CBCS over Netformer or vice versa?
i have used both and to be honest there is little difference between them for how i use it, however i switched back to clemsyns purely of my own choice as battery seemed better for me however as each TF is set up totally different this may not be the case for you.
try them both and see how you get on just remember to clear cache and dalvik before applying new kernel.
Thanks. I couldn't tell much difference, either, but this is my first Android device & first root of anything, so I wanted to check with someone w/experience.
Using Kernel Manager makes flashing a new kernel a breeze (although I did get stuck in a boot loop when I tried to go back to Roach's kernel). It can be set to auto-clear of the cache & Dalvik, too.
Frankly, you all have made rooting so easy that I can't see why everyone shouldn't do it.
No worries the only thing you will have to worry about now is OFD, obsessive flashing disorder. Rooting is a slippery slope lol, always got to try the latest rom or kernel.
I use Clemsys 1.6 at 1.4 Ghz with interactive governor.
No problem of use, no reboots. Stable.
Sent from my Transformer TF101 using XDA Premium App
Hi,
I just purchased a used Droid X to replace my mom's OG droid. I read as much as I could on rooting the DX and all that jazz (completely different coming from an HTC by the way... holy hell and I am sorry).
I have already rooted the Droid X, installed boot strap... etc.
Made a backup using recovery.
I searched the forum for "most reliable ROM" and came up with rubix 2.0
I flashed it through recovery and ended up stuck at the boot motorola logo.
Panicked and stressful I have to say! WTF! Now I understand why it sucks so much to have a locked bootloader. You CAN'T boot into recovery to flash your back up! Well at least I couldn't. I tried the home button, search button boot up method and didn't work. I was getting worried....
After reading more... I SBF'd it which is a completely new thing to me. It ended up being easy but it's really lame coming from the Incredible and Thunderbolt. Again, I now feel your pain!
Anyways, I really DO NOT want to go through that again. Do you have any idea how hard it was to find a downloadable SBF file due to the megaupload shutdown!!!! I have just re-rooted after using the SBF file found here: http://www.droid-life.com/2011/09/06/droidx-gingerbread-4-5-602-sbf-released/
So after all that I am just going to ask.
What is the most reliable ROM and what SBF file do I have to download to be compatible with it???
Remember... this is for my mom... I need a reliable, stable, bug free ROM. This ROM will likely be the one she will use indefinitely so please choose one that is as stable as can be.
Thank you for all your help.
That SBF is perfect for the newest roms.
The DX is on .605...but the kernel doesn't change at all so there is literally no change if you accept the OTA or not.
Stable GB Rom...
I haven't messed around with 1st init (blur based) for a long time...so I can't say for certain.
But as far as 2nd init goes...
I'd choose MIUI.
She'll love it.
Actually, I flashed MIUI to my mom's X (who is completely tech-retarded) and she has been on it for a good 3-4 months now...
http://rootzwiki.com/topic/11858-ro...charge-led-updated-bootmenu-charge-while-off/
The newest build includes a working "boot menu" that can get you into CWM from a power-off state if you ever need it.
Also...
Once you flash...
I'd HIGHLY recommend using said bootmenu to set her overclocking speeds / cpu governor.
I assume she won't be to worried about speed...
So I'd either underclock her a tad...
Or leave her at stock.
But be sure to set the CPU governor to "SmartassV2"
The phone sleeps like a champ.
Literally the second you turn the screen off...the phone sleeps...and stays asleep until a notification/screen is turned on.
FANTASTIC battery life due to this.
I mean...stellar battery.
Also, it's VERY stable.
No bugs what-so-ever...
My signature also has a DX specific rom install tutorial if you'd like a refresher on the DX.
The stock ROM isn't bad. We have a few users in my office that still use it and they have no problems at all. I like to flash a lot and I am currently on MIUI (ICS) but I am thinking about going back to Vortex. It is by far the most stable ROM I've found on the Droid X.
The best Blur ROM I flashed was Liberty 3 v2, great speed, battery etc. CM4DXGB is the best ROM I have ran, I have tried most of them and CM7 is my go to daily driver. Great overall performance, very fast, great battery once you get settled in and awesome customizations. I flashed it on my dads phone and he loved it, my Mom still has a flip phone! Haha
Sent from my DROIDX using Tapatalk
I wouldn't try liberty as a new user, there is a lot of customization that can confuse someone IF they aren't experienced. Apex has two days of battery life when calibrated so i would choose apex. no bugs and incredibly smooth!
Edit: Posted this in the wrong forum - removed.
Sent from my DROIDX using Tapatalk
I am currently using MIUI 2012.2.1 after trying liberty and one other. I really like it, but as is expected after rooting, i want to play around. Although after reading your post, not so sure. MIUI really is great. I can go 2 days without recharging if i shut down at night. I did manage to get into a boot loop requiring an SBF etc. This was traumatic, but now i know how my phone works!
So I would like to try CM7. I downloaded the latest for the Droid X. I guess MIUI does not let rom manager install roms so i have to use clockwork. No problem. Is there any thing i need to do special since i am on a 2-init rom? Do i just do a dalvik wipe, then install the zip?
Gadget_Guru said:
I am currently using MIUI 2012.2.1 after trying liberty and one other. I really like it, but as is expected after rooting, i want to play around. Although after reading your post, not so sure. MIUI really is great. I can go 2 days without recharging if i shut down at night. I did manage to get into a boot loop requiring an SBF etc. This was traumatic, but now i know how my phone works!
So I would like to try CM7. I downloaded the latest for the Droid X. I guess MIUI does not let rom manager install roms so i have to use clockwork. No problem. Is there any thing i need to do special since i am on a 2-init rom? Do i just do a dalvik wipe, then install the zip?
Click to expand...
Click to collapse
Do a system and a data wipe.
Beamed from my TF101 using Tapatalk HD
I had zero issues with SoD running HC roms and HC bootloader. I have serious issues with ICS roms and the unlocked bootloaders. Here is what i have tried:
First tried v3 unlocked bootloader with Thors recovery and CM9 alpha rom. I had many issues with SoDs everytime the screen went off it seems like it SoD. That was the original issue. I recently just tried 3 different recoveries including twrp/ezterry/thors and used all 3 to do full wipes. I installed ezterrys ICS rom. I am getting less SoD..maybe 1 per day but they still persist. Does anyone have any ideas what im doing wrong? Am i the only one with these issues? Its not an app causing this either as I have run with both roms on the base w/o installing any apps and the SoD still persists. Anyone have any experience with this and can enlighten me?
droidroidz said:
I had zero issues with SoD running HC roms and HC bootloader. I have serious issues with ICS roms and the unlocked bootloaders. Here is what i have tried:
First tried v3 unlocked bootloader with Thors recovery and CM9 alpha rom. I had many issues with SoDs everytime the screen went off it seems like it SoD. That was the original issue. I recently just tried 3 different recoveries including twrp/ezterry/thors and used all 3 to do full wipes. I installed ezterrys ICS rom. I am getting less SoD..maybe 1 per day but they still persist. Does anyone have any ideas what im doing wrong? Am i the only one with these issues? Its not an app causing this either as I have run with both roms on the base w/o installing any apps and the SoD still persists. Anyone have any experience with this and can enlighten me?
Click to expand...
Click to collapse
Had sod on any rom (and stock) with changed bootloader (and other problems). Went back to ota stock without root. No problems
I have SoD since going from thors rom back to taboonay and then to V8 bootloader, still trying to solve the issue but no luck. I can't even connect to pc to root it again as I've lost that too
Any of you running a 501?
If so, it's an issue with the kernel.
MD
a500 here
Moscow Desire said:
Any of you running a 501?
If so, it's an issue with the kernel.
MD
Click to expand...
Click to collapse
Using A500
I see so many others with success which is why its killing me that this is not more common issue. There must be something we are doing slightly wrong or forgot to do causing this.
Ok, here is the real deal.
1. ICS Bootloader. Mandatory. Check it when you boot, it should say in the left corner.
2. Recovery version has no effect on SOD. However, you should have the correct one for ICS. Currently I use 1.7.3.
3. The kernel. Now, most of the ICS Roms in the forum for the 500 have a "tweaked kernel". These are the ones you want to use. MAKE SURE the rom you are using is for the patched ICS Bootloader. This includes EZTerry's and Civatos. You have to pay attention with Civ's as he may still have some designed for HC bootloader. YOU DO NOT WANT THESE. I believe Smaury's and Vache's are ok also, but check first.
4. This is probably where the problem is. Wipes and Formats. Sometimes, leftover code from a previous kernel or modules could still possibly be in the tab. This can cause strange issues.
Wipe
Data/factory reset
Cache
Dalvik Cache
(depending on recovery version)
Format System
Format Flexrom
Do this 2 or 3 times, then install the rom.
I use CWM 1.7.3 recovery (too lazy now to change but will in the future)
Also, if you have any doubt which bootloader you currently have, download AcerRecoveryInstaller and it should tell you. After OTA in the Dev forum will also tell you. You don't have to do anything with the app, just start it to get information.
This should get you going.
MD
I have two A500's, both with V8 bootloader and the latest flexreaper rom. One doesn't SOD, the other has constant SOD's. I'm beginning to think it's the hardware. Mine were purchased about 6 months apart, maybe different hardware revisions?
riot1031 said:
I have two A500's, both with V8 bootloader and the latest flexreaper rom. One doesn't SOD, the other has constant SOD's. I'm beginning to think it's the hardware. Mine were purchased about 6 months apart, maybe different hardware revisions?
Click to expand...
Click to collapse
This is some good info! I am pulling my hair our here! As far as what MD suggested I have done all those steps...multiple times with 3 different recoveries wiping everything i can. Do you happen to remember when you purchased them? I bought mine from newegg 8.16.2011
riot1031 said:
I have two A500's, both with V8 bootloader and the latest flexreaper rom. One doesn't SOD, the other has constant SOD's. I'm beginning to think it's the hardware. Mine were purchased about 6 months apart, maybe different hardware revisions?
Click to expand...
Click to collapse
You know, you just added some insight into a theory I've been tossing in my head. Although I thought this was only a51x and a70x based. I didn't know it might be effecting the 50x as well.
Let me run this at you. With the 51x and 70x, the bootloaders seem to be matched to the specific version of ICS installed from factory. (COMGen, version number, etc). We know this, as the bootloaders on several tabs have different naming conventions. It's why certain root methods will not work on some tabs. Currently we have 3 methods, but 1 requires CWM (and our current version will brick the tab if you use the restore option..../data is what bricks).
It's possible, that with ICS, certain kernels are required to function properly on the 500 also. We all know with ICS, the kernel communicated a lot with the bootloader. This "may" be associated with some obscure part of the hardware as well. This I don't know. But with the newer tabs, it definately seems to be hardware software related. Some Roms just WILL NOT run on some tabs.
Now for you guys, here is what I might try. Different kernels. Try running a stock kernel for that specific build number. Or if you haven't tried it yet, try running EZ_Terry's OC kernel built form source. See if you still get SOD.
Just something to try.
MD
Moscow Desire said:
You know, you just added some insight into a theory I've been tossing in my head. Although I thought this was only a51x and a70x based. I didn't know it might be effecting the 50x as well.
Let me run this at you. With the 51x and 70x, the bootloaders seem to be matched to the specific version of ICS installed from factory. (COMGen, version number, etc). We know this, as the bootloaders on several tabs have different naming conventions. It's why certain root methods will not work on some tabs. Currently we have 3 methods, but 1 requires CWM (and our current version will brick the tab if you use the restore option..../data is what bricks).
It's possible, that with ICS, certain kernels are required to function properly on the 500 also. We all know with ICS, the kernel communicated a lot with the bootloader. This "may" be associated with some obscure part of the hardware as well. This I don't know. But with the newer tabs, it definately seems to be hardware software related. Some Roms just WILL NOT run on some tabs.
Now for you guys, here is what I might try. Different kernels. Try running a stock kernel for that specific build number. Or if you haven't tried it yet, try running EZ_Terry's OC kernel built form source. See if you still get SOD.
Just something to try.
MD
Click to expand...
Click to collapse
This is an interesting theory and makes sense. In my case with CM9 and Ezterry's rom I have tried the stock kernel for each and ezterry's OC kernel on both...and still SoDs although ezterrys rom/kernel seems to be far less frequest SoDs. We don't have much options for kernels around here.
Progress?
Has anyone made any progress with figuring this out?
My tablet was running fine on a stock, rooted ICS. Then I installed custom recovery, different kernel, and bootloader when I tried JellyBean (ROM | WIP | CM10 JellyBean 4.1.2 Unofficial for acer a500 [Build 3]) from the Developers forum on here. I started getting SoDs and some of my games weren't running, so I went back to the ICS rom, but the SoDs are still happening. At that point, I was pretty sure it was related to the kernel or the bootloader.
On the "ROM | WIP | CM10 JellyBean 4.1.2 Unofficial for acer a500 [Build 3]" thread in the developers section they are questioning if the SoD is related to CyanogenMod (which I don't believe it is). I wanted to post there about what this thread is hypothesizing, but am unable to post to that thread (too new to XDA).
Update
I went ahead and went back to full stock ICS (bootloader, kernel, etc). Then rooted it again.
The disappearing icon issues have gone away.
Now I'm not sure if I should just stick with it like that or venture out into Jelly Bean land again...
Waleslie said:
I went ahead and went back to full stock ICS (bootloader, kernel, etc). Then rooted it again.
The disappearing icon issues have gone away.
Now I'm not sure if I should just stick with it like that or venture out into Jelly Bean land again...
Click to expand...
Click to collapse
Venturing out to JB land is a choice.
Although CM does a pretty good job of doing things, I always have to remember, they lean toward mainstream devices.
We 50x owners, have some pretty good guys. But, we only have a few, compared to the mainstream devices, which have a whole lot more. Welcome to the tablet world.
If it were a samsung or Asus, would probably have a ton more.
But, my ICS on my 501 runs pretty darn good. And I'm thankful to each and every dev and cook who strive to make it better. It's a pity there are not more for our device.
SOD will always plague us it seems. A lot seems to depend on the revision hardware. Seems the earlier versions don't get it much.
MD
droidroidz said:
This is some good info! I am pulling my hair our here! As far as what MD suggested I have done all those steps...multiple times with 3 different recoveries wiping everything i can. Do you happen to remember when you purchased them? I bought mine from newegg 8.16.2011
Click to expand...
Click to collapse
same problem as you and 8/10/2011 is when I got mine. I have had some version of hc to work with no sod, but tried everthing and every combination out there (with the mod bootloader) and still have sod, so just went back to stock.
Hi all. I am a proud owner of a 32gb wifi Nexus 7. While not new to Android, this is my 1st tablet. Love the size, weight and most of all...is android!
My question is, what combination of ROM with kernel would be best? I know there are a lot of things to consider, but I am looking for opinions only. Without talking down certain ROMs and/or kernels, we can share here opinions based on stability, customization and smoothness! I already encounter an issue when I rooted my 2 days brand new N7 rooting it with the Tool kit. Rooted it fast and easy (successfully), but installed TWRP. Me knowing no better, I love and I'm used to CWM, so I installed ROM Manager and CWM. Long story short, when I went to flash one ROM in particular, in recovery, when I formated system, data reset, wiped cache & dalvik, it wiped my sdcard clean. I mean, thats how I flash my Note 2 for a clean install and never had an issue like that. Then, when I tried to get into recovery via fastboot, I couldn't. It was like CWM wasn't there.
Thanks to the Tool Kit, I was able to un root and go back to stock....then rooted again (with TWRP) and finally flashed CM-10 stable. Also flashed faux's 4.1.2 kernel @ 1600. I like what I have so far, but I would like something more. I got the stable CM-10 from the actual CM thread so the ROM is pretty much untouched.
Can anybody please share what ROM and kernel I should try for a bit of stability, power and smothness at the same time? Any inputs and/or advice, will be greatly appreciated!
Try Paranoidandroid as a ROM. And i think the kernel that comes with it is the smoothest i have used with it.
Sent from my Nexus 7 using Tapatalk HD
Wally72 said:
Hi all. I am a proud owner of a 32gb wifi Nexus 7. While not new to Android, this is my 1st tablet. Love the size, weight and most of all...is android!
My question is, what combination of ROM with kernel would be best? I know there are a lot of things to consider, but I am looking for opinions only. Without talking down certain ROMs and/or kernels, we can share here opinions based on stability, customization and smoothness! I already encounter an issue when I rooted my 2 days brand new N7 rooting it with the Tool kit. Rooted it fast and easy (successfully), but installed TWRP. Me knowing no better, I love and I'm used to CWM, so I installed ROM Manager and CWM. Long story short, when I went to flash one ROM in particular, in recovery, when I formated system, data reset, wiped cache & dalvik, it wiped my sdcard clean. I mean, thats how I flash my Note 2 for a clean install and never had an issue like that. Then, when I tried to get into recovery via fastboot, I couldn't. It was like CWM wasn't there.
Thanks to the Tool Kit, I was able to un root and go back to stock....then rooted again (with TWRP) and finally flashed CM-10 stable. Also flashed faux's 4.1.2 kernel @ 1600. I like what I have so far, but I would like something more. I got the stable CM-10 from the actual CM thread so the ROM is pretty much untouched.
Can anybody please share what ROM and kernel I should try for a bit of stability, power and smothness at the same time? Any inputs and/or advice, will be greatly appreciated!
Click to expand...
Click to collapse
Hi, Wally72...
I don't know if this question can be answered objectively... it all hinges on how you intend to use the device, day to day. If your going to be playing high-octane video games, then a kernel that supports overclocking would be advised... but that will come at a battery life cost. More CPU cycles = battery drain.
For myself, I am currently running PaulOBriens MoDaCo custom ROM (can't post links yet, but Google MoDaCo Nexus7, and you should find it)...
The standard MoDaCo ROM for the N7 doesn't go too far off stock... it just adds some really nice features... AOSP browser (better than Chrome IMHO), expanded powerdown menu, Adobe Flash Player in /system (although Adobe no longer support it, it's still useful to have).
Paul has recently ventured into CyanogenMod territory with CM10.1 unofficial nightlies... which he has stated will be released every Friday.
And this is what I'm running now - MoDaCo CyanogenMod Custom ROM r3 - and in conjunction with Franco's r39 kernel, it's incredibly smooth... and very respectible battery performance as well.
Hope this is of some use...
Rgrds,
Ged.
stock
stock is stable
vital982 said:
stock is stable
Click to expand...
Click to collapse
stock if u want a tabui try smoothrom with franco kernel
Hey guys.
I flashed the ktoonz kernel about a week ago and it works just fine except one thing: after a reboot my phone has forgotten my wifi password and i have to connect it again.
every time i restart the phone it's the same. it worked on stock kernel.
does anyone know this problem? it's quite annoying..
--edit--
i forgot to mention that i'm on stock samsung rom android 4.3 with touchwiz
and it's the international s4 (i9505).
TweeXta said:
Hey guys.
I flashed the ktoonz kernel about a week ago and it works just fine except one thing: after a reboot my phone has forgotten my wifi password and i have to connect it again.
every time i restart the phone it's the same. it worked on stock kernel.
does anyone know this problem? it's quite annoying..
--edit--
i forgot to mention that i'm on stock samsung rom android 4.3 with touchwiz
and it's the international s4 (i9505).
Click to expand...
Click to collapse
I make the same mistake
Originally Posted by monkteo View Post
Hi,I just install the (I9505 XXUEMKE JB 4.3 Pre-Rooted STOCK ROM's) great rom and I thanks you for bring it here.
Question; after installed I try to flash a custom kernel (AOSP/TW/GE - 4.2/4.3 KT-SGS4 - MFD - KTweaker) and everything started to work wrong (no wifi,net fc,and many others)please tel my what kernel it's perfect for your rom and also if it's realy ned to flash a custom kernel ?
10X
A custom kernel is not required for these ROMs as they include the stock Samsung TouchWiz kernel which I'd say is probably the best kernel for the stock ROMs.
Isn't there a way to get WiFi working without flashing a new rom? I don't want to wipe the phone actually and the kernel is pretty nice I think.
It's pretty konservative with the battery and gives me extra power when I need it.
Isn't there a WiFi-fix or something like that?
TweeXta said:
Isn't there a way to get WiFi working without flashing a new rom? I don't want to wipe the phone actually and the kernel is pretty nice I think.
It's pretty konservative with the battery and gives me extra power when I need it.
Isn't there a WiFi-fix or something like that?
Click to expand...
Click to collapse
WiFi-fix
Regards
Got the same issue with 4.4.2 and newest kernel version...
Tried changing build.prop line but with no success.
Is there any kind of help or a adequate wifi fix for kitkat?
Solved: wiped cache and dalvik and fixed permissions couple of times. Now it works
Sent from my GT-I9505 using xda app-developers app
I'm using GT-I9505 "international" with Paranoid Android 4.45 and successfully installed Ktoonsez kernel (3.4.94) with flashify app using Philztouch cwm recovery.
No problems at all, everything works, not tweaking by KTweaker, just raised 2.2GHz from PA's processor settings, ondemand as processor governor and Noop on i/o scheduler.
Tried few KTweaker profiles first but didn't find any good what understands to drop processor on deep sleep mode, almost all keeps it running all the time, PA's own handling with freshly installed KT-SGS4 kernel did best job for me.
Testing with profiles was frustrating thing, there wasn't way back to same situation what I got on fresh install.. few PA flashes later stand on "default".
Props to KToonsez (kernel), Christian Göllner (Flashify) and Paranoid Android.