Related
I installed CWM touch, and superuser zip folder on my Galaxy note (att)
So I read a tut that said to wipe everything so I did on recovery mode, booted it up, worked good, went back because superuser didnt work right. I installed 3-4 times before it said success, now its goes to a crisp samsung logo, then goes blurry and stops.....
Stupid noob mistake I didnt backup anything. Figured it was simple as jailbreaking an iphone (which you cant mess up on, plug in, hit button, done)
I been trying it all but just cant get it to work.
If your phone still boots up
youre not bricked...
Odin back to a stock firmware (GB or ICS)
and start again
jayRokk said:
If youre phone still boots up
youre not bricked...
Odin back to a stock firmware (GB or ICS)
and start again
Click to expand...
Click to collapse
+1.
And if you can't find how to do that, you need to read more before flashing
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
It boots to the samsung logo, but not lock screen. And I'm phoneless now Lol.
Since I was just updated to ICS (att) and did CWM/superuser, would I just have to use odin>PDA with a tar file?
if so which file? I tried that but no luck.
welchertc said:
+1.
And if you can't find how to do that, you need to read more before flashing
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
I been reading alot but seems like there is a hundred different explanations or ways to do it, and hard to find the right way?
liftedzuki said:
Since I was just updated to ICS (att) and did CWM/superuser, would I just have to use odin>PDA with a tar file?
if so which file? I tried that but no luck.
Click to expand...
Click to collapse
Yes its a .tar file
And search for it buddy there is a whole thread on official ICS and with it the CWM file and SU file to get you going
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
http://forum.xda-developers.com/showthread.php?t=1566976
Tried this tar, and it
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> FixRecovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
liftedzuki said:
http://forum.xda-developers.com/showthread.php?t=1566976
Tried this tar, and it
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> FixRecovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You need to stop flashing before you mess up your phone
Stop and read
Why are you flashing that?!?!?!
You have an NOTE
Really stop and read read read
I'm surprised you haven't bricked it yet
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
jayRokk said:
You need to stop flashing before you mess up your phone
Stop and read
Why are you flashing that?!?!?!
You have an NOTE
Really stop and read read read
I'm surprised you haven't bricked it yet
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
:silly: I got it from a link in this note section, I should have seen that though.
So if I flash it, does it flash over the other flash? or does it add to it.
I'll continue readin.
Not all Samsung's are the same. You should only be getting tar files from your specific section. Keep in mind you need to match the model number
Sent from my SPH-L710 using Tapatalk 2
I would suggest going here and flashing one of these one clicks in Odin:
http://forum.xda-developers.com/showthread.php?t=1647756
Sent from my SPH-L710 using Tapatalk 2
And if I'm not mistaken you want the first link. I don't have a note so maybe someone here can chime in.
Sent from my SPH-L710 using Tapatalk 2
That link worked good. Thanks so much to everyone, I about had a heartache as I got my phone like 3 months ago, and just got ICS on it.
This time I'm gonna read alot more before I try it again.
Good idea. Glad it worked. If ya ever have any questions in the future , don't hesitate to ask BEFORE flashing.
Sent from my SPH-L710 using Tapatalk 2
Definitely not gonna be doing it til next weekend. I didnt plan on doing it today just was messin with my phone since galaxy S3 is out, and wanting to make my phone a little cooler, and did it before I had lots of research under my belt. :silly:
Haha it happens. Just be glad ya didn't end up with a huge note shaped paperweight
Sent from my SPH-L710 using Tapatalk 2
liftedzuki said:
Definitely not gonna be doing it til next weekend. I didnt plan on doing it today just was messin with my phone since galaxy S3 is out, and wanting to make my phone a little cooler, and did it before I had lots of research under my belt. :silly:
Click to expand...
Click to collapse
OP if your good to go, can you put Solved in your title....
thank you sir
Dear Friends
I HAVE MESS-UP WITH MY i9300!!!!
The incident is I was using custom rom, and installed some stupid app called "Adblock" or something,
and then, my phone just keep went-off for about 8-10 times a day. So then, I decided to reflash
custom rom by CWM, and after I pressed install in Aroma Installer, it just kick me out all of sudden, and
then, I couldn't get back to CWM anymore, so I decided to flash some stock rom by odin, but what
had happen was it starts until "Nand write start" and stacked for a while, and then just FAIL me.
On the net, I found that Checkrom Resurrection V4 could rescue softbrick i9300, I tried, but
no luck either. Finally, just now, I tried a 3 files stock rom with pit, and it came out as:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXALE8_554452_REV00_user_low_ship.tar.md 5 is valid.
<OSM> MODEM_I9300XXLE8_REV02_REV04_CL1145430.tar.md5 is valid.
<OSM> CSC_OJV_I9300OJVALE7_CL547448_REV00_user_low_noshi p.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
What I have done:
1. reflash custom rom by CWM
2. 3 wipes - (but I am no longer to get back to CWM)
3. flash stock rom - hong kong combo firmware @ Samfirmware - by Odin
4. flash Checkrom Resurrection V4 by Odin
5. flash stock rom - 3 files firmware + pit - by Odin
6. changed usb port
7. changed PC
8. uninstall all applications relative to Kies
have you guys got any idea what can I do? I am thinking to mess-up the phone even badly (till it couldn't switch on), so that I can take it to Samsung Service Center for warranty replacement, but have you got ANY method I can do that to mess it up? Or anything I can over-come from the soft (or hard) brick. PLEASE Give me some help guys. I am very struggle.
Wrong thread.. Needs to be in Q&A
Try a fully stock rom with Odin 1.85
Sent from my GT-I9300 using xda app-developers app
Kingybear said:
Try a fully stock rom with Odin 1.85
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Thanks Mate, but no luck
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXALE8_554452_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXLE8_REV02_REV04_CL1145430.tar.md5 is valid.
<OSM> CSC_OJV_I9300OJVALE7_CL547448_REV00_user_low_noship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Set PIT file..
<ID:0/009> DO NOT TURN OFF TARGET!!
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> sboot.bin
<ID:0/009> NAND Write Start!!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
NatTheCat said:
Wrong thread.. Needs to be in Q&A[/QUOT
I put it on Q&A already, but just wanted to have more people can help, so I put it on here. sorry for any disturb.
Click to expand...
Click to collapse
The fact that you want more people helping you doesnt mean that you can do what you want, wrong section.
By the way, it seems that your s3 is bricked pal.
Sent from my GT-I9300 using Tapatalk
anyone can tell me how to delete the thread? Thanks
aguerito said:
The fact that you want more people helping you doesnt mean that you can do what you want, wrong section.
By the way, it seems that your s3 is bricked pal.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
show the poor guy some love dude, your comments are abrasive he only wants help for his expensive phone sheesh
---------- Post added at 10:03 AM ---------- Previous post was at 09:59 AM ----------
I wouldnt panic yet they say its very hard to brick an S3?
check around and see what you can find out
kk12175 said:
Thanks Mate, but no luck
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXALE8_554452_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXLE8_REV02_REV04_CL1145430.tar.md5 is valid.
<OSM> CSC_OJV_I9300OJVALE7_CL547448_REV00_user_low_noship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Set PIT file..
<ID:0/009> DO NOT TURN OFF TARGET!!
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> sboot.bin
<ID:0/009> NAND Write Start!!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I think it's rom problems dude... I never encounter any problems for adblock app... Which rom did u flashed
Sent from my GT-I9300 using xda premium
jothi2lingam said:
I think it's rom problems dude... I never encounter any problems for adblock app... Which rom did u flashed
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
i was using Omega since v.9 until v33.2 at the last minute. and I found a video in youtube to resurrect my s3 by flashing Checkrom v4:
http://www.youtube.com/watch?v=ZNaQfdOi56E
tried it as well, but it seems doesn't work as it kept rebooting / hanging at the Galaxy S3 logo. And I tried to flashed some stock rom (combo file) from Samfirmware, no luck neither. Tried to flash some stock rom (3 files + pit) HK base rom. Same happened. Fail after Nand Write Start.:silly:
and now, couldn't get into CWM neither.
jothi2lingam said:
I think it's rom problems dude... I never encounter any problems for adblock app... Which rom did u flashed
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Been using adblock for a while myself and never had a hiccup .. excellent app..
Probably mother board died. Same problem with my sister S3. Take to Samsung and use the warranty. :banghead:
Sent from my GT-I9300 using xda premium
johnkhor123 said:
Probably mother board died. Same problem with my sister S3. Take to Samsung and use the warranty. :banghead:
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I had flashed custom rom before, do you think I can still use the warranty? If yes, definitely going.
kk12175 said:
Dear Friends
I HAVE MESS-UP WITH MY i9300!!!!
The incident is I was using custom rom, and installed some stupid app called "Adblock" or something,
and then, my phone just keep went-off for about 8-10 times a day. So then, I decided to reflash
custom rom by CWM, and after I pressed install in Aroma Installer, it just kick me out all of sudden, and
then, I couldn't get back to CWM anymore, so I decided to flash some stock rom by odin, but what
had happen was it starts until "Nand write start" and stacked for a while, and then just FAIL me.
On the net, I found that Checkrom Resurrection V4 could rescue softbrick i9300, I tried, but
no luck either. Finally, just now, I tried a 3 files stock rom with pit, and it came out as:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXALE8_554452_REV00_user_low_ship.tar.md 5 is valid.
<OSM> MODEM_I9300XXLE8_REV02_REV04_CL1145430.tar.md5 is valid.
<OSM> CSC_OJV_I9300OJVALE7_CL547448_REV00_user_low_noshi p.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
What I have done:
1. reflash custom rom by CWM
2. 3 wipes - (but I am no longer to get back to CWM)
3. flash stock rom - hong kong combo firmware @ Samfirmware - by Odin
4. flash Checkrom Resurrection V4 by Odin
5. flash stock rom - 3 files firmware + pit - by Odin
6. changed usb port
7. changed PC
8. uninstall all applications relative to Kies
have you guys got any idea what can I do? I am thinking to mess-up the phone even badly (till it couldn't switch on), so that I can take it to Samsung Service Center for warranty replacement, but have you got ANY method I can do that to mess it up? Or anything I can over-come from the soft (or hard) brick. PLEASE Give me some help guys. I am very struggle.
Click to expand...
Click to collapse
Try TURN OFF antivirus, update Kies, Try on other OS.
Because I had the same problem with own S3.
Windows 8, AVG IS 2013, Odin 3.07,3.04.
Everytime after few second Odin stop working and show FAIL "Complete(Write) operation failed."
But on Windows 7, updated Kies to 2.5, turned off AVG, Odin 3.07, fresh downloaded rom ELK4, Galaxy S3 slowly but finished NAND write
and now I am happy againg
johnkhor123 said:
Probably mother board died. Same problem with my sister S3. Take to Samsung and use the warranty. :banghead:
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Ya i think so,,Same incident for previously after flashed one of the rom from this thread i went to sleep..The phone was reboot itself (stuck in bootloop) till i found at morning, my phone fuc**ing hot stucked in Samsung Galaxy SIII. After tried flashed using odin & using cwm not worked because my phone keep on rebooting. Once send to sammy centre i said that i put in charge, once wakeup in morning my phone keep on rebooting & so hot. So after one week they replace me new board for my s3 even they can see my cwm. I tried to delete cwm but cant. Thank god atlast they replace my s3. so only way is send to samsung centre. I face exactly same issue previously as you facing now
KKTHX said:
Try TURN OFF antivirus, update Kies, Try on other OS.
Because I had the same problem with own S3.
Windows 8, AVG IS 2013, Odin 3.07,3.04.
Everytime after few second Odin stop working and show FAIL "Complete(Write) operation failed."
But on Windows 7, updated Kies to 2.5, turned off AVG, Odin 3.07, fresh downloaded rom ELK4, Galaxy S3 slowly but finished NAND write
and now I am happy againg
Click to expand...
Click to collapse
sounds good. give it a try .. thanks MATE
kk12175 said:
anyone can tell me how to delete the thread? Thanks
Click to expand...
Click to collapse
Thread closed.
So after attempting to do the new rooting method, my computer lost power halfway through and now is stuck on the kies recovery screen. I tried to flash back to stock via Odin, but it always failed. Any advice? (I'm assuming that id need to flash a new bootloader, but I cant find a stock one that would work with Odin. any help would be appreciated
mattman3512 said:
So after attempting to do the new rooting method, my computer lost power halfway through and now is stuck on the kies recovery screen. I tried to flash back to stock via Odin, but it always failed. Any advice? (I'm assuming that id need to flash a new bootloader, but I cant find a stock one that would work with Odin. any help would be appreciated
Click to expand...
Click to collapse
refer to section 1b of my guide.
droidstyle said:
refer to section 1b of my guide.
Click to expand...
Click to collapse
I just tried that, with the pit in the pit spot and the other download in the PDA spot. I got this message
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> modem.bin
<ID:0/005> param.bin
<ID:0/005> recovery.img
<ID:0/005> sboot.bin
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Use the "alternate restore" download from here
http://forum.xda-developers.com/showthread.php?p=35265728
Sent from the dark on a Note 2
if you pay attention to the guide you would of seen to use the alternate restore link if your on the latest L4 ota.
tniewo was
droidstyle said:
if you pay attention to the guide you would of seen to use the alternate restore link if your on the latest L4 ota.
Click to expand...
Click to collapse
when I download the alternate, both of them, they don't show up in Odin... Help? tried the forum and couldn't find the answer
kintwofan said:
Use the "alternate restore" download from here
http://forum.xda-developers.com/showthread.php?p=35265728
Sent from the dark on a Note 2
Click to expand...
Click to collapse
Damn, my man. How many times a day do you think you say "alternate restore "? Lol. I just saw the other thread where dude didn't know what you meant. Thought it was his "alternative option".
You're nice. I couldn't do it. Lol.
Sent from my SCH-I605 using Tapatalk 2
1ManWolfePack said:
Damn, my man. How many times a day do you think you say "alternate restore "? Lol. I just saw the other thread where dude didn't know what you meant. Thought it was his "alternative option".
You're nice. I couldn't do it. Lol.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Ya in a pretty patient guy. Eventually I'll get tired of it. Just like when cm10.1 dropped for s3 and every body was roaming.
Sent from the dark on a Note 2
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?