I bought a note 3 which probably came with 4.4.2 D3 firmware (last 2 letters) with singtel carrier. I OTA updated to 4.4.2 NH1 which is the latest update for singtel version. I tried downgrading the kernel for towelroot cause it needed < jun 2014 so I tried flashing ND3 firmware which failed. Then my device never worked and is always in download mode or it asks for kies recovery which i tried but never worked. I tried flashing like 6 different stock tar's with odin but all fail at the system.img point. Not using any PIT file. I've still not tried flashing the NH1 which i'm currently downloading. Not if this will also fail and i'll be bricked forever. Please HELP! I've tried at least 3 -4 diffrent tars but not NH1 tar so far
Note 3 N9005 32gb LTE 4G SM-9005 (Signtel Singapore)
Also i did not enable usb debugging at all, will that cause a problem?
Ok I tried nh1 firmware as well, it still failed at system ext4 write failure
Solution: Do Not install odin firmwares using vm ware fusion virtual machine. Run bootcamp for mac users and flash via odin in windows native
iamyohann said:
I bought a note 3 which probably came with 4.4.2 D3 firmware (last 2 letters) with singtel carrier. I OTA updated to 4.4.2 NH1 which is the latest update for singtel version. I tried downgrading the kernel for towelroot cause it needed < jun 2014 so I tried flashing ND3 firmware which failed. Then my device never worked and is always in download mode or it asks for kies recovery which i tried but never worked. I tried flashing like 6 different stock tar's with odin but all fail at the system.img point. Not using any PIT file. I've still not tried flashing the NH1 which i'm currently downloading. Not if this will also fail and i'll be bricked forever. Please HELP! I've tried at least 3 -4 diffrent tars but not NH1 tar so far
Note 3 N9005 32gb LTE 4G SM-9005 (Signtel Singapore)
Also i did not enable usb debugging at all, will that cause a problem?
Ok I tried nh1 firmware as well, it still failed at system ext4 write failure
Click to expand...
Click to collapse
You should show us your Odin error as well...
Do you have reactivation lock enabled?
You should enable the usb debugging for odin flash dude , why not enabling it !!??
alii91 said:
You should enable the usb debugging for odin flash dude , why not enabling it !!??
Click to expand...
Click to collapse
Do you even know what you're talking about? You don't need to activate USB Debugging.
USB Debugging is only for in the firmware adb usage. If he's in Download mode, whatever you set in the firmware does not apply anymore. It has its own Download Mode connection.
Yes man I know whay i said and he is talking about firmware adb and I'm talking because I had this problem many times until activated it
alii91 said:
Yes man I know whay i said and he is talking about firmware adb and I'm talking because I had this problem many times until activated it
Click to expand...
Click to collapse
Odin has no relation with USB Debugging/ADB.
It will not make a difference whether it is activated or not.
Also please read the OP, he is stuck in Download Mode, you can't access the system.
Ok maybe you're right I'm sorry, in this case checking the Samsung usb drivers on the pc and install the latest version of it ( could ) be the problem.
Solved
Solved the problem. It was vm ware fusion. Do not try odin on vmware fusion, it has problems. Installed windows, odin ran with succes, now i have knox 0x0 and root
iamyohann said:
Solved the problem. It was vm ware fusion. Do not try odin on vmware fusion, it has problems. Installed windows, odin ran with succes, now i have knox 0x0 and root
Click to expand...
Click to collapse
Parallels works perfectly as well.
Sent from my leanKernel 3.10 powered stock 4.4.2 (NF9) SM-N900T
iamyohann said:
Solved the problem. It was vm ware fusion. Do not try odin on vmware fusion, it has problems. Installed windows, odin ran with succes, now i have knox 0x0 and root
Click to expand...
Click to collapse
toastido said:
Parallels works perfectly as well.
Sent from my leanKernel 3.10 powered stock 4.4.2 (NF9) SM-N900T
Click to expand...
Click to collapse
Regardless, no one should be using a virtual machine to do something that may damage your warranty....
Yes it may work, but it's not true Windows you are working under, you are relying on USB device rerouting and hoping it will work. That bridge shouldn't be trusted, even if it might work as shown above, they are not under XDA's standard supported procedures.
Related
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?
After flashing 4.3 leak on my I9500 using Odin 3.09, it doesn't boot up as it should, I have wiped data/cache, but to no avail. I even flashed the Russian official 4.3 firmware, but it just doesn't boot up as it should.
When I turn on the phone, the phone stops right after the "Galaxy S4 I9500," screen. I see a black screen right after that.
I tried to downgrade my phone using Odin 3.09, 3.07 and 3.04, but it keeps failing. My S4 shows "unsupported version," when I try to flash stock 4.2.2.
I am guessing this is probably happening because of the newer bootloader, the newer bootloader is making it impossible to downgrade to an older version.
exclaimed said:
After flashing 4.3 leak on my I9500 using Odin 3.09, it doesn't boot up as it should, I have wiped data/cache, but to no avail. I even flashed the Russian official 4.3 firmware, but it just doesn't boot up as it should.
When I turn on the phone, the phone stops right after the "Galaxy S4 I9500," screen. I see a black screen right after that.
I tried to downgrade my phone using Odin 3.09, 3.07 and 3.04, but it keeps failing. My S4 shows "unsupported version," when I try to flash stock 4.2.2.
I am guessing this is probably happening because of the newer bootloader, the newer bootloader is making it impossible to downgrade to an older version.
Click to expand...
Click to collapse
ok try this first use the cf root provided in the cf root thread and then dload the latest 4.2.2 http://samsung-updates.com/details/14135/Galaxy_S_4_Exynos_Octa/GT-I9500/XFE/I9500XXUBMH1.html from here and flash it see what happens
Solved.
The problem was that I didn't flash the stock rom that came with my phone. I flashed that and my phone was restored to its factory settings. However my imei was messed up, it was showing me 0049. I rooted, flashed twrp recovery and used twrp to restore from a backup and I got my imei back along with my data.
I will wait for 4.3 to become flashable and see how it goes then.
hypergamer1231 said:
ok try this first use the cf root provided in the cf root thread and then dload the latest 4.2.2 http://samsung-updates.com/details/14135/Galaxy_S_4_Exynos_Octa/GT-I9500/XFE/I9500XXUBMH1.html from here and flash it see what happens
Click to expand...
Click to collapse
Hi, I got back from version 4.2.2 to say. Thank you. But the 4.2.2 's what I want to install other versions (eg Russian version) still odin error. Is it possible to install other versions?
volkantipi said:
Hi, I got back from version 4.2.2 to say. Thank you. But the 4.2.2 's what I want to install other versions (eg Russian version) still odin error. Is it possible to install other versions?
Click to expand...
Click to collapse
i had this issue on my gs3 , try to move the odin md5 rom file and the odin folder to C: or my documents . maybe one of those directories where u have them right now are too large (odin has issues with long directories)
I am having an issue to where any time i try to flash anything it is failing. i have reinstalled all the drivers and its using the oem cord and my drivers for my usb ports are installed. i have re downloaded the modem and even the stock tar and it is still failing any help would be great.
tcooper85 said:
I am having an issue to where any time i try to flash anything it is failing. i have reinstalled all the drivers and its using the oem cord and my drivers for my usb ports are installed. i have re downloaded the modem and even the stock tar and it is still failing any help would be great.
Click to expand...
Click to collapse
What phone do you have? SPH-L720 or or the L720T?
What did you try to Odin? - Recovery, CF-Autoroot? etc. Full Stock .tar? And why just modem?
Did you run Odin as administrator?
Did the device show up at all - any comm port in Odin?
Is the phone new?
Was it ever rooted?
leaderbuilder said:
What phone do you have? SPH-L720 or or the L720T?
What did you try to Odin? - Recovery, CF-Autoroot? etc. Full Stock .tar? And why just modem?
Did you run Odin as administrator?
Did the device show up at all - any comm port in Odin?
Is the phone new?
Was it ever rooted?
Click to expand...
Click to collapse
Got the L720T
i used odin 1.85 and 3.x
yes i ran as admin
yes it shows up in comm port
newish yes
yes it was rooted.
tcooper85 said:
Got the L720T
i used odin 1.85 and 3.x
yes i ran as admin
yes it shows up in comm port
newish yes
yes it was rooted.
Click to expand...
Click to collapse
So the T version has it's own thread.
You CANNOT flash .tars for the standard 720. That's your problem.
Please go here and read through the entire thread.
i was on 4.3 on my galaxy note3 32gb CYO and wanted to change to 4.4.2 for COS (greek provider) i used odin and failed saying odin invalid ext4 image i used the .pit file and enabled the re-partition im using the official cable and tried both usb 2 and 3 ports same problem. also installed samsung drivers for this device. Im running windows 8.1 if this helps at all
SiLeNtOnegr said:
i was on 4.3 on my galaxy note3 32gb CYO and wanted to change to 4.4.2 for COS (greek provider) i used odin and failed saying odin invalid ext4 image i used the .pit file and enabled the re-partition im using the official cable and tried both usb 2 and 3 ports same problem. also installed samsung drivers for this device. Im running windows 8.1 if this helps at all
Click to expand...
Click to collapse
I also had issues when I first tried rooting my phone with odin. I ended up using Kingo to root my phone at first. After that it has been smooth sailing flashing custom roms. I am assuming you are running a rooted 4.3 or are you on a stock 4.3 trying to flash to an official kitkat?
Sent from my SM-N900V using XDA Free mobile app
Hello all,
I recently had to factory reset my phone to bring it in for a screen problem, I used SU to fully unroot & my phone has been stuck in a bootloop since. I have tried to reflash the stock rom, but Odin version 3.09 is getting stuck at setup connection, I have also tried using a .pit file but Odin get stuck at nand flash write or something similar.
I have a Galaxy s7 Edge BTU, all the files are for BTU region, I have also flashed back to stock on many galaxy S range phones. Just don't know what is going wrong.
Things I've tried
Odin 3.09
Odin 3.12.3
Different USB ports
Different USB Cables
Reinstalled USB drivers
I have used the 4 files from the stock firmware.zip
I also used a .pit file for EUR HERO2LTE_EUR_OPEN_SAMFIRM.NET.pit (Used along with the 4 firmware files)
I normally just use the 4 files on my previous phones & all was well.
Can someone please help.
EDIT: I managed to get into recovery & mount usb storage, I put a custom rom on the phone & flashed it. It fixed the partition issues & booted up, I then flashed stock everything using Odin.
You need Odin 3.11.1.
nitrous² said:
You need Odin 3.11.1.
Click to expand...
Click to collapse
Thanks for the information, I'll download it & keep it handy for after the repair to re-root.