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
Related
I have a big problem !!! I had on my phone root s-off ROM Shooter Beats 1,7 and I flashed CWM 4.0.1.-shooteru via fastboot.
BUT when I was in fastboot USB I was thinking that I will try to have root with s-on on the screen on HBOOT. So I used command that I read in unroot section.
fastboot oem fastboot oem writesecureflag 3 and then reboot bootloader and my pfone is off and I cannot turn it on and dont know what to do :-( I am scared
you need to s-off your device again.using cmd
yes, I know, but I cannot turn on the phone.. I cannot do anything
Bricked
Sent from my HTC EVO 3D X515m using XDA App
There is nothing else to do?? :-(
What about warranty? If I cannot get to my phone, HTC cannot know if it doesnt work because of root, right? Do I have a chance?
What about a simple RUU? Just to try, and may it gives you s-on back and hboot and Kernel, so you maybe can boot into fastboot loader
Sent from my HTC EVO 3D X515m using XDA App
I cannot turn my phone on, I cannot go to bootloader, I cannot do anything. But when there is battery there is little red light on and when I remove battery it goes off. It is not blinking it is just permanent weak red colour (it is hardly to see).
When I connect Evo 3D to laptop, there is a sound that something is through USB connected, but the drivers are not regognized (in system there is only something QHUSB_DLOAD)
I was trying cmd and fastboot reboot and it is waiting for device
I was trying adb restart and nothing..
when I try RUU, it cannot find my device
Castellano2 said:
I cannot turn my phone on, I cannot go to bootloader, I cannot do anything. But when there is battery there is little red light on and when I remove battery it goes off. It is not blinking it is just permanent weak red colour (it is hardly to see).
When I connect Evo 3D to laptop, there is a sound that something is through USB connected, but the drivers are not regognized (in system there is only something QHUSB_DLOAD)
I was trying cmd and fastboot reboot and it is waiting for device
I was trying adb restart and nothing..
when I try RUU, it cannot find my device
Click to expand...
Click to collapse
try to use a RUU
If all fails send it back to HTC and say it stopped working overnight
Sent from my HTC EVO 3D X515m using XDA App
Did you have recovery? If you do, the problem you ran into might be an easy one.
1. Plug your phone to a power source (Long press the power button for few seconds and see if the light is on)
2. If the light is on, press the camera button (may be few times if first time doesn't work) and wait.
3. The first two steps should have already taken you into the boot screen. If it doesn't, then sorry.
thre3aces said:
If all fails send it back to HTC and say it stopped working overnight
Sent from my HTC EVO 3D X515m using XDA App
Click to expand...
Click to collapse
Try to push camera, volume up+down and power Buttonand hold it down for a few seconds and see if the phone boots. Then plug in charger and charge it. So you can see if the battery was dead!
Thank you guys for advices but
1, I tried use RUU and as I said it doesnt find my device (there are not drivers anymore)
2, volume plus camera button and so on.. this problem I solved many times.. it was problem with CWM 5.0.2. but I have there 4.0.1. which has no battery bug.
My phone doesnt work and cannot go on.
I googled little bit and find out that people with Desire HD had the same issue and they sent it to service and got new phone. I hope it will be the same I love my phone so muuuuuuch..
I think the problem is that I would need to get drivers for my mobile to get sdk ready.. but :/
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A
Castellano2 said:
Thank you guys for advices but
1, I tried use RUU and as I said it doesnt find my device (there are not drivers anymore)
2, volume plus camera button and so on.. this problem I solved many times.. it was problem with CWM 5.0.2. but I have there 4.0.1. which has no battery bug.
My phone doesnt work and cannot go on.
I googled little bit and find out that people with Desire HD had the same issue and they sent it to service and got new phone. I hope it will be the same I love my phone so muuuuuuch..
I think the problem is that I would need to get drivers for my mobile to get sdk ready.. but :/
Click to expand...
Click to collapse
bricked...there are a few reports here that did the same procedure and bricked it too.
I really cant understand why people play with those things although they have no idea of what they are risking.
..i mean, you could have been very proud that you got a device which csn achieve s-off. Thousands still dteaming of it.
Why the hell you wanted to went back to son and root?
If you would read through the forums you should have nitice, that you cant flash custom kernels easily - just with flash img gui. And flashing radios is
Is completly not possible with son.
Son makes life so much more painful.
And you still did it...sry tried it
Sent from my HTC EVO 3D X515m using xda premium
j4n87 said:
bricked...there are a few reports here that did the same procedure and bricked it too.
I really cant understand why people play with those things although they have no idea of what they are risking.
..i mean, you could have been very proud that you got a device which csn achieve s-off. Thousands still dteaming of it.
Why the hell you wanted to went back to son and root?
If you would read through the forums you should have nitice, that you cant flash custom kernels easily - just with flash img gui. And flashing radios is
Is completly not possible with son.
Son makes life so much more painful.
And you still did it...sry tried it
Sent from my HTC EVO 3D X515m using xda premium
Click to expand...
Click to collapse
I know, I read through forum and find out that problem with QHUSB_DLOAD is always dead end. You cannot understand why people do that? I read a lot of topic where people have written that I tried to unroot their phone because of warranty and in finally step - whitesecure flag 3 - it bricked. They do it exactly how it was in "manual", so they have just bad luck.
I want to have s-on because my cable conector was wrong and I was afraid when I won´t connect my phone to computer, I cannot remove root and my quarantee will finished.. But I didnt flash stock Rom because I want to give it on sd card and when my usb cable won´t work, I could just reflash to stock ROM from my backup..
Right now my phone is in service..
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
So i did the HTC Dev unlock with s-on then installed the team win recovery. Tried to install CM10 with no luck. Installed what i thought was a stock ROM OMJ_EVO_LTE_4.0.3_ICS_Stock_Deodexed.zip
Long story short, been running like this for a few weeks till i can rap my head around this hboot, s-on better but been getting constant lag and occasional artifacts on screen. I also can't seam to get to hboot using the power and down volume button any more. I can get to recovery view titanium backup pro but if i use team win to boot to hboot, it appears to just power off.
Any advice?
Sent from my EVO using xda app-developers app
Connect to adb and in console type adb reboot bootloader. You can also use flash image gui to flash cm10 kernel, then go to recovery and flash ROM
This I shall try. Your advice is appreciated!
Sent from my EVO using xda app-developers app
My EVO doesn't seam to have the ability to get to the bootloader at this point I can run the windows rooter, boot to recovery and install the Rom mentioned in the op. Then root may or may not work....
The screen is constantly getting curupted. The desktop will not update until I touch it again. Major ***** there. Open an ap, doesn't open, touch glass again and app opens and I'm in setting or something else so I hit home key, nothing, hit again and I'm in widgets! Took me a half-hour just to get this posted. I type a word and about 5 secondslaterit spears. Using a process monitor it looks somewhat normal with nothing running in background killing the CPU or memory.
I'm wondering if my poker accepted an ota update. There was a notice in taskbar when this crap started. I think I need to figure out how to get this back to stock.
I'm running 1.13 and tried RUU 1.13 but that crapped out after the reboot. (bootloader again!)
Sent from my EVO using xda app-developers app
Update! I ran RegawMOD EVO 4G LTE Rooter and it completed the root process. I never saw the bootloader/fastboot screen. I can use adb reboot-bootloader to reboot it into bootloader. Again, I have no screen output, it is black. Not even a glow.
So I
Have a funtional Evo 4G LTE but
1) bootloader/fastboot can be accessed via CMD/ adb reboot-bootloader AND power+VOL down and will repond to commands via command line. No display output.
2) can get to twrp 2.2 recovery via adb reboot recovery twrp screen output corrupted and difficult to use.
3) I can get to the rom but screen input is one step behind. IE Power on, in sleep with screen off.... Hit power button, display is corrupted. Slide the unlock ring and I see the unlock screen, touch the area where msg icon is and i see the home screen. touch the area where the first txt thread is and see the default txt screen. Touch where the txt box is and see the thread but the keyboard doesn't show tho it is there... (That would explain the garbled post up above lol)
I'm getting pretty good at "blind" operating this thing but dang....
So at this time, I just flashed the boot image of meanrom via flash image gui because i got fastboot unrooted again as said at the begining of this post. Currently trying to install the rom via twrp. I think. It is currently displaying the swip to flash screen. The swip bar doesn't move so I am not 100% on this yet. Might need to try again.
Does anyone know how to get hboot info via fastboot command line? (I have no screen output as I said) I want to check to see what version I am dealing with. Last post quote:I'm wondering if my poker accepted an ota update. should have been I'm wondering if my pocket accepted an ota update.
Thanks in advance!
Im hoping someone else will chime in but in the meantime, search for diagnosis on your partions, worse case get your phone into bootloader mode and RUU. It looks to me like your partitions are screwed up.
Sent from my EVO using xda app-developers app
Dude, thanks for the input. The more I worked this cell the slower it got. I did get RUU 2.13 to stick to this phone after many other RUU and resetting attempt failures. Got it back to 'broken' stock and visited Sprint.
Tech guys said that the screen is fubar, replacement time. Got to send it back, need $35 please. The way they explained it, I would give them the phone and I would get a new one in the mail in about a week or two, After fighting this thing for a week I was not ready to hear that and kinda went off on them because they couldn't release store stock. I embarrassed myself by being a total asshole and walked out with my poo evo, Sorry guys.
Today, with a few wawa gift cards (they have good coffee) I went back and apologized for my indiscretions and they did an expedited return meaning that they send a new one and then I send the broken one back. Thanks Sprint and sorry again to the the guys for my temper.
MODS, This thread can be killed.
Thanks for the help folks.
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?
I picked up an EVO 4G LTE and was going to see if I can get it set up so i can give it to my son as his first smart phone but I am unable to access the phone. The ring does not pull up to unlock the phone. I am not familiar with sense as I have been on the note until moving to the lg g2. This phone is on 4.1, 3.16.651.3 710RD. I cannot even get the unlock token for the bootloader. I have not met a phone that I have not been able to root, unlock and customize yet and THIS PHONE!!! I am looking for anyone who might know a trick because I have been searching through these forums and others(which i normally never do). Please let me know if there is a fix or if this phone is scrap. Thanks
Your screen issue sounds like a bad digitizer. As far as getting the unlock token, hit the top link in my sig and look at the links regarding how to root the device and make sure you're going through all the steps correctly.
Sent from my HTC device
Thanks, I've went through the process multiple times. I will try again. The ring moves, just does not go all the way up. If the digitizer is bad then I may be it of luck. I had read on another forum where there was the same issue and that flashing a ROM had fixed the problem. I'll look it up but I don't think I'll be able to post the link
Sent from my LG-LS980 using XDA Premium 4 mobile app
Hi you can try doing a factory reset in boot loader to see if that does anything about the lockring not going all the way up if it doesn't its the digitizer acting up
Sent from my SPH-L710 using Tapatalk