Are the ROMs that are available for the Verizon Note 2 baseband specific VRALJB or VRALL4? I did not update and I have noticed some of the newer version ROMs specifically say VRALL4 in their description.
I was in the same boat Friday...never took the OTA and wanted to get on beans8 (VRALL4 baseband). From everything I read it sounds like some people are running ROMs based on VRALL4 with baseband VRALJB. Although it seems to work, the idea of having a mismatch there made me nervous so I installed the new radio when I flashed the rom. Check out post 6191 below...user minazaki provided a great step by step. Worked like a charm.
http://forum.xda-developers.com/showthread.php?t=2032447&page=620
I just downloaded the radio and flashed it worked fine ..then found out beans updated so I flashed that lol good to go
Sent from my SCH-I605 using xda app-developers app
You're able to run either radio on either ROM-base.
Related
I haven't seen a thread for this yet and some people who are running old firmware don't know about this so I thought I'd post it for those that are running old firmware and want to flash ICS Roms without updating to the latest leak. This will work for any .22 based Rom I have tried it on so far. Some devs mention it, others don't. I do not know who made this patch but it came with Scroslers Cleanrom and I thank him for it. If you have constant reboots after flashing a .22 based rom, this is for you.
Hope this helps.
Cameron
every ics rom thread has a patch listed..... and for clearity... Joel was the brains behind the patch... while we may not of used his exact files he was the one that informed us of what files needed to be replaced
lllboredlll said:
every ics rom thread has a patch listed..... and for clearity... Joel was the brains behind the patch... while we may not of used his exact files he was the one that informed us of what files needed to be replaced
Click to expand...
Click to collapse
That may be but I still keep seeing people that don't know about it. So thought i would post it anyway. Doesnt surprise me that he thought of it. He's a genius. So thanks to him.
Sent from my ADR6425LVW using xda premium
How do i go about applying this patch? do i have to rename it something and flash in hboot/bootloader?
After the rim loads up, immediately reboot to recovery, flash in recovery
Sent from my ADR6425LVW using Tapatalk 2
roosxter said:
After the rim loads up, immediately reboot to recovery, flash in recovery
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
What is the rim? Ok so I boot into recovery. I have this patch on the root of my external sd i'm assuming. and using the amon ra recovery i just flash it like i would a rom?
edit: Nevermind! problem solved. i just flash using amon ra recovery as if it were a rom. sweet.
Yup and I meant rom lol
Sent from my ADR6425LVW using Tapatalk 2
roosxter said:
After the rim loads up, immediately reboot to recovery, flash in recovery
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Nah you just have to flash it before you boot into the Rom
Sent from my ADR6425LVW using Tapatalk 2
Ok i started with a stock rooted GB S-OFF with Amons 3.15 recovery
I then downloaded the firmware/radios/hboot combos from chilpill here
http://forum.xda-developers.com/showthread.php?t=1614366
i got the ICS-2.25-JB-5-7 zip then i flashed the NEW FIRMWARE PATCH
and then i got NEWTS RLS 1 ROM
Im getting alot of errors and the main one is HTCDM has stopped and wondering if i have done something wrong I have done and redone again and wiped twice to three times
My questions are and i so apologize because i know its been a wore out subject
But how to know which firmware I am on ??
example GB firmware is this number???
example ICS firmware is this number???
if im on GB firmware and want to goto ICS firmware do i need OLD or NEW FIRMWARE PATCH???
If im on ICS firmware and want to goto GB firmware do i need OLD or NEW FIRMWARE PATCH???
Like i said I am so sorry but it is confusing because you say to get old firmware patch to update to ICS but i thought it would be new firmware to go to ICS
carycooke said:
Ok i started with a stock rooted GB S-OFF with Amons 3.15 recovery
I then downloaded the firmware/radios/hboot combos from chilpill here
http://forum.xda-developers.com/showthread.php?t=1614366
i got the ICS-2.25-JB-5-7 zip then i flashed the NEW FIRMWARE PATCH
and then i got NEWTS RLS 1 ROM
Im getting alot of errors and the main one is HTCDM has stopped and wondering if i have done something wrong I have done and redone again and wiped twice to three times
My questions are and i so apologize because i know its been a wore out subject
But how to know which firmware I am on ??
example GB firmware is this number???
example ICS firmware is this number???
if im on GB firmware and want to goto ICS firmware do i need OLD or NEW FIRMWARE PATCH???
If im on ICS firmware and want to goto GB firmware do i need OLD or NEW FIRMWARE PATCH???
Like i said I am so sorry but it is confusing because you say to get old firmware patch to update to ICS but i thought it would be new firmware to go to ICS
Click to expand...
Click to collapse
If you flashed one of my ics hboot combos then you no longer need to flash the new/old firmware patch after flashing a ics Rom
And I haven't done this myself but flashing the new firmware patch on top of a gingerbread Rom should alow you to use ics firmware on a gingerbread Rom
As for that error I have no idea why your getting it, maybe a bad download or a app conflicting with something, afaik nothing with the firmware or firmware patches will cause that issue
Sent from my ADR6425LVW using Tapatalk 2
thanks superchilpil i do appreciate it tremendously
this might not be the best place for this but here goes.
i seen some talk that running ics roms on old firmware with patch is better the updating your firmware. i am s-off, ics with new firmware.
what are some of your thoughts on this?
neckbonest said:
this might not be the best place for this but here goes.
i seen some talk that running ics roms on old firmware with patch is better the updating your firmware. i am s-off, ics with new firmware.
what are some of your thoughts on this?
Click to expand...
Click to collapse
The simple phrase "if it ain't broke then don't fix it" applies here
If your not having any signal issues then don't upgrade
Sent from my ADR6425LVW using Tapatalk 2
Please bear with me, I'll readily admit that I'm a newb when it comes to flashing ROMs, etc. I rooted my TB with the all-in-one tool and loaded the ICS BAMF Leak. I presume this was essentially an RUU, since I didn't flash any separate radios or anything.
I'm looking for a different ICS ROM to flash, mostly due to the poor memory management on this build.
My question is this, and mainly for clarification- If I wipe/format everything except the SD card, I will have to FIRST flash the ROM, then flash the radio to get data working?
It was only a ROM, and radios don't come with roms but the ones you had when you rooted work with the leak.
To flash a new rom just do the same thing you did for the leak, i have never flashed a radio (except for testing the tool) in a year of having this phone.
trter10 said:
It was only a ROM, and radios don't come with roms but the ones you had when you rooted work with the leak.
To flash a new rom just do the same thing you did for the leak, i have never flashed a radio (except for testing the tool) in a year of having this phone.
Click to expand...
Click to collapse
Well, that's interesting. I installed the NuSense rom based off the ICS leak, and had to install the leaked radios to get data back.
either way, i got the rom flashed and the radio flashed and working.
Thanks for the rooting tool, BTW
ToastyZ71 said:
Well, that's interesting. I installed the NuSense rom based off the ICS leak, and had to install the leaked radios to get data back.
either way, i got the rom flashed and the radio flashed and working.
Thanks for the rooting tool, BTW
Click to expand...
Click to collapse
That is because santod modified the ril to work better with the leak radios. I get data just fine with the .19 radios.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
That is because santod modified the ril to work better with the leak radios. I get data just fine with the .19 radios.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
+1
Hi all, thanks for having such a helpful support forum. I just picked up a new Note 2 and it is on FW 4.1.1. I want to unlock and root/ROM and was wondering about the recommended sequence.
Should I first use Casual to unlock, or should I take the OTA (which I believe updates the bootloader) then unlock? Is there any benefit or detriment to using one way or the other? Thanks for any help.
Sent from my SCH-I605 using xda premium
Over in origional dev section adam has the new root,jailbreak, recovery for the new 4.1.2 ota. So if you want stock 4.1.2 with root and all that you would be safe to take the ota on stock then run CASUAL. I beleive either way your reallywanting 4.1.2 unlocked so you can have custom roms and ive seen some of the roms being updated for the vramc3 base anyhow. So if want you could run casual now with 4.1.1 that you have (you just picked it up so im assuming its all stock) and flash a cust9m rom that has 4.1.2 already implimented. cheak out the rooting/custom rom guide and the jailbreak thread and decide. In the end both paths will lead to the same place.
Just root/unlock 4.1.1 and flash a 4.1.2 VRAMC3 rom of choice in recovery...
Thanks for the help, I appreciate it. I thought it might be six of one half dozen of the other, but after recently going through OTA he11 on the DNA I'm really leery of any updates.
Sent from my SCH-I605 using xda premium
MunkinDrunky said:
Over in origional dev section adam has the new root,jailbreak, recovery for the new 4.1.2 ota. So if you want stock 4.1.2 with root and all that you would be safe to take the ota on stock then run CASUAL. I beleive either way your reallywanting 4.1.2 unlocked so you can have custom roms and ive seen some of the roms being updated for the vramc3 base anyhow. So if want you could run casual now with 4.1.1 that you have (you just picked it up so im assuming its all stock) and flash a cust9m rom that has 4.1.2 already implimented. cheak out the rooting/custom rom guide and the jailbreak thread and decide. In the end both paths will lead to the same place.
Click to expand...
Click to collapse
Yes, it was 4.1.1 stock. I took your advice and unlocked/rooted in 4.1.1. What is the difference in having a base of vrall4 vs. vramc3? I flashed Jelly Beans and am showing 4.1.2 on vrall4. If I went to a different ROM based on vramc3,would it cause any issues? Thanks for the help and sorry for the n00b questions or if they've been answered a lot, I haven't modded Samsung in a while.
Sent from my SCH-I605 using xda premium
eakeller said:
Yes, it was 4.1.1 stock. I took your advice and unlocked/rooted in 4.1.1. What is the difference in having a base of vrall4 vs. vramc3? I flashed Jelly Beans and am showing 4.1.2 on vrall4. If I went to a different ROM based on vramc3,would it cause any issues? Thanks for the help and sorry for the n00b questions or if they've been answered a lot, I haven't modded Samsung in a while.
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
Jelly Beans builds 15 and 16 are on the new base, VRAMC3, which is 4.1.2.
eakeller said:
Yes, it was 4.1.1 stock. I took your advice and unlocked/rooted in 4.1.1. What is the difference in having a base of vrall4 vs. vramc3? I flashed Jelly Beans and am showing 4.1.2 on vrall4. If I went to a different ROM based on vramc3,would it cause any issues? Thanks for the help and sorry for the n00b questions or if they've been answered a lot, I haven't modded Samsung in a while.
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
Many sites have a change log of all the changes that vramc3 brings to the Note 2. I flashed a stock vramc3 ROM that VZW pushed OTA. The only difference is that the Jelly Beans developer (beanstown106) rooted it, replaced the secure bootloader and made it flashable. So I've basically accepted the OTA but I'm still rooted and unlocked.
larry_thagr81 said:
Many sites have a change log of all the changes that vramc3 brings to the Note 2. I flashed a stock vramc3 ROM that VZW pushed OTA. The only difference is that the Jelly Beans developer (beanstown106) rooted it, replaced the secure bootloader and made it flashable. So I've basically accepted the OTA but I'm still rooted and unlocked.
Click to expand...
Click to collapse
Here's what I did: Stock 4.1.1 VRALL4 -> Unlocked/rooted with Casual --> Flashed Jelly Beans build 16
Now in my "About Phone" setup, i have this: Android version 4.1.2; Baseband version I605VRALL4; Build number JZO54K.I605VRAMC3
The build flashed just fine and it appears I'm on VRAMC3. However the baseband remains at VRALL4, I assume because JBeans doesn't update the baseband. Is there any reason to care about the "mismatch" between the baseband and the build? Should I go through the work to update the baseband, and if so what is the best method? I've been looking around the net and have found a bunch of conflicting answers to this question, so hopefully someone can straighten things out regarding the Note 2 specifically.
Thanks for the discussion.
Baseband is the modem. Just download and flash the zip.
Sent from my Note II using Tapatalk 2
eakeller said:
Here's what I did: Stock 4.1.1 VRALL4 -> Unlocked/rooted with Casual --> Flashed Jelly Beans build 16
Now in my "About Phone" setup, i have this: Android version 4.1.2; Baseband version I605VRALL4; Build number JZO54K.I605VRAMC3
The build flashed just fine and it appears I'm on VRAMC3. However the baseband remains at VRALL4, I assume because JBeans doesn't update the baseband. Is there any reason to care about the "mismatch" between the baseband and the build? Should I go through the work to update the baseband, and if so what is the best method? I've been looking around the net and have found a bunch of conflicting answers to this question, so hopefully someone can straighten things out regarding the Note 2 specifically.
Thanks for the discussion.
Click to expand...
Click to collapse
If you look at post #2 in the beans thread, there is a link to the new radio. Flash that and you will be completely up to date.
Sent from my SCH-I605 using Tapatalk 2
randy6675 said:
If you look at post #2 in the beans thread, there is a link to the new radio. Flash that and you will be completely up to date.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Thanks guys, found Scott's zip and flashed the baseband. Everything looks to be consistent, so I'm good.
Sent via Note2 with XDA Premium
My wife's Evo kept failing the 3.17 OTA so I moonshined it this week to allow her to get on latest firmware and software. She is stock other than S-off and root. I am fully aware that the firmware/radio and software are two different things. After getting S-off I flashed the current 3.17 bootloader firmware from Captain's thread and all went well and she is now on 1.13.11.0830 radio. Now I want to get her the software updates to move her from 3.16.651.xx to 3.17.651.4. My question is how to best do this. My thought is to flash the stock rooted deodexed rom but I didn't know if there was an alternative better way. Also, considering that an OTA upgrade of software is a dirty flash sort of, can I dirty flash stock rooted 3.17 over her current 3.16 without doing full wipe. Yes, I realize full wipe would be best and I am willing to do that if dirty flash is a mess. But, for time saving, is there any real danger in dirty flashing stock rooted 3.17 over her current stock rom with s-off and root? It just seems to me to be the rooted equivalalent of taking the OTA update.
Thanks for any advice.
evoimevo said:
My wife's Evo kept failing the 3.17 OTA so I moonshined it this week to allow her to get on latest firmware and software. She is stock other than S-off and root. I am fully aware that the firmware/radio and software are two different things. After getting S-off I flashed the current 3.17 bootloader firmware from Captain's thread and all went well and she is now on 1.13.11.0830 radio. Now I want to get her the software updates to move her from 3.16.651.xx to 3.17.651.4. My question is how to best do this. My thought is to flash the stock rooted deodexed rom but I didn't know if there was an alternative better way. Also, considering that an OTA upgrade of software is a dirty flash sort of, can I dirty flash stock rooted 3.17 over her current 3.16 without doing full wipe. Yes, I realize full wipe would be best and I am willing to do that if dirty flash is a mess. But, for time saving, is there any real danger in dirty flashing stock rooted 3.17 over her current stock rom with s-off and root? It just seems to me to be the rooted equivalalent of taking the OTA update.
Thanks for any advice.
Click to expand...
Click to collapse
Your firmware is updated.
Software is based on the rom you are running if you flash a 3.17 rom you will be updated in that area also.
As for dirty flashing it's not a good idea to dirty flash when going to a new base
thanks bigdaddy, I appreciate the response. Is there any downside to being on older software and newer firmware? I thought Captain TB or someone had said that the firmware and software are optimized to work together and shouldn't be out of sync. If that is the case I probably need to bite the bullet and go ahead and wipe and flash the stock rooted deodexed rom to get her the software update.
bigdaddy619 said:
Your firmware is updated.
Software is based on the rom you are running if you flash a 3.17 rom you will be updated in that area also.
As for dirty flashing it's not a good idea to dirty flash when going to a new base
Click to expand...
Click to collapse
Is it just me... Other than stock rooted 3.17, I'm not seeing any custom roms for this base. Im still using mean bean.
Sent from my EVO using xda app-developers app
lanewhit said:
Is it just me... Other than stock rooted 3.17, I'm not seeing any custom roms for this base. Im still using mean bean.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I think it is kind of what bigdaddy was saying and what CTB has said...3.17 is the software update that brought the firmware update if done OTA. I believe what CTB did was extract the firmware so people could update the radio/firmware without installing the OTA or stock 3.17 ROM. So, you can have latest radio/firmware with CM10.2 for instance. In my case, my wife wants to keep stock as much as possible so I was trying to figure out best way to get her to most recent stock software without taking it OTA. I think the way to do that is going to be to flash 3.17 stock rooted rom. As you mentioned I haven't seen many/any roms built from 3.17 source if it has even been released at all yet. I moved to CM roms long ago and haven't used any Sense roms since meanbean 3.09 which last I checked hadn't been updated in months. There are plenty of CM10.2 based ROMs available that have tons of updates and fixes. I left my wife's stock because otherwise I get blamed every time Sprint or htc messes something up. This way I can say I didn't touch her phone. By s-off and rooting it and installing stock rooted deodexed I am opening myself back up to her wrath but so be it. It's better than her telling me 4 times a day that her phones says an update is ready but fails every time she tries to install it OTA. It's all about path of least pain. LOL.
I would flash the new rooted base. As I mentioned before, I'm on mean bean 3.09 with the updated firmware from the Captains thread and all has been working great.
Sent from my EVO using xda app-developers app
lanewhit said:
I would flash the new rooted base. As I mentioned before, I'm on mean bean 3.09 with the updated firmware from the Captains thread and all has been working great.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Cool. Thanks for that info. I think I am going to do a twrp backup and a dirty flash of stock rooted first. I know that's not the best and most advisable route but dirty flashing is underrated. If things are wonky I will wipe and factory reset and flash again. Dirty flashing a new base on top of the old isn't THAT much different than getting the software update OTA. I trust dirty flashing more than I trust Sprint to be able to seamlessly deliver it. Probably do it tonight while she's asleep and see if she notices anything different tomorrow. I'll just blame Halloween spooks and goblins if things go wrong.
I got a used Note 2 that was already updated to the mj9 version with the locked bootloader. I rooted it using saferoot and installed safestrap.. Been trying out the mj9 roms and I like the ones I've used, but I want to know if there's a way to update this still awesome beast of a phone to nd7 or higher. I've downloaded the I605VRUFND7_I605VZWFND7_VZW.zip file from samroms, but it's still sitting untouched because I haven't seen anything definite.. I'm currently running Alliance build 26 mj9 version, but I also have build 30 nd7 version and Nephilim.STABLE.EMJ9.ROM.v8.0-FINAL-R3Ds.zip
downloaded and sitting on my sdcard with the official nd7 update from samroms..
Basically I wonder if I can just Odin the official samroms nd7? If there is a bootimg I need to delete first? Can I wipe and install the alliance build 30 for nd7?
I suppose mainly I want to get a newer Android version going and want to know the best way to go about it.. The phone isn't activated with Verizon, and I only use it on Wi-Fi, not as an actual phone..
Any tips, suggestions, or ideas are appreciated. Thanks in advance to the best community out there..
Sent from my SCH-I605 using XDA Free mobile app
The:Dude said:
I got a used Note 2 that was already updated to the mj9 version with the locked bootloader. I rooted it using saferoot and installed safestrap.. Been trying out the mj9 roms and I like the ones I've used, but I want to know if there's a way to update this still awesome beast of a phone to nd7 or higher. I've downloaded the I605VRUFND7_I605VZWFND7_VZW.zip file from samroms, but it's still sitting untouched because I haven't seen anything definite.. I'm currently running Alliance build 26 mj9 version, but I also have build 30 nd7 version and Nephilim.STABLE.EMJ9.ROM.v8.0-FINAL-R3Ds.zip
downloaded and sitting on my sdcard with the official nd7 update from samroms..
Basically I wonder if I can just Odin the official samroms nd7? If there is a bootimg I need to delete first? Can I wipe and install the alliance build 30 for nd7?
I suppose mainly I want to get a newer Android version going and want to know the best way to go about it.. The phone isn't activated with Verizon, and I only use it on Wi-Fi, not as an actual phone..
Any tips, suggestions, or ideas are appreciated. Thanks in advance to the best community out there..
Sent from my SCH-I605 using XDA Free mobile app
Click to expand...
Click to collapse
Since your bootloader is locked (and the bootloader is unlockable on 4.3+), the only options I can think of for you would be to.... 1). either stay on 4.3 MJ9 with Safestrap and use 4.3 stock based roms - OR - 2). upgrade the phone to stock 4.4.2 and then root it with Ghettoroot and use Safestrap to run 4.4.2 stock based ROM's. (Due to having a locked bootloader-- you are forced to use stock based ROM's that use the stock kernel when using Safestrap). So, if your phone is on a 4.3 based bootloader - you have to stay with 4.3 based stock ROM's. Once you go to 4.4.2, you have to stay with 4.4.2 stock based ROM's.
My Note 2 is still on the 4.1.2 bootloader, so I haven't personally had to use Safestrap on the Note 2.... but I've read where others say that they've successfully used Safestrap on 4.4.2 after getting the phone rooted.
Personally, I prefer 4.3 to 4.4.2 on my Note 2. I could never find a 4.4.2 based ROM that didn't have some sort of bug that drove me crazy(ier). Either the bluetooth audio would stutter, I would get a lot of lagging with the UI, or would get poor battery life. However, many others report having good success with 4.4.2, so you might be happy with upgrading. I actually decided to come back to the 4.3/MJ9 based Jett ROM v. 3.0, as it does everything that I want in a ROM, works well with my Sony SW3 smartwatch, and runs very stable with great battery life. If you haven't tried out Jett ROM yet, you might want to give it a try (you can find it in the development forum).
Since your phone isn't activated - you obviously won't be getting OTA's, so you'll have to use ODIN if you want to upgrade. If you do decide to upgrade the phone to 4.4.2, you won't be able to return to 4.3 again due to the locked bootloader issue. Also.... if you upgrade 4.4.2, you may want to restore back to total stock 4.3 first and make sure it's wiped clean with a factory reset-- just to make sure nothing is leftover that could mess up the upgrade to 4.4.2.
Good luck!
Hey mattnmag, thanks for the info! It was a good read, and I didn't realize that if I upgraded to kit kat I wouldn't be able to downgrade back to jellybean if I didn't like it.. I've still got all the files I need except for the mj9 stock firmware, so I'll have to dl that before I get too crazy with this thing..
But I did dl the Jett ROM, and I'm gonna give that a run later tonight probably.. Just gotta get my backups onto the PC first just in case.. I hate doing full wipes though.. Because I'm lazy and don't like reinstalling everything lol..
What I'd really like it's too have my cyanogenmod back.. I had that on my old Droid RAZR and loved it..
Sent from my SCH-I605 using XDA Free mobile app