Guys, I tried to update HBOOT to 1.27 for installing ICS on my GB sensation.
I have S-OFF
CID - 11111111
Wen I updated firmware I got Bootloader update failed and phone dead.
Its not turning ON.. not even Bootloader or recovery..
Its completly dead.
Can you suggest me any procedure for this.
Is my phone bricked?
abhishek89 said:
Guys, I tried to update HBOOT to 1.27 for installing ICS on my GB sensation.
I have S-OFF
CID - 11111111
Wen I updated firmware I got Bootloader update failed and phone dead.
Its not turning ON.. not even Bootloader or recovery..
Its completly dead.
Can you suggest me any procedure for this.
Is my phone bricked?
Click to expand...
Click to collapse
It could be just out of battery, but however unless we know what you did exactly, no one can provide you with solution. What method did you use for S Off? And how did you flash 1.27 Hboot?
kgs1992 said:
It could be just out of battery, but however unless we know what you did exactly, no one can provide you with solution. What method did you use for S Off? And how did you flash 1.27 Hboot?
Click to expand...
Click to collapse
For S_OFF I used revolutionary method..
My CID was 11111111
I downloaded the firmware from ARHD thread..
First time when I updated the firmware from bootloader, everything went fine..
I was getting Recovery bootloop,
So again I went to update the same firmware from bootloader,
Everything went ok expect bootloadershowed fail-puo something.
Phone became black without power, never turned on again..
Tried many ways.. no bootloader, recovery, normal boot..
Completely dead
abhishek89 said:
For S_OFF I used revolutionary method..
My CID was 11111111
I downloaded the firmware from ARHD thread..
First time when I updated the firmware from bootloader, everything went fine..
I was getting Recovery bootloop,
So again I went to update the same firmware from bootloader,
Everything went ok expect bootloadershowed fail-puo something.
Phone became black without power, never turned on again..
Tried many ways.. no bootloader, recovery, normal boot..
Completely dead
Click to expand...
Click to collapse
Have you tried charging? removing the battery?
What happens when you connect the phone to PC?
I connected to pc.. some driver failed installed for first time.. I'm not exact about that driver.
After that it is just like dead.. no response..
Even if I put for charging, nothing happens.
Removed battery and reinserted.. tried switching on.. nothing happens..
Please help
Please email me ur number.. ill contact u.
abhishek10141 @ gmail.com
abhishek89 said:
Please email me ur number.. ill contact u.
abhishek10141 @ gmail.com
Click to expand...
Click to collapse
Leave your phone for charging overnight. Then try accessing the bootloader.
Unless the phone can be booted, there is really nothing that can be done.
Try searching for the HTC Unbricking Project if you aren't able to boot.
kgs1992 said:
Leave your phone for charging overnight. Then try accessing the bootloader.
Unless the phone can be booted, there is really nothing that can be done.
Try searching for the HTC Unbricking Project if you aren't able to boot.
Click to expand...
Click to collapse
Wen I first connected my phone via USB..
QHUSB_DLOAD driver installation failed..
Can I give my phone to service centre to repair?
kgs1992 said:
Leave your phone for charging overnight. Then try accessing the bootloader.
Unless the phone can be booted, there is really nothing that can be done.
Try searching for the HTC Unbricking Project if you aren't able to boot.
Click to expand...
Click to collapse
Can this be solved by JTAG USB?
It's a DOA claim & not a warranty claim.
But if they are able to get the phone to boot and it says S Off, I think they might ask for payment for repairs although this would be against your rights.
I'm not sure about that.
But know this for sure, unless the phone boots, or they get fastboot USB working some how, there is almost no way for them to know and they are obligated to repair/replace the phone. If this is within a month of purchase, I think they have a replacement policy.
Please check the HTC india support page & contact them.
kgs1992 said:
It's a DOA claim & not a warranty claim.
But if they are able to get the phone to boot and it says S Off, I think they might ask for payment for repairs although this would be against your rights.
I'm not sure about that.
But know this for sure, unless the phone boots, or they get fastboot USB working some how, there is almost no way for them to know and they are obligated to repair/replace the phone. If this is within a month of purchase, I think they have a replacement policy.
Please check the HTC india support page & contact them.
Click to expand...
Click to collapse
Once I had a S-OFF phone, They dint hesitated to change my motherboard for free even when they knew my phone was rooted..
Will changing motherboard solve this problem?
abhishek89 said:
Guys, I tried to update HBOOT to 1.27 for installing ICS on my GB sensation.
I have S-OFF
CID - 11111111
Wen I updated firmware I got Bootloader update failed and phone dead.
Its not turning ON.. not even Bootloader or recovery..
Its completly dead.
Can you suggest me any procedure for this.
Is my phone bricked?
Click to expand...
Click to collapse
Oh **** that happened to me but I heard the only way you get out is if you can push a Rom threw adb but I didn't try I just sold it when it was bricked LOL
Sent from my Sensation 4G
Related
Hello,
This morning I was in the market ( My Apps) and i chose Update all option. Loads of apps started to download, and after few minutes my phone froze. So i removed the battery and since then I', stuck in the bootloader menu:
AlphaRev
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-38.03.02.14_M
eMMC-boot
Mar 10 2011, 14:58:38
I can't do factory reset or access recovery. At some point I have successfully ran RUU, problem is I'm on UK O2 but being complete idiot I installed 3's ROM. Even the 3's ROM don't boot up. I can't run RUU anymore, because every time RUU is trying to reboot into boot loader it get stuck.
So,
I got phone from O2 that has a 3 logo (its stuck on it),
I have S-OFF phone so it probably voided the warranty.
Can anyone think of any solution please?
Thanks in advance for your help guys.
If you need more info please let me know.
Marcin
There are at least 5 similar topics, one is mine (same thing happened to me). Use search.
Does adb works yor you ?
yeap I have also created a topic on this.
I had to send mine back to HTC to fix.
What I would like to know is, if you send it back to HTC, would they notice the s-off and charge you money?
What ROMs were you all on? I got a similar problem on stock ROM after XTC Clip S-OFF, but a battery pull fixed it. I guess this only happens with S-OFF stock ROMs, so switch to avoid this.
No, adb doesn't see my phone....
mpolak83 said:
No, adb doesn't see my phone....
Click to expand...
Click to collapse
Remember with adb you need to be in Fastboot not Hboot! Very important. Cab you get into Fastboot?
InfernalByte said:
Remember with adb you need to be in Fastboot not Hboot! Very important. Cab you get into Fastboot?
Click to expand...
Click to collapse
When I run Adb devices it doesn't list my phone...so it doesn't work i suppose....
If I send my phone to HTC for repair will they accept it or will charge me because of S-OFF??
I just need my phone to be in the state so I can send it to HTC...I need to at least get rid off 3 logo and S-OFF...
mpolak83 said:
I just need my phone to be in the state so I can send it to HTC...I need to at least get rid off 3 logo and S-OFF...
Click to expand...
Click to collapse
Try flashing the eng hboot by PB88IMG method, and then try and run the correct RUU. That's my best idea.
InfernalByte said:
Try flashing the eng hboot by PB88IMG method, and then try and run the correct RUU. That's my best idea.
Click to expand...
Click to collapse
I have tried that, but I got the error that I can't roll back to older version of hboot.
I have just booked my phone for repair.. I'm gonna act stupid. I'll tell them that my friend installed something on my phone etc. Probably won't work... I will let you know what they said.
HTC gave me some terms and conditions to read and one of the says:
2.3 NonWarranty chargeable Repair Service
a) Repair of a Device that is
In-Warranty but which needs to be repaired including the following or similar
reasons shall be classified as a NonWarranty chargeable Repair Service:
1) Accidental damage. Accidental damage to the Device, such as dropping it
on the ground or in water. 2) Broken Liquid Crystal Display (hereinafter
known as “LCD”). 3) Damaged Sync or Charger Connector. 4) Damage
caused by liquid entering the Device, or other misuse due to the failure of the
Customer to follow the instructions properly. 5) Failure of the Customer to
upgrade the software according to the procedures outlined under the
warranty terms card of the Device. 6) Downloading illegal software onto the
Device. 7) Where the fault is caused by downloading illegal software onto the Device
or other accidental damage, the Customer shall be required to pay for spare
parts, labour, diagnosis and software refurbishment along with shipping and
handling charges.
Is S-OFF classified as illegal software?
Everything except RUU is illegal software...
Bubaaak said:
Everything except RUU is illegal software...
Click to expand...
Click to collapse
So I'm busted?
It's 50:50
Sent from my HTC Desire S using Tapatalk
Bubaaak said:
Everything except RUU is illegal software...
Click to expand...
Click to collapse
Wrong.
Its not illegal but you have probably invalidated your warranty. The thing is HTC have to bother to check your phone for custom software and a lot of the time they do.
Quick update.
I have sent my phone to HTC for repair under warranty yesterday. I have checked the status today, and it says "We are repairing your phone" So it looks like HTC don't check if the phone was rooted or have S-OFF
I've done the same i tried to flash a ruu image that was the wrong one i followed a thread on how to get s-on again just so i knew i could. I got s-on but now my phone is stuck on bootloader and is not recognised by the pc Please let me know how you get on and if you get charged as i will be doing the same i think.
InfernalByte said:
Wrong.
Its not illegal but you have probably invalidated your warranty. The thing is HTC have to bother to check your phone for custom software and a lot of the time they do.
Click to expand...
Click to collapse
Aren't custom Sense ROMs illegal ?
Coz Sense is HTC Proprietary framework.
goatimus said:
I've done the same i tried to flash a ruu image that was the wrong one i followed a thread on how to get s-on again just so i knew i could. I got s-on but now my phone is stuck on bootloader and is not recognised by the pc Please let me know how you get on and if you get charged as i will be doing the same i think.
Click to expand...
Click to collapse
You have to go to fastboot
Sent from my HTC Desire S using Tapatalk
Hey
I just got a huge bootloop while attempting to flash new Venom Room to my HTC One X. http://forum.xda-developers.com/showthread.php?t=1868236
I cannot access the recovery.. After restart (power button+volume down) i can get to bootloader section, but when i try to get into recovery, the phone just restart and stop on the white htc screen.
I already tried to reinstall recovery. Installation was successful, but the problem persists..
Before i had Incert Coins room.
The phone is unlocked, new recovery is installed
Please, help
If you had Insert Coin working on your phone, you have an international (Tegra3) version of the One X. This forum (and the Venom ROM you linked) are for the Snapdragon S3 version. Completely different hardware.
If I'm correct, you flashed a ROM for the wrong phone. Try running the RUU for your phone, but if that doesn't work you may be screwed. Recovery partitions are not the same for the versions. The ROM overwrote the recovery partition of your phone.
You are right.. It WAS the wrong rom.. I have tegra3 processor and this rom comes from american section..
But - is the RUU reinstall only one thing what i can do? I heard its dangerous
Senbration said:
But - is the RUU reinstall only one thing what i can do? I heard its dangerous
Click to expand...
Click to collapse
RUU just returns your phone to the stock condition. Stock ROM and stock recovery. There should be nothing dangerous about it. Just use the right one for your version, carrier, etc. But the CID check should ensure that you don't run the wrong RUU (if RUU is for a different CID, the RUU will not run).
Only thing with RUU, is that it wipes all user data. That may be why you heard its "dangerous". But in the condition you are in, this is not even a consideration anymore.
RUU is not dangerous, and it may be your only hope at this point.
You will need to lock your bootloader before running the RUU.
I've relocked bootloop. But now there is an information "RELOADED, Security Warning"
Will be safe to flash stock RUU now?
Senbration said:
I've relocked bootloop. But now there is an information "RELOADED, Security Warning"
Will be safe to flash stock RUU now?
Click to expand...
Click to collapse
I'm assuming you meant relocked bootloader and now has security warning relocked if this what you meant then you are fine flash the ruu
Sent from my Nocturnalized One XL using Forum Runner
Senbration said:
I've relocked bootloop. But now there is an information "RELOADED, Security Warning"
Will be safe to flash stock RUU now?
Click to expand...
Click to collapse
You mean relocked and not reloaded? If so, you should be good to run the RUU. Redpoint, sorry for highjacking your help session
Sent from my One X using xda premium
ohh, its Relocked.. Im just a bit nervous right now hoping it will unbrick this phone..
Just 3min to complete RUU download.
Do U guys think this stock RUU will rewrite the partitions back?
I've noticed another problem.
Cannot load RUU because the battery level is lower then 30%.
But when i plug the charger the light doesnt flash. It starts to flash when i switch on the phone.
Also cannot switch the phone with the power button. It restart all the time. Only can do that from bootloader command "power down". But when the phone is off the power light doesnt flash..
Does it mean that the battery is not charging at all? Because the light can flash only because the power is low..
The phone shut down completly now.. Does not charge the battery at all.. Power gone off and i cannot even turn on the phone..
Is there any solution how to make it charge?
Ok, the problem is that the wrong ROM i tried to install changed partition and also it seems it destroyed Recovery..
Without recovery the phone cannot charge while being in bootloader mode...
Is there any way to make phone charging when Recovery doesnt work and cannot be flashed?
Please help
Take the phone apart. I mean all the way spart and hardwire a charger to the phone/ battery. Its a pain but you can do it.
Ohh..
I found a treat http://forum.xda-developers.com/showthread.php?t=1658084
There is a way to charge battery by running the script, which makes phone reinstalling constantly. Each time it is reinstalled, the battery is charged a little bit more.
After mayby 40min i went up from 3686 V to 3720 V.
It seems that my only hope is to reinstall RUU. I tried to flash wrong ROM, from wrong model and as one user wrote above, it has rewritten my partition. Same time it destroyed recovery.. I cannot flash recovery now because the partition is rewritten...
And without working recovery i cannot charge the battery being in bootloader.. If i understand it all correctly.
I already tried to install RUU with 3710 V. It started to install, but stopped after few min with information that battery is too low..
So i think ill leave this script running for a whole night, and hope, in the morning battery will be charged just enough to install RUU eventually..
Uff
Okey, finally its fixed..
After 7 hours of constant reinstalling the phone by the script, the battery was loaded enough to finish RUU instalation process.. (battery went to about 3830mV power)
After oryginal RUU was installed, everything went fine.
Now i already re-unlocked the bootloader, re-rooted the phone and all works correctly.
Thanks all people who helped. Mostly to redpoint73, who diagnosed the problem straight away and put me on the right track.
Amazingly impressive to me.
Thanks for following up with your success.
WR
Sent from a CleanRom-V OneX
THAT is AWESOME
Senbration said:
Thanks all people who helped. Mostly to redpoint73, who diagnosed the problem straight away and put me on the right track.
Click to expand...
Click to collapse
Your welcome, and no problem really. It was an easy problem to recognize, as I've seen it several times before on here.
Nice job getting the phone charged. Haven't seen that solution before.
Thanks people for not calling me a noob and not blaming for installing the wrong ROM. Even though it was a silly mistake..
Sent from my HTC One X using Tapatalk 2
Senbration said:
Thanks people for not calling me a noob and not blaming for installing the wrong ROM. Even though it was a silly mistake..
Click to expand...
Click to collapse
Sh1T! Did I forget to do that???? I must have been in a good mood . . .
Heh it must have been so
Sent from my HTC One X using Tapatalk 2
All of a sudden one day I turned it on and it wouldnt go past the htc logo. It comes on, stays on the logo for a few seconds then reboots. I dont know what could have caused this but my friend had it for the day and when I got it back this started happening. I've tried turning the phone on without a simcard and memory card, fractory reseting and wiping the cache partition.
I am a newb but have gotten a reasonable amount of knowlege on android over the past 24 hours but so far none of the posts or information i've gotten on the internet has proven useful. Does anyone know of a solution or advice which may help me with booting to my os.
By the way I have an HTC sensation 4g on T-mobile
Not to sure of the version of android thou but I have a HBOOT of 1.18.
Bricked ..
phoenix220693 said:
All of a sudden one day I turned it on and it wouldnt go past the htc logo. It comes on, stays on the logo for a few seconds then reboots. I dont know what could have caused this but my friend had it for the day and when I got it back this started happening. I've tried turning the phone on without a simcard and memory card, fractory reseting and wiping the cache partition.
I am a newb but have gotten a reasonable amount of knowlege on android over the past 24 hours but so far none of the posts or information i've gotten on the internet has proven useful. Does anyone know of a solution or advice which may help me with booting to my os.
By the way I have an HTC sensation 4g on T-mobile
Not to sure of the version of android thou but I have a HBOOT of 1.18.
Click to expand...
Click to collapse
this same thing happened to me but i have the Sensation not the 4g .. but i'm sure you probably messed up in the firmware update bit .. as i remember that logo flash and restart all the time ..
follow this one, http://forum.xda-developers.com/showthread.php?t=1472298
you've got to get any files concerning the firmware you had off your sd card before you try anything else ..
and check this too: http://forum.xda-developers.com/showthread.php?t=1668276
these are all guides from zero that show you everything ..
good luck then ..
modyali88 said:
this same thing happened to me but i have the Sensation not the 4g .. but i'm sure you probably messed up in the firmware update bit .. as i remember that logo flash and restart all the time ..
follow this one, http://forum.xda-developers.com/showthread.php?t=1472298
you've got to get any files concerning the firmware you had off your sd card before you try anything else ..
and check this too: http://forum.xda-developers.com/showthread.php?t=1668276
these are all guides from zero that show you everything ..
good luck then ..
Click to expand...
Click to collapse
I tried flashing but i only got a little farther then kept restarted again. I turned it on the next morning and it wouldnt even turn on.
Need more details...
Stock?
Rooted?
S-on or s-off?
Custom recovery installed?
One thing is for sure, your phone isn't bricked and can be restored. The details of the device in the questions above are needed to determine exactly how to fix it though.
It sounds like your ROM got corrupted. (I can't even guess how) Ultimately you will be able to fix this by installing a new ROM. It's just a matter of figuring out what procedures you need to use based on your set up in order to do that.
Skipjacks said:
Need more details...
Stock?
Rooted?
S-on or s-off?
Custom recovery installed?
One thing is for sure, your phone isn't bricked and can be restored. The details of the device in the questions above are needed to determine exactly how to fix it though.
It sounds like your ROM got corrupted. (I can't even guess how) Ultimately you will be able to fix this by installing a new ROM. It's just a matter of figuring out what procedures you need to use based on your set up in order to do that.
Click to expand...
Click to collapse
It is stock, but i flashed it from gb to ics to try to resolve the problem. Rooted with htcdev, s-on. Also I installed CWM after it began to do that. I flashed a new hboot but that solved nothing, the next day it got worse and wouldn't even turn on.
phoenix220693 said:
It is stock, but i flashed it from gb to ics to try to resolve the problem. Rooted with htcdev, s-on. Also I installed CWM after it began to do that. I flashed a new hboot but that solved nothing, the next day it got worse and wouldn't even turn on.
Click to expand...
Click to collapse
you should used revolutionary.io method to S-OFF easily your device with that hboot version
that means that you have GB firmware and an ICS rom can't run in that fw version
while your are S-ON you should have installed 4ext recovery,enable smartflash from it and then flash a GB rom
after that you said you flashed a new hboot
i am not sure if you can do that as your are S-ON
and the result is not even turning on!
it seems to me that your device is bricked
use the unbricking project from dev section
edit:can you still enter to bootloader?
rzr86 said:
you should used revolutionary.io method to S-OFF easily your device with that hboot version
that means that you have GB firmware and an ICS rom can't run in that fw version
while your are S-ON you should have installed 4ext recovery,enable smartflash from it and then flash a GB rom
after that you said you flashed a new hboot
i am not sure if you can do that as your are S-ON
and the result is not even turning on!
it seems to me that your device is bricked
use the unbricking project from dev section
edit:can you still enter to bootloader?
Click to expand...
Click to collapse
I cannot use revolutionary because i get the phone to go past the htc logo. I could only get into the bootloader. I upgraded from 1.18 to 1.27 so s-on didnt matter. I tried to unbrick but it said no device found.
phoenix220693 said:
I cannot use revolutionary because i get the phone to go past the htc logo. I could only get into the bootloader. I upgraded from 1.18 to 1.27 so s-on didnt matter. I tried to unbrick but it said no device found.
Click to expand...
Click to collapse
from fastboot connect your device into the pc
go to the folder where you have adb and fastboot files
open a command window there and do
fastboot getvar version-main
i assume you have 3.32.or3.33 firmware but do it
if yes then from this thread do step 2
http://forum.xda-developers.com/showthread.php?t=1631861
after that enable smartflash from recovery and flash an ics rom
hi all,
i HAD a sensation running Android Revolution HD 6.8.0. and without checking properly, i installed AOKP-42-20130118.zip and gapps-jb-20121212-signed.zip. the phone won't boot or charge. i then realised this is not a sensation rom, it's a HTC ONE rom, i think!! . i've followed the HTC Unbricking Project and get "device not found...check connections" in ubuntu. phone shows up on windows as other device labeled QHSUSB_DLOAD. is my phone toast? sorry if all this sounds amateurish as im completely new to all this. thanks all.
thats some dangerous thing happened there ..if HTC UNBRICKING not doing any help ..then service center only
Try flashing the official RUU suitable to your device. It may recover your device
Sent from my HTC Sensation using xda app-developers app
Alsager said:
Try flashing the official RUU suitable to your device. It may recover your device
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
cant seem to connect to device to flash anything. not looking good. any ideas?
Only service center :/
miticogirl said:
Only service center :/
Click to expand...
Click to collapse
thanks all for your help. it seems i live in a country where nobody can fix my phone. i've called nearly every service center in New Zealand. it may be my only option to send this phone to my brother in the USA and get it fixed there. can anyone recommend a repair center anywhere that can fix this? Thanks again.
bensod said:
thanks all for your help. it seems i live in a country where nobody can fix my phone. i've called nearly every service center in New Zealand. it may be my only option to send this phone to my brother in the USA and get it fixed there. can anyone recommend a repair center anywhere that can fix this? Thanks again.
Click to expand...
Click to collapse
have you:
1. installed the HTC drivers
2. put the device in "bootloader mode" when trying to flash the RUU,
3.uninstalled the HTC sync program,
4. used the original USB cable
sorry for very late response.
Alsager said:
have you:
1. installed the HTC drivers
2. put the device in "bootloader mode" when trying to flash the RUU,
3.uninstalled the HTC sync program,
4. used the original USB cable
sorry for very late response.
Click to expand...
Click to collapse
no worries, thanks for answering.
yes tried all of the above, several times. tried newest drivers, and 3.0.0.007, messed around with several usb cables, changed computers. device not found error every time. i think the phone is stuffed. will send it to mobiletechvideos in Texas. it's a 50 dollar repair. will be a bit more careful next time.
bensod said:
no worries, thanks for answering.
yes tried all of the above, several times. tried newest drivers, and 3.0.0.007, messed around with several usb cables, changed computers. device not found error every time. i think the phone is stuffed. will send it to mobiletechvideos in Texas. it's a 50 dollar repair. will be a bit more careful next time.
Click to expand...
Click to collapse
What?
You can boot the phone up to boot loader?
Then did you try flashing a ruu?
Can you post the boot loader details?
Sent from my Nexus 7 using xda premium
ganeshp said:
What?
You can boot the phone up to boot loader?
Then did you try flashing a ruu?
Can you post the boot loader details?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
no, can not boot phone. phone is dead boot bricked.
found a place to fix it but it's not cheap. thanks all for your help.
ganeshp said:
What?
You can boot the phone up to boot loader?
Then did you try flashing a ruu?
Can you post the boot loader details?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
hi, my phone has been recovered and back working. service centre returned the phone with locked bootloader, s-off and hboot 1.29.
i'd like to get back to Android Revolution HD 6.8.0, can i just root and flash a recovery, or have i to unlock the bootloader again on htv dev? can i use the backups i made earlier on hboot 1.27?
thanks again.
bensod said:
hi, my phone has been recovered and back working. service centre returned the phone with locked bootloader, s-off and hboot 1.29.
i'd like to get back to Android Revolution HD 6.8.0, can i just root and flash a recovery, or have i to unlock the bootloader again on htv dev? can i use the backups i made earlier on hboot 1.27?
thanks again.
Click to expand...
Click to collapse
you received the phone with LOCKED bootloader and SOFF ?
then before doing anything ..i would suggest you to ..check whether the phone is soff or not (I've seen 3 cases at-least where the phone showed soff (after the phone got back from service center) but its not actually soff and people bricked their phone again trying to flash stuff) ... to check soff status go to my soff guide (link in my signature)..try the controlbear soff NO HTC_DEV unlock one ..if the phone is properly soff then the controlbear says soff and exits ..otherwise your phone is not soff ..
also you cant do HTC-DEV unlock (motherboard got replaced so IMEI changed) as IMEI changed and the unlock procedure fails ..the only way is JB SOFF
ganeshp said:
you received the phone with LOCKED bootloader and SOFF ?
then before doing anything ..i would suggest you to ..check whether the phone is soff or not (I've seen 3 cases at-least where the phone showed soff (after the phone got back from service center) but its not actually soff and people bricked their phone again trying to flash stuff) ... to check soff status go to my soff guide (link in my signature)..try the controlbear soff NO HTC_DEV unlock one ..if the phone is properly soff then the controlbear says soff and exits ..otherwise your phone is not soff ..
also you cant do HTC-DEV unlock (motherboard got replaced so IMEI changed) as IMEI changed and the unlock procedure fails ..the only way is JB SOFF
Click to expand...
Click to collapse
hi again, thanks for the heads up. i've run controlbear and confirmed the phone is s-off. during the process it asked to install modified juopunutbear hboot, which i said no. should i have? also phone imei is same as before (no motherboard replacement) so whats my next move, i'm a little cautious as I've bricked phone already once!! thanks ganeshp.
bensod said:
hi again, thanks for the heads up. i've run controlbear and confirmed the phone is s-off. during the process it asked to install modified juopunutbear hboot, which i said no. should i have? also phone imei is same as before (no motherboard replacement) so whats my next move, i'm a little cautious as I've bricked phone already once!! thanks ganeshp.
Click to expand...
Click to collapse
yes install juopunutbear hboot via controlbear and if that didnt went successfully ..install patched revoultionary hboot (at the end of first post i think) from kohr-ah firmware thread present in sensation development section.
then you cna continue with custom recovery flashing and then custom rom (if you want you can backup your current stock rom too from the custom recovery before trying the new rom )
ganeshp said:
yes install juopunutbear hboot via controlbear and if that didnt went successfully ..install patched revoultionary hboot (at the end of first post i think) from kohr-ah firmware thread present in sensation development section.
then you cna continue with custom recovery flashing and then custom rom (if you want you can backup your current stock rom too from the custom recovery before trying the new rom )
Click to expand...
Click to collapse
hey thanks for all your help. i'm back to where i was before all the drama. one last thing, is there a rom out there that's pure android? no sense? one you would recommend? thanks again for your help.
bensod said:
hey thanks for all your help. i'm back to where i was before all the drama. one last thing, is there a rom out there that's pure android? no sense? one you would recommend? thanks again for your help.
Click to expand...
Click to collapse
cm 10.1 of albioman ?
the latest one is pretty stable
So I just got my phone back working properly by flashing a Ruu for a previous problem. I was notified of the Jellybean update and proceeded to download it.. Everything was going fine when it came down to installation, but all of a sudden the phone went black and will not turn back on. It had a full charge on it,so Idk whats the problem.. Any suggestions ???
Let me guess: You were rooted and had superCID?
Sent from my Nexus 7 using Tapatalk HD
Should have read this first:
http://forum.xda-developers.com/showthread.php?t=2181929
Sent from my One X using Tapatalk 2
No, I don't have neither..
iElvis said:
Let me guess: You were rooted and had superCID?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
the whole process took awhile for me, felt like it rebooted a few times also. about 20 minutes i think, you could of got in a hurry during the process and messed it up. does the phone detect? maybe u can reruu?
Have you tried holding the power button down for a while (like 30 secs)? You can't get into bootloader via power+vol down? What happens when you plug into your computer? What do you see in Device Manager?
Bricks on stock phones from borked otas are not common, but they do happen. If so, AT&T is good about replacements.
If the charge LED does not come on when charging (use the wall charger, not USB), and the screen doesn't come on at all after charging overnight, the phone is probably not recoverable.
As iElvis mentioned, bricks caused be the OTA aren't common, but they do happen. For one thing, the OTA flashes a new hboot. So if something goes wrong during that process, it may brick the phone. If you are bone stock, its the fault of the update, so AT&T will replace it.
The LED does not come on, believe me I have tried keeping it on the charger all night, with no success.
redpoint73 said:
If the charge LED does not come on when charging (use the wall charger, not USB), and the screen doesn't come on at all after charging overnight, the phone is probably not recoverable.
As iElvis mentioned, bricks caused be the OTA aren't common, but they do happen. For one thing, the OTA flashes a new hboot. So if something goes wrong during that process, it may brick the phone. If you are bone stock, its the fault of the update, so AT&T will replace it.
Click to expand...
Click to collapse
I tried this, and nothing happened.. I will head to my nearest AT&T store soon to get a replacement hopefully.. I guess its not all bad though, I have been enjoying my Lumia 920 with Windows phone 8, but I am missing my Android!
iElvis said:
Have you tried holding the power button down for a while (like 30 secs)? You can't get into bootloader via power+vol down? What happens when you plug into your computer? What do you see in Device Manager?
Bricks on stock phones from borked otas are not common, but they do happen. If so, AT&T is good about replacements.
Click to expand...
Click to collapse
hrrsncrawford14 said:
So I just got my phone back working properly by flashing a Ruu for a previous problem. I was notified of the Jellybean update and proceeded to download it.. Everything was going fine when it came down to installation, but all of a sudden the phone went black and will not turn back on. It had a full charge on it,so Idk whats the problem.. Any suggestions ???
Click to expand...
Click to collapse
I am having the same problem, just updated using 3.18 ruu and the phone went blank it detects as Qhsusb_dload and the ruu doesn't detect anymore
nmupparaju said:
I am having the same problem, just updated using 3.18 ruu and the phone went blank it detects as Qhsusb_dload and the ruu doesn't detect anymore
Click to expand...
Click to collapse
Did you have SuperCID? S-on?
The OP is talking about updating via OTA, which is known to brick your phone if you have SuperCID and S-on. But I was wondering what would happen with the RUU, which was just posted by HTC a couple days ago.
redpoint73 said:
Did you have SuperCID? S-on?
The OP is talking about updating via OTA, which is known to brick your phone if you have SuperCID and S-on. But I was wondering what would happen with the RUU, which was just posted by HTC a couple days ago.
Click to expand...
Click to collapse
I'm sure it's the same thing.
redpoint73 said:
Did you have SuperCID? S-on?
The OP is talking about updating via OTA, which is known to brick your phone if you have SuperCID and S-on. But I was wondering what would happen with the RUU, which was just posted by HTC a couple days ago.
Click to expand...
Click to collapse
I did get supercid, unlocked bootloader installed cm10 relocked bootloader, ruu to 2.20 used for few days, used update tool from htc website to update to jellybean, after using the tool phone never booted back , dead (I guess brick)
When connected to windows pc qhusb_dload shows up
nmupparaju said:
When connected to windows pc qhusb_dload shows up
Click to expand...
Click to collapse
You've got a brick. Sorry. It's not clear why this is happening, but once you're in that mode, you're done.