Develop Bugs

Odin / One click wont restore my phone stuck at boot.bin?

Hi,
I have a GS2 that wasnt being used so I decided to set it up in my bedroom as more of an email checker / facebook browser. I installed a JB rom, setup all my apps that I wanted & used it once or twice. A week later (yesterday) I went to pick it up, saw it was off, hit the power button & nothing. I pulled the battery & found it was stuck at the GSII screen. I am able to get into download mode, so I used Odin (I have the drivers installed already) trying to restore back to stock.
I used HOME_SPH-D710_CL852097_user.tar with Odin (a few different versions), I also used a few different cables & two different PC's. It keeps getting stuck at the same point which is boot.bin.
I tried a bunch of the other 1 clicks such as SPH-D710_GB27_1014481_Rooted_Restore & others. The results are the same.
Any ideas what else i can try?
Thanks,
Rich

Are you giving it enough time? Take about 20 minutes for mine to complete. Possibly longer with usb 1.1?
Sent from my SPH-D710 using xda app-developers app

Sounds like an EMMC failure...
Sent from my SGH-I337 using xda premium

Thanks guys, i am giving it plenty of time at this point it is collecting dust. I have tried multiple machines, multiple one clicks, multiple odin copies & restore files.
I can get into download mode but thats about it. I am at a complete loss on what to do.

There is one thing you can do... But for the life of me, I can't remember what it it called. What it does is partition your device in a way... You lose space but it fixes the issue.
Sent from my SGH-I337 using xda premium

I would be happy to give it a shot if you remember what I need to do.

Get in touch with @Stryke_the_Orc. I believe he was the one that was explaining the process to someone.
Sent from my SGH-I337 using xda premium

Uninstall your samsung drivers and kies if its installed, then reinstall your device drivers. There' two ways you can do this, one is to have the device in download mode and connect it to usb, the other is to install the drivers via an exe package found here
Once Odin recognizes your device, place the tar file found here in the PDA slot and hit start. You might also try the oneclick.exe.
If this doesn't work, let me know.

Stryke_the_Orc said:
Uninstall your samsung drivers and kies if its installed, then reinstall your device drivers. There' two ways you can do this, one is to have the device in download mode and connect it to usb, the other is to install the drivers via an exe package found here
Once Odin recognizes your device, place the tar file found here in the PDA slot and hit start. You might also try the oneclick.exe.
If this doesn't work, let me know.
Click to expand...
Click to collapse
I've tried your suggestions and am having no luck. I've tried different OCs and different cables and in different usb ports, on different computers even! I'm running out of ideas. Any help would be greatly appreciated.

I also sort of gave up. I have a paper weight on my desk & would be great to have it as a backup. Any ideas would be great!

Any way you can grab me screen shots of the process? I'd like to see what the screen is doing when it gets stuck:beer:
Slithering from the nether regions of a twisted mind and tarnished soul

I just encountered this problem myself. I downloaded rwilco's rooted oneclick nodata (which I have used a couple times in the past with flawless execution) and tried to reflash my ROM and it's stuck on the boot.bin. My phone's screen never changed from the default download screen with the ODIN count and warning messages and whatnot. This is the current ODIN log after 10 minutes of letting it sit here:
<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..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
As you can see, it never actually starts updating the firmware because it can't get past the boot part. I've tried multiple USB ports (one of which was USB3.0) and I've already tried uninstalling/reinstalling drivers. I think it's rather obvious there is some sort of communication error between my phone and my computer T_T It's also worth mentioning that Kies will not connect to the phone either. Both Odin and Kies detect that a phone is connected to my PC, but neither software seem to be able to connect to it.
I'm currently in the process of downloading the fullrestore (which I know won't work) to see if that works as well as a copy of standalone odin + the tar versions of the ROM. I will update this post with any progress/news I might have.
On the off chance that maybe someone knows a workaround for the problem that sparked my attempt at re-flashing: Today my phone froze and I held the power button to restart as I always do in such a situation. However, upon restarting my phone just sat at the "Samsung Galaxy S2" logo screen. I tried several battery pulls (with and without the SD card inserted) only to find myself staring at that same exact screen. Also, holding power+home+volup does nothing. The only screen I can access is the download screen (power+home+voldown)
Updates:
Upon trying the rooted full restore oneclick I encountered the same exact problem.
Upon trying Odin 3.09 with rwilco's rooted nodata tar file, I received the following error: <ID:0/003> SetupConnection.. <ID:0/003> Can't open the serial(COM) port.
Upon trying Odin 3.09 with the rooted nodata tar again on a different port, it started with NAND write and told me to wait a couple minutes before it gave up and just said failed.

I'm having an issue similar to this I think. I decided to reflash my phone I downloaded the oc I found on here and everything went fine but now when I press and hold the power button it don't power up. it just sits there. I can plug my charger in and it shows it is charging (the battery comes up) and I can get to DL mode but if I remove the charger and try to get to DL mode it says battery to low to enter download mode...what do I do?
update I don't know how or why but phone finaly booted into recovery for me did a factory reset and wiped cache and rebooted phone is up and running now
---------- Post added at 02:41 PM ---------- Previous post was at 02:16 PM ----------
WhyteDem0n said:
I just encountered this problem myself. I downloaded rwilco's rooted oneclick nodata (which I have used a couple times in the past with flawless execution) and tried to reflash my ROM and it's stuck on the boot.bin. My phone's screen never changed from the default download screen with the ODIN count and warning messages and whatnot. This is the current ODIN log after 10 minutes of letting it sit here:
<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..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
As you can see, it never actually starts updating the firmware because it can't get past the boot part. I've tried multiple USB ports (one of which was USB3.0) and I've already tried uninstalling/reinstalling drivers. I think it's rather obvious there is some sort of communication error between my phone and my computer T_T It's also worth mentioning that Kies will not connect to the phone either. Both Odin and Kies detect that a phone is connected to my PC, but neither software seem to be able to connect to it.
I'm currently in the process of downloading the fullrestore (which I know won't work) to see if that works as well as a copy of standalone odin + the tar versions of the ROM. I will update this post with any progress/news I might have.
On the off chance that maybe someone knows a workaround for the problem that sparked my attempt at re-flashing: Today my phone froze and I held the power button to restart as I always do in such a situation. However, upon restarting my phone just sat at the "Samsung Galaxy S2" logo screen. I tried several battery pulls (with and without the SD card inserted) only to find myself staring at that same exact screen. Also, holding power+home+volup does nothing. The only screen I can access is the download screen (power+home+voldown)
Updates:
Upon trying the rooted full restore oneclick I encountered the same exact problem.
Upon trying Odin 3.09 with rwilco's rooted nodata tar file, I received the following error: <ID:0/003> SetupConnection.. <ID:0/003> Can't open the serial(COM) port.
Upon trying Odin 3.09 with the rooted nodata tar again on a different port, it started with NAND write and told me to wait a couple minutes before it gave up and just said failed.
Click to expand...
Click to collapse
So now I'm having an issue with it not wanting to boot with out going through recoveryy then it only stays booted for a couple minuets
Sent from my C5155 using xda app-developers app

Well, this is my final update because I no longer have the phone. I was eligible for an upgrade as of the day my phone bricked so I said screw it and got a GS4 ^_^

Wish I'd seen this sooner, uninstalling kies and reinstalling your drivers should have fixed this for you. Unless you had hardware failure, which doesn't appear to have been the case.
Slithering from the nether regions of a twisted mind and tarnished soul

XxBriernxX said:
I'm having an issue similar to this I think. I decided to reflash my phone I downloaded the oc I found on here and everything went fine but now when I press and hold the power button it don't power up. it just sits there. I can plug my charger in and it shows it is charging (the battery comes up) and I can get to DL mode but if I remove the charger and try to get to DL mode it says battery to low to enter download mode...what do I do?
update I don't know how or why but phone finaly booted into recovery for me did a factory reset and wiped cache and rebooted phone is up and running now
---------- Post added at 02:41 PM ---------- Previous post was at 02:16 PM ----------
So now I'm having an issue with it not wanting to boot with out going through recoveryy then it only stays booted for a couple minuets
Sent from my C5155 using xda app-developers app
Click to expand...
Click to collapse
This sounds like a faulty battery, do the spin test on it and see if it's bloated.
Slithering from the nether regions of a twisted mind and tarnished soul

I still have my G2 & wouldnt mind using it with just wifi since I dont have sprint anymore but I am still stuck. Any suggestions on how to bring it back?

Stryke_the_Orc said:
This sounds like a faulty battery, do the spin test on it and see if it's bloated.
Slithering from the nether regions of a twisted mind and tarnished soul
Click to expand...
Click to collapse
for a second...just a split second I though you were recommending that I spin my phone around....I had a duh monet seeing as I'm at work lol. i'll give it a shot once this GB27 flash finishes...I've all but given up on my s2 and it sucks cause I really loved the lil bugger

Stryke_the_Orc said:
Wish I'd seen this sooner, uninstalling kies and reinstalling your drivers should have fixed this for you. Unless you had hardware failure, which doesn't appear to have been the case.
Slithering from the nether regions of a twisted mind and tarnished soul
Click to expand...
Click to collapse
I'm rather sure it was hardware failure. At the Sprint store, the technician attempted several times to get my phone into anything other than download mode. Needless to say, he failed every time and I told him not to bother because all my contacts were synced to my Google and/or Facebook accounts anyway. They still did me a solid and bought it back from me after pretending they never saw the issue
Anyway, I'm loving the upgrades provided by my S4 so no worries on my end! Good luck to you guys.

XxBriernxX said:
for a second...just a split second I though you were recommending that I spin my phone around....I had a duh monet seeing as I'm at work lol. i'll give it a shot once this GB27 flash finishes...I've all but given up on my s2 and it sucks cause I really loved the lil bugger
Click to expand...
Click to collapse
Did you figure out if the battery was the issue?

[Q] Firmware upgrade encountered an Issue

Hi,
I am a newb, so speak slowly and be gentle.
I recently bought a note 10.1 2014 edition. I rooted the device. then when KITKAT was released, I flashed back to stock and did the 4.4 update. Success. I then tried to root using CF-AutoRoot. this is where the problem occurred. ODIN 3.09 seemed to freeze for a long long time. I disconnected the USB cable and when trying to reboot the NOTE, I get this error message... Firmware encountered an issue...
So now it is in a boot loop of sorts. I can get the Note into download, but when I try to launch ODIN and re-flash the original stock file, it fails....
Enter CS for MD5..
Check MD5. Do not unplug the cable..
Please wait..
P600ueubkm1_P600XARBMK1_Home.tar.md5 is valid
Checking MD5 finished successfully..
Leave CS..
Added!!
Odin v.3 engine (ID:8)..
File Analysis
Setup Connection
Complete (write) operation failed
All threads completed (succeed 0 / failed 1)
I also see this message on the note display (SW Rev. Check Fail. Device:3, Binary:2)
And to top it off, I get USB connection errors (sometimes device not recognized) when I connect the NOTE to the computer.
Can anyone help ?
Many thanks...

biglug said:
Hi,
I am a newb, so speak slowly and be gentle.
I recently bought a note 10.1 2014 edition. I rooted the device. then when KITKAT was released, I flashed back to stock and did the 4.4 update. Success. I then tried to root using CF-AutoRoot. this is where the problem occurred. ODIN 3.09 seemed to freeze for a long long time. I disconnected the USB cable and when trying to reboot the NOTE, I get this error message... Firmware encountered an issue...
So now it is in a boot loop of sorts. I can get the Note into download, but when I try to launch ODIN and re-flash the original stock file, it fails....
Enter CS for MD5..
Check MD5. Do not unplug the cable..
Please wait..
P600ueubkm1_P600XARBMK1_Home.tar.md5 is valid
Checking MD5 finished successfully..
Leave CS..
Added!!
Odin v.3 engine (ID:8)..
File Analysis
Setup Connection
Complete (write) operation failed
All threads completed (succeed 0 / failed 1)
I also see this message on the note display (SW Rev. Check Fail. Device:3, Binary:2)
And to top it off, I get USB connection errors (sometimes device not recognized) when I connect the NOTE to the computer.
Can anyone help ?
Many thanks...
Click to expand...
Click to collapse
got it flashed to kitkat via kies3 and a different computer...if anyone else has a similar issue

biglug said:
got it flashed to kitkat via kies3 and a different computer...if anyone else has a similar issue
Click to expand...
Click to collapse
I'm having a similar issue but when I try to use Kies to do the firmware update it tells me "SM-P605V does not support initializing" Have you seen this message?

I have not.... I have the p600 wifi only and was able to enter my model # and serial # to update the firmware. Sorry I cant be of more help.
Sent from my SM-P600 using Tapatalk

biglug said:
I have not.... I have the p600 wifi only and was able to enter my model # and serial # to update the firmware. Sorry I cant be of more help.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
Try using ODIN 1.85 or 3.07 instead of 3.09

[Q] Should I give up on my SGH-T999?

To start out, some basic information. I got my SGH-T999 about 2 years ago and used it for about a year on the Stock ROM before proceeding to root the phone. The firmware version before things when went wrong was android 4.1.2. Everything was working fine until about a few days ago when the phone would stop being responsive after putting it into sleep mode, or the screen will turn black and the whole unit is unresponsive (the latter only occurring while I was in the home screen, not while running any apps. Rather, the phone would be fine while an app is running).
Troubleshoot Stage 1
Initialy, I thought there was some sort of app update that was causing this problem, and so I tried uninstalling a few apps that might have been culprits. Didn't work. On occasion, the phone would freeze up while i was trying to uninstall the app. So reading around, someone mentioned that it was possibly the TouchWiz Home that was acting up and I should, clear cache. So I rebooted into recovery (I had the clockworkmod recovery from the initial root). Cleared user data/factory reset as well as clear cache. Didn't work. At this point, the phone was restarting itself almost instantly after booting into the lock screen. I searched a bit more about why this would happen, and came across a post saying that I could be a faulty power button. I actually didn't want to physically alter my phone in any way, so I decided to try to do something with the software first before resorting to altering the physical phone.
Troubleshoot Stage 2
Next thought process was that maybe somehow an OTA was pushed onto my phone and now the firmware is screwed up because of it. So reading through many posts on XDA, I came upon this thread (http://forum.xda-developers.com/showthread.php?t=1771687) for a pre-rooted version of 4.3. I figured, if I was going to re-flash the firmware, I might as well go to the latest one. I proceed to go through the process of flashing the firmware with Odin 1.85, leaving Auto Reboot and F. Reset Time checked. Odin flashes PASS message and I unplug the phone and wait for the reset. Phone starts up all the way past all the logos and to where the home screen was supposed to be. But there was no home screen, just a black screen with only the pull down menu at the top and a message saying "Unfortunately, Settings has stopped working". This message would keep repeating even after pushing the ok button. Next thought process is, maybe TouchWiz is acting up still. So I boot to recovery, reset/format to factory, clear cache, and reboot. Now the phone wont boot past the Samsung logo. Tried to boot to recover again, phone won't boot to recovery anymore. Tried to re-flash the same exact firmware again and this time, odin had some trouble. It would sometimes stop working where it is loading the main code at which point I check the task manager to see if it is still running processes or utilizing any of the computer resources to communicate with the device. I would then have to unplug the phone and reset by removing the battery. This kept occurring about 2 more times before it successfully finished and on doing so, the original problem when I first flashed it was still there.
Troubleshoot Stage 3
Ok, maybe my phone doesn't like the pre-rooted firmware. Looked around XDA again and found this thread (http://forum.xda-developers.com/showthread.php?t=1949687) and downloaded the stock firmware. I stayed with android 4.3 because i read that I can no longer downgrade to a previous android version. Proceeded to flash the Stock firmware 4.3 using Odin 1.85. The process completed on the first try. SUCCESS!! Boot up phone, got past logo, home screen appeared. SUCCESS!! Here, I thought that I was done and my phone was finally working again. So I begin to tweak the settings for my own preferences. I didn't flash anything else or try to root the phone again. I was just plain using the Stock 4.3 firmware that I got from the thread above. After about 10 or so minutes of using the settings, the phone freezes and becomes unresponsive. Won't restart by holding the power button or return to the home screen with the home button. Only other option was to remove the batter and restart the phone. This time, the phone doesnt make it past the Samsung logo screen, and I can no longer boot into recovery. It was stuck on a boot loop and could only be turned off by removing the battery. It didn't occur to me that I should flash Clockworkmod Recovery to reset/format to factory and clear cache as I have read previously and thought that I could just re-flash the stock again. Nope, the same issue came up in Odin as it did with the pre-rooted firmware. Again, I went through the process of checking that Odin was no longer communicating with the phone before unplugging and restarting the procedures to flash the firmware. After about 3 times, the 4th time after unplugging, the screen that tells you "Firmware upgrade encountered an issue, Please select recovery mode in Kies & try again". And when I try to flash again using odin, I get the following message
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUENC2_T999TMBENC2_T999UVUENC2_HOME.tar.md5 is valid.
<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> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Troubleshoot Stage 4
New problem! I now no longer have a PIT partition........and reading around, I found this thread (http://www.sammobile.com/forum/showthread.php?t=15719) of someone who has the same error message coming up in Odin. Thus, I found the PIT file via this thread (http://forum.xda-developers.com/showthread.php?t=1848267&page=4) using the link given by DocHoliday77. Downloaded the T999_16GB.pit as the back panel of my phone indicated that the phone was 16GB. I begin trying to flash with Odin 1.85, checking Auto Reboot, re-partition, and F. Reset Time, including the PIT file and using the Stock 4.3 firmware. This didn't work and only came up with the following error message
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUENC2_T999TMBENC2_T999UVUENC2_HOME.tar.md5 is valid.
<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> Initialzation..
<ID:0/012> Set PIT file..
<ID:0/012> DO NOT TURN OFF TARGET!!
<ID:0/012> Complete(Write) operation failed.
<ID:0/012> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Tried, the same procedure with the pre-rooted 4.3 firmware, still the same message. And haven't gotten past this point since.
Looking back at what I choose to do to try an fix this shutting down problem, I realize there were a few things I could have tried before moving on. But now what I really want to figure out is whether or not my phone can be saved. What have I not tired and what is the end of end to rescue this phone or if its even worth rescuing. I read that JTAG would be the final resort, and I will take that into consideration. Any feedback on what procedures I could've missed would be great as well (for future reference). Thanks for reading this long post and I really do hope I can get this resolved.

I'll try to answer some of this but tbh, tl:dr.
I can very much appreciate a very thorough and detailed post when someone is asking for help. Don't take this the wrong way, but this was a bit much. I could've answered hours ago, but didn't have the time to read it. More importantly though, the majority of people will see how long it is and just close the thread and move on. Like I said, details are good to include, but it gets to a point where it's too overwhelming. Right now I don't even remember a good chunk of what you wrote, and I wasn't able to read it all to begin with.
Not trying to lecture you or anything, but wanted to address it in case it can help you in the future.
I'll try to answer what i can real quick... first, don't use Odin 1.85. That is a very old version. You should only use 3.07 or above. Best to stick with 3.09 or 3.10.
Try the pit file with one of those.
Put the pit file in the pit section and make sure re-partition is checked. Put the firmware in AP. F-Reset time and auto reboot should also be checked, but nothing else.
It does sound a lot like a faulty power switch probably caused all of this. The constant rebooting, crashing and boot looping can and will cause corruption. This is probably what happened to its internal pit. if so, it is very highly likely there is more corrupted data on some of the individual partitions. Depending on which ones, you may or may not be able to fix it without a jtag service.
It is also possible the memory itself could be damaged. If this is the case, the only option is a motherboard replacement. You probably won't know this for sure though unless you try a jtag repair and it fails.
I will say that if the power button is faulty, you should absolutely get that fixed before doing much else. Otherwise it could just bring you right back to where you are now.
If it were me, I would look for a device on ebay with a broken lcd, but a good motherboard with clean imei. Then swap the board. Otherwise it seems to me you'd be spending money on repairs that may or may not work.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Thanks you so very much for the reply! Sorry that it was long and looking at it again, It really is TL: DR. I will keep that in mind for any future posts.
I have tried different versions of Odin 3.04, 3.06, 3.07, 3.09. The first two version also give the same message as version 1.85 while the latter two stall at initializing for more than and hour and there doesn't seem to be any progress. I will try Odin 3.10 and see what happens there.
I guess buying a broken LCD phone would be the best course of action cost-wise afterwards if Odin 3.10 doesn't work. Again I really can't thank you enough for all the help and taking the time to read my post.

Quick tip on buying used devices like that...Be Careful! Pay extra close attention to how every listing is worded. Only buy ones that say things like:
Fully functional except display
Powers on but no picture
Some will try to trip you up by using "clever" phrases, or trying to lead you to assumptions. Also, try to only but from sellers with excellent ratings and a large number of them. They will be more likely to help you if you have a problem.
Good luck!
Sent from my SGH-T999 using Tapatalk

Death S4 mini / hard brick

Hi, suddenly my S4 Mini crashed and it doesn't boot up anymore.
It doesn't enter into recovery mode, but enters into download mode.
So I flashed i flashed the stock firmware via Odin and the procedure freezes in the beginning, so i tried 2-3 times and now my phone is a paperweight, completely dead.
How can I fix it? the JIG USB will resolve the problem?
Thanks
Bye

I got same issue 1 year ago. My phone getting Samsung logo and restarting all the time. I flashed many roms in 1 day. Phone getting hot while flashing rom. Also weather is too hot. Unfortunately i burned my phone's hardware partition (I think I burned baseband).
I thought I gave my phone to phone repair shop which has jtag. I don't want to gave it Samsung service because I lost my guarantee with rooting it. But my father said "you already have guarantee. 2 years didn't exist after you bought your phone. You should gave your phone Samsung service"
I gave it to Samsung authorized service. I said that I was upgrading my phone via Kies. (I was too excited while I was saying this) After that my phone couldn't turn on. (I know I told lie but I need to get fixed my phone without money ? )
After 3-4 day i went there again to take my phone. They gave my phone and told me "your phone's mainboard and sub (charging input socket) were changed.
I was shocked ?. They didn't controlled my phone if it was attained knox counter.
Sorry for my bad English.
Maybe I can't help you but I wanted to share this event that I lived it.
GT-I9190 cihazımdan Tapatalk kullanılarak gönderildi

Odin blocks in this point:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9195XXUAMF5_I9195ITVAMF2_I9195XXUAMF5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> tz.mbn
<ID:0/008> NAND Write Start!!

Same thing happened to my S4 mini Duos on 11th February. My phone was on Stock Samsung Firmware, Custom Recovery, Custom Kernel, and of course rooted.
I changed to stock in December. It was working fine for a month. I texted my friends and after 15 minutes I took out my phone to make a call and I found it was powered off. Then I tried to power on. No response. Then I charged the battery using external battery charger as my phone was not showing charging logo.
After some time, it showed logo and entered Download mode. But didn't enter Recovery mode.
I did a complete flash (nandroid erase all) through ODIN. Not entering custom recovery as well as stock recovery. It shows "recovery booting" but restarts right after that. Stuck on Samsung logo. Just vibrates and reboots again and again.
I gave the phone to a Samsung Authorized Service Center, they declared my phone as hopeless. They say the motherboard is faulty and it needs replacement.
I never even dropped my phone or overclocked the cores. I had been using it gently. I really don't know what to do now. Here I am, looking for a solution.

So, I see that there are more and more people with a same problem and there is no clue what is the cause of the problem. I started a topic with a same question about month ago, but without any reaction.

Hi... I got something similar going on.
Samsung s4 mini running CM13 NIGHTLY (cm-13.0-20160214-NIGHTLY-serranoltexx.zip) Yesterday, I Downloaded Feb 18th nightly and decided to update other apps as well.
Today, as I updated some apps on the play store and got "insufficient message". Decided to make SD Card part of internal memory. Went thru the process and it transferred about 3GB into the SD Card. Afterwards, I proceeded with the CM update. A small screen came up saying it was preparing for upgrade and then it rebooted in recovery, as usual, but this time it blacked out. It just wont go into recovery mode.
Should I try to boot with a different SD Card with the CM update? Is there a way to do it on download mode?
Any suggestions would be great! thanks

Samsung S9+ Live Demo Unit (How Can I Flash?)

Hello there!
I have a S9+ Live Demo Unit and I want to remove the retail mode.
I made it with a Note 8 (N950X). It was easy, I installed Odin in my PC, and I installed the non-retail firmware.
Can I do the same in my S9+?
HELP PLEASE!

Short answer yes. How did you get a demo unit this quickly?

Why do you want to install original firmware into an LDU? Stolen from store?

stearic said:
Short answer yes. How did you get a demo unit this quickly?
Click to expand...
Click to collapse
I work in mobile phone sector.
Fozec said:
Why do you want to install original firmware into an LDU? Stolen from store?
Click to expand...
Click to collapse
Because I have one, it's a gift, and I want to use all the features (except SIM).
Can you help me? (IT'S NOT STOLEN, 100% LEGAL)

Help please, I need to use it as a normal phone (using only WiFi)

Do I have to install Odin in my PC and flash the S9 with the original firmware?

Cristianeon said:
Hello there!
I have a S9+ Live Demo Unit and I want to remove the retail mode.
I made it with a Note 8 (N950X). It was easy, I installed Odin in my PC, and I installed the non-retail firmware.
Can I do the same in my S9+?
HELP PLEASE!
Click to expand...
Click to collapse
Starting with the S8/Note8, Samsung has removed the baseband chips (actually has never included it in the factory) so even if you manage to flash it with stock firmware, it will never pick up a signal no matter what you do. And no, you can't solder in the baseband chips, they are custom chips and extremely difficult to solder being fine pitched surface mounts.
You best option is to try to flash it with the latest stock firmware, disable the MDM security, and use it on WiFi only.
By the way, the N950"X" version is not even a US Qualcomm model, but an international Exynos based main board, so don't waste your time trying to flash the "U/U1" firmware. Try the international "F" version, but most likely it will only accept the specially modified "X" firmware.

billa said:
Starting with the S8/Note8, Samsung has removed the baseband chips (actually has never included it in the factory) so even if you manage to flash it with stock firmware, it will never pick up a signal no matter what you do. And no, you can't solder in the baseband chips, they are custom chips and extremely difficult to solder being fine pitched surface mounts.
You best option is to try to flash it with the latest stock firmware, disable the MDM security, and use it on WiFi only.
By the way, the N950"X" version is not even a US Qualcomm model, but an international Exynos based main board, so don't waste your time trying to flash the "U/U1" firmware. Try the international "F" version, but most likely it will only accept the specially modified "X" firmware.
Click to expand...
Click to collapse
You are wrong. I made It by myself.
I'm Spanish, so I have the Exynos model.
I installed the F Firmware And everything OK.

Cristianeon said:
You are wrong. I made It by myself.
I'm Spanish, so I have the Exynos model.
I installed the F Firmware And everything OK.
Click to expand...
Click to collapse
In the US we have the "X" model which I have physically opened up and the baseband chips are missing, while on other models they removed the sim card contacts completely and it's not resolderable. Look they are not dummies, they know exactly what they're doing.
You can clearly see the empty solder pads which normally are populated with chips. So please don't jump to conclusions so fast before checking the facts.

Cristianeon said:
You are wrong. I made It by myself.
I'm Spanish, so I have the Exynos model.
I installed the F Firmware And everything OK.
Click to expand...
Click to collapse
so you already did it on Note 8 and need help with S9?
why dont you try it and let us know?

I HAVE SAMSUNG S9+ LDU TOO IN PAKISTAN BUT STILL FACING ISSUE TO FLASHING SM-G965X TO SM-G965F PAK FIRMWARE DOWNLOAD FROM UPDATO.COM
<ID:0/003> 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..
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> param.bin
<ID:0/003> dqmdbg.img
<ID:0/003> userdata.img
<ID:0/003> Home Binary Download
<ID:0/003> Total Binary size: 4886 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> up_param.bin
<ID:0/003> cm.bin
<ID:0/003> keystorage.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
SOFTWARE STILL WORKING ON IT NOTHING GOING ON PAST 20 MINS
FIRMWARE INFO
Country / RegionPakistan
PDAG965FXXU1ARC5
Product CodeAK
CSCG965FOXM1ARC4
PhoneG965FXXU1ARC4

So, did it work on the S9+? which firmware did you flash?

Software working good all option done only samsung account not working like samsung store,theme store etc.

what did you use to flash the s9+ live demo cause nothing is working for me

Kwamisky said:
what did you use to flash the s9+ live demo cause nothing is working for me
Click to expand...
Click to collapse
Share your phone systems details csc bootloader etc etc then ill send you download link for s9 or s9+

Cristianeon said:
Hello there!
I have a S9+ Live Demo Unit and I want to remove the retail mode.
I made it with a Note 8 (N950X). It was easy, I installed Odin in my PC, and I installed the non-retail firmware.
Can I do the same in my S9+?
HELP PLEASE!
Click to expand...
Click to collapse
yo tambien trabajo en telefonia movil y tengo un demo s9+ de una promo de samsung. me lo he quedado, consegui flashearlo y ponerle una room stock y quitarle el modo demo.. lo unico que no he podido es hacer que pueda tener una tarjeta sim y tener internet 4g o llamar.. incluso lo rotee pensando que podria asi meterle un imei a la fuerza con las aplicaciones para cambiarlo.. y nada.. no lo he conseguido.. ya no se que mas hacer..

Dude help me to which firmware you Installed please help me by saying via Odinsta?
Cristianeon said:
You are wrong. I made It by myself.
I'm Spanish, so I have the Exynos model.
I installed the F Firmware And everything OK.
Click to expand...
Click to collapse
Which f firmware you Installed please give me tutorial please:crying:

Thanks for your experience. I am stuck with same case. I have been trying to install the F version on the US Galaxy S9+. The greater problem my LDU has is that the date is incorrect and no settings is enabled to allow me make any adjustment. Every necessary settings greyed out. Odin flash attempts all failed and Samsung Kies will always say I should enable USB debugging to even see and recognize my device but that option in developers mode is all greyed out and not allowing enabling. Same thing with factory reset not allowed. What can I do to at least use the Wifi because now it cannot connect due to incorrect date setting still whowing March 2018?

shalomige said:
Thanks for your experience. I am stuck with same case. I have been trying to install the F version on the US Galaxy S9+. The greater problem my LDU has is that the date is incorrect and no settings is enabled to allow me make any adjustment. Every necessary settings greyed out. Odin flash attempts all failed and Samsung Kies will always say I should enable USB debugging to even see and recognize my device but that option in developers mode is all greyed out and not allowing enabling. Same thing with factory reset not allowed. What can I do to at least use the Wifi because now it cannot connect due to incorrect date setting still whowing March 2018?
Click to expand...
Click to collapse
If you want to factory reset but cannot enter recovery for whatever reason, set up security to wipe your device if the wrong code has been entered 10 times, then enter the wrong code 10 times

Samsung Galaxy S9+
*Detection* said:
If you want to factory reset but cannot enter recovery for whatever reason, set up security to wipe your device if the wrong code has been entered 10 times, then enter the wrong code 10 times
Click to expand...
Click to collapse
My problem is that those security settings are not enabled for change as they are greyed out. So I wouldn't even know where to go to set up security to wipe off device. Moreover, I don't usually log on to the phone with code. Are you suggesting I set up code to open the phone screen so that I can enter wrong one or which other code are you referring to? Thank you Sir.