Related
So this can't be rooted? I've checked here:
http://www.droidfiles.us/nexus-s-4g/root-nexus-s-4g/
http://forum.xda-developers.com/showthread.php?t=1074955
http://forum.xda-developers.com/showthread.php?t=878786
I can't seem to get fastboot devices to recognize my device. I'm following all the instructions but I know the update for this device had a root exploit patch. So can this be rooted yet? Obviously I know it can since there are ROMS for it but I can't do it with 2.3.4 for some reason. Any help would be appreciated....
Point the driver to \drivers\64 or 86
It will install the right one
Uncle Jimmy says hello
snandlal said:
Point the driver to \drivers\64 or 86
It will install the right one
Uncle Jimmy says hello
Click to expand...
Click to collapse
I don't think drivers are my problem. I can run adb and fastboot just fine, it just doesnt see my device unless I'm fully booted and with USB debugging on and run adb device. Other than that it wont see it to run fastboot oem unlock.
if do adb device on mine while in boot loader it doesnt see it....however fastboot oem unlock works fine....trust me the device can be rooted.
JimboKern said:
I don't think drivers are my problem. I can run adb and fastboot just fine, it just doesnt see my device unless I'm fully booted and with USB debugging on and run adb device. Other than that it wont see it to run fastboot oem unlock.
Click to expand...
Click to collapse
Have you booted into bootloader with volume up and power? if your drivers are right, it will find you for fastboot
Yes its in fastboot mode, it just doesnt see the device... However if I run the same command while fully booted adb devices it sees it, but in fastboot mode (volume up and power) I can't get it to see the device.
zikronix said:
if do adb device on mine while in boot loader it doesnt see it....however fastboot oem unlock works fine....trust me the device can be rooted.
Click to expand...
Click to collapse
How long does it take because I tried that but it just says waiting for device...
JimboKern said:
How long does it take because I tried that but it just says waiting for device...
Click to expand...
Click to collapse
your drivers are wrong. did you follow this tut?
http://forum.xda-developers.com/showthread.php?t=878786
what os are you on? 7 or xp or mac?
I gave everyone thanks! I was pointing to Evo drivers so all is well now!! Thanks guys!
JimboKern said:
I gave everyone thanks! I was pointing to Evo drivers so all is well now!! Thanks guys!
Click to expand...
Click to collapse
haha, glad you got it.
JimboKern said:
I gave everyone thanks! I was pointing to Evo drivers so all is well now!! Thanks guys!
Click to expand...
Click to collapse
Lol, you have double and triple check yourself as you root.
Sent from my Nexus S 4G using Tapatalk
mikeyinid said:
your drivers are wrong. did you follow this tut?
http://forum.xda-developers.com/showthread.php?t=878786
what os are you on? 7 or xp or mac?
Click to expand...
Click to collapse
Ya what he said. Your drivers are uncle jimmish
Uncle Jimmy says hello
snandlal said:
Ya what he said. Your drivers are uncle jimmish
Uncle Jimmy says hello
Click to expand...
Click to collapse
I dont know how I feel about uncle jim...
I had no problem rooting via fastboot after installing the PDANet drivers. Now if we could get some ROM love, we'LLC be all set.
Sent from my Nexus S 4G using XDA App
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 ?
I need help figuring this out. My phone pops up and recognizes my computer when it's on, but not when in bootloader mode. I'm trying to flash the new bootloader/radios, but I can't. I've already uninstalled and reinstalled google drivers via SDK. Any suggestions? Yes it responds properly when on when i type "adb devices" just not when in bootloader mode.
aval1392 said:
I need help figuring this out. My phone pops up and recognizes my computer when it's on, but not when in bootloader mode. I'm trying to flash the new bootloader/radios, but I can't. I've already uninstalled and reinstalled google drivers via SDK. Any suggestions? Yes it responds properly when on when i type "adb devices" just not when in bootloader mode.
Click to expand...
Click to collapse
Can you be a bit more clear on this? Adb doesn't work in bootloader mode, it isn't meant to, so if you're using adb commands while in the bootloader you're doing the wrong thing. What OS are you using? Exactly what command(s) are you issuing?
How about "fastboot devices"?
Heisenberg said:
Can you be a bit more clear on this? Adb doesn't work in bootloader mode, it isn't meant to, so if you're using adb commands while in the bootloader you're doing the wrong thing. What OS are you using? Exactly what command(s) are you issuing?
Click to expand...
Click to collapse
I figured it out. It took me a bit to realize adb doesn't work in bootloader. But I installed the correct drivers using max Lee's radio, bootloader, vendor flashing video if anyone needs in the future. Thanks for all you help with Heisenberg. https://www.youtube.com/watch?v=jwEJJIQEt3Y if anyone needs help like I did
aval1392 said:
I figured it out. It took me a bit to realize adb doesn't work in bootloader. But I installed the correct drivers using max Lee's radio, bootloader, vendor flashing video if anyone needs in the future. Thanks for all you help with Heisenberg. https://www.youtube.com/watch?v=jwEJJIQEt3Y if anyone needs help like I did
Click to expand...
Click to collapse
We already have a detailed guide right here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Hi!
First of all, I'm sorry for my English...
I have unlocked and rooted my device (Huawei P9 lite).
I have install the TWRP bootloader and I tried to install a new costum ROM, but my device was turned off and never opened again. (Maybe: Low battery).
I try to charge my device but it didn't recognize the charger. So, I removed the battery from device (with the help of a technician) and charging it.
After all, I tried again to root and install TWRP but the device doesn't open or recognized of my PC...the only thing to do is to be recognized by the PC in fastboot mode but not allowing me to do something in the command window.
What am I doing?
First of all....
What exactly did you try to flash? Which "custom ROM" are you talking about?
Schlengge said:
First of all....
What exactly did you try to flash? Which "custom ROM" are you talking about?
Click to expand...
Click to collapse
I download the costum ROM from here: http://forum.xda-developers.com/huawei-p9lite/development/dev-cyanogenmod-13-huawei-p9-lite-t3465612
Use <[DEV] VNS-L21-L22-L31 [EUROPE] Toolkit [0.0.0.8] Bootloader/Recovery/Root/Dual-Sim> and try again to da all from begining...
- check bootloader - lock/unlock
- flash stock recovery/twrp
- root it if is necessary
- copy update.app to SDcard into dload folder and try to reflash device.
I tired... but it didn't recognized my device!
Vangeliskar1 said:
I download the costum ROM from here: http://forum.xda-developers.com/huawei-p9lite/development/dev-cyanogenmod-13-huawei-p9-lite-t3465612
Click to expand...
Click to collapse
Okay so that is interesting.
Have you followed the exact instruction on the Website of Meticulus?
The CM Rom is HIGHLY alpha and cannot be flashed without a strict preparation.
Are you able to boot your phone into fastboot mode?
Schlengge said:
Okay so that is interesting.
Have you followed the exact instruction on the Website of Meticulus?
The CM Rom is HIGHLY alpha and cannot be flashed without a strict preparation.
Are you able to boot your phone into fastboot mode?
Click to expand...
Click to collapse
No...
I can't!
It doesn't work (Volume down + power key)
Vangeliskar1 said:
No...
I can't!
It doesn't work (Volume down + power key)
Click to expand...
Click to collapse
So the device does not respond in any way?
Hmm...
Maybe refer to the CM thread and hope that someone there can help you.
Don't know if Meticulus checks out this forum section.
You said: the only thing to do is to be recognized by the PC in fastboot mode but not allowing me to do something in the command window.
So, the device is recognized by PC in fastboot mode or not?
gtdaniel said:
You said: the only thing to do is to be recognized by the PC in fastboot mode but not allowing me to do something in the command window.
So, the device is recognized by PC in fastboot mode or not?
Click to expand...
Click to collapse
Maybe...I don't know!
I have this message:
C:\adb>fastboot devices
9JT0216627000650 fastboot
C:\adb>
Ok. Try to use this tool [DEV] VNS-L21-L22-L31 [EUROPE] Toolkit [0.0.0.8] Bootloader/Recovery/Root/Dual-Sim>
And tell here what appears to work or not...
gtdaniel said:
Ok. Try to use this tool [DEV] VNS-L21-L22-L31 [EUROPE] Toolkit [0.0.0.8] Bootloader/Recovery/Root/Dual-Sim>
And tell here what appears to work or not...
Click to expand...
Click to collapse
I had tried bu it doesn't work...
I have this massage:
Drivers on PC are installed right? Just to make sure...
May be I'm wrong, there is two options to active in develloper menu ? USB debug and OEM I don't know why ?
Excuse me if I'm off topic.
Schlengge said:
Drivers on PC are installed right? Just to make sure...
Click to expand...
Click to collapse
Yes everything is allright!
I have install and Hi suite!
Phone have any control? Reboot? Power?
When you conected to PC at Devices on PC appear something?
No...it is dead....
On PC: yes! It is apeared to devices
Ok! If appear in Devices is a chance to get it back to life...
It should be recognized in fastboot mode to... (where appears with serial number).
In that stage try that tool to see if is any information visible in status (model, serial number, build number etc)
gtdaniel said:
Ok! If appear in Devices is a chance to get it back to life...
It should be recognized in fastboot mode to... (where appears with serial number).
In that stage try that tool to see if is any information visible in status (model, serial number, build number etc)
Click to expand...
Click to collapse
It is apeared at devices with that name: android Bootloader Interface
Tool?
Which tooL?
In comand window?
That tool: VNS-L21-L22-L31 [EUROPE] Toolkit [0.0.0.8] Bootloader/Recovery/Root/Dual-Sim
You attached a image with phone in fastboot mode. Can you replicate again that stage?
In that stage use that tool and see if phone appear there.
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.