Hi guys,i was looking for guide how to unlock Axon 7 with latest update 1.2.0B05 but can't find anything. Can someone please help? I want to flash resurrection remix rom and not to brick phone...or is there better roms?
I cannot believe you're asking this question.
YOU HAVEN'T READ ANYTHING.
This board is full with uncountable guides.
https://forum.xda-developers.com/showthread.php?t=3573108
Not working....error: Length cannot be less than zero. Parameter name: length
salle25 said:
Not working....error: Length cannot be less than zero. Parameter name: length
Click to expand...
Click to collapse
Really, the last thing this forum needs is people unable to find guides on their own...
Ask @bkores about the error
WTF is wrong with you ppl?? I came to ask for help and you told me i'm retarded and stupid in nice way! If you don't wan't to help anyone then don't post reply or help and don't QQ about that! Thanx a lot!
salle25 said:
WTF is wrong with you ppl?? I came to ask for help and you told me i'm retarded and stupid in nice way! If you don't wan't to help anyone then don't post reply or help and don't QQ about that! Thanx a lot!
Click to expand...
Click to collapse
I'm sry but there's nobody here who will tell you're stupid,
People here are willing to help, but if you are too lazy to search for the guides (yes more then one is available) people will tell you that you are lazy.
Now I link a working guide for you
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
If you want it easier, search for the toolkit, it will make the most work for you.
Nope....not working. axon7tool.exe keeps crashing: "This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information."
Toolkit is useless too,MiFlash doesn't see phone when in EDL mode,reinstaled every possible driver i found and not even Zadig helped. I had custom roms on every singe phone i had,but this one is pain in the ...
Got it sorted....renaming to .bin was problem,thanx
question
me too
salle25 said:
Got it sorted....renaming to .bin was problem,thanx
Click to expand...
Click to collapse
Yes it's a bit harder to unlock and flash, good you managed that, I forgot to tell you that there are two toolkits win32 and win64.
Help cant repair my Axon 7 G latest B05
coremania said:
Yes it's a bit harder to unlock and flash, good you managed that, I forgot to tell you that there are two toolkits win32 and win64.
Click to expand...
Click to collapse
I try to use both method and still withaut succes also have message before run my phone "Your device software can't be checked for corruption, Please lock the bootloader"
I try almost evrything and nothing.
Bizon86 said:
I try to use both method and still withaut succes also have message before run my phone "Your device software can't be checked for corruption, Please lock the bootloader"
I try almost evrything and nothing.
Click to expand...
Click to collapse
So what don't you understand on this message? It tells you that your bootloader is already unlocked [emoji779] [emoji779]
marcus.linkenbach said:
So what don't you understand on this message? It tells you that your bootloader is already unlocked [emoji779] [emoji779]
Click to expand...
Click to collapse
No is not unlocked Axontooolkit says something oposit. I try both guides from this topic and:
- twrp dosent instal
- cant allow oem unllock
- when use UNLOCK BOOTLOADER Miflash dosent see my devices
Bizon86 said:
I try to use both method and still withaut succes also have message before run my phone "Your device software can't be checked for corruption, Please lock the bootloader"
I try almost evrything and nothing.
Click to expand...
Click to collapse
Your bootloader is unlocked, you only got to managed the rest, read this thread here, you will see it's familiar to your situation, read to the end.
https://forum.xda-developers.com/axon-7/help/to-date-guide-rooting-a2017g-b04-t3666808
I try this and still. nothing
Bizon86 said:
I try this and still. nothing
Click to expand...
Click to collapse
This is a bit thin.
A bit more details, you don't manage to go to edl mode ?
Did you try zadig to to get the right drivers working ?
What do see in device manager ?
Can you boot to stock recovery?
Did you tried to start from scratch with the guide, not the toolkit ?
No detail, no help
Edit: if you use only the toolkit, may ask in the toolkit thread for help ???
coremania said:
This is a bit thin.
A bit more details, you don't manage to go to edl mode ?
Did you try zadig to to get the right drivers working ?
What do see in device manager ?
Can you boot to stock recovery?
Did you tried to start from scratch with the guide, not the toolkit ?
No detail, no help
Edit: if you use only the toolkit, may ask in the toolkit thread for help ???
Click to expand...
Click to collapse
Zadig works for axon7tool only, MiFlash uses COM while axon7tool uses usb protocol
- The edl is dont working because phone go blank after use command and computer dosent see it.
- i try zading and try another driver effect is the same.
- in device menager i see android device but only when smartfon is running
- i start from the scratch the effect is the same
- i cant turn allow oem
the problem is with phone if i use adb reboot computer dont see phone
Bizon86 said:
Then what i must do any idea?
Click to expand...
Click to collapse
First of all, understand what you just did. If you don't explain it in an understandable way, we won't get any of it...
So:
-You unlocked the bootloader.
-axon7toolkit failed somewhere, and you didn't tell us exactly where
-you didn't try to use any guide to retake from where it ended up failing
-you didn't try to enter any mode
So just try to get to recovery or fastboot, using the 5 sec screen. After that we'll see
Bizon86 said:
- The edl is dont working because phone go blank after use command and computer dosent see it.
- i try zading and try another driver effect is the same.
- in device menager i see android device but only when smartfon is running
- i start from the scratch the effect is the same
- i cant turn allow oem
the problem is with phone if i use adb reboot computer dont see phone
Click to expand...
Click to collapse
If you go to edl, by adb command or by pressing both volume buttons while connecting usb the screen goes blank, that's ok, it has to be this way.
Why you want to turn on allow oem, you are already unlocked.
Your issue seems to be the driver, I guess.
Edit: try this maybe, from the toolkit FAQ
The toolkit says my device is connected through ADB but adb commands don't work?
Your device may be unauthorized. Unlock your device, open a cmd window, type in "adb devices" and then accept the "Allow USB debugging" prompt on your phone. Make sure to check the "Always allow from this computer" box as well. If you don't get the prompt, try retoggling USB debugging, replugging your device in, and revoking all USB debugging authorizations in developer options.
Related
Hi Guys
Another rooting/flashing noob here that's messed up his N7 sorry
I know there's other threads with similair issues but they all advise fixes involving using adb connection and usb debugging which I cannot do (explained below)
My device will turn on, it goes to the google logo with the green start icon, I can select and go into bootloader and recovery, if I press start it says booting failed in the upper left corner and will go no further.
My device is plugged in via usb, i have the latest rookit 1.5.5, and sdk installed etc, i also have the naked drivers and the factory images from google on my pc.
The machine came with 4.1.2 installed (nakasi-jzo54k).
To mess it up, somewhere in between updating to 4.2, rooting and unrooting it, and flashing it i must have done something wrong but being a happy button bashing noob I don't know what exactly...
And yes I also didn't make a backup of any kind because well I'm just a moron and lesson well learnt.
So yeah, I have no adb connection, can't go into debuging mode and it won't boot.
Does anybody know if there is anyway I can restore my tablet please? Any help would be hugely appreciated!
Many thanks
greyphox said:
Hi Guys
Another rooting/flashing noob here that's messed up his N7 sorry
I know there's other threads with similair issues but they all advise fixes involving using adb connection and usb debugging which I cannot do (explained below)
My device will turn on, it goes to the google logo with the green start icon, I can select and go into bootloader and recovery, if I press start it says booting failed in the upper left corner and will go no further.
My device is plugged in via usb, i have the latest rookit 1.5.5, and sdk installed etc, i also have the naked drivers and the factory images from google on my pc.
The machine came with 4.1.2 installed (nakasi-jzo54k).
To mess it up, somewhere in between updating to 4.2, rooting and unrooting it, and flashing it i must have done something wrong but being a happy button bashing noob I don't know what exactly...
And yes I also didn't make a backup of any kind because well I'm just a moron and lesson well learnt.
So yeah, I have no adb connection, can't go into debuging mode and it won't boot.
Does anybody know if there is anyway I can restore my tablet please? Any help would be hugely appreciated!
Many thanks
Click to expand...
Click to collapse
If you got half way through rooting, what has happened to your ADB?
Try the option "Return to stock and Flash stock image" try that.
What message does ADB give you etc?
Wilks3y said:
If you got half way through rooting, what has happened to your ADB?
Try the option "Return to stock and Flash stock image" try that.
What message does ADB give you etc?
Click to expand...
Click to collapse
Hi thanks
Well when I run 'adb devices' in dos the device does not come up, blank etc
but if in the advanced utilities section of the rookit it will reboot it and say connected etc when i try to boot/flash image for bootloader, system, recovery etc but always goes back to google logo and won't boo up, can still get into bootloader and recovery though
i fully rooted it and unrooted it, i tried to flash 4.1.1 to see if i could thats when this all started
if i try flash stock + unroot option (device is on/normal) sub option the rootkit tries to check adb status and says not connected etc which makes sense as dos won't detect it, if this helps in device manager its coming up as...
samsung android phone
android bootloader interface
so i that driver in rootkit to manually install the naked drivers in device manager and it will say they are up to date etc
so the advanced utilities section for boot/flash image will communicate but no other.....
flash stock root used to detect it but even then in dos it would give me the 'too many links error'
I just hope there is a solution.... and i hope all that makes sense sorry
Cheers
greyphox said:
Hi thanks
Well when I run 'adb devices' in dos the device does not come up, blank etc
but if in the advanced utilities section of the rookit it will reboot it and say connected etc when i try to boot/flash image for bootloader, system, recovery etc but always goes back to google logo and won't boo up, can still get into bootloader and recovery though
i fully rooted it and unrooted it, i tried to flash 4.1.1 to see if i could thats when this all started
if i try flash stock + unroot option (device is on/normal) sub option the rootkit tries to check adb status and says not connected etc which makes sense as dos won't detect it, if this helps in device manager its coming up as...
samsung android phone
android bootloader interface
so i that driver in rootkit to manually install the naked drivers in device manager and it will say they are up to date etc
so the advanced utilities section for boot/flash image will communicate but no other.....
flash stock root used to detect it but even then in dos it would give me the 'too many links error'
I just hope there is a solution.... and i hope all that makes sense sorry
Cheers
Click to expand...
Click to collapse
Have you added ADB to your envioronment varibles?
If not,
Control Panel -> Advanced -> Envioronment Variables, then add the path to your SDK folder to it, after the other variables (Variables are separated using ; )
Also, try to install the drivers, using Wug's method, thats THE ONLY ONE that worked for me, unistall anything to do with nexus before hand.
Goto Device manager, find anything that involves Nexus or Android.
Then Start the "Full Driver Method" on Wugs kit.
This should sort your driver issue.
Then the Nexus should be visible through ADB.
PS- Your adb isnt broken if its accepting the commands.
The reason your device isnt listed, is the Drivers.
You have driver issues, so try the what I just stated and let me know .
nexus toolkit from dev section
ngoralph said:
nexus toolkit from dev section
Click to expand...
Click to collapse
Have you even read what hes said?
He's already tried the toolkit...
Wilks3y said:
Have you added ADB to your envioronment varibles?
If not,
Control Panel -> Advanced -> Envioronment Variables, then add the path to your SDK folder to it, after the other variables (Variables are separated using ; )
Also, try to install the drivers, using Wug's method, thats THE ONLY ONE that worked for me, unistall anything to do with nexus before hand.
Goto Device manager, find anything that involves Nexus or Android.
Then Start the "Full Driver Method" on Wugs kit.
This should sort your driver issue.
Then the Nexus should be visible through ADB.
PS- Your adb isnt broken if its accepting the commands.
The reason your device isnt listed, is the Drivers.
You have driver issues, so try the what I just stated and let me know .
Click to expand...
Click to collapse
The first step in the full driver guide in wugs kit is to enable usb debugging which i cannot do though as it won't power on.......
I have added the environmental variabes before yes sorry, qbkings utube vids showed me how to do that
Just tried these steps
toolkit home screen, flash stock + unroot (softbricked bootloop)
then naksaki 4.2 jzo54k, auto download and extract.
it got to dos stage and i get 'Failed bootloader is locked'
??? thanks again
Wilks3y said:
Have you added ADB to your envioronment varibles?
If not,
Control Panel -> Advanced -> Envioronment Variables, then add the path to your SDK folder to it, after the other variables (Variables are separated using ; )
Also, try to install the drivers, using Wug's method, thats THE ONLY ONE that worked for me, unistall anything to do with nexus before hand.
Goto Device manager, find anything that involves Nexus or Android.
Then Start the "Full Driver Method" on Wugs kit.
This should sort your driver issue.
Then the Nexus should be visible through ADB.
PS- Your adb isnt broken if its accepting the commands.
The reason your device isnt listed, is the Drivers.
You have driver issues, so try the what I just stated and let me know .
Click to expand...
Click to collapse
OK unlocked it via the main unlock option on rootkit and it unlocked ok, so im now re-trying te softbricked option to flash etc and its currently.. writing system...
greyphox said:
OK unlocked it via the main unlock option on rootkit and it unlocked ok, so im now re-trying te softbricked option to flash etc and its currently.. writing system...
Click to expand...
Click to collapse
Sounds good mate !
Need any extra help drop us a PM I'd be happy to lend a hand.
Wilks3y said:
Sounds good mate !
Need any extra help drop us a PM I'd be happy to lend a hand.
Click to expand...
Click to collapse
MOOOOOO!
It wrote to the system ok and now its hanging on erasing user data, googled and its happend to others.......
OK, more help please, been hanging for5 mins lol
Issue Fixed I think, he PM'd me.
Unlocked but... what do I do now?
Newbie but old or old but newbie - With the need and not just a curious want, to be able to "rename" my Nexus 7 v1 so I can see a friendly name in my old DD-WRTed Linksys GL, I finally had enough gumption to try rooting this tablet.
So, I was excited that when I used Nexus Root Toolkit v1.6.8 on my Nexus 7 v1, following the "easy and visual" steps, I actually managed to unlock this device. But when it came to the "root" part, the ADB repeatedly failed to recognize this tablet. I tried all the suggested steps and remedies, but so far, nada.
The tablet now boots past the white "Google" with an unlocked icon at the bottom, but nothing beyond thea big white "right-arrow" on the screen. I can choose a Wi-Fi signal to connect to, but that's it.
This is my first tablet and I have been playing with it for the past 3 months. I know people here are more than willing to help, so thank you in advance.
BTW, I am not that young to spend hours way past sleeping time to scour for answers and piece it together.
Wilks3y said:
Issue Fixed I think, he PM'd me.
Click to expand...
Click to collapse
Could you let me know his solution as I have exactly the same problem and have used all of his previous (unsuccessful) fixes myself?
Kindred Mole said:
Could you let me know his solution as I have exactly the same problem and have used all of his previous (unsuccessful) fixes myself?
Click to expand...
Click to collapse
+1
This worked for me...
Download the image file for your device which you can find at the Google Developer's site
Copy the uncompressed files from the image archive to the platform-tools folder of the Android SDK
Use the up and down volume on the device to get into bootloader mode. Connect the device to a usb port.
Open a command prompt in the platform tools folder and run the flash-all batch file to load the image to your device. After a few minutes I got the happy X logo to get me back to a blank slate.
Hi
Tried to flash a new kernel and all seemed ok (flashed phones and nexus 7 few times now) when I came out of flashing I hit a bootloop, I though nothing of it and tried to restart....same issue, so next I tried to go into cw recovery, no joy, it will not show again.
I can power/vol keys to android fastboot screen with start power restart boot and so on but if I choose recovery nothing happens, I am stuck with either a bootloop or stuck on android fastboot screen and not able to move from either.
I have tried the toolkit and most other things but the problem is it cannot see my nexus 7, even after installing drivers and so on the toolkit (top right) does not list my nexus as found, because of this I cannot reflash any stock firmware/recover/reflash cwr.
Not sure how I can get around this if my pc cannot see the nexus 7.
Thanks for any help
voodoochild2008 said:
Hi
Tried to flash a new kernel and all seemed ok (flashed phones and nexus 7 few times now) when I came out of flashing I hit a bootloop, I though nothing of it and tried to restart....same issue, so next I tried to go into cw recovery, no joy, it will not show again.
I can power/vol keys to android fastboot screen with start power restart boot and so on but if I choose recovery nothing happens, I am stuck with either a bootloop or stuck on android fastboot screen and not able to move from either.
I have tried the toolkit and most other things but the problem is it cannot see my nexus 7, even after installing drivers and so on the toolkit (top right) does not list my nexus as found, because of this I cannot reflash any stock firmware/recover/reflash cwr.
Not sure how I can get around this if my pc cannot see the nexus 7.
Thanks for any help
Click to expand...
Click to collapse
try to flash recovery again via fastboot...or doesnt pc recognize divice at all?
S.R
shivasrage said:
try to flash recovery again via fastboot...
S.R
Click to expand...
Click to collapse
Hi
I cannot flash anything. On the fastboot screen I can scroll up and down powr off/start/recovery....if I choose any (apart from power off) nothing happens.
When I hook it up to my pc it cannot see it, nexus 7 toolkit also cannot see it, it does not list it as found so I cannot flash anything on to it, if I try it just says waiting for device, tried other things and same thing either waiting for device or asks if fastboot installed.
voodoochild2008 said:
Hi
I cannot flash anything. On the fastboot screen I can scroll up and down powr off/start/recovery....if I choose any (apart from power off) nothing happens.
When I hook it up to my pc it cannot see it, nexus 7 toolkit also cannot see it, it does not list it as found so I cannot flash anything on to it, if I try it just says waiting for device, tried other things and same thing either waiting for device or asks if fastboot installed.
Click to expand...
Click to collapse
f****
have you tried flashing factory image from google site.with flash all-sh?
shivasrage said:
f****
have you tried flashing factory image from google site.with flash all-sh?
Click to expand...
Click to collapse
I have a image ready but not able to flash....but what is flash all-sh? trying to search for it, is it a tool to force flash?
voodoochild2008 said:
I have a image ready but not able to flash....but what is flash all-sh? trying to search for it, is it a tool to force flash?
Click to expand...
Click to collapse
no its included in the factory image to flash all i one so it looks like for the nexus 4:
flash-all .....its a windows batch image with all included.... try this
S:R.
shivasrage said:
no its included in the factory image to flash all i one so it looks like for the nexus 4:
flash-all .....its a windows batch image with all included.... try this
S:R.
Click to expand...
Click to collapse
Thanks....but still get waiting for device, thats the problem, nothing seems to see it so I cannot flash anything to it.
You are already at the bootloader screen. Use your computer to fastboot flash a new kernel. Being able to get into recovery has nothing to do with it. You screwed it up flashing a kernel. Its likely thats all you need to fix it. Flash a new one with fastboot.
You are already at the bootloader screen. Use your computer to fastboot flash a new kernel. Being able to get into recovery has nothing to do with it. You screwed it up flashing a kernel. Its likely thats all you need to fix it. Flash a new one with fastboot.
i thought the same as you but fastboot isn recognizig N7 anymore....always wating for device....
Hemidroids said:
You are already at the bootloader screen. Use your computer to fastboot flash a new kernel. Being able to get into recovery has nothing to do with it. You screwed it up flashing a kernel. Its likely thats all you need to fix it. Flash a new one with fastboot.
Click to expand...
Click to collapse
Downloaded the fastboot exe but unsure what it needs to work as when I click on it a run box opens for like half a second and then closes, dont get a chance to read what it says, think I will have to read up on it.
[/COLOR]
voodoochild2008 said:
Downloaded the fastboot exe but unsure what it needs to work as when I click on it a run box opens for like half a second and then closes, dont get a chance to read what it says, think I will have to read up on it.
Click to expand...
Click to collapse
read this... i hope you can follwow that easily like me...
greets S.R.
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
voodoochild2008 said:
Downloaded the fastboot exe but unsure what it needs to work as when I click on it a run box opens for like half a second and then closes, dont get a chance to read what it says, think I will have to read up on it.
Click to expand...
Click to collapse
EXE? doh.......Windows.......sorry cant help.
shivasrage said:
[/COLOR]
read this... i hope you can follwow that easily like me...
greets S.R.
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
Click to expand...
Click to collapse
Tried some of that already but will try again tomorrow.
Thanks for help with this and will post tomorrow if I can sort it. cheers
I hope this instructions can help you a little bit...but if it fails don´t be angry its all I can think of ...at this time ....merry christmas
S.R.
http://forum.xda-developers.com/showthread.php?p=31931117:D
Sent from my Nexus 7 using xda premium
Well after using bits of jrom flasher and nexus toolkit I got it working again, main issue was making the tablet seen, abd and fastboot would not show device.
All up and running again THANKS TO ALL WHO HELPED
voodoochild2008 said:
Well after using bits of jrom flasher and nexus toolkit I got it working again, main issue was making the tablet seen, abd and fastboot would not show device.
All up and running again THANKS TO ALL WHO HELPED
Click to expand...
Click to collapse
How did you get it to work? I have problem getting my device to be recognized. Stuck on boot loop too..
Hey man, how did you get your computer to recognize your device? Would be great to finally fix mine as this is the same exact problem -- computer doesn't recognize it even though in fastboot.
Quacker245 said:
Hey man, how did you get your computer to recognize your device? Would be great to finally fix mine as this is the same exact problem -- computer doesn't recognize it even though in fastboot.
Click to expand...
Click to collapse
I don't understand exactly what you are trying to do, sorry: you said the pc does not see the nexus, "even thought in fastboot".. If you say even thought, it seems to me that you are able to access Android itself or maybe recovery? In that case I can't see the issue.. Sorry my fault, non english mother tongue
But, if have the device soft bricked and you are able to enter ONLY the bootloader (that is what we call often fastboot), then you should start to remove the not working fastboot drivers installed into your PC: launch the nexus in fastboot mode, go to Device Manager into your PC and search for a driver with an yellow exclamation point. This issue is very common so I hope that you have it, too.. So, uninstall that driver, then unlink the nexus from your PC; after a few seconds attach it to another USB port and see if Windows install a driver (it should). If this new driver doesn't work, too, or if Windows does no install any, try this one: http://forum.xda-developers.com/showthread.php?t=1426502
Hope it helps, let us know, see you!
EDIT: also, if you still have no luck, you should find a Linux or Mac PC/laptop and download the adb/fastboot binary files for that OS; this will definitively solve your driver issue ( @#ò#@!"@# Winzozz )
brainvision said:
I don't understand exactly what you are trying to do, sorry: you said the pc does not see the nexus, "even thought in fastboot".. If you say even thought, it seems to me that you are able to access Android itself or maybe recovery? In that case I can't see the issue.. Sorry my fault, non english mother tongue
But, if have the device soft bricked and you are able to enter ONLY the bootloader (that is what we call often fastboot), then you should start to remove the not working fastboot drivers installed into your PC: launch the nexus in fastboot mode, go to Device Manager into your PC and search for a driver with an yellow exclamation point. This issue is very common so I hope that you have it, too.. So, uninstall that driver, then unlink the nexus from your PC; after a few seconds attach it to another USB port and see if Windows install a driver (it should). If this new driver doesn't work, too, or if Windows does no install any, try this one: http://forum.xda-developers.com/showthread.php?t=1426502
Hope it helps, let us know, see you!
EDIT: also, if you still have no luck, you should find a Linux or Mac PC/laptop and download the adb/fastboot binary files for that OS; this will definitively solve your driver issue ( @#ò#@!"@# Winzozz )
Click to expand...
Click to collapse
Hi sorry for not being clear. Basically I am only allowed to access the bootloader and my device is soft-bricked. I'm pretty sure I tried uninstalling and reinstalling the drivers about a year ago when I originally did it, but I'll try again and let you know. Thanks!
Not working anymore.
Sorry.
Do you mean that you had your old tablet already killed, and then you recovered it following these steps?
You can see it here, in my Twitter
https://twitter.com/victorcangil16/status/642389331768942592
Can anyone confirm this on a separate dead tablet? if so its a pretty damn good find.
Hi Victorcangil 16,
Could you exactly discribe how did you make this miracle (which drivers...) ?
Thanks
jo2e said:
Hi Victorcangil 16,
Could you exactly discribe how did you make this miracle (which drivers...) ?
Thanks
Click to expand...
Click to collapse
I used Windows 10 with the NVIDIA Family USB Drivers. I made the process I described in the first post
Victorcangil 16 said:
I used Windows 10 with the NVIDIA Family USB Drivers. I made the process I described in the first post
Click to expand...
Click to collapse
Ok,
Thx for your reply Victorcangil 16.
But how did your device was recognized by windows before done this process ? APX or something else
It was reconized as normal device by Windows, like if I plug my phone to the PC. And the drivers I had to configure them manually, if not, It gives me error when doing FastBoot
Victorcangil 16 said:
It was reconized as normal device by Windows, like if I plug my phone to the PC. And the drivers I had to configure them manually, if not, It gives me error when doing FastBoot
Click to expand...
Click to collapse
It stay on :"<waiting for device>"
And my tablet is not reconized as normal device but as "APX"
What does APX mean?
Change the ADB drivers interface using the next process:
Search in Windows: Device Manager
If the ADB interface has a Yellow alert, Right Click, Update Drivers, Select from Computer, Use Disk, Use all, and then select the file in the NVIDIA Drivers folder (in my case, Downloads). Accept,
Victorcangil 16 said:
What does APX mean?
Click to expand...
Click to collapse
I don't known. My tablet appears like that in the peripherics manager ...
If you hace skype, I can help you easily
Victorcangil 16 said:
If you hace skype, I can help you easily
Click to expand...
Click to collapse
Yes i have skype.
But i think i got the problem : my tablet wasn't rooted and the bootloader was locked...
I think you saved your shield because it was rooted...
I thinks is that. If is has not unlocked bootloader, you can't change nothing. But to unlock it, just type in Fastboot: "fastboot oem unlock" (tablet will Factory Reset)
Victorcangil 16 said:
I thinks is that. If is has not unlocked bootloader, you can't change nothing. But to unlock it, just type in Fastboot: "fastboot oem unlock" (tablet will Factory Reset)
Click to expand...
Click to collapse
Same thing with this command : <waiting for device>
:/ I think something is going on with Drivers
Hi, one question for such kind of reactivation - root is required ?
Yes, Root and Unlocked Bootloader are required ro recover the "killed" Tablet
Just bought by mistake deactivated Shield...is it possible to make root via fastboot ?
Hey guys I just installed the full image of 7.1.2 beta 2 over top of beta 1 using Flashfire without the bootloader and modem selected and all went fine until I decided to use Flashfire to upgrade the bootloader and modem forgetting that we must use Fastboot as I am new to Flashfire and I was reading all through the beta thread before I did it and didn't understand we still must use Fastboot so anyways I am stuck in a hard brick now with the phone not powering on at all and can't do anything to restore it as my Windows 10 now detects the phone as unknown device (device descriptor request failed) is there anything I can do at this point as I just bought this phone used.
The error that I got in Flashfire was that the device storage is full when updating the bootloader as the modem went fine.
@rmorris003
You said the phone won't even power on. You mean no Google? Hold the power button down for a couple of minutes and see if it will reboot. If not put it on a charger, and after fully charging try the long press power button again. If you can get it to start, try to put it in fastboot mode. (ie. power+vol dn). If you can get to bootloader you can send fastboot commands and fix it. If you can get to this point, there are instructions here.
rmorris003 said:
Hey guys I just installed the full image of 7.1.2 beta 2 over top of beta 1 using Flashfire without the bootloader and modem selected and all went fine until I decided to use Flashfire to upgrade the bootloader and modem forgetting that we must use Fastboot as I am new to Flashfire and I was reading all through the beta thread before I did it and didn't understand we still must use Fastboot so anyways I am stuck in a hard brick now with the phone not powering on at all and can't do anything to restore it as my Windows 10 now detects the phone as unknown device (device descriptor request failed) is there anything I can do at this point as I just bought this phone used.
The error that I got in Flashfire was that the device storage is full when updating the bootloader as the modem went fine.
Click to expand...
Click to collapse
Hello... Well if your device is recognized as unknown, you could try to give this a shot:
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Try to install Qualcomm driver first check the device manager. If you see your phone recognized as:
HS-USB QDLOADER 9008
You may be lucky!
Good luck...
5.1 said:
Hello... Well if your device is recognized as unknown, you could try to give this a shot:
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Try to install Qualcomm driver first check the device manager. If you see your phone recognized as:
HS-USB QDLOADER 9008
You may be lucky!
Good luck...
Click to expand...
Click to collapse
I will try this when I get back from work, I just cant get my pc to see it as anything other than unknown device as it says this is the best driver for it.
rmorris003 said:
I will try this when I get back from work, I just cant get my pc to see it as anything other than unknown device as it says this is the best driver for it.
Click to expand...
Click to collapse
I see... There's a txt file in the driver folder. Follow its instructions.
Good luck...
5.1 said:
I see... There's a txt file in the driver folder. Follow its instructions.
Good luck...
Click to expand...
Click to collapse
I am stumped, I have disabled driver enforcement and can't get any drivers to see my phone so I am not sure what to do.
rmorris003 said:
I am stumped, I have disabled driver enforcement and can't get any drivers to see my phone so I am not sure what to do.
Click to expand...
Click to collapse
You disabled driver signature and rebooted your computer? Then installed Qualcomm drivers from the thread I linked you to? I think you have to reboot your computer once more...
Good luck...
I held the power and vol down and now it shows up under com ports so this is a good sign.
Ok got bootloader back and now put twrp on, I had to use qfil with nexus6p_fix_bricked but it got stuck at writing system.img but atleast the phone is on now.
Flashed the 7.1.2 beta 2 full image using the fastboot method included and all is back to normal.
Thanks so much for the help.
rmorris003 said:
Ok got bootloader back and now put twrp on, I had to use qfil with nexus6p_fix_bricked but it got stuck at writing system.img but atleast the phone is on now.
Flashed the 7.1.2 beta 2 full image using the fastboot method included and all is back to normal.
Thanks so much for the help.
Click to expand...
Click to collapse
Wow glad it worked for you... You might push the thanks button in the OP of the thread where you found the debrick tools and thanks @tenfar since he offered the solution. He already saved a few N6P devices. I only linked you to his thread which you could have found yourself anyway...
Cheers...
5.1 said:
Wow glad it worked for you... You might push the thanks button in the OP of the thread where you found the debrick tools and thanks @tenfar since he offered the solution. He already saved a few N6P devices. I only linked you to his thread which you could have found yourself anyway...
Cheers...
Click to expand...
Click to collapse
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.
rmorris003 said:
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.
Click to expand...
Click to collapse
You could report your experience in the other thread. Maybe it could help other users who faced the issue you had. :good:
Cheers...
rmorris003 said:
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.
Click to expand...
Click to collapse
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!
Clarkeofcurtis said:
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!
Click to expand...
Click to collapse
I have the same exact problem, everytime i try to flash with qfil it says it can't connect to my COMPORT
Clarkeofcurtis said:
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!
Click to expand...
Click to collapse
Falitheman said:
I have the same exact problem, everytime i try to flash with qfil it says it can't connect to my COMPORT
Click to expand...
Click to collapse
Hello,
Someone mentioned this in another post:
Hold volume up and plug the USB cord to.your computer and start qfil flash. Keep holding volume up until the flash ends...
Good luck...
5.1 said:
Hello,
Someone mentioned this in another post:
Hold volume up and plug the USB cord to.your computer and start qfil flash. Keep holding volume up until the flash ends...
Good luck...
Click to expand...
Click to collapse
So i have some good news...it connects now. it says start sending programmer but then it says download failed: unable to download flash programmer using sahara protocol and then it fails. Any help?:crying:
Falitheman said:
So i have some good news...it connects now. it says start sending programmer but then it says download failed: unable to download flash programmer using sahara protocol and then it fails. Any help?:crying:
Click to expand...
Click to collapse
Hey,
What version of qpst did you install?
Good luck...
5.1 said:
Hey,
What version of qpst did you install?
Good luck...
Click to expand...
Click to collapse
I am using 2.7.441
Update: It seemed to be working for a second but then it says download failed: qsahara server fail: process fail. Any idea what that means? I really need my phone back
Falitheman said:
I am using 2.7.441
Update: It seemed to be working for a second but then it says download failed: qsahara server fail: process fail. Any idea what that means? I really need my phone back
Click to expand...
Click to collapse
Hey,
Google qpst 2.7.453
It's easy to find. Scan the files on virustotal.com though.
Maybe the older versions are incompatible...
Good luck...
5.1 said:
Hey,
Google qpst 2.7.453
It's easy to find. Scan the files on virustotal.com though.
Maybe the older versions are incompatible...
Good luck...
Click to expand...
Click to collapse
I tried with the version you suggested and i got the same error i just had. Can you send me your version so i can see if that works?
Hello guys. I have the x720 leeco. My problem is that i wiped all and no rom is installed and when i connect the phone to the pc i cant get it done with the drivers so i cant see the internal storage. I can boot on REcovery and Fastboot. Can anyone help me??
Thanks in advance
TrelosEisai said:
Hello guys. I have the x720 leeco. My problem is that i wiped all and no rom is installed and when i connect the phone to the pc i cant get it done with the drivers so i cant see the internal storage. I can boot on REcovery and Fastboot. Can anyone help me??
Thanks in advance
Click to expand...
Click to collapse
Put the rom on an USB stick, connect the stick to the phone with adapter, go into TWRP and flash the rom.
Easyest solution.
Okk i ll try it
Unlucky cant read otg, just putted an micro usb to typec adapter and a micro usb flash drive and cant see it
TrelosEisai said:
Unlucky cant read otg, just putted an micro usb to typec adapter and a micro usb flash drive and cant see it
Click to expand...
Click to collapse
Ok. Than try to flash a stock rom through all in one tool:
https://www.google.com/amp/s/forum....ment/tool-tool-one-mauronofrio-t3580611/amp/5
Oel said:
Ok. Than try to flash a stock rom through all in one tool:
https://www.google.com/amp/s/forum....ment/tool-tool-one-mauronofrio-t3580611/amp/5
Click to expand...
Click to collapse
Agreed,
You are not bricked.
i cant see my device thats the problem
TrelosEisai said:
i cant see my device thats the problem
Click to expand...
Click to collapse
Worst case you can use Qfil.
But first disconnect all unneeded peripherals, and try another cable if possible. Go read the unbricked tested and working. Search the thread for my name, to everything you need in 3 or four posts
Sent from my Pixel XL using XDA Labs
TrelosEisai said:
i cant see my device thats the problem
Click to expand...
Click to collapse
Yeah, but did you installed the all in one thing with the right drivers?
Oel said:
Yeah, but did you installed the all in one thing with the right drivers?
Click to expand...
Click to collapse
which drivers?? i cant do the qfil cause i cant see the phone in pc. when i open it in leeco logo when i connect the phone to pc it says windows cant recognize it.
TrelosEisai said:
which drivers?? i cant do the qfil cause i cant see the phone in pc. when i open it in leeco logo when i connect the phone to pc it says windows cant recognize it.
Click to expand...
Click to collapse
Go read the unbricking thread, it is going to take you days to read, understand, and finally unbrick it. If you are not seeing the device in the system manager of your computer ( Assuming you have a PC) then maybe you are actually bricked.
But, you own a phone that can be unbricked, no not a big deal. It can be resolved, the instructions in the unbricked tested and working thread are explicit go read it.
I create several how to's within that thread on unbricking, and have updated the links on the software tools needed. I have personally unbricked 7 leeco, and several others unbricked their phones by following the advice of everyone who contributed to the thread.
Everything you need and more is there that thread, waiting for you.
Go there get the files, read the instructions and soon you phone will work again. Do not download the qfil from the Original post...it doesn't work. I don't have the links to paste at the moment, nor the time to search for you Just use the thread search bar and type my name to get consolidated steps read through all of the posts, because its a progression.
There are three methods you can use to unbrick, the easiest method is probably Qfil, and Flash 2.0
Essentially you need the Qfil: le_zl1_qfil_ufs_fix , FlashOne2.0 files, go ahead and download prog_ufs_firehose_8996_ddr just in case. But it should download automatically. You need to follow the steps to get your computer ready to unbrick the phone...all in the thread instructions.
Once you do it once successfully, it will become easier with each try.
tsongming said:
Go read the unbricking thread, it is going to take you days to read, understand, and finally unbrick it. If you are not seeing the device in the system manager of your computer ( Assuming you have a PC) then maybe you are actually bricked.
But, you own a phone that can be unbricked, no not a big deal. It can be resolved, the instructions in the unbricked tested and working thread are explicit go read it.
I create several how to's within that thread on unbricking, and have updated the links on the software tools needed. I have personally unbricked 7 leeco, and several others unbricked their phones by following the advice of everyone who contributed to the thread.
Everything you need and more is there that thread, waiting for you.
Go there get the files, read the instructions and soon you phone will work again. Do not download the qfil from the Original post...it doesn't work. I don't have the links to paste at the moment, nor the time to search for you Just use the thread search bar and type my name to get consolidated steps read through all of the posts, because its a progression.
There are three methods you can use to unbrick, the easiest method is probably Qfil, and Flash 2.0
Essentially you need the Qfil: le_zl1_qfil_ufs_fix , FlashOne2.0 files, go ahead and download prog_ufs_firehose_8996_ddr just in case. But it should download automatically. You need to follow the steps to get your computer ready to unbrick the phone...all in the thread instructions.
Once you do it once successfully, it will become easier with each try.
Click to expand...
Click to collapse
Ok i am starting now i will come back with the results
As i understand my phone is not bricked cause i can go into fastboot and REcovery. The problem is i dont have OS installed so i stuck at Leeco image. The other problem is when i connect the phone with the Pc this happens on device manager. So how i can make it to see the internal storage and put inside the phone the rom.
TrelosEisai said:
As i understand my phone is not bricked cause i can go into fastboot and REcovery. The problem is i dont have OS installed so i stuck at Leeco image. The other problem is when i connect the phone with the Pc this happens on device manager. So how i can make it to see the internal storage and put inside the phone the rom.
Click to expand...
Click to collapse
Install Google's USB ADB and Fastboot drivers.
https://developer.android.com/studio/run/win-usb
Can you boot into download mode (I think it's volume down + power) and then connect to PC. After that, you should see the unknown device on device manager. Try to right-click on it and update drivers. On the next screen, select that you have drivers and you'd like to pick your own (not the Windows Update option!) Then select Manufacturer Google and Fastboot/ADB debugging option. Device might work in fastboot now, you can test by doing "fastboot devices". If that works, then you can install ROM via Fastboot.
If this doesn't work, you can revert changes by going into device manager and uninstalling the driver for that device.
Ascertion said:
Install Google's USB ADB and Fastboot drivers.
https://developer.android.com/studio/run/win-usb
Can you boot into download mode (I think it's volume down + power) and then connect to PC. After that, you should see the unknown device on device manager. Try to right-click on it and update drivers. On the next screen, select that you have drivers and you'd like to pick your own (not the Windows Update option!) Then select Manufacturer Google and Fastboot/ADB debugging option. Device might work in fastboot now, you can test by doing "fastboot devices". If that works, then you can install ROM via Fastboot.
If this doesn't work, you can revert changes by going into device manager and uninstalling the driver for that device.
Click to expand...
Click to collapse
I cant find the option for Manufacturer Google for the Fastboot/Adb debugging options
TrelosEisai said:
I cant find the option for Manufacturer Google for the Fastboot/Adb debugging options
Click to expand...
Click to collapse
Hi, sorry for the late reply.
Are you able to see these in screenshots? Between steps 2 and steps 3, you might need to select Android ADB or Android Device before you can see Google in the dropdown.
Maybe after these you might be able to see device in fastboot?