Related
So I've been following DavidRocher's tutorial to install a custom rom (the one that's linked around here the most), I've followed it before installing his RR official rom but as the room started showing a lot of issues, I decided to wipe everything and install something a little more stable such as lineage. I didn't care for Gcam or etc so I wouldn't have minded not having those at all.
However, even after following these steps now once again, even flashing the stock rom as asked for a brand new, clean install, twrp (offain) is hitting me with Error 1s on *any* custom rom that I try installing. I can seemingly flash the stock rom without any issues, but anything else and it's a solid no from TWRP.
Am I missing something?
The error itself is Error applying update: 28 (ErrorCode:: kDownloadOperationExecutionError) Updater process ended with Error: 1 error installing zip file.
I've been wiping, booting, rebooting, re-installing the custom rom, checking the unlocked bootloader and I have had no progress at all. I do not know why this is happening, could anyone please help me?
So, I found out that the -only- rom I can install is the one I originally installed, DavidRocher's official RR which seems to be no longer maintained. Which is also the rom I'm trying to get rid of... This doesn't sem to make any sense, does anyone have -any advice- at all?
JumboTSB said:
So, I found out that the -only- rom I can install is the one I originally installed, DavidRocher's official RR which seems to be no longer maintained. Which is also the rom I'm trying to get rid of... This doesn't sem to make any sense, does anyone have -any advice- at all?
Click to expand...
Click to collapse
Please can you describe exactly the steps that you did from boot to recovery and so?
SubwayChamp said:
Please can you describe exactly the steps that you did from boot to recovery and so?
Click to expand...
Click to collapse
Steps followed were:
Flashing stock daisy_global_images_V10.0.3.0.PDLMIXM_9.0 (flash_all.bat from bigota.d.miui.com/V10.0.3.0.PDLMIXM/daisy_global_images_V10.0.3.0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz)
Turning the phone off after it booted successfully;
Turning it on in fastboot;
Booting offain's twrp-daisy-3.3.0-0-offain.img through fastboot (fastboot boot twrp-daisy-3.3.0-0-offain.img);
No password entered;
Format Data;
Pushing custom rom & twrp;
Attempting to flash custom rom in any of the slots. At this point, it fails and gives me the error on any rom except the official Resurrection Remix rom from DavidRocher, which I can successfully install alongside twrp and force encryption disabler, change slots, install gapps and magisk and boot.
*Any* other rom just fails with that specific error code.
JumboTSB said:
Steps followed were:
Flashing stock daisy_global_images_V10.0.3.0.PDLMIXM_9.0 (flash_all.bat from bigota.d.miui.com/V10.0.3.0.PDLMIXM/daisy_global_images_V10.0.3.0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz)
Turning the phone off after it booted successfully;
Turning it on in fastboot;
Booting offain's twrp-daisy-3.3.0-0-offain.img through fastboot (fastboot boot twrp-daisy-3.3.0-0-offain.img);
No password entered;
Format Data;
Pushing custom rom & twrp;
Attempting to flash custom rom in any of the slots. At this point, it fails and gives me the error on any rom except the official Resurrection Remix rom from DavidRocher, which I can successfully install alongside twrp and force encryption disabler, change slots, install gapps and magisk and boot.
*Any* other rom just fails with that specific error code.
Click to expand...
Click to collapse
Try after to reboot to recovery, before of doing nothing or flash anything:
- Flash the TWRP installer.
- Then Wipe cache/dalvik, system and data
- Then Format data.
- Then change slot and reboot to recovery again.
- Now try to follow the usual steps by flashing rom, TWRP, changing slot, etc.
- If didn´t work change the place where it is the rom, extSDCard instead of internal memory or instead adb sideload.
SubwayChamp said:
Try after to reboot to recovery, before of doing nothing or flash anything:
- Flash the TWRP installer.
- Then Wipe cache/dalvik, system and data
- Then Format data.
- Then change slot and reboot to recovery again.
- Now try to follow the usual steps by flashing rom, TWRP, changing slot, etc.
- If didn´t work change the place where it is the rom, extSDCard instead of internal memory or instead adb sideload.
Click to expand...
Click to collapse
Attempted the following steps and adb sideload, error apparently still persists, sadly. This is just... So weird. It doesn't make any sense at all, maybe the official RR altered the partition sizes in some manner? I tried resizing/repairing them through TWRP and it also didn't change anything... ****.
JumboTSB said:
Attempted the following steps and adb sideload, error apparently still persists, sadly. This is just... So weird. It doesn't make any sense at all, maybe the official RR altered the partition sizes in some manner? I tried resizing/repairing them through TWRP and it also didn't change anything... ****.
Click to expand...
Click to collapse
The message through TWRP still the same? Try erasing boot partition where is allocated TWRP through
Code:
fastboot erase boot
then boot to offain TWRP, flash other recovery like Orange and see if this recovery can flash the rom and later flash again TWRP through Orange I don´t think that RR did that so I flashed both versions on my device and I don´t have this issue but if you sometime resized your partition I don´t guess that TWRP can restore it well, you could resize it again through the same method.
SubwayChamp said:
The message through TWRP still the same? Try erasing boot partition where is allocated TWRP through
Code:
fastboot erase boot
then boot to offain TWRP, flash other recovery like Orange and see if this recovery can flash the rom and later flash again TWRP through Orange I don´t think that RR did that so I flashed both versions on my device and I don´t have this issue but if you sometime resized your partition I don´t guess that TWRP can restore it well, you could resize it again through the same method.
Click to expand...
Click to collapse
I guess I'll try it with orange when I have a little more time then.. Spent the last 10-12 hours trying different procedures with twrp and they were pretty fruitless... It's still so weird, I'm definitely not new to flashing roms, I've done it so many times in the past and this is the very first time I get this sort of behavior. I'll update this once I try out OrangeFox.
hi!
your method has always worked for me, but this time I always get error 1.
I tried to install the pixel experience and lineage and nothing works, can you help me?
:good:
My device forum doesn't have instructions how to do it, i've posted asking there but better to ask here also. I found this post for the Mi A2 that isn't my device mines the Mi A3 https://forum.xda-developers.com/mi-a2/how-to/guide-discussion-aio-gsi-thread-mi-a2-t3933356
The device is A/B arm64 has slots a and b i dunno how that effects flashing here, flashing custom roms will install into the inactive slot then you gotta change your active slot to be the the slot it installed into, then install rest of files there, does this apply with gsi .img files also?
When i tried using flashing the .img file i used orangefox recovery wiped all partitions flashed to system, just says no os installed i will probably try doing that again and flashing DM-Verity & Forceencrypt Disabler and permissiver_v2.zip however who noes if that will help.
If someone can list the correct steps to flash using both fastboot method and twrp/orangefox recovery methods i would appreciate it. If it matters i was trying to flash android 10 gsi. I've seen many different methods listed depending on the device, so i guess that makes it harder to work out.
Thanks.
I've flashed it twice via TWRP with flashing DM-Verity & Forceencrypt Disabler and permissiver_v2.zip. Plus TWRP.
1st time it was into A slot. After 1st flashing I've restarted TWRP and booted into B slot. And then flashed slot B.
After rebooting and seeing Logo in 15 minutes - I've got Android.10
xVM said:
I've flashed it twice via TWRP with flashing DM-Verity & Forceencrypt Disabler and permissiver_v2.zip. Plus TWRP.
1st time it was into A slot. After 1st flashing I've restarted TWRP and booted into B slot. And then flashed slot B.
After rebooting and seeing Logo in 15 minutes - I've got Android.10
Click to expand...
Click to collapse
Thanks for the feedback, are you able to tell me the exact steps? like lets just say twrp is already installed and you factory reset, cleared all data.
Do you flash DM-Verity before you flash the rom? or after you flash the rom and what you just flash Forceencrypt Disabler and permissiver_v2.zip after installing the rom?
What i see with regular roms not gsi when you flash the rom if your on slot a it's actually installing it into slot b when you reboot that's where it is so you need to restart before flashing Magisk and other stuff. So i assume with the gsi maybe you need to reboot after installing as system image before flashing the other files?
Alister. said:
Thanks for the feedback, are you able to tell me the exact steps? like lets just say twrp is already installed and you factory reset, cleared all data.
Do you flash DM-Verity before you flash the rom? or after you flash the rom and what you just flash Forceencrypt Disabler and permissiver_v2.zip after installing the rom?
What i see with regular roms not gsi when you flash the rom if your on slot a it's actually installing it into slot b when you reboot that's where it is so you need to restart before flashing Magisk and other stuff. So i assume with the gsi maybe you need to reboot after installing as system image before flashing the other files?
Click to expand...
Click to collapse
Your better of using fastboot if flashing a gsi .img you dont need twrp really unless the rom is in a .zip format, or your wanting to add extras like magisk and such, or take a backup
Android 11
Did anyone tried Android 11 gsi??
Hi everyone.
I had a issue and i really want help
I had unlock the OEM,and after installing the twrp and format data (to remove the forced encrypt), i had flash the Disable_Dm-Verity_ForceEncrypt zip file.
Okay, after that i have restarted the device and configure as my away to use, after that, booted on recovery again and flashed the magisk.
But i wanna encrypt my device, and when i go to configs->security and encrypt area, says that my device its not encrypted. Okay, i followed the steps and when i gonna try to encrypt the device, the process start and... some seconds after, the phone just restart and nothing has done.
The onlys changes that i have made on system is: root and flashed a splash.img(without that stupid warning of unlocked bootloader)
I really want to encrypt my device, so, if i get stolen, the thief wont get my user data.
Can anyone help me?
Flash the stock rom and and don't flash the encryption disabler next time. You don't need to install TWRP to flash Magisk either, you can just boot it and then flash Magisk. Also you don't even need TWRP, you can just follow the guide in the forum to install Magisk by booting the magisk patched boot.img for your version of the stock ROM and then install Magisk manually via Magisk Manager.
TL;DR : Flash stock ROM and do the same things except flashing dm-verity-disabler, you don't need that for Magisk or TWRP.
marstonpear said:
Flash the stock rom and and don't flash the encryption disabler next time. You don't need to install TWRP to flash Magisk either, you can just boot it and then flash Magisk. Also you don't even need TWRP, you can just follow the guide in the forum to install Magisk by booting the magisk patched boot.img for your version of the stock ROM and then install Magisk manually via Magisk Manager.
TL;DR : Flash stock ROM and do the same things except flashing dm-verity-disabler, you don't need that for Magisk or TWRP.
Click to expand...
Click to collapse
Thanks sir, i will try!
marstonpear said:
Flash the stock rom and and don't flash the encryption disabler next time. You don't need to install TWRP to flash Magisk either, you can just boot it and then flash Magisk. Also you don't even need TWRP, you can just follow the guide in the forum to install Magisk by booting the magisk patched boot.img for your version of the stock ROM and then install Magisk manually via Magisk Manager.
TL;DR : Flash stock ROM and do the same things except flashing dm-verity-disabler, you don't need that for Magisk or TWRP.
Click to expand...
Click to collapse
Sir, i really need twrp now, its there any way i can enable encrypt after rooting the device? (to sure that, if gets stolen, the data need to be wipped out or the password must be given on twrp)
Same issue, i tried to encrypt on security menu,reboot and nothing was done.
@edit
Better, without TWRP, i can flash other zips via magisk/stock recovery?
mrkeitsuke said:
Sir, i really need twrp now, its there any way i can enable encrypt after rooting the device? (to sure that, if gets stolen, the data need to be wipped out or the password must be given on twrp)
Same issue, i tried to encrypt on security menu,reboot and nothing was done.
@edit
Better, without TWRP, i can flash other zips via magisk/stock recovery?
Click to expand...
Click to collapse
I'm not sure what you're trying to do here, do you want to have TWRP + stock encryption?
If so you can just boot TWRP and flash the TWRP installer package (.zip) inside TWRP to do that. And you don't need to change anything, currently I have TWRP installed and encryption enabled on my Stock ROM.
But if you're trying to get TWRP's own encryption, sadly that doesn't work.
You can also use TWRP without flashing/installing it, just go to the directory TWRP is stored in, open a command line, connect your phone and boot it with this command :
Code:
fastboot boot twrp.img
then flash whatever you'd like.
DO NOT lock your bootloader after you flash something on TWRP, this will most probably brick the device.
marstonpear said:
I'm not sure what you're trying to do here, do you want to have TWRP + stock encryption?
If so you can just boot TWRP and flash the TWRP installer package (.zip) inside TWRP to do that. And you don't need to change anything, currently I have TWRP installed and encryption enabled on my Stock ROM.
But if you're trying to get TWRP's own encryption, sadly that doesn't work.
You can also use TWRP without flashing/installing it, just go to the directory TWRP is stored in, open a command line, connect your phone and boot it with this command :
Code:
fastboot boot twrp.img
then flash whatever you'd like.
DO NOT lock your bootloader after you flash something on TWRP, this will most probably brick the device.
Click to expand...
Click to collapse
I want to stick with the stock rom rooted, with the twrp installed and the user data encrypted
So i can flash things through TWRP even i have encrypt enabled?
@edit
dont worry about bootloader, i will keep unlocked
It's perfectly fine to have TWRP and/or Magisk and encryption using stock ROM.
Flash stock ROM (erase user data)
Install TWRP
install Magisk
Don't flash the encryption Disabler. As its name implies, it disables the automatic encryption of the userdata partition.
a1291762 said:
It's perfectly fine to have TWRP and/or Magisk and encryption using stock ROM.
Flash stock ROM (erase user data)
Install TWRP
install Magisk
Don't flash the encryption Disabler. As its name implies, it disables the automatic encryption of the userdata partition.
Click to expand...
Click to collapse
:highfive: i had done this and... i think its working!!! :crying::crying::crying:
(crying for emotion, almost thirty factory resets to get an good result :crying::crying::crying
Anyway, if anything bad occurs, i will update here, thanks a1291762 and marstonpear
Hi all I have been tinkering away and destrying my setup left right and centre to sort this process out but if you're unable to run the latest TWRP for your note from Ian and get stuck at SAMSUNG screen on boot then this process will fix that if followed correctly. This is due to the device's roll back protection.
This process will reset everything back to current date and get everything working on the new Oneui 2.1 base
Process for getting round SAMSUNG screen issue - please read through first and get the files you need before starting. I did this on my N976B but in theory it should work for other 10-range devices, notes indeed!
UNLESS YOUR RUNNING CRUEL KERNEL OR A SPIN OFF, YOU'LL NEED VOL UP AND POWER TO ACTIVATE MAGISK ON EACH BOOT
Needed:
Stock firnware
Magisk app
Twrp image
Pc and odin also patience and a brain lol
-Return to stock by flashing AP/BL/CP&CSC in odin
-Reboot and confirm oem unlocking greyed out, install magisk app and patch twrp image from Ian, also patch your ap file.
-reboot to download, meanwhile get the magisk_patched.tar and insert TWRP renamed as recovery.img in place of the stock patched recovery (keep this one for later)
-In download mode and with auto reboot off in odin, flash BL, Magisk_patched.tar(with the TWRP from Ian in), CP & HOMECSC.
-When flashing is complete exit download mode and immediately hold power and vol up and hold until on TWRP slider screen. swipe to allow modifications, format internal storage and flash multidisabler.
-Reboot TWRP and backup your current patched stock rom. FLASH THE STOCK PATCHED RECOVERY YOU SAVED EARLIER AND THEN FLASH MULTIDISABLER (THIS IS IMPORTANT AS YOU WILL THEN BE ABLE TO INSTALL TWRP VIA THE APP WITHOUT HAVING TO REFORMAT INTERNAL)
-Reboot straight to stock recovery (reboot from TWRP and hold Vol up and power until in stock recovery) and factory reset then reboot.
-You should now boot up as normal, setup your device, in particular have TWRP app and Magisk set up and running.
-Flash the Unpatched TWRP for your device in the TWRP app - reboot TWRP and check the box to kill that annoying swipe to allow modifications and then you are good to flash whatever rom or kernel you want for your device!
Flash the stock patch recovery as boot??
orbital_71 said:
Flash the stock patch recovery as boot??
Click to expand...
Click to collapse
yes then immediately flash multidisabler before you reboot to set up
i have just helped someone through this on TG so it defo works :good::good::good:
It can also confirm this is working. Just followed this guide on my Note 10+ (N975F with CTD1) and happy flashing now.
drexxie1962 said:
It can also confirm this is working. Just followed this guide on my Note 10+ and happy flashing now.
Click to expand...
Click to collapse
Excellent, thanks for testing!!!!!!!
@askmydas
you may find this useful - follow this to get your sec date reset then follow the process spelt out in the thread of the rom you want to use as you may need a different TWRP depending on what sec date the chef of your chosen rom uses.
Hey, when I get to " FLASH THE STOCK PATCHED RECOVERY YOU SAVED EARLIER" I try to do this and it tells me I don't have enough space. Any ideas?
KiwiNote+ said:
Hey, when I get to " FLASH THE STOCK PATCHED RECOVERY YOU SAVED EARLIER" I try to do this and it tells me I don't have enough space. Any ideas?
Click to expand...
Click to collapse
I worked it out, I was trying to install "recovery.img" to boot partition, "recovery.img" needs to be installed to RECOVERY partition. Silly me. Fixed it now, but have a new issue:
After I flash unpatched twrp image through the app, now my phone will only boot into TWRP. I don't even boot with recovery button presses, but it will still boot into TWRP only. Any ideas?
I know this is an old thread, but it may be that my solution could help someone who is locked on the outside of the device (softbrick)
TD,DR: If you have softbrick and you can't boot the device at all, try flashing via Odin the BL, CP, CSC from a stock rom and the AP of another completely different stock rom.
I had an IMEI 0000 issue on my Galaxy Note 8 (SM-N950F), using Hades Rom (custom), and I needed to install the stock rom. As I was on the F(15) binary, there were only two roms (SamMobile and Stockrom.net) available for my country (Brazil) with this binary:
N950FXXUFDUD6_N950FOXMFDUD6_ZTO
stockrom.net_N950FXXUFDUG5_N950FOXMFDUG4_ZTO
And a via Frija:
SM-N950F_1_20210717024140_0wmgsx8iwf_fac
And no Combination Rom for that binary
After flashing these roms several times, I was always stuck on the “Powered by Google” screen, even doing cache wipe and factory reset through stock recovery several times. So I flashed the N950FOXMFDUD6, flashed the CF-Auto-Root and was able to boot the device. Once inside I noticed that it didn't solve the problem of IMEI 0000. I tried a few more procedures, ended up restarting to install TWRP, and the OEM is closed!!! (OEM OFF, Prenormal). I start getting the message “only official binaries are allowed to be flashed(recovery)”. I flash the stock rom, but it gets stuck on “Powered by Google” again. I tryed to install CF-Auto-Root and I get the message “only official binaries…” I can't log into the device anymore. So after four days of desperation, trying every technique possible, trying to create the Combination Rom by unzipping the AP file from the stock Rom and modifying the files inside, without success, I finally try a procedure I haven't seen anywhere else: I go to the modified Odin: Odin3_v3.14.1_3B_PatcheD, I selected the BL, CP, CSC files from the N950FOXMFDUD6 rom and the AP file from the rom SM-N950F_1_20210717024140_0wmgsx8iwf_fac
And it worked! I can boot the device
So I want to root my Xiaomi mi a2 lite, because of it I want to install custom rom, but there is one problem:
while going in twrp recovery (using adb booting command) it gets error : 1; it says : "to flash additional zips please reboot recovery to switch to the update slot"
however, it only happens when I want to flash custom rom (tried 3 different roms), when trying to flash a custom recovery or ForcedEncryptionDisablerDaisy it flashes successfully.
any solutions?
some information :
it's my 3rd time flashing the custom rom on this device:
1) the first one was using the "classic method" (with twrp recovery)
2) the second one was when I got stuck in the bootloader and used XiaoMiFlash application for flashing.
i face the same problem
I have oneplus 7 and have the same issue
flvckoo said:
So I want to root my Xiaomi mi a2 lite, because of it I want to install custom rom, but there is one problem:
while going in twrp recovery (using adb booting command) it gets error : 1; it says : "to flash additional zips please reboot recovery to switch to the update slot"
however, it only happens when I want to flash custom rom (tried 3 different roms), when trying to flash a custom recovery or ForcedEncryptionDisablerDaisy it flashes successfully.
any solutions?
some information :
it's my 3rd time flashing the custom rom on this device:
1) the first one was using the "classic method" (with twrp recovery)
2) the second one was when I got stuck in the bootloader and used XiaoMiFlash application for flashing.
Click to expand...
Click to collapse
same problem here im wasting so much time triying to figure out how to repait the partitions or something, because somehow I had a partition B and now doesnt exist lol.
Hey, mates!
Anyone able to solve this?
I flashed TWRP and Magisk successfully, but every time I try to flash a custom rom it gives me the message "to flash additional zips, please reboot recovery to switch to the updated slot".
I'm on a Xiaomi Mi A2 Lite, btw.
Thanks in advance for any help!
ATTENTION!
I found a solution to the problem, all you need is just to install another recovery, I installed Orange FOX. And you know what? Everything worked. So just install via SD card Orange FOX and be happy!
Thank you, your Yasude!
My phone: XIAOMI Redmi note 10
OF does slot switching automatically? I managed once boot and install OF, wipe, flash SYberia, change slot, anti encryption and magisk, reboot to system. Unfortunately never work with lineage. But OF has options disable encryption and some measures against (i dont like them - own ota recoveries which always make a mess)
LOS dmesg complaints about damaged GPT and cant find many files even after edl flashing with original FW.
just install orange fox