[ROM] Qualcomm Factory ROM - Redmi Note 3 Pro - AOSP - Xiaomi Redmi Note 3 Guides, News, & Discussion

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

Related

Help! soft brick while upgrading to update 3.0

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.

Unable to flash anything in fastboot - unable to enumerate usb device

Hello everybody, I've been using a Zuk Z1 since november and I'm quite satisfied with it.
Some months ago, the G Sensor stopped to work. I've tried the calibration, it seems successful but it doesn't work at all. So I'd like to try another rom, hoping it'll be working again.
Some months ago, I installed Cyanogenmod 13 and, immediately after, ZUI but it didn't work correctly with my smartwatch so I dediced to go back to the original COS, also restoring Cyanogen Recovery. Now I can't flash anything from fastboot: both on Windows 10 and Linux (on three different computers), I can use ADB when the phone is on COS, but when in fastboot I get a "unable to enumerate usb device" and isn't recognised at all.
Is there anything I can try go get out of this problem? I can go to recovery, but can't flash anything as it says that the signature isn't correct.
Thank you.
draga said:
Hello everybody, I've been using a Zuk Z1 since november and I'm quite satisfied with it.
Some months ago, the G Sensor stopped to work. I've tried the calibration, it seems successful but it doesn't work at all. So I'd like to try another rom, hoping it'll be working again.
Some months ago, I installed Cyanogenmod 13 and, immediately after, ZUI but it didn't work correctly with my smartwatch so I dediced to go back to the original COS, also restoring Cyanogen Recovery. Now I can't flash anything from fastboot: both on Windows 10 and Linux (on three different computers), I can use ADB when the phone is on COS, but when in fastboot I get a "unable to enumerate usb device" and isn't recognised at all.
Is there anything I can try go get out of this problem? I can go to recovery, but can't flash anything as it says that the signature isn't correct.
Thank you.
Click to expand...
Click to collapse
I am having the exact same problem. I have to send the phone back for warranty.
I have been trying to use the ALL IN ONE Tool for ZUK and ZUK Tool Beta. Below is the message after which nothing happens. I will post more details and if someone can help me that will be great.
Flashing your Zuk Z1 back to stock. Please wait...
-----------------------------------------------
target reported max download size of 1610612736 bytes
sending 'persist' (4664 KB)...
OKAY [ 0.149s]
writing 'persist'...
OKAY [ 0.090s]
finished. total time: 0.239s
target reported max download size of 1610612736 bytes
sending 'modem' (58545 KB)...
OKAY [ 1.849s]
writing 'modem'...
OKAY [ 0.837s]
finished. total time: 2.686s
target reported max download size of 1610612736 bytes
sending 'sbl1' (280 KB)...
OKAY [ 0.012s]
writing 'sbl1'...
OKAY [ 0.010s]
finished. total time: 0.022s
target reported max download size of 1610612736 bytes
sending 'dbi' (17 KB)...
OKAY [ 0.004s]
writing 'dbi'...
OKAY [ 0.006s]
finished. total time: 0.010s
target reported max download size of 1610612736 bytes
sending 'aboot' (414 KB)...
OKAY [ 0.015s]
writing 'aboot'...
OKAY [ 0.017s]
finished. total time: 0.033s
target reported max download size of 1610612736 bytes
sending 'rpm' (189 KB)...
OKAY [ 0.009s]
writing 'rpm'...
OKAY [ 0.009s]
finished. total time: 0.018s
target reported max download size of 1610612736 bytes
sending 'splash' (562 KB)...
OKAY [ 0.021s]
writing 'splash'...
OKAY [ 0.013s]
finished. total time: 0.034s
target reported max download size of 1610612736 bytes
sending 'tz' (339 KB)...
OKAY [ 0.013s]
writing 'tz'...
OKAY [ 0.013s]
finished. total time: 0.026s
target reported max download size of 1610612736 bytes
sending 'boot' (6538 KB)...
OKAY [ 0.208s]
writing 'boot'...
OKAY [ 0.097s]
finished. total time: 0.305s
target reported max download size of 1610612736 bytes
sending 'recovery' (9168 KB)...
OKAY [ 0.292s]
writing 'recovery'...
OKAY [ 0.135s]
finished. total time: 0.427s
target reported max download size of 1610612736 bytes
erasing 'system'...
OKAY [ 0.086s]
sending 'system' (1546759 KB)...

Moto G5 Plus XT1685 bootloop after falshing

Guys i have problm in flashing my phone moto g5 plus XT1685
i didn't find the correct firmware to flash it , i find XT1681-XT1683
So the problem is before flashing my phone i got update from the system i update phone then i try to downgrade and i fail ...
i try to upgrade from version 7.0 to 7.1 using other firmware "XT1710-08_ALBUS_RETCN_7.1.1_NZS26.71-97-41_cid11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip"
so i flashing it by cmd with 1 erreur the gpt.bin file but system didn't boot it stay in bootloop ....
here is the stap 1 :
+fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.007s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.085s
+fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.123s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.563s]
finished. total time: 0.691s
+fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (2163 KB)...
OKAY [ 0.057s]
writing 'logo'...
OKAY [ 0.078s]
finished. total time: 0.140s
+fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.391s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.321s]
finished. total time: 0.723s
+fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.482s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.424s]
finished. total time: 0.919s
+fastboot flash dsp adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.367s]
writing 'dsp'...
OKAY [ 0.186s]
finished. total time: 0.567s
+fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (540 KB)...
OKAY [ 0.034s]
writing 'oem'...
OKAY [ 0.110s]
finished. total time: 0.153s
+fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (523949 KB)...
OKAY [ 11.582s]
writing 'system'...
OKAY [ 4.377s]
finished. total time: 15.974s
+fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (513455 KB)...
OKAY [ 11.304s]
writing 'system'...
OKAY [ 4.061s]
finished. total time: 15.377s
+fastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (498532 KB)...
OKAY [ 10.994s]
writing 'system'...
OKAY [ 3.518s]
finished. total time: 14.523s
+fastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system' (514493 KB)...
OKAY [ 11.340s]
writing 'system'...
OKAY [ 3.683s]
finished. total time: 127.939s
+fastboot flash system system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system' (514690 KB)...
OKAY [ 11.333s]
writing 'system'...
OKAY [ 3.681s]
finished. total time: 15.026s
+fastboot flash system system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system' (516519 KB)...
OKAY [ 11.398s]
writing 'system'...
OKAY [ 3.761s]
finished. total time: 15.170s
+fastboot flash system system.img_sparsechunk.6
target reported max download size of 536870912 bytes
sending 'system' (505615 KB)...
OKAY [ 11.126s]
writing 'system'...
OKAY [ 3.622s]
finished. total time: 14.761s
+fastboot flash system system.img_sparsechunk.7
target reported max download size of 536870912 bytes
sending 'system' (468359 KB)...
OKAY [ 10.347s]
writing 'system'...
OKAY [ 3.866s]
finished. total time: 14.228s
+fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (75244 KB)...
OKAY [ 1.675s]
writing 'modem'...
OKAY [ 0.668s]
finished. total time: 2.355s
+fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.037s]
finished. total time: 0.039s
+fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.053s]
finished. total time: 0.061s
+fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (880 KB)...
OKAY [ 0.047s]
writing 'fsg'...
OKAY [ 0.103s]
finished. total time: 0.165s
+fastboot erase cache
erasing 'cache'...
OKAY [ 0.030s]
finished. total time: 0.032s
+fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.072s]
finished. total time: 0.074s
+fastboot erase customize
erasing 'customize'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.037s
+fastboot erase clogo
erasing 'clogo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.022s
+fastboot oem fb_mode_clear
...
OKAY [ 0.006s]
finished. total time: 0.008s
+fastboot reboot
rebooting...
finished. total time: 0.007s
Click to expand...
Click to collapse
so after that i try to flash the firmware from the official site motorola
i download the latest one "NPN25.137-92_cid50" and when i falsh it here is what happen in step 2 :
Here the firmware step 2 :
+fastboot oem fb_mode_set
...
OKAY [ 0.005s]
finished. total time: 0.007s
+fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.081s
+fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.122s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.426s
+fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.052s]
writing 'logo'...
OKAY [ 0.075s]
finished. total time: 0.133s
+fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.392s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.312s]
finished. total time: 0.708s
+fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.478s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.424s]
finished. total time: 0.907s
+fastboot flash dsp adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.368s]
writing 'dsp'...
OKAY [ 0.178s]
finished. total time: 0.551s
fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (75646 KB)...
OKAY [ 1.658s]
writing 'oem'...
OKAY [ 0.627s]
finished. total time: 2.291s
+fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (509755 KB)...
OKAY [ 11.181s]
writing 'system'...
OKAY [ 4.218s]
finished. total time: 15.405s
+fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (508223 KB)...
OKAY [ 11.132s]
writing 'system'...
OKAY [ 4.205s]
finished. total time: 15.341s
+fastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (523648 KB)...
OKAY [ 11.447s]
writing 'system'...
OKAY [ 3.799s]
finished. total time: 15.252s
+fastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system' (500822 KB)...
OKAY [ 10.973s]
writing 'system'...
OKAY [ 3.867s]
finished. total time: 14.842s
+fastboot flash system system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system' (433268 KB)...
OKAY [ 9.517s]
writing 'system'...
OKAY [ 3.425s]
finished. total time: 12.948s
+fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (74880 KB)...
OKAY [ 1.649s]
writing 'modem'...
OKAY [ 0.659s]
finished. total time: 2.316s
+fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.025s]
finished. total time: 0.027s
+fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.025s]
finished. total time: 0.026s
+fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (2528 KB)...
OKAY [ 0.060s]
writing 'fsg'...
OKAY [ 0.077s]
finished. total time: 0.142s
+fastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.018s
+fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.050s]
finished. total time: 0.052s
+fastboot erase customize
erasing 'customize'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.010s
+fastboot erase clogo
erasing 'clogo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.008s
+fastboot oem fb_mode_clear
...
OKAY [ 0.146s]
finished. total time: 0.147s
Click to expand...
Click to collapse
Note that in stap 1 : bootloader.img of other frimwear are pass in falshing ... mean higth kernel then 7.0 is passed
but the 2 first step didn't pass in my stap 2 i donne
the phone stay in bootloop
i need to bypass the gpt.bin and bootloader.img to can back the phone work in normal ... if i'm wrong help me
is there way to break security ? or to edit the gpt.bin and bootloader.img to modify the xml files called "gpt.default.xml". , please help me ...
is there tool to extract .img and .bin files ???
i can't flash firmware to my phone correcte

Screen turned black while flashing image

Ok guys let me get to point fast!
I tried to flash 8.1 leaked beat build. connected my usb cable and executed flash_a_all.bat . There was inconsistency in connection my usb conected and disconnected for a moment and the bootloader turned all black.
No light on keys or from screen but vibrates when connection to computer or power + (vol +) or power + (vol-)
in my device manager, the phones is connnected as "Qualcomm HS-USB Diagnostics 900E"
this is how flashing ended
Please help me here guys !!!
HTML:
[HTML](bootloader) Device already : unlocked!
OKAY [ 0.030s]
finished. total time: 0.031s
target reported max download size of 534773760 bytes
sending 'modem_a' (86016 KB)...
OKAY [ 3.039s]
writing 'modem_a'...
OKAY [ 0.419s]
finished. total time: 3.459s
target reported max download size of 534773760 bytes
sending 'sbl1' (384 KB)...
OKAY [ 0.068s]
writing 'sbl1'...
OKAY [ 0.024s]
finished. total time: 0.094s
target reported max download size of 534773760 bytes
sending 'rpm' (172 KB)...
OKAY [ 0.038s]
writing 'rpm'...
OKAY [ 0.022s]
finished. total time: 0.063s
target reported max download size of 534773760 bytes
sending 'tz' (1516 KB)...
OKAY [ 0.088s]
writing 'tz'...
OKAY [ 0.028s]
finished. total time: 0.119s
target reported max download size of 534773760 bytes
sending 'devcfg' (40 KB)...
OKAY [ 0.039s]
writing 'devcfg'...
OKAY [ 0.023s]
finished. total time: 0.062s
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.590s]
writing 'dsp'...
FAILED (remote: check crc failed)
finished. total time: 0.806s
target reported max download size of 534773760 bytes
sending 'aboot' (584 KB)...
OKAY [ 0.047s]
writing 'aboot'...
FAILED (remote: check crc failed)
finished. total time: 0.079s
target reported max download size of 534773760 bytes
sending 'boot_a' (14880 KB)...
OKAY [ 0.540s]
writing 'boot_a'...
FAILED (remote: check crc failed)
finished. total time: 0.736s
target reported max download size of 534773760 bytes
Invalid sparse file format at header magic
sending sparse 'system_a' 1/6 (515622 KB)...
OKAY [ 17.525s]
writing 'system_a' 1/6...
OKAY [ 9.171s]
sending sparse 'system_a' 2/6 (510059 KB)...
OKAY [ 17.378s]
writing 'system_a' 2/6...
OKAY [ 9.401s]
sending sparse 'system_a' 3/6 (518707 KB)...
OKAY [ 17.880s]
writing 'system_a' 3/6...
OKAY [ 20.688s]
sending sparse 'system_a' 4/6 (481011 KB)...
OKAY [ 16.422s]
writing 'system_a' 4/6...
OKAY [ 8.830s]
sending sparse 'system_a' 5/6 (521581 KB)...
OKAY [ 17.874s]
writing 'system_a' 5/6...
OKAY [ 9.791s]
sending sparse 'system_a' 6/6 (308870 KB)...
OKAY [ 10.707s]
writing 'system_a' 6/6...
FAILED (status read failed (Too many links))
finished. total time: 156.759s
target didn't report max-download-size
sending 'lksecapp' (60 KB)...
FAILED (command write failed (No error))
finished. total time: 0.006s
target didn't report max-download-size
sending 'cmnlib' (204 KB)...
FAILED (command write failed (No error))
finished. total time: 0.003s
target didn't report max-download-size
sending 'cmnlib64' (256 KB)...
FAILED (command write failed (No error))
finished. total time: -0.000s
target didn't report max-download-size
sending 'keymaster' (224 KB)...
FAILED (command write failed (No error))
finished. total time: 0.000s
error: Device does not support slots
...
FAILED (command write failed (No error))
finished. total time: 0.004s
< waiting for any device >
rebooting...
finished. total time: 0.016s
Press any key to exit...
[/HTML]

Y6II Cam-L23 Bricked, Huawei usb com 1.0

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

Categories

Resources