[solved] stucked to the bootloader after installing lineageOS image - Wileyfox Swift

After a strange crash of my system, I intended to install lineageOS.
I downloaded the last version of twrp for my device (dl.twrp.me/crackling/) and flashed it sucessfully.
I downloaded the last lineageOS release for my device (download.lineageos.org/crackling) and pushed it successfully.
But after installing the OS from the zip, the phone reboots and gets stucked to the bootloader, without running the OS.
I noticed that the secure boot is enabled, as shown on the picture. (trentesaux.fr/IMG/wileyfox_bootloader.jpeg)
It is the first time I do such things on a smartphone and I would appreciate some help.
As I just created this account, I am not allowed to post links and I had to perform multiple reCAPTCHA verification and to change my IP adress before posting.
Thanks,
Hugo
[edit]
for some reason, I did not see this post : https://forum.xda-developers.com/wileyfox-swift/help/how-to-fix-swift-able-to-boot-t3727294
which solved my problem.
I hope this will help people who, like me, did not find this post.
[/edit]

Related

[Q] "Decryption Unsuccessful" when installing custom ROM to HTC One X

Hi there, I'm desperately hoping someone can help me with this issue as I have trawled through Google for solutions to no avail
I've followed the tutorials from all the lovely people on these forums to get quite far into installing a custom rom for my HTC One X (XenonHD). Unfortunately I've been greeted with the "Decryption unsuccessful" error which I have discovered to be a very persistent error - where many people have many different solutions for it (none have worked for me ) I'm greeted with a password box, and no matter what I type into the box over 4 characters long it says:
Code:
Decryption unsuccessful.
The password you entered is correct**, but unfortunately your data is corrupt.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account.
<Reset Phone>
** - It says this regardless of what I type into the password box.
There was no important data on the phone (it's an old phone) so I'm more interested in just getting this custom rom up and running, it doesn't matter to me if I have to wipe data.
Here are the approximate steps I took to reach this position:
Set up bootloader/fastboot
Installed twrp
Wiped the device (cleared every cache etc.)
Copied XenonHD zip and gapps zip on to sd card
Flashed boot.img to the device
Rebooted - XenonHD spinning logo appears, then after about 30 seconds it asks me to enter the password, and I get the Decryption Unsuccessful error.
If you need any more information from me please just ask!
I am so appreciative of how helpful this forum has been to me so far, so I have really high hopes you guys can help me
Just a quick update: I actually managed to install a different rom using the exact same method that I did for Xenon - no signs of the decryption error whatsoever. I'm a noob at this stuff so I'm not really sure of the relevance of this but it sounds like it could be helpful in pointing towards a solution?
Ollie1700 said:
Just a quick update: I actually managed to install a different rom using the exact same method that I did for Xenon - no signs of the decryption error whatsoever. I'm a noob at this stuff so I'm not really sure of the relevance of this but it sounds like it could be helpful in pointing towards a solution?
Click to expand...
Click to collapse
Wich rom you install? The answare will help
I said in my original post which rom I was installing (XenonHD) - but I've actually managed to fix it!
To anyone else who stumbles upon this thread, if you are getting the decryption unsuccessful error you have to format your phone. In my case, it was a case of updating to the latest TWRP which includes a Format option on the wipe screen. This got rid of the encryption on my phone and I was able to use the rom!
Ollie1700 said:
I said in my original post which rom I was installing (XenonHD) - but I've actually managed to fix it!
To anyone else who stumbles upon this thread, if you are getting the decryption unsuccessful error you have to format your phone. In my case, it was a case of updating to the latest TWRP which includes a Format option on the wipe screen. This got rid of the encryption on my phone and I was able to use the rom!
Click to expand...
Click to collapse
Yes offcorce you migrate from old layout to the new leyout the roms for this two layouts are different

OTA update and BOOT LOOP

Hi peeps. Would be glad if you guys can help me... I always get stuck in boot loop after OTA update. I also tired the same via lineage downloader and still the same issue. .. I use and nexus 6.. Pls help me
On a OnePlus 3, since moving to LineageOS 16 I haven't been able to do a single OTA update without any bootloop (it starts with the LineageOS logo, quite fast then Android booting and asking for a password, then LineageOS logo again, for ever until it reboots into recovery). What has saved me is the following:
* from recovery, adb sideload lineageOS, then OpenGapps, then addonSu
* reboot
I guess the OTA update messes up with OpenGapps, leading to this bootloop...
Mathias
i am having a quite similar issue on Oneplus 3T. Is your device encrypted?
The last couple of days i am going insane with boot looping. I noticed that while i have me device not encrypted, ota updates are successful.
But as soon as i encrypt my device and perform an OTA update, all hell breaks loose
Yes, my device is encrypted. But as I've written above, manually flashing through abd sideload both lineageOS and then OpenGapps works. Actually, most probably only reflashing OpenGapps after the unsuccessful update might be enough...
have you ever messed around with "privacy guard"?
Since i am also trying to figure out what is causing the boot loop, i managed to find that messing around with privacy guard settings might lead you to a boot loop.
Source: Privacy Guard - Recover from bootloop
Deleting (or editing according to the information provided in the link) the /data/system/appops.xml might solve this problem.
I will check this out as soon as a new build is available for download.
Wow, great tip and great link! Yes, I did remove some permissions for Google... Exactly what was described in the linked post.

Several issues while trying to root pixel c

Hello, I am in need of assistance on rooting/my pixel C device.
I was trying to follow the steps outlined in this webpage: https://forum.xda-developers.com/pixel-c/general/guide-unlock-bootloader-install-custom-t3307183/page27
The tablet by itself had 8.1 to start out.
The steps I did so far is
1. Successfully unlocked the bootloader (the 30 second boot time and the beeping noise)
2. Installed TWRP
3. Installed superSU via TWRP
4. flashed the AOSP kernel from this link https://forum.xda-developers.com/pixel-c/development/rom-t3569215
5. Upon system reboot, I noticed two issues:
Issue 1: The apps is pretty empty, including no google play store. I am guessing this was by design, to keep things simple. In addition, I think the original author was saying to install opengapps manually.
Issue 2: Every time I boot to system, I get the message "google connectivity service stopped" error in the beginning (that wording might not be precise). I was able to connect to wifi and bluetooth with no problem, but maybe the connectivity service is responsible for something else, and it is concerning.
6. Another thing I noticed is an issue is when I boot back into TWRP, my internal storage is 0mb. In research it sounds like I need to implement some sort of passcode, as it might be due to the internal storage being encrypted (although I didn't set up any manual encryption myself).
However, when I boot back into system and look, there is no way to set up a screen lock passcode. There is a method to encrpyt the tablet data, but I didn't pursue that, because it projected a long wait time. (If this will indeed fix the problem I will do so)
If I format data through the twrp system, the internal storage comes back.
7. Nonetheless, I was hoping I can still navigate through the system if I just install opengapps. Therefore, I went to opengapps.org, and chose the arm64, 7.1 stock file to download, as this was the default choice it offered (and I couldn't find 8.1- please let me know what the correct one to install is)
8. I then used adb sideload to install the gapps. (As I couldn't access the internal storage)
9. Now, when I try to reboot to system, the TWRP recovery keeps on coming up, every time. Essentially a TWRP bootloop.
My wish is to just get back to the stock 8.1 os with root. Even if I go through a format erase on twrp, the aosp design defaults. Maybe it isn't completely erased?
I have been working days and nights. Maybe it is because I am a novice and a total newb on the pixel C, but looking everywhere it shows similar yet different suggestions, and hasn't been giving me what I am looking for.
Any insight/advice you can give me will be greatly appreciated.
Thank you for reading my long post.
I think I found the correct gapps just by a Google search. It is unfortunate that they're not just out there in plain view on the OpenGapps site. So you flashed the 7.1 apps, and did you get an error message while trying to flash them via TWRP?
To be quite honest, I had a lot of difficulty rooting and flashing a ROM on the Pixel C, myself. The process took me a couple days. I really had to play around with the drivers and the SDK...the latest wouldn't install to my computer unless I installed it using Android Studio. Once I finally had everything set up right, which I can't even remember how I had it set up, it worked. One ROM I flashed didn't boot, and the Lineage one did. Now, I'm on Resurrection Remix, my favorite ROM ever! Hope this helps!
---------- Post added at 08:05 AM ---------- Previous post was at 08:03 AM ----------
I found a link for some gapps for you
https://sourceforge.net/projects/unofficial-opengapps-8-1/files/arm64/20180227/
sabrdawg said:
I think I found the correct gapps just by a Google search. It is unfortunate that they're not just out there in plain view on the OpenGapps site. So you flashed the 7.1 apps, and did you get an error message while trying to flash them via TWRP?
To be quite honest, I had a lot of difficulty rooting and flashing a ROM on the Pixel C, myself. The process took me a couple days. I really had to play around with the drivers and the SDK...the latest wouldn't install to my computer unless I installed it using Android Studio. Once I finally had everything set up right, which I can't even remember how I had it set up, it worked. One ROM I flashed didn't boot, and the Lineage one did. Now, I'm on Resurrection Remix, my favorite ROM ever! Hope this helps!
---------- Post added at 08:05 AM ---------- Previous post was at 08:03 AM ----------
I found a link for some gapps for you
https://sourceforge.net/projects/unofficial-opengapps-8-1/files/arm64/20180227/
Click to expand...
Click to collapse
Hi, I have a suggestion for ya, You can either flash your tablet with the stock rom : https://developers.google.com/android/images , change the recovery to twrp and root your system with supersu Or you can install lineage 15.1 (oreo) + opengapps oreo 8.1 + supersu/magisk15 don't forget to change the vendor image and the boot image also if you want to have access on your internal storage on twrp. Hope that it will help you.
Thanks guys. Since this time, I was able to try different things and was able to get things rooted and erased using a combination of twrp and the original stock rom.
However, during this process, the TWRP recovery was overwritten with the stock one, and when I try to re-flash the twrp recovery using adb (at the Fastboot, using command: Fastboot flash recovery twrp.img ), command line just stalls with no progress.
Has anybody else encountered this before? Any way to re-flash the twrp file? thanks in advance.

Can someone give me the easy, simplified version on how to install Lineage (PH-1)?

First off, sorry if this has been asked or covered before. I made my account just yesterday simply to post this topic.
I have no experience with rooting or installing a different OS on phones, but decided to try with my backup Essential.
So far I've unlocked the bootloader using Fastboot and ADB, but can't seem to get Lineage installed correctly. I've flashed twrp but after being in recovery mode and trying to flash the latest image and Lineage OS, it won't seem to boot out of the bootloader screen.
This has happened twice and both times have been able to wipe it from recovery and go back to stock Essential, thankfully. But I don't know where I'm going wrong. Maybe I don't have the latest image or Lineage zip folder? What partition should I install on?
I've even tried using fastboot -w to wipe my phone and it won't wipe it. I can't remember exactly what cmd says but it's something about not finding user data, I think?
I've watched YouTube videos on how to do it, and the videos I saw referenced the thread made by the user invisiblek.
I also read his post specifically and there is still something that I'm missing.
After having reset my phone twice and get it stock and up and running, I'm on the official Essential build OPM1.180104.14
Could anyone with some knowledge help a newbie?
edit: got it working!

[FP3] Decrypt data in recovery after bootloop

Hello !
I’ve made a little mistake.
This year, I’ve installed LineageOS for MicroG on my Fairphone3. It provides OTA updates but with the last one, it is said I must follow the official instructions on LineageOS website. It was not a prioritiy, so I didn’t do it. At the begining of the month, I’ve open the web page and read the instructions. There are simple, so i’ve done it.
But, I’ve forgotten that my version was MicroG. I’ve installed the “normal” version (lineage-19.1-20220926). Now, my FP3 is in a bootloop . May be due to the absence of MicroG). I’ve tried to install a newer version of LineageOS for MicroG, without success.
My problems are :
I would like to retrieve data
Data directory is encrypted
I’ve locked my phone with a pattern
I’ve found a solution to try a decrypt with Santoku Linux. The script needs a header and a footer. I have found the header but not the footer.
Do you know where to find it ? It seems these files are different according to the manufacturer.
Up ^^
Hi, did you solve your problem?
On my main phone that was on LOS 19 microG, I dirty flashed LOS 20 microG that just went out (https://download.lineage.microg.org/builds/full/FP3/lineage-20.0-20230403-microG-FP3.zip). The reboot went smoothly. The install of updated apps through Aurora would fail every time.
So I went for a reboot, and alas, the animated LOS logo stays forever, and sometimes it reboots. Reapplying the upgrade doesn’t fix anything. Any idea of what could be wrong? Is there any way to revert to a functioning phone?

Categories

Resources