TLDR/update: false alarm, after a pc reboot. and leaving the shield unplugged for a few min. i was able to "adb reboot bootloader" then reflash with fastboot, all good now. mods feel free to delete this bs...
i downloaded the official 3.0 recovery image from nvidia and commented out the bit to flash there recovery so i could keep twrp just like i have previously w/o issues. now im stuck and cant seem to access the bootloader by holding the power button, adb, or fastboot. what other options do i have? flashing from update.zip on sd card?
Code:
./flash-all.sh
< waiting for any device >
target reported max download size of 67108864 bytes
sending 'staging' (3091 KB)...
OKAY [ 0.091s]
writing 'staging'...
OKAY [ 0.152s]
finished. total time: 0.243s
target reported max download size of 67108864 bytes
sending 'boot' (21772 KB)...
OKAY [ 0.527s]
writing 'boot'...
OKAY [ 1.024s]
finished. total time: 1.551s
rebooting...
finished. total time: 0.059s
< waiting for any device >
sending 'system' (1578475 KB)...
FAILED (command write failed (Protocol error))
finished. total time: 0.000s
target reported max download size of 67108864 bytes
erasing 'vendor'...
OKAY [ 0.164s]
sending sparse 'vendor' (65498 KB)...
OKAY [ 1.606s]
writing 'vendor'...
OKAY [ 3.285s]
sending sparse 'vendor' (65472 KB)...
OKAY [ 1.582s]
writing 'vendor'...
OKAY [ 2.895s]
sending sparse 'vendor' (65532 KB)...
OKAY [ 1.611s]
writing 'vendor'...
OKAY [ 3.437s]
sending sparse 'vendor' (48152 KB)...
OKAY [ 1.196s]
writing 'vendor'...
OKAY [ 2.448s]
finished. total time: 18.223s
rebooting...
if it didnt sent the reboot command i could have seen the error and hopefully fixed it. guess i gave nvidia too much credit for error detection in there script.
Hi ,
after an day of searching on the web, i found out the Redmi Note 3 Pro Test ROM (AOSP)
Video: https://www.youtube.com/watch?v=xI6lNYEcgS8
Disclaimer:
Do it on your own risk
Steps for flashing:
0 DOWNLOAD ALL
1 UNZIP SYSTEM.ZIP
2 MOVE ALL ON THE SAME FOLDER
3 PUT THE PHONE IN FASTBOOT MODE
4 OPEN "PROMPT COMMANDS" ON THE FOLDER
5 MOVE "8976_fastboot_all_images.bat" ON PROMPT
4 PLUG IN THE PHONE
5 PUSH ENTER
6 WAIT...
7 ENJOY!!
Video: https://www.youtube.com/watch?v=ZI7v8Rv_-5w
What works?
All works fine but missing only the fingerprint voice on settings.
Is multilanguage?
Yes.
Is for normal use?
Yes and not, you need to clean the ROM from some developing apps,
install OpenGapps arm x64 5.1.1 (only pico works).
Can i install custom recovery?
Yes you can. No patch on boot needed.
FINGERPRINT ON SETTINGS IS MISSING.
FASTBOOT ROM:
https://mega.nz/#F!g5kUgILY!60ZoAWdCtY7LPABO4IMpvw
RECOVERY ROM
(for the work thx to @xinkonging ,for the upload thx to @DrWillz ):
https://mega.nz/#!bldGhI7b!PMiMnZCYSwXpdfTouuuE2F9MZPbPUqCNjfuz4FIP3ts
OK, tried it and its pretty good, especially if like me you like a bare bones Android experience that you can customise.
I rooted it, installed gapps, installed the xposed framework, gravity-box, greenify, adaway etc all working pretty well. Changed the DPI settings also as I like less zoomed in experience. Nova launcher is looking pretty well !!!
I will see what the battery life is like overnight and decide if I will keep using it until we get a decent CM12.1 (or ideally CM13).
Only negatives are as OP said are the fingerprint reader cannot be enabled and in a few places it definitely looks like a 'test ROM'. There are some minimal test apps, but faced with a choice of lots of MIUI apps or a few test apps I would rather the few tests app. The camara App is pretty good IMO also.
jeromeof said:
OK, tried it and its pretty good, especially if like me you like a bare bones Android experience that you can customise.
I rooted it, installed gapps, installed the xposed framework, gravity-box, greenify, adaway etc all working pretty well. Changed the DPI settings also as I like less zoomed in experience. Nova launcher is looking pretty well !!!
I will see what the battery life is like overnight and decide if I will keep using it until we get a decent CM12.1 (or ideally CM13).
Only negatives are as OP said are the fingerprint reader cannot be enabled and in a few places it definitely looks like a 'test ROM'. There are some minimal test apps, but faced with a choice of lots of MIUI apps or a few test apps I would rather the few tests app. The camara App is pretty good IMO also.
Click to expand...
Click to collapse
Thx for the feedback )
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
Do I need to unlock the bootloader first ?
borg79 said:
Do I need to unlock the bootloader first ?
Click to expand...
Click to collapse
no
Does this work on redmi note 3 pro with 2gb ram and 16gb internal?
thanks for AOSP
asdafdasdaf said:
Does this work on redmi note 3 pro with 2gb ram and 16gb internal?
thanks for AOSP
Click to expand...
Click to collapse
Yep
Overall I've got the following impression of this firmware:
1. Switching from 3G -> 4G is more reliable than on any MIUI rom. First of all I don't loose internet connectivity during the switch (with MIUI I always do) and secondly it founds 4G networks almost instantly, and for MIUI it took minutes.
2. I've tried to flash open gapps stock - it basically made them unusable (was unable to create account), but open gapps mini worked ok for me. Though got a problem with black home screen and very slow phone until I've changed home launcher back to trebuschet.
3. Battery usage also increased in my use cases. I usually got 25% battery/8h, but now it's more like 35%/8h. Though it may be related to the fact that all messangers, etc syncs as often as they want, and with MIUI I never was able to properly receive all push notifications, etc for most of the apps.
4. According to some benchmarks, it seems that this rom is a tiny bit faster. (geekbench results increased by 7% for example). Though that doesn't really matter for me.
5. I usually have more RAM available and apps killed less aggressively.
Civilus said:
Overall I've got the following impression of this firmware:
1. Switching from 3G -> 4G is more reliable than on any MIUI rom. First of all I don't loose internet connectivity during the switch (with MIUI I always do) and secondly it founds 4G networks almost instantly, and for MIUI it took minutes.
2. I've tried to flash open gapps stock - it basically made them unusable (was unable to create account), but open gapps mini worked ok for me. Though got a problem with black home screen and very slow phone until I've changed home launcher back to trebuschet.
3. Battery usage also increased in my use cases. I usually got 25% battery/8h, but now it's more like 35%/8h. Though it may be related to the fact that all messangers, etc syncs as often as they want, and with MIUI I never was able to properly receive all push notifications, etc for most of the apps.
4. According to some benchmarks, it seems that this rom is a tiny bit faster. (geekbench results increased by 7% for example). Though that doesn't really matter for me.
5. I usually have more RAM available and apps killed less aggressively.
Click to expand...
Click to collapse
And camera? http://en.miui.com/thread-251822-1-1.html loook this
Inviato dal mio kenzo utilizzando Tapatalk
Naphtha said:
And camera? http://en.miui.com/thread-251822-1-1.html loook this
Inviato dal mio kenzo utilizzando Tapatalk
Click to expand...
Click to collapse
There is a strange focal distance thing...
Why are the focal distances not the same? I mean, it should be 2.0 on PRO for both MIUI and SD ROMs...
Kenzo and 2.2?? Completely strange...
masseselsev said:
There is a strange focal distance thing...
Why are the focal distances not the same? I mean, it should be 2.0 on PRO for both MIUI and SD ROMs...
Kenzo and 2.2?? Completely strange...
Click to expand...
Click to collapse
2.2 and 2.0 is the iris
Inviato dal mio kenzo utilizzando Tapatalk
I have unlocked the bootloader. Can i flash this rom?
Gửi từ Redmi Note 3 của tôi bằng cách sử dụng Tapatalk
HoaPham98 said:
I have unlocked the bootloader. Can i flash this rom?
Gửi từ Redmi Note 3 của tôi bằng cách sử dụng Tapatalk
Click to expand...
Click to collapse
Yep!! :highfive:
device locked
Hi Bro,
I'm facing device locked issue please help
here is the error from promt
G:\Fastboot ROM>"G:\Fastboot ROM\8976_fastboot_all_images.bat"
error: device not found
for not erase modemst1 and modemst2
< waiting for device >
target reported max download size of 536870912 bytes
sending 'tz' (629 KB)...
OKAY [ 0.020s]
writing 'tz'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.020s
target reported max download size of 536870912 bytes
sending 'sbl1' (346 KB)...
OKAY [ 0.020s]
writing 'sbl1'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.020s
target reported max download size of 536870912 bytes
sending 'rpm' (161 KB)...
OKAY [ 0.010s]
writing 'rpm'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'aboot' (560 KB)...
OKAY [ 0.020s]
writing 'aboot'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.020s
target reported max download size of 536870912 bytes
sending 'hyp' (72 KB)...
OKAY [ 0.000s]
writing 'hyp'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'tzbak' (629 KB)...
OKAY [ 0.020s]
writing 'tzbak'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.030s
target reported max download size of 536870912 bytes
sending 'sbl1bak' (346 KB)...
OKAY [ 0.010s]
writing 'sbl1bak'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'rpmbak' (161 KB)...
OKAY [ 0.010s]
writing 'rpmbak'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.020s
target reported max download size of 536870912 bytes
sending 'abootbak' (560 KB)...
OKAY [ 0.020s]
writing 'abootbak'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.030s
target reported max download size of 536870912 bytes
sending 'hypbak' (72 KB)...
OKAY [ -0.000s]
writing 'hypbak'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.010s
erasing 'boot'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'modem' (83542 KB)...
OKAY [ 2.734s]
writing 'modem'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 2.734s
error: cannot load 'system.img'
target reported max download size of 536870912 bytes
erasing 'cache'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.003s
target reported max download size of 536870912 bytes
erasing 'userdata'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'recovery' (32663 KB)...
OKAY [ 1.061s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 1.061s
target reported max download size of 536870912 bytes
sending 'boot' (32015 KB)...
OKAY [ 1.030s]
writing 'boot'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 1.030s
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.530s]
writing 'dsp'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.540s
target reported max download size of 536870912 bytes
sending 'mdtp' (3684 KB)...
OKAY [ 0.122s]
writing 'mdtp'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.122s
erasing 'splash'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'splash' (633 KB)...
OKAY [ 0.030s]
writing 'splash'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.030s
erasing 'DDR'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.020s
rebooting...
finished. total time: -0.000s
G:\Fastboot ROM>
D!nnU said:
Hi Bro,
I'm facing device locked issue please help
here is the error from promt
G:\Fastboot ROM>"G:\Fastboot ROM\8976_fastboot_all_images.bat"
error: device not found
for not erase modemst1 and modemst2
< waiting for device >
target reported max download size of 536870912 bytes
sending 'tz' (629 KB)...
OKAY [ 0.020s]
writing 'tz'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.020s
target reported max download size of 536870912 bytes
sending 'sbl1' (346 KB)...
OKAY [ 0.020s]
writing 'sbl1'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.020s
target reported max download size of 536870912 bytes
sending 'rpm' (161 KB)...
OKAY [ 0.010s]
writing 'rpm'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'aboot' (560 KB)...
OKAY [ 0.020s]
writing 'aboot'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.020s
target reported max download size of 536870912 bytes
sending 'hyp' (72 KB)...
OKAY [ 0.000s]
writing 'hyp'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'tzbak' (629 KB)...
OKAY [ 0.020s]
writing 'tzbak'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.030s
target reported max download size of 536870912 bytes
sending 'sbl1bak' (346 KB)...
OKAY [ 0.010s]
writing 'sbl1bak'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'rpmbak' (161 KB)...
OKAY [ 0.010s]
writing 'rpmbak'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.020s
target reported max download size of 536870912 bytes
sending 'abootbak' (560 KB)...
OKAY [ 0.020s]
writing 'abootbak'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.030s
target reported max download size of 536870912 bytes
sending 'hypbak' (72 KB)...
OKAY [ -0.000s]
writing 'hypbak'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.010s
erasing 'boot'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'modem' (83542 KB)...
OKAY [ 2.734s]
writing 'modem'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 2.734s
error: cannot load 'system.img'
target reported max download size of 536870912 bytes
erasing 'cache'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.003s
target reported max download size of 536870912 bytes
erasing 'userdata'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'recovery' (32663 KB)...
OKAY [ 1.061s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 1.061s
target reported max download size of 536870912 bytes
sending 'boot' (32015 KB)...
OKAY [ 1.030s]
writing 'boot'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 1.030s
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.530s]
writing 'dsp'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.540s
target reported max download size of 536870912 bytes
sending 'mdtp' (3684 KB)...
OKAY [ 0.122s]
writing 'mdtp'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.122s
erasing 'splash'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'splash' (633 KB)...
OKAY [ 0.030s]
writing 'splash'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.030s
erasing 'DDR'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.020s
rebooting...
finished. total time: -0.000s
G:\Fastboot ROM>
Click to expand...
Click to collapse
I'm on 7.1.8.0 stable rom
D!nnU said:
I'm on 7.1.8.0 stable rom
Click to expand...
Click to collapse
You need to unlock bootloader before flashing the ROM
Thank you i had submited for bootloader unlock code.
Sent from my Redmi Note 3 using XDA Free mobile app
how to flash this rom on locked bootloader?
how to flash this rom on locked bootloader? and its flashed how to root it and install Twrp?
Unlock bootloader first . is better.
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
hi,
i already posted this, 3 days ago in another root thread,
a friend of mine tried to flash his phone after bootloader unlocked ok, but after the flash phone bricked, and ask me for help, now I'm asking as well,
tried:
IMAGE Download Software - IDTML01Ver1001 and CAML00LMAA001063_Board_Software_null_null_Android_ 6.0_EMUI_4.1_05021XEW, it always gives error but it seems to flash the fastboot at least, so the phone from: huawei usb com 1.0 goes to fastboot, so in adb i try:
C:\SDK\platform-tools>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (455490 KB)...
OKAY [ 62.178s]
writing 'system' 1/6...
OKAY [ 30.954s]
sending sparse 'system' 2/6 (447920 KB)...
OKAY [ 25.925s]
writing 'system' 2/6...
OKAY [ 30.355s]
sending sparse 'system' 3/6 (460685 KB)...
OKAY [ 20.218s]
writing 'system' 3/6...
OKAY [ 31.334s]
sending sparse 'system' 4/6 (454527 KB)...
OKAY [ 19.641s]
writing 'system' 4/6...
OKAY [ 30.797s]
sending sparse 'system' 5/6 (458441 KB)...
OKAY [ 19.465s]
writing 'system' 5/6...
OKAY [ 30.925s]
sending sparse 'system' 6/6 (20484 KB)...
OKAY [ 0.859s]
writing 'system' 6/6...
OKAY [ 1.406s]
finished. total time: 304.135s
C:\SDK\platform-tools>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (253973 KB)...
OKAY [ 10.453s]
writing 'cust'...
OKAY [ 17.159s]
finished. total time: 27.612s
C:\SDK\platform-tools>fastboot flash userdata userdata.img
target reported max download size of 471859200 bytes
sending 'userdata' (44124 KB)...
OKAY [ 1.770s]
writing 'userdata'...
OKAY [ 3.053s]
finished. total time: 4.838s
C:\SDK\platform-tools>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (23514 KB)...
OKAY [ 1.188s]
writing 'boot'...
FAILED (remote: flash write prim vrl failure)
finished. total time: 1.531s
C:\SDK\platform-tools>fastboot flash fastboot1 fastboot.img
target reported max download size of 471859200 bytes
sending 'fastboot1' (2194 KB)...
OKAY [ 0.141s]
writing 'fastboot1'...
FAILED (remote: image verification error)
finished. total time: 0.188s
C:\SDK\platform-tools>fastboot flash fastboot2 fastboot.img
target reported max download size of 471859200 bytes
sending 'fastboot2' (2194 KB)...
OKAY [ 0.063s]
writing 'fastboot2'...
FAILED (remote: partition does not exist)
finished. total time: 0.078s
C:\SDK\platform-tools>fastboot flash fastboot fastboot.img
target reported max download size of 471859200 bytes
sending 'fastboot' (2194 KB)...
OKAY [ 0.062s]
writing 'fastboot'...
FAILED (remote: flash write prim vrl failure)
finished. total time: 0.156s
C:\SDK\platform-tools>fastboot flash cache cache.img
target reported max download size of 471859200 bytes
sending 'cache' (6248 KB)...
OKAY [ 0.312s]
writing 'cache'...
OKAY [ 0.453s]
finished. total time: 0.766s
C:\SDK\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (37966 KB)...
OKAY [ 1.531s]
writing 'recovery'...
FAILED (remote: flash write prim vrl failure)
finished. total time: 2.031s
--------------------------------------------------------------------------------------------------
so I'm able to flash successfully
system, cust, cache and userdata
but not able:
recovery, fastboot or boot, and after i fastboot reboot,
again only red and green led and huawei usb com 1.0, to start again
thank you very much indeed, for any guide or help, or maybe a cam-l23 board software to try
Hi!
What software do you use?
I hard brico my P8 Lite ALE...
I download rom form Huawei finder and came a wrong one... -.-
So PC only see him as HUAWEI USB COM 1.0.
Your have a similar software, maybe we can hel each other!
Thanks.
hi
persona78 said:
Hi!
What software do you use?
I hard brico my P8 Lite ALE...
I download rom form Huawei finder and came a wrong one... -.-
So PC only see him as HUAWEI USB COM 1.0.
Your have a similar software, maybe we can hel each other!
Thanks.
Click to expand...
Click to collapse
you should try to find:
***IMAGE Download Software*** - IDTML01Ver1001 and CAML00LMAA001063_***Board_Software_null_null_Android***_ 6.0_EMUI_4.1_05021XEW
for your model
thanks to you, for your attention
atv said:
you should try to find:
***IMAGE Download Software*** - IDTML01Ver1001 and CAML00LMAA001063_***Board_Software_null_null_Android***_ 6.0_EMUI_4.1_05021XEW
for your model
thanks to you, for your attention
Click to expand...
Click to collapse
Hi!
Can you provid me that files and a litle tut how to use it?
.
On fastboot, can you unlock bootloader?
-
alguien con el board software
Hi all
My phone is in bootloop since many day. I was on Lineage 18.1 with deezer and google maps installed (only theses 2 apps)
After turning off (for the first time) because there was no battery left. It never restarted
And even worse, the erecoevery is no longer accessible, the TWRP is broken ..
I only have access to Fastboot.
I tested flashing a TWRP or booting on a TWRP via fastboot command ... Impossible. It crashes before splash to the TWRP. (which appears an half second)
I tested hisuite which recognizes my phone in fastboot but does not recognize the model and refuses to restore a system: "device not supported"
I am trying to flash a complete system (via command terminal or via ZRK tool) = impossible to reboot
Bellow the result of my commands
Does anyone have a suggestion for me ?
Code:
./fastboot erase system -w
Erasing 'system' OKAY [ 75.573s]
Finished. Total time: 75.632s
./fastboot flash cache CACHE.img
Sending 'cache' (6200 KB) OKAY [ 0.175s]
Writing 'cache' OKAY [ 0.176s]
Finished. Total time: 0.379s
./fastboot flash crc CRC.img
Sending 'crc' (235 KB) OKAY [ 0.013s]
Writing 'crc' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash curver CURVER.img
Sending 'curver' (0 KB) OKAY [ 0.007s]
Writing 'curver' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash dts DTS.img
Sending 'dts' (23678 KB) OKAY [ 0.679s]
Writing 'dts' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash efi EFI.img
Sending 'efi' (17 KB) OKAY [ 0.007s]
Writing 'efi' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash kernel KERNEL.img
Sending 'kernel' (24576 KB) OKAY [ 0.698s]
Writing 'kernel' OKAY [ 0.865s]
Finished. Total time: 1.590s
./fastboot flash modem_fw MODEM_FW.img
Sending 'modem_fw' (98304 KB) OKAY [ 2.745s]
Writing 'modem_fw' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash modemnvm_update MODEMNVM_UPDATE.img
Sending 'modemnvm_update' (14224 KB) OKAY [ 0.396s]
Writing 'modemnvm_update' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash odm ODM.img
Sending 'odm' (109702 KB) OKAY [ 3.108s]
Writing 'odm' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash package_type PACKAGE_TYPE.img
Sending 'package_type' (0 KB) OKAY [ 0.007s]
Writing 'package_type' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash product PRODUCT.img
Sending 'product' (113532 KB) OKAY [ 3.186s]
Writing 'product' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash ramdisk RAMDISK.img
Sending 'ramdisk' (16384 KB) OKAY [ 0.464s]
Writing 'ramdisk' OKAY [ 0.398s]
Finished. Total time: 0.890s
./fastboot flash recovery_ramdisk RECOVERY_RAMDISK.img
Sending 'recovery_ramdisk' (32768 KB) OKAY [ 0.930s]
Writing 'recovery_ramdisk' OKAY [ 0.800s]
Finished. Total time: 1.760s
./fastboot flash recovery_vbmeta RECOVERY_VBMETA.img
Sending 'recovery_vbmeta' (6 KB) OKAY [ 0.007s]
Writing 'recovery_vbmeta' OKAY [ 0.030s]
Finished. Total time: 0.067s
./fastboot flash recovery_vendor RECOVERY_VENDOR.img
Sending 'recovery_vendor' (16384 KB) OKAY [ 0.464s]
Writing 'recovery_vendor' OKAY [ 0.401s]
Finished. Total time: 0.896s
./fastboot flash sensorhub SENSORHUB.img
Sending 'sensorhub' (820 KB) OKAY [ 0.027s]
Writing 'sensorhub' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash system SYSTEM.img
Sending sparse 'system' 1/6 (460799 KB) OKAY [ 13.234s]
Writing 'system' OKAY [ 12.118s]
Sending sparse 'system' 2/6 (460074 KB) OKAY [ 13.597s]
Writing 'system' OKAY [ 12.556s]
Sending sparse 'system' 3/6 (460751 KB) OKAY [ 13.416s]
Writing 'system' OKAY [ 11.778s]
Sending sparse 'system' 4/6 (453466 KB) OKAY [ 13.196s]
Writing 'system' OKAY [ 11.609s]
Sending sparse 'system' 5/6 (454756 KB) OKAY [ 12.975s]
Writing 'system' OKAY [ 11.150s]
Sending sparse 'system' 6/6 (418060 KB) OKAY [ 11.904s]
Writing 'system' OKAY [ 10.762s]
Finished. Total time: 148.684s
./fastboot flash teeos TEEOS.img
Sending 'teeos' (2576 KB) OKAY [ 0.075s]
Writing 'teeos' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash trustfirmware TRUSTFIRMWARE.img
Sending 'trustfirmware' (115 KB) OKAY [ 0.010s]
Writing 'trustfirmware' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash vbmeta VBMETA.img
Sending 'vbmeta' (9 KB) OKAY [ 0.007s]
Writing 'vbmeta' OKAY [ 0.027s]
Finished. Total time: 0.060s
./fastboot flash vendor VENDOR.img
Sending sparse 'vendor' 1/2 (460710 KB) OKAY [ 13.273s]
Writing 'vendor' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash verlist VERLIST.img
Sending 'verlist' (0 KB) OKAY [ 0.007s]
Writing 'verlist' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash xloader XLOADER.img
Sending 'xloader' (68 KB) OKAY [ 0.008s]
Writing 'xloader' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
naced said:
Hi all
My phone is in bootloop since many day. I was on Lineage 18.1 with deezer and google maps installed (only theses 2 apps)
After turning off (for the first time) because there was no battery left. It never restarted
And even worse, the erecoevery is no longer accessible, the TWRP is broken ..
I only have access to Fastboot.
I tested flashing a TWRP or booting on a TWRP via fastboot command ... Impossible. It crashes before splash to the TWRP. (which appears an half second)
I tested hisuite which recognizes my phone in fastboot but does not recognize the model and refuses to restore a system: "device not supported"
I am trying to flash a complete system (via command terminal or via ZRK tool) = impossible to reboot
Bellow the result of my commands
Does anyone have a suggestion for me ?
Code:
./fastboot erase system -w
Erasing 'system' OKAY [ 75.573s]
Finished. Total time: 75.632s
./fastboot flash cache CACHE.img
Sending 'cache' (6200 KB) OKAY [ 0.175s]
Writing 'cache' OKAY [ 0.176s]
Finished. Total time: 0.379s
./fastboot flash crc CRC.img
Sending 'crc' (235 KB) OKAY [ 0.013s]
Writing 'crc' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash curver CURVER.img
Sending 'curver' (0 KB) OKAY [ 0.007s]
Writing 'curver' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash dts DTS.img
Sending 'dts' (23678 KB) OKAY [ 0.679s]
Writing 'dts' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash efi EFI.img
Sending 'efi' (17 KB) OKAY [ 0.007s]
Writing 'efi' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash kernel KERNEL.img
Sending 'kernel' (24576 KB) OKAY [ 0.698s]
Writing 'kernel' OKAY [ 0.865s]
Finished. Total time: 1.590s
./fastboot flash modem_fw MODEM_FW.img
Sending 'modem_fw' (98304 KB) OKAY [ 2.745s]
Writing 'modem_fw' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash modemnvm_update MODEMNVM_UPDATE.img
Sending 'modemnvm_update' (14224 KB) OKAY [ 0.396s]
Writing 'modemnvm_update' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash odm ODM.img
Sending 'odm' (109702 KB) OKAY [ 3.108s]
Writing 'odm' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash package_type PACKAGE_TYPE.img
Sending 'package_type' (0 KB) OKAY [ 0.007s]
Writing 'package_type' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash product PRODUCT.img
Sending 'product' (113532 KB) OKAY [ 3.186s]
Writing 'product' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash ramdisk RAMDISK.img
Sending 'ramdisk' (16384 KB) OKAY [ 0.464s]
Writing 'ramdisk' OKAY [ 0.398s]
Finished. Total time: 0.890s
./fastboot flash recovery_ramdisk RECOVERY_RAMDISK.img
Sending 'recovery_ramdisk' (32768 KB) OKAY [ 0.930s]
Writing 'recovery_ramdisk' OKAY [ 0.800s]
Finished. Total time: 1.760s
./fastboot flash recovery_vbmeta RECOVERY_VBMETA.img
Sending 'recovery_vbmeta' (6 KB) OKAY [ 0.007s]
Writing 'recovery_vbmeta' OKAY [ 0.030s]
Finished. Total time: 0.067s
./fastboot flash recovery_vendor RECOVERY_VENDOR.img
Sending 'recovery_vendor' (16384 KB) OKAY [ 0.464s]
Writing 'recovery_vendor' OKAY [ 0.401s]
Finished. Total time: 0.896s
./fastboot flash sensorhub SENSORHUB.img
Sending 'sensorhub' (820 KB) OKAY [ 0.027s]
Writing 'sensorhub' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash system SYSTEM.img
Sending sparse 'system' 1/6 (460799 KB) OKAY [ 13.234s]
Writing 'system' OKAY [ 12.118s]
Sending sparse 'system' 2/6 (460074 KB) OKAY [ 13.597s]
Writing 'system' OKAY [ 12.556s]
Sending sparse 'system' 3/6 (460751 KB) OKAY [ 13.416s]
Writing 'system' OKAY [ 11.778s]
Sending sparse 'system' 4/6 (453466 KB) OKAY [ 13.196s]
Writing 'system' OKAY [ 11.609s]
Sending sparse 'system' 5/6 (454756 KB) OKAY [ 12.975s]
Writing 'system' OKAY [ 11.150s]
Sending sparse 'system' 6/6 (418060 KB) OKAY [ 11.904s]
Writing 'system' OKAY [ 10.762s]
Finished. Total time: 148.684s
./fastboot flash teeos TEEOS.img
Sending 'teeos' (2576 KB) OKAY [ 0.075s]
Writing 'teeos' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash trustfirmware TRUSTFIRMWARE.img
Sending 'trustfirmware' (115 KB) OKAY [ 0.010s]
Writing 'trustfirmware' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash vbmeta VBMETA.img
Sending 'vbmeta' (9 KB) OKAY [ 0.007s]
Writing 'vbmeta' OKAY [ 0.027s]
Finished. Total time: 0.060s
./fastboot flash vendor VENDOR.img
Sending sparse 'vendor' 1/2 (460710 KB) OKAY [ 13.273s]
Writing 'vendor' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash verlist VERLIST.img
Sending 'verlist' (0 KB) OKAY [ 0.007s]
Writing 'verlist' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash xloader XLOADER.img
Sending 'xloader' (68 KB) OKAY [ 0.008s]
Writing 'xloader' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Click to expand...
Click to collapse
Hi...
you write that you flashed a TWRP via fastboot and then try to reboot from fastboot mode to TWRP recovery right?
But there is no command to reboot from fastboot directly to recovery like fastboot reboot-recovery or some thing else!
you just can use the command fastboot reboot
then instant unplug the usb-cable and press/hold Vol+ button
i repeat...
fastboot reboot-->enter
unplug the usb cable
press and hold Vol+ button (just the 1 button Vol+ nothing more needet)
good luck
solong
speedson
Receiving the following error.. bootp is my patched image.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot C:\Users\Scott\Pictures\bootp.img
target reported max download size of 268435456 bytes
sending 'boot_a' (98304 KB)...
OKAY [ 2.656s]
writing 'boot_a'...
(bootloader) Image missing cmdline or OS version
FAILED (remote: Failed to write to partition Bad Buffer Size)
finished. total time: 2.954s