Lineage OS 7.1.2 SuperSu Secure Boot Error [SOLVED] - G3 Q&A, Help & Troubleshooting

SOLVED!
So, after just giving up and moving on to another project of trying to flash the ARTX Kernel which didn't work (I'll update this if I find out why it's not working; my phone restarts when im flashing the zip and "2013-2015 [somename ] amurlle.com" pops up in log.) so I researched and found a zip called MrBump.zip which bumps your boot image to get rid of the secure boot check.
How to
Flash SuperSu v2.82.zip via TWRP and then flash MrBump.zip, the phone will reboot after flashing MrBump and then another time for finishing the SuperSu installation.
History
\\
So, I have recently updated from Cyanogenmod 13 to Lineage OS 14.1 as it's faster, pretty, and Xposed was recently released for Nougat.
Installing Lineage wasn't a problem nor Gapps or the su add on package from Lineage which unlocks the OS's own su management service.
I wanted to use SuperSu as it pretty, customization, and better privilege management compared to the option lagging 'Privacy Guard' Lineage uses.
So, I flashed the SuperSu v2.82 zip which gave me a "Secure Boot Error" when rebooting into the system. No partitions seemed to be corrupted or damaged but I assumed
it had to do with the boot.img file as I saw supersu patch the boot image for some stuff I don't know. I decided to research and get my team of arduino super AI's to find
something of an answer of how to fix my problem, stumbling upon an article on XDA from chainfire of a boot image signer. I used Cywgin to create an rsa key and signed my boot image
then figuring out I could use the "BootSigner.zip" to sign the boot image without me creating a rsa key, flashing the zip nothing changed just some other error of where it couldn't read
boot image or the boot image was misdirecting to the system. I then tried fastbooting the signed boot image I made, it didn't work giving me some other ****ty error of mutiny.
I then fastbooted the orginal unsigned boot image I took from my ROM which worked but when booting into the OS SuperSu was still not the active su manager.
I then gave up and am now writing this post in a last option of getting SuperSu on my phone.
I have tried SuperSu 2.78 and kingoroot from the PC hoping that I could then use SuperSuMe
//
Details of my device
\\
LG G3 D855
ARM
Lineage OS 14.1 (20170724)
Gapps 7.1 Micro (20170728)
TWRP 3.1.1-0
//
1 second after turning on the phone the error pops up (the LG logo is visible when the log is onscreen):
ERROR : boot certification verify
[640] --------------------------------------------------
[640]
[640] Secure boot Error!
[640] Cause: boot certification verify
[640]
[640] ---------------------------------------------------
2 seconds later the screen blanks and the LED on my phone blinks blue and red at half second intervals.
Any help would be appreciated, if you need any specifics of my device or screenshots just ask (I can replicate my problems and steps iv'e done if you need me to.)

Eureka!
I did the exact same thing and all the guides that I found assumed that you still had access to the system or had already wiped out download mode. There is a lot of advice out there that really just doesn't work. Anyway, I gave up and decided to do a wipe with suprising results.
boot to stock recovery by holding power+volume down
perform factory reset
phone reboots to TWRP - WHY?!?! I have no idea, but it worked
reinstall your latest lineage image from /data/data/org.lineageos.updater/app_updates/
wipe davlik/cache + reboot
profit!
I don't know why this worked and I stumbled upon this by accident.
Mileage may vary, so please share your results.

XtatX said:
I did the exact same thing and all the guides that I found assumed that you still had access to the system or had already wiped out download mode. There is a lot of advice out there that really just doesn't work. Anyway, I gave up and decided to do a wipe with suprising results.
boot to stock recovery by holding power+volume down
perform factory reset
phone reboots to TWRP - WHY?!?! I have no idea, but it worked
reinstall your latest lineage image from /data/data/org.lineageos.updater/app_updates/
wipe davlik/cache + reboot
profit!
I don't know why this worked and I stumbled upon this by accident.
Mileage may vary, so please share your results.
Click to expand...
Click to collapse
What?
You must've flashed TWRP before, and I don't understand what you mean here. Did you brick your phone trying to flash SuperSu too?
But i'm glad it worked out for you

Bump!

Saterlite said:
What?
You must've flashed TWRP before, and I don't understand what you mean here. Did you brick your phone trying to flash SuperSu too?
But i'm glad it worked out for you
Click to expand...
Click to collapse
Yeah, I had TWRP on it before and got to that point by trying to flash SuperSU on an already installed copy of Lineage. I was really trying to revert to stock and start over when TWRP came up.

Related

V500 secure booting error

Hi guys,
For now I'm stuck on this error on updating to LineageOS (official repo). "secure booting error" me checked!
I used to do a clean Install nothing more than this. Only if things will load I flash GAPPS etc.*
Previously I've successfully flashed cm13 and cm14.1 and so on.
But sometimes I got the "secure booting error"
When flashing (custom) kernels I always get the "secure booting error".
On flashing roms sometimes it does sometimes it won't.
I'm not sure when or what went wrong or not.
I've never had issues to access twrp or flash twrp. Like I see on most topics.
So I'm pretty sure the problem exist in my bootloader.and not in the roms or other flashing. Maybe it isn't fully unlocked?
My LG G Pad 8.3 (v500) bought in The Netherlands.
I flashed V50020F Bootloader: https://www.androidfilehost.com/?fid=24352994023707804.
Flashing all went fine as far as tarp gives the right info. I only don't know how to check this.
TWRP: 3.0.x
Is there guide de to fix this? I've really spend days on this without any solution. It's really frustrated!
Hmm.. Same issue here.
Was on stable CM 14.1 & TWRP 3.0.2.0.
Flashed TWRP 3.0.2.2
Flashed Lineage experimental 14.1 & supersu addon zip
Rebooted and am stuck with the same secure boot error. I don't understand why I can't get into the same TWRP recovery I was just in to attempt to clean flash a nightly LineageOS 14.1.
------------
Here we go: https://forum.xda-developers.com/showpost.php?p=70740190&postcount=84
Follow those steps to get into TWRP.
Xenosis said:
Hmm.. Same issue here.
Was on stable CM 14.1 & TWRP 3.0.2.0.
Flashed TWRP 3.0.2.2
Flashed Lineage experimental 14.1 & supersu addon zip
Rebooted and am stuck with the same secure boot error. I don't understand why I can't get into the same TWRP recovery I was just in to attempt to clean flash a nightly LineageOS 14.1.
------------
Here we go: https://forum.xda-developers.com/showpost.php?p=70740190&postcount=84
Follow those steps to get into TWRP.
Click to expand...
Click to collapse
Don't use supersu with cm/lineage.
The secure boot error can be fixed by flashing this zip in recovery.
https://www.androidfilehost.com/?fid=95916177934554766
Thanks. Ya I had no idea there was a set of flashable su's for LineageOS in Extra.
Got it working. The issue was mostly that I had no idea how to use the hardware buttons for this tablet to get into recovery.
Thanks that helped me out!!
My Problem:
Lineageos 14.1 and Magisk 17.1 installed, updated Lineageos to actual nightly and got a
Secure booting error, Cause : boot certification verify
Solved with:
Boot into recovery mode with TWRP installed
Howto here: https://youtu.be/uo3YfszOPsQ
Than installed: v500-loki-kernel-to-bumped-kernel-signed.zip
Here is the proper thread with backround information
https://forum.xda-developers.com/showpost.php?p=60092491&postcount=1
Fixed it. Great job
[V500] "Secure Booting Error..." solution howto
Let me recap here, 'cause I get trapped in this issue every other year and it takes me a while to retrace back the steps for the solution.
Some intro, for starters: I have been running Lineage OS on my device for years and, at first, whenever I had this, I had to get the LG Mobile Tool plus the full factory ROM to do a KDZ restore -- i.e., start everything from scratch.
There's zero need to do that -- if you had a working TWRP recovery and Android system before, both will still be fully functional after you overcome this problem!
First: you have to get back into TWRP.
This is the hardest part because not only the key press sequence is rather uncommon, you have very little time to get through it, too.
In short, you have to press VOL DOWN + POWER keys until you get the LG logo.
Then you have to quickly release and press all three keys (VOL DOWN + VOL UP + POWER), before the "Secure Boot" error message comes up.
Second: What comes up doesn't make a lot of sense, too: you're dropped in the "Factory Reset" screen.
You'll have to press POWER twice to confirm -- never mind the dire warnings -- to get back into TWRP.
Try again if you don't succeed or check the YouTube video pointed above by HerrRuin good to see how it's done.
Third: once in TWRP, it gets easy.
Download the bumped bootloader from AndroidFileHost, also pointed by HerrRuin above.
(FTR, file name is 'v500-loki-kernel-to-bumped-kernel-signed.zip'; MD5 is 'f1a25de31559462d8c5d4c35d23f84d9')
While still in TWRP, connect the tablet to your computer and transfer the file over.
After the file is copied, flash it via the "INSTALL" button, reboot, and "Bob is your uncle"... :laugh:​
Many thanks to everyone who contributed to this solution that allows me to keep enjoying my G Pad after so many years.

Stuck on team win recovery project please help

I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....
Did you buy the phone second hand or did you try to flash TWRP yourself? It shouldn't have TWRP installed by default.
Regardless, you can use TWRP to flash the latest update.
Given that you have TWRP, I'm assuming that you have an unlocked bootloader. Did you notice a warning pop up everytime you reboot your phone before? It should say something along the lines of "your device has been unlocked and can't be trusted". If not, you'll have to unlock it (it wipes your phone in the process).
If the bootloader is unlocked, you can simply download and flash the latest zip for OOS 4.0.3 in TWRP. This will update you phone and replace TWRP with the stock recovery (so you don't run into this problem again in the future when installing an OTA). If you don't intend to modify your phone in any way, then this is all you need to do, your phone should be functional.
There are plenty of threads with detailed guides on how to do all of this.
I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please
sndr1384 said:
I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please
Click to expand...
Click to collapse
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.
This is issue of using a faulty twrp so for that when ur phone us booting up go to fastboot and flash twrp 3.0.4-1 and everything will work
emuandco said:
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.
Click to expand...
Click to collapse
Similar Problem here:
just wanted to flash latest OOS 4.0.3, so I flashed back stock recovery with flashify and rebooted into recovery mode to flash the already downloaded OOS 4.0.3. zip. That's when it began to go poop! After rebooting it just went dark with no Chance to power it on again! No dice with power button, Volume up/down + power button, nothing! Not even the LED's are blinking when plugged in. So this one seems to be basically dead!
I got it once booting again after randomly pushing the buttons (after x minutes!?), but everytime I reboot the phone it just shuts off without beeing able to power it on again. At the Moment it's dead!
Any ideas what might happened? If I get it on again, should I immediately reset it to factory Settings?
I am kinda lost here! Any help/ideas would be much appreciated!
Flashify? Never used it and never trusted apps which flash stuff on a running system. Use fastboot and reflash the recovery partition. Link to recovery is in my former post.
fastboot flash recovery PATHTOIMGFILE
Thank you for your advice! Still a lot to learn! Got it up again, will try as you suggested!
It appeared that my stock recovery file was corrupted , but all is fine again! Thank you very much!
Mannycolon85 said:
I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....
Click to expand...
Click to collapse
I may have been the person you traded with to get the OnePlus 3, but I took the phone back and after 5 hours I got it up and running.
The phone would boot to TWRP, but even after wiping the entire system and dragging a ROM zip to the internal storage, reinstalling did nothing. It just kept booting back to recovery.
The solution entailed the following.
Download stock recovery IMG. Flashed through TWRP. Rebooted recovery and now was back to stock recovery.
Download the official OxygenOS ROM zip from the OnePlus website and changed the name to update.zip
Next I downloaded Android studio for access to ADB. I had never used ADB before, but I knew this was needed to push a file to the phone.
Needless to say, ADB kept freezing my computer when I would type in the commands to side load.
I deleted Android studio and installed a minimal ADB/Fastboot I found online. I opened my command prompt, typed the command for sideloading, and immediately got my installation starting. It took about 10 minutes to fully install. When it was finished, I rebooted and had a fully functioning OnePlus 3
Sent from my ONEPLUS A3000 using Tapatalk

Bricked(?) Mi 9 SE - I need help

Hey there xda,
so long story short, I'm an idiot.
First of all, what I did in order.
1. Unlocked my bootloader via the Mi Unlock tool
2. Installed TWRP
3. Installed Magisk (latest)
4. Installed a Magisk module called PIXELARITY and rebooted my phone (this is where the problems started)
5. I got into a loop, the only thing I was able to boot was the TWRP recovery
6. I tried to uninstall PIXELARITY Magisk module, with no success, still the same problem
7. I decided to do a factory reset, maybe that will help. It didn't, same issue.
8. I decided to do a complete wipe. EVERYTHING. I wanted to reflash a completely new ROM to solve my issue with the recovery loop. After the wipe, I've restarted my phone (even when TWRP asked if I want it, because I have no OS)
9. We are here, I have a Mi 9 SE without OS, can't boot into recovery, and the only thing I can reach is fastboot (can't even turn off my phone, though)
What I have tried.
1. Tried to flash TWRP via fastboot (since fastboot is my only option), the flashing itself looks fine, everything says OK, but I can't boot into recovery mode (it says Failed to load/authenticate boot image: Load Error)
I don't know what else could I do, to be honest, I'm absolutely not an expert of this stuff, I just wanted to root my phone to actually use some userland-unavailable features, but looks like I've f.ed it up really hard.
Do I have any option at this point? Or do I have to dump my phone, and buy a new one?
Any advice is appreciated.
xHeaven said:
Hey there xda,
so long story short, I'm an idiot.
First of all, what I did in order.
1. Unlocked my bootloader via the Mi Unlock tool
2. Installed TWRP
3. Installed Magisk (latest)
4. Installed a Magisk module called PIXELARITY and rebooted my phone (this is where the problems started)
5. I got into a loop, the only thing I was able to boot was the TWRP recovery
6. I tried to uninstall PIXELARITY Magisk module, with no success, still the same problem
7. I decided to do a factory reset, maybe that will help. It didn't, same issue.
8. I decided to do a complete wipe. EVERYTHING. I wanted to reflash a completely new ROM to solve my issue with the recovery loop. After the wipe, I've restarted my phone (even when TWRP asked if I want it, because I have no OS)
9. We are here, I have a Mi 9 SE without OS, can't boot into recovery, and the only thing I can reach is fastboot (can't even turn off my phone, though)
What I have tried.
1. Tried to flash TWRP via fastboot (since fastboot is my only option), the flashing itself looks fine, everything says OK, but I can't boot into recovery mode (it says Failed to load/authenticate boot image: Load Error)
I don't know what else could I do, to be honest, I'm absolutely not an expert of this stuff, I just wanted to root my phone to actually use some userland-unavailable features, but looks like I've f.ed it up really hard.
Do I have any option at this point? Or do I have to dump my phone, and buy a new one?
Any advice is appreciated.
Click to expand...
Click to collapse
Did you flash vbmeta with fastboot?
Rostbraten said:
Did you flash vbmeta with fastboot?
Click to expand...
Click to collapse
I didn't, but looks like I solved my own question, though. I found an article here: getdroidtips.com/guide-flash-miui-rom-xiaomi-devices/#How_to_Flash_Xiaomi_Firmware_using_Fastboot, I did everything as it says, and it worked. Already reinstalled Magisk, though.
Thanks, anyway! Sorry for opening a thread for this (I was pretty desperate), and hopefully the above link can help other users like me, who were kinda careless about what they do.

Unable to boot phone once TWRP installed?

Hey guys,
So I've been trying for days to get a custom Ron installed on N975F.
Right now I'm on completely reflashed stock Rom. With stock recovery et al. No root.
I am able to flash Magisk with Odin. No trouble. And my phone continues as usual without issue.
However, once I install TWRP, no matter where or how I install it, once I restart my phone it will boot past the warnings without issue, then go to the screen that just says "SAMSUNG" and the phone will never actually boot up.
I can still boot into TWRP recovery without issue, but system itself will never boot, it will just sit on the "SAMSUNG" screen forever.
In fact, it seems like as long as TWRP is installed to recovery, my system will never boot with any Rom. It can be fixed by reinstalling stock recovery, or by reflashing stock in it's entirety (which I have now done before I try again).
Has anyone got any ideas why this might be occurring or how I can address it? I saw some threads about 'rollback protection' but it seems like that is for people who are not even able to boot into TWRP, or get stuck on the first "Samsung Note 10+", screen rather than the system booting "SAMSUNG" screen.
KiwiNote+ said:
Hey guys,
So I've been trying for days to get a custom Ron installed on N975F.
Right now I'm on completely reflashed stock Rom. With stock recovery et al. No root.
I am able to flash Magisk with Odin. No trouble. And my phone continues as usual without issue.
However, once I install TWRP, no matter where or how I install it, once I restart my phone it will boot past the warnings without issue, then go to the screen that just says "SAMSUNG" and the phone will never actually boot up.
I can still boot into TWRP recovery without issue, but system itself will never boot, it will just sit on the "SAMSUNG" screen forever.
In fact, it seems like as long as TWRP is installed to recovery, my system will never boot with any Rom. It can be fixed by reinstalling stock recovery, or by reflashing stock in it's entirety (which I have now done before I try again).
Has anyone got any ideas why this might be occurring or how I can address it? I saw some threads about 'rollback protection' but it seems like that is for people who are not even able to boot into TWRP, or get stuck on the first "Samsung Note 10+", screen rather than the system booting "SAMSUNG" screen.
Click to expand...
Click to collapse
i am guessing try ADB commands see this link! https://www.koskila.net/how-to-use-twrp-to-flash-an-android-device-that-refuses-to-boot-to-twrp/
Many N975 users have reported this issue and I have forwarded concerned to ian as well. What I believe is formatting on latest (last few) twrp causing issue.
If you have N975/N976 then, visit xda My rom thread - Download area - you will find a folder "for stock rom & bootlooped device" download instructions and follow it, I have wrote guide with or without flashing my rom
Edit :
here is direct link, you will find all required file
https://www.mediafire.com/#0urfw8g1gx630
This guide is stop solution to root/root with twrp/fix Samsung roll back bootloop everything. And yes you don't needs to patch anything yourself, all files available are ready to use
Hi Dr Ketan,
Thanks for the response.
I actually solved the issue simply by using the version of TWRP and following the install instructions on your basic "How to Root and Install TWRP" for Note 10+ guide.
So I think this is a problem relating to Ian's latest TWRP. TWRP linked from your thread
is working fine (but leads to issue with Camera in GSI/Lineage OS ROMs).
I will have a look at your special guide relating to Samsung logo/rollback stuff and see if it will allow me to install latest TWRP from Ian and bypass these issues! Thank you.
KiwiNote+ said:
Hi Dr Ketan,
Thanks for the response.
I actually solved the issue simply by using the version of TWRP and following the install instructions on your basic "How to Root and Install TWRP" for Note 10+ guide.
So I think this is a problem relating to Ian's latest TWRP. TWRP linked from your thread
is working fine (but leads to issue with Camera in GSI/Lineage OS ROMs).
I will have a look at your special guide relating to Samsung logo/rollback stuff and see if it will allow me to install latest TWRP from Ian and bypass these issues! Thank you.
Click to expand...
Click to collapse
Yes, As I said issue is related to newer TWRP only. If you use old TWRP, camera will not work. My above link guide is for latest base and you can get latest TWRP only (Included package are having latest available TWRP & Kernel)

TWRP for Sony XZ2c instead of Lineage Recovery?

Hi everyone
After some research, I can't find a succeful way to install TWRP recovery instead of Lineage stock recovery.
It's really embarasing because I'm currently setting up my brand new XZ2c compact to run the way I want it to on Lineage OS 17.1 with Magisk and Xposed modules, and I experienced 3 or 4 endless bootloop that led me to fully format my phone after bunch of hours setting it and tailoring it up... Huge waste of time, frustration overload, as you could expect. So, I really miss tremendous TWRP backup fonctionnality I used to run frequently on my old Z5c... :crying:
Does anyone here as figured out how to replace Lineage stock recovery on this device? Is so, I'd really to hear him out
Have a good week-end!
tomboudiboudi said:
Hi everyone
After some research, I can't find a succeful way to install TWRP recovery instead of Lineage stock recovery.
It's really embarasing because I'm currently setting up my brand new XZ2c compact to run the way I want it to on Lineage OS 17.1 with Magisk and Xposed modules, and I experienced 3 or 4 endless bootloop that led me to fully format my phone after bunch of hours setting it and tailoring it up... Huge waste of time, frustration overload, as you could expect. So, I really miss tremendous TWRP backup fonctionnality I used to run frequently on my old Z5c... :crying:
Does anyone here as figured out how to replace Lineage stock recovery on this device? Is so, I'd really to hear him out
Have a good week-end!
Click to expand...
Click to collapse
You don't install a recovery, but only temporally boot one
https://wiki.lineageos.org/devices/xz2c/install
kurtn said:
You don't install a recovery, but only temporally boot one
https://wiki.lineageos.org/devices/xz2c/install
Click to expand...
Click to collapse
Thanks for replying!
Ok, but if I want this recovery bootable permently away from my computer?
kurtn said:
You don't install a recovery, but only temporally boot one
https://wiki.lineageos.org/devices/xz2c/install
Click to expand...
Click to collapse
Thanks for your (minimalist) advice. Literally just lost 1 hour fixing the bootloop it just caused by following it, I'm delighted.
Behind my post, I was hoping to find someone who could explain a bit more the process of replacing/flashing/booting/(wateveryouwanti'mnotanexpert) a recovery, and at the same time avoiding me wasting more hours in bootlooping/formating/reinstalling. Hopefully, this time I succeed to came out of the bootloop without formating and reseting eveything, but I almost lost my nerves.
All of this is a bit cloudy for me, could you (or someone else that would give me a little of his time to) be pedagogue and explain clearly the whole proccess (and especially what you should avoid if you don't want to get stuck in a bootloop/getting scarying corrupted device message) ?
No one?
tomboudiboudi said:
No one?
Click to expand...
Click to collapse
Wrong forum. Search in you device section.
Hi guys!
Today I tried again to install TWRP on my Sonyh Xperia XZ2C because LineageOS Recovery doesn't provide Nandroid backup, which is a shame.
I tried many ways described over the web, none of those worked, and I ended up with a boot loop at startup with that naughty message "your device is corrupted it cannot be trusted and will not boot". I can't boot to Lineage, neither to recovery. I'm stuck.
With device turned off, I can eventually press volume down, plug it to computer, access fastboot mode (blue led), flash+boot the LineageOSrecovery.img, then the device restart, Sony logo appears... and that's all, I'm stuck with logo in boot loop, and I can't go anywhere further.
I tried to change boot slot (without knowing if it could help with this problem at all) but I alway get "unknown option".
I'm panicking right now, I can't find any way out to this bootloop, if someone could help it will be sooo appreciated!
I tried hard to find a solution for 4 hours now, I'm completly stuck and I can't even sleep. That's why I finally reached out here.
tomboudiboudi said:
Hi guys!
Today I tried again to install TWRP on my Sonyh Xperia XZ2C because LineageOS Recovery doesn't provide Nandroid backup, which is a shame.
I tried many ways described over the web, none of those worked, and I ended up with a boot loop at startup with that naughty message "your device is corrupted it cannot be trusted and will not boot". I can't boot to Lineage, neither to recovery. I'm stuck.
With device turned off, I can eventually press volume down, plug it to computer, access fastboot mode (blue led), flash+boot the LineageOSrecovery.img, then the device restart, Sony logo appears... and that's all, I'm stuck with logo in boot loop, and I can't go anywhere further.
I tried to change boot slot (without knowing if it could help with this problem at all) but I alway get "unknown option".
I'm panicking right now, I can't find any way out to this bootloop, if someone could help it will be sooo appreciated!
I tried hard to find a solution for 4 hours now, I'm completly stuck and I can't even sleep. That's why I finally reached out here.
Click to expand...
Click to collapse
In fastboot mode you should be able to flash stock rom
Is there any way to make the device boot on the Lineage partition without wiping everything?
For an unknown reason, I succed to boot on Lineage Recovery (not TWRP) this morning. I flashed LineageOs rom.zip using adb sideload. After rebooting, the recovery tolds me that I had to wipe everything because the system partition seems to be corrupted, so I did.
I'm a bit tired to lost everything since I made all of this to do Nandroid backups with TWRP........ but I have a fresh new install, my phone works again so it's fine.
But I still need to make Nandroid backups.
Kurtn, you seem to have skills and knowledge. As you can see, I didn't succeed to boot Twrp since october 2020. I don't see why it would be impossible with my device, I'm probably messing something somewhere.
Would you share your knowledge and help me booting/flashing TWRP without bricking everything again?
Could you make an answer instead of a single smiley?
tomboudiboudi said:
Could you make an answer instead of a single smiley?
Click to expand...
Click to collapse
Sorry, i cant. I don't backup and I don't have an a/b device.
Ok, thanks anyway!
tomboudiboudi said:
I didn't succeed to boot Twrp since october 2020. I don't see why it would be impossible with my device, I'm probably messing something somewhere.
Would you share your knowledge and help me booting/flashing TWRP without bricking everything again?
Click to expand...
Click to collapse
Btw.
Code:
fastboot flash boot recovery.img
DOES install the recovery, since it's permanently flashed. Don't know why they (lineage) didn't change that.
kurtn said:
You don't install a recovery, but only temporally boot one
https://wiki.lineageos.org/devices/xz2c/install
Click to expand...
Click to collapse
However @tomboudiboudi , you could boot twrp manually using
Code:
fastboot boot twrp.img
With that, twrp should appear and ask for a password to decrypt your userdata partition.
If that works, you could try to flash boot this very same twrp.img. Maybe you need an additional twrp.zip too which will be sideloaded within twrp itself.
A note for you which might help: I wanted to update my lineage recovery manually using fastboot (older lineage recovery to newer one) and found that nothing (except fastboot) was booting at all after flashing this.
However, after dirty flashing lineageOS.zip, everything worked fine again.
Keep in mind that flashing a recovery will modify your boot.img. If this one doesn't work / is corrupt etc., your os won't boot up.
User699 said:
Btw.
Code:
fastboot flash boot recovery.img
DOES install the recovery, since it's permanently flashed. Don't know why they (lineage) didn't change that.
However @tomboudiboudi , you could boot twrp manually using
Code:
fastboot boot twrp.img
With that, twrp should appear and ask for a password to decrypt your userdata partition.
If that works, you could try to flash boot this very same twrp.img. Maybe you need an additional twrp.zip too which will be sideloaded within twrp itself.
A note for you which might help: I wanted to update my lineage recovery manually using fastboot (older lineage recovery to newer one) and found that nothing (except fastboot) was booting at all after flashing this.
However, after dirty flashing lineageOS.zip, everything worked fine again.
Keep in mind that flashing a recovery will modify your boot.img. If this one doesn't work / is corrupt etc., your os won't boot up.
Click to expand...
Click to collapse
I fear you still haven't realized, what a/b means. The classic concept of having a recovery partition, where you can boot twrp at any time - doesn't apply.
kurtn said:
I fear you still haven't realized, what a/b means. The classic concept of having a recovery partition, where you can boot twrp at any time - doesn't apply.
Click to expand...
Click to collapse
You're right, there is no recovery partition.
As I said: Flashing a recovery.img will modify the boot.img.

Categories

Resources