Hey guys,
I haven't found a suitable help for my problem - in short words:
using on a rooted device cm for a long time - today updated through rom-manager!
from that on I wasn't able to reboot it - don't know if it updated with latest nightly or not...
I'm not able to got into recovery - after yellow triangle it stays black
Tried now to flash this:
codeworkx's Kernel with the ClockworkMod Recovery 5.5.0.4
with heimdall on a mac - followed all the steps correctly I think:
while I'm trying to flash through heimdall I get this message:
Martins-MacBook-Proownloads metze$ heimdall flash --kernel zImage
Heimdall v1.3.2, Copyright (c) 2010-2012, 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...
Failed to detect compatible download-mode device.
Martins-MacBook-Proownloads metze$
any ideas what could be wrong or what I can do?
thx a lot for your help!
metze.b said:
Hey guys,
I haven't found a suitable help for my problem - in short words:
using on a rooted device cm for a long time - today updated through rom-manager!
from that on I wasn't able to reboot it - don't know if it updated with latest nightly or not...
I'm not able to got into recovery - after yellow triangle it stays black
Tried now to flash this:
codeworkx's Kernel with the ClockworkMod Recovery 5.5.0.4
with heimdall on a mac - followed all the steps correctly I think:
while I'm trying to flash through heimdall I get this message:
Martins-MacBook-Proownloads metze$ heimdall flash --kernel zImage
Heimdall v1.3.2, Copyright (c) 2010-2012, 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...
Failed to detect compatible download-mode device.
Martins-MacBook-Proownloads metze$
any ideas what could be wrong or what I can do?
thx a lot for your help!
Click to expand...
Click to collapse
went back to the office and used win! ok now! thx anyway!
I'd normally post this as a reply to Chainfires [2012.10.26] CF-Auto-Root v1.0 [GT-I930x/T/N][SHV-E210*][SHW-M440S] thread in the Galaxy S III Original Android Development subforum, but without 10 posts, I can't post to a development thread, so this is the best I can do for now...
I've a 1 week old SGS3 International (GT-i9300) that has upgraded to JB OTA, now running JB 4.1.1, baseband I9300XXDLID, Build number JRO03C.I9300XXDLJ4. I am unable to root my phone using Chainfires recommended method, as described in that thread. I see the software download to the phone, and then the phone reboots into CWM, and then sits at the CWM menu. Rebooting from CWM menus results in normal start of the phone, and everything working (apparently) normally. Update counter is incremented, and my phone is now detected as modified. However, root is not available, and there appears to be no SU binary on the phone.
Attempting to install SuperSU from the market doesn't work. Running Root Checker from the market confirms that the phone is not rooted.
I appear to be one of several people for whom this method is now failing (though the use of Linux rather than Windows makes me slightly unusual) and wanted to (a) report this to Chainfire, and (b) get some help on what to try next to make this work, as I really want to get root on my handset.
For information, the method I used:
I run Ubuntu, and have no access to a Windows PC, so I made the updates with Heimdall v1.3.1, which as others have noted (around post 120ish) does work and I also double-checked that that specific version could talk to the phone correctly (detect and print-pir both work as expected).
I took the latest CF Auto Root for my phone hardware from Chainfires site (at autoroot [dot] chainfire [dot] eu), and extracted the recovery and cache image files. switched the phone to download (PWR, Vol Down, Home) then Vol Up, plugged in the USB cable and ran "sudo heimdall flash --recovery recovery.img --cache cache.img", resulting in:
Code:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
PIT file download sucessful
Uploading RECOVERY
100%
RECOVERY upload successful
Uploading CACHE
100%
CACHE upload successful
Ending session...
Rebooting device...
Re-attaching kernel driver...
During code download, progress bars move on the phone as expected, and it then reboots into CWM, where it sits waiting for manual input. Rebooting the phone from CWM does not seem to result in root, even through the flash counter has been incremented and the phone is detected as modified.
I would appreciate some help, or a kindly moderator moving this to the right forum/thread and allowing me to continue the conversation over there.
Thanks
Richard
So, I have this issue since yesterday.
Casual will not connect to my phone.
I had Kies installed yesterday, but Kies did not recognize my phone also.
I had drivers downloaded directly from Samsung, and reinstalled them 3 times. Yesterday, for a brief moment, I managed to have Casual connected but apparently missed a step and am still not unlocked.
Steps taken:
antivirus and firewall disabled
tried several different usb cables. Including brand new one
tried ports available
reinstalled drivers
had bootstrap launched or not
Debugging enabled
Does not matter - phone does not connect to Casual. Also, Casual hangs and refuses to shut down, I have to force close it. I have 2 versions, both with same results. Antivirus, btw, treats Casual as a trojan.
Suggestions? Phone is rooted as of yesterday. I get all kinds of weird messages - device Id can not be found (on PC). Phone tells me that a program is missing on PC for file transfer, as in Service Pack 3, or Windows Media Player. Tired. I am running Windows 7. Had PC and phone rebooted several times. Same result. Odin connects to phone just fine.
Oh, and in addition. After about 5 minuters, Casual will connect to the phone, but pressing DoIt button produces no results.
Lat question: Casual says "Put your device into ADB mode". ????????
Try the last post. Maybe it will work. Also you really could have just used your other thread without a new one.
http://forum.xda-developers.com/showthread.php?p=38959999
Sent from my SCH-I605 using Tapatalk 2
I know. But I was always told that you get better results by separating issues into threads. Otherwise, it all gets muddied.
Btw, Casual is working. It's Pushing SuperSU app now. I am past base install via Odin. Problem is - it is moving not even at snail speed, it is moving at a bit per minute speed. Must be something with USB ports. I should have gone for rear USB ports, they are directly in mother board. Can't touch it now, don't want to f something up. I had to do it once on my Droid Charge.
Pushing Exynos Abuse now. I reckon, I'll get there by midnight, ha-ha.
Well I would have helped in either thread. In sure you know but always use usb in back, but at least it's working
Sent from my SCH-I605 using Tapatalk 2
I know. Late now. What threw me off was that I had it all going yesterday off front ports. Now I am stuck, no point in messing it up now. It's pushing something...
Last question. Backatcha goes under bootloader in Odin, not under PDA, right?
ukrkoz said:
Last question. Backatcha goes under bootloader in Odin, not under PDA, right?
Click to expand...
Click to collapse
If that's what casual said. I've been unlocked since before the ota so I'm not sure.
Sent from my SCH-I605 using Tapatalk 2
kintwofan said:
If that's what casual said. I've been unlocked since before the ota so I'm not sure.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
OK. That's what I was told by a good Samaritan. About 50% load done. Setting permissions.. I'll get there eventually. Thanks, kintwo..
ukrkoz said:
OK. That's what I was told by a good Samaritan. About 50% load done. Setting permissions.. I'll get there eventually. Thanks, kintwo..
Click to expand...
Click to collapse
Not a problem my man
Sent from my SCH-I605 using Tapatalk 2
It's done. 2 hrs.
ADB MODE?
a member asked earlier about CASUAL, and when it asks you to put phone in ADB Mode... no one addressed it and I need to know as well. I cant get CASUAL to notice the phone is connected. Installed the SDK, the drivers there, tried installing the drivers from samsung, no luck. Nothing is working. Yes the phone is in set to USB Debugging. Tried every USB on this pc.
cadgrad2010 said:
a member asked earlier about CASUAL, and when it asks you to put phone in ADB Mode... no one addressed it and I need to know as well. I cant get CASUAL to notice the phone is connected. Installed the SDK, the drivers there, tried installing the drivers from samsung, no luck. Nothing is working. Yes the phone is in set to USB Debugging. Tried every USB on this pc.
Click to expand...
Click to collapse
Why did you download the SDK?
As for drivers CASUAL installs its own so you shouldn't have to worry about that.
Is your antivirus off?
What is your OS?
Is Java the latest edition?
Which version of CASUAL are you using? Try one of the nightlies from Adams goo.im page.
Have you tried different USB cords?
Have you tried a different PC?
Sent from my SCH-I605 using XDA Premium HD app
Why did you download the SDK? Downloaded it to make sure I had drivers correct. All drivers are updated as of now. Still a no go though. Disconnected error. I restarted everything over here including my grandmas pacemaker
As for drivers CASUAL installs its own so you shouldn't have to worry about that.
Is your antivirus off? YES
What is your OS? Windows 7 Home Premium
Is Java the latest edition? Yes, Fresh Install
Which version of CASUAL are you using? Try one of the nightlies from Adams goo.im page. CASUAL R701 Nightly
Have you tried different USB cords? Yes, went out and bought another one just to make sure, Currently using the stock.
Have you tried a different PC? Looking for another PC atm.
Sent from my SCH-I605 using XDA Premium HD app[/QUOTE]
Soft Bricked?
So went to a new pc, everything seemed to go well..... now phone is stuck in bootloop. Heres the log:
Created Folder:C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\
Picking Jar File:/C:/Users/Michael/Desktop/NDROID/CASUAL-BackAtchaVerizon-Revision311b.jar
Found Windows Computer
Attempting to write C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\Elevate.exe
File verified.
Attempting to write C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\adb.exe
File verified.
Attempting to write C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\AdbWinApi.dll
File verified.
Attempting to write C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\AdbWinUsbApi.dll
File verified.
sleeping for Windows ADB start
Found: WindowsLinux Galaxy Note 2 Jailbreak
Attempting to write C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\-adb_usb.ini
File verified.
###executing: C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\adb.exe###
Control Change requested but lock is set.
OMFGWOOT GUI running!
This is a tool which will root, unlock, and install a custom recovery on a Verizon Galaxy Note 2.
Searching for scripts
Updating Scripts for UI
From Resource: true
--WindowsLinux Galaxy Note 2 Jailbreak--
This is a tool which will root, unlock, and install a custom recovery on a Verizon Galaxy Note 2. Put your device into ADB mode. Credit for this exploit goes to Lee Harrison
Exiting comboBoxUpdate()
Extracting archive....
Unzipping Superuser.apk
Control Change requested but lock is set.
Unzipping boot.img
Unzipping busybox
unknown
Device List:List of devices attached
Unzipping dependentinstaller.sh
Unzipping exploit
Unzipping exynos-abuse
Unzipping recoverThis
Unzipping rootGN.sh
Unzipping su
Unzipping swagBoot
Unzipping viewmem
Controls Enabled status: true
StartButtonActionPerformed() Script Activated
Script known as WindowsLinux Galaxy Note 2 Jailbreak is running
Controls Enabled status: false
Script WindowsLinux Galaxy Note 2 Jailbreak returned #0WindowsLinux Galaxy Note 2 Jailbreak
Selected resourceWindowsLinux Galaxy Note 2 Jailbreak
Lines in Script 75
Executing Scripted [email protected]
CASUAL has initiated a multithreaded execution environment
Script WindowsLinux Galaxy Note 2 Jailbreak returned #0WindowsLinux Galaxy Note 2 Jailbreak
/SCRIPTS/WindowsLinux Galaxy Note 2 Jailbreak not found in repository.
Reading [email protected]
new command: $MAC $HALT $ECHO This version of CASUAL cannot support mac
new command: $USERCANCELOPTION Are you sure?, This is your only warning.\n You will be Unlocked and Rooted. Your device will\n reboot once and then again into Odin mode. You\n will then flash the Suck It Verizon Odin Bootloader\n package.
SCRIPT COMMAND:$USERCANCELOPTION Are you sure?, This is your only warning.\n You will be Unlocked and Rooted. Your device will\n reboot once and then again into Odin mode. You\n will then flash the Suck It Verizon Odin Bootloader\n package.
COMMAND processed - C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\adb.exe Are you sure?, This is your only warning.
You will be Unlocked and Rooted. Your device will
reboot once and then again into Odin mode. You
will then flash the Suck It Verizon Odin Bootloader
package.
new command: $ECHO Rebooting into download mode
SCRIPT COMMAND:$ECHO Rebooting into download mode
Received ECHO command$ECHO Rebooting into download mode
Rebooting into download mode
new command:
new command:
new command:
new command: $ADB reboot download
SCRIPT COMMAND:$ADB reboot download
sending
###executing: C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\adb.exe###
return from ADB:error: device not found
new command: $HEIMDALL flash --8 "$ZIPFILEboot.img"
SCRIPT COMMAND:$HEIMDALL flash --8 "$ZIPFILEboot.img"
Expanded $ZIPFILE: $HEIMDALL flash --8 "C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\WindowsLinux Galaxy Note 2 Jailbreak\boot.img"
Attempting to write C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\libusb-1.0.dll
File verified.
Attempting to write C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\heimdall.exe
File verified.
detected!
###executing real-time command: C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\heimdall.exe###
Waiting for Downoad Mode device.Heimdall v1.4 RC2
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
--------LINK REMOVED------
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:
-LINK REMOVED-----
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Protocol initialisation successful.
Beginning session...
This device may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading BOOT
0%
19%
38%
57%
76%
95%
100%Ending session...
Releasing device interface...
Heimdall v1.4 RC2
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
--link removed---
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:
----link removed---
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Protocol initialisation successful.
Beginning session...
This device may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading BOOT
0%19%38%57%76%95%100%Ending session...
Releasing device interface...
ERROR: Failed to confirm end of file transfer sequence!ERROR: BOOT upload failed!ERROR: Failed to send end session packet!
new command:
new command:
new command: $ECHO Your device should be rebooting into Android now.
SCRIPT COMMAND:$ECHO Your device should be rebooting into Android now.
Received ECHO command$ECHO Your device should be rebooting into Android now.
Your device should be rebooting into Android now.
new command: $ADB wait-for-device
SCRIPT COMMAND:$ADB wait-for-device
sending
###executing: C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\adb.exe###
shangrila500 said:
Why did you download the SDK?
As for drivers CASUAL installs its own so you shouldn't have to worry about that.
Is your antivirus off?
What is your OS?
Is Java the latest edition?
Which version of CASUAL are you using? Try one of the nightlies from Adams goo.im page.
Have you tried different USB cords?
Have you tried a different PC?
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
cadgrad2010 said:
So went to a new pc, everything seemed to go well..... now phone is stuck in bootloop. Heres the log:
Created Folder:C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\
Picking Jar File:/C:/Users/Michael/Desktop/NDROID/CASUAL-BackAtchaVerizon-Revision311b.jar
Found Windows Computer
Attempting to write C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\Elevate.exe
File verified.
Attempting to write C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\adb.exe
File verified.
Attempting to write C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\AdbWinApi.dll
File verified.
Attempting to write C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\AdbWinUsbApi.dll
File verified.
sleeping for Windows ADB start
Found: WindowsLinux Galaxy Note 2 Jailbreak
Attempting to write C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\-adb_usb.ini
File verified.
###executing: C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\adb.exe###
Control Change requested but lock is set.
OMFGWOOT GUI running!
This is a tool which will root, unlock, and install a custom recovery on a Verizon Galaxy Note 2.
Searching for scripts
Updating Scripts for UI
From Resource: true
--WindowsLinux Galaxy Note 2 Jailbreak--
This is a tool which will root, unlock, and install a custom recovery on a Verizon Galaxy Note 2. Put your device into ADB mode. Credit for this exploit goes to Lee Harrison
Exiting comboBoxUpdate()
Extracting archive....
Unzipping Superuser.apk
Control Change requested but lock is set.
Unzipping boot.img
Unzipping busybox
unknown
Device List:List of devices attached
Unzipping dependentinstaller.sh
Unzipping exploit
Unzipping exynos-abuse
Unzipping recoverThis
Unzipping rootGN.sh
Unzipping su
Unzipping swagBoot
Unzipping viewmem
Controls Enabled status: true
StartButtonActionPerformed() Script Activated
Script known as WindowsLinux Galaxy Note 2 Jailbreak is running
Controls Enabled status: false
Script WindowsLinux Galaxy Note 2 Jailbreak returned #0WindowsLinux Galaxy Note 2 Jailbreak
Selected resourceWindowsLinux Galaxy Note 2 Jailbreak
Lines in Script 75
Executing Scripted [email protected]
CASUAL has initiated a multithreaded execution environment
Script WindowsLinux Galaxy Note 2 Jailbreak returned #0WindowsLinux Galaxy Note 2 Jailbreak
/SCRIPTS/WindowsLinux Galaxy Note 2 Jailbreak not found in repository.
Reading [email protected]
new command: $MAC $HALT $ECHO This version of CASUAL cannot support mac
new command: $USERCANCELOPTION Are you sure?, This is your only warning.\n You will be Unlocked and Rooted. Your device will\n reboot once and then again into Odin mode. You\n will then flash the Suck It Verizon Odin Bootloader\n package.
SCRIPT COMMAND:$USERCANCELOPTION Are you sure?, This is your only warning.\n You will be Unlocked and Rooted. Your device will\n reboot once and then again into Odin mode. You\n will then flash the Suck It Verizon Odin Bootloader\n package.
COMMAND processed - C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\adb.exe Are you sure?, This is your only warning.
You will be Unlocked and Rooted. Your device will
reboot once and then again into Odin mode. You
will then flash the Suck It Verizon Odin Bootloader
package.
new command: $ECHO Rebooting into download mode
SCRIPT COMMAND:$ECHO Rebooting into download mode
Received ECHO command$ECHO Rebooting into download mode
Rebooting into download mode
new command:
new command:
new command:
new command: $ADB reboot download
SCRIPT COMMAND:$ADB reboot download
sending
###executing: C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\adb.exe###
return from ADB:error: device not found
new command: $HEIMDALL flash --8 "$ZIPFILEboot.img"
SCRIPT COMMAND:$HEIMDALL flash --8 "$ZIPFILEboot.img"
Expanded $ZIPFILE: $HEIMDALL flash --8 "C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\WindowsLinux Galaxy Note 2 Jailbreak\boot.img"
Attempting to write C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\libusb-1.0.dll
File verified.
Attempting to write C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\heimdall.exe
File verified.
detected!
###executing real-time command: C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\heimdall.exe###
Waiting for Downoad Mode device.Heimdall v1.4 RC2
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
--------LINK REMOVED------
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:
-LINK REMOVED-----
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Protocol initialisation successful.
Beginning session...
This device may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading BOOT
0%
19%
38%
57%
76%
95%
100%Ending session...
Releasing device interface...
Heimdall v1.4 RC2
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
--link removed---
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:
----link removed---
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Protocol initialisation successful.
Beginning session...
This device may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading BOOT
0%19%38%57%76%95%100%Ending session...
Releasing device interface...
ERROR: Failed to confirm end of file transfer sequence!ERROR: BOOT upload failed!ERROR: Failed to send end session packet!
new command:
new command:
new command: $ECHO Your device should be rebooting into Android now.
SCRIPT COMMAND:$ECHO Your device should be rebooting into Android now.
Received ECHO command$ECHO Your device should be rebooting into Android now.
Your device should be rebooting into Android now.
new command: $ADB wait-for-device
SCRIPT COMMAND:$ADB wait-for-device
sending
###executing: C:\Users\Michael\AppData\Local\Temp\MichaelTEMPCASUALAA41538C\adb.exe###
Click to expand...
Click to collapse
Run Casual again, that seems to fix it for a lot of people. Some people run it as many as 5 times and then everything's gravy.
Sent from my SCH-I605 using XDA Premium HD app
((SOLVED))
((SOLVED))
I figured the partition got screwed up as CASUAL wouldn't run. I ran just the stock .pit using Odin3 v3.07 to clear up the issues and restarted back at a rooted stock. Flashing a CWM now as preferred Recovery.
......aannndd now I get the Verizon Triangle, telling me that I need to take my device in to a center... smh
shangrila500 said:
Run Casual again, that seems to fix it for a lot of people. Some people run it as many as 5 times and then everything's gravy.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
cadgrad2010 said:
((SOLVED))
I figured the partition got screwed up as CASUAL wouldn't run. I ran just the stock .pit using Odin3 v3.07 to clear up the issues and restarted back at a rooted stock. Flashing a CWM now as preferred Recovery.
......aannndd now I get the Verizon Triangle, telling me that I need to take my device in to a center... smh
Click to expand...
Click to collapse
Be careful with CWM, there seem to be a lot of issues with it on our phone because it isn't updated very often. TWRP is the most stable so if you end up having issues just flash the latest zip from here:
http://goo.im/devs/OpenRecovery/t0ltevzw/
Or use Goo Manager to install it.
Sent from my SCH-I605 using XDA Premium HD app
Might need to start over from stock
cadgrad2010 said:
((SOLVED))
I figured the partition got screwed up as CASUAL wouldn't run. I ran just the stock .pit using Odin3 v3.07 to clear up the issues and restarted back at a rooted stock. Flashing a CWM now as preferred Recovery.
......aannndd now I get the Verizon Triangle, telling me that I need to take my device in to a center... smh
Click to expand...
Click to collapse
Most people in this situation have to flash back to stock using Odin. They flash Root66 or the alternate restore. I suggest flashing alternate restore, doing the OTA and then run Casual again.
Aaaallll righty. So im following a few different guides floating arround because it seems to be not a common thing for Ubuntu (12.04) users to want to flash roms onto their S4's.
Here's the main guide i'm following : http://forum.xda-developers.com/showthread.php?t=2290798
Turns out Odin doesn't communicate properly on Ubuntu, for some reason. It wont ever show me a Com port for connection. So it looks like Heimdall is my only option to get the first hook onto this beast of a phone. I'm currently stuck on step 2 of the guide noted above where it has me flash the VRUAMD2 kernel to get hook.
Code:
~$ heimdall detect
Device Detected
~$ sudo heimdall flash --kernel SCH-I545_MD2_423399_Kernel.tar.md5
...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
ERROR: Failed to initialise protocol!
This is my I/O for the current try, can anyone help? I've done my searching but there's nothing that is a direct match to what I want / need, which is to flash this damn MD2 Kernel, and get on with the mod. If anyone knows of a cleaner way to do these things, I'd like to know as well.
BTW: I know this isn't QUITE the right forum, but account permissions and what not prevent me from posting directly to the guide, # of posts and what not.
Hi All, New to this forum and have not found a resolve reading the threads so if someone could correct me that would be awsome.
I am trying to un-hard brick our samsung galaxy player 5.0 intl. It attempted to boot with a flat battery along time ago and has been a brick since. i have periodically kept it charged in case one day i find a resolve.
I have been attempting to use Unbrickable Ressurector but cannot even get it to load.
Initial process:
I have installed ubuntu on a spare laptop.
Installed Java through command line and verified the install.
Downloaded Unbrickable Ressurector from: (github) downloaded as a zip file. 'hummingbird-hibl-master.zip'
changed the zip file permissions to allow executable.
Right clicked an run with Java. But nothing happens. A little bit of hard drive noise but nothing comes up.
In the threads there is mention of running the .jar file but there is no .jar file in this package. I have unzipped and searched the folders to no avail.
I have even tried renaming the zip file to .jar which yeilds the same result as above.
I think it may be that i'm simply stupid or am i missing something?
Any help greatly appreciated.
I have just tried installing java 6 instead of java 8 in case there was a compatibility issue. Set default application to Java 6 runtime. Icon pops up in side bar after double click on 'hummingbird-hibl-master.zip'
then after 14 seconds icon disappears.
Not sure what else to try. I must be missing something obvious?
SymondoR said:
Hi All, New to this forum and have not found a resolve reading the threads so if someone could correct me that would be awsome.
I am trying to un-hard brick our samsung galaxy player 5.0 intl. It attempted to boot with a flat battery along time ago and has been a brick since. i have periodically kept it charged in case one day i find a resolve.
I have been attempting to use Unbrickable Ressurector but cannot even get it to load.
Initial process:
I have installed ubuntu on a spare laptop.
Installed Java through command line and verified the install.
Downloaded Unbrickable Ressurector from: (github) downloaded as a zip file. 'hummingbird-hibl-master.zip'
changed the zip file permissions to allow executable.
Right clicked an run with Java. But nothing happens. A little bit of hard drive noise but nothing comes up.
In the threads there is mention of running the .jar file but there is no .jar file in this package. I have unzipped and searched the folders to no avail.
I have even tried renaming the zip file to .jar which yeilds the same result as above.
I think it may be that i'm simply stupid or am i missing something?
Any help greatly appreciated.
I have just tried installing java 6 instead of java 8 in case there was a compatibility issue. Set default application to Java 6 runtime. Icon pops up in side bar after double click on 'hummingbird-hibl-master.zip'
then after 14 seconds icon disappears.
Not sure what else to try. I must be missing something obvious?
Click to expand...
Click to collapse
Did you miss something? Yes, You missed the date on the OP which was DEC 2011!. The links are out of date and so are the instructions.
1. In 2011 I think maybe ubuntu 11.04/12.04 was current. So you might have trouble getting 14.04 or 16.04 to work.
2. The link for the download of Unbrickable Resurrector is not right. You are looking for a file called "UnBrickableResurrectorR36.jar" which is apparently been expunged from the internet. The current link, that is redirected to github.com, leads to the source code that will "compile" UnBrickableResurrectorR40.jar"( or whatever the lasted version was). So unless you've got some java 6 skills...
EDIT: I managed to find 1 copy of the file here:
https://www.4shared.com/file/1Gx6ZSXjei/UnBrickableResurrectorR40.html
Thanks meticulus for taking the time to reply. That got me out of a sticking point. Greatly appreciated. I know i'm trying to revive old tech but i also don't like being wasteful by just throwing it away. I hope to revive it so my daughter can use it as a ipod alternative. Here's hoping.
Hopefully i don't need any further help and this thread will help any other late comers to fixing the old galaxy player 5.0.
Thanks again.
Hi Meticulus. Progress update: Unbrickable Resurrector R40 now functional.
Connect SGP 5.0 intl.
Device recognised.
S5PC110 Detected.
Clicked : Perform Resurrection - Download Mode
Begin Resurrection Sequence
Requesting Permission to access device
Please wait......Uploading...
This is far as the process goes. Device does not go into download mode. Could i be missing something simple again?
SymondoR said:
Hi Meticulus. Progress update: Unbrickable Resurrector R40 now functional.
Connect SGP 5.0 intl.
Device recognised.
S5PC110 Detected.
Clicked : Perform Resurrection - Download Mode
Begin Resurrection Sequence
Requesting Permission to access device
Please wait......Uploading...
This is far as the process goes. Device does not go into download mode. Could i be missing something simple again?
Click to expand...
Click to collapse
1. It's been quite awhile since I used this but I believe that I used it with ubuntu 12.04 LTS. So first make sure you use that version.
2. Make sure you are NOT using virtualization software such as virtualbox or vmware. Either use a thumbdrive, dualboot, or just install ubuntu natively.
3. You man need to set permission on the USB device in udev. Sort of like this: http://ptspts.blogspot.co.il/2011/10/how-to-fix-adb-no-permissions-error-on.html
Use lsusb to find the exact IdVendor
4. Launch the file in the terminal like this: java -jar UnbrickableRessurectorR40.jar . This may* give you more output to tell what is going on.
Hi Again Meticulus. thanks for you instruction. I have managed to make some more headway from your help.
I performed a new native install of ubuntu 12.04 LTS and Java 6
Now Unbrickable Ressurector appears to work. It recognises the device and after password prompt brings up the now in download mode screen on the GUI window. Although the samsung player screen stays black.
I have now also installed Heimdall Frontend in ubuntu and in the process of learning how to use it and acquiring the correct pit file and firmware. It appears to recognise the player at this stage.
Just to refresh it is a Samsung Galaxy Player 5.0 International 16GB. Made in Korea.
I have pit file: GB70-GalaxyPlayer-16gb.pit
also G70intl.pit
I am thinking the first is a safer bet.
Firmware: G70XXKPL_CL1105219_REV01_user_low_ship_HOME.tar.md5
and: CODE_GB70KRKPG_CL762569_REV01_user_low_ship_HOME.tar
Although heimdall expects tar.gz file extensions. so i'm doing something wrong again.
I'm going to sleep on it and re approach in the morning. (I'm on the other side of the planet in good old New Zealand)
If you have any further advise to offer on correct firmware for this device any help is most appreciated.
SymondoR said:
Hi Again Meticulus. thanks for you instruction. I have managed to make some more headway from your help.
I performed a new native install of ubuntu 12.04 LTS and Java 6
Now Unbrickable Ressurector appears to work. It recognises the device and after password prompt brings up the now in download mode screen on the GUI window. Although the samsung player screen stays black.
I have now also installed Heimdall Frontend in ubuntu and in the process of learning how to use it and acquiring the correct pit file and firmware. It appears to recognise the player at this stage.
Just to refresh it is a Samsung Galaxy Player 5.0 International 16GB. Made in Korea.
I have pit file: GB70-GalaxyPlayer-16gb.pit
also G70intl.pit
I am thinking the first is a safer bet.
Firmware: G70XXKPL_CL1105219_REV01_user_low_ship_HOME.tar.md5
and: CODE_GB70KRKPG_CL762569_REV01_user_low_ship_HOME.tar
Although heimdall expects tar.gz file extensions. so i'm doing something wrong again.
I'm going to sleep on it and re approach in the morning. (I'm on the other side of the planet in good old New Zealand)
If you have any further advise to offer on correct firmware for this device any help is most appreciated.
Click to expand...
Click to collapse
".tar.md5" or ".tar" file must be flashed with Odin in Windows but those files are archives that can be opened via the Archive Manager in Ubuntu and the files extracted. As I said it's been awhile and I'm just talking from memory so do your homework but, basically each file in the archive is a raw dump of the partition. So system.img is the system partition, cache is cache and so on (zImage is kernel) and can be flash via heimdall. I am not very familiar with heimdall front end but from the Terminal, the command is something like:
"heimdall flash --system system.img" ( <---real iffy on exact syntax, something close to that.)
DO NOT FLASH PIT FILES!!! ( I have bricked my device many times and have never had to do this and you shouldn't do it unless you are sure that you have muffed up your partition table!)
Odin is available here and the drivers for windows too but the last time I used them Windows 7 was the thing so...
Techically if you can use Heimdall or Odin with any success, you are already in "Download Mode" and you do not need the Resurrector.
The Terminal command "heimdall --print-pit is a good test. If it can connect to the device and print the pit file with out error then Download mode is working and you can flash a stock ROM with ODIN and as long as it's the right one, your golden...
Hi Meticulus, Here's a quick result of a pit print:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to receive PIT file size!
ERROR: Failed to download PIT file!
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
So I may have a bigger problem. Would that indicate a muffed partition? from what i have read elsewhere i may have a hardware failure which means RIP samsung player.
What originally bricked the device was an attempted boot with a dead flat battery. the device has never had any custom firmware flashed. Purely stock.
Will do some more research in the meantime.
SymondoR said:
Hi Meticulus, Here's a quick result of a pit print:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to receive PIT file size!
ERROR: Failed to download PIT file!
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
So I may have a bigger problem. Would that indicate a muffed partition? from what i have read elsewhere i may have a hardware failure which means RIP samsung player.
What originally bricked the device was an attempted boot with a dead flat battery. the device has never had any custom firmware flashed. Purely stock.
Will do some more research in the meantime.
Click to expand...
Click to collapse
I can be sure but i would say yes, that does point to a partition. The only way to repair you partition table is if you can get into a custom recovery.
Your only hope is if you can flash a custom kernel:
http://www.meticulus.co.vu/p/galaxy-player-5-beanstalk-install-from.html
You can also extract the zImage from the .tar or .tar.md5 file and flash the zImage (kernel) with heimdall sort of like this:
heimdall flash --KERNEL zImage .
The kernel has custom recovery in it and if you can boot into it, you can use the partition tools to straiten yours out.
You might need this:
https://www.youtube.com/watch?v=Uzu4uDTDL5k
and you might want to read through this entire thread:
https://forum.xda-developers.com/showthread.php?t=2398120
Meticulus said:
I can be sure but i would say yes, that does point to a partition. The only way to repair you partition table is if you can get into a custom recovery.
Your only hope is if you can flash a custom kernel:
http://www.meticulus.co.vu/p/galaxy-player-5-beanstalk-install-from.html
You can also extract the zImage from the .tar or .tar.md5 file and flash the zImage (kernel) with heimdall sort of like this:
heimdall flash --KERNEL zImage .
The kernel has custom recovery in it and if you can boot into it, you can use the partition tools to straiten yours out.
You might need this:
https://www.youtube.com/watch?v=Uzu4uDTDL5k
and you might want to read through this entire thread:
https://forum.xda-developers.com/showthread.php?t=2398120
Click to expand...
Click to collapse
Thanks again Maticulus. I have been through all of the above to no avail. The last thread was interesting and tried to repeat the process there to see it the partitions were messed up.
Used adb-shell. (On Windows terminal)after installing Android devalopment suite. but Shows no connected devices. The player shows as SEC S5PC110 test B/D in device manager requiring drivers. Even though I have installed the samsung drivers.
I've also tried to use the zImage previously. Heimdall front end will only allow me to add the extracted file after adding the pit file. But in the end fails to upload the pit file.
Sorry for the low detail as I have decided to give up on this one. I appreciate your input to get me this far. You certainly went above and beyond to help and for that I thank you.
hopefully there is something in here to help someone else in a similar situation.