[Q] My flyer got Bricked i guess!!!! Help me out - HTC Flyer, EVO View 4G

Three days ago i successfully s-off my flyer and rooted it. today, i got an update and on the process of installing it, my flyer my flyer my beloved flyer quit responding. automatically shut down, restarted but stocked in this warning icon and android.. What can i do...... ? Help me out..

It is not bricked.
Long press the power button until it reboots. The update will not install if you have modified any system files.

Solved!!! Thanks a lot "Put your tablet it in recovery. By pressing down the Power button and the Vol Down button. While you have your USB plug to your PC"

You do not want to accept any OTA updates if you are rooted. You will lose root, if you do. And depending on what was updated, you may not be able to achieve root again with the present method (at least that has happened on other HTC devices).
If you want to update, the devs here will often post them in the Development section, in a pre-rooted form.

BadBoy3 said:
Today, i got an update and on the process of installing it...
Click to expand...
Click to collapse
Argn... Never, never install an update on a rooted or S-Off device!
Lucky, that HTC not also update the hboot and S-On it again. That will brick it.

Related

[Q] My HTC Hero isn't working anymore, please help

Hello Developers,
I bought a used HTC Hero Europe.
The Hero is 1,5 years old.
It worked how it should work.
When I was home after I bought it, the device asked for an update.
I installed the update, and it began updating. After it was done, the known White HTC screen showed up, and then it began.. I waited an half our but the screen stayed. I thought it was frozen, so I removed the battery and started it up again, but the same screen..
That night i put the Hero on and went to sleep. When I woke up, the battery was empty, so it didn't work.. I did the following steps:
-Volume-down button and power button, and reset the device, didn't help.
-Installed the drivers on pc, and put it in the computer via HBOOT and FASTBOOT usb, the pc saw the device (not the sd-card) but HTC Sync didn't.
-I tried to install the RUU which came from the HTC site, but that didn't work. Tried 3 others, but they didn't work either. Fail 140/141
-Tried to downgrade, but it didn't saw a number which should be shown. The solution was to reinstall the drivers but that didn't work either.
-Holding the [HOME] and [POWER] button shows a phone with a red triangle.
Please help me!
Gerjannn
Do you know if the phone was rooted beforehand or if it had a custom recovery or rom installed. And what was the update it asked you to install?
No, I don't know both of things, I can ask the guy I bought it from if it is rooted.
I'll do that today and post when he mailed back.
if rooted, flash the recovery image, wipe all and install a custom rom
if not rooted, take it to htc
Okay, well, I think my warranty is void, so I better don't bring it to HTC, or am I wrong? I don't know if it's rooted, will know it soon.
The phone never has been rooted. Is it now easier to fix the phone?
Ok, are you able to boot into fastboot?
Sent from my HTC Hero using XDA App
Yes, I am.
I tried to see the device with cmd and then type adb devices, the cmd shows the serial number of my Desire HD but the HTC Hero serial number isn't shown.. I reinstalled the drivers a few times but that didn't work.
When I pass to see the serial number I think I can downgrade it. But reinstalling the drivers doesn't help to show the serial number, anyone has an idea to fix that?
Thanks in advance.

[Q] Hard Brick evo 3D

I know there are lots of posts about bicks, but after a week searching I could not find any fix for my problem.
I have a S-Off, rooted GSM Evo 3D running Yoda ICS ROM and 4ext Recovery. One day, I was charging it when it hung, I restarted the phone, but it went directly to the bootloader (I didn't touch anything), as I was unaware of what was happening, I simply power it off (using the menu option), when I tried to power it on again, I got no success, only a dim red light appeared, and it is this way eversince.. I cannot power it on, go to the bootloader or anything, the computer recognizes it as QSUSB-DLOAD but there is no partition on it (I tried both Linux and Windows). I tried some unbricking methods without success. I am in Brazil, I tried to call HTC but they said I have to send the device to the origin country (mine is from Rogers, I believe it is Canada), but I don't even know where to send and I'd prefer to fix it by myself if possible. I am open to suggestions anyone could help?
Thanks a Lot!!
AW: [Q] Hard Brick evo 3D
Does adb detect the device?
In that case you could try to run a ruu...
If he can get it into recovery mode then yes. Most of the time its usually something that the end user has done to make it get bricked. I am not saying he actually did something. We also don't know what he has done with his . Phone changing your cid is a good way to brick it. Pulling the battery during a ruu update, flashing a CDMA firmware etc things like that are guaranteed brick makers. However there's only one solution I know of should you not be able to boot into recovery. Try and Google up JTAG. I'm fuzzy on the details about how it works but it can restore your hboot. If you know somebody that knows how to do it, that's your best shot. Otherwise, you will have to send it into HTC Canada or you could try to buy the JTAG hardware and learn how to use it to restore your phone. If anybody has a solution for him please feel free to chime in. Sorry about your phone though. I wish you the best of luck on getting it restored.
Quantenhall said:
Does adb detect the device?
In that case you could try to run a ruu...
Click to expand...
Click to collapse
No, it does not detect the phone. I was searching more thoroughly and found some places here in Brazil that do jtag repairs, I think I will give it a shot.
Thanks!
RonaldoPA said:
No, it does not detect the phone. I was searching more thoroughly and found some places here in Brazil that do jtag repairs, I think I will give it a shot.
Thanks!
Click to expand...
Click to collapse
Just to let you guys know, I did the jtag repair and it worked for about a week, I put back my cfw and yesterday, out of nothing it stopped work again. It was working normally, I left it on the table, checked the time and went do other things, later (about 2 hours) I took the phone to set the alarm for the next day and it didn't turn on...
If someone has any ideas, I appreciate!
Thanks in advance.
RonaldoPA said:
Just to let you guys know, I did the jtag repair and it worked for about a week, I put back my cfw and yesterday, out of nothing it stopped work again. It was working normally, I left it on the table, checked the time and went do other things, later (about 2 hours) I took the phone to set the alarm for the next day and it didn't turn on...
If someone has any ideas, I appreciate!
Thanks in advance.
Click to expand...
Click to collapse
Try using this to unbrick the phone (aimed specifically for DLOAD error, but has worked for other cases): http://forum.xda-developers.com/showthread.php?t=1522351. Afterward, use a combination of both the official instructions from Unlimited.io and this video tutorial to achieve S-OFF. The instructions give you an idea of how-to, the video actually gives you a better sense for the timing. The timing is very specific that needs to be done just right (might take quite a few times to get it done).
If you have an HTC Evo V 4G with Virgin Mobile USA, then you can use this flashable RUU to return to stock (I extracted this from the RUU.exe; just ensure that your bootloader is LOCKED. You can check this by Holding Pwr+Vol Down during boot; top of the screen should say LOCKED). If your phone skips loading into your bootloader and boots into the main OS, pull the battery to bypass quickboot (or turn it off in the settings). To flash the RUU, move the file to the root of your SD card, boot into bootloader, and follow the directions on screen.
brick evo 3d
when i update mwakiousSGS2rom_v.3.0.03 to my evo 3d . this is my bi mistake .and after that my mobile is of ..so pls what can i do .help me

Soft bricked HTC One, HELP PLEASE

Hi All,
I was trying to convert my ATT HTC One (Android 4.3; Hboot 1.55) to International version using the thread: [HOW TO] Convert AT&T/Rogers/T-Mobile HTC One to EU International One. (I had converted my old HTC One which I lost successfully using this thread in past.)
But when I got my new HTC One, I immediately OTA updated it to 4.3 and thus my HBoot also updated to 1.55. (I am a noob and didnt know it updated OTA will update to Hboot to 1.55 which is not compatible with revone to gain S-off. But anyways...)
So yesterday, I gained S-off using rumrunner. Had to root and install custom recovery to do that. Everything was fine until I gained S-off.
As I was S-off now, I decided to go ahead and start converting my Att HTC One to international version. So I started at Step # 4a of above mentioned thread.(I started at 4a bz steps before that are used to gain s-off using revone).
After I completed step 4a, and as menrioned in the thread, HTC One got stuck at 3/4 completed green status bar. And after that when I restarted my phone nothing is showing up. Screen is black and my computer gives me message that device connected could not be recognized. I never got the grey htc screen.
I cannot reboot into adb or recovery. if i hold the power button(10+ secs) phone vibrates. If I turn press the power button again the red led will turn on but screen is still black.
Please tell me i am not screwed and there is a way to fix this.
I really appreciate any kind of help.
You guys rock
P.S: I have searched the forum if someone has had same problem but couldnt find any, if you know any thread that already has solution to this please direct me to it.
striderr05 said:
Hi All,
I was trying to convert my ATT HTC One (Android 4.3; Hboot 1.55) to International version using the thread: [HOW TO] Convert AT&T/Rogers/T-Mobile HTC One to EU International One. (I had converted my old HTC One which I lost successfully using this thread in past.)
But when I got my new HTC One, I immediately OTA updated it to 4.3 and thus my HBoot also updated to 1.55. (I am a noob and didnt know it updated OTA will update to Hboot to 1.55 which is not compatible with revone to gain S-off. But anyways...)
So yesterday, I gained S-off using rumrunner. Had to root and install custom recovery to do that. Everything was fine until I gained S-off.
As I was S-off now, I decided to go ahead and start converting my Att HTC One to international version. So I started at Step # 4a of above mentioned thread.(I started at 4a bz steps before that are used to gain s-off using revone).
After I completed step 4a, and as menrioned in the thread, HTC One got stuck at 3/4 completed green status bar. And after that when I restarted my phone nothing is showing up. Screen is black and my computer gives me message that device connected could not be recognized. I never got the grey htc screen.
I cannot reboot into adb or recovery. if i hold the power button(10+ secs) phone vibrates. If I turn press the power button again the red led will turn on but screen is still black.
Please tell me i am not screwed and there is a way to fix this.
I really appreciate any kind of help.
You guys rock
P.S: I have searched the forum if someone has had same problem but couldnt find any, if you know any thread that already has solution to this please direct me to it.
Click to expand...
Click to collapse
Im having the same issue right not so far couldn't find a fix yet first time doing this and blamm black screen of death
x3reme85 said:
Im having the same issue right not so far couldn't find a fix yet first time doing this and blamm black screen of death
Click to expand...
Click to collapse
If your on a windows 8.1 PC what happen is the RUU downgraded your hboot and windows no longer can see the phone. Most likely your phone is not dead you just need a windows 7 PC to redo all the steps of running the RUU

Recovered my softbricked phone really easy way

Here is where I was at, ready to throw away the phone I ruined. I was rooted and S-ON and unlocked via HTC unlock bootloader web page. I was happily trying new things here when my phone went to all white background with green HTC letters. Wouldnt do anything. While trying to fix that I erased my backup and the software on the phone. I let the phone sit all day hoping the white backgound would go away but no. It wouldnt even power off. But I able to get into bootloader by doing this: Hold down power and volume up for 10 seconds, as soon as the screen goes blank slide finger down to volume down and hold. This got me into boot loader. I tried all the things outlined here to recover (using abd commands, fastboot *.img files nandroid backups, sideloading etc. My CID shows CWS_001 and next to the OS field is blank. Pulled the SIM and SD card to erase cache, no help. Wipe delvick, data, etc all failed with the E: unable to mount message. 2 Days gone by with not even a glimmer of recovering phone
So I went to HTC support download news (sorry cant post a link until 10 posts) and downloaded the RUU that contains the 4.4.3 update. This is an exe file that updates your phone. It failed on the first go. So I relocked the phone using wonders_never_cease M8 all in one kit, then double clicked on the RUU app again. It took off and ran. It is menu driven so I answered all the acknowledgements and got to the update screen. On that screen "current version field was blank and update to field reflected the new RUU version. The instructions tell you to put your phone into recovery mode and select fastboot. My Windows PC already had the HTC drivers loaded. I was shocked when the app began loading modules without failing. I didnt have to do anything except put attach usb cable to phone from PC and put the phone in fastboot. 10 mins later, the phone rebooted and my hated ATT logo and tune showed. Am up and running on 4.4.3 and new firmware.
Everything works fine on the phone (no modules missing). So it appears the "upgrade" will wipe partition and reload all the software on the phone without doing much of anything else. Thought I post this up for any other semi-noob that got into trouble and just wants a working phone. I am not sure a phone that is S-OFF would work but it doesnt hurt to try. I do understand HTC stopped the OTA update due to battery draining issues but the download is still available for fastboot. Am just happy to have a working phone. Now will make a backup in TWRP immediately. Over and out....Michael
sethandian said:
Here is where I was at, ready to throw away the phone I ruined. I was rooted and S-ON and unlocked via HTC unlock bootloader web page. I was happily trying new things here when my phone went to all white background with green HTC letters. Wouldnt do anything. While trying to fix that I erased my backup and the software on the phone. I let the phone sit all day hoping the white backgound would go away but no. It wouldnt even power off. But I able to get into bootloader by doing this: Hold down power and volume up for 10 seconds, as soon as the screen goes blank slide finger down to volume down and hold. This got me into boot loader. I tried all the things outlined here to recover (using abd commands, fastboot *.img files nandroid backups, sideloading etc. My CID shows CWS_001 and next to the OS field is blank. Pulled the SIM and SD card to erase cache, no help. Wipe delvick, data, etc all failed with the E: unable to mount message. 2 Days gone by with not even a glimmer of recovering phone
So I went to HTC support download news (sorry cant post a link until 10 posts) and downloaded the RUU that contains the 4.4.3 update. This is an exe file that updates your phone. It failed on the first go. So I relocked the phone using wonders_never_cease M8 all in one kit, then double clicked on the RUU app again. It took off and ran. It is menu driven so I answered all the acknowledgements and got to the update screen. On that screen "current version field was blank and update to field reflected the new RUU version. The instructions tell you to put your phone into recovery mode and select fastboot. My Windows PC already had the HTC drivers loaded. I was shocked when the app began loading modules without failing. I didnt have to do anything except put attach usb cable to phone from PC and put the phone in fastboot. 10 mins later, the phone rebooted and my hated ATT logo and tune showed. Am up and running on 4.4.3 and new firmware.
Everything works fine on the phone (no modules missing). So it appears the "upgrade" will wipe partition and reload all the software on the phone without doing much of anything else. Thought I post this up for any other semi-noob that got into trouble and just wants a working phone. I am not sure a phone that is S-OFF would work but it doesnt hurt to try. I do understand HTC stopped the OTA update due to battery draining issues but the download is still available for fastboot. Am just happy to have a working phone. Now will make a backup in TWRP immediately. Over and out....Michael
Click to expand...
Click to collapse
congratulations that you restore your device. the link for the RUU its already posted in the General Forum http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
also a bootable no pc version of it http://forum.xda-developers.com/att...-2-23-502-3-bootable-ruu-pc-required-t2860486
as well as the OTA http://forum.xda-developers.com/att-htc-one-m8/general/htc-m8-4-4-3-official-ota-t2860139
t5620 said:
congratulations that you restore your device. the link for the RUU its already posted in the General Forum http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
also a bootable no pc version of it http://forum.xda-developers.com/att...-2-23-502-3-bootable-ruu-pc-required-t2860486
as well as the OTA http://forum.xda-developers.com/att-htc-one-m8/general/htc-m8-4-4-3-official-ota-t2860139
Click to expand...
Click to collapse
Thanks for posting up the links.
sethandian said:
Here is where I was at, ready to throw away the phone I ruined.
Click to expand...
Click to collapse
As long as the screen comes on for this phone, its virtually always recoverable. There was never any reason to think you had to throw away the phone. Next time you are stuck, just ask for help here; as we are happy to help. You did the right thing in trying to find existing solutions. But it sounds like you did your due diligence searching and reading; and would have been justified starting a new thread and asking for help.
sethandian said:
Everything works fine on the phone (no modules missing). So it appears the "upgrade" will wipe partition and reload all the software on the phone without doing much of anything else.
Click to expand...
Click to collapse
That is precisely what the RUU does. Its a complete image, and handy for recovery purposes.
sethandian said:
I do understand HTC stopped the OTA update due to battery draining issues but the download is still available for fastboot. l
Click to expand...
Click to collapse
While the OTA has had some reports of causing battery issues, the RUU has not had any reports of such issue, and seems to be free of it.
sethandian said:
I am not sure a phone that is S-OFF would work but it doesnt hurt to try.
Click to expand...
Click to collapse
S-off does not affect whether or not the RUU will work, I don't know why folks keep saying or asking this. RUU will work whether S-on or S-off. The only difference, is that with S-on, you need to either have a LOCKED bootloader, or RELOCKED (relock it manually if you unlocked it).
Also, in general, S-off does not limit anything. It means "all security off" and enables more access, not the opposite. If anything, S-off enables more things than S-on.
Thanks for the all the info. The experience was a valuable teaching moment. Now back to playing around with the M8.

Starting to really hate EVOs, 2 Phones Bricked today

This started when my phone was acting out on Viper 4.0 rom and I figured I'd wipe it and start fresh, wiped the phone & ROM no longer booted, went to the forum to see if there is anything new to tryout & found dirty unicorn so I thought hey that's different (for me) let's give it a shot. Long story short the phone never came back until I relocked & used a factory RUU and it worked but phone was now locked & back to stock. Phone is S-Off by the way.
Today was a new day and I was determined to either get a new rom on my phone or go back to Viper 4.0, unlocked hboot & rooted the phone, installed the newest TWRP 2.8.01 and decided ok everything looks good let's see what happens, Dirty Unicorn requires that you copy ROM to internal storage then flash and this is where the first problem occurred; I couldn't mount internal storage so I thought meh I'll just boot the factory rom & connect as USB storage so I did that, back into recovery and somehow internal storage is not in either file manager or could I get to it from the install screen. I gave up & decided to go ahead & flash from Micro-SD which didn't work, tried to wipe & fail, tried to fix permissions and fail, every time I reboot it asked to reinstall supersu so I tried to flash the most recent zip I had and sure enough fail finally one of my zips worked and I hit reboot, that was the end of my phone.....
Right now - phone is completely blank, power does nothing, power+vol down does nothing, power+vol down+vol up does nothing. When I plug the phone into PC it shows up as QHSUSB_DLOAD RUU doesn't work and fastboot commands return nothing.
ummm what do I do?
oh & the second phone was a friend's phone that he gave up on gave to me to fix for him, of course that's bricked too but I have a feeling it'll come back maybe after the battery dies, haven't tried yet. But I need to get my own phone working so I can be back in business.
Whatever recommendations are welcome
Can't wait to go to Samsung lol this or something similar happens every time I try to switch or upgrade rom.
oceanisbleu said:
This started when my phone was acting out on Viper 4.0 rom and I figured I'd wipe it and start fresh, wiped the phone & ROM no longer booted, went to the forum to see if there is anything new to tryout & found dirty unicorn so I thought hey that's different (for me) let's give it a shot. Long story short the phone never came back until I relocked & used a factory RUU and it worked but phone was now locked & back to stock. Phone is S-Off by the way.
Today was a new day and I was determined to either get a new rom on my phone or go back to Viper 4.0, unlocked hboot & rooted the phone, installed the newest TWRP 2.8.01 and decided ok everything looks good let's see what happens, Dirty Unicorn requires that you copy ROM to internal storage then flash and this is where the first problem occurred; I couldn't mount internal storage so I thought meh I'll just boot the factory rom & connect as USB storage so I did that, back into recovery and somehow internal storage is not in either file manager or could I get to it from the install screen. I gave up & decided to go ahead & flash from Micro-SD which didn't work, tried to wipe & fail, tried to fix permissions and fail, every time I reboot it asked to reinstall supersu so I tried to flash the most recent zip I had and sure enough fail finally one of my zips worked and I hit reboot, that was the end of my phone.....
Right now - phone is completely blank, power does nothing, power+vol down does nothing, power+vol down+vol up does nothing. When I plug the phone into PC it shows up as QHSUSB_DLOAD RUU doesn't work and fastboot commands return nothing.
ummm what do I do?
oh & the second phone was a friend's phone that he gave up on gave to me to fix for him, of course that's bricked too but I have a feeling it'll come back maybe after the battery dies, haven't tried yet. But I need to get my own phone working so I can be back in business.
Whatever recommendations are welcome
Can't wait to go to Samsung lol this or something similar happens every time I try to switch or upgrade rom.
Click to expand...
Click to collapse
All of the things you mentioned are user error and have nothing to do with HTC or the phone itself. Now as far as an answer goes to try to get your phone working again, have you tried holding power for 60 seconds? MOD Edit: Unnecessary.
goliath714 said:
All of the things you mentioned are user error and have nothing to do with HTC or the phone itself. Now as far as an answer goes to try to get your phone working again, have you tried holding power for 60 seconds? MOD Edit: Unnecessary.
Click to expand...
Click to collapse
Yes of course I tried, the phone has been absolutely unresponsive. No amount of button holding is going to fix QHSUSB_DLOAD
Correct me if I'm wrong but http://forum.xda-developers.com/showthread.php?t=1948485 is the only known solution for QHSUSB_DLOAD due to firmware issue (I'm pretty sure this is what happened) or Jtag.
Here's the kicker, the files in that thread are no longer there so as it stands phone's just a Brick.
So for now I'm giving up on it and going samsung.
When I have the energy I may try working on the second one I have which turns out wasn't bricked instead the power button is unusable 90% of the time, but for now that's going to be left out of commission. Ultimately I need a backup because sprint techs seem to only operate on a 3 day basis when it comes to physical repairs therefore I plan to revive the second phone just to keep it as plan-b.
May all be user error but frankly what takes me minutes with a samsung seems to take days on the past couple of HTC phones I've had, so the ranting aspect of my post is merely in these regards and that only and out of frustration, this sucks because I'd take HTC build quality over samsung any day. I've been an HTC faithful since their first windows phone (5 years ago or so).
I know I have to fix the power button on the second phone but have any idea why it fails halfway through a factory RUU?
that's where I left off with it, it's S-On Unlocked running TWRP 2.8.0.1 I was trying to return it to full stock so I can have a go with facepalm S-Off procedure.
Did you relock the bootloader prior to attempting to run the RUU?
Magnum_Enforcer said:
Did you relock the bootloader prior to attempting to run the RUU?
Click to expand...
Click to collapse
out of 3 different RUUs I donwloaded only one worked, bootloader was relocked, ran RUU, Error 132 "Signature Error"
the one that did work the installer said finished, phone reboots but goes right back to bootloader where it says "Relocked" & "Security Warning" won't do anything else.

Categories

Resources