Database Info

[Solution]Windows 8 - ADB/fastboot driver problem solved!!

Hello!!​
First off; This is copied, from my thread, in the Galaxy Nexus forum... Sorry, if you find the words "Galaxy" or "Samsung". But, this works for pretty much every phone, (except, for the USB drivers)...
{
"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"
}
So, give it a go...
I haven't found another tutorial, like this at all... So, if you find something like this it's copied from me
Now, on to the actually interesting stuff ^^
I have found a solution, to the following problem;
After installing Windows 8, you cannot install fastboot drivers, but it recognizes the ADB drivers...
Solution:
Note: If you feel more comfortable using the Windows Power Shell, you can use that as well, it is, after all, only the Windows shell
Open the dev-manager, by typing following, in a command prompt window, or the run dialog. Whichever you prefer... :
Code:
[B][COLOR="Cyan"]devmgmt.msc[/COLOR][/B]
Now, the device manager, should pop up.
Install ADB drivers, (If you do not have them present, download them here
To prevent confusion: When I say install, it can mean unpack, or install... Quick tip: An installer does nothing, apart from unpacking files, to allocated space, on your computer
Download USB drivers, from here. (Link fixed. Again (-_-") ) (Note: These are the Sammy OEM drivers.)
Should you NOT have drivers installed:
Install the USB drivers, and download ADB/fastboot drivers.
Installation of ADB/fastboot drivers:
Open the device manager, and look for "Samsung Mobile Device", or "Unidentified Device". You can make your search easier, by unplugging the phone, whilst in device manager, then plug it back in, and see what's changed...
Once you have found your phone, Perform a right-click, on the device. Select : "Update device drivers", once the dialog has popped up, choose "Browse my computer" and goto your desktop, where you have installed the files to.
Open just the "drivers" folder, nothing else...
Select OK, then wait for installation to finish.
Once that has been done, you need to reboot your device, into bootloader mode; do this by typing
Code:
path=%userprofile%\Desktop\ADB\
adb reboot-bootloader
into the command prompt (download & install this, if you want to do it the cmd-way...)
Or, turn off your phone, and reboot i it manually into bootloader-mode, by pressing
Code:
VOL UP +DWM & PWR
together, untill phone vibrates...
Once the phone is in bootloader, go back to the device manager, and look for a device named "android 1.0". Perform a right-click on this and select "Update device drivers". Again, selct "Browse my computer", but, instead of clicking on "Browse" and selecting the folder, again, select "Let me pick from a list of drivers." Once the menu has popped up, select "Samsung Android ADB interface". Click OK, and wait for the drivers to install . Then, you're done. You have then successfully installed the ADB + fastboot drivers correctly, to test this, open a cmd window, and type following:
Code:
path=%userprofile%\Desktop\ADB\
fastboot devices
If your device shows up, then you have done it!!
Now type:
Code:
fastboot reboot
adb wait-for-device
adb kill-server
Note: while the phone is booting (If you typed "adb wait-for-device") A cursor will blink, wait for that, to stop blinking, then type the next command
I hope you learned, from this tutorial!! Check out Beatsleigher & M4gkman's Universal Android Toolkit, if you have enough time
Should you have problems, in recovery, open your dev. manager, and look for following device:
Code:
Full
Select, right-click. Update driver (blah, blah, witter, droan)
Browse my computer -> Let me pick -> Samsung ADB -> Done. You have enabled the ADB drivers, on your Android Device!!!!
So, apparently, if you're using Windows 8 and/or USB 3.0 ports, Windows installs its crappy drivers, so you should check out this link, posted by the awesome @tommy_riley and try it out for yourselves! Don't forget to drop him a 'Thanks'!
http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers <- Courtesy of @tommy_riley!
Wow. Over 40.000 clicks and downloads. I'm amazed at you guys!
It doesn't cost anything or hurt to hit that 'Thanks' button... Please be sure to hit it, it helps me out and also shows me what sort of content you want to see from me.
Do you like the effort I put into this? Then consider donating, by adding towards a new PC: http://www.gofundme.com/NewPC
With a new PC, I can create more one-click solutions and stuff and things!

Updates & other info!! (Reserved)
If you have a problem, I'll do it over TeamViewer, if you wish
Ok, here is some news, for you!
Well, according to some people, who have used this tutorial, Microsoft has done something new to their device driver signing.
I did not have note of this, as I was using Ubuntu most of the time and the laptop I was using broke, several weeks ago (It's gonna take me ages to get a new one, with which I can finally finish my ROM cooking..)
And Senior Member "purpler" has posted a link, which teaches you to turn device driver signing off, in the new bootloader, which Windows 8 is using/will be using, so; let's give him loads of thanks, for this!
here is his answer:
purpler said:
confirmed that it works but i had to diable driver signing from Windows8 bootloader (Shutdown.exe /r /o)
Use and Access Windows 8 Boot Loader and Advanced Boot Options
Click to expand...
Click to collapse
Many thanks to you, purpler!
Please, if you notice anymore changes, which interferes with this method, please let me know, how to solve the problem!
Every helpfull answer, with new solutions will be posted in this thread and thanked many times!
EDIT: If you don't want to donate, but still want to thank me, then use these links, instead of the links, in the tutorial.
Mod edit: No adfly links allowed.
4lex96 said:
I've solve the problem, in stead of usb 3.0 i used a usb 2.0 and it worked! Very strange, with 3.0 i had problem with 2.0 no. I hope this funny thing can help someone.
Best regards
Click to expand...
Click to collapse
Senior member 4alex96 has experienced some problems, while using USB® 3.0 ports.
If you are also experiencing these problems, or you have found a solution to this, be sure to post in this thread or write to me via PM and I'll be sure to quote and write this, so others also get to know and are able to get the most out of there Androids!
Creating a new tool!
Hey guys, I'm going to be creating a new tool or two, which will allow you to install ADB and Fastboot directly to the system root and which will install the Google drivers to your C:\ drive.
These tools will be available for a small donation, and they will save you a lot of work, i.e. you will never have to type in "path=<Whereever the ADB files are>" but you can just debug on
If you want to have the program, hit the "Donate to Me" button on the left of this post and donate a small amount. Then in the donation, write me a message, saying what it's for and give me your XDA username and I'll PM you the download link.
(Minimum of 5€)
tommy_riley said:
For Windows 8, I was having an issue getting my phone to be recognized in bootloader mode on an ASUS laptop that only had USB 3.0 drivers, I followed the procedures at the below URL (luckily I had an INTEL chipset) and once I replaced my native Windows USB 3.0 drivers with the Intel USB 3.0 drivers, I was able to work around a lot of issues:
http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers
(I cant post HTTP links yet, but you should be able to plug the above into a browser to find the instructions...)
hope this helps!
Click to expand...
Click to collapse
You get that, guys? Go check out that website, and try it out for yourselves!

Tried using this fix keep getting an error saying the driver is not signed.
-Edit
Got it working had to go into advanced boot options and turn off device signing

thisiswar951 said:
Tried using this fix keep getting an error saying the driver is not signed.
-Edit
Got it working had to go into advanced boot options and turn off device signing
Click to expand...
Click to collapse
Ok, cool. I haven't been on my laptop, for a few days, so I wouldn't know, if MS has released any updates, yet...
I was thinking: WTF is he talking about? It's worked by so many people :O...
xD
LG familyguy59

confirmed that it works but i had to diable driver signing from Windows8 bootloader (Shutdown.exe /r /o)
Use and Access Windows 8 Boot Loader and Advanced Boot Options

Hi, I'm using win8 pro 64bit rtm.
when I double click on the UsbDrv.exe from Samsumg nothing comes up.
even when I run it in compatibility mode it doesn't help...
any ideas? I have disabled signed drivers.
thanks!

hshen45 said:
Hi, I'm using win8 pro 64bit rtm.
when I double click on the UsbDrv.exe from Samsumg nothing comes up.
even when I run it in compatibility mode it doesn't help...
any ideas? I have disabled signed drivers.
thanks!
Click to expand...
Click to collapse
You'll have to wait a moment, the system has to look for all the needed files, in the exe, and then needs to try to execute. If it then doesn't work, I'll upload an updated version, but as this seems to be working pretty much fine, I'll hesitate, not that the updated verison causes problems.
Anyways, I was running Win8 64x and it worked fine, just let the computer do it's work and it will work sooner or later, if nothing happens, even after waiting for 5-10 minutes, then try running it with administrative rights (Run as administrator).. Let me know if it works!

Doesn't work for me because I cant even see my S3 in the device manager.

leeznon said:
Doesn't work for me because I cant even see my S3 in the device manager.
Click to expand...
Click to collapse
Then try a different computer Doesn't mean that your S III is kaputt, does it?
If it then doesn't work, you've probably got dirt in the socket, or something else, like that.
And if you don't have dirt in the socket, then I don't know, whats wrong, but it'll definitely go over warranty

I have find an easiest way to install adb driver on windows 8 : ( disabling driver signature )
- after BIOS on "choose Operating system" screen
-clic "change default setting"
-clic "choose other option"
-clic "troubleshoot"
-clic "advanced option"
-clic " startup setting"
-clic on "restart"
-Install the driver adb as if you were on Windows 7 :laugh:

dalien26 said:
I have find an easiest way to install adb driver on windows 8 : ( disabling driver signature )
- after BIOS on "choose Operating system" screen
-clic "change default setting"
-clic "choose other option"
-clic "troubleshoot"
-clic "advanced option"
-clic " startup setting"
-clic on "restart"
-Install the driver adb as if you were on Windows 7 :laugh:
Click to expand...
Click to collapse
That's what the link in the first post is for. And you still need to follow the steps in the tutorial, otherwise it won't work properly.
I know the tutorial looks complex, but it isn't. You just need to read properly
LG familyguy59/Beatsleigher
EDIT: It's spelled "click"

help me to connect android in win 8
Please help me i am not expert I will give my teamviewr password. i spent hole to connect my android to win 8 but not succeed. when you come to online just inform me. many thanks those were helping.

netbook said:
Please help me i am not expert I will give my teamviewr password. i spent hole to connect my android to win 8 but not succeed. when you come to online just inform me. many thanks those were helping.
Click to expand...
Click to collapse
OK, I will be back, tomorrow. I'm currently at a friend's, so I will be back tomorrow. Send me an e-mail, when you're back, and I'll help you, right away!
LG familyguy59/Beatsleigher

familyguy59 said:
Hello!!​
First off; This is copied, from my thread, in the Galaxy Nexus forum... Sorry, if you find the words "Galaxy" or "Samsung". But, this works for pretty much every phone, (except, for the USB drivers)...
So, give it a go...
I haven't found another tutorial, like this at all... So, if you find something like this it's copied from me
Now, on to the actually interesting stuff ^^
I have found a solution, to the following problem;
After installing Windows 8, you cannot install fastboot drivers, but it recognizes the ADB drivers...
Solution:
Note: If you feel more comfortable using the Windows Power Shell, you can use that aswell, it is, afterall, only the Windows shell
Open the dev-manager, by typing following, in a command prompt window, or the run dialog. Whichever you prefer... :
Code:
[B][COLOR="Cyan"]devmgmt.msc[/COLOR][/B]
Now, the device manager, should pop up.
Install ADB drivers, (If you do not have them present, download them here
To prevent confusion: When I say install, it can mean unpack, or install... Quick tip: An installer does nothing, apart from unpacking files, to allocated space, on your computer
Download USB drivers, from here. (Link fixed) (Thanks so much for 5k+ downloads!!)
Should you NOT have drivers installed:
Install the USB drivers, and download ADB/fastboot drivers.
Installation of ADB/fastboot drivers:
Open the device manager, and look for "Samsung Mobile Device", or "Unidentified Device". You can make your search easier, by unplugging the phone, whilst in device manager, then plug it back in, and see what's changed...
Once you have found your phone, Perform a right-click, on the device. Select : "Update device drivers", once the dialog has popped up, choose "Browse my computer" and goto your desktop, where you have installed the files to.
Open just the "drivers" folder, nothing else...
Select OK, then wait for installation to finish.
Once that has been done, you need to reboot your device, into bootloader mode; do this by typing
Code:
path=%userprofile%\Desktop\ADB\
adb reboot-bootloader
into the command prompt (download & install this, if you want to do it the cmd-way...)
Or, turn off your phone, and reboot i it manually into bootloader-mode, by pressing
Code:
VOL UP +DWM & PWR
together, untill phone vibrates...
Once the phone is in bootloader, go back to the device manager, and look for a device named "android 1.0". Perform a right-click on this and select "Update device drivers". Again, selct "Browse my computer", but, instead of clicking on "Browse" and selecting the folder, again, select "Let me pick from a list of drivers." Once the menu has popped up, select "Samsung Android ADB interface". Click OK, and wait for the drivers to install . Then, you're done. You have then successfully installed the ADB + fastboot drivers correctly, to test this, open a cmd window, and type following:
Code:
path=%userprofile%\Desktop\ADB\
fastboot devices
If your device shows up, then you have done it!!
Now type:
Code:
fastboot reboot
adb wait-for-device
adb kill-server
Note: while the phone is booting (If you typed "adb wait-for-device") A cursor will blink, wait for that, to stop blinking, then type the next command
I hope you learned, from this tutorial!! Check my root helper out, if you have enough time
Should you have problems, in recovery, open your dev. manager, and look for following device:
Code:
Full
Select, right-click. Update driver (blah, blah, witter, droan)
Browse my computer -> Let me pick -> Samsung ADB -> Done. You have enabled the ADB drivers, on your Android Device!!!!
Thanks a ton for 6k+ views/downloads!! The thanks are also very much appreciated!!
9K+ views!!
15K+ views!!!
Click to expand...
Click to collapse
Thanks!!!!! You have no idea how you helped me! Now I don't haveto dual boot Win7 just for this purpose! Thanks a ton!!

llsiddhantll said:
Thanks!!!!! You have no idea how you helped me! Now I don't haveto dual boot Win7 just for this purpose! Thanks a ton!!
Click to expand...
Click to collapse
I'm always glad to help, dude
LG familyguy59/Beatsleigher

heads up - driver signature enforcement policy on win8 can cause some problems. i just disabled it.

shaolinx said:
heads up - driver signature enforcement policy on win8 can cause some problems. i just disabled it.
Click to expand...
Click to collapse
We're already aware of that (see post #2) but still thanks for briefing everyone again.
LG familyguy59/Beatsleigher
Cyanogenmodded very skankily via XDA app. Skanky, indeed

Hi
i try to do this from yesterday night (maybe from 3 o'clock) and nothing... I've windows 8 64bit and xperia S with ICS. With windows 7 i haven't problem but with windwos 8...
Can you help me trought teamviewer?
Thanks a lot dude!

4lex96 said:
Hi
i try to do this from yesterday night (maybe from 3 o'clock) and nothing... I've windows 8 64bit and xperia S with ICS. With windows 7 i haven't problem but with windwos 8...
Can you help me trought teamviewer?
Thanks a lot dude!
Click to expand...
Click to collapse
Well, not at the moment, but I'll get back to you, as soon as I can!
But, to save time, when I'm on your PC, could you make sure you have the executables (ADB, fastboot and the DLLs) from the first post and your OEM USB drivers? That saves a heck of a lot of time
LG familyguy59/Beatsleigher

familyguy59 said:
Well, not at the moment, but I'll get back to you, as soon as I can!
But, to save time, when I'm on your PC, could you make sure you have the executables (ADB, fastboot and the DLLs) from the first post and your OEM USB drivers? That saves a heck of a lot of time
LG familyguy59/Beatsleigher
Click to expand...
Click to collapse
I've solve the problem, in stead of usb 3.0 i used a usb 2.0 and it worked! Very strange, with 3.0 i had problem with 2.0 no. I hope this funny thing can help someone.
Best regards

[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 ?

[GUIDE] Install Android SDK Standalone [ADB][30 Dec 2015]

Android SDK - Powerful tool and easy to set up for use with your Android Device
{
"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"
}
I am putting this together for some who may be confused on how to set this up. I love Android SDK, have been using it for ever and once it is setup, maintenance is extra easy. There are 100 ways to skin a cat with ADB tools and development tools. This is my personal choice, go about it how ever you want. This tool is well maintained and always updated so its a big reason I use it. Great support and a great and powerful tool
Click to expand...
Click to collapse
Part 1. Follow These Steps Below - (Preparation)
Download Links For Tools
1. Java SE Development Kit (JDK)
2. Android SDK Tools Only - Download Only, Do Not Install yet
If You Choose Windows for example
3. Universal ADB Drivers - Instructions Here
Click to expand...
Click to collapse
How to Install and Set-up
1. Install Java SE Development Kit (JDK) from Start Here section if you have not yet
2. Launch Android SDK installer you downloaded up above in Download Links
3. During install - Set Installation Path to
Code:
C:\Android\
4. After Installation is Complete, run SDK Manager.exe
5. Install 5.1.1 and 6.0 since these are the APIs for all current Devices. Should not really see anything less than 5.1.1
Note* - Just put a check box where you see the red circles in the picture. The reason I have Tools (Preview Channel) is because I updated to the 25.0.1 RC2 SDK Tools, however, that is not required. You can choose 24.4.1 and it will be fine. It will say installed where as mine does not in the picture because I chose to use 25.0.1 RC2
6. Let all updates install to completion - This could take a while depending on your internet connection
Click to expand...
Click to collapse
The Computer and Phone are now prepped for you to start the whole ADB Process
Click to expand...
Click to collapse
Part 2. Verifying ADB is set up properly and Working
IMPORTANT - Make sure you have already enabled developer options and USB Debugging or you will not see the below results
1. Open Command Prompt and Change directories to your platform-tools folder. This is where all the adb files are located. See Below
In Command Prompt Type - Refer to Part 3 so you no longer need to Change Directory
Code:
cd c:\Android\platform-tools
2. In Command prompt type
Code:
adb devices
You Should get Prompted to Allow USB debugging - Ignore if You Already Have Done This
3. If your output shows your device attached like below, then you are good to go!!!
and
YOU ARE FINISHED!!! Below is a command to get into the bootloader if interested!! Good Luck
Click to expand...
Click to collapse
Part 3. Environment Variables - No need to Change Directory in Command Prompt Anymore (This is if you want to - Not Required)
1. Press Win+R, then type
Code:
sysdm.cpl
2. Click Advanced Tab
3. Click Environment Variables Button
4. Under System Variables, find Path, click to highlight it and then hit the edit button
Windows 8
Windows 10
5. Go to the end of the Variable Value and add the following exactly as you see it in the code box below
Code:
;C:\Android\platform-tools
Windows 8
Windows 10
6. Click OK to accept the changes you just added
7. Open Command Prompt again to verify by pressing Win+R and type cmd and hit enter
8. Once Command Prompt is open -> Simply type adb devices with your device connected with USB Debugging already enabled
9. If you did everything correctly, there is no need to change paths anymore
Click to expand...
Click to collapse
Getting into the Bootloader
In Command Prompt Type:
Code:
adb reboot bootloader
Thanks To:
@Ashraf - Images used for Environment Variables - Not all were his since the guide was modified
@[B]Snoop05[/B] - ADB Drivers and Fastboot

Reserve if Needed

Thank you so much for this - can i ask what's the size of the SDK manager files which we are supposed to download? For some reason it downloads in 86 kb/s speed (normaly 5-6 mb/s) so I just wanted to know if i'm going to wait a long time

Peccoskaify said:
Thank you so much for this - can i ask what's the size of the SDK manager files which we are supposed to download? For some reason it downloads in 86 kb/s speed (normaly 5-6 mb/s) so I just wanted to know if i'm going to wait a long time
Click to expand...
Click to collapse
Hey the installer size is 145mb. I was able to download it in 15 seconds
Updating sdk manager will take a while. I am not sure of the file size... It will take a while... You only have to do this once. Updates after this will be quick
Sent from my LG-H901 using Tapatalk

bdorr1105 said:
Hey the installer size is 145mb. I was able to download it in 15 seconds
Updating sdk manager will take a while. I am not sure of the file size... It will take a while... You only have to do this once. Updates after this will be quick
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
I've tried it many times.... i have enough space on my drive, but everytime i try to download this one and only part, prints out this error message....why do i always have so many problems with it

Peccoskaify said:
I've tried it many times.... i have enough space on mi drive, everytime i try to download this one and only part it prints out this error message....why do i always have to have so many problems with it
Click to expand...
Click to collapse
Lol you and me both bro, but you don't have to install that, that is optional, the rest looks good. You should be able to use it now
Edit: looks like a network issue or the repository is down... That will work itself out.. Right now, it is not required
Sent from my LG-H901 using Tapatalk

This is seriously getting ridicolous - Now everything is downloaded, cmd sees the device I have every stupid thing set-up and still....phone only reboots when i type - adb reboot bootloader -
Shell I record it for you?
Edit:
I did record it -

Peccoskaify said:
This is seriously getting ridicolous - Now everything is downloaded, cmd sees the device I have every stupid thing set-up and still....phone only reboots when i type - adb reboot bootloader -
Shell I record it for you?
Edit:
I did record it -
Click to expand...
Click to collapse
Sounds like your bootloader is borked, you should always be able to get into...Were you able to flash TWRP successfully? Not sure where you went wrong, I would try to push boot.img again, you should have a recovery
Go Here

bdorr1105 said:
Sounds like your bootloader is borked, you should always be able to get into...Were you able to flash TWRP successfully? Not sure where you went wrong, I would try to push boot.img again, you should have a recovery
Go Here
Click to expand...
Click to collapse
I followed steps till the one i got stuck in, so no i did not flash TWRP :/ or anything else. - It's weird that it is broken because it's new phone and i did not do anything to it, expect for right now :/ But sure I'll try

Peccoskaify said:
I followed steps till the one i got stuck in, so no i did not flash TWRP :/ or anything else. - It's weird that it is broken because it's new phone and i did not do anything to it, expect for right now :/ But sure I'll try
Click to expand...
Click to collapse
I think your bootloader may still be locked
Have you done this? Make sure USB Debugging is enabled, OEM Unlock is checked, You are in PTP, type adb devices and verify it sees your device then do the following Next:
nvm edited out got ahead of myself

bdorr1105 said:
I think your bootloader may still be locked
Have you done this? Make sure USB Debugging is enabled, OEM Unlock is checked, You are in PTP, type adb devices and verify it sees your device then do the following Next:
nvm edited out got ahead of myself
Click to expand...
Click to collapse
If you look at the video you can see that i have both on and PTP too - without PTP cmd won't see my device...i think
oh sorry

Peccoskaify said:
If you look at the video you can see that i have both on and PTP too - without PTP cmd won't see my device...i think
oh sorry
Click to expand...
Click to collapse
Have you had any luck?
Sent from my LG-H901 using Tapatalk

bdorr1105 said:
Have you had any luck?
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Nope :/

Is there way to flash some LG stock android in my phone so it will have bootloader? :/ - I'm not very good in english so i don't even know what to search for :/

Peccoskaify said:
Is there way to flash some LG stock android in my phone so it will have bootloader? :/ - I'm not very good in english so i don't even know what to search for :/
Click to expand...
Click to collapse
Yea I am looking into it the v10 is hard to find anything
Sent from my LG-H901 using Tapatalk

Peccoskaify said:
Is there way to flash some LG stock android in my phone so it will have bootloader? :/ - I'm not very good in english so i don't even know what to search for :/
Click to expand...
Click to collapse
Ok try this
1. Power phone off
2. Hold volume down and power together 3. Once LG Logo appears, let go of power for 1 second and press power again.. Never let go of volume down
4. Then chose to factory reset
This may resolve the issue so you can retry again
Sent from my LG-H901 using Tapatalk

bdorr1105 said:
Ok try this
1. Power phone off
2. Hold volume down and power together 3. Once LG Logo appears, let go of power for 1 second and press power again.. Never let go of volume down
4. Then chose to factory reset
This may resolve the issue so you can retry again
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Did it, nothing changed, is this reason for refund?

Peccoskaify said:
Did it, nothing changed, is this reason for refund?
Click to expand...
Click to collapse
Ok another method
1. Install Terminal Emulator
2. Open the Terminal
3. Type# su
4. Type# reboot-bootloader
This should go straight to the bootloader, if it doesn't, I am at a loss

bdorr1105 said:
Ok another method
1. Install Terminal Emulator
2. Open the Terminal
3. Type# su
4. Type# reboot-bootloader
This should go straight to the bootloader, if it doesn't, I am at a loss
Click to expand...
Click to collapse
I just can't anymore - so far thank you for your help, even though it's never year you are willing to help, not many people would waste time with me

Peccoskaify said:
I just can't anymore - so far thank you for your help, even though it's never year you are willing to help, not many people would waste time with me
Click to expand...
Click to collapse
Thats not correct, su did not work, you should have a # symbol before the command, guess not being rooted doesn't help
edit: connect your phone to the computer and type the same command
I think strangely it is just recognizing adb reboot and omitting the bootloader, so try adb reboot-bootlader when connected to the computer

Nexus 5 WiFi problem...acting strange....turning ON / OFF and Power ON/ OFF

Gentlemen/ Ladies,
I am NOT a developer, in fact I need a little help here, and searching all over internet, I bet you guys are probably the last resort of true assistance to my problem.
I am a proud Nexus 5 (Hammerhead) phone user, yes, still Nexus 5 because it is such a good reliable phone.
But started the day before, the WiFi is turning itself OFF, and although I tried turning it ON, it just keep searching and searching (where the screen usually display all WiFi networks around, it just shows a energy-bar running from left to right, while bottom is pretty much blank except saying turning ON wifi).
The phone then shutting down itself, OR I have to turn the phone OFF, wait to power ON again, sometimes WiFi works , sometimes it does not, or turn if OFF itself after a few minutes. when it's back ON, it works normally for a short time, then OFF again....
All other functions of the phone are flawless, blue tooth, my t-mobile LTE, have no problems.
At this stage, I can’t tell, it is a software and hardware error.
Did’nt drop on the floor, no water damages, no crack on screen, I have been use it nicely. I noticed the battery drinks fast, and I worried that this problem is the result of bad battery/ shutting down due to empty battery, so yesterday I finally replaced the battery with a brand new one.
I checked my charter internet modem, and wireless router, all seems to be ok, as my other PC and laptop both using hard cable and wireless, other cell phone also use the same WiFi at home, they all function OK.
I ran malwarebytes and panda anti-virus on the Nexus 5, no virus.
I tried suggestions from youtube:
-turn the airplane mode ON/OFF
-turn t mobile, bluetooth ON/OFF
-reset network connection, ( that only brings my t mobile ON)
-Developer mode ON, select legacy DHCP,
As you notice, it’s a Nexus, it still runs on Android 6.01 version, not the latest. And I really do not want to “manufacturer re-set” back to original setting, just too much work, not to mention, a reality that I may not able to get updates from Android as the version is old, which really put me in a more difficult position. I am financially tight now and hoping to continue to use this Nexus 5 for another year before I can afford a new phone.
I also noticed from the website here, there is a "FirstEver" Andriod 8.1 for nexus 5 hammerhead available, Will it solve my WiFi problem/ error? Also, it will be nice for my Nexus 5, right? My phone is still running on Android 6 !
Any suggestions, please. Thank you all !

Hello, unfortunately this was very common on the nexus 5. It is a hardware issue. It has something to do with the WiFi chip that's on the motherboard.
It happened to me and funny enough I'm responding to you on that same Nexus 5.
My solution was to buy a used (damaged external) Nexus with functioning internals; CPU, motherboard, BT, WiFi etc etc and then swap out the damage motherboard with the used one. You would have to either flash/reset an OS on the replacement motherboard to "clean" it up.
There's a few tutorials here on XDA on how to disassemble the the back and battery removal. Do a quick search on Google with the addition of "XDA" on the end of the search criteria. The search bar here on XDA is terrible.
Good luck.

Mojar7070 said:
Hello, unfortunately this was very common on the nexus 5. It is a hardware issue. It has something to do with the WiFi chip that's on the motherboard.
It happened to me and funny enough I'm responding to you on that same Nexus 5.
My solution was to buy a used (damaged external) Nexus with functioning internals; CPU, motherboard, BT, WiFi etc etc and then swap out the damage motherboard with the used one. You would have to either flash/reset an OS on the replacement motherboard to "clean" it up.
There's a few tutorials here on XDA on how to disassemble the the back and battery removal. Do a quick search on Google with the addition of "XDA" on the end of the search criteria. The search bar here on XDA is terrible.
Good luck.
Click to expand...
Click to collapse
@Mojar7070,
Thanks for yr reply.
My situation is WiFi sometimes works, sometimes it does'nt. That's why it is difficult for me to determine IF it is a hardware/software issue. Do you think by replacing the pair antenna will work?
https://www.ebay.com/itm/1-Pair-Wir...-LG-Google-Nexus-5-D820-D821-USA/252497470238
I hear what you said, it just that it is difficult to determine the used one truly does not have other hardware error inside, until it's too late, more importantly, I am not someone who is really good in repairing hardware.
Can you share with me how do I go by backing-up the whole Android OS + all data onto my computer? Especially the Android OS....
Million thanks,

Hello, I don't think the wire itself is the issue. You can try, I'm just not sure.
Do you have custom recoveryOr at least have have the boot bootloader unlocked on your phone??
Having TWRP recovery simplifies everything as far as backing up information on the phone.
Your options for downloading from your phone is limited since WiFi is broke. Do you have some data room to upload information to Google backup?? That may be your only option, especially if you're not on a custom recovery.

Mojar7070 said:
Hello, I don't think the wire itself is the issue. You can try, I'm just not sure.
Do you have custom recoveryOr at least have have the boot bootloader unlocked on your phone??
Having TWRP recovery simplifies everything as far as backing up information on the phone.
Your options for downloading from your phone is limited since WiFi is broke. Do you have some data room to upload information to Google backup?? That may be your only option, especially if you're not on a custom recovery.
Click to expand...
Click to collapse
Hello,
Thanks for yr replies.
At this stage, I don't a custom recovery/ boot-loader/ TWRP, BUT see this link below especially step 4 and 5 are exactly what you are saying?! :
https://www.firstever.eu/first-ever-android-8-1-for-nexus-5/#comment-113
If I go get the Android 8 thru them now, it seems to me step 4 & 5 cover what you just mentioned !?
But the thing is, from logical thinking, I should be backing up FIRST, in case if anything don't work out ! Right ?? I know Windows PC, not anroid phones/ OS !!
You are right ON, unless I want to pay more $ for data thru T-mobile LTE for this backup....
When I connect the phone to my PC thru USB, seems to me all things are presented. Can I just copy/ paste onto a folder I create on my PC, but I take it that's NOT bootable ? Or should then put it onto a USB flash drive to make it bootable?
Thank you,

STDupont said:
Hello,
Thanks for yr replies.
At this stage, I don't a custom recovery/ boot-loader/ TWRP, BUT see this link below especially step 4 and 5 are exactly what you are saying?! :
https://www.firstever.eu/first-ever-android-8-1-for-nexus-5/#comment-113
If I go get the Android 8 thru them now, it seems to me step 4 & 5 cover what you just mentioned !?
But the thing is, from logical thinking, I should be backing up FIRST, in case if anything don't work out ! Right ?? I know Windows PC, not anroid phones/ OS !!
You are right ON, unless I want to pay more $ for data thru T-mobile LTE for this backup....
When I connect the phone to my PC thru USB, seems to me all things are presented. Can I just copy/ paste onto a folder I create on my PC, but I take it that's NOT bootable ? Or should then put it onto a USB flash drive to make it bootable?
Thank you,
Click to expand...
Click to collapse
Hello,
Yes, steps 4 and 5 from that site is what I'm referring to. Like I've mentioned before search here on XDA for actually guides and tutorials.
Installing TWRP recovery is the very first step in "fully" backing up your device. Data, OS, user preference and all apps. Plugging into a PC and moving personal folders and files is just that. Transferring files and folders. Now, you can definitely do that and have your personal data on the PC but if you plan to install the 8.1 Android OS anyways you'll need TWRP recovery. So why not "kill two birds with one stone."
You are correct, simply transferring files/folders will not translate to a bootable medium. Having a TWRP backup will do just that. It will act like a "bootable" file whenever you need to roll back to a previous state.
Once you search a guide/tutorial, you'll find that the whole process is done through a PC. So you'll be fine. But please read through the guides first and get familiar with the process before typing any commands in.
Good luck.

Mojar7070 said:
Hello,
Yes, steps 4 and 5 from that site is what I'm referring to. Like I've mentioned before search here on XDA for actually guides and tutorials.
Installing TWRP recovery is the very first step in "fully" backing up your device. Data, OS, user preference and all apps. Plugging into a PC and moving personal folders and files is just that. Transferring files and folders. Now, you can definitely do that and have your personal data on the PC but if you plan to install the 8.1 Android OS anyways you'll need TWRP recovery. So why not "kill two birds with one stone."
You are correct, simply transferring files/folders will not translate to a bootable medium. Having a TWRP backup will do just that. It will act like a "bootable" file whenever you need to roll back to a previous state.
Once you search a guide/tutorial, you'll find that the whole process is done through a PC. So you'll be fine. But please read through the guides first and get familiar with the process before typing any commands in.
Good luck.
Click to expand...
Click to collapse
Hello,
Thank you for yr confirmation, I was not sure, but you strengthen my thought.
Would you please pinpoint to me just where exactly I can read the "guide/ tutorial" section that applies in my situation? This website is so big, I almost "lost in ocean" here....
I will first backup my Nexus 5 today, and waiting for yr "guide/ tutorial" section, mostly like do the installation android 8.1 either Monday night or tuesday night. I notice the guy at FirstEver already produced his custom Android 9.0 version, but it is too new for me, I am thinking he is still perfecting his version, just a thought !
Have you tried the new 9.0 Android yet?
Thank you,

Mojar7070 said:
Hello,
Yes, steps 4 and 5 from that site is what I'm referring to. Like I've mentioned before search here on XDA for actually guides and tutorials.
Installing TWRP recovery is the very first step in "fully" backing up your device. Data, OS, user preference and all apps. Plugging into a PC and moving personal folders and files is just that. Transferring files and folders. Now, you can definitely do that and have your personal data on the PC but if you plan to install the 8.1 Android OS anyways you'll need TWRP recovery. So why not "kill two birds with one stone."
You are correct, simply transferring files/folders will not translate to a bootable medium. Having a TWRP backup will do just that. It will act like a "bootable" file whenever you need to roll back to a previous state.
Once you search a guide/tutorial, you'll find that the whole process is done through a PC. So you'll be fine. But please read through the guides first and get familiar with the process before typing any commands in.
Good luck.
Click to expand...
Click to collapse
Hello Mojar7070,
I ran into some difficulties as I am trying to back-up, seeking guidance:
On Step4 of the FirstEver pages-https://www.firstever.eu/first-ever-android-8-1-for-nexus-5/#
When I typed adb root bootloader, on my DOS black screen of my computer, it says:
"adb" is not recognized as in internal or external command operable program or batch file.
Earlier, as I was doing the ADB , step 9 and step 10 did not pop up, but it did say completed in blue little screen, I did that 3 times, same thing, following their instruction as below:
https://androidmtk.com/download-best-android-adb-driver
Any suggestions ? Thank you,

STDupont said:
Hello Mojar7070,
I ran into some difficulties as I am trying to back-up, seeking guidance:
On Step4 of the FirstEver pages-https://www.firstever.eu/first-ever-android-8-1-for-nexus-5/#
When I typed adb root bootloader, on my DOS black screen of my computer, it says:
"adb" is not recognized as in internal or external command operable program or batch file.
Earlier, as I was doing the ADB , step 9 and step 10 did not pop up, but it did say completed in blue little screen, I did that 3 times, same thing, following their instruction as below:
https://androidmtk.com/download-best-android-adb-driver
Any suggestions ? Thank you,
Click to expand...
Click to collapse
https://forum.xda-developers.com/go...ide-nexus-5-how-to-unlock-bootloader-t2507905
https://forum.xda-developers.com/google-nexus-5/general/how-to-nexus-5-one-beginners-guide-t2510966
Hello,
Try out 1 or both of the links above. That should get you started in the right direction.
---------- Post added at 03:28 AM ---------- Previous post was at 03:26 AM ----------
Mojar7070 said:
https://forum.xda-developers.com/go...ide-nexus-5-how-to-unlock-bootloader-t2507905
https://forum.xda-developers.com/google-nexus-5/general/how-to-nexus-5-one-beginners-guide-t2510966
Hello,
Try out 1 or both of the links above. That should get you started in the right direction.
Click to expand...
Click to collapse
https://forum.xda-developers.com/go...ol-tool-one-driversunlocktwrpfactory-t3358707
Try this one as well. It's an all in one root tool.
Good luck.

Mojar7070 said:
https://forum.xda-developers.com/go...ide-nexus-5-how-to-unlock-bootloader-t2507905
https://forum.xda-developers.com/google-nexus-5/general/how-to-nexus-5-one-beginners-guide-t2510966
Hello,
Try out 1 or both of the links above. That should get you started in the right direction.
---------- Post added at 03:28 AM ---------- Previous post was at 03:26 AM ----------
https://forum.xda-developers.com/go...ol-tool-one-driversunlocktwrpfactory-t3358707
Try this one as well. It's an all in one root tool.
Good luck.
Click to expand...
Click to collapse
Hello Mojar7070,
From the first link you gave me, I ran into more difficulties....( the instruction of that link is no where near the actual scene I ran into....see below 1-5 )
I clicked the download link for Android SDK, my plan was first to get the ADB working.
I got the Android Studio thing that's about over 1GB,
From the link-ADB and Fastboot Installation
1. Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components(Thanks @El Daddy)
Link removed since it expired
2. Extract the zip and place the android-sdk-windows folder on your desktop.
**If you chose to download the slimmed sdk skip to step 5**
3. Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
4. Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
5. To confirm that it is indeed working, open a command prompt window and enter the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
adb version
If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are ....
#2-5 are no where like that at all. See the photo below:
{
"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"
}
After the download installation, i got the first photo, double click to install, took more than hour and half, finally says cannot be done, see photo #2, also during installtion, see Java error.
What did i do wrong??

STDupont said:
Hello Mojar7070,
From the first link you gave me, I ran into more difficulties....( the instruction of that link is no where near the actual scene I ran into....see below 1-5 )
I clicked the download link for Android SDK, my plan was first to get the ADB working.
I got the Android Studio thing that's about over 1GB,
From the link-ADB and Fastboot Installation
1. Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components(Thanks @El Daddy)
Link removed since it expired
2. Extract the zip and place the android-sdk-windows folder on your desktop.
**If you chose to download the slimmed sdk skip to step 5**
3. Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
4. Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
5. To confirm that it is indeed working, open a command prompt window and enter the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
adb version
If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are ....
#2-5 are no where like that at all. See the photo below:
After the download installation, i got the first photo, double click to install, took more than hour and half, finally says cannot be done, see photo #2, also during installtion, see Java error.
What did i do wrong??
Click to expand...
Click to collapse
Hello,
I think you should try the last link. The all in one tool. I know it took me a few times to figure out how to correlate the instructions to what is on the PC screen. The all in one tool simplifies everything.
You can YouTube the tutorials as well get a step by step process.
Good luck.

Hello,
Seems to me that All-In-1 tool can do many things.
But in my situation now, i first need to get the ADB works otherwise I cannot move forward getting back-up, does that "install driver" will get the adb works? If not, which function should I select?
Thanks,

Mojar7070 said:
Hello,
I think you should try the last link. The all in one tool. I know it took me a few times to figure out how to correlate the instructions to what is on the PC screen. The all in one tool simplifies everything.
You can YouTube the tutorials as well get a step by step process.
Good luck.
Click to expand...
Click to collapse
Hello Mojar7070,
Just now, i tried SDK thing again, noticed that JAVA error, i went ahead the got the latest JAVA April 2019 version, this time, the SDK went ok without any error this time.
My question is: when I go back to DOS, to type the cmd command(s) according the FirstEver's instruction #4/ 5, how do I use the SDK thing to solve the " adb is not recognized as an internal or external command operable program or batch file" error ??
Thank you,

STDupont said:
Hello Mojar7070,
Just now, i tried SDK thing again, noticed that JAVA error, i went ahead the got the latest JAVA April 2019 version, this time, the SDK went ok without any error this time.
My question is: when I go back to DOS, to type the cmd command(s) according the FirstEver's instruction #4/ 5, how do I use the SDK thing to solve the " adb is not recognized as an internal or external command operable program or batch file" error ??
Thank you,
Click to expand...
Click to collapse
Gentelmen/ Ladies,
I truly need some help here !
FYI, I did not try the last link, as it seems more complicated and does not looks like it can solve my situation.
I am stuck, first link: downloaded and installation the thing SDK, tried typing the command in DOS, same thing. It is very very frustrated when the instruction(s) are no where near the actual thing from what I see....
Anyone here located near downtown Los Angeles ? Thank you...

[GUIDE][ROOT] QLink Serrano 3 (HPP-L55B) Bootloader Unlocking And Rooting Guide

QLink Serrano 3
Model No. HPP-L55B
By Hot Pepper Mobile
{
"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"
}
Bootloader Unlocking
And Rooting Guide ​
OVERVIEW:
This guide provides step-by-step instructions for unlocking the bootloader and achieving root access on the QLink Serrano 3. Please note that this guide is specifically for the QLink variant of the Serrano 3 (HPP-H55L), as I have not verified the applicability of this guide on other carrier variants of this smartphone. To simplify the rooting procedure, and to cater this guide to new and inexperienced members, I have provided a boot image pre-patched for Magisk systemless root support below, in the downloads section.
IMPORTANT NOTE: The pre-patched boot image in the downloads section below corresponds with firmware build HPP-L55B-J-9.0.0. If your Serrano is running a different build, flashing the pre-patched boot image provided may or may not result in compatibility issues. In short, the best rule of thumb when achieving systemless root is to always patch an image that matches the firmware build installed on your device, otherwise you may encounter issues such as broken WiFi, broken Bluetooth, or your device may not boot at all. Should any members encounter issues of this sort, you may flash your device with the HPP-L55B-J-9.0.0 firmware by following my firmware restoration guide for the Serrano here: QLink Serrano 3 Firmware Restoration Guide
PREREQUISITES:
You will need a Windows PC or laptop with the ADB & fastboot tools installed. I have provided a link below for the latest Minimal ADB & Fastboot tools. You will need the factory supplied, or a quality equivalent micro USB to USB-A data syncing/charging cable. And, you will need your QLink Serrano 3 smartphone. I again emphasize that this guide has only been tested on the QLink variant of the Serrano (HPP-L55B).
DISCLAIMER:
The tasks outlined in this guide encompass inherent risks to the integrity and operability of your smartphone. Moreover, unlocking the bootloader/rooting the device will void any active manufacturer's warranty you may have on your Serrano. By proceeding further, you are assuming full responsibility for the state and health of your smartphone. As such, you are hereby absolving me of any responsibility or civil liability in the unfortunate event things go badly. This guide has been fully and thoroughly tested. Follow the instructions carefully, employ some patience, and pay attention to detail and I'm confident things will go smoothly. It should also be noted that the tasks outlined herein can be carried out using a Mac or Linux computer as well. This particular guide, however, will focus solely on a Windows -based setup.
I.. INSTALLING ADB & FASTBOOT
Because both tasks outlined in this guide require ADB/Fastboot communication between your phone and PC/laptop, this first section will focus on proper installation of the ADB & Fastboot utilities on your Windows computer. If you already have a working ADB/Fastboot environment, skip down to the next section on unlocking the bootloader. Otherwise, follow these steps:​
Download the Minimal ADB & Fastboot tools installer from the link below. Right click the .exe file and opt to run it as an administrator. Follow the on-screen prompts and complete the installation;​
Open the Windows File Explorer, go to This PC and open your C: drive directory. Open Program Files x86 and locate the Minimal ADB & Fastboot folder. Copy the folder and then paste it on your desktop (this step merely configures the ADB & Fastboot directory to a more convenient location from which to work);​
Open the Minimal ADB & Fastboot folder and double click the file named cmd-here. A command prompt will open. Next, connect your Serrano to your Windows computer using a suitable micro USB to USB-A data syncing cable. Ensure that USB Debugging is enabled in your Developer Options menu.​
In the command window you opened in the previous step, execute this command:
Code:
adb devices
Watch your device display for a USB Debugging authorization prompt. Grant the request. If properly connected, the command window will output an alphanumeric string consistent with your device serial number;​
If the command window does not display your serial number, or if you get a WAITING notification, your smartphone isn't communicating properly with your PC or laptop. Try another data syncing cable,; change USB ports; and/or reinstall the Minimal ADB & Fastboot tools on your computer;​
Once you have established proper device communication, we will now test fastboot mode communication. Execute this command:
Code:
adb reboot bootloader
Your device should now boot into fastboot mode, which will be illustrated by a darkly backlit display with the words => FASTBOOT mode.... displayed in a white font at the bottom-left of the screen;​
Next, execute this command:
Code:
fastboot devices
Similar to before, if properly connected, the command window will display your device S/N. If you don't see your S/N, or if the command window says WAITING, you are not properly connected. Again, try changing USB ports, try another data syncing cable, and/or reinstall the Minimal ADb & Fastboot tools on your computer.​
II. UNLOCKING THE BOOTLOADER
WARNING: Unlocking the bootloader triggers a native Android security mechanism that forces the device into a factory data reset. This will erase all saved userdata on your phone. Before proceeding further, make a backup of all saved userdata you wish to keep.​
Open device Settings>System>Developer Options, and enable the OEM Unlock option;​
Boot into fastboot mode by executing:
Code:
adb reboot bootloader
Once in fastboot mode, it's time to initiate bootloader unlocking. Execute this command:
Code:
fastboot flashing unlock
Your smartphone display will now prompt you to tap Volume + to proceed with unlocking, or Volume - to cancel;​
After pressing Volume +, the unlock sequence will finish in just a few seconds. Now reboot to complete the process: Execute:
Code:
fastboot reboot
As mentioned previously, your phone will now initiate a mandatory factory data reset, after which your device will boot into the initial setup phase of the Android OS. Your bootloader is now officially unlocked.​
III. ROOTING THE SMARTPHONE
Now that the bootloader is unlocked, attaining root access is very straightforward.​
Download the patched boot image and vbmeta image files from the links below and save the files in your Minimal ADB & Fastboot folder;​
Double click the cmd-here.exe file to open a command window. Execute this command to flash the patched boot image:
Code:
fastboot flash boot patched_boot.img
Now we will disable dm-verity by executing this command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Now, execute this command to reboot your phone:
Code:
fastboot reboot
Upon reboot into the Android OS, locate the Magisk app or its stub placeholder in your app drawer. Open Magisk, grant any requested permissions, and follow any prompts to finish setting up the root environment. Magisk may initiate a reboot to complete root setup. If the Magisk app or its stub placeholder is not in your app drawer, download the Magisk v25.2 APK from the link below and install it on your phone. That's it. You are rooted with the Magisk v25.2 systemless root solution.​
DOWNLOADS:
• Minimal ADB & Fastboot v1.4.3
• Patched boot.img
• vbmeta.img
• Official Magisk Releases (GitHub)​

Thank you for this I'm going to try this. Here are some of the issues I have been having. When I plug it in to charge it. It keeps trying to boot and will not stop. I have to press the power button to buy bypass an error message that says this device is corrupted. I just got this phone from qulink (Amazon) and it was doing this since I opened it. It will not update the system. I believe the boot issue may have something to do with it. I'm not sure what kind of bloat wear it has but I do know something is running rapidly in the back ground I have practically no battery life and charging it is a night near. Another important question is can I use a chrome book to do the procedure? Any input would be greatly appreciated.
Thanks
John Bridges

John Bridges said:
Thank you for this I'm going to try this. Here are some of the issues I have been having. When I plug it in to charge it. It keeps trying to boot and will not stop. I have to press the power button to buy bypass an error message that says this device is corrupted. I just got this phone from qulink (Amazon) and it was doing this since I opened it. It will not update the system. I believe the boot issue may have something to do with it. I'm not sure what kind of bloat wear it has but I do know something is running rapidly in the back ground I have practically no battery life and charging it is a night near. Another important question is can I use a chrome book to do the procedure? Any input would be greatly appreciated.
Thanks
John Bridges
Click to expand...
Click to collapse
Greetings @John Bridges. You have come to the right place. Sounds like you're stuck in a classic boot loop. Flashing the factory firmware offered in my guide should certainly restore your device to its stock factory state.
The firmware, unfortunately, does include the typical bloatware specific to QLink devices. Of course,, once you get your phone restored via firmware flashing, you can always opt to unlock your bootloader, achieve root and debloat tie stock OS. So, your best option may be to first restore your device by installing firmware, and then rooting.
Serrano Firmware Restoration Guide

Greetings Viva,
Thanks for the great response. I will try your great advice and respect you for dedicating you're time to help the Android epidemic.

John Bridges said:
Greetings Viva,
Thanks for the great response. I will try your great advice and respect you for dedicating you're time to help the Android epidemic.
Click to expand...
Click to collapse
Thank you for the kind words. The type of boot loop you are experiencing is caused from data corruption that occurs when Android decrypts the /userdata partition during the boot sequence. By default, Android encrypts all data on this partition for user security; as such, whenever your device boots up, Android decrypts the data to make it accessible. If any errors or data corruption are incurred during this process, you will be promoted to either try again or perform a factory data reset.
Sorry I just saw your reference to the Chromebook. I'm afraid it won't be much help on this. My guide focuses on a Windows setup; however, Linux or Max can also be used. Out of curiosity, have you first tried factory resetting the phone?

Yes I did still didn't help When I'd tried to start it a message would appear saying the device is court press power button to continue and it came out of the box with this problem. I tried to update it and several different errors would show up,one was something about OTA, Would it be possible to do the procedure with a chrome book?

John Bridges said:
Yes I did still didn't help When I'd tried to start it a message would appear saying the device is court press power button to continue and it came out of the box with this problem. I tried to update it and several different errors would show up,one was something about OTA, Would it be possible to do the procedure with a chrome book?
Click to expand...
Click to collapse
The device is court I mean.

Corrupt I mean

John Bridges said:
Corrupt I mean
Click to expand...
Click to collapse
I understand on the device being data corrupted. Firmware restoration is definitely your best option. I know of no way to flash firmware using a Chromebook. I'll research it and see if it can be done.
Okay I did find an XDA guide on utilizing ADB & fastboot on Chromebook. https://forum.xda-developers.com/t/...-chromeos-adb-fastboot.2157230/#post-38232908
However, even the developers who posted in that thread refer to the procedure as extremely complex.

@John Bridges have you had any luck with restoring your firmware via Chromebook?

For those members who detest the abundance of bloatware included in the factory firmware package, I have unpacked the super.img, removed a considerable amount of the QLink apps, services and other bloatware, and then repacked the super.img. I have removed the annoying QLink lock screen, the QLink "free WiFi" service, a number of the preinstalled Google apps, and some other RAM demanding apps & services. I've noticed a remarkable improvement in performance on my own device as a result of debloating the stock OS in this manner.
I will post a new thread this weekend with this debloated stock OS, and instructions for fastboot installation. You will need an unlocked bootloader to install it.

VivaI
I just haven't had time to do it yet I am anxious to do it however and I will let you know how it went for sure.

VivaI and others,
It is a shame that people like myself that have to get these government phones to have one or hacked and it's a great thing you all are doing to give us a phone that will be actually uncorrupted. I don't know if this matters but the phone I got was from Amazon and it is supposed to be unlocked I don't know if that means the bootlegger is unlocked or anything else but I thought it may be helpful to you to know this.

John Bridges said:
VivaI and others,
It is a shame that people like myself that have to get these government phones to have one or hacked and it's a great thing you all are doing to give us a phone that will be actually uncorrupted. I don't know if this matters but the phone I got was from Amazon and it is supposed to be unlocked I don't know if that means the bootlegger is unlocked or anything else but I thought it may be helpful to you to know this.
Click to expand...
Click to collapse
And I'm talking about the phone or the replacement phone you get from q Link it is supposed to be unlocked and it comes from Amazon I checked on it online.

John Bridges said:
And I'm talking about the phone or the replacement phone you get from q Link it is supposed to be unlocked and it comes from Amazon I checked on it online.
Click to expand...
Click to collapse
To the best of my knowledge -- but not confirmed 100% -- all variants of the Serrano are GSM unlocked. Mine originally came from Amazon as well. By unlocked, I am referring to network unlocked and not the bootloader.

Very nice to know! I'm going to try and get it done tomorrow.

John Bridges said:
Very nice to know! I'm going to try and get it done tomorrow.
Click to expand...
Click to collapse
If you have any questions, or if you encounter any obstacles during the procedure, just let me know.

Viva La Android said:
For those members who detest the abundance of bloatware included in the factory firmware package, I have unpacked the super.img, removed a considerable amount of the QLink apps, services and other bloatware, and then repacked the super.img. I have removed the annoying QLink lock screen, the QLink "free WiFi" service, a number of the preinstalled Google apps, and some other RAM demanding apps & services. I've noticed a remarkable improvement in performance on my own device as a result of debloating the stock OS in this manner.
I will post a new thread this weekend with this debloated stock OS, and instructions for fastboot installation. You will need an unlocked bootloader to install it.
Click to expand...
Click to collapse
Could you share the link to this thread please? The search function on this forum is frustrating and not turning up any relevant results and with your profile set to private I coludn't search for your threads either.
Crap nevermind, I just noticed I could pull up threads you created using the search function and looks like it hasnt been posted yet. Could you update this thread when it is?

GIutton said:
Could you share the link to this thread please? The search function on this forum is frustrating and not turning up any relevant results and with your profile set to private I coludn't search for your threads either.
Crap nevermind, I just noticed I could pull up threads you created using the search function and looks like it hasnt been posted yet. Could you update this thread when it is?
Click to expand...
Click to collapse
Not finalized. There are bugs to work out.

Anyone know why we can't modify, add, or remove files from the system partition using an app like root explorer? I wanted to change my bootanimation on my hot pepper serrano 3 and remove unwanted apps and files since i now have it rooted with magisk 25.2 but system partition seems to be read only at the moment. You can delete stuff from the system partition but they come back after a reboot. Same goes with modifying or adding anything in /system. You need to mention in the OP that we only have partial root not full root. Can anyone confirm this and is there a solution to this problem? Is it just me that is having this issue?