Basically, there was this annoying message saying that a new update was available, and i knew not to click install, but my dumb fingers hit it rather than normally swiping it away.
It said it was installed, and then asked to reboot, i said reboot later.
My phone ended up rebooting itself and now its in a bootloop. It takes me to recovery, but its not twrp.
I can get into fastboot mode, and i have a backup of my data, but how do i go about fixing this??
xIP- said:
Basically, there was this annoying message saying that a new update was available, and i knew not to click install, but my dumb fingers hit it rather than normally swiping it away.
It said it was installed, and then asked to reboot, i said reboot later.
My phone ended up rebooting itself and now its in a bootloop. It takes me to recovery, but its not twrp.
I can get into fastboot mode, and i have a backup of my data, but how do i go about fixing this??
Click to expand...
Click to collapse
Flash twrp and flash magisk after.
If you had magisk prior to update your boot.img needs patched. You could most likely flash a patched boot.img that matches and it will fix it or wipe all data and it will boot.
xIP- said:
Basically, there was this annoying message saying that a new update was available, and i knew not to click install, but my dumb fingers hit it rather than normally swiping it away.
It said it was installed, and then asked to reboot, i said reboot later.
My phone ended up rebooting itself and now its in a bootloop. It takes me to recovery, but its not twrp.
I can get into fastboot mode, and i have a backup of my data, but how do i go about fixing this??
Click to expand...
Click to collapse
Why didn't you hit install?? There's nothing wrong with taking otas. And likely the fact your boot looping is due to having either an encrypted device or a magisk module
joemossjr said:
Why didn't you hit install?? There's nothing wrong with taking otas. And likely the fact your boot looping is due to having either an encrypted device or a magisk module
Click to expand...
Click to collapse
I wasn't sure if it was safe or not. I've been out of the rooting game for awhile, and since coming back to it, I've noticed lots of change lol.
I managed to get my phone up and running, but i lost all data unfortunately. No biggie. I made a backup a few weeks ago, so i didn't lose everything entirely. Just bummed this happened on a day that was already going bad lol.
Thanks everyone for replying, much appreciated <3
Related
Hello everyone. Wanted to share an experience with my OPO,.
Today i rebooted the phone, and when it booted up it presented me the first configuration wizard. I thought, "ok this is strange" but after i completed again the configuration everything was still there.
Tonight I tried to install the XNPH33R update via TWRP, i loaded the file into the sdcard and rebooted into TWRP.
I thought "let's make a nandroid before, in case of problems", and i saw it could not mount the /system partition. The backup failed and then i tried to reboot. The phone does now not start and when i try to boot into TWRP, it reports that now ALL the partitions are borked and can't be mounted, reporting them 0MB, except for the boot one.
My question is, am i the only one that experienced something similar?!
I'm goin on to flash factory image but this seems a big problem!
Little hint: try to install another recovery (e.g. CWM, Philz...) before returning to stock
I doubt OnePlus (or any other mfg) would count this sort of thing a bug if your phone is running anything other than 100% stock.
CafeKampuchia said:
I doubt OnePlus (or any other mfg) would count this sort of thing a bug if your phone is running anything other than 100% stock.
Click to expand...
Click to collapse
Obviously i don't want to report a "bug" that i want oneplus to fix
I just wanted to know what happened, my partitions corrupted themselves by... rebooting?
since i saw that many users reported being stuck at the oneplus logo after updating to XNPH33R i wanted to know if this is related to their experience :silly:
dreamerguy00 said:
Little hint: try to install another recovery (e.g. CWM, Philz...) before returning to stock
Click to expand...
Click to collapse
I flashed the factory image except for recovery and everything works, same old TWRP now reports everything as ok and running.. it's just strange! i flashed countless devices and i own a Nexus 4 and a Nexus 5!
blackbird5308 said:
Obviously i don't want to report a "bug" that i want oneplus to fix
I just wanted to know what happened, my partitions corrupted themselves by... rebooting?
since i saw that many users reported being stuck at the oneplus logo after updating to XNPH33R i wanted to know if this is related to their experience :silly:
I flashed the factory image except for recovery and everything works, same old TWRP now reports everything as ok and running.. it's just strange! i flashed countless devices and i own a Nexus 4 and a Nexus 5!
Click to expand...
Click to collapse
Sorry wrong thread
Sent from E.P.D.Center
I had the same weird problem last night.....
Except my recovery was also reverted to stock.
it happened after i got notifed about an update available couple days in a row which i canceled.
I even have Droidwall and everything but a few apps are blocked from data usage.
What i would suggest is to freeze the ""system update" system app.
I kinda have a feeling the OTA updates have something to do with it.
This happend to me 1 other time a while back with an HTC One X device. Same pattern, System update notifications then couple days of ignoring .... then pooffff...
blackbird5308 said:
Hello everyone. Wanted to share an experience with my OPO,.
Today i rebooted the phone, and when it booted up it presented me the first configuration wizard. I thought, "ok this is strange" but after i completed again the configuration everything was still there.
Tonight I tried to install the XNPH33R update via TWRP, i loaded the file into the sdcard and rebooted into TWRP.
I thought "let's make a nandroid before, in case of problems", and i saw it could not mount the /system partition. The backup failed and then i tried to reboot. The phone does now not start and when i try to boot into TWRP, it reports that now ALL the partitions are borked and can't be mounted, reporting them 0MB, except for the boot one.
My question is, am i the only one that experienced something similar?!
I'm goin on to flash factory image but this seems a big problem!
Click to expand...
Click to collapse
Hi there. Recently (just yesterday) I tried flashing TWRP 3.1.0-0-herolte via Odin V3.12.3.0. However I ran into a little issue. Bootloop. TWRP seemed to work fine, but the phone wouldn't boot into android (stock touchwiz), exhibiting the 'samsung galaxy S7' logo periodically, but not going past that. Firstly I'll give some details on the phone and how I 'tried' to to flash TWRP. The phone I have is an Exynos variant SM-G930F running Android 7.0 and the recent update from late March. It is an Australian model (otherwise known as the 'international' version I think). Anyway as for what I was using as a guide, it was this. Before attempting this I enabled 'OEM unlocking' within the developer options but not 'USB debugging' (not sure if this contributed to the issue, but thought I'd mention it anyway). Later on I downloaded the Samsung Mobile Drivers and the tar file for TWRP. Installed the drivers, opened up Odin, entered download mode on the S7. I placed the tar file in AP and connected via micro usb. Almost everything, including auto-reboot, was turned off except F. Reset Time. Though chances are I probably left it on because I'm a doofus. After all that I pressed 'start' without doing any button combinations. Then after the screen went blank I pressed volume up + home hey + power button, roughly all at the same time. And then I entered TWRP. I then swiped to 'allow system modifications'. However as I didn't want to root the phone at the time, I decided to power it off through the menu. The next time I pushed the power button however, it was stuck in a bootloop. I then went back into TWRP and noticed that when I went into the install menu and was looking at the internal storage it appeared as 0mb (I thought that twrp had deleted all my files at the time), and I couldn't access the files I normally do like the downloads folder or app folders. However it seemed like most of the system folders were there like 'root' and 'data' etc. I then formatted the data and then did a factory reset as I thought it might fix the problem but it didn't. I swiped to install the twrp app but unchecked the two boxes. I then did some research and found out that if I ever were to run into an issue like this that I should flash the stock firmware, which is what I did. And viola! It worked again! I was slightly stressed at the time, lol. Luckily the apps and data I had previously were stored in the cloud.
After all this I have a question, what do you guys think I did wrong? Have you ran into this issue before? And what do you think may have caused the bootloop. I eventually want to start rooting my S7 and perhaps flash a rom, but I don't want to run into the issue again. Cheers!
P.S. I'm probably the biggest tech noob I know so go into a little bit of detail if you know what I did wrong so I don't make the same mistake again
Sounds like you hit the problem listed in step 9 & 10.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot
Click to expand...
Click to collapse
You swiped to allow system modifications, but you chose not to root and turned it off.
I don't see any mention of you flashing the dm-verity and force encryption disabler zip in TWRP which is required even if you're not rooting.
Beanvee7 said:
Sounds like you hit the problem listed in step 9 & 10.
You swiped to allow system modifications, but you chose not to root and turned it off.
I don't see any mention of you flashing the dm-verity and force encryption disabler zip in TWRP which is required even if you're not rooting.
Click to expand...
Click to collapse
Hm, that might actually be it. As a question how would be able to do that? Do I need to download that separately or something ( the dm-verity and encryption disabler zip I mean)?
EDIT
Actually never mind, it seems to say it right within the guide lol. So the problem should go away if I do that first yeah?
Yep just download it and put it on an SD card or transfer to the phones internal storage (I think TWRP lets you USB transfer) and go install zip in TWRP and select it.
That should stop your boot issues after installing TWRP, should even work even if you do it after a failed boot.
Beanvee7 said:
Yep just download it and put it on an SD card or transfer to the phones internal storage (I think TWRP lets you USB transfer) and go install zip in TWRP and select it.
That should stop your boot issues after installing TWRP, should even work even if you do it after a failed boot.
Click to expand...
Click to collapse
Hey bro, just wanted to say thanks. Got it rooted soon after as well. I found out I had to format data first before because it wouldn't let me install any zips. But after doing that it worked without any hiccups.
Cheers.
You should reset/wipe ur device after you have installed twrp through odin. That's a simple that some people wouldn't see in the tutorial. Then if you want root access you can flash SuperSu. Hope your problem will be solved. Good luck.
amalantony said:
You should reset/wipe ur device after you have installed twrp through odin. That's a simple that some people wouldn't see in the tutorial. Then if you want root access you can flash SuperSu. Hope your problem will be solved. Good luck.
Click to expand...
Click to collapse
Already did that before bro. Works as swell as a bell.
TheNickleS said:
Hey bro, just wanted to say thanks. Got it rooted soon after as well. I found out I had to format data first before because it wouldn't let me install any zips. But after doing that it worked without any hiccups.
Cheers.
Click to expand...
Click to collapse
Glad it's all working.
First time I installed TWRP I installed a ROM straight after which said to to format data, so never knew TWRP install alone needed the format data too.
Beanvee7 said:
Glad it's all working.
First time I installed TWRP I installed a ROM straight after which said to to format data, so never knew TWRP install alone needed the format data too.
Click to expand...
Click to collapse
From what I understand that's because the ldm-verity triggers. And so formating the data removes any encryption allowing for things to be flashed. But because I didn't do all of that first my S7 wouldn't boot up past flashing twrp.
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...
I have a well and heavily used Galaxy S5 (GM-900P) and about 2 months ago it started accting up pretty hard. Becoming very very slow so I decided to update to the latest sprint firmware and install a new(er) rom ([ROM][QD1][6.0.1]14Dec2017] Stock-ish Plus Tidbits and Magisk) and all was good for about 5 days and the phone started having apps crash/force close like crazy and most the time just reinstalling them would fix it but a bunch of google play services would crash and would have to uninstall the updates then it would work again for a day or so, sometimes it would randomly restart and get stuck at the boot screen and the phone would get crazy hot and the only way out of it was to boot into the recovery and then reflash the stock firmware in odin again then reinstall the rom. Then I had my phone all of a sudden act like there was no sim card in it and originally though it was a sim card issue but turns out it wasnt, I had to boot into the recovery and do a full wipe of everything reflash the stock firmware yet again and then reinstall the rom again. That happened twice in a matter of a week. At my wits end I decided to give LineageOS v16 a try so I boot into recovery, do a full wipe, boot into download mode, flash the latest stock firmware in odin, then boot right to recovery, flash LineageOS 16.0 then latest Magisk and all was great, for about a week, then Google services start crashing again and random apps crash over and over and even times the phone would slow down and reboot, get stuck at the boot screen and then eventually just reboot back into recovery by itself after failing to boot. But with LineageOS at least just reflashing the rom in the recovery will let it boot right back up sometimes and work as it should for another few days, other times too much stuff will just keep crashing so I do a full wipe and reflash LineageOS and all will be great for another few days to a week and it starts all over again. Its like stuff just randomly gets corrupted on the device and the only way out of it is to reflash the whole thing and start over and enjoy it until it does it again. Sometimes it will go days, sometimes a day later its all screwy again.
Also, TWRP always fails when I try to do a back up and it seems to always fail when in the data or data/private-app part of the system and its never at the same point.
I guess my question here is, could the onboard flash (the motherboard/logic board) be taking a crap on me? I really really dont want to give up on this phone just yet as it has everything I want in a phone and frankly, I just really really like it. I can get a new (used) motherboard for like $20 but even that kind of worries me cause I dont want to possibly be in this same position 3 months later again. I have a Galaxy S8+ (unlocked AT&T phone) that I refuse to use yet just cause I can not root it or unlock the bootloader.
Any help or ideas would be much appreciated and sorry for the long winded post.
could be wrong, on this one, But.....
If it was mew, I would go to stock . run that for a day, maybe 3... if all it well, then flash over what ever Rom you would like.
"KNOWING IT Work" is the key. Oh, another thing, that may help too . seen this on one of the LineageOS 15.1 or 16 is when you wipe ... System and Data, can be Reformatted, they have had some major success by also formatting it, (YES EXT4) but this will help to ensure nothing left over....
May even help with others Android 8.0, 8.1, 9.0....
Well, I have a new motherboard on the way so we'll see how that goes but I did manage to get the stock firmware on there and booted then I reflashed TWRP and then Magisk and going to just run it that way for a bit and see what happens.
I initially went in to TWRP, wiped data,system, etc... then flashed the stock firmware in Odin, then rebooted, got stuck at the Samsung boot logo so pulled the battery, booted to stock recovery, did a factory reset (Wiped everything, internal sd card included), then got it to boot, set the phone up, then rebooted to download mode, flashed TWRP, then rebooted again, set the phone up a bit more then decided to flash Magisk so I have root, and so far its working. 100% stock with magisk. Fingers crossed.
I still think there is an issue with the internal flash memory though as I can not get a TWRP backup to actually complete without failing. It always fails when backing up stuff in the data partition/section and never at the same point like its having read errors or something. I'll grab a TWRP log and post it up in a bit.
Well, that didnt last long. Within an hour, apps started crashing. I will make this thing work! LoL
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 ?