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
Related
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
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
hi guys first of all thanks for all the great work and help for all android users !
ok i guys i got a problem i bricked my phone trying to get s off via lazy panda so today ive been working on my phone all day whit no luck i install ubuntu 32 bit i followed dis guide in dis threat http://forum.xda-developers.com/showthread.php?t=1737123&page=110 post #1099 and everything was goin fine in terminal but it gets stuck here dis how it stays stuck
Bricked device will appear to device node /dev/sdf
ARE YOU SURE?
CTRL+C if not, ENTER to continue
Realnode is /dev/sdf12
Ready to go.
(1) Remove MicroSD card from phone
(2) Connect bricked EVO 4G LTE to usb
Press ENTER when ready
*** Do NOT remove usb cable during process
*** Do NOT press any buttons until PandaFinder requests you to do that!!
******** Press ENTER when you understand this!! Really ********
Lets try unbricking once, before we run it really
Press ENTER to start test
Waiting for device. - found /dev/ttyUSB1 - OK
Waiting device /dev/sdf12.......
its just stuck their no matter how many time i try again thats as far as i get can somebody help me out please sorry for my bad spelling and thanks in advance :fingers-crossed:
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
Okay, here is my problem. First off I am stuck at the HTC quietly brilliant boot screen after I successfully unlocked the bootloader. Then I tried to root the device with rootbootv5 and as i was following the instructions it was trying to backup the phone and got stuck "waiting for the device". Now my computer does not recognize the phone and when i try to factory reset it just goes back to being stuck.
Also when I go into HBOOT it is stuck "checking SD card update" until i unplug the usb cord. When entering recover from HBOOT it just goes to a triangle with a exclamation mark.. This is a AT&T phone if that matters as I have already done some research and it seems it might.. Just got this awesome phone today and I would like to fix this problem if anyone could help I would appreciate it.
treefetty said:
Okay, here is my problem. First off I am stuck at the HTC quietly brilliant boot screen after I successfully unlocked the bootloader. Then I tried to root the device with rootbootv5 and as i was following the instructions it was trying to backup the phone and got stuck "waiting for the device". Now my computer does not recognize the phone and when i try to factory reset it just goes back to being stuck.
Also when I go into HBOOT it is stuck "checking SD card update" until i unplug the usb cord. When entering recover from HBOOT it just goes to a triangle with a exclamation mark.. This is a AT&T phone if that matters as I have already done some research and it seems it might.. Just got this awesome phone today and I would like to fix this problem if anyone could help I would appreciate it.
Click to expand...
Click to collapse
I am almost positive "rootboot" is not for the AT&T phone. Even if it is I would strongly suggest avoiding it. Try relocking the bootloader and running the RUU
Forgot to mention
Forgot to mention after the other actions I tried to use X-Factor to root the device and it said something to the extent that maybe adb was out of date and something about the CID sorry I am not very knowledgeable about this stuff guys..
X factor is for a completely different device, it does a temp root then supercids the device (HTC one xl)
Why don't you just unlock the boot loader and flash a recovery?
Slithered from my HTC One X+
Kraizk said:
I am almost positive "rootboot" is not for the AT&T phone. Even if it is I would strongly suggest avoiding it. Try relocking the bootloader and running the RUU
Click to expand...
Click to collapse
Thank you very much for the reply,
How do i relock the bootloader and I dont even know what a RUU is :/.
the computer wont even recognize the phone, if i try something it just says "waiting on device"
Ugh why did I try this lol.. Still having problems. I restarted my computer and that fixed the problem "waiting for device" now in cmd it will at least recognize the phone BUT, I get this trying to figure out some information
getvar:cid FAILED (command write failed (unknown error))
treefetty said:
Ugh why did I try this lol.. Still having problems. I restarted my computer and that fixed the problem "waiting for device" now in cmd it will at least recognize the phone BUT, I get this trying to figure out some information
getvar:cid FAILED (command write failed (unknown error))
Click to expand...
Click to collapse
fastboot oem lock to lock bootloader.
search the forums for the HTC ONE X+ RUU for AT&T It is a .exe file. Put phone in boot loader and run it.
Finally found it after searching through google here:
http://forum.xda-developers.com/showthread.php?p=34744228&posted=1#post34744228
I am not sure what to do after I've downloaded it. Is there some code I put in when I am in cmd and fastboot? or just run the RUU exe when the phone is in fastboot? I am out of me league, and everything was going so well with the bootloader unlock...
Thanks to all who are helping me!! :good:
treefetty said:
Finally found it after searching through google here:
http://forum.xda-developers.com/showthread.php?p=34744228&posted=1#post34744228
I am not sure what to do after I've downloaded it. Is there some code I put in when I am in cmd and fastboot? or just run the RUU exe when the phone is in fastboot? I am out of me league, and everything was going so well with the bootloader unlock...
Thanks to all who are helping me!! :good:
Click to expand...
Click to collapse
Lock the boot loader using the fastboot command from my previous post. stay in bootloader and run the htc ruu (double click) while the phone is plugged in. This will hopefully revert your phone to stock.
**THE PHONE WILL REBOOT SEVERAL TIMES. LET IT. THIS IS NORMAL. DO NOT UNDER ANY CIRCUMSTANCES UNPLUG IT**
I'll just leave this here.
http://forum.xda-developers.com/showthread.php?t=2066390
Thanks
Okay I got it to work following your instructions. Thanks so much. Normally I can figure this stuff out by goggling but I was stumped last night and freaking out! lol Thanks again.
PS. Can my At&t hox+ even be rooted? My original goal was to root the device so that I would find a workaround At&t's wifi tether subscription that apparently they make you pay for.
treefetty said:
Okay I got it to work following your instructions. Thanks so much. Normally I can figure this stuff out by goggling but I was stumped last night and freaking out! lol Thanks again.
PS. Can my At&t hox+ even be rooted? My original goal was to root the device so that I would find a workaround At&t's wifi tether subscription that apparently they make you pay for.
Click to expand...
Click to collapse
It certainly can be rooted, just check out the link Hasoon posted before your post.
Yes it can be rooted and is fairly simple. I would avoid the tool kit and just flash the recovery yourself ans then the super user zip file.
Sent from my HTC One X+ using xda premium
Also please keep in mind all this stuff- roms, kernels, recoveries are very device specific. Do not flash anything that does not explicitly state it is for the AT&T One x+.