Related
SOLVED
See my most recent post in this thread
______________________________________________________________________________________
Firstly, I've spent the last three days scouring XDA and some other forums searching for solutions and trying various options.
The screen on my N4 has cracked and I've lost the use of the bottom half of the touchscreen. This means that I can't unlock my phone.
The phone is insured and will be repaired, but there are photos of my son's first birthday on the internal memory that I don't want to lose. I'm concerned that the phone will be factory reset during a repair or I'll receive a replacement. I'm trying to access the internal memory remotely to backup these files before I send the phone off. The problem is that I hadn't enabled USB debugging before the accident. The phone is completely stock including the bootloader.
So I can access via fastboot but not via adb.
Q1: Can I pull file from the internal memory via fastboot
Q2: Can I enable usb debugging via fastboot
Q3: The phone is set to display as an MTP device in windows but as I can't unlock the screen, none of the files are showing. Is there anyway around this?
Q4: Purely via fastboot, can I unlock the bootloader, install CWM so to use ADB within it and then return to a stock bootloader?
I think they're my options. Any answers to the above or alternatives would be appreciated.
All of the other threads regarding this, the users seem to either already have CWM installed or they're looking to perform a factory reset. I did consider resetting the device via the bootloader in order to bypass the screenlock but I understand that on the N4 this wipes the internal memory as well.
Unlocking the device isn't needed to pull the files from it, just plug it in and get what you need from the internal memory
EddyOS said:
Unlocking the device isn't needed to pull the files from it, just plug it in and get what you need from the internal memory
Click to expand...
Click to collapse
On mine if I plug it in it appears as an MTP device but with no files. I then have to unlock the screen and select USB something-or-other from the notificationss bar, then the files appear in windows.
Strange, mine never needs to be unlocked...I'm using Windows 8 Pro btw but it also works fine in work on Vista Business
Only other thing I can think of is the fact I'm unlocked and running a custom ROM, I've never used my N4 stock. It was on CM within 30 mins of receiving the unit!
So over the last week I've managed to solve my problem. I've seen several other people asking for help with no luck so I'm posting this here in the hope that the search function will bring it up.
Firstly, my phone was completely stock running 4.2.2, unrooted, with the locked stock bootloader. USB Debugging WAS NOT enabled. I had pattern lock enabled when I dropped the phone. The screen cracked and the bottom half of the touchscreen was unresponsive.
The phone was insured, but I wanted to backup photos from the device before sending it off for repair/replacement.
HOW I FIXED IT.
Please note, you need at least some part of the screen to be working, specifically, some part of the screen where the pattern lock is.
You only need two pieces of software. The Android SDK and the Nexus 4 Toolkit http://forum.xda-developers.com/showthread.php?t=1995688
If you are running 4.2.2 you will need to update the toolkit. I also had the standard issues of installing the USB drivers for the N4. You need to get to a point where is shows up as an ADB device in Windows Device Manager.
As I didn't have USB debuggin enabled I couldn't connect tothe phone via ADB, but if you put it into recovery mode you can use Fastboot. Hold down the power key to turn the device off and turn it on while holding down Vol Down to load up recovery mode.
If you then start the N4 Toolkit, you should see the device listed as a fast boot device.
From within the toolkit unlock your bootloader.
Flash a temporary bootlader, (option 10) as the touchscreeen was broken it has to be CWM.
Once in CWM you can start to use ADB. Open up a DOS command prompt in Windows, go to your SDK/platform tools folder/ to access ADB.exe and you can use the pull command to copy folders to your PC. At this point, instead you can use applications like ADBexplorer or DroidExplorer to do the same thing through a nicer GUI.
If you'd like to still be able to use your phone, although without the touchscreen, you can load an unstable image to get into android and then use ADB to start changing system settings.
Firstly, before exiting CWM, clear the cache. Without doing this the phone jsut hung on the Nexus symbol while loading the image.
in the toolkit go to root/unroot options and select load unstable image(option 4 and then 6). This will fire you up into Android and it should be set up as you left it.
I wanted to enable bluetooth so to use a keyboard (I didn't have a mouse but this is a better option) from the DOS window type the following command
am start -a android.bluetooth.adapter.action.REQUEST_ENABLE
You should eventually get a pop-up on your screen saying that a request has been made to enable bluetooth. Hopefully your screen is working enough to select enable.
Then I use the workaround to disable the sceenlock, found here -> (http://www.addictivetips.com/androi...e-pattern-unlock-on-android-via-adb-commands/) I found method 2 worked for me. I imagine this will be stopped in a future update.
Method 1
adb shell
cd /data/data/com.android.providers.settings/databases
sqlite3 settings.db
update system set value=0 where name='lock_pattern_autolock';
update system set value=0 where name='lockscreen.lockedoutpermanently';
.quit
Method 2
adb shell rm /data/system/gesture.key
If either of these methods are successful you will be able to unlock the phone with an pattern, hence why you need to be able to touch some part of it.
From then, my bluetooth keyboard was already mated to my phone to I was able the navigate the menus to turn on USB Debugging, turn-off the screen lock and a few other bits and pieces I needed to do.
I then restarted (I was still working within the unstable image) and on reboot, all my changes had al been applied. No screen lock, bluetooth enabled and USB Debugging enabled.
Hopefully this will be of help to those in a similar position. Thanks has to go to the toolkit though which provides all the necessary access to carry this out.
I should probably add, you can use the toolkit to relock the bootlader if you're concerned about that and if you can't click the screen to enable bluetooth or mate a keyboard or mouse, once you have USB Debugging enabled you can use software like Screencast to control you phone's screen from a PC.
So typically, just as I fill my claim to repair my nexus my wife drops her, smashing the screen even more than I did so she has absolutely no use of her screen. I went through the process again and though I'd post it in a more simple fashion.
1. Reset Nexus into recovery mode (power & volume down)
2. Connect to PC via USB. Install the USB driver from the SDK so that it appears as an ADB device
3. Fire up the updated toolkit. You should see the nexus as a fast boot device
4. Unlock bootloader
5. Using option 10 on the toolkit load up CWM on the phone. This gives you ADB access so can you pull files off the device via ADB although I could access the SD card through programs like Droid explorer.
6. If you want to carry on further and get into Android properly, you'll need to wipe the cache from within CWM
7. Reboot and hold down the volume key to get back into recovery
8. In the toolkit select root options (option 4) and load temporary image (6) If it hangs on the google or nexus logo you've not wiped the cache.
9. With this second phone I couldn't access it through droid explorer as it was popping up as an MTP device but I could pull the files via command prompt or through the toolkit
10. If you have any use of the touchscreen at all you can run the following command which will then mean that any touch will unlock the device
adb shell rm /data/system/gesture.key11. You can activate bluetooth via adb if you have a mouse or keyboard available but you will need to be able to press okay on the screen
12. Any changes you make in the unstable android image such as lockscreen, bluetooth, enabling debugging, etc will remain in place when you restart the device.
13. You can relock the bootloader if you wish via the toolkit. You just need to be in recovery mode first.
Hope this simplifies the process
Does unlocking bootloader via toolkit not wipe everything? How are you unlocking bootloader and still able to pull data off?
EDIT: it appears fastboot oem unlock on the Nexus 4 *does not* wipe data!
Carpetboy said:
So typically, just as I fill my claim to repair my nexus my wife drops her, smashing the screen even more than I did so she has absolutely no use of her screen. I went through the process again and though I'd post it in a more simple fashion.
1. Reset Nexus into recovery mode (power & volume down)
2. Connect to PC via USB. Install the USB driver from the SDK so that it appears as an ADB device
3. Fire up the updated toolkit. You should see the nexus as a fast boot device
4. Unlock bootloader
5. Using option 10 on the toolkit load up CWM on the phone. This gives you ADB access so can you pull files off the device via ADB although I could access the SD card through programs like Droid explorer.
6. If you want to carry on further and get into Android properly, you'll need to wipe the cache from within CWM
7. Reboot and hold down the volume key to get back into recovery
8. In the toolkit select root options (option 4) and load temporary image (6) If it hangs on the google or nexus logo you've not wiped the cache.
9. With this second phone I couldn't access it through droid explorer as it was popping up as an MTP device but I could pull the files via command prompt or through the toolkit
10. If you have any use of the touchscreen at all you can run the following command which will then mean that any touch will unlock the device
adb shell rm /data/system/gesture.key11. You can activate bluetooth via adb if you have a mouse or keyboard available but you will need to be able to press okay on the screen
12. Any changes you make in the unstable android image such as lockscreen, bluetooth, enabling debugging, etc will remain in place when you restart the device.
13. You can relock the bootloader if you wish via the toolkit. You just need to be in recovery mode first.
Hope this simplifies the process
Click to expand...
Click to collapse
Please HELP, i can get to step 5...but then, when I try to use ADB via cmd (ie. adb shell), it says "error: device offline". what can it be? I don't know if this is a driver related issue (i've tried the toolkit drivers and the SDK drivers)...i'm desperated, I can't access the phone!!
Thanks in advance
not working for me
i'm in same boat with cracked screen. i can get CWM installed but i cant enabled usb debugging without touching the screen so i cant get adb working. how did you turn on usb debugging without the screen
Thanks for the guide.
Im curious on why youd want to boot an unstable(temporary) image after pulling the files using ADB in CWM recovery. Why not just wipe cache and reboot normally into Android ?
usb debugging without screen?
compsmart said:
i'm in same boat with cracked screen. i can get CWM installed but i cant enabled usb debugging without touching the screen so i cant get adb working. how did you turn on usb debugging without the screen
Click to expand...
Click to collapse
Can someone please walk me through how to do this? My screen is completely broken, but I can still turn on/off, I have reason to believe debugging is off because when I connect the phone (a Samsung galaxy sII skyrocket) to my Toshiba laptop via a micro USB, it makes a sound to signal that it's connected. Drives E and F then open up (but are empty) and then disappear. I have no idea what's going on but I absolutely cannot lose all of the data on this phone. Pictures and videos from my old blackberry Torch are on here too, making up about 4 years of my daughter's life that I would lose if I cannot retrieve. Also, I am not super -tech savvy, so if someone could help me I would be forever grateful.
Please!!
:crying:
almost the same issue
I have an Asus memo pad 10 (smart) some of the core apps have been corrupted, (keyboard, UI, launcher etc all the essential stuff) I've been trying to reinstall my UI and launcher from my computer when i found out that USB debugging was disabled. the tablet is basically unusable, i have no way of enabling from the tablet itself. is there a piece of script or something i could run from my PC to enable it?
any help would be greatly appreciated :crying:
bob mc bob said:
I have an Asus memo pad 10 (smart) some of the core apps have been corrupted, (keyboard, UI, launcher etc all the essential stuff) I've been trying to reinstall my UI and launcher from my computer when i found out that USB debugging was disabled. the tablet is basically unusable, i have no way of enabling from the tablet itself. is there a piece of script or something i could run from my PC to enable it?
any help would be greatly appreciated :crying:
Click to expand...
Click to collapse
My screen became unresponsive a while back. I ended up getting and OTG cable and plugging in a mouse. This allowed me to do everything as if the touchscreen was working. There's also an app called MyMobiler that let me plug in my device over USB and control my screen from my PC. Those two helped me enable USB Debugging, flash a custom ROM, root the phone, backup everything I needed, then restore the phone to stock. I hope this helps.
*Sorry for bumping such an old post*
Thanks for the really useful guide!
Could you or someone just confirm to me that unlocking the bootloader does not factory reset? The reason I'm doing this process is to access my personal data so it's important that I can keep it all.
I ask because at the unlock bootloader stage it implicitly warns me that there'll be a factory reset.
Thanks again!
HikerMan said:
*Sorry for bumping such an old post*
Thanks for the really useful guide!
Could you or someone just confirm to me that unlocking the bootloader does not factory reset? The reason I'm doing this process is to access my personal data so it's important that I can keep it all.
I ask because at the unlock bootloader stage it implicitly warns me that there'll be a factory reset.
Thanks again!
Click to expand...
Click to collapse
Unlocking to bootloader will wipe your device
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Unlocking to bootloader will wipe your device
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
In that case, I am confused as to how OP managed to unlock his bootloader. He actually states that the purpose of this was to retrieve data, like me.
Also, in a previous comment in this thread by jw95275, they claim that "it appears fastboot oem unlock on the Nexus 4 *does not* wipe data".
I am concerned about the conflicting answers so far, so will hold off for an explanation before I do anything. Thanks for the response!
HikerMan said:
In that case, I am confused as to how OP managed to unlock his bootloader. He actually states that the purpose of this was to retrieve data, like me.
Also, in a previous comment in this thread by jw95275, they claim that "it appears fastboot oem unlock on the Nexus 4 *does not* wipe data".
I am concerned about the conflicting answers so far, so will hold off for an explanation before I do anything. Thanks for the response!
Click to expand...
Click to collapse
You should just be able to "fastboot boot recovery.img" and boot CWM and then use ADB. W/O unlocking the BL
npjohnson said:
You should just be able to "fastboot boot recovery.img" and boot CWM and then use ADB. W/O unlocking the BL
Click to expand...
Click to collapse
This did not work for me. I have a Nexus 4 with a broken digitizer, locked bootloader, and usb debugging disabled. I need to grab some data off.
I've tried `fastboot flash recovery {{recovery .img}}` and `fastboot boot {{recovery .img}}` without unlocking the bootloader first, and via both methods, I get back "FAILED (remote: not supported in locked device)"
So I'm not sure how people are able to get into custom recovery without first unlocking BL/losing all their data. Can someone explain?
jinglejuice said:
This did not work for me. I have a Nexus 4 with a broken digitizer, locked bootloader, and usb debugging disabled. I need to grab some data off.
I've tried `fastboot flash recovery {{recovery .img}}` and `fastboot boot {{recovery .img}}` without unlocking the bootloader first, and via both methods, I get back "FAILED (remote: not supported in locked device)"
So I'm not sure how people are able to get into custom recovery without first unlocking BL/losing all their data. Can someone explain?
Click to expand...
Click to collapse
On some (few) Motorola devices (not nexus 4), you can fastboot boot without unlocking the BL.
As the title says, I wanted to try CM installer, and I was on everything stock, not rooted. I downloaded PC, and android programs, followed the instructions, however at one point CM installer on my PC said it cannot communicate with my phone, and it was when it was trying to flash recovery. It said I should try different cable, or USB port, but no luck with either, and now it says my phone is not supported.
I tried to enter recovery, but I only get CM guy and it's stuck, even when I turn off the phone, it turns itself on automatically, and to fully turn it off I need to enter fastboot mode, and then turn off. I tried flashing full stock image (I know how to do that, and I have previous experience on this phone), but my fastboot crashes (Fastboot.exe Has stoped Working), tried to download fastboot again, but nothing helped. I also tried to flash recovery only, and I get the same thing... Also tried to do that with custom recovery, but nothing....
Is there something I can do, or do I need a new phone?
Also, I had like 70% battery when I started, so I am afraid to keep trying, cause if I go out of juice, it's game over, right?
Looks more like issues with your pc communicating with your device, which might have causes other side effects due to that. But I have not tried CM Installer yet.
You should see about getting fastboot working correctly first and getting the right adb/fastboot driver (such as latest Universal Naked Driver, link in my sig). You should also use the latest adb/fastboot .exe from Google, download their latest ADT package. If it still crash, use it on a different machine, if you're on Windows 8 try Windows 7 or Ubuntu.
Also make sure the factory image isn't corrupt, I always have issues downloading it from Google.
Also, I had like 70% battery when I started, so I am afraid to keep trying, cause if I go out of juice, it's game over, right?
Click to expand...
Click to collapse
If the battery goes to 0%, just charge it, do you think everyone throw away their N4 when the battery goes to 0? There is the red light problem, but its an easy fix.
Thanks for answering, I fixed it with a strange method (to me). On CM forum j_cor told me this:
"Your device appears to be stuck in sideload. So the good news is no, you are not bricked. Here is what I would try to do:
1. Boot the device - wait for the "stuck" CM guy to display
2. Plug phone to PC and open a command prompt to the directory to C:\Users\enter_your_name\cminstaller\bundle\win32
3. from the prompt "C:\Users\enter_your_name\cminstaller\bundle\win32>" type "adb.exe sideload ClockwordMod.cer" (no quotes) and hit enter
4. This will try and sideload this .cer file and will fail - but it should kick you out to the main recovery screen. Select the Reboot option from Recovery
5. Device should boot back up. It will most likely still be the stock ROM. My guess would be that something disrupted the sideload process when installing the system.zip with CM."
However, this did not fix my problem, but it got my phone to communicate with fastboot. So I was able to flash custom recovery, and do a factory reset, which brought me to the stock ROM, I flashed CM the old-fashioned way then.....
And my PHONE IS UP AND WORKING AGAIN!!!
The main problem in communication was that phone blocked every time I booted into fastboot, and plugged USB cable in.... It immediately became unresponsive to any commands, after I did this, phone wasn't getting stuck in fastboot, so that solved my issue.
A bit of an SOS situation if anyone knows the right steps please
Well, I restored a Titanium Backup and mistakenly toggled the "restore system apk". It ran fine, all restored and then when I rebooted got stuck.
By "stuck", it re-boots constantly. It shows the LG animation, then all I can see is two messages before it starts booting again:
1) "Unfortunately, Google Play Services Has Stopped"
2) "Unfortunately, System UI has stopped
... and then it does the entire boot sequence, animation, again, and again.
Here is what I can do:
* It is in USB debug mode.
* I have drivers on laptop
* I am able to connect with adb and also shell into phone.
* With adb, I have output to the file an "adb bugreport" as well as an "adb logcat".
* I have several backups:
a) The modemsst1.img and modemsst2.img created by Titanium Backup
b) Titanium backups (full apps and data)
c) an "adb backup - all" backup
* I managed to get it into firmware update mode by pressing the volume up button and the power button and then when it flashed red a few times, just the up button. So, I can get it into Firmware update mode.
Of course, I have never really used adb before, except to dabble a bit. So, I am encouraged that I can somehow get into with shell.
I am not unplugging it until I know what to do!
Since then I have been able to turn the phone off and also put it into charging on USB.
This is what worked:
* Hold down power and volume down button until booting stops and phone turns off completely.
When it does shut down, I kept buttons down until it flashes logo again and then shuts down again. Then I let go. Phone is off and when I plugged in the charger it shows charging animation.
Now, after inspecting the bugreport, I noticed a lot of these messages for all the system apps like this one:
"I/PackageManager(21318): Expecting better updatd system app for com.lge.sizech"
I think the cause of all this shralp is this, I did a LG Mobile Support Tool "Upgrade Recovery" and then in Titanium Backup I restored an older backup (incl system apks). At least that makes sense seeing all the "Expecting better apdat system app" messages in the bugreport.
Still not sure what to do next
I tried the very good instructions here:
[Guide] Unroot/Unbrick - flash official factory firmware with LG Launche
http://forum.xda-developers.com/showthread.php?t=2471370
The update succeeded. However, when I rebooted the phone it is in the same boot-loop with message that it was before.
I used the BELL D803B10D_00.kdz file. Now I will try with the earlier version BELL D803BA_00.kdz file.
We will see what happens ...
do you have nandroid backup from previous rom?
I have three backups:
1) Titanium Backup (full)
* This was my first backup performed right after rooting device and installing Titanium Backup.
2) Titanium Backup (full)
* Did this 2 days ago. Device was working OK and did as precaution.
3) ADB BACKUP. I did this one before my Titanium restore.
I restored the first titanium backup and that (ooooppps!) was after I did an LG Firmware update.
ALSO:
I am on Windows 7 64 and although adb works fine, fastboot does not. I understand that might be a problem with windows 7 64.
So, unless anyone objects, I am going to redo on my windows 32 machine and also "fastbook oem unlock".
Since firmware is OK, if I do the fastboot oem unlock, that will wipe everything. But I can still boot and re-setip the phone, right?
Just checking before I fudge everything up here ..
ALSO ALSO:
I had antivirus/theft security installed and I disabled it partway through last restore.
Maybe that has somethng to do with this all .
But I am still cool because I can ADB and also firmware install seems ok.
ADB works and that is the one good sign.
or you can follow ADB Sideload method
http://forum.xda-developers.com/showthread.php?t=2318497
zekurosu said:
or you can follow ADB Sideload method
http://forum.xda-developers.com/showthread.php?t=2318497
Click to expand...
Click to collapse
I don't (didn't) have TWRP installed. How can I sideload without it?
Also, should I adb oem unlock to get it wiped at this point?
I'm having a similar problem on a Bell D803. Just happened very randomly today. I turned my phone off for an exam, then turned it back on after.. initially had no signal and a black background. Settings for factory reset wouldn't work. My phone is rooted and has TWRP. I went into recovery and formatted.
Bootloop.
Bootloop.
Bootloop x 20.
I however, don't get the same two messages. I just keep bootlooping.
Got home, tried to go through download mode to unbrick it, but for some reason my computer isn't picking it up. I have all the drivers, and before this incident, it was recognized.
Any solutions?
I'm thinking of buying an OTG USB and then just flashing a stock zip from recovery. Would that be a possible viable solution?
asdfvtn said:
I'm having a similar problem on a Bell D803. Just happened very randomly today. I turned my phone off for an exam, then turned it back on after.. initially had no signal and a black background. Settings for factory reset wouldn't work. My phone is rooted and has TWRP. I went into recovery and formatted.
Bootloop.
Bootloop.
Bootloop x 20.
I however, don't get the same two messages. I just keep bootlooping.
Got home, tried to go through download mode to unbrick it, but for some reason my computer isn't picking it up. I have all the drivers, and before this incident, it was recognized.
Any solutions?
I'm thinking of buying an OTG USB and then just flashing a stock zip from recovery. Would that be a possible viable solution?
Click to expand...
Click to collapse
Well, I am able to connect with adb fine on my laptop (Win 7 64) but not on my desktop (Win 7 32)
But on my Win 7 64 I cannot get into fastboot.
I am wondering if the driver install on my desktop went foo-bar and needs reinstall. Also, I noticed that the website drivers are more recent USB drivers than some of the ones linked on this site.
I used adb uninstall package for many user packages and it was success. But I still see the packages listed in the bugreport?
For example: I already uninstalled "com.benhirashima.skiplock" and also "com.lookout".
Why? What to do to really zap them for good?
Sorry, I posted the wrong link earlier.
This was the guide I used which succeeded but made no difference to the boot-loop.
LG G2 Stock Firmware (Go Back to Stock)
http://forum.xda-developers.com/showthread.php?t=2432476&highlight=d803
Just figured out how to do a factory reset.
http://www.youtube.com/watch?v=3ogBvzbPikc
The hard reset worked and now I am configuring the phone settings!
So, again, this is what I did:
1) http://forum.xda-developers.com/showthread.php?p=45293512
2) http://www.youtube.com/watch?v=3ogBvzbPikc
Not sure if it all worked but I am setting the phone up as we speak (or as I type)
natureburger said:
Well, I am able to connect with adb fine on my laptop (Win 7 64) but not on my desktop (Win 7 32)
But on my Win 7 64 I cannot get into fastboot.
I am wondering if the driver install on my desktop went foo-bar and needs reinstall. Also, I noticed that the website drivers are more recent USB drivers than some of the ones linked on this site.
Click to expand...
Click to collapse
Hmm that's strange. Unfortunately for me, I'm already on 64-bit and it still isn't picking it up.
ALL FIXED UP
WORKING 110%
:good:
natureburger said:
ALL FIXED UP
WORKING 110%
:good:
Click to expand...
Click to collapse
I have followed this to a t.
Succesfully flashed the stock firmware that came with the phone when sold.
Did hard reset using the the power button and volume down
= phone rebooting every 10 seconds, no wifi, imei = null
adb devices = offline.
Really depressed right now. If anybody can help me I would appreciate it.
zprovo said:
I have followed this to a t.
Succesfully flashed the stock firmware that came with the phone when sold.
Did hard reset using the the power button and volume down
= phone rebooting every 10 seconds, no wifi, imei = null
adb devices = offline.
Really depressed right now. If anybody can help me I would appreciate it.
Click to expand...
Click to collapse
Press the power button down and hold it.
It should turn off, then look like it is turning on, (flash logo very briefly) and then turn off.
Let go of power button and it should stay off.
Do that. Now, does it work to turn off completely?
Let's see if you can do that first.
Then .. do hard reset, exactly like this:
http://www.youtube.com/watch?v=3ogBvzbPikc
Does the hard reset screen show and give you hard reset options?
natureburger said:
Press the power button down and hold it.
It should turn off, then look like it is turning on, (flash logo very briefly) and then turn off.
Let go of power button and it should stay off.
Do that. Now, does it work to turn off completely?
Let's see if you can do that first.
Click to expand...
Click to collapse
Yup. I totally understand what you are saying and have done it many times. I had to use that method to get into download mode and also had to use it to do hard reset.
I just reflashed the phone all over again a second time succesfully.
Reboots every 5 seconds. Keyboard came up for a few seconds for the first time in 48 hours during the initial setup phase. 5 seconds later as I was trying to input a wifi code it would not appear. then it rebooted as usual.
I really appreciate any input right now. :cyclops::crying:
zprovo said:
Yup. I totally understand what you are saying and have done it many times. I had to use that method to get into download mode and also had to use it to do hard reset.
I just reflashed the phone all over again a second time succesfully.
Reboots every 5 seconds. Keyboard came up for a few seconds for the first time in 48 hours during the initial setup phase. 5 seconds later as I was trying to input a wifi code it would not appear. then it rebooted as usual.
I really appreciate any input right now. :cyclops::crying:
Click to expand...
Click to collapse
1) Are you able to completely turn it off using my instructions?
2) When you hard reset (2nd half of this video), http://www.youtube.com/watch?v=3ogBvzbPikc
a) Does the hard reset screen show?
b) Does it give you the hard reset options?
3) Before it was bricked, was it in 'usb debug mode' in developer options?
4) Which kpz version did you restore to?
5) Did your "adb devices" ever work? Did your "adb shell" ever work?
natureburger said:
1) Are you able to completely turn it off using my instructions?
2) When you hard reset (2nd half of this video), http://www.youtube.com/watch?v=3ogBvzbPikc
a) Does the hard reset screen show?
b) Does it give you the hard reset options?
3) Before it was bricked, was it in 'usb debug mode' in developer options?
Click to expand...
Click to collapse
1) Yes absolutely. It is sitting next to me right now doing nothing at all because I turn it off when I am not trying to fix it, otherwise it keeps rebooting relentlessly.
2) a) Yes, same as the video. b) Yes it says the same exact thing as the video. I press power key twice and it begins. The stock recovery android appears with a loading bar on the bottom for ~1 minute then it goes to the boot "lg animation".
3) Yes it was. Before it was bricked I essentially always had it in debug mode because I successfully rooted it and simply left it on debugging mode after having to activate it to root.
4) D801V11B_00.kdz The EXACT same as the original. This is a Videotron (canadian) phone. I can clearly remember without a doubt going into about phone and this is what it was running before all of this happened.
5) I am having a bit of memory strain here, but I do believe it also said adb devices before any of the issues came. It is a good point I will try "adb device" from another trusted computer.
Other notes: I can browse the android os for a few seconds. Sometimes sound does not work, wifi is non functional (even though the keyboard never appears, I managed to have a security free wifi in my proximity and it would not connect (was saying: temporarily avoiding bad signal)) and also I do have modemstat1.img and modemstat2.img backups for EFS.
adb devices consistently shows "offline" but it is definitely recognizing the phone. I have also tried using usb debugging activated and still "offline". Drivers are up to date and all.
The upper drawer in the usual g2 user interface is strange now. it doesnt have anything except for the date (1970 something...) and a "gear" icon for system settings. I am talking the drawer you drag down from the top of the screen.
This phone was working with absolutely no problems 2 days ago.
Thank you so much for looking into this. I have certainly exhausted my repairing capacities. I am entirely dependent upon the knowledgeable individuals in here from here on out.
zprovo said:
1) Yes absolutely. It is sitting next to me right now doing nothing at all because I turn it off when I am not trying to fix it, otherwise it keeps rebooting relentlessly.
2) a) Yes, same as the video. b) Yes it says the same exact thing as the video. I press power key twice and it begins. The stock recovery android appears with a loading bar on the bottom for ~1 minute then it goes to the boot "lg animation".
3) Yes it was. Before it was bricked I essentially always had it in debug mode because I successfully rooted it and simply left it on debugging mode after having to activate it to root.
4) D801V11B_00.kdz The EXACT same as the original. This is a Videotron (canadian) phone. I can clearly remember without a doubt going into about phone and this is what it was running before all of this happened.
5) I am having a bit of memory strain here, but I do believe it also said adb devices before any of the issues came. It is a good point I will try "adb device" from another trusted computer.
Other notes: I can browse the android os for a few seconds. Sometimes sound does not work, wifi is non functional (even though the keyboard never appears, I managed to have a security free wifi in my proximity and it would not connect (was saying: temporarily avoiding bad signal)) and also I do have modemstat1.img and modemstat2.img backups for EFS.
adb devices consistently shows "offline" but it is definitely recognizing the phone. I have also tried using usb debugging activated and still "offline". Drivers are up to date and all.
The upper drawer in the usual g2 user interface is strange now. it doesnt have anything except for the date (1970 something...) and a "gear" icon for system settings. I am talking the drawer you drag down from the top of the screen.
This phone was working with absolutely no problems 2 days ago.
Thank you so much for looking into this. I have certainly exhausted my repairing capacities. I am entirely dependent upon the knowledgeable individuals in here from here on out.
Click to expand...
Click to collapse
Hmmmm..... why your adb devices is not working? But the re-pair works and you can then do hard reset.
But that is good information you shared.
Maybe someone else can chime in.
From my experience:
1) adb usb access seems spotty. My win 7 64 connected fine and it even kept the shell through the reboot cycle. But on my win 7 32 machine it was only detecting device and then not able to shell.
2) I was also able to use from the LG website LG MOBILE SUPPORT TOOLS.
Download the LG MOBILE SUPPORT TOOL
I downloaded the most recent one from the LG website and make sure to select your options >> country and then the correct phone model at the upper right hand corner of the tool.
Then install USB driver for correct phone model.
Then see if USB works, "adb device" should return the device code.
"adb shell" should show the shell prompt.
3) There is always fastboot. But I an noob and know 0% about how to properly connect and use it.
Some others please chime in and help this droid bro!
Hi,
Messed up badly Furious that ZTE made the phone incompatible with Daydream, decided to root the device. Tried various ROMs, but could never get the modem to work in the UK. Eventually tried to reinstall Chinese stock ROM and, to my surprise, the modem still didn't work. Attempted to restore the modem files from TWRP backup and bricked the phone completely. Can only boot into Chinese recovery where only ADB sideload enables the phone to be seen by Windows as Android ADB Interface. EDL mode cannot be seen and Axon7toolkit cannot see the phone even in ADB sideload mode. Attempts to update software result in this message: Package expects build fingerprint of ZTE/P996A03/ailsa_ii:6.0.1/MMB29M/20161027.021856:user/release-keys or ZTE/P996A03/ailsa_ii:7.1.1/NMF26F/20170224.135053:user/release-keys ; this device has ZTE/P996A03/ailsa_ii:7.1.1/NMF26V/20170912.013327:user/release-keys. Most likely, updates won't work anyway, because when the phone was running, updates resulted in a mismatch. Any feedback would be much appreciated.
tretayuga said:
Hi,
Messed up badly Furious that ZTE made the phone incompatible with Daydream, decided to root the device. Tried various ROMs, but could never get the modem to work in the UK. Eventually tried to reinstall Chinese stock ROM and, to my surprise, the modem still didn't work. Attempted to restore the modem files from TWRP backup and bricked the phone completely. Can only boot into Chinese recovery where only ADB sideload enables the phone to be seen by Windows as Android ADB Interface. EDL mode cannot be seen and Axon7toolkit cannot see the phone even in ADB sideload mode. Attempts to update software result in this message: Package expects build fingerprint of ZTE/P996A03/ailsa_ii:6.0.1/MMB29M/20161027.021856:user/release-keys or ZTE/P996A03/ailsa_ii:7.1.1/NMF26F/20170224.135053:user/release-keys ; this device has ZTE/P996A03/ailsa_ii:7.1.1/NMF26V/20170912.013327:user/release-keys. Most likely, updates won't work anyway, because when the phone was running, updates resulted in a mismatch. Any feedback would be much appreciated.
Click to expand...
Click to collapse
You messed up real bad. I assume you forgot to flash the modem files when you flashed the custom ROMs?
EDL mode cannot be seen? What do you mean by that? Keep the Device Manager open, phone disconnected; then hold both volume buttons, wait 5 seconds, connect the USB cable while you are holding them, and wait 3 seconds more before releasing them. The device manager should refresh.
The phone should appear under Ports (COM & LPT) or under USB devices as QUSB_BULK. If it is under USB devices you have to right click on it, Uninstall -> Delete driver software. After that hold all 3 buttons for a long time (both volume buttons and power) and device manager should refresh itself. It should install the Qualcomm driver then. If the driver is ZTE handset diagnostic interface, you'll have to disassemble the phone
Choose an username... said:
You messed up real bad. I assume you forgot to flash the modem files when you flashed the custom ROMs?
EDL mode cannot be seen? What do you mean by that? Keep the Device Manager open, phone disconnected; then hold both volume buttons, wait 5 seconds, connect the USB cable while you are holding them, and wait 3 seconds more before releasing them. The device manager should refresh.
The phone should appear under Ports (COM & LPT) or under USB devices as QUSB_BULK. If it is under USB devices you have to right click on it, Uninstall -> Delete driver software. After that hold all 3 buttons for a long time (both volume buttons and power) and device manager should refresh itself. It should install the Qualcomm driver then. If the driver is ZTE handset diagnostic interface, you'll have to disassemble the phone
Click to expand...
Click to collapse
Thanks. The phone is listed as ZTE Handset Diagnostic Interface(DFU) (COM10) in Ports. It is listed as Unknown USB Device in USB Controllers and following the procedure you described doesn't install the Qualcomm driver. I take it, then, that an engineer would have to disassemble the phone.
tretayuga said:
Thanks. The phone is listed as ZTE Handset Diagnostic Interface(DFU) (COM10) in Ports. It is listed as Unknown USB Device in USB Controllers and following the procedure you described doesn't install the Qualcomm driver. I take it, then, that an engineer would have to disassemble the phone.
Click to expand...
Click to collapse
Or you. Follow the 4th category brick repair manual. I'm just rewriting it but it'll take time
Where are you getting adb sideload from?
Choose an username... said:
Or you. Follow the 4th category brick repair manual. I'm just rewriting it but it'll take time
Where are you getting adb sideload from?
Click to expand...
Click to collapse
Well, with your help I may snatch victory from the jaws of defeat. I'll ask one of the local engineers to dismantle the phone according to your guide and we'll see what we can do. The adb sideload screen is in this photo.
Thanks again.
tretayuga said:
Well, with your help I may snatch victory from the jaws of defeat. I'll ask one of the local engineers to dismantle the phone according to your guide and we'll see what we can do. The adb sideload screen is in this photo.
Thanks again.
Click to expand...
Click to collapse
You still have one other option though. May save you.
Do you have an SD card? If not, get at least a 4 GB one (or one with 3gb free), download an official A2017 update package, unzip it and put the update.zip in the sd card. (If you get a bunch of folders instead of a file called update.zip just take the original zip and put it in the SD).
after that, put it in the sd card and select the option that says 'sd'.
It may work. Right now it's your best shot at not taking it apart
Choose an username... said:
You still have one other option though. May save you.
Do you have an SD card? If not, get at least a 4 GB one (or one with 3gb free), download an official A2017 update package, unzip it and put the update.zip in the sd card. (If you get a bunch of folders instead of a file called update.zip just take the original zip and put it in the SD).
after that, put it in the sd card and select the option that says 'sd'.
It may work. Right now it's your best shot at not taking it apart
Click to expand...
Click to collapse
That's forbidden. When I've tried to update from the SD card using that option, I get a message saying I don't have permission to update from the SD card. I will, however, try again because you've mentioned some things that are slight variations on what I've done before.
tretayuga said:
That's forbidden. When I've tried to update from the SD card using that option, I get a message saying I don't have permission to update from the SD card. I will, however, try again because you've mentioned some things that are slight variations on what I've done before.
Click to expand...
Click to collapse
Yeah, it's possible. But I have one more idea. Can you try one other thing?
There's a way to get to EDL if you have only DFU mode, which is by getting adb (not adb sideload, just normal adb) and issuing "adb reboot edl". If you can get adb (i think you may have adb from the main recovery screen) then you can get to EDL and flash stuff with MiFlash. Try to issue 'adb reboot edl' when you are on the main screen of the recovery mode.
The other way, which might work on your state, is turning the phone off and holding volume down + power. It might open FTM mode (it's a white rectangle in the middle of the screen with the words FTM written on it, can't miss it). If you get there just issue 'adb reboot edl' and flash with MiFlash
Choose an username... said:
Yeah, it's possible. But I have one more idea. Can you try one other thing?
There's a way to get to EDL if you have only DFU mode, which is by getting adb (not adb sideload, just normal adb) and issuing "adb reboot edl". If you can get adb (i think you may have adb from the main recovery screen) then you can get to EDL and flash stuff with MiFlash. Try to issue 'adb reboot edl' when you are on the main screen of the recovery mode.
The other way, which might work on your state, is turning the phone off and holding volume down + power. It might open FTM mode (it's a white rectangle in the middle of the screen with the words FTM written on it, can't miss it). If you get there just issue 'adb reboot edl' and flash with MiFlash
Click to expand...
Click to collapse
Thanks, but I've already tried it. The phone only communicates with the computer in adb sideload mode, so trying adb reboot edl results in an "error:closed" message. If not in sideload mode, adb cannot even register a device. Occasionally, I've seen a small Linux penguin in the middle of the screen and today it hung on the MiFavor logo for some time. If those are significant, I don't know how to get them back. The ZTE engineers have been very thorough. It's frustratiing because the adb sideload thing might work with the right software package, and I can clear the cache and wipe the system; but then I'm back to square one. Your suggestion about dismantling the phone sounds like the most promising path forward and I will have a go tomorrow.
tretayuga said:
Thanks, but I've already tried it. The phone only communicates with the computer in adb sideload mode, so trying adb reboot edl results in an "error:closed" message. If not in sideload mode, adb cannot even register a device. Occasionally, I've seen a small Linux penguin in the middle of the screen and today it hung on the MiFavor logo for some time. If those are significant, I don't know how to get them back. The ZTE engineers have been very thorough. It's frustratiing because the adb sideload thing might work with the right software package, and I can clear the cache and wipe the system; but then I'm back to square one. Your suggestion about dismantling the phone sounds like the most promising path forward and I will have a go tomorrow.
Click to expand...
Click to collapse
So you get the 5 seconds screen? Have you tried to enter fastboot?
If I'm right, you get the Linux penguin when you hit the power button when you are on the 5 seconds screen (the 'Your device can't be checked for corruption' screen). If it appears, use a volume button to get to the options, select 'Bootloader' and try to enter Bootloader mode. It should have fastboot, being an A2017.
If you get to fastboot you can issue 'fastboot boot twrp.img' and your phone will boot into TWRP. Take Lineage, the Universal Bootloader and the A2017 modem and flash them, then format data, and you'll be good to go.
Choose an username... said:
So you get the 5 seconds screen? Have you tried to enter fastboot?
If I'm right, you get the Linux penguin when you hit the power button when you are on the 5 seconds screen (the 'Your device can't be checked for corruption' screen). If it appears, use a volume button to get to the options, select 'Bootloader' and try to enter Bootloader mode. It should have fastboot, being an A2017.
If you get to fastboot you can issue 'fastboot boot twrp.img' and your phone will boot into TWRP. Take Lineage, the Universal Bootloader and the A2017 modem and flash them, then format data, and you'll be good to go.
Click to expand...
Click to collapse
I do indeed get the 5 seconds screen, but the reason I didn't mention it is that it does nothing from what I can see. The phone "boots" after five seconds, but if I press the volume buttons to enter options, Bootloader is not one of them. The Fastboot option just makes the phone reboot and the Recovery option sends me to the screen in the photo upthread. Like I say, they've been very thorough.
Choose an username... said:
So you get the 5 seconds screen? Have you tried to enter fastboot?
If I'm right, you get the Linux penguin when you hit the power button when you are on the 5 seconds screen (the 'Your device can't be checked for corruption' screen). If it appears, use a volume button to get to the options, select 'Bootloader' and try to enter Bootloader mode. It should have fastboot, being an A2017.
If you get to fastboot you can issue 'fastboot boot twrp.img' and your phone will boot into TWRP. Take Lineage, the Universal Bootloader and the A2017 modem and flash them, then format data, and you'll be good to go.
Click to expand...
Click to collapse
Curioser and curioser. I went through the steps to short circuit the test point on the motherboard and MiFlash successfully flashed the Unbrick ROM which you advised. Obviously, the Qualcomm drivers were recognised e.t.c. The state of the phone now is that it is caught in a boot loop. It shows the ZTE screen and the 5-second screen. Going into recovery on the 5-second screen causes the ZTE logo to appear again, then the battery icon keeps showing, switching off and showing again. The Fastboot mode on the 5-second screen now takes me to the Fastboot screen, but entering recovery causes the same battery loop. Did I make a mistake reassembling the phone perhaps? Should I try to flash a different ROM from the test point?
tretayuga said:
Curioser and curioser. I went through the steps to short circuit the test point on the motherboard and MiFlash successfully flashed the Unbrick ROM which you advised. Obviously, the Qualcomm drivers were recognised e.t.c. The state of the phone now is that it is caught in a boot loop. It shows the ZTE screen and the 5-second screen. Going into recovery on the 5-second screen causes the ZTE logo to appear again, then the battery icon keeps showing, switching off and showing again. The Fastboot mode on the 5-second screen now takes me to the Fastboot screen, but entering recovery causes the same battery loop. Did I make a mistake reassembling the phone perhaps? Should I try to flash a different ROM from the test point?
Click to expand...
Click to collapse
So now you have fastboot? Put the TWRP-3.2.1-0.img on the adb folder, then open CMD, navigate to that folder, write 'fastboot boot TW" and press Tab, the filename should appear, if it does hit Enter
If you get to TWRP don't turn the phone off, and flash the universal bootloader, Lineage, the A2017 modem, and Magisk 15.2
Choose an username... said:
So now you have fastboot? Put the TWRP-3.2.1-0.img on the adb folder, then open CMD, navigate to that folder, write 'fastboot boot TW" and press Tab, the filename should appear, if it does hit Enter
If you get to TWRP don't turn the phone off, and flash the universal bootloader, Lineage, the A2017 modem, and Magisk 15.2
Click to expand...
Click to collapse
Sorry, I didn't make that clear. The 5-second screen directs me to Fastboot, but there are only four options there: Start (doesn't work, obviously), Restart Bootloader (brings you back to the same place), Shut down and Recovery (goes to battery icon). Don't know what went wrong--maybe a connection got damaged when the phone was dismantled--but I discover I can't repeat the short circuiting thing and, even though the phone is seen on the system as Qualcomm 90.., MiFlash cannot flash anything different. I despair. I'll send the phone for recycling. Making the Axon 7 incompatible with Daydream was the last straw. I very much appreciate your help just the same.
tretayuga said:
Sorry, I didn't make that clear. The 5-second screen directs me to Fastboot, but there are only four options there: Start (doesn't work, obviously), Restart Bootloader (brings you back to the same place), Shut down and Recovery (goes to battery icon). Don't know what went wrong--maybe a connection got damaged when the phone was dismantled--but I discover I can't repeat the short circuiting thing and, even though the phone is seen on the system as Qualcomm 90.., MiFlash cannot flash anything different. I despair. I'll send the phone for recycling. Making the Axon 7 incompatible with Daydream was the last straw. I very much appreciate your help just the same.
Click to expand...
Click to collapse
No, when you are on the screen with the 4 options you have Fastboot. That is the bootloader mode. Get there and issue 'fastboot devices' and you'll see that you got fastboot from there.
Don't repeat the 4th category manual, just turn the phone off and hold volume up and down, then connect the USB. If it appears as Qualcomm HS-USB QDLoader 9008 you're in EDL.
What's the name of the package that you flashed?
Choose an username... said:
No, when you are on the screen with the 4 options you have Fastboot. That is the bootloader mode. Get there and issue 'fastboot devices' and you'll see that you got fastboot from there.
Don't repeat the 4th category manual, just turn the phone off and hold volume up and down, then connect the USB. If it appears as Qualcomm HS-USB QDLoader 9008 you're in EDL.
What's the name of the package that you flashed?
Click to expand...
Click to collapse
You star! I've followed your advice and now it is exactly the phone I was looking for. (I had made a mistake and forgotten to reconnect something in the internals, but the ROM worked just fine once that was sorted and I've flashed all the things you recommended.) Your name will be sung down the ages in my household, Choose an username. Many thanks
Not sure how to title this forum post, but this is the best I got. Forgive my ignorance and lack of knowledge on these topics.
I was trying to root my Axon 7 mini. After some searching to find out how to unlock the bootloader (like needing JDK, older Android SDK version to run android.bat, etc.), I finally got it to work. Ran Recovery to "apply update from SD Card" (can not remember the file right now) and was then ready to load TWRP Recovery. When I rebooted to the recovery TWRP image, it told me something failed and the phone had to be factory reset. I took my SD card out in fear of my data being deleted and "accidentally" clicked the power button. It then reloaded with a password prompt where I typed some random password (1234 because I never set a pin password nor knew what to do here), clicked submit, and then gave me some error; now my phone doesn't work.
The Problem:
- I can enter bootloader, sometimes, but can only run fastboot commands; adb device does not detect phone so can't run adb commands (always says the server is old or something and reloads daemon successfully but never finds my device regardless). Also, I don't think I can get it to run in EDL mode; MiFlash gives out errors too when trying to flash recovery images.
- Recovery mode doesn't appear or work; not sure if the MiFavor command prompts on the phone is recovery or not, but it's safe to say this no longer appears. This is also where I believe the phone bootloops. I can get the fastboot commands to flash a TWRP recovery, but it never actually enters the TWRP dashboard.
- Can not turn off the phone... I think. None of the command options that appear on-phone shut it off; however, when the screen does stay black, I'm not sure if it's in EDL mode or plainly off.
- Device Manager shows the phone as different stuff (namely Kedacom USB Device and Portable Devices/MTB USB Device). Sometimes Qualcomm appears, but it depends. More often than not, when my device does appear, there's either an error code (like Code 10, Code 43) and/or the device is grayed out.
Conclusion:
I just want to get my phone to work normally again, if possible. Currently, I locked the oem to see if fastboot commands could still work and now I'm stuck at the ZTE logo, so can't try to unlock it right now. What are the proper tools, drivers, programs, etc I need to get this phone back to normal? I've scoured the web and these forums for 2 days now with no luck and lots of either missing info or obscure info.
I bought this at Best Buy, so I'm assuming it's US Axon7 Mini version in terms of drivers (not sure if the box specifies any info that could be useful here).
Un-brick Axon 7 Mini
Dear all,
I experienced the same issue with my phone after I tried to flash it with custom ROMs and recovery.
I thought I lost it as I was not able to enter adb mode (not recognized on the PC) or even not able to enter EDL mode with the button combination so not able to do anything with it.
Only watch it boot and display the ZTE logo.
After some research, here is what I had to do to get it recovered.
First thing you need to get is an EDL cable.
I let you search on your favorite site. Mine was a Generic eDL Deep Flash Qualcomm 9008 Cable 2 in 1 for Z3 X/Octopus.
Until you receive it, make sure you have the latest Qualcomm drivers installed on your PC.
You can find it easily.
Then, connect your phone and your PC with the EDL cable.
Press the button on your EDL cable (there should be one) for a few seconds and keep it pressed.
Then, press the power button and keep it pressed for at least 20 seconds.
At this stage, you should have both buttons pressed and after some time, you should feel the phone rebooting.
After 20 seconds, release the power button.
Then, after 10 other seconds, release the EDL cable button.
At this stage, your phone screen should stay black and your phone should appear in the device manager as Qualcomm USBHUB (or somehting similar)
You are in EDL mode and should be able to perform a recovery flashing using tuliptool.
Then I followed the steps I found here:
https://forum.xda-developers.com/axon-7-mini/how-to/updating-uk-version-zte-axon-7-mini-to-t3717933
If you are still stuck, pm me.
Be patient, all will be fine,
mariegalante55 said:
Dear all,
I experienced the same issue with my phone after I tried to flash it with custom ROMs and recovery.
I thought I lost it as I was not able to enter adb mode (not recognized on the PC) or even not able to enter EDL mode with the button combination so not able to do anything with it.
Only watch it boot and display the ZTE logo.
After some research, here is what I had to do to get it recovered.
First thing you need to get is an EDL cable.
I let you search on your favorite site. Mine was a Generic eDL Deep Flash Qualcomm 9008 Cable 2 in 1 for Z3 X/Octopus.
Until you receive it, make sure you have the latest Qualcomm drivers installed on your PC.
You can find it easily.
Then, connect your phone and your PC with the EDL cable.
Press the button on your EDL cable (there should be one) for a few seconds and keep it pressed.
Then, press the power button and keep it pressed for at least 20 seconds.
At this stage, you should have both buttons pressed and after some time, you should feel the phone rebooting.
After 20 seconds, release the power button.
Then, after 10 other seconds, release the EDL cable button.
At this stage, your phone screen should stay black and your phone should appear in the device manager as Qualcomm USBHUB (or somehting similar)
You are in EDL mode and should be able to perform a recovery flashing using tuliptool.
Then I followed the steps I found here:
https://forum.xda-developers.com/axon-7-mini/how-to/updating-uk-version-zte-axon-7-mini-to-t3717933
If you are still stuck, pm me.
Be patient, all will be fine,
Click to expand...
Click to collapse
I had a feeling an EDL cable was my only option left given everything I've looked up and the multiple methods I've tried. Wanted to avoid spending money on one but doesn't look like I have a choice given the circumstances - oh well. Regardless, thank you for the response and advice. Have to wait a while, though, to get the cable and test to see if this works.
If anyone else ever ends up in the same royally screwed situation as me, getting an EDL cable - or DIY one if you wanna be cheap and are confident enough to do so - is probably your saving grace.
Kuma21 said:
I had a feeling an EDL cable was my only option left given everything I've looked up and the multiple methods I've tried. Wanted to avoid spending money on one but doesn't look like I have a choice given the circumstances - oh well. Regardless, thank you for the response and advice. Have to wait a while, though, to get the cable and test to see if this works.
If anyone else ever ends up in the same royally screwed situation as me, getting an EDL cable - or DIY one if you wanna be cheap and are confident enough to do so - is probably your saving grace.
Click to expand...
Click to collapse
K, I can get tuliptool to work and run command, but i keep getting a "Failed: Unkown Error" response everytime i run a command. Can't unlock my bootloader, nor write a recovery disk due to this error. does anyone have any idea why this happens?