Related
OFFICIAL FXZ IS AVAILABLE: http://sbf.droid-developers.org/phone.php?device=0
I can verify, I was about to get a refurb from Verizon and this was the only thing could unbrick it.
I didn't brick, but things just ... aren't right after the update. I tried to go back to 4.2.2 to reroot and move back to 4.4, but that failed as I couldn't downgrade any longer. Now I get force closes and what not. Hope this helps, thanks so much!
icase81 said:
I didn't brick, but things just ... aren't right after the update. I tried to go back to 4.2.2 to reroot and move back to 4.4, but that failed as I couldn't downgrade any longer. Now I get force closes and what not. Hope this helps, thanks so much!
Click to expand...
Click to collapse
what's not right exactly? i've noticed improvements in responsiveness and battery life with no downside.
yeah, if you're on a locked device there is no way to downgrade. if you're on an unlocked device, you will most likely be able to fxz to 4.2.2 or 4.4 by flashing everything except motoboot and gpt. i'm on an unlocked device, but i can't think of any reason why i'd want to downgrade.
Q9Nap said:
what's not right exactly? i've noticed improvements in responsiveness and battery life with no downside.
yeah, if you're on a locked device there is no way to downgrade. if you're on an unlocked device, you will most likely be able to fxz to 4.2.2 or 4.4 by flashing everything except motoboot and gpt. i'm on an unlocked device, but i can't think of any reason why i'd want to downgrade.
Click to expand...
Click to collapse
So I had a rooted 4.4. Get into the soak test, fxz'd back to stock 4.4 to take the 4.4.2 update. Got it, and everything was peachy for 2 days, no issues at all. Decided I wanted to try and re-root, after people confirmed root stuck around after the 4.4.2 ota. So I tried to fxz back to 4.2.2 to use the slapmymoto method, but flashing the 4.2.2 failed (obviously). So I just wiped user data and cache, booted back up and still had 4.4.2. But now if I try and goto settings -> security, it just force closes. This just feel a bit 'off'.
I just am waiting for the 4.4.2 fxz to come out so I can just flash back to 100% stock 4.4.2. Also, for what its worth, the system.img in the zip from this thread doesn't flash for me. Fails preflash validation, same as 4.4 and 4.2.2. I was able to flash the recovery and boot img though. *shrug* everything works fine for now minus the settings force closes.I tried clearing cache, and from what I can see on other phones, this is usually a permissions issue. Only with stock recovery, I can't run fix permissions and can't make chmod's to /system via adb shell.
icase81 said:
So I had a rooted 4.4. Get into the soak test, fxz'd back to stock 4.4 to take the 4.4.2 update. Got it, and everything was peachy for 2 days, no issues at all. Decided I wanted to try and re-root, after people confirmed root stuck around after the 4.4.2 ota. So I tried to fxz back to 4.2.2 to use the slapmymoto method, but flashing the 4.2.2 failed (obviously). So I just wiped user data and cache, booted back up and still had 4.4.2. But now if I try and goto settings -> security, it just force closes. This just feel a bit 'off'.
I just am waiting for the 4.4.2 fxz to come out so I can just flash back to 100% stock 4.4.2. Also, for what its worth, the system.img in the zip from this thread doesn't flash for me. Fails preflash validation, same as 4.4 and 4.2.2. I was able to flash the recovery and boot img though. *shrug* everything works fine for now minus the settings force closes.I tried clearing cache, and from what I can see on other phones, this is usually a permissions issue. Only with stock recovery, I can't run fix permissions and can't make chmod's to /system via adb shell.
Click to expand...
Click to collapse
the only way to have root on a locked device, as of this posting, is to be rooted on 4.4 before applying the update.
wiping data and cache should fix any force close issues (hopefully).
if not, you can try reapplying the update and wiping data and cache.
please post whether either of these things works to fix your issue.
THIS thread doesn't mention anything about system.img, this one does:
http://forum.xda-developers.com/moto-x/development/xt1060-164-55-2-unofficial-fxz-unlocked-t2659682
the title specifies that it is for unlocked devices only.
Q9Nap said:
the only way to have root on a locked device, as of this posting, is to be rooted on 4.4 before applying the update.
wiping data and cache should fix any force close issues (hopefully).
if not, you can try reapplying the update and wiping data and cache.
please post whether either of these things works to fix your issue.
THIS thread doesn't mention anything about system.img, this one does:
http://forum.xda-developers.com/moto-x/development/xt1060-164-55-2-unofficial-fxz-unlocked-t2659682
the title specifies that it is for unlocked devices only.
Click to expand...
Click to collapse
Cache definitely didn't fix it. Tried that last night. I spent 40 minutes redownloading and setting up apps, so wiping user data again wouldn't be fun. I'll check it out in a few minutes and report back.
EDIT: Nope, cache and userdata wipe did not fix it. Oh well, I'll just wait until the fxz image is out for 4.4.2 and try that then.
So if I'm currently on 4.4 Rooted with a locked device, would I need to flash the stock recovery file that you've supplied first prior to taking the OTA, or do I have to go back to 4.2.2 and then take the update?
I would like to keep root, but after searching around this forum and couple of others, it seems those of us with locked devices are not seeing much luck.
bawoo said:
So if I'm currently on 4.4 Rooted with a locked device, would I need to flash the stock recovery file that you've supplied first prior to taking the OTA, or do I have to go back to 4.2.2 and then take the update?
I would like to keep root, but after searching around this forum and couple of others, it seems those of us with locked devices are not seeing much luck.
Click to expand...
Click to collapse
I would like to know this as well!
bawoo said:
So if I'm currently on 4.4 Rooted with a locked device, would I need to flash the stock recovery file that you've supplied first prior to taking the OTA, or do I have to go back to 4.2.2 and then take the update?
I would like to keep root, but after searching around this forum and couple of others, it seems those of us with locked devices are not seeing much luck.
Click to expand...
Click to collapse
your question really belongs in the q & a section...
as the op states, this recovery is for use only if you have bricked while attempting to apply the update.
to apply the update successfully, you need to have an unmodified system. so if you've made any changes to system files, you should start from the beginning to get to unmodified, rooted 4.4; then apply the update.
updated op with link to fxz download page; 4.4.2 is now available. locked device users please be aware that you will not be able to keep root if you flash the full fxz; not that you really keep it anyway after the taking the ota...
dev edition ftw!
Q9Nap said:
updated op with link to fxz download page; 4.4.2 is now available. locked device users please be aware that you will not be able to keep root if you flash the full fxz; not that you really keep it anyway after the taking the ota...
dev edition ftw!
Click to expand...
Click to collapse
Just an update to my totally off topic issue, flashing the 4.4.2 fxz fixed my crashing Security settings issue. :good: Thanks for the help even though it really wasn't your problem or anything to do with the thread.
icase81 said:
Just an update to my totally off topic issue, flashing the 4.4.2 fxz fixed my crashing Security settings issue. :good: Thanks for the help even though it really wasn't your problem or anything to do with the thread.
Click to expand...
Click to collapse
sure, np. glad you got it working. it's unfortunate that locked users lose root with the 4.4.2 build though.
Another off-topic issue but I was wondering if anyone could help me (VZN Dev Edition). I was on Eclipse 3.1, I used the Mac OS 2.01 Toolkit to upgrade to 4.2.2. I was able to boot but the color on the screen is off (red is showing as blue and blue as red) and camera does not work. I thought it was a small software issue. I installed TWRP and flashed Eclipse 3.2 but still had the same issues.
Any help? Can I use the Toolkit to downgrade to 4.4?
wmjchoi said:
Another off-topic issue but I was wondering if anyone could help me (VZN Dev Edition). I was on Eclipse 3.1, I used the Mac OS 2.01 Toolkit to upgrade to 4.2.2. I was able to boot but the color on the screen is off (red is showing as blue and blue as red) and camera does not work. I thought it was a small software issue. I installed TWRP and flashed Eclipse 3.2 but still had the same issues.
Any help? Can I use the Toolkit to downgrade to 4.4?
Click to expand...
Click to collapse
I'm not familiar with that particular toolkit, but I'm assuming it flashed gpt and motoboot to the 4.4.2 version (I'm also hoping you meant to type 4.4.2, otherwise, flashing an old version might be your problem) both of which you shouldn't try to downgrade. I would recommend re-flashing all of 4.4.2 from the sbf (which is hopefully what that toolkit does -- you should probably post in that thread for this)
Where I am: I'm on a locked Verizon Moto X w/ Root, WP enabled on 4.4.2.
How I got here: I was rooted on 4.4 with WP disabled, and took the OTA after disabling xposed. I kept root and WP was re-enabled.
Now when I try to boot into recovery I get the same error 'slappydj1' was getting earlier in this thread...:
Partition (recovery) Security Version Downgraded
Boot up failed
Any idea if I will be able to flash just the stock recovery from the 4.4.2 fxz and get recovery back?
Or might this cause new sorts of issues?
leffer said:
Where I am: I'm on a locked Verizon Moto X w/ Root, WP enabled on 4.4.2.
How I got here: I was rooted on 4.4 with WP disabled, and took the OTA after disabling xposed. I kept root and WP was re-enabled.
Now when I try to boot into recovery I get the same error 'slappydj1' was getting earlier in this thread...:
Partition (recovery) Security Version Downgraded
Boot up failed
Any idea if I will be able to flash just the stock recovery from the 4.4.2 fxz and get recovery back?
Or might this cause new sorts of issues?
Click to expand...
Click to collapse
Not sure how you took the 4.4.2 OTA as it needs STOCK Recovery in order to install.
You could TRY re-flashing stock recovery via mfastboot, but I'm not sure what state your phone is in, and/or if flashing stock recovery will make things worse.
KidJoe said:
Not sure how you took the 4.4.2 OTA as it needs STOCK Recovery in order to install.
You could TRY re-flashing stock recovery via mfastboot, but I'm not sure what state your phone is in, and/or if flashing stock recovery will make things worse.
Click to expand...
Click to collapse
Yeah, I had stock recovery when I took the OTA, my guess is for some reason the recovery didn't update to 4.4.2 during the OTA. No idea why.
Anyway, I flashed the recovery.img from the 4.4.2 FXZ and it worked. So I have stock recovery back.
Thanks
Would I use the T-Mobile fxz to fastboot flash a Dev Ed. GSM on T-Mobile plan?
leffer said:
Yeah, I had stock recovery when I took the OTA, my guess is for some reason the recovery didn't update to 4.4.2 during the OTA. No idea why.
Anyway, I flashed the recovery.img from the 4.4.2 FXZ and it worked. So I have stock recovery back.
Thanks
Click to expand...
Click to collapse
I might be in the same boat, any help would be appreciated. I was rooted pre-4.4.2, and took the VZW OTA, root survived... everything has been good. Now when I try a factory reset it, it boots to FastBoot mode and Recovery option just reboots the phone.
It does say: Partition (recovery) Security Version Downgraded
Fastboot Reason: Boot Failure
Phone can reboot into Android and works just fine. Should I flash the entire 4.4.2 image or is there a glaring red flag that I'm missing like trying 4.2.2 or 4.4 first?
Thanks all!
I rooted the phone, everything was going good. I was playing with Exposed and I wanted to remove soft keys. I found a post to edit build.prop and I did not back up build.prop before i tried to edit it and all went all from there.
Now When i turn it on i get it booted up but it says unfortunately androidsystem.ui has stopped and wont go any farther,
I am running 4.4.2 stock rom, After this I did a factory reset hoping this to fix the problem...This did not fix it lol.
I am afraid I can not ADB it now as I do not have developer options and USB debugging....
Anyway to edit Build.prop from the computer?
if not how do i fix this?
Thank you!
Bobert the great said:
I rooted the phone, everything was going good. I was playing with Exposed and I wanted to remove soft keys. I found a post to edit build.prop and I did not back up build.prop before i tried to edit it and all went all from there.
Now When i turn it on i get it booted up but it says unfortunately androidsystem.ui has stopped and wont go any farther,
I am running 4.4.2 stock rom, After this I did a factory reset hoping this to fix the problem...This did not fix it lol.
I am afraid I can not ADB it now as I do not have developer options and USB debugging....
Anyway to edit Build.prop from the computer?
if not how do i fix this?
Thank you!
Click to expand...
Click to collapse
First off, brick means it's as functional as a fired clay brick.
Second. ADB from recovery. If you don't have a custom recovery, factory reset.
khaytsus said:
First off, brick means it's as functional as a fired clay brick.
Second. ADB from recovery. If you don't have a custom recovery, factory reset.
Click to expand...
Click to collapse
I don't think a factory reset would help since it only wipes data and cache. He said he already tried one without success.
If you have a custom recovery installed, you have a couple of options. If adb is working, you can pull/push a fixed build.prop. Or you could find a stock build.prop and create a flashable zip for it.
If you don't have a custom recovery, as far as I know you're pretty much stuck having to flash a factory image, which means you'll lose all your data because your internal storage will be wiped.
detonation said:
I don't think a factory reset would help since it only wipes data and cache. He said he already tried one without success.
If you have a custom recovery installed, you have a couple of options. If adb is working, you can pull/push a fixed build.prop. Or you could find a stock build.prop and create a flashable zip for it.
If you don't have a custom recovery, as far as I know you're pretty much stuck having to flash a factory image, which means you'll lose all your data because your internal storage will be wiped.
Click to expand...
Click to collapse
I do not have a custom recovery as I rooted 4.4.2 and as far as I know you can not have recovery with 4.4.2 root unless you downgrade to 4.2 first, root then update, Correct?
I was wondering, Can i install custom recovery now?
Keep in mind this is my second LG G2, The first one I COMPLETELY bricked it and it wont power on, no LG image, No charge, no download mode nothing. I do not want that again as it is a paper weight now lol.
http://forum.xda-developers.com/showthread.php?t=2432476
Would this be the process I would go with?
Thanks to everyone for the help....I hope to have my phone back up and running soon!
Bobert the great said:
I do not have a custom recovery as I rooted 4.4.2 and as far as I know you can not have recovery with 4.4.2 root unless you downgrade to 4.2 first, root then update, Correct?
I was wondering, Can i install custom recovery now?
Keep in mind this is my second LG G2, The first one I COMPLETELY bricked it and it wont power on, no LG image, No charge, no download mode nothing. I do not want that again as it is a paper weight now lol.
Click to expand...
Click to collapse
I have the Verizon version so I can't speak for others, but you only need to downgrade to the 4.2 bootloader to install the recovery and then you can go back to the 4.4 bootloader. I used AutoRec which does it all for you automatically. But at this point I don't think you'll be able to flash a custom recovery, as you either need adb access or the ability to install an apk.
Here's the guide for flashing the factory images: http://forum.xda-developers.com/showthread.php?t=2432476
I suggest trying the TOT method first if your variant is supported
Thank you,
I believe I will trade to flash stock rom again and root from 4.4.
Wish me luck.
As i look into the TOT flash procedure I am wondering what Variant the D803 is....
I have a Telus LG G2 and I believe it is the D803....
It is fixed everyone. Thanks to everyone who helped.
Sent from my LG-D803 using XDA Free mobile app
Bobert the great said:
It is fixed everyone. Thanks to everyone who helped.
Sent from my LG-D803 using XDA Free mobile app
Click to expand...
Click to collapse
I had this issue.
http://forum.xda-developers.com/showthread.php?p=52733594
Now I'm in 4.4.2 again but with a custom recovery and backup. Ready to give it a whirl again.
hello guys, straight to the point
can someone upload to mega a stock 5.1.1 firmware backup to restore through TWRP or philztouch?
the thing is mine cant boot up at optimizing apps so i need one already booted up
i would be very grateful
move the thread to the correct link... dont know if we have a request section
Jaker89 said:
hello guys, straight to the point
can someone upload to mega a stock 5.1.1 firmware backup to restore through TWRP or philztouch?
the thing is mine cant boot up at optimizing apps so i need one already booted up
i would be very grateful
move the thread to the correct link... dont know if we have a request section
Click to expand...
Click to collapse
what you have, against the idea of flash the rom again? as does everyone.
Rajada said:
what you have, against the idea of flash the rom again? as does everyone.
Click to expand...
Click to collapse
it just wont boot up when i reflash, even wiped
Jaker89 said:
it just wont boot up when i reflash, even wiped
Click to expand...
Click to collapse
all phones boot, after a successful flash of a stock ROM with factory reset.
if your not start it has a hardware problem
I've had my Moto X Pure for over a few months now. After rooting it, i installed TWRP 3.0.2 and have had different roms and not come across any problems regarding a hard brick. I was using my phone on the CM 13 Rom, and it was bugging out, so i tried to reboot. After trying to reboot, it would come to the WARNING BOOTLOADER UNLOCKED SCREEN and not boot past that, let alone get into the actual loading screen. Now, i cant boot into twrp. When i try to enter recovery mode, it goes to the TWRP screen, and sits there without proceeding. I cant boot the phone, or boot into recovery. I can only boot into the bootloader. ANY AND EVERY ADVICE IS APPRECIATED THANK YOU!!!
Edit: I fixed it. had to manually extract and reflash some files from a very useful restore to stock tool.
http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905
Thank you for all of the help so quickly.
kagarii said:
I've had my Moto X Pure for over a few months now. After rooting it, i installed TWRP 3.0.2 and have had different roms and not come across any problems regarding a hard brick. I was using my phone on the CM 13 Rom, and it was bugging out, so i tried to reboot. After trying to reboot, it would come to the WARNING BOOTLOADER UNLOCKED SCREEN and not boot past that, let alone get into the actual loading screen. Now, i cant boot into twrp. When i try to enter recovery mode, it goes to the TWRP screen, and sits there without proceeding. I cant boot the phone, or boot into recovery. I can only boot into the bootloader. ANY AND EVERY ADVICE IS APPRECIATED THANK YOU!!!
Click to expand...
Click to collapse
If your able to boot into bootloader you can try to reflashTWRP or flash the original recovery and the original system files.
kagarii said:
I've had my Moto X Pure for over a few months now. After rooting it, i installed TWRP 3.0.2 and have had different roms and not come across any problems regarding a hard brick. I was using my phone on the CM 13 Rom, and it was bugging out, so i tried to reboot. After trying to reboot, it would come to the WARNING BOOTLOADER UNLOCKED SCREEN and not boot past that, let alone get into the actual loading screen. Now, i cant boot into twrp. When i try to enter recovery mode, it goes to the TWRP screen, and sits there without proceeding. I cant boot the phone, or boot into recovery. I can only boot into the bootloader. ANY AND EVERY ADVICE IS APPRECIATED THANK YOU!!!
Click to expand...
Click to collapse
Can you get it into fastboot mode? If you can, it sounds like somehow the recovery is corrupt and you would need to use 'fastboot erase recovery' first, and then 'fastboot flash recovery recovery.img' (using the twrp .img flashable file of course)
I hope that does the trick. Only think I can think of other than that is look for the automated return to stock tool for the moto x 2015 and use that.
thanks
[email protected] said:
If your able to boot into bootloader you can try to reflashTWRP or flash the original recovery and the original system files.
Click to expand...
Click to collapse
fixed it thank you!
thanks
benjmiester said:
Can you get it into fastboot mode? If you can, it sounds like somehow the recovery is corrupt and you would need to use 'fastboot erase recovery' first, and then 'fastboot flash recovery recovery.img' (using the twrp .img flashable file of course)
I hope that does the trick. Only think I can think of other than that is look for the automated return to stock tool for the moto x 2015 and use that.
Click to expand...
Click to collapse
fixed it thank you!
kagarii said:
fixed it thank you!
Click to expand...
Click to collapse
Great news! You're very welcome. I was in that exact same situation with my old Xperia Z2. It's pretty scary.
kagarii said:
fixed it thank you!
Click to expand...
Click to collapse
Can you tell us what fixed it? Do you know if it was firmware related? Was it the recovery? I have multiple people on this device all on custom software, always interested to find the cause of these types of issues for future reference. And most importantly, glad you got it resolved!
Sent from my XT1575 using Tapatalk
DonKilluminati23 said:
Can you tell us what fixed it? Do you know if it was firmware related? Was it the recovery? I have multiple people on this device all on custom software, always interested to find the cause of these types of issues for future reference. And most importantly, glad you got it resolved!
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
I honestly have no idea what the problem was. But i downloaded and used someones lollipop restore to stock tool, literally restoring to the original state you got the phone in, and it worked. I believe it had something to do with the rom, and possibly some xposed modules i had installed, but there was nothing that actually messed around with the phone's system files. I couldn't access recovery in anyway whatsoever, but my advice to you is that if you ever need help because the phone is potentially hard-bricked, see if it connects to PC and if it does use the restore to stock tool.
kagarii said:
I honestly have no idea what the problem was. But i downloaded and used someones lollipop restore to stock tool, literally restoring to the original state you got the phone in, and it worked. I believe it had something to do with the rom, and possibly some xposed modules i had installed, but there was nothing that actually messed around with the phone's system files. I couldn't access recovery in anyway whatsoever, but my advice to you is that if you ever need help because the phone is potentially hard-bricked, see if it connects to PC and if it does use the restore to stock tool.
Click to expand...
Click to collapse
Were you on marshmallow before you used the restore to stock tool? I thought downgrading android versions was a no-no currently.
jDally987 said:
Were you on marshmallow before you used the restore to stock tool? I thought downgrading android versions was a no-no currently.
Click to expand...
Click to collapse
It's possible, through tools like this. I don't know too much of the topic.
jDally987 said:
Were you on marshmallow before you used the restore to stock tool? I thought downgrading android versions was a no-no currently.
Click to expand...
Click to collapse
Mine wouldnt let me factory reset in twrp to flash something else while on cr droid it jist vibrates now it wont even boot into cr droid ive try to flash another rom but nothing since recovery suddenly wont let me wipe. Any advice on whats causing this i have a 64 gb adopted sd catd also i think i accidently repartitioned sd card in twrp.
Sherrillface said:
Mine wouldnt let me factory reset in twrp to flash something else while on cr droid it jist vibrates now it wont even boot into cr droid ive try to flash another rom but nothing since recovery suddenly wont let me wipe. Any advice on whats causing this i have a 64 gb adopted sd catd also i think i accidently repartitioned sd card in twrp.
Click to expand...
Click to collapse
Old thread. But can you at least get into TWRP recovery? Why won't it let you wipe? Like what does it say?
jDally987 said:
Old thread. But can you at least get into TWRP recovery? Why won't it let you wipe? Like what does it say?
Click to expand...
Click to collapse
Nothing it just vibrates as soon as i hit factory reset then bootloops now it wont even go into recovery just fastboot screen but cant get fastboot to work at all and have all drivers android studio etc. Nothing will work need a new solution
It was hash kernel it corrupted all 64 gigs of storage and music etc. Had to return to stock via auto flash firmware.
Mine is XT1572 device. Since the mentioned tool was not available for this model, I took the chance with XT1575 tool. It did all the steps but the issue has become worse. Now, my device is automatically getting On and OFF in seconds and does not boot beyond the bootloader 'unlocked' warning screen. Please please please help !!!!
Solved
zoel.fahmi said:
Guys, i have big problem here.
i wipe system partition, i know i shouldn't have.
Now my phone without Android, any idea how to flash it back to stock?
It always show error when i tried to use twrp from pc (using command prompt + adb)
What stock ROM i should've flash it? Kitkat or Lollipop?
Thanks
Click to expand...
Click to collapse
Just flash any of the ROMs out there?and lemme remind you this is the Development section