Related
I tried to search it but no luck.
I have a Xperia TX and I want to dump the firmware out from it.
is it possible to do that. it's a unlocked stock firmware and not a ROOTed phone.
Thanks
xcody said:
I tried to search it but no luck.
I have a Xperia TX and I want to dump the firmware out from it.
is it possible to do that. it's a unlocked stock firmware and not a ROOTed phone.
Thanks
Click to expand...
Click to collapse
Read the second post in the all in one thread about creating a ftf file.
That will give you the latest software on a ftf file. However, if you have an update due and want to back up the system you are on its trickier.
Best bet is to do an adb pull of system and use dsixdas kitchen to convert it to a .zip file. But you will need to be rooted and have cmw to restore it.
My advice (As its given in the all in one thread) is to make an ftf as soon as you get your phone or as soon as you update in order to be able to flash it back when you want.
The ftf files you make from this method are completely stock.
EDIT
Unlocked but not rooted? What would be the point in doing that?
Thanks gregbradley,
It's unlocked because I got it as unlocked. not root because it's for my wife. she doesn't need a root phone. lol
Anyway, I guess this can't be done without rooting the phone. nvm then.
gregbradley said:
Read the second post in the all in one thread about creating a ftf file.
That will give you the latest software on a ftf file. However, if you have an update due and want to back up the system you are on its trickier.
Best bet is to do an adb pull of system and use dsixdas kitchen to convert it to a .zip file. But you will need to be rooted and have cmw to restore it.
My advice (As its given in the all in one thread) is to make an ftf as soon as you get your phone or as soon as you update in order to be able to flash it back when you want.
The ftf files you make from this method are completely stock.
EDIT
Unlocked but not rooted? What would be the point in doing that?
Click to expand...
Click to collapse
xcody said:
Thanks gregbradley,
It's unlocked because I got it as unlocked. not root because it's for my wife. she doesn't need a root phone. lol
Anyway, I guess this can't be done without rooting the phone. nvm then.
Click to expand...
Click to collapse
Ahh, you dont mean unlocked, you mean sim unlocked. Unlocked for devs means bootloader unlocked.
also, you do not need to be rooted to make a ftf file.
read the instructions in the link
Hi Gregbradley,
I tried to search the forum and googled it also, but I only can find the way to make ftf from the file that downloaded by using Sony PC Companion or SEUS. But not from the phone itself.
What I need is the firmware from the phone.
gregbradley said:
Ahh, you dont mean unlocked, you mean sim unlocked. Unlocked for devs means bootloader unlocked.
also, you do not need to be rooted to make a ftf file.
read the instructions in the link
Click to expand...
Click to collapse
xcody said:
Hi Gregbradley,
I tried to search the forum and googled it also, but I only can find the way to make ftf from the file that downloaded by using Sony PC Companion or SEUS. But not from the phone itself.
What I need is the firmware from the phone.
Click to expand...
Click to collapse
take a backup using recovery and use that system. img in dsixdas kitchen
but that involes rooting.
As i said in previousposts, thats why it should be done as sooner rather later.
Listen, just update and use the new firmware, dont sweat it
Hey all,
I'm having some trouble flashing TWRP on my phone. I've been following this guide here. When attempting to install TWRP to get root, however, it won't work. I've tried several different versions of fastboot & mfastboot. Sometimes I get a "bootloader variable not found" error, but most of the time now it exits saying it's successful. However, when I reboot into fastboot mode and then into recovery mode, it's still at the stock recovery. Can someone tell me what I'm doing wrong?
If it helps, my unlock status code shown is 3.
Thanks in advance!
thehockeydude44 said:
Hey all,
I'm having some trouble flashing TWRP on my phone. I've been following this guide here. When attempting to install TWRP to get root, however, it won't work. I've tried several different versions of fastboot & mfastboot. Sometimes I get a "bootloader variable not found" error, but most of the time now it exits saying it's successful. However, when I reboot into fastboot mode and then into recovery mode, it's still at the stock recovery. Can someone tell me what I'm doing wrong?
If it helps, my unlock status code shown is 3.
Thanks in advance!
Click to expand...
Click to collapse
Had the same issue, what I did is rsdlite back to stock and then attempt to flash twrp ,it worked.
Also make sure the twrp download is OK, you may want to re download it
Sent on my Moto X
flashallthetime said:
Had the same issue, what I did is rsdlite back to stock and then attempt to flash twrp ,it worked.
Also make sure the twrp download is OK, you may want to re download it
Sent on my Moto X
Click to expand...
Click to collapse
Forgot to mention I got the OTA as soon as my phone turned on. So go back to stock, root and then do the OTA?
thehockeydude44 said:
Forgot to mention I got the OTA as soon as my phone turned on. So go back to stock, root and then do the OTA?
Click to expand...
Click to collapse
No, ota won't flash with custom recovery.
Which carrier are you on.
Try a factory reset, you will lose all your data etc, so do a backup on your computer
Sent on my Moto X
flashallthetime said:
No, ota won't flash with custom recovery.
Which carrier are you on.
Try a factory reset, you will lose all your data etc, so do a backup on your computer
Sent on my Moto X
Click to expand...
Click to collapse
I didn't think it would... I'm on ATT, with a Dev edition. And no data to backup yet, just got the phone today.
Could you point me to where you got the working .img file?
thehockeydude44 said:
I didn't think it would... I'm on ATT, with a Dev edition. And no data to backup yet, just got the phone today.
Could you point me to where you got the working .img file?
Click to expand...
Click to collapse
Here' s the rsdlite thread http://forum.xda-developers.com/showthread.php?t=2446515
I believe on your op you used another thread, that thread has I believe the link for rsdlite
Here's the firmware thread http://forum.xda-developers.com/showthread.php?t=2538394
Prior to setting up rsdlite make sure you have the latest moto device manager and drivers installed. Also open up the sbf file and find the XML file, open it up and delete the line that has getvar in it
I took the camera 4.2 ota and I could not flash twrp either even though my boot loader is unlocked. I won't take any more ota's , I'll just flash the firmware through rsdlite
Sent on my Moto X
flashallthetime said:
Here' s the rsdlite thread http://forum.xda-developers.com/showthread.php?t=2446515
I believe on your op you used another thread, that thread has I believe the link for rsdlite
Here's the firmware thread http://forum.xda-developers.com/showthread.php?t=2538394
Prior to setting up rsdlite make sure you have the latest moto device manager and drivers installed. Also open up the sbf file and find the XML file, open it up and delete the line that has getvar in it
I took the camera 4.2 ota and I could not flash twrp either even though my boot loader is unlocked. I won't take any more ota's , I'll just flash the firmware through rsdlite
Sent on my Moto X
Click to expand...
Click to collapse
OK, I'll use rsdlite to get back to stock, and then flash the new firmware, and then see if I can flash the twrp.img. I saw the line about deleting the getvar line, so I'll make sure I do that too... thanks for the help, I'll let you know how it goes.
thehockeydude44 said:
OK, I'll use rsdlite to get back to stock, and then flash the new firmware, and then see if I can flash the twrp.img. I saw the line about deleting the getvar line, so I'll make sure I do that too... thanks for the help, I'll let you know how it goes.
Click to expand...
Click to collapse
Just flash the AT&T KitKat 4.4 sbf file, then you're up to date
Sent on my Moto X
flashallthetime said:
Just flash the AT&T KitKat 4.4 sbf file, then you're up to date
Sent on my Moto X
Click to expand...
Click to collapse
It worked! It must have been because of the OTA I got immediately... but flashing the correct 4.4 worked (I downloaded it directly from Motorola, since none of those specifically said GSM Dev Edition (turned out to be the T-Mo one). SuperSU works too, now just to install TiBu and be on my merry way!
thehockeydude44 said:
It worked! It must have been because of the OTA I got immediately... but flashing the correct 4.4 worked (I downloaded it directly from Motorola, since none of those specifically said GSM Dev Edition (turned out to be the T-Mo one). SuperSU works too, now just to install TiBu and be on my merry way!
Click to expand...
Click to collapse
I think all the firmware files are for either retail or developer editions, anyways glad it worked. I have no idea why this happens with the ota's?
Sent from my XT1058 using XDA Premium 4 mobile app
flashallthetime said:
I think all the firmware files are for either retail or developer editions, anyways glad it worked. I have no idea why this happens with the ota's?
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't know either. Might try and figure it out once I'm done with damn finals in 2 weeks.
I've rooted my Moto X with RockMyMoto, now I unrooted it because I want to OTA Update it to 4.4 Kit Kat.
I've done that, and was stuck on bootloop. Used "fastboot erase cache" to get it running again.
My question is: What should I do with my "unrooted" phone before going to the OTA Update?
I've done some research but it is always answers to specific problems. I think I should download an image from sbf.droid-developers.org/ and flash it with RSD Lite. But do I need to unlock my bootloader in order to do that? Is there any other way I could achieve the same goal?
I really like this kind of stuff, and would like learning in the process... But I think I'm missing something, and I'm afraid to brick my phone after this bootloop problem. And have decided I should ask first, and act later.
(I've bought my device from another person, that bought it from a store. So I think I should download the retail imagem from the website, but does something happen if I download the "wrong" image?)
vh0909 said:
I've rooted my Moto X with RockMyMoto, now I unrooted it because I want to OTA Update it to 4.4 Kit Kat.
I've done that, and was stuck on bootloop. Used "fastboot erase cache" to get it running again.
My question is: What should I do with my "unrooted" phone before going to the OTA Update?
I've done some research but it is always answers to specific problems. I think I should download an image from sbf.droid-developers.org/ and flash it with RSD Lite. But do I need to unlock my bootloader in order to do that? Is there any other way I could achieve the same goal?
I really like this kind of stuff, and would like learning in the process... But I think I'm missing something, and I'm afraid to brick my phone after this bootloop problem. And have decided I should ask first, and act later.
(I've bought my device from another person, that bought it from a store. So I think I should download the retail imagem from the website, but does something happen if I download the "wrong" image?)
Click to expand...
Click to collapse
If you want to keep root with 4.4, follow the steps in SlapMyMoto. If you do not want root in 4.4, yes you can flash the sbf download with RSD Lite. You do not need an unlocked bootloader to flash with RSD Lite. It is always a way to get back to stock.
mjphillips1981 said:
If you want to keep root with 4.4, follow the steps in SlapMyMoto. If you do not want root in 4.4, yes you can flash the sbf download with RSD Lite. You do not need an unlocked bootloader to flash with RSD Lite. It is always a way to get back to stock.
Click to expand...
Click to collapse
Does the process erase all data (like photos and apps for example)?
Thank you for the simple and straight answer!
vh0909 said:
Does the process erase all data (like photos and apps for example)?
Thank you for the simple and straight answer!
Click to expand...
Click to collapse
Yes this process will erase EVERYTHING.
mjphillips1981 said:
Yes this process will erase EVERYTHING.
Click to expand...
Click to collapse
I did that, downloaded the image, then I flashed it into my phone. But it stoped in "reboot In process" and it does not continue. (It rebooted, but didn't erase anything, and it is now on my Homescreen normally)
Is this normal? How do I know if the flash worked?
Guys,i have Retail 1058 Moto X with unlocked Bootloader,TWRP(latest and rooted) and i want to upgrade to 4.4.2!
Some guys already received the 4.4.2 brazilian update via OTA,and extracted the zip file,but,since im on custom recovery,the OTA doesnt reboot the phone into stock and go straight to TWRP,therefore,doesnt conclude the update,and keep restarting!
Since i need the phone,i did a factory reset via TWRP just to get things going!
But,i want to upgrade to 4.4.2!
Is there a way to do that?remove TWRP ou something else?
I've seen some people saying that i need to flash the 4.4 img which it is inside the zip but,i dont have that zip anymore!
Thx in advance!
msespindola said:
Guys,i have Retail 1058 Moto X with unlocked Bootloader,TWRP(latest and rooted) and i want to upgrade to 4.4.2!
Some guys already received the 4.4.2 brazilian update via OTA,and extracted the zip file,but,since im on custom recovery,the OTA doesnt reboot the phone into stock and go straight to TWRP,therefore,doesnt conclude the update,and keep restarting!
Since i need the phone,i did a factory reset via TWRP just to get things going!
But,i want to upgrade to 4.4.2!
Is there a way to do that?remove TWRP ou something else?
I've seen some people saying that i need to flash the 4.4 img which it is inside the zip but,i dont have that zip anymore!
Thx in advance!
Click to expand...
Click to collapse
if you take the 4.4.2 update you will loose root and wont be able to get it back till who knows when.
but you need to flash your phone back to 100% stock just like you did when root your device but instead of using the 4.2.2 CU firmware use the 4.4
here is all the firmware for the Moto X
http://sbf.droid-developers.org/phone.php?device=0
your device is a Att model so you should be able to flash the ATT 4.4 firmware but im not 100% sure but maybe you will find your carrier listed there.
dray_jr said:
if you take the 4.4.2 update you will loose root and wont be able to get it back till who knows when.
but you need to flash your phone back to 100% stock just like you did when root your device but instead of using the 4.2.2 CU firmware use the 4.4
here is all the firmware for the Moto X
http://sbf.droid-developers.org/phone.php?device=0
your device is a Att model so you should be able to flash the ATT 4.4 firmware but im not 100% sure but maybe you will find your carrier listed there.
Click to expand...
Click to collapse
yeah,i know,aware of loosing root,but,mine is retail,and i've found the brazilian retail one(Blur_Version.143.44.8.ghost_row.Brasil.en.BR)!
How do i revert back to stock?never done that before!
Thx for the help so far buddy
msespindola said:
yeah,i know,aware of loosing root,but,mine is retail,and i've found the brazilian retail one(Blur_Version.143.44.8.ghost_row.Brasil.en.BR)!
How do i revert back to stock?never done that before!
Thx for the help so far buddy
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2446515
there are two ways in this guide i like the manual way. but your choice make sure you read everything because if you do this wrong you can brick.
dray_jr said:
http://forum.xda-developers.com/showthread.php?t=2446515
there are two ways in this guide i like the manual way. but your choice make sure you read everything because if you do this wrong you can brick.
Click to expand...
Click to collapse
Okay buddy,will take a look when i get home from work!
One questiona buddy managed to get the fastboot img for me,if i just flash the stock recovery img and then try to update will it work?
msespindola said:
Okay buddy,will take a look when i get home from work!
One questiona buddy managed to get the fastboot img for me,if i just flash the stock recovery img and then try to update will it work?
Click to expand...
Click to collapse
idk i dont like to doing things half way there have been way to many bricks lately.
If he has an unlocked bootloader, why would he not be able to get root back?
I thought when the bootloader was unlocked you had free reign over the device. Shouldn't he be able to upgrade to 4.4.2 and use SU and TWRP to get root back? I don't get why he wouldn't be able to do that.
Flash 4.4.2
Flash TWRP via mfastboot
Install SU zip via TWRP
Boot
Install SU app
What am I missing?
Sent from my Dev Edition Moto X
Schaweet said:
If he has an unlocked bootloader, why would he not be able to get root back?
I thought when the bootloader was unlocked you had free reign over the device. Shouldn't he be able to upgrade to 4.4.2 and use SU and TWRP to get root back? I don't get why he wouldn't be able to do that.
Flash 4.4.2
Flash TWRP via mfastboot
Install SU zip via TWRP
Boot
Install SU app
What am I missing?
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
this is why i dont read on my phone i miss crap anyway if you flash 4.4.2 yes you can flash the 4.4 TWRP and then SuperSU with a unlocked bootloader.. sorry for my miss read thanks for the catch
dray_jr said:
idk i dont like to doing things half way there have been way to many bricks lately.
Click to expand...
Click to collapse
Schaweet said:
If he has an unlocked bootloader, why would he not be able to get root back?
I thought when the bootloader was unlocked you had free reign over the device. Shouldn't he be able to upgrade to 4.4.2 and use SU and TWRP to get root back? I don't get why he wouldn't be able to do that.
Flash 4.4.2
Flash TWRP via mfastboot
Install SU zip via TWRP
Boot
Install SU app
What am I missing?
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Thx guys, I'll do this later, thx for the awesome responses
Sent from my XT1058 using xda app-developers app
dray_jr said:
idk i dont like to doing things half way there have been way to many bricks lately.
Click to expand...
Click to collapse
Can someone else please chime in on this? I have a Dev Edition VZW Moto X, and when the 4.4.2 update is finally available, I want to know what to do. My phone is unlocked & rooted with TWRP installed. Can I just flash the factory recovery and then take the OTA? Or do I have to revert to 100% stock? If I only flash stock recovery and take the OTA, data won't be wiped, will it? That is the big reason I would like to avoid going back to 100% stock if I can.
NPOA556 said:
Can someone else please chime in on this? I have a Dev Edition VZW Moto X, and when the 4.4.2 update is finally available, I want to know what to do. My phone is unlocked & rooted with TWRP installed. Can I just flash the factory recovery and then take the OTA? Or do I have to revert to 100% stock? If I only flash stock recovery and take the OTA, data won't be wiped, will it? That is the big reason I would like to avoid going back to 100% stock if I can.
Click to expand...
Click to collapse
My hope is that someone on here will repackage the OTA for us to sideload. That would be the best case scenario.
If not, I think you just need a stock recovery, but I could be wrong. I've seen someone say you need to flash stock system as well. I have the same questions as you if we don't get a side loadable zip.
Sent from my Dev Edition Moto X
Schaweet said:
My hope is that someone on here will repackage the OTA for us to sideload. That would be the best case scenario.
If not, I think you just need a stock recovery, but I could be wrong. I've seen someone say you need to flash stock system as well. I have the same questions as you if we don't get a side loadable zip.
Click to expand...
Click to collapse
It's not the end of the world if I have to wipe data and restore everything from TiBu, but it's still a PITA I would like to avoid if possible. More importantly, I don't want to run into any issues when installed the update. So if there is any question as to whether stock recovery alone is sufficient for the update to install properly, I will probably go back to full stock to be safe. I guess I have some time to let smarter people figure it out, since there is no update for VZW yet.
NPOA556 said:
It's not the end of the world if I have to wipe data and restore everything from TiBu, but it's still a PITA I would like to avoid if possible. More importantly, I don't want to run into any issues when installed the update. So if there is any question as to whether stock recovery alone is sufficient for the update to install properly, I will probably go back to full stock to be safe. I guess I have some time to let smarter people figure it out, since there is no update for VZW yet.
Click to expand...
Click to collapse
What I've read is you need to go back to stock recovery and also make sure any /system files are unchanged. For example I renamed my old exchange apk's (in /system/app) when I put in the new ones from the nexus 5 on 4.4.2, so I would need to name those files back.
NPOA556 said:
It's not the end of the world if I have to wipe data and restore everything from TiBu, but it's still a PITA I would like to avoid if possible. More importantly, I don't want to run into any issues when installed the update. So if there is any question as to whether stock recovery alone is sufficient for the update to install properly, I will probably go back to full stock to be safe. I guess I have some time to let smarter people figure it out, since there is no update for VZW yet.
Click to expand...
Click to collapse
I'm sure some nice developer will help us along.
What have you done to take you off of stock?
I just have custom recovery and xposed. Xposed shouldn't cause any issues.
Sent from my Dev Edition Moto X
Schaweet said:
I'm sure some nice developer will help us along.
What have you done to take you off of stock?
I just have custom recovery and xposed. Xposed shouldn't cause any issues.
Click to expand...
Click to collapse
I guess nothing, other than TWRP, Xposed, and obviously root. I have seen several people say that you have to unroot before installed an OTA, but I don't know if that applies to the Dev X or just the standard version. A lot of people seem to indicate that you have to go back to stock, so I just want to clarify what is really required.
NPOA556 said:
I guess nothing, other than TWRP, Xposed, and obviously root. I have seen several people say that you have to unroot before installed an OTA, but I don't know if that applies to the Dev X or just the standard version. A lot of people seem to indicate that you have to go back to stock, so I just want to clarify what is really required.
Click to expand...
Click to collapse
Good questions. I'm not sure. We certainly root differently than a non Dev edition. They might have some files modified that we don't have to modify. Also, I wonder is going to stock recovery will unroot us.
I guess we wait and stay patient.
Sent from my Dev Edition Moto X
Surely there must be a way to flash updates through TWRP?
I want to grab one of these
http://sbf.droid-developers.org/phone.php?device=0
and flash it through TWRP. Anyone know if this is possible?
Wouldn't mind 4.4.2 right now on my dev ed, to see if my bluetooth problem gets fixed.
Unfortunately you can not take the ota if
1- you have custom recovery
2- root
3- changed any system file
It will bootloop
Clearing data is always required after any ota
The only hope you have is if someone decides to take that factory image and runnit through kitchen to make it a flashable zip. You will also need the updated modem from either 4.4 or 4.4.2 to prevent system settings from fc ing
This goes for any moto, retail and or developer edition
You may also attempt to flash the sbf firmware and remove the delete userdata from the XML but no guarantee that you will not have issues
Hope that helps
Sent on my Gummy running Lenoto X
To take an ota you must be stock. Meaning everything. As long as you haven't flashed an updated bootloader you can just flash system.IMG and recovery.IMG from the sbf your phone is currently on you can take an ota. A successful ota does NOT require a data wipe.
---------- Post added at 04:08 PM ---------- Previous post was at 04:04 PM ----------
finalarcadia said:
Surely there must be a way to flash updates through TWRP?
I want to grab one of these
http://sbf.droid-developers.org/phone.php?device=0
and flash it through TWRP. Anyone know if this is possible?
Wouldn't mind 4.4.2 right now on my dev ed, to see if my bluetooth problem gets fixed.
Click to expand...
Click to collapse
You cannot flash any of those through twrp! If you want to flash 4.4.2 you need to fastboot the system.IMG and boot.IMG and you will need to wipe your data. If you choose this route you will not be able to take the ota when its available you'd have to wait for the sbf file to be released and update through house of moto, rsd, or fastboot.
flashallthetime said:
Unfortunately you can not take the ota if
1- you have custom recovery
2- root
3- changed any system file
It will bootloop
Clearing data is always required after any ota
...
Click to expand...
Click to collapse
some questions.. and comments...
I agree with #1. You must have STOCK recovery for an OTA to install properly. And #3, because the OTA generally has a file list with check sums to compare against what is on your device to make sure all required files are there and the correct version/size/etc before it will start to install.
#2 I have a question on as I've not had an issue with this unless the root process makes changes to system files (thus causing a problem for #3). I've lost root taking an OTA, but that is it.
Then again, I have a Dev X with unlocked bootloader, and I don't know enough about RockMyMoto, SlapMyMoto, etc was of rooting the X, except that initially they replaced the recovery partition with an image that when selected/booted allowed write to system, etc. This would cause issue with #1 (no longer have stock recovery on the recovery partition), but not sure what, if any system files get touched or altered from stock.
Finally, you mention clearing data being required... This would wipe you back to factory defaults and remove your apps/data. I don't believe its "required" but rather just suggested as it can make the device run smoother after the update is done.
---------- Post added at 05:01 PM ---------- Previous post was at 04:59 PM ----------
msespindola said:
Guys,i have Retail 1058 Moto X with unlocked Bootloader,TWRP(latest and rooted) and i want to upgrade to 4.4.2!
Some guys already received the 4.4.2 brazilian update via OTA,and extracted the zip file,but,since im on custom recovery,the OTA doesnt reboot the phone into stock and go straight to TWRP,therefore,doesnt conclude the update,and keep restarting!
Since i need the phone,i did a factory reset via TWRP just to get things going!
But,i want to upgrade to 4.4.2!
Is there a way to do that?remove TWRP ou something else?
I've seen some people saying that i need to flash the 4.4 img which it is inside the zip but,i dont have that zip anymore!
Thx in advance!
Click to expand...
Click to collapse
Depends on how you rooted.
If you've downloaded the SBF file for the ROM on your device (if you don't have it, see if its available from -> http://sbf.droid-developers.org/phone.php?device=0 ), you can unzip it, and fastboot flash the stock recovery from it onto your device, take the OTA, and then later fastboot flash TWRP back on and install SuperSU again to root.
This assumes you did NOT touch any system files the update will check for prior to running/installing. If you did touch system files, edit build prop, removed/renamed any APK's... then fastboot flash recovery and system before taking the OTA
I just got the 4.4.2 update from claro in chile. But I have not installed it yet. My phone is on 4.2.2 at the moment. The bootloader is unlocked. It is rooted using rockmymoto. What I want to know is what do I need to do to get it ready for the 4.4.2 upgrade? I assume I need to unroot it? Also I have lucky patcher installed and I odexed my system, will this be a problem? Will I be able to get root in 4.4.2?
AGISCI said:
I just got the 4.4.2 update from claro in chile. But I have not installed it yet. My phone is on 4.2.2 at the moment. The bootloader is unlocked. It is rooted using rockmymoto. What I want to know is what do I need to do to get it ready for the 4.4.2 upgrade? I assume I need to unroot it? Also I have lucky patcher installed and I odexed my system, will this be a problem? Will I be able to get root in 4.4.2?
Click to expand...
Click to collapse
There are threads on this in the general folder as well as this folder.
What I don't understand is why you had to root using rockmymoto if your bootloader is unlocked? Why didn't you just flash a custom recovery like TWRP and install SuperSU to root?
Do you have the 4.2.2 post camera update installed?
Cozume said:
There are threads on this in the general folder as well as this folder.
Click to expand...
Click to collapse
I have read various topics in both of the forums on it. But I wanted to be 100% sure of what path I need to follow to be sure I don't brick my phone. 1 thing that had me worried is that I odexed my system with lucky patcher... does this mean I am going to have to flash my firmware back to stock before I can do this?
Cozume said:
What I don't understand is why you had to root using rockmymoto if your bootloader is unlocked? Why didn't you just flash a custom recovery like TWRP and install SuperSU to root?
Click to expand...
Click to collapse
Because I rooted it a month before I unlocked the bootloader.
I still currently have stock recovery though.
Cozume said:
Do you have the 4.2.2 post camera update installed?
Click to expand...
Click to collapse
As far as the post camera update, not sure. My camera version is 3.1.41.2.
AGISCI said:
I have read various topics in both of the forums on it. But I wanted to be 100% sure of what path I need to follow to be sure I don't brick my phone. 1 thing that had me worried is that I odexed my system with lucky patcher... does this mean I am going to have to flash my firmware back to stock before I can do this?
Click to expand...
Click to collapse
That is certainly the safest way to go from all I have read as any system mods could potentially cause a problem. The problem that another poster here had is that the only firmware that is posted for the Claro Chile is the precamera update. He was looking for the postcamera firmware.
http://forum.xda-developers.com/showthread.php?t=2649806
And no one could help him find it. I don't think you can take the OTA if you are on the precamera firmware. Perhaps you can PM the OP in that link and see if he is knowledgeable about Claro chile firmware.
Cozume said:
That is certainly the safest way to go from all I have read as any system mods could potentially cause a problem. The problem that another poster here had is that the only firmware that is posted for the Claro Chile is the precamera update. He was looking for the postcamera firmware.
http://forum.xda-developers.com/showthread.php?t=2649806
And no one could help him find it. I don't think you can take the OTA if you are on the precamera firmware. Perhaps you can PM the OP in that link and see if he is knowledgeable about Claro chile firmware.
Click to expand...
Click to collapse
How can I tell if I am on the pre cam or post cam? Also is there a link that talks about what teh pre cam and post cam does or changed?
AGISCI said:
How can I tell if I am on the pre cam or post cam? Also is there a link that talks about what teh pre cam and post cam does or changed?
Click to expand...
Click to collapse
Go to Settings->About Phone->System Version. What does it say?
139.12.35.ghost_row.AmericaMovil.en.CL
Sent from my Nexus 7 using Tapatalk
AGISCI said:
139.12.35.ghost_row.AmericaMovil.en.CL
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
From the version numbers here:
http://sbf.droid-developers.org/phone.php?device=0
As best I can tell 139.12.35 is the post camera update. The problem is that no one has a copy of the stock firmware posted anywhere that anyone can find.
If that's the case flashing this firmware will not brick me then correct?
Sent from my Nexus 7 using Tapatalk
You say you rooted the phone a month before you unlocked the bootloader. If this is the case then your phone should have been wiped clean as unlocking the bootloader performs a full wipe of the phone.
So something does not add up/make sense.
Steve-x said:
You say you rooted the phone a month before you unlocked the bootloader. If this is the case then your phone should have been wiped clean as unlocking the bootloader performs a full wipe of the phone.
So something does not add up/make sense.
Click to expand...
Click to collapse
I rooted it twice actually. After I unlocked the bootloader it was erased just like you said, and I rooted again using the same method from the first time.
AGISCI said:
If that's the case flashing this firmware will not brick me then correct?
Click to expand...
Click to collapse
Which firmware?
This is from dray_jr on the thread in the Moto X General forum:
the only OTA that can downgrade is 4.4 to 4.2.2 Post Cam
here is what we know right now that might make more sense
4.4 to 4.2.2 Pre Cam will Brick
4.2.2 Post Cam to 4.2.2 Pre Cam will Brick.
4.4.2 to anything will Brick
4.4 to 4.2.2 Post Cam you are ok
http://forum.xda-developers.com/showthread.php?t=2635366&highlight=brick&page=5
You are in quite a unique situation here actually... since there is no stock image that you can go back to. If there was a 4.4 SBF I would have suggested to flash then take the 4.4.2 update. However, it seems as if there was no 4.4 roll out/update for your carrier at all. So this 4.4.2 carrier update would be more than a simple patch from 4.4 to 4.4.2, it would probably end up removing root since you are going from JB to KK.
Your best bet if you want it now is to do the following...
I AM NOT RESPONSIBLE FOR YOUR ACTIONS OR BRICKING YOUR DEVICE
1) Did you make a backup before you messed with anything in the system? If you didn't, then you have to go through the manual process of making sure that it is as clean as a normal stock image.
2) Do you have the original recovery? If not, find a recovery file for your carrier and flash that.
3) Attempt to flash the OTA in the standard recovery.
But honestly, the safest thing to do is to wait until your 4.4.2 SBF is released, that way you can flash it in RSD Lite, preventing a brick as much as possible.
mastarifla said:
But honestly, the safest thing to do is to wait until your 4.4.2 SBF is released, that way you can flash it in RSD Lite, preventing a brick as much as possible.
Click to expand...
Click to collapse
Who releases the sbf? Motorola? Because it looks like the problem is that no one can find the sbf for the 4.2.2 postcamera update for their carrier.
I guess I will have to wait then. I can't afford to brick my phone. I captured the update and pulled it with adb so if anyone needs it I will be able to upload it.
Sent from my Nexus 7 using Tapatalk
Cozume said:
Who releases the sbf? Motorola? Because it looks like the problem is that no one can find the sbf for the 4.2.2 postcamera update for their carrier.
Click to expand...
Click to collapse
Skrilax_CZ maintains the website where the SBF's are stored. Motorola only releases the Developer Edition images to the public, as far as I know. So I believe that this website hosts either his own custom made zips, or he has someone supplying him with insider Moto images (or he works there?).
Personally I think he has a tool to automate this process once he has the firmware loaded onto the phone (if he doesn't have the images already), basically he is adb copying files from the dev partition of his phone and compiling a MD5 hash for each file, then zipping it all up in a nice package to flash with the insider Moto tool RSD Lite (or using manual flash, if you like to live dangerously )
mastarifla said:
Skrilax_CZ maintains the website where the SBF's are stored, as far as I know, Motorola only releases the Dev edition images to the public. So I believe that this website hosts either his own custom made zips, or he has someone supplying him with insider Moto images (or he works there?).
Personally I think he a tool to automate this process once he has the firmware loaded onto the phone (if he doesn't have the images already), basically he is adb copying files from the dev partition of his phone and compiling a MD5 hash for each file, then zipping it all up in a nice package to flash with the insider Moto tool RSD Lite.
Click to expand...
Click to collapse
Thanks! So if you know someone with a stock phone who has never modded or rooted, theoretically you could pull the files from the dev partition of their phone? The trick is getting it into a package that works with RSD Lite?
---------- Post added at 08:56 PM ---------- Previous post was at 08:55 PM ----------
mastarifla said:
Motorola only releases the Developer Edition images to the public, as far as I know.
Click to expand...
Click to collapse
So those of us with Dev Eds should stick to flashing the factory images we get from Motorola directly?
Cozume said:
Thanks! So if you know someone with a stock phone who has never modded or rooted, theoretically you could pull the files from the dev partition of their phone? The trick is getting it into a package that works with RSD Lite?
---------- Post added at 08:56 PM ---------- Previous post was at 08:55 PM ----------
So those of us with Dev Eds should stick to flashing the factory images we get from Motorola directly?
Click to expand...
Click to collapse
Theoretically yes, but in practice it is much harder. Every manufacturer stores their particular data in different partitions on the phone. You have to manually look through the bin files (with a hex editor) in order to determine which are the correct ones. This is even more difficult because most of the information is encrypted. So unless you have insider knowledge or want to compare values in a hex editor, I would strongly suggest you stay away from attempting to make your own files, it can lead to very easy bricks.
I have a XT1053 Unlocked GSM phone (T-Mobile), and the SBF T-Mobile firmwares are the only thing I am going to be flashing, don't flash other regions firmware unless you are certain that it works. IE. let everyone else try it and potentially brick their phone before you end up doing the same thing.
Oh and before I forget, hitting the thanks button works too by the way
mastarifla said:
Theoretically yes, but in practice it is much harder. Every manufacturer stores their particular data in different partitions on the phone. You have to manually look through the bin files (with a hex editor) in order to determine which are the correct ones. This is even more difficult because most of the information is encrypted. So unless you have insider knowledge or want to compare values in a hex editor, I would strongly suggest you stay away from attempting to make your own files, it can lead to very easy bricks.
Click to expand...
Click to collapse
no, I would never try it; I am just trying to understand what the differences are between the various ways for me to brick my device, lol!
mastarifla said:
I have a XT1053 Unlocked GSM phone (T-Mobile), and the SBF T-Mobile firmwares are the only thing I am going to be flashing, don't flash other regions firmware unless you are certain that it works. IE. let everyone else try it and potentially brick their phone before you end up doing the same thing.
Click to expand...
Click to collapse
but if I have a Dev Ed, shouldn't I be flashing the factory images I received from Motorola?
mastarifla said:
Oh and before I forget, hitting the thanks button works too by the way
Click to expand...
Click to collapse
I know I tried but they limit you to 8 thanks a day and I already used mine up for today! I will come back tomorrow and hit the button, promise. I am very good about that. So good that I use up all my thanks quickly. So odd they do that here, but they do.
Cozume said:
but if I have a Dev Ed, shouldn't I be flashing the factory images I received from Motorola?
Click to expand...
Click to collapse
Yes you should, however it is widely known that the T-Mobile version and the Developer Edition have the exact same hardware/firmware (XT1053), actually I think they may have the exact same software build as well, though I am not sure on that one... if they receive the same OTA update that the T-Mobile version receives, that leads me to believe its the same ROM.