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.
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 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
hi,
just got my GS4 today and, very stupidly, agreed to let the phone update to the new firmware via verizon's OTA update to VRUDMI1. realizing i had already made a mistake, i used ODIN to try and flash it back to the stock firmware, which failed. i tried a couple packages for the stock VZ image, but both have failed. also, apparently the VZ GS4 does not give you a serial number, so Samsung's KIES is not an option, unless i am mistaken. i tried downloading that and using my IMEI as the serial but it says the serial is incorrect.
am i completely screwed? or maybe just for the time being until a new image for flashing back to stock from the new firmware is released? the phone boots into ODIN but gives the message that there was an error while updating the firmware, and to try the software repair assistant. based on what i've been reading, it seems that this is sometimes fixable, but perhaps it is just too early for this firmware at this point? ugh.
long shot: the phone was not rooted at the time, locked bootloader, running the fully stock VZ image and new firmware -- perhaps they would provide assistance? i wouldn't hold my breath though!
androidy_guy said:
hi,
just got my GS4 today and, very stupidly, agreed to let the phone update to the new firmware via verizon's OTA update to VRUDMI1. realizing i had already made a mistake, i used ODIN to try and flash it back to the stock firmware, which failed. i tried a couple packages for the stock VZ image, but both have failed. also, apparently the VZ GS4 does not give you a serial number, so Samsung's KIES is not an option, unless i am mistaken. i tried downloading that and using my IMEI as the serial but it says the serial is incorrect.
am i completely screwed? or maybe just for the time being until a new image for flashing back to stock from the new firmware is released? the phone boots into ODIN but gives the message that there was an error while updating the firmware, and to try the software repair assistant. based on what i've been reading, it seems that this is sometimes fixable, but perhaps it is just too early for this firmware at this point? ugh.
long shot: the phone was not rooted at the time, locked bootloader, running the fully stock VZ image and new firmware -- perhaps they would provide assistance? i wouldn't hold my breath though!
Click to expand...
Click to collapse
Yeah once you go to ME7 or MI1, there is no going back. You can only stay where you are, or go forward. You'll need to use Odin again and this time flash the MI1 file.
Which can be found here thanks to Surge1223
http://forum.xda-developers.com/showthread.php?t=2484726
spc_hicks09 said:
Yeah once you go to ME7 or MI1, there is no going back. You can only stay where you are, or go forward. You'll need to use Odin again and this time flash the MI1 file.
Which can be found here thanks to Surge1223
http://forum.xda-developers.com/showthread.php?t=2484726
Click to expand...
Click to collapse
Chances are it will also flip the knox warranty to void because knox status/warranty is now included in the new firmware.
tech_head said:
Chances are it will also flip the knox warranty to void because knox status/warranty is now included in the new firmware.
Click to expand...
Click to collapse
hmm, interesting. perhaps i should try my luck with VZ first? i guess it can't do any harm. currently when it turns on it shows knox status 0x0, which is apparently good. perhaps VZ can flash it somehow? i have no idea what kind of support they provide for this kind of thing.
edit: also it seems this KNOX is mainly relevant for creating a secure zone for corporate applications? i am not using it in that setting. perhaps it would just reduce the resale value somewhat? or is there something i'm not understanding about it.
That flag if set will have Samsung trying to deny any warranty.
They are not going to flash it for you.
Not advocating fraud or anything., but you have only had it one day.......
Sent from my SCH-I545 using Tapatalk
tech_head said:
That flag if set will have Samsung trying to deny any warranty.
They are not going to flash it for you.
Not advocating fraud or anything., but you have only had it one day.......
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
yea, i figured as much. it does say "system status: custom" though - maybe that alone will screw me? not sure how VZ will see that. if they refuse is it worth contacting samsung directly?
also, bought the phone used from a friend, so that prob eliminates any hope from VZ to begin with.
Flash the Odin posted in post 2. Then you can root and use safestrap the same as it being on me7 like it was.
androidy_guy said:
yea, i figured as much. it does say "system status: custom" though - maybe that alone will screw me? not sure how VZ will see that. if they refuse is it worth contacting samsung directly?
also, bought the phone used from a friend, so that prob eliminates any hope from VZ to begin with.
Click to expand...
Click to collapse
Okay, bought from friend not Verizon.
So back to ODIN it is.
You just need the latest firmware to flash. You can't use ME7 but you can use the latest one.
The file is in this thread -> http://forum.xda-developers.com/showthread.php?t=2484726 like one of the previous people posted.
You already know how to use ODIN and this should work. Just remember PDA mode.
Once you flash Me7 there was no going back and MI1 is the same. No going backward.
You should be fine if you can get into download.
^^^^^^^^^ what he said
tech_head said:
Okay, bought from friend not Verizon.
So back to ODIN it is.
You just need the latest firmware to flash. You can't use ME7 but you can use the latest one.
The file is in this thread -> http://forum.xda-developers.com/showthread.php?t=2484726 like one of the previous people posted.
You already know how to use ODIN and this should work. Just remember PDA mode.
Once you flash Me7 there was no going back and MI1 is the same. No going backward.
You should be fine if you can get into download.
Click to expand...
Click to collapse
will do - downloading the package now. should be able to fool around with it after work today. i feel like a real idiot for rushing into this without knowing enough about the OTA firmware that i ignorantly accepted.
at this point i don't really care if the KNOX is triggered or whatever - i always purchase my devices out of warranty and activate them so i can keep my grandfathered unlimited. it's the risk i run for wanting stock android on verizon with unlimited data
ooooook, the package in that thread worked. thanks a lot guys! i was really kicking myself all day over this one, and really had only myself to blame. my only questions now are:
how can i check my KNOX status?
is it likely that there will be a root/CM version for this phone, post UMI1?
Reboot into download and read the tiny text with a magnifying glass
Sent from my SCH-I545 using Tapatalk
Im glad the odin image worked...pulling that thing was kinda difficult lol.
ok i booted into ODIN again and KNOX comes up 0x0, so it looks like i came out unscathed all around. too bad i inadvertently locked my phone down with this update. i got the GS4 so i could upgrade from my GN, in hopes of flashing the latest CM10 on a phone with some nicer hardware.
So, I dropped and cracked another screen, 4 but whose counting. I called Assurion and they said they'll send me a new i605 without updating it to OTA 4.3
Now my main question is how do I go about unlocking the bootloader, and rooting it from stock. It's been so long since I was on a bone stock rom. I know the last time I did it there was some "suck it verizon" file and a .pit file. Do I follow these direstions: http://forum.xda-developers.com/showthread.php?t=2043636
Also, When I get it unlocked and Philz recovery on the phone can I restore a backup of Sophisticated rom, or do I have to reinstall from scratch?
crbnfbr said:
So, I dropped and cracked another screen, 4 but whose counting. I called Assurion and they said they'll send me a new i605 without updating it to OTA 4.3
Now my main question is how do I go about unlocking the bootloader, and rooting it from stock. It's been so long since I was on a bone stock rom. I know the last time I did it there was some "suck it verizon" file and a .pit file. Do I follow these direstions: http://forum.xda-developers.com/showthread.php?t=2043636
Also, When I get it unlocked and Philz recovery on the phone can I restore a backup of Sophisticated rom, or do I have to reinstall from scratch?
Click to expand...
Click to collapse
If its 4.1.2 go here to root, unlock bootloader and install custom recovery in 1 click.
Since u already have a backup, I think after you have custom recovery, you just can restore your backup.(cmiiw)
Bonkurei said:
If its 4.1.2 go here to root, unlock bootloader and install custom recovery in 1 click.
Since u already have a backup, I think after you have custom recovery, you just can restore your backup.(cmiiw)
Click to expand...
Click to collapse
Thanks, that will be a lot easier than the original method I had to do over a year ago. I just really hope they send me a non upgraded phone. The guy said he would put a note in my claim not to do the 4.3 OTA upgrade, fingers crossed.
Bonkurei said:
If its 4.1.2 go here to root, unlock bootloader and install custom recovery in 1 click.
Since u already have a backup, I think after you have custom recovery, you just can restore your backup.(cmiiw)
Click to expand...
Click to collapse
Thanks, that will be a lot easier than the original method I had to do over a year ago. I just really hope they send me a non upgraded phone. The guy said he would put a note in my claim not to do the 4.3 OTA upgrade, fingers crossed.
Turns out to be a moot point. New phonrle came with 4.3. Even though the Assurion guy I talked to yesterday said it wouldn't. Now they say they "have" to update to the newest firmware, or it won't work with the network. What a bunch of BS.
So, I'm sort of confused right now. I'm getting "internet unstable messages" on 4.3, and I only got those was from Beans 4.3 leak.
Could it be that my phone was flashed with a leaked 4.3 then sent in to the insurance company, and never updated because it'd already be running 4.3?
Always getting either "Not authorized by Verizon" or "Upgrade encountered an issue"
Hey guys, hoping someone can help me out with what appears to be a soft brick on my phone.
Background
Bought phone in January 2013, immediately rooted and installed custom recovery. Phone stayed this way until yesterday, when I restored with ODIN and then installed all OTA's to prepare for a replacement under a Best Buy service plan, expecting it to work like it used to where I go into the store and drop off the phone, then a new one is sent to the store. I then installed all OTA's up to 4.4.2 (I think that one is ND7 but not sure as I was using AOSP-based ROMS while rooted). The ODIN restore brought me back to saying the firmware was all official.
Currently
Replacement process changed and I am stuck with this phone for another week while a replacement gets mailed to my home, so I decided to play around with ODIN to restore to MJ9 since most root methods seemed to work for MJ9, but I accidentally chose the LJB image that I had downloaded yesterday for the PDA in ODIN. When running this, it failed on sboot.bin.
I restarted the phone and it said "Firmware Upgrade encountered an issue" and tells me to connect it to Kies, which I tried, but for some reason Kies just runs on Connecting to Device and won't do anything else. I didn't spend a whole lot of time on that though, as it also changed the "System Status" to Custom while leaving Current Binary as Official, and from what I read Kies will refuse to do a recovery if anything is Custom.
I tried to install MJ9 through ODIN and it also fails at sboot.bin, resulting in the same message as above. I downloaded the alternate MC3 from this thread and it ran through ODIN fine since it does not have an sboot.bin, but it gives the error about the firmware not being authorized by Verizon and changes both Current Binary and System Status to Custom (I think MJ9 was the first locked bootloader, so I would assume that is why, but I don't know for sure). There was no alternate for MJ9 so I tried to make my own by extracting, removing sboot.bin, and then putting the rest of the files in a new tar file, but ODIN won't run it and gives an error about the MD5 not matching.
At this point the phone working is not so much of an issue since I already have a replacement on the way to my house, but I would prefer to fix this so a) I have a phone for the next few days, and b) so I don't have to go short something inside on purpose to hard-brick it and prevent them from refusing my replacement claim.
Any help would be greatly appreciated.
Thanks,
Michael
Once you updated the phone to factory stock 4.4.2, you permanently locked the bootloader and you can't downgrade to any other pre 4.4.2 ND7 firmwares. The easiest thing to do now would be to use Odin to restore the device back to to factory 4.4.2 stock firmware. There is GhettoRoot for 4.4.2 if you're wanting to root the device again on 4.4.2... and people are reporting that safestrap works as well for flashing 4.4.2 touchwiz roms. Good luck!
Ahh, I wasn't aware that ND7 couldn't be downgraded at all; I thought anything past MJ9 would work since that was when the bootloader became locked. I don't see any ND7 ODIN images available anywhere and Kies won't allow me to restore the device. Is there another method I should be using to restore? My wife has an i605 on 4.1.1 right now (same background as mine, just not bricked and no OTAs downloaded); if we updated until ND7 was downloaded but not installed, would I be able to pull the OTA from hers and flash in ODIN, or are they not ODIN-compatible?
opalelement said:
Ahh, I wasn't aware that ND7 couldn't be downgraded at all; I thought anything past MJ9 would work since that was when the bootloader became locked. I don't see any ND7 ODIN images available anywhere and Kies won't allow me to restore the device. Is there another method I should be using to restore? My wife has an i605 on 4.1.1 right now (same background as mine, just not bricked and no OTAs downloaded); if we updated until ND7 was downloaded but not installed, would I be able to pull the OTA from hers and flash in ODIN, or are they not ODIN-compatible?
Click to expand...
Click to collapse
Here's a link to the Verizon stock 4.4.2 firmware from Sammobile. You'll have to register, but the download should be free. You should be able to use Odin to restore the device with this firmware file and the pit file from Droidstyle's restore guide. If Odin 3.07 doesn't work, try Odin 3.09 from Sammobile... or try Odin 3.10, which I've been using lately with no problems.
Thanks for that link, I was able to download and restore my phone with the ND7 download. I wasn't aware that SamMobile keeps a firmware database, so I also appreciate that piece of info.
Thanks,
Michael