Related
I have re-flashed factory firmware multiple times now, but I'm still not 100% sure if both boot slots are 100% factory.
Usually after I execute flash-all.bat WITH userdata format, it always reflashes slot A. (besides system_other) Does this mean that boot slot B is not "fresh"???
I'm assuming not because I was on NMF26Q and I wanted to flash Resurrection Remix, which is requiring NOF26V vendor image. After I executed flash-all.bat WITH userdata format and flashing RR, I was on boot slot B and it showed that my vendor image was NMF26Q.
Is there a way to flash both boot slots in case of a RMA and I need to relock bootloader?
* Yes my platform-tools are up to date.
* Yes I watch it flash everything till the end with out fail.
Anutter226 said:
I have re-flashed factory firmware multiple times now, but I'm still not 100% sure if both boot slots are 100% factory.
Usually after I execute flash-all.batWITH userdata format, it always reflashes slot A. (besides system_other) Does this mean that boot slot B is not "fresh"???
I'm assuming not because I was on NMF26Q and I wanted to flash Resurrection Remix, which is requiring NOF26V vendor image. After I executed flash-all.batWITH userdata format and flashing RR, I was on boot slot B and it showed that my vendor image was NMF26Q.
Is there a way to flash both boot slots in case of a RMA and I need to relock bootloader?
* Yes my platform-tools are up to date.
* Yes I watch it flash everything till the end with out fail.
Click to expand...
Click to collapse
I imagine it's overkill but you could just switch the active slot and run flash-all again. As a precaution I would recommend booting into the OS after the first flash-all to make sure it flashed ok. If there happens to be some problem like a bad flash or wrong download you want to be sure that the "other" slot is bootable. Otherwise you might end up with a pair of unbootable slots which could get sticky.
Anutter226 said:
* Yes I watch it flash everything till the end with out fail.
Click to expand...
Click to collapse
then you saw that flash-all.bat flashed both slots
V40 said:
then you saw that flash-all.bat flashed both slots
Click to expand...
Click to collapse
Doesn't flash to both slots on mine
canemaxx said:
Doesn't flash to both slots on mine
Click to expand...
Click to collapse
I believe it flashes to one slot and deletes the data on the other as standard
If you guys would read your terminal output after flashing you would know what gets flashed where. People are making this way to complicated. It is a big change from previous devices but once you know the partitions its pretty easy.
One data slot shared by A + B
Slot A & B have separate partitions for
-Vendor
-Bootloader
-Radio
-Modem
-Boot
-System
Flashall.bat flashes your active slot and installs system_other.img to the inactive system partition and wipes data, unless you edit the flashall.bat and erase -w.
Thats it. Now, how people are handling the two slots is another story. I keep both slots identical. Having two different bootloaders is a recipe for bricks in my opinion.
FWIW, I endorse the post above this one. I would only add if you get in trouble flash all without the -w and then change the active slot and flash all without the-w again.
Golf c said:
Having two different bootloaders is a recipe for bricks in my opinion.
Click to expand...
Click to collapse
Hello,
This makes me think:
With April stock on slot a for example, you accept May OTA... It will write the new bootloader to the inactive slot b.
So there will be two different bootloader anyway, no?
Cheers...
5.1 said:
Hello,
This makes me think:
With April stock on slot a for example, you accept May OTA... It will write the new bootloader to the inactive slot b.
So there will be two different bootloader anyway, no?
Cheers...
Click to expand...
Click to collapse
Yes but your not flashing custom roms and switching slots every flash. Flashing custom roms switches to the inactive slot. Food for thought. I don't know or want to know to much about hard bricking, but Afaik most of the hard bricks involve OTA's. Hence my best practices theory. Same bootloader in both slots. Somebody with more brick knowledge please correct me if I'm wrong?
Golf c said:
Yes but your not flashing custom roms and switching slots every flash. Flashing custom roms switches to the inactive slot. Food for thought. I don't know or want to know to much about hard bricking, but Afaik most of the hard bricks involve OTA's. Hence my best practices theory. Same bootloader in both slots. Somebody with more brick knowledge please correct me if I'm wrong?
Click to expand...
Click to collapse
Hey,
I started fresh before Pure Nexus and flashed NHG47K to both slots.
Anyway, i wiped, reinstalled, a few times since. But the ROM keeps installing to the same slot. It doesn't switch. The second slot still has stock install.
Switched a to b and booted stock. Switch back on a and back to PN...
Of course i'm no expert or developer either.
Where I agree is that custom could create problems I don't know either.
Cheers...
5.1 said:
Hey,
I started fresh before Pure Nexus and flashed NHG47K to both slots.
Anyway, i wiped, reinstalled, a few times since. But the ROM keeps installing to the same slot. It doesn't switch. The second slot still has stock install.
Switched a to b and booted stock. Switch back on a and back to PN...
Of course i'm no expert or developer either.
Where I agree is that custom could create problems I don't know either.
Cheers...
Click to expand...
Click to collapse
Never heard of this. Some people are flashing the same slot on purpose by switching slots before they flash the rom. I have never had any rom I have tried not switch slots. I haven't been on stock since Dirty Unicorns came out in December.
Golf c said:
Never heard of this. Some people are flashing the same slot on purpose by switching slots before they flash the rom. I have never had any rom I have tried not switch slots. I haven't been on stock since Dirty Unicorns came out in December.
Click to expand...
Click to collapse
Hey,
Maybe I'm doing it the wrong way then
Well, I kept having a weird issue, so just rebooted to TWRP, wipe everything except internal storage and reinstall from here: ROM, TWRP zip, reboot TWRP > reinstall vendor, reboot... Never switched slot.
Check this: https://postimg.org/gallery/2muhcz91o/
Slot a is PN, slot b is stock NHG47K.
Cheers...
5.1 said:
Hey,
Maybe I'm doing it the wrong way then
Well, I kept having a weird issue, so just rebooted to TWRP, wipe everything except internal storage and reinstall from here: ROM, TWRP zip, reboot TWRP > reinstall vendor, reboot... Never switched slot.
Check this: https://postimg.org/gallery/2muhcz91o/
Slot a is PN, slot b is stock NHG47K.
Cheers...
Click to expand...
Click to collapse
Somehow you must be switching slots before flashing PN. There is several ways to do it. I think as long as you know what's in the inactive slot, you should be good. My problem is the people that always flash to the same slot could have old bootloaders from who knows what build. You hit the wrong button and your dead.
Golf c said:
Somehow you must be switching slots before flashing PN. There is several ways to do it. I think as long as you know what's in the inactive slot, you should be good. My problem is the people that always flash to the same slot could have old bootloaders from who knows what build. You hit the wrong button and your dead.
Click to expand...
Click to collapse
Hey,
If I do it, i sincerely don't know how or when...
By the way, i just noticed a few apps misbehaving when i manually switched slot from bootloader to boot stock... Now I'm back on PN, i see it kind of messed up some apps permissions. And my browser kept FC even though I wiped its data and cache. Had to reinstall it, lol.
Well, I guess I'll have to install my phone over again...
Cheers...
Delete
---------- Post added at 11:54 PM ---------- Previous post was at 11:48 PM ----------
5.1 said:
Hey,
If I do it, i sincerely don't know how or when...
By the way, i just noticed a few apps misbehaving when i manually switched slot from bootloader to boot stock... Now I'm back on PN, i see it kind of messed up some apps permissions. And my browser kept FC even though I wiped its data and cache. Had to reinstall it, lol.
Well, I guess I'll have to install my phone over again...
Cheers...
Click to expand...
Click to collapse
Afaik you can't run two different roms on Pixel because of the shared data partition. Hence your app problems. I heard stories about people doing it with some quasi work arounds. I think you can run same rom, one rooted, one non rooted. Not worth the reboot for me.
Golf c said:
Delete
---------- Post added at 11:54 PM ---------- Previous post was at 11:48 PM ----------
Afaik you can't run two different roms on Pixel because of the shared data partition. Hence your app problems. I heard stories about people doing it with some quasi work arounds. I think you can run same rom, one rooted, one non rooted. Not worth the reboot for me.
Click to expand...
Click to collapse
Hey,
I did it just to show something to someone earlier. I don't need dual boot either...
One ROM is enough in my opinion.
Ok, time to hit the bed. See you later...
Cheers...
People are looking at this setup like a dual boot computer setup. That isnt what it is or how it works. Its using the same data....which includes all your settings. Boot, kernel and ram disk are in one partition now. There are a ton of moving parts we don't even know about.
This is a fancy update system, just like Chromebooks and iPhones.
TonikJDK said:
People are looking at this setup like a dual boot computer setup. That isnt what it is or how it works. Its using the same data....which includes all your settings. Boot, kernel and ram disk are in one partition now. There are a ton of moving parts we don't even know about.
This is a fancy update system, just like Chromebooks and iPhones.
Click to expand...
Click to collapse
And I don't even use it because I have never taken an OTA. lol!
I'm glad I read this thread. I have just installed the L build and flashed the April bootloader. This took place on slot b and I want slot a to match ....what would the process be to do that? Any help is greatly appreciated
canemaxx said:
I'm glad I read this thread. I have just installed the L build and flashed the April bootloader. This took place on slot b and I want slot a to match ....what would the process be to do that? Any help is greatly appreciated
Click to expand...
Click to collapse
No need since it ia working but you get into Fastboot mode then
Fastboot set_active a
Flash L, flash April bootloadee.
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~
so I used fastboot to attempt to recover slot B on my phone (slot A is fine and boots) by dumping oos 11.2.7.7AA and manually flashing each and every partition, which goes fine except when switching over to fastbootd (via fastboot reboot fastboot) it will not flash odm, product, system_ext, or vendor, it reports that the partition cannot be found/no such file or directory. I mean I am attempting to flash those partitions so I do not understand how it cannot be found because I am flashing them. this is preventing me from restoring oos to slot B. does anyone know if I can force flash those partitions, or why fastbootd will not flash those four? I would be up and running if I could just flash those four so I can have a functional slot B.
I also tried this last night and had the same result on my slot b. I thought maybe it was because a file was consumed from my payload dump (since I had used the same files for slot a) but if you had the same issue then maybe slot b doesn't contain all partitions. Wish I knew how to check that though
shmallow said:
I also tried this last night and had the same result on my slot b. I thought maybe it was because a file was consumed from my payload dump (since I had used the same files for slot a) but if you had the same issue then maybe slot b doesn't contain all partitions. Wish I knew how to check that though
Click to expand...
Click to collapse
so you were unable to flash via fastbootd the product, system_ext, odm partitions either? interesting, but how did you get up and running then, did you fastboot flash all those files to slot A? I have been searching for a week for a solution to repair slot B, every forum, every thread, even asking in random telegram groups on how to fix this, but can't find anyone that knows what to do
If you are in twrp what does it say when you try to mount the partition? I had this issue on my old oneplus 3t, ended up having to follow a guide where I changed the filesystem of the partition to one, then back. I'm not even sure if that's possible with the current version of twrp we have.
thirtythr33 said:
so you were unable to flash via fastbootd the product, system_ext, odm partitions either? interesting, but how did you get up and running then, did you fastboot flash all those files to slot A? I have been searching for a week for a solution to repair slot B, every forum, every thread, even asking in random telegram groups on how to fix this, but can't find anyone that knows what to do
Click to expand...
Click to collapse
First I had done this procedure to slot a. Figured I probably needed to do the same to slot b so I switched to slot b through TWRP, ran the script and yup product, system, system_ext, vendor and odm failed to flash. At that point I just switched back to slot a and breathed a sigh of relief that it didn't mess with that.
Haunt3r said:
If you are in twrp what does it say when you try to mount the partition? I had this issue on my old oneplus 3t, ended up having to follow a guide where I changed the filesystem of the partition to one, then back. I'm not even sure if that's possible with the current version of twrp we have.
Click to expand...
Click to collapse
yeah I thought of that too, so before flashing oos in twrp I tried to mount odm, product, and system_ext, but none will mount and it errors out saying unable to mount partition - not found. thing is I am only using twrp to flash (or attempting to) because I get 'installation failed' in local update in system.
shmallow said:
First I had done this procedure to slot a. Figured I probably needed to do the same to slot b so I switched to slot b through TWRP, ran the script and yup product, system, system_ext, vendor and odm failed to flash. At that point I just switched back to slot a and breathed a sigh of relief that it didn't mess with that.
Click to expand...
Click to collapse
yeah those partitions flash on slot A no issue, but it is slot B that I get the error as well. I hate giving up and not fixing things, that is why I am trying so hard. I just do not understand how my phone boots fine on slot A yet I do not have those partitions
thirtythr33 said:
yeah those partitions flash on slot A no issue, but it is slot B that I get the error as well. I hate giving up and not fixing things, that is why I am trying so hard. I just do not understand how my phone boots fine on slot A yet I do not have those partitions
Click to expand...
Click to collapse
I feel you, that's why I was trying to get it back up too. At this point I think it might be a rabbit hole for me. Until someone proves to me that slot b is actually a full mirror of slot a, I'm just going to assume it's a partial mirror. As it is, as long as I can boot into the bootloader I should always be able to recover slot a. So I'll just pretend b doesn't exist XD
shmallow said:
I feel you, that's why I was trying to get it back up too. At this point I think it might be a rabbit hole for me. Until someone proves to me that slot b is actually a full mirror of slot a, I'm just going to assume it's a partial mirror. As it is, as long as I can boot into the bootloader I should always be able to recover slot a. So I'll just pretend b doesn't exist XD
Click to expand...
Click to collapse
haha yeah I'm stuck with a functioning slot A and a borked B. wait so did you update your oos via fastboot? in other words, I am on 11.2.4.4AA on slot A, I wonder if I can fastboot flash 11.2.7.7AA just like an update would
ok so you ran the fastboot script on slot A. ok well that is what I'll have to try.
thirtythr33 said:
haha yeah I'm stuck with a functioning slot A and a borked B. wait so did you update your oos via fastboot? in other words, I am on 11.2.4.4AA on slot A, I wonder if I can fastboot flash 11.2.7.7AA just like an update would
Click to expand...
Click to collapse
I was coming from LOS so I definitely wasn't on an older version of OOS. I can't quite remember if I wiped beforehand; I think I must have because I don't think it would have worked otherwise. I don't see why you wouldn't be able to flash 11.2.7.7AA on top.. but if its a functional rom it's probably safer to just run their updater instead.
shmallow said:
I was coming from LOS so I definitely wasn't on an older version of OOS. I can't quite remember if I wiped beforehand; I think I must have because I don't think it would have worked otherwise. I don't see why you wouldn't be able to flash 11.2.7.7AA on top.. but if its a functional rom it's probably safer to just run their updater instead.
Click to expand...
Click to collapse
yeah I am on stock oos 11.2.4.4AA, trying to update to 11.2.7.7AA, so even if I switch to slot B in twrp then try to flash oos it still errors out with missing those partitions, so essentially there is no way to update my oos/rom the normal way, twrp or local update, so I am stuck with fastboot flashing all the partition imgs in order to update. fml
thirtythr33 said:
yeah I am on stock oos 11.2.4.4AA, trying to update to 11.2.7.7AA, this is even if I switch to slot B in twrp then try to flash oos it still errors out with missing those partitions, so essentially there is no way to update my oos/rom the normal way, twrp or local update, so I am stuck with fastboot flashing all the partition imgs in order to update. fml
Click to expand...
Click to collapse
Good luck!! Hopefully it works out. I think the only risk is you may lose data, but just doing the same fastboot flash to slot a should work i think. I did it multiple times on a. the second time was because I was going to try a second time to flash onto slot b but forgot to change to slot b... that's when i realized i probably should stop going down that rabbit hole lol.
shmallow said:
Good luck!! Hopefully it works out. I think the only risk is you may lose data, but just doing the same fastboot flash to slot a should work i think. I did it multiple times on a. the second time was because I was going to try a second time to flash onto slot b but forgot to change to slot b... that's when i realized i probably should stop going down that rabbit hole lol.
Click to expand...
Click to collapse
yeah thanks man. the thing is I can prevent fastboot from wiping by just running the flash commands manually, and leaving out the fastboot -w command. but yeah this is a nightmare
thirtythr33 said:
yeah thanks man. the thing is I can prevent fastboot from wiping by just running the flash commands manually, and leaving out the fastboot -w command. but yeah this is a nightmare
Click to expand...
Click to collapse
If you are on oos use local update in system and do full update should fix your inactive slot. At least did for me on my 6t
toolhas4degrees said:
If you are on oos use local update in system and do full update should fix your inactive slot. At least did for me on my 6t
Click to expand...
Click to collapse
yeah man if only I could, I get installation failed in local update, which is the reason why I then tried twrp, but that gives me the partition missing errors, so essentially I cannot flash/update oos/rom
thirtythr33 said:
yeah man if only I could, I get installation failed in local update, which is the reason why I then tried twrp, but that gives me the partition missing errors, so essentially I cannot flash/update oos/rom
Click to expand...
Click to collapse
Did you try multiple times I had it fail on the first time and go through on the 2nd. If that doesn't work look to the msm tool
toolhas4degrees said:
If you are on oos use local update in system and do full update should fix your inactive slot. At least did for me on my 6t
Click to expand...
Click to collapse
this fixed my slot b issues. slot b now boots to OOS. good to know, thanks for that
toolhas4degrees said:
Did you try multiple times I had it fail on the first time and go through on the 2nd. If that doesn't work look to the msm tool
Click to expand...
Click to collapse
hm yeah I did, I attempt to local update with official full AA (11.2.7.7) and it gives me installation failed as soon as I start the process, it actually doesn't even progress at all. that is the most frustrating part (well, all of it is actually)
thing is I have been doing it this way since my 6T, and never had an issue.
thirtythr33 said:
hm yeah I did, I attempt to local update with official full AA (11.2.7.7) and it gives me installation failed as soon as I start the process, it actually doesn't even progress at all. that is the most frustrating part (well, all of it is actually)
thing is I have been doing it this way since my 6T, and never had an issue.
Click to expand...
Click to collapse
Did you try doing local update with 11.2.4.4AA? It might at least give you a solid 11.2.4.4AA b slot
shmallow said:
Did you try doing local update with 11.2.4.4AA? It might at least give you a solid 11.2.4.4AA b slot
Click to expand...
Click to collapse
yep I did, which makes me want to explode with frustration lol. both 11.2.4.4 (my current rom on slot A) and the new 11.2.7.7 will not flash in local update or twrp. so yeah fml
Hello, Sorry to bug you guys...I read multiple different fourms/how2s and I guess I'm a little mixed at what i should do. I Have the oneplus 7t (hd1505) with android 11 rooted, and after that I installed NikGapps after I had it rooted, then flashed nethunter. Was in the terminal as root, all was well..I believe It rebooted and would'nt boot to rom so i went and re'did magisk, may have used a different patched magisk? but now is stuck fastboot. Cant get it to boot.
Sorry for the maybes but I had brain surgry and my memories not the best. Everything was going fine so I didn't document things like normal. Anyways, Is there a program that helps with thiss? MSM somthing? or could anyone please point me in to a nice how2 or some quality links to assist? I really apprricate it, normally I'd just test till I get it, but I think I may be at a point where I could really mess it up.
5k1tz0 said:
Hello, Sorry to bug you guys...I read multiple different fourms/how2s and I guess I'm a little mixed at what i should do. I Have the oneplus 7t (hd1505) with android 11 rooted, and after that I installed NikGapps after I had it rooted, then flashed nethunter. Was in the terminal as root, all was well..I believe It rebooted and would'nt boot to rom so i went and re'did magisk, may have used a different patched magisk? but now is stuck fastboot. Cant get it to boot.
Sorry for the maybes but I had brain surgry and my memories not the best. Everything was going fine so I didn't document things like normal. Anyways, Is there a program that helps with thiss? MSM somthing? or could anyone please point me in to a nice how2 or some quality links to assist? I really apprricate it, normally I'd just test till I get it, but I think I may be at a point where I could really mess it up.
Click to expand...
Click to collapse
If you don't care about data then use msm tools to factory restore. Or you can flash boot image of the rom you were using (unpatched) in fastboot mode itself.
No need to keep data, I'd prefer to wipe device and start fresh instead of getting stuck on the concept of A/B partitions. I get the CMD getvar, but I'm not sure if i flashed the lineage OS to one or both...at 1 point i think i was booted in A, now its saying B. I got overeager and downloaded multiple ROMs and not sure which one worked. In the past I usually downloaded a few and the first one to work I used. Not smart...I know. If I wanted to wipe all and start fresh with gaspps and root, where/how should I do that? I can't just fasatboot oem unlock , could I? Would you recommend stock OS? Lineage? Thanks for your help BTW.
5k1tz0 said:
No need to keep data, I'd prefer to wipe device and start fresh instead of getting stuck on the concept of A/B partitions. I get the CMD getvar, but I'm not sure if i flashed the lineage OS to one or both...at 1 point i think i was booted in A, now its saying B. I got overeager and downloaded multiple ROMs and not sure which one worked. In the past I usually downloaded a few and the first one to work I used. Not smart...I know. If I wanted to wipe all and start fresh with gaspps and root, where/how should I do that? I can't just fasatboot oem unlock , could I? Would you recommend stock OS? Lineage? Thanks for your help BTW.
Click to expand...
Click to collapse
Go to this thread for MSM Tool download and instructions: Unbrick tool to restore your device to OxygenOS