I saw an ancient Nexus S in a random drawer in my house. I figured It would be perfect for working out with since I have a Note 5 and it's a little big to carry around. I intended to use it for running only with endomodo. When I booted I noticed Cyanogen mod was installed. It booted up just fine but there was no play store. So like an idiot, I decided to just download the latest play store APK and install it. The app installed but crashed. I rebooted and now I'm stuck in a boot loop. Any help would be greatly appreciated!
You could boot to the recovery system, here you might be able to access all files, and you could try to remove the wrong apk. Alternatively just install the latest nightly version of CyanogenMod from April 2016, thus overwriting your operating system. Then install "gapps" for Kitkat (Android 4.4). There should be instructions on the CyanogenMod website or in this forum about which ones are valid. Make sure they are suitable for Android 4.4.4. You could also consider updating the recovery, if you like, before doing anything else. The latest working version is TWRP 2.8.7. Keep in mind that the device's nickname is "crespo", and do not install any binary that was built for any other device.
Perhaps it would also be sufficient to just reinstall the gapps using the recovery system. Make sure the gapps match the Android version.
So what would I do (brute force method)?
- Start device in recovery mode.
- Check recovery version. If it's not TWRP 2.8.7.0, install this one using the fastboot method, i.e. start device to bootloader, download TWRP to computer, install adb and fastboot on the computer and use the "fastboot" method to install the Recovery system (must be "twrp-2.8.7.0-crespo.img").
- Start TWRP
- Make a factory reset of the device
- Use computer to download latest CM nightly "cm-11-20160410-NIGHTLY-crespo.zip" and copy it to the device.
- Use computer to download suitable gapps package and copy it to the device
- Use TWRP to install both CM and gapps.
Related
Ok. I have a Samsung S4 mini. Yesterday I installed CM13. Dumb thing to do.
It was an automatic update from CMUpdater, so not through the Recovery menu.
For my surprise, I noticed that this update also updated the ClockWorkMod Recovery to the latest version available.
The CM13 installation went well actually .The phone booted fine. Then of course I needed the new Gapps installed. I downloaded the correct Gapps. Boot into CWM recovery. Choose the Gapps ZIP file. And... Error! I went back to phone to enable root acess (ADB & Apps), and enabled USB debugging also. And...Error! No way to install Gapps with CWM recovery.
After some search I realize that the new Gapps for CM13 is somehow not compatible with the CWM recovery that was instaled. So I downloaded ROM MANAGER to change the recovery to TWRP, which everybody said would perfectly flash the Gapps smoothly. Nothing happened. No TWPR. Only CWM still on. Then I downloaded Flashify and went back and forth on installing and unistalling TWPR and CWM. On and On.
Conclusion: somewhere along the process not only I couldn´t install TWRP recovery, but also have wrecked the CWM recovery. Now, no matter what I do, I cannot enter recovery mode at all, hence i cannot neither install Gapps or Reinstall another ROM to "start from scratch"....
I can boot the phone normally.
I can boot into donwload mode normally.
I tried installing TWRP .tar with ODIN3 but it keeps saying "cant open USB port", so it fails.
I have also installed KIES. It sucessfully install drivers, but fails to connect with my device.
Is there anyway to install a Recovery or a fresh new ROM without having to boot recovery?!
Some help? Please.
Hello,
Welcome to XDA.
Do you have USB debugging enabled in system settings to allow flashing via Odin? You may not even need to use Odin.
Try posting your question in the forum linked below.
http://forum.xda-developers.com/galaxy-s4-mini/help
The experts there may be able to help.
Register an XDA account to post and reply in the forums. Good luck.
Hello guys,
first off: i had something to do in the past with all this stuff but my memory isnt that great anymore so please correct me if im wrong
so here's the thing: my OPO decided to not detect my SIM anymore, so i did a factory reset thru recovery. I also rooted the phone before with a video tutorial from youtube (don't know if i can link it here this is my first post^^). What it does is install SuperSU over TWRP. You then have root without erasing your data! I was kinda surprised because i read in other threads that it actually will.
But anyways back to topic. I am now on these settings:
Cyanogen OS 12.1.1-Y0G7DAS2K1
Stock Recovery
Rooted
Bootloader unlocked (not sure, but i guess otherwise it wouldnt work)
I received a message for the OTA Update to Cyanogen OS 13. Downloaded & installed it, phone reboots into recovery. Already surprised here because its not TWRP anymore but i guess it was just temporary for the root installing. Or maybe it was because i didn't unchecked the "update recovery" checkbox in developer options, i think its active on default.
But anyways, the recovery tries to install it and suddenly the menu shows up again with an android in the background (in his chest is a red warning sign). No error, just the graphical android in the background. After a restart, nothing changed still on the same version. I did a factory reset once more and also "deleted media" and wiped cache.
As i mentioned, im not up-to-date with the differences on CyanogenMod and Cyanogen OS.
What i want to do now:
Step 1: Format my OPO as clean as possible.
Is Factory Reset and wipe media etc. enough for this? Or do i have to hard reset it?
Step 2: Root Access and TWRP.
I lost both of these after an OTA update to my OPO. I guess it was when i received the Cyanogen OS update. I would like to know when exactly these two will be erased and what to do to not lose them anymore. I heard it differs between CM and Cyanogen OS.
Step 3: Decision what OS to use: CyanogenMod or Cyanogen OS?
Im willing to wait for updates as long as they're stable. And i would also prefer to just install them over OTA (when it works^^). I don't want to flash like crazy, i only want a steady, rooted, customizable OS. I searched on this forum but im not sure which are the latest versions of both and what the differences are. What would you suggest me on these preferences?
Step 4: Restoring my Data
I backed up my Apps with Titanium Backup and transfered the folder to my PC. Never used it before, so i would like to know if it can cause any problems if i restore it on a newer version of Cyangogen OS or even Cyanogenmod?
Hope i don't forget anything. Sorry for the long post & noob questions you probably read everyday
EagleJR said:
Hello guys,
first off: i had something to do in the past with all this stuff but my memory isnt that great anymore so please correct me if im wrong
so here's the thing: my OPO decided to not detect my SIM anymore, so i did a factory reset thru recovery. I also rooted the phone before with a video tutorial from youtube (don't know if i can link it here this is my first post^^). What it does is install SuperSU over TWRP. You then have root without erasing your data! I was kinda surprised because i read in other threads that it actually will.
But anyways back to topic. I am now on these settings:
Cyanogen OS 12.1.1-Y0G7DAS2K1
Stock Recovery
Rooted
Bootloader unlocked (not sure, but i guess otherwise it wouldnt work)
I received a message for the OTA Update to Cyanogen OS 13. Downloaded & installed it, phone reboots into recovery. Already surprised here because its not TWRP anymore but i guess it was just temporary for the root installing. Or maybe it was because i didn't unchecked the "update recovery" checkbox in developer options, i think its active on default.
But anyways, the recovery tries to install it and suddenly the menu shows up again with an android in the background (in his chest is a red warning sign). No error, just the graphical android in the background. After a restart, nothing changed still on the same version. I did a factory reset once more and also "deleted media" and wiped cache.
As i mentioned, im not up-to-date with the differences on CyanogenMod and Cyanogen OS.
What i want to do now:
Step 1: Format my OPO as clean as possible.
Is Factory Reset and wipe media etc. enough for this? Or do i have to hard reset it?
Step 2: Root Access and TWRP.
I lost both of these after an OTA update to my OPO. I guess it was when i received the Cyanogen OS update. I would like to know when exactly these two will be erased and what to do to not lose them anymore. I heard it differs between CM and Cyanogen OS.
Step 3: Decision what OS to use: CyanogenMod or Cyanogen OS?
Im willing to wait for updates as long as they're stable. And i would also prefer to just install them over OTA (when it works^^). I don't want to flash like crazy, i only want a steady, rooted, customizable OS. I searched on this forum but im not sure which are the latest versions of both and what the differences are. What would you suggest me on these preferences?
Step 4: Restoring my Data
I backed up my Apps with Titanium Backup and transfered the folder to my PC. Never used it before, so i would like to know if it can cause any problems if i restore it on a newer version of Cyangogen OS or even Cyanogenmod?
Hope i don't forget anything. Sorry for the long post & noob questions you probably read everyday
Click to expand...
Click to collapse
Ok so first you can not perform OTA updates with a custom recovery like TWRP. So if you want OTA updates don't install a custom recovery. You lost TWRP before even performing the OTA update don't know how but you did. So I am going to instruct you how to start fresh.
1. You need ADB and fastboot installed you can get the minimal version here http://forum.xda-developers.com/showthread.php?t=2317790 or you can get the full SDK manager which has fastboot and adb https://developer.android.com/studio/index.html but if your not planning development just go with minimal.
2. Follow this guide http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 You don't need to do step 4 since you want to install a custom recovery. So just reboot after you flash all the stock files.
(Also make sure you download the right stock rom he has a 16gb and a 64gb listed. Or you can download the stock rom straight from cynogen os here https://cyngn.com/support
3. Next you will need the TWRP file you can get it here https://dl.twrp.me/bacon/ if you don't have ADB/Fastboot in your path just place the file in the same folder as your fastboot. Also rename the file to recovery.img make sure you don't name it recovery.img.img
4. Download SUPERSU for root get it here https://download.chainfire.eu/1003/SuperSU/SR1-SuperSU-v2.78-SR1-20160915123031.zip
5. With your phone on plug it in to your computer and transfer the SuperSU zip to the download folder on your phone.
6. Unplug your phone and reboot to fastboot then plug your phone back in
7. Open command prompt in the fastboot folder by holding shift and right click and select open command window here.
8. Type fastboot devices (This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.)
9. Type Fastboot Flash recovery recovery.img
10. Once the flash is done don't let the phone fully boot to system or it will rewrite to the stock recovery so hold the power button and volume down and it will boot into TWRP recovery. IF you let it boot into the system and it does reinstall the stock recovery you will need to re-install twrp
11. Once in twrp perform a backup of your stock rom
12. After the backup is done go back to the main menu of TWRP go to install navigate to the download file and then install SuperSU
13. Now reboot and you now have the stock rom with root and a custom recovery.
14. Difference between cynogen os and cynogenmod http://www.androidcentral.com/difference-between-cyanogen-os-and-cyanogenmod
Hope this helps and
Durso81 said:
Ok so first you can not perform OTA updates with a custom recovery like TWRP. So if you want OTA updates don't install a custom recovery. You lost TWRP before even performing the OTA update don't know how but you did. So I am going to instruct you how to start fresh.
1. You need ADB and fastboot installed you can get the minimal version here http://forum.xda-developers.com/showthread.php?t=2317790 or you can get the full SDK manager which has fastboot and adb https://developer.android.com/studio/index.html but if your not planning development just go with minimal.
2. Follow this guide http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 You don't need to do step 4 since you want to install a custom recovery. So just reboot after you flash all the stock files.
(Also make sure you download the right stock rom he has a 16gb and a 64gb listed. Or you can download the stock rom straight from cynogen os here https://cyngn.com/support
3. Next you will need the TWRP file you can get it here https://dl.twrp.me/bacon/ if you don't have ADB/Fastboot in your path just place the file in the same folder as your fastboot. Also rename the file to recovery.img make sure you don't name it recovery.img.img
4. Download SUPERSU for root get it here https://download.chainfire.eu/1003/SuperSU/SR1-SuperSU-v2.78-SR1-20160915123031.zip
5. With your phone on plug it in to your computer and transfer the SuperSU zip to the download folder on your phone.
6. Unplug your phone and reboot to fastboot then plug your phone back in
7. Open command prompt in the fastboot folder by holding shift and right click and select open command window here.
8. Type fastboot devices (This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.)
9. Type Fastboot Flash recovery recovery.img
10. Once the flash is done don't let the phone fully boot to system or it will rewrite to the stock recovery so hold the power button and volume down and it will boot into TWRP recovery. IF you let it boot into the system and it does reinstall the stock recovery you will need to re-install twrp
11. Once in twrp perform a backup of your stock rom
12. After the backup is done go back to the main menu of TWRP go to install navigate to the download file and then install SuperSU
13. Now reboot and you now have the stock rom with root and a custom recovery.
14. Difference between cynogen os and cynogenmod http://www.androidcentral.com/difference-between-cyanogen-os-and-cyanogenmod
Hope this helps and
Click to expand...
Click to collapse
Thank you very much! I did all of your Instructions step-by-step and it worked flawless. Im now on the latest CM13 Release. I hope it was the right decision and it runs smooth and stable. And if not i got the backup I do have 2 more questions:
-TWRP asked me if i want to let them "modify my partition". It helps when you are getting official updates. Is that important for me? I guess i will just flash future updates over recovery and not over OTA anyways, so i can left this "modify" option unchecked, right?
-While i did the factory reset, it said that most of the time i will not have to delete internal storage. Does that mean it also excludes private stuff like photos, videos & also backups from titanium & TWRP (if it's the same stored location)? Thank you again for anything
EagleJR said:
Thank you very much! I did all of your Instructions step-by-step and it worked flawless. Im now on the latest CM13 Release. I hope it was the right decision and it runs smooth and stable. And if not i got the backup I do have 2 more questions:
-TWRP asked me if i want to let them "modify my partition". It helps when you are getting official updates. Is that important for me? I guess i will just flash future updates over recovery and not over OTA anyways, so i can left this "modify" option unchecked, right?
-While i did the factory reset, it said that most of the time i will not have to delete internal storage. Does that mean it also excludes private stuff like photos, videos & also backups from titanium & TWRP (if it's the same stored location)? Thank you again for anything
Click to expand...
Click to collapse
The only way you can do official updates is to follow all the steps above and flashing the newest stock ROM via fastboot and reinstalling twrp. Now if you want to flash a custom ROM like cynogenmod then you can just download the latest ROM from cynogemod and install it via twrp. As far as your pics go I would either upload them to a cloud service or your PC before switching ROMs. For your apps yes just backup with titanium backup and then just restore them when you change ROMs.
I have unlocked the boot loader on oneplus one long back. I tried to upgrade my rom to Resurrection Remix 7.1.1
I successfully upgraded the ROM and also flashed SuperSu in it. I wanted to flash the Opengaps Aroma 7.1 and that is where I ran into issue because of my stupidity.
I found from GitHub that there were some issues with twrp versions to run the aroma installer thus I tried multiple TWRP versions via (Google play - official TWRP recovery app) by downloading them and flashing it to recovery.
I have taken the full nandroid backup but unfortunately didn't keep it on external devices. So it was in the phone itself.
Now the issue -
When I tried flashing TWRP 3.0.2.0 from existing 2.8.4.1 I tried to run the Aroma but it didn't work. Then I tried to flash the recovery with TWRP 2.8.6.1 but Aroma failed again.
However, on the GitHub there was a info stating that known working TWRP recovery on Oneplus one is of TWRP 2.8.4.1
I tried to flash that into recovery and flash the Aroma, but it didn't boot into recovery with that image. Later I restarted the phone, and again flashed the latest recovery version 3.0.2.0
From here I ran into issue. When tried again to flash the Aroma, it didn't work. So I booted recovery again and in that I selected the recovery version 2.8.4.0 for both recovery and boot partition.
After that, phone is neither booting the system nor into recovery. I don't want to loose my data (which is in phone backup) and neither want to try Aroma again. (Even if all the 900mb data needs to be deleted.).
Can the XDA members confirm can I reinstall recovery working image (2.8.4.1) once again through the adb flash recovery <image>. And boot into recovery mode so that I can delete the boot partition once again and reinstall the ROM and data ?
I tried doing that once but one of the laptops which I had access didn't recognize the adb devices. May be the driver was not working for Win10 OS. However, on my personal laptop earlier I was able to run adb commands through CMD prompt. Currently, I don't have personal laptop and may get it by next week.
Can anybody please share me the links of working android driver so that I can install them on current laptop and then try adb commands from SDK to connect my phone.
Any suggestion from members would be of great help.
Note: Please don't suggest the methods to factory reset or lock bootloader to factory settings. As I don't want to loose all my contacts and data.
If there is a way to get just recovery working on the phone, it would be of great help. So that I can wipe other partitions and rebuild it again.
Thank You.
First version shared was twrp 3.2
New version is 3.3.0
***ORIGINAL TWRP is not my work. Only the porting of it to this device. I take no credit for the source.
*** DISSCLAIMER ALLERT***
I started having issues with encryption coming back to enforcing when using the Ported Team LR TWRP 3.3
Did not have trouble yet with OMFG-Mod version.
Also @ghost45 has made a build of twrp 3.3.1 for F1. It works good as well
https://forum.xda-developers.com/showpost.php?p=79651368&postcount=49
--- all versions give trouble of loosing IMEI when using the remove force encryption patch I suggest below. Left logs with @Zackptg5 .
**May need more testing**
-decryption is broken
-MTP is working
-ADB is working
****--Advanced menu items are not correctly on 3.2 version.
-- Some of the advanced menu was fixed in 3.3.(install root is working)
- Advanced menu has extra features.(all from source twrp)
-- install magisk (currently has V17 on OMFG V19 on LR TEAM)
-- patch dm-verity and force encrypt remove.zip. ( personally I prefer the universal dm-removal patch from xda)
-- Remove system password, (from original dev, I have not tested)
--
--Install (basic directions only)--details may be added later if needed
Open zip and fastboot flash the recovery image if bootloader is unlocked.
or
Open zip , then open scatterfile (scatter file in test 1 has issue, updating it in next test )with sp-flashtool , select download
--First boot into TWRP will give errors for unable to mount /data. This is from the force-encryption.
- When boot into TWRP, select wipe -> format type 'yes' to format data
- When format is done, return to TWRP home page, select reboot -. recovery
--Now Patch device so no longer forces encryption
-- Use built in feature from 'Advanced Menu' or use the following directions--Fails to unpack boot. (current zip used is not compatible with system-as-root boot.img)
-To remove this I use 'Disable_Dm-Verity_ForceEncrypt' from
-- https://github.com/Zackptg5/Disable_Dm-Verity_ForceEncrypt -- currently based on magisk V19.2
-Download from the "Clone or Download" button on the above linked Github Page.
-Unzip the downloaded file. You will have a folder with same name as the zip package. Browse inside this folder, select all files and zip them.
-Put this new zip file onto your phone. ( Hay notice the MTP function on this TWRP works)
- in stall the zip like any normal twrp package.
--Next Install Magisk
--Use Built in Root Option from 'Advanced Menu' to use Magisk V19 or the following direction
- Goto the releases page of magisk github page. ==>LINK
- Download latest Magisk zip , Put file to phone, Install.
-- Download Folder For TWRP Ported from OMFG-Mod
https://www.androidfilehost.com/?w=files&flid=294886
-Screenshots.
- Ported OMFG-MOD gold Button TWRP V3.2
- Ported Team LR TWRP 3.3 standard Button
Attached Below
--Thanks --Mentions
recovery source from [LR TEAM] MIUI
http: //www.miui.com/forum.php?mod=viewthread&tid=19006123&page=1&mobile=2#pid257831639
link is newer version from ported recovery. They updated recently. Next port may use newer base as well.
hello @ColtonDRG. Long time.
I see you posted in umidigi forum that bootloader is not checking signature. So you CAN flash images with flashtool without unlocking. Is that correct.?
I have based the above install guide on that fact that you CAN.
But the first twrp posted by "ghost45" says no it must be unlocked.
edit:
I should be able to verify later today or this weekend, when my order arrives.
OK, verified, when i used flash tool and put twrp on phone before unlocking bootloader, on reboot I was stuck in "RED" status for boot loader. So must unlock
Flash this zip to remove the AdupsFota app
this is the update app. You will not be able to install OTA when rooted and twrp anyway, And if an OTA comes you will get stuck in recovery bootloop. So this flash file will rename the 2 apk related to OTA download and Force reboot that supposed to install that update.
Reserved
Will keep this post for working on issues .
Right now , I discovered after playing with the built in dm verity patch and root install lead imei's getting erased.
Restored the full rom with flash tool fixed, will update process as necessary
Restarted from the top again.
--1 Full stock rom flashed with sp flash tool.
--2 Twrp flashed in flash tool
--3 format /data, reboot recovery
--4 use mtp to copy Disable_Dm-Verity_Forceencrypt to phone
--5 flash the decrypt zip. And at the end of flash the output log showed 'failed to mount /nvdata file not exist'
*** Waiting for input from the Patch dev. Others on his xda thread with MTK have had similar trouble***
--6 use mtp , put stock recovery file on phone. Image flash stock recovery, reboot recovery, do factory reset in stock recovery. This fixed the /nvdata error.
--7 sp flash twrp again, use built in 'install root' option from advanced menu.
Bam all done
New Umidigi f1 recovery 3.3.1 test2 is pubblished.
Test this one if all is corrected...
http://www.mediafire.com/file/1emy4tk1gvnkj96/recovery-twrp-3.3.1_Umidigi_F1_test_2.rar/file
ghost45 said:
New Umidigi f1 recovery 3.3.1 test2 is pubblished.
Test this one if all is corrected...
http://www.mediafire.com/file/1emy4tk1gvnkj96/recovery-twrp-3.3.1_Umidigi_F1_test_2.rar/file
Click to expand...
Click to collapse
Thank you, this one has no displayed errors.
I have question though.
Do you know how to make system be mounted as /system instead of /system/system ?
Hey, buddy. Good to see you on the forums again. When I picked up this device I wondered if anyone from the R1 HD days would also be on it. I seem to have misplaced mine but I'll find it eventually, send me a DM if you wanna talk about it. I'm not 100% sure about this, but the bootloader verifying signatures might have been patched in because I don't remember mine doing that when they first came out. Of course even if it does, SPFT is still useful for unbricking and downgrading, but I really doubt UMIDIGI will patch out the unlock option like BLU did.
Hello again, all. I've been working on my UMIDIGI F1 again and after flashing the most recent firmware update using SPFT and trying to flash TWRP again I realized that something that changed in the latest firmware update has broken all of the existing TWRP images. Now the bootloader screen hangs for a while, sometimes a green bar appears at the top of the screen briefly, and then the phone reboots into Android. It is perhaps worth noting that when I tried to flash the upgrade in download only mode it just complained about the partition layout or something like that and then bailed, telling me to use the Format and Download option instead. I didn't do that because UMIDIGI told me not too and instead opted to try the Firmware Update option, which did work. I'm going to try to downgrade (hopefully I don't get bricked from downgrading preloader, efuses, etc) but I am a bit concerned about what has changed. Stock recovery still boots OK so it would seem to me that the bootloader isn't just completely borked, but either way it's a bit alarming that an OTA caused the custom recoveries we have to go kerplooie.
ColtonDRG said:
Hello again, all. I've been working on my UMIDIGI F1 again and after flashing the most recent firmware update using SPFT and trying to flash TWRP again I realized that something that changed in the latest firmware update has broken all of the existing TWRP images. Now the bootloader screen hangs for a while, sometimes a green bar appears at the top of the screen briefly, and then the phone reboots into Android. It is perhaps worth noting that when I tried to flash the upgrade in download only mode it just complained about the partition layout or something like that and then bailed, telling me to use the Format and Download option instead. I didn't do that because UMIDIGI told me not too and instead opted to try the Firmware Update option, which did work. I'm going to try to downgrade (hopefully I don't get bricked from downgrading preloader, efuses, etc) but I am a bit concerned about what has changed. Stock recovery still boots OK so it would seem to me that the bootloader isn't just completely borked, but either way it's a bit alarming that an OTA caused the custom recoveries we have to go kerplooie.
Click to expand...
Click to collapse
There is a newer twrp that has been released on 4pda.net that supposed to work on newest firmware release.
And downgrading with flashtool should work. Again need to use firmware upgrade option.
mrmazak said:
There is a newer twrp that has been released on 4pda.net that supposed to work on newest firmware release.
And downgrading with flashtool should work. Again need to use firmware upgrade option.
Click to expand...
Click to collapse
Downgrading worked. I couldn't find the newer TWRP version you were referring to and the website you mentioned redirects to a bunch of scammy crap.
ColtonDRG said:
Downgrading worked. I couldn't find the newer TWRP version you were referring to and the website you mentioned redirects to a bunch of scammy crap.
Click to expand...
Click to collapse
We have the twrp file copied to telegram group also. I'm stuck on mobile, or I would just copy the twrp here.
UMIDIGI
UMIDIGI unofficial TG group
https://t.me/UMIDIGI
Disable_Dm-Verity_ForceEncrypt failed
Hello, I'm trying to patch my F1 using the Disable_Dm-Verity_ForceEncrypt, but am stuck with an error "Dumping/splitting image failed. Aborting..." This occurs when I try using the Install from twrp. Has anyone encountered this issue before? I have done a wipe, and also tried installing Magisk (which installs fine).
I decided it was finally time to upgrade to the newer LineageOS 17.1 branch nightlies from my previous installation of 16, rebooted to recovery and sideloaded lineage-17.1-20201013-nightly-enchilada-signed.zip onto it from https://download.lineageos.org/enchilada .
After doing so it appears the recovery successfully updated, it has a new purple skin it didn't have before, however the actual ROM won't start. Instead it goes to fastboot mode and asks whether I want to Start/Restart/Recovery/etc, but I can only get into fastboot or recovery mode.
I've tried flashing older nightlies, but even with 20200922 the issue was still there. I did notice there was a ton of updates in that specific release so I wonder if anything is broken in there.. unfortunately that's also the oldest available nightly so without compiling my own there's no way I can test whether older ones are functional, unless someone here has an older version available perhaps.
I did notice doing adb sideload only makes it go to 47% before the phone goes to installing it, however maybe that's normal, I haven't used it in a while so I don't know for sure. I tried using ADB to push an image onto /tmp, however the new recovery only seems to have 'Apply from ADB' as option so I can't actually install it from there.
Does anyone have any ideas I could try, or perhaps an older LineageOS nightly from before 09-22 laying around somewhere? Any help or suggestions much appreciated!
PPS: Of course I forgot to mention but I also did a factory reset, but that did not help. unsure what else to try besides compiling a rom myself or trying other roms from the forums here, though I'd very much prefer having LineageOS..
I found the reason. I had to install the official Oneplus 6 ROM first, probably to get the right vendor binaries/kernel modules/drivers.
This is what I did:
- fastboot boot TWRP ( TWRP can be found here https://twrp.me/oneplus/oneplus6.html )
- wipe -> advanced wipe -> all the things (technically optional but if you want to get rid of GApps etc this is needed)
- adb sideload official OnePlus 6 'Oxygen' ROM ( https://www.oneplus.com/global/support/softwareupgrade/details?code=PM1574156173727 )
- reboot, fastboot boot TWRP
- run the 'copy partitions' zip from https://androidfilehost.com/?fid=8889791610682929240 to copy Oxygen to the other A/B partition
- Install latest build from https://download.lineageos.org/enchilada
- reboot, optionally boot TWRP again and install GApps, also optionally install TWRP, reboot, enjoy.
PS: Please note that after this you shouldn't switch A/B partition without first flashing another nightly or something over it, i.e fastboot boot twrp and install latest lineageos again, otherwise you'll end up booting the vanilla Oxygen rom