I odin'd back to stock VRALJB from my note running cm10.1 and then took the 2 OTA updates all the way up to VRAMC3. then when I saw CASUAL didn't work (then) with VRAMC3 I tried to Odin back to VRALJB again and this time it failed half way through.
so now when i boot up it says my Baseband is VRALJB but the Build number field ends in VRAMC3.
Repeated attempts at using the Odin process documented in the sticky on this site fail the same way.
Also, the new CASUAL fails with the phone hanging the same way while trying to DL firmware.
Any ideas on how to get the phone back to a 'normal' state?
amghoon said:
I odin'd back to stock VRALJB from my note running cm10.1 and then took the 2 OTA updates all the way up to VRAMC3. then when I saw CASUAL didn't work (then) with VRAMC3 I tried to Odin back to VRALJB again and this time it failed half way through.
so now when i boot up it says my Baseband is VRALJB but the Build number field ends in VRAMC3.
Repeated attempts at using the Odin process documented in the sticky on this site fail the same way.
Also, the new CASUAL fails with the phone hanging the same way while trying to DL firmware.
Any ideas on how to get the phone back to a 'normal' state?
Click to expand...
Click to collapse
Just went through the same thing.. but didn't accept OTA's which you should never... When you say back to "normal" state.. you are bone stock now aren't you? no root, bc you say CASUAL fails.. So what exactly are you asking? I don't think you can use Odin to downgrade from a stock not rooted device. I believe to downgrade you have to be rooted and unlocked which you are not correct? I would say you would have to wait until Adam updates CASUAL (which I think he has for VRAMC3 http://forum.xda-developers.com/showthread.php?t=2272066
lacoursiere18 said:
Just went through the same thing.. but didn't accept OTA's which you should never... When you say back to "normal" state.. you are bone stock now aren't you? no root, bc you say CASUAL fails.. So what exactly are you asking? I don't think you can use Odin to downgrade from a stock not rooted device. I believe to downgrade you have to be rooted and unlocked which you are not correct? I would say you would have to wait until Adam updates CASUAL (which I think he has for VRAMC3 http://forum.xda-developers.com/showthread.php?t=2272066
Click to expand...
Click to collapse
As I said, I didn't take the OTA's until after I had odin'd back to stock. They installed fine- it was only when I tried to Odin again back to VRALJB that I was unable to have it complete and now the device is reporting it has the Baseband for VRALJB and the 'OS' from VRAMC3.
I pasted the CASUAL log up on Adam's CASUAL thread, so mabye he'll be able to help me jailbreak it again. But I think the Odin and CASUAL problems may be related because it hangs on both while trying to download firmware to the phone.
Maybe the first step would be to get the baseband to match the Build Number? And if you can't revert the build back to VRALJB then I guess the only option would be to try to flash the radio back to VRAMC3... which I'm not sure how to do with stock recovery.
You can't flash over the bootloader included with the newest OTA. That is why it isn't working.
imnuts said:
You can't flash over the bootloader included with the newest OTA. That is why it isn't working.
Click to expand...
Click to collapse
Hey I saw your post on another forum for a recovery flashable VRAMC3 radio- do you have a version that's flashable through Odin?
I'm thinking if I get the radio back to VRAMC3 maybe the new CASUAL will work...
amghoon said:
Hey I saw your post on another forum for a recovery flashable VRAMC3 radio- do you have a version that's flashable through Odin?
I'm thinking if I get the radio back to VRAMC3 maybe the new CASUAL will work...
Click to expand...
Click to collapse
Unless there is an unlock method for the latest OTA out, changing the radio won't do anything.
Don't know if it helps but the new Casual did work for me. But I was bone stock VRAMC3 (latest OTA). It worked for me. YMMV. Check my signature for link.
amghoon said:
As I said, I didn't take the OTA's until after I had odin'd back to stock. They installed fine- it was only when I tried to Odin again back to VRALJB that I was unable to have it complete and now the device is reporting it has the Baseband for VRALJB and the 'OS' from VRAMC3.
I pasted the CASUAL log up on Adam's CASUAL thread, so mabye he'll be able to help me jailbreak it again. But I think the Odin and CASUAL problems may be related because it hangs on both while trying to download firmware to the phone.
Maybe the first step would be to get the baseband to match the Build Number? And if you can't revert the build back to VRALJB then I guess the only option would be to try to flash the radio back to VRAMC3... which I'm not sure how to do with stock recovery.
Click to expand...
Click to collapse
did you flash the VRALJB alternate restore file that does not contain a bootloader?
droidstyle said:
did you flash the VRALJB alternate restore file that does not contain a bootloader?
Click to expand...
Click to collapse
i was just on the latest ota, flashed the alternate VRALJB and then the original VRALJB, now i am on VRALJB if it helps.
Related
OK so here is the story and I was debating if this is the right place to post but I do feel it is more on the developing side. I originally rooted and unlocked my bootloader following Casuals method and everything was just fine. I had an option to sell the phone in preparation for buying the GS4 so I used the return to stock method posted in the forums to return my device completely to stock. After doing so everything was also fine. I received an update to LL4 and that went OK straight from Verizon but last night when the VRAMC3 update was pushed to my phone it soft bricked it. It ultimately was stock on the splash screen stating Samsung Note 2. After trying to ODIN back to stock with multiple FAILS I was able to get it back to the Root66 MR Robinson by using the pit file but every time I try to update and or root/unlock bootloader it soft bricks again. I am assuming that the update that was pushed updated my bootloader and as of now I am stuck till there is a new bootloader Jailbreak. If not I would love some instruction on how to get my phone rooted with an unlocked bootloader or a flashable ODIN file that will at least get me to the latest VRAMC3 fully stock ROM. Thank you for the HELP.
Next time read the stickies...when they say NOT to accept OTA updates, usually there is some meaning behind it.
Shawnkanan said:
OK so here is the story and I was debating if this is the right place to post but I do feel it is more on the developing side. I originally rooted and unlocked my bootloader following Casuals method and everything was just fine. I had an option to sell the phone in preparation for buying the GS4 so I used the return to stock method posted in the forums to return my device completely to stock. After doing so everything was also fine. I received an update to LL4 and that went OK straight from Verizon but last night when the VRAMC3 update was pushed to my phone it soft bricked it. It ultimately was stock on the splash screen stating Samsung Note 2. After trying to ODIN back to stock with multiple FAILS I was able to get it back to the Root66 MR Robinson by using the pit file but every time I try to update and or root/unlock bootloader it soft bricks again. I am assuming that the update that was pushed updated my bootloader and as of now I am stuck till there is a new bootloader Jailbreak. If not I would love some instruction on how to get my phone rooted with an unlocked bootloader or a flashable ODIN file that will at least get me to the latest VRAMC3 fully stock ROM. Thank you for the HELP.
Click to expand...
Click to collapse
I had the same problem. Flash the pit file with odin and wait for the phone to turn on. the problem is fixed to get the phone working. Then you can flash other stuff.
Thank you for the replies even though one was not helpful at all. I have flashed the root66 file with the pit and it does work but if I try to run the casual jailbreak or flash any other odin files it fails. My assumption is my bootloader got updated and has locked me out and I will just have to wait for a new boot loader exploit. Thanks
Sent from my SCH-I605 using xda premium
droidstyle said:
Next time read the stickies...when they say NOT to accept OTA updates, usually there is some meaning behind it.
Click to expand...
Click to collapse
Is best advice u can get to avoid unwanted situations
XT912 CDMA
1droidmod said:
Is best advice u can get to avoid unwanted situations
XT912 CDMA
Click to expand...
Click to collapse
No I can give more, but I get tired of repeating myself all the time...especially when its posted in every section of this sub forum.
Read Read, Search Search... U will figure it out..
XT912 CDMA Pac Man 4.2.2
1droidmod said:
Read Read, Search Search... U will figure it out..
XT912 CDMA Pac Man 4.2.2
Click to expand...
Click to collapse
Is there a sticky or something definitive on the subject of rooted (via Casual) Verizon Note 2 users getting the OTA update and retaining root? I'm currently VRALL4, rooted via Casual, with SDM frozen to avoid the OTA update. But I'd rather not stay in this state indefinitely.
madtowner11 said:
Is there a sticky or something definitive on the subject of rooted (via Casual) Verizon Note 2 users getting the OTA update and retaining root? I'm currently VRALL4, rooted via Casual, with SDM frozen to avoid the OTA update. But I'd rather not stay in this state indefinitely.
Click to expand...
Click to collapse
Once you are rooted via Casual there is no such thing as accepting Verizon's OTA if you want your phone to keep working. (This info can be found in 1 or 2 basic searches, which everyone should do first.)
If you want to get the 4.1.2 features there are 3 options that I know of: 1) flash a zip of the 4.1.2 update, 2) flash a full 4.1.2 stock rom, or 3) flash a custom rom that has 4.1.2 features in it. You can find all 3 options in the Original Development section of xda. Imnuts has implemented #1 but read the forum on the ins and outs. Beanstown106 has created #2. And Beanstown106's latest Jellybeans 16 is a custom rom that incorporates 4.1.2.
Ok, so I have my Verizon Galaxy Note 2 on VRALJB and Im trying to unlock my bootloader. Everything goes smooth up until i get to the Casual part. So basically, I did root and unlock me now and it went through it but when it rebooted, it just rebooted my device, it did not go into unsecure bootloader mode? And I don't know what to do now. My phone still works fine like i can access it and everything and technically my phone is not rooted yet (according to root checker). I don't know what to do! Please help! I want to root my phone but not damage it.
Here is what it says in Casual:
[x]Ready for exploit
/system/bin/sh: su: not found
norootDEVICE IS NOT ROOTED! ROOT YOUR DEVICE! Install any VRALJB ROM --Adam Outler
Can anyone help me please? I know that this was the root i had to do since i never took an ota update ever. Can any help I really wanna get roms on my phone!
What update are you on? VRALL4 or VRAMC3? The easiest way to do this would be to use the latest version do CASUAL, No You Verizon.
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
What update are you on? VRALL4 or VRAMC3? The easiest way to do this would be to use the latest version do CASUAL, No You Verizon.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
I said it in my thread, its VRALJB (the first update ever to be released on the phone).
EDIT: I have also mentioned using Casual and ODIN. I did the correct root procedure and search up the VRALJB procedure.
Sorry I am bumping but I really want to be unlocked and rooted and I just cant with casual giving me this error and such. It also gives me an error before sayign cannot open /system/bh su. Or something like that. Can anyone help?
Here is a screenshot of Casual:
http://gyazo.com/d033b72d43d56d2126d6bc20171ed2f0
are you using the unlock method for vraljb found here:
http://forum.xda-developers.com/showthread.php?t=2043636
AldenIsRad said:
I said it in my thread, its VRALJB (the first update ever to be released on the phone).
EDIT: I have also mentioned using Casual and ODIN. I did the correct root procedure and search up the VRALJB procedure.
Click to expand...
Click to collapse
to be clear you have never updated past vraljb? the reason i ask is, if you ever took a update past vraljb, then you must use that unlock method....it does not matter what you currently are on. so if you took the vramc3 ota update then odined back to vraljb for whatever reason, then you must use the mc3 unlock method.
droidstyle said:
to be clear you have never updated past vraljb? the reason i ask is, if you ever took a update past vraljb, then you must use that unlock method....it does not matter what you currently are on. so if you took the vramc3 ota update then odined back to vraljb for whatever reason, then you must use the mc3 unlock method.
Click to expand...
Click to collapse
I never took an update past VRALJB. But I think I may have fixed the problem, I just flashed a stock rooted rom file and what may have seemed to be the problem was in odin, it said my system status was custom. But now its normal after stock rooted rom file. All I will have to do is unlock it. Will the VRAMC3 unlock work? I heard it still works for older android versions.
Good Morning everyone. I need to flash back to 4.1.2 to get my phone looked at. Is it possible to re-root after I get my phone back? I see people are having problems using casual and getting a partition 60 missing? or something on that order any help would be greatly appreciated.
jimbo15482 said:
Good Morning everyone. I need to flash back to 4.1.2 to get my phone looked at. Is it possible to re-root after I get my phone back? I see people are having problems using casual and getting a partition 60 missing? or something on that order any help would be greatly appreciated.
Click to expand...
Click to collapse
When you say "flash back to 4.1.2", do you mean just flash a stock 4.1.2 ROM, or use ODIN to restore your phone to factory locked condition?
As long as the phone does not accept the 4.3 OTA then casual will still work. If the 4.3 OTA gets installed on your phone, then you will not be able to unlock the bootloader again. You can still achieve root access, but not unlock, which will prevent you from being able to install custom roms.
I just want to make sure I've got this right. I've done the VRUEMJ9 4.3 OTA update. If I flash back to the stock VRAMC3 4.1.2 build using ODIN, I still won't be able to unlock my bootloader?
If so, I wish I'd known this before I took the OTA update. On my old phone, I could just sbf to an older build and that took care of any problems. I thought that it would be the same with this phone, but I guess not. Frustrating.
GreenRaccoon said:
I just want to make sure I've got this right. I've done the VRUEMJ9 4.3 OTA update. If I flash back to the stock VRAMC3 4.1.2 build using ODIN, I still won't be able to unlock my bootloader?
If so, I wish I'd known this before I took the OTA update. On my old phone, I could just sbf to an older build and that took care of any problems. I thought that it would be the same with this phone, but I guess not. Frustrating.
Click to expand...
Click to collapse
That is the case, unfortunately. From the research I've done it would seem the bootloader on this device cannot be downgraded. The files we have available to flash via ODIN do not change the bootloader, they are not full images. And yes it is frustrating, several of my family members were not the happy with the 4.3 OTA and were ready to take the custom ROM plunge, too late.
Jiggabitties said:
That is the case, unfortunately. From the research I've done it would seem the bootloader on this device cannot be downgraded. The files we have available to flash via ODIN do not change the bootloader, they are not full images. And yes it is frustrating, several of my family members were not the happy with the 4.3 OTA and were ready to take the custom ROM plunge, too late.
Click to expand...
Click to collapse
Is there a way to track down the full bootloader img for older versions?
palmbeach05 said:
Is there a way to track down the full bootloader img for older versions?
Click to expand...
Click to collapse
Not that I know of.
Sent from my SCH-I605 using xda app-developers app
So before I go off with no knowledge and restoring back to stock, I feel afraid. I believe I may have rooted the deodex 4.3 rom (the first one to come out based on the ota for verizon). Note: I did not flash the firmware package in odin. But I did plash a .zop with MJ9 params required for the rom to have working mobile data.
How I got a soft brick was I was nandroid restoring back to when I first unlocked it but my restore failed for some reason. So I restored my nandroid back up of jedi rom (this was in 4.1.2) and it complted however the logo would only stay on the Samsung Galaxy Note 2 logo screen forever. Would never move from there. I am able to access download mode and recovery (TWRP) mode.
I am thinking of restoring back to stock 4.1.2 VRAMC3 baseband version since I unlocked my bootloader on that OTA and since been using custom roms. However, I believe that the 4.3 rom and flashes I've done may interfere and possibly cause worse damage.
I am a bit paranoid right now.
Can someone please lead me in the right direction. Thank you XDA!
AldenIsRad said:
So before I go off with no knowledge and restoring back to stock, I feel afraid. I believe I may have rooted the deodex 4.3 rom (the first one to come out based on the ota for verizon). Note: I did not flash the firmware package in odin. But I did plash a .zop with MJ9 params required for the rom to have working mobile data.
How I got a soft brick was I was nandroid restoring back to when I first unlocked it but my restore failed for some reason. So I restored my nandroid back up of jedi rom (this was in 4.1.2) and it complted however the logo would only stay on the Samsung Galaxy Note 2 logo screen forever. Would never move from there. I am able to access download mode and recovery (TWRP) mode.
I am thinking of restoring back to stock 4.1.2 VRAMC3 baseband version since I unlocked my bootloader on that OTA and since been using custom roms. However, I believe that the 4.3 rom and flashes I've done may interfere and possibly cause worse damage.
I am a bit paranoid right now.
Can someone please lead me in the right direction. Thank you XDA!
Click to expand...
Click to collapse
Don't be paranoid or afraid.. You'll be ok..
Ok did you flash MJ9 Deodex ROM? If so thats when you bootlooped? Just trying to see where you are now... If you have MJ9 deodex on your sdcard reflash it.. Does it boot? Let me know.
Also the MJ9 firmware package with params and tz is for you to have working Wifi not mobile data..Just to clear things up
Report back..Ill be on all morning
lacoursiere18 said:
Don't be paranoid or afraid.. You'll be ok..
Ok did you flash MJ9 Deodex ROM? If so thats when you bootlooped? Just trying to see where you are now... If you have MJ9 deodex on your sdcard reflash it.. Does it boot? Let me know.
Also the MJ9 firmware package with params and tz is for you to have working Wifi not mobile data..Just to clear things up
Report back..Ill be on all morning
Click to expand...
Click to collapse
First off, I'd like to thank you for offering to help me.
Onto the question, when I flashed the mj9 deodex rom, it worked and booted normally. However, I did not flash the Odin firmware package to get wifi working. Yesterday I was trying to nandroid backup to my Jedi x backup and the restore works but I boot loop. I then try to restore my nandroid backup from when I first unlocked and rooted and I get same results.
Basically the only rom that has booted was the mj9 deodex rom. However it is not on my sd cardare to be reflashed. So I'm relying on unrooting / restoring back to stock. But which version do I need to restore back to.
Bump. Still need help with this. I know lacoursiere18 is helping me and has no response possible due to timezones and such and im willing to wait hoping he responds tomorrow but any help is appreciated!
As long as you never took an OTA for 4.3 or higher... and didn't flash anything that is "stock" above build 4.1.2, then you should be able to restore back to stock 4.1.2 VRAMC3 and reroot/ unlock your bootloader. Droidstyle has written a great guide to help with this. You can find the guide here:
http://forum.xda-developers.com/showthread.php?p=34891181
Under section 1b in Droidstyle's guide... you would need to choose the download link for the "Official VRAMC3 4.1.2 5/5/13" stock restore image, along with the 16gb pit file to restore the phone to full stock.... and follow Droidstyle's steps to Odin flash those 2 files back to the device.
After you restore to stock... then you can use Adam Outler's Casual program to reroot and unlock the bootloader on VRAMC3. Adam's guide is 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.. including Windows Defender...
Good luck!
Sent from my SCH-I605 using XDA Premium 4 mobile app
mattnmag said:
As long as you never took an OTA for 4.3 or higher... and didn't flash anything that is "stock" above build 4.1.2, then you should be able to restore back to stock 4.1.2 VRAMC3 and reroot/ unlock your bootloader. Droidstyle has written a great guide to help with this. You can find the guide here:
http://forum.xda-developers.com/showthread.php?p=34891181
Under section 1b in Droidstyle's guide... you would need to choose the download link for the "Official VRAMC3 4.1.2 5/5/13" stock restore image, along with the 16gb pit file to restore the phone to full stock.... and follow Droidstyle's steps to Odin flash those 2 files back to the device.
After you restore to stock... then you can use Adam Outler's Casual program to reroot and unlock the bootloader on VRAMC3. Adam's guide is 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.. including Windows Defender...
Good luck!
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey thanks for the response. I have one mroe precaution,
I flashed the rom (the link to the right) : http://forum.xda-developers.com/showthread.php?t=2561450
I believe it is "based" on stock but not actually stock. I'm not actually sure and hoping you can confirm. Thanks
AldenIsRad said:
Hey thanks for the response. I have one mroe precaution,
I flashed the rom (the link to the right) : http://forum.xda-developers.com/showthread.php?t=2561450
I believe it is "based" on stock but not actually stock. I'm not actually sure and hoping you can confirm. Thanks
Click to expand...
Click to collapse
You are right. The link you reference is not a totally stock version of android 4.3 MJ9... Beanstown106 created that "modified stock 4.3" version for people with unlocked bootloaders. So as long as you never actually installed an unmodified totally stock version of android 4.3 MJ9 ( or any higher full stock build above build version 4.1.2), then you should be able to restore back to full stock VRAMC3/4.1.2 using Droidstyle's guide. If you decide to take the risk to restore back to stock 4.1.2 and reroot with CASUAL...then I hope it works out for you. I know it can be a little scary, but as you know, there is always some risk that we take when we start modifying our phones. For me, the risk has paid off well so far. Good luck.
Sent from my SCH-I605 using XDA Premium 4 mobile
Delete... Accidentally double posted when intended to edit
Hi guys,
I am trying to help someone get their phone back to stock. It's a verizon galaxy note 2 and all the information I have is that they tried to root or rom it and now it doesn't start (and to get it to boot you have to remove/put in the battery)
I'm following droidstyle's guide and I can get as far as starting the odin flash process to stock, but it goes for a few minutes and then I just get a FAIL.
UPDATE1: So I tried again but with the root66 stock VRALJB and it passed but I'm getting the system software not authorized message. I'll keep trying some things..
Anyway I can get this thing up and running again?
UPDATE2: I'm flashing the stock roms semi-successfully, but even after a PASS on the flash, I get the "Verizon has detected unauthorized software" message. Any ideas?
Bascotie said:
Hi guys,
I am trying to help someone get their phone back to stock. It's a verizon galaxy note 2 and all the information I have is that they tried to root or rom it and now it doesn't start (and to get it to boot you have to remove/put in the battery)
I'm following droidstyle's guide and I can get as far as starting the odin flash process to stock, but it goes for a few minutes and then I just get a FAIL.
UPDATE1: So I tried again but with the root66 stock VRALJB and it passed but I'm getting the system software not authorized message. I'll keep trying some things..
Anyway I can get this thing up and running again?
UPDATE2: I'm flashing the stock roms semi-successfully, but even after a PASS on the flash, I get the "Verizon has detected unauthorized software" message. Any ideas?
Click to expand...
Click to collapse
What version of stock firmware was on the phone when the person tried to root it? If it was mj9 4.3 or above you will have to flash the version that was installed through Odin to get it to work. The bootloader starting in mj9 4.3 doesn't allow to downgrade to previous version.
BluGuy said:
What version of stock firmware was on the phone when the person tried to root it? If it was mj9 4.3 or above you will have to flash the version that was installed through Odin to get it to work. The bootloader starting in mj9 4.3 doesn't allow to downgrade to previous version.
Click to expand...
Click to collapse
Good question. He doesn't really know as he was even newer to this than I am (I've done it on a couple phones in the past only a few times, so I do kinda have the hang of it, but this phone's a bit different).
Can I just try flashing 4.3 or above and see if that works? What would be the way to go if I don't know what was flashed previously?