Hi, folks.
I'm having a bit of a pain point with my new HTC Inspire. After I downgraded the device, the bootloader takes forever to do what it needs to do. It stays on a black screen for about five minutes or so, then brings up the HTC white screen, vibrates immediately after that for about two minutes straight (engine burnout seems imminent here), continues booting for another minute or so and then, finally, loads the operating system.
Potentially relevant specs:
HBOOT: 0.85.2007 (PD9812000)
MICROP: 0438
RADIO: 26.03.02.26_M
S-OFF
I think I need to flash something new, but I don't know what. Any suggestions? Thanks in advance, guys!
UPDATE: I tried re-flashing PD98IMG; did not work.
take out battery put it back in and while holding down the volume - button power the device on, now you will be in the boot loader and to to factory reset then try everything again
---------- Post added at 06:50 PM ---------- Previous post was at 06:48 PM ----------
also this dose not belong in the development section it belongs in Q & A look before you post as this has nothing to do with development, mods please close
A senior member should know this does not belong in the developer forums
Wow; love the help. Thanks, guys.
Buddy, u will get more help if u post ur thoughts & questions in the proper forums. You've been told this before. So in that sense, we ARE helping u.
Right, so this isn't a general problem. I would think issues with bootloaders and such, especially in the context of rooting/unlocking a device, would be issues fit to ask this forum. None of the threads I've searched in Q&A have really helped me, but feel free to continuously tell me I don't know this site.
This is for development. Bottom line. No question of any kind should be posted here. That's why there is a q & a section. The system works if u let it
Well sense this started after you downgraded then I would start over from there. As for where this belongs. ALL questions go into Q&A.
Sorry for all the fuss. I'll make sure things go in the right places next time. Hoping someone can help me here; I just got this phone and would love to start using it!
You said you downgraded. What did you downgrade to?
@Gizmoe: Those instructions called for: 1.32.405.6
You should use "ace hack kit" to return your phone to gingerbread stock with s-on. And then use the same tool to root. It does both and is the most up to date and easy root/return to stock tool for the inspire.
Checking that thread out, I just realised that I did exactly what they warned against: my device shipped with a Gingerbread ROM and I downgraded to the Froyo one as per the Cyanogenmod instructions. I'm downloading the kit as well as the latest stock Gingerbread ROM. Will updating to latest stock ROM with S-ON get me back to where I was?
mrcrassic said:
Checking that thread out, I just realised that I did exactly what they warned against: my device shipped with a Gingerbread ROM and I downgraded to the Froyo one as per the Cyanogenmod instructions. I'm downloading the kit as well as the latest stock Gingerbread ROM. Will updating to latest stock ROM with S-ON get me back to where I was?
Click to expand...
Click to collapse
That's what I assumed. Ace kit should fix you up.
Thanks a lot! Out of curiosity; why does this type of downgrade slow down the bootloader so much? Doing a downgrade on the G2 I had was pretty straightforward (hence why I did this)
Great script. Feel your pain that it was done all in batch, but great script nonetheless.
mrcrassic said:
Thanks a lot! Out of curiosity; why does this type of downgrade slow down the bootloader so much? Doing a downgrade on the G2 I had was pretty straightforward (hence why I did this)
Click to expand...
Click to collapse
I don't know. I have the original hboot so I haven't researched much about it. I just know it was an issue when gingerbread starting rolling out and HTC changed the version of hboot from 0.85.0024 to 0.85.2007.
Interesting. I've finally downloaded the kit; these long boot times make this excruciating, but I'm hoping this resolves it!
The problem is only on fairly recent Inspires (MFG after about Sep. 2011). HTC has shipped them with some different hardware than the earlier ones. The later hardware won't work with the earlier (or the ENG) hboots. I suspect this may be in direct response to AT&T being so anal about tethering. With froyo, you could get by the tethering blocks by editing you APNs. With GB, this ended for most users so many reverted back to froyo to regain tethering.
Hey all, I'm sorry if this seems an odd question, but I'm still trying to get my head wrapped around the process of how the One S gets different features flashed to the device.
I don't have my One S yet (Hopefully it'll arrive later today, 7/27) but I wanted to be prepared when it arrives.
It seems the links are broken in this post and it's stating that this thread is outdated.
If I'm going to flash a new ROM on the device, are the radios generally included in that ROM already? I see that you often times need to manually flash BOOT.IMG on a per-ROM basis due to not having s-off? I'm comfortable with all of that, I just want to make sure that I'm not missing anything, and unfortunately it seems as though there is little information in some of the threads on XDA that clearly answer my question.
Call it a personality defect, I just like to 100% understand something in every possible way before being able to attempt it. Unfortunately when I don't have the device in front of me, it prevents me from being able to do that, but that's what forums are for, right?
Cheers all, I appreciate anyone taking the time to answer my question.
TooSlo said:
Hey all, I'm sorry if this seems an odd question, but I'm still trying to get my head wrapped around the process of how the One S gets different features flashed to the device.
I don't have my One S yet (Hopefully it'll arrive later today, 7/27) but I wanted to be prepared when it arrives.
It seems the links are broken in this post and it's stating that this thread is outdated.
If I'm going to flash a new ROM on the device, are the radios generally included in that ROM already? I see that you often times need to manually flash BOOT.IMG on a per-ROM basis due to not having s-off? I'm comfortable with all of that, I just want to make sure that I'm not missing anything, and unfortunately it seems as though there is little information in some of the threads on XDA that clearly answer my question.
Call it a personality defect, I just like to 100% understand something in every possible way before being able to attempt it. Unfortunately when I don't have the device in front of me, it prevents me from being able to do that, but that's what forums are for, right?
Cheers all, I appreciate anyone taking the time to answer my question.
Click to expand...
Click to collapse
The latest radio with android 4.0.4 rom is said to be much better in terms of performace of wifi and cellular data signal then all previous versions, unfortunately buying a phone at this stage means that you probably will have a later hboot version 1.13 and this hboot doesnt allow flashing radio from recovery like the previous versions. You can find out more info about the radio in this thread: http://forum.xda-developers.com/showthread.php?t=1781033
To answer your other question the radio has to be flashed separately from the ROM. Hopefully your phone comes with a lower hboot so flashing wont be a problem, make sure you dont accept the ota update out of the box like i did so u dont accidently get an upgraded hboot. Makes life more diificult ;p.
Its a used phone and is already running CM9, so I'm hoping its the older boot. I already made sure it was the S4, but I just realized that the unlocked phones don't support TMOUS bands, so I'm a bit screwed at the moment.
I don't know what the next step is for me, so I may be forced to move to Straight Talk until I can get another 100% compatible TMOUS phone. I saw it has 2100 HSPA radio frequencies so I had assumed it would work on TMOUS. Needless to say I feel pretty stupid now.
Thanks again for the links, they were exactly what I was looking for!
Sent from my MB860 using Tapatalk 2
just boot into bootloader it will tell you hboot. i think .06 is stock one
there are radio links here .10 latest for us--if you want 4.0.4 one--research needed
http://ville.giev.de/?page_id=42
flash thru twrp or if cwr you must boot into recovery thru fastboot then flash
Radio from 4.04 update and hboot 1.13
rugmankc said:
just boot into bootloader it will tell you hboot. i think .06 is stock one
there are radio links here .10 latest for us--if you want 4.0.4 one--research needed
http://ville.giev.de/?page_id=42
flash thru twrp or if cwr you must boot into recovery thru fastboot then flash
Click to expand...
Click to collapse
Sorry for putting this question another time, but the answers concerning this are treated in a lot of different threads, just to confirm:
I am on Leedroid 2.1, Radio Version 0.1631501S.17_2_10.23.31501S.10L; i have Hboot 1.13,
I there a possibility for me to flash this new radio radio from update 4.04??
Regards, Dwino
Dwino said:
Sorry for putting this question another time, but the answers concerning this are treated in a lot of different threads, just to confirm:
I am on Leedroid 2.1, Radio Version 0.1631501S.17_2_10.23.31501S.10L; i have Hboot 1.13,
I there a possibility for me to flash this new radio radio from update 4.04??
Regards, Dwino
Click to expand...
Click to collapse
If you want to get this new radio, the only way to do it at this moment is to change to SuperCID and follow the steps from this thread http://forum.xda-developers.com/showthread.php?t=1781033
I bought this phone over eight month ago. I have been patiently waiting for the over-the-air Jellybean update, and it is STILL not here. I understand that it is only a few days away because it was just released for Rogers users in Canada, but I just terminated my account with AT&T. They charge me $120 a month for the lowest amount of minutes with 5gb of data. I bought an unlock code off of eBay for about $1.50 and I have a T-Mobile sim due to come in on Tuesday. During this time of service interruption I plan on rooting my phone to flash custom ROMs. My phone is on firmware version 2.20/4.0.4. I am running Mac OS X. I know there are tons of tutorials on how to do this, but NOTHING is working for me. Would someone mind helping me out here. Useful links, definitions, etc?
-Are you using the right guide ( NOT one X )
-Do you have any experience with flashing etc.?
-What methods have you tried?
-What version is your hboot / os / fw etc.?
IMO, stock ain't that great. But I can understand the hesitation to go down the modding route.
Read some more, clearly post your sw versions and the rom/s you are trying to install with failure symptoms ( after googling ) and people will help you.
Good Luck!
gururug said:
-Are you using the right guide ( NOT one X )
-Do you have any experience with flashing etc.?
-What methods have you tried?
-What version is your hboot / os / fw etc.?
IMO, stock ain't that great. But I can understand the hesitation to go down the modding route.
Read some more, clearly post your sw versions and the rom/s you are trying to install with failure symptoms ( after googling ) and people will help you.
Good Luck!
Click to expand...
Click to collapse
1.) I would love to post a link to the guide I have been using on youtube, but I do not have enough posts to do so yet. I used a guide on youtube that gave a tutorial on Windows, then Linux, then Mac OS X. I was able to successfully root/change my CID to 111111. The guide only went that far, then I tried to unlock the bootloader on htcdev.com, but the tutorial they give was only for Windows, and I am not so savvy on Mac OS X. I gave up and left it at that. This morning I did a factory reset on my phone, so when I use CID getter, it says my CID has been set back to the stock CID, but when I tried to do the same method on Windows, it is telling my that my CID has already been change... Yes it has already been changed, but it has been change BACK too!
2.) No, I have been using iPhones since their initial release date. If it matters, I have successfully jailbroken every iPhone I have owned, and am pretty savvy with this sort of stuff, I just don't know where to take off.
3.) The only method that I have tried, and that I know of is the XFactor exploit. It goes as far as recovering twice, but when it tries to recover the CID, it says it has already been changed. I tried to run the unlock_code.bin or w/e, but it just says "waiting for device."
I am running stock ICS 4.0.4, firmware 2.20 on AT&T. When I boot in to bootloader it says:
*** LOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19AS.32.09.11_2
eMC-boot
Jun 11, 2012.14:36:28
If you know any other methods of changing my fricken CID, I would be the happiest person EVER.
Alright well I can't help you with the CID part but I can tell you that once you do get root access, dont flash a rom butbinstead downgrade your hboot from 1.14 to 1.09. This can easily be achieved by using the Jewel/Evita tool kit in the Android Devolpement topic. You want to do this because on hboot 1.14 you cannot change/flash the boot partition (also radio partition) when in recovery mode. In 1.09 you can. This makes flashing a hell of alot easier. Good luck!
Sent from my HTC One XL using xda premium
Scozzar said:
I beg to differ. I am running on 1.14 and I have absolutely no problems with flashing roms. I would think it might be riskier to downgrade hboot than to just flash a ROM. Flashing a ROM really isn't all that difficult IF you know what you're doing.
Click to expand...
Click to collapse
I tend to agree. Some say the JET tool (to downgrade hboot) is not that hard. And I haven't done it myself (and don't need to as I'm on 1.09). But my understanding is that you have to soft brick the phone in order to get it into Qualcomm download mode, to do the downgrade.
---------- Post added at 03:32 PM ---------- Previous post was at 03:29 PM ----------
ryangunnip said:
1.) I would love to post a link to the guide I have been using on youtube, but I do not have enough posts to do so yet.
Click to expand...
Click to collapse
I would advise against randomly searching for guides on Youtube or other places, and sticking to the guides here on XDA. At the least, other sources are not well organized, and can get you flashing something meant for the Tegra3 version of the One X, which can get you in a lot of trouble.
Sorry I should have clarified. I was talking about the kernel.
Sent from my HTC One XL using xda premium
I'm running over 2.2 too. The only Rom ove got to work is viper. 3.1.0 is damn good bar some lower battery life.
Install latest twrp, flash boot and clear caches and install zip from recovery.
I suspect you have taken a dodgy path playing with a level lower than you have to, on the bright side, your phone still works and you learnt something!
Sent from my HTC One XL using xda app-developers app
thanks
I am trying to attempt messing with this type of thing for the first time so noob handling will be required. My reason is simply my phone is a nice wallpaper display three days after the ota from tmobile 1.63.531.2 710rd.
I began by trying to follow:
http://forum.xda-developers.com/showthread.php?t=1505999
To no avail. Of course I noticed afterwards that for some reason it says to turn s-on in the header... exactly the opposite what what I need to flash the phone back to (PG59IMG_Doubleshot_TMOUS_1.28.531.9_Radio_10.48.9007.00U_10.12.9007.07_M2_release_201815_signed.zip) I have had problems with the phone ever since its first ota a year or so ago. With this latest ota the phone is more or less bricked as of the phone using power saver when I went to sleep last night... Wont call or check into the network...no dial tone. Took me 3-4 restarts for it to even show the antenna symbol and the 4g icon in the taskbar.
My phone is set as S-on for now. The only instructions I have found through the search tool relay how to do it to the sensation... I believe that is the mytouch 4g not slide. However I have the slide which is doubleshot. So my question is, is this instruction on http://forum.xda-developers.com/showthread.php?t=1192300 safe to use with the doubleshot since the (T-Mobile branded HTC myTouch 4g Slide ( doubleshot ) Developers Reference) page links to it indirectly. Using the link at the top of the how to S-on after s-off... again the opposite of what I need so I tried following the link at the top of that page " Guide to Installing S-off, Unlocking, ClockWork, Root, SuperCID & S-on " which takes you to the s-off instruction page for the sensation (Link: http://forum.xda-developers.com/showthread.php?t=1192300 )...I am guessing that it will work and sensation refers to HTC sense, but I don't care to make the mistake of doing it wrong and bricking my phone due to being derp.
I know there is a bit of overdone explanation and redundancy in the addresses I have left here. I am just trying to cover all my bases thanks for the help in advance.
The short and sweet is I need a link by link list with instructions on how to step my phone back for multiple reasons. First the recent OTA more or less broke my phone and I don't want a refurb phone with inferior parts from Assurion...(They were in class action lawsuits for this in the past.) nor do I want to pay 130$ for said replacement. Next from what I just read the 1.63 update has some serious security compromises that are awaiting response from HTC for an update. Basically it gives full accesses to all your data to include your sim and SD card contents to all apps. Regardless of user specified/agreed permissions.
Following ANY routine or procedure for another phone is just too dangerous & will never work anyway. The bad part being you may very well create a brick in the process. If you have the MT4G SLIDE, this is where you will get all that you need so don't even consider other threads.
Since you've done the OTA & are sitting at Hboot 1.63.XXX now you will HAVE to get S-Off before you can go back to your previous Hboot. To DO that you will have to follow the instructions HERE.
If all you are wanting to do is start flashing ROMs, then the instructions you need are HERE.
Keep us informed & we'll try to help if you need it. Good Luck!
WeekendsR2Short said:
Following ANY routine or procedure for another phone is just too dangerous & will never work anyway. The bad part being you may very well create a brick in the process. If you have the MT4G SLIDE, this is where you will get all that you need so don't even consider other threads.
Since you've done the OTA & are sitting at Hboot 1.63.XXX now you will HAVE to get S-Off before you can go back to your previous Hboot. To DO that you will have to follow the instructions HERE.
If all you are wanting to do is start flashing ROMs, then the instructions you need are HERE.
Keep us informed & we'll try to help if you need it. Good Luck!
Click to expand...
Click to collapse
Thanks for the hasty post reply any other suggestions...I have win7ult 64bit. Or will will juopunutbutter work even though they have the below disclaimer?
"Supported Operating Systems:
We only support Windows 7 32bit or Ubuntu 12.04 (and newer) 32bit, you may use a LiveCD if you have the wrong OS installed natively. Win XP 32bit might work for you but we do not support it as we did not test on it."
Also, this, "Be on the Stock RUU and be rooted (have superuser flashed). No other ROMs are supported, Fresh ROM will not work regardless of what you have read elsewhere."
-I am not rooted. Which is something else I want to accomplish so I can set up firewalls that block certain things.
Oh btw provided I can get this phone working again I am also going to attempt to reflash my older mytouch 3g... back to original as well that thing worked better than any of the current phones for my purposes before it got the update prior to the 2.2.1... the original update didn't work with adobe which is fine with me, people need to move on from adobe's garbage anyway. Specifically with the old mytough 3g though that really did add functionality at the sacrifice of sanity since it slowed the phone down so much. On that note though I may just put on a custom if I can get comfortable with this stuff. The last time I looked at a pc this hard was back in win98se when you had to know how to do tricks to make it faster like modifying available rame to twice as much above and below physical ram and a few other tweeks I have long forgotten.
That brings me to another question. If I go custom rom and unlocked this looming threat of brick is weighing in on me. If a phone is bricked is it possible to recover using some of the same tools that bricked it in the first place... flash install original rom as a fix? Just trying to see how much margin of error I have to work with.
Thanks again.
PS who do we talk to about backing off all the java on the site since it is so compromised right now? This sight has more java permissions than most sights of ill reput... though I have been reading these forums off and on for a while so I trust it more than most with this much tracking. I doubt patch 11 actually fixed the issue...since the day before they said it would take two years or more to actually resolve the java zero day exploit.
You should be fine with your pc, I used a 64bit win7 too. If you're worried dual boot linux.
Your my touch 3g is rooted diferentley, go to that forum for details, its not true radio soff but its close enough.
If you brick it its dead, depending how it was bricked jtag could bring it back to life or this phone is part of the unbricking project which will fix some other bricks. Problem is people use brick as a term that means a whole lot of things so its hard to answer. Usually a brick is forever dead, most people don't actually brick their phone though and usually have to be neglecting things to do it.
As for java... just read up on a bunch of trustworthy places for more info and understanding
Sent from my HTC Vision using xda premium
I'm afraid I just don't know about Win 7 64bit and how it will react but I'm sure there has to be a person or two around with experience concerning that OS. It may very well work fine. I CAN tell you that the "wire trick" (junoptobear?) will work fine on MikTouch because that's what I used. It's a stripped down GB stock ROM which is all you're really looking for. Why....I don't know.
As far as bricking goes, there's not a GREAT deal to worry about as long as you follow all instructions to a tee. You REALLY don't have to even have S-Off to flash ROMs as you read in that link. You just need to flash the kernel after you flash the ROM. It WILL limit a few things you can do but not ROM flashing.
When it comes to rescueing a bricked device though, there are only a very few instances that can be done as far as I know. But I'm no developer either. But if you can make it to your bootloader and/or recovery you not bricked. It may be a hardware of software issue but most of the time you can come back from those.
As far as the Java issue you spoke of goes, you may be able to get an answer to that one by PM'ing one of our moderators or admins.
I want to step it back to previous versions because they worked better...primarily the first version... Also, I am not seeing a guide that refers to doing it to the 1.63 patch. keyboard hasn't swyped right since the first ota update. Also my intent is to root an older version so I can remove crapware like dt sync, friend stream, kidzone, tmobile mall, tmobile tv, tmobile setup, telenav gps, and zinio reader.
X-Lander said:
I want to step it back to previous versions because they worked better...primarily the first version... Also, I am not seeing a guide that refers to doing it to the 1.63 patch. keyboard hasn't swyped right since the first ota update. Also my intent is to root an older version so I can remove crapware like dt sync, friend stream, kidzone, tmobile mall, tmobile tv, tmobile setup, telenav gps, and zinio reader.
Click to expand...
Click to collapse
It's a simple flashing process but you HAVE to achieve S-Off first with the "Wire Trick". You can flash it forward without S-Off but not backwards. Does it work at all or is it just frozen to some point in the boot process? Can you access your SDcard? Can you boot to Hboot & recovery? These are a couple of things you will have to be able to do to go forward if I understand you correctly.
I have scoured the internet for a solution, but my phone is from Hell. Every single thing I have ever done has ended in errors, ranging from trying to flash the rom zip and getting a "data length is too large" to errors while my phone did still have an OS and flashing through fastboot or double clicking in an exe would give me errors regarding the version or whatever other bs. I have been actively trying to fix this phone for well over a year! When I first started, it was still under warranty, and now it's just a paperweight that continues to waste days of my time at a time.
I am by no means a noob to electronics, but it seems I must be missing something I didn't learn, as I must be a noob in rooting/unrooting/flashing phones. I hope to God nobody suggests that I should have posted this in another thread, as I have searched all similar threads (all over the internet, different phones, any website that Google could find) and tried every single method anybody suggested. Most methods would be completely useless as I wouldn't meet the prerequisites, but I tried even those methods once I exhausted all serious methods.
I have officially gone mad and am about to say goodbye to all technology and go live in a Amish community for the rest of my life. I became so desperate and crazy that I managed to mess up my phone further than it was to begin with. PLEASE HELP! I am at your humble service, and I await any and all instruction.
A little background:
I got the phone from a family member once they cracked their screen, as I am much more of a hardware techie and I got the phone as a present to fix and use for myself. My family member is trigger happy and likes to root everything he could get his hands on. I am much happier with the stock versions of things as they give the best performance for my needs, not to mention the much less hassles and headaches with updates and reception and so on and so forth. I got the phone when it had 1.73.502.1 software on it. I wanted to upgrade to the 3.18.502.6 software version that was available, unroot the phone, and take everything back to dead stock. Since then, 5.18.502.1 has become available. (Side story about this: when double clicking the 5.18.502.6 RUU exe to go into my temp folder and extract the ROM zip, this version doesn't execute for some reason when downloaded from the "HTC OTA and RUU collection" thread (http://forum.xda-developers.com/showthread.php?t=2119610), and the previous version mentioned does execute and show up in my temp folder in Windows, but there are two roms (rom 1 and rom 2), and when extracting them, I get errors, so I had to download and extract 2.20.502.7, which executed and extracted without any problems)). I tried unlocking the bootloader through HTC's website (yes, I believe I relocked it about a year ago in a stupid move because I read that in order to execute an RUU you have to be relocked), but I guess AT&T is a big douche, so I had to superCID (cid 11111111) before doing so, but simply doing "fastboot oem writecid 11111111" wouldn't work, so I literally tried a million different tools I found until magically (literally, I don't know what happened or what I did), I got to superCID, in which case I unlocked with no problem. I then tried every method possible of updating, flashing, everything, but when things got to the actual rom zip part or executing RUU or basically the last steps, I would always be presented with errors and fails. In an angry move, I went to TWRP and erased everything I could get my hands on (I know, I messed up, kill me), and so I deleted the OS and whatever else was on the phone. Since then, I also managed to relock the bootloader (which I locked and unlocked multiple times with no problem and had the unlock code, so I figured I'm safe forever), and take my CID back to cws__001 (which I thought might be the cause of all of my errors, but found that now I can no longer unlock my bootloader).....
I now have an HTC One X from AT&T that is relocked, CID is cws__001,stock recovery, no operating system to boot into adb, and not able to flash anything on it to get into TWRP at least to try and adb sideload or some other things to take back the screw-ups I did since last night.
Info on bootloader:
TAMPERED
RELOCKED
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.16.32.09.01_3
OpenDSP-v25.1.0.32.0405
eMMC-boot
Nov 26 2012, 18:37:14:-1
I apologize beforehand for even touching the phone's software and trying to mess with it and maybe learn a thing or two in the process. Again, I thank you greatly beforehand for all your input, and I hope to hear back soon!
Erik
You can run the 3.18 att ruu to fix the phone to the point of it booting. If you want to learn a few things (such as custom ROMs and the like) you can visit threads on how to root, unlock the bootloader, get supercid, and then s-off.
Sent from my One XL using XDA Premium 4 mobile app
Thanks for the prompt response
I tried what you suggested just now (downloaded the 3.18.502.6 RUU exe from the thread http://forum.xda-developers.com/showthread.php?t=2119610, went into fastboot, right-clicked the exe and chose to run as administrator), and I got "ERROR [158]: Image Error"
I had tried that numerous times in the past as well, with either the same error or various other errors, through fastboot and through the phone being on and fully operable.
On a side note: for some reason it's recognizing my current image version as 3.18.502.6, but there is no operating system on there now, and when there was, it was definitely 1.73.502.1
Any other suggestions?
edit: also, please don't tell me that I should have changed my CID to CWS__001 instead of cws__001....does it make a difference if the CID is lowercase or uppercase?
Ok, wow. I'm not sure where to start here. I think perhaps your main problem is that you rushed, and you've tried "every single method" for doing things, when there is usually only one specific method for each scenario you encounter on each device. The key is to be patient and do the proper research, and find the method that is going to fix the problem you're facing. The other key is to stay within XDA, and more specifically to stay within your device forum. Venturing onto other websites is a bad idea, they don't properly distinguish between phone models (and the information is usually plagiarised from XDA anyway). If you can't find the method that's going to fix your problem, then ask here, don't wait until you've royally screwed the device to ask for advice.
I believe the CID is case sensitive so there's why the RUU you want to run isn't succeeding. Go to the Compilation Roll-Up thread in my signature, find the 3.18 root method, achieve SuperCID again using that method, unlock your bootloader again, flash TWRP 2.6 from here, flash a ROM from our development section, get s-off, boom, done. Getting s-off is optional but trust me, you're gonna want it.
Sent from my Evita
---------- Post added at 11:36 AM ---------- Previous post was at 11:28 AM ----------
Actually, just realised the 3.18 root method won't work because it requires a working OS. Try flashing your unlock token again to see if it'll unlock your bootloader.
Sent from my Evita
timmaaa said:
Ok, wow. I'm not sure where to start here. I think perhaps your main problem is that you rushed, and you've tried "every single method" for doing things, when there is usually only one specific method for each scenario you encounter on each device. The key is to be patient and do the proper research, and find the method that is going to fix the problem you're facing. The other key is to stay within XDA, and more specifically to stay within your device forum. Venturing onto other websites is a bad idea, they don't properly distinguish between phone models (and the information is usually plagiarised from XDA anyway). If you can't find the method that's going to fix your problem, then ask here, don't wait until you've royally screwed the device to ask for advice.
I believe the CID is case sensitive so there's why the RUU you want to run isn't succeeding. Go to the Compilation Roll-Up thread in my signature, find the 3.18 root method, achieve SuperCID again using that method, unlock your bootloader again, flash TWRP 2.6 from here, flash a ROM from our development section, get s-off, boom, done. Getting s-off is optional but trust me, you're gonna want it.
Sent from my Evita
---------- Post added at 11:36 AM ---------- Previous post was at 11:28 AM ----------
Actually, just realised the 3.18 root method won't work because it requires a working OS. Try flashing your unlock token again to see if it'll unlock your bootloader.
Sent from my Evita
Click to expand...
Click to collapse
Nice, I was hoping hear from you timmaaa, but unfortunately, looking at that root method, as well as any that I have seen in my searches, requires that I be in adb, which as far as I know cannot be done unless the phone boots up, but I do not have an OS, so the phone will not boot up for me to go through with adb commands. Is there something I'm missing? or is there a workaround?
You're correct about me having rushed the process. Well, I didn't at first, but after the first few days, I began to just try anything I could get my hands on, and believe it or not, that was a year ago, so every once in a while I'll grab the phone and try searching some new things, but it's not like there are an infinite number of ways to go about things :\ Thanks for the help so far though, really
edit after seeing your edit: hahaha! yeah, you caught yourself perfectly! Also, in response to your question: I've tried flashing the unlock token through multiple different programs, but to no avail. As you said, I royally screwed myself in thinking that I could put back my CID (but my stupid self didn't put uppercase letters), and I thought I'd still be able to use my unlock token since I had gotten the code beforehand and it worked multiple times before, but I was mistaken
To be honest, I think your only option right now is a jtag repair. I don't think your unlock token is going to work because you no longer have SuperCID.
Sent from my Evita
---------- Post added at 12:33 PM ---------- Previous post was at 11:55 AM ----------
The reason your unlock token isn't working is because it's looking for the same CID you had (11111111) when you unlocked the first time. So jtag is the only thing that's gonna resurrect your phone.
Sent from my Evita
timmaaa said:
To be honest, I think your only option right now is a jtag repair. I don't think your unlock token is going to work because you no longer have SuperCID.
Sent from my Evita
---------- Post added at 12:33 PM ---------- Previous post was at 11:55 AM ----------
The reason your unlock token isn't working is because it's looking for the same CID you had (11111111) when you unlocked the first time. So jtag is the only thing that's gonna resurrect your phone.
Sent from my Evita
Click to expand...
Click to collapse
Please tell me it isn't so! I hate myself...I'm stuck with my girlfriend's HTC Droid DNA (absolutely love this phone, but no LTE for T-Mobile since it's a Verizon exclusive phone), and now I'm finding out I screwed myself over and have an awesome paperweight that I need to pay someone else to repair (I'm assuming JTAG repair is some sort of service facilities offer? That's what my search online showed)
I hope maybe somebody else could chime a differing view on this, but thank you timmaaa for your help and time
Ruu while in fastboot mode.no?
Edit my bad just noticed the part about lower case cid
Sent from my One XL using xda app-developers app
EsoteRIcalfreaK said:
Please tell me it isn't so! I hate myself...I'm stuck with my girlfriend's HTC Droid DNA (absolutely love this phone, but no LTE for T-Mobile since it's a Verizon exclusive phone), and now I'm finding out I screwed myself over and have an awesome paperweight that I need to pay someone else to repair (I'm assuming JTAG repair is some sort of service facilities offer? That's what my search online showed)
I hope maybe somebody else could chime a differing view on this, but thank you timmaaa for your help and time
Click to expand...
Click to collapse
Unfortunately for you there is no differing view. You've gotten the phone to a point where it cannot be resurrected via traditional means. Jtag is indeed your only option, and yes it's a repair service. They hook your motherboard up to a riffbox and push the partitions to it, you can even request things like s-off. There's a user here on XDA called zarboz who does jtag repairs, and I believe he's the cheapest you'll find. He's based out of Ohio I think. Contact him via PM for details.
Sent from my Evita
Great, I have an awesome paperweight that I made myself, and the person that I could talk to so that I could get help doesn't accept private messages from someone who has less than ten posts, hahaha
I'm so hoping that the head of HTC's development department somehow joins the forum and tells me that I just need to fastboot some crying smiley face symbol and the phone will start dancing for me until everything goes back to it's original factory settings...why hasn't HTC adopted Samsuck's and Crapple's software reset through their syncing program yet?!?!
The RUU is HTC's version of software reset. The problem isn't a lack of reset program from the manufacturer, the problem is the fact that you changed the CID incorrectly.
Sent from my Evita
I can't believe uppercase and lowercase make a difference though
Also, I tried executing the RUU in multiple different ways, even when the OS was operable, in the last year, multiple times, with multiple different versions, but I was always presented with an error of some sort and the RUU setup would cancel and close. The first thing I tried after every exploit that I did was to run the RUU, so I really don't know what else I could have done differently to have gotten the RUU to run without errors, or else I wouldn't have gone this far and tried unorthodox measures to try and revive the poor guy
Of course upper case and lower case makes a difference, this is computing after all. There was always a way to get the RUU to run, right up until the point of writing the CID wrong, if you had asked for help here earlier I'm positive I could have figured it out. It's a matter of having done the right research, and being well versed with the device you're working with.
Sent from my Evita
EsoteRIcalfreaK said:
Nice, I was hoping hear from you timmaaa, but unfortunately, looking at that root method, as well as any that I have seen in my searches, requires that I be in adb, which as far as I know cannot be done unless the phone boots up, but I do not have an OS, so the phone will not boot up for me to go through with adb commands. Is there something I'm missing? or is there a workaround?
Click to expand...
Click to collapse
Is this true? The root method needs to have the phone booted into the OS? adb should work in bootloader (but I never had to do the 3.18 root method personally), so I'm unsure of the answer myself.
EsoteRIcalfreaK said:
I have scoured the internet for a solution, but my phone is from Hell.
Click to expand...
Click to collapse
EsoteRIcalfreaK said:
why hasn't HTC adopted Samsuck's and Crapple's software reset through their syncing program yet?!?!
Click to expand...
Click to collapse
Stop blaming the phone, HTC, etc. Its pretty clear that the main problem was your lack of research and understanding. For any phone, the proper research (preferably a few hours at least) needs to be done before attempting any mods. You've found the consequence of rushing the process, and have only yourself to blame.
No offense intended, but its clear you have a lack of understanding of many of the basic concepts, rules, etc., and have also been rushing forward trying a lot of methods that are not completely applicable to your case. This is absolutely not the correct methodology when modding a phone.
EsoteRIcalfreaK said:
I can't believe uppercase and lowercase make a difference though
Click to expand...
Click to collapse
How is that so unbelievable? As timmaaa mentioned, case is often crucial when it comes to computers. Since when is syntax not important when typing computer commands?
For the CID in particular, its obviously all hinging on a handful of crucial characters. So it needs to be typed exactly right.
redpoint73 said:
Is this true? The root method needs to have the phone booted into the OS? adb should work in bootloader (but I never had to do the 3.18 root method personally), so I'm unsure of the answer myself.
Click to expand...
Click to collapse
adb works in recovery or while the phone is stuck at loading screen but not in bootloader. Ofcourse, without an OS there's nothing to grant su. Though, he MAY be able to rewrite his CID using the 3.18 method anyway since I imagine the recovery must have SU or equal permissions..
I am less inclined to want to help after all his whining though :/
exad said:
I am less inclined to want to help after all his whining though :/
Click to expand...
Click to collapse
timmaaa said:
Of course upper case and lower case makes a difference, this is computing after all. There was always a way to get the RUU to run, right up until the point of writing the CID wrong, if you had asked for help here earlier I'm positive I could have figured it out. It's a matter of having done the right research, and being well versed with the device you're working with.
Click to expand...
Click to collapse
redpoint73 said:
Stop blaming the phone, HTC, etc. Its pretty clear that the main problem was your lack of research and understanding. For any phone, the proper research (preferably a few hours at least) needs to be done before attempting any mods. You've found the consequence of rushing the process, and have only yourself to blame.
No offense intended, but its clear you have a lack of understanding of many of the basic concepts, rules, etc., and have also been rushing forward trying a lot of methods that are not completely applicable to your case. This is absolutely not the correct methodology when modding a phone.
Click to expand...
Click to collapse
Guys, guys, please do understand that I did many many hours of research before attempting anything. It wasn't until just recently that I began to just go plain crazy and just throw whatever I could get my hands on into commands and such (and that was all done in the matter of one frustrating night actually, so for almost two years I researched and learned things from mostly this board and tried different methods I found useful). You should see the bookmarks I have created on my browser (I deleted a bunch of useless ones recently, but I have 24 as of right now just explaining One X things)!
If you read closely (I know, I have written a lot, because I have seen people get completely flamed for not writing enough information), I mentioned that I have been trying to revive this phone for over a year now (two years this month). The reason I didn't ask for help earlier, which I wanted to do from day one, is for respect to exactly you guys...
1. I was about to make an account on here and post the very first day I got the phone, but after watching the introduction/noob video on YouTube for this website that explains the rules and what to do before EVER posting ANYthing, I decided to do a little more research and do my best to listen and learn from all the tutorials and great help you guys have given to others.
2. I wanted to make sure, as the video and as many of you mention on this forum, to try every avenue and method before coming for help. I did so precisely for the reason of not wanting to look as though I'm "whining". I might have exaggerated a bit in saying that I threw everything I found at the phone, because I did not just blindly do things without the proper research.
The OS I "accidentally" deleted in hoping to get rid of whatever software was on there that really was not changing or allowing me to RUU or anything. I thought that if I deleted it, it would be easier to put a fresh genuine stock copy on it. I was mistaken, and by the time I realized, I had done the damage to the phone. The biggest mistake that caused this irreversible damage was MY OWN unfortunate way of thought of thinking that uppercase and lowercase wouldn't make a difference (actually the truth is, I thought the original CID was lowercase, but seeing as how I had spent almost two years on this project, and I had had a very long day, I didn't double check to make sure, and I figured that I would be able to go back and change it worst case scenario...this my MY mistake, and I am by no means whining or complaining for MY OWN MISTAKE).
All that being said, please gentleman, if there is anything I could do to revive this phone and reverse my wrong-doings, I would appreciate it greatly and be forever grateful. I assure you, I will not perform a single step without confirming that I am doing the right thing. I am definitely wanting your help, and I definitely do seek to leave behind something that other people who make similar mistakes to mine can look back on for future reference.
Long story short, I messed up, it's my fault, I'm not complaining or whining, my Crapple and Samsuck comments were just to poke fun at those companies, and I would really appreciate it if anyone could help me in any shape way or form. Thank you beforehand
Erik
Good, then try this. You should have adb access within TWRP.
http://forum.xda-developers.com/showthread.php?t=2285086
exad said:
Good, then try this. You should have adb access within TWRP.
http://forum.xda-developers.com/showthread.php?t=2285086
Click to expand...
Click to collapse
Thanks for the info, but I tried doing adb commands while the phone was stuck at the "HTC quietly brilliant" boot screen, as well as in recovery, but the phone isn't detected. I do not have TWRP. I have a stock recovery (Android system recovery <3e>). Any other way to do adb commands in my situation? Thanks beforehand
To be honest I think this was dubious at best, it was worth a try but I didn't hold much hope for it actually working. The only place it might have worked would have been in TWRP, even then your system was wiped so the structure required for the commands doesn't even exist in the partition. Someone else chime in here if I'm wrong, but I still believe jtag is the only option out of this.
Sent from my Evita
EsoteRIcalfreaK said:
Thanks for the info, but I tried doing adb commands while the phone was stuck at the "HTC quietly brilliant" boot screen, as well as in recovery, but the phone isn't detected. I do not have TWRP. I have a stock recovery (Android system recovery <3e>). Any other way to do adb commands in my situation? Thanks beforehand
Click to expand...
Click to collapse
You have stock recovery!? -_- I think timaaa is right then -_- I will flash stock recovery and test ADB just to be sure, just for you homeboy. I will post an update shortly.
---------- Post added at 03:21 PM ---------- Previous post was at 03:05 PM ----------
Yeah, sorry man, Jtag only.