Related
So after installing this amazing rom and loving it for a week or two; I see a kernel update and install it. Everything went smooth but I lost my wifi after the fact. I was hoping someone could help me keep the kernel and get the wifi going. nothing about wifi problems were stated and it work fine previously. I wiped everything and even tried the wifi fix manager thingy i got with the ics rom i was running previously to see if that would do it but to no avail. I wanted to ask the developer but need some 10 post so help a bro out!
p.s....gotta give props to the man who had me running jb before anyone of my friends with newer phones!!! RANDOMBLAME!!!!
bboygmoney said:
So after installing this amazing rom and loving it for a week or two; I see a kernel update and install it. Everything went smooth but I lost my wifi after the fact. I was hoping someone could help me keep the kernel and get the wifi going. nothing about wifi problems were stated and it work fine previously. I wiped everything and even tried the wifi fix manager thingy i got with the ics rom i was running previously to see if that would do it but to no avail. I wanted to ask the developer but need some 10 post so help a bro out!
p.s....gotta give props to the man who had me running jb before anyone of my friends with newer phones!!! RANDOMBLAME!!!!
Click to expand...
Click to collapse
ditto, this happend with my Paranoidandroid install as well. kernel allowed me to stay running without crash, but wifi is a pretty big letdown...
unfortunatly, without the kernel itself being fixed, or the wifi module fixed, we are stuck looking for another alternate kernel... oh yeah, we are pretty limited.
thanks
appreciate the quick reply man. And I'll be keeping my eye out then
bboygmoney said:
appreciate the quick reply man. And I'll be keeping my eye out then
Click to expand...
Click to collapse
found out a very possible reason . are you using his kernel with another system or is this all jt only? he mentioned something about kangbang changing drivers.
dakunesu said:
found out a very possible reason . are you using his kernel with another system or is this all jt only? he mentioned something about kangbang changing drivers.
Click to expand...
Click to collapse
So I'm only using it with jelly time or jb. I'm flashing the os then the kernel cuz the os installs its own. This is an updated kernel for the os.I'm thinking i should maybe wipe the cache partition after the the os then do the kernel but at the same time I would think that other problems would be happening if that was the issue. What do you think?
bboygmoney said:
So I'm only using it with jelly time or jb. I'm flashing the os then the kernel cuz the os installs its own. This is an updated kernel for the os.I'm thinking i should maybe wipe the cache partition after the the os then do the kernel but at the same time I would think that other problems would be happening if that was the issue. What do you think?
Click to expand...
Click to collapse
does the system function without the kernel update?
if it does, you might want to hold off on updating til the ROM updates for it.
dakunesu said:
found out a very possible reason . are you using his kernel with another system or is this all jt only? he mentioned something about kangbang changing drivers.
Click to expand...
Click to collapse
dakunesu said:
does the system function without the kernel update?
if it does, you might want to hold off on updating til the ROM updates for it.
Click to expand...
Click to collapse
It does. N You know I am not even sure what advantages I get from this updated kernel anyways lol but I want it!!
problem solved!
bboygmoney said:
It does. N You know I am not even sure what advantages I get from this updated kernel anyways lol but I want it!!
Click to expand...
Click to collapse
The ROM was updated and the kernel included in the update! Amazing rom , highly recommended especially with the updated kernel!
Ive had enough of running buggy, battery hungry roms and would like to return my Nexus S to stock. The last time I was on stock was 2.3.6 I believe. If I flash via CWM to the official 4.0.3 in this thread: http://forum.xda-developers.com/showthread.php?t=1445570 will I then be able receive OTA updates, ie to 4.1.2? (obviously Ill be rooted again, but im not fussed)
Rotellian said:
Ive had enough of running buggy, battery hungry roms and would like to return my Nexus S to stock. The last time I was on stock was 2.3.6 I believe. If I flash via CWM to the official 4.0.3 in this thread: http://forum.xda-developers.com/showthread.php?t=1445570 will I then be able receive OTA updates, ie to 4.1.2? (obviously Ill be rooted again, but im not fussed)
Click to expand...
Click to collapse
Flash the stock images from Google and 4.1.2 instead.
https://developers.google.com/android/nexus/images#sojujzo54k
Read the instructions, you need to use fastboot for these.
polobunny said:
Flash the stock images from Google and 4.1.2 instead.
https://developers.google.com/android/nexus/images#sojujzo54k
Read the instructions, you need to use fastboot for these.
Click to expand...
Click to collapse
Best way to do it!
Rotellian said:
Ive had enough of running buggy, battery hungry roms and would like to return my Nexus S to stock. The last time I was on stock was 2.3.6 I believe. If I flash via CWM to the official 4.0.3 in this thread: http://forum.xda-developers.com/showthread.php?t=1445570 will I then be able receive OTA updates, ie to 4.1.2? (obviously Ill be rooted again, but im not fussed)
Click to expand...
Click to collapse
Buggy? Battery hungry ? You were in what ROM? All custom ROMs at almost 100% bugs free(especially CM10 and CM10/AOKP based). Weird ...
Dont have the time to setup the computer for Fastboot, couldnt get it working with Win7 last time out either.
aladin6 said:
Buggy? Battery hungry ? You were in what ROM? All custom ROMs at almost 100% bugs free(especially CM10 and CM10/AOKP based). Weird ...
Click to expand...
Click to collapse
Tried all sorts, Oxygen, NSCollab, early ICS roms (awful), others i cant remember. Best combo i had was stock 2.3.6/7 with a Kernel i think. I found that invariably they become less stable the longer you have them installed. Of course if you change rom a lot you'll never notice.
I'm with you, running stock 4.1.2 since it came out, only with custom kernel for BLN, highbigmem and voodoo sound and don't regret it a bit. A lot of free time and no need to update all the time;P
Rotellian said:
Dont have the time to setup the computer for Fastboot, couldnt get it working with Win7 last time out either.
Click to expand...
Click to collapse
How did you root and unlock your phone then? Only way to do it needs an actual working connection with fasboot/adb. Even the 1 click crap uses that.
I guess nothing stops you from flashing 4.0.3 then going the upgrade route, but I don't see that as a very efficient nor a clean way to do it.
madd0g said:
I'm with you, running stock 4.1.2 since it came out, only with custom kernel for BLN, highbigmem and voodoo sound and don't regret it a bit. A lot of free time and no need to update all the time;P
Click to expand...
Click to collapse
OMG, how can you stay with ONE ROM more than one week . No seriously, there is 2 ROMs that they're perfectly stable and full of features: CM10 and ParanaoidAndroid. I no longer look to other ROMs. And ParanoidAndroid is in my device more than 2 weeks
aladin6 said:
OMG, how can you stay with ONE ROM more than one week . No seriously, there is 2 ROMs that they're perfectly stable and full of features: CM10 and ParanaoidAndroid. I no longer look to other ROMs. And ParanoidAndroid is in my device more than 2 weeks
Click to expand...
Click to collapse
It would be hard to call CM10 something related to stable (same for any CM10 base ROM). Even they don't call it that. That's why the nightly tag is for.
polobunny said:
It would be hard to call CM10 something related to stable (same for any CM10 base ROM). Even they don't call it that. That's why the nightly tag is for.
Click to expand...
Click to collapse
Other than "stable" "nightly" "RC" WORDS, CM10 is completely STABLE(at 99%). And i know what "stable" word means. Source: own experience .
polobunny said:
How did you root and unlock your phone then? Only way to do it needs an actual working connection with fasboot/adb. Even the 1 click crap uses that.
I guess nothing stops you from flashing 4.0.3 then going the upgrade route, but I don't see that as a very efficient nor a clean way to do it.
Click to expand...
Click to collapse
Managed to get ADB working on my old XP laptop, which i no longer have! Just tried to install it, and again the driver problem rears its ugly head. Just wont recognise the inf file! Like I said, dont really have the time, guess ill just have to flash to 4.0.3 and wait for the OTA Dont have the time to muck about trying to get the drivers working. Might give it one last bash with the SDK
Rotellian said:
Dont have the time to setup the computer for Fastboot, couldnt get it working with Win7 last time out either.
Click to expand...
Click to collapse
Returning to stock requires a computer. Official OTA updates will not install without the stock recovery.
Sent from my Nexus S 4G using Tapatalk 2
aladin6 said:
Other than "stable" "nightly" "RC" WORDS, CM10 is completely STABLE(at 99%). And i know what "stable" word means. Source: own experience .
Click to expand...
Click to collapse
You'll see a lot of people still have complaints regarding functions that get broken with each version, only to come back working after the next one. It's silly to assume CM team doesn't know **** about development and simply tag "nightly", "RC" and "stable" for the sake of it. Please don't bring up made up stability percentages into the lot.
You can glance at the nightly changelogs yourself to see NPEs getting corrected in relatively core apps nearly every week. Not just for crespo too, but regarding CM10 as a whole.
I'll give you that though, on a day to day basis, the rom is very usable. But good luck getting a 1000 hours uptime without the thing becoming sluggish.
Rotellian said:
Managed to get ADB working on my old XP laptop, which i no longer have! Just tried to install it, and again the driver problem rears its ugly head. Just wont recognise the inf file! Like I said, dont really have the time, guess ill just have to flash to 4.0.3 and wait for the OTA Dont have the time to muck about trying to get the drivers working. Might give it one last bash with the SDK
Click to expand...
Click to collapse
Just get the PDAnet Android drivers.
madd0g said:
Just get the PDAnet Android drivers.
Click to expand...
Click to collapse
Was just going to do that, but think ive got it working now. Im guessing a full install from google's image will result in a compeltely stock phone including bootloader?
lol
Rotellian said:
Ive had enough of running buggy, battery hungry roms and would like to return my Nexus S to stock. The last time I was on stock was 2.3.6 I believe. If I flash via CWM to the official 4.0.3 in this thread: http://forum.xda-developers.com/showthread.php?t=1445570 will I then be able receive OTA updates, ie to 4.1.2? (obviously Ill be rooted again, but im not fussed)
Click to expand...
Click to collapse
lol, really you want to go back to stock?
wats buggy now?
stable roms of ics,gb came in...
I'm using this now: http://forum.xda-developers.com/showthread.php?t=1946338 . It'a a 4.1.2 stock rom, just flash it and you're ready to go.
---------- Post added at 11:31 PM ---------- Previous post was at 11:28 PM ----------
unnamed.aj. said:
lol, really you want to go back to stock?
wats buggy now?
stable roms of ics,gb came in...
Click to expand...
Click to collapse
For me, cm10 m2 was buggy and slow. So I had decided to return to 4.1.2 stock (with Matrix kernel )
sergiu_s said:
I'm using this now: http://forum.xda-developers.com/showthread.php?t=1946338 . It'a a 4.1.2 stock rom, just flash it and you're ready to go.
---------- Post added at 11:31 PM ---------- Previous post was at 11:28 PM ----------
For me, cm10 m2 was buggy and slow. So I had decided to return to 4.1.2 stock (with Matrix kernel )
Click to expand...
Click to collapse
Cheers, looks good Does it include radio? Just flash with CWM?
Rotellian said:
Was just going to do that, but think ive got it working now. Im guessing a full install from google's image will result in a compeltely stock phone including bootloader?
Click to expand...
Click to collapse
If you use all commands from the flash-all.sh script, yes. No need to flash the bootloader and radio if you already have the latest version.
What's the best jelly bean rom for the One S (S4). I'm tired of waiting for the official OTA from HTC so i'm going to try a custom rom. I've heard CM10 is one the best but i could only find nightlies in the development section. Any suggestions?
lonegunman0 said:
What's the best jelly bean rom for the One S (S4). I'm tired of waiting for the official OTA from HTC so i'm going to try a custom rom. I've heard CM10 is one the best but i could only find nightlies in the development section. Any suggestions?
Click to expand...
Click to collapse
Nightlies work fine so don't worry about that and if you want a bit of a tweaked one then BAKED BlackBean is a good rom. But before you do anything if you haven't flashed a rom on this phone then you want to get yourself into the All-In-One Toolkit thread and do a bit of read before you do any flashing and also don't install CWM but instead install TWRP recovery.
Oh right thanks dude, and yh I've done rooting on this phone before so I've got the all in one kit. Atm I'm unrooted so I don't have a custom recovery so what's different about twrp from cwm
lonegunman0 said:
Oh right thanks dude, and yh I've done rooting on this phone before so I've got the all in one kit. Atm I'm unrooted so I don't have a custom recovery so what's different about twrp from cwm
Click to expand...
Click to collapse
Its not buggy and can mount SD and if you have 1.09 or lower Hboot it can also flash the boot.img.
Darknites said:
Its not buggy and can mount SD and if you have 1.09 or lower Hboot it can also flash the boot.img.
Click to expand...
Click to collapse
Would it be an issue if I install cwm, as in major issues
Sent from my HTC One S using xda app-developers app
lonegunman0 said:
Would it be an issue if I install cwm, as in major issues
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Not really but you are bested off with TWRP. Its mostly it will boot into CWM if you turn off the phone with usb cable connected and cant mount SD.
Darknites said:
Its not buggy and can mount SD and if you have 1.09 or lower Hboot it can also flash the boot.img.
Click to expand...
Click to collapse
Baked is good too, but I find the latest PAC Man ROM to be really stable, and has lots of good tweaks and customizations available (its also one of the more recently updated AOSP base ROMs).
Also make sure to use a good AOSP kernel, and klin has the only good solution, his Fusion 3.1. It works very well for me. If your coming from SENSE, you will need to flash that kernel as well in order to load the ROM (check the kernel thread for install instructions and follow carefully, since you may need to fastboot flash in addition to flashing the .zip).
Cheers,
AKToronto
AKToronto said:
Baked is good too, but I find the latest PAC Man ROM to be really stable, and has lots of good tweaks and customizations available (its also one of the more recently updated AOSP base ROMs).
Also make sure to use a good AOSP kernel, and klin has the only good solution, his Fusion 3.1. It works very well for me. If your coming from SENSE, you will need to flash that kernel as well in order to load the ROM (check the kernel thread for install instructions and follow carefully, since you may need to fastboot flash in addition to flashing the .zip).
Cheers,
AKToronto
Click to expand...
Click to collapse
Ya said about Baked and PAC Man is a bit over the top for me and I so wish I could use that kernel but it don't like me for some reason.
Darknites said:
Ya said about Baked and PAC Man is a bit over the top for me and I so wish I could use that kernel but it don't like me for some reason.
Click to expand...
Click to collapse
LOL, I remember your posts in that kernel thread... Hard to know what the issue is. Seems like kernels can have feelings too, and it dont like you, lol.
But in all seriousness, I would definately second your recomendation for using TWRP custom recovery. It has lots of useful features and is way more intuitive than Clockwork. Its also been updated more recently than Clockwork for the HTC One S.
I used clockwork for a while until I tried TWRP and now havent looked back. If you try it, you will see why its better.
AKToronto
AKToronto said:
LOL, I remember your posts in that kernel thread... Hard to know what the issue is. Seems like kernels can have feelings too, and it dont like you, lol.
AKToronto
Click to expand...
Click to collapse
Lol, If only it didn't have the reboots I could happily have the lockscreen glitch lol it looks really cool.
Long boot time
Hmmm i've just installed cm10 using cwm and the initial boot up time is taking ages, i've been waiting for about 10 minutes now. What should i do?
lol i think i should've listen to Darknites and used twrp
lonegunman0 said:
Hmmm i've just installed cm10 using cwm and the initial boot up time is taking ages, i've been waiting for about 10 minutes now. What should i do?
lol i think i should've listen to Darknites and used twrp
Click to expand...
Click to collapse
Lol might be down to not fastbooting the boot.img, did you do that?
boot time
Darknites said:
Lol might be down to not fastbooting the boot.img, did you do that?
Click to expand...
Click to collapse
Whoops forgot to do that, it works now thanks dude
lonegunman0 said:
Whoops forgot to do that, it works now thanks dude
Click to expand...
Click to collapse
Np dude and enjoy.
Darknites said:
Np dude and enjoy.
Click to expand...
Click to collapse
One last thing, where's google now and the play store icon?
lonegunman0 said:
One last thing, where's google now and the play store icon?
Click to expand...
Click to collapse
Download 4.1.2 gapps.
What ROM delivers the closest to unadorned Nexus experience on One S? Would it be AOKP?
lewdvig said:
What ROM delivers the closest to unadorned Nexus experience on One S? Would it be AOKP?
Click to expand...
Click to collapse
CM10 the other roms add other stuff but they are useful so up to you on that.
Darknites said:
Ya said about Baked and PAC Man is a bit over the top for me and I so wish I could use that kernel but it don't like me for some reason.
Click to expand...
Click to collapse
Yeah, klin said it won't work for baked as of yet.
And I would have to agree that baked is the nicest rom available for the one s. I have it UC to 1.026ghz and it's as responsive and quick as anything else at 1.5 or even OC'd higher. The battery life is excellent as well
There's also some settings he added under settings->baked rom control->prop modder/init.d that are really nice. Some signal enhancements, boot settings etc.
I'm not sure if you prefer sense to aosp, or if the main reason for wanting jb is for Google Now, but the viper rom has GNow working just fine and is sense based.
Sent from a baked One S
If I've helped hit the thanks button
beats4x said:
Yeah, klin said it won't work for baked as of yet.
Click to expand...
Click to collapse
No my issue has nothing to do with Baked rom its all in his thread.
I am trying to install Franco kernel on my phone, and I have found the thread for this, but I am really confused on how to install it on my phone. I know that it's the same as installing a ROM, so I downloaded the appropriate version for my phone, but it said "Failed" while flashing it with TWRP. Am I doing something wrong?
SketchySean said:
I am trying to install Franco kernel on my phone, and I have found the thread for this, but I am really confused on how to install it on my phone. I know that it's the same as installing a ROM, so I downloaded the appropriate version for my phone, but it said "Failed" while flashing it with TWRP. Am I doing something wrong?
Click to expand...
Click to collapse
Yes, you are doing something wrong. FranciscoFranco does not have a kernel for the Verizon GSIII. Stop what you're doing and use a kernel from the VZW GSIII Original dev section.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Yes, you are doing something wrong. FranciscoFranco does not have a kernel for the Verizon GSIII. Stop what you're doing and use a kernel from the VZW GSIII Original dev section.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Ahh! Not gonna lie, I feel stupid right now. And thanks, I will. But what kernel would you recommend in terms of battery life-friendly? I've seen you around in the threads. You're awesome at helping people!
SketchySean said:
Ahh! Not gonna lie, I feel stupid right now. And thanks, I will. But what kernel would you recommend in terms of battery life-friendly? I've seen you around in the threads. You're awesome at helping people!
Click to expand...
Click to collapse
I personally love ktoonsez kernel, lots of tweaks and governors to it.
Sent from my SCH-I535 using Tapatalk 2
SketchySean said:
Ahh! Not gonna lie, I feel stupid right now. And thanks, I will. But what kernel would you recommend in terms of battery life-friendly? I've seen you around in the threads. You're awesome at helping people!
Click to expand...
Click to collapse
All the Touchwiz kernels do a good job with increasing battery life.
Wow, I tried to flash the Zeus kernel and it just messed up my phone.. I rebooted and my screen was black. Couldn't reboot again, so I went into recovery mode and restored from back up :/ What did I do wrong?
which rom have you?
I am currently on CM10.1
Sent from my SCH-I535 using xda app-developers app
SketchySean said:
I am currently on CM10.1
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
You need an AOSP kernel. Not TW. KT747 is probably the way to go. Just make sure you download the AOSP version. Next time say what ROM you're running. That way you can avoid confusion early on.
Oh, alright. So that kernel is battery friendly? And is there a specific thread where I can find kernels for my ROM and or phone?
Sent from my SCH-I535 using xda app-developers app
SketchySean said:
Oh, alright. So that kernel is battery friendly? And is there a specific thread where I can find kernels for my ROM and or phone?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Not sure if there is a single thread that lists all the kernels. Just go here to the original android development forum:
http://forum.xda-developers.com/forumdisplay.php?f=1692
and look for threads that have AOSP and Kernel in the thread title.
Edit - actually, perhaps this thread may help you:
http://forum.xda-developers.com/showthread.php?t=2064506
landshark68 said:
Not sure if there is a single thread that lists all the kernels. Just go here to the original android development forum:
http://forum.xda-developers.com/forumdisplay.php?f=1692
and look for threads that have AOSP and Kernel in the thread title.
Edit - actually, perhaps this thread may help you:
http://forum.xda-developers.com/showthread.php?t=2064506
Click to expand...
Click to collapse
Okay, so I flashed the Ktoonz kernel.. and now my screen is black again. I really don't know what I'm doing wrong.
SketchySean said:
Okay, so I flashed the Ktoonz kernel.. and now my screen is black again. I really don't know what I'm doing wrong.
Click to expand...
Click to collapse
When is your CM10.1 rom dated as? When was it released? You might need a kernel from before the rom's date.
SlimSnoopOS said:
When is your CM10.1 rom dated as? When was it released? You might need a kernel from before the rom's date.
Click to expand...
Click to collapse
I can't check cause my screen is black.. but I think I got the one dated at 3/4/2013
I checked the ROM that was in my ext hard drive, and I think it's CM 10.1- 201330304-EXPERIMENTAL-d2vzw-M2
SketchySean said:
I can't check cause my screen is black.. but I think I got the one dated at 3/4/2013
Click to expand...
Click to collapse
As in, from March? lol Ahh, you basically can't flash any current kernel out unless it's from around March 4th. Ahh, you're using the Linux 3.0 based version then. All AOSP roms have moved to the Linux 3.4 kernel as of early April Edit: Actually,mid-March was the Linux 3.0 to 3.4 switch which means all kernels are now incompatible with roms dated say before early March.
Here's KT747 from March 5th, should be fine flashing this.
Edit: flash the AOSP 4.2 version btw, that's what CM10.1 is based on
SlimSnoopOS said:
As in, from March? lol Ahh, you basically can't flash any current kernel out unless it's from before March 4th. Ahh, you're using the Linux 3.0 based version then. All AOSP roms have moved to the Linux 3.4 kernel as of early April which means all kernels are now incompatible with roms dated say before early April.
Here's KT747 from March 5th, should be fine flashing this.
Edit: flash the AOSP 4.2 version btw, that's what CM10.1 is based on
Click to expand...
Click to collapse
If I flash this kernel, will it wipe everything? And is this the only kernel that I can use? I'm really sorry if I'm asking a lot of questions, lol...
SketchySean said:
If I flash this kernel, will it wipe everything? And is this the only kernel that I can use? I'm really sorry if I'm asking a lot of questions, lol...
Click to expand...
Click to collapse
Nah, flashing kernels only necessitates you wiping Cache and Dalvik Cache in recovery. Neither of which is user data. Cache and Dalvik Cache get rebuilt once the rom boots so it's not something you'll notice besides the initial boot.
As for your second question, no this is not the only kernel you can use. If you want to stay on this exact rom, then you'll just have to do a lot of searching through kernel threads, for their Linux 3.0 based kernels from early March. However, this goes along with what I said in my prior post. Given that you are on a March 4th rom, you can only use Linux 3.0 based kernels which kernel devs usually mention in their changelog. Most (honestly all) kernel devs have stopped actively developing these and have moved onto Linux 3.4 kernels which will not boot on the rom you are on because it is outdated.
I encourage you to upgrade your rom to a current one and to keep up with active development that way you don't get left behind when flashing kernels (if that's your thing).
SlimSnoopOS said:
Nah, flashing kernels only necessitates you wiping Cache and Dalvik Cache in recovery. Neither of which is user data. Cache and Dalvik Cache get rebuilt once the rom boots so it's not something you'll notice besides the initial boot.
As for your second question, no this is not the only kernel you can use. If you want to stay on this exact rom, then you'll just have to do a lot of searching through kernel threads, for their Linux 3.0 based kernels from early March. However, this goes along with what I said in my prior post. Given that you are on a March 4th rom, you can only use Linux 3.0 based kernels which kernel devs usually mention in their changelog. Most (honestly all) kernel devs have stopped actively developing these and have moved onto Linux 3.4 kernels which will not boot on the rom you are on because it is outdated.
I encourage you to upgrade your rom to a current one and to keep up with active development that way you don't get left behind when flashing kernels (if that's your thing).
Click to expand...
Click to collapse
Alright, I will flash the 3.0 kernel right now. And as for updating my CM10.1, can i just update it through my phone? I've came across this option where I can just update it through settings. Will updating ROMS wipe my stuff? And I REALLY appreciate your help.
SketchySean said:
Alright, I will flash the 3.0 kernel right now. And as for updating my CM10.1, can i just update it through my phone? I've came across this option where I can just update it through settings. Will updating ROMS wipe my stuff? And I REALLY appreciate your help.
Click to expand...
Click to collapse
I wouldn't. Being that you're moving from a March CM build to a May CM build with a lot of changes, you need to do a full wipe in recovery to upgrade roms. Doing a dirty flash in this case introduces way too much room for issues to arise. As long as you do not wipe internal storage then you will not lose your data on the internal sdcard.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
I wouldn't. Being that you're moving from a March CM build to a May CM build with a lot of changes, you need to do a full wipe in recovery to upgrade roms. Doing a dirty flash in this case introduces way too much room for issues to arise. As long as you do not wipe internal storage then you will not lose your data on the internal sdcard.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
So if I flash from recovery, everything will be exactly the way it was?
hi im new in this forum, reading around and with other members help I think im ready to install a custom rom now, my phone is international and has JB leak 1, and in this thread http://forum.xda-developers.com/showthread.php?t=2050705 in the end the say that you can flash this rom being on this Jb leak, i thought it was only for ics kernel, how is that? does that rom has still the kexec issue with some random phones getting a black screen on boot or is it fix for everyone now? thanks for your help :laugh:
porraxeneize said:
hi im new in this forum, reading around and with other members help I think im ready to install a custom rom now, my phone is international and has JB leak 1, and in this thread http://forum.xda-developers.com/showthread.php?t=2050705 in the end the say that you can flash this rom being on this Jb leak, i thought it was only for ics kernel, how is that? does that rom has still the kexec issue with some random phones getting a black screen on boot or is it fix for everyone now? thanks for your help :laugh:
Click to expand...
Click to collapse
Only & only Kexec based ROM's can be installed directly on JB official (unofficial leak by wangghost) rest all ROM's are for ICS. I too would like to be clarified regarding the black screen kexec issue has been sorted across all kexec roms??
RAD7 said:
Only & only Kexec based ROM's can be installed directly on JB official (unofficial leak by wangghost) rest all ROM's are for ICS. I too would like to be clarified regarding the black screen kexec issue has been sorted across all kexec roms??
Click to expand...
Click to collapse
Yes, black screen issue has been sorted by JBX Kernel.
RAD7 said:
Only & only Kexec based ROM's can be installed directly on JB official (unofficial leak by wangghost) rest all ROM's are for ICS. I too would like to be clarified regarding the black screen kexec issue has been sorted across all kexec roms??
Click to expand...
Click to collapse
XploitMachine said:
Yes, black screen issue has been sorted by JBX Kernel.
Click to expand...
Click to collapse
wait so if I want I can install this rom http://forum.xda-developers.com/showthread.php?t=2050705 on JB leak 1? I just install BMM and the flash zip and its done? the JBX kernel to fix the kexec issue comes already with the rom or I have to install it manually?
porraxeneize said:
wait so if I want I can install this rom http://forum.xda-developers.com/showthread.php?t=2050705 on JB leak 1? I just install BMM and the flash zip and its done? the JBX kernel to fix the kexec issue comes already with the rom or I have to install it manually?
Click to expand...
Click to collapse
as long as your rooted, yes. install BMM, follow instructions in its thread, and flash ROM.
Black screen issue should be fixed without needing JBX.
MotoMudder77 said:
as long as your rooted, yes. install BMM, follow instructions in its thread, and flash ROM.
Black screen issue should be fixed without needing JBX.
Click to expand...
Click to collapse
porraxenieze, afaik a prerequisite of JBX is to be first on a kexec kernel. I u/s what 'MotoMudder' is saying but I am unsure how jbx plays in a multiboot environment, I mean if for ex if someone has stock unoffficial (official) JB leak on sys 1 and on sys 3 if one installs 4.3 kexec PA or say kexec 4.3 Slimbean & then flashes jbx, what happens??
RAD7 said:
porraxenieze, afaik a prerequisite of JBX is to be first on a kexec kernel. I u/s what 'MotoMudder' is saying but I am unsure how jbx plays in a multiboot environment, I mean if for ex if someone has stock unoffficial (official) JB leak on sys 1 and on sys 3 if one installs 4.3 kexec PA or say kexec 4.3 Slimbean & then flashes jbx, what happens??
Click to expand...
Click to collapse
JBX is kexec.
MotoMudder77 said:
JBX is kexec.
Click to expand...
Click to collapse
What I mean to say is in the JBX OP, it mentions before flashing JBX, phone needs to have a kexec ROM installed beforehand & only then jbx can be flashed.
RAD7 said:
What I mean to say is in the JBX OP, it mentions before flashing JBX, phone needs to have a kexec ROM installed beforehand & only then jbx can be flashed.
Click to expand...
Click to collapse
well yea, otherwise you'd be flashing a kernel to a ROM that doesnt support it.
flash ROM, then flash JBX to it.
MotoMudder77 said:
well yea, otherwise you'd be flashing a kernel to a ROM that doesnt support it.
flash ROM, then flash JBX to it.
Click to expand...
Click to collapse
im not sure if I understand, i mean, the only thing I ever did to my phone is update to the JB leak via rsdlite, and now I only want to flash the paranoid android rom, the JBX kernel I do not want it, but now I dont understand if it is required or not to use the rom and prevent the black screen kexec issue
MotoMudder77 said:
as long as your rooted, yes. install BMM, follow instructions in its thread, and flash ROM.
Black screen issue should be fixed without needing JBX.
Click to expand...
Click to collapse
ah okay did not saw this carefully, so I can install the rom on the jb leak 1, already rooted, just need to install bmm and flash
do i have to do the partition and install on system 3 or can i just install it, dont do the partition and install it on system 1?
porraxeneize said:
ah okay did not saw this carefully, so I can install the rom on the jb leak 1, already rooted, just need to install bmm and flash
do i have to do the partition and install on system 3 or can i just install it, dont do the partition and install it on system 1?
Click to expand...
Click to collapse
I would partition. JB ROM's are far from stable, and never will be without kernel source. Always nice to have a stable Daily driver on your phone to fall back on.
Sent from my MB865 using Tapatalk 2
MotoMudder77 said:
I would partition. JB ROM's are far from stable, and never will be without kernel source. Always nice to have a stable Daily driver on your phone to fall back on.
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
mmm okay i guess, i will see it then, when i do the partition the systems 3 - 6 can only be 1gb max right? that means you only have that much to install on the internal memory? seems low..