Heyo!
So.. I recently got the 930F and rooted successful with odin, but my question is now, how do I successfully flash a working TWRP without having all the issues ppl describe below the twrp thread for sgs7?
greetz
after flashing TWRP with odin, enter your new recovery.
Wipe everything, then flash the rest of the files. You won't be able to boot otherwise.
You must in Odin remove the hook at autoreboot.
And then manually switch off the mobile phone with "Home-Vol--Power", then start with "Home-Vol+-Power" and wait until the TWRP screen comes and then let go.
Senaxo said:
You must in Odin remove the hook at autoreboot.
And then manually switch off the mobile phone with "Home-Vol--Power", then start with "Home-Vol+-Power" and wait until the TWRP screen comes and then let go.
Click to expand...
Click to collapse
But I didnt flash TWRP yet, cuz I used the CF-Root method by Chainfire, just rooted with odin and got supersu installed, i cant even boot into a recovery? my phone just starts normally, doesnt samsung have a normal recovery?
can I just re-root with a method with TWRP included without worries or am I gonna brick my phone?
bump
i suggest to full wipe after installing TWRP.
Abuzar Uzair said:
i suggest to full wipe after installing TWRP.
Click to expand...
Click to collapse
Why would you suggest a full wipe? Is it needed?
I did the same thing... used CF-Auto-Root to root my S7 and noticed that I didn't have TWRP. So I just downloaded TWRP Manager from the Play Store and used that to flash TWRP to Recovery. It worked perfectly as far as I can tell, no need to wipe anything.
Unless I've missed something?
d3adm8n said:
Why would you suggest a full wipe? Is it needed?
I did the same thing... used CF-Auto-Root to root my S7 and noticed that I didn't have TWRP. So I just downloaded TWRP Manager from the Play Store and used that to flash TWRP to Recovery. It worked perfectly as far as I can tell, no need to wipe anything.
Unless I've missed something?
Click to expand...
Click to collapse
The full wipe will disable data & sd encryption, so you will not face any problem while flashing roms & kernals, or creating twrp backup.
d3adm8n said:
Why would you suggest a full wipe? Is it needed?
I did the same thing... used CF-Auto-Root to root my S7 and noticed that I didn't have TWRP. So I just downloaded TWRP Manager from the Play Store and used that to flash TWRP to Recovery. It worked perfectly as far as I can tell, no need to wipe anything.
Unless I've missed something?
Click to expand...
Click to collapse
Did it really work? ive read a few other posts about ppl bricking their phones by doing that D:
bump
bump
Maybe a good read if your on Nougat?
https://forum.xda-developers.com/galaxy-s7/how-to/root-official-stock-nougat-7-0-100-t3540765
johnny8910 said:
Maybe a good read if your on Nougat?
https://forum.xda-developers.com/galaxy-s7/how-to/root-official-stock-nougat-7-0-100-t3540765
Click to expand...
Click to collapse
That's completely unrelated to my issue
Kickazz080 said:
Heyo!
So.. I recently got the 930F and rooted successful with odin, but my question is now, how do I successfully flash a working TWRP without having all the issues ppl describe below the twrp thread for sgs7?
greetz
Click to expand...
Click to collapse
I don't know if I'm too late, but this is what I did and it was the easiest way to get TWRP.
Go to the Play Store and download 'TWRP Manager App', when on there hit 'Install TWRP', look for the SG7 type for TWRP and choose the latest datedTWRP (People tend to get Recovery is not seandroid enforcing error because they use an out-of-date recovery image).
It will say there was an error flashing recovery and give the option to Reboot or Reboot Later, but it actually has managed to get TWRP onto your phone so just reboot there and then.
Boom you have TWRP; remember the first thing to do is Format Data.
Good Luck
AzzyC said:
I don't know if I'm too late, but this is what I did and it was the easiest way to get TWRP.
Go to the Play Store and download 'TWRP Manager App', when on there hit 'Install TWRP', look for the SG7 type for TWRP and choose the latest datedTWRP (People tend to get Recovery is not seandroid enforcing error because they use an out-of-date recovery image).
It will say there was an error flashing recovery and give the option to Reboot or Reboot Later, but it actually has managed to get TWRP onto your phone so just reboot there and then.
Boom you have TWRP; remember the first thing to do is Format Data.
Good Luck
Click to expand...
Click to collapse
Format data when I first boot the phone after the twrp-installation-restart? or before flashing rom/kernel?
Kickazz080 said:
Format data when I first boot the phone after the twrp-installation-restart? or before flashing rom/kernel?
Click to expand...
Click to collapse
Format Data after TWRP Installation because our S7 phone has dm-verity and you will not be able to flash zips and ROMs properly. Formatting will get rid of that verity encryption.
Another reason why to format data after TWRP installation is because as this method does not fully get rid of stock recovery and is left dormant, so formatting the data will let TWRP read your Data.
AzzyC said:
Format Data after TWRP Installation because our S7 phone has dm-verity and you will not be able to flash zips and ROMs properly. Formatting will get rid of that verity encryption.
Another reason why to format data after TWRP installation is because as this method does not fully get rid of stock recovery and is left dormant, so formatting the data will let TWRP read your Data.
Click to expand...
Click to collapse
Is there any chance of me ****ing up and losing my imei or smth?
Kickazz080 said:
Is there any chance of me ****ing up and losing my imei or smth?
Click to expand...
Click to collapse
Nope. That is not part of the Data partition so the format shouldn't affect - IMEI No. is part of the EFS partition.
If you do come with any problems though, quote me and I'm here to help. But believe I'm telling you what even I did and I'm running ROMS and shiz now.
Related
I'm hoping someone can help. i have looked in the forums but can't get an solid advice, recently got my galaxy s7 rooted it using cf auto root, i then downloaded latest firmware update for my device from sammobile, used odin to install but it failed and i can't even factory reset my phone as it says Dm-verity verification failure. any help would be great
follow the twrp steps and you will be fine
Studio1b said:
follow the twrp steps and you will be fine
Click to expand...
Click to collapse
Can you elaborate as I'm new to samsung modding been using nexus for a long time
did you follow : http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
If you only want a bootable system partition or writable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
Studio1b said:
did you follow : http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
If you only want a bootable system partition or writable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
Click to expand...
Click to collapse
So your saying i can disable no verity and will be able to install ota via odin? I never used this guide ill check it out
tonyafc said:
So your saying i can disable no verity and will be able to install ota via odin? I never used this guide ill check it out
Click to expand...
Click to collapse
If you do the steps you will be able to restore to stock with kies or smartwatch or odin
or flash a rom once u reboot back to twrp
Studio1b said:
If you do the steps you will be able to restore to stock with kies or smartwatch or odin
or flash a rom once u reboot back to twrp
Click to expand...
Click to collapse
Should i flash the Dm-verity disabler? And I'm already on the stock do you mean latest firmware/ota?
1st off why would u want to do that.
this is what you need to do : CF-AUTO / TWRP / dm-verity / flash custom rom.
If you want a stock rom with root then you need to do everything but flash a custom rom
any time a ota update is forced you will be unrooted, your best best is to do what what i just said
Studio1b said:
any time a ota update is forced you will be unrooted, your best best is to do what what i just said
Click to expand...
Click to collapse
false if using latest CFAR/superSU version
sanriver12 said:
false if using latest CFAR/superSU version
Click to expand...
Click to collapse
So can i get twrp and receive ota on my device or use odin for ota?
tonyafc said:
So can i get twrp and receive ota on my device or use odin for ota?
Click to expand...
Click to collapse
OTA updates will be blocked
https://plus.google.com/+Chainfire/posts/XMFgencRR11
sanriver12 said:
OTA updates will be blocked
https://plus.google.com/+Chainfire/posts/XMFgencRR11
Click to expand...
Click to collapse
So does this mean i cant install latest firmware from sammobile using odin?
Will this void warranty or trip knox guys?
121man said:
Will this void warranty or trip knox guys?
Click to expand...
Click to collapse
Hi
Yes it will......
Guys I am in need of help. I did not fully understand step 10 and just skipped originally. I did notice I could not wipe anything but thought I would be fine so I just dirty flashed custom ROM assuming wipe would work afterwards and I can clean install after.
I am obviously stuck now with 0MB internal storage shown along with no access to phone since it says upon boot that verification has failed and that I need to reset my phone.
Now, I do have important photos/datas which I do not want to lose... I did hear other guys restored their nandroid backup and were fine.
My question is, is there any way for me to access and back up my internal data somehow? I did hear something like flashing a stock firmware via Odin without the cache inside. Could someone confirm that this would work please? Would really appreciate a response. Thanks guys.
EDIT: I did try this:
If you only want a bootable system partition or writable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
But TWRP would not allow me to flash because it said it could not mount storage.
GI guys I have a problem. I rotted the phone with no problem. And I installed twrp. But when I went ahead and installed a custom is it for the first says no access to sdcard in twrp. Next when it boots up it says encryption error or somthing.so then I trie to wipe it, but it just says error. Unable to mount..
So then I go ahead and flash original firmware with Odin and it boots up OK. No problems and everything is just how I left i t acctualy. All my APS and SMS etc. But the root access and twrp is gone.
I then go ahead and flash the autoroot with Odin with no issue. But when it reboots its stuck with black screen and it says with red letters: selinux is not permissive.
So I just finished flashing original is again. And now I'm stuck. What can I do to get this mess sorted.
Please help me.
When you flash TWRP you have to then wipe everything.
then flash supersu
then flash no-verity-opt-encrypt zip
then reboot.
wipe before or after flash twrp? I believe before, hope I'm right
Okay I will try. But where do I get this encrypt zip file?
remosam said:
wipe before or after flash twrp? I believe before, hope I'm right
Click to expand...
Click to collapse
chrb1985 said:
Okay I will try. But where do I get this encrypt zip file?
Click to expand...
Click to collapse
Wipe after flashing TWRP.
All the files you need should be in the TWRP thread for the Galaxy S7
OK. Thanks guys. I wikk give it a try and let you know how it works out
It worked guys. Thanks alot for the help
I went to reload 5.1.11 ..I think it might be because I forgot to remove my security features now keeps rebooting to TWPR
do I have to do a compete wipe now....or is there a simple method ?? Thanks for the help!
Did you have magisk installed? Did you install it again after flashing full ota and twrp?
ImSpiderman said:
Did you have magisk installed? Did you install it again after flashing full ota and twrp?
Click to expand...
Click to collapse
Yes I followed the guide here.. full rom, TWRP installer, reboot to recovery, Magisk 16.4 reboot system..........boots back to TWRP
double post
skyeking69 said:
Yes I followed the guide here.. full rom, TWRP installer, reboot to recovery, Magisk 16.4 reboot system..........boots back to TWRP
Click to expand...
Click to collapse
Strange, that happened to me because i didn't Remember to reflash magisk...wait for someone else to answer but if it isn't a big deal for you i'll just factory reset, it's always good to do after a new update
ImSpiderman said:
Strange, that happened to me because i didn't Remember to reflash magisk...wait for someone else to answer but if it isn't a big deal for you i'll just factory reset, it's always good to do after a new update
Click to expand...
Click to collapse
Yeah I tried that too everything except internal storage...just wondering if I have to wipe that as well ??
skyeking69 said:
Yeah I tried that too everything except internal storage...just wondering if I have to wipe that as well ??
Click to expand...
Click to collapse
No you don't have to
ImSpiderman said:
No you don't have to
Click to expand...
Click to collapse
Well I guess I'll wait for more ideas..... Or might just wipe internal and see what happens...
skyeking69 said:
Well I guess I'll wait for more ideas..... Or might just wipe internal and see what happens...
Click to expand...
Click to collapse
That didn't work? Really strange tho
See this. This article only applies to users running TWRP recovery on a rooted device. Don't have TWRP or don't know what this means? You're probably fine.
If you've recently installed or updated TWRP recovery, you might have faced that you can't install anything with it, and that the start screen is immediately shown when updating your device via Oxygen Updater.
Why is this happening to me?
From what it seems, this issue is caused by TWRP versions 3.2.2-0 and 3.2.3-0 being incompatible with the storage encryption technology present on OnePlus devices.
Normally, you're asked to enter your PIN or unlock pattern before installing an update / flashing something yourself. However, these new TWRP versions don't prompt for it anymore. Therefore, accessing the storage space of your device is no longer possible.
This is really frustrating, as almost all of your updates / .zip files are stored there. But luckily, there is a solution:
How do I fix this issue?
First of all, if you don't have encryption turned on or are not facing this issue, do not proceed with the steps below since flashing a new version of TWRP can be risky.
Now for the the solution: it involves downgrading TWRP to an earlier version, in which installing updates still worked correctly.
The downgrade can be done either by using a computer with the fastboot command, or by using flashing apps such as the Official TWRP app or Flashify on your device itself.
These are the steps you'll need to do:
- Make sure to download TWRP version 3.2.1-1 for your specific device. This is the version which worked fine, and is still fairly recent.
- Flash the version of TWRP using your method of choice. For fastboot users, connect your device to your computer in Fastboot mode and type fastboot flash recovery twrp-3.2.1-1-<yourdevice>.img. When using any of the flashing apps, browse to the correct TWRP.img file and flash it.
- Reboot your device. You'll now be able to access the working version of TWRP
- Do not update your TWRP version until it has been confirmed that this issue has been resolved.
Thanks to Peter Aarnoutse for reporting this issue.
Icon credit: Twitter
Gradusr said:
See this. This article only applies to users running TWRP recovery on a rooted device. Don't have TWRP or don't know what this means? You're probably fine.
If you've recently installed or updated TWRP recovery, you might have faced that you can't install anything with it, and that the start screen is immediately shown when updating your device via Oxygen Updater.
Why is this happening to me?
From what it seems, this issue is caused by TWRP versions 3.2.2-0 and 3.2.3-0 being incompatible with the storage encryption technology present on OnePlus devices.
Normally, you're asked to enter your PIN or unlock pattern before installing an update / flashing something yourself. However, these new TWRP versions don't prompt for it anymore. Therefore, accessing the storage space of your device is no longer possible.
This is really frustrating, as almost all of your updates / .zip files are stored there. But luckily, there is a solution:
How do I fix this issue?
First of all, if you don't have encryption turned on or are not facing this issue, do not proceed with the steps below since flashing a new version of TWRP can be risky.
Now for the the solution: it involves downgrading TWRP to an earlier version, in which installing updates still worked correctly.
The downgrade can be done either by using a computer with the fastboot command, or by using flashing apps such as the Official TWRP app or Flashify on your device itself.
These are the steps you'll need to do:
- Make sure to download TWRP version 3.2.1-1 for your specific device. This is the version which worked fine, and is still fairly recent.
- Flash the version of TWRP using your method of choice. For fastboot users, connect your device to your computer in Fastboot mode and type fastboot flash recovery twrp-3.2.1-1-<yourdevice>.img. When using any of the flashing apps, browse to the correct TWRP.img file and flash it.
- Reboot your device. You'll now be able to access the working version of TWRP
- Do not update your TWRP version until it has been confirmed that this issue has been resolved.
Thanks to Peter Aarnoutse for reporting this issue.
Icon credit: Twitter
Click to expand...
Click to collapse
Thanks but I really don't understand this....first I don't know if encryption is on ? Don't think I have turned it off...2nd 3.2.2.0 worked fine for me before..I installed 5.1.9 and 5.1.11 with no problems.....it was when I tried to reinstall 5.1.11 and forgot to remove security features this happened now?
How old is this thread about TWRP 3.2.2.0 ?
It happened to me since the first time. what i do is wipe everything except internal, flash rom, flash twrp, reboot twrp, boot system, and then after set up, reboot recovery and flash magisk.
I dont know what is the problem ive never used a security feature.(maybe thats my problem)
WOS17 said:
It happened to me since the first time. what i do is wipe everything except internal, flash rom, flash twrp, reboot twrp, boot system, and then after set up, reboot recovery and flash magisk.
I dont know what is the problem ive never used a security feature.(maybe thats my problem)
Click to expand...
Click to collapse
I'll give that a try...... you have no pin or fingerprint or face unlock setup ??
If you have face unlock and or pin than you have issues with the new twrp reed this article , I have posted than you understand it.
Go to twrp and wipe dalvik/art cache, system, data *do not wipe internal* then flash 5.1.11 followed by twrp from xda, reboot to recovery again and flash *latest* Magisk 16.7 not 16.4, reboot system. 100% steps to use if doesn't work God knows whats haqppening to yours mate.
skyeking69 said:
I'll give that a try...... you have no pin or fingerprint or face unlock setup ??
Click to expand...
Click to collapse
No, any security just double tap to wake.
Nameless said:
Go to twrp and wipe dalvik/art cache, system, data *do not wipe internal* then flash 5.1.11 followed by twrp from xda, reboot to recovery again and flash *latest* Magisk 16.7 not 16.4, reboot system. 100% steps to use if doesn't work God knows whats haqppening to yours mate.
Click to expand...
Click to collapse
which TWRP version are you using? what Ive read is Magisk 16.7 has some problems like the pop up that say you have to contact your manufacturer
Nameless said:
Go to twrp and wipe dalvik/art cache, system, data *do not wipe internal* then flash 5.1.11 followed by twrp from xda, reboot to recovery again and flash *latest* Magisk 16.7 not 16.4, reboot system. 100% steps to use if doesn't work God knows whats haqppening to yours mate.
Click to expand...
Click to collapse
Thanks..I'll try that first....the TWRP I have is 3.2.2.0 from official page ( I think ?) I'll try 16.7 and see what happens..
WOS17 said:
No, any security just double tap to wake.
which TWRP version are you using? what Ive read is Magisk 16.7 has some problems like the pop up that say you have to contact your manufacturer
Click to expand...
Click to collapse
I'm using 3.2.2.0 which was working fine.....the guy below tells me to use 16.7 Magisk???? Geez not sure now ?
Gradusr said:
If you have face unlock and or pin than you have issues with the new twrp reed this article , I have posted than you understand it.
Click to expand...
Click to collapse
The thing is TWRP 3.2.2.0 does ask me to enter my pin code then goes to the options page...install, wipe, backup,restore...etc...
Nameless said:
Go to twrp and wipe dalvik/art cache, system, data *do not wipe internal* then flash 5.1.11 followed by twrp from xda, reboot to recovery again and flash *latest* Magisk 16.7 not 16.4, reboot system. 100% steps to use if doesn't work God knows whats haqppening to yours mate.
Click to expand...
Click to collapse
Geez ...now when I go to reboot to recovery it gives me a warning " No OS installed, are you sure you want to reboot?? " what do I do now ??
After i wanted to install Android P, i got a bootloop. so i wanted to go to twrp but now my files are encrypted and twrp is not asking for a pin or pattern so i can't decrypt my internal storage files.
Now the biggest problem is that i just came back from a family weekend and i made a lot of pictures, witch i can't acces now, and i really want them back.
Now i can't install a new os or anything ...
Can someone please help me! i'm really despirate
(sorry for my bad english)
Try downgrading twrp , night get it to ask for pin
downgrading is never the answer. In fact, that will cause this problem to happen. Now i must ask, are you temp booting twrp or is twrp installed to phone.
I got this when I temp booted the mtp enabled twrp the other day, although it still asked for my passcode and said description was successful. When I rebooted the installed (official) twrp it all came back....
MrSteelX said:
downgrading is never the answer. In fact, that will cause this problem to happen. Now i must ask, are you temp booting twrp or is twrp installed to phone.
Click to expand...
Click to collapse
Now i am booting from temp twrp, before that i got the latest twrp installed
Bringing this back up... Did booting from temp twrp work? Ran into the same issue.
Temp boot and use the usb c to pull ur data from the device to a computer. After that you can wipe and start over. Unbricking guide available in the help section
Having the same issue. If I boot using fastboot TWRP I'm able to decrypt data. I did that and flashed stock OOS and the same TWRP version (BluSpark) that was used in the fastboot. But the folders are still encrypted. It's weird how a fastboot can decrypt it but a regular recovery boot can't. Is there any alternatives available?
I'm in the process of backing up my data before I officially bite the bullet.
spartan268 said:
Having the same issue. If I boot using fastboot TWRP I'm able to decrypt data. I did that and flashed stock OOS and the same TWRP version (BluSpark) that was used in the fastboot. But the folders are still encrypted. It's weird how a fastboot can decrypt it but a regular recovery boot can't. Is there any alternatives available?
I'm in the process of backing up my data before I officially bite the bullet.
Click to expand...
Click to collapse
Only way i know to get rid of this by removing the encryption on the data is to Format the Internal Storage !
Totone56 said:
Only way i know to get rid of this by removing the encryption on the data is to Format the Internal Storage !
Click to expand...
Click to collapse
That's what I did in the end. I just backed up my media through fastboot TWRP beforehand. Beats having to use the download tool at least
spartan268 said:
That's what I did in the end. I just backed up my media through fastboot TWRP beforehand. Beats having to use the download tool at least
Click to expand...
Click to collapse
Probably the best way indeed. I think i'm gonna start disabling forced encryption to stop these kind of problems.
Totone56 said:
Probably the best way indeed. I think i'm gonna start disabling forced encryption to stop these kind of problems.
Click to expand...
Click to collapse
How to do it? I tried with zero luck
starche_old said:
How to do it? I tried with zero luck
Click to expand...
Click to collapse
I haven't tried yet, don't know for now !
Hi guys
I was trying some of custom rom on my OP6 and I wanted to go back to Oxygen OS. So i did a clean installation with system wipe and i flashed the last full OTA update. But since i can't boot to system anymore, TWRP always displays that there is no OS installed despite the fact that I've tried several rom . Is this the first time it's done this to me how can I fix it?
raptax said:
Hi guys
I was trying some of custom rom on my OP6 and I wanted to go back to Oxygen OS. So i did a clean installation with system wipe and i flashed the last full OTA update. But since i can't boot to system anymore, TWRP always displays that there is no OS installed despite the fact that I've tried several rom . Is this the first time it's done this to me how can I fix it?
Click to expand...
Click to collapse
The best suggestion I can give you is to flash stock oos with TWRP, reboot to stock recovery, without flashing anything else, wipe data from stock recovery and startup system.. if it is working you can flash back TWRP and magisk if you need it
Just be careful because at your point is easy to lose all of your stored data
Hitman478™ said:
The best suggestion I can give you is to flash stock oos with TWRP, reboot to stock recovery, without flashing anything else, wipe data from stock recovery and startup system.. if it is working you can flash back TWRP and magisk if you need it
Just be careful because at your point is easy to lose all of your stored data
Click to expand...
Click to collapse
I tried your solution ..... and it worked thx man
I don't know why there was a problem with TWRP but the important thing is that my phone is alive again
raptax said:
I tried your solution ..... and it worked thx man
I don't know why there was a problem with TWRP but the important thing is that my phone is alive again
Click to expand...
Click to collapse
Exactly! I'm glad to had help you sometimes if something is done wrong TWRP is dangerous
raptax said:
I tried your solution ..... and it worked thx man
I don't know why there was a problem with TWRP but the important thing is that my phone is alive again
Click to expand...
Click to collapse
If you wipe system, then flash oos ROM, TWRP will think there is no os. You can just ignore and boot.
Wiping system then flashing any time will make twrp display "no os installed" it does this because it hasn't created files for twrp to check if you have a ton installed. Flashing twrp then rebooting to twrp fixes it.
Reboot to stock recovery?
Hitman478™ said:
The best suggestion I can give you is to flash stock oos with TWRP, reboot to stock recovery, without flashing anything else, wipe data from stock recovery and startup system.. if it is working you can flash back TWRP and magisk if you need it
Just be careful because at your point is easy to lose all of your stored data
Click to expand...
Click to collapse
Hi, need a little bit of support, since I'm new to this as well. I was in a working OOS open beta 25/28, but then I think I flashed the wrong zip (OOS 9.0.9?), and I was not able to boot to system. It kept going to "bootloader unlocked" screen and custom recovery. Currently in TWRP blu_spark 3.3.1-x v. 9.109, and it's showing me no OS installed when I attempt to reboot. I haven't rebooted to system yet.
All the folders in my /sdcard is gibberish... if I try to push a file to it, it says "Required key not available." I did remove all security/passwords from my phone before doing any updates/backups.
I completed a wipe cache/dalvik/system via TWRP, and flashed the OOS OTA stable Android 10 zip downloaded directly from OnePlus Support. Considering this situation, do you still think it's safe for me to reboot to system? Then how do I get to stock recovery from there--is that by holding down the buttons?
5xonlineage said:
Hi, need a little bit of support, since I'm new to this as well. I was in a working OOS open beta 25/28, but then I think I flashed the wrong zip (OOS 9.0.9?), and I was not able to boot to system. It kept going to "bootloader unlocked" screen and custom recovery. Currently in TWRP blu_spark 3.3.1-x v. 9.109, and it's showing me no OS installed when I attempt to reboot. I haven't rebooted to system yet.
All the folders in my /sdcard is gibberish... if I try to push a file to it, it says "Required key not available." I did remove all security/passwords from my phone before doing any updates/backups.
I completed a wipe cache/dalvik/system via TWRP, and flashed the OOS OTA stable Android 10 zip downloaded directly from OnePlus Support. Considering this situation, do you still think it's safe for me to reboot to system? Then how do I get to stock recovery from there--is that by holding down the buttons?
Click to expand...
Click to collapse
No, your internal storage Is like trash cause the last rom you flashed has older security patch than oos10. Your device Is now encrypted and wont boot to system. I Guess you have to erase all via MSN tool or fastboot signed rom. Even if you wiped what mentioned above, your problem still be the data.
Fastboot method?
°Washy said:
No, your internal storage Is like trash cause the last rom you flashed has older security patch than oos10. Your device Is now encrypted and wont boot to system. I Guess you have to erase all via MSN tool or fastboot signed rom. Even if you wiped what mentioned above, your problem still be the data.
Click to expand...
Click to collapse
Thank you for replying. I'm relieved that you know of a couple methods to try.
Is using "Format Data" in TWRP an option for dealing with the encryption??
For the MSN tool, can I use this one? Tried looking around, but it's unclear. "[TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" https://forum.xda-developers.com/on...wnloadtool-v4-0-international-t3798892/page10
I would be more comfortable with using fastboot, but am I at any risk of having lost fastboot, or can I just turn off my device from TWRP right now and hold down the buttons to get there? Afraid to move out of TWRP right now, in case I can't get back. I do have twrp-3.3.1-18-enchilada-Q-mauronofrio.img that I can run from fastboot if needed.
By "signed rom," do you mean I can simply flash one of the zips here from fastboot? "[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates" https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Thanks again.
5xonlineage said:
Thank you for replying. I'm relieved that you know of a couple methods to try.
Is using "Format Data" in TWRP an option for dealing with the encryption??
For the MSN tool, can I use this one? Tried looking around, but it's unclear. "[TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" https://forum.xda-developers.com/on...wnloadtool-v4-0-international-t3798892/page10
I would be more comfortable with using fastboot, but am I at any risk of having lost fastboot, or can I just turn off my device from TWRP right now and hold down the buttons to get there? Afraid to move out of TWRP right now, in case I can't get back. I do have twrp-3.3.1-18-enchilada-Q-mauronofrio.img that I can run from fastboot if needed.
By "signed rom," do you mean I can simply flash one of the zips here from fastboot? "[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates" https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Thanks again.
Click to expand...
Click to collapse
I hardbricked my device about 10 times and i was able to recovery It even from a blank screen. Btw format data Will erase all your data but also the internal storage. About fastboot dont be afraid, go under twrp reboot section and reboot to bootloader. Then go under xda op6 guide section and search for mirrors for fastboot rom guide by Mauronofrio. He pushed my ass out the **** a lot of time.
P.s. Sorry but I dunno how to paste a link via xda app. Yes, ik! It's a vert newbie thing.
5xonlineage said:
Thank you for replying. I'm relieved that you know of a couple methods to try.
Is using "Format Data" in TWRP an option for dealing with the encryption??
For the MSN tool, can I use this one? Tried looking around, but it's unclear. "[TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" https://forum.xda-developers.com/on...wnloadtool-v4-0-international-t3798892/page10
I would be more comfortable with using fastboot, but am I at any risk of having lost fastboot, or can I just turn off my device from TWRP right now and hold down the buttons to get there? Afraid to move out of TWRP right now, in case I can't get back. I do have twrp-3.3.1-18-enchilada-Q-mauronofrio.img that I can run from fastboot if needed.
By "signed rom," do you mean I can simply flash one of the zips here from fastboot? "[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates" https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Thanks again.
Click to expand...
Click to collapse
Do you solve, man?
Fastboot ROM
°Washy said:
I hardbricked my device about 10 times and i was able to recovery It even from a blank screen. Btw format data Will erase all your data but also the internal storage. About fastboot dont be afraid, go under twrp reboot section and reboot to bootloader. Then go under xda op6 guide section and search for mirrors for fastboot rom guide by Mauronofrio. He pushed my ass out the **** a lot of time.
P.s. Sorry but I dunno how to paste a link via xda app. Yes, ik! It's a vert newbie thing.
Click to expand...
Click to collapse
That's awesome, I'm starting to grasp how much of a genius Mauronofrio is, after so many people referencing his work.
In his guide, he says, "These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie." This may be a dumb question, but how do I know which zip/OOS version to flash, when I don't have a functioning OS on my phone?
5xonlineage said:
That's awesome, I'm starting to grasp how much of a genius Mauronofrio is, after so many people referencing his work.
In his guide, he says, "These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie." This may be a dumb question, but how do I know which zip/OOS version to flash, when I don't have a functioning OS on my phone?
Click to expand...
Click to collapse
I talked with Mauronofrio in pm and he said me that you could solve your issue simply flash the ROM you want and format data after flash that one. Remember that your internal will be wiped but it would happen in any scenario we talked.
Magisk, boot img?
°Washy said:
I talked with Mauronofrio in pm and he said me that you could solve your issue simply flash the ROM you want and format data after flash that one. Remember that your internal will be wiped but it would happen in any scenario we talked.
Click to expand...
Click to collapse
That worked! And starstruck that you were able to check that with him. I flashed Mauronofrio's fastboot ROM for 10.3.2 and it rebooted (WOW). I clicked through the Google setup pages and checked that my data and wifi worked.
I then went back into fastboot, booted M's twrp img, fomatted data, and then installed twrp-3.3.1-x_blu_spark_v9.109_op6.zip, rebooted into recovery.
Then I think I made a mistake, because I installed Magisk-v20.4.zip. It succeeded, but now I can't boot into system anymore. Is it too late to flash the 10.3.2 boot.img?
5xonlineage said:
That worked! And starstruck that you were able to check that with him. I flashed Mauronofrio's fastboot ROM for 10.3.2 and it rebooted (WOW). I clicked through the Google setup pages and checked that my data and wifi worked.
I then went back into fastboot, booted M's twrp img, fomatted data, and then installed twrp-3.3.1-x_blu_spark_v9.109_op6.zip, rebooted into recovery.
Then I think I made a mistake, because I installed Magisk-v20.4.zip. It succeeded, but now I can't boot into system anymore. Is it too late to flash the 10.3.2 boot.img?
Click to expand...
Click to collapse
No. Just flash stock boot image if magisk broke something.
Rooted
°Washy said:
No. Just flash stock boot image if magisk broke something.
Click to expand...
Click to collapse
I ended up following the guide to Magisk Root without TWRP for OnePlus 6 Oxygen OS https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853 since it was referenced by Mauronofrio's post for having issues getting his TWRP to work with latest Magisk.
Someone posted a patched boot.img for 10.3.2, so now I'm rooted without TWRP. Priorities. Now all I need is for special characters and emojis to work Will keep an eye on other threads.
I'm learning a lot, thanks so much for all your help. You pointed me in the right direction when I was not sure what the hell to do!
5xonlineage said:
I ended up following the guide to Magisk Root without TWRP for OnePlus 6 Oxygen OS https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853 since it was referenced by Mauronofrio's post for having issues getting his TWRP to work with latest Magisk.
Someone posted a patched boot.img for 10.3.2, so now I'm rooted without TWRP. Priorities. Now all I need is for special characters and emojis to work Will keep an eye on other threads.
I'm learning a lot, thanks so much for all your help. You pointed me in the right direction when I was not sure what the hell to do!
Click to expand...
Click to collapse
I followed that thread for the first A10 release cause there wasn't a worked twrp yet. You are welcome man, when I feel myself usefull I always try to help.