Related
Hi,
I have a Windows XP SP3 (i386) that just won't let me use ADB. It doesn't work in ways I will describe shortly, and it never worked, on none of the ROMs I had. I had four roms in total in the past 3 weeks: Rooted original 2.1, non rooted JPM, rooted Kyrillos 3.0 and now I run rooted Lestatious 2.0 Build 1.2.6, akin' to go for 1.7.0.
I am primarily a Linux user (fedora 14 x86_64), and adb works fine for me there. As does ADB over WiFi (both Linux and Windows). For all my needs so far, Linux was enough, ODIN worked from the start, so I never bothered to find what's wrong with the Windows' adb.
But trying out Lestatious, I now have the need to update the rom using Windows, and it wouldn't be bad at all to use some other already prepared scripts for Windows I stumple upon on the forums.
As far as drivers go, I have the freshest Kies installed. I have the necessary Android SDK parts installed. Debugging mode is selected on the phone.
Actually, I am at the point where I have the WHOLE Android SDK installed, and have spent way more time on researching and googling and debugging than I would've needed to convert Lestatious' batch scripts into bash ones. And almost literally, pulling my hair out.
I'm no total noob when it comes to flashing/hacking/rooting/modding devices. I've even done my own Pandora battery switch mod for PSP for God's sake!
But this just stumps me....completely.
All this behaves the same, no matter what combination of starting and killing adb I do, pulling cable out, disabling debugging mode, plugging in, unplugging, enabling debugging, plugging in, etc. It also makes no difference whether I use Android SDK adb or, let's say, Lestatious' supplied adb.
Also note that I have both tools and platform-tools folder in my PATH variable.
Code:
C:\>adb kill-server
C:\>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\>adb devices
List of devices attached
myserialno;-) device
C:\>adb remount
error: protocol fault (status 72 65 6d 6f?!)
C:\>adb shell df
error: protocol fault (status 2f 64 65 76?!)
C:\>adb shell ls
error: protocol fault (status 73 71 6c 69?!)
C:\>adb root
error: protocol fault (status 61 64 62 64?!)
Although it does give me protocol fault, the device does disconnect/reconnect:
Code:
C:\>adb usb
error: protocol fault (status 72 65 73 74?!)
Phone does reboot:
Code:
C:\>adb reboot
error: protocol fault (no status)
Have to break this one, because it never returns:
Code:
C:\>adb shell
^C
Any help will be greatly appreciated.
Thank you.
can i post reply?
[email protected] said:
can i post reply?
Click to expand...
Click to collapse
STOP! NOW!
Sent from my ACID Lestatious 2.0 BUILD 1.7 Galaxy 3 FROYO
Sounds like a Samsung USB driver issue to me. Make sure you got the right ones. Are you using 64-bit or 32-bit windows?
Thom47 said:
Sounds like a Samsung USB driver issue to me. Make sure you got the right ones. Are you using 64-bit or 32-bit windows?
Click to expand...
Click to collapse
Thanks for taking interest in my problem.
I'm using 32-bit Windows XP (with SP3).
I did not fiddle with any drivers, I would if I found any . The drivers were installed with the Samsung Kies software. I also tried uninstalling and installing Kies. The Kies is version Kies_2.0.0.11032_12_9.exe downloaded from UK Samsung Support for Galaxy i5800.
Just to be sure, and because I have access to two completely identical machines (yes, hardware and software is the same, except the Android part).
On one machine I have the complete Android SDK, earlier version of Kies (updated yesterday to the latest version).
On the second machine I have only the latest Kies (never updated, installed it this morning). And no SDK, just Lestatious' adb.exe and AdbWinApi.dll.
The behavior stays the same.
Thanks
Well, try these. They're Samsung's USB drivers for our phone. If possible, try starting from the beginning eg. remove all traces of KIES and your phone, and then apply the downloaded driver. By this I mean "uninstall" the phone from your computer.
Thom47 said:
Well, try these. They're Samsung's USB drivers for our phone. If possible, try starting from the beginning eg. remove all traces of KIES and your phone, and then apply the downloaded driver. By this I mean "uninstall" the phone from your computer.
Click to expand...
Click to collapse
Thanks. I will try it as soon as I get home from work.
Thanks again.
Thom47 said:
Well, try these. They're Samsung's USB drivers for our phone. If possible, try starting from the beginning eg. remove all traces of KIES and your phone, and then apply the downloaded driver. By this I mean "uninstall" the phone from your computer.
Click to expand...
Click to collapse
So, I used usbdeview to uninstall the device first. Then I uninstalled Samsung Kies. And finally Samsung USB drivers that get installed with Kies automatically.
I rebooted, just to be sure. Installed the drivers linked in Thom47's post, and rebooted again.
I ran the adb start-server. Connected my device (which was correctly recognized, just as before). The end result is the same. Although status gives a bit different numbers:
Code:
C:\Documents and Settings\Miki>adb shell ls
error: protocol fault (status 1b 5b 31 3b?!)
C:\Documents and Settings\Miki>adb shell
^C
But looking at the adb client source code, I see that the numbers represent 4 Bytes of data read from some file descriptor when getting adb status. It's a bit too late to follow up what file descriptor, but as readx (used to transfer the first 4B from file descriptor into buffer) is sometimes used for reading device drivers because of its portability, this definitely points a finger to some sort of driver issue.
Just thought that it might help to list connected devices when the phone is plugged in (debugging mode, of course):
ADB Interface->Samsung Android Composite ADB Interface
Disk Drives->SAMSUNG GT-I5800 Card USB Device
Modems->Samsung Android USB Modem (is this supposed to be here?)
USB Controllers->SAMSUNG Android USB composite device
Click to expand...
Click to collapse
Update: I just quickly skimmed through the code to see what is the file descriptor, and it's actually just a socket connection to ADB port. So, if I understood it correctly, the first 4B read by readx are reply from the device (?!). Still could be driver related in my opinion.
Thanks
Right, well that's where my knowledge on linux and stuff ends, so I think you should make a new thread to some general forum, since this might not be related to our phone only.
Will do. Thanks for the help.
--
Sent from my GT-I5800
OK I really need some help and info here. Ive done some searching around on here and other sites, and found what seems to be the only method to fix my phone ... http://forum.xda-developers.com/showthread.php?t=2582142 ... I feel fairly confident that I can accomplish this method. Although im not running ubuntu but rather kali.
My device had the vzw-vs980-27a.kdz and rooted by stumproot.apk. and the other morning verizon pushed the lollipop ota and now my phone is stuck in the secure boot error fastboot. It fits all the signs as described in the fix it post.
Questions:
1. Since i was on 27A and the files provided in the link only go up to 24A, I was wondering if I could use the 24A image files or will they further break my phone?
2. I was able to find a 27A bootstack zip via https://www.androidfilehost.com/?fid=95916177934539347... the only thing is the bootstack files in the zip are .bin files and the instructions call for .img files.
are these two interchangeable? if not can i use the 24A to fix my phone or can some one direct me to a link where i can find the 27A .img files.
Any and all help and input are greatly appreciated.
REALLY NEED HELP!
I cant get my linux system to recognize the phone but when i plug it into a windows system it recognizes it as a unkown device. but i cant upate the driver to a adb driver or fastboot driver
and i cant even turn the phone on or off no matter what button config i try
anyone?
a.perkins89 said:
Although im not running ubuntu but rather kali.
Click to expand...
Click to collapse
It shouldn't matter that you're running Kali instead of Ubuntu. As long as you have the required files: /bin/ls, /sbin/gdisk and /bin/dd you're good to go. You can confirm the location of the binary commands by running the whereis command followed by ls, gdisk, and dd respectively.
If you're having trouble mounting your device or getting it recognized, consider using a more user friendly environment like Ubuntu. Kali is great for forensics and pen-testing but using it to communicate with your phone probably isn't the best choice, it may have missing dependencies.
a.perkins89 said:
I was able to find a 27A bootstack zip via https://www.androidfilehost.com/?fid=95916177934539347... the only thing is the bootstack files in the zip are .bin files and the instructions call for .img files. Are these two interchangeable?
Click to expand...
Click to collapse
Yes they are. Rename all the .bin files to .img and continue from there.
Good luck!
a.perkins89 said:
REALLY NEED HELP!
I cant get my linux system to recognize the phone but when i plug it into a windows system it recognizes it as a unkown device. but i cant upate the driver to a adb driver or fastboot driver
and i cant even turn the phone on or off no matter what button config i try
Click to expand...
Click to collapse
Plug your phone in and type "dmesg" in linux. Paste the output on pastebin.com and link it here.
I'm suspecting you are in a QH USB 9008 error. First of all - dont panic. I have successfully recovered from a 9008 error - but it is a longer process (and it may involve you paying someone 30$).
But first, let us confirm.
I have this problem too, my PC wont recognize that its a phone connected it reads "Unknown Device" on WINdows but when i plug it in the computer with Ubuntu it reads nothing. no 9008 error nothing at all. What do i do? do i have to replace the usb port? cant i just use someone elses same exact usb rig and flash and put my old one back? my current one only works if i clean it with alchohal wait 10 minutes to dry then i plug it into my pc and it detects and if i dont then my pc wont see that theirs something connected to it.
d00lz said:
It shouldn't matter that you're running Kali instead of Ubuntu. As long as you have the required files: /bin/ls, /sbin/gdisk and /bin/dd you're good to go. You can confirm the location of the binary commands by running the whereis command followed by ls, gdisk, and dd respectively.
If you're having trouble mounting your device or getting it recognized, consider using a more user friendly environment like Ubuntu. Kali is great for forensics and pen-testing but using it to communicate with your phone probably isn't the best choice, it may have missing dependencies.
Yes they are. Rename all the .bin files to .img and continue from there.
Good luck!
Click to expand...
Click to collapse
Thank you, I was kind of thinking they were interchangeable, just didn't want to assume and possibly screw the device up some more.
sandys1 said:
Plug your phone in and type "dmesg" in linux. Paste the output on pastebin.com and link it here.
I'm suspecting you are in a QH USB 9008 error. First of all - dont panic. I have successfully recovered from a 9008 error - but it is a longer process (and it may involve you paying someone 30$).
But first, let us confirm.
Click to expand...
Click to collapse
Ok, here it is.. pastebin.com/CH6HqSCT.. Once again thank you for any help you can offer.. This really couldn't have happened to me at a more inconvenient time... I literally just had to get on the search for a new job and dropped my resume' at like 20 places within the few days before my phone dying.
a.perkins89 said:
Thank you, I was kind of thinking they were interchangeable, just didn't want to assume and possibly screw the device up some more.
Ok, here it is.. pastebin.com/CH6HqSCT.. Once again thank you for any help you can offer.. This really couldn't have happened to me at a more inconvenient time... I literally just had to get on the search for a new job and dropped my resume' at like 20 places within the few days before my phone dying.
Click to expand...
Click to collapse
Please plug your device into the USB slot and type the following,
Code:
lsusb
Please reply with the output.
d00lz said:
Please plug your device into the USB slot and type the following,
Code:
lsusb
Please reply with the output.
Click to expand...
Click to collapse
Bus 003 Device 006: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
Bus 003 Device 004: ID 04f2:b230 Chicony Electronics Co., Ltd Integrated HP HD Webcam
Bus 003 Device 003: ID 0781:5530 SanDisk Corp. Cruzer
Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 097: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 138a:003c Validity Sensors, Inc. VFS471 Fingerprint Reader
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
a.perkins89 said:
Bus 003 Device 006: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
Bus 003 Device 004: ID 04f2:b230 Chicony Electronics Co., Ltd Integrated HP HD Webcam
Bus 003 Device 003: ID 0781:5530 SanDisk Corp. Cruzer
Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 097: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 138a:003c Validity Sensors, Inc. VFS471 Fingerprint Reader
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Click to expand...
Click to collapse
Looks like your device is getting detected at least.
Code:
Bus 002 Device 097: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Please confirm this by unplugging your device and running lsusb again and comparing the output.
I urge you to stop using Kali for this and try Ubuntu btw .
yes, when i unplug the phone from the machine and run the command again. Qualcomm no longer shows up, and of course, comes back upon re-attaching
a.perkins89 said:
Thank you, I was kind of thinking they were interchangeable, just didn't want to assume and possibly screw the device up some more.
Ok, here it is.. pastebin.com/CH6HqSCT.. Once again thank you for any help you can offer.. This really couldn't have happened to me at a more inconvenient time... I literally just had to get on the search for a new job and dropped my resume' at like 20 places within the few days before my phone dying.
Click to expand...
Click to collapse
Code:
[ 173.880606] usb 2-1: New USB device found, idVendor=05c6, [B]idProduct=9008[/B]
[ 173.880619] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 173.880625] usb 2-1: Product: QHSUSB__BULK
[ 173.880629] usb 2-1: Manufacturer: Qualcomm CDMA Technologies MSM
[ 173.881813] qcserial 2-1:1.0: Qualcomm USB modem converter detected
[ 173.882151] usb 2-1: Qualcomm USB modem converter now attached to ttyUSB0
Unfortunately, you are in QH USB 9008 mode . so now you are in a more complicated way to recover. I suggest you first read this http://www.reddit.com/r/Android/comments/2p8ju4/xpost_rlgg2_the_lg_g2_is_unbrickable_a_story_of/
Then I suggest you download the TOT files and KDZ files for your phone - please be VERY careful in choosing your TOT and KDZ.
Then I also suggest to download the KDZ extractor in python form . Then extract the image files from the KDZ by running
Code:
python KDZFileTools.py -f ../D80110A_00.kdz -x
python DZFileTools.py -f kdzextracted/D80110a_00.dz -x
So now, you have 3 things - TOT file, KDZ file and extracted image files. Also you need to open the back cover of your phone and figure out how to disconnect the battery (it is a small button like thing). Very easy stuff. All of this is a pre-requisite to unbricking your phone.
Now you have two choices - pay someone to connect to a Windows computer (search for tungkick on this forum) or to use this. I would say, use the second one first ... and then decide to pay or not. FYI - when I unbricked, I didnt have access to the second tool so I had to pay Tungkick.
Hope this helps.
sandys1 said:
Code:
[ 173.880606] usb 2-1: New USB device found, idVendor=05c6, [B]idProduct=9008[/B]
[ 173.880619] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 173.880625] usb 2-1: Product: QHSUSB__BULK
[ 173.880629] usb 2-1: Manufacturer: Qualcomm CDMA Technologies MSM
[ 173.881813] qcserial 2-1:1.0: Qualcomm USB modem converter detected
[ 173.882151] usb 2-1: Qualcomm USB modem converter now attached to ttyUSB0
Unfortunately, you are in QH USB 9008 mode . so now you are in a more complicated way to recover. I suggest you first read this http://www.reddit.com/r/Android/comments/2p8ju4/xpost_rlgg2_the_lg_g2_is_unbrickable_a_story_of/
Then I suggest you download the TOT files and KDZ files for your phone - please be VERY careful in choosing your TOT and KDZ.
Then I also suggest to download the KDZ extractor in python form . Then extract the image files from the KDZ by running
Code:
python KDZFileTools.py -f ../D80110A_00.kdz -x
python DZFileTools.py -f kdzextracted/D80110a_00.dz -x
So now, you have 3 things - TOT file, KDZ file and extracted image files. Also you need to open the back cover of your phone and figure out how to disconnect the battery (it is a small button like thing). Very easy stuff. All of this is a pre-requisite to unbricking your phone.
Now you have two choices - pay someone to connect to a Windows computer (search for tungkick on this forum) or to use this. I would say, use the second one first ... and then decide to pay or not. FYI - when I unbricked, I didnt have access to the second tool so I had to pay Tungkick.
Hope this helps.
Click to expand...
Click to collapse
I can't seem to get the tool to work. Iv downloaded a . tot file from storagecow.eu/index.php?dir=Xda%2FLG+G2%2FStock%2FVerizon%2FTOT+Method%2F.. and when trying to run the first step the tool program stops responding
ok i got that figured out, now im stuck on the second step.. when i try to test ap and emmc i get a serial port open message... dont know wgat to do, and i cant really understand the steps in the second image of the guide
a.perkins89 said:
ok i got that figured out, now im stuck on the second step.. when i try to test ap and emmc i get a serial port open message... dont know wgat to do, and i cant really understand the steps in the second image of the guide
Click to expand...
Click to collapse
I suggest you ask on http://forum.xda-developers.com/lg-g2/general/tool-unbrick-lg-g2-qualcomm-9008-board-t3072073 - I'm not really sure what is the way to use this software.
Hi Everyone:
I am sorry if someone asked this question before, but I could not find an answer that works for me. I just got my phone today and I want to root it. I am planning to use my laptop running Linux FC21. I have used adb on this machine before and it has work flawlessly. Here is what I have done:
- became a developer on the phone
- enabled usb debugging
- enabled OEM unlocking
- connected the phone to my computer.
- I get a notification on the phone saying "USB debugging connected"- typed 'sudo adb devices'
- The list is empty.
I have tried stopping and starting the sever with no effect. I have tried multiple USB ports and cables (USB-A to USB-C). That did not help. I have looked at dmesg and it sees the phone.
Code:
[email protected] ~] dmesg | tail
[ 1650.391982] usb 1-3: Product: PH-1
[ 1650.391984] usb 1-3: Manufacturer: Essential Products
[ 1650.391985] usb 1-3: SerialNumber: PM1LHMA792600274
[ 2128.638511] usb 1-3: USB disconnect, device number 16
[ 2133.666971] usb 1-3: new high-speed USB device number 17 using xhci_hcd
[ 2133.835601] usb 1-3: New USB device found, idVendor=2e17, idProduct=c032
[ 2133.835614] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2133.835617] usb 1-3: Product: PH-1
[ 2133.835618] usb 1-3: Manufacturer: Essential Products
[ 2133.835620] usb 1-3: SerialNumber: PM1LHMA792600274
Finally I have downloaded 51-android.rules from the web and added the line:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="2e17", ATTR{idProduct}=="c032", MODE="0600", OWNER="hal"
This did not help either.
So, HELP!
Thanks
----
EDIT: I tried both my Galaxy Note4 and my Zenwatch3 and they both worked.
----
EDIT: The phone never shows the popup asking if I want to authorize my computer.
Mine wouldn't show the authorization pop up until after I killed the adb server with the phone connected.
So I connected the phone, did adb devices and nothing came back, then killed adb server, restart server, then it have the RSA authorization pop-up, and it showed up in adb devices after that.
I find I need to kill and restart the ADB server every time I connect if want it to work. But it doesn't need to authorize each time. Just the first time.
NaterTots said:
Mine wouldn't show the authorization pop up until after I killed the adb server with the phone connected.
So I connected the phone, did adb devices and nothing came back, then killed adb server, restart server, then it have the RSA authorization pop-up, and it showed up in adb devices after that.
I find I need to kill and restart the ADB server every time I connect if want it to work. But it doesn't need to authorize each time. Just the first time.
Click to expand...
Click to collapse
Thanks for the reply. Unfortunately, this did not work for me.
Have you tried leading your commands with ./?
This is required on Mac: ./adb devices
Airwolf79 said:
Have you tried leading your commands with ./?
This is required on Mac: ./adb devices
Click to expand...
Click to collapse
No, that will not make a difference. The $path is set correctly on the machine. If what you suggested was an issue, I would get "adb: Command not found" when I tried to execute it.
Thanks for the suggestion!
Do you have lastest ADB?
Sent from my PH-1 using XDA Labs
avd said:
Do you have lastest ADB?
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
Well, I have been working this and I think that you identified the problem. I have the most up-to-date for my OS, but it is old and I can't get newer versions to work. I had to move on to Windows :crying:
The instructions I found suggested creating a user group and adding myself to it:
Code:
sudo groupadd androiddev
sudo usermod -aG androiddev your_login_name
Then grant the permissions to that group rather than directly to my user account:
Code:
sudo sh -c "echo 'SUBSYSTEM=="usb",ATTR{idVendor}=="2e17", ATTR{idProduct}=="c032", MODE="0666", GROUP="androiddev"' >> /etc/udev/rules.d/51-android.rules"
I have no idea if that's necessary, but it worked for me. I had to log out and back in before it worked. This is on Fedora 27.
bjs339 said:
The instructions I found suggested creating a user group and adding myself to it:
Then grant the permissions to that group rather than directly to my user account:
I have no idea if that's necessary, but it worked for me. I had to log out and back in before it worked. This is on Fedora 27.
Click to expand...
Click to collapse
When you run fastboot run it as super user.
Modify the flashall and prepend sudo in front of every line
Sent from my PH-1 using XDA Labs
Mine has never seen my device when running adb devices,however commands to give write permission still worked
Sent from my Essential Phone using XDA Labs
Hi all! I am attempting at the end of this project to have Dirty Unicorns running on my device, but I am having a rough time just trying to get the boot loader unlocked.
1st OS: Ubuntu 16.04
I had android-tools-fastboot and adb installed. The phone has developer options and USB debugging turned on.
I started the phone in fastboot(volume down + power), I see the droid bot with the 'hood open' It states to connect the USB cable. I have the USB cable connected to a USB 2.0 port.
Phone states that the USB is connected. From the computer's log:
[Thu Dec 27 11:13:50 2018] usb 1-1: new high-speed USB device number 10 using ehci-pci
[Thu Dec 27 11:13:50 2018] usb 1-1: New USB device found, idVendor=22b8, idProduct=2e80
[Thu Dec 27 11:13:50 2018] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Thu Dec 27 11:13:50 2018] usb 1-1: Product: Fastboot potter S
[Thu Dec 27 11:13:50 2018] usb 1-1: Manufacturer: Motorola Inc.
[Thu Dec 27 11:13:50 2018] usb 1-1: SerialNumber: ZY224G4BVW
So it is seeing it.
When I run sudo adb devices(ran with and without sudo) all I get is "List of devices attached" with nothing listed.
Did some searching(most of the posts are about WIndows) and found this
I implemented those rules and restarted the services, but the permissions never changed. - and yes I changed OWNER= to my username.
So I say, let's try Windows. I have a Win10 machine here. I first go here to download the driver, but when I click on either link at the bottom of the Windows column(32bit or 64bit) It sends me to a page that states "There has been an error with your request." If I click the Mac link, it starts a download. Could you try to test the download link?
I contacted Moto about this and the reply was that I needed to be using Chrome. I have tried FF, Chrome, Opero, IE and Egde. I have tried it from home, work and mobile data, all with the same result.
Could someone help me out here? These pretzels are making me thirsty!
Thanks!
Don't worry about
Code:
adb devices
not showing, you will be using fastboot for the unlocking steps. Type
Code:
fastboot devices
and it should show your devices #. You can then follow the steps for getting unlock code and unlock the bootloader.
[email protected] said:
Don't worry about
Code:
adb devices
not showing, you will be using fastboot for the unlocking steps. Type
Code:
fastboot devices
and it should show your devices #. You can then follow the steps for getting unlock code and unlock the bootloader.
Click to expand...
Click to collapse
Appreciate the reply.
fastboot devices also returns nothing
TheFlashNewb said:
Don't worry about not showing, you will be using fastboot for the unlocking steps. Type
Appreciate the reply.
fastboot devices also returns nothing
Click to expand...
Click to collapse
You need to install Motorola driver to get device. Here is the link from my gdrive to download it:-https://drive.google.com/file/d/1silF8KibEfODhRt7j0twUNI_GLsnKvOW/view?usp=drivesdk
Then all command will run and you need to enable OEM unlock in developers options. So you can unlock your bootloader.
TheFlashNewb said:
Hi all! I am attempting at the end of this project to have Dirty Unicorns running on my device, but I am having a rough time just trying to get the boot loader unlocked.
1st OS: Ubuntu 16.04
...................................
...................................................
Could someone help me out here? These pretzels are making me thirsty!
Thanks!
Click to expand...
Click to collapse
On a Linux distro, like my Debian, we must add "rules" to udev to make your devices discoverable:
1) create a new file in /etc/udev/rules.d called "51-android.rules".
2)copy the following content:
Code:
#adb mode
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="685c", MODE="0666", GROUP="plugdev"
#fastboot mode
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="685c", MODE="0666", GROUP="plugdev"
3) Replace 04e8 and 685c with your usb address. Run the command
Code:
lsusb
TWICE!!
The first time with adb debug ON (grab the usb address, the second time in the fastboot mode).
You'll get 2 different usb address.
4) make sure your user is in the group "plugdev".
5) restart udev as root with:
Code:
service udev restart
6) Then try with usual commands:
Code:
adb devices or fastboot devices
1st off I appreciate all of your input and help!
On a third computer with Lubuntu installed I finally got it to work! Had to use sudo (which did not work on the Ubuntu install).
Well here I go, wish me luck!
Just for a refresher:
#1 - Unlock through Motorola(no backup needed - phone has never been used)
#2 - Install TWRP
#3 - Reboot into recovery - if I don't I will have to reinstall TWRP
#4 - Flash ROM(Dirty Unicorns potter), then flash gapps
(Question - Should I use the Gapps package from the OpenGapps website or the one on the Dirty Unicorns page?)
#5 - Have fun!
Thanks!
TheFlashNewb said:
1st off I appreciate all of your input and help!
On a third computer with Lubuntu installed I finally got it to work! Had to use sudo (which did not work on the Ubuntu install).
Well here I go, wish me luck!
Just for a refresher:
#1 - Unlock through Motorola(no backup needed - phone has never been used)
#2 - Install TWRP
#3 - Reboot into recovery - if I don't I will have to reinstall TWRP
#4 - Flash ROM(Dirty Unicorns potter), then flash gapps
(Question - Should I use the Gapps package from the OpenGapps website or the one on the Dirty Unicorns page?)
#5 - Have fun!
Thanks!
Click to expand...
Click to collapse
You can use opengapps they recommend to use stock gapps as it doesn't have inbuilt AOSP apps. Means it doesn't have dialer , contacts , message , clock , calculator , default browser app.
sinchan_nohara said:
You can use opengapps they recommend to use stock gapps as it doesn't have inbuilt AOSP apps. Means it doesn't have dialer , contacts , message , clock , calculator , default browser app.
Click to expand...
Click to collapse
Thanks for the reply!
On wiping, which partitions should I wipe before installing the ROM? The phone is currently stock and updated to 8.1.
TheFlashNewb said:
Thanks for the reply!
On wiping, which partitions should I wipe before installing the ROM? The phone is currently stock and updated to 8.1.
Click to expand...
Click to collapse
Cache , dalvic cache , system and data. But before doing anything take backup of efs and persist and keep it safe somewhere in cloud or your PC or both. It would be helpful in future if by chance you messed up your device and lost IMEI.
sinchan_nohara said:
Cache , dalvic cache , system and data. But before doing anything take backup of efs and persist and keep it safe somewhere in cloud or your PC or both. It would be helpful in future if by chance you messed up your device and lost IMEI.
Click to expand...
Click to collapse
Oh wow thanks! Does the stock TWRP for potter(from the TWRP website) have an option to backup those partitions? I cannot find an answer. V 3.2.3-1-potter
Also, does it need to be rooted in order to backup EFS and persist?
TheFlashNewb said:
Oh wow thanks! Does the stock TWRP for potter(from the TWRP website) have an option to backup those partitions? I cannot find an answer. V 3.2.3-1-potter
Also, does it need to be rooted in order to backup EFS and persist?
Click to expand...
Click to collapse
Yes twrp has option to backup efs and persist. You don't need root for this.
I've bought one Mi Smart Clock. I love this device: so compact, nice and solid design, a 4inch LCD screen, WiFi and BT capabilities.
There's "too much google" for me, so i'm wondering if it's possible to hack it and run a custom firmware.
Connecting an USB on boot, firstly i got a MediaTek MT65xx Preloader:
Code:
usb 2-2: new high-speed USB device number 22 using xhci_hcd
usb 2-2: New USB device found, idVendor=0e8d, idProduct=2000, bcdDevice= 1.00
usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-2: Product: MT65xx Preloader
usb 2-2: Manufacturer: MediaTek
cdc_acm 2-2:1.0: Zero length descriptor references
cdc_acm: probe of 2-2:1.0 failed with error -22
cdc_acm 2-2:1.1: ttyACM0: USB ACM device
usb 2-2: USB disconnect, device number 22
that send a lot of "READY" to /dev/ttyACM0 device.
After few seconds, it disconnect and connect a:
Code:
usb 2-2: new high-speed USB device number 7 using xhci_hcd
usb 2-2: New USB device found, idVendor=0e8d, idProduct=2008, bcdDevice= 2.23
usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-2: Product: X04G
usb 2-2: Manufacturer: Xiaomi
but i was not able to do something more that configure it as firmware allow.
Anyone already did something? There's any team/group/someone else interested in build an hack for this nice device?
Thanks for any help, really appreciated!
I bought the Chinese version, and its model is slightly different from yours. It is said that this is the overseas version of the Chinese version. I compiled a twrp for this device, not sure if it will work on yours.
GitHub - MaxCaiLC/twrp_xiaomi_lx04_device_tree
Contribute to MaxCaiLC/twrp_xiaomi_lx04_device_tree development by creating an account on GitHub.
github.com
Can you back up your firmware with mtkclient and send it to me? I am interested in this model.
Is there a way to add a custom alarm sound?
Hi!...I also have a LX04 version of the firmware, have you been able to extract the X04G version to be able to update the firmware???
MaxCaiLC said:
I bought the Chinese version, and its model is slightly different from yours. It is said that this is the overseas version of the Chinese version. I compiled a twrp for this device, not sure if it will work on yours.
GitHub - MaxCaiLC/twrp_xiaomi_lx04_device_tree
Contribute to MaxCaiLC/twrp_xiaomi_lx04_device_tree development by creating an account on GitHub.
github.com
Can you back up your firmware with mtkclient and send it to me? I am interested in this model.
Click to expand...
Click to collapse
Did you get the firmware version with google assistant?
TIA
Jordi Escolà said:
Hi!...I also have a LX04 version of the firmware, have you been able to extract the X04G version to be able to update the firmware???
Click to expand...
Click to collapse
I have a device with x04g firmware on it. How can i extract the firmware?