I just received my pixel 3a, and try to install a custom rom on it using twrp. But while installing TWRP I faced an error "Error verifying the received boot.img: Invalid Parameter". I spent a couple of hours trying to find any info about it in the internet. But nothing was really helpful. Is there any way to solve it or another way to perform custom rom installation?
Btw bootloader is unlocked, Android version - 11.
Any help will be appreciated.
Sry for my English.
I don't think they fixed the partition issue yet. I heard no news about it. I would suggest following the instructions from the rom you're trying to flash. Usually it is a fastboot sequence of flashing partitions manually through fastbootd.
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
Overfloww said:
I just received my pixel 3a, and try to install a custom rom on it using twrp. But while installing TWRP I faced an error "Error verifying the received boot.img: Invalid Parameter". I spent a couple of hours trying to find any info about it in the internet. But nothing was really helpful. Is there any way to solve it or another way to perform custom rom installation?
Btw bootloader is unlocked, Android version - 11.
Any help will be appreciated.
Sry for my English.
Click to expand...
Click to collapse
TWRP on the Pixel is pretty much dead.
Related
Hi,
I got my Moto G 2015 XT1541 running with Android 5.1.1 official rom and TWRP Osprey 3.0.0 R2. I just got the official message to upgrade to Marshmallow, but when I to upgrade TWRP comes with the following error: Updater process ended with ERROR: 7
I've placed a full log here: recovery.log
I also tried installing an other OTA file - (2GB Retail EU OTA): Download - thanks to @Osid - from here, but got the same error.
Also, the official update is version 24.41.33.en.EU, and the above file 23.41.47 and is already on my phone, according to "About Phone".
Anyway: Can someone please help me to get past this error and update to the official 24.41.33.en.EU? I've read about changing an updater-script file in the zip if you have one, but this is a block.map.
Thanks allot!
robert1010 said:
Hi,
I got my Moto G 2015 XT1541 running with Android 5.1.1 official rom and TWRP Osprey 3.0.0 R2. I just got the official message to upgrade to Marshmallow, but when I to upgrade TWRP comes with the following error: Updater process ended with ERROR: 7
I've placed a full log here: recovery.log
I also tried installing an other OTA file - (2GB Retail EU OTA): Download - thanks to @Osid - from here, but got the same error.
Also, the official update is version 24.41.33.en.EU, and the above file 23.41.47 and is already on my phone, according to "About Phone".
Anyway: Can someone please help me to get past this error and update to the official 24.41.33.en.EU? I've read about changing an updater-script file in the zip if you have one, but this is a block.map.
Thanks allot!
Click to expand...
Click to collapse
Flash the stock recovery and it will work. Official OTAs and custom Recovery's will not work together.
nobreak1970 said:
Flash the stock recovery and it will work. Official OTAs and custom Recovery's will not work together.
Click to expand...
Click to collapse
Both update methods, as described above, fail. Method 1: using the phone's system updater, method 2: using the official(?) OTA upgrade files provided on this site.
But it looks like the OTA file is of a version I already have. See attachment.
Sorry, I misread your reply. I am looking for the stock recovery now keep you posted.
nobreak1970 said:
Flash the stock recovery and it will work. Official OTAs and custom Recovery's will not work together.
Click to expand...
Click to collapse
Ok, I took the recovery.img from "XT1541_OSPREY_RETEU_2GB_5.1.1_LPI23.72-33_cid7_subsidy-DEFAULT_CFC.xml", my version was 23.72-47. Hope that doesn't really matter. But is was the only 2GB European ROM I could find here.
So I used fastboot to flash that and tried the system update again. At the beginning it looked hopeful; It was showing the Installing System Update with the progress bar, but then briefly the error icon and rebooted without making any changes.
If I need to re-lock and/or un-root to fix this, can it be don without wiping everything?
Thanks again!
robert1010 said:
Ok, I took the recovery.img from "XT1541_OSPREY_RETEU_2GB_5.1.1_LPI23.72-33_cid7_subsidy-DEFAULT_CFC.xml", my version was 23.72-47. Hope that doesn't really matter. But is was the only 2GB European ROM I could find here.
So I used fastboot to flash that and tried the system update again. At the beginning it looked hopeful; It was showing the Installing System Update with the progress bar, but then briefly the error icon and rebooted without making any changes.
If I need to re-lock and/or un-root to fix this, can it be don without wiping everything?
Thanks again!
Click to expand...
Click to collapse
Anyone who can help me with this please?
I am a Chinese and the phone is N9150.But i don't find my phone model in some ROMs like the RR/Oreo...ect.I download the files related N915F/FY/G.I don't know if i am right.
Android version is 6.0.1 with root and the TWRP version is 3.1.0.
I try ROMs include
·RR-N-v5.8.4-20170813-tbltexx-Official
·lineage-15.1-20180123-UNOFFICIAL-tbltexx
·Slim-tbltexx-7.1.1.build.0.7-UNOFFICIAL-20170223-0955.
They all says "Updater process ended with error: 7
Error installing zip file '/external_sd/RR-N-v5.8.4-20170813-tbltexx-Official.zip"
Before flash the roms i wipe Dalvik/art cache,system,data,cache ect.But it seems no use.
I don't know how to solve this problem.I have seen many posts to find some solutions,but my English is poor so i can't get the useful information for me.
Above all,thanks anyone who can help me!
OK,I have solved this problem by using the pit,this make the phone changed to the HK version.
Hey everyone,
i usually don't post questions but i've been on pretty much every forum the web has to offer and am still stuck so i'll try my luck here.
i'm currently running lineage 7.1 on my mi4c, i've used another phone for a while but now that my mi4c has a new battery i wanted to start using it again, is also decided this would be the time to update it to android oreo or pie, this however seems to be impossible.
i can only use twrp up to 3.1.1.1, all higher (and unofficial versions) will not boot via fastboot 'dtb not found' or when flashed via older twrp will freeze on boot screen.
whenever i try to install a new rom it tells me 'error code 7', when i remove the 'assert' lines in the update it gives me 'error code 6'
my device is unlocked, i have checked this in fastboot.
do i have to install miui again before installing another rom? do i have to go back to the standard recovery? i'm currently running out of ideas and hope you guys might be able to help me. maybe i'm overlooking something simple.
kind regards,
Monstreys
Hi! I don't know if this is a coincidence or not, but I was about to start a similar thread.
I try to do exactly what you are doing. I want to install LineageOS 16, unofficial ROM.
For this you need a newer TWRP, like 3.2.3.0, but it doesn't work 'dtb not found' like you said. I found out that this doesn't work because you need to have nougat bootloader. Most probably you have lollipop bootloader like I have, and thats why newer versions of TWRP are not working. I think the only way to update your bootloader to a nougat one is to flash the latest MIUI ROM. But, unfortunately, when you do that the bootloader gets locked, and I can't unlock it via MiUnlock due to Error:20091 when I try to link the phone to the Mi account. In MiUnlock it gives me the "this account cannot unlock the phone" or something like that.
Now I removed the "assert" lines from my rom and flashed it without the error 7 or 6. Some error still apears, but it also apears when I flash LineageOS 14.1, and that version is working even with those 2 errors I can't remember during flash.
After I flashed LineageOS, I flashed gapps and then superSU, and now my mi4c is stuck on mi logo for about 20 minutes, and I think it will remain that way.
So, there are 2 things we need to solve. We need to find a way to install latest MIUI without relocking the bootloader because I can't unlock it via MiUnlock, or to find out why after I flashed LineageOS 16 it gets stuck on MI logo.
I think I found the solution. Do exactly what this guy is doing here and it might work.
https://forum.xda-developers.com/showpost.php?p=78640737&postcount=63
I followed that guy instructions and I managed to install TWRP 3.2.3.0 and LineageOS 16, and it booted. Now I am at the setup part but it has very big lag...
makaveli97 said:
I think I found the solution. Do exactly what this guy is doing here and it might work.
https://forum.xda-developers.com/showpost.php?p=78640737&postcount=63
I followed that guy instructions and I managed to install TWRP 3.2.3.0 and LineageOS 16, and it booted. Now I am at the setup part but it has very big lag...
Click to expand...
Click to collapse
i
i was unable to install the patch file, this nonetheless fixed my problem, thanks!!
if above not working, another method to do it based on my method.
https://forum.xda-developers.com/showpost.php?p=81573941&postcount=199
makaveli97 said:
I think I found the solution. Do exactly what this guy is doing here and it might work.
https://forum.xda-developers.com/showpost.php?p=78640737&postcount=63
I followed that guy instructions and I managed to install TWRP 3.2.3.0 and LineageOS 16, and it booted. Now I am at the setup part but it has very big lag...
Click to expand...
Click to collapse
My MI4C has been successfully flushed into lineage-17.1-20200220-UNOFFICIAL-libra.zip. It has been updated on TWRP 3.1.1 and keeps reporting error 7, and then abandoned TWRP3.1.1 and flashed into OrangeFox-R10.0-1-Stable-libra.zip After brushing libra-aqua_firmware_7.2.9.zip on this REC, you can flash lineage-17.1. I do n’t think it will be impossible to refresh because of partition problems. If you only need to upgrade lineage-17.1, you can refer to this method.:good::good:（Translation is not easy to use）
celrau said:
There is a 3.2.x around. If you don't want to bother go in the zip, /META-INF/com/google/android/ and delete the first lines (the ones starting with "assert") from updater-script, save and flash again.
Click to expand...
Click to collapse
rianawirawan said:
Right now, i'm using 3.1.1 -1 btw
It's latest twrp ver from official
Click to expand...
Click to collapse
TWRP-20190418-3.3.0.0-libra.img for the Xiaomi Mi 4c, by GuaiYiHu :
https://androidfilehost.com/?fid=1395089523397945946
Latest firmware for the Xiaomi Mi 4c libra :
https://github.com/XiaomiFirmwareUp...iui_MI4c_V10.1.1.0.NXKCNFI_13b9b312d0_7.0.zip
I have been struggling to install Pixel Experience Android 12 on my Poxo X3 NFC.
I had PE Android 11 before. When I tried to flash Android 12 I get following error
assert failed: update_dynamic_partition(package_extract_file("dynamic_partition_op_list"))
Updater process ended with ERROR: 1
Error installing zip file ...
What I tried
1, Install latest firmware
2. Format Data
3. Wipe data, dalvik, cache
3. Sideloading Custom Rom
Can someone help me to revive my device please?
Thanks a lot
Hello, on my wife's X3NFC I had to flash the latest Full ROM (12.5.7) via Fastboot.
Then I was able to install the lA12 PE. I don't know why I had to do this, but it worked.
She didn't like A12 PE and now A11 PE is running again on her Phone
Maybe (I heard about that) it works too, if you only flash the super.img from latest Fastboot-Image via Recovery.
SmartJuwel said:
Hello, on my wife's X3NFC I had to flash the latest Full ROM (12.5.7) via Fastboot.
Then I was able to install the lA12 PE. I don't know why I had to do this, but it worked.
She didn't like A12 PE and now A11 PE is running again on her Phone
Maybe (I heard about that) it works too, if you only flash the super.img from latest Fastboot-Image via Recovery.
Click to expand...
Click to collapse
I installed MIUI fastboot rom. Then I tried to flash PE A12 rom without any issues. But after successful completion, phone reboots to bootloader (Fastboot). Can you tell me what I am doing wrong?
Can you please give me steps to install PE after you've installed MIUI fastboot rom?
1st installed latest MIUI via MiFlash
Booting successful into MIUI
Flashing TWRP in Fastboot-Mode
Booting into TWRP, install ROM, wipe Caches and format data.
Reboot Phone
i'm in this very predicament. Still on PE11 Plus Edition and can't flash PE12 giving me the very same ERROR. Can someone pls post the sure way to get this done properly? Links to roms that must be flashed first would be very appreciated...
Snakeatermgs said:
i'm in this very predicament. Still on PE11 Plus Edition and can't flash PE12 giving me the very same ERROR. Can someone pls post the sure way to get this done properly? Links to roms that must be flashed first would be very appreciated...
Click to expand...
Click to collapse
SmartJewel (Post above you) told you how to do it
I recently bought myself a new phone ( the same above and now I'm stuck trying to root it )
I've attached the details of my device in the image below
I successfully managed to unlock the bootloader yesterday and now I have no idea on where to find the stock rom.
Any help appreciated
Thanks
zachabz said:
I recently bought myself a new phone ( the same above and now I'm stuck trying to root it )
I've attached the details of my device in the image below
I successfully managed to unlock the bootloader yesterday and now I have no idea on where to find the stock rom.
Any help appreciated
Thanks
Click to expand...
Click to collapse
I have the exact same phone as you.
I used this post to root: https://forum.xda-developers.com/t/rooting-oneplus-nord-2-ce-lite.4500297/
Didn't run into any problems
I have bricked this device (One Plus Nord CE 2 Lite) by flashing the unofficial twrp image for this device. Device bootloops in TWRP.
Previously, I had succesfully unlocked the bootloader and rooted this device by flashing the patched magisk boot.img by following the method mentioned in this post (https://forum.xda-developers.com/t/rooting-oneplus-nord-2-ce-lite.4500297/)
How to restore the factory image and recover from this?
Any help is appreciated.
Thanks
....double post ...already answered
...bricking impossible
NickR01 said:
I have bricked this device (One Plus Nord CE 2 Lite) by flashing the unofficial twrp image for this device. Device bootloops in TWRP.
Previously, I had succesfully unlocked the bootloader and rooted this device by flashing the patched magisk boot.img by following the method mentioned in this post (https://forum.xda-developers.com/t/rooting-oneplus-nord-2-ce-lite.4500297/)
How to restore the factory image and recover from this?
Any help is appreciated.
Thanks
Click to expand...
Click to collapse
Join telegram group of OnePlus Nord ce2 lite
I have a guide over there also others can help you restoring stock
NickR01 said:
I have bricked this device (One Plus Nord CE 2 Lite) by flashing the unofficial twrp image for this device. Device bootloops in TWRP.
Previously, I had succesfully unlocked the bootloader and rooted this device by flashing the patched magisk boot.img by following the method mentioned in this post (https://forum.xda-developers.com/t/rooting-oneplus-nord-2-ce-lite.4500297/)
How to restore the factory image and recover from this?
Any help is appreciated.
Thanks
Click to expand...
Click to collapse
Same thing happened for me.
It's booting to twrp .
Any fix?>
Droid9.9.0.1 said:
Same thing happened for me.
It's booting to twrp .
Any fix?>
Click to expand...
Click to collapse
Sir, If you have patched magisk boot.img and blank vbmeta.img files on your pc used previously for rooting this device, this will save you your precious time.
Flash the files to their appropriate partitions, the device will overwrite the partitions and boot back with root access.
If you have updated the device after root and flashed magisk to inactive slot for saving root access after OTA the above method won't work.
Installed official version.
But i need twrp for this device.
Any one installed??
Sir, TWRP image available for this device is experimental, unstable and buggy.
There is a problem that occurs when you flash twrp if you are rooted.
After flashing the device bootloops into TWRP and won't boot into system OS even if it's forced to reboot.
Even without root if flashed, twrp cant flash or wipe any data.
On the screen the errors are shown in red.[failed to mount ' / ' ](Invalid Argument)
Let's wait until a stable image is available for this device in the near future.
Thank you .
I want pixel experience on nord ce 2 lte
If any one installed . Please guide me
...pixel experience doesn't work on Nord 2 CE devices ...none of the functions are compatible with this device ...I tried more than one configurations by myself ...the few things you can get working, like Contacts App or Messages App, you can manually download and install from APKmirror or other sources ...no need to "module" these little things
...I would like to change the boot animation, for example ...but to be honest, how often and how long do you see the boot up screen???
i again damaged the os.
This time every thing not working.
it boot loops to fastboot.
Any help ?? @DerDoktore
Is there any msmtool for nord ce 2 lte
...Bootloop to fastboot???? ...that is new to me ...I know the "system damaged" Screen and a traditional Bootloop ...does it "break" the loop at fastboot??? ...or do you see half a second the fastboot screen and restart and again???
Droid9.9.0.1 said:
Same thing happened for me.
It's booting to twrp .
Any fix?>
Click to expand...
Click to collapse
Hey man, did you got any solution for the same?
this is what i tried https://unofficialtwrp.com/twrp-root-oneplus-nord-ce-2-lite/
Sorry i din't update.
I found solution and recovered.
Droid9.9.0.1 said:
Sorry i din't update.
I found solution and recovered.
Click to expand...
Click to collapse
Hey can you send me the stock firmware?
>> oneplus nord ce 2 lite ind
Droid9.9.0.1 said:
>> oneplus nord ce 2 lite ind
Click to expand...
Click to collapse
Thanks bro, finally got my device back.
Installed Oxygen os 13 beta.
Could just follow the guide/s for the Nord N20 5G since it's basically the exact same device with a different touch panel...