Related
Ok, I've put my flame suit on, but I swear I have tried everything. I am not a developer level guy by any means, but I've been installing custom roms since the OG droid. But this time I got distracted and clearly made a foolish mistake. I was installing XDABBEB's new rom and I totally flaked out and installed the bootstrap and the rom in the same flash. it obviously didn't work and even though I read the instructions, I tried to restore my rom from a backup. Now the only thing I can do is boot into fastboot.
I've tried a number of ways to get TWRP or CWM back onto my phone so I can sideload a rom onto it, but every time I try to fastboot a recovery file it says that "remote: image is not a boot image" or something. What I have gathered from my research is that I cant install a custom recovery unless I am rooted.
/
So, without a custom recovery and only fastboot at my disposal, where do I go from here?
sfl007 said:
Ok, I've put my flame suit on, but I swear I have tried everything. I am not a developer level guy by any means, but I've been installing custom roms since the OG droid. But this time I got distracted and clearly made a foolish mistake. I was installing XDABBEB's new rom and I totally flaked out and installed the bootstrap and the rom in the same flash. it obviously didn't work and even though I read the instructions, I tried to restore my rom from a backup. Now the only thing I can do is boot into fastboot.
I've tried a number of ways to get TWRP or CWM back onto my phone so I can sideload a rom onto it, but every time I try to fastboot a recovery file it says that "remote: image is not a boot image" or something. What I have gathered from my research is that I cant install a custom recovery unless I am rooted.
/
So, without a custom recovery and only fastboot at my disposal, where do I go from here?
Click to expand...
Click to collapse
Phone model?
You can try to flash through LG Flash Tools
Swakiny said:
Phone model?
You can try to flash through LG Flash Tools
Click to expand...
Click to collapse
Thanks for the reply.
I have a VS980S. I have tried the LG flash tool, but I can't get any of the numerous LG drivers to recognize my phone. I even tried dd commands in Ubuntu, but all it would do is try and mount volume after volume making it impossible to use the interface,
sfl007 said:
Thanks for the reply.
I have a VS980S. I have tried the LG flash tool, but I can't get any of the numerous LG drivers to recognize my phone. I even tried dd commands in Ubuntu, but all it would do is try and mount volume after volume making it impossible to use the interface,
Click to expand...
Click to collapse
I'm in the same boat man. I tried flashing AOKP and it hung and I rebooted and everything but TWRP was gone. I'm in the process of trying the KDZ method right now.
markrulesallnow said:
I'm in the same boat man. I tried flashing AOKP and it hung and I rebooted and everything but TWRP was gone. I'm in the process of trying the KDZ method right now.
Click to expand...
Click to collapse
I hope it works for you. I tried that and flashing TWRP with fastboot but it said that it wasn't a valid boot image. A little research said that happens when your device is not rooted. But how can I root my phone from fastboot alone?
sfl007 said:
I hope it works for you. I tried that and flashing TWRP with fastboot but it said that it wasn't a valid boot image. A little research said that happens when your device is not rooted. But how can I root my phone from fastboot alone?
Click to expand...
Click to collapse
Try IOroot ... flash it true ADB !!
Denfic said:
Try IOroot ... flash it true ADB !!
Click to expand...
Click to collapse
I'll give a try and report back. But I have a feeling it won't work. I think I have the adb driver loaded but I can't get my computer to recognize any other of the drivers.
sfl007 said:
I'll give a try and report back. But I have a feeling it won't work. I think I have the adb driver loaded but I can't get my computer to recognize any other of the drivers.
Click to expand...
Click to collapse
when opening window in map .. try to tick adb service !!! It might recognize the phone that way !
​
Denfic said:
when opening window in map .. try to tick adb service !!! It might recognize the phone that way !
Click to expand...
Click to collapse
Sorry, what do you mean by "opening window in map"?
I was also in the same boat for 36 h, stuck on trwp recovery, no rom, no gaps in memory... I'm freely sailing now! I did this:
- press together power and lower button to get usb connecting screen, unplugged usb cable.
- LG tools installed and D-802 pilots {for me] installed, plug cable and check pilots again.
- launch in LG tools option for wrong install repair
- wait until the complete rom repair is installed, quite long, and then you win automatic reboot! You just loose root. Ioroot 25 again, that's all.
Hope it works for you chaps.
I had a similar issue. Follow this step by step. It even tells you when and how to install the drivers
http://www.droidviews.com/how-to-restore-lg-g2-to-stock-firmware/
Sent from my VS980 4G using xda app-developers app
Icfatpeople said:
I had a similar issue. Follow this step by step. It even tells you when and how to install the drivers
http://www.droidviews.com/how-to-restore-lg-g2-to-stock-firmware/
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Yeh try this ... what i meant was when opening windows in adb-map ... windows -explorer !
But try the llink provided ...it will wake up your phone ..! :good:
Believe me before doing any thing using your pc just try to change the usb port first, then let it install the driver automatically(if you're using w7/8)
if windows xp just dont plug your phone remove the old LG driver and then plug your phone to another usb port that the one you have used it before with your phone and install the driver, and then proceed....
Why i am telling you this?
because i had almost the same problem with my galaxy note 2..... it wasn't recognizing my phone until i changed my usb port in download
mode and let it istall the driver......
hope it'll help.......... :good:
Icfatpeople said:
I had a similar issue. Follow this step by step. It even tells you when and how to install the drivers
http://www.droidviews.com/how-to-restore-lg-g2-to-stock-firmware/
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Ok, when I try this the computer recognizes my phone as a "USB Modem Phone ADB port" in device manager. But when I follow the directions in the link above if fails at Step 24. It says the phone is not connected. It is asking for my phone to be in "Download mode" in step 17, but I can only get into Fastboot mode. Is that the issue?
Yeah it is. Have you tried getting it into download mode? I was able to when I was stuck with a fast boot
Sent from my VS980 4G using xda app-developers app
---------- Post added at 03:54 PM ---------- Previous post was at 03:53 PM ----------
Try holding the power until the phone is off. Then you should be able to get to download mode
Sent from my VS980 4G using xda app-developers app
Icfatpeople said:
Yeah it is. Have you tried getting it into download mode? I was able to when I was stuck with a fast boot
Sent from my VS980 4G using xda app-developers app
---------- Post added at 03:54 PM ---------- Previous post was at 03:53 PM ----------
Try holding the power until the phone is off. Then you should be able to get to download mode
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Ok, as i understand it you have to hold volume up and plug the device in while its off. The problem I am having is that the phone is always on. Regardless of what mode I have it in, I can always see the back light glowing. I've searched for ways of truly turning the phone off, but I can't find any info.
Suggestions?
sfl007 said:
Ok, as i understand it you have to hold volume up and plug the device in while its off. The problem I am having is that the phone is always on. Regardless of what mode I have it in, I can always see the back light glowing. I've searched for ways of truly turning the phone off, but I can't find any info.
Suggestions?
Click to expand...
Click to collapse
Ok, hold power button until phone turn off, still holding until LG logo appear again, then the phone will turn off completly.
Turn off = Off
(First Off will take a long time, don't worry(about 40 seconds), don't forget: still holding the power button until LG logo appear and the phone Off)
Swakiny said:
Ok, hold power button until phone turn off, still holding until LG logo appear again, then the phone will turn off completly.
Turn off = Off
(First Off will take a long time, don't worry(about 40 seconds), don't forget: still holding the power button until LG logo appear and the phone Off)
Click to expand...
Click to collapse
ok, it seems like it goes off. the backlight appears to be off, but when I hold the volume up button and then plug it in, it immediately goes to fastboot. ugh.
can i use fastboot to send the phone to download mode? I'll start searching for that now.....
Have you tried this
http://forum.xda-developers.com/showthread.php?t=2477595
Sent from my VS980 4G using xda app-developers app
Icfatpeople said:
Have you tried this
http://forum.xda-developers.com/showthread.php?t=2477595
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Holy cow. This might be the last piece of the puzzle. I will report back after trying this.
Today I wanted to switch to CM13 which I found on this forum. I messed up, phone got stuck in a reboot loop, got it into download mode and put it back to a stock version. Now however, I am not able to root my phone using ioroot. This is all I get when I try to root my phone, then it just stops.
Code:
Enable ADB connection..
Developer Options unlocked and ON.
USB debugging ON.
Accept RSA key fingerprint.
Press any key to continue . . .
Waiting for ADB detection...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
When trying to change to a different stock ROM with LG FLASH TOOL 2014 I get the following error when my phone is connected to my PC with MTP.
Code:
The phone is disconnected from PC.
Connect the USB cable and wait a moment. Press the Retry button to resume the setting analysis process.
My phone is still connected, pressing the retry button brings up the same message.
When I select LG Software instead of MTP I get the following error.
Code:
To try upgrade again, follow the steps below.
1. Disconnect the phone from PC and remove hte battery from the phone.
2. Insert the battery back and reconnect the phone to PC.
3. Turn on the phone.
4. Press the Retry button below to start the upgrade.
I can't remove the battery, pressing retry after a reboot brings up the same message.
Software information:
Code:
Android version: 4.4.2
Baseband version: M8974A-AAAANAZM-1.0.190084
Kernel version: 3.4.0
Build number: KOT491.D80220h
Software version: D80220h-EUR-XX
Hardware information:
Code:
Model number: LG-D802
Memory: 32GB
So what do I want to do? Switch from the current ROM to a different one, as that is currently not possible for me. After this I wil retry to put CM13 on my phone. I am out of ideas (not that much experience) so hopefully someone on this forum can help me out!
MajorTemples said:
Today I wanted to switch to CM13 which I found on this forum. I messed up, phone got stuck in a reboot loop, got it into download mode and put it back to a stock version. Now however, I am not able to root my phone using ioroot. This is all I get when I try to root my phone, then it just stops.
Code:
Enable ADB connection..
Developer Options unlocked and ON.
USB debugging ON.
Accept RSA key fingerprint.
Press any key to continue . . .
Waiting for ADB detection...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
When trying to change to a different stock ROM with LG FLASH TOOL 2014 I get the following error when my phone is connected to my PC with MTP.
Code:
The phone is disconnected from PC.
Connect the USB cable and wait a moment. Press the Retry button to resume the setting analysis process.
My phone is still connected, pressing the retry button brings up the same message.
When I select LG Software instead of MTP I get the following error.
Code:
To try upgrade again, follow the steps below.
1. Disconnect the phone from PC and remove hte battery from the phone.
2. Insert the battery back and reconnect the phone to PC.
3. Turn on the phone.
4. Press the Retry button below to start the upgrade.
I can't remove the battery, pressing retry after a reboot brings up the same message.
Software information:
Code:
Android version: 4.4.2
Baseband version: M8974A-AAAANAZM-1.0.190084
Kernel version: 3.4.0
Build number: KOT491.D80220h
Software version: D80220h-EUR-XX
Hardware information:
Code:
Model number: LG-D802
Memory: 32GB
So what do I want to do? Switch from the current ROM to a different one, as that is currently not possible for me. After this I wil retry to put CM13 on my phone. I am out of ideas (not that much experience) so hopefully someone on this forum can help me out!
Click to expand...
Click to collapse
Hi,
You don't need to install any further firmware. Go to this thread: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
And root your device using the tool. It should root just fine.
iubjaved said:
Hi,
You don't need to install any further firmware. Go to this thread: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
And root your device using the tool. It should root just fine.
Click to expand...
Click to collapse
After turning USB debugging off and on then using this I got a bit further.
Code:
Starting adb server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Waiting for device...
Device detected!
Pushing files...
9383 KB/s (1048328 bytes in 0.109s)
4502 KB/s (9226 bytes in 0.002s)
9376 KB/s (4017098 bytes in 0.418s)
Rebooting...
Looking for LG serial port...
Serial port not found! please insert the phone manually into Download mode.
Disconnect the USB cable and turn off the phone.
Then press and hold the Volume Up button, and while you're doing that connect the USB cable again.
Waiting for device...
When I turn my phone off, hold the volume up button while plugging in my phone to my PC it just goes to the charging screen. I however did notice that if I reboot my device and switch to LG software from MTP in the "Select USB connection method" LG One Click Root continues and the following lines appear.
Code:
Waiting for device...
Phone found at COM3!
Rooting phone...
Then nothing happens. If I switch back from LG software to MTP again after this message the following message appears.
Code:
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
##
Done
Sounds great, so I went to check the root with Root Checker which says the following when I validate my root: "Sorry! Root acces is not properly installed on this device".
Would you have any other suggestions?
MajorTemples said:
After turning USB debugging off and on then using this I got a bit further.
Code:
Starting adb server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Waiting for device...
Device detected!
Pushing files...
9383 KB/s (1048328 bytes in 0.109s)
4502 KB/s (9226 bytes in 0.002s)
9376 KB/s (4017098 bytes in 0.418s)
Rebooting...
Looking for LG serial port...
Serial port not found! please insert the phone manually into Download mode.
Disconnect the USB cable and turn off the phone.
Then press and hold the Volume Up button, and while you're doing that connect the USB cable again.
Waiting for device...
When I turn my phone off, hold the volume up button while plugging in my phone to my PC it just goes to the charging screen. I however did notice that if I reboot my device and switch to LG software from MTP in the "Select USB connection method" LG One Click Root continues and the following lines appear.
Code:
Waiting for device...
Phone found at COM3!
Rooting phone...
Then nothing happens. If I switch back from LG software to MTP again after this message the following message appears.
Code:
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
##
Done
Sounds great, so I went to check the root with Root Checker which says the following when I validate my root: "Sorry! Root acces is not properly installed on this device".
Would you have any other suggestions?
Click to expand...
Click to collapse
Then i would suggest you install kingo root and use that instead : https://www.kingoapp.com/root-lg.htm
Awesome worked, in hindsight I should've probably done some more reading up. Because I honestly have no idea what to do next. Should I install AutoRec,find a lollipop ROM install. Then root again, install AutoRec again, download CM13 together with GApps and flash these onto my device? I do realise that im starting to go off-topic, so if this is not allowed I'll post it in the official CM13 forum. Thanks for your help anyway!
MajorTemples said:
Awesome worked, in hindsight I should've probably done some more reading up. Because I honestly have no idea what to do next. Should I install AutoRec,find a lollipop ROM install. Then root again, install AutoRec again, download CM13 together with GApps and flash these onto my device? I do realise that im starting to go off-topic, so if this is not allowed I'll post it in the official CM13 forum. Thanks for your help anyway!
Click to expand...
Click to collapse
You don't need to go through all of that.
First, make sure you have the latest TWRP downloaded to your phone along with the hybrid LP bootloader for your phone.
Then, download the CM13 Rom and GApps you want to use to your phone.
Install KK AutoRec and reboot into recovery.
Flash updated TWRP and reboot back into recovery, then hybrid bootstack and reboot back into recovery (not sure entirely necessary to reboot, but it always works for me). Then you can flash most Stock-based LP or most CM13 or AOSP MM roms.
---------- Post added at 07:30 PM ---------- Previous post was at 07:26 PM ----------
One more thing - important! - take time to read through the thread of any roms you are interested in before flashing them. This will give you an idea of what, if any, issues you can expect and if any tricks are needed to get things working.
djchru said:
You don't need to go through all of that.
First, make sure you have the latest TWRP downloaded to your phone along with the hybrid LP bootloader for your phone.
Then, download the CM13 Rom and GApps you want to use to your phone.
Install KK AutoRec and reboot into recovery.
Flash updated TWRP and reboot back into recovery, then hybrid bootstack and reboot back into recovery (not sure entirely necessary to reboot, but it always works for me). Then you can flash most Stock-based LP or most CM13 or AOSP MM roms.
---------- Post added at 07:30 PM ---------- Previous post was at 07:26 PM ----------
One more thing - important! - take time to read through the thread of any roms you are interested in before flashing them. This will give you an idea of what, if any, issues you can expect and if any tricks are needed to get things working.
Click to expand...
Click to collapse
I have TWRP 2.7.0.0, downloaded the latest image from their websirte but for some reason im not able to install the image. I can't select the image within TWRP. The button that you would usually use to select images isn't there.
I've got a LG D802, so do I download the LP bootloader from here: http://forum.xda-developers.com/lg-g2/development/lg-g2-bootstacks-t3173715 ?
Appreciate the help!
MajorTemples said:
I have TWRP 2.7.0.0, downloaded the latest image from their websirte but for some reason im not able to install the image. I can't select the image within TWRP. The button that you would usually use to select images isn't there.
I've got a LG D802, so do I download the LP bootloader from here: http://forum.xda-developers.com/lg-g2/development/lg-g2-bootstacks-t3173715 ?
Appreciate the help!
Click to expand...
Click to collapse
You can use Flashify from the Play Store to install the TWRP for your device. Make sure you look at blastgator 's TWRP in the G2 Android Development section as it has special thermal control for our devices that will help keep you from damaging your screen. It is also flashable.
djchru said:
You can use Flashify from the Play Store to install the TWRP for your device. Make sure you look at blastgator 's TWRP in the G2 Android Development section as it has special thermal control for our devices that will help keep you from damaging your screen. It is also flashable.
Click to expand...
Click to collapse
Thanks for the heads up about the thermal problems, now on the thermal TWRP by blastgator. Downloaded the bootloader that I linked in my last post, flashed it and got stuck into a bootloop again. So now out of that bootloop, rooted again, and on TWRP 3.2.1-1 with thermal control. Should I try a different bootloader? Sorry for pretty much having to guide me through it with baby steps.
http://forum.xda-developers.com/lg-g2/development/boot-g2-hybrid-bootstacks-t3183219
Try this and let me know how it goes .
---------- Post added at 02:06 PM ---------- Previous post was at 02:04 PM ----------
Once you're up and running, you can check here as well http://forum.yairworkshop.com/viewforum.php?f=16
djchru said:
http://forum.xda-developers.com/lg-g2/development/boot-g2-hybrid-bootstacks-t3183219
Try this and let me know how it goes .
---------- Post added at 02:06 PM ---------- Previous post was at 02:04 PM ----------
Once you're up and running, you can check here as well http://forum.yairworkshop.com/viewforum.php?f=16
Click to expand...
Click to collapse
Should probably not have done that.
When I try to boot, nothing happens, when I hold the power button for 10 seconds the following message pops up.
Code:
ERROR : BOOT certification verify
[830]-----------------------------------
[880]
[930]Secure booting Error!
[1030]
[1080]----------------------------------
After this message the screen goes black again and nothing happens. The solution seems to be: http://forum.xda-developers.com/showthread.php?t=2582142
Problem is that I used a KDZ file to get the KK ROM on my G2 so I don't have any img. files.
You can kdz back or try getting back into recovery. If you get back to recovery, you might want to consider trying twrp 2.8.7.3.
djchru said:
You can kdz back or try getting back into recovery. If you get back to recovery, you might want to consider trying twrp 2.8.7.3.
Click to expand...
Click to collapse
KDZ'ing back means using the LG Flash Tool 2014? Because this doesn't seem to work as it says I haven't connected my phone to my PC, even tough it is connected. I cannot get back into recovery or download mode.
EDIT:
I just noted that the screen goes to black, so it's still on. No idead if this is important.
MajorTemples said:
Thanks for the heads up about the thermal problems, now on the thermal TWRP by blastgator. Downloaded the bootloader that I linked in my last post, flashed it and got stuck into a bootloop again. So now out of that bootloop, rooted again, and on TWRP 3.2.1-1 with thermal control. Should I try a different bootloader? Sorry for pretty much having to guide me through it with baby steps.
Click to expand...
Click to collapse
So you rooted and installed twrp. Then go ahead, make a full nandroid backup on an external usb via OTG and then try installing cm13 , follow steps provided by cm13 thread here.
GL
iubjaved said:
So you rooted and installed twrp. Then go ahead, make a full nandroid backup on an external usb via OTG and then try installing cm13 , follow steps provided by cm13 thread here.
GL
Click to expand...
Click to collapse
Unfortonately currently stuck on a black screen.
MajorTemples said:
Unfortonately currently stuck on a black screen.
Click to expand...
Click to collapse
Go to download mode by turning the phone completely off then hold only the volume up button while plugging it in to the computer
MajorTemples said:
Unfortonately currently stuck on a black screen.
Click to expand...
Click to collapse
I thought you successfully rooted and installed twrp. How did that happened?
I suggest go back to stock, upgrade till 5.0.2 lollipop and then root, install twrp via autorec and flash cm13. I did the same and it works. Lmk if you need further assistance.
Thanks for the suggestions, unfortunately I'm unable to enter download mode.
MajorTemples said:
Thanks for the suggestions, unfortunately I'm unable to enter download mode.
Click to expand...
Click to collapse
Hi,
If you are having issue shutting down your phone because it keeps booting back, then hold the power button ( keep holding it) until it goes black, reboot itself and goes black again. Then press volume up and insert usb into your pc to access download mode. It should fix.
If you simply cannot get into download mode, follow this guide : http://forum.xda-developers.com/showthread.php?t=2582142
LMK if it helped
iubjaved said:
Hi,
If you are having issue shutting down your phone because it keeps booting back, then hold the power button ( keep holding it) until it goes black, reboot itself and goes black again. Then press volume up and insert usb into your pc to access download mode. It should fix.
If you simply cannot get into download mode, follow this guide : http://forum.xda-developers.com/showthread.php?t=2582142
LMK if it helped
Click to expand...
Click to collapse
I have tried getting into download mode that way, but it doesn't work (has worked previously). Problem with that link is that I used a KDZ file so I dont have any img files. djchru said I can "KDZ back into recovery" but I have no idea what that means.
Hello xda members.
I had updateted my asus zenfone 2 ze550 ml to marshmallow by using custome rom. First i installed TWRP recovery successfully. Then took update zip in sd card. Then i flashed phone using that rom. But after flashing is done phone rebooted and it only shows black screen with bright light. Somwhere if we touch on screen then at some specific points screen shows vibration.. but only black screen is there. And then i can only force restart it and forcely shut down it.
Then i thoght to do everything from begaining. Now conditions is that if i connect it to my pc and tried to find adb devices. Cmd window shows device connected in recovery mode. Now i have original rom of asus zenfone 2 but how to flash phone with it when there is no display on phone and computer shows device is connected but in recovery mode.
Please help. Any help would be appreciated.
Thank you.
Follow the steps:
http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=12528
Same happend to me, can't even unbrick it.
Z00A bricked
I used twrp to update the MM zip. it hung for hours so I turned it off. now all I get is a black screen and 2 vibrations. sometimes I can get to fastboot but no matter what I select it restarts to a black screen with 2 vibrations or occasionally a group of color bars. ADB cannot see the device. I have installed intel SOCusb and tried updating the with xFSTK. device manager sees a moorefield device then it disappears, in and out. xFSTK gets through updating dnx_fwr.bin and ifwi.bin but it loses connection to the moorefield device and fails to continue on to update droidboot_dnx.img.POS_sign.bin. I have uninstalled and reinstalled intel SOCusb and xFSTK several times and tried installing them in different orders. same problem. Moorefield device loses connection. I also tried using Asus Flash Tool. sometimes it detects my device, other times not. when it does detect it and I select the raw file and it says it is flashing but nothing happens after hours. I'm not sure what else to try.
kazzot17 said:
Same happend to me, can't even unbrick it.
Click to expand...
Click to collapse
Did you and all others who are having trouble with the zenfone make sure to flash any custom kernel for your rom?? If one is available.. Just a suggestion.. Make sure you're trying to flash the right device and exact model, any follow any guides properly. Go back over and read each step thoroughly just to rule out any steps you may have missed along the way
QuietLion said:
I used twrp to update the MM zip. it hung for hours so I turned it off. now all I get is a black screen and 2 vibrations. sometimes I can get to fastboot but no matter what I select it restarts to a black screen with 2 vibrations or occasionally a group of color bars. ADB cannot see the device. I have installed intel SOCusb and tried updating the with xFSTK. device manager sees a moorefield device then it disappears, in and out. xFSTK gets through updating dnx_fwr.bin and ifwi.bin but it loses connection to the moorefield device and fails to continue on to update droidboot_dnx.img.POS_sign.bin. I have uninstalled and reinstalled intel SOCusb and xFSTK several times and tried installing them in different orders. same problem. Moorefield device loses connection. I also tried using Asus Flash Tool. sometimes it detects my device, other times not. when it does detect it and I select the raw file and it says it is flashing but nothing happens after hours. I'm not sure what else to try.
Click to expand...
Click to collapse
Sent from Sony Xperia Z5 E6653
The problem is they are trying to flash official MM with twrp. Can't be done that way.
Sent from my ASUS_Z00A using Tapatalk
Yeah, I got that far. I'm hoping for a way to unbrick it now.
kenbo111 said:
The problem is they are trying to flash official MM with twrp. Can't be done that way.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
kenbo111 said:
The problem is they are trying to flash official MM with twrp. Can't be done that way.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Ahh, yes.. In that case then you're spot on. To flash any stock firmware, the device needs to be set back to stock factory defaults. And thats because the stock kernel needs to be present so that the stock firmware (official) is able to be flashed properly without bootloops/bricking etc. Think of it as a safety feature
Sent from Sony Xperia Z5 E6653
I was on stock rom.
TheTecXpert said:
Ahh, yes.. In that case then you're spot on. To flash any stock firmware, the device needs to be set back to stock factory defaults. And thats because the stock kernel needs to be present so that the stock firmware (official) is able to be flashed properly without bootloops/bricking etc. Think of it as a safety feature
Sent from Sony Xperia Z5 E6653
Click to expand...
Click to collapse
[email protected] said:
I was on stock rom.
Click to expand...
Click to collapse
I understand that part, but since you have twrp installed, you're not actually considered as being on complete stock.. You're using a custom kernel right? Hence the whole reason why you cant flash stock MM rom via twrp
You need to flash it using a flash tool program for your specific device. (Sony = flashtool, Samsung = Odin. Etc etc).. If you dont need to back anything up orif you already have. Then just flash the stock rom via your devices flash tool using your pc or or via a method that is specific to your device..
There's really no way around it unless you wanna brick your device..
And another person has also mentioned the same thing. That you wont be able to flash stock rom via custom recovery. It ain't gonna happen..
You have to reset your device completely to stock.. And that includes STOCK kernel..
Sent from Sony Xperia Z5 E6653
That is what I'd like to do but I have not found a way to do that.
TheTecXpert said:
I understand that part, but since you have twrp installed, you're not actually considered as being on complete stock.. You're using a custom kernel right? Hence the whole reason why you cant flash stock MM rom via twrp
You need to flash it using a flash tool program for your specific device. (Sony = flashtool, Samsung = Odin. Etc etc).. If you dont need to back anything up orif you already have. Then just flash the stock rom via your devices flash tool using your pc or or via a method that is specific to your device..
There's really no way around it unless you wanna brick your device..
And another person has also mentioned the same thing. That you wont be able to flash stock rom via custom recovery. It ain't gonna happen..
You have to reset your device completely to stock.. And that includes STOCK kernel..
Sent from Sony Xperia Z5 E6653
Click to expand...
Click to collapse
same here
Ok ... first of all..
Do you have all the necessary files on your external SD CARD ready??
------------------If yes then continue on-------------------
1. Open up adb and fastboot with admin privileges..
2. connect your device to your PC in ADB mode
3. in ADB cmd type adb reboot bootloader
***If you have already completed step 4 below previously and you are sure you already have a custom recovery (TWRP) installed on your device, then skip straight to step 5***
4 fastboot flash recovery [nameofrecovery].img (Without the brackets and also Make sure The Recovery.img file is SPECIFICALLY for your MODEL.. ***ZE550ML***
5. While your device is still connected to your PC in either ADB or fastboot mode
in ADB just type the following command below
(if connected via adb) - adb reboot recovery or adb boot recovery
(If connected via fastboot) - fastboot reboot recovery or fastboot boot recovery
IF you device reboots in to TWRP successfully, then all you need to do from this point is...
1. wipe data/Factory reset
2. wipe cache partition
3. reboot now.
you should now be able to boot your device like normal
good luck
let the process complete.. after factory reset is complete proceed
QuietLion said:
I used twrp to update the MM zip. it hung for hours so I turned it off. now all I get is a black screen and 2 vibrations. sometimes I can get to fastboot but no matter what I select it restarts to a black screen with 2 vibrations or occasionally a group of color bars. ADB cannot see the device. I have installed intel SOCusb and tried updating the with xFSTK. device manager sees a moorefield device then it disappears, in and out. xFSTK gets through updating dnx_fwr.bin and ifwi.bin but it loses connection to the moorefield device and fails to continue on to update droidboot_dnx.img.POS_sign.bin. I have uninstalled and reinstalled intel SOCusb and xFSTK several times and tried installing them in different orders. same problem. Moorefield device loses connection. I also tried using Asus Flash Tool. sometimes it detects my device, other times not. when it does detect it and I select the raw file and it says it is flashing but nothing happens after hours. I'm not sure what else to try.
Click to expand...
Click to collapse
try the following guide if helps hit thanks button
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
---------- Post added at 05:57 AM ---------- Previous post was at 05:56 AM ----------
t00lshed said:
same here
Click to expand...
Click to collapse
try the following guide if helps hit thanks button. any question post in that thread.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
---------- Post added at 05:58 AM ---------- Previous post was at 05:57 AM ----------
utsav.goswami1986 said:
Hello xda members.
I had updateted my asus zenfone 2 ze550 ml to marshmallow by using custome rom. First i installed TWRP recovery successfully. Then took update zip in sd card. Then i flashed phone using that rom. But after flashing is done phone rebooted and it only shows black screen with bright light. Somwhere if we touch on screen then at some specific points screen shows vibration.. but only black screen is there. And then i can only force restart it and forcely shut down it.
Then i thoght to do everything from begaining. Now conditions is that if i connect it to my pc and tried to find adb devices. Cmd window shows device connected in recovery mode. Now i have original rom of asus zenfone 2 but how to flash phone with it when there is no display on phone and computer shows device is connected but in recovery mode.
Please help. Any help would be appreciated.
Thank you.
Click to expand...
Click to collapse
try the following guide if helps hit thanks button. any question post in that thread.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
sukhwant717 said:
try the following guide if helps hit thanks button
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
---------- Post added at 05:57 AM ---------- Previous post was at 05:56 AM ----------
try the following guide if helps hit thanks button. any question post in that thread.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
---------- Post added at 05:58 AM ---------- Previous post was at 05:57 AM ----------
try the following guide if helps hit thanks button. any question post in that thread.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
Hi! yes, i did that, my phone showed in devices manager as Moorefield and xfstk dont show any errors after the "begin download" The process is completed without any problem. The phone restart and show me the 4 colours and then restart, not showing me the fastboot. I did many times the process of xfstk, but always is the same result.
pd: excuse my english.
t00lshed said:
Hi! yes, i did that, my phone showed in devices manager as Moorefield and xfstk dont show any errors after the "begin download" The process is completed without any problem. The phone restart and show me the 4 colours and then restart, not showing me the fastboot. I did many times the process of xfstk, but always is the same result.
pd: excuse my english.
Click to expand...
Click to collapse
can you post a screenshot of your pc of xFSTK window. i mean in which columns you selected three files.
does it give you four color bar?
sukhwant717 said:
can you post a screenshot of your pc of xFSTK window. i mean in which columns you selected three files.
does it give you four color bar?
Click to expand...
Click to collapse
yes of course, is attached. The phone gives me four color bar (pink,yellow,other pink i think and green)
t00lshed said:
yes of course, is attached. The phone gives me four color bar (pink,yellow,other pink i think and green)
Click to expand...
Click to collapse
when you get 4 bar. just follow the steps given in following link. do not use asus flash tool. when you get 4 color bar go to adb and fastboot folder and see if fastboot recognize your device.and please post your question in the following thread it will help others too.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
i will answer any quest after two hours gotta go somewhere
sukhwant717 said:
when you get 4 bar. just follow the steps given in following link. do not use asus flash tool. when you get 4 color bar go to adb and fastboot folder and see if fastboot recognize your device.and please post your question in the following thread it will help others too.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
i will answer any quest after two hours gotta go somewhere
Click to expand...
Click to collapse
ok thanks! I did what you tell me but nothing happen, fastboot devices dont recognize my zf2 after xfstk and the 4 bar color.
t00lshed said:
ok thanks! I did what you tell me but nothing happen, fastboot devices dont recognize my zf2 after xfstk and the 4 bar color.
Click to expand...
Click to collapse
can you please upload xFSTK log file
you are using windows 10 did you disabled driver signature enforcement before installing xFSTK and driver?
Many people like me did buy its Xiaomi Mi 5S from Chine wich official Chinese ROM. The problem of this ROM is that unless you are Chinese you dont really enjoy it. But now since the official Global ROM was released all was supposed to be saved and beautiful. Except you could not flash it using the built-in flashing (update) tool of the ROM it just would not recognize it as valid and thats that.
First and most recognized solution you would find is Unlock bootloader and flash it via fastboot (MiFlash windows app). In order to unlock a Xiaomi you have to Apply for unlock and give them specific reason to grant you your wish (pretty lame). Than after unlock it will work. It takes them less then 10 days (official Xiaomi), if not you should write on their forum. Not sure if anyone did not get it, but its still stupid.
There used to be option to do this using EDL mode (or Download mode), but there is no EDL in Mi 5s any more, so no luck here either.
So here is option number two that will always work without unlocking bootloader. It will even work with bricked phones. It is called Deep Flash. This option works only with Qualcom machines (f.e. Snapdragon) and what it does is, it connects your smartphone to your computer via one of COM ports using the Qualcom drivers. Dont ask me how exactly, I dont know, dont care. It just works The whole point of this method is the Deep Flash Cable, you need it and you either make it yourself (real easy) od buy one on Aliexpress (easier, but you have to wait long).
Here is video with the procedure of deep flashing: https://youtu.be/tdk0d2Zrm9w
Here is an OK website with the whole procedure including how to make Deep Flash cable: http://www.stupdroid.com/2016/10/make-xiaomi-deep-flash-cable-and.html
Here is link to the official FASTBOOT Global ROM: http://en.miui.com/thread-454687-1-1.html
Here is link to MiFlash tool: http://en.miui.com/thread-345974-1-1.html - I beleive the new version already has Qualcom drivers included.
If windows was making you trouble and your Qualcom driver will not install here is why: http://en.miui.com/thread-237673-1-1.html
I also attach pictures of my cable and a schematic of what you are actually doing. It is really a simple thing to do. It took me like 20 minutes. No special skills required, and I used only sharp knife, did not even have a razer. I used some random cable, not genuine Xiaomi cable as the guide says. I used non copper cables to connect B and G (I canibalized some other old USB cable).
IMPORTANT NOTE, keep with the flash procedure exactly as it says, or you will get errors ("cannot receive hello packet") when flashing like I did.
1. MiFlash is not running on your PC, Your phone is turned OFF, The two cables (B and G) are connected together, Your Device Manager is ON
2. You connect the Deep Flash cable to your PC use USB 2.0 port (USB 3.0+ are reported not to work)
3. You connect the Deep Flash cable to your Mi5S
4. Wait for 10 seconds. (just count to 13 or something) - apparently this may save you from the "hello packet" error
5. You disconnect the two cables (B and G) - in Device Manager you will see something like Qualcom HS-USB Diagnostic 9008 - keep cables disconnected
6. Only now you launch MiFlash by going to C:\XiaoMi\XiaoMiFlash and Right-clicking on XiaoMiFlash.exe and Run as Administrator
7. In MiFlash tool Press Refresh button - you will see your phone on one COM port
8. Browse to your Global Rom (f.e. capricorn_global_images_V8.0.3.0.MAGMIDI_20161222.0000.00_6.0_global) under this folder you will see folder named image
9. Press Refresh one more time
10. Press Flash and have a coffe (took mine 5 minutes)
11. After you see nice green success you turn off MiFlash
12. Disconnect the cable from phone
13. Boot the phone - dont panic first boot is very long
There ya go. You are now on Xiaomi Mi5S with Global ROM with still locked bootloader. This guide should work with Mi5S Plus, but I did it on my Mi5S only.
Special thanx to XN Logos and his post about unbricking. This one is literarly the same method. But I myself ran around that post 10 times when searching for solution to my problem and never knew this in fact is solution to my problem aswell :silly:
Thanx to awaaas for mentioning the disclaimer about USB 3.0 ports.
Thanx to cerietke for mentioning the 10 second pause in step 4.
Great guide! Unfortunately I have unlocked my device to change to global rom. Hopefully it will benefit other. UP!
I tried following these instructions but have ran into one problem which I managed to solve. In case MiFlash shows an error "cannot receive hello packet" you have to make sure adb driver is installed. More about this is written in this topic: en.miui.com/thread-299790-1-1.html
You can make a backup with built in MIUI app, then copy it to your pc and restore after flashing.
Now I can enjoy a ROM without crappy chinese apps and all notifications are working from the beginning.
Are there any advantages of deep flash method over standard with unlocked bootloader?
Rejerf said:
Are there any advantages of deep flash method over standard with unlocked bootloader?
Click to expand...
Click to collapse
Well you do not have to unlock the bootloader for once. But other than that, no, there are none. But with Xiaomi you have to be approved for unlock case by case and it takes them approx 3 days. But it is just flashing. ROM is the same.
i try this prozedre with help by simply silver paper. what should i say, this also works. xdddd
neverless, i still wait for the "deep flash" cable from aliexpress.
best regards
I tried everything, with the lots of guides, I made my own deep flash cable, I succeeded in putting my mi 5s Plus into deep flash mode but did not succeeded in flashing the Rom.
Every time there is the error message from the Mi flasher cannot receive hello packet etc. Then I applied for unlock boot loader officially. I got SMS with the unlocking permission in 15 minutes. After unlocking boot loader, I put my phone into fast boot mode and flashed fast boot Rom and everything is fine. No error ..nothing. So, I do not want to disappoint anybody, but this method did not worked for me.
Just want to add a note, this method would not work if you use USB 3.0+ port (or USB 2.0 behind USB 3.0 hub) such as on a intel's skylake/kabylake-based machine.
Maybe that's your problem @richie16171?
richie16171 said:
I tried everything, with the lots of guides, I made my own deep flash cable, I succeeded in putting my mi 5s Plus into deep flash mode but did not succeeded in flashing the Rom.
Every time there is the error message from the Mi flasher cannot receive hello packet etc. Then I applied for unlock boot loader officially. I got SMS with the unlocking permission in 15 minutes. After unlocking boot loader, I put my phone into fast boot mode and flashed fast boot Rom and everything is fine. No error ..nothing. So, I do not want to disappoint anybody, but this method did not worked for me.
Click to expand...
Click to collapse
Good point from awaas I did not know that. Try that too.
But I was getting the same error as you. What you need to do is follow my instructions religiously. It made difference to me when I skipped some point or did something parallel. Do exactly as my guide says. Disconnect and turn everything off and start from point one exactly like the guide says.
I remember it was different when I had flashing tool open before and after some point. So go exactly as the guide and you should be fine
awaaas said:
Just want to add a note, this method would not work if you use USB 3.0+ port (or USB 2.0 behind USB 3.0 hub) such as on a intel's skylake/kabylake-based machine.
Maybe that's your problem @richie16171?
Click to expand...
Click to collapse
Nope ..it was USB 2.0 and I am using laptop. I tried all the ports in the computer. Tried with another computer and not once 7 times.
---------- Post added at 02:24 PM ---------- Previous post was at 02:07 PM ----------
Seehank said:
Good point from awaas I did not know that. Try that too.
But I was getting the same error as you. What you need to do is follow my instructions religiously. It made difference to me when I skipped some point or did something parallel. Do exactly as my guide says. Disconnect and turn everything off and start from point one exactly like the guide says.
I remember it was different when I had flashing tool open before and after some point. So go exactly as the guide and you should be fine
Click to expand...
Click to collapse
I did exactly what you said 100%. As I said not once.., with driver signature off and on. I did not had any driver problem. It was showing me the port com16.
I think that is not the right port for flashing.
richie16171 said:
Nope ..it was USB 2.0 and I am using laptop. I tried all the ports in the computer. Tried with another computer and not once 7 times.
---------- Post added at 02:24 PM ---------- Previous post was at 02:07 PM ----------
I did exactly what you said 100%. As I said not once.., with driver signature off and on. I did not had any driver problem. It was showing me the port com16.
I think that is not the right port for flashing.
Click to expand...
Click to collapse
Well man, than this is the end of me :-/ I know I was getting this error when I had MiFlash turned on before I connected my phone to the PC . That gave me same error. But when it was off before and after deep flashmode a opened it up as admin (from the directory, not Start) it worked for me just fine.
Does anyone know if this works in 8.2? When I plug cable in it starts charging..
Agirretxd said:
Does anyone know if this works in 8.2? When I plug cable in it starts charging..
Click to expand...
Click to collapse
The 8,2 hasa big problem with battery drain. Mine 5s has poor battery life now. Just wait a bit.
Is there any work being done on official Lineage OS for the Mi5S?
richie16171 said:
I tried everything, with the lots of guides, I made my own deep flash cable, I succeeded in putting my mi 5s Plus into deep flash mode but did not succeeded in flashing the Rom.
Every time there is the error message from the Mi flasher cannot receive hello packet etc. Then I applied for unlock boot loader officially. I got SMS with the unlocking permission in 15 minutes. After unlocking boot loader, I put my phone into fast boot mode and flashed fast boot Rom and everything is fine. No error ..nothing. So, I do not want to disappoint anybody, but this method did not worked for me.
Click to expand...
Click to collapse
Hey,
I just tried to reflash mine and just like you said I was getting all the errors. No way to fix it But then I uninstalled (also deleted every single file) the MiFlash tool and after installing it again it worked Sooo probably there is some log file or some setting or I dont know what that is doing trouble.
@ Seehank., Thank you so much, Maybe that is the problem... otherwise so many people succeeded doing this, Only I failed.
Now no point. I already unlocked boot loader and flashed the firmware. And that also I flashed in fast boot mode.
Now I have one more Mi note3 pro. And it is the used phone. Someone already unlocked boot loader. That is why or for some reason I was not getting OTA update. Hence the boot loader is unlocked, and I tried to flash with the fast boot mode.. No.. I am getting error. In flash tool it is not showing Com Port..instead some serial number. So I flashed that in EDL mode and success. After that now I am getting OTA update.
Hope this may help others with the hello packet issue.
I was following your guide, but I was going through pretty quickly, which turned out to be relevant. I did some searching on the issue and discovered a post on en.miui.com that suggested a solution (post 32 in the "[Help]-cannot receive hello packet,MiFlash is trying to reset status" topic; as a new user I cannot post outside links). Apparently you'd need to wait at least 10 seconds between step 3 and 4. As I also did a full reboot of the phone without the cable attached that may have also been the solution. I did not further test as I got it working.
Hi guys, have locked phone on purchase, thought I might revive it with above methode but...no way I coulkd install quallcomn drivers, tried (i think) everything, phone gets into charging mode, nothing happens in Device manager...
cerietke said:
Apparently you'd need to wait at least 10 seconds between step 3 and 4.
Click to expand...
Click to collapse
I will add this to the guide. It can not harm anyone So between my guide and steps 3 and 4 wait 10+ seconds.
Hi mate, i followed your guide, everything works till the very last point, when i boot my phone (after the success message in the MiFlash), 2 strange things happen:
1) first time i press "power" button it wont start, i press a second time and it starts
2) the MI logo starts blink every x minutes, but actually is not going forward (still stuck on MI logo after more than 10 mins waiting)
can you help me somehow? Thanks
(or is it hard brick)
Hi,
A2017G
Started with marshmallow,
Unlocked bootloader
attempted to install Slim7
seemed to work but with some possible errors, (wouldn't sync with google... retrospect I should have looked elsewhere before...)
attempted in install stock rom
using
ZTE_A2017GV1.2.0B04_BootStack_by_tron1.zip
ZTE_A2017GV1.2.0B04_Stock_System_by_tron1.zip
which wouldn't boot
So I tried reinstall Slim7
then stock again,
then, like the noob that I am, I removed twrp with
ZTE_A2017GV1.2.0B04_Full_Stock_Reverter_by_tron1.zip
which installs stock recovery
so, now I have a stock rom that won't boot,
an unlocked bootloader
and stock recovery
Not sure what to do from here
thanks in advance for any assistance.
I can abd sideload and update from SD card, but everything I have fails signature verification.
edit: so frustrating trying to find that 1 zip
Dizzee said:
(or is it hard brick)
Hi,
A2017G
Started with marshmallow,
Unlocked bootloader
attempted to install Slim7
seemed to work but with some possible errors, (wouldn't sync with google... retrospect I should have looked elsewhere before...)
attempted in install stock rom
using
ZTE_A2017GV1.2.0B04_BootStack_by_tron1.zip
ZTE_A2017GV1.2.0B04_Stock_System_by_tron1.zip
which wouldn't boot
So I tried reinstall Slim7
then stock again,
then, like the noob that I am, I removed twrp with
ZTE_A2017GV1.2.0B04_Full_Stock_Reverter_by_tron1.zip
which installs stock recovery
so, now I have a stock rom that won't boot,
an unlocked bootloader
and stock recovery
Not sure what to do from here
thanks in advance for any assistance.
Click to expand...
Click to collapse
Just use MiFlash, that one's guaranteed to work. Read my DFU unbrick guide to know how to use it. Just skip the part where you have to disassemble the phone, since you can get to EDL mode by (with the phone off and the USB cable connected to the PC) holding both volume buttons and inserting the USB-C cable to the phone.
I did read your guide, was, hoping to avoid dismantling it...
I tried pressing all 3 buttons.
Am I understanding the procedure correctly:
[phone switched off] + usb-C cable connected to PC only
MiFlash running at this point??
Hold both volume keys in and in insert Cable to Phone
at this point is the phone supposed to switch on?
At no point am I supposed to press the power button?
fyi: I will try different combinations, is great to have a solution, thank you.
Ah.... ok... so, the phone will display nothing, rely on the sound of PC and/or the device manager check and/or hit refresh on miflash
Fyi to anyone, if you have axon7toolkit installed and thus can't install a second version of MiFlash, open up the toolkit and hit 7 (unlock bootloader) to fire up MiFlash... or just go to C:\XiaoMi\XiaoMiFlash
the FULL_EDL file I have produces a couldn't find script Error when loading into MiFlash
so far when attempting to flash all zips
I have started MiFlash with admin
unzipped FULL_EDL file to a folder in root C:\ and ensured there are no spaces in address.
Every time / Every file produces couldn't find script error when loaded into MiFlash
when I attempt to flash the file it says cannot receive hello packet and then times out with an error
Tried disabling anti-virus/firewall, still same error
upgraded MiFlash to 2017.4.24.0 ( older 2016 is included with axon7toolkit), this removes the couldn't find script error, but still not receiving a hello packet, gunna fiddle with the phone as I'm pretty sure the error is coming from there
YES!
rebooted phone, turned off, restarted into EDL, flashed the stock rom from zte site... is in chinese... but it works. Thank you Thank you
so adventure over, after all that I am back to 6.0.1...
Dizzee said:
I did read your guide, was, hoping to avoid dismantling it...
I tried pressing all 3 buttons.
Am I understanding the procedure correctly:
[phone switched off] + usb-C cable connected to PC only
MiFlash running at this point??
Hold both volume keys in and in insert Cable to Phone
at this point is the phone supposed to switch on?
At no point am I supposed to press the power button?
fyi: I will try different combinations, is great to have a solution, thank you.
Ah.... ok... so, the phone will display nothing, rely on the sound of PC and/or the device manager check and/or hit refresh on miflash
Fyi to anyone, if you have axon7toolkit installed and thus can't install a second version of MiFlash, open up the toolkit and hit 7 (unlock bootloader) to fire up MiFlash... or just go to C:\XiaoMi\XiaoMiFlash
the FULL_EDL file I have produces a couldn't find script Error when loading into MiFlash
so far when attempting to flash all zips
I have started MiFlash with admin
unzipped FULL_EDL file to a folder in root C:\ and ensured there are no spaces in address.
Every time / Every file produces couldn't find script error when loaded into MiFlash
when I attempt to flash the file it says cannot receive hello packet and then times out with an error
Tried disabling anti-virus/firewall, still same error
upgraded MiFlash to 2017.4.24.0 ( older 2016 is included with axon7toolkit), this removes the couldn't find script error, but still not receiving a hello packet, gunna fiddle with the phone as I'm pretty sure the error is coming from there
YES!
rebooted phone, turned off, restarted into EDL, flashed the stock rom from zte site... is in chinese... but it works. Thank you Thank you
so adventure over, after all that I am back to 6.0.1...
Click to expand...
Click to collapse
What? It's in chinese?
Can you tell me the name of the file you used? Do you still have cell signal?
Choose an username... said:
What? It's in chinese?
Can you tell me the name of the file you used? Do you still have cell signal?
Click to expand...
Click to collapse
I got it from here: http://www.ztedevice.com/support
selected:- United Kingdom > Mobile Phone > Axon 7
it offers a file "AXON 7(ZTE A2017G) SD card software package(328540B2634ZTE A2017GV1.0.0B11)"
which hints at being compatible with A2017G... but is A2017V and is chinese, although you can change the language in settings there is still plenty here and there, plus chinese bloatware
and No, I didn't get cell signal.
I've gone back to Marshmellow, I will try again, didn't think it would be so different/difficult... Although wow at MiFlash.
FFS!!!! Relocked bootloader and bricked it!!! there should be a warning!
you gotta laugh,
I am a bit livid, I know the guides come with disclaimers, however, you'd think it would be an obvious important warning to make... DO NOT RELOCK YOUR PHONE.
FFS!
Dizzee said:
FFS!!!! Relocked bootloader and bricked it!!! there should be a warning!
you gotta laugh,
I am a bit livid, I know the guides come with disclaimers, however, you'd think it would be an obvious important warning to make... DO NOT RELOCK YOUR PHONE.
FFS!
Click to expand...
Click to collapse
Good lord...
You probably wiped out both IMEIs, now you relock out of the blue... Go to my DFU unbrick guide and stop doing dumb stuff :silly:
Choose an username... said:
Good lord...
You probably wiped out both IMEIs, now you relock out of the blue... Go to my DFU unbrick guide and stop doing dumb stuff :silly:
Click to expand...
Click to collapse
... after I finally got it working again (thanks for the assist), I thought relocking it was just making it secure again. I been rooting/unrooting and swapping out roms since the galaxy s2, who'd think you can't unlock and relock... I do think there should be warnings as it is too easy a mistake to make... lmao stop doing dumb stuff you start first
My phone is insured so I'm not overly fussed, but others will be less fortunate.
hello everywone...i have a troble to...my phone is A2017GV1.2.0B04 like this in post.
I bay this phone whit broken screen, i change the screen and try sim card but the phone is locked Whit google account... When I try my sim to test microphone, the phone it's work OK, but I unlock google account whit add tools and after that my phone don't have a service.
Phone tells no service or turned off airplane mode...what is not true... I can change the 4g/3g/2g connection to only 3g or something else... Wi-Fi and everything else work great but no service... The phone see what operator is on sim but no service... Somebody to help me please and tell me some tutorials how to fix?
I by this phone from Denmark and now I'm in Serbia... Eny help please
Thanks anyway Dragan
---------- Post added at 08:30 PM ---------- Previous post was at 08:27 PM ----------
Mistake,whit adb tools...