Related
Following this tut;
http://forum.xda-developers.com/showthread.php?t=1125414
Step 5: Connect your device to your PC and start Odin3 v1.83. If you installed Samsung Kies correctly, you should see the box in the top left corner of Odin underneath where it says ID:COM should be Yellow and displaying the name of a Com Port your device is connected to.
I cant get there, it doesnt go yellow. I have kies installed correctly, not sure whats wrong
New to rooting btw
However i do get this error come up;
screensnapr.*com/e/ZXruBp.png
xSirAKx said:
Following this tut;
http://forum.xda-developers.com/showthread.php?t=1125414
Step 5: Connect your device to your PC and start Odin3 v1.83. If you installed Samsung Kies correctly, you should see the box in the top left corner of Odin underneath where it says ID:COM should be Yellow and displaying the name of a Com Port your device is connected to.
I cant get there, it doesnt go yellow. I have kies installed correctly, not sure whats wrong
Click to expand...
Click to collapse
Try this guide - it is tried and tested. http://forum.xda-developers.com/showthread.php?t=1075278
Cheers!
Now its working but it shows FAIL
<ID:0/010> Added!!
<ID:0/010> Removed!!
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Removed!!
<ID:0/011> Added!!
<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> PK
<ID:0/011> NAND Write Start!!
<ID:0/011>
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Did you make sure you are in Download mode, and the drivers were installed correctly? Also, did you make sure you added the kernel file in the correct section? (without ticking any unnecessary things)
Yes.
Now it wont switch on.
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Did you tick the PIT box?
Edit - sorry, just reread, you haven't. I hope..
No i didn't. I restored the original firmware but it still wont turn on normally.
Did you have kies running in the background? Make sure you end all kies applications - end process
Nope had shut kies.
Could be a cable failure. Try a different USB cable.
I only have 1 cable. I restored the kernels and it went green that it worked. But my phone doesn't work.
xSirAKx said:
I only have 1 cable. I restored the kernels and it went green that it worked. But my phone doesn't work.
Click to expand...
Click to collapse
You can get a new USB cable for a couple of bucks. I've got like 6 due to all the devices I've had over the years, and 2 of them are bad. They don't last forever.
Managed to restore device using tutorial i found on google androidcute.*com/install-android-2-3-6-gingerbread-for-samsung-galaxy-s2.html
after restoring i decided to give rooting another go.
all worked out fine, i installed rom manager after and it keeps rebooting itself after every few mins
i have cpu tuner installed too i also restored the original kernel after rooting.
xSirAKx said:
after restoring i decided to give rooting another go.
all worked out fine, i installed rom manager after and it keeps rebooting itself after every few mins
i have cpu tuner installed too i also restored the original kernel after rooting.
Click to expand...
Click to collapse
ROM Manager is the devil. I don't think it plays well with CWM. How are you rooting? If you root using a CF-Root kernel, it will auto-install the CWM app, which I believe does everything ROM Manager does.
I used S2 Root, i uninstalled rom manager though.
xSirAKx said:
I used S2 Root, i uninstalled rom manager though.
Click to expand...
Click to collapse
Is it still rebooting?
Sent from my GT-I9100 using XDA App
It was fine the past 3 hours but its just rebooted again 2 twice in the last 10mins.
xSirAKx said:
It was fine the past 3 hours but its just rebooted again 2 twice in the last 10mins.
Click to expand...
Click to collapse
Last time I had this issue, it was some app I installed, but I couldn't figure out which one. I flashed back to stock and was more selective in which apps I chose to reinstall. I've also made sure that all the apps are on phone memory instead of SD card as there was some speculation flying around that this could also contribute to this issue. Haven't had a random reboot in months now.
Hello everyone,
I am not sure whether this is the right place for my question but my Galaxy S II stopped working and I was wondering if anyone might help me?
I tried updating the FW from 2.3 to 4.0 (I'm guessing) through Kies and after about 45 minutes of seeing both screens (PC and Phone) unchanged, I ended up removing the phone. Next, Kies suggested an "Emergency Firmware thingy" (it said it in German so I wouldn't really know how to translate it). Tried again, after 45 minutes gave up once more.
Since then, I downloaded ODIN and tried to follow instructions I found online to flash it (first I tried with Ice-Cream, then with Gingerbread).
Ever since I removed it from Kies, it would only show a phone connected to a PC with a yellow warning triangle in the middle. Whenevery I use the Volume-Menu-Power button, the warning on changing the OS appears and then, when I press "volume up", it shows the green android in the middle and tells me it's downloading and not to turn off the device, though there is no downloading progress.
When I try with ODIN, ODIN recognizes the device on both USB ports - I found md5 files for Germany but every time I start it the Message window says:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLA4_I9100VIAKI1_I9100XXKI4_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> boot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> cache.img
and doesn'tget any farther than "cache.img".
I am at a complete loss as to what to do or try. I have had this phone for a year now, this is the first time I tried to update with Kies - the phone had not been rooted or anything else. The phone has no simlock (I don't know if any other information is relevant).
Any ideas or has my phone thus become the infamous brick? *pleasenopleasenopleaseno*
Thanks in advance for your time and patience - in case I've overread a thread with this exact same problems, I apologize and would appreciate if someone could re-direct me. I've already spent so much time looking for solutions, my concentration may have suffered.
Best wishes,
Junivere
Before flashing with Odin, did you kill all Kies processes from Windows task manager? If not, do that and then start flash.
Edit: And since you can access download mode, its not bricked...so you can relax
Sent from my GT-N7100 using Tapatalk 2
I9100?
Flash JB.
And try an older ODIN version.
And check kies like the above poster suggested.
Other usb port/usb cable might do the work too.
Sent from the little guy
Thanks for the replies!!!
I stopped all the Kies processes over the task manager before (was that enough?) and tried from both USB ports of my laptop (006 and 007 I guess) with equal results.
I used Odin3 v1.85 - is that too old or too new? Which version should I try?
And I am sooooooooo relieved it's not a brick!!!
Thanks again!
kinda old, try 1.3 or 3.x
And flash siyah v5 just for kicks.
Sent from the little guy
I tried again and I'll try to explain step by step, ok? Maybe you notice something I did wrong?
I killed all the Kies processes in the task manager like before.
I downloaded Odin 3 v.07 and started it. I had "Auto reboot" and "F.Reset time" checked and clicked on "PDA" to add the *.md5 file with the firmware.
I started the phone in the download mode and connected it to the PC, Odin recognized it alright.
I started and the first time, with the USB port in front, it stopped at "cache.img" in the message window.
I tried a different FW file and the other USB port further back and for the first time the phone shows a tiny bit of blue in the progress underneath "Downloading..." but in Odin it is now stuck at "factoryfs.img" for the last ten minutes,
The entire message window says this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLA4_I9100VIAKI1_I9100XXKI4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<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> boot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> cache.img
<ID:0/007> factoryfs.img
Any ideas???
Best wishes and thanks again!!!
Flash siyah V5.
Sent from the little guy
How do I do that? I tried to find an instruction in the XDA forum in the 15 minutes I have between posts but couldn't find anything.
Junivere83 said:
How do I do that? I tried to find an instruction in the XDA forum in the 15 minutes I have between posts but couldn't find anything.
Click to expand...
Click to collapse
gokhanmoral.com
Siyah v5 for SII.
Put it on PDA, press start and flash away.
Sent from the little guy
Ok, so now I am starting to get slightly terrified:
When trying to flash Siyah 5 (Siyah-s2-v5.0.1), it stops there:
<ID:0/007> Added!!
<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> zImage
:crying:
Keep trying, you'll come around.
Another usb cable could help.
Another pc would as well.
Sent from the little guy
Ok, so the Sivyah v5 flash worked when I tried Odin3 v1.3 but I'm still battling with the actual firmware.
Thanks for your help so far, though - I'm really greatful and I'll keep trying.
My mission for today will be finding someone's cable and PC to borrow...
I'll keep you posted, though!
Wow, you are the bestest ever!!!
With a netbook (OS Windows 7) I eventually managed the flash - now I'm reconfiguring everything. I am sooooo relieved!!!!
I have one last question (sorry for being so naive!), though:
Is it still possible with a flashed phone (with the Sivya thing on it) to use Kies to try and update or do automatic updates or do I have to flash all the newer firmware?
Best wishes,
Junivere
Junivere83 said:
Wow, you are the bestest ever!!!
With a netbook (OS Windows 7) I eventually managed the flash - now I'm reconfiguring everything. I am sooooo relieved!!!!
I have one last question (sorry for being so naive!), though:
Is it still possible with a flashed phone (with the Sivya thing on it) to use Kies to try and update or do automatic updates or do I have to flash all the newer firmware?
Best wishes,
Junivere
Click to expand...
Click to collapse
Depends on what ROM you are flashing.
For instance, if you flash LS8 you'll get a 22 mb update to get you to LSD.
I would flash LSD straight up tho.
If you don't want a headache with odin no more, feel free to try Mobile Odin, it will perform all the flashing for you.
Sent from the little guy
I have a US SPH-D710 Sprint Samsung S2.that was working OK on ICS 4.0.4. I decided to upgrade to JB via Kies, following the procedure discussed at the official Samsung page on us on support at SupportOwnersFAQPopup.do?faq_id=FAQ00052384&fm_seq=60310 (sorry, I cannot post links)
I had to install Kies, which was not previously installed. It installed OK. Everything started out well and the phone went to 98% or 99% and then the flash failed. Power cycling, the phone came up with a complaint
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I did recovery mode, to the same effect. I then tried the Simple Upgrade tool, to the same effect. It always got to about 98% or 99% and then failed, giving no information, just a failure..
I uninstalled my anti-virus completely (as it was old anyway and it's time to buy a new license) and tried again. Same thing. The simple downloader fails with "Error Occurred! Cancel Download!!"
Then, I went to QBKing and followed a link from qbking77's web page at how-to-root/root-the-samsung-epic-4g-touch/ to a thread at sxtpdevelopers where I downloaded SPH-D710_GB27_1014481_Rooted_Restore.exe and it fails without giving any reason at "hidden"
<ID:0/006> 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/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> Firmware update start..
<ID:0/006> boot.bin
<ID:0/006> cache.img
<ID:0/006> data.img
<ID:0/006> factoryfs.img
<ID:0/006> modem.bin
<ID:0/006> hidden.img
<ID:0/006>
<OSM> All threads completed. (succeed 0 / failed 1)
No complaint at all, just the above. I have tried multiple times with different USB ports and different USB cables. I have successfully flashed/rooted/Odin'd other Samsung phones from this PC before. It's 64-bit Win7. This specific phone has never previously been rooted or flashed. It was on FL24.
The phone goes into download mode just fine, but is otherwise useless. In download mode, the phone says:
ODIN MODE
PRODUCT NAME: SPH-D710
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
What can I do to bring this phone back to life?
I got it working
I went into my office and, using a computer appropriate for this use there, followed exactly the same steps with the same file, for the simple download tool this time, and using a third micro-USB cable, and it worked on the first try. Go figure. This was after trying various different things for about six hours at home, on my Win7 laptop that has worked many times before for other Samsung phones (an Epic 4G and an S4).
ekuns said:
I went into my office and, using a computer appropriate for this use there, followed exactly the same steps with the same file, for the simple download tool this time, and using a third micro-USB cable, and it worked on the first try. Go figure. This was after trying various different things for about six hours at home, on my Win7 laptop that has worked many times before for other Samsung phones (an Epic 4G and an S4).
Click to expand...
Click to collapse
I think that the problem was that you didn't installed the correct drivers on your windows 7 laptop :fingers-crossed:
Or the file was corrupted, and when you downloaded it in your office, the download of the stock rom was succes full
KingOfDope said:
I think that the problem was that you didn't installed the correct drivers on your windows 7 laptop :fingers-crossed:
Or the file was corrupted, and when you downloaded it in your office, the download of the stock rom was succes full
Click to expand...
Click to collapse
Definitely could have been any of those. I was just confused as I'd successfully used Odin on that laptop with several other Samsung phones, both newer and older than the S2. And also because it always got to 98% or 99% before it failed. I think this tells me I need another Win 7 box at home, for troubleshooting this kind of problem.
Maybe look here
Sent from my SM-T210 using xda premium
theunderling said:
Maybe look here
Click to expand...
Click to collapse
I didn't realize that the Sprint version of this phone was so different from the non-Sprint version (nor that this forum was for the non-Sprint version). I found the forum you referenced, and will direct all future questions for this phone over there. Thanks for the pointer.
Ok,I think theres maybe 20 odd different ones.Someone could think youve a standard s2 and give wrong info based on that.
Hello
For a couple of weeks now, i've been trying to fix this phone for a friend who studies as an artist. She wanted the Galaxy Beam for presentations and bought one used as they seemingly ain't to be found in the stores any longer.
Originally, the firmware ends at 2.3.6 on this brand, but this one was rooted to be fit with 4.1.2.
The phone bugged and hung in weird ways, so i thought to follow the steps into downgrading it to stock rom for her and see if that would help.
I am no expert, but since i have successfully rooted several phones and tablets earlier with no issues (its pretty straight forward when it works, right), i felt up for the tast.
I have spent a lot of time googling the last couple weeks, and reading a lot of solutions here on these forums, but i can't seem to find this ecact problem, so here goes.
Samsung Galaxy Beam GT.I8530
Odin3 v3.07
Windows 7 and 8 fully updated (tried both)
No matter which Android version i chose, it ends up at the same spot. Stuck at logo screen after first boot.
I have tried both with and without a PIT file, same result.
This last try was with a PIT and Android 4.1.2. (i understand that PIT is not nessessary, as it should be baked within the PDA if it's a single file, but what won't you try eventually, right?)
Load Odin, admin rights
Boot phone in download mode
Insert USB
-->
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8530DXLJ1_I8530OLBLJ1_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> cache.img.md5
<ID:0/003> NAND Write Start!!
<ID:0/003> hidden.img.md5
<ID:0/003> kernel.bin.md5
<ID:0/003> modem.bin.md5
<ID:0/003> system.img.md5
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
- here, the phone reboots and loads to logo screen *
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
- from here the phone wont nudge from the logo screen. can reboot, nothing new happens.
No other functions work, other than:
- volume down+home+power (download mode)
- power (boots to logo screen)
Thanks for reading! Hope someone feels up for the task
Edit: It might be vital information that the phone will uncharge the battery at logo screen eventually, even when connected to a computer. (5v output) But i believe this is common somehow.
Also, if i try and shut down the phone, it will reboot into a frozen "star icon".
Bump*
What makes this issue differ from others i've read on these forums, is this:
Akiiras said:
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
Any theories?
As much as i hate bumping, i'm feeling kind of responsible to try and fix it. Hope someone got a clue on what might be wrong. Thanks
"I bet you 10 buck you'll get your answer here within a couple days" -a friend said, well, in norwegian though.
I guess a week later and no response means that i've at least earned 10 buck! ^^
Guess i can give it one more shot here before i send it to a repair guy.
*bump*
Akiiras said:
Guess i can give it one more shot here before i send it to a repair guy.
*bump*
Click to expand...
Click to collapse
Are you sure about the right region when choosing a firmware? Did you also try Odin 1.85? Have you tried flash a custom recovery via Odin and flash a rom manually?
LS.xD said:
Are you sure about the right region when choosing a firmware? Did you also try Odin 1.85? Have you tried flash a custom recovery via Odin and flash a rom manually?
Click to expand...
Click to collapse
Hi, and thanks for the reply!
I am pretty sure i got the right firmware region. At least, the only region that covered my location (norway) that i could find, was nordic.
I have not tried Odin v1.85 or manually. I guess i can find a guide on how to do it manually here somewhere, but i'll go for a shot with the older version of Odin right away.
Thanks!
Akiiras said:
Hi, and thanks for the reply!
I am pretty sure i got the right firmware region. At least, the only region that covered my location (norway) that i could find, was nordic.
I have not tried Odin v1.85 or manually. I guess i can find a guide on how to do it manually here somewhere, but i'll go for a shot with the older version of Odin right away.
Thanks!
Click to expand...
Click to collapse
BTW there are 4 different versions for nodric countries --> LINK
Odin3 v1.85 didn't work. Well, in the sense that it probably does a job well done and says everything went well, but the phone wont nudge past boot screen.
I'll see if i can learn how to do it manually and come back with the result.
Edit:
LS.xD said:
BTW there are 4 different versions for nodric countries --> LINK
Click to expand...
Click to collapse
Oh, thanks! I couldnt find it at sammobile myself, so i found it somewhere else. This could be it!
any developments?
I Have the Same Problem
I Have the same problem please anyone help me!!!!!
SOLUTION
Akiiras said:
Hello
For a couple of weeks now, i've been trying to fix this phone for a friend who studies as an artist. She wanted the Galaxy Beam for presentations and bought one used as they seemingly ain't to be found in the stores any longer.
Originally, the firmware ends at 2.3.6 on this brand, but this one was rooted to be fit with 4.1.2.
The phone bugged and hung in weird ways, so i thought to follow the steps into downgrading it to stock rom for her and see if that would help.
I am no expert, but since i have successfully rooted several phones and tablets earlier with no issues (its pretty straight forward when it works, right), i felt up for the tast.
I have spent a lot of time googling the last couple weeks, and reading a lot of solutions here on these forums, but i can't seem to find this ecact problem, so here goes.
Samsung Galaxy Beam GT.I8530
Odin3 v3.07
Windows 7 and 8 fully updated (tried both)
No matter which Android version i chose, it ends up at the same spot. Stuck at logo screen after first boot.
I have tried both with and without a PIT file, same result.
This last try was with a PIT and Android 4.1.2. (i understand that PIT is not nessessary, as it should be baked within the PDA if it's a single file, but what won't you try eventually, right?)
Load Odin, admin rights
Boot phone in download mode
Insert USB
-->
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8530DXLJ1_I8530OLBLJ1_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> cache.img.md5
<ID:0/003> NAND Write Start!!
<ID:0/003> hidden.img.md5
<ID:0/003> kernel.bin.md5
<ID:0/003> modem.bin.md5
<ID:0/003> system.img.md5
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
- here, the phone reboots and loads to logo screen *
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
- from here the phone wont nudge from the logo screen. can reboot, nothing new happens.
No other functions work, other than:
- volume down+home+power (download mode)
- power (boots to logo screen)
Thanks for reading! Hope someone feels up for the task
Edit: It might be vital information that the phone will uncharge the battery at logo screen eventually, even when connected to a computer. (5v output) But i believe this is common somehow.
Also, if i try and shut down the phone, it will reboot into a frozen "star icon".
Click to expand...
Click to collapse
I have The solution For that remove your battery and charge battery by use of another working mobile or battery charger box
after charging you do the flashing using android 4.1.2
it successfully works on my mobile
the problem is battery is low so that at the time of flashing it turned off ....so fill the battery and use......
Hello, guys. First of all sorry for my english, but I need help.
I am here because I dont know what to do, I have tried everything without success. Let me explain: I have a S3 GT-I9300, I have had it since 2013 and I have gone through everything with it: brick, several rom, resets, etc. On saturday I woke up and my phone was in a boot loop, but I said ''bah, I can fix it in 20 mins'', but as you can see I couldnt do it. First of all, NAND write start error appeared, I havent seen that error before, then partition errors appeared too.
I can enter to dowload mode and it says GT-I9300 in product name, I can enter to recovery but I cant do anything there
I have tried to flash the same stock rom that I always have, it is an emergency firmware that I have used like 5 times, so.... It is weird that it cannot fix this up. I also have tried with Sammobile's firmware, with and without pit, in 3 usb ports and with 2 usb cables and always the same result: FAIL.
I hope you can help me, buying another phone in my country is difficult.
It can be a hardware issue on emmc of the phone if failed after so many different tries
dusterphil said:
It can be a hardware issue on emmc of the phone if failed after so many different tries
Click to expand...
Click to collapse
And what can I do about it?
What is the Odin error? Post the Odin log.
audit13 said:
What is the Odin error? Post the Odin log.
Click to expand...
Click to collapse
This is one of those:
<ID:0/005> File analysis..
<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...
Then it does not do anything (in this case I used 4 files + pit, and those files and pit are the ones that I have always used)
The other one is this:
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
This was the first error that appeared. (this is with sammobile's firmware)
The sboot.bin file is the bootloader. It's probably failing to flash for one or more of the following reasons:
the bootloader in the phone is newer than the bootloader in the ROM being flashed;
the ROM is not for the phone being flashed;
need to try a different USB cable;
need to try a different USB port; and/or
the memory chip in the phone is damaged.
Borked nand. If the rom and cable are known to be good and 2 pc's fail then dead nand. It's unfortunate but it happens.
Beamed in by telepathy
I think the phone is dead, it have faught a lot in this years. Thank you anyways
jeanavila_ said:
I think the phone is dead, it have faught a lot in this years. Thank you anyways
Click to expand...
Click to collapse
It's time for you to get a new model