Install Using Lineage Recovery
Flash Stock A71n
Reboot system
https://mega.nz/file/9thDzZTK#W2Hgfam6otB9XdR_sfXxdt3MR--RCc9FedECPT3BJXM
Read this
Search Stock A71n In Lineage os thread
You Should On OneUI 2.0 not OneUI 2.1 if from oneUI 2.1 u should downgrade to 2.0
There is no way to find a UI2.0 Version.
If i installed it on UI2.1 the installation will be successful but after reboot the phone goes into Download Mode and there is written "...vbmeta.img verification failed..."
And the file "stock-a71n.zip" doesn´t install with the message "wrong footer"
The rom works. But charging doesn't not. How do i fix it?
Is this still working well? Did charging ever get fixed?
Related
So I have TWRP installed on my phone and am running the CM 13 custom rom. When I boot into TWRP and then hit reboot system, it gives me the warning "No OS installed! Are you sure you wish to reboot?" It gives me this error every time, even though I DO have an OS installed. The reason that this is a problem is that I need to flash a Gapps zip onto my phone, but whenever I try to, it says that I have no rom installed, and that I need to flash a rom before gapps. This is very annoying, because I DO have a rom installed, but yet these errors keep showing up. To find the guide I followed, type (I'm unable to post links yet) "How to Install CM 13 On T-Mobile Galaxy S2 Android Marshmallow 6.0" into google. It will be the first link. I followed those steps exactly, so I don't know why this is happening. Any possible fixes would be appreciated!
AndroidAllTheWay358 said:
So I have TWRP installed on my phone and am running the CM 13 custom rom. When I boot into TWRP and then hit reboot system, it gives me the warning "No OS installed! Are you sure you wish to reboot?" It gives me this error every time, even though I DO have an OS installed. The reason that this is a problem is that I need to flash a Gapps zip onto my phone, but whenever I try to, it says that I have no rom installed, and that I need to flash a rom before gapps. This is very annoying, because I DO have a rom installed, but yet these errors keep showing up. To find the guide I followed, type (I'm unable to post links yet) "How to Install CM 13 On T-Mobile Galaxy S2 Android Marshmallow 6.0" into google. It will be the first link. I followed those steps exactly, so I don't know why this is happening. Any possible fixes would be appreciated!
Click to expand...
Click to collapse
I would try to flash another version of TWRP. Sometimes, the latest TWRP is not the most compatible with all the ROMs out there.
As the title says I am unable to boot after flashing Magisk (tried v16 and v15.3). It boots fine without magisk but of course no root and no custom recovery. Any help would be appreciated. Didn't have any problems on the previous stable build.
You need to first flash OOS 5.1 let it boot, then go to fastboot and flash twrp then go to twrp and flash magisk, only way to get root
hello, that's what I did and it worked well
this has happened here since 5.0.4
Try to use lastest blu-spark's TWRP, then flash 5.1 & Magisk without extra boot in the middle.
Things I noticed when upgrading:
A) The latest TWRP for dumpling appears to be broken. I get an error mounting /vendor when I use it. I switched to the previous version (20180309) and the error went away and everything seems to work.
B) You may very well have Xposed installed. If you do, there is an SDK bump between OOS 5.0.x and 5.1.x (26 -> 27). You'll need to disable this module either before you install the update (or assuming you already have) remove the module using something like Magisk Manager for Recovery to remove it (reboot to recovery, install module, run mm from terminal, follow prompts).
-Toucan
ToucanSam said:
Things I noticed when upgrading:
A) The latest TWRP for dumpling appears to be broken. I get an error mounting /vendor when I use it. I switched to the previous version (20180309) and the error went away and everything seems to work.
B) You may very well have Xposed installed. If you do, there is an SDK bump between OOS 5.0.x and 5.1.x (26 -> 27). You'll need to disable this module either before you install the update (or assuming you already have) remove the module using something like Magisk Manager for Recovery to remove it (reboot to recovery, install module, run mm from terminal, follow prompts).
-Toucan
Click to expand...
Click to collapse
It's not broken. The vendor error message is because it was recently updated to work better with Project treble, which uses a hidden partition for the vendor. You can simply ignore the error and it will work fine. Or if you flash a treble ROM, the error will then go away.
I just got the phone. Format it in recovery.
Flash latest blu spark twrp (v.8.73).
Flash the Oos ob06.
Reboot to system. Set the phone, instal apps from Play.
Reboot to Fastboot.
Reflash recovery.
Reboot to recovery.
Flash Magisk 15.3. Reboot to system. OK.
Updated Magisk with Magisk.
Hi, Can anyone help me. in my oneplus 5T after installing new rom it is working smooth but i can't upgrade to new updates. in recovery mode the files seems to be decrypted and cant find any folders where i copied the updation . instead new files are found and can't access and find any of the folders of my own. this happened after i input the security lock. i wiped the entire data and installed new roms still it seems so. somebody please help me to find a solution for this
It seems like every time I use twrp, I get an error if "zip verification failed" or "error 7". How can I fix this?
https://imgur.com/a/btliPCR
https://imgur.com/a/L6iGzzO
You are trying wrong twrp, use the pie twrp for pie firmware and Oreo for oreo firmware.
Use latest pitchblack recovery for whyred. Its working perfect.
Official TWRP is not compatible with Pie Firmware. Try my recovery - working on both firmwares well.
For some reason, I managed to get Pie (One UI 1.0) working on my G960F yesterday (with root) and it worked fine until it randomly started boot looping, so I flashed it back to stock Pie and updated to Q. But now, I can't downgrade back to Pie because I get an error in download mode saying "SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 8, BINARY 7". It usually appears after it says RECOVERY in Odin. Luckily I can get the device to boot back to Q, but I really wanna Root it or install a Custom ROM, because I hate One UI, so is there any way to install TWRP on Q yet?
Yes, install twrp through odin, make sure you boot straight into twrp from download mode. Then wipe date and reboot recovery not the system. Then flash the multi disable zip from the download link. Then flash magisk and reboot. All done
https://drive.google.com/file/d/1TBp5hIrzIljYvOquI1H9L78YFtskxMDn/view?usp=drivesdk
my a2 lite got the awful 10.0 update, and I tried to install a custom rom.
the only one that worked was the Avenger MIUI rom.
I'm using dees-troy's twrp 3.3.1
tried to reflash the stock img, it got me into booting only to fastboot mode.
I'm tired of the MIUI, can anyone explain to me step-by-step how to install any aosp-like rom?
back then, I had error number 7, and on my last try, after trying to flash back and such, it couldn't mount the storage correctly.
right now I have an error:
E:recv error on uevent
UduBobo said:
my a2 lite got the awful 10.0 update, and I tried to install a custom rom.
the only one that worked was the Avenger MIUI rom.
I'm using dees-troy's twrp 3.3.1
tried to reflash the stock img, it got me into booting only to fastboot mode.
I'm tired of the MIUI, can anyone explain to me step-by-step how to install any aosp-like rom?
back then, I had error number 7, and on my last try, after trying to flash back and such, it couldn't mount the storage correctly.
right now I have an error:
E:recv error on uevent
Click to expand...
Click to collapse
You need:
twrp-installer-daisy-3.2.3-0-offain (or higher)
Also when you install AOSP based rom you'll have to change A/B slots before rebooting. Most of the roms have step by step guide on the first page / post.