I finally unlocked my bootloader todaye and tried to flash Crdroid following the Munchy youtube tutorial as well as the instructions on the Crdroid forum post.
I've used TWRP 3.9 skkk and the Crdroid build from 28/07/22. Everything was going as planned until i rebooted back in to recovery after flashing the Crdroid ROM. I went to try and flash Gapps and Magisk but no I longer had access to the phones internal storage even though I flashed the ROM from my internal storage. I plugged in my USB stick which also had the Gapps and Magisk files and I flashed them without any errors and then rebooted again.
After rebooting I cant even select internal storage, it stays "stuck" on OTG storage and the internal storage is reported to be "0mb". See picture here (I had unplugged the USB stick before taking this picture).
I decided to try and format data but that was unsuccessful, presumably because there's nothing to format!! Please see picture here.
I followed the Munchy tutorial carefully whilst also reading the Crdroid instructions so I really dont know what I did wrong and i'm now just hoping I haven't bricked my phone as its not even 2 weeks old.
I'd be really grateful for some help.
Go back to stock (without locking bootloader) then follow the first time installation instructions in the crdroid thread
So you had crDroid working, and when you've simply booted into TWRP SKKK, you didn't see the Internal Storage? After flashing GApps or...?
Have you used DFE ?
Are you still able to boot the system?
cyanGalaxy said:
So you had crDroid working, and when you've simply booted into TWRP SKKK, you didn't see the Internal Storage? After flashing GApps or...?
Have you used DFE ?
Are you still able to boot the system?
Click to expand...
Click to collapse
I flashed crDroid without any errors but I never attempted to actually boot in to it, i rebooted back in to recovery after flashing the ROM and when i tried to flash Gapps i realised that something had messed up the internal storage.
I have actually managed to fix the problem using the 'repair file system' option in TWRP. I still dont know why things got messed up in the first place though.
use usb otg to install gapps and magisk from that usb.
if you dont have a usb otg, you can use adb sideload
We have the same issue, but I managed to fix it by using the previous version of TWRP 3.6.0 from SKKK and the version you're referring to version of TWRP 3.9.0 is still buggy for now on alioth/aliothin devices.
TWRP SKKK doesn't seem to be all that reliable. :S
Goooober said:
I flashed crDroid without any errors but I never attempted to actually boot in to it, i rebooted back in to recovery after flashing the ROM and when i tried to flash Gapps i realised that something had messed up the internal storage.
I have actually managed to fix the problem using the 'repair file system' option in TWRP. I still dont know why things got messed up in the first place though.
Click to expand...
Click to collapse
Lol so you had a working ROM but got scared...
When u format data + flash new system u lose access to data untill phone boots for the first time - Rebooting recovery at this point let's you flash gapps from external storage/pc to second slot - But magisk can't be flashed before the phone boots , it will say flashed and all but when you boot the phone magisk won't be there
Instead flash gapps then boot the phone , give it few mins to set everything up then reboot twrp and install magisk.
I don't recommend skk when nebrasy twrp exists
What the **** does "SKKK" mean anyway?
Did the dev's cat's paw land on the keyboard?
Goooober said:
I finally unlocked my bootloader todaye and tried to flash Crdroid following the Munchy youtube tutorial as well as the instructions on the Crdroid forum post.
I've used TWRP 3.9 skkk and the Crdroid build from 28/07/22. Everything was going as planned until i rebooted back in to recovery after flashing the Crdroid ROM. I went to try and flash Gapps and Magisk but no I longer had access to the phones internal storage even though I flashed the ROM from my internal storage. I plugged in my USB stick which also had the Gapps and Magisk files and I flashed them without any errors and then rebooted again.
After rebooting I cant even select internal storage, it stays "stuck" on OTG storage and the internal storage is reported to be "0mb". See picture here (I had unplugged the USB stick before taking this picture).
I decided to try and format data but that was unsuccessful, presumably because there's nothing to format!! Please see picture here.
I followed the Munchy tutorial carefully whilst also reading the Crdroid instructions so I really dont know what I did wrong and i'm now just hoping I haven't bricked my phone as its not even 2 weeks old.
I'd be really grateful for some help.
Click to expand...
Click to collapse
happend with my dad's phone wipe userdata from xiaomiADB/Fastboot Tools watched countless indian videos to fix it
Related
Sorry this is the wrong board-- i reposted on Help&Trouble shooting, I don't know how to delete the thread
I tried flashing an old, alpha, version of sailfish on my phone and since then it's been bootlooping. I can access the recovery and install CM11 but after booting it restarts, every 1-2 minutes. Flashing some other roms gives me bootloops (First boot takes >1 minute, the phone resets).
I've already backed up all my data and wiped internal and external storage, but flashing gives me the same problems.
What can I do? I have the latest TWRP installed
Have you install the Firmware for Redmi 1s by Xiaomi ?
1. install firmware
2. install rom, gapps etc
3. reboot
Deivid_ said:
Sorry this is the wrong board-- i reposted on Help&Trouble shooting, I don't know how to delete the thread
I tried flashing an old, alpha, version of sailfish on my phone and since then it's been bootlooping. I can access the recovery and install CM11 but after booting it restarts, every 1-2 minutes. Flashing some other roms gives me bootloops (First boot takes >1 minute, the phone resets).
I've already backed up all my data and wiped internal and external storage, but flashing gives me the same problems.
What can I do? I have the latest TWRP installed
Click to expand...
Click to collapse
if the above method dont work then try to flash fastboot rom
It was the firmware. I'd never flashed firmware with other phones and neither needed it with other roms. Thanks
Deivid_ said:
Sorry this is the wrong board-- i reposted on Help&Trouble shooting, I don't know how to delete the thread
I tried flashing an old, alpha, version of sailfish on my phone and since then it's been bootlooping. I can access the recovery and install CM11 but after booting it restarts, every 1-2 minutes. Flashing some other roms gives me bootloops (First boot takes >1 minute, the phone resets).
I've already backed up all my data and wiped internal and external storage, but flashing gives me the same problems.
What can I do? I have the latest TWRP installed
Click to expand...
Click to collapse
first of use latest twrp recovery
then wipe everything that you can see(if i say everything then i mean it)
put the latest cm 13.0 zip and gapps to your sd card and
flash both of these and then enjoy
Phuclun510 said:
Have you install the Firmware for Redmi 1s by Xiaomi ?
Click to expand...
Click to collapse
where i can find that firmwire??
savior** said:
where i can find that firmwire??
Click to expand...
Click to collapse
It's in the second or third post of the Cyanogenmod threads in the ORIGINAL DEVELOPMENT subforum.
Already install fastboot rom? these a link http://en.miui.com/thread-14641-1-1.html
Hi Guys,
I installed TWRP in my Mi Max (32GB) (locked BL) yesterday by replacing stock recovery.img with twrp image and flashing that miui8 dev build through MiFlash in EDL mode. After that my total space was showing nearly 8GB.
To mention, I followed all steps properly like clearing dalvik and cache as well as formatting system, data, internal mem but the same happened.
Again I completely removed mods and installed stock, 24GB space was regained. But now when this time also I installed Resurrection Remix CM13 in the same way as no other way worked for locked BL and unlocking bug has really frustrated me, same thing happened.
Somebody please take up this issue and help me. I wonder how people who installed CM13 RR on locked BL are not facing this issue..
hi karanhv post ur question in q&a forum that way more people will be able to respond to u . anyways from what i gathered ur trying to install global developer build over the global stable that came with ur phone so that u could unlock ur device so that u could flash custom rom like cm or rr . good news is that u can do that without unlocking ur bootloader just follow this guide here from step 1-17 : http://forum.xda-developers.com/mi-max/how-to/guide-install-global-miui8-root-t3435594 . just substitute the rom with cm or rr(personally tested by me on global dev rom.)
but things get a bit tricky if u want to stay on stock miui but want to have a custom recovery and root.skip steps 12,13,14,15. and go thru steps 16 & 17.now u will have stock miui with twrp recovery . now if u want to update the stock miui.go to updater app> click the 3 dot button on upper rt side> click on "download update" > the update will downloaded to "downloaded_rom" folder in ur internal storage.now boot to twrp recovery by switching of phone & switching it on again this time holding the vol+ button while it boots up.now after u boot into twrp recovery ,install the zip file that has been downloaded in the "downloaded rom" folder,immidiately after the install,flash supersu zip.now dont reboot yet, using TWRP's file manager navigate to system folder and delete file named "recovery from boot" and then reboot into system thus u will be updated on stock miui while still retaining root and twrp recovery. hope this clears up for u .if u follow all these steps u wont be faced with any memory loss
easy solution
karanhv said:
Hi Guys,
I installed TWRP in my Mi Max (32GB) (locked BL) yesterday by replacing stock recovery.img with twrp image and flashing that miui8 dev build through MiFlash in EDL mode. After that my total space was showing nearly 8GB.
To mention, I followed all steps properly like clearing dalvik and cache as well as formatting system, data, internal mem but the same happened.
Again I completely removed mods and installed stock, 24GB space was regained. But now when this time also I installed Resurrection Remix CM13 in the same way as no other way worked for locked BL and unlocking bug has really frustrated me, same thing happened.
Somebody please take up this issue and help me. I wonder how people who installed CM13 RR on locked BL are not facing this issue..
Click to expand...
Click to collapse
I had the same problem with 64gb version.
In twrp go to wipe
Click option to delete data partition
It will tell you all data will be deleted and encryption disabled.
After data partition gets deleted twrp will report proper internal space, and ROM will also report proper internal space.
Be sure to backup everything before.
So as the title says, after flashing cm14. 1 can't go into recovery anymore, it just a black screen. I tried to use flashify but nothing, a couple of apps show that I have twrp 3.0.2.1 but can't get into it... Help?
Cheers
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Which thread is this from please?
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Yeah man im in the same boat, if i get time ill try this twrp recovery. Where did that recovery come from?, it seems like the CM recovery for 14.1 nightly high jacks the recovery partition (i call it that,i dont know the term for it)
Sent from my ONEPLUS A3000 using Tapatalk
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Hw4ng3r said:
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Click to expand...
Click to collapse
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Thanks a lot guys, that did the trick, and done with flashify
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
@JKMB888 it does work 100% is as simple as flashing the TWRP. Actually, i installed it with CM 14.1 running just fine
Sent from my ONEPLUS A3000 using Tapatalk
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Edit: I found the solution, i had a pattern lock screen and i removed it!
HC4Life said:
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Click to expand...
Click to collapse
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
GrandMasterB said:
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
Click to expand...
Click to collapse
Look at my edited reply...
m4manusraj said:
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Click to expand...
Click to collapse
actually flashify did the trick for me as I had no access to a pc for the time
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
i am facing just the same situation with cm14.1 nightly and can't boot into recovery
i tried flashing the recovery image provided by you i.e. twrp-3.0.2-22-oneplus3.img but i face the same problem again
when i go into the recovery all i see is a black screen with a white notification light on and it remains there untill i switch off my phone manually using the power button
i tried facing the problem when i installed the cm14.1 nightly
i was unable to login snapchat as i device was rooted as said by the message on snapchat
so i decided to unroot my device via supersu FULL UNROOT option
after a reboot i successfully logged into snapchat
then i tried to root it again
i went into recovery to flash the supersu zip
and since then i have been unable to see the twrp recovey
please help me
This thread is a life save. Tried everything and it drove me nuts not getting into recovery.
THANK YOU!
gangangan2 said:
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
Click to expand...
Click to collapse
Thank you so much it's work for me now..
After I got the recovery back, I flashed CM13 again and ARM64 6.0 Nano Gapps for my Oneplus 3, but I'm getting an error after the "preparing apps' screen is loaded saying that - unfortunately the process android.process.media has stopped one plus 3 boot and then the phone switches off.
Any solution to this? I've already tried flashing different versions of CM13.
Thank you!! I was looking for hours.
This link fixed the problem!
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Hey, guys. I'm pretty sure I bricked my phone and there's no way to get out.
So I was on CM13 official builds on my OP3. Then, on the OTA update system they have, I got moved onto the CM14.1. I downloaded from here and went into my twrp recovery to flash. I made a clean flash and then proceeded to go back to system. I thought everything was ok until I realised I hadn't flashed a gapps package which I pretty much need to survive as all my contacts backups etc. are on there. I powered off my phone and went to go back into the recovery after downloading gapps 7.1 micro. It went past the *You're device can not be trusted'* and then went to the oneplus screen. After that, it stayed like that for about 30 secs and powered off. At first, I thought I messed something up and tried again. I repeated that for about 3 times and it didn't work. I tried going into the normal system and coming back to recovery and it didn't work still. In fact, now I can't even get into system. Now, i can only boot up to fastboot, where my computer still doesn't realise my phone is plugged in.
Anyone got any ideas on how to fix this? I wouldn't say I'm a noob at this because I have flashed many times before but I'm relatively new to the scene. I didn't see this thread before i ripped my hair out and i think wrecked my phone @JKMB888
EDIT: I sorted it out with help from Naman Bhalla's unbrick thread and this. A certain combo works and now I'm on CM14.1 enjoying life
Hi, so recently my HTC One X has been acting up so I decided to install a ROM to make it much faster, so I had to unlock the bootloader. When i've done that I flashed CWM on my device. Then I tried to install a rom that was on the device and it didn't install which leads me to my first problem, the page said I needed to reset everything and use the fastboot command to flash the zip file that worked but when I went to CWM (to install gapps) the device never booted in the ROM just kept going back to CWM. So I googled this and there was multiple things I tired out like adb command etc also it would be easier if this problem was fixed if this button worked (mount USB storage) I press that and it does not work. So then I don't know what to do. I'm stuck here please help me the rom was cm-11-20160815-NIGHTLY-endeavoru.zip.
swarby2 said:
Hi, so recently my HTC One X has been acting up so I decided to install a ROM to make it much faster, so I had to unlock the bootloader. When i've done that I flashed CWM on my device. Then I tried to install a rom that was on the device and it didn't install which leads me to my first problem, the page said I needed to reset everything and use the fastboot command to flash the zip file that worked but when I went to CWM (to install gapps) the device never booted in the ROM just kept going back to CWM. So I googled this and there was multiple things I tired out like adb command etc also it would be easier if this problem was fixed if this button worked (mount USB storage) I press that and it does not work. So then I don't know what to do. I'm stuck here please help me the rom was cm-11-20160815-NIGHTLY-endeavoru.zip.
Click to expand...
Click to collapse
CWM was abandoned a long time ago in the community so it won't cope with the instructions modern roms use. Its a bit sad that CWM came to a such sudden end I kind of miss the different recoveries based on it. Not to mention philz touch recovery..
Anyway go here: (its a twrp recovery) http://forum.xda-developers.com/htc-one-x/orig-development/storage-layout-hox-endeavoru-t3022358
Read the instructions and flash the provided .img file and your phone should be up and running within the hour.
Edit: I'm not sure if that rom uses the new or old layout. The documenation is more than a bit poor because the device info is outdated on the cyanogenmod wiki. Last edited in year 2012..
https://wiki.cyanogenmod.org/w/Endeavoru_Info
If the rom will not flash with the new layout recovery provided above.
Read instrutions how to revert to old layout first. And flash this older recovery from here:
https://dl.twrp.me/endeavoru/
SÜPERUSER said:
CWM was abandoned a long time ago in the community so it won't cope with the instructions modern roms use. Its a bit sad that CWM came to a such sudden end I kind of miss the different recoveries based on it. Not to mention philz touch recovery..
Anyway go here: (its a twrp recovery) http://forum.xda-developers.com/htc-one-x/orig-development/storage-layout-hox-endeavoru-t3022358
Read the instructions and flash the provided .img file and your phone should be up and running within the hour.
Edit: I'm not sure if that rom uses the new or old layout. The documenation is more than a bit poor because the device info is outdated on the cyanogenmod wiki. Last edited in year 2012..
https://wiki.cyanogenmod.org/w/Endeavoru_Info
If the rom will not flash with the new layout recovery provided above.
Read instrutions how to revert to old layout first. And flash this older recovery from here:
https://dl.twrp.me/endeavoru/
Click to expand...
Click to collapse
Really? Didn't realise that... Im trying to charge my phone because I can't flash it because the battery is too low. So thanks for telling me. I will post when Ive flashed it to my phone. When you flash it dosen't get rid of all the roms that's already on the phone? Because I cant access the phone within usb but does this recovery solve that? Like mount usb storage like in CWM?
swarby2 said:
Really? Didn't realise that... Im trying to charge my phone because I can't flash it because the battery is too low. So thanks for telling me. I will post when Ive flashed it to my phone. When you flash it dosen't get rid of all the roms that's already on the phone? Because I cant access the phone within usb but does this recovery solve that? Like mount usb storage like in CWM?
Click to expand...
Click to collapse
Flashing the recovery will not wipe anything except the recovery partition obviously. When you boot to twrp you will be able to access the internal storage by going to Mount and press the Mount usb storage twice. And the one x should be detected on your pc.
But when you're done with the backup you will wipe all partitions with the Format data option as described in the thread I linked yesterday. So backup all important data to your computer.
Thank you so much! I'm up and running!
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