[Q] Changing ROM - Verizon Samsung Galaxy Note II

Hey guys. I posted a few days ago with a question about restoring my dad's phone to stock for warranty and this got me thinking about making some changes to my phone as well. I'm currently on Beans rom (Now called Alliance I believe) build 21. I'm thinking about trying out CM11 which I believe is Android 4.4. I went to the CM website to check out a guide on how to do this and came across this: http://wiki.cyanogenmod.org/w/Install_CM_for_i605
This guide APPEARS to be written for Note 2's that took the OTA that locked the bootloader. I still have an unlocked bootloader on Beans rom. So my question is do I need to bother with all the steps in that guide? Or is that only if bootloader is locked? Do I need Heimdall or Clockworkmod Recovery? Can I just use TWRP that I already have and do a data/cache wipe and flash the CM11 Rom? Any firmware files needed? Since my current rom is only Android 4.1.2? The Alliance rom thread says to flash MJ9 firmware before flashing their rom but I see no mention of it in the CM guide.
Thanks so much. You guys are the best!

Related

[Q] Question regarding stock roms / flashing

Hello,
Long time reader here. I finally made an account recently because I finally wanted to Root my phone and mess around with Cyanogenmod.
My question is this: I have an unlocked, unbranded Samsung GT-i9300 that I purchased from Newegg back in the summer time and I have still yet to receive any sort of update (still on 4.0.4). Can someone explain to me the whole stock updates scenario? I would have thought buying an unlocked, unbranded phone I would have at least gotten updates faster than the Verizon S3. Now.. I know I can flash Cyanogenmod and be done with it. Which I have which leads me to the last question. What happens if I flash my phone with the 4.1.2 stock rom that was just released in Poland recently? Will it work? Why wouldn't it? Does the baseband really matter as far as compatibility? (PDA? CSC?)
Thank you for your time.
I answered my own questions. Thanks for looking
I was so excited I forgot to elaborate a little.
I was successfully able to root my phone using cf root / odin, install clockworkmod recovery, install cyanogenmod 10 then re-flash back to stock using triangleaway, and a stock rom from samsung firmware using odin.
I had thought I bricked my phone when it was in an endless loop on the splash screen but I was able to get into android recovery mod and do a format/wipe/clean cache. *phew*

[Q] Question about updating android version from 4.04 having flashed Omega 9.xx

EDIT: [SOLVED] - For anyone following in my footsteps, ROM Manager is useless when flashing between android versions. You need to perform a wipe first so back up apps, SMS and internal SD card files. These threads were most helpful:
OFFICIAL OMEGA FAQ: http://forum.xda-developers.com/showpost.php?p=32864050&postcount=27478
ONE STOP GUIDE TO FLASHING S3: http://forum.xda-developers.com/showthread.php?p=32664054
Hi there,
A year ago I rooted and flashed my phone to Omega 9.xx from stock. Unfortunately, I haven't paid attention to anything since and have only just realised I'm still running 4.04 and a really outdated custom ROM.
So my question is how do I update to Jellybean 4.12/4.22?
I tried flashing to Cyanogenmod using ROM Manager/CWM Touch recovery yesterday to no avail. I got as far as the boot screen where it would stick so I had to restore my nandroid back up.
Is this due to compatibility with my outdated Android version? Do I need to update it before flashing a new custom ROM? I was under the impression flashing the new ROM would auto-update android from 4.04-4.14 - am I mistaken? Details in my signature and my provider is vodafone UK.
Thanks in advance for you help - it's much appreciated.
Kind regards,
Kelevra7
kelevra7 said:
Hi there,
A year ago I rooted and flashed my phone to Omega 9.xx from stock. Unfortunately, I haven't paid attention to anything since and have only just realised I'm still running 4.04 and a really old ROM.
So my question is how do I update to Jellybean 4.12/4.22?
I tried flashing to Cyanogenmod using ROM Manager/CWM Touch recovery yesterday to no avail. I got as far as the boot screen where it would stick so I flashed my nandroid back up.
Is this due to compatibility with my old Android version? Do I need to update it before flashing a new custom ROM? I was under the impression flashing the new ROM would auto-update android from 4.04-4.14 but I think I may be mistaken. Details in my signature and my provider is vodafone UK.
Thanks in advance for you help - it's much appreciated.
Kind regards,
Kelevra7
Click to expand...
Click to collapse
General > Sticky Roll-up Thread > Understanding the basics before rooting
EDIT: [SOLVED] - For anyone following in my footsteps, ROM Manager is useless when flashing between android versions. You need to perform a wipe first so back up apps, SMS and internal SD card files. These threads were most helpful:
OFFICIAL OMEGA FAQ: http://forum.xda-developers.com/show...ostcount=27478
ONE STOP GUIDE TO FLASHING S3: http://forum.xda-developers.com/show...php?p=32664054
rootSU said:
General > Sticky Roll-up Thread > Understanding the basics before rooting
Click to expand...
Click to collapse
Hi,
Thanks for the link. I read the entire first post but am still having a little trouble understanding where to go from here.
Do I need to flash my stock ROM before flashing a custom ROM? This part of your guide suggests I do not:
However, if you immediately plan on flashing a ROM, there's no need to root your existing ROM. Simply skip straight to installing a recovery. Backup then flash what you like.
Click to expand...
Click to collapse
So perhaps I just need to flash a custom ROM using CWM. But I tried this and it didn't work. I have searched a multitude of forums (spent 8+ hours) but to no avail. Nothing specifically references how to update from an old android version/custom ROM.
I have backed up my apps and system data with Titanium backup, got a nandroid backup, installed ROM Manager and Mobile Odin Lite (with the kernel add on) and tried flashing cyanogenmod9 using CWM but it failed - if you could just drop me a line pointing me in the right direction, I'd really appreciate it.
Kind regards,
Kelevra

4.3 OTA and custom Kernel question

Hello, as my thread title suggests I have a question about custom kernels. I made the mistake of updating to 4.3 on my device [I did it for the TRIM feature but wasnt aware of the cons Verizon put in place with 4.3], before 4.3 I was rooted and was using the stock OS and kernel. I do know that its possible to get Root access with 4.3 and Ive already done that - My question is if it is possible to install a custom kernel that will allow me to overclock this device ? I know there are a ton of kernels out there, but I dont want to risk bricking this device or having to download the ODIN 1GB+ 4.3 android file to bring it back to life..Thanks in advance!
Unfortunately, you cannot install a custom kernel. You would need to have an unlocked bootloader to install custom kernels.... and there's no current do it yourself method to unlock the 4.3 MJ9 bootloader.
4.1.2 was the last Android build for our phones where you could have unlocked the bootloader.... and so far, it doesn't look like there's going to be a method developed for 4.3.
mattnmag said:
Unfortunately, you cannot install a custom kernel. You would need to have an unlocked bootloader to install custom kernels.... and there's no current do it yourself method to unlock the 4.3 MJ9 bootloader.
4.1.2 was the last Android build for our phones where you could have unlocked the bootloader.... and so far, it doesn't look like there's going to be a method developed for 4.3.
Click to expand...
Click to collapse
That sucks...I dont think there is a way to go back to 4.1.2 either. Thanks for answer anyways.

Galaxy S3 Downgrade CM 11 - 10.1 i747

I have been a long time lurker on these forums, and to start on here would like to thank all the helpful posts I have read. Currently I am using a Galaxy SIII (i747). I'm not sure what firmware I got it on, however I downloaded the CM installer from the website and used it to flash my phone. It currently is on a really unstable CM11 build (kind of mad the installer pushed a non-RC to my phone) and I would like to downgrade to CM10.x. I checked the d2att wiki and there are no RC or stable CM 11 builds. From what I read there was a bootloader introduced in 4.3 that locked down the phone. I'm not sure if a) I have this locked down bootloader? I currently have TWRP installed, which I think a locked bootloader would prevent. b) Is it safe for me to try and downgrade to CM 10 with ODIN? Any help would be much appreciated.
jdkuki said:
I have been a long time lurker on these forums, and to start on here would like to thank all the helpful posts I have read. Currently I am using a Galaxy SIII (i747). I'm not sure what firmware I got it on, however I downloaded the CM installer from the website and used it to flash my phone. It currently is on a really unstable CM11 build (kind of mad the installer pushed a non-RC to my phone) and I would like to downgrade to CM10.x. I checked the d2att wiki and there are no RC or stable CM 11 builds. From what I read there was a bootloader introduced in 4.3 that locked down the phone. I'm not sure if a) I have this locked down bootloader? I currently have TWRP installed, which I think a locked bootloader would prevent. b) Is it safe for me to try and downgrade to CM 10 with ODIN? Any help would be much appreciated.
Click to expand...
Click to collapse
I also have an ATT S3 (I747) - It's running flawlessly on CM 10.2.1 (4.3) with the UCUEMJB bootloader (which can not be downgraded at this time to my knowledge). It also has TWRP 2.8.1.0 installed. I used this to downgrade from CM11 to CM 10.2.1 by restoring thru TWRP.
So, you should be good to go. Just make a Nandroid backup using TWRP and then flash CM 10.2.1 (zip file) using TWRP.
BTW - the MJB bootloader can not be downgraded. The MJ2 and earlier bootloaders (prior to 4.3) can be. I believe this is what you're referring to as "locked"???
Hope this helps . . .

need some advice

Hi my step son has this phone running blisspop 5.1.1 I want to update his phone to marshmallow. Can I just flash the latest cm 13 or should I odin back to stock and update that way then go through the rooting process? Im not sure if the bootloader and radio and kernel should be updated the stock way first.
I do know with my note 2 I could just flash the latest cm and flash the radio seperate. But this phone is a little foreign to me.
mojorisin7178 said:
Hi my step son has this phone running blisspop 5.1.1 I want to update his phone to marshmallow. Can I just flash the latest cm 13 or should I odin back to stock and update that way then go through the rooting process? Im not sure if the bootloader and radio and kernel should be updated the stock way first.
I do know with my note 2 I could just flash the latest cm and flash the radio seperate. But this phone is a little foreign to me.
Click to expand...
Click to collapse
Currently all the CM-13.0 based ROMs cannot boot with the official marshmallow bootloader. So it would be better to just clean flash the latest CM 13
Good thing I asked. I'm sure the cm team will figure that out at some point. It's actually the reason I asked because I remember on my note 2 going from JB mr1 to mr2 Samsung implemented Knox and sxrewed up everything. Dam girls phone was stock so I did the over he air update this morning. Oh well she doesn't really care anyway.
it's not like you'll wait long for CM to work with the latest bootloader https://review.cyanogenmod.org/#/c/146515
EDIT: it's not like you cant update either, just install CM13 WITHOUT updating stock (which will include the bootloader), aka if you're G900TUVS1FOL1 or older, then CM13 (marshmallow) should work as it has been for the last 5 months

Categories

Resources