8 replies to this topic

[evil_haxor]

I was given a xt1080 for repair

24.13.2.obake-maxx
SU6-7.2
Locked bootloader. No root. No adb access.

 

System boots but there is constants force close of background processes like gapps and acore.

I wanted to factory reset and I did but on reboot it had all the same apps and user data intact, no factory state.

Changing any config or uninstalling any app result in it being back after reboot.

 

What I've tried so far:

 

-Factory option in AP Fastboot menu. Reboots to system with all the data intact.

-Recovery option in AP Fastboot menu. Reboots to bootloader and states "Boot up failed".

 

-fastboot erase userdata

-fastboot -w

both with the resulting output:

erasing 'userdata'...

OKAY [  0.500s]

erasing 'cache'...

OKAY [  0.620s]

finished. total time: 1.120s

but sadly all userdata is sitting there intact after reboot.

 

 

I downloaded VZW-4.4.4-SU6-7.2-release-keys.xml.zip. Tried with RSDLite but it didn't detect the device.

I have installed the drivers and MotorolaDeviceManager. So I decompressed the firmware and flashed the partitions

using fastboot in a script. Resulting in all partitions being flashed OK but after reboot the device

was the same as before with all the apps and user data present. Spooky isn't it?

 

Can some one offer me any advice? Is it a hardware faliure?

 

 

Output of the script follows:

 

C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe oem fb_mode_set

< waiting for device >

...

OKAY [  0.109s]

finished. total time: 0.109s

 

C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe flash partition gpt.bin

sending 'partition' (32 KB)...

OKAY [  0.220s]

writing 'partition'...

This may take a few seconds, if a

different partition table is being

flashed since we need to backup

and restore a few partitions

OKAY [  0.444s]

finished. total time: 0.665s

 

C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe flash motoboot motoboot.img

sending 'motoboot' (1604 KB)...

OKAY [  0.360s]

writing 'motoboot'...

flashing tz ...

flashing rpm ...

flashing aboot ...

flashing sbl1 ...

flashing sbl2 ...

flashing sbl3 ...

OKAY [  4.540s]

finished. total time: 4.900s

 

C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe flash logo logo.bin

sending 'logo' (215 KB)...

OKAY [  0.290s]

writing 'logo'...

OKAY [  0.811s]

finished. total time: 1.102s

 

C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe flash boot boot.img

sending 'boot' (10240 KB)...

OKAY [  0.900s]

writing 'boot'...

OKAY [  1.872s]

finished. total time: 2.772s

 

C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe flash recovery recovery.img

sending 'recovery' (10240 KB)...

OKAY [  0.900s]

writing 'recovery'...

OKAY [  1.512s]

finished. total time: 2.412s

 

C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe flash system system.img

sending 'system' (786432 KB)...

OKAY [ 49.426s]

writing 'system'...

OKAY [ 54.106s]

sending 'system' (531955 KB)...

OKAY [ 33.515s]

writing 'system'...

OKAY [ 36.056s]

finished. total time: 173.103s

 

C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe flash modem NON-HLOS.bin

sending 'modem' (54252 KB)...

OKAY [  3.671s]

writing 'modem'...

OKAY [  2.330s]

finished. total time: 6.002s

 

C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe erase modemst1

erasing 'modemst1'...

OKAY [  0.419s]

finished. total time: 0.419s

 

C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe erase modemst2

erasing 'modemst2'...

OKAY [  0.419s]

finished. total time: 0.419s

 

C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe flash fsg fsg.mbn

sending 'fsg' (538 KB)...

OKAY [  0.330s]

writing 'fsg'...

OKAY [  0.761s]

finished. total time: 1.092s

 

C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe erase cache

erasing 'cache'...

OKAY [  0.649s]

finished. total time: 0.649s

 

C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe erase userdata

erasing 'userdata'...

OKAY [  0.540s]

finished. total time: 0.540s

 

C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe erase customize

erasing 'customize'...

OKAY [  0.150s]

finished. total time: 0.150s

 

C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe erase clogo

erasing 'clogo'...

OKAY [  0.518s]

finished. total time: 0.518s

 

C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe oem config carrier gsm

...

Failed to flash config value

OKAY [  0.149s]

finished. total time: 0.150s

 

C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe oem fb_mode_clear

...

OKAY [  0.148s]

finished. total time: 0.148s

 

C:\Users\ernesto\Downloads\xt1080\ADB&FastBoot_v2.56>mfastboot.exe reboot

rebooting...

 

finished. total time: 0.002s

 

[livinginkaos]

Did you try booting into recovery and erasing data and cache from there

Sent from my Nexus 6P using Tapatalk

[evil_haxor]

Did you try booting into recovery and erasing data and cache from there

Sent from my Nexus 6P using Tapatalk

 

Recovery does not load. On selecting Recovery option in AP Fastboot menu the device reboots to bootloader and states "Boot up failed".

[SamuriHL]

I'd say you have some kind of hardware problem going on as it seems to have flashed everything properly.  If you still can't reboot into recovery after that flash, something else is going on with the device.

[livinginkaos]

The one thing that looked odd to me was :

 

"This may take a few seconds, if a

different partition table is being

flashed since we need to backup

and restore a few partitions"

 

I don't remember seeing a message like that except when going to a new OS.  Did the person who left the device with you try to fix it themselves by flashing firmware? 

[evil_haxor]

 

The one thing that looked odd to me was :

 

"This may take a few seconds, if a

different partition table is being

flashed since we need to backup

and restore a few partitions"

 

I don't remember seeing a message like that except when going to a new OS.  Did the person who left the device with you try to fix it themselves by flashing firmware? 

 

 

 

I really dont know what was done to it before, but is possible some one tried to flash it. I dont have much experience with Motorola so I dont know about the "This may take a few seconds..." message. However it took "total time: 0.665s" to flash gpt ... so idk what conclusion to make. I think it could be a hardware problem, just find it strange not to get any errors. Im thinking about flashing the wrong firmware to see what I get.

[livinginkaos]

I really dont know what was done to it before, but is possible some one tried to flash it. I dont have much experience with Motorola so I dont know about the "This may take a few seconds..." message. However it took "total time: 0.665s" to flash gpt ... so idk what conclusion to make. I think it could be a hardware problem, just find it strange not to get any errors. Im thinking about flashing the wrong firmware to see what I get.

Just don't flash a different device's firmware, that will definitely give you a permanent problem.  You should get a downgrade error since the one you used was the most recent.

[evil_haxor]

I selected BP Tools in bootloader menu. Now I have adb access. Tried to delete some files, this is what I get:

 

shell@obake-maxx:/sdcard/dcim/Camera $ rm *

rm *

rm failed for IMG_20160222_223144143.jpg, Read-only file system

255|shell@obake-maxx:/sdcard/dcim/Camera $

 

In BP Tools mode various devices get detected. One of them is Motorola QC Diag Port, I installed the drivers.

Now it shows in QPST software. QPST has a Software Download utility that is suposed to flash bootloaders, 

partitions images and whole firmware images. Does any one has any experience flashing with QPST?

[livinginkaos]

I don't believe there is write access to the data partition when you boot to bp tools.

Sent from my Nexus 6P using Tapatalk