HI!
1. I have an LG H650E Zero and i'm trying to control it using adb in order to pull build.props but with no success.
The system display a " Device not found " message. I've tried every kind of LG drivers but the problem's remaining.
2.Another problem is that when i try to use fastboot a "Failed" message is displayed for any offastboot commands. It's important to mention that my device it's recognized by laptop in fastboot mode.
3. Is there any kind of custom bootloader for this device to be installed?
I'd appreciate any of your help! Thank you in advance.
billyjayserres said:
HI!
1. I have an LG H650E Zero and i'm trying to control it using adb in order to pull build.props but with no success.
The system display a " Device not found " message. I've tried every kind of LG drivers but the problem's remaining.
2.Another problem is that when i try to use fastboot a "Failed" message is displayed for any offastboot commands. It's important to mention that my device it's recognized by laptop in fastboot mode.
3. Is there any kind of custom bootloader for this device to be installed?
I'd appreciate any of your help! Thank you in advance.
Click to expand...
Click to collapse
Greetings!
Thank you for using XDA Assist.
Please consider posting your question in this friendly help thread where you'll find expert advice:
http://forum.xda-developers.com/showthread.php?t=2259645
Good luck!
Related
I have a Moto G 4g. ADB recognizes the cell and I can restart it in fastboot mode, but when I check in the terminal with:
Code:
fastboot devices
Nothing appears, and if I go on with
Code:
fastboot oem get_unlock_data
It gets stuck at
Code:
< waiting for device >
I tried as a user and as root on an Archlinux machine with android-udev rules as shown in the Archlinux wiki (sorry, i can't put the link). AP Fastboot fast boot menu shows that the cell is locked.
Hi,
You can try a different cable, or USB port on the pc...or even a different pc. Until fastboot devices detects your device, there's nothing you can do.
Reinstall drivers...and you are on the bootloader mode right?
If none of that helps, you can ask in your device section for help....
http://forum.xda-developers.com/moto-g/help
Good luck!
Hi
I've tried with a win 7 machine and i got fastboot working on my phone after installing the drivers. Now i'm able to do the thing i want to, but the problem still persist in linux, so i don't know if i close this thread or leave it open for someone who can solve this.
trichocereus said:
Hi
I've tried with a win 7 machine and i got fastboot working on my phone after installing the drivers. Now i'm able to do the thing i want to, but the problem still persist in linux, so i don't know if i close this thread or leave it open for someone who can solve this.
Click to expand...
Click to collapse
Please start one in your section. Xda Assist is here to help navigate the site, not for support.
Thanks!
Hey guys, this is my device: Nothing helped me after googling for 3 hours
Hipstreet Titan 2 tablet (HS-7DTB25)
i edited its vm heap size from 256 to 32... then. here comes the nightmare.... my device wont boot anymore
adb doesn't work to me and also fastboot... adb detects my device when i selected apply update from adb
Here are the reasons:
when i connect my tablet via usb, then booting into recovery, typed in the command window "adb devices" shows nothing
only shows my device when i selected "apply update from Adb"
"adb sideload" command only works,(because in the device list, it shows like this: 09128218345 sideload) bear in mind that the number there is only an example
installing fastboot drivers doesn't help
typing in the command window "fastboot devices" doesn't show any response...
So if nothing worked out.. this means I cannot also install custom recoveries or Roms...? Is my device dead?
Sorry for bad english guyss.. i am noobie so i'm asking for help :laugh:
Any ideas would be appreciated THANKS
streetMovers said:
Hey guys, this is my device: Nothing helped me after googling for 3 hours
Hipstreet Titan 2 tablet (HS-7DTB25)
i edited its vm heap size from 256 to 32... then. here comes the nightmare.... my device wont boot anymore
adb doesn't work to me and also fastboot... adb detects my device when i selected apply update from adb
Here are the reasons:
when i connect my tablet via usb, then booting into recovery, typed in the command window "adb devices" shows nothing
only shows my device when i selected "apply update from Adb"
"adb sideload" command only works,(because in the device list, it shows like this: 09128218345 sideload) bear in mind that the number there is only an example
installing fastboot drivers doesn't help
typing in the command window "fastboot devices" doesn't show any response...
So if nothing worked out.. this means I cannot also install custom recoveries or Roms...? Is my device dead?
Sorry for bad english guyss.. i am noobie so i'm asking for help :laugh:
Any ideas would be appreciated THANKS
Click to expand...
Click to collapse
Hello and thank you for using XDA Assist.
Sorry it took us a while to get back to you, but here is no forum specifically for your tablet. Your best bet is probably to ask your question with all relevant details in the friendly general Android Q&A, Help & Troubleshooting forum at http://forum.xda-developers.com/android/help where members familiar with your device might be able to advise you. Since your device is not widely used, please be patient and give the experts plenty of time to respond.
Good Luck!
Mike B. said:
Hello and thank you for using XDA Assist.
Sorry it took us a while to get back to you, but here is no forum specifically for your tablet. Your best bet is probably to ask your question with all relevant details in the friendly general Android Q&A, Help & Troubleshooting forum at http://forum.xda-developers.com/android/help where members familiar with your device might be able to advise you. Since your device is not widely used, please be patient and give the experts plenty of time to respond.
Good Luck!
Click to expand...
Click to collapse
Thanks for advice
Hi,
I've just reported an issue about a batch using adb commands.
Please, go to see my post where I report the issue and give me some of your enlightenment about it.
This can be summarize in one question:
On win 8.1 x64, is it normal that the adb reboot bootloader command process keeps running in background after the phone has rebooted to bootloader?
If not, what could cause that?
Thanks for your help guys.
Cheers
Hi
Thank you for using XDA Assist.
ADB is a background process. Adding adb kill-server into your batch should do the trick.
If you need further assistance you may ask in the 2 following threads:
http://forum.xda-developers.com/showthread.php?t=2266638
http://forum.xda-developers.com/showthread.php?t=1241935
Good luck.
The screen on my Note 4 is smashed and I'm trying to do a factory reset on my phone using adb with my phone booted to recovery, the phone shows up correctly in windows explorer and I can access the storage just fine, but when I type the command "recovery --wipe_data" in the adb shell, it starts and then gives me a segmentation fault, I've searched the internet and can't seem to find any solution to this. Please can someone assist with this, I thought it would be trivial but it seems far from it!
XDA Visitor said:
The screen on my Note 4 is smashed and I'm trying to do a factory reset on my phone using adb with my phone booted to recovery, the phone shows up correctly in windows explorer and I can access the storage just fine, but when I type the command "recovery --wipe_data" in the adb shell, it starts and then gives me a segmentation fault, I've searched the internet and can't seem to find any solution to this. Please can someone assist with this, I thought it would be trivial but it seems far from it!
Click to expand...
Click to collapse
Hi
Thank you for using xda assist
I would advise you to create an account first and then you can post questions here
http://forum.xda-developers.com/note-4/help/noob-friendly-question-t2866810
for sure experts there can help you on this
thank you.
Hello,
A friend of my asked me to install a new version on his iOcean X8 Mini.
After a few minutes into the process, I discovered that I couldn't modify anything at all.
Problems start occuring when I enter Fastboot via ADB (I power up the phone, connect it to PC, give it permission to use Android USB Debugging, then via 'adb rebeoot fastboot' I enter the Fastboot menu). Every command I enter here returns 3 dots just doing nothing. My command prompt is unusable after entering a command (for example 'fastboot oem unlock').
I've tried to push a ROM via ADB but this isn't working as well since it returns something like 'no permission' when trying to install, but I figured this was due to the locked bootloader.
Searched all over the internet for solutions, but so far nothing has really worked. What I somehow did mange to do is root the device (don't know if it was by default, I assume not), via RootGenius.
Anybody got any experience with this, and perhaps know some steps I can undertake to indeed unlock the bootloader of this phone?
Thanks in advance!
Hello and thank you for using XDA Assist,
please create an account and ask your question in this section. The experts there should know the best about your device.
Kind regards and good luck
Trafalgar Square
XDA Assist