Related
Hello, i have an xt1033 moto g hard bricked, it boots up normal, but the system crash till the phone reboots, i enter in the fastboot mode and try to flash 4.4.4 again or 5.0.1, no errors at all, but when i reboot the phone it dont have changed nothing, continue with the crashes and the same apps showing.
And adb devices dosnt show nothing, just fastboot recognizes the device. Already tried to flash a custom recovery, it dosnt change, no errors when trying to flash, but when you enter recovery it is the standard one, adb sideload always show an error after reading the file i send.
Already tried erase all the files, but the phone reboot as the same, crashing and rebooting.
I already tried everything i found to revive the phone but whit no luck, tried the RSDLite too but it dosnt recognize my cellphone, i dont know what to do anymore :crying:
Any help are welcome, thanks and sorry for my bad english
Post logs of what happens when you try to flash the XT1033 Factory Firmware Image.
Firmware Images: http://forum.xda-developers.com/showpost.php?p=58534609&postcount=519
Flashing Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
lost101 said:
Post logs of what happens when you try to flash the XT1033 Factory Firmware Image.
Firmware Images: http://forum.xda-developers.com/showpost.php?p=58534609&postcount=519
Flashing Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Here are my full log, system dosnt have changed nothing after all this. Same problems. Already tried to update the bootloader bot it dosnt change too
Microsoft Windows [versão 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Todos os direitos reservados.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
0426104575 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase all
erasing 'all'...
(bootloader) erasing modemst1 ...
(bootloader) erasing modemst2 ...
(bootloader) erasing hob ...
(bootloader) erasing dhob ...
(bootloader) erasing fsg ...
(bootloader) erasing fsc ...
(bootloader) erasing clogo ...
(bootloader) erasing cache ...
(bootloader) erasing userdata ...
OKAY [ 4.758s]
finished. total time: 4.758s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing '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...
OKAY [ 0.390s]
finished. total time: 0.421s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash motoboot motoboot
.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.094s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.104s]
finished. total time: 1.213s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (295 KB)...
OKAY [ 0.078s]
writing 'logo'...
OKAY [ 0.047s]
finished. total time: 0.125s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.406s]
writing 'boot'...
OKAY [ 0.661s]
finished. total time: 1.083s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.421s]
writing 'recovery'...
OKAY [ 0.655s]
finished. total time: 1.076s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257887 KB)...
OKAY [ 8.742s]
writing 'system'...
OKAY [ 7.894s]
finished. total time: 16.636s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (256762 KB)...
OKAY [ 8.940s]
writing 'system'...
OKAY [ 8.225s]
finished. total time: 17.181s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (260106 KB)...
OKAY [ 9.013s]
writing 'system'...
OKAY [ 8.315s]
finished. total time: 17.327s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system' (166048 KB)...
OKAY [ 5.863s]
writing 'system'...
OKAY [ 6.367s]
finished. total time: 12.230s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bi
n
target reported max download size of 536870912 bytes
sending 'modem' (49356 KB)...
OKAY [ 1.794s]
writing 'modem'...
OKAY [ 0.796s]
finished. total time: 2.605s
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.062s]
finished. total time: 0.062s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (102 KB)...
OKAY [ 0.047s]
writing 'fsg'...
OKAY [ 3.188s]
finished. total time: 3.251s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.000s
Never
EVER
use
fastboot erase all
You have erased partitions unique to your phone, you have lost IMEI - you will never be able to make calls over a network again. You should not have used that command. It might be possible to get a ROM booting again, but don't expect anything more than a tablet from now on. Sorry.
lost101 said:
Never
EVER
use
fastboot erase all
You have erased partitions unique to your phone, you have lost IMEI - you will never be able to make calls over a network again. You should not have used that command. It might be possible to get a ROM booting again, but don't expect anything more than a tablet from now on. Sorry.
Click to expand...
Click to collapse
i tried this command to see if something change , but the cellphone is still the same, crashing till reboots, dont know what to do to repair its os it still have the same apps installed, runing the same way, nothing works .-.
d3vileyes said:
i tried this command to see if something change , but the cellphone is still the same, crashing till reboots, dont know what to do to repair its os it still have the same apps installed, runing the same way, nothing works .-.
Click to expand...
Click to collapse
Try using mfastboot.
https://www.androidfilehost.com/?fid=23578570567719065
same thing, i tried to lock my bootloader too but shows an error at the end, the system dont changed again.
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 1.576s]
finished. total time: 1.576s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash partition gp
t.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing '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...
OKAY [ 0.359s]
finished. total time: 0.374s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash motoboot mot
oboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.094s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.112s]
finished. total time: 1.205s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash logo logo.bi
n
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.047s]
writing 'logo'...
OKAY [ 0.047s]
finished. total time: 0.109s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash boot boot.im
g
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.406s]
writing 'boot'...
OKAY [ 0.655s]
finished. total time: 1.061s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash recovery rec
overy.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.406s]
writing 'recovery'...
OKAY [ 0.655s]
finished. total time: 1.061s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash system syste
m.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257887 KB)...
OKAY [ 9.058s]
writing 'system'...
OKAY [ 8.189s]
finished. total time: 17.262s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash system syste
m.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256762 KB)...
OKAY [ 8.958s]
writing 'system'...
OKAY [ 8.239s]
finished. total time: 17.197s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash system syste
m.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260106 KB)...
OKAY [ 9.159s]
writing 'system'...
OKAY [ 8.317s]
finished. total time: 17.476s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash system syste
m.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (166048 KB)...
OKAY [ 5.848s]
writing 'system'...
OKAY [ 6.365s]
finished. total time: 12.229s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash modem NON-HL
OS.bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 1.794s]
writing 'modem'...
OKAY [ 0.842s]
finished. total time: 2.652s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.094s]
writing 'fsg'...
OKAY [ 3.167s]
finished. total time: 3.276s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe erase userdata
erasing 'userdata'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot.exe oem lock
...
FAILED (status read failed (Too many links))
finished. total time: 17.434s
Download TWRP: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Use the command: mfastboot flash recovery twrp-2.8.6.0-falcon.img
Enter Recovery and confirm TWRP works.
Report back.
tried again with no luck, recovery dosnt change too, i tried the f2f and the ext4.
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash recovery recover
y.img
target max-sparse-size: 256MB
sending 'recovery' (10184 KB)...
OKAY [ 0.382s]
writing 'recovery'...
OKAY [ 0.184s]
finished. total time: 0.569s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash recovery openrec
overy-twrp-2.8.4.0-falcon_STOCK.img
target max-sparse-size: 256MB
sending 'recovery' (8168 KB)...
OKAY [ 0.280s]
writing 'recovery'...
OKAY [ 0.156s]
finished. total time: 0.440s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash recovery openrec
overy-twrp-2.8.4.0-falcon_GPE.img
target max-sparse-size: 256MB
sending 'recovery' (8168 KB)...
OKAY [ 0.286s]
writing 'recovery'...
OKAY [ 0.160s]
finished. total time: 0.451s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Try: mfastboot boot openrecovery-twrp-2.8.4.0-falcon_STOCK.img
lost101 said:
Try: mfastboot boot openrecovery-twrp-2.8.4.0-falcon_STOCK.img
Click to expand...
Click to collapse
It worked, it booted on twrp, but if i try to restore or something else it give me "unable to mount /cache" error
Try to format ( wipe and format are different things) cache partition in recovery or using fastboot command
fastboot erase cache
sjandroiddeveloper said:
Try to format ( wipe and format are different things) cache partition in recovery or using fastboot command
fastboot erase cache
Click to expand...
Click to collapse
Everything i try to do it say "unable to mount /cache", i think the /cache partition is bricked, i cant repair or format it, and every time i try to do something it shows me an error :/
d3vileyes said:
Everything i try to do it say "unable to mount /cache", i think the /cache partition is bricked, i cant repair or format it, and every time i try to do something it shows me an error :/
Click to expand...
Click to collapse
I had a problem when my data partition was no mounting
Whenever I flashed a ROM or wiped data or factory reset it gave error cannot mount data
I repaired it by formating data partition using Philz recovery
I am again saying wipe and format are different concepts
Do one thing flash Philz recovery because in twrp you can only format data and not system and cache
So flash Philz touch
Go to wipe and format>Custom format and format cache partition
Then it should work
sjandroiddeveloper said:
I had a problem when my data partition was no mounting
Whenever I flashed a ROM or wiped data or factory reset it gave error cannot mount data
I repaired it by formating data partition using Philz recovery
I am again saying wipe and format are different concepts
Do one thing flash Philz recovery because in twrp you can only format data and not system and cache
So flash Philz touch
Go to wipe and format>Custom format and format cache partition
Then it should work
Click to expand...
Click to collapse
When i try to boot philz_touch_6.58.7-falcon it boots the Motorola logo and crash to a black screen, after this it boots the system
~~~~~~~edit~~~~~~
tried another version of philz touch and it worked, i'm gonna try to format now
d3vileyes said:
When i try to boot philz_touch_6.58.7-falcon it boots the Motorola logo and crash to a black screen, after this it boots the system
Click to expand...
Click to collapse
Did you try the fastboot command
fastboot erase cache
For formatting cache partition
Do it and see that in twrp (since you cannot flash Philz ) that the error is still there or not
sjandroiddeveloper said:
Did you try the fastboot command
fastboot erase cache
For formatting cache partition
Do it and see that in twrp (since you cannot flash Philz ) that the error is still there or not
Click to expand...
Click to collapse
I used the command fastboot erase cache, same error on twrp
C:\Users\Rabugentos\Downloads\Moto G Tools\MotoX>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Rabugentos\Downloads\Moto G Tools\MotoX>mfastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.000s
~~~~~~~~edit~~~~~~
now i can boot philz recovery, i formated /cache and /sdcard, in the screen shows OK but nothing changes
@d3vileyes - I would use adb push a ROM.zip and try flashing that in TWRP. Recovery mode adb is possible, but doesn't always work for Windows users. On a Linux PC / Laptop - it will always work.
ADB command: adb push rom.zip /sdcard/
XT1033 Lollipop ROM zips: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
lost101 said:
@d3vileyes - I would use adb push a ROM.zip and try flashing that in TWRP. Recovery mode adb is possible, but doesn't always work for Windows users. On a Linux PC / Laptop - it will always work.
ADB command: adb push rom.zip /sdcard/
Click to expand...
Click to collapse
when i try to adb push i get this error
Failed to copy 'xt1033_retail_Brazil.zip' to '/sdcard//xt1033_retail_Brazil.zip': Read-only file system
~~~~~~edit~~~~~
Fixed this error with adb shell
mount -o remount rw /sdcard
but when i try to flash it gaves me the same error "unable to mount /cache"
don't know whats going on with the /cache folder
d3vileyes said:
I used the command fastboot erase cache, same error on twrp
C:\Users\Rabugentos\Downloads\Moto G Tools\MotoX>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Rabugentos\Downloads\Moto G Tools\MotoX>mfastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.000s
~~~~~~~~edit~~~~~~
now i can boot philz recovery, i formated /cache and /sdcard, in the screen shows OK but nothing changes
Click to expand...
Click to collapse
First of all when you formatted cache partition in Philz recovery, did it come in the logs below that formatting cache successful or something like that or it again appeared that cannot Mount cache
If it appeared that cache formatting successful then try and wipe cache this time and it should come wipe cache complete
If that happens you are good to go
Just flash a rom again and this time should be successful
sent from falcon
PRESS THANKS IF HELPED?????
I Have try to unlock my phone bootloader...
But i decide to Relock it...
(Firmware XT1039_RETAIL-BR-EU-SS_4.4.4_KXB21.14-L1.56-1_cid12_CFC_1FF)
I got a comand like this:
"fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock"
(Using The Minimal ADB and Fastboot)
(My Device firmware have 4 System IMG Spacechunks.)
Log:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash motoboot motoboot
.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.164s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.297s]
finished. total time: 1.461s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (1060 KB)...
OKAY [ 0.141s]
writing 'logo'...
OKAY [ 0.141s]
finished. total time: 0.281s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.422s]
writing 'boot'...
OKAY [ 1.022s]
finished. total time: 1.443s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.422s]
writing 'recovery'...
OKAY [ 1.022s]
finished. total time: 1.444s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (248267 KB)...
OKAY [ 7.931s]
writing 'system'...
OKAY [ 17.454s]
finished. total time: 25.384s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (248994 KB)...
OKAY [ 7.935s]
writing 'system'...
OKAY [ 15.417s]
finished. total time: 23.353s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (257391 KB)...
OKAY [ 8.205s]
writing 'system'...
OKAY [ 16.311s]
finished. total time: 24.518s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system' (20588 KB)...
OKAY [ 0.742s]
writing 'system'...
OKAY [ 13.748s]
finished. total time: 14.492s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bi
n
target reported max download size of 536870912 bytes
sending 'modem' (59132 KB)...
OKAY [ 1.949s]
writing 'modem'...
OKAY [ 2.892s]
finished. total time: 4.842s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.071s]
finished. total time: 0.073s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.067s]
finished. total time: 0.068s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (710 KB)...
OKAY [ 0.123s]
writing 'fsg'...
OKAY [ 5.347s]
finished. total time: 5.471s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.113s]
finished. total time: 0.114s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.288s]
finished. total time: 0.289s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
...
FAILED (status read failed (Too many links))
finished. total time: 17.622s
But OEM Lock says "Too many Links"
(The device Says "Locked", and restarted, and boot propely)
I Checked in Fastboot
Says "Device is LOCKED. Status Code: 2
Is really Locked?
Didn't see something abnormal here. The "too many links" errors are normal, I've relocked a 2 gen moto g with this tool and everything worked fine.
Hello!
Because I was not sure what is right procedure first I've downgraded moto G from CM12.1 to stock 4.4.4 rom using mfastboot, and then installed 5.0.2. stock rom via mfastboot, and now I'm stuck at warning bootloader unlocked. So if some one can help what to do to get rid of that logo and install stock rom on my moto G.
Thnx.
njofra13 said:
Hello!
Because I was not sure what is right procedure first I've downgraded moto G from CM12.1 to stock 4.4.4 rom using mfastboot, and then installed 5.0.2. stock rom via mfastboot, and now I'm stuck at warning bootloader unlocked. So if some one can help what to do to get rid of that logo and install stock rom on my moto G.
Thnx.
Click to expand...
Click to collapse
Did you flash all the system.img_sparsechunk? From 0 to 3
Yes I did but having no more idea what to do.
njofra13 said:
Yes I did but having no more idea what to do.
Click to expand...
Click to collapse
Check the names, because sometimes they are named system.img_sparsechunk.0, for example, and sometimes system.img_sparsechunk0. You must check that the name that you flash is the exact name of the four files.
The names are ok.
Here are commands for fastboot:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Maybe in here I'm doing something wrong. Also I've managed to install twrp recovery , can this help me?
njofra13 said:
The names are ok.
Here are commands for fastboot:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Maybe in here I'm doing something wrong. Also I've managed to install twrp recovery , can this help me?
Click to expand...
Click to collapse
You should flash system.img_sparsechunk.3 too
Here is paste of my screen after running all commands:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.030s]
writing '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...
OKAY [ 0.338s]
finished. total time: 0.373s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.107s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.125s]
finished. total time: 1.239s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (295 KB)...
OKAY [ 0.073s]
writing 'logo'...
OKAY [ 0.115s]
finished. total time: 0.195s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.392s]
writing 'boot'...
OKAY [ 0.945s]
finished. total time: 1.342s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.408s]
writing 'recovery'...
OKAY [ 0.963s]
finished. total time: 1.378s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.213s]
sending 'system' (257879 KB)...
OKAY [ 8.120s]
writing 'system'...
OKAY [ 16.004s]
finished. total time: 24.358s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.324s]
sending 'system' (256770 KB)...
OKAY [ 8.080s]
writing 'system'...
OKAY [ 16.418s]
finished. total time: 24.828s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.300s]
sending 'system' (260106 KB)...
OKAY [ 8.187s]
writing 'system'...
OKAY [ 16.698s]
finished. total time: 25.191s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.334s]
sending 'system' (159536 KB)...
OKAY [ 5.047s]
writing 'system'...
OKAY [ 11.366s]
finished. total time: 16.755s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (49356 KB)...
OKAY [ 1.595s]
writing 'modem'...
OKAY [ 2.412s]
finished. total time: 4.014s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.070s]
finished. total time: 0.073s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.085s]
finished. total time: 0.089s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (102 KB)...
OKAY [ 0.093s]
writing 'fsg'...
OKAY [ 5.312s]
finished. total time: 5.410s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.132s]
finished. total time: 0.132s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.290s]
finished. total time: 0.293s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.002s
Still stuck on warning bootloader unlocked ....
njofra13 said:
Here is paste of my screen after running all commands:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.030s]
writing '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...
OKAY [ 0.338s]
finished. total time: 0.373s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.107s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.125s]
finished. total time: 1.239s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (295 KB)...
OKAY [ 0.073s]
writing 'logo'...
OKAY [ 0.115s]
finished. total time: 0.195s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.392s]
writing 'boot'...
OKAY [ 0.945s]
finished. total time: 1.342s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.408s]
writing 'recovery'...
OKAY [ 0.963s]
finished. total time: 1.378s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.213s]
sending 'system' (257879 KB)...
OKAY [ 8.120s]
writing 'system'...
OKAY [ 16.004s]
finished. total time: 24.358s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.324s]
sending 'system' (256770 KB)...
OKAY [ 8.080s]
writing 'system'...
OKAY [ 16.418s]
finished. total time: 24.828s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.300s]
sending 'system' (260106 KB)...
OKAY [ 8.187s]
writing 'system'...
OKAY [ 16.698s]
finished. total time: 25.191s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.334s]
sending 'system' (159536 KB)...
OKAY [ 5.047s]
writing 'system'...
OKAY [ 11.366s]
finished. total time: 16.755s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (49356 KB)...
OKAY [ 1.595s]
writing 'modem'...
OKAY [ 2.412s]
finished. total time: 4.014s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.070s]
finished. total time: 0.073s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.085s]
finished. total time: 0.089s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (102 KB)...
OKAY [ 0.093s]
writing 'fsg'...
OKAY [ 5.312s]
finished. total time: 5.410s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.132s]
finished. total time: 0.132s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.290s]
finished. total time: 0.293s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.002s
Still stuck on warning bootloader unlocked ....
Click to expand...
Click to collapse
Try to download mfastboot and use it instead of fastboot
That was the problem .... Thank you for all help ....
My phone is a MHA-L29 C432 B368. Is there a way to flash TWRP into the eRecovery partition (recovery2)?
When I try it, I either get "partition length get error" or "Command not allowed"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash erecovery_ramdisk TWRP_3.2.1-0_OREO_V3.img
target reported max download size of 471859200 bytes
sending 'erecovery_ramdisk' (16506 KB)...
OKAY [ 0.362s]
writing 'erecovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.375s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery2_ramdisk TWRP_3.2.1-0_OREO_V3.img
target reported max download size of 471859200 bytes
sending 'recovery2_ramdisk' (16506 KB)...
OKAY [ 0.361s]
writing 'recovery2_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 0.374s
Hi all,
I need help with my phone being stuck in fastboot...
Today i tried to flash Lineage OS using this guide. I did this from scratch with a stock phone, not rooted or unlocked or anything.
Everything went fine until Step 4 under ROM Installation. My phone refused to start into TWRP. It didn't even start the lineage rom, it always just warned me about my phone being a risk because it is unlocked and then proceeded to start the stock Rom. So i tried the whole thing over and over again a couple of times, always with the same result. Then i read someone writing about how he first had to use wipe > format data before flashing the Rom in TWRP in the Guide Thread (Page 3). So i tried that too. But i must have done something wrong because it now led to my phone restarting into a fastboot mode, which didn't look like the fastboot screen it booted into before e.g. different font style, black background without the little android thingy on the top, and it now says "oem_locked" again.
When i try to boot the system it says:
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Boot up failed
I tried to unlock the phone again using "fastboot oem unlock MYKEY" on my computer it says:
(bootloader) feature disabled
OKAY [ 0.003s]
finished. total time: 0.004s
So i tried to flash back to the stock image as described here.
But i get a "remote failure" error after every command.
Here is the output from Powershell:
PS D:\Minimal ADB and Fastboot> ./fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.002s
PS D:\Minimal ADB and Fastboot> ./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) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.055s
PS D:\Minimal ADB and Fastboot> ./fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (7419 KB)...
OKAY [ 0.249s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Invalid partition name aboot
(bootloader) Invalid partition name rpm
(bootloader) Invalid partition name tz
(bootloader) Invalid partition name devcfg
(bootloader) Invalid partition name cmnlib
(bootloader) Invalid partition name cmnlib64
(bootloader) Invalid partition name keymaster
(bootloader) Invalid partition name prov
(bootloader) Invalid partition name sbl1
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.437s
PS D:\Minimal ADB and Fastboot> ./fastboot flash modem_a NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem_a' (65396 KB)...
OKAY [ 2.147s]
writing 'modem_a'...
(bootloader) Invalid partition name modem_a
FAILED (remote failure)
finished. total time: 2.158s
PS D:\Minimal ADB and Fastboot> ./fastboot flash fsg_a fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg_a' (11684 KB)...
OKAY [ 0.379s]
writing 'fsg_a'...
(bootloader) Invalid partition name fsg_a
FAILED (remote failure)
finished. total time: 0.392s
PS D:\Minimal ADB and Fastboot> ./fastboot erase modemst1
erasing 'modemst1'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.010s
PS D:\Minimal ADB and Fastboot> ./fastboot erase modemst2
erasing 'modemst2'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.027s
PS D:\Minimal ADB and Fastboot> ./fastboot flash dsp_a adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp_a' (16384 KB)...
OKAY [ 0.531s]
writing 'dsp_a'...
(bootloader) Invalid partition name dsp_a
FAILED (remote failure)
finished. total time: 0.538s
PS D:\Minimal ADB and Fastboot> ./fastboot flash logo_a logo.bin
target reported max download size of 536870912 bytes
sending 'logo_a' (1285 KB)...
OKAY [ 0.046s]
writing 'logo_a'...
(bootloader) Invalid partition name logo_a
FAILED (remote failure)
finished. total time: 0.057s
PS D:\Minimal ADB and Fastboot> ./fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (32768 KB)...
OKAY [ 1.085s]
writing 'boot_a'...
(bootloader) Invalid partition name boot_a
FAILED (remote failure)
finished. total time: 1.093s
PS D:\Minimal ADB and Fastboot> ./fastboot flash dtbo_a dtbo.img
target reported max download size of 536870912 bytes
sending 'dtbo_a' (1760 KB)...
OKAY [ 0.058s]
writing 'dtbo_a'...
(bootloader) Invalid partition name dtbo_a
FAILED (remote failure)
finished. total time: 0.066s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system_a' (258873 KB)...
OKAY [ 8.397s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.409s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system_a' (249260 KB)...
OKAY [ 8.139s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.153s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system_a' (262081 KB)...
OKAY [ 8.677s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.693s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system_a' (262141 KB)...
OKAY [ 8.533s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.540s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system_a' (257008 KB)...
OKAY [ 8.366s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.374s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system_a' (242308 KB)...
OKAY [ 7.906s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 7.912s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.6
target reported max download size of 536870912 bytes
sending 'system_a' (262060 KB)...
OKAY [ 8.585s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.596s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.7
target reported max download size of 536870912 bytes
sending 'system_a' (255940 KB)...
OKAY [ 8.420s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.436s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.8
target reported max download size of 536870912 bytes
sending 'system_a' (261918 KB)...
OKAY [ 8.584s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.594s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.9
target reported max download size of 536870912 bytes
sending 'system_a' (83808 KB)...
OKAY [ 2.728s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 2.738s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_b system_b.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system_b' (262140 KB)...
OKAY [ 8.349s]
writing 'system_b'...
(bootloader) Invalid partition name system_b
FAILED (remote failure)
finished. total time: 8.357s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_b system_b.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system_b' (262024 KB)...
OKAY [ 8.368s]
writing 'system_b'...
(bootloader) Invalid partition name system_b
FAILED (remote failure)
finished. total time: 8.376s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_b system_b.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system_b' (43968 KB)...
OKAY [ 1.414s]
writing 'system_b'...
(bootloader) Invalid partition name system_b
FAILED (remote failure)
finished. total time: 1.423s
PS D:\Minimal ADB and Fastboot> ./fastboot flash vendor_a vendor.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'vendor_a' (259120 KB)...
OKAY [ 8.524s]
writing 'vendor_a'...
(bootloader) Invalid partition name vendor_a
FAILED (remote failure)
finished. total time: 8.531s
PS D:\Minimal ADB and Fastboot> ./fastboot flash vendor_a vendor.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'vendor_a' (147628 KB)...
OKAY [ 4.843s]
writing 'vendor_a'...
(bootloader) Invalid partition name vendor_a
FAILED (remote failure)
finished. total time: 4.850s
PS D:\Minimal ADB and Fastboot> ./fastboot flash oem_a oem.img
target reported max download size of 536870912 bytes
sending 'oem_a' (103040 KB)...
OKAY [ 3.370s]
writing 'oem_a'...
(bootloader) Invalid partition name oem_a
FAILED (remote failure)
finished. total time: 3.377s
PS D:\Minimal ADB and Fastboot> ./fastboot flash oem_b oem_other.img
target reported max download size of 536870912 bytes
sending 'oem_b' (185456 KB)...
OKAY [ 6.032s]
writing 'oem_b'...
(bootloader) Invalid partition name oem_b
FAILED (remote failure)
finished. total time: 6.044s
PS D:\Minimal ADB and Fastboot> ./fastboot erase userdata
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.016s
PS D:\Minimal ADB and Fastboot> ./fastboot erase DDR
erasing 'DDR'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.005s
PS D:\Minimal ADB and Fastboot> ./fastboot oem fb_mode_clear
...
OKAY [ 0.001s]
finished. total time: 0.005s
PS D:\Minimal ADB and Fastboot> ./fastboot reboot
rebooting...
finished. total time: 0.001s
And now i'm pretty lost and don't really know how to proceed. It would be great if somebody hat some advice
This situation takes place when you switch to the empty Slot B without copying contents of Slot A there. I have exactly the same problem and my phone has been put to the box, until a proper solution can be found, if any. I have downloaded blankflash files recently, but the command line shows only "waiting for device", in such a way I havent managed to use it propely.
kry52 said:
This situation takes place when you switch to the empty Slot B without copying contents of Slot A there. I have exactly the same problem and my phone has been put to the box, until a proper solution can be found, if any. I have downloaded blankflash files recently, but the command line shows only "waiting for device", in such a way I havent managed to use it propely.
Click to expand...
Click to collapse
Thats unfortunat
I tried the blankflash too, with the same outcome. Then i guess i'll do the same.... put in the box and wait for a solution, if there will ever be any :fingers-crossed:
Anyway... thank you for the reply
Tried switching slots?
To check active slot
Code:
fastboot getvar current-slot
To change to slot a
Code:
fastboot --set-active=a
To change to slot b
Code:
fastboot --set-active=b
To toggle from active to inactive Slot
Code:
fastboot set_active other
Sent from my mata using XDA Labs
---------- Post added at 02:39 AM ---------- Previous post was at 02:38 AM ----------
kry52 said:
... I have downloaded blankflash files recently, but the command line shows only "waiting for device", in such a way I havent managed to use it propely.
Click to expand...
Click to collapse
Was phone in emergency download mode?
Sent from my mata using XDA Labs
In this mode phone will not be in EDL, but you can place it into by issuing `fastboot oem blankflash`. See `fastboot oem help` Afterwards you should be able to restore phone using blank flash file, see this HERE
@sd_shadow Switching slots does nothing. I always get the "remote failure" error massage. And when i'm trying to switch to slot b it tells me there wouldn't be a slot b.
Here the output of the suggested commands:
D:\Minimal ADB and Fastboot>fastboot getvar current-slot
current-slot:
finished. total time: 0.000s
D:\Minimal ADB and Fastboot>fastboot --set-active=a
Setting current slot to 'a'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: -0.000s
D:\Minimal ADB and Fastboot>fastboot --set-active=b
Slot b does not exist. supported slots are:
a
D:\Minimal ADB and Fastboot>fastboot set_active other
Setting current slot to 'a'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: -0.000s
D:\Minimal ADB and Fastboot>
@Geoffrey I was able to put it into EDL. It shows up in my Device Manager as Qualcomm HS-USB QDLoader 9008 but when im trying to run the blankflash like in the guide i get this result:
D:\Downloads\Moto\blankflash_ocean_PDOS29.114-134-2 (1)>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 4.007] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.007] Check qboot_log.txt for more details
[ 4.009] Total time: 4.012s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
D:\Downloads\Moto\blankflash_ocean_PDOS29.114-134-2 (1)>pause
Drücken Sie eine beliebige Taste . . .
Here is the Log File:
**** Log buffer [000001] 2019-11-02_19:45:56 ****
[ 0.000] Opening device: \\.\COM4
[ 0.002] Detecting device
[ 4.010] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.010] Check qboot_log.txt for more details
[ 4.011] Total time: 4.014s
[ 4.011]
[ 4.011] qboot version 3.40
[ 4.011]
[ 4.011] DEVICE {
[ 4.011] name = "\\.\COM4",
[ 4.011] flags = "0x64",
[ 4.011] addr = "0x61FE4C",
[ 4.011] api.bnr = "0xFF2F20",
[ 4.011] }
[ 4.011]
[ 4.011]
[ 4.011] Backup & Restore {
[ 4.011] num_entries = 0,
[ 4.011] restoring = "false",
[ 4.011] backup_error = "not started",
[ 4.011] restore_error = "not started",
[ 4.011] }
[ 4.011]
Any suggestions?
bondu546 said:
@sd_shadow Switching slots does nothing. I always get the "remote failure" error massage. And when i'm trying to switch to slot b it tells me there wouldn't be a slot b.
Here the output of the suggested commands:
D:\Minimal ADB and Fastboot>fastboot getvar current-slot
current-slot:
finished. total time: 0.000s
D:\Minimal ADB and Fastboot>fastboot --set-active=a
Setting current slot to 'a'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: -0.000s
D:\Minimal ADB and Fastboot>fastboot --set-active=b
Slot b does not exist. supported slots are:
a
D:\Minimal ADB and Fastboot>fastboot set_active other
Setting current slot to 'a'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: -0.000s
D:\Minimal ADB and Fastboot>
@Geoffrey I was able to put it into EDL. It shows up in my Device Manager as Qualcomm HS-USB QDLoader 9008 but when im trying to run the blankflash like in the guide i get this result:
D:\Downloads\Moto\blankflash_ocean_PDOS29.114-134-2 (1)>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 4.007] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.007] Check qboot_log.txt for more details
[ 4.009] Total time: 4.012s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
D:\Downloads\Moto\blankflash_ocean_PDOS29.114-134-2 (1)>pause
Drücken Sie eine beliebige Taste . . .
Here is the Log File:
**** Log buffer [000001] 2019-11-02_19:45:56 ****
[ 0.000] Opening device: \\.\COM4
[ 0.002] Detecting device
[ 4.010] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.010] Check qboot_log.txt for more details
[ 4.011] Total time: 4.014s
[ 4.011]
[ 4.011] qboot version 3.40
[ 4.011]
[ 4.011] DEVICE {
[ 4.011] name = "\\.\COM4",
[ 4.011] flags = "0x64",
[ 4.011] addr = "0x61FE4C",
[ 4.011] api.bnr = "0xFF2F20",
[ 4.011] }
[ 4.011]
[ 4.011]
[ 4.011] Backup & Restore {
[ 4.011] num_entries = 0,
[ 4.011] restoring = "false",
[ 4.011] backup_error = "not started",
[ 4.011] restore_error = "not started",
[ 4.011] }
[ 4.011]
Any suggestions?
Click to expand...
Click to collapse
I have the same issue x.x is really hard to unbrick this phone at this point :C my phone boot into a diferent type of bootloader with the START in green color and no android logo, and my pc doesn't recognize de device...
jodytejada said:
I have the same issue x.x is really hard to unbrick this phone at this point :C my phone boot into a diferent type of bootloader with the START in green color and no android logo, and my pc doesn't recognize de device...
Click to expand...
Click to collapse
My PC shows "Android ADB Interface" when the phone is loaded in this emergency fastboot mode, but anyway - ADB commands don't work, fastboot commands bring failures because of the partitions issue and more than that - this emergency fastboot loader is oem_locked and can't be unlocked in a standard way
Will this 134-2 file work on a phone updated to 134-4 ??
Geofferey said:
In this mode phone will not be in EDL, but you can place it into by issuing `fastboot oem blankflash`. See `fastboot oem help` Afterwards you should be able to restore phone using blank flash file, see this HERE
Click to expand...
Click to collapse
This is a 134-2 blankflash file - will it work on 134-4 ??
Despite everyone else being able to flash to a different variant of the XT1955 firmware - apparently the Verizon XT1955-6 is OEM locked at the boot.img stage.
Currently there is no PDOS29.114-134-4 firmware to download at https://mirrors.lolinet.com/firmware.../official/VZW/ to repair it by a re-install of the firmware with - and one cannot install an earlier version . . . unless you know of a way . . .
Everything will re-flash but boot.img and dtbo.img
The Lenovo MOTO Smart Assistant comes back and says it is not supported . . . after recognizing it
Is there a way to re-set the OEM issues of the phone to take earlier versions of the OS - or other variants that you know of ??
Even factory reset is not available - I will look for a fastboot command that can do it - because that is all I can do - it boots right to fastboot now only
estofjlw said:
This is a 134-2 blankflash file - will it work on 134-4 ??
...
Click to expand...
Click to collapse
It should work for any XT1955-5
Sent from my ocean using XDA Labs
sd_shadow said:
It should work for any XT1955-5 /QUOTE]
OK I can try it. I have a xt1955-6 - Verizon
Everything flashes with a xt1955-5 RETUS firmware except the boot.img and dtbo.img
If blank flash is an OEM signed file - maybe it will push over the existing boot.img
I will see if in the middle of the flash - the oem get_unlock_data has changed with the retail bootloader on the phone
From what I saw in vars - some vars had changed in the bootloader
But what I read at https://forum.xda-developers.com/g5/help/how-to-develop-blank-flash-t3791525 it seems to say of the boot.img file is newer - the blank flash will fail
Click to expand...
Click to collapse
estofjlw said:
sd_shadow said:
It should work for any XT1955-5 /QUOTE]
OK I can try it. I have a xt1955-6 - Verizon
Everything flashes with a xt1955-5 RETUS firmware except the boot.img and dtbo.img
If blank flash is an OEM signed file - maybe it will push over the existing boot.img
I will see if in the middle of the flash - the oem get_unlock_data has changed with the retail bootloader on the phone
From what I saw in vars - some vars had changed in the bootloader
But what I read at https://forum.xda-developers.com/g5/help/how-to-develop-blank-flash-t3791525 it seems to say of the boot.img file is newer - the blank flash will fail
Click to expand...
Click to collapse
I believe the boot.img in the blank flash can be updated too.
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
What happend when the device is not recognized by the blank flash and onlly appears Moto ADB Interface???
jodytejada said:
What happend when the device is not recognized by the blank flash and onlly appears Moto ADB Interface???
Click to expand...
Click to collapse
It's not in Emergency Download Mode
PC should see it as
Qualcomm QHSUSB_Bulk or qloader
Sent from my ocean using XDA Labs
VZW update locks out any other firmware
sd_shadow said:
estofjlw said:
I believe the boot.img in the blank flash can be updated too. /QUOTE]
That would be great except if it updates to newer than the RETUS firmware boot.img - which will cause a pre-flash error instead of an oem boot.img error
I have not tried yet . . . but the RETUS 134-4 firmware is older than the VZW 134-4 firmware which has not been posted on the https://mirrors.lolinet.com/firmware/moto/ocean/official/VZW/ website.
No other ocean variant I looked at is newer either - some have the 11/04 modify date - but inside the folder it is not the 134-4 firmware that is for that date.
Verizon's 134-4 update came down between November 2 and 4 in three updates as 1, 2 and then straight to 4 - behind my back on wifi and since the bootloader is still oem locked - and because it is Verizon - not eligible for an unlock code from Motorola due the Verizon ordering it as an oem branded phone, unless I can make it look like a RETUS bootloader to Motorola in the middle of the flash while the bootloader can be unlocked so they provide an unlock code for it _ I am betting I am screwed until the https://mirrors.lolinet.com/firmware/moto/ocean/official/VZW/ site has a post for the 134-4 VZW firmware
Right now it boots to fastboot mode immediately - so I do not want to make it worse and actually brick it
I looked inside the blank flash zip and there is no boot.img - but from my understanding the blank flash contacts the boot img and updates it - to what and how I do not know - in my case it needs to "downgrade" it an earlier date - I sure I had Magisk so it could patch the boot.img and fix this. See https://www.reddit.com/r/MotoG/comments/cdsbw6/quick_reference_moto_g7_power_manually_flashing/
The trouble is of course there is no access to ADB copy, push and pull commands in fastboot
I have a XT1955-5 True Factory unlocked Retail US Phone on the way - and this one will have to be shelved
Click to expand...
Click to collapse
Click to expand...
Click to collapse
sd_shadow said:
It's not in Emergency Download Mode
PC should see it as
Qualcomm QHSUSB_Bulk or qloader
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
Any solution at this point? or onlly a brick to my collection?
sd_shadow said:
estofjlw said:
I believe the boot.img in the blank flash can be updated too.
Click to expand...
Click to collapse
Well I have my answer . . . the Verizon XT1955-6 version restricts using blankflash and it will not go in EDL at all
C:\>fastboot oem blankflash
...
(bootloader) command restricted
FAILED (remote failure)
Since I can flash the RETUS bootloader can anyone suggest another work around to get past boot.img and DTBO.img
Click to expand...
Click to collapse
I'm having a similar problem. After flashing firmware is stuck in fastboot with the OEM relocked and the unlock code does not unlock it. Mine is retus xt1955-5
KeRbYRoK said:
I'm having a similar problem. After flashing firmware is stuck in fastboot with the OEM relocked and the unlock code does not unlock it. Mine is retus xt1955-5
Click to expand...
Click to collapse
Look for retus blank flash
Thanks man.
Ok what I did was hit it with blankflash. That still wouldn't clear out the faulty bootloader that was from the wrong firmware. But I found a new Android 10 firmware flashed it all checks were good and I'm sending this message from it right now.