How can oem unlock leEco le pro 3 x722 - LeEco Le Pro3 Questions & Answers

Hi guys
I destroyed my leEco le pro 3 x722
After passing the custom rom
Now the device is locked on fastboot only
There is no system and no recovery
The problem I have now is the decryption. If the oem unlock is I can update it. Please help oem unlock
The device does not respond to commands
Everything is written
PS C: \ adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (39337 KB) ...
OKAY [0.895s]
writing 'recovery' ...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.940s
How can oem unlock in another way ????

What did you try to flash, and on which firmware?
If you tried flashing stock 26s, that locks the bootloader permanently. There really ought to be a sticky about this here. The mods here aren't active at all, which is a shame. And you cannot flash any random ROM you come across, like MIUI. Someone on this forum tried to flash a MIUI ROM and bricked their phone. There is no one-size-fits-all universal ROM that you can flash on every phone... every ROM requires a set of drivers unique to your device, so you need a dev to port specific ROMs to your device. Just clearing that up for anyone who's confused about ROM availability.
What you're supposed to do in order to flash anything at all is to first flash Batyan's 20s developer ROM via stock recovery, unlock the bootloader via Dev options and fastboot, and then flash TWRP and then your ROM. Apparently the vendor ROMs on 20s (from Banggood, Geekbuying, Gearbest, etc.) cannot be unlocked, even though the OEM unlocking option is present in eUI's Developer options.
As for resolving your brick, post to this thread: https://forum.xda-developers.com/le...velopment--and-mods/try-unbrick-x722-t3686191
Hopefully your brick is a soft one that can be resolved without a QFIL file. Because there's no QFIL available for the x722, and it seems to be very difficult to obtain anyway.

sk8223 said:
What did you try to flash, and on which firmware?
If you tried flashing stock 26s, that locks the bootloader permanently. There really ought to be a sticky about this here. The mods here aren't active at all, which is a shame. And you cannot flash any random ROM you come across, like MIUI. Someone on this forum tried to flash a MIUI ROM and bricked their phone. There is no one-size-fits-all universal ROM that you can flash on every phone... every ROM requires a set of drivers unique to your device, so you need a dev to port specific ROMs to your device. Just clearing that up for anyone who's confused about ROM availability.
What you're supposed to do in order to flash anything at all is to first flash Batyan's 20s developer ROM via stock recovery, unlock the bootloader via Dev options and fastboot, and then flash TWRP and then your ROM. Apparently the vendor ROMs on 20s (from Banggood, Geekbuying, Gearbest, etc.) cannot be unlocked, even though the OEM unlocking option is present in eUI's Developer options.
As for resolving your brick, post to this thread: https://forum.xda-developers.com/le...velopment--and-mods/try-unbrick-x722-t3686191
Hopefully your brick is a soft one that can be resolved without a QFIL file. Because there's no QFIL available for the x722, and it seems to be very difficult to obtain anyway.
Click to expand...
Click to collapse
You installed Batyan's 20s developer ROM
In the past I opened the boot loader but when I tried Rum Miwi did not work
I wanted to go back to the official 26s Rom
Unfortunately everything has lost and the device is ruined
I did not see the warning of testing
How is the solution now

The official 26s ROM locks the bootloader down. If you try to flash anything through it, you'll end up with a bricked device. I'm sorry.
Did you say that you tried to install MIUI? I don't know what "Miwi" is. All I know is, that's something you shouldn't have done.
I'm not sure if you successfully flashed the official 26s ROM or not, and then tried to flash something else... that would cause a brick for sure, AFAIK.
Again, post to the thread about bricked phones that I linked. There are quite a few people with bricks here. Hopefully a solution will present itself soon. Until then, hold onto your phone and hope. :/

sk8223 said:
The official 26s ROM locks the bootloader down. If you try to flash anything through it, you'll end up with a bricked device. I'm sorry.
Did you say that you tried to install MIUI? I don't know what "Miwi" is. All I know is, that's something you shouldn't have done.
I'm not sure if you successfully flashed the official 26s ROM or not, and then tried to flash something else... that would cause a brick for sure, AFAIK.
Again, post to the thread about bricked phones that I linked. There are quite a few people with bricks here. Hopefully a solution will present itself soon. Until then, hold onto your phone and hope. :/
Click to expand...
Click to collapse
Yes, unfortunately, the device is locked
Updated 26s
The manufacturer must find us a solution
Thank you for the kind word

sk8223 said:
What did you try to flash, and on which firmware?
If you tried flashing stock 26s, that locks the bootloader permanently. There really ought to be a sticky about this here. The mods here aren't active at all, which is a shame. And you cannot flash any random ROM you come across, like MIUI. Someone on this forum tried to flash a MIUI ROM and bricked their phone. There is no one-size-fits-all universal ROM that you can flash on every phone... every ROM requires a set of drivers unique to your device, so you need a dev to port specific ROMs to your device. Just clearing that up for anyone who's confused about ROM availability.
What you're supposed to do in order to flash anything at all is to first flash Batyan's 20s developer ROM via stock recovery, unlock the bootloader via Dev options and fastboot, and then flash TWRP and then your ROM. Apparently the vendor ROMs on 20s (from Banggood, Geekbuying, Gearbest, etc.) cannot be unlocked, even though the OEM unlocking option is present in eUI's Developer options.
As for resolving your brick, post to this thread: https://forum.xda-developers.com/le...velopment--and-mods/try-unbrick-x722-t3686191
Hopefully your brick is a soft one that can be resolved without a QFIL file. Because there's no QFIL available for the x722, and it seems to be very difficult to obtain anyway.
Click to expand...
Click to collapse
So your fastboot works just flash the boot loader .
Nice. I finally able to unlock and root. Although I just wished, the first page gets updated with the current method. I have to go through all the pages to fully understand what to do.
So basically a quick roundup:
go in fastboot
flash emmc_appsboot.mbn inside the zip.
reboot
it will ask for a password, just ignore it and reboot back to fastboot
unlock the bootloader
flash twrp
boot into twrp
format phone
then you're done!
Sent from my LEX727 using xda premium

mchlbenner said:
So your fastboot works just flash the boot loader .
Nice. I finally able to unlock and root. Although I just wished, the first page gets updated with the current method. I have to go through all the pages to fully understand what to do.
So basically a quick roundup:
go in fastboot
flash emmc_appsboot.mbn inside the zip.
reboot
it will ask for a password, just ignore it and reboot back to fastboot
unlock the bootloader
flash twrp
boot into twrp
format phone
then you're done!
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Unfortunately I do not know how to scroll
Our Lord is wrong
PS C:\adb> fastboot devices
7b61ab59 fastboot
PS C:\adb> fastboot flash emmc_appsboot.mbn
unknown partition 'emmc_appsboot.mbn'
error: cannot determine image filename for 'emmc_appsboot.mbn'
PS C:\adb> fastboot flash emmc_appsboot.zip
unknown partition 'emmc_appsboot.zip'
error: cannot determine image filename for 'emmc_appsboot.zip'

That file has to be in adb main file.
Sent from my LEX727 using xda premium

mchlbenner said:
That file has to be in adb main file.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
If you have a file please give me the link
Or where I find it

I think you talk about different terminals.
The X722 with 26S strock brick CAN NOT FLASH FOR FASTBOOT.
Greetings.

fastboot flash emmc_appsboot.mbn <- that command is not correct, that's why it errors saying partition not found. The partition to flash is missing, not sure what partition is supposed to be specified, but the command should look like this...... fastboot flash 'thecorrectpartition' emmc_appsboot.mbn

meangreenie said:
fastboot flash emmc_appsboot.mbn <- that command is not correct, that's why it errors saying partition not found. The partition to flash is missing, not sure what partition is supposed to be specified, but the command should look like this...... fastboot flash 'thecorrectpartition' emmc_appsboot.mbn
Click to expand...
Click to collapse
Explain more please
What should i do
Put the file in disk c
Show me this message
PS C:\adb> fastboot flash thecorrectpartition emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'thecorrectpartition' (791 KB)...
OKAY [ 0.034s]
writing 'thecorrectpartition'...

toufik_d said:
Explain more please
What should i do
Put the file in disk c
Show me this message
PS C:\adb> fastboot flash thecorrectpartition emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'thecorrectpartition' (791 KB)...
OKAY [ 0.034s]
writing 'thecorrectpartition'...
Click to expand...
Click to collapse
Your terminal is blocked. It does not have a solution.
Read this:
https://forum.xda-developers.com/le...velopment--and-mods/try-unbrick-x722-t3686191
What they say is for x720 and x727 NOT FOR X722.
The command they say is:
fastboot flash aboot emmc_appsboot.mbn
but as I say, it's NOT GOING TO WORK.
Greetings.

how you wiped everything?
do you have recovery?

F.J.V said:
Your terminal is blocked. It does not have a solution.
Read this:
https://forum.xda-developers.com/le...velopment--and-mods/try-unbrick-x722-t3686191
What they say is for x720 and x727 NOT FOR X722.
The command they say is:
fastboot flash aboot emmc_appsboot.mbn
but as I say, it's NOT GOING TO WORK.
Greetings.
Click to expand...
Click to collapse
That command work for me.
Lex 727 21s.
Sent from my LEX727 using xda premium

mchlbenner said:
That command work for me.
Lex 727 21s.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Of course.
That's what I say, for X720 and X727.
For X722 DOES NOT WORK
Greetings.

danielpinto8zz6 said:
how you wiped everything?
do you have recovery?
Click to expand...
Click to collapse
I wanted to restore the official order
The device is running on fastboot only

Related

permanent CyanogenMod boot logo

Hi there,
sorry, if this was answered before, but I couldn't find the correct answer:
After trying to flash a custom ROM (CMOD) I'm stuck now at the Cyanogen Mod boot animation.
If pressing "Power" button for a while the phone reboots, but gives me again the same boot animation (after ZUK logo).
If pressing "Power" + "Volume +" + "Volume -" buttons for a while the phone reboots, but gives me again the same boot animation (after ZUK logo).
The phone is not recognized via USB on a computer.
Anybody has still an idea what I could do?
Many thanks in advance for hints
best regards
m
What are the steps you followed before you ended up in this situation? What rom were you previously on? Provide as much details as you can without being redundant.
KKaushal said:
What are the steps you followed before you ended up in this situation? What rom were you previously on? Provide as much details as you can without being redundant.
Click to expand...
Click to collapse
I was coming from latest stock. The attempt was to flash CM14.
1.) flash in the thread linked twrp
2.) flash CM14 and Nougat GAPPS micro
3.) reboot ok
4.) fingerprint didn't react, so went back to recovery and flashed both again, causing this loop
many thanks again for any help/hint
best regards
m
If the first time boot with the rom and gapps was okay, maybe you should try wiping /system, /data, /dalvik and /cache and reflash the rom again.. Since you were in stock cmos 12.1, I think it'll be better if you flash official cm13 first, and then jump to cm14 from there to minimize sensor issues such as with the fingerprint like you experienced.
meikelrix said:
any help/hint
Click to expand...
Click to collapse
Mate if you think you're done with everything and nothing seems to help, just search around here how to flash ZUI using QPST. That's the last resort which saves your device from the gravest issues.
However, let me know if you can or can't find that thread or anything else, I'll be happy to help. :good:
KKaushal said:
If the first time boot with the rom and gapps was okay, maybe you should try wiping /system, /data, /dalvik and /cache and reflash the rom again.. Since you were in stock cmos 12.1, I think it'll be better if you flash official cm13 first, and then jump to cm14 from there to minimize sensor issues such as with the fingerprint like you experienced.
Click to expand...
Click to collapse
thank you, but I did wiping and reflash => causing the loop
best regards
m
sahu.prashant said:
Mate if you think you're done with everything and nothing seems to help, just search around here how to flash ZUI using QPST. That's the last resort which saves your device from the gravest issues.
However, let me know if you can or can't find that thread or anything else, I'll be happy to help. :good:
Click to expand...
Click to collapse
many thanks for offering. Any chance to provide a link, in order to spare some time?
best regards
m
meikelrix said:
I did wiping and reflash => causing the loop
Click to expand...
Click to collapse
There are many reasons for a bootloop. Start from scratch once again. Flash stock cos12.1 (or restore if you have a backup), flash cm13 from there after you load twrp, go from cm13 to cm14. I think this should be the way to go to avoid sensor issues. Once in stock, you can go from there. Good luck.
http://forum.xda-developers.com/zuk-z1/development/how-to-flash-zuk-z1-zui-version-t3265741
This is the thread link right here explaining all the steps (although it's a little tricky to follow )
That was the good part....
The worst part is that the download links are dead
I'll try snooping around more and see if I can find anything else and you should try too since the thread will give you an idea what to look for.
If the search comes up empty, I'll upload the files tomorrow by all means
Fortunately found a link....
http://forum.xda-developers.com/showpost.php?p=64202059&postcount=14
sahu.prashant said:
http://forum.xda-developers.com/zuk-z1/development/how-to-flash-zuk-z1-zui-version-t3265741
This is the thread link right here explaining all the steps (although it's a little tricky to follow )
That was the good part....
The worst part is that the download links are dead
I'll try snooping around more and see if I can find anything else and you should try too since the thread will give you an idea what to look for.
If the search comes up empty, I'll upload the files tomorrow by all means
Fortunately found a link....
https://www.androidfilehost.com/?w=files&flid=40618
Click to expand...
Click to collapse
Heya
many thanks again for your much appreciated help!
I'll try to figure and provide the outcome...
best regards
m
KKaushal said:
There are many reasons for a bootloop. Start from scratch once again. Flash stock cos12.1 (or restore if you have a backup), flash cm13 from there after you load twrp, go from cm13 to cm14. I think this should be the way to go to avoid sensor issues. Once in stock, you can go from there. Good luck.
Click to expand...
Click to collapse
thank you, but I can't start from scratch, since the loop won't let me in
Happy to help and hopefully, outcome will be desirable.
meikelrix said:
thank you, but I can't start from scratch, since the loop won't let me in
Click to expand...
Click to collapse
Power button + volume up gets you into recovery mode.
(I think) Power button + volume down gets you into fastboot mode. Not sure about this one, you can search around for the key combo to get into specific modes. From fastboot mode, you can flash the stock cos 12.1 provided from the official support page of cyanogen. Make sure you download the zip compatible with fastboot mode. When you finally get to cos 12.1, you can install Twrp recovery (also available among the forum threads or from the official twrp website), then flash cm13, reboot to check if everything works and then finally move to cm14.
You can post here in case of problems/confusions in any step.
Alternately, in place of cos12.1, you can flash zui as suggested. Search in the 'help, q/a' section of zuk z1 in this forum. You can find the tutorial there. Good luck.
KKaushal said:
Power button + volume up gets you into recovery mode.
(I think) Power button + volume down gets you into fastboot mode. Not sure about this one, you can search around for the key combo to get into specific modes. From fastboot mode, you can flash the stock cos 12.1 provided from the official support page of cyanogen. Make sure you download the zip compatible with fastboot mode. When you finally get to cos 12.1, you can install Twrp recovery (also available among the forum threads or from the official twrp website), then flash cm13, reboot to check if everything works and then finally move to cm14.
You can post here in case of problems/confusions in any step.
Alternately, in place of cos12.1, you can flash zui as suggested. Search in the 'help, q/a' section of zuk z1 in this forum. You can find the tutorial there. Good luck.
Click to expand...
Click to collapse
Hi,
after draining the battery (and loading up a bit) I could get access to fastboot. From there I flashed latest twrp (3.0.2) and booted into twrp.
From twrp I wiped and then flashed latest Nuclear ROM & Gapps. After rebooting I'm still ending up in twrp, again?
PS: flashing the cos 12.1 via fastboot mode didn't work, due to below:
"
fastboot -i 0x2b4c update cm-12.1-YOG4PAS9IG-ham-signed-fastboot-b9cce4220b.zip
target reported max download size of 1610612736 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(14844,0xa3181000) malloc: *** mach_vm_map(size=1585467392) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1583882000 bytes
error: update package missing system.img
"
many thanks again for any help/hints
best regards
m
meikelrix said:
Hi,
after draining the battery (and loading up a bit) I could get access to fastboot. From there I flashed latest twrp (3.0.2) and booted into twrp.
From twrp I wiped and then flashed latest Nuclear ROM & Gapps. After rebooting I'm still ending up in twrp, again?
PS: flashing the cos 12.1 via fastboot mode didn't work, due to below:
"
fastboot -i 0x2b4c update cm-12.1-YOG4PAS9IG-ham-signed-fastboot-b9cce4220b.zip
target reported max download size of 1610612736 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(14844,0xa3181000) malloc: *** mach_vm_map(size=1585467392) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1583882000 bytes
error: update package missing system.img
"
many thanks again for any help/hints
best regards
m
Click to expand...
Click to collapse
Extract cos zip files and flash separately
Enviado desde mi ZUK Z1 mediante Tapatalk
acuicultor said:
Extract cos zip files and flash separately
Enviado desde mi ZUK Z1 mediante Tapatalk
Click to expand...
Click to collapse
That was it. I did the following sequence:
fastboot -i 0x2b4c flash aboot emmc_appsboot.mbn
fastboot -i 0x2b4c flash modem NON-HLOS.bin
fastboot -i 0x2b4c flash rpm rpm.mbn
fastboot -i 0x2b4c flash sbl1 sbl1.mbn
fastboot -i 0x2b4c flash dbi sdi.mbn
fastboot -i 0x2b4c flash splash splash.img
fastboot -i 0x2b4c flash tz tz.mbn
fastboot -i 0x2b4c flash persist persist.img
reboot device
fastboot -i 0x2b4c flash system system.img
fastboot -i 0x2b4c flash boot boot.img
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c flash cache cache.img
fastboot -i 0x2b4c flash userdata userdata.img
fastboot reboot
Then I was back to stock. After that I started from scratch to flash twrp, Nuclear and Gapps.
Many thanks to all that helped!
best regards
m
Kinda stuck on Sending system. Help?
Try this
https://forum.xda-developers.com/zuk-z1/help/boot-loop-cyanogen-logo-t3666056
moriyaprateek said:
Kinda stuck on Sending system. Help?
Click to expand...
Click to collapse
AFAIR, I followed https://stackoverflow.com/questions/34299245/fastboot-flash-system-img-error
=> "fastboot flash –S 256M system PATH_TO_SYSTEM.img" (the -S switch did the trick)
Even i am in the same situation how to fix it bro
meikelrix said:
Heya
many thanks again for your much appreciated help!
I'll try to figure and provide the outcome...
best regards
m
Click to expand...
Click to collapse
stuck with same situation plz need help

Screwed up phone while rolling back Android 7 - help?

So for some background, I was on EMUI 4.1 and successfully flashed to EMUI 5.
Then, I wanted to rollback so I flashed recovery again and stock firmware. I tried flashing with fastboot and didn't work. I tried using Huawei recovery 3-button method, no luck either.
Errors using fastboot flashing:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system "F:\SYSTEM.img"
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (445721 KB)...
OKAY [ 17.780s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 17.822s
Click to expand...
Click to collapse
Error with 3-button method:
Software install failed!
Incompatibility with current version.
Please download the correct update package.
Click to expand...
Click to collapse
When I was booting into Revolution recovery, I could not mount SD card and some other partitions so maybe that has something to do with the 3-button method problem... Furthermore, I don't know how to check which version exactly my phone is, all I know is that it was VNS-L31.
Now I'm stuck with a phone that is constantly rebooting so how do I proceed?
First of all...
Please tell me you have a backup of your Nougat ROM. If yes, restore it.
I have failed to go back to MM several times like you before.
It really is a question of using the right files.
First, flash the OEMInfo that is provided here in the forums.
Second, flash the right firmware. This one is tricky. For me, ONLY VNS-L31 Version C150 worked. No other.
Flashing with fastboot always never works. It always gives an error on system. So you need to find a firmware that works with 3-button method.
Your task now is the get back to working Nougat, since you did something wrong.
Unlock BL, flash Nougat recovery with fastboot.
Then,
easiest is like I said restoring a backup.
If you don't have one, try flashing the Revolution ROM by BadWolf.
Schlengge said:
First of all...
Please tell me you have a backup of your Nougat ROM. If yes, restore it.
I have failed to go back to MM several times like you before.
It really is a question of using the right files.
First, flash the OEMInfo that is provided here in the forums.
Second, flash the right firmware. This one is tricky. For me, ONLY VNS-L31 Version C150 worked. No other.
Flashing with fastboot always never works. It always gives an error on system. So you need to find a firmware that works with 3-button method.
Your task now is the get back to working Nougat, since you did something wrong.
Unlock BL, flash Nougat recovery with fastboot.
Then,
easiest is like I said restoring a backup.
If you don't have one, try flashing the Revolution ROM by BadWolf.
Click to expand...
Click to collapse
Have just solved the problem with the steps from here.
From my understanding, it seems that I lost almost everything, device info, OEM info, recovery... So no technique was working.
The solution in brief was:
1. Go into bootloader to flash recovery (I used Revolution Recovery)
2. In recovery, flash OEM info.
3. Then used the 3-button method to install stock version for the appropriate model (which I could see from OEM info).
4. Unlocked bootloader, triggering a factory reset. (I was stuck in infinite boot before this point.)
As you say Schlengge, it is a matter of using the right files! Thanks. Problem solved.

Why is everything so difficult on this device?

I constantly encounter roadblocks on this phone. Have not had issues with my OP3, Le Max 2, older Note 4 and Nexus 6 . If ZTE is pro this community, why are things not straightforward? On the OP3, simple lock and unlock commands and flash away. Got to do this and do that, 1001 different ideas from people. Right now, my BL is unlocked and I am trying to reinstall TWRP after upgrading to Nougat. This is the message I get when running my adb command to flash recovery:
I have an unlocked BL and recently upgraded to Nougat, but when I try to reinstall TWRP via fastboot flash method, it fails. I have tried two different versions of TWRP 3.0.3-1 & 3.0.4-1. This is the message I get.
PS C:\adb> fastboot flash recovery twrp-3.0.4-1-a7.img
target reported max download size of 536870912 bytes
sending 'recovery' (14472 KB)...
OKAY [ 0.332s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.363s
Any ideas?
Check here and you'll find the answer...
https://forum.xda-developers.com/axon-7/help/fastboot-recognizing-phone-bootloader-t3492201
you need to revert back the drivers to get fastboot working.
DrakenFX said:
Check here and you'll find the answer...
https://forum.xda-developers.com/axon-7/help/fastboot-recognizing-phone-bootloader-t3492201
you need to revert back the drivers to get fastboot working.
Click to expand...
Click to collapse
It is possible rigth now, for a A2017U full stock in NOUGAT (no unlock, no root) to flash TWRP and jump to LineajeOS 14.1 ?
Thanks
Happened to me. Didn't figure it out on there. You have to re unlock the bootloader to get it to work as it currently shows unlocked but is in fact partially locked. I used the bl unlock kit available and ew unlocked the bootloader then jumped to lineage os. You must get to a point in the zip where it says to fastboot oem unlock and instead type fastboot oem lock. Then start the zip guide from the very beginning again
It's not that difficult, it's just different from hacking a Samsung/HTC device. Just be patient and read. We've all had those same problems and there are workarounds to those problems. But the problem you're running into is you don't have the proper fastboot installed that allows fastboot commands.
https://forum.xda-developers.com/ax...on-7-root-bootloader-unlokced-t3441204/page92
Scroll close to the end, bornlivedie mentions that he did on B15 "Nouget"
Altomugriento said:
It is possible rigth now, for a A2017U full stock in NOUGAT (no unlock, no root) to flash TWRP and jump to LineajeOS 14.1 ?
Thanks
Click to expand...
Click to collapse

[Moto G6 Plus] Unable to locate recovery partition

I bought a new Moto G6 Plus XT1926. My goal is to install a twrp image as recovery and then next the lineage.
I got a weird issue when trying to flash "twrp-3.2.1-37-evert.img" on my 1926 by using "./fastboot flash recovery twrp-3.2.1-37-evert.img" on a mac console. The output is:
XT1926 myMac$ ./fastboot flash recovery recovery.img
sending 'recovery' (29440 KB)...
OKAY [ 0.630s]
writing 'recovery'..
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.634s
Just before I unlocked the Bootloader. I tried:
1. Locking bootloader again and flash => nope
2. Restoring the partition table by the following commands:
./fastboot oem fb_mode_set
./fastboot flash partition gpt.bin
./fastboot flash bootloader bootloader.img
./fastboot flash logo logo.bin
./fastboot flash boot boot.img
Does anyone know why the partition "recovery" may be not present and how to make it flashable?
I flashed a XT1039 multiple times without issues, so I got some experiences. But i am out of ideas here.
How can it be that there simple is no recover on the phone I wonder.
Also I downloaded the "TWRP official" App and installed it within the Moto G stock rom and it also says that it can not locate the recovery.
I tried some stuff for two evenings and now i do not know how to continue...
Thanks for hints!
The Recovery is inside the boot, that's why the G6Plus don't have an official TWRP.
The ones we have are the bootable one with decryption enabled, or a flashable one with no decryption
So instead of flashing the TWRP to the recovery partition, I should flash it to the boot partition?
kietob said:
So instead of flashing the TWRP to the recovery partition, I should flash it to the boot partition?
Click to expand...
Click to collapse
No. Do not flash it at all! Load bootloader on your phone, from a pc with a fb and fastboot on it, run "fastboot boot twrp.img" without quotes and twrp.img matches the filename of the twrp IMG file. At this time we can not install twrp to our device. We can only boot it on our device using a pc every single time you need twrp. There was a twrp.img for our device we could flash with fastboot to install on our device but it does not properly flash files sadly. We are trying to raise funds to buy a device for a recognized developer in hopes of making some real progress on modding this device! Look around the G6 forums here and find the thread if you are able to make a PayPal donation or would like to see if you could donate in another way.
Sent from my moto g(6) plus using Tapatalk
Xplorer4x4 said:
No. Do not flash it at all! Load bootloader on your phone, from a pc with a fb and fastboot on it, run "fastboot boot twrp.img" without quotes and twrp.img matches the filename of the twrp IMG file. At this time we can not install twrp to our device. We can only boot it on our device using a pc every single time you need twrp. There was a twrp.img for our device we could flash with fastboot to install on our device but it does not properly flash files sadly. We are trying to raise funds to buy a device for a recognized developer in hopes of making some real progress on modding this device! Look around the G6 forums here and find the thread if you are able to make a PayPal donation or would like to see if you could donate in another way.
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
Hey, any news about flashable TWRP? How can I donate someone who would work on it?
rafikowy said:
Hey, any news about flashable TWRP? How can I donate someone who would work on it?
Click to expand...
Click to collapse
Sadly no news. We have official TWRP now which is good. I'll talk to the devs and try to figure out if it's worth getting a pool started.
Sent from my Moto G6 Plus using XDA Labs

Bootloop redmi 7a vendor.img cant flash

so im trying this since yesterday
Please help me ive been trying to find solution everything flashes except when i try flashing vendor.img it says vendor error : buffer overreads occured due to invalid sparse header how can i fix this my device is redmi7A with unlocked bootloader using original cable on usb2 slot trying to unbrick it since yesterday using latest flashtool and drivers using this firmware eu version Xiaomi_Redmi_7A_V11.0.3.0.QCMEUXM_20200728.0000.00_EEA_10_XFT also would like to mention i unlocked bootloader installed twrp and formated all partitions (brave man i am) tryed using the default firmware upgrade tool also tryed manually installing vendor.img from the firmware but no success tryed formating the partition under twrp to ext2 and returned it to ext4 didnt try to change the size or anything ....this all because the default firmware couldnt install game me vendor error ... at this point im giving up on it ... if anyone knows what must be done hes welcome :fingers-crossed:
here is the msg :
fastboot flash vendor vendor.img
target reported max download size of 535821312 bytes
sending 'vendor' (290176 KB)...
OKAY [ 9.152s]
writing 'vendor'...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 12.419s
....last time i ever buy a chinese device from 5-6 different firmwares i could test only 2 because the others didnt have all the files required in the images folder .....chinese piece of trash and thats it...no way of restoring my device even with the default firmware i still cannot understand did i do something wrong or what......
What says when you tried to flash the vendor with twrp?
first check if you using the newest fastboot version via: fastboot --version
are u sure that you have the EEA Hardware?
when u have access to twrp(recovery) try sideload via adb sideload
and here is a how to flash manually link:
[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5
How to flash a factory image | Return to stock | Unroot your Nexus 5 Hello Nexus 5 Users! I see many users that don't know how to restore their Nexus 5 to stock. It may come in handy, either when you want to RMA your phone, or you want to...
forum.xda-developers.com
plstanchev said:
....last time i ever buy a chinese device .....chinese piece of trash and thats it...
Click to expand...
Click to collapse
this could happen to you with any device! for me the 7A is a really great device. if you unlocked your bootloader you know that there is always a chance to brick your phone! so take responsibility for your actions and don't blame the manufacturer.
PS: if you use more dots and enter it would be much more better to read through your post if someone is trying to help :/
I am also not responsible if anything goes wrong.
May be your download file is corrupted, have you checked the integrity of that file, the extension (.tgz) fastboot firmware.
And flash them with mitool and always download from official site.

Categories

Resources