I would like to install a custom rom, but when trying I came across an error in the twrp saying that the zip was not compatible.
It's the first time I'm doing it, so I'd like some help to understand the whole process from the beginning, what I need to unlock before installing the rom and everything.
I'm on Android 10, ie binary 10.
Thank you for your attention in advance
DO NOT DO IT
Related
Hi everyone,
I just had a very frustrating experience tonight and I really need help because I don't understand why my phone would behave like that.
I wanted to update my phone and go to android 6.0 marshmallow, I tried to flash the latest builds of both SkyDragon and CandySix but here's what happened :
_Concerning SD, the flashing stopped while installing busybox and it said something like "Some symlinks failed"
_Concerning CandySix, the flashing went all the way completely right, everything was OK but when I tried to boot the ROM, it would just boot into teh recovery instead.
Please excuse my english and help me, I really want to update my phone to marshmallow...
Hi all,
I consider myself a noob when is come to flashing stuff on my phone
When ever i try to flash a new ROM on TWRP my phone always gives me an Error 7, to fix this I searched up tutorials on youtube and deleted the "asserts" part of the updater-script file as said but then after doing so and flashing the edited zip, i get another error saying the update binary was not found. I believe the error 7 is due to the fact that a few months ago i wanted the google assistant on my OP3 and changed the build prop, i did not notice the fact that you needed to be on Nougat to do this but realised after changing the build prop. Now nither can I update to newest ROM nor can i flash a custom ROM
Android Version : Marshmello
ROM I want to install : Lineage OS
any help would be appreciated,
thanks
What version of twrp are u on
Ok, so here is the thing. I know a little bit about rooting & custom roms as I rooted & installed custom roms on my previous phone. Some days ago, I unlocked xiaomi phones bootloader, installed twrp, tried to flash rom but no luck. It showed "update process ended with error 7", but that is not the issue here. As I mentioned i flashed custom roms on my previous phone, that same phone I tried flashing custom roms agaim, but I get that error "updated process ended with error 7" And then I tried to flash custom rom on my lg g3, the same error appears again. This makes me suspicious, what am I doing wrong? Whats the the problem? I searched on the net for this error, it showed me, if you install unsupported rom then this message apppears, but I am not installing any unsupported roms, then why is this error keep showing on my every phone??
i think you are using the wrong TWRP for it, there is only one working TWRP Version for the A2 Lite at this moment and it's offains version
if u flash a custom for the first time on the a2 lite, it is a bit more complicate than any other device, so be careful what are you doing.
here is a good instruction for it
https://github.com/tkchn/daisyinstall
solved said:
i think you are using the wrong TWRP for it, there is only one working TWRP Version for the A2 Lite at this moment and it's offains version
if u flash a custom for the first time on the a2 lite, it is a bit more complicate than any other device, so be careful what are you doing.
here is a good instruction for it
https://github.com/tkchn/daisyinstall
Click to expand...
Click to collapse
what twrp version should i use if im on base 10.0.0.9
the same. stick to the offain 3.3.0-0 .. dont use any other version. every custom rom you get here will work with it.
Dear XDA-Developers,
After trying for many hours searching different forums and websites looking for help, I decided to make an account here and ask for help here.
I am currently on a Rooted OnePlus 5t with OxygenOs 9.0.3. I have not updated my phone in a really long time and decided to do so now.
I decided to dirty flash the full official ROM for OxygenOs 9.0.11 which was released recently with TWRP.
At first, I was on an older version of Blu_sparks recovery but replaced it with the newest TWRP from their website (Dumpling 3.3.1-0).
When I first tried to flash it, I got this error message:
failed: no space left on device
E1001: failed to update system image.
Updater process ended with ERROR 7:
Error installing zip file 'sdcard/download/Oneplus5Toxygen_43_OTA_054...
After trying multiple other recoveries, trying to flash with and without the compatibility zip and also trying to flash earlier versions of OxygenOS with different TWRP versions, I still get the same error message from TWRP as above.
Since it says that I supposedly don’t have enough free space, I looked for a way to change that and came across a thread which suggested to free some space by removing system apps that are not unnecessary, I tried doing that and flashing it again, but that also wasn’t successful.
My phone also has more than 10gb of free space.
I also tried to change the „assert“ line in the updater-script of the update, but I did not find any such line in the updater-script document in the zip file?
Does anyone know what causes this error message and what I can do to successfully update my phone?
And I was also wondering what would happen if I just let my phone regularly update it over settings?
It says that root is detected and my phone would be un-rooted once the after updating.
However, the update shown is only 1839mb so I’m very hesitant to do it.
But if I went through with this, would I just have to reroot my phone?
Will my recovery be replaced with the stock recovery, or will it remain TWRP?
Will my Bootloader get locked again?
Thank you so much for taking the time to read this, I appreciate it.
With kind regards,
Mutambo23
I was trying to update the OS on my Nexus 7 2013. I was able to connect it to my PC and unlock it and erase user data using adb commands. But after that it will not go past the Google logo in Recovery or regular Start mode. When I run "adb devices" it does not show up, though my computer does see it since I can run the lock/unlock adb commands and they work. I have uninstalled/reinstalled different adb drivers for the devices. I've tried using 2 different PCs. I can not get adb to fully recognize the device. I tried the Skipsoft Android Toolkit, and it too reports "no device detected".
Have I completed bricked the device? Or is there some way out of this that I haven't though of/found on the internet yet?
I hope someone here can help me!
Thanks!
Assuming you're on stock, try flashing a factory image from Google themselves. This reflashes everything, like stock OS, recovery, bootloader, etc. I'd choose the latest version found here: https://developers.google.com/android/images#razor As long as you understand that this wipes data, then give this a shot and let us know the results!
I found the "Nexus Root Toolkit" windows app. It was able to communicate with the Nexus 7 and restore the factory ROM and I could get it to boot! Now, I've tried about a dozen times to install LIneage, but it keeps getting an error the point of trying to install the ROM, and I haven't figured out what the error means or how to correct it. I've tried multiple TWRP versions and Lineage OS versions. It's driving me nuts!
adamwsh said:
I found the "Nexus Root Toolkit" windows app. It was able to communicate with the Nexus 7 and restore the factory ROM and I could get it to boot! Now, I've tried about a dozen times to install LIneage, but it keeps getting an error the point of trying to install the ROM, and I haven't figured out what the error means or how to correct it. I've tried multiple TWRP versions and Lineage OS versions. It's driving me nuts!
Click to expand...
Click to collapse
Are you trying to install the official version of 17.1? If so, you'll need to look at the install guide on the LineageOS website here: https://wiki.lineageos.org/devices/flox/install
As far as I can tell, you cannot use TWRP, or at least the official TWRP, with this image. You'll need to use the LOS 17.1 Recovery found on the downloads page. If you haven't already, you're going to need to repartition the device with the instructions found on the install guide that I linked.
If this isn't the ROM in question check out the thread for that ROM and see if anyone else has any issues with installation.
NTGDeveloper said:
Are you trying to install the official version of 17.1? If so, you'll need to look at the install guide on the LineageOS website here: https://wiki.lineageos.org/devices/flox/install
As far as I can tell, you cannot use TWRP, or at least the official TWRP, with this image. You'll need to use the LOS 17.1 Recovery found on the downloads page. If you haven't already, you're going to need to repartition the device with the instructions found on the install guide that I linked.
If this isn't the ROM in question check out the thread for that ROM and see if anyone else has any issues with installation.
Click to expand...
Click to collapse
Thank you! I did manage to get 18.1 to flash and load, after using a repartiion tool I found. However, I can't get GAspps to load, saying there isn't enough room on the partition. Now, I'm trying to use NRT to get back to stock (like I was able to do earlier) but now it is getting stuck at the Android 6 startup animation (4 round icons). I'm wondering if it is because I ran the partition update and somehow have to put that back to get the stock ROM to work.
The only suggestion that I would have is to flash the smallest GApps package possible, and before flashing LOS 18.1, wiping pretty much everything, then flashing LOS and GApps. Since OpenGApps doesn't make an Android 11 package yet, I don't know much about the other package providers, but that's all that I can think of. Hope this helps!
NTGDeveloper said:
The only suggestion that I would have is to flash the smallest GApps package possible, and before flashing LOS 18.1, wiping pretty much everything, then flashing LOS and GApps. Since OpenGApps doesn't make an Android 11 package yet, I don't know much about the other package providers, but that's all that I can think of. Hope this helps!
Click to expand...
Click to collapse
I wound up flashing Stock Android 5.0 and it worked. Now I'm updating to 6 via the software upgrade in the OS itself. I feel like this thing is just too old and not large enough memory to handle a custom OS.