Big problem...
After flashing 9.3 on SGS2 without wiping i rebooted in cwm and flashed siyah 2.6.2.
After that the phone stuck on the omega logo and did not boot.
I rebooted into CWM wiped cache/davlic etc and i tryed to reflash the 9.3 and the siyah.
After that i tryed to flash the kernel but the phone restarted itself and since then it doesnt boot at all neither in CWM or into android.
Only in download mode and it's not recognized by ODIN or kies.
ODIN:
ID:0/003> Added!!
<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> zImage
<ID:0/003> NAND Write Start!
Kies: The device is not responding.
BUT windows is recognizing the phone in devices.
What should i do?
IF i try to turn it on it appears a phone-triangle-pc logo and nothing happens after that.
angelossssss said:
Big problem...
After flashing 9.3 on SGS2 without wiping i rebooted in cwm and flashed siyah 2.6.2.
After that the phone stuck on the omega logo and did not boot.
I rebooted into CWM wiped cache/davlic etc and i tryed to reflash the 9.3 and the siyah.
After that i tryed to flash the kernel but the phone restarted itself and since then it doesnt boot at all neither in CWM or into android.
Only in download mode and it's not recognized by ODIN or kies.
ODIN:
ID:0/003> Added!!
<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> zImage
<ID:0/003> NAND Write Start!
Kies: The device is not responding.
BUT windows is recognizing the phone in devices.
What should i do?
IF i try to turn it on it appears a phone-triangle-pc logo and nothing happens after that.
Click to expand...
Click to collapse
1) Get the right CF Kernel from the Chainfire kernel thread in the Android Original Development Thread. Extract the zip to get a TAR and extract the TAR to get a z-image file. Also download the corresponding original stock kernel from the Intratech thread in the same section.
2) Flash the TAR in PDA using Odin. Do not click repartition. This lets you boot with with functional Root and CWM.
3) If you want to get rid of the yellow triangle, then load the z-image file into /sdcard. Reboot into download mode and use Odin to flash the stock kernel (again in the PDA without repartition). After that, go to the CWM app, choose flash kernel and locate the zimage and proceed.
NB: You can read Chainfire and Intratechs threads in case I was vague somewhere.
Thanks mate but i already know and did all these.
The thing is what i do in order to bring my phone back to life.
What is 9.3 you flashed ???
Kies: The device is not responding.
Why are you using KIES to flash a rom is it open and preventing Odin from working .
jje
Are you saying Odin does it doesn't recognise your phone?
In the past Odin flashing has gone wrong and can usually be fixed by a PC reboot or rebooting into download mode again.
Sent from my GT-I9100
9.3 = Omega 9.3 rom.
No i'm not.
I installed kies to see if the phone is recognized. After i realized that it's not i uninstalled the kies.
The thing is that odin sees my phone but stacks at <ID:0/003> NAND Write Start!
With 115 posts no reason for you not to ask in the rom thread as its possible its rom specific .
Dont think it is but worth a try .
Choices try Odin on another PC .
Take phone to service centre and hope it is not an expensive repair .
Buy a JTag machine .
jje
Just tryed odin on another pc and i got the same result...
i had the same problem and tried flashing the PIT thinking it might do something, but ended up fully bricked. couldnt power on anymore. only way is to JTAG it now, if odin cant flash it.
read this thread maybe it can help
http://forum.xda-developers.com/showthread.php?t=1382838&highlight=unbrick
angelossssss said:
9.3 = Omega 9.3 rom.
No i'm not.
I installed kies to see if the phone is recognized. After i realized that it's not i uninstalled the kies.
The thing is that odin sees my phone but stacks at <ID:0/003> NAND Write Start!
Click to expand...
Click to collapse
Were you flashing using Odin without Kies installed? As far as i'm aware Kies must be installed but not running to flash with Odin.
Nothing worked
The phone is off to Samsung service.
Thanks for your help people.
Related
Dear friends,
I think i soft bricked my phone and i do not know what to do.
First i was on 2.3.6 (GB) Sensation N ROM (2.0). Then i desided to go for a stock ICS (4.0.4) and downloded I9100XWLPM (4.0.4) and flashed it with Odin (only PDA file). The flash was sucessfull but i didnt like to experiance of 4.0.4 (i was unable to reach my contacts through the numpad - phone.apk force closes) and i decided to go back to Offical GB (2.3.6) firmware. I flashed with Odin
GT-I9100_XEU_I9100XILA3_I9100XWKI1_I9100XEUKH2 firmware and the flash was suceful. But after restart it gives me force closes on the first boot screen (Google Services framework, Softaware update aplocation) and self restarts and then the same again.
Then i flashed with Odin the "new" GB Bootloader GT-I9100 and the same file again but the result was the same. And then something hapened and i did not manage to flash any more with Odin (flash unsucessful ).
So then i flashed again with the follwing PIT file (i9100_u1_02_20110310_emmc_EXT4-stock.pit) and the
PDA (GT-I9100_XEU_I9100XILA3_I9100XWKI1_I9100XEUKH2.tar.md5) and the flash was sucesfull but i have the same problems with the force closes on the first boot screen.
I am out of ideas and do not know how to proceed.
Any help will be apreciated!
hristo2000 said:
Dear friends,
I think i soft bricked my phone and i do not know what to do.
First i was on 2.3.6 (GB) Sensation N ROM (2.0). Then i desided to go for a stock ICS (4.0.4) and downloded I9100XWLPM (4.0.4) and flashed it with Odin (only PDA file). The flash was sucessfull but i didnt like to experiance of 4.0.4 (i was unable to reach my contacts through the numpad - phone.apk force closes) and i decided to go back to Offical GB (2.3.6) firmware. I flashed with Odin
GT-I9100_XEU_I9100XILA3_I9100XWKI1_I9100XEUKH2 firmware and the flash was suceful. But after restart it gives me force closes on the first boot screen (Google Services framework, Softaware update aplocation) and self restarts and then the same again.
Then i flashed with Odin the "new" GB Bootloader GT-I9100 and the same file again but the result was the same. And then something hapened and i did not manage to flash any more with Odin (flash unsucessful ).
So then i flashed again with the follwing PIT file (i9100_u1_02_20110310_emmc_EXT4-stock.pit) and the
PDA (GT-I9100_XEU_I9100XILA3_I9100XWKI1_I9100XEUKH2.tar.md5) and the flash was sucesfull but i have the same problems with the force closes on the first boot screen.
I am out of ideas and do not know how to proceed.
Any help will be apreciated!
Click to expand...
Click to collapse
install a custom kernel like siyah through download mode.....go to recovery and do a full wipe .....clear dalvik-cache and reboot
you should of posted it in the QA thread, its not bricked, just needs a proper format
http://forum.xda-developers.com/forumdisplay.php?f=1148
mysterio619 said:
install a custom kernel like siyah through download mode.....go to recovery and do a full wipe .....clear dalvik-cache and reboot
Click to expand...
Click to collapse
Ok, i flashed Siyah-v3.3.3d.tar (i load it as PDA in Odin) but the flash was unsucessful:
Here is the log:
<ID:0/009> Added!!
<ID:0/009> Removed!!
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Complete(Write) operation failed.
<ID:0/009> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
What shoud i do?
do u having kies installed by chance? update the Samsung driver again.. if u using win 7 then run running Odin as admin..try every possible way
Prashanthme said:
do u having kies installed by chance? update the Samsung driver again.. if u using win 7 then run running Odin as admin..try every possible way
Click to expand...
Click to collapse
Hi,
I did everything. I uninstalled KIES. I installed again the USB drivers. I restarted the PC. I ran Orin (v1.85) as administrator and flashed. Flash froze at SetupConnection..(1 hour) Here is the log:
.<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
I give up. I will call my provider to fix the phone.
I will keep all of you posted for what hapened!
hristo2000 said:
Hi,
I did everything. I uninstalled KIES. I installed again the USB drivers. I restarted the PC. I ran Orin (v1.85) as administrator and flashed. Flash froze at SetupConnection..(1 hour) Here is the log:
.<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
I give up. I will call my provider to fix the phone.
I will keep all of you posted for what hapened!
Click to expand...
Click to collapse
offfff....i did it......i removed the battery and then went again in download mode and managed to flash the kernel........:laugh:
...it looks like that the download mode was struck...
thank a lot!
Hello,
I've pretty much exhausted all my brainpower trying to figure this one out. I have an I9305 S3 which I am trying to root, I have all the correct drivers installed and Odin v3 shows blue COM4 ID box. When flashing anything, I get this:
<ID:0/004> Added!!
<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.img
Click to expand...
Click to collapse
Then it gets stuck and does nothing. I tried to flash CWM recovery first, and it would say this:
<ID:0/004> Added!!
<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> recovery.img
Click to expand...
Click to collapse
So it appears it tries to flash boot.img or recovery.img but gets stuck. Unplugging the phone and rebooting shows everything to be working and still stock, in other words nothing really happens.
Tried several methods, both using Odin3 v1.87 and v3.07 directly, and via the Galaxy S3 Toolkit, also tried flashing various packages in the S3 Toolkit as well as pre-rooted firmware, all with the same result. Tried uninstalling all Samsung drivers and then installing via the Toolkit. Never installed Kies before but I tried installing Kies and letting it install drivers, then using Odin, still same result. Can anyone help?
DkNINJA said:
Hello,
I've pretty much exhausted all my brainpower trying to figure this one out. I have an I9305 S3 which I am trying to root, I have all the correct drivers installed and Odin v3 shows blue COM4 ID box. When flashing anything, I get this:
Then it gets stuck and does nothing. I tried to flash CWM recovery first, and it would say this:
So it appears it tries to flash boot.img or recovery.img but gets stuck. Unplugging the phone and rebooting shows everything to be working and still stock, in other words nothing really happens.
Tried several methods, both using Odin3 v1.87 and v3.07 directly, and via the Galaxy S3 Toolkit, also tried flashing various packages in the S3 Toolkit as well as pre-rooted firmware, all with the same result. Tried uninstalling all Samsung drivers and then installing via the Toolkit. Never installed Kies before but I tried installing Kies and letting it install drivers, then using Odin, still same result. Can anyone help?
Click to expand...
Click to collapse
try to flash use mobile odin by chainfire
this more safety way
hrcell said:
try to flash use mobile odin by chainfire
this more safety way
Click to expand...
Click to collapse
I can't since I can't get root on my phone.
Just fixed it. After all this time it appears to be a USB port / driver issue. I had a Galaxy S3 I9300 previously and I think there were some conflicts, I switched to a new USB port and everything finished without an issue. Interesting side note, I suspected the problem because when I plugged in the I9305 and tried to copy files to the phone, it gets stuck for any files over a couple of MB in size. I plugged in my old S3 (I9300) and there were no problems. Changing the I9305 to a new port fixed everything.
Guys help..
I was trying to get my phone back to basic and I tried to install an official firmware by using odin 3, and it failed..
Now I am stucked???
My phone failed and know its saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & Try again"
What to to??
what does the log say?
Glebun said:
what does the log say?
Click to expand...
Click to collapse
log???
yes, the Odin log.
Sivasli_ said:
Guys help..
I was trying to get my phone back to basic and I tried to install an official firmware by using odin 3, and it failed..
Now I am stucked???
My phone failed and know its saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & Try again"
What to to??
Click to expand...
Click to collapse
Before flashing, make sure you have all necessary drivers installed and that you have more than 50% (30% is the absolute minimum) of battery left. Then download a ROM (I.e. from sammobile.com/firmware) and make sure that is is the right ROM for your device. If you download something that is for a different device, you may end up bricking it.
Then boot your phone into Odin mode (I think you know how to do that?) and connect the phone to your PC. Wait for the PC to recognize the device as a serial CDC (That's what Windows 7 and Vista usually show) and then wait for Odin to recognize the device. Then (If you have not already) load all the files into Odin (PDA - ROM and kernel, Modem - Phone, CSC - CSC) and hit "Start".
Then it should download fine. If you are still having trouble, feel free to PM me and I'll gladly help via TeamViewer
Lg
Sound to me like Kies was running in the background while you made the Odin flash.....you must disable Kies before using Odin
No Kies was not running in the backgorund..
Could it be, because I was going from 4.1.2 down to 4.0.1 for example? It is a old firmware..
I solved my problem with installing an Omega Rom v43, but I still want to back to original firmware..
what does the log say?
I dont now how to look at the log..
Can I just flash the original firmware even that I am on a Omega firmware?
Glebun said:
what does the log say?
Click to expand...
Click to collapse
Here is what the log says..
<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> tz.img
<ID:0/004> NAND Write Start!!
<ID:0/004> sboot.bin
<ID:0/004> system.img
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
Sivasli_ said:
No Kies was not running in the backgorund..
Could it be, because I was going from 4.1.2 down to 4.0.1 for example? It is a old firmware..
I solved my problem with installing an Omega Rom v43, but I still want to back to original firmware..
Click to expand...
Click to collapse
The new 4.1.2 bootloader (I assume you have it, unless you specifically replaced it with the older one) will blacklist older bootloaders and prevent them from being installed. This might be part of the problem.
Well i had soft bricked s2 before and it was easly repeired by flashing stock rom via odin. But now its diffrent, only thing i can enter is download mode(odin mode), when i try flash stock rom odin stops on cache.img, when trying to flash cwm it stops on NAND write starts. I tried this with all odins i found, also tried diffrent roms. kernels but its same. Also if i try to flash kernel flash count gets bigger and if i try to flash tom it stays the same :/
doing 3 step flash(from odin troubleshoot ):
<ID:0/003> Added!!
<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.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> data.img
Click to expand...
Click to collapse
update: tried to flash counter reset and it seems it worked, so its not odin problem:/
Is there someone who can help me?
Oh yeah! I had the same problem with my SGS plus, everybody told me that i could only repair it with odin, but i brought my device in Samsung Assistence and they repair my device with warrantly ( i had Cwm recovery and root permissions ) so if you can bring your device in samsung assistence and say:"within i update my device at 4.1.2 jb with kies, my pc turned off" they probably will ask you ( if u dont have warrantly) max 50 $ ( in my country 25€ for update a device )
REMEMBER TOUCHWIZ IS DEAD, CYANOGENMOD IS THE FUTURE, AND THE FUTURE IS NOW
have you by any chance did a factory reset in stock 4.0.4 ? if so you might have hit the " superbrick " which kills the internal memory . then there is no internal memory to write to .
What was the last working state and what did you do that became to this ?
i had 4.4.2 omni rom after that tried factory reset :/
well my warranty is long time gone, but i have heard that samsung has given 5years warranty for all samsung mobiles or so,
hey guys,
I don't have a recovery mode (getting white screen instead). only download mode.
I downloaded the correct firmware and tried install and it failed (in system.img) and requested a PIT file.
I downloaded the PIT file and it got failed again.. I tried to install this twrp thing and still not good.
This is what I get when I try to install pit + twrp (auto reboot, re-partition and f. reset time are checked):
<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> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
Edit:
I've tried with the nand checked aswell and got this:
<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> Erase...
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any idea?
Thank you guys!
Have you tried different cables, are you using a USB port on the motherboard?.
The drivers work because it sees the phone in odin.
Are you loading the stock firmware AND the pit file at the same time?.
If you can answer yes to all of those then it's a bin job.
I don't recommend trying to flash a pit and TWRP at the same time. I only recommend using a pit file, when necessary, with stock firmware.
shivadow said:
Have you tried different cables, are you using a USB port on the motherboard?.
The drivers work because it sees the phone in odin.
Are you loading the stock firmware AND the pit file at the same time?.
If you can answer yes to all of those then it's a bin job.
Click to expand...
Click to collapse
Yes, tried a different cable.
Yes, I used a USB port on the motherboard
Yes it's a stock, and tried separately and didn't work.
Damn
audit13 said:
I don't recommend trying to flash a pit and TWRP at the same time. I only recommend using a pit file, when necessary, with stock firmware.
Click to expand...
Click to collapse
I tried to use only the pit but all i get is that error. It didn't matter if I used a TWRP / stock firmware.
Don't flash using only the pit file.
Flash twrp or stock ROM without pit.
If flashing the stock firmware on its own fails or it says about a pit partition in odin then load both the pit file and the stock firmware at the same time. If it fails to flash them you can safely assume the phone has a corrupt nand and is dead.
You can also try flashing older versions of the recovery, twrp or cwmr. The last official cwmr was the most stable for me and helped me recover from a f*ked twrp that caused the e:failed to mount errors.
If it can take a flash of any type it might be recoverable. Just because it fails a flash doesn't mean its dead dead, just borked beyond the usual capability of the average Joe bloggs..
I would recommend, just for the fact it can't get any worse than what it already is, find the stock firmware in separate files along with the last official cwmr and flash them one by one and when you get the fail errors you'll know exactly what part of the nand is faulty. Basically just mess with it until you kill it. If it jumps into life in the meanwhile then you got lucky and should put a ticket on the lottery!.
Hope this helps inspire a bit of confidence!.
audit13 said:
Don't flash using only the pit file.
Flash twrp or stock ROM without pit.
Click to expand...
Click to collapse
I tried it, didn't manage to succeed.
shivadow said:
If flashing the stock firmware on its own fails or it says about a pit partition in odin then load both the pit file and the stock firmware at the same time. If it fails to flash them you can safely assume the phone has a corrupt nand and is dead.
You can also try flashing older versions of the recovery, twrp or cwmr. The last official cwmr was the most stable for me and helped me recover from a f*ked twrp that caused the e:failed to mount errors.
If it can take a flash of any type it might be recoverable. Just because it fails a flash doesn't mean its dead dead, just borked beyond the usual capability of the average Joe bloggs..
I would recommend, just for the fact it can't get any worse than what it already is, find the stock firmware in separate files along with the last official cwmr and flash them one by one and when you get the fail errors you'll know exactly what part of the nand is faulty. Basically just mess with it until you kill it. If it jumps into life in the meanwhile then you got lucky and should put a ticket on the lottery!.
Hope this helps inspire a bit of confidence!.
Click to expand...
Click to collapse
Hahaha thanks mate, I guess I'll just give up and deliver this phone the place it belongs - hell!
Thanks for the help tho, It will be easier to win the lottery as you wrote