[X]Assistant

[CybFor]

EXE q AIM ProoSew this custom recovery. And immediately go to it. By the result, it will be seen whether my stock is suitable.

Attached files

recovery.img(6 MB)


Post has been editedCybFor - 03.04.18, 20:26

Reason for editing: Edit

[EXE q AIM Proo]

CybFor,
the same black screen, even the backlight sensor worked, but there is no image)

In short, this is something to do?

clack

so how do i flash ubifs rum? who will make the video?

Post has been editedEXE q AIM Proo - 03.04.18, 23:23

[CybFor]

EXE q AIM Prooand what's the point? Does the kernel have ubifs support?
Preloader with firmware overwritten?

[EXE q AIM Proo]

CybFor,
I repeat once again, everything absolutely works, except for the image
maybe yes, the recovery still had to earn, at least some, but at least the stock, even though it wasn’t reproduced by caste, I tried several options - silence

There is a 6582 scatter with NAND formatting, supposedly from this device, but it has 6572 percent, I do not know why they decided that there is 6582, or what kind of versions there are.

can try to put 6572 with NAND formatting? How to remake or in flash tula this will not work?

clack

eMMC formattingMT6572_Android_scatter.txt(7.04 KB)

NAND formattingMT6582_Android_scatter.txt(7.48 KB)
supposedly go from this, but not sewn, with an error that costs 6572

Or is it all the same in the rum itself, who has the same problem on the format of the flash drive on which the rum is put

Post has been editedEXE q AIM Proo - 04.04.18, 09:06

[CybFor]

EXE q AIM Proo, I repeat for those who are in the tank, if the kernel does not support the fs format, then the partition will not be mounted! That is, if it were not for the correct fs format, there was no launch of the system at all, and not just images.

And here you have about symptomatology
SP Flash Tool is a flash driver for MTK smartphones. (Post SuigoSora # 47522489)

[EXE q AIM Proo]

CybFor,
Mm, I thought the preloader is needed to synchronize with the computer, there was no problem with that.
That is, I do not need a boot or all the rum to look for a preloader? he didn’t even pay attention to him, the computer immediately sees the device without problems

Post has been editedEXE q AIM Proo - 04.04.18, 10:43

[CybFor]

EXE q AIM Proo, even if the preloader is correct, it is not the fact that it is sewn. There is such an option that he locked himself up. Search, try. Stock backup left?
Better that the whole rum with the preloader and the rest of the files

Post has been editedCybFor - 04.04.18, 11:06

Reason for editing: Adding

[EXE q AIM Proo]

CybFor,
What does it mean, and how to fix it?

Comxx what does it mean Was COM2, and right now COM12-13, or is it from another opera?

Post has been editedEXE q AIM Proo - 04.04.18, 17:19

[EXE q AIM Proo]

By the way, yes, when changing the application, it generally turns on, how to choose now?

[CybFor]

EXE q AIM Proo, I got locked in, that is, just so I can not rewrite it, I need it on the mat. Board contacts to short that would be possible. Or through the jtag flash the chip itself. But it rarely happens.
Som port is a virtual interface ... ask Google for details.
What to do? Or to sort out, or I can merge my own. But since the backup is not with me, then a couple of preloaders will be available to the skinte, what would I do to your size.

[EXE q AIM Proo]

CybFor,
damn for some reason I can not download, it hangs at me or something

Post has been editedEXE q AIM Proo - 04.04.18, 20:00

[CybFor]

EXE q AIM Prootry

Attached files

preloader.zip(59.21 KB)
uboot.zip(384.15 KB)


Post has been editedCybFor - 04.04.18, 23:59

Reason for editing: adding

[CybFor]

EXE q AIM Proo, first one preloader. If not then will be killed

[EXE q AIM Proo]

CybFor,
oo gone thank you
this rum+ your preloader + uboot

after turning off the screen, it is again black. In the settings in fact everything is correctly written, the memory is in a particular case, but it says that the percent is 6582

Post has been editedEXE q AIM Proo - 05.04.18, 09:22

[CybFor]

EXE q AIM ProoDoes the phone write the wrong memory? In the recovery of norms?

[EXE q AIM Proo]

CybFor,
on the contrary, it was not right, as it is, its 20GB and 30GB flash drive, right now, only with a percentage defect
all norms recovery

I do not understand, this is not how many types of devices or something, a lot of firmware 6582 for this device, although they are not sewn

Post has been editedEXE q AIM Proo - 05.04.18, 09:54

[CybFor]

EXE q AIM Proohave a picture Proc writes wrong where ?? In the settings or in flash tule?

[EXE q AIM Proo]

CybFor,
Everything works, in flash tule 6572, in the settings of the device it writes 6582, but this is all nonsense

The main thing is that it turns on, everything works, the screen also works, when the screen is turned off, the screen does not turn on, you have to pull out the battery and re-enable it, then the rules. everything works, the sound is vibrating, etc. but the screen doesn’t, but it’s not always the case with the screen turned on)

Post has been editedEXE q AIM Proo - 05.04.18, 10:26

[CybFor]

EXE q AIM Proo, build.prop you need to edit for the normal display of the prots. In the recovery that I dumped, when a simple screen goes out, does it tan back?

[EXE q AIM Proo]

CybFor,
I installed a custom recovery (I did not think that the screen goes out in it), but it lights up back