Related
Disclaimer: I will not be held responsible for any damage to your phone, your PC or indeed your life from following this guide. The steps in this guide worked for me. If you have problems uninstall everything and start from Step 4 again. Doing this kind of thing could affect your warranty and all that so have a long hard think about it before you go ahead
US Owners - If you flash the UK firmware, you will lose 3g and wifi calling app etc... There are fixes for this problem that can be found on other Forums. A guide on how to restore this which has worked for others is HERE
##WARNING: be careful when flashing 2.51 firmware, firstly its patched so root isn't achievable by the usual methods, and isn't easy to downgrade back to other firmware - I suggest you search and read the various topics on it. My advice is to use 2.21 UK or 2.34 Deblur firmware##
This guide will show you how to debrand your Motorola Defy (Eg bought on T-Mobile UK and want generic UK firmware), or indeed restore the phone if you brick (Eg removing important apps that you shouldn’t have touched!!)
Props go to jutley (Modaco)for his debranding guide for the flipout, and dkspook (Modaco) for his information in other threads, and anyone else who thinks they may have contributed, oh yeah and my Mum.
##Disconnect phone from PC##
STEP 1 Download usb drivers here below
Motorola Drivers Here
STEP 2 Download the debranded Firmware here (To debrand to generic UK I used the one marked UK - choose the one for your country)
Choose Firmware Here
STEP 3 Download RSDLite - I used v4.9, I found earlier versions would not work. Get it here.
RSDLite 4.9 Here
STEP 4 Install the USB Drivers and the RSDLite program and reboot PC
STEP 5 Extract the firmware file you downloaded a while ago. Then copy the .sbf firmware file to c:\Program files\Motorola\RSDLite folder (installation directory for RDSLite). this should come out as JRDNEM_U3_2.21.0_SIGNED_UCAJRDNEMARAB1B80AA028.0R_USAJORDANRTGB_P026_A007_HWp3_S
rvice1FF.sbf for the UK one.
STEP 6 Start the RSDLite program now where it says filename press the select button and find the .sbf firmware file in c:\Program files\Motorola\RSDLite (it should default to this folder) and select the (sbf) file some details will appear on the right hand side.
STEP 7 We now need to boot the phone into the bootloader (as above make sure the phone is disconnected from USB – not sure if matters tho!). Hold the volume up and then power the phone on, after about 5 seconds release the buttons and the bootloader should display - it will show the version and a battery check. Now plug in the USB cable and it should install the drivers . Once the driver installation has finished you should see the phone appear at the bottom of the RSDLite program window under `port 1` - Once this is there you are ready to flash the firmware. NB: I had issues getting it to show a number of times. Uninstalling RSDLite/Drivers, rebooting PC, and then reinstalling these resolved this issue.
STEP 8 Press the start button on the RSDLite and just relax while your device gets flashed,debranded etc. you will see a progress status on the right hand side wait till it reaches 100% but please do not disconect it will reboot the phone automaticly and restart the phone.And just wait untill android comes up and fully running untill you disconnect it should read (PLEASE START PHONE MANUALY) on RSDLite when this shows it is safe to unplug.
Hopefully now you will have a debranded/unbricked phone.
One thing I noticed that was cool is that the data partition stayed intact for me when I debranded, meaning all my settings and installed app (providing you hadn’t moved stuff to /system) were still there after the process – cool! The only thing you will have to do is re-root the device.
Hope you find this useful and I look forward to a great community for the Defy!
Nice job! This worked perfectly. We now just need the tmo us FW. I'm kind of iffy about messing with my phone much more until I have a failsafe.
nitewalkergr said:
Nice job! This worked perfectly. We now just need the tmo us FW. I'm kind of iffy about messing with my phone much more until I have a failsafe.
Click to expand...
Click to collapse
Whats the benefit of the T-Mobile US Firmware - some kind of extra functionality? If we could get it, we could flash by this method and flash back if we didn't like it anyways I suppose.
In theory this method is a failsafe tho because if you mess any thing up you can get back to a different firmware. I must say I personally would like to get my hands on the original T-Mobile UK .sbf, just in case I wanted to put it back to its original state for returns/repair, so if anyone has found it (I haven't yet) please let me know.
If a tmo us user flashes with the uk FW they lose 3g.
A tmo us or just generic us fw would give us the clean sweep option while keeping our 3g.
Can I use the Uk Firm for a Vodafone Spain Defy??
Higgsy said:
Whats the benefit of the T-Mobile US Firmware - some kind of extra functionality? If we could get it, we could flash by this method and flash back if we didn't like it anyways I suppose.
In theory this method is a failsafe tho because if you mess any thing up you can get back to a different firmware. I must say I personally would like to get my hands on the original T-Mobile UK .sbf, just in case I wanted to put it back to its original state for returns/repair, so if anyone has found it (I haven't yet) please let me know.
Click to expand...
Click to collapse
Hi Higgsy, long time no see! Guess its cos you sold your Hero/G2 Touch so you have no need to visit htcdevscene, Its dead there now a days lol. I just got my Defy from T-Mobile UK. I here your after the T-Mobile UK Defy firmware? and I havent rooted or touched the firmware on mine at all, all i've done is charged it up and used as my day to day phone. If you know of a way to pull the firmware from the phone i will gladly upload it for you, if its even possible?
P.s. still got my Hero/G2 Touch not sure if i wanna sell the lil work horse yet lol, what are they selling for these days?
pedrogamo said:
Can I use the Uk Firm for a Vodafone Spain Defy??
Click to expand...
Click to collapse
Yes, I have a simfree defy, and this is my versión. Same version for France, UK, Spain, etc
Cesar Pipes said:
Yes, I have a simfree defy, and this is my versión. Same version for France, UK, Spain, etc
Click to expand...
Click to collapse
Thanks!! I did it. Now my Defy is debranded. Bye Vodafone!
dj_destruction said:
Hi Higgsy, long time no see! Guess its cos you sold your Hero/G2 Touch so you have no need to visit htcdevscene, Its dead there now a days lol. I just got my Defy from T-Mobile UK. I here your after the T-Mobile UK Defy firmware? and I havent rooted or touched the firmware on mine at all, all i've done is charged it up and used as my day to day phone. If you know of a way to pull the firmware from the phone i will gladly upload it for you, if its even possible?
P.s. still got my Hero/G2 Touch not sure if i wanna sell the lil work horse yet lol, what are they selling for these days?
Click to expand...
Click to collapse
Now then DJD!
Na we need the .sbf file for it but it no biggy at the moment. Get it rooted mate - easiest way is to download z4root from the market - works a treat and roots in like 10 secs lol.
Stopped going on htcdevscene for a number of reasons, firstly i could never get on the site and secondly i felt the way it was run was very inconsistent.
Just sold my Hero - they are going for between 80-120 on ebay the top end is for brand new boxed. I have just sold mine to a mobile recycle place for £103. This phone is different gravy to the hero for sure.
Anyway mate look forward to seeing you around again
Thanks for this guide Higgsy, very easy to follow even for a noob like me.
I have now said goodbye to Vodafone's crap a mere 20 minutes after opening the box with my shiny new DEFY in that was delivered today.
milesg said:
Thanks for this guide Higgsy, very easy to follow even for a noob like me.
I have now said goodbye to Vodafone's crap a mere 20 minutes after opening the box with my shiny new DEFY in that was delivered today.
Click to expand...
Click to collapse
No probs - Gone be the dirty network custom apps and splash screens!!
Done too. Thank you.
EDIT: Just reflashed and then calibrated the compass. Seems to be working now. Sorry for the unnecessary message.
Ok, having taken the phone out since I got rid of the Vodafone stuff, I've discovered that the GPS is no longer working. I've got GPS Test on it and it only sees one satellite where before it saw a load. I'm going to reload the firmware now, but does anyone have any ideas?
Higgsy what are the benefits of rooting and flashing the generic unbranded software apart from getting rid of the t-mobile rubbish?
tim440 said:
EDIT: Just reflashed and then calibrated the compass. Seems to be working now. Sorry for the unnecessary message.
Ok, having taken the phone out since I got rid of the Vodafone stuff, I've discovered that the GPS is no longer working. I've got GPS Test on it and it only sees one satellite where before it saw a load. I'm going to reload the firmware now, but does anyone have any ideas?
Click to expand...
Click to collapse
Hmm strange My GPS is fine, locks on in like 5 secs, maybe try rebooting with GPS switched on, if you haven't already done so.
DJD,
No real benefits apart from getting rid of any tmobile crap, there isn't much bloatware in the tmobile uk build anyways. I just like generic lol. And as for rooting - please tell me that question is joke surely as a seasoned veteran you know what that is geezer
I know rooting opens up a world of goodies but there arent any goodies for this phone yet in the way of ROMS, at least thats what i can gather so far lol. Can it be over clocked and JITenabled yet? after rooting it of course, sorry im being lazy n not google-ing lol.
Plus for my totally blonde moment if i flash the generic uk firmware would it still mean i could get the over the air 2.2 update when it is released by motorola before t-mobile release their bloatware version?
dj_destruction said:
I know rooting opens up a world of goodies but there arent any goodies for this phone yet in the way of ROMS, at least thats what i can gather so far lol. Can it be over clocked and JITenabled yet? after rooting it of course, sorry im being lazy n not google-ing lol.
Plus for my totally blonde moment if i flash the generic uk firmware would it still mean i could get the over the air 2.2 update when it is released by motorola before t-mobile release their bloatware version?
Click to expand...
Click to collapse
JIT can be enabled - its not stable imo - I tried it before, gonna have a better look at it.
i would expect you will be able to get the generic 2.2 update, to be fair, I think we will be flashing roms by that time anyways
Anyway stop being a ***** and get it rooted
OI lol,
Just downloaded z4root will put it on my memory card n get root tomorrow me thinks.
p.s z4root is no longer on the market, found the z4root.apk in a thread on here tho luckily lol.
Ok, now I do have a problem. I've flashed the non-branded rom and very happy with it, but my in-call speaker has failed this morning. This seems to be a common problem with the Defy and I suspect it needs replacing or repairing, but I need to put back the branded rom to have the phone in warranty, don't I? How do I even begin to go about that?
tim440 said:
Ok, now I do have a problem. I've flashed the non-branded rom and very happy with it, but my in-call speaker has failed this morning. This seems to be a common problem with the Defy and I suspect it needs replacing or repairing, but I need to put back the branded rom to have the phone in warranty, don't I? How do I even begin to go about that?
Click to expand...
Click to collapse
You can't unless you can find the vodafone .sbf sorry mate it was mentioned at the top of the post.
They probably wouldn't know anyway, just deny all knowledge if they say anything.
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 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
I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
Thanks,
Reffu
Hi,
same issue here. Today the touchscreen stopped working suddenly after i flashed the Android Revolution HD 5.0 Rom yesterday. However, the S-Pen is still working fine. Installing other ROMs and the Stock ROM via Odin did not help. Issue allso appears in Touch-enabled-Recovery.
I see no reason, why this should be a hardware issue, although my N8000 came back from service a few days ago, where they also replaced the screen and digitizer.
Had anyone this issue before and was abled to resolve it?
Greets
I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2
to read this as a Note 10.1 newbie is not very encouraging. are there any similar facts between all of you like
which Note model do you have
how did you jaibreak (which method)
which rom did you have before
which rom do you have now
how did you flash a new rom
...
is there a way to find out whether the touchscreen is really "dead for touch"?
This is a bit scary - my Note 10.1 is arriving today, and I plan to root it at a minimum. I actually don't mind Touchwiz all that much on my Note 2 (which is running CleanROM ACE), so I think I might just root the 10.1 for now.
So restoring completely back to stock (via Odin) doesn't fix it? That is really odd that ROM-ing this thing might cause a hardware failure...
jiggyman said:
I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?
kkretch said:
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?
Click to expand...
Click to collapse
Did anyone solve this, I'm having the same problem.
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
Just curious - did you just root, or did you root and install a ROM?
I am only rooted so far - haven't felt the need to ROM yet - partially due to worries about this happening. I bought a refurb from Best Buy and only get 90 days of warranty.
reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
If they say you got a new one, you got one. They'll tell you otherwise if there's an issue over the phone.
But I wouldn't be afraid of ROMs, but to be more diligent and wise when it comes to choosing them. It's like choosing a poisonous mushroom versus an edible one to make stroganoff or stir fry. If you know what to avoid for the next time and follow the correct process to doing the root and flashing, there will not be an issues.
This is from someone who has soft-bricked my first tablet and learned how to unbrick my SIM-less Captivate and Note 10.1. It's how you apply the method and how much attention you practice not getting stuck into these situations is what matters. Especially since I bricked my tablet via experimentation and un-bricked it on the same day with ease.
It's not some big complex deal of rocket science or something only the mere geniuses can do, its how you perceive yourself and how you act. If you believe that you will suck and brick it to kingdom come , it will happen intentionally or subconsciously.
In this case, it was a freak accident where the file/s accessed and deleted the wrong files which allowed for capacitive touchscreen use, and it should be reported to x developers if you have not done so already.
I have rooted and used the Revolution HD rom, the Rom where you customize the colors of the bar/other things, and on the Captivate, the AOKP Collective. I further customized the latter with the Xperia launcher as it zips.
Did anyone find a repair for this besides replacement? My Note 2 is doing the same thing now.
Has anyone found a fix for the touch screen not working yet??
Anyone have any ideas?
Technicians input for touch problem
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain that follows the instructions on the mod sites exactly as shown step by step will never have a problem, all those that do end up with paper weights or bricks didn't follow the instructions in numerical order.
Believe it or not even if after you have modded a rom and brought it back to standard they know it has been modded as they have a list of problems associated with repairs after roms have been modded so you are only fooling yourself they don't.
Same as the smoker that tells his Dr he has given up even though all the symptoms prove he really didn't.
So in my expert opinion if you play with modding and stuff it up why should you be eligible for a warranty claim ? The manufacturer has sold you or supplied a working item that you decided to f_ck around with and because of your stupidity expect some one else to pay for it.
I am not saying don't mod your phone with all the great roms out there but please to save yourself a lot of pain and cost some poor smuck trying to run a business in these economic times a lot of out of pocket from sending items back for replacement or warranty plus the time it takes to do all the paperwork and such, please please please read the instructions 300% or triple check you are doing everything exactly as the instructions say and you will be enjoying all the new benefits of that customised rom and laughing at all the noobs stuffing up their brand new device from not doing so.
I know this won't fix your problem but reread that last bit it was your problem as you are to clever to follow some one else's instructions
anyone have solution regarding this issue, mine have issue also, can anyone spare how to fix it without changing hardware?
---------- Post added at 06:47 AM ---------- Previous post was at 06:28 AM ----------
i hope anyone can solve my issue with touch not responding
WOW.. on TOPIC Flashing .pit might help ???
Gardum said:
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain
Click to expand...
Click to collapse
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck
erica_renee said:
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck
Click to expand...
Click to collapse
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir
popohunters said:
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir
Click to expand...
Click to collapse
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .
erica_renee said:
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .
Click to expand...
Click to collapse
thanks sir, im done the flashing with pit files+ official firmware but touch screen is still missing, is there a modem file for touch screen maybe i missed it while its in downloading process before i brick the touch screen
any hope out there?????
confused and need help
i have a n8000 , base band version N8000XXCLL1, my touch screen stoped responding while playing a game , only Spen works , tried resetting , but no help, I'm a no-voice when it comes to programing and need a step by step guide >>>> many thanks in advance for all your help
reffu said:
I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
I got the same problem after rooting my phone.... I used the following method and got ride of that Problem. ..
type this star code in in it Phone dialler *#2663#
Now you should see "TSP"
<update>
TAP on TSP ......it will take 5 seconds only....
......
NOW ENJOY ☺☺
Click to expand...
Click to collapse
Are there not any CWM/TWRP Flashable ZIPs for stock or GPE ?
I've just spent frustrating hours trying to get stock or GPE running, on my GSM device that's been happily running CM11 for a while. This in part because I'm running Linux and there's no way to get mfastboot running I guess. Tried under Linux Wine but no luck.
Only after grabbing a windows PC and messing around a bunch have I been able to get CWM re-loaded after a partial install of GPE; The GPE recovery flashed OK but /system failed.
On other popular phones, there have always been flashable ZIPs of stock derived, and GPE derived ROMs. So I could keep custom recovery and easily switch ROMs, in order to test my apps.
If there are no such solutions for MotoG, I'll just have to stick with AOSP ROMs I guess. Is there some technical reason, or just not enough dev interest in ZIP flashable versions of stock and GPE ?
Thanks for any thoughts !
Yeah, I always get nervous with fastboot flashing cause anything can go wrong. Would really love some flashable stock roms. Or atleast a tutorial on how to make one. I have the dual sim version and I am running a GB firmware with cm11 (single working sim). I am guessing that would make things even harder to make a flashable rom to revert to the dualsim firmware (or impossible). Will a simple twrp backup suffice for restoring stock?
Edit: http://forum.xda-developers.com/showthread.php?t=2605824
This might be what you are looking for. Not for dualsim though.
This would be a nice thing to have. Flashing through fastboot is straightforward, but a pain...
divergens said:
This would be a nice thing to have. Flashing through fastboot is straightforward, but a pain...
Click to expand...
Click to collapse
It's not straightforward when it's a proprietary Mfastboot from Motorola.
And Mfastboot is only for Windows and we can't run it from Linux, even with Wine.
Since a lot of Android devs, such as myself, run Linux exclusively, this is a pain. At least the popularity of Samsung has resulted in MobileOdin, to flash firmware on phone, as well as Heimdall to flash from Linux PC.
I gave up on Motorola some time ago. I hoped the new "Google Moto" would be different. With the Moto G and Moto X it looked like the "Google Moto" was finally here. Now the sale to Lenovo... I'm not so happy with "Lenovo Moto".
And since I'm ranting, LOL, what's with the phone date being reset to 1970 (!!!!) ?? I guess they saved a penny or two in hardware with this trick...
hemanthmahesh said:
Will a simple twrp backup suffice for restoring stock?
Click to expand...
Click to collapse
I'm not sure...
hemanthmahesh said:
Edit: http://forum.xda-developers.com/showthread.php?t=2605824
This might be what you are looking for. Not for dualsim though.
Click to expand...
Click to collapse
Thanks. In theory it should work.
In practice it wrote over my custom recovery, then it tried, and failed, to write the system partition. I have no idea why.
This left my MotoG in a state where I had to mess with a Windows PC again, and waste another 30 minutes of my life.
So, AOSP only for me I guess...
(Must. Resist. Temptation to flash non-AOSP. Forever. Or be doomed to waste more time.)
(I have 20 app test phones I've flashed with MANY ROMs each over 3 years. Every stinkin' phone is different, pretty much, and requires different tricks and poses different problems. Each seems to require a minimum of 20 hours of reading and messing about to unlock, root, add recovery, backup, save EFS, avoid corruption bugs, etc. Buying a new test phone is just the START of the "investment" in it. What a pain, LOL.)
Some stock ROM downloads contain motorola fastboot for Linux.
1970 is Unix epoch. Google for it if you want to know more. I'd thought a dev working on Linux would know that already
scott_doyland said:
Some stock ROM downloads contain motorola fastboot for Linux.
Click to expand...
Click to collapse
Really ?? Can you or anyone clue me in to which downloads have a Linux version ? Thanks !
scott_doyland said:
1970 is Unix epoch. Google for it if you want to know more. I'd thought a dev working on Linux would know that already
Click to expand...
Click to collapse
Oh, I've known that since the 80's, along with obscure experience with real ASR33 110 baud TTYs with punch and reader in my basement. Then there were "television TTYs" with 24 lines and 40 columns or less, LOL.
I'm just griping that the clock isn't automatically set. AFAIK some phones went cheap and can't set it automatically, while others do. (?)
Anyway, even decades old PCs have BIOSes that start in the 80's or 90's or 00's, instead of the 70's. Just seems ridiculous to have to scroll through 3+ decades when setting time.
mikereidis said:
Really ?? Can you or anyone clue me in to which downloads have a Linux version ? Thanks !
Oh, I've known that since the 80's, along with obscure experience with real ASR33 110 baud TTYs with punch and reader in my basement. Then there were "television TTYs" with 24 lines and 40 columns or less, LOL.
I'm just griping that the clock isn't automatically set. AFAIK some phones went cheap and can't set it automatically, while others do. (?)
Anyway, even decades old PCs have BIOSes that start in the 80's or 90's or 00's, instead of the 70's. Just seems ridiculous to have to scroll through 3+ decades when setting time.
Click to expand...
Click to collapse
I think it's the 4.3 version (UK retail I used) from sbf-droid that has the moto fastboot. Its just called 'fastboot' though. Worked fine for me flashing stock 4.3 and 4.4.2.
4.4.2 version from.sbf-droid doesn't have it included.
Also one of the official moto x stock downloads from Motorola site has a Linux version.
If you can't find it let me know and I will attach to this thread when I get home.
1970 - fair enough I see your point. I work with IBM pSeries AIX servers and if you remove power AND the internal clock battery dies they revert to 1970 on boot up as well - and they cost tens of thousands of pounds/dollars.