Related
hi,
my oneplus 3 has been rote since i got it (i bought it on launch day) but since i updated it to the beta 19, my phone is no longer rooted : when i put the phone in fastboot it says that my bootloader it unlocked but all the apps who requier root are saying that the phne is not rooted and i cant get twrp to work. i tryied with the official app on my phone and with a program called "tool all in one" (https://forum.xda-developers.com/on...ol-tool-one-driversunlocktwrpfactory-t3398993) and when i flash twrp from the program, i can boot into twrp but then i can't access my files and after i boot the phone, i can no longer boot to twrp
does anyone have a solution that doesn't involve me wiping the phone?
You loose root after updating. Try installing twrp again and then rooting it. Use the toolkit for oneplus 3. Simplifies the process
what do you mean by "then rooting it" ?
the program i use does the same thing as the toolkit and when i install twrp, as i said, it can boot on twrp one time and in twrp i can't access my files and after i boot the phone i can't get back to twrp ,i get the stock recovery
Unless your ROM has built-in root, after flashing TWRP, you have to flash SuperSU or Magisk to obtain root. Mere flashing of TWRP will not give you root.
I know but i can't get to the folder when the magisk file is : when in boot into twrp i cant see my files
Few details... it's quite difficult to help you.
What's the root method? Magisk, SuperSU or Kingroot? Which version?
Ps TWRP recovery is not depending by root, you just need to unlock bootloader (surely it's already unlocked) and flash the same recovery, from PC, via the command "fastboot flash recovery filename.img".
Now enter in TWRP:
1) Wipe /system and /cache;
2) Flash another time Open Beta 19;
3) Flash Magisk or SuperSU (be sure to have latest release);
4) Move TWRP img file from computer to device, then flash it another time (because firmware provides the OOS stock recovery);
5) Reboot and wait 5-10 minutes, because of cache rebuilding.
Tell me if you solve
I am using magisk
Yes my bootloader is unlocked
My problem is that when i flash twrp i cant access my files so i don't want to wipe system if i cant reflash something after
I think that I'll wait for the next update, maybe then it will work
But thank you for your help
Which version of TWRP do you have? Try eng.stk's latest version.
I tryied 3.1.1-2
The eng.stk is not available anymore
Your phone is encrypted, so you have to format data ( but your internal storage wiped by formating data, so back it up ,then only twrp read files in your storage)and flash custom kernel then boot restore backup .
how do you know that my phone is encrypted? i never encrypted it
i use titanium backup so i can't back my phone up until i get rot back
Whenever you flash stock ROM it encrypt if you boot into system directly . So twrp could not read internal storage. Whenever you flash stock ROM you must flash custom kernel or any other method to avoid encryption. This is happened to me and what I'd done is flash custom kernel before boot into rom
To save your data try this
https://forum.xda-developers.com/oneplus-3/how-to/unencrypt-oxygenos-loosing-data-t3412228
Who said that? Check this: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Edit: If you want to save items in internal storage, you can use ADB commands instead of TWRP. You can also simply copy and paste if your PC recognises the internal storage of your phone.
I succeeded but i had to clean everything and use the last backup i made a week ago
Thank you all for your help
dear all, after flashing Xiaomi.eu 20.3.19 update I am stuck in a bootloop to the recovey or to the boot loader.
after the second attempt to flash the zip file I was not able to enter my my so the interal sd card is vlocked.
I have access to the otg drive but.
I tried additional the following:
Format data, caches and system
Install 20.3.19 via OTG
install 20.3-12 via otg
install fresh magisk 20.3 via TWRP
updarde to the newest TWRP
downgrade to an older TWRP
all without success
Does anybody have an idea to solve this issue?
Thanks in advance
If you want to flash xiaomi.eu you shouldn't wipe system when flashing from miui. It won't boot if you wipe system. So now you must flash miui with miflash. Then twrp and xiaomi.eu (wipe cache, dalvick)
Thanks alot for the swift reply.
This is the first time that I had this issue and now I am totally stuck, is there no other way than mi flash?
If I well remember flashing the factor< image will erase everything?
I made a backup but due to the locked internal sd card I have not access on this data.
Thanks for the support
Now I have another problem,
As soon as I start the Mi flash tool or the Mi unlock tool the device shuts down from bootloader mode.
I´m Stuck
Thanks for support
Maybe you have some driver problems?
@baltes: ...or try another cable or another USB-port
Thank a lot,
Ich changed the cable and the USB port as well. No change
I downloaded the standard ADB and Fastboot drivers ver 1.4.3.
I don´t hope the the devise is not toally bricked
@baltes: uninstall ADB/fastboot, Mi tools and Mi drivers. Reboot, install MiFlash again and let it install the needed drivers.
rp158 said:
@baltes: uninstall ADB/fastboot, Mi tools and Mi drivers. Reboot, install MiFlash again and let it install the needed drivers.
Click to expand...
Click to collapse
Thanks,
I uninstalled everything, and reinstalled miflashtool, no change as soon as I select refresh the 9SE shuts down (from bootloader)
I managed to erase the internal storage in TWRP, Im able now toto copy MIUI zip on the interal storage and install it successfully. but reboot is then still again innTWRP
So flash some aosp based Rom. Wipe cache, dalvick, data and system before. Do not flash magisk or other mods. Just Rom and gapps. That kind of Rom should boot. Then you can try flash latest global miui Android 10 with miflash and start over to xiaomi.eu.
@baltes: I wouldn't use AOSP to get MiUI runnable. If you do so,
* format data
* reboot to recovery
* wipe system, vendor, data, both caches
* flash ROM, no GApps
Better make a clean base by MiFlash: now you first say, that Fastboot only aborts when clicking Refresh. I don't remember this tool, but are there other options besides Refresh?
coolek33 said:
So flash some aosp based Rom. Wipe cache, dalvick, data and system before. Do not flash magisk or other mods. Just Rom and gapps. That kind of Rom should boot. Then you can try flash latest global miui Android 10 with miflash and start over to xiaomi.eu.
Click to expand...
Click to collapse
Hello, i don´t know wy but after several formats and installations it worked and I´m running now on 20-3-19
Thanks all
So here's what I did to cause my phone to get stuck on the logo screen:
1. Unlocked my phone using the Mi Unlock
2. Used ADB to install twrp-3.3.1-0-nitrogen
3. I couldn't mount my Data or SD Card folders due to encryption, so someone told me to use TWRP to format data, which I did. It didn't boot up after that.
I've tried the following fixes:
1. TWRP > Advanced Wipe > Cache / Data / Internal Storage / System
2. TWRP > Install > MIUI 11 V11.0.2.0.PEDCNXM
3. TWRP > Install > MIUI 11 V11.0.3.0.PEDCNXM
4. TWRP > Install > Magisk-v20.4
No luck, still stuck on boot. Anyone kind enough to please help?
I had the same problem when I backed up the global rom with OrangeFox and restarted the system without installing anything.
The following procedure worked for me.
User the latest version of TWRP 3.3.1 do not use OrangeFox
1. First you must remove the encryption, Wipe> Format Data, confirm by typing "yes"
2. Advanced Wipe and clean Dalvik, Cache, Data, System and Vendor.
3. Then proceed with the installation.
In my case I installed xiaomi.eu_multi_MIMAX3_V11.0.2.0.QEDCNXM_v11-10
Hope this helps!
irinho said:
I had the same problem when I backed up the global rom with OrangeFox and restarted the system without installing anything.
The following procedure worked for me.
User the latest version of TWRP 3.3.1 do not use OrangeFox
1. First you must remove the encryption, Wipe> Format Data, confirm by typing "yes"
2. Advanced Wipe and clean Dalvik, Cache, Data, System and Vendor.
3. Then proceed with the installation.
In my case I installed xiaomi.eu_multi_MIMAX3_V11.0.2.0.QEDCNXM_v11-10
Hope this helps!
Click to expand...
Click to collapse
Thanks a lot for the reply!
I somehow managed to get it working with OrangeFox, so I'm going to try it for awhile till it breaks. But I can't seem to pass the SafetyNet Check in Magisk, so I might have to your tips eventually.
What I did was:
1. Use the MI Flash tool + 11.03 CN Fastboot ROM to get out of the boot loop.
2. Loaded OrangeFox-R10.1-stable-nitrogen and Magisk-v20.4 on an SD Card
3. ADB + Fastboot to install twrp-3.3.1-0-nitrogen, then installed OrangeFox
4. Using OrangeFox, installed Magisk-v20.4
Hadron001 said:
Thanks a lot for the reply!
I somehow managed to get it working with OrangeFox, so I'm going to try it for awhile till it breaks. But I can't seem to pass the SafetyNet Check in Magisk, so I might have to your tips eventually.
What I did was:
1. Use the MI Flash tool + 11.03 CN Fastboot ROM to get out of the boot loop.
2. Loaded OrangeFox-R10.1-stable-nitrogen and Magisk-v20.4 on an SD Card
3. ADB + Fastboot to install twrp-3.3.1-0-nitrogen, then installed OrangeFox
4. Using OrangeFox, installed Magisk-v20.4
Click to expand...
Click to collapse
I have not yet rooted with magisk on xiaomi.eu so I have no way of giving an opinion on what may have gone wrong in your case.
But did you install the most current magisk from magisk.me and clear the cache?
maybe this video can help you. shows a Brazilian installing orangefox and rooting with magisk in the global rom and everything works, Magisk passes the SafetyNet test. https://youtu.be/O5bq1HMFREI?t=328
Ive already flashed a few phones, but this is the first time that Ive got CMD error "FAILED (remote: (recovery_a) No such partition)". So I booted twrp.img, falshed ArrowOS and TWRP from within TWRP and it said something about Slot A and B, which I dont understand ... some guide also said to Format Data, which I did, and then I just could boot into TWRP in Slot A, and no OS on Slot B, which rebooted me into Slot A. I couldnt find any info about this and I dont know what to do. Anybody knows how to properly flash TWRP and custom ROMs please ?
Start fresh by flashing stock MIUI rom through fastboot and proceed from there
1 Boot once into MIUI and reboot into fastboot
2 fastboot boot twrp.img (from platform tools folder)
3 Flash custom rom like ArrowsOS with inject twrp option checked
4 Reboot recovery
5 Format Data by typing "yes"
6 Reboot to system
7 Done
Follow the TWRP install instructions by fastboot boot TWRP.img
advanced, install TWRP
It should then reboot and TWRP will be installed
Then proceed as above by flashing a ROM e.g ArrowOS with TWRP inject.
Then reboot TWRP and wipe data
Use "fastboot boot TWRP.img" to temporarily boot TWRP.
You can install TWRP by using "Install to Ramdisk" inside TWRP and selecting TWRP.img
Cvenda said:
Ive already flashed a few phones, but this is the first time that Ive got CMD error "FAILED (remote: (recovery_a) No such partition)". So I booted twrp.img, falshed ArrowOS and TWRP from within TWRP and it said something about Slot A and B, which I dont understand ... some guide also said to Format Data, which I did, and then I just could boot into TWRP in Slot A, and no OS on Slot B, which rebooted me into Slot A. I couldnt find any info about this and I dont know what to do. Anybody knows how to properly flash TWRP and custom ROMs please ?
Click to expand...
Click to collapse
Did you manage to fix it? I got into the same problem, I could only fix it downloading the most updated version of adb/fastboot. I don't remember where I downloaded it, but it was what solved this problem for me.
pedrowood said:
Did you manage to fix it? I got into the same problem, I could only fix it downloading the most updated version of adb/fastboot. I don't remember where I downloaded it, but it was what solved this problem for me.
Click to expand...
Click to collapse
well Iam still confused about that Slot A/B thing, but since Ive probably bricked my phone, I flashed the fastboot ROM through MiFlasher and I havent tried flashing TWRP or custom ROM since, there are some things I really like about MIUI so Iam gonna see which ROM Iam gonna choose in the future
Cvenda said:
well Iam still confused about that Slot A/B thing, but since Ive probably bricked my phone, I flashed the fastboot ROM through MiFlasher and I havent tried flashing TWRP or custom ROM since, there are some things I really like about MIUI so Iam gonna see which ROM Iam gonna choose in the future
Click to expand...
Click to collapse
Slot A and B refer to Project Treble, where there are 2 separate partitions. 1 for OEM like Samsung and other for core Android OS. That way Google can update the OS partition with security updates without having to wait for Samsung to implement those security update into their version of Android, as was the case before Galaxy S9. Needless to say, this way security updates get pushed out way faster, because there is no need to wait an entire year (I'm looking at you Samsung) for OEM to finally implement it. Hope this clears things up for you.
Milan-XDA said:
Slot A and B refer to Project Treble, where there are 2 separate partitions. 1 for OEM like Samsung and other for core Android OS. That way Google can update the OS partition with security updates without having to wait for Samsung to implement those security update into their version of Android, as was the case before Galaxy S9. Needless to say, this way security updates get pushed out way faster, because there is no need to wait an entire year (I'm looking at you Samsung) for OEM to finally implement it. Hope this clears things up for you.
Click to expand...
Click to collapse
reason for slots
Robert314 said:
Follow the TWRP install instructions by fastboot boot TWRP.img
advanced, install TWRP
It should then reboot and TWRP will be installed
Then proceed as above by flashing a ROM e.g ArrowOS with TWRP inject.
Then reboot TWRP and wipe data
Click to expand...
Click to collapse
there is a slight problem with this ... I cannot upload any file to the phone, because I have wiped Data, so there is no folder that I can access from the PC, so I can only sideload .zip files, and most of the .zip files just doesnt work for some reason, only ArrowOS, but not the PixelExtended, nor CrDroid ... I cannot even sideload TWRP.img to install it into ramdisk
EDIT: after sideloading ArrowOS and booting TWRP using "fastboot boot twrp.img", I can access internal storage, so I uploaded twrp.img into /sdcard/Download folder, installed it into ramdisk, rebooted to Recovery and now successfully flashing CrDroid ROM that I uploaded to /sdcard/Download
Cvenda said:
there is a slight problem with this ... I cannot upload any file to the phone, because I have wiped Data, so there is no folder that I can access from the PC, so I can only sideload .zip files, and most of the .zip files just doesnt work for some reason, only ArrowOS, but not the PixelExtended, nor CrDroid ... I cannot even sideload TWRP.img to install it into ramdisk
Click to expand...
Click to collapse
You can adb transfer files in TWRP. You could also use a USB stick connected via OTG cable
Robert314 said:
You can adb transfer files in TWRP. You could also use a USB stick connected via OTG cable
Click to expand...
Click to collapse
its behaving so randomly ... I often get error kInstallDeviceOpenError, even tho I successfully installed that ROM at least one time ... I dont know which slot (A/B) to use and when ... now I have ArrowOS in slot A and CrDroid ins lot B, and I cannot flash anything from booted TWRP.img ... Iam gonna try to install TWRP into ramdisk again from USB OTG
Cvenda said:
its behaving so randomly ... I often get error kInstallDeviceOpenError, even tho I successfully installed that ROM at least one time ... I dont know which slot (A/B) to use and when ... now I have ArrowOS in slot A and CrDroid ins lot B, and I cannot flash anything from booted TWRP.img ... Iam gonna try to install TWRP into ramdisk again from USB OTG
Click to expand...
Click to collapse
In order to wipe the super partition (both A/B and data) flash Xiaomi.eu and then wipe data
Robert314 said:
In order to wipe the super partition (both A/B and data) flash Xiaomi.eu and then wipe data
Click to expand...
Click to collapse
how exactly should I proceed ? flash fastboot stock ROM with MiFlasher, boot into bootloader, boot twrp.img, wipe data, and then what ? which slot do I choose ? should I install TWRP into ramdisk, reboot into recovery and then flash custom ROM ?
Cvenda said:
how exactly should I proceed ? flash fastboot stock ROM with MiFlasher, boot into bootloader, boot twrp.img, wipe data, and then what ? which slot do I choose ? should I install TWRP into ramdisk, reboot into recovery and then flash custom ROM ?
Click to expand...
Click to collapse
ROM: xiaomifirmwareupdater.com/archive/miui/alioth/
Mi Flash: xiaomiflashtool.com
ADB & Fastboot: developer.android.com/studio/releases/platform-tools
TWRP: https://forum.xda-developers.com/f/xiaomi-poco-f3-xiaomi-mi-11x-redmi-k40.12161/?prefix_id=33
Clean Install of Xiaomi.eu ROM:
Flash Stock ROM with Mi Flash
Boot System once (to create /data)
Boot TWRP from Nebrassy or @Vasishoth
Flash Xiaomi.eu ROM
Format Data & Dalvik Cache
dreamytom said:
ROM: xiaomifirmwareupdater.com/archive/miui/alioth/
Mi Flash: xiaomiflashtool.com
ADB & Fastboot: developer.android.com/studio/releases/platform-tools
TWRP: https://forum.xda-developers.com/f/xiaomi-poco-f3-xiaomi-mi-11x-redmi-k40.12161/?prefix_id=33
Clean Install of Xiaomi.eu ROM:
Flash Stock ROM with Mi Flash
Boot System once (to create /data)
Boot TWRP from Nebrassy or @Vasishoth
Flash Xiaomi.eu ROM
Format Data & Dalvik Cache
Click to expand...
Click to collapse
in case of flashing custom ROM, are the steps same ? just instead of Xiaomi.eu ROM I flash PE, or CrDroid ? and should I format data and dalvik also or wipe data (that option where I need to type YES) ? Ive found official guide for flashing CrDroid, but Iam stuck st booting animation for 30 minutes
Cvenda said:
in case of flashing custom ROM, are the steps same ? just instead of Xiaomi.eu ROM I flash PE, or CrDroid ? and should I format data and dalvik also or wipe data (that option where I need to type YES) ? Ive found official guide for flashing CrDroid, but Iam stuck st booting animation for 30 minutes
Click to expand...
Click to collapse
Go into TWRP and press wipe then format data (type yes).
regedit12345 said:
Go into TWRP and press wipe then format data (type yes).
Click to expand...
Click to collapse
I have stock rom in slot A (bootable and working) and custom rom in slot B (stuck at booting animation), and I should format data while being in slot A right ?
Cvenda said:
I have stock rom in slot A (bootable and working) and custom rom in slot B (stuck at booting animation), and I should format data while being in slot A right ?
Click to expand...
Click to collapse
Doesn't matter. Just select format data > yes > reboot to system
regedit12345 said:
Doesn't matter. Just select format data > yes > reboot to system
Click to expand...
Click to collapse
sooo what seemes to work for me now is, that I formated data, then flashed PE ROM from OTG and booted into it without any problems
Find Device storage Corupted. Your device is unsafe now. This messgae keeps popping now and then anyway to fix it. Using Stock MIUI 12 13.0.10. Device is Mi 11x (Aliothin).
tried recloking and full flash of firmware erasing everything still no hope.
Any fix
Hi,
Read my post,
CTS doesn't pass even with locked bootloader.
I have poco f3 and i installed a custom ROM on it but then i wanted to use MIUI but when i locked bootloader i got device memory corrupted issue which someone suggested me to fix by flashing persist img and i did that but another problem arise...
forum.xda-developers.com
I hope it helps.
Thanks @johnr64.
Followed these steps using OrangeFox Recovery. TWRP had persmission issues.
1. Boot to OrangeFox Recovery ( Command below only works if booted to OrangeFox Recovery, if you dont have recovery installed just use fastboot command : Fastboot boot ornagefoxrecovery.img)
2. Go to 3 dot menu at bottom and choose terminal
3. type: dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
4. After its finished reboot to the system, finished and fixed.