[Q] SKG Utility Controlbear S-off failure stuck in bootloader, advice

[markwatson]

Aplogies if this is not the best starting point but have been reading for 10 hours and am reluctant to take a next step after failure of s-off that has stuck phone in bootloader.
Details
Copied all SD card data to PC
Rooted phone as described by HTCdev

Used SKG utility to attempt s-off
Controlbear got stuck in some strage loop waiting for device after process had started. Never even got prompted to try the wire trick :-( 30 mins later I had to pull the pin
rebooting phone gave me the Controlbear black screen with Green arrow but could now not connect to the device using controlbear just said waiting for device then press any key to exit

Phone will not boot to android OS

when USB connected to phone in bootloader it says FASTBOOT USB and
fastboot devices lists my connected device so USB is OK

Followed instructions at unlimited.io/troubleshooting to try to recover controlbear -f seemed to do somthing so then did

fastboot flash boot recovery_backup.img
which failed could not find image !!!!! der
downloaded 4ext recovery.img
fastboot flash boot recovery.img

worked

Now have


Details of boot
*** UNLOCKED ***
Pyramid PVT SHIP S-ON RL
HBOOT 1.27.0000
Radio 11.24.3504.10_M
OpenADSP-v)2.6.0.2226.00.0131
cMMC-boot

CID reported by fastboot getvar cid is BM__001

Just tried everything from bootloader but always got back bootloader screen no Controlbear screen with arrow as before

At a whim I ran the controlbear -f again and whammo it came up with the 4ext recovery which I was happy to see. Despite doing a backup before starting anything 4ext says no backup present :-(


How can I recover device? I have downloaded the Bell stock RUU which should be correct for this device. Running it says device image version is 3.32.666.13Hesitant to try anything without some good advice. Hopefully I can recover and try the s-off agin but it's been a painful ride. Is it just as simple as clicking update on the RUU exe?

thanks

 

[ganeshp]

The backups are not present its saying when you are doing controlbear -f
That means you have no backup present in that controlbear folder

This can be either because of
1.you have another copy of controlbear folder where you done the soff process and where the controlbear saved the backups
(there will be boot_backup.img, recovery_ backup.img)

2.you deleted those images from the controlbear folder

Now what you can do is
1.just find the boot_backup.img and flash it via bootloader
fastboot flash boot boot_backup.img

That will get you out of the Juopunutbear screen..

No need to run the ruu in this case

Edit: and with regards to the 4EXT backup.. The backup will be stored in sdcard and during soff process the sdcard will be wiped.. That's why 4EXT said no backup present.. Just format your sdcard again.. Copy the sdcard backup from your pc (at least copy the Clockworkmod/backup folder to sdcard with the same path in sdcard... It holds your rom backup if you did any)
Then try the 4EXT backup

Sent from my pyramid.. Through blazing fast sonic waves

 

[kgs1992]

If your problem was solved, it's a good idea to add [SOLVED] to the topic.

 

[markwatson]

Still in trouble

HI thanks for the advice. Went to the io help and they said relock boot and reflash RUU. Now I have not RUU'd at all as have not been able to find a suitable one. But did fastboot oem lock as suggested. Can I now unlock it again as your post made way more sense and I found the recovery stuff you are speaking of. Just need to unlock and I should be able to recover. is there an unlock command?

 

[kgs1992]

HI thanks for the advice. Went to the io help and they said relock boot and reflash RUU. Now I have not RUU'd at all as have not been able to find a suitable one. But did fastboot oem lock as suggested. Can I now unlock it again as your post made way more sense and I found the recovery stuff you are speaking of. Just need to unlock and I should be able to recover. is there an unlock command?

Copy the unlock_code.bin to the folder with adb & fastboot.
Then

fastboot flash unlocktoken unlock_code.bin

Also, please come down to this channel for support. (I'm only going to help there because you used the tool)
SOLVED

 

[markwatson]

Solved Problem

Hi All Thanks to some sterling efforts by KGS1992 my problem was solved. Take care ye all to ensure that you ensure you get the correct version of controlbear there are many and you need the correct one for your android version. I'll post a detailed summary tomorrow I'm bushed.