HI please help an old noob out
I recently got an S9 and coming from HTC realised touch wizz is awful.
I have flashed ROMs before (HTC desire) but not for a while so found a guide for ResurrectionRemix and cracked on with it.
I have TWRP 3.2.3-0 installed and flashed the ResurrectionRemix 6.0 on S9 ROM with stock Gapps (it all went as it should as far as I could tell no errors ect).
However, when I reboot the phone it just gets stuck on the Samsung boot screen.
Is there anyone who would help me troubleshoot where I went wrong, please?
I think maybe I need to root first?
Thanks
r3t0x said:
HI please help an old noob out
I recently got an S9 and coming from HTC realised touch wizz is awful.
I have flashed ROMs before (HTC desire) but not for a while so found a guide for ResurrectionRemix and cracked on with it.
I have TWRP 3.2.3-0 installed and flashed the ResurrectionRemix 6.0 on S9 ROM with stock Gapps (it all went as it should as far as I could tell no errors ect).
However, when I reboot the phone it just gets stuck on the Samsung boot screen.
Is there anyone who would help me troubleshoot where I went wrong, please?
I think maybe I need to root first?
Thanks
Click to expand...
Click to collapse
Go into twrp recovery then go to wipe, advanced, then check davlik and check cache then slide to wipe then reboot system
Should boot now but first boot takes a little
If after a few mins you still on that bubble shooting thing then you may have to reflash again
But remember after every flash wipe davlik
Flash ROM first
Flash magisk second(for root)
But only get magisk from XDA unless you trust others
Once up and running go into magisk and if you need to install then do that first then MAGISK HIDE all google apps is what I do especially gms I magisk hide that first also bank apps and certain games that have problems running I found they run perfect after I magisk hide them also go to downloads in magisk and install FORCE FAST CHARGE it helps with charging...
Have fun!!!
81! said:
Go into twrp recovery then go to wipe, advanced, then check davlik and check cache then slide to wipe then reboot system
Should boot now but first boot takes a little
If after a few mins you still on that bubble shooting thing then you may have to reflash again
But remember after every flash wipe davlik
Flash ROM first
Flash magisk second(for root)
But only get magisk from XDA unless you trust others
Once up and running go into magisk and if you need to install then do that first then MAGISK HIDE all google apps is what I do especially gms I magisk hide that first also bank apps and certain games that have problems running I found they run perfect after I magisk hide them also go to downloads in magisk and install FORCE FAST CHARGE it helps with charging...
Have fun!!!
Click to expand...
Click to collapse
Thanks, Dude I worked out what I was doing wrong. My phone is on the latest vendor firmware and as such RR will not work.
Unfortunately, I was following a guide and this was not mentioned, took a bit of reading on the XDA RR page to sus it out.
Since then I did try a GSI but it kept locking up on me so eventually went back to stock ROM.
I really would like a ROM which is as close to pixel as it can get (I wanted a pixel but this phone is trough work so had little choice).
I have seen Pixel Experience ROMs but I'm not sure if they will work with vendor firmware or not.
Related
Hello guys, I've searched a little and didn't find any posts that could help me specifically for the Galaxy Nexus.
I've flashed my phone a long time ago and have been using Paranoid Android for probably over a year.
The problem is, my cellphone was really really slow. So I decided to try a new ROM and re-flash it. And So I did.
I've tried flashing this Full_Auto R11 kernel then the CyanogenMod 12 and finally GAPPS.
I was getting error status 6 on Clockwork mod on gapps, but eventually got around it. But it didn't install play store, I've tried manually adding but it didn't work.
So I went for another 5.0 ROM (I'm really interested in getting android 5.0). Wiped all the data, all the cache, installed everything and rebooted.
Bam! Infinite booting screen.
No, I didn't create a nandroid backup because I'm really dumb.
So, I need your help. What I want to do is to get my phone working again with a 5.0 ROM (if possible).
I can boot into ClockWork Recovery just fine, if that helps.
Thank you for the attention.
I would recommend to install latest full factory package from Google.
Then you will start with everything stock, so flash latest TWRP recovery via fastboot (CWM is no longer supported, so error 6 when installing new Lollipop Google Apps appears).
Then in TWRP, do a factory reset, wipe /cache and /system partitions.
Then you can install your Lollipop ROM (over ADB or by pushing ROM package to emulated sdcard).
After this, install latest Full_Auto kernel.
At the end, install Pico Google Apps.
You must install the Pico version, because our /system parition is too small to handle Lollipop with all Google Apps included.
This should work for you, and you will have fully working Lollipop on your Galaxy Nexus
P.S: If you intall the AOSP Lollipop ROM by @freshgiammi and you miss root access, install latest SuperSU flashable zip.
Thank you!
Thank you man!
I've ran into some troubles but managed to do everythings correctly =)
This post can be locked up now.
Thanks again for the reply, LamarrCZ!!
So I rooted my 5X with the help of the Nexus root toolkit. I have successfully flashed Elementalx kernel through TWRP and have tried flashing the ROM and GApps through the toolkit and through TWP but always end up in a bootloop at the Google screen. What am I doing wrong?
I'm just looking to load a Custom ROM to possibly squeeze some extra battery life out of my 5X.
Bootloop
Hi mate,
Did you try and clear cache & dalvic after installing the rom through TWRP.
Also did you install the kernel after the rom & gapps, also try another kernel maybe, or use the stock one with the rom ( if possble ).
or grab the factory image and go back to stock & lock the bootloader.
Also, I did read if you do not use the SDK toolkit from Google ( contains Fastboot and ADB ) , you can have issues like this.
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I will do some reading and see what else I find.
Later
Which ROM are you flashing? Most have a decent installation instruction you should follow precisely.
Basic steps in correct order:
Download ROM and Gapps.
Clear data and caches (always clean install a new ROM).
Flash ROM
Flash Gapps
Flash custom kernel
Root.
Boot (on pre 7.0 first boot may take 10+ minutes)
slysurfer said:
Hi mate,
Did you try and clear cache & dalvic after installing the rom through TWRP.
Also did you install the kernel after the rom & gapps, also try another kernel maybe, or use the stock one with the rom ( if possble ).
or grab the factory image and go back to stock & lock the bootloader.
Also, I did read if you do not use the SDK toolkit from Google ( contains Fastboot and ADB ) , you can have issues like this.
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I will do some reading and see what else I find.
Later
Click to expand...
Click to collapse
I chose options to clear cache and dalvik when using the Nexus root toolkit and then again manually when I tried to flash through TWRP. I don't quite remember which order I tried to install the kernel. I'm assuming from your question the kernel always always has to be flashed after flashing a ROM? (Even if the kernel was previously flashed?)
I'l look into doing it the 'old fashioned' way as it seems it should iron out any issues. Thanks for the help and please reply if you have a chance!
peltus said:
Which ROM are you flashing? Most have a decent installation instruction you should follow precisely.
Basic steps in correct order:
Download ROM and Gapps.
Clear data and caches (always clean install a new ROM).
Flash ROM
Flash Gapps
Flash custom kernel
Root.
Boot (on pre 7.0 first boot may take 10+ minutes)
Click to expand...
Click to collapse
I'm attempting to flash the latest version of Pure Nexus, Gapps, and Elementalx. From what little research I've done it seems like people are able to run this ROM and kernel combination without issues.
I followed these steps to a T and cleared cache/dalvik after every flash. I am on Nougat right now and the phone would get as far as the Google bot logo. The longest I waited was probably 10-15 minutes. Could it possibly take longer on Nougat? Does that have anything to do with encryption?
Thanks all!
Andrew
Angdvl089 said:
I chose options to clear cache and dalvik when using the Nexus root toolkit and then again manually when I tried to flash through TWRP. I don't quite remember which order I tried to install the kernel. I'm assuming from your question the kernel always always has to be flashed after flashing a ROM? (Even if the kernel was previously flashed?)
I'l look into doing it the 'old fashioned' way as it seems it should iron out any issues. Thanks for the help and please reply if you have a chance!
I'm attempting to flash the latest version of Pure Nexus, Gapps, and Elementalx. From what little research I've done it seems like people are able to run this ROM and kernel combination without issues.
I followed these steps to a T and cleared cache/dalvik after every flash. I am on Nougat right now and the phone would get as far as the Google bot logo. The longest I waited was probably 10-15 minutes. Could it possibly take longer on Nougat? Does that have anything to do with encryption?
Thanks all!
Andrew
Click to expand...
Click to collapse
It's unclear to me if you did a clean flash or not.
Check out post #2 in the pure Nexus thread for detailed installation instructions. Follow them to the letter and you should be fine.
I've been running pure Nexus with elementalX for some time now and never had any problems. Are you sure you aren't using the nougat version of elementalX? 3.05 is NOT the correct version for running pure Nexus at this moment as the ROM is still based on 6.01.
peltus said:
It's unclear to me if you did a clean flash or not.
Check out post #2 in the pure Nexus thread for detailed installation instructions. Follow them to the letter and you should be fine.
I've been running pure Nexus with elementalX for some time now and never had any problems. Are you sure you aren't using the nougat version of elementalX? 3.05 is NOT the correct version for running pure Nexus at this moment as the ROM is still based on 6.01.
Click to expand...
Click to collapse
THAT must be the problem! I didn't know it was running on Marshmallow. I'll give that a try now. Thanks for the obvious answer!
Andrew
Angdvl089 said:
THAT must be the problem! I didn't know it was running on Marshmallow. I'll give that a try now. Thanks for the obvious answer!
Andrew
Click to expand...
Click to collapse
So not only did I need the Marshmallow version of ElementalX but I also needed to update my vendor image for the PN ROM. Thanks for the help! All set from here on out.
Andrew
Angdvl089 said:
So not only did I need the Marshmallow version of ElementalX but I also needed to update my vendor image for the PN ROM. Thanks for the help! All set from here on out.
Andrew
Click to expand...
Click to collapse
Glad to be of help. Have fun with your phone!
First of all make sure you're on the correct firmware for whatever rom and kernel your wanting to use or it will not boot. It will bootloop if on say a Marshmallow build amd your trying to install a Nougat rom.. Now if all matches you can proceed.. This is how I've installed roms for 5-6 years: in twrp wipe: data, system, cache, delvik cache, flash rom, flash gapps (open gapps mini is what I use) flash either SuperSu zip or PHH superuser, next reboot. Some roms (example: DU and AICP) come with SU already inside so no need to flash it.. You can tell because in twrp during flash process you'll see SU being installed If rom comes with it. If you choose to use PHH Superuser you'll need his app from Google play store. Just grab it (search PHH Superuser) and open it and you should be good to go. I use SuperSU as I've had issues using other SU with ARISE sound which is also something i use. Hope that's not confusing. Hmu on hangouts if you need help and I'll help when I'm available: [email protected]
Sent from my LG Nexus 5X using XDA Labs
Need any help
Hi mate, i have now unlocked bootloader, installed twrp and installed pure nexus rom. Did not use the toolkit, i used adb and fastboot using commands... It was easy. If you need a hand with anything give us a yell . [quoter=Angdvl089;68875927]So I rooted my 5X with the help of the Nexus root toolkit. I have successfully flashed Elementalx kernel through TWRP and have tried flashing the ROM and GApps through the toolkit and through TWP but always end up in a bootloop at the Google screen. What am I doing wrong?
I'm just looking to load a Custom ROM to possibly squeeze some extra battery life out of my 5X.[/QUOTE]
Hello everyone!
Bought my Oneplus 3 about a month ago and I am generally happy with it. When I bought it, the phone had Oxygen OS 3.2.1 installed on it and as I have heard that 3.2.4 had issues on it, I didn't install it for a while. Then 3.2.6 came out, I decided to give it a try, but as I couldn't find a direct OTA from 3.2.1 to 3.2.6, I firstly sideloaded the incremental update to 3.2.4 and then from 3.2.6. Of course, wiped the cache afterwards.
However, I started experiencing a significant drop in battery life - not that I had to charge my phone 3 times a day or anything, but still really noticeable (For example, with a day of normal usage I would have had 50-60% left, after the 3.2.6 update - probably 20-25%). So I decided that I had to do a clean install of the OS.
Now to the important part, what I did was wipe cache and data, then with ADB sideloaded the full 3.2.6 zip to my phone. The problem is that I still don't think the battery life is quite like what it was in 3.2.1. Onto my question - would you consider what I have done a clean install, if not - could you please give me instructions how can it be done correctly(if possible without unlocking bootloader, installing TWRP, etc as I do not want to tinker with my phone a lot (of course, I have to - I will do it)). Any other suggestions for resolving the battery drain issue are welcome as well.
Thanks in advance!
ivan.panchev said:
Hello everyone!
Bought my Oneplus 3 about a month ago and I am generally happy with it. When I bought it, the phone had Oxygen OS 3.2.1 installed on it and as I have heard that 3.2.4 had issues on it, I didn't install it for a while. Then 3.2.6 came out, I decided to give it a try, but as I couldn't find a direct OTA from 3.2.1 to 3.2.6, I firstly sideloaded the incremental update to 3.2.4 and then from 3.2.6. Of course, wiped the cache afterwards.
However, I started experiencing a significant drop in battery life - not that I had to charge my phone 3 times a day or anything, but still really noticeable (For example, with a day of normal usage I would have had 50-60% left, after the 3.2.6 update - probably 20-25%). So I decided that I had to do a clean install of the OS.
Now to the important part, what I did was wipe cache and data, then with ADB sideloaded the full 3.2.6 zip to my phone. The problem is that I still don't think the battery life is quite like what it was in 3.2.1. Onto my question - would you consider what I have done a clean install, if not - could you please give me instructions how can it be done correctly(if possible without unlocking bootloader, installing TWRP, etc as I do not want to tinker with my phone a lot (of course, I have to - I will do it)). Any other suggestions for resolving the battery drain issue are welcome as well.
Thanks in advance!
Click to expand...
Click to collapse
Personally, i don't think it' s not a clean install, because a clean install need a full wipe of all partitions (internal storage not mandatory)
Without installing TWRP, i think it will be hard to do a really clean flash. But if you change your mind, you will not regret it
First, i suggest you to follow this great guide (and say thanks to his op) : http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733 to unlock, install twrp, backup.
Second, when you are in TWRP, you can wipe your phone (advanced wipe, all partitions except internal storage and usb-otg)
Third, you can install a ROM based on stock OOS or CM13, look in the right section : http://forum.xda-developers.com/oneplus-3/development
Then, you will have a clean system
Lowxorx said:
Personally, i don't think it' s not a clean install, because a clean install need a full wipe of all partitions (internal storage not mandatory)
Without installing TWRP, i think it will be hard to do a really clean flash. But if you change your mind, you will not regret it
First, i suggest you to follow this great guide (and say thanks to his op) : http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733 to unlock, install twrp, backup.
Second, when you are in TWRP, you can wipe your phone (advanced wipe, all partitions except internal storage and usb-otg)
Third, you can install a ROM based on stock OOS or CM13, look in the right section : http://forum.xda-developers.com/oneplus-3/development
Then, you will have a clean system
Click to expand...
Click to collapse
I am willing to install TWRP and do a clean install of the OS, however, I do insist on having the Onplus-provided ROM(if it can be called ROM at all). Is is possible to install it with TWRP? If not, I should probably install TWRP, wipe everything, go back to the stock recovery and install the zip provided from Onplus? Really appreciate your answer!
ivan.panchev said:
I am willing to install TWRP and do a clean install of the OS, however, I do insist on having the Onplus-provided ROM(if it can be called ROM at all). Is is possible to install it with TWRP? If not, I should probably install TWRP, wipe everything, go back to the stock recovery and install the zip provided from Onplus? Really appreciate your answer!
Click to expand...
Click to collapse
You can consider to flash FreedomOS, a stock based rom who allow you to debloat your phone with Aroma Installer. This rom is really close to stock OOS, an much more easy to flash than the stock zip. Follow the op's post here : http://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348
If you really want the full stock rom you can search on the oneplus site, i think you can find the zip file with the stock OOS (but i really recommend you to choose FreedomOS )
Lowxorx said:
You can consider to flash FreedomOS, a stock based rom who allow you to debloat your phone with Aroma Installer. This rom is really close to stock OOS, an much more easy to flash than the stock zip. Follow the op's post here : http://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348
If you really want the full stock rom you can search on the oneplus site, i think you can find the zip file with the stock OOS (but i really recommend you to choose FreedomOS )
Click to expand...
Click to collapse
I believe I have the full zip for the full 3.2.6 version, the question is whether or not I can flash it directly with TWRP. If that's the case, then that's what I am going to do!
ivan.panchev said:
I believe I have the full zip for the full 3.2.6 version, the question is whether or not I can flash it directly with TWRP. If that's the case, then that's what I am going to do!
Click to expand...
Click to collapse
If you have the stock 3.2.6 zip file you can follow theses instructions on the official oneplus site. There are both TWRP and stock recovery guide.
ivan.panchev said:
I believe I have the full zip for the full 3.2.6 version, the question is whether or not I can flash it directly with TWRP. If that's the case, then that's what I am going to do!
Click to expand...
Click to collapse
If you install TWRP, wipe everything, flash the full ROM zip of OOS 3.2.6, it will work. When you unlock your bootloader, a full wipe occurs regardless, so you may just want to do that and see if things improve.
Sent from the OnePlus 3...
making it "RAIN!"
noobtoob said:
If you install TWRP, wipe everything, flash the full ROM zip of OOS 3.2.6, it will work. When you unlock your bootloader, a full wipe occurs regardless, so you may just want to do that and see if things improve.
Sent from the OnePlus 3...
making it "RAIN!"
Click to expand...
Click to collapse
After the second full charge, I think the things are a lot better - I have only used it for 30 minutes screen on today but is still on 82% (with more than 10 hours idle), which a lot like what I used to have when with 3.2.1. Plus, I am in an area with low network coverage, so that's draining the battery as well. Thanks for all of your answers, if I feel the need, will probably flash the whole stock rom with TWRP.
I have a blank App in my app drawer since I flashed my custom ROM and now they're 3 of them. When I tap on the app info it says I need a broader app to view it. I included a screenshot. Anyone know what these are?
Also, my phone keeps randomly rebooting.
@newbrooster89
Looks like apps left from maybe a backup of whatever launcher you were using on your previous setup. Shows the partial icons but not the whole app because they are not installed now. That's what it appears to be. I use nova prime and, I can hold down (long press) an icon and it gives me options and one is playstore and you can select that and it takes you to play store to the app. See if you can long press and maybe select "search" or something that will take you to the app. If not just swipe em off your screen. Its nothing to be worried about. Just something from a past launcher backup/restore.
Edit/added:
Explain how you installed? What rom, what gapps package... What did you wipe in twrp recovery?
I always wipe data and system and cache unless whoever made the rom states not to in their op. (original post) Ex: Lineage 17 The dev says to only wipe data in twrp so that's what I do... otherwise I wipe data, system, cache flash rom, flash twrp installer zip reboot system. Then I boot back into twrp and install gapps and magisk zip for root and reboot system. That's my usual method for installing a rom.
I recommend a factory reset either through your phones settings or fastboot or twrp. See if that stops your reboots ..
NewbRooter89 said:
I have a blank App in my app drawer since I flashed my custom ROM and now they're 3 of them. When I tap on the app info it says I need a broader app to view it. I included a screenshot. Anyone know what these are?
Also, my phone keeps randomly rebooting.
Click to expand...
Click to collapse
if you flashed anything other than lineage you deserve what you are getting
flash713 said:
@newbrooster89
Looks like apps left from maybe a backup of whatever launcher you were using on your previous setup. Shows the partial icons but not the whole app because they are not installed now. That's what it appears to be. I use nova prime and, I can hold down (long press) an icon and it gives me options and one is playstore and you can select that and it takes you to play store to the app. See if you can long press and maybe select "search" or something that will take you to the app. If not just swipe em off your screen. Its nothing to be worried about. Just something from a past launcher backup/restore.
Edit/added:
Explain how you installed? What rom, what gapps package... What did you wipe in twrp recovery?
I always wipe data and system and cache unless whoever made the rom states not to in their op. (original post) Ex: Lineage 17 The dev says to only wipe data in twrp so that's what I do... otherwise I wipe data, system, cache flash rom, flash twrp installer zip reboot system. Then I boot back into twrp and install gapps and magisk zip for root and reboot system. That's my usual method for installing a rom.
I recommend a factory reset either through your phones settings or fastboot or twrp. See if that stops your reboots ..
Click to expand...
Click to collapse
I just ended up deleting everything and flashing a whole new ROM. I was on Lineage 17 but kept having so many bugs that I decided to try a different one. Thanks for the advice though.
sudoxd said:
if you flashed anything other than lineage you deserve what you are getting
Click to expand...
Click to collapse
That's what I was using and I had so many bugs and issues with it.
NewbRooter89 said:
That's what I was using and I had so many bugs and issues with it.
Click to expand...
Click to collapse
Then something was wrong on your end because lineage 17 is very close to being flawless. I've used it several times and always worked great for me.
Flash latest factory image & let it wipe (fastboot -w) at the end don't remove the fastboot -w in the script, if you did. I know many people do that ...
Boot twrp and Wipe data, flash lineage 17 w/gapps
Flash twrp installer (I use 3313) reboot system ...
Boot twrp, flash magisk root zip reboot system.
That's how I've always installed lineage and works great. Sounds like you had something interfering with it. Maybe residue from a past install or something but it was most definitely user error. Reflash factory image and wipe data and install it and it will be close to flawless. If not get logs and post them on lineage thread and someone there can tell you exactly what's going on. 11/30 build is not buggy.
flash713 said:
Then something was wrong on your end because lineage 17 is very close to being flawless. I've used it several times and always worked great for me.
Flash latest factory image & let it wipe (fastboot -w) at the end don't remove the fastboot -w in the script, if you did. I know many people do that ...
Boot twrp and Wipe data, flash lineage 17 w/gapps
Flash twrp installer (I use 3313) reboot system ...
Boot twrp, flash magisk root zip reboot system.
That's how I've always installed lineage and works great. Sounds like you had something interfering with it. Maybe residue from a past install or something but it was most definitely user error. Reflash factory image and wipe data and install it and it will be close to flawless. If not get logs and post them on lineage thread and someone there can tell you exactly what's going on. 11/30 build is not buggy.
Click to expand...
Click to collapse
you dont even need to flash the factory image, will work fine flashing from whatever they have now
sudoxd said:
you dont even need to flash the factory image, will work fine flashing from whatever they have now
Click to expand...
Click to collapse
That's correct you don't have to flash factory image but that's what I would do. There's always more than one way to do something.
flash713 said:
That's correct you don't have to flash factory image but that's what I would do. There's always more than one way to do something.
Click to expand...
Click to collapse
yes but why? just sounds like wasted time to me, our lives are short remember. that time could be spent with friends and family but no here you are flashing factory image before rom
sudoxd said:
yes but why? just sounds like wasted time to me, our lives are short remember. that time could be spent with friends and family but no here you are flashing factory image before rom
Click to expand...
Click to collapse
But I love to flash factory image. Jkjk. ?? The reason I had initially posted that on my comment was because I thought if anything wasn't right on his setup it would square it away or if something was left from another past install on sdcard it would clear it all up. Sure a format data in twrp will do same I just thought of that as an easy thing to say that had a zero % chance of being misunderstood. And what if he was on 9.0? ? That's just how I thought at that moment when I commented that. I know Lineage 17 build for Marlin is damn near flawless. I've been using it off and on since it came out. I see you are the dev who makes that kernel. Saw your link to your work. I remember you from long ago (i used to have another user name but had my account deleted a while back) on some Nexus device everyone and their mom owned. Maybe the 5 or 5x or the Gnex idk but I remember your kernel because it was bad ass.
It probably was something on my end. This is the first phone I've rooted with the A/B slots. I also did it through adb sideload because I was having issues with TWRP. I was also stuck in a bootloop when I installed it. Maybe I'll give it another shot. I did really like having Android 10 and my battery life was much better with lineage.
HI everyone I need your help. i installed Adaway using F-Droid without first installing and activating the systemless hosts modules -- which I thought was optional.
Supposedly, failing to activate "systemless hosts" triggers a warning to do so during install, but not in my case. My Mi Max 3 (Global Edition, Post ARB) is stuck on bootloop to OrangeFox.
Uninstalling Adaway from OrangeFox did not fix the bootloop.
I'd be okay with losing all data and reverting to unrooted stock but I don't know how to revert to unrooted stock in OrangeFox when OrangeFox isn't finding any backup images.
Might manually editing the hosts file perhaps fix this?
Should I go into Wipe and wipe everything? Or simply delete Magisk? Theoretically, should this result in a system reboot back to stock?
If I can't see any img files are they still hidden in the phone somewhere (stock images) to reboot to? Because I moved since I rooted and cannot find the backup drive with my images on them.
My OS is still stock Android and Miui. These are the modules installed in Magisk Version 20.3:
optimizedgpsconf
quickstepswitcher
riru-core
riru-edxposed
terminal_debloater
Please, any suggestions -- I am sorry for being so clueless despite being in this forum for five years but although I am good at following instructions this stuff remains basically "magic" to me.
Best wishes!
Anybody ever lose all recovery, including stock, after flashing?
Hi again, I'm the one that bootlooped following adaway install. Stopped mucking around, wiped my data and used Orangefox to flash the OTA, which fixed the bootloop but the phone was encrypted (I really did wipe everything and check all the right boxes in the Miui menu). No big deal. I booted back into Orange Fox and did another data wipe and was able to boot to system.
Unfortunately, not only did I lose root, I lost recovery -- no TWRP, no OrangeFox, no stock recovery. I can only boot into the system.
And yet oddly, I can still browse the root files using a root browser and some play apps for root users still detect Magisk. (but Magisk Mgr isn't one of them).
I'm guessing the wise thing to do at this point is to use ADB and start over from scratch, reinstalling TWRP, Orangefox, Magisk and the rom?
Again, if anyone has encountered this error or has any inkling of a quicker way to fix it, please jump in. Thanks!
I