Hello XDA Developers
I have been trying to flash a custom rom on my Google Pixel which is running Android Oreo and I have gotten as far as unlocking the bootloader and installing TWRP. How ever when I attempt to flash any zip file it just says error installing zip and I have no idea what's going on. TWRP sometimes even has trouble mounting the proper partitions so it's a bit of a hit and miss. Id really like to install a custom ROM. I thought maybe it was a bad zip file but I have tried several different ROMs and they all throw up the same error.
Update: Okay I have figured out that installing newer versions of TWRP doesn't work with some of the ROMs and it's better to use the older versions but you have to figure out which one that is if they don't tell you. I was able to successfully install a custom ROM.
Dunno if this advice is any good but don't set a pin code or password on the phone leave it unlocked it's easier for TWRP to read the partitions that way.
Related
Hey guys,
So for a couple of hours I've tried quite a few of guides, but I can't fix my problem.
I'm trying to flash the stock ROM from Oneplus, but I get an error that says the following (just typing everything so I don't miss anything for you guys)
Installing '/sdcard/Oneplus_Bacon_OxygenOS-201601190107.zip'
Checking for MD5 file
Skipping MD5 check: no MD5 file found
This package is for "Oneplus" devices, this is a "bacon"
E:Error executing updater binary in zip '/sdcard/Oneplus_Bacon_OxygenOS-201601190107.zip'
Error flashing zip '/sdcard/Oneplus_Bacon_OxygenOS-201601190107.zip'
Updating partition details..."
I currently have no OS on. When I go to the Reboot button and press any of the buttons there, it firstly comes up saying that I have no OS installed. When clicking OK to that, it comes up with a message that my system is not rooted. I have an option to "Do Not Install" and the "Swipe to Install". The same thing happens no matter what I press (the phone just restarts instantly"
I'm running TWRP v2.7.0.0
Any help is greatly appreciated
Using TWRP to install stock rom's
In most cases TWRP cannot install "Stock" roms, mostly due to an issue with "updater scripts." If you want to use the Stock rom than you'll have to go back to the Stock recovery.
Side note: I wanted to use OxygenOS on mine; however, I wanted to keep it rooted so I found a "TWRP safe" version of OxygenOS online. Be cautious if you attempt that because you'll more than likely lose functionality of your Sim/Radio (will have to flash a baseband in the recovery) if you decide to flash another custom Rom over OxygenOS.
Use oneplus one flashtool or bacon toolkit to flast stock rom. Find in tools sections for flashtools
Hi. this is in regards to the rom here:
Dual/Single] HaoZeke's LineageOS [8-4-17]
And my device is a Sony Xperia Z5 model 6653 currently running a modified 32.3 A.0.376 with a patched Kernel running 7.0 and I am rooted
.I'm kinda new to the modifying of droids. I've had one since ever having a phone, but just got into tweaking them.
I just want to be sure I'm doing this right because sometimes the boot image is attached to the zip file or include in the package but I'm assuming we download
it separately here, right? I'm only guessing since I see it located by itself in the dl list. Also, this IS the kernel too right? Or do I have to download that as well somewhere?
I had an image but it's not taking them I guess. Basically the download screen, all the builds and the boot image. I would take the top build as it's newest and the boot image?
Also, flash twrp from that source after flashing the gapps?
In fact what is the order? Rom, then Gapps, then Boot (if we use that boot file) and then finally TWRP?
And Magisk doesn't have to be flashed I think but just gotten in the play store provided this Rom is already rooted?
Also, wanted to be sure this is correct. ARM... 64 for the GAPPS?
Thanks for your help in advance. I appreciate it. I've had a ton of issues with other lineage 7.1 builds and issues with error 7 . I've rewritten updater scripts to no avail, deleting the asserts and nothing . This is the last one I'm trying as it sounds the coolest anyway. Thanks again.
Hello,
ARM64 for gapps, and proper order of flashing is : rom, gapps, boot optionally and then supersu or whatever you want.
And for me deleting asserts line always work, i will send you link with already modified that updater script.
I was working on a J727P. I had just flashed the factory binary combination file. I had a custom rom for lineage on a external sdcard for this device. I rebooted to the stock recovery from the factory binary system. I scrolled down to the update from sdcard and selected the custom rom. To my surprise it began to flash the zip, it actually completed the flash and upon reboot loaded the custom rom. No root was flashed, No ENG files of anykind either. If the combination file selinux is permissive whats to stop flashing of custom rom on any device that doesnt have a custom recovery? it didnt cause any dmverity fail , or oem signature fails.
deshaney said:
I was working on a J727P. I had just flashed the factory binary combination file. I had a custom rom for lineage on a external sdcard for this device. I rebooted to the stock recovery from the factory binary system. I scrolled down to the update from sdcard and selected the custom rom. To my surprise it began to flash the zip, it actually completed the flash and upon reboot loaded the custom rom. No root was flashed, No ENG files of anykind either. If the combination file selinux is permissive whats to stop flashing of custom rom on any device that doesnt have a custom recovery? it didnt cause any dmverity fail , or oem signature fails.
Click to expand...
Click to collapse
That's because the Lineage build for the J727p spoofs the OTA signature check. Nothing stops it. I believe it's just time consuming to implement. You'll get a really good idea what's going on if you compare the scripts in the Perx's Lineage build to an OTA. If you need or want to dig around in a fota.zip, the password is fotatest1234.
Awesome. Thanks for that insight.
Greetings,
I am trying to instal the LineageOS on my XT1039 Peregrine but I am always getting the following error: E1001: Failed to update system image. Updater process ended with ERROR: 7. I am able to install any stock rom on it, without any issue, but when I try to install Lineage, or any other modded rom, it doesn't work at all. (I've only tried Slim and cRdroid, both gave different issues as far as I remember). Doing google searchs mainly I found posts here and on Lineage subreddit which possible fixes which include: Updating the bootloader, which didn't work because it's already on the latest version, told me to downgrade TWRP and try to flash again also didn't work and I have tried editing the updater-script by removing the asserts or editing the block_image_update lines which also didn't work.
I have a XT1069 Titan which I unlocked the bootloader, flashed the twrp recovery and flashed the latest nightly LineageOS build and it worked just fine, but I can't get it to work on my XT1039 Peregrine.
Thank you for your time and apologies if something like this has already been solved before. I couldn't find a [solved] thread that works for me.
All stock roms from here work just fine:
https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816
updater-script mods I tried:
https://forum.xda-developers.com/showpost.php?p=68442611&postcount=1344
https://forum.xda-developers.com/showthread.php?t=2522762
tool I used to try to upgrade my bootloader, but I already had the latest version:
https://forum.xda-developers.com/moto-g/general/falcon-bootloader-upgrader-tool-t3093793
Edit: Not sure if this is worth mentioning, but before getting the stock roms to work, I think I may have hard or soft bricked my peregrine and somehow managed to fix thanks to a lot of hours on google and xda forums.
Off topic!
This is completely off topic, but let's say I want to sell a phone, if I wipe all partitions from twrp will it wipe everything leaving no trace like when we format a SSD before selling a PC? I belive that a factory reset done from android itself doesn't wipe the whole phone and possibly leave traces, is this correct?
I have been trying unsucessfully tryiing to install Havoc OS on my phone for 2 days now and I believe the common theme seems to be TWRP.
I have tried to install different versions of Havoc, and then other Roms too and all fail in the same place.
There is no error code.
I have also tried to install different versions of TWRP going from 3.4.0.0 to 3.3.1.79 to 3.3.1.70 and none of these work
The steps are not complex and I have followed them to the letter
the bootloader is unlocked and magisk got installed although not needed for this part.
I also tried to install the rom via USB OTG and didnt work
please assist I am having so many issues with stock OS that i would like to try something else
TIA Bart
This can be closed I found it a much older version on the TWRP site itself and that actually allowed me to to flash the ROM