I have a moto X, xt1058 from claro, argentina, and i haven't reiceived any OTA so far yet, not even the camera fix one.
Is there anyone else with this problem?
Have you disabled the motorolaOTA app by chance? Or altered your phones system in any way?
Something must be altered on your phone to exclude you from every ota. I'm assuming there has been one for your model, cause I don't know for sure.
Sometimes restoring your phones factory image, the same as you currently are running, will jog the ota to come.
Sent from my Moto X cellular telephone...
ganasiff said:
I have a moto X, xt1058 from claro, argentina, and i haven't reiceived any OTA so far yet, not even the camera fix one.
Is there anyone else with this problem?
Click to expand...
Click to collapse
I have the VZW and I am still on 4.4. So no 4.4.2 OTA update for me yet.
kj2112 said:
Have you disabled the motorolaOTA app by chance? Or altered your phones system in any way?
Something must be altered on your phone to exclude you from every ota. I'm assuming there has been one for your model, cause I don't know for sure.
Sometimes restoring your phones factory image, the same as you currently are running, will jog the ota to come.
Sent from my Moto X cellular telephone...
Click to expand...
Click to collapse
I have my phone totally stock, not even rooted. I'm still con 4.2.2 pre cal fix, i 've used rdslite with the factory image, still no OTA, motorolaOTA.apk is enabled
The at&t xt1058 is still without ota
MOTO X Slapped
[email protected] said:
The at&t xt1058 is still without ota
MOTO X Slapped
Click to expand...
Click to collapse
:fingers-crossed::fingers-crossed:
Related
Anyone able to successfully return to JB after the OTA?
Sent from a White Moto Xposed
I have!! used RSDlite. And flashed the VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-57-X-1_CFC_1FF.xml.zip from
://sbf.droid-developers.org/ghost_rcica/list.php
remicks said:
Anyone able to successfully return to JB after the OTA?
Sent from a White Moto Xposed
Click to expand...
Click to collapse
mjphillips1981 said:
I have!! used RSDlite. And flashed the VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-57-X-1_CFC_1FF.xml.zip from
://sbf.droid-developers.org/ghost_rcica/list.php
Click to expand...
Click to collapse
Awesome thanks, gonna revert back to JB myself as well.
Sent from a White Moto Xposed
reverted back too, needed tethering
RSDlite worked from 4.4 > 4.2.2 for non Dev Edition Moto Xs?
mjphillips1981 said:
I have!! used RSDlite. And flashed the VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-57-X-1_CFC_1FF.xml.zip from
://sbf.droid-developers.org/ghost_rcica/list.php
Click to expand...
Click to collapse
Will this wipe user apps and data?
Sent from my iPad mini using Tapatalk
Yes it will wipe clean everything. Just like the day you bought it from VZW. You will need to root again as well.
jayrod88 said:
Will this wipe user apps and data?
Sent from my iPad mini using Tapatalk
Click to expand...
Click to collapse
mjphillips1981 said:
Yes it will wipe clean everything. Just like the day you bought it from VZW. You will need to root again as well.
Click to expand...
Click to collapse
This is a time where I wish android had a stable backup option not requiring root. Normally I use titanium backup however I'm keeping this stock. iOS has nailed this with iCloud.
Sent from my iPad mini using Tapatalk
One thing that I forgot to add is you need to remove the getvar line in the .xml file.
I can only say this works for VZW. Not sure about other carriers.
so can someone post that they have returned to 4.2.2 from 4.4 on a locked bootloader vzw device please. I know people said you can, or it worked or whatever. But i just want to make sure that you are on a locked device and didn't misread the thread title or something.
yeah, post screen shots of kernel, etc.
I have personally done this on my LOCKED VZW Moto X.
Works like a charm. The RSD Lite, will flash it back to factory unrooted 4.2.2. You will have to use http://forum.xda-developers.com/showthread.php?t=2509590 to reroot if you want.
jayboyyyy said:
so can someone post that they have returned to 4.2.2 from 4.4 on a locked bootloader vzw device please. I know people said you can, or it worked or whatever. But i just want to make sure that you are on a locked device and didn't misread the thread title or something.
Click to expand...
Click to collapse
RSD doesn't want to see my phone, but adb and fastboot work fine. Any ideas? I'm using RSDLite 6.1.5.
Sent from my XT1060 using Tapatalk
imnotmikal said:
RSD doesn't want to see my phone, but adb and fastboot work fine. Any ideas? I'm using RSDLite 6.1.5.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
I believe fastboot has commands for formatting the partitions and then just flash all the things I suppose.
Sent from a White Moto Xposed
This is very strange. I had read at a lot of places while updating to the camera OTA. that downgrade is not allowed..,,So now it is possible to RSD to 4.2.2 Camera OTA SBF even if we installed KitKat on a non-dev edition phone?
tejaskary said:
This is very strange. I had read at a lot of places while updating to the camera OTA. that downgrade is not allowed..,,So now it is possible to RSD to 4.2.2 Camera OTA SBF even if we installed KitKat on a non-dev edition phone?
Click to expand...
Click to collapse
I think they meant downgrade to before the camera OTA?
help please
i'm a noob and need help.
i upgraded to 4.4 from 4.2.2. my 4G signal now sucks. i figure my options are to revert to 4.2.2 or if i could just find the radio kernel (or whatever its called) from 4.2.2 flash that and fix my problems.
i just don't know how to do either. can someone help (yes, hand hold me *embarrassed*) through the process so i don't brick my device?
I have a DE moto x on verizon
thanks
imnotmikal said:
RSD doesn't want to see my phone, but adb and fastboot work fine. Any ideas? I'm using RSDLite 6.1.5.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
did you try booting into recovery and than see if it recognized your phone?
RSD doesn't operate via recovery
Sent from my XT1060 using Tapatalk
Steps that I took to downgrade from KitKat. VZW Moto X Consumer (non-dev) (LOCKED)
1) download and install RSDlite and Motorola Drivers (I used RSDlite 6.1.5)
2) Download http://sbfdownload.droid-developers...2-13.9.0Q2.X-116-MX-17-57-X-1_CFC_1FF.xml.zip
3) Unzip the file
4) Open the .xml file and delete the line that has "getvar"
5) Reboot your phone to "bootloader/fastboot" mode
6) Open RSDlite and load the unzipped edited download from above
7) Make sure your phone shows up
8) Start the flash
9) Once complete the phone should reboot and start up like normal.
I have not had any issues. I have rerooted with RockMyMoto.
Hi all,
I was just wondering about following:
I own a Canadian Version (Rogers) of Moto X. Rogers did not start rolling out KitKat upgrade to Moto X yet. However, there should be OTA upgrade roll-out some time soon. My Moto X is unlocked and I'm using it now on non Rogers network. Question is if my Moto X will receive KitKat OTA if I'm not on the Rogers network? If not how can I upgrade OS without losing all my apps and settings. P.S. phone is not rooted and would like to avoid that if possible.
Thank you all.
So nobody on this forum has any idea about my question?.....
vukc said:
Hi all,
I was just wondering about following:
I own a Canadian Version (Rogers) of Moto X. Rogers did not start rolling out KitKat upgrade to Moto X yet. However, there should be OTA upgrade roll-out some time soon. My Moto X is unlocked and I'm using it now on non Rogers network. Question is if my Moto X will receive KitKat OTA if I'm not on the Rogers network? If not how can I upgrade OS without losing all my apps and settings. P.S. phone is not rooted and would like to avoid that if possible.
Thank you all.
Click to expand...
Click to collapse
I am rather newbish myself with the MotoX, but I have played around with a few ROMS on my old H0X and I assume the principals are usually the same.
When the stock Rogers OTA becomes available you will be prompted to download the OTA. If you choose to install this, it will most likely lock the bootloader.
Your best bet would be to root your phone, and get a custom recovery program on the phone (personally, I like twrp), and do a backup of the entire phone. This way, you can always revert back to that state afterwards.
V.
It shouldn't matter that you aren't physically on the Rogers network. The Moto X should check back to Moto for the update, not a Rogers server. I also have an unlocked Rogers Moto X that I gave to my wife that is on TELUS.
The said thing is, the clueless Rogers reps who man the customer support Twitter don't even think they have an update. They are blaming Moto on not having sent it to them. Hopefully this is just the standard case of clueless CS...
Sent from my Nexus 5 using Tapatalk
If you do receive the ota and you are running any sort of custom recovery, do not install it, why? It will result in bootloops and it will not install. You must have an untouched system and running the stock recovery for the ota to flash correctly.
As for your boot loader, that will remain unlocked. Now what i suggest is neglect the ota and install the rogers KitKat sbf firmware zip instead.
I did accept the rogers camera ota and I could not flash twrp recovery afterwards, it some how prevents you from over riding the stock recovery. To get around this I flash the sbf firmware and I have no issue flashing twrp recovery. Yes my boot loader is unlocked
Sent on my Moto X
Hello folks.
I'm on a bit of a limbo. Can you help me?
Fist of all i should state that i was a former Galaxy S3 owner, so even if I have some experience with the underworld of rooting and flashing, bootloader issues are a bit alien for me.
The problem:
My Brazilian Moto X with unlocked bootloader was on 4.4, and after receiving the OTA update, i thought that i could update it if I removed root and etc (after all i was not using Xposed and ETC, so no deep modifications at /system that i know).
Of course i was wrong, and as greeted with a nice bootloop by my moto X. No problem, I got the 4.4.2 UK and flashed it thought RSD lite. After the flashing, I dit not liked the modifications the UK 4.4.2 retail have (like carrier name on bar, etc etc) and just flashed Philz and recovered my nandroid.
All is nice, but now i can't update to 4.4.2 Brazilian because i can't install 4.4 Retail Brazilian trought RSD lite, since the Moto X just detects that it haves 4.4.2 bootloader and not let me downgrade! I'm in a Limbo \o/
What now? There is any way to downgrade the bootloader? There is any one who have a full Brazilian 4.4.2 image (or a image without carrier name on the bar) for unlocked bootloaders? Any 4.4.2 flashable update using CWM or TWRP?
Oh god, so many questions. Thanks for your atention!
brunodmjr said:
Hello folks.
I'm on a bit of a limbo. Can you help me?
Fist of all i should state that i was a former Galaxy S3 owner, so even if I have some experience with the underworld of rooting and flashing, bootloader issues are a bit alien for me.
The problem:
My Brazilian Moto X with unlocked bootloader was on 4.4, and after receiving the OTA update, i thought that i could update it if I removed root and etc (after all i was not using Xposed and ETC, so no deep modifications at /system that i know).
Of course i was wrong, and as greeted with a nice bootloop by my moto X. No problem, I got the 4.4.2 UK and flashed it thought RSD lite. After the flashing, I dit not liked the modifications the UK 4.4.2 retail have (like carrier name on bar, etc etc) and just flashed Philz and recovered my nandroid.
All is nice, but now i can't update to 4.4.2 Brazilian because i can't install 4.4 Retail Brazilian trought RSD lite, since the Moto X just detects that it haves 4.4.2 bootloader and not let me downgrade! I'm in a Limbo \o/
What now? There is any way to downgrade the bootloader? There is any one who have a full Brazilian 4.4.2 image (or a image without carrier name on the bar) for unlocked bootloaders? Any 4.4.2 flashable update using CWM or TWRP?
Oh god, so many questions. Thanks for your atention!
Click to expand...
Click to collapse
you can't downgrade the bootlaoder sorry
as for the carrier name in the bar someone will make a xposed mod to remove it.
i would either stay with 4.4 if that makes you happy or flash the correct 4.4.2 firmware for your device and tweak it to your liking.
Unfortunately you cannot downgrade the bootloader from 4.4.2 to 4.4.
Is it so dificult to do a 4.4.2 flashable update or we just lack devs?
brunodmjr said:
Is it so dificult to do a 4.4.2 flashable update or we just lack devs?
Click to expand...
Click to collapse
If you find the factory 4.4.2 image for your device, then you manually flash the 4.4.2 files.
Mr. Orange 645 said:
If you find the factory 4.4.2 image for your device, then you manually flash the 4.4.2 files.
Click to expand...
Click to collapse
I can only find the UK one. There is no 4.4.2 factory image for Brazilian Moto X, and i really don't want to install Xposed to remove the carrier name from the bar, since i play Square Enix titles.
brunodmjr said:
I can only find the UK one. There is no 4.4.2 factory image for Brazilian Moto X, and i really don't want to install Xposed to remove the carrier name from the bar, since i play Square Enix titles.
Click to expand...
Click to collapse
Well...then you are at an impasse. Sorry.
Mr. Orange 645 said:
Well...then you are at an impasse. Sorry.
Click to expand...
Click to collapse
So bad. Know any way to convert the OTA update to a CWM flashable zip? Any guide or something?
brunodmjr said:
So bad. Know any way to convert the OTA update to a CWM flashable zip? Any guide or something?
Click to expand...
Click to collapse
No. I, like you, depend on the hard work of developers here for that kind of thing.
Mr. Orange 645 said:
No. I, like you, depend on the hard work of developers here for that kind of thing.
Click to expand...
Click to collapse
I'm a dev too. Let's research.
The full image will probably be available in a few days to a week, so you should probably just wait for it since your phone is working.
Boot loaders are number differently that's why everyone who has flash, or just about everyone who has flashed a new firmware has had issue evedn though the firmwares are 4.4.2, morale . Flash only your specific carrier firmware and all this craziness would stop, my 2 cents
Sent on my Lenoto A2109 tablet
flashallthetime said:
Boot loaders are number differently that's why everyone who has flash, or just about everyone who has flashed a new firmware has had issue evedn though the firmwares are 4.4.2, morale . Flash only your specific carrier firmware and all this craziness would stop, my 2 cents
Sent on my Lenoto A2109 tablet
Click to expand...
Click to collapse
It certainly seems Motorola has changed the game with 4.4.2, flashing other carriers firmware at this time seems quite risky. As you said I wouldn't recommend it right now until more is known and all full flash images of 4.4.2 are released.
Steve-x said:
It certainly seems Motorola has changed the game with 4.4.2, flashing other carriers firmware at this time seems quite risky. As you said I wouldn't recommend it right now until more is known and all full flash images of 4.4.2 are released.
Click to expand...
Click to collapse
Someone should start a thread with all info and have it stickied, getting stupid here, miss info, assuming have a unlocked boot loader will prevent hard bricks.
Sent on my Lenoto A2109 tablet
flashallthetime said:
Boot loaders are number differently that's why everyone who has flash, or just about everyone who has flashed a new firmware has had issue evedn though the firmwares are 4.4.2, morale . Flash only your specific carrier firmware and all this craziness would stop, my 2 cents
Sent on my Lenoto A2109 tablet
Click to expand...
Click to collapse
OP's issue was that he wanted to downgrade to 4.2 -- not that he was trying to change the carrier version of the 4.4.2 bootloader. Are there any threads about someone having an issue trying to flash a different carrier's version of 4.4.2?
piccit said:
OP's issue was that he wanted to downgrade to 4.2 -- not that he was trying to change the carrier version of the 4.4.2 bootloader. Are there any threads about someone having an issue trying to flash a different carrier's version of 4.4.2?
Click to expand...
Click to collapse
Threads no but multiple threads about issues, stay away from flashing another carriers 4.4.2 firmware at this point in time, I'm trying to get boot loader numbers for all carrier firmware , so far all north american and south american boot loaders are the same but T-Mobile and AT&T have yet to be released, European boot loaders are not yet posted
Sent on my Lenoto A2109 tablet
Every issue that I've read about is from people trying to downgrade. I haven't seen anyone have an issue about trying to side-grade
piccit said:
Every issue that I've read about is from people trying to downgrade. I haven't seen anyone have an issue about trying to side-grade
Click to expand...
Click to collapse
Boot loaders numbers are different
Sent on my Gummy running Lenoto X
That's the risk of being impatient and flashing things in a hurry when they drop....that weren't made for our particular phone.
Remember ...good things come to those who wait.......and bad things for those who are too impatient.
Sent from my Moto X cellular telephone...
Just find the Brazilian full 4.4.2 file and rsdlite it or mfastboot flash. I believe it was floating around somewhere.
Sent from my Nexus 7 using XDA Premium 4 mobile app
So, I did some digging around here, and I am more confused than ever. Here is my quick question (hopefully)
I have an bootloader unlocked xt1058 (ATT branded). I ran a nandroid to flash a new rom, only to discover when i went to restore a nandroid, the system folder did not back up, therefore I do not have a /system folder backup of stock ATT 4.4.2.
What I want to know is: Can I fastboot flash ATT's 4.4 system file only (i know bootloader is not compatable), then take the 4.4.2 OTA? Or will this hard brick my phone?
If i searched the forums correctly, it addresses if your bootloader is locked, but not unlocked.
I am running an AOSP now, so i know my way around fastboot and adb.
Any assistance would be helpful, and a flashable zip of stock ATT 4.4.2 would kick a**
Thanks for the help!
I'm not sure exactly how, cause I never have, or would downgrade......but just be sure you find out exactly how to do it. An unlocked boot loader will not protect you from a brick if something is done wrong. In other words....there are ways to brick for sure....locked or unlocked.
To me its a risky endeavor no matter what the case. Mistakes happen.....and in the case of downgrading from 4.4.2....mistakes can cost you a phone. ?
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
kj2112 said:
I'm not sure exactly how, cause I never have, or would downgrade......but just be sure you find out exactly how to do it. An unlocked boot loader will not protect you from a brick if something is done wrong. In other words....there are ways to brick for sure....locked or unlocked.
To me its a risky endeavor no matter what the case. Mistakes happen.....and in the case of downgrading from 4.4.2....mistakes can cost you a phone. ?
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Click to expand...
Click to collapse
Yep! Hence the question. I guess the real question is...with an unlocked bootloader, can i flash System and Recovery (Android 4.4), while on Bootloader (Android 4.4.2)
would the safest thing to do to use RSD and flash (which will stop if there is a security issue)?
I'd just wait for the flash able 4.4.2 files.
Why do you want 4.4 anyway? There's not much difference.... Except a few negatives.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
cpetersen2791 said:
What I want to know is: Can I fastboot flash ATT's 4.4 system file only (i know bootloader is not compatable), then take the 4.4.2 OTA? Or will this hard brick my phone?
Click to expand...
Click to collapse
Yes this will brick your phone. If you are on 4.4.2, and downgrade only parts (say system.img), you'll have a version and security mismatch, including the bootloader and GPT.BIN. If you take an OTA in that state you will brick. (at least that is what many of the users who have bricked have done according to the threads I've read... I haven't actually done it first hand as I don't want to deal with a brick).
cpetersen2791 said:
If i searched the forums correctly, it addresses if your bootloader is locked, but not unlocked.
Click to expand...
Click to collapse
This applies for locked and unlocked bootloaders.
cpetersen2791 said:
Any assistance would be helpful, and a flashable zip of stock ATT 4.4.2 would kick a**
Thanks for the help!
Click to expand...
Click to collapse
As soon as the SBF for ATT 4.4.2 leaks out, I'm sure it will be available on -> http://sbf.droid-developers.org/phone.php?device=0
kj2112 said:
I'd just wait for the flash able 4.4.2 files.
Why do you want 4.4 anyway? There's not much difference.... Except a few negatives.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Click to expand...
Click to collapse
when i ran a "stock" nandroid to test AOSP roms, i failed to back up my system folder, therefore I don't have a Stock ATT OS. I know 4.4.2 was out, but only as OTA, but complete 4.4 was available.
Thanks for all the assistance, i'll wait for the 4.4.2 SBF.
I was wondering if i can safely flash the 4.4.2 file from sbf (retail argentina) on a 4.4.3 (from OTA) phone?
ramarivera said:
I was wondering if i can safely flash the 4.4.2 file from sbf (retail argentina) on a 4.4.3 (from OTA) phone?
Click to expand...
Click to collapse
I'm sure someone here can explain better than I can, but I've read time and time again don't downgrade, there is the risk of bricking
ramarivera said:
I was wondering if i can safely flash the 4.4.2 file from sbf (retail argentina) on a 4.4.3 (from OTA) phone?
Click to expand...
Click to collapse
Yes, as @M973 has advised, you can not "safely" downgrade back to 4.4.2. The reason is that "gpt.bin" - the partition table can NOT be downgraded. Even if you are able to manually downgrade the rest of the partitions to 4.4.2, you will still have a mismatched gpt.bin, and hence will be at risk of bricking the next time you take an OTA.
Once the 4.4.3 or higher SBF for retail Argentina is released, you CAN safely flash it, without risk of bricking.
samwathegreat said:
Yes, as @M973 has advised, you can not "safely" downgrade back to 4.4.2. The reason is that "gpt.bin" - the partition table can NOT be downgraded. Even if you are able to manually downgrade the rest of the partitions to 4.4.2, you will still have a mismatched gpt.bin, and hence will be at risk of bricking the next time you take an OTA.
Once the 4.4.3 or higher SBF for retail Argentina is released, you CAN safely flash it, without risk of bricking.
Click to expand...
Click to collapse
Is it normal for the ota to have been reelased and still no sign of the 4.4.3 SBF on motorola site?
ramarivera said:
Is it normal for the ota to have been reelased and still no sign of the 4.4.3 SBF on motorola site?
Click to expand...
Click to collapse
Yes, it is completely normal. Usually, the SBF is not released for days, weeks, or sometimes even months after the OTA comes out.
I went from 4.4.3 Retail Brazil to 4.4.2, it is possible, yes, you may have a gpt.bin mismatch but at the end I took the 4.4.3 OTA and 4.4.4. And it is working fine. The reason I had to downgrade was that my 4.4.3 was rooted and with xposed and uninstalling and flashing stock recovery did not work while booting the 4.4.4 OTA.
So it can be done but with precaution.
ramarivera said:
Is it normal for the ota to have been reelased and still no sign of the 4.4.3 SBF on motorola site?
Click to expand...
Click to collapse
Define Moto's site.
For example -> http://sbf.droid-developers.org/ is neither owned, nor operated, nor sponsored, nor connected to moto in anyway. Its hosted, run, maintained by some "guys" who come across or otherwise FIND the SBF files, and post them. SBF/FXZ files do not appear there until they are found or leaked. How long that takes has no pattern.
On the other hand... This site -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images *IS* owned and operated by Motorola. It contains the recovery images for the Developer Edition phones (XT1053 and XT1060... note these images also work for the equivalent Non-Dev XT1053 and XT1060 from moto maker and "retail"). Moto posts the images, but it seems its usually AFTER that particular android version has been rolled out to all models in all locations (i.e. the 4.4.2 SBF for the GSM and VZW Dev Edition X didn't show up on Moto's site until after the roll out to 4.4.2 was done on all carriers to all X models, even non-Dev Edition devices).
aben2amu said:
I went from 4.4.3 Retail Brazil to 4.4.2, it is possible, yes, you may have a gpt.bin mismatch but at the end I took the 4.4.3 OTA and 4.4.4. And it is working fine. The reason I had to downgrade was that my 4.4.3 was rooted and with xposed and uninstalling and flashing stock recovery did not work while booting the 4.4.4 OTA.
So it can be done but with precaution.
Click to expand...
Click to collapse
Thats exactly what i want to do, i have a XT1058 , so so say its safe then?
KidJoe said:
Define Moto's site.
For example -> http://sbf.droid-developers.org/ is neither owned, nor operated, nor sponsored, nor connected to moto in anyway. Its hosted, run, maintained by some "guys" who come across or otherwise FIND the SBF files, and post them. SBF/FXZ files do not appear there until they are found or leaked. How long that takes has no pattern.
On the other hand... This site -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images *IS* owned and operated by Motorola. It contains the recovery images for the Developer Edition phones (XT1053 and XT1060... note these images also work for the equivalent Non-Dev XT1053 and XT1060 from moto maker and "retail"). Moto posts the images, but it seems its usually AFTER that particular android version has been rolled out to all models in all locations (i.e. the 4.4.2 SBF for the GSM and VZW Dev Edition X didn't show up on Moto's site until after the roll out to 4.4.2 was done on all carriers to all X models, even non-Dev Edition devices).
Click to expand...
Click to collapse
Yes, my bad, i was talking about http://sbf.droid-developers.org
ramarivera said:
Thats exactly what i want to do, i have a XT1058 , so so say its safe then?
Yes, my bad, i was talking about http://sbf.droid-developers.org
Click to expand...
Click to collapse
@ramarivera : It is your phone, so you can do with it as you would like. Keep in mind that although the procedure worked for that individual, if you try this, you are doing so at your own risk.
I wish you the best of luck. :good: