Related
I unlocked the bootloader but now when i try to flash the twrp by fastboot command i get error as target reported max download size of 268435456 bytes. error : cannot load twrp.
I renamed the file also cleared cache but same error. I m trying from yesterday but same error . pls help me.
Hello,
I have a Moto G (XT1032) since 3 years and all of a sudden, it didn't boot. I had the Stock ROM, I never installed a new ROM or Recovery...
I unlocked my phone and then tried to install TWRP to boot on recovery and make a backup of my data.
I tried several recoveries (twrp-2.8.6.0-xt1032, twrp-3.0.0.0_2-falcon, twrp-3.1.0-0-falcon, twrp-3.1.0-0-xt1032 & clockwork-touch-6.0.4.7-falcon).
I have no problem to send the recovery on the phone. In the fastboot mode on the phone, it says the installation is okay and then, I choose "Recovery" in the fastboot mode on the phone.
The phone reboot and I have the android logo with "No Command". I find this blog : https://wasconet.com/solution-moto-g-android-recovery-mode-no-command/ and so I hold the power button and press the volume up button to enter recovery mode screen.
The problem is, I access the default recovery — which is not TWRP, only a basic recovery where I can't mount the phone. This recovery says :
Android system recovery
LPBS23.13-56-2
...
From there I can reboot, apply update from sdcard or ADB, wipe data/factory, wipe cache, reboot to bootloader, power down or view recovery logs.
What can I do to install a good recovery and to mount my phone to make a backup ?
Thanks guys !
Lately it happens with the latest versions of twrp. Do not boot or boot once, then return the Stock Recovery again.
In my case I can not install v3.1 because it throws me max download size error. :silly:
Try the v3.0.2-2. It works without any problem over my old falcon.
https://dl.twrp.me/falcon/twrp-3.0.2-2-falcon.img.html
I'm not sure if the command works on the Falcon, but first try starting it without flashing it
fastboot boot twrp-3.0.2-2-falcon.img
By the way, can i assume that having Lollipop you have the latest version of the bootloader (41.1A)?
Thanks, it worked ! I made a backup of my files.
Now I try since this morning to install a new ROM... I tried "Factory" in the fastboot mode => Phone blocks on "Bootloader unlock".
With TWRP, I havea lot of problem with the mount. I can see the data but to copy files, it was not possible.
I mount the sdcard in Read Write with the terminal on the phone to copy the Lineage ROM. I tried to install it but I receive an error "1001".
I use now the last version of TWRP, the 3.1.0 with the command fastboot boot. This version works but I have the same error to install Lineage.
I also tried to install the stock version EU 5.1 Stock ROM (Untouched) (522mb) (from here https://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510) with adb sideload.
I saw "succesful" but the phone is always block on the "Bootloader unlock" image...
The bootloader version is indeed 41.1A.
Someone should have an idea to install a system ? (any system, I don't care, I just want a phone that I can use )
Thanks a lot !
Usually error 1001 relates to an encrypted or unreadable partition.
Have you used fastboot or mfastboot to install the system again?
Try Repair or Change file system using twrp.
Wipe>>Advanced Wipe>>
Then try to install any ROM.
If doesn't work. Inside of TWRP go to Advanced>Terminal Emulator
Then execute the command df
That should list you the partitions. Share it and if you know how to take it please share the recovery log after doing all this.
I use fastboot to just boot on the recovery.
To install, I don't tried fastboot or mfastboot. I find a guide to flash with mfastboot, I will try.
Yesterday I made all the wipe possible. Today I made a Repair on the system partition.
Here is the result of the df command :
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 446184 20 446164 0% /dev
tmpfs 446184 20 446164 0% /tmp
/dev/block/mmcblk0p33
667328 11836 655492 2% /cache
/dev/block/mmcblk0p36
5789552 5210064 528432 91% /data
/dev/block/mmcblk0p36
5789552 5210064 528432 91% /sdcard
I noticed something strange yesterday. I tried several times to delete files on the "sdcard" partition, where I found the pictures, whatsapp, ... I deleted some files with Windows (MTP Mode) and the files are always there after delete with no error message. I don't know if it's important or not.
lolo1410 said:
I I noticed something strange yesterday. I tried several times to delete files on the "sdcard" partition, where I found the pictures, whatsapp, ... I deleted some files with Windows (MTP Mode) and the files are always there after delete with no error message. I don't know if it's important or not.
Click to expand...
Click to collapse
When you unlock the bootloader, all your personal data should be deleted normally, but that didn't happen. The internal memory partition is recognized (that's good) but is unreadable, obviously corrupted. (Sorry for not noticing before)
Try installing the firmware again using mfastboot avoiding BOOTLOADER (motoboot) AND GPT files to see if works. If didn't, flash it again including GPT file (Partitions table).
If it still doesn't work, you'll have to figure out how to repartition the entire phone memory.
----------
By the way, never try to restore that DATA BACKUP. Like i say before, it's corrupted. Search a way to decompress and takes only the important files.
Thanks a lot for your time !
Indeed, it's seems there is a probleme with the filesystem.
I tried a flash of GPT & Bootloader but it didn't work.
Here is the log :
C:\adb\tmp>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.026s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.320s
&
C:\adb\tmp>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.093s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.370s
But I'm not sure if I choose the good firmware & bootloader.
On this link (http://www.filefactory.com/folder/c6cdedc45a775d27), which version can I take ?
Here is the information that I have for the phone :
Motorola G XT1032 - Type M0DEB - FCCID ihdt56pf1 buyed in Belgium
AP Fastboot Flash Mode (S)
41.1A (2015-04-10)
CPU MSM8226 CS
eMMC : 8GB Sandisk
DRAM : 1024MB Samsung S4
Try with one of these, and again. DONT FLASH BOOTLOADER (Usually cant be flashed after unlock but, I do not think you want a paperweight)
Retail EU 5.1
https://www.androidfilehost.com/?fid=24052804347848287
Retail EU 5.1 (NEWER BUILD)
https://www.androidfilehost.com/?fid=24499762636006646
You can download others from Here
https://forum.xda-developers.com/mo...rmware-t3110795?_e_pi_=7,PAGE_ID10,4937194410
After several tests, I find a good package, this : XT1032_FALCON_RETFR_5.1_LPBS23.13-56-2_cid7_CFC.xml
I had no error.
I see your message too late, I flash the bootloader
But it's a 41.1A version, here is the info on this package :
BUILD REQUEST INFO:
SW Version: falcon_retfr-user 5.1 LPBS23.13-56-2 2 release-keysMSM8626BP_1032.3116.98.00R
MBM Version: 41.1A
Modem Version: MSM8626BP_1032.3116.98.00R
FSG Version: MSM8626BP_FSG_01.101.00R
Build Fingerprint: motorola/falcon_retfr/falcon_umts:5.1/LPBS23.13-56-2/2:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 221.201.2.falcon_umts.Retail.en.FR
Model number: Moto G
Android Version: 5.1
Baseband Version: MSM8626BP_1032.3116.98.00R
Build Number: LPBS23.13-56-2
Build Date: Fri Feb 26 06:59:41 CST 2016
OTHER MISC VERSION INFO:
Subsidy Lock Config: None
Blur Version: Blur_Version.221.201.2.falcon_umts.Retail.en.FR
Version when read from CPV: falcon_retfr-user 5.1 LPBS23.13-56-2 2 release-keys
I followed the guide here https://forum.xda-developers.com/showthread.php?t=2542219 and no error during all the command. I switch off the phone and unfortunately, no boot...
It's block on the "Warning bootloader unlocked" screen...
The phone is still alive and that's good. Keep trying others roms if you want. But as I said before, surely the internal memory of the phone is corrupt. Unfortunately, I can't help you with that.
Maybe here over XDA there's a tutorial about how to solve your problem.
Okay, thanks a lot for your help.
I just tried the Retail EU 5.1 (NEWER BUILD) and same result : no error but blocks on the boot..
I will continue to test other ROM
I ended up in the same situation when trying to flash GPe on MotoG XT1032; the device was only able to boot into fastboot
After booting into TWRP, I formatted the /data partition again (in order to fallback to F2FS instead of ext4) and I used adb sideload to transfer "XT1032_Retail_Brazil_51_Untouched.zip" (you can find it on xda, under "Stock Motorola Lollipop ROM Collection" thread).
Phone was in full working condition once more
so im trying to send a modem.img to a lg v10 through fastboot, its bootloader unlocked and rooted.i result with this:
C:\Users\jas\Downloads\WindowsLGFirmwareExtract-1.2.5.0-Release>fastboot flash modem modem.img
target reported max download size of 536870912 bytes
sending 'modem' (76800 KB)...
OKAY [ 1.715s]
writing 'modem'...
FAILED (remote: unknown command)
finished. total time: 1.731s
Also twrp cant mount modem or even back it up.I think the partition is read only,is there a way to make it r/w?I also tried clearing cache through fastboot and get the same failed message.
C:\Users\jas\Downloads\WindowsLGFirmwareExtract-1.2.5.0-Release>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: unknown command)
finished. total time: 0.016s
C:\Users\jas\Downloads\WindowsLGFirmwareExtract-1.2.5.0-Release>fastboot format cache
Creating filesystem with parameters:
Size: 1291845632
Block size: 4096
Blocks per group: 32768
Inodes per group: 7888
Inode size: 256
Journal blocks: 4928
Label:
Blocks: 315392
Block groups: 10
Reserved block group size: 79
Created filesystem with 11/78880 inodes and 10367/315392 blocks
target reported max download size of 536870912 bytes
erasing 'cache'...
FAILED (remote: unknown command)
finished. total time: 0.000s
also failing to mount partitions through fastboot while in bootloader
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/ $ mount -o remount,rw /system
mount: Permission denied
any help would be appreciated!
jass65 said:
so im trying to send a modem.img to a lg v10 through fastboot, its bootloader unlocked and rooted.i result with this:
C:\Users\jas\Downloads\WindowsLGFirmwareExtract-1.2.5.0-Release>fastboot flash modem modem.img
target reported max download size of 536870912 bytes
sending 'modem' (76800 KB)...
OKAY [ 1.715s]
writing 'modem'...
FAILED (remote: unknown command)
finished. total time: 1.731s
Also twrp cant mount modem or even back it up.I think the partition is read only,is there a way to make it r/w?I also tried clearing cache through fastboot and get the same failed message.
C:\Users\jas\Downloads\WindowsLGFirmwareExtract-1.2.5.0-Release>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: unknown command)
finished. total time: 0.016s
C:\Users\jas\Downloads\WindowsLGFirmwareExtract-1.2.5.0-Release>fastboot format cache
Creating filesystem with parameters:
Size: 1291845632
Block size: 4096
Blocks per group: 32768
Inodes per group: 7888
Inode size: 256
Journal blocks: 4928
Label:
Blocks: 315392
Block groups: 10
Reserved block group size: 79
Created filesystem with 11/78880 inodes and 10367/315392 blocks
target reported max download size of 536870912 bytes
erasing 'cache'...
FAILED (remote: unknown command)
finished. total time: 0.000s
also failing to mount partitions through fastboot while in bootloader
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/ $ mount -o remount,rw /system
mount: Permission denied
any help would be appreciated!
Click to expand...
Click to collapse
Maybe you can try using adb shell and dd the .img to its correct partition with the proper dd command for your device. You need to find out which mmcblk0 is your modem partition, then use that mmcblk0 as the .img destination in your dd command.
The same command works in Terminal Emulator app also, you just have to enter "su" command first, then the dd command.
TWRP has the ability to flash .img files also, not sure if it works for flashing modem.img though, I've never looked into it.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Maybe you can try using adb shell and dd the .img to its correct partition with the proper dd command for your device. You need to find out which mmcblk0 is your modem partition, then use that mmcblk0 as the .img destination in your dd command.
The same command works in Terminal Emulator app also, you just have to enter "su" command first, then the dd command.
TWRP has the ability to flash .img files also, not sure if it works for flashing modem.img though, I've never looked into it.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. Yes youre right i could try that and will work .its just i need to do it in bootloader mode/ without root su just in case something goes wrong and i dont have access to root to reflash.
ok even using flashwire, it will not flash.In flashfire is says the partition is protected it says it flashed the modem but it doesnt actually. Is there any way to remove this write protection on the modem partition or bypass it to flash?
jass65 said:
ok even using flashwire, it will not flash.In flashfire is says the partition is protected it says it flashed the modem but it doesnt actually. Is there any way to remove this write protection on the modem partition or bypass it to flash?
Click to expand...
Click to collapse
If your bootloader was unlocked correctly then you should be able to fastboot flash it. Are you sure you haven't missed something somewhere along the way?
Sent from my SM-S903VL using Tapatalk
Nope im stumped on this as well.my bootlpader is unlocked even running the fastboot oem unlock command confirms it.frkn LG. I can flash modem in twrp on note 4 with a breeze.
jass65 said:
Nope im stumped on this as well.my bootlpader is unlocked even running the fastboot oem unlock command confirms it.frkn LG. I can flash modem in twrp on note 4 with a breeze.
Click to expand...
Click to collapse
Maybe you need to use LG flashtool and convert the modem file you have to be compatible with flashtool.
Sent from my SM-S903VL using Tapatalk
---------- Post added at 09:47 AM ---------- Previous post was at 09:33 AM ----------
jass65 said:
Nope im stumped on this as well.my bootlpader is unlocked even running the fastboot oem unlock command confirms it.frkn LG. I can flash modem in twrp on note 4 with a breeze.
Click to expand...
Click to collapse
Ah, I think I just realized your problem maybe, don't know why I didn't see it before.
When in fastboot, did you try
fastboot flash radio modem.img
Instead of fastboot flash modem modem.img?
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Maybe you need to use LG flashtool and convert the modem file you have to be compatible with flashtool.
Sent from my SM-S903VL using Tapatalk
---------- Post added at 09:47 AM ---------- Previous post was at 09:33 AM ----------
Ah, I think I just realized your problem maybe, don't know why I didn't see it before.
When in fastboot, did you try
fastboot flash radio modem.img
Instead of fastboot flash modem modem.img?
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
so i tried fastboot flash radio modem.img and still get the same unknown command.is there any other commands to do this?.i think only fastboot can flash it since partition is locked.i mean flashing a whole new rom with lgup always works in download mode but im trying to flash a modified modem. this is the modem partition path /dev/block/mmcblk0p1. dd doesnt work in fastboot correct because i would need su permission.
jass65 said:
so i tried fastboot flash radio modem.img and still get the same unknown command.is there any other commands to do this?.i think only fastboot can flash it since partition is locked.i mean flashing a whole new rom with lgup always works in download mode but im trying to flash a modified modem. this is the modem partition path /dev/block/mmcblk0p1. dd doesnt work in fastboot correct because i would need su permission.
Click to expand...
Click to collapse
I'll try to look for other ways but I can't promise any results.
dd is done via adb shell or terminal emulator, not fastboot.
You're trying to flash a customized kernel? You may as well give up on that without root or at least TWRP.
If you have twrp you can try converting your modem to a flashable zip and flash it as you would a ROM but I doubt it will work with stock bootloader.
Have you tried mounting your partitions while in TWRP?
I don't understand why you're trying to do this without su permission when you are already rooted. The purpose of rooting is to use that root to configure the device as you choose. Why are trying to do it without root?
Sent from my SM-S903VL using Tapatalk
Ok so im rooted , bootloader unlocked and have twrp.twrp will not even see the modem partition.there is also no modem mount partition avaliable in twrp.i try flashing modem.img through twrp and can only select boot or recovery as the partition to flash to.do i need to create a flashable zip with a updater scrpit so twrp can see the modem partition ? also i can't flash modem while im in andoid system enviorment, correct? Yes i can dd it since i have root but the phone would have to be on and in android envoirment.So the only option left is fastboot which keeps throwing that error at me.ive also tried flashfire and that doesnt work either.i really appreciate you talking the time to help!
I was just trying to do it without root so i have a fall back plan.say i flash the moden and cant boot into os.at least i know i can fix the problem with fastboot and it will work.
jass65 said:
Ok so im rooted , bootloader unlocked and have twrp.twrp will not even see the modem partition.there is also no modem mount partition avaliable in twrp.i try flashing modem.img through twrp and can only select boot or recovery as the partition to flash to.do i need to create a flashable zip with a updater scrpit so twrp can see the modem partition ? also i can't flash modem while im in andoid system enviorment, correct? Yes i can dd it since i have root but the phone would have to be on and in android envoirment.So the only option left is fastboot which keeps throwing that error at me.ive also tried flashfire and that doesnt work either.i really appreciate you talking the time to help!
I was just trying to do it without root so i have a fall back plan.say i flash the moden and cant boot into os.at least i know i can fix the problem with fastboot and it will work.
Click to expand...
Click to collapse
Who do you have service with? Some mobie carriers remove fastboot feature from their devices, or at least remove functionality for certain commands. Some carriers go out of their way to keep us from messing with their devices.
If you made this modified modem yourself then I doubt you got all the modifications correct on the first try, flashing it will probably softbrick or maybe even hard brick the device. If it hard bricks you're done. Flashing modems other than the one that belongs on a device is risky business.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Who is do you have service with? Some mobie carriers remove fastboot feature from their devices, or at least remove functionality for certain commands. Some carriers go out of their way to keep us from messing with their devices.
If you made this modified modem yourself then I doubt you got all the modifications correct on the first try, flashing it will probably softbrick or maybe even hard brick the device. If it hard bricks you're done. Flashing modems other than the one that belongs on a device is risky business.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
If fastboot is removed from some devices and i can confirm it is missing on mine too.. How can i add it if it's even possible? would building from aosp source actually work or would i be left in the same boat with no fastboot still?
Sent from my LGLS676 using Tapatalk
Sands207 said:
If fastboot is removed from some devices and i can confirm it is missing on mine too.. How can i add it if it's even possible? would building from aosp source actually work or would i be left in the same boat with no fastboot still?
Sent from my LGLS676 using Tapatalk
Click to expand...
Click to collapse
If fastboot has been removed then you can give up on trying to "add it".
Sent from my SM-S903VL using Tapatalk
hmm i have a tmobile v10 and its the only variant that comes with oem unlock option and was easiest to root.Actually what im trying to do is not flash a modem modified by me. See, i have a network locked v10 and the only way to unlock it is through the tmo device unlock app, no dialer codes , nothing.T mo won't put my request through for a permanent network unlock, even the previous owner has tried calling them.unlock services were less than 30$ near the v10's release now unlock services are 70$-100USD and they dont guarantee anything . thats crazy to unlock a phone.So i've tried putting international rom's on this thing and i cant get a sim unlock promp to show up.I do have the unlock code for it but can't enter it anywhere.Since the system img doesn't hold the unlock info.i figured the modem partition does and searching around confirmed this.So i had a person very very kind enough to upload his *unlocked* t mobile v10 modem so i could try flashing it.Now i have the unlocked modem*not user modified*. that i can't flash lol.
The thing with fastboot is, it won't even let me clear cache partition which is not even locked!?
jass65 said:
hmm i have a tmobile v10 and its the only variant that comes with oem unlock option and was easiest to root.Actually what im trying to do is not flash a modem modified by me. See, i have a network locked v10 and the only way to unlock it is through the tmo device unlock app, no dialer codes , nothing.T mo won't put my request through for a permanent network unlock, even the previous owner has tried calling them.unlock services were less than 30$ near the v10's release now unlock services are 70$-100USD and they dont guarantee anything . thats crazy to unlock a phone.So i've tried putting international rom's on this thing and i cant get a sim unlock promp to show up.I do have the unlock code for it but can't enter it anywhere.Since the system img doesn't hold the unlock info.i figured the modem partition does and searching around confirmed this.So i had a person very very kind enough to upload his *unlocked* t mobile v10 modem so i could try flashing it.Now i have the unlocked modem*not user modified*. that i can't flash lol.
The thing with fastboot is, it won't even let me clear cache partition which is not even locked!?
Click to expand...
Click to collapse
You'll have to follow the prescribed method of unlocking allowed by your network.
Now that I know you're attempting to do something that your network said they wouldn't allow, that means I have to tell you that there is nothing else I or anyone at XDA will do to help. We customize our devices but we don't discuss things that are against carrier policy.
Their modem probably won't work anyway because the way unlock works, the unlock code for each device is different, their unlock code won't unlock you.
If it were that easy then no one would need to pay for an unlock code, everyone with that device could just share the unlock code, it doesn't work like that. Your unlock code will be specific to your device based on its identifying numbers such as serial number and IMEI number, your numbers and the numbers from the other guys device are not the same.
Sent from my SM-S903VL using Tapatalk
I understand where you're coming from but please don't say this is against carrier policy.the device is paid off in full.carriers are just a bunch of d**ks.i can't count how many sim unlock/carrier bypasses threads are on this site, so no this site isn't just about customization.this site ****s all over carrier policies from the moment you unlock your bootloader to the moment you exchange your bricked phone by lying and telling them it was a software update when in reality u were messing with system files.ive literally bypassed 3 different phones networks using solely xda.tell me that's not violating carrier policy. These threads are still live years later.
The tmobile unlock app is broken not just for me but for many other people.they cant even connect to the remote server just like me.when you tell t mobile, they just say oh well cause they already milked you for the phone.its circumstances like this where you gotta work around the normal field.
Yes you're most likely right about the unlock but I thought I'd just give it a shot.
jass65 said:
I understand where you're coming from but please don't say this is against carrier policy.the device is paid off in full.carriers are just a bunch of d**ks.i can't count how many sim unlock/carrier bypasses threads are on this site, so no this site isn't just about customization.this site ****s all over carrier policies from the moment you unlock your bootloader to the moment you exchange your bricked phone by lying and telling them it was a software update when in reality u were messing with system files.ive literally bypassed 3 different phones networks using solely xda.tell me that's not violating carrier policy. These threads are still live years later.
The tmobile unlock app is broken not just for me but for many other people.they cant even connect to the remote server just like me.when you tell t mobile, they just say oh well cause they already milked you for the phone.its circumstances like this where you gotta work around the normal field.
Yes you're most likely right about the unlock but I thought I'd just give it a shot.
Click to expand...
Click to collapse
As a former Moderator here, I can certainly tell you that unlocking isn't even supposed to be discussed at all at XDA but you will find it. That doesn't mean XDA approves.
If you'll read the rules you'll see all kinds of things that aren't supposed be done or discussed here. XDA is all about sharing knowledge but it is certainly not about breaking the rules, some lines get pushed but they are not supposed to be broken.
Your impression of XDA ****ing all over carriers is not how it is at all, it's the members here saying f*** the rules, not XDA.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
As a former Moderator here, I can certainly tell you that unlocking isn't even supposed to be discussed at all at XDA but you will find it. That doesn't mean XDA approves.
If you'll read the rules you'll see all kinds of things that aren't supposed be done or discussed here. XDA is all about sharing knowledge but it is certainly not about breaking the rules, some lines get pushed but they are not supposed to be broken.
Your impression of XDA ****ing all over carriers is not how it is at all, it's the members here saying f*** the rules, not XDA.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
still, thanks for the help.
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
A hawe a Huawei Mate 10 wich after hard brick (COM1) 6 mounth ago wake up himself!!!
Fastboot is works
Bootloader locked
eRecovery works
Stock recovery works
But DC Phoenix not flash any update.app or board.dgtks file (DC gives evrytime ERROR... device not supported, flashing incomplet). Flashing stops befor DC phoenix can open backdoor.
In fastboot works only one command, that is FASTBOOT DEVICES, and result is 123456789ABCDEF
I can*t flash nothing in fastboot vommand line: gives me error for example:
FASTBOOT FLASH OEMINFO OEMINFO.IMG
sending `oeminfo` 378kb...
OKAY
Writing `oeminfo`...
FAILED remote: Command not allowed
Any fastboot command ends with that error
eRecovery get errors after try flash WIFI DNS firmware finder.
Device lost all: oeminfo, vendor, IMEI, model
And only founded information by DC/HCU/fastboot is device name 0123456789ABCDEF
What i can to do to fix that?
Thanks