Android Rooting Issue [Resolved] - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

[Issues Resolved]

Thank you for explaining all you're issues
http://forum.xda-developers.com/showthread.php?t=2258628
this should fix you up, take a deep breath and relax, this is NOTHING
you need to download Odin 3.07 and the MDL firmware from samsung updates or sammobile
Open odin 3.07
check off pda and press the button to insert the .tar you just downloaded (dont touch anything else)
flash
reboot and keep you're phone off WIFI so you don't OTA on the stock ROM
hope this helps my friend, while you're firmware downloads I suggest studying a bit more and learning what you can

Thank you, in the future, would you recommend I use CASUAL or Motochopper? Also, should I install a recovery partition that factory touchwiz or a custom rom?

Danvdh said:
Thank you for explaining all you're issues
http://forum.xda-developers.com/showthread.php?t=2258628
this should fix you up, take a deep breath and relax, this is NOTHING
you need to download Odin 3.07 and the MDL firmware from samsung updates or sammobile
Open odin 3.07
check off pda and press the button to insert the .tar you just downloaded (dont touch anything else)
flash
reboot and keep you're phone off WIFI so you don't OTA on the stock ROM
hope this helps my friend, while you're firmware downloads I suggest studying a bit more and learning what you can
Click to expand...
Click to collapse
I got the following error in Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SGH-M919-UVUAMDB-k0nane.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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
It says "FAIL!" in a big red box instead of PASS! in a green box, what should I do?

I think the problem might have been that I downloaded the wrong firmware.
You said get the "MDL firmware from samsung updates or sammobile".
On the thread you linked to, it was the MDL firmware for an m1919 device and I have an i337 device.
Where can I find the i337 MDL firmware? What site do you mean when you say "samsung updates" or "sammobile"?
Thanks for your help, this is really confusing.

Rextober said:
I think the problem might have been that I downloaded the wrong firmware.
You said get the "MDL firmware from samsung updates or sammobile".
On the thread you linked to, it was the MDL firmware for an m1919 device and I have an i337 device.
Where can I find the i337 MDL firmware? What site do you mean when you say "samsung updates" or "sammobile"?
Thanks for your help, this is really confusing.
Click to expand...
Click to collapse
Here is a link for the I337 MDL Firmware.. You sure are lucky that you got the MDL..If you had got the new MF3, you couldn't flash custom roms without Safestrap.. Anyways, there is the link, hope it helps you.. After downloading it, unzip it and use the .tar file you see..
http://stockroms.net/file/GalaxyS4/SGH-I337/I337UCUAMDL_I337ATTAMDL_ATT.zip

nerdyblonde said:
Here is a link for the I337 MDL Firmware.. You sure are lucky that you got the MDL..If you had got the new MF3, you couldn't flash custom roms without Safestrap.. Anyways, there is the link, hope it helps you.. After downloading it, unzip it and use the .tar file you see..
http://stockroms.net/file/GalaxyS4/SGH-I337/I337UCUAMDL_I337ATTAMDL_ATT.zip
Click to expand...
Click to collapse
Thank you, right now when I turn on the phone it is stuck at the samsung galaxy s black screen and the only way I can turn it off is to remove the battery. If I use the instructions on this thread: http://forum.xda-developers.com/showthread.php?t=2258628, but using the file you mentioned with Odin, it should restore the phone? Does it remove TWRP too?

Rextober said:
Thank you, right now when I turn on the phone it is stuck at the samsung galaxy s black screen and the only way I can turn it off is to remove the battery. If I use the instructions on this thread: http://forum.xda-developers.com/showthread.php?t=2258628, but using the file you mentioned with Odin, it should restore the phone? Does it remove TWRP too?
Click to expand...
Click to collapse
If you just used odin, boot into recovery and do a factory reset. It should get you past a boot loop. If you use Odin it will remove twrp and put on the factory recovery.

jd1639 said:
If you just used odin, boot into recovery and do a factory reset. It should get you past a boot loop. If you use Odin it will remove twrp and put on the factory recovery.
Click to expand...
Click to collapse
Thanks everyone, we got it fixed!!!

Related

[Q] Help, wont boot after bad flash

Hi, yesterday i installed TWRP on my I9505 and I also installed cm 10.1 and it work well, I used it all day today. When i got home i saw that there was a new version of cm so i wanted to update. When i flashed it in twrp i got some error messages, i think it said it couldnt mount /system, I was stupid enough to not write it down. I had to pull the battery to restart and when i rebooted i got the "Firmware upgrade en****ered an issue" message with the triangle.
After this I tried to change recovery with odin to try and flash again but that didnt work and i cant get in to a recovery now. I can get the phone to download mode and odin can see that i plug in the phone. I tried to flash the stock recovery but I get the failed message in Odin. I have also tride to do a reset in Kies but that too failed.
Is there something i can do to save my new phone or did I mess it up permanetly? I was clinging to the hope that if i can get to download mode it can be saved but i dont know.
Any help is greatly appriciated
Bananmos said:
Hi, yesterday i installed TWRP on my I9505 and I also installed cm 10.1 and it work well, I used it all day today. When i got home i saw that there was a new version of cm so i wanted to update. When i flashed it in twrp i got some error messages, i think it said it couldnt mount /system, I was stupid enough to not write it down. I had to pull the battery to restart and when i rebooted i got the "Firmware upgrade en****ered an issue" message with the triangle.
After this I tried to change recovery with odin to try and flash again but that didnt work and i cant get in to a recovery now. I can get the phone to download mode and odin can see that i plug in the phone. I tried to flash the stock recovery but I get the failed message in Odin. I have also tride to do a reset in Kies but that too failed.
Is there something i can do to save my new phone or did I mess it up permanetly? I was clinging to the hope that if i can get to download mode it can be saved but i dont know.
Any help is greatly appriciated
Click to expand...
Click to collapse
did you tried flashing stock fw with pit file?
samersh72 said:
did you tried flashing stock fw with pit file?
Click to expand...
Click to collapse
No i havent. Is the pit file included in the firmware? And do you mean flash fw in odin? Sry if this is a stupid question.
Bananmos said:
No i havent. Is the pit file included in the firmware? And do you mean flash fw in odin? Sry if this is a stupid question.
Click to expand...
Click to collapse
yes with odin.
no pit file is not included.
first flash stock fw without pit file.
if not, flash the fw with .pit file
samersh72 said:
yes with odin.
no pit file is not included.
first flash stock fw without pit file.
if not, flash the fw with .pit file
Click to expand...
Click to collapse
Ok i downloaded the pit file and started downloading fw from samfirmware, it will take a while it looks like. So just to confirm. First i try to flash the FW in PDA in ODIN and if that works it dont need to flash the pit file? If it dosent work i flash the pit file in pit in odin and the the fw?
Thank you very much for helping me.
Bananmos said:
Ok i downloaded the pit file and started downloading fw from samfirmware, it will take a while it looks like. So just to confirm. First i try to flash the FW in PDA in ODIN and if that works it dont need to flash the pit file? If it dosent work i flash the pit file in pit in odin and the the fw?
Thank you very much for helping me.
Click to expand...
Click to collapse
yes. (unzip to get the .pit). dont flash pit file alone! but with firmware.
at the first time, when you flash only firmware in pda, dont mark re-partition
samersh72 said:
yes. (unzip to get the .pit). dont flash pit file alone! but with firmware.
at the first time, when you flash only firmware in pda, dont mark re-partition
Click to expand...
Click to collapse
Ohh ok, I select them both at the same time in Odin?
Bananmos said:
Ohh ok, I select them both at the same time in Odin?
Click to expand...
Click to collapse
yes.
did it succeed when flashed fw alone in pda first?
samersh72 said:
yes.
did it succeed when flashed fw alone in pda first?
Click to expand...
Click to collapse
The download isnt finished yet, its very slow. I will try just the fw first and let you know. If that dosent work ill try it with the pit file.
if the phone enter in bootloop after flashing, wipe data and cache from recovery and reboot
I must go offline now. please report back with the result :good:
samersh72 said:
if the phone enter in bootloop after flashing, wipe data and cache from recovery and reboot
I must go offline now. please report back with the result :good:
Click to expand...
Click to collapse
Ok thank you very much. Will tell you what happens
samersh72 said:
if the phone enter in bootloop after flashing, wipe data and cache from recovery and reboot
I must go offline now. please report back with the result :good:
Click to expand...
Click to collapse
Ok, first I tried without the pit file and its says in Odin that it failed. In the messages windows it says:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAMDE_I9505VDSAMD8_I9505XXUAMDE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> boot.img
<ID:0/007> NAND Write Start!!
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
<ID:0/007> Added!
I then tried with the pit file and fw but it faild aswell. In the message window it said
<ID:0/007> Removed!!
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAMDE_I9505VDSAMD8_I9505XXUAMDE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
<ID:0/007> Added!!
Is there something else I can try? Is it possible that this could be something wrong with the hardware?
Try to change usb port
Use original cable
Disable kies from task manager
Be sure that you downloaded fw for i9505 and it is not corrupted
Sent from my Galaxy using xda premium
Ok i will try. Should I use Odin 1.85 or 3.x?
Sent from my Galaxy Nexus using xda app-developers app
Bananmos said:
Ok i will try. Should I use Odin 1.85 or 3.x?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Same result
Sent from my Galaxy Nexus using xda premium
samersh72 said:
Try to change usb port
Use original cable
Disable kies from task manager
Be sure that you downloaded fw for i9505 and it is not corrupted
Sent from my Galaxy using xda premium
Click to expand...
Click to collapse
Ok I tried with the original cabel and in a new USB port and I could flash the fw without the pit file and now everything seems to work. I used odin 3.07. Thank you so very much for helping me. If you have a paypal I´ll be glad buy you a beer och coffe!
Bananmos said:
Ok I tried with the original cabel and in a new USB port and I could flash the fw without the pit file and now everything seems to work. I used odin 3.07. Thank you so very much for helping me. If you have a paypal I´ll be glad buy you a beer och coffe!
Click to expand...
Click to collapse
Glad to hear that. Any time my friend :thumbup:
Sent from my Galaxy using xda premium
samersh72 said:
Glad to hear that. Any time my friend :thumbup:
Sent from my Galaxy using xda premium
Click to expand...
Click to collapse
Hi , i really like you are HELPING us !!!! :good: Good guy :angel:
Thanks from all of us .

The end of my S4? (Brick/dead) - Help..

Hi guys, long time lurker here anyway i've always flashed my S4 with odin and not a single problem always flashed STOCK firmwares
but today i recently discovered a new firmware on the list for the GT-I9500 Exynos Octa (version) - this firmware to be in fact I9500ZNUCMI1
but now its bombed... it hanged and hanged at booting for 20 min then it shut it self off turned it back on 'the firmware encounter a problem' message popped up... i cannot go into recovery mode AT ALL (just download mode) so i thought i will flash my previous stock firmware known as I9500XXUBMG9 but now i cant even do that..... odin just gives me a god damn fail - FOR THE LOVE OF ANDROID HELP ME
- Kies is not running in the background
- USB connections are fine
- Cables are fine
So do i have to fear this is the end ? lol i cannot believe this happened to me on a STOCK firmware.... (lucky for me... all my stuff is backed up on sd)
Any help would be greatly appreciated
lethcore said:
Hi guys, long time lurker here anyway i've always flashed my S4 with odin and not a single problem always flashed STOCK firmwares
but today i recently discovered a new firmware on the list for the GT-I9500 Exynos Octa (version) - this firmware to be in fact I9500ZNUCMI1
but now its bombed... it hanged and hanged at booting for 20 min then it shut it self off turned it back on 'the firmware encounter a problem' message popped up... i cannot go into recovery mode AT ALL (just download mode) so i thought i will flash my previous stock firmware known as I9500XXUBMG9 but now i cant even do that..... odin just gives me a god damn fail - FOR THE LOVE OF ANDROID HELP ME
- Kies is not running in the background
- USB connections are fine
- Cables are fine
So do i have to fear this is the end ? lol i cannot believe this happened to me on a STOCK firmware.... (lucky for me... all my stuff is backed up on sd)
Any help would be greatly appreciated
Click to expand...
Click to collapse
If you can get into Download mode, all hope is not lost. Uninstall and resinstall drivers, Odin, etc. reboot.
Odin back to stock, immediately boot into stock recovery, wipe data, reboot.
Done.
donalgodon said:
If you can get into Download mode, all hope is not lost. Uninstall and resinstall drivers, Odin, etc. reboot.
Odin back to stock, immediately boot into stock recovery, wipe data, reboot.
Done.
Click to expand...
Click to collapse
Thx for reply
Still says FAIL when i try to flash I9500XXUBMG9 what am i doing wrong ?
rebooted laptop twice plug in S4 via usb says unknown device when in download mode but odin reconise it flash it and nothing happens on the screen then i get the big fat RED FAIL ............... AHHH
lethcore said:
Thx for reply
Still says FAIL when i try to flash I9500XXUBMG9 what am i doing wrong ?
rebooted laptop twice plug in S4 via usb says unknown device when in download mode but odin reconise it flash it and nothing happens on the screen then i get the big fat RED FAIL ............... AHHH
Click to expand...
Click to collapse
The good news is that Download mode is still working. AS long as that's the case, you can get it back. Just keep trying. Switch PCs, switch cables, switch ports, re download a different stock ROM, etc. do whatever it takes to try every variable you can think of.
Eventually, you'll find what's causing it and the ROM will flash successfully. When that happens, get immediately into recovery and wipe data.
(Remove the battery after it flashes, but it back in and hold vol-up+home+power.)
After the data wipe....
Reboot.
Like I said, Download mode means you can find a way to flash, but working with Odin to resolve these issues can sometimes be a PITA. I've had the same thing myself before. Just don't give up. Try to stay calm, and work your way through it. You'll get it eventually.
Edit: Just noticed that you flashed a CHINA firmware. (Why? ) You may be facing this issue because (I think) they use a different pit. There's a thread devoted to resurrecting the device with pit. Maybe check it out.
lethcore said:
Thx for reply
Still says FAIL when i try to flash I9500XXUBMG9 what am i doing wrong ?
rebooted laptop twice plug in S4 via usb says unknown device when in download mode but odin reconise it flash it and nothing happens on the screen then i get the big fat RED FAIL ............... AHHH
Click to expand...
Click to collapse
dont flash China or Hong kong firmwares.
please post odin progression
samersh72 said:
dont flash China or Hong kong firmwares.
please post odin progression
Click to expand...
Click to collapse
Nothing to post just says 'completed' but its failed.... i'll remember this next time stay away from china/hong kong firmwares...
im still tyring now and will let you guys/girls know how it pans out! wish me luck!
lethcore said:
Nothing to post just says 'completed' but its failed.... i'll remember this next time stay away from china/hong kong firmwares...
im still tyring now and will let you guys/girls know how it pans out! wish me luck!
Click to expand...
Click to collapse
INFO HERE
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500XXUBMG9_I9500OJVBMG9_I9500XXUBMG9_HOME.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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> param.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> persdata.img
<ID:0/005> system.img
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
lethcore said:
INFO HERE
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500XXUBMG9_I9500OJVBMG9_I9500XXUBMG9_HOME.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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> param.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> persdata.img
<ID:0/005> system.img
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
recovery is flashed, try to boot into it and make the wipe then re-flash stock, re-wipe.
if not, flash a custom recovery, format system, cache, re-flash stock, re-wipe
@donalgodon
Why ? well i got the I9500 in hong kong (im actually based in china now) (not Chinese though) thought i'll see some nice changes? but seems i fK'ed the phone.... pit? i haven't a clue man pit number? think i've KILLED HER... lol (i never knew the dangers of Chinese firmware) - wont be going down that route again.
@samersh72
Are you sure? i cannot get into 'recover' mode... the phone just hands at 'Firmware upgrade encounted an issue please select kies & try again
i canm only enter download mode.... when i try to enter recover mode it just flashes at the firmware message.
lethcore said:
@samersh72
Are you sure? i cannot get into 'recover' mode... the phone just hands at 'Firmware upgrade encounted an issue please select kies & try again
i canm only enter download mode.... when i try to enter recover mode it just flashes at the firmware message.
Click to expand...
Click to collapse
flash custom recovery,
if not see my signature for flashing right pit with the firmware
samersh72 said:
flash custom recovery,
if not see my signature for flashing right pit with the firmware
Click to expand...
Click to collapse
Well i just grabbed a I9500 pit file and have my stock firmware just add these 2 to odin and click start? that simple or ??
lethcore said:
Well i just grabbed a I9500 pit file and have my stock firmware just add these 2 to odin and click start? that simple or ??
Click to expand...
Click to collapse
yes, make sure that you are using the right pit, put it in "pit" window in odin, and the firmware in "pda", make sure "re-partition" is ticked, start.
samersh72 said:
yes, make sure that you are using the right pit, put it in "pit" window in odin, and the firmware in "pda", make sure "re-partition" is ticked, start.
Click to expand...
Click to collapse
Well you be happy to know
installed the previous firmware and that pit file for I9500 from your sig and everything seems well... booted correctly nothing lost all seems good to early to tell but will keep you informed !
THANK YOU!!!

[Q] Odin FAIL - N910U / From Hong Kong 4.4.4 to Taiwan 5.0.1 ROM

Hi All
I have the Hong Kong Note 4 N910U
PDA N910UXXU1AOC3
CSC N910UZZH1AOC3
As you may know, lollipop 5 is not out yet for this particular version. As I am experiencing some issues with the phone, I thought I'll just do a factory reset. However I've read somewhere here that I can use the other stock roms of the N910U eg; Taiwan 5.01 or New Zealand 5.0.1. So I thought I might aswell update to lollipop and then do a fresh factory reset.
So I downloaded this Taiwan one
PDA N910UXXU1BOD4
CSC N910UZZT1BOD4
However it keeps failing in ODIN.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910UXXU1BOD4_N910UZZT1BOD4_N910UXXU1BOD4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I did use all different versions of ODIN, tried on different usb ports, re-installed installed new drivers, used a different computer etc.. Still same outcome. I am using the original usb cable that came with the phone. What am I missing, any help will be much appreciated ?
gokhan04uk said:
Hi All
I have the Hong Kong Note 4 N910U
PDA N910UXXU1AOC3
CSC N910UZZH1AOC3
As you may know, lollipop 5 is not out yet for this particular version. As I am experiencing some issues with the phone, I thought I'll just do a factory reset. However I've read somewhere here that I can use the other stock roms of the N910U eg; Taiwan 5.01 or New Zealand 5.0.1. So I thought I might aswell update to lollipop and then do a fresh factory reset.
So I downloaded this Taiwan one
PDA N910UXXU1BOD4
CSC N910UZZT1BOD4
However it keeps failing in ODIN.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910UXXU1BOD4_N910UZZT1BOD4_N910UXXU1BOD4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I did use all different versions of ODIN, tried on different usb ports, re-installed installed new drivers, used a different computer etc.. Still same outcome. I am using the original usb cable that came with the phone. What am I missing, any help will be much appreciated ?
Click to expand...
Click to collapse
I have identical problem. Same device, same stock firmware. Trying to update to BOD4
Dancing around:
I've installed last TWRP (https://twrp.me/devices/samsunggalaxynote4exynos.html) from Odin after multiple failed attempts with N910UXXU1BOD4
Device booted normally (long boot with "updating applications")
TA-DA!
it booted to 5.0.1
It's creepy magic, but it works.
BTW, sammobile has newer version (N910UXXU1BOE3_N910UZZT1BOE3_BRI.zip)
I've repeated same procedure with newer rom: N910UXXU1BOE3/N910UZZT1BOE3:
Attempt to flash via Odin new firmware
Get error
Unplug device. Remove battery. Insert battery back. Boot to download mode again
Flash TWRP via odin
Successfully reboot to new system
stari4ek said:
I've repeated same procedure with newer rom: N910UXXU1BOE3/N910UZZT1BOE3:
Attempt to flash via Odin new firmware
Get error
Unplug device. Remove battery. Insert battery back. Boot to download mode again
Flash TWRP via odin
Successfully reboot to new system
Click to expand...
Click to collapse
Thanks for that mate. Will try it when i get home. Im not familiar with using odin or this TWRP thing. So do i download the TWRP tar file and load it to odin, then what? Can you give me the full nstructions please. Im quite confused especially the last bit under odin install method ,
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery"
gokhan04uk said:
Thanks for that mate. Will try it when i get home. Im not familiar with using odin or this TWRP thing. So do i download the TWRP tar file and load it to odin, then what? Can you give me the full nstructions please. Im quite confused especially the last bit under odin install method ,
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery"
Click to expand...
Click to collapse
My device booted to TWRP by itself without any problem, so no need to force it with keys or fastboot.
I forgot to mention, since TWRP is custom recovery You will trigger "knox void warranty 0x1", so if it's important to you - you need another way.
Does Your device boot to system after error with N910UXXU1BOD4? Cause my didn't.
Probably flashing original recovery will fix it also and will not trigger knox
I just want to clarify this just to be clear.
So after it fails you turn off, pull battery, turn on to download mode and install TWRP and then it will boot into TWRP and you just reboot and the BOE3 Taiwan firmware will just boot up? Sounds like magic, like you mentioned before.
stari4ek said:
I've repeated same procedure with newer rom: N910UXXU1BOE3/N910UZZT1BOE3:
Attempt to flash via Odin new firmware
Get error
Unplug device. Remove battery. Insert battery back. Boot to download mode again
Flash TWRP via odin
Successfully reboot to new system
Click to expand...
Click to collapse
stari4ek said:
My device booted to TWRP by itself without any problem, so no need to force it with keys or fastboot.
I forgot to mention, since TWRP is custom recovery You will trigger "knox void warranty 0x1", so if it's important to you - you need another way.
Does Your device boot to system after error with N910UXXU1BOD4? Cause my didn't.
Probably flashing original recovery will fix it also and will not trigger knox
Click to expand...
Click to collapse
Well after the error that odin gave me, i managed to recover my device using kies so my phones back on its original firmware all working. So, what is the method you used to install the latest taiwan update? Did you just go through the normal odin method or ? I dont really want to root the device, i just want to install the original stock 5.1 firmware.
a_ballads said:
I just want to clarify this just to be clear.
So after it fails you turn off, pull battery, turn on to download mode and install TWRP and then it will boot into TWRP and you just reboot and the BOE3 Taiwan firmware will just boot up? Sounds like magic, like you mentioned before.
Click to expand...
Click to collapse
yes. after error.
i "reboot" device to download mode (disconnect from usb, take out battery, put it back. volume-down+home+power).
in download mode I install TWRP.
if "auto reboot" is ticked in odin - it will reboot to new recovery (twrp) automatically. it (twrp) will perform some patching and will reboot device automatically. device will boot to system.
first boot can take a while.
---------- Post added at 10:12 AM ---------- Previous post was at 10:05 AM ----------
gokhan04uk said:
Well after the error that odin gave me, i managed to recover my device using kies so my phones back on its original firmware all working. So, what is the method you used to install the latest taiwan update? Did you just go through the normal odin method or ? I dont really want to root the device, i just want to install the original stock 5.1 firmware.
Click to expand...
Click to collapse
it.s 5.0.1 btw. There is no 5.1 yet
Yes I went through normal odin with last taiwan firmware.
it did fail with error above.
reboot to download mode.
I flashed TWRP on top of it.
when twrp is installed - system boots to new 5.0.1
KNOX is triggered!
some hours device is alive and fully working. no issues... yet =)
As usual. No responsibility here, Do it on Your own risk
stari4ek said:
yes. after error.
i "reboot" device to download mode (disconnect from usb, take out battery, put it back. volume-down+home+power).
in download mode I install TWRP.
if "auto reboot" is ticked in odin - it will reboot to new recovery (twrp) automatically. it (twrp) will perform some patching and will reboot device automatically. device will boot to system.
first boot can take a while.
---------- Post added at 10:12 AM ---------- Previous post was at 10:05 AM ----------
it.s 5.0.1 btw. There is no 5.1 yet
Yes I went through normal odin with last taiwan firmware.
it did fail with error above.
reboot to download mode.
I flashed TWRP on top of it.
when twrp is installed - system boots to new 5.0.1
KNOX is triggered!
some hours device is alive and fully working. no issues... yet =)
As usual. No responsibility here, Do it on Your own risk
Click to expand...
Click to collapse
I see. Well there should be a way of getting this installed without having to root/trigger the knox. I dont see how others are doing it through odin and our ones are failing. There should be a reason. Or it might be that this specific taiwan one fails for everyone? I did see some who flashed the new zealand one without issues..
gokhan04uk said:
I see. Well there should be a way of getting this installed without having to root/trigger the knox. I dont see how others are doing it through odin and our ones are failing. There should be a reason. Or it might be that this specific taiwan one fails for everyone? I did see some who flashed the new zealand one without issues..
Click to expand...
Click to collapse
probably it doesn't like that we're flashing different CSC.
the last image flashed is hidden.img, which if I'm not mistaken has CSC stuff
I'd expect that flashing this TAR without hidden.img or flashing original recovery instead of TWRP - will keep KNOX 0. But this homework is for someone else =)
stari4ek said:
probably it doesn't like that we're flashing different CSC.
the last image flashed is hidden.img, which if I'm not mistaken has CSC stuff
I'd expect that flashing this TAR without hidden.img or flashing original recovery instead of TWRP - will keep KNOX 0. But this homework is for someone else =)
Click to expand...
Click to collapse
Ok, Well if i do it the way you done it, will i get future ota updates or not ? i dont mind voiding warranty because the device is from hong kong, even if something goes wrong it will be a headache to send it back there and wait for it to come back. If I can get future updates wirelessly then i dont mind rooting it.
Nope. It rejects to check OTA. Manual update via Odin is still an option.
Probably, if flash original recovery and reset device, so it switches to new CSC - OTA will work. Probably.
@gokhan04uk
Flashing a custom recovery does solve the problem... but when i tried the method below i noticied changes
BUT DO IT AT YOUR OWN RISK
it worked for me
Rename tar.md5 to tar
Extract tar using 7zip
Extarct hidden.img
Flash it via Odin as PDA/AP
It was succesfull for me
P.S: Knox is not triggered
Salim.Keady said:
@gokhan04uk
Flashing a custom recovery does solve the problem... but when i tried the method below i noticied changes
BUT DO IT AT YOUR OWN RISK
it worked for me
Rename tar.md5 to tar
Extract tar using 7zip
Extarct hidden.img
Flash it via Odin as PDA/AP
It was succesfull for me
P.S: Knox is not triggered
Click to expand...
Click to collapse
This sounds interesting, can you please expand on the inductions as I am I little confused about when to flash hidden.img.
Thanks[emoji1]
Salim.Keady said:
@gokhan04uk
Flashing a custom recovery does solve the problem... but when i tried the method below i noticied changes
BUT DO IT AT YOUR OWN RISK
it worked for me
Rename tar.md5 to tar
Extract tar using 7zip
Extarct hidden.img
Flash it via Odin as PDA/AP
It was succesfull for me
P.S: Knox is not triggered
Click to expand...
Click to collapse
Can you give us full instructions please. I downloaded N910UXXU1BOE3_N910UZZT1BOE3_N910UXXU1BOE3_HOME
After I rename the md5 file to tar and extract. What do I do with the hidden.img file ?
Do I need to use only odin? or anything else
gokhan04uk said:
Can you give us full instructions please. I downloaded N910UXXU1BOE3_N910UZZT1BOE3_N910UXXU1BOE3_HOME
After I rename the md5 file to tar and extract. What do I do with the hidden.img file ?
Do I need to use only odin? or anything else
Click to expand...
Click to collapse
Flash firmware
Hidden fails
Extract hidden.img and flash it as pda
Simple as that
And remeber am not responsible even if it worked for me and another user
Salim.Keady said:
Flash firmware
Hidden fails
Extract hidden.img and flash it as pda
Simple as that
And remeber am not responsible even if it worked for me and another user
Click to expand...
Click to collapse
So I have to go through the normal odin process. Once it fails. I have to flash hidden.img through odin?
gokhan04uk said:
So I have to go through the normal odin process. Once it fails. I have to flash hidden.img through odin?
Click to expand...
Click to collapse
Yes
How do you even flash the hidden.img,ext4 files through odin?

Stuck at Odin mode ? Please help

Hi,
I wanted to reinstall the stock rom via odin and i was trying to put it to odin mode but I didn't know my Pda csc so I decided to reboot it before flashing to make sure I got the correct firmware but now it won't reboot and it's stuck at odin mode despite removing the battery and inserting it again .
Is the phone an i337 or i337m?
audit13 said:
Is the phone an i337 or i337m?
Click to expand...
Click to collapse
IT's i337 and it has the letters UD in the same line and it's from AT&T btw and I checked sammobile website and I think there are two firmware to download but I don't know which one
Thanks for your reply.I could have replied earlier but I didn't get the notification
In download mode, do you see anything about knox or warranty bit?
Id this the stock ROM you tried to flash: http://www.sammobile.com/firmwares/database/SGH-I337/ ?
audit13 said:
In download mode, do you see anything about knox or warranty bit?
Id this the stock ROM you tried to flash: http://www.sammobile.com/firmwares/database/SGH-I337/ ?
Click to expand...
Click to collapse
the knox count is :0
and I didn't even try to flash.I was seeing if i can put it into download mode and then I went to download the firmware and then found out there are two of them so when I tried rebooting to check which one I need from the system info , it got stuck.
Looks like neither of the firmware files from sammobile.com will work as your phone is running at least a 4.3 bootloader as indicated by the presence of the "Knox" in download mode. Your bootloader may be locked as well.
You can't boot into recovery either?
audit13 said:
Looks like neither of the firmware files from sammobile.com will work as your phone is running at least a 4.3 bootloader as indicated by the presence of the "Knox" in download mode. Your bootloader may be locked as well.
You can't boot into recovery either?
Click to expand...
Click to collapse
No I can't
Okay, this may help: http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
audit13 said:
Okay, this may help: http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
Click to expand...
Click to collapse
Ok I will try and let you know.I am currently trying to restore with kies
If kies doesn't work, try smart switch.
audit13 said:
If kies doesn't work, try smart switch.
Click to expand...
Click to collapse
I am getting the same error from kies and odin which is sw rev check fail : fused :5 ,binary :1
and this is odin's log :
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I might try the files in the guide but I don't know which bootloader I have
The rom can't be flashed because the rom you are flashing has a bootloader that is older than the bootloader on the phone. This is evidenced by the failed to flash the aboot.mbn file.
Where did you get the rom file?
audit13 said:
The rom can't be flashed because the rom you are flashing has a bootloader that is older than the bootloader on the phone. This is evidenced by the failed to flash the aboot.mbn file.
Where did you get the rom file?
Click to expand...
Click to collapse
I have just checked and I think kies was downloading the one with the mdl bootloader and I think it's the same one I tried flashing with odin.The first one from this link http://www.sammobile.com/firmwares/database/SGH-I337/
Thanks again
Looks like kies will not restore the phone. You'll have to flash a newer rom using Odin. Check out the link I posted earlier.
audit13 said:
Looks like kies will not restore the phone. You'll have to flash a newer rom using Odin. Check out the link I posted earlier.
Click to expand...
Click to collapse
It only has 2 firmwares and I already tried 1 and the second has a different bootloader.
Edit: If you mean the guide,then it is stated at the end that I shouldn't use it with MDL
http://forum.xda-developers.com/showpost.php?p=65534997&postcount=8
If your phone has the mdl bootloader, the mdl sammobile.comm firmware should work. If the mdl firmware can't be flashed to the phone, this tells me the phone is not running an mdl bootloader.
Yes, the guide should not be used if the bootloader is mdl but this may not be the case with your phone as there is a reference to "knox" in download mode.
audit13 said:
If your phone has the mdl bootloader, the mdl sammobile.comm firmware should work. If the mdl firmware can't be flashed to the phone, this tells me the phone is not running an mdl bootloader.
Yes, the guide should not be used if the bootloader is mdl but this may not be the case with your phone as there is a reference to "knox" in download mode.
Click to expand...
Click to collapse
I don't know what's wrong but kies and smartswitch are downloading the one with the mdl bootloader
It's probably picking the mdl because that is the only full rom available for the i337. Any updates beyond 4.2 were only released as ota updates. You will have no choice but to flash in accordance with a locked bootloader.
audit13 said:
It's probably picking the mdl because that is the only full rom available for the i337. Any updates beyond 4.2 were only released as ota updates. You will have no choice but to flash in accordance with a locked bootloader.
Click to expand...
Click to collapse
There is also the one with the mdb and I tried it too but I didn't work.I didn't understand the second sentence? Should I follow the guide and install one of the firmwares ? Which one do you recommend ? or are they the same ?

Please help me i tried rooting and now my phone won't work

I tried rooting my phone using Odin from this tutorial:
https:// theunlockr(dot)com/2016/02/04/root-samsung-galaxy-s6-edge-plus/
It failed and now my phone reads "Kernel is not seandroid enforcing" and will not enter recovery mode.
I tried installing the proper firmware but when I try using that it fails and my phone then reads "SW REV CHECK FAIL DEVICE 3 BINARY 2"
This is what Odin says:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cm.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
I don't know what to do, and any help would be greatly appreciated!
Also, the firmware I used is G928TUVU2COI5_G928TTMB2COI5_TMB and my model is SM-G928T
Can you still get into download mode? I'm thinking you rooted with the wrong version. Are you on 5.1.1 or 6.0.1?
http://forum.xda-developers.com/s6-...-root-s6-edge-plus-marshmallow-6-0-1-t3325477
kdogguk said:
Can you still get into download mode? I'm thinking you rooted with the wrong version. Are you on 5.1.1 or 6.0.1?
http://forum.xda-developers.com/s6-...-root-s6-edge-plus-marshmallow-6-0-1-t3325477
Click to expand...
Click to collapse
I'm on the most updated software, that's entirely possible. I can get on download mode, I will try to use the link you gave me and give you an update, thank you very much
kdogguk said:
Can you still get into download mode? I'm thinking you rooted with the wrong version. Are you on 5.1.1 or 6.0.1?
http://forum.xda-developers.com/s6-...-root-s6-edge-plus-marshmallow-6-0-1-t3325477
Click to expand...
Click to collapse
Okay so I tried it but since my phone doesn't turn on I cant put in the files from that link, I tried using oden and it failed again. On Odin it says Pass but my phone continues to say Kernel is Not seandroid enforcing, I've been at this for so long and I can't find a fix :'(
Where did you get your stock firmware from to flash with odin?
Is it a 3 file flash or a single large file which you place in the AP slot?
I find the 3 file ones are better as it contains the firmware, bootloader and correct files all for the same version/model.
Try sammobile, the download is slow if you don't have premium access to the download site.
You can also try the program kies or whatever the recovery program is these days, I remember with my note having exhausted all possibilities using it and it actually worked. It's slow but might bring your phone back to life.
Looks like the recovery program lies is now called smart switch...
http://forum.xda-developers.com/tmo...p/flash-stock-firmware-using-samsung-t3079176
kdogguk said:
Where did you get your stock firmware from to flash with odin?
Is it a 3 file flash or a single large file which you place in the AP slot?
I find the 3 file ones are better as it contains the firmware, bootloader and correct files all for the same version/model.
Try sammobile, the download is slow if you don't have premium access to the download site.
You can also try the program kies or whatever the recovery program is these days, I remember with my note having exhausted all possibilities using it and it actually worked. It's slow but might bring your phone back to life.
Looks like the recovery program lies is now called smart switch...
http://forum.xda-developers.com/tmo...p/flash-stock-firmware-using-samsung-t3079176
Click to expand...
Click to collapse
It's a three file flash I believe, I've just been putting one huge file in the AP, I haven't heard of the three file thing, I've tried the Sammobile firmware stock too and it hasn't worked. It fails on Odin. Do you know anything else I could try?
You could try grabbing TWRP recovery and flashing that with odin. That could give you access to a recovery to wipe and factory wipe. You could grab a custom rom and use TWRP to install that.
If you could find the 3 file flash it might help because it will have the right bootloader/firmware/csc for your phone.
Just a quick thought... Have you tried running odin with administration rights in Windows? And is it the latest version of odin?
---------- Post added at 09:42 AM ---------- Previous post was at 09:35 AM ----------
Found these links for you to have a look at...
http://forum.xda-developers.com/tmo...sources-tmobile-g928t-galaxy-s6-edge-t3204478
http://forum.xda-developers.com/tmo...rmware-g928t-complete-untouched-boh6-t3198387
kdogguk said:
You could try grabbing TWRP recovery and flashing that with odin. That could give you access to a recovery to wipe and factory wipe. You could grab a custom rom and use TWRP to install that.
If you could find the 3 file flash it might help because it will have the right bootloader/firmware/csc for your phone.
Just a quick thought... Have you tried running odin with administration rights in Windows? And is it the latest version of odin?
---------- Post added at 09:42 AM ---------- Previous post was at 09:35 AM ----------
Found these links for you to have a look at...
http://forum.xda-developers.com/tmo...sources-tmobile-g928t-galaxy-s6-edge-t3204478
http://forum.xda-developers.com/tmo...rmware-g928t-complete-untouched-boh6-t3198387
Click to expand...
Click to collapse
Sorry this is really late, apparently nothing worked, I took it to the uBreakiFix and they apparently had to install the firmware by it's build number which took like a week cause I had to go through every single build number. But thank you very much for your help

Categories

Resources