Related
Alright, I know this is a known issue and I've read every thread detailing people saying they have this issue but none that have it solved so I'm posting it here since we have some pretty smart guys browsing our forums and I'm hoping one of them can help.
Here is the problem: My 2010 MacBook Pro will recognize my phone as a USB drive but whenever I try to run ADB commands I get "Error device not found". I've tried both USB ports on the machine and with both the computer knows the Nexus S is plugged in (I checked the System Information and it lists the Nexus S, exactly like that, as plugged into a USB port) but it won't recognize it. In the past I've used an older MacBook which could recognize the phone but that is no longer an option. I've tried uninstalling and reinstalling the SDK a few times but never to any avail. Any help would be greatly appreciated.
Forgive me for asking the obvious, but do you have USB Debugging enabled?
distortedloop said:
Forgive me for asking the obvious, but do you have USB Debugging enabled?
Click to expand...
Click to collapse
Absolutely forgiven, I should have stated in the OP that I do in fact have USB debugging enabled.
Had to ask, just to be sure.
Does fastboot work with it (ie, boot to fastboot on the phone and try a fastboot devices command)?
distortedloop said:
Had to ask, just to be sure.
Does fastboot work with it (ie, boot to fastboot on the phone and try a fastboot devices command)?
Click to expand...
Click to collapse
I haven't been able to get any commands to work because once I start the ADB shell I get the device not found error. I could try a different command if you told me what to try
Kill the adb server in your terminal shell:
Code:
adb kill-server
Then try again:
Code:
adb devices
If no joy with that, reboot the phone to fastboot (power off, then press/hold vol+up and then press power on).
Once in fastboot, plug the phone into the Mac USB port, then from the command line in terminal:
Code:
fastboot devices
or might have to be
Code:
./fastboot devices
Not sure what that will tell us, but it would be interesting to know. edit: actually this will tell us if it's a driver type problem or just an adb problem.
FYI - on my MBP the Nexus S shows up as you describe in device manager, so you seem normal in that regard.
distortedloop said:
Kill the adb server in your terminal shell:
Code:
adb kill-server
Then try again:
Code:
adb devices
If no joy with that, reboot the phone to fastboot (power off, then press/hold vol+up and then press power on).
Once in fastboot, plug the phone into the Mac USB port, then from the command line in terminal:
Code:
fastboot devices
or might have to be
Code:
./fastboot devices
Not sure what that will tell us, but it would be interesting to know. edit: actually this will tell us if it's a driver type problem or just an adb problem.
FYI - on my MBP the Nexus S shows up as you describe in device manager, so you seem normal in that regard.
Click to expand...
Click to collapse
Okay, so there were no devices listed for the abd devices and I'm not sure what to preface the fastboot command with since I can't seem to find that in my sdk folder...perhaps I should try reinstalling it again? I know on my windows partition there is a file called fastboot but I've never seen the one for mac
kenvan19 said:
Okay, so there were no devices listed for the abd devices and I'm not sure what to preface the fastboot command with since I can't seem to find that in my sdk folder...perhaps I should try reinstalling it again? I know on my windows partition there is a file called fastboot but I've never seen the one for mac
Click to expand...
Click to collapse
Try the files in this archive attached. Change your working directory in terminal to the one you put them in, doesn't matter what it is. You'll have to use the ./ in front of the commands (./fastboot or ./adb).
Also, have you tried a clean power off and total reboot of the MacBook Pro? Just a shot in the dark with that one, but maybe clean out some memory or something that's screwing you up.
distortedloop said:
Try the files in this archive attached. Change your working directory in terminal to the one you put them in, doesn't matter what it is. You'll have to use the ./ in front of the commands (./fastboot or ./adb).
Click to expand...
Click to collapse
Giving it a shot now
distortedloop said:
Also, have you tried a clean power off and total reboot of the MacBook Pro? Just a shot in the dark with that one, but maybe clean out some memory or something that's screwing you up.
Click to expand...
Click to collapse
I've been booting between Windows and Mac OSX all day trying to get this to work so I've rebooted several times only to have the same issue.
Fastboot devices gave me this output:
serial# fastboot
kenvan19 said:
Fastboot devices gave me this output:
serial# fastboot
Click to expand...
Click to collapse
Glad you noticed that long number was your serial and changed it.
Okay, this tells us that there is nothing wrong with the Mac talking to the phone. That's good news in a way.
I noticed in the Dev section you were asking about this same issue in regards to regaining root.
It seems to me that at this point, with that being your primary concern, you should just use the fastboot mode to fastboot flash recovery clockwork.img or fastboot boot instead of flash. Then you can use clockwork to install the su zip file.
We can worry about getting adb working later on.
distortedloop said:
Glad you noticed that long number was your serial and changed it.
Okay, this tells us that there is nothing wrong with the Mac talking to the phone. That's good news in a way.
I noticed in the Dev section you were asking about this same issue in regards to regaining root.
It seems to me that at this point, with that being your primary concern, you should just use the fastboot mode to fastboot flash recovery clockwork.img or fastboot boot instead of flash. Then you can use clockwork to install the su zip file.
We can worry about getting adb working later on.
Click to expand...
Click to collapse
=O You rule! I was able to fastboot the recovery image and reapply root. Distortedloop you're a ****ing god. I apologize for the profanity but thank you. Thank you. Thank you.
kenvan19 said:
=O You rule! I was able to fastboot the recovery image and reapply root. Distortedloop you're a ****ing god. I apologize for the profanity but thank you. Thank you. Thank you.
Click to expand...
Click to collapse
Great. Glad you're running root again.
Try adb with the file I posted earlier. Also, try cycling the USB debugging a couple of times for good measure.
distortedloop said:
Great. Glad you're running root again.
Try adb with the file I posted earlier. Also, try cycling the USB debugging a couple of times for good measure.
Click to expand...
Click to collapse
Will do both. Again, thank you so much...not being rooted was killing me hehe
kenvan19 said:
My 2010 MacBook Pro will recognize my phone as a USB drive but whenever I try to run ADB commands I get "Error device not found".
Click to expand...
Click to collapse
Hi, I fixed this by installing the Android File Transfer application on the mac. Of course, I had to do the 7 taps on the build number so that I could get to the development settings on the nexus and turn usb debugging on. Also, I had to restart the adb server (adb kill-server; adb start-server).
Occasionally the adb server won't die on a 'kill-server' and I have to kill it manually from the terminal (ps axu |grep adb to find the PID first).
Ahhh wow I've been googling this problem - exact same situation. Now... this might sound ludicrous, but someone asked you if you had enabled USB debugging. Every time I read that bit of advice I was like 'well duh, of course I did, I went and clicked Build number 7 times and became a super rad developer'.
... in short, I made the rather hasty mistake of assuming that enabling the developer options was the same thing as enabling USB debugging. Now ADB is behaving nicely. So - on the off chance you made this same mistake - after enabling developer mode, did you find the now unhidden developer menu and enable USB debugging from there? (please don't flame!) ha ha good luck
**UPDATE**
NEW VERSION
THIS RELIES ON ADB COMMANDS, SO IF YOU DO NOT HAVE USB DEBUGGING TURNED ON, OR A CUSTOM RECOVERY TO BOOT TO, THEN IT WILL NOT BE AS SIMPLE AS JUST RUNING THE PROGRAM.
Another user was having issues because he had an emulator installed, so I updated the file to give you the choice between an emulator, or device. I intend to update further to allow you to check for and select an individual device, that will come soon..
----------------------------------------------------------------------------------------------------------------
Recently my Galaxy s2's screen smashed, and, after replacing it with a GS4, i realized that many of my pictures were stuck on the internal sd card of the GS2. Being unable to turn on mass storage mode, I made a very simple tool that makes using adb pull a simple, painless process, even for the most computer illiterate of android users. Hope this helps if anyone needs it.
For anyone having issues...
If you had not previously activated USB Debugging, there are several steps you need to follow in order to enable ADB
SCREEN WORKING TOUCH BROKEN NO CUSTOM RECOVERYfirst, if you can see your screen, and have access to an otg cable, plug a mouse in to the otg cable, and the otg cable into the phone. Use the mouse to enable USB debugging, or to transfer files.
HOW TO ENABLE USB DEBUGGING
SCREEN WORKING TOUCH BROKEN WITH CUSTOM RECOVERYboot to your custom recovery ADB commands will work here. (usually hold vol- + pwr)
HOW TO BOOT TO RECOVERY
Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices
The result should be something like
List of devices attached
051a4dd5 recovery
^^this number will be different for you
if you get a result on ADB devices, then you can use the program
SCREEN BROKEN TOUCH BROKEN WITH CUSTOM RECOVERYboot to your custom recovery ADB commands will work here. (usually hold vol- + pwr)
HOW TO BOOT TO RECOVERY
Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices
The result should be something like
List of devices attached
051a4dd5 recovery
^^this number will be different for you
if you get a result on ADB devices, then you can use the program
SCREEN BROKEN TOUCH BROKEN NO CUSTOM RECOVERYnow things get complicated...
*The following is paraphrased from this site
1. download the custom recovery image for your device. Copy the recovery image to a convenient location on your computer, preferably with a short path. We will be placing it on the C Drive directly (not in any folder) and using that in the next steps.
Note: The recovery image should have .img extension. If it is in a zip file, extract the .img file from it.
I recommend clockwork mod non touch from this page
2. Power your device off and reboot your device to FASTBOOT or DOWNLOAD MODE depending on which type of device you have.
(most devices are fastboot, SAMSUNG typically uses DOWNLOAD MODE)
how to boot to fastboot or download mode
[FASTBOOT]3. Connect your device to your computer via USB and wait till you see the PC recognize the device
to check if your device is in fastboot and connected use CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
fastboot devices
you will see a list of connected devices. if not, something went wrong.
4. Launch Command Prompt and type the following commands;
cd c:\android (this is your ADB path, c:\android is default)
fastboot flash recovery c:\recovery.img
5. Wait for the process to finish.
6. Turn device off then boot to your custom recovery ADB commands will work here. (usually hold vol- + pwr)
HOW TO BOOT TO RECOVERY
Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices
The result should be something like
List of devices attached
051a4dd5 recovery
^^this number will be different for you
if you get a result on ADB devices, then you can use the program
[RECOVERY MODE (SAMSUNG)]USE THE INSTRUCTIONS ON THIS PAGE
Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices
The result should be something like
List of devices attached
051a4dd5 recovery
^^this number will be different for you
if you get a result on ADB devices, then you can use the program
HOPEFULLY THIS HELPS. REMEMBER TO CHECK THE FORUM PAGE FOR YOUR DEVICE IF YOU RUN INTO ISSUES. THIS ISN'T ANYTHING THE MEMBERS OF XDA HAVEN'T DONE THOUSANDS OF TIMES OVER.
Don't forget to hit "Thanks"
i'll bump this thread for those who didn't see this amazing tool, this tool is really useful, thank you very much
Hi,
Sturggling to find the .adb file as my phone shows up as a "Portable Device" any ideas?
Cheers
Thank you!
I joined just to say thank you to FuzzyMeep Two. Thanks for an awesome tool! It worked better than advertised!
:good:
Thanks again!
-th3r3isnospoon
Question
Hi! Can I use that to restore data not from sdcard but from internal memory of the device? I was storing photos on device memory on my Asus TF300T and now its bricked. I need to restore these photos, my girlfriend has something like 1000 of them from her trip to Caracas. Its very important for her. I already managed to connect the device through fastboot and I launched anb in cmd. What should I do next? Please help me guys
koperkowy said:
Hi! Can I use that to restore data not from sdcard but from internal memory of the device? I was storing photos on device memory on my Asus TF300T and now its bricked. I need to restore these photos, my girlfriend has something like 1000 of them from her trip to Caracas. Its very important for her. I already managed to connect the device through fastboot and I launched anb in cmd. What should I do next? Please help me guys
Click to expand...
Click to collapse
Yes, when it references SD Card it means the internal "SD" storage built in to the phone, not the removable one. It should work as long as ADB can connect.
Sorry for taking so long to reply, i really hope you got your pictures back.
FuzzyMeep Two said:
Recently my Galaxy s2's screen smashed, and, after replacing it with a GS4, i realized that many of my pictures were stuck on the internal sd card of the GS2. Being unable to turn on mass storage mode, I made a very simple tool that makes using adb pull a simple, painless process, even for the most computer illiterate of android users. Hope this helps if anyone needs it.
P.S. I apologize if i have posted this in the wrong place, if so please let me know.
Click to expand...
Click to collapse
Really great stuff - so simple but so effective. Cheers and thanks.
Error msg
zobes said:
Really great stuff - so simple but so effective. Cheers and thanks.
Click to expand...
Click to collapse
When i run that tool, i get the error mesg: more than one device and emulator,
I dont want to uninstall the emulator coz it was a headache getting it running
How i procede to select the device to be used
alisdairjk said:
When i run that tool, i get the error mesg: more than one device and emulator,
I dont want to uninstall the emulator coz it was a headache getting it running
How i procede to select the device to be used
Click to expand...
Click to collapse
NEW VERSION
Try this, i haven't gotten to test it, so please let me know if it worked for you, I added the option of selecting an emulator or USB device, because of your post. Hopefully it helps.
When I try to run this I also get an error message saying that the adb.exe file cannot be found.
Please can anyone help?
Joeb29 said:
When I try to run this I also get an error message saying that the adb.exe file cannot be found.
Please can anyone help?
Click to expand...
Click to collapse
Have you also installed ADB, as well as this software?
I'm also having an issue - I have installed java, java SDK and ADB, so I can now run the data recovery tool. But when I do I'm getting "error:device not found" - am I missing drivers or something? I couldn't get all the way on the ADB configuration, because part of it required me to do something on the device... anyway, looks like the computer isn't recognising the the phone at the moment.
Any help very gratefully received (phone is Samsung Galaxy S2).
joffmeister said:
Have you also installed ADB, as well as this software?
I'm also having an issue - I have installed java, java SDK and ADB, so I can now run the data recovery tool. But when I do I'm getting "error:device not found" - am I missing drivers or something? I couldn't get all the way on the ADB configuration, because part of it required me to do something on the device... anyway, looks like the computer isn't recognising the the phone at the moment.
Any help very gratefully received (phone is Samsung Galaxy S2).
Click to expand...
Click to collapse
I have the same situation right now. Managed to make your program work then I get the "error:device not found". My phone does show up in the computer folder(albeit not in mass storage mode), but isn't that what this program was made to work around?
My phone is a LG Optimus G with a smashed glass... The LCD still displays fine, but I'm stuck at my swipe lock because the digitizer is dead.
Thank you for your help and your wonderful program.
Thanks for this app. My girlfriend broke her screen and digitizer on her Galaxy S4. She never turned USB Debugging mode and has a lock on her screen. When using your app I get the same error when I use adb by itself which is "error: closed". ADB detects my phone but any command I use in ADB or with your app I get that same error.
Do you know how to fix this? Thanks in advance.
Thanks a lot man.
dude this tool is just amazing and does exactly what it promised. I was spending sleepless nights thinking about how to recover my data from my broken galaxy nexus and now that I have it I can rest easy. Seriously can't thank you enough for this. Just joined xda to thank you buddy.:laugh::fingers-crossed:
Getting an error "The system cannot find the path specified."
I start the recovery tool, set eh adb path successfully, and then I get this error. If I try running the recovery to pull the DCIM library I get this:
"error: device not found"
What can I do?
Thanks!
Either way this is an amazing tool, seeing how it helped some people already. :good:
Hi, Seem to have the same problem as many others, Device not found. I cant change to MTP mode on my LG G2.
I hope someone can find a solution to this problem.
Program seems amazing doh.
Hello,
This is really a great tool ! I was wondering if you could add the possibility to recover the external sd card aswell.
Device not found
Tried to recover a Samsung Galaxy S3 mini with a broken screen
I installed adb and RecoverData, run it and then get a "device not found error"
What can I do?
Amazing app. thank you so much :good:
FuzzyMeep Two said:
**UPDATE**
NEW VERSION
Another user was having issues because he had an emulator installed, so I updated the file to give you the choice between an emulator, or device. I intend to update further to allow you to check for and select an individual device, that will come soon..
----------------------------------------------------------------------------------------------------------------
Recently my Galaxy s2's screen smashed, and, after replacing it with a GS4, i realized that many of my pictures were stuck on the internal sd card of the GS2. Being unable to turn on mass storage mode, I made a very simple tool that makes using adb pull a simple, painless process, even for the most computer illiterate of android users. Hope this helps if anyone needs it.
Don't forget to hit "Thanks"
Click to expand...
Click to collapse
Hi, Thank you very musch, It's so usefull for me.. :angel:
Hi there my Huawei LTE watch will be detected by the pc and adb debugging is on - but I can`t trasfer files
Any idea - may be it is a driver issue - but which drivers shall I use
Thanks in advance !
peter7 said:
Hi there my Huawei LTE watch will be detected by the pc and adb debugging is on - but I can`t trasfer files
Any idea - may be it is a driver issue - but which drivers shall I use
Thanks in advance !
Click to expand...
Click to collapse
hello,
you can push and pull by adb command, to transfer files i believe you need root permission.
regards
Hello,
no need for root.
do on PC:
1) install adb driver: http://adbdriver.com/downloads/
2) install adb tool: https://forum.xda-developers.com/sm...tool-android-wear-apk-tools-sideload-t2929177
Make sure adb tool is in same folder as adb (c:\adb\ )
Do on watch
3) preferences >> system >> info >> build number - press 10x to enable developer options
4) developer options >> enable ADB debugging
Now connect the watch to the PC and start the tool. It should be able to connect to the watch and you can install apk's with the tool.
Unfortunately it doesnt work for all apps, just try out.
I installed: simple radio, rpi automation, volume manager, floating toucher.
Hope it helps
regards
reiko
and where are the apk`s for the huawei watch 2
Which apk's do you mean?
You can install any apk...no dedicated huawei watch 2 ones.
The adb tool let you select the apk from any location/folder.
Just try it.
Does this answer your question?
Thanks!
Where do I get the ADB tool from? Do I need to download the full android studio? Do I then need to put the adb.exe into c:\adb\? I've used this tool: https://forum.xda-developers.com/showthread.php?p=42407269#post42407269 and put the adb.exe under c:\adb\, but it doesn't work.. The command adb doesn't work btw.
Thanks again!
Hello,
no need for android studio.
downloads tool + adb driver -> see my post "do on PC".
Obviously my adb driver must already on the watch ...so I did what you referred - but when I click connect to the watch nnothing happens - on the other side the PC is showing LEO ...the watch ....
Ok now I copied the adb driver in c:/adb but still the same result: watch is connected but the apk tool says you must first connect the watch ....
Pls see attached the log file
reikow said:
Hello,
no need for root.
do on PC:
1) install adb driver: http://adbdriver.com/downloads/
2) install adb tool: https://forum.xda-developers.com/sm...tool-android-wear-apk-tools-sideload-t2929177
Make sure adb tool is in same folder as adb (c:\adb\ )
Do on watch
3) preferences >> system >> info >> build number - press 10x to enable developer options
4) developer options >> enable ADB debugging
Now connect the watch to the PC and start the tool. It should be able to connect to the watch and you can install apk's with the tool.
Unfortunately it doesnt work for all apps, just try out.
I installed: simple radio, rpi automation, volume manager, floating toucher.
Hope it helps
regards
reiko
Click to expand...
Click to collapse
nothing to complain about the tool, but if is just to install apk, adb install is really very easy. if you need to delete apk, you can do directly by watch....
regards
reikow said:
Hello,
no need for root.
do on PC:
1) install adb driver: http://adbdriver.com/downloads/
2) install adb tool: https://forum.xda-developers.com/sm...tool-android-wear-apk-tools-sideload-t2929177
Make sure adb tool is in same folder as adb (c:\adb\ )
Do on watch
3) preferences >> system >> info >> build number - press 10x to enable developer options
4) developer options >> enable ADB debugging
Now connect the watch to the PC and start the tool. It should be able to connect to the watch and you can install apk's with the tool.
Unfortunately it doesnt work for all apps, just try out.
I installed: simple radio, rpi automation, volume manager, floating toucher.
Hope it helps
regards
reiko
Click to expand...
Click to collapse
those apks you have installed -any good for this watch?
---------- Post added at 06:56 PM ---------- Previous post was at 06:52 PM ----------
looking for some ideas for programs to install -that can run as standalone programs as i'm using as LTE device at moment
This worked for me.
Ok....new to the smartwatch ROM flashing scene...NOOB alert...lol. How exactly do you 'connect' your smartwatch to a PC? USB cable from charge base to PC and the watch just sits on the wireless stand? That's it?
I'm not rooted, can use adb Wi-Fi though, to even sideload apk files which I have.
For ordinary file transfer, installing the app NavExplorer on both the watch and phone makes file transfer easy. If I remember, long press on files on watch for command options.
Unfortunately I could not find a guide on the bluboo s8 root. anyone help me?
Help to root and change launcher.
That would be awesome. Also, can anyone tell me how to change the launcher? It seems it's protected and I cannot use Nova by defect. Always the factory one comes back.
Thanks in advance...
I tried kingroot but it failed. The bluboo's s8 360 os is a little bit anoying. Especialy the big icons and screen size. A root will make te phone worth buying it. now its just a phone my moms woud like. (Maybe thats a compliment.)
i tryed by: Rootkhp Pro not function
kingroot not function
root genius not function
one click root nothing !!
any news ?
I do not understand the language, maybe that helps
https://4pda.ru/forum/index.php?showtopic=831334&st=1960#entry65454219
I don't have my hands on mine yet (Monday Oct 2nd)so I can't say one way or the other if this will work but I found that the Bluboo Maya uses the same 360 GUI and there is program called rootkhp.pro (i would post a link but it wont let me) that can root that phone so maybe let cross reference anything that can root the bluboo Maya and it may give us some solid leads into rooting the S8 so anyone know anything about the Maya or that rootkhp program I opened it up and seem to be running on my ubuntu desktop I'm going threw the code and from what seen in other root programs it looking very run of the mill. Anyone know of any other phones running this 360 OS?
Probably, your boot loader is locked.
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.
Augustoandro said:
Probably, your boot loader is locked.
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.
Click to expand...
Click to collapse
I can open bootloader, but when my phone in fastboot mode not detected in PC.
any solution ?
Here trick for change homescreen.
Install Apus Launcher - Apus Setting - Set as default launcher - choose your launcher
it work for me, but just temporary. after you restart your phone, you must do this again.
Your guide do not function, beacuse when unlock bootloader do not recognize the phone
Finally Bluboo S8 Rooted
evoin said:
That would be awesome. Also, can anyone tell me how to change the launcher? It seems it's protected and I cannot use Nova by defect. Always the factory one comes back.
Thanks in advance...
Click to expand...
Click to collapse
Here Check my thread, i was find a way to root Bluboo S8
https://forum.xda-developers.com/general/rooting-roms/guide-root-bluboo-s8-systemless-root-t3682560
prydmus said:
Here Check my thread, i was find a way to root Bluboo S8
https://forum.xda-developers.com/general/rooting-roms/guide-root-bluboo-s8-systemless-root-t3682560
Click to expand...
Click to collapse
This method works! MY GOOGLE NOW LAUNCHER FINALLY IS THERE! After rooting my Bluboo S8 I installed app for uninstalling system aps, you have to uninstall "Initiator", then after rebooting you can choose between launchers installed on your phone!
thanks it works perfect
Didn't work for me. How did you guys do it? Did you use an old version of SP flash tool or did you use a different OS cause I am using windows 10.
EDIT:
I also used arch linux and get the same error which is something about a preloader invalid or something.
Dont work for me
Dont work in my phone.
BROM ERROR: STAUS_DEVICE_CTRL_EXCEPTION (0XC0050001)
Edit: I access to the phone via USB without problems. Also install Windows_10_MTK_VCOM_USB_Preloader_Drivers. And the USB is in debugging mode.
Probed all usb ports of my computer. Same error all times.
Some problem the procedure don t work
BROM ERROR: STAUS_DEVICE_CTRL_EXCEPTION (0XC0050001)
In this procedure di not specific if debug USB is enable? And the bootloader in the developement menù. Please post a video o a detailed procedure thanks
No Root Needed
Hey guys, I managed to mimic most of the features of Galaxy s8 without rooting bluboo s8..
Check this video.,,
Transform Bluboo s8 to Samsung s8 by "Perfectionist Ashmi" in youtube..
I can't able to post links in this thread...
hope it helps...
Bluboo S8 launcher change - No root
Hi
Woukd like to share a way to switch Bluboo S8 launcher to another one.
1. On Google Play store, download and install iLauncher X or S+ Launcher
2. Start iLauncher X and goto Preferences icon.
3. You will see an button called "set as default". Swipe it ON and you will be able to select any launcher installed in your Bluboo S8 and set it as default.
Seems to work with S+ Launcher as well.
This works but does not survive to reboot.
Hope this helps.
Lila.
any of you tried to install magisk? because i tried it with flashify but it does not work.
And busybox do not install , this type of root is limited for me.
Check the video for Transforming bluboo S8 to Samsung s8 exactly.!!! By using launchers and No ROOT
[https://youtu.be/IDjrEsk468Y]
Hope it helps .!! Good day .!!
Remove [ and ] from the above link
Hello Everyone,
I would like to learn how to remove bloatware Apps from my Android phone.
I have tried using "ADB commands" but for some reason my computer doesn't recognize/find my Android phone when I connect it to it.
Please help.
Thanks in advance
Download drivers for samsung and enabled adb developer option then type following "adb devices" press enter and should see serial number indicating phone connected via adb
petiolarissean said:
Download drivers for samsung and enabled adb developer option then type following "adb devices" press enter and should see serial number indicating phone connected via adb
Click to expand...
Click to collapse
Hello, and Thanks
I have done that exactly, but it still doesn't work.
And I can't figure out why is not working.
I have installed the Samsung driver, allowed the ADB function on my phone from "Developer Options" etc.
In addition to the advices by petiolarissean , check whether the driver works well, please.
In the 'Devices Manager' of your Windows, check the driver for your Android phone.
If this doesn't work yet, change an usb cable and then try again.
Only to have mentioned it:
So-called bloatware typically is housed in Android's locations /system and/or /system/priv--apps what only can get accessed by Android's root-user after successfully mounted as RW.
James_Watson said:
In addition to the advices by petiolarissean , check whether the driver works well, please.
In the 'Devices Manager' of your Windows, check the driver for your Android phone.
If this doesn't work yet, change an usb cable and then try again.
Click to expand...
Click to collapse
Thanks for your help
I think I will buy a new USB cable and give it a try, hopefully it will work.
Have a nice day
Sorry late reply.I have like 5 different phone.Hard core modder.
This question help alot
Even though you csnt get adb working
Can you still move files from your phone to pc or computer.Or nothing ay all.Your answr will tell me your problem