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.
Im stuck at boot loader, someone please help!!
Ive got a verizon SCH-i545 running NC5. I did towel root, got root access no problem. I then installed ROM manager and did install recovery. This seemed to work too. Then after installing that, I saw something about safestrap and decided to install that too. So I installed BusyBox and then safestrap and I could boot into safestrap no problem, made a backup of my device and then wiped everything (/data dalvik&system) After that my phone rebooted and went into CWM recovery, i didn't think anything of it and I tried flashing the latest nightly CM11 build (cm-11-20140821-NIGHTLY-jflte.zip) but when I try this it gives me:
E:could not verify whole-file signature
E:signature verification failed
In red and then continues and tries to reboot, but when it does it just gets frozen at the Samsung loading screen. Ive tried a few different CM builds but they all do the same.
Is there a way to disable signature verification? Am I just using the wrong build? Should I try different a different ROM (if so suggestions)?
Thanks and hopefully i didn't permanently brick my phone...
Swigster said:
Im stuck at boot loader, someone please help!!
Ive got a verizon SCH-i545 running NC5. I did towel root, got root access no problem. I then installed ROM manager and did install recovery. This seemed to work too. Then after installing that, I saw something about safestrap and decided to install that too. So I installed BusyBox and then safestrap and I could boot into safestrap no problem, made a backup of my device and then wiped everything (/data dalvik&system) After that my phone rebooted and went into CWM recovery, i didn't think anything of it and I tried flashing the latest nightly CM11 build (cm-11-20140821-NIGHTLY-jflte.zip) but when I try this it gives me:
E:could not verify whole-file signature
E:signature verification failed
In red and then continues and tries to reboot, but when it does it just gets frozen at the Samsung loading screen. Ive tried a few different CM builds but they all do the same.
Is there a way to disable signature verification? Am I just using the wrong build? Should I try different a different ROM (if so suggestions)?
Thanks and hopefully i didn't permanently brick my phone...
Click to expand...
Click to collapse
Ok - bad news - you are screwed! Unless you are on MDK bootloader, you are limited to root, safestrap and a TW-based ROM like Eclipse. No CM! Some people have had some success with an AOSP rom but stick with TW based ones.
Do a factory reset and try flashing a stock build.
Then reroot, load safe strap as before and your TW based rom.
zeb carter said:
Ok - bad news - you are screwed! Unless you are on MDK bootloader, you are limited to root, safestrap and a TW-based ROM like Eclipse. No CM! Some people have had some success with an AOSP rom but stick with TW based ones.
Do a factory reset and try flashing a stock build.
Then reroot, load safe strap as before and your TW based rom.
Click to expand...
Click to collapse
Darn, thanks I was going to try and find a stock ROM and see if that works. Any idea where I can find one?
Also what do you mean when you say TW based ROMS? Is there a way I can get an MDK bootloader?
Swigster said:
Darn, thanks I was going to try and find a stock ROM and see if that works. Any idea where I can find one?
Also what do you mean when you say TW based ROMS? Is there a way I can get an MDK bootloader?
Click to expand...
Click to collapse
How much was your phone?
Do some reading because your going to brick it.
You can use safestrap with roms based on your current kernel version, you can flash roms but cannot change your kernel, so the rom must use the stock kernel. Read threads on safestrap, as well as your current firmware version.
http://forum.xda-developers.com/showthread.php?t=2735172
Do that, root your phone, then read into SafeStrap.
Whoop5 said:
http://forum.xda-developers.com/showthread.php?t=2735172
Do that, root your phone, then read into SafeStrap.
Click to expand...
Click to collapse
Thanks, this is what I have been trying to do but I cant get a valid .md5 file, tried the one from this thread: http://forum.xda-developers.com/showthread.php?t=2484726 but I just cant extract it. Will try this one and hopefully it extracts and I can just get my phone back to stock
Our S4 has a locked bootloader, so you can't just flash whatever you so please. The safest route is to flash a stock NC5 image since that's what you're running. Either the downloads aren't finishing, or your internet is nuts fast (and thus I envy you.)
Whoop5 said:
Our S4 has a locked bootloader, so you can't just flash whatever you so please. The safest route is to flash a stock NC5 image since that's what you're running. Either the downloads aren't finishing, or your internet is nuts fast (and thus I envy you.)
Click to expand...
Click to collapse
So I finally got that file downloaded and extracted but when I load it into Odin after clicking the PDA button it says MD5 hash value is invalid. What does that mean and how do i fix this??
What version of odin are you using? Also which tar file are you using? If you're on kitkat you NEED to use the NC5 tar file that Whoop5 posted. If you use any of the ones that you posted you have a chance of bricking your phone. you should probably use the full wipe stock image. You're going to need the samsung jfltevzw 16g.pit file
You should be able to find the pit file in Surge123's post that Whoop5 has posted here. I can post a odin 3.10 if you need it.
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?
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
I rooted my s4 and installed twrp a long time ago used the phone for a little while then stashed it away. It had the following rom installed I545VRVFNC5 stock root oder I believe it was 4.4.2. The other night I installed flash fire and attempted to flash I545_OC1_Stock_rooted_rom mdk. It flashed ok but now I'm getting the verizon warning message and I can't bypass. I can no longer boot into twrp. I think the bootloader is still unlocked, padlock is unlocked upon boot. How do I get myself out of this message?
looneyk said:
I rooted my s4 and installed twrp a long time ago used the phone for a little while then stashed it away. It had the following rom installed I545VRVFNC5 stock root oder I believe it was 4.4.2. The other night I installed flash fire and attempted to flash I545_OC1_Stock_rooted_rom mdk. It flashed ok but now I'm getting the verizon warning message and I can't bypass. I can no longer boot into twrp. I think the bootloader is still unlocked, padlock is unlocked upon boot. How do I get myself out of this message?
Click to expand...
Click to collapse
Try to Odin back to MDK, if you had TWRP... If that doesn't work, nc5. You can't do custom ROM's like Cynanogenmod, but you have a limited amount of freedom with safestrap.
looneyk said:
I rooted my s4 and installed twrp a long time ago used the phone for a little while then stashed it away. It had the following rom installed I545VRVFNC5 stock root oder I believe it was 4.4.2. The other night I installed flash fire and attempted to flash I545_OC1_Stock_rooted_rom mdk. It flashed ok but now I'm getting the verizon warning message and I can't bypass. I can no longer boot into twrp. I think the bootloader is still unlocked, padlock is unlocked upon boot. How do I get myself out of this message?
Click to expand...
Click to collapse
The open padlock means the firmware you have installed is custom and not stock, doesn't mean your boot loader is unlocked. I would simply boot into download mode and re-image your device back to MDK, if that's where you were. What's your current boot loader version?
looneyk said:
I rooted my s4 and installed twrp a long time ago used the phone for a little while then stashed it away. It had the following rom installed I545VRVFNC5 stock root oder I believe it was 4.4.2. The other night I installed flash fire and attempted to flash I545_OC1_Stock_rooted_rom mdk. It flashed ok but now I'm getting the verizon warning message and I can't bypass. I can no longer boot into twrp. I think the bootloader is still unlocked, padlock is unlocked upon boot. How do I get myself out of this message?
Click to expand...
Click to collapse
Sent from my SCH-I545
SnyderGuy said:
The open padlock means the firmware you have installed is custom and not stock, doesn't mean your boot loader is unlocked. I would simply boot into download mode and re-image your device back to MDK, if that's where you were. What's your current boot loader version?
Sent from my SCH-I545
Click to expand...
Click to collapse
I am using an MDK S4.
I can bit to room, but cannot reboot to recovery.
Corrupted recovery after update via TWRP app.
How exactly, do I re-image my device back to MDK?
Do I use this stock MDK ROM? http://forum.xda-developers.com/gal...ment/rom-i545oc1-5-0-1-100-stock-mdk-t3097902
Do I put it in the BL or AP box in ODIN?
No, that is a ROM. You need the stock official software.
http://forum.xda-developers.com/showthread.php?t=2289325
SHOULD be that one...
Put that in AP
XxD34THxX said:
No, that is a ROM. You need the stock official software.
http://forum.xda-developers.com/showthread.php?t=2289325
SHOULD be that one...
Put that in AP
Click to expand...
Click to collapse
I just read it all. Looks like fun!
I sure would like to know what I did wrong. I only used the TWRP app to update TWRP.
pizza_pablo said:
I just read it all. Looks like fun!
I sure would like to know what I did wrong. I only used the TWRP app to update TWRP.
Click to expand...
Click to collapse
That I cannot answer since I do not have MDK. My assumption is a corrupted download of TWRP or a partial install that was interrupted for some reason.
XxD34THxX said:
That I cannot answer since I do not have MDK. My assumption is a corrupted download of TWRP or a partial install that was interrupted for some reason.
Click to expand...
Click to collapse
That may have been the case, since my connection was weak.
I'm just about to do the deed and I checked phone info and the bootloader is now I545VRUFNK4, vice MDK.
Here I go....
Well....I tried these to .tar files with no luck:
http://www.rwilco12.com/downloads.p...Galaxy S4 (Verizon) (SCH-I545)/Stock ROMs/TAR
https://www.androidfilehost.com/?fid=22979706399752783
I did get the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Now, I no longer have the option to cancel Download Mode and bot ROM.
I didn't want to do anything in Kies, for fear of taking an OTA.
Do I have any options?
Even just taking an OTA and selling a former MDK treasure?
This seems to be happening a lot. A LOT. Before you try kies, go into device manager and uninstall the Samsung USB drivers. Then download the DRIVERS ONLY from Sammobile/Samsung. THEN use Odin with a full wipe and repartition of MDK. If you get the same message again, then you have lost the MDK bootloader, and will have to repeat the process with an nc5 tar, which will loose custom ROMs, but you will have root and safestrap.
XxD34THxX said:
This seems to be happening a lot. A LOT. Before you try kies, go into device manager and uninstall the Samsung USB drivers. Then download the DRIVERS ONLY from Sammobile/Samsung. THEN use Odin with a full wipe and repartition of MDK. If you get the same message again, then you have lost the MDK bootloader, and will have to repeat the process with an nc5 tar, which will loose custom ROMs, but you will have root and safestrap.
Click to expand...
Click to collapse
OK. So I am going to uninstall Kies, just for safety sake. Uninstall the Samsung PC drivers. Reinstall the PC drivers.
Use ODIN to flash this http://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung%20Galaxy%20S4%20%28Verizon%29%20%28SCH-I545%29/Stock%20ROMs/TAR in the AP box. Sacrifice a chicken and dance with snakes.
What do you think may have caused the bootloader to change?
At this point I guess any use of the phone will be a positive and somehow retaining MDK will be a miracle.
Thanks, for your assistance, as I am at a loss, at this point!
that is a .gz, so make sure to unip it/ delete that extension so Odin can use it.
My assumption is you may have accidently flashed the entire nk4, not just one with the MDK stuff still in.
XxD34THxX said:
that is a .gz, so make sure to unip it/ delete that extension so Odin can use it.
My assumption is you may have accidently flashed the entire nk4, not just one with the MDK stuff still in.
Click to expand...
Click to collapse
I used the link file, from my last post.
After I unzip it, delete the " .gz "
Got it. Thanks, again!
XxD34THxX said:
that is a .gz, so make sure to unip it/ delete that extension so Odin can use it.
My assumption is you may have accidently flashed the entire nk4, not just one with the MDK stuff still in.
Click to expand...
Click to collapse
So I just looked at the computer file and there was no .gz extention on the file I flashed thru ODIN.
It was not zipped, either.
On the xda page that you link, there was another choice on thier link. It was titled "one click". It is an .exe, titled "SCH-I545_MDK_562219_Stock_Restore.exe" .
What could ODIN do with this?
The other file I found, that I tried, but no change, was titled "VRUAMDK_NoWipe.tar.md5" .
Do you have any other suggestions,please?
Use the Full wipe in this thread:
http://forum.xda-developers.com/showthread.php?t=2301259
If that does not fix anything you have either
A)Hard Brick(unlikely since the device is semi-working)
B) lost MDK.
XxD34THxX said:
Use the Full wipe in this thread:
http://forum.xda-developers.com/showthread.php?t=2301259
If that does not fix anything you have either
A)Hard Brick(unlikely since the device is semi-working)
B) lost MDK.
Click to expand...
Click to collapse
I used this one, the other night, with no change, but this time I will delete Kies and phone drivers, then reinstall phone drivers, before ODIN.
You're a champ!
XxD34THxX said:
Use the Full wipe in this thread:
http://forum.xda-developers.com/showthread.php?t=2301259
If that does not fix anything you have either
A)Hard Brick(unlikely since the device is semi-working)
B) lost MDK.
Click to expand...
Click to collapse
Do I remove the .md5 extension as well as the .gz and just leave the .tar on the end?
ETA: Well, I tried removing both extensions and ODIN would not take it. Received error pop up.
I tried, with no success, ODIN flashing the full wipe and no wipe tars, with no success.
Giving up for the night.
XxD34THxX said:
This seems to be happening a lot. A LOT. Before you try kies, go into device manager and uninstall the Samsung USB drivers. Then download the DRIVERS ONLY from Sammobile/Samsung. THEN use Odin with a full wipe and repartition of MDK. If you get the same message again, then you have lost the MDK bootloader, and will have to repeat the process with an nc5 tar, which will loose custom ROMs, but you will have root and safestrap.
Click to expand...
Click to collapse
I woke up in the middle of the night and something popped into my head and I couldn't get back to sleep, so here we go....
The phone was on Echoe v49 which is Lollipop and I didn't like it. So I decided to go to the last Echoe version that was KitKat, v34.
I flashed this https://www.androidfilehost.com/?fid=95747613655044521 Which apparently is T-Mobile based, and the v20 international patch.
What popped into my head was that maybe my phone was thinking it was a T-Mobile S4, because I picked the wrong kernel. At the time everything seemed to work, except sending SMS. I could make phone calls and receive SMS.
This is was got me out of bed. I went to my notes for the Aroma install, to see what kernel I chose. I recalled picking the stock kernel, which may have been T-Mobile, but my notes say that I picked KTOONES kerenel in Aroma and in the Patcher, picked ADD VZW FILES AND BUILD PROP and NO KERNEL.
I was thinking that I had put a VZW version of TWRP onto a "T-Mobile" S4, getting me stuck to bootup in Download mode only, but still able to cancel Download and boot to system. Then I ODINed the VZW MDK stock firmware and am now with either Download mode or the yellow PC connected to phone screen, with the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I woke up thinking that maybe I had a T=mobile kernel and when I lost TWRP and only had stock recovery, downloaded the VZW version of TWRP on top of T=Mobile install. But the note makes it look like I would have been OK as far as the phone thinking it was a VZW S4.
Sorry if rambling, just trying to pass as many details and thoughts as possible.
Do I have any options, now?
I downloaded the stuff to do Heimdall One Click and was thinking about trying that route, with a file named "SCH-I545_MDK_562219_Stock_Restore.exe"
I have a 32GB MDK VZW SCH-i545 S4 that is running fine on ECHOE v29. Can I copy anything from that phone and flash in ODIN to recover the 16GB (was MDK) VZW SCH-i545 that is stuck on Download mode only?
Is there any way to flash a NANDROID via ODIN or some other program from a PC thru ODIN?
hmmm.. The Ktoonez kernal works on any s4. But if you flashed T mobile Files, which I don't think was the case since you flashed the Verizon stuff... I have never used Heimdall, so I can't comment on that. I don't know what to say. There might be a way to make a debrick image... Someone more experienced will have to help, sorry.
XxD34THxX said:
hmmm.. The Ktoonez kernal works on any s4. But if you flashed T mobile Files, which I don't think was the case since you flashed the Verizon stuff... I have never used Heimdall, so I can't comment on that. I don't know what to say. There might be a way to make a debrick image... Someone more experienced will have to help, sorry.
Click to expand...
Click to collapse
No need to apologize! You have helped all you can. I appreciate it greatly!
I just want to ensure that I exhaust ALL possibilities of recovering the MDK, before I throw in the Kies upgrade towel.
I wonder if I'll get in hot water for starting a new thread.....