I have an HTC One M9 (Sprint) software version 2.11.651.19 (OPJA2) with Android v5.1
Within the last couple months I unlocked the devices bootloader, and rooted it. Last night I left the phone under my laptop and I'm thinking it got way way way too hot, somehow the thing is still alive, however when I went to turn it on in the morning, I had no wifi or cellular capabilities. At first I assumed this was a hardware issue, however I then unrooted the device on a whim, and this fixed it (Until I turned it off again, to my dismay).
I'm thinking somehow my phone overheated (Which explains why my battery life won't go over 47%) and somehow my flash memory must have been corrupted because I can no longer boot into recovery mode, which is my serious catch 22. Since I figure this is some issue related to my firmware, which I would LIKE to reflash (This is my goal here). To my dismay, in order to flash a stock RUU or firmware to the device, you must have your bootloader relocked. However in order to relock your bootloader you must have root, and like an idiot I unrooted it. I can't reinstall SuperSU through my TWRP recovery because my phone refuses to boot into recovery mode. I attempted to re-flash TWRP to the device through download mode, the flashing is completed successfully, however I still cannot boot into my recovery. To break it down simply:
-Want to reflash stock firmware
-Must have root to reflash stock firmware/RUU
-Don't have root because I uninstalled it
-Can't re-root because my recovery is corrupted
-Can't re-flash TWRP (Already tried and it's not working)
-Can't re-root because I can't flash TWRP
-Can't reflash stock firmware because I can't disable it with root
Regardless of this I attempted to use adb and echo to relock the bootloader however instead of getting # I get $, so I'm not really able to do this either. Is there ANY way I can repair my recovery, has anyone ever run into an issue like this before? Or am I just completely screwed, hahaha.
Do you think I might be able to reflash Android V5.1 to try and fix the corruption and then maybe that would allow me to get into recovery mode so I can flash Super SU so I can at least factory reset my device with TWRP, or possible reload stock firmware and factory reset from there?
Thanks guys for any help you can provide.
*EDIT
If anyone wants to provide any advice great, but for now I'm going to try using HTC Sync Manager to load Marshmallow (v6.0) onto the HTC and see if this may allow me to actually get into recovery mode. Downloading the file from here: *nevermind can't post links yet, under 10 posts, you can find it on HTC's website* (This is for the HTC One M9, Sprint) in case anyone else EVER has to run into this awful issue, lol.
Moderators please feel free to update the thread to SOLVED status, I was able to update my phone to marshmallow to resolve the issue. This time around I WILL be backing up my phone, probably not going to root it this time around either, I have like 3 other phones so I'll just root them instead, lol. If you would like the download link I am happy to provide it VIA PM so you can update my OP with the link for the full fix. My phone is able to get wifi and texts now without an issue, unfortunately all my data is wiped but honestly I don't really care!!
Thanks everyone!
Good job on solving your issue.
If you have further questions or want to help out others, you can do so here
http://forum.xda-developers.com/sprint-one-m9/help
http://forum.xda-developers.com/sprint-one-m9
Thread closed
So, I rooted my S7. It worked fine. One day, randomly out of no where it bootlooped (Google play services crashed. I restarted phone and it bootlooped. )
I have not made a single system modification other then rooting it. Didn't mod anything or mess with system files, and I had barely even been using the phone when it happened.
So I unrooted it (The phone still gave me the "Custom" symbol though) and Just now-- It randomly restarted. I didn't restart it. it just did it by itself. And it came into a bootloop. I don't understand why. What can I do to fix this?
MORE SPECIFICALLY: By Bootloop, I mean it stays on the T-Mobile screen and vibrates every minute or so and does not do anything (I even left it alone for ~ 30minutes and it never got past this screen)
Factory resetting the phone fix's it, but I don't want to factory reset my $400 phone every week! I don't understand how I could fix this either.
What method did you use to unroot? Did you flash stock firmware with odin?
sparky2029 said:
What method did you use to unroot? Did you flash stock firmware with odin?
Click to expand...
Click to collapse
All I did pretty much was flash stock s7 firmware. (More specifically boot.img)
Originally couldn't find a stock s7 image then I just used one I already had and it worked fine
EDIT: Flashed the entirety of G930TUVU4APK1 firmware, (Rom and all) Hopefully this will fix my issue and stop it from happening but if Anyone has any ideas or suggestions, I'm all open
Andrew S.S. said:
EDIT: Flashed the entirety of G930TUVU4APK1 firmware, (Rom and all) Hopefully this will fix my issue and stop it from happening but if Anyone has any ideas or suggestions, I'm all open
Click to expand...
Click to collapse
Just now noticed wat your problem is sorry for being late so yes to fix the bootloop refladh stock firm and when you go through all the root steps install xposed (yes it's possible it's insane on how they got it to work but it's possible I've done with my self)after getting xposed installed through flash fire go to xposed and get xtouchwiz something it's a blue gear install that And it will set your system status as official
---------- Post added at 02:22 PM ---------- Previous post was at 02:18 PM ----------
Andrew S.S. said:
EDIT: Flashed the entirety of G930TUVU4APK1 firmware, (Rom and all) Hopefully this will fix my issue and stop it from happening but if Anyone has any ideas or suggestions, I'm all open
Click to expand...
Click to collapse
Here's a quick explanations of wat i think it is it's becuz you've ether heavenly been modding the phone or if your phone status is custom then that's the problem I had with mine after asking around someone gave me the fix i put it in the other comment hope this fixes your issue it worked for me 2 months of no bootloop I switched to 7.0 vzw beta so I lost root
Alright, This is just because I am trying to take precautions so that way I do not end up with a brick.
Currently I am rocking 5.1 PAC-MAN and things are going well. But LineageOS for MM for 6045 came already and I want to use that as my daily driver.
Here is where I run into a problem. For those of you that know I only have LP radios and modems on my system. Main problem I am having and is keeping me from flashing is the lack of a MM radio and or modem. Is there anyone that is on 6045O that had tried this out without having that lockscreen problem?
If you don't flash the MM radios, you will end up with lock screen issues, unfortunately.
-EDIT-
So apparently I can't read. I have the 6045O and this link has the correct modem files to fix the lock screen issues.
https://mega.nz/#F!u0UBAICD!DzKYnswfK5J6dw5WQNgEDg
6.0.1 modem is the file you need.
magus7091 said:
If you don't flash the MM radios, you will end up with lock screen issues, unfortunately.
-EDIT-
So apparently I can't read. I have the 6045O and this link has the correct modem files to fix the lock screen issues.
https://mega.nz/#F!u0UBAICD!DzKYnswfK5J6dw5WQNgEDg
6.0.1 modem is the file you need.
Click to expand...
Click to collapse
Attempted. Everything but the pin issue is good. Weird how it trips badly with the PIN. Installing SuperSU as we speak.
EDIT: Looped after SuperSU flash..
EDIT2: Going back to 5.1. Thank you very much for the support.
Huskied said:
Attempted. Everything but the pin issue is good. Weird how it trips badly with the PIN. Installing SuperSU as we speak.
EDIT: Looped after SuperSU flash..
EDIT2: Going back to 5.1. Thank you very much for the support.
Click to expand...
Click to collapse
While playing around with ROMs for the phone I had some odd issues here and there. As far as the SuperSU flash, it almost always loops a couple times during the reboot process, but I've switched to the lineageOS official su addon because I like native support and root management. Also it never did those initial boot loops. When I did have an issue (just recently, in fact) I ran a wipe of the system partition, then installed the rom, and ran the repair file system option in TWRP, and since then it's been smooth as butter. If you're interested in giving it another go, just let me know and I should be able to link you the files, as they're on my google drive.
magus7091 said:
While playing around with ROMs for the phone I had some odd issues here and there. As far as the SuperSU flash, it almost always loops a couple times during the reboot process, but I've switched to the lineageOS official su addon because I like native support and root management. Also it never did those initial boot loops. When I did have an issue (just recently, in fact) I ran a wipe of the system partition, then installed the rom, and ran the repair file system option in TWRP, and since then it's been smooth as butter. If you're interested in giving it another go, just let me know and I should be able to link you the files, as they're on my google drive.
Click to expand...
Click to collapse
May I ask one more thing? Have you ever gotten the PIN lock or password or pattern lock to work?
EDIT: Nvm. Using Hi-Locker for now. All is good.
I use a pattern lock on mine, and after flashing the modem files, the lock screen functions as it should with all methods. Consider re-flashing the modem and ROM if you get to where you want to play with it, full wipe prior, no dirty flash.
I have the Google Fi Android One X4 XT1900-1, and I made the mistake of trying out Lineage OS, which was great on my last couple phones but a bit underwhelming here. So I wanted to go back to stock. I tried following the threads here and here (just the return-to-stock part, not the Pie update), using the Linux shell script. And everything worked great! EXCEPT! Neither the WiFi nor the SIM card are working. I tried using the firmware from Motorola-Firmware-Team on Android File Host that were marked as Fi, both the most recent and a few versions back. And everything works except the modems.
Any suggestions? I don't really want to be stuck with this meh version of Lineage.
https://mirrors.lolinet.com/firmware/moto/payton/official/FI/
Flash the latest release (XT1900-1_PAYTON_FI_9.0_PPW29.69-39-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip) with your shell script, I guess you flashed stock oreo instead of pie and going back to oreo with pie modem is not a good idea
First, I didn't realize there was a Q&A-specific subforum, admin please feel free to move this thread there!
I gave it a try with the version of the firmware you suggested (I thought since it'd shipped with Oreo and gotten Pie OTA the Oreo one might be better, that's why I was trying that first), but still no luck even with the latest Pie. Maybe there's a problem with the version of the flash-all.sh I'm using? Here's the contents of it, leaving out the AOSP license text:
Code:
#!/bin/sh
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
sleep 9
fastboot --set-active=a
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_b system_other.img
fastboot flash oem_a oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot reboot
Maybe there's something missing, or something I should take out?
It wouldn't help. I have the same issue. I did try reflash with different Roms, Android,firmware.. Everything looks the same. no cellular service, WiFi at all. Imei/WiFi mac address broken.
Next what I want to do to write correct Imei separately..
trixter42 said:
First, I didn't realize there was a Q&A-specific subforum, admin please feel free to move this thread there!
I gave it a try with the version of the firmware you suggested (I thought since it'd shipped with Oreo and gotten Pie OTA the Oreo one might be better, that's why I was trying that first), but still no luck even with the latest Pie. Maybe there's a problem with the version of the flash-all.sh I'm using? Here's the contents of it, leaving out the AOSP license text:
Maybe there's something missing, or something I should take out?
Click to expand...
Click to collapse
ElijahUSA said:
It wouldn't help. I have the same issue. I did try reflash with different Roms, Android,firmware.. Everything looks the same. no cellular service, WiFi at all. Imei/WiFi mac address broken.
Next what I want to do to write correct Imei separately..
Click to expand...
Click to collapse
I imagine you guys did NOT backup your EFS partition in twrp?
I've personally been lucky and never have killed this partition but it's been my understanding that immediately after you install twrp on any device you should backup this partition before installing roms/firmware..
I go the extra yard and save the backup to my PC...
I'd try googling around terms like efs corruption / restore
SyberHexen said:
I imagine you guys did NOT backup your EFS partition in twrp?
I've personally been lucky and never have killed this partition but it's been my understanding that immediately after you install twrp on any device you should backup this partition before installing roms/firmware..
I go the extra yard and save the backup to my PC...
I'd try googling around terms like efs corruption / restore
Click to expand...
Click to collapse
I can look into that, but would Lineage OS still work just fine if that was the case? Because Lineage OS works just fine except for a couple missing features. The modem works on that, no problem. I'd just prefer to use the stock firmware, and that's where I run into problems.
Sorry, my last three phones were a Nexus 4, a Nexus 5, and a Nextbit Robin, so I'm not used to a phone being this difficult to work with.
trixter42 said:
I can look into that, but would Lineage OS still work just fine if that was the case? Because Lineage OS works just fine except for a couple missing features. The modem works on that, no problem. I'd just prefer to use the stock firmware, and that's where I run into problems.
Sorry, my last three phones were a Nexus 4, a Nexus 5, and a Nextbit Robin, so I'm not used to a phone being this difficult to work with.
Click to expand...
Click to collapse
That is strange that it's working in roms.
Did you format userdata before going back to stock?
This was recommended when going to custom ROMs.
Might be relavent in reverse.
Another idea is try one of my firmware only zips.
You can find it in the havoc os thread,
first post near the install instructions
SyberHexen said:
That is strange that it's working in roms.
Did you format userdata before going back to stock?
This was recommended when going to custom ROMs.
Might be relavent in reverse.
Another idea is try one of my firmware only zips.
You can find it in the havoc os thread,
first post near the install instructions
Click to expand...
Click to collapse
Still having trouble...
I did format everything in TWRP before flashing it. I've tried this a bunch of times, in a bunch of different variations, but I've made sure not to carry Lineage data over into the stock ROM.
I tried flashing the Pie Fi stock from lolinet and then flashing your Pie Fi firmware, but then it just bootlooped. I tried it with the retail firmware too, just in case it was some weird rebranded old stock thing, but the same thing happened. It was a good thing to try, though!
Ultimately, the stock ROM just isn't reading my IMEI for some reason, even though Lineage sees it just fine. I do have my IMEI, is there a way to enter it into the stock ROM manually? I've also been playing around with the official Moto tools over in Windows, but no luck there either.
I really appreciate all the suggestions though!
I'm hitting the exact same problem. I have a Google Fi variant, went to Lineage to try it out, tried to revert to stock, and wireless and radio are not working. I followed the guide at https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265, but accidentally skipped the step to install "Copy Partitions Zip". I've been trying to figure out what that file does, but haven't made much progress. I don't know if it's related or not to stock not working.
I lost all data/wifi/cell service after doing a clean flash of the April update. During the setup phase of the initial flash, I had no 4G, device was failing to acknowledge that I even had a SIM card inserted. Wifi was so intermittent that I couldn't enter my password to restore my Google account to the device. After this I tried out numerous stock flashes of the earlier Pie factory firmwares, LineageOS, HavocOS, none of them having any success..
After getting in a bootloop trying to restore the full backup I made right after unlocking my bootloader, I decided to again do a factory firmware flash of the April update and only restore the backups I made of the EFS and Persist partitions, at the initial boot, that didn't seem to work. I decided to go ahead and proceeded with my normal routine of flashing TWRP and the latest Magisk. Thought maybe a Magisk module could kickstart service. Booting after that, I finally had both Wifi and 4G LTE w/ voLTE on Total Wireless again.
Definitely a pain, especially the full backup I had made turning out to be a waste of time.
Just backup your EFS/Persist partitions. Lenovorola's gross mishandling of the EFS partition on nearly every recent device makes this step nearly vital before doing anything to the phone.
Is there any progress towards a solution on this? I experienced this for the first time while trying to re-flash stock April ROM.
Can the same EFS and Persist partitions interchangeable, as in can I use yours? I've been using the re-flash stock, accept OTAs, re-root/twrp method for months now and this is the first time this has happened. Its only bluetooth capable right now. lol
Ok, after more hours... I re-flashed the base 9.0 stock rom (PAYTON_FI_9.0_PPW29.69-26), then re-flash up to current (PAYTON_FI_PPWS29.69-39-2-1_May2019). SIM/WiFi services have returned. I might need to update the FAQs thread with this knowledge but honestly not sure what was the main solution to the troubles.
hxxps://mirrors.lolinet.com/firmware/moto/payton/official/FI/XT1900-1_PAYTON_FI_9.0_PPWS29.69-39-2-3_subsidy-DEFAULT_regulatory-DEFAULT_NO_ERASE_MODEM_CFC.xml.zip
The latest July 1 2019 Security patch is available for download. I wonder if the "NO_ERASE_MODEM" in the name is to signify that this update is able to be installed by everyone without the possibility of the update screwing up the phone if installed? Pretty pathetic that we have to deal with an issue like this, even when taking careful measures to not destroy our phones, Google/Lenovorola allow an official update release with that exact capability regardless of whether the user has modified their handset.
Neffy27 said:
Ok, after more hours... I re-flashed the base 9.0 stock rom (PAYTON_FI_9.0_PPW29.69-26), then re-flash up to current (PAYTON_FI_PPWS29.69-39-2-1_May2019). SIM/WiFi services have returned. I might need to update the FAQs thread with this knowledge but honestly not sure what was the main solution to the troubles.
Click to expand...
Click to collapse
That's what perplexes me. It seemed completely random both the loss of and reintroduction of network services to those that it affected. In my case rooting with Magisk restored services, which for all intents and purposes is a terrible answer to give the common user. With that said, in some cases simply installing an official update on an unmodified bootloader locked phone could destroy network services for a select few very unlucky people.
But some good news, I have been running with the latest update applied. I flashed the May 1 update, and let it update to the July 1 update then factory reset the device, installed Magisk/TWRP and have been getting excellent performance, still no ZRAM crashing issues as with the April 1 (I think) update, and close to 5 hours of SOT with ~70% brightness, Bluetooth, Mobile Radio and nothing disabled sync-wise (Gmail/Hangouts/Facebook/Google News/Weather etc.).
Even with spotty support, this is easily the best handset I have ever used. It may be the best after my weekend lake excursion where it was submerged in my pocket for about 45 total minutes over the span of 4 hours with a couple of quick rinses in the sink to scare my family, none of which have IP certified phones.
NeoandGeo said:
hxxps://mirrors.lolinet.com/firmware/moto/payton/official/FI/XT1900-1_PAYTON_FI_9.0_PPWS29.69-39-2-3_subsidy-DEFAULT_regulatory-DEFAULT_NO_ERASE_MODEM_CFC.xml.zip
The latest July 1 2019 Security patch is available for download. I wonder if the "NO_ERASE_MODEM" in the name is to signify that this update is able to be installed by everyone without the possibility of the update screwing up the phone if installed? Pretty pathetic that we have to deal with an issue like this, even when taking careful measures to not destroy our phones, Google/Lenovorola allow an official update release with that exact capability regardless of whether the user has modified their handset.
That's what perplexes me. It seemed completely random both the loss of and reintroduction of network services to those that it affected. In my case rooting with Magisk restored services, which for all intents and purposes is a terrible answer to give the common user. With that said, in some cases simply installing an official update on an unmodified bootloader locked phone could destroy network services for a select few very unlucky people.
But some good news, I have been running with the latest update applied. I flashed the May 1 update, and let it update to the July 1 update then factory reset the device, installed Magisk/TWRP and have been getting excellent performance, still no ZRAM crashing issues as with the April 1 (I think) update, and close to 5 hours of SOT with ~70% brightness, Bluetooth, Mobile Radio and nothing disabled sync-wise (Gmail/Hangouts/Facebook/Google News/Weather etc.).
Even with spotty support, this is easily the best handset I have ever used. It may be the best after my weekend lake excursion where it was submerged in my pocket for about 45 total minutes over the span of 4 hours with a couple of quick rinses in the sink to scare my family, none of which have IP certified phones.
Click to expand...
Click to collapse
Any chance you can run me through the order in which I can get my service/Wi-Fi back? Or how to correctly root via TRWP/Majisk? Lol. I tried rooting last week... And managed to miss something.. not sure. But after doing it, the phone wouldn't boot. Kept restarting. So I said he'll with it and found the stock rom and flashed it back. Works fine except it doesn't recognize sim or Wi-Fi. So temporarily, I'm using, what I believe to be the most ridiculously slow "newer phone" ever made... At&t Axia. I'm dead without my x4. Could really use some insight
JustDJ_From_Da_Swamp said:
Any chance you can run me through the order in which I can get my service/Wi-Fi back? Or how to correctly root via TRWP/Majisk? Lol. I tried rooting last week... And managed to miss something.. not sure. But after doing it, the phone wouldn't boot. Kept restarting. So I said he'll with it and found the stock rom and flashed it back. Works fine except it doesn't recognize sim or Wi-Fi. So temporarily, I'm using, what I believe to be the most ridiculously slow "newer phone" ever made... At&t Axia. I'm dead without my x4. Could really use some insight
Click to expand...
Click to collapse
Do you have bootloader unlocked? If yes, just flash latest fastboot ROM (29.69-39-2-3 for XT1900-1), boot to TWRP "fastboot boot twrp.img" and flash latest Magisk. SIM/WiFi will be back.
Comby_sk said:
Do you have bootloader unlocked? If yes, just flash latest fastboot ROM (29.69-39-2-3 for XT1900-1), boot to TWRP "fastboot boot twrp.img" and flash latest Magisk. SIM/WiFi will be back.
Click to expand...
Click to collapse
Awesome, I'll try it now. I greatly appreciate that
---------- Post added at 02:16 PM ---------- Previous post was at 01:39 PM ----------
Hey.. umm.. where can I find that new ROM?.. lol I know, it's a shame
I managed to pull it off. Reflashed the stock ROM you suggested, then TWRP/Magisk. She's rooted and running..WITH CELL SERVICE! ?...now I'm seeing how I can mess it up again. I'm pretty green at all this, but I've always been intrigued. I was thinking about Lineage OS 16...but seems to have some issues that are above my intelligence. So I guess I need to take my old @$$ to bed before I mess up a good phone..again. Can't thank ya enough for the help
JustDJ_From_Da_Swamp said:
I managed to pull it off. Reflashed the stock ROM you suggested, then TWRP/Magisk. She's rooted and running..WITH CELL SERVICE! ...now I'm seeing how I can mess it up again. I'm pretty green at all this, but I've always been intrigued. I was thinking about Lineage OS 16...but seems to have some issues that are above my intelligence. So I guess I need to take my old @$$ to bed before I mess up a good phone..again. Can't thank ya enough for the help
Click to expand...
Click to collapse
Glad you got your problem sorted out. Honestly the best ROM for this device has always been Plain Stock w/ Magisk for root. Everything just seems to work without issues, all of the custom ROMs have the odd issue here and there that really prevents the device from being able to be run trouble free.
same problem on 1900-7 version
why is no one discussing stable android 11 for op7p ? got my update round 3 a.m. this morning. been searching all day for a working twrp since the stable android 11 been released. no luck though......
Hi,
Today I installed the update manually and my phone keeps flashing the TWRP load-screen at boot. It's stuck now. Is that because there is no compatible TWRP version yet? How do I fix this?? Any idea?
There is no working TWRP yet for Android 11. You'll need to flash the stock boot.img or rooted boot.img from one of the threads in the news, guides section.
Edit: TWRP screen flashing is because it's incompatible. I had the same issue on the open betas.
Have the exact same issue as above, Twrp screen flashing, cannot boot back to normal even with adb... anybody has a rooted boot.img link that knows works with Android 11?
Should have checked on xda first *slaps his face*
Always check xda first *slaps his face again*
EDIT: For other poor saps with this issue use this -> https://www.androidfilehost.com/?fid=2188818919693770594 I didnt managed to get booted with rooted img but the original boot img file worked well ... at least I got a phone now...
im on 10.3.8 and rooted..
can i just do the same old process.. twrp isnt an issue as long as may apps are safe and root..
santiagoruel13 said:
im on 10.3.8 and rooted..
can i just do the same old process.. twrp isnt an issue as long as may apps are safe and root..
Click to expand...
Click to collapse
No, its not the same process.... For me for example I couldnt get wifi to actually work on rooted image AND you lose the ability to do backups via TWRP..... Refer here for the latest on this: https://forum.xda-developers.com/t/...p-recovery-for-oneplus-7-pro.3931322/page-153
dejjem said:
No, its not the same process.... For me for example I couldnt get wifi to actually work on rooted image AND you lose the ability to do backups via TWRP..... Refer here for the latest on this: https://forum.xda-developers.com/t/...p-recovery-for-oneplus-7-pro.3931322/page-153
Click to expand...
Click to collapse
I mean.. same steps.. that ive used so far amd retain its root.
1. Download rom via o2 updater
2. Flash it via local update
3. Install magisk to inactive slot
4. Reboot.
So if i do this.. wifi wont work??? Is that it???
Finished updating my phone..after downloading it for about 2 hours.
And im quite satisfied with the results. No problems whatsoever..
Glad for you... You probably had already removed the encryption on your mobile... from what I'm reading that is the main incompatibility issue with TWRP...
FWIW after playing around for a day, I had to revert everything Phone wifi was weird (weirder with root and all mods disabled) and system was a little unstable in some 3p apps and there seems to be some bugs with the phone screen 60/90 refresh... Gonna wait a bit to update again.
dejjem said:
Glad for you... You probably had already removed the encryption on your mobile... from what I'm reading that is the main incompatibility issue with TWRP...
FWIW after playing around for a day, I had to revert everything Phone wifi was weird (weirder with root and all mods disabled) and system was a little unstable in some 3p apps and there seems to be some bugs with the phone screen 60/90 refresh... Gonna wait a bit to update again.
Click to expand...
Click to collapse
i dont mind not having TWRP for the meantime,, i just used TWRP previously for flashing CUSTOM kernels.. hehehehe.
anyways, what problem have you encountered regarding wifi?? i dont seem to experience those,, maybe because i came from stable oos 10.3.8..
what app crashed and problems have you encountered???