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.
want relocked BL running newest stock via odin flash without tripping flash counter
Edit; I never did manage to relock the bootloader. However, Verizon still accepted the device since it appeared close enough to stock. I used the alternative restore and triangle away to bring it 95 percent to stock. So I can safely say from my experience that if this is your problem you will probably be fine. It's been a few months and still no new charges on my bill for out of warranty device but YMMV
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 am in a similar situation. I am sending the device back for warranty service since the screen must have burnt out or something. The digitizer catches a touch but there is no light emanating from the screen and since the device was purchased March 28th it is completely under warranty. As it is obvious the root modifications did not cause the screen issue, I do not wish to get a new device via insurance claim and so I am getting another sent.
but my issue is after managing to run triangle away via screencast/adb, how the hell does one relock the device if it's been upgraded to vramc3? from what I have searched, and trust me I have been searching the past two days, which led me here and a few other threads btw, it appears that once the device is on vramc3 it cannot odin back to anything else or it will fail on sboot.bin. And I am not finding any stock odin packages for vramc3, so how the hell does a person take this bad boy back to stock and relock the bootloader for sending to vzw for service? not only that but I can no longer activate recovery since I wouldnt have access to screencast and there is absolutely no way I am sending this device back with even the most minute amount of data in tact so it can be sold to the highest bidder or handed over via an illegal court order for mass search and seizure. anybody have experience with this? i am at the point where i think the only thing I can do is flash the alternate restore for vral but wouldnt that trip my flash counter, and then when they check the device it would probably OTA and softbrick, which I do not want them to have to deal with.
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.
Ok, so yesterday my phone was unable to be rooted and unlocked for some unknown reasons. So, stupidly, I flashed the back to bone stock restore file realizing that it was a custom rom file and soft bricked my device. Luckily, with the help of google, I used root66 in which made my device able to boot up back to normal while rooted.
I then took the 2 OTA updates to get to Android 4.1.2 with the build VRAMC3 and now I know for a factho its completely stock according to odin mode. Im ready to unlock this device and get roms up.
Although, Im still scared at when I soft bricked my device. Im wondering if there is any sort of restore file that is compatible for VRAMC3 or if I can use root66 or a downgradeable pda file if I were to soft brick my device again somehow? If someone can link me to it, that would be appreciated.
Thanks.
http://forum.xda-developers.com/showthread.php?t=2024207.
Read through this has everything u need
Sent from my SCH-I605 using xda premium
Wow, you have now created 3 different threads and posted in 2 different casual threads. Just stick to the most current casual thread and stop the unnecessary multiple threads. Use the current version of casual to unlock your phone. Don't worry, your phone isn't going to blow up from using it
AldenIsRad said:
Ok, so yesterday my phone was unable to be rooted and unlocked for some unknown reasons. So, stupidly, I flashed the back to bone stock restore file realizing that it was a custom rom file and soft bricked my device. Luckily, with the help of google, I used root66 in which made my device able to boot up back to normal while rooted.
I then took the 2 OTA updates to get to Android 4.1.2 with the build VRAMC3 and now I know for a factho its completely stock according to odin mode. Im ready to unlock this device and get roms up.
Although, Im still scared at when I soft bricked my device. Im wondering if there is any sort of restore file that is compatible for VRAMC3 or if I can use root66 or a downgradeable pda file if I were to soft brick my device again somehow? If someone can link me to it, that would be appreciated. Thanks.
Click to expand...
Click to collapse
In this case I would only use the alternate restore to return to stock if you have to. Then you can accept updates or not.
Ridin' a Note 2 blast
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
I just wanted to confirm that you can Odin back to MJ9 4.3 from the newest ND3 4.3 to regain root. This is for 4.3 bootlocked GN2s ONLY. It was quite painless actually, all my data was as it was before. I backed up to the internal memory using Helium just in case (since I lost root), but I was able use saferoot without issue and am now back to rooted.
I had used Kingo before to root, so I am actually glad to use saferoot this time since I am planning to install SafeStrap and flash N3BULA over stock soon.
gee1000 said:
I just wanted to confirm that you can Odin back to MJ9 4.3 from the newest ND3 4.3 to regain root. This is for 4.3 bootlocked GN2s ONLY. It was quite painless actually, all my data was as it was before. I backed up to the internal memory using Helium just in case (since I lost root), but I was able use saferoot without issue and am now back to rooted.
I had used Kingo before to root, so I am actually glad to use saferoot this time since I am planning to install SafeStrap and flash N3BULA over stock soon.
Click to expand...
Click to collapse
Confirmed. Just ODIN'd back to MJ3 from the VRUAND3 update and regained root using Saferoot.
seriously whaaat can u post the needed files and step by step directions ive never used odin before
Sent from my SCH-I605 using XDA Free mobile app
mrraya said:
seriously whaaat can u post the needed files and step by step directions ive never used odin before
Sent from my SCH-I605 using XDA Free mobile app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2024207&nocache=1
Be sure to thank @droidstyle for taking the time to make this guide
Another confirmation, Odin'd back to MJ9 from ND3 then used saferoot to root.
Can also confirm working for me and rooted also. Does anyone know how we can stop the OTA notification or do we just ignore it?
stop the ota notification note 2
Ostate24 said:
Can also confirm working for me and rooted also. Does anyone know how we can stop the OTA notification or do we just ignore it?
Click to expand...
Click to collapse
Change
FWupgrade.apk to FWupgrade.bak
SDM.apk to SDM.bak
I am not allow to post a link at this time so do a search on "stop the ota notification note 2"
Regain root, ND3 question,Correct MJ9, ODIN7
gee1000 said:
I just wanted to confirm that you can Odin back to MJ9 4.3 from the newest ND3 4.3 to regain root. This is for 4.3 bootlocked GN2s ONLY. It was quite painless actually, all my data was as it was before. I backed up to the internal memory using Helium just in case (since I lost root), but I was able use saferoot without issue and am now back to rooted.
I had used Kingo before to root, so I am actually glad to use saferoot this time since I am planning to install SafeStrap and flash N3BULA over stock soon.
Click to expand...
Click to collapse
This is what I have been looking for except it says to "REGAIN" root.. I have never had it (ROOT) to start with.. So will this still work?
and
where do I get the correct MJ9 since I did not get it off my phone before I lost it.?? or am I ODIN back to out of the box state which is VRALJB?
Odin 7 or Odin 9
I have read ODIN7 ? but Odin9 is newest as far as I can tell...want to double check.
thanks so much!!!!
mrraya said:
seriously whaaat can u post the needed files and step by step directions ive never used odin before
Click to expand...
Click to collapse
thebat1 said:
This is what I have been looking for except it says to "REGAIN" root.. I have never had it (ROOT) to start with.. So will this still work?
and
where do I get the correct MJ9 since I did not get it off my phone before I lost it.?? or am I ODIN back to out of the box state which is VRALJB?
Odin 7 or Odin 9
I have read ODIN7 ? but Odin9 is newest as far as I can tell...want to double check.
thanks so much!!!!
Click to expand...
Click to collapse
thebat1, since I am assuming you are on bootlocked ND3 from your screenshot, you will mess up/brick your phone trying to flash VRALJB. You can only go back to MJ9 at this point. The thread I used which is the same posted by iooooooc -- http://forum.xda-developers.com/show...4207&nocache=1 says "4.1.1 VRALJB- http://forum.xda-developers.com/show....php?t=2043636 (Unless you purchased your device within the first month of release and never took the OTA update, DO NOT use this)".
I am pretty sure it doesn't matter if you rooted under MJ9 or not. I was able to Odin without root and I wouldn't see why not being rooted when on MJ9 would not enable you to use Odin (since the whole point of Odin is to flash Samsung phones). I'd make a Helium backup just in case though.
You can read the thread I linked and posted by iooooooc to find out how to reflash. It's the same one I used. It has links to Odin and the MJ9 firmware (look for "VRUEMJ9 4.3" with the warning "ONLY USE THIS IF YOU TOOK THE 4.3 OTA!!") and the PIT file you'll need.
You can also read about and get links to all flavors of Odin (you need v3.07 for the VZ Note II) here: http://forum.xda-developers.com/gal...08-2013-odin-3-09-odin-1-85-versions-t2189539
Finally, to root, here's the main thread for Saferoot: http://forum.xda-developers.com/showthread.php?t=2565758
Everything I read is pretty straightforward.
I also haven't received any notification to upgrade back even though I haven't used the .bak renaming method which is interesting.
Worked great!!!! Thanks for the links guys!!!
Worked Here Too!
gee1000 said:
I just wanted to confirm that you can Odin back to MJ9 4.3 from the newest ND3 4.3 to regain root. This is for 4.3 bootlocked GN2s ONLY. It was quite painless actually, all my data was as it was before. I backed up to the internal memory using Helium just in case (since I lost root), but I was able use saferoot without issue and am now back to rooted.
I had used Kingo before to root, so I am actually glad to use saferoot this time since I am planning to install SafeStrap and flash N3BULA over stock soon.
Click to expand...
Click to collapse
I decided to bite-the-bullet after reading your post, and all I had to do was re-root as well. All said and done it took me 30 minutes tops to have my phone back. I also used Kingo last time, but after ND3, the version of Kingo I used to root MJ9 didn't recognize the phone and the latest version was so full of dire warnings I immediately aborted.
Thanks guys!
dbalman said:
I decided to bite-the-bullet after reading your post, and all I had to do was re-root as well. All said and done it took me 30 minutes tops to have my phone back. I also used Kingo last time, but after ND3, the version of Kingo I used to root MJ9 didn't recognize the phone and the latest version was so full of dire warnings I immediately aborted.
Thanks guys!
Click to expand...
Click to collapse
I just received a replacement for my broken Note 2, which I previously had rooted with N3bula. To root my old phone, given it came with 4.1, I just had to Odin the MJ9 files, and then flash N3bula with TWRP . When I got my replacement, it updated to ND3 before I realized what was going on. Does anyone know what files I actually need to flash to get back to MJ9 from ND3? I found a file called I605VRUEMJ9.tar on one of the links posted recently. Since the actual ROM on the phone is the stock 4.3 rom, I assume I don't need to worry about system.img. I don't know about boot.img, cache.img, recovery.img, sboot.bin. I am confident I should flash tz.img, modem.bin, hidden.img.
Thanks!
---------- Post added at 05:51 PM ---------- Previous post was at 05:21 PM ----------
gee1000 said:
I just wanted to confirm that you can Odin back to MJ9 4.3 from the newest ND3 4.3 to regain root. This is for 4.3 bootlocked GN2s ONLY. It was quite painless actually, all my data was as it was before. I backed up to the internal memory using Helium just in case (since I lost root), but I was able use saferoot without issue and am now back to rooted.
I had used Kingo before to root, so I am actually glad to use saferoot this time since I am planning to install SafeStrap and flash N3BULA over stock soon.
Click to expand...
Click to collapse
Is there a particular reason you wish to use safestrap rather than continuing to use Kingo? Is Kingo not working?
Thx!!
nbock01 said:
Worked great!!!! Thanks for the links guys!!!
Click to expand...
Click to collapse
thebat1, since I am assuming you are on bootlocked ND3 from your screenshot, you will mess up/brick your phone trying to flash VRALJB. You can only go back to MJ9 at this point. The thread I used which is the same posted by iooooooc -- http://forum.xda-developers.com/show...4207&nocache=1 says "4.1.1 VRALJB- http://forum.xda-developers.com/show....php?t=2043636 (Unless you purchased your device within the first month of release and never took the OTA update, DO NOT use this)".
Neither of those links are good.
Thanks!!
@Skilover
If you go to Droidstyle's guide here: http://forum.xda-developers.com/showthread.php?p=34891181 , and then go to section 1b of the guide, you can revert back to MJ9 by following the guide's instructions. You'll want to use the stock file for (VRUEMJ9 4.3) if you're wanting to revert back from ND3.
After you get back to MJ9, you can get root access with saferoot..... Here's the link to saferoot-- http://forum.xda-developers.com/show...php?p=48392009
Sent from my SCH-I605 using XDA Premium 4 mobile app
Amazing..WTG, XDA!
New user here. Been reading a bunch of posts lately as I finally got around to trying to root my SCH-1605, which I have through VZW. For a long time, my big concern was interference on the VZW side. Finally, warranties expired and the urge peaked... just in time for the ND3 OTA update. I tried a couple of methods I found - no success. Finally stumbled on some threads that basically said - ND3 = Out of Luck.
Then I found this post.. :victory:
Truly awesome. Worked like a charm. Looking up good info on locking down the OTA pushes next.
My observations of the differences between my previous attempts and what was missing:
My first attempts:
I neglected to include the 16GB PIT file referenced in the links above (** Note: a few guides I popped across mentioned making sure that only "Auto Reboot" and "F. Reset Time" are checked. When you include the PIT file, it will auto-check "Re-Partition". I left this checked, and it worked like a charm. Can't speak as to the offset of UNchecking this, as - like I said - I left it checked)
I used a different .md5 file that would flag as a fail despite my efforts (I was using a CF autoroot md5). I'm fairly certain this failed due to the OTA update, though it may have been the lack of a PIT file. If someone could provide some more info there, I'm totally open to listen!
Bottom line - my experience was pretty painless after doing adequate research. Thanks a ton! :highfive:
_______________________________________________________________________________________________________________________
I also came across some info stating that the downgrade to the MJ firmware might flag the KNOX (I believe?) or a similar issue. Anyone run across any of those issues using these methods? If someone has a quick link to how I could check this for myself, I'd be very appreciative.
@Tangescence
Glad to hear you had success with rooting . This link should help you check on your knox counter status:
http://forum.xda-developers.com/showthread.php?p=48758233&highlight=odin#post48758233
If "Knox Warranty Void" is at zero, you didn't trip the counter.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Knox warranty void: 0
Confirmed. The flashback left KNOX WARRANTY VOID: 0
Lists as Samsung Official Binary with a System Status of Custom.
Looks good!
I know this is a bit of a side tangent, but safestrap should work with MJ9 and saferoot to allow custom ROMs despite the locked bootloader - right?
Again, many thanks to the community!
Right, safestrap was designed to be used for people with the locked bootloader on a rooted MJ9. Here is the safestrap thread: http://forum.xda-developers.com/showthread.php?p=51616723
I don't know a lot about safestrap, but I believe the ROM slots are not working yet so you'll have to install a custom Rom over the stock ROM if you want to use it. You'll have to do more research to make sure you know how to use it if you want to give it a go.
Sent from my SCH-I605 using XDA Premium 4 mobile app
mattnmag said:
Right, safestrap was designed to be used for people with the locked bootloader on a rooted MJ9. Here is the safestrap thread: http://forum.xda-developers.com/showthread.php?p=51616723
I don't know a lot about safestrap, but I believe the ROM slots are not working yet so you'll have to install a custom Rom over the stock ROM if you want to use it. You'll have to do more research to make sure you know how to use it if you want to give it a go.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Awesome - I'll be researching it tonight and tomorrow. Will post to the safestrap thread with my results and probably a heads up here to redirect. Again, tons of thanks!
Confirmed working
My Verizon Note 2 broke so under warranty I got a replacement device with the latest VRUAND3 build installed. It literally drove me nuts because I was so used to having the advantage of a rooted device with the bootloader unlocked. After doing some research, I came across the information on this thread and it helped me with having at least root access which allows me to take advantage of my Titanium Backup and other apps tailored to rooted devices.
Thank you very much for this post. I hope the devs will one up on Verizon and give the community the ability to have a unlocked bootloader soon. I like the connection speed and coverage with Verizon but their method of controlling how their customers use their devices is just annoying. I paid good money for this phone Verizon! I'm going to do what I wish to do with it to make it unique and personal to me. They just don't seem to understand that. Once again... Thanks. ROOT 4TW!
gee1000 said:
thebat1, since I am assuming you are on bootlocked ND3 from your screenshot, you will mess up/brick your phone trying to flash VRALJB. You can only go back to MJ9 at this point. The thread I used which is the same posted by iooooooc -- http://forum.xda-developers.com/show...4207&nocache=1 says "4.1.1 VRALJB- http://forum.xda-developers.com/show....php?t=2043636 (Unless you purchased your device within the first month of release and never took the OTA update, DO NOT use this)".
I am pretty sure it doesn't matter if you rooted under MJ9 or not. I was able to Odin without root and I wouldn't see why not being rooted when on MJ9 would not enable you to use Odin (since the whole point of Odin is to flash Samsung phones). I'd make a Helium backup just in case though.
You can read the thread I linked and posted by iooooooc to find out how to reflash. It's the same one I used. It has links to Odin and the MJ9 firmware (look for "VRUEMJ9 4.3" with the warning "ONLY USE THIS IF YOU TOOK THE 4.3 OTA!!") and the PIT file you'll need.
You can also read about and get links to all flavors of Odin (you need v3.07 for the VZ Note II) here: http://forum.xda-developers.com/gal...08-2013-odin-3-09-odin-1-85-versions-t2189539
Finally, to root, here's the main thread for Saferoot: http://forum.xda-developers.com/showthread.php?t=2565758
Everything I read is pretty straightforward.
I also haven't received any notification to upgrade back even though I haven't used the .bak renaming method which is interesting.
Click to expand...
Click to collapse