Hi,
When attempting to use TWRP recovery with wileyfox's stock rom, I've a few issues.
First of all, TWRP completely fails to mount /system. It thinks it is 0mb, and as such I cannot install apps onto it (e.g. SuperSU).
Secondly, if I were to boot into system, the recovery would be reset back to the original, and I'd have to re-flash TWRP.
Thirdly, if I use the advanced restart to go to recovery, it may flash up saying it is factory resetting the phone. (It isn't, as when I go back into system everything is as it should be)
A few days ago I was using a version of lineage (A few weeks old) just fine. TWRP would stay installed, it would recognize /system and I could install things to it just fine.
I emailed wileyfox's team for a copy of the most up-to-date OEM rom, which is what is giving me the above issues. I did encounter these issues when i first had the phone, hence my switch to lineage. Though i'd like to go back to the original rom and try and fix this if possible.
I did try changing the file system to F2FS which did allow me to mount /system, but the phone chucked itself into a bootloop so I wiped & flashed it.
Does anyone know what file system works best with the wileyfox swift? Maybe this is the answer.
The goal here is to root the phone, if there's another way of doing so without TWRP, then that's ok with me.
I have some images uploaded on an imgur album to show the problem, however I cannot put them in this yet post as I'm a new user.
Related
Hi, I've had my Sprint Galaxy S3 rooted for a while, and it was encrypted. Instead of decrypting it before flashing a new, non-standard rom, I used TWRP to format /data
Now if I install a non-touchwiz rom, it works perfectly. If I try to install ANY version of a touchwiz rom, however, upon the first boot, the phone prompts me for an encryption password. My original password does not work. I have attempted every rom I could find that is labeled "official."
My TWRP backups also do not install, upon reaching the Cache portion of the restore, the process fails, providing no information as to why.
I'd very much like to get my phone back to its original state, if possible. Any help would be greatly appreciated!
Re: [HELP] Can't install official ROM due to encryption
https://www.youtube.com/watch?v=ypmqJbZqOaU&feature=youtube_gdata_player
Sent from my SPH-L710 using Tapatalk 2
KarmaBytes said:
Hi, I've had my Sprint Galaxy S3 rooted for a while, and it was encrypted. Instead of decrypting it before flashing a new, non-standard rom, I used TWRP to format /data
Now if I install a non-touchwiz rom, it works perfectly. If I try to install ANY version of a touchwiz rom, however, upon the first boot, the phone prompts me for an encryption password. My original password does not work. I have attempted every rom I could find that is labeled "official."
My TWRP backups also do not install, upon reaching the Cache portion of the restore, the process fails, providing no information as to why.
I'd very much like to get my phone back to its original state, if possible. Any help would be greatly appreciated!
Click to expand...
Click to collapse
I've never used encryption, but I'd bet there's still some data lingering in the system folder of the internal storage...
First thing I'd recommend is doing a Factory Reset and a System wipe. This is in TWRP under the Wipe Menu. Then try to flash a TW ROM. See if that works.
If the system wipe doesn't work, I'd next recommend a full wipe of your internal storage (of course, you should copy your nandroid backups and anything else you want to keep to your external SDcard first). This is also found under the Wipe Menu in TWRP.
Then you can install whichever ROM you want (from your External SDcard, 'cause it won't be in our internal storage of course).
Let me know if this works for you.
EDIT: My apologies, apparently the Format /data is supposed to do all the above (and more). I'd recommend the approach in GiantJay's link and see if that works.
So, I had tried wiping and formatting everything already, to no avail.
I just used Odin to flash the original firmware from samsung-updates.com, and after the reboot, I STILL get the encryption prompt... I'm completely lost now. And to top it off, I no longer have a custom recovery or anything with which to flash a different rom :/
EDIT: It would appear that after using ODIN to flash the stock firmware, the stock recovery was capable of succeeding where TWRP was unable to. Performing the factory/DATA reset from the stock recovery fixed my problem.
To others encountering this problem, the following worked for my SPH-L710:
1. Boot into download mode.
2. Use ODIN to flash the correct stock firmware (MD5 or TAR file).
3. Boot device into recovery mode and perform a factory reset.
Easy enough lol.
Thanks a lot for your help, and the quick replies!
Re: [HELP] Can't install official ROM due to encryption
Add "[SOLVED]" to your thread title please (edit the post and then it lets you change the title)
Hello, I have a rogers i747 and I installed the newest CM build today and my internal storage would no longer show up. Afterwards I tried to use a recovery in TWRP and now my phone won't install data or system from any files that I try to flash. The phone will go into recovery mode and it will also go into downloading mode but I have no idea what to do. I can't seem to use any of my recoveries or even flash a new ROM onto the phone.
..
Are you entirely sure internal storage is gone? If you didn't know, the storage is nested into an emulate /0 folder. If you can get the phone to boot go ahead and look around in File Manager or Root Explorer for that folder. Everything you had on internal storage should be located there.
Onto the crazier things you're mentioning...
You should only have one "recovery". Unless of course you mean to say backups that you've saved in the event something goes wrong. Unfortunately with some recoveries the blob files for the backup stack up over time and get too large to be restored. I think updating the recovery might fix that, but I never had to mess with any of that stuff. I usually ended up returning to completely stock software to fix the issues I had the first few times I caught problems no amount of wiping would fix.
Before you do anything crazy go ahead and boot into recovery (hold volume up + home button + power until you see the samsung logo and it boots into twrp or cwm depending on what you're using), clear cache, clear dalvik cache in advanced and then reboot system now. Some issues are taken care of by that, some aren't.
Failing that, try a full wipe of your phone and reflashing the ROM assuming your files haven't been corrupted/deleted somehow.
If that doesn't work you'll need to use Odin or Kies or whatever to return to completely stock and reroot and all that nonsense.
Good luck.
I ended up having to flash a stock rom with Odin and it ended up working again. Not sure what happened but none of my backups would load and the phone was saying that storage was in use but the files weren't accessible and the backups wouldn't write to the internal storage they would say successful but do nothing. If I install twrp and try to flash cm again is there a chance that this same issue will occur again? And does anyone have an idea of why this occurred in the first place? I have never had an issue flashing between roms or using recoveries in the past. Just afraid of permanently bricking my phone at this point by installing a custom rom again. Never had issues before the new cm.
Sent from my SGH-I747M using xda app-developers app
Hi,
I'm having some issues with updating CM so I tried to do it via TWRP instead but it cannot mount E: therfor cannot see my internal storage. I cannot wipe anything but fastboot seems to work but I have no used it apart from rooting my phone.
Could someone help me to fix this, I dont care if i wipe my phone to fix this.
Thanks.
Seeing a lot of this: http://i.imgur.com/CRiJdKY.png
I have the same issue. If it is the same issue, the problem is that TWRP thinks Data is encrypted. In my case, it's not and I have never attempted to do so, but following the flashing of any 5.1 ROM (GPE or AOSP-based) TWRP gets this strange idea Data is encrypted.
The solution is to get the RUU, which will wipe your phone. XDA has one for Verizon. Not sure about the others, but they most likely do. The RUU is a zip you rename and stick on your SD card (root directory) and it will automatically flash. Won't wipe the SD card though. It'll leave you stock and rooted. Then you just fastboot oem flash the TWRP recovery (there's a special one that can be flashed via fastboot) and then you can flash whatever, but flashing 5.1 anything will put you right back in the same situation.
You CAN flash 5.1 ROMs, but you can only do so once and then you have to stay there. You won't be able to update the ROM, or flash another 5.1 ROM, unless you wanna RUU first, then re-fastboot flash TWRP, and then flash the update.
It'll probably resolve itself in August when 5.1 comes officially to the M8 and more people start having this problem. I suspect it's a TWRP thing, but I think TWRP is the only recovery we can use. Philz Touch (CWM fork) hasn't been updated in about a year, so I wouldn't trust it to flash newer ROMs. (Generally, I don't trust recoveries that came out before the Android version of the ROM I'm flashing.) And CWM doesn't seem to support anything after ~2013, so I'm not sure what's up with them. But I like TWRP, it looks nice, and before 5.1, it's never done me wrong. I'm not 100% sure it's doing me wrong now, but it seems to be at fault, and there have been a few times, especially with Lollipop, where you have to use a certain version or higher or you run into a lot of red text.
I got my op3 phone loaded up with twrp version 3.0.2-1 but many errors occurred after I flashed this version.
Current problems on my phone right now:
-"The dm-verity is not started in enforcing mode" occurs every time I turn on the phone.
-Twrp won't read any of my files inside the "sdcard" folder wether it's just regular folder, .zip files, and even .img files.
-It also looks like only 1 version works of twrp works on my phone right now since any twrp versions after 3.1.0 causes the twrp program to froze and doesn't completely move past welcome screen of twrp.
I believe I had the same problem. Contact OnePlus on their support page. In a chat support window, tell the operater about your problem, and ask for an appointment with a level 2 technician. They should schedule you an appointment with a technician who should be able to wipe your phone no matter what state/condition it's in. They fixed my phone in a matter of minutes. But PLEASE, try to remember to be respectful and co-operative, it usually gets you better service no matter who you are dealing with.
For dm - verity problem, it's not a problem tough... Just a security breach as seen by Google.
BTW here is the fix...It's easy , follow the thread :
https://forum.xda-developers.com/oneplus-3/how-to/fix-easy-method-removing-dm-verity-t3544339
Can't comment on twrp as I'm on the 3.0.2-1, haven't tried 3.1. Hope it helps, Thanks!
Use TWRP 3.0.4-1. 3.0.2 can't decrypt internal storage, at least not on mine it couldn't.
Also if you have f2fs file system, TWRP takes a loooooong time to boot. Just wait, even though it seems hung. Takes several minutes. If you have ext4, it's quick. Use the app 'Diskinfo' to check
I had TWRP 3.1 and it would not do OTA of lineage, it would wipe the device when I tried and would not restore backed ROMs, stay away from TWRP 3.1. So, i went back to 3.0.4.1 via fastboot. My suggestion is flash the stock recovery from Oxygen 3.8 marshmallow (this can be found in the archived OnePlus 3 tool kit on XDA) and then sideload the stock marshmallow Oxygen 3.2.8 (download from OnePlus support page) and start all over.
mremghz said:
I had TWRP 3.1 and it would not do OTA of lineage, it would wipe the device when I tried and would not restore backed ROMs, stay away from TWRP 3.1. So, i went back to 3.0.4.1 via fastboot. My suggestion is flash the stock recovery from Oxygen 3.8 marshmallow (this can be found in the archived OnePlus 3 tool kit on XDA) and then sideload the stock marshmallow Oxygen 3.2.8 (download from OnePlus support page) and start all over.
Click to expand...
Click to collapse
That doesn't make sense..
The latest recovery works fine here, atleast the official one. If you are in F2fs and encrypted keep in mind it takes a long long time since F2fs is really bad at this.. Depending in how full your internal storage is it can take up to 10 minutesm
Twrp 3.0.4.1 or
3.1.0 x v.26 blu_spark.
To get OTA you need to be stock, only Oos official stuff.
I do have my oneplus 3 formatted as f2fs, but it is not encrypted. I don't know what happened to it when I tried to do an update with lineage os it basically factory reset the phone (and no I didn't wipe anything but the cache) and it would not install any zips from my internal sd card. I had to go back to fastboot and reflash TWRP 3.0.4.1 recovery. Then I wiped the device and reinstalled lineage, now it works perfectly fine.
They are lineage nighty OTA updates.
HI everyone I need your help. i installed Adaway using F-Droid without first installing and activating the systemless hosts modules -- which I thought was optional.
Supposedly, failing to activate "systemless hosts" triggers a warning to do so during install, but not in my case. My Mi Max 3 (Global Edition, Post ARB) is stuck on bootloop to OrangeFox.
Uninstalling Adaway from OrangeFox did not fix the bootloop.
I'd be okay with losing all data and reverting to unrooted stock but I don't know how to revert to unrooted stock in OrangeFox when OrangeFox isn't finding any backup images.
Might manually editing the hosts file perhaps fix this?
Should I go into Wipe and wipe everything? Or simply delete Magisk? Theoretically, should this result in a system reboot back to stock?
If I can't see any img files are they still hidden in the phone somewhere (stock images) to reboot to? Because I moved since I rooted and cannot find the backup drive with my images on them.
My OS is still stock Android and Miui. These are the modules installed in Magisk Version 20.3:
optimizedgpsconf
quickstepswitcher
riru-core
riru-edxposed
terminal_debloater
Please, any suggestions -- I am sorry for being so clueless despite being in this forum for five years but although I am good at following instructions this stuff remains basically "magic" to me.
Best wishes!
Anybody ever lose all recovery, including stock, after flashing?
Hi again, I'm the one that bootlooped following adaway install. Stopped mucking around, wiped my data and used Orangefox to flash the OTA, which fixed the bootloop but the phone was encrypted (I really did wipe everything and check all the right boxes in the Miui menu). No big deal. I booted back into Orange Fox and did another data wipe and was able to boot to system.
Unfortunately, not only did I lose root, I lost recovery -- no TWRP, no OrangeFox, no stock recovery. I can only boot into the system.
And yet oddly, I can still browse the root files using a root browser and some play apps for root users still detect Magisk. (but Magisk Mgr isn't one of them).
I'm guessing the wise thing to do at this point is to use ADB and start over from scratch, reinstalling TWRP, Orangefox, Magisk and the rom?
Again, if anyone has encountered this error or has any inkling of a quicker way to fix it, please jump in. Thanks!
I