I unlocked bootloader and installed Magisk using twrp recovery mode, then I've uninstalled magisk like normal app and locked bootloader, after that my device was showing a pop up that "System got destroyed". Then I unlocked bootloader again, after this I was able to get into my system but I've face a problem after successfully boot, I wasn't able to turn on wifi, then I've locked bootloader again now I'm having touch issues as well like I can't touch exact part of screen. Please help me out ,(Tried mi flash, doesn't work, getting error)(Sorry for bad English).
DeadsetNub said:
I unlocked bootloader and installed Magisk using twrp recovery mode, then I've uninstalled magisk like normal app and locked bootloader, after that my device was showing a pop up that "System got destroyed". Then I unlocked bootloader again, after this I was able to get into my system but I've face a problem after successfully boot, I wasn't able to turn on wifi, then I've locked bootloader again now I'm having touch issues as well like I can't touch exact part of screen. Please help me out ,(Tried mi flash, doesn't work, getting error)(Sorry for bad English).
Click to expand...
Click to collapse
Did you uninstall magisk through recovery or within magisk manager?
DeadsetNub said:
I unlocked bootloader and installed Magisk using twrp recovery mode, then I've uninstalled magisk like normal app and locked bootloader, after that my device was showing a pop up that "System got destroyed". Then I unlocked bootloader again, after this I was able to get into my system but I've face a problem after successfully boot, I wasn't able to turn on wifi, then I've locked bootloader again now I'm having touch issues as well like I can't touch exact part of screen. Please help me out ,(Tried mi flash, doesn't work, getting error)(Sorry for bad English).
Click to expand...
Click to collapse
Make sure boot.img and other firmware images and system images are from same release. Mostly you are facing firmware compatibility issues
WhatzIt2Ya said:
Did you uninstall magisk through recovery or within magisk manager?
Click to expand...
Click to collapse
firstly I've uninstall magisk like normal apps . app info-> Uninstall.
satishbmsce said:
Make sure boot.img and other firmware images and system images are from same release. Mostly you are facing firmware compatibility issues
Click to expand...
Click to collapse
How can I check it ? tbh I'm noob ?
DeadsetNub said:
firstly I've uninstall magisk like normal apps . app info-> Uninstall.
Click to expand...
Click to collapse
Well that's already a problem, the phone is still rooted. By locking the bootloader while the phone is rooted is a big no no. You'll cause all sorts of problems.
---------- Post added at 06:05 AM ---------- Previous post was at 06:03 AM ----------
DeadsetNub said:
firstly I've uninstall magisk like normal apps . app info-> Uninstall.
Click to expand...
Click to collapse
You need to download magisk uninstaller zip and flash it in twrp. If you still have twrp (with unlocked bootloader), flash it, boot the phone, relfash rom with mi flash tool.
WhatzIt2Ya said:
Well that's already a problem, the phone is still rooted. By locking the bootloader while the phone is rooted is a big no no. You'll cause all sorts of problems.
---------- Post added at 06:05 AM ---------- Previous post was at 06:03 AM ----------
You need to download magisk uninstaller zip and flash it in twrp. If you still have twrp (with unlocked bootloader), flash it, boot the phone, relfash rom with mi flash tool.
Click to expand...
Click to collapse
can you please tell me the procedure ?
DeadsetNub said:
can you please tell me the procedure ?
Click to expand...
Click to collapse
the thing is I'm having touch issue in TWRP mode as well.
DeadsetNub said:
How can I check it ? tbh I'm noob ?
Click to expand...
Click to collapse
If you are not sure. You can download a new fastboot stcok rom from MIUI website and flash it using MiFlash tool. Make sure that you select 'clean_all' option while flashing. You should not select 'clean_all_and_lock', that will lock the boot loader and it might lead to more issues
DeadsetNub said:
can you please tell me the procedure ?
Click to expand...
Click to collapse
I can't tell you the exact, because I never had this issue before, sorry.
Related
Hi. I was trying to install Cyanogenmod on my LG Leon. First, I rooted my phone using KingRoot and then replaced it with SuperSU. Then, I proceeded to install TWRP. But, because I was installing it my first time in my life, I made a mistake and tried do install it using TWRP Manager, without doing a backup of the stock recovery. After rebooting, secure boot error popped up and I had to take out the battery. Now whatever I do I cannot do anything custom rom related. Do you have any hints?
bokjezd said:
Hi. I was trying to install Cyanogenmod on my LG Leon. First, I rooted my phone using KingRoot and then replaced it with SuperSU. Then, I proceeded to install TWRP. But, because I was installing it my first time in my life, I made a mistake and tried do install it using TWRP Manager, without doing a backup of the stock recovery. After rebooting, secure boot error popped up and I had to take out the battery. Now whatever I do I cannot do anything custom rom related. Do you have any hints?
Click to expand...
Click to collapse
You have to enable OEM unlock in Developer Options to prevent the secure boot error, then flash the recovery using Flashify and reboot.
adefesio said:
You have to enable OEM unlock in Developer Options to prevent the secure boot error
Click to expand...
Click to collapse
I already found an advise like this, but I still cannot find that option. I think I have a little bit too old android. Do you know in which version of android it was introduced? I have 5.0.1. Maybe there is another hidden switch simular to the one enabling developer options used to enable OEM unlock?
bokjezd said:
I already found an advise like this, but I still cannot find that option. I think I have a little bit too old android. Do you know in which version of android it was introduced? I have 5.0.1. Maybe there is another hidden switch simular to the one enabling developer options used to enable OEM unlock?
Click to expand...
Click to collapse
Check if there's a software upgrade available from your provider. I can also suggest flashing back the original stock recovery image. Let me know if you need a download link. Which variant is your Leon?
adefesio said:
Check if there's a software upgrade available from your provider. I can also suggest flashing back the original stock recovery image. Let me know if you need a download link. Which variant is your Leon?
Click to expand...
Click to collapse
Yes, there is an update but currently I can't do it because updating reboots to recovery to update something. I would really like to flash back the original recovery, but I don't have the image, so can I have the link, please? My Leon is LG H340n.
bokjezd said:
Yes, there is an update but currently I can't do it because updating reboots to recovery to update something. I would really like to flash back the original recovery, but I don't have the image, so can I have the link, please? My Leon is LG H340n.
Click to expand...
Click to collapse
I am sending a private message with the link. Let me know if it works.
adefesio said:
I am sending a private message with the link. Let me know if it works.
Click to expand...
Click to collapse
Thanks, it seems to work now, but it refuses to update because it detects root. Is there a way to hide it or do I have to do a full unroot? I already tried the "Hide my Root" app.
Edit: Never mind, I will just do the unroot and then update.
Ok, I've downloaded recovery-H340N.img, but when I try to update, it shows that updating screen and then error 0x1125000 pops up. The phone reboots and then it tells me it detected root, however I did a full unroot... Do you know what that error means? And how does LG check for the root?
bokjezd said:
Ok, I've downloaded recovery-H340N.img, but when I try to update, it shows that updating screen and then error 0x1125000 pops up. The phone reboots and then it tells me it detected root, however I did a full unroot... Do you know what that error means? And how does LG check for the root?
Click to expand...
Click to collapse
Reset to factory settings, do the update, root with Kingroot (DON'T replace with SuperSU), restart, enable OEM unlock, install TWRP using Flashify.
adefesio said:
Reset to factory settings, do the update, root, enable OEM unlock, install TWRP using Flashify.
Click to expand...
Click to collapse
Wait, I need to do a backup of all my data, right?
bokjezd said:
Wait, I need to do a backup of all my data, right?
Click to expand...
Click to collapse
Google backs up most of your data, but not all. If you know other ways then do it.
---------- Post added at 03:53 PM ---------- Previous post was at 03:49 PM ----------
Google backs up most of your data but not all. If you know other ways then do it, then:
Reset to factory settings, do the update, root with Kingroot (DON'T replace with SuperSU), restart, enable OEM unlock, install TWRP using Flashify.
adefesio said:
Google backs up most of your data, but not all. If you know other ways then do it.
---------- Post added at 03:53 PM ---------- Previous post was at 03:49 PM ----------
Google backs up most of your data but not all. If you know other ways then do it, then:
Reset to factory settings, do the update, root with Kingroot (DON'T replace with SuperSU), restart, enable OEM unlock, install TWRP using Flashify.
Click to expand...
Click to collapse
I've reset my phone to factory settings, but it still refuses to update with error code 0x1125000 and after rebooting to home screen it says it detected root. I think I'm gonna update with LG Mobile Support Tool.
Wait, does my mobile operator affect what recovery should I flash? If yes, it is P4, often referred to as PLAY. Or maybe I should also flash the boot image you've sent to me? My PC doesn't detect my phone, so I have to repair the updates...
bokjezd said:
Wait, does my mobile operator affect what recovery should I flash? If yes, it is P4, often referred to as PLAY. Or maybe I should also flash the boot image you've sent to me? My PC doesn't detect my phone, so I have to repair the updates...
Click to expand...
Click to collapse
Too many complications. Just reflash the entire ROM with the most recent kdz. Root with Kingroot and don't replace it with SU. You know the rest.
Still nothing. Now it says it's the newest software available, but I cannot find that oem unlock. Are you sure it's available on Leon? I've read some manufacturers remove it...
Hey all!
First post on this site! Ok, so quick question, won't make this too long.
I updated my phone to os 3.1.0 which is awesome, however I want to root it now and I cannot find any recoveries for the new update? Anyone got any ideas or whether or not the old recovery would be compatible with this new update?
Thank you advance guys!
itshaassann said:
Hey all!
First post on this site! Ok, so quick question, won't make this too long.
I updated my phone to os 3.1.0 which is awesome, however I want to root it now and I cannot find any recoveries for the new update? Anyone got any ideas or whether or not the old recovery would be compatible with this new update?
Thank you advance guys!
Click to expand...
Click to collapse
In order to flash custom recovery you will need to unlock bootloader :
1. Instal adb\fastboot on PC then on your opt In developer options enable oem unlock.
2. Reboot phone to fastboot (power off, volume up+power)
3. From cmd type 'fastboot oem unlock'
Then go https://dl.twrp.me/oneplus2/ (download the latest version it will work on oxygen 3.1.0). Then flash supersu (attached)...and you got root
hi.. i flashed supersu 2.78 after updating to oos3.1.0 and i allways get stuck on bootlogo.. is your supersu file different from 2.78?
ty
DACATA said:
hi.. i flashed supersu 2.78 after updating to oos3.1.0 and i allways get stuck on bootlogo.. is your supersu file different from 2.78?
ty
Click to expand...
Click to collapse
Yes, the supersu I attached is modified, so it will work on oxygen 3.1.0.
Aca902 said:
Yes, the supersu I attached is modified, so it will work on oxygen 3.1.0.
Click to expand...
Click to collapse
yes.. got it ty still works
twrp not installing on my oxygenos 3.1.0
help me :'(
alansalim said:
twrp not installing on my oxygenos 3.1.0
help me :'(
Click to expand...
Click to collapse
I can think of two reasons: 1. Your bootloader is not unlocked
2. Your are not using the latest TWPR
It works for me.
@alansalim if you explain us the steps you took, then maybe we can help you
Aca902 said:
I can think of two reasons: 1. Your bootloader is not unlocked
2. Your are not using the latest TWPR
Click to expand...
Click to collapse
after flashing TWRP, when i boot into recovery....there is no TWRP, its stock recovery
alansalim -> step 3..... From cmd type 'fastboot oem unlock'
Aca902 -> twrp installs fine on my phone. but not your supersu ? is i because i'm not having a SD card and try to flash from phone memory ?
InzaneD said:
alansalim -> step 3..... From cmd type 'fastboot oem unlock'
Aca902 -> twrp installs fine on my phone. but not your supersu ? is i because i'm not having a SD card and try to flash from phone memory ?
Click to expand...
Click to collapse
What do you mean by SD card? OPT doesn't have a microsd slot.
I'm not sure, it should work... I have tested it on stock 3.1.0 with latest TWPR...and it worked fine (did it a few times when I was trying custom roms and going back to stock).
EDIT: Try downloading supersu again (maybe corrupted download?) and wipe cache after flashing supersu.
Aca902 said:
What do you mean by SD card? OPT doesn't have a microsd slot.
I'm not sure, it should work... I have tested it on stock 3.1.0 with latest TWPR...and it worked fine (did it a few times when I was trying custom roms and going back to stock).
EDIT: Try downloading supersu again (maybe corrupted download?) and wipe cache after flashing supersu.
Click to expand...
Click to collapse
HAHA I forgot it hasn't a microsd.. DOUGH.
well I have tried to download supersu again but same result. It fails then I try to flash and there's no error description
---------- Post added at 04:18 PM ---------- Previous post was at 03:47 PM ----------
InzaneD said:
HAHA I forgot it hasn't a microsd.. DOUGH.
well I have tried to download supersu again but same result. It fails then I try to flash and there's no error description
Click to expand...
Click to collapse
hmm got it working. just downloaded supersu again and now it works.. Thanks
the command in 3 line must be: fastboot oem unlock
and not fastboot oem ulock
Hello everyone. I am trying to update to October 2017 OTA. Everytime it returns error "Installation problem".
Is this because my phone has a modified bootloader? Perhaps its because I have rooted it? How can I get OTA updates again?
I'm having the same issue. Thought it was because of root but I restored the stock boot.img and no longer rooted but still getting 'Installation Problem' whenever i try to update.
jhorner said:
I'm having the same issue. Thought it was because of root but I restored the stock boot.img and no longer rooted but still getting 'Installation Problem' whenever i try to update.
Click to expand...
Click to collapse
you should also lock the bootloader for ota to work, i dont have mi a1 yet, but on nexus 6 it worked that way
Note to self, re-locking the bootloader will brick your phone
jhorner said:
Note to self, re-locking the bootloader will brick your phone
Click to expand...
Click to collapse
Not on this device... Done many times
Need to be unrooted and stock recovery. Unlocked BL is fine. Switch partition and start device for ota. Then reroot
Chris_Cheekyz said:
Not on this device... Done many times
Click to expand...
Click to collapse
Hmm. I just did 'fastboot oem lock' and after rebooting it says 'The system has been destroyed'
jhorner said:
Hmm. I just did 'fastboot oem lock' and after rebooting it says 'The system has been destroyed'
Click to expand...
Click to collapse
If you are rooted, your phone won't work if you try to lock bootloader. Unroot first and try again
First install stock ROM via MiFlashTool and then update..
It'll definitely work!
matcho13579 said:
If you are rooted, your phone won't work if you try to lock bootloader. Unroot first and try again
Click to expand...
Click to collapse
Just for context, this was the process
1. Tried to update w/o any changes, it failed
2. Unrooted, confirmed w/ SuperSU and tried to update, it failed
3. Locked bootloader via 'fastboot oem lock' and when the device rebooted, it gave the 'system destroyed' message
jhorner said:
Note to self, re-locking the bootloader will brick your phone
Click to expand...
Click to collapse
relocking bootloader dons'nt brick my phone
i have done this using this cmd - fastboot oem lock
and its works perfact
but do this at your own risk
:good::good::good:
Most ota installations failed is because system partition has been compromised. Even if you just mount it rw. You'll need to reflash system img for both system_a and system_b partition.
Restore stock boot.img if your using root (I'm using magisk) install ota and reroot. For magisk, starting from 14.4,you can follow the ota instructions for magisk, basically mi a1 the same as the pixel but not as strict. Locking and unlocking bootloader will not brick or wipe data for mi a1.
jhorner said:
Just for context, this was the process
1. Tried to update w/o any changes, it failed
2. Unrooted, confirmed w/ SuperSU and tried to update, it failed
3. Locked bootloader via 'fastboot oem lock' and when the device rebooted, it gave the 'system destroyed' message
Click to expand...
Click to collapse
Damn.
I've tried to remove root. Removed SuperSu. Flashed stock bootloader - but update continues to fail.
I'll just wait for Oreo then do a full flash
Even i got the same error
What i did was,
Removed Magisk
Flashed latest rom by mi flash with save user data option
Then update ur device, it will work for sure!
Monthly security updates installation problem,how to fix that? Please throw some lights
GSAA RAIN said:
Monthly security updates installation problem,how to fix that? Please throw some lights
Click to expand...
Click to collapse
You should post some information on your phone. Is it stock/rooted? Did you unlock bootloader and install TWRP? What modifications have you done to the phone (if any?)
cheesekun27 said:
Damn.
I've tried to remove root. Removed SuperSu. Flashed stock bootloader - but update continues to fail.
I'll just wait for Oreo then do a full flash
Click to expand...
Click to collapse
You can use miflash and flash the full rom so you are back at stock, just make sure you select the option to save user data so it does not wipe your phone clean.
I have the same problem...what i did was unlocking the bootloader and tried to install themes via substratum and andromeda...but that didn't worked so i uninstalled both and relocked the bootloader. I didn't even rooted the phone but getting the same error. Is this because somehow partition was compromised and can someone please provide me a brief description of rooting this phone and usage of magisk?
Angelictears said:
Most ota installations failed is because system partition has been compromised. Even if you just mount it rw. You'll need to reflash system img for both system_a and system_b partition.
Restore stock boot.img if your using root (I'm using magisk) install ota and reroot. For magisk, starting from 14.4,you can follow the ota instructions for magisk, basically mi a1 the same as the pixel but not as strict. Locking and unlocking bootloader will not brick or wipe data for mi a1.
Click to expand...
Click to collapse
In short one needs to flash the stock rom using mi flash tool right?
---------- Post added at 06:43 AM ---------- Previous post was at 06:42 AM ----------
Angelictears said:
Most ota installations failed is because system partition has been compromised. Even if you just mount it rw. You'll need to reflash system img for both system_a and system_b partition.
Restore stock boot.img if your using root (I'm using magisk) install ota and reroot. For magisk, starting from 14.4,you can follow the ota instructions for magisk, basically mi a1 the same as the pixel but not as strict. Locking and unlocking bootloader will not brick or wipe data for mi a1.
Click to expand...
Click to collapse
thakurvishwendra said:
I have the same problem...what i did was unlocking the bootloader and tried to install themes via substratum and andromeda...but that didn't worked so i uninstalled both and relocked the bootloader. I didn't even rooted the phone but getting the same error. Is this because somehow partition was compromised and can someone please provide me a brief description of rooting this phone and usage of magisk?
Click to expand...
Click to collapse
Were you able to solve your problem?
Couldn't update Installation problem
Rohit Surya said:
Even i got the same error
What i did was,
Removed Magisk
Flashed latest rom by mi flash with save user data option
Then update ur device, it will work for sure!
Click to expand...
Click to collapse
I did thi but problem is still same installation problem
---------- Post added at 04:23 PM ---------- Previous post was at 04:20 PM ----------
goofball2k said:
You should post some information on your phone. Is it stock/rooted? Did you unlock bootloader and install TWRP? What modifications have you done to the phone (if any?)
Click to expand...
Click to collapse
Nothing yet I am facing the installation problem
Hi there I'm new to root, my question is if I root my device will it void my warranty? I only got the device since Nov last year so if it will break the warranty then I'll wait till my warranty runs out. Thanks any feed back will be appreciate
No
Statement from OnePlus said:
The technical process of rooting or unlocking the bootloader does not void the warranty of a OnePlus device. However, we strongly suggest for you to only root or unlock the bootloader of your OnePlus device if you are confident in your understanding of the risks involved.
By accessing resources regularly unavailable to the software, you may damage your hardware during or after the procedure. Such damage is not covered under warranty. In warranty handling, we will first need to verify that any faulty behavior is unrelated to rooting / unlocking.
Click to expand...
Click to collapse
pandachee3 said:
Hi there I'm new to root, my question is if I root my device will it void my warranty? I only got the device since Nov last year so if it will break the warranty then I'll wait till my warranty runs out. Thanks any feed back will be appreciate
Click to expand...
Click to collapse
This Damage Referred is regarding if you by some way kill the motherboard or kill some component by kernel and voltage tweaks which is pretty common to happened if you dont know what ur doing, normal flashing roms and using the devices has no issue
Scronix said:
This Damage Referred is regarding if you by some way kill the motherboard or kill some component by kernel and voltage tweaks which is pretty common to happened if you dont know what ur doing, normal flashing roms and using the devices has no issue
Click to expand...
Click to collapse
Thanks, I will just only root the device and install viper.
You can do what you want with youre phone. If you want out of the box phone again, flash MSM tool. This will wipe absolute everything in youre phone and lock the boot loader.
null0seven said:
You can do what you want with youre phone. If you want out of the box phone again, flash MSM tool. This will wipe absolute everything in youre phone and lock the boot loader.
Click to expand...
Click to collapse
So is that mean if I flash msm tool it will go back to the phone when I got it? Like basically factory reset then yeah? Thanks
pandachee3 said:
So is that mean if I flash msm tool it will go back to the phone when I got it? Like basically factory reset then yeah? Thanks
Click to expand...
Click to collapse
Exactly. It wipes the phone, restores it to stock OxygenOS and locks the bootloader.
Dopamin3 said:
Exactly. It wipes the phone, restores it to stock OxygenOS and locks the bootloader.
Click to expand...
Click to collapse
Thank you so much
Sorry to ask question again, I look for root my device in Google. There's something about A/B slot do I need to do that just for install magisk and do some custom fonts and install viper?
pandachee3 said:
Sorry to ask question again, I look for root my device in Google. There's something about A/B slot do I need to do that just for install magisk and do some custom fonts and install viper?
Click to expand...
Click to collapse
No, but when you want to install software updates you will need to either flash them through twrp and flash twrp again BEFORE you REBOOT. Then reboot to recovery and flash Magisk again to keep root.
Or you can go into magisk, choose uninstall (restore images) flash the update from the os system update. Then before you reboot, go back into magisk and choose install (after OTA option) then you can reboot.
pandachee3
why look on google? You have here a very good guide, step by step, by Fank Wizard
ebproject said:
No, but when you want to install software updates you will need to either flash them through twrp and flash twrp again BEFORE you REBOOT. Then reboot to recovery and flash Magisk again to keep root.
Or you can go into magisk, choose uninstall (restore images) flash the update from the os system update. Then before you reboot, go back into magisk and choose install (after OTA option) then you can reboot.
Click to expand...
Click to collapse
Can I simply just update if I want to update? Then go through the same process again like unlock my bootloader then flash twrp then flash magisk again?
null0seven said:
pandachee3
why look on google? You have here a very good guide, step by step, by Fank Wizard
Click to expand...
Click to collapse
Can you share the link please? Thanks
pandachee3 said:
Can I simply just update if I want to update? Then go through the same process again like unlock my bootloader then flash twrp then flash magisk again?
Click to expand...
Click to collapse
Yeah of course. If you use the TWRP method you don't have to do the adb part again, just flash TWRP and magisk again via TWRP.
---------- Post added at 04:46 PM ---------- Previous post was at 04:44 PM ----------
pandachee3 said:
Can you share the link please? Thanks
Click to expand...
Click to collapse
The full guide is here...
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
I recommend always using the TWRP method otherwise you'll lose TWRP recovery after installing software updates.
ebproject said:
Yeah of course. If you use the TWRP method you don't have to do the adb part again, just flash TWRP and magisk again via TWRP.
---------- Post added at 04:46 PM ---------- Previous post was at 04:44 PM ----------
The full guide is here...
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
I recommend always using the TWRP method otherwise you'll lose TWRP recovery after installing software updates.
Click to expand...
Click to collapse
Thank you so much your a star can I ask what else can I do to my device too? ?
pandachee3 said:
Thank you so much your a star can I ask what else can I do to my device too?
Click to expand...
Click to collapse
I'm using these Magisk modules at the moment:
Busybox
Energized Protection
Viper4Android
YouTube Vanced
OnePlus stereo speaker mod
xXx No Limits ROM (this is a rom that works with Oxygen OS. You can debloat system apps, speed your system up, kill unwanted background applications... and more, with no need to flash a new OS or lose your data)
You can use a themeing app called substratum, but make sure the theme you're applying supports whatever ROM you're using.
Install a custom Kernel.
The possibilities are endless mate. Just make sure you read through whatever you are flashing, you don't want to end up with a brick.
ebproject said:
I'm using these Magisk modules at the moment:
Busybox
Energized Protection
Viper4Android
YouTube Vanced
OnePlus stereo speaker mod
xXx No Limits ROM (this is a rom that works with Oxygen OS. You can debloat system apps, speed your system up, kill unwanted background applications... and more, with no need to flash a new OS or lose your data)
You can use a themeing app called substratum, but make sure the theme you're applying supports whatever ROM you're using.
Install a custom Kernel.
The possibilities are endless mate. Just make sure you read through whatever you are flashing, you don't want to end up with a brick.
Click to expand...
Click to collapse
I don't think I'm confident to do the kernel stuff, I have root all my samsung device before but I'm talking about few years back. That was still note 2 or note 3 lol and I flash custom rom before the rom looks cool lol.
Stereo audio and Dolby Atmos is my thing as well as viper and font.
But thank you so much for your help ?
pandachee3 said:
I don't think I'm confident to do the kernel stuff, I have root all my samsung device before but I'm talking about few years back. That was still note 2 or note 3 lol and I flash custom rom before the rom looks cool lol.
Stereo audio and Dolby Atmos is my thing as well as viper and font.
But thank you so much for your help
Click to expand...
Click to collapse
No problem.
but ....... I am in twrp unable to reboot into my rom. When I click on Install I see all these folders with letters and numbers and what my original folders.
Can somone help me boot into my rom again?
ms.journie said:
but ....... I am in twrp unable to reboot into my rom. When I click on Install I see all these folders with letters and numbers and what my original folders.
Can somone help me boot into my rom again?
Click to expand...
Click to collapse
You will more than likely need to format data. This will cause you to loose everything. But that is what you are seeing, those folders, are your data. Just encrypted.
Also make sure you are on the latest version of TWRP. Sometimes the older unsupported version had encryption errors.
Omg this saddens me! So there's no way I am unable to at least retrieve my pictures?
Scott said:
You will more than likely need to format data. This will cause you to loose everything. But that is what you are seeing, those folders, are your data. Just encrypted.
Also make sure you are on the latest version of TWRP. Sometimes the older unsupported version had encryption errors.
Click to expand...
Click to collapse
Have u tested change boot partition ?
yup
J3zz said:
Have u tested change boot partition ?
Click to expand...
Click to collapse
ms.journie said:
yup
Click to expand...
Click to collapse
Simple test are:
- change boot partition
- reflash system
- Say goodbye too all
Got the same problem, Solved After reboot in twrp and enter the good decryption code
I'm right in the middle of reflashing. I am trying everything else before I do say goodbye to my pictures! :crying:
How did you figure out the decryption code?
J3zz said:
Simple test are:
- change boot partition
- reflash system
- Say goodbye too all
Got the same problem, Solved After reboot in twrp and enter the good decryption code
Click to expand...
Click to collapse
ms.journie said:
I'm right in the middle of reflashing. I am trying everything else before I do say goodbye to my pictures! :crying:
How did you figure out the decryption code?
Click to expand...
Click to collapse
First time entering in twrp after flashing update, I did not get folder to flash magisk, did a reboot and get it, just a bad encryption code I think
Did u flash rom or anything else before getting this problem ?
Yup, I sure did! 4am couldn't sleep so I thought I would finally put a fingerprint mod on; which I have done this before with no issues. For the life of me, I don't remember which mod I tried to install thru Magisk.
My phone is currently stuck on "Phone is starting"
I also think it's time to look into some sort of automatic back up service..... Got any ideas?
J3zz said:
First time entering in twrp after flashing update, I did not get folder to flash magisk, did a reboot and get it, just a bad encryption code I think
Did u flash rom or anything else before getting this problem ?
Click to expand...
Click to collapse
ms.journie said:
Yup, I sure did! 4am couldn't sleep so I thought I would finally put a fingerprint mod on; which I have done this before with no issues. For the life of me, I don't remember which mod I tried to install thru Magisk.
My phone is currently stuck on "Phone is starting"
I also think it's time to look into some sort of automatic back up service..... Got any ideas?
Click to expand...
Click to collapse
Use msmdownloadtool, have u tried using magisk uninstall in twrp with zip file ? Then boot and uninstall the "****in" fantastic module... maybe it works
I did try to uninstall Magisk in twrp using adb shell. I never had any luck with that msmdownloadtool and not only that it relocks your bootloader.
I usually go this route [ROM][STOCK][FASTBOOT][OP6T] Stock Fastboot ROMs for OnePlus 6T https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Thanks for trying to me!
J3zz said:
Use msmdownloadtool, have u tried using magisk uninstall in twrp with zip file ?
Click to expand...
Click to collapse
ms.journie said:
I did try to uninstall Magisk in twrp using adb shell. I never had any luck with that msmdownloadtool and not only that it relocks your bootloader.
I usually go this route [ROM][STOCK][FASTBOOT][OP6T] Stock Fastboot ROMs for OnePlus 6T https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Thanks for trying to me!
Click to expand...
Click to collapse
Good luck !!
I saw this happen when I used the official TWRP app.
It went away when I used this TWRP. Hope that helps.
I'm glad you already know not to use the MSM tool. Too many people jump straight to this.....
You just need to boot the correct recovery and your data will decrypt, and you will be able to back it up to a PC, then you can reload your ROM via TWRP or Fastboot to get the phone bootable again. So now it's a question of what ROM were you running before. Do you need a recovery with the latest security patch or something older? What TWRP are you running. Try 3.3.1-6 psychen6 linked too first. Boot that image from Fastboot. See if your password/pin will work to decrypt your data.