Database Users

Has anyone found news about 2.3 for us???

I wake up everyday looking for news about 2.3 getting released. I am on 2.2.1 so I lost the ability to root. So i hope this comes out soon and if anyone has any info please post.

Officially it should come out in "coming weeks" as this tweet suggests - http://twitter.com/googlenexus/status/16974464310845440.
But there's a way to root your 2.2.1 anyways. Follow this guide:
http://forum.xda-developers.com/showpost.php?p=8315805&postcount=2

KROMO50 said:
I wake up everyday looking for news about 2.3 getting released. I am on 2.2.1 so I lost the ability to root. So i hope this comes out soon and if anyone has any info please post.
Click to expand...
Click to collapse
SuperOneClick works great if you still want root.

KROMO50 said:
I wake up everyday looking for news about 2.3 getting released. I am on 2.2.1 so I lost the ability to root. So i hope this comes out soon and if anyone has any info please post.
Click to expand...
Click to collapse
Just unlock your bootloader.

I have tried the super one click no luck

Other than unlocking, which is the preferred and safest way to do it. You could just follow the guide that was linked here. I did it for my friend just last week because he was afraid of the official way to root for some reason. It worked perfectly.

Yeah I did it the rageagainstthecage way.
Sent from my Nexus One using XDA App

nope but i read about 2.4 just google for:
google-ice-cream-android-2-4
cant post links

My sig says it all...

KROMO50 said:
I have tried the super one click no luck
Click to expand...
Click to collapse
Odd, are you sure you have the latest Super One Click? It worked fine for me 2.2.1 N1 on T-Mobile.

KROMO50 said:
I have tried the super one click no luck
Click to expand...
Click to collapse
Works fine for me. Did you get stuck at the looping problem after following the steps in the OP?
The way around that, as many of us have discovered, is to turn the phone off then run SuperOneClick and select 'root'. Turn the phone back on once 'waiting for device..' is shown in the program and then just leave it until it finishes.
Ensure USB debugging is enabled before you get started and that your PC has the required drivers installed. (Check Device Manager).
To be fair the Original Post needs updating as the instructions aren't very good without the above being mentioned.

DirkGently1 said:
SuperOneClick works great if you still want root.
Click to expand...
Click to collapse
Dumb question but, does that method allow you to install custom roms (e.g. CM7) without unlocking the bootloader, thus keeping the warranty?

frandavid100 said:
Dumb question but, does that method allow you to install custom roms (e.g. CM7) without unlocking the bootloader, thus keeping the warranty?
Click to expand...
Click to collapse
Using exploit to root allows you to get rooted device without unlocking the bootloader. However, I cannot tell you 'your warranty is kept' for certain(as long as bootloader is locked and you can revert to stock, I think it's okay).

frandavid100 said:
Dumb question but, does that method allow you to install custom roms (e.g. CM7) without unlocking the bootloader, thus keeping the warranty?
Click to expand...
Click to collapse
This does not unlock the boot loader....... and, yes you can flash roms once rooted.
Good luck on that warrenty buisness.

LFact said:
However, I cannot tell you 'your warranty is kept' for certain(as long as bootloader is locked and you can revert to stock, I think it's okay).
Click to expand...
Click to collapse
If you do revert to stock there should be no way to tell you ever modified the rom, isn't that right?

frandavid100 said:
If you do revert to stock there should be no way to tell you ever modified the rom, isn't that right?
Click to expand...
Click to collapse
Unfortunately you can only relock the bootloader on Nexus S, according to a Google Android developer

rcknr said:
Officially it should come out in "coming weeks" as this tweet suggests - http://twitter.com/googlenexus/status/16974464310845440
Click to expand...
Click to collapse
Is this "official" though? It's been 23 days since that post.
We'll get it, but I'm just bored of waiting. With so much anticipation, we'll probably be disappointed. Hope not.
Sent from my Nexus One using XDA App

hircus said:
Unfortunately you can only relock the bootloader on Nexus S, according to a Google Android developer
Click to expand...
Click to collapse
His question isn't about relocking the bootloader. But as long as you reflash the stock ROM and recovery, then I don't think there would be a way to tell without further examination. Regardless, HTC isn't too strict with the warranty claims, as many members on this forum have claimed warranty and sent back rooted phones to HTC. You should be fine.

andynx1 said:
Is this "official" though? It's been 23 days since that post.
We'll get it, but I'm just bored of waiting. With so much anticipation, we'll probably be disappointed. Hope not.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
that's 3 weeks. "coming weeks" being a PR equivalent of more than a month, we should be waiting for gb another 2 weeks at least...

It's only 5% of GB, but you can have the keyboard from it. A definite improvement and works perfectly on my N1 with 2.2.1 (no root needed):
http://www.appbrain.com/app/keyboard-from-android-2-3/com.moo.android.inputmethod.latin.free

Stock Image: UK 3G Xoom

Does anybody have a dump of their Stock System.IMG, Recovery.IMG and Boot.IMG files? Without reading I went ahead and flashed the US image and obviously I'm stuck now as I can't find a stock image for the Euro Xoom.
Thanks

how is it?
did you get stuck on not able to use the 3g modem only or you bricked your xoom?

I have posted several thread warning other uk users not to do what you have done. I wish people would read.
If you do read you will find that the solution is out there in the forum in two of my threads.
That said, there is no way for us to relock yet so on that count you're now screwed like the rest of us.
Macbots drool as I XOOM through the Galaxy to my hearts Desire.

Without looking in to it properly I flashed my UK 3G Xoom with the USA Android 3.1
Turns out it doesn't work... but can't get back to my stock UK image now.

Same problem
Same problem here.
Just managed to semi brick my xoom.
If you manage to find any resources on this please also give me some info [email protected], I'll do the same

You know, one day, I'll get an email notification and it'll be a link to the images on the Moto website.
Until then I'm sitting this one out, because no amount of searching will turn up what doesn't exist.

hi folks..
just a quick suggestion. untill the proper stock rom turn out.
why not try flasing the US wifi only rom.
as in general they are the same, apart from the 3g modem part.
i know by doing that, you will loose the 3g. but what can be worse than having it bricked?
i might work as the UK wifi seems to be able to run on US wifi rom.
just an idea.

Solution
Found it!
1. Get the euro rooted boot image (booteuro.img) and with the device disconnected attempt to fastboot flash it (fastboot flash boot booteuro.img).
2. Fastboot will be waiting for the device to boot into fastboot mode.
3. Shutdown with power + volume up
4. Immediately after shutdown release the buttons
5. Immediately after this press them again (power + volume up)
6. Just after the screen turns on release them and press volume down
Then continue with the rooting procedure you had started before you semi-bricked your xoom
Source: http://forum.xda-developers.com/showthread.php?t=1049901
Also get the file from there as I am somehow unable to upload.

tbitbLULA said:
Found it!
1. Get the euro rooted boot image (booteuro.img) and with the device disconnected attempt to fastboot flash it (fastboot flash boot booteuro.img).
2. Fastboot will be waiting for the device to boot into fastboot mode.
3. Shutdown with power + volume up
4. Immediately after shutdown release the buttons
5. Immediately after this press them again (power + volume up)
6. Just after the screen turns on release them and press volume down
Then continue with the rooting procedure you had started before you semi-bricked your xoom
Source: http://forum.xda-developers.com/showthread.php?t=1049901
Also get the file from there as I am somehow unable to upload.
Click to expand...
Click to collapse
Hmm, that thread looks familiar ... I'm not sure though.

Why the People is so desperate and try to flash the UK Xoom with the US Rom, Jesus, if you just do a little research before flashing like crazy you just stop a little Xoom brick from happen.
alias_neo has already post this like 10000000 times, but people continue bricking devices like little childrens!
sorry if I sound not nice but is the truth!
WAIT, just wait for the uk ROM to be released!

Agree whole heartidly with alias, just wait for it.
However I emailed motorola uk support for an update on the motodev site and uk images. Im going to push to find out why they haven't issued them. I can think of 3 at the moment. But hoping they will give us an update soon.
Sent from my MZ601 using XDA Premium App

fkofilee said:
Agree whole heartidly with alias, just wait for it.
However I emailed motorola uk support for an update on the motodev site and uk images. Im going to push to find out why they haven't issued them. I can think of 3 at the moment. But hoping they will give us an update soon.
Sent from my MZ601 using XDA Premium App
Click to expand...
Click to collapse
I emailed them over a week ago, no reply.

got a response, , but they said they dont deal with us on a developer level, so we are stuffed for the mean time... xd

I would be very grateful if somebody could post a dump of system.img for the Xoom 3G with the English language... would be nice to at least get it back in a working state again (With 3G and English language).

Ash09 said:
I would be very grateful if somebody could post a dump of system.img for the Xoom 3G with the English language... would be nice to at least get it back in a working state again (With 3G and English language).
Click to expand...
Click to collapse
i was wondering if you would like to try flashing it with a US wifi only rom? not sure if that will work, it might.
but you will only be back onto as a wifi xoom instead of a 3g xoom.
but it will still be better than a brick.

Ash09 said:
I would be very grateful if somebody could post a dump of system.img for the Xoom 3G with the English language... would be nice to at least get it back in a working state again (With 3G and English language).
Click to expand...
Click to collapse
Hi fella, I've bought a 3g WIFI Xoom UK Version off ebay, it sadly has already been rooted and the kernel changed but if I can help out then please let me know.
Does clockwork recovery work ? If so I could take a image.. wipe my data, take another image for you then restore back mine.. not done much flashing but will help if I can.
p.s I would like to turn mine back to stock if possible, ready for the update.
Steve

CdRsKuLL said:
Hi fella, I've bought a 3g WIFI Xoom UK Version off ebay, it sadly has already been rooted and the kernel changed but if I can help out then please let me know.
Does clockwork recovery work ? If so I could take a image.. wipe my data, take another image for you then restore back mine.. not done much flashing but will help if I can.
p.s I would like to turn mine back to stock if possible, ready for the update.
Steve
Click to expand...
Click to collapse
A userdata dump won't work, we won't be able to flash and relock with any dumps, we need the images from motorola, until then, there is no relock for us.
We need to be patient and wait for 3.1.
For the time being, we have Clockwork Mod which works, as does Tiamat (the old version, not the one for 3.1).
Most mods don't work so guys please, stop bricking your devices by flashing stuff meant for US XOOMs.

I've currently got a German 3.0.1 on mine as it's the only thing I can get 3G + WiFi to work on.
I'm not bothered about relocking yet, would just like a working device (in English). I assume a dump from a UK Xoom would work?

Ash09 said:
I've currently got a German 3.0.1 on mine as it's the only thing I can get 3G + WiFi to work on.
I'm not bothered about relocking yet, would just like a working device (in English). I assume a dump from a UK Xoom would work?
Click to expand...
Click to collapse
It should, yes. But I'm surprised the German version doesn't have English? Did you try going into languages and switching it in the settings?

Yep, only has Deutsch listed... which is quite strange!

[DEV REQUEST] CAN/FR/AUS/UK/MEX/BR Dev to help Unlock CAN/FR/AUS/UK/MEX/BR Atrix

We have a lack of Developers involved with the Atrix hailing from Canada, France, Australia, United Kingdom, Mexico, Brazil. Or so it would seem....
If you are out there, show your faces! I am willing to help as best I can, I am not without knowledge.
Maybe we can make some kind of amalgam with the French 2.1.1 & the "Pudding" SBF? Are the keys different in the AT&T firmware? Preventing us from using portions of it? We have to get moving on this.
*Update 1*
As I stated earlier, the keys might be different from the AT&T version & CAN/FR/AUS/UK versions. Unfortunately they are. The files released today are useless to us, other than the method to compile an SBF of our own when the time comes. We need someone to leak these files:
CG2.smg
CG3.smg
CG42.smg
CG44.smg
firmware.hmg
RDL1.smg
RDL3.smg
From a Gingerbread build for International Atrix's or we wait for the OTA Update. Basically it's a waiting game for a leak or the first OTA Update that is compatible with our devices. I am not even sure if we can grab Code Groups from an already flashed Atrix though.
*Update 2*
Couldn't we use some of that Bootloader Bounty to maybe "Persuade" someone into coughing up a couple Code Groups? Anyone know someone at Bell, Telstra, T-Mobile or Orange UK?

I have an IDEA.
i tried to depack the unlocking SBF and it works. now i can see all the files:
CG2.smg
CG3.smg
CG42.smg
CG44.smg
firmware.hmg
RDL1.smg
RDL3.smg
If i replace the firmware.hmg file for thefirmware.smgon the french or Telstra sbf, it should work but i have a big problem, i cannot repack the file . i have an error message (Error opening files from folder. Some ramdownloaders have nothing to flash, remove them.) (
nexxusty said:
We need to get rolling on this. The problem is, there is not many Canadian Dev's in the Atrix forum.
If there is, show your faces! I am willing to help as best I can, I am not without knowledge.
Maybe we can make some kind of amalgam with the French 2.1.1 & the "Pudding" SBF? Are the keys different in the AT&T firmware? Preventing us from using portions of it? We have to get moving on this.
Click to expand...
Click to collapse

yungboss22 said:
I have an IDEA.
i tried to depack the unlocking SBF and it works. now i can see all the files:
CG2.smg
CG3.smg
CG42.smg
CG44.smg
firmware.hmg
RDL1.smg
RDL3.smg
If i replace the firmware.hmg file for thefirmware.smgon the french or Telstra sbf, it should work but i have a big problem, i cannot repack the file . i have an error message (Error opening files from folder. Some ramdownloaders have nothing to flash, remove them.) (
Click to expand...
Click to collapse
I was about to do just this. So I am guessing we have to figure out if these .img files are signed with the right keys. It seems they are compatible with AT&T devices, but not ours.
I am unsure as to how they did this. I am sure they all chat in IRC somewhere, we need to get in there and ask a few questions.
*edit*
Ended up here. Seems there is a way to recalculate the checksums of the sbf.
Got one step further, went to compile but errored out half way through.
*edit 2*
Not gonna work. The program errors out even when you unpack and repack the stock 2.1.1 SBF.

Try to unpack and repack the SBF, we never know
nexxusty said:
I was about to do just this. So I am guessing we have to figure out if these .img files are signed with the right keys. It seems they are compatible with AT&T devices, but not ours.
I am unsure as to how they did this. I am sure they all chat in IRC somewhere, we need to get in there and ask a few questions.
*edit*
Ended up here. Seems there is a way to recalculate the checksums of the sbf.
Got one step further, went to compile but errored out half way through.
*edit 2*
Not gonna work. The program errors out even when you unpack and repack the stock 2.1.1 SBF.
Click to expand...
Click to collapse

I really don't think this is going to work for you guys but if you have any questions come in to #moto-atrix on freenode and I'll answer the best I can.
nexxusty said:
I was about to do just this. So I am guessing we have to figure out if these .img files are signed with the right keys. It seems they are compatible with AT&T devices, but not ours.
I am unsure as to how they did this. I am sure they all chat in IRC somewhere, we need to get in there and ask a few questions.
*edit*
Ended up here. Seems there is a way to recalculate the checksums of the sbf.
Got one step further, went to compile but errored out half way through.
*edit 2*
Not gonna work. The program errors out even when you unpack and repack the stock 2.1.1 SBF.
Click to expand...
Click to collapse

the only way is to flash the leaked GINGERBREAD chineese SBF Do u have the link of this firmware ?
the2dcour said:
I really don't think this is going to work for you guys but if you have any questions come in to #moto-atrix on freenode and I'll answer the best I can.
Click to expand...
Click to collapse

I will be on IRC in a bit. Just in town grabbing a few things.
Chinese. SBF hmmm....
Sent from my MB860 using XDA App

i haven't seen the full .sbf, all i've seen of this firmware and the way to apply it is in post 2 of this thread

We have waited so long for an unlocked BL and now when we get one, everyone that isn't on AT&T are SOL. I have 100% had it with the Bell side of things.
Looks like we are waiting for an OTA update.....

I guess we'll just have to wait until the 2.3.3 OTA update is released. I know there's skepticism regarding international users obtaining this update, but Motorola went on record stating that it will be released simultaneously for US and UK users. Since SBFs from Orange UK work on all international builds, it would seem likely that all international users will get Gingerbread from them.
EDIT: How were ATT users able to unlock their bootloaders anyway? And why is it so different for us?

I know you guys on Bell are extremely anxious to get your BL unlocked as well, however, I dont think it was necessary to create a new thread in the DEV section for it... It hasnt even been 24 hrs yet. Its also been said hundreds and hundreds of times that requests do not belong in the DEV section.

jgc121 said:
I know you guys on Bell are extremely anxious to get your BL unlocked as well, however, I dont think it was necessary to create a new thread in the DEV section for it... It hasnt even been 24 hrs yet. Its also been said hundreds and hundreds of times that requests do not belong in the DEV section.
Click to expand...
Click to collapse
Although i do appreciate where your coming from, i do think it is necessary for a Bell/international thread for unlocking BL/2.3 for Bell Atrix seeing as our framework is different from the ATT.
Perhaps this request could be moved to the correct area but i do think there should be a Bell/International related thread in the Dev forum.

J-Roc said:
Although i do appreciate where your coming from, i do think it is necessary for a Bell/international thread for unlocking BL/2.3 for Bell Atrix seeing as our framework is different from the ATT.
Perhaps this request could be moved to the correct area but i do think there should be a Bell/International related thread in the Dev forum.
Click to expand...
Click to collapse
Umm see, once we unlock ALL of our Bootloaders... there wont be a "Bell" or "AT&T" version. We will all be running the same stuff. AFAIK.
That's really why I want this the most, I am sick as hell of AT&T only stuff, which is 90% of the mods available, and 100% of the Unlockable Bootloaders available.

nexxusty said:
Umm see, once we unlock ALL of our Bootloaders... there wont be a "Bell" or "AT&T" version. We will all be running the same stuff. AFAIK.
That's really why I want this the most, I am sick as hell of AT&T only stuff, which is 90% of the mods available, and 100% of the Unlockable Bootloaders available.
Click to expand...
Click to collapse
There will still be bell and att versions - the firmwares are still different. I dont think we'll be running "the same stuff" until some of the devs polish up some custom kernels painted with custom roms that can support both models of the Atrix.

jgc121 said:
There will still be bell and att versions - the firmwares are still different. I dont think we'll be running "the same stuff" until some of the devs polish up some custom kernels painted with custom roms that can support both models of the Atrix.
Click to expand...
Click to collapse
I can 100% guarantee there is 1 model of the Atrix hardware. Maybe a couple revisions, but the same hardware nonetheless. This being said, only the software differs. Now that we do not have to use signed files, we can essentially all use the same kernels and data partitions.
If we had an unlock for our phones and flashed the 2.3.4 HKTW build, I highly doubt there would be much difference between our phones and yours when flashed with that same build.

nexxusty said:
I can 100% guarantee there is 1 model of the Atrix hardware. Maybe a couple revisions, but the same hardware nonetheless. This being said, only the software differs. Now that we do not have to use signed files, we can essentially all use the same kernels and data partitions.
If we had an unlock for our phones and flashed the 2.3.4 HKTW build, I highly doubt there would be much difference between our phones and yours when flashed with that same build.
Click to expand...
Click to collapse
I just hope the UK build for ginger comes out the same day the US one does.

Magnetox said:
I just hope the UK build for ginger comes out the same day the US one does.
Click to expand...
Click to collapse
Here's hoping!

Magnetox said:
I just hope the UK build for ginger comes out the same day the US one does.
Click to expand...
Click to collapse
Anyone tried putting cg42 in a french. Orange. T-Mobile sbf? Ill try later if not
Sent from my MB860 using XDA Premium App

stevendeb25 said:
Anyone tried putting cg42 in a french. Orange. T-Mobile sbf? Ill try later if not
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Read my first post. Signing Keys differ.

double. 10 char.

[Q] Super noob needs a help here!

Back in old days when i had a HTC Wildfire with a few clicks i rooted it and started installing new ROMS on to it
But since i got this New Xperia Play : R800i Build NO. 3.0.1.a.0.146 {UK}
I got no clue how to do anything on it. Let me be honest here... I updated my phone using the option under the settings menu in About my phone and seems to be on 2.3.3 and look all my friends have rooted their phones but i got no clue if its even possible . Mabey im not such a noob or something but i would be really greatfull if anyoen could point me atleast to the right direction. Mabey some helpfull links to help a fellow noob

Is your phone sim locked?
Sent from my R800i using Tapatalk

Nope... Well not that i know of, because i got my phone from vodafone and once i inserted a sim card from another operator i made a few calls and i could recieve calls too without any problems.

arian009 said:
Nope... Well not that i know of, because i got my phone from vodafone and once i inserted a sim card from another operator i made a few calls and i could recieve calls too without any problems.
Click to expand...
Click to collapse
Mine was from vodafone and wasnt sim locked either. Ok you have two choices for root. You can either unlock your bootloader (there are many downsides and advantages to this so you should research it) or downgrade to 2.3.2, root using gingerbreak then OTA update to latest version. That way you will not loose root while updating.
Sent from my R800i using Tapatalk

Seems like ol' Freddy is right after all:
http://en.wikipedia.org/wiki/Eternal_return

What OTA Update Means? And please can you give some links on how to downgrade and root it please?

And btw if i use the method of downgrading my phone first will i be able to flash custom ROMs?

Logseman said:
Seems like ol' Freddy is right after all:
http://en.wikipedia.org/wiki/Eternal_return
Click to expand...
Click to collapse
Lmao
Sent from my R800i using Tapatalk

arian009 said:
What OTA Update Means? And please can you give some links on how to downgrade and root it please?
Click to expand...
Click to collapse
Im on my phone so i can't really link. Look in the android development section, there is a thread all about rooting 2.3.3 with a locked bootloader. OTA means over the air. Basically thats when you download and install an update using just your phone.
Sent from my R800i using Tapatalk

arian009 said:
And btw if i use the method of downgrading my phone first will i be able to flash custom ROMs?
Click to expand...
Click to collapse
No you need an unlocked bootloader to flash custom roms. But please read the pros and cons of unlocking your bootloader first. And understand what you can and can't do
Sent from my R800i using Tapatalk

Ok mate just wanna say thanks a lot for your help and i really appreciate it. You really helped me out here. also just one more thing i need to know. By the looks of it the only cons in unlocking your bootloader seems to be that you will lose warranty and that your phone or your radio may get bricked which apparently can be fixed with restoring a backed up data using a program named omnius for se which i'm actually working on... however my only other concern is if there are any other disadvantages regarding the unblocking the bootloader that you happned to know of and be kind to share it with me Also just wanna say that i can see many tutorials as you said in the development section and i quite frankly i don't know which one applies to me since i realized one of the tutorials are for models with build number .184 where as mine is 3.0.1.a.0.145 AND I HAVE NO CLUE WHICH TUTORIAL TO FOLLOW. So i would be greatfull if you could lend me link to a right tutorial whenever you get free time on the PC

If all you want is root you can do that with a locked bootloader. You will have to downgrade to 2.3.2 (.184) then root then ota to get the latest firmware rooted. Follow the guide here. Or see this post i made here for easier instuctions on downgrading and rooting.
If you want to flash custom roms then you do need an unlocked bootloader like AndroHero has said. You dont need a specific guide to unlock your bootloader. Just go too the SE bootloader unlocking site (it gives you all the instructions you need) http://unlockbootloader.sonyericsson.com/. Then just flash doomlords kernel (which autoroots) or anything really from the development section (since i think anything can be rooted with one click with an unlocked bootloader) you will then have root and the ability to flash cutom roms.
Oh btw build number .184 = 2.3.2, build number 3.0.1.a.0.145 = 2.3.3 and build number 4.0.a = 2.3.3 (xloud version, the latest update)
+
If you unlock your bootloader OTA, Pc Companion + SEUS are off limits use any of them after unlocking your bootloader and you will brick your phone. Go to the dev section for the latest updates.

Logseman said:
Seems like ol' Freddy is right after all:
http://en.wikipedia.org/wiki/Eternal_return
Click to expand...
Click to collapse
Looks like I've overseen your sense of humor... Very subtle... Wicked
Regards Dousan...

You won't allow me to get rowdy and yell at folks, so I have to resort to good old snark. Caveat emptor.

Dousan said:
Looks like I've overseen your sense of humor... Very subtle... Wicked
Regards Dousan...
Click to expand...
Click to collapse
Logseman said:
You won't allow me to get rowdy and yell at folks, so I have to resort to good old snark. Caveat emptor.
Click to expand...
Click to collapse
I got it straight away

Logseman said:
You won't allow me to get rowdy and yell at folks, so I have to resort to good old snark. Caveat emptor.
Click to expand...
Click to collapse
Lmao I can't argue with that, althoug it's sneaky to post a link like that, still hilarious
Regards Dousan...

Lost root club

So I did the root keeper wrong and updated, losing root. Anyone else in this club with me? It's only been a few hours and I already miss it.
Atleast I have better pictures though....
Sent from my XT1058 using xda app-developers app

You could reflash the software back to before the update with the KXZ firmware and try the process over again. Depends if the hassle is worth it to you.
http://forum.xda-developers.com/showthread.php?t=2411618

Abyssul said:
You could reflash the software back to before the update with the KXZ firmware and try the process over again. Depends if the hassle is worth it to you.
http://forum.xda-developers.com/showthread.php?t=2411618
Click to expand...
Click to collapse
This process is just flashing the firmware through rsdlite which won't happen because it's a downgrade. I tried.
Sent from my XT1058 using xda app-developers app

Maybe this will work? http://forum.xda-developers.com/showthread.php?p=45955669#post45955669

You can't flash with fastboot? I'm new to the Android ecosystem, but there must be some way to downgrade.

freak4dell said:
Maybe this will work? http://forum.xda-developers.com/showthread.php?p=45955669#post45955669
Click to expand...
Click to collapse
just tried, did not work. fails at the boot.img
Abyssul said:
You can't flash with fastboot? I'm new to the Android ecosystem, but there must be some way to downgrade.
Click to expand...
Click to collapse
first things I tried and doesn't work

I did the update and protected root but my wifi was messed up and wouldn't turn on. I did RSDLite to downgrade and redo it all and it worked fine.
BTW I used this http://forum.xda-developers.com/showthread.php?t=2446515

Some of us didn't want root in the first place! #TeamStockMotoX :silly:

I'm confused as to why someone wouldn't just unlock their bootloader if they are going to be making changes to their system. I understand the warranty issue but who uses that? Most people go through asurion and they won't even notice. Haha
Sent from my Moto X using XDA Premium

eyeisdasteve said:
I'm confused as to why someone wouldn't just unlock their bootloader if they are going to be making changes to their system. I understand the warranty issue but who uses that? Most people go through asurion and they won't even notice. Haha
Sent from my Moto X using XDA Premium
Click to expand...
Click to collapse
Because some of us can't unlock our bootloader.

eyeisdasteve said:
I'm confused as to why someone wouldn't just unlock their bootloader if they are going to be making changes to their system. I understand the warranty issue but who uses that? Most people go through asurion and they won't even notice. Haha
Sent from my Moto X using XDA Premium
Click to expand...
Click to collapse
Just remember that Retail AT&T and Verizon and MotoMaker AT&T variants aren't able to have their boot loaders unlocked
Sent from my XT1058 using Tapatalk 4

Lost root don't care. Motorola got this phone right. I'm good with stock.

rivlez said:
I did the update and protected root but my wifi was messed up and wouldn't turn on. I did RSDLite to downgrade and redo it all and it worked fine.
BTW I used this http://forum.xda-developers.com/showthread.php?t=2446515
Click to expand...
Click to collapse
Your wifi was only screwed up within Recovery mode (write off) correct?
I have a similiar issue. Whether its affecting other things or not, i dont know.
But what do you mean you restored via RSD lite and did it all over again and it was fine?
How did you ujse RSD lite to reflash the firmware since you got the updated OTA, it wont let you downgrade

emerica243 said:
Your wifi was only screwed up within Recovery mode (write off) correct?
I have a similiar issue. Whether its affecting other things or not, i dont know.
But what do you mean you restored via RSD lite and did it all over again and it was fine?
How did you ujse RSD lite to reflash the firmware since you got the updated OTA, it wont let you downgrade
Click to expand...
Click to collapse
My wifi was messed up in any mode. It wouldn't turn on for some reason. I restored the 17.51 firmware after the botched update messed up my wifi and it worked fine and I actually ended up doing it 2 times since a titanium backup messed up my phone. I was definitely on the 17.54 update. It definitely let me downgrade. How would you like me to prove it to you?

my wifi messed up in recovery mode but lte works. Normal mode everything is fine. I am rooted now with latest update.

sravanz said:
my wifi messed up in recovery mode but lte works. Normal mode everything is fine. I am rooted now with latest update.
Click to expand...
Click to collapse
Add me in as another one with no wifi in recovery. Normal mode works just fine as well. Would be nice if there was a fix for this but just glad to still have root with the update.

Rask40 said:
Add me in as another one with no wifi in recovery. Normal mode works just fine as well. Would be nice if there was a fix for this but just glad to still have root with the update.
Click to expand...
Click to collapse
Me too. My wifi is FUBARED in recovery. It's because we don't have the new kernel and to be technical were using the old system/recovery in our "recovery mode" I think that's why it's working in the regular mode and not recovery mode..... Or that's what I understand. Though I'm probably wrong.
When I upgraded I got a failed upgrade after final boot. Although it still says the newest version. I'm tempted to RSD back like some others have just to try but I don't want a paper weight.
Sent from non rooted motoX :'(

gunnyman said:
Lost root don't care. Motorola got this phone right. I'm good with stock.
Click to expand...
Click to collapse
While I'm kind of excited to see SafeStrap out, and updated (fixes phone/data, etc...), I'm still hoping some attempt is in the works for unlock on at&t.
Regardless, there aren't any custom roms to really flash anyways.
Had I an unlocked bootloader, I'd have a custom kernel in the works, and maybe some custom roms with some TeamAcid love.
Come see, come saw... Patience wins all.