easy .. but risky
while installing OS is almost completly without risk as I think, so recovery is my "last chance" to rescue phone if anything bad will happen ...Am I right ?
camera not working (Galaxy S III i9305 / flashed ClockworkMod+touch / Cyanogen 10.1.
- Thread starter marcint43
- Start date
easy .. but risky
while installing OS is almost completly without risk as I think, so recovery is my "last chance" to rescue phone if anything bad will happen ...Am I right ?
N
noppy22
Guest
easy .. but risky
Am I right ?
Well...not really, there is a small risk flashing anything, but changing recovery is no more risky. I always have a few .zip and .tar recoveries on my computer/sd card in case I need to change, but I usually use philz 6.48 .zip that you can change via your existing recovery(you just need to flash it, then reboot straight back to recovery to use it)
I choosed Wipe Data/Factory Restore
FLash Stock Kernel
Install Samsung Apps
and clicked "Flash" ...
sth was done and phone was rebooted to CWM Recovery with info:
ClockworkMod Recovery v6.0.4.7
Waiting for SD Card to mount (20s)
SD Card mounted ...
Verifing SD Card marker ...
SD Card marker not found ...
Error processing ROM Manager script. Please verify that you are performing the backup, restore, or ROM installation from ROM Manager v.4.4.0.0 or higher
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
I choosen Reboot system now ...
Cyaogenmod is back ... nothing changed ... :|
FLash Stock Kernel
Install Samsung Apps
and clicked "Flash" ...
sth was done and phone was rebooted to CWM Recovery with info:
ClockworkMod Recovery v6.0.4.7
Waiting for SD Card to mount (20s)
SD Card mounted ...
Verifing SD Card marker ...
SD Card marker not found ...
Error processing ROM Manager script. Please verify that you are performing the backup, restore, or ROM installation from ROM Manager v.4.4.0.0 or higher
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
I choosen Reboot system now ...
Cyaogenmod is back ... nothing changed ... :|
N
noppy22
Guest
When I am trying to start ROM Customizer ... this soft is stopped ... the same like DriveLink ...
this is really weird ...
I see that on internal sd there is file AGNi_reset_oc-uv_on_boot_failure.zip ...
seems that sth wrong has occured after flashing ...
bricked phone ? HEEELPPPP
sammobile
heimdall flash --BOOT boot.img --RECOVERY recovery.img --SYSTEM system.img --CACHE cache.img --HIDDEN hidden.img --RADIO modem.bin --BOOTLOADER sboot.bin --TZSW tz.img
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading BOOT
100%
BOOT upload successful
Uploading RECOVERY
100%
RECOVERY upload successful
Uploading SYSTEM
100%
SYSTEM upload successful
Uploading CACHE
100%
CACHE upload successful
Uploading HIDDEN
100%
HIDDEN upload successful
Uploading RADIO
100%
RADIO upload successful
Uploading BOOTLOADER
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: BOOTLOADER upload failed!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...
on the screen of phone:
ODIN MODE
PRODUCT NAME: GT-I9305
CUSTOM BINARY DOWNLOAD: Hes (1 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
Secure Download: Enabled
KNOW WARRANTY VOID: 1
AP SWREV: A3
SW REV. CHECK FAIL, DEVICE:3, BINARY:2
blue bar 100%
not restarted yet
sammobile
heimdall flash --BOOT boot.img --RECOVERY recovery.img --SYSTEM system.img --CACHE cache.img --HIDDEN hidden.img --RADIO modem.bin --BOOTLOADER sboot.bin --TZSW tz.img
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading BOOT
100%
BOOT upload successful
Uploading RECOVERY
100%
RECOVERY upload successful
Uploading SYSTEM
100%
SYSTEM upload successful
Uploading CACHE
100%
CACHE upload successful
Uploading HIDDEN
100%
HIDDEN upload successful
Uploading RADIO
100%
RADIO upload successful
Uploading BOOTLOADER
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: BOOTLOADER upload failed!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...
on the screen of phone:
ODIN MODE
PRODUCT NAME: GT-I9305
CUSTOM BINARY DOWNLOAD: Hes (1 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
Secure Download: Enabled
KNOW WARRANTY VOID: 1
AP SWREV: A3
SW REV. CHECK FAIL, DEVICE:3, BINARY:2
blue bar 100%
not restarted yet
when try to reflash:
$ heimdall flash --BOOT boot.img --RECOVERY recovery.img --SYSTEM system.img --CACHE cache.img --HIDDEN hidden.img --RADIO modem.bin --BOOTLOADER sboot.bin --TZSW tz.img
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
[timestamp] [threadID] facility level [function call] <message>
--------------------------------------------------------------------------------
[ 0.000000] [00001e24] libusbx: error [op_set_interface] setintf failed error -1 errno 110
ERROR: Setting up interface failed!
Releasing device interface...
$ heimdall flash --BOOT boot.img --RECOVERY recovery.img --SYSTEM system.img --CACHE cache.img --HIDDEN hidden.img --RADIO modem.bin --BOOTLOADER sboot.bin --TZSW tz.img
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
[timestamp] [threadID] facility level [function call] <message>
--------------------------------------------------------------------------------
[ 0.000000] [00001e24] libusbx: error [op_set_interface] setintf failed error -1 errno 110
ERROR: Setting up interface failed!
Releasing device interface...
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
i9305 (was: android 4.4.2) DriveLink works on Android 4.3 STOCK VERSION
YEAAAHHH ALL WORKS , DriveLinks too !! ))
It just needed go to download mode (volume down, home, power) and reinstall CWM
$ heimdall flash --RECOVERY recovery-clockwork-touch-6.0.4.7-i9305.img --no-reboot
after reboot Android 4.3 STOCK automaticaly has started to install
===
So, now - WORKING DriveLink with FULL MIRRORING CONFIGURATION - configuration:
- Android 4.3, based on Sammobile:
f1af5692d4c113edcd5911324ab781e6 *I9305XXUENH1_I9305TPLENH1_TPL.zip
- CWM as REcovery
- DriveLink app from:
http://www.colmoschinxtreme.com/android -> http://www.colmoschinxtreme.com/android/item/drivelink
Only main Drive Link.apk, without TMServerApp.apk because I dont have root yet... and now is midnight so tomorrow I will test if app is closed when "vehicle is in motion"
- because I was downgraded OS to previous version - KNOX flag equals 1
and one IMPORTANT THING: Finally I found that USB cable was corrupted ... damn chinesee **** ...
When I used origial samung cable Toyota has seen my phone, and DriveLink works perfectly
So... on previous version of CyanogenMod this probably has been working ... but there was only problem with F*****G CABLE !
==
one more important thing: In Toyota avensis you have to touch the engine power button to on to power radio onboard.
I dont know how to use "back" and "properties" touch button from phone so sometimes is important to get phone to hand and click sth... But normally Phone can be hidden in car's box and never touched.
Accidentaly I found how to enter to "pull down menus" ... you need to touch Cars display in right corner and WAIT for about 2 seconds, then horizontal bar will be displayed.. then swipe down as usual
===
sorry for uppercase in letters I am so excited
YEAAAHHH
ALL WORKS , DriveLinks too !! ))It just needed go to download mode (volume down, home, power) and reinstall CWM
$ heimdall flash --RECOVERY recovery-clockwork-touch-6.0.4.7-i9305.img --no-reboot
after reboot Android 4.3 STOCK automaticaly has started to install
===
So, now - WORKING DriveLink with FULL MIRRORING CONFIGURATION - configuration:
- Android 4.3, based on Sammobile:
f1af5692d4c113edcd5911324ab781e6 *I9305XXUENH1_I9305TPLENH1_TPL.zip
- CWM as REcovery
- DriveLink app from:
http://www.colmoschinxtreme.com/android -> http://www.colmoschinxtreme.com/android/item/drivelink
Only main Drive Link.apk, without TMServerApp.apk because I dont have root yet... and now is midnight so tomorrow I will test if app is closed when "vehicle is in motion"
- because I was downgraded OS to previous version - KNOX flag equals 1
and one IMPORTANT THING: Finally I found that USB cable was corrupted ... damn chinesee **** ...
When I used origial samung cable Toyota has seen my phone, and DriveLink works perfectly
So... on previous version of CyanogenMod this probably has been working ... but there was only problem with F*****G CABLE !
==
one more important thing: In Toyota avensis you have to touch the engine power button to on to power radio onboard.
I dont know how to use "back" and "properties" touch button from phone so sometimes is important to get phone to hand and click sth... But normally Phone can be hidden in car's box and never touched.
Accidentaly I found how to enter to "pull down menus" ... you need to touch Cars display in right corner and WAIT for about 2 seconds, then horizontal bar will be displayed.. then swipe down as usual
===
sorry for uppercase in letters
I am so excited whoow one ... little FUNNY .... when I go to CWM and choosen "Reboot" it asked me:
Root access is missing. Root device ? THIS CAN NOT BE UNDONE.
NO
YES - Root device (/system/xbin/su)
unfortunately after "YES" there is no difference:
shell@m3:/ $ su -
/system/bin/sh: su: not found
127|shell@m3:/ $ sudo su
/system/bin/sh: sudo: not found
one ... little FUNNY .... when I go to CWM and choosen "Reboot" it asked me:Root access is missing. Root device ? THIS CAN NOT BE UNDONE.
NO
YES - Root device (/system/xbin/su)
unfortunately after "YES" there is no difference:
shell@m3:/ $ su -
/system/bin/sh: su: not found
127|shell@m3:/ $ sudo su
/system/bin/sh: sudo: not found
N
noppy22
Guest
whoow
Root access is missing. Root device ? THIS CAN NOT BE UNDONE.
NO
YES - Root device (/system/xbin/su)
unfortunately after "YES" there is no difference:
shell@m3:/ $ su -
/system/bin/sh: su: not found
127|shell@m3:/ $ sudo su
/system/bin/sh: sudo: not found
Try installing supersu from the store
tried, but is crashing ...
But on another side, I have more difficult problem...When my car is in motion, DriveLink is closed. I read that I have to do sth with cables to TOyota Touch 2 & Go ...
Probably GrouND cable "HandBrake",
http://www.gt86ownersclub.co.uk/for...-app-potential_topic3578_post76734.html#76734
but also probably cut SPD (SPeeD cable, vehicle in motion signal)...
I dont' know yet.
My car is brand new (1 year)...so I have problem with car warranty
Similar threads
