Develop Bugs

Soft Bricked: No recovery, only fastboot

I did a CM nightly Update, which relocked my phone. I tried to unlock it but something went wrong. I can flash partitions but somehow can't boot into anything besides fastboot. When I try to boot into any recovery (even Stock) the phone just restarts after showing the Oppo logo for a moment. (Just as if I was trying to boot a custom rom from a locked device)
OEM-Info:
Code:
fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.005s]
finished. total time: 0.005s
Booting a recovery.img (Same reaction for every recovery):
Code:
fastboot boot twrp-2.8.7.2-find7.img
downloading 'boot.img'...
OKAY [ 0.355s]
booting...
OKAY [ 0.013s]
finished. total time: 0.368s
Phone Just reboots into a boot loop.
Flashing anything works fine but I'm getting boot loops again.
A strange thing that happens is that if i try
Code:
fastboot oem lock
the process just get's stuck showing three dots. (Same on Windows and Linux) That probably means that the bootloader is in some buggy way half way locked. (That sadly doesn't explains why the stock recovery won't work)
No idea how to fix it. Thank you in advance!
Jakob

Amazing tool here: forum.xda-developers.com/find-7/development/recovery-recovery-installer-7-t2819794

Hey !! I solved the pblm!!! what I did was just hit and trial but it worked. Now I will give the method:
Follow these steps and see if u are lucky enough!
step1: go to fastboot mod in your oppo f1
step2: flash stock recovery using adb. Type in "fastboot flash recovery stock.img"
step3: do not reboot your device and type in "fastboot flashing lock_critical".
step4: type in "fastboot reboot"
After these 4 steps I was able to boot back in Project spectrum. I haven't checked until that if I m able to go to recovery mode but I will update once I check. Check if you can boot.
Note: keep the stock.img file in the same folder in which you have your adb installed.
And I am not sure if this will work for you also.. but it is safe so go give a try!!!
THIS WORKED FOR OPPO F1f YOU CAN TRY YOUR LUCK BY USING THIS METHOD
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Stuck in Fastboot/No Download Mode

Hey guys !
So since i messed up with the recovery mode, i'm stucked in the fastboot with no Download mode (recovery doesnt work neither).
So after searching 3 days in the internet i found the acces to fast through adb by puting a new laf.img in order to restore the download mode and flash a stock firmware !
My problem is that when i try to enter the command on the cmd, i get severals errors, take a look :
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: device not found
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase laf
erasing 'laf'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.034s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash laf laf.img
target reported max download size of 2147483648 bytes
sending 'laf' (18432 KB)...
OKAY [ 0.581s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.615s
Also command : "fastboot boot laf.img" result to "Failed(remote: dtb not found) instead of flash write failure..
Of course i have my G3 855 32GB in download mode (but it goes into fastmode), so when i try a command, lines are added in the screen etc..
Does that mean that my laf.img don't work? I assumed that so i try several, but does it have to be the exact same one as the one who was in my phone before( v20a if i record correctly ) or could it be from any 855 32GB version ?
I also thought it could be a recognition problem as when i type "adb devices" or "adb shell" nothing is found..
If someone has any clue or a link to some guide i'll be more than joyful, thanks in advance !

Try adb fastboot when writing command hope it helps

Anik49 said:
Try adb fastboot when writing command hope it helps
Click to expand...
Click to collapse
Hey thank you so much for answering !
What do you mean by that, i already download the adb/fastboot driver and launch a cmd in the directory they are at, writing "adb fastboot" has no result neither, can you be more specific please ?

cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again: http://open-freax.fr/guide-unbrick-your-lg-g3/

BigsyBiggins said:
cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again:
Click to expand...
Click to collapse
Well i hope my problem can be solved in a safer way, i dont like much to go on the hardware part, so I'll use it as my last hope, but thanks
Altought i think my device is recognized by fastboot in someway because it responds when i type commands in fastboot, and also when i reboot it.
But i'm getting this error :
Code:
error : command never completed
error : auto CMD12 error
error : command completed with errors
error : command timeout error
failed to send stop command
failed writing block @ 1
in the screen of my phone. Does that stand for Cyanogen mode which i was trying to put on my phone ?

I mean when you enter command in cmd use adb before any command also use cmd which one available on android sdk folder....also you can use this method if adb not workinhg properly http://forum.xda-developers.com/lg-g...-9008-t3072091

BigsyBiggins said:
cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again: http://open-freax.fr/guide-unbrick-your-lg-g3/
Click to expand...
Click to collapse
Like @BigsyBiggins said, this is the guide which could fix your phone. HW Part is not too hard!

Anik49 said:
I mean when you enter command in cmd use adb before any command also use cmd which one available on android sdk folder....also you can use this method if adb not workinhg properly
Click to expand...
Click to collapse
Oh ok ! Also your link is not working :s
I understand that the method can work but I think that the method i'm trying to use is really close to succeed, over my search on the internet, i saw lots of people who manage to succeed with it.
But i guess i must do something wrong. I downloaded the kdz file according to my IMEI.
Then I extracted the .dz file with LG Firmware Extract. Then I extracted the file named laf_393216.bin from the dz file. Changed his name into laf.img , put it into the fastboot directory.
Then i typed
Code:
fastboot format cache
fastboot erase laf
fastboot flash laf laf.img
in a cmd from the directory.
It all seemed to work, but then when i remove the battery and restart into download mode, it goes into fastboot after the download mode charging animation..
Also when i try to boot with fastboot boot laf.img i get the error (remote: dtb not found) on the cmd.
And ERROR: Unable to find suitable device tree for device(194/0x0001001/112/0) ERROR: getting device tree adress failed DTB offset is incorrect, kernel image does not have appended DTB)
Am I doing something wrong, should I changed more file than just laf ?

SisGG said:
Oh ok ! Also your link is not working :s
I understand that the method can work but I think that the method i'm trying to use is really close to succeed, over my search on the internet, i saw lots of people who manage to succeed with it.
But i guess i must do something wrong. I downloaded the kdz file according to my IMEI.
Then I extracted the .dz file with LG Firmware Extract. Then I extracted the file named laf_393216.bin from the dz file. Changed his name into laf.img , put it into the fastboot directory.
Then i typed
Code:
fastboot format cache
fastboot erase laf
fastboot flash laf laf.img
in a cmd from the directory.
It all seemed to work, but then when i remove the battery and restart into download mode, it goes into fastboot after the download mode charging animation..
Also when i try to boot with fastboot boot laf.img i get the error (remote: dtb not found) on the cmd.
And ERROR: Unable to find suitable device tree for device(194/0x0001001/112/0) ERROR: getting device tree adress failed DTB offset is incorrect, kernel image does not have appended DTB)
Am I doing something wrong, should I changed more file than just laf ?
Click to expand...
Click to collapse
I don´t know what exactly is the problem, maybe something with your win-driver, some crashed or drifted partitions or some broken files...
I just can repeat my advice: I was in the same situation with my phone after a failed cm13 update and i was trying and reading about 2 days how to solve it - after the above mentioned method, your phone would get out of this "coma".
Maybe somebody else here in this forum could help you with your mentioned method, sorry.

Ernesto0023 said:
I don´t know what exactly is the problem, maybe something with your win-driver, some crashed or drifted partitions or some broken files...
I just can repeat my advice: I was in the same situation with my phone after a failed cm13 update and i was trying and reading about 2 days how to solve it - after the above mentioned method, your phone would get out of this "coma".
Maybe somebody else here in this forum could help you with your mentioned method, sorry.
Click to expand...
Click to collapse
Well I think i'm still under warranty, so i dont wanna touch to much on the hardware.
So do you think, if i send it back without touching anything, saying i put it on charge one night and the next morning it was like this, the warranty could work?

If they found it's rooted or they understand you did something with your software your warrenty is void ?

SisGG said:
Well i hope my problem can be solved in a safer way, i dont like much to go on the hardware part, so I'll use it as my last hope, but thanks
Altought i think my device is recognized by fastboot in someway because it responds when i type commands in fastboot, and also when i reboot it.
But i'm getting this error :
Code:
error : command never completed
error : auto CMD12 error
error : command completed with errors
error : command timeout error
failed to send stop command
failed writing block @ 1
in the screen of my phone. Does that stand for Cyanogen mode which i was trying to put on my phone ?
Click to expand...
Click to collapse
Remove the battery, put it, press the volume + and connect to PC USB, if like entering download, what happens to us not to go, will leave the ****ing LoGo, Well, hold down the volume + and not let go, I think it is less for 2 minutes more. After a while, the computer tells us that something was connected, the phone will tell you who is in fastboot as I said before, if not let me fastboot flash boot files and the LAF, recovery ect, nothing happens, there is still a magic command.
fastboot boot laf.img
Keep it in the ****ing heart

miguexneox said:
Remove the battery, put it, press the volume + and connect to PC USB, if like entering download, what happens to us not to go, will leave the ****ing LoGo, Well, hold down the volume + and not let go, I think it is less for 2 minutes more. After a while, the computer tells us that something was connected, the phone will tell you who is in fastboot as I said before, if not let me fastboot flash boot files and the LAF, recovery ect, nothing happens, there is still a magic command.
fastboot boot laf.img
Keep it in the ****ing heart
Click to expand...
Click to collapse
I dont quite understand what u meant there :s
I already have acces on the fastboot, actually now, my phone goes instantly on fastboot whatever i do.. Though i cannot boot a laf.img downloaded and flashed .. :'(

SisGG said:
I dont quite understand what u meant there :s
I already have acces on the fastboot, actually now, my phone goes instantly on fastboot whatever i do.. Though i cannot boot a laf.img downloaded and flashed .. :'(
Click to expand...
Click to collapse
were u able to resolve this issue. I am in your shoes at the moment.
I have tried the qualcomm. The drivers doesnt seem to work for my phone .
I can't flash or the laf.img . the fastboot commands doesnt seem to work.
and I'm stuck in fastboot .
What can be done

datrmon said:
were u able to resolve this issue. I am in your shoes at the moment.
I have tried the qualcomm. The drivers doesnt seem to work for my phone .
I can't flash or the laf.img . the fastboot commands doesnt seem to work.
and I'm stuck in fastboot .
What can be done
Click to expand...
Click to collapse
You have several options:
- find your phone firmware, extract recovery.img and flash it back through fastboot(do exactly the same for the LAF partition to restore download mode)
- flash a custom recovery for your phone model, if it doesn't work try an older version of TWRP, also it can be that your phone is not d855 but d850 model, so try to flash a d850 custom recovery and see if it works(that was exactly my problem and why i got stuck in fastboot mode, because my phone is d850 model and in settings it says d855, so I flashed wrong TWRP)

Ghikya said:
You have several options:
- find your phone firmware, extract recovery.img and flash it back through fastboot(do exactly the same for the LAF partition to restore download mode)
- flash a custom recovery for your phone model, if it doesn't work try an older version of TWRP, also it can be that your phone is not d855 but d850 model, so try to flash a d850 custom recovery and see if it works(that was exactly my problem and why i got stuck in fastboot mode, because my phone is d850 model and in settings it says d855, so I flashed wrong TWRP)
Click to expand...
Click to collapse
Thanks for the response .
I am unable to flash files at all.
This is the error
D:\mfastboot-v2>fastboot flash laf laf.img
target max-download-size: 2048MB
sending 'laf' (18432 KB)...
OKAY [ 0.646s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.726s
D:\mfastboot-v2>

datrmon said:
Thanks for the response .
I am unable to flash files at all.
This is the error
D:\mfastboot-v2>fastboot flash laf laf.img
target max-download-size: 2048MB
sending 'laf' (18432 KB)...
OKAY [ 0.646s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.726s
D:\mfastboot-v2>
Click to expand...
Click to collapse
It seems that your phone's bootloader is locked, you can try to execute this command: "fastboot oem unlock", and then check state with "fastboot oem device-info". But some people says that it does nothing, so you can try and check for yourself.
You can also try to boot directly an image from fastboot for eaxmple:
Code:
fastboot boot laf.img
or
Code:
fastboot boot twrp.img
So if you could successfully boot a laf image you would be able to access download mode, and if you could boot a custom recowery then you could access ADB and to try to flash other partitions, or even flash a custom rom...

ZE551ML - Stuck in fastboot mode, unable to write using Asus Flash Tool or xFSTK

C:\Asus_Zen_Phone_2>fastboot3 oem partition /tmp/partition.tbl
...
FAILED (remote: GPT command failed) - Also found in Asus flash tool
[2016-07-14T 01:53:53Z] (0x00000000) [0123456789ABCDEF] Flash image ...
[2016-07-14T 01:54:32Z] (0x00000000) [0123456789ABCDEF] Flash image failure(FAILED (remote: GPT command failed)
I tried to flash boot, recovery, droidboot, and system.img, but no luck. Anytime I reboot, goes to fastboot mode only.
Trying to use xFSTK Downloader v1.7, I do not get USB logo. Phone boots into fastboot mode only.
HELP!

SaHiLzZ said:
C:\Asus_Zen_Phone_2>fastboot3 oem partition /tmp/partition.tbl
...
FAILED (remote: GPT command failed) - Also found in Asus flash tool
[2016-07-14T 01:53:53Z] (0x00000000) [0123456789ABCDEF] Flash image ...
[2016-07-14T 01:54:32Z] (0x00000000) [0123456789ABCDEF] Flash image failure(FAILED (remote: GPT command failed)
I tried to flash boot, recovery, droidboot, and system.img, but no luck. Anytime I reboot, goes to fastboot mode only.
Trying to use xFSTK Downloader v1.7, I do not get USB logo. Phone boots into fastboot mode only.
HELP!
Click to expand...
Click to collapse
If you need help , try to be more specific with how you got in this state ?????!
Uninstall ASUS flash tool.
Uninstall xsftk downloader.
Clean system with ccleaner free !
Install isoc driver first.
Flash in xfstk downloader..
Don't go near ASUS Flash tool till success in xfstk
Then follow , don't be shy with the thanks button !
http://forum.xda-developers.com/zenfone2/general/unbrick-vid-tutorial-restore-serial-t3411064
Ps, keep powering off your phone in xfstk.
Pressing power at ten seconds intervals. Till you see it flash.
Keep repeating till success and you get into boot loader version 0094 1069
You on 0094 0183 at the moment coming from 6.0?

Also Happened to me
Please Help It also happened to me to.
my ZF2 is brick,,,
1. i cant xfstk : "failure : FW + OS download did not complete",, just stop in "Firmware download completed. Continuing to OS"
and become "Reconnecting to device". i tried several time but no luck...
several time it give me this
-- "Success: FW download completed! OS download skipped"
and my ZF2 continued to fastboot, but i cant flash splashscreen and droidboot or recovery, etc, only just ifwi its successed. after xfstk my bootloader is become version 0094 1069
2. in Asus Flash Tool give me error to it says "Flash image failure (FAILED (wrong image format))". trying to download several time raw file 2.15.40.13 and 2.20.40.139, but no luck...

pocax said:
Please Help It also happened to me to.
my ZF2 is brick,,,
1. i cant xfstk : "failure : FW + OS download did not complete",, just stop in "Firmware download completed. Continuing to OS"
and become "Reconnecting to device". i tried several time but no luck...
several time it give me this
-- "Success: FW download completed! OS download skipped"
and my ZF2 continued to fastboot, but i cant flash splashscreen and droidboot or recovery, etc, only just ifwi its successed. after xfstk my bootloader is become version 0094 1069
2. in Asus Flash Tool give me error to it says "Flash image failure (FAILED (wrong image format))". trying to download several time raw file 2.15.40.13 and 2.20.40.139, but no luck...
Click to expand...
Click to collapse
In 1069 boot loader , you then flash raw file in flash tool
http://forum.xda-developers.com/zenfone2/general/unbrick-vid-tutorial-restore-serial-t3411064
Watch the vid ..
If you flashed anything in fastboot ..re flash ifwi etc till success again ..but then flash raw.
The vid is easy to understand !

timbernot said:
If you need help , try to be more specific with how you got in this state ?????!
Uninstall ASUS flash tool.
Uninstall xsftk downloader.
Clean system with ccleaner free !
Install isoc driver first.
Flash in xfstk downloader..
Don't go near ASUS Flash tool till success in xfstk
Then follow , don't be shy with the thanks button !
http://forum.xda-developers.com/zenfone2/general/unbrick-vid-tutorial-restore-serial-t3411064
Ps, keep powering off your phone in xfstk.
Pressing power at ten seconds intervals. Till you see it flash.
Keep repeating till success and you get into boot loader version 0094 1069
You on 0094 0183 at the moment coming from 6.0?
Click to expand...
Click to collapse
Keep flashing but failing after 20 attempts in xfstk.
how it happened, its someone else's phone, i think running cm13, and then it stopped working by itself. phone had no access to recovery, and only fastboot or boot cm logo.

SaHiLzZ said:
Keep flashing but failing after 20 attempts in xfstk.
how it happened, its someone else's phone, i think running cm13, and then it stopped working by itself. phone had no access to recovery, and only fastboot or boot cm logo.
Click to expand...
Click to collapse
When you get to that fastboot loop, the only way is indeed xfstk.
I suspect you either didnt follow the video keeping 4 zeros only in the xfstk option, 0x80000807, also remember, you need to run the Flash tool twice, first time you run it, it should show result: OKAY on the phone, then you close the flash tool and say yes to forcibly close, this makes the serial numbers match in the flash tool and the phone, hen launch and flash with the RAW file again, you should press volume up I think to ensure the phone is connected again. Ensure you always select Wipe everything in the flashtool, or it will not boot properly, pay well attention in the video to what timbernot does and says, though for none native english speakers, it might be a little hard to understand everything , but if you do if do this right everything should work.
Also remember, you NEED to boot into recovery mode on Win10 in order to install the iSoc drivers and disable the force driver signature, else they will not install.
I had massive problems with Bootloader when running any tools, so had to go back and do this process several times. Once you get your system up and running, I suggest not even trying the boot unlock tool from ASUS, it has caused me nothing but grief, root your device after the rawflash is succesful and then do the unoffcial bootload unlock via adb.

SaHiLzZ said:
Keep flashing but failing after 20 attempts in xfstk.
how it happened, its someone else's phone, i think running cm13, and then it stopped working by itself. phone had no access to recovery, and only fastboot or boot cm logo.
Click to expand...
Click to collapse
its happened to me to..
always fail in xfstk...

I hope you guys or gals are all sorted now and have lovely nice new stock systems , up n running

LBN said:
When you get to that fastboot loop, the only way is indeed xfstk.
I suspect you either didnt follow the video keeping 4 zeros only in the xfstk option, 0x80000807, also remember, you need to run the Flash tool twice, first time you run it, it should show result: OKAY on the phone, then you close the flash tool and say yes to forcibly close, this makes the serial numbers match in the flash tool and the phone, hen launch and flash with the RAW file again, you should press volume up I think to ensure the phone is connected again. Ensure you always select Wipe everything in the flashtool, or it will not boot properly, pay well attention in the video to what timbernot does and says, though for none native english speakers, it might be a little hard to understand everything , but if you do if do this right everything should work.
Also remember, you NEED to boot into recovery mode on Win10 in order to install the iSoc drivers and disable the force driver signature, else they will not install.
I had massive problems with Bootloader when running any tools, so had to go back and do this process several times. Once you get your system up and running, I suggest not even trying the boot unlock tool from ASUS, it has caused me nothing but grief, root your device after the rawflash is succesful and then do the unoffcial bootload unlock via adb.
Click to expand...
Click to collapse
timbernot said:
I hope you guys or gals are all sorted now and have lovely nice new stock systems , up n running
Click to expand...
Click to collapse
I got the xftsk to flash, successfully:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Got USB flash sign, but NO 4 colored lines. Phone still boots to fastboot.
Help?

Flash again now , repeat till bootloader

timbernot said:
Flash again now , repeat till bootloader
Click to expand...
Click to collapse
flash using xfstk? until what? the four lines?

SaHiLzZ said:
flash using xfstk? until what? the four lines?
Click to expand...
Click to collapse
Yup and don't come back till you succeed
---------- Post added at 06:19 PM ---------- Previous post was at 06:10 PM ----------
SaHiLzZ said:
flash using xfstk? until what? the four lines?
Click to expand...
Click to collapse
wait a minute, what is the number of boot loader ?
0094 1069 ?if not what is it ?
You may have missed the four colours so if 1069 flash with flash tool raw.
If any other number carry on with xfstk

timbernot said:
Yup and don't come back till you succeed
---------- Post added at 06:19 PM ---------- Previous post was at 06:10 PM ----------
wait a minute, what is the number of boot loader ?
0094 1069 ?if not what is it ?
You may have missed the four colours so if 1069 flash with flash tool raw.
If any other number carry on with xfstk
Click to expand...
Click to collapse
Yes 1069.. Fastboot flash with Asus flasher fail with error in first post. GPT error.

All I can suggest is keep flashing xfstk.
When says success again.
Wait till it boots into boot loader fastboot.
Then wait a little longer before flashing raw.

timbernot said:
All I can suggest is keep flashing xfstk.
When says success again.
Wait till it boots into boot loader fastboot.
Then wait a little longer before flashing raw.
Click to expand...
Click to collapse
Done a bit of digging re gpt error.
Stands for grand partition table.
So to me sounds like deep trouble beyond my knowledge .
The reason I say flash xfstk till success and then wait is because I had the same you are experiencing.
I left the phone connected. I went to make a brew, a breather
And a smoke , then all of a sudden ..I seen commands flashing to the phone. Then after about 15 mins I was able to flash raw
I put this down to a couple of possibilities.
One being constant abuse overload through constant attempts in xfstk.
Two , also battery getting low.
And or a mixture of both.
So again I suggest.
Charge fone a couple of hrs.
Let it cool.
Try again.
When success in xfstk, leave connected to PC and see if command start to flash on fone.
Then flash raw
Can I ask you what are the figures you are using in the second box at the bottom ending in CRC in xfstk? .Are they 0x80000807 with gp overide flag ticked ?

LBN said:
When you get to that fastboot loop, the only way is indeed xfstk.
I suspect you either didnt follow the video keeping 4 zeros only in the xfstk option, 0x80000807, also remember, you need to run the Flash tool twice, first time you run it, it should show result: OKAY on the phone, then you close the flash tool and say yes to forcibly close, this makes the serial numbers match in the flash tool and the phone, hen launch and flash with the RAW file again, you should press volume up I think to ensure the phone is connected again. Ensure you always select Wipe everything in the flashtool, or it will not boot properly, pay well attention in the video to what timbernot does and says, though for none native english speakers, it might be a little hard to understand everything , but if you do if do this right everything should work.
Also remember, you NEED to boot into recovery mode on Win10 in order to install the iSoc drivers and disable the force driver signature, else they will not install.
I had massive problems with Bootloader when running any tools, so had to go back and do this process several times. Once you get your system up and running, I suggest not even trying the boot unlock tool from ASUS, it has caused me nothing but grief, root your device after the rawflash is succesful and then do the unoffcial bootload unlock via adb.
Click to expand...
Click to collapse
You don't know it but the lil info you gave there about flashtool having to be ran twice is a gem of info. Developed migraines till this one little bit... Thanks a million.

Zenfone 2 Delux Z00AD ZE551ML Bricked - No Fastboot comands,
hi guys,
i need some help.
i Bricked my Zenfone 2 Delux z00AD ZE551ML
even following the instructions and with all the drivers correctly installed i cant unbrick it.
After sending the XFSTK files (dnx_fwr.bin, e droidboot_dnx.img.POS_sign.bin) my phone has reseted, has gone through the colored screen and then the screen has gone all black.
The fastboot recognizes the device and the ficctitious serial number but doesnt accept the comands.
I´m copying the xFSTK, Asus Flash Tool and fastboot logs below, if anyone can help me i would really aprecciate.
Thank you.
##### xFSTK Downloader 1.7 #####
Settings -> Download Options:
Enable GP Flag Overrider
GP Flag Overrider valeu 0x80000807
Devixe detection Timeout 120
Success: Download of FW Completed OK!
OS: Operating system download completed. ok!
Log:
20:05:08 - XFSTK-STATUS--Firmware and OS download completed.
20:05:08 - XFSTK-LOG--virtual bool MerrifieldDownloader::GetStatus()
20:05:08 - Success: Download of FW Completed.
##### Asus Flash Tool #####
Flash imagem (FAILED (remote: GPT command failed
Log failure:
[2016-09-11T 19:27:25Z] (0x00000000) Detect: 0B05:4DAF:0123456789ABCDEF:0005:0004:0
[2016-09-11T 19:27:27Z] (0x00000000) Detect: 0B05:4DAF:0123456789ABCDEF:0005:0004:1
[2016-09-11T 19:38:03Z] (0x00000000) [0123456789ABCDEF] User remove device from list
[2016-09-11T 19:38:18Z] (0x00000000) Detect: 0B05:4DAF:0123456789ABCDEF:0005:0004:0
[2016-09-11T 19:38:24Z] (0x00000000) Detect: 0B05:4DAF:0123456789ABCDEF:0005:0004:1
[2016-09-11T 19:38:24Z] (0x00000000) [0123456789ABCDEF] Detected this device
[2016-09-11T 19:38:35Z] (0x00000000) [0123456789ABCDEF] Check the detected serial number ...
[2016-09-11T 19:38:35Z] (0x00000000) [0123456789ABCDEF] Flash image ...
[2016-09-11T 19:39:26Z] (0x00000000) [0123456789ABCDEF] Flash image failure(FAILED (remote: GPT command failed)
##### ADB and Fastboot #####
C:\fastboot devices
0123456789ABCDEF fastboot
C:\fastboot oem erase_osip_header
...
(bootloader) cmd_oem!arg= erase_osip_header S
(bootloader) [0]erase_osip_header S
OKAY [ 1.295s]
finished. total time: 1.295s
C:\fastboot oem erase_token
...
(bootloader) cmd_oem!arg= erase_token S
(bootloader) [0]erase_token S
FAILED (remote: Fail erase_token_umip)
finished. total time: 0.764s
C:\fastboot oem start_partitioning
...
(bootloader) cmd_oem!arg= start_partitioning S
(bootloader) [0]start_partitioning S
(bootloader) Start partitioning
OKAY [ 0.998s]
finished. total time: 0.998s
C:\fastboot flash /tmp/partition.tb
l partition.tbl
target reported max download size of 536870912 bytes
sending '/tmp/partition.tbl' (2 KB)...
OKAY [ 0.983s]
writing '/tmp/partition.tbl'...
OKAY [ 1.295s]
finished. total time: 2.293s
C:\fastboot oem partition /tmp/part
ition.tbl
...
(bootloader) cmd_oem!arg= partition /tmp/partition.tbl S
(bootloader) [0]partition S
(bootloader) [1]/tmp/partition.tbl S
FAILED (remote: GPT command failed
)
finished. total time: 0.764s
C:\fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
FAILED (status read failed (Too many links))
finished. total time: 0.905s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
< waiting for any device >
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
FAILED (status read failed (Too many links))
finished. total time: 1.186s

timbernot said:
Done a bit of digging re gpt error.
Stands for grand partition table.
So to me sounds like deep trouble beyond my knowledge .
The reason I say flash xfstk till success and then wait is because I had the same you are experiencing.
I left the phone connected. I went to make a brew, a breather
And a smoke , then all of a sudden ..I seen commands flashing to the phone. Then after about 15 mins I was able to flash raw
I put this down to a couple of possibilities.
One being constant abuse overload through constant attempts in xfstk.
Two , also battery getting low.
And or a mixture of both.
So again I suggest.
Charge fone a couple of hrs.
Let it cool.
Try again.
When success in xfstk, leave connected to PC and see if command start to flash on fone.
Then flash raw
Can I ask you what are the figures you are using in the second box at the bottom ending in CRC in xfstk? .Are they 0x80000807 with gp overide flag ticked ?
Click to expand...
Click to collapse
it is a issue related to emmc. here may be 2 cases. 1. your emmc is corrupted 2. it is not formatted correctly. i am working on it. unfortunately i don't have any bricked device. especially 2gb ram one. even though will update soon if i am able to figure out the issue.. till then before pushing the partition table and after erasing osip header. try to run command " fastboot erase partition" or "fastboot oem erase partition" please reply if something happens

marcusvrbrito said:
hi guys,
i need some help.
i Bricked my Zenfone 2 Delux z00AD ZE551ML
even following the instructions and with all the drivers correctly installed i cant unbrick it.
After sending the XFSTK files (dnx_fwr.bin, e droidboot_dnx.img.POS_sign.bin) my phone has reseted, has gone through the colored screen and then the screen has gone all black.
The fastboot recognizes the device and the ficctitious serial number but doesnt accept the comands.
I´m copying the xFSTK, Asus Flash Tool and fastboot logs below, if anyone can help me i would really aprecciate.
Thank you.
Click to expand...
Click to collapse
U need to do raw flashing two times
once to sort out serial
reboot to bootloader again
second for full flash

device unable to boot Error - mdtp image is corrupted

Hi there,
I have a problem i was try to root my phone.
Now i dont have access to ADB but only fastboot works.
If i start my phone it goes on fastboot mode, and if i try "fast boot twrp-3.3.0-0-daisy.img" i get the error "device unable to boot Error - mdtp image is corrupted"
Can some one help me out, if tried to download the image again but without success..

You don't need twrp for root?!
I guess you need to get a fast boot ROM and flash it. Don't relock the bootloader. Don't flash data. Just all the other partitions.
Maybe even just flash that partition. My phone has a and b. Should just need to flash the current one.

a1291762 said:
You don't need twrp for root?!
I guess you need to get a fast boot ROM and flash it. Don't relock the bootloader. Don't flash data. Just all the other partitions.
Maybe even just flash that partition. My phone has a and b. Should just need to flash the current one.
Click to expand...
Click to collapse
Sorry im a little bit noob, but how it works:
flastboot flash a?

fastboot flash mdtp_a mdtp.img
That file is in the images folder after you extract the fastboot ROM.

Hi,
while having 15 years of Linux experience, I've just dropped into the same issue on my first hour of Android exploration. Currently no OS is installed and the phone boots into fastboot. Booting into twrp-3.3.1-dees_troy-daisy.img failes also with "Error - mdtp image is corrupted".
I've flashed mdtp.img from V10.0.12.0.PDLMIXM as described, but still I get the same error when booting into twrp-3.3.1-dees_troy-daisy.img . Is there somewere a documentation, how to proceed in such a case?
a1291762 said:
fastboot flash mdtp_a mdtp.img
That file is in the images folder after you extract the fastboot ROM.
Click to expand...
Click to collapse

mj2o said:
Hi,
while having 15 years of Linux experience, I've just dropped into the same issue on my first hour of Android exploration. Currently no OS is installed and the phone boots into fastboot. Booting into twrp-3.3.1-dees_troy-daisy.img failes also with "Error - mdtp image is corrupted".
I've flashed mdtp.img from V10.0.12.0.PDLMIXM as described, but still I get the same error when booting into twrp-3.3.1-dees_troy-daisy.img . Is there somewere a documentation, how to proceed in such a case?
Click to expand...
Click to collapse
No OS installed is maybe cause the last rom that you flashed was not flashed in the right slot or correctly flashed.
Also the fastboot command mentioned here is to flash mdtp in "a" slot but you have to see first which is your active slot and then install it on it.

SubwayChamp said:
Also the fastboot command mentioned here is to flash mdtp in "a" slot but you have to see first which is your active slot and then install it on it.
Click to expand...
Click to collapse
I've searched more for the reason and once got the response: FAILED (remote: partition table doesn't exist)
So it sounds I have to recreate the partition table. I haven't found any fastboot command to request the current partition status.

mj2o said:
I've searched more for the reason and once got the response: FAILED (remote: partition table doesn't exist)
So it sounds I have to recreate the partition table. I haven't found any fastboot command to request the current partition status.
Click to expand...
Click to collapse
I don´t think that exist a command to diagnose status of partitions but I´m sure that if you try to flash on an inactive slot then won´t work, ever an inactive slot will give you a fail.
Check your active slot by typing
Code:
fastboot getvar current-slot
and then flash it on the active slot using "mdtp_a" or "mdtp_b" but ONLY if the active slot is actually with all the system on it it´s mean that if you deleted all your system and any of both are actually with partitions running (no matter that with errors) then won´t work this way as you expect.

I have the same problem, what you have did to fix? please

Hi,
I've downloaded and flashed the factory image from miui.com. This way I have reset all my efforts and started all over. You find there the full rom and a flashing guide for the Xiaomi Mi A2 Lite.

mj2o said:
Hi,
I've downloaded and flashed the factory image from miui.com. This way I have reset all my efforts and started all over. You find there the full rom and a flashing guide for the Xiaomi Mi A2 Lite.
Click to expand...
Click to collapse
hi
same issue here @mj2o: Can you please provide a link to the site in English; it all in Chinese and I cannot read it
Thanks

mj2o said:
Hi,
I've downloaded and flashed the factory image from miui.com. This way I have reset all my efforts and started all over. You find there the full rom and a flashing guide for the Xiaomi Mi A2 Lite.
Click to expand...
Click to collapse
SubwayChamp said:
I don´t think that exist a command to diagnose status of partitions but I´m sure that if you try to flash on an inactive slot then won´t work, ever an inactive slot will give you a fail.
Check your active slot by typing
Code:
fastboot getvar current-slot
and then flash it on the active slot using "mdtp_a" or "mdtp_b" but ONLY if the active slot is actually with all the system on it it´s mean that if you deleted all your system and any of both are actually with partitions running (no matter that with errors) then won´t work this way as you expect.
Click to expand...
Click to collapse
@mj2o;80151263:
Code:
fastboot getvar current-slot
returns -->
Code:
current-slot: INVALID
finished. total time: 0.008s
and
Code:
fastboot flash aboot aboot.img
returns -->
Code:
target reported max download size of 534773760 bytes
sending 'aboot' (1024 KB)...
OKAY [ 0.055s]
writing 'aboot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.075s
please advise.

BenG7 said:
@mj2o;80151263:
Code:
fastboot getvar current-slot
returns -->
Code:
current-slot: INVALID
finished. total time: 0.008s
and
Code:
fastboot flash aboot aboot.img
returns -->
Code:
target reported max download size of 534773760 bytes
sending 'aboot' (1024 KB)...
OKAY [ 0.055s]
writing 'aboot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.075s
please advise.
Click to expand...
Click to collapse
Why do you want to flash the bootloader, what is the issue?

Hi @SubwayChamp
I wanted to flash LO16
Did a wpie data -yes format
Then a wipe system as instructed and now im stuck in fast boot.
Device unable to boot. Error - mdtp is corrupted

BenG7 said:
Hi @SubwayChamp
I wanted to flash LO16
Did a wpie data -yes format
Then a wipe system as instructed and now im stuck in fast boot.
Click to expand...
Click to collapse
If your issue is related with mdtp partition then you should to install again this image through fastboot in both slots in order to can boot device again to recovery; use
Code:
fastboot flash mdtp_a mdtp.img
and
Code:
fastboot flash mdtp_b mdtp.img
(you will get the images from any of the full fastboot roms)
From there try again the steps recommended by OP in that thread to get that your device boots on LOS but this is other question concerning only to that thread

Thanks SubwayChamp,
Will try as advised and keep you updated.
I m going to look for the fastboot rom for my daisy.

SubwayChamp said:
If your issue is related with mdtp partition then you should to install again this image through fastboot in both slots in order to can boot device again to recovery; use
Code:
fastboot flash mdtp_a mdtp.img
and
Code:
fastboot flash mdtp_b mdtp.img
(you will get the images from any of the full fastboot roms)
From there try again the steps recommended by OP in that thread to get that your device boots on LOS but this is other question concerning only to that thread
Click to expand...
Click to collapse
@SubwayChamp
dit it and when I
Code:
fastboot reboot
it boots straight back to fastboot.
What next? Mi a2 Lite stuck at Fastboot - No recovery, no nothing! Help ?
Thanks for your help!
[EDIT]
realised I can
Code:
fastboot boot twrp-daisy-3.3.1-0-offain.img
and I can flash the twrp-installer-daisy-3.3.1-0-offain.zip
but if I want to reboot; it says
Code:
No OS installed! Are you sure you wish to reboot?
so I went on with flashing lineageos 16
but at the end of the flash, I get
Code:
Failed to mount '/system' (permission denied)
please advise

BenG7 said:
If your issue is related with mdtp partition then you should to install again this image through fastboot in both slots in order to can boot device again to recovery; use and
@SubwayChamp
dit it and when I
it boots straight back to fastboot.
What next? Mi a2 Lite stuck at Fastboot - No recovery, no nothing! Help ?
Thanks for your help!
Click to expand...
Click to collapse
Your recovery is missed now cause when you flashed LOS was overwritten and device can't boot to system cause some step failed in the process.
If you flashed successfully mdtp images now follow the steps to boot to recovery and then follow those indicated to install LOS.

SubwayChamp said:
Your recovery is missed now cause when you flashed LOS was overwritten and device can't boot to system cause some step failed in the process.
If you flashed successfully mdtp images now follow the steps to boot to recovery and then follow those indicated to install LOS.
Click to expand...
Click to collapse
Thanks; this is what I did:
from TWRP I rebooted to recovery
it took me straight to fastboot again
so I
Code:
fastboot boot twrp-daisy-3.3.1-0-offain.img
again and mounted system partition then I flashed LOS
and the process went fine this time but when I rebooted to the system
it's back to fastboot again!

BenG7 said:
Thanks; this is what I did:
from TWRP I rebooted to recovery
it took me straight to fastboot again
so I
again and mounted system partition then I flashed LOS
and the process went fine this time but when I rebooted to the system
it's back to fastboot again!
Click to expand...
Click to collapse
This is exactly what I tried to tell you: your issue concerning to this thread was solved.
Now you have an issue regarding how to flash and boot to system attempting to install LOS. TWRP is perfectly capable to mount/remount or unmount partitions if needed, no need an action from the user, this is not the reason why you are not booting but the method and steps is discussed more properly in the same thread.
From here you can take one of hese three routes:
- To insist with trying to flash LOS.
- Flash other rom or a previous known working rom.
- Return completely to stock by flashing a full global rom.
Just I could recommend that for the future when you flash a stock rom take a backup of the most important partitions (without userdata) this could avoid that you need to use EDL anymore.

Moto Z2 force constantly bootlooping, Stock rom load but NO Wi-FI or Cellular network

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.