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 ?
Related
Hey Guys,
since I heard many questions lately concerning flashing a boot.img onto the One S I decided to give you a small tutorial! (which should also work on any other device with bootloadermode)
If you have fastboot already installed on your PC it's very quick & easy!
Pls be aware that this could damage your phone & I'm not responsible for this. so only do this if you really feel comfortable with it & you know about the risks!
First of all you need to have fastboot & adb installed, as well as the drivers for the One S. If you haven't, move on to the second post in this thread!
Click to expand...
Click to collapse
If you are on a Sense-based ROM make sure you haven't ticked the fast boot option in the settings!
Click to expand...
Click to collapse
Step 0,5
What is the boot.img?
-> basically it contains the kernel & the ramdisk. But let's hear what the pros have to say:
"The boot.img is a small(ish) file that contains 2 main parts, the kernel (the brain of the Android system) and the ramdisk (a core set of instructions and binaries that begins the boot process and controls base aspects of the system, such as mountpoints, memory management and startup services)" Source
Click to expand...
Click to collapse
Further information can be found here.
Click to expand...
Click to collapse
Do I need to flash the boot.img manually in fastboot?:
No, if you're using TWRP and are on a Hboot-version lower than 1.13
Yes, if you're using any other recovery (like CWM)
Yes, if you're using TWRP and your ville has the Hboot-version 1.13 or higher
Click to expand...
Click to collapse
1.Step
reboot your Phone into the bootloader.
This can either be done via
- powering off and keeping volume up & the power-button pressed
- the extended power-menu (If your ROM has it, just select "reboot" & then "bootloader")
- via adb, connect your phone with the pc, make sure it says "USB debugging connected", go to Android/platform-tools/ & then press shift while you perform a right click with the mouse, then choose "open prompt here", type
Code:
adb reboot-bootloader
& press enter. Your One S should then reboot into the bootloader
I personally prefer one of the last two methods, depending which way occurs faster to me at that specific moment.
Click to expand...
Click to collapse
2.Step
make sure it says "Fastboot USB" like in the following picture
{
"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"
}
(Source = Google)
Click to expand...
Click to collapse
3.Step
Test if it your device has been detected with the following command:
Code:
fastboot devices
if it gives you an answer other than a blank one or an error there you go
Click to expand...
Click to collapse
4.Step
copy the boot.img you want to flash into the folder C:\android\platform-tools\ & then execute the command
Code:
fastboot flash boot boot.img
(if your boot.img is named differently then adjust the last part of the command)
wait for it to succeed.
if it says okay two times & the prompt reappears everything should be fine
Click to expand...
Click to collapse
5.Step
reboot your device with
Code:
fastboot reboot
Click to expand...
Click to collapse
6.Step
If you want check
Code:
Settings -> About phone -> Kernel
if it matches the boot.img you just flashed
Click to expand...
Click to collapse
The whole process should look something like this in your CMD:
Click to expand...
Click to collapse
Here you go!
Quick & easy!
When I helped please press the thanks button!
If you have any suggestions to make it even easier of found a mistake, please tell me, it's already very late in Germany
BE AWARE THAT I'M NOT RESPONSIBLE IF IT DOESN'T WORK OR BREAKS YOUR PHONE! THIS IS JUST THE WAY I UPDATE THE BOOT.IMG ON MY PHONE!
Installing ADB and Fastboot
It's actually pretty easy!
1. Step
download the Android SDK from HERE
Alternatively you can also download the USB drivers & the runtimes for adb & fastboot as a standalone as provided by Inferi0r in the 4th post:
Inferi0r said:
USB drivers only & the adb/fastboot-runtimes only
Click to expand...
Click to collapse
[Download carefully, didn't test them for viruses or (mal)function]
Click to expand...
Click to collapse
2. Step
Run the downloaded file & change the extracting-folder directly to C:\
(..this will take some time...)
You should then have a folder C:\Android
Click to expand...
Click to collapse
3. Step
If you haven't installed the One S' drivers yet, download HTC Sync (e.g. from here, or here) & install it, which will also install the drivers needed for adb & fastboot to work.
If you have them installed already, skip this one & proceed to step 4.
Click to expand...
Click to collapse
4. Step
- go to C:\Android again
- press
Code:
Win + R
on your keyboard to bring up the Run dialog
- type in
Code:
sysdm.cpl
and hit OK
- now, the System Properties panel should open. Click on the Advanced tab
- in the Advanced Tab click on Environment Variables
- at the Environment Variables window find where it says Path in the Section of System variables, click on it, and press the Edit button
- when the new window opens, type in
Code:
;C:\Android
at the very end and klick OK
- now close all the windows, that's all, you're done!
Click to expand...
Click to collapse
5. Step
- go to C:\Android\platform-tools\ again
- right-click with your mouse while pressing shift
- select "open prompt here" & then you're ready to go to.
- most common adb/fastboot commands:
- adb commands
- fastboot commands
- by entering
Code:
adb help
or
Code:
fastboot help
Click to expand...
Click to collapse
When I helped please press the thanks button!
Sticky..
Here are links to usb drivers only and adb/fastboot runtimes only.
Inferi0r said:
Here are links to usb drivers only and adb/fastboot runtimes only.
Click to expand...
Click to collapse
Thank you, will implement them later!
[edit] implemented
Nice write up so cleanly written.
Thanks!
Thanks for posting!
Anyone have any sweet boot images they want to share? I'll see what I can dig up for our screen size and post some myself soon.
Excellent post, thank you. You could also mention the easiest way to boot into bootloader: a root enabled app like Quick Boot, or even Titanium Backup has the option.
Sent from my H1S using XDA Premium.
oh finally thank you ive been trying to find how to do this
i wish HTC phones were easy as samsung phones
So boot.img is basically a kernel?
ri123 said:
So boot.img is basically a kernel?
Click to expand...
Click to collapse
basically it contains the kernel & the ramdisk. But there also are some other things:
"[boot.img is a] custom android format consisting of a 2k header, followed by a gzipped kernel, followed by a ramdisk, followed by a [optional] second stage loader" Source
Click to expand...
Click to collapse
"The boot.img is a small(ish) file that contains 2 main parts, the kernel (the brain of the Android system) and the ramdisk (a core set of instructions and binaries that begins the boot process and controls base aspects of the system, such as mountpoints, memory management and startup services)" Source
Click to expand...
Click to collapse
Further information can be found
HERE
& Here
[edit] added this to the OP
fipsib said:
... 3.Step
Test if it your device has been detected with the following command:
Code:
fastboot devices
if it gives you an answer other than a blank one or an error there you go
4.Step
copy the boot.img you want to flash into the folder C:\android\platform-tools\ & then execute the command
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
You should consider adding an extra 3.5 step like this:
Code:
fastboot boot boot.img
This step is meant to test the kernel & ramdisk before flashing it. Of course, the phone might not be fully functional because the modules in /system/lib/modules might not be paired with the kernel in boot.img. But at least you can see your phone booting!
Why do I have to do that? Can't I just flash the kernel through TWRP or CWM?
iCaptivate said:
Why do I have to do that? Can't I just flash the kernel through TWRP or CWM?
Click to expand...
Click to collapse
You need to do this due to the restrictions that are given with S-On.
The team behind TWRP somehow found a way to flash the boot.img sometimes. But for me (or my device) this didn't work.
this is very confusing to me
i wish if there was an easier way
AlxMAX said:
You should consider adding an extra 3.5 step like this:
Code:
fastboot boot boot.img
This step is meant to test the kernel & ramdisk before flashing it. Of course, the phone might not be fully functional because the modules in /system/lib/modules might not be paired with the kernel in boot.img. But at least you can see your phone booting!
Click to expand...
Click to collapse
I don't think that this is necessary as it will only confuse people not so familliar with the matter, but thank you for your input
a doubt, I have a friend who wants to put the rom CM9, the question you have is: how to flash the boot.img fastboot in ubuntu?
Thanks!
שנשלח הוז שלי באמצעות Tapatalk2
cualla84 said:
a doubt, I have a friend who wants to put the rom CM9, the question you have is: how to flash the boot.img fastboot in ubuntu?
Thanks!
שנשלח הוז שלי באמצעות Tapatalk2
Click to expand...
Click to collapse
should be exactly the same, only with the difference that the Android SDK should be located at
Code:
~/android_sdk/platform-tools/
or
Code:
~/bin/
i have a problem with step 5
i dont have a folder called "platform-tools"
i got two folders
platform
and
tools
qwerty warrior said:
i have a problem with step 5
i dont have a folder called "platform-tools"
i got two folders
platform
and
tools
Click to expand...
Click to collapse
while installing the android sdk did you download "tools", too?
The SoupKit
{
"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"
}
What is SoupKit? At it's heart, SoupKit is for those who are tired of messing around with Windows and are ready to do try something that works. It was created to be "sort of" modular in that after the ADB installer has been installed, other Linux scripts can be installed and run from the command line by just typing the name of the script and without worrying about changing directories or dealing with permissions. It's intended to make the transition from Windows to Linux for Android a little bit easier.
How does it work?
The SoupKit ADB Installer --- FOR ALL KINDLE FIRES
This puts everything where it needs to be, installs any necessary dependencies, installs drivers, configures Linux to run adb and fastboot commands, puts the SoupKit in your $PATH and cleans up after itself, all while taking a fraction of the space needed for the Android SDK. What this means for you is, you will be able open any terminal window and start entering adb or fastboot commands immediately. There's no need to change directories, add sudo commands or certain operators that are confusing to command line newbies ( ./ ). You can enter commands just as you see them in tutorials. No more worrying about “ADB Offline”, “Status Unknown” or “List of devices attached ????????????????”. This alone can make a huge difference for anyone having Kindle Fire problems that can't be fixed in Windows or those who are overwhelmed by the technicalities of configuring Linux for Android.
What you need:
First, you need Linux. Don't worry, it's not as bad as you may think.
Luckily, all Linux distros are free to download and install on your computer. It can also be booted from a USB flash drive so you don't have to wipe out your current OS (although you probably should anyway). You can use a VM, but the only VM that I've found that can detect the Kindle Fire in fastboot mode is Parallels. Vmware won't cut it, and VirtualBox sure as hell won't cut it so don't waste your time with them if you ever need to do anything in fastboot (if you're bricked, you need fastboot).
Probably the best method to get Linux running for a new user is by setting up a Linux LiveUSB.
I'm not going to teach you how to set up a Linux LiveUSB, but there are plenty of FREE programs out there that will not only create a Linux LiveUSB for you, but will download your choice of distro as well, and all you need is a USB flash drive (preferably 8GB or larger). A Google search of “Linux LiveUSB” will offer plenty of choices, although, PendriveLinux seems to be a favorite among most. Just be sure to add plenty of “persistence” (1 or more gigabytes) or you will lose everything every time you reboot. And the better quality of flash drive you can use, the better it will be in the long run. Some flash drives just don't do well and can cause some file system corruption over time (not something you want to be dealing with while you're having Kindle Fire problems).
You'll also have to figure out how to boot your computer from a USB. Check your computer's BIOS manufacturer website for instructions on how to do this.
If you're using a LiveUSB, there is no root/sudo password, just hit enter.
Do not use a USB 3.0 port
Once you have Linux installed and booted, you need to make sure your Internet is working. It may take some configuration on your part but it is necessary for the SoupKit to install properly. Luckily, once you have an Internet connection in Linux, the hard part is over.
Don't put the SoupKit.zip on the USB drive before creating the LiveUSB. Instead, use the web browser to navigate to this page and download it once you have Linux running and your Internet connected. Once it's downloaded, you'll likely find it in your Downloads folder.
SoupKit has been tested extensively on all the latest versions of Ubuntu and Mint, but it hasn't really been tested on anything outside of that. Try other distros if you will, but be warned.
To install:
Right-click the “SoupKit.zip”, select “Extract here” open the SoupKit folder and follow the instructions in the README.
Credits:
Don't worry. I didn't forget about you guys. I'll finish this when I have time. In the meantime, you know who you are, and thank you.
Is that all?
NOPE. What SoupKit would be complete without a little something to go with it? SEE POST #2
Due to recent updates, I've decided to remove the option to install Hashcode's 2nd bootloader. There are too many areas where things can go wrong so I think it would be best to let the user follow the small handful of instructions in the 2nd bootloader thread to get it done. IMO, it is not worth the risk to rely on the user to make sure a downgraded stock bootloader is installed before running the script. Plus I think using a script toinstall the downgraded bootloader gives users a false sense of safety in what is potentially very dangerous to do.
ROOT PLUS for 2nd Generation Kindle Fires
That's right. This works for ALL 2nd generation Kindle Fires
What does it do?
The screenshot above should answer that question pretty quickly.
What do you need to know?
Since Hashcode's bootloader hack is device specific, you must download the version for your device. Each one has the exact same script but the stack, boot and recovery images are different for each particular device. You must have the SoupKit installed for this to work properly. It installs in the same way as the SoupKit; unzip, double click, run in terminal, blah blah.
Make sure you have ADB enabled under “Security” in the settings.
Anything else?
At any point after installation, if you need to run the utility again, just type "rootplus" in the terminal.
What's next?
I have a few more things in store for you guys and they will all be made for the SoupKit. As packages are installed, just type the name of the package in any terminal to launch them at any point (hence "modular"). Everything will be easy to install, easy to launch, and new user friendly.
Don't be skerrd. Move out of your comfort zone a little and give Linux and SoupKit a try. I'm sure you won't be disappointed.
Credits:
* Bin4ry - of course, for providing the root exploit
* prokennexusa and his team - for testing this out on all of the second generation devices
* Thepooch - for extensive testing and always being there to lend a hand
Downloads:
SoupKit - http://d-h.st/PbX
RootPlus for all Kindle Fires - http://d-h.st/jOe
Changelog:
04-23-2013 - Update (RootPlus)
* Removed option to install Hashcode's 2nd bootloader, for safety reasons. There is absolutely nothing wrong with Hashcode's 2nd bootloader. The risk lies in recent updates from Amazon.
03-19-2013 - Update + bugfix (RootPlus)
* Fixed issue with 2nd bootloader install - everything works as it should now
* Added timestamp to saved partitions. Gives users the ability to save more than one set of partition images
03-18-2013 - Update: (RootPlus)
* Changed how 2nd bootloader is installed for compatibility with the KF2
* Added ability to update custom recovery. No need to update the script every time a new recovery is released.
* Added ability to choose partition images to be installed if more than one set exist in the BACKUP folder
* More intuitive restore of saved partition images - will hopefully prevent any chance of user error
03-16-2013 - Bugfix: (RootPlus)
* Fixed issue with permissions on the rootplus script
03-10-2013 - Update: (RootPlus)
* Added extra safety measures, including MD5 check on 2nd bootloader install
02-23-2013 - Initial release
Will try thanks
Sent from my KFTT using xda premium
You, sir, are a wizard... Thanks for putting this together!
Sent from Hell™
Sorry, but I don't see a link for KFHD 7" package. Did I miss somthing?
Rootplus KF 7 is for Kindle Fire HD 7"?
Droid DNA
I'm stuck on installing the bootloader option 6. It back up the kfhd7 then go to installing stacks. There I get a line that is "/system/etc/install-recovery.sh' - No such file or directory" the kindle reboots. And that's were it stuck saying...< waiting for device >
zuke66 said:
I'm stuck on installing the bootloader option 6. It back up the kfhd7 then go to installing stacks. There I get a line that is "/system/etc/install-recovery.sh' - No such file or directory" the kindle reboots. And that's were it stuck saying...< waiting for device >
Click to expand...
Click to collapse
For now, use the restore option to restore the partitions that were saved when you chose the option to install the bootloader hack and TWRP.
In the meantime, I need to know what software version you're using, and whether or not you have edited your build.prop. Also, after you restore your system, use adb to access the shell and list the contents of your /system/etc directory and post it here.
Code:
adb shell su -c "ls /system/etc"
When I do a restore it reboots then stop at "waiting for device"
Sent from my SPH-L710 using xda app-developers app
zuke66 said:
When I do a restore it reboots then stop at "waiting for device"
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Okay, a few questions...
Do you have normal use of the device? Does it boot normally? Have you rebooted yet (if not, don't)
You still haven't told me what software version you are running or whether or not you've edited your build.prop...
What Linux distro/version are you using?
Is your Linux install a full install, LiveUSB, or VM?
Is it 32 or 64 bit?
Are you using a USB 3.0 port?
Do you have a factory cable?
What is the output of the following command?:
Code:
sudo cat /etc/udev/rules.d/51-android.rules
Thanks dude I got adb working plus with the old soupkit revived my kindle fire 1st gen
Sent from my KFTT using xda premium
Update 3-10-2013: Added extra safety measures, including MD5 check on 2nd bootloader install
3-16-2013: Fixed issue with permissions on the rootplus script
03-18-2013 - Update: (RootPlus)
* Changed how 2nd bootloader is installed for compatibility with the KF2
* Added ability to update custom recovery. No need to update the script every time a new recovery is released.
* Added ability to choose partition images to be installed if more than one set exist in the BACKUP folder
* More intuitive restore of saved partition images - will hopefully prevent any chance of user error
03-19-2013 - Update + bugfix (RootPlus)
* Fixed issue with 2nd bootloader install - everything works as it should now
* Added timestamp to saved partitions. Gives users the ability to save more than one set of partition images
If you downloaded yesterday's update, please install this one. There was a bug preventing the 2nd bootloader install. It is fixed now.
Sorry for the inconvenience.
Hello, I'm stuck at step 6. Until "installing stack" it works fine, but than came some "not a directory" Alerts. See here:
http://pastebin.com/3rk4Vksh
Even setting it manualy with a rebooter-app in fastboot mode dosn't works, because it was not listed.
My System: Linux Mint 14 Cinnamon 64 bit (regular install). I dosn't have a fastboot cable yet, but the rebooter app. I think this is the point. The tool want to reboot it into fastboot, but it wants to boot normally.
Edit: I testet my fastboot with the instructons fron the 2nd bootloader tread and it works. But I have to boot normally and than rebooting it from the app into fastboot mode.
When did you download this? The most recent version installs the 2nd bootloader through the shell, not fastboot. And was your device rooted before trying to install the 2nd bootloader?
[Edit:] I think I see what the problem might be. Download this copy of the RootPlus script, place it in your ~/bin/SoupKit/files folder and replace the one that's already there. Let me know if that makes a difference and I'll upload an updated version.
It was the same, but I found the error. The directory tmp and the file install-recovery.sh were withe a .bak below. Just renamed and it should work.
Edit: it was succsessfull ^^
Panixy said:
It was the same, but I found the error. The directory tmp and the file install-recovery.sh were withe a .bak below. Just renamed and it should work.
Click to expand...
Click to collapse
Renaming install-recovery.sh to install-recovery.sh.bak is a necessary part of the recovery install. Why your tmp directory was renamed, I couldn't say. I'm looking at the script now and I don't see anything of the sort. I'll keep looking at it to see if anything stands out at me.
Thanks for this. I have a friend is no friend to linux, but I am. I read some other posts about rooting a kindle on software 7.30. Is this possible, or no? It's weird because people are successful to obtain root, but in post #2, it says that it will not work. just need to know so i can tell him.
either way, thank you for all the work that you do
Android SDK - Powerful tool and easy to set up for use with your HTC One M8
{
"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"
}
Note - Java is needed to Run SDK Manager - Install JAVA
The Reason that you would want to use Android SDK is because its very easy, it's well updated and it just WORKS! There is much more use with HTC devices with adb then with Samsung when it comes to the daily things like splash screens, radio updates, firmware. You will be dealing a lot with the bootloader and fastboot flashing. So to help out, I will post a helpful guide to help you get started for use with the HTC One M8.
Click to expand...
Click to collapse
USB 3.0 Information if Needed
USB 3.0 Windows 8 Solution Link 1
USB 3.0 Windows 8 Solution Lin 2 - Found in above thread
Part 1. Follow These Steps Below - (Preparation)
1. Download Android SDK For Windows
2. Click the
either the 32bit version or 64bit version
3. Create a folder in the C: and name it Android. See below
4. Place adt-bundle-windows in the Android Folder you just created. Use WinZip, WinRAR or 7-Zip to extract the contents inside the folder. See Below
5. Once extracted, Double click SDK Manager and instal all 4.4.2 and 4.3 items and under tools (SDK Tools and Platform Tools). See Picture Below
6. After all packages are installed and updated, download the latest HTC Sync Manager and install once download completes
7. Once Sync Manager completes installation process, go to control panel and uninstall HTC Sync Manager only, you will see HTC Driver in there as well (LEAVE IT THERE)
8. Important, make sure you enable developer options and turn on USB Debugging. Instructions Below if you are unsure how to do that
1. Go to Settings > About > Software information > More > Tap Build Number 5x
2. Once you get notification saying Developer options is unlocked go back to > settings
3. Click Developer options
4. Add check in the box USB Debugging
9. Plug phone into the computer and let it install all the drivers, you should see pop ups.
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
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\sdk\platform-tools
2. In Command prompt type
Code:
adb devices
3. If your output shows your device attached like below, then you are good to go!!!
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 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
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\sdk\platform-tools
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
Reserve if needed
Thanks! Good stuff.. I just installed Windows 8 and totally forgot that I had to reinstall this... ( which originally took me 8 hours to figure out the first time! Lol ) this will definitely help future HTC people out...
Thanks for the guide but will this work with USB 3.0? I have an Asus G750JW with 4x usb 3.0 ports and no usb 2.0
x70xchallengerx said:
Thanks for the guide but will this work with USB 3.0? I have an Asus G750JW with 4x usb 3.0 ports and no usb 2.0
Click to expand...
Click to collapse
USB 3.0 gets a bad rep. I do a lot of my adb with a USB 3.0 with few issues
Sent from my HTC6525LVW using Tapatalk
OP Updated
Updated OP
1. Added Environment Variables to no longer have to Change Directory
2. Cleaned up OP
3. Added Thanks
x70xchallengerx said:
Thanks for the guide but will this work with USB 3.0? I have an Asus G750JW with 4x usb 3.0 ports and no usb 2.0
Click to expand...
Click to collapse
wtoj34 said:
USB 3.0 gets a bad rep. I do a lot of my adb with a USB 3.0 with few issues
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I am aware that USB 3.0 does cause issues with adb, mostly the longer running ones it hangs sometimes, I don't have an answer for that right now, I am running with 2.0 still and I have zero issues.
This is something that I came across that seemed to resolve a lot of adb issues
USB 3.0 Help with ADB
also
XDA Thread I found that in
cant launch sdk manager
After installing abd on Windows8.1 64 is there a trick to launch so that i can add and update?
Fixed issue. New pc and forgot to install java...?
bdorr1105 said:
Android SDK - Powerful tool and easy to set up for use with your HTC One M8
USB 3.0 Information if Needed
USB 3.0 Windows 8 Solution Link 1
USB 3.0 Windows 8 Solution Lin 2 - Found in above thread
Part 1. Follow These Steps Below - (Preparation)
Part 2. Verifying ADB is set up properly and Working
Part 3. Environment Variables - No need to Change Directory in Command Prompt Anymore (This is if you want to - Not Required)
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
Click to expand...
Click to collapse
davidmatt34 said:
After installing abd on Windows8.1 64 is there a trick to launch so that i can add and update?
Fixed issue. New pc and forgot to install java...?
Click to expand...
Click to collapse
Thanks for sharing that, I added that as note in the OP...Glad you are setup and good to go
I feel like such an idiot, but I want to be sure I'm getting the latest HTC Sync... I follow the link in the OP and it takes me to support.. I Google and the same thing happens.. They move it over at HTC?
I found it here... http://www.htc.com/us/support/software/htc-sync-manager.aspx
And this worked flawlessly!! I was always afraid of going back to Windows 8.1 because of ADB/Fastboot being broken.. so far so good!! Side loading soon!!
jbarcus81 said:
I feel like such an idiot, but I want to be sure I'm getting the latest HTC Sync... I follow the link in the OP and it takes me to support.. I Google and the same thing happens.. They move it over at HTC?
I found it here... http://www.htc.com/us/support/software/htc-sync-manager.aspx
And this worked flawlessly!! I was always afraid of going back to Windows 8.1 because of ADB/Fastboot being broken.. so far so good!! Side loading soon!!
Click to expand...
Click to collapse
Glad everything is working, the link in my OP went to the same exact HTC Sync Manager yours did, pull yours you posted and mine side by side its the same, not sure what happened, either way glad you are up and running
bdorr1105 said:
Glad everything is working, the link in my OP went to the same exact HTC Sync Manager yours did, pull yours you posted and mine side by side its the same, not sure what happened, either way glad you are up and running
Click to expand...
Click to collapse
Yeah.. the link just wasn't working at the time.. weird..
jbarcus81 said:
Yeah.. the link just wasn't working at the time.. weird..
Click to expand...
Click to collapse
Thanks for the update
Sent from my HTC6525LVW using Tapatalk
Also make sure you don't have drivers installed for another phone.. ADB couldn't find my M8 until I uninstalled my lg spectrums drivers on Win 8.1
Sent from my HTC6525LVW using XDA Free mobile app
Nice job.. Thanks for this. My first W8.1 machine.
Guys can someone help ,,
everything is installed and still getting the following error :
C:\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
SH44FWM09049 device
C:\Android\android-sdk\platform-tools>
C:\Android\android-sdk\platform-tools>
C:\Android\android-sdk\platform-tools>fastboot reboot-bootloader
< waiting for device >
i've been trying to fix this for the past 4 hours but no luck ,, anyone ??
I$ device in fastboot mode?
nvmd
without changing environment variable we can even hold shift+right click the folder containing the adb and open command window from the menu isn't it?
technochatter said:
without changing environment variable we can even hold shift+right click the folder containing the adb and open command window from the menu isn't it?
Click to expand...
Click to collapse
Yes.
Code:
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
A lot.
Original Guide
Prerequisites
1.) Download LG Root
2.) Download LG Drivers
3.) A micro USB cable connected to your PC
4.) Your device must be unencrypted
5.) Before you ask a question, make sure you looked at the pictures in the guide.
1.) Download and unzip the LG_Root.zip in your preferred location
I chose the Desktop for my location
{
"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"
}
2.) Enable ADB debugging on your device
Go to Settings > About Phone > Software Information and tap build number until you are presented with "You are now a developer"
Exit back to Settings main screen
In Developer Options enable USB Debugging (Some devices require enabling PTP for debugging to work)
3.) In the root of LG_Root folder start a command prompt
Instructions may vary based on Window's version
Inside of LG_Root folder hold shift and right click a blank space you should see "Open command window here"
4.) Now that we have a command prompt running in the root of the folder let's get started. (Commands are copy+paste unless specified)
Let's make sure our device is connected
Code:
adb.exe devices
5.) Great! My device is connected let's continue, we need to get the files onto the device used for this root method.
In the same command prompt let's execute another command
Code:
adb.exe push busybox /data/local/tmp/ && adb.exe push lg_root.sh /data/local/tmp && adb.exe push UPDATE-SuperSU-v2.46.zip /data/local/tmp
6.) Well that was easy , let's continue (Now that we have the files on our device we want to put our device is download mode)
(Note this method may vary from device to device)
Power off your device
When the device is powered off, hold volume up and insert a USB cable connected to the PC
Wait for the drivers to install
7.) We're almost done (you've managed to get in download mode)
8.) Let's find which COM port our device is connected to
Double click ports.bat (This will give us the COM port in which our device is connected we are looking for the Diag port)
You may exit this command prompt when you have your COM port number, keep the other command prompt open
9.) Let's Begin! (Keep the device in Download mode)
Let's run Send_Command.exe (It couldn't connect? Make sure you COM port number is correct it varies)
Code:
Send_Command.exe \\.\COM4
10.) Final Step!!!!!! (We must run the root script)
Code:
sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
11.) We're done
You may pull the battery to get the device out of Download mode
Credit
All credit goes to @jgkim find a post and thank this guy for posting the method.
Thank @high247 for ports.bat
One Click Root
You can follow the one click root guide here thanks to @avicohh
Devices confirmed working with root method (If your device isn't listed it's most likely still supported)
LG F60 (all variants)
LG Tribute (all variants)
LG G2 (all variants)
LG MS395/D393
LG G3 (all variants)
LG L90 (all variants)
LG Transpyre
LG Volt (LS740)
LG G Flex 2
NOTE: Do not attempt this on devices with 5.1.1 , at the time this method was posted it worked on many firmware 5.0.2 and below. With the current releases from LG, this method has and will brick many users. This can be said for the one click method as well. Failure to read the complete thread may render your device non repairable as the KDZ firmware isn't released for all LG devices.
Are u saying it unlocks vzw boot loader
EDIT: Fixed, Bootloader Unlocked.
dabug123 said:
Are u saying it unlocks vzw boot loader
Click to expand...
Click to collapse
It works for some devices. It has yet to be confirmed. The confirmed devices are for root only.
Unjustified Dev said:
It works for some devices. It has yet to be confirmed. The confirmed devices are for root only.
Click to expand...
Click to collapse
Right root,unlock vzw g3 my question there is fastboot was removed..So is fastboot being replaced with that.
dabug123 said:
Right root,unlock vzw g3 my question there is fastboot was removed..So is fastboot being replaced with that.
Click to expand...
Click to collapse
After zeroing out the LAF partition the boot loader falls back to fastboot the LAF partition is simply LG's Download mode. Once it falls back to fastboot you can run fastboot commands , but nothing is being replaced it existed it was just a priority LAF over fastboot. If fastboot was removed by LG in your device it wouldn't be replaced.
Unjustified Dev said:
After zeroing out the LAF partition the boot loader falls back to fastboot the LAF partition is simply LG's Download mode. Once it falls back to fastboot you can run fastboot commands , but nothing is being replaced it existed it was just a priority LAF over fastboot. If fastboot was removed by LG in your device it wouldn't be replaced.
Click to expand...
Click to collapse
yes I understand laf and the ends and outs,what I'm saying is fastboot was removed on the Verizon g3 so if I remove laf there will be no fastboot.just confirming this can't replace fastboot that was removed
dabug123 said:
yes I understand laf and the ends and outs,what I'm saying is fastboot was removed on the Verizon g3 so if I remove laf there will be no fastboot.just confirming this can't replace fastboot that was removed
Click to expand...
Click to collapse
I guess I should warn people about that thanks, hopefully someone can find a workaround for the secure boot.
Unjustified Dev said:
I guess I should warn people about that thanks.
Click to expand...
Click to collapse
Ya definitely ,I know better but guy above may have already gone down that road.Would be nice to replace it somehow..The users may not realize Verizon is the only g3 with no fastboot and removing laf can be very dangerous..
EDIT: Fixed problem.
high247 said:
I've re installed the LG Driver three times with no luck getting my phone to be recognized when I'm in fastboot mode.
I attached a picture showing with what is happening when in fastboot. I did try poniting to the LG Driver Folder, but it said it could not find anything. When I'm just in MTP or PTP Debug Mode the phone is recognized, so I'm confused.
Click to expand...
Click to collapse
It may be due to XP but could you try this guide here here
Unjustified Dev said:
It may be due to XP but could you try this guide here here
Click to expand...
Click to collapse
Hey I'm still on xp for a few more weeks till my new beast gets built.
Going to try that now. Thanks for helping!
dabug123 said:
Ya definitely ,I know better but guy above may have already gone down that road.Would be nice to replace it somehow..The users may not realize Verizon is the only g3 with no fastboot and removing laf can be very dangerous..
Click to expand...
Click to collapse
You can actually add it back manually just start a shell and reverse the command
dd if=/sdcard/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
added it to guide. Thanks again.
Got it my driver issue fixed with the help of this post http://forum.xda-developers.com/showpost.php?p=59310899&postcount=471 the driver in the file he attached is just what I needed to get it to work correctly.
It might also be very useful for anyone else who might run into the same problem I did. Cheers!
---------- Post added at 02:15 AM ---------- Previous post was at 02:10 AM ----------
Rooted, Bootloader UNLOCKED, and installed AdFree.apk... Today was a good day!
Unjustified Dev said:
You can actually add it back manually just start a shell and reverse the command
dd if=/sdcard/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
added it to guide. Thanks again.
Click to expand...
Click to collapse
No u misunderstood me again I mean I wish this was a way to put fastboot back.Good u added those instructions though for adding laf back,good to have posted.
Thank you so much Unjustified Dev! I was almost quite literally banging my head against a wall trying to figure this out. This guide was just I needed. My mistake was just opening the command prompt by itself instead of opening the command prompt in the folder itself. No I'm fully rooted. Thanks again!:good:
Root method works for LG Volt LS740 - ZV4 and ZV5 firmware
Unjustified Dev said:
You can actually add it back manually just start a shell and reverse the command
dd if=/sdcard/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
added it to guide. Thanks again.
Click to expand...
Click to collapse
I can't do this because I'm on vzw, but I must be missing something.
Normally you would have to run a fastboot command similar to, fastboot oem unlock, but I don't see where you instructed to run any commands.
Maybe I overlooked it, went to bed at 12 and woke up for work at 4:30 lol
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