Search results

I did factory reset and setup as new phone after updating from miui 11 to miui 12 and ghosting is not apparent anymore i dont know why.

This could be hardware issue, it happened to me using keyboard, otherwise everything works, if you are desperate to check if its hardware or software issue i would flash GSI rom and just check, i think there is one where its almost stable, only bug is FOD, but for testing this issue its good i...

Try disabling power saver package called "com.miui.powerkeeper" then report back if it still have touch problems. Use https://github.com/Szaki/XiaomiADBFastbootTools or adb command line, whatever you are confortable more with.

Download links are dead? Ray_lau I am unable to download, just says connection timeout on sourceforge link on PE site?

Its been a long time i have been on this thread since i dont have note 4 anymore, there is NO way to get original IMEI back if you dont have backup. Only thing you can do is flash another imei with Z3X.

No singleimage.bin is good, but the programmer is not so it doesnt work, make peace guys this device is not popular and there will probably never be a blankflash at this point your best bet is JTAG or toss it in the trash :D

I shared that from vache source, but the programmer is not good so it wont flash.

Vache is not responding, looks like he is away, the singleimage.bin he shared with me is 8937 but it appears that programmer is not correct, bad thing is that these programmers need to be signed to be used with the phone, i guess unless moto releases there, all these devices will remain bricks...

Hi guys, i have blankflash.zip provided by vache from G5+ forum, the singleimage.bin is 8937 for our board and it passes, but programmer.bin is not correct so it wont load, here it is if someone wants to experiment: https://www.sendspace.com/file/9jvu1p If you are on windows 10 do...

Yes and this is G5 forum.

Most guys here bricked their G5s :D

TheFixItMan I am back with more findings regarding singleimage.bin, if you open any phone singleimage.bin and Cedric bootloader.img you will see almost same structure, there is manifest in header that says: name="MSM8937" There are some lines missing from bootloader.img that are present in...

TheFixItMan I also found out that the singleimage.bin you shared as a fix from first post is in fact "MSM8952" so the guy that shared it is teasing us, you can edit singleimage.bin files in notepad or notepad++ there is manifest in the header that says "MSM8952". So we can give up on that one.

This one is not working, do you by any chance have any MSM8937 singleimage.bin from any other phone for me to try?

TheFixItMan takoa Ok guys i discovered something new, while on windows 10 with driver signing enforcement enabled you WILL get error opening single image, however when you disable it "run cmd as admin" then type: bcdedit.exe /set nointegritychecks on After that restart your PC and try the bat...

He explained the process to me, he said he used JTAG over usb (makes no sense to me), so i hoped if i manage to fix it fully i could root and dump something he used, but i bricked it again. I found some things in cracked version of boxes from gsmhosting but it doesnt work and i am not allowed to...

I am not sure, i think that the guy in store managed to JTAG bootloader ver 24 but it was not able to validate boot.img thefore no boot so i was stuck at bootloader, after that i flashed v25 and still same thing, then tried to flash v23 and bricked it to qualcomm 9008 again, so its dead again...

Maybe the image is corrupted when you uploaded it, since it cant be opened.

TheFixItMan Tried with few other methods its not working for me at least, lets wait for someone else to test, i am on windows 10 x64.

Not working, I tried with and without battery, run as admin and normal, ran command manually too, every time this output: **** Log buffer [000001] 2018-04-26_20:18:03 **** [ 0.000] Opening device: \\.\COM3 [ 0.001] Detecting device [ 0.004] ...cpu.id = 79 (0x4f) [ 0.004] ...cpu.sn =...

Tried still same problem just this time it fails with gpt.bin, also the phone is totally bricked again so ... :)

I used JTAG flasher from GSM forum, but the thing is my bootloader used to be unlocked then after flash it went to locked status and CID was 0xDEAD, basically now i cant every fix it with jtag so its dead totally.

Cant, the bootloader i flashed was locked, and to flash twrp you need to unlock it wich i cant because of no oem unlock.

Still cant flash it, however i tried your firmware, flashed bootloader, now version changed from B8.23 to B8.25, but when i get to fastboot flash boot boot.img i still get: sending 'boot' (16384 KB)... OKAY [ 20.642s] writing 'boot'... (bootloader) Image boot failed validation (bootloader)...

I tryed that and get the same message as soon as it gets to boot.img "Preflash Validation Failed", i flashed 7.1 android bootloader on it, it looks like i am flashing older roms and i cant find latest rom download, tryed version 93 same thing?

This method is derived from reverse engeneering an exploit from a hardware box released on gsm forums i cant share it now, not until i have full method with system booting then i will share.

I cant flash stock i tryed from that page "Moto G5 - Nov 2017 firmware NPP25.137-93", when it gets to boot/recovery imgs it says: Method i tryed to get bootloader.img back is related to dissasembly of the phone and shorting emmc pins to get unrestricted access to the memory and while mounted...

Hello guys, I have found a way to restore hard brick "flashing led", but the problem is that now i have device with erased system and locked bootloader, cant flash anything due to "(bootloader) Preflash validation failed", tryed to download few firmware files to try but nothing can be flashed...

I tryed this multiple times, doesnt work.

Hello, I need to spy on my sons phone, bare in mind that i am legally fully able to do this, so please don't bash this thread. What i need is software/apk recommendation from you guys on what software is the best. He is tech savvy (but i am rooting and installing custom software on his device)...

Is it possible to hex edit blankflash files for partition index or they are signed? Are you allowed to make this discussion since you work for moto, can we ask for more :) ? Also do you know anything related to loading bootloader images to phone with some other way except blankflash I am aware...

I don't think that will work, cedric have all those functions disabled, also there is no need to follow that tutorial to get full dump img as its 16/2GB, only first 160mb are needed they contain bootloader, kernel and recovery at start of the emmc, so you can use loader.img someone posted above...

Yes same with my phone.

These .img files should boot bootloader directly from SDCard but it seems thar Cedric does not support this feature, so only way is JTAG and non updated blank-flash file.

I think this battery is OEM i ordered it and will try: https://www.ebay.com/itm/New-Original-BL-T9-Battery-For-LG-Google-Nexus-5-D820-D821-2300mAh-3-8V-8-74Wh/292226321718?ssPageName=STRK%3AMEBIDX%3AIT&var=591145508905&_trksid=p2057872.m2749.l2649 Since it has all the right data i think its...

Motorola sucks bad, Google and Xiaomi for instance have tools to recover dead bootloader eg. "Mi Flash", motorola gave developers easy bootloader unlock but no way to recover it, whats the point then, either make it recoverable or make it non erasable easily.

This is not related to driver, bot Qualcomm and Quectel 9008 drivers work and allow communication with the phone, patch level is too high so blankflash files dont pass and dont allow bootloader to be flashed. Only solution is JTAG or motherboard replacement if patch level is higher than one in...

Np, i took the phone to service center for JTAG, hopefully they will manage to fix it somehow :)

Every partition, but its ok now i sent the phone for jtag and well see if they can fix it :)

Ok guys new update, Cubico provided me with Loader.img -73 firmware, so far tried nothing changed, device still showing no sign of life except Qualcomm 9008... not booting or anything, if someone have 93 bootloader Loader.img dump i can try that too, if not i will take it to shop to someone with...

Cubico We can try, but i don't think it will work tho. Please upload and we will see i guess :)

MotoJunkie01 Hi, I was wondering why is it so easy on Moto devices to corrupt bootloader, for instace take samsung and its download mode that thing is a beast and it is so hard to destroy or nexus bl or xiaomi, they have MiFlash so even if it gets corrupted you can revive it. Why other...

No one willing to give away five minutes to help? :) I will make it worthwhile since my phone is dead i am sure there is a change to fix it with this, and will make tutorial for community :)

Hey i have bricked bootloader but i think other partitions are alive, can you help me with this: https://forum.xda-developers.com/g5/help/bootloader-deleted-hard-brick-help-t3754608 If i make it go live i will give you my /persist, thanks.

Guys i am trying to make unbrick method for Cedric, does anyone have 5 minutes of time to make loader.img, all you have to do is to be on firmware .93, bl unlocked and rooted. Type in terminal emulator dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960 And upload me that...

Tryed, not applicable for this mode, i need blankflash or some other method, i still have yet to try sdcard flash, but i am loosing hope here, might just accept that its totally bricked and thats it, oh well moving on i guess.

Hello guys, I have cedric, bootloader unlocked, rooted, etc.. I used some SDcard format app and selected wrong storage to format emmcblk0, so i formated entire phone, now in device manager its detected as "Quectel QDLoader 9008 " cannot power it on as well i think bootloader is bricked, i tryed...

Its internal memory so if its slow, then you will have slow camera taking images, or slow instant messaging apps such as viber pulling info from memory. I would advise you tu use atleast class 10, they are cheap and are better than class 4 or less.

Is your rom doing something to the modem? After i installed it and restored back my stock backup i have problems with calls that happen in other nougat roms, like when you call someone its silent but he can receive call etc...?

What is the status of this rom, stable? Are there random reboots... etc?