Like the title says. I'm lost in the sauce with this. I have a Verizon VS980 rooted on software version VS98039A Android 5.0.2 . I've installed TRWP and also Flashify etc... every time I flash the .zip or .img ends up in the same result. Just throws up and security boot issue appears on the upper left corner. My goal is to install a custom rom but first step says "39A boot stack required" Someone please point me in the right direction.
Related
I'm setting up a RAZR i for a family member but cant seem to install latest OTA. It will boot to recovery fine and looks like its installing but half way through the sick android logo pops up and it reboots telling me the update failed.
I dont know if it has any significance but i unlocked the bootloader prior to trying the OTA update and also flashed TWRP recovery.
After realising the OTA required stock recovery i flashed a stock recovery image but i have no idea if this is version specific. I pulled the recovery file from LeBobo's recovery flasher tool.
The system version i'm running is 91.2.29001.XT890.Retail.en.GB does anyone have the required stock recovery i can use please?
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.
Hi,
I was on 6.0 on XT1095. Tried to root it. Screwed up by flashing something that didn't work. Now i am stuck on 'warning bootloader unlocked' screen. Previously when I was on 5.1 I restored my phone from bootloop by using official images from Moto and using their instructions. Now there are no 6.0 images. I guess trying to reflash the whole 5.1 ijmages would brick my phone. I tried flashing just the system image of 5.1. It didn't work.
I found this 6.0 stock ROM here on XDA http://forum.xda-developers.com/moto-x-2014/development/rom-xt1095-flashable-stock-rom-t3277874 . How do I flash this?
Please help. I'm on stock recovery. Previously I ran commands like 'fastboot flash system x.img' and so on when phone was in fastboot mode. How to flash this zip now.
Thanks in advance.
A bootloop is simple to get out of. Just press and hold the power and volume down keys to boot into recovery and go from there. If your phone isn't booting past the unlocked bootloader warning splash then you need to elaborate on WTF you flashed. Just saying "something that didn't work" isn't sufficient to make an accurate diagnosis.
To flash that stock ROM you posted a link to above would require you to fastboot flash a custom recovery first.
As for restoring a 5.1 image I don't understand why you'd think that would brick your device. You're formatting the entire device by going back to ANY stock image. Just because you are on 6.0 doesn't mean you have to restore a 6.0 stock image (that probably won't be available for some time).
sent from my moto x™
Hi, I updated my rooted OnePlus 3t with an OTA update (dumb, I know, I wasn't thinking). It failed and the device needed to be wiped. I've since tried to go through the process to reinstall twrp and supersu and I can no longer get it to boot when TWRP and superSU are installed. The weird thing is, I AM able to use it with the stock recovery and non-root, but any subsequent flashes fail, despite it appearing as if everything has been installed properly.
One last wrench to throw into this: I cannot access recovery (whether TWRP or stock) without running
Code:
fastboot boot recovery.img
. When I run that, I'm able to get into recovery, however if I go through the phone itself on the main menu after unlocking the phone, it just reboots and brings me right back to where I was.
Any ideas on what I may have done wrong and how to fix it? I've been following the guide from the oneplus forums, I've run that process about 5 or 6 times over the past day to no avail.
P.S. Have flashed the newest version of dm-verity
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.