Database Develop

Trying to update from My Rom 1.2

Hi all, I need some (or much) help I'm trying to update to the 602 version, to EMUI 3.0 or the lollipop but I really can´t figure out how, downloaded 'My Rom v3.3' according to instructions I should update to 602 I've already downloaded a CWM flashable 'http://forum.xda-developers.com/ascend-p7/general/cwm-flashable-b609-p7-l10-complete-t3004343' tryed to flash CWM via fastboot but nothing happens when I try to go to recovery just as the latest TWRP, What I'm missing? Please help. :crying:

KV92GT said:
Hi all, I need some (or much) help I'm trying to update to the 602 version, to EMUI 3.0 or the lollipop but I really can´t figure out how, downloaded 'My Rom v3.3' according to instructions I should update to 602 I've already downloaded a CWM flashable 'http://forum.xda-developers.com/ascend-p7/general/cwm-flashable-b609-p7-l10-complete-t3004343' tryed to flash CWM via fastboot but nothing happens when I try to go to recovery just as the latest TWRP, What I'm missing? Please help. :crying:
Click to expand...
Click to collapse
Hi! You need to flash the stock recovery, b133 or b135 unfortunately I do not have those files, there's a post pointing to stock recovery but links are dead, may be someone here could be kind enough to provide those images for us

KV92GT said:
Hi all, I need some (or much) help I'm trying to update to the 602 version, to EMUI 3.0 or the lollipop but I really can´t figure out how, downloaded 'My Rom v3.3' according to instructions I should update to 602 I've already downloaded a CWM flashable 'http://forum.xda-developers.com/ascend-p7/general/cwm-flashable-b609-p7-l10-complete-t3004343' tryed to flash CWM via fastboot but nothing happens when I try to go to recovery just as the latest TWRP, What I'm missing? Please help. :crying:
Click to expand...
Click to collapse
I am exactly in the same situation for several weeks.....
My actual config is
My-Rom V1.2
TWRP 2.8.1.0
I want to upgrade to either My-Rom 3.3 or Stock lollipop
The main issue is that I can't do that with my actual recovery, and no other recovery works on my phone, no idea why.
The only recovery img that is working is the one I use at the moment: openrecovery-twrp-2.8.1.0.img
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery [COLOR="Green"]openrecovery-twrp-2.8.1.0.img[/COLOR]
target reported max download size of 838860800 bytes
sending 'recovery' (11896 KB)...
OKAY [ 0.463s]
writing 'recovery'...
OKAY [ 0.582s]
finished. total time: 1.047s
Here's a little peak on all recovery img files I have tried so far:
cwm.img
recovery_cwm.img
CWM-6.0.5.0.img
B609_recovery.img
recovery-clockwork-3.0.0.5-ascend.img
TWRP-2.8.7.0.img
TWRP-2.8.7.0.img
openrecovery-twrp-2.8.1.0.img
And you can see below that the flashing procedure is completely normal for all attempts
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery D:\Users\tom\Downloads\cwm.img
target reported max download size of 838860800 bytes
sending 'recovery' (11848 KB)...
OKAY [ 0.458s]
writing 'recovery'...
OKAY [ 0.671s]
finished. total time: 1.130s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.001s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery D:\Users\tom\Downloads\recovery_cwm.img
target reported max download size of 838860800 bytes
sending 'recovery' (11848 KB)...
OKAY [ 0.461s]
writing 'recovery'...
OKAY [ 0.559s]
finished. total time: 1.023s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.001s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery \\NAS1\tom\Firmwares\HuaweiP7\CWM-6.0.5.0.img
target reported max download size of 838860800 bytes
sending 'recovery' (11848 KB)...
OKAY [ 0.458s]
writing 'recovery'...
OKAY [ 0.570s]
finished. total time: 1.032s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.001s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery \\NAS1\tom\Firmwares\HuaweiP7\B609_recovery.img
target reported max download size of 838860800 bytes
sending 'recovery' (16384 KB)...
OKAY [ 0.634s]
writing 'recovery'...
OKAY [ 0.793s]
finished. total time: 1.430s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery D:\Users\tom\Downloads\recovery-clockwork-3.0.0.5-ascend.img
target reported max download size of 838860800 bytes
sending 'recovery' (3636 KB)...
OKAY [ 0.145s]
writing 'recovery'...
OKAY [ 0.169s]
finished. total time: 0.317s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery D:\Users\tom\Downloads\TWRP-2.8.7.0.img
target reported max download size of 838860800 bytes
sending 'recovery' (13182 KB)...
OKAY [ 0.512s]
writing 'recovery'...
OKAY [ 0.643s]
finished. total time: 1.157s
I grabbed all those recovery img here on the P7 forums and they are apparently working for most of us.
Consider I flashed each of them at least 5 times. None of them works but the last one.
The most horrible is that I don't even know WHY ???????
I have read countless threads in this forum to unblock the situation and I am still nowhere because, if I have found a few people having the same issue, I could not found any valid solution.
If you can, please help.

Well... Here you have it
Do it at YOUR OWN RISK!
This is the STOCK RECOVERY B135 from my Huawey Ascend P7
You can flash it using flashify or go with the fastboot procedure
1. Unpack it
2. Flash it
'https://mega.nz/#!0pF0jawS!Q8NNIkYIy_k2e6abgTYvAoyT11M92HL5iG9riG3f7-k'

SiulGKT said:
Well... Here you have it
Do it at YOUR OWN RISK!
This is the STOCK RECOVERY B135 from my Huawey Ascend P7
You can flash it using flashify or go with the fastboot procedure
1. Unpack it
2. Flash it
'https://mega.nz/#!0pF0jawS!Q8NNIkYIy_k2e6abgTYvAoyT11M92HL5iG9riG3f7-k'
Click to expand...
Click to collapse
Thank you! downloading,do you recommend flashify?

KV92GT said:
Thank you! downloading,do you recommend flashify?
Click to expand...
Click to collapse
You'de welcome, yes!

SiulGKT said:
You'de welcome, yes!
Click to expand...
Click to collapse
Thank you very much SiulGKT it worked like a charm! now I will try to update to 3.3! :laugh:

Crippius said:
I am exactly in the same situation for several weeks.....
My actual config is
My-Rom V1.2
TWRP 2.8.1.0
I want to upgrade to either My-Rom 3.3 or Stock lollipop
The main issue is that I can't do that with my actual recovery, and no other recovery works on my phone, no idea why.
The only recovery img that is working is the one I use at the moment: openrecovery-twrp-2.8.1.0.img
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery [COLOR="Green"]openrecovery-twrp-2.8.1.0.img[/COLOR]
target reported max download size of 838860800 bytes
sending 'recovery' (11896 KB)...
OKAY [ 0.463s]
writing 'recovery'...
OKAY [ 0.582s]
finished. total time: 1.047s
Here's a little peak on all recovery img files I have tried so far:
cwm.img
recovery_cwm.img
CWM-6.0.5.0.img
B609_recovery.img
recovery-clockwork-3.0.0.5-ascend.img
TWRP-2.8.7.0.img
TWRP-2.8.7.0.img
openrecovery-twrp-2.8.1.0.img
And you can see below that the flashing procedure is completely normal for all attempts
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery D:\Users\tom\Downloads\cwm.img
target reported max download size of 838860800 bytes
sending 'recovery' (11848 KB)...
OKAY [ 0.458s]
writing 'recovery'...
OKAY [ 0.671s]
finished. total time: 1.130s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.001s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery D:\Users\tom\Downloads\recovery_cwm.img
target reported max download size of 838860800 bytes
sending 'recovery' (11848 KB)...
OKAY [ 0.461s]
writing 'recovery'...
OKAY [ 0.559s]
finished. total time: 1.023s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.001s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery \\NAS1\tom\Firmwares\HuaweiP7\CWM-6.0.5.0.img
target reported max download size of 838860800 bytes
sending 'recovery' (11848 KB)...
OKAY [ 0.458s]
writing 'recovery'...
OKAY [ 0.570s]
finished. total time: 1.032s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.001s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery \\NAS1\tom\Firmwares\HuaweiP7\B609_recovery.img
target reported max download size of 838860800 bytes
sending 'recovery' (16384 KB)...
OKAY [ 0.634s]
writing 'recovery'...
OKAY [ 0.793s]
finished. total time: 1.430s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery D:\Users\tom\Downloads\recovery-clockwork-3.0.0.5-ascend.img
target reported max download size of 838860800 bytes
sending 'recovery' (3636 KB)...
OKAY [ 0.145s]
writing 'recovery'...
OKAY [ 0.169s]
finished. total time: 0.317s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery D:\Users\tom\Downloads\TWRP-2.8.7.0.img
target reported max download size of 838860800 bytes
sending 'recovery' (13182 KB)...
OKAY [ 0.512s]
writing 'recovery'...
OKAY [ 0.643s]
finished. total time: 1.157s
I grabbed all those recovery img here on the P7 forums and they are apparently working for most of us.
Consider I flashed each of them at least 5 times. None of them works but the last one.
The most horrible is that I don't even know WHY ???????
I have read countless threads in this forum to unblock the situation and I am still nowhere because, if I have found a few people having the same issue, I could not found any valid solution.
If you can, please help.
Click to expand...
Click to collapse
I've uploaded the b135, give it a try.
---------- Post added at 04:41 PM ---------- Previous post was at 04:36 PM ----------
KV92GT said:
Thank you very much SiulGKT it worked like a charm! now I will try to update to 3.3! :laugh:
Click to expand...
Click to collapse
Glad to see it! You're welcome! Good luck!

There's an improvement for sure, to not say a breakthrough
I am in the Huwaei recovery and it is currently installing the B609 update.app that I put in dload folder.
Crossing fingers!
A big up to you already man :good:

B135 Installed
B609 Installed
B621 installing
Thanks again @SiulGKT

SiulGKT said:
Well... Here you have it
Do it at YOUR OWN RISK!
This is the STOCK RECOVERY B135 from my Huawey Ascend P7
You can flash it using flashify or go with the fastboot procedure
1. Unpack it
2. Flash it
'https://mega.nz/#!0pF0jawS!Q8NNIkYIy_k2e6abgTYvAoyT11M92HL5iG9riG3f7-k'
Click to expand...
Click to collapse
Hello, I'm sorry but when i try to download your file, mega is asking for a key, can you give me this key?
Hope you still have it

i cant lock the bootloader of my nexus 6

hello i can't lock the bootloader of my nexus 6 since i received it from the technical service of motorola. before i send it to them it was closed and when i received it it was unlock and another no padlock its apear when is booting. ive traid every thing but nothing work
i can flash factory images but i cant relock it. fastboot oem lock works on my nexus 7 but not on my nexus 6

You should use the correct command, as google documents it.
But locking your bootloader is a pretty bad idea, and will prevent you from having any ability to fix anything if it fails to boot. If you cannot boot into android, you cannot enable unlock, and will be locked out for good with no recourse other then to send it in.
See this page
https://source.android.com/security/verifiedboot/verified-boot.html
Scroll down to "changing the device state" and use the given fastboot command.

i want to lock it because motorola say to me if the bootloader is open there is no wanrranty so thats my problem

alex482 said:
i want to lock it because motorola say to me if the bootloader is open there is no wanrranty so thats my problem
Click to expand...
Click to collapse
If it boots you can lock it. If it doesn't boot, then they won't know either.
But if you lock it, and an OTA mucks it up, then you can send it to repair, and won't have a phone for weeks.

istperson said:
If it boots you can lock it. If it doesn't boot, then they won't know either.
But if you lock it, and an OTA mucks it up, then you can send it to repair, and won't have a phone for weeks.
Click to expand...
Click to collapse
i dont know i was tried :
fastboot oem lock and fastboot flashing lock and its doesnt work
but on my nexus 7 its work perfectly

alex482 said:
i dont know i was tried :
fastboot oem lock and fastboot flashing lock and its doesnt work
but on my nexus 7 its work perfectly
Click to expand...
Click to collapse
Do other adb/fastboot commands work?

What does
Code:
fastboot devices
say?

yes its work adb devices , adb reboot, adb reboot bootloader, fastboot flash...., fastboot devices , fastboot reboot and fastboot reboot-bootloader

istperson said:
What does
Code:
fastboot devices
say?
Click to expand...
Click to collapse
C:\Program Files (x86)\platform-tools>fastboot devices
ZX1G423BMR fastboot

C:\Program Files (x86)\platform-tools>fastboot oem lock
...
(bootloader) Please flash valid signed images firstly!
FAILED (remote failure)
finished. total time: 0.077s
that it what it say when i tried to lock it but i also tried to flash the factory image its work but then when i try to lock it the same massage appear again

Please paste here the output of flashing the factory image.

istperson said:
Please paste here the output of flashing the factory image.
Click to expand...
Click to collapse
yes when its finish i copy and past everything here

I'd be curious what specific error it gives with the fastboot flashing lock says, as that should be the command now assuming your on MM and using up to date SDK.

C:\Program Files (x86)\platform-tools>adb devices
List of devices attached
ZX1G423BMR device
C:\Program Files (x86)\platform-tools>adb reboot bootloader
C:\Program Files (x86)\platform-tools>fastboot devices
ZX1G423BMR fastboot
C:\Program Files (x86)\platform-tools>fastboot erase boot
erasing 'boot'...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Program Files (x86)\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.048s]
finished. total time: 0.048s
C:\Program Files (x86)\platform-tools>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.014s]
finished. total time: 0.016s
C:\Program Files (x86)\platform-tools>fastboot erase system
erasing 'system'...
OKAY [ 0.617s]
finished. total time: 0.617s
C:\Program Files (x86)\platform-tools> fastboot flash bootloader bootloader-shamu-moto-apq8084-71.15.img
target reported max download size of 536870912 bytes
sending 'bootloader' (10387 KB)...
OKAY [ 0.409s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.685s]
finished. total time: 1.102s
C:\Program Files (x86)\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.004s
C:\Program Files (x86)\platform-tools>fastboot flash radio radio-shamu-d4.01-9625-05.27+fsg-9625-02.104.img
target reported max download size of 536870912 bytes
sending 'radio' (115487 KB)...
OKAY [ 4.283s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.522s]
finished. total time: 5.808s
C:\Program Files (x86)\platform-tools>fastboot reboot bootloader
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Program Files (x86)\platform-tools>fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system' (517178 KB)...
OKAY [ 20.071s]
writing 'system'...
OKAY [ 6.964s]
sending sparse 'system' (515137 KB)...
OKAY [ 20.267s]
writing 'system'...
OKAY [ 7.088s]
sending sparse 'system' (518219 KB)...
OKAY [ 20.493s]
writing 'system'...
OKAY [ 7.188s]
sending sparse 'system' (492726 KB)...
OKAY [ 19.042s]
writing 'system'...
OKAY [ 6.804s]
finished. total time: 107.938s
C:\Program Files (x86)\platform-tools>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (8197 KB)...
OKAY [ 0.316s]
writing 'boot'...
OKAY [ 0.116s]
finished. total time: 0.431s
C:\Program Files (x86)\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (8915 KB)...
OKAY [ 0.334s]
writing 'recovery'...
OKAY [ 0.126s]
finished. total time: 0.463s
C:\Program Files (x86)\platform-tools>fasboot flash cache cache.img
"fasboot" no se reconoce como un comando interno o externo,
programa o archivo por lotes ejecutable.
C:\Program Files (x86)\platform-tools>fastboot flash cache cache.img
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.057s]
sending 'cache' (6248 KB)...
OKAY [ 0.237s]
writing 'cache'...
OKAY [ 0.137s]
finished. total time: 0.446s
C:\Program Files (x86)\platform-tools>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 1.349s]
finished. total time: 1.349s
C:\Program Files (x86)\platform-tools>fastboot flash userdata userdata.img
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 1.165s]
sending 'userdata' (138868 KB)...
OKAY [ 5.070s]
writing 'userdata'...
OKAY [ 3.001s]
finished. total time: 9.236s
C:\Program Files (x86)\platform-tools>fastboot oem lock
...
(bootloader) Please flash valid signed images firstly!
FAILED (remote failure)
finished. total time: 0.070s
C:\Program Files (x86)\platform-tools>fastboot reboot
rebooting...
finished. total time: -0.000s

yes im on 6.0 marshmallow and the sdk with the latest update

Just a couple of questions. If you go to Settings, is Developer mode off or on? If it's not on, please turn it on and check if Enable OEM unlocking is on or off.
But this as well can be an incompatible hardware error. Why did you send it for repairs?

istperson said:
Just a couple of questions. If you go to Settings, is Developer mode off or on? If it's not on, please turn it on and check if Enable OEM unlocking is on or off.
But this as well can be an incompatible hardware error. Why did you send it for repairs?
Click to expand...
Click to collapse
yes its all turn on i send to it to change the rear camera because it was factory failure

Then it too must be a hardware problem.

do you think so?

alex482 said:
do you think so?
Click to expand...
Click to collapse
It seems, you did everything right. The line "(bootloader) Please flash valid signed images firstly!" is returned by the bootloader, and the bootloader is, opposite to adb and fastboot, closed source. So no help from the source.
I googled it, and it appeared on the Moto G 2014 device.

Flashed Potter by mistake on Sanders Need help.

I have tried following guides on going back to stock rom but getting many errors in doing that. I have also tried flashing many different roms with TWRP. I get many errors when doing that one of them is local error 7. One also tells me that it detects OEM partition now at potter. The model of this device is XT1806.
This is my attempt to get things back to stock.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem fb_mode_set
...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.016s]
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.094s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash bootloader bootloader.img
target reported max download size of 534773760 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.141s]
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.538s]
finished. total time: 0.695s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (71925 KB)...
OKAY [ 2.068s]
writing 'modem'...
OKAY [ 1.067s]
finished. total time: 3.151s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (3024 KB)...
OKAY [ 0.078s]
writing 'fsg'...
OKAY [ 0.109s]
finished. total time: 0.203s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dsp adspso.bin
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.488s]
writing 'dsp'...
OKAY [ 0.284s]
finished. total time: 0.787s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2192 KB)...
OKAY [ 0.063s]
writing 'logo'...
OKAY [ 0.125s]
finished. total time: 0.188s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.492s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.375s]
finished. total time: 0.867s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.614s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.484s]
finished. total time: 1.098s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.0
target reported max download size of 534773760 bytes
sending 'system' (256355 KB)...
OKAY [ 7.384s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.415s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.1
target reported max download size of 534773760 bytes
sending 'system' (262115 KB)...
OKAY [ 7.538s]
writing 'system'...
OKAY [ 3.399s]
finished. total time: 10.937s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.2
target reported max download size of 534773760 bytes
sending 'system' (259034 KB)...
OKAY [ 7.468s]
writing 'system'...
OKAY [ 3.535s]
finished. total time: 11.019s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.3
target reported max download size of 534773760 bytes
sending 'system' (262013 KB)...
OKAY [ 7.507s]
writing 'system'...
OKAY [ 3.523s]
finished. total time: 11.046s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.4
target reported max download size of 534773760 bytes
sending 'system' (262142 KB)...
OKAY [ 7.517s]
writing 'system'...
OKAY [ 3.387s]
finished. total time: 10.920s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.5
target reported max download size of 534773760 bytes
sending 'system' (262140 KB)...
OKAY [ 7.492s]
writing 'system'...
OKAY [ 3.283s]
finished. total time: 10.775s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.6
target reported max download size of 534773760 bytes
sending 'system' (259637 KB)...
OKAY [ 7.466s]
writing 'system'...
OKAY [ 3.293s]
finished. total time: 10.775s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.7
target reported max download size of 534773760 bytes
sending 'system' (240915 KB)...
OKAY [ 6.953s]
writing 'system'...
OKAY [ 3.633s]
finished. total time: 10.617s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.8
target reported max download size of 534773760 bytes
sending 'system' (262142 KB)...
OKAY [ 7.506s]
writing 'system'...
OKAY [ 3.650s]
finished. total time: 11.155s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.9
target reported max download size of 534773760 bytes
sending 'system' (233189 KB)...
OKAY [ 6.672s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 7.237s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.10
target reported max download size of 534773760 bytes
sending 'system' (65436 KB)...
OKAY [ 1.890s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 1.905s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem oem.img
target reported max download size of 534773760 bytes
sending 'oem' (145482 KB)...
OKAY [ 4.172s]
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 4.172s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.813s]
finished. total time: 0.813s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase DDR
erasing 'DDR'...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem fb_mode_clear
...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot

I'll need a bit more information.
What stock ROM did you try and flash? There's stock Nougat for the xt1806 that is different that stock Nougat for the other versions (XT1800,XT1801,XT1802,etc). It seems the Stock Oreo build can be flashed to all of them with minor issues.
Also, why are you trying to flash an OTA using TWRP? That won't work.

pizzaboy192 said:
I'll need a bit more information.
What stock ROM did you try and flash? There's stock Nougat for the xt1806 that is different that stock Nougat for the other versions (XT1800,XT1801,XT1802,etc). It seems the Stock Oreo build can be flashed to all of them with minor issues.
Also, why are you trying to flash an OTA using TWRP? That won't work.
Click to expand...
Click to collapse
I figured out after that it was OTA. The point I was trying to show was that it is detecting potter on the OEM partition. All other roms like PixelExperience, Xtended Rom and Arrow all just give error 7. E1001 : Failed to update system image.
I am trying to flash stock ROM SANDERS_OPS28.65-36_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.

briant97 said:
I figured out after that it was OTA. The point I was trying to show was that it is detecting potter on the OEM partition. All other roms like PixelExperience, Xtended Rom and Arrow all just give error 7. E1001 : Failed to update system image.
I am trying to flash stock ROM SANDERS_OPS28.65-36_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.
Click to expand...
Click to collapse
Not sure about this but check in your root (/) and/or /vendor directory for default.prop file (/vendor might have a build.prop instead). Check to see if there's anything odd there. I once had a default.prop with entries from a long-forgotten custom ROM that was causing issues. See if potter is in any of them.
LG G3 D851, LiquidRemix v9.1.3 Oreo ROM, microG (NoGapps), MultiROM, XDA Legacy

marcdw said:
Not sure about this but check in your root (/) and/or /vendor directory for default.prop file (/vendor might have a build.prop instead). Check to see if there's anything odd there. I once had a default.prop with entries from a long-forgotten custom ROM that was causing issues. See if potter is in any of them.
LG G3 D851, LiquidRemix v9.1.3 Oreo ROM, microG (NoGapps), MultiROM, XDA Legacy
Click to expand...
Click to collapse
default.prop
https://ghostbin.com/paste/bx9uj
build.prop
I could not find a build.prop file anywhere.

briant97 said:
default.prop
https://ghostbin.com/paste/bx9uj
build.prop
I could not find a build.prop file anywhere.
Click to expand...
Click to collapse
Every ROM has a build.prop, if I'm not mistaken, sitting in /system directory.
EDIT: Your default.prop looks good. Has sanders throughout and shows sdk25 (Nougat).
LG G3 D851, LiquidRemix v9.1.3 Oreo ROM, microG (NoGapps), MultiROM, XDA Legacy

marcdw said:
Every ROM has a build.prop, if I'm not mistaken, sitting in /system directory.
EDIT: Your default.prop looks good. Has sanders throughout and shows sdk25 (Nougat).
LG G3 D851, LiquidRemix v9.1.3 Oreo ROM, microG (NoGapps), MultiROM, XDA Legacy
Click to expand...
Click to collapse
I cannot find a build.prop file /system only contains a lost and found directory.
I also looked through every single directory. Can someone provide me with a flashable build.prop file maybe that would help resolve.
This is oem.prop file. May need a way to resolve this file is part of the issue as well. This for sure contains potter info.
#
# OEM_BUILD_PROPERTIES
#
ro.build.version.incremental=b8ea
ro.build.version.ci=16
ro.mot.build.guid=54d0fbcff7908bd
ro.product.name=potter
ro.mot.build.oem.product=potter
ro.mot.build.customerid=retail
Also here is my recovery.log for when i tried to flash Xtended Rom
https://hastebin.com/uvejafafug.sql

briant97 said:
I cannot find a build.prop file /system only contains a lost and found directory.
I also looked through every single directory. Can someone provide me with a flashable build.prop file maybe that would help resolve.
This is oem.prop file. May need a way to resolve this file is part of the issue as well. This for sure contains potter info.
#
# OEM_BUILD_PROPERTIES
#
ro.build.version.incremental=b8ea
ro.build.version.ci=16
ro.mot.build.guid=54d0fbcff7908bd
ro.product.name=potter
ro.mot.build.oem.product=potter
ro.mot.build.customerid=retail
Also here is my recovery.log for when i tried to flash Xtended Rom
https://hastebin.com/uvejafafug.sql
Click to expand...
Click to collapse
simple just flash the correct stock image as i can see you can successfully flash bootloader of sanders

chirayu19091997 said:
simple just flash the correct stock image as i can see you can successfully flash bootloader of sanders
Click to expand...
Click to collapse
Can you please let me know how to do this correctly. As you can see above I tried to flash it via the bootloader back to stock using the commands. If I can use TWRP, where can I find a flashable stock rom. As so far nothing is working.

briant97 said:
Can you please let me know how to do this correctly. As you can see above I tried to flash it via the bootloader back to stock using the commands. If I can use TWRP, where can I find a flashable stock rom. As so far nothing is working.
Click to expand...
Click to collapse
As far as a TWRP flashable for the XT1806, this is what I used way back when. Nougat. Still on it as a primary ROM. No chance of OTAs or anything but I'm not interested in stock Oreo anyway.
https://forum.xda-developers.com/showthread.php?t=3738502
[ROM][STOCK][TWRP ZIP] Sanders Stock 7.1.1 rooted NPS26.116-61
LG G3 D851, LiquidRemix v9.1.3 Oreo ROM, microG (NoGapps), MultiROM, XDA Legacy

Here is my attempts to flash this stock file. It still wont boot to an OS. Just reboots to twrp.

Total brain freeze. I remember the rebooting into TWRP thing and there were numerous posts about it. Fix was trivial but for the life of me I can't remember.
As far as getting into the OS, have you tried manually via the bootloader screen?
LG G3 D851, LiquidRemix v9.1.3 Oreo ROM, microG (NoGapps), MultiROM, XDA Legacy

marcdw said:
Total brain freeze. I remember the rebooting into TWRP thing and there were numerous posts about it. Fix was trivial but for the life of me I can't remember.
As far as getting into the OS, have you tried manually via the bootloader screen?
LG G3 D851, LiquidRemix v9.1.3 Oreo ROM, microG (NoGapps), MultiROM, XDA Legacy
Click to expand...
Click to collapse
How do you manually get into the OS via bootloader?

briant97 said:
How do you manually get into the OS via bootloader?
Click to expand...
Click to collapse
In TWRP, choose "reboot bootloader" and then in that, choose "start"
---------- Post added at 12:42 AM ---------- Previous post was at 12:41 AM ----------
briant97 said:
Here is my attempts to flash this stock file. It still wont boot to an OS. Just reboots to twrp.
Click to expand...
Click to collapse
That 2nd shot is normal errors for that specific restore (even says so in the OP). Looks good so far, just need to get it to boot to OS

pizzaboy192 said:
In TWRP, choose "reboot bootloader" and then in that, choose "start"
---------- Post added at 12:42 AM ---------- Previous post was at 12:41 AM ----------
That 2nd shot is normal errors for that specific restore (even says so in the OP). Looks good so far, just need to get it to boot to OS
Click to expand...
Click to collapse
It will not boot into the OS.

Anybody have any other ideas or thoughts. The oem partition is still the issue. Is there anyway to reflash this partition to the correct version?
I tried letting the phone boot over night as requested above but it never booted.

Hmm I made a bat file to fix this issue but can't find it
the concept is the bootloader accepts the firmware I told you can flash rom because you can flash Sanders bootloader and as seen in op
will see bat just hit me a private message me busy till 27 Nov 2018 and I can help on 27 or 28 IST

marcdw said:
Total brain freeze. I remember the rebooting into TWRP thing and there were numerous posts about it. Fix was trivial but for the life of me I can't remember.
As far as getting into the OS, have you tried manually via the bootloader screen?
LG G3 D851, LiquidRemix v9.1.3 Oreo ROM, microG (NoGapps), MultiROM, XDA Legacy
Click to expand...
Click to collapse
Sent you a private message.

I think you should try QPST flashing because this method will flash stock rom while device is off or even no battery,hope this can overwrite your prev wrong rom,

glewo45 said:
I think you should try QPST flashing because this method will flash stock rom while device is off or even no battery,hope this can overwrite your prev wrong rom,
Click to expand...
Click to collapse
https://androidmtk.com/use-qpst-flash-tool
I got to step 5 here and nothing shows under ports. I have tried when phone is at bootloader and also when phone is in twrp.

LOCKED BOOTLOADER No USB DEBUGGING STUCK IN FASTBOOT LOOP

Here is the thing, RM3 launched in india week ago, and it had lot of bugs, capacitive button YouTube, finger print find in page chrome, sub standard camera app and loads of other bugs, So i downloaded the Chinese ROM v2.30 and put it in root storage of phone, I did not unlock bootloader or Enable USB debugging, Installed the ROM, the installation went smooth, and the device did not boot, ERROR THE DEVICE IS CORRUPT IT CANNOT BE TRUSTED, AND WILL NOT BOOT, VISIT THE LINK etc. a common error on RM3 Devices, i tried everything on this post https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page2 and this https://www.getdroidtips.com/nubia-emergency-tool-unbrick/ and many other methods as well, the main difference here is the My device is not Bootloader unlocker is NOT rooted is not USB debugging enabled, Only positive is that i can install few things via FASTBOOT, except RECOVERY which is obviously locked. KINDLY HLEP

try to flash official recovery, extracted from the from that you installed.
after extraction, you would be able to see recovry.img thats the official recovery, wipe cache and data restart, probably it should work.
or download the global rom and install it via OTG.

No such options
Psychotic0666 said:
try to flash official recovery, extracted from the from that you installed.
after extraction, you would be able to see recovry.img thats the official recovery, wipe cache and data restart, probably it should work.
or download the global rom and install it via OTG.
Click to expand...
Click to collapse
Dude thanks, but i dont have WIPE CACHE RESTART OPTIONS, plus i cant boot into any recovery TWRP or CHINESE stock, Thankfully i found a way to unlock bootloader i guess via FASTBOOT, , still no response and unable to get into OTG OR DATA RESET OR CACHE RESET OPTIONS
Here is the list of options i got.
REBOOT SYSTEM NOW = BOOTLOOP AGAIN
REBOOT TO RECOVERY MODE = BOOTLOOP AGAIN
REBOOT TO EMEG RECOVERY MODE = Black Screen no response.
BOOT TO EDLOAD = Success as PC detects the phone as a Qualcomm Device, NUBIA Recovery soft (Very old) also detects phone
POwer off = Bootloop AGAIN
KIndly help

thel'vadam said:
Here is the thing, RM3 launched in india week ago, and it had lot of bugs, capacitive button YouTube, finger print find in page chrome, sub standard camera app and loads of other bugs, So i downloaded the Chinese ROM v2.30 and put it in root storage of phone, I did not unlock bootloader or Enable USB debugging, Installed the ROM, the installation went smooth, and the device did not boot, ERROR THE DEVICE IS CORRUPT IT CANNOT BE TRUSTED, AND WILL NOT BOOT, VISIT THE LINK etc. a common error on RM3 Devices, i tried everything on this post https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page2 and this https://www.getdroidtips.com/nubia-emergency-tool-unbrick/ and many other methods as well, the main difference here is the My device is not Bootloader unlocker is NOT rooted is not USB debugging enabled, Only positive is that i can install few things via FASTBOOT, except RECOVERY which is obviously locked. KINDLY HLEP
Click to expand...
Click to collapse
Hi, maybe you should flash the stock recovery and then try to update your system. You can't directly flash a global version to a Chinese version, they sign with different key I think.

Did you try to flash official recovery extracted from the zip.
Fastboot flash recovery recovery.img?
---------- Post added at 09:13 AM ---------- Previous post was at 09:10 AM ----------
I had the same problem, flashing official recovery helped me to get the recovery working again and then i flashed the global rom.. It worked for me.

JerryYin said:
Hi, maybe you should flash the twrp and use twrp to flash the stock udate package, the RM3 twrp can flash stock ota
package
Click to expand...
Click to collapse
Yep tried that shows success, even on locked bootloader, since my fastboot can be unlocked via CMD, i can push any recovery into the phone, the issue is, i cant boot into recovery using any key / menu combination.

Psychotic0666 said:
Did you try to flash official recovery extracted from the zip.
Fastboot flash recovery recovery.img?
---------- Post added at 09:13 AM ---------- Previous post was at 09:10 AM ----------
I had the same problem, flashing official recovery helped me to get the recovery working again and then i flashed the global rom.. It worked for me.
Click to expand...
Click to collapse
Yep tried that shows success, even on locked bootloader, since my fastboot can be unlocked via CMD, i can push any recovery into the phone, the issue is, i cant boot into recovery using any key / menu combination.

JerryYin said:
Hi, maybe you should flash the stock recovery and then try to update your system. You can't directly flash a global version to a Chinese version, they sign with different key I think.
Click to expand...
Click to collapse
thel'vadam said:
Yep tried that shows success, even on locked bootloader, since my fastboot can be unlocked via CMD, i can push any recovery into the phone, the issue is, i cant boot into recovery using any key / menu combination.
Click to expand...
Click to collapse
My suggestion is that flash the global version recovery first, and see if it can boot.

JerryYin said:
My suggestion is that flash the global version recovery first, and see if it can boot.
Click to expand...
Click to collapse
Tried that now, still unable to get into new recovery settings, im stuck with the same options as mentioned above,

thel'vadam said:
Tried that now, still unable to get into new recovery settings, im stuck with the same options as mentioned above,
Click to expand...
Click to collapse
How about use fastboot commands?
fastboot boot "your recovery file"
Or flash the recovery into boot section?
fastboot flash boot "your recovery file"

JerryYin said:
How about use fastboot commands?
fastboot boot "your recovery file"
Or flash the recovery into boot section?
fastboot flash boot "your recovery file"
Click to expand...
Click to collapse
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem nubia_unlock NUBIA_NX629J
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.004s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 2.130s]
booting...
FAILED (remote: unknown command)
finished. total time: 2.134s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot recovery.img
target reported max download size of 805306368 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.127s]
writing 'boot'...
OKAY [ 0.627s]
finished. total time: 2.757s
C:\Program Files (x86)\Minimal ADB and Fastboot>
NOTHING HAPPENED

thel'vadam said:
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem nubia_unlock NUBIA_NX629J
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.004s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 2.130s]
booting...
FAILED (remote: unknown command)
finished. total time: 2.134s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot recovery.img
target reported max download size of 805306368 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.127s]
writing 'boot'...
OKAY [ 0.627s]
finished. total time: 2.757s
C:\Program Files (x86)\Minimal ADB and Fastboot>
NOTHING HAPPENED
Click to expand...
Click to collapse
Okay`````just asked some friend work for nubia, you need to flash the vbmeta.img into vbmeta partition with same software version recovery file, you can try to flash both chinese and global version. I will come back on Monday to see if you solve this

JerryYin said:
Okay`````just asked some friend work for nubia, you need to flash the vbmeta.img into vbmeta partition with same software version recovery file, you can try to flash both chinese and global version. I will come back on Monday to see if you solve this
Click to expand...
Click to collapse
Can please elaborate this a little bit, also be informed that my RM3 is indian variant, it has separate indian variant ROM available from Nubia India 1.96 GB, so In my opinion GLOBAL AND CHINESE ROM s both wont work, my luck rests with the indian ROM. Ill still try whatever you suggest.

Meanwhile try this, extract the official room
Fastboot oem nub_unlock nubia_nx629j
flash parameter parameter.img
Reboot
Fastboot oem nub_unlock nubia_nx629j
Fastboot flash boot boot.img
Then recovery
Then splash
Then modem non-hlos.bin
At last system.Img
Fastboot reboot
Fat 32 pendrive with official zip, rename =UPDATE, flash via otg, try it out, it might work

Psychotic0666 said:
Meanwhile try this, extract the official room
Fastboot oem nub_unlock nubia_nx629j
flash parameter parameter.img
Reboot
Fastboot oem nub_unlock nubia_nx629j
Fastboot flash boot boot.img
Then recovery
Then splash
Then modem non-hlos.bin
At last system.Img
Fastboot reboot
Fat 32 pendrive with official zip, rename =UPDATE, flash via otg, try it out, it might work
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem nubia_unlock NUBIA_NX629J
...
(bootloader) START update nubia fastboot unlock flag!!!
(bootloader) set state to 1 ok!!!
OKAY [ 0.009s]
finished. total time: 0.010s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY [ 0.166s]
finished. total time: 0.167s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modem
erasing 'modem'...
OKAY [ 0.011s]
finished. total time: 0.012s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem nubia_unlock NUBIA_NX629J
...
(bootloader) START update nubia fastboot unlock flag!!!
(bootloader) set state to 1 ok!!!
OKAY [ 0.008s]
finished. total time: 0.009s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dsp dspso.bin
target reported max download size of 805306368 bytes
sending 'dsp' (65536 KB)...
OKAY [ 1.748s]
writing 'dsp'...
OKAY [ 0.343s]
finished. total time: 2.093s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash parameter parameter.img
target reported max download size of 805306368 bytes
sending 'parameter' (0 KB)...
OKAY [ 0.009s]
writing 'parameter'...
OKAY [ 0.004s]
finished. total time: 0.015s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 805306368 bytes
sending 'boot' (98304 KB)...
OKAY [ 3.432s]
writing 'boot'...
OKAY [ 0.406s]
finished. total time: 3.840s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (98304 KB)...
OKAY [ 2.139s]
writing 'recovery'...
OKAY [ 0.518s]
finished. total time: 2.658s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash splash splash.img
target reported max download size of 805306368 bytes
sending 'splash' (7419 KB)...
OKAY [ 0.207s]
writing 'splash'...
OKAY [ 0.056s]
finished. total time: 0.265s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
target reported max download size of 805306368 bytes
sending 'modem' (144180 KB)...
OKAY [ 3.778s]
writing 'modem'...
OKAY [ 1.045s]
finished. total time: 4.826s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magic
erasing 'system'...
OKAY [ 0.027s]
sending sparse 'system' 1/5 (778291 KB)...
OKAY [ 17.596s]
writing 'system' 1/5...
OKAY [ 0.004s]
sending sparse 'system' 2/5 (697207 KB)...
OKAY [ 22.095s]
writing 'system' 2/5...
OKAY [ 0.003s]
sending sparse 'system' 3/5 (752301 KB)...
OKAY [ 24.678s]
writing 'system' 3/5...
OKAY [ 0.003s]
sending sparse 'system' 4/5 (782303 KB)...
OKAY [ 30.918s]
writing 'system' 4/5...
OKAY [ 0.003s]
sending sparse 'system' 5/5 (723054 KB)...
OKAY [ 30.517s]
writing 'system' 5/5...
OKAY [ 0.002s]
finished. total time: 125.859s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>
STILL SAME

Did you flash the files from global rom?

same incident.
thel'vadam said:
Here is the thing, RM3 launched in india week ago, and it had lot of bugs, capacitive button YouTube, finger print find in page chrome, sub standard camera app and loads of other bugs, So i downloaded the Chinese ROM v2.30 and put it in root storage of phone, I did not unlock bootloader or Enable USB debugging, Installed the ROM, the installation went smooth, and the device did not boot, ERROR THE DEVICE IS CORRUPT IT CANNOT BE TRUSTED, AND WILL NOT BOOT, VISIT THE LINK etc. a common error on RM3 Devices, i tried everything on this post https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page2 and this https://www.getdroidtips.com/nubia-emergency-tool-unbrick/ and many other methods as well, the main difference here is the My device is not Bootloader unlocker is NOT rooted is not USB debugging enabled, Only positive is that i can install few things via FASTBOOT, except RECOVERY which is obviously locked. KINDLY HLEP
Click to expand...
Click to collapse
we have the same exact situtation. i tried every method here https://forum.xda-developers.com/red-magic-3/help/device-corrupt-trusted-boot-t3940057 and here https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page9 still to no avail. did you try this on your phone?

godric12 said:
we have the same exact situtation. i tried every method here https://forum.xda-developers.com/red-magic-3/help/device-corrupt-trusted-boot-t3940057 and here https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page9 still to no avail. did you try this on your phone?
Click to expand...
Click to collapse
i was once able to get a white screen with green highlighted squicircles, it did allow me to acess the boot from OTG option, i tried installing the indian ROM, it installed successfully, then after restart, same FASTBOOT LOOP WITH ERROR, i dont know how i got to that menu, i repeated the exact steps again, im still not able to get PAST BOOT LOOP.

Psychotic0666 said:
Did you flash the files from global rom?
Click to expand...
Click to collapse
YES TRIED ALL GLOBAL CHINESE indian, all variants. All recovery files all respective System.img files.
IM USING ORIGINAL IN BOX USB C cable if thats a thing,
Though i do get this ERROR (( Invalid sparse file format at header magic )) while pushing SYSTEM.img, it still suceeds, in 5/5 parts. after brief waiting.

Switch off the device and turn back on the Try going to recovery manually with vol and power button

[ROM][13][amogus] AOSP 13.0

AOSP 13
This is a moto-common project release under the codename amogus. This build supports the following devices: rav, rav_t, sofia, sofiap, sofiap_ao, sofiap_sprout, sofiar.​
Code:
/*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What's AOSP?
AOSP is Android as Google publish without any modifications.
Whats not working?
Speakerphone on sofia variants​
Instructions to install the ROM:
Reboot to bootloader:
Code:
adb reboot bootloader
The following will wipe your internal data:
Code:
fastboot -w
Code:
fastboot update package.zip
It will reboot your device to fastbootd, you might get the following warning:
Code:
FAILED (remote: 'Old partitions are not compatible with the new super layout; wipe needed')
, but you can continue with the following commands
Fastbootd:
Code:
fastboot flash product product.img
Code:
fastboot flash system system.img
Code:
fastboot flash vendor vendor.img
Code:
fastboot reboot
Downloads: Here
Source Code: Here
Sept 2: Fixed USB Mode Switching, Switched to new rebased kernel, Switched to EROFS
Sept 12: EGIS Fingerprint gestures fixed, Switch BtAudio to AIDL and September Patch level
Sept 28:
System Responsiveness has been tuned and improved
Introduce Multigenerational LRU Framework
Tune Dalvik Heap Sizes
Switched to QTI Thermal HAL
DT2W has been fixed for RAV (HIMAX) variants of amogus
Signature Spoofing support has been added to the ROM
Jan 26:
January Security Patch
Feb 27:
Feb security patch

Electimon said:
AOSP 13
This is a moto-common project release under the codename amogus. This build supports the following devices: rav, rav_t, sofia, sofiap, sofiap_ao, sofiap_sprout, sofiar.​
Click to expand...
Click to collapse
Great job! Thank you!
Would love to try but I can't downgrade :/

spiral777 said:
Great job! Thank you!
Would love to try but I can't downgrade :/
Click to expand...
Click to collapse
You can't downgrade? What do you mean by this?

Electimon said:
You can't downgrade? What do you mean by this?
Click to expand...
Click to collapse
I'm on a11, I don't have to downgrade to a10 to apply this update.zip?

spiral777 said:
I'm on a11, I don't have to downgrade to a10 to apply this update.zip?
Click to expand...
Click to collapse
No you don't, moto-common projects use custom vendors.

i got this to boot on my moto g fast thank you
edit: its still on android 11
just incase anyone might need it and something unexpected happens... https://support.lenovo.com/us/en/downloads/ds101291-rescue-and-smart-assistant-lmsa

spiral777 said:
i got this to boot on my moto g fast thank you
edit: its still on android 11
just incase anyone might need it and something unexpected happens... https://support.lenovo.com/us/en/downloads/ds101291-rescue-and-smart-assistant-lmsa
Click to expand...
Click to collapse
Microsoft Windows [Version 10.0.22000.856]
(c) Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
xxxxx fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
error: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
error: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
error: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.835s]
finished. total time: 0.835s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot update package.zip
W/ziparchive(11136): Unable to open 'package.zip': No such file or directory
error: failed to open zip file 'package.zip': I/O error
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash product product.img
target reported max download size of 799954944 bytes
sending 'product_b' (273816 KB)...
OKAY [ 9.958s]
writing 'product_b'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.048s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 799954944 bytes
Invalid sparse file format at header magic
sending sparse 'system_b' 1/2 (778517 KB)...
OKAY [ 28.791s]
writing 'system_b' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 28.885s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash vendor vendor.img
target reported max download size of 799954944 bytes
sending 'vendor_b' (471860 KB)...
OKAY [ 17.570s]
writing 'vendor_b'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.649s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.016s

spiral777 said:
Microsoft Windows [Version 10.0.22000.856]
(c) Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
xxxxx fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
error: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
error: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
error: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.835s]
finished. total time: 0.835s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot update package.zip
W/ziparchive(11136): Unable to open 'package.zip': No such file or directory
error: failed to open zip file 'package.zip': I/O error
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash product product.img
target reported max download size of 799954944 bytes
sending 'product_b' (273816 KB)...
OKAY [ 9.958s]
writing 'product_b'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.048s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 799954944 bytes
Invalid sparse file format at header magic
sending sparse 'system_b' 1/2 (778517 KB)...
OKAY [ 28.791s]
writing 'system_b' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 28.885s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash vendor vendor.img
target reported max download size of 799954944 bytes
sending 'vendor_b' (471860 KB)...
OKAY [ 17.570s]
writing 'vendor_b'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.649s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.016s
Click to expand...
Click to collapse
Uh you actually have to use the name of the zip in place of package.zip

Sept 2: Fixed USB Mode Switching, Switched to new rebased kernel, Switched to EROFS

So like are we able to go back to 11 if we don’t like 13?

TS_Brittany said:
So like are we able to go back to 11 if we don’t like 13?
Click to expand...
Click to collapse
Yes

Sept 12: EGIS Fingerprint gestures fixed, Switch BtAudio to AIDL and September Patch level

amogus

Truly an amogus moment

ive followed the install instructions as much as i can...factory reset...but this rom just bootloops on my moto g...anyone else get this to boot up?

spiral777 said:
ive followed the install instructions as much as i can...factory reset...but this rom just bootloops on my moto g...anyone else get this to boot up?
Click to expand...
Click to collapse
Can you show me the output of the commands?

Electimon said:
Can you show me the output of the commands?
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
xxxxx fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.835s]
finished. total time: 0.835s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot update aosp_amogus-img-eng.electimon-1.zip
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash product product.img
target reported max download size of 799954944 bytes
sending 'product_b' (273816 KB)...
OKAY [ 9.958s]
writing 'product_b'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.048s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 799954944 bytes
Invalid sparse file format at header magic
sending sparse 'system_b' 1/2 (778517 KB)...
OKAY [ 28.791s]
writing 'system_b' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 28.885s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash vendor vendor.img
target reported max download size of 799954944 bytes
sending 'vendor_b' (471860 KB)...
OKAY [ 17.570s]
writing 'vendor_b'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.649s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.016s
on rav moto g fast, thank you

spiral777 said:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
xxxxx fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.835s]
finished. total time: 0.835s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot update aosp_amogus-img-eng.electimon-1.zip
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash product product.img
target reported max download size of 799954944 bytes
sending 'product_b' (273816 KB)...
OKAY [ 9.958s]
writing 'product_b'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.048s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 799954944 bytes
Invalid sparse file format at header magic
sending sparse 'system_b' 1/2 (778517 KB)...
OKAY [ 28.791s]
writing 'system_b' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 28.885s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash vendor vendor.img
target reported max download size of 799954944 bytes
sending 'vendor_b' (471860 KB)...
OKAY [ 17.570s]
writing 'vendor_b'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.649s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.016s
on rav moto g fast, thank you
Click to expand...
Click to collapse
Please use official platform-tools and not ancient Minimal ADB and Fastboot from like 2015. Thanks.

touchscreen and fingerprint reader not working on my retus moto g fast.

Electimon said:
Please use official platform-tools and not ancient Minimal ADB and Fastboot from like 2015. Thanks.
Click to expand...
Click to collapse
updating platform tools worked ty
https://app.box.com/s/voj724lqdb7cc8z3i8xt6mx3wxc96e3p
but product, system, and vendor failed to flash from twrp