My niece, who is adorably four, has created some serious problems for me. She was playing with my phone and set a PIN- I have no idea what the pin is, and it doesn't seem like there's an alternative way to get into the phone. When I deliberately get it wrong a bunch of times it doesn't offer me the ability to sign in with my google account, and it's currently in airplane mode (which I can't do anything about)
I'm totally fine with wiping and starting fresh, everything's backed up anyway, but for some reason I can't?
Things I've tried:
-putting in a series of PINs hoping it would let me log in with my google account, no go
-rebooting with hardware keys to fastboot/hboot, and using factory reset from there. The screen goes blank, sometimes it loads a phone with a single red triangle and exclamation point, but it doesn't wipe
-booting into the stock android recovery and using wipe data/factory reset. The system recovery says it's KOT49H, when I hit wipe data/factory reset I get options including 'yes- delete all user data' which backs up and restores 'data preload' and 'cw package' and 'yes- back-up phone settings' which says it completes, but I end up at the PIN screen again
-installing a RUU zip from here: http://forum.xda-developers.com/showthread.php?t=2757462 It installs the 1.58.502.1 just fine, but doesn't wipe the device. When I try the 2.23.503 it gives me a series of 'fail-pu' errors and doesn't install
-unlocking the bootloader via fastboot-usb. I submit the token, get the screen asking me to confirm that I want to unlock the bootloader, then the phone boots normally. No wipe, no unlock.
-I don't think I can run an actual RUU, because I can't unlock the screen. RebootRUU just restarts the phone normally for some reason.
I'm obviously just about out of my mind, am I missing something obvious?
When I go to the bootloader, it says
*** LOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.16.0.000
RADIO-1.12.21331931.LA11G
OpenDSP-V38.2.2-00542-M8974.0311
OS-1.58.502.1
eMMC-BOOT 2048MB
Apr 18 2014,16:06:33.0
I got the phone used a few months ago and never had any issues; I've never done any dev stuff with it (but I probably should have, to head this stuff off! Lesson learned)
I'm fairly sure fastboot is on, and USB debugging is not on. My head hurts from staring sadly at my phone, please help XDA!
Wowww, your niece really painted you into a tight corner.
Did you try to run an RUU executable? I wouldn't think the screen lock would matter.
redpoint73 said:
Wowww, your niece really painted you into a tight corner.
Did you try to run an RUU executable? I wouldn't think the screen lock would matter.
Click to expand...
Click to collapse
Sure did! And she's probably my favorite person in the world, but today I'm a little grouchy. :/
I ran the RUU executable and it recognized the phone in fastboot-usb, but when it tries to reboot to bootloader it just reboots normally and then gives me a usb-170 connection error.
I appreciate the idea very much!
grumpus said:
Sure did! And she's probably my favorite person in the world, but today I'm a little grouchy. :/
I ran the RUU executable and it recognized the phone in fastboot-usb, but when it tries to reboot to bootloader it just reboots normally and then gives me a usb-170 connection error.
I appreciate the idea very much!
Click to expand...
Click to collapse
You have HTC Sync installed on the computer?
Try a different USB port, different cable, make sure you aren't plugged into any USB hub.
Also, is the port USB 3.0? I've seen this cause some issues.
redpoint73 said:
You have HTC Sync installed on the computer?
Try a different USB port, different cable, make sure you aren't plugged into any USB hub.
Also, is the port USB 3.0? I've seen this cause some issues.
Click to expand...
Click to collapse
Got optimistic for a second because I hadn't tried multiple cables, but now I've tried three cables on two computes on nine total ports and gotten the same thing. I installed HTC Sync (hadn't been using it before) and the associated drivers. It'll still recognize and start the update in fastboot (but then when it tries to reboot to bootloader it instead reboots the entire phone)
I'm completely baffled.
Can you fastboot flash TWRP and boot into custom recovery?
If you can I have a link to a forum over in the Nexus 5 section that states his lockscreen fixer zip should work with any kit Kat or jellybean android .
http://forum.xda-developers.com/goo...flash-zip-bypass-nexus-5-lock-screen-t2781247
At least worth a shot if you can get into a custom recovery
AT&T HTC ONE M8
Isn't there an option to reset pin via your google account? I can't remember off the top of my head.
-Sent from a payphone...
jball said:
Can you fastboot flash TWRP and boot into custom recovery?
If you can I have a link to a forum over in the Nexus 5 section that states his lockscreen fixer zip should work with any kit Kat or jellybean android .
http://forum.xda-developers.com/goo...flash-zip-bypass-nexus-5-lock-screen-t2781247
At least worth a shot if you can get into a custom recovery
Click to expand...
Click to collapse
He can't unlock the bootloader, and unfortunately you can't flash custom recovery with a locked bootloader.
But good ideas. Any brainstorming is appreciated at this point, as I've completely run out of ideas.
I would not think that PIN lock would lock out so many things, especially RUU.
@grumpus
I don't give up on anything very easily so I've found these and the website I got the screenshots from
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://android.stackexchange.com/qu...android-device-as-have-no-internet-connection
I'll keep looking
AT&T HTC ONE M8
---------- Post added at 10:44 PM ---------- Previous post was at 10:30 PM ----------
[/COLOR @grumpus
http://theunlockr.com/2012/04/19/how-to-access-an-android-device-if-you-forget-your-pattern-or-pin/
Go for the "screen lock" #2 method for below link
http://joyofandroid.com/how-to-unlock-android-phone/
AT&T HTC ONE M8
Wow, a RUU.exe won't solve it, that's amazingly strange. It was my first suggestion until I re-read the post. I think it's 10 wrong pin entries and it will reset itself if it's stock.
Post if you fixed it or not OP
AT&T HTC ONE M8
Related
http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+Prime+TF201&p=20&s=16
Direct ASUS link
Direct apk link (dropbox)
Mediafire, in case dropbox gets killed.
md5 of the file than unlocked my bootloader: af305839d357431a4f1505f96b62d48d
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
They were a tad quiet about that. So much for a press release or anything.
I feel sodomized now...
This is a load of legal BS, which is only to benefit one party (ASUS). I wonder if such one-sided contracts will even stand up in court...
Great news !!!!
This future certainly looks bright !!
Bring on the Roms etc.
unlocking success XD now booting up it only takes a few seconds...
Finally! I really hope this will kickstart development.
strange recovery... only had a look for a few seconds as there is a timecounter in the background, but there is an option to install linux , mnt usb? maybe with FS? and to wipe (I don't want to press the button). I think it checked up the internal storage for some special files, like bootloader in htc for the pd**.img
Basically this unlocker grabs the serial of the CPU, tells the Asus server... Gets back the necessary info to unlock, unlocks the device and leave a marker for warranty thrashing (It mentions some sort of flag), then reboots.
Edit:If anyone was wondering, the serial of the cpu would be independent of the device serial (In format 0245xxxxxxxxxxxx) is acquired from /proc/cpuinfo
Edit2:I believe the unlock server is mdm.asus.com via HTTPS, also I believe it uses the Android device ID as well.
More Info!!! Thanks
couldn't someone just make a app, that does all this, except tell the asus sever our cpu number?
that way they would still think we havent unlocked it?
this is great news, the only problem i see is not being able to recieve OTA anymore. i am sure a dev will figure out a way to get us unlocked primes a way to install/flash them.
This is good to know and I will be keeping an eye out for any results that the community has using it. However, I won't be downloading/installing the tool because my Prime has not been rooted or gone backwards with ICS versions. I want to go the official update route for awhile yet. This is just a personal preference. I have too much money tied up in this unit to void the warranty.
Ramis93 said:
couldn't someone just make a app, that does all this, except tell the asus sever our cpu number?
that way they would still think we havent unlocked it?
Click to expand...
Click to collapse
It's a challenge-response thing with the challenge built from the cpu serial and device id (or one of those, or more... Didn't take a close look). Only Asus and the person in possession of the device would know these.
Also they're not stupid enough to just let you throw unlock requests at them without recording them. (After all they do have to look up the keys to unlock the bootloader)
Also they're probably wiping the DRM keys on the device as well, so devs don't go extracting them after they've unlocked their bootloaders.
neckbonest said:
this is great news, the only problem i see is not being able to recieve OTA anymore. i am sure a dev will figure out a way to get us unlocked primes a way to install/flash them.
Click to expand...
Click to collapse
DD'ing blobs *should* work still, although YMMV.
nice! now let's hope for a good recovery and custom roms!
As much as I want to use this I'm not going too. Don't want to lose my warranty as I dont trust this device with the amount of problems that surround it so far. Also wont get OTA updates. Asus know how to screw over there buyers, should of been unlocked before release.
Hm, did anyone get fastboot to work? For me it stays for ever at the line "Starting Fastboot USB download protocol"
Does it wipe the device?
joeyddr said:
Does it wipe the device?
Click to expand...
Click to collapse
No. It just does some stuff and reboots.
Diamondback said:
No. It just does some stuff and reboots.
Click to expand...
Click to collapse
Any chance of a pic of the recovery?
barryflanagan said:
Any chance of a pic of the recovery?
Click to expand...
Click to collapse
There is not really a usable recovery. Only the OTA one which just shows you an error once you start it. (Because there is no OTA file to apply)
Once booting with VOL_DOWN you can choose between a cold boot, wiping data or entering fastboot mode (which does not really seem to work for me)
Hi all,
I just purchased a HTC Rezound (used). Clean ESN, I have it activated and working fine. It is running the most recent official OTA build from Verizon (last January I believe).
Strangely, I am not able to perform a factory reset on the device to get it back to stock from the previous user. I have tried via the settings menu, and I have tried via the hard reset (power btn + Vol down), neither work. The device just reboots as usual.
I see at the top of the device (when rebooting using hard reset keys) it says it is unlocked, and S-ON. Go easy on me as I am still trying to learn what I will need to do to eventually put ROM's on this device - but anyone have any clues why I can't perform a simply hard reset and succeed? Thanks!
Dunno what the exact state of the kernel, ROM, etc. is since it is unlocked, perhaps something about that phone's configuration causes it to fail. Try running a RUU just to take all the guesswork out of what the previous owner did to that thing, here is the GB OTA thanks to con247: http://forum.xda-developers.com/showthread.php?p=22045045
Thank you - does this information give any clues?
Here's what I see:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
that doesnt really help but you should definitely run the RUU it will reset everything
next
Hi, You will want to read all the great info here on xda about HTC Lock and Unlock. Your goal is to use adb and flash to re-lock it. After it's relocked,
you can run an exe called RUU when it's connected to a computer. I'd recommend using the 2.01.605.11. It will fix all woes, including your ability to
do a reset on it. It's their best Gingerbread version, and compatible with your system.
After you do the RUU, you will be ready for the new ICS coming out SOOOON.
Yeah, that is on the same build as OTA, may be a custom ROM still, Factory Reset should wipe all RAM data if it is indeed on a stock ROM fine, hmm. Check Settings > Power and make sure Fast Boot is deselected, that may interfere with the reboot process while it resets. Other than checking the recovery in that boot menu you posted for a custom recovery with options there to wipe and reset, try a RUU still is all I got, haha.
michaelbsheldon said:
Hi, You will want to read all the great info here on xda about HTC Lock and Unlock. Your goal is to use adb and flash to re-lock it. After it's relocked,
you can run an exe called RUU when it's connected to a computer. I'd recommend using the 2.01.605.11. It will fix all woes, including your ability to
do a reset on it. It's their best Gingerbread version, and compatible with your system.
After you do the RUU, you will be ready for the new ICS coming out SOOOON.
Click to expand...
Click to collapse
actually you do not to relock before running a RUU
PhantasmRezound said:
Yeah, that is on the same build as OTA, mag be a custom ROM still, Factory Reset should wipe all RAM data if it is indeed on a stock ROM fine, hmm. Check Settings > Power and make sure Fast Boot is deselected, that may interfere with the reboot process while it resets. Other than checking the recovery in that boot menu you posted for a custom recovery with options there to wipe and reset, try a RUU still is all I got, haha.
Click to expand...
Click to collapse
that would be an option but it would be easier if he reset with an RUU and then learned everything else about modding and flashing himself rather than have it installed for him
Oh yeah, RUU is definitely easier and learning all the info here in XDA is recommended (should be mandatory for all modding and modded phone owners.) But checking those things are quick solutions to try while waiting for a quarter to a half a gig of RUU data to download lol. I have limited connection speeds and always think laterally while troubleshooting.
Po1soNNN said:
actually you do not to relock before running a RUU
Click to expand...
Click to collapse
Yes you most certainly do. He has s-on so he has to relock.
yep he needs to relock and run ruu since he is s-on
Just to follow up -thank you everyone for helping me get started and solve the problem.
I re-locked and applied the suggested RUU in this thread - all is good now!
THanks!
So I have my new HOX+ (AT&T). I got it boot unlocked, perma rooted...and the first thing i tried to modify was the fonts using the "font installer" app. Well this turned into a fiasco. it installed the font...showed a whole string of *insert Asian language characters here* on the status bar, went into a reboot...and never came back again. It boots to the White HTC splash screen, and just hangs.
At this point, I can reboot into TWRP recovery...but for whatever reason....my recovery isn't present. I don't know what i screwed up...but it isn't there. So I wiped everything...now I need an OS. Preferably a factory ROM....but I don't think anything exists yet for the AT&T model. And how can I get it on the phone!? I come from a world of GS3, where Odin could save the day...
Can anyone help me out/point me the right way?
arminyack said:
So I have my new HOX+ (AT&T). I got it boot unlocked, perma rooted...and the first thing i tried to modify was the fonts using the "font installer" app. Well this turned into a fiasco. it installed the font...showed a whole string of *insert Asian language characters here* on the status bar, went into a reboot...and never came back again. It boots to the White HTC splash screen, and just hangs.
At this point, I can reboot into TWRP recovery...but for whatever reason....my recovery isn't present. I don't know what i screwed up...but it isn't there. So I wiped everything...now I need an OS. Preferably a factory ROM....but I don't think anything exists yet for the AT&T model. And how can I get it on the phone!? I come from a world of GS3, where Odin could save the day...
Can anyone help me out/point me the right way?
Click to expand...
Click to collapse
dang...no one!
I can USB mount the phone within TWRP..but when it shows up as a drive on my comp, clicking on it yields a "please insert a disk" message...
Wish I could help. I know how much your situation sucks. It's one of the drawbacks of hacking our device. The carrier or company will obviously not help since its our fault. Hopefully you got it working by now.
Sent from my iPhone using Tapatalk
davidstech11 said:
Wish I could help. I know how much your situation sucks. It's one of the drawbacks of hacking our device. The carrier or company will obviously not help since its our fault. Hopefully you got it working by now.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Still "softbricked".
I cant get my machine to recognize the device when it is on TWRP with the storage mounted, so I cannot get a zip file on it to do anything.
This is what I get when I launch into TWRP with the device plugged into my comp.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So the device wont appear under "My Computer", therefore I cannot copy any .zip file to the device, therefore, its a brick.
arminyack said:
This is what I get when I launch into TWRP with the device plugged into my comp.
So the device wont appear under "My Computer", therefore I cannot copy any .zip file to the device, therefore, its a brick.
Click to expand...
Click to collapse
I just tried adb pushing maXimusATT_1.0.0zip to my phone (sucess!) and then flashed that successfully...then rebooted.....abd I'm still boot looped!!!!:crying:
arminyack said:
I just tried adb pushing maXimusATT_1.0.0zip to my phone (sucess!) and then flashed that successfully...then rebooted.....abd I'm still boot looped!!!!:crying:
Click to expand...
Click to collapse
UPDATE I redid it, and this time, remembered to flash the image file first, THEN install the .zip.
sucess!!!!
Wow... glad you got it fixed, but sorry that no one was apparently around to help you out today. In the future, you can also flash the RUU file to return to stock.
http://d-h.st/users/hasoon2000/?fld_id=7650#files
I bet you were happy. lol. I know I would be after all that. So, are you going to flash and change more things around? lol.
Sent from my iPhone using Tapatalk
davidstech11 said:
I bet you were happy. lol. I know I would be after all that. So, are you going to flash and change more things around? lol.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Being that I usually cant leave well enough alone...that will happen soon enough! I just gotta make sure I have a recovery available next time!
I was runing 4.2 with MKD build number, tried to update via ODIN to 4.3.3 with his flash image
http://forum.xda-developers.com/showthread.php?p=47011336
Odin gets me this error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After that, i got this message on my phone screen
"firmware upgrade encountered error
please select recovery mode in kies and try again"
I cant get into Download or Recovery mod... or power on the phone!
When i conect it to my pc it reads it like "QHUSB DLOAD"
I instaled the QHUSB DLOAD drivers and the pc recognize it like Qualcom HS-USB QDLoader 9008(COM5)
Odin reads it also (COM5) but i cant reflash it because i cant get into Download mode
H E L P !
ANYONE ? Cmon please.... any ides, tips help ?
AnajaDroid said:
ANYONE ? Cmon please.... any ides, tips help ?
Click to expand...
Click to collapse
If you can't boot it into recovery, it's pretty much bricked. Look around for people offering to JTAG it to recover.
Before I consider helping you, why on earth would you attempt flashing this? Why not instead flash a 4.3 rom? I have to know you were intentionally trying to lock your bootloader before I try to help....it just feels so wrong giving instructions for locking a bootloader
---------- Post added at 06:44 PM ---------- Previous post was at 06:39 PM ----------
k1mu said:
If you can't boot it into recovery, it's pretty much bricked. Look around for people offering to JTAG it to recover.
Click to expand...
Click to collapse
I bet it would still get into download mode since aboot wasnt flashed, well I guess it depends on whether or not the phone even attempts to boot or not though. I've gotten my S4 out of qhusb by keep the charger plugged in and constantly removing and inserting the battery.
Surge1223 said:
I bet it would still get into download mode since aboot wasnt flashed, well I guess it depends on whether or not the phone even attempts to boot or not though. I've gotten my S4 out of qhusb by keep the charger plugged in and constantly removing and inserting the battery.
Click to expand...
Click to collapse
Very likely. It's pretty hard to brick this phone into a state where it can't be recovered.
However, I've seen people do amazing things like flashing GS3 ROMs and wondering why they didn't work. Or less crazy, flashing AT&T ROMs on a VZ phone. People that stupid are why Verizon is so anal about locking down their phones.
I was just trying to update it to 4.3 since OTA didnt work I taught this was stock odin flashable image...
AnajaDroid said:
I was just trying to update it to 4.3 since OTA didnt work I taught this was stock odin flashable image...
Click to expand...
Click to collapse
Stock mean locked boot loader!!
What USB cable did you use and what port on the computer? While it's a bit of a stupid question I had a problem like that when doing an ODIN restore and tried all kinds of fixes including a totally different computer and it turns out the USB cable I was using was crap even though it'd transfer files over fine, ODIN didn't like it.
If you can't get it out of QHUSB DLOAD with button pressing, you can try this tool http://forum.legija.net/showthread....g-galaxy-S4-(i9505-and-similar)-via-USB-Cable.
LemonSlice said:
What USB cable did you use and what port on the computer? While it's a bit of a stupid question I had a problem like that when doing an ODIN restore and tried all kinds of fixes including a totally different computer and it turns out the USB cable I was using was crap even though it'd transfer files over fine, ODIN didn't like it.
If you can't get it out of QHUSB DLOAD with button pressing, you can try this tool http://forum.legija.net/showthread....g-galaxy-S4-(i9505-and-similar)-via-USB-Cable.
Click to expand...
Click to collapse
It was COM3 port, and it was OEM samsung usb cable...
I Tried everything i can but there is no way to get into download/recovery mod...
I had a similar problem the other day, don't worry. Depending on whatever build you were on before you bricked it, download that baseband and odin it on there. It did wonders for me and should work for you.
Solved... The device was hardbricked.... JTAG did the trick, cost me about 35$
Hi there! I need some help, I am trying to root my device and need a boot.img, but I cannot find a Rom for the x9 anywhere online.
This is my first time doing this, I got this phone just to mess around with rooting. But maybe I bought a bad phone for it.
If there are no Flash Roms online, what are the next steps? Can I use a Rom for the e9 which released alongside this phone? Sounds like it wouldnt work.. but IDK.
Looking for help from the experts ^^
Any help is appreciated.
Finally found one! Took over 2 hours to download a 2gb file O,O but it's finally done.
Now I am having problems getting into bootloader mode.
In developer mode with both OEM unlocking and USB debugging enabled.
Used the correct cmd prompt (adb reboot bootloader) but the phone just restarts.
I've tried restarting while holding the volume buttons.
VOL Down = Factory Test Mode, nothing works as expected there.
VOL UP = A boot menu letting me select from ~10 options, one of them is Boot to Bootloader. Selecting that simply boots normal, nothing special.
I have followed three guides:
How TO Root Vodafone Smart X9 Magisk without TWRP Recovery
If your Smart X9 is rooted using Magisk without TWRP Recovery. You can control a lot of features such as you can remove unwanted software.
www.getdroidpro.com
Vodafone Smart E9 Unlock Bootloader with Fastboot Method
How to unlock bootloader on your Vodafone with Fastboot Method. You can install custom ROM, custom recovery, kernel, flash all data
www.mobilewithdrivers.com
All seem logical enough, many similarities between them. I just cannot get into fastboot mode.
I've seen LOADS of threads with this same problem on this forum. And none of them have any solutions. So I think this is the end of the road. If nobody has figured it out .. then I am just out of luck I guess?
HalpNeeded said:
Forget, your phone have only 3 buttons
Click to expand...
Click to collapse
Hi @joke19 !
I havnt seen any of the guides mentioning needing a certain amount of buttons :O
How does that factor in - does that mean it cannot be rooted for some reason?
Still having this problem, and I have followed a lot of guides to the letter. I cant see what I am doing wrong. Here's where I am:
Phone is visible on device manager and the drivers are up-to-date.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PC is fully up to date on Windows 10.
I've got the lastest up-to-date version of platform-tools.
I'm using USB2.0 with the correct wires.
The phone is in developer mode with USB Debugging and OEM unlocking enabled.
I'm using the correct command lines. adb devices & adb reboot bootloader work as expected.
But none of these will work: fastboot devices, fastboot flashing unlock, fastboot oem unlock.
I just get < waiting for any device >
Can anyone help figure this out? I must be doing sooomething wrong. Everything online says its a driver issue, but then again, all the guides on how to fix that driver issue have been followed and completed. The first bullet with the image should also sort of verify that.
Praying some wizard out there has the knowledge I need to get this working! ^^
HalpNeeded said:
Still having this problem, and I have followed a lot of guides to the letter. I cant see what I am doing wrong. Here's where I am:
Phone is visible on device manager and the drivers are up-to-date.
View attachment 5671635
PC is fully up to date on Windows 10.
I've got the lastest up-to-date version of platform-tools.
I'm using USB2.0 with the correct wires.
The phone is in developer mode with USB Debugging and OEM unlocking enabled.
I'm using the correct command lines. adb devices & adb reboot bootloader work as expected.
But none of these will work: fastboot devices, fastboot flashing unlock, fastboot oem unlock.
I just get < waiting for any device >
Can anyone help figure this out? I must be doing sooomething wrong. Everything online says its a driver issue, but then again, all the guides on how to fix that driver issue have been followed and completed. The first bullet with the image should also sort of verify that.
Praying some wizard out there has the knowledge I need to get this working! ^^
Click to expand...
Click to collapse
did you manage to get this working?