Hello,
A week ago, my phone was on and suddently reboot.
After that, it boots and arrived to the end of loading, it reboots, and does the same thing again and again.
I tried installing another rom with clockwork mod : still the same.
Tried to format / erase partitions with clockwork and fastboot : still the same.
Tried to install stock rom with fastboot : error, same with odin.
Tried omap : still the same.
And after all of that, nothing changed, it's still bootlooping.
So I don't know what to do.
Thanks for your help.
PS : I used last version of PAC-MAN ROM and a custom kernel (don't remember the name sorry).
aurel2108 said:
Tried to install stock rom with fastboot : error, same with odin.
Tried omap : still the same.
Click to expand...
Click to collapse
What are the errors?
With fastboot :
Code:
Device version-bootloader is 'PRIMELC03'.
Update requires 'PRIMEMD04'.
(I tried to flash bootloader and radio before update.)
With odin :
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> odin.takju.jwr66y.4.3.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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> bootloader.img
<ID:0/003> radio.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
(And a big red FAIL.)
aurel2108 said:
With fastboot :
Code:
Device version-bootloader is 'PRIMELC03'.
Update requires 'PRIMEMD04'.
(I tried to flash bootloader and radio before update.)
With odin :
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> odin.takju.jwr66y.4.3.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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> bootloader.img
<ID:0/003> radio.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
(And a big red FAIL.)
Click to expand...
Click to collapse
Try a different version of Odin
I've got a similar issue that my phone is basically locked on one backup state and can't be flashed. I tried odin as well. first time I had a similar fail like you did. Later I had a success - however it didn't solve my issue...
aurel2108 said:
With fastboot :
Code:
Device version-bootloader is 'PRIMELC03'.
Update requires 'PRIMEMD04'.
(I tried to flash bootloader and radio before update.)
With odin :
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> odin.takju.jwr66y.4.3.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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> bootloader.img
<ID:0/003> radio.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
(And a big red FAIL.)
Click to expand...
Click to collapse
flash attached new bootloader md5 file (unzip) in odin as bootloader. then flash other images with fastboot commands.
samersh72 said:
flash attached new bootloader md5 file (unzip) in odin as bootloader. then flash other images with fastboot commands.
Click to expand...
Click to collapse
I tried, i've got a big blue RESET after flashing bootloader with odin so I don't know if it works.
But after flashing radio and updating image, still the same error. :/
aurel2108 said:
I tried, i've got a big blue RESET after flashing bootloader with odin so I don't know if it works.
But after flashing radio and updating image, still the same error. :/
Click to expand...
Click to collapse
after flashing bootloader, did you boot in fastboot mode (bootloader) and flashed other images?
it failed booting or failed flashing with fastboot?
samersh72 said:
after flashing bootloader, did you boot in fastboot mode (bootloader) and flashed other images?
it failed booting or failed flashing with fastboot?
Click to expand...
Click to collapse
After flashing it, it reboots to the system, and bootloops.
So I get to fastboot myself and tried to flash last stock image (jwr66y).
It failed flashing with fastboot, still the error mentionned before about the bootloader.
aurel2108 said:
After flashing it, it reboots to the system, and bootloops.
So I get to fastboot myself and tried to flash last stock image (jwr66y).
It failed flashing with fastboot, still the error mentionned before about the bootloader.
Click to expand...
Click to collapse
retry with odin, see odin troubleshooting in my thread.
if not, i doubt in a hardware issue
samersh72 said:
retry with odin, see odin troubleshooting in my thread.
if not, i doubt in a hardware issue
Click to expand...
Click to collapse
It's not failing but shows me a blue "RESET", boots to the system and bootloops.
Where can I find another version of Odin ?
aurel2108 said:
It's not failing but shows me a blue "RESET", boots to the system and bootloops.
Where can I find another version of Odin ?
Click to expand...
Click to collapse
try to change also usb cable and usb port. odin link http://www.androidfilehost.com/?fid=23060877489998839
What a bizarre problem...
Hi!
I'm kinda having the same problem. Woke up friday morning (6/12-13) and found my phone in a very strange bootloop.
It boots up, loads for a couple seconds (a little bit longer with the SIM taken out) and then freezes and reboots.
I think I have tried everything. Factory reset, wiped all data in stock recovery, flashed Clockwork recovery and tried to wipe (and format) from there (getting following error: "e: unknown volume /sdcard/.android_secure"), tried flashing via fastboot, flashing via sideload in Clockwork recovery where installation gets aborted. I tried with multi-formatter-v1 to change between ext4fs and rfs but that made no difference. Odin3 v1.85 makes it all the way but has not been able to change anything, the phone still boots up like nothing has happened. Odin3 v3.09 gives me "Complete(Write) operation failed" at the system.img file (tested on two different computers, different USB ports with different cables) and that made me jump over to try the OMAP method.
And even then, when I tried flashing with OMAP (which gives me no error messages) the phone boots up like NOTHING has happened and guess what!? The phone reboots itself! I tried directly after the OMAP flash, to boot in download mode and flash a Odin file but without success.
48 hours later of almost constant googeling with trial and error and it seems like that internal memory is indestructible.
Has it something to do with permissions/rights to write to the memory?
Can somebody help me with this?
I will be forever grateful
oskan.lindgren said:
Hi!
Can somebody help me with this?
I will be forever grateful
Click to expand...
Click to collapse
It took too much time when flashing system before fail ?
I guess your emmc chip is fried.
Sent from my Galaxy Nexus using xda premium
Oh.. that sounds bad...
samersh72 said:
It took too much time when flashing system before fail ?
I guess your emmc chip is fried.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Aha, I don't know whats normal but Odin is working like 10 - 15 minutes before I get the FAIL message on the system.img.
What to do if the emmc chip is fried?
Odin is the worst toolkit ever... it sucks! should be banned
Why don't You try to flash the factory image using the flash-all.bat/flash-all.sh...?
just download the factory image, decompress it, add platform-tools components inside the unzipped folder (fastboot.exe, adb.exe...) connect the phone in fastboot mode and click flash-all...
https://developers.google.com/android/nexus/images?hl=fr-FR#yakju
or
flash it manually using fastboot...
follow the steps in this guide
http://forum.xda-developers.com/showthread.php?t=1626895
or use other toolkits!
enricocid said:
Odin is the worst toolkit ever... it sucks! should be banned
Why don't You try to flash the factory image using the flash-all.bat/flash-all.sh...?
just download the factory image, decompress it, add platform-tools components inside the unzipped folder (fastboot.exe, adb.exe...) connect the phone in fastboot mode and click flash-all...
https://developers.google.com/android/nexus/images?hl=fr-FR#yakju
or
flash it manually using fastboot...
follow the steps in this guide
http://forum.xda-developers.com/showthread.php?t=1626895
or use other toolkits!
Click to expand...
Click to collapse
You are talking about the most famous tool for samsung phones....
Sure fastboot is preferred for NEXUS... But odin still an option
Fastboot will give him same result sir
It will stuck on flashing system.img
Dont use TOOLKIT!
Sent from my Galaxy Nexus using xda premium
Odin is the worst toolkit ever... it sucks! should be banned
Why don't You try to flash the factory image using the flash-all.bat/flash-all.sh...?
just download the factory image, decompress it, add platform-tools components inside the unzipped folder (fastboot.exe, adb.exe...) connect the phone in fastboot mode and click flash-all...
https://developers.google.com/androi...hl=fr-FR#yakju
or
flash it manually using fastboot...
follow the steps in this guide
http://forum.xda-developers.com/show....php?t=1626895
or use other toolkits!
Click to expand...
Click to collapse
Unfortunately I've tried both options you suggest, no luck. Flashing manually looks like its working, I get an "OK" on every image, including system.img. But even then phone boots up like nothing has happened.
samersh72, I promise, won't use toolkit. Doesn't see any profit in doing so, better to have full control the manual way.
Could it have something to do with permissions? That would be weird since ClockWork recovery has root and so does Odin, but who knows.
oskan.lindgren said:
Unfortunately I've tried both options you suggest, no luck. Flashing manually looks like its working, I get an "OK" on every image, including system.img. But even then phone boots up like nothing has happened.
samersh72, I promise, won't use toolkit. Doesn't see any profit in doing so, better to have full control the manual way.
Could it have something to do with permissions? That would be weird since ClockWork recovery has root and so does Odin, but who knows.
Click to expand...
Click to collapse
did it take too much time also when flashing system.img with fastboot command??
if nothing will change, it means that you must replace the emmc chip.
a little test here: lock the bootloader with fastboot command..... i guess it will never lock and it will still unlocked. nothing will stick on a died emmc
samersh72 said:
did it take too much time also when flashing system.img with fastboot command??
if nothing will change, it means that you must replace the emmc chip.
a little test here: lock the bootloader with fastboot command..... i guess it will never lock and it will still unlocked. nothing will stick on a died emmc
Click to expand...
Click to collapse
Yes, it took like 20 - 30 minutes to flash system.img with fastboot command. Will try to lock bootloader now and se what happends!
Is it possible to change just the emmc chip? I've googled a bit and it seems like it's soldered on like a bigger board with some other stuff?
oskan.lindgren said:
Yes, it took like 20 - 30 minutes to flash system.img with fastboot command. Will try to lock bootloader now and se what happends!
Is it possible to change just the emmc chip? I've googled a bit and it seems like it's soldered on like a bigger board with some other stuff?
Click to expand...
Click to collapse
yes, but some service center change the whole motherboard
you must take it to service center.
it will cost... it is not cheap
Hello People,
I have a samsung galaxy s4 mini GT-I9195, whenever i turn it on :
Image size too large!! W:1080, H:1920
display image fail
SECURE FAIL: KERNEL
I tryed few original roms , but none working.
I tryed this procedure from this theread : http://forum.xda-developers.com/showthread.php?t=2364980
and still not workin.
Here's what it shows on Odin Mode:
Product name: GT-I9195
Current Binary: Samsung Oficial
System Status: custom
Knox kernel Lock : 0*fffffffc
Knox warranty Void: 0*fffffffc
CSB-CONFIG-LSB: 0*30
Bootloader AP Swrev :2
Write Protection : Enable
but when i press volume up+home.. its not entering in recovery mode..
on the phone was instaled Cyanogen
Thanx!!
nik23 said:
Hello People,
I have a samsung galaxy s4 mini GT-I9195, whenever i turn it on :
Image size too large!! W:1080, H:1920
display image fail
SECURE FAIL: KERNEL
I tryed few original roms , but none working.
I tryed this procedure from this theread : http://forum.xda-developers.com/showthread.php?t=2364980
and still not workin.
Here's what it shows on Odin Mode:
Product name: GT-I9195
Current Binary: Samsung Oficial
System Status: custom
Knox kernel Lock : 0*fffffffc
Knox warranty Void: 0*fffffffc
CSB-CONFIG-LSB: 0*30
Bootloader AP Swrev :2
Write Protection : Enable
but when i press volume up+home.. its not entering in recovery mode..
on the phone was instaled Cyanogen
Thanx!!
Click to expand...
Click to collapse
The problem was resolved. i instaled few original roms, and it worked at last!
What a mess! :crying:
I had my S4 i9505 with ROM Movistar Spain (XEC) Android 5.0.1 and I need to install a Movistar or free Android 4.3 ROM to use Mirrorlink in a Toyota Auris car.
After a lot of tinkering with ROMs and bootloaders now the mobile stops at the logo screen showing "Samsung Galaxy S4 GT-I9505".
If I try to install any ROM from the Download mode with Odin it gives me the following error:
<ID: 0/004> Odin engine v (ID: 3.1207) ..
<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> NAND Write Start !!
<ID: 0/004> SingleDownload.
<ID: 0/004> sbl1.mbn
<ID: 0/004> sbl2.mbn
<ID: 0/004> sbl3.mbn
<ID: 0/004> rpm.mbn
<ID: 0/004> aboot.mbn
<ID: 0/004> FAIL! (Auth)
<ID: 0/004>
<ID: 0/004> Complete (Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Neither Kies nor dr.fone recognize the mobile, because they stay in "connecting ..."
As I can access the bootloader (Philz Touch 6.58.7) I have done all the wipes but when rebooting it never passes the logo screen.
In Download mode this appears:
ODIN MODE
PRODUCT NAME: GT-I95095
CURRENT BYNARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: ENABLE
eMMC BURST MODE: enabled
Any ideas? ¿Could be a KNOX problem?
Thank you! :good:
Papalapa said:
What a mess! :crying: I had my S4 i9505 with ROM Movistar Spain (XEC) Android 5.0.1 and I need to install a Movistar or free Android 4.3 ROM to use Mirrorlink in a Toyota Auris car...
Click to expand...
Click to collapse
I don't have this variant but, your best bet is to post this question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=2192886
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.