Database Info

[Q] Can someone explain QHUSB_DLOAD to me??

From researching around XDA, it looks like a "mode" either the PC or the phone enters into.... but what does it mean or do?
My problem is that when I plug my device into the laptop, it tries to install the necessary drivers, but states that it "Cannot install QHUSB_DLOAD"...
Any knee-jerk ideas as to why this would be? Is this one the drivers I install with the HTC drivers? I installed the drivers that are in the hasoon2000 post which contains the AIO toolkit. The driver file is called: HTC 3.0.0.007. I was thinking I could install it manually if it was a driver from this file....but I also tried to extract it (thinking I would get the necessary inf or .dll files), but it wouldn't let me extract it.
Any help is appreciated...!

http://www.google.nl/search?hl=en&s...s;..0.0...1ac.1j2.6.mobile-gws-hp.I6MZc5Yffqg
Or
http://www.google.nl/search?q=brick...ZSN0wXvoYHQAw&ved=0CAgQ_AUoAQ&biw=360&bih=567
Verstuurd van mijn HTC One S met Tapatalk

It seems you are in a brick! Do not use unlimited.io's tool, just not yet. That will hamper your efforts to rescue your phone.
Use the unbrickig thread in development. You need an Ubuntu LiveCD / Wubi
Sent from my One S using Tapatalk 2

Well that would make sense. The phone is an old 1S which I took for a swim (inadvertently) and it is damaged (it works, but the display is barely operable). Thankfully, I have a brand new replacement from TMO, but the problem is that I <b>really, really need the contents of my SD card</b> from the damaged phone. Before I go through the unbricking procedure, let me ask... Do you know of any simpler way to recover the contents of the SD?? That's all I need. Them I'm shipping it back to TMO.
Regarding a live Ubuntu CD...I have a dual boot setup but it's a debian distro...but I cannot imagine that would be an issue...but I guess I will find out.
Sent from my HTC VLE_U using xda premium

syntropic said:
Well that would make sense. The phone is an old 1S which I took for a swim (inadvertently) and it is damaged (it works, but the display is barely operable). Thankfully, I have a brand new replacement from TMO, but the problem is that I <b>really, really need the contents of my SD card</b> from the damaged phone. Before I go through the unbricking procedure, let me ask... Do you know of any simpler way to recover the contents of the SD?? That's all I need. Them I'm shipping it back to TMO.
Regarding a live Ubuntu CD...I have a dual boot setup but it's a debian distro...but I cannot imagine that would be an issue...but I guess I will find out.
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
Debian shouldn't really be an issue but I would work with Ubuntu just to be on the safe side. Not sure of a quicker way to rescue the contents of the SD card. Maybe if you enumerate the partitions you can save a copy of the SD card? Not sure though, touch of jobo would be a better person to ask since I am not too experienced with Linux.
I would unbrick it the normal way, unless someone knows otherwise.
Sent from my One S using Tapatalk 2

I wanted to do some testing, but I seem unable to boot into QHSUSB mode. On my other OneS I could do it by holding vol-up while rebooting bootloader, but not anymore.
Look at the downgrade thread. You can skip the step where you have to brick the device.
If you can see your partitions in your devices, you can try and mount the partition directly.
mkdir mydeadsdcard
mount -r -t vfat /dev/hdx36 mydeadsdcard
Chances are you can not see your partitions tho. I think the reason you boot into QHSUSB is that your emmc is defective.
-Jobo

touch of jobo said:
I wanted to do some testing, but I seem unable to boot into QHSUSB mode. On my other OneS I could do it by holding vol-up while rebooting bootloader, but not anymore.
Look at the downgrade thread. You can skip the step where you have to brick the device.
If you can see your partitions in your devices, you can try and mount the partition directly.
mkdir mydeadsdcard
mount -r -t vfat /dev/hdx36 mydeadsdcard
Chances are you can not see your partitions tho. I think the reason you boot into QHSUSB is that your emmc is defective.
Click to expand...
Click to collapse
I actually got it to connect (or I no longer so the QHUSB error). However, when I type adb devices, this is displayed.
C:\HTCOne>adb devices
List of devices attached
HT244W403652 recovery
So.. Is this phone in recovery right now??? (remember my screen is non-functional). And I was running Jellybean 4.2.2 on that phone....I tried "adb pull /mnt/sdcard" "adb pull /storage/sdcard" "adb pull /mnt/sdcard0" and "adb pull /storage/sdcard0"
And in all cases, it reported that the remote object "does not exist". Am I referring to the SDcard correctly??? Or is this an issue with the fact that it seems to be in recovery??
Thanks!!!

syntropic said:
I actually got it to connect (or I no longer so the QHUSB error). However, when I type adb devices, this is displayed.
C:\HTCOne>adb devices
List of devices attached
HT244W403652 recovery
So.. Is this phone in recovery right now??? (remember my screen is non-functional). And I was running Jellybean 4.2.2 on that phone....I tried "adb pull /mnt/sdcard" "adb pull /storage/sdcard" "adb pull /mnt/sdcard0" and "adb pull /storage/sdcard0"
And in all cases, it reported that the remote object "does not exist". Am I referring to the SDcard correctly??? Or is this an issue with the fact that it seems to be in recovery??
Thanks!!!
Click to expand...
Click to collapse
You can try referring to the internal storage using the mmcblk number (mmcblk0p12 is HBOOT for example)
Sent from my One S using Tapatalk 2

usaff22 said:
You can try referring to the internal storage using the mmcblk number (mmcblk0p12 is HBOOT for example)
Sent from my One S using Tapatalk 2
Click to expand...
Click to collapse
What is the block number for the SD card? I apologize for my ignorance....

syntropic said:
What is the block number for the SD card? I apologize for my ignorance....
Click to expand...
Click to collapse
/dev/block/mmcblk0p36

You're aces...
Sent from my HTC VLE_U using xda premium

Also see here: http://forum.xda-developers.com/showthread.php?t=2091801

touch of jobo said:
Also see here: http://forum.xda-developers.com/showthread.php?t=2091801
Click to expand...
Click to collapse
That's awesome! I had no idea someone had figured that many of them out...
I think i will thumbtack that to my wall.

OK... well here is what happened so far...
I tried using the block number but that wasn't recognized either... apparently the phone was off or actually in recovery (as it says "recovery" after I run "adb devices".
Then I decided to hit the power button. To my surprise, the screen flashed on. It made it all the way through to the home screen and then snapped off.... but I hear text message notifications so I know it is on. When I do "adb devices" now, I get "XXXXXXX offline" (see below for a cut/paste of my shell (I am in dos unfortunately).
C:\Windows\system32>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT244W403652 recovery
C:\Windows\system32>cd\
C:\>adb pull /dev/block/mmcblk0p36 c:\sdcardbak\
remote object '/dev/block/mmcblk0p36' not a file or directory
<<<At this point I powered up the phone... the screen went dead, but the phone is still running. Windows informed me that Linux Gadjet drivers were installed... However, I have no access to a pass-through storage device, and as you can see below, adb states that it is offline.>>>
C:\>adb devices
List of devices attached
HT244W403652 offline
I ran "adb pull /dev/block/mmcblk0p36/ ..." again and I recieved an error: device offline. I don't even know what offline means in this context. I always have USB debugging on this phone and I would be surprised if it wasn't still turned on. So what does offline mean??? Any ideas??
I have to copy this SD card in the next 24 hours and send this non-functioning 1S back to TMO, or they are going to screw me out of $850.....any help is sincerely appreciated!!!!!
EDIT: From a glance around the web and XDA... this seems like a driver issue... however, I just finished rooting my new 1S and everything worked fine. I tried switching USB jacks. As far as rebooting.... I can try, but I doubt the screen will turn on during the boot animation.... from experience it takes about 3 days for the screen to work... then it dies upon hitting the desktop (just like the scenario above). The only thing I can think of doing is installing HTC Sync... it is a longshot, but I cannot think of another solution.

Well HTC Sync didn't make a difference. I still get Error: device Offline when I try to do any action.
Is there any adb expert here who knows something??? I am trying to go through the adb commands (the few listed in windows), and hoping that something can be done.
As mentioned earlier.... I have some very important files on this SD card, and because I have been sent a replacement, I need to return this phone to TMO by thursday morning, or they will debit my card $850. Beyond important files, I also just have several GB of pictures and things that I really hate to lose.
So if there are any talents here who could think out of a box I would really really appreciate it.

syntropic said:
Well HTC Sync didn't make a difference. I still get Error: device Offline when I try to do any action.
Is there any adb expert here who knows something??? I am trying to go through the adb commands (the few listed in windows), and hoping that something can be done.
As mentioned earlier.... I have some very important files on this SD card, and because I have been sent a replacement, I need to return this phone to TMO by thursday morning, or they will debit my card $850. Beyond important files, I also just have several GB of pictures and things that I really hate to lose.
So if there are any talents here who could think out of a box I would really really appreciate it.
Click to expand...
Click to collapse
Are you running a CM10.1 or Android 4.2.2 ROM?
Device offline is usually when you haven't allowed adb to perform operations on your phone.
If yes, once you do adb devices and if USB debugging is enabled, you need to press "always allow from this computer" and "OK" (obviously you have to simulate where the buttons are since your touchscreen doesn't work)
Here's a screenshot from a different device to help you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my One S using Tapatalk 2

usaff22 said:
Are you running a CM10.1 or Android 4.2.2 ROM?
Device offline is usually when you haven't allowed adb to perform operations on your phone.
If yes, once you do adb devices and if USB debugging is enabled, you need to press "always allow from this computer" and "OK" (obviously you have to simulate where the buttons are since your touchscreen doesn't work)
Here's a screenshot from a different device to help you.
Sent from my One S using Tapatalk 2
Click to expand...
Click to collapse
Thank you... that's very helpful... I was running a baked bean version I built and that was based on cm10.1/ 4.2.2.
But the only puzzling thing is: (i) I have never seen that message before and yet (ii) was—before the phone was damaged—in ADB all of the time...
So I will trying poking around the screen. I only hope that when the screen goes out it doesn't also render touchscreen non-functional. Since we cannot "wake-up" our phones if they are in sleep mode, right?? We always need to use a hardware button like Power or the volume rocker. But I will give it a shot...
THANKS!

Well, know the screen is on all the time, but there is nothing to see... it is all distorted video... like chomatic noise basically. And I tried several times to run "adb devices" and when I would get
error: device offline
I would try to press the part of the screen I surmised would be correct.
Eventually I launched some app I have on my desktop...so the touchscreen is working.
But I don't think that message is the problem (or rather, I don't think it is coming up).
I know this is not an easy nut to crack, but if you have any other ideas, please let me know. I am going to scour the web for any other posts about offline devices. I just cannot imagine that, since ADB was built for a developer to use from a special shell on the computer that there isn't some way to hack through this....

syntropic said:
Well, know the screen is on all the time, but there is nothing to see... it is all distorted video... like chomatic noise basically. And I tried several times to run "adb devices" and when I would get
error: device offline
I would try to press the part of the screen I surmised would be correct.
Eventually I launched some app I have on my desktop...so the touchscreen is working.
But I don't think that message is the problem (or rather, I don't think it is coming up).
I know this is not an easy nut to crack, but if you have any other ideas, please let me know. I am going to scour the web for any other posts about offline devices. I just cannot imagine that, since ADB was built for a developer to use from a special shell on the computer that there isn't some way to hack through this....
Click to expand...
Click to collapse
So the screen half-works now? Does it show part of the screen?
I would keep trying to get the device online using the accept RSA fingerprint method. You can connect the phone via USB to a different computer with adb. Type adb devices on the cmd/terminal and then the "Accept RSA fingerprint" dialog should come up.

syntropic said:
Am I referring to the SDcard correctly??? Or is this an issue with the fact that it seems to be in recovery??
Click to expand...
Click to collapse
When you boot into recovery, your sdcard is not yet mounted.
Boot your device into recovery.
Get into an adb shell and type 'mount /sdcard'.
In you adb shell, type 'df' (or 'mount') before and after you mount the sdcard partition to make sure it got mounted. Type 'ls /sdcard/' to check whether you can see your files on your sdcard. If your sdcard partition is now properly mounted in recovery, then from your PC you can adb pull /sdcard/
-Jobo

[Q] Rooting NEC Terrain

Hello! I've read the one thread I can find on this, but doesn't seem to be a lot of activity there lately.
I wonder whether anyone's still working on this and whether there's been any progress!
Anyone know?
Thanks much
WP

Wombat Pete said:
Hello! I've read the one thread I can find on this, but doesn't seem to be a lot of activity there lately.
I wonder whether anyone's still working on this and whether there's been any progress!
Anyone know?
Thanks much
WP
Click to expand...
Click to collapse
Root it with Framaroot App...
Press thanks if it worked

Worth trying, but - alas
N'ayam Amarsh'e said:
Root it with Framaroot App...
Press thanks if it worked
Click to expand...
Click to collapse
Thanks for the idea; unfortunately, neither exploit worked. Any other ideas?

Wombat Pete said:
Thanks for the idea; unfortunately, neither exploit worked. Any other ideas?
Click to expand...
Click to collapse
I have a universal Guide To root phones I am now goin' to post it... You can read it and root your phone
---------- Post added at 01:22 PM ---------- Previous post was at 12:34 PM ----------
Wombat Pete said:
Thanks for the idea; unfortunately, neither exploit worked. Any other ideas?
Click to expand...
Click to collapse
Read My Universal GUIDE To root Any Android Device : http://forum.xda-developers.com/showthread.php?t=2684210
Don't Forget To press Thanks Whenever I help You...

Problem with Explorer
N'ayam Amarsh'e, I'm trying your system. So far, so good - up until the Droid Explorer step.
But Droid Explorer installs, with the SDK tools, ... and then crashes upon running it (can't find the SDK stuff).
I looked at the Droid Explorer site under issues - EVERYONE is now having this problem.
I tried various locations for SDK, ...uninstalling and reinstalling DE, and and even earlier releases of Droid Explorer (from before the problem seemed to have cropped up) - nothing works.
Is there any alternative that will work? Or do you happen to know how to fix this problem (no one on their forums seems to know!)?
Thanks again
PS - I got release 8.7.2.x64 to install AND start, but now it doesn't find the android device. Made sure USB debugging is still connected, and that it's "connected as a media device".
PPS - Droid Explorer's site says everywhere that it's supposed to work for already-rooted devices...
N'ayam Amarsh'e said:
I have a universal Guide To root phones I am now goin' to post it... You can read it and root your phone
---------- Post added at 01:22 PM ---------- Previous post was at 12:34 PM ----------
Read My Universal GUIDE To root Any Android Device : http://forum.xda-developers.com/showthread.php?t=2684210
Don't Forget To press Thanks Whenever I help You...
Click to expand...
Click to collapse

Wombat Pete said:
N'ayam Amarsh'e, I'm trying your system. So far, so good - up until the Droid Explorer step.
But Droid Explorer installs, with the SDK tools, ... and then crashes upon running it (can't find the SDK stuff).
I looked at the Droid Explorer site under issues - EVERYONE is now having this problem.
I tried various locations for SDK, ...uninstalling and reinstalling DE, and and even earlier releases of Droid Explorer (from before the problem seemed to have cropped up) - nothing works.
Is there any alternative that will work? Or do you happen to know how to fix this problem (no one on their forums seems to know!)?
Thanks again
PS - I got release 8.7.2.x64 to install AND start, but now it doesn't find the android device. Made sure USB debugging is still connected, and that it's "connected as a media device".
PPS - Droid Explorer's site says everywhere that it's supposed to work for already-rooted devices...
Click to expand...
Click to collapse
Hi this shouldn't be a problem but I think linux would be the best.... in linux you can use nautilus for exploring files of your device with root privileges... try it... i m going to edit the guide now...

Linux
N'ayam Amarsh'e said:
Hi this shouldn't be a problem but I think linux would be the best.... in linux you can use nautilus for exploring files of your device with root privileges... try it... i m going to edit the guide now...
Click to expand...
Click to collapse
So I have to find someone with a linux box? I don't have one at the moment... hmmm...

Wombat Pete said:
So I have to find someone with a linux box? I don't have one at the moment... hmmm...
Click to expand...
Click to collapse
See my guide again it's updated... it also have links

Nautilus does not detect NEC Terrain in Recovery mode
N'ayam Amarsh'e said:
See my guide again it's updated... it also have links
Click to expand...
Click to collapse
Tried Ubuntu 11.04 as well as a couple of other versions. None of them detect anything with the NEC Terrain in recovery mode.
Other hints are welcome, I too would like to have this phone rooted.

timekiller_9 said:
Tried Ubuntu 11.04 as well as a couple of other versions. None of them detect anything with the NEC Terrain in recovery mode.
Other hints are welcome, I too would like to have this phone rooted.
Click to expand...
Click to collapse
You surely don't have drivers.... Download them again and give it a try...

N'ayam Amarsh'e said:
You surely don't have drivers.... Download them again and give it a try...
Click to expand...
Click to collapse
What drivers are you talking about? There are no "drivers" for Ubuntu per say. The only thing that needs to be done is in /etc/udev/rules.d you have to have the appropriate vendor in there, which I do. With the NEC Terrain booted normally:
$ ./adb devices
List of devices attached
30c17c2 device
then I do
$ ./adb reboot recovery
and wait for the NEC Terrain to get in to recovery mode
$ ./adb devices
List of devices attached
And that's it, no devices listed. The NEC Terrain does not respond in recovery mode. Please don't say I don't have drivers, drivers are for Windows. You said this should be done in Ubuntu via Nautilus. I'm not seeing how that could be the case. Please enlighten.

Waiting and Watching
Just Gonna throw out that i have two of these phones. If anyone can tell me what to do to help things along I will. I have tried several different universal root methods to no avail. Watching intently. Interested enough that i made an xda account after lurking for the last few years.

Any luck rooting the NEC Terrain?

No Luck
Haven't had any luck rooting it yet. But I'm quite impressed with the durability of these phones. Ive had mine covered in paint, washed it with gas, and sent it to the bottom of the swimming pool. It just keeps going strong.

Official NEC Terrain site has changed..
Before I bought my NEC Terrain the page necterrain(dot)com was an info site about the phone.
It has since changed to a strange log-in page. I know this is off toppic, but maybe there is some magical nugget of root-getting unlocking code in there.
..not that I'm advocating breaking into such a page.. I'm just postulating. :laugh:

found this today...
I'm not too savvy with this tech stuff but i figured if anyone could do it it would be you guy's here... i did not create this nor write it and since i am new i cannot post a link but its from our friends over at yumapk... so w/o further a due:
"Here is the tutorial of getting root access on NEC Terrain.
Before getting access on NEC Terrain, you need to prepare 4 tools:
Ⅰ：Android SDK
Ⅱ: The related drive of NEC Terrain
Ⅲ: cm-hero-recovery.img
Ⅳ: superuser.zi
The first step is to install USB drive:
Firstly, let’s come into this step. Find Setting-Application program-USB debugger button, then check the first option. Next, connect your USB line with PC, it will prompt you to install driver. If it is the 32 bit system, then you are supposed to choose “x86” document to install the drive. Whereas, if it is 64 bit system, choose “amd64” document to install the drive.
The second step is to prepare the software for NEC Terrain:
In detail, remove the “TMG” document in your software kit to the root directory in C disk, in order to give us the convenience of finding C:\TMG\
The third step is to examine adb.exe and fastboot.exe:
To begin with the third procedure, all we need to do is to ensure that we have the document of adb.exe and fastboot.exe in TMG. So we need to accomplish those procedures one by one.
The fourth step is to check the condition of drive installation:
Unplug your USB line, then shut down NEC Terrain, next press the backspace key. Go on pressing the power key to enter bootloader. Then connect NEC Terrain with PC, and fastbootusb will come out in NEC Terrain. Pay more attention that never press mount at this time.
Open Start-Run-CMD, then enter the order: cdC:\TMG
C:\TMG>_ will come out when the order runs successfully.
Then input the order: fastboot devices.
The fifth step is to start rooting:
Enter: fastboot boot cm-hero-recovery.img after C:\TMG>. Then NEC Terrain will enter the mode of recovery.
We will see seven options in this mode, they are the following ones:
[Home+Back]reboot system now\\restart
　[Alt+S]apply sdcard:update.zip\\install update.zip in SD
　[Alt+A]apply any zip fromsd\\install any zip file in SD
　[Alt+W]wipe data /factoryreset\\delete all datas
　[Alt+B]nandroid v2.2 backup\\back up
　[Alt+R]restore late stbackup\\recover the final back-ups
[Alt+F]repair ext filesystems\\suggest backing up ROM in NEC Terrain, use the trackball to move the cursor to [Alt+B]nandroidv2.2backup, check it. If there is something wrong with your NEC Terrain, it can also recover.
　　
　
　　
　　Now start entering the order, an order is in a line. Pay attention to the small letters and the big letters and also the blank.
　　adb shell mount /system
　　adb push su /system/bin/
　　adb shell chmod 4755 /system/bin/su
　　adb push Superuser.apk /system/app/
　　adb shell reboot
　　After rebooting, you will finally get root access on NEC Terrain."
if this works hopefully someone can make a script to make this more convenient for the others like me

[permanently]temp rooting tools
it suport xposed framework , wifi tethering shoud work(byebye ATT.
this tool came from twitter/uniQta.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://twitter.com/uniQta/status/515004550520918017/photo/1
https://twitter.com/uniQta/status/514104619396378624/photo/1
----
03/26 file was removed.

Hi.. I'm a completly new android guy and started with NEC terrain this week.. And after one weekend with it I managed to skrew it up allready.. I have an unlocked phone, but played with some 2G/3G/LTE apps, so I could switch between those signals, since I could do that on my old BB pearl, and on the pearl it worked like a charm.. Well I press the wrong button, and now my radio is turned onto USA BAND, and can't be changed unless I flash the stock firmware.. I have no idea how to do that so I need help.. But at the same time I've looked up all this ROOT, cuz' this awesome phone does not have my good old features from nokia feature phones nor the blackberry.. the abillity turn power off AND ON on schedule.
And thru my frustrations I fell over a guy who put android 4.4 on his device, since I'm new I read somewhere I can't post links.. But if you google: "How to update NEC Terrain to Android 4.4-Kitkat" then you find the post right away.. does this help you guys? and in the end me?
Greatings from Daniel from Denmark

Lets continue discussion in one thread!
http://forum.xda-developers.com/showpost.php?p=59514154&postcount=77
I created a GitHub repo to collect information, also on how to disable apps (since thats as good as it gets for now).

[Guide] Root on Linux Mint

Rooting a Xiaomi Mi 4i on Linux Mint 17.1 Rebecca
- This guide might also be relevant for users of Debian and Ubuntu
Disclaimer: I accept no responsibility for any damage you do to your phone, body, life or anything else in the past present or future.
This has been written as I had so much difficulty in getting my Mi 4i rooted. I kept trying to do it in Windows through Virtual Box but kept failing.
1. Enable Developer Options
- On your phone, go to Settings
- About phone
- Keep tapping on the Android version until the message at the bottom says that you are a developer
2. Enable USB debugging
- On your phone, go to Settings
- Additional settings
- Developer options
- USB debugging
3. Install the tools
Code:
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
4. Try and see the devices
- Connect the phone to your computer
- Run the following command at the terminal
Code:
adb devices
- It will now say List of devices attached.
- If you see another line with an 8 character identifier such as bf1b6529 then you can skip step 5
5. Add phone to known devices
- Run the following command on the terminal
Code:
echo 0x2717 >> ~/.android/adb_usb.ini
6. Add your computer to trusted devices on your phone
- Enter the following command on the terminal:
Code:
adb devices
- Look on your phone, it should now be asking you if it can add the machine to the trusted devices, or something like that. I'm writing this from memory.
7. Check that adb devices is working
- Enter the following command on the terminal:
Code:
adb devices
- Check that the device ID is there (8 characters such as bf1b6529)
- Check that it says device after it
8. Kill adb
- Enter the following command on the terminal
Code:
adb kill-server
9. Now for the fun. You will need sudo access for this stage.
- Download boot.img to your computer.
- At the terminal, navigate to the directory where you downloaded boot.img, this will probably be ~/Downloads
- At the terminal:
Code:
adb reboot bootloader
- You will now see a screen like the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- At the terminal:
Code:
sudo su
fastboot devices
- You will now see your device ID followed by fastboot
Code:
fastboot boot boot.img
- You will now see something like the following:
Code:
downloading 'boot.img'...
OKAY [ 1.022s]
booting...
OKAY [ 0.259s]
finished. total time: 1.281s
10. Restart
- At the terminal enter:
Code:
fastboot reboot
- You should now see a textual boot screen wher you can see it actually carrying out the rooting with boot.img
- Then it should boot as normal into Android
- Check your apps. You should now have SuperSU

Thanks for step no 5. After trying all kind of 51-android.rules guide from stackoverflow and your solution work. Now I can detect my device in Linux Mint.
5. Add phone to known devices
- Run the following command on the terminal
Code:
echo 0x2717 >> ~/.android/adb_usb.ini
Click to expand...
Click to collapse

thanks....
finally i can connect my mi4i to my linux desktop

Thank you for your guide. I assume this will work on Ubuntu 14.04 as well.
Question to step no.9: "Download boot.img to your current dir" => Which directory do you mean? The root of the phone or on my laptop? Sorry for being newbie. Many thanks.

rmsinaga said:
Which directory do you mean? The root of the phone or on my laptop?
Click to expand...
Click to collapse
You need to download boot.img to your laptop. I've updated Step 9 with the following:
- Download boot.img to your computer.
- At the command line, navigate to the directory where you downloaded boot.img, this will probably be ~/Downloads
Click to expand...
Click to collapse

Step one on the path to rooting my m4i was getting adb to work.
kblade29m said:
Thanks for step no 5. After trying all kind of 51-android.rules guide from stackoverflow and your solution work. Now I can detect my device in Linux Mint.
Click to expand...
Click to collapse
After much googling, much time, and trial and error, I had reached this point. Then I come here and here it is! All made simple.
The next hurdle is that adb devices shows the phone with the word "offline," and that is where...
aembleton said:
- Look on your phone, it should now be asking you if it can add the machine to the trusted devices, or something like that. I'm writing this from memory.
Click to expand...
Click to collapse
...I find I wasn't even seeing the message because the flip cover was closed. Doh.
This is my second Android phone, and I rooted and installed CM on the previous one, a Defy+. Still feel very much a novice, and approaching the rooting is quite scary. Among my worries...
Does this method change the recovery?
Does this method, with boot.img, install a new rom, or does it root the exisiting one?
Will everything else be reset/wiped? (well, backups anyway. Of course).
Will Xiaomi updates still work and be installable?
I am considering using method 1 from "Root/Unroot V6.5.x W/out Losing Stock Recovery [Simplified]" (new member: cannot make that a link) . Any comments?
It is so nice to see the Linux, and especially mint-specific, advice here. Thank you!
(My first post here: usual forum-novice disclaimers apply )

I have used this method to root my mi4i.
Quick answer:
1. No
2. It only roots the existing ROM
3. No
4. You need to full unroot 1st from SuperSU before updating, otherwise it will be bootloop
5. Never tried before

rmsinaga said:
I have used this method to root my mi4i.
Quick answer:
... ... ...
Click to expand...
Click to collapse
Great answer! :good:
Thank you very much for attention to every detail. The only thing putting me off going for this straight away is that I am travelling in just over a week, which doesn't give me any margin for making mistakes (if they can be made, I will make them!).
You mentioned having failed to make stuff work in a virtual machine. Did you try Wine? I failed to make the Mi PC manager software run in Wine.

Simple, painless and absolutely effective
aembleton said:
10. Restart[/B]
- At the terminal enter:
Code:
fastboot reboot
Click to expand...
Click to collapse
(response typed from memory)
Code:
# fastboot reboot
<Waiting for Device>
...amd it goes on waiting. Does anybody get any other response on the terminal screen after this?
Anyway, Be Patient! Probably better to make tea or something away from the screen. After several minutes of Fastboot screen on the phone, the process continues as premised...
aembleton said:
- You should now see a textual boot screen wher you can see it actually carrying out the rooting with boot.img
- Then it should boot as normal into Android
- Check your apps. You should now have SuperSU
Click to expand...
Click to collapse
...and all is well.
After the phone had rebooted, I just ctrl-c-ed the fastboot process and exited from the terminal.

Works wonders, thanks!
Could only find ****ty .exe rooting tools that seemed sketchy and don't have windows installed anymore, so this saved me hours.
My computer could find the phone through adb and got authorized, the phone couldn't find my computer through adb though which was strange but it still worked fine. Thanks alot!

Thad E Ginathom said:
4. Will Xiaomi updates still work and be installable?)
Click to expand...
Click to collapse
rmsinaga said:
4. You need to full unroot 1st from SuperSU before updating, otherwise it will be bootloop
Click to expand...
Click to collapse
Just tried this, it does not work.
Disabled root from SuperSU and updated to the newest weekly developer rom, and my device is now in a boot loop.
I'm currently trying to download the stable fastboot rom from the MIUI forums, but their servers are both incredibly slow and unstable. Doesn't go past 100kb/s and the download loses connection after a while and fails to continue the download. If someone could provide a alternative download link that would be great.
EDIT: Found a hidden link on the rom page for the fastboot rom from the miui page. Go to this page and Ctrl-F Mi4i

zenolijo said:
Found a hidden link on the rom page for the fastboot rom from the miui page. Go to this page and Ctrl-F Mi4i
Click to expand...
Click to collapse
Did this work for you?
I also got into a boot loop after installing the latest update. I installed the latest stable version. This worked, but the Play Store won't start.

aembleton said:
Did this work for you?
I also got into a boot loop after installing the latest update. I installed the latest stable version. This worked, but the Play Store won't start.
Click to expand...
Click to collapse
Well, the stable fastboot rom isn't the global version, so i only used it to get my phone running again and then flashed the stable global version. Everything works as expected now.

How to update ROM using fastboot in Linux?
Do you know how to update ROM using fastboot in Linux?
Sorry to bother you as I'm new in this Linux world.
Thank you.

Thank you man, you have guided us to the land of light, you are our moses, krishna, muhammad and so on and so forth. We can flash left and right without second thoughts. Please keep up your efforts. Thank you one more time.

My phone is, as per previous posts, rooted, using this method.
Can I now flash TWRP recovery from Linux?

Hey, this is a method only for Xiaomi Mi4i? I have an Estar Crystal-clearview and wondering if I can root it by this method? I run the terminal with the adb install and then for the list of devices attached, and I started thinking about!
P.s. Just searched ''root with mint'' and your post was first!

Thad E Ginathom said:
Can I now flash TWRP recovery from Linux?
Click to expand...
Click to collapse
Eventually I got around to doing this using Flashify. I followed the instructions here on the MIUI forum. It was simple and straightforward and I now have TWRP recovery.
However, when I tried to use it to do a backup, it said there was not enough space. But it was long past bedtime, and that is another story that I have yet to investigate. There is probably a simple answer, err... make more space! The absence of SD card slot and the limited internal memory is the big frustration about this phone.
But I want to upgrade MIUI --- and I don't want to do it without an easy backtrack to the previous ROM.

[Solved] Step 9 not working
Goto developer options
Check if 'fastboot mode' is enabled

Thanks
Hi aembleton,
Thanks a lot. it worked just fine.
does this replace recovery too ?

[TOOL] MobyDroid (Android Device Manager for Linux, Windows and MacOS)

Hello every one,
MobyDroid is a simple and cross-platform Android Devices Manager.
It runs on any operating system with Java support (Mac OS X, Windows, Linux, BSD, Solaris...).
THIS IS JUST A BETA RELEASE !
I have been running linux from while now. And what I noticed is there is no GUI Android Devices Manager until now (QtADB didn't work for me).
Basicly I kept using ADB command line and kept waiting for someone to make something or some alternatives.
Some day a friend of mine kept complaining about the same problem. After that, I decided to make a simple Apk installer with a graphical user interface. And something lead to another.
And I wanted to share it for any one having the same problem.
So here it is !
Prerequisites
Java Runtime Environment (JRE) 1.8 or later
ADB
BETA
THIS IS JUST A BETA RELEASE !
So you should expect a ton of bugs or crash issues.
if you encounter an issue or have a great ideas please file an issue.
Download
You can download from here.
Authors
Bilux ([email protected])
Link
MobyDroid
https://github.com/ibilux/MobyDroid
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ibilux said:
Hello every one,
MobyDroid is a simple and cross-platform Android Devices Manager.
It runs on any operating system with Java support (Mac OS X, Windows, Linux, BSD, Solaris...).
THIS IS JUST A BETA RELEASE !
I have been running linux from while now. And what I noticed is there is no GUI Android Devices Manager until now (QtADB didn't work for me).
Basicly I kept using ADB command line and kept waiting for someone to make something or some alternatives.
Click to expand...
Click to collapse
this is kinda long term general issue, most of manufacturers had their own app, samsung, htc, lg, and there is no general solution android manager, so this could be a start of a big project. good luck
Sent from my ONE A2005 using Tapatalk

chxei said:
this is kinda long term general issue, most of manufacturers had their own app, samsung, htc, lg, and there is no general solution android manager, so this could be a start of a big project. good luck
Sent from my ONE A2005 using Tapatalk
Click to expand...
Click to collapse
Thank you very much.
As a start, I'm just trying to give back to the XDA and open source community.

Nice work keep up ???

@ibilux
Hi, is this project discontinued?
Any plans for future development?
Thanks!

EuK_V said:
@ibilux
Hi, is this project discontinued?
Any plans for future development?
Thanks!
Click to expand...
Click to collapse
I just didn't have anything to add.
But, if you have an issue or feature, I'll look into it.

ibilux said:
I just didn't have anything to add.
But, if you have an issue or feature, I'll look into it.
Click to expand...
Click to collapse
Thank you, for your reply!
First of all I'd like to say that I am interested more in the "File manager" function of the app. And if you don't mind I have some suggestions:
I am faced with the following: when I start the app I don't have full root access, though "su root permissions" is checked in settings. I can browse the root directory, but cannot create or delete any file or folder. There is a workaround: if I start adb as root from my Ubuntu terminal executing:
adb root
after that I have full root access to my phone. It works this way, but I think since Mobydroid is a gui to adb, it should be able to start adb as root.
Also it would be great if the app could start adb via wifi (I don't know maybe add an option to choose how to connect via usb or network. Now if I start adb via network in terminal executing:
adb connect 192.168.0.101:5555
Mobydroid then works well. Again I need to make some actions outside the app before I start it. (BTW IP address of a device is just an example)
Another thing I'd like to say is that Mobydroid when viewing a device shows symlinks to folders as files and you cannot enter them. On the side of Ubuntu it works well, symlinks to folders work as folders and you can enter them. See my screenshot.
And it would be great to have sort options like "folders first" to sort folders before files and to sort dot folders (.folder) after regular folders and dot files after regular files. Like it works in most linux FMs.
Hope this wouldn't be too overwhelming...
Thanks!

EuK_V said:
Thank you, for your reply!
First of all I'd like to say that I am interested more in the "File manager" function of the app. And if you don't mind I have some suggestions:
I am faced with the following: when I start the app I don't have full root access, though "su root permissions" is checked in settings. I can browse the root directory, but cannot create or delete any file or folder. There is a workaround: if I start adb as root from my Ubuntu terminal executing:
adb root
after that I have full root access to my phone. It works this way, but I think since Mobydroid is a gui to adb, it should be able to start adb as root.
Also it would be great if the app could start adb via wifi (I don't know maybe add an option to choose how to connect via usb or network. Now if I start adb via network in terminal executing:
adb connect 192.168.0.101:5555
Mobydroid then works well. Again I need to make some actions outside the app before I start it. (BTW IP address of a device is just an example)
Another thing I'd like to say is that Mobydroid when viewing a device shows symlinks to folders as files and you cannot enter them. On the side of Ubuntu it works well, symlinks to folders work as folders and you can enter them. See my screenshot.
And it would be great to have sort options like "folders first" to sort folders before files and to sort dot folders (.folder) after regular folders and dot files after regular files. Like it works in most linux FMs.
Hope this wouldn't be too overwhelming...
Thanks!
Click to expand...
Click to collapse
Root and wireless connection features has been implemented in version v0.4.
I'll implement symbolic links and folders order in next release.

Thanks. Works good, but it can't sort dirs/files by name or date.

sorry but it doesn't work

@rifkican, enable adb in developer settings.

Is this still working? I tried to run it but i get this error:
[CheckBinaries] : I: couldn't create file: Read-only file system.

pabekam said:
Is this still working? I tried to run it but i get this error:
[CheckBinaries] : I: couldn't create file: Read-only file system.
Click to expand...
Click to collapse
What platform are u using ? and how did u install MobyDroid ?

ibilux said:
What platform are u using ? and how did u install MobyDroid ?
Click to expand...
Click to collapse
Windows. I downloaded the Standalone version, installed java and run the command over cmd. MobyDroid starts but in the cmd i get the error message. In MobyDroid when i go to the file manager, it doesnt show me any files/folders on my phone

pabekam said:
Windows. I downloaded the Standalone version, installed java and run the command over cmd. MobyDroid starts but in the cmd i get the error message. In MobyDroid when i go to the file manager, it doesnt show me any files/folders on my phone
Click to expand...
Click to collapse
can u provide full log errors.

ibilux said:
can u provide full log errors.
Click to expand...
Click to collapse
how do i do that?

ADB no longer works with devices I have used for years

I originally posted in the "Ask ANY Question. Noob Friendly" thread but got no replies so am trying again in its own thread. I just find it hard to believe no one has seen a similar problem anywhere....
ILikeOldStuff said:
I've been using ADB for some years on several devices but recently ran into a snag. On the same machine (an older desktop running XP) where it has always worked before, I recently tried to use it but got an odd error message:
E:\platform-tools> adb version​Android Debug Bridge version 1.0.32​Revision 57224c5cff69-android​​E:\platform-tools> adb devices -l​List of devices attached​* daemon not running. starting it now on port 5037 *​ADB server didn't ACK​*failed to start daemon *​error: cannot connect to daemon: No error​error: cannot connect to daemon: No error​​I tried to google it but everything I found either assumed there was a problem with eclipse, with wifi, with not using correct cables, not installing drivers, etc. But NOTHING about a case where it used to work but for some reason no longer does.
I do not (and never did have) have eclipse, nor even the android SDK installed, just the much smaller platform-tools thing. The desktop box does not have any wifi radio hardware so I can rule those out. It also is not a usb port or cable issue as I can still transfer files through MTP.
It is not really a device issue as it suddenly started happening on ALL android devices including ones I used it on before. And it isn't a case where the device updated to change anything as these are older devices running FroYo, IceCreamSandwich, Jellybean, and Oreo, where updates stopped many years ago.
I don't think it is a device driver issue as all devices I tried do show up properly in device manager.
The last time it worked was 25Sep2022 when I adjusted some permissions on the BetterBatteryStats app. I did not need it again until recently when it started doing the above error message.
Has anyone seen anything similar or have an idea how to fix it?
Click to expand...
Click to collapse
I will add that I have tried disabling AV and adding extra permissions to the firewall (which were never needed before as the process was always local) to no avail. I have never had genymotion installed (another common culprit according to various google hits). There does not seem to be anything useful in system event logs either. And Task Manager does show the adb process is indeed running.
One question I have , is how to get more clues for solving this problem. I thought firewall logs might show if that was blocking anything, so set it to log all connection activity attempts but it is not showing up in firewall logs, which makes me think the problem is elsewhere.
I see that some apps can write things to system event logs, but ADB seemingly has not done this. Is there some setting to make it write event log entries, or any other way it can be made to write some debug logging details somewhere?
Any other thoughts of how to solve this?

To start, I suggest using the latest version of platform-tools-latest-windows.zip.
or use mAid:
[LIVE-ISO][mAid][v4.0] manage all your Android devices without driver hassle
is now: (read here why) About The existence of mAid (abbreviation for [m]anage your [A]ndro[id]) has a simple reason. I wanted to have something where I were able to point users to when they came with issues on Windows because the most...
forum.xda-developers.com

Update ADB: dowmload latest version from here
Releases · K3V1991/ADB-and-FastbootPlusPlus
A small Application for Windows that allows you to install the latest Version of ADB and Fastboot Files on the Computer without installing the entire Android SDK Package + Toolkit & Commands - ...
github.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ze7zez said:
To start, I suggest using the latest version of platform-tools-latest-windows.zip.
or use mAid:
Click to expand...
Click to collapse
Sadly I can't do either of these. Platform tools R23 (that I have been using) is the last one that is compatible with Windows XP. And this desktop box is running on an old P4 processor, which is 32bit only, with no hardware support for virtualization either, so mAid does not look compatible.
xXx yYy said:
Update ADB: dowmload latest version from here
Click to expand...
Click to collapse
Again, that looks like too new of a version of platform_tools to be compatible with XP.
But thank you both for at least trying to help!
What bugs me, is that debugging mode USED to work, until recently when it didn't.

ILikeOldStuff said:
...
Again, that looks like too new of a version of platform_tools to be compatible with XP.
...
Click to expand...
Click to collapse
The ADB driver ( has nothing to do with platform tools package ) since ever is 32-bit, hence it will work with Windows XP, too.

xXx yYy said:
The ADB driver ( has nothing to do with platform tools package ) since ever is 32-bit, hence it will work with Windows XP, too
Click to expand...
Click to collapse
While it may be still 32 bit, it does not work anymore with Windows XP since it uses functions that are only available in Vista & up. It gives an error message:
The procedure entry point WSAPoll could not be located in the dynamic link library WS2_32.dll.​

Time to change OS version or update WS2_32.DLL ( read: WinSock 2 DLL - the system file that contains the Windows Sockets API, an important software that is used to run most network and internet applications ) .

Right, v23 is latest version working for Windows XP (and still works). delete the %userprofile%\.android folder and try again (do backup if necessary)

alecxs said:
delete the %userprofile%\.android folder and try again
Click to expand...
Click to collapse
This took a little longer before it eventually gave a similar error message :
E:\platform-tools> adb devices -l​List of devices attached​* daemon not running. starting it now on port 5037 *​* daemon started sucessfully *​** daemon still not running​*failed to start daemon *​error: cannot connect to daemon: No error​error: cannot connect to daemon: No error​​but Task Manager shows adb.exe is indeed running, and my firewall log reports that adb.exe is listening on port 5037, and is not blocked.

what firewall? is that the cause? disable completely?

Comodo 3.14.130099.587
I don't really think it is the cause, it has been running on the machine since even before the first use of ADB and never caused an issue before, allowing ADB to work in the past. Also ADB has never showed up in the logs as having been blocked.
I might try disabling it later tonight when I get home.

do a search on whole disk for other adb.exe make sure you haven't running multiple instances.

ILikeOldStuff said:
...
​but Task Manager shows adb.exe is indeed running, and my firewall log reports that adb.exe is listening on port 5037, and is not blocked.
Click to expand...
Click to collapse
In a previous post you stated ADB.EXE doesn't work due to missing or invalid shared system library file named WS2_32.DLL file.
Why not fix this issue as 1st thing of all things?
ws2_32.dll free download | DLL‑files.com
Download ws2_32.dll free! Fix DLL missing error. Solve it yourself or get help using DLL‑files.com Client to fix DLL error automatically.
www.dll-files.com

xXx yYy said:
In a previous post you stated ADB.EXE doesn't work due to missing or invalid shared system library file named WS2_32.DLL file.
Why not fix this issue as 1st thing of all things?
Click to expand...
Click to collapse
It is neither missing nor invalid. There is Ws2_32.dll version 5.1.2600.7074 present in \Windows\system32. This is the latest version for XP, from installing MS16-077 KB3161949 ; it just does not have (and was never intended to have) the WSAPoll function that was introduced in Vista.
This error message only happens if I try to run the latest version of ADB, which is no longer compatible with XP. I do not see this when I stay with the r23 version that is the last one compatible with XP.
xXx yYy said:
Time to change OS version or update WS2_32.DLL
Click to expand...
Click to collapse
Installing a newer Windows OS is not really an option for this older hardware; it just does not have the RAM nor CPU horsepower for anything beyond XP. There is also the lack of device drivers for older hardware, and I am not willing to do without such "frills" as a working video card, ethernet adapter, parallel printer port, and other items which I use on a daily basis but are not supported by W10.

alecxs said:
what firewall? is that the cause? disable completely?
Click to expand...
Click to collapse
ILikeOldStuff said:
Comodo 3.14.130099.587
I don't really think it is the cause . . .
I might try disabling it later tonight when I get home.
Click to expand...
Click to collapse
I finally got around to trying this, and it turns out you were right and I thought incorrectly. So thanks for the reminder to re-check the obvious.
alecxs said:
do a search on whole disk for other adb.exe make sure you haven't running multiple instances.
Click to expand...
Click to collapse
The only other copies of adb.exe that I have are inside the .zip files for other newer (no longer XP compatible) versions of platform-tools. I left them inside the .zip files and unzipped only the r23 version to prevent accidentally running the wrong ones.
Task Manager mostly only showed the one instance. The only time I could see multiple was when I disabled the firewall, started one, re-enabled the firewall, then did another "adb devices -l"; repeating this sequence several times would produce one additional instance for each repeat. Using task manager to kill the extras allowed the remaining one to work properly provided the firewall was disabled.
So I can still run the r23 version of ADB after all, although the workaround of disabling first the ethernet and then the firewall is inconvenient to say the least, and hardly ideal.
I am still confused why Comodo FW clearly is blocking this while not logging that action. And also why it is blocked at all when I am using only a USB cable and neither ethernet nor wifi networks. Even moreso why it USED to work with no need to disable the firewall but no longer does.
Looks like getting these other questions sorted will need some visits to the Comodo forums.

adb client communicates with adb server via TCP. here is list of ports you must whitelist in firewall.
https://developer.android.com/tools/adb