Related
Hi All,
My little sister has an Inspire 4g. She's not very tech savvy and wouldn't know the difference between a rom and a skin. She is now on her 3rd inspire because of what sounds to me like a bricking problem. Any help in diagnosing this problem would be great. I searched the forum, but everything i found had to do with rom flashing.
Symptoms:
Phone won't power on unless battery is removed. Once it starts powering up, it gets to the HTC logo and freezes. She waited about 15 minutes and nothing would happen.
This happened over night one night, she woke up and couldn't power on.
It also happened 10 days later with a replacement phone while playing a game.
Any thoughts on the matter?
Thanks,
Ratkid2271
Has the phone been rooted?
mudknot2005 said:
Has the phone been rooted?
Click to expand...
Click to collapse
No, the phone was not rooted. She wouldn't know how to root. Everything is stock, except for a few apps she installed from the market place.
You say she's on now on phone #3. The symptoms you describe occurred on #3, or on all three phones?
In other words, has it been the same exact symptoms that caused her to go through two other phones?
Sent from my Inspire using XDA Premium
The first phone bricked over night, the second while she was playing the game. Her third phone has not bricked yet, but I want to help her prevent it from bricking if I can. She's getting fed up with the phone...
Sent from my MB860 using XDA App
Have you tried a new or different charger?
Sent from my ADR6300 using Tapatalk
C Brown said:
Have you tried a new or different charger?
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
Or especially car charger. Never turn the car on with the phone plugged in. Bad mojo.
Sent from my Inspire 4G using XDA Premium App
First phone that bricked, it was charging from a wallwart over night. The second time it was not plugged in at all...
Sent from my MB860 using XDA App
ratkid2271 said:
First phone that bricked, it was charging from a wallwart over night. The second time it was not plugged in at all...
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Where are these phones coming from? ATT store, best buy, Costco?
I find it hard to believe you'd get 2 bad phones, and be fearing for a third, if the place you got them from are giving you new, not refurbished replacements. I'm not saying it isn't possible, just that it seems unlikely, especially with this phone, from this manufacturer.
Just for piece of mind, you may want to give a closer look at your what/how your sister is using/handling the phone, as well, just to make absolutely sure the problem is indeed a bad batch of phones.
That way if it does happen a third time, you can confidently articulate the symptoms to the place of return. After having to replace more than a couple phones, places might start to get a little more reluctant to keep doing replacements.
FWIW
Sent from my Inspire using XDA Premium
The original phone was purchased at an at&t store. The replacements came from the same store. They were NIB. The only thing that i can think of is that an OTA update was pushed (are they able to force the update, they prompt on my atrix) and she didn't let it finish. Would that brick the phone?
ratkid2271 said:
The original phone was purchased at an at&t store. The replacements came from the same store. They were NIB. The only thing that i can think of is that an OTA update was pushed (are they able to force the update, they prompt on my atrix) and she didn't let it finish. Would that brick the phone?
Click to expand...
Click to collapse
I'm telling you its the midget porn. All the kids are watching it these days
Sent from my Desire HD using XDA App
ratkid2271 said:
The original phone was purchased at an at&t store. The replacements came from the same store. They were NIB. The only thing that i can think of is that an OTA update was pushed (are they able to force the update, they prompt on my atrix) and she didn't let it finish. Would that brick the phone?
Click to expand...
Click to collapse
An failed OTA update could definitely brick a phone, and I have heard of Verizon or some carrier doing a "silent" update, but I don't think one has occurred for this phone yet, though an update is in the works from att.
Besides, I don't think they'd do a major, potentially brick-causing OTA anyways, after what happened with the bell/rogers captivate, or whatever it was, fiasco awhile back.
If the replacements were NIB and from att, that makes me even more skeptical that the cause was a bad batch of phones, especially if the replacements were spaced several days apart, as they get new shipments in, further decreasing the likelihood of 2 bad ones from the same batch.
Sent from my Inspire using XDA Premium
The whole issue of brick by ota update can easily and practically be solved by manufacturers of Android phones distributing desktop update software, similar to blackberry manager software. I know with the Samsung captivate, you can download the kies program to update. But it wasn't distributed with the phone so most users aren't going to be aware. I still yet have to be explained why this isn't in practice.
Sent from my Desire HD using XDA App
my first inspire did this. This was on day one without root. I would think it was probably a bad coincidence. I bet she's in the clear.
Sent from my Xoom using XDA Premium App
laxwillsch said:
my first inspire did this. This was on day one without root. I would think it was probably a bad coincidence. I bet she's in the clear.
Click to expand...
Click to collapse
Do you know what you were doing when this happened?
I wish i actually saw the phone(s) in their bricked state. I feel like i could give better information to everyone. It seems like this is not a very common issue or i would have found at least one other post about it. I'm hoping it was just a fluke. Thanks for all the suggestions guys.
XDA members rock!
I think she's going to have to take a good long look at what she has done with each phone...
- How has she been charging it?
- Did she download the same apps every time? What were they?
- Does she have any friends who have offered to help her tweak the settings or anything on the phone that may have inadvertently messed up something or tried to flash it?
- What sort of environment is it kept in?
- Protective case? Other accessories?
I think these need to be investigated to properly identify the cause. 3 phones dying that quickly may be indicative of a situation that she is creating without KNOWING that she is doing so.
If it bricks after failing a OTA update, and you still got it to boot I don't see why you couldn't run the RUU. Even then if it doesn't fully boot you shouldn't have a problem getting into the boot loader and using a pd98img to recover. It is really hard REALLY hard to completely brick this phone.
mudknot2005 said:
If it bricks after failing a OTA update, and you still got it to boot I don't see why you couldn't run the RUU. Even then if it doesn't fully boot you shouldn't have a problem getting into the boot loader and using a pd98img to recover. It is really hard REALLY hard to completely brick this phone.
Click to expand...
Click to collapse
D'oh, you beat me to it...was just thinking the same thing about using a stock RUU and the bootloader.
Ok, well I'm getting a new HTC Thunderbolt today (Android) and am selling my old HTC DROID Incredible to a friend who's coincidentally just dropped his old Eris into a pool! Anyway, my question is this: I've rooted my D.Inc. and have Cyanogenmod 7.2 on it. Would I/he need to unroot and go back to the stock ROM to use the phone on his own contract? Thanks, let me know.
I don't believe so.
But where did you get CM7.2? There isn't even a 7.1 yet lol.
Sent from my Droid Incredible running CM7.
Thank you.
And you're right. I was messing the decimals up. I meant 7.0.2.1. It's on ROM Manager. lol, sorry for the confusion.
So I'll likely need to un-root?
I don't think you'll need to unroot, although I'm not 100% sure. I hope someone else can chime in with a more certain answer.
And its alright lol I was just like "wait a minute, beta? " lol
Sent from my Droid Incredible running CM7.
Yeah, I'm getting the same semi-certain answers that it'll be fine from the guys on the cyanogenmod forum. I think I'll just take the leap of faith...I don't see why it would be a problem.
I know at one point there was a place on the VZW website to change your phone and you just manually typed in the ESN of the new phone and voila new phone activated.
But, I never did try that w/a rooted phone
chimpsnest said:
I know at one point there was a place on the VZW website to change your phone and you just manually typed in the ESN of the new phone and voila new phone activated.
But, I never did try that w/a rooted phone
Click to expand...
Click to collapse
You don't happen to have a link for that, do you? I think my wife is gonna switch to my OG Droid, now that I have the T-Bolt, but I don't want to have to go back to stock from CM7 to take it back to the VZW store.
You should be able to call in to verizon and change it as well.
Long as you don't have an actual rep look at the phone, shouldn't be an issue.
Just dial *228 from it choose option 1 .. no laws against root just voids warranty and if you use wireless tether you breach terms
Sent from my ADR6400L using XDA App
No you do not need to unroot. Just be careful if you bring it in to Verizon while rooted. I did, but I had my buddy switch my old phone to another family member and activate the new one so I really didn't care.
dirtyfingers said:
No you do not need to unroot. Just be careful if you bring it in to Verizon while rooted. I did, but I had my buddy switch my old phone to another family member and activate the new one so I really didn't care.
Click to expand...
Click to collapse
This is correct, when I got my TB I gave my wife my rooted OG Droid running CM7 and it activated for her just fine. I've also showed off my OG Droid to the reps at my VZW store all the time. Most of them were rocking rooted phones anyway, they just don't like it when you bring it in and try to lie about it being rooted when something goes wrong.
There's a link when he logs in to verizonwireless.com to activate new device. Just type in the ESN and choose a plan. I sold my fascinate running one of adrynalyne's roms and activated fit or my buddy from my thunderbolt that way. No problems at all.
Yeah, it seems to be that everyone agrees it'll work. I've committed to do it. When it's done and if it works I'll post it here for possible info purposes.
I activate them all the time. In most cases you can just dial *228 option 3 and follow the prompts to activate any Verizon phone anywhere. I work for a Verizon retailer.
Sent from my ADR6400L using XDA Premium App
I agree with most everyone but using the website never seems to work. And if the Verizon framework has been removed, good luck getting them to update it.
My suggestion would be to download a normalish Rom/stock and switch it over with him. It's got to be the fastest way. Good luck!
Sent from my ADR6400L using XDA Premium App
There will be no issues activating the phone, you do not have to unroot. Verizon cannot stop you from rooting, you just technically lose your warranty!
fillyo said:
There will be no issues activating the phone, you do not have to unroot. Verizon cannot stop you from rooting, you just technically lose your warranty!
Click to expand...
Click to collapse
lies, their contract says that they can end your contract for using tampered with phones.
So no they can't stop you, but they can end your contract and force you to pay the cancellation fee, refuse to activate the phone, etc if you walk in and happen to talk to the wrong person.
doesn't mean they will, but they can.
No matter what i do, rom i flash, partition i wipe.... wallet force closes and does not work. i am using the nexus 4g. even if i unroot and roll back to 2.3.4 wipe everything multiple ways, accept ota updates just like i did before, wallet fails.
so ive rooted and unrooted before 2.3.7, took the ota and everything was dandy.
all i did was root a few days later and it was done. i am convinced there is some data on the nfc chip just like data was being saved on the gps when switching certain evo roms. Why would simply rooting the phone break wallet when sooo many people are running it rooted? almost wanna take it to sprint....
You need the ke1 radio for it to work on 2.3.7 without hacking it on there
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
You need the ke1 radio for it to work on 2.3.7 without hacking it on there
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Yes remember this is a now unrooted sprint nexus returned to stock with all the proper radio's and all...
Bump
suggestions anyone?
tried taking it to sprint but didnt have time to stick around and wait a few hours....
Same thing happened to me, I called google wallet support they blamed it on me unlocking the bootloader and flashing a custom rom. Basically you're sol unless you can swap it out at sprint. as far as I know. Google isn't responding to this issue.
Sent from my Nexus S 4G using xda premium
rican408 said:
Bump
suggestions anyone?
tried taking it to sprint but didnt have time to stick around and wait a few hours....
Click to expand...
Click to collapse
Also, make sure you're copying the 2.3.7 versions of:
com.android.nfc_extras.jar > system/framework
com.google.android.nfc_extras.xml > system/etc/permissions.
If you know how to sign APKs, make sure Wallet and Nfc have the same signature. If you don't know how, copy over Nfc as well to system/app and wipe cache either way.
Hope that works. Good luck.
Returned the phone to sprint overnight. Wow. The sales people and techs there are completely clueless. Oh well. After me schooling them on everything, they decided to give me a new phone. It will be shipped in a few days.
rican408 said:
Returned the phone to sprint overnight. Wow. The sales people and techs there are completely clueless. Oh well. After me schooling them on everything, they decided to give me a new phone. It will be shipped in a few days.
Click to expand...
Click to collapse
You mean refurbished phone?
Sent from my Nexus S 4G using xda premium
Probably refurbished. From what I understand these phone go through more tests than new phones and still look new. I'm fine with that. If the phone continues to fail (which I doubt) then I can get a new phone.
So I got a new phone from sprint. Interesting I had to set up a new Google prepaid card. Got another 10 bucks...
rican408 said:
So I got a new phone from sprint. Interesting I had to set up a new Google prepaid card. Got another 10 bucks...
Click to expand...
Click to collapse
yea, the prepaid card is tied to the phone's meid. New phone = new meid.
Actually, the whole gw app is tired to the meid. I'm talking to the money market level 2 guys trying to figure out how I funked mine up so badly without swapping phones
Sent from my Nexus S 4G using xda premium
The key is to flash the wallet fix rite on top of the rom you flash. In the same recovery session. Works everytime.
snandlal said:
The key is to flash the wallet fix rite on top of the rom you flash. In the same recovery session. Works everytime.
Click to expand...
Click to collapse
Nope. Did not work for me. Mine was done no matter what I did.
Hey guys, not new to the forums, but just coming back. I have been using an Iphone for the last year or so, and after I upgraded and was unable to jailbreak it (untethered at least), I couldn't take it anymore. I went on to swappa and found what I felt like was a great deal on a brand new HTC One S for $310. I have a question now though. I have been trying out Straight Talk for about a month, and I really have no complaints since much of my data use is over wifi. However, how do I unlock the HTC One S for TMobile so that I can use it with my ATT Straight Talk sim? I'm not even sure I will have to, but it should be here tomorrow and I would like to be prepared. I thought I read you could do this by rooting the phone, but like I said, I haven't been using Android for over a year now so I just wanted to ask the experts. Any help would be appreciated.
Hey there... It's pretty easy. I'm not a noob anymore but im not very advanced either. With that said see the two links I'm attaching.
First root your phone with the one touch tool. It's pretty easy. If you have a mac, run vmware or parallels to do it on windows-that's what I did.
Root: http://forum.xda-developers.com/showthread.php?p=24973565
Then follow the instructions in this post to unlock your phone so you can use your non tmo sim card:
http://forum.xda-developers.com/showthread.php?p=27010217
Hope it works for you. I'd appreciate it if you would hit the thanks if I helped you out.
Sent from my T-Mobile HTC One S. Fo Shizzle.
joecreed said:
Hey guys, not new to the forums, but just coming back. I have been using an Iphone for the last year or so, and after I upgraded and was unable to jailbreak it (untethered at least), I couldn't take it anymore. I went on to swappa and found what I felt like was a great deal on a brand new HTC One S for $310. I have a question now though. I have been trying out Straight Talk for about a month, and I really have no complaints since much of my data use is over wifi. However, how do I unlock the HTC One S for TMobile so that I can use it with my ATT Straight Talk sim? I'm not even sure I will have to, but it should be here tomorrow and I would like to be prepared. I thought I read you could do this by rooting the phone, but like I said, I haven't been using Android for over a year now so I just wanted to ask the experts. Any help would be appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1693491 should be what you are after....
Have a great day!
fsustrength said:
Have a great day!
Click to expand...
Click to collapse
Hey guys,
I just received a TMobile HTC S One today to replace my Iphone. I want to use it with straight talk, but I need to root the phone to unlock it first. I've been following the instructions I was pointed to here on the site, and when I got to the following step, I got stuck:
Type this into your command prompt window fastboot oem get_identifier_token
All my CMD prompt box is saying is < waiting for device >
I'm getting no lines of info like the tutorial says I should. I'm kinda nervous because I have my phone powered on and plug into the computer on that white fastboot use screen with teh android guys on skateboards at the bottom. Can anyone help? I really hope I didn't mess up a phone I just spent over $300 on. I'll be here waiting if anyone can give me a hand. Much appreciated.
Have you installed the HTC drivers on your PC?
Sent from my HTC One S using xda app-developers app
ATSPerson said:
Have you installed the HTC drivers on your PC?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
I think so...weren't they in one of the real files I was told to install at the beginning of that thread?
I don't think you have done any damage to you phone. If adb cannot see it or can't send any data. Which guide are you following?
Sent from my HTC One S using xda app-developers app
ATSPerson said:
I don't think you have done any damage to you phone. If adb cannot see it or can't send any data. Which guide are you following?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1583427
I was following this guide, and then I tried using the software too and had the same problem, at the same step. I did a factory restore from my bootloader screen to get out of that first jam.
joecreed said:
http://forum.xda-developers.com/showthread.php?t=1583427
I was following this guide, and then I tried using the software too and had the same problem, at the same step. I did a factory restore from my bootloader screen to get out of that first jam.
Click to expand...
Click to collapse
Make sure USB debbuging is ON and fastboot is OFF (in settings on your phone). Also, make sure you are using a decent data USB cord (some are only for power, and won't transfer data..that was my problem when I got the same "waiting" screen). Also, try using different USB ports on your computer. Don't know why exactly, but sometimes that helps.
simple.mobile
Hey guys I'm using my HTC one.s on simple.mobile but I can't use the internet unless its on WiFi and I can't see pictures. When people text me them.sorry for all the periods this phone is doing it
pabel101 said:
Hey guys I'm using my HTC one.s on simple.mobile but I can't use the internet unless its on WiFi and I can't see pictures. When people text me them.sorry for all the periods this phone is doing it
Click to expand...
Click to collapse
I think you have to change the APN settings for that
tgtoys said:
Make sure USB debbuging is ON and fastboot is OFF (in settings on your phone). Also, make sure you are using a decent data USB cord (some are only for power, and won't transfer data..that was my problem when I got the same "waiting" screen). Also, try using different USB ports on your computer. Don't know why exactly, but sometimes that helps.
Click to expand...
Click to collapse
The debugging was the problem with the root. Thanks a bunch for that help. Now however I can't seem to unlock my phone from TMobile. I tried everything in the previously mentioned thread, but I keep getting no strings errors. Anyone have any advice?
Nothing worse than having a brand new phone that you can't even use the second day you have it. Man this sucks.
joecreed said:
Nothing worse than having a brand new phone that you can't even use the second day you have it. Man this sucks.
Click to expand...
Click to collapse
Even if you unlock it you will not get full data , only edge speeds ,
Sent from my HTC One S using xda premium
Ok so heres the short of it. I was attempting to root my phone with the Hasoon V1.1 Tool kit and needless to say, everything went wrong. Here's what happened. I did everything to unlock the bootloader. Got my token ID and all that stuff. Next, I loaded the twrp recovery. Cleared everything out of the phone, and went to load a rom. It kept telling me "Failed" when I tried applying the rom. It ended up getting into a boot loop and wouldn't do much. I got it to go back to the recovery when this started and still it wouldn't load any of the ATT Htc One x Roms. I made sure those were the ones I had. Now, at random throughout the process at some point last night, it wouldn't do anything. It has a blank screen. When I plug it in, the status light shows nothing. It was on the charger last night all night, and has not changed. No status light, no screen, nothing! I know you guys are going to ask for more information, but low and behold, like most people you smart guys deal with, I'm a noob. I rooted my google G1, and my HTC inspire without too much trouble, but this is just completely beyond me. As I was doing research I read about problems people were having with the blank screen of death. I'm just worried because I don't have insurance and I'm pretty much screwed without a phone. Does anyone have any input as to what I can do? I'm just beyond aggrivated not having a phone, and I don't have much money to be getting a new one. PLEASE HELP ME
-Mike
Which Rom exactly were you trying to install?
Sent from my HTC One X using xda app-developers app
Which ROM you flashed? Did you successfully root? Can you hold power + volume down to access twrp? Did you try to charge it? What does it do when plugged to computer?
Sent from my One X using xda premium
InflatedTitan said:
Which ROM you flashed? Did you successfully root? Can you hold power + volume down to access twrp? Did you try to charge it? What does it do when plugged to computer?
Sent from my One X using xda premium
Click to expand...
Click to collapse
This, as well as... Which phone do you have, the X or XL. The XL is specific in which rooting method you can use.
Sent from my HTC One XL using xda app-developers app
-Power and volume down do absolutely nothing
-Rom was Endeavoru Cyanogen Mod
-Kernel was Franco Kernel r21
-Plugged into computer, does nothing. No status light, nothing.
I am thinking it wasn't the software that did it. It was plugged into the usb port of my laptop the whole time, but may have died. I read online somewhere if you completely discharge the phone, you need a special charger to charge it. If I loaded the wrong kernel it could have gotten below it's "dead" percentage. Correct me if I'm wrong, but with Lithium Ion batteries, completely discharging them is not good for the battery. If it had nothing to tell it to stop, and the usb port on my laptop didn't keep up with the amount I was messing with it, it could just be completely dead. I don't know. I'm an idiot and I apologize about all the gapps I'm giving you guys with information. I'm doing the best I can, but bottom line is after it didn't work at first, I tried a few different recoveries with Hasoons tool kit, and a couple different roms but the roms never loaded. Always failed.
The phone I have I believe to be the One X, but I don't know the difference. When I booted my phone, it did the HTC Quietly Brilliant screen, then the ATT Rethink possible screen. What is the difference between the one X and one XL? I thought the XL was a larger version of the phone unfortunately, and now I'm seeing differently. It's the ATT phone, 16 gb internal storage, mini sim on the top, Dual Core processor not quad core.
With your battery being so low and possibly even dead when you tried to do anything with it, could have a problem. The other problem, if my memory is correct in what I was reading the Endeavoru cyanogen ROM is for the X only, international version. If yours is AT&T like you say, if the flash was performed correctly.... I hate to say this but you might have a nice $500 paperweight, for now. I would PM Abdolutelygrim and see what he thinks, unless he isn't already here.. his current project is unbricking Evita.
Sent from my HTC One XL using xda app-developers app
minimac21234 said:
The phone I have I believe to be the One X, but I don't know the difference. When I booted my phone, it did the HTC Quietly Brilliant screen, then the ATT Rethink possible screen. What is the difference between the one X and one XL? I thought the XL was a larger version of the phone unfortunately, and now I'm seeing differently. It's the ATT phone, 16 gb internal storage, mini sim on the top, Dual Core processor not quad core.
Click to expand...
Click to collapse
You have what we call an HTC one xl or AT&T one x. The phones look almost exactly the same but the internal components are completely different. (youre in the right forum)
Sent from my HTC One XL
I went through almost the same thing last night, with the exception of my battery dying. In the event that you are able to get the phone to charge, this guide helped me get my phone working again.
Good luck!
The phone was fully charged when I began, and I periodically connected and disconnected it when I was having my initial problems. I deleted my cache dalvic cache, etc everything after I saved all my important pictures and videos and files etc. so I just deleted everything to start over fresh. I don't know what the hell I did. I just figured this wouldnt be too hard since I did it with 2 of my own phones in the past, and a few friends phones also. I think my problem may have been with being ignorant and not knowing there were multiple versions of this phone that all look identical but aren't. Ohhhhhhhh boy. This is bad lol.
minimac21234 said:
I think my problem may have been with being ignorant and not knowing there were multiple versions of this phone that all look identical but aren't. Ohhhhhhhh boy. This is bad lol.
Click to expand...
Click to collapse
That is indeed your problem. The One X and One XL use a different partition layout, and international roms will attempt to overwrite the One XL boot partition. Hboot is wp in 2.20 but not in earlier versions. Even so, you can end up with corrupted firmware even if hboot is untouched. Numerous people have done it. Some devs are working on a way to fix this. Here's the thread, you'll need to get yourself in the queue or just see if you can get a replacement.
http://forum.xda-developers.com/showthread.php?t=1966850
Replacement isn't an option. I didn't get a chance to get insurance on it because I cracked the digitizer within the first 2 weeks of having the phone, and I opened it last night to see if something from when I cracked the digitizer came loose causing the phone to not boot. Thanks for the feedback so far guys. I'm not expecting miracles. I put myself into this mess, I'm just really hoping someone may be able to fix it soon. Not having a phone is really going to put a damper on my side work. Can't get phone calls from people on craigslist if I don't have a phone SH!T
Do you know what firmware your phone was on before you did this........it will be the determining factor if it's fixable atm
Sent from my HTC One XL using Tapatalk 2
I'm wondering if when I was trying to use CWM it screwed me up too. I read in a few peoples signatures that CWM also isn't compatable with the One XL. I feel like the biggest jackass. I'm the computer/cell phone/electronics guy in my area, and now I feel as if I should go into early retirement. I will stay open minded and hopeful that absolutelygrim and others come up with a solution, but bottom line, for all you guys that have made this process damn near idiot proof for people like me, I want to say thanks, and also apologize for all of us noobs that make something as simple as knowing what you are doing before you do it and following directions harder for the developers. It's awesome you guys do what you do in your spare time, only for people like myself to make it more of a hastle. Once again, thanks for trying to fix this guys. My bad.
18th... I was on 2.20. I read that there is a work around for 1.80(I think that's the firmware), but either way, yes I was on 2.20. I have been looking once a week for a new exploit to be able to root the one x, since there wasnt any options until about a week ago if you had 2.20. I bet that's why there are so many people screwing this up. They, like myself, are probably so eager to root it they don't take their time. I remember the first time I rooted my HTC inspire I took about 3-4 hours because I quadrouple checked what I was doing. And damn it am I kicking myself in the ass that I didn't do that this time around.
The problem was the endeavor Rom....but depending on what firmware you were on, 1.85 or 2.20 it can be fixed. If you were on 1.85 or below, it's fixable right now. If 2.20 then not atm.
Sent from my HTC One XL using Tapatalk 2
minimac21234 said:
I'm wondering if when I was trying to use CWM it screwed me up too. I read in a few peoples signatures that CWM also isn't compatable with the One XL.
Click to expand...
Click to collapse
The problem with CWM is that the version for the One XL is an unsupported port. So it's buggy, but the worst I've heard of it doing is corrupting people's sd card or occasionally borking installs, both of which are easily fixable.
The only time I've heard of CWM bricking One XL phones is when people use ROM Manager (which isn't supported for this phone, though GP will let you install it anyway) to install the endeavour version, which causes the same problem as flashing an endeavour rom.
Dang.. I thought it was just icecoldjelly that been banging up peoples OneX. I guess the new hboots aren't as noob-proof as we thought
Sent from my Liquidy Smooth, blazingly fast as f#@k OneXL using xda premium app.
InflatedTitan said:
Dang.. I thought it was just icecoldjelly that been banging up peoples OneX. I guess the new hboots aren't as noob-proof as we thought
Sent from my Liquidy Smooth, blazingly fast as f#@k OneXL using xda premium app.
Click to expand...
Click to collapse
It very well could be just Ice Cold Jelly. There is no guarantee something else I did last night bricked my phone. I know I attempted ICJ, and a few other stupid and ignorant attempts. But, I would guess it was from that.
minimac21234 said:
I know I attempted ICJ
Click to expand...
Click to collapse
There you are. That is surely the culprit.
iElvis said:
There you are. That is surely the culprit.
Click to expand...
Click to collapse
Lol... I knew I could get it out of him
Just jokin, hope everything works out OP... just keep following absolutelygrimm's unbricking thread and hope for a breakthrough
Sent from my Liquidy Smooth, blazingly fast as f#@k OneXL using xda premium app.