Hello everybody,
once again I'm in trouble.
With help of Marcowe I updated my phone with no OS to Oreo
HTML:
https://forum.xda-developers.com/z2-force/help/z2-os-help-to-t3837577
I wanted to give it another try and here I my attempts to install LOS.
1. oem unlock
2. I booted into current twrp (fastboot boot twrp-3.2.3-2-nash.img
3. adb push of lineange onto internal sd card
4. In TWRP under advanced wipe I pressed format data (If I now think about it, in the progress windows there was some red text probably not a good sign)
5. I installed LOS with now error
6. There was an option to delete dalvik cache which I pressed
7 . System reboot
8. Black screen Device Manager shows me Qualcomm HS-USB QDLoader 9008 (COM6)
I tried a blankflash file from here
HTML:
https://unbricks.com/unbrick-motorola-moto-z2-force-update-fix-issues/
but it shows me an error. Log file will be at end of post.
QFIL does not find a corresponding MBN nor an XML file in stock rom
HTML:
https://forum.xda-developers.com/z2-force/development/factory-image-moto-z2-force-nash-retail-t3699306
If you have got any idea to get my phone back, I would be happy and would like to contribute.
Regards,
Bew
Log file:
[ 0.001] Opening device: \\.\COM6
[ 0.003] Detecting device
[ 34.009] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.009] Check qboot_log.txt for more details
[ 34.009] Total time: 34.011s
[ 34.009]
[ 34.009] qboot version 3.85
[ 34.009]
[ 34.009] DEVICE {
[ 34.009] name = "\\.\COM6",
[ 34.009] flags = "0x64",
[ 34.009] addr = "0x28FD74",
[ 34.009] api.bnr = "0x372FD8",
[ 34.009] }
[ 34.009]
[ 34.009]
[ 34.009] Backup & Restore {
[ 34.009] num_entries = 0,
[ 34.009] restoring = "false",
[ 34.009] backup_error = "not started",
[ 34.009] restore_error = "not started",
[ 34.009] }
[ 34.009]
Try this, power the phone back on. If you get that screen again cover the power button (don't press yet) with one finger, then cover the volume down button (don't press yet) with another.. Then press the power button, until the screen goes blank, then right after it does, (while still holding down the power button) Press the volume down button, until it comes on again.. Hopefully it will give you the bootloader instead.. If it does, Then find a flashll file for your carrier.
doubledragon5 said:
Try this, power the phone back on. If you get that screen again cover the power button (don't press yet) with one finger, then cover the volume down button (don't press yet) with another.. Then press the power button, until the screen goes blank, then right after it does, (while still holding down the power button) Press the volume down button, until it comes on again.. Hopefully it will give you the bootloader instead.. If it does, Then find a flashll file for your carrier.
Click to expand...
Click to collapse
Hello doubledragon5,
the screen is blank all the time. It stays black if I try to turn it on or off. The phone gives no sign if its on or off.
Regards,
Bew
b.bew said:
Hello doubledragon5,
the screen is blank all the time. It stays black if I try to turn it on or off. The phone gives no sign if its on or off.
Regards,
Bew
Click to expand...
Click to collapse
Sorry miss read your post.
Unbrick yo Brick quick ish
Here are the signed diag drivers for win
Qualcomm Diag Drivers Signed
attached is the blankflash zip
Unplug your phone, install diag drivers, replug and wait for the everything to recognize and settle.
Unzip the blankflash to a folder and run the bat file, after it's done you should be back in bootloader where you can re-flash the latest firmware for your phone.
Use 2.0 usb ports from your motherboard, not a hub like the front of your pc; and use the oem cable.
If you have trouble getting this to work then unplug your phone from your pc, uninstall your moto drivers and the qualcomm drivers. Restart. Reininstall the drivers, reboot; then plug your phone and wait for the drivers to recognize, install, and settle. You may need to try to run the blankflash a couple of times to get it to take. You may need to try alternate usb ports, even 3.0+
This phone can be super picky about ports, cables, and even adb/fastboot versions. For most they won't have to worry about most of this, but for others this is the basic setup that works for the majority of users.
*Note - To get into blankflash/edl mode manually...
from bootloader prompt 'fastboot oem blankflash' w/o quotes
via adb command 'adb reboot edl' w/o quotes
41rw4lk said:
Here are the signed diag drivers for win
Qualcomm Diag Drivers Signed
attached is the blankflash zip
Unplug your phone, install diag drivers, replug and wait for the everything to recognize and settle.
Unzip the blankflash to a folder and run the bat file, after it's done you should be back in bootloader where you can re-flash the latest firmware for your phone.
Click to expand...
Click to collapse
Thank you very much.
I was able to start in bootloader again. I was not able to flash the firmware via the procedure described by Marcowe (see link in first post, it mentioned that they are no sectors _a _b or something like that, I will recheck.). Still I was able too boot in Oreo.
I guess because its an A/B device? Does this mean that one is corrupted now?
Regards,
Bew
b.bew said:
Thank you very much.
I was able to start in bootloader again. I was not able to flash the firmware via the procedure described by Marcowe (see link in first post, it mentioned that they are no sectors _a _b or something like that, I will recheck.). Still I was able too boot in Oreo.
I guess because its an A/B device? Does this mean that one is corrupted now?
Regards,
Bew
Click to expand...
Click to collapse
So you're able to boot and use your phone, correct? If so, don't worry about the other slot, it'll get sorted when a new update comes out, or you flash a custom rom (if you choose to). If you followed Marcowe's flashing instructions from that other post you linked, then the same firmware is flashed on both slots. As for slot _a _b messages, could have been an out of date bootloader session depending on what you were doing and what, if anything, you flashed prior to trying to flash the firmware. A few different things could be going on there, so unless you can't boot I wouldn't trip on it at the moment.
Either way, if you can boot and use your phone I wouldn't worry about it, unless there is something specific you're trying to do. Alternatively, you can boot into bootloader mode and run the command 'fastboot getvar all' w/o quotes and get a little info about the state of your phone.
41rw4lk said:
So you're able to boot and use your phone, correct? If so, don't worry about the other slot, it'll get sorted when a new update comes out, or you flash a custom rom (if you choose to). If you followed Marcowe's flashing instructions from that other post you linked, then the same firmware is flashed on both slots. As for slot _a _b messages, could have been an out of date bootloader session depending on what you were doing and what, if anything, you flashed prior to trying to flash the firmware. A few different things could be going on there, so unless you can't boot I wouldn't trip on it at the moment.
Either way, if you can boot and use your phone I wouldn't worry about it, unless there is something specific you're trying to do. Alternatively, you can boot into bootloader mode and run the command 'fastboot getvar all' w/o quotes and get a little info about the state of your phone.
Click to expand...
Click to collapse
I'm able to boot and use my phone. I would like to use lineageos but my last two attempts where disasters.
I copied the last part of the info state which gives information about the slots since I'm not sure wat to delete besides of serial number.
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
b.bew said:
I'm able to boot and use my phone. I would like to use lineageos but my last two attempts where disasters.
I copied the last part of the info state which gives information about the slots since I'm not sure wat to delete besides of serial number.
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
Click to expand...
Click to collapse
You weren't on the correct build when you flashed Lineage OS. It explicitly says which one to be on in the OP.
http://download.invisiblek.org/nash/unbrick.zip -- this has instructions in it. We've done it hundreds of time, and I know it works.
Best of luck.
fastboot oem fb_mode_set
fastboot getvar max-sparse-size
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash bootloader_a bootloader.img
fastboot flash bootloader_b bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash modem_b NON-HLOS.bin
fastboot flash fsg_b fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.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 oem_a oem.img
fastboot flash bluetooth_b BTFM.bin
fastboot flash dsp_b adspso.bin
fastboot flash logo_b logo.bin
fastboot flash boot_b boot.img
fastboot flash system_b system.img_sparsechunk.0
fastboot flash system_b system.img_sparsechunk.1
fastboot flash system_b system.img_sparsechunk.2
fastboot flash system_b system.img_sparsechunk.3
fastboot flash system_b system.img_sparsechunk.4
fastboot flash system_b system.img_sparsechunk.5
fastboot flash oem_b oem.img
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
Put this as your flashall.bat with your correct firmware
hello i have the same problem all time, first install qualcom drivers, then i uninstall motorola drivers and reboot, is very difficult to detect my phone in my pc, dont know why, but when detects it says unknown device, then i manually update the driver to Qualcomm HS-USB QDLoader 9008 (COM6), and its ok, run bat file blankflash, but it says waiting for device all time i did on my windows 7 pc and my windows 1 pc is the same, can anyone help me?
XxeAgLeAnGeLxX said:
hello i have the same problem all time, first install qualcom drivers, then i uninstall motorola drivers and reboot, is very difficult to detect my phone in my pc, dont know why, but when detects it says unknown device, then i manually update the driver to Qualcomm HS-USB QDLoader 9008 (COM6), and its ok, run bat file blankflash, but it says waiting for device all time i did on my windows 7 pc and my windows 1 pc is the same, can anyone help me?
Click to expand...
Click to collapse
You have to stop thread jumping and posting bits and pieces of your problem here and there, it makes it difficult to help you and it clutters the thread making it hard to reference for other users. Are we to back track through 3-4 different threads to see what the original problem is and what you've tried? Plus this thread is almost a year old and I'm sure isn't relevant to what your problem is.
41rw4lk said:
You have to stop thread jumping and posting bits and pieces of your problem here and there, it makes it difficult to help you and it clutters the thread making it hard to reference for other users. Are we to back track through 3-4 different threads to see what the original problem is and what you've tried? Plus this thread is almost a year old and I'm sure isn't relevant to what your problem is.
Click to expand...
Click to collapse
sorry
41rw4lk said:
Here are the signed diag drivers for win
Qualcomm Diag Drivers Signed
attached is the blankflash zip
Unplug your phone, install diag drivers, replug and wait for the everything to recognize and settle.
Unzip the blankflash to a folder and run the bat file, after it's done you should be back in bootloader where you can re-flash the latest firmware for your phone.
Use 2.0 usb ports from your motherboard, not a hub like the front of your pc; and use the oem cable.
If you have trouble getting this to work then unplug your phone from your pc, uninstall your moto drivers and the qualcomm drivers. Restart. Reininstall the drivers, reboot; then plug your phone and wait for the drivers to recognize, install, and settle. You may need to try to run the blankflash a couple of times to get it to take. You may need to try alternate usb ports, even 3.0+
This phone can be super picky about ports, cables, and even adb/fastboot versions. For most they won't have to worry about most of this, but for others this is the basic setup that works for the majority of users.
*Note - To get into blankflash/edl mode manually...
from bootloader prompt 'fastboot oem blankflash' w/o quotes
via adb command 'adb reboot edl' w/o quotes
Click to expand...
Click to collapse
I tried multiple methods to get into edl mode to do a blankflash , but I am not succesful. I tried the manual commands you mentioned but "fastboot oem blankflash" throws an error "command restricted".
adb reboot edl simply reboots multiple times and then boots normally to os, doesn't get detected as Qualcomm 9092 device.
I tried qcom method from bootloader which just normally boots the device to android but my laptop does detect it as qualcomm 9092 device. but then your blank-flash file doesn't work on it and stays on "waiting for device" .
Reason I want to blankflash is I accidentally flashed stock pie retail rom on my TMO 1789-04 device and now I dont have network/no sim error. Although baseband and imei are visible I dont have network or shows no sim error. I did manage to install TMO stock oreo but still no luck. As a last try I want to do blankflash and see if it helps.
can you please help me to get into edl mode or help blankflash my moto XT 1789-04?
latadswapnil said:
I tried multiple methods to get into edl mode to do a blankflash , but I am not succesful. I tried the manual commands you mentioned but "fastboot oem blankflash" throws an error "command restricted".
adb reboot edl simply reboots multiple times and then boots normally to os, doesn't get detected as Qualcomm 9092 device.
I tried qcom method from bootloader which just normally boots the device to android but my laptop does detect it as qualcomm 9092 device. but then your blank-flash file doesn't work on it and stays on "waiting for device" .
Reason I want to blankflash is I accidentally flashed stock pie retail rom on my TMO 1789-04 device and now I dont have network/no sim error. Although baseband and imei are visible I dont have network or shows no sim error. I did manage to install TMO stock oreo but still no luck. As a last try I want to do blankflash and see if it helps.
can you please help me to get into edl mode or help blankflash my moto XT 1789-04?
Click to expand...
Click to collapse
Blankflash won't solve that problem. Once you flash a pie modem you're stuck with it. The only solution is a pie modem which doesn't exist for TMO. No one has found a work around for this and with this phone being as old as it is now, it's unlikely that anything useful will be provided. Sorry. If you look around the forum you see dozens of warnings and examples of flashing the wrong firmware to your phone, most notably pie firmware. I think the only solution would be a pie modem that works for TMO too or a way to overwrite the modem nv value, both are pretty far out there.
41rw4lk said:
Blankflash won't solve that problem. Once you flash a pie modem you're stuck with it. The only solution is a pie modem which doesn't exist for TMO. No one has found a work around for this and with this phone being as old as it is now, it's unlikely that anything useful will be provided. Sorry. If you look around the forum you see dozens of warnings and examples of flashing the wrong firmware to your phone, most notably pie firmware. I think the only solution would be a pie modem that works for TMO too or a way to overwrite the modem nv value, both are pretty far out there.
Click to expand...
Click to collapse
is there a way we can erase flash memory and reinstall bootloader and everything from scratch?
Also, can you please help blankflashing the phone? any steps that I can take to be in edl mode?
41rw4lk said:
Blankflash won't solve that problem. Once you flash a pie modem you're stuck with it. The only solution is a pie modem which doesn't exist for TMO. No one has found a work around for this and with this phone being as old as it is now, it's unlikely that anything useful will be provided. Sorry. If you look around the forum you see dozens of warnings and examples of flashing the wrong firmware to your phone, most notably pie firmware. I think the only solution would be a pie modem that works for TMO too or a way to overwrite the modem nv value, both are pretty far out there.
Click to expand...
Click to collapse
So it seems that the problem is flashing a newer modem that is not compatible with Tmobile. Can you expand on where the info is written and why it cannot be reverted?
Sackgi said:
So it seems that the problem is flashing a newer modem that is not compatible with Tmobile. Can you expand on where the info is written and why it cannot be reverted?
Click to expand...
Click to collapse
The problem is TMO stopped with oreo, never made pie. So if you flashed a pie modem on TMO you're out of luck. When you flash a new modem most times it bumps your revision number up, so you can't roll back. You can typically only flash within the same revision or higher. Meaning you can't rollback to a lower revision modem.That info and warnings are all over this forum, and a lot of it is just anti-rollback.
Even on oreo whenever someone would flash the wrong oreo firmware, if it had a higher revision than what the proper firmware had, they would have to wait for an update that had an equal or higher revision modem to recover. Since TMO never and won't ever make pie firmware, going back is just not possible.
41rw4lk said:
The problem is TMO stopped with oreo, never made pie. So if you flashed a pie modem on TMO you're out of luck. When you flash a new modem most times it bumps your revision number up, so you can't roll back. You can typically only flash within the same revision or higher. Meaning you can't rollback to a lower revision modem.That info and warnings are all over this forum, and a lot of it is just anti-rollback.
Even on oreo whenever someone would flash the wrong oreo firmware, if it had a higher revision than what the proper firmware had, they would have to wait for an update that had an equal or higher revision modem to recover. Since TMO never and won't ever make pie firmware, going back is just not possible.
Click to expand...
Click to collapse
So what you are telling me is that there is no way to rollback once the revision number is higher. I question how is that no one has figured it out how to overcome this. Is it not possible to write a script to trick the system to install the old modem using the new modem file? In other words, if what needs to be verified is that the revision number matches, would it be possible to modify the new modem file with the old modem one?
Nothing is ever impossible, this site is a testament to that. Those revision numbers are most likely stored as nv values. How easy it is to edit those, idk. Can it be done without bricking your phone, idk. I do know that plenty of members have thrown everything they can think of at this problem to no avail, several of them just completely bricking their phone entirely.
What you're saying makes sense on paper, but you're talking about hijacking the boot process and injecting data long before android even enters the picture. That's qualcomm stuff, like blankflashing.
The reality is, it's an android 9 problem on a phone that's stuck on 8 while the rest have moved on to 10 and 11. Not a big market of players to delve into this problem, sorry. As for just editing a modem, not so easy. I've seen others trying in other forums. Not to mention what gets flagged and tripped trying to flash something like that. Once you edit an officially signed package, it's no longer officially signed. Sorry to be the bad news bear.
Related
ZE551ML - 4gb ram
I encountered this error when flashing thru fastboot.
My phone came from no fastboot/recovery then flash firmware with xFSTK, was able to get fastboot.
Tried commands like;
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
none of this works, getting " FAILED (remote: flash_cmds error!) " error.
Images are from WW_ZE551ML_2.15.40.13_20150506 official rom.
tried the clear cache command it just escape out of fastboot mode.
Also tried Asus Flash tool but getting failed error.
I hope someone could help.
Try flash the raw for .13 in flashtools ...5 minutes after you get "xfstki"- 'success!' but leave your cable in fone. Hopefully you see it flash to fone in that time. When you do see it flash leave it a while
Then start the flashtools ..if you see small green then red text in fastboot...restart flashtools when until it goes 'sky blue and bigger bold text' you will then get success there
P's, can you put all the links for fwr dnx and ifwi and raw etc here for me for .13 should I need these again ..my pc crashed ugh!
Thanks for your reply,
I'm at work right now.
But I'll try this later.
[SOLVED] FAILED (remote: flash_cmds error!)
This guide help me out..
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
Thanks XDA.
Thanks for that,glad you`re sorted out... pc restored now saved all the stuff for zenny , pheeeew !
@asus_abz May i know how did you get rid of "FAILED (remote: flash_cmds error!) " error."
I am trying to fix my hard bricked Zenfone 2 and the only thing that seems working is fastboot but i keep getting the above error message.
Thank you!
ulbx said:
@asus_abz May i know how did you get rid of "FAILED (remote: flash_cmds error!) " error."
I am trying to fix my hard bricked Zenfone 2 and the only thing that seems working is fastboot but i keep getting the above error message.
Thank you!
Click to expand...
Click to collapse
Same problem here. Anyone got any experience on this? Tried the guide above. Getting this error message in CMD:
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (12395 KB)...
OKAY [ 2.009s]
writing 'boot'...
FAILED (remote: flash_cmds error!
)
finished. total time: 4.831s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (13967 KB)...
OKAY [ 2.082s]
writing 'recovery'...
FAILED (remote: flash_cmds error!
)
finished. total time: 4.917s
C:\adb>fastboot flash system system.img
error: cannot open 'system.img'
Asus Zenfone 2 (ZE551ML) /MM Z00A_WW_4.21.40.134
Workaround Solution to the dreaded remote: flash_cmds error!
Osaci said:
Same problem here. Anyone got any experience on this? Tried the guide above. Getting this error message in CMD:
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (12395 KB)...
OKAY [ 2.009s]
writing 'boot'...
FAILED (remote: flash_cmds error!
)
finished. total time: 4.831s
...
Click to expand...
Click to collapse
I was getting the exact same error after using xfstk-downloader_v1.7.0.exe to unbrick my Asus Zenfone 2 ZE551ML. Not seeing a reply to your post and after searching only to find unrelated posts. I took a whack at it and after a few hours, finally got my device to boot up again *insert Dr. Frankenstein's "It's Alive!" impersonation here*. My hypothesis was that it had to do with the partitioning being read incorrectly since it was the device reporting back issues with execution of the commands. In any case, here is how I got past it.
=--=-=-=-=-=-=-=-=--=--= If you want to go YOLO and skip to the answer, look for the HOT PINK
Legal Disclaimer: This is not a guide or tutorial. The following narrative may contain words or phrases commonly found in guides and tutorials found on forums.xda-developers.com such as "first," "then," and "make sure" which are used to portray the voice inside my head telling myself what to do, how to do it and what to expect and any references to taking steps as found in a guide or tutorial is purely coincidence. There are a number of important factors that could cause actual events or actual results of the typed narrative or therein to differ materially from those indicated by such set instructions.
Okay okay All kidding aside, you know the drill, im not responsible, dont hold me liable, try at your own risk and it may or may not work for you.
Updated 07-30-17: Some of the source file links were reported as broken and an alternative source was found by and provided courtesy of @beachbouy Thanks beachbouy!
||What the brick? How it all began (Skippable) ||
The following events occurred on my Zenfone 2 : ZE551ML, originally with firmware LRX21V.WW-ASUS_Z00A-2.20.40.198_20160930_8756 which I foolishly and carelessly used the built-in system update to install the recently transferred firmware update file. after unlocking the bootloader and installing custom recovery, OEM software detected and offered to update for me so i then assumed, it probably detected that it would be compatible right? so i thought, WTH why not?....lol um yea, no. failed but I was having a YOLO moment and just had to do it anyways.
Lesson learned and happy to be alive to tell someone my story ;P.
|| Road to Recover and Encountering the "FAILED (remote: flash_cmds error!" (Skippable) ||
How I ultimately arrived at receiving this error (and for you to decide whether or not it may work for you):
My device was limp bricked where the screen didn't turn on and would only vibrate after holding the power button as an indication of life when beginning with the unbrick guide as previously posted by asus_abz within this thread (or otherwise found here http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256)
In accordance with the guide, I was able to successfully use xfstk-downloader to get to the first checkpoint of success and arrived at the "not ..familiar ASUS screen but instead 4 color, just like some TV stations stop broadcasting on TV" Which means the device is working off of changes made with droidboot_dnx.img.POS_sign.bin, ifwi.bin, and dnx_fwr.bin
When attempting to use Asus FlashTool 1.0.0.14 to flash the .RAW image file, it would fail for reasons I fail to recall but otherwise...
Any attempts to use an elevated CMD prompt using the
Code:
fastboot flash boot boot.img
^^^^^^^^^would resultin the remote:flash_cmds error!
|| `';~-=Resolving The Issue: Say Goodbye to flash_cmds error!=-~;'` ||
If you don't already have it, downlaod the .RAW format firmware for your device from the aforementioned guide at the Asus Flasher section
Otherwise ZE551ML2.20.40.194 or ZE550ML 2.20.40.155 (direct link from guide but the one for 550 is broken)
Open (EXTRACT) the .RAW image file with Winrar, 7zip or equivalent and extract the contants of the .RAW image file to your ADB directory
Start device in bootloader and connected with fastboot and run the following commands
Code:
fastboot oem erase_osip_header
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase APD
fastboot erase ADF
fastboot erase cache
fastboot oem stop_partitioning
fastboot flash fastboot droidboot_sign.bin
Optionally (if you want to restore the full .RAW version)
Code:
fastboot flash ifwi ifwi.bin
Then seal the deal with
Code:
fastboot flash recovery recovery_sign.bin
fastboot format system
fastboot flash splashscreen splash_sign.bin
fastboot flash system system.img
fastboot flash boot boot_sign.bin
fastboot reboot
Alternatively, you can flash your own recovery and whatnot because by now you should be able to successfully run the flash command for those partitions, but I would suggest flashing back to full stock first and then flash to custom. Personally, I flashed everything from the .RAW firmware except for recovery
Code:
fastboot flash recovery twrp.img
After the device restarts it might go through the updating android apps screen so expect a longer than usual boot up.
Optionally, you can include "fastboot erase data" if you needed to have a clean reinstall (such as coming from a different version of android) but I didn't bother because I didn't ever successsfully load another ROM and for me, by not wiping data, I was able to have it restored back to how I had it before I made any experimenting with restoring my backup from before the shaninagans.
I hope this helps anyone who may have had the same issue. Hit the Thanks if it does!
nucleare GOD BLESS YOU !!! you saved my fuc***d Zenfone 2 now i can send it back to ASUS becouse the camera keep on closing. Thank you
Marvelous stuff , this should be in a thread of its own for those with gpt trouble
nucleare said:
I was getting the exact same error after using ... to unbrick my Asus Zenfone 2 ZE551ML. ... Hit the Thanks if it does!
Click to expand...
Click to collapse
Thanks, you save me!
great guide OP
Sometimes you will need the following commands too
Make sure you type the correct name
Code:
fastboot flash dnx dnx_fwr_ann_a0-mofd_v1-ze551ml.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
fastboot flash token bom-token.bin
Hnk1 said:
Sometimes you will need the following commands too
Make sure you type the correct name
Code:
fastboot flash dnx dnx_fwr_ann_a0-mofd_v1-ze551ml.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
fastboot flash token bom-token.bin
Click to expand...
Click to collapse
Thanks @Hnk1 for pointing that out! To be sure, (and feel free to correct me if I'm wrong) if I'm not mistaken, the commands are going to depend if they're unbricking from a failed Lollipop to Marshmallow brick, or a Lollipop to Lollipop update brick, or essentially the last stable android file system build prior to the brick. And just to note in case someone finds this thread far in the future, the commands referenced the filenames that originated from the extracted downloads which had been linked to tutorials and were not changed. Therefore, if restoring using alternative RAW files, one would need to adjust the img/bin files accordingly.
~-`-`-`-`-~
@Raul74 and @CrazyPhantomBR Thank you for the appreciation posts! It totally makes the time spent writing that all up worthwhile. And, I know that feeling of relief to see your device finally working again , so I am glad to have played a part in providing that experience for you guys
nucleare said:
I was getting the exact same error after using xfstk-downloader_v1.7.0.exe to unbrick my Asus Zenfone 2 ZE551ML. Not seeing a reply to your post and after searching only to find unrelated posts. I took a whack at it and after a few hours, finally got my device to boot up again *insert Dr. Frankenstein's "It's Alive!" impersonation here*. My hypothesis was that it had to do with the partitioning being read incorrectly since it was the device reporting back issues with execution of the commands. In any case, here is how I got past it.
=--=-=-=-=-=-=-=-=--=--= If you want to go YOLO and skip to the answer, look for the HOT PINK
Legal Disclaimer: This is not a guide or tutorial. The following narrative may contain words or phrases commonly found in guides and tutorials found on forums.xda-developers.com such as "first," "then," and "make sure" which are used to portray the voice inside my head telling myself what to do, how to do it and what to expect and any references to taking steps as found in a guide or tutorial is purely coincidence. There are a number of important factors that could cause actual events or actual results of the typed narrative or therein to differ materially from those indicated by such set instructions.
Okay okay All kidding aside, you know the drill, im not responsible, dont hold me liable, try at your own risk and it may or may not work for you.
||What the brick? How it all began(Skippable) ||
The following events occurred on my Zenfone 2 : ZE551ML, originally with firmware LRX21V.WW-ASUS_Z00A-2.20.40.198_20160930_8756 which I foolishly and carelessly used the built-in system update to install the recently transferred firmware update file. after unlocking the bootloader and installing custom recovery, OEM software detected and offered to update for me so i then assumed, it probably detected that it would be compatible right? so i thought, WTH why not?....lol um yea, no. failed but I was having a YOLO moment and just had to do it anyways.
Lesson learned and happy to be alive to tell someone my story ;P.
|| Road to Recover and Encountering the "FAILED (remote: flash_cmds error!" (Skippable) ||
How I ultimately arrived at receiving this error (and for you to decide whether or not it may work for you):
My device was limp bricked where the screen didn't turn on and would only vibrate after holding the power button as an indication of life when beginning with the unbrick guide as previously posted by asus_abz within this thread (or otherwise found here http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256)
When attempting to use Asus FlashTool 1.0.0.14 to flash the .RAW image file, it would fail for reasons I fail to recall but otherwise...
If you don't already have it, downlaod the .RAW format firmware for your device from the aforementioned guide at the Asus Flasher section
Otherwise ZE551ML2.20.40.194 or ZE550ML 2.20.40.155 (direct link from guide but the one for 550 is broken)
Start device in bootloader and connected with fastboot and run the following commands
Optionally (if you want to restore the full .RAW version)
Then seal the deal with
Alternatively, you can flash your own recovery and whatnot because by now you should be able to successfully run the flash command for those partitions, but I would suggest flashing back to full stock first and then flash to custom. Personally, I flashed everything from the .RAW firmware except for recovery
After the device restarts it might go through the updating android apps screen so expect a longer than usual boot up.
Optionally, you can include "fastboot erase data" if you needed to have a clean reinstall (such as coming from a different version of android) but I didn't bother because I didn't ever successsfully load another ROM and for me, by not wiping data, I was able to have it restored back to how I had it before I made any experimenting with restoring my backup from before the shaninagans.
I hope this helps anyone who may have had the same issue. Hit the Thanks if it does!
Click to expand...
Click to collapse
You rocked buddy :good:
---------- Post added at 06:46 PM ---------- Previous post was at 06:45 PM ----------
Hnk1 said:
great guide OP
Sometimes you will need the following commands too
Make sure you type the correct name
Click to expand...
Click to collapse
U 2 buddy...great work
nucleare said:
Code:
fastboot oem erase_osip_header
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase APD
fastboot erase ADF
fastboot erase cache
fastboot oem stop_partitioning
fastboot flash fastboot droidboot_sign.bin
Code:
fastboot flash recovery recovery_sign.bin
fastboot format system
fastboot flash splashscreen splash_sign.bin
fastboot flash system system.img
fastboot flash boot boot_sign.bin
fastboot reboot
Click to expand...
Click to collapse
Where other post-xFSTK instructions left me hanging, this helped immensely. Thanks so much!
nucleare said:
I was getting the exact same error after using xfstk-downloader_v1.7.0.exe to unbrick my Asus Zenfone 2 ZE551ML. Not seeing a reply to your post and after searching only to find unrelated posts. I took a whack at it and after a few hours, finally got my device to boot up again *insert Dr. Frankenstein's "It's Alive!" impersonation here*. My hypothesis was that it had to do with the partitioning being read incorrectly since it was the device reporting back issues with execution of the commands. In any case, here is how I got past it.
=--=-=-=-=-=-=-=-=--=--= If you want to go YOLO and skip to the answer, look for the HOT PINK
Legal Disclaimer: This is not a guide or tutorial. The following narrative may contain words or phrases commonly found in guides and tutorials found on forums.xda-developers.com such as "first," "then," and "make sure" which are used to portray the voice inside my head telling myself what to do, how to do it and what to expect and any references to taking steps as found in a guide or tutorial is purely coincidence. There are a number of important factors that could cause actual events or actual results of the typed narrative or therein to differ materially from those indicated by such set instructions.
Okay okay All kidding aside, you know the drill, im not responsible, dont hold me liable, try at your own risk and it may or may not work for you.
||What the brick? How it all began (Skippable) ||
The following events occurred on my Zenfone 2 : ZE551ML, originally with firmware LRX21V.WW-ASUS_Z00A-2.20.40.198_20160930_8756 which I foolishly and carelessly used the built-in system update to install the recently transferred firmware update file. after unlocking the bootloader and installing custom recovery, OEM software detected and offered to update for me so i then assumed, it probably detected that it would be compatible right? so i thought, WTH why not?....lol um yea, no. failed but I was having a YOLO moment and just had to do it anyways.
Lesson learned and happy to be alive to tell someone my story ;P.
|| Road to Recover and Encountering the "FAILED (remote: flash_cmds error!" (Skippable) ||
How I ultimately arrived at receiving this error (and for you to decide whether or not it may work for you):
My device was limp bricked where the screen didn't turn on and would only vibrate after holding the power button as an indication of life when beginning with the unbrick guide as previously posted by asus_abz within this thread (or otherwise found here http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256)
In accordance with the guide, I was able to successfully use xfstk-downloader to get to the first checkpoint of success and arrived at the "not ..familiar ASUS screen but instead 4 color, just like some TV stations stop broadcasting on TV" Which means the device is working off of changes made with droidboot_dnx.img.POS_sign.bin, ifwi.bin, and dnx_fwr.bin
When attempting to use Asus FlashTool 1.0.0.14 to flash the .RAW image file, it would fail for reasons I fail to recall but otherwise...
Any attempts to use an elevated CMD prompt using the
Code:
fastboot flash boot boot.img
^^^^^^^^^would resultin the remote:flash_cmds error!
|| `';~-=Resolving The Issue: Say Goodbye to flash_cmds error!=-~;'` ||
If you don't already have it, downlaod the .RAW format firmware for your device from the aforementioned guide at the Asus Flasher section
Otherwise ZE551ML2.20.40.194 or ZE550ML 2.20.40.155 (direct link from guide but the one for 550 is broken)
Open (EXTACT) the .RAW image file with Winrar or equivalent and extract the contants of the .RAW image file to your ADB directory
Start device in bootloader and connected with fastboot and run the following commands
Code:
fastboot oem erase_osip_header
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase APD
fastboot erase ADF
fastboot erase cache
fastboot oem stop_partitioning
fastboot flash fastboot droidboot_sign.bin
Optionally (if you want to restore the full .RAW version)
Code:
fastboot flash ifwi ifwi.bin
Then seal the deal with
Code:
fastboot flash recovery recovery_sign.bin
fastboot format system
fastboot flash splashscreen splash_sign.bin
fastboot flash system system.img
fastboot flash boot boot_sign.bin
fastboot reboot
Alternatively, you can flash your own recovery and whatnot because by now you should be able to successfully run the flash command for those partitions, but I would suggest flashing back to full stock first and then flash to custom. Personally, I flashed everything from the .RAW firmware except for recovery
Code:
fastboot flash recovery twrp.img
After the device restarts it might go through the updating android apps screen so expect a longer than usual boot up.
Optionally, you can include "fastboot erase data" if you needed to have a clean reinstall (such as coming from a different version of android) but I didn't bother because I didn't ever successsfully load another ROM and for me, by not wiping data, I was able to have it restored back to how I had it before I made any experimenting with restoring my backup from before the shaninagans.
I hope this helps anyone who may have had the same issue. Hit the Thanks if it does!
Click to expand...
Click to collapse
GOD bless you and your family for this tutorial )
nucleare said:
I was getting the exact same error after using xfstk-downloader_v1.7.0.exe to unbrick my Asus Zenfone 2 ZE551ML. Not seeing a reply to your post and after searching only to find unrelated posts. I took a whack at it and after a few hours, finally got my device to boot up again *insert Dr. Frankenstein's "It's Alive!" impersonation here*. My hypothesis was that it had to do with the partitioning being read incorrectly since it was the device reporting back issues with execution of the commands. In any case, here is how I got past it.
=--=-=-=-=-=-=-=-=--=--= If you want to go YOLO and skip to the answer, look for the HOT PINK
Legal Disclaimer: This is not a guide or tutorial. The following narrative may contain words or phrases commonly found in guides and tutorials found on forums.xda-developers.com such as "first," "then," and "make sure" which are used to portray the voice inside my head telling myself what to do, how to do it and what to expect and any references to taking steps as found in a guide or tutorial is purely coincidence. There are a number of important factors that could cause actual events or actual results of the typed narrative or therein to differ materially from those indicated by such set instructions.
Okay okay All kidding aside, you know the drill, im not responsible, dont hold me liable, try at your own risk and it may or may not work for you.
||What the brick? How it all began (Skippable) ||
The following events occurred on my Zenfone 2 : ZE551ML, originally with firmware LRX21V.WW-ASUS_Z00A-2.20.40.198_20160930_8756 which I foolishly and carelessly used the built-in system update to install the recently transferred firmware update file. after unlocking the bootloader and installing custom recovery, OEM software detected and offered to update for me so i then assumed, it probably detected that it would be compatible right? so i thought, WTH why not?....lol um yea, no. failed but I was having a YOLO moment and just had to do it anyways.
Lesson learned and happy to be alive to tell someone my story ;P.
|| Road to Recover and Encountering the "FAILED (remote: flash_cmds error!" (Skippable) ||
How I ultimately arrived at receiving this error (and for you to decide whether or not it may work for you):
My device was limp bricked where the screen didn't turn on and would only vibrate after holding the power button as an indication of life when beginning with the unbrick guide as previously posted by asus_abz within this thread (or otherwise found here http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256)
In accordance with the guide, I was able to successfully use xfstk-downloader to get to the first checkpoint of success and arrived at the "not ..familiar ASUS screen but instead 4 color, just like some TV stations stop broadcasting on TV" Which means the device is working off of changes made with droidboot_dnx.img.POS_sign.bin, ifwi.bin, and dnx_fwr.bin
When attempting to use Asus FlashTool 1.0.0.14 to flash the .RAW image file, it would fail for reasons I fail to recall but otherwise...
Any attempts to use an elevated CMD prompt using the
Code:
fastboot flash boot boot.img
^^^^^^^^^would resultin the remote:flash_cmds error!
|| `';~-=Resolving The Issue: Say Goodbye to flash_cmds error!=-~;'` ||
If you don't already have it, downlaod the .RAW format firmware for your device from the aforementioned guide at the Asus Flasher section
Otherwise ZE551ML2.20.40.194 or ZE550ML 2.20.40.155 (direct link from guide but the one for 550 is broken)
Open (EXTACT) the .RAW image file with Winrar or equivalent and extract the contants of the .RAW image file to your ADB directory
Start device in bootloader and connected with fastboot and run the following commands
Code:
fastboot oem erase_osip_header
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase APD
fastboot erase ADF
fastboot erase cache
fastboot oem stop_partitioning
fastboot flash fastboot droidboot_sign.bin
Optionally (if you want to restore the full .RAW version)
Code:
fastboot flash ifwi ifwi.bin
Then seal the deal with
Code:
fastboot flash recovery recovery_sign.bin
fastboot format system
fastboot flash splashscreen splash_sign.bin
fastboot flash system system.img
fastboot flash boot boot_sign.bin
fastboot reboot
Alternatively, you can flash your own recovery and whatnot because by now you should be able to successfully run the flash command for those partitions, but I would suggest flashing back to full stock first and then flash to custom. Personally, I flashed everything from the .RAW firmware except for recovery
Code:
fastboot flash recovery twrp.img
After the device restarts it might go through the updating android apps screen so expect a longer than usual boot up.
Optionally, you can include "fastboot erase data" if you needed to have a clean reinstall (such as coming from a different version of android) but I didn't bother because I didn't ever successsfully load another ROM and for me, by not wiping data, I was able to have it restored back to how I had it before I made any experimenting with restoring my backup from before the shaninagans.
I hope this helps anyone who may have had the same issue. Hit the Thanks if it does!
Click to expand...
Click to collapse
This Must ba a Sticky Solved Topic Not Tried yet but All Text Blog Telling my Situation
Edit:14.02.2017 GOD bless you Man Working Like a Magic Pls Mods Stick This Solution...
thank you to all for the kind words and more glad to hear it helped you. Perhaps I should rewrite the "tutorial" in a more 'toned down' and chronologically-and-well-laid out manner to be considered for sticky
EDIT: **that is of course, if the MODs see it as a worthwhile effort/meaningful contribution since this can be seen /regarded as a more lengthy answer to a troubleshooting question.
To clarify additional commands:
Hnk1 said:
Sometimes you will need the following commands too
Make sure you type the correct name
Code:
fastboot flash dnx dnx_fwr_ann_a0-mofd_v1-ze551ml.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
fastboot flash token bom-token.bin
Click to expand...
Click to collapse
For the future reference of any who stumble upon this page in the future, the aforementioned commands from @Hnk1 will apply to you if you did not use, or did not successfully flash already with, xfstk-downloader_v1.x.x to previously restore from no loading screen type brick to USB icon screen boot-loop type brick and more specifically stands in as an alternative method for flashing ifwi/dnx_fwr/droidboot/OSP as outlined in the program's (xFSTK's) Standard Operating Procedure Documentation PDF excerpt, which is commonly found with the filename "ZE550ML_ZE551ML_xFSTK_SOP.pdf" and included in many, if not all, current unbrick Zenfone methodologies.
Man, you are awesome!, i lost two fk.. days trying to do this with the asus flashtool, but no sucess, with your tip worked perfecly!.
I'm saving it offline in case somethink like it happens again, (probably will, since i love testing roms).
I have struggled to fix my bootlooping problem , After install LOS rom/ other rom and flashing the Magisk. Everything installed fine, but for some reason, after restarting the system it will get to LOS loading screen and bootloop. I attempted to install a stock rom on it, but that load fine but it WIFI and Cellular Network doesn't work. The boot loader has been unlocked Any detail instruction will be highly appreciated. Thanks
Background info, I have spent more than 1 years using this awesome phone with Lineage OS 15.1 , I wake up one morning with the constantly boot looping. I have the T-Mobile version with the bootloader unlocked. I have also spent weeks going through and following other threads but haven't been able to resolved my issue.
sammd301 said:
I have struggled to fix my bootlooping problem , After install LOS rom/ other rom and flashing the Magisk. Everything installed fine, but for some reason, after restarting the system it will get to LOS loading screen and bootloop. I attempted to install a stock rom on it, but that load fine but it WIFI and Cellular Network doesn't work. The boot loader has been unlocked Any detail instruction will be highly appreciated. Thanks
Background info, I have spent more than 1 years using this awesome phone with Lineage OS 15.1 , I wake up one morning with the constantly boot looping. I have the T-Mobile version with the bootloader unlocked. I have also spent weeks going through and following other threads but haven't been able to resolved my issue.
Click to expand...
Click to collapse
Whenever you move from custom to stock and vice versa you should format user data. Easiest way is in bootloader mode, issue the command 'fastboot -w' w/o quotes.
41rw4lk said:
Whenever you move from custom to stock and vice versa you should format user data. Easiest way is in bootloader mode, issue the command 'fastboot -w' w/o quotes.
Click to expand...
Click to collapse
I applied the "fastboot -w" below is the output I got; Still no WIFI and Cellular network not working
-------------------------------------------------------------
PS C:\adb> fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type not supported.
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.005s
-------------------------------------------------
sammd301 said:
I applied the "fastboot -w" below is the output I got; Still no WIFI and Cellular network not working
-------------------------------------------------------------
PS C:\adb> fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type not supported.
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.005s
-------------------------------------------------
Click to expand...
Click to collapse
Do you have an imei number still? Is the bootloader still unlocked? Have you tried following the return to stock thread and doing a clean install of the latest TMO firmware?
41rw4lk said:
Do you have an imei number still? Is the bootloader still unlocked? Have you tried following the return to stock thread and doing a clean install of the latest TMO firmware?
Click to expand...
Click to collapse
The IMEI number is “Unknown” , Yes the bootloader is Unlocked because, I am able to flash TWRP image on the phone. Yes I spent close to a week following the return to stock thread, the first time I did it, the Cellular network come on about 30 minutes after the phone completed loading to the home screen. Thanks for the guidance
You need to blankflash, then flash the latest TMO firmware for your phone. Usually you lose baseband when you flash the wrong firmware, does it say XT1789-04 by the usb port?
sammd301 said:
The IMEI number is “Unknown” , Yes the bootloader is Unlocked because, I am able to flash TWRP image on the phone. Yes I spent close to a week following the return to stock thread, the first time I did it, the Cellular network come on about 30 minutes after the phone completed loading to the home screen. Thanks for the guidance
Click to expand...
Click to collapse
I would go through the unlock process again. Your bootloader shows flashing_locked
Uzephi said:
I would go through the unlock process again. Your bootloader shows flashing_locked
Click to expand...
Click to collapse
I follow the procedure to unlocked the bootloader again, it now shows "flashing_unlocked" as show in the photo below; I flashed another oem rom but still no wifi and network and Still Baseband /Baseline is < not found>
sammd301 said:
I follow the procedure to unlocked the bootloader again, it now shows "flashing_unlocked" as show in the photo below; I flashed another oem rom but still no wifi and network and Still Baseband /Baseline is < not found>
Click to expand...
Click to collapse
Can you link the flash all you used and how you flashed it?
Uzephi said:
Can you link the flash all you used and how you flashed it?
Click to expand...
Click to collapse
I have been following this tread on xda [ https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783 ]
Below is the steps
How to fix your phone:
Download the Utilities zip Link to the flash all https://www.androidfilehost.com/?fid=5862345805528053597
Extract the zip to it's own folder
Download the flash all for your device from the options below.
Extract the flash all zip into the same folder as the Utilities.
Run the Flashall.bat file
Watch windows command prompt put your phone back to stock!
sammd301 said:
I have been following this tread on xda [ https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783 ]
Below is the steps
How to fix your phone:
Download the Utilities zip Link to the flash all https://www.androidfilehost.com/?fid=5862345805528053597
Extract the zip to it's own folder
Download the flash all for your device from the options below.
Extract the flash all zip into the same folder as the Utilities.
Run the Flashall.bat file
Watch windows command prompt put your phone back to stock!
Click to expand...
Click to collapse
What zip did you use?
Edit: that thread uses AFH which has an older version bootloader than in your picture so something isn't going right. How long does it take to flash?
Edit 2: does your phone reboot after running the .bat file?
I used the T-Mobile Flash All zip the link was to google drive https://drive.google.com/file/d/1Bo_ry_38J6BHy4-A4fuhAnv94C5yV1TW/edit
sammd301 said:
I used the T-Mobile Flash All zip the link was to google drive https://drive.google.com/file/d/1Bo_ry_38J6BHy4-A4fuhAnv94C5yV1TW/edit
Click to expand...
Click to collapse
Yeah, that one is old. Try https://androidfilehost.com/?fid=11410963190603877456 just like the guide states, it should open command prompt and you should see it flashing. The process can take s minute or two. If it immediately closes within 30 seconds or hangs, it didn't flash
Uzephi said:
What zip did you use?
Edit: that thread uses AFH which has an older version bootloader than in your picture so something isn't going right. How long does it take to flash?
Edit 2: does your phone reboot after running the .bat file?[/QUOTE
Yes the phone does reboot by itself after running the .bat file, But it reboot back to bootloader screen.
Click to expand...
Click to collapse
Uzephi said:
Yeah, that one is old. Try https://androidfilehost.com/?fid=11410963190603877456 just like the guide states, it should open command prompt and you should see it flashing. The process can take s minute or two. If it immediately closes within 30 seconds or hangs, it didn't flash
Click to expand...
Click to collapse
I download the suggested rom [ https://androidfilehost.com/?fid=11410963190603877456 ] and flashed it to my phone running flashall.bat via Windows PowerShell,
It took approximately 6 minutes for the flashing to be complete, but with some minor error, Afterword the phone reboot back to the bootloader screen. After starting it still doesn't show the IMEI number and No cellular network or WIFI available.
The output of the flashing process is below along with the attach screenshot of the error;
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.803s]
finished. total time: 0.807s
sammd301 said:
I download the suggested rom [ https://androidfilehost.com/?fid=11410963190603877456 ] and flashed it to my phone running flashall.bat via Windows PowerShell,
It took approximately 6 minutes for the flashing to be complete, but with some minor error, Afterword the phone reboot back to the bootloader screen. After starting it still doesn't show the IMEI number and No cellular network or WIFI available.
The output of the flashing process is below along with the attach screenshot of the error;
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.803s]
finished. total time: 0.807s
Click to expand...
Click to collapse
Flash again, after it is done, type fastboot --set-active=other and then run it one last time. Then boot your phone.
Uzephi said:
Flash again, after it is done, type fastboot --set-active=other and then run it one last time. Then boot your phone.
Click to expand...
Click to collapse
After flashing the rom again, and getting the error " Erase successful, but not automatically formatting..." I input the fastboot command "fastboot --set-active=other" and I got back "unknown option -- set-active=other" as show in the image below. Was the syntax right?
I have been googling the errors I have received like "Erase successful, but not automatically formatting.
File system type raw not supported" to see if I can land on page that can help resolve the issue with the phone.
I have downloaded the latest adb and fastboot platform tools versions, after running the flashall.bat file, I still got the same error at the end. I follow up with the "fastboot --set-active=other" command and this time I got [ Setting current slot to '`' FAILED (remote: '') ] as show in the image below.
sammd301 said:
I have downloaded the latest adb and fastboot platform tools versions, after running the flashall.bat file, I still got the same error at the end. I follow up with the "fastboot --set-active=other" command and this time I got [ Setting current slot to '`' FAILED (remote: '') ] as show in the image below.
Click to expand...
Click to collapse
Seems it isn't recognizing other then, which it should. Do =_b then to see if you can swap to slot B
Uzephi said:
Seems it isn't recognizing other then, which it should. Do =_b then to see if you can swap to slot B
Click to expand...
Click to collapse
After inputting the command [ fastboot --set-active=_b ] the output I got back was [ Slot _b does not exist. supported slots are:
a
b ]
I proceed to input [ fastboot --set-active=b ] the output was [ Setting current slot to 'b' ]
So I the flashing again and input the [ fastboot --set-active=b ] again and got back [ Setting current slot to 'b' ]
I pressed the power button to start the phone from bootloader menu , the phone boot-loop with the Motorola logo as show, after 6 to 8 cycling of the boot looping with the Motorola logo the phone bootup again with T-Mobile logo. When it got home screen, I saw again that Network and cellular still not working and No IMEI number too.
I have an odd problem that I never experienced before, maybe some have? Using Linux (Arch with android-tools installed), I'm trying to unlock my XZ2C like I have done lots of time with "sudo fastboot oem unlock 0x". But, this time it just wont run. The cursor jumps about 30 characters (spaces I guess) and just sits there, nothing else happens. Have to pull the cable to the phone to "abort" fastboot. It looks like this (the FAILED part is what I get after I pull the cable);
Code:
*#*sudo fastboot oem unlock 0x9366CB600ED6A33C
[sudo] lösenord för zynex:
< waiting for any device >
FAILED (Status read failed (No such device))
fastboot: error: Command failed
I have tried change the cable, but still the same. Any ideas?? I read in the twrp thread about a bootloader bug, not sure if that have something to do with it. I'm on latest fw (52.0.A.10.6).
PS, yes I have OEM unlock checked, ADB debug etc etc...
-- Mike
zynexx said:
I have an odd problem that I never experienced before, maybe some have? Using Linux (Arch with android-tools installed), I'm trying to unlock my XZ2C like I have done lots of time with "sudo fastboot oem unlock 0x". But, this time it just wont run. The cursor jumps about 30 characters (spaces I guess) and just sits there, nothing else happens. Have to pull the cable to the phone to "abort" fastboot. It looks like this (the FAILED part is when what I get after I pull the cable);
Code:
*#*sudo fastboot oem unlock 0x9366CB600ED6A33C
[sudo] lösenord för zynex:
< waiting for any device >
FAILED (Status read failed (No such device))
fastboot: error: Command failed
I have tried change the cable, but still the same. Any ideas?? I read in the twrp thread about a bootloader bug, not sure if that have something to do with it. I'm on latest fw (52.0.A.10.6).
PS, yes I have OEM unlock checked, ADB debug etc etc...
-- Mike
Click to expand...
Click to collapse
Latest is 11.3
I would update first
Do you use at least platform tools v29.0.4?
Is the phone in the blue led fastboot mode?
MartinX3 said:
Latest is 11.3
I would update first
Do you use at least platform tools v29.0.4?
Is the phone in the blue led fastboot mode?
Click to expand...
Click to collapse
Ah, seems that 11.3 hasn't been released here yet then, still says I'm up to date. Not sure if that's the issue here thou?
Yep, use android-tools v29.0.4-2, that's the latest release on Arch Linux.
Yes, it's blue. It finds the device when running fastboot devices, and continues after the "waiting for any device" part, but get stuck after that. Never had this issue before, so I'm not sure where to start. Maybe an issue with the bootloader itself?
zynexx said:
Ah, seems that 11.3 hasn't been released here yet then, still says I'm up to date. Not sure if that's the issue here thou?
Yep, use android-tools v29.0.4-2, that's the latest release on Arch Linux.
Yes, it's blue. It finds the device when running fastboot devices, and continues after the "waiting for any device" part, but get stuck after that. Never had this issue before, so I'm not sure where to start. Maybe an issue with the bootloader itself?
Click to expand...
Click to collapse
The bootloader didn't change since months
Do you use the correct code or only "0x"?
And does "fastboot getvar all" gives you output?
(Bootloader version should be 118)
Can't install TWRP on XZ2C
Guys, trying to install TWRP recovery in Fastboot, posting that code: "fastboot flash boot twrp-3.2.3-0-xz2p.img" and it says that "twrp-3.2.3-0-xz2p.img not found", although i've put .img file in ADB directory. Can't figure it out
MartinX3 said:
The bootloader didn't change since months
Do you use the correct code or only "0x"?
And does "fastboot getvar all" gives you output?
(Bootloader version should be 118)
Click to expand...
Click to collapse
I used the code I got from Sony. Maybe should check so I entered the correct IMEI?
Yep, did get a bunch of stuff from it. Can post it if it would help?
m4ikl1983 said:
Guys, trying to install TWRP recovery in Fastboot, posting that code: "fastboot flash boot twrp-3.2.3-0-xz2p.img" and it says that "twrp-3.2.3-0-xz2p.img not found", although i've put .img file in ADB directory. Can't figure it out
Click to expand...
Click to collapse
Bit of topic here, but check so you have read permission for the file (if using Linux). Not sure what you mean by ADB directory, but I guess you mean the directory you have the binary in? You will need to provide the full path to the image file (if you are not in the same directory), fx ~/Download/yourimage.img.
MartinX3 said:
The bootloader didn't change since months
Do you use the correct code or only "0x"?
And does "fastboot getvar all" gives you output?
(Bootloader version should be 118)
Click to expand...
Click to collapse
Not sure why, but I think I entered the wrong IMEI last time. Although, I get the same problem. Running the command, the cursor just jumps like 30-35 characters to the right and stays there, not additional text. Have to pull the cable to abort the command.
This is some of the output from getvar (omitted the partition part);
(bootloader) hw-revision:20001
(bootloader) unlocked:no
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4015
(bootloader) version-baseband:1311-5320_52.0.A.10.6
(bootloader) version-bootloader:1310-7079_X_Boot_SDM845_LA2.0_P_118
(bootloader) erase-block-size: 0x1000
(bootloader) logical-block-size: 0x1000
(bootloader) variant:SDM UFS
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:b
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:6
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno:BH901602BZ
(bootloader) serial:28b51f27
(bootloader) product:H8324
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
Click to expand...
Click to collapse
Ok, this was pretty odd. While typing the last comment here, I had run the unlock command and it was just sitting there in the backgrund for a couple of minutes, nothing happened. Pulled the cable, and then the bootloader was magically unlocked anyway. So problem fixed. Not sure why I didn't get any output from the command though
One question though, when rebooting I get a lock pad icon and the text "You device software can't be checked for corruption. Please lock your bootloader". Never seen that on a Sony device before. Is his a new thing?
m4ikl1983 said:
Guys, trying to install TWRP recovery in Fastboot, posting that code: "fastboot flash boot twrp-3.2.3-0-xz2p.img" and it says that "twrp-3.2.3-0-xz2p.img not found", although i've put .img file in ADB directory. Can't figure it out
Click to expand...
Click to collapse
Please follow the TWRP instructions in the TWRP thread.
Your command is wrong.
---------- Post added at 02:03 PM ---------- Previous post was at 02:01 PM ----------
zynexx said:
Ok, this was pretty odd. While typing the last comment here, I had run the unlock command and it was just sitting there in the backgrund for a couple of minutes, nothing happened. Pulled the cable, and then the bootloader was magically unlocked anyway. So problem fixed. Not sure why I didn't get any output from the command though
One question though, when rebooting I get a lock pad icon and the text "You device software can't be checked for corruption. Please lock your bootloader". Never seen that on a Sony device before. Is his a new thing?
Click to expand...
Click to collapse
Nice to hear that it works now.
I never saw a android device which doesn't mention on boot that it got unlocked.
So it isn't new for me.
Ahh btw
Since you unlocked on 9.0 your camera will still work in stock.
(In custom rom anyway but there the camera is under construction and get its next update this or next month, but only on android 10.0 with 4.14 kernel).
MartinX3 said:
Please follow the TWRP instructions in the TWRP thread.
Your command is wrong.
---------- Post added at 02:03 PM ---------- Previous post was at 02:01 PM ----------
Nice to hear that it works now.
I never saw a android device which doesn't mention on boot that it got unlocked.
So it isn't new for me.
Ahh btw
Since you unlocked on 9.0 your camera will still work in stock.
(In custom rom anyway but there the camera is under construction and get its next update this or next month, but only on android 10.0 with 4.14 kernel).
Click to expand...
Click to collapse
Tried the camera, and it works like a charm
Oh, I never saw anything like it on my other Xperias, just the normal Sony logo The only device I seen it on is Samsungs.
Althougt, I still having problem now that I'm about to flash TWRP. Get the same problem as before, just
hangs there without anything happens.
Code:
Sending 'boot.img' (30904 KB) #FAILED (remote: 'unknown command')
fastboot: error: Command failed
The # is where the cursor is, and when i pull the cable I get FAILED. This is pretty odd.
zynexx said:
Tried the camera, and it works like a charm
Oh, I never saw anything like it on my other Xperias, just the normal Sony logo The only device I seen it on is Samsungs.
Althougt, I still having problem now that I'm about to flash TWRP. Get the same problem as before, just
hangs there without anything happens.
Code:
Sending 'boot.img' (30904 KB) #FAILED (remote: 'unknown command')
fastboot: error: Command failed
The # is where the cursor is, and when i pull the cable I get FAILED. This is pretty odd.
Click to expand...
Click to collapse
Did you follow the twrp instructions carefully including the correct booting into the fastboot mode?
MartinX3 said:
Did you follow the twrp instructions carefully including the correct booting into the fastboot mode?
Click to expand...
Click to collapse
Yep, I read about the bug and booted into fastboot with adb. But still hangs the same way when I tried unlocking the bootloader itself. Also downloaded the platform tools from Google and tried the fastboot from there, but still same outcome.
Is there another way to flash TWRP, think I seen a app of some kind long ago. But I guess I need to have it rooted before I can use it. Think I have a moment 22 situation here :/
zynexx said:
Yep, I read about the bug and booted into fastboot with adb. But still hangs the same way when I tried unlocking the bootloader itself. Also downloaded the platform tools from Google and tried the fastboot from there, but still same outcome.
Is there another way to flash TWRP, think I seen a app of some kind long ago. But I guess I need to have it rooted before I can use it. Think I have a moment 22 situation here :/
Click to expand...
Click to collapse
That's a very weird situation
Did you try it with another computer?
Or with linux instead of windows?
Or switched the slot to slot A with "fastboot --set-active=a" ?
That also requires to flash the newest 11.3 stock firmware again.
(With xperifirm and newflasher from XDA since OTA won't work any longer.)
MartinX3 said:
That's a very weird situation
Did you try it with another computer?
Or with linux instead of windows?
Or switched the slot to slot A with "fastboot --set-active=a" ?
That also requires to flash the newest 11.3 stock firmware again.
(With xperifirm and newflasher from XDA since OTA won't work any longer.)
Click to expand...
Click to collapse
Just tried with another one, running KDE Neon. Same problem. Always using Linux, don't even own a Windows system
Tried fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img, but that one got stuck to. Nothing happens. I will try flash 11.3 and see is that might solve the issue I have.
zynexx said:
Just tried with another one, running KDE Neon. Same problem. Always using Linux, don't even own a Windows system
Tried fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img, but that one got stuck to. Nothing happens. I will try flash 11.3 and see is that might solve the issue I have.
Click to expand...
Click to collapse
So weird.
You use google plattform tools v29.x and I assume a up to date linux distribution? (I tested it with at least kernel 4.15, running 5.0 now).
Since we both use the same bootloader, it must be something in your hardware or usb cable which disturbs the communication.
MartinX3 said:
So weird.
You use google plattform tools v29.x and I assume a up to date linux distribution? (I tested it with at least kernel 4.15, running 5.0 now).
Since we both use the same bootloader, it must be something in your hardware or usb cable which disturbs the communication.
Click to expand...
Click to collapse
Yep, downloaded the latest one from Google to but got the same error. Using Arch, so it's very up to date Using kernel 5.3.7-arch1-2-ARCH. Have tried another USB cable to, I will see if I can dig out a third one and try.
Btw, seems that NCB firmware are still at 10.6, that' why I haven't gotten any update yet.
zynexx said:
Yep, downloaded the latest one from Google to but got the same error. Using Arch, so it's very up to date Using kernel 5.3.7-arch1-2-ARCH. Have tried another USB cable to, I will see if I can dig out a third one and try.
Btw, seems that NCB firmware are still at 10.6, that' why I haven't gotten any update yet.
Click to expand...
Click to collapse
No woories, the 11.3 is only relevant for the TWRP installation.
A "fastboot boot twrp.img" should still work.
Maaaaybe the kernel is too new and contains a driver bug?
MartinX3 said:
No woories, the 11.3 is only relevant for the TWRP installation.
A "fastboot boot twrp.img" should still work.
Maaaaybe the kernel is too new and contains a driver bug?
Click to expand...
Click to collapse
I downloaded Customized DE 11.3 and flashed it, but still have problem trying fastboot boot twrp.img.
This is very odd indeed. Don't think it's the kernel, the other computer has kernel 4.4.
Starting to think there's an problem with the phone itself, whatever that could be!?
MartinX3 said:
No woories, the 11.3 is only relevant for the TWRP installation.
A "fastboot boot twrp.img" should still work.
Maaaaybe the kernel is too new and contains a driver bug?
Click to expand...
Click to collapse
It seems that I can't do anything regarding fastboot, except rebooting it. Nothing else work, tried fastboot --set-active=a, but nothing happens at all. Tried fastboot flash boot twrp.img, same thing. Fastboot executes, but then nothing. Have to pull the cable to abort the program.
Have never in all the years I played with Android phones run into this stuff. Fastboot has always worked.
Code:
*# sudo fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.051s
*# sudo fastboot --set-active=a
<no output after this>
Preparation:
Notes are important, please pay attention
ONLY use stock USB-A to USB-C cable
I have tried the stock cable from Axon 7, fail fail and more fail, don't make this mistake
DON'T store flash files on USB storage.
fastboot will timeout if your flash files are stored at a slow storage device such as a USB drive, or slow computer with eMMC drive
Download and extract the patched MSM download tool and related flash files (credit)
Download and extract TWRP 3.4.0-2 Test by mauronofrio (credit)
Download and extract 10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT.zip (credit)
Optional: Unlock bootloader at this official OnePlus page with those steps
automated process you have to wait 1 whole week for
if you take this route, you will have an easier time get into EDL
Optional for Driver and boot into EDL: Download and extract the TOOL ALL IN ONE (credit) (untested) (can skip this step if you have driver and completed preparation step 7)
Flash Operations:
Run the MSM executable with Administrator Privilege
Boot into bootloader on 7T (if you already have adb connection, adb reboot bootloader would work as well)
Restart device: Vol Up + Power
Boot into recovery: when system reboot from step 4, immediately press and hold Vol Down + Power until recovery screen
Boot into fastboot: English -> Advanced -> fastboot
Boot into EDL on 7T
If you have OnePlus unlock token from Preparation step 7
Connect USB cable to both PC and 7T
on MSMDownloadTool, click Enum to display your device
fastboot flash cust-unlock unlock_token.bin
fastboot oem unlock
fastboot boot twrp.img
when TWRP boot: adb reboot edl
on MSMDownloadTool it will now show connected
If you don't want to wait for token (untested)
Use TOOL ALL IN ONE
Or, hold down the buttons then click start in MSM. If you release the volume buttons early it will kick you out of EDL--well at least for me. you can release the buttons once MSM starts (credit)
When MsmDownloadTool display connected, hit Start until 7T display CORRUPT message (normal behavior) and reboot into fastboot by ITSELF. If your 7T doesn't get into fastboot screen automatically, something is wrong with previous step, redo EDL flashing and do NOT proceed.
Start Power-Shell with Administrator Privilege and go to the extracted path of 10.0.13-global-oneplus7toxygen_14.o.19_ota_019_all_2009281709_1026-fastboot.zip (DO NOT USE DOS, it will fail you miserably)
Unlock bootloader: .\fastboot flashing unlock_critical (suggested, because it works, so I didn't test the oem unlock method)
To avoid potential conflict with installed fastboot binary (possibly lower version), you can either
edit the flash-all.bat, and change fastboot to .\fastboot, such that only the local fastboot binary will be invoked instead of pathed binary
OR run those identical commands with copy and paste
Code:
.\fastboot -w
.\fastboot flash boot boot.img
.\fastboot flash dtbo dtbo.img
.\fastboot flash modem modem.img
.\fastboot flash reserve reserve.img
.\fastboot flash recovery recovery.img
.\fastboot --disable-verity flash vbmeta vbmeta.img
.\fastboot --disable-verity flash vbmeta_system vbmeta_system.img
.\fastboot reboot fastboot
.\fastboot flash abl abl.img
.\fastboot flash aop aop.img
.\fastboot flash bluetooth bluetooth.img
.\fastboot flash cmnlib cmnlib.img
.\fastboot flash cmnlib64 cmnlib64.img
.\fastboot flash devcfg devcfg.img
.\fastboot flash dsp dsp.img
.\fastboot flash hyp hyp.img
.\fastboot flash imagefv imagefv.img
.\fastboot flash keymaster keymaster.img
.\fastboot flash LOGO LOGO.img
.\fastboot flash multiimgoem multiimgoem.img
.\fastboot flash odm odm.img
.\fastboot flash oem_stanvbk oem_stanvbk.img
.\fastboot flash opproduct opproduct.img
.\fastboot flash qupfw qupfw.img
.\fastboot flash storsec storsec.img
.\fastboot flash tz tz.img
.\fastboot flash uefisecapp uefisecapp.img
.\fastboot flash xbl xbl.img
.\fastboot flash xbl_config xbl_config.img
.\fastboot flash system system.img
.\fastboot flash vendor vendor.img
.\fastboot flash product product.img
.\fastboot reboot
Few notes
User data is wiped, again, lol
reserve partition flashing can produce error msg: FAILED (remote: '(reserve_a) No such partition'), it is OK but others should not Fail
Device will reboot once during the flashing process
After reboot, device will NOT go into fastboot screen but instead go into stock recovery screen, however fastboot will pick up and resume flashing the rest, ONLY IF YOU ARE UNDER POWER-SHELL, so DO NOT flash under DOS
if anything else fails besides the reserve partition, repeat step 7
Device will boot into system, you may use the OS updater to upgrade to the lastest firmware then relock bootloader or proceed with root with Magisk
Hope this will save you some precious time. Major kudos for previous contributions from post 1 and post 2.
All steps are recorded from memory, please let me know if any mistakes are in need of correction.
Tested working on Dec 5, 2020
I have followed this method (and literally anything else I can find) to a T and the farthest I get is when flashing the ROM, I get "Flashing is not allowed for critical partitions" - which I can only find people saying that means the bootloader needs to be unlocked, but it is?! It's definitely, fully unlocked. No matter what I try I can't get around that error during the flashing process and it stays stuck on the T-Mobile ROM.
I had the same issue with the critical partition error when I was under DOS and during the reboot process, 7T will only boot into the normal fastboot screen. In here, I always gets that error over and over. I stopped getting it when 7T boot into the recovery screen under power-shell.
Few things to make sure:
Stock cable
Power-shell in admin priv
Use local fastboot binary
If things still not looking up, I would try a different PC.
Good luck.
Yup, those are all correct and I have tried another PC. Now I'm scared I may have bricked it, because other than booting it into FastBoot it just loops on the "Your device is corrupted" screen. Any thoughts? It did this after I re-locked the bootloader to try unlocking Critical again.
Is your device is corrupt screen the one that gets displayed after the MSM EDL flashing?
If so, does your device auto boot into fastboot afterwards?
My thinking is after MSM tool, your device is corrupted, then you unlock critical flashing. Afterwards, the partitions being flashed in by the fastboot should prevent the corrupt msg being displayed. If you are all getting corrupt msg after the fastboot reboot, then something is off with the first part of your fastboot flashing.
It's that same screen, yes, but the phone is just stuck in a boot loop. It says "Your device is corrupt. It can't be trusted and will not boot." and goes black and says it again, over and over. It will not automatically boot to Fastboot, but if I mess with the volume/power keys, I can get it to the fastboot screen. But no matter what else I do it goes back to an endless loop with the corrupt message.
I think some error could have been carried over from the MSMDownloadTool flashing process. My 7T always auto boot into fastboot screen after the corrupt msg display without interaction on my end.
Try your EDL flashing part again, and at the same time, re-download the preparation step 4 file over again and try use that instead afterwards if you are still stuck on the boot loop, just to prevent possible discrepancies might be caused by corrupted file (unlikely, but it doesn't hurt right?)
Gotcha, thanks. Got it into EDL mode and am running MSM right now.
Okay, EDL/MSM was successful, then I tried flashing the ROM per the instructions again but got the same error of being unable to flash to Critical. It no longer does the "device is corrupt" error boot loop, but the phone ONLY boots to Fastboot now, no matter what I do.
Best of luck. Hope the pain stops for you soon, hah.
Can you post your power-shell display message for the last flash-all.bat invocation?
Also, are you using .\fastboot flashing unlock_critical in admin priv power-shell to unlock the bootloader after MSM flashing?
Yes, that's what I was using. Unlocking it wasn't an issue, and when I try any type of unlock command it says it's already unlocked, which I believe to be true. But it still refuses to write to critical.
I can post my powershell message when I get back home. But basically it ran fine at first, it did fail at the "reserve" portion which I read to be normal, but after that it kept saying cannot flash to critical.
I just got the phone today so I hope it's not already bricked. But the fact that I got it out of the "corrupt" loop gives me hope I can fix it. Is there any place to download the stock T-Mobile ROM so I can try and start over? Assuming it will even let me flash it. I couldn't find any by searching.
One observation I found to be very interesting.
The device should have been locked by the MSM tool through EDL flashing; yet, your device shows it's already unlocked.
I think the issue is still with your EDL flashing process as it should lock the bootloader then use flashing unlock critical to prevent critical partition flashing errors.
Also, your device is not bricked as long as you can still perform EDL flash. Just kept going and you can get it working without having to EDL flash anything else.
I see, thanks for the insight. So just so I don't mess anything up further, exactly what steps in what order do you recommend I perform?
My first instinct is to keep trying the EDL flashing until you can perform flashing critical unlock properly.
If things keep on failing, try to change your PC, driver, or other environmental variables.
It's just a painful process of elimination that you have to stick to.
Also, unless there are potential hardware issues, flashing like this shouldn't carry any more risk to brick your device compare to just using your device regularly. You aren't changing the hardware/software that is responsible for facilitating EDL.
EDL is fine, unlock_critical is fine, but flash-all gives me the same 'Flashing is not allowed for Critical Partitions' error on some partitions, and then I get stuck on the T-Mobile boot screen after. I'd think it wouldn't be the TMo screen by that point, right?
I've gone through this twice with the OEM cable and a different cable. The device was up to date with the latest TMo OTA before I started.
I'm about to try the TMo MSM to see if I can get it back to a working state.
Do you want to wipe all the data ( Reccomended )[Y/N]?nSending 'boot_a' (98304 - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
seryniti said:
EDL is fine, unlock_critical is fine, but flash-all gives me the same 'Flashing is not allowed for Critical Partitions' error on some partitions, and then I get stuck on the T-Mobile boot screen after. I'd think it wouldn't be the TMo screen by that point, right?
I've gone through this twice with the OEM cable and a different cable. The device was up to date with the latest TMo OTA before I started.
I'm about to try the TMo MSM to see if I can get it back to a working state.
Do you want to wipe all the data ( Reccomended )[Y/N]?nSending 'boot_a' (98304 - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
Click to expand...
Click to collapse
Edit:
[GUIDE][WIP]T-Mobile Brand Conversion to Rooted Global Firmware
First, let me say that this is only an attempt to pull this information out from a lot of different threads that require a bunch of research and a lot of institutional knowledge of Android. The idea of this thread is going from 100% T-Mobile...
forum.xda-developers.com
Apparently I'm not getting into FastbootD, so it's not flashing on the proper place. I'm going to try again. I noticed earlier when it runs "fastboot reboot fastboot" it's not working properly.
seryniti said:
Edit:
[GUIDE][WIP]T-Mobile Brand Conversion to Rooted Global Firmware
First, let me say that this is only an attempt to pull this information out from a lot of different threads that require a bunch of research and a lot of institutional knowledge of Android. The idea of this thread is going from 100% T-Mobile...
forum.xda-developers.com
Apparently I'm not getting into FastbootD, so it's not flashing on the proper place. I'm going to try again. I noticed earlier when it runs "fastboot reboot fastboot" it's not working properly.
Click to expand...
Click to collapse
Let me know what you find. I didn't even know there was other versions of MSM so I'll try that as well. I'd love to just at least get mine out of only being able to boot to Fastboot.
seryniti said:
Edit:
[GUIDE][WIP]T-Mobile Brand Conversion to Rooted Global Firmware
First, let me say that this is only an attempt to pull this information out from a lot of different threads that require a bunch of research and a lot of institutional knowledge of Android. The idea of this thread is going from 100% T-Mobile...
forum.xda-developers.com
Apparently I'm not getting into FastbootD, so it's not flashing on the proper place. I'm going to try again. I noticed earlier when it runs "fastboot reboot fastboot" it's not working properly.
Click to expand...
Click to collapse
Your 7T should be on the stock recovery screen when fastboot reboot fastboot completes. If your device boots into T-Mobile boot screen or bootloader, something is wrong with your env on PC.
You should never see T-Mobile boot screen at any given time during fastboot flashing process.
The final reboot should complete the conversion and boot into the intentional version OS.
I've been disappointed with some of the firmware here, like Lineage and Arrow. Havoc has been my favorite, but when we transitioned from Havoc Android 10 (3.*) to Android 11 (4.*) I have lost LTE every morning, which means no texts, no data, no phone calls. I have to power down and up and who knows when I'd lose LTE again.
Also with TWRP I could not slide the unock, and trying to select files the screen mapping is all wrong, meaning I'd touch a file at the bottom and a file toward the top would be selected. I don't know why the problems were because no one has ever been able to communicate the structure and framework of Android coherently. It seems that most just know parts of it intuitively, not the whole intellectually.
So I have to resort to Stock. I thought maybe installing Stock then Havoc 4.8 would solve the LTE problem, but when doing that Havoc's boot just circles around forever.
So without further adieu here is how to install Stock on your Moto G Power. Mine is US T-Mobile on an XT2041-4.
Get the firmware here: https://mirrors.lolinet.com/firmware/moto/sofia/official/
I hit RETUS and RETUS_10 for Retail US Android 10. If you have a different carrier or nation try and decipher which is right for you. Use 10 as Beetle says below. (as of Jan, 2022, Havoc 4.12)
Unzip this file into its own directory and you will get a series of images and .xml files. Boot your phone into fastboot mode by turning it off, then hold {VolDown}{Power} at the same time to go into fastboot mode. In this case you do -not- then reboot into fastbootd mode! Just leave it like this and connect to your computer.
Code:
# fastboot devices
... should give you something like
Code:
ZY227VX6NG fastboot
Good, your computer sees the phone.
Go into the firmware directory. A key file here is flashfile.xml. This tells you exactly how these image files must be applied to the phone and in what order. I'll show below the files and procedure for my phone, but yours may be different so refer to that flashfile for your firmware.
The first file to flash is important. It sets up the partitions on the phone properly:
Code:
# fastboot flash partition gpt.bin
Now just work your way down flashfile. Here's mine:
Code:
# fastboot flash bootloader bootloader.img
# fastboot flash vbmeta vbmeta.img
# fastboot flash radio radio.img
# fastboot flash bluetooth BTFM.bin
# fastboot flash dsp dspso.bin
# fastboot flash logo logo.bin
# fastboot flash boot boot.img
# fastboot flash dtbo dtbo.img
# fastboot flash recovery recovery.img
# fastboot flash super super.img_sparsechunk.0
# fastboot flash super super.img_sparsechunk.1
# fastboot flash super super.img_sparsechunk.2
# fastboot flash super super.img_sparsechunk.3
# fastboot flash super super.img_sparsechunk.4
# fastboot flash super super.img_sparsechunk.5
# fastboot flash super super.img_sparsechunk.6
# fastboot flash super super.img_sparsechunk.7
# fastboot flash super super.img_sparsechunk.8
# fastboot flash super super.img_sparsechunk.9
# fastboot flash super super.img_sparsechunk.10
# fastboot flash super super.img_sparsechunk.11
# fastboot flash super super.img_sparsechunk.12
# fastboot flash super super.img_sparsechunk.13
# fastboot flash super super.img_sparsechunk.14
# fastboot flash super super.img_sparsechunk.15
# fastboot erase carrier
# fastboot erase userdata
# fastboot erase metadata
# fastboot erase ddr
# fastboot oem fb_mode_clear
And that's it. Reboot. It will take a while the first time so don't interrupt it. You're back to stock.
If you were trying to flash havoc over android 11 firmware, it wont work. These roms need android 10 as a base.
Ah, that explains it. I think Havoc is the best, but 4.6 and 4.8 reliably drop LTE for me mornings. It's caused business problems.
I now find that it's impossible to tear G**gle out of Stock, so that's out for me. Maybe Arrow or something.
What carrier do you have? I'm getting ready to put maybe Havoc or Linage on this phone, but need to know what to watch out for.
It seems to be like Android 11 is a common denominator in a lot of the issues I've seen people having. That's why I have no intention of even moving to a custom rom based on 11 for a good while. I'll be staying at Lineage 17 or Havoc 3 until I have no other choice. There's nothing in 11 I need or want, and that will probably be true for 12 and 13 and so on. As for de-googling Android, that's likely going to just get harder and harder with each version.
I seem to be the only one having problems with Android 11 afaict. Haven't seen anyone else posting issues. Decided it's something about my phone, but laying down 11 stock reset everything. I just can't run Havoc anymore.
I highly recommend Havoc 3.*.
I wonder whether laying down Android 10 would fix my issues with Havoc 4.*?
I went back to stock for the same reason as OP. As far as de-googling, it's a chore to get it to a point where I feel a bit comfortable turning wi-fi on, but I'm not very comfortable. Basically I disable all google stuff, including the play store, prevent the google apps installed post-setup, remove permissions from play services, turn off networking for it and everything else, go through settings to disable 'functions' , I use the keepass2android app's keyboard, install a different sms app, keep contacts to device, and firewall everything - I don't allow much networking functionality at all. Of course, I'm rooted., I also use app manager to disable trackers and disable "0" which is 'rough' location for all apps, system included - I eneble it for weather. I use aurora and f-droid for apps, but, mostly just reinstall from dumps. Also, I don't use a lot of apps and for my feng shui, the device (and my edge) works well. I'm likely leaving out a bunch of little tweaks that I do, apologies.
I use nextcloud, adaway, sms backup and restore, acalendar+, fx, firefox focus or bromite, pi-hole is on my LAN. ON my edge, with lineage (17) and tweaked 'my way', I feel reasonably safe. On my g power with stock, tweaked, I feel a little naked. Whereas I'm not shy, I am private. My g power mostly stays turned off kept in a drawer in my office.
I've been running CrDroid (google-free) v7.7 (android 11) with good results. I have data turned off on this screenshot, but have used it in limited amounts (my current plan allows only 1G per month). BTW, I'm on Red Pocket GSMA (ATT).
So I've cleared the decks by laying down Stock Android 10, then installing Havoc 4.8.
If I lose data tomorrow morning I will have to use another firmware, although I'm confident.
+1 on aCalendar+ and its beautiful widget, and add CalendarNotifications for nice popup.
I use SuperBackups to back up apps and call logs to SD card, and also AppBackupRestore just to be sure. Everything on the SD card was preserved during all these latest calisthenics, thankfully, including after the fastboot erases.
I've set up a Davical server at home for calendar and contacts sync, and on the phone DAVx5 to communicate with it. It's a faff to set up, but such a joy to know my calendars and contacts are always synced with home, once set up. (Thunderbird+Lightning for now, maybe soon Kontact)
The phone does all internet access through a WireGuard tunnel to home WG server virtual machine (interface: inWG), and then out the outWG interface to come out appearing that I'm in Switzerland or Spain, using AzireVPN service.
For Android firewall I use the fine AFWall+ and its little on/off widget, and for apps I always try F-Droid first then APKPure. Browser is Vivaldi. To transfer files with LAN I connect with wifi then use SSHDroid as SSH server on the phone and sshfs on the server to mount the phone. (SSHDroid is worrisomely getting old)
Also I use Nova as desktop renderer. I have 5 phone desktops and it takes me a day to rebuild everything with the standard Havoc desktop (Shady Launcher), no offense SkullShady. Nova lets you back up and restore all settings, including complete desktops setup, which is such a pleasure.
G**gle-less. G**gle-free. Sans G**gle. In my Postfix server I kick back all gmail messages with, "THANK YOU FOR SENDING THIS, BUT GMAIL IS CONSIDERED A SECURITY PROBLEM. PLEASE RE-SEND FROM ANOTHER ACCOUNT."
Good sign - I have data this morning.
Deleted. Thank you.
Worked like a charm. Followed this guide, then ran fastboot oem lock, to prepare a phone to give away. Thank you.
I extracted the files straight to my platform-tools folder to simplify.
Quantumstate said:
Good sign - I have data this morning.
Click to expand...
Click to collapse
Remember me? I still have my Sofia, but it's running stock A11 and Nova Launcher 6.2.9 rather that 7x which screws with my Android widgets. So, I've set the Play Store not to auto update apps to keep 6.2.9. This setup is OK, but I'd rather root it, install TWRP, and an updateable/upgradeable custom ROM. Can you offer some step-by-step guidance?
Thanks
jhford said:
Remember me? I still have my Sofia, but it's running stock A11 and Nova Launcher 6.2.9 rather that 7x which screws with my Android widgets. So, I've set the Play Store not to auto update apps to keep 6.2.9. This setup is OK, but I'd rather root it, install TWRP, and an updateable/upgradeable custom ROM. Can you offer some step-by-step guidance?
Thanks
Click to expand...
Click to collapse
Sure I remember you. I just did an install of beetle84's last version of Havoc as above, and as per the directions in his thread, it's worked ever since. Only glitch is I lose mobile data every morning, but just power down and reboot.
I'm afraid of this version as I tried and tried but could not make it work. Phone was down for days.
Beetle84 said:
If you were trying to flash havoc over android 11 firmware, it wont work. These roms need android 10 as a base.
Click to expand...
Click to collapse
I'm researching if I can flash XT2041-4_SOFIA_RETUS_10_QPMS30.80-109-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip onto my unrooted Android 11 phone, an XT2041-4 that was Android 10 but now Android 11.
I'm not familiar with havoc so I'm curious what you mean. Is that image flashable to my phone or am I wanting to flash havoc over android 11 firmware?
I followed the steps in the oP and bricked my device. I didn't unlock the bootloader so if you follow the tutorial above be sure to unlock the bootloader before wiping the partition.
If anyone knows how to recover from that point I'd appreciate any help. I have the unlock code but I didn't enable unlocking the bootloader before wiping the partition as I didn't know I needed to do that so I hosed myself.
powershift said:
I followed the steps in the oP and bricked my device. I didn't unlock the bootloader so if you follow the tutorial above be sure to unlock the bootloader before wiping the partition.
If anyone knows how to recover from that point I'd appreciate any help. I have the unlock code but I didn't enable unlocking the bootloader before wiping the partition as I didn't know I needed to do that so I hosed myself.
Click to expand...
Click to collapse
Are you still able to boot to the bootloader menu using hardware keys? You should be able to continue unlocking it regardless of what you wiped. Either way that shouldn't stop you from being able to flash the stock rom.
What exactly are you stuck on now?
TaZeR369 said:
Are you still able to boot to the bootloader menu using hardware keys? You should be able to continue unlocking it regardless of what you wiped. Either way that shouldn't stop you from being able to flash the stock rom.
What exactly are you stuck on now?
Click to expand...
Click to collapse
It wouldn't unlock in fastboot. What I did was I downloaded Android 11 and flashed it, then did the boot loader unlock.
But when applying stock Android 10 w/out errors during the flash, on boot the blue Motorola splash screen shows, it acts like it is booting then it reboots and the blue screen goes away and comes back. It will do that boot loop all day. I had to revert back to Android 11, but at least the phone boots now although I'd still like to get Android 10 on there as I'm not at all a fan of V11.
powershift said:
It wouldn't unlock in fastboot. What I did was I downloaded Android 11 and flashed it, then did the boot loader unlock.
But when applying stock Android 10 w/out errors during the flash, on boot the blue Motorola splash screen shows, it acts like it is booting then it reboots and the blue screen goes away and comes back. It will do that boot loop all day. I had to revert back to Android 11, but at least the phone boots now although I'd still like to get Android 10 on there as I'm not at all a fan of V11.
Click to expand...
Click to collapse
I think maybe you should try to flash stock android 10 image again. It's the kind of error that happened to me when I missed a step or forgot a command and looking over your post I think there is something missing or added that shouldn't be there. Also don't flash anything like magisk or twrp along with it, wait until the first boot for anything more.
Heres whats always worked for me (same model phone):
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot flash super super.img_sparsechunk.15
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
TaZeR369 said:
I think maybe you should try to flash stock android 10 image again. It's the kind of error that happened to me when I missed a step or forgot a command and looking over your post I think there is something missing or added that shouldn't be there. Also don't flash anything like magisk or twrp along with it, wait until the first boot for anything more.
Heres whats always worked for me (same model phone):
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot flash super super.img_sparsechunk.15
fastboot erase userdata
fastboot erase ddr
fastboot flash dsp dspso.bin
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
That is what my script looks like with one exception, I can't run the flash bootloader bootloader.img successfully because it fails validation. All other steps succeed. Did you have Android 11 bootloader on there and put the Android 10 bootloader back?
In addition to those steps, I tried fastboot getvar max-sparse-size before all others and still no joy. I think the Android 11 bootloader doesn't boot Android 10 and I don't know how to reflash it back to the old bootloader even while unlocked.
Code:
[email protected]:~/android$ sudo /home/anon/android/platform-tools/fastboot oem unlock 2T4ETJZNOSHSA324GL6G
(bootloader) Bootloader is unlocked!
OKAY [ 15.676s]
Finished. Total time: 15.676s
[email protected]:~/android$
[email protected]:~/android/moto_stock_android10$ sudo /home/anon/android/platform-tools/fastboot flash bootloader bootloader.img
Sending 'bootloader' (14204 KB) OKAY [ 0.557s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
[email protected]:~/android/moto_stock_android10$
powershift said:
That is what my script looks like with one exception, I can't run the flash bootloader bootloader.img successfully because it fails validation. All other steps succeed. Did you have Android 11 bootloader on there and put the Android 10 bootloader back?
In addition to those steps, I tried fastboot getvar max-sparse-size before all others and still no joy. I think the Android 11 bootloader doesn't boot Android 10 and I don't know how to reflash it back to the old bootloader even while unlocked.
Code:
[email protected]:~/android$ sudo /home/anon/android/platform-tools/fastboot oem unlock 2T4ETJZNOSHSA324GL6G
(bootloader) Bootloader is unlocked!
OKAY [ 15.676s]
Finished. Total time: 15.676s
[email protected]:~/android$
[email protected]:~/android/moto_stock_android10$ sudo /home/anon/android/platform-tools/fastboot flash bootloader bootloader.img
Sending 'bootloader' (14204 KB) OKAY [ 0.557s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
[email protected]:~/android/moto_stock_android10$
Click to expand...
Click to collapse
It does flash back, I've done it a few times, I didn't have any difficulty. You said you unlocked the bootloader before, but you seem to be entering the code to unlock it again each time you try to flash or? Because once its unlocked you shouldn't be needing to do oem unlock anymore, unless you've locked it again. Also what distro are you using and adb package?
There may be some verification problem here if something is not fully unlocked for some reason, so just to clarify the first time you flashed android 10 over 11 you also had the bootloader failed error, or is this now on the second try?
Perhaps if all else fails can try to change to the next active slot like b, and try to flash there in case something maybe the partition table got screwed up somehow (at the start) "fastboot set_active b", cold booting with a twrp image may be able to fix it in that case.
I mean unless there is some kind of new protection in the lastest versions of 11 that i dont know about...? Maybe as a last resort reflash android 11 but the first version after 10, and then try to downgrade from that? I dunno man sorry... some stuff to think about...