Hi,
Can someone help me? My Moto Z bricks itself:
I have a Moto Z XT1650-3. On January 31 the phone shutdown alone, after I unlocked teh screen with fingerprints then I restarted the phone and all fine. Then the phone shutdown again, when the phone restarted. It restarted in fastboot mode I switched to restart normally when it showed these message "Your device has failed verification and may not work properly".
I have my phone unusable. When my phone returned for the Moto Technical Support It only boots in fastmode. No recovery no OS (android). I've to say that I never try to root or unlocked the bootloader of my Phone it worked really smooth. I bought the Phone on October 4th 2016.
Finally I tried to reflash the Stock Firmware via fastboot and the problem continues . The phone only boots in fastboot again an again. I tried via fastboot the CMD: gtrvall and said tha warrantyavoid NO.
When I tried recovey mode the same message appears "Your device has failed verification and may not work properly" and I cant do anything.
I wonder someone can help me.
Regards
So you tried to reflash the firmware via fastboot and your device is still dead?
I had the same issue but flashing via RSDLite fixed it.
In your case, I may have to throw in the towel and assume that a critical block on your system partition is corrupted beyond recovery, possibly caused by a defective NAND module.
D13H4RD2L1V3 said:
So you tried to reflash the firmware via fastboot and your device is still dead?
I had the same issue but flashing via RSDLite fixed it.
In your case, I may have to throw in the towel and assume that a critical block on your system partition is corrupted beyond recovery, possibly caused by a defective NAND module.
Click to expand...
Click to collapse
Hi
Yes i tried to reflash via fastboot it didn't worked the phone boot until in fastboot mode and sometimes the Motos logo appears and then again fastboot mode?.
Thnks for answer but if it is this i think that its a hsrdware failure and the warranty must have to apply in this case because my phone is until in warranty I think that this problem its hardware from the first day and this message its like. Warning that something isn't right?
I will try again with Motorola warranty to replace the phone
Regards
Related
I have hard bricked my device, even motherboard is dead, no sound when connected to PC. Phone is in waranty. What should i say to realme support so they won't be able to tell that I tried to install custom ROM and charge me for motherboard. It's a new phone. I unlocked the boot-loader.
Deepakk88 said:
I have hard bricked my device, even motherboard is dead, no sound when connected to PC. Phone is in waranty. What should i say to realme support so they won't be able to tell that I tried to install custom ROM and charge me for motherboard. It's a new phone. I unlocked the boot-loader.
Click to expand...
Click to collapse
best bet is to visit SC and tell them your device stopped working after official update . don't say anything else
I told them that the phone failed to start after a software update. They repaired it in 2 hrs and gave it back. So the motherboard was not fried as I thought.
What happened was that the TWRP recovery someone provided here has not worked, my device failed to get in to TWRP recovery after I have re-started the phone, So, I tried to flash with other TWRP versions that some people linked to in their posts on Realme U1 on other websites. None of them worked and after sometime my phone went in to bootloop, I got it in to fastboot screen by holding down the power and vol down button and tried various fastboot commands, none of them fixed the bootoop. I finally gave the command 'fastboot oem reboot -recovery' then it switched off the phone.
I recently got a Razer Phone (original, not Razer Phone 2) that I installed Lineage OS on, and I was dumb enough to re-lock the bootloader. Now I can't enable flashing. When I boot it gives the message "Your device has failed verification and may not work properly [...] Device will continue to boot in 5 seconds"
After 5 seconds it reboots and now it's stuck in that loop. It won't enter the recovery (same message) but the bootloader is still accessible.
I can use fastboot but I can't flash anything since it's locked, and I can't re-enable flashing.
Also I got it used from a friend so there's no way I'm gonna be able to RMA the thing.
Any help will be appreciated!
Hi folks,
I've got a new A52 5G and wanted it to root. TWRP couldn't be used, because each and every possible solution failed. I even got stuck at boot with a message that the recovery couldn't get startet, even if I just restarted the phone without pressing the keys and without plugged USB cable.
Even flashing the original firmware was not possible. Then I tried to lock the bootloader again and flashing of the firmware was going on with odin. Puh... Then I used the Magisk method without TWRP to change die boot.img with magisk and load it in Odin. Success! I had now root on the phone. Yesterday I read about uninstall Magisk and install it afterwards on the B partition for updating the firmware over OTA. But accidentally I pressed the button below "uninstall" and it performed imediately. Now my phone is dead again... With unlocked Bootloader it is stuck in a bootload and I can start the Samsung recovery mode to wipe the cache for example. I wiped the phone completely, but it is still stucked in a bootloop.
Then I tried my first method: Just lock the Bootloader again (in the download mode) and then flash the new firmware with odin. But Odin either crashes or is giving me instantly the message "failed".
When I'm trying to start the phone (it happened also after locking the bootloader) i'm getting the download screen and the message with a big red !
"partition boot
Reason boot: Hash of data does not match digest in descriptor. [2nd] (3)
Calculated Hash of (boot) : 23B8CFD554, (VEMETA) : D23E59ACD6
CUSTOM boot
VBMETA A526BXXU1AUCA, 38851814R"
Now I unlocked the bootloader again, to access the recovery mode so I can turn it off. Otherwise its stuck in the damn bootloop. Can't flash and wipe doesn't help either.
Please help me somehow -.-
why did you u
Insomnium_D said:
Hi folks,
I've got a new A52 5G and wanted it to root. TWRP couldn't be used, because each and every possible solution failed. I even got stuck at boot with a message that the recovery couldn't get startet, even if I just restarted the phone without pressing the keys and without plugged USB cable.
Even flashing the original firmware was not possible. Then I tried to lock the bootloader again and flashing of the firmware was going on with odin. Puh... Then I used the Magisk method without TWRP to change die boot.img with magisk and load it in Odin. Success! I had now root on the phone. Yesterday I read about uninstall Magisk and install it afterwards on the B partition for updating the firmware over OTA. But accidentally I pressed the button below "uninstall" and it performed imediately. Now my phone is dead again... With unlocked Bootloader it is stuck in a bootload and I can start the Samsung recovery mode to wipe the cache for example. I wiped the phone completely, but it is still stucked in a bootloop.
Then I tried my first method: Just lock the Bootloader again (in the download mode) and then flash the new firmware with odin. But Odin either crashes or is giving me instantly the message "failed".
When I'm trying to start the phone (it happened also after locking the bootloader) i'm getting the download screen and the message with a big red !
"partition boot
Reason boot: Hash of data does not match digest in descriptor. [2nd] (3)
Calculated Hash of (boot) : 23B8CFD554, (VEMETA) : D23E59ACD6
CUSTOM boot
VBMETA A526BXXU1AUCA, 38851814R"
Now I unlocked the bootloader again, to access the recovery mode so I can turn it off. Otherwise its stuck in the damn bootloop. Can't flash and wipe doesn't help either.
Please help me somehow -.-
Click to expand...
Click to collapse
why did you OTA update the rooted phone
it is clearly written that your phone might brick.
what happened to you is your boot.img file is replaced with the newer version try replacing with the boot.img file of previous version.
I didn't, because I get (as always, this is not my first rooted phone) the message, that the system has been changed. OTA is not working and I read that uninstall magisk, update the phone and BEFORE reboot install magisk again on partition B. But I accidentaly pressed the second option in magisk, complete uninstall or how its name is. Didn't expected, that its start instantly without a "Caution" message.
Uninstalling Magisk should not bring my phone into a bootloop anyway, even if I wipe the cache. Or am I wrong?
raja0408 said:
what happened to you is your boot.img file is replaced with the newer version try replacing with the boot.img file of previous version.
Click to expand...
Click to collapse
That is the problem how do I do that, when everything with odin stops imediately or odin crashes.
Does Odin give you any error messages? Are you patching all of the files for the firmware AP BL CP & CSC? Are you making sure to use the non home CSC? Have you tried using Samsung Smart Switch to recover your phone?
Smart Switch didn't recognize the phone. The only error on Odin was "succeed 0 / failed 1).
It worked with Windows 10 notebook and the USB C Port. However it didn't worked on Win 7 and regular USB Ports. Very strange. Well, but now I have the original firmware and again lots of bloatware. TWRP doesn't work, impossible to boot with it. How can I root the A52 with Magisk that way, to deactivate it - if needed - for firmware updates? The phone doesn't has A/B partition.
Same happened to me.
So, I have an A52 Indian version and want to flash the Canadian firmware. I downloaded different versions of the Canadian firmware and used Odin to flash. I followed the instructions on downloading the files, loading them into Odin,hit Start and it kept failing. It was giving an error message regarding a repartitioning error. Could this be due to having to tick "OEM Unlocking" in developer options which I hadn't done?
Hey, is your phone still stuck ?
SHAREit
ok hear me out, I'm a newbie, and I missed up, plz help
I was trying to root my device following this tutorial, I flashed twrp and vbmeta and every thing went alright without errors, I booted the phone into recovery to continue as how the tutorial said, but it gave me the orange state error and it restarted into system but now the device is factory reset, I enabled usb debugging and went on to follow this tutorial, every thing went same as before and I couldn't boot into recovery, so I decided to flash the "orange_state_disabler_MTK Only.zip" with adb and every thing went downhill from there, It won't boot to recovery, bootloader nor system, It just stays at a blank screen after the logo and the orange state message, It is recognized by adb as "recovery" and I can do adb commands but I can't boot to bootloader to flash the stock firmware, I found this thread and tried using the tool mentioned there, Faced an error, solved it and the phone still won't boot to any thing.
so, is there any way I can get out of this situation ?
TLDR / what you should know/ idk ¯\_(ツ)_/¯
- did something wasn't supposed to do
- can't boot to recovery
- can't boot to bootloader
- device recognized by adb but can't do fastboot commands
- device is recognized by MTKAuthBypassToolV25
- can't shutdown nor restart using phone physical buttons
- don't know if the below screenshots would help with any thing, but here goes nothing
You have misunderstanding, Orange State does not cause anything. That is just notification that bootloader is unlocked, nothing more. Therefore the Orange State Disabler cannot fix anything. You don't need this at all.
But it seems it destroyed fastboot. flash lk from SP Flash Tool
aIecxs said:
You have misunderstanding, Orange State does not cause anything. That is just notification that bootloader is unlocked, nothing more. Therefore the Orange State Disabler cannot fix anything. You don't need this at all.
But it seems it destroyed fastboot. flash lk from SP Flash Tool
Click to expand...
Click to collapse
please explain, I don't know what IK is, and if I could flash things with SP flash tools, wouldn't I be able to flash stock firmware?
lk - little kernel. that is the partition where fastboot lives (and was modified by Orange State Disabler).
you need partition image from stock ROM and any flash tool to restore its original state.
i can't do that because i can't boot to bootloader
you don't need bootloader, only preloader or bootrom
ok turns out ima an idiot and misunderstood the entire situation , this is my first dealing with an mtk device so i thought sp flash tool is like odin and you need to be in download mode to flash things so i panicked, and didn't read well how to use the tool.
flashed stock firmware and the phone is up and running again
thanks for your help man really appreciate it and sorry for wasting your time
I am currently trying to install LineageOS on my phone. I personally have never unlocked or reinstalled a new operating system on my phone. I looked on some XDA forums for some guides and i found one and followed the steps. I unlocked my phone and I installed a custom TWRP because I was trying to downgrade the phone back to android 11. Once i was done flashing the file to the phone and rebooted it doesn't boot anymore and only gives me a booting screen for a few seconds after I hold down the power and volume up button for a few seconds nothing else works. I have use the MSM tool and put my phone into EDL mode and it detected the phone with a black screen. Every time I use the tool it works till about 18% then it gives me a Sahara communication failed error and then my phone gets out of EDL mode.. I installed all the drivers needed on my PC and used multiple USB 2.0 slots but it still fails. Any help would be appreciated.
There are warnings in the TWRP thread for the N200 that it is broken and should not be flashed.
I have written an easy to follow guide here to downgrade to A11 with Fastboot Enhance.
Unfortunately, now that you have used MSMTool on the phone, it is now bootloader LOCKED. This tool should be the last resort only if you are already hard bricked. You could have gotten the phone into fastboot if either boot.img was still intact and re-flashed the rom with a still unlocked bootloader. The phone will change slots after so many failed boots.
Now that your boot loader is locked, the only tool that can modify the phone is MSMTool. If you can get into Recovery, do delete user data and try again.
Otherwise, you will need to get an RMA and send phone back to OP.
scanman0 said:
There are warnings in the TWRP thread for the N200 that it is broken and should not be flashed.
I have written an easy to follow guide here to downgrade to A11 with Fastboot Enhance.
Unfortunately, now that you have used MSMTool on the phone, it is now bootloader LOCKED. This tool should be the last resort only if you are already hard bricked. You could have gotten the phone into fastboot if either boot.img was still intact and re-flashed the rom with a still unlocked bootloader. The phone will change slots after so many failed boots.
Now that your boot loader is locked, the only tool that can modify the phone is MSMTool. If you can get into Recovery, do delete user data and try again.
Otherwise, you will need to get an RMA and send phone back to OP.
Click to expand...
Click to collapse
Sorry I should have written more details but I currently have a hard bricked device. It will not boot and It failed to boot like 20 times. It will not enter fastboot or even get past the logo when you first turn it on. I did use MSM tool after it wasn't letting me into fastboot. Thanks for the help and I will send it back.
z67gp said:
Sorry I should have written more details but I currently have a hard bricked device. It will not boot and It failed to boot like 20 times. It will not enter fastboot or even get past the logo when you first turn it on. I did use MSM tool after it wasn't letting me into fastboot. Thanks for the help and I will send it back.
Click to expand...
Click to collapse
Fix Sahara communication failed error in MSM Download Tool
In this tutorial, we will show you how to fix the Sahara communication failed and other related MSM Download Tool errors.
www.droidwin.com