Related
So tonight my phone randomly froze and restarted itself, and is now perpetually stuck on the black screen with the white Google text. Every so often it restarts itself back to that point and stops. I was running Nougat from the beta program workaround.
I have done tons of research and am at a loss. So far I have:
-Booted into fastboot mode and attempted Recovery Mode. I can navigate using the volume keys until Recovery Mode shows up in red, but when I hit the Power button to select it the phone immediately boots back to the normal Google logo loop.
-Tried to flash a stock image via command line, no luck because of bootloader I think.
I might not be using all the right terminology, but it seems to me that I am stuck because I never enabled USB Debugging or Unlocked my Bootloader while the phone was working?
-If I go to CMD and type 'ADB devices' I just get a message saying "List of devices attached" and nothing else.
-If I type 'Fastboot Devices' then my phones serial number appears and it says fastboot next to it.
-If I type 'fastboot flashing unlock' it says "FAILED (remote: oem unlock is not allowed)
Does anyone have any ideas on how to fix this and get my phone working again?
Thanks in advance!
Galrash said:
So tonight my phone randomly froze and restarted itself, and is now perpetually stuck on the black screen with the white Google text. Every so often it restarts itself back to that point and stops. I was running Nougat from the beta program workaround.
I have done tons of research and am at a loss. So far I have:
-Booted into fastboot mode and attempted Recovery Mode. I can navigate using the volume keys until Recovery Mode shows up in red, but when I hit the Power button to select it the phone immediately boots back to the normal Google logo loop.
-Tried to flash a stock image via command line, no luck because of bootloader I think.
I might not be using all the right terminology, but it seems to me that I am stuck because I never enabled USB Debugging or Unlocked my Bootloader while the phone was working?
-If I go to CMD and type 'ADB devices' I just get a message saying "List of devices attached" and nothing else.
-If I type 'Fastboot Devices' then my phones serial number appears and it says fastboot next to it.
-If I type 'fastboot flashing unlock' it says "FAILED (remote: oem unlock is not allowed)
Does anyone have any ideas on how to fix this and get my phone working again?
Thanks in advance!
Click to expand...
Click to collapse
Lesson #1: always keep your bootloader unlocked.
Don't bother trying any fastboot commands, they will never work because your bootloader is locked. Don't bother trying any adb commands either, they won't work in fastboot/bootloader mode (they only work while booted into Android and in recovery). I hate to say it but you're basically screwed. With no access to fastboot, no access to recovery, and no access to there's literally zero you can do. This should be covered under warranty, though. When you say the Nougat "beta program workaround" what exactly do you mean?
Heisenberg said:
Lesson #1: always keep your bootloader unlocked.
Don't bother trying any fastboot commands, they will never work because your bootloader is locked. Don't bother trying any adb commands either, they won't work in fastboot/bootloader mode (they only work while booted into Android and in recovery). I hate to say it but you're basically screwed. With no access to fastboot, no access to recovery, and no access to there's literally zero you can do. This should be covered under warranty, though. When you say the Nougat "beta program workaround" what exactly do you mean?
Click to expand...
Click to collapse
Where if you got impatient for an OTA you could sign up for the android beta program to get Nougat (once it was officially released) and then opt out of the program without having to downgrade back to Marshmallow.
I was worried I might be screwed. I will call google tomorrow and see what can be done, although I am a little worried since I bought the phone from Best Buy instead of from the Google Play store
Galrash said:
Where if you got impatient for an OTA you could sign up for the android beta program to get Nougat (once it was officially released) and then opt out of the program without having to downgrade back to Marshmallow.
I was worried I might be screwed. I will call google tomorrow and see what can be done, although I am a little worried since I bought the phone from Best Buy instead of from the Google Play store
Click to expand...
Click to collapse
I'm not entirely sure how it works but I believe you'll need to contact Best Buy. Even so it should be covered by warranty.
Galrash said:
Where if you got impatient for an OTA you could sign up for the android beta program to get Nougat (once it was officially released) and then opt out of the program without having to downgrade back to Marshmallow.
I was worried I might be screwed. I will call google tomorrow and see what can be done, although I am a little worried since I bought the phone from Best Buy instead of from the Google Play store
Click to expand...
Click to collapse
In my experience, Best Buy will not honor manufacturer warranties on smartphones; So unless you bought their Geek Squad coverage, they will tell you to contact Huawei for a warranty RMA.
Contact Info for Warranty RMA:
Huawei Device USA
1-888-548-2934 (1-888-5HUAWEI)
Got ahold of Huawei and it was surprisingly easy and fast. They emailed me a shipping label I just have to drop my phone in the mail and send it to them and it will be covered under warranty. Luckily I have my old Nexus 6 to use until they get it back to me
First of all, I would like to point out that the XDA Developers website has made this problem harder than it needed to be. This post is originally from Stack Exchange, but people said I would have more luck here with this problem. But every little thing I do it a problem. Try to use a proxy on the website? Nope. Try to post this in the Samsung Galaxy S7 section, where it's SUPPOSED to be? Nope. I know it's all to prevent spam, but I mean come on. Be a little lenient here. Anyways, I'm done with my rant. Back to the post.
I have made the mistake of trying to root my phone. Which is fine, but it's a lot more complicated than I thought it was, but since I have asperger's, once I start something, I feel like I have to finish it.
I have a Samsung Galaxy S7 (SM-G930U) with Sprint. I've heard that these phones are EXTREMELY difficult to root. Some even call it impossible. But I can at least try.
I ended up getting tunneled down a endless loop of tasks to complete before I actually root my phone, for preparation. One of the things I must complete is I have to install a TWRP Recovery Image in case of failure. But in order to do that, I have to unblock the bootloader.
To do this, I am using Platform Tools, with includes ADB (Android Debugging Bridge), and Fastboot. I connect my phone to my PC via USB cable, open the CMD, and type:
adb reboot bootloader
Once I do this, my phone reboots into the bootloader, just like it should. Normally, the next step I would take would be to type in:
fastboot oem unlock
When I do this, I am left with the message:
< waiting for any device >
I'm assuming that means that it's not detecting my phone at all. It's odd though, because it was able to detect my device perfectly fine whenever my phone was booted normally, but when I go into the bootloader, it doesn't detect my phone anymore.
After hours of searching around the internet, I found that a potential problem could be the drivers of my phone that are installed on my PC.
Sure enough, if I open up the Device Manager, when in the bootloader, under Universal Serial Bus Controllers, I found the driver "SAMSUNG Mobile USB CDC Composite Device", with a little yellow arrow next to it on the icon.
If I double-click on the entry, in the "Device Status" box, it will say:
This device cannot start. (Code 10)
An invalid parameter was passed to a service or function.
Code 10 means that Windows is saying "There's a problem, but I don't know what." And well, I'm stumped by this.
The drivers work perfectly fine if I'm booted normally, which is why I'm confused. In the meantime, I'll continue my rampage across the internet for a solution to this problem that actually WORKS.
If you're wondering, I using Windows 10.
TheEthanMaverick said:
First of all, I would like to point out that the XDA Developers website has made this problem harder than it needed to be. This post is originally from Stack Exchange, but people said I would have more luck here with this problem. But every little thing I do it a problem. Try to use a proxy on the website? Nope. Try to post this in the Samsung Galaxy S7 section, where it's SUPPOSED to be? Nope. I know it's all to prevent spam, but I mean come on. Be a little lenient here. Anyways, I'm done with my rant. Back to the post.
I have made the mistake of trying to root my phone. Which is fine, but it's a lot more complicated than I thought it was, but since I have asperger's, once I start something, I feel like I have to finish it.
I have a Samsung Galaxy S7 (SM-G930U) with Sprint. I've heard that these phones are EXTREMELY difficult to root. Some even call it impossible. But I can at least try.
I ended up getting tunneled down a endless loop of tasks to complete before I actually root my phone, for preparation. One of the things I must complete is I have to install a TWRP Recovery Image in case of failure. But in order to do that, I have to unblock the bootloader.
To do this, I am using Platform Tools, with includes ADB (Android Debugging Bridge), and Fastboot. I connect my phone to my PC via USB cable, open the CMD, and type:
adb reboot bootloader
Once I do this, my phone reboots into the bootloader, just like it should. Normally, the next step I would take would be to type in:
fastboot oem unlock
When I do this, I am left with the message:
< waiting for any device >
I'm assuming that means that it's not detecting my phone at all. It's odd though, because it was able to detect my device perfectly fine whenever my phone was booted normally, but when I go into the bootloader, it doesn't detect my phone anymore.
After hours of searching around the internet, I found that a potential problem could be the drivers of my phone that are installed on my PC.
Sure enough, if I open up the Device Manager, when in the bootloader, under Universal Serial Bus Controllers, I found the driver "SAMSUNG Mobile USB CDC Composite Device", with a little yellow arrow next to it on the icon.
If I double-click on the entry, in the "Device Status" box, it will say:
This device cannot start. (Code 10)
An invalid parameter was passed to a service or function.
Code 10 means that Windows is saying "There's a problem, but I don't know what." And well, I'm stumped by this.
The drivers work perfectly fine if I'm booted normally, which is why I'm confused. In the meantime, I'll continue my rampage across the internet for a solution to this problem that actually WORKS.
If you're wondering, I using Windows 10.
Click to expand...
Click to collapse
I am having similar problems with my Galaxy S7. In order to make any significant changes, the bootloader MUST be unlocked FIRST. Hence, the dilemma, if you can't make changes without an unlocked bootloader, and you can't unlock the bootloader, what can be done.
As far as I know Samsung devices simply don't have no fastboot support. Refer to Odin flashing tool instead.
Alright. just to get this out of the way, I used to do tech support for HTC many moons ago. like back when they were *the* name in originating new tech to smart phones. I worked my ass off to get into the R&D team that handled all the new products that got released and to our product recovery team(the idiots that try to put a good light on a bad decision made by corporate). I have rooted and installed custom ROMS and recovery software on several phones from them as well as since then with the latest being my old galaxy S7 loaded up with TWRP and lineagoe OS(although i do not remember which version now)
But i did not do literally *ANY* of that with my Xiaomi MiA1. the phone functioned how i wanted it to out of the box and with the stock ROM, i had no need or desire to do anything with the ROM.
I have all but completely given up on doing this on my own now. I have gone over every guide on the MI forums for xiaomi and i think i may have even exhausted the ones that are available here now too. I am not sure WTH the problem at this point even is but here is the lowdown:
:fingers-crossed:
got the update near the end of December/beginning of January to update my MI A1 to the new android pie version that just came out OTA(i actually have two of these phones, one i have not updated since the first update to oreo, and this one that is hardbricked from after the PIE update)
At first when i got the OTA update, my phone started to act sluggish. simple apps like messenger, or google drive that had always worked flawlessly suddenly were taking ages to load. So like any sensible person, i pulled my info to my SD card, took it out, and then did a system recovery to restore factory defaults and start with a fresh OS again, just like when windows starts behaving poorly.
only this did not fix the problem. It persisted with poor performance after the factory data reset and upon my next reboot, my phone just stopped loading when it got to the MI logo on the screen. i literally let the phone sit on this screen overnight thinking just maybe it was being slow to boot after the reset. No luck and in the morning it remained at this screen.
just to make a note:
-phone was purchased off of amazon, i have reached out to the seller(it was a business)
-phone is in CANADA, so there are no service centers
-i CANNOT enter recovery mode(pwr + volup + voldn), it just freezes at the mi screen
-i CAN enter fastboot, but cannot flash room
-bootloader is locked and i have not yet found a method that will successfully unlock it
-the miflash tool does not work(on any version what-so-ever)
-the mi unlock tool gets to 50% and then fails, cannot unlock
-i have installed minimal adb for fastboot, none of the related commands succeed(yes system sees the phone:
c:\adb>fastboot devices
91c0963c0804 fastboot)
-i cannot unlock bootloader here and cannot install twrp or any other recovery image and it will not allow it even temporarily
I've gotten desperate enough to have even gone to the extreme and tried EDL mode by using test point to enter, computer recognizes the device even as the qualcom 9008, still no luck with any of the tools or ROMs provided on Xiaomi's website.
So be real with me here ladies and gents.... should i take this thing on my next trip up a telecomm tower and biff it as hard as i can at the ground(obviously in a snowless area for the most satisfaction) or can you saintly people actually offer me some support on this to turn my brick paperweight back into a phone again?
it is also worth mentioning that this is my first post here because i have never before had a problem with following any of he guides on here to accomplish any task i've ever set out to do with an android device, but this beastly lil mother is seriously making me consider becoming an iphone person(not really but do you get the frustration here?)
I'm writing this at 5:30 in the morning after being up all night working on this task so if my info is missing somewhere along the line just poke me with stick and i will fill in the blanks as needed.
I couldn't be bothered to get and load screenshots tonight but i will get some up tomorrow after sleep, for now i am going to the graveyard to rest.
Thanks for any responses in advance here.
What error show miflash when you try to flash in edl mode?
balannaer said:
Alright. just to get this out of the way, I used to do tech support for HTC many moons ago. like back when they were *the* name in originating new tech to smart phones. I worked my ass off to get into the R&D team that handled all the new products that got released and to our product recovery team(the idiots that try to put a good light on a bad decision made by corporate). I have rooted and installed custom ROMS and recovery software on several phones from them as well as since then with the latest being my old galaxy S7 loaded up with TWRP and lineagoe OS(although i do not remember which version now)
But i did not do literally *ANY* of that with my Xiaomi MiA1. the phone functioned how i wanted it to out of the box and with the stock ROM, i had no need or desire to do anything with the ROM.
I have all but completely given up on doing this on my own now. I have gone over every guide on the MI forums for xiaomi and i think i may have even exhausted the ones that are available here now too. I am not sure WTH the problem at this point even is but here is the lowdown:
:fingers-crossed:
got the update near the end of December/beginning of January to update my MI A1 to the new android pie version that just came out OTA(i actually have two of these phones, one i have not updated since the first update to oreo, and this one that is hardbricked from after the PIE update)
At first when i got the OTA update, my phone started to act sluggish. simple apps like messenger, or google drive that had always worked flawlessly suddenly were taking ages to load. So like any sensible person, i pulled my info to my SD card, took it out, and then did a system recovery to restore factory defaults and start with a fresh OS again, just like when windows starts behaving poorly.
only this did not fix the problem. It persisted with poor performance after the factory data reset and upon my next reboot, my phone just stopped loading when it got to the MI logo on the screen. i literally let the phone sit on this screen overnight thinking just maybe it was being slow to boot after the reset. No luck and in the morning it remained at this screen.
just to make a note:
-phone was purchased off of amazon, i have reached out to the seller(it was a business)
-phone is in CANADA, so there are no service centers
-i CANNOT enter recovery mode(pwr + volup + voldn), it just freezes at the mi screen
-i CAN enter fastboot, but cannot flash room
-bootloader is locked and i have not yet found a method that will successfully unlock it
-the miflash tool does not work(on any version what-so-ever)
-the mi unlock tool gets to 50% and then fails, cannot unlock
-i have installed minimal adb for fastboot, none of the related commands succeed(yes system sees the phone:
c:\adb>fastboot devices
91c0963c0804 fastboot)
-i cannot unlock bootloader here and cannot install twrp or any other recovery image and it will not allow it even temporarily
I've gotten desperate enough to have even gone to the extreme and tried EDL mode by using test point to enter, computer recognizes the device even as the qualcom 9008, still no luck with any of the tools or ROMs provided on Xiaomi's website.
So be real with me here ladies and gents.... should i take this thing on my next trip up a telecomm tower and biff it as hard as i can at the ground(obviously in a snowless area for the most satisfaction) or can you saintly people actually offer me some support on this to turn my brick paperweight back into a phone again?
it is also worth mentioning that this is my first post here because i have never before had a problem with following any of he guides on here to accomplish any task i've ever set out to do with an android device, but this beastly lil mother is seriously making me consider becoming an iphone person(not really but do you get the frustration here?)
I'm writing this at 5:30 in the morning after being up all night working on this task so if my info is missing somewhere along the line just poke me with stick and i will fill in the blanks as needed.
I couldn't be bothered to get and load screenshots tonight but i will get some up tomorrow after sleep, for now i am going to the graveyard to rest.
Thanks for any responses in advance here.
Click to expand...
Click to collapse
take your sd card off your phone i had similar issues and fixed them that way
ccalixtro said:
What error show miflash when you try to flash in edl mode?
Click to expand...
Click to collapse
it depends on which version of the flash tool is used. the beta version of the flash tool claims that it is successful, but the phone will not load to the Android OS after that is completed and it still will not load into the recovery mode to attempt to factory reset or anything else.
other versions have given errors:
miflash 2017.7.20.0 gives the response after attempting for about 10 seconds of "ACK count don't match!"
miflash 2018.11.15.0 gives the error response of "cannot receive hello packet"
and as stated before the miflash beta goes through the complete flash process with the result stating a "success" response, but the phone will not load to OS, just remains stuck on the MI logo screen when the phone is booting up
i have some screen grabs of all this but i am not yet worthy through XDA to be permitted to share them
thanks for the reply
kuartito said:
take your sd card off your phone i had similar issues and fixed them that way
Click to expand...
Click to collapse
i dismantled the phone manually bro, when you use EDL mode this way the SIM/SD tray is removed you then remove the entire backplate and then disconnect the battery cable from the circuit board and you use the test point method to short two pins that force the system to start in EDL mode when you connect the usb-C cable, so unfortunately that is not the issue :crying:
it never seems to be the simple solutions
Thanks for the reply!
Still dead in the water on this one.
Going to look into getting a replacement, that is a disappointing end to the Xiaomi experience
Facing similar issue. Am able to flash however still stuck when device is rebooted with this message;
Supported API: 3
E: Failed to clear BCB message: failed to FSync/dev/block/bootdevice/by-name/miscperation not permitted.
Hello Guys, beforehand, sorry for bad formatting and some english mistakes.
Let me explain what happened.
I was trying to unlock my Nexus 7 bootloader, but I couldn´t get to the Fastboot mode via adb, so I decided to enter fastboot mode by pressing Power + Volume Down button, but I did this while my tablet was connected to the PC, and after that, it shut down and just don´t turned on anymore. (Never got to fastboot mode)
Now when I connect to windows it only show as an AXP Device and it disconnects and connects when i hold Power button, but never starts.
Also I want to note that.
I didn´t manage to get into fastboot mode.
I didn´t manage to unlock the bootloader.
Didn´t install any Custom Rom.
The device is technically 100% stock, so I don´t expect it to be a Hard Brick, but at the same time, I tried all the button combinations and it still wont turn on.
This happened to anyone? Do you guys have any idea what it could be? Any Sollutions for this?
Thank you.
(Edit: I don´t have the Blobs.bin file in case i need to use the Nvflash.)
Gabu1405 said:
Hello Guys, beforehand, sorry for bad formatting and some english mistakes.
Let me explain what happened.
I was trying to unlock my Nexus 7 bootloader, but I couldn´t get to the Fastboot mode via adb, so I decided to enter fastboot mode by pressing Power + Volume Down button, but I did this while my tablet was connected to the PC, and after that, it shut down and just don´t turned on anymore. (Never got to fastboot mode)
Now when I connect to windows it only show as an AXP Device and it disconnects and connects when i hold Power button, but never starts.
Also I want to note that.
I didn´t manage to get into fastboot mode.
I didn´t manage to unlock the bootloader.
Didn´t install any Custom Rom.
The device is technically 100% stock, so I don´t expect it to be a Hard Brick, but at the same time, I tried all the button combinations and it still wont turn on.
This happened to anyone? Do you guys have any idea what it could be? Any Sollutions for this?
Thank you.
(Edit: I don´t have the Blobs.bin file in case i need to use the Nvflash.)
Click to expand...
Click to collapse
Take a look at this comprehensive listing of Nexus 7 button presses/interrupts. They may be of some use...
https://forum.xda-developers.com/showthread.php?p=37606945#post37606945
Hi, Gabu1405...
APX mode is never a good sign with the Nexus 7. It usually indicates that the bootloader has become corrupted, erased or overwritten (by something that is not a valid bootloader). When this occurs, the device is hardbricked and usually requires a motherboard replacement to resurrect the device, although there is a procedure called 'flatline', but this requires previously generated device unique 'blob' files, which you mention in your post.
Having said all of that though, nothing in your description should have caused the bootloader to have become 'damaged'. In order to erase, corrupt or overwrite the bootloader, your device would need to be bootloader unlocked in the first place, because a locked bootloader prohibits any unauthorised write access - bootloader locked devices can only be system 'modified' by official digitally signed updates from Google, which are flashed via the stock recovery.
Are you certain the Nexus 7 is showing as an APX device in Windows device manager?
What was the battery status/percentage when you attempted to unlock the bootloader? Maybe the tablet just needs a good charge, maybe for several hours!
You don't unlock the bootloader with ADB. Android Debug Bridge only works in fully booted Android and with the stock factory recovery. You need to use fastboot to unlock the bootloader, the command being fastboot oem unlock, whilst the device is in fastboot mode, which you boot into via the Volume Down+Power Button key press combo, as you mention in your post.
How it (may have) got into APX mode is certainly strange, because as I've said, this isn't something that normally happens spontaneously - when it happens, it's often due to people mistakenly flashing an incorrect .IMG file to the bootloader partition, causing the bootloader to be overwritten. A possible explanation is hardware failure, and that the emmc/NAND chip storage has developed a fault, and caused the bootloader to become corrupted. It's worth bearing in mind that the Nexus 7 is now seven years old, and with the best will in the world, these things don't last forever, unfortunately. Components fail and data corruptions occur.
If your Nexus 7 is truly in APX mode, for whatever reason, then I'm afraid it's likely hardbricked, and a motherboard replacement is the only realistic way of resurrecting it.
I can only suggest you try charging your Nexus 7, maybe overnight, or for several hours at least, and maybe try the button presses referenced via the link at the top of this post, and see if you can coax life back into your Nexus 7. It does happen sometimes; a seemingly dead device will suddenly spring back to life, through a combination of serendipity and hitting on doing the right things, in the right order, and at the right time
Good luck, Gabu1405...
Rgrds,
Ged.
GedBlake said:
Take a look at this comprehensive listing of Nexus 7 button presses/interrupts. They may be of some use...
https://forum.xda-developers.com/showthread.php?p=37606945#post37606945
Hi, Gabu1405...
APX mode is never a good sign with the Nexus 7. It usually indicates that the bootloader has become corrupted, erased or overwritten (by something that is not a valid bootloader). When this occurs, the device is hardbricked and usually requires a motherboard replacement to resurrect the device, although there is a procedure called 'flatline', but this requires previously generated device unique 'blob' files, which you mention in your post.
Having said all of that though, nothing in your description should have caused the bootloader to have become 'damaged'. In order to erase, corrupt or overwrite the bootloader, your device would need to be bootloader unlocked in the first place, because a locked bootloader prohibits any unauthorised write access - bootloader locked devices can only be system 'modified' by official digitally signed updates from Google, which are flashed via the stock recovery.
Are you certain the Nexus 7 is showing as an APX device in Windows device manager?
What was the battery status/percentage when you attempted to unlock the bootloader? Maybe the tablet just needs a good charge, maybe for several hours!
You don't unlock the bootloader with ADB. Android Debug Bridge only works in fully booted Android and with the stock factory recovery. You need to use fastboot to unlock the bootloader, the command being fastboot oem unlock, whilst the device is in fastboot mode, which you boot into via the Volume Down+Power Button key press combo, as you mention in your post.
How it (may have) got into APX mode is certainly strange, because as I've said, this isn't something that normally happens spontaneously - when it happens, it's often due to people mistakenly flashing an incorrect .IMG file to the bootloader partition, causing the bootloader to be overwritten. A possible explanation is hardware failure, and that the emmc/NAND chip storage has developed a fault, and caused the bootloader to become corrupted. It's worth bearing in mind that the Nexus 7 is now seven years old, and with the best will in the world, these things don't last forever, unfortunately. Components fail and data corruptions occur.
If your Nexus 7 is truly in APX mode, for whatever reason, then I'm afraid it's likely hardbricked, and a motherboard replacement is the only realistic way of resurrecting it.
I can only suggest you try charging your Nexus 7, maybe overnight, or for several hours at least, and maybe try the button presses referenced via the link at the top of this post, and see if you can coax life back into your Nexus 7. It does happen sometimes; a seemingly dead device will suddenly spring back to life, through a combination of serendipity and hitting on doing the right things, in the right order, and at the right time
Good luck, Gabu1405...
Rgrds,
Ged.
Click to expand...
Click to collapse
Sorry, I expressed myself wrongly, I ran the same command as you said, it was fastboot oem unlock and it just said, "waiting for device..." then I tried fastboot oem unlock-go, also the same thing "waiting for device" so I just disconnected the tablet and restarted it and it was working pretty fine, then I connected to the PC and tried to enter fastboot mode manually, and this is when it shut down and never turned back on.
Also, my battery was at 70% at that time and yes, It's clearly on APX mode.
Well, thank you for your reply, now the only thing I got to do is recharge it and hope for the best.
Regards.
Gabu1405 said:
Sorry, I expressed myself wrongly, I ran the same command as you said, it was fastboot oem unlock and it just said, "waiting for device..." then I tried fastboot oem unlock-go, also the same thing "waiting for device" so I just disconnected the tablet and restarted it and it was working pretty fine, then I connected to the PC and tried to enter fastboot mode manually, and this is when it shut down and never turned back on.
Also, my battery was at 70% at that time and yes, It's clearly on APX mode.
Well, thank you for your reply, now the only thing I got to do is recharge it and hope for the best.
Regards.
Click to expand...
Click to collapse
Probably not much use until, or indeed if, you can get out of APX Mode... But the 'waiting for device' message is usually an indicator of a Windows driver problem - Windows is not able to communicate with the Nexus 7.
The way you'd normally do things is by first running the command fastboot devices
This command does nothing, except to confirm you have a viable fastboot connection, by displaying your Nexus 7's unique serial number in your Windows Command/DOS box. If this serial number fails to appear, you have a driver/connectivity problem and proceeding on to fastboot oem unlock would be pointless until the driver/connectivity problem is resolved.
Anyway, I hope charging the device helps. I'm still inclined to think that your device is recoverable - it would certainly be very unusual for the bootloader to be borked when it hasn't even been unlocked yet. In the seven years I've been a Nexus 7 owner, and being active on these forums for many of those years, I haven't encountered any reports by other XDA members where a locked bootloader has simply quit working... As I say, it'd be very unusual, but I suppose not wholly impossible.
Rgrds,
GB.
GedBlake said:
Probably not much use until, or indeed if, you can get out of APX Mode... But the 'waiting for device' message is usually an indicator of a Windows driver problem - Windows is not able to communicate with the Nexus 7.
The way you'd normally do things is by first running the command fastboot devices
This command does nothing, except to confirm you have a viable fastboot connection, by displaying your Nexus 7's unique serial number in your Windows Command/DOS box. If this serial number fails to appear, you have a driver/connectivity problem and proceeding on to fastboot oem unlock would be pointless until the driver/connectivity problem is resolved.
Anyway, I hope charging the device helps. I'm still inclined to think that your device is recoverable - it would certainly be very unusual for the bootloader to be borked when it hasn't even been unlocked yet. In the seven years I've been a Nexus 7 owner, and being active on these forums for many of those years, I haven't encountered any reports by other XDA members where a locked bootloader has simply quit working... As I say, it'd be very unusual, but I suppose not wholly impossible.
Rgrds,
GB.
Click to expand...
Click to collapse
Well, charged my device for a whole day, and now I tried to do the button combinations which you sent the link, nothing happened.
I thought that my battery could be unplugged or the cable was loose or something, so I opened the tablet and it was fine.
So, I just decided to do the button combinations while plugged into my PC, and I noticed that doesn´t matter which combination I try, the tablet disconnects from the PC and instantly reconnects, but still in APX mode.
I guess it is Game Over for me, gonna recharge it again, and try again tomorrow.
Thanks again.
Gabu1405 said:
Hello Guys, beforehand, sorry for bad formatting and some english mistakes.
Let me explain what happened.
I was trying to unlock my Nexus 7 bootloader, but I couldn´t get to the Fastboot mode via adb, so I decided to enter fastboot mode by pressing Power + Volume Down button, but I did this while my tablet was connected to the PC, and after that, it shut down and just don´t turned on anymore. (Never got to fastboot mode)
Now when I connect to windows it only show as an AXP Device and it disconnects and connects when i hold Power button, but never starts.
Also I want to note that.
I didn´t manage to get into fastboot mode.
I didn´t manage to unlock the bootloader.
Didn´t install any Custom Rom.
The device is technically 100% stock, so I don´t expect it to be a Hard Brick, but at the same time, I tried all the button combinations and it still wont turn on.
This happened to anyone? Do you guys have any idea what it could be? Any Sollutions for this?
Thank you.
(Edit: I don´t have the Blobs.bin file in case i need to use the Nvflash.)
Click to expand...
Click to collapse
Hi!
I had a Nexus 7 stuck in APX mode as well. Without the blobs saved you can't do anything. I tried a lot of thigs but nothing really helped. I ended up searching for an another N7 with a broken screen but with a working motherboard online. I was lucky and find one around $15. I swapped the boards and it was good to go.
Zsolti
Gabu1405 said:
Hello Guys, beforehand, sorry for bad formatting and some english mistakes.
Let me explain what happened.
I was trying to unlock my Nexus 7 bootloader, but I couldn´t get to the Fastboot mode via adb, so I decided to enter fastboot mode by pressing Power + Volume Down button, but I did this while my tablet was connected to the PC, and after that, it shut down and just don´t turned on anymore. (Never got to fastboot mode)
Now when I connect to windows it only show as an AXP Device and it disconnects and connects when i hold Power button, but never starts.
Also I want to note that.
I didn´t manage to get into fastboot mode.
I didn´t manage to unlock the bootloader.
Didn´t install any Custom Rom.
The device is technically 100% stock, so I don´t expect it to be a Hard Brick, but at the same time, I tried all the button combinations and it still wont turn on.
This happened to anyone? Do you guys have any idea what it could be? Any Sollutions for this?
Thank you.
(Edit: I don´t have the Blobs.bin file in case i need to use the Nvflash.)
Click to expand...
Click to collapse
Check out my guide.
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?