I am trying to flash the newly arrived CyanogenMod 14.1 Nightly ( cm-14.1-20161221-NIGHTLY-onyx ) on my Oneplus X When I try to boot twrp3022, it says "FAILED (remote: dtb not found)".
Device : Oneplus X (ONE E1003)
tried recoveries :
twrp3021
twrp3022
twrp3030
cyanogenmod14.1recoverynightly
these above mentioned recoveries gives me that dtb error.
Twrp 3020 boots succesfully but gives me error 7 (TZ Assert Failed) while trying to flash latest CM14.1 nightly.
Any help would be great.
himanshuitis said:
I am trying to flash the newly arrived CyanogenMod 14.1 Nightly ( cm-14.1-20161221-NIGHTLY-onyx ) on my Oneplus X When I try to boot twrp3022, it says "FAILED (remote: dtb not found)".
Device : Oneplus X (ONE E1003)
tried recoveries :
twrp3021
twrp3022
twrp3030
cyanogenmod14.1recoverynightly
these above mentioned recoveries gives me that dtb error.
Twrp 3020 boots succesfully but gives me error 7 (TZ Assert Failed) while trying to flash latest CM14.1 nightly.
Any help would be great.
Click to expand...
Click to collapse
Hello,
Are you on the latest bootloader?
Regards
Vatsal,
Forum Moderator.
Hi my friends
I update my mate 9 to Oreo beta. its cool.
now I want install TWRP Recovery, but in installation through fastboot, I faced with this error:
failed (remote: partition length get error)
please help me. I cannot install recovery.
thanks
where did you get the Oreo beta?
I believe the beta can be downloaded through their web site as a limited tester. My understanding of flashing recovery onto the new Android build is that you'll need a newest version of twrp to work for oreo. Most the time the new updates will mess around with the internal storage space.
ystokar said:
where did you get the Oreo beta?
Click to expand...
Click to collapse
You can get it via FH.
vang2k said:
I believe the beta can be downloaded through their web site as a limited tester.
Click to expand...
Click to collapse
The 250 users quota has long been filled unfortunately.
Sent from my MHA-L29 using XDA Labs
martin2007 said:
Hi my friends
I update my mate 9 to Oreo beta. its cool.
now I want install TWRP Recovery, but in installation through fastboot, I faced with this error:
failed (remote: partition length get error)
please help me. I cannot install recovery.
thanks
Click to expand...
Click to collapse
The recovery partitions are different in Android O. There is no working TWRP yet.
If you want to downgrade, however, there will be a solution soon.
Here is the solution (forwad)
This is TWRP to Mate 9/Android O, brought to you by FunkyHuawei. This will also work for the Mate 10, Mate 10 Pro, Mate 10 Porsche and other EMUI 8 devices.
It´s just a preliminary build so I can´t promise anything/everything will work! Keep that in mind. I´m not responsible if you brick your device.
DOWNLOAD LINK:
https://drive.google.com/file/d/0B45NCsO2AL_1NEh2aDFLM3JlYkU
It works on the Android O build here:
https://www.reddit.com/r/FunkyHuawei...id_o_beta_for/
and the official European beta.
To install:
First, have Android O running. Unlock the bootloader. Download the twrp image.
Then, run in fastboot mode:
fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
Then, reboot holding volume up, and you´ve got TWRP!
Note: With the Android O update, it is no longer possible to flash the recovery2 partition. Furthermore, the names of the partitions have changed. Please keep that in mind, and don´t mess around too much with TWRP, to be sure you don´t brick your system!
fairyland4ever said:
Here is the solution (forwad)
This is TWRP to Mate 9/Android O, brought to you by FunkyHuawei. This will also work for the Mate 10, Mate 10 Pro, Mate 10 Porsche and other EMUI 8 devices.
It´s just a preliminary build so I can´t promise anything/everything will work! Keep that in mind. I´m not responsible if you brick your device.
DOWNLOAD LINK:
https://drive.google.com/file/d/0B45NCsO2AL_1NEh2aDFLM3JlYkU
It works on the Android O build here:
https://www.reddit.com/r/FunkyHuawei...id_o_beta_for/
and the official European beta.
To install:
First, have Android O running. Unlock the bootloader. Download the twrp image.
Then, run in fastboot mode:
fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
Then, reboot holding volume up, and you´ve got TWRP!
Note: With the Android O update, it is no longer possible to flash the recovery2 partition. Furthermore, the names of the partitions have changed. Please keep that in mind, and don´t mess around too much with TWRP, to be sure you don´t brick your system!
Click to expand...
Click to collapse
It worked, I have TWRP, but my PC does not connect to ADB. I tried reinstalling all the drivers but it does not even make any sound when I connect it to USB
fairyland4ever said:
Here is the solution (forwad)
This is TWRP to Mate 9/Android O, brought to you by FunkyHuawei. This will also work for the Mate 10, Mate 10 Pro, Mate 10 Porsche and other EMUI 8 devices.
It´s just a preliminary build so I can´t promise anything/everything will work! Keep that in mind. I´m not responsible if you brick your device.
DOWNLOAD LINK:
https://drive.google.com/file/d/0B45NCsO2AL_1NEh2aDFLM3JlYkU
It works on the Android O build here:
https://www.reddit.com/r/FunkyHuawei...id_o_beta_for/
and the official European beta.
To install:
First, have Android O running. Unlock the bootloader. Download the twrp image.
Then, run in fastboot mode:
fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
Then, reboot holding volume up, and you´ve got TWRP!
Note: With the Android O update, it is no longer possible to flash the recovery2 partition. Furthermore, the names of the partitions have changed. Please keep that in mind, and don´t mess around too much with TWRP, to be sure you don´t brick your system!
Click to expand...
Click to collapse
great, that worked well. now - with the changed partition table, would you recommend rooting the phone with either of these methods: https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986 ?
Dear friend, i have same issue, kindly tell me how to change partition table?
Hi, I also have Mate 9 L09 and have exact same error message:
fastboot flash recovery twrpo.img
target reported max download size of 471859200 bytes
sending 'recovery' (26982 KB)...
OKAY [ 0.579s]
writing 'recovery'...
FAILED (remote: partition length get error)
UPDATE:
OK, I managed it by myself, haha.
For anyone else with same issue.
Since Oreo: Partition names have changed.
Use this command: fastboot flash recovery_ramdisk RECOVERY.img
"recovery" changed to "recovery_ramdisk" now.
finished. total time: 0.600s
I downloaded that special TWRP recovery image, but still get the same message. Does not work for me, any new solution available?
tobyffm said:
Hi, I also have Mate 9 L09 and have exact same error message:
fastboot flash recovery twrpo.img
target reported max download size of 471859200 bytes
sending 'recovery' (26982 KB)...
OKAY [ 0.579s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.600s
I downloaded that special TWRP recovery image, but still get the same message. Does not work for me, any new solution available?
Click to expand...
Click to collapse
You need to flash to recovery_ramdisk. Fastboot flash recovery_ramdisk twrpo.img
Hi there , so if we want to flash Oreo through fastboot , what could be the commands lines please ?
as ie : fastboot flash boot boot.img or boot_ramdisk / boot_kernel boot.img ? and so on ..
the complete list of commands, would any 1 pass it over here please ? thanks a bunch
FuM8 said:
Hi there , so if we want to flash Oreo through fastboot , what could be the commands lines please ?
as ie : fastboot flash boot boot.img or boot_ramdisk / boot_kernel boot.img ? and so on ..
the complete list of commands, would any 1 pass it over here please ? thanks a bunch
Click to expand...
Click to collapse
Well. You can flash most partitions. If you extract imgs from an oreo update.app you get the complete list (though some can't be flashed, like erecovery_*.img).
If you extract ramdisk (boot ramdisk) from update.app you flash it as fastboot flash ramdisk ramdisk.img. Kernel flashed as fastboot flash kernel kernel.img.
Recovery ramdisk as fastboot flash recovery_ramdisk recovery_ramdisk.img
To extract in Huawei Update Extractor you need to go to settings and disable checksum, it won't extract because something is up with erecovery_ramdis.img (it's misspelled too).
thank you for your reply @ ante0
Something else please .. as I tried and failed to update from MHA-L09-c432198 to Oreo I now get a bootloop error 14 iom3 , I saw on another thread some solutions, which dont work for me as I just cannot boot into twrp because of my battery not charging, even in download / recovery mode... battery three months old... and always working good
What I need to know is how can I either get my twrp saved system back through fastboot or else how can I flash - again only by fastboot mean - the stock firmware of my c432b198 or ...? as i need to flash boot, recovery, cust & system , how can I do so while there is no CUST img in extracted data (seems to be inside the data img itself).
Or else how can do A COMPLETE FORMAT of my internal storage ? the command , any1 i do, give either "not allowed" or partition lengh etc"
any way I can use fastboot to get out of this bootloop iom3 error 14 which don't let my battery charge a little ?
I'm a little much confused and do apology for that. Any help is desesperated needed .
So what is the boot image or the boot partition now called in OREO? I am trying to unbrick my Honor 9 and had Oreo L09-B321 on it before. The only thing I am missing is to successfully flash boot since I am also getting the "partition length error" when I use fastboot boot BOOT.img.
overflyer said:
So what is the boot image or the boot partition now called in OREO? I am trying to unbrick my Honor 9 and had Oreo L09-B321 on it before. The only thing I am missing is to successfully flash boot since I am also getting the "partition length error" when I use fastboot boot BOOT.img.
Click to expand...
Click to collapse
I think ramdisk is the boot partition in oreo, so you have to use fastboot flash ramdisk RAMDISK.img.
YASS
tobyffm said:
Hi, I also have Mate 9 L09 and have exact same error message:
fastboot flash recovery twrpo.img
target reported max download size of 471859200 bytes
sending 'recovery' (26982 KB)...
OKAY [ 0.579s]
writing 'recovery'...
FAILED (remote: partition length get error)
UPDATE:
OK, I managed it by myself, haha.
For anyone else with same issue.
Since Oreo: Partition names have changed.
Use this command: fastboot flash recovery_ramdisk RECOVERY.img
"recovery" changed to "recovery_ramdisk" now.
finished. total time: 0.600s
I downloaded that special TWRP recovery image, but still get the same message. Does not work for me, any new solution available?
Click to expand...
Click to collapse
Worked like a charm. Thanks.
****ty ADB
i have adb drivers installed but if i enter: fastboot flash recovery_ramdisk RECOVERY.img it says cannot load RECOVERY.img
still stuck
tothl74 said:
I think ramdisk is the boot partition in oreo, so you have to use fastboot flash ramdisk RAMDISK.img.
Click to expand...
Click to collapse
i still get folowing error
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (34634 KB)...
OKAY [ 1.214s]
writing 'recovery_ramdisk'...
FAILED (remote: partition error)
finished. total time: 1.235s
i have tried all three commands
fastboot flash recovery twrp_Honor_7x.img
fastboot flash recovery_ramdisk twrp_Honor_7x.img
fastboot flash ramdisk twrp_Honor_7x.img
i cant flash!! same error!!!
failed remote partition lenght get error
Hey guys i got a new problem with my phone. I did a factory reset and later i unlocked the bootlader again but when i tried to do something with adb said ''Command not allowed'' later when i tried to install twrp said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 471859200 bytes
sending 'recovery' (8728 KB)...
OKAY [ 0.252s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.266s
Are you on Oreo?
Edit: seeing your thread below this one you are.
Oreo uses RECOVERY_RAMDISK instead of RECOVERY.
So you'd flash with fastboot flash recovery_ramdisk recovery.img
Make sure you're flashing a recovery for Oreo
ante0 said:
Are you on Oreo?
Edit: seeing your thread below this one you are.
Oreo uses RECOVERY_RAMDISK instead of RECOVERY.
So you'd flash with fastboot flash recovery_ramdisk recovery.img
Make sure you're flashing a recovery for Oreo
Click to expand...
Click to collapse
I'm loving you so much right now
ante0 said:
Are you on Oreo?
Edit: seeing your thread below this one you are.
Oreo uses RECOVERY_RAMDISK instead of RECOVERY.
So you'd flash with fastboot flash recovery_ramdisk recovery.img
Make sure you're flashing a recovery for Oreo
Click to expand...
Click to collapse
I flashed with it but when i opened the recovery mode he opened erecovery from huawei and i flashed twrp for oreo
CommunalH said:
I flashed with it but when i opened the recovery mode he opened erecovery from huawei and i flashed twrp for oreo
Click to expand...
Click to collapse
Could you send me the recovery you're flashing?
ante0 said:
Could you send me the recovery you're flashing?
Click to expand...
Click to collapse
When i tried to flash to oreo i downloaded a file named Hwota8, in there were the twrp named TWRP8_3.0.3
CommunalH said:
When i tried to flash to oreo i downloaded a file named Hwota8, in there were the twrp named TWRP8_3.0.3
Click to expand...
Click to collapse
Good, that's the correct one
Can you boot to system?
ante0 said:
Good, that's the correct one
Can you boot to system?
Click to expand...
Click to collapse
I don't hace OS right now, options neither
CommunalH said:
I don't hace OS right now, options neither
Click to expand...
Click to collapse
What is your model of mate 9? (LxxCxxxBxxx)
I thought you should try to flash ramdisk and kernel as well, in case KERNEL partition is broken too it would probably go to erecovery (erecovery uses its own kernel.)
If you are on AL00 or C636 you can use dload right away. If not we'll have to find another way.
ante0 said:
What is your model of mate 9? (LxxCxxxBxxx)
I thought you should try to flash ramdisk and kernel as well, in case KERNEL partition is broken too it would probably go to erecovery (erecovery uses its own kernel.)
If you are on AL00 or C636 you can use dload right away. If not we'll have to find another way.
Click to expand...
Click to collapse
I don't know here to find my build number without OS, i know it's MHA-L09B
I just flashed the OOS Android 10 beta ROM via the system upgrade tool (didn't work via TWRP) so now I'm unrooted. ROM works fine, but I'm having trouble re-rooting. I'm trying to boot the TWRP img via fastboot and keep getting the same error:
Code:
c:\adb>fastboot boot twrp.img
Sending 'boot.img' (28980 KB) OKAY [ 0.640s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
I'm unable to boot into TWRP and tried different versions of the img file, all which give me the same error. How can I fix this?
vorsprungtechnik said:
I just flashed the OOS Android 10 beta ROM via the system upgrade tool (didn't work via TWRP) so now I'm unrooted. ROM works fine, but I'm having trouble re-rooting. I'm trying to boot the TWRP img via fastboot and keep getting the same error:
Code:
c:\adb>fastboot boot twrp.img
Sending 'boot.img' (28980 KB) OKAY [ 0.640s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
I'm unable to boot into TWRP and tried different versions of the img file, all which give me the same error. How can I fix this?
Click to expand...
Click to collapse
Doesn't work yet, don't think it will for a while because fastboot has changed apparently.
The guy who makes the OP7 port has it baked in, but it's not encrypted
brashmadcap said:
Doesn't work yet, don't think it will for a while because fastboot has changed apparently.
The guy who makes the OP7 port has it baked in, but it's not encrypted
Click to expand...
Click to collapse
Ok thanks. So there's no way to possibly root the new ROM at the moment?
Flash patched boot.img via fastboot. Just becarful with magisk modules at the moment.
Bradl79 said:
Flash patched boot.img via fastboot. Just becarful with magisk modules at the moment.
Click to expand...
Click to collapse
Can you elaborate on this? The part about being careful with modules? I got magisk working, and I'm using 2 modules, YT Vanced and Google Dialer framework.
When should I be careful? When there is a new update for the A10 beta? Or just on how many modules you install, or which ones?
Thanks
Meaning if u go into a bootloop u r pretty much screwed without a twrp, there is no way to remove the module.
Deleted, wrong post
ArkAngel06 said:
Can you elaborate on this? The part about being careful with modules? I got magisk working, and I'm using 2 modules, YT Vanced and Google Dialer framework.
When should I be careful? When there is a new update for the A10 beta? Or just on how many modules you install, or which ones?
Thanks
Click to expand...
Click to collapse
Just be smart. Use stuff that doesn't fundementally alter things (framework mods, etc.). FDE is updated, Vanced works, stuff like call recorder, fonts etc. should be fine. I'd avoid audio mods (directories might have changed idk) and things like auto brightness fix (framework mods).
---------- Post added at 02:22 AM ---------- Previous post was at 02:20 AM ----------
vorsprungtechnik said:
Ok thanks. So there's no way to possibly root the new ROM at the moment?
Click to expand...
Click to collapse
Updating from rooted OOS Pie, flash magisk through manager to inactive slot before reboot after OTA finished. Worked for me.
Of course I don't have any recovery at all so we will see how that goes three days from now when I install something crazy
vorsprungtechnik said:
I just flashed the OOS Android 10 beta ROM via the system upgrade tool (didn't work via TWRP) so now I'm unrooted. ROM works fine, but I'm having trouble re-rooting. I'm trying to boot the TWRP img via fastboot and keep getting the same error:
Code:
c:\adb>fastboot boot twrp.img
Sending 'boot.img' (28980 KB) OKAY [ 0.640s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
I'm unable to boot into TWRP and tried different versions of the img file, all which give me the same error. How can I fix this?
Click to expand...
Click to collapse
I fixed this on the op6 by doing this:
Note: On Windows systems, thanks to a bug in fastboot, you must first swap to slot a with fastboot set_active a, then specify slot a when flashing images, e.g. fastboot flash boot_a <recovery_filename>.img
(from lineageos install site)
however after this was a success i'm now stuck on the 1+ fastboot splash screen and it never actually goes to recovery. Hopefully you've figured it out by now but I came across your post a few times while I was looking for the solution myself
So, i bumped into this the other day, what i did was, flash the full Android 10 fastboot rom using the op6 aio tool, then, using fastboot I flashed twrp the one from mauronofrio, then from twrp without wiping anything, I flashed the stock boot.img, then the twrp installer again from mauronofrio and voila, twrp working, I also flashed magisk after the first boot, this is all in the fool proof guide in the guides subforum
any update on this? just updated to OOS 10.3.2 and cant boot into twrp anymore. All I want is to have twrp...any way to roll back to android 9?