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.
Related
Hey , Guyz ... So i have Xt1550 ( Moto G 2015 Indian - 2GB / 16 GB )
Updated to Marshmallow and i didn't liked it that much so , tried of Downgrading by flashing factory images of Android 5.1.1 Lollipop
( http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 )
I used this command on fastboot -
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.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 system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
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
Cmd commands -
Code:
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.063s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.531s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot flash bootloader bootloader.img
target reported max download size of 268435456 bytes
sending 'bootloader' (2546 KB)...
OKAY [ 0.188s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) flashing aboot ...
(bootloader) flashing tz ...
(bootloader) flashing hyp ...
(bootloader) flashing rpm ...
OKAY [ 1.714s]
finished. total time: 1.902s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (917 KB)...
OKAY [ 0.219s]
writing 'logo'...
OKAY [ 0.094s]
finished. total time: 0.328s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.720s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.388s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.751s]
writing 'recovery'...
OKAY [ 1.047s]
finished. total time: 1.799s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (232264 KB)...
OKAY [ 8.355s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.022s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.1
target reported max download size of 268435456 bytes
sending 'system' (261326 KB)...
OKAY [ 9.178s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.305s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.2
target reported max download size of 268435456 bytes
sending 'system' (241145 KB)...
OKAY [ 8.747s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.872s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.3
target reported max download size of 268435456 bytes
sending 'system' (255386 KB)...
OKAY [ 9.354s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.526s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.4
target reported max download size of 268435456 bytes
sending 'system' (257385 KB)...
OKAY [ 9.151s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.231s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.5
target reported max download size of 268435456 bytes
sending 'system' (240406 KB)...
OKAY [ 8.585s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.710s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
sending 'modem' (36944 KB)...
OKAY [ 1.555s]
writing 'modem'...
OKAY [ 1.064s]
finished. total time: 2.635s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.086s]
finished. total time: 0.086s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.116s]
finished. total time: 0.116s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot flash fsg fsg.mbn
target reported max download size of 268435456 bytes
sending 'fsg' (2035 KB)...
OKAY [ 0.243s]
writing 'fsg'...
OKAY [ 0.113s]
finished. total time: 0.359s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot erase cache
erasing 'cache'...
OKAY [ 0.140s]
finished. total time: 0.140s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot erase userdata
erasing 'userdata'...
OKAY [ 4.068s]
finished. total time: 4.084s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>fastboot reboot
rebooting...
finished. total time: -0.000s
E:\Mobile\Moto G3\Firmware\XT1550_OSPREY_RETASIA_DS_2GB_5.1.1_LPI23.72-65_cid7_s
ubsidy-DEFAULT_CFC.xml>
So now my phone is bricked ! thats my fault as i tried downgrading bootloader !
I can access bootloader mode and i have already tried flashing that again without using
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
commands !
Now tell me what to do , I don't want to unlock bootloader and install twrp and install cm12.1.1
Please help what can be done ?
Thanks
This is because your BL is locked. Pls unlock it and then try flashing the firmware. BROTIP: Always avoid downgrading.. Now flash the MM firmware to at least boot the device (if firmware is out).
Forever Alone said:
This is because your BL is locked. Pls unlock it and then try flashing the firmware. BROTIP: Always avoid downgrading.. Now flash the MM firmware to at least boot the device (if firmware is out).
Click to expand...
Click to collapse
Even i can't unlock bootloader .. because i have not enabled that on developer settings ( - As said by nelsonw )
harsinghal said:
Even i can't unlock bootloader [emoji14] .. because i have not enabled that on developer settings ( - As said by nelsonw )
Click to expand...
Click to collapse
Call it Stone not brick....[emoji12]
Sent from my MotoG3 using Tapatalk
get someone to backup their bootloader.img from marshmallow , and restore it back to YOUR device . that should work. I dont personally have marshmallow on my device as it is not available yet
ifu said:
Call it Stone not brick....[emoji12]
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Brick can be bricked , stone is hard to break !
I can deal with a brick ... not with a stone
therealduff1 said:
get someone to backup their bootloader.img from marshmallow , and restore it back to YOUR device . that should work. I dont personally have marshmallow on my device as it is not available yet
Click to expand...
Click to collapse
You know any guide on how to backup bootloader image ? I can try asking my frnd for that !
harsinghal said:
You know any guide on how to backup bootloader image ? I can try asking my frnd for that !
Click to expand...
Click to collapse
You can try googling it , as I am not sure myself. But I do know it is do able. Probably someone like fastboot backup bootloader. Don't try that command because I don't actually know if that it right xD . Anyway just flash the output file as a .img file , to your device and it should all be ok.
Please hit thanks , it means alot
Whether downgradable?
Fellas I have an XT1550. I got updated to stock MM via OTA. Afterwards I unlocked my bootloade, flashed latest TWRP and BetaSuperSU 2.66. Everything was fine untill when I tried to remove my Bootloader Unlocked warning screen by following steps in http://forum.xda-developers.com/2015-moto-g/themes-apps/remove-unlocke-bootloader-message-t3177801.
My phone got stuck in bootloader screen.
I wiped everything using TWRP.
Is it safe for me to flash stock lollipop now using fastboot without hard bricking.??????
Help !
Still Not able to Downgrade to Lollipop ! :crying::crying:
jithgr said:
Fellas I have an XT1550. I got updated to stock MM via OTA. Afterwards I unlocked my bootloade, flashed latest TWRP and BetaSuperSU 2.66. Everything was fine untill when I tried to remove my Bootloader Unlocked warning screen by following steps in http://forum.xda-developers.com/2015-moto-g/themes-apps/remove-unlocke-bootloader-message-t3177801.
My phone got stuck in bootloader screen.
I wiped everything using TWRP.
Is it safe for me to flash stock lollipop now using fastboot without hard bricking.??????
Click to expand...
Click to collapse
I upgraded to MM and downgraded to 5.1.1 successfully.
1> Try to access your stock recovery and do a wipe (data and cache). This step is very important as stated by @lost101 on his firmware flashing guide.
2> reboot back to boot loader mode
3> when using the flash commands, the first one : fastboot flash partition gpt.bin will potentially fail. This is since the partitions were updated to the tables defined according to the requirement of MM. Dont worry. fail on this command wont do anything.
4> proceed with the other commands one by one to flash your 5.1.1 carefully until the last command which says reboot.
TaDa.. downgrade completed.
'Factory data reset' in Android is an essential step that needs to be done when changing ROMs or downgrading. If your bootloader is unlocked, flash a custom ROM via TWRP, boot into Android and do a reset. After this, fastboot flashing of firmware images will be successful. If your bootloader is locked, you may have no choice but to return the phone to retailer.
@harsinghal :
Try the below order. It worked for me.
fastboot flash partition gpt.bin (Skip this command if prev validation fails)
fastboot flash bootloader bootloader.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 system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
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
Click to expand...
Click to collapse
Thanks bro, after data and cache wipe it worked, until then it was a nightmare.
Thanks again.
A friend of mine bricked his Moto G 2013 and, after many attempts on fixing it, I was unable to get it to work in any way.
The problem:
Classic boot loop: It gets stuck on "unlocked bootloader" screen on startup.
Why don't you just flash the stock rom directly from fastboot?
I did try to flash it many times, but it simply doesn't work.
No FAILED status is shown on fastboot flashing, but it simply doesn't install.
Why don't you flash a custom rom from a custom recovery?
Installing a custom recovery flashing also don't work even without showing any error on installation.
I was able to boot from twrp.img directly from fastboot, but it gives an error on any rom I try to flash from it.
Wiping from it did not help either.
The solution:
I have no clue. :crying:
Interesting,
What device is it? (XT10**) --> edit: I didn't see it was in subject, so xt1033
What os is you're computer running? (And what method did you use to install adb&fastboot)
Make sure you have recent adb and fastboot builds
If you are on Linux, you only need to make sure android-tools-adb and android-tools-fastboot are properly installed and updated (and that the udev rules allow to access the device)
If not I can't help you with the os specific part
I would retry to flash 41.1A bootloader first, and then try again to flash twrp 3.0.2 + CM13 + micro gapps
matmutant said:
Interesting,
What device is it? (XT10**) --> edit: I didn't see it was in subject, so xt1033
What os is you're computer running? (And what method did you use to install adb&fastboot)
Make sure you have recent adb and fastboot builds
If you are on Linux, you only need to make sure android-tools-adb and android-tools-fastboot are properly installed and updated (and that the udev rules allow to access the device)
If not I can't help you with the os specific part
I would retry to flash 41.1A bootloader first, and then try again to flash twrp 3.0.2 + CM13 + micro gapps
Click to expand...
Click to collapse
I'm on a windows 7 x64 machine.
Installed minimal adb&fastoot v1.1.3 via .exe installer... I don't really remember from where I have downloaded it, got it months ago, trying to unbrick my hard bricked moto G 2014.
Tried your method reflashing bootloader 41.1A found here:
41.1A
It also returned no error upon installation, perhaps, no luck on installing twrp again.
Tried flashing stock again:
Code:
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.050s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.350s
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.130s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.410s
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.120s]
writing 'logo'...
OKAY [ 0.080s]
finished. total time: 0.210s
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.430s]
writing 'boot'...
OKAY [ 0.610s]
finished. total time: 1.050s
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.430s]
writing 'recovery'...
OKAY [ 0.610s]
finished. total time: 1.040s
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.040s]
sending 'system' (249379 KB)...
OKAY [ 8.242s]
writing 'system'...
OKAY [ 8.129s]
finished. total time: 16.411s
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.050s]
sending 'system' (252566 KB)...
OKAY [ 8.329s]
writing 'system'...
OKAY [ 7.401s]
finished. total time: 15.780s
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.060s]
sending 'system' (249711 KB)...
OKAY [ 8.219s]
writing 'system'...
OKAY [ 15.926s]
finished. total time: 24.205s
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' (47152 KB)...
OKAY [ 1.600s]
writing 'modem'...
OKAY [ 0.760s]
finished. total time: 2.360s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.050s]
finished. total time: 0.050s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.060s]
finished. total time: 0.060s
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.100s]
writing 'fsg'...
OKAY [ 3.185s]
finished. total time: 3.285s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.060s]
finished. total time: 0.060s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.070s]
finished. total time: 0.070s
Now i'm getting "fails" on the beggining.
lhtrevisan said:
I'm on a windows 7 x64 machine.
Installed minimal adb&fastoot v1.1.3 via .exe installer... I don't really remember from where I have downloaded it, got it months ago, trying to unbrick my hard bricked moto G 2014.
Tried your method reflashing bootloader 41.1A found here:
41.1A
It also returned no error upon installation, perhaps, no luck on installing twrp again.
Tried flashing stock again:
Code:
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.050s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.350s
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.130s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.410s
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.120s]
writing 'logo'...
OKAY [ 0.080s]
finished. total time: 0.210s
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.430s]
writing 'boot'...
OKAY [ 0.610s]
finished. total time: 1.050s
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.430s]
writing 'recovery'...
OKAY [ 0.610s]
finished. total time: 1.040s
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.040s]
sending 'system' (249379 KB)...
OKAY [ 8.242s]
writing 'system'...
OKAY [ 8.129s]
finished. total time: 16.411s
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.050s]
sending 'system' (252566 KB)...
OKAY [ 8.329s]
writing 'system'...
OKAY [ 7.401s]
finished. total time: 15.780s
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.060s]
sending 'system' (249711 KB)...
OKAY [ 8.219s]
writing 'system'...
OKAY [ 15.926s]
finished. total time: 24.205s
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' (47152 KB)...
OKAY [ 1.600s]
writing 'modem'...
OKAY [ 0.760s]
finished. total time: 2.360s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.050s]
finished. total time: 0.050s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.060s]
finished. total time: 0.060s
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.100s]
writing 'fsg'...
OKAY [ 3.185s]
finished. total time: 3.285s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.060s]
finished. total time: 0.060s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.070s]
finished. total time: 0.070s
Now i'm getting "fails" on the beggining.
Click to expand...
Click to collapse
This make me think you would need to flash a 5.1 gpt.bin (that you can find in an official zip for your XT1033 device), and then retry to update the bootloader
Though I should work, "sh*t happens" sometime (I am currently failing to update a Peregrine from JB to CM13 xD
Got gpt.bin from "official" untouched 5.1 update... same error when trying to flash it.
lhtrevisan said:
Got gpt.bin from "official" untouched 5.1 update... same error when trying to flash it.
Click to expand...
Click to collapse
what does "fastboot getvar version-bootloader" outputs?
and "getvar all" too btw"
matmutant said:
what does "fastboot getvar version-bootloader" outputs?
and "getvar all" too btw"
Click to expand...
Click to collapse
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar version-bootloader"
version-bootloader: 411A
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x5
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: T099706POH
(bootloader) cid: 0x000C
(bootloader) channelid: 0x00
(bootloader) uid: 50AA5E040F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jul 9 4: 2:45 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retbr_ds/falcon_um
(bootloader) ro.build.fingerprint[1]: tsds:5.1/LPBS23.13-56-2/2:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.221.201.2.falcon_umt
(bootloader) ro.build.version.full[1]: sds.Brasil.en.BR
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g89906d6 ([email protected]
(bootloader) kernel.version[1]: ilclbld27) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri Feb 26 07:13:58 CST 2016
(bootloader) sdi.git: git=MBM-NG-V41.1A-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.1A-0-g199f3c5
(bootloader) rpm.git: git=MBM-NG-V41.1A-0-g8b7736e
(bootloader) tz.git: git=MBM-NG-V41.1A-0-g99c1a7c
(bootloader) aboot.git: git=MBM-NG-V41.1A-0-g80481ae
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.060s
When you succeded to boot TWRP (using fastboot), did you try to flash an official 5.1 retail build?
---------- Post added at 22:39 ---------- Previous post was at 22:27 ----------
Did you have a llok at this thread too?
I didn't have time to read it thoroughly but the guy might had a similar problem?
http://forum.xda-developers.com/moto-g/help/c-spire-xt1031-moto-g-bootloader-t3156173
matmutant said:
When you succeded to boot TWRP (using fastboot), did you try to flash an official 5.1 retail build?
---------- Post added at 22:39 ---------- Previous post was at 22:27 ----------
Did you have a llok at this thread too?
I didn't have time to read it thoroughly but the guy might had a similar problem?
http://forum.xda-developers.com/moto-g/help/c-spire-xt1031-moto-g-bootloader-t3156173
Click to expand...
Click to collapse
No, I didn't try that, as I'm not able to send any archive to the cell phone in order to be able to install that from twrp.
The error I mentioned on first post was at "pushing" the rom into the cell phone... I think it's because adb is not able to find my device ("adb devices -l" returns no results).
Also, twrp mounts the cell phone as an removable drive, perhaps, it freezes if I try to save directly with Ctrl+C and Ctrl+V.
lhtrevisan said:
No, I didn't try that, as I'm not able to send any archive to the cell phone in order to be able to install that from twrp.
The error I mentioned on first post was at "pushing" the rom into the cell phone... I think it's because adb is not able to find my device ("adb devices -l" returns no results).
Also, twrp mounts the cell phone as an removable drive, perhaps, it freezes if I try to save directly with Ctrl+C and Ctrl+V.
Click to expand...
Click to collapse
So you have a TWRP installed on the device???? (which one?)
If so, use and OTG flashdrive, you might succeed from there
matmutant said:
So you have a TWRP installed on the device???? (which one?)
If so, use and OTG flashdrive, you might succeed from there
Click to expand...
Click to collapse
No, i don't have it installed... I use it booting from fastboot with "fastboot boot recovery.img" where recovery.img is twrp image renamed.
Edit: Also I don't have an OTG cable. :/
lhtrevisan said:
No, i don't have it installed... I use it booting from fastboot with "fastboot boot recovery.img" where recovery.img is twrp image renamed.
Edit: Also I don't have an OTG cable. :/
Click to expand...
Click to collapse
try to find one
That would be interesting to try to boot from the recovery (via fastboot), unplug, plug OTG w/ a 5.1 stock rom zip and try to flash
matmutant said:
try to find one
That would be interesting to try to boot from the recovery (via fastboot), unplug, plug OTG w/ a 5.1 stock rom zip and try to flash
Click to expand...
Click to collapse
I gave up on that... Returned it to my friend earlier today. Thank you very much for the effort on helping me.
Is there any way of closing the thread here?
[Failed]
lhtrevisan said:
I gave up on that... Returned it to my friend earlier today. Thank you very much for the effort on helping me.
Is there any way of closing the thread here?
Click to expand...
Click to collapse
You're welcome!
I am really sorry I couldn't help you more,
Maybe your friend can try the last option him/herself ?
I don't think you can close the thread yourself, but let's keep it open if someone ever wants to add something one day
How to revert back to normal from gpe
Sent from my Redmi 3S using XDA-Developers mobile app
lhtrevisan said:
A friend of mine bricked his Moto G 2013 and, after many attempts on fixing it, I was unable to get it to work in any way.
The problem:
Classic boot loop: It gets stuck on "unlocked bootloader" screen on startup.
Why don't you just flash the stock rom directly from fastboot?
I did try to flash it many times, but it simply doesn't work.
No FAILED status is shown on fastboot flashing, but it simply doesn't install.
Why don't you flash a custom rom from a custom recovery?
Installing a custom recovery flashing also don't work even without showing any error on installation.
I was able to boot from twrp.img directly from fastboot, but it gives an error on any rom I try to flash from it.
Wiping from it did not help either.
The solution:
I have no clue. :crying:
Click to expand...
Click to collapse
May be, check your android version matches TWRP recovery version
Hi There,
I hope someone can advise and possibly provide help resolving this problem.
The Moto G4 XT1622 is not able to boot to OS, It only boots into bootloader, cannot go into recovery and cannot go into Factory Mode etc.
The error i get on the phone is....
"Start Up Failed"
Failed to verify hab image boot
Failed to verify boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot Reason: Fall-through from normal boot mode
I have tried to clear fb_mode and tried to unlock the bootloader without success.
I have tried various stock roms to get this fixed. The phone has never been unlocked and not been rooted.
C:\adb>fastboot oem fb_mode_set
...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\adb>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.094s
C:\adb>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.172s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) Security version downgrade
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) will fail: flash:aboot
FAILED (remote failure)
finished. total time: 0.319s
C:\adb>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (1848 KB)...
OKAY [ 0.094s]
writing 'logo'...
OKAY [ 0.078s]
finished. total time: 0.172s
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.687s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.891s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.664s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.883s
C:\adb>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257278 KB)...
OKAY [ 9.982s]
writing 'system'...
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.097s
C:\adb>fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (258607 KB)...
OKAY [ 10.125s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.157s
C:\adb>fastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (258384 KB)...
OKAY [ 10.076s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.107s
C:\adb>fastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system' (252313 KB)...
OKAY [ 9.973s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.004s
C:\adb>fastboot flash system system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system' (254404 KB)...
OKAY [ 10.017s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.064s
C:\adb>fastboot flash system system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system' (258060 KB)...
OKAY [ 10.114s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.161s
C:\adb>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (76857 KB)...
OKAY [ 3.038s]
writing 'modem'...
OKAY [ 2.036s]
finished. total time: 5.075s
C:\adb>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\adb>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\adb>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (1864 KB)...
OKAY [ 0.100s]
writing 'fsg'...
OKAY [ 0.109s]
finished. total time: 0.210s
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.031s
C:\adb>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.078s]
finished. total time: 0.078s
C:\adb>fastboot erase customize
erasing 'customize'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\adb>fastboot erase clogo
erasing 'clogo'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\adb>fastboot oem fb_mode_clear
...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.016s
Click to expand...
Click to collapse
Phatzy said:
Hi There,
I hope someone can advise and possibly provide help resolving this problem.
The Moto G4 XT1622 is not able to boot to OS, It only boots into bootloader, cannot go into recovery and cannot go into Factory Mode etc.
The error i get on the phone is....
"Start Up Failed"
Failed to verify hab image boot
Failed to verify boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot Reason: Fall-through from normal boot mode
I have tried to clear fb_mode and tried to unlock the bootloader without success.
I have tried various stock roms to get this fixed. The phone has never been unlocked and not been rooted.
Click to expand...
Click to collapse
It looks to me like you're trying to flash a firmware that is a downgrade from what was already on the device. It's probably blocking you because it won't allow a downgrade. Flash the version that the device already had on it or flash a newer version.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
I throught that would be the case but i have tried the 4 roms available for this device and even the 7.0 OTA rom but nothing if able to flash. I cannot even unlock the bootloader.
Thanks
Phatzy said:
I throught that would be the case but i have tried the 4 roms available for this device and even the 7.0 OTA rom but nothing if able to flash. I cannot even unlock the bootloader.
Thanks
Click to expand...
Click to collapse
You may have to faatboot flash the individual .img(boot, system, cache, recovery, etc..) files by themselves.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Yeah I tried that too. I just get the same errors as this.....
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.094s
Click to expand...
Click to collapse
Phatzy said:
Yeah I tried that too. I just get the same errors as this.....
Click to expand...
Click to collapse
Do you have USB debugging enabled?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Hi,
I dont think so as I cannot check due to the phone not able to get pass bootloader. I tried to use the fb_mode command but still goes back to bootloader saying filed to start.
Thanks..
Droidriven said:
Do you have USB debugging enabled?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
My story goes.
Had happy running TugaPower Rom
Decided to install MultiRom and Ubuntu.
Then after running for a week or so, decided to wipe and install TugaPower alone.
All has run well for a while. Decided to wipe and make a fresh install.
MultiRom I am unable to fully remove, even trying to replace with original TWRP.
When I try to flash the ROM, I get reported that this cant be installed as the model is . not bacon or A0001. error 7
I have edited the updater-script to not make a check on the model and it then installs.
When i reboot it goes straight back to the recovery!!!
I have tried reinstalling multirom and then flashing but again it keeps going to the recovery.
Ive tried to fastboot the original OS via https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541, but fastboot reports `FAILED (remote: Device not unlocked cannot flash or erase)`
(Full output at bottom)
The install all end with 1 and multirom could see the roms
ive tried extracting just the .img and flashing to get going
im at a loss, any help much appreciated
Code:
[email protected]:sudo fastboot oem unlock
...
OKAY [ 0.009s]
finished. total time: 0.009s
[email protected]:/home/steve/Downloads/cm# ./flash-all.sh
target reported max download size of 1073741824 bytes
sending 'modem' (57457 KB)...
OKAY [ 1.805s]
writing 'modem'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 1.806s
target reported max download size of 1073741824 bytes
sending 'sbl1' (273 KB)...
OKAY [ 0.011s]
writing 'sbl1'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.013s
target reported max download size of 1073741824 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.004s]
writing 'dbi'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.006s
target reported max download size of 1073741824 bytes
sending 'aboot' (445 KB)...
OKAY [ 0.015s]
writing 'aboot'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.017s
target reported max download size of 1073741824 bytes
sending 'rpm' (186 KB)...
OKAY [ 0.008s]
writing 'rpm'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.010s
target reported max download size of 1073741824 bytes
sending 'tz' (325 KB)...
OKAY [ 0.012s]
writing 'tz'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.015s
target reported max download size of 1073741824 bytes
sending 'LOGO' (328 KB)...
OKAY [ 0.013s]
writing 'LOGO'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.015s
target reported max download size of 1073741824 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.322s]
writing 'oppostanvbk'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.323s
target reported max download size of 1073741824 bytes
sending 'recovery' (9968 KB)...
OKAY [ 0.314s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.315s
target reported max download size of 1073741824 bytes
erasing 'system'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.000s
target reported max download size of 1073741824 bytes
sending 'boot' (7274 KB)...
OKAY [ 0.231s]
writing 'boot'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.232s
target reported max download size of 1073741824 bytes
erasing 'cache'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.000s
target reported max download size of 1073741824 bytes
erasing 'userdata'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.000s
rebooting...
finished. total time: 0.050s
Boot the phone into fastboot mode and open cmd with administrative rights and go into the adb platform tools folder and enter in cmd fastboot OEM -device info
kallum7 said:
Boot the phone into fastboot mode and open cmd with administrative rights and go into the adb platform tools folder and enter in cmd fastboot OEM -device info
Click to expand...
Click to collapse
C:\Windows\system32>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.016s]
finished. total time: 0.016s
now run script
C:\Windows\system32>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Windows\system32>fastboot boot C:\Users\Steve\Downloads\twrp-3.2.3-0-bacon.img
downloading 'boot.img'...
OKAY [ 0.438s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.438s
C:\Windows\system32>fastboot oem unlock
...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Windows\system32>fastboot boot C:\Users\Steve\Downloads\twrp-3.2.3-0-bacon.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.438s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.438s
C:\Windows\system32>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.016s]
finished. total time: 0.016s
Try another USB micro cable
Thank you for your reply.
I have tried two other cables I have and still having the same issues
Are you using Linux or windows
kallum7 said:
Are you using Linux or windows
Click to expand...
Click to collapse
I have both available,
I am trying each OS at each new try
Ran all three of the files on here to get the triggers to true / true
https://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
I then ran `fastboot boot twrp.img`
This gave me twrp and i then installed a rom as normal...
im back up and running
thanks for all your patience and help
stevieag said:
Ran all three of the files on here to get the triggers to true / true
https://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
I then ran `fastboot boot twrp.img`
This gave me twrp and i then installed a rom as normal...
im back up and running
thanks for all your patience and help
Click to expand...
Click to collapse
Im having problems again..
OTA lineage update came up..
i clicked to install.
Phone restarted and immediately went to the multirom twrp screen.
I have had this in the past and have needed to install from this screen but i couldnt find the file to install
So on phone restart it loops back to the multirom twrp
I can still adb and fastboot see below
Code:
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.006s]
finished. total time: 0.006s
on fastboot boot twrp.img
it seems to restart but sits on fastboot screen
story:
on fastboot
send command
fastboot screen goes brighter
Any ideas
I have tried windows and linux plus 2 cables
What would be ideal would to completely clear multirom from my phone and get back to stock or stock twrp so i can flash as normal
stevieag said:
Im having problems again..
OTA lineage update came up..
i clicked to install.
Phone restarted and immediately went to the multirom twrp screen.
I have had this in the past and have needed to install from this screen but i couldnt find the file to install
So on phone restart it loops back to the multirom twrp
I can still adb and fastboot see below
Code:
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.006s]
finished. total time: 0.006s
on fastboot boot twrp.img
it seems to restart but sits on fastboot screen
story:
on fastboot
send command
fastboot screen goes brighter
Any ideas
I have tried windows and linux plus 2 cables
What would be ideal would to completely clear multirom from my phone and get back to stock or stock twrp so i can flash as normal
Click to expand...
Click to collapse
sorted
https://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390
Ultimate fix
Right, i ended with a boot loop i couldnt sort
so
i downloaded - cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot.zip (to big for upload)
This contains all the files you need including os
Once in fastboot
volume up and power or in recovery
Code:
adb reboot bootloader
In windows in a terminal (search next to start menu for cmd, right click on the pop up cmd and choose open as admin)
Run each of these
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash LOGO logo.bin
fastboot flash modem NON-HLOS.bin
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata_64G.img
fastboot reboot
THIS IS FOR 64GB ONLY with 16GB change userdata_64.img to the file userdata.img
In Linux open terminal, drop to root
Code:
sudo su -
you can then run above files or run flash-radio.sh
Code:
./flash-radio.sh
weirly may still need sudo!!!
This will install the os etc and you are back to stock (although old)
Now you can install twrp as normal
Code:
fastboot flash recovery twrp.img
Code:
fastboot reboot
here you should be back to normal twrp recovery
Copy over your ROM and Gapps
Install as normal twrp and done
im now on pie with 3.2.2 twrp and gapps 9
This installed ROMs that were complaining of not the right model, error 7, error 255 ........ and on
All sorted, in fact ive installed 3 different roms now without fails
hello,
i'm trying to flash dtbo image and that vendor image and even the recovery but it hits me woth this error!
if someone could hjelp me would be appericiated.
yes i have unlocked everything.
Thanks in advance!!!
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dtbo "C:\Users\Rollin'\Downloads\Compressed\dtbo.img"
target reported max download size of 805306368 bytes
sending 'dtboa' (24576 KB)...
OKAY [ 0.658s]
writing 'dtboa'...
(bootloader) Invalid partition name dtboa
FAILED (remote failure)
finished. total time: 0.735s
Walther6 said:
hello,
i'm trying to flash dtbo image and that vendor image and even the recovery but it hits me woth this error!
if someone could hjelp me would be appericiated.
yes i have unlocked everything.
Thanks in advance!!!
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dtbo "C:\Users\Rollin'\Downloads\Compressed\dtbo.img"
target reported max download size of 805306368 bytes
sending 'dtboa' (24576 KB)...
OKAY [ 0.658s]
writing 'dtboa'...
(bootloader) Invalid partition name dtboa
FAILED (remote failure)
finished. total time: 0.735s
Click to expand...
Click to collapse
Look at this post and the answer below it. Let me know if you have any questions!