I decided a few days ago that I wanted to restore my Moto X Pure to stock and lock the bootloader. I have been unsuccessful so far. I have attempted to restore the stock OS via the Moto X Pure Multi Tool V3 and all 3 stock image sets from Motorola's website.
I can restore all images except the partition. The phone is running fine, just unlocked. When I attempt to flash the partition file I get the error message "(bootloader) Preflash validation failed"
I initially had problems after unlocking and installing CM because the partitions were weird. Installing TWRP instead allowed me to install CM.
Related
So basically, I was running a rooted stock 2.2 on my Droid 2 when I noticed the notification for an update... so I allowed it to download and install the update and it failed, of course. So no biggie, right? I'll just wipe the system and flash the 2.3.20 update.zip - well, the flash worked but broke my camera app, my dialer, my keyboard and a few other system apps.
SO, I downloaded and reflashed... same thing.
Now, my plan was to wipe the system again and flash the SBF... Opened up RSD, loaded the SBF and started the flash.
after about 10 minutes, I get an error in RSD telling me the flash failed and the "system is corrupt"
My phone now says:
Bootloader
D2.35
Code Corrupt
Battery OK
OK to Program
Transfer Mode:
USB
So I tried flashing the SBF again... same error. Phone won't eve make it to the splash screen..
Now what?
*EDIT/UPDATE:
3rd time's a charm!!! The third SBF flash attempt succeeded, phone is rebooting now. *crosses fingers*
Okay we're good - anyone know why the flash would fail twice and then succeed with absolutely nothing different??
I unlocked the bootloader of my moto x pure and flashed twrp on it. I also installed cyanogenmod 13 onto my phone and everything was working fine, up until I tried using the encrypt feature in the cyanogenmod settings. I started the process, but after over 36 hours of it not finishing and staying in the booting screen I realized there was a problem. I cut the failed process short and from then on my phone would only ever stay in that same screen when powered it on. I tried restoring a backup as well as reinstalling the system, but when I try restoring it says there is an
"Error opening: '/data' (I/O error)".
When I try reinstalling cyanogenmod, twrp says it is successful but it stays in a bootloop, permanently showing the picture of the cyanogenmod guy.
Thanks in advance!
I created a Nandroid of my X Compact running Marshmallow using TWRP (TWRP-3.0.2-3-F5321) last week. TWRP told me the recovery had completed successfully.
When I tried to restore from that recovery today, I received the error message: "Your device has been unlocked and the boot image is not working"
Any ideas as to what I've done wrong?
Seems like something wrong with kernel... Try to reflash your kernel in recovery, fastboot or Flashtool, depending what kernel are you using..
Thanks so much. I formatted my handset and started again from scratch so I'm a bit reluctant to try and restore now, but in the future if I need to I'll try and reflash the kernel. (I'm using Androplus Kernel)
I'm a relative beginner to flashing and rooting I used the ZTE axon 7 toolkit and now my phone is stuck in the boot animation. I can get into TWRP but when I flash the LineageOS zip in TWRP I get the following in red: Updater Process ended with Error: 7 Error Installing zip file '/external_sd/lineage-14.1-20170605-nightly-axon7-signed.zip' Updating Partition details....
....done Not sure what I'm doing wrong any help appreciated.
Did you fully wipe system before installing lineage? Did you make a back up of stock before installing in TWRP? Did you make sure your specific model is supported for that particular ROM?
Bad download?
Install Nougat bootloader.
I installed Nougat and tried to flash it using TWRP it installed successfully but when I turn the phone on I see this error image imgur.DOTcom/a/1EljH I can't insert links because I'm under 10 posts it seems)
How could I flash a stock rom if the recovery is now stock?
I attempted to install Lineage OS on my Pixel C. When I attempt to sideload Lineage OS, I get an error that says "Updater process ended with signal: 7" and it acts like I have no system image installed and just keeps boot-looping. I tried to flash back to stock, but I keep getting an error that says "error: Cannot generate image for userdata". I have re-downloaded all of the images, and retried over and over again, to no avail. Any advice is appreciated!
Well, I finally got my tablet to boot again. I extracted the factory image and individually flashed each component (boot, cache, recovery, vendor, system - in that order) and I'm back to a clean install of the stock android. I went back and flashed twrp (successfully), and tried to sideload Lineage again per the instructions on their website, and got the same result. If I can't figure this out, I may be going back to just stock android.
Is it your first attempt at a custom rom?
Have you flashed a recent kernel, bootloader is unlocked etc?
edit: lol, last reply was from May..
Hey, I guess I haven't been on here in a while, and never saw your reply to this. It is not my first attempt at a custom rom. Bootloader is unlocked, and kernel is up to date (or was in May). I ended up staying on stock android since I had no trouble getting it to work. Best I can recall, I think I read that there was a conflict between TWRP and the kernel version I was on. Around the same time, I tried to flash LineageOS to my Essential PH-1, and had similar issues, and ended up just staying with stock android. I've been flashing custom roms since cyanogenmod was available on my Nexus One (I think that was on cupcake), and while I'm not an expert, I'm pretty comfortable with the process, so I went back to my Moto N6, and was able to flash LineageOS to that without a problem. I know that the Pixel C and PH-1 both have the whole A/B slot architecture, and I wonder if I wasn't managing that correctly, but I've gone through a couple of custom roms on my Pixel C over the years without having that problem, so I just don't know. Right now I'm fine with stock (rooted) Android, but the bug is sure to bite me again soon, so we'll see what happens then.
I recently downgraded to Lineage 15.1 (official) from 16 and had some issues.
Short story to make it work was; installed the April version of the official factory/ota image like you did to overcome version conflicts.
(booting to TWRP.img after getting to the correct recovery menu by pressing power+volume up).
In TWRP; As the \data folder was encrypted I had to format that first (advanced wipe) and used adb to push files to \sdcard.
I flashed the Lineage 15.1 zip, gapps and Magisks before rebooting.
As that build enforces encryption of \data at first boot you may need to use "default_password" to load TWRP with access to \data in the future.
Hope this helps