Well, it won't let me post in the official thread so I'm forced to put it here.
I recently installed the Team EOS Jelly Bean nightly (Stingray MZ602) their gapps, and reflashed the ICS radio as recommended using Rogue Recovery. Things have been working well except the WiFi. It tends to cut out randomly. It will be connected yet not transmit or receive. I have to turn it off and on frequently in order for it to work. No, it's not the router or my network. I am hoping for a solution other than going back to ICS.
First thing I would do is to full wipe and format /system
And flash twrp recovery that is advised as stable flasher.
Then redownload the ROM and gapps and make sure check sum is OK,
Then flash and reboot.
This way, you would id the source of your issue, ROM bug or recovery flasher? Cuz I know other guys face no issues like yours with twrp. Worth to try. Good luck.
The twrp page hasn't been updated since April and the project itself hasn't been updated since October of 2011. How can you be sure that it'll work with the radio zip better than Rogue? Or even the Team EOS JB build?
Twrp is advised by team eos. They asked to use it. And you need twrp for Xoom,
http://forum.xda-developers.com/showthread.php?p=28988754
Installation method 4 thru goo manager.
I remember one of the stingray users had an issue with the radio flashing and it went great with twrp.
Good luck.
Didn't work. I still have to reset the WiFi every 5 minutes or so. Also, the twrp recovery takes a LOT longer to load than Rogue's. Almost thought it wasn't going to work for a bit until the 'curtain' finally rose.
Over 24-hour bump...
Just put on EOS 138 and reflashed the radios after going back to Rogue. Still radio issues with WiFi. Found some other threads detailing that Jelly Bean in general seems to have WiFi issues. As much as I hate it, I'm starting to think that I will have to 1) revert to ICS, 2) wait for an updated radio file, or 3) deal with it.
Wifi Issue
First Aid Computing said:
Just put on EOS 138 and reflashed the radios after going back to Rogue. Still radio issues with WiFi. Found some other threads detailing that Jelly Bean in general seems to have WiFi issues. As much as I hate it, I'm starting to think that I will have to 1) revert to ICS, 2) wait for an updated radio file, or 3) deal with it.
Click to expand...
Click to collapse
I always have that problem with their roms. Flash a kernel, thats always helped my situation.
Also I have zero issues with wifi on JB with my GNexus, N7, Infuse and Atrix. Its not JB, at least not as far as I have seen. Granted none are stock.
Which kernel would you recommend?
Also, until JB I have not had this issue with EOS builds.
issues
First Aid Computing said:
Which kernel would you recommend?
Also, until JB I have not had this issue with EOS builds.
Click to expand...
Click to collapse
I flashed Eos 138 last night (was on CNA), without doing the radios, nor a kernel, and didn’t have any problems.
The Eos forum states that it has the kernel baked into the rom, so flashing the kernel is likely redundant.
However, for ****s and giggles I tried flashing the Eos 3.0.15 kernel and it would not flash, but I was able to flash the Eos 3.0.5 kernel instead and it took. I haven’t seen any issues, either before or after the kernel flash, so perhaps you should try re-flashing the entire rom sans radios and see what happens.
One of the nice things about the Xoom is its pretty easy to fix anything you could do to it via ADB and fastboot, so try some different combos, or start all the way over (from stock). If that doesn’t help, try a different JB rom and see if you get the same problem.
Also make sure you are flashing the right rom, there are several variants for the Xoom - 3G, 4G, Euro, and of course wifi only.
Just flashed CM10 and the non-EOS gapps without flashing radios. Running on WiFi for about 20 minutes so far without issue. Will try more testing later today.
EOS 4 & Kindle
Thanks EOS for 4.2.1! Feels like most things are working...except Kindle locks up on start-up. Just sayin'....
Related
I have come to the conclusion that something is wrong with my phone. I have tried to install ICS....a lot. I am not exagerating when I say that I have tried every Odin install, and every ICS ROM that has more than a few positive results. Nothing will work. I am not new to flashing, I have had a Captivate, Inspire, Tab and have had no issues with those, even created a few themes and build.prop tweaks. I know what I am doing and I follow the OP instructions perfectly. The damn thing just wont take. I get the white Samsung screen, a black screen, a vibration, and a reboot. So at this point I think I am just going to stick with GB for right now and hope that either the offcial ICS update works (when available) or maybe 5.0 later this year.
Two weeks of try to make this work has run me ragged. Outside of the ICS issues though this is by far the best device I have had in terms of performance and reliablility.
Rant over.
Did u flash the uclc5 radio at any point in time?
If not what radio did u install, and did u install it before u flashed ics rom?
What recovery were u using?
Did u odin back stock in between each ics attempt? Did u use dark side wipe at all?
*#* Google dropbox, its useful.
https://www.dropbox.com/referrals/NTcwNDE0ODUyOQ *#*
icenight89 said:
Did u flash the uclc5 radio at any point in time?
If not what radio did u install, and did u install it before u flashed ics rom?
What recovery were u using?
Did u odin back stock in between each ics attempt? Did u use dark side wipe at all?
*#* Google dropbox, its useful.
https://www.dropbox.com/referrals/NTcwNDE0ODUyOQ *#*
Click to expand...
Click to collapse
I have not tried the uclc5 radio. I saw a bunch of posts about it being for the Note, however the ROMs I was looking at all used ucld2 and ucla4 radios, so that is what I have been trying. Even the ROMs with the radio included as part of the install didn't work. And yes, I installed the radios (when applicable) before attempting the ROM install.
Recovery is the same, most ROMs suggested a particular recovery and I attempted using the suggestion in each OP, then attempted with the newest recovery when they didn't work, so I bascially did each ROM I tried twice. I did flash back to stock before each attempt.
I do have the dark side wipe and ran it before every attempt, then followed the OP instructions to perform the normal wipe\format and dalvik wipes when directed.
What kills me is that I get the same bootloop when trying an Odin ICS. The only version of that I have not tried is the version that was extracted from the oneclick.
I even had problems getting a GB ROM to install. I did manage to get superlite 3.1 installed after several attempts. You better believe I have nandroid backups of this working install....in several places.
My other concern is that even when the official update gets pushed out that I won't be able to install that either.
I appreciate your suggestion to use uclc5 radio. If I try to install that I suppose I need to try and flash a ROM that does not come with a radio as part of the package?
lacer4576 said:
I have not tried the uclc5 radio. I saw a bunch of posts about it being for the Note, however the ROMs I was looking at all used ucld2 and ucla4 radios, so that is what I have been trying. Even the ROMs with the radio included as part of the install didn't work. And yes, I installed the radios (when applicable) before attempting the ROM install.
Recovery is the same, most ROMs suggested a particular recovery and I attempted using the suggestion in each OP, then attempted with the newest recovery when they didn't work, so I bascially did each ROM I tried twice. I did flash back to stock before each attempt.
I do have the dark side wipe and ran it before every attempt, then followed the OP instructions to perform the normal wipe\format and dalvik wipes when directed.
What kills me is that I get the same bootloop when trying an Odin ICS. The only version of that I have not tried is the version that was extracted from the oneclick.
I even had problems getting a GB ROM to install. I did manage to get superlite 3.1 installed after several attempts. You better believe I have nandroid backups of this working install....in several places.
My other concern is that even when the official update gets pushed out that I won't be able to install that either.
I appreciate your suggestion to use uclc5 radio. If I try to install that I suppose I need to try and flash a ROM that does not come with a radio as part of the package?
Click to expand...
Click to collapse
Personally, I haven't had anything but trouble with superdarkside. Its an excellent tool, but for me, hasn't meshed well with ICS. You should try following seans op for Sky ICS UCLC4, without using darkside at all to change from where your at now.
Also, the modem (aside from UCLC5 for some) has no effect on the installs, I sat on Sky ICS UCLC4 with the UCLC3 modem for a couple weeks without any issues at all.
I have tried all of the CWM mods posted here, and to be honest, my favorite is the CWM touch when installed from rommanager. Seans roms seem to take better with it more than the rest. The CWM touch that is posted on the sky UCLC4 OP is good, but it has a couple minor bugs.
Are you using SuperSU or superuser? Supersu has backfired on numerous occasions for me, I always stick to superuser (and I'm sure I'll be flamed for the comment. Every skyrocket reacts differently, remember)
mahausrath said:
Personally, I haven't had anything but trouble with superdarkside. Its an excellent tool, but for me, hasn't meshed well with ICS. You should try following seans op for Sky ICS UCLC4, without using darkside at all to change from where your at now.
Also, the modem (aside from UCLC5 for some) has no effect on the installs, I sat on Sky ICS UCLC4 with the UCLC3 modem for a couple weeks without any issues at all.
I have tried all of the CWM mods posted here, and to be honest, my favorite is the CWM touch when installed from rommanager. Seans roms seem to take better with it more than the rest. The CWM touch that is posted on the sky UCLC4 OP is good, but it has a couple minor bugs.
Are you using SuperSU or superuser? Supersu has backfired on numerous occasions for me, I always stick to superuser (and I'm sure I'll be flamed for the comment. Every skyrocket reacts differently, remember)
Click to expand...
Click to collapse
I will give it a shot. I would really like to get back to ICS, I got so used to it on my other phones.
I have been using superuser, haven't had a problem yet from that.
lacer4576 said:
I have not tried the uclc5 radio. I saw a bunch of posts about it being for the Note, however the ROMs I was looking at all used ucld2 and ucla4 radios, so that is what I have been trying. Even the ROMs with the radio included as part of the install didn't work. And yes, I installed the radios (when applicable) before attempting the ROM install.
Recovery is the same, most ROMs suggested a particular recovery and I attempted using the suggestion in each OP, then attempted with the newest recovery when they didn't work, so I bascially did each ROM I tried twice. I did flash back to stock before each attempt.
I do have the dark side wipe and ran it before every attempt, then followed the OP instructions to perform the normal wipe\format and dalvik wipes when directed.
What kills me is that I get the same bootloop when trying an Odin ICS. The only version of that I have not tried is the version that was extracted from the oneclick.
I even had problems getting a GB ROM to install. I did manage to get superlite 3.1 installed after several attempts. You better believe I have nandroid backups of this working install....in several places.
My other concern is that even when the official update gets pushed out that I won't be able to install that either.
I appreciate your suggestion to use uclc5 radio. If I try to install that I suppose I need to try and flash a ROM that does not come with a radio as part of the package?
Click to expand...
Click to collapse
I know this may be silly but have you tried to re-download the one click leak your using? Maybe you have a bad download or a corrupt file. And, or try to use a different usb port when you flash. It seems you've tried everything and maybe you have a defective device. I started having a lot of issues recently after going from ROM to ROM so I just flashed the one-click to get back to a clean state and then carefully chose which ROM I wanted to use and carefully install it. I've always used Darkside Superwipe but since I've quit using it, things have been much smoother. What I do now is what most Devs are saying now is to wipe/factory reset multiple times and format/system multiple times. If thats not working maybe go all the way back to stock GB with k0nanes stock tar and go from there. As far as the uclc5 radio, be careful!! I'm sure you've read that it can corrupt a partition and cause issues. I did flash it once and it did work for 48 hours but I noticed signal loss so I flashed back to uclc2. Maybe I got lucky it didn't mess me up, who knows? And if you have an issue not receiving an official update, IF you do go back to the stock GB tar, do a nandroid and flash that when it comes out. Just make sure you flash the stock recovery before you take it. I have a stock GB backup on my SD, so IF and WHEN it does come out, I'll just flash the backup, flash stock recovery and take the OTA. With your constant bootloops, it seems to me its a bad download or a defective device. It seems you've tried everything. Good luck...
^^^ this makes sense. Also I was asking about the note radio to advise u against it, or u may end up screwing up ur phone even worse, and have to make a visit to my corrupt efs fix thread lol.
hcyplr29 said:
I know this may be silly but have you tried to re-download the one click leak your using? Maybe you have a bad download or a corrupt file. And, or try to use a different usb port when you flash. It seems you've tried everything and maybe you have a defective device. I started having a lot of issues recently after going from ROM to ROM so I just flashed the one-click to get back to a clean state and then carefully chose which ROM I wanted to use and carefully install it. I've always used Darkside Superwipe but since I've quit using it, things have been much smoother. What I do now is what most Devs are saying now is to wipe/factory reset multiple times and format/system multiple times. If thats not working maybe go all the way back to stock GB with k0nanes stock tar and go from there. As far as the uclc5 radio, be careful!! I'm sure you've read that it can corrupt a partition and cause issues. I did flash it once and it did work for 48 hours but I noticed signal loss so I flashed back to uclc2. Maybe I got lucky it didn't mess me up, who knows? And if you have an issue not receiving an official update, IF you do go back to the stock GB tar, do a nandroid and flash that when it comes out. Just make sure you flash the stock recovery before you take it. I have a stock GB backup on my SD, so IF and WHEN it does come out, I'll just flash the backup, flash stock recovery and take the OTA. With your constant bootloops, it seems to me its a bad download or a defective device. It seems you've tried everything. Good luck...
Click to expand...
Click to collapse
I will try to get a different download, but I do not think that is it. The only reason I say that is because my phone had the exact same response for EVERY ROM I have download. They can't all be bad files. I have tried on two different PCs with three different USB cables. Good thought though, I have had bad downloads before. I am going to keep trying as the ROMs are updated and hope that I figure out what is going on, and hope that I can get the official update at some point. Then I will just root it and get rid of the bloat myself if I have to
I am going to stay away from the L5 radio, not worth the hassle.
On a side note, if installing a rom from the site, remember, most will work with the "base"
But need to reset/full boot before "updating".. dont just flash rom and flash update then reboot
I had a hard time with ICS as well with different problems, all I can say is it disproves the definition of insanity. Trying the same things over and over again will eventually make it work!
Hang in there, it's worth it. Whenever you do get the ODIN one click to work I highly recommend flashing Raider03's SMOOTHIE ROM. Awesome battery life and extremely "SMOOTH"! But be prepared for a few FCs and bugs with all of the ICS ROMS for now!
Just sharing my experience in upgrading to Jelly Bean on the Captivate.
Before you begin:
Before you begin, back up your efs partition.
Some ICS and JB ROMS have issues where they will forget your IMEI. If this is the case you'll need to restore your efs partition. If you don't already have a back up, you'll have to reflash to stock (pain in the butt) so that you can back up your efs so that you can restore it on your shiny new ROM. Without an IMEI, you won't be able to make calls or access wireless networks.
How to Backup/restore EFS: http://forum.xda-developers.com/showthread.php?t=859914
General Process
ICS and Jelly Bean are too big to put the entire rom in /system, so the current practice is to break up the ROM into 2 or more zip files (the ROM itself and a second zip that has essential apps like the Market). Both have to be flashed.
The ROMs have upgraded CWM (Recovery Modules) so you have to flash the ROM twice. The first time installs the CWM, the second time installs the ROM.
My journey
I had been using Mosaic, which is now defunct. When I started seeing posts from Studacris (former Mosaic developer) from several months ago saying "Gingerbread? What is this the stone age?" I decided perhaps is was time to upgrade to ICS.
Of course when I started looking at ICS ROMS, it turns out that now there are Jelly Bean ROMS available as well. Some people say the JB ROMS solve several problems with ICS. Others say the ICS are more stable for now.
Moral of the story. Your Captivate is unique. You won't know which is which until you try them, but my journey may help you.
1. I want to try Slim Bean, but coming from Gingerbread, it's recommended to start on Cynanogen (CM)
2. So I might as well try CM, but do I try CM9 (ICS) or CM10 (JB)?
3. Ah what the heck, let's go CM10!!!
4. Okay, there's at least four versions. The official, three unofficials of varying "v" releases, the Devil version with datadata (what the heck is datadata?), some guy's custom rolled ROM which he says is likely to brick your phone.
5. Okay, I'll try the latest V8 version with the Devil kernel (note, you should use the version with datadata).
6. Flash goes fine, but now it hangs on black screen with the word Android. After 30 minutes, I figured it really was hanged. Reflashing and rewiping solved that problem.
7. I had a lot of issues with it (see below), so I decided to try Slim ICS.
8. I had other issues with SlimICS (see below), so what the heck, let's try Slim Bean.
9. Slim Bean seems like a keeper to me: Fast; great feautures; decent launcher (vastly better than SlimICS). Only real problem I'm finding is that the Market won't let me install (or even see) Astro Player, which is one of my absolute must have apps. Still trying the dev's workaround.
CM 10 Issues:
Outdated:
1. The home key and back key are reversed.
2. My IMEI was wrong, and restoring EFS didn't help
3. I experienced intermittent lag on the launcher
Update CM10
Everything works fine in CM10 Helly Bean (29.07.2012). Faster than Slim.
http://forum.xda-developers.com/showthread.php?t=1783064.
Slim ICS Issues
The first thing the Slim ICS installer does is install its own CWM and in the process it will erase your sdcard (internal memory)
SO....
1. Back up your internal SDCARD before you start
2. To save time, put the zip files on your external card also (the newer CWM will let you install from the external card)
3. I hate the launcher
4. I still couldn't make phone calls.
Slim Bean issues
Works great except for the market issue. Seems to be a problem with the DPI. Still waiting to see if it resolves. Alternatively, I could try to restore my Mosaic version of Astro Player with Titanium back up.
Update:
1. Market issue resolved after about 36 hours of following the fix on the website.
2. Internal card and sdcard were reversed, (/sdcard and /emmc)
Conclusion
I hope my journey helps someone out there.
patrokov said:
Slim Bean issues
Works great except for the market issue. Seems to be a problem with the DPI. Still waiting to see if it resolves. Alternatively, I could try to restore my Mosaic version of Astro Player with Titanium back up.
Click to expand...
Click to collapse
Apps still aren't showing up in the market, but the TiBu restored apps work fine.
patrokov said:
Slim ICS Issues
The first thing the Slim ICS installer does is install its own CWM and in the process it will erase your sdcard (internal memory)
SO....
1. Back up your internal SDCARD before you start
2. To save time, put the zip files on your external card also (the newer CWM will let you install from the external card)
3. I hate the launcher
4. I still couldn't make phone calls.
Click to expand...
Click to collapse
I initially had that issue of not being able to make any calls. I didn't even have ANY service. Then I went to check which baseband/modem I had and sure enough I found the rom didn't flash a modem. I had to go find one and flash it. After that it worked perfectly.
I also didn't like the new Lightning Launcher so I went back to the old launcher they used - Zeam Launcher.
Ravenmtx said:
I initially had that issue of not being able to make any calls. I didn't even have ANY service. Then I went to check which baseband/modem I had and sure enough I found the rom didn't flash a modem. I had to go find one and flash it. After that it worked perfectly.
I also didn't like the new Lightning Launcher so I went back to the old launcher they used - Zeam Launcher.
Click to expand...
Click to collapse
Which modem did you end up flashing?
CM 10 Issues:
1. The home key and back key are reversed.
2. My IMEI was wrong, and restoring EFS didn't help
3. I experienced intermittent lag on the launcher
Click to expand...
Click to collapse
1 sounds like you did not flash a proper kernel
2 no imei troubles here
3 NO LAG WHAT SO EVER
CheesyNutz said:
1 sounds like you did not flash a proper kernel
2 no imei troubles here
3 NO LAG WHAT SO EVER
Click to expand...
Click to collapse
CM10 comes with the Devil kernel. Flashing another kernel is not part of their installation instructions.
patrokov said:
CM10 comes with the Devil kernel. Flashing another kernel is not part of their installation instructions.
Click to expand...
Click to collapse
It does, but it depends on who ports or where did you get your CM10 rom. That problem you stated occurs when you flash a i9000 devil kernel for what I know. Jelly bean in cappy needs the devil version that has datadata on its filename either VC or CMC. Visit the Hell Bean Thread.
patrokov said:
Which modem did you end up flashing?
Click to expand...
Click to collapse
I tried most of them. I live in the Washington DC area and I found the latest XXJVU worked best for me. You'll just have to find out which one works best for you.
takeoutttt said:
It does, but it depends on who ports or where did you get your CM10 rom. That problem you stated occurs when you flash a i9000 devil kernel for what I know. Jelly bean in cappy needs the devil version that has datadata on its filename either VC or CMC. Visit the Hell Bean Thread.
Click to expand...
Click to collapse
I flashed the CM10 that was to be renamed Helly Bean, following these directions: http://hellybean.site11.com/help.html
(at the time the url was something like cm10.site11.com but the directions are the same.)
takeoutttt said:
It does, but it depends on who ports or where did you get your CM10 rom. That problem you stated occurs when you flash a i9000 devil kernel for what I know. Jelly bean in cappy needs the devil version that has datadata on its filename either VC or CMC. Visit the Hell Bean Thread.
Click to expand...
Click to collapse
Exactly
Sent from my SGH-I897 using Tapatalk 2
CheesyNutz said:
Exactly
Sent from my SGH-I897 using Tapatalk 2
Click to expand...
Click to collapse
takeoutttt said:
It does, but it depends on who ports or where did you get your CM10 rom. That problem you stated occurs when you flash a i9000 devil kernel for what I know. Jelly bean in cappy needs the devil version that has datadata on its filename either VC or CMC. Visit the Hell Bean Thread.
Click to expand...
Click to collapse
This is what I originally flashed and had all the issues with. Is this the wrong one?
http://rootaxbox.no-ip.org/divers/devil_jellybean/rom/v8/
Tonight I flashed this one, and everything works perfectly.
http://rootaxbox.no-ip.org/divers/devil_jellybean/rom/20120729/
The reason I ask is that I'm trying to find out whether it was my error or some weirdness on my cappy's part.
patrokov said:
I flashed the CM10 that was to be renamed Helly Bean, following these directions: http://hellybean.site11.com/help.html
(at the time the url was something like cm10.site11.com but the directions are the same.)
Click to expand...
Click to collapse
I don't personally recommend that page because it was not actually tested yet by porters it means that the file in that site was raw JB. Recently derteufel uploaded a version that is "busted". So I would suggest to pay a visit to the HellBean thread and test a version that has already ported.
I just installed the stable CM9 and I don't really like what I am seeing. The lag on the home screen is unbearable and sometimes the notification bar splits into two when I am pulling it down. I will definitely try a CM10 rom and see how well it functions but I want to use the most stable version, or better yet the one with the least issues that I can use as my day to day rom. I really don't want to go through the trouble of installing every single JB rom.
droyd666 said:
I will definitely try a CM10 rom and see how well it functions but I want to use the most stable version, or better yet the one with the least issues that I can use as my day to day rom. I really don't want to go through the trouble of installing every single JB rom.
Click to expand...
Click to collapse
I'd definitely recommend Helly Bean first, in that case.
helly bean all the way. the only problem i have with it is when flashing a new rom (whether its the same to re-flash or upgrading to latest) you lose google now.
I'm running the 8/11 build OF CM10 KANG builds "JELLYBRO" by Makelegs, it's running great! Here's the link below.
http://forum.xda-developers.com/showthread.php?t=1803709
Sent from my SGH-I897 using Tapatalk 2
Definitely Helly Bean. Make sure to do a solid master clear and format of your phone first, then flash the latest helly bean. Long time user of slimics then slimbean and just switched over.
Only jellybean rom I've found that works FAST right out of the box, and even better when changing a few settings with devil kernel config. Only rom in which devil config settings actually stick after reboot as well!
VashTS said:
helly bean all the way. the only problem i have with it is when flashing a new rom (whether its the same to re-flash or upgrading to latest) you lose google now.
Click to expand...
Click to collapse
Not if you flash the add-on like you are supposed to...
Sent from a jelly bean
So far the latest cm9 nightly is the only ics that has worked well for me. All the jb roms I tried have me a lot of issues (sd card switch, no modem-couldn't even flash a modem, etc) so I haven't built up the confidence to try again.
My problems aren't with ROM behavior, but rather the newer versions of system apps. The phone app on gb had a feature at the end of a phone call to redial or text the person you just called. Miss that. Also the clock app doesn't have the world clock. Not a fan of that one. Over all everything is smooth but a lot of features I had with apex 12 are greatly missed.
Sent from my SGH-I897 using xda premium
simple man said:
I'm running the 8/11 build OF CM10 KANG builds "JELLYBRO" by Makelegs, it's running great! Here's the link below.
http://forum.xda-developers.com/showthread.php?t=1803709
Sent from my SGH-I897 using Tapatalk 2
Click to expand...
Click to collapse
I also applaud jellybro on my phone and flash each day with new builds as they come. Remeber to have a quick read thro the cherry picks to see what was changed/added/fixed. Runs great!
I do use the devil kernel with it tho - http://rootaxbox.no-ip.org/derteufel/jellybean/Cappy/113/. I use the CMC one.
Matt/eg.
So I have a little bit of a strange issue.
I had flashed the AOKP Milestone 5 on my TF, and although I managed to fix the CWM bootloop, it doesn't appear I'm able to install any other ROM.
Since I've flashed it, any other ROM I attempt to flash either fails to complete it's first boot (watched a few different ones try for hours yesterday) or wifi will not turn on. The wifi issue is also present in my backup from stock.
Perhaps for the ROMs that are booting for me there is a different kernel I may have better luck with? Thoughts, anyone?
frankxanders said:
So I have a little bit of a strange issue.
I had flashed the AOKP Milestone 5 on my TF, and although I managed to fix the CWM bootloop, it doesn't appear I'm able to install any other ROM.
Since I've flashed it, any other ROM I attempt to flash either fails to complete it's first boot (watched a few different ones try for hours yesterday) or wifi will not turn on. The wifi issue is also present in my backup from stock.
Perhaps for the ROMs that are booting for me there is a different kernel I may have better luck with? Thoughts, anyone?
Click to expand...
Click to collapse
What recovery are you using? might pay to try another (Recommended: http://forum.xda-developers.com/showthread.php?t=1759452)
You may want to obtain a kernel compatible with the ROM you want to try and flash both the ROM and kernel at the same time. The wrong kernel could definitely cause both the booting problems and the wifi not turning on.
I think about a kernel problem too, go to your ROM thread and you'll see the best kernel to flash with it...
I love Cyanogenmod, very much so. I downloaded the stable 10.1 build for my phone and it was mostly rock solid. When 10.2.1 come around I was pumped. I downloaded it and immediately encountered force closes out the bum. I switched back and a month later tried again. It was a slightly better experience as I realized I forgot to flash the 4.3 Gapps with my original attempt, but force closes cluttered my screen daily. I want to be able to upgrade, but the ROM just seems completely unstable for my phone. Has anyone experienced these things on their phone? Has anyone fixed these problems? Can anyone recommend the most stable and most up-to-date ROM even though stable and up-to-date rarely go hand in hand.
stjake said:
I love Cyanogenmod, very much so. I downloaded the stable 10.1 build for my phone and it was mostly rock solid. When 10.2.1 come around I was pumped. I downloaded it and immediately encountered force closes out the bum. I switched back and a month later tried again. It was a slightly better experience as I realized I forgot to flash the 4.3 Gapps with my original attempt, but force closes cluttered my screen daily. I want to be able to upgrade, but the ROM just seems completely unstable for my phone. Has anyone experienced these things on their phone? Has anyone fixed these problems? Can anyone recommend the most stable and most up-to-date ROM even though stable and up-to-date rarely go hand in hand.
Click to expand...
Click to collapse
Look in the CM11 thread, the nightlies are pretty stable for the most part and most us using it use it as a daily driver. You MUST perform a full wipe when installing a ROM, even when moving between point releases. If not, you'll encounter problems. GApps must also be flashed after the ROM has been flashed (assuming you want to use Google)
CWGSM3VO said:
Look in the CM11 thread, the nightlies are pretty stable for the most part and most us using it use it as a daily driver. You MUST perform a full wipe when installing a ROM, even when moving between point releases. If not, you'll encounter problems. GApps must also be flashed after the ROM has been flashed (assuming you want to use Google)
Click to expand...
Click to collapse
Yeah I figured that I need to wipe everything and install the proper GApps after my first attempt at 10.2 which to my credit I did do on my second try. Is there a particular nightly release that seems more stable than the rest? To put this in more context, I travel alone from college to various other places often a bit and my college is situated in almost a black hole of service for Verizon so I tend to take reliability over cutting edge even though I very badly want the newest and greatest. I'm on spring break so I'll try the newest nightly and back up my phone. Luckily I have a ton of space on my phone so I can always have a stable back up ready to be flashed on the fly.
stjake said:
Yeah I figured that I need to wipe everything and install the proper GApps after my first attempt at 10.2 which to my credit I did do on my second try. Is there a particular nightly release that seems more stable than the rest? To put this in more context, I travel alone from college to various other places often a bit and my college is situated in almost a black hole of service for Verizon so I tend to take reliability over cutting edge even though I very badly want the newest and greatest. I'm on spring break so I'll try the newest nightly and back up my phone. Luckily I have a ton of space on my phone so I can always have a stable back up ready to be flashed on the fly.
Click to expand...
Click to collapse
By their very nature, Nightlies are not considered stable in the strictest sense of the word. For most of us, they have been. But if you need reliability over cutting-edge, I'd stick with 10.2 or one of the CM11 Milestone builds (however, the RAZR HD only has one that I know of, CM11-M2).
My personal take is that given you're in an area with poor reception, choosing CM11 over CM10.2 (for example) wouldn't give you any better results over the other. Signal is signal.
My suggestion, given your circumstances and criteria, would be to stick with 10.2 but do a FULL backup via Recovery of your stock ROM (or whatever you're using instead of CyanognMod) and then do a FULL wipe of the following (and only these):
- user data
- /system partition
- /cache partition
- dalvik cache (usually found under Advanced in CWM recoveries)
Your phone will be in an unusable state after this. From here, still in Recovery, flash CM10.2 and then the appropriate GApps (make sure you choose the right one; a 4.4.2 GApps isn't suitable for a 4.3 OS) and reboot. If memory serves, CM10.2 is Android 4.3.1
If you're still having problems, you can restore your backup in Recovery or worst case, RSDLite the appropriate SBF for your phone to return to the carrier-stock ROM. But be aware if you chose the RSDLite path, you will lose everything. Basically it'll be like day-1 when you got the phone
Unroot help!!!
Hi I am trying to figure out how to unroot my Droid Razr HD...I bought it used from my buddy who upgraded and before we met up to make the deal I didn't know till after; that he rooted it and won't tell me how to unroot. I have only ever rooted one phone with his help and that was my thunderbolt. This phone is running CM 11-20140218-NIGHTLY-xt926. I want to bring it back to stock rom but have yet to find anyway to do that...it would be awesome if you guys could help me!!
Lanevox said:
Hi I am trying to figure out how to unroot my Droid Razr HD...I bought it used from my buddy who upgraded and before we met up to make the deal I didn't know till after; that he rooted it and won't tell me how to unroot. I have only ever rooted one phone with his help and that was my thunderbolt. This phone is running CM 11-20140218-NIGHTLY-xt926. I want to bring it back to stock rom but have yet to find anyway to do that...it would be awesome if you guys could help me!!
Click to expand...
Click to collapse
Find the FXZ you want to flash and use RSD or House of Moto to flash it.
I have been running CM 11 for quite a while now on my Nexus 5 and I always have been having signal issues where it would drop consistently and with the data not working despite having a connection. Also, I would get LTE signal sometimes but data would not work. These issues were not present when I installed stock Android or even some other ROMs but I really like CM and wanted to stick to it. I was experimenting around today and for the last 6 hours I have not had any issues yet so I wanted to share this with others in case they are in a similar situation. I did these steps in order.
1) Wipe clean your entire phone. Philz recovery helps here as it can be done in 1 step.
2) Install the latest CM nightly OR latest snapshot. I am personally running todays nightly (12/11/14)
3) Install a custom kernel. I have read around the forums that sometimes the stock CM kernel gives issues so I installed the Chaos kernel which is the only CAF kernel I could find.
4) Flash Lollipops baseband. This here seems to have removed most of the problems. I flashed the m8974a-2.0.50.2.21 baseband.
5) Boot into the ROM and update the APN. Although CM usually picks up on APN settings I have noticed that the ones in by default weren't exactly the newest APNs I found on Google. Update them and reboot again.
* If you decide to install the Nigthtlies, keep in mind when you upgrade to the next newest Nightly you will have to flash the custom kernel again !
I did these steps and I am consistently getting 4-5 bars and in areas where there is LTE coverage my data is working fine. Hopefully at least 1 person can benefit from this !
Enjoy