Develop Bugs

HELP! Phone soft bricked, ODIN failing

So I was attempting to flash the CWM6 safe kernel to upgrade to CM9 beta 1 on my girlfriend's phone. The kernel flash didn't go well and the phone was stuck at the splash screen. I'm attempting to ODIN FH13 via One Click. ODIN sees the phone, and the process starts...but always fails at:
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012>
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas/help?
Thanks in advance.

Nevermind...it all the of the sudden felt like working after 3 attempts.

[Q] i9082L update to 4.2.2 issue

I have previously successfully installed CWM (using Odin) and flashed two version of the GENNXT ROM 4.1.2 using CWM on my i9082L. However, I have not been able to flash leaked 4.2.2 (using Odin) and now I can't flash the official 4.2.2 (using Odin) either. Any ideas? 4.2.2 not compatible with i9082L?
Thanks
Update:
Oh, and I now can't get back into 4.1.2 either. Did a nand restore: stuck at Samsung logo. Was able to flash CWM again using Odin and flashed 4.1.2 GENNEXT: stuck at Samsung logo. Does the 4.2.2 update repartition? If so, will flashing official 4.1.2 using Odin get me back into my phone? Am downloading 4.1.2 Odin package now.
Using Odin to flash official 4.2.2 results in this:
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9082XXUBMGA_I9082OXEBMGA_I9082XXUBMGA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> vc-firmware.img
<ID:0/011> NAND Write Start!!
<ID:0/011> Transmission Complete..
<ID:0/011> Now Writing.. Please wait about 2 minutes
<ID:0/011> Receive Response from boot-loader
<ID:0/011> boot.img
<ID:0/011> Transmission Complete..
<ID:0/011> Now Writing.. Please wait about 2 minutes
<ID:0/011> Receive Response from boot-loader
<ID:0/011> recovery.img
<ID:0/011> Transmission Complete..
<ID:0/011> Now Writing.. Please wait about 2 minutes
<ID:0/011> Receive Response from boot-loader
<ID:0/011> BcmCP.img
<ID:0/011> Transmission Complete..
<ID:0/011> Now Writing.. Please wait about 2 minutes
<ID:0/011> Receive Response from boot-loader
<ID:0/011> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
And flashing the leaked 4.2.2 results in this:
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOT_I9082XXUBMF2_REV05.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9082XXUBMF2_871997_REV05_user_mid_noship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9082XXUBMF2_REV05.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_OXA_I9082OXABMF2_871997_REV05_user_mid_noship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Set PIT file..
<ID:0/011> DO NOT TURN OFF TARGET!!
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> BcmBoot.img
<ID:0/011> NAND Write Start!!
<ID:0/011> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Finished downloading 4.1.1 stock and tried to flash using Odin:
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9082XXAMF7_I9082ODDMF3__I9082XXAME4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Do I need a 4.1.2 pit file? If so, can someone share?
Thanks!

The 4.2.2. Release by samsung is not supported by 9082L model and it's only for 9082 model .
Just flash back to official 4.1.2 rom of ur fone model which is 9082L through pc odin then after process completes just goto Stock recovery <3e> and wipe data and factory reset from there then u able to bootup ur fone as normal again .
Sent from my GT-I9082 using Tapatalk 2

balliboxer said:
The 4.2.2. Release by samsung is not supported by 9082L model and it's only for 9082 model .
Just flash back to official 4.1.2 rom of ur fone model which is 9082L through pc odin then after process completes just goto Stock recovery <3e> and wipe data and factory reset from there then u able to bootup ur fone as normal again .
Sent from my GT-I9082 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. So I'll try to flash the 4.1.2 stock firmware I am downloading right now through Odin.
Interestingly, your 4.1.2 GENNEXT roms worked flawlessly on my i9082L. I'll keep using your latest 4.1.2 rom than for the time being, until Samsung releases a 4.2.2 for the 9082L (and maybe you will make a ROM?).

Solved
rikponne said:
Thanks. So I'll try to flash the 4.1.2 stock firmware I am downloading right now through Odin.
Interestingly, your 4.1.2 GENNEXT roms worked flawlessly on my i9082L. I'll keep using your latest 4.1.2 rom than for the time being, until Samsung releases a 4.2.2 for the 9082L (and maybe you will make a ROM?).
Click to expand...
Click to collapse
I managed to flash i9082L 4.1.2 firmware through Odin, and my phone is working again. Thanks for the advice!
Is there anything against flashing your 4.1.2 GENNEXT Rom over this? I have done it before in the past, as mentioned, and it has been running fine as far as I have been able to tell.

I want to know can I have permanent cwm on my galaxy grand after root?
Sent from my GT-I9082 using xda premium

Hey sir I want to knw can I have a nice flare and light effect in my galaxy grand?
Sent from my GT-I9082 using xda premium
---------- Post added at 12:59 PM ---------- Previous post was at 12:50 PM ----------
balliboxer said:
The 4.2.2. Release by samsung is not supported by 9082L model and it's only for 9082 model .
Just flash back to official 4.1.2 rom of ur fone model which is 9082L through pc odin then after process completes just goto Stock recovery <3e> and wipe data and factory reset from there then u able to bootup ur fone as normal again .
Sent from my GT-I9082 using Tapatalk 2
Click to expand...
Click to collapse
Balliboxer can I have nice light and flare effect on my galaxy grand?
Sent from my GT-I9082 using xda premium

Anirudh2 said:
Hey sir I want to knw can I have a nice flare and light effect in my galaxy grand?
Sent from my GT-I9082 using xda premium
---------- Post added at 12:59 PM ---------- Previous post was at 12:50 PM ----------
Balliboxer can I have nice light and flare effect on my galaxy grand?
Sent from my GT-I9082 using xda
U r asking on wrong thread bro
Go Here
http://forum.xda-developers.com/showthread.php?p=42541219
Sent from my GT-I9082 using xda premium
Click to expand...
Click to collapse

S4 Mini -Root Issue

Hi Guys ,
When I connect my phone just vibrate so my last solution is to root it .so below my issues :
-Using Odin3 v1.85 ,I got that :
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery-clockwork-6.0.5.1-serranoltexx.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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Using other Odin versions ,I got :
Stuck on initialization .
Also be informed I tried with different usb port ,different cables.

Odin 1.85 sounds old, I user Odin 3,09 that I downloaded from xda (see link below) to install custom recovery (TWRP) now but I have run clockwork earlier on my s4 mini (GT-i9195) and it works fine.
Odin 3.09 - http://forum.xda-developers.com/showthread.php?t=2353876

linol said:
Odin 1.85 sounds old, I user Odin 3,09 that I downloaded from xda (see link below) to install custom recovery (TWRP) now but I have run clockwork earlier on my s4 mini (GT-i9195) and it works fine.
Odin 3.09 - http://forum.xda-developers.com/showthread.php?t=2353876
Click to expand...
Click to collapse
When I plug my phone just vibrate and nothing happen after. when I want to power it also vibrate and nothing on screen .but I can enter on odin mode >
What's could be ? I need your support .
Thanks in advance

How about you plug your USB cable directly at the backside of CPU incase of desktop pc. and also Turn off AntiVirus and kill kies in task manager if its running.
But before doing any of that try connecting your phone to kies. and check if it can be connected. if not install the drivers.

thanks for your but didn't help ,below what I got :
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1100)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..

You can try flash emergency firmware from Samsung kies. Never tested but maybe can bring back to life your phone.

kies can't detect my mobile

Have you installed the Samsung drivers?

Yes,installed

bingozingo said:
Yes,installed
Click to expand...
Click to collapse
Looks like your eMMC is dead.

How can I confirm that ?

bingozingo said:
How can I confirm that ?
Click to expand...
Click to collapse
IMO, the only way is to look for a full restore image of your device.
Keywords to use in your search are: i9195xxucnh5, rev01, low_user_ship, tar.md5
The full restore image is the one used by Kies to initialise the devise to its factory state. It can be a single file or, in most cases, 4 files (BOOTLOADER, AP, CP and CSC).
It contain the PIT file, necessary to re-partition the entire eMMc, and every image for each new created partition.
If you find that image, or a member can provide it, there are good chances that your phone come back to life.
If Odin fails to flash the image and says "can't re-repartition", then your are good to look for another chipset.
Sorry, i can't help you with links.

pls ,have you the steps to do that ?,also did you have the full name of the all files that can help for search .

pls help
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_OXA_I9195OXABML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
I wanna be crazy .

Can you note exactly what is written on the Download Mode screen ?

Downloading
Do not turn off target!!

bingozingo said:
Downloading
Do not turn off target!!
Click to expand...
Click to collapse
No, i mean what is written in the upper left corner.

Odin Mode
product name : GT-I9195
Current Binary : samsung official
system status : official
Knox kernel lock : 0x0
knox warranty void : 0x0
csb-config-lsb : 0x30
bootloader ap swrev : 2
write protection : enable

bingozingo said:
Odin Mode
product name : GT-I9195
Current Binary : samsung official
system status : official
Knox kernel lock : 0x0
knox warranty void : 0x0
csb-config-lsb : 0x30
bootloader ap swrev : 2
write protection : enable
Click to expand...
Click to collapse
Nothing strange here...
Your bootloader can see the content of system partition.
Can you access stock recovery (Power Button+Volume Up) ?
If you can, do a factory reset then reboot.

When I want to enter on recovery mode( power+volume up ) ,it's just vibrate .nothing on screen

flashable zip for J200GU stock

Hello,
I am unable to flash stock firmware back to my J200GU with Odin since it always gives me a fail.
So I was trying to flash directly on TWRP or ADB sideload but I always get an error with my zip firmwares.
Does anyone knows where to get the zip firmwares ready for ADB sideload or TWRP?
Sorry if it is a stupid question but I am really newb on this.
Thanks.

use noblerom/hydrarom meta-inf folder in your rom.

RevolverRz said:
use noblerom/hydrarom meta-inf folder in your rom.
Click to expand...
Click to collapse
I have tried what you recomended and TWRP proceeds to install hydrarom, however it is installed very fast and when it reboots i am stuck at bootloop. I believe it has sucessfully installed hydra but not the stock rom I wanted.
I have currently no OS on my phone or any firmaware so my guess is that to be able to install this custom roms (hydra and noble) i need to already have a stock firmware an this will be just an add on. Correct me if I am wrong.
Are the firmwares from SAMMOBILE ready to be used on TWRP? I am starting to think the are not to be used on TWRP but ODIN instead, but ODIN always gives me a fail. SO my question is: IS there a way to make roms downloaded from SAMMOBILE install on TWRP or adb sideload? Any guide about this?
Thanks. I appreciate any help since I have my J2 completly useless now

Can you post your Odin log?
or use the 4 files repair firmware.
https://www.androidfilehost.com/?fid=24407100847293886

RevolverRz said:
Can you post your Odin log?
or use the 4 files repair firmware.
https://www.androidfilehost.com/?fid=24407100847293886
Click to expand...
Click to collapse
Just tried the repair files and got this error on ODIN:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any more suggestions?

<ID:0/004> sboot.bin
<ID:0/004> FAIL!
Means this rom is not for you j200gu.
Use the most recent version of rom from here..
http://updato.com/firmware-archive-select-model?q=SM-J200GU&rpp=15&order=date&dir=desc&exact=1

pic upload edit
This is my phone. It was bought in Thailand and its dual sim. I am not sure which is the correct firmware for my phone since its dual sim. Can anyone guide me?

RevolverRz said:
Can you post your Odin log?
or use the 4 files repair firmware.
https://www.androidfilehost.com/?fid=24407100847293886
Click to expand...
Click to collapse
Thank you! Finally!
I have tried flashing using just the AP file instead of all 4 files and it worked. When I tried to use the 4 files together in Odin it failed but instead using only the AP I was able to install the firmware and get a PASS.
Thanks alot for all the help in this forum

sushyoshi said:
Thank you! Finally!
I have tried flashing using just the AP file instead of all 4 files and it worked. When I tried to use the 4 files together in Odin it failed but instead using only the AP I was able to install the firmware and get a PASS.
Thanks alot for all the help in this forum
Click to expand...
Click to collapse
Glad to hear that

FRP/FAP Locked
RevolverRz said:
Glad to hear that
Click to expand...
Click to collapse
I accidentally turned off the oem unlocking in dev options(couple of hours earlier) and then when i tried to change my emoticon pack it says FAP Lock. Thank you so much!!! :good: :highfive: (I use Samsung J200GU)

Need help to unbrick Samsung SM-A505F

Hello,
A friend of mine tried to root his phone(SM-A505F) using Odin3 and TWRP i really don't know what he did but he says that he unzip the .tar file for TWRP and tried to flash each .img file that was converted to .tar.md5 into AP. So what happens next is he accidentally flash something in BL. Now the phone is stuck on a loop and can only go to download mode. Now i'm trying to help him unbrick it by just flashing a stock which I found here: https://forum.xda-developers.com/galaxy-a50/how-to/stock-rom-samsung-galaxy-a50-sm-a5005f-t3926746
But the phone is SM-A505F and we're from Philippines and it was bought locally so region wise there is no stock rom for SM-A505F so i tried to use SM-A505GN.
Unfortunately it's not working. Odin3 always get's stuck on here:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 6025 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> param.bin
<ID:0/005> up_param.bin
<ID:0/005> cm.bin
<ID:0/005> keystorage.bin
<ID:0/005> uh.bin
<ID:0/005> vbmeta.img
<ID:0/005> boot.img[/SIZE]
And on the phone it shows: "SW REV. CHECK FAIL(BOOTLOADER) DEVICEL: 3, BINARY: 1"
I would really appriciate any help here as my friend is crying over it, as it is a just bought phone
Thanks in advance
PS. Also tried the SM-A505F stock rom and it has the same result

Hi, hoping I can help a bit. Had a similar issue with my A50 after flashing TWRP, so I'm hoping I can help. Im from from the Netherlands and using the FN variant, but this should apply to any variant.
You can download the F firmware from here; its quite fast (a lot better than dealing with sammobile's website).
imei.info/download-firmware/samsung/samsung-galaxy-a50/SM-A505F/
After unpacking the zip, you have to put every .tar.md5 file into the right directory in Odin.
Put phone into download mode (hold volume buttons while putting in usb c cable connected to laptop)
make sure you lock the bootloader first. (by long pressing up if i remember correctly)
I suggest using the latest ODIN for this. Can you keep me posted if this works?
---------- Post added at 08:26 PM ---------- Previous post was at 08:23 PM ----------
Agil1ty said:
Hi, hoping I can help a bit. Had a similar issue with my A50 after flashing TWRP, so I'm hoping I can help. Im from from the Netherlands and using the FN variant, but this should apply to any variant.
You can download the F firmware from here; its quite fast (a lot better than dealing with sammobile's website).
imei.info/download-firmware/samsung/samsung-galaxy-a50/SM-A505F/
After unpacking the zip, you have to put every .tar.md5 file into the right directory in Odin.
Put phone into download mode (hold volume buttons while putting in usb c cable connected to laptop)
make sure you lock the bootloader first. (by long pressing up if i remember correctly)
I suggest using the latest ODIN for this. Can you keep me posted if this works?
Click to expand...
Click to collapse
Btw did you remove any google account before trying to flash TWRP? If not, try to get into recovery after flashing with ODIN and do a factory reset. You will have to put in the same google account after rebooting in android.