Ok I desperately need some help here. I first got my Note 2 February of last year and quickly rooted it and loaded up Scott's Clean Rom (whichever version was available at the time). I kept going through the updates for Clean Rom and had no issues and was still running Clean Rom until a few weeks ago. Since he was no longer making updates to it I decided just to return to stock since I didn't need root capabilities anymore. I went through the steps in this post, [GUIDE][VZW Edition]How to Root/Rom/Return to Stock the VZW Galaxy Note II! to flash the Official VRAMC3 4.1.2 update to return to stock and had no issues. Everything worked perfectly for several days. Then a friend of mine let me borrow his Note 3 out since I was thinking about buying one. While I had the Note 3, he accepted the latest factory update on my Note 2. Now I'm soft bricked, hopefully not hard bricked.
When I boot up the phone it just sits on the Galaxy Note 2 logo. I can't get into recovery but I can still get into Odin mode. I first tried using Odin to flash the pit file to repartition the phone, and even though I knew it probably wouldn't work I then tried loading the Official VRAMC3 4.1.2 update again. Of course it failed. I've tried multiple times since then to load the Official 4.3 updates, even the newest one that just came out a few days ago. No matter what I have tried I still cannot get the phone to load past the Galaxy Note 2 logo or get into recovery. Also when I go into Odin Mode here is exactly what it reads.
PRODUCT NAME: SCH-1605
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX WARRANTY VOID: 0
AP SWREV: A2
Any help would be greatly appreciated. I can't buy the Note 3 like I want to until I'm able to fix and sell this phone, so I'm currently stuck using my old HTC Thunderbolt that barely runs at this point. Thanks in advance!!
xashaffer said:
Ok I desperately need some help here. I first got my Note 2 February of last year and quickly rooted it and loaded up Scott's Clean Rom (whichever version was available at the time). I kept going through the updates for Clean Rom and had no issues and was still running Clean Rom until a few weeks ago. Since he was no longer making updates to it I decided just to return to stock since I didn't need root capabilities anymore. I went through the steps in this post, [GUIDE][VZW Edition]How to Root/Rom/Return to Stock the VZW Galaxy Note II! to flash the Official VRAMC3 4.1.2 update to return to stock and had no issues. Everything worked perfectly for several days. Then a friend of mine let me borrow his Note 3 out since I was thinking about buying one. While I had the Note 3, he accepted the latest factory update on my Note 2. Now I'm soft bricked, hopefully not hard bricked.
When I boot up the phone it just sits on the Galaxy Note 2 logo. I can't get into recovery but I can still get into Odin mode. I first tried using Odin to flash the pit file to repartition the phone, and even though I knew it probably wouldn't work I then tried loading the Official VRAMC3 4.1.2 update again. Of course it failed. I've tried multiple times since then to load the Official 4.3 updates, even the newest one that just came out a few days ago. No matter what I have tried I still cannot get the phone to load past the Galaxy Note 2 logo or get into recovery. Also when I go into Odin Mode here is exactly what it reads.
PRODUCT NAME: SCH-1605
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX WARRANTY VOID: 0
AP SWREV: A2
Any help would be greatly appreciated. I can't buy the Note 3 like I want to until I'm able to fix and sell this phone, so I'm currently stuck using my old HTC Thunderbolt that barely runs at this point. Thanks in advance!!
Click to expand...
Click to collapse
Did you try to go into Odin and flash this:
VRUEMJ9 4.3- http://www.androidfilehost.com/?fid=23269279319197589(ONLY USE THIS IF YOU TOOK THE 4.3 OTA!! There currently is no bootloader unlock method for 4.3 which means you can no longer flash custom roms, recoveries, or kernels!!!)
with the pit inlcuded.. If not do so.. Then report back.. If you can not get past "Note 2" screen then see, now, if you can get into recovery.. Press UP+HOME+POWER.. and then proceed to do a Factory Reset.
lacoursiere18 said:
Did you try to go into Odin and flash this:
VRUEMJ9 4.3- USE THIS IF YOU TOOK THE 4.3 OTA!! There currently is no bootloader unlock method for 4.3 which means you can no longer flash custom roms, recoveries, or kernels!!!)
with the pit inlcuded.. If not do so.. Then report back.. If you can not get past "Note 2" screen then see, now, if you can get into recovery.. Press UP+HOME+POWER.. and then proceed to do a Factory Reset.
Click to expand...
Click to collapse
That was the first thing that I tried and I still could not get pass the logo or get into Recovery. I will try it again though shortly and let you know what happens.
Just tried it. According to Odin everything Passes, but it still won't go past the logo screen and still won't go into recovery. Any other ideas?
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.
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.
I recently bought a new GS4 SCH-i545
Well i got it friday from Verizon, and had it rooted by Saturday. By Sunday I wanted my iphone back, so i wanted to reclaim warranty. Used Odin3 and the stock firmware for my device, and hit start and it failed. My phone is stuck at the Update with Kies, and I can get it into download mode. Thing is I've tried a a bunch of stock firmwares for my phone model and none of them work (Also I tried ODin 3 185 3.07 and 3.09). I'm at a stand still and any help will be greatly appreciated. Feel free to ask for anymore information that I may have left out.
I rooted with Safe Root,
video I followed is on youtube titled:
Galaxy S4 Build MK2 and MJ7 root instructions
Thanks
Drevangough said:
I recently bought a new GS4 SCH-i545
Well i got it friday from Verizon, and had it rooted by Saturday. By Sunday I wanted my iphone back, so i wanted to reclaim warranty. Used Odin3 and the stock firmware for my device, and hit start and it failed. My phone is stuck at the Update with Kies, and I can get it into download mode. Thing is I've tried a a bunch of stock firmwares for my phone model and none of them work (Also I tried ODin 3 185 3.07 and 3.09). I'm at a stand still and any help will be greatly appreciated. Feel free to ask for anymore information that I may have left out.
I rooted with Safe Root,
video I followed is on youtube titled:
Galaxy S4 Build MK2 and MJ7 root instructions
Thanks
Click to expand...
Click to collapse
You try going into stock recovery and clearing cache and factory data reset?
Verizon Galaxy S4
SafeStrap
Hyperdrive 12
Sprint Galaxy S4
Philz
Carbon 4.4
Hello! I am new to this forum but I am in a little fickle.
I have the Samsung Note 2 TMOBILE and couple weeks ago, I updated to 4.3 through regular OTA. I then rooted and flashed Cyanogenmod 11 and thus, voided my Samsung Knox Warranty bugger thing. I then attempted to go back to stock by flashing stock 4.1.1 through Odin and it worked! I tried to do OTA update again but I realized that the Samsung Knox Void kept me from reaching update services... So I was stuck at 4.1.1 Stock. From there, I was able to flash other custom roms and everything worked.
However, this is a problem for me. The 4.1.2 update from Tmobile was what enabled LTE on my note 2. So right now, I have the old baseband(?) that does not allow LTE. I even attempted to flash a non-knox 4.1.2 (which allowed LTE) through Odin and everything worked until the last second, but it flashed FAIL and I was unable to update my baseband(?).
I was wondering if there is another way to enable LTE by updating to 4.1.2 in any way? Or is this completely unable due to the Samsung Knox?
Thank you in advance.
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?
Ok so hopefully i can get some help with my issue here. I have just resurrected my S4 i thought was dead, but it had the power button sticking problem, and now after about 3 years its going again! This is my problem tho. I got this phone early in the releases. Rooted while on 4.3, unlocked my bootloader on 4.3, ran many ROMS and tons of flashing with no problems. Currently the phone is (ironically) running Ressurrection Remix KK V5.1.0. My Baseband version still states 1545VRUAMDK. I have been trying to get everything up to date but nothing is working right. Im on TWRP version 2.6.0 and yes i have been into recovery since getting it working again. One time when trying to update TWRP i got the Unautorized Software yellow sign sceen. Booted to Download mode and cancelled. I cant get it back into Recovery now and my TWRP wasnt updated. How has my phone became locked again, and how can i fix this? Thanks
If your really still on MDK you can just reunlock your bootloader. Any higher and your stuck on stock, or you could try your luck with flashfire but it only works with touchwiz rims and when I used it on my old s4 it hard bricked it.
You have soft-bricked
Use Odin and flash the no-wipe tar of MDK while in download mode then re-root, etc. You need to use Flashfire to update TWRP. I did the same thing as you recently testing ROM installation with different versions of TWRP. If you update by flashing the img file via TWRP it soft bricks, I found out the hard way.