Hey all -
I have a T-Mobile Galaxy SIII with TWRP, AOKP JB Milestone 5 and GooManager. I got a pop-up for AOKP JB Milestone 6 this morning, so I downloaded it and added that file, Lean Kernel 2.9 and gapps (latest that could be downloaded) to the flash list. I set my Dalvik cache to clear before flashing anything, then rebooted the phone to flash everything. Immediately after the flash, the phone seemed to reboot, but with a blank screen. After a while, the capacitive buttons on the front started working and when I plugged the phone into my computer the file transfer program popped up.
However ... at no point can I ever get anything to display on the screen. I've tried rebooting into recovery (volume up, home button, power button) and nothing. I don't really care about the data on my phone, I have proper backups of everything. But what I can't seem to do is get it to a point where I can recover it. What are my options here if rebooting into recovery doesn't work?
Thanks!
As an addendum, the phone is clearly booted into the OS. I have a blinking notification LED that indicates a new e-mail, and calls placed to the phone cause it to ring. I just can't see .... anything on it.
I was able to get into TWRP, somehow. I took out my T-Mobile SIM card and had it plugged into USB. I held down the recovery combo and then it booted up into recovery. It also displayed the Galaxy SIII white splash screen for the first time since the bad flash. What the hell.
chuffykow said:
I was able to get into TWRP, somehow. I took out my T-Mobile SIM card and had it plugged into USB. I held down the recovery combo and then it booted up into recovery. It also displayed the Galaxy SIII white splash screen for the first time since the bad flash. What the hell.
Click to expand...
Click to collapse
so was you able to use your phone again i say go back to a nandroid you have or flash a rom that you know works good on your phone without that white screen and trouble shoot from there that it very strange indeed if you get success with the other just try posting in the ROM thread that you flashed you could possibly get more help where it happened :good:
I went back to AOKP Milestone 5 after doing a full wipe. I saw a number of graphics changes in the Milestone 6 code review, so it's possible that had something to do with it. In any case, I'm no longer panicing
Does mr6 use the 3.4 kernel? If yes, then you were using the wrong version of leankernel.
Ya its all kernel related and user error.
Aerowinder said:
Does mr6 use the 3.4 kernel? If yes, then you were using the wrong version of leankernel.
Click to expand...
Click to collapse
mt3g said:
Ya its all kernel related and user error.
Click to expand...
Click to collapse
I assumed it was user error. I just wanted to lay out the steps I took, so I could get some help on a recovery path. I thought that a JB based ROM would work with any kernel that supports JB. Looks like I was wrong.
chuffykow said:
I assumed it was user error. I just wanted to lay out the steps I took, so I could get some help on a recovery path. I thought that a JB based ROM would work with any kernel that supports JB. Looks like I was wrong.
Click to expand...
Click to collapse
Nope, JB can be AOSP, TouchWiz, 4.1, 4.2, 4.2.2, 3.0 kernel, 3.4 kernel. Just need to read and make sure you know what you're doing before just doing it. That's why I frown at people being lazy (not just you) and not reading the forums and such, and just using apps to update and flash.
mt3g said:
Nope, JB can be AOSP, TouchWiz, 4.1, 4.2, 4.2.2, 3.0 kernel, 3.4 kernel. Just need to read and make sure you know what you're doing before just doing it. That's why I frown at people being lazy (not just you) and not reading the forums and such, and just using apps to update and flash.
Click to expand...
Click to collapse
Thank's for the condescension, I appreciate being called lazy. I might not have an encyclopedic knowledge of Everything Android, but between the knowledge I do have and the details I read on the AOKP release page, I saw nothing that indicated I _couldn't_ run LeanKernel, especially when it was only a point release on the same ROM I was previously using.
I had a look at the changelog that's available on their page. It's pretty lame. http://gerrit.sudoservers.com/#/q/status:merged,n,z that one will probably have the kernel info. A good rule of thumb is when you flash a new rom, wait until the kernel is up to date (release date). For instance, don't flash a 3/01 kernel on a 4/24 rom - wait for kernel update.
I don't recommend flashing anything with the 3.4 kernel right now. Even if you manage to pull off stability, it's still laggy and eating about 3x the battery it should. This goes for the custom kernels, too. I'll put up with stability issues, but can't deal with bad battery. Already bad enough as it is. Need my phone during the day and not near a charger.
chuffykow said:
Thank's for the condescension, I appreciate being called lazy. I might not have an encyclopedic knowledge of Everything Android, but between the knowledge I do have and the details I read on the AOKP release page, I saw nothing that indicated I _couldn't_ run LeanKernel, especially when it was only a point release on the same ROM I was previously using.
Click to expand...
Click to collapse
calm down lol, you could have read up any of the kernel threads that there are some compatible issues with kernels and roms right now.
Aerowinder said:
I had a look at the changelog that's available on their page. It's pretty lame. http://gerrit.sudoservers.com/#/q/status:merged,n,z that one will probably have the kernel info. A good rule of thumb is when you flash a new rom, wait until the kernel is up to date (release date). For instance, don't flash a 3/01 kernel on a 4/24 rom - wait for kernel update.
I don't recommend flashing anything with the 3.4 kernel right now. Even if you manage to pull off stability, it's still laggy and eating about 3x the battery it should. This goes for the custom kernels, too. I'll put up with stability issues, but can't deal with bad battery. Already bad enough as it is. Need my phone during the day and not near a charger.
Click to expand...
Click to collapse
Thanks for the tip! I appreciate it.
Related
I'm hoping that someone might be able to help me with a problem I'm having with the Franco Kernel. I have a rooted Galaxy Nexus, running on stock Android 4.0.2. I have a bit of experience running various custom ROMs and kernels with a OG Droid and HTC Thunderbolt. Until now, I've been content to run stock ICS on the GNex, along with the stock kernel.
I was impressed with the amount of praise I have recently read (I'm a habitual lurker on a number of Android forums) about the Franco kernel, however, and thought I would give it a go. If it can improve performance and battery life, that is fantastic. So, I bought the franco.Kernel updater from the Market, downloaded the zip file (#15), proceeded to recovery and installed it.
That seemed to all go smoothly. The problem is that when I rebooted, the phone got hung up on the black and white "Google" screen. I know sometimes, it can take a while for the phone to do what it needs to do under the hood before it boots up, but after ten minutes on the "Google" screen I did a battery pull, went straight to recovery and reverted to my latest backup.
I've done some searching for anyone who's had a similar issue, but I can't seem to find what the problem might be. Most likely, I'm simply missing something small but critical to the successful installation of this kernel. I'm hoping someone with more experience than me might recognize what it is I'm doing wrong.
Any patient assistance or advice would be heartily appreciated. Cheers!
I could be wrong, but Franco works for 4.0.3, not 4.0.2.
Which could be precisely the one small thing I am missing. I will check this out. Thanks for the suggestion.
Im using franco 14.4, not yet upgraded because when you flash a new kernel, you have always to wipe everything and i'm lazy now ..
P4p3r1n0 said:
Im using franco 14.4, not yet upgraded because when you flash a new kernel, you have always to wipe everything and i'm lazy now ..
Click to expand...
Click to collapse
Where are you getting this information from?
Not once did I have (nor have other people) wipe everything on kernel updates. You do not have to wipe everything for a kernel flash...
bowsersoulstar said:
Where are you getting this information from?
Not once did I have (nor have other people) wipe everything on kernel updates. You do not have to wipe everything for a kernel flash...
Click to expand...
Click to collapse
cool! thanks! good to know I read a bit everywhere.
I mean, I know how a kernel is, and thinking about it it's true that is not needed to wipe, but if he has some problems he could try this out :/ maybe a fresh installation of everything could be good
I have searched via various keywords for days and have not found an answer to my problem yet. I have only run across one other post (on another forum) that describes exactly my issue and they are asking the exact same question I have with no response.
I am using the AT&T Samsung Galaxy S3. I have downloaded CM 10.0.0 stable d2att on several occasions (different computers even), verified the md5, and installed on my phone. I have used CWM, CWM Touch, and TWRP to install hoping it was an issue there. Regardless of what I have done, I have the same issue addressed below:
I make or receive a phone call. No problems answering a phone call when it comes in. However when I hang up, the screen immediately goes back to sleep (which seems to be normal for the Nexus after researching). However, if I press the power button after the call is ended, the screen does not turn on at all. The hardware buttons (menu and back) do light up however and they remain lit. Regardless of what I do my phone stays stuck in this mode unless I hold the power button for about 10 seconds or so and force it to reboot, at which point it operates normal with no issues until my next phone call.
Has anyone experienced this issue and if so did you find a way to resolve it that does not require rebooting the phone? Right now this is the only thing keeping me from using the ROM as my daily driver.
Imo, AOSP-based ROMs run best when coming from stock. I flash back to touchwiz the before flashing them. Not sure if you've tried this.
Also, I had some small issues with the exact same rom that kept me from making it my daily driver. If you want stability, I can vouch for AOKP 4.1.2. I'm in no hurry for 4.2 with this rom running so well with no bugs or glitches
xBeerdroiDx said:
Imo, AOSP-based ROMs run best when coming from stock. I flash back to touchwiz the before flashing them. Not sure if you've tried this.
Also, I had some small issues with the exact same rom that kept me from making it my daily driver. If you want stability, I can vouch for AOKP 4.1.2. I'm in no hurry for 4.2 with this rom running so well with no bugs or glitches
Click to expand...
Click to collapse
Thanks. Seems that it was destined not to work. Oh well. I was on TW nearly everytime. I will give AOKP a shot. Should like it equally as well because I prefer AOSP roms. I am assuming you restore nandroid stock...or do you odin flash?
aybarrap1 said:
Thanks. Seems that it was destined not to work. Oh well. I was on TW nearly everytime. I will give AOKP a shot. Should like it equally as well because I prefer AOSP roms. I am assuming you restore nandroid stock...or do you odin flash?
Click to expand...
Click to collapse
I don't think it matters but I usually restore my tw/stock nandroid because it's right there and I don't lose root.
When I flashed the rom im currently running, I formatted /system /data and battery. Not sure if you care or need that info, just passing it on as this device has run really well for me on this OS.
I also flashed the Nexus 4 camera/gallery and the TW clock. The aokp camera is lame-o, and controlling the alarms is easier on the TW clock.
If you can't find them on the forum here (where I got them), PM me your email and I will send you the zips if you are interested. I believe I flashed them both in cwm, wiped cache/dalvik and then adjusted permissions in root browser to rw-r-r
AOKP's 4.1.2 jellybean milestone 1 is still on goo.im
xBeerdroiDx said:
I don't think it matters but I usually restore my tw/stock nandroid because it's right there and I don't lose root.
When I flashed the rom im currently running, I formatted /system /data and battery. Not sure if you care or need that info, just passing it on as this device has run really well for me on this OS.
I also flashed the Nexus 4 camera/gallery and the TW clock. The aokp camera is lame-o, and controlling the alarms is easier on the TW clock.
If you can't find them on the forum here (where I got them), PM me your email and I will send you the zips if you are interested. I believe I flashed them both in cwm, wiped cache/dalvik and then adjusted permissions in root browser to rw-r-r
AOKP's 4.1.2 jellybean milestone 1 is still on goo.im
Click to expand...
Click to collapse
I actually downloaded the camera/gallery apk for 4.2 as well as the keyboard. Already installed and running. Prefer both over the 4.1.2 versions installed on AOKP and CM10. Thanks for the info.
I have myself a Rogers based S3, that has the stock Jelly Bean OS on it.
Its bogged down, I don't like it anymore.
I have seen the OS on the Nexus unit's and find it to be WAY better (more fluid, more options and much better UI for texting)
Now for the explanation of this thread....
I have NO idea what I'm doing anymore when it comes to this phone. It's not rooted, NO CWM installed.. And i fear i may brick it if i don't know exactly what i'm doing.
That being said, i would like to go to a stock Google OS, or something very close to it.
What are my options? I would like to try and make this as pain free as possible. As far as i can recall, rooting//cwm and Os load on my captivate was really easy... This time around, i am finding way too many "possible" ways of doing everything. I think more or less, i need to be pointed to the right way so i don't get confused.
Anyone willing to toss me a hand on this one :fingers-crossed:
http://forum.xda-developers.com/showthread.php?t=2343223
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
saj222 said:
http://forum.xda-developers.com/showthread.php?t=2343223
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4
Click to expand...
Click to collapse
Instead of linking me to something I've already read, how about actually saying something.
I'm finding too many "this might work for rogers, this might not"
Last time i followed a tutorial meant for an AT&T unit, I hard bricked the phone, and ended up tossing it
Sorry if it was in the wrong section before Kenny.
How about me not responding at all next time? I know no one is forcing me but its simple enough to find this info by searching. I understand your hesitance... No one wants an expensive brick.
I'll put something together for you later today unless someone else beats me to it. Deal?
js593 said:
What are my options? I would like to try and make this as pain free as possible. As far as i can recall, rooting//cwm and Os load on my captivate was really easy... This time around, i am finding way too many "possible" ways of doing everything. I think more or less, i need to be pointed to the right way so i don't get confused.
Click to expand...
Click to collapse
Good thread to read: http://forum.xda-developers.com/showthread.php?t=1725839
First you need to get root. 2 easy ways here. First one is install a stock rooted ROM with Odin. Look for the Rogers image here: http://forum.xda-developers.com/showthread.php?t=1739426 Second one is to install CF-Root with Odin, here: http://forum.xda-developers.com/showthread.php?t=1963790 Make sure to get the one for I747M. Second option is faster b/c the zip is way smaller. Now you have stock root.
Next get GooManager https://play.google.com/store/apps/details?id=com.s0up.goomanager&hl=en. Run it, press menu and then install open recovery script or something like that. It will install TWRP custom recovery. Now you can flash ROMs. Perform Nandroid backup before commencing flashing.
For a pure Google like experience, give Slimrom or AOKP (Task650) a try. Very stable.
Slim - http://forum.xda-developers.com/showthread.php?t=2085739
AOKP - http://forum.xda-developers.com/showthread.php?t=1766684
Dandroid is the latest stock themed to the hilt like Cyanogenmod. Very stable.
Dandroid - http://forum.xda-developers.com/showthread.php?t=2121506
saj222 said:
Good thread to read: http://forum.xda-developers.com/showthread.php?t=1725839
First you need to get root. 2 easy ways here. First one is install a stock rooted ROM with Odin. Look for the Rogers image here: http://forum.xda-developers.com/showthread.php?t=1739426 Second one is to install CF-Root with Odin, here: http://forum.xda-developers.com/showthread.php?t=1963790 Make sure to get the one for I747M. Second option is faster b/c the zip is way smaller. Now you have stock root.
Next get GooManager https://play.google.com/store/apps/details?id=com.s0up.goomanager&hl=en. Run it, press menu and then install open recovery script or something like that. It will install TWRP custom recovery. Now you can flash ROMs. Perform Nandroid backup before commencing flashing.
For a pure Google like experience, give Slimrom or AOKP (Task650) a try. Very stable.
Slim - http://forum.xda-developers.com/showthread.php?t=2085739
AOKP - http://forum.xda-developers.com/showthread.php?t=1766684
Dandroid is the latest stock themed to the hilt like Cyanogenmod. Very stable.
Dandroid - http://forum.xda-developers.com/showthread.php?t=2121506
Click to expand...
Click to collapse
Thank you very much. I';ll be looking this over and attempting this tonight.
js593 said:
I have myself a Rogers based S3, that has the stock Jelly Bean OS on it.
Its bogged down, I don't like it anymore.
I have seen the OS on the Nexus unit's and find it to be WAY better (more fluid, more options and much better UI for texting)
Now for the explanation of this thread....
I have NO idea what I'm doing anymore when it comes to this phone. It's not rooted, NO CWM installed.. And i fear i may brick it if i don't know exactly what i'm doing.
That being said, i would like to go to a stock Google OS, or something very close to it.
What are my options? I would like to try and make this as pain free as possible. As far as i can recall, rooting//cwm and Os load on my captivate was really easy... This time around, i am finding way too many "possible" ways of doing everything. I think more or less, i need to be pointed to the right way so i don't get confused.
Anyone willing to toss me a hand on this one :fingers-crossed:
Click to expand...
Click to collapse
I'm using Task650 4.2.2. on my Rogers device and IMO it's the best out there. Never bricked my phone and smooth as butter.
thecoach1999 said:
I'm using Task650 4.2.2. on my Rogers device and IMO it's the best out there. Never bricked my phone and smooth as butter.
Click to expand...
Click to collapse
Hey guys.
So i got the phone rooted, and TWRP is installed. I have a NANDROID backup already done, but i'm a little confused on the roms. Could someone help me with this?
Last i recall, the roms were a single file, Ive downloaded the AOKP JB in this thread http://forum.xda-developers.com/showthread.php?t=1766684 but i'm confused on how to install the rom (as its a .zip file, there's multiple files in the folder....)
Thank in advance!
Edit - I tried to flash the rom anyways, and AOKP one Failed and turned up with an error. It comes up saying "Error executing updater binary in zip "
Edit2 - I just managed to flash Dandroid to the S3, but apps are failing to load everywhere. Unsure if this is something to do with the network or anything, but im also not getting LTE with Rogers.... Play store wont connect either (and i did to the Gapps update...?)
js593 said:
Hey guys.
So i got the phone rooted, and TWRP is installed. I have a NANDROID backup already done, but i'm a little confused on the roms. Could someone help me with this?
Last i recall, the roms were a single file, Ive downloaded the AOKP JB in this thread http://forum.xda-developers.com/showthread.php?t=1766684 but i'm confused on how to install the rom (as its a .zip file, there's multiple files in the folder....)
Thank in advance!
Edit - I tried to flash the rom anyways, and AOKP one Failed and turned up with an error. It comes up saying "Error executing updater binary in zip "
Edit2 - I just managed to flash Dandroid to the S3, but apps are failing to load everywhere. Unsure if this is something to do with the network or anything, but im also not getting LTE with Rogers.... Play store wont connect either (and i did to the Gapps update...?)
Click to expand...
Click to collapse
Before flashing you need to wipe. Data, system, dalvik and cache. Oh and before this put the new ROM files and anything you want to keep like pics on the external sdcard.
Do you have an updated bootloader? http://forum.xda-developers.com/showthread.php?t=2321310
Try re downloading the AOKP ROM and flash the while thing (the .zip). Then flash the gapps. You may have a bad download the first time.
With non-touchwiz ROMs you need to install the ROM and gapps. Do not install any gapps with dandroid.
saj222 said:
Before flashing you need to wipe. Data, system, dalvik and cache. Oh and before this put the new ROM files and anything you want to keep like pics on the external sdcard.
Do you have an updated bootloader? http://forum.xda-developers.com/showthread.php?t=2321310
Try re downloading the AOKP ROM and flash the while thing (the .zip). Then flash the gapps. You may have a bad download the first time.
With non-touchwiz ROMs you need to install the ROM and gapps. Do not install any gapps with dandroid.
Click to expand...
Click to collapse
I believe i ran into the issue blindly.
I forgot to update the bootloader before flashing it. Will try again when i get home and report back with anything.
..
fffft said:
If that sorts your issues, then call it done and thank the people that helped you.
The earlier suggestions were good and not to be faulted. However there is more than one way to do most things. So if you are not happy for whatever reason here is a slightly different approach. There are some very stable custom ROMs that are very snappy and have a similar no lag, fluid feel (Google calls this "butter") to them vis a vis the Nexus. So a simple approach to that result would be:
1. Download and install the Samsung S3 V7.0 toolkit (program)
2. Start the toolkit program
Choose "n" when asked if you want to update the program
Choose your phone version. This is probably "53" for you
Choose option #1 from the main menu to install the necessary USB driver to your PC
After the driver is installed, connect your phone to your PC with the Samsung USB cable.
If your phone is currently stable, you can skip steps #3 + 4.
If you are uncertain, then steps #3 + 4 will restore a stock Rogers firmware as a starting point:
3. Go to Samsung updates and download a stock Rogers firmware
4. Install the stock firmware. This is toolkit menu option #8, 4, 2
5. Download the custom Wicked Aroma ROM v10 (main thread here)
6. Copy the Wicked Aroma ROM to your phone. You can do this in windows by going to file manager and drag and drop the Wicked file (leave it zipped) on the "Samsung Mobile MTP Device - Phone/Data" folder icon.
7. Flash the Wicked ROM from "recovery mode"
Ensure that your battery is at least 80% charged. Then turn your phone off and disconnect the USB cable
Push and hold the home button, volume up and power button at the same time until you feel the phone vibrate and see blue text on screen in the upper left hand corner. Then release the buttons.
On the onscreen phone menu, choose wipe (factory reset)
Then choose install and select the Wicked_v10. zip file
The rest of the install will be automated on your phone screen. It will ask you to select a number of options. If you are uncertain, then just leave them at the default settings. Ensure that you leave the wipe cache setting as is when asked. And I'd recommend the stock theme and stock kernel to start. The rest you can leave as is or change to what sounds attractive to you.
Note that the wicked ROM will change your boot splash screen. Most people won't care and it's not that hard to revert if you don't like the logo for some reason. This is the logo that appears for a few seconds when you first power up a phone.
This is a very snappy, pretty much zero lag and stable ROM. I think that you'd like it.
.
Click to expand...
Click to collapse
Thanks for the lengthy reply.
I tried putting the new bootloader on there, and tried re-flashing, but it did the same thing. So, in the mean time i'm going to use the Dandroid rom (didn't install the Gapps) and it seems to be working okay. I just fear a bit as the phone seems to be running much warmer then it usually does....
In the mean time, ill use this one, and see if it makes a difference (it could still be loading all my settings and whatnot, so we'll see what happens. I love the look of this rom though. Very simple, very clean. Exactly what i was looking for. Those samsung stock themes are terrible.... Thanks a bunch for the help people. Greatly appreciate it!
Personal taste varies a lot and there are a lot of themed ROMs on this site. So you should be able to find something that you like. It sounds like you want something snappy and Spartan looking. If you like your results so far, then no need to go any further.
If you end up trying the Wicked ROM, perhaps choose the Miui or Holo launcher and ASOP lock screen options.
There are an endless variety of home screen themes to be discovered. And no way to know what you might like. A few random screen shots:
http://media02.hongkiat.com/cool-android-homescreens/Clood.jpg
http://media02.hongkiat.com/cool-android-homescreens/evening.jpg
http://main.makeuseoflimited.netdna-cdn.com/wp-content/uploads/2012/09/jb_holo_launcher.jpg
http://i380.photobucket.com/albums/oo248/jb-dan/DroidInc/d4281332.jpg
http://mycolorscreen.com/wp-content/uploads/homescreens_2012/270592/KLPOS7.png
http://desktopspotting.com/wp-content/uploads/2011/12/Minimal-Android-Home-screen.png
.
Just installed the Wicked rom on my S3. NICE! Need to play with the settings a bit to get it configured the way I like, but a definite keeper.
Very nice job.....Kudos!
What's up everyone? I am having a strange problem when trying to flash just about any kernel on my N7. While I'm not a developer or anything, I'm not new to flashing ROMs or Kernels by far. In fact, my love affair with smartphones began when I got an HTC Apache with Windows Mobile 5. Anyway, every time I try to flash a kernel, it will show successful, and then the phone will boot into a fuzzy/pixelated light blue screen. Eventually, this screen will go away and my device will be pretty much locked up. All the images will have turned blue and orange, and the only way for me to get back into recovery will be to hold volume down + power, until the phone shuts off. The only kernel I have had any success with is Glitch, and I have even had this happen with it a couple times.
I always make sure to read through the instructions, and have done lots of searching here, and via Google. After I flash a rom, I will make sure the N7 boots up, and works properly, then reboot into recovery, do a full wipe, and flash the zip from TWRP. My most recent attempt was with Buttered AOKP w/Aroma installer. It walks you through the steps in a manner that should make this easy for anyone. It give you the option to wipe cache and kernel, which I always do, but no go. The only way I can get Glitch to run on it, is to complete the whole process twice.
Sorry if the answer is right under my nose, but I couldn't take it anymore and had to ask. I've never once bricked a device, nor have I had issues flashing kernels on any device before. Somebody please restore my sanity!!! I didn't have much to begin with.
yamus08 said:
What's up everyone? I am having a strange problem when trying to flash just about any kernel on my N7. While I'm not a developer or anything, I'm not new to flashing ROMs or Kernels by far. In fact, my love affair with smartphones began when I got an HTC Apache with Windows Mobile 5. Anyway, every time I try to flash a kernel, it will show successful, and then the phone will boot into a fuzzy/pixelated light blue screen. Eventually, this screen will go away and my device will be pretty much locked up. All the images will have turned blue and orange, and the only way for me to get back into recovery will be to hold volume down + power, until the phone shuts off. The only kernel I have had any success with is Glitch, and I have even had this happen with it a couple times.
I always make sure to read through the instructions, and have done lots of searching here, and via Google. After I flash a rom, I will make sure the N7 boots up, and works properly, then reboot into recovery, do a full wipe, and flash the zip from TWRP. My most recent attempt was with Buttered AOKP w/Aroma installer. It walks you through the steps in a manner that should make this easy for anyone. It give you the option to wipe cache and kernel, which I always do, but no go. The only way I can get Glitch to run on it, is to complete the whole process twice.
Sorry if the answer is right under my nose, but I couldn't take it anymore and had to ask. I've never once bricked a device, nor have I had issues flashing kernels on any device before. Somebody please restore my sanity!!! I didn't have much to begin with.
Click to expand...
Click to collapse
Flashing a CAF kernel on an aosp Rom or a aosp kernel on a CAF Rom. What Rom are you on? (cynanogen based roms are CAF)
Sent from my Nexus 7 using Tapatalk 4
xfrancis14 said:
Flashing a CAF kernel on an aosp Rom or a aosp kernel on a CAF Rom. What Rom are you on? (cynanogen based roms are CAF)
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Currently on: [ROM] Buttered Flo AOKP 4.3.1 [+Aroma] [2013-10-12]
It has all the kernels built into the aroma installer, so I would assume they are all compatible. Some more than others.
I got 3.4.1 Glitch-Flo to run on it, but had to return phone to stock, and flash twice, to get it to work. The aroma installer also has the option to use Faux Kernel in one of three flavors. I tried the "Ultra CCCCCCOMBO" first, and then the "Enhanced Stock", but no go.
When I go to the thread for both kernels, it says they are CAF kernels, but it's kind of strange they they would be included as an option in the rom. I have tried a few other roms, with various kernels too, and not had any luck. I want to get a log to post, but I'm not sure if I will be able to pull it via ADB, when the device is pretty much unresponsive.
Thanks for your response, and let me know if what you think about the CAF kernels being inlcuded with the AOKP rom.
Thanks,
Yam
Sooooo..... Isn't aokp based of the cm kernel? If that's the case, any of the kernels I am trying should work. I would post this in the ROM thread, but its happened with just about every ROM kernel combination in have tried. What's the dealio
Any update on this? I am having the exact same problem with my Nexus 4 running ProBAM 2.0 ROM. I have tried flashing every kernel and every version possible and it either freezes before boot (Google logo) or I get the blue screen... help anyone? I really want to flash a kernel with FauxSound, that's really all I want. Thanks so much!
Hello,
I've read through the Everything thread on Development, as well as searched using the xda search and google site search, but come up with nothing.
The Everything thread mentions that the current version of CWRM won't charge when the phone is off or in recovery, but I can't find anything about which version is the 'latest' (6.0.1.2, 5.0.2.7), nor if this also affects the TWRP recoveries (2.6.3, 2.4.1)? For that matter, I can't find anything that even mentions the charging problems at all aside from the Everything thread!
If there is a charging problem with all of the third party ROMs, is there a method to go back to the stock recovery after flashing in a ROM and backing up /efs/? I'm basically shooting for a fully functional phone and I don't plan on changing ROMs all over the place, just root and ICS.
Help?
Thanks!
TooG435 said:
Hello,
I've read through the Everything thread on Development, as well as searched using the xda search and google site search, but come up with nothing.
The Everything thread mentions that the current version of CWRM won't charge when the phone is off or in recovery, but I can't find anything about which version is the 'latest' (6.0.1.2, 5.0.2.7), nor if this also affects the TWRP recoveries (2.6.3, 2.4.1)? For that matter, I can't find anything that even mentions the charging problems at all aside from the Everything thread!
If there is a charging problem with all of the third party ROMs, is there a method to go back to the stock recovery after flashing in a ROM and backing up /efs/? I'm basically shooting for a fully functional phone and I don't plan on changing ROMs all over the place, just root and ICS.
Help?
Thanks!
Click to expand...
Click to collapse
I think something like 6.0.4 the latest CWMR. ( you can build with http://builder.clockworkmod.com/ , Existing Device option doesnt work)
It charges in latest TWRP, you can see "+" char when on charge next to the battery level.
Stock uses recovery for official upgrade, and factory reset. We have only offline charge issue, but recovery has no effect on it. Offline charger works with a limitation. I wouldnt bother you with the explanation, since you said you would like to use stock ICS.
You can backup efs in rooted rom without recovery. You can always flash recovery with odin phone in download mode.
Thanks.
I guess I had assumed the comment was referring to the builds in the Development forum, not the overall CWMR project! Is there a currently recommended recovery, or is it a toss up to personal preference? I'm not so much tied to ICS as tied to a completely working ROM - especially as I see all the bluetooth and skype issues with the JB ROMs, which (as far as I can tell) are still unresolved / unknown?
TooG435 said:
Thanks.
I guess I had assumed the comment was referring to the builds in the Development forum, not the overall CWMR project! Is there a currently recommended recovery, or is it a toss up to personal preference? I'm not so much tied to ICS as tied to a completely working ROM - especially as I see all the bluetooth and skype issues with the JB ROMs, which (as far as I can tell) are still unresolved / unknown?
Click to expand...
Click to collapse
I make TWRP for i927, we dont have other up to date, but you can build yourself.
Dont you have issue with stock ICS? I made up to date issue list in me CM 10.2, you could decide it suit for you or not, you may know stock limitation already.
I hope voip issue would be resolved soon.
bubor said:
I make TWRP for i927, we dont have other up to date, but you can build yourself.
Dont you have issue with stock ICS? I made up to date issue list in me CM 10.2, you could decide it suit for you or not, you may know stock limitation already.
I hope voip issue would be resolved soon.
Click to expand...
Click to collapse
My only real requirement in a phone is that it be reliable - I don't want to have to pop out batteries or have no audio on calls if I get stranded in the middle of nowhere. At this point, my phone is still in the mail - got a used one from a friend, but it hasn't arrived, so I haven't had much ability to experiment yet.
My Android experience is exclusively with a Transformer TF101, which had 4.0.4 ICS stock and is currently running Katkiss JB 4.2.2_226 (Katkiss 4.3 isn't stable enough for me yet, was getting daily crashes last time I tried). All of the phone components are new to me - and the Glide seems to have a more fragmented recovery scene than the TF101, which is pretty much TWRP or nothin'
Thanks again for your help!