Related
Is there any way to wipe everything non-stock (including supersu systemless, xposed, etc) from fasboot, without being able to enter recovery?
The normal cache, boot, bootloader, radio, recovery, vendor partitions can be flashed over, and flashing the userdata.img after erasing it in theory wipes /data/sdcard/0/ (or however it's called now). However, what about the other changes systemless supersu, xposed and other mods may have done? for example, supersu's partition would stay? How could I literally reset all this to pure stock?
Thanks!
RusherDude said:
Is there any way to wipe everything non-stock (including supersu systemless, xposed, etc) from fasboot, without being able to enter recovery?
The normal cache, boot, bootloader, radio, recovery, vendor partitions can be flashed over, and flashing the userdata.img after erasing it in theory wipes /data/sdcard/0/ (or however it's called now). However, what about the other changes systemless supersu, xposed and other mods may have done? for example, supersu's partition would stay? How could I literally reset all this to pure stock?
Thanks!
Click to expand...
Click to collapse
Uninstall Xposed first. Now enter the bootloader and fastboot flash boot (to remove SuperSU) then fastboot flash system (to remove SuperSU and Xposed modifications in /system). That's it. Please use the factory image that matches your stock rom.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Uninstall Xposed first. Now enter the bootloader and fastboot flash boot (to remove SuperSU) then fastboot flash system (to remove SuperSU and Xposed modifications in /system). That's it. Please use the factory image that matches your stock rom.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks for the fast reply!
My problem is that I didn't disable Xposed before the problem happened, and now I can't entery recovery. I am with a bootlooping phone that can only enter fastboot (and even so sometimes crashes there), impossible to boot or enter recovery by all means (even after flashing stock recovery) .
After flashing the stock boot and system (and all others) partitions, SuperSU should be completely gone, but Xposed? If I wasn't able to disable it before, it would be hooking app_process and more stuff, but would this stuff be overwritten by the new boot and system?
Thanks a lot!! :good:
RusherDude said:
Thanks for the fast reply!
My problem is that I didn't disable Xposed before the problem happened, and now I can't entery recovery. I am with a bootlooping phone that can only enter fastboot (and even so sometimes crashes there), impossible to boot or enter recovery by all means (even after flashing stock recovery) .
After flashing the stock boot and system (and all others) partitions, SuperSU should be completely gone, but Xposed? If I wasn't able to disable it before, it would be hooking app_process and more stuff, but would this stuff be overwritten by the new boot and system?
Thanks a lot!! :good:
Click to expand...
Click to collapse
Yes, both are removed when you flash those files. Xposed modules would still be installed but you can uninstall those in Android. What did you do to bootloop?
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Yes, both are removed when you flash those files. Xposed modules would still be installed but you can uninstall those in Android. What did you do to bootloop?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Nothing. I hadn't flashed anything since august lol.. i was setting up an alarm and it froze and since then bootloop and freezes on every screen (including orange warning from bootloader unlocked, google logo, start of bootanimation, fastboot, recovery (when by miracle it shows the first image or stock one for a frame..) and even the charging animation when trying to charge it offline crashes).
I have talked with a google rep and she menaced me with warranty void if the device software was not original, lol?? on a nexus? on Europe when software modifications can't void a hardware problem warranty?? is this normal on Google? I know people that in the past sent devices even rooted booting normally and there was no problem, I don't know if something changed with the Pixel approach now... the only semi-stable boot mode is fastboot, most of the time it boots with the hardware combination keys and only sometimes crashes, most of the time lets you flash stuff with no problem.
I have flashed all the stock partitions (including erasing userdata and flashing userdata from the factory images..) and I don't know if I should lock the bootloader or just send it unlocked like I told them I had lol..
Hi all! I updated the phone to the OxygenOS Open Beta 7 through the instructions one the OnePlus website. I made sure to remove the screen lock before I started flashing and stuff, and I also made a TWRP backup, to be able to restore if anything goes wrong.
Well, now when I boot the phone, I get a message that the phone could not be decrypted and I need to reset it. When I go to stock recovery it asks me for a password. And when I flash and go to TWRP recovery it cannot see my sd card since it is encrypted. What should I do? Any help is appreciated!
Did you have set a pin password before ? if yes use the last one that you may have used
I had twrp recovery and couldn't decrypt.
See if you can try the instructions in the link
http://forum.xda-developers.com/showpost.php?p=69389114&postcount=3
I am at the same point now .. did you solve your problem? dont wanna wipe my data!
pidl said:
I am at the same point now .. did you solve your problem? dont wanna wipe my data!
Click to expand...
Click to collapse
You are in encrypting state, you lost all your data (internal included) at this point. just reflash and decrypt it, you'll just be fine, your data is lost tho.
Always remember to flash SuperSU or Magisk to patch your boot.img after flashing a full rom or before booting it to avoid encryption process like this
Rizezky said:
You are in encrypting state, you lost all your data (internal included) at this point. just reflash and decrypt it, you'll just be fine, your data is lost tho.
Always remember to flash SuperSU or Magisk to patch your boot.img after flashing a full rom or before booting it to avoid encryption process like this
Click to expand...
Click to collapse
Is there no way to somehow backup that data?
If you are still stuck, here is what i did and got rid of password, go to setting remove old pin, set the new one, root your device through ADB SIDELOAD reboot to recovery and enter the new pin, it should work
Fingers crossed
Hi, i have a xiaomi mi 6. The bootloader is unlocked, officially.
My question is: can i relock the bootloader after i moved two apps as a system apps? The applications only work that way, or with root privileges. Those two app is needed to enable or disable android services.
I use banking apps, which detect rooted or unlocked phones. Safetynet need to
pass. Keeping root or magisk is not an option for me. Beside safetynet, those banking apps have their own custom detecting sistem, which magisk can't hide.
I have stock recovery now , root is removed (unrooted).
On my old sony z3 that procedures worked, dose is work on mi 6 too? Or it will brick the device.? A bricked device with locked bootloader is a nightmare...
I want a locked bootloader to be able to use fingerprint and use all of my banking apps. But i need to enable/disable services at any time.
Hi,
From what I heard, if you relock the bootloader, you won't be able to unlock it again as xiaomi won't give you the right to unlock phone twice. So it's a bad idea.
Lork Scorguar said:
Hi,
From what I heard, if you relock the bootloader, you won't be able to unlock it again as xiaomi won't give you the right to unlock phone twice. So it's a bad idea.
Click to expand...
Click to collapse
Thanks for replying.
If you get permission to unlock officially, you cand unlock and relock as many times as you want.
Absolutely not. If you made a modification of the system, dm-verity will notice it, and the phone will be stuck in a bootloop.
Boot in custom recovery and move the app in system.. You dont need root for that. Just un-encrypted phone and TWRP.
Main problem will be, how you get the files from the apk. You could install it on another phone (which is rooted), make the app a system app and then get the folders of said app, which you can copy via adb to your Mi6. And in recovery mode you can mount system as rw.
OR
TWRP has a feature to make any app a system app (dunno)
OR
someone can make you flashable zip file for TWRP.
thE_29 said:
Boot in custom recovery and move the app in system.. You dont need root for that. Just un-encrypted phone and TWRP.
Main problem will be, how you get the files from the apk. You could install it on another phone (which is rooted), make the app a system app and then get the folders of said app, which you can copy via adb to your Mi6. And in recovery mode you can mount system as rw.
OR
TWRP has a feature to make any app a system app (dunno)
OR
someone can make you flashable zip file for TWRP.
Click to expand...
Click to collapse
Thanks man, but converting app to system app is not a problem. I can do that with root or with twrp, as you mentioned.
The problem is relocking the bootloader after i moved app as a system app and disabled some services.
G4B33 said:
Absolutely not. If you made a modification of the system, dm-verity will notice it, and the phone will be stuck in a bootloop.
Click to expand...
Click to collapse
Will dm-verity prevent my phone from booting if i flash no-dm-verity patch or disable dm-verity from twrp?
After i disabled it, flash stock recovery and relock?
After a bit of trial and error, I managed to find a combination of files and actions that allowed me to successfully root my 64GB Pixel C on 8.0.0 by installing SuperSU via TWRP.
Steps:
Perform a clean installation of the official release, found here
Use the unofficial 3.0.0 TWRP release found in this thread (direct download link here) and boot to recovery ("fastboot boot [TWRP filename].img") - the latest official 3.1.1 TWRP did not work, either via flashing or booting
ADB sideload SuperSU 2.82SR3 found in this thread (direct download link here)
Hope this helps!
Stuck at TWRP after
Flashed the TWRP from the link and side loaded the SuperSU, now my Pixel C is stuck at TWRP on reboot, any idea ?
Jeff Z. said:
Flashed the TWRP from the link and side loaded the SuperSU, now my Pixel C is stuck at TWRP on reboot, any idea ?
Click to expand...
Click to collapse
The only thing I can think of is to reflash the stock recovery using the downloaded factory image. Seems like it was flashed, not simply booted into TWRP.
Sent from my Pixel XL using Tapatalk
MadManMoon said:
The only thing I can think of is to reflash the stock recovery using the downloaded factory image. Seems like it was flashed, not simply booted into TWRP.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Thanks. My problem was my pixel kept booting to TWRP even selecting to boot the system, kind of strange. I think I missed your first step, the pad was OTA updated to 8.0 from 8.0 Beta release. I will try again with flash the factory image of 8.0 first.
Anyone else able to root their pixel c tablet on Oreo with success? I'm thinking about trying it with the original posters guide. Just thought I'd see who else has been able to make this work.
NitroSS said:
Anyone else able to root their pixel c tablet on Oreo with success? I'm thinking about trying it with the original posters guide. Just thought I'd see who else has been able to make this work.
Click to expand...
Click to collapse
Still works for me as of the September 2017 update. About to try it again with the October update.
It's driving me absolutely mad. I just got a brand new Pixel C today. It's updated to the latest Oreo but nothing else has been installed yet. I unlocked the bootloader and copied the SuperSU zip file onto the device via USB file transfer from my PC, then I set up a password. I'm booting (not flashing) TWRP because all I want is root.
When I'm prompted for a password in TWRP I'm told it's invalid. I also tried "default_password" and that's invalid, too. I looked all over for a solution and found a modified TWRP that doesn't prompt for a password but it won't decrypt the internal storage.
I'm really pulling my hair out here. I can't figure out why it's working for some people and not others.
CatThief said:
It's driving me absolutely mad. I just got a brand new Pixel C today. It's updated to the latest Oreo but nothing else has been installed yet. I unlocked the bootloader and copied the SuperSU zip file onto the device via USB file transfer from my PC, then I set up a password. I'm booting (not flashing) TWRP because all I want is root.
When I'm prompted for a password in TWRP I'm told it's invalid. I also tried "default_password" and that's invalid, too. I looked all over for a solution and found a modified TWRP that doesn't prompt for a password but it won't decrypt the internal storage.
I'm really pulling my hair out here. I can't figure out why it's working for some people and not others.
Click to expand...
Click to collapse
Try format userdata, then boot straight into twrp
Command is "fastboot format userdata"
You also have to flash SuperSU while in twrp to stop the tablet from encrypting again.
Huffy1 said:
Try format userdata, then boot straight into twrp
Command is "fastboot format userdata"
You also have to flash SuperSU while in twrp to stop the tablet from encrypting again.
Click to expand...
Click to collapse
I'm confused about "stop the tablet from encrypting again". I know TWRP needs to decrypt the data partition to access it, but are you saying encryption won't be re-enabled when I reboot the system? I had to ask because it sounds strange that installing the SuperSU zip would mess with encryption.
CatThief said:
I'm confused about "stop the tablet from encrypting again". I know TWRP needs to decrypt the data partition to access it, but are you saying encryption won't be re-enabled when I reboot the system? I had to ask because it sounds strange that installing the SuperSU zip would mess with encryption.
Click to expand...
Click to collapse
If everything goes to plan yes.
You can encrypt again if you wish through settings once the tablet is booted up
Huffy1 said:
If everything goes to plan yes.
You can encrypt again if you wish through settings once the tablet is booted up
Click to expand...
Click to collapse
Does this mean when I flash the factory images for the monthly updates and need to root the device again that I'll be wiping all userdata each time?
CatThief said:
Does this mean when I flash the factory images for the monthly updates and need to root the device again that I'll be wiping all userdata each time?
Click to expand...
Click to collapse
No just use flashfire to update and keep root, it won't encrypt the tablet. You can still boot official twrp as well after using flashfire to update as your tablet shouldn't encrypt.
Huffy1 said:
No just use flashfire to update and keep root, it won't encrypt the tablet. You can still boot official twrp as well after using flashfire to update as your tablet shouldn't encrypt.
Click to expand...
Click to collapse
Is removing encryption something everyone is doing, or is it just a workaround for the people who can't get TWRP to work? I never ran into anything like this before.
CatThief said:
Is removing encryption something everyone is doing, or is it just a workaround for the people who can't get TWRP to work? I never ran into anything like this before.
Click to expand...
Click to collapse
Use FDE then and it reportedly works.
Huffy1 said:
Use FDE then and it reportedly works.
Click to expand...
Click to collapse
Just curious though, is this a standard prerequisite for using TWRP and rooting *all* Pixel C devices?
CatThief said:
Just curious though, is this a standard prerequisite for using TWRP and rooting *all* Pixel C devices?
Click to expand...
Click to collapse
Don't know, only telling you what I did cause I had the same problem as you
Well I'm finally rooted. I didn't change the encryption, just tried a different method and after several tries it finally worked. I used adb sideload inside TWRP after canceling the password screen. Odd that it took several tries, though, to get through it without generating errors. We'll see how it goes next month.
I have had a lot of trouble with rooting Oreo...
I started out trying to use Magisk but gave up after many attempts. Every version, and every kernel I tried resulted in booting to recovery and not system. I could have tried the ADB method but I actually want to have TWRP so I didn't try that.
By the time I tried SuperSU my factory image had had an OTA and many apps & files installed so I can't say my system is "clean" but I have Fastboot flashed the stock boot image many (many) times to recover from whatever Magisk does to the kernel. I never looked all that hard for this unofficial TWRP people talk about so I used 3.1.1-1. At some point I converted to File Based Encryption because it is so much nicer to use, and so TWRP cannot decrypt my internal storage, but the workaround is to put zips and images on a USB drive. It also does not ask for a password. So far so good, I have my workarounds. I do also have this weird error where TWRP cannot unmount the system but I can flash kernels without problems. I have chosen to keep system read-only for superstitious reasons. I think it will fail if I look at it funny sometimes lol.
From this state I flashed the latest SuperSU and it booted! So I do have root. I still would like to try Magisk for the modules but it seems this isn't ready. However, my trusty old terminal app hangs at the su command... and several kernels will crash my tablet... so it's "working" but there is more to do. And literally just now I see I have an OTA. lol.
I followed the original instructions and got rooted with the latest version of Oreo. But, TWRP still wouldn't flash correctly without causing boot loops.
I finally got it resolved by using the original instructions, then loading the Official TWRP app from Google Play. I used the app to flash twrp-3.1.1-1-dragon.img.
Everything is working properly now. I have 8.0.0 (OPR1.170623.032, Nov 2017) loaded and rooted, and the Pixel C will boot into TWRP and see the encrypted data.
Is it posible to flash latest Oreo stock factory image https://developers.google.com/android/images ryu-opr1.170623.032-factory-020f1cf9.zip using stock TWRP or do I have to side load it ?
I'm getting a Invalid zip file format error in TWRP when I try and flash it
Hi Everyone,
I need some help. The short of it is that Magisk has put me into a bootloop. Here is what I have done to end up at this point:
1) Attempted to install Magisk v17 when the notification popped up. This failed and then removed root from my phone but the phone was working normally otherwise at this point.
2) Attempted to run the Magisk Uninstaller zip in TWRP. It appeared to run fine.
3) Attempted to run the Magisk v17 zip while still in TWRP right after running the Uninstaller. It appeared to run fine.
4) Attempted to reboot and this is where my real trouble began. I am now stuck in a bootloop.
5) Got back into TWRP
6) Attempted to run the Uninstaller again. This time it fails with an error.
7) I then attempted to boot into bootloader mode. I was able to get there but then running "fastboot devices" shows no phone attached.
I'm at a loss of what to do now and I really don't want to factory reset. Is there anything I can do to get out of this? Any help would be greatly appreciated!
OK so I have since been able to reflash boot.img and I'm now able to boot the phone. Still not sure what to do about getting root back though.
Just install trwp again and flash magisk, I'm running 17.1 with few modules activated and had no problems with the latest updates
SeriousFlash said:
Just install trwp again and flash magisk, I'm running 17.1 with few modules activated and had no problems with the latest updates
Click to expand...
Click to collapse
What about rooting and then unrooting? I want to root my phone to move some apps to system and then unroot my phone. Some of the apps and games I have still detect Magisk even with Magisk Hide and running core only mode.
Any idea?
Oblituarius said:
What about rooting and then unrooting? I want to root my phone to move some apps to system and then unroot my phone. Some of the apps and games I have still detect Magisk even with Magisk Hide and running core only mode.
Any idea?
Click to expand...
Click to collapse
Don't root the phone then and read on how to relock your phone is my personal advice. Had a similar issue with the German skygo app and it was detecting the unlock.
SeriousFlash said:
Don't root the phone then and read on how to relock your phone is my personal advice. Had a similar issue with the German skygo app and it was detecting the unlock.
Click to expand...
Click to collapse
I don't have issue with it detecting that the bootloader is unlocked.
The apps that detected root only detect that part. I even have TWRP still running with the stock image reflashed.
Just want to find a reliable source of how to unroot phone after rooting. I think I know what to do and it is all related to the boot.img
I just have to try it.