Hey,
Sorry total noob at messing with my phone, buuuuuut I tried to (foolishly) downgrade my Verizon sch-i545 from OC1 because I hate it. I tried to flash back to MDK using ODIN 3.4, 3.7, AND 3.9 all of which failed. From what I can find it seems like flashing to anything from a Verizon sch-i545 running OC1 is destined to fail due to something contained in the update. Is this correct? Since the failed flash, I can't get my phone to turn back on normally, it just gives me the "Software Update Failed, use verizon software repair assistant..." which from what I can find is downloaded from the phone when you plug it in? But it didn't seem to do so for mine when I initially plugged it in to back up files. I can't find an online source to download the verizon software from. So basically I'm asking for help on just getting my phone functioning again? It doesn't seem like I've bricked it, but I don't know what to do after a failed flash? Can I download the 5.0.1 firmware and flash it using odin and it will actually work because it's 5.0.1? I'm tired of waiting 2 hrs to download a firmware to have it immediately fail haha. Or is there another much simpler way to get it out of this mode and back to just running normal ****ty lollipop? I can get the phone back into download mode, but that's it. Thanks for any help. Sorry if anything is silly or redundant, tried searching for hours without finding much.
Thanks.
Try This
BreakThroughCity said:
Hey,
Sorry total noob at messing with my phone, buuuuuut I tried to (foolishly) downgrade my Verizon sch-i545 from OC1 because I hate it. I tried to flash back to MDK using ODIN 3.4, 3.7, AND 3.9 all of which failed. From what I can find it seems like flashing to anything from a Verizon sch-i545 running OC1 is destined to fail due to something contained in the update. Is this correct? Since the failed flash, I can't get my phone to turn back on normally, it just gives me the "Software Update Failed, use verizon software repair assistant..." which from what I can find is downloaded from the phone when you plug it in? But it didn't seem to do so for mine when I initially plugged it in to back up files. I can't find an online source to download the verizon software from. So basically I'm asking for help on just getting my phone functioning again? It doesn't seem like I've bricked it, but I don't know what to do after a failed flash? Can I download the 5.0.1 firmware and flash it using odin and it will actually work because it's 5.0.1? I'm tired of waiting 2 hrs to download a firmware to have it immediately fail haha. Or is there another much simpler way to get it out of this mode and back to just running normal ****ty lollipop? I can get the phone back into download mode, but that's it. Thanks for any help. Sorry if anything is silly or redundant, tried searching for hours without finding much.
Thanks.
Click to expand...
Click to collapse
Ok I have already gone down this road myself.
First can you get your phone into download mode ? If so re-flash the original firmware. This file is on the XDA site somewhere ,I remember seeing it. I loaded mine at a very slow download took hours , did it over night . I have had to redo my phone several times trying with Odin after countless lockups.
The OC1 can not be changed it has a locked boot-loader that can not be unlocked @ this time. So no downgrade changes of ant kind. You CAN NOT GO BACK I highly suggest you read more on this site to help you better.
There is only a handful of ROMs you can install & they have to be OC1 compatable
traco1 said:
Ok I have already gone down this road myself.
First can you get your phone into download mode ? If so re-flash the original firmware. This file is on the XDA site somewhere ,I remember seeing it. I loaded mine at a very slow download took hours , did it over night . I have had to redo my phone several times trying with Odin after countless lockups.
The OC1 can not be changed it has a locked boot-loader that can not be unlocked @ this time. So no downgrade changes of ant kind. You CAN NOT GO BACK I highly suggest you read more on this site to help you better.
There is only a handful of ROMs you can install & they have to be OC1 compatable
Click to expand...
Click to collapse
Thanks! That worked like a charm. If anyone else sees this and is in a similar situation, flashing the OC1 back definitely work the first time. I had to try and try again, different USB ports, pull the battery out, wait, and try again. Eventually with persistence it worked.
Related
Hi,
I recently J Tagged my galaxy S4 Verizon and it came back to me with these specs:
ME7 stock Rooted Rom
Android 4.2.2
Base band
I545VRUAME7
Safe Strap 3.64 TWPR v 2.6.3.1
Hyperdrive ROM ver 10
I tried to use ODIN to re-flash to stock ROM VRUAMDK_Nowipe_tar_md5. So that I may be able to update to the new Hyperdriver ROM and it didn't turn out as planned.
HERE IS WHAT I DID:
I just turned off the phone.
Installed Samsung drivers on PC
Down loaded the TAR file loaded it in to ODIN and hit PDA and let it do its thing.
I've tried this several times and every times it ends in a FAIL.
I can put the phone into download mode but that it nothing past that.
Some times I get the message to connect it to KIES as it need missing files. I did that too and KIES takes forever to search for the S4 and cannot find it.
The drivers are installed the PC recognizes the phone. But KIES does not.
The guy who J tagged it said that he froze the system apk SDM 1.0 to stop OTA.
Does any one know how to help me get out of this predicament? I would really appreciate the help and guidance.
Thanks in advance!
radiskull1973 said:
Hi,
I recently J Tagged my galaxy S4 Verizon and it came back to me with these specs:
ME7 stock Rooted Rom
Android 4.2.2
Base band
I545VRUAME7
Safe Strap 3.64 TWPR v 2.6.3.1
Hyperdrive ROM ver 10
I tried to use ODIN to re-flash to stock ROM VRUAMDK_Nowipe_tar_md5. So that I may be able to update to the new Hyperdriver ROM and it didn't turn out as planned.
HERE IS WHAT I DID:
I just turned off the phone.
Installed Samsung drivers on PC
Down loaded the TAR file loaded it in to ODIN and hit PDA and let it do its thing.
I've tried this several times and every times it ends in a FAIL.
I can put the phone into download mode but that it nothing past that.
Some times I get the message to connect it to KIES as it need missing files. I did that too and KIES takes forever to search for the S4 and cannot find it.
The drivers are installed the PC recognizes the phone. But KIES does not.
The guy who J tagged it said that he froze the system apk SDM 1.0 to stop OTA.
Does any one know how to help me get out of this predicament? I would really appreciate the help and guidance.
Thanks in advance!
Click to expand...
Click to collapse
You can't revert to older firmware. It's been posted over and over. If you were on ME7 then you have to get a ME7 Tar file and use Odin to flash that. After that, if you want Hyperdrive RLS 12, you would have to update to MJ7 (or MK2), then install Safestrap 3.70.
You have a lot of reading to do. I suggest you take your time and do your research.
Sent from my NCC 1701 Using Tapatalk 4
ME7 TAR
riker147 said:
You can't revert to older firmware. It's been posted over and over. If you were on ME7 then you have to get a ME7 Tar file and use Odin to flash that. After that, if you want Hyperdrive RLS 12, you would have to update to MJ7 (or MK2), then install Safestrap 3.70.
You have a lot of reading to do. I suggest you take your time and do your research.
Sent from my NCC 1701 Using Tapatalk 4
Click to expand...
Click to collapse
Hey thanks for the reply, you're right I should have done some more reading. I managed to start the phone but it's running real sluggish. I've done several searches for a ME7 TAR file to use with ODIN but I can't fine any thing. You happen to know of a link that could help me out. Appreciate it.
Sorry for the bother!
radiskull1973 said:
Hey thanks for the reply, you're right I should have done some more reading. I managed to start the phone but it's running real sluggish. I've done several searches for a ME7 TAR file to use with ODIN but I can't fine any thing. You happen to know of a link that could help me out. Appreciate it.
Sorry for the bother!
Click to expand...
Click to collapse
Quick search found this http://forum.xda-developers.com/showthread.php?t=2301259. Take your time and read everything before you jump in. Good luck.
Should I OTA now??
riker147 said:
Quick search found this http://forum.xda-developers.com/showthread.php?t=2301259. Take your time and read everything before you jump in. Good luck.
Click to expand...
Click to collapse
Thanks so much for the help and the links they really saved the day. I managed to follow instruction closely and installed stock ME7 through ODIN and rooted the phone.
Should I go ahead and do a OTA update or will lock me down and keep me from installing custom ROM?
radiskull1973 said:
Thanks so much for the help and the links they really saved the day. I managed to follow instruction closely and installed stock ME7 through ODIN and rooted the phone.
Should I go ahead and do a OTA update or will lock me down and keep me from installing custom ROM?
Click to expand...
Click to collapse
You can currently root any of the I545 versions, so updating is not prohibited. You'll need to decide if it's worthwhile.
None of the versions later than MDK will allow you to install a custom recovery. Also, Custom ROMs are limited and installed using Safestrap, only Touchwiz compatible. No AOSP or CM.
What exactly does j-tag do on an S4?
J Tag
Schoat333 said:
What exactly does j-tag do on an S4?
Click to expand...
Click to collapse
I just going to repeat things like a parrot because I'm new to all of this. I flashed the wrong ROM, meaning ROM meant for another model other than my phone which is a SCH-I545. That ruins the EMMC chip that has all the booting up information. At this point the phone is HARD BRICKED. In J TAG they use a certain device after disassembling the phone and re install necessary software to bring it back to life and save the phone, so you don't have to throw it away. Man folks of Ebay offer this service for around $30 not a bad deal. Made my phone run pretty good as new.
I connect my Galaxy Mega (i9205) to kies and it showed that my phone have new update. Bear in mind that my phone is rooted previously (CWM). Kies updated my phone to I9205XXUCNA3. I update my phone with no problem (it took longer time only) but unfortunately KNOX ruined everything. It keeps on saying that SuperUser is trying to access the system. Furthermore, my Wifi is not working at all. I tried to click on the toggle button but no to avail.
So after searching, I found out how to disable KNOX - By flashing using vcoreroot-v2. Done flashing with this file, and now I can't see my interna; SDCard. I'm doomed and now I don't know what to do to turn back to how it was before.
Anybody that can help me, really appreciate it.
nuar_y said:
I connect my Galaxy Mega (i9205) to kies and it showed that my phone have new update. Bear in mind that my phone is rooted previously (CWM). Kies updated my phone to I9205XXUCNA3. I update my phone with no problem (it took longer time only) but unfortunately KNOX ruined everything. It keeps on saying that SuperUser is trying to access the system. Furthermore, my Wifi is not working at all. I tried to click on the toggle button but no to avail.
So after searching, I found out how to disable KNOX - By flashing using vcoreroot-v2. Done flashing with this file, and now I can't see my interna; SDCard. I'm doomed and now I don't know what to do to turn back to how it was before.
Anybody that can help me, really appreciate it.
Click to expand...
Click to collapse
I see that so far you have found a way to disable knox AND cripple your Mega...
IMHO the best way to fix this situation is:
1. Download once more your newest firmware I9205XXUCNA3 (e.g. from Sammobile) and flash it by Odin to resolve starting position. Or try to restore your firmware through Kies.
2. Then BEFORE YOU DO SOMETHING read forums to find information how safely root firmware with KNOX. You have to be known so probably your warranty is already void and if not so it will be on the first attempt to root your unit. You are warned... There are some threads about rooting KNOX-ed firmware and even how to come back (partially) to previous build.
BEWARE! Do not attempt to flash older firmware lest you brick your Mega. New bootloader prevent from downgrading and if you try you will have endless bootloop. Upgradindg to newest firmware is one way trip.
OK I've followed your advise:
1. Re-download I9205XXUCNA3 from Sammobile and flash using odin.
2. Re-apply vcoreroot-v2
and after reboot.... WALLA!! My phone is back to normal again! And same goes to my internal SDCard, back as normal.
I have a problem with messaging where it keeps on crashing at first. But then I boot into recovery, clear cache and apply factory reset.
Now, all back to normal.
Anyhow, thank you so much for the tips. Now I can ease out a bit
nuar_y said:
OK I've followed your advise:
1. Re-download I9205XXUCNA3 from Sammobile and flash using odin.
2. Re-apply vcoreroot-v2
and after reboot.... WALLA!! My phone is back to normal again! And same goes to my internal SDCard, back as normal.
I have a problem with messaging where it keeps on crashing at first. But then I boot into recovery, clear cache and apply factory reset.
Now, all back to normal.
Anyhow, thank you so much for the tips. Now I can ease out a bit
Click to expand...
Click to collapse
I am glad you are successful. Sometimes you have to repeat two times, but no more: one for download errors, two for your errors. But if then you are not successful... then you have to look for another solution...
Can I know what rom u are using before updating to stock rom using kies?
Sent from my GT-I9205 using XDA Free mobile app
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?
I don't mean to beat a dead horse, as I'm sure it's been brought up. But every search I've done just brings up how to update to OC1 without losing root. All the way back to the original Motorola Droid, I've always rooted and added a custom recovery and ROM to every phone I've had. I was running Hyperdrive RLS20 and loved it. I've been using Hyperdrive since my Galaxy S3. Then I saw Hyperdrive RLS21 came out and decided I wanted to give it a shot. And although I've flashed over a few hundred ROMs no problem, this time really screwed my phone. I could only get into DL mode. I tried about 25 different ways until I had Kies fix it, which put it on 5.0.1. Can I revert down with Odin? Or is there anything I can do to get root and SU back. Any help would be much, MUCH appreciated
Nope, by taking the latest OTA (or in this case Kies) you've locked yourself into the latest version, for which there is currently no Root
That sucks. No way to use Odin in order to downgrade or anything? This is the first time since I've ever owned an android phone that I've been stuck without root
52brandon said:
That sucks. No way to use Odin in order to downgrade or anything? This is the first time since I've ever owned an android phone that I've been stuck without root
Click to expand...
Click to collapse
Nope. Locked Bootloader sucks.
Every single time there is an update these individuals always end up in this situation! !! No matter how many times they're told to wait and just not update!!!
Charlie115 said:
Every single time there is an update these individuals always end up in this situation! !! No matter how many times they're told to wait and just not update!!!
Click to expand...
Click to collapse
Don't lump me In with that crowd. I had no intention on going to 5.0.1. If you read my original post, I was upgrading to Hyperdrive KK21 from KK20 (and yes, I followed every single instruction to the T. My only guess is that the USB connection got messed up and only flashed a portion causing the problems) and it **** the bed mid-update. I couldn't get into SS recovery or even stock recovery, only DL mode. I spent 2 days without a working phone trying to flash every single Odin file that retained root and they all failed. So I used Kies to try to repair it and ended up ****ed on 5.0.1. The one solution I didn't want. I've NEVER had an android since the D1 that wasn't rooted running a custom ROM. Which is why I'm so desperately trying to get back to rooted. While 5.0.1 is actually a very nice OS, not having all the root options is killing me. And since its now 2 generations old, my hopes that a root exploit will be found, or that people even care enough to try to find one are extremely low. But, I sure hope I'm wrong, and that an exploit for one of the newer generations Galaxies will work on this one too. I'm OCD about having root and this is killing me
52brandon said:
I couldn't get into SS recovery or even stock recovery, only DL mode. I spent 2 days without a working phone trying to flash every single Odin file that retained root and they all failed.
Click to expand...
Click to collapse
If you're ever in this situation again, give up on retaining your current root, flash back to true stock (with a re-partition .pit file as well), and re-root. If you had flashed the nc5 full-wipe with the .pit file and just restored root from a clean system, you would have been fine.
52brandon said:
Don't lump me In with that crowd. I had no intention on going to 5.0.1. If you read my original post, I was upgrading to Hyperdrive KK21 from KK20 (and yes, I followed every single instruction to the T. My only guess is that the USB connection got messed up and only flashed a portion causing the problems) and it **** the bed mid-update. I couldn't get into SS recovery or even stock recovery, only DL mode. I spent 2 days without a working phone trying to flash every single Odin file that retained root and they all failed. So I used Kies to try to repair it and ended up ****ed on 5.0.1. The one solution I didn't want. I've NEVER had an android since the D1 that wasn't rooted running a custom ROM. Which is why I'm so desperately trying to get back to rooted. While 5.0.1 is actually a very nice OS, not having all the root options is killing me. And since its now 2 generations old, my hopes that a root exploit will be found, or that people even care enough to try to find one are extremely low. But, I sure hope I'm wrong, and that an exploit for one of the newer generations Galaxies will work on this one too. I'm OCD about having root and this is killing me
Click to expand...
Click to collapse
Well, you should have known better than to use kies...
Sent from my SCH-I545 using XDA Free mobile app
Honestly I don't even think that devlopers will make much effort to even find out how to root this version as its says that this is one of two updates before getting lollypop.
Development Forums are for developers to share their work and post their Roms and Mods.
Questions belong in the Q&A section.
Thread has been moved to correct section, please pay attention to XDA rules.
Root
52brandon said:
I don't mean to beat a dead horse, as I'm sure it's been brought up. But every search I've done just brings up how to update to OC1 without losing root. All the way back to the original Motorola Droid, I've always rooted and added a custom recovery and ROM to every phone I've had. I was running Hyperdrive RLS20 and loved it. I've been using Hyperdrive since my Galaxy S3. Then I saw Hyperdrive RLS21 came out and decided I wanted to give it a shot. And although I've flashed over a few hundred ROMs no problem, this time really screwed my phone. I could only get into DL mode. I tried about 25 different ways until I had Kies fix it, which put it on 5.0.1. Can I revert down with Odin? Or is there anything I can do to get root and SU back. Any help would be much, MUCH appreciated
Click to expand...
Click to collapse
KingRoot 4.1 rooted my galaxy s4 on oc1....and try flashing an nc5 tar in flashfire
You cannot flash anything with flashfire. If you flash that tar, you WILL brick.
Question
Just wondering, i have rooted my OC1 with Kingroot 4.1, now, can someone make a guide showing how to downgrade from OC1?
PD:. Sorry for my horrible english.
Epiphany^ said:
Just wondering, i have rooted my OC1 with Kingroot 4.1, now, can someone make a guide showing how to downgrade from OC1?
PD:. Sorry for my horrible english.
Click to expand...
Click to collapse
You can't downgrade from OC1.
Downgrade isn't a root issue, it is a bootloader issue. Unless the bootloader gets unlocked, we're stuck on OC1
kingroot does work
I had done the dumb thing and was impatient and did the oc1 update to later find out you can not downgrade and im on Verizon Samsung galaxy s4 (sch-i545) which even on kit kat is very limited to rooting it.. but on a whim I seen a post about king root and it mentioned that and I did see this myself but it will say not supported like it did on mine. but I figured what the hell.. whats the worst that could happen... well im rooted now and only tried because I had seen others make that comment.. well kingroot works for s4 Verizon with locked bootloader.. no need to downgrade from oc1.. just get the app and click... took less than 10 mins if I rememner right.. and I have had no pronlems in 3 days.. it oddly even fixed some of the bugs I was having with oc1 like incoming calls not ringing
Munk3ybones said:
I had done the dumb thing and was impatient and did the oc1 update to later find out you can not downgrade and im on Verizon Samsung galaxy s4 (sch-i545) which even on kit kat is very limited to rooting it.. but on a whim I seen a post about king root and it mentioned that and I did see this myself but it will say not supported like it did on mine. but I figured what the hell.. whats the worst that could happen... well im rooted now and only tried because I had seen others make that comment.. well kingroot works for s4 Verizon with locked bootloader.. no need to downgrade from oc1.. just get the app and click... took less than 10 mins if I rememner right.. and I have had no pronlems in 3 days.. it oddly even fixed some of the bugs I was having with oc1 like incoming calls not ringing
Click to expand...
Click to collapse
You have root. But you have a much lower chance of getting an unlocked Bootloader than anyone on NC5/NK1/NK4. They have root, module loading, and a potential for kexec to run custom kernels.
Don't upgrade to OC1 via OTA if you haven't already everyone! Use Muniz_ri's keeproot upgrade method!
Sent from my Nexus 6 using Tapatalk
---------- Post added at 12:53 AM ---------- Previous post was at 12:53 AM ----------
bigg6987 said:
Downgrade isn't a root issue, it is a bootloader issue. Unless the bootloader gets unlocked, we're stuck on OC1
Click to expand...
Click to collapse
Even then you're stuck. Rollback has little to do with the BL. Rollback is set at a much lower level (physically).
Sent from my Nexus 6 using Tapatalk
I am going crazy trying to resolve my issue. I was tasked with getting CM13 onto a new S4 I545VRUFNK1. The only root that worked was Kingo Root despite several website claiming that towelroot or one click would work, they DID NOT. After installing TWRP and the 3.0.1 recovery, when i go into recover a Verizon message appears saying the software is not authorized so it won't work.
There are several version of this phone which is contributing to the problem. At this point I want to get a stock rom of 4.4.2 and flash it with odin and get it back to the way it was before I tried to do this.
samsmobile won't let me download, samsung-firmware.org only lets me get 3/4 of it and I can't resume it. Everyone wants money for this firmware and even that seems to not work and I probably have to cancel a credit card and dispute the charge
Can someone please either tell me how to bypass the verizon warning so I can get CM13 (i found a thread that talked about editing some system files, but looked very risky) or even better, help me with a download of the firmware, should be 1.5 GB in size so I can reflash with Odin
Please help before I or the phone break
Use samsung kies for the firmware. You will not get cm13 on nk1, stop trying or you will hard brick.
Sent from my SCH-I545 using XDA-Developers mobile app
http://forum.xda-developers.com/showthread.php?t=2735172
you are never going to get CM or ASOP or any rom that requires a custom bootloader/recovery/kernel to run on the S4
its not possible