Related
Hello,
I am relatively new to this and clearly making some mistakes, from what I have found on these forums I can't see anyone else having the same issues with this device. Any help would be greatly appreciated. So here goes:
I recently tried installing SHOstock's rom, everything appeared successful and the phone began to boot, but hung on the samsung logo with the padlock for 10+ minutes. I tried to reboot, same thing. When booting back into recovery to do a wipe and give it another shot, I was prompted for a password (which I did not set up). So I decided I had probably screwed something up and tried to flash back to stock with Odin. Odin failed, and now all I can get is "Firmware upgrade encountered an issue..." I get this even when trying to enter recovery. I've tried connecting to Kies as well, but no such luck, as it doesn't connect to the device.Currently working on downloading another copy of the stock software to try with Odin again.
Any help is appreciated,
Thanks
What S4 do you have( model#)?
Are you sure you are using the correct firmware?
Are you sure the Kernel and ROM you tried to install were correct for your phone?
Did ODIN recognize your phone or did it fail during / after installation? Was there a specific message?
Re-downloading is good (you said you were doing that now) just to make sure it wasn't a bad download.
scott14719 said:
What S4 do you have( model#)?
Are you sure you are using the correct firmware?
Are you sure the Kernel and ROM you tried to install were correct for your phone?
Did ODIN recognize your phone or did it fail during / after installation? Was there a specific message?
Re-downloading is good (you said you were doing that now) just to make sure it wasn't a bad download.
Click to expand...
Click to collapse
First, thank you for the quick response.
After redownloading from a different source, Odin's flash passed this time, and after a factory reset I am back in. Thank you again for the help.
Alright, Lemme lay it out for you guys.
I rooted my phone about 3 weeks ago, and then unrooted it because, even though I'm learning, I didn't see the point in having root because I didn't want to brick my device. So along comes the update (I337UCUAMF3). I downloaded and installed it and at the end it told me that it failed (I'm not sure why, my device status was "Official"), although I noticed several changes in the UI including the status bar on the top of the screen being transparent instead of black. It was working, although I still wanted to flash to stock. I had rooted and changed a font that I wanted to change back, and so I tried flashing it (with Odin 3.07) and got an error (put it into "downloading..." mode, the error reads "SW REV. CHECK FAIL : fused : 2 , Binary : 1". I restarted it and it got stuck on the AT&T logo. I tried to flash it again and this time I tried to do it with Kies and now it's stuck on the Kies error "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." If any of you need pictures I can produce them. Can ANYONE help me figure this out. I'm a tech and so when I find a problem, I can't stop working on it until I fix it. I got 2 hours of sleep last night because of this, took a vacation day from work, and I just want to fix it. Thank you in advance for all of your guys help!!
P.S. If I don't take the battery out, it won't turn off. I think it's called a bootloop. If I try T Flash on Odin, I get an error message that says "Not found boot image in sdcard". I have a boot.img on my sdcard, but I'm not sure if it's in root because I can't get into my phone to get to my file explorer.
You might try to Wipe Data/Factory Reset from recovery mode (hold Vol_up while it reboot).
then do odin or kies again. I am not saying it's fix ,but nothing to lose to try.
pakxelaos said:
You might try to Wipe Data/Factory Reset from recovery mode (hold Vol_up while it reboot).
then do odin or kies again. I am not saying it's fix ,but nothing to lose to try.
Click to expand...
Click to collapse
I've tried to get into recovery mode. My device just says "Odin. Could not boot into normal recovery mode"
You need to read and search...
http://forum.xda-developers.com/showthread.php?t=2360859
This sounds like the same issue.
scott14719 said:
You need to read and search...
http://forum.xda-developers.com/showthread.php?t=2360859
This sounds like the same issue.
Click to expand...
Click to collapse
Might be. It didn't come up in ANY of the searches I did on the issue. Trust me. I looked for a long while for this. Maybe I just wasn't looking for the right thing. Sorry for cluttering the forum.
That fixed one problem, but I'm still stuck at AT&T splash screen...
circasurvives said:
That fixed one problem, but I'm still stuck at AT&T splash screen...
Click to expand...
Click to collapse
Can you access recovery via 3 button method?
ou812bkewl said:
Can you access recovery via 3 button method?
Click to expand...
Click to collapse
No i still get the "Downloading..." screen.
Unfortunately you may be stuck.
In most normal circumstances, you can put your phone into Odin / Download mode by holding Volume Down as you power on the phone. (Recovery is Volume Up and Power). Once in Odin mode, you would launch the Odin application (Odin v3.07 is latest). You would also make sure the Samsung drivers are installed. Then you'd open Odin, and click on PDA and select a odin md5 file which contains every partition basically your phone uses, recovery, system, data, etc, as they were from factory. (Found here http://samsung-updates.com/device/?id=SGH-I337 )If it doesn't boot from there, it should then allow you to boot recovery and you can go to wipe data/factory reset, then the device would boot.
The only issue is that only "AMDB" and "AMDL" firmware is available as a Odin package. AMF3 is not. And if AMF3 is installed, it updates the bootloader on the device. Odin checks the bootloader on the device before it flashes everything, and if it's a newer version than what it's trying to flash (Ex if you try flashing AMDL, and AMF3 is already applied), then it will error out and not work.
Kies is hit and miss. People were restoring through Kies, not sure how. I usually avoid Kies myself. You can try putting the phone into Download Mode and hooking it up to Kies from there and see what happens.
So: You can try Odin, however if the AMF3 bootloader was applied then you're out of luck there until a AMF3 Odin package is out.
WoodburyMan said:
Unfortunately you may be stuck.
In most normal circumstances, you can put your phone into Odin / Download mode by holding Volume Down as you power on the phone. (Recovery is Volume Up and Power). Once in Odin mode, you would launch the Odin application (Odin v3.07 is latest). You would also make sure the Samsung drivers are installed. Then you'd open Odin, and click on PDA and select a odin md5 file which contains every partition basically your phone uses, recovery, system, data, etc, as they were from factory. (Found here http://samsung-updates.com/device/?id=SGH-I337 )If it doesn't boot from there, it should then allow you to boot recovery and you can go to wipe data/factory reset, then the device would boot.
The only issue is that only "AMDB" and "AMDL" firmware is available as a Odin package. AMF3 is not. And if AMF3 is installed, it updates the bootloader on the device. Odin checks the bootloader on the device before it flashes everything, and if it's a newer version than what it's trying to flash (Ex if you try flashing AMDL, and AMF3 is already applied), then it will error out and not work.
Kies is hit and miss. People were restoring through Kies, not sure how. I usually avoid Kies myself. You can try putting the phone into Download Mode and hooking it up to Kies from there and see what happens.
So: You can try Odin, however if the AMF3 bootloader was applied then you're out of luck there until a AMF3 Odin package is out.
Click to expand...
Click to collapse
Is there a way to flash another bootloader? I know that it's an option in Odin 3.07...
circasurvives said:
Is there a way to flash another bootloader? I know that it's an option in Odin 3.07...
Click to expand...
Click to collapse
Nope. Odin as part of PDA tries to flash the Bootloader. The Bootloader button is the same, but for Bootloader only as opposed to the entire system.
If your patient and can wait someone may come out with a unlock tool for AMF3, or another work around, or a Odin image of AMF3. May be a while though. There are more advanced users on here besides myself that may have insite that may allow you to get back on AMF3 stock images but to my knowledge you're stuck without a AMF3 odin image.
You could always go to your carrier store and say "The phone updated the other day and now wont boot after the update". It's the truth. See what they say.
---------- Post added at 04:53 PM ---------- Previous post was at 04:46 PM ----------
This may help? http://forum.xda-developers.com/showthread.php?t=2360859
WoodburyMan said:
Nope. Odin as part of PDA tries to flash the Bootloader. The Bootloader button is the same, but for Bootloader only as opposed to the entire system.
If your patient and can wait someone may come out with a unlock tool for AMF3, or another work around, or a Odin image of AMF3. May be a while though. There are more advanced users on here besides myself that may have insite that may allow you to get back on AMF3 stock images but to my knowledge you're stuck without a AMF3 odin image.
You could always go to your carrier store and say "The phone updated the other day and now wont boot after the update". It's the truth. See what they say.
---------- Post added at 04:53 PM ---------- Previous post was at 04:46 PM ----------
This may help? http://forum.xda-developers.com/showthread.php?t=2360859
Click to expand...
Click to collapse
Well I went to AT&T and had to order a replacement because I "lost" my other one lol. I have my new one and I was going to update it because I have no interest in rooting this one (I was hoping to wait until the other problem got solved by someone and make that one my test device.) and I wanted the extra LTE bands that MF3 provides. Alas, there isn't a software update available. Did AT&T pull I337UCUAMF3 off the market? If not, do you know why I wouldn't be able to see it?
circasurvives said:
Well I went to AT&T and had to order a replacement because I "lost" my other one lol. I have my new one and I was going to update it because I have no interest in rooting this one (I was hoping to wait until the other problem got solved by someone and make that one my test device.) and I wanted the extra LTE bands that MF3 provides. Alas, there isn't a software update available. Did AT&T pull I337UCUAMF3 off the market? If not, do you know why I wouldn't be able to see it?
Click to expand...
Click to collapse
Well. That's one way to do it. Just buying another phone outright. Eventually a odin image for AMF3 will be released and you can unbrick the old one.
AMF3 is still out there. Sometimes takes a day or two for phone to see the update.
You can flash AMF3 modem while still keeping the Loki-vulnerable AMDL bootloader. That's what I did. I did get some gain and speed on LTE and a little better signal strength (maybe placebo effect) from the AMF3 modem.
IMHO on the new phone I would root and run Goldeneye...Keep AMDL bootloader. Goldeneye is the same as AMF3 stock firmware essentially, but sped up, and you can run it without updating the AMF3 bootloader.
Run Loki / TWRP / Motochopper tool: http://forum.xda-developers.com/showthread.php?t=2297900
Flash AMF3 modem only from recovery from this post (assuming you have AT&T SGH-I337): http://forum.xda-developers.com/showthread.php?p=43432287#post43432287
Install Goldeneye Rom Zip: from recovery: http://forum.xda-developers.com/showthread.php?t=2313469
or instead of Goldeneye.. a rooted zipaligned version of MF3 update someone made that doesn't patch the bootloader http://forum.xda-developers.com/showthread.php?t=2364635
WoodburyMan said:
Well. That's one way to do it. Just buying another phone outright. Eventually a odin image for AMF3 will be released and you can unbrick the old one.
AMF3 is still out there. Sometimes takes a day or two for phone to see the update.
You can flash AMF3 modem while still keeping the Loki-vulnerable AMDL bootloader. That's what I did. I did get some gain and speed on LTE and a little better signal strength (maybe placebo effect) from the AMF3 modem.
IMHO on the new phone I would root and run Goldeneye...Keep AMDL bootloader. Goldeneye is the same as AMF3 stock firmware essentially, but sped up, and you can run it without updating the AMF3 bootloader.
Run Loki / TWRP / Motochopper tool: http://forum.xda-developers.com/showthread.php?t=2297900
Flash AMF3 modem only from recovery from this post (assuming you have AT&T SGH-I337): http://forum.xda-developers.com/showthread.php?p=43432287#post43432287
Install Goldeneye Rom Zip: from recovery: http://forum.xda-developers.com/showthread.php?t=2313469
or instead of Goldeneye.. a rooted zipaligned version of MF3 update someone made that doesn't patch the bootloader http://forum.xda-developers.com/showthread.php?t=2364635
Click to expand...
Click to collapse
Where can I find Goldeneye?
circasurvives said:
Where can I find Goldeneye?
Click to expand...
Click to collapse
Dude the links right there in the post lol
WoodburyMan said:
Dude the links right there in the post lol
Click to expand...
Click to collapse
Lol I noticed that after I said it hahaha
I'm kinda nervous to do anything after I bricked my last one.
Bricking seems a bit troublesome but from what I have read it's pretty tough to do if instructions are followed and even if not - best of luck.
WoodburyMan said:
Well. That's one way to do it. Just buying another phone outright. Eventually a odin image for AMF3 will be released and you can unbrick the old one.
AMF3 is still out there. Sometimes takes a day or two for phone to see the update.
You can flash AMF3 modem while still keeping the Loki-vulnerable AMDL bootloader. That's what I did. I did get some gain and speed on LTE and a little better signal strength (maybe placebo effect) from the AMF3 modem.
IMHO on the new phone I would root and run Goldeneye...Keep AMDL bootloader. Goldeneye is the same as AMF3 stock firmware essentially, but sped up, and you can run it without updating the AMF3 bootloader.
Run Loki / TWRP / Motochopper tool: http://forum.xda-developers.com/showthread.php?t=2297900
Flash AMF3 modem only from recovery from this post (assuming you have AT&T SGH-I337): http://forum.xda-developers.com/showthread.php?p=43432287#post43432287
Install Goldeneye Rom Zip: from recovery: http://forum.xda-developers.com/showthread.php?t=2313469
or instead of Goldeneye.. a rooted zipaligned version of MF3 update someone made that doesn't patch the bootloader http://forum.xda-developers.com/showthread.php?t=2364635
Click to expand...
Click to collapse
Does anyone know where to find an Odin MF3 ROM?
Please don't make multiple threads on the same thing, not good for business.
So, I was going to install a Lollipop rom and I thought I followed directions correctly but it gets stuck at the "Powered by Android" very first screen. Booting into recovery gets me into the simple manual recovery mode and not safestrap. Odin also doesn't seem to recognize that I've connected my phone - although maybe there's a special way to do it?
I basically need help getting my phone working again. I've dug around but everything seems focused around using Odin and I don't know how to get that to see my phone in the state that it's in.
Help!
So, reasons I am dumb #1: I had no idea what the key combo to boot into Odin was (volume down+home+power) So, now I can get to Odin and I'll try to figure it out from here unless someone jumps in with something before I do.
Sheesh. Sigh.
im in need of help myself as I went to root my sm-g900v and now am stuck in bootloop.. how do i fix this? no matter what I do to get it to restart, same result....
rlo5ca said:
im in need of help myself as I went to root my sm-g900v and now am stuck in bootloop.. how do i fix this? no matter what I do to get it to restart, same result....
Click to expand...
Click to collapse
From Download Mode, just flash a stock ROM. If you hadn't rooted yet, you can use Kies 3, from Samsung, to reset your phone to newest ROM, correcting any issues. Verizon also has a Software Repair tool you can try, but I like Kies better. All the info you need is in the stickies.
Hi all,
So I've decided to root my Exynos International Galaxy Note 3 (SM-N900) using Chainfire's CF-Auto-Root. All went well until Odin got stuck at cache.img, then fails after a couple of minutes. I unplug the phone and restart it, it then displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" whenever I try to boot. I can access download mode again, but not recovery. My phone is stock 4.2.2.
It's the first time I have such a problem, I flashed a couple of phones before without any trouble. I searched XDA for a solution and tried other Odin versions, different cable/ports, even tried on another computer: Same issue. Stuck at cache.img. I can't get my phone to work again. Some people suggested it might have something to do with USB debugging, but I can't remember if I left it enabled or disabled.
I didn't back any of my data (I didn't expect the root to fail...) and retrieving my phone, rooted or not, is of the utmost importance. Please avoid posting solutions that involve data loss.
Feel free to ask about anything I might have left out.
Thanks!
GST_Diandre said:
Hi all,
So I've decided to root my Exynos International Galaxy Note 3 (SM-N900) using Chainfire's CF-Auto-Root. All went well until Odin got stuck at cache.img, then fails after a couple of minutes. I unplug the phone and restart it, it then displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" whenever I try to boot. I can access download mode again, but not recovery. My phone is stock 4.2.2.
It's the first time I have such a problem, I flashed a couple of phones before without any trouble. I searched XDA for a solution and tried other Odin versions, different cable/ports, even tried on another computer: Same issue. Stuck at cache.img. I can't get my phone to work again. Some people suggested it might have something to do with USB debugging, but I can't remember if I left it enabled or disabled.
I didn't back any of my data (I didn't expect the root to fail...) and retrieving my phone, rooted or not, is of the utmost importance. Please avoid posting solutions that involve data loss.
Feel free to ask about anything I might have left out.
Thanks!
Click to expand...
Click to collapse
I think you'll have to flash an official Sammy Firmware to get past the error, although if you look in the Note 3 Android Development, I recall seeing some deodexed, rooted firmware that is supposed to work from Odin. Not sure if any of them are for exynos version though.
Data? I keep everything I can on the extSD for exactly this reason. You should be able to remove the card and put it in a card caddy and read it in a PC and copy out your media etc. The root process shouldn't have overwritten anything you need.
For rooting, maybe DL the SuperSU zip file Chainfire's website and flash it in Recovery once you're up and running? I use TWRP but Philz or CWM recoveries will do it.
Journyman16 said:
I think you'll have to flash an official Sammy Firmware to get past the error, although if you look in the Note 3 Android Development, I recall seeing some deodexed, rooted firmware that is supposed to work from Odin. Not sure if any of them are for exynos version though.
Data? I keep everything I can on the extSD for exactly this reason. You should be able to remove the card and put it in a card caddy and read it in a PC and copy out your media etc. The root process shouldn't have overwritten anything you need.
For rooting, maybe DL the SuperSU zip file Chainfire's website and flash it in Recovery once you're up and running? I use TWRP but Philz or CWM recoveries will do it.
Click to expand...
Click to collapse
I see. So in newbie terms, if I flash the official firmware I have from SamMobile, I should have my phone back running with all my apps & data? Also, any hint about why rooting didn't work in the first place?
After this tragic experience with Odin, I'm gonna forget root for now, maybe update to Lollipop then think about rooting again.
Thanks for replying !
GST_Diandre said:
I see. So in newbie terms, if I flash the official firmware I have from SamMobile, I should have my phone back running with all my apps & data? Also, any hint about why rooting didn't work in the first place?
After this tragic experience with Odin, I'm gonna forget root for now, maybe update to Lollipop then think about rooting again.
Thanks for replying !
Click to expand...
Click to collapse
Did the official firmware work when you did it? If so, download Phone INFO Samsung from Play and use it to check what hardware you actually have.
I have had issues with CF-Auto root recently so I flash Stock, then the TWRP md5 file (in Odin 3.09) then I boot into Recovery and flash SuperSU. That gives me Recovery and root. You normally have to run SuperSU when you start so it can update.
U[pdating to LP is a good idea - most of the things going on in Dev are now LP versions.
Journyman16 said:
Did the official firmware work when you did it? If so, download Phone INFO Samsung from Play and use it to check what hardware you actually have.
I have had issues with CF-Auto root recently so I flash Stock, then the TWRP md5 file (in Odin 3.09) then I boot into Recovery and flash SuperSU. That gives me Recovery and root. You normally have to run SuperSU when you start so it can update.
U[pdating to LP is a good idea - most of the things going on in Dev are now LP versions.
Click to expand...
Click to collapse
I didn't flash the official firmware ever. Before trying to root with Odin and getting it stuck, I never flashed or modified anything internally on this phone.
Obviously, I can't use Phone INFO because my phone is stuck at BSOD.
I will upgrade to Lollipop, once I can get my phone working as it was. For now I'm still hesitating to flash the official firmware. I don't know if that would wipe the apps or just get back the phone as it was.
GST_Diandre said:
I didn't flash the official firmware ever. Before trying to root with Odin and getting it stuck, I never flashed or modified anything internally on this phone.
Obviously, I can't use Phone INFO because my phone is stuck at BSOD.
I will upgrade to Lollipop, once I can get my phone working as it was. For now I'm still hesitating to flash the official firmware. I don't know if that would wipe the apps or just get back the phone as it was.
Click to expand...
Click to collapse
It will wipe Apps and Data - it makes your phone like you just bought it.
I didn't realise it was stuck in that mode - just thought that happened whenever you tried to flash something.
First thing. Turn phone off. Take back off and remove battery for 10 secs or so. Turn it on holding down Vol Down + Home + Power - release when DL screen shows and press Vol Down. If that gets you into the phone, spend some time saving your data to extSD.
I use Call Logs Backup & Restore, SMS Backup & Restore, I export my Contacts to ext storage. I use TiBu to backup all my apps to a folder on extSDCard. If you are on Stock ROM, you should be able to set your camera to save to extSDCard but you need a file explorer (I use ES File Explorer) to copy your current DCIM folder across - other than that, look for music, documents and video folders on internal memory)
If it doesn't open the phone for you, & your data is important, take card out and use adapter to save data onto a computer.
Go to Sammobile and download the proper official firmware for your phone - note you need to set up a free account before you can DL.
Download Odin 3.09 Run Odin
Then repeat the phone process but this time press Vol Up when at the DL screen. It is important to have the phone Off and electrically flat before attempting a firmware update.
Connect phone to PC - Odin should recognise it. If it doesn't you probably need the Samsung USB Drivers so get them and install them.
Then connect phone again. Click AP and find your DL from Sammobile. Wait for it to load then press Start. Wait... it will reboot and usually sits on the logo for quite some time.
Set up your phone, and restore or reinstall your apps.
Rotsa Ruck!
Journyman16 said:
It will wipe Apps and Data - it makes your phone like you just bought it.
I didn't realise it was stuck in that mode - just thought that happened whenever you tried to flash something.
First thing. Turn phone off. Take back off and remove battery for 10 secs or so. Turn it on holding down Vol Down + Home + Power - release when DL screen shows and press Vol Down. If that gets you into the phone, spend some time saving your data to extSD.
I use Call Logs Backup & Restore, SMS Backup & Restore, I export my Contacts to ext storage. I use TiBu to backup all my apps to a folder on extSDCard. If you are on Stock ROM, you should be able to set your camera to save to extSDCard but you need a file explorer (I use ES File Explorer) to copy your current DCIM folder across - other than that, look for music, documents and video folders on internal memory)
If it doesn't open the phone for you, & your data is important, take card out and use adapter to save data onto a computer.
Go to Sammobile and download the proper official firmware for your phone - note you need to set up a free account before you can DL.
Download Odin 3.09 Run Odin
Then repeat the phone process but this time press Vol Up when at the DL screen. It is important to have the phone Off and electrically flat before attempting a firmware update.
Connect phone to PC - Odin should recognise it. If it doesn't you probably need the Samsung USB Drivers so get them and install them.
Then connect phone again. Click AP and find your DL from Sammobile. Wait for it to load then press Start. Wait... it will reboot and usually sits on the logo for quite some time.
Set up your phone, and restore or reinstall your apps.
Rotsa Ruck!
Click to expand...
Click to collapse
Thank you, I just tried going into download mode and pressing vol down, still get the same BSOD. I guess that means phone cannot be recovered as it is...
I'm backing up my stuff now. I have no problem backing up contacts/SMS/etc.., but can you tell me whether I can still back up applications and restore them as they were using Titanium Backup on PC ? I know this should have been done before even soft-bricking my phone, but since it inaccessible to run the app on it...
I already have the official firmware waiting to be installed, just need to be sure about TiBU and that I backed up everything correctly Thanks for answering !
GST_Diandre said:
Thank you, I just tried going into download mode and pressing vol down, still get the same BSOD. I guess that means phone cannot be recovered as it is...
I'm backing up my stuff now. I have no problem backing up contacts/SMS/etc.., but can you tell me whether I can still back up applications and restore them as they were using Titanium Backup on PC ? I know this should have been done before even soft-bricking my phone, but since it inaccessible to run the app on it...
I already have the official firmware waiting to be installed, just need to be sure about TiBU and that I backed up everything correctly Thanks for answering !
Click to expand...
Click to collapse
That depends... TiBu can only recover what you've saved (obvious I know...) and only if it didn't get wiped in the new firmware flash. (which it will if you didn't choose extSDCard for the backups)
Other than that, once your phone is set up and your Google account active, Play Store will DL all your apps.
Journyman16 said:
That depends... TiBu can only recover what you've saved (obvious I know...) and only if it didn't get wiped in the new firmware flash. (which it will if you didn't choose extSDCard for the backups)
Other than that, once your phone is set up and your Google account active, Play Store will DL all your apps.
Click to expand...
Click to collapse
Okay great So where exactly do I get TiBu for pc?
GST_Diandre said:
Okay great So where exactly do I get TiBu for pc?
Click to expand...
Click to collapse
Unfortunately it's a Play Store app, so first you have to get your phone working.
You could try the attached from Recovery but I have no idea if it would work as it's from my rooted CM12.1 system.
Journyman16 said:
Unfortunately it's a Play Store app, so first you have to get your phone working.
You could try the attached from Recovery but I have no idea if it would work as it's from my rooted CM12.1 system.
Click to expand...
Click to collapse
Recovery isn't working for me... The only thing I can access on the phone is Download mode.
I guess it's lost? :/
GST_Diandre said:
Recovery isn't working for me... The only thing I can access on the phone is Download mode.
I guess it's lost? :/
Click to expand...
Click to collapse
The only other thing I can think of would be using ADB over USB but I don't know if that would work with DL mode or if it is only for Recovery. You'd have to search and learn how to use it.
So maybe time to just get the phone working and make sure for future you have backups?
Journyman16 said:
The only other thing I can think of would be using ADB over USB but I don't know if that would work with DL mode or if it is only for Recovery. You'd have to search and learn how to use it.
So maybe time to just get the phone working and make sure for future you have backups?
Click to expand...
Click to collapse
SOLVED. I can't believe how easy it was. I was about to flash it over from scratch but then it struck me.
Chainfire ships Odin with all its root bundles, a version where you cannot untick "Auto Reboot". Because of Auto Reboot being ticked, Odin freezes at "cache.img". It might not freeze for some people but for me, having Auto Reboot activated causes the freeze
Downloading a different version of Odin (any version, I used 3.09) that allows changing parameters and LEAVING EVERYTHING UNTICKED BUT F. RESET TIME works like a charm.
Don't forget to reboot your phone after Odin displays PASS or RESET (Long press power).
I'm going to PM Chainfire about this, and tell a max of people about it.
Thank you for your support
EDIT: Also going to NANDroid my phone. I'm tired of panicking over failed roots
so samsung has reps at most best buys that will help you free of charge ( i had to go there when i first started rooting because i softbricked my phone and had no idea what to do and needed it the next day so if you dont feel like waiting or need something done that second or just dont wanna post on here you can always head up there and just tellem your question and theyll try and help you with what you need
Veid71 said:
so samsung has reps at most best buys that will help you free of charge ( i had to go there when i first started rooting because i softbricked my phone and had no idea what to do and needed it the next day so if you dont feel like waiting or need something done that second or just dont wanna post on here you can always head up there and just tellem your question and theyll try and help you with what you need
Click to expand...
Click to collapse
Thank you for your post. I soft bricked my S5 (bootloop) and will keep this in mind. For now I am at home and want to see if I can figure it myself. I need help to push a working ROM to my device SD card. I found a toolkit on root page http://forum.xda-developers.com/showpost.php?p=64744448&postcount=2
***Is there a tutorial that can help me know how to use the toolkit?
cyberfem said:
Thank you for your post. I soft bricked my S5 (bootloop) and will keep this in mind. For now I am at home and want to see if I can figure it myself. I need help to push a working ROM to my device SD card. I found a toolkit on root page http://forum.xda-developers.com/showpost.php?p=64744448&postcount=2
***Is there a tutorial that can help me know how to use the toolkit?
Click to expand...
Click to collapse
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
check that out if you werent previously rooted if you were previously rooted then try this
Use Odin to flash the lollipop kernel you were using. Then go into the stock recovery (hold Home + Vol UP and Power) and clear the cache and reboot. If that doesn't work, go back into the stock recovery, clear cache and select factory reset, then reboot. That should allow MOAR (whatever rom you want i stole this post from one of my other topics about when i softbricked mine) to boot, then you can reinstall SafeStrap Lollipop.
If you're getting any kind of logo screen showing up on boot, you are only "soft" bricked (not "hard" or permanently bricked) and you can fix it easily.
If you're only getting a logo, try what Veid71 said in the post above mine. If that doesn't work, then worst case you just need to flash a factory restore image with Odin and start over.
A word of caution, though: if your firmware version was updated to BOE1, BOG5, BOK3, do NOT flash an earlier factory image or you will brick because after BOD the bootloader was locked and you can't downgrade it.
painiac said:
If you're getting any kind of logo screen showing up on boot, you are only "soft" bricked (not "hard" or permanently bricked) and you can fix it easily.
If you're only getting a logo, try what Veid71 said in the post above mine. If that doesn't work, then worst case you just need to flash a factory restore image with Odin and start over.
A word of caution, though: if your firmware version was updated to BOE1, BOG5, BOK3, do NOT flash an earlier factory image or you will brick because after BOD the bootloader was locked and you can't downgrade it.
Click to expand...
Click to collapse
I get the logo screen like it is turning on then it goes to recovery mode options. I can get to Download mode and Odin has a blue port connection but my Win8 and Win7 PCs do not see the device at all, so I cant' flash in Odin. Background - I attempted to root using jrkruse method and got stuck and never rooted. Anyone know a way around this maybe using the external SD card?
cyberfem said:
I get the logo screen like it is turning on then it goes to recovery mode options. I can get to Download mode and Odin has a blue port connection but my Win8 and Win7 PCs do not see the device at all, so I cant' flash in Odin. Background - I attempted to root using jrkruse method and got stuck and never rooted. Anyone know a way around this maybe using the external SD card?
Click to expand...
Click to collapse
When it boots into the recovery mode options, try clearing cache and then reboot. If that doesn't work, do it again, clearing cache and also factory reset. That may allow your phone to boot back up normally.
The SDcard Unbrick method is only needed if your phone cannot boot into Download mode. In this case, it wouldn't help you because your phone is functioning in that regard.
When you have the phone in Download mode, your computer won't show it as a device in "My Computer" because it's not connected as a media device., but software that knows how to look for it can see it. If Odin is lighting up blue in the first ID:COM box, it IS seeing the phone and you will be able to flash to it.
If you're to a point where you need to flash a factory restore image, click the "AP" button in Odin to select it. The image needs to be one that ends with a file extension "tar.md5", or Odin can't see it. If what you've downloaded is a zip archive, the image is inside that and you need to extract it first. Use the image in "step 2" of the root thread
I figured out what went wrong from your response thanks! I had saved the .tar.md5 on the external SD card rather than pc. Now attempting to re-root, .bat sees device but doesn't root.
cyberfem said:
I figured out what went wrong from your response thanks! I had saved the .tar.md5 on the external SD card rather than pc. Now attempting to re-root, .bat sees device but doesn't root.
Click to expand...
Click to collapse
yeah its really annoying youll have to unplug and plug it back in and x out of the thing like 20 times before it acutually does it