Database Users

[Q] Help to root SGS4 I9505 - brazilian version

I´ve been reading this forum for 3 days and searching for all informations needed to root my SGS4 I9505. I have already followed the threads http://forum.xda-developers.com/showthread.php?p=40819876 and also read ChainFire´s thread http://forum.xda-developers.com/showthread.php?t=2219803
I have also tried to use the SGS4 toolkit found in this thread http://forum.xda-developers.com/showthread.php?t=2192841
I have tried different versions of Odin (v 1.85, v 3.07, v 3.04) and did not get success. It seems that it is write protected some way, since when in download mode, the last line in the left superior edge shows "Write Protection= Enable"
I attached the messages from Odin (same messages in all versions of Odin). I tried to install the PIT file alone as well, but also another error message comes, also saying that the complete (write) operation failed.
My firmware version is AP,CP: I9505VJUBMG3 and CSC: I9505ZTOBMG3
I will really appreciate any help to root my phone.

Hello guys,
Come on, help me with this, please? :crying:
kponto said:
I´ve been reading this forum for 3 days and searching for all informations needed to root my SGS4 I9505. I have already followed the threads http://forum.xda-developers.com/showthread.php?p=40819876 and also read ChainFire´s thread http://forum.xda-developers.com/showthread.php?t=2219803
I have also tried to use the SGS4 toolkit found in this thread http://forum.xda-developers.com/showthread.php?t=2192841
I have tried different versions of Odin (v 1.85, v 3.07, v 3.04) and did not get success. It seems that it is write protected some way, since when in download mode, the last line in the left superior edge shows "Write Protection= Enable"
I attached the messages from Odin (same messages in all versions of Odin). I tried to install the PIT file alone as well, but also another error message comes, also saying that the complete (write) operation failed.
My firmware version is AP,CP: I9505VJUBMG3 and CSC: I9505ZTOBMG3
I will really appreciate any help to root my phone.
Click to expand...
Click to collapse

Hello guys, please, can someone help me?

kponto said:
Hello guys, please, can someone help me?
Click to expand...
Click to collapse
dude see u checked re-partition make sure its unchecked and only auto-reboot and f.reset time is checked
also only choose pda bur dont choose pit
and thats it

qazmed said:
dude see u checked re-partition make sure its unchecked and only auto-reboot and f.reset time is checked
also only choose pda bur dont choose pit
and thats it
Click to expand...
Click to collapse
qazmed, I have also tried to flash only the CF-auto-root file without the PIT file, with only auto-reboot and f.reset time checked, but it did not work too. Anyway, I´ll try to flash my original stock version again and then try again to flash the CF auto-root according to a hint from samersh, as soon as I finish to download it (1.5GB!!). thnx!

kponto said:
qazmed, I have also tried to flash only the CF-auto-root file without the PIT file, with only auto-reboot and f.reset time checked, but it did not work too. Anyway, I´ll try to flash my original stock version again and then try again to flash the CF auto-root according to a hint from samersh, as soon as I finish to download it (1.5GB!!). thnx!
Click to expand...
Click to collapse
Hi, tried to flash stock rom with pit file, both with re-partition unchecked and checked and did not succeed. In the first case, the failure message from Odin is "There is no pit partition" and in the second case, the failure msg is "Complete (write) operation failed!"
It seems to have a kind of "write protection" that does not allow Odin to flash... Does anyone have heard anything about this???

I am having the exact same problem as the guy that posted this thread!! Anyone may help please ?

Ensifolk said:
I am having the exact same problem as the guy that posted this thread!! Anyone may help please ?
Click to expand...
Click to collapse
Hi, I have just solved the problem and got to flash CF autoroot with Odin, by simply using the ORIGINAL USB CABLE ! Before this, I was using a diferent cable just bought with a cheap charger. It´s strange, because all usb cables have the same 4 wires, but it seems flashing process is very sensitive and probably the cheap cables insert unacceptable noise in the circuit loop...
Just found this info here: http://forum.xda-developers.com/showthread.php?t=2267107&page=2
Try it and I hope you get good results !!

kponto said:
Hi, I have just solved the problem and got to flash CF autoroot with Odin, by simply using the ORIGINAL USB CABLE ! Before this, I was using a diferent cable just bought with a cheap charger. It´s strange, because all usb cables have the same 4 wires, but it seems flashing process is very sensitive and probably the cheap cables insert unacceptable noise in the circuit loop...
Just found this info here: http://forum.xda-developers.com/showthread.php?t=2267107&page=2
Try it and I hope you get good results !!
Click to expand...
Click to collapse
Man I was just gonna send you a message telling you that I tried a different cable USB, the original one and that it worked! Hahahahahhaa! Likewise my friend, this easy solution did the trick

[Q] Bricked - Please Help (SOLVED)

Hi all,
I am really hoping someone can help me. I have a Sprint Samsung Galaxy S4 (Non T version) that appears to be soft bricked. My phone was hanging on the yellow Sprint screen so after other procedures, I decided to try and ODIN a stock version. What I had before all this happened was MK2 (knox) stock with only CF Auto Root. I downloaded the MK2 stock ROM from XDA and tried to ODIN. It failed. It got through the majority of the process and then at the very end it said FAILED. Now if I try and boot the phone, it automatically goes into the firmware error screen. So I still have the ability to ODIN but it always fails. I have also downloaded the NAE stock ROM from XDA and tried that too. I have tried using Odin 3.07, 3.09, and even 1.85. All fail. On the screen I sometimes get these messages as the ODIN process fails. Either a start [2xx, 1440] and next line BAR [2xx, 1440], or I get a start and then a sw rev check fail fused 5 binary 4. These are all in red letters just underneath the download mode details. I really don't know what to do. Please help me recover my phone. Any help is greatly appreciated. Thanks so much!

IF your phnone was on an NAE firmware you will probably have problems going back to MK2.
Search for the NAE firmware .tar and try that.

@SuperG03
So great to see you posting back after asking for help.
So cool when people contribute to what worked and didn't so that others can be helped and help to contribute to the community at large.....
Oh, wait you didn't.
Guess all is good.
smmmeeesh.

leaderbuilder said:
IF your phnone was on an NAE firmware you will probably have problems going back to MK2.
Search for the NAE firmware .tar and try that.
Click to expand...
Click to collapse
As I mentioned in my OP, I tried the NAE firmware with multiple attempts on various editions of Odin. All without success.
leaderbuilder said:
@SuperG03
So great to see you posting back after asking for help.
So cool when people contribute to what worked and didn't so that others can be helped and help to contribute to the community at large.....
Oh, wait you didn't.
Guess all is good.
smmmeeesh.
Click to expand...
Click to collapse
I'm sorry, it's been like a day and a half and I've been trying like crazy to figure out how to fix this thing... Not sure how fast you expect me to reply, but I do appreciate any and all help.
SuperG03

Just really wondering if you attempted the suggestions. And or what you've done to get it to work.
It gets old trying to assist people, especially when they make it sound so urgent, and then never hearing back.
Hope you get it working.
Good luck!

leaderbuilder said:
Just really wondering if you attempted the suggestions. And or what you've done to get it to work.
It gets old trying to assist people, especially when they make it sound so urgent, and then never hearing back.
Hope you get it working.
Good luck!
Click to expand...
Click to collapse
I definitely understand trying to help and not ever hearing back would get annoying... However, for the first like half a day I checked back at this thread every hour or 2 and it had a lot of views but not any replies. Even as of now, there hasn't been a reply with a suggestion of what to do that I haven't already stated I did try in my OP (you suggested NAE and I had been trying that already). I do appreciate you at least trying though.
SuperG03

SuperG03 said:
Hi all,
I am really hoping someone can help me. I have a Sprint Samsung Galaxy S4 (Non T version) that appears to be soft bricked. My phone was hanging on the yellow Sprint screen so after other procedures, I decided to try and ODIN a stock version. What I had before all this happened was MK2 (knox) stock with only CF Auto Root. I downloaded the MK2 stock ROM from XDA and tried to ODIN. It failed. It got through the majority of the process and then at the very end it said FAILED. Now if I try and boot the phone, it automatically goes into the firmware error screen. So I still have the ability to ODIN but it always fails. I have also downloaded the NAE stock ROM from XDA and tried that too. I have tried using Odin 3.07, 3.09, and even 1.85. All fail. On the screen I sometimes get these messages as the ODIN process fails. Either a start [2xx, 1440] and next line BAR [2xx, 1440], or I get a start and then a sw rev check fail fused 5 binary 4. These are all in red letters just underneath the download mode details. I really don't know what to do. Please help me recover my phone. Any help is greatly appreciated. Thanks so much!
Click to expand...
Click to collapse
So now I would like to reply as to try and help anyone else that might have had something similar to this happen to their phone. I DID FIX my phone but using a CRAZY method that I have no good idea of why it worked. So here goes...
LONG VERSION (Short Version below for those that don't want to read about all my trials and efforts):
So as I mentioned I was on MK2 before the problem started. I tried to ODIN the MK2 Stock ROM I downloaded here but it failed. So then I decided ok maybe the issue was the older ROM, so I downloaded the NAE Stock ROM and tried to ODIN that. Again, failed. Now both of these 2 tries got far into the process before they failed. So again, through reading various posts here and on other forums it was suggested to try with other version of ODIN (I had been trying 3.07). I then tried the MK2 ROM again but with ODIN 3.09 but it failed almost immediately. That is when I noticed the lines "SW Rev Check Fail Fused 5 Binary X" every time it tried and failed. My guess is that this has something to do with the whole not being able to downgrade ROMs at any point and since I had almost completed the NAE stock ROM ODIN flash, it was stuck only with the option for NAE. So then onto trying NAE with ODIN 3.09. Once again, got most of the way done but failed toward the end of the system.img.ext4 part. I kept noticing that on the screen, almost as soon as I started the ODIN process it would output a line saying Start [220, 1440] and then soon after a line saying BAR [224, 1440]. Now I still have no idea what any of that means, but it was always failing, mostly toward the end of the flash. I then tried other ODIN versions including 1.85. All with the same results. I was at a loss. At that point I got desperate and decided I wasn't even going to try and save my DATA and thought maybe the partitions got corrupted so I found the NAE PIT file from these forums and attempted to ODIN both the PIT and the PDA with re-partition option. Once again, all attempts with all ODIN versions failed, with the same START and BAR messages showing up. I then broke down and decided to post here for help. I kept reading but everyone kept just saying in other threads about maybe KIES interfering if it was active in anyway, etc. so I check my processes and there were no KIES ones running. At that moment something occurred to me about another process by which to flash that I remember from my Galaxy S2 days. That was Heimdall. So, I decided to go on a mission to learn how to use Heimdall myself without a ready package. I finally learned how and decided to try it. I had to extract out all the .bin and .ext4, etc files out of the NAE tar and load them up manually. I started to flash and it looked to be working but then alas, it failed similarly to how ODIN did. I was at my wits end by this point. However, something occurred to me when I realized that the .tar had all these independent files in it that ODIN just tried to do all together. So here is what I did that finally WORKED. I used ODIN 3.09 with the NAE PIT file and the NAE ROM PDA file. I checked only Re-Partition and unchecked all others. I then watched exactly what ODINs log said was being flashed to the phone and what failed. I kept re-flashing until I got passed the system.img.ext4 file and the it failed on one of the others. I made note at which files out of the 13 that came from the .tar file were sent by ODIN successfully before it failed. I then closed ODIN and restarted phone in download mode and went to Heimdall. I used Heimdall to manually select only the remaining files left of the 13 that DID not go through successfully. I then flashed those I think 3 or 4 files and it said it was successful. I then rebooted my phone and to my SHOCK the phone booted up successfully and went into the OS as if it was factory wiped and ready for first time use. I was a bit bummed about having to redo all my settings, etc again and losing my old Text Messages, etc, but was so happy to have my phone back up and running. Thanks for reading this whole thing (I know it was quite long) and I hope it helps someone else out of a similar jam.
SHORT VERSION:
GET NAE Stock ROM
GET NAE PIT File
GET ODIN 3.09
GET Heimdall
YOU WILL LOSE YOUR DATA
Step 1) Use ODIN 3.09 (Run as Admin) and load up PIT file and PDA. Uncheck everything but RE-Partition
Step 2) (Hard Part) Keep flashing over and over again until you get at least the system.img.ext4 part to go through before ODIN says FAIL (It should fail on another file, like hidden.img.ext4 or NON-HLOS.bin
Step 3) Scroll through the ODIN log on the left and note every file that was successful. Basically any files it says was successful until the last one that it stops at and says FAIL
Step 4) You will need to extract out the contents of the NAE Stock ROM tar file to another directory
Step 5) Use Heimdall frontend (Run as Admin) and use the flash tab
Step 6) Load the PIT file into Heimdall as that is required for anything. But DO NOT use RE-Partition option
Step 7) Click Add and select each of the remaining files with their appropriate Partition Name and browse for those files from the ones you extracted from the tar. There are 13 files total from the tar file. Just load up (Add) starting with the file that failed in ODIN and then load up whichever ones that did not show up on the ODIN log at all. Click Start and cross your fingers
Step 8) If all went well, the phone should reboot and be up and running. If not you might have to start at Step 1 and try again
Step 9) Jump For Joy that your phone is Alive and working again!!!
Once again, I wanted to share my experience with everyone in hopes that it will help someone else out. I have no idea why I had to go to such great lengths of combining 2 versions of FLASHING and doing it piece by piece, but that is for greater minds then me to either know or figure out. I'm just happy my phone is working again! Good luck to anyone else having a similar issue.
SuperG03

Start Up Fail while installing rom

Ok guys I just recently rooted my first phone. All was well until I tried to install my first ROM. It seemed to be going fine until I got a Screen that said "start up fail" and in small red text at the top it said "Custom Binary Blocked By Secure Boot (Boot. img)" Here is a picture of the screen: http://imgur.com/a/DQ62P
Here is the link to the ROM: http://forum.xda-developers.com/verizon-s7-edge/development/stang5litre-edition-5-0-s7e-t3450208
Any Ideas on what I can do to fix this?

Dizzy.Dylan said:
Ok guys I just recently rooted my first phone. All was well until I tried to install my first ROM. It seemed to be going fine until I got a Screen that said "start up fail" and in small red text at the top it said "Custom Binary Blocked By Secure Boot (Boot. img)" Here is a picture of the screen: http://imgur.com/a/DQ62P
Here is the link to the ROM: http://forum.xda-developers.com/verizon-s7-edge/development/stang5litre-edition-5-0-s7e-t3450208
Any Ideas on what I can do to fix this?
Click to expand...
Click to collapse
Anyone got any ideas on what to do?

Dizzy.Dylan said:
Anyone got any ideas on what to do?
Click to expand...
Click to collapse
I had a similar occurrence while using FlashFire when I accidentally hit the EverRoot option. You'll have to put it into download mode and ODIN a stock ROM onto it. Then ROOT and upgrade as usual being careful not to hit the EverRoot. Hope it helps.

otterdad said:
I had a similar occurrence while using FlashFire when I accidentally hit the EverRoot option. You'll have to put it into download mode and ODIN a stock ROM onto it. Then ROOT and upgrade as usual being careful not to hit the EverRoot. Hope it helps.
Click to expand...
Click to collapse
I never hit EverRoot and I've tried it twice now and still havent gotten it to work Could it be something to do with the firmware?

Hey man, sorry to hear about this, I'm not exactly sure your problem, but I guess I would start by re-flashing the ENG Boot for your device (via Odin) - assuming that's the root method you used (you can find it here if you haven't got it elsewhere) Otherwise you could flash your device's stock firmware via Odin and then you could try following this guide here for rooting, and retry everything, which is what I would recommend.
I used that guide for my brother's SM-G935V and it has worked "flawlessly", I haven't tried installing a ROM on it yet but it should work as long as the ROM itself works, - I say "flawlessly" because there are a few issues with rooting this phone, but you can easily work around all of them.
I would recommend explaining and detailing your problem as much as you possibly can, in this post and in future posts, so that you can get as much help as possible.. if you need any clarification on anything, let me know, and be careful, for your first phone experimenting ,there's a lot of sh** that can go wrong! Keep in mind that you can fix most problems by flashing your stock firmware with Odin if all else fails.
Best of luck to you, let me know how it goes.

Odin "complete(write) operation failed" when rooting

I'm trying to use PartCyborgRom on my Galaxy S8 SM-G950U USA version. When I first clicked start in Odin, it said, "complete(write) operation failed". Following that I get a blue screen that says something along the lines of update failed. If I flash part 2 it will let me go back into download mode but the cycle repeats. So far I have used two different computers (with the Samsung drivers installed), at least 2 USB 2 and 3 ports (I know it says not to use 3 but I wanted to see if anything changed), and 2 different cables. I've seen other threads where people say to keep trying while leaving Odin open, etc but none of that has worked either. Does anyone know what the cause could be?

QuantumPie said:
I'm trying to use PartCyborgRom on my Galaxy S8 SM-G950U USA version. When I first clicked start in Odin, it said, "complete(write) operation failed". Following that I get a blue screen that says something along the lines of update failed. If I flash part 2 it will let me go back into download mode but the cycle repeats. So far I have used two different computers (with the Samsung drivers installed), at least 2 USB 2 and 3 ports (I know it says not to use 3 but I wanted to see if anything changed), and 2 different cables. I've seen other threads where people say to keep trying while leaving Odin open, etc but none of that has worked either. Does anyone know what the cause could be?
Click to expand...
Click to collapse
You need to read a bit better and you would see that most of the errors you received are normal
What bootloader revision is your device on. 5th number from end is bootloader revision
Try to read a bit better and search the thread. All is answered there. There will be failures but some are normal and needed for this root method to work

TheMadScientist said:
You need to read a bit better and you would see that most of the errors you received are normal
What bootloader revision is your device on. 5th number from end is bootloader revision
Try to read a bit better and search the thread. All is answered there. There will be failures but some are normal and needed for this root method to work
Click to expand...
Click to collapse
Just realized I could search for keywords in a thread a few minutes ago.
I'm no longer sure but I'm guessing it was past 2. If that is the case, is there any way I can root?

QuantumPie said:
Just realized I could search for keywords in a thread a few minutes ago.
I'm no longer sure but I'm guessing it was past 2. If that is the case, is there any way I can root?
Click to expand...
Click to collapse
I didn't mean to sound like a arse. This root method can be tricky is why I say read read read. A lot of people miss the section of upload mode errors and device software unauthorized screen
What is the current firmware on the device.
If you don't see like a secure check fail. Binary or something you should be good. Which would be displayed in download mode screen. And Odin would fail right off

I'm now back to stock with a v5 bootloader. I'm trying to follow this method but I am getting a "Re-Partition operation failed" error even though I don't have that option ticked. Do I need it ticked or have to use the pit file? I can't get a clear sense of what the pit file does from my googling.

TheMadScientist said:
I didn't mean to sound like a arse. This root method can be tricky is why I say read read read. A lot of people miss the section of upload mode errors and device software unauthorized screen
What is the current firmware on the device.
If you don't see like a secure check fail. Binary or something you should be good. Which would be displayed in download mode screen. And Odin would fail right off
Click to expand...
Click to collapse
I'm now back to stock with a v5 bootloader. I'm trying to follow this method but I am getting a "Re-Partition operation failed" error even though I don't have that option ticked. Do I need it ticked or have to use the pit file? I can't get a clear sense of what the pit file does from my googling.
(Sorry for double posting. I wasn't sure if you get a notification without me replying to you)

QuantumPie said:
I'm now back to stock with a v5 bootloader. I'm trying to follow this method but I am getting a "Re-Partition operation failed" error even though I don't have that option ticked. Do I need it ticked or have to use the pit file? I can't get a clear sense of what the pit file does from my googling.
(Sorry for double posting. I wasn't sure if you get a notification without me replying to you)
Click to expand...
Click to collapse
V5 is unrootsble and no downgrade. You might as well find a new device if you need root

Samsung Galaxy J3 2016 Firmware hidden.img stuck

Hello there,
I recently tried to get Android 10 onto my old phone. But i already got stuck on trying to root it. First I could not install new firmware because of FAP lock.
Then when I tried to get around the lock, I tried to root the phone with this tutorial. But Odin failed at hidden.img. Several times. And now I am stuck with "Firmware upgrade encountered an issue Select recovery mode in Kies".
I tried flashing with deleted hidden.img - it does not work. When I add an .md5 extension, Odin says binary invalid. When I remove the ".md5", Odin just crashes.
Any ideas?
If it is somehow important: I once rooted this device, but for some update or app, idk, i went back to normal, I dont really remember. I use Windows 10.
Thanks

tHr4sh3R said:
Hello there,
I recently tried to get Android 10 onto my old phone. But i already got stuck on trying to root it. First I could not install new firmware because of FAP lock.
Then when I tried to get around the lock, I tried to root the phone with this tutorial. But Odin failed at hidden.img. Several times. And now I am stuck with "Firmware upgrade encountered an issue Select recovery mode in Kies".
I tried flashing with deleted hidden.img - it does not work. When I add an .md5 extension, Odin says binary invalid. When I remove the ".md5", Odin just crashes.
Any ideas?
If it is somehow important: I once rooted this device, but for some update or app, idk, i went back to normal, I dont really remember. I use Windows 10.
Thanks
Click to expand...
Click to collapse
there is no Android 10 available for this phone

2gg1 said:
there is no Android 10 available for this phone
Click to expand...
Click to collapse
Well thank you, but that not helping with the issue that i cannot flash my phone with stock rom via odin.

tHr4sh3R said:
Well thank you, but that not helping with the issue that i cannot flash my phone with stock rom via odin.
Click to expand...
Click to collapse
So you have download the samsung drivers? Unzipped the file with result of a .md5 file? connected your phone to the pc with download mode? And then putted the file on the AP section? And clicked start?
Everything i just mentioned (except the .md5) can you find on HighOnAndroid website. Try to get the odin from there.
Please reply if it worked

2gg1 said:
So you have download the samsung drivers? Unzipped the file with result of a .md5 file? connected your phone to the pc with download mode? And then putted the file on the AP section? And clicked start?
Everything i just mentioned (except the .md5) can you find on HighOnAndroid website. Try to get the odin from there.
Please reply if it worked
Click to expand...
Click to collapse
Well yes, I already did all you described, but did not get it from HighOnAndroid (I also tried, but the "samsung drivers" are Malware which is blocked by Windows, so...).
I know how to flash a phone. It just does not work because of some weird Error with the hidden.img. I also saw a ton of other people trying to flash their phone with this Error, but their solutions do not work. So I need someone with another solution.

tHr4sh3R said:
Well yes, I already did all you described, but did not get it from HighOnAndroid (I also tried, but the "samsung drivers" are Malware which is blocked by Windows, so...).
I know how to flash a phone. It just does not work because of some weird Error with the hidden.img. I also saw a ton of other people trying to flash their phone with this Error, but their solutions do not work. So I need someone with another solution.
Click to expand...
Click to collapse
Try get the samsung drivers from samsungs official website

I once again tried it with these drivers. No change.
I just want to tell you, that I am no idiot and I know how to flash a phone. It just is a very specific problem, that occurs a lot apparently: https://www.youtube.com/results?search_query=flash+galaxy+hidden.img+stuck
The problem is, that the solutions posted on Youtube and other places do. not. work. As I explained in my starting post.