I am attempting to put lineageos on my new Mi A1, following the installation guide here https://wiki.lineageos.org/devices/tissot/install
I have previously installed lineage on my old Moto G LTE and a Samsung Galaxy S4 and have not run into issues.
I have unlocked the bootloader and all that but I can't get twrp to boot.
I boot into fastboot with
Code:
adb reboot bootloader
that works fine, then I
Code:
fastboot boot twrp-3.2.2-0-tissot.img
This seems to have no effect, other than my phone 'disconnecting' from the PC.
I get the following terminal output
Code:
./fastboot boot .\twrp-3.2.2-0-tissot.img
Downloading 'boot.img' OKAY [ 0.682s]
booting OKAY [ 0.623s]
Finished. Total time: 1.336s
However nothing happens on the phone, it still just has the fastboot logo on it.
At this point if I manually reboot (long-press power) it will reboot into stock rom.
If I manually reboot into recovery (long-press power+volume up) it will reboot into stock recovery
I have ensured my sytem tools are up to date, and tried the previous version of twrp, and there is no change.
I WAS able to get twrp to boot using the "Mi A1 Tool" i found here https://forum.xda-developers.com/mi-a1/how-to/tool-xiaomi-mi-a1-tool-drivers-unlock-t3742857
However I was not able to install lineage due to an error.
I did not copy the exact output but it was something along the lines of
error 7, kInstallDeviceOpenError
After this attempt, I reflashed the stock rom using Xiaomi tools, and am back to the beginning.
The phone is fully up-to-date with stock updates, Android 8.1, July security update.
Once again went through the bootloader unlocking, and everything, but have arrived at the same result.
Anyone have any ideas?
any help would be greatly appreciated!
Thanks!
Hey, could you try this TWRP made for Oreo? https://www.androidfilehost.com/?fid=818070582850498337 (thread: https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472)
I've also had some issues booting TWRP, but running
Code:
fastboot oem unlock
was enough to boot it successfully (
Code:
fastboot boot recovery-3.2.1-2-oreo.img
)
Thank you!
dgadelha said:
Hey, could you try this TWRP made for Oreo? https://www.androidfilehost.com/?fid=818070582850498337 (thread: https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472)
I've also had some issues booting TWRP, but running
Code:
fastboot oem unlock
was enough to boot it successfully (
Code:
fastboot boot recovery-3.2.1-2-oreo.img
)
Click to expand...
Click to collapse
This recovery image worked great, AND installed lineage, thank you very much.
However, I am now unable to get gapps working.
I was pointed to this changelog here https://lineageos.org/Changelog-19/ by a user in the lineage subreddit.
I rebooted from twrp into the lineage recovery, chose Apply Update -> Apply from ADB
On my PC I run
Code:
./adb sideload .\MindTheGapps-8.1.0-arm64-20180610_024023
.zip
and after a pause I get the output
Code:
serving: '.\MindTheGapps-8.1.0-arm64-20180610_024023.zip' (~0%) adb: failed to read command: No error
and sometimes I get
Code:
serving: '.\MindTheGapps-8.1.0-arm64-20180610_024023.zip' (~0%) adb: failed to read command: Connection reset by peer
What happens on the phone has been a little different each time I have attempted this.
It either pops up on screen that it is unable to verify the file, install anyway?, doing so doesn't work.
OR it is hung up on a progress bar screen, with the following log output, or a slight variation of it
Code:
Stopping adbd...
Now send the package you want to apply to the device with "adb sideload <filename>"...
Finding update package...
Opening update package...
Verifying update package...
E: Signature verification failed
E:error: 21 Restarting dbd... Installation aborted.
After many attempts of this, reflashing lineage, and trying again, it did miraculously start doing the transfer at one point. It got to 47% then failed again.
Can't you just install from recovery?
https://forum.xda-developers.com/mi-a1/development/rom-lineageos-15-1-t3757938
pidermin said:
This recovery image worked great, AND installed lineage, thank you very much.
However, I am now unable to get gapps working.
I was pointed to this changelog here https://lineageos.org/Changelog-19/ by a user in the lineage subreddit.
I rebooted from twrp into the lineage recovery, chose Apply Update -> Apply from ADB
On my PC I run
Code:
./adb sideload .\MindTheGapps-8.1.0-arm64-20180610_024023
.zip
and after a pause I get the output
Code:
serving: '.\MindTheGapps-8.1.0-arm64-20180610_024023.zip' (~0%) adb: failed to read command: No error
and sometimes I get
Code:
serving: '.\MindTheGapps-8.1.0-arm64-20180610_024023.zip' (~0%) adb: failed to read command: Connection reset by peer
What happens on the phone has been a little different each time I have attempted this.
It either pops up on screen that it is unable to verify the file, install anyway?, doing so doesn't work.
OR it is hung up on a progress bar screen, with the following log output, or a slight variation of it
Code:
Stopping adbd...
Now send the package you want to apply to the device with "adb sideload <filename>"...
Finding update package...
Opening update package...
Verifying update package...
E: Signature verification failed
E:error: 21 Restarting dbd... Installation aborted.
After many attempts of this, reflashing lineage, and trying again, it did miraculously start doing the transfer at one point. It got to 47% then failed again.
Click to expand...
Click to collapse
Hey,
Install GApps also at TWRP. Signature verification is failing most probably because the Lineage Recovery should be accepting only Lineage-signed ZIP files.
You can install TWRP in your current boot image (so you don't need to boot TWRP everytime through fastboot) with this ZIP: https://www.androidfilehost.com/?fid=746010030569959456 (yet, you need to boot to TWRP through fastboot so you can flash it, but no need to boot it manually after installing it). Notice that after every system update you may need to install TWRP again (same for Magisk), as boot images get replaced.
Also, if sideload fails, you can just do a
Code:
adb push filename.zip /sdcard/
then install the ZIP directly from the "Install" section on TWRP.
Thanks!
Thanks a lot!
I found and was able to follow this guide
https://forum.xda-developers.com/mi-a1/how-to/lineageos-gapps-magisk-twrp-dolbyatmos-t3762939
instead of the one on the lineageOS website, and I am up and running.
Thank you very much for your time!
Can't boot to recovery or fastboot
I'm totally not getting the problem, i am having network issues on my Mi A1 on both Oreo and pie. So I decided to install a custom ROM but I can't boot my device to fastboot or recovery, it simply reboots . I tried the hard keys as well as through the PC using command prompt it just reboots normally. Any suggestions on what should I do Please?
Azan Qazi said:
I'm totally not getting the problem, i am having network issues on my Mi A1 on both Oreo and and pie. So I decided to install a custom ROM but I can't boot my device to fastboot or recovery, it simply reboots . I tried the hard keys as well as through the PC using command prompt. Any suggestions on what should I do.
Click to expand...
Click to collapse
Have you tried doing reboot in the OS and choosing Recovery option?
Azan Qazi said:
I'm totally not getting the problem, i am having network issues on my Mi A1 on both Oreo and pie. So I decided to install a custom ROM but I can't boot my device to fastboot or recovery, it simply reboots . I tried the hard keys as well as through the PC using command prompt it just reboots normally. Any suggestions on what should I do Please?
Click to expand...
Click to collapse
TrueMS said:
Have you tried doing reboot in the OS and choosing Recovery option?
Click to expand...
Click to collapse
yes sir I did tried several times. But as I said above it simply reboots the system.
Related
Kit-Kat OTA came out for my Nexus 4 today and I went to apply it but during the install it errored out and the phone subsequently enters a boot loop. I can get into a recovery shell and attempt to push the update via sideload but I get an error:
Symlinks and permissions...
set_metadata_recursive: some changes failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted
I'm 99% sure there's a binary in /system/xbin/ or /system/bin/ thats set immutable (chattr +i) causing this to fail but I can't launch an adb shell from recovery to fix this. Can anybody help me out here?
ykram said:
Kit-Kat OTA came out for my Nexus 4 today and I went to apply it but during the install it errored out and the phone subsequently enters a boot loop. I can get into a recovery shell and attempt to push the update via sideload but I get an error:
Symlinks and permissions...
set_metadata_recursive: some changes failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted
I'm 99% sure there's a binary in /system/xbin/ or /system/bin/ thats set immutable (chattr +i) causing this to fail but I can't launch an adb shell from recovery to fix this. Can anybody help me out here?
Click to expand...
Click to collapse
Are you using stock recovery to do this?
You pretty much explained why, but if you had rooted the phone it could fail due to other reasons too.
If you have an unlocked bootloader then you can boot TWRP (not install, but boot by fastboot boot twrp.img), it have its own terminal and you can go in and chattr -i that file.
Or with unlocked bootloader you just "fastboot format system" and flash the full system.img from the factory image. Or use TWRP to flash a stock rom.
I don't see how else you could have ran a chattr command to the /system without root. But without an unlocked bootloader you pretty much only have the choice of factory reset or unlock the bootloader in which both will wipe all data. But I'm pretty sure beside fastboot erase and format, not even factory reset in recovery could get rid of an immutable file. There is no adb access in stock recovery beside adb sideload signed packages (otherwise every android phones will be very unsecure).
eksasol said:
Are you using stock recovery to do this?
You pretty much explained why, but if you had rooted the phone it could fail due to other reasons too.
If you have an unlocked bootloader then you can boot TWRP (not install, but boot by fastboot boot twrp.img), it have its own terminal and you can go in and chattr -i that file.
Or with unlocked bootloader you just "fastboot format system" and flash the full system.img from the factory image. Or use TWRP to flash a stock rom.
I don't see how else you could have ran a chattr command to the /system without root. But without an unlocked bootloader you pretty much only have the choice of factory reset or unlock the bootloader in which both will wipe all data. But I'm pretty sure beside fastboot erase and format, not even factory reset in recovery could get rid of an immutable file. There is no adb access in stock recovery beside adb sideload signed packages (otherwise every android phones will be very unsecure).
Click to expand...
Click to collapse
Unfortunately, you're correct. I was rooted at one point and had an old 'su' binary around that was immutable, completely forgotten about. My bootloader is stock atm and I'm still stuck on 'no command' I'm accepting the inevitability that I'll have to wipe and start over but I'm not even sure how to flash the factory firmware now since I'm either stuck in a 'Google' boot loop or I get 'no command'.
Any suggestions?
ykram said:
Unfortunately, you're correct. I was rooted at one point and had an old 'su' binary around that was immutable, completely forgotten about. My bootloader is stock atm and I'm still stuck on 'no command' I'm accepting the inevitability that I'll have to wipe and start over but I'm not even sure how to flash the factory firmware now since I'm either stuck in a 'Google' boot loop or I get 'no command'.
Any suggestions?
Click to expand...
Click to collapse
When you see no command that is normal. To bring up the stock recovery menu, while holding Power first, press Volume Up.
Google bootloop have nothing to do with flashing factory image since it required using fastboot in fastboot mode (not in recovery), aka the bootloader menu. Links in my signature have instructions to flash factory image.
eksasol said:
When you see no command that is normal. To bring up the stock recovery menu, while holding Power first, press Volume Up.
Google bootloop have nothing to do with flashing factory image since it required using fastboot in fastboot mode (not in recovery), aka the bootloader menu. Links in my signature have instructions to flash factory image.
Click to expand...
Click to collapse
Cool, gotch ya. Many thanks for the response and help.
Hi, I recently tried to unbrick my phone from corrupted bootloader by using xFSTK and basically following this tutorial http://forum.xda-developers.com/android/development/hard-bricked-zenfone-unbrick-method-to-t3131911. However, the steps given there weren't working well for me, because xFSTK was giving me this error: "XFSTK-STATUS--USBSN:629391F5E045705C--Softfuses Binary absent. Please provide binary.". I fixed it by using softfuse binary (whatever it does) found under this video https://www.youtube.com/watch?v=o-b1sPy8SlI. Apparently, it wasn't the best idea and flashing that messed up my phone so bad that now nothing is even displayed. The only thing that is still working is that it is detected as 'CLOVERVIEW' device when I connect it to my pc and I can flash it using xFSTK. No fastboot, no recovery. Is it still possible to fix this or do I just have a stylish paperweight?
try look there http://23pin.logdown.com/ just search
The tutorial on that blog is exactly the same as here on xda (just translated). Still no luck.
see this post its written by asus guys:
http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=33800
@quad muffin.........I had this issue several times. It's nothing serious and you just need to make sure you turn off your device. Long press the power button will turn off the device but honestly, it's difficult to understand it's on/off at this situation. Please follow the below instructions:
1. TURN OFF the device
2. Press and hold Volume Up+Power to enter to fastboot/droidboot. When the ASUS logo shows up, release the power button and keep on pressed the Volume UP button. This will take you to droidboot mode.
3. check whether your PC detects the fastboot...
Code:
fastboot devices
if not, go to device manager and install the fastboot driver(by online). if fails, install from the PC by selecting the android device from the list.
4. download this image UL-ASUS_T00F-WW-2.21.40.30-user.zip: http://dlcdnet.asus.com/pub/ASUS/Ze...user.zip?_ga=1.61130092.1708615694.1457697474
5. extract fastboot.img, boot.img, recovery.img from the zip file and copy to ADB folder to flash. Copy UL-ASUS_T00F-WW-2.21.40.30-user.zip to ADB folder as well.
6. run the below commands:
Code:
fastboot flash fastboot fastboot.img
fastboot reboot-bootloader
wait for reboot.....
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
7. then go to recovery by selecting from the menu
8. in the recovery, select wipe data/factory reset
9. select wipe cache partition
10. select apply update over adb sideload
11. Now check whether your PC detects the ADB over USB. if not, go to your PC's device manager and install the ADB driver online. if fails, install from the PC by selecting the android device from the list.
12. after successful detection, run below command
Code:
adb sideload UL-ASUS_T00F-WW-2.21.40.30-user.zip
let me know if it works or not. Good luck.
Thanks a lot for the reply, but unfortunatelly a few days ago I sent my phone to asus service and they fixed it by replacing mainboard. But I'm sure the steps will be usefull for people trying to fix their phones in the future.
quad muffin said:
Thanks a lot for the reply, but unfortunatelly a few days ago I sent my phone to asus service and they fixed it by replacing mainboard. But I'm sure the steps will be usefull for people trying to fix their phones in the future.
Click to expand...
Click to collapse
I will post my instruction with debrick soon.
I guess it will help you...
http://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455/
When "adb sideload <filename>" finished...
"Finding update package...
Opening update package...
Verifying update package...
Installing update...
Device image SKU:
TW
OTA image SKU: TW
Please update to newest 4.3 image first...
Erasing old dictionary...
Updating splash image...
Updating IFWI image...
(SKIP) Updating 3g Module firmware image...
(SKIP) Updating 3G module nvm...
Install from ADB complete."
But still stuck at Asus logo
wernico said:
When "adb sideload <filename>" finished...
"Finding update package...
Opening update package...
Verifying update package...
Installing update...
Device image SKU:
TW
OTA image SKU: TW
Please update to newest 4.3 image first...
Erasing old dictionary...
Updating splash image...
Updating IFWI image...
(SKIP) Updating 3g Module firmware image...
(SKIP) Updating 3G module nvm...
Install from ADB complete."
But still stuck at Asus logo
Click to expand...
Click to collapse
Reboot to bootloader, flash the fastboot, boot, and recovery images from the firmware zip file. Then go to recovery and sideload the firmware again.
Sent from my ASUS_T00J using XDA-Developers mobile app
Can't flash via TWRP, "failed mount system", twrp sideload not working either.. stuck
I need my phone for work tomorrow so any help would be greatly appreciated.
I'm on TWRP 3.2.3-1 and was using the latest stock oreo rom from here: https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
My phone suddenly didn't have a reception today, after rebooting I regained reception but couldn't make calls. I rebooted to recovery and tried to dirty flash the same stock twrp flashable oreo rom that I was using and it failed. Apparently the OS got corrupted. I tried repeatedly to flash the ROM and then noticed I was getting an error : failed to mount system , invalid argument. I couldn't mount system via the Mount tab in TWRP and I couldn't find anything helpful to resolve this error.
I did some more research downloaded the fastboot flashable ROM from here : https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433 and tried to flash the rom via adb using adb sideload in twrp but twrp doesn't seem to load that function correctly. In the elevated command prompt in the adb directory I type adb sideload filename.zip and it just freezes up my PC. My device does show up with the adb devices command and shows " *Serial Number* RECOVERY ".
I don't understand what to do with the instructions in the fastboot flash stock thread I posted above and I'm at the limit of my knowledge. No idea how to proceed... any help is greatly appreciated.
I tried extracting the xml.zip into the adb folder and rebooted to bootloader/AP Fastboot Flash Mode and was going to try the commands in the fastboot Rom thread but my device only shows up in adb devices when I load twrp. uhhhhgggghhhhhh guess I'll have to buy a backup phone tomorrow while I try to get this one working
Holy hell.... I didn't realize since I was in the fastboot/bootloader I had to use "fastboot devices" command to see the device. Tried that and saw the device listed, so I created a .bat file using the commands in the fastboot roms thread above and I have a functional device again. Whohoooooo!
Did you try to format /System/ as EXT4?
Hello, I'm trying to install LineageOS on my Asus Zenfone Max Pro m1 (ZB602KL) but I'm stuck in TWRP and cannot install any OS.
(Sorry I cannot post proper external links as i am new on this forum)
I will try to explain what I did as clearly as possible (I was following the install page X00TD from the LineageOS website) :
1. Unlocking the bootloader
No problem here I guess, I just downloaded the from asus.com/Phone/ZenFone-Max-Pro-M1/HelpDesk_Download/ then
Code:
adb install
it then run the application from the device.
2. Installing a custom recovery using fastboot
This is where is start to be blurry for me. I download the TWRP from the link given by the LineageOS install page (androidfilehost.com/?fid=3700668719832241089) I can
Code:
fastboot flash recovery <recovery_filename>.img
without any problem but when I reboot into recovery I don't get TWRP and when try to
Code:
fastboot boot <recovery_filename>.img
I get something like this :
Code:
downloading 'boot.img'...
OKAY [ 2.292s]
booting...
FAILED (remote: unknown command)
So I'm trying to get an other version of TWRP from the TWRP website but the Asus Zenfone Max Pro m1 is not listed in the devices section (twrp.me/Devices/Asus/). I finally found this reddit post reddit.com/r/LineageOS/comments/aiiw3f/flashing_twrp_on_linux_fastboot_doesnt_work/ , download this TWRP androidfilehost.com/?fid=11410963190603879312 and flash it using
Code:
fastboot flash:raw boot <recovery_filename>.img
as recommended on the post and can finaly boot into TWRP.
3. Installing LineageOS from recovery
I "format data" and do an "advanced wipe" as indicated on the LineageOS install page, I get some error messages (encryption, etc.) so I reboot into recovery and try again and it seems to work. I try to sideload the last lineage build downloaded here download.lineageos.org/X00TD but I get this :
Code:
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
so I decided to
Code:
adb push
it and install it via TWRP but I get an
Code:
Updater process ended with ERROR: 7
. I found this reddit post reddit.com/r/LineageOS/comments/cfwnox/x00td_lineageos_16_firmware_error/. I downloaded the firmware from asus.com/Phone/ZenFone-Max-Pro-M1/HelpDesk_Download/ but I cannot install it from TWRP (error 7 again).
Then I found some link to a "PIE" firmware that I can install from TWRP after installing the "PIE" firmware I can finally install LineageOS but when I reboot I get some warning message saying : "the boot loaded is unlocked and software integrity..." after this I get the LineageOS loading animation (the right to left blue bubble) for 2 minutes then it reboot to TWRP.
Voila.
- I don't really understand the difference between the FIRMWARE (1.5 Gb) or the PIE FIRMWARE (60 Mb) or even the LineageOS file. I'm still trying to adb push some firmware or OS and install them but i'm affraid of making an irreversible mistake and "brick" the phone.
- I don't know if the problem come from my
Code:
fastboot flash:raw boot <recovery_filename>.img
TWRP install or from a bad TWRP file, or from the OS/firmware file.
So what should I do now? How do I clean this mess and install a working OS (LineageOS or even back to Asus/Android factory OS)?
Any help is appreciated, Thank you
uncheck TWRP boxes?
I found this post reddit.com/r/LineageOS/comments/dtnec5/infinite_loading_screen_after_fresh_installation/
and I simply unchecked the TWRP auto install boxes before reboot... and it seems to work for the moment.
The OS takes 7.8Gb, I don't know if it's a normal size or I messed something.
Flash newer firmware
hello everyone. I haven't modded a smartphone for a long time and I need some help.
after installing lineage os a few years ago now i would like to go back with oxygen but i have problems with the installation of twrp.
I installed the platform tools and drivers and placed the twrp image in the (platform tools) folder.
debugging enabled
launching the command in the windows prompt: adb reboot bootloader the smartphone restarts correctly and shows me the screen with the choice START RESTART RECOVERY POWER OFF
the fastboot devices command, however, does not return any results
inserting the adb rebbot fastboot command instead the phone starts correctly in lineage os fastboot mode and now the fastboot devices command gives the result
now I enter the folder where I copied the twrp image cd c:\platform-tools and I give the command fastboot boot twrp.img (the file is renamed TWRP)
but this is the result
c:\platform-tools>fastboot boot twrp.img
Sending 'boot.img' (33116 KB) OKAY [ 0.995s]
Booting FAILED (remote: 'Unrecognized command boot')
fastboot: error: Command failed
Can someone be kind enough to help me. I have made many different attempts to no avail.
Thank you!
sun-k said:
hello everyone. I haven't modded a smartphone for a long time and I need some help.
after installing lineage os a few years ago now i would like to go back with oxygen but i have problems with the installation of twrp.
I installed the platform tools and drivers and placed the twrp image in the (platform tools) folder.
debugging enabled
launching the command in the windows prompt: adb reboot bootloader the smartphone restarts correctly and shows me the screen with the choice START RESTART RECOVERY POWER OFF
the fastboot devices command, however, does not return any results
inserting the adb rebbot fastboot command instead the phone starts correctly in lineage os fastboot mode and now the fastboot devices command gives the result
now I enter the folder where I copied the twrp image cd c:\platform-tools and I give the command fastboot boot twrp.img (the file is renamed TWRP)
but this is the result
c:\platform-tools>fastboot boot twrp.img
Sending 'boot.img' (33116 KB) OKAY [ 0.995s]
Booting FAILED (remote: 'Unrecognized command boot')
fastboot: error: Command failed
Can someone be kind enough to help me. I have made many different attempts to no avail.
Thank you!
Click to expand...
Click to collapse
Hello,
let me see if i can help,
but i need some info....
Which the LineageOS version
your device currently running ?
Is your 6T a global or T-Mobile version ?
hi, thanks for the reply. it is a secondary phone and has an old lineage version. yesterday with a different PC than usual I managed to install the latest version of twrp from cmd after solving a partition problem. i installed twrp only theoretically since after reboot the lineage prompt doesn't start and the boot stops at the screen with fastboot written... by forcibly turning it off I can access the bootloader. this is the current situation. 6t golobal...
developments ... from what I wrote above I could not get any progress. the device goes into bootloader mode manually but from the windows prompt it is not detected by the adb device command or by fastboot device .. so I can't advance ...
Going back to stock version does not necessarily
imply the use of a custom recovery,
you just need to use the MSM/rollback tool.
You can download it from THIS thread.
Use the earlier version of the tool as
you don't know wich exactly the
version of android installed in your device,
9.0.16 suggested.
When you will have a running device,
manually download and install OOS 9.0.17 firmware,
which will let your device to upgrade to android 10 and so on...
READ carefully @iaTa THREAD to follow exact MSM procedure.
Use a Windows pc and be sure
you have installed Oneplus driver.
Feel free to ask.