Hey guys, i'm new to the nexus world, i've had a Nexus 7 but I never rooted it.
I just got an LTE Nexus 9 and want to root it and flash TWRP. I'm using WinDroid. The problem is, i never get prompted to accept ADB permissions. Coming from a Samsung phone, when i check USB debugging, I automatically get a popup menu on my phone asking me with I want to give this PC permissions to use ADB. On my nexus 9, nothing happens. I see in Device manager that my nexus is connected under Android ADB Interface, and I know my drivers are installed, but WinDroid doesnt see my device, it's always offline.
Anybody know what could be the issue?
polish_pat said:
Hey guys, i'm new to the nexus world, i've had a Nexus 7 but I never rooted it.
I just got an LTE Nexus 9 and want to root it and flash TWRP. I'm using WinDroid. The problem is, i never get prompted to accept ADB permissions. Coming from a Samsung phone, when i check USB debugging, I automatically get a popup menu on my phone asking me with I want to give this PC permissions to use ADB. On my nexus 9, nothing happens. I see in Device manager that my nexus is connected under Android ADB Interface, and I know my drivers are installed, but WinDroid doesnt see my device, it's always offline.
Anybody know what could be the issue?
Click to expand...
Click to collapse
What is windroid? To root do this:
1. Enable developer options.
2. In developer options enable oem unlock
3. If you don't have fastboot set up on your pc Google 15 second adb install xda
4. Unlock your bootloader if it isn't already, fastboot oem unlock
5. Flash twrp onto your device, fastboot flash recovery twrp.img
6. Flash supersu in twrp
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
What is windroid? To root do this:
1. Enable developer options.
2. In developer options enable oem unlock
3. If you don't have fastboot set up on your pc Google 15 second adb install xda
4. Unlock your bootloader if it isn't already, fastboot oem unlock
5. Flash twrp onto your device, fastboot flash recovery twrp.img
6. Flash supersu in twrp
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Windroid is an easy to use universal toolkit. it basically automates the Unlock/root/recovery process. You can find more details here: http://forum.xda-developers.com/nexus-9/development/tool-windroid-universal-android-toolkit-t2984544
As for my issue, i have solved it checking in other threads, i have to set tablet to Camera USB mode, then it asks for RSA authentification right away. Thanks for your help anyways,
polish_pat said:
Windroid is an easy to use universal toolkit. it basically automates the Unlock/root/recovery process. You can find more details here: http://forum.xda-developers.com/nexus-9/development/tool-windroid-universal-android-toolkit-t2984544
As for my issue, i have solved it checking in other threads, i have to set tablet to Camera USB mode, then it asks for RSA authentification right away. Thanks for your help anyways,
Click to expand...
Click to collapse
Nah, I prefer to use fastboot. I can do it faster and I know what it's doing. Glad you got your device working though.
Sent from my Nexus 9 using XDA Free mobile app
My tool worked well for unlocking bootloader but it failed to install recovery and root, I think this might be because Platform Tools was not installed. I ended up doing it manually via command line. Worked perfect. Thanks for your input
Related
Hi,
the last days, I read a lot about flashing custom ROMs and wanted to do so with my HTC Legend. I'm not really new to flashing ROMs in general.I already flashed several other devices, but I'm stuck with unlocking the bootloader. My problem is, that the CMD is either reacting with "CommandError" or "waiting for device". I'm not able to get the token for unlocking the bootloader. Another problem is, that the SDK Manager won't start for me. So I just grabbed the 3 files out of the filesystem and tried it with them. Using HTCs recommended fastboot.exe doesn't change anything. I hope you can help me with a few details:
1. Do I have to install something else than HTC Sync? (I think, it already installed the driver, too)
2. Which connection mode should i choose, when connecting the legend? (recharging/hdd/htc sync/tethering)
3. Which version of the SDK should I use? Is it possible, that someone just gives me a zip with those 3 files?
I'm looking forward to your answers!
Regards
OdlG
SOLUTION:
The solution was a too old version. My phone had version 3.15.405.3.
First I updated to version 3.15.405.6 (found via google here at xda-dev).
Then I patched the new ROM I downloaded from htc-dev (step 0 at unlocking; must connect phone for that hint!) 3.30.0.0.
Then I could receive the token via CMD at a Windows 7 PC (Win8 PC still said "waiting for device", obviously because the driver wasn't installed correctly so the phone wasn't recognised in fastboot mode).
I followed the last steps rom htc-dev and now unlocked the bootloader
Click to expand...
Click to collapse
(pardon my english, it's not my mothertongue)
AW: Difficulties with unlocking the Bootloader
You should use charging mode and you have to activate usb debugging in settings
Sent from my HTC One using xda app-developers app
Thanks for the reply!
I already enbled USB Debugging, and now tried it in charging mode. I created a BAT-File with the following command:
cd C:\Android\
fastboot oem get_identifier_token
But it still says "waiting for device" Any suggestions?
Did you follow these instructions? especcially selecting "fastboot"?
http://www.htcdev.com/bootloader/unlock-instructions
if yes and it still didn't work i've no idea at the moment
I tried it once more:
I connected the phone, "fastboot usb" is written there. the cmd still writes "waiting for device". after a few seconds, the pc reports, that the usb device could not be recognised. then there is written "fastboot" instead of "fastboot usb", though the cable is still connected.
a few hours ago i also got a guide at htc dev, that i should install da RUU (what does it mean btw?). i downloaded the german vodafone version and tried to install it. I will try that once more, hopefully the unlock will be successful afterwards!
thanks for your advice!
EDIT:I'm using the following software btw.
Android SDK (adt-bundle-windows-x86_64-20130219)
Java RE 7 Update 17
HTC Sync (3.3.X or something like that)
The RUU installer is starting the setup without problems. It's rebooting the phone o install version 3.30 (hboot1.02). But when the Phone starts in the bootloader mode and displays "RUU", the PC is unable to detect the USB device and the setup fails caused by missing usb connection
Can I somehow influence the detection of the phone in fastboot/bootloader mode?
Normally it should be enough to install the HTC USB Drivers...
You can grab the newest for example from this thread: http://forum.xda-developers.com/showthread.php?t=2191279
The second what you need is an actual adb.exe, fastboot.exe, AdbWinApi.dll & AdbWinUsbApi.dll... grab it for example from here: http://d-h.st/RvD (Thanx to torxx (http://forum.xda-developers.com/member.php?u=3828647))
After u've installed the drivers and extracted the adb file do the folowing
Turn off your phone completly
Push Vol down & Power ...device will start
Navigate with vol+- to fastboot press power
connect with usb-cable (possible that windows will install drivers...wait till its complete)
now "fastboot usb" should be read in the display of your phone
open a shell (cmd)
navigate to your fastboot.exe
type: "fastboot oem get_identifier_token"
it seems, that my htc firmware is far too old (3.15.405.3). i installed all the stuff on my win7 laptop instead of win8 desktop pc and could install the RUU... at least untill the notification, that i needed to update the firmware first, and update hboot1.02 (3.30.0.0) afterwards. the big update is also 150MB, the small one only 5MB. i'll give it a try and report back here, if i am able to manage all the stuff^^
btw autoupdating via options doesn't work ("phone is up to date"). do i have to sign in via google to get a better result?
I managed to unlock the bootloader!
The solution was a too old version. My phone had version 3.15.405.3.
First I updated to version 3.15.405.6 (found via google here at xda-dev).
Then I patched the new ROM I downloaded from htc-dev (step 0 at unlocking; must connect phone for that hint!) 3.30.0.0.
Then I could receive the token via CMD at a Windows 7 PC (Win8 PC still said "waiting for device", obviously because the driver wasn't installed correctly so the phone wasn't recognised in fastboot mode).
I followed the last steps rom htc-dev and now unlocked the bootloader
now i will try the rest Thanks for the helpful hints!
AW: [solved] Difficulties with unlocking the Bootloader
Okay nice to hear that it now works:thumbup:
I would say... Have fun while flashing and trying new roms
Sent from my HTC One using xda app-developers app
esco27 said:
Okay nice to hear that it now works:thumbup:
I would say... Have fun while flashing and trying new roms
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Already flashed CM10.1 It's not as smooth as on my Ainol Aurora 2 Tablet, but the Legend hasn't got the power by far. But if you have a look at the specs, it is amazing, how good it runs on the legend
Thanks for all the help! That was definately worth it^^ I only have minor problems with my SIM-card up to now.
i messed up. i had cwm recovery rom running, but i did not install it. then i installed cyanogenmod. now recovery is cyanogenmod, but i want it to be cwm recovery. im stuck i dont know how to do what i want.
when i boot into recovery, i get cyanogenmod. adb and fastboot commands do not seem to be working. like i cant switch to fastboot via adb reboot bootloader. (no laughing please... is that because i flashed the custom rom???)
google play is not installed yet either because adb and fastboot isnt working like it was before i flashed cyanogenmod. i was going to try to download the cwm rom manager again to help me install (permanently) cwm recovery rom.
im so lost and a noobie, so details for replies please. and thank you for the help.
Its hard to give details in replies without details in your question, please give as much information about your device as possible, especially the make and model
But generally speaking fastboot will only work in bootloader and adb will only work in os and recovery mode
To give more specific answers on what your steps should be please give more device specifics
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Its hard to give details in replies without details in your question, please give as much information about your device as possible, especially the make and model
But generally speaking fastboot will only work in bootloader and adb will only work in os and recovery mode
To give more specific answers on what your steps should be please give more device specifics
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Motorola Droid Razr HD
bootloader unlocked
rooted
running CyanogenMod 10.2
wifi access
CWM Rom Manager not installed
Google Play not installed
Recovery ROM seems to be CyanogenMod
retalger said:
Motorola Droid Razr HD
bootloader unlocked
rooted
running CyanogenMod 10.2
wifi access
CWM Rom Manager not installed
Google Play not installed
Recovery ROM seems to be CyanogenMod
Click to expand...
Click to collapse
I don't believe cyanogen has made a recovery since the g1 days so I doubt you have this. But if your not sure what recovery you have upload a pic of it.
If you want a new recovery download the appropriate recovery for your device and use fastboot to install it, see here for help
http://forum.xda-developers.com/showthread.php?t=2277112
If you continue to have issues with adb or fastboot commands, post all input/output from cmd/terminal here
Sent from my Nexus 4 using XDA Premium 4 mobile app
Adb not working?
Make sure u have enabled debugging
Sent from my GT-S5570 using XDA Premium 4 mobile app
Faiyaz5yaz said:
Adb not working?
Make sure u have enabled debugging
Sent from my GT-S5570 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I BET THATS IT! i installed the custom rom, so debugging needs to be turned back on. the setting was overwritten with the new rom flash. duh! THANK YOU VERY MUCH!
for those of you coming to this thread after me, enable developer mode by going to Settings > About Phone and tapping on Build Number 7
Update: this did solve my problem/question. also watch cyanogenmod's screen. it will ask you to confirm debugging mode use each time or you can say its ok from this pc all the time. the latter worked best for me. another thing i ran into was phone would not power off unless i unplugged the usb cable. if i asked it to power off with the usb cable plugged in, it rebooted instead.
retalger said:
I BET THATS IT! i installed the custom rom, so debugging needs to be turned back on. the setting was overwritten with the new rom flash. duh! THANK YOU VERY MUCH!
for those of you coming to this thread after me, enable developer mode by going to Settings > About Phone and tapping on Build Number 7
Click to expand...
Click to collapse
Hit thanks if I helped u
Sent from my GT-S5570 using XDA Premium 4 mobile app
retalger said:
I BET THATS IT! i installed the custom rom, so debugging needs to be turned back on. the setting was overwritten with the new rom flash. duh! THANK YOU VERY MUCH!
for those of you coming to this thread after me, enable developer mode by going to Settings > About Phone and tapping on Build Number 7
Update: this did solve my problem/question. also watch cyanogenmod's screen. it will ask you to confirm debugging mode use each time or you can say its ok from this pc all the time. the latter worked best for me. another thing i ran into was phone would not power off unless i unplugged the usb cable. if i asked it to power off with the usb cable plugged in, it rebooted instead.
Click to expand...
Click to collapse
here's how i resolved my complete question:
1) enabled developer mode by going to Settings > About Phone and tapping on Build Number 7
2) activated advanced boot options by going to Settings > Developer Options > Advanced reboot (check it)
3) told phone to always allow debugging mode from my/this pc
4) booted into fastboot mode
5) plugged in usb cable
6) entered the command "adb reboot-bootloader" to switch to fastboot mode
7) entered the command "fastboot devices" to ensure i was in fastboot mode
8) entered the command "mfastboot flash recovery <downloaded.img>" to flash cwm
9) unplugged usb cable
10) reboot into recovery to verify flash was successful
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
osikiri said:
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
Click to expand...
Click to collapse
My watch is now bricked because I have no way to get out of "adb sideload" mode...how did you get out of that mode? please tell me.
TjPhysicist said:
My watch is now bricked because I have no way to get out of "adb sideload" mode...how did you get out of that mode? please tell me.
Click to expand...
Click to collapse
I pushed the reset button on the back(the silver one right above the charging connectors) with a pen for about 10 seconds, and it rebooted.
osikiri said:
I pushed the reset button on the back(the silver one right above the charging connectors) with a pen for about 10 seconds, and it rebooted.
Click to expand...
Click to collapse
Wow ok, that's a LOT longer than I'm used to with other devices...THANK GOD I thought I had bricked it completely.
Anyway, now i have to figure out a way to get adb to work in sideload,...i mean CLEARLY it's possible lots of others doing it..
---------- Post added at 08:26 AM ---------- Previous post was at 07:41 AM ----------
TjPhysicist said:
Wow ok, that's a LOT longer than I'm used to with other devices...THANK GOD I thought I had bricked it completely.
Anyway, now i have to figure out a way to get adb to work in sideload,...i mean CLEARLY it's possible lots of others doing it..
Click to expand...
Click to collapse
Ok, does anyone know how to get my computer to recognise my watch in recovery mode? It's not about 'driver' the computer plain doesn't recognise that anything is plugged in at all.
I know the post is quite old already, but I experience exactly the same phenomenon...
I tried multiple PCs Linux and Windows,but non of them recognized the watch (neither on 4.4W1 nor on 4.2W2).
Anyone any idea?
Wikiwix said:
I know the post is quite old already, but I experience exactly the same phenomenon...
I tried multiple PCs Linux and Windows,but non of them recognized the watch (neither on 4.4W1 nor on 4.2W2).
Anyone any idea?
Click to expand...
Click to collapse
I believe u need to update the drivers.....I always go-to device manager...update driver..hit select from list..and choose android adb....
Sent from my LGLS990 using XDA Free mobile app
mrkrabs said:
I believe u need to update the drivers.....I always go-to device manager...update driver..hit select from list..and choose android adb....
Sent from my LGLS990 using XDA Free mobile app
Click to expand...
Click to collapse
The problem, as @osikiri stated, is that the device does not get recognized at all (no unknown devices in devicemanager and the sound that comes on plugging in a device does not come as well). Furthermore, afaik Linux does not even need any drivers
Had the same issue today... and the only way out way battery death and recharge
JaceAlvejetti said:
Had the same issue today... and the only way out way battery death and recharge
Click to expand...
Click to collapse
If this really helps (seems weird): I guess the exact setting could be necassary:
You simply ran out of battery while the watch was running(not recovery or fastboot) and then plugged it in and went directly (or not?) to the recovery?
Thanks in advance, would be really great to fix this!
Anyone ever find a fix to this? I'm trying to manually install the 5.0 update and I'm having the same issue. Every post I find with search tells me to update drivers but I'm on a Mac that doesn't even use ADB drivers. I've updated the SDK.
MSigler said:
Anyone ever find a fix to this? I'm trying to manually install the 5.0 update and I'm having the same issue. Every post I find with search tells me to update drivers but I'm on a Mac that doesn't even use ADB drivers. I've updated the SDK.
Click to expand...
Click to collapse
I'm doing the same thing and having the same issues!
Yeah, same issue for me as described.
Windows (Win7 x64 for me) doesn't even realise that the device is connected when it is in recovery mode. Although it will connected properly when booted normally.
+1 Any ideas?
Same issue for me. I've tried removing and replacing it on the cradle, killing and restarting the adb server, entering recovery by the touchscreen or by the adb/fastboot commands, clearing debugging keys, etc... Anybody have any other ideas?
---------- Post added at 07:25 PM ---------- Previous post was at 06:46 PM ----------
Ok, so it appears that the recovery img on 4.4w2 broke adb support or something. There are a few threads that suggest you can root and flash it or just wait for the OTA. We'll see whether I get the OTA before I have time to try this out.
Lollipop OTA Update: Download and How-To (Root Required)
I made a script that roots and updates your watch to 5.0.1 in a click.
[UTILITY][RESTORE][UNLOCK][ROOT] LG G Watch Tool
My way of doing it
osikiri said:
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
Click to expand...
Click to collapse
I've similar problem, and I've spent almost 3 hours to find the solution. I found that following solution work for me:
http://forum.xda-developers.com/g-watch-r/development/manual-ota-update-root-t2969845
I've changed the step slightly according to the comments inside the thread:
- Enter Bootloader (swipe top left-bottom right as soon as the LG logo pops up on boot)
- Unlock bootloader (fastboot oem unlock) and boot the watch normally once
- Turn off and re-enter bootloader
- Flash 5.0.1 Stock Recovery (fastboot boot recovery.img)
// Do Not Flash 5.0.2 stock recovery
- Enter recovery and ADB sideload the update (tap the android, select install update from ADB and enter adb sideload filename.zip)
//you might have to reinstall the ADB drivers, just follow the simple step to install ADB driver
Done.
fi thought it was finally the solution, but fastboot oem unlock bricked my sony smartwatch3. I see tomorrow if with my windows pc i can fix with sony companion, otherwise i'll have to use the warranty
willisc said:
I've similar problem, and I've spent almost 3 hours to find the solution. I found that following solution work for me:
http://forum.xda-developers.com/g-watch-r/development/manual-ota-update-root-t2969845
I've changed the step slightly according to the comments inside the thread:
- Enter Bootloader (swipe top left-bottom right as soon as the LG logo pops up on boot)
- Unlock bootloader (fastboot oem unlock) and boot the watch normally once
- Turn off and re-enter bootloader
- Flash 5.0.1 Stock Recovery (fastboot boot recovery.img)
// Do Not Flash 5.0.2 stock recovery
- Enter recovery and ADB sideload the update (tap the android, select install update from ADB and enter adb sideload filename.zip)
//you might have to reinstall the ADB drivers, just follow the simple step to install ADB driver
Done.
Click to expand...
Click to collapse
Hi,
I got my Nexus 9 around launch date and used Wugs toolkit to unlock bootloader, root and install teamwin recovery.
I kept gettting OTA updates for 5.0.2 but they wouldn't install. After months of ignoring I thought I'd update.
It wouldn't update so I tried to use Wugs toolkit to 'Flash stock + unroot to latest version'.
This failed saying something about no fastboot device, although the device went to the white screen and seemed to be displaying hboot/fastboot as options...
I got frustrated and used TWRP to wipe everything, including the OS!
I'm used to Samsung so expected an Odin type program to flash over my mess... I can't seem to do anything now.
HELP! (Please!)
A reason I don't like tool kits. If they don't work as expected you have no idea what to do next. Follow the long method of this, http://forum.xda-developers.com/showthread.php?p=58956577
Sent from my Nexus 9 using XDA Free mobile app
Appreciate the reply but I can't enable anything within the device as there is no OS installed...
I have used vol down and power to select fastboot.... Is this "Boot your device into the bootloader" in your guide?
All I get is waiting for device in the cmd window
thanks
jotan said:
Appreciate the reply but I can't enable anything within the device as there is no OS installed...
I have used vol down and power to select fastboot.... Is this "Boot your device into the bootloader" in your guide?
All I get is waiting for device in the cmd window
thanks
Click to expand...
Click to collapse
Vol down and power does bring you into the bootloader. Do you have usb drivers setup? Go into device manager on your pc with the device connected. Do you have an icon with a yellow exclamation mark? If so right click on it and go to where you can choose a driver from a list on your computer. Choose Android adb composite interface.
Sent from my Nexus 9 using XDA Free mobile app
Sorry about the late reply, been on my honeymoon! For some reason it just wouldn't work on my PC, so I used my laptop and all was well.
Thanks.
Thread closed!
Hey everyone. Today I've finally unbricked my Zenfone 7 after my dumbass locked the oem with fastboot since I've already rooted my phone and didn't want to use adb anymore (I was getting tired of the warranty voided message at boot too). Right after locking the oem, the phone booted and displayed a message that says: " Your device is corrupted. It cannot be trusted and won't boot". You already could tell I was scared as hell, so all I did the past hours was to look around until I found this solution!
Have in mind I'm not an expert or a developer, I'm only hoping you find this thread if you ever find yourself locked in fastboot with no access to recovery, oem, adb or usb debugging, just fastboot commands.
Having said that, you need to flash the raw firmware for your device. For the Zenfone 7 the one you need is "WW__ZS670KS_29.14.53.5_MR1.3_20201111_release-user.raw".
You also need:
- Android sdk and platform tools (minimal adb works too but I recommend original google software)
- Usb asus drivers
- Usb google drivers (installable from android studio just like sdk and platform tools)
Turn on your device on fastboot and connect it to your pc, then open cmd or powershell on your platform-tools folder and execute
Code:
fastboot devices
to check if your zenfone is detected. Close the command prompt.
Now, on the raw rom folder open flashall_AFT.cmd as administrator, then it should start flashing all of the stock firmware files. Once the prompt closes itself, reboot your phone using volume keys and power button to select.
In my case, right after booting, the phone displayed a message that said "your phone is corrupted" but with a wipe data option this time around. Choose wipe data/factory reset (all your data will be gone).
There you go! The phone should reboot into stock clean rom now.
I get Flashing is not allowed in Lock State
RickJF said:
I get Flashing is not allowed in Lock State
Click to expand...
Click to collapse
did you unlock bootloader?
IronSingh said:
did you unlock bootloader?
Click to expand...
Click to collapse
No, to do so I need go get into developer tools,
wich I can't because android won't boot
[ROM][OFFICIAL] Omnirom for zenfone7/7pro [Android-13.0]
What is Omnirom ? Selinux Status: Enforcing Instructions : Follow this Steps by steps You need to be lastest firmware on both slots Please. How to have lastest FW on both slots: Reboot twrp Flash stock + twrp on opposite reboot recovery do...
forum.xda-developers.com
RickJF said:
No, to do so I need go get into developer tools,
wich I can't because android won't boot
Click to expand...
Click to collapse
RickJF said:
I get Flashing is not allowed in Lock State
Click to expand...
Click to collapse
How strange, you shouldn't need OEM unlock to flash the raw rom. Hope you get through it... meanwhile I'll let you know if I find a possible solution
tommydotwav said:
How strange, you shouldn't need OEM unlock to flash the raw rom. Hope you get through it... meanwhile I'll let you know if I find a possible solution
Click to expand...
Click to collapse
What is the problem?
tommydotwav said:
How strange, you shouldn't need OEM unlock to flash the raw rom. Hope you get through it... meanwhile I'll let you know if I find a possible solution
Click to expand...
Click to collapse
thanks, I've searched enough and tried it all, sent ticket to Asus support,
they say considering all that it's probably physically corrupted,
nothing much I can do at home
RickJF said:
thanks, I've searched enough and tried it all, sent ticket to Asus support,
they say considering all that it's probably physically corrupted,
nothing much I can do at home
Click to expand...
Click to collapse
DM me, make sure you are able to do test Point, we can fix it via EDL