Hey guys hope you can help with my oneplus 7 pro. So I did not backup before rooting the device, however, I was able to successfully root it. The problem arose when I wanted to take the twrp official 3.3.1-2 and upgraded to 3.3.1-29 version. I flashed it on the system image in the twrp setting, but it ended up writing over OS. Now there is no OS on the oneplus 7 pro. Do you guys have a suggestion into how I can fix this problem? and bring it back into the rooted phone. I also was hoping if you guys know anyway to lock the twrp with a password in the future? thank you
1] Your TWRP should already have had a pin if you had set a pin (same one) when using the rom
2] Can you still boot into TWRP as recovery? If so then go grab the latest 9.5.7 :
Official : https://otafsg1.h2os.com/patch/amaz...ygen_21.E.11_OTA_011_all_1906040003_25c96.zip
My mirror on AFH : https://www.androidfilehost.com/?fid=6006931924117889610
You should be able to flash it using TWRP if you've not messed up too badly, then you may be back to default rom and can start again.
If you get that far then read the guide on the @mauronofrio TWRP properly and flash everything again. I've also uploaded a rooted 9.5.7 boot image here if you want to try that way instead :
https://forum.xda-developers.com/showpost.php?p=79678478&postcount=522
If the worst comes to the worst then you may be able to boot into fastboot then run :
fastboot boot twrp-3.3.1-29-guacamole.img
Boot into TWRP and try sideloading the whole 9.5.7 rom instead
18os13 said:
Hey guys hope you can help with my oneplus 7 pro. So I did not backup before rooting the device, however, I was able to successfully root it. The problem arose when I wanted to take the twrp official 3.3.1-2 and upgraded to 3.3.1-29 version. I flashed it on the system image in the twrp setting, but it ended up writing over OS. Now there is no OS on the oneplus 7 pro. Do you guys have a suggestion into how I can fix this problem? and bring it back into the rooted phone. I also was hoping if you guys know anyway to lock the twrp with a password in the future? thank you
Click to expand...
Click to collapse
You could always download one of the fastboot ROMs and flash them again. You're obviously unlocked etc so all you'd need to do is fastboot flash system system.img. just make sure it's the same version.
ok since the update I was able to get the twrp installed again, but choose a wrong option in the reboot menu, something to do with edl, now the phone turn on at all :/
I give up, apparently people just can't follow instructions.
djsubterrain said:
I give up, apparently people just can't follow instructions.
Click to expand...
Click to collapse
it was slightly before I read this post :/. Is there anything possible now or am i screwed?
18os13 said:
it was slightly before I read this post :/. Is there anything possible now or am i screwed?
Click to expand...
Click to collapse
honestly I have no idea what I just did, but everything just came back online again
18os13 said:
it was slightly before I read this post :/. Is there anything possible now or am i screwed?
Click to expand...
Click to collapse
MSM tool, guac recovery.
theres a thread in this section. It will wipe the phone.
18os13 said:
honestly I have no idea what I just did, but everything just came back online again
Click to expand...
Click to collapse
Be vewy vewy careful...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
just get out of EDL, either hold down the power button or hold - and Power for like 10 seconds until u boot out of it
Ok so I basically pressed the volume and down buttom with the power button, then the phone recovered back to the when I first got it and it got uprooted. Anyway, the whole reason I was wanted to root the phone was so that I can lock the TWRP with a password. This would only give me access to hard resetting the phone. Do any of you guys have a solution to this? its a phone for my little brother, and I want to restrict his access to the internet, but he knows how to hard reset the phone using the volume down and power. however, if I can lock the TWRP with a password he cant get around that part as easily.
18os13 said:
Ok so I basically pressed the volume and down buttom with the power button, then the phone recovered back to the when I first got it and it got uprooted. Anyway, the whole reason I was wanted to root the phone was so that I can lock the TWRP with a password. This would only give me access to hard resetting the phone. Do any of you guys have a solution to this? its a phone for my little brother, and I want to restrict his access to the internet, but he knows how to hard reset the phone using the volume down and power. however, if I can lock the TWRP with a password he cant get around that part as easily.
Click to expand...
Click to collapse
You might be able to do that with a guest account but you can't lockout TWRP with a password, it will use the pin applied to the phone. If you set it up as the default user with a pin then that's the pin that will be applied to TWRP so I would look at setting him up as a guest instead which should keep him out of TWRP too.
djsubterrain said:
You might be able to do that with a guest account but you can't lockout TWRP with a password, it will use the pin applied to the phone. If you set it up as the default user with a pin then that's the pin that will be applied to TWRP so I would look at setting him up as a guest instead which should keep him out of TWRP too.
Click to expand...
Click to collapse
perfect, thanks for the help
Related
Hello , does anyone know how to get into AP fast boot with an encrypted phone? Or if its even possible to use
The latest 4.4 fast boot files to do a full wipe and restore to stock on encrypted phone?
Sent from my XT1080 using Tapatalk
Im assuming by encrypted you mean locked bootloader. If so. Use command abd reboot bootloader in the cmd prompt provided you have sdk installed
Maxx'd out Kit Kat
Encrypted phone. My boot loader is locked as well I don't have a Dev version.
Sent from my XT1080 using Tapatalk
Bump..
Does anybody know what I'm referring to? I can't seem to get into AP fast boot... But my main question would be ...does anybody know method to reverse (any method at all) to get back to stock even though I encrypted my phone via settings---- security- "encrypt my phone" ?
Sent from my XT1080 using Tapatalk
mikeymax said:
Bump..
Does anybody know what I'm referring to? I can't seem to get into AP fast boot... But my main question would be ...does anybody know method to reverse (any method at all) to get back to stock even though I encrypted my phone via settings---- security- "encrypt my phone" ?
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
You need way more details here. Its like trying to solve a 50 piece puzzle with only 3.
Maxx'd out Kit Kat
Hmmmm apologies, i honestly am not clear on what details. I have a locked standard droid maxx.. On kit Kat not rooted...I went to settings security and ran the process of encrypting my phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
. With that said , there is an added layer during startup you add a PW to unlock your phone And then it boots up... Basically my question is general around restoring to a fresh stock phone ..is there a method I can try ? I
Sent from my XT1080 using Tapatalk
Yes. Refer to my guide linked below HOWEVER ignore everything but the section about using RSD lite to FXZ flash the phone. Also substitute the 4.2.2 fxz file for the 4.4 file found at the same site that is linked for the 4.2.2 file.
http://forum.xda-developers.com/showthread.php?t=2616104
Maxx'd out Kit Kat
mikeymax said:
Does anybody know what I'm referring to? I can't seem to get into AP fast boot... But my main question would be ...does anybody know method to reverse (any method at all) to get back to stock even though I encrypted my phone via settings---- security- "encrypt my phone" ?
Click to expand...
Click to collapse
Yes, I do know what you mean. I also encrypted my phone. When an encrypted phone is restarted, it first prompts for a passhrase/PIN code that's used to unlock the encryption key for storage.
I haven't restarted my phone since encrypting it (besides that first restart) and I am trying to see how long it will go without being restarted. I know - I'm weird - but I'm not wild about trying to figure out how to enter fastboot at the moment.
However, I saw a thread at android central where a guy factory reset his encrypted phone from recovery and was trying to get rid of the encryption prompt, and was able to do so from fastboot, so I think he'd know exactly what you have to do. The thread is here: http://forums.androidcentral.com/mo...ctory-reset-after-encrypting.html#post3396255
I'd PM drwtsn32 there - I'll bet he can help.
mikeymax said:
Hello , does anyone know how to get into AP fast boot with an encrypted phone? Or if its even possible to use
The latest 4.4 fast boot files to do a full wipe and restore to stock on encrypted phone?
Click to expand...
Click to collapse
I finally restarted my encrypted phone. I was able to get into fastboot just like everybody else - hold volume down and power together from a powered down phone for at least 5 seconds, then release power while continuing to hold volume down - that starts Fastboot.
Hi everyone !
Here I am in a really bad situation...
I bought a second hand phone with a rom issu and the guy who had it told me he ahd no time to waste trying to make it work again, I decided to buy it thinking that nothing could resist a factory reset via ADB.
But, and if I'm here today, it's because I'm in a such a situation, I need some help, and hope you guys can find a solution or at least some leads.
when I got it:
- model 16 GB D821
- The battery was not correctly attached in the phone (i did open it and put it back how it should be and seems to work)
- it is root, bootloader unlock, with Teamwin recovery version 2.6.3.2
- bootloader version HHZ11D
I can launch the teamwin recovery, it's asking for a password when it's starts, i don't know whay BUT I did a data format seeing that some people had some problem with it and did that to fix it
In Teamwin I got 0mb of storage and no OS installed, again it could be fixable via ADB
Now the best !
I can't flash anything on the phone. I can connect to it, it's well detected, I can control it (via ADB or Fastboot) and I can even had a temporary recovery with the nexus toolkit. but:
-Impossible to flash the bootloader, I do everything right, there is not "error" but at the end nothing changes, I'm back with the HHZ11D version and not the latest on I'm trying to get the HHZ11Z.
-Impossible to flash the recovery, same as the bootloader, version teamwin 2.6.3.2.
-impossible to flash a rom, and I don't have one anyway....
Here we are, I think I tried everything, but any clue would be appreciated. I hope I can fix this...
Thanks for your help.
And finally a picture of my fastboot -w when I do one, does it seem normal to you ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try in fastboot, fastboot oem lock. Then reboot and see if the bootloader is locked. I'm guessing it isn't and your emmc is bad.
Sent from my Nexus 5
nothing will stick, emmc fried.
samersh72 said:
nothing will stick, emmc fried.
Click to expand...
Click to collapse
Is there anything I can do ? Seems not...
Can I change it ?
RealMyop said:
Is there anything I can do ? Seems not...
Can I change it ?
Click to expand...
Click to collapse
No, you're hosed. Rma would be the option but not in your case. You're not going to be able to flash anything.
Sent from my Nexus 5
RealMyop said:
Is there anything I can do ? Seems not...
Can I change it ?
Click to expand...
Click to collapse
Did bootloader get locked?
GUGUITOMTG4 said:
Did bootloader get locked?
Click to expand...
Click to collapse
Yes I can lock back the bootloader.
RealMyop said:
Yes I can lock back the bootloader.
Click to expand...
Click to collapse
If you can lock it, unlock it again then fastboot flash the cache.img from the factory image
Sent from my Nexus 5
You may be lucky. here you will find the cache.img on method 2. If it doesn't work, do the method 1
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
GUGUITOMTG4 said:
You may be lucky. here you will find the cache.img on method 2. If it doesn't work, do the method 1
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
I did try and it's not working either... Is there a part in the phone I can change to fix this ?
RealMyop said:
I did try and it's not working either... Is there a part in the phone I can change to fix this ?
Click to expand...
Click to collapse
The mother board
Sent from my SAMSUNG-SGH-I727
Hello,
I have ran out of things to try with this phone - hoping someone out there knows if there is something that can be done.
Was given the device to remove the FRP (Factory reset protection). I set up fastboot, adb drivers and started messing around with it.
First of all, I tried upgrading to the newest MM version for it using the official images from the Motorola website - turns out it does not remove the google account lock, and the version was different than the ones they use in the 'FRP bypass' videos.
Then, I tried downgrading it to 5.1.1 (the same way I did to MM, using fastboot), and some of the commands failed - resulting in the phone not booting up, unless I go straight for the Vol down + power button to get to the bootloader.
Lastly, I tried flashing an older version of MM, only to get 'failed to validate system image' on boot (picture below). Is there something that could fix this/remove the damn FRP? The warranty does not matter, the thing is unusable - any kind of ROM etc. would do. Debugging is disabled.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The loader, currently:
was the phone stolen? because why would anyone hard reset their device, just asking.
dont know any solution for you
and btw.. NEVER try to downgrade your device it can cause problems, as you see
Not sure, it was given as a collateral for a job or something, and the guy disappeared. Basically, it is either try and make it usable or just throw it away. Trying to figure out what are the options at the moment.
HelpMeruth said:
was the phone stolen? because why would anyone hard reset their device, just asking.
dont know any solution for you
and btw.. NEVER try to downgrade your device it can cause problems, as you see
Click to expand...
Click to collapse
You need to re-flash the latest firmware you flashed to your device boot again. To downgrade you have to unlock the bootloader first, but the OEM unlock setting in developer settings must be turned on, what I think you can't do with the FRP lock.
coolizard said:
You need to re-flash the latest firmware you flashed to your device boot again. To downgrade you have to unlock the bootloader first, but the OEM unlock setting in developer settings must be turned on, what I think you can't do with the FRP lock.
Click to expand...
Click to collapse
Ok, I flashed it again, it's 6.0.0. I even managed to get into the settings by doing the usual FRP bypass, however, this version does not have the developer options enabled by clicking the build number, and the 'users' setting is not there, therefore I cannot enable USB debugging like everyone does.
Your first error was upgrading to the latest version, because the newest version they have fixed.
I don't know if this will help, but in fastboot mode try to format system, and reflash the stock!
ExaHamza said:
Your first error was upgrading to the latest version, because the newest version they have fixed.
I don't know if this will help, but in fastboot mode try to format system, and reflash the stock!
Click to expand...
Click to collapse
I realize my mistake now :/ Tried formatting, reflashing.. I guess it's called Factory Reset Protection for a reason eh
Enirox said:
I realize my mistake now :/ Tried formatting, reflashing.. I guess it's called Factory Reset Protection for a reason eh
Click to expand...
Click to collapse
have you unlocked?
Sent from my MotoG3 using Tapatalk
ExaHamza said:
have you unlocked?
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
No, I have not. Had a real laugh though - I was able to access the settings - disable setup wizard - open chrome using google now, download apk's (like nova launcher) and have a home screen, browse apps all while FRP'ed. No go on the debugging/reset though :crying:
If can install apps try to root it with kingroot, and replace the stock recovery with TWRP, then format everything, and put another ROM into, after that reflash your stock. I don't know if you can do this without unlocking the bootloader.
I have seen some devices allowing do root + TWRP, without unlocking the bootloader. But you can try it!
Sent from my MotoG3 using Tapatalk
I tiried to flash the new oxygen pie beta. For whatever reason something went wrong and now here I am.
First time i flashed the beat I got the "Your device is corrupt" error. It's not the typical unlocked boot loader error. The explanation point is red, there is no mention of unlocked bootloader and I need to press power button in order to proceed. I tried flashing again at this point and I wiped everything in TWRP, but that didn't help.
Afterwards I have decided to go back to oreo and just upgrade to pie by local upgrade, but after flashing oreo I still get the red "your device is corrupt". However, I can still boot to the oxygen os and it seem to be working fine.
think its the encryption so reformat the data partition and start from scratch
RiTCHiE007 said:
think its the encryption so reformat the data partition and start from scratch
Click to expand...
Click to collapse
Formatted data and wiped everything. Flashed the pie beta. I can boot to the os, but I still get the error..
RiTCHiE007 said:
think its the encryption so reformat the data partition and start from scratch
Click to expand...
Click to collapse
I am decrypt and still get the same warning. I'm sure it'll be fixed later.
mikex8593 said:
I am decrypt and still get the same warning. I'm sure it'll be fixed later.
Click to expand...
Click to collapse
Thing is I still got that error when I went back to 8.1, which suggests it's not the android pie issue. Well, phone is working fine so I guess I will live for now.
Edit:
Something is messed up as I can't pass safetynet, CTS profile fails
Yep, the same. Even completely wiped everything in stock recovery. Seems fine once you hit power twice to go past it.
---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------
I had to flash the OnePlus6Oxygen_OTA_010_O_MR1_20180607.zip to fix the error when going back to 8.1. Grabbed ti from one of the How To threads for reverting.
Can you post the link to the file?
Barsky said:
Yep, the same. Even completely wiped everything in stock recovery. Seems fine once you hit power twice to go past it.
---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------
I had to flash the OnePlus6Oxygen_OTA_010_O_MR1_20180607.zip to fix the error when going back to 8.1. Grabbed ti from one of the How To threads for reverting.
Click to expand...
Click to collapse
Guess it is actually form Oneplus site:
https://forums.oneplus.com/threads/...ficial-oxygen-os-roms-and-ota-updates.835607/
In rollback builds under Signed flashable zips (Android P Developer Preview)
Your device will work by hitting power twice at the red text/corrupt still but you can fix it so that your on Beta without it.
Anyone thats getting corrupt device/red text during boot after flashing this beta or any other I have figured the only solution I know of possible atm to get around it so you can have beta's without the error. You will need to use the unbrick tool to totally clear your device from anything that is causing the issue and after that update your phone through settings as normal with no issue. Here is the tool and info for anyone who needs it:
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Every other way possible tried nothing else worked for me but this. Your device will be in the same state basically as it was in the box so *totally* cleaned.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nameless said:
Your device will work by hitting power twice at the red text/corrupt still but you can fix it so that your on Beta without it.
Anyone thats getting corrupt device/red text during boot after flashing this beta or any other I have figured the only solution I know of possible atm to get around it so you can have beta's without the error. You will need to use the unbrick tool to totally clear your device from anything that is causing the issue and after that update your phone through settings as normal with no issue. Here is the tool and info for anyone who needs it:
https://forum.xda-developers.com/one...ional-t3798892
Every other way possible tried nothing else worked for me but this. Your device will be in the same state basically as it was in the box so *totally* cleaned.
View attachment 4587785
Click to expand...
Click to collapse
The URL you shared is giving 404 error
Please share correct URL
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
This worked for me , back to stock , then try PIE again
:good:
soldier1 said:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
This worked for me , back to stock , then try PIE again
Click to expand...
Click to collapse
So you are now back to P beta 1 without the error? Hmm. I got my phone back to 8.1 without the area. But once I flashed it again, the same thing came back.
Thanks
Ended up using qualcomm tool, then flashed P beta 1, then unlocked bootloader, installed twrp, installed magisk7. Everything is good now.
Flashing stock didn't help me, I still had the error. I used the qualcom tool and now I'm on pie without the error.
Barsky said:
Yep, the same. Even completely wiped everything in stock recovery. Seems fine once you hit power twice to go past it.
---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------
I had to flash the OnePlus6Oxygen_OTA_010_O_MR1_20180607.zip to fix the error when going back to 8.1. Grabbed ti from one of the How To threads for reverting.
Click to expand...
Click to collapse
Also had the same and flashing back the roll back package fixed it, definitely keeping this zip!
Spoke too soon got the corrupt message after going back to 5.1.11 then to oos beta 1 so had to use the unbrick tool instead.
my guess is that the bootloader can not tell if phone is bootloader locked or unlocked. Has any1 tried flashing the bootloader files to see if that could fix it without debrick tool?
mati11233 said:
Thing is I still got that error when I went back to 8.1, which suggests it's not the android pie issue. Well, phone is working fine so I guess I will live for now.
Edit:
Something is messed up as I can't pass safetynet, CTS profile fails
Click to expand...
Click to collapse
No its not, safetynet will not pass, says so even in changelog
Yeah i got the same error, only solution for me was to use unbrick tool
Flash OOS Beta over H2OS beta, no need to wipe data between the two. But it works wonders.
i tried to flash 3qtr with pixel flasher now im in a loop and not sure how to fix can anyone help?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can you get into bootloader? Completely turn off the phone. Then wait a few seconds to make sure it is off. Afterwards, press power and volume down at the same time until you see bootloader menu.
If you can get into bootloader, go to android flash tools website and reflash.
When the screen goes black to reboot, hold down power + volume down. You should boot to bootloader doing that. Then you can flash the factory image and that should fix it... I think. I've never used Pixel Flasher before. I just do everything manually myself.
xdeeranx said:
Can you get into bootloader? Completely turn off the phone. Then wait a few seconds to make sure it is off. Afterwards, press power and volume down at the same time until you see bootloader menu.
If you can get into bootloader, go to android flash tools website and reflash.
Click to expand...
Click to collapse
yes i can
jdog94 said:
yes i can
Click to expand...
Click to collapse
Then you can can either download the factory image to manually patch (making sure to use platform tools r33.0.3 and NOT latest) or you can use android flash tools the website (If you use website, it's just follow instructions, select the image you want to flash, select options, then flash).
jdog94 said:
i tried to flash 3qtr with pixel flasher now im in a loop and not sure how to fix can anyone help?
Click to expand...
Click to collapse
Are you rooted and do you have any Magisk modules installed? Sounds like maybe a Magisk mod may be in need of an update and caused a bootloop. If this is the case, you can choose to disable Magisk mods in Pixel Flasher and flash again.
Kind of hard to tell without much details given...
Worked thanks So much
I was rooted not sure how I screwed up back to factory now
jdog94 said:
I was rooted not sure how I screwed up back to factory now
Click to expand...
Click to collapse
If you reflashed the image you remove root. Just reroot and you'll be okay.
Still not sure how to do 3qtr beta without screwing up
jdog94 said:
Still not sure how to do 3qtr beta without screwing up
Click to expand...
Click to collapse
Like what Lughnasadh said, it is hard to pinpoint the reason why it screwed up without enough information. Could be platform tools depending on what version you used. And it could also be your magisks modules that are causing the loop. Or the options you selected in pixel flasher. Not sure tbh. Or maybe an entire problem we aren't aware of lol.
Personally, what I would do is a clean flash. Cleanest way to do it. Just back up everything. Do a clean install of the image. Reroot and reinstall all apps/modules afterwards.
xdeeranx said:
Like what Lughnasadh said, it is hard to pinpoint the reason why it screwed up without enough information. Could be platform tools depending on what version you used. And it could also be your magisks modules that are causing the loop. Or the options you selected in pixel flasher. Not sure tbh. Or maybe an entire problem we aren't aware of lol.
Personally, what I would do is a clean flash. Cleanest way to do it. Just back up everything. Do a clean install of the image. Reroot and reinstall all apps/modules afterwards.
Click to expand...
Click to collapse
Thanks