I have recently noticed the potential of the A/B partition system in Mi A1. Is it possible to flash the rom only on one partition? Is the rom flashed onto both the partitions(via TWRP)?
I've installed two systems long time ago, LAOS 14.1 and Stock December Oreo, i can see both bootanimations (with a Slot change from TWRP), LAOS can boot normally, Android One can boot BUT you can only see a black screen with a lot of errors (like, Android System Stopped etc.), So at least you can use just one System, maybe there's a workaround, i don't know.
Sent from my Mi A1 using XDA Labs
Related
Hey guys,
I have a little problem with my new OP2.
I unlocked the bootloader and rooted etc.
I installed Paranoid Android and I wanst sure which kernel works on it.
So I tried flashing one for CM13 and one for OOS3, but both of them wouldnt work.
Now Im trying to get back to stock or atleast flash the boot.img from the Paranoid ROM.
I can boot, access the recovery and bootloader. I flashed different boot.imgs (Stock and Paranoid) and recoverys. But none of them helped.
The touchscreen wont react at all. If I boot, if I am in the recovery. It just wont work. Hardware button seems to be fine though.
Any ideas how to fix that?
Try wiping system partition and flash the PA ROM again (and Gapps of course) and it will restore system and kernel back to PA default.
If touch still doesn't work, then you'll probably have to wipe userdata partition as something you installed with the kernels not supporting other than official latest CM13 sources is messing with your system.
You need to flash full stock using fastboot from unbrick guide.
Sent from my ONE A2005 using Tapatalk
google megaunbrick guide oneplus2 and follow that!
didn't got your logic behind flashing custom kernel that too on paranoid android, I can understand that for cm13 as the battery life sucks there but pa easily gives 6+ hrs of sot which any other rom or even a custom kernel can't even come closer to it in my personal experience.
meaning you can try to flash the whole rom through fast boot or use unbrick guide to go full stock.
Hi, I tried to encrypt my Mi A1 with Android’s full-disk encryption. Unfortunately something went wrong, so I tried to flash a Rom. First I tried a dirty flash with the official LOS 15.1 (20190224). But the Display went crazy. So I head to flash the stock Rom through fastboot. After this my Mi A1 worked. Next I tried a clean flash with the same LOS-Rom, but I get the same result. I also tried some other versions of LOS, but I get also the same result. I also tried to flash LOS 16.0 (20190301) and also AospExtended v6.3(20190213). The result after flashing those Custom Roms is that the Display stays black, but not like the phone is off. It looks like the display is active but black. I had also tried LOS for microg 15.1(20190310) but the result was the same as flashing LOS 15.1
When I flash LOS 15.1 or the other Roms with the same result and I boot in TWRP the Display there also went crazy.
Sometime when I format or flash something with TWRP I get the message ,,Failed to mount ‘/system’ (Permission denied). But I always get the same result after flashing.
I hope someone could help me.
same to me
just recovey my phone with mi flash y culdnt get a costom rom again
You need to correct youe version of TWRP recovery
Infact, you need to try different versions to see which one works for uh...
Try booting into recovery IMG from Fast boot again and again if uh are really troubled by a permanent recovery.
I attempted to install Lineage OS on my Pixel C. When I attempt to sideload Lineage OS, I get an error that says "Updater process ended with signal: 7" and it acts like I have no system image installed and just keeps boot-looping. I tried to flash back to stock, but I keep getting an error that says "error: Cannot generate image for userdata". I have re-downloaded all of the images, and retried over and over again, to no avail. Any advice is appreciated!
Well, I finally got my tablet to boot again. I extracted the factory image and individually flashed each component (boot, cache, recovery, vendor, system - in that order) and I'm back to a clean install of the stock android. I went back and flashed twrp (successfully), and tried to sideload Lineage again per the instructions on their website, and got the same result. If I can't figure this out, I may be going back to just stock android.
Is it your first attempt at a custom rom?
Have you flashed a recent kernel, bootloader is unlocked etc?
edit: lol, last reply was from May..
Hey, I guess I haven't been on here in a while, and never saw your reply to this. It is not my first attempt at a custom rom. Bootloader is unlocked, and kernel is up to date (or was in May). I ended up staying on stock android since I had no trouble getting it to work. Best I can recall, I think I read that there was a conflict between TWRP and the kernel version I was on. Around the same time, I tried to flash LineageOS to my Essential PH-1, and had similar issues, and ended up just staying with stock android. I've been flashing custom roms since cyanogenmod was available on my Nexus One (I think that was on cupcake), and while I'm not an expert, I'm pretty comfortable with the process, so I went back to my Moto N6, and was able to flash LineageOS to that without a problem. I know that the Pixel C and PH-1 both have the whole A/B slot architecture, and I wonder if I wasn't managing that correctly, but I've gone through a couple of custom roms on my Pixel C over the years without having that problem, so I just don't know. Right now I'm fine with stock (rooted) Android, but the bug is sure to bite me again soon, so we'll see what happens then.
I recently downgraded to Lineage 15.1 (official) from 16 and had some issues.
Short story to make it work was; installed the April version of the official factory/ota image like you did to overcome version conflicts.
(booting to TWRP.img after getting to the correct recovery menu by pressing power+volume up).
In TWRP; As the \data folder was encrypted I had to format that first (advanced wipe) and used adb to push files to \sdcard.
I flashed the Lineage 15.1 zip, gapps and Magisks before rebooting.
As that build enforces encryption of \data at first boot you may need to use "default_password" to load TWRP with access to \data in the future.
Hope this helps
Hi all,
Since a couple of days I was able to unlock the bootloader on my Mi 9T Pro device. I managed to install TWRP recovery via fastboot and then the vendor, Lineage, other kernel, Magisk as zip via TWRP recovery.
It worked fine, until at one moment I rebooted and suddenly it started only the fastboot. No OS anymore, but also no recovery. Flashing TWRP again via fastboot worked, but recovery was not loading and it kept booting into fastmode.
I repaired it via the Xiaomi Flashtool, by flashing the Global rom again. System flashed, MIUI booted. After I could unlock bootloader again, flash recovery, and TWRP was also loading again.
Suddenly, I still don't know exactly why, it again started booting only to fastboot. Flashing the official ROM via the Xiaomi tool repaired the device again. Then I continued again with TWRP + vendor/LineageOS/Magisk/kernel. Works!
Now my device runs LineageOS 17.1, still has TWRP working, is rooted, has updated kernel and all seems fine. However I am scared that this strange "only booting to fastboot and needs complete wipe/reinstall by installing official Rom via Xiaomi tool" again. (It means, at any moment you will lose your whole device, setup, configuration, applications and data...)
Now I was wondering: can anyone explain me what is the rootcause for this "only booting to fastboot" bug?
Am I doing something wrong?
Is it perhaps caused by a kernel or magisk bug in the version I use?
Did I flash the wrong TWRP? (I tried official and some version for Mi 9T Pro found in this forums).
I don't see it yet, I hope someone knows what causes this issue. Then I know what to be careful for.
What causes this bug?
Thanks in advance!
***EDIT: Oops! I accidentally posted this in the Mi 9T forum instead of the Mi 9T Pro. Perhaps the issue and answer is the same, however perhaps a mod can move this to the Q&A subforum of the Mi 9T Pro? Sorry***
This usually happens if you wipe system and/or vendor partitions and then reboot (at least that's how I got this issue). For some reason if those are empty or invalid, the device gets stuck to fastboot and can't even boot to TWRP (neither directly or using fastboot boot).
To avoid that just never reboot (even reboot to recovery) right after wiping system/vendor, always make sure a ROM is installed first (or just don't wipe them since usually the ROMs take care of it before the install anyways).
Thank you!
Indeed, even TWRP did not load, exactly as you describe.
So that means for some reason the system or vendor partition got wiped or corrupted. Thanks, I will think why that might happened and where to be extra careful for.
Hey all,
Are Oneplus 6T T-Mobile users able to flash custom roms?
A few months ago I tried everything to flash Xtended or Lineage, but I was getting the bootloop/reboots. I tried converting to international, among other things, but nothing worked, and if it did, it was very buggy (managed to flash MIUI, but couldn't use it as a daily driver. Updated to Android 10 after International, but a lot of weird bugs like missing emojis, etc.)
I haven't seen anyone mention or talk about it, but if you have a T-Mobile OP6T, can you still flash a custom rom?
From what I've read and I've read just about everything there is for this device as long as you covert to international and move to 10.3.4 firmware then custom roms should work at this time.
Sent from my ONEPLUS A6013 using XDA Labs
I've flashed just about everything onto mine with no issues.. Ended up going back to oos 10 just because of certain features I couldn't live without though, however i ditched the t-mobile version for the international and modified a few things with magisk and twrp. The only time I have been caught in a bootloop is when I didn't want to wipe the data partition and something didn't play nice. Or going from andriod 9 to a 10 rom or 10 back to 9 without completely wiping everything and starting with the stock 9 or 10 before flashing. Was kind of weird and this is just how i got it to work for me, after lots of retrys
cwtechshiz said:
I've flashed just about everything onto mine with no issues.. Ended up going back to oos 10 just because of certain features I couldn't live without though, however i ditched the t-mobile version for the international and modified a few things with magisk and twrp. The only time I have been caught in a bootloop is when I didn't want to wipe the data partition and something didn't play nice. Or going from andriod 9 to a 10 rom or 10 back to 9 without completely wiping everything and starting with the stock 9 or 10 before flashing. Was kind of weird and this is just how i got it to work for me, after lots of retrys
Click to expand...
Click to collapse
ya flash international then upgrade to 10 unlock bootloader
im on tmobel flash to international and now running linage works great
@oooscasianooo No issues on my end. I converted my tmo 6t to international then upgraded to 10.3.4 then flashed RR rom first attempt all booted no issues on 10.3.4 or RR at all.
How I installed rom:
boot twrp (by mauronofrio) , flash oos 10.3.4,, flash twrp installer zip, reboot recovery, flash oos 10.3.4, flash twrp installer zip, reboot recovery, flash rom, (if rom has gapps included) format data, wipe data & cache,flash twrp installer zip, reboot system.
Or with finalize zip that copies firmware to other slot for you...
Boot twrp, flash OOS 10.3.4, flash rom w/gapps included, flash twrp installer zip, flash finalize zip, format data, wipe data & cache, reboot system.
If rom does not have included gapps you just have to reboot recovery before you flash your gapps package then reboot system afterwards.. Evo X has twrp and gapps so it's even a shorter time frame for installation.. just boot twrp, flash OOS 10.3.4, flash Evo X rom, flash finalize zip, format data, wipe data & cache , reboot system.
(Edited)
hi
Does Dual Sim with the Tmo OP6T after swapping out the simtray to a dual one ?
I plan to use Lineage 17.1 with dual-sim's on a used tmo-op6t
G
ghatothkach said:
hi
Does Dual Sim with the Tmo OP6T after swapping out the simtray to a dual one ?
I plan to use Lineage 17.1 with dual-sim's on a used tmo-op6t
G
Click to expand...
Click to collapse
I was going to ask the same question, as I am also planning to install Lineage on my Tmo 6T. Did you ever find the answer?