[Q] Soft Bricked sgh-i337m. Please Help - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

Please lend a hand to help me rectify a problem.
Started earlier today by CF-Auto-Root my New Rogers SGH-i1337m, installed without incident via Odin 3.07, followed up with TWRP 2.7 install, again via Odin, without incident, then created NANDROID backup to ext sdcard.
First issues started cropping up, but culminating in what appears to be soft bricking:
1st) Could not mount internal memory (was attempting to browse in Windows) via TWRP. Every time I would select internal memory it would mount the sd card contents only. Weird, but pales compared to further issues.
2nd) Was preparing to install Custom ROM, boot into TWRP, attempted factory reset but this just constantly restarted TWRP. Thought this was strange so I figured Id use Goomanager to update TWRP, occurred without incident and I went back to attempt to factory reset, but then trouble started.
3rd) Boot looping, could not boot back into the OS. Decided I would attempt to restore my Nandroid backup, TWRP loads fine but restore didn't work. Figured Id try flashing back to stock rom (obtained RWC-I337MVLUEMK6-20131125124040 via links in other comments. This is where things got out of control:
A) Restore via Odin 3.07 failed, device restart failedbut loaded the "Firmware Upgrade encountered an issue..." screen.
B) Attempted redownloading the stock rom, new usb port, new oem cable, reinstalled drivers, and with each Odin would fail as follows:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUEMK6_I337MOYAEMK6_I337MVLUEMK6_HOME.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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
C) Briefly TWRP would not load, so I reflashed 2.7.0.1 for openrecovery-twrp-2.7.0.1-jfltecan without incident, TWRP reloaded fine, could now do factory reset, but often end up getting could not mount /system. Now using TWRP to restore theNANDRPID from earlier seemed to rebuild the partitions and said it was successful, and the device will boot to a static Samsung screen, but after 20 mins of waiting, would not boot farther.
D) At this point tried to reflash w Odin 3.07 the stock, but still get that error.
So here is where I'm at, with what appears to get me the closest to booting/flashing with stock:
1) Reflashed openrecovery-twrp-2.7.0.1-jfltecan.tar with Odin 3.07, immediately following this:
<ID:0/004> Removed!!
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/004> Added!!
<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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
..and the device hangs @ "Samsung Galaxy S4" black screen, letting that sit for 15mins without any change (didn't expect it to, but may as well be complete).
2) TWRP is bootable (load screen says Recovery is not SEANDROID ENFORCED and Set Warranty Bit: recovery) and functional, rebooting recovery states "No OS installed, are you sure you want to restart? ". Interestingly with 2.7.0.1 now installed, i can factory reset but with errors "E: unable to mount '/system". In TWRP, i have tried restore of my NANDROID backup, it completes successfully and appears to rebuild the partitions, but even after completing the restore and rebooting, still end up hanging at the static Samsung screen for >20mins without a change. I could transpose the entire log from the restore if needed.
3) At this point I would try Odin 3.07 with the above stock image, and the failure when attempting to write system occurs again.
Ive been searching for hours and hours and attempting to reflash but not making any headway.
Could anyone help point me in some better directions? I just finished attempting KIES emergency restore, but it too failed when it tried to upload to the device.
Any help would be greatly appreciated.

You've done all the right things. The only other thing I can think of is using a different firmware version in Odin.
Sent from my Nexus 5

jd1639 said:
You've done all the right things. The only other thing I can think of is using a different firmware version in Odin.
Sent from my Nexus 5
Click to expand...
Click to collapse
Perhaps I should try flashing a custom rom? Maybe something like CM 10.2?
I think the problem lies with a possible permission problem with the system partition, but I don't know how to go about checking those permissions, let alone correcting a possible fault.
Thoughts?

Did you factory reset in stock recovery before you installed twrp?
Sent from my SGH-I337M using Tapatalk

2Tone5 said:
Did you factory reset in stock recovery before you installed twrp?
Sent from my SGH-I337M using Tapatalk
Click to expand...
Click to collapse
I believe so, but it has been several iterations of different attempts to fix things that I cannot be certain any longer.
Let's pretend I didn't, for arguments sake. Implications?
Furthermore, I have created some life back into the device; however, still having problems.
1) Using ODIN 3.09, I successfully flashed TWRP back on to the device.
2) With TWRP, I successfully flashed CM 10.2. The device loads completely into the OS--the only thing I cannot confirm yet is full telephone functionality as my backup phone is what was reconnected to ROGERS. So.....there is life in this thing yet.
3) With TWRP, I have successfully created NANDROID backup of the device under 10.2 and used it to restore after a few failed attempts at getting to stock.
So here's a problem for right now: No matter what source stock ROM I have been using, I337MVLUFNC1_I337MOYAFNC1_I337MVLUFNC1_HOME.tar.md5 or I337MVLUFNC1_880525_REV06_user_low_ship_MULTI (both are what were claimed to be stock 4.4.2 for sgh-i337m ROGERS), it consistently fails in ODIN when flashing system.
I can easily then reflash TWRP (because the ODIN flashing the above stock breaks the recovery image), get into TWRP and restore the CM10.2 NANDROID, and at least back in business there.
I'm about to try flashing (again, but likely fruitlessly) RWC-I337MVLUEMK6-20131125124040.zip from samsung-updates.com via ODIN 3.09. I don't have much hope that ODIN will get it onto the device.
Seems to me like perhaps ODIN can't get the stock roms onto the device for some reason!? Am I doing something wrong? Perhaps someone can point me to a stock 4.3 (or 4.4.2) ROM for ROGERS SGH-i337M that is known to work (or at least deemed reliable) that I could try? Perhaps ODIN is messed up for me?
I'm pretty frustrated as I would think if I can install via TWRP a custom kernel and custom ROM, I should be able to get the stock ROM/etc. back onto the device.
Perhaps I'm missing a step?
TWRP: Wipe> Factory Reset then wipe Cache.
Reboot into Download Mode
ODIN 3.09: Added!! --> AP Select my stock ROM (any of the above), only have Auto Reboot and F. Reset Time selected, start (then fail in my case).
Perhaps I should find another computer!? I have two OEM cables, tried both ports......
This is ridiculously frustrating.

Which bootloader are you on?
Sent from my SGH-I337M using Tapatalk

Just wanted to say that I got burned by TRWP a few days ago due to the same issues.
1) Flashed a custom kernel days before. Was working fine but didn't like the performance of the new kernel so I decided to restore my backups of /boot and /system.
2) Did the restore. Cleared /cache and dalvik. Reboot.
3) Stuck on the Samsung Galaxy S4 bootloader screen.
4) Tried to reboot into TWRP, but didn't work. Would just cause phone to automatically restart and hang at the bootloader screen.
5) After many many reboots, was able to finally boot into TWRP.
6) Flashed a custom ROM based the original stock ROM I had installed and that got me up and running again. No data loss as I never touched /data with TWRP.
I'm currently experimenting with CWM and Philz. TWRP, never again.

2Tone5 said:
Which bootloader are you on?
Sent from my SGH-I337M using Tapatalk
Click to expand...
Click to collapse
Uncertain at this point -- any way to determine that or just flash a known decent one?
Interestingly: CM10.2.1 everything works except for calls and any other sound on the device. ......this is ridiculous.

bzwick said:
Uncertain at this point -- any way to determine that or just flash a known decent one?
Interestingly: CM10.2.1 everything works except for calls and any other sound on the device. ......this is ridiculous.
Click to expand...
Click to collapse
Upon more research, I guess I have a knox bootloader since I have a Knox 0x1 trip.

bzwick said:
Upon more research, I guess I have a knox bootloader since I have a Knox 0x1 trip.
Click to expand...
Click to collapse
Without knowing exactly, theres more trial and error ... so ill give you an example: you can't flash 4.2.2 firmware.tar.md5 over a 4.4.2 bootloader (which sounds like you may have )in odin anymore due to knox. What I can suggest to you that should work is go to sammobile.com and download the latest 4.4.2 official firmware for the 1337m and follow the instructions precisely on the download page.
Sent from my SGH-I337M using Tapatalk
---------- Post added at 12:14 AM ---------- Previous post was at 12:12 AM ----------
http://www.sammobile.com/firmwares/
Sent from my SGH-I337M using Tapatalk
---------- Post added at 12:16 AM ---------- Previous post was at 12:14 AM ----------
Once you download it and its installed make sure to turn off your phone and boot into stock recovery and do a factory reset and if you really want to be clean flash the firmware again and all your problems should be gone
Sent from my SGH-I337M using Tapatalk

2Tone5 said:
Without knowing exactly, theres more trial and error ... so ill give you an example: you can't flash 4.2.2 firmware.tar.md5 over a 4.4.2 bootloader (which sounds like you may have )in odin anymore due to knox. What I can suggest to you that should work is go to sammobile.com and download the latest 4.4.2 official firmware for the 1337m and follow the instructions precisely on the download page.
Sent from my SGH-I337M using Tapatalk
---------- Post added at 12:14 AM ---------- Previous post was at 12:12 AM ----------
http://www.sammobile.com/firmwares/
Sent from my SGH-I337M using Tapatalk
---------- Post added at 12:16 AM ---------- Previous post was at 12:14 AM ----------
Once you download it and its installed make sure to turn off your phone and boot into stock recovery and do a factory reset and if you really want to be clean flash the firmware again and all your problems should be gone
Sent from my SGH-I337M using Tapatalk
Click to expand...
Click to collapse
Ok, I'll give it a go and report findings as follows (decided to try a different computer to eliminate that fact too):
1) sammobile.com --> http://www.sammobile.com/firmwares/3/?download=26590 - PDA - I337MVLUFNC1, CSC - I337MOYAFNC1, etc.
2) Downloaded and installed fresh 3.09 from sammobile per instructions.
3) Successfully flashed this firmware, phone returning back to normal as official kernel and official rom, knox warranty tripped still, but that's the way it goes.
SO: Moral of the story - ensure that not just using any kind of virtualization software to try and do flashing, use a proper PC. I hope somehow this finds its way to some other schlub that messes this up.
ROGERS is sending me a new phone anyway other problems involving sound and I was within 15 day return. Lucky me I guess...
I guess the next time around I'll need a closer look at avoiding knox tripping...

It works for me
2Tone5 said:
[/COLOR]Once you download it and its installed make sure to turn off your phone and boot into stock recovery and do a factory reset and if you really want to be clean flash the firmware again and all your problems should be gone
Sent from my SGH-I337M using Tapatalk
Click to expand...
Click to collapse
Thank you!! It works for me. It's very important to do a clean flash. :good:

I am having a crazy issue I can't seem to fix with my i337. I am trying to revert back to stock and I ran odin I get a pass notification but when I reboot my phone prompts that I have unauthorized software on my phone an to contact AT&T. I can't seem to make this work and I can't boot into recovery. Any ideas on what may help. Feeling pretty lost at this point.

Related

[Q] N9005 revert to stock rom

Cheers!
I recently flashed CyanogenMod 11 on my N9005. The thing is i'm not happy with it and i want to revert back to a stock rom. So what i was wondering is if i have to revert to the exact old version (4.3) or i could flash a stock KitKat firmware from SamMobile and how can i do that? I read a thread where a guy bricked his phone when trying with cwm cause he had some files missing. I know most users are sick of noobs like me asking this kind of questions but i would much appreciate if someone could help me out.
Thanks
FreeeMans20 said:
Cheers!
I recently flashed CyanogenMod 11 on my N9005. The thing is i'm not happy with it and i want to revert back to a stock rom. So what i was wondering is if i have to revert to the exact old version (4.3) or i could flash a stock KitKat firmware from SamMobile and how can i do that? I read a thread where a guy bricked his phone when trying with cwm cause he had some files missing. I know most users are sick of noobs like me asking this kind of questions but i would much appreciate if someone could help me out.
Thanks
Click to expand...
Click to collapse
Follow the instructions on the link, also there is a link on that page which takes you another page how to root N9005XXUENB7 which is the latest firmware for samsung galaxy note 3 SM-N9005. Please make sure you follow the instructions carefully and you have the right model international Note 3 SM-N9005,
http://nasirtech.blogspot.co.uk/2014/03/n9005xxuenb7-android-442-kitkat.html
The above method is for bringing the phone to factory stock. If you just want to revert back to a samsung rom and your phone is rooted with custom recovery, which I presume it is, you can just flash a samsung rom of your choice there are plenty to choose from and every rom thread have instructions how to flash their rom
Hope this helps, all the best.
Cheers
vtec303 said:
Follow the instructions on the link, also there is a link on that page which takes you another page how to root N9005XXUENB7 which is the latest firmware for samsung galaxy note 3 SM-N9005. Please make sure you follow the instructions carefully and you have the right model international Note 3 SM-N9005,
The above method is for bringing the phone to factory stock. If you just want to revert back to a samsung rom and your phone is rooted with custom recovery, which I presume it is, you can just flash a samsung rom of your choice there are plenty to choose from and every rom thread have instructions how to flash their rom
Hope this helps, all the best.
Click to expand...
Click to collapse
Cheers man. I'm downloading as we speak. Hopefully i'll come back with good news.
No problem mate, I am sure the process will go butter smooth but let us know if you come across any problems , all the best.
Problem in Odin
vtec303 said:
No problem mate, I am sure the process will go butter smooth but let us know if you come across any problems , all the best.
Click to expand...
Click to collapse
So, like yesterday, Odin fails on me. At the very end. When the green loading bar is full and it seems like it's going to succeed, the last line says failed. The phone has CWM 6.0.4.7 flashed and CF AutoRoot. Any ideeas?
FreeeMans20 said:
So, like yesterday, Odin fails on me. At the very end. When the green loading bar is full and it seems like it's going to succeed, the last line says failed. The phone has CWM 6.0.4.7 flashed and CF AutoRoot. Any ideeas?
Click to expand...
Click to collapse
ok that NB7 is failing on me as well for some reason, but in the mean time to get your phone back on line download NB4 (link below) and flash using odin 3.07, thats what I did and got no errors phone booted with no problems, if it takes too long to boot after flashing or goes in a boot loop enter recovery mode (home+power+vol up) and do data/factory reset and clear cache but that will wipe the internal storage, hope this will work
http://samsung-updates.com/device/?id=SM-N9005
Thanks
vtec303 said:
ok that NB7 is failing on me as well for some reason, but in the mean time to get your phone back on line download NB4 (link below) and flash using odin 3.07, thats what I did and got no errors phone booted with no problems, if it takes too long to boot after flashing or goes in a boot loop enter recovery mode (home+power+vol up) and do data/factory reset and clear cache but that will wipe the internal storage, hope this will work
http://samsung-updates.com/device/?id=SM-N9005
Click to expand...
Click to collapse
Downloading as we speak. I'll give it a try when done. I'll let you know!
Same
vtec303 said:
ok that NB7 is failing on me as well for some reason, but in the mean time to get your phone back on line download NB4 (link below) and flash using odin 3.07, thats what I did and got no errors phone booted with no problems, if it takes too long to boot after flashing or goes in a boot loop enter recovery mode (home+power+vol up) and do data/factory reset and clear cache but that will wipe the internal storage, hope this will work
http://samsung-updates.com/device/?id=SM-N9005
Click to expand...
Click to collapse
Same thing. This is what i'm getting every time i try to flash a ROM.Any other suggestions? Vtec303, can you please tell what are the exact steps you took to flash it? Thanks
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB4_N9005AUTENB1_N9005XXUENB1_HOME.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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)
ok sorry to hear that mate, give one more try with NB3, hopefully that should work, fingers crossed
If that fails than try this:
http://forum.xda-developers.com/showthread.php?t=2613374
That guys phone is a Hong Kong model but the files he is using to flash are compatible with international Note 3
SM N9005.
Sent from my SM-N9005 using Tapatalk
Another thing is your phone a 16GB model ?, or is it 32 or 64GB, cheers.
It's actually 32GB. I'm just after realizing. Would that be the reason why it's not working?
Sent from my SM-N9005 using xda app-developers app
Thanks
vtec303 said:
ok sorry to hear that mate, give one more try with NB3, hopefully that should work, fingers crossed
If that fails than try this:
http://forum.xda-developers.com/showthread.php?t=2613374
That guys phone is a Hong Kong model but the files he is using to flash are compatible with international Note 3
SM N9005.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Thanks man. FeralFire's tutorial helped me a lot. That was the only way i could flash a custom ROM. And thanks for opening my eyes and reminding me about the size of my phone. For some reason, i got stuck to thinking that my device has only 16GB. Cheers and a big Thanks for your help!
No problem ur welcome, I am glad your phone is back online mate and I hope it stays that way , all the best, tc
Sent from my SM-N9005 using Tapatalk

please help before I brick it

good evening
I am in a bit of tight spot
and before a srew it up (more) I wonder if you could help
I have a SM-G900V which is rooted and I had TWRP working just fine
I tried to flash a rom (project infinity) with aroma which freezed on installing aroma
the developer replied to me that the problem was from TWRP which had a bus and that I should instal CWP
I tried to install CWP on top of TWRP through ODIN and got a failure message
as of now I have neither TWRP or CWP or any rom flashed in mydevice
once I go into recovery mode and try to flash the previous rom that I had through the sdcard it says "footer is wrong signature fail" an reboots and gets stuck with no rom
just tried to reinstall TWRP through ODIN and got the failure message again
with the folowing message:
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth) <OSM> All threads completed. (succeed 0 / failed 1)
please help
Hey man,
Sounds like you're in a bit of a pickle. Not sure if this would be a bit extreme, but I'd download the stock firmware and flash it through Odin. After that, reflash recovery and retry your rom.
I kind of see flashing back to stock a 'fail safe' in most cases, so it's always handy to have the stock firmware stored somewhere anyway. ?
Sent from my SM-G900I
..
fffft said:
Don't flash anything until someone discerns what went wrong..
being impatient at this point will put you at high risk of bricking or worse.
The phone boots normally up until the footer error?
What is the exact error message that you see?
What version of TWRP did you have?
Any backups? If so, do they include your baseband, EFS & PIT?
16 GB ROM?
Did you have a Verizon ROM when this happened?
Rooted?
.
Click to expand...
Click to collapse
let me start by thank you for your time!
I am a bit new to all this, I have flashed some roms in the past so I am also familiar with some stuff...
The phone doesn't boot it gets stuck like the attached picture, the OS doesn't start.
I don't see any message as it is stuck like I mentioned before, I just saw a message of "FAIL!" in Odin when I tried to install CWM on top of TWRP
my version of TWRP was 2.7.1.0
I had a backup on TWRP but as I dont see TWRP working anymore I dont know if its still available
my phone is 16GB
my SM-G900V is rooted and at the moment I had working perfectly SpeedROM v1 Rev2
if you would like to contact me through chat let me know, and again thank you very much!!
Try this
..
fffft said:
Okay, on the positive side there isn't anything to suggest that your bootloader is corrupt which would make this a lot harder. Probably the failed aroma install just messed your kernel up. But I don't want to recommend messing around with shortcut solutions e.g. just flashing the kernel that may or may not work, but would put you at unnecessary further risk.
The earlier suggestion to flash a full stock image is generally sound advice, but it does not apply to all situations. My questions were basically aimed at getting a sense of whether you have corrupted the bootloader or partitioning which has a bearing on how to best recover your phone.
First, I am assuming that you do not have the Dev (unlocked bootloader) version S5. If you have the Dev edition with the unlocked bootloader, do not proceed with the rest of this post until we discuss that.
On the assumption that you have a regular 16 GB Verizon SM-G900V S5, then I would like to see you Odin flash a full stock S5 Verizon image that has been rooted. Unfortunately I couldn't find anyone who has made and posted a stock rooted Verizon S5 image like that. I don't mean a stock rooted (custom) ROM.. I mean the full stock firmware image, including the bootloader, but rooted.
That's fine. The rooted part would just be a little extra insurance put against theoretical possible snags i.e. Knox issues. So I will suggest that you use Odin to flash a full stock Verizon S5 image, with an explicit partition table. Normally we don't touch the partition information (PIT) in Odin, but in your case we need to.
Download the files below from this thread
Unless you already have the file on your PC
Verizon S5 Retail Tar 4.4.2 NCG baseband and Mar 31 kernel
MD5: 699a949b57c771b00db9f3ed675c7a5e
NCG Pit
MD5: 3dd82f91a02c82e60e0a1f9964fdb5c0
Odin 3.09
MD5: 810ad286967d0a33881fd8181d35959f
You should thank the OP in that thread for collating the files that you need in one place.
Particularly that all important PIT file.
Start Odin and check these three boxes only: Auto reboot, Re-Partition, F. Reset Time
Choose the PIT file in the PIT window. Note that the PIT file needs to be extracted. Do not leave it zipped.
Choose the stock firmware tar.md5 file in the PDA window. The tar.md5 file needs to remain tarred i.e. tar.md5 or .tar
Put your phone into download mode. Ensure that your phone is off, remove the battery for a few seconds if necessary, then press volume down + home + power until you see the android robot screen come up. If it doesn't go into download mode, repeat these steps. And in the very unlikely event that you can't get into the download mode at all, stop and post that information
Connect your phone to your PC, Odin should say that it has detected your phone
Press start and let Odin flash your phone
Basically we are replacing all of the system files and assuring that your partitioning has not been corrupted
When Odin finishes with a success message your phone should be back to normal. Do a normal reboot to confirm
If you did not backup your phone, your user files in the /data partition might still be accessible
Decide if you wish to back them up or not. Do so if you need them. Then do a factory reset from the Settings menu
You will need to re-root and reinstall your apps, etc
If you run into any difficulties:
If the Odin write fails, note the error message and double check that your Odin settings were correct
Do not close Odin. Pull the battery from your phone for ten seconds.
Then replace the battery and go into download mode again (vol down + home + power)
Note whether Odin detects the phone
Then try flashing with Odin again. Note that you are not closing the Odin program if the first flash attempt fails
Odin can be a bit picky and it is not unheard of to have to reset the phone like this and run the session a second time
Odin is also picky about USB cables. If you still continued trouble, try a different USB cable and USB port
Don't despair if anything goes astray. There is almost always an alternate way to go about something.
Let us know your results so that we can (hopefully) celebrate. Or at least regroup.
.
Click to expand...
Click to collapse
you senior member??? pppffffffff
you should OWN this forum!!! thanx a lot for your extended time in this explanation mate, I will proceed and let you know
Agreed. I use a Dell and sometimes I have problems with odin using the front usb. I have to use the read usb and then no problems.
Hi Guys!!
I am back, back with my phone completely restored
A special THANX to fffff for your help!!
..

[Q] S4 Soft Brick

Hey so one of my friends is having problems getting their S4 to boot. Currently she has K0T49H.L720VPUFNAE on her S4. She has no custom recovery, but did have the phone rooted. Now the device can't boot. It gets past the Samsung Galaxy S4 screen and then goes black, the blue notification light pulses, and the phone makes a beep (almost like the initial boot sound) and then just hangs there. I've tried to odin back to stock, but I receive "failed! (Auth) almost immediately after starting.
On the Samsung Galaxy S4 screen both "Kernel is not seandroid enforcing" & "Warranty bit: kernel" are displayed in the top corner.
I can boot into stock recovery & download mode.
Any help would be appreciated!
It sounds like you are trying to Odin an older version on there than NAE. You cant downgrade, only can flash the NAE tar or the newer NG2.
Download it here, and try flashing it instead. After you flash, if it still wont boot, boot into recovery mode and do a factory reset.
random45 said:
It sounds like you are trying to Odin an older version on there than NAE. You cant downgrade, only can flash the NAE tar or the newer NG2.
Download it here, and try flashing it instead. After you flash, if it still wont boot, boot into recovery mode and do a factory reset.
Click to expand...
Click to collapse
I am trying to flash NAE tar and have tried the NG2. Both result in the errors mentioned above.
I also have gone into stock recovery and performed a factory reset.
Joey43 said:
I am trying to flash NAE tar and have tried the NG2. Both result in the errors mentioned above.
I also have gone into stock recovery and performed a factory reset.
Click to expand...
Click to collapse
can you post the log from odin? Also what version of odin are you using? have you tried flashing Phil's Recovery and maybe just installing a ROM?
random45 said:
can you post the log from odin? Also what version of odin are you using? have you tried flashing Phil's Recovery and maybe just installing a ROM?
Click to expand...
Click to collapse
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.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> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
There's the log. I can't install a custom recovery either. It acts like it is installing correctly, but when it reboots it is still stock recovery.
Joey43 said:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.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> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
There's the log. I can't install a custom recovery either. It acts like it is installing correctly, but when it reboots it is still stock recovery.
Click to expand...
Click to collapse
what version of odin are you using?
random45 said:
what version of odin are you using?
Click to expand...
Click to collapse
Oh, sorry. I've tried both 3.07 & 3.09
Joey43 said:
Oh, sorry. I've tried both 3.07 & 3.09
Click to expand...
Click to collapse
Okay, its really strange honestly. I spent sometime looking online for possible solutions, and the only thing I can come up with is:
1. make sure you are using the usb cable that came with the phone, and that it is undamaged
2. if its a desktop, make sure the usb cable is connected on the back. if you have usb 3.0 ports try it on there
3. some people say odin and kies dont get along. I do not share this experience, but who knows, doesnt hurt to try uninstalling kies, and install phone drivers
How did this happen by the way?
random45 said:
Okay, its really strange honestly. I spent sometime looking online for possible solutions, and the only thing I can come up with is:
1. make sure you are using the usb cable that came with the phone, and that it is undamaged
2. if its a desktop, make sure the usb cable is connected on the back. if you have usb 3.0 ports try it on there
3. some people say odin and kies dont get along. I do not share this experience, but who knows, doesnt hurt to try uninstalling kies, and install phone drivers
How did this happen by the way?
Click to expand...
Click to collapse
I'm using my S3 cable since her OEM one is broken. I tried around 4 different cables since I had the same thought. I never had kies installed and I did install the drivers.
I have really awful internet stability and speed (like 100kbs) so I'm hoping that the download is just corrupted and I'm just trying to re-download it.
I honestly don't know, she gave it to her brother to look at first, whom I suspect made the issue worse. I'm usually pretty good at fixing these things and I thought that it was an easy fix since it could reach download mode. I really appreciate all the help still.
have you tried flashing a pit file?
here is a 16 GB Sprint L720 NAE pit file you can try. do that with caution, and as a last resort.
Joey43 said:
I'm using my S3 cable since her OEM one is broken. I tried around 4 different cables since I had the same thought. I never had kies installed and I did install the drivers.
I have really awful internet stability and speed (like 100kbs) so I'm hoping that the download is just corrupted and I'm just trying to re-download it.
I honestly don't know, she gave it to her brother to look at first, whom I suspect made the issue worse. I'm usually pretty good at fixing these things and I thought that it was an easy fix since it could reach download mode. I really appreciate all the help still.
Click to expand...
Click to collapse
random45 said:
have you tried flashing a pit file?
here is a 16 GB Sprint L720 NAE pit file you can try. do that with caution, and as a last resort.
Click to expand...
Click to collapse
I tried that and received a "secure check fail: PIT" error. Phone performs the same as before.
i think the phone's busted....maybe try sending it to that one place that can jtag phones?
I think this is the site, but dont hold me to it.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s4-jtag-brick-repair/
random45 said:
i think the phone's busted....maybe try sending it to that one place that can jtag phones?
I think this is the site, but dont hold me to it.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s4-jtag-brick-repair/
Click to expand...
Click to collapse
I got philz custom recovery finally, and was able to flash NG2 pre-rooted, but the baseband version is old and wifi/data isn't working. I'm trying to flash the NG2 Modem.tar under the phone tab in odin, but i receive fail auth still and secure check fail: apnhlos.
I'm currently pursuing .tar to flashable .zip python converters, because it seems I cannot flash anything but one specific version of philz recovery in odin, but can flash anything through custom recovery.
Joey43 said:
I got philz custom recovery finally, and was able to flash NG2 pre-rooted, but the baseband version is old and wifi/data isn't working. I'm trying to flash the NG2 Modem.tar under the phone tab in odin, but i receive fail auth still and secure check fail: apnhlos.
I'm currently pursuing .tar to flashable .zip python converters, because it seems I cannot flash anything but one specific version of philz recovery in odin, but can flash anything through custom recovery.
Click to expand...
Click to collapse
Okay, so your making some progress.
random45 said:
Okay, so your making some progress.
Click to expand...
Click to collapse
where can i get that philz recovery im goin thru the same thang
I don't have this phone anymore. Good luck.
Sent from my SM-N910P using Tapatalk
To be honest TWRP is your better option for recovery on the S4 (I was a staunch supporter of Philz on my S3) one thing you need to make sure when you flash TWRP it to uncheck the auto reboot option. When flash completes, unplug and pull battery and then boot directly into recovery, then it sticks. You may be having WiFi/data issues because of your baseband/ROM combo. Have you tried flashing the latest stock?
Need Help Device stuck After flash?
I have the sprint sph l720t model. I finally acquired root access. I tried to flash Cyogenmod. When I did, it finished and rebooted and a after reboot it says cyogen mod in a circle that just keeps on spinning. I tried to get back to my blue team win screen into recovery but no luck. I got the phone to go into download mode once. I do have backups on my SD card with all the files can I flash a backup? What can I do?? The recovery says in red kernel is not se enforcing then under that in yellow set warranty bit: kernel? Can I use odin to do something in download mode to get my device back up?? I did refash my MD.5 file again from chainfire no luck! Help? Thanks
mattzeller said:
To be honest TWRP is your better option for recovery on the S4 (I was a staunch supporter of Philz on my S3) one thing you need to make sure when you flash TWRP it to uncheck the auto reboot option. When flash completes, unplug and pull battery and then boot directly into recovery, then it sticks. You may be having WiFi/data issues because of your baseband/ROM combo. Have you tried flashing the latest stock?
Click to expand...
Click to collapse
Yes I am now running Lollipop 5.0.1. I also did finally get TWRP installed. Everything is back to normaral. I re-installed the firmware from sam mobile. I then ofcoarse, went and flashed cf-autoroot with Odin. I pulled the batterry this time and booted up into recovery. Somehow everything is working and I do have recovery somewhere in my device. I want to try another Rom but Honestly TWRP makes me nervous evertime I open the app! What should I try next. Its just like factory rom with root but not really root. Its weird. At suggestios would be cool.. Thanks
EngineManShawn said:
Yes I am now running Lollipop 5.0.1. I also did finally get TWRP installed. Everything is back to normaral. I re-installed the firmware from sam mobile. I then ofcoarse, went and flashed cf-autoroot with Odin. I pulled the batterry this time and booted up into recovery. Somehow everything is working and I do have recovery somewhere in my device. I want to try another Rom but Honestly TWRP makes me nervous evertime I open the app! What should I try next. Its just like factory rom with root but not really root. Its weird. At suggestios would be cool.. Thanks
Click to expand...
Click to collapse
You have a lot of options now that you are presumably on the latest baseband. Just download the ROM you want, copy it to your external SD card and flash in TWRP.
If you like TouchWiz I suggest Wicked X:
http://forum.xda-developers.com/showthread.php?t=3115583
It's a fairly modified TW ROM, with quite a few mods that you can apply as you see fit. The developer is fantastic, quick to support and address issues. Every time he changes devices, I change to that device, he's that good. I've been stalking him since his time developing for the S2.
If TW isn't your thing, I suggest BlissPop:
http://forum.xda-developers.com/showthread.php?p=62018060
When I'm not running Wicked X I'm running BlissPop. The only caveat is I have not been able to get data to work properly on the latest builds, but the experimental build from 9/28 that I run is flawless. If you can't find it on their page, let me know I have it up on Mega.
Neither one is better than the other, it just a matter of preference. They both have great battery life, especially when paired with Greenify.

At&T s5 Bootloop

Classic case of bootlooping.
Recently used Flashfire to install rooted stock version of Lollipop 5.0. After trying to reinstall X-posed framework by flashing through flashfire, phone became bootlooped at At&t logo, remaining bricked after factory reseting and clearing cache.
Used odin to try and downgrade back to a stable version of 4.4 kickat. However, phone now bootloops after shuddering at samsung logo, before blipping to black screen with blue indicator light permently on. Trying to install current version of OTA rom through default recovery made no change. Suspecting bootloader my be root of issue, as trying to flash stock version of 4.4 bootloader in odin fails.
Currently looking for options to simple get phone back complete factor reset at this point. Links to other threads that have already solved this problem welcome.
SkunkID said:
Classic case of bootlooping.
Recently used Flashfire to install rooted stock version of Lollipop 5.0. After trying to reinstall X-posed framework by flashing through flashfire, phone became bootlooped at At&t logo, remaining bricked after factory reseting and clearing cache.
Used odin to try and downgrade back to a stable version of 4.4 kickat. However, phone now bootloops after shuddering at samsung logo, before blipping to black screen with blue indicator light permently on. Trying to install current version of OTA rom through default recovery made no change. Suspecting bootloader my be root of issue, as trying to flash stock version of 4.4 bootloader in odin fails.
Currently looking for options to simple get phone back complete factor reset at this point. Links to other threads that have already solved this problem welcome.
Click to expand...
Click to collapse
Did you do a full wipe after coming back from lollipop? You will always need to do that whether your are changing roms or moving from one android version to another. Try to make a full wipe in recovery and then reboot. If it doesn't work, do a full wipe and reflash the stable 4.4 kitkat firmware.
Also i hope you knew that getting xposed on lollipop to work is a bit more complicated than getting it to work on non samsung devices running lollipop. You will need to edit core-libart.jar and services.jar which is abit complicated if you don't have much knowledge of android previously.
Good morning, I have a Samsung S5 SM-G900h that is locked in the boot screen. The former owner tried to update the android to Lollipop, but did not know what he was doing and it now only comes into Download mode (not enter recovery mode). I've tried to go back to stock rom via Odin, but gives the error "There is not PIT Partition". I tried to rewrite with the PIT file, but gives the error "Failed Repartition". In last resort, I tried to erase the Nand, but neither worked. I've only had USB cable, door and computer, but all without success. I have a "junk" at hand?
Below is log Odin (already tried 3:07, 3:09, 3:10)
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900HXXU1ANG3_G900HOJV1ANG1_G900HXXU1ANG3_HOME.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> Erase...
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
the difference between the models S5 AT & T, Verizon, Sprint and T-Mobile? how to identify mine?
digaovaa said:
Good morning, I have a Samsung S5 SM-G900h that is locked in the boot screen.
Click to expand...
Click to collapse
Make a separate thread
---------- Post added at 14:37 ---------- Previous post was at 14:36 ----------
SkunkID said:
Classic case of bootlooping.
Recently used Flashfire to install rooted stock version of Lollipop 5.0. After trying to reinstall X-posed framework by flashing through flashfire, phone became bootlooped at At&t logo, remaining bricked after factory reseting and clearing cache.
Used odin to try and downgrade back to a stable version of 4.4 kickat. However, phone now bootloops after shuddering at samsung logo, before blipping to black screen with blue indicator light permently on. Trying to install current version of OTA rom through default recovery made no change. Suspecting bootloader my be root of issue, as trying to flash stock version of 4.4 bootloader in odin fails.
Currently looking for options to simple get phone back complete factor reset at this point. Links to other threads that have already solved this problem welcome.
Click to expand...
Click to collapse
Tried flashing stock Lollipop with ODIN?
If you bootloader is locked (AT&T likely is) then you'll be stuck with the Lollipop bootloader with no way to downgrade afaik

Soft Brick G900V using Odin Stuck in Recovery Mode

My GS5 G900V is stuck to recovery mode while I was trying to root. My mistake was I used odin to flash it back to a older version to try to root it and I did not did my research I know im a dummy. Now its Soft brick. I looked around and looked around to find answers but nothing seems to work for me. Ive tried using odin again to flash it back to the current firmware but Odin does not work.
It will be stuck on the Samsung GS5 screen and will go straight to recovery mode. Ive tried wiping cache and restore to factory settings still did not work. Tried taking out the battery for some time still did not work. I tried flashing through sd card still did not work.
This is the current log I have. Been trying different things since last night. Nothing works.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Found this link here but not sure how to use it: http://forum.xda-developers.com/showthread.php?t=2446269
I saw one thread with my similar problems. I think this is how they fixed it but I do not know how to do it. Can someone tell me how to use it? It will be greatly appreciated.
Thanks for all the help!
j0mz said:
My GS5 G900V is stuck to recovery mode while I was trying to root. My mistake was I used odin to flash it back to a older version to try to root it and I did not did my research I know im a dummy. Now its Soft brick. I looked around and looked around to find answers but nothing seems to work for me. Ive tried using odin again to flash it back to the current firmware but Odin does not work.
It will be stuck on the Samsung GS5 screen and will go straight to recovery mode. Ive tried wiping cache and restore to factory settings still did not work. Tried taking out the battery for some time still did not work. I tried flashing through sd card still did not work.
This is the current log I have. Been trying different things since last night. Nothing works.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Found this link here but not sure how to use it: http://forum.xda-developers.com/showthread.php?t=2446269
I saw one thread with my similar problems. I think this is how they fixed it but I do not know how to do it. Can someone tell me how to use it? It will be greatly appreciated.
Thanks for all the help!
Click to expand...
Click to collapse
What version (3 letter) are/were you on?
How I unbricked my phone was to do #4 in Notes in the first post: http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
BEWARE the warnings...you might be up the creek if you are on OE1 firmware
simplepinoi177 said:
What version (3 letter) are/were you on?
How I unbricked my phone was to do #4 in Notes in the first post: http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
BEWARE the warnings...you might be up the creek if you are on OE1 firmware
Click to expand...
Click to collapse
I believe mine was on OD5
I cant use flashfire because my phone is stuck on recovery mode. I cant get pass that.
j0mz said:
I believe mine was on OD5
I cant use flashfire because my phone is stuck on recovery mode. I cant get pass that.
Click to expand...
Click to collapse
you don't use flashfire...
I'm not saying to do the whole thing on the first post...just NUMBER #4 IN THE NOTES...
You use Odin and the file given to unbrick your phone back to NCG...
again, just go to NOTES and do #4 to unbrick the phone. You should be safe/fine if you are on OD5. Don't forget to root again and install a superuser...
Then you can go here to install whatever version you are interested in... http://forum.xda-developers.com/showthread.php?t=2784880
simplepinoi177 said:
you don't use flashfire...
I'm not saying to do the whole thing on the first post...just NUMBER #4 IN THE NOTES...
You use Odin and the file given to unbrick your phone back to NCG...
again, just go to NOTES and do #4 to unbrick the phone. You should be safe/fine if you are on OD5. Don't forget to root again and install a superuser...
Then you can go here to install whatever version you are interested in... http://forum.xda-developers.com/showthread.php?t=2784880
Click to expand...
Click to collapse
I tried it but Odin cant find it. Its a rar file?
Stuck in recovery mode loop. SM-G900V Verizon G900VVRU2BOG5
Im in the exact same situation... i have been literally sitting in front of my PC for hours on end to try and resolve this issue. I cant get back my current firmware now even. Just stuck on the recovery mode. I flashed NCG kernal and it went through as normal, however, all it does not is after the samsung loading sign it goes back into system recovery. I have tried everything from cache wipe to factory reset, system reboot, everything! it just does the same thing - goes back into recovery mode- it is getting really frustrating for me. I would really appreciate it if someone could tell me exactly how to get out of it and use the phone as normal again.
I am on sm-g900v
G900VVRU2BOG5
Verizon mobile S5
I have tried to flash almost all the available ROMS and nothing works everytime this come up: ( i am using the latest Kies drivers, Odin 3.10.6, etc)..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1ANCG_G900VVZW1ANCG_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1005)..
<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> Get PIT for mapping.. - - i have the pit file and if i use it to flash i get the same output failed completion.
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
PLEASE HELP. THANK YOU.
Tried rooting my SM-G900V. I managed to flash a kernel on it, but kept getting "FAIL!" in Odin when I tried flashing a custom rom. Even after I flashed a kernel on my phone still worked fine. One day it said some nonsense about securtiy updates, I clicked on it and BOOM. Stock OS, GONE. Kernel, GONE. It started giving me a message "use Verizon recovery assistant" I tried getting the program, no dice. I don't have root and I'm on the latest version of lolipop that they have released for the SM-G900V.
CAN ANYONE HELP, PLEASE. IF MY MOM KNEW I WAS MESSING WITH MY PHONE SHE'D KILL ME. SHE THINKS I'VE BEEN CHARGING IT FOR 3 DAYS!!!
m0bk3yn1nj4 said:
Tried rooting my SM-G900V. I managed to flash a kernel on it, but kept getting "FAIL!" in Odin when I tried flashing a custom rom. Even after I flashed a kernel on my phone still worked fine. One day it said some nonsense about securtiy updates, I clicked on it and BOOM. Stock OS, GONE. Kernel, GONE. It started giving me a message "use Verizon recovery assistant" I tried getting the program, no dice. I don't have root and I'm on the latest version of lolipop that they have released for the SM-G900V.
CAN ANYONE HELP, PLEASE. IF MY MOM KNEW I WAS MESSING WITH MY PHONE SHE'D KILL ME. SHE THINKS I'VE BEEN CHARGING IT FOR 3 DAYS!!!
Click to expand...
Click to collapse
can you boot into download mode? if go here http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784 and flash the full NCG tar then re root your device remember you always wanna flash ni2 kernal or nk2 then flash the rom then the kernal that works with your rom never flash the kernel that works with your rom before you flash the rom
m0bk3yn1nj4 said:
Tried rooting my SM-G900V. I managed to flash a kernel on it, but kept getting "FAIL!" in Odin when I tried flashing a custom rom. Even after I flashed a kernel on my phone still worked fine. One day it said some nonsense about securtiy updates, I clicked on it and BOOM. Stock OS, GONE. Kernel, GONE. It started giving me a message "use Verizon recovery assistant" I tried getting the program, no dice. I don't have root and I'm on the latest version of lolipop that they have released for the SM-G900V.
CAN ANYONE HELP, PLEASE. IF MY MOM KNEW I WAS MESSING WITH MY PHONE SHE'D KILL ME. SHE THINKS I'VE BEEN CHARGING IT FOR 3 DAYS!!!
Click to expand...
Click to collapse
If you were on the latest version of Lollipop and were not yet rooted, you cannot root your phone, flash custom ROMs, and I don't think you can flash kernels. You need to get your hands on a full ODIN stock tar file for the build your phone was on. OG5 is available, but I don't think the OK3 file is available yet. If you took an update in the past 2 or 3 days prior to trying this, you are stuck for a while with no way out. If you did not take an update on your phone in the past 2 or 3 days, look for the OG5 full stock ODIN file to flash to your phone.
---------- Post added at 05:36 PM ---------- Previous post was at 05:34 PM ----------
Veid71 said:
can you boot into download mode? if go here http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784 and flash the full NCG tar then re root your device remember you always wanna flash ni2 kernal or nk2 then flash the rom then the kernal that works with your rom never flash the kernel that works with your rom before you flash the rom
Click to expand...
Click to collapse
He said he was on the latest Lollipop version when he tried to root. If so, he cannot flash the NCG file. He wasn't already rooted, he was trying to root on the latest Lollipop build which can't be done at this time.
landshark68 said:
If you were on the latest version of Lollipop and were not yet rooted, you cannot root your phone, flash custom ROMs, and I don't think you can flash kernels. You need to get your hands on a full ODIN stock tar file for the build your phone was on. OG5 is available, but I don't think the OK3 file is available yet. If you took an update in the past 2 or 3 days prior to trying this, you are stuck for a while with no way out. If you did not take an update on your phone in the past 2 or 3 days, look for the OG5 full stock ODIN file to flash to your phone.
---------- Post added at 05:36 PM ---------- Previous post was at 05:34 PM ----------
He said he was on the latest Lollipop version when he tried to root. If so, he cannot flash the NCG file. He wasn't already rooted, he was trying to root on the latest Lollipop build which can't be done at this time.
Click to expand...
Click to collapse
ah okay i see then his post was kinda confusing
I don't know how to do that ODIN stuff, is there a video guide out or something?
landshark68 said:
If you were on the latest version of Lollipop and were not yet rooted, you cannot root your phone, flash custom ROMs, and I don't think you can flash kernels. You need to get your hands on a full ODIN stock tar file for the build your phone was on. OG5 is available, but I don't think the OK3 file is available yet. If you took an update in the past 2 or 3 days prior to trying this, you are stuck for a while with no way out. If you did not take an update on your phone in the past 2 or 3 days, look for the OG5 full stock ODIN file to flash to your phone.
Click to expand...
Click to collapse
I have no idea what any of this means. Please, can you help me?!
m0bk3yn1nj4 said:
I don't know how to do that ODIN stuff, is there a video guide out or something?
Click to expand...
Click to collapse
m0bk3yn1nj4 said:
I have no idea what any of this means. Please, can you help me?!
Click to expand...
Click to collapse
No offense intended, but if you don't know how to use ODIN and you don't have any idea what any of what I wrote means, you shouldn't be trying to root your phone without understanding all of it. I'm not aware of a video guide for using ODIN but I'd be willing to bet you could probably find one on youtube. If you can't find a video guide, found in post #4 of this thread is an old picture guide that should give you a pretty good understanding of using ODIN:
http://forum.androidcentral.com/ver...=1.251820425.1215152510.1443888191#post542513
I believe the PDA button is now called the AP button. Follow the video guide you found or the attached picture guide and flash the full BOG5 ODIN tar file found in this thread:
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
There may even be a guide for using ODIN found here at XDA if you dig around some. Not sure.
landshark68 said:
No offense intended, but if you don't know how to use ODIN and you don't have any idea what any of what I wrote means, you shouldn't be trying to root your phone without understanding all of it. I'm not aware of a video guide for using ODIN but I'd be willing to bet you could probably find one on youtube. If you can't find a video guide, found in post #4 of this thread is an old picture guide that should give you a pretty good understanding of using ODIN:
http://forum.androidcentral.com/ver...=1.251820425.1215152510.1443888191#post542513
I believe the PDA button is now called the AP button. Follow the video guide you found or the attached picture guide and flash the full BOG5 ODIN tar file found in this thread:
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
There may even be a guide for using ODIN found here at XDA if you dig around some. Not sure.
Click to expand...
Click to collapse
Much obliged
simplepinoi177 said:
What version (3 letter) are/were you on?
How I unbricked my phone was to do #4 in Notes in the first post: http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
BEWARE the warnings...you might be up the creek if you are on OE1 firmware
Click to expand...
Click to collapse
i have a sm-g900v BOG5. i bricked mine phone so i tried #4 as you said and get FAIL! in Odin. am i doing something wrong?
rachelrgr said:
i have a sm-g900v BOG5. i bricked mine phone so i tried #4 as you said and get FAIL! in Odin. am i doing something wrong?
Click to expand...
Click to collapse
You can grab the stock firmware, either OG5. OK3, or PB1 (newest), and flash with odin in the AP slot, I also recommend grabbing the PIT file (goes in the PIT slot). If you want root, then just go ahead and grab the PB1 and follow the directions on this link.
Firmware Link: http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370

Categories

Resources