[Q] ODIN fails at 'system.img.ext4' - 4.3 with KNOX bootloader - Galaxy S 4 Q&A, Help & Troubleshooting

ODIN keeps failing at 'system.img.ext4' - 4.3 with KNOX bootloader
Hi guys
I've recently tried to flash a 4.3 stock rom via Odin and it failed, and I now have a bricked phone that has this warning:
PHONE-----YELLOW TRIANGLE----- COMPUTER
'Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
I tried to flash the latest KNOX bootloader roms via ODIN to boot up the phone, however....
ODIN keeps hanging on the "system" flashing command and goes to a red "fail". It won't start flashing "system.img.ext4.... etc"
I've tried all versions of ODIN and all version of 4.3
I can't use any 4.2.2 roms as the phone only seems to accept 4.3 stock roms now.
Do you guys know why ODIN keeps failing at flashing 'system.img.ext4' ?
Any advice would be greatly appreciated, thanks!

how to fix odin fail
Hey guys
I found a way to fix my ODIN flashing errors (with system.img.ext4)
Install SAMSUNG USB drivers from here: http://forum.xda-developers.com/showthread.php?t=2038555
Make sure you are NOT using VMWare Fusion on Mac OS X.
Bootcamp your Mac if you have to (with 64 bit Windows 7 preferably), or borrow a friends' Windows laptop.
My biggest mistake was running VMWare Fusion on Mac OS X - the new KNOX bootloader/roms doesn't like being flashed on virtual Windows PC
Odin flash PDA should work perfectly fine now
I finally saved my phone from being a brick after 36 hours!!!!

Thanks for this - I too was attempting to do this using VM Fusion. Sorted once I flashed on a non virtual machine.

VMWare Fusion
I had the exact same issue using Odin from VMWare Fusion. Since I didn't have a PC handy, I had Parallels installed on my other mac. I was able to successfully flash the new ROM via my Parallels VM.

I Just flash the PIT file form 4.2.2 after flash 4.3 and everything is ok.
Wysłane z mojego GT-I9506 przy użyciu Tapatalka

I have the same problem but in windows
Hello community
can someone get me some instructions to solve this on a windows 8.1 notebook
S4 mini I9195 - Spanish Vodafone phone, flagged already with KNOX 0x1
4.2.2. android
Thank you in advance

orchid18 said:
I had the exact same issue using Odin from VMWare Fusion. Since I didn't have a PC handy, I had Parallels installed on my other mac. I was able to successfully flash the new ROM via my Parallels VM.!
Click to expand...
Click to collapse
Oh Geez! Wish I had found this post hours ago...

Thank so much!
orchid18 said:
Hey guys
I found a way to fix my ODIN flashing errors (with system.img.ext4)
Install SAMSUNG USB drivers from here: http://forum.xda-developers.com/showthread.php?t=2038555
Make sure you are NOT using VMWare Fusion on Mac OS X.
Bootcamp your Mac if you have to (with 64 bit Windows 7 preferably), or borrow a friends' Windows laptop.
My biggest mistake was running VMWare Fusion on Mac OS X - the new KNOX bootloader/roms doesn't like being flashed on virtual Windows PC
Odin flash PDA should work perfectly fine now
I finally saved my phone from being a brick after 36 hours!!!!
Click to expand...
Click to collapse
very nice! Thank! This worked for me. After 7 hours make trying recover my mini s4!

orchid18 said:
Hey guys
I found a way to fix my ODIN flashing errors (with system.img.ext4)
Install SAMSUNG USB drivers from here: http://forum.xda-developers.com/showthread.php?t=2038555
Make sure you are NOT using VMWare Fusion on Mac OS X.
Bootcamp your Mac if you have to (with 64 bit Windows 7 preferably), or borrow a friends' Windows laptop.
My biggest mistake was running VMWare Fusion on Mac OS X - the new KNOX bootloader/roms doesn't like being flashed on virtual Windows PC
Odin flash PDA should work perfectly fine now
I finally saved my phone from being a brick after 36 hours!!!!
Click to expand...
Click to collapse
I have the same problem with my s5 mini (dual sim) sm-g800H, Odin fails just when it starts system.img.ext4. Any help with this, i have tried it on a couple of Windows 7 pcs using different USB cables and different Odin versions, any idea how to solve this?

Kitkat
if you have installed Stock Kitkat or Custom 4.4.2 Touchwiz rom [some roms support rolling back and others don't], you won't be able to roll back to 4.3 . i had this problem when i tried to roll back to 4.3 from 4.4.2
Fix : install latest Kitkat firmware

Al_Jourgensen said:
Hello community
can someone get me some instructions to solve this on a windows 8.1 notebook
S4 mini I9195 - Spanish Vodafone phone, flagged already with KNOX 0x1
4.2.2. android
Thank you in advance
Click to expand...
Click to collapse
1.install samsung usb driver
2. find your mobile model and download single .tar image from sammobile
3. flash through odin(tick only F.reset time and auto reboot)

Odin Fail with VMWare Fusion on Mac: The below worked for me
This post is late to this thread: Wanted to share what worked for me for Verizon SCH-I545 Samsung Galaxy S4:
* Used Windows 7 on VMWare Fusion 7.0.1 on MacBook Air; Odin 3.09
* Experienced same Odin failure for "system.img.ext4" during process; this fixed it.
* Change Fusion USB Settings: Close Windows but not Fusion. Go to "Fusion Settings/USB & Bluetooth". Go to "Advanced USB options" and select "USB Compatibility" USB 1.1.
* Restart Fusion and restart Windows.
* I used TAR file "I545VRUFNC5_I545VZWFNC5_I545VRUFNC5_HOME.tar.md5" inside downloadable file "I545VRUFNC5_I545VZWFNC5_VZW" which was downloaded from URL: sammobile.com/firmwares/database/SCH-I545
* Note: I joined this website for 1 week to take advantage of faster download speeds. I tried without joining and the download timed out before the download was completed. Speed was much faster with membership.
* Prep phone for download by pressing 3-buttons "Power-Home-Volume Down". Note: Be sure to hold down the "Volume Down" portion of the button and not the complete Volume button. Press Volume Up when prompted on screen by the phone.
* Start Odin 3.0.9
* Plug in phone using USB cable that came with phone. Other cables may work - but I don't know.
* Odin will indicate that the phone was "Added"
* Be sure to select in Odin the Options "Auto Reboot" and "F. Reset Time". Select "AP" and go to file to add: "I545VRUFNC5_I545VZWFNC5_I545VRUFNC5_HOME.tar.md5"
* Adding this file takes a few seconds. Once added click "Start"
* The process seemed to take quite a bit of time, likely due to it being a USB 1.1 but it eventually took.
* Once it "Passed" in Odin the phone was on the red Verizon screen for about 3 minutes and then indicated it was updating the apps
* Once apps were updated the phone was in startup mode
* It worked fine and was back to normal.
* Close Windows, and reset Fusion USB settings back to USB 2.0.
* Note: I use USB 2.0 settings in Fusion as Windows 7 doesn't recognize USB 3.0 and Windows (in Windows Explorer) has difficulties, when USB 3.0 is selected, recognizing many connected USB devices even though Fusion indicates these devices are connected.
Hope this works. Thanks to the many folks on this thread and in this forum who assisted me in determining a solution.

you saved my life !!!!
thanks
it works with parallel desktop.

I'm still having that problem.
orchid18 said:
Hey guys
I found a way to fix my ODIN flashing errors (with system.img.ext4)
Install SAMSUNG USB drivers from here: http://forum.xda-developers.com/showthread.php?t=2038555
Make sure you are NOT using VMWare Fusion on Mac OS X.
Bootcamp your Mac if you have to (with 64 bit Windows 7 preferably), or borrow a friends' Windows laptop.
My biggest mistake was running VMWare Fusion on Mac OS X - the new KNOX bootloader/roms doesn't like being flashed on virtual Windows PC
Odin flash PDA should work perfectly fine now
I finally saved my phone from being a brick after 36 hours!!!!
Click to expand...
Click to collapse
i have downloaded drivers but this time when that fails. it just moved little bit but still fails

Swapnil Soni said:
i have downloaded drivers but this time when that fails. it just moved little bit but still fails
Click to expand...
Click to collapse
orchid18 said:
ODIN keeps failing at 'system.img.ext4' - 4.3 with KNOX bootloader
Hi guys
I've recently tried to flash a 4.3 stock rom via Odin and it failed, and I now have a bricked phone that has this warning:
PHONE-----YELLOW TRIANGLE----- COMPUTER
'Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
I tried to flash the latest KNOX bootloader roms via ODIN to boot up the phone, however....
ODIN keeps hanging on the "system" flashing command and goes to a red "fail". It won't start flashing "system.img.ext4.... etc"
I've tried all versions of ODIN and all version of 4.3
I can't use any 4.2.2 roms as the phone only seems to accept 4.3 stock roms now.
Do you guys know why ODIN keeps failing at flashing 'system.img.ext4' ?
Any advice would be greatly appreciated, thanks!
Click to expand...
Click to collapse
I finally get rid of this after several hours of searching. for me im flashing the 4 files, after failed flashing, ive red from somewhere to rename the phone/cp file, by removing .md5, then extracting modem.bin to put in cp box(odin), then flash success, then reboot samsung to download mode again the flash the last csc file, finally saw the progress bar.

Worked for me too, thanks!!! Was trying to install using Odin v3.12.3 in VMware Workstation on Windows 10.

Related

HELP: I bricked my Note 3 (N900). Forget to enable USB debugging before flashing!

I have just bricked my newly-bought Note 3 (N900).
I wanted to flash the latest version of Note 3 via Odin 3.08 (from 4.3 to 4.4.2). I made a big mistake as I didn't enable the "USB DEBUGGING" mode before go to download mode.
I clicked start in Odin and it show FAIL!!!
After I restart the phone all I see on the screen is the message "Firmware upgrade encountered an issue Please select recovery mode in Kies & try again."
I tried to recover it through Kies, but the it shows the phone is not connected or not support. Meaning the Kies cannot communicate with the phone at all.
I also tries to flash in Odin many times, but it still fails.
Please!!! Can anyone here give me some solution.
Thanks.
boycam said:
I have just bricked my newly-bought Note 3 (N900).
I wanted to flash the latest version of Note 3 via Odin 3.08 (from 4.3 to 4.4.2). I made a big mistake as I didn't enable the "USB DEBUGGING" mode before go to download mode.
I clicked start in Odin and it show FAIL!!!
After I restart the phone all I see on the screen is the message "Firmware upgrade encountered an issue Please select recovery mode in Kies & try again."
I tried to recover it through Kies, but the it shows the phone is not connected or not support. Meaning the Kies cannot communicate with the phone at all.
I also tries to flash in Odin many times, but it still fails.
Please!!! Can anyone here give me some solution.
Thanks.
Click to expand...
Click to collapse
make sure kies is not running then try odin again
jaythenut said:
make sure kies is not running then try odin again
Click to expand...
Click to collapse
I tried many time already, but still fail. I think because the usb debugging mode was not enable at the first place.
Thank anyway.
boycam said:
I tried many time already, but still fail. I think because the usb debugging mode was not enable at the first place.
Thank anyway.
Click to expand...
Click to collapse
Usb debugging has nothing to do with it failing when you're using odin. Try a different version of odin.
A simple reflash via Odin 1.85 or 3.07/3.04 will fix it.
boycam said:
I have just bricked my newly-bought Note 3 (N900).
I wanted to flash the latest version of Note 3 via Odin 3.08 (from 4.3 to 4.4.2). I made a big mistake as I didn't enable the "USB DEBUGGING" mode before go to download mode.
I clicked start in Odin and it show FAIL!!!
After I restart the phone all I see on the screen is the message "Firmware upgrade encountered an issue Please select recovery mode in Kies & try again."
I tried to recover it through Kies, but the it shows the phone is not connected or not support. Meaning the Kies cannot communicate with the phone at all.
I also tries to flash in Odin many times, but it still fails.
Please!!! Can anyone here give me some solution.
Thanks.
Click to expand...
Click to collapse
USB Debugging has nothing to do with odin flash, make sure while flashing below steps.
1. Update boot loader is selected in odin.(Edit:for single file not required)
2. Disable antivirus.
3. make sure note 3 drivers are installed.
4. kies not running in bag round.
5.Clear Factory Data & Catch before flash.
if all of those step fail..
try to flash ur rom on other computer or laptop
Sent from my SM-N900 using XDA Premium 4 mobile app
radicalisto said:
A simple reflash via Odin 1.85 or 3.07/3.04 will fix it.
Click to expand...
Click to collapse
Thankx man itis worked:good::good:
jdomadia said:
USB Debugging has nothing to do with odin flash, make sure while flashing below steps.
1. Update boot loader is selected in odin.(Edit:for single file not required)
2. Disable antivirus.
3. make sure note 3 drivers are installed.
4. kies not running in bag round.
5.Clear Factory Data & Catch before flash.
Click to expand...
Click to collapse
tried flashin with diff odin versions, was not working, tried ver 1.85, cause it lets you select update boot loader.......and BAM,,it worked on my tmobile tab 4, now i c.an wipe the tears off the key board, thanks, didnt do # 5 tho, was rooting the tab with cf auto.
markap99 said:
tried flashin with diff odin versions, was not working, tried ver 1.85, cause it lets you select update boot loader.......and BAM,,it worked on my tmobile tab 4, now i c.an wipe the tears off the key board, thanks, didnt do # 5 tho, was rooting the tab with cf auto.
Click to expand...
Click to collapse
You've indeed saved my day... I've been searching high and low, installing various versions of Odin3, downloading tonnes of tar, tarmd5, zip, etc.!
Pardon me for my ignorance, but I never intended to root my cell phone in the first place. I was merely following what Kies suggested, "A New Firmware, Wanna Upgrade?" Oh, truly? Gee, thanks! And **** it, it screwed up my GT-N7000, saying "Firmware upgrade encountered an issue..." and my cell phone never saw the daylight again, regardless how I started it, factory-reset mode wasn't possible at all, only download mode could be started up. Tried with various methods of Odin3 on multiple ROMS, to no avail, until I read your short reply. BAM! (As you put it...)
Thanks a bunch, mate!
I have a similar issue with my sm n900. Lost my imei and baseband, i needed to flash a custom rom to get my baseband before working on the imei, after flashing via odin phone boots to samsung logo then goes blank. And recovery says E failed to mount efs . But i need to use adb on my pc. So how can i possibly enabe usb debugging in order for adb to find my device?
Flashing a stock ROM from sammobile.com via Odin does not require USB debugging. Flashing a stock ROM will flash everything, including modem, bootloader, and recovery.
My N900 Bricked
I am unable to Go to download mode not even the charging symbol too
no Luck at all phone is not starting need a Unbrick or help me how to get it sorted
galaxy Note 3 Sm N900
Tried to open the phone to short the wire but the shorting mentioned in all the imagees doesnt match the design of the phone internal
can some one tell me which points to short to start the phoen in Ext sd mode
or any help would help

[Q] ODIN keeps crashing!

Hello so i believed i soft bricked my Galaxy S4 when trying to install a custom ROM. I tied to factory reset in my settings but it stayed at the downloading stage for multiple hours so i had to reboot. I downloaded a factory PDA file and PIT file to use with ODIN but everytime i click start it says ODIN is not responding and after it fixes it says Failed. Please help i really would like to fix my phone asap.
TheSamsungGuyS4 said:
Hello so i believed i soft bricked my Galaxy S4 when trying to install a custom ROM. I tied to factory reset in my settings but it stayed at the downloading stage for multiple hours so i had to reboot. I downloaded a factory PDA file and PIT file to use with ODIN but everytime i click start it says ODIN is not responding and after it fixes it says Failed. Please help i really would like to fix my phone asap.
Click to expand...
Click to collapse
Make sure you didnt connect your phone to USB 3.0 Port
TheSamsungGuyS4 said:
Hello so i believed i soft bricked my Galaxy S4 when trying to install a custom ROM. I tied to factory reset in my settings but it stayed at the downloading stage for multiple hours so i had to reboot. I downloaded a factory PDA file and PIT file to use with ODIN but everytime i click start it says ODIN is not responding and after it fixes it says Failed. Please help i really would like to fix my phone asap.
Click to expand...
Click to collapse
Bott in recovery, then wipe cach and dalvik, this will help if you're still on boot screen, and also for bottloop.
About USB 3.0. I always connect my devices via USB 3.0, it doesn't matter, the only thing is to have Intel drivers (Win 7) and not Microsoft (Win 8).
Reinstall KIES/drivers on your computer then connect your devices.
I think it should be OK
Hallelujah !
TheSamsungGuyS4 said:
Hello so i believed i soft bricked my Galaxy S4 when trying to install a custom ROM. I tied to factory reset in my settings but it stayed at the downloading stage for multiple hours so i had to reboot. I downloaded a factory PDA file and PIT file to use with ODIN but everytime i click start it says ODIN is not responding and after it fixes it says Failed. Please help i really would like to fix my phone asap.
Click to expand...
Click to collapse
if you use PDA file you don't need pit file
and please note,when flashing PDA file using ODIN check F.reset time and auto-reboot option only
also, before flash using ODIN make sure ODIN recognize your device ( the box will turn to blue ) then you can press start to start the process
petrusconsult said:
Bott in recovery, then wipe cach and dalvik, this will help if you're still on boot screen, and also for bottloop.
About USB 3.0. I always connect my devices via USB 3.0, it doesn't matter, the only thing is to have Intel drivers (Win 7) and not Microsoft (Win 8).
Reinstall KIES/drivers on your computer then connect your devices.
I think it should be OK
Hallelujah !
Click to expand...
Click to collapse
No, I've use windows 8.1 and it work fine and it'll work on other windows as well ..please note that someone maybe install windows 7 OS over their current OS and it will create more problem to them..
Zaraee said:
if you use PDA file you don't need pit file
and please note,when flashing PDA file using ODIN check F.reset time and auto-reboot option only
also, before flash using ODIN make sure ODIN recognize your device ( the box will turn to blue ) then you can press start to start the process
No, I've use windows 8.1 and it work fine and it'll work on other windows as well ..please note that someone maybe install windows 7 OS over their current OS and it will create more problem to them..
Click to expand...
Click to collapse
With one-file rom, if you want to make a repartition, you need PIT FILE !
Yes..but why bother to repartition your device..as many of them bricked their device by flashing wrong pit file
Sent from my GT-I9500

Odin issue or my usb it's faulty? please help

I, i've tried to update my friend's phone to latest unbranded build and for the lulz now i'm in troubles, well, i'll be the more accurate that i can be, so here we go:
Well, the phone enter in recovery mode as well it enter at download mode, so i'll proceed to install drivers and check odin, my lap is currently running w8.1 x64 so odin doesn't detected com port, well after a lot of googling i'll finally go to a friend lap with windows xp and drivers installed succesfully, and ODIN detect the phone at a COM port in download mode.
Well i just put the partitions file (instead i tell odin to not repartition) and put the .tar file of my unbranded s5360L, well the first times i get "setup connection" and it ends forever on it, if i close odin from task manager and reopen, com port is not detected anymore, i need to reboot and reinstall drivers to get it work and if i got tooo much luck after a few try's it start download but fail at 2 secs of the first module install.
In every PC i check'd (odin 1.84) with samsung v3000 drivers and .tar.md5 file it happens on that way, i'm very frustated cause my friend ask me for the phone and its bootlooped and i don't know how can i proceed u.u
Can anyone give me some light to fight this uncertain problem? i tried to isolate the problem as well but with no results for my perception.
Thanks, sorry for TL, but please read y.y
for TL;DR: Odin 1.83 with samsung drivers no kies stuck @ setupconnection or install a little bit and just fail everytime i try.
To start off with odin & flashing firmware works fine in Windows 8.1 - Just run the driver setup programme in compatibility mode by right click the setup file - select properties than compatibility tab & from the drop down box select windows xp sp3 - select apply and now the setup programme will run - keep clicking next & job done
Now for the firmware - never use the pit or bootloader file - its just not needed to flash stock firmware & if you flash the wrong one you will brick your phone
Use odin 3.07
All firmware and instructions are on my firmware thread to which you find either at the top of the dev section or by clicking the link to my threads in my signature below
Note if you have downloaded firmware from elsewhere delete it & download it from my thread using my instructions

[i9505] Odin not working Windows 10 x64

So I am trying to install a custom recovery for my i9505, but Odin does not recognize the phone which was put in download mode before. Please help me! Here are some details:
I got proper USB Drivers installed (1.5.55.0), tried even with Kies/smart switch installed
Using Odin 3.09-3.10.7
Different usb-cables
Completly UNROOTED i9505 with STOCK recovery and 80% charge
In device manager the phone does not appear properly. It has two listings:
1. Other Devices\ MSM8960
2. USB-Controller \ Unknown USB Device (Error trying to get device description //translated from German
Windows 10 Home 64bit
Personally I think it should be a problem with Windows 10 but I am not sure...
To the phone itself because it could be hardware-wise broken:
The phone itself is a completly meltdown. Before I tried repairing it the speaker were broken (no sound). The phone ran an official lollipop rom. I think 5.0.1. Then I thought I could just hit a software update to fix maybe some problems. I updated to I9505XXUHOJ2 [5.0.1] DBT
And now the software experience is completly broken. The phone gets a lot of soft-reboots, the booting takes like 5 minutes and yes the phone is factory reseted. BUT HEY THE SPEAKER WORK AGAIN?!
I really dont know what is happening but there can be only 2 solutions:
1. Re-Install stock software via odin and then switch to cm and hope it works
2. or throw this piece of sh*t away because the cr*ppy hardware is brokanus sarus rekt
or is there any other solution? Tell me
Otherwise I would also ask if there is any solution to install cm12.1 or a custom recovery without root and odin access. (thinking of sideloading in recovery or something like this)
Thanks for reading and replying. I am gratefull for everything I hope the best ^.^
Try running Odin in compatibility mode, set for Windows 7.
fabsau said:
So I am trying to install a custom recovery for my i9505, but Odin does not recognize the phone which was put in download mode before. Please help me! Here are some details:
I got proper USB Drivers installed (1.5.55.0), tried even with Kies/smart switch installed
Using Odin 3.09-3.10.7
Different usb-cables
Completly UNROOTED i9505 with STOCK recovery and 80% charge
In device manager the phone does not appear properly. It has two listings:
1. Other Devices\ MSM8960
2. USB-Controller \ Unknown USB Device (Error trying to get device description //translated from German
Windows 10 Home 64bit
Personally I think it should be a problem with Windows 10 but I am not sure...
To the phone itself because it could be hardware-wise broken:
The phone itself is a completly meltdown. Before I tried repairing it the speaker were broken (no sound). The phone ran an official lollipop rom. I think 5.0.1. Then I thought I could just hit a software update to fix maybe some problems. I updated to I9505XXUHOJ2 [5.0.1] DBT
And now the software experience is completly broken. The phone gets a lot of soft-reboots, the booting takes like 5 minutes and yes the phone is factory reseted. BUT HEY THE SPEAKER WORK AGAIN?!
I really dont know what is happening but there can be only 2 solutions:
1. Re-Install stock software via odin and then switch to cm and hope it works
2. or throw this piece of sh*t away because the cr*ppy hardware is brokanus sarus rekt
or is there any other solution? Tell me
Otherwise I would also ask if there is any solution to install cm12.1 or a custom recovery without root and odin access. (thinking of sideloading in recovery or something like this)
Thanks for reading and replying. I am gratefull for everything I hope the best ^.^
Click to expand...
Click to collapse
Windows 10 x64 works fine. I used it myself.
Try all the different usb ports and reinstall the drivers. Use the drivers from here:
http://developer.samsung.com/technical-doc/view.do?v=T000000117
Hi,
As the addition, make sure Kies isn't running when Odin is executed as it could cause the device being not detected properly in Odin.
PS Note: I used Windows 10 Home x64 too and working fine as it should.
Sent from my GT-I9500

Bootloop, No recovery and No download Mode.

Hello,
I was trying to flash Twrp recovery in my phone using flashify. It said flash successfully and i rebooted. It starting bootlooping. I manually tried by pressing Volume up + Home+Power keys it was still doing bootloop. I tried to goto download mode by pressing Volume Down+ Home+Power keys it still kept bootlooping even USB jig didn't work. I need your valued suggestion about what to do next.
Thanks in Advance.
I have Samsung Galaxy Grand Primr G530H
here is video link youtu.be/B_EtRTH93YE
Just flash your firmware from Odin using a PC, I had a similar problem in my tablet, it didn't had download mode either and that worked, try it.
When I connect it to Pc it keeps bootlooping and pc gives sound of connecting then disconnecting of hardware.
GorJessSpazzer said:
Just flash your firmware from Odin using a PC, I had a similar problem in my tablet, it didn't had download mode either and that worked, try it.
Click to expand...
Click to collapse
How did you flash a firmware, when your tablet didn't have download mode? What ODIN version did you use? please tell us we need your experience.
talvigi said:
How did you flash a firmware, when your tablet didn't have download mode? What ODIN version did you use? please tell us we need your experience.
Click to expand...
Click to collapse
Turn off your device, keep your finger in the button until the device is off or pull off the battery, connect it to the PC and flash your firmware through Odin, at that moment I used the 3.70 i think but you can use the latest version it's fine, that should install download mode and the whole firmware if that doesn't work I'm afraid I don't know how else I can help, that's what I did and it worked
GorJessSpazzer said:
Turn off your device, keep your finger in the button until the device is off or pull off the battery, connect it to the PC and flash your firmware through Odin, at that moment I used the 3.70 i think but you can use the latest version it's fine, that should install download mode and the whole firmware if that doesn't work I'm afraid I don't know how else I can help, that's what I did and it worked
Click to expand...
Click to collapse
You are right I did it the same way and it worked for me too. I actually was thinking the phone was quite dead bur or wasn't, I just flashed the recovery firmware 4.4.4 Russian and if you ask me food the step by step procedure it was just like this:
1. I started the Odin 3.07 and connected my device to see is it was detected or not, my surprise the Odin catch it, and shown added and the port number was 18.
2. I just pulled out the USB cable from my laptop and loaded the BL file only to just flash the bootloader file and see what would happen, I was trying it bcz I was totally disappointed with the device i.e. Grand Prime 530H Duos. I also noticed that my device was not stable even with that black screen it used to restart after almost five minutes in that case. And I knew that in 5 minute I will just be able to flash BL file. The BL file was loaded on the Odin now and I inserted the USB cable again while keeping the vol down button pressed to my laptop when the Odin again found and connected with my device, I didnot take any more time to flash BL file.
3. As soon as i had not flashed all the SW therefore, my device didn't boot properly, and I thought it didn't work but when my device was connected to the computer I just listened the startup tone of the Android 4.4.4. From that moment I knew my device was not dead now so i had to select all four files from the recovery firmware of 4.4.4 and connect the device to odin even there was no sign of download mode, as soon i clicked the Start button i saw many things in the Odin which were good enough to see. after the firmware flashed the device got started.
Sent from my SAMSUNG-SM-G920A using Tapatalk
talvigi said:
You are right I did it the same way and it worked for me too. I actually was thinking the phone was quite dead bur or wasn't, I just flashed the recovery firmware 4.4.4 Russian and if you ask me food the step by step procedure it was just like this:
1. I started the Odin 3.07 and connected my device to see is it was detected or not, my surprise the Odin catch it, and shown added and the port number was 18.
2. I just pulled out the USB cable from my laptop and loaded the BL file only to just flash the bootloader file and see what would happen, I was trying it bcz I was totally disappointed with the device i.e. Grand Prime 530H Duos. I also noticed that my device was not stable even with that black screen it used to restart after almost five minutes in that case. And I knew that in 5 minute I will just be able to flash BL file. The BL file was loaded on the Odin now and I inserted the USB cable again while keeping the vol down button pressed to my laptop when the Odin again found and connected with my device, I didnot take any more time to flash BL file.
3. As soon as i had not flashed all the SW therefore, my device didn't boot properly, and I thought it didn't work but when my device was connected to the computer I just listened the startup tone of the Android 4.4.4. From that moment I knew my device was not dead now so i had to select all four files from the recovery firmware of 4.4.4 and connect the device to odin even there was no sign of download mode, as soon i clicked the Start button i saw many things in the Odin which were good enough to see. after the firmware flashed the device got started.
Sent from my SAMSUNG-SM-G920A using Tapatalk
Click to expand...
Click to collapse
I'm glad I helped you and thanks for your description, other people with the same problem can see it, my English its not good and I was afraid that I didn't help you correctly.
Same problem, but apparently worst!
AwkWeirdo said:
Hello,
I was trying to flash Twrp recovery in my phone using flashify. It said flash successfully and i rebooted. It starting bootlooping. I manually tried by pressing Volume up + Home+Power keys it was still doing bootloop. I tried to goto download mode by pressing Volume Down+ Home+Power keys it still kept bootlooping even USB jig didn't work. I need your valued suggestion about what to do next.
Thanks in Advance.
I have Samsung Galaxy Grand Primr G530H
here is video link youtu.be/B_EtRTH93YE
Click to expand...
Click to collapse
Hello guys! Could you please help me with the same issue? The difference is that Odin doesn't recognize when I plug in my phone! I don't know what else to do. It's a G530H.
Thank you very much!
GorJessSpazzer said:
I'm glad I helped you and thanks for your description, other people with the same problem can see it, my English its not good and I was afraid that I didn't help you correctly.
Click to expand...
Click to collapse
talvigi said:
You are right I did it the same way and it worked for me too. I actually was thinking the phone was quite dead but it wasn't, I just flashed the recovery firmware 4.4.4 Russian and if you ask me for the step by step procedure it was someting like this:
1. I started the Odin 3.07 and connected my device to see if it was detected or not, to my surprise, Odin catch it, and shown added and the port number was 18.
2. I just pulled out the USB cable from my laptop and loaded the BL file only to just flash the bootloader file and see what would happen, I was trying it bcz I was totally disappointed with the device i.e. Grand Prime 530H Duos. I also noticed that my device was not stable even with that black screen it used to restart after almost five minutes in that case. And I knew that in 5 minute I will just be able to flash BL file. The BL file was loaded on the Odin now and I inserted the USB cable again while keeping the vol down + home key pressed, to my laptop when the Odin again found and connected with my device, I didnot take any more time to flash BL file.
3. As soon as i had not flashed all the SW therefore, my device didn't boot properly, and I thought it didn't work but when my device was connected to the computer I just listened the startup tone of the Android 4.4.4. or the device. From that moment I knew my device was not dead now so i pullup the battery, put it again inside to check its status, did this almost thrice, but still the same black screen, yet i heard the startup sound everytime. Now as far as knew the phone is on but showing nothing, I had to select all four files from the recovery firmware of 4.4.4 and connect the device to odin even there was no sign of download mode, as soon i clicked the Start button i saw many things in the Odin bar which were good enough to see. after the firmware flashed the device got started.
Sent from my SAMSUNG-SM-G920A using Tapatalk
Click to expand...
Click to collapse
Sent from my SAMSUNG-SM-G920A using Tapatalk
lucas13garcia said:
Hello guys! Could you please help me with the same issue? The difference is that Odin doesn't recognize when I plug in my phone! I don't know what else to do. It's a G530H.
Thank you very much!
Click to expand...
Click to collapse
Is your USB cable original is it working on other devices? And are you using a USB 2.0 port, that is very much necessary, for Odin and some other hardware/software environment applications. And you also must have Samsung USB drivers installed in your PC, you can also try all this process on some other PCs
Sent from my SAMSUNG-SM-G920A using Tapatalk
talvigi said:
Is your USB cable original is it working on other devices? And are you using a USB 2.0 port, that is very much necessary, for Odin and some other hardware/software environment applications. And you also must have Samsung USB drivers installed in your PC, you can also try all this process on some other PCs
Sent from my SAMSUNG-SM-G920A using Tapatalk
Click to expand...
Click to collapse
Hello!
Yes, that USB works with other phones. And even not being the original one, it was working to transfer files before this issue...
It is a USB 2.0 port, and even when I go to "Device Manage" on Windows, it doesn't show any port with an unknown device or something like that...
Thanks!

Categories

Resources