I've been lurking on these forums a bit - trying to nerve myself up to install Jellybean. I'm a complete noob. (some Linux experience, curious about Android) Here's what I've picked up. (All measured relative to stock Froyo.) (And I like to fiddle, but I also love my Captivate-so I'm a bit nervous about this...)
Good stuff:
1. Jellybean is great, everything works. Helly Bean/Devil is probably a bit more stable than Cyanogenmod 10 right now. Phone, WIFI, Camera, Movie, Apps all work at the moment. ICS and Gingerbread were all appreciably laggy.
Iffy Stuff:
1. The GPS on anything but stock Froyo may behave a bit better, or not, as the Captivate GPS has hardware issues in addition to possible problems with stock Froyo.
Bad stuff
1. Encryption Unsuccessful: Jellybean is likely to share the 'Encryption Unsuccessful' bug with ICS on the Captivate. For some reason, ICS seems to handle SD access a bit differently than Froyo and this occasionally permanently borks the internal SD. It may occasionally bork an external SD, but that seems fixable so far. Someday, someone may figure out a fix, but don't count on it. For now, any Captive running ICS or later should expect to eventually lose the internal SD permanently.
2. IMEI: Something in the latest installs may result in replacement of my IMEI with a generic one. This will result in AT&T temporarily blocking my phone. This may be related to some custom roms and possibly some apps borking up the efs folder after something in the more recent Cyanogenmods sets the efs folder as R/W.
3. Bootloaders: If I bork up bootloader flashing, I can end up hard-bricked.
4. Sleep of death: Custom ROMs may aggravate a 'sleep of death' issue on older Captivates. Fortunately, I checked and my Captivate doesn't have this issue.
I'm wondering if the following sketch is workable and if I've left anything major out:
1. Backup phone thoroughly. Test backups.
2. Remove SIM card (or stay at home, AT&T simply doesn't pick up here anyways-)
3. Print out and follow one of the sensible guides for upgrading to Helly Bean/Devil Kernel. Use Heimdell - and - after the first time I flash new bootloaders - stop flashing new bootloaders. If I do hardbrick, I can most likely do a bit of soldering to do the unbrickable mod for recovery.
4. Disable access to internal storage and run from partitioned 64 GB external SD card chosen for fast R/W in small blocks (4k).
5. Check IMEI and fix access permissions to efs folder.
So, assuming that the above isn't completely idiotic...
1. How comparable (in terms of speed and stability) should I expect this setup to be? I'm particularly worried about running from a SD card. Most earlier recommendations have been to run from 16 GB SD cards, but I'd kind of like the extra storage. People who bork their internal SD cards seem to end up switching phones even after getting the external setup working and I'm wondering if external access is just unreasonably slow. Also, would 64 GB sizes result in ridiculous boot times or some sort of size limit?
2. Also, is Jellybean inherently laggy on a Captivate - or should it be comparable in responsiveness to Froyo?
3. If I do someday successfully bork my external SD card with an Encryption Unsuccessful message -what sort of information would be useful for me to provide?
4. I should expect a modest increase in setup time when flashing new roms (editing mounting information), but not that many other problems?
I would say you are over-thinking it.
Go here and follow the install instructions --> http://slimroms.nfye.eu/
No guts, no glory.
Sent from my SGH-I897 using xda app-developers app
Yeah I would agree that you're over thinking it. But there's nothing wrong with that. I remember being equally cautious and skeptical about flashing once, but luckily I had a knowledgeable friend to help me quite a bit.
You said you're on stock Froyo? Make sure you root, I don't think I saw that in any of your steps.
Honestly, if you follow the instructions to most ROMS you'll be fine. No need to worry so much. Especially once you do it once, you'll be MUCH more comfortable with flashing in the future. Maybe even watch a few youtube videos of people doing it! That always helps me. I'm more of a visual learner though.
But you're right, you do need to have a backup of your EFS folder, and taking your sim out would be best As far as performance vs froyo. Phenomenal. I've never had my cappy run this smooth, and you can thank project butter for that. Android lag is virtually gone
I was super nervous about rooting and going CM but it is the best decision you will ever make thats for sure. It has increased my phones speed enourmously and made it like a new phone, I would never run a phone on stock firware now lol. Why dont you just go with CM9 stabel release to start if you are nervous. My gf is still on CM9 and it is miles ahead of stock and essentially bug free
Slim ICS & Helly Bean
Yeah I would not go straight to Jelly Bean... try out ICS.
I have been using Slim ICS v4.2 as a daily driver for about a month now, no issues so far. Thank God, the Encryption Unsuccessful issue has not hit me yet. It seems to be random, so be careful. There are guides out there to get the phone running again, but those are for ICS. Not sure if they would work on JB.
Ice Cream Sandwich is much faster than stock 2.3.5 Gingerbread, don't know about 2.2 though. Though it does depend on what ROM you're using. I think the most popular ones are Slim, Team Nyx (ICSSGS?), CM9 and of course AOKP and MIUI (WeUI?). Jelly Bean ROMs include Helly Bean, Slim Bean, ParanoidAndroid, and CM10 nightlies (just off the top of my head, feel free to add to this guys).
I have not tried Jelly Bean yet as I am a bit apprehensive as well. I heard that Jelly Bean removes the datadata partition, and that screws things up going back to GB/ICS? Or maybe it screws up restoring Nandroids? Not sure. I mean, if I don't like Helly Bean, I want to comfortably be able to go back to Slim ICS. I think I will try a Jelly Bean ROM eventually but I may go back to ICS if it's slow/buggy/laggy. The developer of Helly Bean is DerTeufel, I know he's an amazing dev and more knowledgeable at this stuff than I will ever be, but I had a horrible experience using his Devil kernel with Slim ICS. Random reboots whenever I tried doing something "heavy" (like scrolling fast in browser). Semaphore kernel was better but it broke Maps and video playback. So I re-flashed the ROM and it's all good again.
And I like to fiddle, but I also love my Captivate-so I'm a bit nervous about this...
Click to expand...
Click to collapse
Yeah, same here, I just got it this year (2012) so I'll probably have it for a long time! Android has come so far though, it makes me jealous, and I want the latest Thank God this phone has gotten awesome support from developers, maybe we'll have Android 4.2 and - who knows? - a 5.0 ROM or two Maybe I should learn developing so I can make it myself.
__________________________________________
Edit:
run from partitioned 64 GB external SD card
Click to expand...
Click to collapse
Hmm, I thought Captivate only supports 32 GB? Maybe a custom ROM will support 64?
Just about any ROM in the development forum is going to be SO MUCH better than stock froyo.
I have enjoyed using slim ics and slim Bean. Both great roms..
Sent from my SGH-I897 using xda app-developers app
curiousgeo said:
So, assuming that the above isn't completely idiotic...
1. How comparable (in terms of speed and stability) should I expect this setup to be? I'm particularly worried about running from a SD card. Most earlier recommendations have been to run from 16 GB SD cards, but I'd kind of like the extra storage. People who bork their internal SD cards seem to end up switching phones even after getting the external setup working and I'm wondering if external access is just unreasonably slow. Also, would 64 GB sizes result in ridiculous boot times or some sort of size limit?
2. Also, is Jellybean inherently laggy on a Captivate - or should it be comparable in responsiveness to Froyo?
3. If I do someday successfully bork my external SD card with an Encryption Unsuccessful message -what sort of information would be useful for me to provide?
4. I should expect a modest increase in setup time when flashing new roms (editing mounting information), but not that many other problems?
Click to expand...
Click to collapse
I think the phone's internal memory is FINE. Just the internal SDcard is messed up. Since the system partition, and other OS files are in the internal memory, you should be fine with booting and speed. All that's messed up are the /data and /sdcard partitions.
Thanks to you all :good::good::good:- particularly the guy who mentioned that a 64 Gb card wouldn't work. (I'm not sure it wouldn't - since some threads sounded like they were able to get one working...but...realistically...I'm not close to filling up storage anyways.)
Rooting went smooth (One Click Root), backups are pretty smooth-still need to test them. (Titanium, Pro version, not because I need it...just the developer obviously put in a lot of work...) A 32 GB microSD card is on order - Sandisk ULT Class 10 - seems to have excellent noncontiguous read/write speeds. By the way, Amazon had much, much better prices than the local Best Buy.
Y'know, some people are pretty aggressive - that's great. Other people...read every thread on XDA regarding the encryption unsuccessful bug before rooting their phones. Yes. Sigh. It would have been more cost-effective to buy a new phone. I did learn a few things though.
I'm confused. For Captivates, I thought the OS was typically stored on the internal SD card? And the Encryption Unsuccessful Fixes I've seen amount to partitioning the external card, installing a rom on the external card, and modifying vold.fstab. Um...maybe I'll just install a file explorer and have a look. Need to pick a good one - want exploration and chmod. There doesn't seem to be an explicit guide to running Helly Bean from an external card, (unless my search foo fails me), so I'll need to figure something out.
Attached is a screenshot of several different folders in Root Browser. You can see all the different partitions.
The guy who made the guide for the Encryption Unsuccessful issue mentioned,
Your partitions for /data and /sdcard are no longer accessible.
Click to expand...
Click to collapse
So I guess that means everything else is fine? And I think you install the ROM from the external SD card, not on it.
Well I have been running helly bean with/Devil kernel and it is a bit laggy at frist, but it's all about getting the tweaks right in the devil configuration set-up. I would definitely suggest going through ICS, and not go straight to helly bean/ devil kernel. I would suggest doc's ICS V12, and get comfortable using that particular Rom with the icey glitch kernel before moving on to helly bean/ Devil kernel.
Sent from my SGH-I897 using xda premium
May i ask how did you tweak the Devil kernel and what are your settings? When I installed helly bean i found it lags quite a bit (even with lagfree governor), so i returned to cm9 (which is virtually lag free)
Sent from my SGH-I897 using xda app-developers app
Related
So we just bought a nook color and she is still new to it. Obviously, she reads lots of books and I... well, want to make this into a tab and play w/ it. She might want to do web browsing and install some games/apps, but primarily will be used as an e-reader.
What rom (if any) do you suggest I flash? Or will I be better off just rooting the device and leaving it as is (w/ market)? She has no patience for developmental stuff so looking for something stable but also something I can play with
stevedawg85 said:
So we just bought a nook color and she is still new to it. Obviously, she reads lots of books and I... well, want to make this into a tab and play w/ it. She might want to do web browsing and install some games/apps, but primarily will be used as an e-reader.
What rom (if any) do you suggest I flash? Or will I be better off just rooting the device and leaving it as is (w/ market)? She has no patience for developmental stuff so looking for something stable but also something I can play with
Click to expand...
Click to collapse
Root the Stock and leave it. its the most stable rom.
Make your own SD card, running Nookie Froyo or CyanogenMod. When you take the card out and reboot, her machine is completely back to normal, or so I'm told. You both get to have what you want.
I can run CM from SD card w/o rooting the device!? if so... sweet, I saw sum tuts but still educating myself. Rooting and leaving stock is also a good idea, however I heard B&N is able to update your device thus losing root... Is this true?
For her, it sounds like just rooting would be the best option, since it has the market, all of the B&N features, and is stable. As mentioned above, running a ROM from the sd card is a good option for you. After rooting it, you could format the sd card used to root, and then load a ROM such as CM7, Froyo, or Honeycomb from the SD card to play with.
This way, she has her mostly stock setup, and you have your tablet setup that you can load by just popping in the sd card and rebooting. When you're done playing with it, power down, pop the sd card out, reboot, and it's back to her setup.
If you do decide to run a ROM from the sd card, make sure to get at least a class 4 (sandisk class 4 4GB works well for me). Then, if you find something that would work for both of you, you could look at flashing to internal EMMC for better speed/performance. Another option is dual-booting between ROMs, which you can find more about in the development section.
stevedawg85 said:
I can run CM from SD card w/o rooting the device!? if so... sweet, I saw sum tuts but still educating myself. Rooting and leaving stock is also a good idea, however I heard B&N is able to update your device thus losing root... Is this true?
Click to expand...
Click to collapse
There is a thread in the dev section on how to block the updates. Here's a link to the sd card version of CM7 you asked about. You don't have to root first, but you can.
http://forum.xda-developers.com/showthread.php?t=989637
Sent from my X to the interwebs
As suggested I'd root the stock software for the wife, and when you want to play choose a ROM that can run from the sdcard and you will be good to go.
Currently I run 4 different setups. Stock rooted on internal mem. Then I setup 3 different sdcards to mess around with Honeycomb, CM7, and Froyo from time to time.
C Dippa said:
There is a thread in the dev section on how to block the updates. Here's a link to the sd card version of CM7 you asked about. You don't have to root first, but you can.
http://forum.xda-developers.com/showthread.php?t=989637
Sent from my X to the interwebs
Click to expand...
Click to collapse
You do not have to root it first. All you have to do is create a live SDcard with Clockwork ROM manager put the SDCard in and boot it up holding the n and the power button in > wipe > flash CM7.
With this device reading off the SD first you do not have "antonoot" first.
I've ran CM7, Honeycomb and a few others. My personal choice is stock rooted device is perfect.
stevedawg85 said:
I can run CM from SD card w/o rooting the device!?
Click to expand...
Click to collapse
I know! I couldn't believe it was that easy either. I'm going to add a notice to my signature. This kind of great capability should be right in people's faces..
Nookiefroyo runs great off an SD card for me.
Sent from my PC36100 using XDA App
Thanks for everyone's input...
She gonna be using it 75% of the time, so I decided to root and leave it as is. Everything works good. I tried to do nookie froyo off SD card but had too much trouble w/ adb, i'll save it for another week. But for now, stock root works good. Got Zeam and Home switcher to help both of us out
I wanted to point out the only downside of rooted stock is that she cannot use in the in-store B&N features! If she plans on using that (i've heard they have not only the hour of reading free, but also sometimes offer deals and events) then you might wanna not be rooted and use the SD card. I know this is a little late to tell you as you already did it, but I thought I'd let you know anyway.
stevedawg85 said:
Thanks for everyone's input...
She gonna be using it 75% of the time, so I decided to root and leave it as is. Everything works good. I tried to do nookie froyo off SD card but had too much trouble w/ adb, i'll save it for another week. But for now, stock root works good. Got Zeam and Home switcher to help both of us out
Click to expand...
Click to collapse
I'll throw this in for whenever you feel like creating a bootable SD CARD to play with. I've found that higher class sd cards make a much bigger difference in how fast/well the rom operates than you might think.
Is there a Dev out there that would be willing to check into the possibility of making a copy of the Stock B&N ROM available from SD partition OR figuring out a way to dual-boot to both stock and CM7 without having to run CM7 from the SD? I hate running CM7 from the SD it's fairly fast considering but still makes me want to pull my hair out at times. But I, like many others, cannot be without Stock Rom on my Nook(my daughter loves the interactive NC books like Dr. Suess and some of my books don't seem to work on the Nook App for Android which BTW is buggy as hell on CM7). If there is a way to run both from internal flash or just run Stock from SD card that would be amazing! I wouldn't care if it were a little buggy as much as I do with CM7 since I only use it to read books. But I asked on these forums and was told that there is no way to have both CM and Stock on your nook without running CM7 from the slot.
http://forum.xda-developers.com/showthread.php?t=1061523
Thanks so much Mr Frosty! I searched but I guess I chose my words poorly, cuz I didn't find that. Then someone else said it couldn't be done. Anyway you are the man!
no probs
Hi everyone,
I have a Galaxy S that is rooted, but runs on stock Froyo.
In the last couple of weeks/months it has been slugging to a slow halt though... when I start it up, it can take tens of minutes to be ready to use. And when I use it, it sometimes shows black screens for minutes at a time.
Using this 'high-end' phone has become a very, very painful process for me.
So I started looking for answers. And I found them. A LOT of them.
So much, I am not sure where to start.
The last few days I have been casually reading and taking in data from this forum, but I have yet failed to form me a proper view of what to do... Kernels, ROMs, speed fixes, modems... help?
I am sorry if I am breaking any rules; I did search, and I did read. However, no thread I found has a proper and up-to-date guide regarding the best way to get my phone to be a powerhouse, not a snail.
(Could I keep my current apps installed?)
I would very much appreciate anyone who is willing to donate some time to get me going. I know some programming and am the families 'go-to-guy' when it comes to computers, so I should be ok once I get some pointers on what to look for.
Thank you for reading (and responding?),
MM
I dunno if this will help you anyway i'll post it http://forum.xda-developers.com/showthread.php?t=939752
I did read that; thanks for the suggestion though.
It doesn't really go into kernels/roms/modems etc. which my main confusion is about.
I just downloaded darky's ROM... Reading their site, but I am afraid of losing my apps, not going to 2.3, having it interfere with my lagfix etc. =/
If you are afraid of loosing apps you can use titanium backup. You can download it from the market. I can't tell you anymore because that thread explains very well what you have to do. But i can say that after some time it will be very easy and you will not be afraid to flash a kernel or a rom. I post this too but i think you have read this too http://forum.xda-developers.com/showthread.php?t=723596
I did read that... I missed the 2.2 / 2.3 part however.
I planned on using Darky's ROM but that link says its a Froyo ROM.
Which one is better, currently; Cyanogen (Gingerbread) or Darky's (Froyo)?
Edit: also, while that post lists a lot of options, it in no way goes into which is the best option for which people...
Increasing the confusion a little bit more, so to speak.
Try cyanogenmod and darkyy rom and decide which is the best. I can't recommend anything you have to decide. But i suggest to upgrade to gingerbread. Your phone will get smoother. (darky's 10.2 is based on jvq a 2.3.4 gingerbread firmware). Link: http://forum.xda-developers.com/showthread.php?t=1061946 http://forum.xda-developers.com/showthread.php?t=814091. Remember: with cyanogenmod you have to use different kernels
Mad Maniak said:
The last few days I have been casually reading and taking in data from this forum, but I have yet failed to form me a proper view of what to do... Kernels, ROMs, speed fixes, modems... help?
MM
Click to expand...
Click to collapse
I'm a noob but I'll try to clear out few things for you.
From what I understand ROMs are like operating systems you use on PC.you currently have a froyo ROM running and flashing a gingerbread ROM will be like going from windows XP to windows 7.
when you download a ROM and unrar it you'll see 3 files.
PDA is the main one. PDA is Android and the apps that come with it. MODEM is the firmware of the wireless chipset of the device, it controls WiFi, Bluetooth and 3G/2G/GSM connections. The CSC holds connection data for the broadband networks as well as apps that are only available in certain languages/intended for a specific area or operator.
A kernel is like the heart of the operating system.It manages the system resources and acts as bridge between the software and hardware.
Now there are stock kernels and custom kernels. when you flash(install) a stock ROM all the necessary things are installed along with the stock kernel.
But if you wish you can flash custom kernels over stock kernels.
The speed/lag fix things you have read are basically conversion of file systems to enhance the I/O performance of your phone. You should know of the NTFS,FAT32 file systems in windows, similarly you android phone can have RFS,EXT4 file system. when you flash a stock rom RFS is default file system that gets installed.Many say that this RFS is to blame for the lag,slowness in our phone so what we do? we convert to EXT4. but to convert to EXT4 you need to be running a custom kernel.
So let me tell you this go on and flash a stock gingerbread rom, Im using the latest stock 2.3.4 XXJVR and you should try it. then you flash the voodoo kernel for XXJVR. it'll root your phone,convert the file system to EXT4.
reply if you have confusions.
cheers
Now you are on froyo. If you want to upgrade to gingerbread you should loose your application. Because if you backup your application using titanium backup or any other software from froyo. Its not advisable to restore in gingerbread. It will give always problem. So better way is download Drakys v10.2RE and do a fresh install.
http://samsung-sgs.blogspot.com/2011/08/how-to-flash-darkys-rom-v102-re.html
This happened to me once, when I was already on Froyo, lagfix activated, etc.
Took forever to boot, and was slow as hell.
Reason: faulty microsd card. The phone kept trying to read from it, and was unable to. I tried taking out the card and... voilá!
You could be still on Éclair and no lag fix activated, the phone would never behave like that. Try taking out the microsd card.
(Couldn't even read the card in the computer, so you see).
Hi guys, a small update:
I got Darky's 10.2, which is VERY smooth.
I reformatted my external microSD and put my stuff (music) back on it. Clean install on the internal SD.
It is a very enjoyable device once again. Two issues:
-It sometimes hangs on a black screen which I can't get out of with the home button. It seems only a battery in-and-out fixes this. (This issue worries me; is the internal SD corrupted?)
-The external microSD sometimes needs to be ejected and re-inserted to work.
Any solutions regarding that? Should I get a new microSD, or even contact Samsung to ask for a new phone (especially the first issue worries me... a lot).
Again, thanks a lot for the very extensive answers.
Especially marib; your post was very informative, and I'll be keeping a bookmark of it for future reference... thanks!
I think you could search for this issues in the darky's thread and if not found post the issue there to get a promt solution.
forum.xda-developers.com/showthread.php?t=814091
Yeah, figured as much.
Will be tackeling these issues in the weekend.
Just thought of posting them in this here thread too. Might have gotten lucky, and the thread was here anywho.
Again, thanks.
Hi -
I'm not really a newbie, but I'm a lurker, so I'm forced to post here for now. I spent some time yesterday flashing JB roms (after my CM9 bit the dust following a nandroid backup). After initial success with HellyBean, I was led into temptation by SlimBean/Semaphore and decided to give it a try. So, I followed all of the instructions, not even installing the extras and had no real trouble booting the system. But I had enormous lag to the point where the phone was not really usable. While using Titanium Backup to restore my apps and data (which took over an hour -- on HB it takes about 15 minutes), the Market process kept crashing in the background. Calls to su were taking an inordinate amount of time, causing apps like AdAway to timeout. And so on.
I wiped and installed twice, so I don't think it was a fluke, and I applied the 2.0.1 update, as well.
Anyway, I went back to HellyBean and everything is zippy again. I prefer the SlimBean idea and aesthetic, but it was not usable on my particular phone (GT-I9000 GSM / XJVT modem). Not sure if anyone else has had a similar problem and knows the solution. If anyone from the dev forum sees this and wants to link to it so that the ROM dev is aware, that would be great. Thanks.
sm72
sockmonkey72 said:
Hi -
I'm not really a newbie, but I'm a lurker, so I'm forced to post here for now. I spent some time yesterday flashing JB roms (after my CM9 bit the dust following a nandroid backup). After initial success with HellyBean, I was led into temptation by SlimBean/Semaphore and decided to give it a try. So, I followed all of the instructions, not even installing the extras and had no real trouble booting the system. But I had enormous lag to the point where the phone was not really usable. While using Titanium Backup to restore my apps and data (which took over an hour -- on HB it takes about 15 minutes), the Market process kept crashing in the background. Calls to su were taking an inordinate amount of time, causing apps like AdAway to timeout. And so on.
I wiped and installed twice, so I don't think it was a fluke, and I applied the 2.0.1 update, as well.
Anyway, I went back to HellyBean and everything is zippy again. I prefer the SlimBean idea and aesthetic, but it was not usable on my particular phone (GT-I9000 GSM / XJVT modem). Not sure if anyone else has had a similar problem and knows the solution. If anyone from the dev forum sees this and wants to link to it so that the ROM dev is aware, that would be great. Thanks.
sm72
Click to expand...
Click to collapse
So, as this forum is called Q&A, let me answer my own question, and possibly help some other poor sucker with the same problem. The problem is apparently my S-NAND speed, and for reasons apparently mysterious to everyone who talks about it, some (older) SGS have either slower or broken S-NAND memory. And for some reason that I don't understand, kernels which use /datadata (like the Helly Bean kernel) allow those of us with this particular S-NAND configuration to use ROMs in a reasonably lagless fashion.
So, as I understand it, I should:
- re-wipe and install Slim Bean
- boot into recovery and flash the HB kernel
- enjoy Slim Bean without horrible UI lag
Someone please correct me if I'm wrong. Thanks.
sm72
sockmonkey72 said:
So, as this forum is called Q&A, let me answer my own question, and possibly help some other poor sucker with the same problem. The problem is apparently my S-NAND speed, and for reasons apparently mysterious to everyone who talks about it, some (older) SGS have either slower or broken S-NAND memory. And for some reason that I don't understand, kernels which use /datadata (like the Helly Bean kernel) allow those of us with this particular S-NAND configuration to use ROMs in a reasonably lagless fashion.
So, as I understand it, I should:
- re-wipe and install Slim Bean
- boot into recovery and flash the HB kernel
- enjoy Slim Bean without horrible UI lag
Someone please correct me if I'm wrong. Thanks.
sm72
Click to expand...
Click to collapse
Basically, the JB devil kernel uses the faster /datadata partition.
If you're worried about low storage space install the Datafix app in the Play Store.
I use CM9 and recently flashed "build 5 captivate mtd/cm9, based on teamhacksung's ICS Build 14 (USB host mode driver)".
Now, the internal SD card can only be accessed through CWM. Root Explorer tells me the SD card isn't mounted and in the preferences, the option to mount it is greyed out.
So what I'm looking for is mostly a way to manually mount the SD card through the terminal emulator or something. That would be enormously helpful for the time being. Until I have the time to wipe the whole damn thing and make everything work like it used to.
(And... idiot that I am, I thought "Meh, I'm not going to do a nandroid backup before flashing this - I'm sure such a minor update is gonna be fine" - so restoring a backup isn't really an option either...)
I'm not sure but all I know is you are using a very ancient kernel... I don't know why you thought it was an upgrade. It is essentially the kernel from an alpha build that had many bugs at the time. There are probably incompatibilities between this and current CM code. Both Semaphore and Devil kernels (which are current) support USB Host, if that's what it is that you are looking for.
Oh, and since you only flashed a kernel, a nandroid would be mostly useless. Just flash a new one or flash CM9 again to return to the stock one.
Well... I didn't think it was a whole kernel but just a driver (I don't know enough to know where/how in the whole system drivers are integrated). And since it was the latest version for CM9, I figured it'll be fine. Didn't even realize that CM10 stable is out already. (And I thought that nandroid backs up kernel, ROM and data?)
At any rate - thank you very much for explaining and providing those solutions! :good:
notthere said:
Well... I didn't think it was a whole kernel but just a driver (I don't know enough to know where/how in the whole system drivers are integrated). And since it was the latest version for CM9, I figured it'll be fine. Didn't even realize that CM10 stable is out already. (And I thought that nandroid backs up kernel, ROM and data?)
At any rate - thank you very much for explaining and providing those solutions! :good:
Click to expand...
Click to collapse
Yes, nandroids do back up kernels, but if that's all you want to restore, it's simpler to just flash one.
Sent from my SGH-I777 using xda premium