Related
Hello!
My Oppo Find 7 (international) seems to be bricked.
I'm on stock ROM COS 1.2.5 with stock recovery 1.0
After booting it stuck in the Setup-Wizzard with "settings has stopped"-Loop.
Unfortunately in stock-ROMs the USB-debugging is disabled, so i can't acces via adb fastboot to flash other recoverys.
And cause of the loop i can not enable USB-debugging...
The recovery (stock 1.0) let me only flash 1.2.5, no other ROMs work.
Things that work:
- entering fastboot (but no access via adb as i wrote)
- entering recovery and execute "zip from sd" (while sd means only internal sd here)
- normal boot to the f****** Setup-Assistant, enter PIN. At slect Language the "setting has stopped"-loop starts
- while the device is in loop, i can access the internal and external SD-card via PC, copy and delete files works
Please, has anybody an idea what to do ?
Thanks to all
Marco
Since you can get into fastboot, download a custom recovery, go to fastboot, type
fastboot flash recovery x
Replacing x with the full name and extension of the file, and install a ROM. Alternatively, if you want ColorOS, try downloading 1.2.4i, and installing it through the stock recovery. Then you can update from there
Hmmmm....
Positive! At this moment i learned that USB-debugging is needed for adb-access on a booted device, not for fastboot-access
Yes, i could flash TWRP via fastboot (puuhh, not bricked)
THANKS !!
Now i can mess around the "settings has closed"-Loop, wich is still in place.
(No wiping fixes the problem, even 1.2.1 nor 1.2.3 or whatever)
But i'm on the road again and can check out fixes.
Thanks again!!
That's weird. Did you ever install custom ROMs before having this issue?
Did you try formatting System in TWRP? But be careful, when you format System you have to install stock Color OS BEFORE rebooting your device. That means stay in TWRP after you format and install the ROM, then reboot.
I am new to android.
I Had temp rooted my phone using king root app.
I tried to download and install the OTA but while installing it would take me to the Fastboot mode and not update.
so I downloaded the flashify app from the play store and flashed the ota.
now my phone wont boot into the system even if I select factory reset it just comes back to fastboot mode.
I unlocked my phone and flashed twrp and using filemanager in twrp I saw that all my files are intact.
Is there any way I can boot into the system without loosing my data.
I read somewhere that all the options are mapped to flashboot so it is not rebooting to system, so is there any file I can edit to set the reboot option back to system .
Please help me.
So i had 4.0.1 rooted before. I decided to return to stock by flashing full 4.0.1 on TWRP. That's when I started getting the error. I flashed 3.2.8 on stock recovery 2.0 and dm-verity error is gone. But installing 4.0.1 on stock recovery 2.0 results to dm-verity error again. I cannot use adb sideload as my computer is too slow
More details: before, I successfully updated my OP3 with 3.2.8 to 4.0.1 without the dm-verity warning. After that, I flashed blu_spark's TWRP v11, swiped to allow modifications and rooted it with SuperSU 2.79 and flashed some mods, still no warning. Yesterday, I decided to return to full stock. I updated my TWRP to the unofficial 3.0.3-0 (the official one wasn't available yesterday yet), wiped system, cache, and data excluding internal storage, then flashed 4.0.1. The dm-verity warning started to show. I followed your guide and other guides here on XDA, I cannot fix it. The only solution I found is to rollback to 3.2.8, I installed the zip file on the stock recovery from your guide (flashing the recovery before). I'm having problems with adb sideload, PC lags so much and sideloading never finishes, so what I do is copy the zip file in the internal storage. After I flashed 3.2.8 and rebooted, the recovery was replaced by the V1.0 version that doesn't have the function of installing zip from internal storage, so I flashed your stock recovery again. Booting to the new recovery, I flashed the 4.0.1 zip and the dm-verity warning shows again.
Right now, my OP3 is on 3.2.8 with stock ROM, kernel, and recovery. No dm-verity warning. I don't know how to update to 4.0.1 without getting that again
Simple. New bootloader added that warning and the old one never had a dm-verity nag screen. Flash it and ignore it. It shows up due to TWRP installed.
Check the freedomos thread and download the 3.2.7 fw and flash with TWRP and its gone, I am not using the nougat fw on 4.0.2, always make nandroid backups
install beta 7 firmware
Don't bother! It's not worth it! It's just a stupid message!
I have tried by following these steps (I initially had twrp-3.0.2-1.28-oneplus3 installed):
1. booted to TWRP recovery;
2. copied recovery_OBT8N.img to phone;
3. installed stock recovery_OBT8N.img via TWRP as image > recovery;
4. booted to stock recovery (directly from TWRP);
5. while in stock recovery, I have wiped the phone (for a clean flash);
6. installed OxygenOS 4.0 (N) via ADB;
7. once the installation got completed, I rebooted the phone;
8. once the phone started, I did not finished the startup setting;
9. switched-off the phone and booted in fastboot mode;
10. flashed TWRP recovery - twrp-3.0.2-1.28-oneplus3 again;
11. switched off the phone;
12. started the phone in TWRP recovery; TWRP asks for a password to decrypt - ignore it;
13. wiped the phone (I wanted to do so to make sure it is a really clean install, even if this wipes everything);
14. rebooted again to TWRP recovery; this time I did not get any password prompt;
15. from TWRP, I copied SR1-SuperSU-v2.79-SR1-20161221223537.zip to phone storage (while connected to my laptop, obviously);
16. installed SR1-SuperSU-v2.79-SR1-20161221223537.zip, wiped data & cache and rebooted system;
17. everything went fine, with no dm-verity and rooted.
It will Keep showing Because You flashed Oxygen OS from TWRP . Try flashing this just after flashing the OS .
it will disable DM verity and disable force encryption .
cpt.macp said:
It will Keep showing Because You flashed Oxygen OS from TWRP . Try flashing this just after flashing the OS .
it will disable DM verity and disable force encryption .
Click to expand...
Click to collapse
Please try this method. Tested and it works for me.
step
Assuming your bootloader is unlocked. Copy
1. fastboot boot twrp twrp-3.0.2-1.28-oneplus3.img
2. Now you will be in TWRP, perform wipe -> Format Data, perform Wipe -> Advanced wipe "All folder" except USB-OTG
3. Reboot to recovery
4. adb sideload OnePlus3Oxygen_16_OTA_037_all_1701041839_401.zip (if adb cannot read, because filesize too big. Use laa_2_0_4.zip to fix the adb.exe first.)
5. After adb sideload done, reboot to TWRP immediately, enable MTP to copy the file: no-verity-opt-encrypt-5.1.zip into your internal storage and install no-verity-opt-encrypt-5.1.zip immediately.
Then everything will be fine.
bkcheah75 said:
Please try this method. Tested and it works for me.
step
Assuming your bootloader is unlocked. Copy
1. fastboot boot twrp twrp-3.0.2-1.28-oneplus3.img
2. Now you will be in TWRP, perform wipe -> Format Data, perform Wipe -> Advanced wipe "All folder" except USB-OTG
3. Reboot to recovery
4. adb sideload OnePlus3Oxygen_16_OTA_037_all_1701041839_401.zip (if adb cannot read, because filesize too big. Use laa_2_0_4.zip to fix the adb.exe first.)
5. After adb sideload done, reboot to TWRP immediately, enable MTP to copy the file: no-verity-opt-encrypt-5.1.zip into your internal storage and install no-verity-opt-encrypt-5.1.zip immediately.
Then everything will be fine.
Click to expand...
Click to collapse
I was not having any Issue . But Surely Your Help and concern is much appreciated
and Yes this is also one of the way to remove DM verity and use the zip
Currently using:
ROM - FreedomOS-2.1
TWRP - blu_spark_v11-oo3
Phone - Encrypted
I have the DM-Verity message at boot. Would reflashing FreedomOS-2.1 Through TWRP & then immediately flash no-verity-opt-encrypt.zip get rid of the message?
Thanks
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
I have a poco f3 using lineage os
So I updated Magisk to 26.1 and zygdisk wasn't working so I deactivated the modules via magisk in order to try to make it work. But the phone never rebooted it got stuck on bootloop. I tried to delete the modules via twrp but it didn't work, the phone would not boot and it showed the fastboot screen. Then I tried via orange fox, and i got the same problem. The thing is that all of my files are still in my phone and i made the stupid mistake of not doing any backup because i was travelling when i updated magisk.
Even if i try to do i dirty flash, add or delete anything via recovery the files do not get erased or installed. Everything stays the same after i restart.
bemuratt said:
I have a poco f3 using lineage os
So I updated Magisk to 26.1 and zygdisk wasn't working so I deactivated the modules via magisk in order to try to make it work. But the phone never rebooted it got stuck on bootloop. I tried to delete the modules via twrp but it didn't work, the phone would not boot and it showed the fastboot screen. Then I tried via orange fox, and i got the same problem. The thing is that all of my files are still in my phone and i made the stupid mistake of not doing any backup because i was travelling when i updated magisk.
Even if i try to do i dirty flash, add or delete anything via recovery the files do not get erased or installed. Everything stays the same after i restart.
Click to expand...
Click to collapse
I would try this:
Download magisk 26.1
Place into a folder
Make a copy of it in the same folder
Rename one copy to magisk.zip
Rename the other copy to uninstaller.zip
(example: magisk.apk would be renamed to magisk.zip, you want to make sure you're changing the file type from an apk to a zip)
Boot into recovery
Your pc should recognize your phones storage to transfer things in recovery
Transfer folder to phone (if needed)
Flash uninstaller.zip
Clear cache
See if your phone boots
If it does, you can boot back into recovery and try to flash the magisk.zip. If bootloop still, flash uninstaller.zip again
Zinnz said:
I would try this:
Download magisk 26.1
Place into a folder
Make a copy of it in the same folder
Rename one copy to magisk.zip
Rename the other copy to uninstaller.zip
(example: magisk.apk would be renamed to magisk.zip, you want to make sure you're changing the file type from an apk to a zip)
Boot into recovery
Your pc should recognize your phones storage to transfer things in recovery
Transfer folder to phone (if needed)
Flash uninstaller.zip
Clear cache
See if your phone boots
If it does, you can boot back into recovery and try to flash the magisk.zip. If bootloop still, flash uninstaller.zip again
Click to expand...
Click to collapse
I did what you said, uninstalled magisk then reboot system and it goes straight to the fastboot screen. Then I boot recovery again and there's no sign of the folders, it is like everything is the same as when the phone had its first bootlopp
bemuratt said:
I did what you said, uninstalled magisk then reboot system and it goes straight to the fastboot screen. Then I boot recovery again and there's no sign of the folders, it is like everything is the same as when the phone had its first bootlopp
Click to expand...
Click to collapse
Have you tried booting from the other slot? If you're on a switch to b, or vise versa
Yes I did, but partition B shows no files even with twrp or orange fox. It's like nothing gets actually deleted or written on the phone.
I don't know what to do. Because whatever i'm flashing be the recovery, be magisk, be any folder whatsoever, it doesn't stay in the device after rebooting
bemuratt said:
I don't know what to do. Because whatever i'm flashing be the recovery, be magisk, be any folder whatsoever, it doesn't stay in the device after rebooting
Click to expand...
Click to collapse
And even if i try to uninstall magisk, and the folders go away, its always there when i boot recovery again
Hi,
In fastboot, re-flash the original boot.img of your installed rom, maybe it'll work.
Good luck.
I did that, no success. I'll make a nanodroid backup, a clean flash and see what i can save from the backup!
Guys, I solved it.
I found out that the bootloop happened because I deactivated magisk module for android Auto. The system wouldn't start if the app didn't find the module. So I was trying to deleted via recovery, but it was not possible as I mentioned above.
So i did a backup with orange fox of the data and internal storage. Wiped the phone back to factory settings and reflashed the lineage os from scratch and rooted it again. Then i went back to recovery, restored everything and i was able to delete android auto and the phone booted with everything in it, all my pics, chats you name it!
Thanks for the help guys!