opensuse 13.1 x86_64
heimdall 1.4.1
Samsung s2 plus i9105p
i installed with no problem twrp-3.0.2-0-s2vep.img from twrp site or twrp-recovery-2.6.30_4.2.2.img from http://forum.xda-developers.com/showthread.php?t=1538053
but when i boot with home+volume up+power the stock recovery is launched instead of twrp.
log of the flashing:
**********************************************************************************************************
[email protected]:~/rpmd/samsung> heimdall flash --RECOVERY twrp-3.0.2-0-s2vep.img
Heimdall v1.4.1
Copyright (c) 2010-2014 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...
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...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
Rebooting device...
Releasing device interface...
[email protected]:
**********************************************************************************************************
ok i found solution.
use this statement:
heimdall flash --RECOVERY twrp-3.0.2-0-s2vep.img --no-reboot
once flashing is finished then use home+volume up+power. thus you launch twrp.
at the first launch twrp becomes the default recovery for the system.
Related
im trying to flash the JB boot loader to my 3113 using:
heimdall flash --secondary-boot sbl.bin --verbose (tried w/o verbose as well)
opening terminal in the folder containing the sbl
this is what i get back:
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...
PIT file download successful.
ERROR: Partition "secondary-boot" does not exist in the specified PIT.
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
kind of a newb when it comes to heimdall, so if someone can tell me what im doing wrong it will be greatly appreciated.
thanks
Wel after digging deeper, took a look at the pit file for this device and the sbl partition is actually named "SBL1". So the command should have been:
Heimdall flash --SBL1 Sbl.bin
Now I have JB bootloader, and just incase anybody wanted to know
Thanks
Sent from my GT-P3113 using xda app-developers app
Hi!
I had PacMan Rom Milestone 1 on my tab. Then the official Jelly Bean rom from Samsung was ported to the p6810 and I wanted to try it because I had problems with wifi.
After flashing with Mobile Odin the tab was stuck at Samsung logo (the animated and colored one). (I waited for +10 minutes, maybe I wasn t patient enogh)
So I tryed reflashing with Heimdall (as I only have a linux machine at the moment):
-First I flashed with the GUI and it did flash all the files except sbl (No correct response (or something like that) at the end of the transfer of sbl.bin).
-So I tryed flashing form command line but the command line tool did completely ignore the sbl. I also tryed to flash only sbl but so it didn´t flash anything, but didn´t give out any errors.
-Ok let´s flash the new rom released by Samsung for Spain in September. Sadly now the tab is stuck at the first boot screen
$ sudo heimdall flash --cache cache.img --factoryfs factoryfs.img --hidden hidden.img --recovery recovery.img --secondary-boot Sbl.bin --kernel zImage --param param.lfs
Password or swipe finger:
Heimdall v1.3.1, Copyright (c) 2010-2011, 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...
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 KERNEL
100%
KERNEL upload successful
Uploading RECOVERY
100%
RECOVERY upload successful
Uploading CACHE
100%
CACHE upload successful
Uploading FACTORYFS
100%
FACTORYFS upload successful
Uploading HIDDEN
100%
HIDDEN upload successful
Uploading SBL1
100%
SBL1 upload successful
Uploading PARAM
100%
PARAM upload successful
Ending session...
Rebooting device...
Re-attaching kernel driver...
Click to expand...
Click to collapse
I read many threads about this problem and I´m trying to discharge the tab now but I don´t have the same problems (I can go into recovery without problems).
Can I do a "wipe data/factory reset" without risking the brick bug?
Thank you for reading the long explanation.
Teddy
Ok I got it running with PacMan flashed from CWM and I restted the flash counter . Now I'll see if get Stock GB running...
I think I've made a few mistakes but I don't think all hope is lost. Part of my problem is simply that most of the links to ROMs and images for this phone are broken.
I'm going to try to keep this as short as possible, but this is what I did...
I followed this guide: http://forum.xda-developers.com/showthread.php?t=1801106
Unlocked bootloader with HTC's tool.
Flashed CWM recovery
Backed up stock ROM (1.55.531.3) with CWM
Flashed MikTouch 0.7 ROM
On reboot, the screen hung on the mytouch logo, so I presume that the flash failed and restore.
A few more tries and I decide to root and S-OFF before trying to flash the ROM again.
Used a superuser apk to gain root, verified that root was obtained.
Loaded up an ubuntu live CD, ran JuopunutBear.
Followed all steps and did the wire trick wrong (only tapped once instead of twice).
It failed, on rebooting the phone the following screen is displayed: https://www.dropbox.com/s/d1hz7j66h7mxj36/2014-10-13 13.46.31.jpg?dl=0
On checking the SD card, I find that the phone is unable to mount it, it seems to be fried so the backup I had is now gone.
I attempted to do the wire trick (correctly) many more times with no success.
I was able to revive the SD card later by repartitioning it with the MT4GS and then formatting it with my HTC Amaze, but the backup is still gone.
Did a ton more research and then went to bed...
This morning I woke up and shut off the computer I had used to do JuopunutBear, thereby losing the backup that it had made (mistake, didn't realize there was a backup there).
The only stock ROM I could find with a working download link was 1.28.531.9, I renamed it to P59IMG.zip and tried to flash it.
No luck, it has a progress bar that fills, then it reboots and I'm back to the screen with the green arrow.
I tried relocking the bootloader first, and it seems to get further but then fails when it realizes my HBOOT is newer than the one in the image.
I've been looking into downgrading the HBOOT version to 1.44.0007 so I can just do an S-OFF and be done with it, but I can't figure out how to do that.
I hear that you can't get S-OFF with 1.45.0013 using JuopunutBear, of course I only found this out today but I'm not even sure it's true.
The guide I was following uses HBOOT 1.45.0013 so when I get to the step where it says I can flash ROMs, I'm not really sure why it didn't work for me.
So here's where I'm stuck...
HBOOT 1.45.0013
S-ON
Unlocked
CWM 5.5.0.4 Recovery
Stuck on the software download screen: https://www.dropbox.com/s/d1hz7j66h7mxj36/2014-10-13 13.46.31.jpg?dl=0
I've gone through this process with several phones so I'm not really new at this. I've done a Samsung Behold II, HTC myTouch 3g and an HTC Amaze 4g. At this point I think my best course would be to restore this phone to stock before trying anything else. If I had a signed 1.55.531.3 ROM then I think I could get it back to where I started so I can try the whole thing again. But I can't find a working download link to one. I'd also be fine with going back to 1.28.531.9 as I think I could more easily do S-OFF with it.
Can someone with a bit more knowledge/experience please let me know if I'm missing something? Or just post some links to the ROMs I need?
Thanks!
Ok, I don't know why or how this worked, but I plugged the phone back into the ubuntu box and ran JuopunutBear like 10 times. It failed several times, in different places, with different errors each time. So I just kept doing it over and over again until it finally worked!
I now have MikTouch 0.7 installed and working perfectly.
Below is a log of the funkiness I experienced with JuopunutBear in case anyone ever has a similar problem...
[email protected]:~$ cd Downloads/
[email protected]:~/Downloads$ dir
cb
[email protected]:~/Downloads$ cd cb
[email protected]:~/Downloads/cb$ dir
adb ControlBear fastboot jb_boot.img jb_hboot.zip MD5SUM
[email protected]:~/Downloads/cb$ chmod 755 ControlBear adb fastboot
[email protected]:~/Downloads/cb$ sudo ./ControlBear rolBear
========= ControlBear 0.11 beta for JuopunutBear S-OFF ==========
(c) Copyright 2012 Unlimited.IO
If you have acquired this software from anywhere
other than our website this version may be out of
date and unsupported. Please see our website for
instructions on how to use this tool and for support.
This program may not be redistributed or included in other
works without the express permission of Team Unlimited.
Starting up......
Testing ADB connection
[email protected]:~/Downloads/cb$ sudo ./ControlBear
========= ControlBear 0.11 beta for JuopunutBear S-OFF ==========
(c) Copyright 2012 Unlimited.IO
If you have acquired this software from anywhere
other than our website this version may be out of
date and unsupported. Please see our website for
instructions on how to use this tool and for support.
This program may not be redistributed or included in other
works without the express permission of Team Unlimited.
Rebooting from bootloader
Waiting...
...Waiting
Detecting...Starting up......
Testing ADB connection
Test 1: Rebooting into bootloader
Waiting fastboot (5/60)
Waiting.....
Test 2: Booting device into JuopunutBear boot-mode
Waiting ADB.... (7/60)
Test 2.1: Rebooting into bootloader
Waiting fastboot (2/60)
Waiting...
Waiting...
Waiting ADB.... (1/60)
Test (2.1): Booting FAILED (2)
[email protected]:~/Downloads/cb$ sudo ./ControlBear
========= ControlBear 0.11 beta for JuopunutBear S-OFF ==========
(c) Copyright 2012 Unlimited.IO
If you have acquired this software from anywhere
other than our website this version may be out of
date and unsupported. Please see our website for
instructions on how to use this tool and for support.
This program may not be redistributed or included in other
works without the express permission of Team Unlimited.
Rebooting from bootloader
Waiting...
...Waiting
Detecting...Starting up......
Testing ADB connection
Test 1: Rebooting into bootloader
Waiting fastboot (5/60)
Waiting.....
Test 2: Booting device into JuopunutBear boot-mode
Waiting ADB.... (7/60)
Test 2.1: Rebooting into bootloader
Waiting fastboot (2/60)
Waiting...
Waiting...
Waiting ADB.... (1/60)
Test (2.1): Booting FAILED (2)
[email protected]:~/Downloads/cb$ sudo ./ControlBear
========= ControlBear 0.11 beta for JuopunutBear S-OFF ==========
(c) Copyright 2012 Unlimited.IO
If you have acquired this software from anywhere
other than our website this version may be out of
date and unsupported. Please see our website for
instructions on how to use this tool and for support.
This program may not be redistributed or included in other
works without the express permission of Team Unlimited.
Rebooting from bootloader
Waiting...
...Waiting
Detecting...Starting up......
Testing ADB connection
Test 1: Rebooting into bootloader
Waiting fastboot (5/60)
Waiting.....
Test 2: Booting device into JuopunutBear boot-mode
Waiting ADB.... (7/60)
Test 2.1: Rebooting into bootloader
Waiting fastboot (2/60)
Waiting...
Waiting...
Waiting ADB.... (1/60)
Test (2.1): Booting FAILED (2)
[email protected]:~/Downloads/cb$ sudo ./ControlBear
========= ControlBear 0.11 beta for JuopunutBear S-OFF ==========
(c) Copyright 2012 Unlimited.IO
If you have acquired this software from anywhere
other than our website this version may be out of
date and unsupported. Please see our website for
instructions on how to use this tool and for support.
This program may not be redistributed or included in other
works without the express permission of Team Unlimited.
Starting up......
Testing ADB connection
Test 1: Rebooting into bootloader
Waiting fastboot (5/60)
Waiting.....
Test 2: Booting device into JuopunutBear boot-mode
Waiting ADB.... (7/60)
Test 2.1: Rebooting into bootloader
Waiting fastboot (2/60)
Waiting...
Waiting...
Waiting ADB.... (1/60)
Test (2.1): Booting FAILED (2)
[email protected]:~/Downloads/cb$ sudo ./ControlBear
========= ControlBear 0.11 beta for JuopunutBear S-OFF ==========
(c) Copyright 2012 Unlimited.IO
If you have acquired this software from anywhere
other than our website this version may be out of
date and unsupported. Please see our website for
instructions on how to use this tool and for support.
This program may not be redistributed or included in other
works without the express permission of Team Unlimited.
Rebooting from bootloader
Waiting...
...Waiting
Detecting...Starting up......
Testing ADB connection
Test 1: Rebooting into bootloader
Waiting fastboot (5/60)
Waiting.....
Test 2: Booting device into JuopunutBear boot-mode
Waiting ADB.... (7/60)
Device detected.....................
Connection test ok!
Searching device.....
Found device.....
Backing up......
Transferring backups....
Backup ok!!
Using eMMC dev /dev/block/mmcblk0
Using MMC dev /dev/block/mmcblk1
Boot partition is /dev/block/mmcblk0p20
Recovery partition is /dev/block/mmcblk0p21
Is information correct?
You have 5 seconds time to stop process by pressing CTRL+C
Finding some beer.....
Found first....
Found second....
Found third....
Hmmmm... where is that last one....... Wait a sec....
=== Waiting for device....
(5/45)
Found device...
Waiting for device to settle... Please wait...
Cannot open file /data/local/tmp/jb_boot.img
Using eMMC dev /dev/block/mmcblk0
Using MMC dev /dev/block/mmcblk1
Boot partition is /dev/block/mmcblk0p20
Recovery partition is /dev/block/mmcblk0p21
Is information correct?
You have 5 seconds time to stop process by pressing CTRL+C
Finding some beer.....
Found first....
No Juopunutbear boot image found
Failed at (2.1) step....
Cannot enter JuopunutBear boot-mode
Quit....
[email protected]:~/Downloads/cb$ sudo ./ControlBear
========= ControlBear 0.11 beta for JuopunutBear S-OFF ==========
(c) Copyright 2012 Unlimited.IO
If you have acquired this software from anywhere
other than our website this version may be out of
date and unsupported. Please see our website for
instructions on how to use this tool and for support.
This program may not be redistributed or included in other
works without the express permission of Team Unlimited.
Starting up......
Searching device.....
Found device.....
Found backups!
Making room for beer......
Loading sixpacks on sdcard......
Loaded......
Do not remove sdcard from phone
Do wire-trick now!! Check the instructions at unlimited.io
Do not remove sdcard from phone
Do wire-trick now!! Check the instructions at unlimited.io
Do not remove sdcard from phone
Do wire-trick now!! Check the instructions at unlimited.io
Do not remove sdcard from phone
Do wire-trick now!! Check the instructions at unlimited.io
Do not remove sdcard from phone
Do wire-trick now!! Check the instructions at unlimited.io
Do not remove sdcard from phone
Do wire-trick now!! Check the instructions at unlimited.io
Do not remove sdcard from phone
Do wire-trick now!! Check the instructions at unlimited.io
Do not remove sdcard from phone
Do wire-trick now!! Check the instructions at unlimited.io
=== Waiting for device....
(2/45)
Fastboot detected
Rebooting device
Please wait....
(3/45)
Found device...
Waiting for device to settle... Please wait...
Cannot open file /data/local/tmp/jb_boot.img
Using eMMC dev /dev/block/mmcblk0
Using MMC dev /dev/block/mmcblk1
Boot partition is /dev/block/mmcblk0p20
Recovery partition is /dev/block/mmcblk0p21
Is information correct?
You have 5 seconds time to stop process by pressing CTRL+C
Finding some beer.....
Found first....
No Juopunutbear boot image found
Failed at (2.1) step....
Cannot enter JuopunutBear boot-mode
Quit....
[email protected]:~/Downloads/cb$ sudo ./ControlBear
========= ControlBear 0.11 beta for JuopunutBear S-OFF ==========
(c) Copyright 2012 Unlimited.IO
If you have acquired this software from anywhere
other than our website this version may be out of
date and unsupported. Please see our website for
instructions on how to use this tool and for support.
This program may not be redistributed or included in other
works without the express permission of Team Unlimited.
Starting up......
Searching device.....
Found device.....
Found backups!
Getting into bar.....
Raising Glass
SUCCESS - Taking a sip.
SUCCESS - Beer is tasty.
SUCCESS - Beer is tasty.
SUCCESS - Beer is tasty.
SUCCESS - Beer is tasty.
SUCCESS - Buddies and Beer
Checking alcohol level......
Seems to be just right.....
Let's take one more......
Aaaah, nice sunny day!!
Rebooting.......
=== Waiting for device....
(3/45)
Found device...
Waiting for device to settle... Please wait...
Cannot open file /data/local/tmp/jb_boot.img
Cowardly refusing to S-OFF this phone
Error code is: 4E D7 B9 21
Quit....
[email protected]:~/Downloads/cb$ sudo ./ControlBear
========= ControlBear 0.11 beta for JuopunutBear S-OFF ==========
(c) Copyright 2012 Unlimited.IO
If you have acquired this software from anywhere
other than our website this version may be out of
date and unsupported. Please see our website for
instructions on how to use this tool and for support.
This program may not be redistributed or included in other
works without the express permission of Team Unlimited.
Starting up......
Searching device.....
Found device.....
Found backups!
Beer......more beer......more beer...
...too much beer on sdcard...
You will need to reformat external sdcard manually!!
Rebooting RUU mode.......
=== Waiting for device....
(1/45)
Fastboot detected
JuopunutBear S-OFF success
Installing JuopunutBear hboot.....
Waiting.....
Flashing.......
Rebooting......
JuopunutBear hboot installed
Mortico said:
I think I've made a few mistakes but I don't think all hope is lost. Part of my problem is simply that most of the links to ROMs and images for this phone are broken.
I'm going to try to keep this as short as possible, but this is what I did...
I followed this guide: http://forum.xda-developers.com/showthread.php?t=1801106
Unlocked bootloader with HTC's tool.
Flashed CWM recovery
Backed up stock ROM (1.55.531.3) with CWM
Flashed MikTouch 0.7 ROM
On reboot, the screen hung on the mytouch logo, so I presume that the flash failed and restore.
Click to expand...
Click to collapse
Because the kernel is different, and you were still S-ON at the time, you would have needed to fastboot the boot.img file or else be stucjk in bootloop.
Mortico said:
A few more tries and I decide to root and S-OFF before trying to flash the ROM again.
Used a superuser apk to gain root, verified that root was obtained.
Loaded up an ubuntu live CD, ran JuopunutBear.
Followed all steps and did the wire trick wrong (only tapped once instead of twice).
Click to expand...
Click to collapse
Shouldn't have made a difference, unless you were just tapping once the whole time. Then the process will eventually fail. It takes a while to get the timing right.
Mortico said:
It failed, on rebooting the phone the following screen is displayed: https://www.dropbox.com/s/d1hz7j66h7mxj36/2014-10-13 13.46.31.jpg?dl=0
On checking the SD card, I find that the phone is unable to mount it, it seems to be fried so the backup I had is now gone.
I attempted to do the wire trick (correctly) many more times with no success.
I was able to revive the SD card later by repartitioning it with the MT4GS and then formatting it with my HTC Amaze, but the backup is still gone.
Did a ton more research and then went to bed...
Click to expand...
Click to collapse
From there there was a restore script on the Juopunutbear package. But in hindsight, you probably already know that.
Mortico said:
This morning I woke up and shut off the computer I had used to do JuopunutBear, thereby losing the backup that it had made (mistake, didn't realize there was a backup there).
The only stock ROM I could find with a working download link was 1.28.531.9, I renamed it to P59IMG.zip and tried to flash it.
No luck, it has a progress bar that fills, then it reboots and I'm back to the screen with the green arrow.
I tried relocking the bootloader first, and it seems to get further but then fails when it realizes my HBOOT is newer than the one in the image.
I've been looking into downgrading the HBOOT version to 1.44.0007 so I can just do an S-OFF and be done with it, but I can't figure out how to do that.
Click to expand...
Click to collapse
Downgrading does not worrk. Can only go in one direction.
Mortico said:
I hear that you can't get S-OFF with 1.45.0013 using JuopunutBear, of course I only found this out today but I'm not even sure it's true.
The guide I was following uses HBOOT 1.45.0013 so when I get to the step where it says I can flash ROMs, I'm not really sure why it didn't work for me.
So here's where I'm stuck...
HBOOT 1.45.0013
S-ON
Unlocked
CWM 5.5.0.4 Recovery
Stuck on the software download screen: https://www.dropbox.com/s/d1hz7j66h7mxj36/2014-10-13 13.46.31.jpg?dl=0
I've gone through this process with several phones so I'm not really new at this. I've done a Samsung Behold II, HTC myTouch 3g and an HTC Amaze 4g. At this point I think my best course would be to restore this phone to stock before trying anything else. If I had a signed 1.55.531.3 ROM then I think I could get it back to where I started so I can try the whole thing again. But I can't find a working download link to one. I'd also be fine with going back to 1.28.531.9 as I think I could more easily do S-OFF with it.
Can someone with a bit more knowledge/experience please let me know if I'm missing something? Or just post some links to the ROMs I need?
Thanks!
Click to expand...
Click to collapse
Found your request in another thread, from the below it looks resolved, but the offer for the images are still on the table (maybe you have a better way to host it than I do, if you care for that ).
Mortico said:
Ok, I don't know why or how this worked, but I plugged the phone back into the ubuntu box and ran JuopunutBear like 10 times. It failed several times, in different places, with different errors each time. So I just kept doing it over and over again until it finally worked!
I now have MikTouch 0.7 installed and working perfectly.
Below is a log of the funkiness I experienced with JuopunutBear in case anyone ever has a similar problem...
[email protected]:~$ cd Downloads/
[email protected]:~/Downloads$ dir
cb
[email protected]:~/Downloads$ cd cb
[email protected]:~/Downloads/cb$ dir
adb ControlBear fastboot jb_boot.img jb_hboot.zip MD5SUM
[email protected]:~/Downloads/cb$ chmod 755 ControlBear adb fastboot
[email protected]:~/Downloads/cb$ sudo ./ControlBear rolBear
========= ControlBear 0.11 beta for JuopunutBear S-OFF ==========
(c) Copyright 2012 Unlimited.IO
If you have acquired this software from anywhere
other than our website this version may be out of
date and unsupported. Please see our website for
instructions on how to use this tool and for support.
This program may not be redistributed or included in other
works without the express permission of Team Unlimited.
Starting up......
Testing ADB connection
[email protected]:~/Downloads/cb$ sudo ./ControlBear
========= ControlBear 0.11 beta for JuopunutBear S-OFF ==========
(c) Copyright 2012 Unlimited.IO
If you have acquired this software from anywhere
other than our website this version may be out of
date and unsupported. Please see our website for
instructions on how to use this tool and for support.
This program may not be redistributed or included in other
works without the express permission of Team Unlimited.
Rebooting from bootloader
Waiting...
...Waiting
Detecting...Starting up......
Testing ADB connection
Test 1: Rebooting into bootloader
Waiting fastboot (5/60)
Waiting.....
Test 2: Booting device into JuopunutBear boot-mode
Waiting ADB.... (7/60)
Test 2.1: Rebooting into bootloader
Waiting fastboot (2/60)
Waiting...
Waiting...
Waiting ADB.... (1/60)
Test (2.1): Booting FAILED (2)
[email protected]:~/Downloads/cb$ sudo ./ControlBear
========= ControlBear 0.11 beta for JuopunutBear S-OFF ==========
(c) Copyright 2012 Unlimited.IO
If you have acquired this software from anywhere
other than our website this version may be out of
date and unsupported. Please see our website for
instructions on how to use this tool and for support.
This program may not be redistributed or included in other
works without the express permission of Team Unlimited.
Rebooting from bootloader
Waiting...
...Waiting
Detecting...Starting up......
Testing ADB connection
Test 1: Rebooting into bootloader
Waiting fastboot (5/60)
Waiting.....
Test 2: Booting device into JuopunutBear boot-mode
Waiting ADB.... (7/60)
Test 2.1: Rebooting into bootloader
Waiting fastboot (2/60)
Waiting...
Waiting...
Waiting ADB.... (1/60)
Test (2.1): Booting FAILED (2)
[email protected]:~/Downloads/cb$ sudo ./ControlBear
========= ControlBear 0.11 beta for JuopunutBear S-OFF ==========
(c) Copyright 2012 Unlimited.IO
If you have acquired this software from anywhere
other than our website this version may be out of
date and unsupported. Please see our website for
instructions on how to use this tool and for support.
This program may not be redistributed or included in other
works without the express permission of Team Unlimited.
Rebooting from bootloader
Waiting...
...Waiting
Detecting...Starting up......
Testing ADB connection
Test 1: Rebooting into bootloader
Waiting fastboot (5/60)
Waiting.....
Test 2: Booting device into JuopunutBear boot-mode
Waiting ADB.... (7/60)
Test 2.1: Rebooting into bootloader
Waiting fastboot (2/60)
Waiting...
Waiting...
Waiting ADB.... (1/60)
Test (2.1): Booting FAILED (2)
[email protected]:~/Downloads/cb$ sudo ./ControlBear
========= ControlBear 0.11 beta for JuopunutBear S-OFF ==========
(c) Copyright 2012 Unlimited.IO
If you have acquired this software from anywhere
other than our website this version may be out of
date and unsupported. Please see our website for
instructions on how to use this tool and for support.
This program may not be redistributed or included in other
works without the express permission of Team Unlimited.
Starting up......
Testing ADB connection
Test 1: Rebooting into bootloader
Waiting fastboot (5/60)
Waiting.....
Test 2: Booting device into JuopunutBear boot-mode
Waiting ADB.... (7/60)
Test 2.1: Rebooting into bootloader
Waiting fastboot (2/60)
Waiting...
Waiting...
Waiting ADB.... (1/60)
Test (2.1): Booting FAILED (2)
[email protected]:~/Downloads/cb$ sudo ./ControlBear
========= ControlBear 0.11 beta for JuopunutBear S-OFF ==========
(c) Copyright 2012 Unlimited.IO
If you have acquired this software from anywhere
other than our website this version may be out of
date and unsupported. Please see our website for
instructions on how to use this tool and for support.
This program may not be redistributed or included in other
works without the express permission of Team Unlimited.
Rebooting from bootloader
Waiting...
...Waiting
Detecting...Starting up......
Testing ADB connection
Test 1: Rebooting into bootloader
Waiting fastboot (5/60)
Waiting.....
Test 2: Booting device into JuopunutBear boot-mode
Waiting ADB.... (7/60)
Device detected.....................
Connection test ok!
Searching device.....
Found device.....
Backing up......
Transferring backups....
Backup ok!!
Using eMMC dev /dev/block/mmcblk0
Using MMC dev /dev/block/mmcblk1
Boot partition is /dev/block/mmcblk0p20
Recovery partition is /dev/block/mmcblk0p21
Is information correct?
You have 5 seconds time to stop process by pressing CTRL+C
Finding some beer.....
Found first....
Found second....
Found third....
Hmmmm... where is that last one....... Wait a sec....
=== Waiting for device....
(5/45)
Found device...
Waiting for device to settle... Please wait...
Cannot open file /data/local/tmp/jb_boot.img
Using eMMC dev /dev/block/mmcblk0
Using MMC dev /dev/block/mmcblk1
Boot partition is /dev/block/mmcblk0p20
Recovery partition is /dev/block/mmcblk0p21
Is information correct?
You have 5 seconds time to stop process by pressing CTRL+C
Finding some beer.....
Found first....
No Juopunutbear boot image found
Failed at (2.1) step....
Cannot enter JuopunutBear boot-mode
Quit....
[email protected]:~/Downloads/cb$ sudo ./ControlBear
========= ControlBear 0.11 beta for JuopunutBear S-OFF ==========
(c) Copyright 2012 Unlimited.IO
If you have acquired this software from anywhere
other than our website this version may be out of
date and unsupported. Please see our website for
instructions on how to use this tool and for support.
This program may not be redistributed or included in other
works without the express permission of Team Unlimited.
Starting up......
Searching device.....
Found device.....
Found backups!
Making room for beer......
Loading sixpacks on sdcard......
Loaded......
Do not remove sdcard from phone
Do wire-trick now!! Check the instructions at unlimited.io
Do not remove sdcard from phone
Do wire-trick now!! Check the instructions at unlimited.io
Do not remove sdcard from phone
Do wire-trick now!! Check the instructions at unlimited.io
Do not remove sdcard from phone
Do wire-trick now!! Check the instructions at unlimited.io
Do not remove sdcard from phone
Do wire-trick now!! Check the instructions at unlimited.io
Do not remove sdcard from phone
Do wire-trick now!! Check the instructions at unlimited.io
Do not remove sdcard from phone
Do wire-trick now!! Check the instructions at unlimited.io
Do not remove sdcard from phone
Do wire-trick now!! Check the instructions at unlimited.io
=== Waiting for device....
(2/45)
Fastboot detected
Rebooting device
Please wait....
(3/45)
Found device...
Waiting for device to settle... Please wait...
Cannot open file /data/local/tmp/jb_boot.img
Using eMMC dev /dev/block/mmcblk0
Using MMC dev /dev/block/mmcblk1
Boot partition is /dev/block/mmcblk0p20
Recovery partition is /dev/block/mmcblk0p21
Is information correct?
You have 5 seconds time to stop process by pressing CTRL+C
Finding some beer.....
Found first....
No Juopunutbear boot image found
Failed at (2.1) step....
Cannot enter JuopunutBear boot-mode
Quit....
[email protected]:~/Downloads/cb$ sudo ./ControlBear
========= ControlBear 0.11 beta for JuopunutBear S-OFF ==========
(c) Copyright 2012 Unlimited.IO
If you have acquired this software from anywhere
other than our website this version may be out of
date and unsupported. Please see our website for
instructions on how to use this tool and for support.
This program may not be redistributed or included in other
works without the express permission of Team Unlimited.
Starting up......
Searching device.....
Found device.....
Found backups!
Getting into bar.....
Raising Glass
SUCCESS - Taking a sip.
SUCCESS - Beer is tasty.
SUCCESS - Beer is tasty.
SUCCESS - Beer is tasty.
SUCCESS - Beer is tasty.
SUCCESS - Buddies and Beer
Checking alcohol level......
Seems to be just right.....
Let's take one more......
Aaaah, nice sunny day!!
Rebooting.......
=== Waiting for device....
(3/45)
Found device...
Waiting for device to settle... Please wait...
Cannot open file /data/local/tmp/jb_boot.img
Cowardly refusing to S-OFF this phone
Error code is: 4E D7 B9 21
Quit....
[email protected]:~/Downloads/cb$ sudo ./ControlBear
========= ControlBear 0.11 beta for JuopunutBear S-OFF ==========
(c) Copyright 2012 Unlimited.IO
If you have acquired this software from anywhere
other than our website this version may be out of
date and unsupported. Please see our website for
instructions on how to use this tool and for support.
This program may not be redistributed or included in other
works without the express permission of Team Unlimited.
Starting up......
Searching device.....
Found device.....
Found backups!
Beer......more beer......more beer...
...too much beer on sdcard...
You will need to reformat external sdcard manually!!
Rebooting RUU mode.......
=== Waiting for device....
(1/45)
Fastboot detected
JuopunutBear S-OFF success
Installing JuopunutBear hboot.....
Waiting.....
Flashing.......
Rebooting......
JuopunutBear hboot installed
Click to expand...
Click to collapse
Excellent! If at first you don't succeed, try try again!
From there there was a restore script on the Juopunutbear package. But in hindsight, you probably already know that.
Click to expand...
Click to collapse
Yeah, by the time I found out about the restore function the computer I had booted up with the live CD had been rebooted into windows. So whatever backups JuopunutBear made disappeared when I rebooted.
I'm quite relieved that I got this phone working again, we need to get another year out of it at least. I had been nagging my wife for about 6 months to let me install a ROM on her phone as it was crashing constantly and extremely laggy. I couldn't stand to even watch her use it. Finally her phone became unusable even for her and she handed it over.
Had I not succeed, it would have meant buying her a new phone that we can't really afford right now. But worse, it would mean she'd never trust me to touch another phone of her's again.
VINDICATED! Her phone is now running better than the day she bought it.
[Solved] Heimdall problem s10e "an error has occured while updating device software"
Hi there, I was trying to change my firmware (to prepare my phone before flashing a lineageos rom), I did so using heimdall (last samsung firmware downloaded from sammobile), and it crashed in the middle of the process (while copying VENDOR file). Not sure if it is a problem with the firmware or something else (but I guess not the cable as I tried with 2 cables and the problem arrives always at the same moment).
The phone is a SM-G970F, I was trying to flash the firmware U9DTJA.
Anyway, I can still flash with heimdall, although the screen is not the "standard" download mode screen… but I don't know what to do!? I tried to install virtualbox+samsung drivers + odin (standard version and then patched version), I can't get odin to recognize my phone. Windows just tells me "this device can perform faster" when I allow virtualbox to detect the phone (which appears as Samsung Gadget Serial [021B]). I also tried smart switch without success (I don't know what it is suppose to do, but looks like it does not recognize any phone). Do you think this is normal due to the fact that the phone is not truly in download mode? Or is it a problem with windows drivers? An idea to either fix things with heimdall or to get odin working?
I would appreciate if someone has any hints as it's my only phone and I'm kind of stuck
-------------- EDIT: this is what I get when flashing:
heimdall flash --BOOTLOADER sboot.bin --CM cm.bin --PARAM param.bin --UP_PARAM up_param.bin --KEYSTORAGE keystorage.bin --UH uh.bin --DTB dt.img --DTBO dtbo.img --BOOT boot.img --RECOVERY recovery.img --RADIO modem.bin --DQMDBG dqmdbg.img --VBMETA vbmeta.img --SYSTEM system.img --VENDOR vendor.img --PRODUCT product.img --CACHE cache.img --OMR omr.img --CP_DEBUG modem_debug.bin --USERDATA userdata.img
Heimdall v1.4.2
Copyright (c) 2010-2017 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...
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...
PIT file download successful.
Uploading BOOTLOADER
100%
BOOTLOADER upload successful
Uploading CM
100%
CM upload successful
Uploading PARAM
100%
PARAM upload successful
Uploading UP_PARAM
100%
UP_PARAM upload successful
Uploading KEYSTORAGE
100%
KEYSTORAGE upload successful
Uploading UH
100%
UH upload successful
Uploading DTB
100%
DTB upload successful
Uploading DTBO
100%
DTBO upload successful
Uploading BOOT
100%
BOOT upload successful
Uploading RECOVERY
100%
RECOVERY upload successful
Uploading RADIO
100%
RADIO upload successful
Uploading DQMDBG
100%
DQMDBG upload successful
Uploading VBMETA
100%
VBMETA upload successful
Uploading SYSTEM
100%
SYSTEM upload successful
Uploading VENDOR
21%
ERROR: Failed to send file part packet!
ERROR: VENDOR upload failed!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Click to expand...
Click to collapse
Well I found a workaround. Apparently:
- There is a bug with heimdall or libusb, I don't know at which level exactly but it does not work well with this device and I'm apparently not the only one for which it happened
- Altough the screen was not the "standard" download mode ,the phone was ready to be flashed, no problem with that.
- I managed to flash with odin by borrowing a windows computer… … …
- I have no idea why it does not work with virtualbox, but apparently this was really a virtualbox problem (or the way linux deals with usb, no idea) and nothing related to the phone in particular. It would be great to find a way to get that working, but I have no clue so far.
At least, I have a working phone now…
Hi,
I would like to get suggestions on a ROM to flash on A12,
Lineage is available?
Suggestions.
Thank you.
Try some gsi roms.
Yes, i’m going to flash GSI’s on my PIT partition for system.img, but that partition isn’t found from my PIT file
An i’m encountering this error below on Heimdall,
Code:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
ERROR: Failed to send handshake!ERROR: Protocol initialisation failed!
Releasing device interface...
But my Android side is below, and feels like ok,
Code:
Heimdall Download mode (high speed)
Product name: SM-A125F
Current binary: Samsung official
OEM lock: Off (U)
KG status: Checking
MTK secure boot: Enable
Warranty void: 0x0 (0x0)
PR SWREV: B1 NS1 K1 S1
Secure Download: Enable
CASS: 0x1
DID: 000ac3086b58
CARRIER_ID: TGY
Im trying to install some GSI's too, the problem is that we have the system.img but to make the changes we have to flash it in the "super" partition, thats why Heimdall doesnt recognized it from the A12's pit... Please let me know if you guys solve it...
I guess, instead flash your GSI .img files on your super partition, and you instead need to download online PIT docs, according to your ‘‘Product name’’.
I tried to flash the Lineage GSI by Andy Yan on SF using Heimdall (yes i’m no longer on Windows), and also AOSP one, but unfortunately and somewhy,
Code:
SW REV check failed!
I cant follow you , Im not so much familiarized with this dynamic partition but Ill try to...
For me, on LinageOs when I turn off the screen and then turn it back on screen touch doesn't work.
GSI 11 same problem and the 3 button navigation pannel not working.