Here is what has happened:
1. Successfully rooted Note 3
2. Attempted to do WIFI tether hack by changing services.jar and services.odex
3. Rebooted phone and it started up fine but hung on the yellow spring screen (must have downloaded an incompatible version)
4. Tried to reset to factory in recovery mode but it didn't work; still hung on the yellow screen
5. Tried to use KIES to download firmware but it does not recognize the phone with either v2.6 or v3.0
6. Downloaded stock firmware and attempted to flash through ODIN 3.07 but it failed
7. Next I attempted to flash stock FW through ODIN 3.09 but lost power and now I get "firmware upgrade encountered an issue" error
8. It says go to KIES recovery mode but it does not recognize the phone
Here is ODIN 3.9 dialog:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900PVPUBMJ4_N900PSPTBMJ4_N900PVPUBMJ4_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> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<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)
Can anyone help me get this fixed at least to stock?
aksaunders said:
Here is what has happened:
1. Successfully rooted Note 3
2. Attempted to do WIFI tether hack by changing services.jar and services.odex
3. Rebooted phone and it started up fine but hung on the yellow spring screen (must have downloaded an incompatible version)
4. Tried to reset to factory in recovery mode but it didn't work; still hung on the yellow screen
5. Tried to use KIES to download firmware but it does not recognize the phone with either v2.6 or v3.0
6. Downloaded stock firmware and attempted to flash through ODIN 3.07 but it failed
7. Next I attempted to flash stock FW through ODIN 3.09 but lost power and now I get "firmware upgrade encountered an issue" error
8. It says go to KIES recovery mode but it does not recognize the phone
Here is ODIN 3.9 dialog:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900PVPUBMJ4_N900PSPTBMJ4_N900PVPUBMJ4_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> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<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)
Can anyone help me get this fixed at least to stock?
Click to expand...
Click to collapse
U can't downgrade bootloader you need to install nab or nc5 in Odin ....can't use mj4 won't work as your phone must have already been on kit kat
Sent from my SM-N900P using Xparent BlueTapatalk 2
Downlloading NC5
Epix4G said:
U can't downgrade bootloader you need to install nab or nc5 in Odin ....can't use mj4 won't work as your phone must have already been on kit kat.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I am downloading an nc5 .tar now. I am in the middle of the New Mexico desert on military duty so I am connecting to my phone as a hotspot and it takes forever. My DL speed is fluctuating between 185-200 kb/s. Do you know of any private links for either a nab or nc5 that would be faster for me?
Epix4G said:
U can't downgrade bootloader you need to install nab or nc5 in Odin ....can't use mj4 won't work as your phone must have already been on kit kat
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Overnight, I downloaded the SM-N900P NC5 Full Restore Unrooted (Compressed Archive).exe. This morning, I followed the instruction in that XDA post, plugged the phone, hit start, and crossed my fingers. Fifteen minutes of sweating later I had a factory stock phone again and I let out that big breath I was holding. Now, I am deciding if I want to root again and try another wifi hack. Thanks for the help. You are a lifesaver...a phone save for sure.
aksaunders said:
Overnight, I downloaded the SM-N900P NC5 Full Restore Unrooted (Compressed Archive).exe. This morning, I followed the instruction in that XDA post, plugged the phone, hit start, and crossed my fingers. Fifteen minutes of sweating later I had a factory stock phone again and I let out that big breath I was holding. Now, I am deciding if I want to root again and try another wifi hack. Thanks for the help. You are a lifesaver...a phone save for sure.
Click to expand...
Click to collapse
Congratulations! Your Knox flag is still 0x1 though so you are not "factory stock". Once you root and/or install a custom recovery that flag is set and can't be reset, at least not on our phones yet.
Still Happy
JimSmith94 said:
Congratulations! Your Knox flag is still 0x1 though so you are not "factory stock". Once you root and/or install a custom recovery that flag is set and can't be reset, at least not on our phones yet.
Click to expand...
Click to collapse
You are correct but I am still very pleased. BTW, do you know of a wifi tether hack for a build ending in NC5?
aksaunders said:
You are correct but I am still very pleased. BTW, do you know of a wifi tether hack for a build ending in NC5?
Click to expand...
Click to collapse
Go into the Android Dev section for the Note 3. Freeza, Sac23, Joshbeach all have NC5 Roms that have the wifi hack built in. Also, Josh has a Mod section and has the hotspot hack itself.
Nickitt said:
Go into the Android Dev section for the Note 3. Freeza, Sac23, Joshbeach all have NC5 Roms that have the wifi hack built in. Also, Josh has a Mod section and has the hotspot hack itself.
Click to expand...
Click to collapse
But have to be on a deodexed ROM ... there is not one for odexed just stock ROM
Sent from my SM-N900P using Xparent BlueTapatalk 2
Related
** Thank you to JGeigerM, hexitnow, and joderme for the solution.
** Solver was paid.
** I leave a condensed version in case someone is frantically googling like I was.
[Background]
I downloaded VRUAME7 for my Galaxy S4.
I then tried to flash Blue Toggles apk.
I then began getting the message "Unfortunately, System UI has stopped".
I decided to use Odin to attempt to flash MDK firmware, which FAILED as you will see below:
**ODIN LOG**:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VRUAMDK_NoWipe.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NON-HLOS.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
**PHONE LOG**
START [224, 1448]
SW REV. CHECK FAIL : fused : 3, Binary : 1
**SOLUTION**:
(1) Verizon GS4 I545 VRUAME7 Stock Image = http://invisiblek.org/sch-i545/SCH-I...3crny1_fac.zip
(2) Unzip that file when downloaded
(3) Run Odin 3.07 (latest as of posting) as administrator
(4) Select .MD5 file that you unzipped as a PDA
(5) Hit Start once it loads
Here is the link to the stock ME7 image... http://forum.xda-developers.com/showthread.php?t=2357235
Try this one and see if it works.
You were trying to flash the mdk firmware which you cant flash back to once on me7. the stock me7 file is at this link
http://forum.xda-developers.com/showthread.php?p=43420116
The mods for me7 need to be made for it most of the time I believe framework is quite a bit different from mdk which is why you got yourself a soft brick. Im gonna put this out there just in case yoh were looking into it but youre unable to flash a custom recovery on me7 or else youll get another soft brick of sorts. There are people working on it tho.
Sent from my SCH-I545 using Tapatalk 2
EDIT: Solved
I'm glad I could help. XDA forum stalking has become my new habit so I saw it when you posted :good:
EDIT: Solved
Yeah that was a bad download. Another user posted the same thing. After he redownloaded it he was good to go.
Sent from my SCH-I545 using Tapatalk 2
It lives!
Thank you all so much again.
A mod can switch this to solved.
I'm trying to contact JGeigerM for payment.
Sorry, hexitnow, you were 2 minutes later than his original link.
m0bstr said:
It lives!
Thank you all so much again.
A mod can switch this to solved.
I'm trying to contact JGeigerM for payment.
Sorry, hexitnow, you were 2 minutes later than his original link.
Click to expand...
Click to collapse
I wouldnt of accepted anything for payment so im not worried bout it. You can edit your post and add solved to the title. Glad you got it going though.
Sent from my SCH-I545 using Tapatalk 2
It wasn't much help to send you just a link to an image.
Sent from my SCH-I535 using Tapatalk 4
I got my s4 (i545) from verizon about 1 1/2 months ago and I did receive the lastest ota when i got my phone. Once i came across a new method to install custom roms using safestrapi believe i used the me7 version of hyperdrive. Once I installed the custom rom, everything was fine and dandy. I rebooted and got a message from verizon saying you been messing with your phone. So than i researched how to fix a soft brick and came across this site to use
rom - SCH-I545_VZW_1_20130613171315_24s13crny1_fac.zip
rom2 - SCH-I545_MDK_562219_Stock_Restore
Note: It appears the site i used to install safestrap didnt include FLASH HASCODES FIX OVER TOP OF ROM.
Odin failed:
<ID:0/003> Added!!
<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> 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> 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> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> persdata.img.ext4
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
I am trying to find a stock rom that will let me re-flash. I hope someone has came across this issue. Any help would be appreciated.
Thanks
You need to find the me7 Odin restore file. You can't downgrade from me7 to mdk that is the reason safe strap had to be created
Sent from my SCH-I545 using Tapatalk 4
I am just having problems finding the stock rom for my phone.. since you cant install a rom that is earlier than the date of your ota version
vital01 said:
I am just having problems finding the stock rom for my phone.. since you cant install a rom that is earlier than the date of your ota version
Click to expand...
Click to collapse
Sammobile.com
my version is not in the list. sch-i545 thanks
vital01 said:
my version is not in the list. sch-i545 thanks
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/showthread.php?p=43420116
I have done that method.. btw im on mac using fusion to use windows 7. Odin still fails.. I dont know what else to do.. I guess i have a paperweight.
vital01 said:
I have done that method.. btw im on mac using fusion to use windows 7. Odin still fails.. I dont know what else to do.. I guess i have a paperweight.
Click to expand...
Click to collapse
Your running out in PDA slot in Odin and only have auto-reboot checked? Your Odin print out looks like it's trying. What version of odin are you using? I've had best luck with 1.85
Yes that is correct.. auto-reboot is the only one checked.. and i have used 1.85 and the 3+ versions
vital01 said:
Yes that is correct.. auto-reboot is the only one checked.. and i have used 1.85 and the 3+ versions
Click to expand...
Click to collapse
Have you been able to fix this? I have the same setup as you: VZW GS4, Odin fails in the same spot, I am using a Mac and Fusion 7 with Win7 VM.
Thanks.
*UPDATE: (Oct 21)*
I was able to successfully flash/recover stock ME7 using ODIN on my Win7 laptop, instead of connecting to Win7 in a VM on my Mac.
Thanks for the reply I ended up sending it to a service on ebay
wryun said:
Have you been able to fix this? I have the same setup as you: VZW GS4, Odin fails in the same spot, I am using a Mac and Fusion 7 with Win7 VM.
Thanks.
*UPDATE: (Oct 21)*
I was able to successfully flash/recover stock ME7 using ODIN on my Win7 laptop, instead of connecting to Win7 in a VM on my Mac.
Click to expand...
Click to collapse
For a Mac, you should be using Heimdall, which is a OSX native application that does what Odin does on Windows.
Update: Root has been achieved, and Safestrap works - See here
This is a new update for SCH-1545 taking users to VRUDMI1. This is the stock factory image, taken straight from Kies. At this point only download for research or curiosity because this build has not been tested again for root access and you very well may loose both root and custom recovery by flashing this. So far I see a lot of Knox related stuff. Also, If you need to go back to stock for whatever reason I suggest using the VRUAME7 (or MDK) factory image instead. Both VRUAME7 and VRUAMDK stock Odin tars contained 14 partitions over which they would write over. However, in the newest build VRUDMI1, only 13 partitions are wrote over because it doesn’t contain a persdata.img.ext4.
Changes so far in this build:
1. VRUMDI1 DOES NOT WIPE THE PERSDATA PARTITION! (persdata.img.ext4)
2. ROOT METHOD FOR VRUAME7 NO LONGER WORKS ON THIS BUILD! - NEW ROOT METHOD here
3. New system apps are included, read more here
Nonetheless, if you want to rose root and recovery (maybe forever) then,
1. Unzip the file and you should have a tar.md5
2. Select the tar.md5 in Odin under PDA and keep Odin's default settings
3. Click start and wait for it to say pass
File: SCH-I545_VZW_3_20131015092810_3pa3eg8qji.zip
MD5:8335da10191b0e2ce84a701b8e5249b4
Mirrors:
https://db.tt/Q6EVK0bY
https://db.tt/qZupCjFT
https://db.tt/XwsbAHdL
http://www.androidfilehost.com/?fid=23159073880936987
Your Dropbox link has been disabled.
Sent from my SPH-L720 using Tapatalk
ChadH42 said:
Your Dropbox link has been disabled.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I'm putting a mirror up soon.
I would guess that whatever exploit is used in ME7 to get root is fixed in this build.
*Fingers crossed*
Another mirror :good:
http://www.androidfilehost.com/?fid=23159073880936987
toadlife said:
I would guess that whatever exploit is used in ME7 to get root is fixed in this build.
*Fingers crossed*
Click to expand...
Click to collapse
why? That would totally suck lol
Sent from my SCH-I545 using XDA Premium HD app
elliwigy said:
why? That would totally suck lol
Sent from my SCH-I545 using XDA Premium HD app
Click to expand...
Click to collapse
I meant fingers crossed that it isn't.
Kinda sad that we have to hope our devices are vulnerable.
Has anyone odined this over a phone with dmi1 already on it? I remeber folks with the international version having issues tripping the knox counter.
Sent from my SCH-I545 using xda app-developers app
Has anyone attempted flashing the radios only? I'm happy on CM 10.2, I just want the improved radios in the new TW build.
Edit: I found a thread. Sorry for taking up your precious space.
Can I use this on a currently bricked device or do I have to use the stock version?
sethjk said:
Can I use this on a currently bricked device or do I have to use the stock version?
Click to expand...
Click to collapse
This is the stock version.
I flashed mk2 with odin full wipe today, since I545VRUDMI1 was rooted I decided to try and flash this odin image to check out the new build and then root it... but it keeps failing. I have checked and verified the crc values, they all check out. Any ideas? Also has anyone actually gotten this from OTA? When I flash back to bone stock and run the OTA's untill says I have the latest, I only get up to MK2. Here is Odin log:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUDMI1_I545VZWDMI1_I545VRUDMI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
xxxtncxxx said:
I flashed mk2 with odin full wipe today, since I545VRUDMI1 was rooted I decided to try and flash this odin image to check out the new build and then root it... but it keeps failing. I have checked and verified the crc values, they all check out. Any ideas? Also has anyone actually gotten this from OTA? When I flash back to bone stock and run the OTA's untill says I have the latest, I only get up to MK2. Here is Odin log:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUDMI1_I545VZWDMI1_I545VRUDMI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
This is from last year man.
Sent from my SCH-I545 using xda app-developers app
xxxtncxxx said:
I flashed mk2 with odin full wipe today, since I545VRUDMI1 was rooted I decided to try and flash this odin image to check out the new build and then root it... but it keeps failing. I have checked and verified the crc values, they all check out. Any ideas? Also has anyone actually gotten this from OTA? When I flash back to bone stock and run the OTA's untill says I have the latest, I only get up to MK2
Click to expand...
Click to collapse
Once you are on MK2, you can't flash an older release. MI1 is older than MK2, so you're trying to flash backwards.
What are you trying to accomplish? Since you're on MK2, root it, install Safestrap, then flash a custom ROM.
I suggest you read the following sticky thread: http://forum.xda-developers.com/showthread.php?t=2606501
And this thread as well http://forum.xda-developers.com/showthread.php?t=2578569
Flashing without understanding what you're doing will quickly brick your phone if you're not careful.
Good god I'm ashamed... I thought it was a newer build LOL explains alot!
Sent from my SCH-I545 using Tapatalk
Believe it or not I know what I am doing, I miss read something and thought I1 was above K2, and thinking that I couldn't understand what was happening. It's very hard to really brick an S4 if u are moderately educated in the subject you can get out of most situations. Even doing numbskull things like what I did. Was a long bad day of work, working on old out of date servers for 12 hrs can really melt your brain.
Sent from my SCH-I545 using Tapatalk
Hey guys, I need some help. I was switching roms and I guess i must have deleted my storage. So I had no rom to install and no backup. I tried to odin back to stock and it failed. Now my phone will only boot to odin mode but it says firmware upgrade encountered a problem. I searched and searched for answers and tried many things but no solutions seem to work. I have tried one click MJ4 full restore, and one click NAB full restore and neither work. they fail. So what can I try next? I have been working on this for hours and I have to go to work in 5 hours and need my phone. Please help.
drunkensunday said:
Hey guys, I need some help. I was switching roms and I guess i must have deleted my storage. So I had no rom to install and no backup. I tried to odin back to stock and it failed. Now my phone will only boot to odin mode but it says firmware upgrade encountered a problem. I searched and searched for answers and tried many things but no solutions seem to work. I have tried one click MJ4 full restore, and one click NAB full restore and neither work. they fail. So what can I try next? I have been working on this for hours and I have to go to work in 5 hours and need my phone. Please help.
Click to expand...
Click to collapse
What was on your phone prior to this happening?
We need the back story up to when you started flashing 2 separate operating systems onto your device (JellyBean, MJ4, TouchWiz KitKat, NAB).
You mention that you were switching roms...what rom were you on, and to what rom did you try to flash?
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
What was on your phone prior to this happening?
We need the back story up to when you started flashing 2 separate operating systems onto your device (JellyBean, MJ4, TouchWiz KitKat, NAB).
You mention that you were switching roms...what rom were you on, and to what rom did you try to flash?
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I was on this rom : http://forum.xda-developers.com/showthread.php?t=2567499 and was trying to switch to this rom:
http://forum.xda-developers.com/showthread.php?t=2696396
However I never even started the write because I deleted everything on accident prior to trying to write the rom. I was S-OFF and rooted and I believe I was on 4.3.
Oh then the first thing I did was try to odin this file: N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5
That failed, then I tried the 2 previously mentioned one click odin stocks.
Oh and I was on TWRP 2.6.1 but now I have no recovery.
drunkensunday said:
Oh and I was on TWRP 2.6.1 but now I have no recovery.
Click to expand...
Click to collapse
Have you tried odin twrp to your phone maybe it doesn't like you not having any recovery?
Cheryl
drunkensunday said:
I was on this rom : http://forum.xda-developers.com/showthread.php?t=2567499 and was trying to switch to this rom:
http://forum.xda-developers.com/showthread.php?t=2696396
However I never even started the write because I deleted everything on accident prior to trying to write the rom. I was S-OFF and rooted and I believe I was on 4.3.
Click to expand...
Click to collapse
The MJ4 tar would've worked had you flashed it (you were on MJ4, JellyBean, but on a prerooted rom).
Having failed at MJ4, going with the NAB and NC5 (both KitKat), may have sent your system into a nosedive of confusion.
Tell me if you can get into download mode at all home + power + volume down).
Your version of TWRP is old, but that has nothing to do with this. You need to put your phone back to stock, then upgrade if you want to flash a KitKat rom.
The MJ4 tar file will put stock everything back on your phone, even recovery, so your TWRP will be gone...but you can get it back.
Let me know if you can get into download mode, and we can take it from there.
Sent from my SM-N900P using Xparent BlueTapatalk 2
I can get in to download mode, but it has a triangle with exclamation mak and it says "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again. However the phone still comunicates with oden. The writting process starts but fails every time. I did the 1 click mj4 and it fails as well.
And I don't need to hold buttons to get to download, it's the only screen the phone goes to no matter what.
drunkensunday said:
I can get in to download mode, but it has a triangle with exclamation mak and it says "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again. However the phone still comunicates with oden. The writting process starts but fails every time. I did the 1 click mj4 and it fails as well.
And I don't need to hold buttons to get to download, it's the only screen the phone goes to no matter what.
Click to expand...
Click to collapse
Please quote me when responding, if you don't mind. It let's me know that you've posted something.
As long as you can get into download mode, you can do something, hopefully.
A bricked device doesn't get into anything, won't even power into that screen. It's called brick for that reason.
What happens when you do volume up + power + home? Nothing, stock recovery, download mode, etc? Also, power down completely, and remove your SD card.
You can try...
1. Flashing the tar file via PC Odin in lieu of the one-click package (perhaps at this point not a possibility given that you've tried to flash the latest NC5 tar
2. Taking into Sprint where a root tolerant tech is available, and have them put the latest firmware on it for you, over-the-wire style (speak little, play clueless, Google around before going into the brick-and-mortar location
3. Flashing the NAB or NC5 tar, same way (you already have tried one or both of these I believe
Ultimately, option 2 may be your best hope.
Good luck!
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
Please quote me when responding, if you don't mind. It let's me know that you've posted something.
As long as you can get into download mode, you can do something, hopefully.
A bricked device doesn't get into anything, won't even power into that screen. It's called brick for that reason.
What happens when you do volume up + power + home? Nothing, stock recovery, download mode, etc? Also, power down completely, and remove your SD card.
You can try...
1. Flashing the tar file via PC Odin in lieu of the one-click package (perhaps at this point not a possibility given that you've tried to flash the latest NC5 tar
2. Taking into Sprint where a root tolerant tech is available, and have them put the latest firmware on it for you, over-the-wire style (speak little, play clueless, Google around before going into the brick-and-mortar location
3. Flashing the NAB or NC5 tar, same way (you already have tried one or both of these I believe
Ultimately, option 2 may be your best hope.
Good luck!
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Here's the Odin log when I try flashing:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
drunkensunday said:
Here's the Odin log when I try flashing:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
remove battery from phone..... now with battery removed reinstall battery. boot to recovery by holding volume+ and power button simultaneously.
if you can access any type of stock recovery do a full wipe from it. not if you cant try rebooting computer . try usb in a different port. sometimes its something so simple. could even be a cord issue. do you have another cord to try? any micro usb will work.
kaos420 said:
remove battery from phone..... now with battery removed reinstall battery. boot to recovery by holding volume+ and power button simultaneously.
if you can access any type of stock recovery do a full wipe from it. not if you cant try rebooting computer . try usb in a different port. sometimes its something so simple. could even be a cord issue. do you have another cord to try? any micro usb will work.
Click to expand...
Click to collapse
I do not have any recovery at all. I tried 2 cords, I'll try the reboot of computer now. Does it matter I'm on a Mac using vmware for win 7?
drunkensunday said:
I do not have any recovery at all. I tried 2 cords, I'll try the reboot of computer now. Does it matter I'm on a Mac using vmware for win 7?
Click to expand...
Click to collapse
Are you using the USB 3.0 cord ... That's the only one I use for Odin
Sent from my SM-N900P using Xparent BlueTapatalk 2
Epix4G said:
Are you using the USB 3.0 cord ... That's the only one I use for Odin
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Yes, but in a usb 2.0 port if it matters....
Reboot and new port gave me a slightly different Odin log but still 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)
drunkensunday said:
Reboot and new port gave me a slightly different Odin log but still 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)
Click to expand...
Click to collapse
you have all correct files? your sd card is out? if not remove sd card and try. also mac could be a issue idk im a windows guy. but http://forum.xda-developers.com/showthread.php?t=2369125 this thread shows how to unbrick you would need to run Linux virtual though.
kaos420 said:
you have all correct files? your sd card is out? if not remove sd card and try. also mac could be a issue idk im a windows guy. but http://forum.xda-developers.com/showthread.php?t=2369125 this thread shows how to unbrick you would need to run Linux virtual though.
Click to expand...
Click to collapse
I think either trying it from a Windows PC (shouldn't matter, but why not try) or carefully selecting a Sprint store (root friendly tech, knows what he or she is doing) for an over-the-wire update, are worth a shot.
Sent from my SM-N900P using Xparent BlueTapatalk 2
drunkensunday said:
Reboot and new port gave me a slightly different Odin log but still 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)
Click to expand...
Click to collapse
It is a possibility that you had a bad download and also are you using the odin you from chain fire when you rooted? I had the same problem last month. I spent 5 hours trying to figure it out. Turns out I just had a bad download.
Sent from my SM-N900P using xda app-developers app
Just got back from Sprint Store. They said my warrenty is void and there is nothing they can do. I guess I will redownload and try on a pc. I'll be back.... ugh.
drunkensunday said:
Just got back from Sprint Store. They said my warrenty is void and there is nothing they can do. I guess I will redownload and try on a pc. I'll be back.... ugh.
Click to expand...
Click to collapse
did you have tep? did you tell them what you tried?
Ok, so here is the deal.
I have the Samsung Galaxy Mega 6.3 with U.S Cellular (SCH-R960) and I have run into some problems. What I did was try to root. Flashed CWM Recovery in Odin and when I tried to boot back up again, I was stuck in bootloop. So I tried to revert back to stock by flashing the stock firmware for my phone in Odin, the problem is, everytime I try and do that, I get this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9200XXUCNC2_I9200OLBCNC1_I9200XXUCNC2_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> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Also, on the phone screen it says
SECURE CHECK FAIL: sbl1
I can boot into recovery and also into download mode. Although if I try to just boot the phone normal it just stays on the Samsung Galaxy Mega logo screen. I have tried sideloading a .zip and that also fails.
Does anyone have any idea of how to fix this? Any help would be greatly appreciated.
Deleted cause by my noob. Sorry
Sent from my Nexus 7 using Tapatalk
yusopa said:
Why you dont try go to galaxy mega thread to get help. I think you face something big what we call knox problem. You cant root your device before you know your device surely. Samsung provide new bootloader with knox right now.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thought this was the Mega forum? And yes I know about knox I bricked an S3 because of it but I didn't think it was added until 4.3?
the firmware you are trying to flash (which is i9200) is not for your us cellular version of mega (which is r960).
find the correct one then proceed.
yusopa said:
Why you dont try go to galaxy mega thread to get help. I think you face something big what we call knox problem. You cant root your device before you know your device surely. Samsung provide new bootloader with knox right now.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
jk0l said:
the firmware you are trying to flash (which is i9200) is not for your us cellular version of mega (which is r960).
find the correct one then proceed.
Click to expand...
Click to collapse
I'm not using it as a phone anymore, just kinda as a tablet. So does it matter that it isnt the r960 firmware?
vBIGLEWISv said:
Ok, so here is the deal.
I have the Samsung Galaxy Mega 6.3 with U.S Cellular (SCH-R960) and I have run into some problems. What I did was try to root. Flashed CWM Recovery in Odin and when I tried to boot back up again, I was stuck in bootloop. So I tried to revert back to stock by flashing the stock firmware for my phone in Odin, the problem is, everytime I try and do that, I get this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9200XXUCNC2_I9200OLBCNC1_I9200XXUCNC2_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> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Also, on the phone screen it says
SECURE CHECK FAIL: sbl1
I can boot into recovery and also into download mode. Although if I try to just boot the phone normal it just stays on the Samsung Galaxy Mega logo screen. I have tried sideloading a .zip and that also fails.
Does anyone have any idea of how to fix this? Any help would be greatly appreciated.
Click to expand...
Click to collapse
Try with samsung kies to revert back to stock..See it helps or not.
Carnage said:
Try with samsung kies to revert back to stock..See it helps or not.
Click to expand...
Click to collapse
Kies doesn't work either. It wont connect and when I try manually it wont accept my S/N. I'm stuck here I'm not sure what to do.
I am also found ths problem. Kies also not working... Bad experience..
Bro grab the right firmware for the phone just cause its not gonna be used as a phone does not mean that you don't have to have the correct **** for the phone lol
Sent from my sgh-i527 with xda premium 4
HOPSIN-KAT KEYBOARDS IS NOW UP AND RUNNING CHECK EM OUT OVER AT THE CANDY SHOP!
http://forum.xda-developers.com/showthread.php?p=52221912
vBIGLEWISv said:
Kies doesn't work either. It wont connect and when I try manually it wont accept my S/N. I'm stuck here I'm not sure what to do.
Click to expand...
Click to collapse
Are you really cannot boot into download mode?..vol down+power button..try power on the device,remove the battery,put it back again,and quickly press the download mode combination keys (vol down+power button) see it boots to download mode or not..if its boot, grab your latest firmware and flash it via odin. About the kies,try to uninstall and download the latest version of kies solve it..
EDIT:I have search your firmware and don't find any link.you have to wait until the firmware for your specific model number released by Samsung.
hopsin4444 said:
Bro grab the right firmware for the phone just cause its not gonna be used as a phone does not mean that you don't have to have the correct **** for the phone lol
Sent from my sgh-i527 with xda premium 4
HOPSIN-KAT KEYBOARDS IS NOW UP AND RUNNING CHECK EM OUT OVER AT THE CANDY SHOP!
http://forum.xda-developers.com/showthread.php?p=52221912
Click to expand...
Click to collapse
Thats the problem the stock firmware doesnt exist for my phone or at least I cant find it.
well then, thats unfortunate. im sorry.
so its certain that theres no way for you to go back to stock.
edit:
actually, try to wipe data and cache in recovery then reboot.
if it still bootloops, then I recommend you patiently wait until the stock firmware for your phone is released.