So i have never had so many problems with a phone, but this would be the first one a customer tried doing on their own.
So he downloaded the latest file from sammobile for his SCH-i605. he used odin to flash and was stuck in boot loop. I have tried many different methods to try and get his phone working. I have tried all of the alternate method files to no avail. the current file i have flashed is the VRAMC3 restore out of all the files i have tried this is 1 of very few that make it through the write. All the others fail on sboot. It currently sits on the unauthorized verizon blah blah blah. Its had no recovery since he brought it over and havent been able to get recovery back. All i have access to is download mode, some firmwares give me the kies screen talking about an error but cant get it seen in kies versions 2 and 3.
If you need any other info just ask, if i know the answer i will give it. He has no clue as to what OS he was on or even what the ROM that was on there.
BCityModz said:
So i have never had so many problems with a phone, but this would be the first one a customer tried doing on their own.
So he downloaded the latest file from sammobile for his SCH-i605. he used odin to flash and was stuck in boot loop. I have tried many different methods to try and get his phone working. I have tried all of the alternate method files to no avail. the current file i have flashed is the VRAMC3 restore out of all the files i have tried this is 1 of very few that make it through the write. All the others fail on sboot. It currently sits on the unauthorized verizon blah blah blah. Its had no recovery since he brought it over and havent been able to get recovery back. All i have access to is download mode, some firmwares give me the kies screen talking about an error but cant get it seen in kies versions 2 and 3.
If you need any other info just ask, if i know the answer i will give it. He has no clue as to what OS he was on or even what the ROM that was on there.
Click to expand...
Click to collapse
If the person tried to ODIN flash the latest firmware version for the SCH-I605, then it would have been VRUFND7 4.4.2 Kit Kat. (Unfortunately... once you install 4.3 or 4.4.2 on our Note 2's, both of those firmwares lock the bootloader with no current do it yourself method to unlock it. You can't successfully flash a prior Android version onto the phone after you upgrade past 4.1.2 either because of the locked bootloader).
Check out Droidstyle's Restore Guide here: http://forum.xda-developers.com/showthread.php?p=34891181. You will probably need to flash the pit file with the firmware to get it to Odin flash successfully. You can grab the SCH-I605 16gb Pit file from the guide.
Even though Droidstyle's guide is a little old, it is still the same steps for restoring to 4.4.2, so if you follow the guide (section 1b), it should help you fix the phone.
He doesn't have a link for the 4.4.2 firmware, but you can grab it from Sammobile. It looks like the Sammobile site is currently down for maintenance, but the link is here: http://www.sammobile.com/firmwares/download/30950/I605VRUFND7_I605VZWFND7_VZW.zip/
If you're using an older ODIN, then I would probably try to use a newer Odin version like 3.0.9 or 3.10.0. Make sure you run it with Administrative privileges and disable antivirus programs.
Good luck!
mattnmag said:
If the person tried to ODIN flash the latest firmware version for the SCH-I605, then it would have been VRUFND7 4.4.2 Kit Kat. (Unfortunately... once you install 4.3 or 4.4.2 on our Note 2's, both of those firmwares lock the bootloader with no current do it yourself method to unlock it. You can't successfully flash a prior Android version onto the phone after you upgrade past 4.1.2 either because of the locked bootloader).
Check out Droidstyle's Restore Guide here: http://forum.xda-developers.com/showthread.php?p=34891181. You will probably need to flash the pit file with the firmware to get it to Odin flash successfully. You can grab the SCH-I605 16gb Pit file from the guide.
Even though Droidstyle's guide is a little old, it is still the same steps for restoring to 4.4.2, so if you follow the guide (section 1b), it should help you fix the phone.
He doesn't have a link for the 4.4.2 firmware, but you can grab it from Sammobile. It looks like the Sammobile site is currently down for maintenance, but the link is here: http://www.sammobile.com/firmwares/download/30950/I605VRUFND7_I605VZWFND7_VZW.zip/
If you're using an older ODIN, then I would probably try to use a newer Odin version like 3.0.9 or 3.10.0. Make sure you run it with Administrative privileges and disable antivirus programs.
Good luck!
Click to expand...
Click to collapse
Ive tried that one as well and almost all the files in that thread. When he flashed the 4.4.2 firmware the phone wouldnt boot all it did was flash the Note 2 screen. Ive used the pit file as well with no luck. Using the top file on the link fails almost instantly, VRAMC3 writes and passes but will not boot, shows the unauthorized firmware screen.
I'm wondering if he flashed a firmware onto the phone that was from a different carrier like ATT or something. If so, he may have messed up the phone so bad that it might need jtag to repair it.
You've probably already tried all the normal Odin tips like using a different usb cable, different ports on the computer (usb 2.0 port is recommended), etc... so I won't go over all those.
I've never tried it and don't know if I'd recommend it, but I recall reading some threads a while back where someone discussed trying the Nand Erase function in Odin.... (again.... I'm not saying to do that... but you may want to research it to see if it might be an option if nothing else works).
I've also read where people say that they've used Cygwin to create custom tar files... then they ODIN installed each of the separate partition files (e.g. recovery, boot, modem, system, etc...), onto their Samsung device.
I'm not knowledgeable enough to offer guidance with Cygwin and I'm not sure if either of these ideas would work, but I just thought I'd throw them out there for the sake of brainstorming for ideas. Maybe someone will respond to your request who has more knowledge and ideas.
I wish you luck with getting it fixed.
Related
Below is the situation i'm in. Please dont reply with a generic "flash xyz in Odin" post as ive tried if you read.
I got a used Note 2. It has a clean ESN. Works fine. I wanted too root/unlock it to load a custom recovery and then a custom ROM.
It has VRALI3 as both baseband and Build.
I tried to use multiple version of Casual with no luck. I then tried to use different odin files with no luck..i keep getting an error and fails during the nand flash portion. At one point I soft bricked it (only boot logo..no recovery...no boot).
Only way i restored it was via sch-i605-16gb.pit in the pit area, I605VRLI3- verizon.tar for PDA and uncheck re-partition.
So back to where I was.
I tried to then use the pit file with CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar
No luck..fails with nand flash write error.
Tried instructions at http://forum.xda-developers.com/showthread.php?p=34891181
No luck.
Then I tried to load root66_VZW_stock_system.tar and it worked. It only has a system.img file in it.
With this..I have a baseband of VRALI3 but with a build of VRALJB with ROOT.
So I was supper happy and then tried to repeat everything above with no luck still..nand flash error.
I tried goo manager since i had root and loaded custom recovery..got the yellow triangle.
Back to pit + vrali3..then pit + root66 back to root.
And thats where i sit.
I think VRALI3 was a prelease build???? But i dont know what i need to do to get out of it and unlock the bootloader. I have no idea what version bootloader was/is loaded already....
What can I do??
Thank you for reading...and any help would be appretiated.
guardianali said:
Below is the situation i'm in. Please dont reply with a generic "flash xyz in Odin" post as ive tried if you read.
I got a used Note 2. It has a clean ESN. Works fine. I wanted too root/unlock it to load a custom recovery and then a custom ROM.
It has VRALI3 as both baseband and Build.
Click to expand...
Click to collapse
Vrali3 is the pre release which has a different bootloader than the other 3 versions. As far as I know, you are up a creak without a paddle. There is no way to unlock bootloader and root, or change to a different version when you are on that. Probably why the person was selling it. I'm guessing the person was selling it for cheaper than other ones and that's why you bought it. That pre release is known to be attached to that damn toolkit that people think is awesome. Sell it and buy a different one.
Sent From My Sticky Note, Too?
I have a Verizon galaxy note II, and had been running AllianceROM.
AllianceROM seemed to be running pretty good until one day when my accelerometer stopped working. I thought it may be a software bug, so I tried to reflash the ROM. I got a bootloop, and tried again.
I tried to flash cyanogenmod 11 and still got a bootloop. Then I realized I didn't have a safe backup.
I attempted to flash some stock firmware through ODIN, since I couldn't get anything to work through cwm.
In the end, I'm stuck with a note II that can't boot. When I try to turn it on, I see the galaxy note II logo, but then the screen goes black (not off, I have to pop the battery out before I can try again.) Power+home+volume up now brings me to android system recovery/manual mode, and power+home+volume down gets me to ODIN mode.
Any suggestions or help would be greatly appreciated. I really wasn't planning on getting a new phone at this point, so I hope it's not beyond fixing! Thanks in advance.
Ethan,
It sounds like you should be able to fix your device if you are careful. If you can boot into the stock recovery using power+ home + volume up buttons, then do a factory reset and wipe cache... that might fix your problem and let the device boot up normally.
You should also check out Droidstyle's restore guide at this link: http://forum.xda-developers.com/showthread.php?p=34891181. His guide has links and detailed instructions on how to restore back to stock. (Hit the thanks button for him too... as he spent a lot of time making the guide).
Remember that 4.1.2 is the last build that allows us to unlock our bootloader, so don't restore the device to 4.3 or 4.4.2 unless you want to permanently lock your bootloader. Also, there's no current root method for our phones if they get updated to stock 4.4.2, so don't odin that unless you decide you don't want root and custom ROM'S anymore.
Good luck!
mattnmag said:
Ethan,
It sounds like you should be able to fix your device if you are careful. If you can boot into the stock recovery using power+ home + volume up buttons, then do a factory reset and wipe cache... that might fix your problem and let the device boot up normally.
You should also check out Droidstyle's restore guide at this link: http://forum.xda-developers.com/showthread.php?p=34891181. His guide has links and detailed instructions on how to restore back to stock. (Hit the thanks button for him too... as he spent a lot of time making the guide).
Remember that 4.1.2 is the last build that allows us to unlock our bootloader, so don't restore the device to 4.3 or 4.4.2 unless you want to permanently lock your bootloader. Also, there's no current root method for our phones if they get updated to stock 4.4.2, so don't odin that unless you decide you don't want root and custom ROM'S anymore.
Good luck!
Click to expand...
Click to collapse
I just tried following that guide, installing the .pit file and the suggested stock firmware, but Odin reported "FAIL" instead of "PASS."
Now when I try to turn my phone on or go to stock recovery, I get the message "Firmware upgrade encountered an issue. Please use Software Repair Assistant & try again."
Any hope left?
Ethan.S said:
I just tried following that guide, installing the .pit file and the suggested stock firmware, but Odin reported "FAIL" instead of "PASS."
Now when I try to turn my phone on or go to stock recovery, I get the message "Firmware upgrade encountered an issue. Please use Software Repair Assistant & try again."
Any hope left?
Click to expand...
Click to collapse
Yes, there's still hope to fix it if you can get the phone into download mode.
Here's some info to clarify before you try something else.... What firmware did you try to install when you used Droidstyle's guide? Also, in your initial post, you said "I attempted to flash some stock firmware through ODIN, since I couldn't get anything to work through cwm." What firmware did you flash at that point.... was it one of the Verizon stock firmwares? And what build number was it ( 4.1.2 VRAMC3 , 4.3 VRUEMJ9, 4.4.2 VRUFND7)?
I ask this because, if you flashed 4.3 or 4.4.2, then you can no longer restore back to 4.1.2....you would have to restore back to one of those newer versions (and those newer firmwares actually lock the bootloader and install Knox security features... so that's why I was suggesting not to use them--- unless you already did before you had placed your original post for help).
If you can't restore the phone through ODIN using Droidstyle's guide, then you might try the emergency firmware recovery feature that's available through the Samsung Kies program. You can find Kies at this link: http://www.samsung.com/us/kies/
**The KIES instructions say to use Kies version 2.6 for Firmware recovery back to 4.1.2, and use Kies version 3 for Firmware 4.3 and 4.4.2.
Here's a link to Kies 3 FAQ as well: ( http://www.samsung.com/us/support/SupportOwnersFAQPopup.do?faq_id=FAQ00059191&fm_seq=81528 ). Scroll down under Basic Functions and look for the link to "How do I Perform an Emergency Firmware Recovery..." The process should be similar if you plan to use KIES 2.6 instead - (that's only if you're able to restore back to 4.1.2 and you never Odin flashed one of the newer 4.3+ firmwares) .
I hope you can get it fixed. If you're not sure of things, I would suggest researching more and asking more questions before going forward. There is risk that we all take whenever we start modifying our phones, and the more knowledge we can get, the better chances of recovering from errors when we mess something up. (I know I've made plenty of errors as I've tried to learn... I even bricked my Tranformer Prime tablet shortly after receiving it from EBay :banghead: ). If worst comes to worst, you might end up having to pay someone to do a Jtag repair to unbrick it.... but let's hope it doesn't come to that.
Also-- you could try Verizon's Software Upgrade/Repair Assistant found here: ( http://www.verizonwireless.com/support/devices/knowledge_base.html/80201/ ). I have no idea what the differences are between Verizon's software repair assistant and Kies.... **
Hello guys. I helped my dad a while back to root and flash a custom rom to his Note 2. He's recently been having some trouble with it and wants to restore it to stock. He was running Beans rom I believe the dev goes by Beanstown106 or something like that. Was an older version I think build 21 or 22. Used CASUAL to root. So I have a few questions. Does it matter what version of ODIN I use or should I just get the latest? Do I need to get the app to reset the counter? He might end up sending it in for warranty. All I should need is the PIT and PDA file to flash to stock with ODIN correct?
I found this video guide and seems to be relatively simple. But I just want to make sure I don't screw it up by using wrong ODIN version or anything like that. Safe to just use the links provided in the video for PIT/PDA files? Here's the video link if anyone wants to check it: https://www.youtube.com/watch?v=4qtbEevn1VA or if you have a better video guide that I should use instead or have links to share for the files I need I would appreciate it
jcr4990 said:
Hello guys. I helped my dad a while back to root and flash a custom rom to his Note 2. He's recently been having some trouble with it and wants to restore it to stock. He was running Beans rom I believe the dev goes by Beanstown106 or something like that. Was an older version I think build 21 or 22. Used CASUAL to root. So I have a few questions. Does it matter what version of ODIN I use or should I just get the latest? Do I need to get the app to reset the counter? He might end up sending it in for warranty. All I should need is the PIT and PDA file to flash to stock with ODIN correct?
I found this video guide and seems to be relatively simple. But I just want to make sure I don't screw it up by using wrong ODIN version or anything like that. Safe to just use the links provided in the video for PIT/PDA files? Here's the video link if anyone wants to check it: https://www.youtube.com/watch?v=4qtbEevn1VA or if you have a better video guide that I should use instead or have links to share for the files I need I would appreciate it
Click to expand...
Click to collapse
"Do I need to get the app to reset the counter?" If you're going to return it for warranty... it would be good idea to reset the binary counter. The Triangle Away app from Chainfire is available in the Play store for this. **You'll need to run Triangle away before you restore to stock as you need to have the bootloader unlocked when you run it... or you could hard brick the phone.**
"Does it matter what version of ODIN I use or should I just get the latest?" Either of the Odin versions 3.07, 3.09, or 3.10 should work fine to restore the phone.
"All I should need is the PIT and PDA file to flash to stock with ODIN correct?" Correct. The firmware goes into PDA slot in Odin v. 3.07. In Odin 3.09 and 3.10, AP has replaced the PDA slot... so the firmware would go in AP in newer Odin versions. Pit file goes into Pit slot in either Odin version.
I think that video is a good reference to help restore the phone. I used it myself when first learning to return this phone to stock. I don't know if I would use the download links or not in the YouTube video, as I tend to stick with Xda provided links.
You've probably found Droidstyle's Restore guide already, but if not, check it out here: ( http://forum.xda-developers.com/showthread.php?p=34891181 ). Section 1b has step by step instructions to restore the phone. He has a link for Odin 3.07 on his guide which should work fine. He also has the pit file for download.
Since you are on 4.1.2 bootloader... I would probably restore back to that firmware version. After you restore to stock, you can take the OTA'S to get up to 4.4.2 if you're wanting to return it for warranty (just remember that you can't downgrade back to 4.3 or 4.1.2 if you upgrade to 4.4.2). The one thing I would do after returning the phone to Stock would be to boot into recovery, then wipe cache & do a factory reset... as Odin doesn't seem to fully wipe everything.
Droidstyle's link for 4.1.2 looks to be down.... but recognized XDA Developer imnuts has the 4.1.2 VRAMC3 Odin file on his Android File Host site here: https://www.androidfilehost.com/?fid=23159073880932932
Good luck.
So i have a stock sprint note 3 that had 4.4.4 on it.
I attempted to install twrp/cwm through odin, but it failed and now i'm stuck in the failed firmware update loop.
I have tried installing older versions of the stock firmware, seems like i'm stuck looking for a 4.4.4 which seems kinda hard to find right now.
What are my other options, my friend is looking for the serial numbers to see if i can just use keis to recover.
k0ncept said:
So i have a stock sprint note 3 that had 4.4.4 on it.
I attempted to install twrp/cwm through odin, but it failed and now i'm stuck in the failed firmware update loop.
I have tried installing older versions of the stock firmware, seems like i'm stuck looking for a 4.4.4 which seems kinda hard to find right now.
What are my other options, my friend is looking for the serial numbers to see if i can just use keis to recover.
Click to expand...
Click to collapse
Although your thread will probably be moved to the Q&A section, you stated you are able to install older versions...... take it back into DL mode and Odin 4.4.4. There are several threads you can download the NK4 Firmware from including the Sammobile site.
SM-N900P Spint (cdma) 2014 December 4.4.4 N900PVPUDNK4 N900PSPTDNK4
shadowcliffs Thread in the General Section
.
k0ncept said:
So i have a stock sprint note 3 that had 4.4.4 on it.
I attempted to install twrp/cwm through odin, but it failed and now i'm stuck in the failed firmware update loop.
I have tried installing older versions of the stock firmware, seems like i'm stuck looking for a 4.4.4 which seems kinda hard to find right now.
What are my other options, my friend is looking for the serial numbers to see if i can just use keis to recover.
Click to expand...
Click to collapse
Honestly it sounds like you're making this more difficult than it really is.
All you need is;
NK4 .tar
SU
&
TWRP
So i'm fairly new to this the last phone i did was my vz s4 (and it went off with less bumps).
I'm stuck in the boot load loop. I can't flash any ROM on it right now, i think i'm trying to find the right 4.4.4 rom. Any place with good rom support would help. sammobile is far too slow on downloads...also there are a few 4.4.4 roms by now.
So the phone was purchased in early Nov 2014, already on a 4.4.4.
I dl'd odin and a TWRP, foolishly didn't make sure 4.4.4 could be flashed in the same way. Odin marked it as failed and when i re-start the phone it runs into the "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
The phone can get into download mode just fine (cannot boot)...tho i have no idea what to flash onto it now.
k0ncept said:
So the phone was purchased in early Nov 2014, already on a 4.4.4.
I dl'd odin and a TWRP, foolishly didn't make sure 4.4.4 could be flashed in the same way. Odin marked it as failed and when i re-start the phone it runs into the "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
The phone can get into download mode just fine (cannot boot)...tho i have no idea what to flash onto it now.
Click to expand...
Click to collapse
As Nickitt stated, don't make it more than it is. If you can get into DL mode then you are not fully bricked which is good. You need to flash an " Official 4.4.4 Firmware " to get you out of this situation, whether it be a slow download or not. I provided a link in my original first response of several uploads of 4.4.4 that you could possibly use that were uploaded by member shadowcliffs in his same thread/post. After you have flashed the official firmware and gone through the initial setup once again with the stock firmware, get the phone back into DL Mode and flash TWRP or Philz CWM recovery via ODIN. Once you have your custom recovery loaded, flash the Custom Rom of your choice.
Hey dark,
thanks for the quick and very very useful response. i wish i hit this up way sooner i did find those links after hours of searching through garbage. i've been downloading a few 4.4.4 images for the last 2hours. Hopefully this will help me! sadly those are the same slow connections i've scene. damn 50kb/sec so sad haha
I'll keep the board posted. but mostly bump that og thread
Damn, fails on the nk4 image and the nh7.
fails on the same spot system.img.ext4
any other suggestions board? please?
make sure your using the hltespr version of either TWRP or philz recovery, if its not working on TWRP switch to philiz. Could also be a bad download - re-download and flash again
Why don't you just use TWRP Manager to install TWRP after you root?
Sent from my GALAXY Note 3 via Tapatalk
not being able to root was the problem
FIXED my issues!!
Never use vmware and Mac to run heimdall or Odin... They should more prominently tell you that.
Thank you board for the concern
problem solved
Thanks for updating that you fixed the problem and what it was. It sounded like you were doing everything correctly. i was getting concerned that it wasn't working. I don't use mac, but if i did i would have been very grateful for that knowledge. thanks for the update. too often someone fixes the problem and just quits posting on the thread.:good:
k0ncept said:
FIXED my issues!!
Never use vmware and Mac to run heimdall or Odin... They should more prominently tell you that.
Thank you board for the concern
Click to expand...
Click to collapse
Parallels is a better option imo as far as v-machines are concerned but anything after Mountain lion doesn't work well. The newest mac osx doesn't work at all with Heimdall. It won't download the pit file. If your running mavricks you can try using a program called winebottle
How to Run Odin On Mac: http://youtu.be/j7fpouzMSsk also jOdin is another desktop tool to use. jOdin is a early stage online flashing tool with limited capabilities at this time.Beings its a online flashing tool. I would make sure to have a good internet connection or you could run into trouble im guessing. All in all I think its a good idea I just hope this project keeps going.
JOdin - Using Odin on a Mac: http://youtu.be/MiPRXq207Ug
It's only right jag.
Goat, thanks for the additional information. I hope there are improved options for the mac and Linux one day
k0ncept said:
It's only right jag.
Goat, thanks for the additional information. I hope there are improved options for the mac and Linux one day
Click to expand...
Click to collapse
Me too bro, me too!
Hi all,
I am a newbie and don't know much. So please bear with me.
I was trying to root my Galaxy S5(SM-G900H) by using the tutorial given on http://forum.xda-developers.com/showthread.php?t=2696537 but the process did not go as planned as keep struck on recovery.img on odin3.10 so I googled and found that changing USB port will help so I take out the battery changed the port and try again but this time I soft-bricked the phone as odin struck on cache.img and now when i try to start my phone I get Firmware upgrade encountered. So now I again googled and found about unified toolkit and install it on my windows 10 ,now when i choose option 6 (i.e. flash stock boot image to your device) it says waiting for usb debugging to be enabled ,now I remember I turn USB debugging on but it is still struck here. Now what should I do? My parents gave this phone just a week ago and I am in deep trouble.
P.S.-I am only able go into the download mode not recovery mode.
Boot into Download Mode and use Odin to install the original firmware. Might require a factory reset after if still bootlooping. Here is a link to 6.0.1 from Sri Lanka https://mega.nz/#!YMAFhR4a!pZmf7OEWgzDzET1FLGsAOQ5XyVlvE8y4pJfB8KDNbMI . Any region firmware should work for the F model. If you want your specific one then check sammobile.com. I just linked to the other because it is a much faster download.
Problem encountred while installing original firmware
I tried to use Odin to install original firmware , I started the process but Odin got struck on sboot.bin (Also I read somewhere that whole process does not take more than 10 minutes). So please help me.
Which firmware did you try?
You might be able to use Kies to recover your device as well.
es0tericcha0s said:
Which firmware did you try?
You might be able to use Kies to recover your device as well.
Click to expand...
Click to collapse
I downloaded it from http://www.teamandroiders.com/samsung-galaxy-s5-sm-g900h-stock-rom-firmware/ with PDA: I9500XXUBOL2. I want to know one more thing as I am in India so should I use INU or INS?
ratcoder said:
I downloaded it from http://www.teamandroiders.com/samsung-galaxy-s5-sm-g900h-stock-rom-firmware/ with PDA: I9500XXUBOL2. I want to know one more thing as I am in India so should I use INU or INS?
Click to expand...
Click to collapse
Oh geez...no wonder it isn't working. i9500 = S4. Really gotta be careful with that kind of thing.
INU is for unlocked from the factory
INS is for phones from a carrier
Either one should work. As mentioned, with the G900h, any firmware should work that is for that model, no matter the region. Use the one I posted and change the language or grab the one for India from sammobile.com though it'll take an hour or 2.
Edit: I see that it was just mislabeled as i9500, but the download says g900h after all.
Were you on 5.1.1 or 5.0 before you started this process?
es0tericcha0s said:
Oh geez...no wonder it isn't working. i9500 = S4. Really gotta be careful with that kind of thing.
INU is for unlocked from the factory
INS is for phones from a carrier
Either one should work. As mentioned, with the G900h, any firmware should work that is for that model, no matter the region. Use the one I posted and change the language or grab the one for India from sammobile.com though it'll take an hour or 2.
Edit: I see that it was just mislabeled as i9500, but the download says g900h after all.
Were you on 5.1.1 or 5.0 before you started this process?
Click to expand...
Click to collapse
Well I downloaded another one from http://firmwarefile.com/samsung-sm-g900h the second one, before it all started I was on 5.0 and the link you give does not work anymore. Anyway I tried with the firmware with upper link. And Odin is struck with sboot.bin for more than an hour. And have no idea what's going on? So what should I do?
Also someone suggested to use Pit. Should I use it?
No, don't use the pit. Try the newer firmware for 6.0
es0tericcha0s said:
No, don't use the pit. Try the newer firmware for 6.0
Click to expand...
Click to collapse
So I downloaded the 3rd link from http://firmwarefile.com/samsung-sm-g900h for newer version and try Odin 11.2 with it. I try two times to flash the firmware first time it struck on sboot.bin and second time it just showed fails(I used Odin with administrative rights this time) .Please see the attached images. Please tell me what should I do now. I want to repair it ASAP.
Not sure. This is pretty standard stuff. Have used Odin 1000 times and haven't had that much trouble with it. Sorry.
es0tericcha0s said:
Not sure. This is pretty standard stuff. Have used Odin 1000 times and haven't had that much trouble with it. Sorry.
Click to expand...
Click to collapse
I think I should mention that the firmware I used was INS not INU and if you have a genuine link for version 6 for INU with fast download speed, please share it (different than sammobile because it has only fast speed only for premium users). Should I use PIT or try something else than Odin. Anything that might help please tell me. I have got this phone just a week ago and my parents are not gonna give me a new one so please help me.
I keep encountering sboot.bin error ,maybe there is a way to resolve it?
I'd just try to load TWRP and a custom rom at this point.
es0tericcha0s said:
I'd just try to load TWRP and a custom rom at this point.
Click to expand...
Click to collapse
Actually I have no idea what TWRP is so any link or anything that can help without ruining the situtation.
http://forum.xda-developers.com/galaxy-s5/development/rom-t3224562
es0tericcha0s said:
http://forum.xda-developers.com/galaxy-s5/development/rom-t3224562
Click to expand...
Click to collapse
I want to know one more thing on the above link there is a custom firmware and there is a custom ROM with bootloader and all. So should I flash custom firmware or use the instructions given on thread to flash custom ROM?
The custom rom does not include bootloader and modem. You will need to flash via Odin if you were not on the same firmware as the software is based off of. I would flash them anyway, to be safe. You can skip the root part as it is not need. Follow the instruction in post 2 for stock rom users minus the root part. Make sure to boot directly back into TWRP recovery before it attempts to boot. You can load rom on SD card and any additional add-ons you want. Plenty of youtube guides on how to use Odin to flash TWRP and such.
es0tericcha0s said:
The custom rom does not include bootloader and modem. You will need to flash via Odin if you were not on the same firmware as the software is based off of. I would flash them anyway, to be safe. You can skip the root part as it is not need. Follow the instruction in post 2 for stock rom users minus the root part. Make sure to boot directly back into TWRP recovery before it attempts to boot. You can load rom on SD card and any additional add-ons you want. Plenty of youtube guides on how to use Odin to flash TWRP and such.
Click to expand...
Click to collapse
Finally seen some progress, thank you very much. I successfully flashed TWRP recovery, but I got a couple of questions. Firstly I should flash ROM from recovery mode and then go to download mode to flash boot-loader and Modem files right? Should I flash ROM from SD card? And if this custom ROM causes problem is there a way to get to stock ROM? And is this custom ROM rooted or I have to root it via CF-Auto root or try anything else?
Rom might work without bootloader and modem. Just depends on your previous firmware. I would try and flash it though as it was recommended. Rom flash from SD card or internal. Either way should work. You will be able to go back to stock if you can find a firmware that works. It is already rooted.
es0tericcha0s said:
Rom might work without bootloader and modem. Just depends on your previous firmware. I would try and flash it though as it was recommended. Rom flash from SD card or internal. Either way should work. You will be able to go back to stock if you can find a firmware that works. It is already rooted.
Click to expand...
Click to collapse
Thank you very much.phone is working again with custom ROM.just one more thing if I upgrade from custom ROM what will happen?
:good::highfive::victory:
It should work to reflash the original firmware through Odin. Just get the one that matches your baseband version.