Related
Edit: Solved, see bottom
ROM (D6633_Customized HK_1290-5630_23.4.A.0.546_R6C_HK_SuperSU2.46_XZDR2.8.21-signedv2)
Bit of a dumb move on my part. It all started when my snapchat stopped working, I updated, and then Titanium Backup wouldn't restore the data properly (giving me "parse error"). I was trying to fix that and read online that sometimes this is caused by improper permissions, so I booted into recovery mode, couldn't find the option, but somehow decided "hey, maybe my root permission (?) is wrong slash it's 6am and I just watched a wild 2016 election end" and I hit the button. Now my phone is stuck in a bootloop.
So my question:
1) What exactly does re-root phone do (in CWM), and why would that have messed me up? Is it because I have a pre-rooted rom?
2) I wiped cache and delvik and it doesn't help
3) How do I fix this? I was thinking of loading a SuperSU zip on the SD card from my computer and flashing that, assuming somehow a corrupted root is at fault. I can't seem to get the thing in ADB mode as a side note.
3b) If that seems like a good idea, does it matter what one I use?
4) If I reflash the ROM, it should keep my apps and stuff, ya? I don't actually care if my phone is crippled, I just need it to work long enough to properly back up some media, and mainly get my whatsapp over to my new SIM card. If I can't get in it's forever stuck on my old number which I don't have the SIM for anymore.
Any help would be GREATLY appreciated.
Edit: I don't know how to delete this. Anyways, with other resources I found out that because I used a pre-rooted ROM, there were issues with using CWM to try to do the rooting with its built in functions, softbricking the phone. Reflashing the original pre-rooted ROM worked fine.
Hello!
I seem to only post on this homepage whenever I f*** up, and so here I am...
I'll try to explain this as best as possible.
I decided I wanted to root my OP6 so I could cheat in PoGO since the weather turned bad.
I followed a guide precisely - https://oneplus.gadgethacks.com/how-to/root-your-oneplus-6-with-magisk-beginners-guide-0185541/ - this one specifically.
So my phone is now rooted and I've got Magisk and TWRP, everything seems fine. I go to download the Root Checker and it gives me an error that it's not compatible with my device.
I freak out and try out various things inside Magisk Hide to make it work. It eventually works out and "YAY MY PHONE IS IN FACT ROOTED". Although the SafetyNet thing gives me an error.
Okay, I Install PoGo, go to Magisk Hide and select it. Start it up, log in.... Failed.... "Oh no". Failed... Failed... Failed...
Urgh, whatever I think. Let's just get rid of the root and TWRP then. Can't be too hard? Oh Magisk has an uninstall feature, let's hit that up. Uninstalled. Huh? PoGo still not working.
I've spent a few hours now trying to get this to work, my phone is wiped and not really useful. Let's remove TWRP then right? Right??! Steps are simple.
Wipe Phone, get a stock OP6 rom thing.
Press the install button. Nothing happens, wait for 10 minutes. It now asks me to reboot, no errors show up.
Good, it's booting. It's been twenty minutes, still booting... 30 minutes, still booting...
I'm stuck.
I know I screwed up somewhere, but does anyone know what I can do?
I can reboot to recovery, which is stock recovery now.
EDIT: Okay, so I couldn't idly sit by, so I went into recovery and wiped data yet again. It booted up this time and is now asking me to update my OS!
One problem resides, I can't download Netflix, which means I'm tripping the safetynet thing. Is it because my bootloader is unlocked? If so, how do I lock it again?
EDIT2: I really can't sit still. Googled, found out how to lock bootloader. Let's see if Netflix works.
EDIT3: Netflix can be downloaded, so I think everything works as it should again. I'm now installing official updates to my phone. If it breaks, I'll be here again.
LOL.
At least you have a working device again.
Once you unlock your bootloader your widevine level goes to 3 (level 1 is default meaning bootloader locked). There are people reporting to get netflix working but HD streams seem to be broken then so just SD quality.
I guess you messed up with your a/b partitions. This happens when you don't install twrp properly to both slots. Installing means to boot twrp with fastboot and install latest twrp.zip.
After that you flash magisk. Right now to keep dm verity you need to flash magisk 16.0 (stable). After rebooting your system, open magisk switch to beta channel and install latest version (16.7) directly through the magisk app. After reboot you should have dm verity ticked.
For safety.net passing: magisk needs an update due to api changes from safety.net/ google.
If my rom doesn't boot I just reinstall latest oos build, boot twrp and flash twrp.zip, then magisk.
lol, glad you have everything up again. I remember when i used to go through these scenarios on the regular. Do you want root for any specific reason? i only ask because after years of being rooted, i really feel that the pros no longer outweigh the cons. Once the whole A/B partition thing was introduced (i believe it was in Nougat?), it opened up the doors to a lot of possible issues with softbricking, etc. I'm still here on xda to see if there's anything that will bring back the itch for tinkering/rooting, but for the time being, you can find just about any nonroot alternative to what you might need.
PhilGizzle said:
Hello!
I seem to only post on this homepage whenever I f*** up, and so here I am...
I'll try to explain this as best as possible.
I decided I wanted to root my OP6 so I could cheat in PoGO since the weather turned bad.
I followed a guide precisely - https://oneplus.gadgethacks.com/how-to/root-your-oneplus-6-with-magisk-beginners-guide-0185541/ - this one specifically.
So my phone is now rooted and I've got Magisk and TWRP, everything seems fine. I go to download the Root Checker and it gives me an error that it's not compatible with my device.
I freak out and try out various things inside Magisk Hide to make it work. It eventually works out and "YAY MY PHONE IS IN FACT ROOTED". Although the SafetyNet thing gives me an error.
Okay, I Install PoGo, go to Magisk Hide and select it. Start it up, log in.... Failed.... "Oh no". Failed... Failed... Failed...
Urgh, whatever I think. Let's just get rid of the root and TWRP then. Can't be too hard? Oh Magisk has an uninstall feature, let's hit that up. Uninstalled. Huh? PoGo still not working.
I've spent a few hours now trying to get this to work, my phone is wiped and not really useful. Let's remove TWRP then right? Right??! Steps are simple.
Wipe Phone, get a stock OP6 rom thing.
Press the install button. Nothing happens, wait for 10 minutes. It now asks me to reboot, no errors show up.
Good, it's booting. It's been twenty minutes, still booting... 30 minutes, still booting...
I'm stuck.
I know I screwed up somewhere, but does anyone know what I can do?
I can reboot to recovery, which is stock recovery now.
EDIT: Okay, so I couldn't idly sit by, so I went into recovery and wiped data yet again. It booted up this time and is now asking me to update my OS!
One problem resides, I can't download Netflix, which means I'm tripping the safetynet thing. Is it because my bootloader is unlocked? If so, how do I lock it again?
EDIT2: I really can't sit still. Googled, found out how to lock bootloader. Let's see if Netflix works.
EDIT3: Netflix can be downloaded, so I think everything works as it should again. I'm now installing official updates to my phone. If it breaks, I'll be here again.
Click to expand...
Click to collapse
thefallen924 said:
lol, glad you have everything up again. I remember when i used to go through these scenarios on the regular. Do you want root for any specific reason? i only ask because after years of being rooted, i really feel that the pros no longer outweigh the cons. Once the whole A/B partition thing was introduced (i believe it was in Nougat?), it opened up the doors to a lot of possible issues with softbricking, etc. I'm still here on xda to see if there's anything that will bring back the itch for tinkering/rooting, but for the time being, you can find just about any nonroot alternative to what you might need.
Click to expand...
Click to collapse
It is just different.
You have to forget the "old way" and then you don't face any problems.
Same with encryption that wasn't present before.
I still can't live without root.
Too many missing functions (xpsoed edge, titanium, afwall, xprivacy, gravitybox).
And the newer rom system by just applying a magisk module is pretty cool.
pdppdp said:
LOL.
At least you have a working device again.
Once you unlock your bootloader your widevine level goes to 3 (level 1 is default meaning bootloader locked). There are people reporting to get netflix working but HD streams seem to be broken then so just SD quality.
I guess you messed up with your a/b partitions. This happens when you don't install twrp properly to both slots. Installing means to boot twrp with fastboot and install latest twrp.zip.
After that you flash magisk. Right now to keep dm verity you need to flash magisk 16.0 (stable). After rebooting your system, open magisk switch to beta channel and install latest version (16.7) directly through the magisk app. After reboot you should have dm verity ticked.
For safety.net passing: magisk needs an update due to api changes from safety.net/ google.
If my rom doesn't boot I just reinstall latest oos build, boot twrp and flash twrp.zip, then magisk.
Click to expand...
Click to collapse
hey, i rooted my device yesterday on 10.3.3, all was good until i got into a bootloop after installing busybox from the magisk repo. i keep going back to the fastboot mode, i still have access to twrp but sadly i didnt make a nandroid backup. i really dont know what to do now and i know this is not the relevant thread to ask this question. im sorry, but if anyone knows a method to solve this please let me know. thanks
I would make a nandroid (just in case) now and then flash the full firmware again, reflash twrp and then xxx. This keeps your data and you should have a working system.
pdppdp said:
I would make a nandroid (just in case) now and then flash the full firmware again, reflash twrp and then xxx. This keeps your data and you should have a working system.
Click to expand...
Click to collapse
Make a nandroid of the Bootlooped system? Is it OK to flash the full firmware without performing a factory reset? Thanks...
EDIT- thanks a lot for this method Bro. .worked like a charm and now I'm back into system. .reflashing twrp and magisk now..thanks again
You're welcome.
Nandroid of your data in case something goes wrong and wipes the device. System is 'replacable'
pdppdp said:
You're welcome.
Nandroid of your data in case something goes wrong and wipes the device. System is 'replacable'
Click to expand...
Click to collapse
Yup that's a good precaution to take in case things go south. Anyways i was reading your earlier post on how unlocking the bootloader sets the widevine level to 3 and causes some problems to use netflix. I was unaware of this issue before i rooted. It's really a bummer, soon after reading your post i realized that netflix was missing and i went to play store to download. I couldn't find the app,then i downloaded the app from apk mirror and after installation i had this error that the device is not supported by the app. I did some research on the issue and on a OnePlus forum i found a solution, i went to the netflix website and logged in with my account, then i tried playing something which indicated me to download the app from play store and viola, the app got downloaded and works perfectly fine, it's kinda surprising. Thought I'd share this here if in case it might work for someone else...
So here is situation.
Phone been running 8.x version of havocos for months, however I was never fully happy due to broken usb tethering and random lockups (blue light freeze).
I decided to work on the phone 2-3 days ago, this involved doing a manual backup of all of data/media, and a nandroid backup. As well as some exports of configs in tasker etc.
I then flashed OOS stock, and nolimits, discovered tethering was still broken (yet it works with same sim in samsung galaxy s7 and hauwei).
This was the only issue tho, everything else was functioning as expected, phone was still fast.
Then I needed quick access to something that was on my phone from havocos, so decided to do a nandroid restore, this nandroid backup had all partitions ticked. The restore I also had all ticked.
The restore failed with an error 255 during data restore, I googled and found out is a nasty known bug for 2 years on TWRP, this backup was done on 3.2.3, I know now is a newer 3.3.x where this particular bug with corrupt backups might possibly be fixed.
I decided to try and boot havoc anyway but it boot looped, so I then went back into TWRP, and restored the vendor partition which was skipped. As it stopped on data, still boot looped, but also now this created a device is corrupt error on every rom boot even on stock OOS.
I spent ages trying to fix this error and during the process, discovered my phone no longer can be detected in flash boot as a com device in windows so currently the phone cannot be used with the MSM tool.
Eventually I reflashed stock using a flash-all script from here, and also put back on twrp using that script, and noticed even more issues that were not there before.
1 - phone is now much slower, stock before booted in one second after first boot, now its way way slower. Over 10 seconds so 10x as slow.
2 - I think before was a cache partition but is now gone. Supposedly these arent a thing anymore tho.
3 - nolimits zip will no longer flash with an error 1, I did exact same process as before but simply doesnt work now, the twrp detailed log right before the error 1 says "Please install the latest Magisk!" which suggests its failing to detect magisk.
4 - camera app is way slower, and OOS feels slower, laggier in general than before the problem.
5 - MTP no longer works when phone is booted up, again this is stock OOS and even if phone isnt rooted no magisk etc. But still works in TWRP. Basically the device pops up, I can see internal storage, but the size information is missing, and is no visible files/folders.
From what I can see I think my EFS is fine, I see an imei number.
I did fix the corrupted device error using a reboot command someone posted in that thread, so that error is gone now at least.
Try to flash oxygen os beta version from the official download links, let it install the stock recovery, then boot into rom, finish the installation progress by just skipping it and then factory reset it twice from recovery mode.
after doing that and finishing the setup , try to take picture and see if its saves it to gallery ( if the picture delete it self try to factory reset it through recovery for 1 more time)
I think you have figured out whats wrong, it just clicked, and I went to post and found your post so sorry no reply yet.
Indeed the problem seems to be a lack of /data/media/0
I have multiple times wiped data, and twrp has been putting files directly in /data/media, I just discovered I Cannot even take screenshots, magisk cannot download modules as well.
So I guess the stock recovery creates this structure?
Pretty shocking that twrp doesnt fix this or even have an option to. I will report back and let you know how things go, thanks.
Issue still there after stock recovery reset, wow these phones are damn hard to work with.
Also it seemed to do nothing, no settings were lost etc.
So basically stock recovery even if I choose full wipe does nothing, there seems to be some kind of lock on the internal storage that anything made by one plus is refusing to write.
I wonder if this is due to the device is corrupt message I had before where it said the device can no longer be trusted.
I can confirm that files that are on there are now visible in file manager and root explorer. But file manager can do no writes. root explorer can create new stuff but cannot delete or overwrite anything there, gets access denied.
I propose to start over again following this guide, option flash-all-partitions.bat. Helped for me.
I already stated thats already been done.
I eventually got msm working. and that luckily worked.
@chrcol ..., but you've issues
chrcol said:
I already stated thats already been done.
I eventually got msm working. and that luckily worked.
Click to expand...
Click to collapse
In recovery, format data. Problem fixed. Wipe will never fix your problem but format will.
The module that did this was "liboemcrypto disabler" and was advertised as allowing DRM content to be viewed in full HD despite my bootloader being unlocked. It immediately put me in a boot loop after installing. I removed the magisk module from recovery but I was stuck in a boot loopstill and ended up having to wipe. I've done a full wipe, I've fully erased and decrypted the phone with ALL IN ONE tool and then installed a new stock ROM via fastboot. I then used TWRP to wipe EVERYTHING and then used ALL IN ONE TOOL to erase the phone and then used MSM tools to reflash a stock ROM and start from scratch while also choosing to wipe all data in the process. Netflix not working has persisted through all of this, it seems this module has touched a drm file that is normally out of reach in the wiping process / it's not replaced when doing a clean install. Another odd thing is that throughout this whole process, Nova Launcher stayed installed throughout all of the wipes. Any time I try to open Netflix it either says I need to update and clicking okay brings me to the play store where it tells me Netflix is not compatible on my device. Sometimes I get other error messages but it's always the same, Netflix doesn't work. The odd thing is I got it working on Pie in the process of unlocking my tmobile bootloader with the Android 10 DP3 so I could root it. Netflix actually worked for a second while I was on Pie, up until I updated to Android 10. This leads me to believe that the drm Android 10 is using is different from Pie and upgrading put me back to relying on the ruined drm file. I've even tried installing and uninstalling the magisk module that screwed all of this up hoping it would replace the original drm file but I've had no luck. This is such an odd problem. I had no clue any magisk module had the power to give your phone problems that literally can't be fixed through full wipes and reinstalls. I've tried removing netflix from ADB and reinstalling the apk manually but there's still no luck. The other streaming services that normally rely on this DRM are fine. If anyone has the slightest idea of what to do here I'd love to hear it! Are all drm files the same for everyone? If I were to aquire the drm file that was replaced while installing this thing could that possibly fix it? The file that is modified is under /vendor/lib/ and is named "liboemcrypto.so"
Hello,
About two months ago I successfully rooted that phone through Magisk. Now I am facing the told problem. I searched for some problems like mine, but it is not because of updates. I do not remember I have done something dangerous for the system. However, I tried to install this package. When I tried with the Android package installer, I got an error "it could not be installed". Then I tried to do it through this app manager for rooted devices, and it just stayed loading for a while until I just closed it. I entered the custom app manager and I realized that the app was recognized as an installed app, but however, I could not see it in the poco app launcher. I launched the app and it worked fine, but when tried to make f-droid a system app it displayed an error "/ directory could not be remounted as read-write". I left it be and removed that app. Everything fine... But the next morning the phone was asking for the SIM unlocking code. I unlocked both, the SIM and the phone, but after about five minutes it rebooted to MIUI recovery 5.0. If once in recovery mode the phone is inactive for a while, it automatically reboots to system. The rebooting time once unlocked the SIM was decreasing to two minutes. Apparently, it only will reboot if the SIM is unlocked, and the time is five minutes when the phone is cold and it decreases as it is being restarted. The phone it is not too hot when rebooted.
Thank you if you spent your time by reading the text above. Now the question: How can I fix it without losing my data? Regards.
PD: I do not have enough time to make a backup till it is rebooted, at least from system, and safe mode did not solve the issue.
You tried to install an obsolete app for moving apps to system, an app from 2016... no less?! What were you thinking?
Let me be honest and tell you that that move was extremely stupid. Chalk up your mistake to a brain fart, take the loss and try to reflash the firmware without formatting anything prior to doing so. Leave internal storage, dalvik, cache and everything else untouched. You just might make the phone bootable to backup your data, and then do a PROPER flash procedure.
Tomo123 said:
You tried to install an obsolete app for moving apps to system, an app from 2016... no less?! What were you thinking?
Let me be honest and tell you that that move was extremely stupid. Chalk up your mistake to a brain fart, take the loss and try to reflash the firmware without formatting anything prior to doing so. Leave internal storage, dalvik, cache and everything else untouched. You just might make the phone bootable to backup your data, and then do a PROPER flash procedure.
Click to expand...
Click to collapse
So therefore, which partition should I reflash with the stock ROM?
MxtApps said:
Hello,
About two months ago I successfully rooted that phone through Magisk. Now I am facing the told problem. I searched for some problems like mine, but it is not because of updates. I do not remember I have done something dangerous for the system. However, I tried to install this package. When I tried with the Android package installer, I got an error "it could not be installed". Then I tried to do it through this app manager for rooted devices, and it just stayed loading for a while until I just closed it. I entered the custom app manager and I realized that the app was recognized as an installed app, but however, I could not see it in the poco app launcher. I launched the app and it worked fine, but when tried to make f-droid a system app it displayed an error "/ directory could not be remounted as read-write". I left it be and removed that app. Everything fine... But the next morning the phone was asking for the SIM unlocking code. I unlocked both, the SIM and the phone, but after about five minutes it rebooted to MIUI recovery 5.0. If once in recovery mode the phone is inactive for a while, it automatically reboots to system. The rebooting time once unlocked the SIM was decreasing to two minutes. Apparently, it only will reboot if the SIM is unlocked, and the time is five minutes when the phone is cold and it decreases as it is being restarted. The phone it is not too hot when rebooted.
Thank you if you spent your time by reading the text above. Now the question: How can I fix it without losing my data? Regards.
PD: I do not have enough time to make a backup till it is rebooted, at least from system, and safe mode did not solve the issue.
Click to expand...
Click to collapse
flash the stock firmware with miflashtool and select de option "save_user_data" and done, the firmware will be flashed and your data will stay there
tutibreaker said:
flash the stock firmware with miflashtool and select de option "save_user_data" and done, the firmware will be flashed and your data will stay there
Click to expand...
Click to collapse
OK, that flash was successful, the root and the custom recovery were lost, but it is still rebooting. Should I flash all?
MxtApps said:
OK, that flash was successful, the root and the custom recovery were lost, but it is still rebooting. Should I flash all?
Click to expand...
Click to collapse
if you flash all your data will be lost, any way to install custom recovery and save your data from it ?