I will try to describe problem as much as I can:
1.Unlocked bootloader(unofficial way).
2.Installed TWRP 3.0.M4-0(success).
3.Installed(in such order as stated by some guide) : CM14.1 Firmware(Kate) - 26.11.2016 >>> CM14.1-20161222 Nightly Kenzo >>> Opengapps arm64 7.1 nano with TWRP(success).
4.Reboot, CM 14.1 launches correctly, although it has saved settings and apps from MIUI, making it real mess. Now the problem starts. I assumed by doing factory reset I'll get clean 14.1 - wrong. After that turning on my phone causes it to launch TWRP instead of system.
(Failed)Attempts to fix:
1.Install CM14.1 again.
2.Wipe + install CM14.1 again.
3.Can't get into EDL mode(as stated here http://en.miui.com/thread-290959-1-1.html)
Additional info:
1.Fastboot mode launches, but 'adb devices' doesn't find anything(it was before). Device manager sees phone as well as MiFlash. Not succesful trying to update drivers(system found them up-to-date).
2.I have Kate edition, started installing after reading this http://forum.xda-developers.com/redmi-note-3/how-to/index-custom-roms-t3396628 , last posts states, that sometimes it's necessary to flash non-hlos.bin file to system(not sure if even necessary in my case, as CM14.1 launched before factory cleaning).
3.Only similar thing I found is : http://forums.androidcentral.com/sa...p-after-factory-reset-cyanogenmod-12-1-a.html , but about different device and CM version.
I'll appreciate any suggestions on how to fix it(either getting into CM14.1 or back to MIUI, preferably the first).
@edit - Solved myself. For anyone encountering such problem, I could install succesfully MIUI back, when I launched my windows in Disable Drivers Signature Mode.
what exactly have you done at the point "factory cleaning" ? do you mean anything in running android or in TWRP?
h0LLe said:
what exactly have you done at the point "factory cleaning" ? do you mean anything in running android or in TWRP?
Click to expand...
Click to collapse
Factory clean from android settings after running CM14.1 succesfully for the first time. No idea why it caused a problem, but as I wrote in edit, it is solved.
Related
Hello,
My Thor device seems to be bricked after trying to enable encryption in Lineage OS (this happened a couple of months ago).
The device used to have an unlocked bootloader with TWRP 3.1.1-1, Lineage OS 14.1 20170710 and Open GApps installed and was running without any problems (thanks to all the people here who have made this possible btw!) until enabling encryption. The encryption process was running for an eternity (more than one day), so I switched the device off.
Since then, I only get a grey "kindle fire" logo. No booting of Lineage or TWRP anymore . It's possible to start in fastboot mode via pressing the on/off switch and the volume button simultaneously, though.
I don't have any experience with bricked devices. Any suggestions what to do? And are there known issues with encryption on this device?
Many thanks in advance for your help!
RiseT said:
Hello,
My Thor device seems to be bricked after trying to enable encryption in Lineage OS (this happened a couple of months ago).
The device used to have an unlocked bootloader with TWRP 3.1.1-1, Lineage OS 14.1 20170710 and Open GApps installed and was running without any problems (thanks to all the people here who have made this possible btw!) until enabling encryption. The encryption process was running for an eternity (more than one day), so I switched the device off.
Since then, I only get a grey "kindle fire" logo. No booting of Lineage or TWRP anymore . It's possible to start in fastboot mode via pressing the on/off switch and the volume button simultaneously, though.
I don't have any experience with bricked devices. Any suggestions what to do? And are there known issues with encryption on this device?
Many thanks in advance for your help!
Click to expand...
Click to collapse
Have you tried booting a TWRP image from fastboot? If that works recovery will be a lot easier.
fastboot devices
--> if no response to this command you'll need to update host drivers
fastboot boot <twrp-image-name>
--> you can download a suitable TWRP image from here
Davey126 said:
Have you tried booting a TWRP image from fastboot? If that works recovery will be a lot easier.
fastboot devices
--> if no response to this command you'll need to update host drivers
fastboot boot <twrp-image-name>
--> you can download a suitable TWRP image from here
Click to expand...
Click to collapse
Excellent! MANY MANY THANKS! You've made my day! Worked like a charm (i. e. worked like a charm after my usual trial & error for hours to make Windows accept a Kindle Fire driver for fastboot - had to force one it warned me about on it to make it finally work).
A couple more question if I may:
When and why does one need a "Fastboot cable" (always been confused about this)?
Do you happen to know if device encryption normally works with this device?
Does switching debugging off in Lineage prevent unbricking via fastboot like this (wouldn't think so but want to make sure)?
Thanks again!
RiseT said:
Excellent! MANY MANY THANKS! You've made my day! Worked like a charm (i. e. worked like a charm after my usual trial & error for hours to make Windows accept a Kindle Fire driver for fastboot - had to force one it warned me about on it to make it finally work).
A couple more question if I may:
When and why does one need a "Fastboot cable" (always been confused about this)?
Do you happen to know if device encryption normally works with this device?
Does switching debugging off in Lineage prevent unbricking via fastboot like this (wouldn't think so but want to make sure)?
Thanks again!
Click to expand...
Click to collapse
Quick answers as I'm on the move (sorry for brevity) ...
- Moto drivers almost always work with HDX devices; install this package (don't have to launch it) which includes drivers; no warnings either
- Fastboot cables are largely ineffective on Amazon devices and rarely needed (special/unique cases beyond scope of this post)
- Encryption is NOT supported with custom ROMs on this device; dipping your head in boiling oil is a more enjoyable experience
- Prior debug setting in Lineage should have little/no impact on unbricking success
If you are unable to reload a ROM (Lineage in particular) you may have to do some further work on the data partition to remove encryption remnants. Post back if this is the case; I'll try to scare up the related material.
Davey126 said:
If you are unable to reload a ROM (Lineage in particular) you may have to do some further work on the data partition to remove encryption remnants. Post back if this is the case; I'll try to scare up the related material.
Click to expand...
Click to collapse
Thanks for your replies!
Thanks, my Thor is already up & running with the latest LineageOS and Open GApps. No problems so far. Prior to installing, In order to play it safe, I've made sure to wipe/format all partitions (including the data partition) from TWRP. Had a feeling that this would possibly be a good thing to do after that (partially?) failed encryption experience...
RiseT said:
Thanks, my Thor is already up & running with the latest LineageOS and Open GApps. No problems so far. Prior to installing, In order to play it safe, I've made sure to wipe/format all partitions (including the data partition) from TWRP. Had a feeling that this would possibly be a good thing to do after that (partially?) failed encryption experience...
Click to expand...
Click to collapse
Suspect encryption run was incomplete as simply the wiping data partition in TWRP is usually insufficient to remove critical remnants. A format is needed along with something else I don't immediately recall. You would be aware if that was needed as Lineage would hang on boot.
I can second this warning, do NOT USE ENCRYPTION. I tried so unter Lineage OS 14.1. As a result I had to wipe/format the data partition using TWRP, which let me escape from the bootloop.
Davey126 said:
Suspect encryption run was incomplete as simply the wiping data partition in TWRP is usually insufficient to remove critical remnants. A format is needed along with something else I don't immediately recall. You would be aware if that was needed as Lineage would hang on boot.
Click to expand...
Click to collapse
Can you give more details on how to remove these remnants? I did the same thing as OP this morning & now I'm here trying to undo my mistake :crying:
I still have TWRP 3.1.1-1 & I can flash stock 4.5.5 rom, but I can't flash any other custom roms as I'd get into a boot loop with grey kindle fire logo. I did wipe everything except sdcard, and the stock rom is running perfectly fine, except for root & gapps, of course.
Edit: SOLVED, courtesy to this post https://forum.xda-developers.com/showpost.php?p=74710623&postcount=1029
Hello, first of all i am sorry for my english.
I beg you to help me.
I wanted to do an update from my Cuoco92 to Lineage ( https://forum.xda-developers.com/le...x-lineageos-15-1-oreo-leeco-le-max-2-t3771577 ) and i surely made something wrong because the phone was litteraly stuck.
So, i waited 1 hours... and nothing happened. Then, I decided to force the reset. Recovery told me that no rom was installed.
Then, i tried to install several roms from the website (cuoco, linegae, small eui...) but there are some issue :
- google play doesnot want to work at all.
- most of the time, the phone is saying something like "data corrupted. Put in it factory mode" and even when i reset my phone in factory mode, it is still telling me that.
Now, i am giving up because sideload said me "Error 7" each time i try to install something new.
I need your help. I beg you, i can give you with a steam game or something like that but i want to fix that...
Someone want to skype or i dont know?
Thank you!!
in TWRP please go to wipe > format data > yes.
then install any rom.
Heyyo, please upgrade to the latest version of TWRP. 3.2.1-2. it has fixed ADB sideload where as older versions it is broken.
https://twrp.me/leeco/leecolemax2.html
Also, another option is to use ADB push which tbh I always prefer over sideload so that the full zip is on the device.
IE...
adb push NameOfFile.zip /sdcard/
That will copy that zip to the sdcard folder which is the root of the data partition so it can be easily deleted once you are fully booted into the ROM.
For Gapps? I recommend MindTheGapps arm64. It's fully compatible to LineageOS and Oreo ROMs in general where as OpenGapps for Oreo is still of beta quality.
Lastly, I recommend upgrading your device firmware. X820 30s is the latest stable but arguably 466D has a newer timestamp for the modem portion of the firmware so in theory it should have better cellular connectivity.
All links can be found in the LineageOS 15.1 for x2 thread.
Good luck!
Hi everyone,
I unlocked the bootloader with XiaoMiTool V2 (I have no Windows computer) and flashed TWRP with it, and then the current crDroid to check it out.
After that, I installed Lineage for MicroG with the XiaoMiTool V2, but this time, Lineage did not boot. (Probably not a great idea, to use this tool to exchange one custom ROM to another.)
I tried to sideload it manually, following these installation instructions without success:
https://wiki.lineageos.org/devices/beryllium/install
The Poco drops into fastboot after a wile after turning it on, but I can boot into TWRP (Official 3.3.0-0) with Vol+ & Power
What are the next steps to diagnose or reach normal installation behaviour?
Thnx for any suggestions
hanseatic2 said:
Hi everyone,
I unlocked the bootloader with XiaoMiTool V2 (I have no Windows computer) and flashed TWRP with it, and then the current crDroid to check it out.
After that, I installed Lineage for MicroG with the XiaoMiTool V2, but this time, Lineage did not boot. (Probably not a great idea, to use this tool to exchange one custom ROM to another.)
I tried to sideload it manually, following these installation instructions without success:
https://wiki.lineageos.org/devices/beryllium/install
The Poco drops into fastboot after a wile after turning it on, but I can boot into TWRP (Official 3.3.0-0) with Vol+ & Power
What are the next steps to diagnose or reach normal installation behaviour?
Thnx for any suggestions
Click to expand...
Click to collapse
tried flashing crdroid again?
suritsuwal said:
tried flashing crdroid again?
Click to expand...
Click to collapse
That seemed to work. Thnx. I am back on crDroid for now.
I suspect the issue with data encryption settings, but had not the chance to reproduce the prob or find a proper way.
I'll try to figure out how to enable signature spoofing and run microG on crDroid now.
hanseatic2 said:
That seemed to work. Thnx. I am back on crDroid for now.
I suspect the issue with data encryption settings, but had not the chance to reproduce the prob or find a proper way.
I'll try to figure out how to enable signature spoofing and run microG on crDroid now.
Click to expand...
Click to collapse
:good:
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Wiki.
Recovery
The LineageOS 17.1 reovery is recommended
If you still want to use TWRP never install the TWRP app as system app. Otherwise your device won't boot
Current lineage 17.1 shamu nightlies are based on the N6F27M October 2017 update from google.
So you should be using the radio and bootloader img from that update.
Before you flash a bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one and don't need to flash it again.
They can be extracted from the factory image on google's site here.
Or you can use the ones linked below that I already extracted:
radio-shamu-d4.01-9625-05.45+fsg-9625-02.117.img
bootloader-shamu-moto-apq8084-72.04.img
IMPORTANT NOTE FOR VERIZON USERS: Google released a separate October 2017 security update (NGI77B) just for verizon users that has a different radio. So you'll want to flash it. I repeat, THIS RADIO IS JUST FOR VERIZON USERS.
radio-shamu-d4.01-9625-05.51+fsg-9625-02.118.img
You can use fastboot to flash the bootloader and radio.
More information and installation instructions can be found on the LineageOS wiki here.
Download Links
LineageOS: https://download.lineageos.org/shamu
Google apps: Opengapps Use an ARM (not ARM64) package for Android 10
HEADS UP: When you initially install LineageOS, be sure you flash the gapps package with your ROM. If you boot your ROM, then go back and try to flash gapps after, you're gonna have a bad time.
Changelog
Builddate: 2020.06.17
Changes:
[new] June security updates
[new] LineageOS clock
Builddate: 2020.05.29
Changes:
[new] May security updates
[fix] ULL audio fixes
[new] Add back serif fonts
[fix] Screen turning itself on when no lockscreen is set
[new] Etar calendar
Builddate: 2020.04.12
Changes:
[new] April security updates ROM & kernel
Builddate: 2020.04.08
Changes:
[new] Initial LineagOS 17.1 release
Known Issues:
[bug] Trusted voice is not working and probably never will
[bug] TWRP is not able do decrypt your data if you encrypted it with lineage-16.0
[bug] IMS is not working - if you need it you have to stay on lineage-15.1
XDA:DevDB Information
LineageOS, ROM for the Nexus 6
Contributors
Elektroschmock, elektroschmock, npjohnson
Source Code: http://github.com/lineagos
ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2020-04-08
Last Updated 2020-04-08
Reserved
First build isn't out yet, but I don't want the LineageOS 16.0 thread to be spammed with 17.1 questions
Will waiting for the build you might want to read the Changlog for the first LineageOS 17.1 release:
Changelog 24
Will there be a possibility to root?
Should we wait for 17.1 to flash the radio and bootloader or can we do it now to get it out of the way?
What are the commands for flashing those two images?
Thanks @Elektroschmock and @npjohnson for keeping the Nexus 6 alive in 2020. :good:
Eazy said:
Will there be a possibility to root?
Click to expand...
Click to collapse
Yes you can use your root solution of choice.
Only thing coming with the ROM is adb root.
dlbarron said:
Should we wait for 17.1 to flash the radio and bootloader or can we do it now to get it out of the way?
What are the commands for flashing those two images?
Click to expand...
Click to collapse
Actually you should already have those radio and bootloader images if you had the latest stock image installed at one point.
Commands are:
fastboot flash bootlader [name_of_the_bootloader_image]
and
fastboot flash radio [name_of_the_radio_image]
Elektroschmock said:
Actually you should already have those radio and bootloader images if you had the latest stock image installed at one point.
Commands are:
fastboot flash bootlader [name_of_the_bootloader_image]
and
fastboot flash radio [name_of_the_radio_image]
Click to expand...
Click to collapse
Actually, I've been running Lineage and CM before that since I brought the phone home. So there's no way I had the latest stock image installed ever.
Thanks, I'm all set
Welp I did a stupid.
Flashed the new 17.1 recovery via fastboot. Then I tried to sideload via adb (based on the instructions) but Linux machine kept complaining about needs adb root. Tried with root permission nothing, Then came the stupid. Rebooted into recovery and tried to apply the update. Well that went how I expected, badly. Stuck on LOS loading screen.
Needed a fresh install anyway.
Stick to the instructions, guys.
BootloopedMillennials said:
Welp I did a stupid.
Flashed the new 17.1 recovery via fastboot. Then I tried to sideload via adb (based on the instructions) but Linux machine kept complaining about needs adb root. Tried with root permission nothing, Then came the stupid. Rebooted into recovery and tried to apply the update. Well that went how I expected, badly. Stuck on LOS loading screen.
Needed a fresh install anyway.
Stick to the instructions, guys.
Click to expand...
Click to collapse
Hello you can flash twrp with your pc after boot in twrp flash 17.1 + gapps micro + magisk 20.4 + wipe data + wipe dalvik + wipe cache reboot and it work perfectly ! Ps no intall twrp app in twrp recovery before reboot or you have bootloop Cordialy
BIG THANKS @Elektroschmock very Nice work
xrenoix said:
Hello you can flash twrp with your pc after boot in twrp flash 17.1 + gapps micro + magisk 20.4 + wipe data + wipe dalvik + wipe cache reboot and it work perfectly ! Ps no intall twrp app in twrp recovery before reboot or you have bootloop Cordialy
BIG THANKS @Elektroschmock very Nice work
Click to expand...
Click to collapse
My system got corrupted by the previous process. So I had to do a fresh install.
BootloopedMillennials said:
My system got corrupted by the previous process. So I had to do a fresh install.
Click to expand...
Click to collapse
Hello you have test wipe system with twrp ? Or test repair ? And use pico gapps for trébuchet launcher not work with mirco gapps but pixel launcher work ? !
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
mrk2815 said:
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
Click to expand...
Click to collapse
Best would be to use built in update. Unless you want to do a clean install, there's no reason to do it.
the update inside of lineage is blocking updating to lineage 17.1 , i tried tha earlier and i jsut tried it again. then it gives the link to the wiki page.so thats not going to work.i will have to do the old method of flashing through twrp or hoping that there is a command line approach to flashing lineage through lineage recovery.
mrk2815 said:
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
Click to expand...
Click to collapse
Sorry, I didn't ignore your question, but I first had to check.
It's kind of hard to imagine how a blind person would do it if you can see.
If you have Lineage recovery installed and are able to boot into recovery do the following steps:
Press the Volume Down button 1 time
Press the power button two times
You are now in the adb apply update mode.
There you can install all the zip files you want. I guess you script does the rebooting to system itself.
If you need further help just ask.
@Elektroschmock
Thanks for your hard work!
I have two questions, if lineage recovery wipe the internal storage every time when I wipe the data or system? and when I flash the boot animation it seems not work. May you give some suggestion? Thank you!
s_dino said:
@Elektroschmock
Thanks for your hard work!
I have two questions, if lineage recovery wipe the internal storage every time when I wipe the data or system? and when I flash the boot animation it seems not work. May you give some suggestion? Thank you!
Click to expand...
Click to collapse
The recovery doesn't do anything on it's own. If you want to wipe any partition you need to select the corrosponding entry in the recovery.
I don't know about which bootanimation you are talking about. Do you mean the bootloader?
Before you flash bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one.
Elektroschmock said:
The recovery doesn't do anything on it's own. If you want to wipe any partition you need to select the corrosponding entry in the recovery.
I don't know about which bootanimation you are talking about. Do you mean the bootloader?
Before you flash bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one.
Click to expand...
Click to collapse
In TWRP I can select only wipe data/cache/system, the internal storage can be retained. The lineage recovery haven't the "wipe internal storage" option, so how can I wipe the data/system and keep the internal storage at the same time? Do I need to update the recovery version when I update the system daily build?
I mean I want use the google original boot animation to replace the lineage boot animation, but not success.
I noticed this: "disable audio rotation tracking"
https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/272403
Is that the end of stereo sound in landscape? (Of course if that is necessary to fix the loss of sound in calls, it is totally worth it, just curious).
s_dino said:
In TWRP I can select only wipe data/cache/system, the internal storage can be retained. The lineage recovery haven't the "wipe internal storage" option, so how can I wipe the data/system and keep the internal storage at the same time? Do I need to update the recovery version when I update the system daily build?
I mean I want use the google original boot animation to replace the lineage boot animation, but not success.
Click to expand...
Click to collapse
You still have those options:
Go to "Factory Reset"
There you can choose which partition you want to wipe.
- Wipe data/factory reset
- Wipe cache
- Wipe system
I guess you want the "wipe system" option
Sorry we don't support modifying our builds for obvius reasons. If you want to do that you are on your own. Sorry.
runekock said:
I noticed this: "disable audio rotation tracking"
https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/272403
Is that the end of stereo sound in landscape? (Of course if that is necessary to fix the loss of sound in calls, it is totally worth it, just curious).
Click to expand...
Click to collapse
It's just a test. Non of us was able to trigger the loss of audio. Youl'll still have stereo but it won't switch channels if you turn your device.
Already opened an issue on GitHub but looks like the dev got a long backlog. If anyone has a fix I'd really appreciate it.
I experienced the following when updating TWRP to 3.5.0_90:
- long loading time: takes ~20s to finish initialization
- when I deal with anything that supposedly work with the /system partition the device will freeze and shutdown. Tried: wipe system+data; flash magisk; flash gapps. Somehow dirty flashing a rom worked just fine (manipulating /data is fine I guess?)
Tried reversing to 3.4.0 and won't be able to properly mount existing partitions. Guess I should just wait for a fix. For those who look to update - proceed with caution!
bloomfielderic said:
Already opened an issue on GitHub but looks like the dev got a long backlog. If anyone has a fix I'd really appreciate it.
I experienced the following when updating TWRP to 3.5.0_90:
- long loading time: takes ~20s to finish initialization
- when I deal with anything that supposedly work with the /system partition the device will freeze and shutdown. Tried: wipe system+data; flash magisk; flash gapps. Somehow dirty flashing a rom worked just fine (manipulating /data is fine I guess?)
Tried reversing to 3.4.0 and won't be able to properly mount existing partitions. Guess I should just wait for a fix. For those who look to update - proceed with caution!
Click to expand...
Click to collapse
Only install twrp-3.5.0_90. It does not work! twrp-3.4.0-0-clover. The same is true. Only twrp-3.3.1-0-clover can be returned
agreed... v3.5.0-9 just boot to black screen recovery... this is a bug...
v3.4.0 need to format data to be able to read it properly.... this is not bug...
I installed latest twrp on mi pad 4 and now it gets stuck on the twrp logo screen also i cannot boot my system just keeps going to the twrp screen ive tried installing different recoveries but same issue just gets stuck on recovery logo screen is there a fix for this ?
bloomfielderic said:
Already opened an issue on GitHub but looks like the dev got a long backlog. If anyone has a fix I'd really appreciate it.
I experienced the following when updating TWRP to 3.5.0_90:
- long loading time: takes ~20s to finish initialization
- when I deal with anything that supposedly work with the /system partition the device will freeze and shutdown. Tried: wipe system+data; flash magisk; flash gapps. Somehow dirty flashing a rom worked just fine (manipulating /data is fine I guess?)
Click to expand...
Click to collapse
Can confirm, just experienced the same with v3.5.1_9-0 coming from v3.3.1. And when I tried to proceed flashing RR, was dumped into shutdown and then fastboot.
Used fastboot to re-flash recovery and upon issuing 'fastboot reboot recovery' was again dumped into shutdown (and then back to fastboot).
UPDATE: tried flashing different TWRP versions (the ones linked in the LineageOS 17.1 and crDroid threads, plus an old Mokee I had on file) without success. Fastboot doesn't throw any errors, but the copying phase appears to me overly fast and upon reboot all it does is go back to fastboot. Well, the device is soft-bricked as it is, looks like I'll have to try the MiFlash route.
UPDATE2: I did use MiFlash succesfully and am now on LOS 17.1. OrangeFox (found here, as well as the TWRP linked in the LOS 17.1 thread) were the ones that worked for me in the end...