Database Users

[Q] Odin not working + bricked phone without doing anything unusual.

First, I'm not a noob, so don't answer something like "did you go into download mode" or something like that ok? Thanks.
I just bricked my phone which is on Savie's kernel, Hyperion 8 while multitasking hard. I was converting a batch of MP3s, Downloading a video and listening to music, when it just hanged, when I decided to restart it , i realised that it was bricked. Even worse, Odin can't get it out of brick. Odin can recognize the device, complete the flash sucessfully
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_S5360_DXLJ1.tar.md5 is valid.
<OSM> MODEM_S5360_DXLF1.tar.md5 is valid.
<OSM> CSC_S5360_OLBLG1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> param.lfs
<ID:0/003> system.img
<ID:0/003> sbl.bin
<ID:0/003> userdata.img
<ID:0/003> BcmCP.img
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response form LOKE
<ID:0/003> csc.rfs
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
But it just won't boot. I need help, urgent. PWEATY PWEATY PWEASE is there anyone out there?

Can you enter recovery?
If yes, go into CWM and check if you can mount /data.
If you can mount /data, then I dont know what is wrong, but if you cant mount /data, then try this: http://forum.xda-developers.com/show....php?t=2122370
I hope it helps.

Flash stock kernel via odin from
https://hotfile.com/list/2023820/c55629e
wait a while with the cable still attached until it says passed
you should then be able to get into stock recovery
from there flash a temporary cwm
then restore your nandriod backup
Or
Wipe system & data & Flash a cutom rom or deodex stock rom from dev section

Hey thanks for your time... I booted it up the next day without doing anything special.
It was hard bricked, nothing I could do except entering download mode, and even after I flashed Odin successfully it is still bricked. Even weirder, I didn't do anything to brick /un brick it
________________________________
Many people don't get this but,
Being humble is like the "I win" button in your life.

s4 death :(

Hi all,
i tried to flash cyanogenmod unofficial, on the flash an error was comming, now the device dosent start...
when i boot the phone normaly, is comming: firmware upgrade encountered an issue. please select recovery mode in kies & try again.
i tryed to flash the original firmware:
(I9505XXUAMDF_I9505AUTAMD8_AUT)
I9505XXUAMDF_I9505AUTAMD8_I9505XXUAMDF_HOME.tar
but an error in odin is comming:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAMDF_I9505AUTAMD8_I9505XXUAMDF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Removed!!
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
please can you help me?

cutalaxy said:
Hi all,
i tried to flash cyanogenmod unofficial, on the flash an error was comming, now the device dosent start...
when i boot the phone normaly, is comming: firmware upgrade encountered an issue. please select recovery mode in kies & try again.
i tryed to flash the original firmware:
(I9505XXUAMDF_I9505AUTAMD8_AUT)
I9505XXUAMDF_I9505AUTAMD8_I9505XXUAMDF_HOME.tar
but an error in odin is comming:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAMDF_I9505AUTAMD8_I9505XXUAMDF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Removed!!
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
please can you help me?
Click to expand...
Click to collapse
Try flashing along with pit file
MKe sure u have the proper file for the same
Sent from my GT-I9500 using xda premium

123hiten said:
Try flashing along with pit file
MKe sure u have the proper file for the same
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
where can i find the pit file?

cutalaxy said:
where can i find the pit file?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2265477&highlight=stock+firmware
this link has it attached take the correct one u would know better
dont worry i had the same issue on my note 2 a month ago and was wrkng fine after flashing rescue firmware urs wil work too

damn, it doeset work for me
is it hard brick?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAMDF_I9505AUTAMD8_I9505XXUAMDF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!

cutalaxy said:
damn, it doeset work for me
is it hard brick?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAMDF_I9505AUTAMD8_I9505XXUAMDF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Click to expand...
Click to collapse
No its not at a hard brick dont worry dont panic thats the best wat to work around
I would say dont use pit file unless its last option and try without that only may be in other pc using other cable some below steps myte also help u
2) Install later Kies.
3) Kill al kies applications (all 4 of them).
disable antivirus or whatever you got there.) Get to Download Mode and push Vol Up.
7) Open Odin.
8) Plug the device to your laptop.
Does it see the device?
If NO:
A) Get another usb cable, are you using ?
B) Try different Odin Versions (download 3 or 4).
C) Try another USB port.
D) Still no luck? reboot the pc and start from step 3.
---------- Post added at 08:30 PM ---------- Previous post was at 08:23 PM ----------
Download 2/3 stock firmware and try installing thru ODIN it should work
Make sure u have all the drivers installed
MAke sure kies is not open or make sure its closed even in background process

okay, with odin 1.85 now has worked phu... lucky
but i'm confused... all(!) my settings and apps etc. are still installed and settet? why dat?
only root is going... i'm now flashing root again
i think i will wait for an official CWM and official Cyanogen... is to hot for me
@123hiten
thank you very much!! I thought now i have to get out 700$ again... :S

cutalaxy said:
okay, with odin 1.85 now has worked phu... lucky
but i'm confused... all(!) my settings and apps etc. are still installed and settet? why dat?
only root is going... i'm now flashing root again
i think i will wait for an official CWM and official Cyanogen... is to hot for me
@123hiten
thank you very much!! I thought now i have to get out 700$ again... :S
Click to expand...
Click to collapse
Official firmware is not a wiping one. It doesnt flash userdata, it replace system, recovery, and some other partitions.
sent from my Galaxy

cutalaxy said:
okay, with odin 1.85 now has worked phu... lucky
but i'm confused... all(!) my settings and apps etc. are still installed and settet? why dat?
only root is going... i'm now flashing root again
i think i will wait for an official CWM and official Cyanogen... is to hot for me
@123hiten
thank you very much!! I thought now i have to get out 700$ again... :S
Click to expand...
Click to collapse
Great to hear that man
If u flash stock firmware all will remain as its in ODIN but its good if u reset the device after or b4 root
Also take a EFS backup of ur device and be safe

i had root before the device bricks... so i rootet it now again, and works good...
yeah, i will backup efs (hope this <- works...)
yah, thank you again...
have a nice day..

stuck at bootloop, odin failing to flash stock firmware

Hey all, after being on cm for a while I returned to stock using odin. After I rooted using motochopper and installed cwm. I then attempted to updated using OTA. It seemed to go well, but I got the message the the stock recovery could be flashed and I said no the fix and then said no to fix root. The phone is now stuck on bootloop and get the message below when trying to flash stock firmware(MDB or MDL) using ODIN. When I did try and boot the phone gave me a message about some file being in use. I have no idea where to go from here and any tips would be greatly appreciated.
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!

You returned to stock, put a custom recovery on and then you decided to take the mf3 firmware update? Your recovery is now borked. Check out the best buy fix.

jd1639 said:
You returned to stock, put a custom recovery on and then you decided to take the mf3 firmware update? Your recovery is now borked. Check out the best buy fix.
Click to expand...
Click to collapse
Alright, thanks.

http://forum.xda-developers.com/showthread.php?p=45359306
Ah, the old ninja edit. Lol

[Q] Soft-bricked Verizon Galaxy Note 3

(Previous thread can be seen here)​
Hi all,
Thank you for whom reads this thread. - Very recently I tried to root my Samsung Galaxy Note 3. The method I was using was the Kingo application that isn't prohibited on the forum which I now know. At this point I am unsure what to do, besides flashing this but I am unsure if this method will work. Plus I do not know how to flash this or where to even begin.
Basically in short, I tried doing the following:
Root with the Kingo root application that I got from the official site.
After I used Wanam Exposed to customize my stock ROM.
Played on my phone for a bit and then I got a random error: "Unfortunately, System Ui has stopped"
I posted a thread about this issue (without much detail on what I was doing) and I was recommended to flash these stock files which didn't work. Here is the following errors while I try to flash the file in Odin:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
At this point I do not know what to do. I am not hard bricked but I assume I am soft bricked because my phone will not boot into my system because of the error I posted above. If anyone can get me on the right track this would be great. Thank you.

the same thing has happened to me before and i plugged my phone into the computer and used the built in verizon upgrade center and went to the repair section
Storm.hf said:
(Previous thread can be seen here)​
Hi all,
Thank you for whom reads this thread. - Very recently I tried to root my Samsung Galaxy Note 3. The method I was using was the Kingo application that isn't prohibited on the forum which I now know. At this point I am unsure what to do, besides flashing this but I am unsure if this method will work. Plus I do not know how to flash this or where to even begin.
Basically in short, I tried doing the following:
Root with the Kingo root application that I got from the official site.
After I used Wanam Exposed to customize my stock ROM.
Played on my phone for a bit and then I got a random error: "Unfortunately, System Ui has stopped"
I posted a thread about this issue (without much detail on what I was doing) and I was recommended to flash these stock files which didn't work. Here is the following errors while I try to flash the file in Odin:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
At this point I do not know what to do. I am not hard bricked but I assume I am soft bricked because my phone will not boot into my system because of the error I posted above. If anyone can get me on the right track this would be great. Thank you.
Click to expand...
Click to collapse

Could you please link me to the software
Sent from my GT-P5113 using xda app-developers app

I think your phone may have had firmware that was later than what you were trying to flash. From what you posted you were flashing mi9 which was the first one with initial released phones. They would explain the soft brick. Then there was update MJ7 and now there is MJE. I would suggest finding the MJ7 tar file and try that and see if that will fix the soft brick. If same results then try MJE.
Hope this helps.
Tap'n & Talk'n on my Note 3

tried to root and sky fall down

ok let`s start from the start, i tried to root my note 3 sm-n9005 and failed to succeed.
i used the cf auto root guide, odin said success but my phone failed to boot and went straight to recovery mode.
then, i tried using odin 3.07/09/11/185 to rewrite into the stock rom, but odins says FAIL and gives nothing in return.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGBPB1_N9005EVRGBPB1_N9005XXUGBOJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
i just want get my phone back with android that above 4.4
please help :crying:

Looks like the ROM you are trying to flash is not made for your phone or the ROM is older than the ROM currently installed on the phone.
Are you using the original Samsung USB cable? Tried different USB cables and ports?

For Root note 3 use Towelroot by Chainfire.
Sent from my Limited Edition Note 3 LTE using Super Tapatalk

Download Official 5.0 ROM from Sammobile and flash it in Odin, after it try to root phone...
In dialog this looks like firmware file is damaged

The firmware doesn't look damaged, the firmware you are trying to flash has a bootloader that is older than the bootloader in the phone.
isn't chainfire's root method called cfautoroot?

download one more time...