Hello everyone.
I've got Samsung Galaxy s9+ and I forgot the pattern. I would like to unlock it without losing the data, what is important for me is the photos and videos. I've tried every method on youtube but unfortunately none is working. I bought several programs like Dr.Fone and 4ukey but they don't support this model. Is there anyway to unlock it without Factory Reset? I'm willing to pay for this.
Thank you
If you can get it into fastboot, you can copy the files to your pc using adb and some commands.
Look for a tutorial on this
PhotonIce said:
If you can get it into fastboot, you can copy the files to your pc using adb and some commands.
Look for a tutorial on this
Click to expand...
Click to collapse
Thank you for your reply. is fastboot same as recovery mood? sorry but I'm so noob in tech
Get the android studio adb tools zip, unzip it. Install fastboot and normal drivers for your phone. Enter adb, plug in your phone using a data cable. Now, type adb devices. Boot your phone into recovery mode first, your device should show up. If it doesn't, then once in recovery mode, there should be an option to enter fastboot. Select that. If your device still won't appear, try entering download mode (I think download mode is the one you should try first).
Once your device appears in the adb command window, google the command for copying files using adb. Use this command to copy all the files to either an sd card inserted in the phone, or directly onto your pc (if possible).
If none of this is working out for you, and you are willing to pay, take it to a data recovery shop/centre. They should be able to extract the data from the device at a reasonable price.
PhotonIce said:
Get the android studio adb tools zip, unzip it. Install fastboot and normal drivers for your phone. Enter adb, plug in your phone using a data cable. Now, type adb devices. Boot your phone into recovery mode first, your device should show up. If it doesn't, then once in recovery mode, there should be an option to enter fastboot. Select that. If your device still won't appear, try entering download mode (I think download mode is the one you should try first).
Once your device appears in the adb command window, google the command for copying files using adb. Use this command to copy all the files to either an sd card inserted in the phone, or directly onto your pc (if possible).
If none of this is working out for you, and you are willing to pay, take it to a data recovery shop/centre. They should be able to extract the data from the device at a reasonable price.
Click to expand...
Click to collapse
I'm speechless for your kind help. I'll try to do all these steps.
I tried to search for "android studio adb tools" but I can't find it's download link. Sorry, but can you please to share me download link for the zip file, I'll really appreciate that so much, then I'll follow your steps.
I took the phone to several phone shops but they couldn't do it. They just telling me they can factory reset which I can do it but I don't want to lose the photos and videos.
Once again, Thank you so much
Here's the link, (sorry, its called platform tools not adb tools, my bad).
Downloading Platform Tools…
Get the Platform Tools to discharge the ADB and fastboot commands that permit the users to perform several incredible benefits and unlock the system settings
magiskupdate.com
Try taking the phone to a data recovery shop, instead of some regular phone/repair shop.
pickasfu said:
Hello everyone.
I've got Samsung Galaxy s9+ and I forgot the pattern. I would like to unlock it without losing the data, what is important for me is the photos and videos. I've tried every method on youtube but unfortunately none is working. I bought several programs like Dr.Fone and 4ukey but they don't support this model. Is there anyway to unlock it without Factory Reset? I'm willing to pay for this.
Thank you
Click to expand...
Click to collapse
Doesn't the S9+ have a fingerpritn reader though? Just use that to unlock it..
PhotonIce said:
Here's the link, (sorry, its called platform tools not adb tools, my bad).
Downloading Platform Tools…
Get the Platform Tools to discharge the ADB and fastboot commands that permit the users to perform several incredible benefits and unlock the system settings
magiskupdate.com
Try taking the phone to a data recovery shop, instead of some regular phone/repair shop.
Click to expand...
Click to collapse
Thank you for your reply. I'll try this method and let's hope it will success, I'll keep you updated.
===
There are several data recovery shops I contacted after your advice, but unfortunately they deal with laptops, external memory cards and hard drives.
PhotonIce said:
Doesn't the S9+ have a fingerpritn reader though? Just use that to unlock it..
Click to expand...
Click to collapse
It does. But if device restarted you are forced to enter the pattern or the password and there will be no option for fingerprints.
PhotonIce said:
Get the android studio adb tools zip, unzip it. Install fastboot and normal drivers for your phone. Enter adb, plug in your phone using a data cable. Now, type adb devices. Boot your phone into recovery mode first, your device should show up. If it doesn't, then once in recovery mode, there should be an option to enter fastboot. Select that. If your device still won't appear, try entering download mode (I think download mode is the one you should try first).
Once your device appears in the adb command window, google the command for copying files using adb. Use this command to copy all the files to either an sd card inserted in the phone, or directly onto your pc (if possible).
If none of this is working out for you, and you are willing to pay, take it to a data recovery shop/centre. They should be able to extract the data from the device at a reasonable price.
Click to expand...
Click to collapse
Hi,
I downloaded the platform tools and I unzipped it, I installed Samsung dex and the drivers for on the PC, when I plugin the cable I can see there is Galaxy S9+ driver but it's empty because the phone is locked. When I try to open adb.exe it's not doing anything. all the exe doesn't work except sqlite3.exe. Attached is the screen
Is it possible for you to help me via teamviewr? If it success I would pay you. Even if it's not success I'll pay you. I don't mind to pay upfront, Thank you for your help sir
Related
Hi guys,
I flashed a wrong ROM, and then the screen doesn't turn on any more, plug in computer, computer can't recognize the device, it gives me plug-in then unplug and then plug-in sound while it is plug in all the time. tried mini USB jig, no response. is it completely dead? anyway to save it?
Thanks guys
thunderzhao said:
Hi guys,
I flashed a wrong ROM, and then the screen doesn't turn on any more, plug in computer, computer can't recognize the device, it gives me plug-in then unplug and then plug-in sound while it is plug in all the time. tried mini USB jig, no response. is it completely dead? anyway to save it?
Thanks guys
Click to expand...
Click to collapse
If you want unbrick hardbrick solution please PM me.
Thanks.
hard brick = replace parts
soft brick = fixable
if your computer is outputting sound when you connect your phone to it, then there is life in the phone its not hard bricked. *ive softbricked many phones, and ive hard bricked 1, so i know the difference*
can you get to recovery?
can you get to download mode?
can you adb devices via pc?
JamieD81 said:
hard brick = replace parts
soft brick = fixable
if your computer is outputting sound when you connect your phone to it, then there is life in the phone its not hard bricked. *ive softbricked many phones, and ive hard bricked 1, so i know the difference*
can you get to recovery?
can you get to download mode?
can you adb devices via pc?
Click to expand...
Click to collapse
Thanks for your reply, I can't get into recovery or download. but never tried adb device via PC, is that the same as odin?. I will try that, and is there a guide on how to do that?
Well... if you freshly flashed a Rom let's hope that dev had usb debugging on. If not this is all am exercise in setting up adb...cause even if the device isn't bricked without that setting on, adb will not communicate with the device.
Install java runtime environment and add to variable path.
Then you can install the android sdk.
Once installed open a command prompt.
Cd (change directories) to the "platform-tools" folder of the sdk install.
Once the prompt is there type:
Adb devices (enter)
If you get a device and then an alpanumeric id, your device is alive
From there type:
Adb reboot recovery (enter)
To boot into recovery and flash a working Rom.
Or adb reboot download (enter)
To boot download mode and use Odin.
If adb says device offline, usb debughing is off but your device is still alive, try the button combos for recovery, or invest in a jig to force download mode.
And finally if that gets nothing.... you're bricked.
Mobile tech videos . Com is a very reputable site that offers jtag debricking repair.
Wow cris, I am amazed at your thorough responses.
rangercaptain said:
Wow cris, I am amazed at your thorough responses.
Click to expand...
Click to collapse
Sometimes even zombies can provide a benefit to society.
Studa ... Nice going sir.
Sent from my Big Ass Outlaw Phone
studacris said:
Well... if you freshly flashed a Rom let's hope that dev had usb debugging on. If not this is all am exercise in setting up adb...cause even if the device isn't bricked without that setting on, adb will not communicate with the device.
Install java runtime environment and add to variable path.
Then you can install the android sdk.
Once installed open a command prompt.
Cd (change directories) to the "platform-tools" folder of the sdk install.
Once the prompt is there type:
Adb devices (enter)
If you get a device and then an alpanumeric id, your device is alive
From there type:
Adb reboot recovery (enter)
To boot into recovery and flash a working Rom.
Or adb reboot download (enter)
To boot download mode and use Odin.
If adb says device offline, usb debughing is off but your device is still alive, try the button combos for recovery, or invest in a jig to force download mode.
And finally if that gets nothing.... you're bricked.
Mobile tech videos . Com is a very reputable site that offers jtag debricking repair.
Click to expand...
Click to collapse
thanks a lot for your detailed instruction!!!
unfortunately, computer cannot recognize the device, it just goes on and off endlessly, and asking to format the drive, Adb devices doesn't show anything either. probably have to send to repair
The usual cure for flashing a ROM for another device is a JTAG service. cris mentioned it -- www.mobiletechvideos.com. It takes a week for the repair and costs you about $50.
The phone is returned with your carrier's stock ROM ICS 4.0.4.
rangercaptain said:
The usual cure for flashing a ROM for another device is a JTAG service. cris mentioned it -- www.mobiletechvideos.com. It takes a week for the repair and costs you about $50.
The phone is returned with your carrier's stock ROM ICS 4.0.4.
Click to expand...
Click to collapse
Sounds like a plan, Thanks
thunderzhao said:
Sounds like a plan, Thanks
Click to expand...
Click to collapse
I only do for $ 25 and ship it back right away . More detail PM me.
So I recently pulled my G Watch back out and installed the most recent OTA 6.0.1, installed TWRP, the custom kernel, and rooted it. Obviously all of that required ADB to function correctly. It did perfectly. I installed ADB using the 15 Second ADB Installer, and used WinDroid Toolkit to flash TWRP and get into recovery and do the rest, that by default installed the ClockworkMod ADB drivers, all of this on my Windows 10 PC.
Those drivers worked perfectly. Until today.
I did a fresh install of CM13 on my Nexus 5 phone, which my watch was paired to at the time. I wiped everything and started over, so I then went into my watches settings and did the Factory Reset so I could start fresh and resync up with my new rom install on my phone.
But when I try to connect via ADB or even try to list the devices it always states "Unauthorized"...
For whatever reason, no matter what I try it wont bring up the prompt on my phone to authorize this computer.
I revoked Debug permissions on both my watch and my phone, tried different usb ports, turned off and on debugging in all its forms on both my watch and phone, plus restarted all my devices and my PC. I have tried google's adb drivers as well.
Not sure what else there is to possibly try, seems I have covered all my bases here. Just doesn't make sense that it worked and now all the sudden it doesn't...
Glad I'm not the only one having this problem! I've tried same exact methods you mentioned with no luck. Hopefully someone knows what's going on here and provide a solution
Maybe deleting the keys in the computer will fix it. If it works with another computer, then it's the solution. On Mac, they are stored in a folder called .android in the home folder, if I recall correctly. Anyway it should be easy to find online how to delete the keys in the OS you're using.
What I did was first authorise my phone to my pc's adb then I copied adb_keys from /data/misc/adb/ on my phone to my pc. I then copied that while in TWRP on my LG G watch to the same directory /data/misc/adb/ and rebooted to system and voila adb access restored!
Thanks for your suggestions guys, but I officially give up figuring this out. Tried other computers and it still says "unauthorized." Tried both Windows 10 and Ubuntu and still the same error. Some thing's definitely happened since Wear 6.0 update or maybe invisible kernel for 6.0?
@Xmaster24 I would try your TWRP way, but I never installed it as I didn't see the need for it. I don't think there's a way to install it now without ADB, is there?
xymic said:
Thanks for your suggestions guys, but I officially give up figuring this out. Tried other computers and it still says "unauthorized." Tried both Windows 10 and Ubuntu and still the same error. Some thing's definitely happened since Wear 6.0 update or maybe invisible kernel for 6.0?
@Xmaster24 I would try your TWRP way, but I never installed it as I didn't see the need for it. I don't think there's a way to install it now without ADB, is there?
Click to expand...
Click to collapse
adb is absolutely not required. seeing as you are running 6.0.1 get the custom TWRP from my root guide here and follow the instructions on flashing the recovery. Seeing as you don't have adb you will just have to power off your watch and boot it up and swipe top left to bottom right as soon as you see something
Xmaster24 said:
adb is absolutely not required. seeing as you are running 6.0.1 get the custom TWRP from my root guide here and follow the instructions on flashing the recovery. Seeing as you don't have adb you will just have to power off your watch and boot it up and swipe top left to bottom right as soon as you see something
Click to expand...
Click to collapse
Aaaaaand we're back, Houston! Thanks a lot man. Works great now.
Hello
I have the same problem as author of this thread. How can I get authorize adb? I need it to push some files to internal memory.
I suffer the same problem.
Ok, I found solove for this problem. Just what you need is back to stock for example by this method: http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863 or manually("fastboot flash" command): http://forum.xda-developers.com/g-watch/development/how-to-to-stock-rooted-6-0-t3339875 If you will have bootloop, you need to factory reset in twrp and reboot. To boot into twrp when you have bootloop you must enter to bootloader mode and write in cmd "fastboot boot YourTwrpName.img" command. I used twrp from this topic: http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512 After all you can update your watch to actual android wear version and again root/ change kernel.
Sorry for my bad english. I am not native speaker.
koszanty said:
Ok, I found solove for this problem. Just what you need is back to stock for example by this method: http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863 or manually("fastboot flash" command): http://forum.xda-developers.com/g-watch/development/how-to-to-stock-rooted-6-0-t3339875 If you will have bootloop, you need to factory reset in twrp and reboot. To boot into twrp when you have bootloop you must enter to bootloader mode and write in cmd "fastboot boot YourTwrpName.img" command. I used twrp from this topic: http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512 After all you can update your watch to actual android wear version and again root/ change kernel.
Sorry for my bad english. I am not native speaker.
Click to expand...
Click to collapse
Sorry, but, with ADB in "unauthorized" state it can't be done.
Guys, read Xmaster24's posts in first page. That's how I fixed it.
turbomann said:
Sorry, but, with ADB in "unauthorized" state it can't be done.
Click to expand...
Click to collapse
Why? Fastboot is diffrent thing than adb and it should work without 'adb authorization'. I used this method and it worked for me.
xymic said:
Guys, read Xmaster24's posts in first page. That's how I fixed it.
Click to expand...
Click to collapse
If you don't have copy of adb keys on watch sdcard, probably you cant use his fix(or am I wrong?). By the way, how can I mange files in TWRP mode without working adb? In TWRP is special option/ command for mange files by PC or something like that? If I connect watch to PC I can't see it as mass storage.
koszanty said:
Why? Fastboot is diffrent thing than adb and it should work without 'adb authorization'. I used this method and it worked for me.
If you don't have copy of adb keys on watch sdcard, probably you cant use his fix(or am I wrong?). By the way, how can I mange files in TWRP mode without working adb? In TWRP is special option/ command for mange files by PC or something like that? If I connect watch to PC I can't see it as mass storage.
Click to expand...
Click to collapse
You had flash 5.1.1 and then upgrade to 6.0.1? Are there bootloader compatible?
koszanty said:
If you don't have copy of adb keys on watch sdcard, probably you cant use his fix(or am I wrong?). By the way, how can I mange files in TWRP mode without working adb? In TWRP is special option/ command for mange files by PC or something like that? If I connect watch to PC I can't see it as mass storage.
Click to expand...
Click to collapse
You only need to have adb_keys file on the phone not the watch. In my case, I was able to use adb perfectly fine while I was in TWRP. Basically here's what I did:
1. Copy adb_keys file from your phone to computer. It is located in /data/misc/adb. If you can't see the file, you probably have to authorize your phone first with your computer.
2. Flash TWRP recovery from XMaster24's link using fastboot on your watch.
3. Boot into recovery. You don't need go into any options. While on the recovery homescreen, Just use this command to transfer adb_keys file into your watch:
Code:
adb push adb_keys /data/misc/adb
You can check using "Files" option in recovery to see if the file is transferred into the watch.
4. Reboot your watch and you should be able to access adb now.
You can do it your way as well, but using xmaster24's method saves time, I think
xymic said:
You only need to have adb_keys file on the phone not the watch. In my case, I was able to use adb perfectly fine while I was in TWRP. Basically here's what I did:
1. Copy adb_keys file from your phone to computer. It is located in /data/misc/adb. If you can't see the file, you probably have to authorize your phone first with your computer.
2. Flash TWRP recovery from XMaster24's link using fastboot on your watch.
3. Boot into recovery. You don't need go into any options. While on the recovery homescreen, Just use this command to transfer adb_keys file into your watch:
Code:
adb push adb_keys /data/misc/adb
You can check using "Files" option in recovery to see if the file is transferred into the watch.
4. Reboot your watch and you should be able to access adb now.
You can do it your way as well, but using xmaster24's method saves time, I think
Click to expand...
Click to collapse
In my case adb doesn't worked at all
turbomann said:
You had flash 5.1.1 and then upgrade to 6.0.1? Are there bootloader compatible?
Click to expand...
Click to collapse
It's compatibile but can occur bootloop. If you will have bootloop, you must do that what I write some posts earlier.
I'm realised that my phone with MM do the same bug, unauthorized, I look for adb_keys file but folder ADB is empty, then only remains flash and update on the watch.
*im not developer, neither noob i just like to share what I know*
Maybe this is a noob guide, but i did my best to share something helpful
before you go deeper, be sure to check your phone able to get into fastboot mode. If you cant, use REAL unbrick method instead
If your phone soft or hard bricked, bootloop, stuck on logo etc you know you are f***ed unless you know what should to do.
Some time ago bootlooped my phone, but i cant go to recovery, cant ADB because I forgot to enable USB debugging, my computer wont recognize my phone poperly because my phone mad at me, and my phone flickering like hell *party hard*. Maybe this is a brick not bootloop but whatever
Good friend of mine tell me what should to do
What you need:
Working PC with minimal ADB and fastboot installed //see the thread here, your phone's USB and ADB driver installed //download here if you dont have it
Working USB DATA cable
Custom recovery everything will do, as long as its compatible with your current android version. Rename the img to recovery.img
ROM you prefer everything will do, as long as its compatible with your current android version. Move to your SD Card
The power of will
Step:
1. Make sure your phone is turned off
2. Boot into fastboot mode, you will see some chinese message
3. Plug your phone to to your PC
4. Check if your PC at least know that you are pluged in your phone (check via device manager by 'plug and un-plug' your phone and check for 'appear and disappear' device , mine listed as it is was a modem.)
5. Move the recovery.img inside minimal adb and recovery folder root usually under c:/programfiles directory
6. Run the minimal adb and fastboot, check your device by using /adb devices/ command without backslash
7. If your device is not listed, dont worry. We still able to use the fastboot
8. Boot your phone into recovery mode by using /fastboot boot recovery.img/ command without backslash
9. Wait for few secs, and your phone should touched down to recovery mode.
10. Do wipe (data, dalvik, cache, system, internal)
11. Flash your prefered ROM
12. ..........???
13. Profit
Troubleshooting:
If your PC unable to recognize your phone completely, try using another usb cable, usb ports, uninstall-reinstall, plug-unplug, and make sure your phone in fastboot mode before you plug your phone to the PC.
Feel free to critics, I hope this helped you :fingers-crossed:
Thank you for all who helped me making this post.
McBubu_1337 said:
*im not developer, neither noob i just like to share what I know*
Maybe this is a noob guide, but i did my best to share something helpful
before you go deeper, be sure to check your phone able to get into fastboot mode. If you cant, use REAL unbrick method instead
If your phone soft or hard bricked, bootloop, stuck on logo etc you know you are f***ed unless you know what should to do.
Some time ago bootlooped my phone, but i cant go to recovery, cant ADB because I forgot to enable USB debugging, my computer wont recognize my phone poperly because my phone mad at me, and my phone flickering like hell *party hard*. Maybe this is a brick not bootloop but whatever
Good friend of mine tell me what should to do
What you need:
Working PC with minimal ADB and fastboot installed //see the thread here, your phone's USB and ADB driver installed //download here if you dont have it
Working USB DATA cable
Custom recovery everything will do, as long as its compatible with your current android version. Rename the img to recovery.img
ROM you prefer everything will do, as long as its compatible with your current android version. Move to your SD Card
The power of will
Step:
1. Make sure your phone is turned off
2. Boot into fastboot mode, you will see some chinese message
3. Plug your phone to to your PC
4. Check if your PC at least know that you are pluged in your phone (check via device manager by 'plug and un-plug' your phone and check for 'appear and disappear' device , mine listed as it is was a modem.)
5. Move the recovery.img inside minimal adb and recovery folder root usually under c:/programfiles directory
6. Run the minimal adb and fastboot, check your device by using /adb devices/ command without backslash
7. If your device is not listed, dont worry. We still able to use the fastboot
8. Boot your phone into recovery mode by using /fastboot boot recovery.img/ command without backslash
9. Wait for few secs, and your phone should touched down to recovery mode.
10. Do wipe (data, dalvik, cache, system, internal)
11. Flash your prefered ROM
12. ..........???
13. Profit
Troubleshooting:
If your PC unable to recognize your phone completely[B/], try using another usb cable, usb ports, uninstall-reinstall, plug-unplug, and make sure your phone in fastboot mode before you plug your phone to the PC.
Feel free to critics, I hope this helped you :fingers-crossed:
Thank you for all who helped me making this post.
Click to expand...
Click to collapse
Good work bro
The Hard Gamer said:
Good work bro
Click to expand...
Click to collapse
Thanks, its noob post so i dont expect anything special
McBubu_1337 said:
Thanks, its noob post so i dont expect anything special
Click to expand...
Click to collapse
It is a good help to those who are new to getting bricked
It shows waiting for device
Tommen1998 said:
It shows waiting for device
Click to expand...
Click to collapse
You may need to check some things:
Your PC actually know that you have inserted your phone. It doesn't have to know it's a phone (so it can be detected as unknown device or something similar, mine is detected as a modem)
Your phone is indeed in fastboot mode, you can tell yours is in fastboot mode by a Chinese message at the bottom of the screen
Change your cable data, make sure it is a cable data, not a normal charging cable
let me know if you need some help
McBubu_1337 said:
You may need to check some things:
Your PC actually know that you have inserted your phone. It doesn't have to know it's a phone (so it can be detected as unknown device or something similar, mine is detected as a modem)
Your phone is indeed in fastboot mode, you can tell yours is in fastboot mode by a Chinese message at the bottom of the screen
Change your cable data, make sure it is a cable data, not a normal charging cable
let me know if you need some help
Click to expand...
Click to collapse
Hello. I Tried a lot, but my PC doesn't recognise my phone. The phone is in fastboot mode. I've tried by changing cables too
same issue
Tommen1998 said:
Hello. I Tried a lot, but my PC doesn't recognise my phone. The phone is in fastboot mode. I've tried by changing cables too
Click to expand...
Click to collapse
I am also getting the same issue tried different cables but not working. Anyone please help me
The same issue. I think it's about getting it recognized in Fastboot mode. It's recognized in Android but not in Fastboot. All new devices are installed including those you get in Diagnostic 9091 mode (Power+V+). What do I need for Fastboot mode?
Hey guys sorry if this is newb question but I've been looking for hours and just getting overwhelmed.
I have an SPC glow 10.1 cheap tablet purchased in Spain, apparantly a rebranded Chinese tab.
Android version 6.0, tried rooting with Kingoapp APK which was a complete fake waste of time. Tried framaroot, it said the exploits don't work.
Where should I be looking to be able to root something like this? I.e. which app/project like Xposed or Magisk here?
Thanks a lot
androidferret said:
Hey guys sorry if this is newb question but I've been looking for hours and just getting overwhelmed.
I have an SPC glow 10.1 cheap tablet purchased in Spain, apparantly a rebranded Chinese tab.
Android version 6.0, tried rooting with Kingoapp APK which was a complete fake waste of time. Tried framaroot, it said the exploits don't work.
Where should I be looking to be able to root something like this? I.e. which app/project like Xposed or Magisk here?
Thanks a lot
Click to expand...
Click to collapse
Have you unlocked the bootloader?
Augustoandro said:
Have you unlocked the bootloader?
Click to expand...
Click to collapse
No, I have not, how would you do that? There is no info on the Internet if I search for this brand name SPC.
Is there a way to find out which Chinese tab this is a rebrand of perhaps? Thanks
androidferret said:
No, I have not, how would you do that? There is no info on the Internet if I search for this brand name SPC.
Is there a way to find out which Chinese tab this is a rebrand of perhaps? Thanks
Click to expand...
Click to collapse
Please take a backup of ur data before proceeding further.
Try this,
Download adb and Koush Universal adb driver and install them on ur pc, always install the driver first and don't install the drivers adb setup asks u to install.
Run command prompt as administrator.
Open the folder in c drive where adb is installed, u can use file explorer for this.
Press Shift+right click and select open command window here.
Enable USB debugging on your phone and connect it to the pc by a USB cord.
Enter command "adb devices" without quotation marks.
If it shows some device connected, only then proceed further.
Enter command " adb reboot bootloader"
Enter command " fastboot devices", if it shows some device to be connected, only then proceed further.
Enter command " fastboot oem unlock".
Ur phone may then ask for final confirmation on the phone screen, select yes.
When procedure completes, type "fastboot reboot" and ur phone will reboot.
U can now use Kingoroot or any other tool for rooting.
Thanks Augusto, your advice was great,
it worked so far, but it wasn't easy getting there.
Here's what I did for others:
1. Installed adb and fastboot on my computer from Android developers, turn on debugging on tablet
2. Downloaded universal USB driver installer (aka. koush driver)
3. Installed but adb did not see my tablet, turns out the tablet is not in the list for the USB driver installer
4. Downloaded source code for koush driver, had to modify the .inf file as described in one of the comments on the github page,
by copy pasting two of the existing lines in the inf file and replacing with the USB id codes found from Device Manager in Windows 7.
5. After modifying the .inf file was able to install the driver from Device Manager "Update Driver..." for the Android device
6. Finally after this adb was able to see it under "adb devices"
7. Restart to bootloader with the command "adb reboot bootloader", this entered fastboot on my tablet
8. Tried to run "fastboot devices" but again the phone is not seen.
9. Apparently when in fastboot mode, the tablet appears under completely different USB ids which can be seen in Device Manager
10. Had to go back to the same .inf file and add two more lines with the new Device IDs
11. Installed the driver again in Device Manager, "Update driver"...
12. Now fastboot can see it too!
13. Entered the command "fastboot oem unlock", got the message that the unlock failed!
14. Had to restart tablet in normal mode go into Developer Options and set "OEM unlock"
15. Reboot to fastboot, unlock now works! Reboot phone using "fastboot reboot"
A strange thing happened at this point, the little android figure with cogs in his stomach came up for a few seconds, then the OEM logo for a long time,
after waiting a few minutes I force reset it. It started up but the system was completely erased and put into factory state, including completely erasing every single file I had on it,
even pictures, etc., it asked the first install questions from the very beginning. Fortunately I didn't have anything valuable.
So I got this far, now I'd like to root it,
I tried framaroot, not working, I don't trust Kingoroot, any recommendations for the root method from a reliable source?
androidferret said:
Thanks Augusto, your advice was great,
it worked so far, but it wasn't easy getting there.
Here's what I did for others:
1. Installed adb and fastboot on my computer from Android developers, turn on debugging on tablet
2. Downloaded universal USB driver installer (aka. koush driver)
3. Installed but adb did not see my tablet, turns out the tablet is not in the list for the USB driver installer
4. Downloaded source code for koush driver, had to modify the .inf file as described in one of the comments on the github page,
by copy pasting two of the existing lines in the inf file and replacing with the USB id codes found from Device Manager in Windows 7.
5. After modifying the .inf file was able to install the driver from Device Manager "Update Driver..." for the Android device
6. Finally after this adb was able to see it under "adb devices"
7. Restart to bootloader with the command "adb reboot bootloader", this entered fastboot on my tablet
8. Tried to run "fastboot devices" but again the phone is not seen.
9. Apparently when in fastboot mode, the tablet appears under completely different USB ids which can be seen in Device Manager
10. Had to go back to the same .inf file and add two more lines with the new Device IDs
11. Installed the driver again in Device Manager, "Update driver"...
12. Now fastboot can see it too!
13. Entered the command "fastboot oem unlock", got the message that the unlock failed!
14. Had to restart tablet in normal mode go into Developer Options and set "OEM unlock"
15. Reboot to fastboot, unlock now works! Reboot phone using "fastboot reboot"
A strange thing happened at this point, the little android figure with cogs in his stomach came up for a few seconds, then the OEM logo for a long time,
after waiting a few minutes I force reset it. It started up but the system was completely erased and put into factory state, including completely erasing every single file I had on it,
even pictures, etc., it asked the first install questions from the very beginning. Fortunately I didn't have anything valuable.
So I got this far, now I'd like to root it,
I tried framaroot, not working, I don't trust Kingoroot, any recommendations for the root method from a reliable source?
Click to expand...
Click to collapse
I told you to take backup of your data beforehand.
I am recommending Kingoroot because I personally used it to root my phone.
Augustoandro said:
I told you to take backup of your data beforehand.
I am recommending Kingoroot because I personally used it to root my phone.
Click to expand...
Click to collapse
I know about the backup, I just wasn't expecting it to wipe everything, I don't know why it did that.
As for Kingoroot, I installed the official app from play store which was a completely fake and dangerous looking piece of crap,
it showed like 50 ads asked me to rate it and then some weird pop ups kept coming, and then it did nothing. No message whatsoever.
Thank god my phone wasn't rooted because
I don't know what the lowlifes who do KingoRoot would have done with it.
I don't trust this company to install their software on my computer and I can't believe you guys recommend such an obviously
unscrupulous, malware product to others. Why is KingoRoot even on Google Play, they should be among the trojan trash of the every single antivirus and antimalware.
androidferret said:
I know about the backup, I just wasn't expecting it to wipe everything, I don't know why it did that.
As for Kingoroot, I installed the official app from play store which was a completely fake and dangerous looking piece of crap,
it showed like 50 ads asked me to rate it and then some weird pop ups kept coming, and then it did nothing. No message whatsoever.
Thank god my phone wasn't rooted because
I don't know what the lowlifes who do KingoRoot would have done with it.
I don't trust this company to install their software on my computer and I can't believe you guys recommend such an obviously
unscrupulous, malware product to others. Why is KingoRoot even on Google Play, they should be among the trojan trash of the every single antivirus and antimalware.
Click to expand...
Click to collapse
I meant Kingoroot for PC and not Kingoroot Android.
They are different, although from the same company.
Wow it turns out I was using a fake Kingoroot from the Play Store so I take back my comments regarding KingoRoot.
I can't believe the Play Store allows such trash.
Not sure if this is the proper place for this question; if not, please move. I picked up an Irulu Expro No. X9 Android tablet on eBay. It seems to work fine, except I can't get past the login screen. I tried many times the various key combinations to get it into recovery mode but none worked. Other suggestions had me putting it in debug mode first, but how to do that if you can't get logged in? I'm not concerned about saving any data, I would just like to be able to use it. I would appreciate any help to solve my problem. Thanx.
@jrockow
Have you ever tried to check whether the device is accessable by means of ADB?
Code:
adb devices
If it's accessable then you easily can remove the password lock. You do this by launching Android Settings via ADB as shown next:
Code:
adb devices
adb shell am start -a android.settings.SETTINGS
jwoegerbauer said:
@jrockow
Have you ever tried to check whether the device is accessable by means of ADB?
Code:
adb devices
If it's accessable then you easily can remove the password lock. You do this by launching Android Settings via ADB as shown next:
Code:
adb devices
adb shell am start -a android.settings.SETTINGS
Click to expand...
Click to collapse
Thanx for your quick reply.
adb devices doesn't list anything.
I thought you needed to enable USB debugging for ADB to work?
Don't know how to do that if I can't log in.
jrockow said:
Thanx for your quick reply.
adb devices doesn't list anything.
I thought you needed to enable USB debugging for ADB to work?
Don't know how to do that if I can't log in.
Click to expand...
Click to collapse
OK, so I'm somewhat of a rookie when it comes to ADB and FASTBOOT.
I'm not sure I have everything correct. I'm using an app called "Minimal ADB and Fastboot".
I have another tablet, same as the one I can't access, and I have turned on the developer options.
Even with that, I still can't see any devices when I run ADB.
FYI: When I look at devices in my PC it shows up as X9, which I believe is correct.
With my no password tablet, I can actually see all the directories of my Android on my PC.
If I try that with the other one don't see any directories.
jrockow said:
With my no password tablet, I can actually see all the directories of my Android on my PC.
Click to expand...
Click to collapse
Android's USB in that case is set to MTP mode, not ADB mode. MTP operates at the file level. Your Android device doesn’t expose its entire storage device to Windows computer. Instead, when you connect a device to your computer, the computer queries the device and the device responds with a list of files and directories it offers.
When Andoid's USB is in ADB mode, device can completely get controlled from Windows computer.
jrockow said:
I'm using an app called "Minimal ADB and Fastboot".
Click to expand...
Click to collapse
Serious Android device owners use the USB-driver ( AKA ADB ) as provided by device's OEM/Carrier.
jwoegerbauer said:
Android's USB in that case is set to MTP mode, not ADB mode. MTP operates at the file level. Your Android device doesn’t expose its entire storage device to Windows computer. Instead, when you connect a device to your computer, the computer queries the device and the device responds with a list of files and directories it offers.
When Andoid's USB is in ADB mode, device can completely get controlled from Windows computer.
Serious Android device owners use the USB-driver ( AKA ADB ) as provided by device's OEM/Carrier.
Click to expand...
Click to collapse
I was incorrect in my earlier post, when I said I turned on the developer mode on my "good" tablet and I still couldn't access it thru ADB.
I found out I really didn't have it turned on, and when I did I was able to execute the ADB commands.
That gets me back to my earlier post about not being able to turn on the developer mode on my "bad" tablet if I can't log in.
I would think with all the guys working on this stuff someone has come up with a way to get around a lost password?
I remind you, I tried the power+volume sequence many times, many ways, so I need a different approach; if there is one?
Thanx.
@jrockow
Because the tablet can't connect with PC via ADB then wondering why you don't contact seller of the tablet? Unlock Screen Password always can be done with Google Account Android device initially was bound to.
jwoegerbauer said:
@jrockow
Because the tablet can't connect with PC via ADB then wondering why you don't contact seller of the tablet? Unlock Screen Password always can be done with Google Account Android device initially was bound to.
Click to expand...
Click to collapse
I have already reached out to the seller. However, he knows nothing of the history of the tablet. He's just a guy who collects tons of electronics and sells them on eBay.
What really frustrates me is I can quite easily get my "good" tablet to enter recovery mode with the power+vol combination. I have tried many, many times to duplicate the same combo on the "bad" tablet and it just jumps over the recovery mode and boots to the logon screen.
Is it possible someone made some change to the tablet that won't allow it to go into recovery?
jrockow said:
I have already reached out to the seller. However, he knows nothing of the history of the tablet. He's just a guy who collects tons of electronics and sells them on eBay.
What really frustrates me is I can quite easily get my "good" tablet to enter recovery mode with the power+vol combination. I have tried many, many times to duplicate the same combo on the "bad" tablet and it just jumps over the recovery mode and boots to the logon screen.
Is it possible someone made some change to the tablet that won't allow it to go into recovery?
Click to expand...
Click to collapse
So, I've come to the conclusion that what I'm asking for just can't be done.
Can't enter reset with any key combo I've tried; can't use ADB because debugging not on; can't go to Google because I don't know who owned the phone before me.
If this were a PC device, there are multiple apps available to get around a lost password. I've done it many times.
I was really hoping there would be some Android genius out there who could help.
What a shame to realize that a perfectly good working device might as well be thrown in the trash.
jrockow said:
So, I've come to the conclusion that what I'm asking for just can't be done.
Can't enter reset with any key combo I've tried; can't use ADB because debugging not on; can't go to Google because I don't know who owned the phone before me.
If this were a PC device, there are multiple apps available to get around a lost password. I've done it many times.
I was really hoping there would be some Android genius out there who could help.
What a shame to realize that a perfectly good working device might as well be thrown in the trash.
Click to expand...
Click to collapse
If you know that the phone basically supports ADB, if the phone has a slot for external SD-card, if you can boot into Recovery Mode, if the Recovery Mode allows you to "apply update from sd-card" then you by means of an OTA can enable USB-debugging, then you can access the phone via ADB.
Currently I'm working on such an UPDATE.ZIP and will, if it's bug free, it publish here on XDA.
Personally don't own a phone what supports ADB: it's a HUAWEI Y7 2019. If you are willing to become a tester let me know it. I'll then PM you the link to the UPDATE.ZIP.
jwoegerbauer said:
If you know that the phone basically supports ADB, if the phone has a slot for external SD-card, if you can boot into Recovery Mode, if the Recovery Mode allows you to "apply update from sd-card" then you by means of an OTA can enable USB-debugging, then you can access the phone via ADB.
Currently I'm working on such an UPDATE.ZIP and will, if it's bug free, it publish here on XDA.
Personally don't own a phone what supports ADB: it's a HUAWEI Y7 2019. If you are willing to become a tester let me know it. I'll then PM you the link to the UPDATE.ZIP.
Click to expand...
Click to collapse
If I could boot into Recovery Mode my problem would be solved.