Database Develop

Touchscreen not working after flash, Ali Moto G6

Hello,
I followed the steps to install TWRP correctly, and then flashed ALI_RETAIL_9.0_PPSS29.55-24-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC that i got from https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/ and the process worked correctly. However, I foolishly thought I had flashed the wrong build and then flashed ALI_OPS27.82-19-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC that I got from https://forum.xda-developers.com/moto-g6/how-to/stock-firmware-moto-g6-t3792292
Now my phone boots fine, but the touchscreen does not work at all, neither in TWRP nor when booted into the firmware. Is there any hope?
Model is ali XT1925-6
If I burnt out a part, what parts are they and how difficult will it be to replace them?
Edit: I now realize that my carrier channel is retus, and I installed retail. However, the touchscreen did not fail on that rom

II firmware that you flashed you only linked to the whole thread, you didn't show the exact firmware that you tried to flash.
Why not just try the one for your firmware and your carrier from mirrors.lolinet.com
The firmware used first time should be fine if it works

madbat99 said:
II firmware that you flashed you only linked to the whole thread, you didn't show the exact firmware that you tried to flash.
Why not just try the one for your firmware and your carrier from mirrors.lolinet.com
The firmware used first time should be fine if it works
Click to expand...
Click to collapse
Thanks for your response,
I installed androidfilehost.com/?fid=818222786056029922 from the second thread.
I tried reflashing the first rom, but the touchscreen does not work there either. I've just downloaded and installed the correct rom, still no dice
Is it possible that the second rom burnt my digitizer?
Edit: the fingerprint sensor doesn't respond on the setup screen either, although I'm not sure if thats because it isn't working or it doesnt do anything on the setup screen

I think part of the problem may be that I cannot wipe system when installing a new rom; using adb shell twrp wipe system returns Error with wipe command value 'system', and I cannot access the touchscreen to do it via the UI. Are there any other ways to wipe system? fastboot erase system -w fails with Permission denied
Edit: I was able to erase system as well as data, cache, and dalvik before flashing. Still no change
The script I'm using to flash roms is
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash boot boot.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 system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot oem fb_mode_clear
fastboot reboot

fisher_1 said:
I think part of the problem may be that I cannot wipe system when installing a new rom; using adb shell twrp wipe system returns Error with wipe command value 'system', and I cannot access the touchscreen to do it via the UI. Are there any other ways to wipe system? fastboot erase system -w fails with Permission denied
Edit: I was able to erase system as well as data, cache, and dalvik before flashing. Still no change
The script I'm using to flash roms is
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash boot boot.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 system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Download the "newest" firmware for your device with matching SKU and software channel. Don't use someone else's script. The commands for flashing the firmware are in the flashfile.xml in the firmware zip. Extract it and check the commands. You can use XML to batch program to create your own batch script if you must use a script.
It's unlikely that flashing a firmware broke your hardware.
If it's software related, flashing the correct firmware should fix it.
If it's a hardware problem, then it won't. But official firmware isn't likely to cause hardware failure
The firmware package in the first post of that thread is pretty old.

Unfortunately it still is not working. I used the commands from flashfile.xml and flashed XT1925-6_ALI_RETUS_9.0_PPSS29.55-24-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC, the correct firmware, but nothing has changed.
On a side note, when I flash a file, I get the message (bootloader) is-logical: (partitionName) not found, althought I get an OKAY response so I'm assuming it flashes correctly.

I'm having the same issue, got the phone on July 12 and immediately started the unlocking/rooting process (that's what I bought the device for) following dejello's guide. Everything went perfect, phone was working all right for 2 days then on Monday morning after using the device for a while, I placed it in an upper pocket of my backpack drove home and next thing I know the touch screen isn't working, not even on TWRP . Hardware damage seems very unlikely on my case. I did a factory reset using a mouse, but I haven't been able to flash stock back. I'll try that later today and see what happens.
UPDATE: It was a hardware issue. Came home and flashed back to stock, still had no touch response. Since my software troubleshoot had no success I decided to give hardware a shot. I followed this video to disassemble the phone. I started tweaking the digitizer connector. With the phone still disassembled I turned it on and still no touch. Disconnected it again and blew some air with a hair dryer to it trying to remove any debris, connected it again and still no touch. Repeated the process a couple times and eventually the screen was responsive again. I think this specific device came with something loose or some dirt on it.

Cant'n Boting

I flash ROM using twrp, then I format everything and the system, then I reboot, but instead can't get into twrp, it finally gets stuck at fastboot! what's the solution

ayen2904 said:
I flash ROM using twrp, then I format everything and the system, then I reboot, but instead can't get into twrp, it finally gets stuck at fastboot! what's the solution
Click to expand...
Click to collapse
Follow the instruction on the following page:
"You can try to use the instructions given on this page https://forum.xda-developers.com/red...t3940057/page2. Extract all img and bin files from the Global ROM and place them into the folder where the "cmd-here.exe" is. Also you need "system.img" you can download that here https://drive.google.com/drive/folde...pQ1KK1LjysSfYm, but dont download the other files they might be the Chinese files.
After you extracted the img and bin files and placed them into the folder where the cmd is placed connect your phone to the computer, open the cmd exe and run the commands
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot bootloader
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot flash dsp dspso.bin
fastboot oem nubia_lock NUBIA_NX629J
fastboot reboot
After all that you should be able to go into recovery mode through fastboot mode if not then try and flash dtbo.img and vbmeta.img in the line of commands so for example "fastboot flash dtbo dtbo.img" and "fastboot flash vbmeta vbmeta.img" looking something like this...
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot bootloader
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
fastboot flash modem NON-HLOS.bin
fastboot flash dsp dspso.bin
fastboot flash system system.img
fastboot reboot
This was the line of commands I used when my recovery mode was corrupt and somehow worked
I hope this helps and let me know if it worked or if the issue is still there. Also the forum has several posts on this matter and they might have the answer you are looking for as it helped me with this issue. Good Luck!"

HELP!! My red magic 3 is in bootloader bootloop

I flash the Chinese ROM to the global version of red magic3
And entered the boot loader boot loop
How to fix it?
If you try to flash system.img, tell me how to fix the problem that fastboot.exe will stop working.
I saw other threads, but I didn't know well because I was so nervous in English

yajujann said:
I flash the Chinese ROM to the global version of red magic3
And entered the boot loader boot loop
How to fix it?
If you try to flash system.img, tell me how to fix the problem that fastboot.exe will stop working.
I saw other threads, but I didn't know well because I was so nervous in English
Click to expand...
Click to collapse
I am Japanese High school student . So I can't understand English well

kelv55l said:
(skipped message) ...
After you extracted the img and bin files and placed them into the folder where the cmd is placed connect your phone to the computer, open the cmd exe and run the commands
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot bootloader
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot flash dsp dspso.bin
fastboot oem nubia_lock NUBIA_NX629J
fastboot reboot
After all that you should be able to go into recovery mode through fastboot mode if not then try and flash dtbo.img and vbmeta.img in the line of commands so for example "fastboot flash dtbo dtbo.img" and "fastboot flash vbmeta vbmeta.img" looking something like this...
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot bootloader
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
fastboot flash modem NON-HLOS.bin
fastboot flash dsp dspso.bin
fastboot flash system system.img
fastboot reboot
This was the line of commands I used when my recovery mode was corrupt and somehow worked
I hope this helps and let me know if it worked or if the issue is still there. Also the forum has several posts on this matter and they might have the answer you are looking for as it helped me with this issue. Good Luck!
Click to expand...
Click to collapse
Please try this kelv55l's suggestion

into fastboot
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash recovery recovery.img
then into recovery wipe data
you can get recovery.img from update.zip

Hello i have no system.img ...
i can not find them in the NX629J_Z69_EN_WPJ0O_V210.zip
Can you Help me or can you me send the system.img
Please
My Phone have a bootloob in the fastboot mode...
"Hello, I have a problem. I flash twrp on my phone and wanted to flash from CN to EU version. I deleted the system and wanted to select the EU zip file. it did not work. That's why I restarted the phone. Now the phone starts only in the bootloader and the phone is no longer recognized by the PC although I have installed all drivers. Is there a special software that recognizes the phone or is the phone now forever defect? "
Thanks for the Help!
https://imgur.com/a/TRAJp9I

here you have the files and commands necessary to fix it. use the last sdk
https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page7

Thanks for the Answer!
I have a Problem with the Flash system.img
I have Uploadet a Sreenshoot!
https://imgur.com/a/b3Vdi9N

try fastboot flash -S 500M system system.img
if it wont work
fastboot flash -S 100M system system.img

ok i make
---------- Post added at 12:40 AM ---------- Previous post was at 12:27 AM ----------
tattoomees said:
try fastboot flash -S 500M system system.img
if it wont work
fastboot flash -S 100M system system.img
Click to expand...
Click to collapse
Holly !
THANKS MAN YOU ARE A HERO!!!!!
THANKS BROOO

Failed to verify Hab Image Boot

First im trying to reinstall stock firmware on a model XT1925-3, from a friend.
It was stuck at Moto Logo, i tried everything you could imagine to make it work. Nothing happens. The things I tried:
-It have locked bootloader (i cant unlock because i cant boot to "Allow OEM").
-Tried all 8 RETBR firmwares (https://mirrors.lolinet.com/firmware/moto/ali/official/RETBR/) and none worked.
-Trying the following commands:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash boot boot.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 system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot erase userdata
fastboot erase DDR
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot oem fb_mode_clear
fastboot reboot
It goes very well, but after restart, it backs to fastboot screen and cant boot.
-Tried another cable, tried another PC, tried another port
-Attached the screen it is now
If theres anything you can do to help me. I appreciated

There's nothing wrong with your cable, your PC or something else! Otherwise you can't even process the first the command in fastboot.
So first thing I would do is booting into recovery. Although it's the stock one it will be very useful to get detailed information in your case.
Once in fastboot mode use the Vol -/+ keys to navigate to reboot to recovery and press power. Then have a look at the logs provided by the recovery. There should be two different kinds of logs - the kernel log and the recovery.log. Choose kernel.log (maybe it's called last_dmsg.log or sth like that). It provides the most detailed information on Android and why you're stuck in a bootloop. Be aware that it has more than one page which will be shown up. Have a look at the left corner on the bottom. Don't expect to find the major error on the last lines, but somewhere in the last 150 lines.
That's one thing you can do.
Another advise is to give the repair tool a chance which is mentioned in your screenshot. This is a really good option in your case.
Good luck!!

i may have just bricked my phone, can someone help me?

when i try to repair it using the moto repair tool, it says failed, when i try to boot into android, it says to enter a password, ive never had a password, i dont know what to do, or even where to start to try to fix it. the bootloader is locked, and i dont know how to boot into the os... it says your phone has loaded a different operating system, then the id says bad key, can someone help?

Bad key shows up when your boot.img flashed is modified and the system is locked.
By enter password you mean the drawing dots or a numeric code?
Try using this software: https://support.lenovo.com/br/pt/downloads/ds101291-rescue-and-smart-assistant-lmsa
If it shows failed on it too then you need to reflash via cmd with exact same version ( locked bootloader wont let you flash a different version than exact one). Use fastboot getvar all and find the line with the version stating. then download and flash it.

mrsiri said:
Bad key shows up when your boot.img flashed is modified and the system is locked.
By enter password you mean the drawing dots or a numeric code?
Try using this software: https://support.lenovo.com/br/pt/downloads/ds101291-rescue-and-smart-assistant-lmsa
If it shows failed on it too then you need to reflash via cmd with exact same version ( locked bootloader wont let you flash a different version than exact one). Use fastboot getvar all and find the line with the version stating. then download and flash it.
Click to expand...
Click to collapse
by password, it says "To Start Android, Enter your device password"
also how would i go about flashing the exact version? ive never flashed something before

Look for ro.build.fingerprint after typing command: "fastboot getvar all"
Then download ROM via lolinet https://mirrors.lolinet.com/firmware/moto/ali/
and flash via typing these commands:
fastboot flash gpt PGPT
fastboot flash preloader preloader.bin
fastboot flash lk_a lk.img
fastboot flash tee_a tee.img
fastboot flash md1img_a md1img.img
fastboot erase nvdata
fastboot flash spmfw_a spmfw.img
fastboot flash scp_a scp.img
fastboot flash sspm_a sspm.img
fastboot flash cam_vpu1_a cam_vpu1.img
fastboot flash cam_vpu2_a cam_vpu2.img
fastboot flash cam_vpu3_a cam_vpu3.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtb_a dtb.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash system_b system_other.img_sparsechunk.1
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot erase metadata
fastboot reboot bootloader