EDIT:
I managed to get back to stock pushing it through with fastboot!
Crisis well and truly averted.
Hi,
So I updated to the latest version of Viper4Android through Magisk Manager, and a few seconds after completion my device powered off and on again, but it couldn't boot.
I went into TWRP recovery to factory reset, this did not help. Me being an idiot I have no backups, and no roms on my system storage so I can't flash the stock firmware, and when I attempt to sideload with ADB, TWRP simply hangs on starting ADB side-load feature.
As it is, I'm thinking of updating to the latest version of TWRP available to see if this would fix the ADB sideload error, but don't want to take these steps until I get some advice from the forum.
Cheers, any help is appreciated.
Download the firmware, download TWRP, download Magisk (zip and Manager app). Start from scratch. (You can remove the -w from the fastboot line in the .bat or .sh file to keep your data.)
When it boots, set it up again - email, your apps, etc. Then make a TWRP backup and copy it to your PC. Make it a habit, if you make major changes, to do a TWRP backup and copy it to your PC. (Whatever problems I've ever had, and I've created many, I always had at least one backup I could fall back on. Maybe I had to flash twice because I did something stupid the first time, but I always ended up with the backup back on the phone. And this goes back to the beginning of TWRP. No more starting with an empty installation of the firmware - with TWRP there's no excuse.)
Related
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.
Hey,
Quick rundown: Stuck in a bootloop to some sort of empty bootloader screen which has the readout:
"Start/Restart Bootloader/Recovery Mode/Power Off"
"Press volume key to select, and press power key to select"[Regarding above options]
"FastBoot Mode
PRODUCT_NAME - sdm845
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - [Gonna leave this out for now]
SECURE BOOT - yes
DEVICE STATE - unlocked" [this line is in red]
Every choice besides Power Off returns me to the same window. What can I do to recover from this?
Background:
So I was trying to update my OP6 to the current OxygenOS while keeping my root using TWRP and Magisk, which I've done in the past without any issue(i.e. go in recovery flash OS, flash current TWRP, reboot back to recovery, flash current Magisk as I understand it). However this time I was running into an issue flashing the Oxygen update getting an error that said it "failed to map file" for the zip. My first instinct was to update TWRP to see if the newest version didn't run into this issue so I flashed that followed by the current Magisk(no reboot in between). After booting back to standard operations everything seemed fine. I went back into recovery and tried the OS update again, but hit the same issue.
I couldn't find anything specific to OP6 with this issue, but similar questions with other devices suggested clearing the dalvik cache, which I tried to no useful effect. Then I came across this thread (forums.oneplus.com/threads/oxygen-os3-i-have-a-problem-please-help.440587/page-2 too new to hyperlink) and did what I think really messed me up which was boldly follow this guy's advice to do an advanced wipe of everything but internal storage(I also left USB storage intact) from TWRP. This failed to fix the issue with the file mapping error when I subsequently tried to flash the update, though I was able to flash TWRP and Magisk successfully again before rebooting and ending up in this loop.
Any assistance in fixing this or general tips on how to not be foolish when messing around with this stuff is greatly appreciated.
Update:
So I followed the advice gleaned from the resourceful person here(https://forum.xda-developers.com/oneplus-6t/help/bootloader-baseband-versions-blank-t3927565) to try working with the device from my computer with fastboot. At first it would recognize the device as "Android" but be unable to find a driver for it and adb/fastboot both failed to recognize it as a device. After installing MiniTool(more as a way to backup what was on the SD card) the proper device driver also got installed and I was able to access it with fastboot; I ran into similar issues as the linked thread above, solved it by switching to b(still failed) then back to a.
Currently I've got it booted into TWRP and I'm working on getting the current Oxygen .zip copied onto the phone storage but the transfer keeps failing after moving a negligible amount.
Update 2:
Via TWRP was able to sideload the current up-to-date standard OS onto it, however my Google backup seems to have decided to disappear on me and the only OP backup I have is ages old. Anyone have recommendations on data recovery tools?
next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.
NickTheHuy said:
next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.
Click to expand...
Click to collapse
Good to know, thanks for the info!
I assume that happened when I messed around with advanced wipe, do you know which of the folders I selected that would have been under? And just for future awareness, would that have not occurred had I just used TWRP's standard wipe instead?
You can run a program that will install 9.0.6 from scratch, running a batch file...
Save my life before yesterday....
Your device is bricked
If able to access the TWRP recovery then boot into twrp and try to get all the data stored in your computer.
Then use the Qualcomm flash tool to completely recover from your hard bricked OP6.
from here https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
Then its easy, again unlock boot-loader flash TWRP and magisk.
Hey,
I updated already rooted phone with Oxygen updater (forgot that he will remove TWRP in auto install) and now can't get it to fastboot into TWRP with ADB. I tried several .img files but non worked. Every time it goes to Crash dump.
Did someone successfully fastbooted into one? Or the only solution is to go back and do it manually from OOS 10?
Thank you!
99mike199 said:
Hey,
I updated already rooted phone with Oxygen updater (forgot that he will remove TWRP in auto install) and now can't get it to fastboot into TWRP with ADB. I tried several .img files but non worked. Every time it goes to Crash dump.
Did someone successfully fastbooted into one? Or the only solution is to go back and do it manually from OOS 10?
Thank you!
Click to expand...
Click to collapse
If you are on OOS 11 then use the attached file and try the below steps.
1. Reboot to Fastboot mode.
2. Use command : Fastboot boot boot.img (use attached TWRP alone)
3. Once rebooted to recovery mode Install recovery by Advanced -> Install Current TWRP . This should install the image automatically to your device.
Reboot your phone to system mode and then reboot it back to recovery mode later.
Hope the above helps.
TWRP is wonky on A11, for now.
If I'm not mistaken the TWRP provided by other poster will have issues with making and restoring backups.
If you are still rooted and looking for a backup/restore method, you might as well leave TWRP alone for now and simply maintain root through the Magisk app. If root was lost, then you can use the version provided here: https://forum.xda-developers.com/t/recovery-11-unofficial-teamwin-recovery-project.4306803/ which is likely what other user posted, to restore root and then wait for Google to release the full deets on A11 to hobby developers who can then make a new TWRP.
This worked for me to get back TWRP and root after upgrading. Thank you very much!
Just so that everyone is aware because no one here seems to be aware of anything...
TWRP version twrp-3.6.1_11-0-redfin.img from here: https://dl.twrp.me/redfin/
Works just fine if you just temp boot from fastboot with the most recent OTA SPA2A.220405.003
And you DO NOT HAVE TO INSTALL A KERNEL FOR IT TO WORK, THIS BUILD ONLY
With this build, you can indeed backup and restore your system. I have used this build since it was live, and it works no problem.
I cannot confirm it works with any other build, nor can I confirm you can install it to ramdisk and get it to work.
But it works just fine with temp booting from fastboot. Backup, Restore, etc works just fine for me. I have gone back and forth from my build to the OTA no problem whatsoever, and have been able to restore all userdata from the most recent OTA.
BIG THANKS TO TWRP, AND bigbiff for his work
and, btw, you have to reboot anywhere from 1 to 3 times after a restore for it to completely boot.
You'll see the old boot logo first and it will freeze, then the new boot logo and it could freeze, then the third time it boots just fine. They even have this listed on TWRP's site I believe.
So, if you're having trouble after a restore, just reboot a few times but wait until it hangs before you do. It will eventually come up.
Also, it is possible to install this same recovery to your boot.img ramdisk. You cannot flash this image directly or else you will end up in a boot loop.
In order to install permanently to the ramdisk, you have to disable verity and verification just like for root, then temp boot the twrp.img, then while in recovery adb push twrp.img /
Then go to install, and choose the twrp.img and it will ramdisk install it. Then wipe all userdata--must be done, no way around it.
Reboot to recovery, and backup the boot.img only. Then copy the boot.emmc.win to somewhere on your internal SD card as twrpboot.img.Then you need to boot into the system, install magisk app, and then patch twrpboot.img, then reboot to bootloader and flash the patched boot.
After all of that you will have both a rooted boot.img with permanent recovery in the ramdisk.
I do not know anything about safety net as I don't use any kind of banking apps at all so that will be your own responsibility to deal with.
That's so good to finally hear, looks like I'm going to have to do this. Thanks for the update, off topic but considering making a guide with as many links to projects, roms, kernels, etc that are being made or in process specifically for our phone and differentiating a11 and a12 support
stayboogy_Officially said:
Then copy the boot.emmc.win to somewhere on your internal SD card as twrpboot.img.Then you need to boot into the system, install magisk app, and then patch twrpboot.img
Click to expand...
Click to collapse
This worked for me. I have Magisk and TWRP installed on stock Android 12.1 version 220305.
I was worried because I did not actively Disable Verity or Verification , or unencrypt anything.
But I am able to make full backups, and restore them, which is what i care about
I updated to Android build SP2A.220505.002 (via TWRP 3.6.2, magisk 24.3, and the May 2022 ota update file).
No problems yet..
has anyone updated to Android13 ?
Hi, I run LineageOS 19.1 on my Vayu. It is obviously unlocked and I have Rooted it with Magisk.
I have put off updating the System but did it just now through the Updater in the Settings. From 20220916 to 20221104.
I ran into a Bootloop and went into Fastboot, installed TWRP with ADB sideload. (Had stock Recovery before)
I then tried to just revert back to 20220916 (which was not so smart). I tried to sideloaded the boot.img, but it showed "failed".
--> Still in Bootloop after Rebooting
Now I am unable to flash any boot.img or boot at all.
I tried to flash something else (Magisk.zip), which worked. I have removed all magisk modules, tried to boot with
magisk --remove-modules.
Does anyone have any Ideas? I don't really want to Reset my Phone, even though I have abundant Backups.
Thank you )
Moving back to old version almost all the times is not possible without full reset, new version contains new scripts and possibly new files, how would you explain this for system?
By flashing old version over new one, you probably messed up your system, might as well just backup your data and start from scratch.