Hi,
I've think i've caused a problem on my Phone, I tried flashing a number of roms but now after flashing DlevRom 3.1_KI4. And trying to restore it back to Stock.
Its hanging on when using 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> boot.bin
I can use Heimdall to flash my kernel back to stock without any issue. But using Odin it keeps doing the above.
I've tried CF-Root-SGS2_XX_XEO_KI4-v4.4-CWM4 kernel which i'm able to flash and access clockworkmod but i'm unable to flash CyanogenMod rom which is still stored on the phones memory it shows a number of errors.
The default rom/kernel i'm trying to restore to are
ROM - GT-I9100_XEU_I9100XWKI4_I9100XEUKH2_I9100XXKI1
Kernel - Kernel_I9100XWKI4
I've flashed back to these before when it had CyanogenMod on. So i'm not sure what the problem is now.
Anybody got any ideas to help me.
Also when flashing with ClockworkMod, all roms flash very quickly like its not changing anything.
Have you put asn ICS rom on your phone and changed the bootloaders is my first question??
jje
No keeping away from ICS roms at present. I Flashed my phone with DlevRom 3.1_KI4 rom which booted up ok but decided to go have a go again with CyanogenMod. So went into Clockmod selected the ZIP it went thought the process but display error see attached image.
http://img585.imageshack.us/img585/2970/dsc00010ob.jpg
I didn't change the kernel before trying to change to cyanogenmod so it had the kernel from DlevRom.
Then i starting having these problems.
But at present the only way i can change the kernel is using Heimdal. If i try using Odin it freezes.
Hope that makes sense.
That error is telling you it thinks your device isn't an I9100, or the check to determine if it is isn't working correctly. If you're sure you do have an I9100, follow the instructions to install CM7 to the letter, which involve flashing a different kernel first (you said you can do this with Heimdall), and then flashing the CM7 zip twice in succession.
Yes i have a Samsung Galaxy I9100 (UK). Yeah i was able to flash without a problem but then i think i forget to reflash the kernel with the CM7 one. But using Heimdall i'm able to reflash to any kernel without any problems. Its only when i try to flash a rom that it doesn't work.
So now sure how ive done that to make it think i have a differnet type of phone.
I've had CM7 running on the device before and stock but wanted to try a couple more roms. So maybe i've skipped a step somewhere but not sure.
Related
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.
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!
Hi,
I recently tried new Slim 3.0 ROM on my I9300, and noticed it changed my Kernel also as a fan of Siyah I decided to reflash that to my phone but Oden has got stuck during the process.
It hasn't PASS(ed) it is stuck on BOOT the messages in the message log are as follows
<ID:0/005> Added!!
Odin v.3 engine (ID:5)
File analysis
SetupConnection
Initialzation
Get PIT for mapping
Firmware update start
boot.img
NAND Write Start!!
Thats as far as it got, so my question is what can I do?
Cheers
Wrong or bad file flashing is first guess .
jje
Yes, I think was a personal error rather than issue with any of the tools or files i used.
Is it ok to pull the cable out and reconnect to attempt the flash again or is that gonna mess things up?
You can always flash or via recovery
Hello,
My Galaxy s2 is stuck in boot loop, I can see only the GS2 logo.
It went into this situation after holding down power button trying to turn it off.
Tried to remove battery and nothing changed.
Entered recovery mode and did wipe cache and then reboot.
It went past the initial logo, showed samsung animation and then it went back to samsung logo boot loop. It never went to samsung animation again.
From that point on it does not boot to recovery mode, it shows the android robot with the spinning cog for a while and then it goes back to the samsung logo boot loop.
The phone can go to download mode without problem. I have not tried to install a stock firmware through odin, since I would like to get a backup of the sms messages from the phone first. I already have backup of pics, contacts, etc so I dont care about anything else besides the sms.
The phone was running the latest spanish stock JB version
GT-I9100 Galaxy S II
PDA: I9100XWLSD
CSC: I9100FOPLS4
MODEM: I9100XXLS8
Added: 2013-02-03
The only modifications to stock were
. Root when it was running ICS
. CSC change from EUR to FOP (so that it auto upgraded to JB from ICS)
The phone retained root after the auto JB upgrade
Do you know if there a solution to this situation? I am still under warranty so I can take it back to samsung so I would like to avoid installing CWM recovery kernel that would make them immediately reject service due to warranty void.
thank you in advance!
Yes, you can keep trying to flash a stock firmware in Odin. Click the link in my signature if you're having troubles with the flash failing. Flash the JB version you were on before, that's got the most chance of working with out having to wipe.
Personally, I think you're going to have to get a working recovery and factory reset to be honest.
Sent from a galaxy far, far away
Hopper8 said:
Yes, you can keep trying to flash a stock firmware in Odin. Click the link in my signature if you're having troubles with the flash failing. Flash the JB version you were on before, that's got the most chance of working with out having to wipe.
Personally, I think you're going to have to get a working recovery and factory reset to be honest.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
thank you for answering, so if I install the same version through Odin, it will not wipe out the current phone contents by default?
Toliver said:
thank you for answering, so if I install the same version through Odin, it will not wipe out the current phone contents by default?
Click to expand...
Click to collapse
Correct. A 1-part firmware will not wipe by default. If you flash a 3-part firmware (JB leak, LSJ for instance) that WILL wipe by default.
If you flash something other than the firmware you were on directly before the bootloop, you've got pretty much no chance of getting out of the bootloop without a factory reset. If you flash the same firmware you were on before the bootloop, then there's a chance of getting it to boot up with all your data.
If that (flashing with the same stock ROM) doesn't work, then I'm afraid its down to a factory reset, sorry.
Hopper8 said:
Correct. A 1-part firmware will not wipe by default. If you flash a 3-part firmware (JB leak, LSJ for instance) that WILL wipe by default.
If you flash something other than the firmware you were on directly before the bootloop, you've got pretty much no chance of getting out of the bootloop without a factory reset. If you flash the same firmware you were on before the bootloop, then there's a chance of getting it to boot up with all your data.
If that (flashing with the same stock ROM) doesn't work, then I'm afraid its down to a factory reset, sorry.
Click to expand...
Click to collapse
Ok then, I will give it a try and see how it goes. Another solution that I was thinking about is to try to install CWM through odin (i'm not sure if it's possible though) then boot into CWM and get backup through it. Then if I apply a stock firmware through odin, this would remove CWM and install the stock recovery kernel back, correct?
Yes, that's possible. You can flash Philz kernel via Odin, it's stock kernel only with root CWM. Other than that its the same. You could do that procedure using his kernel. When you flash stock rom via Odin then yes, you'd get rid of the custom recovery.
Depending on what you want to do (warranty etc) read up about the flash counter and then triangle away.
Sent from a galaxy far, far away
regarding the 1-part firmware, I downloaded from sammobile the I9100XWLSD_I9100FOPLS4_FOP.zip.
The zip archive contains a tar.md5 file I9100XWLSD_I9100FOPLS4_I9100XXLS8_HOME.tar.md5 and a dll file SS_DL.dll.
So I should use only the tar.md5 in the PDA section of odin, right? should I keep this dll in the same folder as the tar.md5 in case odin needs it?
Also does it make any difference which odin version should I use?
thaks again
Well I suppose it can't hurt to put it in the same directory, but I don't know if it really does anything. Yes, flash it in the pda section.. Which version? Take your pick. I usually use 3.0.4 but have also used others. Click my signature if you want a zip file with a few versions.
Sent from a galaxy far, far away
I tried flashing the same rom as it was installed but nothing changed, after the first boot I see the robot with the cog, a thin progress bar filling below it and then it goes to boot loop. No luck getting into recovery, still the same symptom... Besides the sms backup I am thinking about how to recover it, should I try installing 4.0.3 that was the factory default? Any more ideas??
thanks again
The odin log seems clean though, no error or anything else
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100FOPLS4_I9100XXLS8_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> cache.img
<ID:0/007> NAND Write Start!!
<ID:0/007> factoryfs.img
<ID:0/007> hidden.img
<ID:0/007> modem.bin
<ID:0/007> boot.bin
<ID:0/007> param.lfs
<ID:0/007> Sbl.bin
<ID:0/007> zImage
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/007> Removed!!
And can you try a factory reset from the stock recovery? You're not on 4.0.4 so it'll be safe.
@gastonw, can you have a look here? I know that I've seen Odin passing but still no boot... I just can't remember how on earth it was fixed. It seems I didn't bookmark it either.
Sent from a galaxy far, far away
Hopper8 said:
And can you try a factory reset from the stock recovery? You're not on 4.0.4 so it'll be safe.
@gastonw, can you have a look here? I know that I've seen Odin passing but still no boot... I just can't remember how on earth it was fixed. It seems I didn't bookmark it either.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
Could you provide more details on how to do a factory reset from stock recovery? Do you mean to flash 4.0.3 via odin? Or is it some options in odin that would enforce factory reset?
More details are to search for it mate. It's covered so many times that it's just plain spoonfeeding if I'm to post it.
Sent from a galaxy far, far away
Eventually I made it work by installing the 4.0.3 EUR via odin. I did not allow it to boot into the OS, as soon as it finished flashing via odin, I rebooted into recovery mode. This time it went in successfully. Then I used the CWM recovery kernel that just runs from the sd (it does not install) and got the full backup. Later on by using nandroid manager I recovered the sms messages + more (apps, etc). Thanks for all the help!
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