Unsuccessful Moto E 3G Flash? - Android Q&A, Help & Troubleshooting

Just found my old Moto e 2nd gen and decided to root it. I have unlocked the bootloader, When I flash with the twrp found here http://forum.xda-developers.com/moto-e-2015/orig-development/twrp-recovery-moto-e-3g-2015-t3084849 I do fastboot flash recovery FILENAME.img and it says
target reported max download size of 268435456 bytes
sending 'recovery' (7658 KB)...
OKAY [ 0.326s]
writing 'recovery'...
OKAY [ 0.228s]
finished. total time: 0.559s
Every thing seems good but when I press the volume down two times and go to recovery mode it just refreshes the screen. In bootloader logs it says Boot Up Failed every time I attempt to load into the recovery.
Product/Cariant: surnia XT1526 8GB P3
Serial: TA09805E9S

adsf
Bump

Related

Problem when flashing custom recovey Moto E 2015

I have used Twrp recovery to get custom recovery. While flashing the recovery it showing like this
(bootloader) has-slot:recovery: not found
target reported max download size of 268435456 bytes
sending 'recovery' (8092 KB)...
OKAY [ 0.263s]
writing 'recovery'...
OKAY [ 0.840s]
finished. total time: 1.115s.
I want to know if someone is experiencing the same error and if they have fixed it and how. Thanks.

Fastboot errors

Hello everyone. I have some issues with Fastboot. whenever I try to flash recovery.img i get this error. my device is Cherry Mobile Touch xl 2 with android 6.0 and mt6580.
C:\android-sdk_r24.4.1-windows\android-sdk-windows\platform-tools>fastboot flash flash recovery.img
target reported max download size of 134217728 bytes
sending 'flash' (10678 KB)...
OKAY [ 0.266s]
writing 'flash'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.281s
When I try to just boot into custom recovery, everything goes well except that the phone just reboots. it does not boot into custom recovery. I heard it from somewhere that fastboot boot recovery.img command did not work anymore. Is this true?
C:\android-sdk_r24.4.1-windows\android-sdk-windows\platform-tools>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.281s]
booting...
OKAY [ 0.063s]
finished. total time: 0.344s
Thank you for your help.

TWRP for Zenfone 3 Zoom

Now that we have our own forum I figure I might as well put this here (taken from guide here).
1. Unlock the boot loader with the instructions / app from Asus
2. Download TWRP. Specifically twrp-3.1.0-0-Z01H-20170408.img ** [edit: also rename to twrp.img once downloaded]
4. Reboot to fastboot by rebooting the phone, and pressing the down arrow during the unlock screen.
5. Flash the recovery image `fastboot flash recovery twrp.img`
6. I had to power cycle the phone completely to get TWRP running.
Original post:
https://www.reddit.com/r/zenfone/comments/6gqha5/zenfone_3_ze553kl_z01hd_root/
C:\adb>fastboot.exe flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (33422 KB)...
OKAY [ 0.737s]
writing 'recovery'...
OKAY [ 0.454s]
finished. total time: 1.197s
It's not working, I have no idea why.

TWRP Oreo

Hello guys, i've unlock bootloader using motorola official method but after run command to flash TWRP the next message appears:
PS D:\Alan\Moto Z\fastboot> fastboot flash recovery .\twrp-3.2.3-0-griffin.img
target reported max download size of 536870912 bytes
sending 'recovery' (23344 KB)...
OKAY [ 0.496s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.761s]
finished. total time: 1.261s
Any way to install TWRP in Oreo?
alanflanker said:
Hello guys, i've unlock bootloader using motorola official method but after run command to flash TWRP the next message appears:
PS D:\Alan\Moto Z\fastboot> fastboot flash recovery .\twrp-3.2.3-0-griffin.img
target reported max download size of 536870912 bytes
sending 'recovery' (23344 KB)...
OKAY [ 0.496s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.761s]
finished. total time: 1.261s
Any way to install TWRP in Oreo?
Click to expand...
Click to collapse
After flashing you need to reboot to recovery.

Anti Rollback

Hi everyone, couldn't find anything relevant on the internet and the forum about the rollback problem, there is any way to install custons ROMs with that anabled? since i bought my moto g8 power mid last year i never could install any custom rom because of that, fastboot always give me anti-rollbakc warning and won't flash some partitons so it always ended up bootlooping and i go back to stock, there is any way to disable that feature? or bypass, how can i solve this problem?
Below is the fastboot log of what usually happens.
Code:
writing 'vbmeta_a'...
(bootloader) WARNING: vbmeta_a anti rollback downgrade, 10 vs 14
OKAY [ 0.007s]
finished. total time: 0.017s
Here are the full version of the previous log i posted, i was trying to install the HavocOS via fastboot
Code:
C:\Users\henri\Documents\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 805261312 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 1.519s]
writing 'boot_a'...
OKAY [ 1.058s]
finished. total time: 2.579s
C:\Users\henri\Documents\Minimal ADB and Fastboot>fastboot flash product product.img
target reported max download size of 805261312 bytes
sending sparse 'product_a' 1/3 (720896 KB)...
OKAY [ 17.117s]
writing 'product_a' 1/3...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.121s
C:\Users\henri\Documents\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 805261312 bytes
sending sparse 'system_a' 1/2 (720896 KB)...
OKAY [ 17.125s]
writing 'system_a' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.129s
C:\Users\henri\Documents\Minimal ADB and Fastboot>fastboot flash vbmeta vbmeta.img
target reported max download size of 805261312 bytes
sending 'vbmeta_a' (4 KB)...
OKAY [ 0.009s]
writing 'vbmeta_a'...
(bootloader) WARNING: vbmeta_a anti rollback downgrade, 0 vs 14
OKAY [ 0.011s]
finished. total time: 0.020s
You definitely are in fastboot d? Not just the bootloader?
When you are flashing the inages, if you have a green robot and some text down the bottom, that is fastboot/bootloader.
Fastboot d is different, you will definitely know if you are in fastboot d.
Beetle84 said:
You definitely are in fastboot d? Not just the bootloader?
When you are flashing the inages, if you have a green robot and some text down the bottom, that is fastboot/bootloader.
Fastboot d is different, you will definitely know if you are in fastboot d.
Click to expand...
Click to collapse
That was on bootloader, i searched about the fastboot d but couldn't find any explanation/tutorial how to enter it, i tried the command fastboot reboot fastboot but it gives unknown fastboot target, can you help me?
Fastboot reboot fastboot is the correct way from the bootloader.
You need to update your platform tools.
Also you need to be on android 10 for these roms to boot.
One of the guys helped me out with this earlier. After you've unlocked your boot loader and if your on android 11.
Use rescue & smart assistant to backup your stock rom, it will tell you what kind it is too....
Then go download the android 10 stock version.
Then use moto tools by vache and load the android 10 stock rom into it. Just follow the directions and place it in bootloader.
after that flash whatever puppy of your choosing. Also I'd advise against flashing twrp just boot it. Also if you do use twrp, make sure you don't reboot from side B! you will brick your device....
Beetle84 said:
Fastboot reboot fastboot is the correct way from the bootloader.
You need to update your platform tools.
Also you need to be on android 10 for these roms to boot.
Click to expand...
Click to collapse
That solved all the problem i was facing, thanks
revengesrage said:
One of the guys helped me out with this earlier. After you've unlocked your boot loader and if your on android 11.
Use rescue & smart assistant to backup your stock rom, it will tell you what kind it is too....
Then go download the android 10 stock version.
Then use moto tools by vache and load the android 10 stock rom into it. Just follow the directions and place it in bootloader.
after that flash whatever puppy of your choosing. Also I'd advise against flashing twrp just boot it. Also if you do use twrp, make sure you don't reboot from side B! you will brick your device....
Click to expand...
Click to collapse
Thansk for the tips, it is really important to set the partitions, i was struggling a lot to boot system since twrp redirected things to side B while A was set, i don't know why but now everthing is running flawlessly

Categories

Resources