Ok guys so I have a Sony Xperia Z Ultra and I decided to install Marshmallow 6.0 on it (which wasn't released for my phone). I downloaded the boot, cache, system and userdata imgs of Marshmallow 6.0 and installed them using fastboot, then I was supposed to boot in recovery mode and wipe the caches and do a reset, before installing the G-apps zip file and completing the entire process. So I tried to start recovery mode which I had previously installed already and it failed, starting in safe mode instead. Then I re-installed the recovery using a batch file in a directory downloaded from NUT's XDA Developers download site, which failed on the first try. So I tried again and it was installed, meaning my phone will automatically reboot into recovery right after it was done. My phone rebooted but my screen remained black and nothing happened. I tried holding down the power button and it vibrated but nothing happened again. I tried holding down the power and volume down button for 30sec and more, tried it with the volume up button too and it didn't work. I tried connecting my phone to the pc but it won't recognize it (of course) and I tried holding the volume up button upon connecting to enter fastboot but that failed as well. Now it's stuck like this and I'm hoping its battery drains out and it powers off. Help.
Update: I went to sleep and now that I've woken up, the screen is still going with the low battery red light. I don't know for how long it will continue, but the problem remains.
Update: Now my pc recognizes it but all adb commands have no effect.
Jissatsu said:
Ok guys so I have a Sony Xperia Z Ultra and I decided to install Marshmallow 6.0 on it (which wasn't released for my phone). I downloaded the boot, cache, system and userdata imgs of Marshmallow 6.0 and installed them using fastboot, then I was supposed to boot in recovery mode and wipe the caches and do a reset, before installing the G-apps zip file and completing the entire process. So I tried to start recovery mode which I had previously installed already and it failed, starting in safe mode instead. Then I re-installed the recovery using a batch file in a directory downloaded from NUT's XDA Developers download site, which failed on the first try. So I tried again and it was installed, meaning my phone will automatically reboot into recovery right after it was done. My phone rebooted but my screen remained black and nothing happened. I tried holding down the power button and it vibrated but nothing happened again. I tried holding down the power and volume down button for 30sec and more, tried it with the volume up button too and it didn't work. I tried connecting my phone to the pc but it won't recognize it (of course) and I tried holding the volume up button upon connecting to enter fastboot but that failed as well. Now it's stuck like this and I'm hoping its battery drains out and it powers off. Help.
Update: I went to sleep and now that I've woken up, the screen is still going with the low battery red light. I don't know for how long it will continue, but the problem remains.
Update: Now my pc recognizes it but all adb commands have no effect.
Click to expand...
Click to collapse
you should give some info... like what rom youre using. also use twrp 3.x with mm
you cant expect help without telling the error messages you get...
you can always power off your phone with holding vol down + power for 30sec
MusterMaxMueller said:
you should give some info... like what rom youre using. also use twrp 3.x with mm
you cant expect help without telling the error messages you get...
you can always power off your phone with holding vol down + power for 30sec
Click to expand...
Click to collapse
YEAH ok here's my issue. NO MATTER WHAT recovery I install (through the app or fastboot) IT DOES NOT WORK. Any earlier version of TWRP, it will boot into, but the screen is unresponsive, while the latest version of TWRP simply acts like it isn't there as the phone never boots into recovery, this has been happening on MM and now it's happening on my latest stock. After the failed MM attempts I've downloaded the latest C6833 stock and everything is fine, but I'd like to be able to install custom roms like everyone else. It took me a day or two to learn how to actually do that, but I still have no idea why NO recovery works for me. My device is rooted, bootloader unlocked, all that crap. I tried many kernel links on your site, especially that main one that the mod posted, but the links are dead. Help.
Jissatsu said:
YEAH ok here's my issue. NO MATTER WHAT recovery I install (through the app or fastboot) IT DOES NOT WORK. Any earlier version of TWRP, it will boot into, but the screen is unresponsive, while the latest version of TWRP simply acts like it isn't there as the phone never boots into recovery, this has been happening on MM and now it's happening on my latest stock. After the failed MM attempts I've downloaded the latest C6833 stock and everything is fine, but I'd like to be able to install custom roms like everyone else. It took me a day or two to learn how to actually do that, but I still have no idea why NO recovery works for me. My device is rooted, bootloader unlocked, all that crap. I tried many kernel links on your site, especially that main one that the mod posted, but the links are dead. Help.
Click to expand...
Click to collapse
there is other way to enter twrp 3.0.2 with new bootloader, power + vol down (instead of up!)
read op of twrp thread and follow instructions carefully and it'll work. also for the twrp i build you must be on a rom which uses sony aosp device tree (like aicp). otherwise i wont guarantee that it will work.
MusterMaxMueller said:
there is other way to enter twrp 3.0.2 with new bootloader, power + vol down (instead of up!)
read op of twrp thread and follow instructions carefully and it'll work. also for the twrp i build you must be on a rom which uses sony aosp device tree (like aicp). otherwise i wont guarantee that it will work.
Click to expand...
Click to collapse
I tried holding the button down like you said, tried rebooting to recovery from TWRP manager itself, with root access granted of course. Nothing. Can you link the post or something? However I don't think anything in it will fix my issue.
Sounds like you flashed a recovery for another model. I had this issue with a ROM awhile back.
Didn't read the walls of text.
I recommend using you flashtool and flashing a stock ftf. Re-root, recovery and flash again.
---------- Post added at 06:16 AM ---------- Previous post was at 06:11 AM ----------
Edit. Read somethings. There are plenty of ROMs on xda do not flash the old way which is part by part. Flash the most recent Sony firmware, and you should be able to flash MM ROMs.
I have copy's of the recovery if needed.
I did flash the latest FTF using the flash tool, but I need a working recovery in order to install the gapps and still no recovery works on my device.
check here
http://forum.xda-developers.com/xpe...2-0-togari-t3452968/post68481255#post68481255
Related
Ok, so I rooted my LGOG E970. I figured I better unlock it as well, so I used FreeGee and unlocked it. I tried to download CWM but it said it couldnt download file. So I thought I would reboot my phone. Now, all I get is the google logo, with the unlocked key underneath, and it then goes to the LG logo and back to Google and shuts off. I tried to hold down power and volume down, nothing, and power volume up nothing.:crying:
any ideas? Thanks in advance! I love this phone!
CJ
You too, huh?
I did this the other night, and when the CWM failed to install I went to download it myself... That's when I saw that CWM for geeb is 6.0.3.8, not 6.0.4.5 like FreeGee shows. (Looks like FreeGee has moved on to targeting G2 or another... Oops.)
I hope you backed up your EFS, because mine was screwed up and I needed to manually restore it from the backup I'd taken. (I've had my phone rooted for 9+ months, finally got fed up with stock and was looking to get onto a 4.4 ROM)
So here's what I did:
Held power button until phone was properly off (failed boot seemed to be a still partially on state)
Held volumn up first, then started holding power.
When phone vibrated slightly, I let go of power and kept holding volume up... You should be in boot loader now.
When your phone is in the bootloader, connect to your PC (Make sure you have the proper drivers if you use Windows; I use Linux which doesn't have the same nonsense setup for drivers like Windows does)
Make sure "fastboot devices" shows your phone and then type: fastboot flash recovery _____recovery file name.img____
Press volume down twice to select "Recovery", and press power once to select it... You should be booted into the recovery that you just installed.
Once you're in a recovery, you can push a ROM zip via ADB, flash, wipe data/dalvik cache and reboot.
thanks, Just a little more help
aedren said:
You too, huh?
I did this the other night, and when the CWM failed to install I went to download it myself... That's when I saw that CWM for geeb is 6.0.3.8, not 6.0.4.5 like FreeGee shows. (Looks like FreeGee has moved on to targeting G2 or another... Oops.)
I hope you backed up your EFS, because mine was screwed up and I needed to manually restore it from the backup I'd taken. (I've had my phone rooted for 9+ months, finally got fed up with stock and was looking to get onto a 4.4 ROM)
So here's what I did:
Held power button until phone was properly off (failed boot seemed to be a still partially on state)
Held volumn up first, then started holding power.
When phone vibrated slightly, I let go of power and kept holding volume up... You should be in boot loader now.
When your phone is in the bootloader, connect to your PC (Make sure you have the proper drivers if you use Windows; I use Linux which doesn't have the same nonsense setup for drivers like Windows does)
Make sure "fastboot devices" shows your phone and then type: fastboot flash recovery _____recovery file name.img____
Press volume down twice to select "Recovery", and press power once to select it... You should be booted into the recovery that you just installed.
Once you're in a recovery, you can push a ROM zip via ADB, flash, wipe data/dalvik cache and reboot.
Click to expand...
Click to collapse
I try to go to recovery and it just goes blank. What program with my crazy windows would be best to get a stock file to the phone? Or any other ideas>
thanks again
ZombieGeek said:
I try to go to recovery and it just goes blank. What program with my crazy windows would be best to get a stock file to the phone? Or any other ideas>
thanks again
Click to expand...
Click to collapse
Yeah, the stock recovery won't boot if you try it either. I forgot to tell you that. If you drop in a custom recovery (TWRP or CWM), it will work fine and you can both create a backup of your data and flash a new ROM...
If you want to try to get back to stock, LGNPST is what you should try. But to be completely honest, I don't know if you can LGNPST from the state that it's in. I haven't tried, and I'm using a custom ROM now (the whole reason I unlocked the bootloader to begin with).
bummer
aedren said:
Yeah, the stock recovery won't boot if you try it either. I forgot to tell you that. If you drop in a custom recovery (TWRP or CWM), it will work fine and you can both create a backup of your data and flash a new ROM...
If you want to try to get back to stock, LGNPST is what you should try. But to be completely honest, I don't know if you can LGNPST from the state that it's in. I haven't tried, and I'm using a custom ROM now (the whole reason I unlocked the bootloader to begin with).
Click to expand...
Click to collapse
again, thanks so much! you are my hero, only problem is, I loaded the kit kat bu houstonn and now I have no cellular? I hate it when your phone isnt a phone lol
ZombieGeek said:
again, thanks so much! you are my hero, only problem is, I loaded the kit kat bu houstonn and now I have no cellular? I hate it when your phone isnt a phone lol
Click to expand...
Click to collapse
Yeah, I got that too. I don't know if I got it fixed due to changing ROM, using the suggested recovery from the ROM, or if it was due to me restoring my EFS backup.
I flashed the TeamWin recovery found in the PSX instructions. Then I flashed PSX + Latest kernel + Banks Gapps + Banks Google Camera + AT&T NFC fix + SuperSU. I manually restored EFS from an ADB shell while in recovery.
When I booted I had: LTE works, Wifi works, NFC works, Camera works, ART works... The only things failing for me are the following:
Cell provider shows up as "Maritime" (display bug; as mentioned, LTE works fine and I'm on AT&T)
Settings > Developer Tools > Geeky Process Stats (does nothing)
Settings > Lockscreen > Slider Shortcuts (crashes as soon as I tap the middle ring)
LogCat is spammed with "QCOM PowerLock: Failed to acquire lock" whenever my finger is on the screen.
/system/xbin/mount --bind doesn't work (neither does mount -o bind). It gets sorta half-way-there, because the target directory can't be removed, but isn't bound properly it seems.
Other than that, it's been fast and smooth.
Hallo,
I think i might have bricked my device.
Currently i have "light" in the display of my Sony Xperia Go, but there are no boot animation or anything on screen.
It does not react to any button combination that i know of (which is power on/off and holding volume up while inserting usb).
I am using linux.
The phone was rooted, with working SU - using "Root_with_Restore_by_Bin4ry_v35"
The bootloader was unlocked with instructions from http://developer.sonymobile.com/unlockbootloader/
I wanted to use
[ROM] [UB] [XperiaSTE] CyanogenMod 11 for Xperia go.
I downloaded the file cm11.0-4-lotus.zip from build link 4.
I extracted boot.img from the zip as pr instructions.
Powered off the device, pressed vol up while inserting the usb.
Then i ran the following command from terminal:
fastboot flash boot boot.img
Which flashed the img and confirmed the success.
Then i tried to reboot the device to go to step 3 in the instructions for the CM rom.
But it never powered on properly.
I can not turn it off, and i can not find the device with fastboot if i try to connect like i did before. (power off the device, pressed vol up while inserting the usb.)
Are there anything i can do?
I wanted to try to remove the battery, but im not sure if its doable with normal tools?
Im sorry, i should have searched more before posting.
The quote below seems to have restored the contact to the phone. Now i just need to flash correctly.
Cwikla said:
When it stuck, press vol up amd power and wait for 3 vibrations. After that it should boot up normally.
Click to expand...
Click to collapse
I have the exact same problem, and posted my question in the Newbies thread:
http://forum.xda-developers.com/showpost.php?p=54125595&postcount=3957.
Please, have you found out how to solve the issue?
Yes.
Follow the instructions in the quote from my previous post.
Then the phone turns off, after which you can connect to it again.
Hold down vol up, and insert your usb cable.
When the light turns blue/purple, you will be able to use fastboot again to flash a new boot.img file.
Im still working on my own phone, its not running yet.
Yeah, got there as well.
I have reflashed stock and tried again a couple of times with no luck.
We are not the only ones:
http://forum.xda-developers.com/xperia-u/issues/install-cm11-xperia-sola-t2810800
Perhaps it's the TWRP recovery that doesn't like our model?
Tried the:
[ROM][UB][UNOFFICIAL] OmniROM 4.4 for Xperia Go
It uses CWM, and here I can activate recovery and install the rom...
In the xperia go section, there's a thread with all the kitkat rom's.
I tried all of them, but only omnirom worked for me, like with you.
However, one or two of them did use TWRP, so I don't think it is because of the recovery.
I'd prefer to get slimrom on the phone, like I've got on the one I'm using my self.
But I couldn't find any download link for xperia go
I have an XT1526 from Freedompop. It came prerooted with TWRP installed, however SuperSU was removed. I tried to install SuperSU via Google Play, and after that the phone would not start. It would be stuck on the Moto logo. I tried to reinstall supersu via TWRP . I used this package:
SR1-SuperSU-v2.79-SR1-20161221223537.zip . The install went through, but the phone still does not start.
I tried to do something via adb/fastboot.
adb devices does not show the phone connected, however fastboot devices sees the phone connected.
fastboot reboot works too.
What should I do now?
Currently only bootloader and TWRP work. TWPR sees the content on the SD card
mzel said:
I have an XT1526 from Freedompop. It came prerooted with TWRP installed, however SuperSU was removed. I tried to install SuperSU via Google Play, and after that the phone would not start. It would be stuck on the Moto logo. I tried to reinstall supersu via TWRP . I used this package:
SR1-SuperSU-v2.79-SR1-20161221223537.zip . The install went through, but the phone still does not start.
I tried to do something via adb/fastboot.
adb devices does not show the phone connected, however fastboot devices sees the phone connected.
fastboot reboot works too.
What should I do now?
Currently only bootloader and TWRP work. TWPR sees the content on the SD card
Click to expand...
Click to collapse
Press and hold the power button on the boot animation screen until the phone is forced restarted again.... Do this until it boots completed
If the problem doesn't stop, try different version of SuperSU.... Also tell more about your ROM?
Assassin's Blood said:
Press and hold the power button on the boot animation screen until the phone is forced restarted again.... Do this until it boots completed
If the problem doesn't stop, try different version of SuperSU.... Also tell more about your ROM?
Click to expand...
Click to collapse
I have restarted the phone this way many times and it never comes past the logo. Also on the long press it does not shut down, it only restarts.
What is the version of SuperSU suitable for this phone?
I have not changed the ROM. It is whatever it came with. How can I check?
A
mzel said:
I have restarted the phone this way many times and it never comes past the logo. Also on the long press it does not shut down, it only restarts.
What is the version of SuperSU suitable for this phone?
I have not changed the ROM. It is whatever it came with. How can I check?
A
Click to expand...
Click to collapse
Check it in your settings or bootloader.... Turn off the phone and press down+ power simultaneously....
Assassin's Blood said:
Check it in your settings or bootloader.... Turn off the phone and press down+ power simultaneously....
Click to expand...
Click to collapse
With power+Volume up it goes to the Moto logo. With power+Volume Down it goes to the bootloader and shows some info. No word about the ROM. What is strange - baseband NULL.
I suppose it is some Boost ROM, but this is just my guess
Wiping the phone via TWRP and flashing the https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip helped.
Thanks a lot!
Hi friends,
i already tried all the guides from xda and my blu vivo 5 doesnt work with this combination: marshmallow+twrp+root.
I did the flash to android 5.1 and ok;
i did the ota update to android 6 ok;
when i try flash to twrp, my fastboot doesnt work, i have this message:
"fastboot mode...
the function had been switched off for private information secure,forced open would be at risk". And i cant acess the recover mode using volu - plus power buttom,simply doesnt work.This happend only after the ota uptade to android 6.
I dont know how to fix it,any idea about what the hell is going on?
up!! same problem here i tried absolutely all methods and app's but no one helped as long as the boot loader is locked i can't get any chance to root this phone *Blu vivo5* *Android 6.0-Marshmallow*
wohcalamity said:
up!! same problem here i tried absolutely all methods and app's but no one helped as long as the boot loader is locked i can't get any chance to root this phone *Blu vivo5* *Android 6.0-Marshmallow*
Click to expand...
Click to collapse
Friend, i did it.Now im on marshmallow + twrp+ xposed everything alright, including battery.
What happend to me(its not so easy like these guides and steps):
Ive tried a lot of combinations of configurations...try this:
1- flash to stock rom, use flash tool like administrator, dont select user data and flash.
2- wait phone reboot, if stop in boot logo, just press power down and wait.I did some errors here, apps erros and the phone stay in loop on boot, so, if happends just press volume + and power, wipe cache and restore, it will work and you will acess normally.So, go to settings and give a new format factory.After this, do ota update,there are two, one with 97 mb and the android with more that 1gb.
3-Same way, after config marshmallow, wipe cache and do restore,so, go to flash tool again, here is the "key" that works to me :
take the recovery file from this post : [ROOT][HOW TO] Going from Stock Lollipop to marshmallow official and root it!!! (sorry but i cant post links) and do the same, dont select user data and flash.After flash, press vol + and power and see if your phone goes to twrp menu, if doesnt work, flash again until it works.I tried a lot of times and i have a strange issue, my phone lose acess to twrp sometimes and i have to repeat the flash process.
After you get the twrp the things will be easy, just take the super su file and install with twrp.
So, i did it even being with fastboot locked and i didnt set usb debbuging or any configuration, just flash and wipe until it works, but work...
Hi guys, any help would be much appreciated! I have studied all threads on XDA on bricked and boot loop'ed Honor 5X phones. I'm not a complete noob -- I have been flashing CM/LineageOS for years on Nexus 4, 5, 7, 9 and 6P, and this is the first time I have been stumped.
My KIW-L24 has an early version of LineageOS 14.1, and also TWRP 3.1.1-0 on it. I used the LineageOS updater to download a later LineageOS build, and initiated the update. As expected, the phone rebooted into TWRP, briefly showed the TWRP boot screen, but then after about 1 second, the phone reboots to the Honor boot screen for about 3 seconds, and then boots back to TWRP ... and so the cycle repeats endlessly between the two boot screens until the battery dies.
I cannot seem to get the device into bootloader/fastboot mode so that I can reflash TWRP and/or LineageOS or stock ROM. I have tried every combination of hardware keys to get the phone into fastboot (including Power+Vol Down). I tried initiating the download mode back to stock with the update.app placed in /dload/ on the sdcard (Power+Vol Down+Vol Up). I tried plugging in the PC-USB cable + Vol Down. While plugged into the PC via USB cable, I tried issuing "adb reboot bootloader" while the TWRP screen momentarily pops up (I literally have a less than a half-second when adb recognizes the phone). All without any success.
I am truly stuck! Any ideas? I have a practically brand new paperweight at the moment. :crying: Thanks very much in advance for any suggestions!
Are you sure battery isnt flat ?
You can use twrp as fas as i understand.. Correct me if i am wrong..
You can download stock rom twrp backup for your model from repository thread and try to restore backup with twrp..
Thanks, but I cannot 'use' TWRP! If I could, my problems would be easily solved, I have plenty of experience re-flashing ROMs, boot images, radios, etc.
Also, the battery is fine. At full charge, the phone powers up and immediately enters the endless boot cycle I previously described.
As soon as the phone shows the TWRP boot screen, the phone reboots again. I cannot do anything at all with TWRP. As I previously wrote, I have even tried using adb to force a reboot into fastboot while the TWRP boot screen shows for that split second (the PC momentarily recognizes the USB Android device). Unfortunately , TWRP reboots the phone too quickly.
pet_zeus said:
Thanks, but I cannot 'use' TWRP! If I could, my problems would be easily solved, I have plenty of experience re-flashing ROMs, boot images, radios, etc.
Also, the battery is fine. At full charge, the phone powers up and immediately enters the endless boot cycle I previously described.
As soon as the phone shows the TWRP boot screen, the phone reboots again. I cannot do anything at all with TWRP. As I previously wrote, I have even tried using adb to force a reboot into fastboot while the TWRP boot screen shows for that split second (the PC momentarily recognizes the USB Android device). Unfortunately , TWRP reboots the phone too quickly.
Click to expand...
Click to collapse
Boot into boot loader by holding volume down and pushing in cable when huawei logo shows, I can tell you now its a bar-steward and may take many times before it actually does it !
---------- Post added at 02:53 PM ---------- Previous post was at 02:52 PM ----------
swukjay said:
Boot into boot loader by holding volume down and pushing in cable when huawei logo shows, I can tell you now its a bar-steward and may take many times before it actually does it !
Click to expand...
Click to collapse
If that doesnt work use e-recovery to restore phone and recovery to stock
---------- Post added at 03:07 PM ---------- Previous post was at 02:53 PM ----------
This may help https://forum.xda-developers.com/mate-8/general/fastboot-erecovery-recovery-upgrade-mode-t3543441
GOOD LUCK !
swukjay said:
Boot into boot loader by holding volume down and pushing in cable when huawei logo shows, I can tell you now its a bar-steward and may take many times before it actually does it !
If that doesnt work use e-recovery to restore phone and recovery to stock
Click to expand...
Click to collapse
Thanks, I just spent the another hour trying to enter Fastboot and eRecovery modes, and I must be missing something! At this point, no matter which button combination I press, I can't seem to affect the boot cycling of the phone (between TWRP and Honor boot screens).
Maybe relevant, but I am unable to even turn off the phone, it won't stop the alternating boot loop -- I don't believe in coincidences, but perhaps the power button just died? I had one Nexus 5 that started bootlooping because of the power button issue, but that was a very different behaviour than this -- the Honor deosn't get as far as booting to the OS.
GOOD LUCK !
Click to expand...
Click to collapse
Thank you, looks like I'll need some! Will update if I can figure out a way out...
pet_zeus said:
Thanks, I just spent the another hour trying to enter Fastboot and eRecovery modes, and I must be missing something! At this point, no matter which button combination I press, I can't seem to affect the boot cycling of the phone (between TWRP and Honor boot screens).
Maybe relevant, but I am unable to even turn off the phone, it won't stop the alternating boot loop -- I don't believe in coincidences, but perhaps the power button just died? I had one Nexus 5 that started bootlooping because of the power button issue, but that was a very different behaviour than this -- the Honor deosn't get as far as booting to the OS.
Thank you, looks like I'll need some! Will update if I can figure out a way out...
Click to expand...
Click to collapse
Sound to me like you flash Non VOLTE firmware on a Volte enabled modem thats causing the boot loop, the best course of action is to restore using e-recovery, that uses a separate recovery partition so hopefully wont boot loop, remember it may take a few times to boot and you must use a usb lead that is connected to a computer, a usb charger WILL NOT DO IT !
When it boots to e-recovery select download latest firmware, you will need to connect to wifi, just follow instructions and let it restore
pet_zeus said:
Thank you, looks like I'll need some! Will update if I can figure out a way out...
Click to expand...
Click to collapse
Erecovery should work, connect your USB to a computer and volume down + power
Another new user who posts when he has a problem and doesn't reply with an update as to what solution solved his problem, this constantly winds me up, new users who do this and dont update the thread should be kicked off
SOLVED!
Sorry for the delay of the update--I got busy and left my phone to collect dust for a while.
The ONLY solution that actually worked was to rip the phone apart and physically disconnect the battery ( !! ). Then, reconnecting the battery while holding down [Power] and [Vol -] got me into fastboot recovery, as per instructions in this thread (I had to avoid booting normally, or into recovery -- TWRP -- since either would put the phone back into the bootloop):
​https://forum.xda-developers.com/honor-5x/how-to/guide-entering-fastboot-using-key-t3400869
After that, it was smooth sailing; I was able to kill TWRP by flashing RECOVERY.img that I extracted from stock B140 image (using Huawei extractor https://forum.xda-developers.com/showthread.php?t=2433454), then force-update to stock B331, then latest TWRP and LineageOS. One hiccup: for whatever reason, I needed to do a factory reset/wipe in TWRP before it would flash LineageOS without giving error 7, despite the fact that I had just flashed the stock image.
Thank you all for your help and input!