Related
I just successfully rooted my phone using the DooMLoRD method. I wan't to use a Jellybean custom rom(probably aokp). What kernel do I need? I have a Galaxy S2 with version 2.3.4 and gingerbread.uckh7.
You need one with cwm baked in. It's that simple. The rom you select will flash the recommended kernel
Sent from my Galaxy Nexus
aknbad23 said:
I just successfully rooted my phone using the DooMLoRD method. I wan't to use a Jellybean custom rom(probably aokp). What kernel do I need? I have a Galaxy S2 with version 2.3.4 and gingerbread.uckh7.
Click to expand...
Click to collapse
All roms will automatically flash an appropriate kernel.
dsmboost said:
All roms will automatically flash an appropriate kernel.
Click to expand...
Click to collapse
Ok, but don't I need to backup my phone(contacts,apps,etc) with CWM recovery before I put a ROM on it? That would mean I need a CWM kernel right?
aknbad23 said:
Ok, but don't I need to backup my phone(contacts,apps,etc) with CWM recovery before I put a ROM on it?
Click to expand...
Click to collapse
These are really basic and common questions that you are asking and can be easily found by searching. I'm just giving you a fair warning, because you will be flamed by others for not searching.
Creating backups via CWM is not a requirement to flash anything. It is highly recommended that you do create backups though (especially if you're new to this), in case something goes wrong while flashing stuff.
dsmboost said:
These are really basic and common questions that you are asking and can be easily found by searching. I'm just giving you a fair warning, because you will be flamed by others for not searching.
Creating backups via CWM is not a requirement to flash anything. It is highly recommended that you do create backups though (especially if you're new to this), in case something goes wrong while flashing stuff.
Click to expand...
Click to collapse
Thanks.
And with that, i will close this here, and advise further searching in the future (if you are willing to do something that can hose your phone, please take 10 minutes, and read the basic guides on what to do... it will be a life saver..)
I recently picked up a GP 4.2. I immediately got it rooted so now I'm running a 2.3.6 stock rom with root. What's the next step in terms of getting a recovery installed and maybe moving up to an ICS or JB rom? I've kind of poked around a bit but it's some what confusing with all the other types of GPs in the same area. Does anybody have a recovery and rom they'd recommend? Is using rom manager to push CWM feasible?
I would recommend the ChaOS ROM/Kernel which includes CWM. It is one of the few available ROMs for this device right now but offers a lot of great features. You can also install an S3 or Jelly Bean theme with the ChaOS ROM. Here's the link to the ROM: http://forum.xda-developers.com/showthread.php?t=2279806. I do not believe using ROM manager to push CWM is feasible on this device. Also, CM7 will most likely make it on to this device very soon. I would recommend watching for that in the near future. I know it can be a hassle trying to weed through the Galaxy Player forums to find 4.2 information but it's all we've got. Hope this helps and welcome to the SGP 4.2 community!
MetaMav said:
I would recommend the ChaOS ROM/Kernel which includes CWM. It is one of the few available ROMs for this device right now but offers a lot of great features. You can also install an S3 or Jelly Bean theme with the ChaOS ROM. Here's the link to the ROM: http://forum.xda-developers.com/showthread.php?t=2279806. I do not believe using ROM manager to push CWM is feasible on this device. Also, CM7 will most likely make it on to this device very soon. I would recommend watching for that in the near future. I know it can be a hassle trying to weed through the Galaxy Player forums to find 4.2 information but it's all we've got. Hope this helps and welcome to the SGP 4.2 community!
Click to expand...
Click to collapse
Thank you for the info Meta. I'm somewhere around the mid-high mid level with flashing and rooting but slogging through trying to find the right info for a GP 4.2 was getting a bit hectic. I think part of it was the way some people abbreviate the model compared to others. I just wanted to make sure I didn't brick the device.
I got it mainly for a perm, in-car music and GPS/navigation provider instead of always looking to my phone to do it. One thing I noticed about the rom, it mentions installing it via CWM. If I don't have CWM yet, can this rom get pushed by odin or do I have to get CWM first and then flash the rom?
NapalmDawn said:
Thank you for the info Meta. I'm somewhere around the mid-high mid level with flashing and rooting but slogging through trying to find the right info for a GP 4.2 was getting a bit hectic. I think part of it was the way some people abbreviate the model compared to others. I just wanted to make sure I didn't brick the device.
I got it mainly for a perm, in-car music and GPS/navigation provider instead of always looking to my phone to do it. One thing I noticed about the rom, it mentions installing it via CWM. If I don't have CWM yet, can this rom get pushed by odin or do I have to get CWM first and then flash the rom?
Click to expand...
Click to collapse
you should flash CWM via odin first and then flash the ROM via CWM
Would the instructions here be the right thing to do?
http://www.youtube.com/watch?v=-MbHDbjph8A
MetaMav said:
I would recommend the ChaOS ROM/Kernel which includes CWM. It is one of the few available ROMs for this device right now but offers a lot of great features. You can also install an S3 or Jelly Bean theme with the ChaOS ROM. Here's the link to the ROM: http://forum.xda-developers.com/showthread.php?t=2279806. I do not believe using ROM manager to push CWM is feasible on this device. Also, CM7 will most likely make it on to this device very soon. I would recommend watching for that in the near future. I know it can be a hassle trying to weed through the Galaxy Player forums to find 4.2 information but it's all we've got. Hope this helps and welcome to the SGP 4.2 community!
Click to expand...
Click to collapse
Do you know if CM will come to the 3.6 as well? And from what I understand, to get CWM on the 3.6 you have to flash a custom kernel?
NapalmDawn said:
Would the instructions here be the right thing to do?
http://www.youtube.com/watch?v=-MbHDbjph8A
Click to expand...
Click to collapse
Yes. Those instructions are correct. However, you do not need to run the adb dev tool like the person does in the beginning of video in order to boot into download mode. You can just hold the power, home, and down-volume button to boot the phone into download mode before using Odin. Zaclimon's CWM kernel can be found here (along with the wifi fix): http://forum.xda-developers.com/showthread.php?t=2198444 and installed with the instructions in the youtube video.
Xenphor said:
Do you know if CM will come to the 3.6 as well? And from what I understand, to get CWM on the 3.6 you have to flash a custom kernel?
Click to expand...
Click to collapse
From what I have read I know that SerkTheTurk is currently compiling CM for the 4.2. I would imagine either him or some other 3.6 dev will take up the task of CM for your device. And, the answer to your second question is yes, you do have to flash a custom kernel similar to how the 4.2 requires a custom kernel.
Hope that helps.
MetaMav said:
Yes. Those instructions are correct. However, you do not need to run the adb dev tool like the person does in the beginning of video in order to boot into download mode. You can just hold the power, home, and down-volume button to boot the phone into download mode before using Odin. Zaclimon's CWM kernel can be found here (along with the wifi fix): http://forum.xda-developers.com/showthread.php?t=2198444 and installed with the instructions in the youtube video.
From what I have read I know that SerkTheTurk is currently compiling CM for the 4.2. I would imagine either him or some other 3.6 dev will take up the task of CM for your device. And, the answer to your second question is yes, you do have to flash a custom kernel similar to how the 4.2 requires a custom kernel.
Hope that helps.
Click to expand...
Click to collapse
Ok thanks. I also have a question regarding flashing kernels. In the linux world (and other os world), randomly changing your kernel is a big no no that would lead to major compatibility issues. I don't understand how people can mix and match kernels, roms, firmware, bootloaders, recoveries and everything else? There won't be conflicts?
Regarding the kernel available for the 3.6: what do I do if I encounter stability issues with it and, say, the upcoming CM7? I wouldn't be able to go back to my original kernel because I didn't have CWM to back it up in the first place. Won't I be stuck with a potentially faulty kernel?
Xenphor said:
Ok thanks. I also have a question regarding flashing kernels. In the linux world (and other os world), randomly changing your kernel is a big no no that would lead to major compatibility issues. I don't understand how people can mix and match kernels, roms, firmware, bootloaders, recoveries and everything else? There won't be conflicts?
Regarding the kernel available for the 3.6: what do I do if I encounter stability issues with it and, say, the upcoming CM7? I wouldn't be able to go back to my original kernel because I didn't have CWM to back it up in the first place. Won't I be stuck with a potentially faulty kernel?
Click to expand...
Click to collapse
In changing kernels in the android world, you have mixed results. There are times a kernel can cause some issues but for the most part (we're talking like 98%), if an XDA dev posts a kernel and lets you know you can use it, you can trust it. These devs no matter the device spend painstaking hours ironing things out. Also, many of them have a select group of people testing the kernel for faults and issues. In a very active community, if a well known dev posts a kernel, you can trust it. HOWEVER...no matter what we think or believe or what we're told, every device is a unique and beautiful snowflake. Back up back up back up BACK UP BACK UP BACK UP your stuff. If you want to be super ULTRA safe, take the back up and download it to your PC or somewhere safe.
NapalmDawn said:
In changing kernels in the android world, you have mixed results. There are times a kernel can cause some issues but for the most part (we're talking like 98%), if an XDA dev posts a kernel and lets you know you can use it, you can trust it. These devs no matter the device spend painstaking hours ironing things out. Also, many of them have a select group of people testing the kernel for faults and issues. In a very active community, if a well known dev posts a kernel, you can trust it. HOWEVER...no matter what we think or believe or what we're told, every device is a unique and beautiful snowflake. Back up back up back up BACK UP BACK UP BACK UP your stuff. If you want to be super ULTRA safe, take the back up and download it to your PC or somewhere safe.
Click to expand...
Click to collapse
Well that's my dilemma because in order to backup my kernel I first need to flash the custom kernel to get CWM. What do I do?
Xenphor said:
Well that's my dilemma because in order to backup my kernel I first need to flash the custom kernel to get CWM. What do I do?
Click to expand...
Click to collapse
Just flash the cwm kernel because its basically the stock kernel but with cwm, and it shouldnt brick but if it does you can flash the stock kernel back again
Sent from my YP-GI1 using Tapatalk 2
SerkTheTurk said:
Just flash the cwm kernel because its basically the stock kernel but with cwm, and it shouldnt brick but if it does you can flash the stock kernel back again
Sent from my YP-GI1 using Tapatalk 2
Click to expand...
Click to collapse
Where could I find a stock kernel?
Xenphor said:
Where could I find a stock kernel?
Click to expand...
Click to collapse
US version: http://forum.xda-developers.com/showthread.php?t=1885374
International: http://forum.xda-developers.com/showthread.php?t=1884071
Sent from my YP-GI1 using Tapatalk 2
SerkTheTurk said:
US version: http://forum.xda-developers.com/showthread.php?t=1885374
International: http://forum.xda-developers.com/showthread.php?t=1884071
Sent from my YP-GI1 using Tapatalk 2
Click to expand...
Click to collapse
Ok thank you. However, will this work with YP-GS1?
But about kernels, on the webpage where I downloaded the stock rooted rom http://tau.shadowchild.nl/attn1/?p=166 it says specifically that the Wifi module in system and kernel must MATCH. This is what I'm talking about in regards to kernel compatibility with roms. How do I know if a kernel I'm downloading will have changes applied to it that will work with another rom like with this stock rom/kernel?
Well in order-I used odin to flash CWM. Once it rebooted, I saw the Galaxy SII boot anim. Used Rom Manager to have it boot to CWM. From there I flashed wifi fix, the rom and then the mod pack. My build number is gingerbread-ueld3. From what I can tell, I think I'm all done. At first I was like hrmmmmm. Doesn't look much different. When I hit the toggle bar though, I could tell it had changed. The process was all very simple after I got headed in the right direction with CWM. That was my only confusing start point for this.
Edit-my bad. The rom didn't take on the first flash. I could tell by the build number. Reflashing the rom and the s3 addons. Hrmmm. Might be boot looping. It's going through the comet and coming up to the white samsung, vibrates a few times after a bit and goes back to the comet with no sound.
NapalmDawn said:
Well in order-I used odin to flash CWM. Once it rebooted, I saw the Galaxy SII boot anim. Used Rom Manager to have it boot to CWM. From there I flashed wifi fix, the rom and then the mod pack. My build number is gingerbread-ueld3. From what I can tell, I think I'm all done. At first I was like hrmmmmm. Doesn't look much different. When I hit the toggle bar though, I could tell it had changed. The process was all very simple after I got headed in the right direction with CWM. That was my only confusing start point for this.
Edit-my bad. The rom didn't take on the first flash. I could tell by the build number. Reflashing the rom and the s3 addons. Hrmmm. Might be boot looping. It's going through the comet and coming up to the white samsung, vibrates a few times after a bit and goes back to the comet with no sound.
Click to expand...
Click to collapse
Well I had to flash this kernel http://forum.xda-developers.com/showthread.php?t=2198234 to get CWM on mine. I haven't actually flashed anything with CWM because there doesn't seem to be any good roms for the 3.6 unless CM7 comes out sometime. I used Odin to flash a stock rom from here http://tau.shadowchild.nl/attn1/?p=166
NapalmDawn said:
Well in order-I used odin to flash CWM. Once it rebooted, I saw the Galaxy SII boot anim. Used Rom Manager to have it boot to CWM. From there I flashed wifi fix, the rom and then the mod pack. My build number is gingerbread-ueld3. From what I can tell, I think I'm all done. At first I was like hrmmmmm. Doesn't look much different. When I hit the toggle bar though, I could tell it had changed. The process was all very simple after I got headed in the right direction with CWM. That was my only confusing start point for this.
Edit-my bad. The rom didn't take on the first flash. I could tell by the build number. Reflashing the rom and the s3 addons. Hrmmm. Might be boot looping. It's going through the comet and coming up to the white samsung, vibrates a few times after a bit and goes back to the comet with no sound.
Click to expand...
Click to collapse
Poop. I think I bootloped the sucker. I can use Odin to reflash the stock, rooted rom just like I did when I got it first rooted right? Do we have another rom for the 4.2 I could try flashing? Not sure why it has bootlooped. I even went back into CWM, did a factory reset, flashed only the rom (no addons) and same thing. Possible bad download? It is flashing from the internal SD as my CWM is not seeing my external SD.
NapalmDawn said:
Poop. I think I bootloped the sucker. I can use Odin to reflash the stock, rooted rom just like I did when I got it first rooted right? Do we have another rom for the 4.2 I could try flashing? Not sure why it has bootlooped. I even went back into CWM, did a factory reset, flashed only the rom (no addons) and same thing. Possible bad download? It is flashing from the internal SD as my CWM is not seeing my external SD.
Click to expand...
Click to collapse
I have been meaning to post this on the dev thread for awhile. I thought this problem might only be for certain people but I think it applies to US and maybe non-EU devices. I believe that the ChaOS ROM will bootloop on US (YP-GI1/XAA) devices if you do not install ChaOS's Enhanced Stock ROM (http://forum.xda-developers.com/showthread.php?t=2279450) for whatever reason. I spent days trying to install his ROM and bootlooping.
The way I successfully installed (if I remember correctly):
-Do a factory reset of rooted stock ROM
-Boot to CWM (meaning you have already flashed the custom kernel) and install ChaOS's Enhanced Stock (put all install files on internal SD)
-Boot to CWM, wipe davlick cache under "advanced", wipe cache partition, and install the ChaOS ROM
-Wait a little while and your device should boot up properly
I hope this works for you. If it doesn't let me know and I can help you further. If this does work for you too then I will post this on the ROM's thread for other users.
Xenphor said:
Well that's my dilemma because in order to backup my kernel I first need to flash the custom kernel to get CWM. What do I do?
Click to expand...
Click to collapse
SerkTheTurk said it very well, you do not need to worry, but if you also want to do a backup before you install the custom kernel you could use the adb tools on the computer to backup the device. I'm sure you could learn how to do that with a quick Google search.
MetaMav said:
I have been meaning to post this on the dev thread for awhile. I thought this problem might only be for certain people but I think it applies to US and maybe non-EU devices. I believe that the ChaOS ROM will bootloop on US (YP-GI1/XAA) devices if you do not install ChaOS's Enhanced Stock ROM (http://forum.xda-developers.com/showthread.php?t=2279450) for whatever reason. I spent days trying to install his ROM and bootlooping.
The way I successfully installed (if I remember correctly):
-Do a factory reset of rooted stock ROM
-Boot to CWM (meaning you have already flashed the custom kernel) and install ChaOS's Enhanced Stock (put all install files on internal SD)
-Boot to CWM, wipe davlick cache under "advanced", wipe cache partition, and install the ChaOS ROM
-Wait a little while and your device should boot up properly
I hope this works for you. If it doesn't let me know and I can help you further. If this does work for you too then I will post this on the ROM's thread for other users.
SerkTheTurk said it very well, you do not need to worry, but if you also want to do a backup before you install the custom kernel you could use the adb tools on the computer to backup the device. I'm sure you could learn how to do that with a quick Google search.
Click to expand...
Click to collapse
ell there's not really much point in backing up the kernel when I've already downloaded it on my computer.
I've since flashed KingOS rom and don't really notice any differences at besides a few color changes... what's all the hype about?
Xenphor said:
ell there's not really much point in backing up the kernel when I've already downloaded it on my computer.
I've since flashed KingOS rom and don't really notice any differences at besides a few color changes... what's all the hype about?
Click to expand...
Click to collapse
Xen-it seems GPlayer development is still fairly newish. the work you see from devs now are all ground work. For the 4.2 and 3.6, they seem a little less dev populated than the 4 and 5. People will build upon the work of early devs and eventually get kernels that can OC and maybe ICS and JB roms. At this stage, we likely won't see anything like ZOMG earth shattering until people spend time with the devices. Seems Serk is on his way to doing the best he can for 4.2 but I am not sure who is tackling 3.6
It's weird how roms for devices go. I learned this when I had a tbolt and shockingly saw a FUNCTIONAL JB rom for my old Eris while the tbolt was still hanging back in ginger land with not even a really good ICS rom let alone JB. I asked the Tbolt community-why? How is it the dinosaur Eris has JB and not us? It all depends on what the devs can do with the sources provided. Sometimes certain hardware points are sticky. you can have beautiful JB rom for a device that can't talk to the camera if the hardware source isn't made available (reference the HP TP for many years)
For now, flash what you're comfortable with and and learn what you do and don't like. Also learn if you want to play things safe and not experiment or take on potentially beta builds. For the tbolt, tackling an ICS rom was too dicey so I never did. On my new Rezound, I eat up JB roms as they are in much better shape
Hi all,
So my question is a pretty basic one, but obvious answer doesn't seem to be logical.
I just rooted my Verizon GS4 ME7, and installed SafeStrap 3.6x build, successfully, root achieved.
Now, my question is, I've tried installing the ROMs from other devs that state that they are TWRP compatible (because SS is TWRP based), yet none of them have booted successfully. So, if the problem exists because of a lack of compatibility (for a reason I'm not fully understanding), what is the point of having SS without any ROMs being compatible?
I'm willing to help a dev with coding or something to fix the problem, but idk what to look for or why this is happening?.
HELP!
Thanks!
beamer182 said:
Hi all,
So my question is a pretty basic one, but obvious answer doesn't seem to be logical.
I just rooted my Verizon GS4 ME7, and installed SafeStrap 3.6x build, successfully, root achieved.
Now, my question is, I've tried installing the ROMs from other devs that state that they are TWRP compatible (because SS is TWRP based), yet none of them have booted successfully. So, if the problem exists because of a lack of compatibility (for a reason I'm not fully understanding), what is the point of having SS without any ROMs being compatible?
I'm willing to help a dev with coding or something to fix the problem, but idk what to look for or why this is happening?.
HELP!
Thanks!
Click to expand...
Click to collapse
Just because its twrp compatible doesnt mean its SS compatible. Any rom that doesnt use the TW kernel wont work, so aosp roms are out of the question. What roms are you trying to install and stupid question, did you follow the install procedure outlined in the SS thread.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
hexitnow said:
Just because its twrp compatible doesnt mean its SS compatible. Any rom that doesnt use the TW kernel wont work, so aosp roms are out of the question. What roms are you trying to install and stupid question, did you follow the install procedure outlined in the SS thread.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Click to expand...
Click to collapse
So I guess that makes sense. I did follow the procedure outlined in the thread; to the T. I just tried the PACman ROM, SlimBut what are some roms that DO use the TW kernel? Because as far as I can tell, the only ROM that successfully flashes thus far is the HYPERDRIVE ROM, which is stock minus the bloatware and adding a few tweaks.
beamer182 said:
So I guess that makes sense. I did follow the procedure outlined in the thread; to the T. I just tried the PACman ROM, SlimBut what are some roms that DO use the TW kernel? Because as far as I can tell, the only ROM that successfully flashes thus far is the HYPERDRIVE ROM, which is stock minus the bloatware and adding a few tweaks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2448726
Hey everyone, this is my first post in the Verizon GN2 area. I just swapped my TMo GN2 for a BNIB Verizon Gn2, still has stock MC3. Popped in SIM to make sure all was good, it started to DL the OTA update, so I yanked the battery and SIM until I have it rooted. I have a lot of experience with rooting, ROMS and flashing, but with a same-but-different device, I would like the pro's here to give me a few pointers, if possible.
Best root method for a device with older firmware?
Is the ND7 radio flashable on older kernel\bootloader combos?
If you were in my shoes, what steps would you take to root and flash to keep maximum flexibility in the future?
Thanks to all the devs for their hard work, and thanks in advice for any pointers!
OwenW71 said:
Hey everyone, this is my first post in the Verizon GN2 area. I just swapped my TMo GN2 for a BNIB Verizon Gn2, still has stock MC3. Popped in SIM to make sure all was good, it started to DL the OTA update, so I yanked the battery and SIM until I have it rooted. I have a lot of experience with rooting, ROMS and flashing, but with a same-but-different device, I would like the pro's here to give me a few pointers, if possible.
Best root method for a device with older firmware?
Is the ND7 radio flashable on older kernel\bootloader combos?
If you were in my shoes, what steps would you take to root and flash to keep maximum flexibility in the future?
Thanks to all the devs for their hard work, and thanks in advice for any pointers!
Click to expand...
Click to collapse
1. Best root method for a device with older firmware?
To root and unlock the bootloader on stock 4.1.2, you need to use Adam Outler's CASUAL program found here: ( http://forum.xda-developers.com/showthread.php?t=2272066 ). The version of Casual that worked for me was R515.... just make sure you totally disable all virus scanning on your computer before running it... (you may need to kill processes in Task Manager to stop Window's Defender).
2. Is the ND7 radio flashable on older kernel\bootloader combos?
As far as radio’s/modems go... I know you can flash newer radios on the older ROM/kernel combos.... but I would probably just use the radio that's recommended in the thread for whatever custom ROM you plan to flash.
Here’s some links to where you can grab the radios:
--Grab Beanstown106’s modified ODIN flashable firmware package for MJ9 from the bottom of the first post in this thread: ( http://forum.xda-developers.com/showthread.php?t=2578458 )
--You can grab older recovery flashable radios/modems here: ( http://forum.xda-developers.com/showthread.php?t=2108510 )
--Here's a link for the ND7 4.4.2 RADIO (scroll down on the first post to find it under downloads). It is meant to be flashed in recovery, but it may be a good idea to ODIN flash Beanstown106's modified MJ9 firmware first.... ( http://forum.xda-developers.com/showthread.php?t=2765021 )
--Here's a thread with helpful steps on how to flash the modems in recovery: ( http://forum.xda-developers.com/showthread.php?p=43217826&highlight=install#post43217826 )
--Also, here's a link to a post with more detailed instructions on how to Odin flash the MJ9 firmware after you download and unzip the file... ( http://forum.xda-developers.com/showthread.php?p=50047714&highlight=unzip#post50047714 ).
-------------------------------------------------------------------
3. If you were in my shoes, what steps would you take to root and flash to keep maximum flexibility in the future?
If you flash any full stock builds newer than VRAMC3 4.1.2, then you'll end up locking the bootloader with no way to unlock it at this point (so don't ODIN flash full stock 4.3 or 4.4.2 or take OTA's if you want to keep the option to flash a custom recovery/kernel/etc...). Use the recovery flashable 4.3 and 4.4.2 based ROM's in the development threads if you want to experience features from those builds and maintain ability to unlock bootloader. In my personal experience, I've found 4.1.2 based ROM's to be the most stable for me with the fewest overall problems. I ran JellyBeans build 22 as my main "go to" ROM for a long time with no real problems.... (that was the last JellyBeans ROM that he put out with a 4.1.2 base before he moved on to 4.3 for that ROM. You can still grab the older JellyBeans build 22 from Beanstown106's Android File Host if you're interested.... just go to this thread: http://forum.xda-developers.com/showthread.php?t=2032447 -- and scroll down on the first post to find the link for the older builds).
I'd also recommend that you read through all the stickies in the development/general/help threads, just to get familiar with all the ins and outs of this phone. Especially check out droidstyle's Guide on – ( "How to Root/Rom/Return to Stock the VZW Galaxy Note II" ). This will save your butt if you mess something up and need to return to stock to start over.
Thanks for the info!
I think I will stick with the MC3 BL for now, and try to find a 4.4.2 flashable ROM that works well. Most of the ones I've looked at are saying they require the MJ9 or later BL...seems odd to require a locked bootloader. Recommendations are welcome, but I'm not against doing my homework. Thanks again for the reply and info. Already have root and flashed a few ROMs that did not make the grade, but will keep looking.
OwenW71 said:
Thanks for the info!
I think I will stick with the MC3 BL for now, and try to find a 4.4.2 flashable ROM that works well. Most of the ones I've looked at are saying they require the MJ9 or later BL...seems odd to require a locked bootloader. Recommendations are welcome, but I'm not against doing my homework. Thanks again for the reply and info. Already have root and flashed a few ROMs that did not make the grade, but will keep looking.
Click to expand...
Click to collapse
Mj9 is the radio. Never upgrade your bootloader or you will be locked.
Sent from my SCH-I605 using Tapatalk
@ OwenW71,
I know it's kind of confusing... but the link I gave you to Beanstown106’s modified MJ9 firmware package at: ( http://forum.xda-developers.com/showthread.php?t=2578458 )... it is not the official stock mj9 firmware... It's just needed for updating the radios/wifi to use when flashing custom 4.3+ ROM'S from the development threads.
Like michigan66 said... you don't want to take any OTA's for 4.3/4.4.2...or odin flash the official stock Verizon 4.3/4.4.2 firmware... because that will lock the bootloader with no way for you to unlock it.
mattnmag said:
@ OwenW71,
I know it's kind of confusing... but the link I gave you to Beanstown106’s modified MJ9 firmware package at: ( http://forum.xda-developers.com/showthread.php?t=2578458 )... it is not the official stock mj9 firmware... It's just needed for updating the radios/wifi to use when flashing custom 4.3+ ROM'S from the development threads.
Like michigan66 said... you don't want to take any OTA's for 4.3/4.4.2...or odin flash the official stock Verizon 4.3/4.4.2 firmware... because that will lock the bootloader with no way for you to unlock it.
Click to expand...
Click to collapse
So that thread says it is a full firmware package, but you're saying it will leave my bootloader alone? I'm not accustomed to seeing Odin packages that don't mess with the BL. According to the post, I flash the firmware with Odin, then use Recovery to flash the ROM? It did not state how the ROM is flashed.
It also looks like TWRP is not in favor right now, but it is the recovery that the jailbreak provides. Guess I should switch to Philz. Ah, so much to do...
THanks again!
OwenW71 said:
So that thread says it is a full firmware package, but you're saying it will leave my bootloader alone? I'm not accustomed to seeing Odin packages that don't mess with the BL. According to the post, I flash the firmware with Odin, then use Recovery to flash the ROM? It did not state how the ROM is flashed.
It also looks like TWRP is not in favor right now, but it is the recovery that the jailbreak provides. Guess I should switch to Philz. Ah, so much to do...
THanks again!
Click to expand...
Click to collapse
So where BeansTown106 says.... "You Need to Flash This Full Firmware Package Via Odin to get the new modem and to get wifi to work..."— for clarification, this is not factory stock Verizon firmware. Beanstown106 modified things and this is just the radio/wifi related portion. It will not change the VRAMC3 bootloader.
Yes, you will flash custom ROM'S via a zip file in custom recovery.... (you don't want to flash any custom ROM'S in Odin after using CASUAL-- see this thread for more about why: http://forum.xda-developers.com/showthread.php?p=35396049).
TWRP works fine for some ROM's and Philz or CWM is recommended for others. Most ROM threads recommend a recovery and I would just use whatever is recommended for the custom ROM that you decide to flash.
Okay, thanks! I was aware of the warning about using Odin for custom ROMs, so that is part of what gave me pause about flashing MJ9, in addition to the BL concern.
Thanks so much for the guidance. The stickies are good, but they did not really spell out the process for keeping an unlocked BL while still making my way up a more current firmware.
Honestly, guys like you make this forum a joy. I very briefly used the iPhone 5s that work gave me, and I was going ape****. I'm not an Apple hater, but iPhones suck. Slow, bad apps, bad gps, no customization. So glad to come back from the dark side! And with guys like this to help a fella out, can there be any question which side is on the side of light and goodness?
Cheers!
Sent from my SCH-I605 using XDA Free mobile app
Hello all,
I've rooted several phones in the past, but have been having more trouble with my verizon galaxy s4 than I have with the rest. Not so much with the processes themselves, those were easy, but with feeling comfortable with the guides I am using since there are so many different builds and versions.
I had stock NG6, I felt comfortable and succeeded in rooting using the kernel flash and downgrade method (http://forum.xda-developers.com/galaxy-s4-verizon/general/how-to-root-i545vrufng6-t2905848).
Now I'm looking to get a ROM backup of my current config (reflashed to NG6) or a stock ROM i can flash. I downloaded the ROM Manager CWM offers in the playstore, but when I ran it after install it requires a custom recovery, as per usual. I say "OK" and I end up with the following:
SAMSUNG
Samsung Galaxy S4 (Verizon)
jfltevzw
UNSUPPORTED DEVICE
Device not Listed Above
Click here if your device is not shown in the list above.
I was a little worried about the jfltevzw under the first option, since I was unable to find anything in the various information my phone tells me (build, kernel, etc) that matches that string.
Normally I never post unless I truly can't find anything... but I've spent about 2 hours looking through stickies and instructions here and on other sites for creating a recovery and installing SS/CyanogenMod, and I haven't had any luck. I've rooted quite a few devices and I use this forum as my go-to, so I was wondering if anyone could point me in the right direction?
dev info:
Carrier: verizon
model: I545
droid ver: 4.4.2
kernel: 3.4.0
baseband: I545VRUFNG6
status: rooted (from NG6 via flash to NC5 -> root w/ towelroot -> flash NG6)
any help is appreciated!
Thanks!
As of right now you can't install AOSP roms
Safestrap is the Only recovery you can use. No CWM, TWRP Or cyanogen or any other AOSP Roms. Look for the threads about safestrap with your ng6 . And Roms that work with safestrap. Hyper drive is a good one, along with several others.
Oh. And extremely limited for kernels.
wtherrell said:
Safestrap is the Only recovery you can use. No CWM, TWRP Or cyanogen or any other AOSP Roms. Look for the threads about safestrap with your ng6 . And Roms that work with safestrap. Hyper drive is a good one, along with several others.
Oh. And extremely limited for kernels.
Click to expand...
Click to collapse
OK. Will do, thanks!
Do you think it might be good to flash NC5 and stay there even though my phone was stock NG6? Not like I'm really concerned with the new stock features.
edit: the only thing bothering me so far rooting with the method i used is I haven't had any random reboots... some people were reporting upwards of 30/day and I haven't had a problem in ~4 hours. Seems inconsistent ><
I've been trying to install SS via flashing the NC5 first then installing, but I'm having a lot of crash/reboots attempting to get anything going on my phone.
there a version of SS that can be installed on NG6?
No different kernel, it won't install
Sent from my SCH-I545 using XDA Free mobile app
kongmingtwo said:
there a version of SS that can be installed on NG6?
Click to expand...
Click to collapse
You will need to Odin back to NC5 using the full wipe .tar then use the rooting method at the bottom of this OP in order for the safestrap app to work correctly: http://forum.xda-developers.com/galaxy-s4-verizon/general/how-to-root-i545vrufng6-t2905848
muniz_ri said:
You will need to Odin back to NC5 using the full wipe .tar then use the rooting method at the bottom of this OP in order for the safestrap app to work correctly: http://forum.xda-developers.com/galaxy-s4-verizon/general/how-to-root-i545vrufng6-t2905848
Click to expand...
Click to collapse
I don't actually have SS installed yet, working on that.
https://www.androidfilehost.com/?fid=95784891001611119
Safestrap 3.75v sch-I545 kitkat A03 for NG6