Related
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!
I've got DU 12.2 OFFICIAL installed on my phone now and am having some problems, Any gapps i try to install fails, i can receive calls but cant make any using data or wifi, my memory card works fine in the phone but doesn't show up on the computer, when i hook my phone up to the computer i cant get into download/fastboot mode, shows no devices on the devices command. i have to boot into fastboot by powering off the phone and doing the volume down + power then everything works fine. Any ideas what I may have done wrong or what the problem might be?? I was on stock Oreo 8.0 rooted w/twerp installed, done a full wipe a couple times before i flashed just to be safe..
Gapps are preinstalled. Do not flash any. I haven't had any calling issues with Sprint. Memory card shows up with adb disabled for windows and enabled for Linux. Adb reboot-bootloader works for me on both windows 7 and Linux. APM works as well from developer options (Advanced Power Menu).
Just my experiences running DU for the past two months
Uzephi said:
Gapps are preinstalled. Do not flash any. I haven't had any calling issues with Sprint. Memory card shows up with adb disabled for windows and enabled for Linux. Adb reboot-bootloader works for me on both windows 7 and Linux. APM works as well from developer options (Advanced Power Menu).
Just my experiences running DU for the past two months
Click to expand...
Click to collapse
Hi, what steps did you take to flash the rom?? I tried to reflash again with the same results. I wiped everything except OEM and micro SD card. did you flash the official or one of the weeklies?? this is the version ive been trying to flash: du_nash-v12.2-20180511-0850-OFFICIAL
blake .l said:
I've got DU 12.2 OFFICIAL installed on my phone now and am having some problems, Any gapps i try to install fails, i can receive calls but cant make any using data or wifi, my memory card works fine in the phone but doesn't show up on the computer, when i hook my phone up to the computer i cant get into download/fastboot mode, shows no devices on the devices command. i have to boot into fastboot by powering off the phone and doing the volume down + power then everything works fine. Any ideas what I may have done wrong or what the problem might be?? I was on stock Oreo 8.0 rooted w/twerp installed, done a full wipe a couple times before i flashed just to be safe..
Click to expand...
Click to collapse
I can give you my experience with DU. I ran the RC version which had recently had the issue with sdcard fixed. Like Uzephi said, no need for gapps, they're already baked in. As for adb/fastboot, you just need to reinstall the drivers, and manually add the moto adb driver when your device is in charge only mode. Then you should be able to run those commands just like always. I can elaborate more on that if you need. As far as flashing, I followed the flashing instructions for the AOSiP rom and flashed the 27.1 prep zip as well. Though the prep zip might be unnecessary if you have oreo on both slots. Uzephi would know better than I as far as that goes. I know the RCs and weeklies are signed differently, so no dirty flashing between the two. It might be better to flash the prep zip to have a clean slate on both slots.
Anyway, that was my experience. Hope that answers some of your questions.
blake .l said:
Hi, what steps did you take to flash the rom?? I tried to reflash again with the same results. I wiped everything except OEM and micro SD card. did you flash the official or one of the weeklies?? this is the version ive been trying to flash: du_nash-v12.2-20180511-0850-OFFICIAL
Click to expand...
Click to collapse
I use RC since I live on the wild side (I have tried to hard brick this phone so many times, only thing I won't try is locking BL since that's a stupid way to hard brick.) Airwalk says it perfectly. If you have Oreo on both slots, no need for the prep zip. I flash twrp.zip after booting into twrp, reboot recovery, flash rom, flash twrp again, reboot recovery, flash my kernel, flash magisk, reboot bootloader, fastboot -w, then boot to system.
Obviously I take more steps than needed. That's to flash my kernel, root and twrp after the flash before booting which isn't advised (wild child over here), you should fully boot first, then do the flashing of root, kernel, twrp, etc.
41rw4lk said:
I can give you my experience with DU. I ran the RC version which had recently had the issue with sdcard fixed. Like Uzephi said, no need for gapps, they're already baked in. As for adb/fastboot, you just need to reinstall the drivers, and manually add the moto adb driver when your device is in charge only mode. Then you should be able to run those commands just like always. I can elaborate more on that if you need. As far as flashing, I followed the flashing instructions for the AOSiP rom and flashed the 27.1 prep zip as well. Though the prep zip might be unnecessary if you have oreo on both slots. Uzephi would know better than I as far as that goes. I know the RCs and weeklies are signed differently, so no dirty flashing between the two. It might be better to flash the prep zip to have a clean slate on both slots.
Anyway, that was my experience. Hope that answers some of your questions.
Click to expand...
Click to collapse
You beat me to it! I think we have a race going on here, lol. You are correct 100% though
41rw4lk said:
I can give you my experience with DU. I ran the RC version which had recently had the issue with sdcard fixed. Like Uzephi said, no need for gapps, they're already baked in. As for adb/fastboot, you just need to reinstall the drivers, and manually add the moto adb driver when your device is in charge only mode. Then you should be able to run those commands just like always. I can elaborate more on that if you need. As far as flashing, I followed the flashing instructions for the AOSiP rom and flashed the 27.1 prep zip as well. Though the prep zip might be unnecessary if you have oreo on both slots. Uzephi would know better than I as far as that goes. I know the RCs and weeklies are signed differently, so no dirty flashing between the two. It might be better to flash the prep zip to have a clean slate on both slots.
Anyway, that was my experience. Hope that answers some of your questions.
Click to expand...
Click to collapse
Good deal brother thanks for the info.... I will give it a try for sure.....
blake .l said:
Good deal brother thanks for the info.... I will give it a try for sure.....
Click to expand...
Click to collapse
Let us know how it goes
Uzephi said:
Let us know how it goes
Click to expand...
Click to collapse
Well guys I followed the the flashing instructions for the install guide from the AOSiP ROM to the "T" going from stock 27.1 Oreo 4 different times today to no avail, I came up with the same outcome as before. No calling, mem card not showing up on computer, having to manually boot into fastboot and so on. I downloaded Los 15.1 and followed the same procedure as with DU and it works like a charm. I just hope now it keeps getting updates Thanks again for your help and suggestions guys
blake .l said:
Well guys I followed the the flashing instructions for the install guide from the AOSiP ROM to the "T" going from stock 27.1 Oreo 4 different times today to no avail, I came up with the same outcome as before. No calling, mem card not showing up on computer, having to manually boot into fastboot and so on. I downloaded Los 15.1 and followed the same procedure as with DU and it works like a charm. I just hope now it keeps getting updates Thanks again for your help and suggestions guys
Click to expand...
Click to collapse
Try the RC from 0509. I have been running it since the 9th with no issues.
I've tried to follow the instructions here (https://plus.google.com/communities...5/stream/2a745c1e-aae6-4b50-93dd-14417258d7ce).
I did a huge mistake of thinking that flashing for slot a and slot b was the same of step (2/2) I saw in the screen.
I was coming from Stock Nougat (7.1.1) and, most probably, I finished having oreo in one slot and nougat in the other.
I reflashed TWRP as per instructions.
When I tried to reboot, phone got dead (no charge, no turning on, and no bootloader...). This scared me totally. I unbrick some Asus, Google and Samsung before. But this time it was too premature and having no bootloader is unbelievable.
Will the AOSiP guide will work now for me? I'm with Oreo (don't know how to check if on both slots...), but if a new phone.
Does anybody know why we can't have a DU thread here in xda?
Technical said:
I've tried to follow the instructions here (https://plus.google.com/communities...5/stream/2a745c1e-aae6-4b50-93dd-14417258d7ce).
I did a huge mistake of thinking that flashing for slot a and slot b was the same of step (2/2) I saw in the screen.
I was coming from Stock Nougat (7.1.1) and, most probably, I finished having oreo in one slot and nougat in the other.
I reflashed TWRP as per instructions.
When I tried to reboot, phone got dead (no charge, no turning on, and no bootloader...). This scared me totally. I unbrick some Asus, Google and Samsung before. But this time it was too premature and having no bootloader is unbelievable.
Will the AOSiP guide will work now for me? I'm with Oreo (don't know how to check if on both slots...), but if a new phone.
Does anybody know why we can't have a DU thread here in xda?
Click to expand...
Click to collapse
See this thread for my experience with a similar issuehttps://forum.xda-developers.com/z2-force/help/gotta-super-slim-brick-t3798403
mookiexl said:
See this thread for my experience with a similar issuehttps://forum.xda-developers.com/z2-force/help/gotta-super-slim-brick-t3798403
Click to expand...
Click to collapse
Posted there, thanks. But I'm not sure if it is all the same, for all Z2 models. I can't find a DU step by step tutorial. There are some details that expert people are not writing and I'm new to Motorola, slot a/b, etc. I'm not a newbie, just that this phone has a lot of peculiarities...
Technical said:
Posted there, thanks. But I'm not sure if it is all the same, for all Z2 models. I can't find a DU step by step tutorial. There are some details that expert people are not writing and I'm new to Motorola, slot a/b, etc. I'm not a newbie, just that this phone has a lot of peculiarities...
Click to expand...
Click to collapse
My AOSiP instructions is how I installed to the T. I did no other steps. I did that on every install from stock to an AOSP based ROM. I have not yet bricked to 9008 mode to try blank flashing yet to verify instructions on how to do that.
Uzephi said:
My AOSiP instructions is how I installed to the T. I did no other steps. I did that on every install from stock to an AOSP based ROM. I have not yet bricked to 9008 mode to try blank flashing yet to verify instructions on how to do that.
Click to expand...
Click to collapse
Thanks. I've moved to https://forum.xda-developers.com/showpost.php?p=76754449&postcount=24 to ask you about .zip preparation file for XT1789-05 model.
Uzephi said:
Try the RC from 0509. I have been running it since the 9th with no issues.
Click to expand...
Click to collapse
Well I tried the RC from 05/09/18 and the newest version of RC, followed the same flashing guide to the "T"and got the same results, phone can receive calls but cant make any, cant boot to fastboot through computer etc. went back to Los and all works fine. I dont know what the problem is wit DU and my phone..
blake .l said:
Well I tried the RC from 05/09/18 and the newest version of RC, followed the same flashing guide to the "T"and got the same results, phone can receive calls but cant make any, cant boot to fastboot through computer etc. went back to Los and all works fine. I dont know what the problem is wit DU and my phone..
Click to expand...
Click to collapse
They tell you need to flash to both slots. Here on xda, devs say we need to flash ROM just to one slot. Of course, I'm not sure this is the problem. Just trying to imagine myself at DU.
By the way, are there any settings (customization) present in DU that AOSIP does not have?
Technical said:
They tell you need to flash to both slots. Here on xda, devs say we need to flash ROM just to one slot. Of course, I'm not sure this is the problem. Just trying to imagine myself at DU.
By the way, are there any settings (customization) present in DU that AOSIP does not have?
Click to expand...
Click to collapse
A few things, yes. Mainly the dirty tweaks in settings
Didn't really care for the DU. Although it does have working 4g on sprint(much props there). I just didn't personally like the "feel" of it. I'm rockin the unofficial LOS 15.1 right now and its pretty lovely. I'm limited to ROMs b/c of sprint but so far LOS kicks ass.
First, let me say I have been using rooted phones with twrp for several years and never had the slightest problem with them, so I generally know what I am doing, but the Mi A2 Lite is just a disaster area for me, not with Magisk, that works fine, but twrp seems impossible for me to install on 10.0.3.0 without soft bricking ( I had twrp installed on 10.0.2.0 and 10.0.1.0 so I am not unfamiliar with the method, but on 10.0.3.0 - no way). I have done so many factory resets now I have my own parking space at the factory! (That is humour btw).
So I wondered if a different approach to the problem might work. I am not a coder or phone guru, so what I propose might be nonsense, if it is I am sure somebody will tell me.
We are all used to the concept of the 'patched_boot.img' created by Magisk and if you don't want to produce your own version the forum usually has a link to it. Magisk though is not the problem, twrp is, so what I am proposing is that somebody provides a link to a 'double_patched_boot.img' ie a flashable boot image that contains both twrp and magisk and that can directly replace the stock boot via fastboot.
Apparently there are some folks that have managed to install both twrp and magisk on 10.0.3.0, so if one of them could extract the 'double_patched_boot.img' from their phone it might help out a lot. How do you achieve that? Well there is probably more than one way, but the way that I would choose (if I could manage to install them both in the first place) is to boot into twrp, connect to pc, take a miflash backup of the phone and then unzip it with the following command (this is a linux command I am sure someone can provide a windows equivalent):
Code:
tar -xzf ********.tgz
where ********.tgz is the name of your miflash backup.
Then extract the boot.img from the resulting folder, rename it to something like 'double_patched_boot_10.0.3.0.img' and provide a link to it on the forum. Then some brave soul could try it out (probably not me as I am sick of doing factory resets and don't have any backups because I don't have any recovery to make them from).
OTOH this might just not be practical, I don't know enough to be sure.
i was having similar issues. replaced my mi a2 lite and followed the guide for the aosp 109 gsi here in the forum replacing the fstab and one other file i forgot they name but it's instructed. i have twrp zero the fixed one, magisk, and I'm running the RR PIE ROM with zero issues and I've been back and forth in and out of recovery no problem. I'm pretty sure it will work for you too.
12:121390 said:
i was having similar issues. replaced my mi a2 lite and followed the guide for the aosp 109 gsi here in the forum replacing the fstab and one other file i forgot they name but it's instructed. i have twrp zero the fixed one, magisk, and I'm running the RR PIE ROM with zero issues and I've been back and forth in and out of recovery no problem. I'm pretty sure it will work for you too.
Click to expand...
Click to collapse
Interesting. I have certainly thought of jumping ship to a custom rom, but I would like to wait a little before I do so, ideally until someone fires up a Lineage rom for the A2 Lite. But if things continue as badly as they have done so far with stock roms then I might well join you on RR.
viking777 said:
Interesting. I have certainly thought of jumping ship to a custom rom, but I would like to wait a little before I do so, ideally until someone fires up a Lineage rom for the A2 Lite. But if things continue as badly as they have done so far with stock roms then I might well join you on RR.
Click to expand...
Click to collapse
also because of the new ARB thing, custom is much safer, i think i bricked my last device rolling back from ota 9.0 software to ota 8.1. that's a non-issue with custom. just something to be wary of. the current RR pie gsi is near flawless for he so far. hope that helps a little
12:121390 said:
also because of the new ARB thing, custom is much safer, i think i bricked my last device rolling back from ota 9.0 software to ota 8.1. that's a non-issue with custom. just something to be wary of. the current RR pie gsi is near flawless for he so far. hope that helps a little
Click to expand...
Click to collapse
Anti roll back is disabled and not an issue if bootloader is unlocked
Nice thread. Tried it as well but no chance 10.0.3.00 + twrp + magisk. And you are right the problem is twrp.
Sent from my Phh-Treble vanilla using Tapatalk
12:121390 said:
i was having similar issues. replaced my mi a2 lite and followed the guide for the aosp 109 gsi here in the forum replacing the fstab and one other file i forgot they name but it's instructed. i have twrp zero the fixed one, magisk, and I'm running the RR PIE ROM with zero issues and I've been back and forth in and out of recovery no problem. I'm pretty sure it will work for you too.
Click to expand...
Click to collapse
Does RR Pie have any issues on Mi A2 Lite? Whichever GSI I'd tried, I had lags :/
12:121390 said:
i was having similar issues. replaced my mi a2 lite and followed the guide for the aosp 109 gsi here in the forum replacing the fstab and one other file i forgot they name but it's instructed. i have twrp zero the fixed one, magisk, and I'm running the RR PIE ROM with zero issues and I've been back and forth in and out of recovery no problem. I'm pretty sure it will work for you too.
Click to expand...
Click to collapse
brother i also want to install RR PIE Rom can you please give me the guide link?
hossman said:
Anti roll back is disabled and not an issue if bootloader is unlocked
Click to expand...
Click to collapse
correct it is not. what happened was.. lol. i thought i was crafty and did some file swapping and made miflash setups that would flash so the stock files as usual , but with gsi's like RR and/or bootleggers for the system image. and it works, up until i flashed from RR to bootleggers with those setups described previously . there is where my genius was flawed. lol. lesson learned
---------- Post added at 06:43 AM ---------- Previous post was at 06:38 AM ----------
marstonpear said:
Does RR Pie have any issues on Mi A2 Lite? Whichever GSI I'd tried, I had lags :/
Click to expand...
Click to collapse
for me, i have not come across anything caused by the GSI. any issues I've faced are purely self inflicted.
I don´t get your problems... Just boot twrp, and install it as described in original thread.
After that flash back aboot from 9.6.11.0 and the message "your system got destroyed" will disappear!
Voodoojonny said:
I don´t get your problems... Just boot twrp, and install it as described in original thread.
After that flash back aboot from 9.6.11.0 and the message "your system got destroyed" will disappear!
Click to expand...
Click to collapse
You might not get my problem, but likewise I don't get your solution. Firstly aboot has never been touched during the attempted twrp install so why flash it at all, it has not been changed, and secondly you suggest I flash it with something that is how many versions old 4?, 5?, I'm not sure, when just about every post you ever read stresses that you should not mix old and new partitions at the same time.
I hope you forgive my scepticism, but can you actually suggest the slightest reason why this might work?
Or is it all just voodoo johnny (sorry, couldn't resist that).
viking777 said:
You might not get my problem, but likewise I don't get your solution. Firstly aboot has never been touched during the attempted twrp install so why flash it at all, it has not been changed, and secondly you suggest I flash it with something that is how many versions old 4?, 5?, I'm not sure, when just about every post you ever read stresses that you should not mix old and new partitions at the same time.
I hope you forgive my scepticism, but can you actually suggest the slightest reason why this might work?
Or is it all just voodoo johnny (sorry, couldn't resist that).
Click to expand...
Click to collapse
Aboot is the bootloader. Since Pie the aboot was modified to check wheather there are modification on your boot.img. So everytime you modify something (like installing twrp), you get the message "your system got destroyed".
9.6.11.0 is the last version of Oreo. Here the bootloader didn´t check boot.img.
That´s why you need to flash 9.6.11.0 - maybe the older verstions will work too. Didn´t check. But I guess only 9.6.11.0 will work becouse it was the latest oreo version and it had to have a bootloader which can boot up pie (to have ota working).
Here you can find the aboot.img I use... and which works without any problem on pie - right now I´m running 10.0.3.0...
Just flash it via fastboot.
Voodoojonny said:
Aboot is the bootloader. Since Pie the aboot was modified to check wheather there are modification on your boot.img. So everytime you modify something (like installing twrp), you get the message "your system got destroyed".
9.6.11.0 is the last version of Oreo. Here the bootloader didn´t check boot.img.
That´s why you need to flash 9.6.11.0 - maybe the older verstions will work too. Didn´t check. But I guess only 9.6.11.0 will work becouse it was the latest oreo version and it had to have a bootloader which can boot up pie (to have ota working).
Here you can find the aboot.img I use... and which works without any problem on pie - right now I´m running 10.0.3.0...
Just flash it via fastboot.
Click to expand...
Click to collapse
OK that makes sense now - thank you for the explanation. I will probably give that a try sometime, but not right now as I have a stable working phone for the first time in ages and I don't want to jeopardise that.
Just one question though. When I had twrp installed on 10.0.2.0, it was fine at doing backups, but on the two occasions I tried to restore with them they failed, by which I don't mean that the restore didn't repair the phone, but that it was impossible to even carry out the restore, it started but did not complete - just ended with 'Restore Failed' message.
Have you tried any restores with twrp installed in the manner you suggest and if so did they work? No point in installing it otherwise.
viking777 said:
OK that makes sense now - thank you for the explanation. I will probably give that a try sometime, but not right now as I have a stable working phone for the first time in ages and I don't want to jeopardise that.
Just one question though. When I had twrp installed on 10.0.2.0, it was fine at doing backups, but on the two occasions I tried to restore with them they failed, by which I don't mean that the restore didn't repair the phone, but that it was impossible to even carry out the restore, it started but did not complete - just ended with 'Restore Failed' message.
Have you tried any restores with twrp installed in the manner you suggest and if so did they work? No point in installing it otherwise.
Click to expand...
Click to collapse
There seems to be some bugs restoring system and vendor... Some users talked about... I usually only save and restore the data and boot partition and I never had any problems with that. For all other partitions you can use miflash or fastboot...
Yeah all my twrp full backups don't work after a fresh stock installment either, that's very annoying.
The twrp version for daisy is bugged. Backups are not working, the wifi with GSI Roms on pie stock is not working anymore as soon as twrp is installed as well.
Sent from my Phh-Treble vanilla using Tapatalk
Thanks for the replies above. @voodoojohnny
In my case it was the data partition that caused the restore to fail, vendor and system and boot all seemed to go through normally. @cd492
Based on what you say along with my own experiences and those of voovoojohnny, it looks like twrp is more trouble than it is worth at the moment. I think I will make do without it for now and hope for a better version in the future.
viking777 said:
First, let me say I have been using rooted phones with twrp for several years and never had the slightest problem with them, so I generally know what I am doing, but the Mi A2 Lite is just a disaster area for me, not with Magisk, that works fine, but twrp seems impossible for me to install on 10.0.3.0 without soft bricking ( I had twrp installed on 10.0.2.0 and 10.0.1.0 so I am not unfamiliar with the method, but on 10.0.3.0 - no way). I have done so many factory resets now I have my own parking space at the factory! (That is humour btw).
So I wondered if a different approach to the problem might work. I am not a coder or phone guru, so what I propose might be nonsense, if it is I am sure somebody will tell me.
We are all used to the concept of the 'patched_boot.img' created by Magisk and if you don't want to produce your own version the forum usually has a link to it. Magisk though is not the problem, twrp is, so what I am proposing is that somebody provides a link to a 'double_patched_boot.img' ie a flashable boot image that contains both twrp and magisk and that can directly replace the stock boot via fastboot.
Apparently there are some folks that have managed to install both twrp and magisk on 10.0.3.0, so if one of them could extract the 'double_patched_boot.img' from their phone it might help out a lot. How do you achieve that? Well there is probably more than one way, but the way that I would choose (if I could manage to install them both in the first place) is to boot into twrp, connect to pc, take a miflash backup of the phone and then unzip it with the following command (this is a linux command I am sure someone can provide a windows equivalent):
where ********.tgz is the name of your miflash backup.
Then extract the boot.img from the resulting folder, rename it to something like 'double_patched_boot_10.0.3.0.img' and provide a link to it on the forum. Then some brave soul could try it out (probably not me as I am sick of doing factory resets and don't have any backups because I don't have any recovery to make them from).
OTOH this might just not be practical, I don't know enough to be sure.
Click to expand...
Click to collapse
THIS HAS NOT BEEN TESTED ON GSI'S YET
I'm currently in the process of RR with TWRP but having extreme Encryption errors
Grab these two files (Big Thanks to Zerovoid, Seryioo, and mac12m99)
Fixed SDCard Support TWRP Image File (Put this on your SDCard and Computer)-
https://forum.xda-developers.com/mi...unofficial-twrp-daisy-mount-sd-fixed-t3889390
Fixed SDCard Support TWRP Installer Zip (Put this on your SDCard)-
https://androidfilehost.com/?fid=11410963190603893418
But I got TWRP on 10.0.3.0 with magisk, and Justic Kernel.
THIS WILL WIPE YOUR DEVICE I'M DEFINITELY NOT RESPONSIBLE FOR LOST DATA
Start with the phone being on with USB Debugging enabled correctly
Type adb reboot bootloader
So flash the 10.0.3.0 ROM through MiFlash using the flash_all.bat, this process has to be done so backup your data before erasing.
After it is done flashing it restarts, go ahead and hold power and volume down right back to the Bootloader
Type: fastboot boot twrp-3.2.3-0-daisy_zero.img
It would boot into TWRP, if you see something about decryption hit cancel this may mean you haven't followed directions so far
Tap install and find your SD Card, find the fixed-twrp-installer-daisy.zip where ever you put it on your SD Card and install it, this process takes a few minutes when finished DO NOT HIT REBOOT SYSTEM!
Hit the home button back to TWRP home screen and tap reboot >>> bootloader
Download this to your computer - https://androidfilehost.com/?fid=11410963190603884024
Type: fastboot flash aboot aboot_9.6.4.img
Then type: fastboot reboot
Afterwards your phone shall boot up to Android if it does hold power and volume up and release power and keep hold volume up when the screen turns back on to go-to recovery, if TWRP boots up you have successfully completed the task.
Now flash Magisk zip (optional)
Hopefully this helped kind of my first tutorial, this was my process.
InfinityXDA said:
THIS HAS NOT BEEN TESTED ON GSI'S YET
I'm currently in the process of RR with TWRP but having extreme Encryption errors
Grab these two files (Big Thanks to Zerovoid, Seryioo, and mac12m99)
Fixed SDCard Support TWRP Image File (Put this on your SDCard and Computer)-
https://forum.xda-developers.com/mi...unofficial-twrp-daisy-mount-sd-fixed-t3889390
Fixed SDCard Support TWRP Installer Zip (Put this on your SDCard)-
https://androidfilehost.com/?fid=11410963190603893418
But I got TWRP on 10.0.3.0 with magisk, and Justic Kernel.
THIS WILL WIPE YOUR DEVICE I'M DEFINITELY NOT RESPONSIBLE FOR LOST DATA
Start with the phone being on with USB Debugging enabled correctly
Type adb reboot bootloader
So flash the 10.0.3.0 ROM through MiFlash using the flash_all.bat, this process has to be done so backup your data before erasing.
After it is done flashing it restarts, go ahead and hold power and volume down right back to the Bootloader
Type: fastboot boot twrp-3.2.3-0-daisy_zero.img
It would boot into TWRP, if you see something about decryption hit cancel this may mean you haven't followed directions so far
Tap install and find your SD Card, find the fixed-twrp-installer-daisy.zip where ever you put it on your SD Card and install it, this process takes a few minutes when finished DO NOT HIT REBOOT SYSTEM!
Hit the home button back to TWRP home screen and tap reboot >>> bootloader
Download this to your computer - https://androidfilehost.com/?fid=11410963190603884024
Type: fastboot flash aboot aboot_9.6.4.img
Then type: fastboot reboot
Afterwards your phone shall boot up to Android if it does hold power and volume up and release power and keep hold volume up when the screen turns back on to go-to recovery, if TWRP boots up you have successfully completed the task.
Now flash Magisk zip (optional)
Hopefully this helped kind of my first tutorial, this was my process.
Click to expand...
Click to collapse
Thank you very much for posting this process in such detail, unfortunately I think you must have missed my last post where I said:
it looks like twrp is more trouble than it is worth at the moment. I think I will make do without it for now and hope for a better version in the future.
Click to expand...
Click to collapse
I meant it, at least for now, but maybe your post will help somebody else.
viking777 said:
Thank you very much for posting this process in such detail, unfortunately I think you must have missed my last post where I said:
I meant it, at least for now, but maybe your post will help somebody else.
Click to expand...
Click to collapse
Yes I didn't see that post but understand I didn't give you links to the official TWRP, I gave you the unofficial fixed TWRP which actually features SD Card Support and trust me it works completely fine I haven't had a problem yet. This took me hours upon hours to figure out what I was doing wrong.
The only specific reason you are not successfully getting TWRP is because you didn't flash the aboot.img after installing the zip.
I hope this helps you in the future!
thanks InfinityXDA for the tutorial, you should create a post just for it~
****** Would really appreciate some help here...
I've tried to install quick reboot (zips), magik, (zips) and busybox, on 3.4 0-0 twrp, and it won't work to boot to system, still says on this version it cannot mount the system. I don't have the perma-recovery file as I cannot find it online, and nexus root toolkit doesn't download it in the dispensaries, latest version.
Hope I haven't knacked it, i also have some screenshots but it doesn't matter as I cannot access the system itself, unless i am missing something it should just boot back to system, I don't understand what I am doing wrong, or have done wrong. Got the img and everything with it.
That said, the mount storage issue is the only thing red, or wrong in the flash, everything else worked apparently, said it installed without a hitch. Which was different that with the standard NRT downloaded twrp, with supersu, as that didn't work.
It just goes back to twrp constantly, can't boot. Help. Really wish I just waited for a response here first. Also I don't believe this is a bootloop, as it just goes back to twrp not bootloader or anything else, probably wrong.
I have been using this vid from the start: realizing that wasn't doing it, magik and a new bionic busybox zip eventually did the trick on 3.4 0-0 twrp, but it sitll won't boot to system. It is probably something obvious, I have been on this for hours today and yesterday, no luck.
only thing i can think of is something to do with: fastboot flash recovery twrp-3.2.1-0-fbe-4core-bullhead.img
basically i flashed the latest version, i dunno if it's supported by nexus 5x.
thanks. uh just please say it ain't bricked.
Anyone?!
edit:
hi all, after immense pain, stress and struggle to get the thing to mount, and trying everything suggested online, it eventually just like "soft-bricked" or whatever, like it was just perma-stuck on the google screen and wouldn't boot to system. i am guessing it's because after a mistake it wiped the system.
i have managed to flash it back to stock, everything is there, and/or redownloading. no way am i gonna bother again, like if it ain't broke don't fix it at this point that would be foolish thought it was perma broke. i'm gonna get a profressional to do it or something, or to give me one to one support to try it again. in the meantime i am going to learn more about rooting and the NRT and all the fundamentals of that.
if anyone here has advice about this still, or articles where I can read about it online, where to learn etc. I'd appreciate that as well, thanks.
Cam3333 said:
****** Would really appreciate some help here...
I've tried to install quick reboot (zips), magik, (zips) and busybox, on 3.4 0-0 twrp, and it won't work to boot to system, still says on this version it cannot mount the system. I don't have the perma-recovery file as I cannot find it online, and nexus root toolkit doesn't download it in the dispensaries, latest version.
Hope I haven't knacked it, i also have some screenshots but it doesn't matter as I cannot access the system itself, unless i am missing something it should just boot back to system, I don't understand what I am doing wrong, or have done wrong. Got the img and everything with it.
That said, the mount storage issue is the only thing red, or wrong in the flash, everything else worked apparently, said it installed without a hitch. Which was different that with the standard NRT downloaded twrp, with supersu, as that didn't work.
It just goes back to twrp constantly, can't boot. Help. Really wish I just waited for a response here first. Also I don't believe this is a bootloop, as it just goes back to twrp not bootloader or anything else, probably wrong.
I have been using this vid from the start: realizing that wasn't doing it, magik and a new bionic busybox zip eventually did the trick on 3.4 0-0 twrp, but it sitll won't boot to system. It is probably something obvious, I have been on this for hours today and yesterday, no luck.
only thing i can think of is something to do with: fastboot flash recovery twrp-3.2.1-0-fbe-4core-bullhead.img
basically i flashed the latest version, i dunno if it's supported by nexus 5x.
thanks. uh just please say it ain't bricked.
Click to expand...
Click to collapse
issues such as what youve experienced are usually caused by version mismatches. I dont have this device and am unfamiliar with the root process for it, but it shouldnt be too different from any other phone. what is the baseband version of your actual phone?
look at this specific reply in this thread
GUIDE - Fix bootloop with locked bootloader via ADB/Fastboot (Android M, N, O)
Hi, Here is fix for those, who have problem with bootloop on 5X with locked bootloader and OEM unlock disabled. This tutorial works for Beta Android O bootloop too. You will need: ADB + drivers installed...
forum.xda-developers.com
So firstly i have been doing this myself when necessary for many years now thanks XDA Devs!
The device im using is always just a pokemon go spoof device, maybe the odd game for kids but strictly trashable in the passed. Part of the saftest method to set up the device was that i couldnt backup via TWRP. I didnt care anything i needed was saved on the cloud via game accounts...
Unfortunalty a few months ago i accidently updated from 10 to 11 and it killed my setup.. i was in the mood to fix it off i went. the same methods appeared to be identical for 10 to 11 just newer versions.....
I destroyed my everyday phones camera so i was using the pixel to save important info , only some of which i backed up correctly.. these include keys to wallets. my backup keys....
I stupidy went headfirst into doing the same thing i had done numerous times for myself and others. Its a pretty noob mistake i know.
Im pretty sure i can flash my way back without loosing data, but i need to be 100%.
I believe sideloading the OTA is safe for what i want, but i also see the backup your data warning hitting me on the forehead. Not trusting myself here at the minute.
was android 10 rooted and smali patcher, updated to Android 11... untoached, unlocked bootloader, dev enabled.
Obviosly Pixle 2 XL
Build rp1a.201005.004.a1
So i simply booted TWRP.img v 3.3.0-0 then installed the zip. normal permission errors FAILED TO MOUNT '/SYSTEM (INVALID ARGUMENT)
never needed to care before and wasnt thinking BACKUP.
I renamed magisk v23.0 apk to .zip like normal... installed via TWRP like normal.... whats not normal is im stuck with the loading bar under the G on the splash screen.
It only ever had this problem with samali but it just takes a bit.
I apologise for the story and not getting straight to it but i feel like a clown for this one and felt the need to explain my noobie mistake.
All i care about it a way back to booting up the device with my data intact so i can make it safe. i can knock down and rebuild the setup i need myself, i have been doing this long enough. really just want the clarity on a sure thing way back to my data.
Cheers yall, FYI u can take the micky out of me if you like i get it hahah.
Hi! Did you try to:
Code:
fastboot boot boot.img
from bootloader?
If you will use untouched boot.img from ROM you have on phone, it could boot normally if bootloop happend after magisk patching.
If you will sideload ota image, your data should stay on their place.
somin.n said:
Hi! Did you try to:
Code:
fastboot boot boot.img
from bootloader?
If you will use untouched boot.img from ROM you have on phone, it could boot normally if bootloop happend after magisk patching.
If you will sideload ota image, your data should stay on their place.
Click to expand...
Click to collapse
I Actually had not tried a thing once i realised what i could be losing, i had to drop my understanding and pride and triple check my methods.
I extracted boot.img from stock Firmware and fastooted back into the OS. Cheers.
I had that ready to go i almost did it before opening the thread..
I appreciate your time thanks buddy, highly appreciated.