i tried rollback from Oreo to Nought. after flashing .img files through TWRP i got error like.......,
Error
Func no: 10 (boot image)
error no: 2 (load failed)
please help. suggest the Oreo stock boot.img link
thanks in advance
if same post already exist pls link me through
i searched xda i didn't find a solution.
i've unlocked bootloader !
babu.123 said:
i tried rollback from Oreo to Nought. after flashing .img files through TWRP i got error like.......,
Error
Func no: 10 (boot image)
error no: 2 (load failed)
please help. suggest the Oreo stock boot.img link
thanks in advance
if same post already exist pls link me through
i searched xda i didn't find a solution.
i've unlocked bootloader !
Click to expand...
Click to collapse
Roll-back is possible, but not like that.
To help or suggestions what you I can try. Will need to know what you flashed, where you flashed it, what was any message after or during flashing.
Also need to know if twrp also gives this type of message, or if it boots.
As far as link to Oreo stock images. Need to know what model and build number. (You know there are almost 10 model/region combo's and each has at least 3 builds)
mrmazak said:
Roll-back is possible, but not like that.
To help or suggestions what you I can try. Will need to know what you flashed, where you flashed it, what was any message after or during flashing.
Also need to know if twrp also gives this type of message, or if it boots.
As far as link to Oreo stock images. Need to know what model and build number. (You know there are almost 10 model/region combo's and each has at least 3 builds)
Click to expand...
Click to collapse
Model : BND-al10
Got oreo as beta tester.
From firware finder app download roll back full ota package. And extracted that update.app and flashed boot, system, and stock recovery.
After that try to reboot the device. Stucked at bootloop.
Twrp is working. When i try to restore (i had backup the system, ext. Data) restore process success but error ahows as
Alert
Update the system again
Error
Func no: 10 (boot)
Error no: 2 ( load failed).
I tried another zip files to flash through memory card but zip loading failed in twrp.
babu.123 said:
Model : BND-al10
Got oreo as beta tester.
From firware finder app download roll back full ota package. And extracted that update.app and flashed boot, system, and stock recovery.
After that try to reboot the device. Stucked at bootloop.
Twrp is working. When i try to restore (i had backup the system, ext. Data) restore process success but error ahows as
Alert
Update the system again
Error
Func no: 10 (boot)
Error no: 2 ( load failed).
I tried another zip files to flash through memory card but zip loading failed in twrp.
Click to expand...
Click to collapse
Should have used hwota or hurupdater to flash the fullota, not extract the images, but too late for that.
Wow, what a mess.
For starters, to explain some of what seems to have happened.
Nougat and oreo have different partitions. Not only in name but also location.
Twrp cannot create any partition.
That being said, Oreo does not have a boot or recovery partition, so where did you flash the boot.img and recovery.img
It is obvious the stock recovery flash was not to "recovery_ramdisk" because twrp still working.
Not quite sure what parts were in you backup that you tried. And the " other zip " is a mystery.
I would think, since twrp is loading that using hurupdater might still be an option.
Thanks for your advice. Get back to system with oreo with the help of hurupdater.
1st i have no idea what is hurupdater is. But i Google for it. And now i am able use my mobile.
Thanks a lot
mrmazak said:
Should have used hwota or hurupdater to flash the fullota, not extract the images, but too late for that.
Wow, what a mess.
For starters, to explain some of what seems to have happened.
Nougat and oreo have different partitions. Not only in name but also location.
Twrp cannot create any partition.
That being said, Oreo does not have a boot or recovery partition, so where did you flash the boot.img and recovery.img
It is obvious the stock recovery flash was not to "recovery_ramdisk" because twrp still working.
Not quite sure what parts were in you backup that you tried. And the " other zip " is a mystery.
I would think, since twrp is loading that using hurupdater might still be an option.
Click to expand...
Click to collapse
Thanks for that idea. It worked. Now my mobile is working.
Using hurupdater flashed stock rom of full ota. Thanks a lot
Related
Hi all,
I re-installed stock rom and stock recovery and now i can receive official 7.0 OTA but when it tries to install the OTA on stock recovery, (after %24 processing) it says this error on attachment.
Did you restore untouched stock system image + boot image + stock recovery?
Tarima said:
Did you restore untouched stock system image + boot image + stock recovery?
Click to expand...
Click to collapse
I'd already restored stok image + stock recovery but I didn't know that I should restore boot image too. I was thinking that restoring stock image include also boot image. So should I restore boot image too?
Sent from my HTC 10 using XDA-Developers mobile app
YEK1907 said:
I'd already restored stok image + stock recovery but I didn't know that I should restore boot image too. I was thinking that restoring stock image include also boot image. So should I restore boot image too?
Click to expand...
Click to collapse
Yes I believe so. Look at the general steps in this thread:
http://forum.xda-developers.com/htc-10/how-to/guide-how-to-ota-receive-corrupt-message-t3378187
I would try restoring the boot image first, and if it still doesn't work then you can also try one of the stock recovery zips from the above thread.
Tarima said:
Yes I believe so. Look at the general steps in this thread:
http://forum.xda-developers.com/htc-10/how-to/guide-how-to-ota-receive-corrupt-message-t3378187
I would try restoring the boot image first, and if it still doesn't work then you can also try one of the stock recovery zips from the above thread.
Click to expand...
Click to collapse
Unfortunately after flashing boot image that i found inside this zip http://forum.xda-developers.com/htc...ry-ruu-ota-t3359297/post69350016#post69350016
i can not even receive the ota. it says this error :
"Can't update software"
"There was unexpected error and the file system may be corrupted etc...."
Yes now try the thread I quoted you regarding the corrupt system. Use one of the stock recoveries from that thread as they have a line in the zip package to erase the Devinfo partition.
I wasn't able to find the one matching my exact software version l, so I flashed a previous version for my phone from that thread, and with my Devinfo now erased I then flashed the latest stock recovery.img matching my firmware.
Tarima said:
Yes now try the thread I quoted you regarding the corrupt system. Use one of the stock recoveries from that thread as they have a line in the zip package to erase the Devinfo partition.
I wasn't able to find the one matching my exact software version l, so I flashed a previous version for my phone from that thread, and with my Devinfo now erased I then flashed the latest stock recovery.img matching my firmware.
Click to expand...
Click to collapse
Solved. Thank you for help.
Yesterday, after rom installation, i'd installed custom recovery for rooting and using Titanium Backup and then i think i couldn't install correct stock recovery.
Today i tried to re-install the stock rom, and directly check ota. Now i am on Android 7.0
Hi,
I get on my OP3 this issue when I start the phone.
it dissappeers in 5 sec. Phone is working fine.
"the dm verity is not started in enforcing mode".
Help? kiss
YourTheBest said:
Hi,
I get on my OP3 this issue when I start the phone.
it dissappeers in 5 sec. Phone is working fine.
"the dm verity is not started in enforcing mode".
Help? kiss
Click to expand...
Click to collapse
It is just a warning. This is no issue and from the kernel.
I managed (i do not know how i have done this) to install oos beta 8 with supersu and without this message.
I experimented a little bit. I flashed the extracted beta 8 firmware and flashed the system via fastboot.
But i do not know why this message is completly away from my phone.
If you don't want to see it flash stock recovery
I did the following..
1. Sideload OxygenOS 3.2.6 from TWRP
2. Flash stock recovery from OnePlus downloads
3. Sideload from stock recovery Open Beta 8
Stock recovery is rewritten by new recovery and no more dm error.
Oneplus 3 dm-verity verification failed when i boot
https://forums.oneplus.net/threads/...ailed-when-i-boot.476968/page-3#post-15476095
But what is causing this problem in the first place? Is it because twrp is give permissions to make changes to the /system partition? And this dm-verity thing, will it cause any problems if left as it is?
ali.jujara said:
But what is causing this problem in the first place? Is it because twrp is give permissions to make changes to the /system partition? And this dm-verity thing, will it cause any problems if left as it is?
Click to expand...
Click to collapse
No, you can leave it there, it's just a warning.
Sent from my OnePlus 3 using Tapatalk
I found simple fix.
just flash CB 7 firmware and modem throuth twrp.
https://www.androidfilehost.com/?fid=457095661767116249
ZeppeMan said:
I did the following..
1. Sideload OxygenOS 3.2.6 from TWRP
2. Flash stock recovery from OnePlus downloads
3. Sideload from stock recovery Open Beta 8
Stock recovery is rewritten by new recovery and no more dm error.
Oneplus 3 dm-verity verification failed when i boot
Click to expand...
Click to collapse
.
So no more twrp in build 8. you're rocking stock recovery right? if yes, how you're able to gain root? as far as I know, there are no ways to root oxygen os 8/9 from inside.
.
Ps. I wanna lock my bootloader. flash build 9 with stock recovery. like new intact phone. plus, I wanna gain root from inside (without the help of twrp). any help or opinion?
I was on OB10. i unlock bootloader and flashed twrp. after this dm-verity error keeps coming at every boot. I tried formatting to ext4 file system but no luck. After some time i gave up and flashed OB10 again. Any idea on how to unlock and flash custom roms without dm-verity error? If I revert back to 3.2.8, can i flash the nougat roms without error?
Search the forum . Everything is answered
here
Hi, earlier, I wanted to change the rom of my mi 5s. I've got an error 7 on twrp during the flash. I tried many things: edit the installation script, format all the data, update and downgrade TWRP, and finally perform a fastboot flash using mi flash and the last one worked. But I am not longer able to flash a custom rom without getting error 7 after the "Patching system image unconditionally" message. I've tested lineage, havoc, pixel experience, miui, even 8.1 rom but same result. I'm stuck with fastboot global miui 10
Btw, I think that after the error the partition are corrupted since I can't repair them with TWRP.
I don't know what I can do more.
edit: I tried to lock and relock bootlander, still geting the same error. I'm stuck on Oreo
bob_bricoleur said:
Hi, earlier, I wanted to change the rom of my mi 5s. I've got an error 7 on twrp during the flash. I tried many things: edit the installation script, format all the data, update and downgrade TWRP, and finally perform a fastboot flash using mi flash and the last one worked. But I am not longer able to flash a custom rom without getting error 7 after the "Patching system image unconditionally" message. I've tested lineage, havoc, pixel experience, miui, even 8.1 rom but same result. I'm stuck with fastboot global miui 10
Btw, I think that after the error the partition are corrupted since I can't repair them with TWRP.
I don't know what I can do more.
edit: I tried to lock and relock bootlander, still geting the same error. I'm stuck on Oreo
Click to expand...
Click to collapse
I think that i figured out something, I am able to flash system.img file using fastboot but I can't flash zip rom using recovery.
As anyone encounter this ?
Did you try reflash twrp latest version?
Sorry for my bad English grammar,
I have stucked in TWRP for all this day, flashed many different roms and got the same message :
"E1001: Failed to update system/vendor image.
Updater process ended with ERROR:7
Error installing zip file '...' "
My base is 11.0.4 xiaomi.eu rom (MIUI 11, Android 10), start flashing 11.0.3 custom rom (MIUI 11, Android 9) and got that ERROR, then flashed Havoc/ASOiP rom, end up with flashing STOCK MIMAX3Global_V11.0.2.0.QEDMIXM on Mi offficial site via TWRP but still no luck, samething.
I have already tried lastest TWRP 3.3.1, 3.2.3, PitchBlack Recovery, and modified Updater-Script aswell (Delete 1st line).
Thank you for your help ! :crying:
Have you tried any of these tips?
Did you tried any android 10 ROMs?
I'm not sure if the downgrade from 10 to 9 is possible at all
I had wiped my system partition at one point and got this as well. Fixed by using the mi flash tool and the full system image (not a twrp / orange fox rom) and then wiped my data partition to get rid of the boot password. I don't know if anti rollback effects 10 to 9. Look into it though. You're looking for a fastboot rom. Just make sure to not "clean and lock". I'm having trouble finding the fastboot rom I found to fix it but it should come in a .tgz file. Good luck
On my way to installing LineageOS I tried to downgrade Android version 11 -> 10. Unfortunately I used the WRONG INCOMPATIBLE firmware files from google's website (I think for 3 XL), that's why I have a brick now. ''Device is corrupt and no bootup possible.''
Access to Fastboot and STOCK Recovery Mode is possible.
Bootloader is Locked Now (it *was* unlocked before for flashing the firmware)
ADB is not working (since I'm getting stuck on ''google'' symbol when booting up I can't go to Developer Settings)
Factory Preset from Recovery Mode fails: ''can't send spi messages.'' Same Brick occurs.
With No Access to ADB (is it possible to set up from fastboot mode without enabling it in den Developer Options?) I can't try stuff.
And with the bootloader locked no way to flash a new Rom right?
I have NO IDEA what to do next, any IDEAS??
Thank you!!
#brick
Since you can get to recovery you should download the latest ota and sideload it from recovery.
https://developers.google.com/android/images
you should flash the stock image from recovery. Basically unzip it all and just run "flash-all.bat"
41rw4lk said:
Since you can get to recovery you should download the latest ota and sideload it from recovery.
Click to expand...
Click to collapse
Thank you, this worked perfectly fine, since you don't need an unlocked bootloader to flash this system image.
However, I am facing a new problem on my way to installing TWRP Recovery Image...!!
CMD gives me THIS log:
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
- the device is unlocked (I even relocked it and unlocked it again, didn't work)
- I tried one other older .img for my phone from official twrp.me website, didn't work
Any Ideas?
dadu1257 said:
Thank you, this worked perfectly fine, since you don't need an unlocked bootloader to flash this system image.
However, I am facing a new problem on my way to installing TWRP Recovery Image...!!
CMD gives me THIS log:
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
- the device is unlocked (I even relocked it and unlocked it again, didn't work)
- I tried one other older .img for my phone from official twrp.me website, didn't work
Any Ideas?
Click to expand...
Click to collapse
You need the BL unlocked to flash unsigned/unofficial images, so make sure yours is unlocked. That being said, I'm not sure how solid twrp is for our device, I've never tried it. Twrp was/is a little iffy for android 10 never mind 11. Most around here just use fastboot to do what needs to be done. Most of it is pretty quick and painless, and twrp is not really necessary.
dadu1257 said:
Thank you, this worked perfectly fine, since you don't need an unlocked bootloader to flash this system image.
However, I am facing a new problem on my way to installing TWRP Recovery Image...!!
CMD gives me THIS log:
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
- the device is unlocked (I even relocked it and unlocked it again, didn't work)
- I tried one other older .img for my phone from official twrp.me website, didn't work
Any Ideas?
Click to expand...
Click to collapse
I'm pretty sure you would have to downgrade to android 9 (pie) and install a custom kernel to get twrp to install. Unless you want to rock android pie - like I currently am (Bootlegger's 9 - I like my smartbar customizations) - it's best to give up on TWRP and just use fastboot commands for android 10 and up.
If you do decide to downgrade to pie the elementalX kernel (ElementalX-P3a-1.06) works fine with twrp and is available on their site. Temp boot twrp via fastboot, flash kernel, flash twrp zip file, reboot to recovery and flash magisk zip for root (if you want root). But it may be hard to find older pie ROMs out in the wild to flash since devs have dropped support and will be focused on android 10/11.
teemothay said:
I'm pretty sure you would have to downgrade to android 9 (pie) and install a custom kernel to get twrp to install. Unless you want to rock android pie - like I currently am (Bootlegger's 9 - I like my smartbar customizations) - it's best to give up on TWRP and just use fastboot commands for android 10 and up.
If you do decide to downgrade to pie the elementalX kernel (ElementalX-P3a-1.06) works fine with twrp and is available on their site. Temp boot twrp via fastboot, flash kernel, flash twrp zip file, reboot to recovery and flash magisk zip for root (if you want root). But it may be hard to find older pie ROMs out in the wild to flash since devs have dropped support and will be focused on android 10/11.
Click to expand...
Click to collapse
Unlike most of the LineageOS Tutorials out there is used the Custom Recovery from Lineage to install LIneageOS! It was super easy, a few ADB commands and here it is. No Root, no TWRP whatsoever.
Follow wiki lineageos devices website instructions. Here you may also find the recovery data.
Thx guys/girls!
dadu1257 said:
Unlike most of the LineageOS Tutorials out there is used the Custom Recovery from Lineage to install LIneageOS! It was super easy, a few ADB commands and here it is. No Root, no TWRP whatsoever.
Follow wiki lineageos devices website instructions. Here you may also find the recovery data.
Thx guys/girls!
Click to expand...
Click to collapse
Cool. No more soft brick for you :good: Congrats on sorting things out. :highfive:
BUT I still cannot install TWRP Recovery on LineageOS 17. I am getting the same problem as quoted below.
I want to perform Nandroid Backups, any other way to that if TWRP doesn't want me? Maybe with a Magisk Root and some app from F Droid?
?
thanks
dadu1257 said:
Thank you, this worked perfectly fine, since you don't need an unlocked bootloader to flash this system image.
However, I am facing a new problem on my way to installing TWRP Recovery Image...!!
CMD gives me THIS log:
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
- the device is unlocked (I even relocked it and unlocked it again, didn't work)
- I tried one other older .img for my phone from official twrp.me website, didn't work
Any Ideas?
Click to expand...
Click to collapse
dadu1257 said:
BUT I still cannot install TWRP Recovery on LineageOS 17. I am getting the same problem as quoted below.
I want to perform Nandroid Backups, any other way to that if TWRP doesn't want me? Maybe with a Magisk Root and some app from F Droid?
?
thanks
Click to expand...
Click to collapse
Twrp doesn't work very well on android 10 and above, there is a twrp install guide around here, but not much has come from it. When was the last time anyone actually made and used a nandroid backup? Not that backups aren't important, but that's a little antiquated. Besides, most are really trying to backup data, which is a shared partition on A/B devices. Generally, restoring data on A/B devices causes more problems than anything. Most data backups can be done with an app and/or making a backup of your internal storage. As for more sensitive things like your persist partition and whatnot, you can always use the 'dd' command to back those partitions up.
I should clarify, restoring nand backups of data causes more problems on A/B devices, apps that restore data and settings tend to handle it better.
Now having a different problem
I tried to install Magisk following this guide https://magisk.download/root-pixel-3a-3a-xl/
When I try to flash magisk_patched.img in fastboot, it flashes, but reboots to fastboot with "error boot prepare" displayed.
I am stuck in Fastboot now.
How can I get out of that?
I used the boot.img from the google firmware android 10 I built Lineage on. Should I use a boot.img from LineageOS .zip? Is there anything like this?
What is dm-verity?
Can I get to my previous unrooted device?
I have a Pixel 3aXL with LineageOS 17
''bootslot: b
enter reason: error boot prepare''
dadu1257 said:
Now having a different problem
I tried to install Magisk following this guide https://magisk.download/root-pixel-3a-3a-xl/
When I try to flash magisk_patched.img in fastboot, it flashes, but reboots to fastboot with "error boot prepare" displayed.
I am stuck in Fastboot now.
How can I get out of that?
I used the boot.img from the google firmware android 10 I built Lineage on. Should I use a boot.img from LineageOS .zip? Is there anything like this?
What is dm-verity?
Can I get to my previous unrooted device?
I have a Pixel 3aXL with LineageOS 17
''bootslot: b
enter reason: error boot prepare''
Click to expand...
Click to collapse
Reflash the boot.img from Los17 to get back to proper boot up, then patch Los17 boot.img and flash that to have root.
41rw4lk said:
Reflash the boot.img from Los17 to get back to proper boot up, then patch Los17 boot.img and flash that to have root.
Click to expand...
Click to collapse
Where is the boot.img from Lineage? There is no such file in the Lineage folder I downloaded.
dadu1257 said:
Where is the boot.img from Lineage? There is no such file in the Lineage folder I downloaded.
Click to expand...
Click to collapse
A lot of devs wil upload the boot.img separately when they upload the rom, so wherever you downloaded Los from check there. If you just have a payload.bin file in your zip, you can always dump it and grab the boot.img there. You could always just reflash Los period to get boot back, then us 'dd' command to backup your own boot.img.
custom recovery for lineageos 17 based on android 10?
teemothay said:
I'm pretty sure you would have to downgrade to android 9 (pie) and install a custom kernel to get twrp to install. Unless you want to rock android pie - like I currently am (Bootlegger's 9 - I like my smartbar customizations) - it's best to give up on TWRP and just use fastboot commands for android 10 and up.
If you do decide to downgrade to pie the elementalX kernel (ElementalX-P3a-1.06) works fine with twrp and is available on their site. Temp boot twrp via fastboot, flash kernel, flash twrp zip file, reboot to recovery and flash magisk zip for root (if you want root). But it may be hard to find older pie ROMs out in the wild to flash since devs have dropped support and will be focused on android 10/11.
Click to expand...
Click to collapse
thanks!
I got Lineage 17 w/ Magisk root running now and want to perform a full NANDroid Backup.
After some research it seems crucial to have a custom recovery like TWRP for that. There is the online nandroid thing - but I would need CWM or anything like this to restore?!
So my question is
a) is there another custom recovery (compatible with Pixel 3a XL w/ lineage 17 based on android 10) I can install and perform Nandroid backup with?
b) any other solution to perform this backup and restore? I heard there are cmd commands for that as well , but I'm a noobie not so sure to do that.
of course there are several apps out there to backup data.. but I don't trust ''any'' app to get root permission. In F Droid I couldn't find what I was looking for.
thank you for help!