Related
First of all thanks for this great forum !!!!
This will be my first post. I have to thank all developers to get the sensation s-off.
I made a stupid mistake with the eng hboot. I played a little round and typed
"fastboot oem fdisk erase_emmc.
Now Phone is completly dead and bricked. Can not power on and no charging.
But it must be possible to bring the sensation back to life. I downloades QPST an drivers and see, that the device is in download mode.
I tried cdma workshop and DFS CDMA Tool too.
Can somebody make a dump with QPST and backuo the nv file and firmware image to unbrick the sensation.
Please no commands why I have done this. I said it before. I have no second sensation to try it by myself.
Has anyone an idea ??? (without to send it back or jtag flash)
Thank you for any help.
Kindly regards Woody01
Sorry for bad English
Send me the commands and i do it for you!
No comment on what you have done
I'm sorry man, but we can't help you. Once you erase something like that, it's over for that device. If i'm reading correctly, the internal sd card is completely wiped, no recovery, no HBOOT, no / (original mount point). The thing that bothers me, if you didn't know what it did, why would you run that command? That is idiocy at it's finest. The only thing you could do is send it back for a warranty replacement, since it's bricked like that, they won't able to tell you ever rooted or flashed anything. If you do send it back, play dumb, say you woke up one day after charging it all night and it just wouldn't turn on any longer. Once you get your replacement, do not install the ENG HBOOT, it isn't for noobs for this exact reason.
Download mode could be a mode where it wait for flash ... keep it off until someone comes with ideas....
Thank you for your answers but I expectet such replies.
It must be possible to bring it back. In QPST you have the ability to flash back the Multi-Image file. But i am missing the the phon image hex and boot hex. I think if someone make a backup from the Multi-Backup and NV file we could unbrick it.
For the Galaxy S someone wrote at tool (One click unbrick). There will be everything restored. (partition, boot, etc).
Is someone interestet to help me trying this ????
Kindly regard Woody01
I say again tell me how i do it .... backing up should be no problem for a device
@xtcislove
First of all you must dwonload QPST (I found it by google). I have version 2.7 buil 355.
You need the QHSUSB Drivers. I found the drivers on google. I think the phone must be in diag mode. Use QPST Software download. There is an option backup. There you can backup the firmware. It will be restored as an qcn file.
To restore the NV File you can try DFS CDMA Tool. There is an option to read the NV file. At that point I could write the file from Wildfire. I could delete it too. I used the free version 3.2.0.0
For Diag mode you need the HTC Diag driver.
It is possible for me to upload these files here in forum and is it allowed ???.
Thank you
Be careful with the NV file. There is your imei and serial number. It would be nice if someone send the file with edited imei and serial.
I need the hex files for QPST. Some wrote in the www something about CDMA-Workshop to get the hex dump.
Kindly regards Woody01
Sry i cant edit my imei etc out ...
and with 3 posts i dont trust you really ... sry i think u should ifnd someone
@ xtcislove
I understand you and is absolutly O.K . I would not send the NV file with my emei and serial too. (only the file with editet imei and serial)
I hope someone is interestet and crazy to unbrick the device and help me.
Kindly regards Woody01
Get a warranty replacement and don't even S-Off your phone. You obviously can't handle it.
In curious, why were you doing what you were doing?
Sent from my HTC Sensation Z710e using XDA Premium App
WorldWide60 said:
In curious, why were you doing what you were doing?
Click to expand...
Click to collapse
Haha i was wondering the exact same thing
I have similar situation. my phone won't boot, no LED anywhere.
what i stupidly did was, i tried to reinstall the stock ROM and between shuffling the screens around i skipped one step. that step was actually opening the stock ROM and running it and following the commands. so i tried to unroot and S-on without selecting a ROM to flash...... now i'm screwed.
i checked my SD card in my old phone and all the data is still there. will that make a difference. or am i helpless?
massasshadows said:
I have similar situation. my phone won't boot, no LED anywhere.
what i stupidly did was, i tried to reinstall the stock ROM and between shuffling the screens around i skipped one step. that step was actually opening the stock ROM and running it and following the commands. so i tried to unroot and S-on without selecting a ROM to flash...... now i'm screwed.
i checked my SD card in my old phone and all the data is still there. will that make a difference. or am i helpless?
Click to expand...
Click to collapse
I have my sensation bricked...it's dead with screen black...someone has a solution? Thanks to anyone
Bricked mine too (Yes, very stupid indeed)
aramis73 said:
I have my sensation bricked...it's dead with screen black...someone has a solution? Thanks to anyone
Click to expand...
Click to collapse
I was stupid enough to brick mine too by an S-OFF -> S-ON transition . No solution I guess? I e-mailed three different repair centers, but no response yet. I wonder if it is possible at all to flash the Sensation's bootloader without a functional USB connection.
For other phones it can be done by a JTAG interface, but this is very delicate job which I can't do myself.
For now I consider it bricked. I bought some Apple stocks (AEX ING Sprinters Long, Dutch stock market) and will let these pay (I'm already there after today) for the new Sensation that I bought already. If it is repairable after all I will sell one of them again. I'm not going for a warranty return. Beside the fact that it is possibly detectable that I voided the warranty by touching the bootloader, it is my own mistake that I have to pay for....
By the way I have been looking for more people who killed their HTC Sensation, but I could only find you two guys and a german who is mentioned in this thread as well.
Please keep in touch!
choas2009 said:
I was stupid enough to brick mine too by an S-OFF -> S-ON transition . No solution I guess? I e-mailed three different repair centers, but no response yet. I wonder if it is possible at all to flash the Sensation's bootloader without a functional USB connection.
For other phones it can be done by a JTAG interface, but this is very delicate job which I can't do myself.
For now I consider it bricked. I bought some Apple stocks (AEX ING Sprinters Long, Dutch stock market) and will let these pay (I'm already there after today) for the new Sensation that I bought already. If it is repairable after all I will sell one of them again. I'm not going for a warranty return. Beside the fact that it is possibly detectable that I voided the warranty by touching the bootloader, it is my own mistake that I have to pay for....
By the way I have been looking for more people who killed their HTC Sensation, but I could only find you two guys and a german who is mentioned in this thread as well.
Please keep in touch!
Click to expand...
Click to collapse
I'm actually doing the whole return process. Since mine is so badly inoperable, I'm hoping that after they inspect it they will be able to give me a new one. I was able to S-On the phone (as far as i know) during the process so if they are able to read it, it should be cool. If anything i'll either be turned down or have to pay for a new one.
Planning on blaming it on the over night charging + the 2.3.4 update they released the day i bricked it haha. It's all just a game of chance.
i did it too my friend , some mistake S-off ---> s=on transition , do you have any solutions
Hello everyone, I'm a noob and this my first post. I had been reading blogs for years now on all sort of advice and solutions, so yes this is my first reply or post on any blogs. I usually find the answer I'm looking for so posting anything was unnecessary. Now I really need help. I screwed up some how. I was attempting to turn S back to ON because my device was not taking the new update, and by doing so bricked my phone (wont power on. I'm guessing I had restored a rom and not original back up which xl VipeR lx had warned about in his instructions. I have SD with su-2.3.6.3-efgh-signed.zip on it. Can someone please help I really should had not rooted my phone because I dont have the knowledge. I can take instructions very well (was Soldier in the U.S Army for 8 years (2 years in Iraq). So if some one would please give me instruction on how to fix this, I would really appreciate it.
Is there any solution ?
Thanks !
Would this tool allow me to make a backup of my phone that can be restored if ever it is bricked? In other words, would it make my phone nearly unbrickable? I mean, there is very little chance of my phone being bricked, I make sure I know exactly what command does before I execute it. I realised I have spent most of my days in the last couple of weeks reading XDA and thinking about my soon to be gf in Hong Kong XD. I just worry that when flashing a firmware file I may be left with a brick, or even get one of those bricks people speak of that just happens randomly. I really don't want to lose my phone, it means so much to me lol. I just get so worried with these things....
What I'm trying to ask is, a partition backup created with this tool can be flashed to the phone with what functioning partitions? ie do you need a working radio partition or not? working hboot? Cause what I'm scared most about is flashing a bad radio and creating a phone that can not get into hboot... i'm also scared about getting a random brick which at the moment seems to be unfixable.
Mind you, it would make a pretty impressive paperweight....
EDIT: found this guide... can someone explain what NV items are? A small understanding of this may allow me to make a backup using this tool that could then be used to unbrick sensations... I couldn't find what NV items are... I also found this....
Sorry to put this here but first post after joining,and I can't post in the required section.
I have been trying to resurrect my bricked HTC Pico. I followed this thread http://forum.xda-developers.com/showthread.php?t=2048312 and found the rom to be very good and fast but one issue so if someone can let the developer know, After following all the instructions and installing the rom I can't do anything else due to it saying there is no more space even though I have set up the extra partition as ext3 before installing the rom.
Is that you IHATEHIPSTERSSS?
Anyways check out this thread
http://forum.xda-developers.com/showthread.php?t=1500165
I'd factory restore the phone and start the process over. As long as the computer sees the phone when it connects.you're not bricked.
Sorry, don't know who you are talking about and I tried the RUU but get a certificate failure. As I said, I tried everything suggested, even a full factory reset.
Oh and I have already done the suggested with extracting the files from the RUU
OK I talked to another guy on a tech site last night who is new to the pico and flashing ROMs.
Its been years since I delt with an HTC device. Google around using 'certificate failure' in the keywords. Hopefully somebody had a similar problem and figured it out.
Sorry I can't be of more help.
Thanks, it seems that because the phone was originally a T-Mobile phone, there are no RUU's that will go onto the phone because it won't accept a generic RUU. It would need to be a T-Mob RUU for the Pico, I have scoured the net but nothing so i'll just keep trying to sort the memory issue somehow.
Hi,
First of all, I'm new to this Forum, but i've been following it for quite a while now since almost everything Android related you can find here. And People around here seem really knowledgeable.
I've trying to update my One SV K2_UL, and i seem to got it messed up.
I was able to flash the update, and everything went smoothely, until i got to the firmware files, a cannot get them to flash.
I guess the problem is my phone is S-ON, and i cannot change it's CID, although a tried several ways of doing it.
And i cannot guet my phone to be S-OFF, i tried Moonshine but it gets stuck on second test. - "Waiting for ADB".
My phone is exactly the same as leegreenaway refers in this post:
http://forum.xda-developers.com/showthread.php?t=2512742&page=9
so i guess, it's not an equipment problem, it was really my order of doing things that screwed this.
Can someone please help me? What can I do?
I tried to revert to old version but with no luck.
Thank you in advance.
Rui
Yes, as long you are S-On, you can't flash the firmware files.
If moonshine don't work for you, you can try the new rumrunner S-Off (which is made from the same people).
Take care on the instructions on the page there, as it is new, i can not really tell you how it will work.
I have tried rumrunner also, it behaved a little different from moonshine since it passed the second test, and found the device, but than nothing, it didn't go further it just said - "Press Enter to Exit.".
Thanks for the fast reply btw.
Then maybe this post, can give you a helping hand.
If you have Norton Antivirus, disable it. Make sure, you have a sdcard in the phone.
I did had Norton in the beginning of my day, but i already uninstalled it, just to make sure,.
I do have a sdcard on my phone.
So i tried running rumrunners once again, and took a ps of what is happening.
View attachment 2398349
When i see it right, you are on windows 8?
Windows 8 is known as not "driver-friendly" related to android/adb.
Maybe you have a chance to use a Windows 7 PC or even Linux.
Maybe @beaups knows whats the problem is...
Yes you're right,
i'm on windows 8.
unfortunately i do not own any PC with win7, althought ADB looks to be working right since i was able to use the shell and other adb stuff, i might as well give it a try tomorrow at work. I just hope i can turn this around, the phone is working great appart from that fantastic noise the speaker makes.
Thank you.
Well, today I tried to use both moonshine and rumrunner at work, but with no luck. The pc at work is running win7, althought the problem persisted exactly the same in rumrunner, in moonshine it was a bit different because it only stopped the second time it was waiting for adb. I was wondering if someone with the orange phone from UK could provide the firmware from that update, and if this souls male a difference.
Thanks again,
Sent from my HTC One SV using xda app-developers app
Last idea on my side:
You wrote in first post, you flashed everything except firmware. That means, you have the Sense 5 software already installed?
I think you should try then with the stock software, moonshine is made for.
Maybe its checking the version (HTC One SV (k2_ul) 2.14.401.6) and fails, because it is wrong.
Well, actually I got that same conclusion in my mind yesterday, just when I arrived at home from work. So I used the 2.14 odexed stock you provided in a thread, and from there I was able to run moonshine, it completed successfully, and after I just had to re-flash the 3.22 odexed, change the cid and flash the firmware. Voila, problems solved everything is in order now.
So the problem was only, the boot img moonshine was trying to flash would never work on my sys version.
Thank you very much for your help, this was a great learning experience.
Cheers,
Rui
Sent from my HTC One SV using xda app-developers app
Glad you got it sorted out.
old.splatterhand said:
Yes, as long you are S-On, you can't flash the firmware files.
If moonshine don't work for you, you can try the new rumrunner S-Off (which is made from the same people).
Take care on the instructions on the page there, as it is new, i can not really tell you how it will work.
Click to expand...
Click to collapse
Thankyou thiese s-off utility helped me to take s-off
Hi Guys,
I'm trying to get a 'stable' rom for a phone I've given to my daughter (Evita / Telstra one XL).
I've tried a heap of things, tried to s-off, change radio files etc... Anyway, current status is that it's been unlocked, s-on, and I have twrp.. I'm using KickDroid XL v4.0.0 ROM, looks great, but the phone keeps on rebooting... Also loosing 3G signal, so have to reboot it quite a few times a day to resolve. (tired another rom, same problem, loss of 3g signal and multiple reboots during the day)
I'm sure it's got to do with the radio file, but can't seem to fix that. I've read 'so much!' information, but really confused now. I've tried to supercid it, unsuccessfully, tried to find the all-in-one toolking (bt it looks like its been removed)..
So, this is what I have when I boot it:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.11.0000
RADIO-0.23a.32.09.29
OpenDSP-v28.1.0.32.0504
eMMC-boot
Jun 7 2012,13:10:34
TWRP recovery
2.6.3.0
htc one xl
Evita
Any help in how to (or if I should) get the radio/hboot up to hopefully resolve the loss of 3G?
I'm no expert, but not that dumb either. I follow instructions from the start, but most of the time it gets stuck half way (ie, when doing supercid, boots to the HTC logo, but won't go any further)..
Any help really appreciated.
The problem is not that the ROM is unstable, the ROM is perfectly stable if you meet the requirements. The problem is your current firmware version. You need to update to the 2.15 firmware package. It does state that very clearly in the "You Need" section in the beginning of the Kickdroid thread. Please search/research properly before posting in future, it's part of the XDA rules. This issue has been discussed extensively in every single Sense 5 ROM thread, plus this is probably the 100th thread like this in our Q&A section.
Sent from my Evita
Why are you even giving your daughter a rooted/modded phone at all? Unless she has an understanding of what root means, its not a good idea. Does she even need anything except a bone stock phone?
thanks timmaaa, I appreciate you taking the time out to reply.
I'll do some more checking on firmware 2.15... I've honestly read about 5 hours last weekend on various threads... some lead to dead ends (it toolbox), some I can't get to work (supercid)... I tried this a couple of months ago, and almost bricked it, but managed to get twrp working...
Redpoint73, are you asking why give her a phone, or why a rooted phone? The answer to the first one is that she is 11, and catches the bus to and from school. The phone is used in an emergency. I've rooted it to give her some new features, and because it was locked with Telstra and that is not the carrier we are using anymore (much cheaper options here than Telstra), so I needed to get rid of the firmware...
Overall, I appreciate any help. I actually run 5 forums (car related), and I fully understand noob's coming on and asking the same question week after week. Our forums have a lot less posts than this one (< 200,000), but we still have members, week in-week out, answering the same questions because they like to help, and because sometimes there is too much information out there to sift through, especially when somebody is willing to point you in the right direction with a friendly smile
duplicate post, (sorry, hit save twice!)
jnrdavo said:
Redpoint73, are you asking why give her a phone, or why a rooted phone? The answer to the first one is that she is 11, and catches the bus to and from school. The phone is used in an emergency. I've rooted it to give her some new features, and because it was locked with Telstra and that is not the carrier we are using anymore (much cheaper options here than Telstra), so I needed to get rid of the firmware...
Click to expand...
Click to collapse
Its pretty clear from my post that it was root/mod that I was referring to. Root has nothing to do with Subsidy (SIM) Lock, and the firmware has little to do with the carrier you are on (I've been using the German T-Mobile stock ROM for a while now, despite being on AT&T).
Of course its up to you to decide what you do with the phone. But you should consider (if you haven't already) the security risk of giving a rooted device to a user that knows little or nothing about such things. Even more so for s-off, which is necessary for the solution that timmaaa suggested.
My question has less to do with exactly "who" the phone is for. But more to the point, when people come on here saying they are modding the phone for "someone else" (be it mom, third cousin, or whatever), if that person isn't doing it for themselves, its pretty questionable whether they need such mods at all.
ok, thanks redpoint73..
I understand where you are coming from, and appreciate your comments.
Now, anybody else like to point me in the right direction (to a link to get the latest firmware, or a compatible one working)?
jnrdavo said:
Now, anybody else like to point me in the right direction (to a link to get the latest firmware, or a compatible one working)?
Click to expand...
Click to collapse
You serious? timmaaa already told you where to find it.
Since I'm feeling charitable right now, here it is, complete with step-by-step instructions (only need to follow Posts #2 and 4): http://forum.xda-developers.com/showthread.php?t=2485865
The original thread where Turge posted his firmware package (see under "OPTIONAL", s-off is required before doing this): http://forum.xda-developers.com/showpost.php?p=45072132&postcount=1
Or just install the Beastmode kernel (S-off not required): http://forum.xda-developers.com/showthread.php?t=2165880
thanks mate. I appreciate the charity, I really do I'm trying not to be a nob.. I'm actually having another go this morning... I've got win 8.1 (yeah, I know) so trying to get the latest driver to work is a pain.... Just trying x_factory windows, backups up twice, but then doesn't run the next command (to change CID)...
Anyway, thanks again. I'll persist on...
Ok first off I would like to start off by thanking everyone in advance. I am a little weird at explaining over text but ill try. I have a old AT&T HTC One X that I was wanting to install a jellybean custom rom on. I guess in order to do that i have to update the Hboot to 1.36 (Hboot currently 1.14). Now correct me if i'm wrong but I did a little research and noticed I had to unlock the bootloader prior to updating the Hboot, so I watched a video by a guy known as "onexroot" (link below) and followed his steps. But when I looked at my CID it was 11111111 so I didn't really know which option to pick. So I stopped and did a little more research on this and had no success. I continued and picked list . After going through the next few steps I get an error "FAILED(12 signature verification fail)" I went online and researched this and it seemed that that error only came up on nexus one devices? I am completely stuck and seem to run into a error every time I try to mess with this phone. I would be very thankful if someone on this forum could shed some light in the direction i need to go with this phone. I have attached a ZIP file with the pictures and a text document containing the link to the youtube video and my email address. I put them into a ZIP because the pictures were to big and i'm unable to post links because I am a new user.
Thanks,
Tyler
Mrhand1113 said:
Ok first off I would like to start off by thanking everyone in advance. I am a little weird at explaining over text but ill try. I have a old AT&T HTC One X that I was wanting to install a jellybean custom rom on. I guess in order to do that i have to update the Hboot to 1.36 (Hboot currently 1.14). Now correct me if i'm wrong but I did a little research and noticed I had to unlock the bootloader prior to updating the Hboot, so I watched a video by a guy known as "onexroot" (link below) and followed his steps. But when I looked at my CID it was 11111111 so I didn't really know which option to pick. So I stopped and did a little more research on this and had no success. I continued and picked list . After going through the next few steps I get an error "FAILED(12 signature verification fail)" I went online and researched this and it seemed that that error only came up on nexus one devices? I am completely stuck and seem to run into a error every time I try to mess with this phone. I would be very thankful if someone on this forum could shed some light in the direction i need to go with this phone. I have attached a ZIP file with the pictures and a text document containing the link to the youtube video and my email address. I put them into a ZIP because the pictures were to big and i'm unable to post links because I am a new user.
Thanks,
Tyler
Click to expand...
Click to collapse
Wrong forum mate you must to ask in Evita vorum here is international HOX forum don't use anything from here on your phone
Reported and will be moved
Mrhand1113 said:
Ok first off I would like to start off by thanking everyone in advance. I am a little weird at explaining over text but ill try. I have a old AT&T HTC One X that I was wanting to install a jellybean custom rom on. I guess in order to do that i have to update the Hboot to 1.36 (Hboot currently 1.14). Now correct me if i'm wrong but I did a little research and noticed I had to unlock the bootloader prior to updating the Hboot, so I watched a video by a guy known as "onexroot" (link below) and followed his steps. But when I looked at my CID it was 11111111 so I didn't really know which option to pick. So I stopped and did a little more research on this and had no success. I continued and picked list . After going through the next few steps I get an error "FAILED(12 signature verification fail)" I went online and researched this and it seemed that that error only came up on nexus one devices? I am completely stuck and seem to run into a error every time I try to mess with this phone. I would be very thankful if someone on this forum could shed some light in the direction i need to go with this phone. I have attached a ZIP file with the pictures and a text document containing the link to the youtube video and my email address. I put them into a ZIP because the pictures were to big and i'm unable to post links because I am a new user.
Thanks,
Tyler
Click to expand...
Click to collapse
I think you're a bit confused here, and it's probably due to going to onexroot.com for information. XDA is the only place you should go to for info regarding modifying your device. That other site doesn't properly distinguish between the HTC One X (Endeavoru) and the HTC One XL / at&t One X (Evita), they're completely different phones and the firmware isn't compatible. You have the HTC One XL / at&t One X (Evita), but the tool you've been using is for the HTC One X (Endeavoru), it's a good thing it keeps failing otherwise you'd have an expensive paperweight on your hands.
Anyway, stay within XDA, and more importantly, stay within the correct device subforum. This is our device main page:
http://forum.xda-developers.com/one-x-att
Don't ever venture out of this section or you'll end up in trouble.
So, what you need to do is go to htcdev.com and unlock your bootloader. Once you've done that you can flash TWRP recovery to your device. Once you've done that you can flash SuperSU to get root. Once you've done that you can get s-off via the Facepalm s-off method. And once you've done that you can upgrade your firmware (not just your hboot) in order to run the latest Jellybean ROMs. I have a guide thread in my signature which will explain most of the above stuff, but feel free to ask any questions if you need further help.
Transmitted via Bacon