Hello Guys,
I'm stuck with my Samsung Galaxy S4. It's a GT-I9505 by Vodafone Germany. I came from stock Samsung Firmware 4.22 and wanted to root by using Odin3 an CF-Auto-Root. When flashing the cf-auto-root....tar.md5 Odin showed FAIL instead of PASS.
I think my big mistake was, not to switch the phone to USB-debugging ON. I forgot this. So now, when booting, the device asks me to do the emergency recovery with Samsung KIES. But unfortunately this doesn't work. Kies says Phone not connected. What can i do?
As far as i can figure out, i crashed the kernel with this flashing-attempt. i read something about using a PIT-File and a stock-rom to fix this.
Luckily i can boot to download-mode and also Odin seems to realize, that i plugged in the phone.
I would be VERY happy and thankful, if someone could give me a hint or even better a step-by-step instruction, how to get my Galaxy S4 back to work. Even with the stock Firmware. At least, it's working again....but how can i manage it?
Thanks guys!
Alex.
Look in the i9505 forum for a stock firmware tar and flash it via Odin and you will be back 100% stock as if you just bought it. Instructions for flashing the stock firmware tar will be in the post. I would search and link you but on my phone.
Sent from my SGH-M919 using xda app-developers app
Adam0524 said:
Look in the i9505 forum for a stock firmware tar and flash it via Odin and you will be back 100% stock as if you just bought it. Instructions for flashing the stock firmware tar will be in the post. I would search and link you but on my phone.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
MAy be you have a link for me? I'm new to this forum and site....
Thanks a lot!
Sy36 said:
MAy be you have a link for me? I'm new to this forum and site....
Thanks a lot!
Click to expand...
Click to collapse
Here ya go http://forum.xda-developers.com/showthread.php?t=2252982
Its possible you had a corrupted cf-autoroot image. If you have an MD5 on the stock rom you download, use ODIN 3.04 or 3.07 to flash as they check the MD5 sums before flashing as long as the rom has an MD5 extension - .tar.md5.
ultramag69 said:
Its possible you had a corrupted cf-autoroot image. If you have an MD5 on the stock rom you download, use ODIN 3.04 or 3.07 to flash as they check the MD5 sums before flashing as long as the rom has an MD5 extension - .tar.md5.
Click to expand...
Click to collapse
FIRST OF ALL:
Thank you very much for helping me!
I got my SGS4 back working! :laugh::laugh::laugh:
But it wasn't done with only flashing a stock ROM. I also had to use a PIT file for repartioning the phone.
Another trick (or was it just coincident?) was, i had to use to ORIGINAL usb-cable for flashing. First i used a third-party usb-cable. May this was also an issue.
So in the end, i followed this howto:
wccftech.com/how-to-unbrick-samsung-galaxy-s4
i downloaded the PIT-file and the stock firmware, recommended by Adam0524, from further above.
I hope my mistakes while flashing my SGS4 and the solution i found may help others, who run into the same problem. So if you have trouble flashing your S4's and get a FAIL message in Odin, but if you can still enter the download-mode, there will be a great chance to get it back working.
What you'll need is:
Odin 3.07
Stock firmware for GT-I9505 (about 1,7 GB)
PIT-File for your GT-I9505 (about 3 KB)
ORIGINAL Samsung usb-cable (!)
and relax, everything will be good in the end
P.S.: I'm so glad that my S4 is working again...!!!!! :laugh:
Your problem was in usb cable.
Btw, usb debug has to do nothing with flashing with odin. It is used only when you are booted in OS
Sent from my Galaxy
Also, just as a caution to all noob flashers, god that sounds rude, remember that flashing a pit file is generally the LAST thing you do before sending it back to Samsung... There is a very large amount of risk in flashing pit files. If you have the wrong one, this happens a lot with people new to playing with their phones, the file is corrupt or you just do something bad then you can end up with a true brick...
I have an S3 that someone played around with. I can boot to download mode, no recovery and can't repartition... Needs j-tag when I get the time....
i9505 bricked
I've been running 4.2.2 stock rooted with CF autoroot and using Philz recovery when tried to flash 4.3 through Mobile Odin, and I ended up having my phone bricked. It only goes in download mode and when trying to recover from kies it gets stuck in the same screen where it shoes *** SV REV. CHECK FAIL : Fused : 3 , Binary : 1 *** I desperately need some help with this guys.
Thanks in advance.
rubnduardo said:
I've been running 4.2.2 stock rooted with CF autoroot and using Philz recovery when tried to flash 4.3 through Mobile Odin, and I ended up having my phone bricked. It only goes in download mode and when trying to recover from kies it gets stuck in the same screen where it shoes *** SV REV. CHECK FAIL : Fused : 3 , Binary : 1 *** I desperately need some help with this guys.
Thanks in advance.
Click to expand...
Click to collapse
Hows it? I think you would have figured by now. Just flash a stock ROM via download mode / Odin
Btw, OP I was shocked that you wrote CF-Autoroot bricked your device, it is by far the safest root method available. As you have aknolwedged later it is not a problem caused by it.
dogmatism said:
Hows it? I think you would have figured by now. Just flash a stock ROM via download mode / Odin
Btw, OP I was shocked that you wrote CF-Autoroot bricked your device, it is by far the safest root method available. As you have aknolwedged later it is not a problem caused by it.
Click to expand...
Click to collapse
It was a problem with the bootloader as we all know android 4.3 has new ones -.-! I felt like the biggest noob ever. Do you happen to know about a GPe based rom for i9505?
Related
Hello everybody im in a little bit of a crisis.
I tried to update my modem to MK2 and I used odin to do so. It turns out that it failed for some reason.
After that whenever I boot my phone it gives me a black screen and says Firmware Upgrade encountered an issue. Please select recovery mode in Kies and try again.
After that I followed this youtube video right here: https://www.youtube.com/watch?v=G1jyZ5QafAQ and downloaded this file to go back to stock: http://downloadandroidfiles.org/download-l720vpuamdc_l720sptamdc_spr-zip/
But yet it still gave me a Fail in odin. Any help would be appreciated as I am Freaking out right now
Here is the message log directly from odin when it starts
Firmware update starts
aboot.mbn
NAND write start
Complete(Write) Operation Failed
I switched USB ports now Odin is saying there is no PIT partition
88exp88 said:
Hello everybody im in a little bit of a crisis.
I tried to update my modem to MK2 and I used odin to do so. It turns out that it failed for some reason.
After that whenever I boot my phone it gives me a black screen and says Firmware Upgrade encountered an issue. Please select recovery mode in Kies and try again.
After that I followed this youtube video right here: https://www.youtube.com/watch?v=G1jyZ5QafAQ and downloaded this file to go back to stock: http://downloadandroidfiles.org/download-l720vpuamdc_l720sptamdc_spr-zip/
But yet it still gave me a Fail in odin. Any help would be appreciated as I am Freaking out right now
Click to expand...
Click to collapse
If your on MJA/MK2 firmware (bootloader) you cannot go back to MDC (the file you showed).
Also did you run PC Odin 'As Administrator'?
You can find the link to the MK2 here.
leaderbuilder said:
If your on MJA/MK2 firmware (bootloader) you cannot go back to MDC (the file you showed).
Also did you run PC Odin 'As Administrator'?
You can find the link to the MK2 here.
Click to expand...
Click to collapse
I am on MDC bootloader. What I did was download the tar file from stockroms.net for MDC. And I ran the 3.07 odin as adimistrator and it worked. Thank you cause I think that it was me not clicking run as administrator. Another question: Is it worth upgrading to MK2 if I wanna root again or should I just keep MK2. I have the geeksquad warrenty from bestbuy so it shouldn't matter if it trips the knox flag because I give them rooted phones all the time.
88exp88 said:
I am on MDC bootloader. What I did was download the tar file from stockroms.net for MDC. And I ran the 3.07 odin as adimistrator and it worked. Thank you cause I think that it was me not clicking run as administrator. Another question: Is it worth upgrading to MK2 if I wanna root again or should I just keep MK2. I have the geeksquad warrenty from bestbuy so it shouldn't matter if it trips the knox flag because I give them rooted phones all the time.
Click to expand...
Click to collapse
I wouldn't update to the knox bootloader (take the OTA or flash the full .tar) but that's me, for now.
Since you're on the earlier bootloader you can still update to any number of ROMs that have the knox bootloader removed.
Also I would definitely update the modem firmware - Unknownforce has a thread for that here.
Spend some time and read and you'll find loads of stuff you can do.
Good luck.
leaderbuilder said:
I wouldn't update to the knox bootloader (take the OTA or flash the full .tar) but that's me, for now.
Since you're on the earlier bootloader you can still update to any number of ROMs that have the knox bootloader removed.
Also I would definitely update the modem firmware - Unknownforce has a thread for that here.
Spend some time and read and you'll find loads of stuff you can do.
Good luck.
Click to expand...
Click to collapse
So I can use the files http://forum.xda-developers.com/showthread.php?t=2338919 in odin to update. Also since I am on mdc could I just use the latest in odin or do I have to go incrementaly.
Sent from my SPH-L720 using xda app-developers app
If you truly are on MDC and did not trip the knox bootloader you can Odin back to stock MDC. That will wipe the phone completely, giving you an all MDC phone - bootloader, recovery (stock), kernel, modem and ROM.
But I would just jump to MF9. It was the last official without the Knox bootloader. You can grab that here.
This is the FULL system tar. All stock, kernel, recovery, ROM Modem.
Extract the .tar.md5 and place that in the PDA slot and that's it. Make sure you don't check 'repartition'!.
Then use CF-Autoroot to root and again be careful NOT to check anything like repartition etc.
Once rooted you can then open up supersu, update the binaries. Go to playstore and download GooManager. User that to install custom recovery and then you can flash away.
I do suggest you spend some time here reading a whole bunch. You'll learn a lot about these methods and how and what you can do.
Good luck.
leaderbuilder said:
If you truly are on MDC and did not trip the knox bootloader you can Odin back to stock MDC. That will wipe the phone completely, giving you an all MDC phone - bootloader, recovery (stock), kernel, modem and ROM.
But I would just jump to MF9. It was the last official without the Knox bootloader. You can grab that here.
This is the FULL system tar. All stock, kernel, recovery, ROM Modem.
Extract the .tar.md5 and place that in the PDA slot and that's it. Make sure you don't check 'repartition'!.
Then use CF-Autoroot to root and again be careful NOT to check anything like repartition etc.
Once rooted you can then open up supersu, update the binaries. Go to playstore and download GooManager. User that to install custom recovery and then you can flash away.
I do suggest you spend some time here reading a whole bunch. You'll learn a lot about these methods and how and what you can do.
Good luck.
Click to expand...
Click to collapse
Hey man, just wanted to say thanks for continuing your tradition of quality posting. It is responses like this that made the E4GT forums such a great place to be.
leaderbuilder said:
If you truly are on MDC and did not trip the knox bootloader you can Odin back to stock MDC. That will wipe the phone completely, giving you an all MDC phone - bootloader, recovery (stock), kernel, modem and ROM.
But I would just jump to MF9. It was the last official without the Knox bootloader. You can grab that here.
This is the FULL system tar. All stock, kernel, recovery, ROM Modem.
Extract the .tar.md5 and place that in the PDA slot and that's it. Make sure you don't check 'repartition'!.
Then use CF-Autoroot to root and again be careful NOT to check anything like repartition etc.
Once rooted you can then open up supersu, update the binaries. Go to playstore and download GooManager. User that to install custom recovery and then you can flash away.
I do suggest you spend some time here reading a whole bunch. You'll learn a lot about these methods and how and what you can do.
Good luck.
Click to expand...
Click to collapse
Ok I have upgraded to MF9 now should I use Unkown Forces links: http://forum.xda-developers.com/showthread.php?t=2338919 to upgrade the firmware and modem?
And when I try to root with CF auto root on MF9 it fails on complete write operation failed.
Strike that its all good
If you're on MF9 full rooted you can update your firmware/modem following Unknownforce's instructions.
HOWEVER PLEASE take heed about the MJA(MK2 too) Notes: ...
some people report better success with turning Auto Reboot and F. Reset Time unchecked. Do the same flash, but when you see PASS on Odin, unplug the phone and Hold the Power key for 10 seconds to reboot.
Click to expand...
Click to collapse
And read through the whole post not just the OP. Some people had to flash it a few times to get it to show up (in system info) properly - mainly because they didn't follow directions precisely and skipped the note part on MJA/MK2.
Since you're now on MF9 fully rooted (stock) you can install yourself a custom recovery (Philz or TWRP - the latest Philz;philz_touch_6.08.9-jfltespr, seems to be the most reliable for now) and flash some ROMs. Virtually all of the 4.3/4.4 ROMs require the MK2 modem so know that too.
One thing I would highly recommend is to spend some time reading through the sections to get a clearer understanding of how this device behaves vs others (HTC, Moto etc.). Every device has it's peculiarities and caveats and not paying attention to them could ruin you day.
i have a different problem. i think my sprint sph-l720 bricked because my screen is stuck on kernel is not seandroid enforcing and it also says set warrant bit: kernel. need help as soon as possible
Tonymontana2421 said:
i have a different problem. i think my sprint sph-l720 bricked because my screen is stuck on kernel is not seandroid enforcing and it also says set warrant bit: kernel. need help as soon as possible
Click to expand...
Click to collapse
People need to know the difference between soft bricked and hard bricked. Most say bricked and they mean soft. Hard is nearly impossible to get the phone back up and running. I have that same problem when I try to install a kernel. You need to reflash a ROM.
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
People need to know the difference between soft bricked and hard bricked. Most say bricked and they mean soft. Hard is nearly impossible to get the phone back up and running. I have that same problem when I try to install a kernel. You need to reflash a ROM.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
can you tell me which rom i need to flash because i cant figure out what rom i need to use in odin
i was flashing mk2 on my mf3 with Odin because my phone won't update, and it failed so i disconnected the device and it says "firmware upgrade encountered an issue" i tried Kies firmware upgrade and initialization, but it's stuck on 0%. need serious help.
ryujeff said:
i was flashing mk2 on my mf3 with Odin because my phone won't update, and it failed so i disconnected the device and it says "firmware upgrade encountered an issue" i tried Kies firmware upgrade and initialization, but it's stuck on 0%. need serious help.
Click to expand...
Click to collapse
Try the MK2 firmware again through ODIN. You might need to redownload it to make sure it was a good download. Make sure you check the check sum to make sure it matches.
scott14719 said:
Try the MK2 firmware again through ODIN. You might need to redownload it to make sure it was a good download. Make sure you check the check sum to make sure it matches.
Click to expand...
Click to collapse
use odin kies is useless i havent bee able to use kies sinc e intalling different roms
ron31 said:
use odin kies is useless i havent bee able to use kies sinc e intalling different roms
Click to expand...
Click to collapse
I'm pretty sure that's what i told him to do..."use ODIN".
scott14719 said:
I'm pretty sure that's what i told him to do..."use ODIN".
Click to expand...
Click to collapse
my main point was kies is useless
ryujeff said:
i was flashing mk2 on my mf3 with Odin because my phone won't update, and it failed so i disconnected the device and it says "firmware upgrade encountered an issue" i tried Kies firmware upgrade and initialization, but it's stuck on 0%. need serious help.
Click to expand...
Click to collapse
I dunno if u used this files in the first place from my thread.... http://forum.xda-developers.com/showthread.php?t=2621279 .....btw just follow post#2.... u should be updating to MK2 just fine .....Goodluck. ..:thumbup:
Swyped from MK2 Dark Venom SS Edition
ted77usa said:
I dunno if u used this files in the first place from my thread.... http://forum.xda-developers.com/showthread.php?t=2621279 .....btw just follow post#2.... u should be updating to MK2 just fine .....Goodluck. ..:thumbup:
Swyped from MK2 Dark Venom SS Edition
Click to expand...
Click to collapse
yes! that's the one i used but after few minutes, odin says FAIL. i retried but it didn't work. it's just stuck on 0%
Now i'll try MF3 with odin, but i can't find the MF3 tar file. can you please help?
scott14719 said:
Try the MK2 firmware again through ODIN. You might need to redownload it to make sure it was a good download. Make sure you check the check sum to make sure it matches.
Click to expand...
Click to collapse
Odin is the first thing I tried
I ran into a very similar problem a while back and this is how i fixed my problem. Here's some history first...I have the SGH-I337, Model # GT-I9505
Android Ver: 4.3
Baseband Ver: I337UCEMK2
Kernel: 3.40-faux123-JB4.3-Custom
Build #: JSS15J.I9505XXUEML6
ROM: FoxHound Diamond Dogs 3.6 (in my opinion the greatest ROM)
I was trying to update my modem from the I337UCUAMDL firmware to the I337UCEMK2 firmware via mobile Odin. When my rebooted I was left with a black screen with red lettering stating something about unauthorized firmware. I could not boot into the ROM (not even safe mode), couldn't boot into my recovery but i could get into download mode. I connected to Kies and did an emergency firmware upgrade and yes it does take a while to download the firmware and flash the phone. Now my phone was back to stock so I had to re-root the phone, which i did successfully, loaded my custom recovery, did a nandroid backup and finally flashed the FoxHound 3.6 ROM. The interesting part is that from the first time I rooted my S4 I only had a little over 2gb of internal storage. After I redid everything after the Kies emergency firmware upgrade I had over 6gb of internal storage. Anyway, I found a flashable modem zip that could be flashed within my recovery and it worked like a champ, bringing my baseband version from the AMDL to the MK2. I can't remember where I found it but it is in one of XDA's AT&T galaxy s4 forums. I also have the zip file if you can't find it and would like me to help.
I take NO credit for the root method, the custom recovery or the custom ROM that are mentioned above. I have the utmost respect for these and all developers here on XDA.
Hello guys, so i sold my AT&T Galaxy S4 to a friend an move up to Note 3.
After a couple of weeks he downloaded an app from Playstore and got into a Bootloop. I tol;d him i could help him as I have come through the same procedure again in the past.
I tried flashing the same rom the phone had by that time "I337UCUFMLD_OneClick" and i Got a FAIL.
Soon i realized the phone was bricked. I have been searhing for 5-6 hours today, tried to flash "ALL_ATT_I337UCUFNB1_I337ATTFNB1_505595_REV06_user_low_ship_MULTI_CERT.tar", all MK2 roms I Found here, and the only once which worked was flashing the "pit" file and flashing "I337_NC1_Stock_Recovery.tar". Now The phone has access to both Download & recovery mode but
i 'cant enable usb debugging cause i can't access the system.
If anyone has a clue, please help!
PS: Sry for the long description, can't post links.
You should be able to flash the all in one nb1 tar use Odin 3 v1.85 make sure you extract the rar and load the tar in the pda slot. Unless it's been updated to nc1 then you'll have to wait and hope someone releases a all in one for that.
Sent from my SGH-I337. And no we can't flash Aosp based ROMs with a locked bootloader!
dave5777 said:
You should be able to flash the all in one nb1 tar use Odin 3 v1.85 make sure you extract the rar and load the tar in the pda slot. Unless it's been updated to nc1 then you'll have to wait and hope someone releases a all in one for that.
Sent from my SGH-I337. And no we can't flash Aosp based ROMs with a locked bootloader!
Click to expand...
Click to collapse
Thanks for the quick responce!
Nope, i flashed only the stock recovery from NC1 cause it was the only one i could find
Att recently pushed the nc1 firmware if your friend unknowingly applied the nc1 update and it flashed a new bootloader then that would make the nb1 Odin fail. I think your best bet is going to the Samsung Rep at your local Best buy and they can flash the factory image.
Sent from my SGH-I337. And no we can't flash Aosp based ROMs with a locked bootloader!
dave5777 said:
Att recently pushed the nc1 firmware if your friend unknowingly applied the nc1 update and it flashed a new bootloader then that would make the nb1 Odin fail. I think your best bet is going to the Samsung Rep at your local Best buy and they can flash the factory image.
Sent from my SGH-I337. And no we can't flash Aosp based ROMs with a locked bootloader!
Click to expand...
Click to collapse
Thanks for the advice, we were about to after the weekend.
PS: I tried flashing using 1.85 ... reaches 90% of SYSTEM and fails...
dave5777 said:
Att recently pushed the nc1 firmware if your friend unknowingly applied the nc1 update and it flashed a new bootloader then that would make the nb1 Odin fail. I think your best bet is going to the Samsung Rep at your local Best buy and they can flash the factory image.
Sent from my SGH-I337. And no we can't flash Aosp based ROMs with a locked bootloader!
Click to expand...
Click to collapse
It has been reported that the NC1 update did not incriment the Q-fuse count in aboot. If this is true, it should be safe to Odin NB1 back onto a phone that took the NC1 update without it causing failure..
Solution
dave5777 said:
You should be able to flash the all in one nb1 tar use Odin 3 v1.85 ... !
Click to expand...
Click to collapse
After several tries i managed to flash it back to STOCK NB1 with no problem.
The only Problem some people may have is that if you try flashing with odin 3+ and then try 1.85, you will fail due to Windows instabilitty.
I recommend taking battary of the phone for 1 hour (may sound too much but worked for me) restart PC, and try flashing right away after your computer boots up!
I will propably make a guide out of this cause that brick was tricky as hell.
Thanks everyone for replying
PROBLEM SOLVED :good:
Okay so I've searched the forums and haven't found the answer to what I'm looking for quite yet. I'm not new to rooting, but new to the Galaxy Note 3. I just recently started getting prompted for the update to KK4.4.2 (I have the Verizon model and we all know how long they take to push out updates.) So I decided to flash the leaked de-oxed NC2 rom and after follow the instructions from here. I reboot and get stuck at a black screen. It boots no further and I have to pull the battery to get back to recovery.
Am I missing something, another step maybe? Is this an old process?
Any help would be appreciated. Thanks
Did you also flash the firmware package in odin?
<Note3>
LeftyGR said:
Did you also flash the firmware package in odin?
<Note3>
Click to expand...
Click to collapse
Yes I also flashed the firmware through Odin. Does it matter which version of Odin I used?
Odin doesn't matter.
Root 4.3
Install safe strap.
Now you can update to the rooted 4.4 through odin.
barrackOBAMA said:
Odin doesn't matter.
Root 4.3
Install safe strap.
Now you can update to the rooted 4.4 through odin.
Click to expand...
Click to collapse
Actually it looks as if this was caused by Odin 3.09. It doesn't seem to like the bootloader file for NC2 and for some reason doesn't load the entire boot portion of the file. Flashed with Odin 3.07 and booted no problem. Thanks for the input though.
My Galaxy s7 broke down and had to go back to my old galaxy s4, but I have a big problem or small, want to install this room but I can not install any recovery.
I tried everything in these last two days, stock rooms SamMobile, kernel's, TWRP, ROM Manager, philz Touch via odin .... via zip file ..... bootloader and modem .... pit files ... .pages and pages on xda ... different odin, cables.....everything
And always appears this error
E: footer is wrong
E: signature verification failed
If anyone can give help to fix this I am very appreciated, I want to install this room, but it's complicated
Thank you in advance
And sorry for my bad english
What is the phone's model number? The errors appear on Odin? What bootloader version is on the phone?
Galaxy S4
GT-I9505
4.4.2
I9505XXUGNJ8
bootloader .......where I see the bootloader?
audit13 said:
What is the phone's model number? The errors appear on Odin? What bootloader version is on the phone?
Click to expand...
Click to collapse
In the Odin no errors, everthing is ok
Galaxy s4
GT-I9505
4.4.2 stock room
i9505xxugnj8
where I see the bootloader?
Stock firmware firmware from Odin includes stock recovery.
Flash again with Odin by doing this: uncheck everything in Odin except f reset time, flash rom, when you see the word reset in the status window, remove USB cable from phone, remove battery for three seconds, replace battery, use buttons to boot directly to recovery, factory reset/wipe, reboot.
believe it or not I've done it in a post here on xda, I tried everything
different computers, even if the smartphone is original
Tiaguinho said:
believe it or not I've done it in a post here on xda, I tried everything
different computers, even if the smartphone is original
Click to expand...
Click to collapse
Is the phone rooted? Or can you root it?
If it is or you manage to root it, you should be able to flash a twrp.img file via Flashify.
yes, is rooted
GDReaper with Flashify I made it
finally yupiiiiiiiii
Thank you all for the great help, problem solved
thank you .... thank you, saved the day
thank you to all