[Q] Soft bricked SCH-I545!! HELP PLEASE!!! - Verizon Samsung Galaxy S 4

I made the mistake of trading phones with a guy whose GS4 was rooted with SS recovery and there were no MSD in it when we traded. I brought it home, restarted it. And it began to get stuck on the "FIRMWARE UPGRADE ENCOUNTERED AN ISSUE. PLEASE SELECT RECOVERY MODE IN KIES & TRY AGAIN." which I know to not use Kies as it was useless to me when I had my first GS4 at time of launch. I am fairly new at this with a gs4. I have tried and tried with ODIN v3.07. I have been on here and looking through forums and I went to other forums besides xda with countless different trials. NONE have been even the slightest bit helpful...
I was wondering since it was stuck on the devilish yellow triangle screen. I can not even get past this to get the launcher... could ADB be the problem since I can't get it to even boot up to enable it?
before anyone asks, to which will waste both our time....
yes, i have used the stock vz firmware and placed it in the PDA section in ODIN
THIS IS WHAT I GET EVERY TIME.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUAME7_I545VZWAME7_I545VRUAME7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
ALL HELP IS MUCH APPRECIATED!!:good:

Are you sure you were on ME7? You might need to flash a newer firmware.
Sent from my NCC-1701 using Tapatalk.

Definitely need to flash newer firmware

degradedtree69 said:
I made the mistake of trading phones with a guy whose GS4 was rooted with SS recovery and there were no MSD in it when we traded. I brought it home, restarted it. And it began to get stuck on the "FIRMWARE UPGRADE ENCOUNTERED AN ISSUE. PLEASE SELECT RECOVERY MODE IN KIES & TRY AGAIN." which I know to not use Kies as it was useless to me when I had my first GS4 at time of launch. I am fairly new at this with a gs4. I have tried and tried with ODIN v3.07. I have been on here and looking through forums and I went to other forums besides xda with countless different trials. NONE have been even the slightest bit helpful...
I was wondering since it was stuck on the devilish yellow triangle screen. I can not even get past this to get the launcher... could ADB be the problem since I can't get it to even boot up to enable it?
before anyone asks, to which will waste both our time....
yes, i have used the stock vz firmware and placed it in the PDA section in ODIN
THIS IS WHAT I GET EVERY TIME.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUAME7_I545VZWAME7_I545VRUAME7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
ALL HELP IS MUCH APPRECIATED!!:good:
Click to expand...
Click to collapse
This has happened to me about four times with my phone. I was able to fix through a process of Kies and Odin. It seems that if you do all that you can in Kies, as far as attempting to re-install the stock firmware. Kies has the drivers you need in order for Odin to work. You will need to run through the Kies process (it will fail), but you will get the drivers you need. You will then need to boot into download mode and do the Odin flash process. This is all assuming you have the correct files for Odin. You will need to flash the stock build afterwards unless you have a backup and are able to access safestrap which i doubt you will have.

Related

[Q] Kies broke my phone, is it recoverable?

Hi Guys
I was having some trouble connecting my Galaxy S2 to my comp this evening to transfer some photos. Downloaded and installed Kies and it said there was a software update. Went through with it, upgrading to Icecream Sandwich (or w/e its called) but during the installation process it failed (can't remember the exact error message).
My phone is now unable to switch on, just showing the error message:
"Firmware upgraded encountered an issue. Please select recovery mode in Kies and try again."
Unfortunately, Kies will not locate my device and will not go through with recovery.
After some searching I came accross this forum, and specifically http://forum.xda-developers.com/showthread.php?t=1449771]this thread.
I've worked my way through that. I can flash the kernel succesfully through Odin (says pass) but when I try and flash the firmware it fails.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-I9100_NEW_BOOTLOADER.tar.md5 is valid.
<OSM> I9100PBVKL2_I9100PORALB1_I9100PBVKL2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
Get the same trying to use Bootloader aswell.
Now I'm guessing my warranty is now voided, so is there anything I can do to save my phone or is it completely b0rked?
Help much appreciated.
Some details from under my battery
Model GT-I9100P
SSN: I9100PGSMH
Any other details you need?
Bare in mind i cannot get into the phone at all.
Is it possible that I need to use the ICS recovery package rather than the Gingerbread?
i think u need full rom with pit and ur phone will work
Hi, thanks for your reply.
Unfortunately I'm in work and don't have a comp with full access. Any chance you could possibly link the files I need or at least point me in the right direction.
Many thanks.

Phone is screwed..

Not sure which CWM I was coming from, but I wanted to go back to stock. Here is what I did:
C:\Users\Brian\Downloads\Cell Phone\CI500_VZW_EH03_GB_CM.tar.md5
C:\Users\Brian\Downloads\Cell Phone\atlas_v2.2.pit
I select the partition box and got this error.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI500_VZW_EH03_GB_CM.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> param.lfs
<ID:0/003> Sbl.bin
<ID:0/003> boot.bin
<ID:0/003> recovery.bin
<ID:0/003> zImage
<ID:0/003> factoryfs.rfs
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help. I dont know what else to do. Thanks so much.
I literally have tried everything. Not sure if the .tar is incorrect, or what is happening. Phone wont turn on though, its stuck on the samsung logo boot.
Have you:
Tried a different usb cable (or several)?
Tried a different usb port?
Tried a different OS?
Tried a different version of Odin?
Tried redownloading the files?
Tried stock 2.2 Froyo instead?
Looks like it was the USB cable. Damn i spent like 2 hours researching and trying everything . Thanks for the response bro. Have a good one.
No problem, it's always the last thing you think of. Glad you got it though

[Q] S4 s/w upgrade issue - Soft brick

Hi folks. Longtime rooter and reader, but first time poster.
I attempted the S4 (VZW) s/w upgrade released today, using Kies, and during the process it froze and error-ed the following on my phone:
"Firmware upgrade encountered and issue. Please select recover mode in Kies & try again."
Of course, I've attempted the emergency recovery option a few times in Kies with no success. It will recognize my phone and the emergency recovery file, but will not actually send any data to the device to flash back to pre-s/w update.
So, I did a bunch of reading and d/l-ed a few stock roms to flash back using Odin (3.07). I get the same error with all roms as follows:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Erase...
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I can go into more detail on the roms attempted if necessary, but this seems like a phone/user issue as all the rom attempts responded with the same authorization error.
Thoughts and/or next steps?
Edit:
I was able to get Kies to start an emergency recovery d/l, but it failed part way through. Pic of error attached.
Same Problem
Hey man,
my gs4 is failing at the same part....did you happen to figure out a solution?
most of galaxy S4 new security ( i545, i9505, SC-04E) phones end up with aboot.mbn coz of old firmware version. check firmware version before write with odin. i got same prob with SC-04E new security comes with MUAMG2 firmware. i have try to downgrade with MUAMDI and MUAMF1. both ends with aboot.mbn error. but it worked with MUAMF2 version.
always try to update with same or new version. downgrade will end up with this error.
regards..
same issue
i have the same issue with my phone, anyone found a solution yet?

[Q] Error while using ODIN to flash to stock.

Hi, I'm trying to restore my phone to stock using ODIN.
I have Odin 3.09 and have the latest Scamsung Kies installed (for the usb driver).
The file I am flashing is: http://www.androidfilehost.com/?fid=23203820527944861
The message log I get from Odin is:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Not really sure what I'm doing wrong. My phone was on the ME7 version (And running a SafeStrap rom) before I wanted to restore it today.
xMopx said:
Hi, I'm trying to restore my phone to stock using ODIN.
I have Odin 3.09 and have the latest Scamsung Kies installed (for the usb driver).
The file I am flashing is: http://www.androidfilehost.com/?fid=23203820527944861
The message log I get from Odin is:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Not really sure what I'm doing wrong. My phone was on the ME7 version (And running a SafeStrap rom) before I wanted to restore it today.
Click to expand...
Click to collapse
You can't flash backwards. Flash me7.
gnubian said:
You can't flash backwards. Flash me7.
Click to expand...
Click to collapse
That makes sense, I wasn't aware that I was using an older firmware file. I'm having trouble finding the ME7 file, could you point me to a copy? Thanks!
xMopx said:
That makes sense, I wasn't aware that I was using an older firmware file. I'm having trouble finding the ME7 file, could you point me to a copy? Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2357235
That will wipe everything, so make sure to back up your files if you haven't already. Good luck!
gnubian said:
http://forum.xda-developers.com/showthread.php?t=2357235
That will wipe everything, so make sure to back up your files if you haven't already. Good luck!
Click to expand...
Click to collapse
Thanks! But with that file I got this error:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Which from what I could find, meant I needed to repartition. So I grabbed the Pit file in this thread: http://forum.xda-developers.com/showthread.php?t=2290859
But got this:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
Edit: I did have Safestrap recovery installed - do I need to flash a stock recovery or is it contained in that firmware file?
xMopx said:
Thanks! But with that file I got this error:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Which from what I could find, meant I needed to repartition. So I grabbed the Pit file in this thread: http://forum.xda-developers.com/showthread.php?t=2290859
But got this:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
Edit: I did have Safestrap recovery installed - do I need to flash a stock recovery or is it contained in that firmware file?
Click to expand...
Click to collapse
Just go to the safestrap app in app drawer on stock slot and uninstall it.
gnubian said:
Just go to the safestrap app in app drawer on stock slot and uninstall it.
Click to expand...
Click to collapse
I can't do that anymore, a result of these failed flashes is that I can't boot the system currently.
xMopx said:
I can't do that anymore, a result of these failed flashes is that I can't boot the system currently.
Click to expand...
Click to collapse
What happens when you start the phone?
gnubian said:
What happens when you start the phone?
Click to expand...
Click to collapse
It says:
FIrmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I tried using the Kies recovery, but it doesn't detect that the phone needs recovering (both on that screen and the download screen used for odin).
xMopx said:
It says:
FIrmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I tried using the Kies recovery, but it doesn't detect that the phone needs recovering (both on that screen and the download screen used for odin).
Click to expand...
Click to collapse
Are you positive you were on me7 and not mj7? Because the error you got for me7 looks the same as the one for mdk...
gnubian said:
Are you positive you were on me7 and not mj7? Because the error you got for me7 looks the same as the one for mdk...
Click to expand...
Click to collapse
Positive. I had installed the rom/recovery before anything newer than me7 was released. And I remember when I upgraded from whatever it shipped with to ME7 because the upgrade window popped up and I tapped Install by accident. I had this installed: http://forum.xda-developers.com/showthread.php?t=2351840.
Edit: to confirm, I found my old post asking about the modules to get that rom to work on ME7: http://forum.xda-developers.com/showthread.php?p=46944438
Was waiting for someone else to chime in who may know more than me. Have you tried booting into recovery from being powered off?
gnubian said:
Was waiting for someone else to chime in who may know more than me. Have you tried booting into recovery from being powered off?
Click to expand...
Click to collapse
No problem, but yeah. After every failure I would battery-pull and go back into recovery.
Edit: Tried a different USB cable and a different computer today. No dice
xMopx said:
No problem, but yeah. After every failure I would battery-pull and go back into recovery.
Edit: Tried a different USB cable and a different computer today. No dice
Click to expand...
Click to collapse
So when you went to recovery it went to stock recovery I'm assuming? Or you got the error?
If it went to stock recovery did you try wiping everything before flashing in odin?
gnubian said:
So when you went to recovery it went to stock recovery I'm assuming? Or you got the error?
If it went to stock recovery did you try wiping everything before flashing in odin?
Click to expand...
Click to collapse
Err sorry, I meant download mode (Power+Voldown). If I try booting into recovery, I get the dead android: http://i.imgur.com/HRWVsvZ.jpg
xMopx said:
Err sorry, I meant download mode (Power+Voldown). If I try booting into recovery, I get the dead android: http://i.imgur.com/HRWVsvZ.jpg
Click to expand...
Click to collapse
Try finding a stock recovery tar for your build and just flashing that in odin.
gnubian said:
Try finding a stock recovery tar for your build and just flashing that in odin.
Click to expand...
Click to collapse
I had the thought of doing this, but wasn't able to find one.
xMopx said:
I had the thought of doing this, but wasn't able to find one.
Click to expand...
Click to collapse
I looked around a little and didn't fine one either. I'd try making a request thread, I'm sure someone knows how to make a tar of it you can use in odin.
gnubian said:
I looked around a little and didn't fine one either. I'd try making a request thread, I'm sure someone knows how to make a tar of it you can use in odin.
Click to expand...
Click to collapse
Isn't the recovery contained in the larger firmware files? What gain would flashing the stock recovery get?
I'm thinking I might just take the phone to a Verizon store and say, "Samsung kies told me it was going to update my phone, I took a shower and when I came back it was like this".
Edit: I untarred the firmware file, and it contained recovery.img. Can I flash that with odin?
xMopx said:
Isn't the recovery contained in the larger firmware files? What gain would flashing the stock recovery get?
I'm thinking I might just take the phone to a Verizon store and say, "Samsung kies told me it was going to update my phone, I took a shower and when I came back it was like this".
Edit: I untarred the firmware file, and it contained recovery.img. Can I flash that with odin?
Click to expand...
Click to collapse
I believe it has to be a tar. If you can get it on there and wipe data/factory reset it may get rid of safestrap and allow you to odin the full stock tar.

[Q] Full Restore - Unrooted FAIL help please

Please help.
i tried to do a stock restore using the method here http://forum.xda-developers.com/show....php?t=2657828 and there was an error. i did this before and it worked now it failed.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
the phone doesn't want to start and it says " firmware upgrade encountered an issue. Please select recovery mode in kiess & try again." i tried that but i doens't work. if i start the odin one-click exe. it tries to instal and i get the same error.
what can i do to restore my android?
Edit: i think i fixed it. i tried the file i had 3~4 times and nothing so i downloaded the nab stock rom fromhttp://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung%20Galaxy%20Note%203%20%28SM-N900P%29/Stock%20ROMs/ and it's installing now. i hope there are no more isues.
Valentin6282 said:
Please help.
Edit: i think i fixed it. i tried the file i had 3~4 times and nothing so i downloaded the nab stock rom fromhttp://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung%20Galaxy%20Note%203%20%28SM-N900P%29/Stock%20ROMs/ and it's installing now. i hope there are no more isues.
Click to expand...
Click to collapse
The NAB file will fix your issues, but I'll address what happened so others can see this thread and learn.
On the Note 3, once you're on Kit Kat (NAB or NC5), you cannot downgrade to Jellybean (MJ4).
Trying to do so will cause the error in OPs post.
There are tons of repositories where you can get stock NAB or NC5 TW Roms (taking a stroll through the Developers Section will find them easily), so all you have to do is try one of those and all of your issues will be solved.

Categories

Resources