I recently bought a new Samsung Galaxy Tab Pro 8.4 tablet, and not being satisfied that it's only running Android 4.4.2, I attempted to take care of that myself.
I believe I may have written over the OS with the recovery while using some bargain basement recovery flashing program instead of doing it by hand and using Heimdall.
Here's what I'm currently experiencing
-Whenever I try to boot into the device, I get stuck, indefinitely on the Samsung Galaxy Tab Pro loading screen.
-I have tried to utilize the recovery to try to restore to factory settings, to no avail.
-I have tried to flash a new recovery to the device using Heimdall with the following results
sudo heimdall flash --RECOVERY recovery.img --no-reboot
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
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:
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 send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...
-------
I am not sure what to do to currently fix the issue, I think if i re-write the entire partitions with a brand new ROM it could fix the problem entirely....however I'm not entirely sure how to go about that.
It appears that my pc and tablet are not wanting to communicate on this front at all. As all communications between the two inevitably ends in failure in download mode.
If anyone has any advice or suggestions I would be most appreciative
I also haad the idea of trying to adb flash the files over, but with the way Samsung's seem to be set up, I do not believe that is a viable option
I believe I may have written over the OS with the recovery while using some bargain basement recovery flashing program instead of doing it by hand and using Heimdall.
Here's what I'm currently experiencing
-Whenever I try to boot into the device, I get stuck, indefinitely on the Samsung Galaxy Tab Pro loading screen.
-I have tried to utilize the recovery to try to restore to factory settings, to no avail.
-I have tried to flash a new recovery to the device using Heimdall with the following results
sudo heimdall flash --RECOVERY recovery.img --no-reboot
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
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:
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 send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...
-------
I am not sure what to do to currently fix the issue, I think if i re-write the entire partitions with a brand new ROM it could fix the problem entirely....however I'm not entirely sure how to go about that.
It appears that my pc and tablet are not wanting to communicate on this front at all. As all communications between the two inevitably ends in failure in download mode.
If anyone has any advice or suggestions I would be most appreciative
I also haad the idea of trying to adb flash the files over, but with the way Samsung's seem to be set up, I do not believe that is a viable option
Aucun commentaire:
Enregistrer un commentaire