Related
So I bricked my phone...
I have searched around the other threads with bricked devices but none of them had that worked for me. I am rooted and unlocked so I cant flash a RUU.
I can get into bootloader, it says fastboot but when I try fastboot oem Lock or any other command it says waiting for device and doesnt seem to do anything. (I can see the bootloader screen and the red FASTBOOT sign on my phone)
I can get into my recovery (TWRP V.2.1.8.1) but my SD seems to have disappeared, it wont mount to phone and I can not see it on file manager. Which means no backups or ROMS to reinstall. It also will not mount to my PC in recovery.
Since fastboot isnt working I cant flash new boot recovery or relock bootloader. I can completely stuck
If there is a way with adb (never used it so would need more detailed instructions).
If i try boot into ROM it just shows splash then loops.
Hadcook said:
So I bricked my phone...
I have searched around the other threads with bricked devices but none of them had that worked for me. I am rooted and unlocked so I cant flash a RUU.
I can get into bootloader, it says fastboot but when I try fastboot oem Lock or any other command it says waiting for device and doesnt seem to do anything. (I can see the bootloader screen and the red FASTBOOT sign on my phone)
I can get into my recovery (TWRP V.2.1.8.1) but my SD seems to have disappeared, it wont mount to phone and I can not see it on file manager. Which means no backups or ROMS to reinstall. It also will not mount to my PC in recovery.
Since fastboot isnt working I cant flash new boot recovery or relock bootloader. I can completely stuck
If there is a way with adb (never used it so would need more detailed instructions).
If i try boot into ROM it just shows splash then loops.
Click to expand...
Click to collapse
assuming you're using Windows. Is HTC sync running? If so kill it.
If you can get to boatloader, you should be able to see the phone in windows. It's kind of a failsafe.
gunnyman said:
assuming you're using Windows. Is HTC sync running? If so kill it.
If you can get to boatloader, you should be able to see the phone in windows. It's kind of a failsafe.
Click to expand...
Click to collapse
Your a genius...
I never shut HTC sync as soon as I did that I could OEM lock and now I am running the RUU.
Thanks for the quick reply and help.
Hadcook said:
Your a genius...
I never shut HTC sync as soon as I did that I could OEM lock and now I am running the RUU.
Thanks for the quick reply and help.
Click to expand...
Click to collapse
No problemmo.
You're only bricked (as far as I know) if you can't get to the bootloader.
gunnyman said:
No problemmo.
You're only bricked (as far as I know) if you can't get to the bootloader.
Click to expand...
Click to collapse
My other one x doesn't boot. Just stays in QHSUSB :banghead: I have warranty on the way for it. Still trying to figure out how to get boot back on it
Sent from my HTC One X using xda premium
dkirchik said:
My other one x doesn't boot. Just stays in QHSUSB :banghead: I have warranty on the way for it. Still trying to figure out how to get boot back on it
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
how did it get in QHSUSB? Is what someone said about pwr/vol UP true?
dkirchik said:
My other one x doesn't boot. Just stays in QHSUSB :banghead: I have warranty on the way for it. Still trying to figure out how to get boot back on it
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Have you tried oem refurb in fastboot. I think that's the command.
Sent from my HTC One X using xda premium
kleeman7 said:
Have you tried oem refurb in fastboot. I think that's the command.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I can't boot into fastboot.
Sent from my HTC One X using xda premium
You shouldn't need to, there was a post in s-off saying it could be ran from dload mode. From what I read.
beaups said:
I tried the pg1fs. sig check failure. As a matter of fact doing "fastboot flash aksldjflkadsfjdlsk pg1fs.img" causes the same error, so something is in the img that causes sig check or any flash attempt except recovery is sig checked. Fastbook oem refurbish puts out a lot of interesting text, then reboots into recovery and looks for something (doesn't say what).on sd card (I tried copying IMG's to internal and external sd, no luck). Interesting thing about refurb command is it seems particularly "excited" about the fact that we have super CID - run it yourself and see, no harm is done (data, etc.). one recovery boots you can screw around with volume and power keys to see the text.
Click to expand...
Click to collapse
Sent from my HTC One X using xda premium
Sent from my HTC One X using xda premium
Phone is officially dead.
RUU'ed and it completed install without problems but phone still boot loops
Which RUU did you run? Did you try running it again? Can you still boot into the bootloader? If so what does it say at the top?
Sent from my HTC One X using xda app-developers app
I relocked boot loader and ran the AT&T 1.85 ruu
Basically I now have the phone booting up, but when sense loads I can do very little on it, like text or call. As soon as I try do something more like browse the web the phone freezes and reboots. The back get warm and won't turn on immediately. I want to say the second core is shorting which is why as soon as it clicks in it freezes. Or at least what my limited knowledge would suggest.
Guessing I'm done and will be using dumb phone for 6 months
The phone has a 1 year warranty call customer service and get a new one.
Doesn't the fact that I used htc dev unlock void that warranty? And I never got my phone from AT&T so they won't help obviously.
I thought that was the whole reason some people didn't want to use htc dev unlock because it voids that warranty and they won't help because the phone was rooted and boot loader unlocked? Has anyone tried to get a replacement from htc after unlocking?
You might void it says. Hardware defects are covered. AT&T covers the phone for 1 year regardless of where you bought it. Call them.
Hadcook said:
Phone is officially dead.
RUU'ed and it completed install without problems but phone still boot loops
Click to expand...
Click to collapse
reinstall STOCK recovery (unlock BL again first if needed)
relock BL if you unlocked in step 1
factory reset
RUU
profit.
beaups said:
reinstall STOCK recovery (unlock BL again first if needed)
relock BL if you unlocked in step 1
factory reset
RUU
profit.
Click to expand...
Click to collapse
Woooooaaahhhh stock recovery? Doesn't the ruu do that? If not where could I find the stock recovery?
I thought once you have ruu you can factory reset...
gunnyman said:
You might void it says. Hardware defects are covered. AT&T covers the phone for 1 year regardless of where you bought it. Call them.
Click to expand...
Click to collapse
I doubt AT&T would help, I bought the phone out of contract from best buy they would be getting screwed. I'll try contact htc after 4th of July
They will help. They take care of phone warranty for you. You still pay for service . This warranty is part of why you pay them.
ok i dont know what happened.........ive went into twrp recovery many times before!! i went to get in recovery, it wouldnt let me!!! everytime i tried....it would just sit for about 1 and a half seconds then reboot to the htc white screen with the red lettering on the bottom. like it was trying to reboot into the rom. well it wouldnt go to my current rom no matter what!!!! finally held down power untill my soft keys blinked a few times which then eventually got me into my bootloader. from there i tried rebooting into recovery with same results as before! then tried from bootloader mode to reboot into the rom.........no go!!!!!! so finally now i locked bootloader, and am running ruu!!!!! hopefully it boots up ok? ill report back with my findings! anyone see this before?
edit...........got it to boot finally!!!!!! deleted all my files!!!!!! music, pics, everything! luckily i made a backup the other day! still lost some of my files and such! damn it man! this sucks!
Another prime example of why you should always have a backup. Glad you got it unbricked though.
Sent from my HTC One X using xda premium
ECEXCURSION said:
Another prime example of why you should always have a backup. Glad you got it unbricked though.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
me 2!!!! scared me bro!!!!!!! lol!
Ok well now I tried unlocking my bootloader again, it went through fine, but I can't get a custom recovery on here? My bootloader now says
Tampered
Relocked
Any suggestions?
Sent from my HTC One X using Xparent ICS Tapatalk 2
zounduser said:
Ok well now I tried unlocking my bootloader again, it went through fine, but I can't get a custom recovery on here? My bootloader now says
Tampered
Relocked
Any suggestions?
Sent from my HTC One X using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
Need to root first??
Sent from my HTC One X using xda app-developers app
zounduser said:
Ok well now I tried unlocking my bootloader again, it went through fine, but I can't get a custom recovery on here? My bootloader now says
Tampered
Relocked
Any suggestions?
Sent from my HTC One X using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
If it says relocked, do you think you unlocked it? I'm just saying, my suggestion would be to not flash a recovery until the bootloader says unlocked. But let's see what others say.
Sent from my HTC One X using Tapatalk 2
SoberGuy said:
If it says relocked, do you think you unlocked it? I'm just saying, my suggestion would be to not flash a recovery until the bootloader says unlocked. But let's see what others say.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
yes i agree as well. however i didnt try pushing the recovery until after i ran the unlock process. im not completely dumb. lol but ya still no go ran the unlock bootloader twice with no luck.
rpomponio said:
Need to root first??
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
im rooted, with super su, as i said the unlock process went through, 2 the point where it says on screen........do you want to unlock bootloader. so basically its not sticking?
edit....after i ran the ruu, bootloader just said relocked. now it says tampered and relocked.
zounduser said:
im rooted, with super su, as i said the unlock process went through, 2 the point where it says on screen........do you want to unlock bootloader. so basically its not sticking?
edit....after i ran the ruu, bootloader just said relocked. now it says tampered and relocked.
Click to expand...
Click to collapse
Re-run the unlock but do not boot to boot loader using adb. Shut the phone off, boot to bootlader by holding vol- then run unlock again. reboot back to bootlader and check. This has been happening a lot, cant explain why but if you boot to bootlader through adb then the unlock doesnt stick a lot of times. Its happened to me on my last two phones. If you werent using ADB and it still didnt stick, just keep trying, it will work. I found the solution in the unlock bootlader thread, after 20+ tries using adb to reboot. It worked first time when i bypassed ADB. i was scared, thought HTC blocked us lol. :fingers-crossed:
nugzo said:
Re-run the unlock but do not boot to boot loader using adb. Shut the phone off, boot to bootlader by holding vol- then run unlock again. reboot back to bootlader and check. This has been happening a lot, cant explain why but if you boot to bootlader through adb then the unlock doesnt stick a lot of times. Its happened to me on my last two phones. If you werent using ADB and it still didnt stick, just keep trying, it will work. I found the solution in the unlock bootlader thread, after 20+ tries using adb to reboot. It worked first time when i bypassed ADB. i was scared, thought HTC blocked us lol. :fingers-crossed:
Click to expand...
Click to collapse
im going to try this right now
Got it!
if i boot to bootloader myself the script wont run it just hangs at restarting adb
Edit......fixed it.
Ok here's the deal. After my little experiance,had a lot of problems! Not sure what happened? But I'm not taking the risk again. I had to ruu again to get to stock, well after puting a new sim in....still fc's! Couldn't do anything with the device. So I took it in and got ANOTHER replacement, they said they have never seen anything like it?! Anyways... Mods please feel free to delete this thread! Thanks.
edit.......just so u all know this all started when trying to flash magnolia rom, i got the status 1 error, so i decided to try from cwmr touch. thats where the problem began!!!!!! so if i were users, i would stick with TWRP recovery!!!!
Hello,
I'm having trouble re-unlocking my bootloader. I relocked it to try to use the telus ruu but the ruu failed (I think because i forgot to flash the recovery) however. now I cannot unlock the bootloader. It accepts my bin but then Just keeps showing relocked and I can't flash anything....
Anyone try this or have any ideas?
I'm thinking I can't unloack the bootloader cuz I have no recovery for a factory reset and I can't flash a recovery cuz I'm relocked... Am I right? Is there anything I can do to fix this?
exad said:
Hello,
I'm having trouble re-unlocking my bootloader. I relocked it to try to use the telus ruu but the ruu failed (I think because i forgot to flash the recovery) however. now I cannot unlock the bootloader. It accepts my bin but then Just keeps showing relocked and I can't flash anything....
Anyone try this or have any ideas?
I'm thinking I can't unloack the bootloader cuz I have no recovery for a factory reset and I can't flash a recovery cuz I'm relocked... Am I right? Is there anything I can do to fix this?
Click to expand...
Click to collapse
What method are you using for the unlock key? I don"t think you can use the same key twice. Try starting the unlock process from scratch and getting a new unlock code from HTC.
exad said:
Hello,
I'm having trouble re-unlocking my bootloader. I relocked it to try to use the telus ruu but the ruu failed (I think because i forgot to flash the recovery) however. now I cannot unlock the bootloader. It accepts my bin but then Just keeps showing relocked and I can't flash anything....
Anyone try this or have any ideas?
I'm thinking I can't unloack the bootloader cuz I have no recovery for a factory reset and I can't flash a recovery cuz I'm relocked... Am I right? Is there anything I can do to fix this?
Click to expand...
Click to collapse
I managed to re-unlock it by continuously trying, powering off the phone, powered back on, eventually it re-unlocked.. I guess it's just glitchiness. In case anyone else has this issue they can reference this.
Venomtester said:
What method are you using for the unlock key? I don"t think you can use the same key twice.
Click to expand...
Click to collapse
Incorrect, you can use the same key over and over.
The process is just glitchy, as the OP has found. Sometimes the key will work on the first try, sometimes it takes 10 tries (whether unlocking the first time, or re-unlocking).
redpoint73 said:
Incorrect, you can use the same key over and over.
The process is just glitchy, as the OP has found. Sometimes the key will work on the first try, sometimes it takes 10 tries (whether unlocking the first time, or re-unlocking).
Click to expand...
Click to collapse
excuse me, is it same on all device/developer.? i'm using sony xperia Neo L (mt25i)
sorry for such noob question, i'm very new with this stuff..
SonyEricsson Xperia Neo L (MT25i)
BOOTLOADER : Locked Bootloader
ROM : Stock
maskz said:
excuse me, is it same on all device/developer.? i'm using sony xperia Neo L (mt25i)
sorry for such noob question, i'm very new with this stuff..
SonyEricsson Xperia Neo L (MT25i)
BOOTLOADER : Locked Bootloader
ROM : Stock
Click to expand...
Click to collapse
No it's not the same. This is specific to our device, you should ask in your own forum to get some help.
Sent from my Evita
maskz said:
excuse me, is it same on all device/developer.? i'm using sony xperia Neo L (mt25i)
sorry for such noob question, i'm very new with this stuff..
SonyEricsson Xperia Neo L (MT25i)
BOOTLOADER : Locked Bootloader
ROM : Stock
Click to expand...
Click to collapse
No it's not the same. HTC phone is not the same as a Sony. Go to the proper forum and ask there I dont know enough about your device to even guess.
This thread is from 1/2013......
And it's not recommended to hijack or revive an someones old thread to ask questions like this. It can lead to confusion in some cases
Sent from my HTC One XL using xda premium
Ah to see this post... How humbling..
Sent from my HTC One X using xda app-developers app
exad said:
Ah to see this post... How humbling..
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Lmao it's old as dirt
Sent from my HTC One XL using xda premium
exad said:
Ah to see this post... How humbling..
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Was thinking the same thing... I'm now looking at my old posts. Who was that noob? I mean really.
Sent from my evita
exad said:
Ah to see this post... How humbling..
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Did you ever find a good solution for this issue?
I am faced with the same issue. I restored my phone back to factory state, and relocked it, but now I've flash the Unlock file numerous times, but it still remains "RELOCKED"
Please help!
la_vengeance said:
Did you ever find a good solution for this issue?
I am faced with the same issue. I restored my phone back to factory state, and relocked it, but now I've flash the Unlock file numerous times, but it still remains "RELOCKED"
Please help!
Click to expand...
Click to collapse
Hold power until the phone shuts off, then press and hold volume down until bootloader comes up, then try again, over and over untuil it works.
It took me something like 30 tries before it worked.
exad said:
Hold power until the phone shuts off, then press and hold volume down until bootloader comes up, then try again, over and over untuil it works.
It took me something like 30 tries before it worked.
Click to expand...
Click to collapse
Thanks for the quick reply.
Oh sheesh...
Also, did you have any issues with S-OFF on the latest firmware and updates? I have tried the Facepalm S-Off method a million times and keep running into the same error. Don't know why....
What error?
Sent from my Evita
timmaaa said:
What error?
Sent from my Evita
Click to expand...
Click to collapse
It's after this step:
fastboot flash zip PJ8312000-OneX.zip
It doesn't flash the zip file properly. I was expecting that “FAILED (remote: 92 supercid! please flush image again immediately)” error as stated in instructions, but I receive an ERROR 99.
I will go home in a few minutes and try to re-unlock it again and go through the whole process. I've tried unlocking it so many times already...HTC drives me nuts.
If you get the error 99, try simulating a battery pull and start the process again.
Sent from my Evita
la_vengeance said:
It's after this step:
fastboot flash zip PJ8312000-OneX.zip
It doesn't flash the zip file properly. I was expecting that “FAILED (remote: 92 supercid! please flush image again immediately)” error as stated in instructions, but I receive an ERROR 99.
I will go home in a few minutes and try to re-unlock it again and go through the whole process. I've tried unlocking it so many times already...HTC drives me nuts.
Click to expand...
Click to collapse
Yes try again, that also takes several tries sometimes, Easiest to do on a sense rom and if you run into the issue, again the best thing to do is hold power until the phone shuts off and then try again (this simulates a battery pull).
If you have further issues, post in this thread.
exad said:
Yes try again, that also takes several tries sometimes, Easiest to do on a sense rom and if you run into the issue, again the best thing to do is hold power until the phone shuts off and then try again (this simulates a battery pull).
If you have further issues, post in this thread.
Click to expand...
Click to collapse
Alright, will continue trying to unlock and report back...
Thanks for the support BTW.
---------- Post added at 12:31 PM ---------- Previous post was at 12:15 PM ----------
exad said:
Yes try again, that also takes several tries sometimes, Easiest to do on a sense rom and if you run into the issue, again the best thing to do is hold power until the phone shuts off and then try again (this simulates a battery pull).
If you have further issues, post in this thread.
Click to expand...
Click to collapse
This worked right away! I wish I had posted before the 4 hours of trying to trouble shoot...
You're a miracle worker.
I tried S-Off and received this message at the step of entering the last 3 commands to complete S-Off..
adb shell su -c "/data/local/tmp/soffbin3"
/system/bin/sh: not found
la_vengeance said:
Alright, will continue trying to unlock and report back...
Thanks for the support BTW.
---------- Post added at 12:31 PM ---------- Previous post was at 12:15 PM ----------
This worked right away! I wish I had posted before the 4 hours of trying to trouble shoot...
You're a miracle worker.
I tried S-Off and received this message at the step of entering the last 3 commands to complete S-Off..
adb shell su -c "/data/local/tmp/soffbin3"
/system/bin/sh: not found
Click to expand...
Click to collapse
Copy/paste your CMD please, I'd like to get a good understanding.
exad said:
Copy/paste your CMD please, I'd like to get a good understanding.
Click to expand...
Click to collapse
oh! I tried one more time and it ran through all the commands without a problem!!!
Amazing..
Thanks a million man, really really appreciate it.
Is there a ROM you recommend?
I am afraid to install PA again because of it bricking my phone 2x already...the touchscreen wasnt working at all..
I'm leaning towards Carbon, CM10.1 or 10.2...
Hello guys, mainly developers and their friends who might mention my case between each other.
This is a quite big problem, so maybe these few lines below deserve a second read.
From the very beginning: I bought an XE in Europe from second hand. I was about to open the bootloader by using htcdev. As a good layman I found a useless thread which's misled me: I factory reset the phone and after that I did not enable USB Debugging. On the official htc site of unlocking bootloader I chose the option from the list, titled 'Sensation EU'. Since then I've already found out this is an Asian device (cid: ASIA-HK-CHT HTC__622), so I should have chosen 'All other supported device'. In the last step by unlocking bootloader I got a question about unlocking it, or not, whereupon I asked it to do so, causing immediate freeze on the screen.
So, this smartie is bricked now - even though I can reach the bootloader(h-boot 1.29) and the recovery(stock) too - considering the following: I can't unlock it anymore by using the right 'Unlock_code.bin' file either, since it shows me the same frozen screen after choosing 'yes' (by step 12 at htcdev). Nor I can S-OFF or accomplish the RUU procedure. At the latter I can go until it's checked the P58IMG.zip file, and asking me for applying the update. When I press vol_up the brick begins updating the bootloader and never finishes. I mean I like watching that screen for hours, colorful and I'm really obsessed with the phrase 'Updating...', but I'd still like to use this sensation for calls and things. If run the execute file(RUU) on PC, while the phone is connected via 'FASTBOOT USB' it gets stuck at 'rebooting bootloader...' In fastboot I can't even erase my cache, neither in recovery.
Do you think, it'll ever be able to use for its destiny again, if I'd follow the instructions you may give me?
Thank you very much in advance.
Post your bootloader details
Sent from my HTC Sensation 4G using xda premium
adamagic said:
Hello guys, mainly developers and their friends who might mention my case between each other.
This is a quite big problem, so maybe these few lines below deserve a second read.
From the very beginning: I bought an XE in Europe from second hand. I was about to open the bootloader by using htcdev. As a good layman I found a useless thread which's misled me: I factory reset the phone and after that I did not enable USB Debugging. On the official htc site of unlocking bootloader I chose the option from the list, titled 'Sensation EU'. Since then I've already found out this is an Asian device (cid: ASIA-HK-CHT HTC__622), so I should have chosen 'All other supported device'. In the last step by unlocking bootloader I got a question about unlocking it, or not, whereupon I asked it to do so, causing immediate freeze on the screen.
So, this smartie is bricked now - even though I can reach the bootloader(h-boot 1.29) and the recovery(stock) too - considering the following: I can't unlock it anymore by using the right 'Unlock_code.bin' file either, since it shows me the same frozen screen after choosing 'yes' (by step 12 at htcdev). Nor I can S-OFF or accomplish the RUU procedure. At the latter I can go until it's checked the P58IMG.zip file, and asking me for applying the update. When I press vol_up the brick begins updating the bootloader and never finishes. I mean I like watching that screen for hours, colorful and I'm really obsessed with the phrase 'Updating...', but I'd still like to use this sensation for calls and things. If run the execute file(RUU) on PC, while the phone is connected via 'FASTBOOT USB' it gets stuck at 'rebooting bootloader...' In fastboot I can't even erase my cache, neither in recovery.
Do you think, it'll ever be able to use for its destiny again, if I'd follow the instructions you may give me?
Thank you very much in advance.
Click to expand...
Click to collapse
bootloader details please
also does the phone fully boot up anymore? i assume not have you tried to factory reset from the stock recovery, or even hboot?
anything else you should know?
ganeshp said:
Post your bootloader details
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
heavy_metal_man said:
bootloader details please
also does the phone fully boot up anymore? i assume not have you tried to factory reset from the stock recovery, or even hboot?
Click to expand...
Click to collapse
Thanks for your response. I can't factory reset from nowhere, it causes frostbite. So the details:
H-BOOT Pyramid 1.29.0000, LOCKED, S-ON; the phone main version is 3.32.708.151
adamagic said:
Thanks for your response. I can't factory reset from nowhere, it causes frostbite. So the details:
H-BOOT Pyramid 1.29.0000, LOCKED, S-ON; the phone main version is 3.32.708.151
Click to expand...
Click to collapse
Hi,
If you can get to bootloader,you are not bricked.
adamagic said:
Thanks for your response. I can't factory reset from nowhere, it causes frostbite. So the details:
H-BOOT Pyramid 1.29.0000, LOCKED, S-ON; the phone main version is 3.32.708.151
Click to expand...
Click to collapse
Flash an ruu from the bootloader
@malybru
I lost the link to ruu.. You might have it. the v8-info (something like that) URL will have it in sensation xe section
Sent from my Nexus 7 using xda premium
ganeshp said:
Flash an ruu from the bootloader
@malybru
I lost the link to ruu.. You might have it. the v8-info (something like that) URL will have it in sensation xe section
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
do you mean this link?
http://forum.xda-developers.com/showthread.php?t=1672425
ganeshp said:
Flash an ruu from the bootloader
@malybru
I lost the link to ruu.. You might have it. the v8-info (something like that) URL will have it in sensation xe section
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hi,
THIS ONE?
rzr86 said:
do you mean this link?
http://forum.xda-developers.com/showthread.php?t=1672425
Click to expand...
Click to collapse
Not the guide
malybru said:
Hi,
THIS ONE?
Click to expand...
Click to collapse
Yes this one
Sent from my HTC Sensation 4G using xda premium
ganeshp said:
Not the guide
Yes this one
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
Thank you guys, I really appropriate your help. The only thing is when I try to run the execute file, it stops doing anything by "rebooting bootloader"... After 20 minutes the same screen, and the guide only tells me that it takes approximately 10 minutes. When I try to flash it from bootloader, I doesn't go any further then updating bootloader.
Question: the RUU on the link you post is 3.33.707. My phone is HK and not WWE, so it's 708 and not 707. In the txt the cid version is HTC__621, mine is HTC_622. Do you think is enough if I'd just write my cid number into that? I'll givi it a go anyways, but if you have any advice...
Thank guys, you're the best.
adamagic said:
Thank you guys, I really appropriate your help. The only thing is when I try to run the execute file, it stops doing anything by "rebooting bootloader"... After 20 minutes the same screen, and the guide only tells me that it takes approximately 10 minutes. When I try to flash it from bootloader, I doesn't go any further then updating bootloader.
Question: the RUU on the link you post is 3.33.707. My phone is HK and not WWE, so it's 708 and not 707. In the txt the cid version is HTC__621, mine is HTC_622. Do you think is enough if I'd just write my cid number into that? I'll givi it a go anyways, but if you have any advice...
Thank guys, you're the best.
Click to expand...
Click to collapse
Ohh then the ruu won't work and changing the cid won't help either.
Hmm we need that ruu
Otherwise try the soff without htcdev (guide link in my signature) as you can't htcdev unlock it
Sent from my Nexus 7 using xda premium
still nothing
malybru said:
Hi,
Click to expand...
Click to collapse
Yeah, thanks for the link, but it doesn't work either. I've written the 'cidnum: HTC__622' (without any spaces before and after that) into the txt, but after it's checked the P58IMG.zip doesn't ask me anything, just let me be in bootloader like I'd have started the device in bootloader mode without SD.
all right
ganeshp said:
Ohh then the ruu won't work and changing the cid won't help either.
Hmm we need that ruu
Otherwise try the soff without htcdev (guide link in my signature) as you can't htcdev unlock it
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
All right, I will try to S-OFF using your guide, but the 3rd and 4th points are not available for me. So I can only connect my phone to PC with Fastboot USB. :\ What do you think?
p.s. This is the file I could go the furthest with: RUU_PYRAMID_LE_ICS_35_S_hTC_Asia_HK_3.32.708.112_R_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_253449_signed.exe
As you see, it is still 3.32, but finally 708, but the last number from that part really makes me anxious, because it's 112, and on my phone that number is 151. I really don't want to give up, so any advice will be appropriated. (Yes, I've seen the donate me button on your profile )
adamagic said:
All right, I will try to S-OFF using your guide, but the 3rd and 4th points are not available for me. So I can only connect my phone to PC with Fastboot USB. :\ What do you think?
p.s. This is the file I could go the furthest with: RUU_PYRAMID_LE_ICS_35_S_hTC_Asia_HK_3.32.708.112_R_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_253449_signed.exe
As you see, it is still 3.32, but finally 708, but the last number from that part really makes me anxious, because it's 112, and on my phone that number is 151. I really don't want to give up, so any advice will be appropriated. (Yes, I've seen the donate me button on your profile )
Click to expand...
Click to collapse
you can try it
you don't have to lose anything at all
if it doesn't work it will just throw you an error
see how it goes
ganeshp said:
Ohh then the ruu won't work and changing the cid won't help either.
Hmm we need that ruu
Otherwise try the soff without htcdev (guide link in my signature) as you can't htcdev unlock it
Click to expand...
Click to collapse
rzr86 said:
you can try it
see how it goes
Click to expand...
Click to collapse
Well, I'm in command: "* daemon not running. starting it now on port 5037 *|* daemon started successfully *" and it's been nothing happening since I've started the method 10 min ago.
"Hmm we need that ruu" => which numbers must match you think in the name of the file? And where the hell to find? yahoo twice better than ggl, so I found the previous one I've showed you.
adamagic said:
Well, I'm in command: "* daemon not running. starting it now on port 5037 *|* daemon started successfully *" and it's been nothing happening since I've started the method 10 min ago.
"Hmm we need that ruu" => which numbers must match you think in the name of the file? And where the hell to find? yahoo twice better than ggl, so I found the previous one I've showed you.
Click to expand...
Click to collapse
Flash the ruu with phone connected from fastboot
Thats should work
Also if the ruu flashing stuck at some point.. There will be a log generated at C:/ruu post the log here (latest modified file)
Edit: btw Donate won't work for me. You can donate to devs on my behalf if you want
Sent from my Nexus 7 using xda premium
ohh yes
ganeshp said:
Flash the ruu with phone connected from fastboot
Thats should work
Also if the ruu flashing stuck at some point.. There will be a log generated at C:/ruu post the log here (latest modified file)
Edit: btw Donate won't work for me. You can donate to devs on my behalf if you want
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Some persian guy has uploaded the file I need, but unfortunately I can't register, because I can't answer the randon question during the registration process... Somebody?
http://www.fars-gsm.com/showthread.php?t=57177
So its been a while since I've been to xda so I hope I'm posting this in the right section.
Just so you know, I realize that what I did I will probably never be able to fix, I just want to make sure before I go before google on my knees and beg for mercy. I'm also aware that what I did is so stupid and unforgivable that I should never be allowed to root a device ever again. With that out of the way, here is my problem.
I just had my pixel replaced after my previous one had hardware problems, that are irreverent to this topic. I was setting it up to be my daily driver again, so I unlocked the bootloader, rooted it, loaded a few systemUI mods and the elementalx kernel. I had it working really well, but one thing was bugging me. That stupid notification that you get every time you boot up with the bootloader unlocked. I hated it. I got to thinking about it today, and I thought "Could it be possible to relock the bootloader with the changes that I made and have it still work?" I was thinking that once the mods were put in, it shouldn't matter whether or not the bootloader was unlocked or not cause the changes were already made. So I did the unthinkable and relocked my bootloader after I did all the stuff listed above.
So yes I major bricked my device by doing this, and yes I'm a major idiot for thinking that locking the bootloader was an OK thing to do. I can still get into fastboot mode, but thats it. When I try to boot into the system, it flashes the splash screen for about .5 seconds then goes black for 2 seconds then repeats. It does the same thing in recovery mode so adb side loading firmware is out of the question. I can't use fastboot boot whatever.img cause the bootloader is locked. I can't fastboot wipe userdata or mess with the system in any way via fastboot. And to top it all off, I cant reunlock the bootloader because it requires that an option be checked in the system that I now can't boot into.
This is a last ditch effort to see if I can fix this device myself, or if I need to go to google and pray they let me rma my device a second time
Any Ideas?
-MightyMouse- said:
So its been a while since I've been to xda so I hope I'm posting this in the right section.
Just so you know, I realize that what I did I will probably never be able to fix, I just want to make sure before I go before google on my knees and beg for mercy. I'm also aware that what I did is so stupid and unforgivable that I should never be allowed to root a device ever again. With that out of the way, here is my problem.
I just had my pixel replaced after my previous one had hardware problems, that are irreverent to this topic. I was setting it up to be my daily driver again, so I unlocked the bootloader, rooted it, loaded a few systemUI mods and the elementalx kernel. I had it working really well, but one thing was bugging me. That stupid notification that you get every time you boot up with the bootloader unlocked. I hated it. I got to thinking about it today, and I thought "Could it be possible to relock the bootloader with the changes that I made and have it still work?" I was thinking that once the mods were put in, it shouldn't matter whether or not the bootloader was unlocked or not cause the changes were already made. So I did the unthinkable and relocked my bootloader after I did all the stuff listed above.
So yes I major bricked my device by doing this, and yes I'm a major idiot for thinking that locking the bootloader was an OK thing to do. I can still get into fastboot mode, but thats it. When I try to boot into the system, it flashes the splash screen for about .5 seconds then goes black for 2 seconds then repeats. It does the same thing in recovery mode so adb side loading firmware is out of the question. I can't use fastboot boot whatever.img cause the bootloader is locked. I can't fastboot wipe userdata or mess with the system in any way via fastboot. And to top it all off, I cant reunlock the bootloader because it requires that an option be checked in the system that I now can't boot into.
This is a last ditch effort to see if I can fix this device myself, or if I need to go to google and pray they let me rma my device a second time
Any Ideas?
Click to expand...
Click to collapse
Well I'm not sure of this, but can't you unlock your bootloader through adb? If so then just flash the stock image.. I also saw a post somewhere about restoring your phone with a locked bootloader. Again this is just a suggestion but worth looking into.
-MightyMouse- said:
Any Ideas?
Click to expand...
Click to collapse
I'll not chastise you for what you did, I've locked the bl after making changes too although I never did care about the splash screen. I just don't look at it after a reboot, hold it until it vibrates and then log in. But I understand you not liking is since I've seen other posts about trying to get rid of it. But... your only mistake was flipping the OEM unlock switch. You could have relocked the bl with that switch still enabled and not have the splash screen any longer.
So at this point you have to beg for a replacement. I don't think they'll give you a hard time about it if you're honest as you were here. You might get some suggestions from others so good luck. You did try to factory reset in recovery right? Oh just looked and you can't get into recovery. What happens when you try from bl menu? You don't even see the android little guy saying "no command"?
quinejh said:
Well I'm not sure of this, but can't you unlock your bootloader through adb? If so then just flash the stock image.. I also saw a post somewhere about restoring your phone with a locked bootloader. Again this is just a suggestion but worth looking into.
Click to expand...
Click to collapse
Thanks for answering. I had looked into this, but the only way that you could do that is adb sideloading an ota from google. That can only be done by the recovery which is now borked.
bobby janow said:
I'll not chastise you for what you did, I've locked the bl after making changes too although I never did care about the splash screen. I just don't look at it after a reboot, hold it until it vibrates and then log in. But I understand you not liking is since I've seen other posts about trying to get rid of it. But... your only mistake was flipping the OEM unlock switch. You could have relocked the bl with that switch still enabled and not have the splash screen any longer.
So at this point you have to beg for a replacement. I don't think they'll give you a hard time about it if you're honest as you were here. You might get some suggestions from others so good luck. You did try to factory reset in recovery right? Oh just looked and you can't get into recovery. What happens when you try from bl menu? You don't even see the android little guy saying "no command"?
Click to expand...
Click to collapse
What makes me really mad is that I never disabled OEM unlock. That being said, I did see that is was disabled in settings and didn't think anything of it. I can't get into recovery at all, even through the bootloader. My guess is I borked the image that the recovery was put on as well as the system and probably a couple others. Something I know I could fix if the boot loader wasn't locked. Well I think I will get the ball rolling on an RMA then.
@-MightyMouse- When you have bootloader unlocked the option is grayed out and thereby disabled. But it does say bootloader is already unlocked so no action is needed. If you didn't switch it back over then there really is no reason that it should be disabled in the settings. When did you see it disabled if you can't get into the system? And what happens when you type the unlock command from bootloader menu? I'm locked but I think it's something like fastboot oem unlock or maybe it's changed. What does the screen say? I'm sure you tried it but I'm just curious.
bobby janow said:
@-MightyMouse- When you have bootloader unlocked the option is grayed out and thereby disabled. But it does say bootloader is already unlocked so no action is needed. If you didn't switch it back over then there really is no reason that it should be disabled in the settings. When did you see it disabled if you can't get into the system? And what happens when you type the unlock command from bootloader menu? I'm locked but I think it's something like fastboot oem unlock or maybe it's changed. What does the screen say? I'm sure you tried it but I'm just curious.
Click to expand...
Click to collapse
That was the first thing I tried. I forget what it said, but I do remember that it wouldn't let me. No matter, I already got it RMA'ed but have to wait till Monday to ship it off.
-MightyMouse- said:
That was the first thing I tried. I forget what it said, but I do remember that it wouldn't let me. No matter, I already got it RMA'ed but have to wait till Monday to ship it off.
Click to expand...
Click to collapse
Ok cool. Good luck.
Sent from my Pixel using XDA-Developers Legacy app
-MightyMouse- said:
That was the first thing I tried. I forget what it said, but I do remember that it wouldn't let me. No matter, I already got it RMA'ed but have to wait till Monday to ship it off.
Click to expand...
Click to collapse
So, what error shows up when you try - fastboot flashing unlock ?
After you somehow manage to unlock BL, you could try using the flash-all.bat script to quickly begin to push the images....
Edit: nvm. I see you have gone through a RMA again.
NoobInToto said:
So, what error shows up when you try - fastboot flashing unlock ?
After you somehow manage to unlock BL, you could try using the flash-all.bat script to quickly begin to push the images....
Edit: nvm. I see you have gone through a RMA again.
Click to expand...
Click to collapse
The error was something like option unavailable. Went through the RMA process which was surprisingly good. Every time I've gone through it, they never ask more than one or two questions before they ask for my imei and tell me that my device could be replaced, which is great, because if I can't fix it, it just needs to be replaced anyways. In other news I got my third pixel just a couple hours ago so hopefully this one lasts me longer than a day.