HI!
Today I upgraded my Swift to Version of 5th october.
Then I tried to do the encrytion. Phone booted and showed a black screen after LineageOS-Logo. Every now and then there was back button flashing at left bottom . After some minutes the phone went to Recovery. I booted to OS and encrytion was not there.
Try to use the TWRP version from the LineageOS wiki and not the official one.
https://wiki.lineageos.org/devices/crackling/install
zomgzerg said:
Try to use the TWRP version from the LineageOS wiki and not the official one.
https://wiki.lineageos.org/devices/crackling/install
Click to expand...
Click to collapse
Good hint, I will try that...
Same problem.
this helped:
https://gitlab.com/LineageOS/issues/android/issues/10
Related
Hello,
I flashed a CustomROM and gapps, tried to reboot into system, but my phone does not react anymore since that attempt. The screen is black.
ROM: http://forum.xda-developers.com/mi-max/development/rom-cm13-unoficial-2016-06-14-universal-t3473016
Gapps: core package from 07-16-16 (arm)
Is there a way to recover it?
Tsd560ti said:
Hello,
I flashed a CustomROM and gapps, tried to reboot into system, but my phone does not react anymore since that attempt. The screen is black.
ROM: http://forum.xda-developers.com/mi-max/development/rom-cm13-unoficial-2016-06-14-universal-t3473016
Gapps: core package from 07-16-16 (arm)
Is there a way to recover it?
Click to expand...
Click to collapse
You have hydrogen or helium?
Which TWRP image did you install exactly?
My device is a Helium 64-3GB bought in China (June/16)
Recovery was flashed using Flasher Toolkit from "en.miui.com" -> /thread-301971-1-1.html
(Link not allowed)
file name: "twrp-3.0.2-2-hydrogen"
I remember that I might have seen Hydrogen in the text box during installation, if you aim on the detection during the installation.
Tsd560ti said:
My device is a Helium 64-3GB bought in China (June/16)
Recovery was flashed using Flasher Toolkit from "en.miui.com" -> /thread-301971-1-1.html
(Link not allowed)
file name: "twrp-3.0.2-2-hydrogen"
I remember that I might have seen Hydrogen in the text box during installation, if you aim on the detection during the installation.
Click to expand...
Click to collapse
Yeah... Wrong recovery and the install detected your helium as hydrogen leaving you a brick.
My bad... I just added the warning about that in the thread after seeing your question... Should of thought about this scenario but since we have helium twrp for a long time now I I assumed nobody is isuing hidrogen... I knew what you did just wanted to make sure.
Never been in a brick myself but read this thread and you should be back booting in no time
http://forum.xda-developers.com/mi-max/how-to/guide-install-global-miui8-root-t3435594
And install proper twrp, please... or you won't be able to install any helium rom.
The device gets recognized in MiFlash, but after flashing the twrp and the stock rom, the device still does not boot.
Any proposes on my mistake?
EDIT: I just started the procedure again, unplugged the battery, connected the "jumper" and the phone booted properly.
After some failed reboots, it randomly booted into TWRP (now the right one, at least i hope so. gonna check this later) and I installed the latest RR (love the design).
So now, its just the ugly 3G-bug left and a little OC would be nice
Tsd560ti said:
The device gets recognized in MiFlash, but after flashing the twrp and the stock rom, the device still does not boot.
Any proposes on my mistake?
EDIT: I just started the procedure again, unplugged the battery, connected the "jumper" and the phone booted properly.
After some failed reboots, it randomly booted into TWRP (now the right one, at least i hope so. gonna check this later) and I installed the latest RR (love the design).
So now, its just the ugly 3G-bug left and a little OC would be nice
Click to expand...
Click to collapse
Great job:good:
So here's my story. I have a Moto X4 phone that I recently rooted and installed LineageOS 15.1 on from this page:
https://download.lineageos.org/payton
I followed the linked installation instructions and everything worked great for a couple days. This morning the 10/23 update came through and I went ahead and installed it. It seemed to take a long time and I had to go to work, but on my way to work I noticed it gave the prompt to reboot which I did. Once at work I found it was completely dead. No lights. Nothing when attempting to charge. Buttons don't do anything. Nothing. I tried plugging into my laptop at home tonight to try adb and nothing there either.
Any ideas on what could have happened to it? I'd think it'd at least light up or show some kind of intro screen. The only thing I can think of is that the thumbprint/pattern protection was on (my work requires it for email access) before installing the update. I know TWRP seems to have issues with this when booting into recovery.
After installing the LineageOS ROM, I also installed GAPPS and the arm64 LineageOS su add-on.
How easy is it to try disconnecting the reconnecting the battery? Or is that not worth a try at this point?
Thanks.
Hi!
Ota update is currently broken on this device. check link bellow for a fix:
https://forum.xda-developers.com/showpost.php?p=77905869&postcount=635
Hope it helps!
assmist said:
Hi!
Ota update is currently broken on this device. check link bellow for a fix:
https://forum.xda-developers.com/showpost.php?p=77905869&postcount=635
Hope it helps!
Click to expand...
Click to collapse
It did! Thanks! This is actually the post with blank flash zip file download that solved it for me. It booted right to the bootloader which I then selected recovery. It jumped to the LineageOS recovery screen. I then just chose to start LineageOS.
https://forum.xda-developers.com/showpost.php?p=76942904&postcount=30
Dear everyone, thanks for accepting me.
I am stuck with my Nexus 7 2013.
A couple of months ago, I have installed Lineage OS 16.0 (21 July version) succesfully, but when I tried to install Gapps I have had the common error of lack of space even if I tried the pico version.
Then I cannot remember exactly what I did (poor me).
Anyway at this moment I can enter into bootloader (FLO-04.08 - unlocked) but cannot enter anymore into recovery mode, if I choose ‘recovery mode’ it returns in bootloader, then I choose ‘Start’ and it goes on Google black screen (with padlock open in the bottom) and ontop there is still options to choose, if I choose ‘Recovery mode’ it returns in bootloader screen, if I choose start it happens nothing.
Besides I cannot figure out how to reinstall TWRP from Lineage 16.0, it doesn’t work.
Is there somebody else who were stuck like me? Do you have any suggestion?
If you need more information please ask!
Thanks in advance guys!
Michael
paperinopaolino said:
I cannot figure out how to reinstall TWRP from Lineage 16.0, it doesn’t work.
Click to expand...
Click to collapse
Hi, install TWRP:
fastboot flash recovery twrp.imgMore info. As for LineageOS, consider an older version with most current security updates. If Gapps still produce errors, just run this repartition script.
:good:
-------------EDIT-------------
paperinopaolino said:
Then I cannot remember exactly what I did (poor me).
Click to expand...
Click to collapse
Perhaps you did partitioning with https://forum.xda-developers.com/ne...partition-nexus-7-2013-repartition-t3844386.i - Note the warnings....
Repartition will erase all your data. If something gone wrong - we recommend you NOT to do anything by yourself. Write here for help, else you may do only worse.
Click to expand...
Click to collapse
The above-linked thread may have a fix already.
I am new to XDA. I flashed my Nexus 7 with Lineage OS 16 using TWRP. It was working perfectly. Since I didn't require it for my daily use, I didn't use it for about 4 months. I took it out two days ago and started it up. It started fine but its touch was not responding. It is not the first time that this has happened and usually the touch starts working after a few hours or a day. But this time it was taking too long. So I decided to factory reset it (from Lineage settings). But after restarting, it is stuck on the Google logo.
I cannot even access TWRP recovery. Using the key combination (Power+VolumeUp+VolumeDown) just restarts the device.
Any ideas?
C Karthik said:
I am new to XDA. I flashed my Nexus 7 with Lineage OS 16 using TWRP. It was working perfectly. Since I didn't require it for my daily use, I didn't use it for about 4 months. I took it out two days ago and started it up. It started fine but its touch was not responding. It is not the first time that this has happened and usually the touch starts working after a few hours or a day. But this time it was taking too long. So I decided to factory reset it (from Lineage settings). But after restarting, it is stuck on the Google logo.
I cannot even access TWRP recovery. Using the key combination (Power+VolumeUp+VolumeDown) just restarts the device.
Any ideas?
Click to expand...
Click to collapse
Yes:
#1 to enter TWRP recovery use Power+VolumeUp, not Power+VolumeUp+VolumeDown
-- alternatively do Power+VolumeDown and then select "Recovery"
#2 to fix touch issues check this post
#3 for any other issue do a more complete factory reset with RESTOCK first
:fingers-crossed:
k23m said:
Yes:
#1 to enter TWRP recovery use Power+VolumeUp, not Power+VolumeUp+VolumeDown
-- alternatively do Power+VolumeDown and then select "Recovery"
#2 to fix touch issues check this post
#3 for any other issue do a more complete factory reset with RESTOCK first
:fingers-crossed:
Click to expand...
Click to collapse
Well I have tried all key combinations ,it just restarts.
My tab is nexus 7 2013 flo. Recently I tried to flash new custom rom., I am using Havoc A11 and wish to change LOS 18.1 official. I tried to flashTwrp 3.5.1. I have done using fastboot boot twrp 3.5.1.img. Process was normal. After flashing I tried to get into recovery. The tablet landed in google logo. I tried all possibl ways to see whether tablet to reboot to bootloader but failed dall my attempts. I am unable to recover my tablet. I seek the help, direction and suggetion of forum to solve this problem.
Raja M Reddy said:
The tablet landed in google logo. I tried all possibl ways to see whether tablet to reboot to bootloader but failed
Click to expand...
Click to collapse
Now the screen is blank, device appears dead and you can not boot in fastboot mode anymore - correct?
If no, boot in fastboot mode and flash an older version of TWRP, eg 3.5.0 or 3.3.1
If yes, connect it to PC and check for a new USB device. If you see Qualcomm HS-USB 9008 - VID_05C6&PID_9008, try Nexus 7 2013 Unbricking Guide
So previous to yesterday I had a fully working Galaxy S9 G960F, running the latest version of crDroid 11 (from 2021 heh), and something like TWRP 3.5.1? A fairly old version anyway, since I'd been running the same OS for the past year. I recently noticed someone had gotten 13 working on the S9, so I downloaded it and installed it like I'd done every other time installing a custom OS before, rebooted, and then the phone starts automatically going to recovery on boot, but gets stuck on the TWRP splash screen each time.
So I figured maybe the version of TWRP was too old for Android 13, and grab the latest (3.7.0), flash that with Odin, start the phone and I can at least get into recovery this time. So I try installing crDroid again. Same deal, just instantly boots straight back into recovery. So, figuring I'd best just go back to what I was using before, I reinstalled the previous crDroid 11 I had been using, and.. for some reason with that installed it only boots into Download mode unless I force it into Recovery. I try wiping everything and trying again, same deal. I even tried installing a different rom (Evolution X) and that just straight reboot looped.
If I go back to 3.5.1 TWRP it gets stuck on the splash screen btw. I am not sure what to do from here. Can I go back to stock and start over? Is there something else I should be doing? I've changed roms a bunch of times in the past and this is the first time 'just reinstall what worked before' hasn't worked, heh.
(For clarification, with crDroid 13: Phone turns on, shows Samsung Galaxy S9 boot screen, then goes straight into TWRP. With crDroid 11: Phone turns on, Galaxy S9 boot screen, straight into Downloading. With Evolution X: Phone turns on, Galaxy S9 boot screen, shut down and reboot. Buttons don't seem to be pressed in.)
DeiwosN said:
..... Can I go back to stock and start over? Is there something else I should be doing? I've changed roms a bunch of times in the past and this is the first time 'just reinstall what worked before' hasn't worked, heh.
....
Click to expand...
Click to collapse
Similar thing happened to me on a different Samsung device.
I did:
Used at that time SamFirm_Reborn_0.3.6.2 to get latest stock from samsung servers directly after inserting correct device designation and csc code.
Checked "binary nature" to get the full multiple part stock rom.
Flashed that with Odin.
Started from scratch.
Thank you so much! That fixed it.
DeiwosN said:
Thank you so much! That fixed it.
Click to expand...
Click to collapse
Glad I could help.
Perhaps useful for other users that you mark this thread as solved.