S-Off help!!!! - HTC Rezound

so i did s-off for my rezound, and it says everything has completed, however it is stuck at i guess the final reboot, at the htc screen. black background with silver-blackish htc letters. heres what CMD said:
Old beer detected...... Please wait......
Starting up......
Connecting to device...
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/mmcblk0p22
Recovery partition is /dev/block/mmcblk0p23
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....
Found fourth....
Rebooting.......
=== Waiting for device....
(22/45)
Found device...
Waiting for device to settle... Please wait...
Making room for beer......
Loading sixpacks on sdcard......
Loaded......
Board vigor detected
Rebooting into fastboot!!
=== Waiting for device....
(4/45)
Fastboot detected
Do not remove sdcard from phone
Do wire-trick now!! Look instructions on the web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions on the web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions on the web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions on the web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions on the web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions on the web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions on the web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions on the web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions on the web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions on the web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions on the web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions on the web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions on the web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions on the web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions on the web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions on the web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions on the web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions on the web
Waiting for device....
(9/45)
Fastboot detected
Rebooting device
Please wait....
(10/45)
Found device...
Waiting for device to settle... Please wait...
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....
(1/45)
Fastboot detected
Beer is tasty, lets take another!!
Please wait....
Found device...
Waiting for device to settle... Please wait...
Beer......more beer......more beer...
Rebooting RUU mode.......
=== Waiting for device....
(3/45)
Fastboot detected
JuopunutBear S-OFF success
Cannot open embed output file
Installing JuopunutBear hboot.....
Waiting.....
Flashing.......
Rebooting......
JuopunutBear hboot installed
Press ENTER to exit.....
what should i do???

Press enter and pull battery.

GrayTheWolf said:
Pull battery?
Click to expand...
Click to collapse
was scared too, but alright.
i pressed enter, i unplugged the usb, to pull the battery, and hboot came up, but it says:
tampered
locked
s-off
all the info
then it says "RUU" and thats it.... theres no fast boot, recovery etc...

so should i still just pull batery or select ruu?

nvm fixed.... thaks Wolf!

so, how did you end up fixing it? was it just a battery pull that was required?

Quadrider10 said:
nvm fixed.... thaks Wolf!
Click to expand...
Click to collapse
Hi, I'm having the exact same problem that you did. Can you please post what you did to fix it?
- Steve

With all that beer, I'm thinking he passed out!
Sent from my HTC Incredible 4G on Verizon's periodically blazing fast and mostly reliable 4G LTE network using xda-developers app

Related

[Q] Please help - Vital mistake made while flashing rom

Good evening all!
It seems that I may have made a mistake! Either that or my mind is to tired to think strait! Please help!
Firstly, after having several successful attempts at flashing custom roms/radios and experimenting with my device, I thought I had finally found the ROM of choice! Here's what I have done: performed a task29 run to clean up any straggling files ... normal process right!? No! I forgot the most important step to the process before totally wiping all information off my phone. I formatted my SD card without adding any type of rom to my device before running task29. I've tried running the customRUU tool from my PC and have had zero luck. My phone attempts to boot with none of the red text in the loading screen and just hangs. I can enter the bootloader screen but I still have zero luck on getting anything to work from the customruu tool.
Any information that anyone could willing provide would be greatly apprecaited!! I apologies for wasting anyones time!
Thanks in advance,
Braizy <<<< (Noob!)
Braizy said:
Good evening all!
It seems that I may have made a mistake! Either that or my mind is to tired to think strait! Please help!
Firstly, after having several successful attempts at flashing custom roms/radios and experimenting with my device, I thought I had finally found the ROM of choice! Here's what I have done: performed a task29 run to clean up any straggling files ... normal process right!? No! I forgot the most important step to the process before totally wiping all information off my phone. I formatted my SD card without adding any type of rom to my device before running task29. I've tried running the customRUU tool from my PC and have had zero luck. My phone attempts to boot with none of the red text in the loading screen and just hangs. I can enter the bootloader screen but I still have zero luck on getting anything to work from the customruu tool.
Any information that anyone could willing provide would be greatly apprecaited!! I apologies for wasting anyones time!
Thanks in advance,
Braizy <<<< (Noob!)
Click to expand...
Click to collapse
Dude, you should be able to hold down the volume down button before powering on the device. You should get to the bootloader screen with no issues and be able to establish an ActiveSync <--> USB connection from there with your PC and flash using the CustomRUU.exe tool.
Braizy said:
Good evening all!
It seems that I may have made a mistake! Either that or my mind is to tired to think strait! Please help!
Firstly, after having several successful attempts at flashing custom roms/radios and experimenting with my device, I thought I had finally found the ROM of choice! Here's what I have done: performed a task29 run to clean up any straggling files ... normal process right!? No! I forgot the most important step to the process before totally wiping all information off my phone. I formatted my SD card without adding any type of rom to my device before running task29. I've tried running the customRUU tool from my PC and have had zero luck. My phone attempts to boot with none of the red text in the loading screen and just hangs. I can enter the bootloader screen but I still have zero luck on getting anything to work from the customruu tool.
Any information that anyone could willing provide would be greatly apprecaited!! I apologies for wasting anyones time!
Thanks in advance,
Braizy <<<< (Noob!)
Click to expand...
Click to collapse
Next time use FlashaholicRUU as it will perform task29+flash the ROM.. (won't let you proceed if you don't include an .nbh)
agupta80 said:
Dude, you should be able to hold down the volume down button before powering on the device. You should get to the bootloader screen with no issues and be able to establish an ActiveSync <--> USB connection from there with your PC and flash using the CustomRUU.exe tool.
Click to expand...
Click to collapse
That's what I thought as well ... I have my device connected via USB, looking at the bootloader screen as we speak and it's still not showing my anything under ActiveSync. I've tried installing a different Radio as well, still no change.
Here's exactly what I'm looking at on the bootloader screen:
PB81120 SS-B3
SPL-2.08.HSPL 8G XE
0X05
CotullaHSPL 0X50
USB
That's it! I can attempt to boot normal as if I were just powering on the device and I get the white "stick together" t-mobile splash screen.
Scabes24 said:
Next time use FlashaholicRUU as it will perform task29+flash the ROM.. (won't let you proceed if you don't include an .nbh)
Click to expand...
Click to collapse
I tried using FlashaholicRUU just now. I was able to perform the task29 process successfully, I held the volume down button at 100% and let the phone enter into the bootloader screen. I then continue with the on screen prompts from PC to start the ROM update process ... only for the update utility to tell me;
ERROR [240] : FILE OPEN The Update Utility can not open the requested file. Please check your update Utility.
Click to expand...
Click to collapse
Update:
I was finally able to get it flashed and operational. I found a ROM that had a customRUU packaged with the download and a good radio. I used the Utility in the package and all is working now. Not to pleased with the ROM but it's only temporary. Thanks a bunch for everyone's help and input.
Excuse me while I wipe the sweat from my forehead!
-Braizy

[DOWNGRADE HBOOT/UNBRICK] HBOOT 1.50 -> 1.40 for S-OFF/Root

Firstly, I want to thank the guys that made it all possible...
MOVZX
RussianBear
Fuses
Dexter93
TrevE
Crackanug
closeone
USSENTERNCC1701E
jcase
The entire Revolutionary team
Now on to the goodies...
UPDATE 3/21/12
DO NOT BRICK YOUR DEVICE IF YOU ARE S-OFF, THE DEVICE WILL NOT GO INTO EMMC MODE AS EXPECTED, AND YOU WILL HAVE A TRUE BRICK IN YOUR HANDS!!!
If you're already S-OFF, but on 1.50, you can do one of two things... I have attached the PG86IMG.zip with the 1.40 bootloader on it, download it copy to sd card and flash via bootloader.
The other option is to simply re-run 1.13 RUU, this will downgrade it as well, but this will also erase all data in the process.
For S-ON... Things you'll need...
A linux PC and some very basic linux knowledge...
The 2.17 RUU ZIP image
You'll also need the 1.13 RUU EXE (All the RUU's can be found here -> http://www.filefactory.com/f/4ef0ef536face67a/)
Download the downgrade.zip in the attachment (includes downgrade tool, hboot 1.40.0000(hboot.img), and misc.img)
Backup your apps/data if you need to, this process will wipe EVERYTHING
(If you're already bricked, start from Step 2)
closeone has posted a "all in one" Tool to do much of the following. (No, it's not a one click, there likely won't be a one click using this method, don't ask about it)
I have not personally tested it, but the idea is sound and if he's done it correctly it should work just fine, If you wish to try it, it is here (Yes, it still uses Linux, but on a bootable CD) -> http://forum.xda-developers.com/showthread.php?t=1563342
First Step
VIDEO OF STEP 1 (video says Step 2, but just start here)
BRICK (Yes, I said brick) your device. BUT in a CERTAIN way.
You need to brick your device by corrupting the HBOOT during the HBOOT Update.
(MAKE SURE YOU ARE TRULY S-ON, IF YOU BRICK YOUR DEVICE WHILE S-OFF, THIS IS PERMANENT and CANNOT BE RECOVERED FROM)
(MAKE SURE YOU ARE TRULY S-ON, IF YOU BRICK YOUR DEVICE WHILE S-OFF, THIS IS PERMANENT and CANNOT BE RECOVERED FROM)
(MAKE SURE YOU ARE TRULY S-ON, IF YOU BRICK YOUR DEVICE WHILE S-OFF, THIS IS PERMANENT and CANNOT BE RECOVERED FROM)
(If you are HTC Unlocked, you MUST RELOCK BEFORE starting)
1.) Take your 2.17 ZIP image, put it on the root of your SDCard, call it PG86IMG.zip.
2.) With the phone on Battery power alone, Reboot to BootLoader, let it detect the zip and read and get to the point where it wants you to press Vol-Up to update.
3.) LET THE DEVICE SIT FOR AT LEAST a Minute or Two.
4.) Pull off the battery cover (careful not to let the battery fall out) and plug the device into AC power. (HTC Power charger, other chargers have been known not to work for this, the reason for this is that the HTC's power adapters output more power than the standard ones.)
5.) Pull the battery out. (The device should stay on, if it doesn't, start over and try again) Also, leave the battery out through the REST OF THIS GUIDE until told to put it back in.
6.) Here's the tricky part, Read this a couple times, be ready to pull the ac cable out at the right time... press the vol up key in, Give it approximately 5 seconds from the START of it saying the word "Updating" next to Bootloader (The very first one it flashes) Then Pull the charger cord promptly, and plug it right back in, if this worked right, you'll see the red charge light be VERY(VERY VERY) DIM, and it should stay solid for the most part. (See the FAQ in post 2 for more info on this step, if you're having issues.)
The device is now bricked and ready for the next part.
Second Step
VIDEO OF STEP 2 (Removed for now, it's outdated)
The next step is the linux part. Do not plug your phone in to the linux box until you are told to do so. Very important.
1.) Boot up to Linux (I used Ubuntu, but I am guessing that any Linux OS will work)
2.) Extract your downgrade.zip file to the linux PC, Home folder is the best spot and is the easiest to work with.
3.) Open up Terminal, gain root, (su, or sudo -s)(give it your password)
4.) Run the command chmod 755 downgrade (if it's not in your home folder, add the full path to it)
5.) Type ./downgrade and press Enter.
You will see the below output:
Code:
==== Original emmc_recover tool written by Fuses ====
==== Downgrade v 1.0, written by Unknownforce ====
Ready to Downgrade?
Press ENTER for yes, or Press Ctrl+C for no.
Press Enter here, then you'll get the following:
Code:
Step 1... Plug in Device while holding down Volume Down key...
Waiting for device...
Now... Hold down the Volume Down key, (and keep holding it down) and plug the phone in, you should see something similar to the below:
Code:
Found the Correct Device!
Writing image file!
511+1 records in
511+1 records out
1047808 bytes (1.0 MB) copied, 0.36689 s, 2.9 MB/s
SUCCESS!
Step 2... Unplug the device now.
AFTER device is removed, press Enter to proceed to next step.
Unplug the device, and press Enter again, you will see the following:
Code:
Step 3... Plug the device back in
while holding the Volume Down key again.
Waiting for device...
Plug the device in again holding down the Volume Down key the entire time again, you should see the following:
Code:
Writing image file!
511+1 records in
511+1 records out
1047808 bytes (1.0 MB) copied, 0.36689 s, 2.9 MB/s
SUCCESS!
From there, pull your SD Card out (so it doesn't try to update from the PG86IMG.zip...) throw your battery back in, boot up to bootloader. 1.40.0000
(Some people have said that they needed to "let the device sit" for a few minutes here, mine works immediately every time, YMMV)
To get back to a bootable rom and revolutionary, select FASTBOOT, connect it to the PC and run the 1.13 RUU EXE all the way through, (NOT the zip) then just revolutionary (a few times) and have a beer.
A few side notes:
When you run Revolutionary, you might have to do it a few times... I also didn't get to the point where it asked to flash a recovery... so I did this via fastboot, and simply used TWRP 2.0 .img file.
Use fastboot flash recovery blahblahblah.img -- this did NOT work when it was just regular 1.40.0000 S-OFF, only when it was revolutionary 1.40.1100 S-OFF
DISCLAIMER This is NOT a guarantee... because I'm sure it could come back... But in basic terms... I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE, I have given you a method that worked for me, and SHOULD work for you, but if your house burns down, your car gets a flat tire, or your phone stops working... You are responsible for any and all of those things.
FAQ's
Can I do this on Windows?
Currently there is no way to do this on Windows. It's unlikely that there will be a way to do it on windows, Windows USB is too slow and doesn't detect the device the same as Linux does.
Can I do this in (Insert virtual PC software)?
The only one I've heard that works is VMWare, however You're again relying on Windows to pass the device to a virtual machine, which isn't ideal. I know for a fact that VirtualBox does not work, and Cygwin also does not work.
Common Errors
I can't get my phone to brick, I've tried a million times!
Patience is a virtue. This step is the hardest part of all, HTC Designed their phone to be brick proof for a reason. I believe the trick here is to let the device sit on the update screen for a minute or two, then do the update and count out 5 seconds. Also there's the update bar that appears in the upper right hand corner, much like the bar that is there when it's checking the zip file before the update prompt. The INSTANT you see that, pull the power. This is typically 5-6 seconds after it says updating, but only after it's been sitting for a bit... I believe the trick is to let it sit for a bit before pressing Volume up to update.
My PG86IMG.zip is not detected or the phone checks it and it doesn't prompt me to update it
There are several possibilities:
The phone is HTC Unlocked - You must re-lock.
The phone is S-OFF - Don't even try to brick it because you'll permanently brick it.
The phone is Re-locked, but still has a custom rom/recovery on it. - This will show a security warning and not allow the PG86IMG.zip to be flashed. - You must put the phone in FASTBOOT USB and run the RUU exe that matches your software version.
The File is not named correctly, it's PG86IMG.zip (Make sure it's not PG86IMG.zip.zip)
The PG86IMG.zip is either corrupt, not signed properly, or modified in some way. - Download another one.
I press Volume up to Update, and my phone shuts off
First make sure you're using a standard HTC A/C Adapter and cable. These are designed to charge at 1000 mA, other manufacturer's chargers typically only hit 900 mA. The phone needs it all to stay on and update properly without the battery in.
Second, make sure you're not using a higher end SD Card. This will draw too much power and not let the phone update when it comes to that time because the power drain to have the screen on, the sd card powered and the update running is more than what the A/C adapter can output. - My 16GB Class 10, shuts the phone off, my Class 4, 2 GB, does not. YMMV.
Third, if you're stuck with the high end SD card, or think it could be the cause, simply pull it after you pull the battery and BEFORE you press volume Up to update. The phone will still update. However, I don't know if this affects the speed of the update at all... so just watch it the first time and time it, then time your pull accordingly.
I'm getting Permission Denied when trying to run the linux commands
You don't have root, either type su or sudo -s, your prompt should have a # at the end and not a $.
Or, you didn't set the chmod correctly on the downgrade file. This is again chmod 755 downgrade (or /path/to/downgrade)
I get Misc image is missing!!! or HBOOT image is missing!!!
The hboot.img and misc.img files must be in the same location as the downgrade file, they are hard coded into the downgrade tool to be in the same location, their names are also hard coded, so don't rename them.
Whoa!
Sent from my PG86100 using xda premium
Good job man, glad to see you did it!
Erg, Why so complected! I must now download virtual machine -_-... Its ok IM SUPER EXCITED IF THIS TURNS OUT TO NOT WORK I WILL KILL something.. Great work buddy, you deserve lots of attention <3
Holy sh*t! Great job team!
Any chance of seeing a guide for a PC?
Excellent work!!
Well done everyone
I'll see about making something a little bit more automated this weekend if nobody beats me to it.
Sent from my PG86100 using xda premium
Bairdog35 said:
Erg, Why so complected! I must now download virtual machine
Click to expand...
Click to collapse
Just use a Live CD. No VM needed
saw ya guys did it on the Sensation...thanks and good job on bringing it to us 1.5 E3D users!
incredible. just incredible.
spectacular work man.
Freakin awesome work man...this is a huge accomplishment. Hopefully someone can figure out a way to do this with windows though, as I and probably many others don't have access to a linux computer.
I've been lucky enough to already have 1.40 hboot but many people with 1.50 are gonna love you for this! Great job man, this is what "true" deving is all about! Congrats
Sent from my PG86100 using xda premium
I am going to install Ubuntu and try it. It does not look like a hard job. Thanks for sharing.
Great job! I know a guy who makes awesome tools. He made one for the Evo View 4G for easy downgrade + root + ROM, it does everything. I just hit him up and asked him to check this out and see if he might be able to help this out at all.
I've been waiting for this for a while now. THANK YOU ALL AGAIN!!
Any possible way to get the phone to say "Locked" instead of "Relocked"?
All in all great work guys. I'm sure it will be less complex very shortly.
EGOvoruhk said:
Just use a Live CD. No VM needed
Click to expand...
Click to collapse
I have to use a VM, because the LIVE CD does not have the right drivers for everything to work on my computer.
/me bowing down
Have HBOOT 1.4 but you are all amazing
Hope everyone that spoke in the bounty thread pays up plus more!
Holy frakking bat-turds! Thank you from all of us living in 1.5 purgatory! This is AWESOME!
Bairdog35 said:
Erg, Why so complected! I must now download virtual machine -_-... Its ok IM SUPER EXCITED IF THIS TURNS OUT TO NOT WORK I WILL KILL something.. Great work buddy, you deserve lots of attention <3
Click to expand...
Click to collapse
Virtual machine WILL NOT work, it MUST be a native linux PC.

[Q] Please help!!!! S-off Messed phone up!

I followed the directions and now my phone is stuck in some sort of download mode. I can still get to the bootloader. I can flash through adb any recovery i want, in the recovery i can restore my rom, but here's the problem no matter what when i reboot the amaze this screen is as far as i can go. Even when i go to control bear now it won't go past the checking for device press enter to exit. I would be just happy going back to what i had just as long as i have it working again i'm puzzled. like i said i can flash any recovery i want, but it's stuck at this screen.
i downloaded the newer version of juo s-off and just ran that and this is the result:
======== ControlBear version 0.2.1 for JuopunutBear S-OFF ==========
Old beer detected...... Please wait......
Starting up......
Backing up......
Transferring backups....
Backup ok!!
Using eMMC dev /dev/block/mmcblk0
Using MMC dev /dev/block/mmcblk1
Boot partition is /dev/block/mmcblk0p22
Recovery partition is /dev/block/mmcblk0p23
Is information correct? You have 5 seconds time to press CTRL+C
Finding some beer.....
Found first....
Found second....
Found third....
Found fourth....
Hmmmm... where is that last one....... Wait a sec....
Waiting device....
Found device... Please wait...
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
** daemon still not runningerror: cannot connect to daemon
Waiting device....
** daemon still not runningerror: cannot connect to daemon
** daemon still not runningerror: cannot connect to daemon
** daemon still not runningerror: cannot connect to daemon
Found device... Please wait...
adb server is out of date. killing...
* daemon started successfully *
error: device not found
** daemon still not runningerror: cannot connect to daemon
Waiting device....
** daemon still not runningerror: cannot connect to daemon
** daemon still not runningerror: cannot connect to daemon
ADB server didn't ACK
* failed to start daemon *
error: protocol fault (no status)
ADB server didn't ACK
* failed to start daemon *
error: protocol fault (no status)
** daemon still not runningerror: cannot connect to daemon
** daemon still not runningerror: cannot connect to daemon
ADB server didn't ACK
* failed to start daemon *
error: protocol fault (no status)
it almost seem like you need to kill ADB.exe first, then update your SDK and try again.
alright i'll give that a try i hope it works lol thanx
:also one thing that i've noticed is that my dowload symbol looks different then the one in the guides. it doesn't say juop on the top of it like the other guides i've seen.
been stuck here for like 20 min:
======== ControlBear version 0.2.1 for JuopunutBear S-OFF ==========
Old beer detected...... Please wait......
Starting up......
Waiting device
Backing up......
Transferring backups....
Backup ok!!
Making room for beer......
Loading sixpacks on sdcard......
Loaded......
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Waiting device....
Found device... Please wait...
sounds like the wire trick wasnt performed right that time, just kill off the program and try again, took me like 20 tries to get it right, downside is that your stuck with the arrows until you get S-off, and dont worry, mine never said juonunput either
cool thanx that puts my mind at ease a little bit lol
so when the wire trick is done properly does it go to straight to the download thing again or to the htc thing?
It goes back to the boot logo then to the download screen. the program window should read "taking first beer, second, third, fourth, fifth, one more, that should have worked..." or something like that (don't remember what it says exactly)
Pulsewave said:
sounds like the wire trick wasnt performed right that time, just kill off the program and try again, took me like 20 tries to get it right, downside is that your stuck with the arrows until you get S-off, and dont worry, mine never said juonunput either
Click to expand...
Click to collapse
you need to finish the process to have the JB Hboot, you can do so by flashing the J_Hboot file that comes with the unlock. to flash it renamed ph85img.zip and put it on your SD then reboot to bootloader.
it also askes you at the end if ya wanna flash it, works that way too lol
when the phone restarts does it change from this instantly:
======== ControlBear version 0.2.1 for JuopunutBear S-OFF ==========
Old beer detected...... Please wait......
Starting up......
Found backups!
Making room for beer......
Loading sixpacks on sdcard......
Loaded......
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Waiting device....
Found device... Please wait...
or does it take a few minutes?
change the jb-boot.img or the jb_hboot.zip to the ph85img.zip? i tried with the zip file and it doesn't recognize it when i boot up.
dont bother with the jb_hboot.zip or image, thats only if you miss the last step, if you mess up the wire trick (it gives you a couple attempts) it'll wait for a bit then it'll reboot the phone and give you a "still sober" error after looking like its working, it even does the "first beer...." sequence, if you get the trick right the phone should reboot and show the "waiting, found device" then go into the "first beer...." sequence
at the very end itll ask you if you want to flash the jb_hboot, hit yes!
Pulsewave said:
dont bother with the jb_hboot.zip or image, thats only if you miss the last step, if you mess up the wire trick (it gives you a couple attempts) it'll wait for a bit then it'll reboot the phone and give you a "still sober" error after looking like its working, it even does the "first beer...." sequence, if you get the trick right the phone should reboot and show the "waiting, found device" then go into the "first beer...." sequence
at the very end itll ask you if you want to flash the jb_hboot, hit yes!
Click to expand...
Click to collapse
well i had trouble with the wire trick and at the end my phone got S-off but never asked me to install the JB Hboot and running control bear again didnt install the Hboot. kept telling me the phone already had S-off, thats why I flashed the Hboot that way.
---------- Post added at 05:45 PM ---------- Previous post was at 05:38 PM ----------
sonnet420 said:
change the jb-boot.img or the jb_hboot.zip to the ph85img.zip? i tried with the zip file and it doesn't recognize it when i boot up.
Click to expand...
Click to collapse
you have to reboot the phone into bootloader.
this sux it's still not working i've tried the timing tons of different ways. i've flashed two different recoveries through adb and nothing. it just doesn't want to work with me lol so they're is no way of going back then huh? i "have" to make it s-off now?
I think you have to keep going until you get the wire trick rigth.
Yup, once you start theres no going back, you have no other choice but to s-off, even using and RUU wont help...
what kind of wire are you using?
it get's stuck on like found device for like ever so i have to restart the phone and the application then it comes up with this:
======== ControlBear version 0.2.1 for JuopunutBear S-OFF ==========
Old beer detected...... Please wait......
Starting up......
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......
Let's take one more......
S-OFF Failed
Errorcode: 66732337
ErrorMsg: Still sober
Quit....
this is what it stalls on before i reset it and it looks like my last post:
======== ControlBear version 0.2.1 for JuopunutBear S-OFF ==========
Old beer detected...... Please wait......
Starting up......
Found backups!
Making room for beer......
Loading sixpacks on sdcard......
Loaded......
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Waiting device....
Found device... Please wait...
it will stay like that indefinately until i restart the phone and app. I'm using a twisted wire that is a little bigger than the wire in a bread tie. This is pissing me off. lol

ADB

I went from HC back to GB. After runing RUU i got back to stock GB. Wanted to soff and load FlyHIgh rom but....
adb does not ecognize mine device anymore.
Sometimes it does but says device offline.
most of the time it jus does not list it.
C:\android-win-tools>adb devices
List of devices attached
HT196T401151 offline
C:\android-win-tools>adb devices
List of devices attached
Any tips much apriciated.
enable usb debugging?
with it enabled yes.
Ninja edit:
lol however this wil sound stupid i had debugging on but its like Flyer wouldnt accept it.
after unpluging reenabling and repluging now i see device. wierd. but works.
Thx for a hint
Fastboot disselected under power menu?
but now..
revolutionary:
hanging here:
Beta key accepted - thank you for participating!
Zerging Root... this might take a minute or so..
for a couple of minutes
are you using the same usb port and cable you have always used? Long Shot there.
are you able to do simple adb task like reboot bootloader? May want to try and resinstall fastboot drivers on pc, or just reboot both flyer and pc.
C:\android-win-tools>adb reboot bootloader
error: protocol fault (no status)
C:\android-win-tools>
but device did rebotet into hboot
rebooted phone comp: worked well now
C:\android-win-tools>adb reboot bootloader
C:\android-win-tools>
http://forum.xda-developers.com/showthread.php?t=1194709
so i hang with revolutionary app not runing all the way. It does not hang or anything just endesly displaying message;
Beta key accepted - thank you for participating!
Zerging Root... this might take a minute or so..
rest all looks ok now; checked HBOOT its suported with 1.11.0003
This is geting much biger then me lol so ill stop until i recive help lol
Funny enought it worked with DEBUGGING - UNCHECKED. wierd but worked

[Q] Another S-OFF question, getting an RUU error?

This is where I'm stuck at. It says it was successful but it keeps saying "Hmmm, still no device
Open device manager and check adb and/or fastboot drivers!!". I'm sitting here in amon ra recovery, what should I do?
======== ControlBear 0.7 beta for JuopunutBear S-OFF ==========
Starting up......
Connecting to device...
Searching device.....
Found device.....
Found backups!
Making room for beer......
Loading sixpacks on sdcard......
Loaded......
Board vigor detected
Rebooting into fastboot!!
=== Waiting for device....
(2/45)
Fastboot detected
Do not remove sdcard from phone
Do wire-trick now!! Look instructions on the web
Waiting for device....
(6/45)
Fastboot detected
Rebooting device
Please wait....
(7/45)
Found device...
Waiting for device to settle... Please wait...
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....
(1/45)
Fastboot detected
Beer is tasty, lets take another!!
Please wait....
Found device...
Waiting for device to settle... Please wait...
Beer......more beer......more beer...
Rebooting RUU mode.......
=== Waiting for device....
(45/45)
Hmmm, still no device
Open device manager and check adb and/or fastboot drivers!!
Resetting connection....1........2....
(45/45)
Hmmm, still no device
Open device manager and check adb and/or fastboot drivers!!
Resetting connection....1........2....
(39/45)
Click to expand...
Click to collapse
apophis9283 got me all fixed, thx!
What was the solution?
neowisdom1031 said:
What was the solution?
Click to expand...
Click to collapse
It so sad for this big site which i learn too much from it... What is answer ?!
All of body know and just answer in private . so what's point ? we are here to help to ghete but ...
so . by the way please just answer the solution .... I do it 1 week and can't find any way.
i do many custom rom all of them freeze on htc not boot or just boot and camera ... phone not work....please help
iauq said:
It so sad for this big site which i learn too much from it... What is answer ?!
All of body know and just answer in private . so what's point ? we are here to help to ghete but ...
so . by the way please just answer the solution .... I do it 1 week and can't find any way.
i do many custom rom all of them freeze on htc not boot or just boot and camera ... phone not work....please help
Click to expand...
Click to collapse
Are you s-off or s-on?
If you're getting stuck on the white screen and you are s-on you need to pull the boot.img from whatever ROM you're flashing and then flash it in fastboot right after you flash the ROM.
fastboot flash boot boot.img

Categories

Resources