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
As many of you know, the WiFi on the official 4.3 flashable ROMS is blocked by the new bootloader. I'm not sure if this will fix it completely (I downloaded http://forum.xda-developers.com/showthread.php?t=1975560 the latest one from that, extracted and flashed each of those through Heimdall, but if the bootloader is the only problem, then you should be able to fix just that).
So once you have heimdall installed (cross-platform) and added to your path, run the following script:
heimdall flash --BOOTLOADER sboot.bin
^yes, it's case sensitive
Note: you can't use your OS to boot you into the bootloader. It's actually not the same as using the button combo to boot to the bootloader. Heimdall will not work if the text in the top left doesn't appear.
If you want to download from that url and extract, extract the .tar.md5 file, you'll see a few files, and then terminal, cd to wherever you extracted to and then run:
heimdall flash --TZSW tz.img --BOOT boot.img --CACHE cache.img --HIDDEN hidden.img --RADIO modem.bin --RECOVERY recovery.img --BOOTLOADER sboot.bin --SYSTEM system.img
Hi, last days, my S4 Mini were turned Off.
Phone don't react to AC adapter, and don't react for nothing...
PC recognized this phone as qhsusb_dload (Brick..),
So, i went to https://forum.xda-developers.com/showthread.php?t=2600869 , downloaded debrick.img from one of replies , and phone turned On ! When it turned on, screen looking like this:
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS..
COPY FROM T-FLASH..
BOOT RECOVERY..
WRITE 139008 sectors..
FLASH WRITE FAILURE
ddi : mmc_read failed
ODIN MODE
PRODUCT NAME : GT-I9195
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-Config-LSB: 0x30
BOOTLOADR AP SWAEV:2
WRITE PROTECTION: Enable
Click to expand...
Click to collapse
So its time for firmware. I downloaded 4,4,2 from server and tried to flash, but ODIN shows There is no PIT partition.
then I downloaded pit file ad trying to load it by odin but it's hanged out on <ID:0/014> SetupConnection..... and then :
<ID:0/014> Initialzation..
<ID:0/014> Set PIT file..
<ID:0/014> DO NOT TURN OFF TARGET!!
<ID:0/014> FAIL!
<ID:0/014>
<ID:0/014> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
and phone shows:
MMC: mmc_read fail
PIT FAIL : TOTAL SECTORS (0)
Click to expand...
Click to collapse
What now? Please help me! Sorry for my bad english..
you must change the emmc chip, I have the same problem!
ps: you have flashed the wrong debrick.img, this is for i9205!
hasky93 said:
you must change the emmc chip, I have the same problem!
ps: you have flashed the wrong debrick.img, this is for i9205!
Click to expand...
Click to collapse
Okay Thanks. i Think that new mainboard will be easier to apply, and price will be drawed. I Have mainobard for 20$