Has anyone tested BAM on the TF201? If so what were your feelings on it vs CM11?
TF 201 is on BAMs supported Device List
I'm assuming you need to be on the 4.1 bootloader with a working recovery. You install it via the application
BAM Installer
if anyone is on 4.1 and willing to flash you should let me know how it goes. I am on Cromi-X on the 4.2 bootloader so I am hesitant to go through the whole flashing process if the ROM is buggy. Thanks in advanced.
feyerbrand said:
Has anyone tested BAM on the TF201? If so what were your feelings on it vs CM11?
TF 201 is on BAMs supported Device List
I'm assuming you need to be on the 4.1 bootloader with a working recovery. You install it via the application
BAM Installer
if anyone is on 4.1 and willing to flash you should let me know how it goes. I am on Cromi-X on the 4.2 bootloader so I am hesitant to go through the whole flashing process if the ROM is buggy. Thanks in advanced.
Click to expand...
Click to collapse
I have been trying to get it install since yesterday. It says it installed successfully using the new TWRP Voyager recovery that is KitKat compatible. The ROM just sits at the Asus screen though for 3 or 4 minutes and won't boot the ROM. I don't know if there is something else I need to do or not. I know I haven't bricked my device as I was able to get back into recovery and install my backup. Anyone have any suggestions???
alias4ever said:
I have been trying to get it install since yesterday. It says it installed successfully using the new TWRP Voyager recovery that is KitKat compatible. The ROM just sits at the Asus screen though for 3 or 4 minutes and won't boot the ROM. I don't know if there is something else I need to do or not. I know I haven't bricked my device as I was able to get back into recovery and install my backup. Anyone have any suggestions???
Click to expand...
Click to collapse
Maybe the new recovery isn't necessary? I am not too sure it seems like a lot of the community for developing is found on Google+ I haven't seen anything on XDA about BAM Android for our Primes, hence the reason I posted here in the Q&A
feyerbrand said:
Maybe the new recovery isn't necessary? I am not too sure it seems like a lot of the community for developing is found on Google+ I haven't seen anything on XDA about BAM Android for our Primes, hence the reason I posted here in the Q&A
Click to expand...
Click to collapse
Actually I had to use the new recovery because of an error 7 message. I did research and I found out I needed a KitKat compatible recovery. Hopefully someone out there can help us.
alias4ever said:
Actually I had to use the new recovery because of an error 7 message. I did research and I found out I needed a KitKat compatible recovery. Hopefully someone out there can help us.
Click to expand...
Click to collapse
Have you tried it with the CWM that Namidairo made?
feyerbrand said:
Have you tried it with the CWM that Namidairo made?
Click to expand...
Click to collapse
I would love to try it with the new CWM that Namidairo made but I am very leery of trying it with it because of the fact being that I heard you could hard brick your device using CWM with certain ROM's.
alias4ever said:
I would love to try it with the new CWM that Namidairo made but I am very leery of trying it with it because of the fact being that I heard you could hard brick your device using CWM with certain ROM's.
Click to expand...
Click to collapse
Ah well that makes sense, we don't want to brick the tab over a possible ROM. How is CM11 though? I had 10.2 for a while but it stuttered too much for my taste. Have you noticed any degradation of overall performance with gaming and videos?
feyerbrand said:
Ah well that makes sense, we don't want to brick the tab over a possible ROM. How is CM11 though? I had 10.2 for a while but it stuttered too much for my taste. Have you noticed any degradation of overall performance with gaming and videos?
Click to expand...
Click to collapse
Nope really don't want any bricks. I'm still playing around with CM11 so I'll let you know for sure in a few days. So far I really like it. :good:
Related
Just wanted to know how everyone is preparing for android 4.3 which I'm sure is to be announced and available later on today.
Custom ROM users: are you flashing back to stock?
As a rooted and custom ROM user, I'm torn between flashing back to stock for update or just waiting a few weeks until its baked into some awesome ROMs. Thoughts?
Sent from my Nexus 10 using Tapatalk HD
HarmonyFlame said:
Just wanted to know how everyone is preparing for android 4.3 which I'm sure is to be announced and available later on today.
Custom ROM users: are you flashing back to stock?
As a rooted and custom ROM user, I'm torn between flashing back to stock for update or just waiting a few weeks until its baked into some awesome ROMs. Thoughts?
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Not doing anything. Doesn't really bother me. Once it's released, if it is found to have some must-have improvements, then i'll most likely wait for AOKP to incorporate it, but for now, my tablet works just fine and i can't see a reason to consider changing things up.
hughlle said:
Not doing anything. Doesn't really bother me. Once it's released, if it is found to have some must-have improvements, then i'll most likely wait for AOKP to incorporate it, but for now, my tablet works just fine and i can't see a reason to consider changing things up.
Click to expand...
Click to collapse
That's fair. For me though, honestly I may end up flashing back just to resolve the Mali driver issue. On my n10 it is a huge problem and I may not be able to wait any longer to resolve it, so hopefully 4.3 includes the drivers. We'll see.
Sent from my Nexus 4 using Tapatalk 4 Beta
I also plan to just wait until it makes its way to CM. I'm planning on building my ROMs from source from this point on (adding PDroid and some other local changes) and it shouldn't take too long until CM is updated. I picked CM mainly because their build instructions are the best I've been able to find.
Just announced that starting today, Android 4.3 will be pushed to the Nexus 4, Nexus 7, Galaxy Nexus and Nexus 10.
Hi guys,
Do you recon 4.3 will need wipe or non - wipe? hope its non-wipe
HarmonyFlame said:
Just wanted to know how everyone is preparing for android 4.3 which I'm sure is to be announced and available later on today.
Custom ROM users: are you flashing back to stock?
As a rooted and custom ROM user, I'm torn between flashing back to stock for update or just waiting a few weeks until its baked into some awesome ROMs. Thoughts?
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Can we receive update if on stock, but rooted? Do we have to have stock recovery? Never had a Nexus device so I'm just wondering...
Its been so long since I updated mine I can't even remember what to do. I think the Nexus 10 toolkit will do it for me since I'm rooted.
dfox123 said:
Can we receive update if on stock, but rooted? Do we have to have stock recovery? Never had a Nexus device so I'm just wondering...
Click to expand...
Click to collapse
While I'm not positive, I'm fairly certain that you update even without stock recovery, but you will use root unless you use an app called "OTA Root keeper"
It's already available for download at https://developers.google.com/android/nexus/images#mantarayjwr66v
Flash with fastboot.
CazeW said:
It's already available for download at https://developers.google.com/android/nexus/images#mantarayjwr66v
Flash with fastboot.
Click to expand...
Click to collapse
Keep in mind if you do this, your device will be wiped. This is NOT an OTA.
mustbepbs said:
Keep in mind if you do this, your device will be wiped. This is NOT an OTA.
Click to expand...
Click to collapse
I flashed manually and via the script and get stuck at the X logo on boot.
I would hold off on flashing for now.
xetrev said:
I flashed manually and via the script and get stuck at the X logo on boot.
I would hold off on flashing for now.
Click to expand...
Click to collapse
Flashed mine, wiped all data, but works fine (I had restored to stock rom and recovery beforehand).
Notable changes include slightly snappier response, miracast support, and apparently finger flinger is fixed (read that in a other thread, i'm not rooted so can't check)
Chluz said:
Flashed mine, wiped all data, but works fine (I had restored to stock rom and recovery beforehand).
Notable changes include slightly snappier response, miracast support, and apparently finger flinger is fixed (read that in a other thread, i'm not rooted so can't check)
Click to expand...
Click to collapse
Yup, we can't confirm that in the code yet but it looks good. The end to random reboots might be here
Sent from my Nexus 10 using xda app-developers app
Chluz said:
...and apparently finger flinger is fixed (read that in a other thread, i'm not rooted so can't check)
Click to expand...
Click to collapse
Made me laugh. I'm sure you meant surface flinger.
From my S-Off BadSeed DNA
trickster2369 said:
Made me laugh. I'm sure you meant surface flinger.
From my S-Off BadSeed DNA
Click to expand...
Click to collapse
Yep ?
Sent from my Nexus 10 using Tapatalk HD
Did anyone get ota yet? I don't want to flash factory image so I don't lose data as I just lost all my data a week ago
Sent from my Xperia Play (r800x)
xetrev said:
I flashed manually and via the script and get stuck at the X logo on boot.
I would hold off on flashing for now.
Click to expand...
Click to collapse
I had that problem when I flashed the old OS after unlocking bootloader when I got the N10. A subsequent data wipe fixed it:
1. Reboot into Fast Boot
2. Select Recovery using volume rocker. Hit power to select. You'll get the android mascot with the red exclamation point.
4. Press Power and Volume Up at the same time (this is the side of the volume rocker that is away from the power button for those new to the device).
5. Choose to wipe all data. Confirm the selection.
6. Reboot.
I have my rablet rooted and bootloader unkocked. If i update via OTA i will lose root i suppose? I heard that the bootloader changes too. It will be relocked?
Hey all!
It's first build of CM11 for i777
Downloads:
ROM (17.11.2013): http://d-h.st/Swz
core google apps (17.50 MB): http://d-h.st/PbA
Sources:
kernel: https://github.com/CyanogenMod/android_kernel_samsung_smdk4412/tree/cm-11.0
Do not promise to support it in future
Rom is not tested due I have no such device.
Thanks!!!
But if i want to install i have to be on cm10.2 and flash cm11 and core apps without wipes? Right? O i can install it from a 4.1.2 samsung rom?
Sent from my SGH-I777 using XDA Premium 4 mobile app
Wayland_ACE said:
Hey all!
It's first build of CM11 for i777
Downloads:
ROM (17.11.2013): http://d-h.st/Swz
core google apps (17.50 MB): http://d-h.st/PbA
Sources:
kernel: https://github.com/CyanogenMod/android_kernel_samsung_smdk4412/tree/cm-11.0
Do not promise to support it in future
Rom is not tested due I have no such device.
Click to expand...
Click to collapse
Doesn't boot. Just spinning logo forever. Didn't have time to see if ADB was on to try to get a logcat. Will try later.
auTONYmous said:
Doesn't boot. Just spinning logo forever. Didn't have time to see if ADB was on to try to get a logcat. Will try later.
Click to expand...
Click to collapse
I had been keeping an eye on his i9100 thread and the jist was to flash the latest CM nightly to have the newest recovery then reboot recovery and flash Waylands CM11 like normal.
Thanks Wayland, I am glad you have decided to help us out as well!
Also I just tested using the steps from the i9100 thread and still just get the CM boot logo. Nothing I did could get past it. I could however restore a Nandroid I had just made so no harm done.
Kind Regards,
Render
It doesnt boot for me too I would like to help with a logcat but the usb port dont work on my phone
Thanks anyway!
Sent from my SGH-I777 using XDA Premium 4 mobile app
I will try again later today and provide a Log when I get back home
Logcat
I could not get past the CM boot logo so I could not provide a log at. If there is another way to get one for you then please let me know so I can do so.
Kind Regards
Render
I tried my best to get my phone to spit out a logcat because my phone also would not boot, it just sat at the splash screen. But, alas, I could not figure out how to get my device to not show offline. I know how to do it when Android is running, but not like that. BUTTTT, if someone can explain to me how to make the phone go "online" for adb during boot, I can pull a logcat, and would be more than grateful to do so, because im dying to try KitKat. Keep up the good work!
fastboot?
Is there no way to put the phone into fast boot mode and get a logcat that way? Would give it a try myself but my comp is on the fritz.
CWM
Rookie407 said:
Is there no way to put the phone into fast boot mode and get a logcat that way? Would give it a try myself but my comp is on the fritz.
Click to expand...
Click to collapse
This might be a long shot, but I think it requires you to have CWM 6.0.4.3 and higher to install correctly. You might double check your current version.
My CWM version was 6.0.4.5 and it doesnt boot. So theres may be a problem that only a logcat could show..
Sent from my SGH-I777 using XDA Premium 4 mobile app
Wayland said he would be taking another look at CM11 and our phone tomorrow. Just so you guys know.
Read on the i9100 forum before that someone who couldn't it to boot the normal way got it to work by just flashing CWM and not CM10.2. Tried that and no luck here.
phillytemptation said:
Read on the i9100 forum before that someone who couldn't it to boot the normal way got it to work by just flashing CWM and not CM10.2. Tried that and no luck here.
Click to expand...
Click to collapse
Could it be an incompatible kernel issue? I know on the lg optimus zip and galaxy precedent (both straight talk phones with dev support from another forum) we had to enable sd-ext before cm would work. Not sure if that's the case here or not just a suggestion.
Wish I had internet to set up my build environment.
I have been watching the i9100 thread and have e been trying everything that has worked there but to no avail. I have been wanting to compile cm11 but have not had the time to do so. Wayland, most likely, will need to make some minor change but since he does not own our phone so we will need to be patient. I told him I would volunteer to test if need be.
RenderBroken said:
I have been watching the i9100 thread and have e been trying everything that has worked there but to no avail. I have been wanting to compile cm11 but have not had the time to do so. Wayland, most likely, will need to make some minor change but since he does not own our phone so we will need to be patient. I told him I would volunteer to test if need be.
Click to expand...
Click to collapse
If needed I have a spare s2 I can use for dev purposes however I'm not on the i777 but the s959g(straight talk) Vasily the same but minor software differences. I can be reached at [email protected] a lot easier then I can on this thread if y'all need any assistance.
I have been working on 4.4 for the i777 and getting CM11 to work right, I found that some people had to do ANOTHER Wipe data/factory reset AFTER flashing the rom and gapps. This is what has to be done on the CM11 rom I ported to the i777 to make it work. Just thought I would share.
Would you happen to know what is not working on this ROM? Any bugs you have found? Thanks.
RenderBroken said:
I have been working on 4.4 for the i777 and getting CM11 to work right, I found that some people had to do ANOTHER Wipe data/factory reset AFTER flashing the rom and gapps. This is what has to be done on the CM11 rom I ported to the i777 to make it work. Just thought I would share.
Click to expand...
Click to collapse
hmm still can't get it to boot.
RenderBroken said:
I have been working on 4.4 for the i777 and getting CM11 to work right, I found that some people had to do ANOTHER Wipe data/factory reset AFTER flashing the rom and gapps. This is what has to be done on the CM11 rom I ported to the i777 to make it work. Just thought I would share.
Click to expand...
Click to collapse
Doesn't work. Not only that but now I can't go back to cm 10.2 after flashing this. I'd advise everyone to stay away from this port until its 100℅ bootable. If you try to go back you end up with status 7 error.
Sent from my Nexus 4 using Tapatalk
Kitkat is very important for our old device!!
How can we do ?
Is there any developer is building CM11~~
chongbos said:
Kitkat is very important for our old device!!
How can we do ?
Is there any developer is building CM11~~
Click to expand...
Click to collapse
It is very doubtful you will ever see kitkat. it also depends on whether there is a recovery that can flash it.
Sent from my One using Tapatalk
I've been on my wife's gnexus running kitkat and the very latest kernels for a few days and I can tell you it's got nothing on good ol' Thundershed/Leankernel 6.2. I think I've flashed everything available for the tbolt and that is the best for me....by far!
chongbos said:
Kitkat is very important for our old device!!
How can we do ?
Is there any developer is building CM11~~
Click to expand...
Click to collapse
its very possible with the few 3.0 kernels we have floating around, compiling the latest clockwork mod would be the easiest step, but I don't know of any developers up to do it, I just got a new computer so I might, oh & I could guarantee that the data wouldn't work lol
I'd just be happy to find an active host that I can DL the stock, debloated ICS ROM. Or CM 10.1 or CM 10.2. I can't believe that I can't find a single place to DL from.
Randy
I'm helping my friend install CyanogenMod 12 on his S4 (jfltevzw). We've rooted it and we're currently doing a full backup through Safestrap in case anything happens. Once that's finished, I'm unsure as to what we should do. CyanogenMod's wiki has installation instructions for the Verizon S4, but it says in big bold letters to not attempt this if on a ROM newer than I545VRUAMDK. He's on the latest version that Samsung/Verizon have pushed out, which is I545VRUFNK1. Is there an alternate way to install CyanogenMod on top of the newer stock ROM, or is it not possible?
vaindil said:
I'm helping my friend install CyanogenMod 12 on his S4 (jfltevzw). We've rooted it and we're currently doing a full backup through Safestrap in case anything happens. Once that's finished, I'm unsure as to what we should do. CyanogenMod's wiki has installation instructions for the Verizon S4, but it says in big bold letters to not attempt this if on a ROM newer than I545VRUAMDK. He's on the latest version that Samsung/Verizon have pushed out, which is I545VRUFNK1. Is there an alternate way to install CyanogenMod on top of the newer stock ROM, or is it not possible?
Click to expand...
Click to collapse
its not possible. ONLY mdk builds will work.
Raymondlikesroot said:
its not possible. ONLY mdk builds will work.
Click to expand...
Click to collapse
Dang, so there's absolutely nothing whatsoever that can be done? The page says you can't downgrade, but is anything at all possible now that he's beyond the MDK build? He really wants to make the switch and is fine with doing a complete wipe or whatever is necessary.
EDIT: I've been trying to read up on the VZW S4 and why this isn't possible, but I don't quite get it. Reading other threads it seems like the reason is because the bootloader is locked, but that can't be the case if he was able to install Safestrap. I'm coming from a Nexus 5 where everything is incredibly simple, so I apologize for my ignorance. (I don't mean to say you're wrong or anything as I have no idea myself, I just don't understand why it doesn't work on newer ROMs.)
vaindil said:
Dang, so there's absolutely nothing whatsoever that can be done? The page says you can't downgrade, but is anything at all possible now that he's beyond the MDK build? He really wants to make the switch and is fine with doing a complete wipe or whatever is necessary.
EDIT: I've been trying to read up on the VZW S4 and why this isn't possible, but I don't quite get it. Reading other threads it seems like the reason is because the bootloader is locked, but that can't be the case if he was able to install Safestrap. I'm coming from a Nexus 5 where everything is incredibly simple, so I apologize for my ignorance. (I don't mean to say you're wrong or anything as I have no idea myself, I just don't understand why it doesn't work on newer ROMs.)
Click to expand...
Click to collapse
The reason we use Safestrap as opposed to twrp is because the bootloader is locked.
Surge1223 said:
The reason we use Safestrap as opposed to twrp is because the bootloader is locked.
Click to expand...
Click to collapse
Oh, okay. Really unfortunate that this isn't possible now. So he's just stuck with TouchWiz and can't do anything about it?
vaindil said:
Oh, okay. Really unfortunate that this isn't possible now. So he's just stuck with TouchWiz and can't do anything about it?
Click to expand...
Click to collapse
Yep
Sent from my my Lollipopped S4
vaindil said:
Oh, okay. Really unfortunate that this isn't possible now. So he's just stuck with TouchWiz and can't do anything about it?
Click to expand...
Click to collapse
you can install hyperdrive rom
its not lolipop but its worlds better then stock ...
also there is a chance of getting the 5.01 GPE edition rom running when Samsung releases the lolipop update for the vz s4
that would at least give us a working lolipop kernel to use with the gpe rombase
and hey you never know there could be a exploite in the lolipop rom/kernel that lets us get kexec working
Basically safestrap loads after the kernel but early enough to replace point to a different root for the system. So we can load what ever system we want... But are stuck with the kernel the phone booted. If the system is based on the stock kernel this is fine... But when it starts making calls to custom kernel stuff you will have trouble.
So Cyanogenmod only provides the GUI? I've installed CM on two B&N tablets and I've been asked to root a new Verizon Samsung Galaxy S4. I've assumed that, because it's new, it will have I545VRUFNK1 4.4.2. I rooted my VSG s3 years ago to 4.3 and there was no going back on that one. It looks like it's the same with VSG s4. So, if CM provides only the GUI, then a rooted VSG s4 can still access Google Apps? What is the concern with with TW based ROMs? Is it the recovery/backup feature or only being stuck with the VSG s4 GUI?
Raymondlikesroot said:
its not possible. ONLY mdk builds will work.
Click to expand...
Click to collapse
This explains why I bricked my phone when I tried to flash CM12...
ryant35 said:
This explains why I bricked my phone when I tried to flash CM12...
Click to expand...
Click to collapse
haha yeah, that could maybe potentially probably be the issue. Just maybe.
Couldn't you ODIN back to an older baseband version and then try to flash CM12?
Lockett said:
Couldn't you ODIN back to an older baseband version and then try to flash CM12?
Click to expand...
Click to collapse
Nope, in order to get CM, you'll need to be on MDK. Samsung prevents downgrading.
btw. the baseband version doesn't matter much. Its the bootloader version that is the toughie.
Boo! I just picked up my S4 yesterday after a 5 month run of using Windows Phone so I'm trying to figure this phone out. I'm on NK1 and trying to figure out how to root now.
vaindil where did you find a VRUFNK1 compatible version of Safestrip?
Hey guys, so the last phone I rooted and had a bootstrap on with custom roms was the Motorola Droid x2. We couldn't even get into the kernel. So with that being said I've acquired super user on my g3 months ago to freeze apps. But now I don't depend on my phone like I did then for work. So I want to do the whole thing and I'm unsure what choices to make. I'm not looking for a guide for installing stuff (at least not yet ) just trying to get suggestions and hopefully good recommendations.
So here's the main point for the post
TLDR!!!!!
Current android version 5.0.1
kernels- unlock it? Change it? Not sure what all you can actually do with that.
Bootstrap- clock work mod? Or any other one can't think of names but need something to load roms
Rom for battery and power- cyanogenmod is what I use to run on the x2 not sure if it's still one of the best?
Anything else I missed that I should get and check out?
Thanks in advance
Put TWRP custom recovery on your phone with the autorec TWRP app by @bender_007, in the General section of the non-variant specific G3 sections. Once you give the app superuser permissions it looks like it's hung up but give it 10-30 seconds because it's backing up your current recovery. Then click the button to install TWRP. Download the latest TWRP v2.8.7.0 from its thread also somewhere in the G3 sections, and flash it from your current TWRP.
I use @xdabbeb 's VS985 v2.0 ROM, which is based on the latest official LG ROM, build 35B, based on Android 5.1.1. Very happy with it, very smooth and great on battery.
I haven't heard the term bootstrap with regards to custom recoveries. I'd suggest just calling them custom recoveries.
Thanks for your input it's been a while after I read it I was like yep it's custom recoveries lol thank you again
Tweek900 said:
Thanks for your input it's been a while after I read it I was like yep it's custom recoveries lol thank you again
Click to expand...
Click to collapse
You're welcome! Glad to help!
So I tried to come to this site from my computer and it wouldn't load properly. I'm not sure if it's a me probably or the site please let me know thanks
Tweek900 said:
So I tried to come to this site from my computer and it wouldn't load properly. I'm not sure if it's a me probably or the site please let me know thanks
Click to expand...
Click to collapse
its you. i used a pc to access the site most of today and haven't had an issue.
Alright thanks I'll look into my pc then. Also I haven't decided if I want to flash a custom kernel I don't know what all it can change any advice?