I just wanted to share the big mistake I made because I didn't realize that there were more then one variants of my phone...
My wife bought me a new HTC One X for Christmas at full retail so we didn't have to extend our contract. I activated it December 26th.
I rooted it the same day and unlocked the bootloader the following day with no problems.... I didn't do anything else to it for 3 weeks.
Night before last I followed instructions I found online here: http://theunlockr.com/2012/04/28/how-to-install-clockworkmod-touch-recovery-on-htc-one-x/ to install Clockwork mod.
Everything seemed to install and everything seemed fine until I got to the end where I was to type in the command prompt to reboot. The phone shut down and will not reboot. No charge indicator anymore nothing! Won't even go into bootloader now with the Vol- and power button.
After all this I realized (thanks to members on here) that I had installed the wrong version of clockwork mod... I installed the version for the endeavoru when I appearently have something else.
So it probably is/was a stupid mistake on my part for not researching more....I just wanted to tell the other noobs doing this stuff to just please read read read!!!!
I have rooted and replaced the ROM's on all my previous phones and tablets with no problem but I do not do this everyday....Just when I get a new phone so I guess I got cocky and just assumed this one would be just as easy....
So I now have a 3 week old $599.99 paper weight.....
Please be careful and avoid the same mistake I made....
I find myself saying this over and over again on this forum: Don't Google around to random websites for phone mods.
This is a perfect example why. Those websites are not well organized, and therefore will easily mislead you into installing mods to your phone that are not meant for your version of the One X.
Plus, almost all of these "unlock" or "root" webites just steal content from XDA. Look at the webpage the OP linked. It just gives credit by giving a link that goes right back here to XDA. These random websites don't create their own content, they just steal from XDA, and add a few sentences of text that any moron can type, and call the work theirs.
Stick to XDA. As long as you are in the forum that says "AT&T", any ROMs, mods, etc. you find will be safe for the AT&T version of the One X, and its other dual core S4 variants.
There are a few other reputable websites with Android mods. But unless you know for a fact they are legit, its better to assume they are not, and stick to XDA.
Its really that simple.
I agree however I didn't just "Google" the recovery install instructions. I got to this page from a link in an XDA post I had read. Problem was I was apparently in the wrong HTC ONE X Forum. The instructions listed on the site are correct for the "Other" version of the phone.
It's an easy mistake to make with the way this site delivers a search. Example: Go up to the top of the page where it has a search box and says "Find your device"
Type in HTC ONE X. Look at which model the search returns. The International model, Not our AT&T version. Granted I should of read a little more closely, I didn't. The picture was my phone so I scrolled down and began reading threads.
If there are more then one variant of the same phone then both should appear when you search for a device so we can pick the correct version. I was unaware there were different versions of the HTC One X until today....
so it is what it is, I can't go back and do it all over and It's been a very expensive lesson learned so my post was to encourage other noobs to read read read so this doesn't happen to somebody else.
I'll eventually go buy another One X and might even go extend my contract and get one sooner.....either way, next time I'll know.
(Going back to my shattered screen Inspire has not been a pleasant experience, makes me really miss the One X)
Take care.
Man that sucks soooooo bad... Which rom did you pick? It sucks you used cwm.. If you would have used twrp there's a 94% chance it would have just failed instead of flashing.... Sorry for your luck bro.
Sent from my One X using Tapatalk 2
InflatedTitan said:
Man that sucks soooooo bad... Which rom did you pick? It sucks you used cwm.. If you would have used twrp there's a 94% chance it would have just failed instead of flashing.... Sorry for your luck bro.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
i think he bricked by flashing wrong cwm, not rom.
Honestly, how ridiculous is it that AT&T called the One XL variant the One X. Poor name choice has lead to problems like OP experienced.
ethantarheels123 said:
i think he bricked by flashing wrong cwm, not rom.
Click to expand...
Click to collapse
The problem isn't with cwm... You can run cwm all day everyday. Problem is its not supported, people been getting their sdcard wiped and what not. The problem with running cwm is that it doesn't restrict what's being flashed IF its not supported. He would have flashed an international rom, and cwm let it happen.
The international Devs worked in their ROMs to fail in twrp for our device..
Sent from my One X using Tapatalk 2
Hmm I wonder if the jet tool could help unbrick it, or is after flashing a wring recovery it to late? I don't have experience unbricking phones, just throwing out there.
scribed on my soon to be sold for note 2 one x!
jessepatty said:
I agree however I didn't just "Google" the recovery install instructions. I got to this page from a link in an XDA post I had read.
Click to expand...
Click to collapse
I find it odd that an XDA post links to the page you posted, since that page just links back to XDA, and doesn't seem to contain any unique or original content. That's why it seemed that you had "Googled" for that webpage, which seems to be what too many people are doing. My apologies since this is not the case, so maybe I should make my font smaller in the post above! ;-P
jessepatty said:
Problem was I was apparently in the wrong HTC ONE X Forum. The instructions listed on the site are correct for the "Other" version of the phone.
Click to expand...
Click to collapse
Yes, its still easy to confuse the variants on XDA, but at least XDA has the forums split apart at all, and makes the distinction between the dual and quad core versions (not the case on most other fly-by-night "root" or "unlock" websites).
Its too late for your current phone. But if you replace it with another AT&T One X, in the future just stick to this forum section and you will be safe from flashing the wrong mods: http://forum.xda-developers.com/forumdisplay.php?f=1538
Use the button "SEARCH THIS FORUM" button instead of the one at the top of the webpage, and you will always stay within the forum for the AT&T version.
And as I mentioned in my previous post, make sure the webpage you are looking at makes mention of "AT&T, Rogers etc." at the top of the page, and you are sure to be in the correct forum section.
You can also take a look at my Index thread, which has most any resource you will ever need: http://forum.xda-developers.com/showthread.php?t=1671237
Everything listed on this Index is specific to the dual core AT&T version and its variants.
jessepatty said:
If there are more then one variant of the same phone then both should appear when you search for a device so we can pick the correct version. I was unaware there were different versions of the HTC One X until today....
Click to expand...
Click to collapse
I've had 5 different smartphones/tablets going back to old Windows Mobile days, and every one of them has had multiple variants, some even having CDMA and GSM variants in the same forum section (but with seperate subforums). In the past you often had to be very careful and verify that you weren't flashing a ROm for the wrong variant (such as flashing a CDMA ROM on a GSM phone). The way XDA is organized for the variants of the One X is actually less confusing than many other devices.
Its good to keep in mind on any smartphone device to research as much as possible, and make sure you are doing mods specific to your version, before doing anything.
ethantarheels123 said:
i think he bricked by flashing wrong cwm, not rom.
Click to expand...
Click to collapse
InflatedTitan said:
The problem isn't with cwm... You can run cwm all day everyday.
Click to expand...
Click to collapse
Actually, if you flash CWM Touch Recovery from inside ROM Manager, you can get a brick. The version in ROM Manager is for endeavour, and it bricks largely for the same reason the endeavour roms do.
iElvis said:
Actually, if you flash CWM Touch Recovery from inside ROM Manager, you can get a brick. The version in ROM Manager is for endeavour, and it bricks largely for the same reason the endeavour roms do.
Click to expand...
Click to collapse
Oh... Ill respectively take my foot out of my mouth lol.
Sent from my One X using Tapatalk 2
To help everyone (Put this in your OP) if you want
Just type : fastboot getvar all
into the Command Prompt before you DO ANYTHING!
This will tell you all your information you need to know about your phone. For ex if its Evita or endevou
InflatedTitan said:
Man that sucks soooooo bad... Which rom did you pick? It sucks you used cwm.. If you would have used twrp there's a 94% chance it would have just failed instead of flashing.... Sorry for your luck bro.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Thanks, it is what it is
ethantarheels123 said:
i think he bricked by flashing wrong cwm, not rom.
Click to expand...
Click to collapse
This is true. I hadn't made it to installing a rom yet.
unitedatom said:
Honestly, how ridiculous is it that AT&T called the One XL variant the One X. Poor name choice has lead to problems like OP experienced.
Click to expand...
Click to collapse
I couldn't agree more (now) LoL
redpoint73 said:
I find it odd that an XDA post links to the page you posted, since that page just links back to XDA, and doesn't seem to contain any unique or original content. That's why it seemed that you had "Googled" for that webpage, which seems to be what too many people are doing. My apologies since this is not the case, so maybe I should make my font smaller in the post above! ;-P
Yes, its still easy to confuse the variants on XDA, but at least XDA has the forums split apart at all, and makes the distinction between the dual and quad core versions (not the case on most other fly-by-night "root" or "unlock" websites).
Its too late for your current phone. But if you replace it with another AT&T One X, in the future just stick to this forum section and you will be safe from flashing the wrong mods: http://forum.xda-developers.com/forumdisplay.php?f=1538
Use the button "SEARCH THIS FORUM" button instead of the one at the top of the webpage, and you will always stay within the forum for the AT&T version.
And as I mentioned in my previous post, make sure the webpage you are looking at makes mention of "AT&T, Rogers etc." at the top of the page, and you are sure to be in the correct forum section.
You can also take a look at my Index thread, which has most any resource you will ever need: http://forum.xda-developers.com/showthread.php?t=1671237
Everything listed on this Index is specific to the dual core AT&T version and its variants.
I've had 5 different smartphones/tablets going back to old Windows Mobile days, and every one of them has had multiple variants, some even having CDMA and GSM variants in the same forum section (but with seperate subforums). In the past you often had to be very careful and verify that you weren't flashing a ROm for the wrong variant (such as flashing a CDMA ROM on a GSM phone). The way XDA is organized for the variants of the One X is actually less confusing than many other devices.
Its good to keep in mind on any smartphone device to research as much as possible, and make sure you are doing mods specific to your version, before doing anything.
Click to expand...
Click to collapse
Thanks....I too have done something, root, unlock bootloaders, install roms, etc over and over going back to win mobile as well and I've never been this careless before. I was in a hurry to get all the AT&T bloatware off it and make it more user friendly so I let my guard down and now have to live with my actions.
ronnyg12 said:
To help everyone (Put this in your OP) if you want
Just type : fastboot getvar all
into the Command Prompt before you DO ANYTHING!
This will tell you all your information you need to know about your phone. For ex if its Evita or endevou
Click to expand...
Click to collapse
THANK YOU!
I will let everyone know that when I got home from work today I found a box at my front door. I opened it up and found a replacement HTC One X. I call and spoke with AT&T questioning why and they said that they went ahead and did a warranty defect on the original phone due to it only being 3 weeks old. So I am excited to say I have a new one in my hand at this time.
Now I just need to start from scratch and figure this out without doing this again. If anyone wants to help walk me through it step by step, I will be forever grateful
Jess
jessepatty said:
I will let everyone know that when I got home from work today I found a box at my front door. I opened it up and found a replacement HTC One X. I call and spoke with AT&T questioning why and they said that they went ahead and did a warranty defect on the original phone due to it only being 3 weeks old. So I am excited to say I have a new one in my hand at this time.
Now I just need to start from scratch and figure this out without doing this again. If anyone wants to help walk me through it step by step, I will be forever grateful
Jess
Click to expand...
Click to collapse
Your new ATT one x probably came with 2.20 software and a new Hboot. I would start reading here:
TOOL KIT NOOB PROOF
Nice all in one tool kit!
eraste said:
Your new ATT one x probably came with 2.20 software and a new Hboot. I would start reading here:
TOOL KIT NOOB PROOF
Nice all in one tool kit!
Click to expand...
Click to collapse
Yes, 2.20...Old one was 1.85
That is what I have, that I used on the first phone.
Thank you
Im having issues with HTCdev.com loading.....keeps timing out. I'm not sure what is up with that.
Gonna try it again tomorrow. Seems like the server is either down or swamped right now.
I did the perm root command in the tool kit which pushed SU to the phone and it says to boot in recovery and run it. I can't seem to get the command line correct to unzip and install SU now. Can somebody post the correct command line to unzip and install SU.
Thanks
jessepatty said:
Im having issues with HTCdev.com loading.....keeps timing out. I'm not sure what is up with that.
Gonna try it again tomorrow. Seems like the server is either down or swamped right now.
I did the perm root command in the tool kit which pushed SU to the phone and it says to boot in recovery and run it. I can't seem to get the command line correct to unzip and install SU now. Can somebody post the correct command line to unzip and install SU.
Thanks
Click to expand...
Click to collapse
The HTCDev.com website is having some serious issues the last few days. Several different users have posted on various posts about the website not working. One user contacted HTC, and they said they are working on getting it back up and running.
You need to unlock the bootloader and install TWRP (custom recovery) before you can flash SU. Once you do those things, just go into recovery, select the install option, and select the SU zip. Its a flashable zip, not something you are supposed to unzip.
redpoint73 said:
The HTCDev.com website is having some serious issues the last few days. Several different users have posted on various posts about the website not working. One user contacted HTC, and they said they are working on getting it back up and running.
You need to unlock the bootloader and install TWRP (custom recovery) before you can flash SU. Once you do those things, just go into recovery, select the install option, and select the SU zip. Its a flashable zip, not something you are supposed to unzip.
Click to expand...
Click to collapse
Thanks....
Yeah I keep submitting my token ID and I get the page that says it was successfully submitted and that I will receive an email with the unlock file attachment but I never get the email... I've submitted it like 4 times now...
I can't do anything else without that file attachment it says I need. I thought I may be able to use the Unlock_code.bin file from my previous phone that died but it says that they are specific to the token ID generated so I guess that is out.
Gonna have to wait until their site is fully functioning before I can proceed.
jessepatty said:
Thanks....
Yeah I keep submitting my token ID and I get the page that says it was successfully submitted and that I will receive an email with the unlock file attachment but I never get the email... I've submitted it like 4 times now...
I can't do anything else without that file attachment it says I need. I thought I may be able to use the Unlock_code.bin file from my previous phone that died but it says that they are specific to the token ID generated so I guess that is out.
Gonna have to wait until their site is fully functioning before I can proceed.
Click to expand...
Click to collapse
Looked in you bulk or spam folders? First time I did it ny email put it there didn't know it twittled my thumbs for almost 2 hours until I noticed it lol. Yea I know I'm an idiot.
Sent from my HTC One XL using Tapatalk 2
Related
i have searched, read and read more. but i am totally stuck on getting a custom theme and dock setup on my rooted phone. is there a how to that is better written than the ones i have come across on start to end on programs, apps, w/e i need to get one of these custom themes working. seems i follow what is there, but get stuck on area's of it, than i search on that to come up with nothing or no info. maybe im just over doing it all in one day on learning all this, lol. im a video person, but havent seen a install video of this. any help or links or something? thanks
tyhodge07 said:
i have searched, read and read more. but i am totally stuck on getting a custom theme and dock setup on my rooted phone. is there a how to that is better written than the ones i have come across on start to end on programs, apps, w/e i need to get one of these custom themes working. seems i follow what is there, but get stuck on area's of it, than i search on that to come up with nothing or no info. maybe im just over doing it all in one day on learning all this, lol. im a video person, but havent seen a install video of this. any help or links or something? thanks
Click to expand...
Click to collapse
Youre asking how to install a theme?? Find once compatible for your rom. Stick it on your sd card. Boot into recovery, and flash it.
Post what problems you are having. Good luck.
Sent from my PC36100 using XDA App
Dredge said:
Youre asking how to install a theme?? Find once compatible for your rom. Stick it on your sd card. Boot into recovery, and flash it.
Click to expand...
Click to collapse
im not even sure which rom to use, i have tried a couple but the adk is where i am stuck at, when i go to command prompt it isnt at the c://adk/etc.. like what all the write ups are at, its at c://user/applications or something of that nature and i type what should be typed in on the /adk part of it and says it can not be found. i tried reinstalling the adk again and same problem, im doing something wrong somewhere i assume or stuck in a spot that i keep doing wrong and not noticing. i just rooted it, so whatever rom i have i am assuming is the stock one since i havent gotten past this yet.
Your in over your head man, seriously, YOU put the sdk where you want it, me, I just put it in C:\sdk to make my life easy when changing directories.
If command line work is not something your familiar with, have patience, enjoy your rom as it is right now and wait until the super easy one click gui programs are created.
Did you buy the phone already rooted, or did you root it yourself?
Dredge said:
Did you buy the phone already rooted, or did you root it yourself?
Click to expand...
Click to collapse
i rooted it myself. also when i right click on tools and im supposed to see open in comand promp or something, that doesnt appear?
tyhodge07 said:
i rooted it myself. also when i right click on tools and im supposed to see open in comand promp or something, that doesnt appear?
Click to expand...
Click to collapse
You say you rooted it yourself, which is great, but the questions you're asking are so far out that it makes it urprising that you did.
UNLESS... you rooted using simpleroot or some ****? If sooooooo, that makes ur questions make a lot more sense.
Anyways you just boot into recovery, and flash the zip from that menu.
It has nothing to do with adb, cmd, or any of that other bull**** you're talking about. Just do what's bolded and stop going 3 miles outside of the box.
TJDuckett said:
You say you rooted it yourself, which is great, but the questions you're asking are so far out that it makes it urprising that you did.
UNLESS... you rooted using simpleroot or some ****? If sooooooo, that makes ur questions make a lot more sense.
Anyways you just boot into recovery, and flash the zip from that menu.
It has nothing to do with adb, cmd, or any of that other bull**** you're talking about. Just do what's bolded and stop going 3 miles outside of the box.
Click to expand...
Click to collapse
I agree, OP, you are way over complicating it dude. What is your build number? Settings> about phone> software information.
If I didn't know better I would almost bet you're trying to troll us. Being a brand new account and all.
Dredge said:
I agree, OP, you are way over complicating it dude. What is your build number? Settings> about phone> software information.
If I didn't know better I would almost bet you're trying to troll us. Being a brand new account and all.
Click to expand...
Click to collapse
build number
1.17.651.1 cl160858
ive tried the reboot and flash thing and nothing happened, said missing filie or something and erased my phone and now vibrate doesnt work? this is after placing them theme on there i want to use and trying to load it in the boot screen. dont know all these names for the android system. prob just so used to messing with the iphones which is what is making this so hard for me, lol.
tyhodge07 said:
build number
1.17.651.1 cl160858
ive tried the reboot and flash thing and nothing happened, said missing filie or something and erased my phone and now vibrate doesnt work? this is after placing them theme on there i want to use and trying to load it in the boot screen. dont know all these names for the android system. prob just so used to messing with the iphones which is what is making this so hard for me, lol.
Click to expand...
Click to collapse
I don't believe you anymore. Even Root tutorials direct you to install a rom after rooting, which would put you at 1.47.65 or whatever even without 2.2 upgrading.
Trying to flash a zip that isn't valid doesn't do anything at all to your phone... it just... doesn't work and sends you on your way. Absolutely nothing you type comes off as a "real" problem.
Anyways, I'm just going to say straight out, that I think you're trolling and that it's sad that you made an account just to waste your time.
I'm done with this thread.
TJDuckett said:
I don't believe you anymore. Even Root tutorials direct you to install a rom after rooting, which would put you at 1.47.65 or whatever even without 2.2 upgrading.
Trying to flash a zip that isn't valid doesn't do anything at all to your phone... it just... doesn't work and sends you on your way. Absolutely nothing you type comes off as a "real" problem.
Anyways, I'm just going to say straight out, that I think you're trolling and that it's sad that you made an account just to waste your time.
I'm done with this thread.
Click to expand...
Click to collapse
think what you would like, im not a kid. ive answered your questions. computers or phones is nothing new to me. family works for sprint, but will not mess with the rooting part of it. so i was left alone on this. ive searched and searched and what u have read is where i am at. basically i am wanting a custom theme. i have tethering and all that crap that works fine. but a theme wont work and a rom to be 1.47 or whatever was never put on, i have what i posted and have everything a rooted phone should have. obviously im stuck on that rom part of it. no reason to be a **** or call someone a troll or say their trolling, when their asking questions. if ur intentions wernt to help, than dont reply. u wasted ur own time.
So it seems like we'll need to fight over at the Microsoft forums if we're to try to stay up-to-date. I need you to contribute to my post over at msdn here: http://forums.create.msdn.com/forums/p/78753/476964.aspx#476964
Maybe if enough of us hit'em, we can get some kind of answer. Dev phones should have been the first to be updated.
Still no updates for Taylor.
It says in the forums that you linked to that there will be no updates for the Samsung Taylor phones.
the92playboy said:
It says in the forums that you linked to that there will be no updates for the Samsung Taylor phones.
Click to expand...
Click to collapse
Seems like there won't be and update for LG Panthers either.
Anyone wanna trade for an Android device?
Might be a newb question here but....
Did people have to pay for these developer phones? Or did MS just send them out to registered/respected developers?
I suppose, you can flash your phone with the Omnia 7/Quantum ROM at your own risk.
the92playboy said:
Might be a newb question here but....
Did people have to pay for these developer phones? Or did MS just send them out to registered/respected developers?
Click to expand...
Click to collapse
Yup, Microsoft just sent them out.
day2die said:
I suppose, you can flash your phone with the Omnia 7/Quantum ROM at your own risk.
I would like to give th Quantum ROM a try , but I do not know where to start. I am a Bell user in Canada so I think they have the Quantum. I used to flash old WM and Android Devices all the time, but WP7 is new to me. Anyone have a thread or no if anyone has sucessfully flashed a LG Panther to anything else? I can get into a bootloader, but it is probably just Microsofts bootloader.
Click to expand...
Click to collapse
NevinM said:
day2die said:
I suppose, you can flash your phone with the Omnia 7/Quantum ROM at your own risk.
I would like to give th Quantum ROM a try , but I do not know where to start. I am a Bell user in Canada so I think they have the Quantum. I used to flash old WM and Android Devices all the time, but WP7 is new to me. Anyone have a thread or no if anyone has sucessfully flashed a LG Panther to anything else? I can get into a bootloader, but it is probably just Microsofts bootloader.
Click to expand...
Click to collapse
Looks like it's really possible, because i succesfully connected to the phone using QXDM, and even downloaded NAND's image (it's raw, so for extracting page size required, because size in the partition table is relative to page size). Though may flash it, i think bootloader will work. But you probably can get bricked device. Unfortunally i have no enough time for explorations.
Click to expand...
Click to collapse
Useless guy said:
Looks like it's really possible, because i succesfully connected to the phone using QXDM, and even downloaded NAND's image (it's raw, so for extracting page size required, because size in the partition table is relative to page size). Though may flash it, i think bootloader will work. But you probably can get bricked device. Unfortunally i have no enough time for explorations.
Click to expand...
Click to collapse
I think flashing the unbranded Optimus 7 ROM would be the best bet for us. There is a registry key named "HasKeyboard" that's defaulted to 0 that we can change to 1. That might be the way to go. Also I'm wondering if we'd have to go the goldcard method to move over to a Quantum or Optimus rom.
The problem is I don't have another phone and there's no MTTY process to unbrick our phones so I'm a little hesitant to try.
fb401 said:
Useless guy said:
I think flashing the unbranded Optimus 7 ROM would be the best bet for us. There is a registry key named "HasKeyboard" that's defaulted to 0 that we can change to 1. That might be the way to go. Also I'm wondering if we'd have to go the goldcard method to move over to a Quantum or Optimus rom.
The problem is I don't have another phone and there's no MTTY process to unbrick our phones so I'm a little hesitant to try.
Click to expand...
Click to collapse
Goldcard isn't required. Only HTC devices require it.
I've dumped my ROM, so if bootloader will work (i hope), device can be easily flashed.
Is anyone wanna to try? QPST can flash certain partitions (looks like only dsp1 and efs are required for succesful update). Unfortunally i can't risk my phone, because i'm developing an application.
Click to expand...
Click to collapse
Not being rude, but are people complaining that a phone that they received for free is not getting the update and not being continued? If you never paid anything for it in the first place, what are you out then?
the92playboy said:
Not being rude, but are people complaining that a phone that they received for free is not getting the update and not being continued? If you never paid anything for it in the first place, what are you out then?
Click to expand...
Click to collapse
Not every got it free.
Me to...
I am not sure if it is worthwhile attempting a flash. The problem is we are all developers and having no device is probably not worth the risk. I have not flashed anything WP7 so I am pretty hesitant. Is this the link to flashing info you guys are considering?
http://forum.xda-developers.com/showthread.php?t=935605
In reading the other threads, there is no real confirmation on the Panther not getting updated. It is clear the the Taylor will not. I am curious if we are running the exact ROM that another device is? If so, ROM from those devices may work. I am trying to remember what the download name was (was it Pacific or something?). I deleted the file. If I still had it I would consider giving flashing a try. I wish Microsoft had not shut down the microsoft connect site for these phones. Any thoughts?
the92playboy said:
Not being rude, but are people complaining that a phone that they received for free is not getting the update and not being continued? If you never paid anything for it in the first place, what are you out then?
Click to expand...
Click to collapse
I got mine off of eBay due to it being the best keyboard phone out at the time (the Quantum is a joke), so it wasn't free for me. Once we get a HTC 7 Pro here that's compatible with AT&T's 3G bands, I'll switch over to that.
NevinM said:
I am not sure if it is worthwhile attempting a flash. The problem is we are all developers and having no device is probably not worth the risk. I have not flashed anything WP7 so I am pretty hesitant. Is this the link to flashing info you guys are considering?
http://forum.xda-developers.com/showthread.php?t=935605
In reading the other threads, there is no real confirmation on the Panther not getting updated. It is clear the the Taylor will not. I am curious if we are running the exact ROM that another device is? If so, ROM from those devices may work. I am trying to remember what the download name was (was it Pacific or something?). I deleted the file. If I still had it I would consider giving flashing a try. I wish Microsoft had not shut down the microsoft connect site for these phones. Any thoughts?
Click to expand...
Click to collapse
I was thinking more the Europe Open Optimus 7 rom here: http://forum.xda-developers.com/showthread.php?t=935578
Like you said, I can't be without a device so I'm really hesitant to try flashing
Well there is going to be a point where and update or feature will make our phones aka gw910 or Taylor completely useless as for development or testing, so this is something to consider.
Yeah connect has been down since a long time ago I have been struggling to find the FW file provided in the msdn/connect/internet forums, I’m guessing the only way now is to contact either a developer/evangelist/god/msdn who has that file available in storage, with the firmware we can create our own updated custom FW way easier than creating one from scratch and/or experiment with other FW like the optimus 7/Q.
And idea can we consider spoofing the gw910 to an optimus 7/Q .7004 using the registry editor? Making ZUNE update just the components needed.
also im willing to give it a go flashing mi gw910 UsellesGuy any info on how can i dump mi firmware. and posible explanation as in how to recover.I read the bootloader post before but is there anything else i need ?
dragoxt said:
Well there is going to be a point where and update or feature will make our phones aka gw910 or Taylor completely useless as for development or testing, so this is something to consider.
Yeah connect has been down since a long time ago I have been struggling to find the FW file provided in the msdn/connect/internet forums, I’m guessing the only way now is to contact either a developer/evangelist/god/msdn who has that file available in storage, with the firmware we can create our own updated custom FW way easier than creating one from scratch and/or experiment with other FW like the optimus 7/Q.
And idea can we consider spoofing the gw910 to an optimus 7/Q .7004 using the registry editor? Making ZUNE update just the components needed.
also im willing to give it a go flashing mi gw910 UsellesGuy any info on how can i dump mi firmware. and posible explanation as in how to recover.I read the bootloader post before but is there anything else i need ?
Click to expand...
Click to collapse
Microsoft delivers updates using binary patches, they apply only to concrete file version, else they will be broken (or updating will be failed).
Thank you, but i think better way is to wait a bit, until situation about updates will clear up. If update will be not received - i'll begin my work
Useless guy said:
Microsoft delivers updates using binary patches, they apply only to concrete file version, else they will be broken (or updating will be failed).
Thank you, but i think better way is to wait a bit, until situation about updates will clear up. If update will be not received - i'll begin my work
Click to expand...
Click to collapse
On twitter I've tired contacting @winphonesupport as far as our phones being updated. They replied: "Let us see if our team knows and we'll get back to you. ^EB"
I haven't gotten another answer back yet. I doubt I'll get one at all honestly.
quick question about updating a developer device
Hi
I'm a complete newby about wp7.
I've two Optimus 7 in my possession that seem to be developer devices.
Here the phones info:
OS Version: 6516Mainline
SW Version: LG-E900AT-00-V08d-ORG-UK-JUL-24-2010
HW Version: E
More info:
OS Version: 6516Mainline (buildlab).20100713-1228
Firmware revision number: 0.8.4.10
Hardware revision number: 0.1.5.0
Bootloader version: 1.4.1.0
Chip SOC version: 0.30.2.0
Now I've tried to update the firmware like in this post:
http://forum.xda-developers.com/showthread.php?t=935578
But it doesn't work (LGDP2 connect to phone start the update but give the error 1002)
Is there a way to flash these phones to be like normal phones? (I don't intent to develop on them) Or my hardware version is to old (prototype)
Thanks for the help
fb401 said:
I think flashing the unbranded Optimus 7 ROM would be the best bet for us. There is a registry key named "HasKeyboard" that's defaulted to 0 that we can change to 1. That might be the way to go. Also I'm wondering if we'd have to go the goldcard method to move over to a Quantum or Optimus rom.
The problem is I don't have another phone and there's no MTTY process to unbrick our phones so I'm a little hesitant to try.
Click to expand...
Click to collapse
so you are relying on a dev phone that MS was gracious enough to give you as your only device and are complaining that you didn't get the update???
edit: after reading your replies, this wasn't a publicly released phone, so if you don't get the updates, I don't feel you have a complaint.
I see a lot of people having problems and lost how to relock bootloader to update via RUU. This is a quick little tutorial. This works with AT&T that I've tested but should work with.others Mods I'm sorry if I'm posting this in the wrong place...but it feels right here.
If you are relocking make sure you have SuperCid.....
Open command where your SDK tools are....quick way is to hold shift and right click and choose open command line here. Make sure debugging is checked on. Plug device in charge mode, and type adb command as followed below.
"fastboot oem lock"
Now you should be relocked on bootloader. While in bootloader run the RUU 1.85 exe file and follow instructions....takes about 15 min or so to complete. Once done the phone will reboot. Enable debugging once again under developer options. Got to the HTC dev page to unlock bootloader....follow instructions to unlock....use option all other supported devices..... obtain token to unlock bootloader...I hear you can use the old token but this is how you obtain new one just incase.
Place the token bin file inside your SDK tools folder....fire up command prompt once again, go reboot into your bootloader on phone, connect phone to pc, and type adb command as followed...
"fastboot oem get_identifier_token"
Then select yes on phone....blah blah...phone will reboot...once rebooted enable debugging again, go to power options and turn off fastboot....then power off phone......go into bootloader by holding volume down and power and make sure bootloader says unlocked...if not run token identifier command again...took me two trys to get it.....I've heard others take more tries.....if it says unlocked....reboot phone....flash cwr...you can use the one click recovery on this forum..... Then reboot into recovery and go happy flashing on your now updated device. I'll update later, I was just typing this up real quick at work. I might make a bat tool to make things easier.
There is already a thread started on this topic in the General section
http://forum.xda-developers.com/showthread.php?t=1675312
This same thing is posted in General I believe by a different user and also in every forum thread I've come across today lol.
Oops sorry didn't know that...I'm sorry...mods you can delete then...sorry guys...didn't mean to step on toes
This is getting redundant
Sent from my HTC One X using Tapatalk 2
mrjaydee82 said:
Oops sorry didn't know that...I'm sorry...mods you can delete then...sorry guys...didn't mean to step on toes
Click to expand...
Click to collapse
No reason to be sorry, you're only trying to help
freshleysnipes said:
No reason to be sorry, you're only trying to help
Click to expand...
Click to collapse
I agree.
Just my 2 cents, I don't regularly comb the General subforum to add important threads to the Index sticky thread. I'd personally rather guides like this be posted in Development. Although I think its inevitable that some useful info is going to end up in General.
plus, i think a .bat tool would be very helpful in this instance. would love if that could be created.
thanks for your work
redpoint73 said:
Just my 2 cents, I don't regularly comb the General subforum to add important threads to the Index sticky thread. I'd personally rather guides like this be posted in Development. Although I think its inevitable that some useful info is going to end up in General.
Click to expand...
Click to collapse
I'm seeing that the One X is a different beast and the users are a bit different too, I bet many won't ever even LOOK in Dev.
This helped me out beyond belief! Even if this was on the forum already, I had not seen it. Thanks for the write up.
This totally belongs in this sub-forum. This is related to modifying boot loaders and working around HTC patching the root exploits in 1.85. This is not "General" material.
As far as it being redundant to what is posted in General, how was one to know? Come one guys.
Also OP, You can use the same token that you initially got when you unlocked on 1.82. You dont need to gen a new one. Just throwing that out there.
I had submitted my reply at the same time as the second poster. It just seems like the same info that a lot of other users have posted else where is all.
Sent from my HTC One X using XDA
Thank you.
I know this has been posted everywhere but the way you worded made it easier.
I finally got it going from another threat but read your take on it and it was easier to follow.
When I get home tonight, gonna write up a .bat tool
scrosler said:
This totally belongs in this sub-forum. This is related to modifying boot loaders and working around HTC patching the root exploits in 1.85. This is not "General" material.
As far as it being redundant to what is posted in General, how was one to know? Come one guys.
Click to expand...
Click to collapse
I posted this guide in GENERAL a few days ago because I felt like there was NOTHING developmental happening here. It is a general how-to on locking and unlocking your bootloader. Nothing new, in a development sense, is happening in this post.
I'm not saying he's wrong, but it's how I felt when I posted this guide in the general section. I suppose it doesn't matter as long as people are finding the help they need.
Moderator needs to move this irrelevant thread.
Sent from my HTC One X using XDA
mrjaydee82 said:
When I get home tonight, gonna write up a .bat tool
Click to expand...
Click to collapse
I actually have the entire process scripted I just didint post it because I dont want to take on that responsibility... I like to focus on ROMS.
If you need help you have my email.
freshleysnipes said:
I posted this guide in GENERAL a few days ago because I felt like there was NOTHING developmental happening here. It is a general how-to on locking and unlocking your bootloader. Nothing new, in a development sense, is happening in this post.
I'm not saying he's wrong, but it's how I felt when I posted this guide in the general section. I suppose it doesn't matter as long as people are finding the help they need.
Click to expand...
Click to collapse
He also delves into custom recovery and that falls under Development. That is not General. With your line of thought the entire "Unlock Bootloader" thread should be in General too because its not technically development?
Sorry not trying to get into a pissing contest I am just trying to show you a alternative point of view.
But we can agree that the that info is useful regarldess of its location...
My thread got hammered with this question when people were updating my ROM. I wish someone made this thread earlier or at least I knew about it. I rarely look at General. Had I seen your thread I could have sent people over there instead of derailing my thread. Oh well. At least I know where to send them now!
And as far as being duplicates, that's a good! Look at any big sub forum and you will see lots of guides on the exact same subject. Each thread explaining it a little different and some threads putting in videos, others with screenshot. There is nothing wrong with too much info. People learn different ways and with different methods / styles of communication.
-Scott
scrosler said:
I actually have the entire process scripted I just didint post it because I dont want to take on that responsibility... I like to focus on ROMS. -Scott
Click to expand...
Click to collapse
Be very nice if you released it.
Pumpiron579 said:
Be very nice if you released it.
Click to expand...
Click to collapse
I sent OP what I have. He can take the scripts over. I like to focus on ROMS. I dont like working with the unlocking aspect.
Okay,
I'm hoping that I'm posting this in the right place, since I'm new here, but here it goes.
I was wondering how to tell if I am able to use a rom. I know the obvious that it has to be for my phone, but what other important things (such as firmware) should I look at to make sure a rom is right for my phone. If there's a thread on this already, or if this is the wrong section please just point me in the right direction.
If the ROM is made for your phone, then it will work completely. If it was made for a phone in the same family of devices as yours, it may work fully or partially. For example, I have the LG P505. I can use any ROM made for the P505. I can use any ROM made for the P500 (which opens the doors to dozens of choices, from only a handful), but the screen driver is wrong, so the colors are messed up, and once the screen goes black, it doesn't come back (lol). To solve it, I have to flash a kernel made specifically for my phone (P505) after flashing the ROM.
If you have a flashable kernel .zip for your phone, you can use any ROM made for the whole family of devices of which your phone is a part.
Vinny Bacon said:
Okay,
I'm hoping that I'm posting this in the right place, since I'm new here, but here it goes.
I was wondering how to tell if I am able to use a rom. I know the obvious that it has to be for my phone, but what other important things (such as firmware) should I look at to make sure a rom is right for my phone. If there's a thread on this already, or if this is the wrong section please just point me in the right direction.
Click to expand...
Click to collapse
Just read the OP of the ROM thread (all of it; more than once). That's where you should find information on compatibility. If its in your device's section, its quite likely it will be compatible. But, you still need to read in case it requires a specific recovery, etc. to be flashed and work correctly.
Thanks for the replies! I've been having problems with boot loops and I was wondering if it was a compatibility issue. where would I get my hands on my phones kernel? I have an HTC sensation currently running sence-o-manic btw
Theonew said:
Just read the OP of the ROM thread (all of it; more than once). That's where you should find information on compatibility. If its in your device's section, its quite likely it will be compatible. But, you still need to read in case it requires a specific recovery, etc. to be flashed and work correctly.
Click to expand...
Click to collapse
I'm having trouble flashing ViperS. the op doesn't specify any procedures, but I get caught in a boot loop after going through the setup. not sure if I'm missing something or if i may have neglected to run a process that the op is assuming Ive completed. Needless to say, I'm completely lost lol.
Vinny Bacon said:
Thanks for the replies! I've been having problems with boot loops and I was wondering if it was a compatibility issue. where would I get my hands on my phones kernel? I have an HTC sensation currently running sence-o-manic btw
Click to expand...
Click to collapse
Vinny Bacon said:
I'm having trouble flashing ViperS. the op doesn't specify any procedures, but I get caught in a boot loop after going through the setup. not sure if I'm missing something or if i may have neglected to run a process that the op is assuming Ive completed. Needless to say, I'm completely lost lol.
Click to expand...
Click to collapse
Thanks for the replies! I've been having problems with boot loops and I was wondering if it was a compatibility issue. where would I get my hands on my phones kernel? I have an HTC sensation currently running sence-o-manic btw. I'm having trouble flashing ViperS. the op doesn't specify any procedures, but I get caught in a boot loop after going through the setup. not sure if I'm missing something or if i may have neglected to run a process that the op is assuming Ive completed. Needless to say, I'm completely lost lol.
Vinny Bacon said:
Thanks for the replies! I've been having problems with boot loops and I was wondering if it was a compatibility issue. where would I get my hands on my phones kernel? I have an HTC sensation currently running sence-o-manic btw. I'm having trouble flashing ViperS. the op doesn't specify any procedures, but I get caught in a boot loop after going through the setup. not sure if I'm missing something or if i may have neglected to run a process that the op is assuming Ive completed. Needless to say, I'm completely lost lol.
Click to expand...
Click to collapse
If you go to sensation forum instead of posting in general there will be A LOT more people there to help you.
Once you get there, read stickied thread by malybru called something like "great starting point for new sensation users" in Sensation general, and if you still have questions after that, go to Sensation Q&A , find another stickied thread called "Help Thread" and ask there.
Yep so I tried to install CM11
and the last thing was to:
fastboot flash boot boot.img
and that was it. Cannot restore my Nandroid backup - it doesn't boot back up.
Just gets stuck at the HTC page with "This build is for development purposes".
I think I need the stock boot.img but it is no where to be found.
Any help??
Just paid someone to get the RUU and restore then phone. I have no idea how he found the RUU since no one else here has it. If they have it they are not sharing it.
Who did you find to restore your phone?
808phone said:
Just paid someone to get the RUU and restore then phone. I have no idea how he found the RUU since no one else here has it. If they have it they are not sharing it.
Click to expand...
Click to collapse
I have the same problem. Who did you find to restore your phone? Is it possible that I could contact them?
so basically you paid a guy to google the right RUU???
all you had to do is check your CID (its written on fastboot) and search for that, they really arent that hard to find!!
http://forum.xda-developers.com/showthread.php?t=2140967
also if you're going to keep flashing different roms its also a good idea to keep that RUU on your pc somewhere!!
There was no matching ruu. What no one told me was that you could use a newer ruu than the one you have. Another thing, before you judge, there were no replies to help me so I had no choice. Since then look how many times I have helped others.
chrons6 said:
I have the same problem. Who did you find to restore your phone? Is it possible that I could contact them?
Click to expand...
Click to collapse
As I previously posted, you can use a newer ruu than the version you have installed. That's what the guy did.
In not judging at all man, i just couldnt understand as to why you couldnt fine the info... They guy you paid is no different to you or me, che just searched harder... As for the ruu the name itself tells you its an update... No biggie im glad you got it worked out in the end
Sent from my One S using xda app-developers app
zubeedubs said:
In not judging at all man, i just couldnt understand as to why you couldnt fine the info... They guy you paid is no different to you or me, che just searched harder... As for the ruu the name itself tells you its an update... No biggie im glad you got it worked out in the end
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Did you not read what I said? THERE WAS NO MATCHING RUU! Read OK????
No one told me you could use a NEWER RUU.
If someone - perhaps you had told me, yeah fine, I could have done it. No one helped ok?
BTW: I did a nandroid backup, I had installed custom recovery, rooted with superSU etc... I had adb, fastboot working too. Because I couldn't get an answer I paid someone.
If you have a JTAG machine and you were running a business then maybe you are just like him.
808phone said:
Did you not read what I said? THERE WAS NO MATCHING RUU! Read OK????
No one told me you could use a NEWER RUU.
If someone - perhaps you had told me, yeah fine, I could have done it. No one helped ok?
BTW: I did a nandroid backup, I had installed custom recovery, rooted with superSU etc... I had adb, fastboot working too. Because I couldn't get an answer I paid someone.
If you have a JTAG machine and you were running a business then maybe you are just like him.
Click to expand...
Click to collapse
dude theres no need to get fassy about anything... unless your one s is knock off means that there is a RUU for your device and that you simply couldnt find one in the small amount of time that you searched for one...
and just to gnaw a little more at your flawed logic and sour attitude RUU means "ROM UPDATE UTILITY" so i guess your right in not being able to use a newer one... :good:
AND BTW.. i dont have a jtag but i do run a business and in my line of work we see folk like you everyday, ever so quick to get pi**ed at someone for THEIR OWN mistakes!!!
and maybe if youre that impatient and wound up for your own calamities it serves you right to have paid for a simple task..
---------- Post added at 08:21 PM ---------- Previous post was at 08:14 PM ----------
chrons6 said:
I have the same problem. Who did you find to restore your phone? Is it possible that I could contact them?
Click to expand...
Click to collapse
have a peek at the RUU thread in the dev section and follow the instructions... it really isnt that difficult!!!
? and in my line of work we see folk like you everyday
Right and that's why I have more thanks and posts than you for helping people.
Yes, I know that a RUU has a version number too. I know what it means. If you even took the time to realize that after having to pay, I helped out other people after that so they wouldn't have to pay.
I guess you don't read. I said you COULD use a newer version of the RUU but no one told me.
Where were you when I asked for help? Never mind, you go about yourself and I will continue helping.
In my line of work I know people like you too. You are the type of person people avoid so create your own thread and stop jumping in with unhelpful info.
808phone said:
? and in my line of work we see folk like you everyday
Right and that's why I have more thanks and posts than you for helping people.
Yes, I know that a RUU has a version number too. I know what it means. If you even took the time to realize that after having to pay, I helped out other people after that so they wouldn't have to pay.
I guess you don't read. I said you COULD use a newer version of the RUU but no one told me.
Where were you when I asked for help? Never mind, you go about yourself and I will continue helping.
In my line of work I know people like you too. You are the type of person people avoid so create your own thread and stop jumping in with unhelpful info.
Click to expand...
Click to collapse
about your deluded logic: paying a guy to fix your mistakes is the right info??? seriously?? and thats supposed to help the next guy more than directing him towards the right RUU??? boy you really are a contribution to the comunity...
about your thanks rating: i signed up last month and youve been here since january if youve ever contributed anything on here then you should have more thanks than me, its basic math, also i think i should point out that its a forum and not "thank marathon" nobody wins a prize for them...
as far as helping people: i suppose you have, i dont really care that much either..
lastly: i came on your thread infact to lend a hand, until i saw that youre actually lazy and ready to fire off your mouth at strangers for nothing apart from stating the obvious truth...
so as of now you can take your all your thanks and try and cash them in for the next phone you softbrick and "need" to pay someone else to fix...or maybe not!!!
as for me this discussion is closed as i can only feed a troll so much!!!
808phone said:
As I previously posted, you can use a newer ruu than the version you have installed. That's what the guy did.
Click to expand...
Click to collapse
I understand how the RUU works and how to use it. My problem, though I hope not, may be slightly more unique?
I had previously rooted by ONE S T-Mobile version and it had been working fine. I then decided to try out another rom. I likely flashed an incorrect boot img because it would only reboot into fastboot, but would still allow me to go into recovery. I went to recovery and restored my nandroid backup; however, now the phone will get stuck on the opening HTC screen the red language on the bottom, "this build is for development purposes only." It will hang on this screen for about 20 seconds and then turn off. No loop. When I attempt to power up again, I get a quick horizontal flash of light across my screen and then the orange LED comes on in the top left corner indicating the phone is charging. I then hold down power and again the phone gets stuck on the opening HTC screen with the red language.
My problem is that I cannot get the phone into fastboot
I've received advice on how to enter the bootloader: power off the phone manually by pressing power for 10+ seconds. Then I' should be able to enter the bootloader and fastboot. (Vol down + power)
Unfortunately, no matter how many times I try, using the above method and a variety of other methods, I still can't get past "HTC developmental purposes only" screen. I'm not new to android and have experience with a number of phones, but this is my first HTC. Pretty frustrating thus far. Rather than spend many more hours pulling out my hair and continually going in circles with no progress to show for my efforts, I'd rather pay someone to make the necessary fixes for me.
Any additional advice would be much appreciated.
same problem
zubeedubs said:
about your deluded logic: paying a guy to fix your mistakes is the right info??? seriously?? and thats supposed to help the next guy more than directing him towards the right RUU??? boy you really are a contribution to the comunity...
about your thanks rating: i signed up last month and youve been here since january if youve ever contributed anything on here then you should have more thanks than me, its basic math, also i think i should point out that its a forum and not "thank marathon" nobody wins a prize for them...
as far as helping people: i suppose you have, i dont really care that much either..
lastly: i came on your thread infact to lend a hand, until i saw that youre actually lazy and ready to fire off your mouth at strangers for nothing apart from stating the obvious truth...
so as of now you can take your all your thanks and try and cash them in for the next phone you softbrick and "need" to pay someone else to fix...or maybe not!!!
as for me this discussion is closed as i can only feed a troll so much!!!
Click to expand...
Click to collapse
Just to say that I
chrons6 said:
I understand how the RUU works and how to use it. My problem, though I hope not, may be slightly more unique?
I had previously rooted by ONE S T-Mobile version and it had been working fine. I then decided to try out another rom. I likely flashed an incorrect boot img because it would only reboot into fastboot, but would still allow me to go into recovery. I went to recovery and restored my nandroid backup; however, now the phone will get stuck on the opening HTC screen the red language on the bottom, "this build is for development purposes only." It will hang on this screen for about 20 seconds and then turn off. No loop. When I attempt to power up again, I get a quick horizontal flash of light across my screen and then the orange LED comes on in the top left corner indicating the phone is charging. I then hold down power and again the phone gets stuck on the opening HTC screen with the red language.
My problem is that I cannot get the phone into fastboot
I've received advice on how to enter the bootloader: power off the phone manually by pressing power for 10+ seconds. Then I' should be able to enter the bootloader and fastboot. (Vol down + power)
Unfortunately, no matter how many times I try, using the above method and a variety of other methods, I still can't get past "HTC developmental purposes only" screen. I'm not new to android and have experience with a number of phones, but this is my first HTC. Pretty frustrating thus far. Rather than spend many more hours pulling out my hair and continually going in circles with no progress to show for my efforts, I'd rather pay someone to make the necessary fixes for me.
Any additional advice would be much appreciated.
Click to expand...
Click to collapse
Thankfully I finally figured out how to consistently get my phone to enter into Fastboot; however, no the trouble I'm having is finding the proper RUU. I've tried the 3 T-mobile varients available in the RUU depository found here
http://forum.xda-developers.com/showthread.php?t=2094414
But alas, while I am able to run the RUU program, which enters my phone into a mode where the screen is all black expect for the HTC logo in the middle, I keep on getting error codes. Are there more than 3 RUU varients identified in the depository?
Oh, I should note that I was also able to get into recovery, but my SD was unable to mount so I can't find my Nandroid
Youre at least half Way there, what recovery are you using?? If you can get your PC to see the device try and format the memory to fat32 from PC...
Sent from my One S using xda app-developers app
zubeedubs said:
Youre at least half Way there, what recovery are you using?? If you can get your PC to see the device try and format the memory to fat32 from PC...
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
I believe I'm using TWRP 6.3.0...I'm at work right now and without the phone, but I'm fairly confident that's the recovery. I'll to get the phone into USB mode and see if I'm offered the opportunity to format the memory.
By the way, thanks for the help...it's much appreciated.
chrons6 said:
I believe I'm using TWRP 6.3.0...I'm at work right now and without the phone, but I'm fairly confident that's the recovery. I'll to get the phone into USB mode and see if I'm offered the opportunity to format the memory.
By the way, thanks for the help...it's much appreciated.
Click to expand...
Click to collapse
That won't help. You can fix the sdcrad bug by flashing stock recovery via fastbot and preform "factory reset + clear storage"