Hallo i need help on my One+3T is Official Lineage OS installed and latest TWRP when i will Update now Lineage OS in twrp, twrp say internal Storage 0mb my question is now why?
AndroideChris said:
Hallo i need help on my One+3T is Official Lineage OS installed and latest TWRP when i will Update now Lineage OS in twrp, twrp say internal Storage 0mb my question is now why?
Click to expand...
Click to collapse
Now my question is why you posted this on wrong forums?
Sorry ist anywhere a twrp Forum here?
This is oneplus one section...
Related
Hi all, i have a problem whan i install lineage os, i don't have any system on my oneplus one and i want install lineage but when the installation has finished, my phone restart and freeze on logo one plus one android powered.
if you have a solution ;D
good night
LucasJahier said:
Hi all, i have a problem whan i install lineage os, i don't have any system on my oneplus one and i want install lineage but when the installation has finished, my phone restart and freeze on logo one plus one android powered.
if you have a solution ;D
good night
Click to expand...
Click to collapse
Which firmware were you on? Which recovery you used?
Did you tried previous lineage os nightly's?
I don't know what firmware i m and i have try with the latest nighly release. And i use the latest version of twrp
LucasJahier said:
I don't know what firmware i m and i have try with the latest nighly release. And i use the latest version of twrp
Click to expand...
Click to collapse
Go to setting > about phone and see Baseband version.
If you're coming from CM13.1 make sure to wipe everything except internal storage.
Download the ROM again if possible (the version you have downloaded may be corrupted) from the Lineage os official site and gapps(micro or pico).
Flash the ROM first and then gapps.
Reboot your device.
If you want the Root access download the Su add-on from the Lineage website also.
Hope it will work.
Let us know.
Thanks.
Re
Re,
Sorry... but i don't have any os in my oneplus one... he is empty exept zip the lastest version of official website and zip of gapps.
Thank you
Hello,
today I got the official Android Q Update for my Oneplus 7 Pro.
Since my phone was rooted, I downloaded the whole update, let it install and didn't reboot.
Then I installed Magisk over the Magisk app to the other partition.
After that I flashed TWRP as module via Magisk and flashed Magisk.zip again via Magisk.
Then I rebooted my phone and it was rooted as expected. The problem is, my TWRP has no access to my sdcard.
A week ago I installed already the OxygenOS 10.0.0 for testing purposes and had the same problem. I didn't focused on the TWRP problem because I went back the same day to OxygenOS 9. Since I have now the official OxygenOS 10 I would prefer a working TWRP.
Any possibilities to get TWRP working or do we have to wait until TWRP rolls out an update?
I read severel posts of people who got TWRP running but these are from the Beta and I am not shure if running only means that TWRP is on the phone even if it can't acces the sdcard.
Thank you very much.
The unofficial twrp 70 works well for me. Just search in the forum.
shan_pei said:
The unofficial twrp 70 works well for me. Just search in the forum.
Click to expand...
Click to collapse
Thank you for your reply. I tried the TWRP 70 but I still can't mount the storage...
Delete as I'm idiot twrp not available for android 10
funkyirishman said:
Delete as I'm idiot twrp not available for android 10
Click to expand...
Click to collapse
It's been available since maybe a week after Android 10 came out (fixed the problem with fastboot boot). But you may be looking at the "official" TWRP website. You need to use an "unofficial" version TWRP (current version is -76) from the dev's thread here:
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Recently I decided to play around with my retired xiaomi 4c which I bought in 2016/2017.
Firstly, I unlocked my phone and installed TWRP recovery. (the version I installed is twrp-3.1.1-0-libra), the link I used is here: https://dl.twrp.me/libra, the reason why I did not install version 3.1.1-1 is that It won't load in recovery mode.
Secondly, I tried to install lineage 14.1, 15.1,16.1, 17.1 (none of them worked), It gave me this error
E3004 the packge is for device 4c,libra, this device is .
After searching on google, I deleted the first line (the assert statement) in META-INF\com\google\android\updater-script.
I guess it managed to be installed (no error pop out).
the log displayed while it is installing:
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
packing system image unconditionally
However, when I click boot to system, it stuck on the mi logo.
I need some suggestions on how to make this work.
Thanks in advance!
Flash the latest available official miui (currently V10.1.1.0), via mi flash tools
Flash twrp or orangefox, via ADB. twrp official site has an old version, androidfilehost has a newer version TWRP-20190528-3.3.1.0-libra. orangefox official site has taken down libra files but sourceforge has OrangeFox -R10.0-1-Stable-libra.
Then try again
I experienced "this device is ." problem before.
From I read somewhere in XDA, sometimes a ROM may require certain recovery images to flash. So if the image is published with some recovery, you may want to try them together.
The last time I flashed my mi4c successfully, the LineageOS build and TWRP are both from this post: https://forum.xda-developers.com/t/rom-android-8-9-10-unofficial-lineageos-for-mi-4c-mi-4s.4008625/ .
Good luck
Gourcuff14 said:
Flash the latest available official miui (currently V10.1.1.0), via mi flash tools
Flash twrp or orangefox, via ADB. twrp official site has an old version, androidfilehost has a newer version TWRP-20190528-3.3.1.0-libra. orangefox official site has taken down libra files but sourceforge has OrangeFox -R10.0-1-Stable-libra.
Then try again
Click to expand...
Click to collapse
Thank you! I finally managed to install lineage 14.1, but not 15.1, 16.1 or 17.1, weird
momocraft said:
I experienced "this device is ." problem before.
From I read somewhere in XDA, sometimes a ROM may require certain recovery images to flash. So if the image is published with some recovery, you may want to try them together.
The last time I flashed my mi4c successfully, the LineageOS build and TWRP are both from this post: https://forum.xda-developers.com/t/rom-android-8-9-10-unofficial-lineageos-for-mi-4c-mi-4s.4008625/ .
Good luck
Click to expand...
Click to collapse
Thank you, I finally managed to install lineage 14.1, but not 15.1, 16.1 or 17.1, weird.
Haha but now I failed to bypass the ssl pinning through sslunpinning and frida ><, frida says Bad access due to invalid address
Any idea how to fix this?
Try the boot image included in this build package and post your findings in that thread for assistance.
[ROM][8.1/9/10/11][Unofficial][EOL] LineageOS for Mi-4c/Mi-4s
DESCRIPTION Unofficial LineageOS ROMs for Mi-4c (libra) and Mi-4s (aqua), with base-layer enhancements and performance optimizations. Version 15.1/16.0/17.1/18.1 are available for download. FEATURE The following items may not be available for...
forum.xda-developers.com
you need orangefox for mi4c
yanzifan021 said:
Thank you! I finally managed to install lineage 14.1, but not 15.1, 16.1 or 17.1, weird
Click to expand...
Click to collapse
Hi friend, could you share the download link 14.1, thanks
timsg said:
Hi friend, could you share the download link 14.1, thanks
Click to expand...
Click to collapse
Here there are some builds https://androidfilehost.com/?w=search&s=libra&type=files&page=19
I am using my poco x3 pro with mi eu as my daily driver; however, duplicate apps still reign supreme and the default mi music app doesn't get recognized in Android Auto.
I have dabbled in custom roms before, a couple times but most of them have stopped me from completely using the phone normally, namely broken camera support with drive doesn't recognizing the camera (even with gcam, don't @ me), slow document viewer and so on. As such, I generally refrained from using them, until I saw Crdroid 8 with MIUI cam, which seems like the best of both world for me.
The guides on the thread are too vague? And Im not sure about updating (the rom required a custom recovery image, however, my recovery is too old and i don't want to risk my phone getting bricked)
Can someone help? Thanks a lot!
bump
Boot to twrp
Format data
Wipe data, dalvik, cache
Install latest firmware - https://xiaomifirmwareupdater.com/firmware/vayu/
Install ROM
Flash Gapps
Format data
AmmarHaseeb said:
Boot to twrp
Format data
Wipe data, dalvik, cache
Install latest firmware - https://xiaomifirmwareupdater.com/firmware/vayu/
Install ROM
Flash Gapps
Format data
Click to expand...
Click to collapse
Does this erase the internal storage? I don't have an SD card and a usb otg
BreadGyarados said:
Does this erase the internal storage? I don't have an SD card and a usb otg
Click to expand...
Click to collapse
I already got that figured out
BreadGyarados said:
I already got that fig
Click to expand...
Click to collapse
BreadGyarados said:
I already got that figured out
Click to expand...
Click to collapse
Flash latest twrp, or orangefox recovery. On A11 android you can put rom zip to internal storage and flash from there, on a12 you need sideload rom, because recovery still not support encrypting storage.
irmas5 said:
Flash latest twrp, or orangefox recovery. On A11 android you can put rom zip to internal storage and flash from there, on a12 you need sideload rom, because recovery still not support encrypting storage.
Click to expand...
Click to collapse
I see!
does twrp support cross android versions? Like can I dirty flash one of the update (a12)? The crdroid og thread mentioned sth about a12 custom recovery
BreadGyarados said:
does twrp support cross android versions? Like can I dirty flash one of the update (a12)? The crdroid og thread mentioned sth about a12 custom recovery
Click to expand...
Click to collapse
All custom recoveries cannot decrypt Android 12 yet.
So you cannot see internal storage in any Android 12 ROM if your phone is encrypted. This will cause difficulties in dirty flash Android 12 systems.
What do you mean cross Android versions? MIUI to CrDroid 12 ? CrDroid 11 to CrDroid 12? CrDroid 12 to CrDroid 12?
It is better to do clean flash than to only dirty flash when you are crossing different OS and different Android version to prevent bugs.
pl1992aw said:
All custom recoveries cannot decrypt Android 12 yet.
So you cannot see internal storage in any Android 12 ROM if your phone is encrypted. This will cause difficulties in dirty flash Android 12 systems.
What do you mean cross Android versions? MIUI to CrDroid 12 ? CrDroid 11 to CrDroid 12? CrDroid 12 to CrDroid 12?
It is better to do clean flash than to only dirty flash when you are crossing different OS and different Android version to prevent bugs.
Click to expand...
Click to collapse
What I meant cross android versions is that miui eu running android 11 to crdroid running android 12, as the device has no official android 12 support.
I know that I need to clean flash the roms as a first time installation, but current twrp supports android 11 (check it on mifirm).
BreadGyarados said:
What I meant cross android versions is that miui eu running android 11 to crdroid running android 12, as the device has no official android 12 support.
I know that I need to clean flash the roms as a first time installation, but current twrp supports android 11 (check it on mifirm).
Click to expand...
Click to collapse
The deciding matter is the Android system currently installed in the phone.
Your example is MIUI.eu with Android 11, in custom recoveries should be able to see internal storage.
[Phone is now Android 11]
After you install CrDroid Android 12 and boot, then custom recoveries cannot see internal storage if it's encrypted.
[Phone is now Android 12]
If you revert from CrDroid Android 12 to MIUI.eu Android 11 and boot, then custom recoveries should be able to see internal storage again.
[Phone is now Android 11]
If your phone is now Android 12, when you want to install something or flash/update a ROM in custom recoveries, it will be a bit complicated as mentioned earlier. You have to sideload with commands.
If you have microSD cards in the phone or USB OTG, then custom recoveries should be able to read them even under when phone is Android 12.
Whether ROMs can dirty flash or not, you have to read the ROM thread and replies (or Telegram if there is no XDA thread), especially replies by the developer.
Some version cannot be dirty flashed, even if it's by the same developer.