So I'm coming from a cm-12.1 install and going back to stock since Android Pay doesn't work under cm and I just want to give it a try. I downloaded the stock OS from Motorola's developer portal and flashed back using the exact order listed in the readme. Now that I'm attempting to boot I'm stuck on the bootloader unlocked warning screen. I have an XT1060(VZW Dev edition). Yes I am using the VZW Dev 4.4.4 images. I did do a complete format of all partitions prior to flashing except /data although I did use TWRP to wipe /data excluding /data/media. What am I doing wrong that's causing my phone not to boot? I'm currently in the process of restoring my cm-12.1 backup but I'd like to get back to stock.
This issue has been resolved. For whatever reason motorola included 4 fastboot binaries with the images. A Windows one, Darwin one, and two for Linux. One of the Linux binaries was not patched with multiflash and the other was. I was using the one without multiflash and so I ended up with a corrupt system partition which explains the failure to boot.
Related
So I'm fairly new to using custom roms but I've been flashing different roms on my nexus 6 for the past few weeks seeing which one I like. Anyway, I've been running chroma and lean kernel de encrypted but I was getting some weird glitches in chrome so i decidd to flash blisspop. I did a standard wipe in twrp and flashed blisspop and it just went straight to a black screen then reloaded twrp. I tried rebooting the system and I got to the blisspop splash screen but it wouldn't boot past that so I forced it to reboot to recovery (might have been a mistake) but I wiped/flashed back to the chroma rom I'd been using and that did the same thing. I managed to get it to display the error which was something along the lines of unable to access data. I tried formatting but it gives an error along the same lines. I think I somehow deleted or corrupted my data partition and I can't find any way to fix it. When I get home I can post a more specific error report if it's needed. Is there some way to reformat partitions with twrp and adb? Any help would be greatly appreciated.
Not adb but boot to bootloader and do "fastboot format userdata".
If you haven't an unencrypted kernel, flash one before boot
Just took delivery and trying to root. Using nexus root kit successful at unlocking. But will not unencrypt or root. Being denied copying files from PC to device Also can not flash/recover to any other boot img. Is there anyway to revert back to an unencrypted image? Stock build came as LMY47D but it updated to the 5.1.1 yesterday. Also is there any known issues using windows 10 to run the toolkit?
Have you tried just doing everything the proper way following our guides?
i.e using fastboot to flash stock images, and TWRP recovery. Then use recovery to flash a kernel that doesn't force encryption. Then format userdata from recovery.
It's very easy
yeah, I hate to be that guy, but you really should avoid the toolkit and learn some very basic fastboot and adb commands.
Once you have these at your disposal, you can pretty much unbork anything on a nexus.
Okay, I haven't been able to update since LMY48I. Back then I was on stock recovery. Re-locking bootloader and all but still was not able to take OTA (always came up with dead android guy with "Error"). I'll skip the (probably) irrelevant stuff since then and give you the current situation:
Currently unlocked, rooted, with custom recovery. Still on LMY48I. I can't take OTAs obviously, and have tried flashing OTA updates manually with no luck and have tried flashing the entire Marshmallow image and that will not work either (sideload or flashing from internal storage in recovery). Sideload comes up with Closed error (device DOES show up in device list and I can do other things). Flashing from within recovery just says "Failed".
Please help me get to Marshamallow!
Edit: On Project Fi by the way.
Edit 2: Also, I've tried the flash-all script.
Now it says the device is corrupted when I boot up. I can still access recovery. Any help walking me through getting all of the correct firmware and latest build on would be much appreciated.
Thank you.
Edit: Looks like i'm good. I flashed each .img individually. I'm super curious why flash-all, sideload, and flashing from device wouldn't work though.
altvisionx said:
......./I flashed each .img individually. I'm super curious why flash-all, sideload, and flashing from device wouldn't work though.
Click to expand...
Click to collapse
Flashall.bat stops; only m-bootloader and m-radio are flash. Google's fault. You did the right thing by extracting the images and fasbiot flash them.
You cannot sideload the full factory image or flash from storage. Only fastboot
And just to clarify, you can't take an OTA (sideloading or otherwise) if your phone is rooted, have a custom recovery or a custom kernel (or any other modification to the system). The state of the bootloader (locked or unlocked) does not affect the ability to take an OTA update.
Hello I am working with an XT1060 Developer edition, it is verified to be the xt1060 vie barcodes in The bootloader menu. It has twrp installed and has bootloader unlocked. After trying to flash CM12.1 it is stuck in bootloop. Oddly it appears that my system backup has been deleted. I have tried to flash a firmware zip that is allegedly the vzwxt1060dev edition 4.4.2 and boot animation is different indicating that the OEM ROM did load however the boot loop remains. I did erroneously flash a recovery.IMG onto the boot partition using twrp, however I was under the impression that flashing a new ROM would overwrite this. What is it that I am missing here?
I bootloop mine on a regular basis not having a SD card sucks adb sideload gets me up and going u lose everything
Hello,
I tried to install the Oreo 8.1 OTA update, OPS28.65-36 on my dad's moto, which is currently running NPSS26.116-26-18.
The boot loader is unlocked but all partitions are unmodified, when I run TWRP I always do that using "fastboot boot twrp.img"
Unfortunately the update fails with an error but does not tell me which error it is.
I tried to side load the appropriate OTA update using fastboot, I got the zip from https://forum.xda-developers.com/showpost.php?p=77963554&postcount=224 which seemed to be the right release channel reteu
This failed with an error indicating that the system partition's checksum was not was was expected.
Strangely after that TWRP 3.1.1 stopped working i.e. it stuck at boot on the boot logo, luckily a newer edition TWRP-3.2.1-r20 (64bit Supported!) worked.
I guess the half done side load updated the boot loader and or the base band firmware before it failed with the system partition
I have a TWRP backup of boot and system from then the phone was new and one from today morning, it seams that when the phone was ne it had NPSS26.116-26-16 so it has installed some OTAs in the mean time. Also the checksum's of boot and system changed between the two backups.
How How can I get the new firmware onto the phone? Is there some were a TWRP instalable Oreo 8.1 image? Or a fastboot flashable full image?
Has someone else experienced similar issues?
First of all this should be in Q&A form not development. Secondly a fastboot flashable file has been available for quite some time. Anytime you've use TWRP even just booting into TWRP leaving stock recovery it modifies the system so that's why the OTA fails. Here is the thread for a fastboot flashable Oreo update.
https://forum.xda-developers.com/mo...t/moto-g5s-plus-moto-stock-firmwares-t3843626
I'm sorry for posting in the wrong section in was in a hurry and did not payed attention to detail, mea culpa.
I see in that listing you've linked only one file "SANDERS_OPS28.65-36_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" that is for Oreo and it does not say for which release channel it is.
Does the release channel even matter with a full image?
I would also like to inquire about your statement that just booting TWRP from RAM changes partitions, could you please provide a link to corroborate that. I find that very unexpected. IMHO normally it should not auto mount any partition writable unless selected in the mount options or required by the choose operation.
As I reported the phone seams to have installed some minor OTA's between the first and the second update. The version numbers changes and the boot and system partitions are very different.