Related
Hey all,
Strange happenings, I was only stock ROM rooted and decrypted boot image. Attempted update to 5.0.1 using factory image and flashed a boot image that somebody else created for the 5.0.1 to keep it decrypted. Factory reset and all that now device showing 23.03GB free on the 64GB version of the device. I have flashed back to stock using factory images numerous times. Attempted fastboot format cache and userdata as well and then flashed factory images to no avail. I remember at one point (I forget when) that there was a userdata_64G in the factory images that needed to be flashed on this device to get it showing 64GB, but that is not part of either factory image downloaded from Google. Please help I am not sure where to go next.
Boot into recovery, perform an FDR. This has always fixed this issue for me on my N4 and N5.
I've just made an FDR my final step after I flash a factory image...helps avoid this problem all together.
vbman213 said:
Boot into recovery, perform an FDR. This has always fixed this issue for me on my N4 and N5.
I've just made an FDR my final step after I flash a factory image...helps avoid this problem all together.
Click to expand...
Click to collapse
FDR is that factory reset? Or something else?
Yeah factory data reset. Issue with the user data file causes this issue only fix is to factory data reset.
Jnewell05 said:
Yeah factory data reset. Issue with the user data file causes this issue only fix is to factory data reset.
Click to expand...
Click to collapse
Is there a special way of doing this that will do it or just the normal way?
I just noticed my 64gb is the same, but I don't feel like wiping again just yet
Can't good get their factory images working correctly? Frigging flash all broken. And borked storage spaces from factory images.
U can try to adb erase userdata but I'm sure this erases your device. Safe bet is factory data reset through stock recovery
Jnewell05 said:
U can try to adb erase userdata but I'm sure this erases your device. Safe bet is factory data reset through stock recovery
Click to expand...
Click to collapse
this. recovery-->factory data reset fixes it no problem. short term pain, long term solution
I have just completed the decryption process on my Nexus 6 64gb, and now it shows up as a 32gb device... No matter how many times I do a Factory Data Reset on it, it never changes or fixes itself back to the proper space of 64gb. Any help is greatly appreciated.
This is what finally worked for me:
http://forum.xda-developers.com/showpost.php?p=58201783&postcount=106
Reboot into the bootloader and type this:
fastboot format userdata
fastboot format cache
fastboot reboot
That will obviously wipe all your data again, but it should return back to 64GB
linebacker71 said:
I have just completed the decryption process on my Nexus 6 64gb, and now it shows up as a 32gb device... No matter how many times I do a Factory Data Reset on it, it never changes or fixes itself back to the proper space of 64gb. Any help is greatly appreciated.
This is what finally worked for me:
http://forum.xda-developers.com/showpost.php?p=58201783&postcount=106
Reboot into the bootloader and type this:
fastboot format userdata
fastboot format cache
fastboot reboot
That will obviously wipe all your data again, but it should return back to 64GB
Click to expand...
Click to collapse
Yes, you need to format Data....thats the only way.
If I have a 32gb nexus and it only shows 23 GB is the same thing wrong? Or is it just like a hit or miss on the exact GB?
linebacker71 said:
I have just completed the decryption process on my Nexus 6 64gb, and now it shows up as a 32gb device... No matter how many times I do a Factory Data Reset on it, it never changes or fixes itself back to the proper space of 64gb. Any help is greatly appreciated.
This is what finally worked for me:
http://forum.xda-developers.com/showpost.php?p=58201783&postcount=106
Reboot into the bootloader and type this:
fastboot format userdata
fastboot format cache
fastboot reboot
That will obviously wipe all your data again, but it should return back to 64GB
Click to expand...
Click to collapse
Seconding this, found these instructions when I had this issue on my 64gb and they worked for me.
Yes! Thank you! This worked perfectly didn't have to root(again) thanks again!
Ironjim4102 said:
Yes! Thank you! This worked perfectly didn't have to root(again) thanks again!
Click to expand...
Click to collapse
Just a boot into recovery and factory reset done the job for me and wiped catch.
To avoid ever having this issue, do NOT flash the userdata.img file contained in the factory image. It is not meant for a 64GB device. And it is never needed anyway. If you want to start with a clean slate, always replace "fastboot flash userdata userdata.img" with "fastboot format userdata", and you will avoid the issue altogether.
Glad I found this - thought my 64GB N6 was "fake" or something for a minute!
efrant said:
To avoid ever having this issue, do NOT flash the userdata.img file contained in the factory image. It is not meant for a 64GB device. And it is never needed anyway. If you want to start with a clean slate, always replace "fastboot flash userdata userdata.img" with "fastboot format userdata", and you will avoid the issue altogether.
Click to expand...
Click to collapse
New Nexus 6 owner here -- Glad I found this thread -- was kind of freaking out after updating OTA, bricking due to some random error, reflashing and just discovering my lovely 23GB free... Live and learn -- always some new "twist" with a new device. Titanium backup to the rescue again, huh?
I had to factory reset from stock recovery to fix mine...fastboot nor twrp data reset would work.
droidstyle said:
I had to factory reset from stock recovery to fix mine...fastboot nor twrp data reset would work.
Click to expand...
Click to collapse
TWRP wouldn't work because a factory reset there will only use the rm (remove) command for /data/data and /data/app. You actually need to format the entire /data partition because the incorrect size problem is a file system issue.
That said, there is absolutely no reason that fastboot format userdata shouldn't fix it. I've never seen it fail for this.
well it failed for me...I tried it several times. I could only get the right partition size from a factory reset via stock recovery. Also in TWRP I wiped data/ factory reset and formatted internal...still nothing.
No issues here w/ fastboot format userdata
FWIW and for the record, I was on rooted 5.1.1 (cf auto root), build LMY48M, and stock recovery. I backed up all apps and app data with Titanium Backup, then I used:
adb reboot-bootloader
fastboot format userdata
fastboot format cache
fastboot reboot
...and all was well with the "/sdcard" storage.
I restored all my apps and data with Titanium backup, and I'm just re-configuring my launcher again (Nova Launcher Prime). I installed TWRP earlier (I've missed it!), and I'm a happy camper (for now, heh).
Now, back to the "shadows" from whence I came.
Hello everyone!
Today I decided to change from Dalvik to ART. Phone restarted couple of times and was always stuck on "Android is upgrading". When it finally came to the unlock screen I unlocked it and then I got some error (Everytime I unlocked it). So that happened every time after I rebooted my phone. And after some time I think my battery went to 0% and I had to connect it and then I couldn't even get to the locked screen. Phone got stuck after Motorola animation and black blank screen appears.
I looked online to see what's the problem and saw that many people fixed this with flasing ROM, so I decided to do it myself. I unlocked the bootloader and tried to do some recovery with erasing cache and nothing works. I downloaded some ROMs includiding stock 4.4.4 and installed in command prompt with some fastboot commands like this:
fastboot-moto-windows.exe flash partition gpt.bin
fastboot-moto-windows.exe flash motoboot motoboot.img
fastboot-moto-windows.exe flash logo logo.bin
fastboot-moto-windows.exe flash boot boot.img
fastboot-moto-windows.exe flash recovery recovery.img
fastboot-moto-windows.exe flash system system.img_sparsechunk1
fastboot-moto-windows.exe flash system system.img_sparsechunk2
fastboot-moto-windows.exe flash system system.img_sparsechunk3
fastboot-moto-windows.exe flash modem NON-HLOS.bin
fastboot-moto-windows.exe erase modemst1
fastboot-moto-windows.exe erase modemst2
fastboot-moto-windows.exe flash fsg fsg.mbn
fastboot-moto-windows.exe erase cache
fastboot-moto-windows.exe erase userdata
Everything went smoothly but still when I turned on my phone it was still stuck at blank screen after animation.
I saw many other ways to do it including (ADB) but I'm noob at all this and tried something but I'm not sure which one to do cause there is so many guides.
Does anyone have any idea how to fix this?
I would really appreciate it!
Thanks!
candycornown said:
Hello everyone!
Today I decided to change from Dalvik to ART. Phone restarted couple of times and was always stuck on "Android is upgrading". When it finally came to the unlock screen I unlocked it and then I got some error (Everytime I unlocked it). So that happened every time after I rebooted my phone. And after some time I think my battery went to 0% and I had to connect it and then I couldn't even get to the locked screen. Phone got stuck after Motorola animation and black blank screen appears.
I looked online to see what's the problem and saw that many people fixed this with flasing ROM, so I decided to do it myself. I unlocked the bootloader and tried to do some recovery with erasing cache and nothing works. I downloaded some ROMs includiding stock 4.4.4 and installed in command prompt with some fastboot commands like this:
fastboot-moto-windows.exe flash partition gpt.bin
fastboot-moto-windows.exe flash motoboot motoboot.img
fastboot-moto-windows.exe flash logo logo.bin
fastboot-moto-windows.exe flash boot boot.img
fastboot-moto-windows.exe flash recovery recovery.img
fastboot-moto-windows.exe flash system system.img_sparsechunk1
fastboot-moto-windows.exe flash system system.img_sparsechunk2
fastboot-moto-windows.exe flash system system.img_sparsechunk3
fastboot-moto-windows.exe flash modem NON-HLOS.bin
fastboot-moto-windows.exe erase modemst1
fastboot-moto-windows.exe erase modemst2
fastboot-moto-windows.exe flash fsg fsg.mbn
fastboot-moto-windows.exe erase cache
fastboot-moto-windows.exe erase userdata
Everything went smoothly but still when I turned on my phone it was still stuck at blank screen after animation.
I saw many other ways to do it including (ADB) but I'm noob at all this and tried something but I'm not sure which one to do cause there is so many guides.
Does anyone have any idea how to fix this?
I would really appreciate it!
Thanks!
Click to expand...
Click to collapse
similar problem see here
if you can get to AP Fastboot flash mode its fixable see post #4 to reset (try this 1st)
http://forum.xda-developers.com/moto-g-2014/help/unmodified-factory-xt1068-froze-normal-t3024381/post58694698#post58694698
reefuge said:
similar problem see here
if you can get to AP Fastboot flash mode its fixable see post #4 to reset (try this 1st)
http://forum.xda-developers.com/moto-g-2014/help/unmodified-factory-xt1068-froze-normal-t3024381/post58694698#post58694698
Click to expand...
Click to collapse
Thank you for your reply!
I followed everything you posted on the other thread and it installed files successfully. But then again after animation it is still blank.
candycornown said:
Thank you for your reply!
I followed everything you posted on the other thread and it installed files successfully. But then again after animation it is still blank.
Click to expand...
Click to collapse
did you get any error messages if not that sounds like you need to wipe cache / data
can you boot to recovery to reset
or post #6 with modified script ( from AP fastboot flash mode )
will force everything to flash and reset
reefuge said:
did you get any error messages if not that sounds like you need to wipe cache / data
can you boot to recovery to reset
or post #6 with modified script ( from AP fastboot flash mode )
will force everything to flash and reset
Click to expand...
Click to collapse
I got 1 message about missing chunk.4 or something. In folder I have 0, 1, 2, 3 system.img_sparechunk.
I can boot to recovery and see 4 options (reboot system now, apply update from sdcard, apply update from ADB, wipe data/factory reset, wipe cache partition).
I already tried wipe data and wipe cache partition and still the same. Wipe cache finishes in just a second...
I already used that script in post #6.
candycornown said:
I got 1 message about missing chunk.4 or something. In folder I have 0, 1, 2, 3 system.img_sparechunk.
I can boot to recovery and see 4 options (reboot system now, apply update from sdcard, apply update from ADB, wipe data/factory reset, wipe cache partition).
I already tried wipe data and wipe cache partition and still the same. Wipe cache finishes in just a second...
I already used that script in post #6.
Click to expand...
Click to collapse
the modified is for lollipop only (dont worry it wont harm) just errors
i can do a kitkat if needed
reefuge said:
the modified is for lollipop only (dont worry it wont harm) just errors
i can do a kitkat if needed
Click to expand...
Click to collapse
Yes please.
I saw somewhere that I need to enable USB debugging for some things? How can I even enable it if I cannot access the locked screen?
candycornown said:
Yes please.
I saw somewhere that I need to enable USB debugging for some things? How can I even enable it if I cannot access the locked screen?
Click to expand...
Click to collapse
Done see other thread
no thats why its modified but you need to be able to put phone in AP fastboot flash mode by the volume down and power button method - no USB debugging required
down load 444 or 502 (not both) easy installer in my signature, then the CORRECT modified auto restore script, then extract both zip to SAME folder , usB cable in fastboot flash mode and run modified script
reefuge said:
Done see other thread
no thats why its modified but you need to be able to put phone in AP fastboot flash mode by the volume down and power button method - no USB debugging required
down load 444 or 502 (not both) easy installer in my signature, then the CORRECT modified auto restore script, then extract both zip to SAME folder , usB cable in fastboot flash mode and run modified script
Click to expand...
Click to collapse
I did as you said, download 4.4.4 and modified script into same folder. I ran the script and everything went fine, no errors.
But after it rebooted there was still blank screen after animation.
candycornown said:
I did as you said, download 4.4.4 and modified script into same folder. I ran the script and everything went fine, no errors.
But after it rebooted there was still blank screen after animation.
Click to expand...
Click to collapse
strange , DO you have the motorola device mangers drivers installed? (supplied in other thread)
did you watch phone screen as well - should have yellow confirmation text as flashes , purple shows problems
you definately have a xt1068 DUAL SIM phone?
reefuge said:
strange , DO you have the motorola device mangers drivers installed? (supplied in other thread)
did you watch phone screen as well - should have yellow confirmation text as flashes , purple shows problems
you definately have a xt1068 DUAL SIM phone?
Click to expand...
Click to collapse
Yes, I have the latest version of Motorola drivers.
SKU: XT1068
It has dual SIM
I watched the screen and nothing was purple, only yellow and on computer everything said OKAY.
I bought it on german site:
http://www.computeruniverse.net/en/products/90566676/motorola-moto-g-2-gen.asp
EDIT:
The phone can't be turned off. Everytime I turn it off it turns on again after 2 senconds.
candycornown said:
Yes, I have the latest version of Motorola drivers.
SKU: XT1068
It has dual SIM
I watched the screen and nothing was purple, only yellow and on computer everything said OKAY.
I bought it on german site:
http://www.computeruniverse.net/en/products/90566676/motorola-moto-g-2-gen.asp
EDIT:
The phone can't be turned off. Everytime I turn it off it turns on again after 2 senconds.
Click to expand...
Click to collapse
you have unlocked bootloaded status 3 in AP Fastboot Mode ?
did you at any time start a ota 5.0.2 upgrade or via any other method?
try running this in AP Fastboot Mode
reefuge said:
you have unlocked bootloaded status 3 in AP Fastboot Mode ?
did you at any time start a ota 5.0.2 upgrade or via any other method?
try running this in AP Fastboot Mode
Click to expand...
Click to collapse
Yes, I have status 3. I didn't upgrade to version 5 yet.
Do you recommend to try this fix that you attached first or version 5 that you sent me on PM?
candycornown said:
Yes, I have status 3. I didn't upgrade to version 5 yet.
Do you recommend to try this fix that you attached first or version 5 that you sent me on PM?
Click to expand...
Click to collapse
version 5 in pm now same as in my signature (both updated)
Yes I hope the 5.0.2 will sort things for you but no promises... if you have unlocked boot loader we should be able to go back to 4.4.4 (if you need to) otherwise you will be on 5.0.2
reefuge said:
version 5 in pm now same as in my signature (both updated)
Yes I hope the 5.0.2 will sort things for you but no promises... if you have unlocked boot loader we should be able to go back to 4.4.4 (if you need to) otherwise you will be on 5.0.2
Click to expand...
Click to collapse
Damn, it installed witout any problem I guess, but still stuck after animation.
Is this probably a defective phone? I am out of ideas what to do and thinking about repair shop.
candycornown said:
Damn, it installed witout any problem I guess, but still stuck after animation.
Is this probably a defective phone? I am out of ideas what to do and thinking about repair shop.
Click to expand...
Click to collapse
you do realise after the world boot up animation, it stops on the blue 'm'' globe for about 5-10 mins when setting up android, then moves to android upgrading 1 of 50 apps.... before fully booting -whole thing can take 20 mins
also i had black screen a few times (soft brick) and used my TWRP back up
still have ideas / fixes
if you install TWRP 2.8.4.0 recovery and boot to recovery
we can do full wipe inc dalvik, cache and data and try again.
if that fails
I will give you a clean restore from my fone to flash to yours via TWRP
reefuge said:
you do realise after the world boot up animation, it stops on the blue 'm'' globe for about 5-10 mins when setting up android, then moves to android upgrading 1 of 50 apps.... before fully booting -whole thing can take 20 mins
also i had black screen a few times (soft brick) and used my TWRP back up
still have ideas / fixes
if you install TWRP 2.8.4.0 recovery and boot to recovery
we can do full wipe inc dalvik, cache and data and try again.
if that fails
I will give you a clean restore from my fone to flash to yours via TWRP
Click to expand...
Click to collapse
In my case it wont even show globe for 5-10 minutes. After restore script finished on my PC and phone the phone restarted and went to animation like alaways. I didn't see any upgrading.
I will try now with TWRP.
reefuge said:
you do realise after the world boot up animation, it stops on the blue 'm'' globe for about 5-10 mins when setting up android, then moves to android upgrading 1 of 50 apps.... before fully booting -whole thing can take 20 mins
also i had black screen a few times (soft brick) and used my TWRP back up
still have ideas / fixes
if you install TWRP 2.8.4.0 recovery and boot to recovery
we can do full wipe inc dalvik, cache and data and try again.
if that fails
I will give you a clean restore from my fone to flash to yours via TWRP
Click to expand...
Click to collapse
Ok, so now that I got TWRP finally something new showed up on my phone Team Win Recovery Project v2.8.4.0. I see many options (Install, Wipe, Backup, Restore, Mount, Setting, Advanced, Reboot). What should I choose here?
candycornown said:
In my case it wont even show globe for 5-10 minutes. After restore script finished on my PC and phone the phone restarted and went to animation like alaways. I didn't see any upgrading.
I will try now with TWRP.
Click to expand...
Click to collapse
when you boot into TWRP
select wipe
advanced wipe
then tick
dalvik
data
internal storage
cache
leave
system
usb otg
external sdcard
swipe to wipe
press (left) home icon
reboot
system
do not install
reefuge said:
when you boot into TWRP
select wipe
advanced wipe
then tick
dalvik
data
internal storage
cache
leave
system
usb otg
external sdcard
swipe to wipe
press (left) home icon
reboot
system
do not install
Click to expand...
Click to collapse
Did all that and got this:
Wipe Complete
Failed
Full SELinux support is present.
E: Unable to open '/cache/recovery/.version'.
MTP Enabled
Wiping Dalvik Cache Directories...
Cleaned: /data/dalvik-cache...
- - Dalvik Cache Directories Wipe Complete!
Wiping data without wiping /data/media ...
Done.
Wiping internal storage - - /data/media...
Updating partition details...
E: Unable to stat '/data/system/++
/
1
'
... done
Hello everybody,
I'm new, I hope someone can help me here ... I'm quite sure somewhere on these forums there must already be answers for my problem but I'm too dumb to find them.
I have the European? 2014 Moto X (not sure how to get the exact model now?!)
Unlocked bootloader, rooted.
Everything was fine, except today I got the 5.0.2 (?) OTA update ...
I didn't want to do it, but it kept asking. The moment I pressed "don't ask again" the phone rebooted
and now it's stuck at the white bootup screen (Motorola logo)
I somehow managed to get into the fastboot? mode once, by somehow pressing buttons at startup ... but, well
My two questions are:
1. Can I still backup my data, photos, textfiles, etc etc
2. How do I go back to a working system. (maybe without loosing my data)
Please tell me if it's possible, and how ... or please push me into the right directions.
But as I'm half panicking detailed instructions would be so fantastic.
Personally, how I would recover data, is boot to fastboot and flash TWRP again (since you indicated you were unlocked boot loader). In TWRP, plug in the device to a computer via USB and your files will be there. Then you can reflash the stock firmware and be good to go. If you are comfortable flashing the firmware through fastboot, you can choose to not wipe data and you should be all set.
It may be worth trying just clearing the cache and seeing if you can boot.
Sent from my Moto X 2015 Pure Edition using Tapatalk
xKroniK13x said:
Personally, how I would recover data, is boot to fastboot and flash TWRP again (since you indicated you were unlocked boot loader). In TWRP, plug in the device to a computer via USB and your files will be there. Then you can reflash the stock firmware and be good to go. If you are comfortable flashing the firmware through fastboot, you can choose to not wipe data and you should be all set.
It may be worth trying just clearing the cache and seeing if you can boot.
Click to expand...
Click to collapse
Hey! Thanks a lot!
I did fastboot boot twrp, and managed to backup my data on the internat storage! Yeah! Thanks!! <3
Now to part 2, I tried to wipe the cache partition in TWRP, but it doesn't help; when I reboot it still only shows the white logo..
Should I wipe other partitions aswell? (davikcache?)
If there's a way without loosing the phone setup, it would be great.
(Installed apps ... open tabs in firefox etc ...)
I also have a "online nandroid" backup, I think from back then, right after I rooted.
Would I restore the system.img from there?
Will this remove installed apps?
Or should I restore all partitions made by online nandroid backup?!
(I thought this would be better than... or how would I find the right stock firmware online for my device?)
Sorry for being such a beginner!!!!
psssss said:
Hey! Thanks a lot!
I did fastboot boot twrp, and managed to backup my data on the internat storage! Yeah! Thanks!! <3
Now to part 2, I tried to wipe the cache partition in TWRP, but it doesn't help; when I reboot it still only shows the white logo..
Should I wipe other partitions aswell? (davikcache?)
If there's a way without loosing the phone setup, it would be great.
(Installed apps ... open tabs in firefox etc ...)
I also have a "online nandroid" backup, I think from back then, right after I rooted.
Would I restore the system.img from there?
Will this remove installed apps?
Or should I restore all partitions made by online nandroid backup?!
(I thought this would be better than... or how would I find the right stock firmware online for my device?)
Sorry for being such a beginner!!!!
Click to expand...
Click to collapse
Lollipop actually doesn't use dalvik, so that won't help. If you have a nandroid, you of course can restore to that but it would likely lose your apps/settings. You can try restoring just the system, it sort of depends on what went wrong. In my experience being stuck not booting, I generally just reflash everything. Not the most convenient but it is the most effective.
Sent from my Moto X 2015 Pure Edition using Tapatalk
xKroniK13x said:
Lollipop actually doesn't use dalvik, so that won't help. If you have a nandroid, you of course can restore to that but it would likely lose your apps/settings. You can try restoring just the system, it sort of depends on what went wrong. In my experience being stuck not booting, I generally just reflash everything. Not the most convenient but it is the most effective.
Click to expand...
Click to collapse
Hey xKroniK13x,
thanks a lot for caring!
Of course, catastrophy happened:
I did fastboot boot twrp and tried to restore system from there, didn't work so I restored system _and boot from my nandroid backup there
guess this was very stupid because
Now my phone boots right into the fastboot mode, and I can't fastboot boot TWRP anymore,
it says "incomplete boot image for booting"
partition sizes wrong, etc etc ...
what I did now was flashing TWRP, at least this worked and I can boot it from the phone now.
So, please, one more time help (for a very stupid user ):
1. I guess keeping my apps and settings is out of discussion now, haha
But is there a way, with unlocked bootloader, TWRP installed to go back to stock?
2. Now ... given my phone is not completely broken, I just thought about installing CM?!
Would this be recommended? is it working fine?
I'm just thinking about it, because with Cyanogenmod I won't have problems like this in the future, right?
(OTA updates destroying my phone because of root....)
Whoa, I'm sorry for posting this here, but ... :angel:
psssss said:
Hey xKroniK13x,
thanks a lot for caring!
Of course, catastrophy happened:
I did fastboot boot twrp and tried to restore system from there, didn't work so I restored system _and boot from my nandroid backup there
guess this was very stupid because
Now my phone boots right into the fastboot mode, and I can't fastboot boot TWRP anymore,
it says "incomplete boot image for booting"
partition sizes wrong, etc etc ...
what I did now was flashing TWRP, at least this worked and I can boot it from the phone now.
So, please, one more time help (for a very stupid user ):
1. I guess keeping my apps and settings is out of discussion now, haha
But is there a way, with unlocked bootloader, TWRP installed to go back to stock?
2. Now ... given my phone is not completely broken, I just thought about installing CM?!
Would this be recommended? is it working fine?
I'm just thinking about it, because with Cyanogenmod I won't have problems like this in the future, right?
(OTA updates destroying my phone because of root....)
Whoa, I'm sorry for posting this here, but ... :angel:
Click to expand...
Click to collapse
If you've been contemplating installing a ROM, now would be a good time to do so. Just remember to wipe the data on the phone even though it doesn't boot. And CM OTA shouldn't cause issues like this, it just flashes the zip file in your recovery. Doesn't care about root or anything of course. Otherwise, if you'd like to do stock, just use MDM to get the firmware and flash away. Hope this helped!
Sent from my Moto X 2015 Pure Edition using Tapatalk
Hi !
I have exactly the same problem.
Can you tell us how you did to fix the bootloop ?
Thank you
benjo22 said:
Hi !
I have exactly the same problem.
Can you tell us how you did to fix the bootloop ?
Thank you
Click to expand...
Click to collapse
Try clearing your cache in a recovery/fastboot, or reflash the firmware! No guarantee the cache will fix it, but sometimes it will.
Sent from my Moto X 2015 Pure Edition using Tapatalk
Thank you for your help.
Clearing the cache doesn't work, so I'm searching for others ways...
Can you tell me how to flash the firmware with adb ?
Thanks
Edit : I have an European version
benjo22 said:
Thank you for your help.
Clearing the cache doesn't work, so I'm searching for others ways...
Can you tell me how to flash the firmware with adb ?
Thanks
Edit : I have an European version
Click to expand...
Click to collapse
That is answered in the FAQ thread... It is a guide for Moto G but it is applicable for this device too. http://forum.xda-developers.com/showthread.php?t=2876769
Sent from my Moto X 2015 Pure Edition using Tapatalk
@xKroniK13x
Hey, thanks for somehow guiding me through this :victory:
MDM didn't work, so I just went for the CM 12.1 nightly.
I also had concerns because in my attempts to clear cache etc etc I had "wrong partition size" etc etc
But CM installed without problems!
(Just one more question- there can't be any problems in the future because of messed up partitions, right? Does CM fix this by installing? Or should I stop caring, if it works, it works, right?!)
In fact, CM runs great, fantastic on my phone.
I lost some app data, and most annoyingly my SMS, but ...
Other than that, I'm really happy with CM :laugh:
@benjo22
Hey, I tried to fix it by clearing cache partitions from a fastboot TWRP (I don't know how you call it, I just booted TWRP without installing it)
This didn't work, so I tried to restore a nandroid backup,
but this made it even worse. (partition errors, only fastboot mode, etc etc)
Just booting with TWRP without installing also didn't work anymore,
so I put TWRP on the phone, which luckily worked, downloaded CM 12.1, installed it via TWRP,
never did it before, but I was lucky, it seems like it worked great!
Even kept my "SD CARD" data, but lost apps and some data ...
So I didn't fix the bootloop, but I hope I made it better, futureproof...
Glad you got up and running. CM shouldn't cause any future issues as far as partitions and such.
Sent from my Moto X 2015 Pure Edition using Tapatalk
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.
Hey, sorry if this information is posted elsewhere, I haven't been able to find it with any google or forum searches. I have an Android One moto x4, on google Fi. I've unlocked the bootloader, and rooted the phone (with magisk). Before doing all this (before rooting, after unlocking), I had used TWRP's backup function.
I decided to try to get the 8.1 update [side question: I was only offered OPW28.1; would OPW28.2 have been offered to me without first updating to 28.1?] EDIT: NO. I know that I need to remove root to successfully update the phone, so I used the in-app uninstall function of Magisk, and then rebooted the phone. I tried to run the system update afterwards---and it failed, about halfway through installing. Since this point I cannot get Android to even see there is OPW28.1 , much less OPW28.2. So, I think "That's cool. I have a backup, I'll just restore from that." So, I made another backup, and then tried to restore just the system and system_image (in TWRP---this was probably a mistake). It didn't work---and I don't remember if the phone even booted. EDIT: I think I didn't wait long enough.
So I tried to restore the full backup---and it failed restoring the "bluetooth" partition: it runs out of space (!?)[1]. The phone did not appear to be able to boot after that (it spent a long time at the "Android One" screen, with the color bar oscillating). The good news for me is that I tried a factory reset (all data, I think the option was "user data and customization", the third option), and the phone starts (hooray, no brick). EDIT: TWRP backup does not work. I'll eventually file a bug about this.
Rebooting the phone, it looks totally new (but it remembered my google account name ?? what ??). However, it still isn't letting me update (still isn't seeing the new version is system updates). I tried the dialing "*#*#checkin#*#*" and it says it succeeds, but even after a reboot it doesn't do anything. I cannot find a "google services framework" (or motorola update services) to clear data on in the apps list, but shouldn't that have been reset in both the factory reset and my failed restore attempt anyway? EDIT: Nobody ever got back to me about this.
Sorry for the length of this, I'd really appreciate any input.
[1] adb shell during the TWRP restore session, "tar_extract_file(): failed to extract /bt_firmware//image/crbtfw21.tlv !!!". df /bt_firmware shows 100% use. Why would that even be possible? EDIT: The ext4 partition must have been made with slightly different options that allowed everything to be packed into the tiny partition
EDIT: I downloaded the original Fi firmware from firmware.center /firmware/Motorola/Moto%20X4/Stock/, and flashed the bluetooth partition (after confirming that the the files in that image are bit identical to the backup I made). Bluetooth still doesn't seem to be turning on. Should I just reflash everything? Can I restore my data partition and expect a functional phone? EDIT: I may have flashed to _b instead of _a. In any case I was later able to fix this by flashing the newer firmware quoted below.
SojPapus said:
Hey, sorry if this information is posted elsewhere, I haven't been able to find it with any google or forum searches. I have an Android One moto x4, on google Fi. I've unlocked the bootloader, and rooted the phone (with magisk). Before doing all this (before rooting, after unlocking), I had used TWRP's backup function.
I decided to try to get the 8.1 update [side question: I was only offered OPW28.1; would OPW28.2 have been offered to me without first updating to 28.1?]. I know that I need to remove root to successfully update the phone, so I used the in-app uninstall function of Magisk, and then rebooted the phone. I tried to run the system update afterwards---and it failed, about halfway through installing. Since this point I cannot get Android to even see there is OPW28.1 , much less OPW28.2. So, I think "That's cool. I have a backup, I'll just restore from that." So, I made another backup, and then tried to restore just the system and system_image (in TWRP---this was probably a mistake). It didn't work---and I don't remember if the phone even booted.
So I tried to restore the full backup---and it failed restoring the "bluetooth" partition: it runs out of space (!?)[1]. The phone did not appear to be able to boot after that (it spent a long time at the "Android One" screen, with the color bar oscillating). The good news for me is that I tried a factory reset (all data, I think the option was "user data and customization", the third option), and the phone starts (hooray, no brick).
Rebooting the phone, it looks totally new (but it remembered my google account name ?? what ??). However, it still isn't letting me update (still isn't seeing the new version is system updates). I tried the dialing "*#*#checkin#*#*" and it says it succeeds, but even after a reboot it doesn't do anything. I cannot find a "google services framework" (or motorola update services) to clear data on in the apps list, but shouldn't that have been reset in both the factory reset and my failed restore attempt anyway?
Sorry for the length of this, I'd really appreciate any input.
[1] adb shell during the TWRP restore session, "tar_extract_file(): failed to extract /bt_firmware//image/crbtfw21.tlv !!!". df /bt_firmware shows 100% use. Why would that even be possible?
EDIT: I downloaded the original Fi firmware from firmware.center /firmware/Motorola/Moto%20X4/Stock/, and flashed the bluetooth partition (after confirming that the the files in that image are bit identical to the backup I made). Bluetooth still doesn't seem to be turning on. Should I just reflash everything? Can I restore my data partition and expect a functional phone?
Click to expand...
Click to collapse
Go here: https://androidfilehost.com/?w=files&flid=229118
Download PAYTON_FI_OPW28.46-13_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Flash it and you're good to go. Definitely wipe your userdata as part of the instructions.
ptn107 said:
Go here: androidfilehost.com /?w=files&flid=229118
Download PAYTON_FI_OPW28.46-13_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Flash it and you're good to go. Definitely wipe your userdata as part of the instructions.
Click to expand...
Click to collapse
Thank you. Do you happen to know how I can go about checking the cryptographic signatures for these downloads? EDIT: I never managed to do this. I'm considering re-locking my bootloader, which should presumably allow this guarantee to be made. But then I risk bricking the phone. I'm not afraid to go digging around a little bit in the images (I can mount an ext4 filesystem or run simg2img no problem). EDIT: I did go mucking around, and I don't have the public key to go about verifying the bootloader. So that's probably a dead-end.
Also, is resetting user data after every upgrade just SOP when running rooted? Is there some approach to making that less painful that I don't know about? EDIT: NO CLUE. Nobody helped me with this. Also, TWRP doesn't seem to support encryption after the upgrade, so I wasn't able to try restoring from my backup. EDIT ON EDIT: Restoring a TWRP data backup went fine. However, right now TWRP 3.2.1-1 isn't supporting decryption for OPW28.1, so that's another complication. (Just remove the password, and everything seems to work)
EDIT: I've tracked down otacert.zip (containing ota.x509.pem), the key presumably used to sign the OTAs, but the images on firmware.center and androidfilehost don't seem to be signed. Were those signatures stripped out? Is it possible for me to capture those OTA directly (my phone should be receiving these)? My question still stands: how do I force my phone to download the new OTA. I'll deal with flashing it once I can get my hands on it. ANOTHER EDIT: I was able to capture the OTA, but it still isn't installing.
EDIT2: I think I've got a better link.
ptn107 said:
Go here: https://androidfilehost.com/?w=files&flid=229118
Download PAYTON_FI_OPW28.46-13_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Flash it and you're good to go. Definitely wipe your userdata as part of the instructions.
Click to expand...
Click to collapse
Flash how? From TWRP?
edufur said:
Flash how? From TWRP?
Click to expand...
Click to collapse
from fastboot
TWRP will be removed upon flashing.
ptn107 said:
from fastboot
TWRP will be removed upon flashing.
Click to expand...
Click to collapse
So here is my situation. I already rooted and TWRPd my stock phone when it was Oreo 8.0
I would like to get it up to current but stay rooted and TWRPd. Is it possible to flash it from TWRP and then immediatly reflash TWRP and ROOT?
If not, when is the right method in fastboot to go back to stock (keeping in mind I have TWRP right now along with root)....?
edufur said:
So here is my situation. I already rooted and TWRPd my stock phone when it was Oreo 8.0
I would like to get it up to current but stay rooted and TWRPd. Is it possible to flash it from TWRP and then immediatly reflash TWRP and ROOT?
If not, when is the right method in fastboot to go back to stock (keeping in mind I have TWRP right now along with root)....?
Click to expand...
Click to collapse
This is not an update zip or rom that can be flashed from TWRP. You will have to do the following:
1. Flash this firmware via fastboot which gets you 8.1.0 w/ April update. (Note: you will lose TWRP and root)
2. Boot the new stock 8.1.0 and take the may security update which will be offered almost immediately.
3. Once on 8.1.0 may update you may reinstall TWRP and a root solution. Be aware that if you do then OTAs from here on won't work. So if you want the June update you will have to re-flash stock 8.1.0 and start over.
Flashing stock will automatically remove whatever twrp or root you have.
To flash this firmware:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash boot boot.img
fastboot flash logo logo.bin
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
ptn107 said:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
Click to expand...
Click to collapse
Is there a reason you are suggesting reflashing the partition table? That would seem to expose a flasher to more risk that needed.
Granted, I'm not able to OTA to OPW28.2. But the android update engine doesn't reflash the partition table, as far as I can tell.
edufur said:
So here is my situation. I already rooted and TWRPd my stock phone when it was Oreo 8.0
I would like to get it up to current but stay rooted and TWRPd. Is it possible to flash it from TWRP and then immediatly reflash TWRP and ROOT?
If not, when is the right method in fastboot to go back to stock (keeping in mind I have TWRP right now along with root)....?
Click to expand...
Click to collapse
Could you let me know if you are able to OTA to OPW28.2 afterwards? I was not able to after reflashing.
SojPapus said:
Is there a reason you are suggesting reflashing the partition table? That would seem to expose a flasher to more risk that needed.
Granted, I'm not able to OTA to OPW28.2. But the android update engine doesn't reflash the partition table, as far as I can tell.
Could you let me know if you are able to OTA to OPW28.2 afterwards? I was not able to after reflashing.
Click to expand...
Click to collapse
Well, now I am afraid to flash since there is a question as to why the partition table was recommended. I almost want to hold out for an official flash to stock tool from motorola.
edufur said:
Well, now I am afraid to flash since there is a question as to why the partition table was recommended. I almost want to hold out for an official flash to stock tool from motorola.
Click to expand...
Click to collapse
I had no problem getting the 28.1 flashable firmware (cited earlier) working on my phone. I would be sure to only flash to the currently disabled slot--and I'd also be sure to backup the data partition before-hand (and move it off-phone). If you're not touching your active slot, there really shouldn't be any way to mess up the phone (just make sure you're able to get into fastboot with both slots first). If something goes wrong, you can just reset the active slot to the old one.
28.1 doesn't have functioning ADB, so you might also consider setting up Termux and an ssh server on the phone so you can still get a command line on it if needed.