Bootloop, even odin or omap does nothing - Samsung Galaxy Nexus
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
Related
[Q] fastboot FAILED command too many links Help!
I just rebooted my Nexus and now it sits still at the Google logo. I'm in desperate need of help. I did install CWM and a custom ROM. When I try to boot in recovery the device locks up and I have to pull the battery. I have tried the Galaxy Nexus Toolkit, Fastboot commands to restore an stock image and do a factory reset. For example. Code: C:\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img sending 'recovery' (4760 KB)... OKAY [ 0.456s] writing 'recovery'... FAILED (status read failed (Too many links)) finished. total time: 0.551s I'm out of options here. Anyone can give me a helping hand? its 02:30 AM and I need my alarm to go off at 6:30. EDIT: I am also getting a Fastboot Command failed Read error -2147483647 in fastboot. Also getting this. Code: C:\android-sdk-windows\platform-tools>adb reboot-bootloader error: device not found C:\android-sdk-windows\platform-tools>fastboot devices 0146A541234C00B fastboot C:\android-sdk-windows\platform-tools>adb reboot-bootloader error: device not found
Am I the only one with this problem?
well, i'll try to help some. your second box shows you 'fastboot devices', but then 'adb reboot - no device' - adb and fastboot are two different programs and operate at different points. if fastboot is recognizing your phone, you should be able to push a recovery. if the one you are using is giving you errors, try a different version, or download it again (maybe its corrupt?) i dont know, but i hope that helps you get back on track. definitely read up through the stickies on fastboot use & adb use
DaMightyTom said: I just rebooted my Nexus and now it sits still at the Google logo. I'm in desperate need of help. I did install CWM and a custom ROM. When I try to boot in recovery the device locks up and I have to pull the battery. I have tried the Galaxy Nexus Toolkit, Fastboot commands to restore an stock image and do a factory reset. For example. Code: C:\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img sending 'recovery' (4760 KB)... OKAY [ 0.456s] writing 'recovery'... FAILED (status read failed (Too many links)) finished. total time: 0.551s I'm out of options here. Anyone can give me a helping hand? its 02:30 AM and I need my alarm to go off at 6:30. EDIT: I am also getting a Fastboot Command failed Read error -2147483647 in fastboot. Also getting this. Code: C:\android-sdk-windows\platform-tools>adb reboot-bootloader error: device not found C:\android-sdk-windows\platform-tools>fastboot devices 0146A541234C00B fastboot C:\android-sdk-windows\platform-tools>adb reboot-bootloader error: device not found Click to expand... Click to collapse it seems you flashed the wrong recovery. they are gms and lte specific. so go to the appropriate developer forum and get the right one. next, fastboot only works when you are in the bootloader screen. adb is for when the phone is on or in recovery mode. but, it looks like you don't have the right drivers for abd.. no matter, everything can be done in fastboot for now.
Flashed the wrong recovery? I dont think so, I get this error no matter what I do. I have tried flashing the recovery, flashing 3 different versions of the GSM stock firmware. flashing CMW recovery and manually flashing bootloader, radio from google stock firmware. Nothing works. Too many links and the phone freezes in bootloader mode.
When pulling the battery I get a faint burning smell inside the device? Could it be a hardware malfunction rather than a software?
I just installed ADB drivers on my laptop to no avail. Same problem. I can get into the bootloader, something It's frozen at start but sometimes I get contact and PDA recognises it, if I press the popup to connect Pda to the phone I get a Failed command inside the phone. After any fastboot command like recovery or flash the phone returns unknown command or too many links and freezes. Code: C:\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img sending 'recovery' (4760 KB)... OKAY [ 0.456s] writing 'recovery'... FAILED (status read failed (Too many links)) finished. total time: 0.521s C:\android-sdk-windows\platform-tools>fastboot devices ???????????? fastboot
I just tried booting the phone up and it was standing on the startup graphics for a LONG time. But then I got this message: Encryption unsuccessfull. Encryption was interupted and cant resume bla bla To move forward i have to press this "reset" button. Im trying but pressing wont do anything. Anyone have any ideas before I return the device?
have you tried flashing a whole system image instead of just a recovery image ? get images here http://forum.xda-developers.com/showthread.php?t=1366806
Code: C:\android-sdk-windows\platform-tools>fastboot flash bootloader bootloader-magur o-primekk15.img sending 'bootloader' (2308 KB)... OKAY [ 0.220s] writing 'bootloader'... FAILED (status read failed (Too many links)) finished. total time: 0.360s C:\android-sdk-windows\platform-tools>fastboot devices 0146A5470200C00B fastboot C:\android-sdk-windows\platform-tools>fastboot flash radio radio-maguro-i9250xxk k6.img sending 'radio' (12288 KB)... OKAY [ 1.170s] writing 'radio'... FAILED (status read failed (Too many links)) finished. total time: 1.857s C:\android-sdk-windows\platform-tools>fastboot -w update image-yakju-icl53f.zip archive does not contain 'boot.sig' archive does not contain 'recovery.sig' archive does not contain 'system.sig' -------------------------------------------- Bootloader Version...: PRIMEKK15 Baseband Version.....: I9250XXKK6 Serial Number........: 0146A5470200C00B -------------------------------------------- checking product... OKAY [ 0.010s] checking version-bootloader... OKAY [ -0.000s] checking version-baseband... OKAY [ 0.010s] sending 'boot' (4074 KB)... OKAY [ 0.390s] writing 'boot'... FAILED (status read failed (Too many links)) finished. total time: 0.460s C:\android-sdk-windows\platform-tools>
Try a different USB port or USB cable.
tried that multiple computers and different ports
have you tried putting it into download mode ( not bootloader ) and flashing via odin?
No not yet. How can i do that?
I have odin and the nexus in download mode. Now before I do anything, is there a nice neat guide how to install factory settings with everything?
yea i am sure there is if you search i have seen a few odin threads around. sorry to busy right now to hunt it down for you ( at work )
Okey so i found this. http://samsung.de/de/Privatkunden/M...nexus/GT-I9250TSADBT/detail.aspx?atab=support Original firmware for the nexus. Seems to be an Exe file with implemented odin or something. Anyways I ran it. It got stock on Write Nand or something. I googled it and someone suggested I would pull the battery and try it again. Now I got a phone --> Triangle --> computer once I put the battery in. I can't access download mode or bootloader mode but the computer recognises the phone once i plug it in. EDIT: Actually when I plug it in it spazzes out like something is plugging it in and plugging it out all the time. The device manager is flickering since its updating.
Plugging it in the computer then putting the batteri in seems to made Odin find it again. tried to run it. Code: <ID:0/003> Odin v.3 engine (ID:3).. <ID:0/003> Check Magic Code <ID:0/003> Odin3 One Click Download.. <ID:0/003> File analysis.. <ID:0/003> SetupConnection.. <ID:0/003> Initialzation.. <ID:0/003> Send lock information.. <ID:0/003> Get PIT for mapping.. <ID:0/003> Firmware update start.. <ID:0/003> recovery.img <ID:0/003> NAND Write Start!! It's stuck now.
what happens when you boot the phone ? can you get into bootloader? recovery ?
Goat_For_Sale said: what happens when you boot the phone ? can you get into bootloader? recovery ? Click to expand... Click to collapse No. recovery havent worked since the start of the problem. Only bootloader and download mode. Now I am stuck with the triangle. http://imageshack.us/photo/my-images/830/1000192x.jpg/ Found this picture its very similiar to the one I am having.
Update your BootLoader for 4.3
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
No MD5 file found error while flashing with TWRP !
Hello there...I have an issue with my htc m8...When I try to flash a firmware or a custom rom like Maximus HD rom..I always get that error : Failed : no md5 file found I have a rooted device with s-off and twrp recovery Any help ? Thanks
1. You cannot flash a firmware in TWRP recovery .. you need fastboot flash the firmware.zip in RUU mode 2. Disable md5 checking in TWRP so you won't have that md5 error when a zip has no md5
ckpv5 said: 1. You cannot flash a firmware in TWRP recovery .. you need fastboot flash the firmware.zip in RUU mode 2. Disable md5 checking in TWRP so you won't have that md5 error when a zip has no md5 Click to expand... Click to collapse So all I have to do is ticking the "Skip MD5 verification of backup files " option ? Is there any guide to how to flash unsigned firmware using fast boot in RUU mode ? Thanks ?
1. Yes 2. Lazy to rewrite thing all over again ... you can find it on many threads ... Here is what I wrote for different firmware but the basic is the same ... http://forum.xda-developers.com/showpost.php?p=64471713&postcount=10519
S4 Mini hard bricked, and Pit Error.
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$
I think that I bricked my Samsung S4
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.