im trying to flash havoc os and just started the process
i am getting the attached error regarding switching slots.
I have carefully followed all the steps, bootloader is unlocked and TWRP is installed too
please help
Update here when the process fails and I choose reboot from TWRP the phones then boots into a clean install of Andrpid 10 is this normal behavior?
so tried various things like changing the slot from a to b and back
changed how the files were copied and the location too but all failed.
reinstalled TWRP too
tried a different custom rom and got the same error
however when trying to reflash stock Android 10 rom this worked so TWRP works?
This can be closed I found a much older version of twrp on the TWRP site itself and that actually allowed me to to flash the ROM
Sounds like you had a bad download. Like a corrupted zip
Thanks bud but it it didn't matter what zip or what wrong I tried none of them worked in the end I downloaded an old version of TWRP 3. 3.1.0 and that worked 1st time
Please close the thread
Related
Hi,
Just for you to know:
Model: r7plusf
Recovery: TWRP 3.0.2-0
----------------------------------------
So earlier today I did an OTA update (cm-14.1-20161205-NIGHTLY-r7plus.zip), but couldn't get my phone to boot.
So naturally, I tried wiping Cache and ART cache, but was still bootlooping.
Thought there might be someting wrong with my ROM and data, so I formated data and Installed ROM and GAPPS again after ADB pushing them onto my phone.
Now, and although CM14.1 and GAPPS are successfully installed on my Oppo R7 Plus, I can't boot into the OS. Every time I try reboot system, whether through POWER_BUTTON, RECOVERY or ADB, I just boot into Recovery.
Worst of all, for some unknown reason, I can't get into BOOTLOADER, neither through button combination, nor through Recovery nor ADB.
I found this article (http://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386) in the LG G3 thread about executing some shell commands, but I haven't tested testing it with my phone's variables because it might hard brick it...
Please Help!
[EDIT] I now have access to fastboot but still recovery looping like crazy.
I installed the same update via CyanDelta , worked like a charm ! hopefully you get back up and running.
[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date
Same thing happened to me! Where did you get a copy of the stock recovery? Link?
resverse said:
[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date
Click to expand...
Click to collapse
I had the same problem. Can't remember exactly how I resolved it. But I think, I use CM recovery to flash nightly. Then flash TWRP to flash gapps. For some strange reason, using CM recovery also show no enough disk space whenever I try to flash opengapps. But TWRP recovery can flash opengapps successfully.
Don't use the OTA, use adb sideload to flash the nightly next time. So far, adb sideload has not given me any issue to flash nightly.
Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.
corbalan12 said:
Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.
Click to expand...
Click to collapse
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse
resverse said:
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse
Click to expand...
Click to collapse
Thank you very much!!!! I'll try tomorrow and tell you.
I appreciate a lot!
First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.
Hi.
A friend gave me his Moto G1 2013 to install Linage OS but I'm really having troubles with it, first of all it doesn't allow me to install TWRP, when I type fastboot flash recovery recovery.img it says that it installs but it doesn't, when I try to boot on it it just doesn't boot, the way I had access to TWRP was typing fastboot boot recovery.img...
When I got in I did the first step when you install a new Custom ROM that is wipe system, cache and dalvik cache, then I tried to install the ROM zip file but it gave me "error 7" I looked for solutions and I found one that is modifying updater-script file, I did it but it gave me another error about mount system, I looked for solutions too and I found one that is modifying file system format to anotherone and then bringing it back to the original format but still having the same error.
After that I decided to go back to stock ROM, I have flashed many times the stock ROM with fastboot commands but it just doesn't boot into the OS, when I try to boot the phone it boots into bootloader again... Any solution to this? Is it a hardware problem? Please help me I'm so embarrased with my friend.
Same thing happened to me!
Basidialfiddle said:
Hi.
A friend gave me his Moto G1 2013 to install Linage OS but I'm really having troubles with it, first of all it doesn't allow me to install TWRP, when I type fastboot flash recovery recovery.img it says that it installs but it doesn't, when I try to boot on it it just doesn't boot, the way I had access to TWRP was typing fastboot boot recovery.img...
When I got in I did the first step when you install a new Custom ROM that is wipe system, cache and dalvik cache, then I tried to install the ROM zip file but it gave me "error 7" I looked for solutions and I found one that is modifying updater-script file, I did it but it gave me another error about mount system, I looked for solutions too and I found one that is modifying file system format to anotherone and then bringing it back to the original format but still having the same error.
After that I decided to go back to stock ROM, I have flashed many times the stock ROM with fastboot commands but it just doesn't boot into the OS, when I try to boot the phone it boots into bootloader again... Any solution to this? Is it a hardware problem? Please help me I'm so embarrased with my friend.
Click to expand...
Click to collapse
Hi! I tried something similar with a similar result. I first unlocked my Moto G's bootloader. Then installed TWRP using fastboot. After that I tried flashing Resurrection Remix rom which failed. I've been stuck in a kind of bootloop since then. My handset powers up, finds something wrong, tries to go into recovery, fails and does this over and over again.
Since I am able to boot into bootloader mode, I tried to flash the stock rom by following instructions from this thread https://forum.xda-developers.com/showthread.php?p=47820707#post47820707
I have tried different variations from many different forums (fora?) all with the same result. Still stuck in the bootloop-thingie.
Btw, I also tried the unbricking guide from this thread
https://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788 without any success. My phone shows up as a Motorola ADB device and also as XT1033 in Device Manager when its plugged in.
Anyone know anything to help me out?
gaurav.kar said:
Hi! I tried something similar with a similar result. I first unlocked my Moto G's bootloader. Then installed TWRP using fastboot. After that I tried flashing Resurrection Remix rom which failed. I've been stuck in a kind of bootloop since then. My handset powers up, finds something wrong, tries to go into recovery, fails and does this over and over again.
Since I am able to boot into bootloader mode, I tried to flash the stock rom by following instructions from this thread https://forum.xda-developers.com/showthread.php?p=47820707#post47820707
I have tried different variations from many different forums (fora?) all with the same result. Still stuck in the bootloop-thingie.
Btw, I also tried the unbricking guide from this thread
https://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788 without any success. My phone shows up as a Motorola ADB device and also as XT1033 in Device Manager when its plugged in.
Anyone know anything to help me out?
Click to expand...
Click to collapse
Hi, I found the solution time ago, sorry for answering to late, hope I can still be helpful.
Well, what I did is, I booted into TWRP, then I did a total format to the storage, after that I did something kind of crazy, I switched my storage format to anotherone and then I turned it back to how it was before (example: I was on fat32, I switched to exFAT and then I switched again to fat32) after doing that I tried to flash LinageOS and it allowed me, it booted and now my friend has Android Oreo on his Moto G1
Hope it works for you mate, those situations are very frustrating, good luck
Good evening /hello/hi,
i own moto one power device (Ram: 4gb, Version: 9.0 pie, MODEL: moto one power, qualcomm snapdragon 626) and i was trying to root my device..
i was successfully able to unlock my bootloader without any error, then i installed and flashed twrp.img(latest version) after flashing twrp i was trying to flash the magisk file which initially landed with a pop up msg (FAILED). After trying it several times i tried to sideload it using adb and was then finally successful and tried to reboot my phone. After rebooting the device i was constantly stuck in the bootloop for almost 20 minutes, i tried rebooting it later but was still in bootloop, so i realized the rom is deleted.
NOTE: The mistake i made was not backing up my device thinking everything will be done fine but i was wrong and landed with this problem.
I also tried to fetch STOCK ROM from forum and flash it, but those zip files was not working. Some say's "invalid zip file" and or "signature not matched".
I also tried to fix the signature error by turning off the option for signature verfication from twrp but still was unable to flash.
i am currently using a custom rom to work with it, but the stock rom was really very good and i would just like to use it.
SO IN THE END I MAKE A HUMBLE REQUEST TO PLEASE, CAN SOMEONE PROVIDE ME THE STOCK ROM SO I CAN FLASH IT CAN START MY PHONE.
A while ago I had a ROM running but switched back to OOS due to battery drain. Time passed and I wanted to give it another go and tried installing another ROM, after getting the recommended variant of TWRP running I tried doing the usual, wiping then installing, but as soon as I tried flashing the ROM it kept giving me this log:
Code:
Flashing A/B zip to inactive slot: A
Step 1/2
Error applying update: 26 (ErrorCode :: kDownloadMetadataSignatureMismatch)
Updater process ended with ERROR: 1
To flash additional zips, please reboot recovery to switch to the updated slot.
Error installing zip file '/sdcard/<insert filename>.zip'
etc
I thought maybe it was because the ROM had failed to download properly, so I tried a different ROM and downloaded the other one again, but it still gave me the same error. I tried several things like formatting the storage because I saw a youtube video doing that, but although my phone boots normally if I try to download anything it fails. Not sure why this is happening. I still can't flash any ROM.
If partitions have been corrupt
I think you have hetter to flash latest "oos fastboot"
then restart from a "kind new" phone
anyway,
tipically with .zip file, also a .md5 or .md5sum file Is published
if you start checking It, you will not run in this kind of problems
WayneKosi said:
A while ago I had a ROM running but switched back to OOS due to battery drain. Time passed and I wanted to give it another go and tried installing another ROM, after getting the recommended variant of TWRP running I tried doing the usual, wiping then installing, but as soon as I tried flashing the ROM it kept giving me this log:
Code:
Flashing A/B zip to inactive slot: A
Step 1/2
Error applying update: 26 (ErrorCode :: kDownloadMetadataSignatureMismatch)
Updater process ended with ERROR: 1
To flash additional zips, please reboot recovery to switch to the updated slot.
Error installing zip file '/sdcard/<insert filename>.zip'
etc
I thought maybe it was because the ROM had failed to download properly, so I tried a different ROM and downloaded the other one again, but it still gave me the same error. I tried several things like formatting the storage because I saw a youtube video doing that, but although my phone boots normally if I try to download anything it fails. Not sure why this is happening. I still can't flash any ROM.
Click to expand...
Click to collapse
Long shot but did you figure this issue out? Im running into the same issue with my Oneplus 7 Pro
Hi everyone,
I've been trying to get TWRP to stick for a while now, but still haven't been able to get it to install. A while ago I managed to flash Resurrection Remix using Lineage recovery which does work, but since Lineage recovery is quite limited, I really wanted to get TWRP to work. Since TWRP 3.5.0 released yesterday, I gave it another shot hoping that they fixed the issue, to no success.
I can get into TWRP just fine by temp booting it with fastboot, but after flashing the installer zip, any recovery that was previously installed gets wiped and the device will reboot when trying to get into recovery. I can still boot my phone otherwise.
The steps I took to get to this point:
Unlocked bootloader
fastboot boot twrp.img
Decrypt using screen pattern (successfully)
Flashed twrp installer zip (no error messages, process finishes successfully)
Reboot into recovery (both from twrp and bootloader at a later point)
Things I've tried:
Use a different TWRP version. Same problem as described above on both 3.4.x and 3.5.x, can't get it to decrypt on lower versions due to Android 10.
Install to recovery ramdisk, this just breaks things even more, probably because it's an A/B device?
Try a different recovery. Lineage recovery works just fine, but it's very very limited. Would really like to get TWRP working.
Trying to flash the zip results in no error messages, but any previously installed recovery gets wiped and magisk is uninstalled, which leads me to believe that it has done at least something to the boot img.
Thank you in advance.
EDIT 25.02.2021:
- Attached TWRP log
EDIT 12.03.2021:
- Log didn't want to attach, they can be found here: https://pastebin.com/awnhHDBU
Same question here. It seems that you can only boot from TWRP, not install it.
Tried installing again today, to no avail. However, I was smart enough to save the log this time. I have attached it to the main post, would be much appreciated if someone could check it out.