• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root s-off mess up!

N

nexgenasian

Member
OMG, my computer powered down while trying to do S-OFF with JuopunutBear. So it got stuck at the JuopunutBear screen. To top it off I think I screwed something up in the in slot to stick the wire in. So I figured I'd just revert out of it and I've been trying TWRP Nandroid recover for hours trying to restore my rooted stock rom but to no avail, it seems to be stuck at install recovery img.
Furthermoreit seems that what I've been attempting is the wrong way to do it. The computer I was doing it on lost the files below:

boot_backup.img
recovery_backup.img
sdcard.img

I re ran controlbear on another machine, it generated those files and then I attempted this fix

Per instructions here,
Unlimited.IO

but I get
fastboot flash recover recovery_backup.img
sending 'recover' (16383 KB)... OKA [ 3.391s]
writing 'recover'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 7.320s

I suspect my tampering with nandroid has screwed up that recover_backup.img that was generated.

HELP!!!
Can someone send me those files??? Or are they unique to each phone? If so I'm so screwed!
 
pull the battery out, hold down power and down volume till you are on the bootloader? (white screen with fastboot option not to sure on the name of it recovery screen maybe?) Enable fastboot, Plug it into the computer that has the back up img files.

Go to your command prompt change the directory to your s-off tools folder

example: cd Desktop\soff

Then do this command

ControlBear -f

It'll prompt a few things in the cmd then in about a minute your phone will boot up normally

EDIT! sorry didn't read the whole issue. Those image files are unquie to the rom on your phone and the hardware you have installed.

Wish I could assist you further :\
 
You must log in or register to reply here.
Back
Top Bottom