how do i get into fast boot to see if i have s-off thanxs
Pull the battery, hold volume down and power for a few seconds
The Rezound has been rooted says teamandirc it's on youtube.
Sent from my HTC
LTE 4G Rezound
I think jcase was bsing.
Sent from my Galaxy Tab 10.1
Pretty sure linking to that video means he's BSing Just a hunch
Related
Hi.
I recently got a refurbished Evo 3D after my old one's digitizer broke. About 2 days afterwards, I was being stupid and accidentally dropped my phone. The back popped off and the battery came out. Now it shows a dim red light whenever it should be charging (via usb cable into my computer) and refuses to even turn on. However, whenever I plug it in, it makes the sound that windows recognizes that a USB device is plugged in. Is this a sign of hope that I can fix my phone? Please give me any suggestions.
Things I have tried:
-Holding power down (with the volume buttons and camera button etc.)
-Trying to use the command: adb reboot bootloader
-Taking out batter and using a different one from another phone.
-Charging the original battery to full using the spare Evo 3D and then attempting the above.
Before I dropped it I did root the phone and stupidly attempted to install the wrong ROM (used CDMA instead of the other one, can't remember the name off the top of my head, but it's the one used in Rogers phones), but it didn't brick the phone or anything.
One more thing to note is that right after I dropped it and tried to boot it up it made it to the white HTC screen, then turned off.
Hopefully this is enough information, and thanks in advance for any help.
Check out the thread in the dev section about downgrading hboot 1.5 at some point in it, you purposefully brick it to a faint red light. Try to follow instructions from there.
Sent from my PG86100 using xda premium
troublein420 said:
Check out the thread in the dev section about downgrading hboot 1.5 at some point in it, you purposefully brick it to a faint red light. Try to follow instructions from there.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Any other suggestions? I don't have a linux machine, and currently my ISP is not exactly cooperating with my internet connection, so it's extremely slow atm, and as a result will probably take too long to download.
troublein420 said:
Check out the thread in the dev section about downgrading hboot 1.5 at some point in it, you purposefully brick it to a faint red light. Try to follow instructions from there.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Not to just repeat what others have said, but the dim red light truly sounds like what happens when the phone is bricked. If it is, you may be able to save it by following that thread when your ISP cooperates. It is strange though that dropping it would cause it to brick.
If he is on Rogers, he has a GSM phone & can't use the Hboot 1.50 cdma downgrade thread. There are 2 stickied downgrade threads in the Gsm section.
Sent from my PG86100 using Tapatalk
Well you know the old saying once you drop it its over or you could turn it in and get a replacement
Sent from my HTC EVO 3D X515m using xda premium
out of warranty ? =.=
just 2 days after returning
Here's what I would try
Here's what I would try:
1. Take battery out of phone and make sure, 100% sure, the phone is off.
2. Once the phone is 100% powered down pop the battery back in.
3. Now what I would do is hold down power + volume up until the phone comes to HBOOT.
4. If HBOOT doesn't come up, idk. If you have a working nandroid, I would restore from it. If you don't, just select fast boot, then select the option to start up normally (which I forget what it is called...).
-cburk
I've searched the forums and consulted Google and for the life of me cannot find anywhere how one actually figures out the HBOOT version of their HTC Flyer. I have Honeycomb, if it makes a difference.
Shut your Flyer down completely. Be sure fast Boot is turned off in the power settings from your Settings menu.
-Wait for about 10 seconds after you powered down.
-Hold the Volume Down button for about 3 seconds.
-Keep holding Volume Down and then press and hold down Power simultaneously.
-So you should be holding Volume Down and Power at the same time.
The tablet should now boot into Hboot menu.
Your Hboot should be listed near the top.
***I kinda exaggerated the wait times and time you need to hold the buttons. It really should take just a few seconds of holding the buttons. But until you get the hang of the timing, this should be fool proof.
Thanks, worked perfectly. Also, is there any sort of tutorial for using HTCdev Unlock Bootloader for the Flyer? I swear that there's no useful documentation for doing anything dev-related on this device anywhere.
what is your end goal? HTC Dev unlock is in most cases not the best solution
I'm trying to root and get S-Off on my Flyer, but revolutionary doesn't support my HBOOT. Any information I can find about doing it seems to assume that you're already an expert going in.
KalosCast said:
I'm trying to root and get S-Off on my Flyer, but revolutionary doesn't support my HBOOT. Any information I can find about doing it seems to assume that you're already an expert going in.
Click to expand...
Click to collapse
Are you on honeycomb or gingerbread
Sent from my HTC Flyer P510e using xda premium
I'm on Honeycomb.
you need to downgrade to gingerbread s off then use the s off hc method. there are a couple different routes to do so, and all do require a bit of knowledge or at least solid reading comprehension to accomplish
WTF, so about 2 hours ago my evo just crapped out. Its S-off running Flex360s 1.72 rom. I was at the store and pulled out my phone, I hit the power button and nothing would happen. When I got home I noticed its stuck at the splash screen with no backlight. Held the power button till it restarted and it would vibrate and bootloop till it eventually get stuck at the splash screen. The whole time the backlight being off. It can go to bootloader but its like frozen and even then the backlight is still off. Too bad I cant pull the battery, also it will not just turn off
Time to plug in USB and run the latest RUU for Jewel?
Sent From My S-OFFed, R00ted, 100% Tricked-Out HTC Evo 4G LTE via XDA Premium!
Similar to mine,,,
boost happy said:
WTF, so about 2 hours ago my evo just crapped out. Its S-off running Flex360s 1.72 rom. I was at the store and pulled out my phone, I hit the power button and nothing would happen. When I got home I noticed its stuck at the splash screen with no backlight. Held the power button till it restarted and it would vibrate and bootloop till it eventually get stuck at the splash screen. The whole time the backlight being off. It can go to bootloader but its like frozen and even then the backlight is still off. Too bad I cant pull the battery, also it will not just turn off
Click to expand...
Click to collapse
Mine bricked itself too...
http://forum.xda-developers.com/showthread.php?t=1800686
michael.stollaire said:
Time to plug in USB and run the latest RUU for Jewel?
Sent From My S-OFFed, R00ted, 100% Tricked-Out HTC Evo 4G LTE via XDA Premium!
Click to expand...
Click to collapse
Already tried. It basically told me to screw myself lol.
EDIT: OK I've had it connected to my computer for awhile trying to communicate through ADB. I have fail, & in another attempt to power it off, I held power down for like 3 mins straight. After releasing power it stayed off, and now I have a charging light!!! In a few I will attempt going into bootloader again
still screwed
boost happy said:
still screwed
Click to expand...
Click to collapse
May sound like a dumb question but did you have it plugged into a car charger before going into the store?
Sent from my EVO using xda premium
mcvoss said:
May sound like a dumb question but did you have it plugged into a car charger before going into the store?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
You are not actually bricked since your device turns on and shows some responsiveness when doing so (i.e. bootloader) My phone is ACTUALLY BRICKED meaning it has no response of any type whatsoever. If you can successfully boot into bootloader then you'd want to select "fastboot" then run the Jewel RUU from your PC. You'll need all the necessary fastboot drivers installed beforehand.
Can't select anything in bootloader. Its unresponsive
boost happy said:
Can't select anything in bootloader. Its unresponsive
Click to expand...
Click to collapse
Smash it, TEP time.
Sent from my EVO using xda premium
shook187 said:
Smash it, TEP time.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
yes, I feel like going out back with the phone and 1911..
I do have TEP and Best Buy black tie. I may go to best buy and see what they will do.. I just hope like hell I dont end up with the new HBOOT
boost happy said:
yes, I feel like going out back with the phone and 1911..
I do have TEP and Best Buy black tie. I may go to best buy and see what they will do.. I just hope like hell I dont end up with the new HBOOT
Click to expand...
Click to collapse
bring it to best buy, you will get a loaner phone for 3 days and then get the new one. whats nice is there people at geek squad dont know how to check if the phone is even rooted, also you get the new one before the people get the broken one.
Hey guys, quite honestly this is just a post-mortem help I felt I would want to chime in with. I just had almost a heart attack last night thinking I bricked my HTC Raider 4G / HTC Holiday / HTC Vivid / HTC Velocity 4G - Whatever you want to call it, it's the same phone. BTW, the captcha on this site and the discrimination towards new users is borderline a war crime
I want to ensure you that if you followed the whole Juopunutbear S-off bootloop / ControlBear method - your phone is NOT BRICKED. Mine wasn't, and I almost gave up on it last night. I ended up trading my HTC Raider 4G with someone for a Samsung Galaxy S III, but I wanted to touch base and just give you a heads up as to what I did (as best my memory serves me).
My situation was as follows:
1) I used the whole S-Off Toolkit By Hasoon2000 - and actually got S-Off (Security Off)
2) I followed to a tee, with all of it's "beer" references and did the whole "wire-trick" see picture below, I had to pull out my lab lamp light to see it and was getting more and more angry as the evening progressed.
3) My phone was stuck in the Juopunutbear S-Off Bootloop (or Boot Loop as some put it)
4) I could get the phone into Recovery/Fastboot (whatever you want to call it.)
Here is what I did to fix it:
1) Get yourself your OEM RUU (This is the Original Equipment Manufacturer Rom Update Utility), I hate acronyms so I will clarify as I go. You can download these at the following link (If you come back to this page a year from now and the links are broken, Google them by the exact file name, I am certain someone out there will keep backups forever. The link below surely has your carrier, e.g. Telstra etc. Follow the instructions and download your RUU for your carrier:
http://www.filefactory.com/f/002b74e0f4775869/
2) Pull the battery out of your HTC Raider / Holiday / Vivid / Velocity
3) Re-insert the battery into the phone
4) Press the volume down button + power and hold until the "Bootloader" or "Recovery" or "HBoot" or "Fastboot" screen comes up - many names for it.
5) Once the screen has come up, click on Fastboot and connect it to your computer. If it detects your computer it will say "Fastboot USB", this is good and it will look like the image at the bottom.
6) Once the phone is connected, run the specific file name for your phone based on carrier from point number 1.
7) Leave the phone plugged in and running, and it will basically flash the phone back to OEM - at least this way you can have a useable phone and will allow you to retreat/regroup and fight another day.
Fastboot USB Photo - Get your phone to look like this by going through the menus, it won't take more than 10 seconds
http://i47.tinypic.com/ru5m55.png
My Lab Setup - With The "Wire Trick" + Lamp and me getting more and more pissed off.
http://i48.tinypic.com/dyng9v.jpg
I hope this helps, I was quite honestly pulling my hair out trying to find out more information/help but it was just almost impossible to find for this phone - I think the reduced user base is partially to blame for this. My previous phone was a Samsung Galaxy S I9000 and I had absolutely no issues with support. I've learned my lesson and devices to back out, I now have a nice Samsung Galaxy S 3. If you need anything - I think you can PM me. P.S. I ran both Virtuous Inquisition ROM as well as Wajee's 1.5 and they were ok - Wajee was a bit better.
All that typing and you didn't even post for the correct device
Sent from my HTC_Amaze_4G using xda app-developers app
You could just have use the controlbear -r command..iirc
Sent from my HTC_Amaze_4G using xda app-developers app
Spastic909 said:
All that typing and you didn't even post for the correct device
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Long night, i'll be moving this. or reposting there.
ce3jay said:
You could just have use the controlbear -r command..iirc
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
I did, it did not help anything. It kept going into the Juopunutbear arrow down screen.
This is still good advice. Just needs minor tweaking for Amaze and you got yourself a deal!
Sent From My HTC Amaze 4G via Someone's Room
Hello friends and thanks for reading. Glad to finally be a part of one of the most highly respectable, trustworthy, and knowledgeable development sites on the Internet. Not an ass kisser, just feel that if you've used a website to fix or mod ALOT of different things that you didn't know how to fully do on your own, and you also learned how and why, you should express some appreciation. I've searched and searched but I'm pretty sure this is one of the more rare bricks. Not one of those did u hold volume down and OMG theres the hboot menu threads lol. So here goes...
Modification Procedure:
JuopunutBear S-Off
Hboot 1.50.5050
Radio 1.09.00.0706
Recovery TWRP v2.2.0
Angry Bean Rom CM 10.1 build 06.07.13
Joe Blow Hacks
Computer rig:
Ubuntu 12.04 x32 & Windows 8 x32 dual boot
Asus A8AE-LE
Amd Athlon 64 3500+
2gb Pc3200
Tools / Testing Equipment:
- 2 identical model Evo's
Model: PG86100
- 2 identical batteries (all working)
- Both phones have had the same exact procedure done
- The other Evo that went through the procedure is still working fine and I use it as my main phone
What it Does / Doesn't do:
- Cant get to hboot
- Cant get to recovery
- With battery in and usb charger plugged in, and not hitting any buttons including power, there is a solid red light that would indicate normal charging. I don't believe it is because the other Evo, after letting the bad one supposedly charge the battery, says the battery is low
- With the usb charger unplugged and a known charged battery placed in the phone and me hitting power once, it vibrates once and the home, menu, back and search light up. Screen shows absolutely nothing. holding volume up down and power in this state makes the phone vibrate once and all the lights go out. Then after a second adb sees it again as device offline
- When I boot using either Windows or Ubuntu, the command “adb devices” shows the serial and offline
- When I boot the working Evo using either Windows or Ubuntu, the command “adb devices” shows the serial and device (as it should)
- Adb and fastboot run fine with the working Evo
- Adb is about useless on the dead Evo. Every command = error device offline
Things I tried that failed:
- Volume up + power it vibrates once and the home, menu, back and search light up
- Volume down + power the phone doesn't boot (can't access hboot)
- Charger in the phone first with no battery. Then I held volume up and down and inserted the battery. Phone just goes back to the solid red light and gets hot. Screen shows absolutely nothing
(yes I took my time do to the fact that most problems occur do to a lack of patience and user error :silly:
- Ruu (no fastboot)
- ./brickdetect.sh Device can't be detected. Check connections
I usually got this type of thing in the bag but this time I'm just not getting anywhere. Any and all input would be greatly appreciated. Is there something not right here in this Evo setup that I'm not seeing or in your opinion do u think that the working Evo is in “harms way”? I keep wondering...Thanks
What happened to the phone before it got into its current state? Did this happen while you were doing the S-off procedure?
Sent from my Evo 3D CDMA using xda premium
The Fer-Shiz-Nizzle said:
What happened to the phone before it got into its current state? Did this happen while you were doing the S-off procedure?
Sent from my Evo 3D CDMA using xda premium
Click to expand...
Click to collapse
No thats the thing. I did both Evo procedures at the same time. Same files and everything. S-off went great for both phones. The phone was being used as a dlna client. Right before it "bricked", it was watching The Walking Dead. Would you consider this to be a brick, as i don't want to be misleading people. Theres a lotta posts that throw around bricked and hard bricked like there the same when there not...
Noxus001 said:
No thats the thing. I did both Evo procedures at the same time. Same files and everything. S-off went great for both phones. The phone was being used as a dlna client. Right before it "bricked", it was watching The Walking Dead. Would you consider this to be a brick, as i don't want to be misleading people. Theres a lotta posts that throw around bricked and hard bricked like there the same when there not...
Click to expand...
Click to collapse
I mean ya i know it's bricked lol but should it be defined as hard bricked?...
Is it getting hot around cameras while it's on charger?
If it is your motherboard died
Yes it is. Installed a a known good board inside the dead evo and I'm currently using it to post.
Sent from my Evo V 4G using xda premium
Noxus001 said:
Yes it is. Installed a a known good board inside the dead evo and I'm currently using it to post.
Sent from my Evo V 4G using xda premium
Click to expand...
Click to collapse
So it's all fine now?
Yes all is well. Thanks for all the help
Sent from my Evo V 4G using xda premium
Just a coincidence that the board died?
Noxus001 said:
Yes it is. Installed a a known good board inside the dead evo and I'm currently using it to post.
Sent from my Evo V 4G using xda premium
Click to expand...
Click to collapse
Hi everyone.
So, what do you guys think happened here? Did the motherboard just happen to die, or was its demise hastened by modifying the phone?
Good to read that you solved your problem, though. So, where did you get a replacement board, just off one of the usual sell yours buy someone else's type sites?