So I was on lineage 7.1 when I decided to update TWRP for some reason . Anyway after that my phone only booted to download mode and Unauthorized software warning thingi.
So I thought hmm well I can fix this by going back all the way to VRUAMDK. So I flash VRUAMDK-No-Wipe with odin 3.07 but now get a boot loop at the verizon logo.
Followed this guide:
https://forum.xda-developers.com/showthread.php?t=2301259
My question is, does anyone have the fully stock VRUAMDK firmware? I cant find an active link anywhere. OR Should I just try flashing some available stock firmware and lose my unlocked bootloader?
Really any advice would be welcome.
Thanks!
Edit- after exhaustive searching I have found https://www.rwilco12.com/Files/Devices/Samsung Galaxy S4 (Verizon) (SCH-I545)/Stock ROMs/ with a stock rom that worked. I hope that link helps anyone out there looking for a working mdk rom.
Related
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 just realized I'm in the wrong subforum, please move to Verizon i535 forum, thanks]
My initial intention was to backup the phone before attempting to install Cyanogenmod on it.
I ran towelroot and installed Rom Manager, and flashed the custom recovery.
Upon attempting to enter recovery, it's telling me that some non-Verizon system software is detected so I can't even get in there to backup my phone. I researched and apparently after 4.2 all the bootloaders are locked and cannot be rommed. That sucks, but anyway, this thing is already running 4.4.2 (just got in from Ebay purchase).
How can I get back the stock recovery? I've searched all over the forums but can't quite find what to do. Something with Odin and a stock image? Does that exist for 4.4.2?
TIA
You can get stock recoveries on the net but if you cant flash it you need to go to samsung-updates.com and download the latest rom for that device, flash it with odin then re root it. If there's a cf-autoroot for it you should use that, otherwise any other recommended method.
If your lastest rom on the website is earlier than 4.3 then dont worry about efs etc as custom roms dont change that
If it IS 4.3 or later do not flash anything lower than 4.3. This is because you dont know what the last stock version was.
Going back to stock via odin should solve any issues with all sammy devices. Common sense and reading a lot goes a long way.
Dont forget to reset to factory when flashing back to stock, most common cause of boot loop.
Sent from a stolen phone!
I have the Verizon Galaxy s4 and I rooted it and attempted to install the cm-12.1 custom rom. I could not get CWM to work so I went to the safestrap route. My phone got stuck booting into recovery so I flashed stock everything VIA Odin. It failed. So now I'm stuck with the message at start up "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again".
Please HELP.
P.S It is the SCH-I545 model.
WarCrazy said:
I have the Verizon Galaxy s4 and I rooted it and attempted to install the cm-12.1 custom rom. I could not get CWM to work so I went to the safestrap route. My phone got stuck booting into recovery so I flashed stock everything VIA Odin. It failed. So now I'm stuck with the message at start up "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again".
Please HELP.
P.S It is the SCH-I545 model.
Click to expand...
Click to collapse
What were you on... CM-12 does not work on any bootloader besides MDK. It does not work with safestrap. It will not work with CWM. Odin with a FULL NC5 WIPE. If that does not work, its bricked. Possibly JTG, but I doubt it. Read more before you do something. This could have been avoided.
XxD34THxX said:
What were you on... CM-12 does not work on any bootloader besides MDK. It does not work with safestrap. It will not work with CWM. Odin with a FULL NC5 WIPE. If that does not work, its bricked. Possibly JTG, but I doubt it. Read more before you do something. This could have been avoided.
Click to expand...
Click to collapse
Well, I did everything from a different site instructions. But I appreciate the reply. I did thankfully fix my phone by connecting it to Kies which restored firmware. Problem now, I lost root access and I upgraded to 5.0.1 lollipop from 4.2.2 kitkat and I now can't seem to find a rooting option now. Running SCH-I545 VRUGOC1.
Can you point me to the right direction? I've decently looked around, don't see any way to do it?
WarCrazy said:
Well, I did everything from a different site instructions. But I appreciate the reply. I did thankfully fix my phone by connecting it to Kies which restored firmware. Problem now, I lost root access and I upgraded to 5.0.1 lollipop from 4.2.2 kitkat and I now can't seem to find a rooting option now. Running SCH-I545 VRUGOC1.
Can you point me to the right direction? I've decently looked around, don't see any way to do it?
Click to expand...
Click to collapse
No root for OC1. No downgrade either as a qfuse has been blown.
After an unsuccessful flash of Xposed Framework with Chainfire's FlashFire Beta, my device wouldn't boot past the AT&T logo. I attempted to flash NB1 stock firmware using Odin from OC4, but I have the same issue.
Specifics
Device - Samsung Galaxy S4 AT&T (jflteatt)
Firmware - NB1 Stock I think, KNOX flag is untripped but download says I have custom Android version. Tried flashing with Odin and got reset/pass. KNOX flag was tripped before, I read its an eFuse so I'm confused
Should I try flashing again or what... I'd like a quick answer as I currently have no phone. Mod feel free to move this if its in the wrong forum. If you need more information just let me know
Samsung devices are know to have issue with xposed. They made changes to the art runtime and last I heard xposed has not fixed it yet.
So if I want Xposesd I should stay on KitKat
How can I get my device working... I've tried what other threads suggested (cache wipe, factory reset, battery pull for thirty seconds). Should I try the stock image again with Odin or try Kies?
bsch27 said:
So if I want Xposesd I should stay on KitKat
How can I get my device working... I've tried what other threads suggested (cache wipe, factory reset, battery pull for thirty seconds). Should I try the stock image again with Odin or try Kies?
Click to expand...
Click to collapse
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
xposed works fine on lollipop, but you have to use wanams version of the framework for tw
OK, thanks for the advice. FlashFire can run with a locked bootloader, right?
Also, I still can't figure out how to get my phone booting again I would greatly appreciate advice on how to get past the at&t logo
EDIT
My bootloader is locked so I can only flash with Odin and stock recovery. Took the AT&T OTA before I knew what I was doing.
I found the solution! I was trying to flash a MBL stock AIO with Odin, but after I took an OTA from AT&T a while back, they locked downgrading that far because it's vulnerable to Loki. I found a thread on another forums that stated the firmware was mislabeled. I feel lucky, could have hard bricked it! I managed to install a (proper) deodexed NB1 firmware, rooted it with Towelroot, and upgraded to Lollipop through a FlashFire flash. I was able to install Xposed successfully. Thanks for all the help! It's greatly appreciated!
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.