I flashed LineageOS (for the Moto G4 Plus) onto my Moto G4 Plus (XT1644) using TeamWin (TWRP) and clicked reboot. It didn't boot, and instead went into a blank screen and the LED flashed. I can still enter back into FastBoot and Recovery. Please help me (am a noob)
Thanks!
I have the same problem
DragonHartX07 said:
I have the same problem
Click to expand...
Click to collapse
Hello. If you have this problem, follow the directions @ https://forum.xda-developers.com/showpost.php?p=67031808&postcount=4 and if you have XT1644, download firmware at http://www.filefactory.com/file/3t2...PJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip.
Hope this helps, wish you the best of luck with your soft-bricked device. Need any other help, I am happy to research for you.
~wz68XDA
Same problem man. It's been about 2 weeks with me. If you look closely its only the backlight which goes off after the boot and the LCD and touch is still on.
Please do look for a solution as i have found no solution to this problem. I've tried reflashing different roms and the stock firmware too, it comes on for a few mins after I flash stock firmware and the blacklight goes off after some time and the issue repeats after every boot. @wz68XDA
_Rushaan_ said:
Same problem man. It's been about 2 weeks with me. If you look closely its only the backlight which goes off after the boot and the LCD and touch is still on.
Please do look for a solution as i have found no solution to this problem. I've tried reflashing different roms and the stock firmware too, it comes on for a few mins after I flash stock firmware and the blacklight goes off after some time and the issue repeats after every boot. @wz68XDA
Click to expand...
Click to collapse
Have you tried flashing the complete stock ROM for your device? Did you follow the instructions in the link in my previous post, completely resetting the whole device, or did you flash it with TWRP/CWM? This will reset your bootloader, recovery, everything back to stock.
Also, do you have a picture of your device when this problem occurs?
Thanks,
wz68XDA
wz68XDA said:
Have you tried flashing the complete stock ROM for your device? Did you follow the instructions in the link in my previous post, completely resetting the whole device, or did you flash it with TWRP/CWM? This will reset your bootloader, recovery, everything back to stock.
Also, do you have a picture of your device when this problem occurs?
Thanks,
wz68XDA
Click to expand...
Click to collapse
I have tried flashing the complete stock rom for my XT1643 with "fastboot oem lock" but I noticed it never locked the bootloader no matter how many times I flashed the stock rom.
The phone won't even go into the bootloader now and the LED Flashes for a while when connected to a USB cable and then nothing, it won't come up or get recognized by the computer.
wz68XDA said:
I flashed LineageOS (for the Moto G4 Plus) onto my Moto G4 Plus (XT1644) using TeamWin (TWRP) and clicked reboot. It didn't boot, and instead went into a blank screen and the LED flashed. I can still enter back into FastBoot and Recovery. Please help me (am a noob)
Thanks!
Click to expand...
Click to collapse
After you flash a ROM, make sure you wipe the Cache/Dalvik before you reboot. And, in case something goes wrong, ALWAYS MAKE A BACKUP!!
And, LOS takes about 10 minutes after a flash for the first boot.
_Rushaan_ said:
I have tried flashing the complete stock rom for my XT1643 with "fastboot oem lock" but I noticed it never locked the bootloader no matter how many times I flashed the stock rom.
The phone won't even go into the bootloader now and the LED Flashes for a while when connected to a USB cable and then nothing, it won't come up or get recognized by the computer.
Click to expand...
Click to collapse
The instructions in my post do not indicate that you need to relock the bootloader. There are separate instructions for that. Flashing the stock ROM will not relock your devices bootloader.
wz68XDA said:
The instructions in my post do not indicate that you need to relock the bootloader. There are separate instructions for that. Flashing the stock ROM will not relock your devices bootloader.
Click to expand...
Click to collapse
I get you, but I never got to try your instructions because my phone won't get into the bootloader now.
I followed the instructions on this thread ( https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695 ) when it was working. I have an XT1643.
_Rushaan_ said:
I get you, but I never got to try your instructions because my phone won't get into the bootloader now.
I followed the instructions on this thread ( https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695 ) when it was working. I have an XT1643.
Click to expand...
Click to collapse
What OS were you on before, btw - was it Nougat? Try holding the power button down for 2-3 minutes, see if a reset will cause it to boot.
Does your computer still see your device as a Qualcomm HSB BULK or USB 9008 or something similar? Perhaps try https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23
If the above doesn't work, you may have to take your device to a service centre.
Also, as I understand, you need the latest firmwares to lock your device, which would be flashing the latest Nougat build.
As for your original backlight issue, it does appear to be a hardware issue if it's persisting across ROMs.
_Rushaan_ said:
I get you, but I never got to try your instructions because my phone won't get into the bootloader now.
I followed the instructions on this thread ( https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695 ) when it was working. I have an XT1643.
Click to expand...
Click to collapse
So you are unable to get into fastboot? Then, unfortunately, I believe yout device is hard bricked.
echo92 said:
What OS were you on before, btw - was it Nougat? Try holding the power button down for 2-3 minutes, see if a reset will cause it to boot.
Does your computer still see your device as a Qualcomm HSB BULK or USB 9008 or something similar? Perhaps try https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23
If the above doesn't work, you may have to take your device to a service centre.
Also, as I understand, you need the latest firmwares to lock your device, which would be flashing the latest Nougat build.
As for your original backlight issue, it does appear to be a hardware issue if it's persisting across ROMs.
Click to expand...
Click to collapse
I was on Resurrection remix when the issue first occurred, I have since then tried jumping many roms, with the backlight working for a few mins before crashing but even flashing the stock rom didn't help.
I did flash the latest firmware but now that it won't go into the bootloader I'm assuming its a paperweight now since it won't even get recognized by the computer, no it doesn't show anything when connected.
I'll still give service center a try and hope they don't find out my bootloader was unlocked and not honor the warranty.
Thanks/
---------- Post added at 08:20 PM ---------- Previous post was at 08:19 PM ----------
wz68XDA said:
So you are unable to get into fastboot? Then, unfortunately, I believe yout device is hard bricked.
Click to expand...
Click to collapse
I'll give the service center a go.
Thanks a lot
---------- Post added at 08:26 PM ---------- Previous post was at 08:20 PM ----------
@wz68XDA
@echo92
EDIT: I just plugged in the device to the computer and pressed the powerbutton and the screen came on and its now on a "Installing system upate" screen. I remember authorizing to install an OTA before the phone went full dead. I guess I'll be able to get into the bootloader now.
Could you please instruct me on how to lock the bootloader again so I can claim warranty at the service center?
It says " SOFTWARE STATUS: OFFICIAL" But still shows the bootloader unlocked warning with ID:bad
Thanks
_Rushaan_ said:
I was on Resurrection remix when the issue first occurred, I have since then tried jumping many roms, with the backlight working for a few mins before crashing but even flashing the stock rom didn't help.
I did flash the latest firmware but now that it won't go into the bootloader I'm assuming its a paperweight now since it won't even get recognized by the computer, no it doesn't show anything when connected.
I'll still give service center a try and hope they don't find out my bootloader was unlocked and not honor the warranty.
Thanks/
---------- Post added at 08:20 PM ---------- Previous post was at 08:19 PM ----------
I'll give the service center a go.
Thanks a lot
---------- Post added at 08:26 PM ---------- Previous post was at 08:20 PM ----------
@wz68XDA
@echo92
EDIT: I just plugged in the device to the computer and pressed the powerbutton and the screen came on and its now on a "Installing system upate" screen. I remember authorizing to install an OTA before the phone went full dead. I guess I'll be able to get into the bootloader now.
Could you please instruct me on how to lock the bootloader again so I can claim warranty at the service center?
It says " SOFTWARE STATUS: OFFICIAL" But still shows the bootloader unlocked warning with ID:bad
Thanks
Click to expand...
Click to collapse
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/91987/p/1449,8620
You can send a support ticket to Motorola
and locking bootloader will NOT restore warranty
Good Luck,
wz68XDA
_Rushaan_ said:
I was on Resurrection remix when the issue first occurred, I have since then tried jumping many roms, with the backlight working for a few mins before crashing but even flashing the stock rom didn't help.
I did flash the latest firmware but now that it won't go into the bootloader I'm assuming its a paperweight now since it won't even get recognized by the computer, no it doesn't show anything when connected.
I'll still give service center a try and hope they don't find out my bootloader was unlocked and not honor the warranty.
Thanks/
---------- Post added at 08:20 PM ---------- Previous post was at 08:19 PM ----------
I'll give the service center a go.
Thanks a lot
---------- Post added at 08:26 PM ---------- Previous post was at 08:20 PM ----------
@wz68XDA
@echo92
EDIT: I just plugged in the device to the computer and pressed the powerbutton and the screen came on and its now on a "Installing system upate" screen. I remember authorizing to install an OTA before the phone went full dead. I guess I'll be able to get into the bootloader now.
Could you please instruct me on how to lock the bootloader again so I can claim warranty at the service center?
It says " SOFTWARE STATUS: OFFICIAL" But still shows the bootloader unlocked warning with ID:bad
Thanks
Click to expand...
Click to collapse
Hmm, now it's powering on (and hopefully now charged), would you be willing to try re-flashing the latest firmware (https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369), see if you can get your system back up and running. Also, in that guide, there'll be instructions on how to re-lock your bootloader (and possibly mask the bootloader warning). It's still however up to the service centre as to whether they'll check your warranty (as on record it's been voided by issuing the unlock code) or whether they just look at the receipts. Good luck either way though!
Related
so i went through the steps indicated in the XDA thread linked below, and having done this before with my other samsung (s4) the steps seemed familiar enough... except that after flashing the boot image with ODIN, instead of rebooting the phone gives me the following error message:
"Bootloader exception
RST_STAT = 0x10000000
....more stuff here....
Exception: do_handler_sync: unkown (esr: 0x2000000=
....now the phone only boots up to the point where it shows that error message! it doesn´t even switch off... all i can do is reboot with the vol down + home+ power combo but then i return to that screen...
is the phone bricked for good or is there a way out of this?
Thx
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
platypus78 said:
so i went through the steps indicated in the XDA thread linked below, and having done this before with my other samsung (s4) the steps seemed familiar enough... except that after flashing the boot image with ODIN, instead of rebooting the phone gives me the following error message:
"Bootloader exception
RST_STAT = 0x10000000
....more stuff here....
Exception: do_handler_sync: unkown (esr: 0x2000000=
....now the phone only boots up to the point where it shows that error message! it doesn´t even switch off... all i can do is reboot with the vol down + home+ power combo but then i return to that screen...
is the phone bricked for good or is there a way out of this?
Thx
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
Click to expand...
Click to collapse
Are you able to get into download mode? By pressing volume down+power+home button? If yes then flashing latest stock firmware using odin may help you to overcome this issue..Or you can try samaung smart switch application on your pc and emergency recovery software can be done..If you need any help regarding this two..You can ask
your problem will be solved if you manage to put in download mode and flash stock firmware with odin, if any error occurs during flash you may need to use pit file
The problem is that right now i cannot get back into download mode... I cannot even switch the device off!!!
All i can do is reboot in the download mode (down+home+power) but instead of going into download mode it immediately displays the same message i wrote above...
Seems like a boot loop only working in download mode... Ive been reading around but cannot get any similar error message...
@DroidHackeR - i assume that to use samsung smartswitch i still would need to into dowload mode, if not fully boot the mobile right?
8 month old guide... a little bit outdated..
I have a question... Did you update the phone to Android 7 AKA Nougat?
If that's true you just did the wrong thing to attempt a Downgrade which usually ends pretty bad in newer phones.
swith off your phone and plug usb in,does windows recognize the phone? or a modem or something?
---------- Post added at 08:46 PM ---------- Previous post was at 08:45 PM ----------
i guess you have a corrupt bootloader file or repartition thicked or something
demon2112 said:
swith off your phone and plug usb in,does windows recognize the phone? or a modem or something?
---------- Post added at 08:46 PM ---------- Previous post was at 08:45 PM ----------
i guess you have a corrupt bootloader file or repartition thicked or something
Click to expand...
Click to collapse
If Re-partition is ticked he most likely wont be able to power up at all.... most likely that the bootloader he flashed is older than the one that was on the phone...
---------- Post added at 21:14 ---------- Previous post was at 21:10 ----------
I think that a last ditch chance would be disconnecting the battery of the phone and reattach it(Opening back cover = No longer water-resistant) or wait for it to shutdown due lack of charge and then try to start it in download mode...
Right... The phone was obviously not upgraded to nougat (the whole point in my trying this in the first place)... The thing is, although the guide is old i saw recent posts from people rooting with this method...
I have no choice but to wait and see if after the battery runs out anything will change, but i song have a good feeling about it... Damn...
flashing wrong bootloader will make your device turn to an expensive stone paper weigh. if your device is not 930x... then that is what happen to it.
the bootloader was the right one (at least it was intended for my model) - god knows what happened, as i´m not exactly new to this and have never had a single issue before...
anyways, more to the point: after battery discharging it seems to be going back into download mode - now what do you recommend? i am downloading an original rom from sammobile, should i just flash that with odin? i´m not so sure anymore which bootloader i should attempt to download :/
EDIT: so after flashing the ROM from sammobile everything seems to be back on track... looks like i dodged a bullet this time, but it was out of purely dumb luck :/
thanks to all for your feedback, much appreciated!
platypus78 said:
the bootloader was the right one (at least it was intended for my model) - god knows what happened, as i´m not exactly new to this and have never had a single issue before...
anyways, more to the point: after battery discharging it seems to be going back into download mode - now what do you recommend? i am downloading an original rom from sammobile, should i just flash that with odin? i´m not so sure anymore which bootloader i should attempt to download :/
EDIT: so after flashing the ROM from sammobile everything seems to be back on track... looks like i dodged a bullet this time, but it was out of purely dumb luck :/
thanks to all for your feedback, much appreciated!
Click to expand...
Click to collapse
Nice to hear that you recovered from the "semi-hardbrick", anyways enjoy your "new" phone? xD
Hey guys,
My XZ Premium updated to 9.0. Since then I started to have many problems.
Yesterday a messagage appeared: Your phone is corrupt, it may not work properly. It can't be trusted.
Hours later it frozed and turned off. Now it's not responding to anything. The led isn't working and the device manager shows it as SOMC Flash Device.
The comands pressing volume buttons while I connect the USB cable are not working either.
Can I save it? I bought it three months ago :crying:
First, try to repair it with Sony Companion and Newflasher. if those not work return it to your dealer or ask for a repair under warranty.
Styler911 said:
First, try to repair it with Sony Companion and Newflasher. if those not work return it to your dealer or ask for a repair under warranty.
Click to expand...
Click to collapse
I alredy tried. It's not working. I bought in a different country that I live now. I can't use the local warranty.
first of all try a factory reset if the phone not modified.
If you have TWRP installed, wipe the phone out of TWRP.
Probably water in usb port then charging caused it
it cant hurt to try have you tried pressing volume up and power together until you get 3 vibrations?
mad0701 said:
first of all try a factory reset if the phone not modified.
If you have TWRP installed, wipe the phone out of TWRP.
Click to expand...
Click to collapse
I don't have the TWRP installed. The device is not responing via PC.:crying:
stipi69 said:
it cant hurt to try have you tried pressing volume up and power together until you get 3 vibrations?
Click to expand...
Click to collapse
The device is not responding to any command that I try...
amakuramio said:
Probably water in usb port then charging caused it
Click to expand...
Click to collapse
It never get wet, and when it does I make sure that no water remains....
Can you see your phone in the Systemcontrol? If yes: does the device is valid or does the device has an Akklamation Mark "!" beside? Maybe you must install the fastboot driver?
---------- Post added at 08:42 AM ---------- Previous post was at 08:37 AM ----------
on other hand:
try the Flash tool (Version 0.9.2.5.0) with a ftf file.
With this you can also change the version of country, remove a branding or viversa....
You will find links to the tool and ftf here in the forum
mad0701 said:
Can you see your phone in the Systemcontrol? If yes: does the device is valid or does the device has an Akklamation Mark "!" beside? Maybe you must install the fastboot driver?
---------- Post added at 08:42 AM ---------- Previous post was at 08:37 AM ----------
on other hand:
try the Flash tool (Version 0.9.2.5.0) with a ftf file.
With this you can also change the version of country, remove a branding or viversa....
You will find links to the tool and ftf here in the forum
Click to expand...
Click to collapse
It only appears as SOMC Flash Device. The ADB or Flash Tools can't get access to the internal memory. I know there's a way to access the internal memory. Just don't know which one yet.
It looks like a coincidence. Hardware not be working may be the real issue.
If you find a knowledgeable repair shop, they can clear your flash and install the original Sony shipped OS for a little money. Most of the time this is done from the USB after a factory reset explained by others here. However, if the USB port is not working then accessing the flash needs opening the unit which will cost you.
And then if the hardware has failed, none of this would help anyway.
What's happen, if you press for 6 Sec or longer Power and Volume up together?
please, my nokia 5 TA 1024 got stuck in a bootloop after a system update. i tried resetting from the recovery mode, but it keeps saying "failed to find device for partition system". i tried flashing with a rom i found online but an error keeps poping up at a point in the flashing process.(i used OST for flashing). i looked into that and i found out that i have to unlock the bootloader. but since the phone cant actually boot, i dont know how to unlock it. please help.:crying:
havardgyasi said:
please, my nokia 5 TA 1024 got stuck in a bootloop after a system update. i tried resetting from the recovery mode, but it keeps saying "failed to find device for partition system". i tried flashing with a rom i found online but an error keeps poping up at a point in the flashing process.(i used OST for flashing). i looked into that and i found out that i have to unlock the bootloader. but since the phone cant actually boot, i dont know how to unlock it. please help.:crying:
Click to expand...
Click to collapse
Got the same problem months ago by an upgrade from oreo to pie. Nothing worked except "fastboot reboot bootloader" from terminal followed by pluged in the phone.
It was not possible for me to do more things. Could not solve the problem until I get an EDL-cable. Then found out that the upgrade had damaged the bootloader. Could then flash it with the latest OST, the EDL-cable and the 7.1 Rom.
Spartan42 said:
Got the same problem months ago by an upgrade from oreo to pie. Nothing worked except "fastboot reboot bootloader" from terminal followed by pluged in the phone.
It was not possible for me to do more things. Could not solve the problem until I get an EDL-cable. Then found out that the upgrade had damaged the bootloader. Could then flash it with the latest OST, the EDL-cable and the 7.1 Rom.
Click to expand...
Click to collapse
ohk. i managed to get the cable. can you please walk me through the process of getting into EDL mode?
havardgyasi said:
ohk. i managed to get the cable. can you please walk me through the process of getting into EDL mode?
Click to expand...
Click to collapse
There are a bunch of instructions how to use the Cable in the right order.
It is important that the driver in Windows is the right one. Most of the time (in mine device) the EDL-mode was detected incorrectly and the driver has to be changed manually.
It's been a while, so I do not remember all the steps. I'm sorry. I've searched the Nokia 5 and 6 Forums. That should answer most of the questions. The rest was try and error.
Good Luck
---------- Post added at 01:37 AM ---------- Previous post was at 01:33 AM ----------
https://forum.xda-developers.com/no...p-unbricking-ny-nokia-6-t3947148/post79889899
https://forum.xda-developers.com/no...p-unbricking-ny-nokia-6-t3947148/post79889899
Try this one for the drivers.
Hello people of XDA.
Can someone help me please?
I woke up this morning only to find out that my phone won't turn on.
There's 75% left in the battery before I went to sleep.
I tried pressing and holding the power button but it won't turn on.
I also tried charging but the LED is blinking red.
Any solution? TIA
UPDATE:
After more than a month (because of quarantine/lockdown), I finally had my phone checked and repaired. It turns out it's a hardware problem: POWER SUPPLY.
Can you go into recovery mode? If yes, clean flash the rom otherwise use qfil tool to restore your phone
try to plug charger and check if battery is low even if you left it at 75% before you sleep, then try press and hold power button until it boots
otherwise reboot to recovery and fastboot - from here you can do the steps to recover your data or format the phone
Here is the same problem but in the morning i saw my phone in recovery mode..I tried all the possible solution :
1.Flashing fastboot rom through adb
2.Flashing firware through qfill tool
Better to mentioned that above 2 flash procedure were successful bt in the end of all successful flashing my phone booted into again recovery mode instead of system..
So,if there any other solution please help me..Its 48hours i'm working on it bt in the end i
get nothing but failure..!
---------- Post added at 08:38 PM ---------- Previous post was at 08:35 PM ----------
swarup16 said:
Here is the same problem but in the morning i saw my phone in recovery mode..I tried all the possible solution :
1.Flashing fastboot rom through adb
2.Flashing firware through qfill tool
Better to mentioned that above 2 flash procedure were successful bt in the end of all successful flashing my phone booted into again recovery mode instead of system..
So,if there any other solution please help me..Its 48hours i'm working on it bt in the end i
get nothing but failure..!
Click to expand...
Click to collapse
:crying:
Thank you for your replies.
My phone CANNOT BOOT to recovery or fastboot so I can't use QFIL.
I think the problem is the battery because I tried charging for hours but the charger is not hot to the touch. THE LED IS JUST BLINKING RED.
I will have it replaced after our community quarantine.
Random Member said:
Thank you for your replies.
My phone CANNOT BOOT to recovery or fastboot so I can't use QFIL.
I think the problem is the battery because I tried charging for hours but the charger is not hot to the touch. THE LED IS JUST BLINKING RED.
I will have it replaced after our community quarantine.
Click to expand...
Click to collapse
try qfil
---------- Post added at 05:27 PM ---------- Previous post was at 05:25 PM ----------
Random Member said:
Thank you for your replies.
My phone CANNOT BOOT to recovery or fastboot so I can't use QFIL.
I think the problem is the battery because I tried charging for hours but the charger is not hot to the touch. THE LED IS JUST BLINKING RED.
I will have it replaced after our community quarantine.
Click to expand...
Click to collapse
qfil doesnt require recovery or fastboot mode.
press v+ and V- button at a time and connect data cable.
Note: qfil drivers must be installed
mr.willy123 said:
try qfil
---------- Post added at 05:27 PM ---------- Previous post was at 05:25 PM ----------
qfil doesnt require recovery or fastboot mode.
press v+ and V- button at a time and connect data cable.
Note: qfil drivers must be installed
Click to expand...
Click to collapse
How would you know if it's working?
Do you have Telegram?
Here's what I've done:
1. Installed Qualcomm drivers for Windows.
2. Downloaded/installed QFIL.
3. Launched QFIL.
4. Press vol + and vol - at the same time and connected data cable.
5. QFIL still shows "NO PORT AVAILABLE."
mr.willy123 said:
try qfil
---------- Post added at 05:27 PM ---------- Previous post was at 05:25 PM ----------
qfil doesnt require recovery or fastboot mode.
press v+ and V- button at a time and connect data cable.
Note: qfil drivers must be installed
Click to expand...
Click to collapse
Problem still not fixed. I'm sure "USB debugging" is enabled on my phone.
When I charge or connect my phone via USB, there is no charging animation.
black screen and vibration ??
mr.willy123 said:
try qfil
---------- Post added at 05:27 PM ---------- Previous post was at 05:25 PM ----------
qfil doesnt require recovery or fastboot mode.
press v+ and V- button at a time and connect data cable.
Note: qfil drivers must be installed
Click to expand...
Click to collapse
soufkas said:
black screen and vibration ??
Click to expand...
Click to collapse
no vibration and battery animation when plugging
soufkas said:
black screen and vibration ??
Click to expand...
Click to collapse
no vibration and battery animation when plugging in the charger
same
Random Member said:
no vibration and battery animation when plugging in the charger
Click to expand...
Click to collapse
have the same problem any update on how to solve this XD
My asus zenfone max pro m1 has not been booting since the april 21st update.
It boots completely, asks for pattern to decrypt storage and irrespective of whether or not i enter the pattern, it reboots. Looks like some system services are failing after boot and hence i need to wipe or clean flash the system partition.
Situation:
This is my dad's phone and it wasn't tampered with at all. Unfortunately boot loader is locked and usb debugging is off.
None of my 2 laptops detect it in fastboot or adb in windows and linux. I've installed proper drivers but it doesn't even show up in device manager as unknown or whatever.
It normally enters fastboot and recovery modes.
I did the root integrity check from recovery and it reported 92 files missing and 90 unknown files.
What i tried:
Reinstalling the same update through recovery (makes no difference)
Installing older updates ( recovery doesn't allow)
Factory reset through recovery (makes no difference)
flashing via fastboot (fastboot doesn't detect)
The only thing i did not try is qfil and I'm not doing that because a lot of people have reported losing their IMEI and other hardware information.
Also, I couldn't find a stock qfil firmware they were stock based made by other people.
Asus's update broke the phone. But I don't see a lot of people posting about it. I could use some help.
Thank you
---------- Post added at 04:40 PM ---------- Previous post was at 04:36 PM ----------
axit50 said:
Can you go into recovery mode? If yes, clean flash the rom otherwise use qfil tool to restore your phone
Click to expand...
Click to collapse
The update messed up its own system files. Clean flash means wiping partition and installing again.
How can we do that from stock recovery where it doesn't wipe /system ?
All installations from recovery are dirty.
dev.kasibhatla said:
My asus zenfone max pro m1 has not been booting since the april 21st update.
It boots completely, asks for pattern to decrypt storage and irrespective of whether or not i enter the pattern, it reboots. Looks like some system services are failing after boot and hence i need to wipe or clean flash the system partition.
Situation:
This is my dad's phone and it wasn't tampered with at all. Unfortunately boot loader is locked and usb debugging is off.
None of my 2 laptops detect it in fastboot or adb in windows and linux. I've installed proper drivers but it doesn't even show up in device manager as unknown or whatever.
It normally enters fastboot and recovery modes.
I did the root integrity check from recovery and it reported 92 files missing and 90 unknown files.
What i tried:
Reinstalling the same update through recovery (makes no difference)
Installing older updates ( recovery doesn't allow)
Factory reset through recovery (makes no difference)
flashing via fastboot (fastboot doesn't detect)
The only thing i did not try is qfil and I'm not doing that because a lot of people have reported losing their IMEI and other hardware information.
Also, I couldn't find a stock qfil firmware they were stock based made by other people.
Asus's update broke the phone. But I don't see a lot of people posting about it. I could use some help.
Thank you
---------- Post added at 04:40 PM ---------- Previous post was at 04:36 PM ----------
The update messed up its own system files. Clean flash means wiping partition and installing again.
How can we do that from stock recovery where it doesn't wipe /system ?
All installations from recovery are dirty.
Click to expand...
Click to collapse
I am using custom ROM (MiUI) when my problem happened.
Random Member said:
I am using custom ROM (MiUI) when my problem happened.
Click to expand...
Click to collapse
I have same prob, did you find a solution
phone is dead ( problem mother boad dead ) any aftermarket service or website ?
Hi, I tried updating to the newest miui.eu release, sadly I couldn't charge my phone after I successfully updated. So I wiped the system to flash the rom I used beforehand. Sadly, now my whole partition couldn't be decrypted and I couldn't access it via USB. So after a while I decided to format data. Now I had a phone with twrp, no data and no access via USB..
I changed the phones usb charging port with no success.
EDL doesnt seem to work either, maybe i am doing it wrong.
I really like this phone, I just repaired the display so I hope it isn't bricked.
Can you help me?
Thanks in advance, if you need further information, just ask!
I'm really appreciate your hardwork ?
Only one solution you have left, open back panel of your phone and find two golden point of EDL mode and then hold two points with joint pin and remember your phone battery should be removed and then connect to pc with hold two golden points now your phone is in EDL MODE then flash with stock rom through mi flash tool and remember inside your pc Modem driver is installed which is required in EDL MODE then that's easier to roll back at initial state of phone ? now your phone work smoothly.
---------- Post added at 01:12 PM ---------- Previous post was at 01:11 PM ----------
I'm really appreciate your hardwork ?
Only one solution you have left, open back panel of your phone and find two golden point of EDL mode and then hold two points with joint pin and remember your phone battery should be removed and then connect to pc with hold two golden points now your phone is in EDL MODE then flash with stock rom through mi flash tool and remember inside your pc Modem driver is installed which is required in EDL MODE then that's easier to roll back at initial state of phone ? now your phone work smoothly.
Check
bCid_diCb said:
Hi, I tried updating to the newest miui.eu release, sadly I couldn't charge my phone after I successfully updated. So I wiped the system to flash the rom I used beforehand. Sadly, now my whole partition couldn't be decrypted and I couldn't access it via USB. So after a while I decided to format data. Now I had a phone with twrp, no data and no access via USB..
I changed the phones usb charging port with no success.
EDL doesnt seem to work either, maybe i am doing it wrong.
I really like this phone, I just repaired the display so I hope it isn't bricked.
Can you help me?
Thanks in advance, if you need further information, just ask!
Click to expand...
Click to collapse
Thus is edl mode test pin points.
bCid_diCb said:
Hi, I tried updating to the newest miui.eu release, sadly I couldn't charge my phone after I successfully updated. So I wiped the system to flash the rom I used beforehand. Sadly, now my whole partition couldn't be decrypted and I couldn't access it via USB. So after a while I decided to format data. Now I had a phone with twrp, no data and no access via USB..
I changed the phones usb charging port with no success.
EDL doesnt seem to work either, maybe i am doing it wrong.
I really like this phone, I just repaired the display so I hope it isn't bricked.
Can you help me?
Thanks in advance, if you need further information, just ask!
Click to expand...
Click to collapse
Edl mode via shorting out the tester point is the only way for you , I beleive your presist or crust partition might have been totally messed up that's why you phone is like this or maybe you didn't enable usb debugging by default luckily your bootloader isn't locked it it was locked then your might have become something like a paperblock of 200grams.
bCid_diCb said:
Hi, I tried updating to the newest miui.eu release, sadly I couldn't charge my phone after I successfully updated. So I wiped the system to flash the rom I used beforehand. Sadly, now my whole partition couldn't be decrypted and I couldn't access it via USB. So after a while I decided to format data. Now I had a phone with twrp, no data and no access via USB..
I changed the phones usb charging port with no success.
EDL doesnt seem to work either, maybe i am doing it wrong.
I really like this phone, I just repaired the display so I hope it isn't bricked.
Can you help me?
Thanks in advance, if you need further information, just ask!
Click to expand...
Click to collapse
Have you tried flashing a rom using miflash https://www.xiaomiflash.com/?
bCid_diCb said:
Hi, I tried updating to the newest miui.eu release, sadly I couldn't charge my phone after I successfully updated. So I wiped the system to flash the rom I used beforehand. Sadly, now my whole partition couldn't be decrypted and I couldn't access it via USB. So after a while I decided to format data. Now I had a phone with twrp, no data and no access via USB..
I changed the phones usb charging port with no success.
EDL doesnt seem to work either, maybe i am doing it wrong.
I really like this phone, I just repaired the display so I hope it isn't bricked.
Can you help me?
Thanks in advance, if you need further information, just ask!
Click to expand...
Click to collapse
i had the same problem years ago with another device ... try to go in twrp press the power botton for 15 sec rebot on twrp format data (not with advanced wipe) and after that a full wipe in advanced wipe.... And look if you solved the encrypt problem.... (Sorry for my bad english)...
---------- Post added at 06:40 PM ---------- Previous post was at 06:17 PM ----------
Yakusha90 said:
i had the same problem years ago with another device ... try to go in twrp press the power botton for 15 sec rebot on twrp format data (not with advanced wipe) and after that a full wipe in advanced wipe.... And look if you solved the encrypt problem.... (Sorry for my bad english)...
Click to expand...
Click to collapse
A lot of time an hard rebot can help... try you can't lose anything ...
I'm curious... let me know if it worked ...
---------- Post added at 08:00 PM ---------- Previous post was at 07:58 PM ----------
Yakusha90 said:
i had the same problem years ago with another device ... try to go in twrp press the power botton for 15 sec rebot on twrp format data (not with advanced wipe) and after that a full wipe in advanced wipe.... And look if you solved the encrypt problem.... (Sorry for my bad english)...
---------- Post added at 06:40 PM ---------- Previous post was at 06:17 PM ----------
A lot of time an hard rebot can help... try you can't lose anything ...
Click to expand...
Click to collapse
I mean with this method...
Yakusha said:
I'm curious... let me know if it worked ...
---------- Post added at 08:00 PM ---------- Previous post was at 07:58 PM ----------
I mean with this method...
Click to expand...
Click to collapse
This method didn't work, I will try the esl option next. I tried it before tho with no success, maybe because I didn't install the qualcomm driver. What could be the problem if my phone still doesn't get recognized?
It's so weird that a software issue causes my phone to not be able to connect to my computer on the recover layer
Try this:. Go in twrp - advanced - terminal - and write reboot edl in the terminal and after that flash the official MIUI rom.... try and let me know...
---------- Post added at 09:00 PM ---------- Previous post was at 08:44 PM ----------
bCid_diCb said:
This method didn't work, I will try the esl option next. I tried it before tho with no success, maybe because I didn't install the qualcomm driver. What could be the problem if my phone still doesn't get recognized?
It's so weird that a software issue causes my phone to not be able to connect to my computer on the recover layer
Click to expand...
Click to collapse
Don't open the phone...
Yakusha said:
Try this:. Go in twrp - advanced - terminal - and write reboot edl in the terminal and after that flash the official MIUI rom.... try and let me know...
---------- Post added at 09:00 PM ---------- Previous post was at 08:44 PM ----------
Don't open the phone...
Click to expand...
Click to collapse
if i type reboot edl in the terminal of twrp, my phone goes into a bootloop, showing the mi.com logo, my computer doesnt recognize anything sadly
Did you try to decrypt in twrp with your account's password?
Yakusha said:
Did you try to decrypt in twrp with your account's password?
Click to expand...
Click to collapse
How to do it?
Yakusha said:
Did you try to decrypt in twrp with your account's password?
Click to expand...
Click to collapse
There is nothing left to decrypt I think. How to do it though(for the next time things go wrong)?
bCid_diCb said:
There is nothing left to decrypt I think. How to do it though(for the next time things go wrong)?
Click to expand...
Click to collapse
With the official rom encrypted when you boot in twrp it ask your password for decrypt... But if you bot in twrp and it don't ask anything then you don't have anything to decrypt...
Try to check the others threads...
I'm pretty sure that you can fix it without open it...
Mouths ago I solved a hard brick on my pixel 2xl that was without fastboot, twrp and pc didn't recognize it... I used a tool for reinstall usb drivers and official rom... I will try to find the guide and send it to you as information...
---------- Post added at 04:24 PM ---------- Previous post was at 03:53 PM ----------
How Windows see you device?... Try to go in device manager and check... if your phone appears in device manager as "QHSUSB_BULK" or unknow device, you have to install the proper driver....
And try this tool https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
So I tried a lot of things, reboot edl didn't work, Testpoint short-circuit didn't work either.
It's hard to say, but I don't know what happened and I have to say goodbye to my beloved phone. It drives me crazy that I didn't found what happened. I don't even know, if I will flash my next phone.
Thanks for your support, if you want to try your luck, or need a display (2weeks old) or any other part, just pm me.
:crying:
bCid_diCb said:
So I tried a lot of things, reboot edl didn't work, Testpoint short-circuit didn't work either.
It's hard to say, but I don't know what happened and I have to say goodbye to my beloved phone. It drives me crazy that I didn't found what happened. I don't even know, if I will flash my next phone.
Thanks for your support, if you want to try your luck, or need a display (2weeks old) or any other part, just pm me.
:crying:
Click to expand...
Click to collapse
Did you try XiaoMiToolV2 ? When you have all drivers, type in program "my phone is bricked", the program should recognize the phone (turning on in twrp) running in recovery and forcing to fastboot mode.
crt-shadow said:
Did you try XiaoMiToolV2 ? When you have all drivers, type in program "my phone is bricked", the program should recognize the phone (turning on in twrp) running in recovery and forcing to fastboot mode.
Click to expand...
Click to collapse
"No devices found[...]"