30 replies to this topic

[asgaard]

What else we can do? As far as i know Recovery partition was erased, is there any chance to install it, again?

[SamuriHL]

I don't have any more advice for you.  Fastboot fails because you didn't follow the directions I gave you.  RSD isn't working which is why I said to try fastboot with the specific file I went and found for your device.  

[asgaard]

Sorry for late reply, just get back home.

I follow all steps which You suggest me. I tried House of Moto 2.2 first of all (later on 2.3) and really don't know what i'm doing wrong, because it seems to be working fine at the beginning. Can You have a look on the pictures and tells me where is my fault?

 

Thanks in advance

 

Btw. RSD starts in House of Moto after few commands.

If recovery partition was erased is it linked anyhow with Your program?

[SamuriHL]

Nope, my program doesn't erase anything until the script tells it to, and it most certainly doesn't tell it to erase the recovery partition.  Run the createLog program again and I'll show you what you did wrong and why fastboot mode (which is what you need....RSD is NOT going to fix this else we'd not be using the House of Moto for this in the first place) isn't working.

[asgaard]

My dear friend that's misunderstood. I didn't mean that Your program erase recovery partition, i've used another program on another site before You sent me a link to Yours. I'll create Log program again (which version of House of Moto should i fire it up?? )

[asgaard]

Ok. folks just to let You know, friend of mine advice me to try such a commands (i had a chat with him over the internet)

 

1. CMD: fastboot oem get_unlock_data

fastboot oem get_unlock_data
...
(bootloader) 3A25150915586129#54413233373034
(bootloader) 48354100000000000000000000#1ACF
(bootloader) 4FDA6DCEE30F10CACA1F7FC1CBD39CB
(bootloader) 08BBF#DFF3ABAE76852954D805ED6EF
(bootloader) 3FA0000
OKAY [ 0.290s]
finished. total time: 0.290s

2. fastboot oem unlock PJYERHAJMZMPVYSRKIXN

fastboot oem unlock PJYERHAJMZMPVYSRKIXN
...
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
(bootloader) Erase userdata fail
(bootloader) General Unlock failure!
(bootloader) OEM unlock failure!
FAILED (remote failure)
finished. total time: 8.390s

In Motorola phone it says
Unlock
Fastboot command failed

He said that partition table is faulty. It can be done only in Linux or JTAG.


We tried this as well:

CMD: fastboot format data

(bootloader) Variable not supported!
formatting 'data' partition...
(bootloader) Variable not supported!
FAILED (remote failure)
FAILED (remote failure)
finished. total time: 0.342s

 

He said that emmc is faulty and that's why fastboot doesn't work.

 

Any advice on this, please?

[SamuriHL]

That's beyond anything anyone on this forum can help you with.  JTag is not a software thing.  It's a piece of hardware that allows you to reflash the phone in a very special way.  

[cmh714]

jtag is not for goofing around by most people.

[asgaard]

So any advice? Sell it as faulty or try something else?

[asgaard]

This afternoon I was in few repair shops in Dublin and none of them can fixed as they stated that Motorola isn't so popular in IRL. Mostly i heard "i have no clue" or "You have to send to manufacturer". One of them tried fixed (it takes roughly 3 hours), but also gave up. He said that it's nearly same story with chip which Samsung S3 had. Don't ask me what does it mean, cuz have no idea. Friend of mine who's also user on another forum about phones will fix it as he stated, but don't know if i gonna send it to Poland. At this stage i have to stop any more tests with Motorola as i don't know what i have to do.


Thanks for all support and will keep You inform if something turn up.

Btw. one of Chinese "call him tech-e" broked back cover of Motorola (beside camera, cracked glass), but i noticed it when i left his repair centre.

[asgaard]

Ok. guys quick update.

Friend of mine who fix phones put hands on that Motorola and tried everything. As he said there is little chance to fix it, but first of all You need to get to memory without unlocked bootloader, as it's blocked all commands. Any suggestions? 

 

Unfornately there isn't any fix atm, so i had to buy motherboard for it.

Thanks anyway for any solutions.