Related
My Moto X now refuses to boot. With stock recovery it'll get past the bootloader, then blink an image of a dead android with the message "Error" briefly, and keep doing so every ~10 seconds. If I flash TWRP, any attempt to boot takes me to TWRP, with log messages reading "unable to mount..." for a bunch of partitions (/data, /cache, storage, etc.)
Can I recover my device?
The short sequence of events: I rooted my phone (T-Mobile phone, unlocked it via Motorola's website) and installed TWRP. Later I tried to accept the 4.4.2 OTA update, but the phone wouldn't take the update, because TWRP. Flashed stock recovery tried again, got stuck in bootloop. Tried flashing back the 4.4 / 140.44.3 images from here, now I'm stuck with a blinking error message.
I see there are a bunch of image files bundled into the 4.4.2 / 161.44.25 update - would flashing those do any good?
What version is your bootloader?
Steve-x said:
What version is your bootloader?
Click to expand...
Click to collapse
Version 30.B2.
OK, you still have the 4.4 bootloader so you should have no problem flashing the full tmobile/retail/dev edition build of firmware. I'd perform a full flash with rsdlite or with fastboot using all of the commands in the xml file in the same order. Do not skip any files or bypass any files if there are errors.
This will reset your phone and wipe all content!
Did you attempt to clear dalvik and cache, I believe you can do it through fastboot
Fast boot erase cache should work . its trying to flash the it's ,so you need to delete the cache where the ota file downloaded to
Sent on my Gummy running Lenoto X
so here is abit more help here are the full firmware links
T-Mobile 4.4
http://sbf.droid-developers.org/download.php?device=0&file=2
that is the file you need to flash with RSD Lite or Fastboot and it should get you 100% back up and running.
But then if you want to go to 4.4.2 after you flash the firmware before you add anything or install TWRP just update the phone to 4.4.2 then install the custom recovery and SuperSU.
Steve-x said:
OK, you still have the 4.4 bootloader so you should have no problem flashing the full tmobile/retail/dev edition build of firmware. I'd perform a full flash with rsdlite or with fastboot using all of the commands in the xml file in the same order. Do not skip any files or bypass any files if there are errors.
This will reset your phone and wipe all content!
Click to expand...
Click to collapse
I have tried both RSD Lite, and applying all of the commands from the XML file manually, following the directions from here. Both ways, I still get the blinking error message
The "can't mount..." log messages I get if I flash back to TWRP suggest it could be some sort of partitioning problem, but I'm not sure how to diagnose that.
And the flashing of all files completes successfully?
Steve-x said:
And the flashing of all files completes successfully?
Click to expand...
Click to collapse
I could have sworn that I wasn't getting any errors previously. Now, however, after trying to flash system.img (making sure to use mfastboot, of course), I get an error on the phone, "sp space is not enough". Not sure what it means, and Googling around doesn't turn up any answers.
dray_jr said:
so here is abit more help here are the full firmware links
T-Mobile 4.4
http://sbf.droid-developers.org/download.php?device=0&file=2
Click to expand...
Click to collapse
Yep, that's exactly what I flashed. Made sure the md5sum matched my download and everything.
flashallthetime said:
Did you attempt to clear dalvik and cache, I believe you can do it through fastboot
Click to expand...
Click to collapse
Yep, cleared the cache, no luck
Ouch, it does kind of sound like the partition table got damaged. I suppose you could try "fastboot erase system" and then try to flash the system partition again.
So I guess more warnings into my noobs guide to accept an ota thread
Maybe I should put a notice not to accept the ota and only flash your carriers sbf firmware when available?
Sent on my Gummy running Lenoto X
Steve-x said:
Ouch, it does kind of sound like the partition table got damaged. I suppose you could try "fastboot erase system" and then try to flash the system partition again.
Click to expand...
Click to collapse
Code:
C:\Users\spiffytech\Documents\sdk\platform-tools>fastboot erase system
(bootloader) Variable not supported!
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.101s
Well, that was very weird. In the bootloader I scrolled through the menu and accidentally selected "Factory". No idea what that's supposed to do, but now my phone boots again! I'm going to really, really, hope I don't break it again...
I want to try the 4.4.2 update now, but given I'm not really sure why my device works again I'm scared to.
spiffytech said:
Well, that was very weird. In the bootloader I scrolled through the menu and accidentally selected "Factory". No idea what that's supposed to do, but now my phone boots again! I'm going to really, really, hope I don't break it again...
I want to try the 4.4.2 update now, but given I'm not really sure why my device works again I'm scared to.
Click to expand...
Click to collapse
Good for you, I would wait for the sbf firmware to be available to flash, seems to me a safer way of getting the update
Sent on my Gummy running Lenoto X
flashallthetime said:
Good for you, I would wait for the sbf firmware to be available to flash, seems to me a safer way of getting the update
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
I'll go with that plan What is it that makes flashing from sbf safer?
So if you perform a full factory reset the phone will boot up normally now? If that is the case then I don't see any problem with accepting the OTA to 4.4.2.
Help PLZ
I had the exact same problem as OP, took the same course of action, and got a successful boot. I do some minimal stuff, check if everything is working, turn on dev mode, etc. I put in my wifi password.
I wanted to check if my bootloader was back to stock, so I turned off my device, and then tried to power on. Pressing the power button does nothing.
So I get into fastboot, and select factory (reset) again. It boots up, but it doesn't seem like it actually did a factory reset, because it automatically connected to my wifi..
Have you any idea what's going on, and how perhaps to solve this weird dilemna?
EDIT: I'm not sure if I actually did anything, but after a couple reboots it just started working normally. I installed the update to 4.4.2 and everything is smooth thus far.
Eventually the phone prompted me to apply the 4.4.2 update so often the phone was actually unusable - it'd go back to the "do you want to update?" screen as soon as I backed out of it. I was thus forced to apply it OTA. Fortunately, the update went through fine this time, and my phone continues to work fine
Thanks for your help, folks!
Hi, I have a republic wireless moto x I just successfully rooted and updated to 4.4.2 from 4.2.2 with a locked bootloader with no write protection (wp)
Since I updated it to 4.4.2 I have this error that pops up that I can not resolve
"Unfortunately, the process com.motorola.process.system has stopped"
I googled several pages of several website results and several pages of google but can not find the solution.
Solutions found was to:
Safe Mode (I tried this first with no apps installed on non safemode and non system apps updated, didn't work and popped up even on safe mode)
Change date & time method (didn't work)
Wipe Cache (didn't work)
Wipe Cache & dalvik cache (didn't work)
I am debating about factory reset but unsure if it will make me lose my root because I have a locked bootloader (if that matters in anyway I am still new to this, and that my moto x is from republic wireless not like other carriers with unlocked bootloaders).
Please help me and discuss with me how I can get rid of that error.
androiddoglover6969 said:
Hi, I have a republic wireless moto x I just successfully rooted and updated to 4.4.2 from 4.2.2 with a locked bootloader with no write protection (wp)
Since I updated it to 4.4.2 I have this error that pops up that I can not resolve
"Unfortunately, the process com.motorola.process.system has stopped"
I googled several pages of several website results and several pages of google but can not find the solution.
Solutions found was to:
Safe Mode (I tried this first with no apps installed on non safemode and non system apps updated, didn't work and popped up even on safe mode)
Change date & time method (didn't work)
Wipe Cache (didn't work)
Wipe Cache & dalvik cache (didn't work)
I am debating about factory reset but unsure if it will make me lose my root because I have a locked bootloader (if that matters in anyway I am still new to this, and that my moto x is from republic wireless not like other carriers with unlocked bootloaders).
Please help me and discuss with me how I can get rid of that error.
Click to expand...
Click to collapse
You shouldn't have done it. You obviously didn't read or follow any of the guides here or you would have known better.
There was ONE (very tricky and convoluted) way of retaining root and it involves SafeStrap.
Sorry to say - there will likely be no root in your future.
A factory reset will most likely not help. You will have to download the 4.4.2 SBF and re-flash the entire stock rom.
There's a guide here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
^ This is the only way to get your phone back to being usable again. MAKE SURE you do NOT try to flash anything but 4.4.2. Flashing a prior version will likely permanently brick your phone.
After this process, the ONLY way you're going to obtain ROOT is to unlock your BL.
I hate to hear this happened to you, but its posted -all over- this forum that you cannot take the 4.4.2 OTA if you are rooted on a previous version. If you had followed the guide, and used Safestrap, you would be OK.....but now its too late. Once you've flashed the 4.4.2 OTA, it updates the bootloader, patching all of the exploits we used previously. Game Over.
Good Luck
samwathegreat said:
You shouldn't have done it. You obviously didn't read or follow any of the guides here or you would have known better.
There was ONE (very tricky and convoluted) way of retaining root and it involves SafeStrap.
Sorry to say - there will likely be no root in your future.
A factory reset will most likely not help. You will have to download the 4.4.2 SBF and re-flash the entire stock rom.
There's a guide here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
^ This is the only way to get your phone back to being usable again. MAKE SURE you do NOT try to flash anything but 4.4.2. Flashing a prior version will likely permanently brick your phone.
After this process, the ONLY way you're going to obtain ROOT is to unlock your BL.
I hate to hear this happened to you, but its posted -all over- this forum that you cannot take the 4.4.2 OTA if you are rooted on a previous version. If you had followed the guide, and used Safestrap, you would be OK.....but now its too late. Once you've flashed the 4.4.2 OTA, it updates the bootloader, patching all of the exploits we used previously. Game Over.
Good Luck
Click to expand...
Click to collapse
I did not have a root before 4.4.2. And I did not take the 4.4.2 OTA. I did follow the guide and have used Safestrap and still have it. What do you mean flash the 4.4.2 OTA? You mean installing it through the update notification? Well I didn't do that if that is what you meant. I flashed through the using the guide to get me no WP, root, and 4.4.2. So am I still doing it wrong?
androiddoglover6969 said:
I did not have a root before 4.4.2. And I did not take the 4.4.2 OTA. I did follow the guide and have used Safestrap and still have it. What do you mean flash the 4.4.2 OTA? You mean installing it through the update notification? Well I didn't do that if that is what you meant. I flashed through the using the guide to get me no WP, root, and 4.4.2. So am I still doing it wrong?
Click to expand...
Click to collapse
Sorry for the confusion...
Hmm...you didn't mention safestrap in OP - just that you "successfully rooted and updated to 4.4.2 from 4.2.2"
OK so if you followed the guide exactly your bootloader should still be on the JellyBean bootloader.
Assuming you followed the guide, you can start over. If you're ABSOLUTELY SURE you didn't update to the 4.4.2 bootloader, then I suggest starting from scratch.
Use RSD Lite to restore the 4.2.2 (JellyBean) rom (Again, you've been warned. If theres any possibility you flashed the 4.4.2 bootloader last time, this WILL brick your phone) Also, be careful to NOT flash the 4.4.2 ROM, or you will NOT be able to root as this patches the exploit.
Just follow the guide step-by-step: http://forum.xda-developers.com/moto-x/general/guide-republic-wireless-moto-x-kitkat-4-t2738233
The first step is to restore back the 4.2.2 stock rom, so this is where you should start. Don't forget to re-install safestrap and MotoWpNoMo as described.
Please let us know how it works out.
samwathegreat
samwathegreat said:
Sorry for the confusion...
Hmm...you didn't mention safestrap in OP - just that you "successfully rooted and updated to 4.4.2 from 4.2.2"
OK so if you followed the guide exactly your bootloader should still be on the JellyBean bootloader.
Assuming you followed the guide, you can start over. If you're ABSOLUTELY SURE you didn't update to the 4.4.2 bootloader, then I suggest starting from scratch.
Use RSD Lite to restore the 4.2.2 (JellyBean) rom (Again, you've been warned. If theres any possibility you flashed the 4.4.2 bootloader last time, this WILL brick your phone) Also, be careful to NOT flash the 4.4.2 ROM, or you will NOT be able to root as this patches the exploit.
Just follow the guide step-by-step: http://forum.xda-developers.com/moto-x/general/guide-republic-wireless-moto-x-kitkat-4-t2738233
The first step is to restore back the 4.2.2 stock rom, so this is where you should start. Don't forget to re-install safestrap and MotoWpNoMo as described.
Please let us know how it works out.
samwathegreat
Click to expand...
Click to collapse
Aslo, before I start to do the RSD Lite to restore the 4.2.2. Is there any other way how I can identify what is causing that error "com.motorola.process.system"? And isolate and get rid of that problem somehow or finding that stock app and preventing it from doing that?
androiddoglover6969 said:
Aslo, before I start to do the RSD Lite to restore the 4.2.2. Is there any other way how I can identify what is causing that error "com.motorola.process.system"? And isolate and get rid of that problem somehow or finding that stock app and preventing it from doing that?
Click to expand...
Click to collapse
Its extremely difficult to know why you are getting the error, but if you RSD Lite and start over, it will fix this issue.
Far too many people are running safestrap and not receiving the error. Likely there is a file on your device corrupted somewhere. RSD Lite will fix it as it completely restores the all of the partitions.
Just go -slow- step-by-step, and post here if you get confused or have questions. We will get your phone back to normal...
On another note....if you have $45 laying around, I highly suggest you email the gentleman from China. Once unlocked, you won't have to go through this long drawn-out process. You simply SBF back to stock, fastboot flash TWRP, and you're done. TWRP will install su-installer for you.
Your choice. The BL unlock method is best because you have permanent access and can never lose root.
Safestrap method will work as well, but you have to be very careful to not accept any new OTAs until the devs find a solution and post it here.
Good Luck.
samwathegreat said:
Its extremely difficult to know why you are getting the error, but if you RSD Lite and start over, it will fix this issue.
Far too many people are running safestrap and not receiving the error. Likely there is a file on your device corrupted somewhere. RSD Lite will fix it as it completely restores the all of the partitions.
Just go -slow- step-by-step, and post here if you get confused or have questions. We will get your phone back to normal...
On another note....if you have $45 laying around, I highly suggest you email the gentleman from China. Once unlocked, you won't have to go through this long drawn-out process. You simply SBF back to stock, fastboot flash TWRP, and you're done. TWRP will install su-installer for you.
Your choice. The BL unlock method is best because you have permanent access and can never lose root.
Safestrap method will work as well, but you have to be very careful to not accept any new OTAs until the devs find a solution and post it here.
Good Luck.
Click to expand...
Click to collapse
Woops I responded to another post but I am going to expect my bootloader code.
What is the first step from all of this that I should do?
1. SBF = what exactly? Hitting the factory reset button?
2. Fastboot Flash TWRP ? So after SBF. Fastboot Flash TWRP is done in AP Fastboot screen? Stock Recovery Screen? Or what screen exactly?
3. Did the guide I do didn't safestrap (twrp?) installed the su-installer for me as well right? Just wondering.
androiddoglover6969 said:
Woops I responded to another post but I am going to expect my bootloader code.
What is the first step from all of this that I should do?
1. SBF = what exactly? Hitting the factory reset button?
2. Fastboot Flash TWRP ? So after SBF. Fastboot Flash TWRP is done in AP Fastboot screen? Stock Recovery Screen? Or what screen exactly?
3. Did the guide I do didn't safestrap (twrp?) installed the su-installer for me as well right? Just wondering.
Click to expand...
Click to collapse
1.)
You can find the sbf files (stock rom) here: http://sbf.droid-developers.org/phone.php?device=0
Download the correct file for your carrier and try to flash with RSD lite.
You can find a great guide here: http://forum.xda-developers.com/moto...using-t2446515
PAY CLOSE ATTENTION TO STEP 4 - editing the xml file
If for some reason that doesn't work, let us know what carrier you are on and we can help you with manual flashing commands for your specific carrier.
Basically, an SBF is a complete STOCK image of the original filesystem (all partitions). By SBFing, you will be 100% back to factory stock. This method (SBFing) will actually fix a corrupted filesystem.
A "factory reset" does NOT do this. I highly suggest you do the SBF back to stock, and not try just reseting. If there is corruption, reset won't fix it.
Don't bother setting up any apps yet or setting up the phone. Wait until you complete the entire process.
2.
Yes! You'll flash TWRP from the "AP Fastboot" screen (bootloader).
UNLOCK YOUR BOOTLOADER FIRST. Otherwise you won't be able to flash TWRP custom recovery.
Now unplug the USB cord, and power off your device. Hold down the VOL DOWN button, and power back on. You will now be in bootloader (fastboot) mode. Plug the USB back into the phone now.
You must have "mfastboot" downloaded. You'll type:
mfastboot flash recovery twrp_file_you_downloaded.img (obviously replace with the actual filename)
You can find complete instructions here: http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
P.S. If the download link for TWRP in the original post does not work, look near the end of the thread. Someone else re-uploaded it.
3.
Its entirely possible that something went afoul during your flashing process. I doubt the guide is to blame, because nearly everyone reported success. Sometimes things just go wrong...?
Good Luck.
samwathegreat said:
1.)
You can find the sbf files (stock rom) here: http://sbf.droid-developers.org/phone.php?device=0
Download the correct file for your carrier and try to flash with RSD lite.
You can find a great guide here: http://forum.xda-developers.com/moto...using-t2446515
PAY CLOSE ATTENTION TO STEP 4 - editing the xml file
If for some reason that doesn't work, let us know what carrier you are on and we can help you with manual flashing commands for your specific carrier.
Basically, an SBF is a complete STOCK image of the original filesystem (all partitions). By SBFing, you will be 100% back to factory stock. This method (SBFing) will actually fix a corrupted filesystem.
A "factory reset" does NOT do this. I highly suggest you do the SBF back to stock, and not try just reseting. If there is corruption, reset won't fix it.
2.
Yes! You'll flash TWRP from the "AP Fastboot" screen (bootloader). You must have "mfastboot" downloaded. You'll type:
mfastboot flash recovery twrp_file_you_downloaded.img (obviously replace with the actual filename)
You can find complete instructions here: http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
P.S. If the download link for TWRP in the original post does not work, look near the end of the thread. Someone else re-uploaded it.
3.
Its entirely possible that something went afoul during your flashing process. I doubt the guide is to blame, because nearly everyone reported success. Sometimes things just go wrong...?
Good Luck.
Click to expand...
Click to collapse
On step 1. It is republic wireless 4.4.2 that I should download right. Correct me if I'm wrong.
Also is there RSDlite for mac or similar software? I tried to google it and xda'd it but I don't think there is. Or any other way to flash it into it.
androiddoglover6969 said:
On step 1. It is republic wireless 4.4.2 that I should download right. Correct me if I'm wrong.
Also is there RSDlite for mac or similar software? I tried to google it and xda'd it but I don't think there is. Or any other way to flash it into it.
Click to expand...
Click to collapse
If you have already received your code, yes, you should flash republic 4.4.2
If you haven't...just wait until you have it for sure. Once you flash 4.4.2 theres no going back. As long as you get unlock code, this is no problem....you'll be able to root regardless.
But, if for any reason he doesn't have your code (unlikely), you'll never be able to root once on 4.4.2....
As of right now (If I understand you completely), since you followed the safestrap guide, you SHOULD be on the jellybean bootloader, so the steps would be different if you didn't have an unlock code (and wanted to retain root).
Don't worry about any of this until we know for sure if you can get unlocked. In the unlikely event you don't get a code, post back here and I will step you through it.
Otherwise (if you get code), yes, start by using RSD Lite to flash the Republic Wireless 4.4.2 SFB per my previous instructions.
EDIT:
Just read the part about being on a MAC. AFAIK, there is no RSD Lite for Mac. We will have to go another route, unless you want to install windows inside a virtual machine....The dev that created the Mac Tooklit sold his X, and its no longer supported.
We will just do manual flashing...make sure you downloaded the "mfastboot" and followed all instructions on the RSD Lite thread I linked, EXCEPT follow the "Manual Flashing" instructions instead.
Extract the Republic Wireless SBF zip file Put the contents in to the same folder where fastboot and mfastboot are located. Here are the commands you will type after booting your X Into bootloader (Fastboot mode):
***Notice that mfastboot is used to flash the system.img. DONT try to use regular fastboot. Just type these commands one at a time.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier sprint ***be sure to type sprint. RW is a sprint MVNO, and I checked the xml file and this is the correct command for the Republic Wireless rom.
fastboot oem fb_mode_clear
Now reboot. Expect it to take a little longer than normal for the first boot-up. Congrats! You're now on 4.4.2 and your corruption issue will be a thing of the past.
Now Complete steps 2 & 3
samwathegreat said:
If you have already received your code, yes, you should flash republic 4.4.2
If you haven't...just wait until you have it for sure. Once you flash 4.4.2 theres no going back. As long as you get unlock code, this is no problem....you'll be able to root regardless.
But, if for any reason he doesn't have your code (unlikely), you'll never be able to root once on 4.4.2....
As of right now (If I understand you completely), since you followed the safestrap guide, you SHOULD be on the jellybean bootloader, so the steps would be different if you didn't have an unlock code (and wanted to retain root).
Don't worry about any of this until we know for sure if you can get unlocked. In the unlikely event you don't get a code, post back here and I will step you through it.
Otherwise (if you get code), yes, start by using RSD Lite to flash the Republic Wireless 4.4.2 SFB per my previous instructions.
EDIT:
Just read the part about being on a MAC. AFAIK, there is no RSD Lite for Mac. We will have to go another route, unless you want to install windows inside a virtual machine....The dev that created the Mac Tooklit sold his X, and its no longer supported.
We will just do manual flashing...make sure you downloaded the "mfastboot" and followed all instructions on the RSD Lite thread I linked, EXCEPT follow the "Manual Flashing" instructions instead.
Extract the Republic Wireless SBF zip file Put the contents in to the same folder where fastboot and mfastboot are located. Here are the commands you will type after booting your X Into bootloader (Fastboot mode):
***Notice that mfastboot is used to flash the system.img. DONT try to use regular fastboot. Just type these commands one at a time.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier sprint ***be sure to type sprint. RW is a sprint MVNO, and I checked the xml file and this is the correct command for the Republic Wireless rom.
fastboot oem fb_mode_clear
Now reboot. Expect it to take a little longer than normal for the first boot-up. Congrats! You're now on 4.4.2 and your corruption issue will be a thing of the past.
Now Complete steps 2 & 3
Click to expand...
Click to collapse
So what you showed me on manual way was if I was to install virtual windows right? Also that link showed it was 4.4 not 4.4.2... so am I still good or I shouldn't do that method? Thanks again for your effort.
androiddoglover6969 said:
So what you showed me on manual way was if I was to install virtual windows right? Also that link showed it was 4.4 not 4.4.2... so am I still good or I shouldn't do that method? Thanks again for your effort.
Click to expand...
Click to collapse
No. What I showed you was the manual fastboot method. This will run on Mac natively. You'll have to download the android SDK for mac, and install, then download the mfastboot binary (either 32 or 64 bit) here: https://gist.github.com/crazed/7670423 *** after you download the file (moto-fastboot-osx64), RENAME it to mfastboot.
Although the link on how to SBF back to stock shows android 4.4, it doesn't matter. The SBF process is the same no matter which version you are on. You just need to download the right carrier/version from here http://sbf.droid-developers.org/phone.php?device=0
Not to confuse you but if you were to install virtual windows, you could probably use the rsd lite method.
Do one but not both. The native (manual) version should be simpler for you. I had assumed you already had the necessary android SDK since you said you went through the whole safestrap process and everything. Were you on a different computer when you did that?
Have you received your code yet? Hold off on SBFing until you have it in hand.
samwathegreat said:
No. What I showed you was the manual fastboot method. This will run on Mac natively. You'll have to download the android SDK for mac, and install, then download the mfastboot binary (either 32 or 64 bit) here: https://gist.github.com/crazed/7670423 *** after you download the file (moto-fastboot-osx64), RENAME it to mfastboot.
Although the link on how to SBF back to stock shows android 4.4, it doesn't matter. The SBF process is the same no matter which version you are on. You just need to download the right carrier/version from here http://sbf.droid-developers.org/phone.php?device=0
Not to confuse you but if you were to install virtual windows, you could probably use the rsd lite method.
Do one but not both. The native (manual) version should be simpler for you. I had assumed you already had the necessary android SDK since you said you went through the whole safestrap process and everything. Were you on a different computer when you did that?
Have you received your code yet? Hold off on SBFing until you have it in hand.
Click to expand...
Click to collapse
Havn't got the code yet. And I did the motowpnomo on windows 8. Everything else did on mac.
Just got my code at 23hrs.
I just wanted to do add onto the process and make minor adjustments to make it clear.
Did Step 1.
and then at the end
He will say reboot, but don't go waiting to install your apps or update it or setting it up. Just start it up normal power up. Then when it says select language (not sure if needs debugging or not but I did) go to developer options by clicking on settings. go all the way down to "about phone" tap on "build number" a couple times you will see developer options pop up. Go back and go down to developer options and go find usb debugging. Then hit accept on phone pop up when usb debugging is enabled so your phone trust your computer. then do ./adb reboot bootloader
It should get you into ap fastboot mode then do my step 2.
Step 2 - Unlock bootloader before doing mfastboot-ing the twrp so you don't get the
invalid image size on your phone
or
writing 'recovery'... INFOPreflash validation failed
FAILED (remote failure) on your terminal
So by doing this to unlock bootloader
fastboot getvar all
then
fastboot oem unlock CODEHERE
Should give you a "unlock" blue text with black screen.
Then the step 2 mentioned by samwathegreat for TWRP which will download the file without the invalidity error message on both computer or moto x on ap fastboot screen.
Then step 3. I used the Down arrow to select "recovery" which gave me the TWRP screen.
Step 4. I went into the TWRP screen and hit reboot and a pop up for SuperSU popped up notifying me to install SuperSU. Swipe next and it'll install and then voila!
Step 5. Click on SuperSu app and it should reboot and try to install.
Step 6. Hit the thanks button to samwathegreat
androiddoglover6969 said:
Havn't got the code yet. And I did the motowpnomo on windows 8. Everything else did on mac.
Just got my code at 23hrs.
I just wanted to do add onto the process and make minor adjustments to make it clear.
Did Step 1.
and then at the end
He will say reboot, but don't go waiting to install your apps or update it or setting it up. Just start it up normal power up. Then when it says select language (not sure if needs debugging or not but I did) go to developer options by clicking on settings. go all the way down to "about phone" tap on "build number" a couple times you will see developer options pop up. Go back and go down to developer options and go find usb debugging. Then hit accept on phone pop up when usb debugging is enabled so your phone trust your computer. then do ./adb reboot bootloader
It should get you into ap fastboot mode then do my step 2.
Step 2 - Unlock bootloader before doing mfastboot-ing the twrp so you don't get the
invalid image size on your phone
or
writing 'recovery'... INFOPreflash validation failed
FAILED (remote failure) on your terminal
So by doing this to unlock bootloader
fastboot getvar all
then
fastboot oem unlock CODEHERE
Should give you a "unlock" blue text with black screen.
Then the step 2 mentioned by samwathegreat for TWRP which will download the file without the invalidity error message on both computer or moto x on ap fastboot screen.
Then step 3. I used the Down arrow to select "recovery" which gave me the TWRP screen.
Step 4. I went into the TWRP screen and hit reboot and a pop up for SuperSU popped up notifying me to install SuperSU. Swipe next and it'll install and then voila!
Step 5. Click on SuperSu app and it should reboot and try to install.
Step 6. Hit the thanks button to samwathegreat
Click to expand...
Click to collapse
Excellent! Thanks for pointing that the instructions didn't specify that you must unlock your BL before flashing TWRP. Edited Post # 8 to include the step. You can also unlock BL before you start any of the steps, but must do it before flashing custom recovery as you have pointed out.
I did suggest a slightly different method, however, that doesn't require enabling developer options or usb debugging. If you unplug the phone and power it off, you can get straight into fastboot mode without 'adb reboot bootloader'. You just hold down VOL DOWN, and power it on. Then you plug the USB cord back in. It only works if you unplug the phone first....for some reason if you leave it plugged in, you can't power off the phone...it just immediately reboots.
So, to wrap this all up, just a couple more questions:
Did you complete the entire process on your Mac? And can you confirm that the error you were originally receiving (in Original Post) is no longer popping up?
And finally, check out xposed framework installer and "gravity box" mod. You can do some really cool mods with gravity box. I suggest you boot into TWRP and make a nandroid backup -just in case- before you go playing around with xposed.
Have fun.
samwathegreat said:
Excellent! Thanks for pointing that the instructions didn't specify that you must unlock your BL before flashing TWRP. Edited Post # 8 to include the step. You can also unlock BL before you start any of the steps, but must do it before flashing custom recovery as you have pointed out.
I did suggest a slightly different method, however, that doesn't require enabling developer options or usb debugging. If you unplug the phone and power it off, you can get straight into fastboot mode without 'adb reboot bootloader'. You just hold down VOL DOWN, and power it on. Then you plug the USB cord back in. It only works if you unplug the phone first....for some reason if you leave it plugged in, you can't power off the phone...it just immediately reboots.
So, to wrap this all up, just a couple more questions:
Did you complete the entire process on your Mac? And can you confirm that the error you were originally receiving (in Original Post) is no longer popping up?
And finally, check out xposed framework installer and "gravity box" mod. You can do some really cool mods with gravity box. I suggest you boot into TWRP and make a nandroid backup -just in case- before you go playing around with xposed.
Have fun.
Click to expand...
Click to collapse
Yes I complete the whole process on the Mac. Yes the original error is no longer popping up. What is a nandroid back up? I did a back up after I installed all my apps and updated it and dragged that copy to my desktop and uploaded it to my cloud.
I hear about xposed framework and gravity box but I have no clue what it looks like and also forgot what nandroid is but I'll look it up.
And yes android reboots can't stay on shut down when cord is connected. Which is funny.
androiddoglover6969 said:
Yes I complete the whole process on the Mac. Yes the original error is no longer popping up. What is a nandroid back up? I did a back up after I installed all my apps and updated it and dragged that copy to my desktop and uploaded it to my cloud.
I hear about xposed framework and gravity box but I have no clue what it looks like and also forgot what nandroid is but I'll look it up.
And yes android reboots can't stay on shut down when cord is connected. Which is funny.
Click to expand...
Click to collapse
If you backed up from within custom recovery (TWRP), thats the same thing. Some recoveries call them ''backup', some 'nandroid'....same thing.
Thanks for the final follow-up. Take care...
samwathegreat said:
If you backed up from within custom recovery (TWRP), thats the same thing. Some recoveries call them ''backup', some 'nandroid'....same thing.
Thanks for the final follow-up. Take care...
Click to expand...
Click to collapse
Also I installed everything I needed to from gravitybox and well framework xposed too. Which is very similar to jailbreak tweaks on the iPhone.
Thanks again.
Hi all,
Is there any difference, if I'm with Art or Dalvik for receiving the update?
I don't receive the update yet, still in 4.4.2 and I use Art,
I'm questioning if with Dalvik can get earlier?
Br
Sent from my XT1052 using XDA Free mobile app
If your device is getting the update, it doesn't matter which runtime, ART or Dalvik, you are running. You'll get it when you get it.
Sent from my XT1060 using XDA Premium 4 mobile app
sylarm said:
Hi all,
Is there any difference, if I'm with Art or Dalvik for receiving the update?
I don't receive the update yet, still in 4.4.2 and I use Art,
I'm questioning if with Dalvik can get earlier?
Br
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
I noticed you're using 1052. I'm not 100% but I thought the current soak test was only for XT1060
sylarm said:
Hi all,
Is there any difference, if I'm with Art or Dalvik for receiving the update?
I don't receive the update yet, still in 4.4.2 and I use Art,
I'm questioning if with Dalvik can get earlier?
Br
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
As already advised, it doesn't matter. But please be sure to post in the correct sub-forum next time. Questions belong in Q&A, NOT General. See the 2nd stick post at the top of the General Sub-forum...
sylarm said:
Hi all,
Is there any difference, if I'm with Art or Dalvik for receiving the update?
I don't receive the update yet, still in 4.4.2 and I use Art,
I'm questioning if with Dalvik can get earlier?
Br
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
Me to Still waiting for OTA for my XT1052(Rooted).... I could not find the OTA Capture zip
treyf711 said:
I noticed you're using 1052. I'm not 100% but I thought the current soak test was only for XT1060
Click to expand...
Click to collapse
Moto X (XT 1052) phones in India have already started receiving the 4.4.4 update
Here in Portugal nothing, and this update I is missing here, to fix the S. O. Battery drain.
At least I hope so...
Sent from my XT1052 using XDA Free mobile app
yekollu said:
Moto X (XT 1052) phones in India have already started receiving the 4.4.4 update
Click to expand...
Click to collapse
Have you seen anyone having the 4.4.4 on an Indian X? Moto announced about the update kinda quickly.
devilsdouble said:
Have you seen anyone having the 4.4.4 on an Indian X? Moto announced about the update kinda quickly.
Click to expand...
Click to collapse
Yep!!! Not much of a cosmetic difference though. Phone appliccation looks a little different, there is the new alert app and also the Google+ app (with accompanying Photos)
Not much difference compared to 4.4.2 I hope it gives better battery life. light user interface of dialer, camera tweaks, added pause button in video recording.
Sent from my XT1052 using XDA Free mobile app
Update 4.4.4 Xt1052
Today morning, when i woked up and checked my phone, there was a update notification of 4.4.4. I was pretty much exicted looking that and i start the update process.
Now when the download was completed i clicked on Install the update, phone automatically powered off and rebooted into the TWRP and does nothing with that update. I selected that zip update file from cache folder and failed to install from TWRP as well. Then i rebooted the phone and after some time like 1 minute phone again rebooted into TWRP this time i removed CACHE so that next time the phone will not reboot and it works fine but i can't install the update
Please tell me how should i update now from 4.4.2 to 4.4.4, , if you did on your rooted moto x. I only unlocked bootloader and din't change the rom. Rom is still the same which i got at the time of purchase
vijayid_94 said:
Today morning, when i woked up and checked my phone, there was a update notification of 4.4.4. I was pretty much exicted looking that and i start the update process.
Now when the download was completed i clicked on Install the update, phone automatically powered off and rebooted into the TWRP and does nothing with that update. I selected that zip update file from cache folder and failed to install from TWRP as well. Then i rebooted the phone and after some time like 1 minute phone again rebooted into TWRP this time i removed CACHE so that next time the phone will not reboot and it works fine but i can't install the update
Please tell me how should i update now from 4.4.2 to 4.4.4, , if you did on your rooted moto x. I only unlocked bootloader and din't change the rom. Rom is still the same which i got at the time of purchase
Click to expand...
Click to collapse
........flash back 4.4.2 stock recovery.....
samwathegreat said:
........flash back 4.4.2 stock recovery.....
Click to expand...
Click to collapse
Bro i had mentioned that i din't changed the rom, its already the stock one which i got with it. I had just unlocked the bootloader.
Do i still need to go to Stock
vijayid_94 said:
Bro i had mentioned that i din't changed the rom, its already the stock one which i got with it. I had just unlocked the bootloader.
Do i still need to go to Stock
Click to expand...
Click to collapse
Stock ----recovery----. You specifically said it rebooted into TWRP - which means you HAD to have flashed custom recovery. So flash stock recovery back on - from the 4.4.2 sbf of your carrier:
fastboot flash recovery recovery.img
and assuming you haven't made any significant modifications to /system, the OTA will install without issue. You data will be intact.
Recovery does not = ROM. Two different things.
Correct! Stock recovery must be present or the OTA update will fail.
If you have Xposed with any module you must remove them too.
Flashed stock recovery and still unsuccessful with 4.4.4 OTA upgrade
This is for Verizon Developer's Moto X with an unlocked bootloader.
I forgot that I loaded TWRP on my wife's phone so I tried to take the update and it failed. I also had the modified vzwentitlement.apk loaded so that she could use native tethering. So here's what I did:
- Deleted the modified vzwentitlement.apk
- Removed the ".bak" from the original vzwentitlementservice.apk.bak and the vzwentitlementservice.odex.bak files
- Unrooted the phone using SuperSU's Permanent Unroot option in settings (not sure that was required but didn't want to take any chances
- Downloaded and unzipped the Moto X 4.4.2 from the Motorola firmware site
- Copied the unzipped recovery.img to the Minimal ADB and Fastboot directory
- Flashed the stock recovery back to the phone
I did all that and the phone went into recovery with the little green Droid guy with the hatch open. The blue progress line got about halfway done when the phone rebooted and said it was unsuccessful.
Any ideas what I'm missing? I'd hate to have to flash back to 4.4.2 and lose all her settings, but I will if no one has any better suggestions.
benjamin1492 said:
This is for Verizon Developer's Moto X with an unlocked bootloader.
I forgot that I loaded TWRP on my wife's phone so I tried to take the update and it failed. I also had the modified vzwentitlement.apk loaded so that she could use native tethering. So here's what I did:
- Deleted the modified vzwentitlement.apk
- Removed the ".bak" from the original vzwentitlementservice.apk.bak and the vzwentitlementservice.odex.bak files
- Unrooted the phone using SuperSU's Permanent Unroot option in settings (not sure that was required but didn't want to take any chances
- Downloaded and unzipped the Moto X 4.4.2 from the Motorola firmware site
- Copied the unzipped recovery.img to the Minimal ADB and Fastboot directory
- Flashed the stock recovery back to the phone
I did all that and the phone went into recovery with the little green Droid guy with the hatch open. The blue progress line got about halfway done when the phone rebooted and said it was unsuccessful.
Any ideas what I'm missing? I'd hate to have to flash back to 4.4.2 and lose all her settings, but I will if no one has any better suggestions.
Click to expand...
Click to collapse
Use the FXZ instead. It is a "keep data" FXZ which means that all here data and apps will be intact. It will require re-flashing TWRP, and re-rooting afterwards. You will also need to re-do the entitlement hack. It's very easy. You can use RSD Lite, and you should be back up and running with everything intact in less than 15 minutes from start.
The FXZ method does not use a manifest since it replaces your partitions completely - except for /data (where all your apps and settings are stored).
http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
Hey guys.
I had download stock recovery for my Moto X.
The zip contain many files as seen into the image below.
Please someone tell me the procedure of flashing them into my phone. I don't know actually how to go now. Do i need to wipe all the data from the phone or just have to wipe system only.
Is the below commands are enough or i have to do some other things as well.
adb reboot bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
Sent from my XT1052 using XDA Free mobile app
samwathegreat said:
Use the FXZ instead. It is a "keep data" FXZ which means that all here data and apps will be intact. It will require re-flashing TWRP, and re-rooting afterwards. You will also need to re-do the entitlement hack. It's very easy. You can use RSD Lite, and you should be back up and running with everything intact in less than 15 minutes from start.
The FXZ method does not use a manifest since it replaces your partitions completely - except for /data (where all your apps and settings are stored).
http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
Click to expand...
Click to collapse
That did the trick, or at least a variation of it did the trick. The post said that the new 4.4.4 FXZ actually DID wipe date, so I followed the RSD Flasher instructions but kept data with a fresh 4.4.2 flash instead. Then I downloaded the 4.4.4 OTA. This time it took. I have re-rooted and got my tether hack back in place. Thanks for all your help.
vijayid_94 said:
Hey guys.
I had download stock recovery for my Moto X.
The zip contain many files as seen into the image below.
Please someone tell me the procedure of flashing them into my phone. I don't know actually how to go now. Do i need to wipe all the data from the phone or just have to wipe system only.
Is the below commands are enough or i have to do some other things as well.
adb reboot bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
Fastboot flash recovery recovery.IMG
Should be sufficient. If you still can't take the ota, then also do:
mfastboot flash system system.img
Now you should be able to accept the ota without losing data. You will need to flash TWRP back and re-root.
If anything goes wrong, you will run all the commands you listed but that WILL erase all of your data.
Good luck :good:
Hi all, I'm at a loss here as I've tried everything I could think of. I've completely reflashed everything using fastboot to the stock 4.4.2 image, wiped userdata and cache and when I go to install the system update I get an error and it's unsuccessful. What am I missing or doing wrong? Thx
hlaalu said:
Hi all, I'm at a loss here as I've tried everything I could think of. I've completely reflashed everything using fastboot to the stock 4.4.2 image, wiped userdata and cache and when I go to install the system update I get an error and it's unsuccessful. What am I missing or doing wrong? Thx
Click to expand...
Click to collapse
Just use the FXZ instead....
http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
@hlaalu : EDIT - WAIT. I assumed you were on the Verizon DEV editon.
On the GSM Unlocked Dev edition??? Don't flash that FXZ!
What device are you on???
samwathegreat said:
Just use the FXZ instead....
http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
@hlaalu : EDIT - WAIT. I assumed you were on the Verizon DEV editon.
On the GSM Unlocked Dev edition??? Don't flash that FXZ!
What device are you on???
Click to expand...
Click to collapse
I AM on Verizon, thanks for checking. I have no idea what the FXZ is but I'm a little concerned with the big red warning.
hlaalu said:
I AM on Verizon, thanks for checking. I have no idea what the FXZ is but I'm a little concerned with the big red warning.
Click to expand...
Click to collapse
HAHA! Just between you and me -- EVERY FLASHABLE FILE on XDA should have that warning. The problem is that people fail to read or follow instructions. They will flash wrong carrier's roms, attempt to downgrade, etc. Either of which can end up bricking your device - in a heartbeat.
Anyways that FXZ is the FULL factory image -- straight from Motorola, signed with release keys. There's nothing safer. Flashing the FXZ is much safer even than taking the OTA, because it actually replaces (and hence can repair a corrupted/damaged filesystem) all partitions instead of just doing an incremental update (like an OTA).
This particular FXZ is a "keep data" FXZ, meaning it will do the same thing as the OTA - only difference is you will need to re-root afterwards. All your data will still be intact. If you are using Xposed, you will also need to re-install it, but any modules you had installed will keep their respective settings.
Good Luck. That is EXACTLY what you need...
samwathegreat said:
HAHA! Just between you and me -- EVERY FLASHABLE FILE on XDA should have that warning. The problem is that people fail to read or follow instructions. They will flash wrong carrier's roms, attempt to downgrade, etc. Either of which can end up bricking your device - in a heartbeat.
Anyways that FXZ is the FULL factory image -- straight from Motorola, signed with release keys. There's nothing safer. Flashing the FXZ is much safer even than taking the OTA, because it actually replaces (and hence can repair a corrupted/damaged filesystem) all partitions instead of just doing an incremental update (like an OTA).
This particular FXZ is a "keep data" FXZ, meaning it will do the same thing as the OTA - only difference is you will need to re-root afterwards. All your data will still be intact. If you are using Xposed, you will also need to re-install it, but any modules you had installed will keep their respective settings.
Good Luck. That is EXACTLY what you need...
Click to expand...
Click to collapse
Thanks I'll give that a shot. Too bad I didn't see this earlier, all my data has been wiped...repeatedly lol. Custom recovery will still be flashed using fastboot after FXZ?
hlaalu said:
Thanks I'll give that a shot. Too bad I didn't see this earlier, all my data has been wiped...repeatedly lol. Custom recovery will still be flashed using fastboot after FXZ?
Click to expand...
Click to collapse
Precisely. After successfully booted to android (and you verify all is well), go back to bootloader, and:
fastboot flash twrpfilename.img
(get the latest version here: http://techerrata.com/browse/twrp2/ghost )
Then immediately after flashing it, type:
fastboot reboot-bootloader
then VOL DOWN to Recovery, and VOL UP to enter it. Once in, click exit. It will offer to root for you.....
(you MUST enter into TWRP immediately after flashing it [before booting into android again] -- if you don't it won't "stick" and will revert to stock recovery. As long as you immediately boot into TWRP after flashing it, it will "stick" forever....or until you flash something else to recovery. It is unknown why this happens, but the solution is easy enough....)
Up and running again, thanks a bunch for all the help!
Below are the instructions for using MoFo to flash the AT&T XT1097 to 5.1. The rooted image has a modified build.prop file for free tether. Thanks go to @Slack3r for making the ext4 image and @btdownloads7 for developing the root method.
Since this is a 5.1 image, in order to get it to boot, you need to do the following BEFORE flashing the 5.1 system image:
1) Download the stock 5.1 files and extract them:
https://mega.co.nz/#!bN0BjKbI!zzq5b9wZBo-XFGNkcWtgw7mnXZgC5BWrEC-GZcGLELo
2) Using a root file explorer (like ES Explorer with root enabled), delete everything in /data/dalvik-cache and /cache - YOU MUST DO THIS!
3) Reboot into bootloader mode and run the commands below to flash the following stock 5.1 files for the XT1097:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash recovery recovery.img
Do NOT flash the 5.1 bootloader (motoboot.img) or partition table (gpt.bin) - if you do, you will not be able to use MoFo ever again!!!!!
4) Download the rooted 5.1 image from here, extract it and flash it using MoFo.
https://mega.co.nz/#!ct8DlQxQ!DRMC_TvCcUk7V-FjCBfjsmIoOvw_f0WEdM7gx2waqzM
MD5 of the unzipped file = 146B6A65D925B985857A2F28D4294765
Note that with the XT1096 we had issues if we tried to boot into recovery after initially flashing the 5.1 system image so instead of booting into recovery and wiping cache where you might get weird flashing dead androids, we had to boot into system first.
Obviously if you want Xposed or anything else in the image, someone will need to add it in.
Thank you!
Those of us already rooted with mofo on 5.0.2 need to return to stock 5.0.2 first, correct?
Casyis said:
Thank you!
Those of us already rooted with mofo on 5.0.2 need to return to stock 5.0.2 first, correct?
Click to expand...
Click to collapse
No, the instructions as written in the OP are complete. Like the instructions say, you need to do step 2:
2) Using a root file explorer (like ES Explorer with root enabled), delete everything in /data/dalvik-cache and /data/cache - YOU MUST DO THIS!
Then you can flash the rest of the 5.1 stock files for your device EXCEPT for the bootloader (motoboot.img) and partition table (gpt.bin). Then use MoFo to flash the rooted 5.1 image for your device.
Thanks for clarifying.
I followed the instructions precisely, and the phone won't power up normally. It goes into recovery, and the android icon with exclamation just flashes intermittently. I'm unable to enter options to wipe cache. I can boot into recovery by holding volume down, but normal startup presents this behavior.
Any ideas?
EDIT: I chose BP Tools in boot options, and now the phone at least appears to be booting normally -- currently optimizing apps.
EDIT 2: Okay, so selecting BP tools evidently kicked the phone into booting normally. Looks like everything is just as it should be. Not sure what happened here, but in the end everything is good. Thank you (everyone involved) for getting this done for us!
Casyis said:
Thanks for clarifying.
I followed the instructions precisely, and the phone won't power up normally. It goes into recovery, and the android icon with exclamation just flashes intermittently. I'm unable to enter options to wipe cache. I can boot into recovery by holding volume down, but normal startup presents this behavior.
Any ideas?
EDIT: I chose BP Tools in boot options, and now the phone at least appears to be booting normally -- currently optimizing apps.
EDIT 2: Okay, so selecting BP tools evidently kicked the phone into booting normally. Looks like everything is just as it should be. Not sure what happened here, but in the end everything is good. Thank you (everyone involved) for getting this done for us!
Click to expand...
Click to collapse
This was happening with the XT1096 - you have to get it into system before recovery. You likely hit the wrong button and ended up in recovery instead of system. But once you get it into system, then it is fine.
Thanks again @JulesJam I am downloading now! Do you notice a big performance difference in 5.1? Will be nice to finally kill these memory bugs, so major thanks for that!
The OS is much snappier than 5.0.2. You can tell by going into multitasking and seeing how quickly the tiles load. Very, very nice. No re-draws at all yet since I flashed.
Step 2 implies that I'm already rooted. If I'm not, I assume I need to start with Step 0: Root the device with a 5.0 IMG?
What all would I need to fastboot flash from the stock files to return to stock @JulesJam ? My company just started using AirWatch service to get company email. Problem is airwatch will not work with root. Unfortunatly I will have to lose the ability to use MoFo.. Any help with this is greatly appreciated. Thanks!
bamachevrolet said:
What all would I need to fastboot flash from the stock files to return to stock @JulesJam ? My company just started using AirWatch service to get company email. Problem is airwatch will not work with root. Unfortunatly I will have to lose the ability to use MoFo.. Any help with this is greatly appreciated. Thanks!
Click to expand...
Click to collapse
FYI - like it says in the MoFo Noob Guide - MoFo trips the root checker and it is not able to be undone by flashing back to stock. I don't know how AirWatch works, but if it looks at the qe, then it will see you as rooted even if you aren't.
First thing I would do is flash back to 5.0.2 by flashing the stock 5.0.2 firware (link is in the MoFo Noob Guide)
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1 (repeat this for all of the sparsechunks)
then boot into recovery and wipe the cache. Then boot into system. I believe it will need to downgrade the sensor firmware so allow that to happen.
Then boot into bootloader mode and see if your software status still says modified or not. Then boot into recovery and see what your qe status is. If after that your software status is still modified and your qe is still 1/1, I would do a factory reset and see if that corrects it. It probably won't though.
You will then have to decide whether or not you want to take the 5.1 OTA because your phone is going to want to upgrade. Instead of taking the 5.1 OTA which will upgrade your bootloader and partition table, you have the option of flashing stock 5.1 everything but the motoboot.img and gpt.bin. That would keep you stock 5.1 but still keep your bootloader and partition table on 5.0.2 so that if you wanted to sell the phone later, you could sell it with a copy of MoFo that still works. I put this out there because idk how AirWatch works and if flashing back to stock doesn't change your software status from modified or your qe from 1/1, you may not be able to use AirWatch, idk.
Thank you so much for the detailed explanation @JulesJam . Unfortunately I followed the instructions to the T and didn't run into any issues until I tried to boot into recovery. I got the dead android with a line under saying "no command". So I tried running system first. I got through the boot animation and then a black screen. I let the black screen sit for 30 min and nothing happened. I had the exact issue when installing 5.1, I was able to get it to boot using BT tools. Unfortunately this is not working now. I get the same black screen after the boot animation. I tried multiple times with no luck. I can however still get into fastboot without issues
Any ideas how I can get 5.0.2 to boot? Thanks again!
bamachevrolet said:
I get the same black screen after the boot animation. I tried multiple times with no luck. I can however still get into fastboot without issues
Any ideas how I can get 5.0.2 to boot? Thanks again!
Click to expand...
Click to collapse
For sure you flashed the 5.0.2 logo.bin, boot.img and all of the 5.0.2 system sparsechunks? That sounds like the system partition was not flashed properly.
Perhaps the 5.0.2 system files you have are corrupted? Are you sure the files you have are the stock 5.0.2 files for the AT&T XT1097?
bamachevrolet said:
I got the dead android with a line under saying "no command". !
Click to expand...
Click to collapse
That's OK as long as he is not flashing. When you have the dead android, go ahead and press and hold power then tap volume up to get into recovery and wipe the cache.
Thank you! I was able to get into recovery to wipe cache, but still won't boot.
I downloaded 5.0.2 from your noob guide, and flashed everything in the order of your first replied post. I am going to start over, just in case I missed something.
Don't think it matters but the sparsechunk starts at 0 in the AT&T file. I flashed the sparschunks in order, and in my case 0-8.
bamachevrolet said:
Thank you! I was able to get into recovery to wipe cache, but still won't boot.
Click to expand...
Click to collapse
How long do you let the blank screen sit before you try to get into bootloader mode? I remember sometimes it takes awhile for it to boot.
Also, the dalvik-cache may need to be wiped too. That would require a factory reset to do it so you could boot into recovery and do a factory reset. Unless there is some way to wipe the dalvik-cache from bootloader mode.
bamachevrolet said:
Don't think it matters but the sparsechunk starts at 0 in the AT&T file. I flashed the sparschunks in order, and in my case 0-8.
Click to expand...
Click to collapse
That's fine. I wasn't sure what number they started with.
bamachevrolet said:
I downloaded 5.0.2 from your noob guide, and flashed everything in the order of your first replied post. I am going to start over, just in case I missed something.
Click to expand...
Click to collapse
And after you do, let it sit at the blank screen for awhile to make sure that it isn't an issue of needing time to boot up. If it still won't boot, try the factory reset.
Thank you so much @JulesJam !!! I'm booted to stock 5.0.2 now. I did have to do a factory reset, but not too big of a deal. Unfortunately I forgot to backup my 48 tasker profiles...lol. So glad to have it back up. Thank you again!!!
---------- Post added at 11:06 AM ---------- Previous post was at 11:01 AM ----------
[/COLOR @JulesJam do you have a donation link?
bamachevrolet said:
Thank you so much @JulesJam !!! I'm booted to stock 5.0.2 now. I did have to do a factory reset, but not too big of a deal. Unfortunately I forgot to backup my 48 tasker profiles...lol. So glad to have it back up. Thank you again!!![
Click to expand...
Click to collapse
Glad it worked out, sucks about the tasker profiles though. So it seems like the dalvik-cache has to be wiped, too. I will note that in the future people should delete the contents of the dalvik-cache folder before flashing back to the earlier version of the software.
Does your software status still say modified in bootloader mode? What is your qe when you boot into recovery?
bamachevrolet said:
@JulesJam do you have a donation link?
Click to expand...
Click to collapse
No but thanks for the offer. If you want to donate, please donate to the ASPCA.